openstack/openstack-manuals
Code Issues Proposed changes

Imported Translations from Transifex

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

Change-Id: I014bb4508636dbed6ee7dba28b4f26d43f0ed1c3
This commit is contained in:
OpenStack Proposal Bot 2015-02-09 06:12:37 +00:00
parent d9d86905b0
commit a43c87cb13
4 changed files with 58 additions and 54 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -1,7 +1,7 @@
msgid "" msgid ""
msgstr "" msgstr ""
"Project-Id-Version: PACKAGE VERSION\n" "Project-Id-Version: PACKAGE VERSION\n"
"POT-Creation-Date: 2015-02-07 06:11+0000\n" "POT-Creation-Date: 2015-02-09 06:10+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n" "Language-Team: LANGUAGE <LL@li.org>\n"
@ -6296,13 +6296,13 @@ msgstr ""
#. When image changes, this message will be marked fuzzy or untranslated for you. #. When image changes, this message will be marked fuzzy or untranslated for you.
#. It doesn't matter what you translate it to: it's not used at all. #. It doesn't matter what you translate it to: it's not used at all.
#: ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:713(None) #: ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:720(None)
msgid "@@image: '../../common/figures/ml2_without_l2pop_full_mesh.png'; md5=881485c0686f20b82967d5b817932952" msgid "@@image: '../../common/figures/ml2_without_l2pop_full_mesh.png'; md5=881485c0686f20b82967d5b817932952"
msgstr "" msgstr ""
#. When image changes, this message will be marked fuzzy or untranslated for you. #. When image changes, this message will be marked fuzzy or untranslated for you.
#. It doesn't matter what you translate it to: it's not used at all. #. It doesn't matter what you translate it to: it's not used at all.
#: ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:725(None) #: ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:732(None)
msgid "@@image: '../../common/figures/ml2_without_l2pop_partial_mesh.png'; md5=66fe83560a3e1880ffe3a85d80538f83" msgid "@@image: '../../common/figures/ml2_without_l2pop_partial_mesh.png'; md5=66fe83560a3e1880ffe3a85d80538f83"
msgstr "" msgstr ""
@ -6658,71 +6658,75 @@ msgstr ""
msgid "The Modular Layer 2 plug-in allows OpenStack Networking to simultaneously utilize the variety of layer 2 networking technologies found in complex real-world data centers. It currently includes drivers for the local, flat, VLAN, GRE and VXLAN network types and works with the existing <emphasis>Open vSwitch</emphasis>, <emphasis>Linux Bridge </emphasis>, and <emphasis>HyperV</emphasis> L2 agents. The <emphasis>ML2</emphasis> plug-in can be extended through mechanism drivers, allowing multiple mechanisms to be used simultaneously. This section describes different <emphasis>ML2</emphasis> plug-in and agent configurations with different type drivers and mechanism drivers." msgid "The Modular Layer 2 plug-in allows OpenStack Networking to simultaneously utilize the variety of layer 2 networking technologies found in complex real-world data centers. It currently includes drivers for the local, flat, VLAN, GRE and VXLAN network types and works with the existing <emphasis>Open vSwitch</emphasis>, <emphasis>Linux Bridge </emphasis>, and <emphasis>HyperV</emphasis> L2 agents. The <emphasis>ML2</emphasis> plug-in can be extended through mechanism drivers, allowing multiple mechanisms to be used simultaneously. This section describes different <emphasis>ML2</emphasis> plug-in and agent configurations with different type drivers and mechanism drivers."
msgstr "" msgstr ""
#: ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:693(para) #: ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:694(para)
msgid "Currently, there is no need to define <parameter>SEGMENTATION_ID</parameter> network provider attribute for GRE and VXLAN network types. The choice can be delegated to Networking, in such case ML2 plug-in tries to find a network in tenant network pools which respects specified provider network attributes."
msgstr ""
#: ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:700(para)
msgid "Previously, Networking deployments were only able to use the plug-in that had been selected at implementation time. For example, a deployment running the Open vSwitch plug-in was only able to use Open vSwitch exclusively; it wasn't possible to simultaneously run another plug-in such as Linux Bridge. This was found to be a limitation in environments with heterogeneous requirements." msgid "Previously, Networking deployments were only able to use the plug-in that had been selected at implementation time. For example, a deployment running the Open vSwitch plug-in was only able to use Open vSwitch exclusively; it wasn't possible to simultaneously run another plug-in such as Linux Bridge. This was found to be a limitation in environments with heterogeneous requirements."
msgstr "" msgstr ""
#: ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:699(para) #: ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:706(para)
msgid "Disabling a ML2 type driver and re-enabling it later may lead to database inconsistencies if ML2 is reconfigured without support for that type." msgid "Disabling a ML2 type driver and re-enabling it later may lead to database inconsistencies if ML2 is reconfigured without support for that type."
msgstr "" msgstr ""
#: ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:703(title) #: ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:710(title)
msgid "ML2 with L2 population mechanism driver" msgid "ML2 with L2 population mechanism driver"
msgstr "" msgstr ""
#: ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:704(para) #: ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:711(para)
msgid "The L2 Population driver enables broadcast, multicast, and unicast traffic to scale out on large overlay networks. This traffic is sent to the relevant agent via encapsulation as a targeted unicast." msgid "The L2 Population driver enables broadcast, multicast, and unicast traffic to scale out on large overlay networks. This traffic is sent to the relevant agent via encapsulation as a targeted unicast."
msgstr "" msgstr ""
#: ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:707(para) #: ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:714(para)
msgid "Current <emphasis>Open vSwitch</emphasis> and <emphasis>Linux Bridge</emphasis> tunneling implementations broadcast to every agent, even if they don't host the corresponding network as illustrated below." msgid "Current <emphasis>Open vSwitch</emphasis> and <emphasis>Linux Bridge</emphasis> tunneling implementations broadcast to every agent, even if they don't host the corresponding network as illustrated below."
msgstr "" msgstr ""
#: ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:716(para) #: ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:723(para)
msgid "As broadcast emulation on overlay is costly, it may be better to avoid its use for MAC learning and ARP resolution. This supposes the use of proxy ARP on the agent to answer VM requests, and to populate forwarding table. Currently only the <emphasis>Linux Bridge</emphasis> Agent implements an ARP proxy. The pre-population limits L2 broadcasts in overlay, however it may anyway be necessary to provide broadcast emulation. This is achieved by broadcasting packets via unicast only to the relevant agents as illustrated below.<placeholder-1/>The partial-mesh is available with the <emphasis>Open vSwitch</emphasis> and <emphasis>Linux Bridge</emphasis> agents. The following scenarios will use the L2 population mechanism driver with an <emphasis>Open vSwitch</emphasis> agent and a <emphasis>Linux Bridge</emphasis> agent. Enable the l2 population driver by adding it to the list of mechanism drivers. In addition, a tunneling driver must be selected. Supported options are GRE, VXLAN, or a combination of both. Configuration settings are enabled in <filename>ml2_conf.ini</filename>:" msgid "As broadcast emulation on overlay is costly, it may be better to avoid its use for MAC learning and ARP resolution. This supposes the use of proxy ARP on the agent to answer VM requests, and to populate forwarding table. Currently only the <emphasis>Linux Bridge</emphasis> Agent implements an ARP proxy. The pre-population limits L2 broadcasts in overlay, however it may anyway be necessary to provide broadcast emulation. This is achieved by broadcasting packets via unicast only to the relevant agents as illustrated below.<placeholder-1/>The partial-mesh is available with the <emphasis>Open vSwitch</emphasis> and <emphasis>Linux Bridge</emphasis> agents. The following scenarios will use the L2 population mechanism driver with an <emphasis>Open vSwitch</emphasis> agent and a <emphasis>Linux Bridge</emphasis> agent. Enable the l2 population driver by adding it to the list of mechanism drivers. In addition, a tunneling driver must be selected. Supported options are GRE, VXLAN, or a combination of both. Configuration settings are enabled in <filename>ml2_conf.ini</filename>:"
msgstr "" msgstr ""
#: ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:740(title) #: ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:747(title)
msgid "Scenario 1: L2 population with Open vSwitch agent" msgid "Scenario 1: L2 population with Open vSwitch agent"
msgstr "" msgstr ""
#: ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:741(para) #: ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:748(para)
msgid "Enable the l2 population extension in the <emphasis>Open vSwitch</emphasis> agent, and configure the <placeholder-1/> and <placeholder-2/> parameters in the <filename>ml2_conf.ini</filename> file:" msgid "Enable the l2 population extension in the <emphasis>Open vSwitch</emphasis> agent, and configure the <placeholder-1/> and <placeholder-2/> parameters in the <filename>ml2_conf.ini</filename> file:"
msgstr "" msgstr ""
#: ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:745(replaceable) ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:758(replaceable) #: ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:752(replaceable) ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:765(replaceable)
msgid "192.168.1.10" msgid "192.168.1.10"
msgstr "" msgstr ""
#: ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:748(replaceable) #: ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:755(replaceable)
msgid "GRE" msgid "GRE"
msgstr "" msgstr ""
#: ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:748(replaceable) #: ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:755(replaceable)
msgid "VXLAN" msgid "VXLAN"
msgstr "" msgstr ""
#: ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:752(title) #: ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:759(title)
msgid "Scenario 2: L2 population with <emphasis>Linux Bridge</emphasis> agent" msgid "Scenario 2: L2 population with <emphasis>Linux Bridge</emphasis> agent"
msgstr "" msgstr ""
#: ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:753(para) #: ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:760(para)
msgid "Enable the l2 population extension on the <emphasis>Linux Bridge</emphasis> agent. Enable VXLAN and configure the local_ip parameter in <filename>ml2_conf.ini</filename>." msgid "Enable the l2 population extension on the <emphasis>Linux Bridge</emphasis> agent. Enable VXLAN and configure the local_ip parameter in <filename>ml2_conf.ini</filename>."
msgstr "" msgstr ""
#: ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:762(title) #: ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:769(title)
msgid "Enable security group API" msgid "Enable security group API"
msgstr "" msgstr ""
#: ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:763(para) #: ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:770(para)
msgid "The ML2 plug-in can concurrently support different L2 agents (or other mechanisms) with different configuration files, so each L2 agent configuration file (such as <filename>ovs_neutron_plugin.ini</filename> or <filename>linuxbridge_conf.ini</filename>) should contain the appropriate <placeholder-1/> value for that agent in addition to setting <placeholder-2/> to <literal>True</literal> (which is the default)." msgid "The ML2 plug-in can concurrently support different L2 agents (or other mechanisms) with different configuration files, so each L2 agent configuration file (such as <filename>ovs_neutron_plugin.ini</filename> or <filename>linuxbridge_conf.ini</filename>) should contain the appropriate <placeholder-1/> value for that agent in addition to setting <placeholder-2/> to <literal>True</literal> (which is the default)."
msgstr "" msgstr ""
#: ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:772(para) #: ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:779(para)
msgid "The <placeholder-1/> value in the API server's <filename>ml2_conf.ini</filename> file does not matter." msgid "The <placeholder-1/> value in the API server's <filename>ml2_conf.ini</filename> file does not matter."
msgstr "" msgstr ""
#: ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:775(para) #: ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:782(para)
msgid "To disable the securitygroup API, edit the <filename>ml2_conf.ini</filename> file on the API server, and <filename>ovs_neutron_plugin.ini</filename>, <filename>linuxbridge_conf.ini</filename> or other L2 agent configuration files on the agent servers :" msgid "To disable the securitygroup API, edit the <filename>ml2_conf.ini</filename> file on the API server, and <filename>ovs_neutron_plugin.ini</filename>, <filename>linuxbridge_conf.ini</filename> or other L2 agent configuration files on the agent servers :"
msgstr "" msgstr ""

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

@ -1,7 +1,7 @@
msgid "" msgid ""
msgstr "" msgstr ""
"Project-Id-Version: PACKAGE VERSION\n" "Project-Id-Version: PACKAGE VERSION\n"
"POT-Creation-Date: 2015-02-05 06:21+0000\n" "POT-Creation-Date: 2015-02-09 06:10+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n" "Language-Team: LANGUAGE <LL@li.org>\n"
@ -262,7 +262,7 @@ msgid "Multi-site"
msgstr "" msgstr ""
#: ./doc/arch-design/ch_multi_site.xml:9(para) #: ./doc/arch-design/ch_multi_site.xml:9(para)
msgid "A multi-site OpenStack environment is one in which services located in more than one data center are used to provide the overall solution. Usage requirements of different multi-site clouds may vary widely, however they share some common needs. OpenStack is capable of running in a multi-region configuration allowing some parts of OpenStack to effectively manage a grouping of sites as a single cloud. With some careful planning in the design phase, OpenStack can act as an excellent multi-site cloud solution for a multitude of needs." msgid "A multi-site OpenStack environment is one in which services, located in more than one data center, are used to provide the overall solution. Usage requirements of different multi-site clouds may vary widely, but they share some common needs. OpenStack is capable of running in a multi-region configuration. This enables some parts of OpenStack to effectively manage a group of sites as a single cloud. With careful planning in the design phase, OpenStack can act as an excellent multi-site cloud solution for a multitude of needs."
msgstr "" msgstr ""
#: ./doc/arch-design/ch_multi_site.xml:19(para) #: ./doc/arch-design/ch_multi_site.xml:19(para)

56
doc/arch-design/locale/zh_CN.po
View File

@ -8,8 +8,8 @@
msgid "" msgid ""
msgstr "" msgstr ""
"Project-Id-Version: OpenStack Manuals\n" "Project-Id-Version: OpenStack Manuals\n"
"POT-Creation-Date: 2015-02-08 04:29+0000\n" "POT-Creation-Date: 2015-02-09 04:30+0000\n"
"PO-Revision-Date: 2015-02-08 04:11+0000\n" "PO-Revision-Date: 2015-02-09 03:40+0000\n"
"Last-Translator: johnwoo_lee <lijiangsheng1@gmail.com>\n" "Last-Translator: johnwoo_lee <lijiangsheng1@gmail.com>\n"
"Language-Team: Chinese (China) (http://www.transifex.com/projects/p/openstack-manuals-i18n/language/zh_CN/)\n" "Language-Team: Chinese (China) (http://www.transifex.com/projects/p/openstack-manuals-i18n/language/zh_CN/)\n"
"MIME-Version: 1.0\n" "MIME-Version: 1.0\n"
@ -454,15 +454,15 @@ msgstr "多区域"
#: ./doc/arch-design/ch_multi_site.xml9(para) #: ./doc/arch-design/ch_multi_site.xml9(para)
msgid "" msgid ""
"A multi-site OpenStack environment is one in which services located in more " "A multi-site OpenStack environment is one in which services, located in more"
"than one data center are used to provide the overall solution. Usage " " than one data center, are used to provide the overall solution. Usage "
"requirements of different multi-site clouds may vary widely, however they " "requirements of different multi-site clouds may vary widely, but they share "
"share some common needs. OpenStack is capable of running in a multi-region " "some common needs. OpenStack is capable of running in a multi-region "
"configuration allowing some parts of OpenStack to effectively manage a " "configuration. This enables some parts of OpenStack to effectively manage a "
"grouping of sites as a single cloud. With some careful planning in the " "group of sites as a single cloud. With careful planning in the design phase,"
"design phase, OpenStack can act as an excellent multi-site cloud solution " " OpenStack can act as an excellent multi-site cloud solution for a multitude"
"for a multitude of needs." " of needs."
msgstr "一个多区域openstack环境是指它的服务分布在多个数据中心来提供整体的服务.不同的多区域云可能在使用要求上区别会很大,然而它们还是有一些共同点的.openstack可以运行在多区域环境下,允许某部分服务有效地像管理一个单区域的云一样来管理着由多个区域组成的群组.通过在设计阶段仔细计划,面对不同的需求,openstack可以是一个多区域云的完美解决方案" msgstr ""
#: ./doc/arch-design/ch_multi_site.xml19(para) #: ./doc/arch-design/ch_multi_site.xml19(para)
msgid "" msgid ""
@ -1774,7 +1774,7 @@ msgid ""
"also benefit by possibly being able to forecast growth per region, rather " "also benefit by possibly being able to forecast growth per region, rather "
"than expanding the capacity of all regions simultaneously, therefore " "than expanding the capacity of all regions simultaneously, therefore "
"maximizing the cost-effectiveness of the multi-site design." "maximizing the cost-effectiveness of the multi-site design."
msgstr "" msgstr "Telemetry也会部署到每个region中，虽然每个region的增长可能不一样或者使用的频率也不同。Ceilometer将运行在每个region中的监测数据，然后回报到中心地点。这在OpenStack环境中对于最终用户也好，对于系统管理员也好，都有很大的用处，使最终用户根据某些局部的负载高于其他地方做出决定而成为可能，然后采取相应的措施。使系统管理员在每个region预测增长成为可能，而不是去盲目的同等看待所有region而去扩展它们，因此对于多区域设计是最大化的节省资源。"
#: ./doc/arch-design/multi_site/section_prescriptive_examples_multi_site.xml64(para) #: ./doc/arch-design/multi_site/section_prescriptive_examples_multi_site.xml64(para)
msgid "" msgid ""
@ -1787,7 +1787,7 @@ msgid ""
"one of the regions causing an outage in service. It also has the added " "one of the regions causing an outage in service. It also has the added "
"benefit of being able to run a central storage repository as a primary cache" "benefit of being able to run a central storage repository as a primary cache"
" for distributing content to each of the regions." " for distributing content to each of the regions."
msgstr "" msgstr "运行此类基础设施的一个关键决定是是否提供冗余模式。在此配置中有两类冗余和高可用模式需要被实现。第一类围绕中心化OpenStack组件的可用性，Keystone会基于三个中心化的数据中心而形成高可用，而成为中心化的OpenStack组件。这会防止任何的region失效而导致服务不可用。这也会为在每个region运行着中央存储仓库作为主要缓存，用于分发内容，带来额外的好处。"
#: ./doc/arch-design/multi_site/section_prescriptive_examples_multi_site.xml75(para) #: ./doc/arch-design/multi_site/section_prescriptive_examples_multi_site.xml75(para)
msgid "" msgid ""
@ -1795,7 +1795,7 @@ msgid ""
" data center in each of the edge regional locations will house a second " " data center in each of the edge regional locations will house a second "
"region near the first. This ensures that the application will not suffer " "region near the first. This ensures that the application will not suffer "
"degraded performance in terms of latency and availability." "degraded performance in terms of latency and availability."
msgstr "" msgstr "第二类容易是边缘数据中心本身。在每个边缘region地带的第二个数据中心会在靠近第一个region边上承载起第二个region的功用。这确保应用不会遭受延迟和可用性方面的性能下降。"
#: ./doc/arch-design/multi_site/section_prescriptive_examples_multi_site.xml80(para) #: ./doc/arch-design/multi_site/section_prescriptive_examples_multi_site.xml80(para)
msgid "" msgid ""
@ -1814,7 +1814,7 @@ msgid ""
" 24/7 basis. The company has typical 2-tier architecture with a web front-" " 24/7 basis. The company has typical 2-tier architecture with a web front-"
"end servicing the customer requests and a NoSQL database back end storing " "end servicing the customer requests and a NoSQL database back end storing "
"the information." "the information."
msgstr "" msgstr "在脑子里想着一个大型扩展的web应用被设计为遵循云的原则。应用被设计为在应用商店中7*24的提供服务，公司拥有典型的2层架构，前端是用户需求的web服务，后端是用NoSQL数据库存放信息。"
#: ./doc/arch-design/multi_site/section_prescriptive_examples_multi_site.xml97(para) #: ./doc/arch-design/multi_site/section_prescriptive_examples_multi_site.xml97(para)
msgid "" msgid ""
@ -1822,7 +1822,7 @@ msgid ""
"providersusually due to the fact these applications were running out of a " "providersusually due to the fact these applications were running out of a "
"single geographical location. The design therefore should mitigate the " "single geographical location. The design therefore should mitigate the "
"chance of a single site causing an outage for their business." "chance of a single site causing an outage for their business."
msgstr "" msgstr "最后，经常由于一些因素他们的应用运行在单个地理位置,主要的公有云提供者因此会停止一些服务。因此设计中要考虑如何降低由于单个站点引起的中断业务的几率。"
#: ./doc/arch-design/multi_site/section_prescriptive_examples_multi_site.xml102(para) #: ./doc/arch-design/multi_site/section_prescriptive_examples_multi_site.xml102(para)
#: ./doc/arch-design/generalpurpose/section_prescriptive_example_general_purpose.xml30(para) #: ./doc/arch-design/generalpurpose/section_prescriptive_example_general_purpose.xml30(para)
@ -1843,7 +1843,7 @@ msgid ""
"services, Identity, Orchestration, Telemetry, Image Service and Object " "services, Identity, Orchestration, Telemetry, Image Service and Object "
"Storage will be installed centrallywith nodes in each of the region " "Storage will be installed centrallywith nodes in each of the region "
"providing a redundant OpenStack Controller plane throughout the globe." "providing a redundant OpenStack Controller plane throughout the globe."
msgstr "" msgstr "运行着OpenStack控制器服务的：网络服务、GUI界面、块存储以及计算服务，都运行在每三个region的本地。其他的服务：认证、Orchestration、Telemetry、镜像服务以及对象存储会安装到每个region的中心节点，通过全局来提供冗余的OpenStack控制器。"
#: ./doc/arch-design/multi_site/section_prescriptive_examples_multi_site.xml120(para) #: ./doc/arch-design/multi_site/section_prescriptive_examples_multi_site.xml120(para)
#: ./doc/arch-design/generalpurpose/section_prescriptive_example_general_purpose.xml44(para) #: ./doc/arch-design/generalpurpose/section_prescriptive_example_general_purpose.xml44(para)
@ -1898,14 +1898,14 @@ msgid ""
"data on a globally available swift container. according to the usage and " "data on a globally available swift container. according to the usage and "
"load on the database serveradditional shards will be provisioned according " "load on the database serveradditional shards will be provisioned according "
"to the thresholds defined in Telemetry." "to the thresholds defined in Telemetry."
msgstr "" msgstr "另外一个自动伸缩的Heat模板会用于部署分布式MongoDB shard，在全部的三个地点存储全局可用的swift容器数据。基于数据库服务所使用的和负载，以及Telemetry定义的阀值，来决定是否增加额外的shard。"
#: ./doc/arch-design/multi_site/section_prescriptive_examples_multi_site.xml163(para) #: ./doc/arch-design/multi_site/section_prescriptive_examples_multi_site.xml163(para)
msgid "" msgid ""
"The reason that three regions were selected here was because of the fear of " "The reason that three regions were selected here was because of the fear of "
"having abnormal load on a single region in the event of a failure. Two data " "having abnormal load on a single region in the event of a failure. Two data "
"center would have been sufficient had the requirements been met." "center would have been sufficient had the requirements been met."
msgstr "" msgstr "这里选择三个region的原因是由于担心偶然的异常负载在单个region会引发失效。两个数据中心足够可以满足需求。"
#: ./doc/arch-design/multi_site/section_prescriptive_examples_multi_site.xml167(para) #: ./doc/arch-design/multi_site/section_prescriptive_examples_multi_site.xml167(para)
msgid "" msgid ""
@ -1916,7 +1916,7 @@ msgid ""
"appropriate built-in hooks into the OpenStack cloudwhereas the other tools " "appropriate built-in hooks into the OpenStack cloudwhereas the other tools "
"were external and not native to OpenStack. In additionsince this deployment " "were external and not native to OpenStack. In additionsince this deployment "
"scenario was relatively straight forwardthe external tools were not needed." "scenario was relatively straight forwardthe external tools were not needed."
msgstr "" msgstr "这里用到Orchestration是由于自动伸缩的内部功能和偶然增长的负载后的自动复原功能。另外一些配置管理工具，如Puppet或Chef也会在此场景下用到，但是不会被选择用于Orchestration，在OpenStack云中它们做不到内部的钩子，也不是OpenStack本身的工具。此外，其实相对简单的场景根本用不到这些额外的工具。"
#: ./doc/arch-design/multi_site/section_prescriptive_examples_multi_site.xml176(para) #: ./doc/arch-design/multi_site/section_prescriptive_examples_multi_site.xml176(para)
msgid "" msgid ""
@ -1926,7 +1926,7 @@ msgid ""
"could also have been used including the handling of replicationbut were not " "could also have been used including the handling of replicationbut were not "
"chosen, because Object Storage is already an intricate part of the " "chosen, because Object Storage is already an intricate part of the "
"infrastructureand proven solution." "infrastructureand proven solution."
msgstr "" msgstr "OpenStack对象存储在这里的使用，是为镜像服务提供后端支撑，而镜像存储最合适的解决方案就是全局的分布式存储解决方案，而对象存储恰恰满足其自身的复制机制。本土的解决方案也已经被使用，包括复制的处理，但都没有选择，因为对象存储已经是基础设施和成熟的解决方案的复杂部分。"
#: ./doc/arch-design/multi_site/section_prescriptive_examples_multi_site.xml184(para) #: ./doc/arch-design/multi_site/section_prescriptive_examples_multi_site.xml184(para)
msgid "" msgid ""
@ -1948,7 +1948,7 @@ msgid ""
"cost of bandwidth and transit, since the content resides on sites closer to " "cost of bandwidth and transit, since the content resides on sites closer to "
"the customer, instead of a centralized content store that would require " "the customer, instead of a centralized content store that would require "
"utilizing higher cost cross country links." "utilizing higher cost cross country links."
msgstr "" msgstr "多区域OpenStack部署常见的一个场景是创建内容分发网络CDN，一个应用使用本地架构会有低网络延迟和接近用户的需求，为了提供给用户极致的体验，为了减少带宽和传送的费用，因此将内容输送到更加接近客户，而替代中心化的内容存储这种需要跨国连接的高额费用。"
#: ./doc/arch-design/multi_site/section_prescriptive_examples_multi_site.xml203(para) #: ./doc/arch-design/multi_site/section_prescriptive_examples_multi_site.xml203(para)
msgid "" msgid ""
@ -1959,7 +1959,7 @@ msgid ""
"minimum number of network hops for any given end user. Despite these " "minimum number of network hops for any given end user. Despite these "
"differences, the storage replication configuration has significant overlap " "differences, the storage replication configuration has significant overlap "
"with that of a geo-redundant load balancing use case." "with that of a geo-redundant load balancing use case."
msgstr "" msgstr "此架构通常包括一个放置在最接近节点的用户需求的地理位置组件。在此场景下，目标是跨所有站点的100%冗余，已经不是一个需求，意图是为任何指定的最终用户有最大化内容可用，最小的网络hop跳数。尽管他们不一样，存储冗余配置和地理位置冗余负载均衡用例有明显的重叠。"
#: ./doc/arch-design/multi_site/section_prescriptive_examples_multi_site.xml212(para) #: ./doc/arch-design/multi_site/section_prescriptive_examples_multi_site.xml212(para)
msgid "" msgid ""
@ -1969,7 +1969,7 @@ msgid ""
"sent to a global services load balancer that determines the location of the " "sent to a global services load balancer that determines the location of the "
"client, then routes the request to the closest OpenStack site where the " "client, then routes the request to the closest OpenStack site where the "
"application completes the request." "application completes the request."
msgstr "" msgstr "在此例中，应用利用此多区域OpenStack基于位置敏感的安装，在每个站点的计算集群中启动web服务和内容服务的实例，来自客户的请求会第一时间发送到全局服务负载均衡器，然后负载均衡器会决定客户的位置，当应用完成请求，路由会将请求发给最近的OpenStack站点。"
#: ./doc/arch-design/multi_site/section_tech_considerations_multi_site.xml8(title) #: ./doc/arch-design/multi_site/section_tech_considerations_multi_site.xml8(title)
#: ./doc/arch-design/network_focus/section_tech_considerations_network_focus.xml8(title) #: ./doc/arch-design/network_focus/section_tech_considerations_network_focus.xml8(title)
@ -1989,7 +1989,7 @@ msgid ""
"designed in a variety of ways to handle individual application needs. A " "designed in a variety of ways to handle individual application needs. A "
"multi-site deployment will have additional challenges compared to single " "multi-site deployment will have additional challenges compared to single "
"site installations and will therefore be a more complex solution." "site installations and will therefore be a more complex solution."
msgstr "" msgstr "设计一个多区域OpenStack有许多的技术因素需要被纳入有关的账单。一个OpenStack云有很多中办法来设计，去掌控分离的应用需求，一个多区域的部署相比于单一站点的安装会带来额外的挑战，也因此将会是一个更加复杂的解决方案。"
#: ./doc/arch-design/multi_site/section_tech_considerations_multi_site.xml16(para) #: ./doc/arch-design/multi_site/section_tech_considerations_multi_site.xml16(para)
msgid "" msgid ""
@ -2092,7 +2092,7 @@ msgid ""
" the users of the system, when reading Identity documentation, as it is " " the users of the system, when reading Identity documentation, as it is "
"required to define the region name when providing actions to an API endpoint" "required to define the region name when providing actions to an API endpoint"
" or in the dashboard." " or in the dashboard."
msgstr "" msgstr "身份是多数OpenStack用户的第一道“门槛”，对于绝大多数OpenStack的主要操作都有和身份服务互动的需求，因此，确保你为用户提供身份认证服务单一的URL非常重要，同样重要的是身份服务的正确文档和配置region。在你安装时考虑好每个站点定义的region的身份命名空间，这对于系统管理很重要，当阅读身份文档时，它会要求当在API端点或GUI界面执行某些操作时所定义的region名称。"
#: ./doc/arch-design/multi_site/section_tech_considerations_multi_site.xml94(para) #: ./doc/arch-design/multi_site/section_tech_considerations_multi_site.xml94(para)
msgid "" msgid ""
@ -2102,7 +2102,7 @@ msgid ""
"may be able to cope with this via internal mechanisms. Others, however, may " "may be able to cope with this via internal mechanisms. Others, however, may "
"require the implementation of an external system including global services " "require the implementation of an external system including global services "
"load balancers or anycast-advertised DNS." "load balancers or anycast-advertised DNS."
msgstr "" msgstr "负载均衡是安装多站点OpenStack另外一个常见的问题，它可能运行着负载均衡即服务的HAproxy实例，这些可能是本地一个特定的region，一些应用也许通过内部机制来应对这种情况，另外，也许需要外部的系统来实现，诸如全局服务负载均衡器或者anycast-advertised DNS。"
#: ./doc/arch-design/multi_site/section_tech_considerations_multi_site.xml102(para) #: ./doc/arch-design/multi_site/section_tech_considerations_multi_site.xml102(para)
msgid "" msgid ""
@ -2116,7 +2116,7 @@ msgid ""
"back end. Benchmarking allows the operational staff to provide users with an" "back end. Benchmarking allows the operational staff to provide users with an"
" understanding of the amount of time required for a stored or modified " " understanding of the amount of time required for a stored or modified "
"object to become available to the entire environment." "object to become available to the entire environment."
msgstr "" msgstr "取决于在设计站点时的选择的存储模式，存储的复制和可用性也是最终用户所关心的。如果一个应用有理解region的能力，那么它可能会保持通过region分离的对象存储系统，在此种情形下，用户需要在多个region访问对象的话就需要去自己去跨站点复制，基于中心化的swift代理，用户也许需要后端对象存储的复制基准时间。测试基准允许运维人员提供给用户可以理解的存储需求的总计时间或者是更改对象使之在整个环境中可用。"
#: ./doc/arch-design/multi_site/section_tech_considerations_multi_site.xml114(title) #: ./doc/arch-design/multi_site/section_tech_considerations_multi_site.xml114(title)
#: ./doc/arch-design/network_focus/section_tech_considerations_network_focus.xml432(title) #: ./doc/arch-design/network_focus/section_tech_considerations_network_focus.xml432(title)

8
doc/image-guide/locale/zh_CN.po
View File

@ -6,8 +6,8 @@
msgid "" msgid ""
msgstr "" msgstr ""
"Project-Id-Version: OpenStack Manuals\n" "Project-Id-Version: OpenStack Manuals\n"
"POT-Creation-Date: 2015-02-05 14:23+0000\n" "POT-Creation-Date: 2015-02-09 04:31+0000\n"
"PO-Revision-Date: 2015-02-06 03:50+0000\n" "PO-Revision-Date: 2015-02-08 23:20+0000\n"
"Last-Translator: 秋林 <chenqioulin_1983@163.com>\n" "Last-Translator: 秋林 <chenqioulin_1983@163.com>\n"
"Language-Team: Chinese (China) (http://www.transifex.com/projects/p/openstack-manuals-i18n/language/zh_CN/)\n" "Language-Team: Chinese (China) (http://www.transifex.com/projects/p/openstack-manuals-i18n/language/zh_CN/)\n"
"MIME-Version: 1.0\n" "MIME-Version: 1.0\n"
@ -2141,7 +2141,7 @@ msgstr "<link href=\"http://susestudio.com\">SUSE Studio</link> 是一个在浏
#: ./doc/image-guide/ch_obtaining_images.xml7(title) #: ./doc/image-guide/ch_obtaining_images.xml7(title)
msgid "Get images" msgid "Get images"
msgstr "Get images" msgstr "获取镜像"
#: ./doc/image-guide/ch_obtaining_images.xml9(para) #: ./doc/image-guide/ch_obtaining_images.xml9(para)
msgid "" msgid ""
@ -2308,7 +2308,7 @@ msgstr "其他Linux发行版的官方镜像"
msgid "" msgid ""
"As of this writing, we are not aware of other distributions that provide " "As of this writing, we are not aware of other distributions that provide "
"images for download." "images for download."
msgstr "在本文档便携式，我们并未发现其他Linux发行版提供镜像下载。" msgstr "在本文档编写时，我们并未发现其他Linux发行版提供镜像下载。"
#: ./doc/image-guide/ch_obtaining_images.xml132(title) #: ./doc/image-guide/ch_obtaining_images.xml132(title)
msgid "Rackspace Cloud Builders (multiple distros) images" msgid "Rackspace Cloud Builders (multiple distros) images"