Imported Translations from Transifex
Change-Id: I2a18bdf99b884c45b55707c1218d0eec54600fd7
This commit is contained in:
OpenStack Proposal Bot
parent
34f38616b4
commit
711d938069
@ -1,7 +1,7 @@
|
||||
msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: PACKAGE VERSION\n"
|
||||
"POT-Creation-Date: 2014-07-04 06:05+0000\n"
|
||||
"POT-Creation-Date: 2014-07-08 06:08+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"
|
||||
@ -123,34 +123,34 @@ msgid "Then the LogAdapter object returned by <code>get_logger()</code>, usually
|
||||
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."
|
||||
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”, and so on. 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)
|
||||
#: ./doc/admin-guide-cloud/section_object-storage-monitoring.xml:212(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)
|
||||
#: ./doc/admin-guide-cloud/section_object-storage-monitoring.xml:221(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)
|
||||
#: ./doc/admin-guide-cloud/section_object-storage-monitoring.xml:226(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)
|
||||
#: ./doc/admin-guide-cloud/section_object-storage-monitoring.xml:231(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)
|
||||
#: ./doc/admin-guide-cloud/section_object-storage-monitoring.xml:237(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)
|
||||
#: ./doc/admin-guide-cloud/section_object-storage-monitoring.xml:243(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)
|
||||
#: ./doc/admin-guide-cloud/section_object-storage-monitoring.xml:286(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 ""
|
||||
|
||||
|
||||
File diff suppressed because it is too large
Load Diff
File diff suppressed because it is too large
Load Diff
File diff suppressed because it is too large
Load Diff
@ -1,7 +1,7 @@
|
||||
msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: PACKAGE VERSION\n"
|
||||
"POT-Creation-Date: 2014-07-01 06:07+0000\n"
|
||||
"POT-Creation-Date: 2014-07-08 06:08+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"
|
||||
@ -133,83 +133,83 @@ msgstr ""
|
||||
msgid "Orchestration"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/bk-config-ref.xml:6(title) ./doc/config-reference/bk-config-ref.xml:8(titleabbrev)
|
||||
#: ./doc/config-reference/bk-config-ref.xml:7(title) ./doc/config-reference/bk-config-ref.xml:12(titleabbrev)
|
||||
msgid "OpenStack Configuration Reference"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/bk-config-ref.xml:16(orgname) ./doc/config-reference/bk-config-ref.xml:22(holder)
|
||||
#: ./doc/config-reference/bk-config-ref.xml:20(orgname) ./doc/config-reference/bk-config-ref.xml:26(holder)
|
||||
msgid "OpenStack Foundation"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/bk-config-ref.xml:20(year)
|
||||
#: ./doc/config-reference/bk-config-ref.xml:24(year)
|
||||
msgid "2013"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/bk-config-ref.xml:21(year)
|
||||
#: ./doc/config-reference/bk-config-ref.xml:25(year)
|
||||
msgid "2014"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/bk-config-ref.xml:24(productname)
|
||||
#: ./doc/config-reference/bk-config-ref.xml:28(productname)
|
||||
msgid "OpenStack"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/bk-config-ref.xml:25(releaseinfo)
|
||||
#: ./doc/config-reference/bk-config-ref.xml:29(releaseinfo)
|
||||
msgid "icehouse"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/bk-config-ref.xml:29(remark)
|
||||
#: ./doc/config-reference/bk-config-ref.xml:33(remark)
|
||||
msgid "Copyright details are filled in by the template."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/bk-config-ref.xml:34(para)
|
||||
#: ./doc/config-reference/bk-config-ref.xml:38(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:44(date)
|
||||
#: ./doc/config-reference/bk-config-ref.xml:48(date)
|
||||
msgid "2014-04-16"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/bk-config-ref.xml:48(para)
|
||||
#: ./doc/config-reference/bk-config-ref.xml:52(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:59(date)
|
||||
#: ./doc/config-reference/bk-config-ref.xml:63(date)
|
||||
msgid "2014-03-11"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/bk-config-ref.xml:63(para)
|
||||
#: ./doc/config-reference/bk-config-ref.xml:67(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:72(date)
|
||||
#: ./doc/config-reference/bk-config-ref.xml:76(date)
|
||||
msgid "2014-01-09"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/bk-config-ref.xml:76(para)
|
||||
#: ./doc/config-reference/bk-config-ref.xml:80(para)
|
||||
msgid "Removes content addressed in installation, merges duplicated content, and revises legacy references."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/bk-config-ref.xml:85(date)
|
||||
#: ./doc/config-reference/bk-config-ref.xml:89(date)
|
||||
msgid "2013-10-17"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/bk-config-ref.xml:89(para)
|
||||
#: ./doc/config-reference/bk-config-ref.xml:93(para)
|
||||
msgid "Havana release."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/bk-config-ref.xml:95(date)
|
||||
#: ./doc/config-reference/bk-config-ref.xml:99(date)
|
||||
msgid "2013-08-16"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/bk-config-ref.xml:99(para)
|
||||
#: ./doc/config-reference/bk-config-ref.xml:103(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:109(date)
|
||||
#: ./doc/config-reference/bk-config-ref.xml:113(date)
|
||||
msgid "2013-06-10"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/bk-config-ref.xml:113(para)
|
||||
#: ./doc/config-reference/bk-config-ref.xml:117(para)
|
||||
msgid "Initial creation of Configuration Reference."
|
||||
msgstr ""
|
||||
|
||||
@ -7271,7 +7271,7 @@ msgid "http://www.lfd.uci.edu/~gohlke/pythonlibs/"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:206(para)
|
||||
msgid "You must scroll to the greenlet section for the following file: greenlet-0.4.0.win32-py2.7.exe"
|
||||
msgid "You must scroll to the greenlet section for the following file: greenlet-0.4.0.win32-py2.7.exe"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:208(para)
|
||||
@ -7614,7 +7614,7 @@ 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."
|
||||
msgid "Management network - RabbitMQ, MySQL, and other services. 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)
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: PACKAGE VERSION\n"
|
||||
"POT-Creation-Date: 2014-07-01 06:07+0000\n"
|
||||
"POT-Creation-Date: 2014-07-08 06:08+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"
|
||||
@ -1970,7 +1970,7 @@ msgid "deduplication<indexterm class=\"singular\"><placeholder-1/></indexterm>"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/glossary/glossary-terms.xml:1996(para)
|
||||
msgid "The process of finding duplicate data at the disk block, file, and/or object level to minimize storage use—currently unsupported within OpenStack."
|
||||
msgid "The process of finding duplicate data at the disk block, file, and/or object level to minimize storage usecurrently unsupported within OpenStack."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/glossary/glossary-terms.xml:2004(primary)
|
||||
@ -2706,7 +2706,7 @@ msgid "exclusive queue<indexterm class=\"singular\"><placeholder-1/><placeholder
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/glossary/glossary-terms.xml:2725(para)
|
||||
msgid "Connected to by a direct consumer in RabbitMQ—Compute, the message can be consumed only by the current connection."
|
||||
msgid "Connected to by a direct consumer in RabbitMQCompute, the message can be consumed only by the current connection."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/glossary/glossary-terms.xml:2732(primary)
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: PACKAGE VERSION\n"
|
||||
"POT-Creation-Date: 2014-07-01 06:07+0000\n"
|
||||
"POT-Creation-Date: 2014-07-08 06:08+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,187 +9,187 @@ msgstr ""
|
||||
"Content-Type: text/plain; charset=UTF-8\n"
|
||||
"Content-Transfer-Encoding: 8bit\n"
|
||||
|
||||
#: ./doc/high-availability-guide/ch_controller.xml:6(title)
|
||||
#: ./doc/high-availability-guide/ch_controller.xml:7(title)
|
||||
msgid "Cloud controller cluster stack"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/ch_controller.xml:8(simpara)
|
||||
#: ./doc/high-availability-guide/ch_controller.xml:9(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)
|
||||
#: ./doc/high-availability-guide/ch_ha_aa_network.xml:7(title)
|
||||
msgid "OpenStack network nodes"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/ch_ha_aa_network.xml:8(simpara)
|
||||
#: ./doc/high-availability-guide/ch_ha_aa_network.xml:9(simpara)
|
||||
msgid "OpenStack network nodes contain:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/ch_ha_aa_network.xml:11(simpara)
|
||||
#: ./doc/high-availability-guide/ch_ha_aa_network.xml:12(simpara)
|
||||
msgid "neutron DHCP agent"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/ch_ha_aa_network.xml:16(simpara)
|
||||
#: ./doc/high-availability-guide/ch_ha_aa_network.xml:17(simpara)
|
||||
msgid "neutron L2 agent"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/ch_ha_aa_network.xml:21(simpara)
|
||||
#: ./doc/high-availability-guide/ch_ha_aa_network.xml:22(simpara)
|
||||
msgid "Neutron L3 agent"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/ch_ha_aa_network.xml:26(simpara)
|
||||
#: ./doc/high-availability-guide/ch_ha_aa_network.xml:27(simpara)
|
||||
msgid "neutron metadata agent"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/ch_ha_aa_network.xml:31(simpara)
|
||||
#: ./doc/high-availability-guide/ch_ha_aa_network.xml:32(simpara)
|
||||
msgid "neutron lbaas agent"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/ch_ha_aa_network.xml:37(simpara)
|
||||
#: ./doc/high-availability-guide/ch_ha_aa_network.xml:38(simpara)
|
||||
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_pacemaker.xml:6(title)
|
||||
#: ./doc/high-availability-guide/ch_pacemaker.xml:7(title)
|
||||
msgid "The Pacemaker cluster stack"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/ch_pacemaker.xml:8(simpara)
|
||||
#: ./doc/high-availability-guide/ch_pacemaker.xml:9(simpara)
|
||||
msgid "OpenStack infrastructure high availability relies on the <link href=\"http://www.clusterlabs.org\">Pacemaker</link> cluster stack, the state-of-the-art high availability and load balancing stack for the Linux platform. Pacemaker is storage and application-agnostic, and is in no way specific to OpenStack."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/ch_pacemaker.xml:13(simpara)
|
||||
#: ./doc/high-availability-guide/ch_pacemaker.xml:14(simpara)
|
||||
msgid "Pacemaker relies on the <link href=\"http://www.corosync.org\">Corosync</link> messaging layer for reliable cluster communications. Corosync implements the Totem single-ring ordering and membership protocol. It also provides UDP and InfiniBand based messaging, quorum, and cluster membership to Pacemaker."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/ch_pacemaker.xml:18(simpara)
|
||||
#: ./doc/high-availability-guide/ch_pacemaker.xml:19(simpara)
|
||||
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/ch_ha_aa_rabbitmq.xml:6(title)
|
||||
#: ./doc/high-availability-guide/ch_ha_aa_rabbitmq.xml:7(title)
|
||||
msgid "RabbitMQ"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/ch_ha_aa_rabbitmq.xml:8(simpara)
|
||||
#: ./doc/high-availability-guide/ch_ha_aa_rabbitmq.xml:9(simpara)
|
||||
msgid "RabbitMQ is the default AMQP server used by many OpenStack services. Making the RabbitMQ service highly available involves the following steps:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/ch_ha_aa_rabbitmq.xml:12(simpara) ./doc/high-availability-guide/ha_aa_rabbitmq/section_install_rabbitmq.xml:6(title)
|
||||
#: ./doc/high-availability-guide/ch_ha_aa_rabbitmq.xml:13(simpara) ./doc/high-availability-guide/ha_aa_rabbitmq/section_install_rabbitmq.xml:6(title)
|
||||
msgid "Install RabbitMQ"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/ch_ha_aa_rabbitmq.xml:17(simpara)
|
||||
#: ./doc/high-availability-guide/ch_ha_aa_rabbitmq.xml:18(simpara)
|
||||
msgid "Configure RabbitMQ for HA queues"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/ch_ha_aa_rabbitmq.xml:22(simpara)
|
||||
#: ./doc/high-availability-guide/ch_ha_aa_rabbitmq.xml:23(simpara)
|
||||
msgid "Configure OpenStack services to use Rabbit HA queues"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/ch_intro.xml:6(title)
|
||||
#: ./doc/high-availability-guide/ch_intro.xml:7(title)
|
||||
msgid "Introduction to OpenStack High Availability"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/ch_intro.xml:8(simpara)
|
||||
#: ./doc/high-availability-guide/ch_intro.xml:9(simpara)
|
||||
msgid "High Availability systems seek to minimize two things:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/ch_intro.xml:11(simpara)
|
||||
#: ./doc/high-availability-guide/ch_intro.xml:12(simpara)
|
||||
msgid "<emphasis role=\"strong\">System downtime</emphasis> — occurs when a <emphasis>user-facing</emphasis> service is unavailable beyond a specified maximum amount of time, and"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/ch_intro.xml:15(simpara)
|
||||
#: ./doc/high-availability-guide/ch_intro.xml:16(simpara)
|
||||
msgid "<emphasis role=\"strong\">Data loss</emphasis> — accidental deletion or destruction of data."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/ch_intro.xml:19(simpara)
|
||||
#: ./doc/high-availability-guide/ch_intro.xml:20(simpara)
|
||||
msgid "Most high availability systems guarantee protection against system downtime and data loss only in the event of a single failure. However, they are also expected to protect against cascading failures, where a single failure deteriorates into a series of consequential failures."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/ch_intro.xml:20(simpara)
|
||||
#: ./doc/high-availability-guide/ch_intro.xml:21(simpara)
|
||||
msgid "A crucial aspect of high availability is the elimination of single points of failure (SPOFs). A SPOF is an individual piece of equipment or software which will cause system downtime or data loss if it fails. In order to eliminate SPOFs, check that mechanisms exist for redundancy of:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/ch_intro.xml:23(simpara)
|
||||
#: ./doc/high-availability-guide/ch_intro.xml:24(simpara)
|
||||
msgid "Network components, such as switches and routers"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/ch_intro.xml:28(simpara)
|
||||
#: ./doc/high-availability-guide/ch_intro.xml:29(simpara)
|
||||
msgid "Applications and automatic service migration"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/ch_intro.xml:33(simpara)
|
||||
#: ./doc/high-availability-guide/ch_intro.xml:34(simpara)
|
||||
msgid "Storage components"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/ch_intro.xml:38(simpara)
|
||||
#: ./doc/high-availability-guide/ch_intro.xml:39(simpara)
|
||||
msgid "Facility services such as power, air conditioning, and fire protection"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/ch_intro.xml:43(simpara)
|
||||
#: ./doc/high-availability-guide/ch_intro.xml:44(simpara)
|
||||
msgid "Most high availability systems will fail in the event of multiple independent (non-consequential) failures. In this case, most systems will protect data over maintaining availability."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/ch_intro.xml:44(simpara)
|
||||
#: ./doc/high-availability-guide/ch_intro.xml:45(simpara)
|
||||
msgid "High-availability systems typically achieve uptime of 99.99% or more, which roughly equates to less than an hour of cumulative downtime per year. In order to achieve this, high availability systems should keep recovery times after a failure to about one to two minutes, sometimes significantly less."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/ch_intro.xml:45(simpara)
|
||||
#: ./doc/high-availability-guide/ch_intro.xml:46(simpara)
|
||||
msgid "OpenStack currently meets such availability requirements for its own infrastructure services, meaning that an uptime of 99.99% is feasible for the OpenStack infrastructure proper. However, OpenStack <emphasis>does</emphasis><emphasis>not</emphasis> guarantee 99.99% availability for individual guest instances."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/ch_intro.xml:46(simpara)
|
||||
#: ./doc/high-availability-guide/ch_intro.xml:47(simpara)
|
||||
msgid "Preventing single points of failure can depend on whether or not a service is stateless."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/ch_intro.xml:49(title)
|
||||
#: ./doc/high-availability-guide/ch_intro.xml:50(title)
|
||||
msgid "Stateless vs. Stateful services"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/ch_intro.xml:51(simpara)
|
||||
#: ./doc/high-availability-guide/ch_intro.xml:52(simpara)
|
||||
msgid "A stateless service is one that provides a response after your request, and then requires no further attention. To make a stateless service highly available, you need to provide redundant instances and load balance them. OpenStack services that are stateless include nova-api, nova-conductor, glance-api, keystone-api, neutron-api and nova-scheduler."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/ch_intro.xml:52(simpara)
|
||||
#: ./doc/high-availability-guide/ch_intro.xml:53(simpara)
|
||||
msgid "A stateful service is one where subsequent requests to the service depend on the results of the first request. Stateful services are more difficult to manage because a single action typically involves more than one request, so simply providing additional instances and load balancing will not solve the problem. For example, if the Horizon user interface reset itself every time you went to a new page, it wouldn’t be very useful. OpenStack services that are stateful include the OpenStack database and message queue."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/ch_intro.xml:53(simpara)
|
||||
#: ./doc/high-availability-guide/ch_intro.xml:54(simpara)
|
||||
msgid "Making stateful services highly available can depend on whether you choose an active/passive or active/active configuration."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/ch_intro.xml:57(title)
|
||||
#: ./doc/high-availability-guide/ch_intro.xml:58(title)
|
||||
msgid "Active/Passive"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/ch_intro.xml:59(simpara)
|
||||
#: ./doc/high-availability-guide/ch_intro.xml:60(simpara)
|
||||
msgid "In an active/passive configuration, systems are set up to bring additional resources online to replace those that have failed. For example, OpenStack would write to the main database while maintaining a disaster recovery database that can be brought online in the event that the main database fails."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/ch_intro.xml:60(simpara)
|
||||
#: ./doc/high-availability-guide/ch_intro.xml:61(simpara)
|
||||
msgid "Typically, an active/passive installation for a stateless service would maintain a redundant instance that can be brought online when required. Requests are load balanced using a virtual IP address and a load balancer such as HAProxy."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/ch_intro.xml:61(simpara)
|
||||
#: ./doc/high-availability-guide/ch_intro.xml:62(simpara)
|
||||
msgid "A typical active/passive installation for a stateful service maintains a replacement resource that can be brought online when required. A separate application (such as Pacemaker or Corosync) monitors these services, bringing the backup online as necessary."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/ch_intro.xml:65(title)
|
||||
#: ./doc/high-availability-guide/ch_intro.xml:66(title)
|
||||
msgid "Active/Active"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/ch_intro.xml:67(simpara)
|
||||
#: ./doc/high-availability-guide/ch_intro.xml:68(simpara)
|
||||
msgid "In an active/active configuration, systems also use a backup but will manage both the main and redundant systems concurrently. This way, if there is a failure the user is unlikely to notice. The backup system is already online, and takes on increased load while the main system is fixed and brought back online."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/ch_intro.xml:68(simpara)
|
||||
#: ./doc/high-availability-guide/ch_intro.xml:69(simpara)
|
||||
msgid "Typically, an active/active installation for a stateless service would maintain a redundant instance, and requests are load balanced using a virtual IP address and a load balancer such as HAProxy."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/ch_intro.xml:69(simpara)
|
||||
#: ./doc/high-availability-guide/ch_intro.xml:70(simpara)
|
||||
msgid "A typical active/active installation for a stateful service would include redundant services with all instances having an identical state. For example, updates to one instance of a database would also update all other instances. This way a request to one instance is the same as a request to any other. A load balancer manages the traffic to these systems, ensuring that operational systems always handle the request."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/ch_intro.xml:70(simpara)
|
||||
#: ./doc/high-availability-guide/ch_intro.xml:71(simpara)
|
||||
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 ""
|
||||
|
||||
@ -277,83 +277,83 @@ msgstr ""
|
||||
msgid "Begin trunk designation."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/ch_network.xml:6(title)
|
||||
#: ./doc/high-availability-guide/ch_network.xml:7(title)
|
||||
msgid "Network controller cluster stack"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/ch_network.xml:8(simpara)
|
||||
#: ./doc/high-availability-guide/ch_network.xml:9(simpara)
|
||||
msgid "The network controller sits on the management and data network, and needs to be connected to the Internet if a VM needs access to it."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/ch_network.xml:10(simpara)
|
||||
#: ./doc/high-availability-guide/ch_network.xml:11(simpara)
|
||||
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/ch_ha_aa_haproxy.xml:6(title)
|
||||
#: ./doc/high-availability-guide/ch_ha_aa_haproxy.xml:7(title)
|
||||
msgid "HAproxy nodes"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/ch_ha_aa_haproxy.xml:8(simpara)
|
||||
#: ./doc/high-availability-guide/ch_ha_aa_haproxy.xml:9(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)
|
||||
#: ./doc/high-availability-guide/ch_ha_aa_haproxy.xml:13(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)
|
||||
#: ./doc/high-availability-guide/ch_ha_aa_haproxy.xml:16(simpara)
|
||||
msgid "Here is an example for HAproxy configuration file:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/ch_ha_aa_haproxy.xml:155(simpara)
|
||||
#: ./doc/high-availability-guide/ch_ha_aa_haproxy.xml:156(simpara)
|
||||
msgid "After each change of this file, you should restart HAproxy."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/ch_ha_aa_controllers.xml:6(title)
|
||||
#: ./doc/high-availability-guide/ch_ha_aa_controllers.xml:7(title)
|
||||
msgid "OpenStack controller nodes"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/ch_ha_aa_controllers.xml:8(simpara)
|
||||
#: ./doc/high-availability-guide/ch_ha_aa_controllers.xml:9(simpara)
|
||||
msgid "OpenStack controller nodes contain:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/ch_ha_aa_controllers.xml:11(simpara)
|
||||
#: ./doc/high-availability-guide/ch_ha_aa_controllers.xml:12(simpara)
|
||||
msgid "All OpenStack API services"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/ch_ha_aa_controllers.xml:16(simpara)
|
||||
#: ./doc/high-availability-guide/ch_ha_aa_controllers.xml:17(simpara)
|
||||
msgid "All OpenStack schedulers"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/ch_ha_aa_controllers.xml:21(simpara)
|
||||
#: ./doc/high-availability-guide/ch_ha_aa_controllers.xml:22(simpara)
|
||||
msgid "Memcached service"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/part_active_passive.xml:6(title)
|
||||
#: ./doc/high-availability-guide/part_active_passive.xml:7(title)
|
||||
msgid "HA using active/passive"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/ch_api.xml:6(title)
|
||||
#: ./doc/high-availability-guide/ch_api.xml:7(title)
|
||||
msgid "API node cluster stack"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/ch_api.xml:8(simpara)
|
||||
#: ./doc/high-availability-guide/ch_api.xml:9(simpara)
|
||||
msgid "The API node exposes OpenStack API endpoints onto external network (Internet). It must talk to the cloud controller on the management network."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/ch_ha_aa_db.xml:6(title)
|
||||
#: ./doc/high-availability-guide/ch_ha_aa_db.xml:7(title)
|
||||
msgid "Database"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/ch_ha_aa_db.xml:8(simpara)
|
||||
#: ./doc/high-availability-guide/ch_ha_aa_db.xml:9(simpara)
|
||||
msgid "The first step is installing the database that sits at the heart of the cluster. When we talk about High Availability, we talk about several databases (for redundancy) and a means to keep them synchronized. In this case, we must choose the MySQL database, along with Galera for synchronous multi-master replication."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/ch_ha_aa_db.xml:12(simpara)
|
||||
#: ./doc/high-availability-guide/ch_ha_aa_db.xml:13(simpara)
|
||||
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/part_active_active.xml:6(title)
|
||||
#: ./doc/high-availability-guide/part_active_active.xml:7(title)
|
||||
msgid "HA using active/active"
|
||||
msgstr ""
|
||||
|
||||
@ -529,7 +529,7 @@ msgstr ""
|
||||
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)
|
||||
#: ./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:190(simpara) ./doc/high-availability-guide/controller/section_mysql.xml:202(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 ""
|
||||
|
||||
@ -853,259 +853,259 @@ msgstr ""
|
||||
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)
|
||||
#: ./doc/high-availability-guide/controller/section_rabbitmq.xml:11(title)
|
||||
msgid "Highly available RabbitMQ"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/controller/section_rabbitmq.xml:8(simpara)
|
||||
#: ./doc/high-availability-guide/controller/section_rabbitmq.xml:13(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)
|
||||
#: ./doc/high-availability-guide/controller/section_rabbitmq.xml:17(simpara)
|
||||
msgid "configuring a DRBD device for use by RabbitMQ,"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/controller/section_rabbitmq.xml:17(simpara)
|
||||
#: ./doc/high-availability-guide/controller/section_rabbitmq.xml:22(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)
|
||||
#: ./doc/high-availability-guide/controller/section_rabbitmq.xml:28(simpara) ./doc/high-availability-guide/controller/section_mysql.xml:28(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)
|
||||
#: ./doc/high-availability-guide/controller/section_rabbitmq.xml:34(simpara)
|
||||
msgid "configuring RabbitMQ to listen on that IP address,"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/controller/section_rabbitmq.xml:34(simpara)
|
||||
#: ./doc/high-availability-guide/controller/section_rabbitmq.xml:39(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."
|
||||
#: ./doc/high-availability-guide/controller/section_rabbitmq.xml:46(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 developershowever 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)
|
||||
#: ./doc/high-availability-guide/controller/section_rabbitmq.xml:58(title) ./doc/high-availability-guide/controller/section_mysql.xml:55(title)
|
||||
msgid "Configure DRBD"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/controller/section_rabbitmq.xml:55(simpara)
|
||||
#: ./doc/high-availability-guide/controller/section_rabbitmq.xml:60(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)
|
||||
#: ./doc/high-availability-guide/controller/section_rabbitmq.xml:65(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)
|
||||
#: ./doc/high-availability-guide/controller/section_rabbitmq.xml:81(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)
|
||||
#: ./doc/high-availability-guide/controller/section_rabbitmq.xml:90(simpara) ./doc/high-availability-guide/controller/section_mysql.xml:87(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)
|
||||
#: ./doc/high-availability-guide/controller/section_rabbitmq.xml:98(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)
|
||||
#: ./doc/high-availability-guide/controller/section_rabbitmq.xml:104(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)
|
||||
#: ./doc/high-availability-guide/controller/section_rabbitmq.xml:111(para) ./doc/high-availability-guide/controller/section_mysql.xml:108(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)
|
||||
#: ./doc/high-availability-guide/controller/section_rabbitmq.xml:125(title)
|
||||
msgid "Create a file system"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/controller/section_rabbitmq.xml:122(simpara)
|
||||
#: ./doc/high-availability-guide/controller/section_rabbitmq.xml:127(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)
|
||||
#: ./doc/high-availability-guide/controller/section_rabbitmq.xml:132(simpara) ./doc/high-availability-guide/controller/section_mysql.xml:129(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)
|
||||
#: ./doc/high-availability-guide/controller/section_rabbitmq.xml:136(simpara) ./doc/high-availability-guide/controller/section_mysql.xml:133(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)
|
||||
#: ./doc/high-availability-guide/controller/section_rabbitmq.xml:143(title)
|
||||
msgid "Prepare RabbitMQ for Pacemaker high availability"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/controller/section_rabbitmq.xml:140(simpara)
|
||||
#: ./doc/high-availability-guide/controller/section_rabbitmq.xml:145(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)
|
||||
#: ./doc/high-availability-guide/controller/section_rabbitmq.xml:158(title)
|
||||
msgid "Add RabbitMQ resources to Pacemaker"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/controller/section_rabbitmq.xml:155(simpara)
|
||||
#: ./doc/high-availability-guide/controller/section_rabbitmq.xml:160(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)
|
||||
#: ./doc/high-availability-guide/controller/section_rabbitmq.xml:193(simpara)
|
||||
msgid "<literal>p_ip_rabbitmq</literal>, a virtual IP address for use by RabbitMQ (192.168.42.100),"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/controller/section_rabbitmq.xml:193(simpara)
|
||||
#: ./doc/high-availability-guide/controller/section_rabbitmq.xml:198(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)
|
||||
#: ./doc/high-availability-guide/controller/section_rabbitmq.xml:204(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)
|
||||
#: ./doc/high-availability-guide/controller/section_rabbitmq.xml:209(simpara) ./doc/high-availability-guide/controller/section_mysql.xml:221(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)
|
||||
#: ./doc/high-availability-guide/controller/section_rabbitmq.xml:215(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)
|
||||
#: ./doc/high-availability-guide/controller/section_rabbitmq.xml:220(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)
|
||||
#: ./doc/high-availability-guide/controller/section_rabbitmq.xml:226(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>):"
|
||||
#: ./doc/high-availability-guide/controller/section_rabbitmq.xml:228(simpara)
|
||||
msgid "Your OpenStack services must now point their RabbitMQ configuration to the highly available, virtual cluster IP addressrather than a RabbitMQ server"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/controller/section_rabbitmq.xml:231(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:236(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)
|
||||
#: ./doc/high-availability-guide/controller/section_mysql.xml:11(title)
|
||||
msgid "Highly available MySQL"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/controller/section_mysql.xml:8(simpara)
|
||||
#: ./doc/high-availability-guide/controller/section_mysql.xml:13(simpara)
|
||||
msgid "MySQL is the default database server used by many OpenStack services. Making the MySQL service highly available involves"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/controller/section_mysql.xml:12(simpara)
|
||||
#: ./doc/high-availability-guide/controller/section_mysql.xml:17(simpara)
|
||||
msgid "Configure a DRBD device for use by MySQL,"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/controller/section_mysql.xml:17(simpara)
|
||||
#: ./doc/high-availability-guide/controller/section_mysql.xml:22(simpara)
|
||||
msgid "Configure MySQL to use a data directory residing on that DRBD device,"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/controller/section_mysql.xml:29(simpara)
|
||||
#: ./doc/high-availability-guide/controller/section_mysql.xml:34(simpara)
|
||||
msgid "Configure MySQL to listen on that IP address,"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/controller/section_mysql.xml:34(simpara)
|
||||
#: ./doc/high-availability-guide/controller/section_mysql.xml:39(simpara)
|
||||
msgid "managing all resources, including the MySQL daemon itself, with the Pacemaker cluster manager."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/controller/section_mysql.xml:41(simpara)
|
||||
#: ./doc/high-availability-guide/controller/section_mysql.xml:46(simpara)
|
||||
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:52(simpara)
|
||||
#: ./doc/high-availability-guide/controller/section_mysql.xml:57(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 ""
|
||||
|
||||
#: ./doc/high-availability-guide/controller/section_mysql.xml:57(title)
|
||||
#: ./doc/high-availability-guide/controller/section_mysql.xml:62(title)
|
||||
msgid "<literal>mysql</literal> DRBD resource configuration (<literal>/etc/drbd.d/mysql.res</literal>)"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/controller/section_mysql.xml:73(simpara)
|
||||
#: ./doc/high-availability-guide/controller/section_mysql.xml:78(simpara)
|
||||
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:90(para)
|
||||
#: ./doc/high-availability-guide/controller/section_mysql.xml:95(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 ""
|
||||
|
||||
#: ./doc/high-availability-guide/controller/section_mysql.xml:96(para)
|
||||
#: ./doc/high-availability-guide/controller/section_mysql.xml:101(para)
|
||||
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:117(title)
|
||||
#: ./doc/high-availability-guide/controller/section_mysql.xml:122(title)
|
||||
msgid "Creating a file system"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/controller/section_mysql.xml:119(simpara)
|
||||
#: ./doc/high-availability-guide/controller/section_mysql.xml:124(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 MySQL data. XFS is the generally recommended filesystem:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/controller/section_mysql.xml:135(title)
|
||||
#: ./doc/high-availability-guide/controller/section_mysql.xml:140(title)
|
||||
msgid "Prepare MySQL for Pacemaker high availability"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/controller/section_mysql.xml:137(simpara)
|
||||
#: ./doc/high-availability-guide/controller/section_mysql.xml:142(simpara)
|
||||
msgid "In order for Pacemaker monitoring to function properly, you must ensure that MySQL’s database files reside on the DRBD device. If you already have an existing MySQL database, the simplest approach is to just move the contents of the existing <literal>/var/lib/mysql</literal> directory into the newly created filesystem on the DRBD device."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/controller/section_mysql.xml:143(simpara)
|
||||
#: ./doc/high-availability-guide/controller/section_mysql.xml:148(simpara)
|
||||
msgid "You must complete the next step while the MySQL database server is shut down."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/controller/section_mysql.xml:149(simpara)
|
||||
#: ./doc/high-availability-guide/controller/section_mysql.xml:154(simpara)
|
||||
msgid "For a new MySQL installation with no existing data, you may also run the <literal>mysql_install_db</literal> command:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/controller/section_mysql.xml:154(simpara)
|
||||
#: ./doc/high-availability-guide/controller/section_mysql.xml:159(simpara)
|
||||
msgid "Regardless of the approach, the steps outlined here must be completed on only one cluster node."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/controller/section_mysql.xml:159(title)
|
||||
#: ./doc/high-availability-guide/controller/section_mysql.xml:164(title)
|
||||
msgid "Add MySQL resources to Pacemaker"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/controller/section_mysql.xml:161(simpara)
|
||||
#: ./doc/high-availability-guide/controller/section_mysql.xml:166(simpara)
|
||||
msgid "You can now add the Pacemaker configuration for MySQL resources. Connect to the Pacemaker cluster with <literal>crm configure</literal>, and add the following cluster resources:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/controller/section_mysql.xml:200(simpara)
|
||||
#: ./doc/high-availability-guide/controller/section_mysql.xml:205(simpara)
|
||||
msgid "<literal>p_ip_mysql</literal>, a virtual IP address for use by MySQL (192.168.42.101),"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/controller/section_mysql.xml:205(simpara)
|
||||
#: ./doc/high-availability-guide/controller/section_mysql.xml:210(simpara)
|
||||
msgid "<literal>p_fs_mysql</literal>, a Pacemaker managed filesystem mounted to <literal>/var/lib/mysql</literal> on whatever node currently runs the MySQL service,"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/controller/section_mysql.xml:211(simpara)
|
||||
#: ./doc/high-availability-guide/controller/section_mysql.xml:216(simpara)
|
||||
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:222(simpara)
|
||||
#: ./doc/high-availability-guide/controller/section_mysql.xml:227(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 ""
|
||||
|
||||
#: ./doc/high-availability-guide/controller/section_mysql.xml:227(simpara)
|
||||
#: ./doc/high-availability-guide/controller/section_mysql.xml:232(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 MySQL service, and its dependent resources, on one of your nodes."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/controller/section_mysql.xml:233(title)
|
||||
#: ./doc/high-availability-guide/controller/section_mysql.xml:238(title)
|
||||
msgid "Configure OpenStack services for highly available MySQL"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/controller/section_mysql.xml:235(simpara)
|
||||
msgid "Your OpenStack services must now point their MySQL configuration to the highly available, virtual cluster IP address — rather than a MySQL server’s physical IP address as you normally would."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/controller/section_mysql.xml:238(simpara)
|
||||
msgid "For OpenStack Image, for example, if your MySQL service IP address is 192.168.42.101 as in the configuration explained here, you would use the following line in your OpenStack Image registry configuration file (<literal>glance-registry.conf</literal>):"
|
||||
#: ./doc/high-availability-guide/controller/section_mysql.xml:240(simpara)
|
||||
msgid "Your OpenStack services must now point their MySQL configuration to the highly available, virtual cluster IP addressrather than a MySQL server"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/controller/section_mysql.xml:243(simpara)
|
||||
msgid "For OpenStack Image, for example, if your MySQL service IP address is 192.168.42.101 as in the configuration explained here, you would use the following line in your OpenStack Image registry configuration file (<literal>glance-registry.conf</literal>):"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/controller/section_mysql.xml:248(simpara)
|
||||
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 ""
|
||||
|
||||
@ -1166,7 +1166,7 @@ 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 & 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."
|
||||
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 & Resources Agents, we don’t check if the service is actually running). That’s why all OpenStack API should be monitored by another tool, for example 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)
|
||||
|
||||
@ -4,9 +4,9 @@
|
||||
msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: OpenStack Manuals\n"
|
||||
"POT-Creation-Date: 2014-07-01 20:21+0000\n"
|
||||
"PO-Revision-Date: 2014-07-01 08:21+0000\n"
|
||||
"Last-Translator: Tomoyuki KATO <tomo@dream.daynight.jp>\n"
|
||||
"POT-Creation-Date: 2014-07-08 03:10+0000\n"
|
||||
"PO-Revision-Date: 2014-07-07 15:34+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"
|
||||
@ -14,45 +14,45 @@ msgstr ""
|
||||
"Language: ja\n"
|
||||
"Plural-Forms: nplurals=1; plural=0;\n"
|
||||
|
||||
#: ./doc/high-availability-guide/ch_controller.xml6(title)
|
||||
#: ./doc/high-availability-guide/ch_controller.xml7(title)
|
||||
msgid "Cloud controller cluster stack"
|
||||
msgstr "クラウドコントローラーのクラスタースタック"
|
||||
|
||||
#: ./doc/high-availability-guide/ch_controller.xml8(simpara)
|
||||
#: ./doc/high-availability-guide/ch_controller.xml9(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)
|
||||
#: ./doc/high-availability-guide/ch_ha_aa_network.xml7(title)
|
||||
msgid "OpenStack network nodes"
|
||||
msgstr "OpenStack ネットワークノード"
|
||||
|
||||
#: ./doc/high-availability-guide/ch_ha_aa_network.xml8(simpara)
|
||||
#: ./doc/high-availability-guide/ch_ha_aa_network.xml9(simpara)
|
||||
msgid "OpenStack network nodes contain:"
|
||||
msgstr "OpenStack ネットワークノードは次のものを含みます。"
|
||||
|
||||
#: ./doc/high-availability-guide/ch_ha_aa_network.xml11(simpara)
|
||||
#: ./doc/high-availability-guide/ch_ha_aa_network.xml12(simpara)
|
||||
msgid "neutron DHCP agent"
|
||||
msgstr "Neutron DHCP エージェント"
|
||||
|
||||
#: ./doc/high-availability-guide/ch_ha_aa_network.xml16(simpara)
|
||||
#: ./doc/high-availability-guide/ch_ha_aa_network.xml17(simpara)
|
||||
msgid "neutron L2 agent"
|
||||
msgstr "neutron L2 エージェント"
|
||||
|
||||
#: ./doc/high-availability-guide/ch_ha_aa_network.xml21(simpara)
|
||||
#: ./doc/high-availability-guide/ch_ha_aa_network.xml22(simpara)
|
||||
msgid "Neutron L3 agent"
|
||||
msgstr "neutron L3 エージェント"
|
||||
|
||||
#: ./doc/high-availability-guide/ch_ha_aa_network.xml26(simpara)
|
||||
#: ./doc/high-availability-guide/ch_ha_aa_network.xml27(simpara)
|
||||
msgid "neutron metadata agent"
|
||||
msgstr "neutron メタデータエージェント"
|
||||
|
||||
#: ./doc/high-availability-guide/ch_ha_aa_network.xml31(simpara)
|
||||
#: ./doc/high-availability-guide/ch_ha_aa_network.xml32(simpara)
|
||||
msgid "neutron lbaas agent"
|
||||
msgstr "neutron LBaaS エージェント"
|
||||
|
||||
#: ./doc/high-availability-guide/ch_ha_aa_network.xml37(simpara)
|
||||
#: ./doc/high-availability-guide/ch_ha_aa_network.xml38(simpara)
|
||||
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 "
|
||||
@ -61,11 +61,11 @@ msgid ""
|
||||
"highly available."
|
||||
msgstr "neutron L2 エージェントは高可用性にする必要がありません。各データ転送ノードにインストールされる必要があります。また、Open vSwitch または Linux Bridge として仮想ネットワークドライバーを制御します。1 つの L2 エージェントをノードごとに実行し、その仮想インターフェースを制御します。これが分散できず、高可用性にできない理由です。"
|
||||
|
||||
#: ./doc/high-availability-guide/ch_pacemaker.xml6(title)
|
||||
#: ./doc/high-availability-guide/ch_pacemaker.xml7(title)
|
||||
msgid "The Pacemaker cluster stack"
|
||||
msgstr "Pacemaker クラスタースタック"
|
||||
|
||||
#: ./doc/high-availability-guide/ch_pacemaker.xml8(simpara)
|
||||
#: ./doc/high-availability-guide/ch_pacemaker.xml9(simpara)
|
||||
msgid ""
|
||||
"OpenStack infrastructure high availability relies on the <link "
|
||||
"href=\"http://www.clusterlabs.org\">Pacemaker</link> cluster stack, the "
|
||||
@ -74,7 +74,7 @@ msgid ""
|
||||
"specific to OpenStack."
|
||||
msgstr "OpenStack インフラの高可用性は <link href=\"http://www.clusterlabs.org\">Pacemaker</link> クラスター・スタックに依存しています。これは Linux プラットフォームにおける最先端の高可用性および負荷分散のスタックです。Pacemaker はストレージとアプリケーションに依存しません。また、OpenStack に固有ではありません。"
|
||||
|
||||
#: ./doc/high-availability-guide/ch_pacemaker.xml13(simpara)
|
||||
#: ./doc/high-availability-guide/ch_pacemaker.xml14(simpara)
|
||||
msgid ""
|
||||
"Pacemaker relies on the <link "
|
||||
"href=\"http://www.corosync.org\">Corosync</link> messaging layer for "
|
||||
@ -83,7 +83,7 @@ msgid ""
|
||||
"messaging, quorum, and cluster membership to Pacemaker."
|
||||
msgstr "Pacemaker は信頼できるクラスター通信として <link href=\"http://www.corosync.org\">Corosync</link> メッセージング層に依存しています。Corosync は Totem 単一リング順序制御・メンバー管理プロトコルを実装しています。また、UDP および InfiniBand によるメッセージング、クォーラムおよびクラスターメンバー管理を Pacemaker に提供します。"
|
||||
|
||||
#: ./doc/high-availability-guide/ch_pacemaker.xml18(simpara)
|
||||
#: ./doc/high-availability-guide/ch_pacemaker.xml19(simpara)
|
||||
msgid ""
|
||||
"Pacemaker interacts with applications through <emphasis>resource "
|
||||
"agents</emphasis> (RAs), of which it supports over 70 natively. Pacemaker "
|
||||
@ -94,51 +94,51 @@ 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/ch_ha_aa_rabbitmq.xml6(title)
|
||||
#: ./doc/high-availability-guide/ch_ha_aa_rabbitmq.xml7(title)
|
||||
msgid "RabbitMQ"
|
||||
msgstr "RabbitMQ"
|
||||
|
||||
#: ./doc/high-availability-guide/ch_ha_aa_rabbitmq.xml8(simpara)
|
||||
#: ./doc/high-availability-guide/ch_ha_aa_rabbitmq.xml9(simpara)
|
||||
msgid ""
|
||||
"RabbitMQ is the default AMQP server used by many OpenStack services. Making "
|
||||
"the RabbitMQ service highly available involves the following steps:"
|
||||
msgstr "RabbitMQ が多くの OpenStack サービスにより使用される標準の AMQP サーバーです。RabbitMQ サービスを高可用性にすることは、以下の手順が関連します。"
|
||||
|
||||
#: ./doc/high-availability-guide/ch_ha_aa_rabbitmq.xml12(simpara)
|
||||
#: ./doc/high-availability-guide/ch_ha_aa_rabbitmq.xml13(simpara)
|
||||
#: ./doc/high-availability-guide/ha_aa_rabbitmq/section_install_rabbitmq.xml6(title)
|
||||
msgid "Install RabbitMQ"
|
||||
msgstr "RabbitMQ のインストール"
|
||||
|
||||
#: ./doc/high-availability-guide/ch_ha_aa_rabbitmq.xml17(simpara)
|
||||
#: ./doc/high-availability-guide/ch_ha_aa_rabbitmq.xml18(simpara)
|
||||
msgid "Configure RabbitMQ for HA queues"
|
||||
msgstr "高可用性 キュー用の RabbitMQ の設定"
|
||||
|
||||
#: ./doc/high-availability-guide/ch_ha_aa_rabbitmq.xml22(simpara)
|
||||
#: ./doc/high-availability-guide/ch_ha_aa_rabbitmq.xml23(simpara)
|
||||
msgid "Configure OpenStack services to use Rabbit HA queues"
|
||||
msgstr "RabbitMQ HA キューを使用するための OpenStack サービスの設定"
|
||||
|
||||
#: ./doc/high-availability-guide/ch_intro.xml6(title)
|
||||
#: ./doc/high-availability-guide/ch_intro.xml7(title)
|
||||
msgid "Introduction to OpenStack High Availability"
|
||||
msgstr "OpenStack 高可用性の概要"
|
||||
|
||||
#: ./doc/high-availability-guide/ch_intro.xml8(simpara)
|
||||
#: ./doc/high-availability-guide/ch_intro.xml9(simpara)
|
||||
msgid "High Availability systems seek to minimize two things:"
|
||||
msgstr "高可用性システムは以下の二つを最小化しようとします。"
|
||||
|
||||
#: ./doc/high-availability-guide/ch_intro.xml11(simpara)
|
||||
#: ./doc/high-availability-guide/ch_intro.xml12(simpara)
|
||||
msgid ""
|
||||
"<emphasis role=\"strong\">System downtime</emphasis> — occurs when a "
|
||||
"<emphasis>user-facing</emphasis> service is unavailable beyond a specified "
|
||||
"maximum amount of time, and"
|
||||
msgstr "<emphasis role=\"strong\">システム停止時間</emphasis> — 指定された最大時間を超える<emphasis>ユーザーが直面する</emphasis>サービスの利用不可能な時間の発生。"
|
||||
|
||||
#: ./doc/high-availability-guide/ch_intro.xml15(simpara)
|
||||
#: ./doc/high-availability-guide/ch_intro.xml16(simpara)
|
||||
msgid ""
|
||||
"<emphasis role=\"strong\">Data loss</emphasis> — accidental deletion or "
|
||||
"destruction of data."
|
||||
msgstr "<emphasis role=\"strong\">データ損失</emphasis> — 不慮の削除、またはデータの破損。"
|
||||
|
||||
#: ./doc/high-availability-guide/ch_intro.xml19(simpara)
|
||||
#: ./doc/high-availability-guide/ch_intro.xml20(simpara)
|
||||
msgid ""
|
||||
"Most high availability systems guarantee protection against system downtime "
|
||||
"and data loss only in the event of a single failure. However, they are also "
|
||||
@ -146,7 +146,7 @@ msgid ""
|
||||
"deteriorates into a series of consequential failures."
|
||||
msgstr "多くの高可用性システムは単一障害事象のみで、システム停止やデータ損失に対する保護を保証します。しかしながら、単一障害が一連の障害を悪化させていく、段階的な障害に対しても保護することが期待されます。"
|
||||
|
||||
#: ./doc/high-availability-guide/ch_intro.xml20(simpara)
|
||||
#: ./doc/high-availability-guide/ch_intro.xml21(simpara)
|
||||
msgid ""
|
||||
"A crucial aspect of high availability is the elimination of single points of"
|
||||
" failure (SPOFs). A SPOF is an individual piece of equipment or software "
|
||||
@ -154,30 +154,30 @@ msgid ""
|
||||
"eliminate SPOFs, check that mechanisms exist for redundancy of:"
|
||||
msgstr "高可用性の重要な側面は単一障害点 (SPOF) を減らすことです。SPOF は、障害が発生した場合にシステム停止やデータ損失を引き起こす、設備やソフトウェアの個々の部品です。SPOF を削減するために、以下の冗長性に対するメカニズムを確認します。"
|
||||
|
||||
#: ./doc/high-availability-guide/ch_intro.xml23(simpara)
|
||||
#: ./doc/high-availability-guide/ch_intro.xml24(simpara)
|
||||
msgid "Network components, such as switches and routers"
|
||||
msgstr "スイッチやルーターなどのネットワークの構成要素"
|
||||
|
||||
#: ./doc/high-availability-guide/ch_intro.xml28(simpara)
|
||||
#: ./doc/high-availability-guide/ch_intro.xml29(simpara)
|
||||
msgid "Applications and automatic service migration"
|
||||
msgstr "アプリケーションおよび自動的なサービスのマイグレーション"
|
||||
|
||||
#: ./doc/high-availability-guide/ch_intro.xml33(simpara)
|
||||
#: ./doc/high-availability-guide/ch_intro.xml34(simpara)
|
||||
msgid "Storage components"
|
||||
msgstr "ストレージ構成要素"
|
||||
|
||||
#: ./doc/high-availability-guide/ch_intro.xml38(simpara)
|
||||
#: ./doc/high-availability-guide/ch_intro.xml39(simpara)
|
||||
msgid "Facility services such as power, air conditioning, and fire protection"
|
||||
msgstr "電源、空調、防火などに関する設備"
|
||||
|
||||
#: ./doc/high-availability-guide/ch_intro.xml43(simpara)
|
||||
#: ./doc/high-availability-guide/ch_intro.xml44(simpara)
|
||||
msgid ""
|
||||
"Most high availability systems will fail in the event of multiple "
|
||||
"independent (non-consequential) failures. In this case, most systems will "
|
||||
"protect data over maintaining availability."
|
||||
msgstr "多くの高可用性システムは複数の独立した (不連続な) 障害が発生すると停止します。この場合、多くのシステムは可用性の維持よりデータの保護を優先します。"
|
||||
|
||||
#: ./doc/high-availability-guide/ch_intro.xml44(simpara)
|
||||
#: ./doc/high-availability-guide/ch_intro.xml45(simpara)
|
||||
msgid ""
|
||||
"High-availability systems typically achieve uptime of 99.99% or more, which "
|
||||
"roughly equates to less than an hour of cumulative downtime per year. In "
|
||||
@ -185,7 +185,7 @@ msgid ""
|
||||
"after a failure to about one to two minutes, sometimes significantly less."
|
||||
msgstr "高可用性システムは一般的に 99.99% かそれ以上の稼働時間を達成します。これは、年間の累積停止時間として 1 時間以内ほどです。これを達成するために、高可用性システムは、障害発生後の復旧時間を1、2分に、ときどきさらに短時間にする必要があります。"
|
||||
|
||||
#: ./doc/high-availability-guide/ch_intro.xml45(simpara)
|
||||
#: ./doc/high-availability-guide/ch_intro.xml46(simpara)
|
||||
msgid ""
|
||||
"OpenStack currently meets such availability requirements for its own "
|
||||
"infrastructure services, meaning that an uptime of 99.99% is feasible for "
|
||||
@ -194,17 +194,17 @@ msgid ""
|
||||
"availability for individual guest instances."
|
||||
msgstr "OpenStack は自身のインフラストラクチャーサービスに対して、現在そのような要件を満たしています。99.99% の稼働時間が OpenStack インフラストラクチャーに対して完全に実現するという意味です。しかしながら、OpenStack は個々のゲストインスタンスに対して 99.99% の可用性を保証<emphasis>していません</emphasis>。"
|
||||
|
||||
#: ./doc/high-availability-guide/ch_intro.xml46(simpara)
|
||||
#: ./doc/high-availability-guide/ch_intro.xml47(simpara)
|
||||
msgid ""
|
||||
"Preventing single points of failure can depend on whether or not a service "
|
||||
"is stateless."
|
||||
msgstr "単一障害点を無くすことは、サービスがステートレスであるかどうかに依存する可能性があります。"
|
||||
|
||||
#: ./doc/high-availability-guide/ch_intro.xml49(title)
|
||||
#: ./doc/high-availability-guide/ch_intro.xml50(title)
|
||||
msgid "Stateless vs. Stateful services"
|
||||
msgstr "ステートレスサービスとステートフルサービス"
|
||||
|
||||
#: ./doc/high-availability-guide/ch_intro.xml51(simpara)
|
||||
#: ./doc/high-availability-guide/ch_intro.xml52(simpara)
|
||||
msgid ""
|
||||
"A stateless service is one that provides a response after your request, and "
|
||||
"then requires no further attention. To make a stateless service highly "
|
||||
@ -213,7 +213,7 @@ msgid ""
|
||||
"glance-api, keystone-api, neutron-api and nova-scheduler."
|
||||
msgstr "ステートレスなサービスは、リクエストの後に応答を返すもので、その後の注意をする必要がないものです。ステートレスなサービスを高可用性にするには、冗長なインスタンスとそれらの負荷分散を提供する必要があります。ステートレスな OpenStack サービスは nova-api、nova-conductor、glance-api、keystone-api、neutron-api、nova-scheduler があります。"
|
||||
|
||||
#: ./doc/high-availability-guide/ch_intro.xml52(simpara)
|
||||
#: ./doc/high-availability-guide/ch_intro.xml53(simpara)
|
||||
msgid ""
|
||||
"A stateful service is one where subsequent requests to the service depend on"
|
||||
" the results of the first request. Stateful services are more difficult to "
|
||||
@ -224,17 +224,17 @@ msgid ""
|
||||
"are stateful include the OpenStack database and message queue."
|
||||
msgstr "ステートフルサービスは、最初のサービスリクエストの結果に基づいて、後続のものがサービスにリクエストします。ステートフルサービスは管理することがより難しいです。その理由は、単一のアクションが複数のリクエストに関係するため、単に追加インスタンスと負荷分散を提供しても問題が解決しないからです。たとえば、Horizon ユーザーインターフェースが新しいページに移動するたびにリセットすると、かなり使い勝手が悪くなります。ステートフルな OpenStack サービスに OpenStack データベースとメッセージキューがあります。"
|
||||
|
||||
#: ./doc/high-availability-guide/ch_intro.xml53(simpara)
|
||||
#: ./doc/high-availability-guide/ch_intro.xml54(simpara)
|
||||
msgid ""
|
||||
"Making stateful services highly available can depend on whether you choose "
|
||||
"an active/passive or active/active configuration."
|
||||
msgstr "ステートフルサービスの高可用性は、アクティブ / パッシブとアクティブ / アクティブのどちらの設定を選択するかに依存する可能性があります。"
|
||||
|
||||
#: ./doc/high-availability-guide/ch_intro.xml57(title)
|
||||
#: ./doc/high-availability-guide/ch_intro.xml58(title)
|
||||
msgid "Active/Passive"
|
||||
msgstr "アクティブ/パッシブ"
|
||||
|
||||
#: ./doc/high-availability-guide/ch_intro.xml59(simpara)
|
||||
#: ./doc/high-availability-guide/ch_intro.xml60(simpara)
|
||||
msgid ""
|
||||
"In an active/passive configuration, systems are set up to bring additional "
|
||||
"resources online to replace those that have failed. For example, OpenStack "
|
||||
@ -243,7 +243,7 @@ msgid ""
|
||||
"fails."
|
||||
msgstr "アクティブ / パッシブの設定の場合、システムは故障したリソースを置き換えるために、オンラインで追加リソースをセットアップします。たとえば、メインのデータベースが故障したときにオンラインになる災害対策データベースを維持する限り、OpenStack はメインのデータベースに書き込みます。"
|
||||
|
||||
#: ./doc/high-availability-guide/ch_intro.xml60(simpara)
|
||||
#: ./doc/high-availability-guide/ch_intro.xml61(simpara)
|
||||
msgid ""
|
||||
"Typically, an active/passive installation for a stateless service would "
|
||||
"maintain a redundant instance that can be brought online when required. "
|
||||
@ -251,7 +251,7 @@ msgid ""
|
||||
"such as HAProxy."
|
||||
msgstr "一般的にステートレスサービスをアクティブ / パッシブにインストールすると、必要に応じてオンラインにできる冗長なインスタンスを維持することになります。リクエストは HAProxy のような仮想 IP アドレスとロードバランサーを使用して負荷分散されます。"
|
||||
|
||||
#: ./doc/high-availability-guide/ch_intro.xml61(simpara)
|
||||
#: ./doc/high-availability-guide/ch_intro.xml62(simpara)
|
||||
msgid ""
|
||||
"A typical active/passive installation for a stateful service maintains a "
|
||||
"replacement resource that can be brought online when required. A separate "
|
||||
@ -259,11 +259,11 @@ msgid ""
|
||||
"bringing the backup online as necessary."
|
||||
msgstr "一般的にステートレスサービスをアクティブ / パッシブにインストールすると、必要に応じてオンラインにできる置換リソースを維持します。 独立したアプリケーション (Pacemaker や Corosync など) がこれらのサービスを監視し、必要に応じてバックアップ側をオンラインにします。"
|
||||
|
||||
#: ./doc/high-availability-guide/ch_intro.xml65(title)
|
||||
#: ./doc/high-availability-guide/ch_intro.xml66(title)
|
||||
msgid "Active/Active"
|
||||
msgstr "アクティブ/アクティブ"
|
||||
|
||||
#: ./doc/high-availability-guide/ch_intro.xml67(simpara)
|
||||
#: ./doc/high-availability-guide/ch_intro.xml68(simpara)
|
||||
msgid ""
|
||||
"In an active/active configuration, systems also use a backup but will manage"
|
||||
" both the main and redundant systems concurrently. This way, if there is a "
|
||||
@ -272,14 +272,14 @@ msgid ""
|
||||
" online."
|
||||
msgstr "アクティブ / アクティブの設定の場合、システムはバックアップ側も使用しますが、メインと冗長システムを同時に管理します。このように、ユーザーが気が付かない障害が発生した場合、バックアップシステムはすでにオンラインであり、メインシステムが復旧され、オンラインになるまでの間は負荷が高くなります。"
|
||||
|
||||
#: ./doc/high-availability-guide/ch_intro.xml68(simpara)
|
||||
#: ./doc/high-availability-guide/ch_intro.xml69(simpara)
|
||||
msgid ""
|
||||
"Typically, an active/active installation for a stateless service would "
|
||||
"maintain a redundant instance, and requests are load balanced using a "
|
||||
"virtual IP address and a load balancer such as HAProxy."
|
||||
msgstr "一般的にステートレスサービスをアクティブ / アクティブにインストールすると、冗長なインスタンスを維持することになります。リクエストは HAProxy のような仮想 IP アドレスとロードバランサーを使用して負荷分散されます。"
|
||||
|
||||
#: ./doc/high-availability-guide/ch_intro.xml69(simpara)
|
||||
#: ./doc/high-availability-guide/ch_intro.xml70(simpara)
|
||||
msgid ""
|
||||
"A typical active/active installation for a stateful service would include "
|
||||
"redundant services with all instances having an identical state. For "
|
||||
@ -289,7 +289,7 @@ msgid ""
|
||||
"that operational systems always handle the request."
|
||||
msgstr "一般的にステートレスサービスをアクティブ / アクティブにインストールすることは、すべてのインスタンスが同じ状態を持つ冗長なサービスになることを含みます。たとえば、あるインスタンスのデータベースの更新は、他のすべてのインスタンスも更新されます。このように、あるインスタンスへのリクエストは、他へのリクエストと同じです。ロードバランサーがこれらのシステムのトラフィックを管理し、利用可能なシステムが常にリクエストを確実に処理します。"
|
||||
|
||||
#: ./doc/high-availability-guide/ch_intro.xml70(simpara)
|
||||
#: ./doc/high-availability-guide/ch_intro.xml71(simpara)
|
||||
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 "
|
||||
@ -385,28 +385,28 @@ msgstr "2012-05-24"
|
||||
msgid "Begin trunk designation."
|
||||
msgstr "trunk 指定を始めました。"
|
||||
|
||||
#: ./doc/high-availability-guide/ch_network.xml6(title)
|
||||
#: ./doc/high-availability-guide/ch_network.xml7(title)
|
||||
msgid "Network controller cluster stack"
|
||||
msgstr "ネットワークコントローラーのクラスタースタック"
|
||||
|
||||
#: ./doc/high-availability-guide/ch_network.xml8(simpara)
|
||||
#: ./doc/high-availability-guide/ch_network.xml9(simpara)
|
||||
msgid ""
|
||||
"The network controller sits on the management and data network, and needs to"
|
||||
" be connected to the Internet if a VM needs access to it."
|
||||
msgstr "ネットワークコントローラーは、管理ネットワークとデータネットワークにあり、仮想マシンがインターネットにアクセスする必要がある場合にインターネットに接続する必要があります。"
|
||||
|
||||
#: ./doc/high-availability-guide/ch_network.xml10(simpara)
|
||||
#: ./doc/high-availability-guide/ch_network.xml11(simpara)
|
||||
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 "Networking スケジューラーが 1 つのノードに認識するよう、両方のノードが同じホスト名を持つべきです。たとえば、単一の L3 ノードに接続された仮想ルーターです。"
|
||||
|
||||
#: ./doc/high-availability-guide/ch_ha_aa_haproxy.xml6(title)
|
||||
#: ./doc/high-availability-guide/ch_ha_aa_haproxy.xml7(title)
|
||||
msgid "HAproxy nodes"
|
||||
msgstr "HAproxy ノード"
|
||||
|
||||
#: ./doc/high-availability-guide/ch_ha_aa_haproxy.xml8(simpara)
|
||||
#: ./doc/high-availability-guide/ch_ha_aa_haproxy.xml9(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 "
|
||||
@ -415,7 +415,7 @@ msgid ""
|
||||
"connections is clearly realistic with today’s hardware."
|
||||
msgstr "HAProxy は高可用性、負荷分散、TCP と HTTP ベースのアプリケーションに対するプロキシを提供する非常に高速かつ信頼性のあるソリューションです。とくに永続性とレイヤー 7 処理を必要とする、非常に負荷の高いウェブサイトに適しています。数千の接続をサポートすることは、今日のハードウェアではかなり現実的です。"
|
||||
|
||||
#: ./doc/high-availability-guide/ch_ha_aa_haproxy.xml12(simpara)
|
||||
#: ./doc/high-availability-guide/ch_ha_aa_haproxy.xml13(simpara)
|
||||
msgid ""
|
||||
"For installing HAproxy on your nodes, you should consider its <link "
|
||||
"href=\"http://haproxy.1wt.eu/#docs\">official documentation</link>. Also, "
|
||||
@ -423,53 +423,53 @@ msgid ""
|
||||
"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)
|
||||
#: ./doc/high-availability-guide/ch_ha_aa_haproxy.xml16(simpara)
|
||||
msgid "Here is an example for HAproxy configuration file:"
|
||||
msgstr "これは HAproxy 設定ファイルの例です。"
|
||||
|
||||
#: ./doc/high-availability-guide/ch_ha_aa_haproxy.xml155(simpara)
|
||||
#: ./doc/high-availability-guide/ch_ha_aa_haproxy.xml156(simpara)
|
||||
msgid "After each change of this file, you should restart HAproxy."
|
||||
msgstr "このファイルをそれぞれ変更した後、HAproxy を再起動しなければいけません。"
|
||||
|
||||
#: ./doc/high-availability-guide/ch_ha_aa_controllers.xml6(title)
|
||||
#: ./doc/high-availability-guide/ch_ha_aa_controllers.xml7(title)
|
||||
msgid "OpenStack controller nodes"
|
||||
msgstr "OpenStack コントローラーノード"
|
||||
|
||||
#: ./doc/high-availability-guide/ch_ha_aa_controllers.xml8(simpara)
|
||||
#: ./doc/high-availability-guide/ch_ha_aa_controllers.xml9(simpara)
|
||||
msgid "OpenStack controller nodes contain:"
|
||||
msgstr "OpenStack コントローラーノードは次のものを含みます。"
|
||||
|
||||
#: ./doc/high-availability-guide/ch_ha_aa_controllers.xml11(simpara)
|
||||
#: ./doc/high-availability-guide/ch_ha_aa_controllers.xml12(simpara)
|
||||
msgid "All OpenStack API services"
|
||||
msgstr "すべての OpenStack API サービス"
|
||||
|
||||
#: ./doc/high-availability-guide/ch_ha_aa_controllers.xml16(simpara)
|
||||
#: ./doc/high-availability-guide/ch_ha_aa_controllers.xml17(simpara)
|
||||
msgid "All OpenStack schedulers"
|
||||
msgstr "すべての OpenStack スケジューラー"
|
||||
|
||||
#: ./doc/high-availability-guide/ch_ha_aa_controllers.xml21(simpara)
|
||||
#: ./doc/high-availability-guide/ch_ha_aa_controllers.xml22(simpara)
|
||||
msgid "Memcached service"
|
||||
msgstr "Memcached サービス"
|
||||
|
||||
#: ./doc/high-availability-guide/part_active_passive.xml6(title)
|
||||
#: ./doc/high-availability-guide/part_active_passive.xml7(title)
|
||||
msgid "HA using active/passive"
|
||||
msgstr "アクティブ/パッシブを使用した HA"
|
||||
|
||||
#: ./doc/high-availability-guide/ch_api.xml6(title)
|
||||
#: ./doc/high-availability-guide/ch_api.xml7(title)
|
||||
msgid "API node cluster stack"
|
||||
msgstr "API ノードクラスタースタック"
|
||||
|
||||
#: ./doc/high-availability-guide/ch_api.xml8(simpara)
|
||||
#: ./doc/high-availability-guide/ch_api.xml9(simpara)
|
||||
msgid ""
|
||||
"The API node exposes OpenStack API endpoints onto external network "
|
||||
"(Internet). It must talk to the cloud controller on the management network."
|
||||
msgstr "API ノードは外部ネットワーク (インターネット) にある OpenStack API エンドポイントにさらされています。管理ネットワークでクラウドコントローラーと通信する必要があります。"
|
||||
|
||||
#: ./doc/high-availability-guide/ch_ha_aa_db.xml6(title)
|
||||
#: ./doc/high-availability-guide/ch_ha_aa_db.xml7(title)
|
||||
msgid "Database"
|
||||
msgstr "データベース"
|
||||
|
||||
#: ./doc/high-availability-guide/ch_ha_aa_db.xml8(simpara)
|
||||
#: ./doc/high-availability-guide/ch_ha_aa_db.xml9(simpara)
|
||||
msgid ""
|
||||
"The first step is installing the database that sits at the heart of the "
|
||||
"cluster. When we talk about High Availability, we talk about several "
|
||||
@ -478,14 +478,14 @@ msgid ""
|
||||
"multi-master replication."
|
||||
msgstr "最初の手順は、クラスターの中心にあるデータベースをインストールすることです。私たちが高可用性について議論するとき、複数の (冗長性のための) データベースとそれらを同期させる方法について議論しています。この場合、MySQL データベースを、マルチマスターレプリケーション同期のために Galera と一緒に使用する必要があります。"
|
||||
|
||||
#: ./doc/high-availability-guide/ch_ha_aa_db.xml12(simpara)
|
||||
#: ./doc/high-availability-guide/ch_ha_aa_db.xml13(simpara)
|
||||
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 "データベースの選択は決められたものではありません。必ずしも MySQL を使用する必要がありません。しかしながら、OpenStack のインストール環境ではかなり一般的な選択肢であるため、ここでは MySQL を取り扱います。"
|
||||
|
||||
#: ./doc/high-availability-guide/part_active_active.xml6(title)
|
||||
#: ./doc/high-availability-guide/part_active_active.xml7(title)
|
||||
msgid "HA using active/active"
|
||||
msgstr "アクティブ/アクティブを使用した HA"
|
||||
|
||||
@ -740,8 +740,8 @@ msgstr "Block Storage API リソース用の 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/controller/section_rabbitmq.xml190(simpara)
|
||||
#: ./doc/high-availability-guide/controller/section_mysql.xml202(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)
|
||||
@ -1222,74 +1222,74 @@ msgid ""
|
||||
" 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)
|
||||
#: ./doc/high-availability-guide/controller/section_rabbitmq.xml11(title)
|
||||
msgid "Highly available RabbitMQ"
|
||||
msgstr "高可用性 RabbitMQ"
|
||||
|
||||
#: ./doc/high-availability-guide/controller/section_rabbitmq.xml8(simpara)
|
||||
#: ./doc/high-availability-guide/controller/section_rabbitmq.xml13(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)
|
||||
#: ./doc/high-availability-guide/controller/section_rabbitmq.xml17(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/controller/section_rabbitmq.xml22(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)
|
||||
#: ./doc/high-availability-guide/controller/section_rabbitmq.xml28(simpara)
|
||||
#: ./doc/high-availability-guide/controller/section_mysql.xml28(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)
|
||||
#: ./doc/high-availability-guide/controller/section_rabbitmq.xml34(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/controller/section_rabbitmq.xml39(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)
|
||||
#: ./doc/high-availability-guide/controller/section_rabbitmq.xml46(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 のアクティブ・アクティブのキューのミラーが成熟すると、近い将来に変更される可能性もあります。"
|
||||
"queues</link>, happens to be the one preferred by the RabbitMQ "
|
||||
"developershowever 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.xml53(title)
|
||||
#: ./doc/high-availability-guide/controller/section_mysql.xml50(title)
|
||||
#: ./doc/high-availability-guide/controller/section_rabbitmq.xml58(title)
|
||||
#: ./doc/high-availability-guide/controller/section_mysql.xml55(title)
|
||||
msgid "Configure DRBD"
|
||||
msgstr "DRBD の設定"
|
||||
|
||||
#: ./doc/high-availability-guide/controller/section_rabbitmq.xml55(simpara)
|
||||
#: ./doc/high-availability-guide/controller/section_rabbitmq.xml60(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)
|
||||
#: ./doc/high-availability-guide/controller/section_rabbitmq.xml65(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)
|
||||
#: ./doc/high-availability-guide/controller/section_rabbitmq.xml81(simpara)
|
||||
msgid ""
|
||||
"This resource uses an underlying local disk (in DRBD terminology, a "
|
||||
"<emphasis>backing device</emphasis>) named "
|
||||
@ -1304,21 +1304,21 @@ msgid ""
|
||||
"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)
|
||||
#: ./doc/high-availability-guide/controller/section_rabbitmq.xml90(simpara)
|
||||
#: ./doc/high-availability-guide/controller/section_mysql.xml87(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)
|
||||
#: ./doc/high-availability-guide/controller/section_rabbitmq.xml98(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)
|
||||
#: ./doc/high-availability-guide/controller/section_rabbitmq.xml104(para)
|
||||
msgid ""
|
||||
"Creates the <literal>/dev/drbd1</literal> device node, "
|
||||
"<emphasis>attaches</emphasis> the DRBD device to its backing store, and "
|
||||
@ -1326,8 +1326,8 @@ msgid ""
|
||||
"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)
|
||||
#: ./doc/high-availability-guide/controller/section_rabbitmq.xml111(para)
|
||||
#: ./doc/high-availability-guide/controller/section_mysql.xml108(para)
|
||||
msgid ""
|
||||
"Kicks off the initial device synchronization, and puts the device into the "
|
||||
"<literal>primary</literal> (readable and writable) role. See <link "
|
||||
@ -1338,11 +1338,11 @@ msgid ""
|
||||
"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)
|
||||
#: ./doc/high-availability-guide/controller/section_rabbitmq.xml125(title)
|
||||
msgid "Create a file system"
|
||||
msgstr "ファイルシステムの作成"
|
||||
|
||||
#: ./doc/high-availability-guide/controller/section_rabbitmq.xml122(simpara)
|
||||
#: ./doc/high-availability-guide/controller/section_rabbitmq.xml127(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"
|
||||
@ -1350,25 +1350,25 @@ msgid ""
|
||||
"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)
|
||||
#: ./doc/high-availability-guide/controller/section_rabbitmq.xml132(simpara)
|
||||
#: ./doc/high-availability-guide/controller/section_mysql.xml129(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)
|
||||
#: ./doc/high-availability-guide/controller/section_rabbitmq.xml136(simpara)
|
||||
#: ./doc/high-availability-guide/controller/section_mysql.xml133(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)
|
||||
#: ./doc/high-availability-guide/controller/section_rabbitmq.xml143(title)
|
||||
msgid "Prepare RabbitMQ for Pacemaker high availability"
|
||||
msgstr "Pacemaker 高可用性のための RabbitMQ の準備"
|
||||
|
||||
#: ./doc/high-availability-guide/controller/section_rabbitmq.xml140(simpara)
|
||||
#: ./doc/high-availability-guide/controller/section_rabbitmq.xml145(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 "
|
||||
@ -1378,45 +1378,45 @@ msgid ""
|
||||
"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)
|
||||
#: ./doc/high-availability-guide/controller/section_rabbitmq.xml158(title)
|
||||
msgid "Add RabbitMQ resources to Pacemaker"
|
||||
msgstr "RabbitMQ リソースの Pacemaker への追加"
|
||||
|
||||
#: ./doc/high-availability-guide/controller/section_rabbitmq.xml155(simpara)
|
||||
#: ./doc/high-availability-guide/controller/section_rabbitmq.xml160(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)
|
||||
#: ./doc/high-availability-guide/controller/section_rabbitmq.xml193(simpara)
|
||||
msgid ""
|
||||
"<literal>p_ip_rabbitmq</literal>, a virtual IP address for use by RabbitMQ "
|
||||
"(192.168.42.100),"
|
||||
msgstr "<literal>p_ip_rabbitmq</literal>, RabbitMQ により使用される仮想 IP アドレス (192.168.42.100),"
|
||||
|
||||
#: ./doc/high-availability-guide/controller/section_rabbitmq.xml193(simpara)
|
||||
#: ./doc/high-availability-guide/controller/section_rabbitmq.xml198(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)
|
||||
#: ./doc/high-availability-guide/controller/section_rabbitmq.xml204(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)
|
||||
#: ./doc/high-availability-guide/controller/section_rabbitmq.xml209(simpara)
|
||||
#: ./doc/high-availability-guide/controller/section_mysql.xml221(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)
|
||||
#: ./doc/high-availability-guide/controller/section_rabbitmq.xml215(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 "
|
||||
@ -1425,7 +1425,7 @@ msgid ""
|
||||
"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/controller/section_rabbitmq.xml220(simpara)
|
||||
msgid ""
|
||||
"Once completed, commit your configuration changes by entering "
|
||||
"<literal>commit</literal> from the <literal>crm configure</literal> menu. "
|
||||
@ -1433,18 +1433,17 @@ msgid ""
|
||||
" on one of your nodes."
|
||||
msgstr "完了すると、<literal>crm configure</literal> メニューから <literal>commit</literal> と入力し、設定の変更をコミットします。Pacemaker は RabbitMQ サービスおよび依存するリソースを同じノードに起動します。"
|
||||
|
||||
#: ./doc/high-availability-guide/controller/section_rabbitmq.xml221(title)
|
||||
#: ./doc/high-availability-guide/controller/section_rabbitmq.xml226(title)
|
||||
msgid "Configure OpenStack services for highly available RabbitMQ"
|
||||
msgstr "高可用性 RabbitMQ のための OpenStack サービスの設定"
|
||||
|
||||
#: ./doc/high-availability-guide/controller/section_rabbitmq.xml223(simpara)
|
||||
#: ./doc/high-availability-guide/controller/section_rabbitmq.xml228(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 アドレスを指し示す必要があります。"
|
||||
"highly available, virtual cluster IP addressrather than a RabbitMQ server"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/controller/section_rabbitmq.xml226(simpara)
|
||||
#: ./doc/high-availability-guide/controller/section_rabbitmq.xml231(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 "
|
||||
@ -1452,7 +1451,7 @@ msgid ""
|
||||
">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)
|
||||
#: ./doc/high-availability-guide/controller/section_rabbitmq.xml236(simpara)
|
||||
msgid ""
|
||||
"No other changes are necessary to your OpenStack configuration. If the node "
|
||||
"currently hosting your RabbitMQ experiences a problem necessitating service "
|
||||
@ -1461,35 +1460,35 @@ msgid ""
|
||||
"continue to run normally."
|
||||
msgstr "OpenStack の設定に他の変更は必要ありません。現在 RabbitMQ を稼働しているノードが、サービスのフェイルオーバーを必要とする問題に遭遇した場合、ネットワークの中断と通常どおりの動作継続により、OpenStack のサービスは MySQL の短時間の中断に遭遇するかもしれません。"
|
||||
|
||||
#: ./doc/high-availability-guide/controller/section_mysql.xml6(title)
|
||||
#: ./doc/high-availability-guide/controller/section_mysql.xml11(title)
|
||||
msgid "Highly available MySQL"
|
||||
msgstr "高可用性 MySQL"
|
||||
|
||||
#: ./doc/high-availability-guide/controller/section_mysql.xml8(simpara)
|
||||
#: ./doc/high-availability-guide/controller/section_mysql.xml13(simpara)
|
||||
msgid ""
|
||||
"MySQL is the default database server used by many OpenStack services. Making"
|
||||
" the MySQL service highly available involves"
|
||||
msgstr "MySQL は多くの OpenStack サービスにより使用される標準のデータベースサーバーです。MySQL サービスを高可用性にするには、次のことが関係します。"
|
||||
|
||||
#: ./doc/high-availability-guide/controller/section_mysql.xml12(simpara)
|
||||
#: ./doc/high-availability-guide/controller/section_mysql.xml17(simpara)
|
||||
msgid "Configure a DRBD device for use by MySQL,"
|
||||
msgstr "MySQL により使用するための DRBD デバイスの設定,"
|
||||
|
||||
#: ./doc/high-availability-guide/controller/section_mysql.xml17(simpara)
|
||||
#: ./doc/high-availability-guide/controller/section_mysql.xml22(simpara)
|
||||
msgid "Configure MySQL to use a data directory residing on that DRBD device,"
|
||||
msgstr "MySQL がこの DRBD デバイスにあるデータディレクトリを使用するよう設定します。"
|
||||
|
||||
#: ./doc/high-availability-guide/controller/section_mysql.xml29(simpara)
|
||||
#: ./doc/high-availability-guide/controller/section_mysql.xml34(simpara)
|
||||
msgid "Configure MySQL to listen on that IP address,"
|
||||
msgstr "その IP アドレスをリッスンするよう MySQL を設定します。"
|
||||
|
||||
#: ./doc/high-availability-guide/controller/section_mysql.xml34(simpara)
|
||||
#: ./doc/high-availability-guide/controller/section_mysql.xml39(simpara)
|
||||
msgid ""
|
||||
"managing all resources, including the MySQL daemon itself, with the "
|
||||
"Pacemaker cluster manager."
|
||||
msgstr "Pacemaker クラスターマネージャーを用いて、MySQL デーモン自身を含め、すべてのリソースを管理します。"
|
||||
|
||||
#: ./doc/high-availability-guide/controller/section_mysql.xml41(simpara)
|
||||
#: ./doc/high-availability-guide/controller/section_mysql.xml46(simpara)
|
||||
msgid ""
|
||||
"<link "
|
||||
"href=\"http://codership.com/products/mysql_galera\">MySQL/Galera</link> is "
|
||||
@ -1500,20 +1499,20 @@ 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.xml52(simpara)
|
||||
#: ./doc/high-availability-guide/controller/section_mysql.xml57(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 "Pacemaker ベースの MySQL サーバーは <literal>/var/lib/mysql</literal> ディレクトリをマウントする DRBD リソースが必要です。この例では、DRBD リソースが単に <literal>mysql</literal> という名前になっています。"
|
||||
|
||||
#: ./doc/high-availability-guide/controller/section_mysql.xml57(title)
|
||||
#: ./doc/high-availability-guide/controller/section_mysql.xml62(title)
|
||||
msgid ""
|
||||
"<literal>mysql</literal> DRBD resource configuration "
|
||||
"(<literal>/etc/drbd.d/mysql.res</literal>)"
|
||||
msgstr "<literal>mysql</literal> DRBD リソース設定 (<literal>/etc/drbd.d/mysql.res</literal>)"
|
||||
|
||||
#: ./doc/high-availability-guide/controller/section_mysql.xml73(simpara)
|
||||
#: ./doc/high-availability-guide/controller/section_mysql.xml78(simpara)
|
||||
msgid ""
|
||||
"This resource uses an underlying local disk (in DRBD terminology, a "
|
||||
"<emphasis>backing device</emphasis>) named "
|
||||
@ -1528,13 +1527,13 @@ 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.xml90(para)
|
||||
#: ./doc/high-availability-guide/controller/section_mysql.xml95(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 "DRBD メタデータを初期化し、メタデータの初期セットを <literal>/dev/data/mysql</literal> に書き込みます。両方のノードで完了する必要があります。"
|
||||
|
||||
#: ./doc/high-availability-guide/controller/section_mysql.xml96(para)
|
||||
#: ./doc/high-availability-guide/controller/section_mysql.xml101(para)
|
||||
msgid ""
|
||||
"Creates the <literal>/dev/drbd0</literal> device node, "
|
||||
"<emphasis>attaches</emphasis> the DRBD device to its backing store, and "
|
||||
@ -1542,11 +1541,11 @@ msgid ""
|
||||
"on both nodes."
|
||||
msgstr "<literal>/dev/drbd0</literal> デバイスノードを作成し、DRBD デバイスをそのバックエンドに<emphasis>接続</emphasis>し、DRBD ノードを同期先に<emphasis>接続</emphasis>します。両方のノードで完了する必要があります。"
|
||||
|
||||
#: ./doc/high-availability-guide/controller/section_mysql.xml117(title)
|
||||
#: ./doc/high-availability-guide/controller/section_mysql.xml122(title)
|
||||
msgid "Creating a file system"
|
||||
msgstr "ファイルシステムの作成"
|
||||
|
||||
#: ./doc/high-availability-guide/controller/section_mysql.xml119(simpara)
|
||||
#: ./doc/high-availability-guide/controller/section_mysql.xml124(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"
|
||||
@ -1554,11 +1553,11 @@ msgid ""
|
||||
"recommended filesystem:"
|
||||
msgstr "DRBD リソースが実行中になり、プライマリロールになると (まだ初期デバイス同期が実行中かもしれません)、MySQL データのファイルシステムの作成を進められます。XFS が一般的に推奨されるファイルシステムです。"
|
||||
|
||||
#: ./doc/high-availability-guide/controller/section_mysql.xml135(title)
|
||||
#: ./doc/high-availability-guide/controller/section_mysql.xml140(title)
|
||||
msgid "Prepare MySQL for Pacemaker high availability"
|
||||
msgstr "Pacemaker 高可用性のための MySQL の準備"
|
||||
|
||||
#: ./doc/high-availability-guide/controller/section_mysql.xml137(simpara)
|
||||
#: ./doc/high-availability-guide/controller/section_mysql.xml142(simpara)
|
||||
msgid ""
|
||||
"In order for Pacemaker monitoring to function properly, you must ensure that"
|
||||
" MySQL’s database files reside on the DRBD device. If you already have an "
|
||||
@ -1567,55 +1566,55 @@ msgid ""
|
||||
"created filesystem on the DRBD device."
|
||||
msgstr "Pacemaker の監視を正しく機能させるために、MySQL のデータベースファイルを必ず DRBD デバイスに置く必要があります。既存の MySQL データベースがあれば、最も簡単な方法は、既存の <literal>/var/lib/mysql</literal> ディレクトリの中身を、DRBD デバイスに新しく作成したファイルシステムにそのまま移動することです。"
|
||||
|
||||
#: ./doc/high-availability-guide/controller/section_mysql.xml143(simpara)
|
||||
#: ./doc/high-availability-guide/controller/section_mysql.xml148(simpara)
|
||||
msgid ""
|
||||
"You must complete the next step while the MySQL database server is shut "
|
||||
"down."
|
||||
msgstr "MySQL データベースサーバーがシャットダウンしている間に、次の手順を完了する必要があります。"
|
||||
|
||||
#: ./doc/high-availability-guide/controller/section_mysql.xml149(simpara)
|
||||
#: ./doc/high-availability-guide/controller/section_mysql.xml154(simpara)
|
||||
msgid ""
|
||||
"For a new MySQL installation with no existing data, you may also run the "
|
||||
"<literal>mysql_install_db</literal> command:"
|
||||
msgstr "既存のデータが無い新しい MySQL インストール環境の場合、<literal>mysql_install_db</literal> コマンドを実行する必要があるかもしれません。"
|
||||
|
||||
#: ./doc/high-availability-guide/controller/section_mysql.xml154(simpara)
|
||||
#: ./doc/high-availability-guide/controller/section_mysql.xml159(simpara)
|
||||
msgid ""
|
||||
"Regardless of the approach, the steps outlined here must be completed on "
|
||||
"only one cluster node."
|
||||
msgstr "その方法に関わらず、ここに概要が示された手順は一つだけのクラスターノードで完了する必要があります。"
|
||||
|
||||
#: ./doc/high-availability-guide/controller/section_mysql.xml159(title)
|
||||
#: ./doc/high-availability-guide/controller/section_mysql.xml164(title)
|
||||
msgid "Add MySQL resources to Pacemaker"
|
||||
msgstr "MySQL リソースの Pacemaker への追加"
|
||||
|
||||
#: ./doc/high-availability-guide/controller/section_mysql.xml161(simpara)
|
||||
#: ./doc/high-availability-guide/controller/section_mysql.xml166(simpara)
|
||||
msgid ""
|
||||
"You can now add the Pacemaker configuration for MySQL resources. Connect to "
|
||||
"the Pacemaker cluster with <literal>crm configure</literal>, and add the "
|
||||
"following cluster resources:"
|
||||
msgstr "これで MySQL リソース用の Pacemaker 設定を追加できます。<literal>crm configure</literal> を用いて Pacemaker クラスターに接続し、以下のクラスターリソースを追加します。"
|
||||
|
||||
#: ./doc/high-availability-guide/controller/section_mysql.xml200(simpara)
|
||||
#: ./doc/high-availability-guide/controller/section_mysql.xml205(simpara)
|
||||
msgid ""
|
||||
"<literal>p_ip_mysql</literal>, a virtual IP address for use by MySQL "
|
||||
"(192.168.42.101),"
|
||||
msgstr "<literal>p_ip_mysql</literal>, MySQL により使用される仮想 IP アドレス (192.168.42.101),"
|
||||
|
||||
#: ./doc/high-availability-guide/controller/section_mysql.xml205(simpara)
|
||||
#: ./doc/high-availability-guide/controller/section_mysql.xml210(simpara)
|
||||
msgid ""
|
||||
"<literal>p_fs_mysql</literal>, a Pacemaker managed filesystem mounted to "
|
||||
"<literal>/var/lib/mysql</literal> on whatever node currently runs the MySQL "
|
||||
"service,"
|
||||
msgstr "<literal>p_fs_mysql</literal>, 現在 MySQL サービスを実行している、すべてのノードにおいて <literal>/var/lib/mysql</literal> にマウントされている、Pacemaker が管理しているファイルシステム。"
|
||||
|
||||
#: ./doc/high-availability-guide/controller/section_mysql.xml211(simpara)
|
||||
#: ./doc/high-availability-guide/controller/section_mysql.xml216(simpara)
|
||||
msgid ""
|
||||
"<literal>ms_drbd_mysql</literal>, the <emphasis>master/slave set</emphasis> "
|
||||
"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.xml222(simpara)
|
||||
#: ./doc/high-availability-guide/controller/section_mysql.xml227(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 "
|
||||
@ -1624,7 +1623,7 @@ msgid ""
|
||||
" the resource to match your preferred virtual IP address."
|
||||
msgstr "<literal>crm configure</literal> はバッチ入力をサポートします。そのため、現在の pacemaker 設定の中に上をコピー・ペーストし、適宜変更を反映できます。たとえば、お好みの仮想 IP アドレスに一致させるために、<literal>crm configure</literal> メニューから <literal>edit p_ip_mysql</literal> と入力し、リソースを編集できます。"
|
||||
|
||||
#: ./doc/high-availability-guide/controller/section_mysql.xml227(simpara)
|
||||
#: ./doc/high-availability-guide/controller/section_mysql.xml232(simpara)
|
||||
msgid ""
|
||||
"Once completed, commit your configuration changes by entering "
|
||||
"<literal>commit</literal> from the <literal>crm configure</literal> menu. "
|
||||
@ -1632,18 +1631,17 @@ msgid ""
|
||||
" one of your nodes."
|
||||
msgstr "完了すると、<literal>crm configure</literal> メニューから <literal>commit</literal> と入力し、設定の変更をコミットします。Pacemaker は MySQL サービスおよび依存するリソースを同じノードに起動します。"
|
||||
|
||||
#: ./doc/high-availability-guide/controller/section_mysql.xml233(title)
|
||||
#: ./doc/high-availability-guide/controller/section_mysql.xml238(title)
|
||||
msgid "Configure OpenStack services for highly available MySQL"
|
||||
msgstr "高可用性 MySQL のための OpenStack サービスの設定"
|
||||
|
||||
#: ./doc/high-availability-guide/controller/section_mysql.xml235(simpara)
|
||||
#: ./doc/high-availability-guide/controller/section_mysql.xml240(simpara)
|
||||
msgid ""
|
||||
"Your OpenStack services must now point their MySQL configuration to the "
|
||||
"highly available, virtual cluster IP address — rather than a MySQL server’s "
|
||||
"physical IP address as you normally would."
|
||||
msgstr "OpenStack サービスは、通常どおり MySQL サーバーの物理 IP アドレスを指定する代わりに、MySQL の設定が高可用性と仮想クラスター IP アドレスを指し示す必要があります。"
|
||||
"highly available, virtual cluster IP addressrather than a MySQL server"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/controller/section_mysql.xml238(simpara)
|
||||
#: ./doc/high-availability-guide/controller/section_mysql.xml243(simpara)
|
||||
msgid ""
|
||||
"For OpenStack Image, for example, if your MySQL service IP address is "
|
||||
"192.168.42.101 as in the configuration explained here, you would use the "
|
||||
@ -1651,7 +1649,7 @@ msgid ""
|
||||
">glance-registry.conf</literal>):"
|
||||
msgstr "OpenStack Image の例として、MySQL サーバーの IP アドレスがここで説明された設定にあるように 192.168.42.101 ならば、OpenStack Image レジストリ設定ファイル (<literal>glance-registry.conf</literal>) で以下の行を使用する必要があります。"
|
||||
|
||||
#: ./doc/high-availability-guide/controller/section_mysql.xml243(simpara)
|
||||
#: ./doc/high-availability-guide/controller/section_mysql.xml248(simpara)
|
||||
msgid ""
|
||||
"No other changes are necessary to your OpenStack configuration. If the node "
|
||||
"currently hosting your database experiences a problem necessitating service "
|
||||
@ -1738,10 +1736,10 @@ 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 "
|
||||
"& 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 "
|
||||
"That’s why all OpenStack API should be monitored by another tool, for "
|
||||
"example Nagios, with the goal to detect failures in the Cloud Framework "
|
||||
"infrastructure."
|
||||
msgstr "API ポートへの TCP 接続を確立するだけのため、監視チェックは極めてシンプルです。Corosync とリソースエージェントを使用するアクティブ / パッシブモードと比べて、サービスが実際に動作しているかを確認しません。そのため、クラウドのフレームワーク環境における障害を検知するために、すべての OpenStack API は他のツール (例: Nagios) により監視すべきです。"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/ha_aa_controllers/section_run_openstack_api_and_schedulers.xml41(title)
|
||||
msgid "Schedulers"
|
||||
|
||||
File diff suppressed because one or more lines are too long
File diff suppressed because it is too large
Load Diff
@ -4,9 +4,9 @@
|
||||
msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: OpenStack Manuals\n"
|
||||
"POT-Creation-Date: 2014-06-27 05:07+0000\n"
|
||||
"PO-Revision-Date: 2014-06-27 06:04+0000\n"
|
||||
"Last-Translator: Tomoyuki KATO <tomo@dream.daynight.jp>\n"
|
||||
"POT-Creation-Date: 2014-07-08 03:10+0000\n"
|
||||
"PO-Revision-Date: 2014-07-07 15:34+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"
|
||||
@ -518,11 +518,12 @@ msgstr "ログに関する問い合わせの応答を短縮するために、swi
|
||||
|
||||
#: ./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>) できます。"
|
||||
"You can use the <option>-o</option> or <option>--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.xml18(title)
|
||||
msgid "Upload and analyze log files"
|
||||
@ -573,9 +574,9 @@ 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 "
|
||||
"This example uses the <option>-o</option> option and a hyphen "
|
||||
"(<literal>-</literal>) to get information about an object."
|
||||
msgstr "この例は、オブジェクトに関する情報を取得するために、<option>-o —output</option> オプションとハイフン (<literal>-</literal>) を使用します。"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/user-guide-admin/section_cli_swift_analyze_log_files.xml67(para)
|
||||
msgid ""
|
||||
@ -607,10 +608,10 @@ 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 を使用します。"
|
||||
"Use a bash for loop with awk and swift with the <option>-o</option> or "
|
||||
"<option>--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.xml119(para)
|
||||
msgid ""
|
||||
@ -2365,12 +2366,12 @@ 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)
|
||||
#: ./doc/user-guide-admin/section_dashboard_admin_manage_stacks.xml5(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)
|
||||
#: ./doc/user-guide-admin/section_dashboard_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 "
|
||||
@ -2379,7 +2380,7 @@ msgid ""
|
||||
msgstr "Orchestration により、OpenStack クラウドに対して、テンプレートによるオーケストレーションエンジンが提供されます。これは、繰り返し実行可能な環境として、ストレージ、ネットワーク、インスタンス、アプリケーションなどのクラウドインフラストラクチャーリソースを作成および管理するために使用できます。"
|
||||
|
||||
#: ./doc/user-guide-admin/section_cli_admin_manage_stacks.xml11(para)
|
||||
#: ./doc/user-guide-admin/section_dashboard_admin_manage_stacks.xml10(para)
|
||||
#: ./doc/user-guide-admin/section_dashboard_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 "
|
||||
@ -3114,31 +3115,31 @@ msgid ""
|
||||
"<guibutton>Delete Users</guibutton> to confirm the deletion."
|
||||
msgstr "<guilabel>ユーザーの削除の確認</guilabel>ウィンドウで、削除の確認をするために<guibutton>ユーザーの削除</guibutton>をクリックします。"
|
||||
|
||||
#: ./doc/user-guide-admin/section_cli_admin_manage_environment.xml4(title)
|
||||
#: ./doc/user-guide-admin/section_cli_admin_manage_environment.xml5(title)
|
||||
msgid "Manage the OpenStack environment"
|
||||
msgstr "OpenStack 環境の管理"
|
||||
|
||||
#: ./doc/user-guide-admin/section_cli_admin_manage_environment.xml5(para)
|
||||
#: ./doc/user-guide-admin/section_cli_admin_manage_environment.xml6(para)
|
||||
msgid "This section includes tasks specific to the OpenStack environment."
|
||||
msgstr "このセクションは、OpenStack 環境に固有の作業を含みます。"
|
||||
|
||||
#: ./doc/user-guide-admin/section_dashboard_admin_manage_stacks.xml14(para)
|
||||
#: ./doc/user-guide-admin/section_dashboard_admin_manage_stacks.xml15(para)
|
||||
msgid "For information about:"
|
||||
msgstr "詳細は以下のとおりです。"
|
||||
|
||||
#: ./doc/user-guide-admin/section_dashboard_admin_manage_stacks.xml19(para)
|
||||
#: ./doc/user-guide-admin/section_dashboard_admin_manage_stacks.xml20(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)
|
||||
#: ./doc/user-guide-admin/section_dashboard_admin_manage_stacks.xml19(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)
|
||||
#: ./doc/user-guide-admin/section_dashboard_admin_manage_stacks.xml23(para)
|
||||
msgid ""
|
||||
"The basic creation and deletion of Orchestration stacks, refer to the <link "
|
||||
"href=\"http://docs.openstack.org/user-"
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: PACKAGE VERSION\n"
|
||||
"POT-Creation-Date: 2014-06-25 06:07+0000\n"
|
||||
"POT-Creation-Date: 2014-07-08 06:08+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"
|
||||
@ -370,7 +370,7 @@ msgid "Use the swift client <option>-o</option> or <option>-output</option> opti
|
||||
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."
|
||||
msgid "You can use the <option>-o</option> or <option>--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)
|
||||
@ -418,7 +418,7 @@ 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."
|
||||
msgid "This example uses the <option>-o</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)
|
||||
@ -442,7 +442,7 @@ 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."
|
||||
msgid "Use a bash for loop with awk and swift with the <option>-o</option> or <option>--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)
|
||||
@ -1735,15 +1735,15 @@ msgstr ""
|
||||
msgid "tenantID"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/user-guide-admin/section_cli_admin_manage_stacks.xml:5(title) ./doc/user-guide-admin/section_dashboard_admin_manage_stacks.xml:4(title)
|
||||
#: ./doc/user-guide-admin/section_cli_admin_manage_stacks.xml:5(title) ./doc/user-guide-admin/section_dashboard_admin_manage_stacks.xml:5(title)
|
||||
msgid "Launch and manage stacks"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/user-guide-admin/section_cli_admin_manage_stacks.xml:6(para) ./doc/user-guide-admin/section_dashboard_admin_manage_stacks.xml:5(para)
|
||||
#: ./doc/user-guide-admin/section_cli_admin_manage_stacks.xml:6(para) ./doc/user-guide-admin/section_dashboard_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_cli_admin_manage_stacks.xml:11(para) ./doc/user-guide-admin/section_dashboard_admin_manage_stacks.xml:10(para)
|
||||
#: ./doc/user-guide-admin/section_cli_admin_manage_stacks.xml:11(para) ./doc/user-guide-admin/section_dashboard_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 ""
|
||||
|
||||
@ -2289,27 +2289,27 @@ msgstr ""
|
||||
msgid "In the <guilabel>Confirm Delete Users</guilabel> window, click <guibutton>Delete Users</guibutton> to confirm the deletion."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/user-guide-admin/section_cli_admin_manage_environment.xml:4(title)
|
||||
#: ./doc/user-guide-admin/section_cli_admin_manage_environment.xml:5(title)
|
||||
msgid "Manage the OpenStack environment"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/user-guide-admin/section_cli_admin_manage_environment.xml:5(para)
|
||||
#: ./doc/user-guide-admin/section_cli_admin_manage_environment.xml:6(para)
|
||||
msgid "This section includes tasks specific to the OpenStack environment."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/user-guide-admin/section_dashboard_admin_manage_stacks.xml:14(para)
|
||||
#: ./doc/user-guide-admin/section_dashboard_admin_manage_stacks.xml:15(para)
|
||||
msgid "For information about:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/user-guide-admin/section_dashboard_admin_manage_stacks.xml:19(para)
|
||||
#: ./doc/user-guide-admin/section_dashboard_admin_manage_stacks.xml:20(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)
|
||||
#: ./doc/user-guide-admin/section_dashboard_admin_manage_stacks.xml:19(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)
|
||||
#: ./doc/user-guide-admin/section_dashboard_admin_manage_stacks.xml:23(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 ""
|
||||
|
||||
|
||||
5444
doc/user-guide/locale/fr.po
Normal file
5444
doc/user-guide/locale/fr.po
Normal file
File diff suppressed because it is too large
Load Diff
Loading…
Reference in New Issue
Block a user