Imported Translations from Transifex
Change-Id: Idb5051d2672a91c731b688227db316d30d891992
This commit is contained in:
OpenStack Proposal Bot
parent
841dfaa106
commit
fb21219680
@ -6,8 +6,8 @@
|
||||
msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: OpenStack Manuals\n"
|
||||
"POT-Creation-Date: 2014-05-26 01:46+0000\n"
|
||||
"PO-Revision-Date: 2014-05-25 23:54+0000\n"
|
||||
"POT-Creation-Date: 2014-05-27 02:13+0000\n"
|
||||
"PO-Revision-Date: 2014-05-27 04:51+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"
|
||||
@ -10955,7 +10955,7 @@ msgstr ""
|
||||
#: ./doc/common/section_cli_nova_startstop.xml40(replaceable)
|
||||
#: ./doc/common/section_cli_nova_boot.xml188(replaceable)
|
||||
msgid "INSTANCE_NAME"
|
||||
msgstr ""
|
||||
msgstr "INSTANCE_NAME"
|
||||
|
||||
#: ./doc/common/section_cli_nova_get_console.xml9(para)
|
||||
msgid "The command returns a URL from which you can access your instance:"
|
||||
@ -11405,7 +11405,7 @@ msgstr ""
|
||||
#: ./doc/common/ch_cli_keystone_commands.xml234(para)
|
||||
#: ./doc/common/ch_cli_keystone_commands.xml1100(para)
|
||||
msgid "Create new user"
|
||||
msgstr ""
|
||||
msgstr "新しいユーザーの作成"
|
||||
|
||||
#: ./doc/common/ch_cli_keystone_commands.xml242(para)
|
||||
#: ./doc/common/ch_cli_keystone_commands.xml1149(para)
|
||||
@ -12126,7 +12126,7 @@ msgstr ""
|
||||
#: ./doc/common/section_storage-concepts.xml21(td)
|
||||
#: ./doc/common/section_objectstorage-characteristics.xml46(title)
|
||||
msgid "Object Storage (swift)"
|
||||
msgstr ""
|
||||
msgstr "Object Storage (swift)"
|
||||
|
||||
#: ./doc/common/section_objectstorage-arch.xml64(para)
|
||||
msgid ""
|
||||
@ -24327,7 +24327,7 @@ msgstr ""
|
||||
|
||||
#: ./doc/common/section_getstart_image.xml5(title)
|
||||
msgid "OpenStack Image Service"
|
||||
msgstr ""
|
||||
msgstr "OpenStack Image Service"
|
||||
|
||||
#: ./doc/common/section_getstart_image.xml6(para)
|
||||
msgid "The OpenStack Image Service includes the following components:"
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: PACKAGE VERSION\n"
|
||||
"POT-Creation-Date: 2014-05-13 06:25+0000\n"
|
||||
"POT-Creation-Date: 2014-05-27 06:11+0000\n"
|
||||
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
|
||||
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
|
||||
"Language-Team: LANGUAGE <LL@li.org>\n"
|
||||
@ -1146,402 +1146,430 @@ msgid "MySQL with Galera"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:1599(simpara)
|
||||
msgid "Rather than starting with a vanilla version of MySQL and then adding Galera to it, you will want to install a version of MySQL patched for wsrep (Write Set REPlication) from <link href=\"https://launchpad.net/codership-mysql/0.7\">https://launchpad.net/codership-mysql/0.7</link>. Note that the installation requirements are a bit touchy; you will want to make sure to read the README file so you don’t miss any steps."
|
||||
msgid "Rather than starting with a vanilla version of MySQL, and then adding Galera, you will want to install a version of MySQL patched for wsrep (Write Set REPlication) from <link href=\"https://launchpad.net/codership-mysql/0.7\">https://launchpad.net/codership-mysql/0.7</link>. The wsrep API is suitable for configuring MySQL High Availability in OpenStack because it supports synchronous replication."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:1604(simpara)
|
||||
msgid "Next, download Galera itself from <link href=\"https://launchpad.net/galera/+download\">https://launchpad.net/galera/+download</link>. Go ahead and install the *.rpms or *.debs, taking care of any dependencies that your system doesn’t already have installed."
|
||||
msgid "Note that the installation requirements call for careful attention. Read the guide <link href=\"https://launchpadlibrarian.net/66669857/README-wsrep\">https://launchpadlibrarian.net/66669857/README-wsrep</link> to ensure you follow all the required steps."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:1607(simpara)
|
||||
msgid "Once you’ve completed the installation, you’ll need to make a few configuration changes:"
|
||||
msgid "Installing Galera through a MySQL version patched for wsrep:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:1608(simpara)
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:1610(simpara)
|
||||
msgid "Download Galera from <link href=\"https://launchpad.net/galera/+download\">https://launchpad.net/galera/+download</link>, and install the *.rpms or *.debs, which takes care of any dependencies that your system doesn’t already have installed."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:1617(simpara)
|
||||
msgid "Adjust the configuration:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:1622(simpara)
|
||||
msgid "In the system-wide <literal>my.conf</literal> file, make sure mysqld isn’t bound to 127.0.0.1, and that <literal>/etc/mysql/conf.d/</literal> is included. Typically you can find this file at <literal>/etc/my.cnf</literal>:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:1615(simpara)
|
||||
msgid "When adding a new node, you must configure it with a MySQL account that can access the other nodes so that it can request a state snapshot from one of those existing nodes. First specify that account information in <literal>/etc/mysql/conf.d/wsrep.cnf</literal>:"
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:1630(simpara)
|
||||
msgid "When adding a new node, you must configure it with a MySQL account that can access the other nodes. The new node must be able to request a state snapshot from one of the existing nodes:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:1619(simpara)
|
||||
msgid "Next connect as root and grant privileges to that user:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:1621(simpara)
|
||||
msgid "You’ll also need to remove user accounts with empty usernames, as they cause problems:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:1623(simpara)
|
||||
msgid "You’ll also need to set certain mandatory configuration options within MySQL itself. These include:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:1629(simpara)
|
||||
msgid "Finally, make sure that the nodes can access each other through the firewall. This might mean adjusting iptables, as in:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:1633(simpara)
|
||||
msgid "It might also mean configuring any NAT firewall between nodes to allow direct connections, or disabling SELinux or configuring it to allow mysqld to listen to sockets at unprivileged ports."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:1636(simpara)
|
||||
msgid "Now you’re ready to actually create the cluster."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:1639(title)
|
||||
msgid "Create the cluster"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:1641(simpara)
|
||||
msgid "In creating a cluster, you first start a single instance, which creates the cluster. The rest of the MySQL instances then connect to that cluster. For example, if you started on <literal>10.0.0.10</literal> by executing the command:"
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:1635(simpara)
|
||||
msgid "Specify your MySQL account information in <literal>/etc/mysql/conf.d/wsrep.cnf</literal>:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:1643(simpara)
|
||||
msgid "you could then connect to that cluster on the rest of the nodes by referencing the address of that node, as in:"
|
||||
msgid "Connect as root and grant privileges to that user:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:1645(simpara)
|
||||
msgid "You also have the option to set the <literal>wsrep_cluster_address</literal> in the <literal>/etc/mysql/conf.d/wsrep.cnf</literal> file, or within the client itself. (In fact, for some systems, such as MariaDB or Percona, this may be your only option.) For example, to check the status of the cluster, open the MySQL client and check the status of the various parameters:"
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:1651(simpara)
|
||||
msgid "Remove user accounts with empty usernames because they cause problems:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:1652(simpara)
|
||||
msgid "You should see a status that looks something like this:"
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:1659(simpara)
|
||||
msgid "Set up certain mandatory configuration options within MySQL itself. These include:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:1701(title)
|
||||
msgid "Galera monitoring scripts"
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:1672(simpara)
|
||||
msgid "Check that the nodes can access each other through the firewall. Depending on your environment, this might mean adjusting iptables, as in:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:1703(simpara)
|
||||
msgid "(Coming soon)"
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:1680(simpara)
|
||||
msgid "This might also mean configuring any NAT firewall between nodes to allow direct connections. You might need to disable SELinux, or configure it to allow mysqld to listen to sockets at unprivileged ports."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:1707(title)
|
||||
msgid "Other ways to provide a highly available database"
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:1683(simpara)
|
||||
msgid "Now you’re ready to create the cluster."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:1686(title)
|
||||
msgid "Create the cluster"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:1688(simpara)
|
||||
msgid "In creating a cluster, you first start a single instance, which creates the cluster. The rest of the MySQL instances then connect to that cluster:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:1691(simpara)
|
||||
msgid "An example of creating the cluster:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:1694(simpara)
|
||||
msgid "Start on <literal>10.0.0.10</literal> by executing the command:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:1702(simpara)
|
||||
msgid "Connect to that cluster on the rest of the nodes by referencing the address of that node, as in:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:1709(simpara)
|
||||
msgid "MySQL with Galera is by no means the only way to achieve database HA. MariaDB (<link href=\"https://mariadb.org/\">https://mariadb.org/</link>) and Percona (<link href=\"http://www.percona.com/\">http://www.percona.com/</link>) also work with Galera. You also have the option to use Postgres, which has its own replication, or some other database HA option."
|
||||
msgid "You also have the option to set the <literal>wsrep_cluster_address</literal> in the <literal>/etc/mysql/conf.d/wsrep.cnf</literal> file, or within the client itself. (In fact, for some systems, such as MariaDB or Percona, this may be your only option.)"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:1717(title)
|
||||
msgid "RabbitMQ"
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:1713(simpara)
|
||||
msgid "An example of checking the status of the cluster."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:1719(simpara)
|
||||
msgid "RabbitMQ is the default AMQP server used by many OpenStack services. Making the RabbitMQ service highly available involves the following steps:"
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:1716(simpara)
|
||||
msgid "Open the MySQL client and check the status of the various parameters:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:1723(simpara) ./doc/high-availability-guide/bk-ha-guide.xml:1740(title)
|
||||
msgid "Install RabbitMQ"
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:1723(simpara)
|
||||
msgid "You should see a status that looks something like this:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:1728(simpara)
|
||||
msgid "Configure RabbitMQ for HA queues"
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:1772(title)
|
||||
msgid "Galera monitoring scripts"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:1733(simpara)
|
||||
msgid "Configure OpenStack services to use Rabbit HA queues"
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:1774(simpara)
|
||||
msgid "(Coming soon)"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:1742(simpara)
|
||||
msgid "This setup has been tested with RabbitMQ 2.7.1."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:1745(title)
|
||||
msgid "On Ubuntu / Debian"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:1747(simpara) ./doc/high-availability-guide/bk-ha-guide.xml:1757(simpara)
|
||||
msgid "RabbitMQ is packaged on both distros:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:1750(link)
|
||||
msgid "Official manual for installing RabbitMQ on Ubuntu / Debian"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:1755(title)
|
||||
msgid "On Fedora / RHEL"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:1760(link)
|
||||
msgid "Official manual for installing RabbitMQ on Fedora / RHEL"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:1766(title)
|
||||
msgid "Configure RabbitMQ"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:1768(simpara)
|
||||
msgid "Here we are building a cluster of RabbitMQ nodes to construct a RabbitMQ broker. Mirrored queues in RabbitMQ improve the availability of service since it will be resilient to failures. We have to consider that while exchanges and bindings will survive the loss of individual nodes, queues and their messages will not because a queue and its contents is located on one node. If we lose this node, we also lose the queue."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:1773(simpara)
|
||||
msgid "We consider that we run (at least) two RabbitMQ servers. To build a broker, we need to ensure that all nodes have the same erlang cookie file. To do so, stop RabbitMQ everywhere and copy the cookie from rabbit1 server to other server(s):"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:1778(simpara)
|
||||
msgid "Then, start RabbitMQ on nodes. If RabbitMQ fails to start, you can’t continue to the next step."
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:1778(title)
|
||||
msgid "Other ways to provide a highly available database"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:1780(simpara)
|
||||
msgid "Now, we are building the HA cluster. From rabbit2, run these commands:"
|
||||
msgid "MySQL with Galera is by no means the only way to achieve database HA. MariaDB (<link href=\"https://mariadb.org/\">https://mariadb.org/</link>) and Percona (<link href=\"http://www.percona.com/\">http://www.percona.com/</link>) also work with Galera. You also have the option to use Postgres, which has its own replication, or another database HA option."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:1784(simpara)
|
||||
msgid "To verify the cluster status :"
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:1788(title)
|
||||
msgid "RabbitMQ"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:1789(simpara)
|
||||
msgid "If the cluster is working, you can now proceed to creating users and passwords for queues."
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:1790(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/bk-ha-guide.xml:1791(emphasis)
|
||||
msgid "Note for RabbitMQ version 3"
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:1794(simpara) ./doc/high-availability-guide/bk-ha-guide.xml:1811(title)
|
||||
msgid "Install RabbitMQ"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:1793(simpara)
|
||||
msgid "Queue mirroring is no longer controlled by the <emphasis>x-ha-policy</emphasis> argument when declaring a queue. OpenStack can continue to declare this argument, but it won’t cause queues to be mirrored. We need to make sure that all queues (except those with auto-generated names) are mirrored across all running nodes:"
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:1799(simpara)
|
||||
msgid "Configure RabbitMQ for HA queues"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:1798(link)
|
||||
msgid "More information about High availability in RabbitMQ"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:1803(title)
|
||||
msgid "Configure OpenStack services to use RabbitMQ"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:1805(simpara)
|
||||
msgid "We have to configure the OpenStack components to use at least two RabbitMQ nodes."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:1806(simpara)
|
||||
msgid "Do this configuration on all services using RabbitMQ:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:1807(simpara)
|
||||
msgid "RabbitMQ HA cluster host:port pairs:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:1809(simpara)
|
||||
msgid "How frequently to retry connecting with RabbitMQ:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:1811(simpara)
|
||||
msgid "How long to back-off for between retries when connecting to RabbitMQ:"
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:1804(simpara)
|
||||
msgid "Configure OpenStack services to use Rabbit HA queues"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:1813(simpara)
|
||||
msgid "This setup has been tested with RabbitMQ 2.7.1."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:1816(title)
|
||||
msgid "On Ubuntu / Debian"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:1818(simpara) ./doc/high-availability-guide/bk-ha-guide.xml:1828(simpara)
|
||||
msgid "RabbitMQ is packaged on both distros:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:1821(link)
|
||||
msgid "Official manual for installing RabbitMQ on Ubuntu / Debian"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:1826(title)
|
||||
msgid "On Fedora / RHEL"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:1831(link)
|
||||
msgid "Official manual for installing RabbitMQ on Fedora / RHEL"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:1837(title)
|
||||
msgid "Configure RabbitMQ"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:1839(simpara)
|
||||
msgid "Here we are building a cluster of RabbitMQ nodes to construct a RabbitMQ broker. Mirrored queues in RabbitMQ improve the availability of service since it will be resilient to failures. We have to consider that while exchanges and bindings will survive the loss of individual nodes, queues and their messages will not because a queue and its contents is located on one node. If we lose this node, we also lose the queue."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:1844(simpara)
|
||||
msgid "We consider that we run (at least) two RabbitMQ servers. To build a broker, we need to ensure that all nodes have the same erlang cookie file. To do so, stop RabbitMQ everywhere and copy the cookie from rabbit1 server to other server(s):"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:1849(simpara)
|
||||
msgid "Then, start RabbitMQ on nodes. If RabbitMQ fails to start, you can’t continue to the next step."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:1851(simpara)
|
||||
msgid "Now, we are building the HA cluster. From rabbit2, run these commands:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:1855(simpara)
|
||||
msgid "To verify the cluster status :"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:1860(simpara)
|
||||
msgid "If the cluster is working, you can now proceed to creating users and passwords for queues."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:1862(emphasis)
|
||||
msgid "Note for RabbitMQ version 3"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:1864(simpara)
|
||||
msgid "Queue mirroring is no longer controlled by the <emphasis>x-ha-policy</emphasis> argument when declaring a queue. OpenStack can continue to declare this argument, but it won’t cause queues to be mirrored. We need to make sure that all queues (except those with auto-generated names) are mirrored across all running nodes:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:1869(link)
|
||||
msgid "More information about High availability in RabbitMQ"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:1874(title)
|
||||
msgid "Configure OpenStack services to use RabbitMQ"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:1876(simpara)
|
||||
msgid "We have to configure the OpenStack components to use at least two RabbitMQ nodes."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:1877(simpara)
|
||||
msgid "Do this configuration on all services using RabbitMQ:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:1878(simpara)
|
||||
msgid "RabbitMQ HA cluster host:port pairs:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:1880(simpara)
|
||||
msgid "How frequently to retry connecting with RabbitMQ:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:1882(simpara)
|
||||
msgid "How long to back-off for between retries when connecting to RabbitMQ:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:1884(simpara)
|
||||
msgid "Maximum retries with trying to connect to RabbitMQ (infinite by default):"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:1815(simpara)
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:1886(simpara)
|
||||
msgid "Use durable queues in RabbitMQ:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:1817(simpara)
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:1888(simpara)
|
||||
msgid "Use H/A queues in RabbitMQ (x-ha-policy: all):"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:1819(simpara)
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:1890(simpara)
|
||||
msgid "If you change the configuration from an old setup which did not use HA queues, you should interrupt the service:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:1823(simpara)
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:1894(simpara)
|
||||
msgid "Services currently working with HA queues: OpenStack Compute, OpenStack Block Storage, OpenStack Networking, Telemetry."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:1828(title)
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:1899(title)
|
||||
msgid "HAproxy nodes"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:1830(simpara)
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:1901(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/bk-ha-guide.xml:1834(simpara)
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:1905(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/bk-ha-guide.xml:1837(simpara)
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:1908(simpara)
|
||||
msgid "Here is an example for HAproxy configuration file:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:1977(simpara)
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:2048(simpara)
|
||||
msgid "After each change of this file, you should restart HAproxy."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:1981(title)
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:2052(title)
|
||||
msgid "OpenStack controller nodes"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:1983(simpara)
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:2054(simpara)
|
||||
msgid "OpenStack controller nodes contain:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:1986(simpara)
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:2057(simpara)
|
||||
msgid "All OpenStack API services"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:1991(simpara)
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:2062(simpara)
|
||||
msgid "All OpenStack schedulers"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:1996(simpara)
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:2067(simpara)
|
||||
msgid "Memcached service"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:2003(title)
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:2074(title)
|
||||
msgid "Run OpenStack API and schedulers"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:2007(title)
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:2078(title)
|
||||
msgid "API services"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:2009(simpara)
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:2080(simpara)
|
||||
msgid "All OpenStack projects have an API service for controlling all the resources in the Cloud. In Active / Active mode, the most common setup is to scale-out these services on at least two nodes and use load-balancing and virtual IP (with HAproxy & Keepalived in this setup)."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:2013(emphasis)
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:2084(emphasis)
|
||||
msgid "Configure API OpenStack services"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:2015(simpara)
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:2086(simpara)
|
||||
msgid "To configure our Cloud using Highly available and scalable API services, we need to ensure that:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:2018(simpara)
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:2089(simpara)
|
||||
msgid "You use Virtual IP when configuring OpenStack Identity endpoints."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:2023(simpara)
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:2094(simpara)
|
||||
msgid "All OpenStack configuration files should refer to Virtual IP."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:2029(emphasis)
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:2100(emphasis)
|
||||
msgid "In case of failure"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:2031(simpara)
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:2102(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."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:2038(title)
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:2109(title)
|
||||
msgid "Schedulers"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:2040(simpara)
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:2111(simpara)
|
||||
msgid "OpenStack schedulers are used to determine how to dispatch compute, network and volume requests. The most common setup is to use RabbitMQ as messaging system already documented in this guide. Those services are connected to the messaging backend and can scale-out :"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:2045(simpara)
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:2116(simpara)
|
||||
msgid "nova-scheduler"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:2050(simpara)
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:2121(simpara)
|
||||
msgid "nova-conductor"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:2055(simpara)
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:2126(simpara)
|
||||
msgid "cinder-scheduler"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:2060(simpara)
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:2131(simpara)
|
||||
msgid "neutron-server"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:2065(simpara)
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:2136(simpara)
|
||||
msgid "ceilometer-collector"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:2070(simpara)
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:2141(simpara)
|
||||
msgid "heat-engine"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:2075(simpara)
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:2146(simpara)
|
||||
msgid "Please refer to the RabbitMQ section for configure these services with multiple messaging servers."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:2080(title)
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:2151(title)
|
||||
msgid "Memcached"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:2082(simpara)
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:2153(simpara)
|
||||
msgid "Most of OpenStack services use an application to offer persistence and store ephemeral data (like tokens). Memcached is one of them and can scale-out easily without specific trick."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:2084(simpara)
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:2155(simpara)
|
||||
msgid "To install and configure it, read the <link href=\"http://code.google.com/p/memcached/wiki/NewStart\">official documentation</link>."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:2085(simpara)
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:2156(simpara)
|
||||
msgid "Memory caching is managed by oslo-incubator so the way to use multiple memcached servers is the same for all projects."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:2086(simpara)
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:2157(simpara)
|
||||
msgid "Example with two hosts:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:2088(simpara)
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:2159(simpara)
|
||||
msgid "By default, controller1 handles the caching service but if the host goes down, controller2 does the job. For more information about memcached installation, see the OpenStack Cloud Administrator Guide."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:2095(title)
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:2166(title)
|
||||
msgid "OpenStack network nodes"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:2097(simpara)
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:2168(simpara)
|
||||
msgid "OpenStack network nodes contain:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:2100(simpara)
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:2171(simpara)
|
||||
msgid "neutron DHCP agent"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:2105(simpara)
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:2176(simpara)
|
||||
msgid "neutron L2 agent"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:2110(simpara)
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:2181(simpara)
|
||||
msgid "Neutron L3 agent"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:2115(simpara)
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:2186(simpara)
|
||||
msgid "neutron metadata agent"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:2120(simpara)
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:2191(simpara)
|
||||
msgid "neutron lbaas agent"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:2126(simpara)
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:2197(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/bk-ha-guide.xml:2134(title)
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:2205(title)
|
||||
msgid "Run neutron DHCP agent"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:2136(simpara)
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:2207(simpara)
|
||||
msgid "OpenStack Networking service has a scheduler that lets you run multiple agents across nodes. Also, the DHCP agent can be natively highly available. For details, see <link href=\"http://docs.openstack.org/trunk/config-reference/content/app_demo_multi_dhcp_agents.html\">OpenStack Configuration Reference</link>."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:2142(title)
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:2213(title)
|
||||
msgid "Run neutron L3 agent"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:2144(simpara)
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:2215(simpara)
|
||||
msgid "The neutron L3 agent is scalable thanks to the scheduler that allows distribution of virtual routers across multiple nodes. But there is no native feature to make these routers highly available. At this time, the Active / Passive solution exists to run the Neutron L3 agent in failover mode with Pacemaker. See the Active / Passive section of this guide."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:2153(title)
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:2224(title)
|
||||
msgid "Run neutron metadata agent"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:2155(simpara)
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml:2226(simpara)
|
||||
msgid "There is no native feature to make this service highly available. At this time, the Active / Passive solution exists to run the neutron metadata agent in failover mode with Pacemaker. See the Active / Passive section of this guide."
|
||||
msgstr ""
|
||||
|
||||
|
||||
@ -4,9 +4,9 @@
|
||||
msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: OpenStack Manuals\n"
|
||||
"POT-Creation-Date: 2014-05-23 21:32+0000\n"
|
||||
"PO-Revision-Date: 2014-05-23 12:32+0000\n"
|
||||
"Last-Translator: Tomoyuki KATO <tomo@dream.daynight.jp>\n"
|
||||
"POT-Creation-Date: 2014-05-27 02:13+0000\n"
|
||||
"PO-Revision-Date: 2014-05-27 01:51+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"
|
||||
@ -1776,29 +1776,39 @@ msgstr "Galera を用いた MySQL"
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml1599(simpara)
|
||||
msgid ""
|
||||
"Rather than starting with a vanilla version of MySQL and then adding Galera "
|
||||
"to it, you will want to install a version of MySQL patched for wsrep (Write "
|
||||
"Set REPlication) from <link href=\"https://launchpad.net/codership-"
|
||||
"mysql/0.7\">https://launchpad.net/codership-mysql/0.7</link>. Note that the "
|
||||
"installation requirements are a bit touchy; you will want to make sure to "
|
||||
"read the README file so you don’t miss any steps."
|
||||
msgstr "MySQL の派生バージョンから始めるよりは、<link href=\"https://launchpad.net/codership-mysql/0.7\">https://launchpad.net/codership-mysql/0.7</link> にある wsrep (Write Set REPlication) のパッチを適用したバージョンの MySQL をインストールするとよいでしょう。インストール要件が少しややこしいことに注意してください。すべての手順を見落とさないために、README ファイルを必ず参照するとよいでしょう。"
|
||||
"Rather than starting with a vanilla version of MySQL, and then adding "
|
||||
"Galera, you will want to install a version of MySQL patched for wsrep (Write"
|
||||
" Set REPlication) from <link href=\"https://launchpad.net/codership-"
|
||||
"mysql/0.7\">https://launchpad.net/codership-mysql/0.7</link>. The wsrep API "
|
||||
"is suitable for configuring MySQL High Availability in OpenStack because it "
|
||||
"supports synchronous replication."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml1604(simpara)
|
||||
msgid ""
|
||||
"Next, download Galera itself from <link "
|
||||
"href=\"https://launchpad.net/galera/+download\">https://launchpad.net/galera/+download</link>."
|
||||
" Go ahead and install the *.rpms or *.debs, taking care of any dependencies "
|
||||
"that your system doesn’t already have installed."
|
||||
msgstr "次に、Galera 自身を <link href=\"https://launchpad.net/galera/+download\">https://launchpad.net/galera/+download</link> からダウンロードします。そして、システムにまだインストールされていない依存パッケージに注意しながら、*.rpms または *.debs をインストールします。"
|
||||
"Note that the installation requirements call for careful attention. Read the"
|
||||
" guide <link href=\"https://launchpadlibrarian.net/66669857/README-"
|
||||
"wsrep\">https://launchpadlibrarian.net/66669857/README-wsrep</link> to "
|
||||
"ensure you follow all the required steps."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml1607(simpara)
|
||||
msgid ""
|
||||
"Once you’ve completed the installation, you’ll need to make a few "
|
||||
"configuration changes:"
|
||||
msgstr "インストールを完了すると、少し設定を変更する必要があります。"
|
||||
msgid "Installing Galera through a MySQL version patched for wsrep:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml1608(simpara)
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml1610(simpara)
|
||||
msgid ""
|
||||
"Download Galera from <link "
|
||||
"href=\"https://launchpad.net/galera/+download\">https://launchpad.net/galera/+download</link>,"
|
||||
" and install the *.rpms or *.debs, which takes care of any dependencies that"
|
||||
" your system doesn’t already have installed."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml1617(simpara)
|
||||
msgid "Adjust the configuration:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml1622(simpara)
|
||||
msgid ""
|
||||
"In the system-wide <literal>my.conf</literal> file, make sure mysqld isn’t "
|
||||
"bound to 127.0.0.1, and that <literal>/etc/mysql/conf.d/</literal> is "
|
||||
@ -1806,153 +1816,169 @@ msgid ""
|
||||
"<literal>/etc/my.cnf</literal>:"
|
||||
msgstr "システム全体の <literal>my.conf</literal> ファイルで、mysqld が 127.0.0.1 に制限されておらず、<literal>/etc/mysql/conf.d/</literal> がインクルードされることを確認します。このファイルは一般的に <literal>/etc/my.cnf</literal> にあります。"
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml1615(simpara)
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml1630(simpara)
|
||||
msgid ""
|
||||
"When adding a new node, you must configure it with a MySQL account that can "
|
||||
"access the other nodes so that it can request a state snapshot from one of "
|
||||
"those existing nodes. First specify that account information in "
|
||||
"access the other nodes. The new node must be able to request a state "
|
||||
"snapshot from one of the existing nodes:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml1635(simpara)
|
||||
msgid ""
|
||||
"Specify your MySQL account information in "
|
||||
"<literal>/etc/mysql/conf.d/wsrep.cnf</literal>:"
|
||||
msgstr "新しいノードを追加するとき、他のノードにアクセスできる MySQL アカウントを用いて設定する必要があります。それらの既存のノードのどれかから状態のスナップショットを実行できるようにするためです。まず、<literal>/etc/mysql/conf.d/wsrep.cnf</literal> にアカウント情報を指定します。"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml1619(simpara)
|
||||
msgid "Next connect as root and grant privileges to that user:"
|
||||
msgstr "次に root として接続し、そのユーザーに権限を与えます。"
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml1643(simpara)
|
||||
msgid "Connect as root and grant privileges to that user:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml1621(simpara)
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml1651(simpara)
|
||||
msgid "Remove user accounts with empty usernames because they cause problems:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml1659(simpara)
|
||||
msgid ""
|
||||
"You’ll also need to remove user accounts with empty usernames, as they cause"
|
||||
" problems:"
|
||||
msgstr "また、問題を引き起こす可能性があるので、空のユーザー名を用いてユーザーアカウントを削除する必要があります。"
|
||||
"Set up certain mandatory configuration options within MySQL itself. These "
|
||||
"include:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml1623(simpara)
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml1672(simpara)
|
||||
msgid ""
|
||||
"You’ll also need to set certain mandatory configuration options within MySQL"
|
||||
" itself. These include:"
|
||||
msgstr "MySQL 自身の中で特定の必須設定オプションを設定する必要があります。これらには次のものがあります。"
|
||||
"Check that the nodes can access each other through the firewall. Depending "
|
||||
"on your environment, this might mean adjusting iptables, as in:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml1629(simpara)
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml1680(simpara)
|
||||
msgid ""
|
||||
"Finally, make sure that the nodes can access each other through the "
|
||||
"firewall. This might mean adjusting iptables, as in:"
|
||||
msgstr "最後に、ノードがファイアウォール越しにお互いにアクセスできることを確認します。これは次のような iptables の調整を意味するかもしれません。"
|
||||
"This might also mean configuring any NAT firewall between nodes to allow "
|
||||
"direct connections. You might need to disable SELinux, or configure it to "
|
||||
"allow mysqld to listen to sockets at unprivileged ports."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml1633(simpara)
|
||||
msgid ""
|
||||
"It might also mean configuring any NAT firewall between nodes to allow "
|
||||
"direct connections, or disabling SELinux or configuring it to allow mysqld "
|
||||
"to listen to sockets at unprivileged ports."
|
||||
msgstr "直接通信を許可するためにノード間の NAT ファイアウォールを設定すること、または、SELinux を無効化すること、mysqld が非特権ポートでソケットをリッスンできるよう設定することを意味します。"
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml1683(simpara)
|
||||
msgid "Now you’re ready to create the cluster."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml1636(simpara)
|
||||
msgid "Now you’re ready to actually create the cluster."
|
||||
msgstr "これで実際にクラスターを作成する準備ができました。"
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml1639(title)
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml1686(title)
|
||||
msgid "Create the cluster"
|
||||
msgstr "クラスターの作成"
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml1641(simpara)
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml1688(simpara)
|
||||
msgid ""
|
||||
"In creating a cluster, you first start a single instance, which creates the "
|
||||
"cluster. The rest of the MySQL instances then connect to that cluster. For "
|
||||
"example, if you started on <literal>10.0.0.10</literal> by executing the "
|
||||
"command:"
|
||||
msgstr "クラスターを作成するとき、クラスターを作成する、単独のインスタンスをまず起動します。MySQL インスタンスの残りはそのクラスターに接続します。たとえば、以下のコマンドを実行して、<literal>10.0.0.10</literal> に起動する場合です。"
|
||||
"cluster. The rest of the MySQL instances then connect to that cluster:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml1643(simpara)
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml1691(simpara)
|
||||
msgid "An example of creating the cluster:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml1694(simpara)
|
||||
msgid "Start on <literal>10.0.0.10</literal> by executing the command:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml1702(simpara)
|
||||
msgid ""
|
||||
"you could then connect to that cluster on the rest of the nodes by "
|
||||
"referencing the address of that node, as in:"
|
||||
msgstr "次のとおり、そのノードを参照することにより、残りのノードからそのクラスターに接続できます。"
|
||||
"Connect to that cluster on the rest of the nodes by referencing the address "
|
||||
"of that node, as in:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml1645(simpara)
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml1709(simpara)
|
||||
msgid ""
|
||||
"You also have the option to set the <literal>wsrep_cluster_address</literal>"
|
||||
" in the <literal>/etc/mysql/conf.d/wsrep.cnf</literal> file, or within the "
|
||||
"client itself. (In fact, for some systems, such as MariaDB or Percona, this "
|
||||
"may be your only option.) For example, to check the status of the cluster, "
|
||||
"open the MySQL client and check the status of the various parameters:"
|
||||
msgstr "<literal>/etc/mysql/conf.d/wsrep.cnf</literal> ファイル、またはクライアント自身の中に <literal>wsrep_cluster_address</literal> を設定できます。(実際、MariaDB や Percona のようないくつかのシステムは、これが唯一の選択肢になるでしょう。) たとえば、クラスターの状態を確認するために、MySQL クライアントを開き、さまざまなパラメーターの状態を確認します。"
|
||||
"may be your only option.)"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml1652(simpara)
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml1713(simpara)
|
||||
msgid "An example of checking the status of the cluster."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml1716(simpara)
|
||||
msgid "Open the MySQL client and check the status of the various parameters:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml1723(simpara)
|
||||
msgid "You should see a status that looks something like this:"
|
||||
msgstr "このように見える状態を確認すべきです。"
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml1701(title)
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml1772(title)
|
||||
msgid "Galera monitoring scripts"
|
||||
msgstr "Galera 監視スクリプト"
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml1703(simpara)
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml1774(simpara)
|
||||
msgid "(Coming soon)"
|
||||
msgstr "(近日公開)"
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml1707(title)
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml1778(title)
|
||||
msgid "Other ways to provide a highly available database"
|
||||
msgstr "高可用性データベースを提供する別の方法"
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml1709(simpara)
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml1780(simpara)
|
||||
msgid ""
|
||||
"MySQL with Galera is by no means the only way to achieve database HA. "
|
||||
"MariaDB (<link href=\"https://mariadb.org/\">https://mariadb.org/</link>) "
|
||||
"and Percona (<link "
|
||||
"href=\"http://www.percona.com/\">http://www.percona.com/</link>) also work "
|
||||
"with Galera. You also have the option to use Postgres, which has its own "
|
||||
"replication, or some other database HA option."
|
||||
msgstr "MySQL と Galera の併用がデータベースを HA 化する唯一の方法ではありません。MariaDB (<link href=\"https://mariadb.org/\">https://mariadb.org/</link>) や Percona (<link href=\"http://www.percona.com/\">http://www.percona.com/</link>) も Galera と併用できます。独自のレプリケーション機能を持つ Postgres や他のデータベースの HA オプションを使用するという選択肢もあります。"
|
||||
"replication, or another database HA option."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml1717(title)
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml1788(title)
|
||||
msgid "RabbitMQ"
|
||||
msgstr "RabbitMQ"
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml1719(simpara)
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml1790(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/bk-ha-guide.xml1723(simpara)
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml1740(title)
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml1794(simpara)
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml1811(title)
|
||||
msgid "Install RabbitMQ"
|
||||
msgstr "RabbitMQ のインストール"
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml1728(simpara)
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml1799(simpara)
|
||||
msgid "Configure RabbitMQ for HA queues"
|
||||
msgstr "高可用性 キュー用の RabbitMQ の設定"
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml1733(simpara)
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml1804(simpara)
|
||||
msgid "Configure OpenStack services to use Rabbit HA queues"
|
||||
msgstr "RabbitMQ HA キューを使用するための OpenStack サービスの設定"
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml1742(simpara)
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml1813(simpara)
|
||||
msgid "This setup has been tested with RabbitMQ 2.7.1."
|
||||
msgstr "このセットアップは RabbitMQ 2.7.1 を用いてテストしました。"
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml1745(title)
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml1816(title)
|
||||
msgid "On Ubuntu / Debian"
|
||||
msgstr "Ubuntu / Debian の場合"
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml1747(simpara)
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml1757(simpara)
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml1818(simpara)
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml1828(simpara)
|
||||
msgid "RabbitMQ is packaged on both distros:"
|
||||
msgstr "RabbitMQ がどちらもパッケージ化されています。"
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml1750(link)
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml1821(link)
|
||||
msgid "Official manual for installing RabbitMQ on Ubuntu / Debian"
|
||||
msgstr "Ubuntu / Debian に RabbitMQ をインストールする方法の公式マニュアル"
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml1755(title)
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml1826(title)
|
||||
msgid "On Fedora / RHEL"
|
||||
msgstr "Fedora / RHEL の場合"
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml1760(link)
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml1831(link)
|
||||
msgid "Official manual for installing RabbitMQ on Fedora / RHEL"
|
||||
msgstr "Fedora / RHEL に RabbitMQ をインストールする方法の公式マニュアル"
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml1766(title)
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml1837(title)
|
||||
msgid "Configure RabbitMQ"
|
||||
msgstr "RabbitMQ の設定"
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml1768(simpara)
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml1839(simpara)
|
||||
msgid ""
|
||||
"Here we are building a cluster of RabbitMQ nodes to construct a RabbitMQ "
|
||||
"broker. Mirrored queues in RabbitMQ improve the availability of service "
|
||||
@ -1962,7 +1988,7 @@ msgid ""
|
||||
"node. If we lose this node, we also lose the queue."
|
||||
msgstr "これから RabbitMQ ブローカーを構築するために RabbitMQ ノードのクラスターを構築します。障害の耐性ができるため、RabbitMQ のキューミラーによりサービスの可用性を高められます。メッセージ交換とバインドにより個々のノードの損失があると、キューとその内容が 1 つのノードに置かれているため、キューとそれらのメッセージが無くなることに注意してください。このノードが失われた場合、キューも失われます。"
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml1773(simpara)
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml1844(simpara)
|
||||
msgid ""
|
||||
"We consider that we run (at least) two RabbitMQ servers. To build a broker, "
|
||||
"we need to ensure that all nodes have the same erlang cookie file. To do so,"
|
||||
@ -1970,31 +1996,31 @@ msgid ""
|
||||
"server(s):"
|
||||
msgstr "(少なくとも) 2 つの RabbitMQ サーバーを実行することを考えます。ブローカーを構築するために、すべてのノードが必ず同じ erlang クッキーファイルを持つ必要があります。そうするために、すべての RabbitMQ を停止し、クッキーを rabbit1 サーバーから他のサーバーにコピーします。"
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml1778(simpara)
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml1849(simpara)
|
||||
msgid ""
|
||||
"Then, start RabbitMQ on nodes. If RabbitMQ fails to start, you can’t "
|
||||
"continue to the next step."
|
||||
msgstr "そして、ノードで RabbitMQ を起動します。RabbitMQ の起動に失敗した場合、次の手順に進めません。"
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml1780(simpara)
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml1851(simpara)
|
||||
msgid "Now, we are building the HA cluster. From rabbit2, run these commands:"
|
||||
msgstr "これで、HA クラスターの構築ができました。rabbit2 からこれらのコマンドを実行します。"
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml1784(simpara)
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml1855(simpara)
|
||||
msgid "To verify the cluster status :"
|
||||
msgstr "クラスターの状態を確認する方法:"
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml1789(simpara)
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml1860(simpara)
|
||||
msgid ""
|
||||
"If the cluster is working, you can now proceed to creating users and "
|
||||
"passwords for queues."
|
||||
msgstr "クラスターが動作していれば、キュー用のユーザーとパスワードを作成する手順に進めます。"
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml1791(emphasis)
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml1862(emphasis)
|
||||
msgid "Note for RabbitMQ version 3"
|
||||
msgstr "RabbitMQ バージョン 3 の注意事項"
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml1793(simpara)
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml1864(simpara)
|
||||
msgid ""
|
||||
"Queue mirroring is no longer controlled by the <emphasis>x-ha-"
|
||||
"policy</emphasis> argument when declaring a queue. OpenStack can continue to"
|
||||
@ -2003,66 +2029,66 @@ msgid ""
|
||||
"mirrored across all running nodes:"
|
||||
msgstr "キューの宣言時、キューミラーが <emphasis>x-ha-policy</emphasis> 引数により制御されなくなりました。OpenStack がこの引数を宣言し続けますが、キューはミラーされません。すべてのキュー (自動生成された名前を除いて) が実行中の全ノードにわたり確実にミラーされる必要があります。"
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml1798(link)
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml1869(link)
|
||||
msgid "More information about High availability in RabbitMQ"
|
||||
msgstr "RabbitMQ の高可用性に関する詳細"
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml1803(title)
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml1874(title)
|
||||
msgid "Configure OpenStack services to use RabbitMQ"
|
||||
msgstr "RabbitMQ を使用するための OpenStack サービスの設定"
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml1805(simpara)
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml1876(simpara)
|
||||
msgid ""
|
||||
"We have to configure the OpenStack components to use at least two RabbitMQ "
|
||||
"nodes."
|
||||
msgstr "2 つ以上の RabbitMQ ノードを使用するよう、OpenStack のコンポーネントを設定する必要があります。"
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml1806(simpara)
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml1877(simpara)
|
||||
msgid "Do this configuration on all services using RabbitMQ:"
|
||||
msgstr "RabbitMQ を使用するすべてのサービスでこの設定を行います。"
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml1807(simpara)
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml1878(simpara)
|
||||
msgid "RabbitMQ HA cluster host:port pairs:"
|
||||
msgstr "RabbitMQ HA クラスターの host:port の組:"
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml1809(simpara)
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml1880(simpara)
|
||||
msgid "How frequently to retry connecting with RabbitMQ:"
|
||||
msgstr "RabbitMQ と再接続する頻度:"
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml1811(simpara)
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml1882(simpara)
|
||||
msgid "How long to back-off for between retries when connecting to RabbitMQ:"
|
||||
msgstr "RabbitMQ に接続するとき再試行するまでにバックオフする間隔:"
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml1813(simpara)
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml1884(simpara)
|
||||
msgid ""
|
||||
"Maximum retries with trying to connect to RabbitMQ (infinite by default):"
|
||||
msgstr "RabbitMQ に接続を試行する最大回数 (デフォルトで無制限):"
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml1815(simpara)
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml1886(simpara)
|
||||
msgid "Use durable queues in RabbitMQ:"
|
||||
msgstr "RabbitMQ での永続キューの使用:"
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml1817(simpara)
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml1888(simpara)
|
||||
msgid "Use H/A queues in RabbitMQ (x-ha-policy: all):"
|
||||
msgstr "RabbitMQ での H/A キューの使用 (x-ha-policy: all):"
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml1819(simpara)
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml1890(simpara)
|
||||
msgid ""
|
||||
"If you change the configuration from an old setup which did not use HA "
|
||||
"queues, you should interrupt the service:"
|
||||
msgstr "HA キューを使用していない古いセットアップから設定を変更した場合、サービスを中断しなければいけません。"
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml1823(simpara)
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml1894(simpara)
|
||||
msgid ""
|
||||
"Services currently working with HA queues: OpenStack Compute, OpenStack "
|
||||
"Block Storage, OpenStack Networking, Telemetry."
|
||||
msgstr "次のサービスはいま HA キューで動作しています。OpenStack Compute、OpenStack Cinder、OpenStack Networking、Telemetry。"
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml1828(title)
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml1899(title)
|
||||
msgid "HAproxy nodes"
|
||||
msgstr "HAproxy ノード"
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml1830(simpara)
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml1901(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 "
|
||||
@ -2071,7 +2097,7 @@ msgid ""
|
||||
"connections is clearly realistic with today’s hardware."
|
||||
msgstr "HAProxy は高可用性、負荷分散、TCP と HTTP ベースのアプリケーションに対するプロキシを提供する非常に高速かつ信頼性のあるソリューションです。とくに永続性とレイヤー 7 処理を必要とする、非常に負荷の高いウェブサイトに適しています。数千の接続をサポートすることは、今日のハードウェアではかなり現実的です。"
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml1834(simpara)
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml1905(simpara)
|
||||
msgid ""
|
||||
"For installing HAproxy on your nodes, you should consider its <link "
|
||||
"href=\"http://haproxy.1wt.eu/#docs\">official documentation</link>. Also, "
|
||||
@ -2079,43 +2105,43 @@ 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/bk-ha-guide.xml1837(simpara)
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml1908(simpara)
|
||||
msgid "Here is an example for HAproxy configuration file:"
|
||||
msgstr "これは HAproxy 設定ファイルの例です。"
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml1977(simpara)
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml2048(simpara)
|
||||
msgid "After each change of this file, you should restart HAproxy."
|
||||
msgstr "このファイルをそれぞれ変更した後、HAproxy を再起動しなければいけません。"
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml1981(title)
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml2052(title)
|
||||
msgid "OpenStack controller nodes"
|
||||
msgstr "OpenStack コントローラーノード"
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml1983(simpara)
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml2054(simpara)
|
||||
msgid "OpenStack controller nodes contain:"
|
||||
msgstr "OpenStack コントローラーノードは次のものを含みます。"
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml1986(simpara)
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml2057(simpara)
|
||||
msgid "All OpenStack API services"
|
||||
msgstr "すべての OpenStack API サービス"
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml1991(simpara)
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml2062(simpara)
|
||||
msgid "All OpenStack schedulers"
|
||||
msgstr "すべての OpenStack スケジューラー"
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml1996(simpara)
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml2067(simpara)
|
||||
msgid "Memcached service"
|
||||
msgstr "Memcached サービス"
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml2003(title)
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml2074(title)
|
||||
msgid "Run OpenStack API and schedulers"
|
||||
msgstr "OpenStack API & スケジューラーの実行"
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml2007(title)
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml2078(title)
|
||||
msgid "API services"
|
||||
msgstr "API サービス"
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml2009(simpara)
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml2080(simpara)
|
||||
msgid ""
|
||||
"All OpenStack projects have an API service for controlling all the resources"
|
||||
" in the Cloud. In Active / Active mode, the most common setup is to scale-"
|
||||
@ -2123,29 +2149,29 @@ msgid ""
|
||||
"IP (with HAproxy & Keepalived in this setup)."
|
||||
msgstr "すべての OpenStack プロジェクトは、クラウドにあるすべてのリソースを制御するための API サービスを持ちます。アクティブ / アクティブモードの場合、最も一般的なセットアップ環境は、少なくとも 2 つのノードにこれらのサービスをスケールアウトし、(このセットアップで HAproxy と Keepalived を用いて) 負荷分散および仮想 IP を使用します。"
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml2013(emphasis)
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml2084(emphasis)
|
||||
msgid "Configure API OpenStack services"
|
||||
msgstr "OpenStack サービスの API の設定"
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml2015(simpara)
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml2086(simpara)
|
||||
msgid ""
|
||||
"To configure our Cloud using Highly available and scalable API services, we "
|
||||
"need to ensure that:"
|
||||
msgstr "私たちのクラウド環境が高可用性かつスケーラブルな API サービスを使用するよう設定するために、以下の事項を確認する必要があります。"
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml2018(simpara)
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml2089(simpara)
|
||||
msgid "You use Virtual IP when configuring OpenStack Identity endpoints."
|
||||
msgstr "OpenStack Identity エンドポイントを設定するときに仮想 IP を使用します。"
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml2023(simpara)
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml2094(simpara)
|
||||
msgid "All OpenStack configuration files should refer to Virtual IP."
|
||||
msgstr "すべての OpenStack 設定ファイルは仮想 IP を参照すべきです。"
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml2029(emphasis)
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml2100(emphasis)
|
||||
msgid "In case of failure"
|
||||
msgstr "失敗の場合"
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml2031(simpara)
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml2102(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 "
|
||||
@ -2155,11 +2181,11 @@ msgid ""
|
||||
"infrastructure."
|
||||
msgstr "API ポートへの TCP 接続を確立するだけのため、監視チェックは極めてシンプルです。Corosync とリソースエージェントを使用するアクティブ / パッシブモードと比べて、サービスが実際に動作しているかを確認しません。そのため、クラウドのフレームワーク環境における障害を検知するために、すべての OpenStack API は他のツール (例: Nagios) により監視すべきです。"
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml2038(title)
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml2109(title)
|
||||
msgid "Schedulers"
|
||||
msgstr "スケジューラー"
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml2040(simpara)
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml2111(simpara)
|
||||
msgid ""
|
||||
"OpenStack schedulers are used to determine how to dispatch compute, network "
|
||||
"and volume requests. The most common setup is to use RabbitMQ as messaging "
|
||||
@ -2167,100 +2193,100 @@ msgid ""
|
||||
" messaging backend and can scale-out :"
|
||||
msgstr "OpenStack スケジューラーは、コンピュート、ネットワーク、ボリュームのリクエストをどのようにディスパッチするかを決めるために使用されます。最も一般的なセットアップ環境は、このガイドにドキュメント化されたメッセージングシステムとして RabbitMQ を使用することです。これらのサービスはメッセージングのバックエンドに接続され、スケールアウトできます。"
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml2045(simpara)
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml2116(simpara)
|
||||
msgid "nova-scheduler"
|
||||
msgstr "nova-scheduler"
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml2050(simpara)
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml2121(simpara)
|
||||
msgid "nova-conductor"
|
||||
msgstr "nova-conductor"
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml2055(simpara)
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml2126(simpara)
|
||||
msgid "cinder-scheduler"
|
||||
msgstr "cinder-scheduler"
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml2060(simpara)
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml2131(simpara)
|
||||
msgid "neutron-server"
|
||||
msgstr "neutron-server"
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml2065(simpara)
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml2136(simpara)
|
||||
msgid "ceilometer-collector"
|
||||
msgstr "ceilometer-collector"
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml2070(simpara)
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml2141(simpara)
|
||||
msgid "heat-engine"
|
||||
msgstr "heat-engine"
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml2075(simpara)
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml2146(simpara)
|
||||
msgid ""
|
||||
"Please refer to the RabbitMQ section for configure these services with "
|
||||
"multiple messaging servers."
|
||||
msgstr "これらのサービスを複数のメッセージングサービスを用いて設定する方法は、RabbitMQ のセクションを参照してください。"
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml2080(title)
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml2151(title)
|
||||
msgid "Memcached"
|
||||
msgstr "Memcached"
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml2082(simpara)
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml2153(simpara)
|
||||
msgid ""
|
||||
"Most of OpenStack services use an application to offer persistence and store"
|
||||
" ephemeral data (like tokens). Memcached is one of them and can scale-out "
|
||||
"easily without specific trick."
|
||||
msgstr "ほとんどの OpenStack サービスは、永続性を提供し、(トークンのような) 一時的なデータを保存するために、アプリケーションを使用します。memcached は、それらの一つで、特別な工夫をすることなく簡単にスケールアウト可能にできます。"
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml2084(simpara)
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml2155(simpara)
|
||||
msgid ""
|
||||
"To install and configure it, read the <link "
|
||||
"href=\"http://code.google.com/p/memcached/wiki/NewStart\">official "
|
||||
"documentation</link>."
|
||||
msgstr "インストールおよび設定するために、<link href=\"http://code.google.com/p/memcached/wiki/NewStart\">公式ドキュメント</link>を参照します。"
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml2085(simpara)
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml2156(simpara)
|
||||
msgid ""
|
||||
"Memory caching is managed by oslo-incubator so the way to use multiple "
|
||||
"memcached servers is the same for all projects."
|
||||
msgstr "メモリキャッシュは、複数の memcached サーバーを使用する方法がすべてのプロジェクトで同じにするために、Oslo インキュベーターにより管理されています。"
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml2086(simpara)
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml2157(simpara)
|
||||
msgid "Example with two hosts:"
|
||||
msgstr "2 つのホストを用いた例:"
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml2088(simpara)
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml2159(simpara)
|
||||
msgid ""
|
||||
"By default, controller1 handles the caching service but if the host goes "
|
||||
"down, controller2 does the job. For more information about memcached "
|
||||
"installation, see the OpenStack Cloud Administrator Guide."
|
||||
msgstr "デフォルトで、controller1 がキャッシュサービスを処理します。しかし、このホストが停止すると、controller2 がこのジョブを実行します。memcached のインストールに関する詳細は OpenStack クラウド管理者ガイドを参照してください。"
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml2095(title)
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml2166(title)
|
||||
msgid "OpenStack network nodes"
|
||||
msgstr "OpenStack ネットワークノード"
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml2097(simpara)
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml2168(simpara)
|
||||
msgid "OpenStack network nodes contain:"
|
||||
msgstr "OpenStack ネットワークノードは次のものを含みます。"
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml2100(simpara)
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml2171(simpara)
|
||||
msgid "neutron DHCP agent"
|
||||
msgstr "Neutron DHCP エージェント"
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml2105(simpara)
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml2176(simpara)
|
||||
msgid "neutron L2 agent"
|
||||
msgstr "neutron L2 エージェント"
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml2110(simpara)
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml2181(simpara)
|
||||
msgid "Neutron L3 agent"
|
||||
msgstr "neutron L3 エージェント"
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml2115(simpara)
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml2186(simpara)
|
||||
msgid "neutron metadata agent"
|
||||
msgstr "neutron メタデータエージェント"
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml2120(simpara)
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml2191(simpara)
|
||||
msgid "neutron lbaas agent"
|
||||
msgstr "neutron LBaaS エージェント"
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml2126(simpara)
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml2197(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 "
|
||||
@ -2269,11 +2295,11 @@ msgid ""
|
||||
"highly available."
|
||||
msgstr "neutron L2 エージェントは高可用性にする必要がありません。各データ転送ノードにインストールされる必要があります。また、Open vSwitch または Linux Bridge として仮想ネットワークドライバーを制御します。1 つの L2 エージェントをノードごとに実行し、その仮想インターフェースを制御します。これが分散できず、高可用性にできない理由です。"
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml2134(title)
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml2205(title)
|
||||
msgid "Run neutron DHCP agent"
|
||||
msgstr "Neutron DHCP エージェントの実行"
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml2136(simpara)
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml2207(simpara)
|
||||
msgid ""
|
||||
"OpenStack Networking service has a scheduler that lets you run multiple "
|
||||
"agents across nodes. Also, the DHCP agent can be natively highly available. "
|
||||
@ -2282,11 +2308,11 @@ msgid ""
|
||||
"Reference</link>."
|
||||
msgstr "OpenStack Networking Service はノードをまたがり複数のエージェントを実行できるスケジューラーがあります。また、DHCP エージェントはネイティブで高可用性にできます。詳細は <link href=\"http://docs.openstack.org/trunk/config-reference/content/app_demo_multi_dhcp_agents.html\">OpenStack 設定リファレンス</link>を参照してください。"
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml2142(title)
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml2213(title)
|
||||
msgid "Run neutron L3 agent"
|
||||
msgstr "Neutron L3 エージェントの実行"
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml2144(simpara)
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml2215(simpara)
|
||||
msgid ""
|
||||
"The neutron L3 agent is scalable thanks to the scheduler that allows "
|
||||
"distribution of virtual routers across multiple nodes. But there is no "
|
||||
@ -2295,11 +2321,11 @@ msgid ""
|
||||
"mode with Pacemaker. See the Active / Passive section of this guide."
|
||||
msgstr "仮想ルーターを複数のノードに渡り配布できるスケジューラーのおかげで、Neutron L3 エージェントがスケール可能になりました。しかし、これらのルーターを高可用性にする独自の機能はありません。今のところ、Pacemaker のフェイルオーバーモードで Neutron L3 エージェントを実行させる、アクティブ / パッシブのソリューションがあります。このガイドのアクティブ / パッシブのセクションを参照ください。"
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml2153(title)
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml2224(title)
|
||||
msgid "Run neutron metadata agent"
|
||||
msgstr "Neutron メタデータエージェントの実行"
|
||||
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml2155(simpara)
|
||||
#: ./doc/high-availability-guide/bk-ha-guide.xml2226(simpara)
|
||||
msgid ""
|
||||
"There is no native feature to make this service highly available. At this "
|
||||
"time, the Active / Passive solution exists to run the neutron metadata agent"
|
||||
|
||||
@ -4,8 +4,8 @@
|
||||
msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: OpenStack Manuals\n"
|
||||
"POT-Creation-Date: 2014-05-26 01:46+0000\n"
|
||||
"PO-Revision-Date: 2014-05-26 05:50+0000\n"
|
||||
"POT-Creation-Date: 2014-05-27 02:14+0000\n"
|
||||
"PO-Revision-Date: 2014-05-27 01:51+0000\n"
|
||||
"Last-Translator: Tomoyuki KATO <tomo@dream.daynight.jp>\n"
|
||||
"Language-Team: Japanese (http://www.transifex.com/projects/p/openstack-manuals-i18n/language/ja/)\n"
|
||||
"MIME-Version: 1.0\n"
|
||||
@ -35,7 +35,7 @@ msgid ""
|
||||
"<filename>/etc/<replaceable>SERVICE</replaceable>/policy.json</filename> "
|
||||
"file. For example, the policy defined for OpenStack Identity service is "
|
||||
"defined in the <filename>/etc/keystone/policy.json</filename> file."
|
||||
msgstr ""
|
||||
msgstr "OpenStack Identity は、プロジェクトにユーザーのロールを定義します。しかし、そのロールの意味を定義することは、完全に個々のサービス次第です。これは、サービスのポリシーとして参照されます。各ロールの権限の詳細を取得する場合、各サービスの <filename>/etc/<replaceable>SERVICE</replaceable>/policy.json</filename> ファイルで利用可能な <filename>policy.json</filename> ファイルを参照してください。例えば、OpenStack Identity に定義されているポリシーは、<filename>/etc/keystone/policy.json</filename> ファイルに定義されています。"
|
||||
|
||||
#: ./doc/user-guide-admin/section_dashboard_admin_manage_roles.xml24(title)
|
||||
msgid "Create a role"
|
||||
@ -278,7 +278,7 @@ msgid ""
|
||||
"<link href=\"http://docs.openstack.org/admin-guide-"
|
||||
"cloud/content/\"><citetitle>OpenStack Cloud Administrator "
|
||||
"Guide</citetitle></link>."
|
||||
msgstr ""
|
||||
msgstr "フレーバーは、インスタンスを起動するために使用できるコンピュートホストを決めることもできます。フレーバーのカスタマイズの詳細は、<link href=\"http://docs.openstack.org/admin-guide-cloud/content/\"><citetitle>OpenStack Cloud Administrator Guide</citetitle></link> を参照してください。"
|
||||
|
||||
#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml19(para)
|
||||
#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml14(para)
|
||||
@ -451,7 +451,7 @@ msgid ""
|
||||
"assigned, with 256 MB memory, no disk space, and one VCPU. The rxtx-factor "
|
||||
"indicates the slice of bandwidth that the instances with this flavor can use"
|
||||
" (through the Virtual Interface (vif) creation in the hypervisor)."
|
||||
msgstr ""
|
||||
msgstr "これは、割り当て ID を自動取得し、256MB メモリ、ディスクなし、1 仮想 CPU を持つ、パブリックな「extra tiny」フレーバーを作成するために、追加のオプションパラメーターを用いた例です。rxtx-factor は、このフレーバーのインスタンスが (ハイパーバイザーでの仮想インターフェースの作成により) 使用できる帯域幅を意味します。"
|
||||
|
||||
#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml129(para)
|
||||
msgid ""
|
||||
@ -590,7 +590,7 @@ msgid ""
|
||||
"procedures, refer to the <citetitle>Manage IP Addresses</citetitle> section "
|
||||
"in the <link href=\"http://docs.openstack.org/user-"
|
||||
"guide/content/\"><citetitle>OpenStack End User Guide</citetitle></link>."
|
||||
msgstr ""
|
||||
msgstr "デフォルトで、管理ユーザーとエンドユーザーどちらも、プロジェクトとインスタンスに Floating IP アドレスを割り当てられます。<filename>/etc/nova/policy.json</filename> ファイルを更新することにより、IP アドレスを管理するユーザー権限を変更できます。Floating IP の基本的な手順は、<link href=\"http://docs.openstack.org/user-guide/content/\"><citetitle>OpenStack End User Guide</citetitle></link> の <citetitle>Manage IP Addresses</citetitle> セクションを参照してください。"
|
||||
|
||||
#: ./doc/user-guide-admin/section_cli_nova_floating_ips.xml23(para)
|
||||
msgid ""
|
||||
@ -1157,7 +1157,7 @@ msgid ""
|
||||
"To assign a host to the aggregate, click <guilabel>+</guilabel> for the "
|
||||
"host. The host moves from the <guilabel>All available hosts</guilabel> list "
|
||||
"to the <guilabel>Selected hosts</guilabel> list."
|
||||
msgstr ""
|
||||
msgstr "ホストにアグリゲートを割り当てるために、ホストの <guilabel>+</guilabel> をクリックします。ホストが、<guilabel>すべての利用可能なホスト</guilabel>一覧から<guilabel>選択済みホスト</guilabel>一覧に移動します。"
|
||||
|
||||
#: ./doc/user-guide-admin/section_dashboard_admin_manage_host_aggregates.xml96(para)
|
||||
msgid ""
|
||||
@ -1785,7 +1785,7 @@ msgid ""
|
||||
"You can use the <code>allow_same_net_traffic</code> option in the "
|
||||
"<filename>/etc/nova/nova.conf</filename> file to globally control whether "
|
||||
"the rules apply to hosts which share a network."
|
||||
msgstr ""
|
||||
msgstr "ネットワークを共有しているホストに適用されるルールを全体的に制御するために、<filename>/etc/nova/nova.conf</filename> ファイルで <code>allow_same_net_traffic</code> オプションを使用できます。"
|
||||
|
||||
#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml27(para)
|
||||
msgid "If set to:"
|
||||
@ -2967,14 +2967,14 @@ msgid ""
|
||||
"alerts. Data can be collected by notifications sent by existing OpenStack "
|
||||
"components (for example, usage events emitted from Compute) or by polling "
|
||||
"the infrastructure (for example, libvirt)."
|
||||
msgstr ""
|
||||
msgstr "Telemetry モジュールは、OpenStack ベースのクラウドに関するユーザーレベルの使用状況データを提供します。顧客への課金、システム監視、アラートなどに使用できます。データは、既存の OpenStack コンポーネント (例えば、Compute からの使用状況のイベント) により送信された通知、またはインフラストラクチャー (例えば、libvirt) によるポーリングにより収集できます。"
|
||||
|
||||
#: ./doc/user-guide-admin/section_dashboard_admin_view_cloud_resources.xml13(para)
|
||||
msgid ""
|
||||
"You can only view metering statistics on the dashboard (available only to "
|
||||
"administrators). The Telemetry service must be set up and administered "
|
||||
"through the <placeholder-1/> command-line interface (CLI)."
|
||||
msgstr ""
|
||||
msgstr "ダッシュボードでメータリングの統計情報を表示のみできます (管理者のみ利用可能)。Telemetry サービスがセットアップされ、<placeholder-1/> コマンドラインインターフェースにより管理されている必要があります。"
|
||||
|
||||
#: ./doc/user-guide-admin/section_dashboard_admin_view_cloud_resources.xml17(para)
|
||||
msgid ""
|
||||
@ -3012,14 +3012,14 @@ msgstr "プロジェクトごとの受信および送信の使用量を表示す
|
||||
msgid ""
|
||||
"<guilabel>Global Object Storage Usage</guilabel> tab to view incoming and "
|
||||
"outgoing storage bytes per tenant (project)."
|
||||
msgstr ""
|
||||
msgstr "プロジェクトごとのストレージの受信および送信バイト数を表示するための、<guilabel>全体オブジェクトストレージ使用状況</guilabel>タブ。"
|
||||
|
||||
#: ./doc/user-guide-admin/section_dashboard_admin_view_cloud_resources.xml35(para)
|
||||
msgid ""
|
||||
"<guilabel>Global Network Usage</guilabel> tab to view duration and creation "
|
||||
"requests for networks, subnets, routers, ports, and floating IPs, per tenant"
|
||||
" (project)."
|
||||
msgstr ""
|
||||
msgstr "プロジェクトごとのネットワーク、サブネット、ルーター、ポート、Floating IP の使用期間および作成リクエスト数を表示するための、<guilabel>ネットワーク全体使用量</guilabel>タブ。"
|
||||
|
||||
#: ./doc/user-guide-admin/section_dashboard_admin_view_cloud_resources.xml38(para)
|
||||
msgid ""
|
||||
@ -3027,7 +3027,7 @@ msgid ""
|
||||
"defined metrics. You group by project, define the value type (min, max, avg,"
|
||||
" or sum), and specify the time period (or even use a calendar to define a "
|
||||
"date range)."
|
||||
msgstr ""
|
||||
msgstr "ユーザー定義の測定項目による他系列の折れ線グラフを表示するための、<guilabel>統計</guilabel>タブ。プロジェクトによるグループ化、値の種類の定義 (最小、最大、平均、合計)、対象期間の指定 (日付の期間を定義するためにカレンダーを使用) をできます。"
|
||||
|
||||
#: ./doc/user-guide-admin/section_dashboard_admin_view_cloud_resources.xml29(para)
|
||||
msgid "Click the: <placeholder-1/>"
|
||||
|
||||
Loading…
Reference in New Issue
Block a user