openstack/openstack-manuals
Code Issues Proposed changes

Imported Translations from Transifex

Browse Source 
Change-Id: I4123e98ab80bd09ff304dff91a78118ce9cb995e
This commit is contained in:
OpenStack Proposal Bot 2014-08-07 06:04:50 +00:00
parent 30e4b3a0dd
commit 5659c36a2b
3 changed files with 9 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
doc/arch-design/locale/arch-design.pot
View File

@ -1,7 +1,7 @@
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"POT-Creation-Date: 2014-08-06 06:08+0000\n"
"POT-Creation-Date: 2014-08-07 06:03+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"
@ -1978,7 +1978,7 @@ msgid "Telemetry module"
msgstr ""
#: ./doc/arch-design/network_focus/section_prescriptive_examples_network_focus.xml:69(para)
msgid "Beyond the normal Identity, Compute, Image Service and Object Storage components, the Orchestration module is a recommended component to handle properly scaling the workloads to adjust to demand. The Telemetry module will also need to be included in the design due to the requirement for auto-scaling. Web services tend to be bursty in load, have very defined peak and valley usage patterns and, as a result, benefit from automatic scaling of instances based upon traffic. At a network level, a split network configuration will work well with databases residing on private tenant networks since these do not emit a large quantity of broadcast traffic and may need to interconnect to some databases for content."
msgid "Beyond the normal Identity, Compute, Image Service and Object Storage components, the Orchestration module is a recommended component to handle properly scaling the workloads to adjust to demand. Due to the requirement for auto-scaling, the design includes the Telemetry module. Web services tend to be bursty in load, have very defined peak and valley usage patterns and, as a result, benefit from automatic scaling of instances based upon traffic. At a network level, a split network configuration will work well with databases residing on private tenant networks since these do not emit a large quantity of broadcast traffic and may need to interconnect to some databases for content."
msgstr ""
#: ./doc/arch-design/network_focus/section_prescriptive_examples_network_focus.xml:84(title)

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

@ -1,7 +1,7 @@
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"POT-Creation-Date: 2014-07-29 06:09+0000\n"
"POT-Creation-Date: 2014-08-07 06:04+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"
@ -466,7 +466,7 @@ msgid "Other ways to provide a highly available database"
msgstr ""
#: ./doc/high-availability-guide/ha_aa_db/section_other_ways_to_provide_a_highly_available_database.xml:9(para)
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."
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 PostgreSQL, which has its own replication, or another database HA option."
msgstr ""
#: ./doc/high-availability-guide/ha_aa_network/section_run_neutron_l3_agent.xml:7(title)

10
doc/high-availability-guide/locale/ja.po
View File

@ -4,9 +4,9 @@
msgid ""
msgstr ""
"Project-Id-Version: OpenStack Manuals\n"
"POT-Creation-Date: 2014-07-31 21:35+0000\n"
"PO-Revision-Date: 2014-07-29 14:41+0000\n"
"Last-Translator: Tomoyuki KATO <tomo@dream.daynight.jp>\n"
"POT-Creation-Date: 2014-08-06 13:08+0000\n"
"PO-Revision-Date: 2014-08-06 06:12+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"
@ -642,9 +642,9 @@ msgid ""
"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 "
"with Galera. You also have the option to use PostgreSQL, which has its own "
"replication, or another database HA option."
msgstr "MySQL と Galera の併用がデータベースを HA 化する唯一の方法ではありません。MariaDB (<link href=\"https://mariadb.org/\">https://mariadb.org/</link>) や Percona (<link href=\"http://www.percona.com/\">http://www.percona.com/</link>) も Galera と併用できます。独自のレプリケーション機能を持つ Postgres や他のデータベースの HA オプションを使用するという選択肢もあります。"
msgstr ""
#: ./doc/high-availability-guide/ha_aa_network/section_run_neutron_l3_agent.xml7(title)
msgid "Run neutron L3 agent"