Imported Translations from Transifex
For more information about this automatic import see: https://wiki.openstack.org/wiki/Translations/Infrastructure Change-Id: I5c2b39d5c51105054d4cc83459a055d886b9cfe4
This commit is contained in:
OpenStack Proposal Bot
parent
1d0429e037
commit
8a6b74a906
File diff suppressed because one or more lines are too long
@ -1,7 +1,7 @@
|
||||
msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: PACKAGE VERSION\n"
|
||||
"POT-Creation-Date: 2015-03-20 06:43+0000\n"
|
||||
"POT-Creation-Date: 2015-03-26 06:08+0000\n"
|
||||
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
|
||||
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
|
||||
"Language-Team: LANGUAGE <LL@li.org>\n"
|
||||
@ -586,7 +586,7 @@ msgid "Deployers must be aware of this and provide the appropriate customization
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/multi_site/section_operational_considerations_multi_site.xml:19(para)
|
||||
msgid "Note that, as of the Icehouse release, documentation for implementing this feature is in progress. See this bug for more information: <link href=\"https://bugs.launchpad.net/openstack-manuals/+bug/1340509\">https://bugs.launchpad.net/openstack-manuals/+bug/1340509</link>."
|
||||
msgid "As of the Icehouse release, documentation for implementing this feature is in progress. See this bug for more information: <link href=\"https://bugs.launchpad.net/openstack-manuals/+bug/1340509\">https://bugs.launchpad.net/openstack-manuals/+bug/1340509</link>."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/multi_site/section_operational_considerations_multi_site.xml:26(title)
|
||||
@ -718,7 +718,7 @@ msgid "Documentation"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/multi_site/section_operational_considerations_multi_site.xml:173(para)
|
||||
msgid "Users must be able to leverage cloud infrastructure and provision new resources in the environment. It is important that user documentation is accessible by users of the cloud infrastructure to ensure they are given sufficient information to help them leverage the cloud. As an example, by default OpenStack will schedule instances on a compute node automatically. However, when multiple regions are available, it is left to the end user to decide in which region to schedule the new instance. The dashboard will present the user with the first region in your configuration. The API and CLI tools will not execute commands unless a valid region is specified. It is therefore important to provide documentation to your users describing the region layout as well as calling out that quotas are region-specific. If a user reaches his or her quota in one region, OpenStack will not automatically build new instances in another. Documenting specific examples will help users understand how to operate the cloud, thereby reducing calls and tickets filed with the help desk."
|
||||
msgid "Users must be able to leverage cloud infrastructure and provision new resources in the environment. It is important that user documentation is accessible by users of the cloud infrastructure to ensure they are given sufficient information to help them leverage the cloud. As an example, by default OpenStack schedules instances on a compute node automatically. However, when multiple regions are available, it is left to the end user to decide in which region to schedule the new instance. The dashboard presents the user with the first region in your configuration. The API and CLI tools do not execute commands unless a valid region is specified. It is therefore important to provide documentation to your users describing the region layout as well as calling out that quotas are region-specific. If a user reaches his or her quota in one region, OpenStack does not automatically build new instances in another. Documenting specific examples helps users understand how to operate the cloud, thereby reducing calls and tickets filed with the help desk."
|
||||
msgstr ""
|
||||
|
||||
#. When image changes, this message will be marked fuzzy or untranslated for you.
|
||||
@ -732,7 +732,7 @@ msgid "Architecture"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/multi_site/section_architecture_multi_site.xml:9(para)
|
||||
msgid "This graphic is a high level diagram of a multiple site OpenStack architecture. Each site is an OpenStack cloud but it may be necessary to architect the sites on different versions. For example, if the second site is intended to be a replacement for the first site, they would be different. Another common design would be a private OpenStack cloud with replicated site that would be used for high availability or disaster recovery. The most important design decision is how to configure the storage. It can be configured as a single shared pool or separate pools, depending on the user and technical requirements."
|
||||
msgid "This graphic is a high level diagram of a multi-site OpenStack architecture. Each site is an OpenStack cloud but it may be necessary to architect the sites on different versions. For example, if the second site is intended to be a replacement for the first site, they would be different. Another common design would be a private OpenStack cloud with replicated site that would be used for high availability or disaster recovery. The most important design decision is how to configure the storage. It can be configured as a single shared pool or separate pools, depending on the user and technical requirements."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/multi_site/section_architecture_multi_site.xml:25(title)
|
||||
@ -784,11 +784,11 @@ msgid "Dependencies"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/multi_site/section_architecture_multi_site.xml:103(para)
|
||||
msgid "The architecture for a multi-site installation of OpenStack is dependent on a number of factors. One major dependency to consider is storage. When designing the storage system, the storage mechanism needs to be determined. Once the storage type is determined, how it will be accessed is critical. For example, we recommend that storage should use a dedicated network. Another concern is how the storage is configured to protect the data. For example, the recovery point objective (RPO) and the recovery time objective (RTO). How quickly can the recovery from a fault be completed, will determine how often the replication of data be required. Ensure that enough storage is allocated to support the data protection strategy."
|
||||
msgid "The architecture for a multi-site installation of OpenStack is dependent on a number of factors. One major dependency to consider is storage. When designing the storage system, the storage mechanism needs to be determined. Once the storage type is determined, how it is accessed is critical. For example, we recommend that storage should use a dedicated network. Another concern is how the storage is configured to protect the data. For example, the recovery point objective (RPO) and the recovery time objective (RTO). How quickly can the recovery from a fault be completed, determines how often the replication of data is required. Ensure that enough storage is allocated to support the data protection strategy."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/multi_site/section_architecture_multi_site.xml:115(para)
|
||||
msgid "Networking decisions include the encapsulation mechanism that will be used for the tenant networks, how large the broadcast domains should be, and the contracted SLAs for the interconnects."
|
||||
msgid "Networking decisions include the encapsulation mechanism that can be used for the tenant networks, how large the broadcast domains should be, and the contracted SLAs for the interconnects."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/multi_site/section_user_requirements_multi_site.xml:8(title) ./doc/arch-design/network_focus/section_user_requirements_network_focus.xml:8(title) ./doc/arch-design/generalpurpose/section_user_requirements_general_purpose.xml:8(title) ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:416(term) ./doc/arch-design/compute_focus/section_user_requirements_compute_focus.xml:12(title) ./doc/arch-design/hybrid/section_user_requirements_hybrid.xml:8(title) ./doc/arch-design/massively_scalable/section_user_requirements_massively_scalable.xml:8(title) ./doc/arch-design/massively_scalable/section_user_requirements_massively_scalable.xml:52(title) ./doc/arch-design/storage_focus/section_user_requirements_storage_focus.xml:8(title)
|
||||
@ -844,11 +844,11 @@ msgid "Consistency of images and templates across different sites"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/multi_site/section_user_requirements_multi_site.xml:74(para)
|
||||
msgid "It is essential that the deployment of instances is consistent across the different sites. This needs to be built into the infrastructure. If the OpenStack Object Storage is used as a back end for the Image Service, it is possible to create repositories of consistent images across multiple sites. Having central endpoints with multiple storage nodes will allow for consistent centralized storage for each and every site."
|
||||
msgid "It is essential that the deployment of instances is consistent across the different sites. This needs to be built into the infrastructure. If the OpenStack Object Storage is used as a back end for the Image Service, it is possible to create repositories of consistent images across multiple sites. Having central endpoints with multiple storage nodes allows consistent centralized storage for each and every site."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/multi_site/section_user_requirements_multi_site.xml:81(para)
|
||||
msgid "Not using a centralized object store will increase operational overhead so that a consistent image library can be maintained. This could include development of a replication mechanism to handle the transport of images and the changes to the images across multiple sites."
|
||||
msgid "Not using a centralized object store increases operational overhead so that a consistent image library can be maintained. This could include development of a replication mechanism to handle the transport of images and the changes to the images across multiple sites."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/multi_site/section_user_requirements_multi_site.xml:87(para)
|
||||
@ -868,7 +868,7 @@ msgid "Multiple network links should be deployed between sites to provide redund
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/multi_site/section_user_requirements_multi_site.xml:108(para)
|
||||
msgid "The ability to maintain object availability in both sites has significant implications on the object storage design and implementation. It will also have a significant impact on the WAN network design between the sites."
|
||||
msgid "The ability to maintain object availability in both sites has significant implications on the object storage design and implementation. It also has a significant impact on the WAN network design between the sites."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/multi_site/section_user_requirements_multi_site.xml:112(para)
|
||||
@ -928,7 +928,7 @@ msgid "The deployed applications need to continue to function and, more importan
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/multi_site/section_user_requirements_multi_site.xml:178(para)
|
||||
msgid "It is important to understand what will happen to the replication of objects and data between the sites when a site goes down. If this causes queues to start building up, consider how long these queues can safely exist until something explodes."
|
||||
msgid "It is important to understand what happens to the replication of objects and data between the sites when a site goes down. If this causes queues to start building up, consider how long these queues can safely exist until something explodes."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/multi_site/section_user_requirements_multi_site.xml:185(para)
|
||||
@ -964,18 +964,18 @@ msgid "Authentication between sites"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/multi_site/section_user_requirements_multi_site.xml:213(para)
|
||||
msgid "Ideally it is best to have a single authentication domain and not need a separate implementation for each and every site. This will, of course, require an authentication mechanism that is highly available and distributed to ensure continuous operation. Authentication server locality is also something that might be needed as well and should be planned for."
|
||||
msgid "Ideally it is best to have a single authentication domain and not need a separate implementation for each and every site. This, of course, requires an authentication mechanism that is highly available and distributed to ensure continuous operation. Authentication server locality is also something that might be needed as well and should be planned for."
|
||||
msgstr ""
|
||||
|
||||
#. 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.
|
||||
#: ./doc/arch-design/multi_site/section_prescriptive_examples_multi_site.xml:86(None)
|
||||
#: ./doc/arch-design/multi_site/section_prescriptive_examples_multi_site.xml:85(None)
|
||||
msgid "@@image: '../figures/Multi-Site_Customer_Edge.png'; md5=01850cf774e7075bd7202c6e7f087f36"
|
||||
msgstr ""
|
||||
|
||||
#. 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.
|
||||
#: ./doc/arch-design/multi_site/section_prescriptive_examples_multi_site.xml:190(None)
|
||||
#: ./doc/arch-design/multi_site/section_prescriptive_examples_multi_site.xml:191(None)
|
||||
msgid "@@image: '../figures/Multi-site_Geo_Redundant_LB.png'; md5=c94a96f6084c2e50a0eb6846f6fde479"
|
||||
msgstr ""
|
||||
|
||||
@ -990,115 +990,119 @@ msgid "Prescriptive examples"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/multi_site/section_prescriptive_examples_multi_site.xml:13(para)
|
||||
msgid "Based on the needs of the intended workloads, there are multiple ways to build a multi-site OpenStack installation. Below are example architectures based on different requirements. These examples are meant as a reference, and not a hard and fast rule for deployments. Use the previous sections of this chapter to assist in selecting specific components and implementations based on specific needs."
|
||||
msgid "There are multiple ways to build a multi-site OpenStack installation, based on the needs of the intended workloads. Below are example architectures based on different requirements. These examples are meant as a reference, and not a hard and fast rule for deployments. Use the previous sections of this chapter to assist in selecting specific components and implementations based on specific needs."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/multi_site/section_prescriptive_examples_multi_site.xml:20(para)
|
||||
msgid "A large content provider needs to deliver content to customers that are geographically dispersed. The workload is very sensitive to latency and needs a rapid response to end-users. After reviewing the user, technical and operational considerations, it is determined beneficial to build a number of regions local to the customer's edge. In this case rather than build a few large, centralized data centers, the intent of the architecture is to provide a pair of small data centers in locations that are closer to the customer. In this use case, spreading applications out allows for different horizontal scaling than a traditional compute workload scale. The intent is to scale by creating more copies of the application in closer proximity to the users that need it most, in order to ensure faster response time to user requests. This provider will deploy two datacenters at each of the four chosen regions. The implications of this design are based around the method of placing copies of resources in each of the remote regions. Swift objects, Glance images, and block storage will need to be manually replicated into each region. This may be beneficial for some systems, such as the case of content service, where only some of the content needs to exist in some but not all regions. A centralized Keystone is recommended to ensure authentication and that access to the API endpoints is easily manageable."
|
||||
msgid "A large content provider needs to deliver content to customers that are geographically dispersed. The workload is very sensitive to latency and needs a rapid response to end-users. After reviewing the user, technical and operational considerations, it is determined beneficial to build a number of regions local to the customer's edge. In this case rather than build a few large, centralized data centers, the intent of the architecture is to provide a pair of small data centers in locations that are closer to the customer. In this use case, spreading applications out allows for different horizontal scaling than a traditional compute workload scale. The intent is to scale by creating more copies of the application in closer proximity to the users that need it most, in order to ensure faster response time to user requests. This provider deploys two datacenters at each of the four chosen regions. The implications of this design are based around the method of placing copies of resources in each of the remote regions. Swift objects, Glance images, and block storage need to be manually replicated into each region. This may be beneficial for some systems, such as the case of content service, where only some of the content needs to exist in some but not all regions. A centralized Keystone is recommended to ensure authentication and that access to the API endpoints is easily manageable."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/multi_site/section_prescriptive_examples_multi_site.xml:44(para)
|
||||
msgid "Installation of an automated DNS system such as Designate is highly recommended. Unless an external Dynamic DNS system is available, application administrators will need a way to manage the mapping of which application copy exists in each region and how to reach it. Designate will assist by making the process automatic and by populating the records in the each region's zone."
|
||||
msgid "It is recommended that you install an automated DNS system such as Designate. Application administrators need a way to manage the mapping of which application copy exists in each region and how to reach it, unless an external Dynamic DNS system is available. Designate assists by making the process automatic and by populating the records in the each region's zone."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/multi_site/section_prescriptive_examples_multi_site.xml:51(para)
|
||||
msgid "Telemetry for each region is also deployed, as each region may grow differently or be used at a different rate. Ceilometer will run to collect each region's metrics from each of the controllers and report them back to a central location. This is useful both to the end user and the administrator of the OpenStack environment. The end user will find this method useful, in that it is possible to determine if certain locations are experiencing higher load than others, and take appropriate action. Administrators will also benefit by possibly being able to forecast growth per region, rather than expanding the capacity of all regions simultaneously, therefore maximizing the cost-effectiveness of the multi-site design."
|
||||
#: ./doc/arch-design/multi_site/section_prescriptive_examples_multi_site.xml:50(para)
|
||||
msgid "Telemetry for each region is also deployed, as each region may grow differently or be used at a different rate. Ceilometer collects each region's metrics from each of the controllers and report them back to a central location. This is useful both to the end user and the administrator of the OpenStack environment. The end user will find this method useful, as it makes possible to determine if certain locations are experiencing higher load than others, and take appropriate action. Administrators also benefit by possibly being able to forecast growth per region, rather than expanding the capacity of all regions simultaneously, therefore maximizing the cost-effectiveness of the multi-site design."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/multi_site/section_prescriptive_examples_multi_site.xml:64(para)
|
||||
msgid "One of the key decisions of running this sort of infrastructure is whether or not to provide a redundancy model. Two types of redundancy and high availability models in this configuration will be implemented. The first type revolves around the availability of the central OpenStack components. Keystone will be made highly available in three central data centers that will host the centralized OpenStack components. This prevents a loss of any 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 for distributing content to each of the regions."
|
||||
#: ./doc/arch-design/multi_site/section_prescriptive_examples_multi_site.xml:63(para)
|
||||
msgid "One of the key decisions of running this sort of infrastructure is whether or not to provide a redundancy model. Two types of redundancy and high availability models in this configuration can be implemented. The first type revolves around the availability of the central OpenStack components. Keystone can be made highly available in three central data centers that host the centralized OpenStack components. This prevents a loss of any 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 for distributing content to each of the regions."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/multi_site/section_prescriptive_examples_multi_site.xml:75(para)
|
||||
msgid "The second redundancy topic is that of the edge data center itself. 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 degraded performance in terms of latency and availability."
|
||||
#: ./doc/arch-design/multi_site/section_prescriptive_examples_multi_site.xml:74(para)
|
||||
msgid "The second redundancy topic is that of the edge data center itself. A second data center in each of the edge regional locations house a second region near the first. This ensures that the application does not suffer degraded performance in terms of latency and availability."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/multi_site/section_prescriptive_examples_multi_site.xml:80(para)
|
||||
#: ./doc/arch-design/multi_site/section_prescriptive_examples_multi_site.xml:79(para)
|
||||
msgid "This figure depicts the solution designed to have both a centralized set of core data centers for OpenStack services and paired edge data centers:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/multi_site/section_prescriptive_examples_multi_site.xml:90(title)
|
||||
#: ./doc/arch-design/multi_site/section_prescriptive_examples_multi_site.xml:89(title)
|
||||
msgid "Geo-redundant load balancing"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/multi_site/section_prescriptive_examples_multi_site.xml:91(para)
|
||||
#: ./doc/arch-design/multi_site/section_prescriptive_examples_multi_site.xml:90(para)
|
||||
msgid "A large-scale web application has been designed with cloud principles in mind. The application is designed provide service to application store, on a 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 the information."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/multi_site/section_prescriptive_examples_multi_site.xml:97(para)
|
||||
#: ./doc/arch-design/multi_site/section_prescriptive_examples_multi_site.xml:96(para)
|
||||
msgid "As of late there has been several outages in number of major public cloud providersusually due to the fact these applications were running out of a single geographical location. The design therefore should mitigate the chance of a single site causing an outage for their business."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/multi_site/section_prescriptive_examples_multi_site.xml:102(para) ./doc/arch-design/generalpurpose/section_prescriptive_example_general_purpose.xml:30(para)
|
||||
#: ./doc/arch-design/multi_site/section_prescriptive_examples_multi_site.xml:101(para) ./doc/arch-design/generalpurpose/section_prescriptive_example_general_purpose.xml:30(para)
|
||||
msgid "The solution would consist of the following OpenStack components:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/multi_site/section_prescriptive_examples_multi_site.xml:106(para) ./doc/arch-design/generalpurpose/section_prescriptive_example_general_purpose.xml:34(para)
|
||||
#: ./doc/arch-design/multi_site/section_prescriptive_examples_multi_site.xml:105(para) ./doc/arch-design/generalpurpose/section_prescriptive_example_general_purpose.xml:34(para)
|
||||
msgid "A firewall, switches and load balancers on the public facing network connections."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/multi_site/section_prescriptive_examples_multi_site.xml:110(para)
|
||||
msgid "OpenStack Controller services running, Networking, dashboard, Block Storage and Compute running locally in each of the three regions. The other services, Identity, Orchestration, Telemetry, Image Service and Object Storage will be installed centrallywith nodes in each of the region providing a redundant OpenStack Controller plane throughout the globe."
|
||||
#: ./doc/arch-design/multi_site/section_prescriptive_examples_multi_site.xml:109(para)
|
||||
msgid "OpenStack Controller services running, Networking, dashboard, Block Storage and Compute running locally in each of the three regions. The other services, Identity, Orchestration, Telemetry, Image Service and Object Storage can be installed centrallywith 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:120(para) ./doc/arch-design/generalpurpose/section_prescriptive_example_general_purpose.xml:44(para)
|
||||
#: ./doc/arch-design/multi_site/section_prescriptive_examples_multi_site.xml:119(para) ./doc/arch-design/generalpurpose/section_prescriptive_example_general_purpose.xml:44(para)
|
||||
msgid "OpenStack Compute nodes running the KVM hypervisor."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/multi_site/section_prescriptive_examples_multi_site.xml:124(para)
|
||||
msgid "OpenStack Object Storage for serving static objects such as images will be used to ensure that all images are standardized across all the regions, and replicated on a regular basis."
|
||||
#: ./doc/arch-design/multi_site/section_prescriptive_examples_multi_site.xml:123(para)
|
||||
msgid "OpenStack Object Storage for serving static objects such as images can be used to ensure that all images are standardized across all the regions, and replicated on a regular basis."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/multi_site/section_prescriptive_examples_multi_site.xml:130(para)
|
||||
#: ./doc/arch-design/multi_site/section_prescriptive_examples_multi_site.xml:129(para)
|
||||
msgid "A Distributed DNS service available to all regionsthat allows for dynamic update of DNS records of deployed instances."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/multi_site/section_prescriptive_examples_multi_site.xml:135(para)
|
||||
msgid "A geo-redundant load balancing service will be used to service the requests from the customers based on their origin."
|
||||
#: ./doc/arch-design/multi_site/section_prescriptive_examples_multi_site.xml:134(para)
|
||||
msgid "A geo-redundant load balancing service can be used to service the requests from the customers based on their origin."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/multi_site/section_prescriptive_examples_multi_site.xml:140(para)
|
||||
msgid "An autoscaling heat template will used to deploy the application in the three regions. This template will include:"
|
||||
#: ./doc/arch-design/multi_site/section_prescriptive_examples_multi_site.xml:139(para)
|
||||
msgid "An autoscaling heat template can be used to deploy the application in the three regions. This template includes:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/multi_site/section_prescriptive_examples_multi_site.xml:145(para)
|
||||
#: ./doc/arch-design/multi_site/section_prescriptive_examples_multi_site.xml:143(para)
|
||||
msgid "Web Servers, running Apache."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/multi_site/section_prescriptive_examples_multi_site.xml:148(para)
|
||||
#: ./doc/arch-design/multi_site/section_prescriptive_examples_multi_site.xml:146(para)
|
||||
msgid "Appropriate <literal>user_data</literal> to populate the central DNS servers upon instance launch."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/multi_site/section_prescriptive_examples_multi_site.xml:152(para)
|
||||
#: ./doc/arch-design/multi_site/section_prescriptive_examples_multi_site.xml:150(para)
|
||||
msgid "Appropriate Telemetry alarms that maintain state of the application and allow for handling of region or instance failure."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/multi_site/section_prescriptive_examples_multi_site.xml:157(para)
|
||||
msgid "Another autoscaling Heat template will be used to deploy a distributed MongoDB shard over the three locationswith the option of storing required data on a globally available swift container. according to the usage and load on the database serveradditional shards will be provisioned according to the thresholds defined in Telemetry."
|
||||
#: ./doc/arch-design/multi_site/section_prescriptive_examples_multi_site.xml:155(para)
|
||||
msgid "Another autoscaling Heat template can be used to deploy a distributed MongoDB shard over the three locationswith the option of storing required data on a globally available swift container. According to the usage and load on the database serveradditional shards can be provisioned according to the thresholds defined in Telemetry."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/multi_site/section_prescriptive_examples_multi_site.xml:163(para)
|
||||
msgid "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 center would have been sufficient had the requirements been met."
|
||||
#. <para>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 center would have been sufficient
|
||||
#. had the requirements been met.</para>
|
||||
#: ./doc/arch-design/multi_site/section_prescriptive_examples_multi_site.xml:165(para)
|
||||
msgid "Two data centers would have been sufficient had the requirements been met. But three regions are selected here to avoid abnormal load on a single region in the event of a failure."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/multi_site/section_prescriptive_examples_multi_site.xml:167(para)
|
||||
#: ./doc/arch-design/multi_site/section_prescriptive_examples_multi_site.xml:168(para)
|
||||
msgid "Orchestration is used because of the built-in functionality of autoscaling and auto healing in the event of increased load. Additional configuration management tools, such as Puppet or Chef could also have been used in this scenario, but were not chosen due to the fact that Orchestration had the appropriate built-in hooks into the OpenStack cloudwhereas the other tools were external and not native to OpenStack. In additionsince this deployment scenario was relatively straight forwardthe external tools were not needed."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/multi_site/section_prescriptive_examples_multi_site.xml:176(para)
|
||||
msgid "OpenStack Object Storage is used here to serve as a back end for the Image Service since was the most suitable solution for a globally distributed storage solutionwith its own replication mechanism. Home grown solutions could also have been used including the handling of replicationbut were not chosen, because Object Storage is already an intricate part of the infrastructureand proven solution."
|
||||
#: ./doc/arch-design/multi_site/section_prescriptive_examples_multi_site.xml:177(para)
|
||||
msgid "OpenStack Object Storage is used here to serve as a back end for the Image Service since it is the most suitable solution for a globally distributed storage solutionwith its own replication mechanism. Home grown solutions could also have been used including the handling of replicationbut were not chosen, because Object Storage is already an intricate part of the infrastructureand proven solution."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/multi_site/section_prescriptive_examples_multi_site.xml:184(para)
|
||||
#: ./doc/arch-design/multi_site/section_prescriptive_examples_multi_site.xml:185(para)
|
||||
msgid "An external load balancing service was used and not the LBaaS in OpenStack because the solution in OpenStack is not redundant and does not have any awareness of geo location."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/multi_site/section_prescriptive_examples_multi_site.xml:193(title)
|
||||
#: ./doc/arch-design/multi_site/section_prescriptive_examples_multi_site.xml:194(title)
|
||||
msgid "Location-local service"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/multi_site/section_prescriptive_examples_multi_site.xml:194(para)
|
||||
msgid "A common use for a multi-site deployment of OpenStack, is for creating a Content Delivery Network. An application that uses a location-local architecture will require low network latency and proximity to the user, in order to provide an optimal user experience, in addition to reducing the cost of bandwidth and transit, since the content resides on sites closer to the customer, instead of a centralized content store that would require utilizing higher cost cross country links."
|
||||
#: ./doc/arch-design/multi_site/section_prescriptive_examples_multi_site.xml:195(para)
|
||||
msgid "A common use for a multi-site deployment of OpenStack, is for creating a Content Delivery Network. An application that uses a location-local architecture requires low network latency and proximity to the user, in order to provide an optimal user experience, in addition to reducing the cost of bandwidth and transit, since the content resides on sites closer to the customer, instead of a centralized content store that requires utilizing higher cost cross-country links."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/multi_site/section_prescriptive_examples_multi_site.xml:203(para)
|
||||
@ -1106,7 +1110,7 @@ msgid "This architecture usually includes a geo-location component that places u
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/multi_site/section_prescriptive_examples_multi_site.xml:212(para)
|
||||
msgid "In this example, the application utilizing this multi-site OpenStack install that is location aware would launch web server or content serving instances on the compute cluster in each site. Requests from clients will first be 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 application completes the request."
|
||||
msgid "In this example, the application utilizing this multi-site OpenStack install that is location aware would launch web server or content serving instances on the compute cluster in each site. Requests from clients are first 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 application completes the request."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/multi_site/section_tech_considerations_multi_site.xml:8(title) ./doc/arch-design/network_focus/section_tech_considerations_network_focus.xml:8(title) ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:12(title) ./doc/arch-design/compute_focus/section_user_requirements_compute_focus.xml:90(title) ./doc/arch-design/compute_focus/section_tech_considerations_compute_focus.xml:12(title) ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:12(title) ./doc/arch-design/massively_scalable/section_tech_considerations_massively_scalable.xml:12(title) ./doc/arch-design/storage_focus/section_tech_considerations_storage_focus.xml:8(title)
|
||||
@ -1114,7 +1118,7 @@ msgid "Technical considerations"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/multi_site/section_tech_considerations_multi_site.xml:9(para)
|
||||
msgid "There are many technical considerations to take into account with regard to designing a multi-site OpenStack implementation. An OpenStack cloud can be designed in a variety of ways to handle individual application needs. A multi-site deployment will have additional challenges compared to single site installations and will therefore be a more complex solution."
|
||||
msgid "There are many technical considerations to take into account with regard to designing a multi-site OpenStack implementation. An OpenStack cloud can be designed in a variety of ways to handle individual application needs. A multi-site deployment has additional challenges compared to single site installations and therefore is a more complex solution."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/multi_site/section_tech_considerations_multi_site.xml:16(para)
|
||||
@ -1122,15 +1126,15 @@ msgid "When determining capacity options be sure to take into account not just t
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/multi_site/section_tech_considerations_multi_site.xml:20(para)
|
||||
msgid "Inter-site link capacity describes the capabilities of the connectivity between the different OpenStack sites. This includes parameters such as bandwidth, latency, whether or not a link is dedicated, and any business policies applied to the connection. The capability and number of the links between sites will determine what kind of options may be available for deployment. For example, if two sites have a pair of high-bandwidth links available between them, it may be wise to configure a separate storage replication network between the two sites to support a single Swift endpoint and a shared object storage capability between them. (An example of this technique, as well as a configuration walk-through, is available at <link href=\"http://docs.openstack.org/developer/swift/replication_network.html#dedicated-replication-network\">http://docs.openstack.org/developer/swift/replication_network.html#dedicated-replication-network</link>). Another option in this scenario is to build a dedicated set of tenant private networks across the secondary link using overlay networks with a third party mapping the site overlays to each other."
|
||||
msgid "Inter-site link capacity describes the capabilities of the connectivity between the different OpenStack sites. This includes parameters such as bandwidth, latency, whether or not a link is dedicated, and any business policies applied to the connection. The capability and number of the links between sites determine what kind of options are available for deployment. For example, if two sites have a pair of high-bandwidth links available between them, it may be wise to configure a separate storage replication network between the two sites to support a single Swift endpoint and a shared object storage capability between them. (An example of this technique, as well as a configuration walk-through, is available at <link href=\"http://docs.openstack.org/developer/swift/replication_network.html#dedicated-replication-network\">http://docs.openstack.org/developer/swift/replication_network.html#dedicated-replication-network</link>). Another option in this scenario is to build a dedicated set of tenant private networks across the secondary link using overlay networks with a third party mapping the site overlays to each other."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/multi_site/section_tech_considerations_multi_site.xml:38(para)
|
||||
msgid "The capacity requirements of the links between sites will be driven by application behavior. If the latency of the links is too high, certain applications that use a large number of small packets, for example RPC calls, may encounter issues communicating with each other or operating properly. Additionally, OpenStack may encounter similar types of issues. To mitigate this, tuning of the Identity service call timeouts may be necessary to prevent issues authenticating against a central Identity service."
|
||||
msgid "The capacity requirements of the links between sites is driven by application behavior. If the latency of the links is too high, certain applications that use a large number of small packets, for example RPC calls, may encounter issues communicating with each other or operating properly. Additionally, OpenStack may encounter similar types of issues. To mitigate this, tuning of the Identity service call timeouts may be necessary to prevent issues authenticating against a central Identity service."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/multi_site/section_tech_considerations_multi_site.xml:47(para)
|
||||
msgid "Another capacity consideration when it comes to networking for a multi-site deployment is the available amount and performance of overlay networks for tenant networks. If using shared tenant networks across zones, it is imperative that an external overlay manager or controller be used to map these overlays together. It is necessary to ensure the amount of possible IDs between the zones are identical. Note that, as of the Icehouse release, OpenStack Networking was not capable of managing tunnel IDs across installations. This means that if one site runs out of IDs, but other does not, that tenant's network will be unable to reach the other site."
|
||||
msgid "Another capacity consideration when it comes to networking for a multi-site deployment is the available amount and performance of overlay networks for tenant networks. If using shared tenant networks across zones, it is imperative that an external overlay manager or controller be used to map these overlays together. It is necessary to ensure the amount of possible IDs between the zones are identical. Note that, as of the Icehouse release, OpenStack Networking was not capable of managing tunnel IDs across installations. This means that if one site runs out of IDs, but other does not, that tenant's network is unable to reach the other site."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/multi_site/section_tech_considerations_multi_site.xml:58(para)
|
||||
@ -1154,11 +1158,11 @@ msgid "Identity is normally the first interface for the majority of OpenStack us
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/multi_site/section_tech_considerations_multi_site.xml:94(para)
|
||||
msgid "Load balancing is another common issue with multi-site installations. While it is still possible to run HAproxy instances with Load-Balancer-as-a-Service, these will be local to a specific region. Some applications may be able to cope with this via internal mechanisms. Others, however, may require the implementation of an external system including global services load balancers or anycast-advertised DNS."
|
||||
msgid "Load balancing is another common issue with multi-site installations. While it is still possible to run HAproxy instances with Load-Balancer-as-a-Service, these are local to a specific region. Some applications may be able to cope with this via internal mechanisms. Others, however, may require the implementation of an external system including global services load balancers or anycast-advertised DNS."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/multi_site/section_tech_considerations_multi_site.xml:102(para)
|
||||
msgid "Depending on the storage model chosen during site design, storage replication and availability will also be a concern for end-users. If an application is capable of understanding regions, then it is possible to keep the object storage system separated by region. In this case, users who want to have an object available to more than one region will need to do the cross-site replication themselves. With a centralized swift proxy, however, the user may need to benchmark the replication timing of the Object Storage back end. Benchmarking allows the operational staff to provide users with an understanding of the amount of time required for a stored or modified object to become available to the entire environment."
|
||||
msgid "Depending on the storage model chosen during site design, storage replication and availability are also a concern for end-users. If an application is capable of understanding regions, then it is possible to keep the object storage system separated by region. In this case, users who want to have an object available to more than one region need to do the cross-site replication themselves. With a centralized swift proxy, however, the user may need to benchmark the replication timing of the Object Storage back end. Benchmarking allows the operational staff to provide users with an understanding of the amount of time required for a stored or modified object to become available to the entire environment."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/multi_site/section_tech_considerations_multi_site.xml:114(title) ./doc/arch-design/network_focus/section_tech_considerations_network_focus.xml:432(title) ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:387(term) ./doc/arch-design/generalpurpose/section_user_requirements_general_purpose.xml:120(term) ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:590(title) ./doc/arch-design/compute_focus/section_user_requirements_compute_focus.xml:96(term) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:177(term) ./doc/arch-design/compute_focus/section_tech_considerations_compute_focus.xml:257(title) ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:253(title) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:18(para) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:42(term) ./doc/arch-design/storage_focus/section_user_requirements_storage_focus.xml:12(para) ./doc/arch-design/storage_focus/section_user_requirements_storage_focus.xml:119(term)
|
||||
@ -1174,7 +1178,7 @@ msgid "Since multi-site systems can be geographically separated, they may have w
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/multi_site/section_tech_considerations_multi_site.xml:129(para)
|
||||
msgid "Storage availability can also be impacted by the architecture of a multi-site deployment. A centralized Object Storage service requires more time for an object to be available to instances locally in regions where the object was not created. Some applications may need to be tuned to account for this effect. Block Storage does not currently have a method for replicating data across multiple regions, so applications that depend on available block storage will need to manually cope with this limitation by creating duplicate block storage entries in each region."
|
||||
msgid "Storage availability can also be impacted by the architecture of a multi-site deployment. A centralized Object Storage service requires more time for an object to be available to instances locally in regions where the object was not created. Some applications may need to be tuned to account for this effect. Block Storage does not currently have a method for replicating data across multiple regions, so applications that depend on available block storage need to manually cope with this limitation by creating duplicate block storage entries in each region."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/multi_site/section_tech_considerations_multi_site.xml:139(title) ./doc/arch-design/network_focus/section_user_requirements_network_focus.xml:163(title) ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:630(term) ./doc/arch-design/generalpurpose/section_user_requirements_general_purpose.xml:191(term) ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:778(title) ./doc/arch-design/compute_focus/section_user_requirements_compute_focus.xml:160(term) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:435(term) ./doc/arch-design/compute_focus/section_tech_considerations_compute_focus.xml:268(title) ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:107(title) ./doc/arch-design/storage_focus/section_tech_considerations_storage_focus.xml:47(term) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:448(term) ./doc/arch-design/storage_focus/section_user_requirements_storage_focus.xml:136(term)
|
||||
@ -1182,7 +1186,7 @@ msgid "Security"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/multi_site/section_tech_considerations_multi_site.xml:140(para)
|
||||
msgid "Securing a multi-site OpenStack installation also brings extra challenges. Tenants may expect a tenant-created network to be secure. In a multi-site installation the use of a non-private connection between sites may be required. This may mean that traffic would be visible to third parties and, in cases where an application requires security, this issue will require mitigation. Installing a VPN or encrypted connection between sites is recommended in such instances."
|
||||
msgid "Securing a multi-site OpenStack installation also brings extra challenges. Tenants may expect a tenant-created network to be secure. In a multi-site installation the use of a non-private connection between sites may be required. This may mean that traffic would be visible to third parties and, in cases where an application requires security, this issue requires mitigation. Installing a VPN or encrypted connection between sites is recommended in such instances."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/multi_site/section_tech_considerations_multi_site.xml:148(para)
|
||||
|
||||
@ -8,8 +8,8 @@
|
||||
msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: OpenStack Manuals\n"
|
||||
"POT-Creation-Date: 2015-03-20 03:44+0000\n"
|
||||
"PO-Revision-Date: 2015-03-20 03:12+0000\n"
|
||||
"POT-Creation-Date: 2015-03-26 05:47+0000\n"
|
||||
"PO-Revision-Date: 2015-03-25 10:27+0000\n"
|
||||
"Last-Translator: openstackjenkins <jenkins@openstack.org>\n"
|
||||
"Language-Team: Chinese (China) (http://www.transifex.com/projects/p/openstack-manuals-i18n/language/zh_CN/)\n"
|
||||
"MIME-Version: 1.0\n"
|
||||
@ -934,12 +934,12 @@ msgstr "部署者务必意识到这点，为他们的站点提供合适的定制
|
||||
|
||||
#: ./doc/arch-design/multi_site/section_operational_considerations_multi_site.xml19(para)
|
||||
msgid ""
|
||||
"Note that, as of the Icehouse release, documentation for implementing this "
|
||||
"feature is in progress. See this bug for more information: <link "
|
||||
"As of the Icehouse release, documentation for implementing this feature is "
|
||||
"in progress. See this bug for more information: <link "
|
||||
"href=\"https://bugs.launchpad.net/openstack-"
|
||||
"manuals/+bug/1340509\">https://bugs.launchpad.net/openstack-"
|
||||
"manuals/+bug/1340509</link>."
|
||||
msgstr "注意，自从Icehouse版本发布后，实现此特性的文档一直都在写作中，详情请浏览： <link href=\"https://bugs.launchpad.net/openstack-manuals/+bug/1340509\">https://bugs.launchpad.net/openstack-manuals/+bug/1340509</link>。"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/multi_site/section_operational_considerations_multi_site.xml26(title)
|
||||
msgid "Licensing"
|
||||
@ -1150,18 +1150,18 @@ msgid ""
|
||||
"resources in the environment. It is important that user documentation is "
|
||||
"accessible by users of the cloud infrastructure to ensure they are given "
|
||||
"sufficient information to help them leverage the cloud. As an example, by "
|
||||
"default OpenStack will schedule instances on a compute node automatically. "
|
||||
"default OpenStack schedules instances on a compute node automatically. "
|
||||
"However, when multiple regions are available, it is left to the end user to "
|
||||
"decide in which region to schedule the new instance. The dashboard will "
|
||||
"present the user with the first region in your configuration. The API and "
|
||||
"CLI tools will not execute commands unless a valid region is specified. It "
|
||||
"is therefore important to provide documentation to your users describing the"
|
||||
" region layout as well as calling out that quotas are region-specific. If a "
|
||||
"user reaches his or her quota in one region, OpenStack will not "
|
||||
"automatically build new instances in another. Documenting specific examples "
|
||||
"will help users understand how to operate the cloud, thereby reducing calls "
|
||||
"and tickets filed with the help desk."
|
||||
msgstr "用户必须自行去操作云基础设施以及在环境中部署新的资源。用户查阅用户文档来操作云，这样的话能够给出准确的文档就很重要。举例来说，默认情况下OpenStack自动的调度实例到某个计算节点，但是，当多个region均可用时，就得用户自行决定在哪个region中调度新的实例。GUI界面显示的是用户配置的第一个region，而API和CLI工具若不指定合法的region就不会执行。因此提供文档很重要，文档中要描述region的层次以及特定region的配额等，如果用户在一个region中达到了配额的上限，OpenStack是不会自动到另外的region中构建新的实例的。文档中描述特别的例子将会帮助用户理解如何操作云，因此而减少电话呼救和现场维修。"
|
||||
"decide in which region to schedule the new instance. The dashboard presents "
|
||||
"the user with the first region in your configuration. The API and CLI tools "
|
||||
"do not execute commands unless a valid region is specified. It is therefore "
|
||||
"important to provide documentation to your users describing the region "
|
||||
"layout as well as calling out that quotas are region-specific. If a user "
|
||||
"reaches his or her quota in one region, OpenStack does not automatically "
|
||||
"build new instances in another. Documenting specific examples helps users "
|
||||
"understand how to operate the cloud, thereby reducing calls and tickets "
|
||||
"filed with the help desk."
|
||||
msgstr ""
|
||||
|
||||
#. When image changes, this message will be marked fuzzy or untranslated for
|
||||
#. you.
|
||||
@ -1183,16 +1183,16 @@ msgstr "架构"
|
||||
|
||||
#: ./doc/arch-design/multi_site/section_architecture_multi_site.xml9(para)
|
||||
msgid ""
|
||||
"This graphic is a high level diagram of a multiple site OpenStack "
|
||||
"architecture. Each site is an OpenStack cloud but it may be necessary to "
|
||||
"architect the sites on different versions. For example, if the second site "
|
||||
"is intended to be a replacement for the first site, they would be different."
|
||||
" Another common design would be a private OpenStack cloud with replicated "
|
||||
"site that would be used for high availability or disaster recovery. The most"
|
||||
" important design decision is how to configure the storage. It can be "
|
||||
"configured as a single shared pool or separate pools, depending on the user "
|
||||
"and technical requirements."
|
||||
msgstr "此图一个多区域OpenStack架构的高度抽象示意图。每个站点都是一个OpenStack云，但是根据架构的需要可能是不同的版本。例如，如果第二个站点的使命就是替代第一个站点，他们就可以不同。另为通用的设计是一个私有的OpenStack云是完全复制的站点将用来做高可用或灾难恢复。最重要的设计决定是如何配置存储，既可以配置为单个共享池也可以是分离的池，这取决于用户和技术的需求。"
|
||||
"This graphic is a high level diagram of a multi-site OpenStack architecture."
|
||||
" Each site is an OpenStack cloud but it may be necessary to architect the "
|
||||
"sites on different versions. For example, if the second site is intended to "
|
||||
"be a replacement for the first site, they would be different. Another common"
|
||||
" design would be a private OpenStack cloud with replicated site that would "
|
||||
"be used for high availability or disaster recovery. The most important "
|
||||
"design decision is how to configure the storage. It can be configured as a "
|
||||
"single shared pool or separate pools, depending on the user and technical "
|
||||
"requirements."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/multi_site/section_architecture_multi_site.xml25(title)
|
||||
msgid "OpenStack services architecture"
|
||||
@ -1316,21 +1316,21 @@ msgid ""
|
||||
"The architecture for a multi-site installation of OpenStack is dependent on "
|
||||
"a number of factors. One major dependency to consider is storage. When "
|
||||
"designing the storage system, the storage mechanism needs to be determined. "
|
||||
"Once the storage type is determined, how it will be accessed is critical. "
|
||||
"For example, we recommend that storage should use a dedicated network. "
|
||||
"Another concern is how the storage is configured to protect the data. For "
|
||||
"example, the recovery point objective (RPO) and the recovery time objective "
|
||||
"(RTO). How quickly can the recovery from a fault be completed, will "
|
||||
"determine how often the replication of data be required. Ensure that enough "
|
||||
"storage is allocated to support the data protection strategy."
|
||||
msgstr "对于一个多区域OpenStack安装架构来说，依赖于很多的因素，其中一个主要的依赖需要考虑的就是存储。当设计存储系统时，存储的机制需要决定。一旦存储的类型决定了，如何访问就成了重点。例如，我们建议存储使用专用网络。另外一个需要考虑的是如果配置存储来保护数据。例如恢复点目标(RPO)和恢复时间目标(RTO),如何快速的从完全失效中恢复，将决定复制数据如何频繁的需求。确保有足够的存储来分配，以支持数据保护策略。"
|
||||
"Once the storage type is determined, how it is accessed is critical. For "
|
||||
"example, we recommend that storage should use a dedicated network. Another "
|
||||
"concern is how the storage is configured to protect the data. For example, "
|
||||
"the recovery point objective (RPO) and the recovery time objective (RTO). "
|
||||
"How quickly can the recovery from a fault be completed, determines how often"
|
||||
" the replication of data is required. Ensure that enough storage is "
|
||||
"allocated to support the data protection strategy."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/multi_site/section_architecture_multi_site.xml115(para)
|
||||
msgid ""
|
||||
"Networking decisions include the encapsulation mechanism that will be used "
|
||||
"Networking decisions include the encapsulation mechanism that can be used "
|
||||
"for the tenant networks, how large the broadcast domains should be, and the "
|
||||
"contracted SLAs for the interconnects."
|
||||
msgstr "网络决定包括用于租户网络的封装机制，广播域有多大，以及内部联通的服务水平协议。"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/multi_site/section_user_requirements_multi_site.xml8(title)
|
||||
#: ./doc/arch-design/network_focus/section_user_requirements_network_focus.xml8(title)
|
||||
@ -1460,17 +1460,17 @@ msgid ""
|
||||
"different sites. This needs to be built into the infrastructure. If the "
|
||||
"OpenStack Object Storage is used as a back end for the Image Service, it is "
|
||||
"possible to create repositories of consistent images across multiple sites. "
|
||||
"Having central endpoints with multiple storage nodes will allow for "
|
||||
"consistent centralized storage for each and every site."
|
||||
msgstr "在跨不同的站点有必要保持部署实例的一致性，这需要构建基础设施，如果为镜像服务提供的后端存储是OpenStack对象存储的话，这很轻松的就可跨多个站点建立一致性镜像的仓库。具有中央端点与多个存储节点将允许为每一个站点有一致的集中存储。"
|
||||
"Having central endpoints with multiple storage nodes allows consistent "
|
||||
"centralized storage for each and every site."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/multi_site/section_user_requirements_multi_site.xml81(para)
|
||||
msgid ""
|
||||
"Not using a centralized object store will increase operational overhead so "
|
||||
"that a consistent image library can be maintained. This could include "
|
||||
"development of a replication mechanism to handle the transport of images and"
|
||||
" the changes to the images across multiple sites."
|
||||
msgstr "不使用中心化的对象存储将会带来运维方面的问题，例如一致性的镜像库就需要维护，包括开发复制机制以掌控传输镜像和跨多站点的镜像变化。"
|
||||
"Not using a centralized object store increases operational overhead so that "
|
||||
"a consistent image library can be maintained. This could include development"
|
||||
" of a replication mechanism to handle the transport of images and the "
|
||||
"changes to the images across multiple sites."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/multi_site/section_user_requirements_multi_site.xml87(para)
|
||||
msgid ""
|
||||
@ -1508,9 +1508,9 @@ msgstr "多网络链路应该在站点之间部署，以提供所有组件的冗
|
||||
#: ./doc/arch-design/multi_site/section_user_requirements_multi_site.xml108(para)
|
||||
msgid ""
|
||||
"The ability to maintain object availability in both sites has significant "
|
||||
"implications on the object storage design and implementation. It will also "
|
||||
"have a significant impact on the WAN network design between the sites."
|
||||
msgstr "维护对象可用性的能力会显著影响到对象存储的设计和实现，也会影响到站点之间的广域网网络设计。"
|
||||
"implications on the object storage design and implementation. It also has a "
|
||||
"significant impact on the WAN network design between the sites."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/multi_site/section_user_requirements_multi_site.xml112(para)
|
||||
msgid ""
|
||||
@ -1618,11 +1618,11 @@ msgstr "已经部署的应用需要持续的服务，且更加重要的，需要
|
||||
|
||||
#: ./doc/arch-design/multi_site/section_user_requirements_multi_site.xml178(para)
|
||||
msgid ""
|
||||
"It is important to understand what will happen to the replication of objects"
|
||||
" and data between the sites when a site goes down. If this causes queues to "
|
||||
"It is important to understand what happens to the replication of objects and"
|
||||
" data between the sites when a site goes down. If this causes queues to "
|
||||
"start building up, consider how long these queues can safely exist until "
|
||||
"something explodes."
|
||||
msgstr "当一个站点失效时，理解在站点之间的对象和数据复制会发生什么很重要。如果这导致队列开始建立，要考虑到多长时间这些队列到什么事情爆炸发生之前可安全完成。"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/multi_site/section_user_requirements_multi_site.xml185(para)
|
||||
msgid ""
|
||||
@ -1674,16 +1674,16 @@ msgstr "站点之间的认证"
|
||||
#: ./doc/arch-design/multi_site/section_user_requirements_multi_site.xml213(para)
|
||||
msgid ""
|
||||
"Ideally it is best to have a single authentication domain and not need a "
|
||||
"separate implementation for each and every site. This will, of course, "
|
||||
"require an authentication mechanism that is highly available and distributed"
|
||||
" to ensure continuous operation. Authentication server locality is also "
|
||||
"separate implementation for each and every site. This, of course, requires "
|
||||
"an authentication mechanism that is highly available and distributed to "
|
||||
"ensure continuous operation. Authentication server locality is also "
|
||||
"something that might be needed as well and should be planned for."
|
||||
msgstr "理想中最好是有一个单一的认证域而不是在每个站点中分离的去实现。这当然会要求认证机制是高可用和分布式的确定持续可操作。局部认证服务也需要好好的规划。"
|
||||
msgstr ""
|
||||
|
||||
#. 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.
|
||||
#: ./doc/arch-design/multi_site/section_prescriptive_examples_multi_site.xml86(None)
|
||||
#: ./doc/arch-design/multi_site/section_prescriptive_examples_multi_site.xml85(None)
|
||||
msgid ""
|
||||
"@@image: '../figures/Multi-Site_Customer_Edge.png'; "
|
||||
"md5=01850cf774e7075bd7202c6e7f087f36"
|
||||
@ -1692,7 +1692,7 @@ msgstr "@@image: '../figures/Multi-Site_Customer_Edge.png'; md5=01850cf774e7075b
|
||||
#. 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.
|
||||
#: ./doc/arch-design/multi_site/section_prescriptive_examples_multi_site.xml190(None)
|
||||
#: ./doc/arch-design/multi_site/section_prescriptive_examples_multi_site.xml191(None)
|
||||
msgid ""
|
||||
"@@image: '../figures/Multi-site_Geo_Redundant_LB.png'; "
|
||||
"md5=c94a96f6084c2e50a0eb6846f6fde479"
|
||||
@ -1717,13 +1717,13 @@ msgstr "示例"
|
||||
|
||||
#: ./doc/arch-design/multi_site/section_prescriptive_examples_multi_site.xml13(para)
|
||||
msgid ""
|
||||
"Based on the needs of the intended workloads, there are multiple ways to "
|
||||
"build a multi-site OpenStack installation. Below are example architectures "
|
||||
"There are multiple ways to build a multi-site OpenStack installation, based "
|
||||
"on the needs of the intended workloads. Below are example architectures "
|
||||
"based on different requirements. These examples are meant as a reference, "
|
||||
"and not a hard and fast rule for deployments. Use the previous sections of "
|
||||
"this chapter to assist in selecting specific components and implementations "
|
||||
"based on specific needs."
|
||||
msgstr "基于所需要专注的负载，构建多区域OpenStack安装有好几种办法。下面的架构例子基于不同的需求，这些例子仅仅用作参考，对于部署不是硬性和快速的规则。使用前面本章前几节来帮助基于特殊的需求选择特定的组件和实现。"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/multi_site/section_prescriptive_examples_multi_site.xml20(para)
|
||||
msgid ""
|
||||
@ -1738,72 +1738,71 @@ msgid ""
|
||||
"horizontal scaling than a traditional compute workload scale. The intent is "
|
||||
"to scale by creating more copies of the application in closer proximity to "
|
||||
"the users that need it most, in order to ensure faster response time to user"
|
||||
" requests. This provider will deploy two datacenters at each of the four "
|
||||
"chosen regions. The implications of this design are based around the method "
|
||||
"of placing copies of resources in each of the remote regions. Swift objects,"
|
||||
" Glance images, and block storage will need to be manually replicated into "
|
||||
"each region. This may be beneficial for some systems, such as the case of "
|
||||
"content service, where only some of the content needs to exist in some but "
|
||||
"not all regions. A centralized Keystone is recommended to ensure "
|
||||
"authentication and that access to the API endpoints is easily manageable."
|
||||
msgstr "一个大型的内容提供商需要为分散在不同地理位置的客户交付内容，此负载对延迟极为敏感，而且还得快速响应最终用户。经过用户的回顾，技术和运营的考虑，最后决定构建有利于本地客户边缘的几个region，在此用例中，没有选择构建几个大型的、中心化的数据中心，而是架构的意图很明确，在接近最终用户的地方提供几个小型的数据中心，在此用例中，取代传统计算负载扩展的方式，而使用不同的横向扩展快速扩充应用，为了确保用户需求的快速响应时间，为贴近用户最迫切的需求，专注于通过创建更多应用的复制的扩展。此供应商会在每4个所选择的region部署两个数据中心，此设计的实现是围绕这每个远端的region复制资源的方法。Swift对象存储服务，Glance镜像服务，以及块存储在每个region都需要手动的复制，这也许有利于一些系统，比如内容服务的用例，他们的一些内容仅出现在部分而不是全部的region。建议建立一个中心化的Keystone，确保认证服务和API端点访问可轻松管理。"
|
||||
" requests. This provider deploys two datacenters at each of the four chosen "
|
||||
"regions. The implications of this design are based around the method of "
|
||||
"placing copies of resources in each of the remote regions. Swift objects, "
|
||||
"Glance images, and block storage need to be manually replicated into each "
|
||||
"region. This may be beneficial for some systems, such as the case of content"
|
||||
" service, where only some of the content needs to exist in some but not all "
|
||||
"regions. A centralized Keystone is recommended to ensure authentication and "
|
||||
"that access to the API endpoints is easily manageable."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/multi_site/section_prescriptive_examples_multi_site.xml44(para)
|
||||
msgid ""
|
||||
"Installation of an automated DNS system such as Designate is highly "
|
||||
"recommended. Unless an external Dynamic DNS system is available, application"
|
||||
" administrators will need a way to manage the mapping of which application "
|
||||
"copy exists in each region and how to reach it. Designate will assist by "
|
||||
"making the process automatic and by populating the records in the each "
|
||||
"region's zone."
|
||||
msgstr "强烈建议安装一个自动的DNS系统，比如Designate。除非有外部的动态DNS系统可用，应用管理员会需要一个管理办法，在每个region中映射那个应用复制出现以及如何访问它们。Desginate将会将这些流程自动化，而且会填充记录到每个region的区。"
|
||||
"It is recommended that you install an automated DNS system such as "
|
||||
"Designate. Application administrators need a way to manage the mapping of "
|
||||
"which application copy exists in each region and how to reach it, unless an "
|
||||
"external Dynamic DNS system is available. Designate assists by making the "
|
||||
"process automatic and by populating the records in the each region's zone."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/multi_site/section_prescriptive_examples_multi_site.xml51(para)
|
||||
#: ./doc/arch-design/multi_site/section_prescriptive_examples_multi_site.xml50(para)
|
||||
msgid ""
|
||||
"Telemetry for each region is also deployed, as each region may grow "
|
||||
"differently or be used at a different rate. Ceilometer will run to collect "
|
||||
"each region's metrics from each of the controllers and report them back to a"
|
||||
"differently or be used at a different rate. Ceilometer collects each "
|
||||
"region's metrics from each of the controllers and report them back to a "
|
||||
"central location. This is useful both to the end user and the administrator "
|
||||
" of the OpenStack environment. The end user will find this method useful, in"
|
||||
" that it is possible to determine if certain locations are experiencing "
|
||||
"higher load than others, and take appropriate action. Administrators will "
|
||||
"also benefit by possibly being able to forecast growth per region, rather "
|
||||
"than expanding the capacity of all regions simultaneously, therefore "
|
||||
"maximizing the cost-effectiveness of the multi-site design."
|
||||
msgstr "Telemetry也会部署到每个region中，虽然每个region的增长可能不一样或者使用的频率也不同。Ceilometer将运行在每个region中的监测数据，然后回报到中心地点。这在OpenStack环境中对于最终用户也好，对于系统管理员也好，都有很大的用处，使最终用户根据某些局部的负载高于其他地方做出决定而成为可能，然后采取相应的措施。使系统管理员在每个region预测增长成为可能，而不是去盲目的同等看待所有region而去扩展它们，因此对于多区域设计是最大化的节省资源。"
|
||||
"of the OpenStack environment. The end user will find this method useful, as "
|
||||
"it makes possible to determine if certain locations are experiencing higher "
|
||||
"load than others, and take appropriate action. Administrators also benefit "
|
||||
"by possibly being able to forecast growth per region, rather than expanding "
|
||||
"the capacity of all regions simultaneously, therefore maximizing the cost-"
|
||||
"effectiveness of the multi-site design."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/multi_site/section_prescriptive_examples_multi_site.xml64(para)
|
||||
#: ./doc/arch-design/multi_site/section_prescriptive_examples_multi_site.xml63(para)
|
||||
msgid ""
|
||||
"One of the key decisions of running this sort of infrastructure is whether "
|
||||
"or not to provide a redundancy model. Two types of redundancy and high "
|
||||
"availability models in this configuration will be implemented. The first "
|
||||
"type revolves around the availability of the central OpenStack components. "
|
||||
"Keystone will be made highly available in three central data centers that "
|
||||
"will host the centralized OpenStack components. This prevents a loss of any "
|
||||
"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"
|
||||
" for distributing content to each of the regions."
|
||||
msgstr "运行此类基础设施的一个关键决定是是否提供冗余模式。在此配置中有两类冗余和高可用模式需要被实现。第一类围绕中心化OpenStack组件的可用性，Keystone会基于三个中心化的数据中心而形成高可用，而成为中心化的OpenStack组件。这会防止任何的region失效而导致服务不可用。这也会为在每个region运行着中央存储仓库作为主要缓存，用于分发内容，带来额外的好处。"
|
||||
"availability models in this configuration can be implemented. The first type"
|
||||
" revolves around the availability of the central OpenStack components. "
|
||||
"Keystone can be made highly available in three central data centers that "
|
||||
"host the centralized OpenStack components. This prevents a loss of any 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 for "
|
||||
"distributing content to each of the regions."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/multi_site/section_prescriptive_examples_multi_site.xml75(para)
|
||||
#: ./doc/arch-design/multi_site/section_prescriptive_examples_multi_site.xml74(para)
|
||||
msgid ""
|
||||
"The second redundancy topic is that of the edge data center itself. 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 "
|
||||
"degraded performance in terms of latency and availability."
|
||||
msgstr "第二类容易是边缘数据中心本身。在每个边缘region地带的第二个数据中心会在靠近第一个region边上承载起第二个region的功用。这确保应用不会遭受延迟和可用性方面的性能下降。"
|
||||
" data center in each of the edge regional locations house a second region "
|
||||
"near the first. This ensures that the application does not suffer degraded "
|
||||
"performance in terms of latency and availability."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/multi_site/section_prescriptive_examples_multi_site.xml80(para)
|
||||
#: ./doc/arch-design/multi_site/section_prescriptive_examples_multi_site.xml79(para)
|
||||
msgid ""
|
||||
"This figure depicts the solution designed to have both a centralized set of "
|
||||
"core data centers for OpenStack services and paired edge data centers:"
|
||||
msgstr "此示意图描述所设计的解决方案，同时拥有一个为OpenStack服务的中心化的核心数据中心和两个边缘化的数据中心："
|
||||
|
||||
#: ./doc/arch-design/multi_site/section_prescriptive_examples_multi_site.xml90(title)
|
||||
#: ./doc/arch-design/multi_site/section_prescriptive_examples_multi_site.xml89(title)
|
||||
msgid "Geo-redundant load balancing"
|
||||
msgstr "地理冗余负载均衡"
|
||||
|
||||
#: ./doc/arch-design/multi_site/section_prescriptive_examples_multi_site.xml91(para)
|
||||
#: ./doc/arch-design/multi_site/section_prescriptive_examples_multi_site.xml90(para)
|
||||
msgid ""
|
||||
"A large-scale web application has been designed with cloud principles in "
|
||||
"mind. The application is designed provide service to application store, on a"
|
||||
@ -1812,7 +1811,7 @@ msgid ""
|
||||
"the information."
|
||||
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.xml96(para)
|
||||
msgid ""
|
||||
"As of late there has been several outages in number of major public cloud "
|
||||
"providersusually due to the fact these applications were running out of a "
|
||||
@ -1820,90 +1819,94 @@ msgid ""
|
||||
"chance of a single site causing an outage for their business."
|
||||
msgstr "最后，经常由于一些因素他们的应用运行在单个地理位置,主要的公有云提供者因此会停止一些服务。因此设计中要考虑如何降低由于单个站点引起的中断业务的几率。"
|
||||
|
||||
#: ./doc/arch-design/multi_site/section_prescriptive_examples_multi_site.xml102(para)
|
||||
#: ./doc/arch-design/multi_site/section_prescriptive_examples_multi_site.xml101(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_prescriptive_example_general_purpose.xml30(para)
|
||||
msgid "The solution would consist of the following OpenStack components:"
|
||||
msgstr "解决方案将由下列OpenStack组件组成："
|
||||
|
||||
#: ./doc/arch-design/multi_site/section_prescriptive_examples_multi_site.xml106(para)
|
||||
#: ./doc/arch-design/multi_site/section_prescriptive_examples_multi_site.xml105(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_prescriptive_example_general_purpose.xml34(para)
|
||||
msgid ""
|
||||
"A firewall, switches and load balancers on the public facing network "
|
||||
"connections."
|
||||
msgstr "防火墙、交换机、以及负载均衡设备在公网中直接面向全网的连接。"
|
||||
|
||||
#: ./doc/arch-design/multi_site/section_prescriptive_examples_multi_site.xml110(para)
|
||||
#: ./doc/arch-design/multi_site/section_prescriptive_examples_multi_site.xml109(para)
|
||||
msgid ""
|
||||
"OpenStack Controller services running, Networking, dashboard, Block Storage "
|
||||
"and Compute running locally in each of the three regions. The other "
|
||||
"services, Identity, Orchestration, Telemetry, Image Service and Object "
|
||||
"Storage will be installed centrallywith nodes in each of the region "
|
||||
"providing a redundant OpenStack Controller plane throughout the globe."
|
||||
msgstr "运行着OpenStack控制器服务的：网络服务、GUI界面、块存储以及计算服务，都运行在每三个region的本地。其他的服务：认证、Orchestration、Telemetry、镜像服务以及对象存储会安装到每个region的中心节点，通过全局来提供冗余的OpenStack控制器。"
|
||||
"Storage can be installed centrallywith 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.xml120(para)
|
||||
#: ./doc/arch-design/multi_site/section_prescriptive_examples_multi_site.xml119(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_prescriptive_example_general_purpose.xml44(para)
|
||||
msgid "OpenStack Compute nodes running the KVM hypervisor."
|
||||
msgstr "OpenStack计算节点运行着KVM的hypervisor。"
|
||||
|
||||
#: ./doc/arch-design/multi_site/section_prescriptive_examples_multi_site.xml124(para)
|
||||
#: ./doc/arch-design/multi_site/section_prescriptive_examples_multi_site.xml123(para)
|
||||
msgid ""
|
||||
"OpenStack Object Storage for serving static objects such as images will be "
|
||||
"OpenStack Object Storage for serving static objects such as images can be "
|
||||
"used to ensure that all images are standardized across all the regions, and "
|
||||
"replicated on a regular basis."
|
||||
msgstr "OpenStack对象存储为静态内容提供服务，例如图片，确保所有的图片都通过标准化的存于所有的region，且使用定期复制。"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/multi_site/section_prescriptive_examples_multi_site.xml130(para)
|
||||
#: ./doc/arch-design/multi_site/section_prescriptive_examples_multi_site.xml129(para)
|
||||
msgid ""
|
||||
"A Distributed DNS service available to all regionsthat allows for dynamic "
|
||||
"update of DNS records of deployed instances."
|
||||
msgstr "在所有的region中都有一个分布式DNS服务可用，允许动态的为已经部署的实例更新DNS记录。"
|
||||
|
||||
#: ./doc/arch-design/multi_site/section_prescriptive_examples_multi_site.xml135(para)
|
||||
#: ./doc/arch-design/multi_site/section_prescriptive_examples_multi_site.xml134(para)
|
||||
msgid ""
|
||||
"A geo-redundant load balancing service will be used to service the requests "
|
||||
"A geo-redundant load balancing service can be used to service the requests "
|
||||
"from the customers based on their origin."
|
||||
msgstr "基于地理位置的负载均衡服务用于顾客过去使用的需求。"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/multi_site/section_prescriptive_examples_multi_site.xml140(para)
|
||||
#: ./doc/arch-design/multi_site/section_prescriptive_examples_multi_site.xml139(para)
|
||||
msgid ""
|
||||
"An autoscaling heat template will used to deploy the application in the "
|
||||
"three regions. This template will include:"
|
||||
msgstr "在三个region中都使用自动伸缩heat模板来部署应用。此模板包括："
|
||||
"An autoscaling heat template can be used to deploy the application in the "
|
||||
"three regions. This template includes:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/multi_site/section_prescriptive_examples_multi_site.xml145(para)
|
||||
#: ./doc/arch-design/multi_site/section_prescriptive_examples_multi_site.xml143(para)
|
||||
msgid "Web Servers, running Apache."
|
||||
msgstr "Web服务，运行 Apache。"
|
||||
|
||||
#: ./doc/arch-design/multi_site/section_prescriptive_examples_multi_site.xml148(para)
|
||||
#: ./doc/arch-design/multi_site/section_prescriptive_examples_multi_site.xml146(para)
|
||||
msgid ""
|
||||
"Appropriate <literal>user_data</literal> to populate the central DNS servers"
|
||||
" upon instance launch."
|
||||
msgstr "当实例启动时，中心DNS服务器会填写合适的<literal>user_data</literal>。"
|
||||
|
||||
#: ./doc/arch-design/multi_site/section_prescriptive_examples_multi_site.xml152(para)
|
||||
#: ./doc/arch-design/multi_site/section_prescriptive_examples_multi_site.xml150(para)
|
||||
msgid ""
|
||||
"Appropriate Telemetry alarms that maintain state of the application and "
|
||||
"allow for handling of region or instance failure."
|
||||
msgstr "正确的Telemetry警告，维护着应用的状态且允许掌控region或实例失效。"
|
||||
|
||||
#: ./doc/arch-design/multi_site/section_prescriptive_examples_multi_site.xml157(para)
|
||||
#: ./doc/arch-design/multi_site/section_prescriptive_examples_multi_site.xml155(para)
|
||||
msgid ""
|
||||
"Another autoscaling Heat template will be used to deploy a distributed "
|
||||
"Another autoscaling Heat template can be used to deploy a distributed "
|
||||
"MongoDB shard over the three locationswith the option of storing required "
|
||||
"data on a globally available swift container. according to the usage and "
|
||||
"load on the database serveradditional shards will be provisioned according "
|
||||
"to the thresholds defined in Telemetry."
|
||||
msgstr "另外一个自动伸缩的Heat模板会用于部署分布式MongoDB shard，在全部的三个地点存储全局可用的swift容器数据。基于数据库服务所使用的和负载，以及Telemetry定义的阀值，来决定是否增加额外的shard。"
|
||||
"data on a globally available swift container. According to the usage and "
|
||||
"load on the database serveradditional shards can be provisioned according to"
|
||||
" the thresholds defined in Telemetry."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/multi_site/section_prescriptive_examples_multi_site.xml163(para)
|
||||
#. <para>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 center would have been sufficient
|
||||
#. had the requirements been met.</para>
|
||||
#: ./doc/arch-design/multi_site/section_prescriptive_examples_multi_site.xml165(para)
|
||||
msgid ""
|
||||
"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 "
|
||||
"center would have been sufficient had the requirements been met."
|
||||
msgstr "这里选择三个region的原因是由于担心偶然的异常负载在单个region会引发失效。两个数据中心足够可以满足需求。"
|
||||
"Two data centers would have been sufficient had the requirements been met. "
|
||||
"But three regions are selected here to avoid abnormal load on a single "
|
||||
"region in the event of a failure."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/multi_site/section_prescriptive_examples_multi_site.xml167(para)
|
||||
#: ./doc/arch-design/multi_site/section_prescriptive_examples_multi_site.xml168(para)
|
||||
msgid ""
|
||||
"Orchestration is used because of the built-in functionality of autoscaling "
|
||||
"and auto healing in the event of increased load. Additional configuration "
|
||||
@ -1914,37 +1917,37 @@ msgid ""
|
||||
"scenario was relatively straight forwardthe external tools were not needed."
|
||||
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.xml177(para)
|
||||
msgid ""
|
||||
"OpenStack Object Storage is used here to serve as a back end for the Image "
|
||||
"Service since was the most suitable solution for a globally distributed "
|
||||
"Service since it is the most suitable solution for a globally distributed "
|
||||
"storage solutionwith its own replication mechanism. Home grown solutions "
|
||||
"could also have been used including the handling of replicationbut were not "
|
||||
"chosen, because Object Storage is already an intricate part of the "
|
||||
"infrastructureand proven solution."
|
||||
msgstr "OpenStack对象存储在这里的使用，是为镜像服务提供后端支撑，而镜像存储最合适的解决方案就是全局的分布式存储解决方案，而对象存储恰恰满足其自身的复制机制。本土的解决方案也已经被使用，包括复制的处理，但都没有选择，因为对象存储已经是基础设施和成熟的解决方案的复杂部分。"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/multi_site/section_prescriptive_examples_multi_site.xml184(para)
|
||||
#: ./doc/arch-design/multi_site/section_prescriptive_examples_multi_site.xml185(para)
|
||||
msgid ""
|
||||
"An external load balancing service was used and not the LBaaS in OpenStack "
|
||||
"because the solution in OpenStack is not redundant and does not have any "
|
||||
"awareness of geo location."
|
||||
msgstr "一个额外的负载均衡服务将被使用，而不是OpenStack的LBaaS,因为OpenStack的LBaaS在OpenStack中不是冗余的解决方案而且不具有地理位置的任何特征。"
|
||||
|
||||
#: ./doc/arch-design/multi_site/section_prescriptive_examples_multi_site.xml193(title)
|
||||
#: ./doc/arch-design/multi_site/section_prescriptive_examples_multi_site.xml194(title)
|
||||
msgid "Location-local service"
|
||||
msgstr "本地服务"
|
||||
|
||||
#: ./doc/arch-design/multi_site/section_prescriptive_examples_multi_site.xml194(para)
|
||||
#: ./doc/arch-design/multi_site/section_prescriptive_examples_multi_site.xml195(para)
|
||||
msgid ""
|
||||
"A common use for a multi-site deployment of OpenStack, is for creating a "
|
||||
"Content Delivery Network. An application that uses a location-local "
|
||||
"architecture will require low network latency and proximity to the user, in "
|
||||
"architecture requires low network latency and proximity to the user, in "
|
||||
"order to provide an optimal user experience, in addition to reducing the "
|
||||
"cost of bandwidth and transit, since the content resides on sites closer to "
|
||||
"the customer, instead of a centralized content store that would require "
|
||||
"utilizing higher cost cross country links."
|
||||
msgstr "多区域OpenStack部署常见的一个场景是创建内容分发网络CDN，一个应用使用本地架构会有低网络延迟和接近用户的需求，为了提供给用户极致的体验，为了减少带宽和传送的费用，因此将内容输送到更加接近客户，而替代中心化的内容存储这种需要跨国连接的高额费用。"
|
||||
"the customer, instead of a centralized content store that requires utilizing"
|
||||
" higher cost cross-country links."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/multi_site/section_prescriptive_examples_multi_site.xml203(para)
|
||||
msgid ""
|
||||
@ -1961,11 +1964,11 @@ msgstr "此架构通常包括一个放置在最接近节点的用户需求的地
|
||||
msgid ""
|
||||
"In this example, the application utilizing this multi-site OpenStack install"
|
||||
" that is location aware would launch web server or content serving instances"
|
||||
" on the compute cluster in each site. Requests from clients will first be "
|
||||
"sent to a global services load balancer that determines the location of the "
|
||||
" on the compute cluster in each site. Requests from clients are first 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 "
|
||||
"application completes the request."
|
||||
msgstr "在此例中，应用利用此多区域OpenStack基于位置敏感的安装，在每个站点的计算集群中启动web服务和内容服务的实例，来自客户的请求会第一时间发送到全局服务负载均衡器，然后负载均衡器会决定客户的位置，当应用完成请求，路由会将请求发给最近的OpenStack站点。"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/multi_site/section_tech_considerations_multi_site.xml8(title)
|
||||
#: ./doc/arch-design/network_focus/section_tech_considerations_network_focus.xml8(title)
|
||||
@ -1983,9 +1986,9 @@ msgid ""
|
||||
"There are many technical considerations to take into account with regard to "
|
||||
"designing a multi-site OpenStack implementation. An OpenStack cloud can be "
|
||||
"designed in a variety of ways to handle individual application needs. A "
|
||||
"multi-site deployment will have additional challenges compared to single "
|
||||
"site installations and will therefore be a more complex solution."
|
||||
msgstr "设计一个多区域OpenStack有许多的技术因素需要被纳入有关的账单。一个OpenStack云有很多中办法来设计，去掌控分离的应用需求，一个多区域的部署相比于单一站点的安装会带来额外的挑战，也因此将会是一个更加复杂的解决方案。"
|
||||
"multi-site deployment has additional challenges compared to single site "
|
||||
"installations and therefore is a more complex solution."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/multi_site/section_tech_considerations_multi_site.xml16(para)
|
||||
msgid ""
|
||||
@ -2000,11 +2003,11 @@ msgid ""
|
||||
"between the different OpenStack sites. This includes parameters such as "
|
||||
"bandwidth, latency, whether or not a link is dedicated, and any business "
|
||||
"policies applied to the connection. The capability and number of the links "
|
||||
"between sites will determine what kind of options may be available for "
|
||||
"deployment. For example, if two sites have a pair of high-bandwidth links "
|
||||
"available between them, it may be wise to configure a separate storage "
|
||||
"replication network between the two sites to support a single Swift endpoint"
|
||||
" and a shared object storage capability between them. (An example of this "
|
||||
"between sites determine what kind of options are available for deployment. "
|
||||
"For example, if two sites have a pair of high-bandwidth links available "
|
||||
"between them, it may be wise to configure a separate storage replication "
|
||||
"network between the two sites to support a single Swift endpoint and a "
|
||||
"shared object storage capability between them. (An example of this "
|
||||
"technique, as well as a configuration walk-through, is available at <link "
|
||||
"href=\"http://docs.openstack.org/developer/swift/replication_network.html"
|
||||
"#dedicated-replication-"
|
||||
@ -2013,18 +2016,18 @@ msgid ""
|
||||
"to build a dedicated set of tenant private networks across the secondary "
|
||||
"link using overlay networks with a third party mapping the site overlays to "
|
||||
"each other."
|
||||
msgstr "站点间的链接能力描述的是在不同的OpenStack站点之间连通性的能力。这里包含的参数有带宽、延迟，线路是否是专用、以及任何连接的业务规则认可。站点之间连接的能力和数量将决定部署时何种属性可用。例如，如果在两个站点之间有一组高带宽的连接可用，也许就想配置一个在两个站点之间分离的存储复制网络，以支持单一的Swift端点和共享的对象存储。 (此技术的一个更好的例子，详细的配置，请参阅 <link href=\"http://docs.openstack.org/developer/swift/replication_network.html#dedicated-replication-network\">http://docs.openstack.org/developer/swift/replication_network.html#dedicated-replication-network</link>)。此场景的另外一个属性是构建专用的一组租户私有网络，在第二条线路使用覆盖网络，一个第三方的映射在彼此的站点覆盖。"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/multi_site/section_tech_considerations_multi_site.xml38(para)
|
||||
msgid ""
|
||||
"The capacity requirements of the links between sites will be driven by "
|
||||
"The capacity requirements of the links between sites is driven by "
|
||||
"application behavior. If the latency of the links is too high, certain "
|
||||
"applications that use a large number of small packets, for example RPC "
|
||||
"calls, may encounter issues communicating with each other or operating "
|
||||
"properly. Additionally, OpenStack may encounter similar types of issues. To "
|
||||
"mitigate this, tuning of the Identity service call timeouts may be necessary"
|
||||
" to prevent issues authenticating against a central Identity service."
|
||||
msgstr "应用的行为驱动着站点之间线路能力的需求，如果线路的延迟太高，某些应用使用大量的小包，比如RPC调用，就会遭遇彼此之间的通信问题和正确操作的问题。另外，OpenStack会遇到类似的问题，为了降低这些问题的发生几率，优化认证服务调用的超时时间就非常的有必要，这样可以防止认证在中心化身份服务的冲突。"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/multi_site/section_tech_considerations_multi_site.xml47(para)
|
||||
msgid ""
|
||||
@ -2036,8 +2039,8 @@ msgid ""
|
||||
"IDs between the zones are identical. Note that, as of the Icehouse release, "
|
||||
"OpenStack Networking was not capable of managing tunnel IDs across "
|
||||
"installations. This means that if one site runs out of IDs, but other does "
|
||||
"not, that tenant's network will be unable to reach the other site."
|
||||
msgstr "另外关于容量的考虑因素，当它涉及到多站点部署网络的可用量时，以及对于租户网络的负载网络的性能。如果使用了跨zone的共享租户网络，那么将外部覆盖管理或控制器映射到一起就很迫切。非常有必要确保zone之间的ID量一致。记住，在Icehouse版本发布时，OpenStack网络还没有在安装时拥有管理隧道ID的能力，这意味着如果其中一个站点用完了ID，但是另外一个站点没有用完，租户网络将无法达到其它站点。"
|
||||
"not, that tenant's network is unable to reach the other site."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/multi_site/section_tech_considerations_multi_site.xml58(para)
|
||||
msgid ""
|
||||
@ -2094,25 +2097,25 @@ msgstr "身份是多数OpenStack用户的第一道“门槛”，对于绝大多
|
||||
msgid ""
|
||||
"Load balancing is another common issue with multi-site installations. While "
|
||||
"it is still possible to run HAproxy instances with Load-Balancer-"
|
||||
"as-a-Service, these will be local to a specific region. Some applications "
|
||||
"may be able to cope with this via internal mechanisms. Others, however, may "
|
||||
"as-a-Service, these are local to a specific region. Some applications may be"
|
||||
" able to cope with this via internal mechanisms. Others, however, may "
|
||||
"require the implementation of an external system including global services "
|
||||
"load balancers or anycast-advertised DNS."
|
||||
msgstr "负载均衡是安装多站点OpenStack另外一个常见的问题，它可能运行着负载均衡即服务的HAproxy实例，这些可能是本地一个特定的region，一些应用也许通过内部机制来应对这种情况，另外，也许需要外部的系统来实现，诸如全局服务负载均衡器或者anycast-advertised DNS。"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/multi_site/section_tech_considerations_multi_site.xml102(para)
|
||||
msgid ""
|
||||
"Depending on the storage model chosen during site design, storage "
|
||||
"replication and availability will also be a concern for end-users. If an "
|
||||
"replication and availability are also a concern for end-users. If an "
|
||||
"application is capable of understanding regions, then it is possible to keep"
|
||||
" the object storage system separated by region. In this case, users who want"
|
||||
" to have an object available to more than one region will need to do the "
|
||||
"cross-site replication themselves. With a centralized swift proxy, however, "
|
||||
"the user may need to benchmark the replication timing of the Object Storage "
|
||||
"back end. Benchmarking allows the operational staff to provide users with an"
|
||||
" understanding of the amount of time required for a stored or modified "
|
||||
"object to become available to the entire environment."
|
||||
msgstr "取决于在设计站点时的选择的存储模式，存储的复制和可用性也是最终用户所关心的。如果一个应用有理解region的能力，那么它可能会保持通过region分离的对象存储系统，在此种情形下，用户需要在多个region访问对象的话就需要去自己去跨站点复制，基于中心化的swift代理，用户也许需要后端对象存储的复制基准时间。测试基准允许运维人员提供给用户可以理解的存储需求的总计时间或者是更改对象使之在整个环境中可用。"
|
||||
" to have an object available to more than one region need to do the cross-"
|
||||
"site replication themselves. With a centralized swift proxy, however, the "
|
||||
"user may need to benchmark the replication timing of the Object Storage back"
|
||||
" end. Benchmarking allows the operational staff to provide users with an "
|
||||
"understanding of the amount of time required for a stored or modified object"
|
||||
" to become available to the entire environment."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/multi_site/section_tech_considerations_multi_site.xml114(title)
|
||||
#: ./doc/arch-design/network_focus/section_tech_considerations_network_focus.xml432(title)
|
||||
@ -2157,9 +2160,9 @@ msgid ""
|
||||
"was not created. Some applications may need to be tuned to account for this "
|
||||
"effect. Block Storage does not currently have a method for replicating data "
|
||||
"across multiple regions, so applications that depend on available block "
|
||||
"storage will need to manually cope with this limitation by creating "
|
||||
"duplicate block storage entries in each region."
|
||||
msgstr "在一个多区域部署中，存储可用性也会影响到架构。一个中心化的对象存储服务需要在region中为实例本地存取对象中频繁的使用，在对象没有建立的地方。一些应用也许为此而需要作出相应的调整。块存储目前还没有跨多个region的复制数据的方法，所以应用若依赖可用的块存储的话，需要手动的复制，由于这种限制导致在每个region都要创建重复的块存储。"
|
||||
"storage need to manually cope with this limitation by creating duplicate "
|
||||
"block storage entries in each region."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/multi_site/section_tech_considerations_multi_site.xml139(title)
|
||||
#: ./doc/arch-design/network_focus/section_user_requirements_network_focus.xml163(title)
|
||||
@ -2182,10 +2185,10 @@ msgid ""
|
||||
"Tenants may expect a tenant-created network to be secure. In a multi-site "
|
||||
"installation the use of a non-private connection between sites may be "
|
||||
"required. This may mean that traffic would be visible to third parties and, "
|
||||
"in cases where an application requires security, this issue will require "
|
||||
"in cases where an application requires security, this issue requires "
|
||||
"mitigation. Installing a VPN or encrypted connection between sites is "
|
||||
"recommended in such instances."
|
||||
msgstr "多区域OpenStack安装的安全会来带额外的挑战，租户会为了安全会建立一个租户创建的网络。在多区域站点安装中也许没有需求去使用非私有网络来连接站点，这意味着流量对于第三方来说是可见的，假如应用对安全有需求，这就是个问题需要去解决，安全一VPN或者将连接加密在站点之间，在此情形下就非常有必要。"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/multi_site/section_tech_considerations_multi_site.xml148(para)
|
||||
msgid ""
|
||||
|
||||
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
@ -19,8 +19,8 @@
|
||||
msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: OpenStack Manuals\n"
|
||||
"POT-Creation-Date: 2015-03-25 04:19+0000\n"
|
||||
"PO-Revision-Date: 2015-03-25 03:40+0000\n"
|
||||
"POT-Creation-Date: 2015-03-26 05:47+0000\n"
|
||||
"PO-Revision-Date: 2015-03-25 15:53+0000\n"
|
||||
"Last-Translator: openstackjenkins <jenkins@openstack.org>\n"
|
||||
"Language-Team: French (http://www.transifex.com/projects/p/openstack-manuals-i18n/language/fr/)\n"
|
||||
"MIME-Version: 1.0\n"
|
||||
@ -16381,13 +16381,13 @@ msgstr "Aucun"
|
||||
#: ./doc/common/tables/heat-rabbitmq.xml81(td)
|
||||
#: ./doc/common/tables/heat-rabbitmq.xml85(td)
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml20(td)
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml24(td)
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml28(td)
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml25(td)
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml32(td)
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml36(td)
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml40(td)
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml44(td)
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml52(td)
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml41(td)
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml46(td)
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml50(td)
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml59(td)
|
||||
#: ./doc/common/tables/keystone-amqp.xml21(td)
|
||||
#: ./doc/common/tables/keystone-amqp.xml25(td)
|
||||
#: ./doc/common/tables/keystone-amqp.xml29(td)
|
||||
@ -20422,7 +20422,7 @@ msgstr "(IntOpt) Nombre minimum de connexions SQL à garder ouvertes dans un poo
|
||||
#: ./doc/common/tables/heat-rabbitmq.xml29(td)
|
||||
#: ./doc/common/tables/heat-rabbitmq.xml33(td)
|
||||
#: ./doc/common/tables/heat-rabbitmq.xml37(td)
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml48(td)
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml54(td)
|
||||
#: ./doc/common/tables/keystone-rpc.xml76(td)
|
||||
#: ./doc/common/tables/keystone-rpc.xml80(td)
|
||||
#: ./doc/common/tables/keystone-rpc.xml84(td)
|
||||
@ -22269,7 +22269,7 @@ msgstr ""
|
||||
#: ./doc/common/tables/glance-policy.xml21(replaceable)
|
||||
#: ./doc/common/tables/nova-neutron.xml21(replaceable)
|
||||
#: ./doc/common/tables/keystone-ldap.xml21(replaceable)
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml28(replaceable)
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml32(replaceable)
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml56(replaceable)
|
||||
#: ./doc/common/tables/ceilometer-api.xml33(replaceable)
|
||||
#: ./doc/common/tables/cinder-lvm.xml29(replaceable)
|
||||
@ -23853,13 +23853,6 @@ msgstr ""
|
||||
#: ./doc/common/tables/swift-object-server-filter-healthcheck.xml21(td)
|
||||
#: ./doc/common/tables/swift-object-server-app-object-server.xml93(td)
|
||||
#: ./doc/common/tables/swift-container-reconciler-container-reconciler.xml29(td)
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml21(td)
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml25(td)
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml29(td)
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml33(td)
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml37(td)
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml41(td)
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml49(td)
|
||||
#: ./doc/common/tables/swift-object-server-DEFAULT.xml61(td)
|
||||
#: ./doc/common/tables/swift-object-server-DEFAULT.xml65(td)
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml21(td)
|
||||
@ -23912,11 +23905,6 @@ msgstr ""
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-authtoken.xml45(td)
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-authtoken.xml49(td)
|
||||
#: ./doc/common/tables/swift-object-server-pipeline-main.xml21(td)
|
||||
#: ./doc/common/tables/swift-memcache-memcache.xml21(td)
|
||||
#: ./doc/common/tables/swift-memcache-memcache.xml25(td)
|
||||
#: ./doc/common/tables/swift-memcache-memcache.xml33(td)
|
||||
#: ./doc/common/tables/swift-memcache-memcache.xml41(td)
|
||||
#: ./doc/common/tables/swift-memcache-memcache.xml45(td)
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml21(td)
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml25(td)
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml29(td)
|
||||
@ -23999,7 +23987,7 @@ msgstr ""
|
||||
#: ./doc/common/tables/swift-object-server-app-object-server.xml28(replaceable)
|
||||
#: ./doc/common/tables/swift-object-server-app-object-server.xml64(replaceable)
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-catch_errors.xml28(replaceable)
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml32(replaceable)
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml36(replaceable)
|
||||
#: ./doc/common/tables/swift-object-server-DEFAULT.xml48(replaceable)
|
||||
#: ./doc/common/tables/swift-object-server-DEFAULT.xml56(replaceable)
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml44(replaceable)
|
||||
@ -24061,7 +24049,7 @@ msgstr ""
|
||||
#: ./doc/common/tables/swift-container-server-DEFAULT.xml126(replaceable)
|
||||
#: ./doc/common/tables/swift-object-server-app-object-server.xml84(replaceable)
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml20(replaceable)
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml24(replaceable)
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml25(replaceable)
|
||||
#: ./doc/common/tables/swift-object-server-DEFAULT.xml138(replaceable)
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml20(replaceable)
|
||||
#: ./doc/common/tables/swift-account-server-app-account-server.xml44(replaceable)
|
||||
@ -25698,7 +25686,7 @@ msgstr ""
|
||||
#: ./doc/common/tables/swift-object-server-filter-healthcheck.xml25(td)
|
||||
#: ./doc/common/tables/swift-object-server-app-object-server.xml101(td)
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-catch_errors.xml41(td)
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml53(td)
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml60(td)
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml65(td)
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-gatekeeper.xml41(td)
|
||||
#: ./doc/common/tables/swift-object-expirer-filter-proxy-logging.xml92(td)
|
||||
@ -29801,7 +29789,6 @@ msgid "127.0.0.1:11211"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-cache.xml29(td)
|
||||
#: ./doc/common/tables/swift-memcache-memcache.xml37(td)
|
||||
msgid "Comma separated list of memcached servers ip:port services"
|
||||
msgstr ""
|
||||
|
||||
@ -36343,26 +36330,74 @@ msgstr ""
|
||||
msgid "[filter-keystoneauth]"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml36(replaceable)
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml21(td)
|
||||
msgid ""
|
||||
"The backwards compatible behavior can be disabled by setting this option to "
|
||||
"False."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml26(td)
|
||||
msgid ""
|
||||
"This option allows middleware higher in the WSGI pipeline to override auth "
|
||||
"processing, useful for middleware such as tempurl and formpost. If you know "
|
||||
"you are not going to use such middleware and you want a bit of extra "
|
||||
"security, you can set this to False."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml33(td)
|
||||
msgid ""
|
||||
"Name of the default domain. It is identified by its UUID, which by default "
|
||||
"has the value \"default\"."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml37(td)
|
||||
msgid ""
|
||||
"If this option is set to True, it allows to give a user whose username is "
|
||||
"the same as the project name and who has any role in the project access "
|
||||
"rights elevated to be the same as if the user had one of the "
|
||||
"<placeholder-1/>. Note that the condition compares names rather than UUIDs. "
|
||||
"This option is deprecated. It is False by default."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml41(replaceable)
|
||||
msgid "admin, swiftoperator"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml40(replaceable)
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml42(td)
|
||||
msgid ""
|
||||
"Operator role defines the user which is allowed to manage a tenant and "
|
||||
"create containers or give ACL to others. This parameter may be prefixed with"
|
||||
" an appropriate prefix."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml46(replaceable)
|
||||
msgid "ResellerAdmin"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml44(replaceable)
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml47(td)
|
||||
msgid ""
|
||||
"The reseller admin role gives the ability to create and delete accounts."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml50(replaceable)
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml32(replaceable)
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-domain_remap.xml24(replaceable)
|
||||
msgid "AUTH"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml45(td)
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml51(td)
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml33(td)
|
||||
msgid "The naming scope for the auth service. Swift"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml52(replaceable)
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml55(td)
|
||||
msgid ""
|
||||
"When present, this option requires that the X-Service-Token header supplies "
|
||||
"a token from a user who has a role listed in service_roles. This parameter "
|
||||
"may be prefixed with an appropriate prefix."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml59(replaceable)
|
||||
msgid "egg:swift#keystoneauth"
|
||||
msgstr ""
|
||||
|
||||
@ -42350,6 +42385,30 @@ msgstr ""
|
||||
msgid "0.3"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/common/tables/swift-memcache-memcache.xml21(td)
|
||||
msgid "Timeout in seconds (float) for connection"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/common/tables/swift-memcache-memcache.xml25(td)
|
||||
msgid "Timeout in seconds (float) for read and write"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/common/tables/swift-memcache-memcache.xml33(td)
|
||||
msgid "Sets how memcache values are serialized and deserialized"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/common/tables/swift-memcache-memcache.xml37(td)
|
||||
msgid "Comma-separated list of memcached servers ip:port services"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/common/tables/swift-memcache-memcache.xml41(td)
|
||||
msgid "Timeout in seconds (float) for pooled connection"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/common/tables/swift-memcache-memcache.xml45(td)
|
||||
msgid "Number of servers to retry on failures getting a pooled connection"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/common/tables/ceilometer-debug.xml26(td)
|
||||
msgid "(BoolOpt) Allow novaclient's debug log output."
|
||||
msgstr ""
|
||||
|
||||
@ -7,8 +7,8 @@
|
||||
msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: OpenStack Manuals\n"
|
||||
"POT-Creation-Date: 2015-03-25 04:19+0000\n"
|
||||
"PO-Revision-Date: 2015-03-25 03:40+0000\n"
|
||||
"POT-Creation-Date: 2015-03-26 05:47+0000\n"
|
||||
"PO-Revision-Date: 2015-03-26 03:30+0000\n"
|
||||
"Last-Translator: openstackjenkins <jenkins@openstack.org>\n"
|
||||
"Language-Team: Japanese (http://www.transifex.com/projects/p/openstack-manuals-i18n/language/ja/)\n"
|
||||
"MIME-Version: 1.0\n"
|
||||
@ -16369,13 +16369,13 @@ msgstr "なし"
|
||||
#: ./doc/common/tables/heat-rabbitmq.xml81(td)
|
||||
#: ./doc/common/tables/heat-rabbitmq.xml85(td)
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml20(td)
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml24(td)
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml28(td)
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml25(td)
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml32(td)
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml36(td)
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml40(td)
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml44(td)
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml52(td)
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml41(td)
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml46(td)
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml50(td)
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml59(td)
|
||||
#: ./doc/common/tables/keystone-amqp.xml21(td)
|
||||
#: ./doc/common/tables/keystone-amqp.xml25(td)
|
||||
#: ./doc/common/tables/keystone-amqp.xml29(td)
|
||||
@ -20410,7 +20410,7 @@ msgstr ""
|
||||
#: ./doc/common/tables/heat-rabbitmq.xml29(td)
|
||||
#: ./doc/common/tables/heat-rabbitmq.xml33(td)
|
||||
#: ./doc/common/tables/heat-rabbitmq.xml37(td)
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml48(td)
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml54(td)
|
||||
#: ./doc/common/tables/keystone-rpc.xml76(td)
|
||||
#: ./doc/common/tables/keystone-rpc.xml80(td)
|
||||
#: ./doc/common/tables/keystone-rpc.xml84(td)
|
||||
@ -22257,7 +22257,7 @@ msgstr ""
|
||||
#: ./doc/common/tables/glance-policy.xml21(replaceable)
|
||||
#: ./doc/common/tables/nova-neutron.xml21(replaceable)
|
||||
#: ./doc/common/tables/keystone-ldap.xml21(replaceable)
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml28(replaceable)
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml32(replaceable)
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml56(replaceable)
|
||||
#: ./doc/common/tables/ceilometer-api.xml33(replaceable)
|
||||
#: ./doc/common/tables/cinder-lvm.xml29(replaceable)
|
||||
@ -23841,13 +23841,6 @@ msgstr ""
|
||||
#: ./doc/common/tables/swift-object-server-filter-healthcheck.xml21(td)
|
||||
#: ./doc/common/tables/swift-object-server-app-object-server.xml93(td)
|
||||
#: ./doc/common/tables/swift-container-reconciler-container-reconciler.xml29(td)
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml21(td)
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml25(td)
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml29(td)
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml33(td)
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml37(td)
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml41(td)
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml49(td)
|
||||
#: ./doc/common/tables/swift-object-server-DEFAULT.xml61(td)
|
||||
#: ./doc/common/tables/swift-object-server-DEFAULT.xml65(td)
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml21(td)
|
||||
@ -23900,11 +23893,6 @@ msgstr ""
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-authtoken.xml45(td)
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-authtoken.xml49(td)
|
||||
#: ./doc/common/tables/swift-object-server-pipeline-main.xml21(td)
|
||||
#: ./doc/common/tables/swift-memcache-memcache.xml21(td)
|
||||
#: ./doc/common/tables/swift-memcache-memcache.xml25(td)
|
||||
#: ./doc/common/tables/swift-memcache-memcache.xml33(td)
|
||||
#: ./doc/common/tables/swift-memcache-memcache.xml41(td)
|
||||
#: ./doc/common/tables/swift-memcache-memcache.xml45(td)
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml21(td)
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml25(td)
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml29(td)
|
||||
@ -23987,7 +23975,7 @@ msgstr ""
|
||||
#: ./doc/common/tables/swift-object-server-app-object-server.xml28(replaceable)
|
||||
#: ./doc/common/tables/swift-object-server-app-object-server.xml64(replaceable)
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-catch_errors.xml28(replaceable)
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml32(replaceable)
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml36(replaceable)
|
||||
#: ./doc/common/tables/swift-object-server-DEFAULT.xml48(replaceable)
|
||||
#: ./doc/common/tables/swift-object-server-DEFAULT.xml56(replaceable)
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml44(replaceable)
|
||||
@ -24049,7 +24037,7 @@ msgstr "86400"
|
||||
#: ./doc/common/tables/swift-container-server-DEFAULT.xml126(replaceable)
|
||||
#: ./doc/common/tables/swift-object-server-app-object-server.xml84(replaceable)
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml20(replaceable)
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml24(replaceable)
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml25(replaceable)
|
||||
#: ./doc/common/tables/swift-object-server-DEFAULT.xml138(replaceable)
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml20(replaceable)
|
||||
#: ./doc/common/tables/swift-account-server-app-account-server.xml44(replaceable)
|
||||
@ -25686,7 +25674,7 @@ msgstr ""
|
||||
#: ./doc/common/tables/swift-object-server-filter-healthcheck.xml25(td)
|
||||
#: ./doc/common/tables/swift-object-server-app-object-server.xml101(td)
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-catch_errors.xml41(td)
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml53(td)
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml60(td)
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml65(td)
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-gatekeeper.xml41(td)
|
||||
#: ./doc/common/tables/swift-object-expirer-filter-proxy-logging.xml92(td)
|
||||
@ -29789,7 +29777,6 @@ msgid "127.0.0.1:11211"
|
||||
msgstr "127.0.0.1:11211"
|
||||
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-cache.xml29(td)
|
||||
#: ./doc/common/tables/swift-memcache-memcache.xml37(td)
|
||||
msgid "Comma separated list of memcached servers ip:port services"
|
||||
msgstr ""
|
||||
|
||||
@ -36331,26 +36318,74 @@ msgstr ""
|
||||
msgid "[filter-keystoneauth]"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml36(replaceable)
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml21(td)
|
||||
msgid ""
|
||||
"The backwards compatible behavior can be disabled by setting this option to "
|
||||
"False."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml26(td)
|
||||
msgid ""
|
||||
"This option allows middleware higher in the WSGI pipeline to override auth "
|
||||
"processing, useful for middleware such as tempurl and formpost. If you know "
|
||||
"you are not going to use such middleware and you want a bit of extra "
|
||||
"security, you can set this to False."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml33(td)
|
||||
msgid ""
|
||||
"Name of the default domain. It is identified by its UUID, which by default "
|
||||
"has the value \"default\"."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml37(td)
|
||||
msgid ""
|
||||
"If this option is set to True, it allows to give a user whose username is "
|
||||
"the same as the project name and who has any role in the project access "
|
||||
"rights elevated to be the same as if the user had one of the "
|
||||
"<placeholder-1/>. Note that the condition compares names rather than UUIDs. "
|
||||
"This option is deprecated. It is False by default."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml41(replaceable)
|
||||
msgid "admin, swiftoperator"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml40(replaceable)
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml42(td)
|
||||
msgid ""
|
||||
"Operator role defines the user which is allowed to manage a tenant and "
|
||||
"create containers or give ACL to others. This parameter may be prefixed with"
|
||||
" an appropriate prefix."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml46(replaceable)
|
||||
msgid "ResellerAdmin"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml44(replaceable)
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml47(td)
|
||||
msgid ""
|
||||
"The reseller admin role gives the ability to create and delete accounts."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml50(replaceable)
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml32(replaceable)
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-domain_remap.xml24(replaceable)
|
||||
msgid "AUTH"
|
||||
msgstr "AUTH"
|
||||
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml45(td)
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml51(td)
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml33(td)
|
||||
msgid "The naming scope for the auth service. Swift"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml52(replaceable)
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml55(td)
|
||||
msgid ""
|
||||
"When present, this option requires that the X-Service-Token header supplies "
|
||||
"a token from a user who has a role listed in service_roles. This parameter "
|
||||
"may be prefixed with an appropriate prefix."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml59(replaceable)
|
||||
msgid "egg:swift#keystoneauth"
|
||||
msgstr ""
|
||||
|
||||
@ -42338,6 +42373,30 @@ msgstr ""
|
||||
msgid "0.3"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/common/tables/swift-memcache-memcache.xml21(td)
|
||||
msgid "Timeout in seconds (float) for connection"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/common/tables/swift-memcache-memcache.xml25(td)
|
||||
msgid "Timeout in seconds (float) for read and write"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/common/tables/swift-memcache-memcache.xml33(td)
|
||||
msgid "Sets how memcache values are serialized and deserialized"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/common/tables/swift-memcache-memcache.xml37(td)
|
||||
msgid "Comma-separated list of memcached servers ip:port services"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/common/tables/swift-memcache-memcache.xml41(td)
|
||||
msgid "Timeout in seconds (float) for pooled connection"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/common/tables/swift-memcache-memcache.xml45(td)
|
||||
msgid "Number of servers to retry on failures getting a pooled connection"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/common/tables/ceilometer-debug.xml26(td)
|
||||
msgid "(BoolOpt) Allow novaclient's debug log output."
|
||||
msgstr ""
|
||||
|
||||
@ -10,8 +10,8 @@
|
||||
msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: OpenStack Manuals\n"
|
||||
"POT-Creation-Date: 2015-03-25 04:19+0000\n"
|
||||
"PO-Revision-Date: 2015-03-25 03:14+0000\n"
|
||||
"POT-Creation-Date: 2015-03-26 05:47+0000\n"
|
||||
"PO-Revision-Date: 2015-03-25 15:53+0000\n"
|
||||
"Last-Translator: openstackjenkins <jenkins@openstack.org>\n"
|
||||
"Language-Team: Chinese (China) (http://www.transifex.com/projects/p/openstack-manuals-i18n/language/zh_CN/)\n"
|
||||
"MIME-Version: 1.0\n"
|
||||
@ -892,7 +892,7 @@ msgstr ""
|
||||
|
||||
#: ./doc/common/section_cli_nova_quotas.xml207(replaceable)
|
||||
msgid "value"
|
||||
msgstr ""
|
||||
msgstr "值"
|
||||
|
||||
#: ./doc/common/section_cli_nova_quotas.xml214(title)
|
||||
msgid "To view quota values for an existing tenant (project)"
|
||||
@ -16372,13 +16372,13 @@ msgstr "无"
|
||||
#: ./doc/common/tables/heat-rabbitmq.xml81(td)
|
||||
#: ./doc/common/tables/heat-rabbitmq.xml85(td)
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml20(td)
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml24(td)
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml28(td)
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml25(td)
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml32(td)
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml36(td)
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml40(td)
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml44(td)
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml52(td)
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml41(td)
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml46(td)
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml50(td)
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml59(td)
|
||||
#: ./doc/common/tables/keystone-amqp.xml21(td)
|
||||
#: ./doc/common/tables/keystone-amqp.xml25(td)
|
||||
#: ./doc/common/tables/keystone-amqp.xml29(td)
|
||||
@ -20413,7 +20413,7 @@ msgstr ""
|
||||
#: ./doc/common/tables/heat-rabbitmq.xml29(td)
|
||||
#: ./doc/common/tables/heat-rabbitmq.xml33(td)
|
||||
#: ./doc/common/tables/heat-rabbitmq.xml37(td)
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml48(td)
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml54(td)
|
||||
#: ./doc/common/tables/keystone-rpc.xml76(td)
|
||||
#: ./doc/common/tables/keystone-rpc.xml80(td)
|
||||
#: ./doc/common/tables/keystone-rpc.xml84(td)
|
||||
@ -22260,7 +22260,7 @@ msgstr ""
|
||||
#: ./doc/common/tables/glance-policy.xml21(replaceable)
|
||||
#: ./doc/common/tables/nova-neutron.xml21(replaceable)
|
||||
#: ./doc/common/tables/keystone-ldap.xml21(replaceable)
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml28(replaceable)
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml32(replaceable)
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml56(replaceable)
|
||||
#: ./doc/common/tables/ceilometer-api.xml33(replaceable)
|
||||
#: ./doc/common/tables/cinder-lvm.xml29(replaceable)
|
||||
@ -23844,13 +23844,6 @@ msgstr ""
|
||||
#: ./doc/common/tables/swift-object-server-filter-healthcheck.xml21(td)
|
||||
#: ./doc/common/tables/swift-object-server-app-object-server.xml93(td)
|
||||
#: ./doc/common/tables/swift-container-reconciler-container-reconciler.xml29(td)
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml21(td)
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml25(td)
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml29(td)
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml33(td)
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml37(td)
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml41(td)
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml49(td)
|
||||
#: ./doc/common/tables/swift-object-server-DEFAULT.xml61(td)
|
||||
#: ./doc/common/tables/swift-object-server-DEFAULT.xml65(td)
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml21(td)
|
||||
@ -23903,11 +23896,6 @@ msgstr ""
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-authtoken.xml45(td)
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-authtoken.xml49(td)
|
||||
#: ./doc/common/tables/swift-object-server-pipeline-main.xml21(td)
|
||||
#: ./doc/common/tables/swift-memcache-memcache.xml21(td)
|
||||
#: ./doc/common/tables/swift-memcache-memcache.xml25(td)
|
||||
#: ./doc/common/tables/swift-memcache-memcache.xml33(td)
|
||||
#: ./doc/common/tables/swift-memcache-memcache.xml41(td)
|
||||
#: ./doc/common/tables/swift-memcache-memcache.xml45(td)
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml21(td)
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml25(td)
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml29(td)
|
||||
@ -23990,7 +23978,7 @@ msgstr ""
|
||||
#: ./doc/common/tables/swift-object-server-app-object-server.xml28(replaceable)
|
||||
#: ./doc/common/tables/swift-object-server-app-object-server.xml64(replaceable)
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-catch_errors.xml28(replaceable)
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml32(replaceable)
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml36(replaceable)
|
||||
#: ./doc/common/tables/swift-object-server-DEFAULT.xml48(replaceable)
|
||||
#: ./doc/common/tables/swift-object-server-DEFAULT.xml56(replaceable)
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml44(replaceable)
|
||||
@ -24052,7 +24040,7 @@ msgstr ""
|
||||
#: ./doc/common/tables/swift-container-server-DEFAULT.xml126(replaceable)
|
||||
#: ./doc/common/tables/swift-object-server-app-object-server.xml84(replaceable)
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml20(replaceable)
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml24(replaceable)
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml25(replaceable)
|
||||
#: ./doc/common/tables/swift-object-server-DEFAULT.xml138(replaceable)
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml20(replaceable)
|
||||
#: ./doc/common/tables/swift-account-server-app-account-server.xml44(replaceable)
|
||||
@ -25689,7 +25677,7 @@ msgstr ""
|
||||
#: ./doc/common/tables/swift-object-server-filter-healthcheck.xml25(td)
|
||||
#: ./doc/common/tables/swift-object-server-app-object-server.xml101(td)
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-catch_errors.xml41(td)
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml53(td)
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml60(td)
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml65(td)
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-gatekeeper.xml41(td)
|
||||
#: ./doc/common/tables/swift-object-expirer-filter-proxy-logging.xml92(td)
|
||||
@ -29792,7 +29780,6 @@ msgid "127.0.0.1:11211"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-cache.xml29(td)
|
||||
#: ./doc/common/tables/swift-memcache-memcache.xml37(td)
|
||||
msgid "Comma separated list of memcached servers ip:port services"
|
||||
msgstr ""
|
||||
|
||||
@ -36334,26 +36321,74 @@ msgstr ""
|
||||
msgid "[filter-keystoneauth]"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml36(replaceable)
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml21(td)
|
||||
msgid ""
|
||||
"The backwards compatible behavior can be disabled by setting this option to "
|
||||
"False."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml26(td)
|
||||
msgid ""
|
||||
"This option allows middleware higher in the WSGI pipeline to override auth "
|
||||
"processing, useful for middleware such as tempurl and formpost. If you know "
|
||||
"you are not going to use such middleware and you want a bit of extra "
|
||||
"security, you can set this to False."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml33(td)
|
||||
msgid ""
|
||||
"Name of the default domain. It is identified by its UUID, which by default "
|
||||
"has the value \"default\"."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml37(td)
|
||||
msgid ""
|
||||
"If this option is set to True, it allows to give a user whose username is "
|
||||
"the same as the project name and who has any role in the project access "
|
||||
"rights elevated to be the same as if the user had one of the "
|
||||
"<placeholder-1/>. Note that the condition compares names rather than UUIDs. "
|
||||
"This option is deprecated. It is False by default."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml41(replaceable)
|
||||
msgid "admin, swiftoperator"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml40(replaceable)
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml42(td)
|
||||
msgid ""
|
||||
"Operator role defines the user which is allowed to manage a tenant and "
|
||||
"create containers or give ACL to others. This parameter may be prefixed with"
|
||||
" an appropriate prefix."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml46(replaceable)
|
||||
msgid "ResellerAdmin"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml44(replaceable)
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml47(td)
|
||||
msgid ""
|
||||
"The reseller admin role gives the ability to create and delete accounts."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml50(replaceable)
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml32(replaceable)
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-domain_remap.xml24(replaceable)
|
||||
msgid "AUTH"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml45(td)
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml51(td)
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml33(td)
|
||||
msgid "The naming scope for the auth service. Swift"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml52(replaceable)
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml55(td)
|
||||
msgid ""
|
||||
"When present, this option requires that the X-Service-Token header supplies "
|
||||
"a token from a user who has a role listed in service_roles. This parameter "
|
||||
"may be prefixed with an appropriate prefix."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml59(replaceable)
|
||||
msgid "egg:swift#keystoneauth"
|
||||
msgstr ""
|
||||
|
||||
@ -42341,6 +42376,30 @@ msgstr ""
|
||||
msgid "0.3"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/common/tables/swift-memcache-memcache.xml21(td)
|
||||
msgid "Timeout in seconds (float) for connection"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/common/tables/swift-memcache-memcache.xml25(td)
|
||||
msgid "Timeout in seconds (float) for read and write"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/common/tables/swift-memcache-memcache.xml33(td)
|
||||
msgid "Sets how memcache values are serialized and deserialized"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/common/tables/swift-memcache-memcache.xml37(td)
|
||||
msgid "Comma-separated list of memcached servers ip:port services"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/common/tables/swift-memcache-memcache.xml41(td)
|
||||
msgid "Timeout in seconds (float) for pooled connection"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/common/tables/swift-memcache-memcache.xml45(td)
|
||||
msgid "Number of servers to retry on failures getting a pooled connection"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/common/tables/ceilometer-debug.xml26(td)
|
||||
msgid "(BoolOpt) Allow novaclient's debug log output."
|
||||
msgstr ""
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: PACKAGE VERSION\n"
|
||||
"POT-Creation-Date: 2015-03-25 06:08+0000\n"
|
||||
"POT-Creation-Date: 2015-03-26 06:09+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"
|
||||
@ -2290,7 +2290,7 @@ msgstr ""
|
||||
msgid "Dashboard/httpd log files"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/dashboard/section_dashboard-log-files.xml:22(td) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:127(th) ./doc/config-reference/block-storage/drivers/ibm-gpfs-volume-driver.xml:80(th) ./doc/config-reference/block-storage/drivers/ibm-flashsystem-volume-driver.xml:92(th) ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:309(td) ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:206(th) ./doc/config-reference/block-storage/drivers/coraid-driver.xml:371(th) ./doc/config-reference/block-storage/drivers/hds-hnas-driver.xml:378(td) ./doc/config-reference/compute/section_compute-scheduler.xml:812(th) ./doc/config-reference/compute/section_compute-scheduler.xml:916(th)
|
||||
#: ./doc/config-reference/dashboard/section_dashboard-log-files.xml:22(td) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:127(th) ./doc/config-reference/block-storage/drivers/ibm-gpfs-volume-driver.xml:80(th) ./doc/config-reference/block-storage/drivers/ibm-flashsystem-volume-driver.xml:92(th) ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:309(td) ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:206(th) ./doc/config-reference/block-storage/drivers/coraid-driver.xml:371(th) ./doc/config-reference/block-storage/drivers/hds-hnas-driver.xml:378(td) ./doc/config-reference/compute/section_compute-scheduler.xml:851(th) ./doc/config-reference/compute/section_compute-scheduler.xml:955(th)
|
||||
msgid "Description"
|
||||
msgstr ""
|
||||
|
||||
@ -3786,7 +3786,7 @@ msgstr ""
|
||||
msgid "Typically a OpenStack Block Storage volume instance has only one such service label. For example, any <literal>svc_0</literal>, <literal>svc_1</literal>, <literal>svc_2</literal>, or <literal>svc_3</literal> can be associated with it. But any mix of these service labels can be used in the same instance <placeholder-1/>."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:306(td) ./doc/config-reference/block-storage/drivers/hds-hnas-driver.xml:375(td) ./doc/config-reference/compute/section_compute-scheduler.xml:811(th) ./doc/config-reference/compute/section_compute-scheduler.xml:915(th)
|
||||
#: ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:306(td) ./doc/config-reference/block-storage/drivers/hds-hnas-driver.xml:375(td) ./doc/config-reference/compute/section_compute-scheduler.xml:850(th) ./doc/config-reference/compute/section_compute-scheduler.xml:954(th)
|
||||
msgid "Option"
|
||||
msgstr ""
|
||||
|
||||
@ -9423,7 +9423,7 @@ msgstr ""
|
||||
msgid "Sections"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_nova-conf.xml:32(literal) ./doc/config-reference/compute/section_compute-scheduler.xml:817(td) ./doc/config-reference/compute/section_compute-scheduler.xml:827(td) ./doc/config-reference/compute/section_compute-scheduler.xml:839(td)
|
||||
#: ./doc/config-reference/compute/section_nova-conf.xml:32(literal) ./doc/config-reference/compute/section_compute-scheduler.xml:856(td) ./doc/config-reference/compute/section_compute-scheduler.xml:866(td) ./doc/config-reference/compute/section_compute-scheduler.xml:878(td)
|
||||
msgid "[DEFAULT]"
|
||||
msgstr ""
|
||||
|
||||
@ -9439,7 +9439,7 @@ msgstr ""
|
||||
msgid "Configures the baremetal hypervisor driver."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_nova-conf.xml:49(literal) ./doc/config-reference/compute/section_compute-scheduler.xml:921(td) ./doc/config-reference/compute/section_compute-scheduler.xml:929(td) ./doc/config-reference/compute/section_compute-scheduler.xml:936(td) ./doc/config-reference/compute/section_compute-scheduler.xml:943(td) ./doc/config-reference/compute/section_compute-scheduler.xml:953(td)
|
||||
#: ./doc/config-reference/compute/section_nova-conf.xml:49(literal) ./doc/config-reference/compute/section_compute-scheduler.xml:960(td) ./doc/config-reference/compute/section_compute-scheduler.xml:968(td) ./doc/config-reference/compute/section_compute-scheduler.xml:975(td) ./doc/config-reference/compute/section_compute-scheduler.xml:982(td) ./doc/config-reference/compute/section_compute-scheduler.xml:992(td)
|
||||
msgid "[cells]"
|
||||
msgstr ""
|
||||
|
||||
@ -9527,7 +9527,7 @@ msgstr ""
|
||||
msgid "Configures a matchmaker ring."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_nova-conf.xml:142(literal) ./doc/config-reference/compute/section_compute-scheduler.xml:848(td) ./doc/config-reference/compute/section_compute-scheduler.xml:854(td) ./doc/config-reference/compute/section_compute-scheduler.xml:864(td) ./doc/config-reference/compute/section_compute-scheduler.xml:886(td)
|
||||
#: ./doc/config-reference/compute/section_nova-conf.xml:142(literal) ./doc/config-reference/compute/section_compute-scheduler.xml:887(td) ./doc/config-reference/compute/section_compute-scheduler.xml:893(td) ./doc/config-reference/compute/section_compute-scheduler.xml:903(td) ./doc/config-reference/compute/section_compute-scheduler.xml:925(td)
|
||||
msgid "[metrics]"
|
||||
msgstr ""
|
||||
|
||||
@ -11291,7 +11291,7 @@ msgstr ""
|
||||
msgid "When using the VMwareVCDriver (vCenter) with OpenStack Compute with vSphere version 5.0 or earlier, <filename>nova.conf</filename> must include the following extra config option:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:1031(title) ./doc/config-reference/compute/section_compute-scheduler.xml:984(title)
|
||||
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:1031(title) ./doc/config-reference/compute/section_compute-scheduler.xml:1023(title)
|
||||
msgid "Configuration reference"
|
||||
msgstr ""
|
||||
|
||||
@ -11571,7 +11571,7 @@ msgstr ""
|
||||
|
||||
#. 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.
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:794(None)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:833(None)
|
||||
msgid "@@image: '../../common/figures/nova-weighting-hosts.png'; md5=000eab4cf0deb1da2e692e023065a6ae"
|
||||
msgstr ""
|
||||
|
||||
@ -11868,458 +11868,470 @@ msgid "Only schedules instances on hosts if there is sufficient disk space avail
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:419(para)
|
||||
msgid "You can configure this filter to enable a fixed amount of disk overcommitment by using the <literal>disk_allocation_ratio</literal> configuration option in <filename>nova.conf</filename>. The default setting is:"
|
||||
msgid "You can configure this filter to enable a fixed amount of disk overcommitment by using the <literal>disk_allocation_ratio</literal> configuration option in the <filename>nova.conf</filename> configuration file. The default setting disables the possibility of the overcommitment and allows launching a VM only if there is a sufficient amount of disk space available on a host:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:426(para)
|
||||
msgid "Adjusting this value to greater than 1.0 enables scheduling instances while over committing disk resources on the node. This might be desirable if you use an image format that is sparse or copy on write so that each virtual instance does not require a 1:1 allocation of virtual disk to physical storage."
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:429(para)
|
||||
msgid "DiskFilter always considers the value of the <placeholder-1/> property and not the one of the <placeholder-2/> property of a hypervisor's statistics:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:434(title)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:450(para)
|
||||
msgid "As it can be viewed from the command output above, the amount of the available disk space can be less than the amount of the free disk space. It happens because the <placeholder-1/> property accounts for the virtual size rather than the actual size of images. If you use an image format that is sparse or copy on write so that each virtual instance does not require a 1:1 allocation of a virtual disk to a physical storage, it may be useful to allow the overcommitment of disk space."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:460(para)
|
||||
msgid "To enable scheduling instances while overcommitting disk resources on the node, adjust the value of the <literal>disk_allocation_ratio</literal> configuration option to greater than <literal>1.0</literal>:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:466(para)
|
||||
msgid "If the value is set to <literal>>1</literal>, we recommend keeping track of the free disk space, as the value approaching <literal>0</literal> may result in the incorrect functioning of instances using it at the moment."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:473(title)
|
||||
msgid "GroupAffinityFilter"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:436(para)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:475(para)
|
||||
msgid "This filter is deprecated in favor of <link linkend=\"servergroupantiaffinityfilter\">ServerGroupAffinityFilter</link>."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:440(para)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:479(para)
|
||||
msgid "The GroupAffinityFilter ensures that an instance is scheduled on to a host from a set of group hosts. To take advantage of this filter, the requester must pass a scheduler hint, using <literal>group</literal> as the key and an arbitrary name as the value. Using the <placeholder-1/> command-line tool, use the <literal>--hint</literal> flag. For example:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:448(replaceable) ./doc/config-reference/compute/section_compute-scheduler.xml:469(replaceable) ./doc/config-reference/compute/section_compute-scheduler.xml:706(replaceable) ./doc/config-reference/compute/section_compute-scheduler.xml:721(replaceable)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:487(replaceable) ./doc/config-reference/compute/section_compute-scheduler.xml:508(replaceable) ./doc/config-reference/compute/section_compute-scheduler.xml:745(replaceable) ./doc/config-reference/compute/section_compute-scheduler.xml:760(replaceable)
|
||||
msgid "IMAGE_ID"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:449(para)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:488(para)
|
||||
msgid "This filter should not be enabled at the same time as <link linkend=\"groupantiaffinityfilter\">GroupAntiAffinityFilter</link> or neither filter will work properly."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:455(title)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:494(title)
|
||||
msgid "GroupAntiAffinityFilter"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:457(para)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:496(para)
|
||||
msgid "This filter is deprecated in favor of <link linkend=\"servergroupantiaffinityfilter\">ServerGroupAntiAffinityFilter</link>."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:461(para)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:500(para)
|
||||
msgid "The GroupAntiAffinityFilter ensures that each instance in a group is on a different host. To take advantage of this filter, the requester must pass a scheduler hint, using <literal>group</literal> as the key and an arbitrary name as the value. Using the <placeholder-1/> command-line tool, use the <literal>--hint</literal> flag. For example:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:470(para)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:509(para)
|
||||
msgid "This filter should not be enabled at the same time as <link linkend=\"groupaffinityfilter\">GroupAffinityFilter</link> or neither filter will work properly."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:476(title)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:515(title)
|
||||
msgid "ImagePropertiesFilter"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:477(para)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:516(para)
|
||||
msgid "Filters hosts based on properties defined on the instance's image. It passes hosts that can support the specified image properties contained in the instance. Properties include the architecture, hypervisor type, hypervisor version (for Xen hypervisor type only), and virtual machine mode."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:483(para)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:522(para)
|
||||
msgid "For example, an instance might require a host that runs an ARM-based processor, and QEMU as the hypervisor. You can decorate an image with these properties by using:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:488(para)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:527(para)
|
||||
msgid "The image properties that the filter checks for are:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:491(para)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:530(para)
|
||||
msgid "<literal>architecture</literal>: describes the machine architecture required by the image. Examples are <literal>i686</literal>, <literal>x86_64</literal>, <literal>arm</literal>, and <literal>ppc64</literal>."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:498(para)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:537(para)
|
||||
msgid "<literal>hypervisor_type</literal>: describes the hypervisor required by the image. Examples are <literal>xen</literal>, <literal>qemu</literal>, and <literal>xenapi</literal>."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:502(para)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:541(para)
|
||||
msgid "<literal>qemu</literal> is used for both QEMU and KVM hypervisor types."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:506(para)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:545(para)
|
||||
msgid "<literal>hypervisor_version_requires</literal>: describes the hypervisor version required by the image. The property is supported for Xen hypervisor type only. It can be used to enable support for multiple hypervisor versions, and to prevent instances with newer Xen tools from being provisioned on an older version of a hypervisor. If available, the property value is compared to the hypervisor version of the compute host."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:515(para)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:554(para)
|
||||
msgid "To filter the hosts by the hypervisor version, add the <literal>hypervisor_version_requires</literal> property on the image as metadata and pass an operator and a required hypervisor version as its value:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:522(para)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:561(para)
|
||||
msgid "<literal>vm_mode</literal>: describes the hypervisor application binary interface (ABI) required by the image. Examples are <literal>xen</literal> for Xen 3.0 paravirtual ABI, <literal>hvm</literal> for native ABI, <literal>uml</literal> for User Mode Linux paravirtual ABI, <literal>exe</literal> for container virt executable ABI."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:533(title)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:572(title)
|
||||
msgid "IsolatedHostsFilter"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:534(para)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:573(para)
|
||||
msgid "Allows the admin to define a special (isolated) set of images and a special (isolated) set of hosts, such that the isolated images can only run on the isolated hosts, and the isolated hosts can only run isolated images. The flag <literal>restrict_isolated_hosts_to_isolated_images</literal> can be used to force isolated hosts to only run isolated images."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:542(para)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:581(para)
|
||||
msgid "The admin must specify the isolated set of images and hosts in the <filename>nova.conf</filename> file using the <literal>isolated_hosts</literal> and <literal>isolated_images</literal> configuration options. For example:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:551(title)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:590(title)
|
||||
msgid "IoOpsFilter"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:552(para)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:591(para)
|
||||
msgid "The IoOpsFilter filters hosts by concurrent I/O operations on it. Hosts with too many concurrent I/O operations will be filtered out. The <placeholder-1/> option specifies the maximum number of I/O intensive instances allowed to run on a host. A host will be ignored by the scheduler if more than <placeholder-2/> instances in build, resize, snapshot, migrate, rescue or unshelve task states are running on it."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:565(title)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:604(title)
|
||||
msgid "JsonFilter"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:570(para)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:609(para)
|
||||
msgid "="
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:573(para)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:612(para)
|
||||
msgid "<"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:576(para)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:615(para)
|
||||
msgid ">"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:579(para)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:618(para)
|
||||
msgid "in"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:582(para)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:621(para)
|
||||
msgid "<="
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:585(para)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:624(para)
|
||||
msgid ">="
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:588(para)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:627(para)
|
||||
msgid "not"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:591(para)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:630(para)
|
||||
msgid "or"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:594(para)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:633(para)
|
||||
msgid "and"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:598(code)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:637(code)
|
||||
msgid "$free_ram_mb"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:601(code)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:640(code)
|
||||
msgid "$free_disk_mb"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:604(code)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:643(code)
|
||||
msgid "$total_usable_ram_mb"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:607(code)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:646(code)
|
||||
msgid "$vcpus_total"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:610(code)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:649(code)
|
||||
msgid "$vcpus_used"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:566(para)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:605(para)
|
||||
msgid "The JsonFilter allows a user to construct a custom filter by passing a scheduler hint in JSON format. The following operators are supported:<placeholder-1/>The filter supports the following variables:<placeholder-2/>Using the <placeholder-3/> command-line tool, use the <literal>--hint</literal> flag:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:617(para) ./doc/config-reference/compute/section_compute-scheduler.xml:689(para) ./doc/config-reference/compute/section_compute-scheduler.xml:753(para)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:656(para) ./doc/config-reference/compute/section_compute-scheduler.xml:728(para) ./doc/config-reference/compute/section_compute-scheduler.xml:792(para)
|
||||
msgid "With the API, use the <literal>os:scheduler_hints</literal> key:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:622(title)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:661(title)
|
||||
msgid "MetricsFilter"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:623(para)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:662(para)
|
||||
msgid "Filters hosts based on metrics <literal>weight_setting</literal>. Only hosts with the available metrics are passed so that the metrics weigher will not fail due to these hosts."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:630(title)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:669(title)
|
||||
msgid "NumInstancesFilter"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:631(para)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:670(para)
|
||||
msgid "Hosts that have more instances running than specified by the <placeholder-1/> option are filtered out when this filter is in place."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:638(title)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:677(title)
|
||||
msgid "PciPassthroughFilter"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:639(para)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:678(para)
|
||||
msgid "The filter schedules instances on a host if the host has devices that meet the device requests in the <literal>extra_specs</literal> attribute for the flavor."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:646(title)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:685(title)
|
||||
msgid "RamFilter"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:647(para)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:686(para)
|
||||
msgid "Only schedules instances on hosts that have sufficient RAM available. If this filter is not set, the scheduler may over provision a host based on RAM (for example, the RAM allocated by virtual machine instances may exceed the physical RAM)."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:652(para)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:691(para)
|
||||
msgid "You can configure this filter to enable a fixed amount of RAM overcommitment by using the <literal>ram_allocation_ratio</literal> configuration option in <filename>nova.conf</filename>. The default setting is:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:659(para)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:698(para)
|
||||
msgid "This setting enables 1.5GB instances to run on any compute node with 1GB of free RAM."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:663(title)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:702(title)
|
||||
msgid "RetryFilter"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:664(para)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:703(para)
|
||||
msgid "Filters out hosts that have already been attempted for scheduling purposes. If the scheduler selects a host to respond to a service request, and the host fails to respond to the request, this filter prevents the scheduler from retrying that host for the service request."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:670(para)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:709(para)
|
||||
msgid "This filter is only useful if the <literal>scheduler_max_attempts</literal> configuration option is set to a value greater than zero."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:676(title)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:715(title)
|
||||
msgid "SameHostFilter"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:677(para)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:716(para)
|
||||
msgid "Schedules the instance on the same host as another instance in a set of instances. To take advantage of this filter, the requester must pass a scheduler hint, using <literal>same_host</literal> as the key and a list of instance UUIDs as the value. This filter is the opposite of the <literal>DifferentHostFilter</literal>. Using the <placeholder-1/> command-line tool, use the <literal>--hint</literal> flag:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:694(title)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:733(title)
|
||||
msgid "ServerGroupAffinityFilter"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:695(para)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:734(para)
|
||||
msgid "The ServerGroupAffinityFilter ensures that an instance is scheduled on to a host from a set of group hosts. To take advantage of this filter, the requester must create a server group with an <literal>affinity</literal> policy, and pass a scheduler hint, using <literal>group</literal> as the key and the server group UUID as the value. Using the <placeholder-1/> command-line tool, use the <literal>--hint</literal> flag. For example:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:706(replaceable) ./doc/config-reference/compute/section_compute-scheduler.xml:721(replaceable)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:745(replaceable) ./doc/config-reference/compute/section_compute-scheduler.xml:760(replaceable)
|
||||
msgid "SERVER_GROUP_UUID"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:709(title)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:748(title)
|
||||
msgid "ServerGroupAntiAffinityFilter"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:710(para)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:749(para)
|
||||
msgid "The ServerGroupAntiAffinityFilter ensures that each instance in a group is on a different host. To take advantage of this filter, the requester must create a server group with an <literal>anti-affinity</literal> policy, and pass a scheduler hint, using <literal>group</literal> as the key and the server group UUID as the value. Using the <placeholder-1/> command-line tool, use the <literal>--hint</literal> flag. For example:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:724(title)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:763(title)
|
||||
msgid "SimpleCIDRAffinityFilter"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:725(para)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:764(para)
|
||||
msgid "Schedules the instance based on host IP subnet range. To take advantage of this filter, the requester must specify a range of valid IP address in CIDR format, by passing two scheduler hints:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:731(literal)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:770(literal)
|
||||
msgid "build_near_host_ip"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:733(para)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:772(para)
|
||||
msgid "The first IP address in the subnet (for example, <literal>192.168.1.1</literal>)"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:739(literal)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:778(literal)
|
||||
msgid "cidr"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:741(para)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:780(para)
|
||||
msgid "The CIDR that corresponds to the subnet (for example, <literal>/24</literal>)"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:747(para)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:786(para)
|
||||
msgid "Using the <placeholder-1/> command-line tool, use the <literal>--hint</literal> flag. For example, to specify the IP subnet <literal>192.168.1.1/24</literal>"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:758(title)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:797(title)
|
||||
msgid "TrustedFilter"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:759(para)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:798(para)
|
||||
msgid "Filters hosts based on their trust. Only passes hosts that meet the trust requirements specified in the instance properties."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:766(title)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:805(title)
|
||||
msgid "TypeAffinityFilter"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:767(para)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:806(para)
|
||||
msgid "Dynamically limits hosts to one instance type. An instance can only be launched on a host, if no instance with different instances types are running on it, or if the host has no running instances at all."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:776(title)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:815(title)
|
||||
msgid "Weights"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:778(para)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:817(para)
|
||||
msgid "When resourcing instances, the filter scheduler filters and weights each host in the list of acceptable hosts. Each time the scheduler selects a host, it virtually consumes resources on it, and subsequent selections are adjusted accordingly. This process is useful when the customer asks for the same large amount of instances, because weight is computed for each requested instance."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:785(para)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:824(para)
|
||||
msgid "All weights are normalized before being summed up; the host with the largest weight is given the highest priority."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:789(title)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:828(title)
|
||||
msgid "Weighting hosts"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:798(para)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:837(para)
|
||||
msgid "If cells are used, cells are weighted by the scheduler in the same manner as hosts."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:800(para)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:839(para)
|
||||
msgid "Hosts and cells are weighted based on the following options in the <filename>/etc/nova/nova.conf</filename> file:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:804(caption)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:843(caption)
|
||||
msgid "Host weighting options"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:810(th) ./doc/config-reference/compute/section_compute-scheduler.xml:914(th)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:849(th) ./doc/config-reference/compute/section_compute-scheduler.xml:953(th)
|
||||
msgid "Section"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:818(literal) ./doc/config-reference/compute/section_compute-scheduler.xml:944(literal)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:857(literal) ./doc/config-reference/compute/section_compute-scheduler.xml:983(literal)
|
||||
msgid "ram_weight_multiplier"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:819(td)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:858(td)
|
||||
msgid "By default, the scheduler spreads instances across all hosts evenly. Set the <placeholder-1/> option to a negative number if you prefer stacking instead of spreading. Use a floating-point value."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:828(literal)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:867(literal)
|
||||
msgid "scheduler_host_subset_size"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:829(td)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:868(td)
|
||||
msgid "New instances are scheduled on a host that is chosen randomly from a subset of the N best hosts. This property defines the subset size from which a host is chosen. A value of 1 chooses the first host returned by the weighting functions. This value must be at least 1. A value less than 1 is ignored, and 1 is used instead. Use an integer value."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:840(literal) ./doc/config-reference/compute/section_compute-scheduler.xml:954(literal)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:879(literal) ./doc/config-reference/compute/section_compute-scheduler.xml:993(literal)
|
||||
msgid "scheduler_weight_classes"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:842(literal)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:881(literal)
|
||||
msgid "nova.scheduler.weights.all_weighers"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:841(td)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:880(td)
|
||||
msgid "Defaults to <placeholder-1/>, which selects the RamWeigher and MetricsWeigher. Hosts are then weighted and sorted with the largest weight winning."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:849(literal)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:888(literal)
|
||||
msgid "weight_multiplier"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:850(td)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:889(td)
|
||||
msgid "Multiplier for weighting metrics. Use a floating-point value."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:855(literal)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:894(literal)
|
||||
msgid "weight_setting"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:859(literal)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:898(literal)
|
||||
msgid "name1.value * 1.0 + name2.value * -1.0"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:856(td)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:895(td)
|
||||
msgid "Determines how metrics are weighted. Use a comma-separated list of metricName=ratio. For example: \"name1=1.0, name2=-1.0\" results in: <placeholder-1/>"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:865(literal)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:904(literal)
|
||||
msgid "required"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:868(para)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:907(para)
|
||||
msgid "TrueRaises an exception. To avoid the raised exception, you should use the scheduler filter MetricFilter to filter out hosts with unavailable metrics."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:877(para)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:916(para)
|
||||
msgid "FalseTreated as a negative factor in the weighting process (uses the option)."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:866(para)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:905(para)
|
||||
msgid "Specifies how to treat unavailable metrics:<placeholder-1/>"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:887(literal)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:926(literal)
|
||||
msgid "weight_of_unavailable"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:888(td)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:927(td)
|
||||
msgid "If <placeholder-1/> is set to False, and any one of the metrics set by <placeholder-2/> is unavailable, the <placeholder-3/> value is returned to the scheduler."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:897(para) ./doc/config-reference/compute/section_compute-scheduler.xml:963(para)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:936(para) ./doc/config-reference/compute/section_compute-scheduler.xml:1002(para)
|
||||
msgid "For example:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:908(caption)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:947(caption)
|
||||
msgid "Cell weighting options"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:922(literal)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:961(literal)
|
||||
msgid "mute_weight_multiplier"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:923(td)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:962(td)
|
||||
msgid "Multiplier to weight mute children (hosts which have not sent capacity or capacity updates for some time). Use a negative, floating-point value."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:930(literal)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:969(literal)
|
||||
msgid "mute_weight_value"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:931(td)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:970(td)
|
||||
msgid "Weight value assigned to mute children. Use a positive, floating-point value with a maximum of '1.0'."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:937(literal)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:976(literal)
|
||||
msgid "offset_weight_multiplier"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:938(td)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:977(td)
|
||||
msgid "Multiplier to weight cells, so you can specify a preferred cell. Use a floating point value."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:945(td)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:984(td)
|
||||
msgid "By default, the scheduler spreads instances across all cells evenly. Set the <placeholder-1/> option to a negative number if you prefer stacking instead of spreading. Use a floating-point value."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:956(literal)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:995(literal)
|
||||
msgid "nova.cells.weights.all_weighers"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:955(td)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:994(td)
|
||||
msgid "Defaults to <placeholder-1/>, which maps to all cell weighers included with Compute. Cells are then weighted and sorted with the largest weight winning."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:972(title)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:1011(title)
|
||||
msgid "Chance scheduler"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:974(para)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:1013(para)
|
||||
msgid "As an administrator, you work with the filter scheduler. However, the Compute service also uses the Chance Scheduler, <literal>nova.scheduler.chance.ChanceScheduler</literal>, which randomly selects from lists of filtered hosts."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:985(para)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:1024(para)
|
||||
msgid "To customize the Compute scheduler, use the configuration option settings documented in <xref linkend=\"config_table_nova_scheduler\"/>."
|
||||
msgstr ""
|
||||
|
||||
|
||||
@ -6,9 +6,9 @@
|
||||
msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: OpenStack Manuals\n"
|
||||
"POT-Creation-Date: 2015-03-18 08:46+0000\n"
|
||||
"PO-Revision-Date: 2015-03-18 08:45+0000\n"
|
||||
"Last-Translator: openstackjenkins <jenkins@openstack.org>\n"
|
||||
"POT-Creation-Date: 2015-03-26 05:48+0000\n"
|
||||
"PO-Revision-Date: 2015-03-26 03:30+0000\n"
|
||||
"Last-Translator: Tomoyuki KATO <tomo@dream.daynight.jp>\n"
|
||||
"Language-Team: Japanese (http://www.transifex.com/projects/p/openstack-manuals-i18n/language/ja/)\n"
|
||||
"MIME-Version: 1.0\n"
|
||||
"Content-Type: text/plain; charset=UTF-8\n"
|
||||
@ -3511,4 +3511,4 @@ msgstr "上の例では、ゲストの <literal>centos-6.4</literal> が VNC デ
|
||||
#. Put one translator per line, in the form of NAME <EMAIL>, YEAR1, YEAR2
|
||||
#: ./doc/image-guide/ch_creating_images_manually.xml0(None)
|
||||
msgid "translator-credits"
|
||||
msgstr "Tomoyuki KATO <tomo@dream.daynight.jp>, 2013-2014"
|
||||
msgstr "Tomoyuki KATO <tomo@dream.daynight.jp>, 2013-2015"
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: PACKAGE VERSION\n"
|
||||
"POT-Creation-Date: 2015-03-18 06:14+0000\n"
|
||||
"POT-Creation-Date: 2015-03-26 06:09+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"
|
||||
@ -211,11 +211,11 @@ msgstr ""
|
||||
msgid "Start the Identity service and configure it to start when the system boots:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/install-guide/section_keystone-install.xml:245(para) ./doc/install-guide/section_basics-database.xml:27(para) ./doc/install-guide/section_basics-database.xml:76(para) ./doc/install-guide/section_ceilometer-swift.xml:87(para) ./doc/install-guide/section_ceilometer-nova.xml:114(para) ./doc/install-guide/section_ceilometer-nova.xml:125(para) ./doc/install-guide/section_sahara-install.xml:97(para) ./doc/install-guide/section_ceilometer-cinder.xml:30(para) ./doc/install-guide/section_ceilometer-cinder.xml:40(para) ./doc/install-guide/section_cinder-storage-node.xml:264(para) ./doc/install-guide/section_cinder-controller-node.xml:220(para) ./doc/install-guide/section_basics-ntp.xml:60(para) ./doc/install-guide/section_basics-ntp.xml:102(para) ./doc/install-guide/section_nova-controller-install.xml:266(para) ./doc/install-guide/section_nova-networking-compute-node.xml:63(para) ./doc/install-guide/section_glance-install.xml:294(para) ./doc/install-guide/section_dashboard-install.xml:133(para) ./doc/install-guide/section_neutron-compute-node.xml:215(para) ./doc/install-guide/section_neutron-compute-node.xml:304(para) ./doc/install-guide/section_neutron-compute-node.xml:315(para) ./doc/install-guide/section_neutron-controller-node.xml:393(para) ./doc/install-guide/section_neutron-controller-node.xml:409(para) ./doc/install-guide/section_neutron-network-node.xml:434(para) ./doc/install-guide/section_neutron-network-node.xml:457(para) ./doc/install-guide/section_neutron-network-node.xml:533(para) ./doc/install-guide/section_trove-install.xml:236(para) ./doc/install-guide/section_nova-networking-controller-node.xml:31(para) ./doc/install-guide/section_nova-compute-install.xml:215(para) ./doc/install-guide/section_heat-install.xml:288(para) ./doc/install-guide/section_ceilometer-glance.xml:33(para) ./doc/install-guide/section_basics-queue.xml:49(para) ./doc/install-guide/section_basics-queue.xml:109(para) ./doc/install-guide/section_ceilometer-controller.xml:26(para) ./doc/install-guide/section_ceilometer-controller.xml:78(para) ./doc/install-guide/section_ceilometer-controller.xml:375(para) ./doc/install-guide/object-storage/section_swift-finalize-installation.xml:68(para) ./doc/install-guide/object-storage/section_swift-finalize-installation.xml:106(para) ./doc/install-guide/object-storage/section_swift-storage-node.xml:169(para)
|
||||
#: ./doc/install-guide/section_keystone-install.xml:245(para) ./doc/install-guide/section_basics-database.xml:27(para) ./doc/install-guide/section_basics-database.xml:76(para) ./doc/install-guide/section_ceilometer-swift.xml:87(para) ./doc/install-guide/section_ceilometer-nova.xml:114(para) ./doc/install-guide/section_ceilometer-nova.xml:125(para) ./doc/install-guide/section_sahara-install.xml:97(para) ./doc/install-guide/section_ceilometer-cinder.xml:30(para) ./doc/install-guide/section_ceilometer-cinder.xml:40(para) ./doc/install-guide/section_cinder-storage-node.xml:264(para) ./doc/install-guide/section_cinder-controller-node.xml:220(para) ./doc/install-guide/section_basics-ntp.xml:60(para) ./doc/install-guide/section_basics-ntp.xml:102(para) ./doc/install-guide/section_nova-controller-install.xml:266(para) ./doc/install-guide/section_nova-networking-compute-node.xml:63(para) ./doc/install-guide/section_glance-install.xml:294(para) ./doc/install-guide/section_dashboard-install.xml:133(para) ./doc/install-guide/section_neutron-compute-node.xml:215(para) ./doc/install-guide/section_neutron-compute-node.xml:304(para) ./doc/install-guide/section_neutron-compute-node.xml:315(para) ./doc/install-guide/section_neutron-controller-node.xml:393(para) ./doc/install-guide/section_neutron-controller-node.xml:409(para) ./doc/install-guide/section_neutron-network-node.xml:434(para) ./doc/install-guide/section_neutron-network-node.xml:457(para) ./doc/install-guide/section_neutron-network-node.xml:533(para) ./doc/install-guide/section_trove-install.xml:236(para) ./doc/install-guide/section_nova-networking-controller-node.xml:31(para) ./doc/install-guide/section_nova-compute-install.xml:215(para) ./doc/install-guide/section_heat-install.xml:288(para) ./doc/install-guide/section_ceilometer-glance.xml:33(para) ./doc/install-guide/section_basics-queue.xml:64(para) ./doc/install-guide/section_ceilometer-controller.xml:26(para) ./doc/install-guide/section_ceilometer-controller.xml:78(para) ./doc/install-guide/section_ceilometer-controller.xml:375(para) ./doc/install-guide/object-storage/section_swift-finalize-installation.xml:68(para) ./doc/install-guide/object-storage/section_swift-finalize-installation.xml:106(para) ./doc/install-guide/object-storage/section_swift-storage-node.xml:169(para)
|
||||
msgid "On SLES:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/install-guide/section_keystone-install.xml:248(para) ./doc/install-guide/section_basics-database.xml:25(para) ./doc/install-guide/section_basics-database.xml:79(para) ./doc/install-guide/section_ceilometer-swift.xml:89(para) ./doc/install-guide/section_ceilometer-nova.xml:117(para) ./doc/install-guide/section_ceilometer-nova.xml:127(para) ./doc/install-guide/section_sahara-install.xml:99(para) ./doc/install-guide/section_ceilometer-cinder.xml:33(para) ./doc/install-guide/section_ceilometer-cinder.xml:42(para) ./doc/install-guide/section_cinder-storage-node.xml:269(para) ./doc/install-guide/section_cinder-controller-node.xml:225(para) ./doc/install-guide/section_basics-ntp.xml:63(para) ./doc/install-guide/section_basics-ntp.xml:105(para) ./doc/install-guide/section_nova-controller-install.xml:279(para) ./doc/install-guide/section_nova-networking-compute-node.xml:68(para) ./doc/install-guide/section_glance-install.xml:299(para) ./doc/install-guide/section_dashboard-install.xml:138(para) ./doc/install-guide/section_neutron-compute-node.xml:218(para) ./doc/install-guide/section_neutron-compute-node.xml:306(para) ./doc/install-guide/section_neutron-compute-node.xml:318(para) ./doc/install-guide/section_neutron-controller-node.xml:397(para) ./doc/install-guide/section_neutron-controller-node.xml:412(para) ./doc/install-guide/section_neutron-network-node.xml:436(para) ./doc/install-guide/section_neutron-network-node.xml:460(para) ./doc/install-guide/section_neutron-network-node.xml:543(para) ./doc/install-guide/section_trove-install.xml:243(para) ./doc/install-guide/section_nova-networking-controller-node.xml:35(para) ./doc/install-guide/section_nova-compute-install.xml:220(para) ./doc/install-guide/section_heat-install.xml:295(para) ./doc/install-guide/section_ceilometer-glance.xml:36(para) ./doc/install-guide/section_basics-queue.xml:52(para) ./doc/install-guide/section_basics-queue.xml:111(para) ./doc/install-guide/section_ceilometer-controller.xml:24(para) ./doc/install-guide/section_ceilometer-controller.xml:81(para) ./doc/install-guide/section_ceilometer-controller.xml:388(para) ./doc/install-guide/object-storage/section_swift-finalize-installation.xml:73(para) ./doc/install-guide/object-storage/section_swift-finalize-installation.xml:119(para) ./doc/install-guide/object-storage/section_swift-storage-node.xml:172(para)
|
||||
#: ./doc/install-guide/section_keystone-install.xml:248(para) ./doc/install-guide/section_basics-database.xml:25(para) ./doc/install-guide/section_basics-database.xml:79(para) ./doc/install-guide/section_ceilometer-swift.xml:89(para) ./doc/install-guide/section_ceilometer-nova.xml:117(para) ./doc/install-guide/section_ceilometer-nova.xml:127(para) ./doc/install-guide/section_sahara-install.xml:99(para) ./doc/install-guide/section_ceilometer-cinder.xml:33(para) ./doc/install-guide/section_ceilometer-cinder.xml:42(para) ./doc/install-guide/section_cinder-storage-node.xml:269(para) ./doc/install-guide/section_cinder-controller-node.xml:225(para) ./doc/install-guide/section_basics-ntp.xml:63(para) ./doc/install-guide/section_basics-ntp.xml:105(para) ./doc/install-guide/section_nova-controller-install.xml:279(para) ./doc/install-guide/section_nova-networking-compute-node.xml:68(para) ./doc/install-guide/section_glance-install.xml:299(para) ./doc/install-guide/section_dashboard-install.xml:138(para) ./doc/install-guide/section_neutron-compute-node.xml:218(para) ./doc/install-guide/section_neutron-compute-node.xml:306(para) ./doc/install-guide/section_neutron-compute-node.xml:318(para) ./doc/install-guide/section_neutron-controller-node.xml:397(para) ./doc/install-guide/section_neutron-controller-node.xml:412(para) ./doc/install-guide/section_neutron-network-node.xml:436(para) ./doc/install-guide/section_neutron-network-node.xml:460(para) ./doc/install-guide/section_neutron-network-node.xml:543(para) ./doc/install-guide/section_trove-install.xml:243(para) ./doc/install-guide/section_nova-networking-controller-node.xml:35(para) ./doc/install-guide/section_nova-compute-install.xml:220(para) ./doc/install-guide/section_heat-install.xml:295(para) ./doc/install-guide/section_ceilometer-glance.xml:36(para) ./doc/install-guide/section_basics-queue.xml:67(para) ./doc/install-guide/section_ceilometer-controller.xml:24(para) ./doc/install-guide/section_ceilometer-controller.xml:81(para) ./doc/install-guide/section_ceilometer-controller.xml:388(para) ./doc/install-guide/object-storage/section_swift-finalize-installation.xml:73(para) ./doc/install-guide/object-storage/section_swift-finalize-installation.xml:119(para) ./doc/install-guide/object-storage/section_swift-storage-node.xml:172(para)
|
||||
msgid "On openSUSE:"
|
||||
msgstr ""
|
||||
|
||||
@ -471,7 +471,7 @@ msgstr ""
|
||||
msgid "In the <literal>[filter:ceilometer]</literal> section, configure notifications:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/install-guide/section_ceilometer-swift.xml:67(replaceable) ./doc/install-guide/section_ceilometer-nova.xml:38(replaceable) ./doc/install-guide/section_cinder-storage-node.xml:158(replaceable) ./doc/install-guide/section_cinder-controller-node.xml:138(replaceable) ./doc/install-guide/section_nova-controller-install.xml:145(replaceable) ./doc/install-guide/section_neutron-compute-node.xml:94(replaceable) ./doc/install-guide/section_neutron-controller-node.xml:181(replaceable) ./doc/install-guide/section_neutron-network-node.xml:98(replaceable) ./doc/install-guide/section_trove-install.xml:104(replaceable) ./doc/install-guide/section_trove-install.xml:180(replaceable) ./doc/install-guide/section_nova-compute-install.xml:58(replaceable) ./doc/install-guide/section_heat-install.xml:191(replaceable) ./doc/install-guide/section_ceilometer-glance.xml:23(replaceable) ./doc/install-guide/section_basics-queue.xml:64(replaceable) ./doc/install-guide/section_ceilometer-controller.xml:232(replaceable)
|
||||
#: ./doc/install-guide/section_ceilometer-swift.xml:67(replaceable) ./doc/install-guide/section_ceilometer-nova.xml:38(replaceable) ./doc/install-guide/section_cinder-storage-node.xml:158(replaceable) ./doc/install-guide/section_cinder-controller-node.xml:138(replaceable) ./doc/install-guide/section_nova-controller-install.xml:145(replaceable) ./doc/install-guide/section_neutron-compute-node.xml:94(replaceable) ./doc/install-guide/section_neutron-controller-node.xml:181(replaceable) ./doc/install-guide/section_neutron-network-node.xml:98(replaceable) ./doc/install-guide/section_trove-install.xml:104(replaceable) ./doc/install-guide/section_trove-install.xml:180(replaceable) ./doc/install-guide/section_nova-compute-install.xml:58(replaceable) ./doc/install-guide/section_heat-install.xml:191(replaceable) ./doc/install-guide/section_ceilometer-glance.xml:23(replaceable) ./doc/install-guide/section_basics-queue.xml:73(replaceable) ./doc/install-guide/section_ceilometer-controller.xml:232(replaceable)
|
||||
msgid "RABBIT_PASS"
|
||||
msgstr ""
|
||||
|
||||
@ -4284,11 +4284,11 @@ msgid "Updated cover and fixed small errors in appendix."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/install-guide/section_basics-queue.xml:8(title)
|
||||
msgid "Messaging server"
|
||||
msgid "Message queue"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/install-guide/section_basics-queue.xml:9(para)
|
||||
msgid "OpenStack uses a <glossterm>message broker</glossterm> to coordinate operations and status information among services. The message broker service typically runs on the controller node. OpenStack supports several message brokers including <application>RabbitMQ</application>, <application>Qpid</application>, and <application>ZeroMQ</application>. However, most distributions that package OpenStack support a particular message broker. This guide covers the RabbitMQ message broker which is supported by each distribution. If you prefer to implement a different message broker, consult the documentation associated with it."
|
||||
msgid "OpenStack uses a <glossterm>message queue</glossterm> to coordinate operations and status information among services. The message queue service typically runs on the controller node. OpenStack supports several message queue services including <application>RabbitMQ</application>, <application>Qpid</application>, and <application>ZeroMQ</application>. However, most distributions that package OpenStack support a particular message queue service. This guide implements the RabbitMQ message queue service because most distributions support it. If you prefer to implement a different message queue service, consult the documentation associated with it."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/install-guide/section_basics-queue.xml:21(link)
|
||||
@ -4304,59 +4304,43 @@ msgid "ZeroMQ"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/install-guide/section_basics-queue.xml:31(title)
|
||||
msgid "To install the <application>RabbitMQ</application> message broker service"
|
||||
msgid "To install the message queue service"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/install-guide/section_basics-queue.xml:43(title)
|
||||
msgid "To configure the message broker service"
|
||||
#: ./doc/install-guide/section_basics-queue.xml:33(para)
|
||||
msgid "Add the upstream repository key:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/install-guide/section_basics-queue.xml:45(para)
|
||||
msgid "Start the message broker service and configure it to start when the system boots:"
|
||||
#: ./doc/install-guide/section_basics-queue.xml:38(para)
|
||||
msgid "Add the upstream repository:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/install-guide/section_basics-queue.xml:57(para)
|
||||
msgid "The message broker creates a default account that uses <literal>guest</literal> for the username and password. To simplify installation of your test environment, we recommend that you use this account, but change the password for it."
|
||||
#: ./doc/install-guide/section_basics-queue.xml:43(para)
|
||||
msgid "Update the package database:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/install-guide/section_basics-queue.xml:61(para)
|
||||
msgid "Run the following command:"
|
||||
#: ./doc/install-guide/section_basics-queue.xml:47(para)
|
||||
msgid "Install the package:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/install-guide/section_basics-queue.xml:62(para)
|
||||
#: ./doc/install-guide/section_basics-queue.xml:58(title)
|
||||
msgid "To configure the message queue service"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/install-guide/section_basics-queue.xml:60(para)
|
||||
msgid "Start the message queue service and configure it to start when the system boots:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/install-guide/section_basics-queue.xml:72(para)
|
||||
msgid "Add the <literal>openstack</literal> user:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/install-guide/section_basics-queue.xml:75(para)
|
||||
msgid "Replace <replaceable>RABBIT_PASS</replaceable> with a suitable password."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/install-guide/section_basics-queue.xml:67(para)
|
||||
msgid "You must configure the <literal>rabbit_password</literal> key in the configuration file for each OpenStack service that uses the message broker."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/install-guide/section_basics-queue.xml:71(para)
|
||||
msgid "For production environments, you should create a unique account with a suitable password. For more information on securing the message broker, see the <link href=\"https://www.rabbitmq.com/man/rabbitmqctl.1.man.html\">documentation</link>."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/install-guide/section_basics-queue.xml:76(para)
|
||||
msgid "If you decide to create a unique account with a suitable password for your test environment, you must configure the <literal>rabbit_userid</literal> and <literal>rabbit_password</literal> keys in the configuration file of each OpenStack service that uses the message broker."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/install-guide/section_basics-queue.xml:84(para)
|
||||
msgid "For RabbitMQ version 3.3.0 or newer, you must enable remote access for the <literal>guest</literal> account."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/install-guide/section_basics-queue.xml:88(para)
|
||||
msgid "Check the RabbitMQ version:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/install-guide/section_basics-queue.xml:94(para)
|
||||
msgid "If necessary, edit the <filename>/etc/rabbitmq/rabbitmq.config</filename> file and configure <literal>loopback_users</literal> to reference an empty list:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/install-guide/section_basics-queue.xml:100(para)
|
||||
msgid "Contents of the original file might vary depending on the source of the RabbitMQ package. In some cases, you might need to create this file."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/install-guide/section_basics-queue.xml:106(para)
|
||||
msgid "Restart the message broker service:"
|
||||
#: ./doc/install-guide/section_basics-queue.xml:79(para)
|
||||
msgid "Permit configuration, write, and read access for the <literal>openstack</literal> user:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/install-guide/section_ceilometer-controller.xml:12(para)
|
||||
|
||||
@ -5,9 +5,9 @@
|
||||
msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: OpenStack Manuals\n"
|
||||
"POT-Creation-Date: 2015-03-25 04:19+0000\n"
|
||||
"PO-Revision-Date: 2015-03-25 04:01+0000\n"
|
||||
"Last-Translator: Tomoyuki KATO <tomo@dream.daynight.jp>\n"
|
||||
"POT-Creation-Date: 2015-03-26 05:48+0000\n"
|
||||
"PO-Revision-Date: 2015-03-26 06:01+0000\n"
|
||||
"Last-Translator: openstackjenkins <jenkins@openstack.org>\n"
|
||||
"Language-Team: Japanese (http://www.transifex.com/projects/p/openstack-manuals-i18n/language/ja/)\n"
|
||||
"MIME-Version: 1.0\n"
|
||||
"Content-Type: text/plain; charset=UTF-8\n"
|
||||
@ -527,8 +527,7 @@ msgstr "Identity のサービスを起動し、システム起動時に起動す
|
||||
#: ./doc/install-guide/section_nova-compute-install.xml215(para)
|
||||
#: ./doc/install-guide/section_heat-install.xml288(para)
|
||||
#: ./doc/install-guide/section_ceilometer-glance.xml33(para)
|
||||
#: ./doc/install-guide/section_basics-queue.xml49(para)
|
||||
#: ./doc/install-guide/section_basics-queue.xml109(para)
|
||||
#: ./doc/install-guide/section_basics-queue.xml64(para)
|
||||
#: ./doc/install-guide/section_ceilometer-controller.xml26(para)
|
||||
#: ./doc/install-guide/section_ceilometer-controller.xml78(para)
|
||||
#: ./doc/install-guide/section_ceilometer-controller.xml375(para)
|
||||
@ -568,8 +567,7 @@ msgstr "SLES の場合:"
|
||||
#: ./doc/install-guide/section_nova-compute-install.xml220(para)
|
||||
#: ./doc/install-guide/section_heat-install.xml295(para)
|
||||
#: ./doc/install-guide/section_ceilometer-glance.xml36(para)
|
||||
#: ./doc/install-guide/section_basics-queue.xml52(para)
|
||||
#: ./doc/install-guide/section_basics-queue.xml111(para)
|
||||
#: ./doc/install-guide/section_basics-queue.xml67(para)
|
||||
#: ./doc/install-guide/section_ceilometer-controller.xml24(para)
|
||||
#: ./doc/install-guide/section_ceilometer-controller.xml81(para)
|
||||
#: ./doc/install-guide/section_ceilometer-controller.xml388(para)
|
||||
@ -1015,7 +1013,7 @@ msgstr "<literal>[filter:ceilometer]</literal> セクションに、通知を設
|
||||
#: ./doc/install-guide/section_nova-compute-install.xml58(replaceable)
|
||||
#: ./doc/install-guide/section_heat-install.xml191(replaceable)
|
||||
#: ./doc/install-guide/section_ceilometer-glance.xml23(replaceable)
|
||||
#: ./doc/install-guide/section_basics-queue.xml64(replaceable)
|
||||
#: ./doc/install-guide/section_basics-queue.xml73(replaceable)
|
||||
#: ./doc/install-guide/section_ceilometer-controller.xml232(replaceable)
|
||||
msgid "RABBIT_PASS"
|
||||
msgstr "RABBIT_PASS"
|
||||
@ -4926,7 +4924,7 @@ msgstr ""
|
||||
msgid ""
|
||||
"Edit the <filename>/etc/nova/nova.conf</filename> file on the controller "
|
||||
"node and complete the following actions:"
|
||||
msgstr ""
|
||||
msgstr "コントローラーノードで <filename>/etc/nova/nova.conf</filename> ファイルを編集し、以下の作業を実行します。"
|
||||
|
||||
#: ./doc/install-guide/section_neutron-controller-node.xml380(para)
|
||||
msgid "Populate the database:"
|
||||
@ -4936,7 +4934,7 @@ msgstr "データベースにデータを登録します。"
|
||||
msgid ""
|
||||
"Database population occurs later for Networking because the script requires "
|
||||
"complete server and plug-in configuration files."
|
||||
msgstr ""
|
||||
msgstr "データベースへのデータ登録は、スクリプトが設定済みのサーバーとプラグインの設定ファイルを前提としているため、Networking の設定後に行います。"
|
||||
|
||||
#: ./doc/install-guide/section_neutron-controller-node.xml405(para)
|
||||
msgid ""
|
||||
@ -4973,13 +4971,13 @@ msgstr "コントローラーノードにおいて、これらの手順を実行
|
||||
|
||||
#: ./doc/install-guide/section_ceilometer-verify.xml20(para)
|
||||
msgid "List available meters:"
|
||||
msgstr ""
|
||||
msgstr "利用可能な測定項目を一覧表示します。"
|
||||
|
||||
#: ./doc/install-guide/section_ceilometer-verify.xml29(para)
|
||||
msgid ""
|
||||
"Some meters might not appear until after you successfully launch at least "
|
||||
"one instance."
|
||||
msgstr ""
|
||||
msgstr "いくつかの測定項目は、少なくとも 1 つのインスタンスが正常に起動するまで表示されないかもしれません。"
|
||||
|
||||
#: ./doc/install-guide/section_ceilometer-verify.xml34(para)
|
||||
msgid "Download an image from the Image Service:"
|
||||
@ -4988,7 +4986,7 @@ msgstr "Image Service からイメージをダウンロードします。"
|
||||
#: ./doc/install-guide/section_ceilometer-verify.xml38(para)
|
||||
msgid ""
|
||||
"List available meters again to validate detection of the image download:"
|
||||
msgstr ""
|
||||
msgstr "再び利用可能な測定項目を一覧表示し、イメージのダウンロードを検知できるかどうかを検証します。"
|
||||
|
||||
#: ./doc/install-guide/section_ceilometer-verify.xml51(para)
|
||||
msgid ""
|
||||
@ -5030,7 +5028,7 @@ msgid ""
|
||||
"In the <literal>[ovs]</literal> section, enable tunnels, configure the local"
|
||||
" tunnel endpoint, and map the external flat provider network to the <literal"
|
||||
">br-ex</literal> external network bridge:"
|
||||
msgstr ""
|
||||
msgstr "<literal>[ovs]</literal> セクションにおいて、トンネルを有効化し、ローカルトンネルエンドポイントを設定し、外部フラットネットワークプロバイダーを <literal>br-ex</literal> 外部ネットワークブリッジに対応づけます。"
|
||||
|
||||
#: ./doc/install-guide/section_neutron-network-node.xml208(para)
|
||||
msgid ""
|
||||
@ -5336,7 +5334,7 @@ msgid ""
|
||||
"<literal>demo</literal> tenants and users. Future portions of this guide "
|
||||
"reference these scripts to load appropriate credentials for client "
|
||||
"operations."
|
||||
msgstr ""
|
||||
msgstr "<literal>admin</literal> および <literal>demo</literal> のテナントとユーザーのクライアント環境スクリプトを作成します。このガイドの以降は、これらのスクリプトを参照して、クライアント操作に適切なクレデンシャルを読み込みます。"
|
||||
|
||||
#: ./doc/install-guide/section_keystone-openrc.xml22(para)
|
||||
msgid ""
|
||||
@ -5371,11 +5369,11 @@ msgid ""
|
||||
"Note the two different ports used above. Port 35357 is used for "
|
||||
"administrative functions only. Port 5000 is for normal user functions and is"
|
||||
" the most commonly used."
|
||||
msgstr ""
|
||||
msgstr "ここで 2 つのポートが使用されていることに注意してください。ポート 35357 番は管理機能のためだけに使用されます。ポート 5000 番は通常のユーザー機能のために使用され、最も一般的に使用されます。"
|
||||
|
||||
#: ./doc/install-guide/section_keystone-openrc.xml47(title)
|
||||
msgid "To load client environment scripts"
|
||||
msgstr ""
|
||||
msgstr "クライアント環境スクリプトの読み込み方法"
|
||||
|
||||
#: ./doc/install-guide/section_keystone-openrc.xml49(para)
|
||||
msgid ""
|
||||
@ -5383,7 +5381,7 @@ msgid ""
|
||||
"associated client environment script prior to running them. For example, to "
|
||||
"load the location of the Identity service and <literal>admin</literal> "
|
||||
"tenant and user credentials:"
|
||||
msgstr ""
|
||||
msgstr "特定のテナントとユーザーとしてクライアントを実行する場合、実行する前に関連するクライアント環境スクリプトを単に読み込むことができます。例えば、Identity の位置および <literal>admin</literal> テナントとユーザーのクレデンシャルを読み込みます。"
|
||||
|
||||
#: ./doc/install-guide/section_sahara-verify.xml7(title)
|
||||
msgid "Verify the Data processing service installation"
|
||||
@ -5566,7 +5564,7 @@ msgstr "trove-conductor.conf"
|
||||
msgid ""
|
||||
"You need to take upstream <filename>api-paste.ini</filename> and change "
|
||||
"content below in it:"
|
||||
msgstr ""
|
||||
msgstr "アップストリームの <filename>api-paste.ini</filename> を取得し、以下の内容を変更する必要があります。"
|
||||
|
||||
#: ./doc/install-guide/section_trove-install.xml82(para)
|
||||
msgid ""
|
||||
@ -5574,7 +5572,7 @@ msgid ""
|
||||
">api-paste.ini</filename>) and set appropriate values for the OpenStack "
|
||||
"service URLs (can be handled by Keystone service catalog), logging and "
|
||||
"messaging configuration, and SQL connections:"
|
||||
msgstr ""
|
||||
msgstr "各ファイル (<filename>api-paste.ini</filename> を除く) の <literal>[DEFAULT]</literal> セクションを編集し、OpenStack のサービスの URL (Keystone のサービスカタログにより取り扱われるもの)、ログ設定、メッセージングの設定、SQL 接続の項目に適切な値を設定します。"
|
||||
|
||||
#: ./doc/install-guide/section_trove-install.xml92(literal)
|
||||
#: ./doc/install-guide/section_trove-install.xml145(replaceable)
|
||||
@ -5587,7 +5585,7 @@ msgid ""
|
||||
"Configure the Database module to use the RabbitMQ message broker by setting "
|
||||
"the following options in the <literal>[DEFAULT]</literal> configuration "
|
||||
"group of each file:"
|
||||
msgstr ""
|
||||
msgstr "各ファイルの <literal>[DEFAULT]</literal> 設定グループに以下のオプションを設定することにより、Database モジュールを設定して、RabbitMQ メッセージブローカーを使用します。"
|
||||
|
||||
#: ./doc/install-guide/section_trove-install.xml103(replaceable)
|
||||
msgid "guest"
|
||||
@ -5751,7 +5749,7 @@ msgstr ""
|
||||
msgid ""
|
||||
"This chapter omits the backup manager because it depends on the Object "
|
||||
"Storage service."
|
||||
msgstr ""
|
||||
msgstr "バックアップマネージャーは Object Storage に依存するため、この章では省略します。"
|
||||
|
||||
#: ./doc/install-guide/ch_cinder.xml29(para)
|
||||
msgid ""
|
||||
@ -6938,21 +6936,22 @@ msgid "Updated cover and fixed small errors in appendix."
|
||||
msgstr "表紙の更新と付録の小さなミスの修正。"
|
||||
|
||||
#: ./doc/install-guide/section_basics-queue.xml8(title)
|
||||
msgid "Messaging server"
|
||||
msgstr "メッセージングサーバー"
|
||||
msgid "Message queue"
|
||||
msgstr "メッセージキュー"
|
||||
|
||||
#: ./doc/install-guide/section_basics-queue.xml9(para)
|
||||
msgid ""
|
||||
"OpenStack uses a <glossterm>message broker</glossterm> to coordinate "
|
||||
"operations and status information among services. The message broker service"
|
||||
"OpenStack uses a <glossterm>message queue</glossterm> to coordinate "
|
||||
"operations and status information among services. The message queue service "
|
||||
"typically runs on the controller node. OpenStack supports several message "
|
||||
"brokers including <application>RabbitMQ</application>, "
|
||||
"queue services including <application>RabbitMQ</application>, "
|
||||
"<application>Qpid</application>, and <application>ZeroMQ</application>. "
|
||||
"However, most distributions that package OpenStack support a particular "
|
||||
"message broker. This guide covers the RabbitMQ message broker which is "
|
||||
"supported by each distribution. If you prefer to implement a different "
|
||||
"message broker, consult the documentation associated with it."
|
||||
msgstr "OpenStack は、サービス間の操作と状態を調整するために、<glossterm baseform=\"message broker\">メッセージブローカー</glossterm>を使用します。メッセージブローカーサービスは、一般的にコントローラーノードで動作します。OpenStack は、<application>RabbitMQ</application>、<application>Qpid</application>、<application>ZeroMQ</application> などのメッセージブローカーをサポートします。しかしながら、OpenStack をパッケージ化している多くのディストリビューションは、特定のメッセージブローカーをサポートします。このガイドは、各ディストリビューションによりサポートされる RabbitMQ メッセージブローカーを取り扱います。別のメッセージブローカーを導入したければ、関連ドキュメントを確認してください。"
|
||||
"message queue service. This guide implements the RabbitMQ message queue "
|
||||
"service because most distributions support it. If you prefer to implement a "
|
||||
"different message queue service, consult the documentation associated with "
|
||||
"it."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/install-guide/section_basics-queue.xml21(link)
|
||||
msgid "RabbitMQ"
|
||||
@ -6967,86 +6966,50 @@ msgid "ZeroMQ"
|
||||
msgstr "ZeroMQ"
|
||||
|
||||
#: ./doc/install-guide/section_basics-queue.xml31(title)
|
||||
msgid ""
|
||||
"To install the <application>RabbitMQ</application> message broker service"
|
||||
msgstr "<application>RabbitMQ</application> メッセージブローカーサービスのインストール方法"
|
||||
msgid "To install the message queue service"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/install-guide/section_basics-queue.xml43(title)
|
||||
msgid "To configure the message broker service"
|
||||
msgstr "メッセージブローカーサービスの設定方法"
|
||||
#: ./doc/install-guide/section_basics-queue.xml33(para)
|
||||
msgid "Add the upstream repository key:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/install-guide/section_basics-queue.xml45(para)
|
||||
#: ./doc/install-guide/section_basics-queue.xml38(para)
|
||||
msgid "Add the upstream repository:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/install-guide/section_basics-queue.xml43(para)
|
||||
msgid "Update the package database:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/install-guide/section_basics-queue.xml47(para)
|
||||
msgid "Install the package:"
|
||||
msgstr "パッケージをインストールします。"
|
||||
|
||||
#: ./doc/install-guide/section_basics-queue.xml58(title)
|
||||
msgid "To configure the message queue service"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/install-guide/section_basics-queue.xml60(para)
|
||||
msgid ""
|
||||
"Start the message broker service and configure it to start when the system "
|
||||
"Start the message queue service and configure it to start when the system "
|
||||
"boots:"
|
||||
msgstr "メッセージブローカーサービスを起動し、システム起動時に起動するよう設定します。"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/install-guide/section_basics-queue.xml57(para)
|
||||
msgid ""
|
||||
"The message broker creates a default account that uses "
|
||||
"<literal>guest</literal> for the username and password. To simplify "
|
||||
"installation of your test environment, we recommend that you use this "
|
||||
"account, but change the password for it."
|
||||
msgstr "メッセージブローカーは、ユーザー名とパスワードに <literal>guest</literal> を使用するデフォルトアカウントを作成します。テスト環境のインストールを簡単にするために、このアカウントを使用し、そのパスワードを変更しないことを推奨します。"
|
||||
#: ./doc/install-guide/section_basics-queue.xml72(para)
|
||||
msgid "Add the <literal>openstack</literal> user:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/install-guide/section_basics-queue.xml61(para)
|
||||
msgid "Run the following command:"
|
||||
msgstr "以下のコマンドを実行します。"
|
||||
|
||||
#: ./doc/install-guide/section_basics-queue.xml62(para)
|
||||
#: ./doc/install-guide/section_basics-queue.xml75(para)
|
||||
msgid ""
|
||||
"Replace <replaceable>RABBIT_PASS</replaceable> with a suitable password."
|
||||
msgstr "<replaceable>RABBIT_PASS</replaceable> を適切なパスワードに置き換えます。"
|
||||
|
||||
#: ./doc/install-guide/section_basics-queue.xml67(para)
|
||||
#: ./doc/install-guide/section_basics-queue.xml79(para)
|
||||
msgid ""
|
||||
"You must configure the <literal>rabbit_password</literal> key in the "
|
||||
"configuration file for each OpenStack service that uses the message broker."
|
||||
msgstr "メッセージブローカーを使用する各 OpenStack サービスの設定ファイルで <literal>rabbit_password</literal> キーを設定する必要があります。"
|
||||
|
||||
#: ./doc/install-guide/section_basics-queue.xml71(para)
|
||||
msgid ""
|
||||
"For production environments, you should create a unique account with a "
|
||||
"suitable password. For more information on securing the message broker, see "
|
||||
"the <link "
|
||||
"href=\"https://www.rabbitmq.com/man/rabbitmqctl.1.man.html\">documentation</link>."
|
||||
"Permit configuration, write, and read access for the "
|
||||
"<literal>openstack</literal> user:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/install-guide/section_basics-queue.xml76(para)
|
||||
msgid ""
|
||||
"If you decide to create a unique account with a suitable password for your "
|
||||
"test environment, you must configure the <literal>rabbit_userid</literal> "
|
||||
"and <literal>rabbit_password</literal> keys in the configuration file of "
|
||||
"each OpenStack service that uses the message broker."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/install-guide/section_basics-queue.xml84(para)
|
||||
msgid ""
|
||||
"For RabbitMQ version 3.3.0 or newer, you must enable remote access for the "
|
||||
"<literal>guest</literal> account."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/install-guide/section_basics-queue.xml88(para)
|
||||
msgid "Check the RabbitMQ version:"
|
||||
msgstr "RabbitMQ のバージョンを確認します。"
|
||||
|
||||
#: ./doc/install-guide/section_basics-queue.xml94(para)
|
||||
msgid ""
|
||||
"If necessary, edit the <filename>/etc/rabbitmq/rabbitmq.config</filename> "
|
||||
"file and configure <literal>loopback_users</literal> to reference an empty "
|
||||
"list:"
|
||||
msgstr "必要に応じて、<filename>/etc/rabbitmq/rabbitmq.config</filename> ファイルを編集して、<literal>loopback_users</literal> が空の一覧を参照するよう設定します。"
|
||||
|
||||
#: ./doc/install-guide/section_basics-queue.xml100(para)
|
||||
msgid ""
|
||||
"Contents of the original file might vary depending on the source of the "
|
||||
"RabbitMQ package. In some cases, you might need to create this file."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/install-guide/section_basics-queue.xml106(para)
|
||||
msgid "Restart the message broker service:"
|
||||
msgstr "メッセージブローカーサービスを再起動します。"
|
||||
|
||||
#: ./doc/install-guide/section_ceilometer-controller.xml12(para)
|
||||
msgid ""
|
||||
"This section describes how to install and configure the Telemetry module, "
|
||||
|
||||
@ -17,8 +17,8 @@
|
||||
msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: OpenStack Manuals\n"
|
||||
"POT-Creation-Date: 2015-03-18 04:57+0000\n"
|
||||
"PO-Revision-Date: 2015-03-18 04:52+0000\n"
|
||||
"POT-Creation-Date: 2015-03-26 05:48+0000\n"
|
||||
"PO-Revision-Date: 2015-03-26 06:01+0000\n"
|
||||
"Last-Translator: openstackjenkins <jenkins@openstack.org>\n"
|
||||
"Language-Team: Korean (Korea) (http://www.transifex.com/projects/p/openstack-manuals-i18n/language/ko_KR/)\n"
|
||||
"MIME-Version: 1.0\n"
|
||||
@ -539,8 +539,7 @@ msgstr "Identity 서비스를 시작하고 시스템 부팅시 시작하도록
|
||||
#: ./doc/install-guide/section_nova-compute-install.xml215(para)
|
||||
#: ./doc/install-guide/section_heat-install.xml288(para)
|
||||
#: ./doc/install-guide/section_ceilometer-glance.xml33(para)
|
||||
#: ./doc/install-guide/section_basics-queue.xml49(para)
|
||||
#: ./doc/install-guide/section_basics-queue.xml109(para)
|
||||
#: ./doc/install-guide/section_basics-queue.xml64(para)
|
||||
#: ./doc/install-guide/section_ceilometer-controller.xml26(para)
|
||||
#: ./doc/install-guide/section_ceilometer-controller.xml78(para)
|
||||
#: ./doc/install-guide/section_ceilometer-controller.xml375(para)
|
||||
@ -580,8 +579,7 @@ msgstr "SLES 상에서:"
|
||||
#: ./doc/install-guide/section_nova-compute-install.xml220(para)
|
||||
#: ./doc/install-guide/section_heat-install.xml295(para)
|
||||
#: ./doc/install-guide/section_ceilometer-glance.xml36(para)
|
||||
#: ./doc/install-guide/section_basics-queue.xml52(para)
|
||||
#: ./doc/install-guide/section_basics-queue.xml111(para)
|
||||
#: ./doc/install-guide/section_basics-queue.xml67(para)
|
||||
#: ./doc/install-guide/section_ceilometer-controller.xml24(para)
|
||||
#: ./doc/install-guide/section_ceilometer-controller.xml81(para)
|
||||
#: ./doc/install-guide/section_ceilometer-controller.xml388(para)
|
||||
@ -1027,7 +1025,7 @@ msgstr ""
|
||||
#: ./doc/install-guide/section_nova-compute-install.xml58(replaceable)
|
||||
#: ./doc/install-guide/section_heat-install.xml191(replaceable)
|
||||
#: ./doc/install-guide/section_ceilometer-glance.xml23(replaceable)
|
||||
#: ./doc/install-guide/section_basics-queue.xml64(replaceable)
|
||||
#: ./doc/install-guide/section_basics-queue.xml73(replaceable)
|
||||
#: ./doc/install-guide/section_ceilometer-controller.xml232(replaceable)
|
||||
msgid "RABBIT_PASS"
|
||||
msgstr "RABBIT_PASS"
|
||||
@ -6950,20 +6948,21 @@ msgid "Updated cover and fixed small errors in appendix."
|
||||
msgstr "표지 업데이트 및 부록 부분의 약간의 오류 수정."
|
||||
|
||||
#: ./doc/install-guide/section_basics-queue.xml8(title)
|
||||
msgid "Messaging server"
|
||||
msgstr "메시징 서버"
|
||||
msgid "Message queue"
|
||||
msgstr "메시지 큐"
|
||||
|
||||
#: ./doc/install-guide/section_basics-queue.xml9(para)
|
||||
msgid ""
|
||||
"OpenStack uses a <glossterm>message broker</glossterm> to coordinate "
|
||||
"operations and status information among services. The message broker service"
|
||||
"OpenStack uses a <glossterm>message queue</glossterm> to coordinate "
|
||||
"operations and status information among services. The message queue service "
|
||||
"typically runs on the controller node. OpenStack supports several message "
|
||||
"brokers including <application>RabbitMQ</application>, "
|
||||
"queue services including <application>RabbitMQ</application>, "
|
||||
"<application>Qpid</application>, and <application>ZeroMQ</application>. "
|
||||
"However, most distributions that package OpenStack support a particular "
|
||||
"message broker. This guide covers the RabbitMQ message broker which is "
|
||||
"supported by each distribution. If you prefer to implement a different "
|
||||
"message broker, consult the documentation associated with it."
|
||||
"message queue service. This guide implements the RabbitMQ message queue "
|
||||
"service because most distributions support it. If you prefer to implement a "
|
||||
"different message queue service, consult the documentation associated with "
|
||||
"it."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/install-guide/section_basics-queue.xml21(link)
|
||||
@ -6979,84 +6978,48 @@ msgid "ZeroMQ"
|
||||
msgstr "ZeroMQ"
|
||||
|
||||
#: ./doc/install-guide/section_basics-queue.xml31(title)
|
||||
msgid ""
|
||||
"To install the <application>RabbitMQ</application> message broker service"
|
||||
msgstr "<application>RabbitMQ</application> 메시지 브로커 서비스 설치"
|
||||
|
||||
#: ./doc/install-guide/section_basics-queue.xml43(title)
|
||||
msgid "To configure the message broker service"
|
||||
msgstr "메시지 브로커 서비스 구성"
|
||||
|
||||
#: ./doc/install-guide/section_basics-queue.xml45(para)
|
||||
msgid ""
|
||||
"Start the message broker service and configure it to start when the system "
|
||||
"boots:"
|
||||
msgstr "메시지 브로커 서비스를 시작하고 시스템 부팅시 시작하도록 설정합니다:"
|
||||
|
||||
#: ./doc/install-guide/section_basics-queue.xml57(para)
|
||||
msgid ""
|
||||
"The message broker creates a default account that uses "
|
||||
"<literal>guest</literal> for the username and password. To simplify "
|
||||
"installation of your test environment, we recommend that you use this "
|
||||
"account, but change the password for it."
|
||||
msgid "To install the message queue service"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/install-guide/section_basics-queue.xml61(para)
|
||||
msgid "Run the following command:"
|
||||
msgstr "다음 명령을 실행하십시오:"
|
||||
#: ./doc/install-guide/section_basics-queue.xml33(para)
|
||||
msgid "Add the upstream repository key:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/install-guide/section_basics-queue.xml62(para)
|
||||
#: ./doc/install-guide/section_basics-queue.xml38(para)
|
||||
msgid "Add the upstream repository:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/install-guide/section_basics-queue.xml43(para)
|
||||
msgid "Update the package database:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/install-guide/section_basics-queue.xml47(para)
|
||||
msgid "Install the package:"
|
||||
msgstr "패키지를 설치합니다:"
|
||||
|
||||
#: ./doc/install-guide/section_basics-queue.xml58(title)
|
||||
msgid "To configure the message queue service"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/install-guide/section_basics-queue.xml60(para)
|
||||
msgid ""
|
||||
"Start the message queue service and configure it to start when the system "
|
||||
"boots:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/install-guide/section_basics-queue.xml72(para)
|
||||
msgid "Add the <literal>openstack</literal> user:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/install-guide/section_basics-queue.xml75(para)
|
||||
msgid ""
|
||||
"Replace <replaceable>RABBIT_PASS</replaceable> with a suitable password."
|
||||
msgstr "<replaceable>RABBIT_PASS</replaceable> 를 알맞은 패스워드로 변경하십시오."
|
||||
|
||||
#: ./doc/install-guide/section_basics-queue.xml67(para)
|
||||
#: ./doc/install-guide/section_basics-queue.xml79(para)
|
||||
msgid ""
|
||||
"You must configure the <literal>rabbit_password</literal> key in the "
|
||||
"configuration file for each OpenStack service that uses the message broker."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/install-guide/section_basics-queue.xml71(para)
|
||||
msgid ""
|
||||
"For production environments, you should create a unique account with a "
|
||||
"suitable password. For more information on securing the message broker, see "
|
||||
"the <link "
|
||||
"href=\"https://www.rabbitmq.com/man/rabbitmqctl.1.man.html\">documentation</link>."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/install-guide/section_basics-queue.xml76(para)
|
||||
msgid ""
|
||||
"If you decide to create a unique account with a suitable password for your "
|
||||
"test environment, you must configure the <literal>rabbit_userid</literal> "
|
||||
"and <literal>rabbit_password</literal> keys in the configuration file of "
|
||||
"each OpenStack service that uses the message broker."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/install-guide/section_basics-queue.xml84(para)
|
||||
msgid ""
|
||||
"For RabbitMQ version 3.3.0 or newer, you must enable remote access for the "
|
||||
"<literal>guest</literal> account."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/install-guide/section_basics-queue.xml88(para)
|
||||
msgid "Check the RabbitMQ version:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/install-guide/section_basics-queue.xml94(para)
|
||||
msgid ""
|
||||
"If necessary, edit the <filename>/etc/rabbitmq/rabbitmq.config</filename> "
|
||||
"file and configure <literal>loopback_users</literal> to reference an empty "
|
||||
"list:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/install-guide/section_basics-queue.xml100(para)
|
||||
msgid ""
|
||||
"Contents of the original file might vary depending on the source of the "
|
||||
"RabbitMQ package. In some cases, you might need to create this file."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/install-guide/section_basics-queue.xml106(para)
|
||||
msgid "Restart the message broker service:"
|
||||
"Permit configuration, write, and read access for the "
|
||||
"<literal>openstack</literal> user:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/install-guide/section_ceilometer-controller.xml12(para)
|
||||
|
||||
@ -13,8 +13,8 @@
|
||||
msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: OpenStack Manuals\n"
|
||||
"POT-Creation-Date: 2015-03-18 04:57+0000\n"
|
||||
"PO-Revision-Date: 2015-03-18 04:52+0000\n"
|
||||
"POT-Creation-Date: 2015-03-26 05:48+0000\n"
|
||||
"PO-Revision-Date: 2015-03-26 06:01+0000\n"
|
||||
"Last-Translator: openstackjenkins <jenkins@openstack.org>\n"
|
||||
"Language-Team: Portuguese (Brazil) (http://www.transifex.com/projects/p/openstack-manuals-i18n/language/pt_BR/)\n"
|
||||
"MIME-Version: 1.0\n"
|
||||
@ -535,8 +535,7 @@ msgstr "Inicie o serviço de Identidade e configure-o para iniciar quando o sist
|
||||
#: ./doc/install-guide/section_nova-compute-install.xml215(para)
|
||||
#: ./doc/install-guide/section_heat-install.xml288(para)
|
||||
#: ./doc/install-guide/section_ceilometer-glance.xml33(para)
|
||||
#: ./doc/install-guide/section_basics-queue.xml49(para)
|
||||
#: ./doc/install-guide/section_basics-queue.xml109(para)
|
||||
#: ./doc/install-guide/section_basics-queue.xml64(para)
|
||||
#: ./doc/install-guide/section_ceilometer-controller.xml26(para)
|
||||
#: ./doc/install-guide/section_ceilometer-controller.xml78(para)
|
||||
#: ./doc/install-guide/section_ceilometer-controller.xml375(para)
|
||||
@ -576,8 +575,7 @@ msgstr "No SLES:"
|
||||
#: ./doc/install-guide/section_nova-compute-install.xml220(para)
|
||||
#: ./doc/install-guide/section_heat-install.xml295(para)
|
||||
#: ./doc/install-guide/section_ceilometer-glance.xml36(para)
|
||||
#: ./doc/install-guide/section_basics-queue.xml52(para)
|
||||
#: ./doc/install-guide/section_basics-queue.xml111(para)
|
||||
#: ./doc/install-guide/section_basics-queue.xml67(para)
|
||||
#: ./doc/install-guide/section_ceilometer-controller.xml24(para)
|
||||
#: ./doc/install-guide/section_ceilometer-controller.xml81(para)
|
||||
#: ./doc/install-guide/section_ceilometer-controller.xml388(para)
|
||||
@ -1023,7 +1021,7 @@ msgstr ""
|
||||
#: ./doc/install-guide/section_nova-compute-install.xml58(replaceable)
|
||||
#: ./doc/install-guide/section_heat-install.xml191(replaceable)
|
||||
#: ./doc/install-guide/section_ceilometer-glance.xml23(replaceable)
|
||||
#: ./doc/install-guide/section_basics-queue.xml64(replaceable)
|
||||
#: ./doc/install-guide/section_basics-queue.xml73(replaceable)
|
||||
#: ./doc/install-guide/section_ceilometer-controller.xml232(replaceable)
|
||||
msgid "RABBIT_PASS"
|
||||
msgstr "RABBIT_PASS"
|
||||
@ -6946,21 +6944,22 @@ msgid "Updated cover and fixed small errors in appendix."
|
||||
msgstr "Atualizada a capa e corrigidos pequenos erros no apêndice."
|
||||
|
||||
#: ./doc/install-guide/section_basics-queue.xml8(title)
|
||||
msgid "Messaging server"
|
||||
msgstr "Servidor de mensagens"
|
||||
msgid "Message queue"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/install-guide/section_basics-queue.xml9(para)
|
||||
msgid ""
|
||||
"OpenStack uses a <glossterm>message broker</glossterm> to coordinate "
|
||||
"operations and status information among services. The message broker service"
|
||||
"OpenStack uses a <glossterm>message queue</glossterm> to coordinate "
|
||||
"operations and status information among services. The message queue service "
|
||||
"typically runs on the controller node. OpenStack supports several message "
|
||||
"brokers including <application>RabbitMQ</application>, "
|
||||
"queue services including <application>RabbitMQ</application>, "
|
||||
"<application>Qpid</application>, and <application>ZeroMQ</application>. "
|
||||
"However, most distributions that package OpenStack support a particular "
|
||||
"message broker. This guide covers the RabbitMQ message broker which is "
|
||||
"supported by each distribution. If you prefer to implement a different "
|
||||
"message broker, consult the documentation associated with it."
|
||||
msgstr "O OpenStack utiliza um <glossterm>intermediador de mensagens</glossterm> para coordenar operações e informações de status entre serviços. O serviço de intermediador de mensagens roda no nodo controlador.\nO OpenStack suporta vários intermediadores de mensagens, incluindo <application>RabbitMQ</application>, <application>Qpid</application>, e <application>ZeroMQ</application>. Contudo, a maioria das distribuições que empacotam o OpenStack suportam um intermediador de mensagens particular. Este guia cobre o intermediador de mensagens RabbitMQ que é suportado por cada distribuição. Se você preferir implementar um intermediador de mensagens diferente, consulte a documentação associada a ele."
|
||||
"message queue service. This guide implements the RabbitMQ message queue "
|
||||
"service because most distributions support it. If you prefer to implement a "
|
||||
"different message queue service, consult the documentation associated with "
|
||||
"it."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/install-guide/section_basics-queue.xml21(link)
|
||||
msgid "RabbitMQ"
|
||||
@ -6975,86 +6974,50 @@ msgid "ZeroMQ"
|
||||
msgstr "ZeroMQ"
|
||||
|
||||
#: ./doc/install-guide/section_basics-queue.xml31(title)
|
||||
msgid ""
|
||||
"To install the <application>RabbitMQ</application> message broker service"
|
||||
msgstr "Para instalar o serviço de intermediador de mensagem <application>RabbitMQ</application> "
|
||||
msgid "To install the message queue service"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/install-guide/section_basics-queue.xml43(title)
|
||||
msgid "To configure the message broker service"
|
||||
msgstr "Par configurar o serviço de intermediador de mensagem"
|
||||
#: ./doc/install-guide/section_basics-queue.xml33(para)
|
||||
msgid "Add the upstream repository key:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/install-guide/section_basics-queue.xml45(para)
|
||||
#: ./doc/install-guide/section_basics-queue.xml38(para)
|
||||
msgid "Add the upstream repository:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/install-guide/section_basics-queue.xml43(para)
|
||||
msgid "Update the package database:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/install-guide/section_basics-queue.xml47(para)
|
||||
msgid "Install the package:"
|
||||
msgstr "Instalar o pacote:"
|
||||
|
||||
#: ./doc/install-guide/section_basics-queue.xml58(title)
|
||||
msgid "To configure the message queue service"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/install-guide/section_basics-queue.xml60(para)
|
||||
msgid ""
|
||||
"Start the message broker service and configure it to start when the system "
|
||||
"Start the message queue service and configure it to start when the system "
|
||||
"boots:"
|
||||
msgstr "Inicie o serviço de intermediador de mensagem e configure-o para iniciar quando o sistema inicializar:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/install-guide/section_basics-queue.xml57(para)
|
||||
msgid ""
|
||||
"The message broker creates a default account that uses "
|
||||
"<literal>guest</literal> for the username and password. To simplify "
|
||||
"installation of your test environment, we recommend that you use this "
|
||||
"account, but change the password for it."
|
||||
msgstr "O intermediador de mensagens cria uma conta padrão que utiliza <literal>guest</literal> para nome de usuário e senha. Para simplificar a instalação do seu ambiente de teste, recomendamos que você utilize esta conta, mas altere a senha para ela."
|
||||
#: ./doc/install-guide/section_basics-queue.xml72(para)
|
||||
msgid "Add the <literal>openstack</literal> user:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/install-guide/section_basics-queue.xml61(para)
|
||||
msgid "Run the following command:"
|
||||
msgstr "Execute o seguinte comando:"
|
||||
|
||||
#: ./doc/install-guide/section_basics-queue.xml62(para)
|
||||
#: ./doc/install-guide/section_basics-queue.xml75(para)
|
||||
msgid ""
|
||||
"Replace <replaceable>RABBIT_PASS</replaceable> with a suitable password."
|
||||
msgstr "Substitua <replaceable>RABBIT_PASS</replaceable> com uma senha adequada."
|
||||
|
||||
#: ./doc/install-guide/section_basics-queue.xml67(para)
|
||||
#: ./doc/install-guide/section_basics-queue.xml79(para)
|
||||
msgid ""
|
||||
"You must configure the <literal>rabbit_password</literal> key in the "
|
||||
"configuration file for each OpenStack service that uses the message broker."
|
||||
msgstr "Você deve configurar a chave do <literal>rabbit_password</literal> no arquivo de configuração para cada serviço OpenStack que utiliza o intermediador de mensagem."
|
||||
|
||||
#: ./doc/install-guide/section_basics-queue.xml71(para)
|
||||
msgid ""
|
||||
"For production environments, you should create a unique account with a "
|
||||
"suitable password. For more information on securing the message broker, see "
|
||||
"the <link "
|
||||
"href=\"https://www.rabbitmq.com/man/rabbitmqctl.1.man.html\">documentation</link>."
|
||||
msgstr "Para ambientes de produção, você deve criar uma conta única com uma senha adequada. Para mais informações sobre como proteger o intermediador de mensagens, consulte a <link href=\"https://www.rabbitmq.com/man/rabbitmqctl.1.man.html\">documentação</link>."
|
||||
|
||||
#: ./doc/install-guide/section_basics-queue.xml76(para)
|
||||
msgid ""
|
||||
"If you decide to create a unique account with a suitable password for your "
|
||||
"test environment, you must configure the <literal>rabbit_userid</literal> "
|
||||
"and <literal>rabbit_password</literal> keys in the configuration file of "
|
||||
"each OpenStack service that uses the message broker."
|
||||
msgstr "Se você decidir criar uma conta única com uma senha adequada para seu ambiente de teste, você deve configurar as chaves <literal>rabbit_userid</literal> e <literal>rabbit_password</literal> no arquivo de configuração de cada serviço OpenStack que utilize o intermediador de mensagens."
|
||||
|
||||
#: ./doc/install-guide/section_basics-queue.xml84(para)
|
||||
msgid ""
|
||||
"For RabbitMQ version 3.3.0 or newer, you must enable remote access for the "
|
||||
"<literal>guest</literal> account."
|
||||
"Permit configuration, write, and read access for the "
|
||||
"<literal>openstack</literal> user:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/install-guide/section_basics-queue.xml88(para)
|
||||
msgid "Check the RabbitMQ version:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/install-guide/section_basics-queue.xml94(para)
|
||||
msgid ""
|
||||
"If necessary, edit the <filename>/etc/rabbitmq/rabbitmq.config</filename> "
|
||||
"file and configure <literal>loopback_users</literal> to reference an empty "
|
||||
"list:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/install-guide/section_basics-queue.xml100(para)
|
||||
msgid ""
|
||||
"Contents of the original file might vary depending on the source of the "
|
||||
"RabbitMQ package. In some cases, you might need to create this file."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/install-guide/section_basics-queue.xml106(para)
|
||||
msgid "Restart the message broker service:"
|
||||
msgstr "Reinicie o serviço de intermediador de mensagens:"
|
||||
|
||||
#: ./doc/install-guide/section_ceilometer-controller.xml12(para)
|
||||
msgid ""
|
||||
"This section describes how to install and configure the Telemetry module, "
|
||||
|
||||
@ -10,8 +10,8 @@
|
||||
msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: OpenStack Manuals\n"
|
||||
"POT-Creation-Date: 2015-03-18 04:57+0000\n"
|
||||
"PO-Revision-Date: 2015-03-18 04:52+0000\n"
|
||||
"POT-Creation-Date: 2015-03-26 05:48+0000\n"
|
||||
"PO-Revision-Date: 2015-03-26 06:01+0000\n"
|
||||
"Last-Translator: openstackjenkins <jenkins@openstack.org>\n"
|
||||
"Language-Team: Russian (http://www.transifex.com/projects/p/openstack-manuals-i18n/language/ru/)\n"
|
||||
"MIME-Version: 1.0\n"
|
||||
@ -532,8 +532,7 @@ msgstr "Запустите службу Идентификации и настр
|
||||
#: ./doc/install-guide/section_nova-compute-install.xml215(para)
|
||||
#: ./doc/install-guide/section_heat-install.xml288(para)
|
||||
#: ./doc/install-guide/section_ceilometer-glance.xml33(para)
|
||||
#: ./doc/install-guide/section_basics-queue.xml49(para)
|
||||
#: ./doc/install-guide/section_basics-queue.xml109(para)
|
||||
#: ./doc/install-guide/section_basics-queue.xml64(para)
|
||||
#: ./doc/install-guide/section_ceilometer-controller.xml26(para)
|
||||
#: ./doc/install-guide/section_ceilometer-controller.xml78(para)
|
||||
#: ./doc/install-guide/section_ceilometer-controller.xml375(para)
|
||||
@ -573,8 +572,7 @@ msgstr "На SLES:"
|
||||
#: ./doc/install-guide/section_nova-compute-install.xml220(para)
|
||||
#: ./doc/install-guide/section_heat-install.xml295(para)
|
||||
#: ./doc/install-guide/section_ceilometer-glance.xml36(para)
|
||||
#: ./doc/install-guide/section_basics-queue.xml52(para)
|
||||
#: ./doc/install-guide/section_basics-queue.xml111(para)
|
||||
#: ./doc/install-guide/section_basics-queue.xml67(para)
|
||||
#: ./doc/install-guide/section_ceilometer-controller.xml24(para)
|
||||
#: ./doc/install-guide/section_ceilometer-controller.xml81(para)
|
||||
#: ./doc/install-guide/section_ceilometer-controller.xml388(para)
|
||||
@ -1020,7 +1018,7 @@ msgstr ""
|
||||
#: ./doc/install-guide/section_nova-compute-install.xml58(replaceable)
|
||||
#: ./doc/install-guide/section_heat-install.xml191(replaceable)
|
||||
#: ./doc/install-guide/section_ceilometer-glance.xml23(replaceable)
|
||||
#: ./doc/install-guide/section_basics-queue.xml64(replaceable)
|
||||
#: ./doc/install-guide/section_basics-queue.xml73(replaceable)
|
||||
#: ./doc/install-guide/section_ceilometer-controller.xml232(replaceable)
|
||||
msgid "RABBIT_PASS"
|
||||
msgstr "RABBIT_PASS"
|
||||
@ -6943,21 +6941,22 @@ msgid "Updated cover and fixed small errors in appendix."
|
||||
msgstr "Обновлена обложка и исправлены небольшие ошибки в приложении."
|
||||
|
||||
#: ./doc/install-guide/section_basics-queue.xml8(title)
|
||||
msgid "Messaging server"
|
||||
msgstr "Сервер сообщений"
|
||||
msgid "Message queue"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/install-guide/section_basics-queue.xml9(para)
|
||||
msgid ""
|
||||
"OpenStack uses a <glossterm>message broker</glossterm> to coordinate "
|
||||
"operations and status information among services. The message broker service"
|
||||
"OpenStack uses a <glossterm>message queue</glossterm> to coordinate "
|
||||
"operations and status information among services. The message queue service "
|
||||
"typically runs on the controller node. OpenStack supports several message "
|
||||
"brokers including <application>RabbitMQ</application>, "
|
||||
"queue services including <application>RabbitMQ</application>, "
|
||||
"<application>Qpid</application>, and <application>ZeroMQ</application>. "
|
||||
"However, most distributions that package OpenStack support a particular "
|
||||
"message broker. This guide covers the RabbitMQ message broker which is "
|
||||
"supported by each distribution. If you prefer to implement a different "
|
||||
"message broker, consult the documentation associated with it."
|
||||
msgstr "OpenStack использует <glossterm>брокер сообщенийr</glossterm> для координации операций и информации о статусе между службами. Служба брокера сообщений обычно запущена на управляющем узле. OpenStack поддерживает несколько брокеров сообщений, включая <application>RabbitMQ</application>, <application>Qpid</application> и <application>ZeroMQ</application>. Однако, большинство дистрибутивов, поддерживающих OpenStack, поддерживают определённый брокер сообщений. Это руководство использует брокер сообщений RabbitMQ, который поддерживается каждым дистрибутивом. Если вы предпочитаете использовать другой брокер сообщений, проконсультируйтесь с его документацией."
|
||||
"message queue service. This guide implements the RabbitMQ message queue "
|
||||
"service because most distributions support it. If you prefer to implement a "
|
||||
"different message queue service, consult the documentation associated with "
|
||||
"it."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/install-guide/section_basics-queue.xml21(link)
|
||||
msgid "RabbitMQ"
|
||||
@ -6972,84 +6971,48 @@ msgid "ZeroMQ"
|
||||
msgstr "ZeroMQ"
|
||||
|
||||
#: ./doc/install-guide/section_basics-queue.xml31(title)
|
||||
msgid ""
|
||||
"To install the <application>RabbitMQ</application> message broker service"
|
||||
msgstr "Для установки брокера сообщений <application>RabbitMQ</application>"
|
||||
msgid "To install the message queue service"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/install-guide/section_basics-queue.xml43(title)
|
||||
msgid "To configure the message broker service"
|
||||
msgstr "Для настройки брокера сообщений"
|
||||
#: ./doc/install-guide/section_basics-queue.xml33(para)
|
||||
msgid "Add the upstream repository key:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/install-guide/section_basics-queue.xml45(para)
|
||||
#: ./doc/install-guide/section_basics-queue.xml38(para)
|
||||
msgid "Add the upstream repository:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/install-guide/section_basics-queue.xml43(para)
|
||||
msgid "Update the package database:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/install-guide/section_basics-queue.xml47(para)
|
||||
msgid "Install the package:"
|
||||
msgstr "Установите пакет:"
|
||||
|
||||
#: ./doc/install-guide/section_basics-queue.xml58(title)
|
||||
msgid "To configure the message queue service"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/install-guide/section_basics-queue.xml60(para)
|
||||
msgid ""
|
||||
"Start the message broker service and configure it to start when the system "
|
||||
"Start the message queue service and configure it to start when the system "
|
||||
"boots:"
|
||||
msgstr "Запустите сервис брокера сообщений и настройте его автоматический запуск при загрузке системы:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/install-guide/section_basics-queue.xml57(para)
|
||||
msgid ""
|
||||
"The message broker creates a default account that uses "
|
||||
"<literal>guest</literal> for the username and password. To simplify "
|
||||
"installation of your test environment, we recommend that you use this "
|
||||
"account, but change the password for it."
|
||||
msgstr "Брокер сообщений создаёт стандартный аккаунт, который использует <literal>guest</literal> в качестве имени пользователя и пароля. Для упрощения установки вашей тестовой среды, мы рекомендуем использовать этот аккаунт, но изменить его пароль."
|
||||
#: ./doc/install-guide/section_basics-queue.xml72(para)
|
||||
msgid "Add the <literal>openstack</literal> user:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/install-guide/section_basics-queue.xml61(para)
|
||||
msgid "Run the following command:"
|
||||
msgstr "Исполните следующую команду:"
|
||||
|
||||
#: ./doc/install-guide/section_basics-queue.xml62(para)
|
||||
#: ./doc/install-guide/section_basics-queue.xml75(para)
|
||||
msgid ""
|
||||
"Replace <replaceable>RABBIT_PASS</replaceable> with a suitable password."
|
||||
msgstr "Замените <replaceable>RABBIT_PASS</replaceable> на подходящий пароль."
|
||||
|
||||
#: ./doc/install-guide/section_basics-queue.xml67(para)
|
||||
#: ./doc/install-guide/section_basics-queue.xml79(para)
|
||||
msgid ""
|
||||
"You must configure the <literal>rabbit_password</literal> key in the "
|
||||
"configuration file for each OpenStack service that uses the message broker."
|
||||
msgstr "Вам необходимо настроить ключ <literal>rabbit_password</literal> в конфигурционных файлов каждой службы OpenStack, которая использует брокер сообщений."
|
||||
|
||||
#: ./doc/install-guide/section_basics-queue.xml71(para)
|
||||
msgid ""
|
||||
"For production environments, you should create a unique account with a "
|
||||
"suitable password. For more information on securing the message broker, see "
|
||||
"the <link "
|
||||
"href=\"https://www.rabbitmq.com/man/rabbitmqctl.1.man.html\">documentation</link>."
|
||||
msgstr "Для производственных сред, вам стоит создать уникальный аккаунт с подходящим паролем. За дополнительной информацией о том, как обезопасить брокер сообщений, обратитесь к <link href=\"https://www.rabbitmq.com/man/rabbitmqctl.1.man.html\">документации</link>."
|
||||
|
||||
#: ./doc/install-guide/section_basics-queue.xml76(para)
|
||||
msgid ""
|
||||
"If you decide to create a unique account with a suitable password for your "
|
||||
"test environment, you must configure the <literal>rabbit_userid</literal> "
|
||||
"and <literal>rabbit_password</literal> keys in the configuration file of "
|
||||
"each OpenStack service that uses the message broker."
|
||||
msgstr "Если вы решите создать уникальный аккаунт с подходящим паролем для вашей тестовой среды, вам необходимо настроить ключи <literal>rabbit_userid</literal> и <literal>rabbit_password</literal> в файле конфигурации каждой службы OpenStack, которая использует этот брокер сообщений."
|
||||
|
||||
#: ./doc/install-guide/section_basics-queue.xml84(para)
|
||||
msgid ""
|
||||
"For RabbitMQ version 3.3.0 or newer, you must enable remote access for the "
|
||||
"<literal>guest</literal> account."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/install-guide/section_basics-queue.xml88(para)
|
||||
msgid "Check the RabbitMQ version:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/install-guide/section_basics-queue.xml94(para)
|
||||
msgid ""
|
||||
"If necessary, edit the <filename>/etc/rabbitmq/rabbitmq.config</filename> "
|
||||
"file and configure <literal>loopback_users</literal> to reference an empty "
|
||||
"list:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/install-guide/section_basics-queue.xml100(para)
|
||||
msgid ""
|
||||
"Contents of the original file might vary depending on the source of the "
|
||||
"RabbitMQ package. In some cases, you might need to create this file."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/install-guide/section_basics-queue.xml106(para)
|
||||
msgid "Restart the message broker service:"
|
||||
"Permit configuration, write, and read access for the "
|
||||
"<literal>openstack</literal> user:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/install-guide/section_ceilometer-controller.xml12(para)
|
||||
|
||||
@ -20,9 +20,9 @@
|
||||
msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: OpenStack Manuals\n"
|
||||
"POT-Creation-Date: 2015-03-25 04:19+0000\n"
|
||||
"PO-Revision-Date: 2015-03-25 02:31+0000\n"
|
||||
"Last-Translator: Alfred <alfredhuang211@qq.com>\n"
|
||||
"POT-Creation-Date: 2015-03-26 05:48+0000\n"
|
||||
"PO-Revision-Date: 2015-03-26 06:01+0000\n"
|
||||
"Last-Translator: openstackjenkins <jenkins@openstack.org>\n"
|
||||
"Language-Team: Chinese (China) (http://www.transifex.com/projects/p/openstack-manuals-i18n/language/zh_CN/)\n"
|
||||
"MIME-Version: 1.0\n"
|
||||
"Content-Type: text/plain; charset=UTF-8\n"
|
||||
@ -542,8 +542,7 @@ msgstr "启动身份认证服务，并将该服务配为系统启动时自动启
|
||||
#: ./doc/install-guide/section_nova-compute-install.xml215(para)
|
||||
#: ./doc/install-guide/section_heat-install.xml288(para)
|
||||
#: ./doc/install-guide/section_ceilometer-glance.xml33(para)
|
||||
#: ./doc/install-guide/section_basics-queue.xml49(para)
|
||||
#: ./doc/install-guide/section_basics-queue.xml109(para)
|
||||
#: ./doc/install-guide/section_basics-queue.xml64(para)
|
||||
#: ./doc/install-guide/section_ceilometer-controller.xml26(para)
|
||||
#: ./doc/install-guide/section_ceilometer-controller.xml78(para)
|
||||
#: ./doc/install-guide/section_ceilometer-controller.xml375(para)
|
||||
@ -583,8 +582,7 @@ msgstr "在 SLES 系统中："
|
||||
#: ./doc/install-guide/section_nova-compute-install.xml220(para)
|
||||
#: ./doc/install-guide/section_heat-install.xml295(para)
|
||||
#: ./doc/install-guide/section_ceilometer-glance.xml36(para)
|
||||
#: ./doc/install-guide/section_basics-queue.xml52(para)
|
||||
#: ./doc/install-guide/section_basics-queue.xml111(para)
|
||||
#: ./doc/install-guide/section_basics-queue.xml67(para)
|
||||
#: ./doc/install-guide/section_ceilometer-controller.xml24(para)
|
||||
#: ./doc/install-guide/section_ceilometer-controller.xml81(para)
|
||||
#: ./doc/install-guide/section_ceilometer-controller.xml388(para)
|
||||
@ -1030,7 +1028,7 @@ msgstr "在 <literal>[filter:ceilometer]</literal> 部分，配置提醒："
|
||||
#: ./doc/install-guide/section_nova-compute-install.xml58(replaceable)
|
||||
#: ./doc/install-guide/section_heat-install.xml191(replaceable)
|
||||
#: ./doc/install-guide/section_ceilometer-glance.xml23(replaceable)
|
||||
#: ./doc/install-guide/section_basics-queue.xml64(replaceable)
|
||||
#: ./doc/install-guide/section_basics-queue.xml73(replaceable)
|
||||
#: ./doc/install-guide/section_ceilometer-controller.xml232(replaceable)
|
||||
msgid "RABBIT_PASS"
|
||||
msgstr "RABBIT_PASS"
|
||||
@ -1254,7 +1252,7 @@ msgstr "配置 Compute 服务"
|
||||
msgid ""
|
||||
"Telemetry uses a combination of notifications and an agent to collect "
|
||||
"Compute metrics. Perform these steps on each compute node."
|
||||
msgstr ""
|
||||
msgstr "Telemetry 通过结合使用通知和代理来收集Computer度量值。在每个计算节点上执行这些步骤。"
|
||||
|
||||
#: ./doc/install-guide/section_ceilometer-nova.xml12(title)
|
||||
msgid "To install and configure the agent"
|
||||
@ -2126,7 +2124,7 @@ msgid ""
|
||||
"baseform=\"firewall\">firewalls</glossterm>, <glossterm baseform=\"load "
|
||||
"balancer\">load balancers</glossterm>, and <glossterm baseform=\"virtual "
|
||||
"private network (VPN)\">virtual private networks (VPNs)</glossterm>."
|
||||
msgstr ""
|
||||
msgstr "OpenStack Networking (neutron) 管理您的OpenStack环境中虚拟网络基础设施 (VNI) 的所有方面和物理网络基础设施 (PNI) 的接入层方面。OpenStack Networking 允许租户创建高级虚拟网络拓扑，包括<glossterm baseform=\"firewall\">防火墙</glossterm>， <glossterm baseform=\"load balancer\">负载均衡</glossterm>和<glossterm baseform=\"virtual private network (VPN)\">虚拟私有网络(VPNs)</glossterm>等服务。"
|
||||
|
||||
#: ./doc/install-guide/section_neutron-concepts.xml17(para)
|
||||
msgid ""
|
||||
@ -2152,7 +2150,7 @@ msgid ""
|
||||
" on the external network are accessible by anybody physically on the outside"
|
||||
" network. Because the external network merely represents a view into the "
|
||||
"outside network, DHCP is disabled on this network."
|
||||
msgstr ""
|
||||
msgstr "任何给定的Networking设置至少有一个外部网络。不像其他的网络，外部网络不仅仅是一个虚拟定义的网络。相反,它代表了一种OpenStack安装之外的能从物理的，外部的网络访问的视图。外部网络上的IP地址能被任何物理接入外面网络的人所访问。因为外部网络仅仅代表了进入外面网络的一个视图，网络上的DHCP是关闭的。"
|
||||
|
||||
#: ./doc/install-guide/section_neutron-concepts.xml32(para)
|
||||
msgid ""
|
||||
@ -2161,7 +2159,7 @@ msgid ""
|
||||
"VMs. Only the VMs on any given internal network, or those on subnets "
|
||||
"connected through interfaces to a similar router, can access VMs connected "
|
||||
"to that network directly."
|
||||
msgstr ""
|
||||
msgstr "外部网络之外，任何 Networking 设置拥有一个或多个内部网络。这些软件定义的网络直接连接到虚拟机。仅仅在给定网络上的虚拟机，或那些在通过接口连接到相近路由的子网上的虚拟机，能直接访问连接到那个网络上的虚拟机。"
|
||||
|
||||
#: ./doc/install-guide/section_neutron-concepts.xml38(para)
|
||||
msgid ""
|
||||
@ -2179,7 +2177,7 @@ msgid ""
|
||||
" the internal network. Whenever something is connected to a subnet, that "
|
||||
"connection is called a port.You can associate external network IP addresses "
|
||||
"with ports to VMs. This way, entities on the outside network can access VMs."
|
||||
msgstr ""
|
||||
msgstr "另外，您能够将外部网络的IP地址分配到内部网络的端口。无论合适有什么连接上了子网，那个连接就被称为一个端口。您能连接外部网络的IP地址和虚拟机的端口。这样，外面网络的实体就能访问虚拟机了。"
|
||||
|
||||
#: ./doc/install-guide/section_neutron-concepts.xml50(para)
|
||||
msgid ""
|
||||
@ -2188,7 +2186,7 @@ msgid ""
|
||||
"rules in groups. A VM can belong to one or more security groups, and "
|
||||
"Networking applies the rules in those security groups to block or unblock "
|
||||
"ports, port ranges, or traffic types for that VM."
|
||||
msgstr ""
|
||||
msgstr "Networking也支持<emphasis role=\"italic\">安全组</emphasis>。安全组允许管理员分组定义防火墙规则。一个虚拟机可以属于一个或多个安全组，Networking针对这个虚拟机，应用这些安全组里的规则来阻塞或者开启端口，端口范围，或通讯类型。"
|
||||
|
||||
#: ./doc/install-guide/section_neutron-concepts.xml56(para)
|
||||
msgid ""
|
||||
@ -2198,7 +2196,7 @@ msgid ""
|
||||
"plug-in and a security group plug-in (or just the No-Op security group plug-"
|
||||
"in). Additionally, Firewall-as-a-Service (FWaaS) and Load-Balancer-"
|
||||
"as-a-Service (LBaaS) plug-ins are available."
|
||||
msgstr ""
|
||||
msgstr "每一个Networking使用的插件都有其自有的概念。虽然对操作VNI和OpenStack环境不是至关重要的，但理解这些概念能帮助你设置Networking。所有的Networking安装使用了一个核心插件和一个安全组插件(或仅是空操作安全组插件)。另外，防火墙即服务(FWaaS)和负载均衡即服务(LBaaS)插件是可用的。"
|
||||
|
||||
#: ./doc/install-guide/section_nova-networking-initial-network.xml7(title)
|
||||
msgid "Create initial network"
|
||||
@ -2281,7 +2279,7 @@ msgid ""
|
||||
"href=\"http://git.openstack.org/cgit/openstack/horizon\">Horizon</link>, is "
|
||||
"a Web interface that enables cloud administrators and users to manage "
|
||||
"various OpenStack resources and services."
|
||||
msgstr ""
|
||||
msgstr "OpenStack 仪表盘，即 <link href=\"http://git.openstack.org/cgit/openstack/horizon\">Horizon</link>，是云管理员和用户管理OpenStack资源和服务的网络界面。"
|
||||
|
||||
#: ./doc/install-guide/ch_horizon.xml13(para)
|
||||
msgid ""
|
||||
@ -6953,20 +6951,21 @@ msgid "Updated cover and fixed small errors in appendix."
|
||||
msgstr "更新了封面并修正了附录中的一些小错误。"
|
||||
|
||||
#: ./doc/install-guide/section_basics-queue.xml8(title)
|
||||
msgid "Messaging server"
|
||||
msgstr "消息服务器"
|
||||
msgid "Message queue"
|
||||
msgstr "消息队列"
|
||||
|
||||
#: ./doc/install-guide/section_basics-queue.xml9(para)
|
||||
msgid ""
|
||||
"OpenStack uses a <glossterm>message broker</glossterm> to coordinate "
|
||||
"operations and status information among services. The message broker service"
|
||||
"OpenStack uses a <glossterm>message queue</glossterm> to coordinate "
|
||||
"operations and status information among services. The message queue service "
|
||||
"typically runs on the controller node. OpenStack supports several message "
|
||||
"brokers including <application>RabbitMQ</application>, "
|
||||
"queue services including <application>RabbitMQ</application>, "
|
||||
"<application>Qpid</application>, and <application>ZeroMQ</application>. "
|
||||
"However, most distributions that package OpenStack support a particular "
|
||||
"message broker. This guide covers the RabbitMQ message broker which is "
|
||||
"supported by each distribution. If you prefer to implement a different "
|
||||
"message broker, consult the documentation associated with it."
|
||||
"message queue service. This guide implements the RabbitMQ message queue "
|
||||
"service because most distributions support it. If you prefer to implement a "
|
||||
"different message queue service, consult the documentation associated with "
|
||||
"it."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/install-guide/section_basics-queue.xml21(link)
|
||||
@ -6982,86 +6981,50 @@ msgid "ZeroMQ"
|
||||
msgstr "ZeroMQ"
|
||||
|
||||
#: ./doc/install-guide/section_basics-queue.xml31(title)
|
||||
msgid ""
|
||||
"To install the <application>RabbitMQ</application> message broker service"
|
||||
msgstr "安装 <application>RabbitMQ</application> 消息 broker 服务"
|
||||
|
||||
#: ./doc/install-guide/section_basics-queue.xml43(title)
|
||||
msgid "To configure the message broker service"
|
||||
msgstr "配置 message broker 服务"
|
||||
|
||||
#: ./doc/install-guide/section_basics-queue.xml45(para)
|
||||
msgid ""
|
||||
"Start the message broker service and configure it to start when the system "
|
||||
"boots:"
|
||||
msgstr "启动消息 broker 服务并将其配置为随系统启动："
|
||||
|
||||
#: ./doc/install-guide/section_basics-queue.xml57(para)
|
||||
msgid ""
|
||||
"The message broker creates a default account that uses "
|
||||
"<literal>guest</literal> for the username and password. To simplify "
|
||||
"installation of your test environment, we recommend that you use this "
|
||||
"account, but change the password for it."
|
||||
msgid "To install the message queue service"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/install-guide/section_basics-queue.xml61(para)
|
||||
msgid "Run the following command:"
|
||||
msgstr "执行以下命令："
|
||||
#: ./doc/install-guide/section_basics-queue.xml33(para)
|
||||
msgid "Add the upstream repository key:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/install-guide/section_basics-queue.xml62(para)
|
||||
#: ./doc/install-guide/section_basics-queue.xml38(para)
|
||||
msgid "Add the upstream repository:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/install-guide/section_basics-queue.xml43(para)
|
||||
msgid "Update the package database:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/install-guide/section_basics-queue.xml47(para)
|
||||
msgid "Install the package:"
|
||||
msgstr "安装包："
|
||||
|
||||
#: ./doc/install-guide/section_basics-queue.xml58(title)
|
||||
msgid "To configure the message queue service"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/install-guide/section_basics-queue.xml60(para)
|
||||
msgid ""
|
||||
"Start the message queue service and configure it to start when the system "
|
||||
"boots:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/install-guide/section_basics-queue.xml72(para)
|
||||
msgid "Add the <literal>openstack</literal> user:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/install-guide/section_basics-queue.xml75(para)
|
||||
msgid ""
|
||||
"Replace <replaceable>RABBIT_PASS</replaceable> with a suitable password."
|
||||
msgstr "将其中的 <replaceable>RABBIT_PASS</replaceable> 替换为一个合适的密码。"
|
||||
|
||||
#: ./doc/install-guide/section_basics-queue.xml67(para)
|
||||
#: ./doc/install-guide/section_basics-queue.xml79(para)
|
||||
msgid ""
|
||||
"You must configure the <literal>rabbit_password</literal> key in the "
|
||||
"configuration file for each OpenStack service that uses the message broker."
|
||||
"Permit configuration, write, and read access for the "
|
||||
"<literal>openstack</literal> user:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/install-guide/section_basics-queue.xml71(para)
|
||||
msgid ""
|
||||
"For production environments, you should create a unique account with a "
|
||||
"suitable password. For more information on securing the message broker, see "
|
||||
"the <link "
|
||||
"href=\"https://www.rabbitmq.com/man/rabbitmqctl.1.man.html\">documentation</link>."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/install-guide/section_basics-queue.xml76(para)
|
||||
msgid ""
|
||||
"If you decide to create a unique account with a suitable password for your "
|
||||
"test environment, you must configure the <literal>rabbit_userid</literal> "
|
||||
"and <literal>rabbit_password</literal> keys in the configuration file of "
|
||||
"each OpenStack service that uses the message broker."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/install-guide/section_basics-queue.xml84(para)
|
||||
msgid ""
|
||||
"For RabbitMQ version 3.3.0 or newer, you must enable remote access for the "
|
||||
"<literal>guest</literal> account."
|
||||
msgstr "对于 RabbitMQ 的 3.3.0 或更新版本，您必须为 <literal>guest</literal> 帐户启用远程访问。"
|
||||
|
||||
#: ./doc/install-guide/section_basics-queue.xml88(para)
|
||||
msgid "Check the RabbitMQ version:"
|
||||
msgstr "检查RabbitMQ的版本："
|
||||
|
||||
#: ./doc/install-guide/section_basics-queue.xml94(para)
|
||||
msgid ""
|
||||
"If necessary, edit the <filename>/etc/rabbitmq/rabbitmq.config</filename> "
|
||||
"file and configure <literal>loopback_users</literal> to reference an empty "
|
||||
"list:"
|
||||
msgstr "如果需要的话，修改配置文件 <filename>/etc/rabbitmq/rabbitmq.config</filename> 并配置 <literal>loopback_users</literal> 为一个空的列表："
|
||||
|
||||
#: ./doc/install-guide/section_basics-queue.xml100(para)
|
||||
msgid ""
|
||||
"Contents of the original file might vary depending on the source of the "
|
||||
"RabbitMQ package. In some cases, you might need to create this file."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/install-guide/section_basics-queue.xml106(para)
|
||||
msgid "Restart the message broker service:"
|
||||
msgstr "重启消息 broker 服务："
|
||||
|
||||
#: ./doc/install-guide/section_ceilometer-controller.xml12(para)
|
||||
msgid ""
|
||||
"This section describes how to install and configure the Telemetry module, "
|
||||
|
||||
File diff suppressed because it is too large
Load Diff
Loading…
Reference in New Issue
Block a user