Imported Translations from Transifex
For more information about this automatic import see: https://wiki.openstack.org/wiki/Translations/Infrastructure Change-Id: I6f0482c4dc6bee27c2d8d11c85c5432e654a36f7
This commit is contained in:
OpenStack Proposal Bot
parent
a0224e0dd2
commit
f517234b8c
File diff suppressed because it is too large
Load Diff
@ -1,7 +1,7 @@
|
||||
msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: PACKAGE VERSION\n"
|
||||
"POT-Creation-Date: 2015-04-25 06:08+0000\n"
|
||||
"POT-Creation-Date: 2015-04-30 06:07+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 "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 Kilo 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)
|
||||
@ -907,7 +907,7 @@ msgstr ""
|
||||
msgid "Replication"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/multi_site/section_user_requirements_multi_site.xml:158(para) ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:792(para) ./doc/arch-design/compute_focus/section_tech_considerations_compute_focus.xml:284(para) ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:113(para)
|
||||
#: ./doc/arch-design/multi_site/section_user_requirements_multi_site.xml:158(para) ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:792(para) ./doc/arch-design/compute_focus/section_tech_considerations_compute_focus.xml:284(para) ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:105(para)
|
||||
msgid "Management"
|
||||
msgstr ""
|
||||
|
||||
@ -1134,7 +1134,7 @@ msgid "The capacity requirements of the links between sites is driven by applica
|
||||
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 is 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 Kilo 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)
|
||||
@ -1145,7 +1145,7 @@ msgstr ""
|
||||
msgid "A third form of capacity comes in the multi-region-capable components of OpenStack. Centralized Object Storage is capable of serving objects through a single namespace across multiple regions. Since this works by accessing the object store via swift proxy, it is possible to overload the proxies. There are two options available to mitigate this issue. The first is to deploy a large number of swift proxies. The drawback to this is that the proxies are not load-balanced and a large file request could continually hit the same proxy. The other way to mitigate this is to front-end the proxies with a caching HTTP proxy and load balancer. Since swift objects are returned to the requester via HTTP, this load balancer would alleviate the load required on the swift proxies."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/multi_site/section_tech_considerations_multi_site.xml:79(title) ./doc/arch-design/compute_focus/section_tech_considerations_compute_focus.xml:217(title) ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:204(title)
|
||||
#: ./doc/arch-design/multi_site/section_tech_considerations_multi_site.xml:79(title) ./doc/arch-design/compute_focus/section_tech_considerations_compute_focus.xml:217(title) ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:196(title)
|
||||
msgid "Utilization"
|
||||
msgstr ""
|
||||
|
||||
@ -1165,7 +1165,7 @@ msgstr ""
|
||||
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:93(term) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:176(term) ./doc/arch-design/compute_focus/section_tech_considerations_compute_focus.xml:258(title) ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:236(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)
|
||||
#: ./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:93(term) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:176(term) ./doc/arch-design/compute_focus/section_tech_considerations_compute_focus.xml:258(title) ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:228(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)
|
||||
msgid "Performance"
|
||||
msgstr ""
|
||||
|
||||
@ -1181,7 +1181,7 @@ msgstr ""
|
||||
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:155(term) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:413(term) ./doc/arch-design/compute_focus/section_tech_considerations_compute_focus.xml:267(title) ./doc/arch-design/hybrid/section_architecture_hybrid.xml:132(para) ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:98(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)
|
||||
#: ./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:155(term) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:413(term) ./doc/arch-design/compute_focus/section_tech_considerations_compute_focus.xml:267(title) ./doc/arch-design/hybrid/section_architecture_hybrid.xml:132(para) ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:90(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)
|
||||
msgid "Security"
|
||||
msgstr ""
|
||||
|
||||
@ -1621,7 +1621,7 @@ msgstr ""
|
||||
msgid "Configuring incorrect IP addresses, VLANs, and routes can cause outages to areas of the network or, in the worst-case scenario, the entire cloud infrastructure. Misconfigurations can cause disruptive problems and should be automated to minimize the opportunity for operator error."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/network_focus/section_user_requirements_network_focus.xml:105(term) ./doc/arch-design/generalpurpose/section_operational_considerations_general_purpose.xml:107(title) ./doc/arch-design/compute_focus/section_operational_considerations_compute_focus.xml:102(title) ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:66(title)
|
||||
#: ./doc/arch-design/network_focus/section_user_requirements_network_focus.xml:105(term) ./doc/arch-design/generalpurpose/section_operational_considerations_general_purpose.xml:107(title) ./doc/arch-design/compute_focus/section_operational_considerations_compute_focus.xml:102(title) ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:58(title)
|
||||
msgid "Capacity planning"
|
||||
msgstr ""
|
||||
|
||||
@ -1818,7 +1818,7 @@ msgid "Compute-heavy workloads may also induce interactions with the network. So
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/network_focus/section_architecture_network_focus.xml:33(para)
|
||||
msgid "Some network dependencies are going to be external to OpenStack. While OpenStack Networking is capable of providing network ports, IP addresses, some level of routing, and overlay networks, there are some other functions that it cannot provide. For many of these, external systems or equipment may be required to fill in the functional gaps. Hardware load balancers are an example of equipment that may be necessary to distribute workloads or offload certain functions. Note that, as of the Icehouse release, dynamic routing is currently in its infancy within OpenStack and may need to be implemented either by an external device or a specialized service instance within OpenStack. Tunneling is a feature provided by OpenStack Networking, however it is constrained to a Networking-managed region. If the need arises to extend a tunnel beyond the OpenStack region to either another region or an external system, it is necessary to implement the tunnel itself outside OpenStack or by using a tunnel management system to map the tunnel or overlay to an external tunnel. OpenStack does not currently provide quotas for network resources. Where network quotas are required, it is necessary to implement quality of service management outside of OpenStack. In many of these instances, similar solutions for traffic shaping or other network functions will be needed."
|
||||
msgid "Some network dependencies are going to be external to OpenStack. While OpenStack Networking is capable of providing network ports, IP addresses, some level of routing, and overlay networks, there are some other functions that it cannot provide. For many of these, external systems or equipment may be required to fill in the functional gaps. Hardware load balancers are an example of equipment that may be necessary to distribute workloads or offload certain functions. Note that, as of the Kilo release, dynamic routing is currently in its infancy within OpenStack and may need to be implemented either by an external device or a specialized service instance within OpenStack. Tunneling is a feature provided by OpenStack Networking, however it is constrained to a Networking-managed region. If the need arises to extend a tunnel beyond the OpenStack region to either another region or an external system, it is necessary to implement the tunnel itself outside OpenStack or by using a tunnel management system to map the tunnel or overlay to an external tunnel. OpenStack does not currently provide quotas for network resources. Where network quotas are required, it is necessary to implement quality of service management outside of OpenStack. In many of these instances, similar solutions for traffic shaping or other network functions will be needed."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/network_focus/section_architecture_network_focus.xml:57(para)
|
||||
@ -1866,7 +1866,7 @@ msgid "Many people overlook an important design decision: The choice of layer-3
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/network_focus/section_architecture_network_focus.xml:164(para)
|
||||
msgid "As of the Icehouse release, OpenStack has limited support for dynamic routing, however there are a number of options available by incorporating third party solutions to implement routing within the cloud including network equipment, hardware nodes, and instances. Some workloads will perform well with nothing more than static routes and default gateways configured at the layer-3 termination point. In most cases this will suffice, however some cases require the addition of at least one type of dynamic routing protocol if not multiple protocols. Having a form of interior gateway protocol (IGP) available to the instances inside an OpenStack installation opens up the possibility of use cases for anycast route injection for services that need to use it as a geographic location or failover mechanism. Other applications may wish to directly participate in a routing protocol, either as a passive observer as in the case of a looking glass, or as an active participant in the form of a route reflector. Since an instance might have a large amount of compute and memory resources, it is trivial to hold an entire unpartitioned routing table and use it to provide services such as network path visibility to other applications or as a monitoring tool."
|
||||
msgid "As of the Kilo release, OpenStack has limited support for dynamic routing, however there are a number of options available by incorporating third party solutions to implement routing within the cloud including network equipment, hardware nodes, and instances. Some workloads will perform well with nothing more than static routes and default gateways configured at the layer-3 termination point. In most cases this will suffice, however some cases require the addition of at least one type of dynamic routing protocol if not multiple protocols. Having a form of interior gateway protocol (IGP) available to the instances inside an OpenStack installation opens up the possibility of use cases for anycast route injection for services that need to use it as a geographic location or failover mechanism. Other applications may wish to directly participate in a routing protocol, either as a passive observer as in the case of a looking glass, or as an active participant in the form of a route reflector. Since an instance might have a large amount of compute and memory resources, it is trivial to hold an entire unpartitioned routing table and use it to provide services such as network path visibility to other applications or as a monitoring tool."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/network_focus/section_architecture_network_focus.xml:186(para)
|
||||
@ -3151,15 +3151,15 @@ msgstr ""
|
||||
msgid "These security domains are:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:786(para) ./doc/arch-design/compute_focus/section_tech_considerations_compute_focus.xml:278(para) ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:107(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:786(para) ./doc/arch-design/compute_focus/section_tech_considerations_compute_focus.xml:278(para) ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:99(para)
|
||||
msgid "Public"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:789(para) ./doc/arch-design/compute_focus/section_tech_considerations_compute_focus.xml:281(para) ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:110(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:789(para) ./doc/arch-design/compute_focus/section_tech_considerations_compute_focus.xml:281(para) ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:102(para)
|
||||
msgid "Guest"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:795(para) ./doc/arch-design/compute_focus/section_tech_considerations_compute_focus.xml:287(para) ./doc/arch-design/hybrid/section_architecture_hybrid.xml:186(title) ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:116(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:795(para) ./doc/arch-design/compute_focus/section_tech_considerations_compute_focus.xml:287(para) ./doc/arch-design/hybrid/section_architecture_hybrid.xml:186(title) ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:108(para)
|
||||
msgid "Data"
|
||||
msgstr ""
|
||||
|
||||
@ -5207,175 +5207,171 @@ msgstr ""
|
||||
msgid "Vendors can add proprietary customization to their distributions. If an application or architecture makes use of these features, it will be difficult to migrate to or use other types of environments."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:38(para)
|
||||
msgid "Anyone planning to use older versions of OpenStack prior to Havana should consider carefully before attempting to incorporate functionality between versions. Internal differences in older versions may be so great that the best approach might be to consider the versions to be essentially diverse platforms, as different as OpenStack is from Amazon Web Services or Microsoft Azure."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:45(para)
|
||||
#: ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:37(para)
|
||||
msgid "If an environment includes non-OpenStack clouds, it may experience compatibility problems. CMP tools must account for the differences in the handling of operations and implementation of services. Some situations in which these incompatibilities can arise include differences between the way in which a cloud:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:52(para)
|
||||
#: ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:44(para)
|
||||
msgid "Deploys instances"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:55(para)
|
||||
#: ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:47(para)
|
||||
msgid "Manages networks"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:58(para)
|
||||
#: ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:50(para)
|
||||
msgid "Treats applications"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:61(para)
|
||||
#: ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:53(para)
|
||||
msgid "Implements services"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:67(para)
|
||||
#: ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:59(para)
|
||||
msgid "One of the primary reasons many organizations turn to a hybrid cloud system is to increase capacity without having to make large capital investments."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:70(para)
|
||||
#: ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:62(para)
|
||||
msgid "Capacity, and the placement of workloads, accounts for the design of a mostly internally-operated cloud. The long-term capacity plan for this design must incorporate growth over time to prevent permanent consumption of a more expensive external cloud. In order to avoid this scenario, we recommend accounting for the future applications' capacity requirements and plan growth appropriately."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:78(para)
|
||||
#: ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:70(para)
|
||||
msgid "Unpredictability is a consideration for capacity planning. It is difficult to predict the amount of load a particular application might incur if the number of users fluctuate, or the application experiences an unexpected increase in popularity. It is possible to define application requirements in terms of vCPU, RAM, bandwidth or other resources and plan appropriately. However, other clouds might not use the same metric or even the same oversubscription rates."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:85(para)
|
||||
#: ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:77(para)
|
||||
msgid "Oversubscription is a method to emulate more capacity than may physically be present. For example, a physical hypervisor node with 32GB RAM may host 24 instances, each provisioned with 2GB RAM. As long as all 24 instances are not concurrently utilizing 2 full gigabytes, this arrangement is a non-issue. However, some hosts take oversubscription to extremes and, as a result, performance can frequently be inconsistent. If at all possible, determine what the oversubscription rates of each host are and plan capacity accordingly."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:99(para)
|
||||
#: ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:91(para)
|
||||
msgid "Security domains are an important distinction when planning for a hybrid cloud environment and its capabilities. A security domain comprises users, applications, servers or networks that share common trust requirements and expectations within a system."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:104(para)
|
||||
#: ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:96(para)
|
||||
msgid "The security domains are:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:119(para)
|
||||
#: ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:111(para)
|
||||
msgid "You can map the security domains individually to the organization's installation or combine them. For example, some deployment topologies combine both guest and data domains onto one physical network, whereas other topologies physically separate the networks. In each case, the cloud operator should be aware of the appropriate security concerns. We recommend mapping security domains against the specific OpenStack deployment topology. The domains and their trust requirements depend upon whether the cloud instance is public, private, or hybrid."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:129(para)
|
||||
#: ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:121(para)
|
||||
msgid "The public security domain is an entirely untrusted area of the cloud infrastructure. It can refer to the internet as a whole, or simply to networks over which an organization has no authority. Do not trust this domain. For example, in a hybrid cloud deployment, any information traversing between and beyond the clouds is of the public domain and untrustworthy."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:135(para)
|
||||
#: ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:127(para)
|
||||
msgid "The guest security domain handles compute data. Instances on the cloud generate the data, but not services that support the operation of the cloud, such as API calls. We recommend not to trust this domain if you are a public cloud provider that uses hybrid cloud configurations, or a private cloud provider who does not have controls on instance use and allows unrestricted internet access to instances. Private cloud providers, however, can use this network as an internally trusted network if controls are in place."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:143(para)
|
||||
#: ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:135(para)
|
||||
msgid "The management security domain is where services interact. The networks in this domain transport confidential data such as configuration parameters, user names, and passwords. Trust this domain when it is behind an organization's firewall in deployments."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:147(para)
|
||||
#: ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:139(para)
|
||||
msgid "The data security domain is concerned primarily with information pertaining to the storage services within OpenStack. The data that crosses this network has integrity and confidentiality requirements. Depending on the type of deployment there may also be availability requirements. The trust level of this network is heavily dependent on deployment decisions and does not have a default level of trust."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:154(para)
|
||||
#: ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:146(para)
|
||||
msgid "When operating or utilizing public or private clouds, consider the management of the users. The identity service allows for LDAP to be part of the authentication process. Including these systems in your OpenStack deployments may ease user management if integrating into existing systems."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:160(para)
|
||||
#: ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:152(para)
|
||||
msgid "Be mindful of consistency when utilizing third party clouds to explore authentication options."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:163(para)
|
||||
#: ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:155(para)
|
||||
msgid "Due to the passing of user names, passwords, and tokens between client machines and API endpoints, we recommend the placement of API services behind hardware to perform SSL termination."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:166(para)
|
||||
#: ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:158(para)
|
||||
msgid "The hypervisor also requires a security assessment. In a public cloud, organizations typically do not have control over the choice of hypervisor. For example, Amazon uses its own particular version of Xen. Properly securing your hypervisor is important. Attacks made upon the unsecured hypervisor are called a \"hypervisor breakout\". Hypervisor breakout describes the event of a compromised or malicious instance breaking out of the resource controls of the hypervisor and gaining access to the bare metal operating system and hardware resources."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:175(para)
|
||||
#: ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:167(para)
|
||||
msgid "There is not an issue if the security of instances is not important. However, enterprises need to avoid vulnerability. The only way to do this is to avoid the situation where the instances are running on a public cloud. That does not mean that there is a need to own all of the infrastructure on which an OpenStack installation operates; it suggests avoiding situations in which sharing hardware with others occurs."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:182(para)
|
||||
#: ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:174(para)
|
||||
msgid "There are other services worth considering that provide a bare metal instance instead of a cloud. In other cases, it is possible to replicate a second private cloud by integrating with a private Cloud-as-a-Service deployment. The organization does not buy the hardware, but also does not share with other tenants. It is also possible to use a provider that hosts a bare-metal \"public\" cloud instance for which the hardware is dedicated only to one customer, or a provider that offers private Cloud-as-a-Service."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:191(para)
|
||||
#: ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:183(para)
|
||||
msgid "It is important to realize that each cloud implements services differently. What keeps data secure in one cloud may not do the same in another. Be sure to know the security requirements of every cloud that handles the organization's data or workloads."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:196(para)
|
||||
#: ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:188(para)
|
||||
msgid "More information on OpenStack Security can be found in the <link href=\"http://docs.openstack.org/security-guide\"><citetitle>OpenStack Security Guide</citetitle></link>."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:205(para)
|
||||
#: ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:197(para)
|
||||
msgid "When it comes to utilization, it is important that the CMP understands what workloads are running, where they are running, and their preferred utilizations. For example, in most cases it is desirable to run as many workloads internally as possible, utilizing other resources only when necessary. On the other hand, situations exist in which the opposite is true. The internal cloud may only be for development and stressing it is undesirable. In most cases, a cost model of various scenarios helps with this decision. However, internal priorities influence this analysis. To improve efficiency, make these decisions programmatically."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:216(para)
|
||||
#: ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:208(para)
|
||||
msgid "The Telemetry module (ceilometer) provides information on the usage of various OpenStack components. There are two limitations to consider:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:221(para)
|
||||
#: ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:213(para)
|
||||
msgid "If there is to be a large amount of data (for example, if monitoring a large cloud, or a very active one) it is desirable to use a NoSQL back end for Ceilometer, such as MongoDB."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:228(para)
|
||||
#: ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:220(para)
|
||||
msgid "You must monitor connections to non-OpenStack clouds and report this information to the CMP."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:237(para)
|
||||
#: ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:229(para)
|
||||
msgid "Performance is of the upmost importance in the design of a cloud. When it comes to a hybrid cloud deployment, many of the same issues for multi-site deployments apply, such as network latency between sites. It is also important to think about the speed at which a workload can be spun up in another cloud, and how to reduce the time necessary to accomplish the task. This may mean moving data closer to applications or applications closer to the data they process, including a grouping functionality so that connections that require low latency take place over a single cloud rather than spanning clouds. This may also mean ensuring that the CMP has the intelligence to know which cloud can most efficiently run which types of workloads."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:250(para)
|
||||
#: ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:242(para)
|
||||
msgid "As with utilization, native OpenStack tools are available to assist. Ceilometer can measure performance and, if necessary, the Orchestration (heat) module can react to changes in demand by spinning up more resources."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:255(para)
|
||||
#: ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:247(para)
|
||||
msgid "It is important to note, however, that Orchestration requires special configurations in the client to enable functioning with solution offerings from Amazon Web Services. When dealing with other types of clouds, it is necessary to rely on the features of the CMP."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:265(title)
|
||||
#: ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:257(title)
|
||||
msgid "Components"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:266(para)
|
||||
#: ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:258(para)
|
||||
msgid "The number and types of native OpenStack components that are available for use is dependent on whether the deployment is exclusively an OpenStack cloud or not."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:269(para)
|
||||
#: ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:261(para)
|
||||
msgid "Using more than one cloud in any situation requires consideration of four OpenStack tools:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:273(para)
|
||||
#: ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:265(para)
|
||||
msgid "OpenStack Compute (nova): Regardless of deployment location, hypervisor choice has a direct effect on how difficult it is to integrate with one or more additional clouds. For example, integrating a Hyper-V based OpenStack cloud with Azure has less compatibility issues than if KVM is used."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:281(para)
|
||||
#: ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:273(para)
|
||||
msgid "Networking (neutron): Whether OpenStack Networking or legacy networking (nova-network) is used, the network is one place where understanding integration capabilities is necessary in order to connect between clouds."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:287(para)
|
||||
#: ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:279(para)
|
||||
msgid "Telemetry module (ceilometer): Use of Telemetry depends, in large part, on what the other parts of the cloud are using."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:292(para)
|
||||
#: ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:284(para)
|
||||
msgid "Orchestration module (heat): Similarly, Orchestration can be a valuable tool in orchestrating tasks a CMP decides are necessary in an OpenStack-based cloud."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:301(title)
|
||||
#: ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:293(title)
|
||||
msgid "Special considerations"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:302(para)
|
||||
#: ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:294(para)
|
||||
msgid "Hybrid cloud deployments also involve two more issues that are not common in other situations:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:306(para)
|
||||
msgid "Image portability: Note that, as of the Icehouse release, there is no single common image format that is usable by all clouds. Conversion or the recreation of images is necessary if porting between clouds. To make things simpler, launch the smallest and simplest images feasible, installing only what is necessary preferably using a deployment manager such as Chef or Puppet. Do not use golden images for speeding up the process. However, if you repeat the deployment of the same images, we recommend utilizing this technique instead of provisioning applications on lighter images each time."
|
||||
#: ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:298(para)
|
||||
msgid "Image portability: Note that, as of the Kilo release, there is no single common image format that is usable by all clouds. Conversion or the recreation of images is necessary if porting between clouds. To make things simpler, launch the smallest and simplest images feasible, installing only what is necessary preferably using a deployment manager such as Chef or Puppet. Do not use golden images for speeding up the process. However, if you repeat the deployment of the same images, we recommend utilizing this technique instead of provisioning applications on lighter images each time."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:318(para)
|
||||
#: ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:310(para)
|
||||
msgid "API differences: Avoid using a hybrid cloud deployment with more than just OpenStack (or with different versions of OpenStack). The APIs need to perform certain functions that are different. The CMP needs to know how to handle all necessary versions. To get around this issue, some implementers build portals to achieve a hybrid cloud environment, but a heavily developer-focused organization may benefit more from a hybrid cloud broker SDK such as jClouds."
|
||||
msgstr ""
|
||||
|
||||
|
||||
@ -9,8 +9,8 @@
|
||||
msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: OpenStack Manuals\n"
|
||||
"POT-Creation-Date: 2015-04-25 08:49+0000\n"
|
||||
"PO-Revision-Date: 2015-04-25 07:21+0000\n"
|
||||
"POT-Creation-Date: 2015-04-30 05:49+0000\n"
|
||||
"PO-Revision-Date: 2015-04-29 14:10+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"
|
||||
@ -802,17 +802,6 @@ msgstr ""
|
||||
"部署者务必意识到这点，为他们的站点提供合适的定制服务目录，无论是手动还是定"
|
||||
"制，都的使用这些部署工具。"
|
||||
|
||||
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 ""
|
||||
"自Icehouse版本发布后，关于实现此特性的文档工作正在进行中。欲了解更多信息参考"
|
||||
"bug相关文档：<link href=\"https://bugs.launchpad.net/openstack-manuals/"
|
||||
"+bug/1340509\">https://bugs.launchpad.net/openstack-manuals/+bug/1340509</"
|
||||
"link>。"
|
||||
|
||||
msgid "Licensing"
|
||||
msgstr "许可"
|
||||
|
||||
@ -2892,41 +2881,6 @@ msgstr ""
|
||||
"网络负载。其他的一些应用也可能是高度事务性的，非常频繁的加上事务性锁，执行相"
|
||||
"应的工作，然后解锁。这也会影响到网络的性能。"
|
||||
|
||||
msgid ""
|
||||
"Some network dependencies are going to be external to OpenStack. While "
|
||||
"OpenStack Networking is capable of providing network ports, IP addresses, "
|
||||
"some level of routing, and overlay networks, there are some other functions "
|
||||
"that it cannot provide. For many of these, external systems or equipment may "
|
||||
"be required to fill in the functional gaps. Hardware load balancers are an "
|
||||
"example of equipment that may be necessary to distribute workloads or "
|
||||
"offload certain functions. Note that, as of the Icehouse release, dynamic "
|
||||
"routing is currently in its infancy within OpenStack and may need to be "
|
||||
"implemented either by an external device or a specialized service instance "
|
||||
"within OpenStack. Tunneling is a feature provided by OpenStack Networking, "
|
||||
"however it is constrained to a Networking-managed region. If the need arises "
|
||||
"to extend a tunnel beyond the OpenStack region to either another region or "
|
||||
"an external system, it is necessary to implement the tunnel itself outside "
|
||||
"OpenStack or by using a tunnel management system to map the tunnel or "
|
||||
"overlay to an external tunnel. OpenStack does not currently provide quotas "
|
||||
"for network resources. Where network quotas are required, it is necessary to "
|
||||
"implement quality of service management outside of OpenStack. In many of "
|
||||
"these instances, similar solutions for traffic shaping or other network "
|
||||
"functions will be needed."
|
||||
msgstr ""
|
||||
"有些网络方面的依赖会是在 OpenStack 环境以外的。虽然 OpenStack 联网方式已经能"
|
||||
"够提供网络端口，IP 地址管理，某种程度上的路由功能，以及覆盖网络，仍然有一些功"
|
||||
"能是其无法提供的。对于这些 OpenStack 提供不了的功能，我们就需要使用外部系统或"
|
||||
"者设备来填补功能上的空白。硬件的负载均衡器就是此类设备中的一种，需要它来分配"
|
||||
"负载或者完成部分特定的上层功能。请注意，直到 Icehouse 版本发布之时，"
|
||||
"OpenStack 中的动态路由功能仍未成熟，且可能需要使用外部的设备或者 OpenStack 中"
|
||||
"专门的服务实例来实现。OpenStack 联网提供了隧道功能，然而该功能却只能在 "
|
||||
"OpenStack 联网所管理的范围内使用。如果需要将隧道从 OpenStack 的范围扩展至另外"
|
||||
"一个区域或者外部系统，则有必要在 OpenStack 之外使用能够将隧道或者整个覆盖网络"
|
||||
"映射到外部的隧道的其它隧道管理系统来实现隧道功能。OpenStack 目前并不提供网络"
|
||||
"资源配额功能。如果需要对网络资源进行配额管理，则有必要在 OpenStack 之外采用其"
|
||||
"它的服务质量管理机制。很多类似的情形下，将需要类似流量整形或者其它网络功能的"
|
||||
"解决方案。"
|
||||
|
||||
msgid ""
|
||||
"Depending on the selected design, Networking itself might not even support "
|
||||
"the required <glossterm baseform=\"Layer-3 network\">layer-3 network</"
|
||||
@ -3098,38 +3052,6 @@ msgstr ""
|
||||
"类型的负载变得可能。这将改变单栈情景下的地址计划的需求，并且，过渡性的 IPv6 "
|
||||
"部署也能够减少对于 IPv4 地址的需求。"
|
||||
|
||||
msgid ""
|
||||
"As of the Icehouse release, OpenStack has limited support for dynamic "
|
||||
"routing, however there are a number of options available by incorporating "
|
||||
"third party solutions to implement routing within the cloud including "
|
||||
"network equipment, hardware nodes, and instances. Some workloads will "
|
||||
"perform well with nothing more than static routes and default gateways "
|
||||
"configured at the layer-3 termination point. In most cases this will "
|
||||
"suffice, however some cases require the addition of at least one type of "
|
||||
"dynamic routing protocol if not multiple protocols. Having a form of "
|
||||
"interior gateway protocol (IGP) available to the instances inside an "
|
||||
"OpenStack installation opens up the possibility of use cases for anycast "
|
||||
"route injection for services that need to use it as a geographic location or "
|
||||
"failover mechanism. Other applications may wish to directly participate in a "
|
||||
"routing protocol, either as a passive observer as in the case of a looking "
|
||||
"glass, or as an active participant in the form of a route reflector. Since "
|
||||
"an instance might have a large amount of compute and memory resources, it is "
|
||||
"trivial to hold an entire unpartitioned routing table and use it to provide "
|
||||
"services such as network path visibility to other applications or as a "
|
||||
"monitoring tool."
|
||||
msgstr ""
|
||||
"直到 Icehouse 版本的发布，OpenStack 对于动态路由的支持都很有限。然而，通过集"
|
||||
"成第三方的解决方案，包括网络设备、硬件节点以及实例，有很多的选择可以在云中实"
|
||||
"现路由。有一些类型的负载只需要在三层网络的终结点处设置好静态路由和默认的网关"
|
||||
"的情况下就可以很好地工作了。大多数情况下这是足够的，但是有些使用场景却需要至"
|
||||
"少一种动态路由协议的使用，如果不是要求多种协议同时使用的话。在一个 OpenStack "
|
||||
"部署中，使得某种内部网关协议(IGP)对于实例可用，能够让服务使用单播路由注入作为"
|
||||
"地理位置或者故障转移机制成为可能。其它的应用则可能直接参与到路由协议之中，作"
|
||||
"为一个类似 looking glass 一样的被动的观察者，或者作为一个路由反射器这样的主动"
|
||||
"参与者。由于一个实例可能具有大量的计算和内存资源，存放整个未分区的路由表并使"
|
||||
"用它来提供类似于给其它应用使用的网络路径可见性，或者监控工具等的服务，并不会"
|
||||
"是什么大问题。"
|
||||
|
||||
msgid ""
|
||||
"Path maximum transmission unit (MTU) failures are lesser known but harder to "
|
||||
"diagnose. The MTU must be large enough to handle normal traffic, overhead "
|
||||
|
||||
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-04-29 02:39+0000\n"
|
||||
"PO-Revision-Date: 2015-04-28 23:51+0000\n"
|
||||
"POT-Creation-Date: 2015-04-30 05:50+0000\n"
|
||||
"PO-Revision-Date: 2015-04-30 05:48+0000\n"
|
||||
"Last-Translator: openstackjenkins <jenkins@openstack.org>\n"
|
||||
"Language-Team: French (http://www.transifex.com/projects/p/openstack-manuals-"
|
||||
"i18n/language/fr/)\n"
|
||||
@ -1537,8 +1537,8 @@ msgstr "Orchestration"
|
||||
msgid "Telemetry"
|
||||
msgstr "Métrologie"
|
||||
|
||||
msgid "Data Processing"
|
||||
msgstr "Traitement des données en cours"
|
||||
msgid "Data processing service"
|
||||
msgstr "Service de traitement des données"
|
||||
|
||||
msgid "Logical architecture"
|
||||
msgstr "Architecture du logiciel"
|
||||
@ -1676,9 +1676,6 @@ msgstr "evacuated_server_name"
|
||||
msgid "host_b"
|
||||
msgstr "host_b"
|
||||
|
||||
msgid "Data processing service"
|
||||
msgstr "Service de traitement des données"
|
||||
|
||||
msgid "OpenStack Block Storage"
|
||||
msgstr "Stockage par Bloc d'OpenStack"
|
||||
|
||||
@ -2759,6 +2756,12 @@ msgstr ""
|
||||
msgid "[clients]"
|
||||
msgstr "[clients]"
|
||||
|
||||
msgid "localhost"
|
||||
msgstr "localhost"
|
||||
|
||||
msgid "2"
|
||||
msgstr "2"
|
||||
|
||||
msgid "[percona]"
|
||||
msgstr "[percona]"
|
||||
|
||||
@ -2771,9 +2774,6 @@ msgstr "[policy]"
|
||||
msgid "3"
|
||||
msgstr "3"
|
||||
|
||||
msgid "2"
|
||||
msgstr "2"
|
||||
|
||||
msgid "5"
|
||||
msgstr "5"
|
||||
|
||||
@ -2792,9 +2792,6 @@ msgstr "true"
|
||||
msgid "swift"
|
||||
msgstr "swift"
|
||||
|
||||
msgid "localhost"
|
||||
msgstr "localhost"
|
||||
|
||||
msgid "1024"
|
||||
msgstr "1024"
|
||||
|
||||
|
||||
@ -7,8 +7,8 @@
|
||||
msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: OpenStack Manuals\n"
|
||||
"POT-Creation-Date: 2015-04-29 02:39+0000\n"
|
||||
"PO-Revision-Date: 2015-04-29 00:12+0000\n"
|
||||
"POT-Creation-Date: 2015-04-30 05:50+0000\n"
|
||||
"PO-Revision-Date: 2015-04-30 05:48+0000\n"
|
||||
"Last-Translator: openstackjenkins <jenkins@openstack.org>\n"
|
||||
"Language-Team: Japanese (http://www.transifex.com/projects/p/openstack-"
|
||||
"manuals-i18n/language/ja/)\n"
|
||||
@ -811,6 +811,9 @@ msgstr "Configuration Reference"
|
||||
msgid "Operations Guide"
|
||||
msgstr "Operations Guide"
|
||||
|
||||
msgid "Networking Guide"
|
||||
msgstr "ネットワークガイド"
|
||||
|
||||
msgid "High Availability Guide"
|
||||
msgstr "High Availability Guide"
|
||||
|
||||
@ -1726,9 +1729,6 @@ msgstr "python-ceilometerclient"
|
||||
msgid "Create and collect measurements across OpenStack."
|
||||
msgstr "OpenStack 全体の測定項目を作成、収集します。"
|
||||
|
||||
msgid "Data Processing"
|
||||
msgstr "データ処理"
|
||||
|
||||
msgid "Creates and manages Hadoop clusters on OpenStack."
|
||||
msgstr "OpenStack に Hadoop クラスターを作成、管理します。"
|
||||
|
||||
@ -4199,9 +4199,6 @@ msgstr "443"
|
||||
msgid "300"
|
||||
msgstr "300"
|
||||
|
||||
msgid "(IntOpt) Size of RPC connection pool."
|
||||
msgstr "(整数オプション) RPC 接続プールの容量。"
|
||||
|
||||
msgid "60"
|
||||
msgstr "60"
|
||||
|
||||
@ -4211,6 +4208,27 @@ msgstr "64"
|
||||
msgid "(IntOpt) Size of RPC thread pool."
|
||||
msgstr "(整数オプション) RPC スレッド・プールの容量。"
|
||||
|
||||
msgid "localhost"
|
||||
msgstr "localhost"
|
||||
|
||||
msgid "5672"
|
||||
msgstr "5672"
|
||||
|
||||
msgid "(IntOpt) Size of RPC connection pool."
|
||||
msgstr "(整数オプション) RPC 接続プールの容量。"
|
||||
|
||||
msgid "2"
|
||||
msgstr "2"
|
||||
|
||||
msgid "1.0"
|
||||
msgstr "1.0"
|
||||
|
||||
msgid "guest"
|
||||
msgstr "guest"
|
||||
|
||||
msgid "/"
|
||||
msgstr "/"
|
||||
|
||||
msgid "127.0.0.1"
|
||||
msgstr "127.0.0.1"
|
||||
|
||||
@ -4223,9 +4241,6 @@ msgstr "admin"
|
||||
msgid "3"
|
||||
msgstr "3"
|
||||
|
||||
msgid "2"
|
||||
msgstr "2"
|
||||
|
||||
msgid "5"
|
||||
msgstr "5"
|
||||
|
||||
@ -4271,12 +4286,6 @@ msgstr "true"
|
||||
msgid "swift"
|
||||
msgstr "swift"
|
||||
|
||||
msgid "1.0"
|
||||
msgstr "1.0"
|
||||
|
||||
msgid "localhost"
|
||||
msgstr "localhost"
|
||||
|
||||
msgid "1024"
|
||||
msgstr "1024"
|
||||
|
||||
@ -4295,9 +4304,6 @@ msgstr "zaqar"
|
||||
msgid "neutron"
|
||||
msgstr "neutron"
|
||||
|
||||
msgid "5672"
|
||||
msgstr "5672"
|
||||
|
||||
msgid "22"
|
||||
msgstr "22"
|
||||
|
||||
@ -4331,12 +4337,6 @@ msgstr "8"
|
||||
msgid "2048"
|
||||
msgstr "2048"
|
||||
|
||||
msgid "guest"
|
||||
msgstr "guest"
|
||||
|
||||
msgid "/"
|
||||
msgstr "/"
|
||||
|
||||
msgid "10000"
|
||||
msgstr "10000"
|
||||
|
||||
@ -4465,11 +4465,8 @@ msgstr "eventlet"
|
||||
msgid "16384"
|
||||
msgstr "16384"
|
||||
|
||||
msgid "75"
|
||||
msgstr "75"
|
||||
|
||||
msgid "500"
|
||||
msgstr "500"
|
||||
msgid "vlan"
|
||||
msgstr "vlan"
|
||||
|
||||
msgid "on"
|
||||
msgstr "の"
|
||||
@ -4694,6 +4691,15 @@ msgstr "ロール"
|
||||
msgid "6002"
|
||||
msgstr "6002"
|
||||
|
||||
msgid "75"
|
||||
msgstr "75"
|
||||
|
||||
msgid "500"
|
||||
msgstr "500"
|
||||
|
||||
msgid "networks"
|
||||
msgstr "ネットワーク"
|
||||
|
||||
msgid "(StrOpt) The driver used to manage the virtual interface."
|
||||
msgstr ""
|
||||
"(文字列オプション) 仮想インターフェースを管理するために使用するドライバー。"
|
||||
|
||||
@ -11,8 +11,8 @@
|
||||
msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: OpenStack Manuals\n"
|
||||
"POT-Creation-Date: 2015-04-29 02:39+0000\n"
|
||||
"PO-Revision-Date: 2015-04-29 00:12+0000\n"
|
||||
"POT-Creation-Date: 2015-04-30 05:50+0000\n"
|
||||
"PO-Revision-Date: 2015-04-30 05:48+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"
|
||||
@ -855,17 +855,6 @@ msgid ""
|
||||
"associated components:"
|
||||
msgstr "以下书籍解释了如何安装一个基于OpenStack云及其相关的组件"
|
||||
|
||||
msgid ""
|
||||
"Installation Guide for openSUSE 13.1 and SUSE Linux Enterprise Server 11 SP3"
|
||||
msgstr "基于openSUSE 13.1 或 SUSE Linux Enterprise Server 11 SP3的安装向导"
|
||||
|
||||
msgid ""
|
||||
"Installation Guide for Red Hat Enterprise Linux 7, CentOS 7, and Fedora 20"
|
||||
msgstr "基于Red Hat Enterprise Linux 7, CentOS 7, 以及 Fedora 20的安装向导"
|
||||
|
||||
msgid "Installation Guide for Ubuntu 14.04"
|
||||
msgstr "基于Ubuntu 14.04的安装向导"
|
||||
|
||||
msgid ""
|
||||
"The following books explain how to configure and run an OpenStack cloud:"
|
||||
msgstr "以下书籍解释了如何配置和运行一个基于OpenStack的云："
|
||||
@ -1509,8 +1498,8 @@ msgstr "Orchestration"
|
||||
msgid "Telemetry"
|
||||
msgstr "Telemetry"
|
||||
|
||||
msgid "Data Processing"
|
||||
msgstr "数据处理"
|
||||
msgid "Data processing service"
|
||||
msgstr "数据处理服务"
|
||||
|
||||
#. When image changes, this message will be marked fuzzy or untranslated for
|
||||
#. you.
|
||||
@ -1658,9 +1647,6 @@ msgstr "evacuated_server_name"
|
||||
msgid "host_b"
|
||||
msgstr "host_b"
|
||||
|
||||
msgid "Data processing service"
|
||||
msgstr "数据处理服务"
|
||||
|
||||
msgid ""
|
||||
"The Data processing service for OpenStack (sahara) aims to provide users "
|
||||
"with a simple means to provision data processing (Hadoop, Spark) clusters by "
|
||||
@ -2693,9 +2679,6 @@ msgstr ""
|
||||
"提供可扩展和稳定的云数据库即服务的功能，可同时支持关系性和非关系性数据库引"
|
||||
"擎。"
|
||||
|
||||
msgid "Data Processing Service"
|
||||
msgstr "数据处理服务"
|
||||
|
||||
msgid "Sahara"
|
||||
msgstr "Sahara"
|
||||
|
||||
@ -3319,6 +3302,9 @@ msgstr "基于Intel的处理器"
|
||||
msgid "None"
|
||||
msgstr "无"
|
||||
|
||||
msgid "-1"
|
||||
msgstr "-1"
|
||||
|
||||
msgid "0"
|
||||
msgstr "0"
|
||||
|
||||
@ -3340,9 +3326,6 @@ msgstr "10"
|
||||
msgid "1"
|
||||
msgstr "1"
|
||||
|
||||
msgid "-1"
|
||||
msgstr "-1"
|
||||
|
||||
msgid "3600"
|
||||
msgstr "3600"
|
||||
|
||||
@ -3388,6 +3371,24 @@ msgstr "60"
|
||||
msgid "64"
|
||||
msgstr "64"
|
||||
|
||||
msgid "$qpid_hostname:$qpid_port"
|
||||
msgstr "$qpid_hostname:$qpid_port"
|
||||
|
||||
msgid "5672"
|
||||
msgstr "5672"
|
||||
|
||||
msgid "2"
|
||||
msgstr "2"
|
||||
|
||||
msgid "$rabbit_host:$rabbit_port"
|
||||
msgstr "$rabbit_host:$rabbit_port"
|
||||
|
||||
msgid "guest"
|
||||
msgstr "客户机"
|
||||
|
||||
msgid "/"
|
||||
msgstr "/"
|
||||
|
||||
msgid "trove.guestagent.strategies.backup.mysql_impl"
|
||||
msgstr "trove.guestagent.strategies.backup.mysql_impl"
|
||||
|
||||
@ -3436,9 +3437,6 @@ msgstr "35357"
|
||||
msgid "3"
|
||||
msgstr "3"
|
||||
|
||||
msgid "2"
|
||||
msgstr "2"
|
||||
|
||||
msgid "720"
|
||||
msgstr "720"
|
||||
|
||||
@ -3457,12 +3455,6 @@ msgstr "swift"
|
||||
msgid "neutron"
|
||||
msgstr "neutron"
|
||||
|
||||
msgid "$qpid_hostname:$qpid_port"
|
||||
msgstr "$qpid_hostname:$qpid_port"
|
||||
|
||||
msgid "5672"
|
||||
msgstr "5672"
|
||||
|
||||
msgid "[BRCD_FABRIC_EXAMPLE]"
|
||||
msgstr "[BRCD_FABRIC_EXAMPLE]"
|
||||
|
||||
@ -3498,48 +3490,9 @@ msgstr "/opt/stack/data/neutron/cisco/config_drive"
|
||||
msgid "[hosting_devices]"
|
||||
msgstr "[hosting_devices]"
|
||||
|
||||
msgid ""
|
||||
"neutron.plugins.cisco.cfg_agent.device_drivers.csr1kv.csr1kv_routing_driver."
|
||||
"CSR1kvRoutingDriver"
|
||||
msgstr ""
|
||||
"neutron.plugins.cisco.cfg_agent.device_drivers.csr1kv.csr1kv_routing_driver."
|
||||
"CSR1kvRoutingDriver"
|
||||
|
||||
msgid "csr1kv_cfg_template"
|
||||
msgstr "csr1kv_cfg_template"
|
||||
|
||||
msgid ""
|
||||
"neutron.plugins.cisco.l3.hosting_device_drivers.csr1kv_hd_driver."
|
||||
"CSR1kvHostingDeviceDriver"
|
||||
msgstr ""
|
||||
"neutron.plugins.cisco.l3.hosting_device_drivers.csr1kv_hd_driver."
|
||||
"CSR1kvHostingDeviceDriver"
|
||||
|
||||
msgid "csr1kv_openstack_img"
|
||||
msgstr "csr1kv_openstack_img"
|
||||
|
||||
msgid ""
|
||||
"neutron.plugins.cisco.l3.plugging_drivers.n1kv_trunking_driver."
|
||||
"N1kvTrunkingPlugDriver"
|
||||
msgstr ""
|
||||
"neutron.plugins.cisco.l3.plugging_drivers.n1kv_trunking_driver."
|
||||
"N1kvTrunkingPlugDriver"
|
||||
|
||||
msgid "osn_mgmt_pp"
|
||||
msgstr "osn_mgmt_pp"
|
||||
|
||||
msgid "osn_t1_np"
|
||||
msgstr "osn_t1_np"
|
||||
|
||||
msgid "osn_t1_pp"
|
||||
msgstr "osn_t1_pp"
|
||||
|
||||
msgid "osn_t2_np"
|
||||
msgstr "osn_t2_np"
|
||||
|
||||
msgid "osn_t2_pp"
|
||||
msgstr "osn_t2_pp"
|
||||
|
||||
msgid ""
|
||||
"nova.api.ec2.cloud:nova.notifications.notify_decorator, nova.compute.api:"
|
||||
"nova.notifications.notify_decorator"
|
||||
@ -3590,15 +3543,6 @@ msgstr "LOG_USER"
|
||||
msgid "heat.common.heat_keystoneclient.KeystoneClientV3"
|
||||
msgstr "heat.common.heat_keystoneclient.KeystoneClientV3"
|
||||
|
||||
msgid "$rabbit_host:$rabbit_port"
|
||||
msgstr "$rabbit_host:$rabbit_port"
|
||||
|
||||
msgid "guest"
|
||||
msgstr "客户机"
|
||||
|
||||
msgid "/"
|
||||
msgstr "/"
|
||||
|
||||
msgid "http://127.0.0.1:6080/vnc_auto.html"
|
||||
msgstr "http://127.0.0.1:6080/vnc_auto.html"
|
||||
|
||||
@ -3705,6 +3649,9 @@ msgstr "无"
|
||||
msgid "openstack"
|
||||
msgstr "openstack"
|
||||
|
||||
msgid "[ml2_cisco]"
|
||||
msgstr "[ml2_cisco]"
|
||||
|
||||
msgid "[ml2_cisco_apic]"
|
||||
msgstr "[ml2_cisco_apic]"
|
||||
|
||||
@ -3840,6 +3787,9 @@ msgstr "cinder"
|
||||
msgid "Option"
|
||||
msgstr "选项"
|
||||
|
||||
msgid "[DEFAULT] default_log_levels"
|
||||
msgstr "[DEFAULT] default_log_levels"
|
||||
|
||||
msgid "[DEFAULT] rpc_zmq_matchmaker"
|
||||
msgstr "[DEFAULT] rpc_zmq_matchmaker"
|
||||
|
||||
@ -3849,29 +3799,41 @@ msgstr "oslo.messaging._drivers.matchmaker.MatchMakerLocalhost"
|
||||
msgid "100"
|
||||
msgstr "100"
|
||||
|
||||
msgid "[database] db_inc_retry_interval = True"
|
||||
msgstr "[database] db_inc_retry_interval = True"
|
||||
|
||||
msgid "[database] db_max_retries = 20"
|
||||
msgstr "[database] db_max_retries = 20"
|
||||
|
||||
msgid "[database] db_max_retry_interval = 10"
|
||||
msgstr "[database] db_max_retry_interval = 10"
|
||||
|
||||
msgid "[database] db_retry_interval = 1"
|
||||
msgstr "[database] db_retry_interval = 1"
|
||||
|
||||
msgid "[database] mysql_sql_mode = TRADITIONAL"
|
||||
msgstr "[database] mysql_sql_mode = TRADITIONAL"
|
||||
|
||||
msgid "[database] slave_connection = None"
|
||||
msgstr "[database] slave_connection = None"
|
||||
|
||||
msgid "[database] sqlite_db = oslo.sqlite"
|
||||
msgstr "[database] sqlite_db = oslo.sqlite"
|
||||
|
||||
msgid "[database] sqlite_synchronous = True"
|
||||
msgstr "[database] sqlite_synchronous = True"
|
||||
|
||||
msgid "[database] use_db_reconnect = False"
|
||||
msgstr "[database] use_db_reconnect = False"
|
||||
|
||||
msgid "[heat_api_cfn]"
|
||||
msgstr "[heat_api_cfn]"
|
||||
|
||||
msgid "8000"
|
||||
msgstr "8000"
|
||||
|
||||
msgid "75"
|
||||
msgstr "75"
|
||||
|
||||
msgid "[NSX_DHCP]"
|
||||
msgstr "[NSX_DHCP]"
|
||||
|
||||
msgid "[NSX_LSN]"
|
||||
msgstr "[NSX_LSN]"
|
||||
|
||||
msgid "[NSX_METADATA]"
|
||||
msgstr "[NSX_METADATA]"
|
||||
|
||||
msgid "[NSX_SYNC]"
|
||||
msgstr "[NSX_SYNC]"
|
||||
|
||||
msgid "500"
|
||||
msgstr "500"
|
||||
msgid "vlan"
|
||||
msgstr "vlan"
|
||||
|
||||
msgid "on"
|
||||
msgstr "on"
|
||||
@ -3885,8 +3847,26 @@ msgstr "9191"
|
||||
msgid "network"
|
||||
msgstr "网络"
|
||||
|
||||
msgid "[DEFAULT] default_log_levels"
|
||||
msgstr "[DEFAULT] default_log_levels"
|
||||
msgid ""
|
||||
"neutron.plugins.cisco.cfg_agent.device_drivers.csr1kv.csr1kv_routing_driver."
|
||||
"CSR1kvRoutingDriver"
|
||||
msgstr ""
|
||||
"neutron.plugins.cisco.cfg_agent.device_drivers.csr1kv.csr1kv_routing_driver."
|
||||
"CSR1kvRoutingDriver"
|
||||
|
||||
msgid ""
|
||||
"neutron.plugins.cisco.l3.hosting_device_drivers.csr1kv_hd_driver."
|
||||
"CSR1kvHostingDeviceDriver"
|
||||
msgstr ""
|
||||
"neutron.plugins.cisco.l3.hosting_device_drivers.csr1kv_hd_driver."
|
||||
"CSR1kvHostingDeviceDriver"
|
||||
|
||||
msgid ""
|
||||
"neutron.plugins.cisco.l3.plugging_drivers.n1kv_trunking_driver."
|
||||
"N1kvTrunkingPlugDriver"
|
||||
msgstr ""
|
||||
"neutron.plugins.cisco.l3.plugging_drivers.n1kv_trunking_driver."
|
||||
"N1kvTrunkingPlugDriver"
|
||||
|
||||
msgid "compute"
|
||||
msgstr "compute"
|
||||
@ -4155,12 +4135,30 @@ msgstr "8003"
|
||||
msgid "ext4"
|
||||
msgstr "ext4"
|
||||
|
||||
msgid "8088"
|
||||
msgstr "8088"
|
||||
|
||||
msgid "tcp://127.0.0.1:60001"
|
||||
msgstr "tcp://127.0.0.1:60001"
|
||||
|
||||
msgid "3000"
|
||||
msgstr "3000"
|
||||
|
||||
msgid "Member"
|
||||
msgstr "成员"
|
||||
|
||||
msgid "sha1"
|
||||
msgstr "sha1"
|
||||
|
||||
msgid "75"
|
||||
msgstr "75"
|
||||
|
||||
msgid "[NSX_SYNC]"
|
||||
msgstr "[NSX_SYNC]"
|
||||
|
||||
msgid "500"
|
||||
msgstr "500"
|
||||
|
||||
msgid "6081"
|
||||
msgstr "6081"
|
||||
|
||||
@ -4173,12 +4171,6 @@ msgstr "[DEFAULT] db_backend"
|
||||
msgid "$instances_path/snapshots"
|
||||
msgstr "$instances_path/snapshots"
|
||||
|
||||
msgid "tcp://127.0.0.1:60001"
|
||||
msgstr "tcp://127.0.0.1:60001"
|
||||
|
||||
msgid "3000"
|
||||
msgstr "3000"
|
||||
|
||||
msgid ""
|
||||
"cinder.zonemanager.drivers.brocade.brcd_fc_zone_client_cli."
|
||||
"BrcdFCZoneClientCLI"
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: PACKAGE VERSION\n"
|
||||
"POT-Creation-Date: 2015-04-28 06:08+0000\n"
|
||||
"POT-Creation-Date: 2015-04-30 06:07+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"
|
||||
@ -321,95 +321,97 @@ msgstr ""
|
||||
msgid "While the old syntax is still supported, we recommend using the newer, more intuitive syntax."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/bk-config-ref.xml:8(title) ./doc/config-reference/bk-config-ref.xml:13(titleabbrev)
|
||||
#. - TODO(jaegerandi) Add back to the above once Kilo has branched:
|
||||
#. status="draft">
|
||||
#: ./doc/config-reference/bk-config-ref.xml:10(title) ./doc/config-reference/bk-config-ref.xml:15(titleabbrev)
|
||||
msgid "OpenStack Configuration Reference"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/bk-config-ref.xml:21(orgname) ./doc/config-reference/bk-config-ref.xml:28(holder)
|
||||
#: ./doc/config-reference/bk-config-ref.xml:23(orgname) ./doc/config-reference/bk-config-ref.xml:30(holder)
|
||||
msgid "OpenStack Foundation"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/bk-config-ref.xml:25(year)
|
||||
#: ./doc/config-reference/bk-config-ref.xml:27(year)
|
||||
msgid "2013"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/bk-config-ref.xml:26(year)
|
||||
#: ./doc/config-reference/bk-config-ref.xml:28(year)
|
||||
msgid "2014"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/bk-config-ref.xml:27(year)
|
||||
#: ./doc/config-reference/bk-config-ref.xml:29(year)
|
||||
msgid "2015"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/bk-config-ref.xml:30(productname)
|
||||
#: ./doc/config-reference/bk-config-ref.xml:32(productname)
|
||||
msgid "OpenStack"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/bk-config-ref.xml:31(releaseinfo)
|
||||
#: ./doc/config-reference/bk-config-ref.xml:33(releaseinfo)
|
||||
msgid "kilo"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/bk-config-ref.xml:35(remark)
|
||||
#: ./doc/config-reference/bk-config-ref.xml:37(remark)
|
||||
msgid "Copyright details are filled in by the template."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/bk-config-ref.xml:40(para)
|
||||
#: ./doc/config-reference/bk-config-ref.xml:42(para)
|
||||
msgid "This document is for system administrators who want to look up configuration options. It contains lists of configuration options available with OpenStack and uses auto-generation to generate options and the descriptions from the code for each project. It includes sample configuration files."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/bk-config-ref.xml:50(date)
|
||||
#: ./doc/config-reference/bk-config-ref.xml:52(date)
|
||||
msgid "2014-10-15"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/bk-config-ref.xml:54(para)
|
||||
#: ./doc/config-reference/bk-config-ref.xml:56(para)
|
||||
msgid "Updates for Juno: updated all configuration tables, include sample configuration files, add chapter for Data processing service, update and enhance driver configuration."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/bk-config-ref.xml:65(date)
|
||||
#: ./doc/config-reference/bk-config-ref.xml:67(date)
|
||||
msgid "2014-04-16"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/bk-config-ref.xml:69(para)
|
||||
#: ./doc/config-reference/bk-config-ref.xml:71(para)
|
||||
msgid "Update for Icehouse: Updated all configuration tables, include sample configuration files, add chapters for Database service, Orchestration, and Telemetry."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/bk-config-ref.xml:80(date)
|
||||
#: ./doc/config-reference/bk-config-ref.xml:82(date)
|
||||
msgid "2014-03-11"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/bk-config-ref.xml:84(para)
|
||||
#: ./doc/config-reference/bk-config-ref.xml:86(para)
|
||||
msgid "Sorted component listing. Moved procedures to the <link href=\"http://docs.openstack.org/admin-guide-cloud/content/\"><citetitle>Cloud Administrator Guide</citetitle></link>"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/bk-config-ref.xml:93(date)
|
||||
#: ./doc/config-reference/bk-config-ref.xml:95(date)
|
||||
msgid "2014-01-09"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/bk-config-ref.xml:97(para)
|
||||
#: ./doc/config-reference/bk-config-ref.xml:99(para)
|
||||
msgid "Removes content addressed in installation, merges duplicated content, and revises legacy references."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/bk-config-ref.xml:106(date)
|
||||
#: ./doc/config-reference/bk-config-ref.xml:108(date)
|
||||
msgid "2013-10-17"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/bk-config-ref.xml:110(para)
|
||||
#: ./doc/config-reference/bk-config-ref.xml:112(para)
|
||||
msgid "Havana release."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/bk-config-ref.xml:116(date)
|
||||
#: ./doc/config-reference/bk-config-ref.xml:118(date)
|
||||
msgid "2013-08-16"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/bk-config-ref.xml:120(para)
|
||||
#: ./doc/config-reference/bk-config-ref.xml:122(para)
|
||||
msgid "Moves Block Storage driver configuration information from the <citetitle>Block Storage Administration Guide</citetitle> to this reference."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/bk-config-ref.xml:130(date)
|
||||
#: ./doc/config-reference/bk-config-ref.xml:132(date)
|
||||
msgid "2013-06-10"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/bk-config-ref.xml:134(para)
|
||||
#: ./doc/config-reference/bk-config-ref.xml:136(para)
|
||||
msgid "Initial creation of Configuration Reference."
|
||||
msgstr ""
|
||||
|
||||
@ -585,7 +587,7 @@ msgstr ""
|
||||
msgid "Find an example object server configuration at <filename>etc/object-server.conf-sample</filename> in the source code repository."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/ch_objectstorageconfigure.xml:22(para) ./doc/config-reference/ch_objectstorageconfigure.xml:51(para) ./doc/config-reference/ch_objectstorageconfigure.xml:76(para) ./doc/config-reference/ch_objectstorageconfigure.xml:109(para) ./doc/config-reference/ch_objectstorageconfigure.xml:126(para) ./doc/config-reference/ch_objectstorageconfigure.xml:153(para) ./doc/config-reference/ch_objectstorageconfigure.xml:182(para) ./doc/config-reference/ch_objectstorageconfigure.xml:225(para) ./doc/config-reference/ch_objectstorageconfigure.xml:234(para)
|
||||
#: ./doc/config-reference/ch_objectstorageconfigure.xml:22(para) ./doc/config-reference/ch_objectstorageconfigure.xml:51(para) ./doc/config-reference/ch_objectstorageconfigure.xml:76(para) ./doc/config-reference/ch_objectstorageconfigure.xml:109(para) ./doc/config-reference/ch_objectstorageconfigure.xml:126(para) ./doc/config-reference/ch_objectstorageconfigure.xml:152(para) ./doc/config-reference/ch_objectstorageconfigure.xml:181(para) ./doc/config-reference/ch_objectstorageconfigure.xml:224(para) ./doc/config-reference/ch_objectstorageconfigure.xml:233(para)
|
||||
msgid "The available configuration options are:"
|
||||
msgstr ""
|
||||
|
||||
@ -641,43 +643,43 @@ msgstr ""
|
||||
msgid "Sample container sync reconciler configuration file"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/ch_objectstorageconfigure.xml:149(title)
|
||||
#: ./doc/config-reference/ch_objectstorageconfigure.xml:148(title)
|
||||
msgid "Account server configuration"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/ch_objectstorageconfigure.xml:150(para)
|
||||
#: ./doc/config-reference/ch_objectstorageconfigure.xml:149(para)
|
||||
msgid "Find an example account server configuration at <filename>etc/account-server.conf-sample</filename> in the source code repository."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/ch_objectstorageconfigure.xml:173(title)
|
||||
#: ./doc/config-reference/ch_objectstorageconfigure.xml:172(title)
|
||||
msgid "Sample account server configuration file"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/ch_objectstorageconfigure.xml:178(title)
|
||||
#: ./doc/config-reference/ch_objectstorageconfigure.xml:177(title)
|
||||
msgid "Proxy server configuration"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/ch_objectstorageconfigure.xml:179(para)
|
||||
#: ./doc/config-reference/ch_objectstorageconfigure.xml:178(para)
|
||||
msgid "Find an example proxy server configuration at <filename>etc/proxy-server.conf-sample</filename> in the source code repository."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/ch_objectstorageconfigure.xml:216(title)
|
||||
#: ./doc/config-reference/ch_objectstorageconfigure.xml:215(title)
|
||||
msgid "Sample proxy server configuration file"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/ch_objectstorageconfigure.xml:221(title)
|
||||
#: ./doc/config-reference/ch_objectstorageconfigure.xml:220(title)
|
||||
msgid "Proxy server memcache configuration"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/ch_objectstorageconfigure.xml:222(para)
|
||||
#: ./doc/config-reference/ch_objectstorageconfigure.xml:221(para)
|
||||
msgid "Find an example memcache configuration for the proxy server at <filename>etc/memcache.conf-sample</filename> in the source code repository."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/ch_objectstorageconfigure.xml:230(title)
|
||||
#: ./doc/config-reference/ch_objectstorageconfigure.xml:229(title)
|
||||
msgid "Rsyncd configuration"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/ch_objectstorageconfigure.xml:231(para)
|
||||
#: ./doc/config-reference/ch_objectstorageconfigure.xml:230(para)
|
||||
msgid "Find an example rsyncd configuration at <filename>etc/rsyncd.conf-sample</filename> in the source code repository."
|
||||
msgstr ""
|
||||
|
||||
@ -1162,74 +1164,82 @@ msgid "Use the following options in the <filename>metering_agent.ini</filename>
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/networking/section_networking-options-reference.xml:121(title)
|
||||
msgid "Policy"
|
||||
msgid "Nova"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/networking/section_networking-options-reference.xml:122(para)
|
||||
msgid "Use the following options in the <filename>neutron.conf</filename> file to change policy settings."
|
||||
msgid "Use the following options in the <filename>neutron.conf</filename> file to change nova-related settings."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/networking/section_networking-options-reference.xml:128(title)
|
||||
msgid "Quotas"
|
||||
msgid "Policy"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/networking/section_networking-options-reference.xml:129(para)
|
||||
msgid "Use the following options in the <filename>neutron.conf</filename> file for the quota system."
|
||||
msgid "Use the following options in the <filename>neutron.conf</filename> file to change policy settings."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/networking/section_networking-options-reference.xml:135(title)
|
||||
msgid "Rootwrap"
|
||||
msgid "Quotas"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/networking/section_networking-options-reference.xml:136(para)
|
||||
msgid "Use the following options in the <filename>neutron.conf</filename> file for the rootwrap settings"
|
||||
msgid "Use the following options in the <filename>neutron.conf</filename> file for the quota system."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/networking/section_networking-options-reference.xml:142(title)
|
||||
msgid "Scheduler"
|
||||
msgid "Rootwrap"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/networking/section_networking-options-reference.xml:143(para)
|
||||
msgid "Use the following options in the <filename>neutron.conf</filename> file to change scheduler settings."
|
||||
msgid "Use the following options in the <filename>neutron.conf</filename> file for the rootwrap settings"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/networking/section_networking-options-reference.xml:149(title)
|
||||
msgid "Security Groups"
|
||||
msgid "Scheduler"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/networking/section_networking-options-reference.xml:150(para)
|
||||
msgid "Use the following options in the <filename>neutron.conf</filename> file to change scheduler settings."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/networking/section_networking-options-reference.xml:156(title)
|
||||
msgid "Security Groups"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/networking/section_networking-options-reference.xml:157(para)
|
||||
msgid "Use the following options in the configuration file for your driver to change security group settings."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/networking/section_networking-options-reference.xml:154(para)
|
||||
#: ./doc/config-reference/networking/section_networking-options-reference.xml:161(para)
|
||||
msgid "Now Networking uses iptables to achieve security group functions. In L2 agent with <placeholder-1/> option enabled, it makes use of IPset to improve security group's performance, as it represents a hash set which is insensitive to the number of elements."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/networking/section_networking-options-reference.xml:158(para)
|
||||
#: ./doc/config-reference/networking/section_networking-options-reference.xml:165(para)
|
||||
msgid "When a port is created, L2 agent will add an additional IPset chain to it's iptables chain, if the security group that this port belongs to has rules between other security group, the member of that security group will be added to the ipset chain."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/networking/section_networking-options-reference.xml:162(para)
|
||||
#: ./doc/config-reference/networking/section_networking-options-reference.xml:169(para)
|
||||
msgid "If a member of a security group is changed, it used to reload iptables rules which is expensive. However, when IPset option is enabled on L2 agent, it does not need to reload iptables if only members of security group were changed, it should just update an IPset."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/networking/section_networking-options-reference.xml:168(para)
|
||||
#: ./doc/config-reference/networking/section_networking-options-reference.xml:175(para)
|
||||
msgid "A single default security group has been introduced in order to avoid race conditions when creating a tenant's default security group. The race conditions are caused by the uniqueness check of a new security group name. A table <literal>default_security_group</literal> implements such a group. It has <literal>tenant_id</literal> field as a primary key and <literal>security_group_id</literal>, which is an identifier of a default security group. The migration that introduces this table has a sanity check that verifies if a default security group is not duplicated in any tenant."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/networking/section_networking-options-reference.xml:181(title)
|
||||
#: ./doc/config-reference/networking/section_networking-options-reference.xml:188(title)
|
||||
msgid "SSL and Certification Authority"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/networking/section_networking-options-reference.xml:182(para)
|
||||
#: ./doc/config-reference/networking/section_networking-options-reference.xml:189(para)
|
||||
msgid "Use the following options in the <filename>neutron.conf</filename> file to enable SSL."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/networking/section_networking-options-reference.xml:188(title)
|
||||
#: ./doc/config-reference/networking/section_networking-options-reference.xml:195(title)
|
||||
msgid "Testing"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/networking/section_networking-options-reference.xml:189(para)
|
||||
#: ./doc/config-reference/networking/section_networking-options-reference.xml:196(para)
|
||||
msgid "Use the following options to alter testing-related features."
|
||||
msgstr ""
|
||||
|
||||
@ -1290,10 +1300,6 @@ msgid "l3_agent.ini"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/networking/section_networking-sample-configuration-files.xml:58(title)
|
||||
msgid "lbaas_agent.ini"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/networking/section_networking-sample-configuration-files.xml:64(title)
|
||||
msgid "metadata_agent.ini"
|
||||
msgstr ""
|
||||
|
||||
@ -1370,50 +1376,58 @@ msgid "IBM SDN-VE configuration options"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/networking/section_networking-plugins.xml:102(title)
|
||||
msgid "Layer 2 Gateway configuration options"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/networking/section_networking-plugins.xml:108(title)
|
||||
msgid "Linux bridge Agent configuration options"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/networking/section_networking-plugins.xml:109(title)
|
||||
#: ./doc/config-reference/networking/section_networking-plugins.xml:115(title)
|
||||
msgid "Meta Plug-in configuration options"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/networking/section_networking-plugins.xml:110(para)
|
||||
#: ./doc/config-reference/networking/section_networking-plugins.xml:116(para)
|
||||
msgid "The Meta Plug-in allows you to use multiple plug-ins at the same time."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/networking/section_networking-plugins.xml:118(title)
|
||||
#: ./doc/config-reference/networking/section_networking-plugins.xml:124(title)
|
||||
msgid "MidoNet configuration options"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/networking/section_networking-plugins.xml:124(title)
|
||||
#: ./doc/config-reference/networking/section_networking-plugins.xml:130(title)
|
||||
msgid "NEC configuration options"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/networking/section_networking-plugins.xml:130(title)
|
||||
#: ./doc/config-reference/networking/section_networking-plugins.xml:136(title)
|
||||
msgid "Nuage configuration options"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/networking/section_networking-plugins.xml:136(title)
|
||||
#: ./doc/config-reference/networking/section_networking-plugins.xml:142(title)
|
||||
msgid "One Convergence NVSD configuration options"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/networking/section_networking-plugins.xml:142(title)
|
||||
#: ./doc/config-reference/networking/section_networking-plugins.xml:148(title)
|
||||
msgid "OpenContrail configuration options"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/networking/section_networking-plugins.xml:148(title)
|
||||
#: ./doc/config-reference/networking/section_networking-plugins.xml:154(title)
|
||||
msgid "Open vSwitch Agent configuration options"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/networking/section_networking-plugins.xml:155(title)
|
||||
#: ./doc/config-reference/networking/section_networking-plugins.xml:161(title)
|
||||
msgid "PLUMgrid configuration options"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/networking/section_networking-plugins.xml:161(title)
|
||||
#: ./doc/config-reference/networking/section_networking-plugins.xml:167(title)
|
||||
msgid "SR-IOV configuration options"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/networking/section_networking-plugins.xml:167(title)
|
||||
#: ./doc/config-reference/networking/section_networking-plugins.xml:173(title)
|
||||
msgid "VMware vSphere configuration options"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/networking/section_networking-plugins.xml:179(title)
|
||||
msgid "VMware NSX configuration options"
|
||||
msgstr ""
|
||||
|
||||
|
||||
File diff suppressed because it is too large
Load Diff
@ -6,9 +6,9 @@
|
||||
msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: OpenStack Manuals\n"
|
||||
"POT-Creation-Date: 2015-04-24 04:26+0000\n"
|
||||
"PO-Revision-Date: 2015-04-22 18:05+0000\n"
|
||||
"Last-Translator: Ilya Alekseyev <ilyaalekseyev@acm.org>\n"
|
||||
"POT-Creation-Date: 2015-04-30 05:50+0000\n"
|
||||
"PO-Revision-Date: 2015-04-30 05:48+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"
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: PACKAGE VERSION\n"
|
||||
"POT-Creation-Date: 2015-04-28 06:08+0000\n"
|
||||
"POT-Creation-Date: 2015-04-30 06:07+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"
|
||||
@ -283,10 +283,6 @@ msgstr ""
|
||||
msgid "The packages already contain a cron job under <filename>/etc/cron.hourly/keystone</filename>, so it is not necessary to manually configure a periodic task that purges expired tokens."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/install-guide/section_keystone-install.xml:367(para)
|
||||
msgid "We recommend that you use <systemitem class=\"service\">cron</systemitem> to configure a periodic task that purges expired tokens hourly:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/install-guide/section_basics-database.xml:8(title)
|
||||
msgid "SQL database"
|
||||
msgstr ""
|
||||
@ -3800,7 +3796,7 @@ msgid "Add the Block Storage service"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/install-guide/ch_cinder.xml:8(para)
|
||||
msgid "The OpenStack Block Storage service provides block storage devices to guest instances. The method in which the storage is provisioned and consumed is determined by the Block Storage driver, or drivers in the case of a multi-backend configuration. There are a variety of drivers that are available: NAS/SAN, NFS, iSCSI, Ceph, and more. The Block Storage API and scheduler services typically run on the controller nodes. Depending upon the drivers used, the volume service can run on controllers, compute nodes, or standalone storage nodes. For more information, see the <link href=\"http://docs.openstack.org/juno/config-reference/content/section_volume-drivers.html\"><citetitle>Configuration Reference</citetitle></link>."
|
||||
msgid "The OpenStack Block Storage service provides block storage devices to guest instances. The method in which the storage is provisioned and consumed is determined by the Block Storage driver, or drivers in the case of a multi-backend configuration. There are a variety of drivers that are available: NAS/SAN, NFS, iSCSI, Ceph, and more. The Block Storage API and scheduler services typically run on the controller nodes. Depending upon the drivers used, the volume service can run on controllers, compute nodes, or standalone storage nodes. For more information, see the <link href=\"http://docs.openstack.org/kilo/config-reference/content/section_volume-drivers.html\"><citetitle>Configuration Reference</citetitle></link>."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/install-guide/ch_cinder.xml:20(para)
|
||||
@ -4534,163 +4530,165 @@ msgstr ""
|
||||
msgid "The Debian OpenStack packages offer automation for this, so OpenStack users do not have to manually edit the configuration files."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/install-guide/bk-openstack-install-guide.xml:8(title)
|
||||
#. TODO(jaegerandi) Add back to the above once Kilo has branched:
|
||||
#. status="draft">
|
||||
#: ./doc/install-guide/bk-openstack-install-guide.xml:10(title)
|
||||
msgid "OpenStack Installation Guide for <phrase os=\"rhel;centos;fedora\">Red Hat Enterprise Linux 7, CentOS 7, and Fedora 21</phrase><phrase os=\"ubuntu\">Ubuntu 14.04</phrase><phrase os=\"debian\">Debian 7</phrase><phrase os=\"opensuse\">openSUSE 13.2 and SUSE Linux Enterprise Server 12</phrase>"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/install-guide/bk-openstack-install-guide.xml:19(phrase)
|
||||
#: ./doc/install-guide/bk-openstack-install-guide.xml:21(phrase)
|
||||
msgid "Red Hat Enterprise Linux, CentOS, and Fedora"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/install-guide/bk-openstack-install-guide.xml:20(phrase)
|
||||
#: ./doc/install-guide/bk-openstack-install-guide.xml:22(phrase)
|
||||
msgid "Ubuntu 14.04"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/install-guide/bk-openstack-install-guide.xml:21(phrase)
|
||||
#: ./doc/install-guide/bk-openstack-install-guide.xml:23(phrase)
|
||||
msgid "openSUSE and SUSE Linux Enterprise Server"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/install-guide/bk-openstack-install-guide.xml:22(phrase)
|
||||
#: ./doc/install-guide/bk-openstack-install-guide.xml:24(phrase)
|
||||
msgid "Debian 7"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/install-guide/bk-openstack-install-guide.xml:18(titleabbrev)
|
||||
#: ./doc/install-guide/bk-openstack-install-guide.xml:20(titleabbrev)
|
||||
msgid "OpenStack Installation Guide for <placeholder-1/><placeholder-2/><placeholder-3/><placeholder-4/>"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/install-guide/bk-openstack-install-guide.xml:31(orgname)
|
||||
#: ./doc/install-guide/bk-openstack-install-guide.xml:33(orgname)
|
||||
msgid "OpenStack"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/install-guide/bk-openstack-install-guide.xml:35(year)
|
||||
#: ./doc/install-guide/bk-openstack-install-guide.xml:37(year)
|
||||
msgid "2012"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/install-guide/bk-openstack-install-guide.xml:36(year)
|
||||
#: ./doc/install-guide/bk-openstack-install-guide.xml:38(year)
|
||||
msgid "2013"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/install-guide/bk-openstack-install-guide.xml:37(year)
|
||||
#: ./doc/install-guide/bk-openstack-install-guide.xml:39(year)
|
||||
msgid "2014"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/install-guide/bk-openstack-install-guide.xml:38(year)
|
||||
#: ./doc/install-guide/bk-openstack-install-guide.xml:40(year)
|
||||
msgid "2015"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/install-guide/bk-openstack-install-guide.xml:39(holder)
|
||||
#: ./doc/install-guide/bk-openstack-install-guide.xml:41(holder)
|
||||
msgid "OpenStack Foundation"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/install-guide/bk-openstack-install-guide.xml:41(releaseinfo)
|
||||
#: ./doc/install-guide/bk-openstack-install-guide.xml:43(releaseinfo)
|
||||
msgid "kilo"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/install-guide/bk-openstack-install-guide.xml:42(productname)
|
||||
#: ./doc/install-guide/bk-openstack-install-guide.xml:44(productname)
|
||||
msgid "OpenStack Installation Guide"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/install-guide/bk-openstack-install-guide.xml:46(remark)
|
||||
#: ./doc/install-guide/bk-openstack-install-guide.xml:48(remark)
|
||||
msgid "Copyright details are filled in by the template."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/install-guide/bk-openstack-install-guide.xml:51(para)
|
||||
#: ./doc/install-guide/bk-openstack-install-guide.xml:53(para)
|
||||
msgid "The OpenStack® system consists of several key projects that you install separately. These projects work together depending on your cloud needs. These projects include Compute, Identity Service, Networking, Image Service, Block Storage, Object Storage, Telemetry, Orchestration, and Database. You can install any of these projects separately and configure them stand-alone or as connected entities. <phrase os=\"debian\">This guide walks through an installation by using packages available through Debian 7 (code name: Wheezy).</phrase><phrase os=\"ubuntu\">This guide walks through an installation by using packages available through Ubuntu 14.04.</phrase><phrase os=\"rhel;centos;fedora\">This guide shows you how to install OpenStack by using packages available through Fedora 21 as well as on Red Hat Enterprise Linux 7 and its derivatives through the EPEL repository.</phrase><phrase os=\"opensuse;sles\">This guide shows you how to install OpenStack by using packages on openSUSE 13.2 and SUSE Linux Enterprise Server 12 through the Open Build Service Cloud repository.</phrase> Explanations of configuration options and sample configuration files are included."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/install-guide/bk-openstack-install-guide.xml:80(date)
|
||||
#: ./doc/install-guide/bk-openstack-install-guide.xml:82(date)
|
||||
msgid "2014-10-15"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/install-guide/bk-openstack-install-guide.xml:84(para)
|
||||
#: ./doc/install-guide/bk-openstack-install-guide.xml:86(para)
|
||||
msgid "For the Juno release, this guide contains these updates: Replace openstack-config commands with general configuration file editing. Standardize on a single message queue system (RabbitMQ). Reference generic SQL database, enabling MySQL or MariaDB where appropriate. Replace auth_port and auth_protocol with identity_uri, and auth_host with auth_uri. Multiple edits for consistency. It has been updated for Juno and new distribution versions."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/install-guide/bk-openstack-install-guide.xml:102(date)
|
||||
#: ./doc/install-guide/bk-openstack-install-guide.xml:104(date)
|
||||
msgid "2014-06-03"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/install-guide/bk-openstack-install-guide.xml:106(para)
|
||||
#: ./doc/install-guide/bk-openstack-install-guide.xml:108(para)
|
||||
msgid "Start documentation for Juno."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/install-guide/bk-openstack-install-guide.xml:113(date)
|
||||
#: ./doc/install-guide/bk-openstack-install-guide.xml:115(date)
|
||||
msgid "2014-04-16"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/install-guide/bk-openstack-install-guide.xml:117(para)
|
||||
#: ./doc/install-guide/bk-openstack-install-guide.xml:119(para)
|
||||
msgid "Update for Icehouse, rework Networking setup to use ML2 as plugin, add new chapter for Database service setup, improved basic configuration."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/install-guide/bk-openstack-install-guide.xml:126(date)
|
||||
#: ./doc/install-guide/bk-openstack-install-guide.xml:128(date)
|
||||
msgid "2013-10-25"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/install-guide/bk-openstack-install-guide.xml:130(para)
|
||||
#: ./doc/install-guide/bk-openstack-install-guide.xml:132(para)
|
||||
msgid "Added initial Debian support."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/install-guide/bk-openstack-install-guide.xml:136(date)
|
||||
#: ./doc/install-guide/bk-openstack-install-guide.xml:138(date)
|
||||
msgid "2013-10-17"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/install-guide/bk-openstack-install-guide.xml:140(para)
|
||||
#: ./doc/install-guide/bk-openstack-install-guide.xml:142(para)
|
||||
msgid "Havana release."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/install-guide/bk-openstack-install-guide.xml:146(date)
|
||||
#: ./doc/install-guide/bk-openstack-install-guide.xml:148(date)
|
||||
msgid "2013-10-16"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/install-guide/bk-openstack-install-guide.xml:150(para)
|
||||
#: ./doc/install-guide/bk-openstack-install-guide.xml:152(para)
|
||||
msgid "Add support for SUSE Linux Enterprise."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/install-guide/bk-openstack-install-guide.xml:157(date)
|
||||
#: ./doc/install-guide/bk-openstack-install-guide.xml:159(date)
|
||||
msgid "2013-10-08"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/install-guide/bk-openstack-install-guide.xml:161(para)
|
||||
#: ./doc/install-guide/bk-openstack-install-guide.xml:163(para)
|
||||
msgid "Complete reorganization for Havana."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/install-guide/bk-openstack-install-guide.xml:168(date)
|
||||
#: ./doc/install-guide/bk-openstack-install-guide.xml:170(date)
|
||||
msgid "2013-09-09"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/install-guide/bk-openstack-install-guide.xml:172(para)
|
||||
#: ./doc/install-guide/bk-openstack-install-guide.xml:174(para)
|
||||
msgid "Build also for openSUSE."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/install-guide/bk-openstack-install-guide.xml:178(date)
|
||||
#: ./doc/install-guide/bk-openstack-install-guide.xml:180(date)
|
||||
msgid "2013-08-01"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/install-guide/bk-openstack-install-guide.xml:182(para)
|
||||
#: ./doc/install-guide/bk-openstack-install-guide.xml:184(para)
|
||||
msgid "Fixes to Object Storage verification steps. Fix bug <link href=\"https://bugs.launchpad.net/openstack-manuals/+bug/1207347\">1207347</link>."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/install-guide/bk-openstack-install-guide.xml:191(date)
|
||||
#: ./doc/install-guide/bk-openstack-install-guide.xml:193(date)
|
||||
msgid "2013-07-25"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/install-guide/bk-openstack-install-guide.xml:195(para)
|
||||
#: ./doc/install-guide/bk-openstack-install-guide.xml:197(para)
|
||||
msgid "Adds creation of cinder user and addition to the service tenant. Fix bug <link href=\"https://bugs.launchpad.net/openstack-manuals/+bug/1205057\">1205057</link>."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/install-guide/bk-openstack-install-guide.xml:205(date)
|
||||
#: ./doc/install-guide/bk-openstack-install-guide.xml:207(date)
|
||||
msgid "2013-05-08"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/install-guide/bk-openstack-install-guide.xml:209(para)
|
||||
#: ./doc/install-guide/bk-openstack-install-guide.xml:211(para)
|
||||
msgid "Updated the book title for consistency."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/install-guide/bk-openstack-install-guide.xml:216(date)
|
||||
#: ./doc/install-guide/bk-openstack-install-guide.xml:218(date)
|
||||
msgid "2013-05-02"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/install-guide/bk-openstack-install-guide.xml:220(para)
|
||||
#: ./doc/install-guide/bk-openstack-install-guide.xml:222(para)
|
||||
msgid "Updated cover and fixed small errors in appendix."
|
||||
msgstr ""
|
||||
|
||||
@ -5179,7 +5177,7 @@ msgid "The <glossterm baseform=\"cloud controller node\">controller node</glosst
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/install-guide/ch_overview.xml:70(para) ./doc/install-guide/ch_overview.xml:175(para)
|
||||
msgid "Optionally, the controller node runs portions of Block Storage, Object Storage, Orchestration, Telemetry, Database, and Data Processing services. These components provide additional features for your environment."
|
||||
msgid "Optionally, the controller node runs portions of Block Storage, Object Storage, Orchestration, Telemetry, Database, and Data processing services. These components provide additional features for your environment."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/install-guide/ch_overview.xml:77(para)
|
||||
|
||||
@ -5,8 +5,8 @@
|
||||
msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: OpenStack Manuals\n"
|
||||
"POT-Creation-Date: 2015-04-28 02:16+0000\n"
|
||||
"PO-Revision-Date: 2015-04-27 17:35+0000\n"
|
||||
"POT-Creation-Date: 2015-04-30 05:50+0000\n"
|
||||
"PO-Revision-Date: 2015-04-30 05:48+0000\n"
|
||||
"Last-Translator: openstackjenkins <jenkins@openstack.org>\n"
|
||||
"Language-Team: Japanese (http://www.transifex.com/projects/p/openstack-"
|
||||
"manuals-i18n/language/ja/)\n"
|
||||
@ -356,13 +356,6 @@ msgstr ""
|
||||
"持ちます。そのため、期限切れトークンを完全削除する定期タスクを手動設定する必"
|
||||
"要がありません。"
|
||||
|
||||
msgid ""
|
||||
"We recommend that you use <systemitem class=\"service\">cron</systemitem> to "
|
||||
"configure a periodic task that purges expired tokens hourly:"
|
||||
msgstr ""
|
||||
"期限切れトークンを定期的に削除するために、<systemitem class=\"service"
|
||||
"\">cron</systemitem> を使用することを推奨します。"
|
||||
|
||||
msgid "SQL database"
|
||||
msgstr "SQL データベース"
|
||||
|
||||
|
||||
@ -18,8 +18,8 @@
|
||||
msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: OpenStack Manuals\n"
|
||||
"POT-Creation-Date: 2015-04-28 02:16+0000\n"
|
||||
"PO-Revision-Date: 2015-04-27 17:35+0000\n"
|
||||
"POT-Creation-Date: 2015-04-30 05:50+0000\n"
|
||||
"PO-Revision-Date: 2015-04-30 05:48+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"
|
||||
@ -296,13 +296,6 @@ msgstr ""
|
||||
"이 설정에서는 SQL 데이터베이스 서버를 이용하기 때문에, SQLite 데이터베이스 파"
|
||||
"일을 제거할 수 있습니다:"
|
||||
|
||||
msgid ""
|
||||
"We recommend that you use <systemitem class=\"service\">cron</systemitem> to "
|
||||
"configure a periodic task that purges expired tokens hourly:"
|
||||
msgstr ""
|
||||
"우리는 당신이 사용하는 <systemitem class=\"service\">cron</systemitem> 에 시"
|
||||
"간단위로 만료된 토큰을 제거하는 주기적인 태스크를 설정할 것을 추천합니다:"
|
||||
|
||||
msgid "SQL database"
|
||||
msgstr "SQL 데이터베이스"
|
||||
|
||||
|
||||
@ -13,8 +13,8 @@
|
||||
msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: OpenStack Manuals\n"
|
||||
"POT-Creation-Date: 2015-04-28 02:16+0000\n"
|
||||
"PO-Revision-Date: 2015-04-27 17:35+0000\n"
|
||||
"POT-Creation-Date: 2015-04-30 05:50+0000\n"
|
||||
"PO-Revision-Date: 2015-04-30 05:48+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"
|
||||
@ -305,14 +305,6 @@ msgstr ""
|
||||
"Devido esta configuração utilizar um servidor de banco de dados SQL, você "
|
||||
"pode remover o arquivo de banco de dados SQLite:"
|
||||
|
||||
msgid ""
|
||||
"We recommend that you use <systemitem class=\"service\">cron</systemitem> to "
|
||||
"configure a periodic task that purges expired tokens hourly:"
|
||||
msgstr ""
|
||||
"Recomendamos que você utilize o <systemitem class=\"service\">cron</"
|
||||
"systemitem> para configurar uma tarefa periódica que limpa os tokens "
|
||||
"expirados de hora em hora:"
|
||||
|
||||
msgid "SQL database"
|
||||
msgstr "Banco de dados SQL"
|
||||
|
||||
@ -6461,16 +6453,6 @@ msgstr ""
|
||||
"serviços como um banco de dados SQL, <glossterm>fila de mensagens</"
|
||||
"glossterm>, e <glossterm>Network Time Protocol (NTP)</glossterm>."
|
||||
|
||||
msgid ""
|
||||
"Optionally, the controller node runs portions of Block Storage, Object "
|
||||
"Storage, Orchestration, Telemetry, Database, and Data Processing services. "
|
||||
"These components provide additional features for your environment."
|
||||
msgstr ""
|
||||
"Opcionalmente, o nodo controlador executa partes dos serviços de Block "
|
||||
"Storage, Object Storage, Orquestração, Telemetria, Banco de Dados, e "
|
||||
"Processamento de Dados. Este componentes fornecem características adicionais "
|
||||
"ao seu ambiente."
|
||||
|
||||
msgid ""
|
||||
"The network node runs the Networking plug-in and several agents that "
|
||||
"provision tenant networks and provide switching, routing, <glossterm "
|
||||
|
||||
@ -10,8 +10,8 @@
|
||||
msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: OpenStack Manuals\n"
|
||||
"POT-Creation-Date: 2015-04-28 02:16+0000\n"
|
||||
"PO-Revision-Date: 2015-04-27 17:35+0000\n"
|
||||
"POT-Creation-Date: 2015-04-30 05:50+0000\n"
|
||||
"PO-Revision-Date: 2015-04-30 05:48+0000\n"
|
||||
"Last-Translator: openstackjenkins <jenkins@openstack.org>\n"
|
||||
"Language-Team: Russian (http://www.transifex.com/projects/p/openstack-"
|
||||
"manuals-i18n/language/ru/)\n"
|
||||
@ -302,14 +302,6 @@ msgstr ""
|
||||
"Поскольку эта конфигурация использует сервер баз данных SQL, вы можете "
|
||||
"удалить файл базы данных SQLite:"
|
||||
|
||||
msgid ""
|
||||
"We recommend that you use <systemitem class=\"service\">cron</systemitem> to "
|
||||
"configure a periodic task that purges expired tokens hourly:"
|
||||
msgstr ""
|
||||
"Мы рекомендуем использовать <systemitem class=\"service\">cron</systemitem> "
|
||||
"для создания периодической задачи, которая будет очищать истёкшие токены "
|
||||
"каждый час:"
|
||||
|
||||
msgid ""
|
||||
"Most OpenStack services use an SQL database to store information. The "
|
||||
"database typically runs on the controller node. The procedures in this guide "
|
||||
@ -4918,15 +4910,6 @@ msgstr ""
|
||||
"сообщений</glossterm> и <glossterm>Протокол сетевого времени (NTP)</"
|
||||
"glossterm>."
|
||||
|
||||
msgid ""
|
||||
"Optionally, the controller node runs portions of Block Storage, Object "
|
||||
"Storage, Orchestration, Telemetry, Database, and Data Processing services. "
|
||||
"These components provide additional features for your environment."
|
||||
msgstr ""
|
||||
"Дополнительно, управляющий узел содержит части служб Блочного хранения, "
|
||||
"Хранилища Объектов, Оркестровки, Телеметрии, Базы Данных и Обработки Данных. "
|
||||
"Эти компоненты предоставляют дополнительный функционал вашей среде."
|
||||
|
||||
msgid ""
|
||||
"The network node runs the Networking plug-in and several agents that "
|
||||
"provision tenant networks and provide switching, routing, <glossterm "
|
||||
|
||||
@ -22,8 +22,8 @@
|
||||
msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: OpenStack Manuals\n"
|
||||
"POT-Creation-Date: 2015-04-28 02:16+0000\n"
|
||||
"PO-Revision-Date: 2015-04-27 17:35+0000\n"
|
||||
"POT-Creation-Date: 2015-04-30 05:50+0000\n"
|
||||
"PO-Revision-Date: 2015-04-30 05:48+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"
|
||||
@ -325,13 +325,6 @@ msgid ""
|
||||
"SQLite database file:"
|
||||
msgstr "而下面的配置将使用 SQL 数据库服务，可以删除该 SQLite 数据库文件："
|
||||
|
||||
msgid ""
|
||||
"We recommend that you use <systemitem class=\"service\">cron</systemitem> to "
|
||||
"configure a periodic task that purges expired tokens hourly:"
|
||||
msgstr ""
|
||||
"建议使用 <systemitem class=\"service\">cron</systemitem> 配置计划任务每个小时"
|
||||
"定时清理过期的身份凭证："
|
||||
|
||||
msgid "SQL database"
|
||||
msgstr "SQL数据库"
|
||||
|
||||
@ -4608,26 +4601,6 @@ msgstr "启动数据库服务并将其设置为随系统启动："
|
||||
msgid "Add the Block Storage service"
|
||||
msgstr "添加块设备存储服务"
|
||||
|
||||
msgid ""
|
||||
"The OpenStack Block Storage service provides block storage devices to guest "
|
||||
"instances. The method in which the storage is provisioned and consumed is "
|
||||
"determined by the Block Storage driver, or drivers in the case of a multi-"
|
||||
"backend configuration. There are a variety of drivers that are available: "
|
||||
"NAS/SAN, NFS, iSCSI, Ceph, and more. The Block Storage API and scheduler "
|
||||
"services typically run on the controller nodes. Depending upon the drivers "
|
||||
"used, the volume service can run on controllers, compute nodes, or "
|
||||
"standalone storage nodes. For more information, see the <link href=\"http://"
|
||||
"docs.openstack.org/juno/config-reference/content/section_volume-drivers.html"
|
||||
"\"><citetitle>Configuration Reference</citetitle></link>."
|
||||
msgstr ""
|
||||
"OpenStack 的块设备存储服务为虚拟机实例提供块设备存储设备。提供和消费存储的方"
|
||||
"法是由块存储驱动或配置了多后端的驱动所决定的。有各种各样的可用存储：NAS/SAN、"
|
||||
"NFS、iSCSI、Ceph 等。块设备存储 API 和调度服务一般运行在控制节点上。根据驱动"
|
||||
"程序的使用，卷服务可以运行在控制节点、计算节点或单个存储节点上。要了解更多信"
|
||||
"息，请阅读 <link href=\"http://docs.openstack.org/juno/config-reference/"
|
||||
"content/section_volume-drivers.html\"><citetitle>Configuration Reference</"
|
||||
"citetitle></link>。"
|
||||
|
||||
msgid ""
|
||||
"This chapter omits the backup manager because it depends on the Object "
|
||||
"Storage service."
|
||||
@ -6261,14 +6234,6 @@ msgstr ""
|
||||
"包括一些支持服务，例如 SQL 数据库、<glossterm>消息队列</glossterm>和"
|
||||
"<glossterm>网络时间协议 (NTP)</glossterm>。"
|
||||
|
||||
msgid ""
|
||||
"Optionally, the controller node runs portions of Block Storage, Object "
|
||||
"Storage, Orchestration, Telemetry, Database, and Data Processing services. "
|
||||
"These components provide additional features for your environment."
|
||||
msgstr ""
|
||||
"可选地，可以在控制节点运行块设备存储、对象存储、Orchestration、Telemetry、数"
|
||||
"据库和数据处理服务的一部分。这些组件可以为您的环境提供额外的功能。"
|
||||
|
||||
msgid ""
|
||||
"The network node runs the Networking plug-in and several agents that "
|
||||
"provision tenant networks and provide switching, routing, <glossterm "
|
||||
|
||||
File diff suppressed because it is too large
Load Diff
File diff suppressed because it is too large
Load Diff
Loading…
Reference in New Issue
Block a user