Imported Translations from Zanata
For more information about this automatic import see: https://wiki.openstack.org/wiki/Translations/Infrastructure Change-Id: Ie6ea99900a9bd030a46f55a9d99ff283d5b1ebd3
This commit is contained in:
OpenStack Proposal Bot
parent
7d56dd3ba9
commit
c2ea5231bd
@ -1,7 +1,7 @@
|
||||
msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: PACKAGE VERSION\n"
|
||||
"POT-Creation-Date: 2015-10-28 06:28+0000\n"
|
||||
"POT-Creation-Date: 2015-11-03 06:30+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"
|
||||
@ -266,7 +266,7 @@ msgid "It may also be helpful to install a few extra options in order to facilit
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/ch_legal-security-requirements.xml:249(para)
|
||||
msgid "Another useful tool for managing a multi-site installation is OpenStack Orchestration (heat). The Orchestration module allows the use of templates to define a set of instances to be launched together or for scaling existing sets. It can set up matching or differentiated groupings based on regions. For instance, if an application requires an equally balanced number of nodes across sites, the same heat template can be used to cover each site with small alterations to only the region name."
|
||||
msgid "Another useful tool for managing a multi-site installation is Orchestration (heat). The Orchestration service allows the use of templates to define a set of instances to be launched together or for scaling existing sets. It can set up matching or differentiated groupings based on regions. For instance, if an application requires an equally balanced number of nodes across sites, the same heat template can be used to cover each site with small alterations to only the region name."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/ch_network_focus.xml:7(title)
|
||||
@ -838,15 +838,15 @@ msgid "OpenStack Object Storage"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/network_focus/section_prescriptive_examples_network_focus.xml:63(para)
|
||||
msgid "Orchestration module"
|
||||
msgid "Orchestration service"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/network_focus/section_prescriptive_examples_network_focus.xml:66(para)
|
||||
msgid "Telemetry module"
|
||||
msgid "Telemetry service"
|
||||
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, we recommend the Orchestration module component to handle the proper scaling of 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 works 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, we recommend the Orchestration service component to handle the proper scaling of workloads to adjust to demand. Due to the requirement for auto-scaling, the design includes the Telemetry service. 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 works 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:83(title)
|
||||
@ -950,7 +950,7 @@ msgid "Depending on the selected design, Networking itself might not support the
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/network_focus/section_architecture_network_focus.xml:49(para)
|
||||
msgid "Interaction with orchestration services is inevitable in larger-scale deployments. The Orchestration module is capable of allocating network resource defined in templates to map to tenant networks and for port creation, as well as allocating floating IPs. If there is a requirement to define and manage network resources when using orchestration, we recommend that the design include the Orchestration module to meet the demands of users."
|
||||
msgid "Interaction with orchestration services is inevitable in larger-scale deployments. The Orchestration service is capable of allocating network resource defined in templates to map to tenant networks and for port creation, as well as allocating floating IPs. If there is a requirement to define and manage network resources when using orchestration, we recommend that the design include the Orchestration service to meet the demands of users."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/network_focus/section_architecture_network_focus.xml:57(title)
|
||||
@ -2216,7 +2216,7 @@ msgid "The OS-hypervisor combination should be chosen based on the interoperabil
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:461(para)
|
||||
msgid "The OpenStack components you choose can have a significant impact on the overall design. While there are certain components that are always present (Compute and Image service, for example), there are other services that may not be required. As an example, a certain design may not require the Orchestration module. Omitting Orchestration would not typically have a significant impact on the overall design, however, if the architecture uses a replacement for OpenStack Object Storage for its storage component, this could potentially have significant impacts on the rest of the design."
|
||||
msgid "The OpenStack components you choose can have a significant impact on the overall design. While there are certain components that are always present (Compute and Image service, for example), there are other services that may not be required. As an example, a certain design may not require the Orchestration service. Omitting Orchestration would not typically have a significant impact on the overall design, however, if the architecture uses a replacement for OpenStack Object Storage for its storage component, this could potentially have significant impacts on the rest of the design."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:471(para)
|
||||
@ -2243,7 +2243,7 @@ msgstr ""
|
||||
msgid "OpenStack Object Storage (swift) (or another object storage solution)"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:492(para) ./doc/arch-design/compute_focus/section_tech_considerations_compute_focus.xml:257(para)
|
||||
#: ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:492(para) ./doc/arch-design/compute_focus/section_tech_considerations_compute_focus.xml:256(para)
|
||||
msgid "OpenStack Block Storage (cinder)"
|
||||
msgstr ""
|
||||
|
||||
@ -2536,30 +2536,30 @@ msgid "Also consider several specialized components:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/compute_focus/section_tech_considerations_compute_focus.xml:238(para)
|
||||
msgid "<glossterm>Orchestration</glossterm> module (<glossterm>heat</glossterm>)"
|
||||
msgid "<glossterm>Orchestration</glossterm> (heat)"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/compute_focus/section_tech_considerations_compute_focus.xml:240(para)
|
||||
msgid "Given the nature of the applications involved in this scenario, these are heavily automated deployments. Making use of Orchestration is highly beneficial in this case. You can script the deployment of a batch of instances and the running of tests, but it makes sense to use the Orchestration module to handle all these actions."
|
||||
#: ./doc/arch-design/compute_focus/section_tech_considerations_compute_focus.xml:239(para)
|
||||
msgid "Given the nature of the applications involved in this scenario, these are heavily automated deployments. Making use of Orchestration is highly beneficial in this case. You can script the deployment of a batch of instances and the running of tests, but it makes sense to use the Orchestration service to handle all these actions."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/compute_focus/section_tech_considerations_compute_focus.xml:249(para) ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:153(term)
|
||||
msgid "Telemetry module (ceilometer)"
|
||||
#: ./doc/arch-design/compute_focus/section_tech_considerations_compute_focus.xml:248(para) ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:153(term)
|
||||
msgid "Telemetry (ceilometer)"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/compute_focus/section_tech_considerations_compute_focus.xml:250(para)
|
||||
msgid "Telemetry and the alarms it generates support autoscaling of instances using Orchestration. Users that are not using the Orchestration module do not need to deploy the Telemetry module and may choose to use external solutions to fulfill their metering and monitoring requirements."
|
||||
#: ./doc/arch-design/compute_focus/section_tech_considerations_compute_focus.xml:249(para)
|
||||
msgid "Telemetry and the alarms it generates support autoscaling of instances using Orchestration. Users that are not using the Orchestration service do not need to deploy the Telemetry service and may choose to use external solutions to fulfill their metering and monitoring requirements."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/compute_focus/section_tech_considerations_compute_focus.xml:258(para)
|
||||
#: ./doc/arch-design/compute_focus/section_tech_considerations_compute_focus.xml:257(para)
|
||||
msgid "Due to the burst-able nature of the workloads and the applications and instances that perform batch processing, this cloud mainly uses memory or CPU, so the need for add-on storage to each instance is not a likely requirement. This does not mean that you do not use OpenStack Block Storage (cinder) in the infrastructure, but typically it is not a central component."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/compute_focus/section_tech_considerations_compute_focus.xml:267(para) ./doc/arch-design/multi_site/section_architecture_multi_site.xml:89(title)
|
||||
#: ./doc/arch-design/compute_focus/section_tech_considerations_compute_focus.xml:266(para) ./doc/arch-design/multi_site/section_architecture_multi_site.xml:89(title)
|
||||
msgid "Networking"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/compute_focus/section_tech_considerations_compute_focus.xml:268(para)
|
||||
#: ./doc/arch-design/compute_focus/section_tech_considerations_compute_focus.xml:267(para)
|
||||
msgid "When choosing a networking platform, ensure that it either works with all desired hypervisor and container technologies and their OpenStack drivers, or that it includes an implementation of an ML2 mechanism driver. You can mix networking platforms that provide ML2 mechanisms drivers."
|
||||
msgstr ""
|
||||
|
||||
@ -2644,7 +2644,7 @@ msgid "OS and hypervisor selection impact the following areas:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:167(para)
|
||||
msgid "The selection of OpenStack components is important. There are certain components that are required, for example the compute and image services, but others, such as the Orchestration module, may not be present."
|
||||
msgid "The selection of OpenStack components is important. There are certain components that are required, for example the compute and image services, but others, such as the Orchestration service, may not be present."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:171(para)
|
||||
@ -2675,7 +2675,7 @@ msgstr ""
|
||||
msgid "Networking (neutron)"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:193(para)
|
||||
#: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:193(para) ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:160(term)
|
||||
msgid "Orchestration (heat)"
|
||||
msgstr ""
|
||||
|
||||
@ -2684,7 +2684,7 @@ msgid "A compute-focused design is less likely to include OpenStack Block Storag
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:201(para)
|
||||
msgid "The exclusion of certain OpenStack components might also limit the functionality of other components. If a design includes the Orchestration module but excludes the Telemetry module, then the design cannot take advantage of Orchestration's auto scaling functionality as this relies on information from Telemetry."
|
||||
msgid "The exclusion of certain OpenStack components might also limit the functionality of other components. If a design includes the Orchestration service but excludes the Telemetry service, then the design cannot take advantage of Orchestration's auto scaling functionality as this relies on information from Telemetry."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:210(para)
|
||||
@ -2876,7 +2876,7 @@ msgid "CERN maintains a small set of Scientific Linux 5 and 6 images onto which
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/compute_focus/section_prescriptive_examples_compute_focus.xml:137(para)
|
||||
msgid "CERN does not require direct billing, but uses the Telemetry module to perform metering for the purposes of adjusting project quotas. CERN uses a sharded, replicated, MongoDB back-end. To spread API load, CERN deploys instances of the nova-api service within the child cells for Telemetry to query against. This also requires the configuration of supporting services such as keystone, glance-api, and glance-registry in the child cells."
|
||||
msgid "CERN does not require direct billing, but uses the Telemetry service to perform metering for the purposes of adjusting project quotas. CERN uses a sharded, replicated, MongoDB back-end. To spread API load, CERN deploys instances of the nova-api service within the child cells for Telemetry to query against. This also requires the configuration of supporting services such as keystone, glance-api, and glance-registry in the child cells."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/compute_focus/section_prescriptive_examples_compute_focus.xml:151(para)
|
||||
@ -3230,7 +3230,7 @@ msgid "It may also be helpful to install a few extra options in order to facilit
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/multi_site/section_tech_considerations_multi_site.xml:166(para)
|
||||
msgid "Another useful tool for managing a multi-site installation is Orchestration (heat). The Orchestration module allows the use of templates to define a set of instances to be launched together or for scaling existing sets. It can also be used to set up matching or differentiated groupings based on regions. For instance, if an application requires an equally balanced number of nodes across sites, the same heat template can be used to cover each site with small alterations to only the region name."
|
||||
msgid "Another useful tool for managing a multi-site installation is Orchestration (heat). The Orchestration service allows the use of templates to define a set of instances to be launched together or for scaling existing sets. It can also be used to set up matching or differentiated groupings based on regions. For instance, if an application requires an equally balanced number of nodes across sites, the same heat template can be used to cover each site with small alterations to only the region name."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/multi_site/section_user_requirements_multi_site.xml:10(title)
|
||||
@ -3444,7 +3444,7 @@ msgid "A firewall, switches and load balancers on the public facing network conn
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/multi_site/section_prescriptive_examples_multi_site.xml:112(para)
|
||||
msgid "OpenStack Controller services running, Networking, dashboard, Block Storage and Compute running locally in each of the three regions. Identity service, Orchestration module, Telemetry module, Image service and Object Storage service can be installed centrally, with nodes in each of the region providing a redundant OpenStack Controller plane throughout the globe."
|
||||
msgid "OpenStack Controller services running, Networking, dashboard, Block Storage and Compute running locally in each of the three regions. Identity service, Orchestration service, Telemetry service, Image service and Object Storage service can be installed centrally, with nodes in each of the region providing a redundant OpenStack Controller plane throughout the globe."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/multi_site/section_prescriptive_examples_multi_site.xml:121(para) ./doc/arch-design/generalpurpose/section_prescriptive_example_general_purpose.xml:44(para)
|
||||
@ -3644,7 +3644,7 @@ msgid "A CMP must be aware of what workloads are running, where they are running
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:90(para)
|
||||
msgid "The Telemetry module (ceilometer) provides information on the usage of various OpenStack components. Note the following:"
|
||||
msgid "The Telemetry service (ceilometer) provides information on the usage of various OpenStack components. Note the following:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:94(para)
|
||||
@ -3660,7 +3660,7 @@ msgid "Performance is critical to hybrid cloud deployments, and they are affecte
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:119(para)
|
||||
msgid "As with utilization, native OpenStack tools help improve performance. For example, you can use Telemetry to measure performance and the Orchestration module (heat) to react to changes in demand."
|
||||
msgid "As with utilization, native OpenStack tools help improve performance. For example, you can use Telemetry to measure performance and the Orchestration service (heat) to react to changes in demand."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:123(para)
|
||||
@ -3687,10 +3687,6 @@ msgstr ""
|
||||
msgid "Use of Telemetry depends, in large part, on what the other parts of the cloud you are using."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:160(term)
|
||||
msgid "Orchestration module (heat)"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:162(para)
|
||||
msgid "Orchestration can be a valuable tool in orchestrating tasks a CMP decides are necessary in an OpenStack-based cloud."
|
||||
msgstr ""
|
||||
@ -3982,7 +3978,7 @@ msgid "This example shows two clouds with a Cloud Management Platform (CMP) conn
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/hybrid/section_prescriptive_examples_hybrid.xml:54(para)
|
||||
msgid "The private OpenStack cloud has at least one controller and at least one compute node. It includes metering using the Telemetry module. The Telemetry module captures the load increase and the CMP processes the information. If there is available capacity, the CMP uses the OpenStack API to call the Orchestration service. This creates instances on the private cloud in response to user requests. When capacity is not available on the private cloud, the CMP issues a request to the Orchestration service API of the public cloud. This creates the instance on the public cloud."
|
||||
msgid "The private OpenStack cloud has at least one controller and at least one compute node. It includes metering using the Telemetry service. The Telemetry service captures the load increase and the CMP processes the information. If there is available capacity, the CMP uses the OpenStack API to call the Orchestration service. This creates instances on the private cloud in response to user requests. When capacity is not available on the private cloud, the CMP issues a request to the Orchestration service API of the public cloud. This creates the instance on the public cloud."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/hybrid/section_prescriptive_examples_hybrid.xml:65(para)
|
||||
@ -4090,7 +4086,7 @@ msgid "Implementing a baseline of upper-layer services across all of the cloud p
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/hybrid/section_architecture_hybrid.xml:69(para)
|
||||
msgid "For example, through the <glossterm>Database service</glossterm> for OpenStack (<glossterm>trove</glossterm>), OpenStack supports MySQL as a service but not NoSQL databases in production. To move from or run alongside AWS, a NoSQL workload must use an automation tool, such as the Orchestration module (heat), to recreate the NoSQL database on top of OpenStack."
|
||||
msgid "For example, through the <glossterm>Database service</glossterm> for OpenStack (<glossterm>trove</glossterm>), OpenStack supports MySQL as a service but not NoSQL databases in production. To move from or run alongside AWS, a NoSQL workload must use an automation tool, such as the Orchestration service (heat), to recreate the NoSQL database on top of OpenStack."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/hybrid/section_architecture_hybrid.xml:79(para)
|
||||
@ -5564,7 +5560,7 @@ msgid "OpenStack <glossterm>dashboard</glossterm> (<glossterm>horizon</glossterm
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:439(para)
|
||||
msgid "<glossterm>Telemetry</glossterm> module (<glossterm>ceilometer</glossterm>)"
|
||||
msgid "<glossterm>Telemetry</glossterm> (<glossterm>ceilometer</glossterm>)"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:443(para)
|
||||
@ -5778,7 +5774,7 @@ msgid "Increasing OpenStack Object Storage means network bandwidth needs to be t
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_prescriptive_example_general_purpose.xml:90(para)
|
||||
msgid "Leveraging Orchestration and Telemetry modules is also a potential issue when providing auto-scaling, orchestrated web application environments. Defining the web applications in <glossterm baseform=\"Heat Orchestration Template (HOT)\">Heat Orchestration Templates (HOT)</glossterm> negates the reliance on the current scripted Puppet solution."
|
||||
msgid "Leveraging Orchestration and Telemetry services is also a potential issue when providing auto-scaling, orchestrated web application environments. Defining the web applications in <glossterm baseform=\"Heat Orchestration Template (HOT)\">Heat Orchestration Templates (HOT)</glossterm> negates the reliance on the current scripted Puppet solution."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_prescriptive_example_general_purpose.xml:95(para)
|
||||
|
||||
@ -12,7 +12,7 @@
|
||||
msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: PACKAGE VERSION\n"
|
||||
"POT-Creation-Date: 2015-10-30 03:19+0000\n"
|
||||
"POT-Creation-Date: 2015-11-02 22:23+0000\n"
|
||||
"MIME-Version: 1.0\n"
|
||||
"Content-Type: text/plain; charset=UTF-8\n"
|
||||
"Content-Transfer-Encoding: 8bit\n"
|
||||
@ -127,16 +127,6 @@ msgstr ""
|
||||
"己的数据库和消息队列(理想情况下是集群化的)，并提供将负载细分到这些子系统中的"
|
||||
"功能，以提高整体性能。"
|
||||
|
||||
msgid ""
|
||||
"<glossterm>Orchestration</glossterm> module (<glossterm>heat</glossterm>)"
|
||||
msgstr ""
|
||||
"<glossterm>Orchestration</glossterm> 模块 (<glossterm>heat</glossterm>)"
|
||||
|
||||
msgid ""
|
||||
"<glossterm>Telemetry</glossterm> module (<glossterm>ceilometer</glossterm>)"
|
||||
msgstr ""
|
||||
"<glossterm>Telemetry</glossterm> module (<glossterm>ceilometer</glossterm>)"
|
||||
|
||||
msgid ""
|
||||
"<link linkend=\"arch-guide-openstack-on-openstack\">OpenStack on OpenStack</"
|
||||
"link>: describes building a multi-tiered cloud by running OpenStack on top "
|
||||
@ -2379,17 +2369,6 @@ msgstr "传统联网方式(nova-network)"
|
||||
msgid "Legal requirements"
|
||||
msgstr "法律需求"
|
||||
|
||||
msgid ""
|
||||
"Leveraging Orchestration and Telemetry modules is also a potential issue "
|
||||
"when providing auto-scaling, orchestrated web application environments. "
|
||||
"Defining the web applications in <glossterm baseform=\"Heat Orchestration "
|
||||
"Template (HOT)\">Heat Orchestration Templates (HOT)</glossterm> negates the "
|
||||
"reliance on the current scripted Puppet solution."
|
||||
msgstr ""
|
||||
"借助于Orchestration和Telemetry模块可以为web应用环境提供自动扩展的能力。使用"
|
||||
"Puppet脚本定义web应用的 <glossterm baseform=\"Heat Orchestration Template "
|
||||
"(HOT)\">Heat Orchestration Templates (HOT)</glossterm>即可实现。"
|
||||
|
||||
msgid ""
|
||||
"Leveraging existing monitoring systems is an effective check to ensure "
|
||||
"OpenStack environments can be monitored."
|
||||
@ -3141,9 +3120,6 @@ msgstr "运营者的需求"
|
||||
msgid "Orchestration (heat)"
|
||||
msgstr "编排 (heat)"
|
||||
|
||||
msgid "Orchestration module"
|
||||
msgstr "编排模块"
|
||||
|
||||
msgid ""
|
||||
"Organizations need to determine if it is logical to create their own clouds "
|
||||
"internally. Using a private cloud, organizations are able to maintain "
|
||||
@ -3873,12 +3849,6 @@ msgstr "技术因素"
|
||||
msgid "Technical requirements"
|
||||
msgstr "技术需求"
|
||||
|
||||
msgid "Telemetry module"
|
||||
msgstr "计量模块"
|
||||
|
||||
msgid "Telemetry module (ceilometer)"
|
||||
msgstr "Telemetry 模块 (ceilometer)"
|
||||
|
||||
msgid "Telemetry uses MongoDB."
|
||||
msgstr "Telemetry 使用MongoDB。"
|
||||
|
||||
|
||||
@ -8,7 +8,7 @@ msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: Common documents 1.0.0\n"
|
||||
"Report-Msgid-Bugs-To: \n"
|
||||
"POT-Creation-Date: 2015-10-30 06:28+0000\n"
|
||||
"POT-Creation-Date: 2015-11-03 06:31+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"
|
||||
@ -3468,7 +3468,7 @@ msgstr ""
|
||||
|
||||
#: ../common/get_started_with_openstack.rst:36
|
||||
msgid ""
|
||||
"`Dashboard <http://www.openstack.org/software/releases/kilo/components/"
|
||||
"`Dashboard <http://www.openstack.org/software/releases/liberty/components/"
|
||||
"horizon>`__"
|
||||
msgstr ""
|
||||
|
||||
@ -3485,7 +3485,8 @@ msgstr ""
|
||||
|
||||
#: ../common/get_started_with_openstack.rst:41
|
||||
msgid ""
|
||||
"`Compute <http://www.openstack.org/software/releases/kilo/components/nova>`__"
|
||||
"`Compute <http://www.openstack.org/software/releases/liberty/components/"
|
||||
"nova>`__"
|
||||
msgstr ""
|
||||
|
||||
#: ../common/get_started_with_openstack.rst:42
|
||||
@ -3501,7 +3502,7 @@ msgstr ""
|
||||
|
||||
#: ../common/get_started_with_openstack.rst:46
|
||||
msgid ""
|
||||
"`Networking <http://www.openstack.org/software/releases/kilo/components/"
|
||||
"`Networking <http://www.openstack.org/software/releases/liberty/components/"
|
||||
"neutron>`__"
|
||||
msgstr ""
|
||||
|
||||
@ -3519,8 +3520,8 @@ msgstr ""
|
||||
|
||||
#: ../common/get_started_with_openstack.rst:52
|
||||
msgid ""
|
||||
"`Object Storage <http://www.openstack.org/software/releases/kilo/components/"
|
||||
"swift>`__"
|
||||
"`Object Storage <http://www.openstack.org/software/releases/liberty/"
|
||||
"components/swift>`__"
|
||||
msgstr ""
|
||||
|
||||
#: ../common/get_started_with_openstack.rst:53
|
||||
@ -3538,8 +3539,8 @@ msgstr ""
|
||||
|
||||
#: ../common/get_started_with_openstack.rst:60
|
||||
msgid ""
|
||||
"`Block Storage <http://www.openstack.org/software/releases/kilo/components/"
|
||||
"cinder>`__"
|
||||
"`Block Storage <http://www.openstack.org/software/releases/liberty/"
|
||||
"components/cinder>`__"
|
||||
msgstr ""
|
||||
|
||||
#: ../common/get_started_with_openstack.rst:61
|
||||
@ -3555,7 +3556,7 @@ msgstr ""
|
||||
|
||||
#: ../common/get_started_with_openstack.rst:65
|
||||
msgid ""
|
||||
"`Identity service <http://www.openstack.org/software/releases/kilo/"
|
||||
"`Identity service <http://www.openstack.org/software/releases/liberty/"
|
||||
"components/keystone>`__"
|
||||
msgstr ""
|
||||
|
||||
@ -3571,8 +3572,8 @@ msgstr ""
|
||||
|
||||
#: ../common/get_started_with_openstack.rst:70
|
||||
msgid ""
|
||||
"`Image service <http://www.openstack.org/software/releases/kilo/components/"
|
||||
"glance>`__"
|
||||
"`Image service <http://www.openstack.org/software/releases/liberty/"
|
||||
"components/glance>`__"
|
||||
msgstr ""
|
||||
|
||||
#: ../common/get_started_with_openstack.rst:71
|
||||
@ -3587,7 +3588,7 @@ msgstr ""
|
||||
|
||||
#: ../common/get_started_with_openstack.rst:74
|
||||
msgid ""
|
||||
"`Telemetry <http://www.openstack.org/software/releases/kilo/components/"
|
||||
"`Telemetry <http://www.openstack.org/software/releases/liberty/components/"
|
||||
"ceilometer>`__"
|
||||
msgstr ""
|
||||
|
||||
@ -3603,8 +3604,8 @@ msgstr ""
|
||||
|
||||
#: ../common/get_started_with_openstack.rst:78
|
||||
msgid ""
|
||||
"`Orchestration <http://www.openstack.org/software/releases/kilo/components/"
|
||||
"heat>`__"
|
||||
"`Orchestration <http://www.openstack.org/software/releases/liberty/"
|
||||
"components/heat>`__"
|
||||
msgstr ""
|
||||
|
||||
#: ../common/get_started_with_openstack.rst:79
|
||||
@ -3621,7 +3622,7 @@ msgstr ""
|
||||
|
||||
#: ../common/get_started_with_openstack.rst:84
|
||||
msgid ""
|
||||
"`Database service <http://www.openstack.org/software/releases/kilo/"
|
||||
"`Database service <http://www.openstack.org/software/releases/liberty/"
|
||||
"components/trove>`__"
|
||||
msgstr ""
|
||||
|
||||
@ -3637,7 +3638,7 @@ msgstr ""
|
||||
|
||||
#: ../common/get_started_with_openstack.rst:88
|
||||
msgid ""
|
||||
"`Data processing service <http://www.openstack.org/software/releases/kilo/"
|
||||
"`Data processing service <http://www.openstack.org/software/releases/liberty/"
|
||||
"components/sahara>`__"
|
||||
msgstr ""
|
||||
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: PACKAGE VERSION\n"
|
||||
"POT-Creation-Date: 2015-10-30 06:28+0000\n"
|
||||
"POT-Creation-Date: 2015-11-03 06:31+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"
|
||||
@ -5374,7 +5374,7 @@ msgstr ""
|
||||
msgid "NFS (access by IP)"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/shared-file-systems/drivers/glusterfs-driver.xml:21(title) ./doc/config-reference/shared-file-systems/drivers/hdfs-native-driver.xml:38(title) ./doc/config-reference/shared-file-systems/drivers/ibm-gpfs-driver.xml:22(title) ./doc/config-reference/shared-file-systems/drivers/emc-vnx-driver.xml:66(title) ./doc/config-reference/shared-file-systems/drivers/huawei-nas-driver.xml:45(title) ./doc/config-reference/shared-file-systems/drivers/hp-3par-share-driver.xml:10(title) ./doc/config-reference/shared-file-systems/drivers/glusterfs-native-driver.xml:47(title) ./doc/config-reference/shared-file-systems/drivers/emc-isilon-driver.xml:35(title) ./doc/config-reference/block-storage/drivers/zfssa-iscsi-driver.xml:93(title) ./doc/config-reference/block-storage/drivers/emc-scaleio-driver.xml:22(title) ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:99(title) ./doc/config-reference/block-storage/drivers/pure-storage-driver.xml:23(title) ./doc/config-reference/block-storage/drivers/dell-storagecenter-driver.xml:17(title) ./doc/config-reference/block-storage/drivers/dell-equallogic-driver.xml:10(title) ./doc/config-reference/block-storage/drivers/hds-hnas-driver.xml:17(title) ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:252(title) ./doc/config-reference/block-storage/drivers/violin-v6000-driver.xml:73(title) ./doc/config-reference/block-storage/drivers/emc-vnx-driver.xml:38(title) ./doc/config-reference/block-storage/drivers/sheepdog-driver.xml:18(title) ./doc/config-reference/block-storage/drivers/emc-xtremio-driver.xml:21(title) ./doc/config-reference/block-storage/drivers/ibm-flashsystem-volume-driver.xml:289(title) ./doc/config-reference/block-storage/drivers/violin-v7000-driver.xml:59(title) ./doc/config-reference/block-storage/drivers/emc-vmax-driver.xml:35(title) ./doc/config-reference/block-storage/drivers/xio-volume-driver.xml:17(title) ./doc/config-reference/block-storage/drivers/prophetstor-dpl-driver.xml:18(title) ./doc/config-reference/block-storage/drivers/hp-msa-driver.xml:48(title) ./doc/config-reference/block-storage/drivers/dothill-driver.xml:53(title) ./doc/config-reference/block-storage/drivers/scality-sofs-driver.xml:16(title) ./doc/config-reference/block-storage/drivers/hitachi-storage-volume-driver.xml:56(title) ./doc/config-reference/block-storage/drivers/lenovo-driver.xml:48(title) ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:66(title) ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:327(title) ./doc/config-reference/block-storage/drivers/zfssa-nfs-driver.xml:15(title)
|
||||
#: ./doc/config-reference/shared-file-systems/drivers/glusterfs-driver.xml:21(title) ./doc/config-reference/shared-file-systems/drivers/hdfs-native-driver.xml:38(title) ./doc/config-reference/shared-file-systems/drivers/ibm-gpfs-driver.xml:22(title) ./doc/config-reference/shared-file-systems/drivers/emc-vnx-driver.xml:66(title) ./doc/config-reference/shared-file-systems/drivers/huawei-nas-driver.xml:45(title) ./doc/config-reference/shared-file-systems/drivers/hp-3par-share-driver.xml:10(title) ./doc/config-reference/shared-file-systems/drivers/glusterfs-native-driver.xml:47(title) ./doc/config-reference/shared-file-systems/drivers/emc-isilon-driver.xml:35(title) ./doc/config-reference/block-storage/drivers/zfssa-iscsi-driver.xml:93(title) ./doc/config-reference/block-storage/drivers/emc-scaleio-driver.xml:22(title) ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:99(title) ./doc/config-reference/block-storage/drivers/pure-storage-driver.xml:23(title) ./doc/config-reference/block-storage/drivers/dell-storagecenter-driver.xml:17(title) ./doc/config-reference/block-storage/drivers/dell-equallogic-driver.xml:10(title) ./doc/config-reference/block-storage/drivers/hds-hnas-driver.xml:17(title) ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:252(title) ./doc/config-reference/block-storage/drivers/violin-v6000-driver.xml:73(title) ./doc/config-reference/block-storage/drivers/emc-vnx-driver.xml:38(title) ./doc/config-reference/block-storage/drivers/sheepdog-driver.xml:18(title) ./doc/config-reference/block-storage/drivers/emc-xtremio-driver.xml:21(title) ./doc/config-reference/block-storage/drivers/ibm-flashsystem-volume-driver.xml:289(title) ./doc/config-reference/block-storage/drivers/violin-v7000-driver.xml:59(title) ./doc/config-reference/block-storage/drivers/emc-vmax-driver.xml:35(title) ./doc/config-reference/block-storage/drivers/xio-volume-driver.xml:17(title) ./doc/config-reference/block-storage/drivers/prophetstor-dpl-driver.xml:18(title) ./doc/config-reference/block-storage/drivers/hp-msa-driver.xml:48(title) ./doc/config-reference/block-storage/drivers/dothill-driver.xml:53(title) ./doc/config-reference/block-storage/drivers/nimble-volume-driver.xml:13(title) ./doc/config-reference/block-storage/drivers/scality-sofs-driver.xml:16(title) ./doc/config-reference/block-storage/drivers/hitachi-storage-volume-driver.xml:56(title) ./doc/config-reference/block-storage/drivers/lenovo-driver.xml:48(title) ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:66(title) ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:327(title) ./doc/config-reference/block-storage/drivers/zfssa-nfs-driver.xml:15(title)
|
||||
msgid "Supported operations"
|
||||
msgstr ""
|
||||
|
||||
@ -9058,31 +9058,31 @@ msgstr ""
|
||||
msgid "ScaleIO: Version 1.32"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/block-storage/drivers/emc-scaleio-driver.xml:25(para) ./doc/config-reference/block-storage/drivers/emc-xtremio-driver.xml:24(para)
|
||||
#: ./doc/config-reference/block-storage/drivers/emc-scaleio-driver.xml:25(para) ./doc/config-reference/block-storage/drivers/emc-xtremio-driver.xml:24(para) ./doc/config-reference/block-storage/drivers/nimble-volume-driver.xml:16(para)
|
||||
msgid "Create, delete, clone, attach, and detach volumes"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/block-storage/drivers/emc-scaleio-driver.xml:28(para) ./doc/config-reference/block-storage/drivers/emc-xtremio-driver.xml:27(para)
|
||||
#: ./doc/config-reference/block-storage/drivers/emc-scaleio-driver.xml:28(para) ./doc/config-reference/block-storage/drivers/emc-xtremio-driver.xml:27(para) ./doc/config-reference/block-storage/drivers/nimble-volume-driver.xml:19(para)
|
||||
msgid "Create and delete volume snapshots"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/block-storage/drivers/emc-scaleio-driver.xml:31(para) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:26(para) ./doc/config-reference/block-storage/drivers/emc-xtremio-driver.xml:30(para) ./doc/config-reference/block-storage/drivers/zfssa-nfs-driver.xml:27(para)
|
||||
#: ./doc/config-reference/block-storage/drivers/emc-scaleio-driver.xml:31(para) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:26(para) ./doc/config-reference/block-storage/drivers/emc-xtremio-driver.xml:30(para) ./doc/config-reference/block-storage/drivers/nimble-volume-driver.xml:22(para) ./doc/config-reference/block-storage/drivers/zfssa-nfs-driver.xml:27(para)
|
||||
msgid "Create a volume from a snapshot"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/block-storage/drivers/emc-scaleio-driver.xml:34(para) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:25(para) ./doc/config-reference/block-storage/drivers/emc-xtremio-driver.xml:33(para) ./doc/config-reference/block-storage/drivers/zfssa-nfs-driver.xml:30(para)
|
||||
#: ./doc/config-reference/block-storage/drivers/emc-scaleio-driver.xml:34(para) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:25(para) ./doc/config-reference/block-storage/drivers/emc-xtremio-driver.xml:33(para) ./doc/config-reference/block-storage/drivers/nimble-volume-driver.xml:25(para) ./doc/config-reference/block-storage/drivers/zfssa-nfs-driver.xml:30(para)
|
||||
msgid "Copy an image to a volume"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/block-storage/drivers/emc-scaleio-driver.xml:37(para) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:25(para) ./doc/config-reference/block-storage/drivers/emc-xtremio-driver.xml:36(para) ./doc/config-reference/block-storage/drivers/zfssa-nfs-driver.xml:33(para)
|
||||
#: ./doc/config-reference/block-storage/drivers/emc-scaleio-driver.xml:37(para) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:25(para) ./doc/config-reference/block-storage/drivers/emc-xtremio-driver.xml:36(para) ./doc/config-reference/block-storage/drivers/nimble-volume-driver.xml:28(para) ./doc/config-reference/block-storage/drivers/zfssa-nfs-driver.xml:33(para)
|
||||
msgid "Copy a volume to an image"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/block-storage/drivers/emc-scaleio-driver.xml:40(para) ./doc/config-reference/block-storage/drivers/emc-xtremio-driver.xml:39(para)
|
||||
#: ./doc/config-reference/block-storage/drivers/emc-scaleio-driver.xml:40(para) ./doc/config-reference/block-storage/drivers/emc-xtremio-driver.xml:39(para) ./doc/config-reference/block-storage/drivers/nimble-volume-driver.xml:31(para)
|
||||
msgid "Extend a volume"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/block-storage/drivers/emc-scaleio-driver.xml:43(para) ./doc/config-reference/block-storage/drivers/emc-xtremio-driver.xml:45(para)
|
||||
#: ./doc/config-reference/block-storage/drivers/emc-scaleio-driver.xml:43(para) ./doc/config-reference/block-storage/drivers/emc-xtremio-driver.xml:45(para) ./doc/config-reference/block-storage/drivers/nimble-volume-driver.xml:34(para)
|
||||
msgid "Get volume statistics"
|
||||
msgstr ""
|
||||
|
||||
@ -9258,7 +9258,7 @@ msgstr ""
|
||||
msgid "SIO_PASSWD"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/block-storage/drivers/emc-scaleio-driver.xml:130(title) ./doc/config-reference/block-storage/drivers/hds-hnas-driver.xml:291(caption)
|
||||
#: ./doc/config-reference/block-storage/drivers/emc-scaleio-driver.xml:130(title) ./doc/config-reference/block-storage/drivers/hds-hnas-driver.xml:291(caption) ./doc/config-reference/block-storage/drivers/nimble-volume-driver.xml:160(title)
|
||||
msgid "Configuration options"
|
||||
msgstr ""
|
||||
|
||||
@ -11849,7 +11849,7 @@ msgstr ""
|
||||
msgid "Set the following in your <filename>cinder.conf</filename> to use the Datera volume driver:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/block-storage/drivers/datera-volume-driver.xml:17(para) ./doc/config-reference/block-storage/drivers/nimble-volume-driver.xml:18(para)
|
||||
#: ./doc/config-reference/block-storage/drivers/datera-volume-driver.xml:17(para)
|
||||
msgid "Use the following options to configure the volume driver:"
|
||||
msgstr ""
|
||||
|
||||
@ -12999,7 +12999,7 @@ msgstr ""
|
||||
msgid "Xtremapp: Version 3.0 and 4.0"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/block-storage/drivers/emc-xtremio-driver.xml:42(para)
|
||||
#: ./doc/config-reference/block-storage/drivers/emc-xtremio-driver.xml:42(para) ./doc/config-reference/block-storage/drivers/nimble-volume-driver.xml:37(para)
|
||||
msgid "Manage and unmanage a volume"
|
||||
msgstr ""
|
||||
|
||||
@ -14794,14 +14794,143 @@ msgid "The SambaFS driver requires <placeholder-1/> version 1.7 or higher on Lin
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/block-storage/drivers/nimble-volume-driver.xml:6(title)
|
||||
msgid "Nimble volume driver"
|
||||
msgid "Nimble Storage volume driver"
|
||||
msgstr ""
|
||||
|
||||
#. <para>The volume driver configures XXX. More information about the driver is available at
|
||||
#. <xlink href="http://example.com">example.com</xlink>.
|
||||
#. </para>
|
||||
#: ./doc/config-reference/block-storage/drivers/nimble-volume-driver.xml:13(para)
|
||||
msgid "Set the following in your <filename>cinder.conf</filename> to use the Nimble volume driver:"
|
||||
#: ./doc/config-reference/block-storage/drivers/nimble-volume-driver.xml:7(para)
|
||||
msgid "Nimble Storage fully integrates with the OpenStack platform through the Nimble Cinder driver, allowing a host to configure and manage Nimble Storage array features through Block Storage interfaces."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/block-storage/drivers/nimble-volume-driver.xml:10(para)
|
||||
msgid "Support for the Liberty release is available from Nimble OS 2.3.8 or later."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/block-storage/drivers/nimble-volume-driver.xml:40(para)
|
||||
msgid "Enable encryption and default performance policy for a volume-type using extra-specs"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/block-storage/drivers/nimble-volume-driver.xml:45(para)
|
||||
msgid "The Nimble Storage implementation uses iSCSI only. Fibre Channel is not supported."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/block-storage/drivers/nimble-volume-driver.xml:50(title)
|
||||
msgid "Nimble Storage driver configuration"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/block-storage/drivers/nimble-volume-driver.xml:51(para)
|
||||
msgid "Update the file <filename>/etc/cinder/cinder.conf</filename> with the given configuration."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/block-storage/drivers/nimble-volume-driver.xml:53(para)
|
||||
msgid "In case of a basic (single back-end) configuration, add the parameters within the <literal>[default]</literal> section as follows."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/block-storage/drivers/nimble-volume-driver.xml:58(replaceable) ./doc/config-reference/block-storage/drivers/nimble-volume-driver.xml:72(replaceable) ./doc/config-reference/block-storage/drivers/nimble-volume-driver.xml:92(term)
|
||||
msgid "NIMBLE_MGMT_IP"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/block-storage/drivers/nimble-volume-driver.xml:59(replaceable) ./doc/config-reference/block-storage/drivers/nimble-volume-driver.xml:73(replaceable) ./doc/config-reference/block-storage/drivers/nimble-volume-driver.xml:98(term)
|
||||
msgid "NIMBLE_USER"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/block-storage/drivers/nimble-volume-driver.xml:60(replaceable) ./doc/config-reference/block-storage/drivers/nimble-volume-driver.xml:74(replaceable) ./doc/config-reference/block-storage/drivers/nimble-volume-driver.xml:105(term)
|
||||
msgid "NIMBLE_PASSWORD"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/block-storage/drivers/nimble-volume-driver.xml:63(para)
|
||||
msgid "In case of multi back-end configuration, for example, configuration which supports multiple Nimble Storage arrays or a single Nimble Storage array with arrays from other vendors, use the following parameters."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/block-storage/drivers/nimble-volume-driver.xml:76(replaceable) ./doc/config-reference/block-storage/drivers/nimble-volume-driver.xml:87(replaceable) ./doc/config-reference/block-storage/drivers/nimble-volume-driver.xml:111(term)
|
||||
msgid "NIMBLE_BACKEND_NAME"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/block-storage/drivers/nimble-volume-driver.xml:78(para)
|
||||
msgid "In case of multi back-end configuration, Nimble Storage volume-type is created and associated with a back-end name as follows."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/block-storage/drivers/nimble-volume-driver.xml:81(para)
|
||||
msgid "Single back-end configuration users do not need to create the volume-type."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/block-storage/drivers/nimble-volume-driver.xml:84(replaceable) ./doc/config-reference/block-storage/drivers/nimble-volume-driver.xml:86(replaceable) ./doc/config-reference/block-storage/drivers/nimble-volume-driver.xml:119(term)
|
||||
msgid "NIMBLE_VOLUME_TYPE"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/block-storage/drivers/nimble-volume-driver.xml:89(para)
|
||||
msgid "This section explains the variables used above:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/block-storage/drivers/nimble-volume-driver.xml:94(para)
|
||||
msgid "Management IP address of Nimble Storage array/group."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/block-storage/drivers/nimble-volume-driver.xml:100(para)
|
||||
msgid "Nimble Storage account login with minimum \"power user\"(admin) privilege if RBAC is used."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/block-storage/drivers/nimble-volume-driver.xml:107(para)
|
||||
msgid "Password of the admin account for nimble array."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/block-storage/drivers/nimble-volume-driver.xml:113(para)
|
||||
msgid "A volume back-end name which is specified in <filename> cinder.conf</filename>. This is also used while assigning a back- end name to the Nimble volume-type."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/block-storage/drivers/nimble-volume-driver.xml:121(para)
|
||||
msgid "The Nimble volume-type which is created from CLI and associated with <replaceable>NIMBLE_BACKEND_NAME</replaceable>."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/block-storage/drivers/nimble-volume-driver.xml:127(para)
|
||||
msgid "After updating the <filename>cinder.conf</filename>, the cinder-api, cinder-scheduler, and cinder-volume needs to be restarted."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/block-storage/drivers/nimble-volume-driver.xml:131(title)
|
||||
msgid "Nimble driver extra specs"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/block-storage/drivers/nimble-volume-driver.xml:132(para)
|
||||
msgid "Nimble volume driver also supports the following extra specs options:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/block-storage/drivers/nimble-volume-driver.xml:136(term)
|
||||
msgid "'nimble:encryption'='yes'"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/block-storage/drivers/nimble-volume-driver.xml:138(para)
|
||||
msgid "Used to enable encryption for a volume-type"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/block-storage/drivers/nimble-volume-driver.xml:142(term)
|
||||
msgid "'nimble:perfpol-name'=<replaceable>PERF_POL_NAME</replaceable>"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/block-storage/drivers/nimble-volume-driver.xml:145(para)
|
||||
msgid "PERF_POL_NAME is the name of a performance policy which exists on the Nimble array and should be enabled for every volume in a volume-type"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/block-storage/drivers/nimble-volume-driver.xml:151(para)
|
||||
msgid "These extra-specs can be enabled by using the following command:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/block-storage/drivers/nimble-volume-driver.xml:153(replaceable)
|
||||
msgid "\\ VOLUME_TYPE"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/block-storage/drivers/nimble-volume-driver.xml:154(replaceable)
|
||||
msgid "KEY"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/block-storage/drivers/nimble-volume-driver.xml:154(replaceable)
|
||||
msgid "\\ VALUE"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/block-storage/drivers/nimble-volume-driver.xml:156(para)
|
||||
msgid "VOLUME_TYPE is the Nimble volume-type and KEY and VALUE are the options mentioned above."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/block-storage/drivers/nimble-volume-driver.xml:161(para)
|
||||
msgid "The Nimble storage driver supports these configuration options:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/block-storage/drivers/scality-sofs-driver.xml:6(title)
|
||||
|
||||
@ -15,12 +15,12 @@ msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: Installation Guide 0.1\n"
|
||||
"Report-Msgid-Bugs-To: \n"
|
||||
"POT-Creation-Date: 2015-11-01 04:53+0000\n"
|
||||
"POT-Creation-Date: 2015-11-02 22:24+0000\n"
|
||||
"MIME-Version: 1.0\n"
|
||||
"Content-Type: text/plain; charset=UTF-8\n"
|
||||
"Content-Transfer-Encoding: 8bit\n"
|
||||
"PO-Revision-Date: 2015-11-02 05:57+0000\n"
|
||||
"Last-Translator: KATO Tomoyuki <kato.tomoyuki@jp.fujitsu.com>\n"
|
||||
"PO-Revision-Date: 2015-11-02 07:17+0000\n"
|
||||
"Last-Translator: Akihiro Motoki <amotoki@gmail.com>\n"
|
||||
"Language: ja\n"
|
||||
"Plural-Forms: nplurals=1; plural=0;\n"
|
||||
"X-Generator: Zanata 3.7.1\n"
|
||||
@ -1898,7 +1898,7 @@ msgstr "データベースクライアントを終了します。"
|
||||
msgid ""
|
||||
"Explanations of configuration options and sample configuration files are "
|
||||
"included."
|
||||
msgstr "設定オプションの説明およびサンプル設定ファイルがあります。"
|
||||
msgstr "設定オプションの説明および設定ファイル例が書かれています。"
|
||||
|
||||
msgid "Finalize installation"
|
||||
msgstr "インストールの最終作業"
|
||||
@ -5046,12 +5046,12 @@ msgid ""
|
||||
"can install any of these projects separately and configure them stand-alone "
|
||||
"or as connected entities."
|
||||
msgstr ""
|
||||
"OpenStack システムは、別々にインストールできるいくつかの主要なプロジェクトか"
|
||||
"ら構成されます。これらのプロジェクトは、クラウドの必要性によって一緒に動作で"
|
||||
"きます。Compute、Identity、Networking、Image service、Block Storage、Object "
|
||||
"Storage、Telemetry、Orchestration、Database です。これらのプロジェクトを別々"
|
||||
"にインストールして、スタンドアロンや接続されたエンティティーとして設定できま"
|
||||
"す。"
|
||||
"OpenStack システムは、別々にインストールできる複数の主要なプロジェクトから構"
|
||||
"成されます。クラウドの要件に応じて、これらのプロジェクトを組み合わあせて動作"
|
||||
"させます。Compute、Identity、Networking、Image service、Block Storage、"
|
||||
"Object Storage、Telemetry、Orchestration、Database などがあります。これらのプ"
|
||||
"ロジェクトを別々にインストールして、設定により単独で動かしたり組み合わせて動"
|
||||
"かしたりできます。"
|
||||
|
||||
msgid ""
|
||||
"The Orchestration service (heat) uses a heat orchestration template (HOT) to "
|
||||
@ -5627,7 +5627,7 @@ msgstr ""
|
||||
"十分にあるが、OpenStack は初めてというユーザーを対象にして書かれています。"
|
||||
|
||||
msgid "This guide documents OpenStack Liberty release."
|
||||
msgstr "このガイドは OpenStack Liberty リリースをドキュメント化しています。"
|
||||
msgstr "このガイドは OpenStack Liberty リリースについて記載しています。"
|
||||
|
||||
msgid ""
|
||||
"This guide shows you how to install OpenStack by using packages available on "
|
||||
@ -5635,7 +5635,7 @@ msgid ""
|
||||
msgstr ""
|
||||
"このガイドは、EPEL リポジトリー経由で Red Hat Enterprise Linux 7 および派生"
|
||||
"ディストリビューションにおいて利用可能なパッケージを使用して、OpenStack をイ"
|
||||
"ンストールする方法について説明しています。"
|
||||
"ンストールする方法について説明します。"
|
||||
|
||||
msgid ""
|
||||
"This guide shows you how to install OpenStack by using packages on openSUSE "
|
||||
@ -5643,8 +5643,8 @@ msgid ""
|
||||
"Cloud repository."
|
||||
msgstr ""
|
||||
"このガイドは、Open Build Service Cloud リポジトリー経由で openSUSE 13.2 や "
|
||||
"SUSE Linux Enterprise Server 12 においてパッケージを使用して、OpenStack をイ"
|
||||
"ンストールする方法について説明しています。"
|
||||
"SUSE Linux Enterprise Server 12 で利用可能なパッケージを使用して、OpenStack "
|
||||
"をインストールする方法について説明します。"
|
||||
|
||||
msgid ""
|
||||
"This guide uses a service project that contains a unique user for each "
|
||||
@ -5657,15 +5657,15 @@ msgid ""
|
||||
"This guide walks through an installation by using packages available through "
|
||||
"Canonical's Ubuntu Cloud archive repository."
|
||||
msgstr ""
|
||||
"このガイドは、Canonical の Ubuntu Cloud アーカイブリポジトリー において利用可"
|
||||
"能なパッケージを使用するインストールについて詳細に説明しています。"
|
||||
"このガイドは、Canonical の Ubuntu Cloud アーカイブリポジトリー で利用可能な"
|
||||
"パッケージを使用したインストールについて詳細に説明します。"
|
||||
|
||||
msgid ""
|
||||
"This guide walks through an installation by using packages available through "
|
||||
"Debian 8 (code name: Jessie)."
|
||||
msgstr ""
|
||||
"このガイドは、Debian 8 (コード名: Jessie) において利用可能なパッケージを使用"
|
||||
"するインストールについて詳細に説明しています。"
|
||||
"このガイドは、Debian 8 (コード名: Jessie) で利用可能なパッケージを使用したイ"
|
||||
"ンストールについて詳細に説明します。"
|
||||
|
||||
msgid ""
|
||||
"This information is stored in the configuration file for each service. For "
|
||||
@ -5885,10 +5885,11 @@ msgid ""
|
||||
"configuration deploys the Apache HTTP server to handle requests and "
|
||||
"Memcached to store tokens instead of an SQL database."
|
||||
msgstr ""
|
||||
"このセクションは、コントローラーノードに OpenStack Identity、コード名 "
|
||||
"keystone をインストールして設定する方法を説明します。この設定は、パフォーマン"
|
||||
"ス目的で、リクエストを処理するために Apache HTTP server を配備して、SQL デー"
|
||||
"タベースの代わりにトークンを保存するために Memcached を配備します。"
|
||||
"このセクションでは、コントローラーノードに OpenStack Identity サービス、コー"
|
||||
"ド名 keystone をインストールして設定する方法を説明します。この設定は、パ"
|
||||
"フォーマンス目的で、リクエストを処理するために Apache HTTP server を配備し"
|
||||
"て、SQL データベースの代わりにトークンを保存するために Memcached を配備しま"
|
||||
"す。"
|
||||
|
||||
msgid ""
|
||||
"This section describes how to install and configure the Telemetry service, "
|
||||
|
||||
@ -8,7 +8,7 @@ msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: Networking Guide 0.9\n"
|
||||
"Report-Msgid-Bugs-To: \n"
|
||||
"POT-Creation-Date: 2015-10-19 06:29+0000\n"
|
||||
"POT-Creation-Date: 2015-11-03 06:31+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"
|
||||
@ -77,11 +77,9 @@ msgstr ""
|
||||
# #-#-#-#-# adv_config_service_chaining.pot (Networking Guide 0.9) #-#-#-#-#
|
||||
# #-#-#-#-# adv_config_VPNaaS.pot (Networking Guide 0.9) #-#-#-#-#
|
||||
# #-#-#-#-# migration_legacy_to_dvr.pot (Networking Guide 0.9) #-#-#-#-#
|
||||
# #-#-#-#-# migration_legacy_to_L3_HA.pot (Networking Guide 0.9) #-#-#-#-#
|
||||
#: ../adv_config_VPNaaS.rst:5 ../adv_config_group_policy.rst:5
|
||||
#: ../adv_config_group_policy.rst:12 ../adv_config_operational.rst:5
|
||||
#: ../adv_config_service_chaining.rst:7 ../migration_legacy_to_L3_HA.rst:5
|
||||
#: ../migration_legacy_to_dvr.rst:5
|
||||
#: ../adv_config_service_chaining.rst:7 ../migration_legacy_to_dvr.rst:5
|
||||
msgid "TBD"
|
||||
msgstr ""
|
||||
|
||||
@ -3297,7 +3295,9 @@ msgid ""
|
||||
"encapsulates layer-2 Ethernet frames over layer-4 UDP packets."
|
||||
msgstr ""
|
||||
|
||||
#: ../migration.rst:3
|
||||
# #-#-#-#-# migration_legacy_to_L3_HA.pot (Networking Guide 0.9) #-#-#-#-#
|
||||
# #-#-#-#-# migration.pot (Networking Guide 0.9) #-#-#-#-#
|
||||
#: ../migration.rst:3 ../migration_legacy_to_L3_HA.rst:22
|
||||
msgid "Migration"
|
||||
msgstr ""
|
||||
|
||||
@ -3305,6 +3305,101 @@ msgstr ""
|
||||
msgid "Legacy to L3 HA"
|
||||
msgstr ""
|
||||
|
||||
#: ../migration_legacy_to_L3_HA.rst:5
|
||||
msgid ""
|
||||
"This section describes the process of migrating from a legacy router to an "
|
||||
"L3 HA router, which is available starting from the Mitaka release."
|
||||
msgstr ""
|
||||
|
||||
#: ../migration_legacy_to_L3_HA.rst:8
|
||||
msgid ""
|
||||
"Similar to the legacy scenario, all network traffic on a project network "
|
||||
"that requires routing actively traverses only one network node regardless of "
|
||||
"the quantity of network nodes providing HA for the router. Therefore, this "
|
||||
"high-availability implementation primarily addresses failure situations "
|
||||
"instead of bandwidth constraints that limit performance. However, it "
|
||||
"supports random distribution of routers on different network nodes to reduce "
|
||||
"the chances of bandwidth constraints and to improve scaling."
|
||||
msgstr ""
|
||||
|
||||
#: ../migration_legacy_to_L3_HA.rst:16
|
||||
msgid ""
|
||||
"This section summarizes parts of :doc:`scenario_l3ha_ovs` and :doc:"
|
||||
"`scenario_l3ha_lb`. For details regarding needed infrastructure and "
|
||||
"configuration to allow actual L3 HA deployment, read the relevant guide "
|
||||
"before continuing with the migration process."
|
||||
msgstr ""
|
||||
|
||||
#: ../migration_legacy_to_L3_HA.rst:24
|
||||
msgid ""
|
||||
"The migration process is quite simple, it involves turning down the router "
|
||||
"by setting the router's ``admin_state_up`` attribute to ``False``, upgrading "
|
||||
"the router to L3 HA and then setting the router's ``admin_state_up`` "
|
||||
"attribute back to ``True``."
|
||||
msgstr ""
|
||||
|
||||
#: ../migration_legacy_to_L3_HA.rst:30 ../migration_legacy_to_L3_HA.rst:104
|
||||
msgid ""
|
||||
"Once starting the migration, south-north connections (instances to internet) "
|
||||
"will be severed. New connections will be able to start only when the "
|
||||
"migration is complete."
|
||||
msgstr ""
|
||||
|
||||
#: ../migration_legacy_to_L3_HA.rst:34 ../migration_legacy_to_L3_HA.rst:108
|
||||
msgid "Here is the router we have used in our demonstration:"
|
||||
msgstr ""
|
||||
|
||||
# #-#-#-#-# migration_legacy_to_L3_HA.pot (Networking Guide 0.9) #-#-#-#-#
|
||||
# #-#-#-#-# scenario_dvr_ovs.pot (Networking Guide 0.9) #-#-#-#-#
|
||||
# #-#-#-#-# scenario_l3ha_lb.pot (Networking Guide 0.9) #-#-#-#-#
|
||||
# #-#-#-#-# scenario_l3ha_ovs.pot (Networking Guide 0.9) #-#-#-#-#
|
||||
# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-#
|
||||
# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-#
|
||||
# #-#-#-#-# scenario_provider_lb.pot (Networking Guide 0.9) #-#-#-#-#
|
||||
# #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-#
|
||||
#: ../migration_legacy_to_L3_HA.rst:53 ../migration_legacy_to_L3_HA.rst:127
|
||||
#: ../scenario_dvr_ovs.rst:730 ../scenario_dvr_ovs.rst:756
|
||||
#: ../scenario_dvr_ovs.rst:930 ../scenario_l3ha_lb.rst:422
|
||||
#: ../scenario_l3ha_lb.rst:448 ../scenario_l3ha_lb.rst:611
|
||||
#: ../scenario_l3ha_ovs.rst:432 ../scenario_l3ha_ovs.rst:458
|
||||
#: ../scenario_l3ha_ovs.rst:621 ../scenario_legacy_lb.rst:741
|
||||
#: ../scenario_legacy_lb.rst:763 ../scenario_legacy_ovs.rst:843
|
||||
#: ../scenario_legacy_ovs.rst:865 ../scenario_provider_lb.rst:491
|
||||
#: ../scenario_provider_lb.rst:512 ../scenario_provider_ovs.rst:542
|
||||
#: ../scenario_provider_ovs.rst:563
|
||||
msgid "Source the administrative project credentials."
|
||||
msgstr ""
|
||||
|
||||
#: ../migration_legacy_to_L3_HA.rst:54 ../migration_legacy_to_L3_HA.rst:128
|
||||
msgid ""
|
||||
"Set the admin_state_up to ``False``. This will severe south-north "
|
||||
"connections until admin_state_up is set to ``True`` again."
|
||||
msgstr ""
|
||||
|
||||
#: ../migration_legacy_to_L3_HA.rst:62 ../migration_legacy_to_L3_HA.rst:136
|
||||
msgid "Set the ``ha`` attribute of the router to ``True``."
|
||||
msgstr ""
|
||||
|
||||
#: ../migration_legacy_to_L3_HA.rst:69 ../migration_legacy_to_L3_HA.rst:143
|
||||
msgid ""
|
||||
"Set the admin_state_up to ``True``. This will severe south-north connections "
|
||||
"until admin_state_up is set to ``True`` again."
|
||||
msgstr ""
|
||||
|
||||
#: ../migration_legacy_to_L3_HA.rst:77 ../migration_legacy_to_L3_HA.rst:151
|
||||
msgid "Make sure that the router's ``ha`` attribute has changed to ``True``."
|
||||
msgstr ""
|
||||
|
||||
#: ../migration_legacy_to_L3_HA.rst:98
|
||||
msgid "L3 HA to Legacy"
|
||||
msgstr ""
|
||||
|
||||
#: ../migration_legacy_to_L3_HA.rst:100
|
||||
msgid ""
|
||||
"To return to legacy mode, you turn down the router again, turning off L3 HA "
|
||||
"and starting the router again"
|
||||
msgstr ""
|
||||
|
||||
#: ../migration_legacy_to_dvr.rst:3
|
||||
msgid "Legacy to DVR"
|
||||
msgstr ""
|
||||
@ -5109,25 +5204,6 @@ msgstr ""
|
||||
msgid "Verify service operation"
|
||||
msgstr ""
|
||||
|
||||
# #-#-#-#-# scenario_dvr_ovs.pot (Networking Guide 0.9) #-#-#-#-#
|
||||
# #-#-#-#-# scenario_l3ha_lb.pot (Networking Guide 0.9) #-#-#-#-#
|
||||
# #-#-#-#-# scenario_l3ha_ovs.pot (Networking Guide 0.9) #-#-#-#-#
|
||||
# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-#
|
||||
# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-#
|
||||
# #-#-#-#-# scenario_provider_lb.pot (Networking Guide 0.9) #-#-#-#-#
|
||||
# #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-#
|
||||
#: ../scenario_dvr_ovs.rst:730 ../scenario_dvr_ovs.rst:756
|
||||
#: ../scenario_dvr_ovs.rst:930 ../scenario_l3ha_lb.rst:422
|
||||
#: ../scenario_l3ha_lb.rst:448 ../scenario_l3ha_lb.rst:611
|
||||
#: ../scenario_l3ha_ovs.rst:432 ../scenario_l3ha_ovs.rst:458
|
||||
#: ../scenario_l3ha_ovs.rst:621 ../scenario_legacy_lb.rst:741
|
||||
#: ../scenario_legacy_lb.rst:763 ../scenario_legacy_ovs.rst:843
|
||||
#: ../scenario_legacy_ovs.rst:865 ../scenario_provider_lb.rst:491
|
||||
#: ../scenario_provider_lb.rst:512 ../scenario_provider_ovs.rst:542
|
||||
#: ../scenario_provider_ovs.rst:563
|
||||
msgid "Source the administrative project credentials."
|
||||
msgstr ""
|
||||
|
||||
# #-#-#-#-# scenario_dvr_ovs.pot (Networking Guide 0.9) #-#-#-#-#
|
||||
# #-#-#-#-# scenario_l3ha_lb.pot (Networking Guide 0.9) #-#-#-#-#
|
||||
# #-#-#-#-# scenario_l3ha_ovs.pot (Networking Guide 0.9) #-#-#-#-#
|
||||
|
||||
Loading…
Reference in New Issue
Block a user