From 0504afcb37e8e559e738da1dda444ec282d939f2 Mon Sep 17 00:00:00 2001 From: OpenStack Proposal Bot Date: Thu, 5 Mar 2015 06:13:11 +0000 Subject: [PATCH] Imported Translations from Transifex For more information about this automatic import see: https://wiki.openstack.org/wiki/Translations/Infrastructure Change-Id: I79b0763fa7842ece323d7b4129062f5a656f7d51 --- doc/arch-design/locale/arch-design.pot | 200 ++++++---- doc/arch-design/locale/zh_CN.po | 412 ++++++++++++--------- doc/common/locale/common.pot | 6 +- doc/common/locale/fr.po | 11 +- doc/common/locale/ja.po | 11 +- doc/common/locale/zh_CN.po | 11 +- doc/install-guide/locale/install-guide.pot | 10 +- doc/install-guide/locale/ja.po | 24 +- doc/install-guide/locale/ko_KR.po | 20 +- doc/install-guide/locale/pt_BR.po | 22 +- doc/install-guide/locale/ru.po | 20 +- 11 files changed, 423 insertions(+), 324 deletions(-) diff --git a/doc/arch-design/locale/arch-design.pot b/doc/arch-design/locale/arch-design.pot index 62173c6eef..727323104f 100644 --- a/doc/arch-design/locale/arch-design.pot +++ b/doc/arch-design/locale/arch-design.pot @@ -1,7 +1,7 @@ msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" -"POT-Creation-Date: 2015-03-04 06:10+0000\n" +"POT-Creation-Date: 2015-03-05 06:11+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -5429,171 +5429,223 @@ msgstr "" msgid "When building a storage focused OpenStack architecture, strive to build a flexible design that is based on a industry standard core. One way of accomplishing this might be through the use of different back ends serving different use cases." msgstr "" -#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml:11(para) -msgid "Maintenance tasks: The storage solution should take into account storage maintenance and the impact on underlying workloads." +#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml:9(para) +msgid "Operational factors affect the design choices for a general purpose cloud, and operations staff receive tasks regarding the maintenance of cloud environments for larger installations." +msgstr "" + +#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml:14(term) +msgid "Maintenance tasks" msgstr "" #: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml:16(para) -msgid "Reliability and availability: Reliability and availability depends on wide area network availability and on the level of precautions taken by the service provider." +msgid "The storage solution should take into account storage maintenance and the impact on underlying workloads." msgstr "" -#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml:22(para) -msgid "Flexibility: Organizations need to have the flexibility to choose between off-premise and on-premise cloud storage options. This concept relies on relevant decision criteria that is complementary to initial direct cost savings potential. For example, continuity of operations, disaster recovery, security, and records retention laws, regulations, and policies." +#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml:22(term) +msgid "Reliability and availability" msgstr "" -#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml:32(para) -msgid "In a cloud environment with very high demands on storage resources, it becomes vitally important to ensure that monitoring and alerting services have been installed and configured to provide a real-time view into the health and performance of the storage systems. Using an integrated management console, or other dashboards capable of visualizing SNMP data, will be helpful in discovering and resolving issues that might arise within the storage cluster. An example of this is Ceph's Calamari." +#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml:24(para) +msgid "Reliability and availability depend on wide area network availability and on the level of precautions taken by the service provider." msgstr "" -#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml:41(para) -msgid "A storage-focused cloud design should include:" +#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml:31(term) +msgid "Flexibility" +msgstr "" + +#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml:33(para) +msgid "Organizations need to have the flexibility to choose between off-premise and on-premise cloud storage options. This concept relies on relevant decision criteria that is complementary to initial direct cost savings potential. For example, continuity of operations, disaster recovery, security, and records retention laws, regulations, and policies." msgstr "" #: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml:44(para) -msgid "Monitoring of physical hardware resources." -msgstr "" - -#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml:47(para) -msgid "Monitoring of environmental resources such as temperature and humidity." +msgid "Monitoring and alerting services are vitally important in cloud environments with high demands on storage resources. These services provide a real-time view into the health and performance of the storage systems. An integrated management console, or other dashboards capable of visualizing SNMP data, is helpful when discovering and resolving issues that arise within the storage cluster." msgstr "" #: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml:51(para) +msgid "A storage-focused cloud design should include:" +msgstr "" + +#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml:54(para) +msgid "Monitoring of physical hardware resources." +msgstr "" + +#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml:57(para) +msgid "Monitoring of environmental resources such as temperature and humidity." +msgstr "" + +#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml:61(para) msgid "Monitoring of storage resources such as available storage, memory and CPU." msgstr "" -#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml:55(para) +#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml:65(para) msgid "Monitoring of advanced storage performance data to ensure that storage systems are performing as expected." msgstr "" -#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml:60(para) +#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml:70(para) msgid "Monitoring of network resources for service disruptions which would affect access to storage." msgstr "" -#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml:65(para) +#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml:75(para) msgid "Centralized log collection." msgstr "" -#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml:68(para) +#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml:78(para) msgid "Log analytics capabilities." msgstr "" -#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml:71(para) +#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml:81(para) msgid "Ticketing system (or integration with a ticketing system) to track issues." msgstr "" -#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml:75(para) +#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml:85(para) msgid "Alerting and notification of responsible teams or automated systems which will remediate problems with storage as they arise." msgstr "" -#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml:80(para) +#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml:90(para) msgid "Network Operations Center (NOC) staffed and always available to resolve issues." msgstr "" -#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml:85(title) +#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml:96(title) msgid "Management efficiency" msgstr "" -#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml:86(para) -msgid "When designing a storage solution at scale, ease of management of the storage devices is an important consideration. Within a storage cluster, operations personnel will often be required to replace failed drives or nodes and provide ongoing maintenance of the storage hardware. When the cloud is designed and planned properly, the process can be performed in a seamless and organized manner that does not have an impact on operational efficiency." +#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml:97(para) +msgid "Operations personnel will often be required to replace failed drives or nodes and provide ongoing maintenance of the storage hardware." msgstr "" -#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml:94(para) -msgid "Provisioning and configuration of new or upgraded storage is another important consideration when it comes to management of resources. The ability to easily deploy, configure, and manage storage hardware will result in a solution which is easy to manage. This also makes use of management systems that can automate other pieces of the overall solution. For example, replication, retention, data backup and recovery." +#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml:99(para) +msgid "Provisioning and configuration of new or upgraded storage is another important consideration when it comes to management of resources. The ability to easily deploy, configure, and manage storage hardware results in a solution that is easy to manage. This also makes use of management systems that can automate other pieces of the overall solution. For example, replication, retention, data backup and recovery." msgstr "" -#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml:102(title) +#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml:109(title) msgid "Application awareness" msgstr "" -#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml:103(para) -msgid "When designing applications that will leverage storage solutions in the cloud, design the application to be aware of the underlying storage subsystem and the features available. As an example, when creating an application that requires replication, we recommend that the application be designed to detect whether replication is a feature natively available in the storage subsystem. In the event that replication is not available, the application can be designed to react in a manner such that it will be able to provide its own replication services. An application that is designed to be aware of the underlying storage systems can be deployed in a wide variety of infrastructures and still have the same basic behavior regardless of the differences in the underlying infrastructure." +#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml:110(para) +msgid "Well-designed applications should be aware of underlying storage subsystems, in order to use cloud storage solutions effectively." msgstr "" -#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml:118(title) +#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml:112(para) +msgid "If natively available replication is not available, the application must be able to be modified by operations personnel so that they can provide their own replication service. In the event that replication is unavailable, operations personnel can design applications to react such that they can provide their own replication services. An application designed to detect underlying storage systems can function in a wide variety of infrastructures, and still have the same basic behavior regardless of the differences in the underlying infrastructure." +msgstr "" + +#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml:124(title) msgid "Fault tolerance and availability" msgstr "" -#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml:119(para) -msgid "Designing for fault tolerance and availability of storage systems in an OpenStack cloud is vastly different when comparing the block storage and object storage services. The object storage service is designed to have consistency and partition tolerance as a function of the application. Therefore, it does not have any reliance on hardware RAID controllers to provide redundancy for physical disks. In contrast, block storage resource nodes are commonly configured with advanced RAID controllers and high performance disks that are designed to provide fault tolerance at the hardware level." +#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml:125(para) +msgid "Designing for fault tolerance and availability of storage systems in an OpenStack cloud is vastly different when comparing the Block Storage and Object Storage services. The Object Storage service is designed to have consistency and partition tolerance as a function of the application. Therefore, it does not have any reliance on hardware RAID controllers to provide redundancy for physical disks." msgstr "" -#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml:130(para) -msgid "In cases where applications require extreme performance out of block storage devices, we recommend you deploy high performing storage solutions such as SSD disk drives or flash storage systems. When considering these solutions, it is important to consider the availability of software and support to ease with the hardware and software integration process." +#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml:134(title) +msgid "Block Storage fault tolerance and availability" msgstr "" -#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml:137(para) -msgid "In environments that place extreme demands on block storage, it is advisable to take advantage of multiple storage pools. In this case, each pool of devices should have a similar hardware design and disk configuration across all hardware nodes in that pool. This allows for a design that provides applications with access to a wide variety of block storage pools, each with their own redundancy, availability, and performance characteristics. When deploying multiple pools of storage it is also important to consider the impact on the block storage scheduler which is responsible for provisioning storage across resource nodes. Ensuring that applications can schedule volumes in multiple regions, each with their own network, power, and cooling infrastructure, can give tenants the ability to build fault tolerant applications that will be distributed across multiple availability zones." +#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml:135(para) +msgid "Block Storage resource nodes are commonly configured with advanced RAID controllers and high performance disks that are designed to provide fault tolerance at the hardware level." msgstr "" -#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml:152(para) -msgid "In addition to the block storage resource nodes, it is important to design for high availability and redundancy of the APIs and related services that are responsible for provisioning and providing access to storage. It is recommended to design a layer of hardware or software load balancers in order to achieve high availability of the appropriate REST API services to provide uninterrupted service. In some cases, it may also be necessary to deploy an additional layer of load balancing to provide access to back-end database services responsible for servicing and storing the state of block storage volumes. Designing a highly available database solution to store the Block Storage databases is also recommended. A number of highly available database solutions such as Galera and MariaDB can be leveraged to help keep database services online to provide uninterrupted access so that tenants can manage block storage volumes." +#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml:139(para) +msgid "Deploy high performing storage solutions such as SSD disk drives or flash storage systems in cases where applications require extreme performance out of Block Storage devices." msgstr "" -#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml:168(para) -msgid "In a cloud with extreme demands on block storage the network architecture should take into account the amount of East-West bandwidth that will be required for instances to make use of the available storage resources. Network devices selected should support jumbo frames for transferring large blocks of data. In some cases, it may be necessary to create an additional back-end storage network dedicated to providing connectivity between instances and block storage resources so that there is no contention of network resources." +#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml:142(para) +msgid "In environments that place extreme demands on Block Storage, it is advisable to take advantage of multiple storage pools. In this case, each pool of devices should have a similar hardware design and disk configuration across all hardware nodes in that pool. This allows for a design that provides applications with access to a wide variety of Block Storage pools, each with their own redundancy, availability, and performance characteristics. When deploying multiple pools of storage it is also important to consider the impact on the Block Storage scheduler which is responsible for provisioning storage across resource nodes. Ensuring that applications can schedule volumes in multiple regions, each with their own network, power, and cooling infrastructure, can give tenants the ability to build fault tolerant applications that will be distributed across multiple availability zones." msgstr "" -#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml:178(title) +#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml:157(para) +msgid "In addition to the Block Storage resource nodes, it is important to design for high availability and redundancy of the APIs and related services that are responsible for provisioning and providing access to storage. We recommend desiging a layer of hardware or software load balancers in order to achieve high availability of the appropriate REST API services to provide uninterrupted service. In some cases, it may also be necessary to deploy an additional layer of load balancing to provide access to back-end database services responsible for servicing and storing the state of Block Storage volumes. We also recommend designing a highly available database solution to store the Block Storage databases. A number of highly available database solutions such as Galera and MariaDB can be leveraged to help keep database services online to provide uninterrupted access so that tenants can manage Block Storage volumes." +msgstr "" + +#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml:173(para) +msgid "In a cloud with extreme demands on Block Storage, the network architecture should take into account the amount of East-West bandwidth that will be required for instances to make use of the available storage resources. Network devices selected should support jumbo frames for transferring large blocks of data. In some cases, it may be necessary to create an additional back-end storage network dedicated to providing connectivity between instances and Block Storage resources so that there is no contention of network resources." +msgstr "" + +#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml:184(title) msgid "Object Storage fault tolerance and availability" msgstr "" -#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml:180(para) -msgid "While consistency and partition tolerance are both inherent features of the object storage service, it is important to design the overall storage architecture to ensure that those goals can be met by the system being implemented. The OpenStack object storage service places a specific number of data replicas as objects on resource nodes. These replicas are distributed throughout the cluster based on a consistent hash ring which exists on all nodes in the cluster." +#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml:185(para) +msgid "While consistency and partition tolerance are both inherent features of the Object Storage service, it is important to design the overall storage architecture to ensure that those goals are met by the system being implemented. The OpenStack Object Storage service places a specific number of data replicas as objects on resource nodes. These replicas are distributed throughout the cluster based on a consistent hash ring which exists on all nodes in the cluster." msgstr "" -#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml:188(para) -msgid "The object storage system should be designed with sufficient number of zones to provide quorum for the number of replicas defined. As an example, with three replicas configured in the Swift cluster, the recommended number of zones to configure within the object storage cluster in order to achieve quorum is 5. While it is possible to deploy a solution with fewer zones, the implied risk of doing so is that some data may not be available and API requests to certain objects stored in the cluster might fail. For this reason, ensure the number of zones in the object storage cluster is properly accounted for." +#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml:193(para) +msgid "The Object Storage system should be designed with sufficient number of zones to provide quorum for the number of replicas defined. As an example, with three replicas configured in the Swift cluster, the recommended number of zones to configure within the Object Storage cluster in order to achieve quorum is 5. While it is possible to deploy a solution with fewer zones, the implied risk of doing so is that some data may not be available and API requests to certain objects stored in the cluster might fail. For this reason, ensure the number of zones in the Object Storage cluster is properly accounted for." msgstr "" -#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml:198(para) -msgid "Each object storage zone should be self-contained within its own availability zone. Each availability zone should have independent access to network, power and cooling infrastructure to ensure uninterrupted access to data. In addition, each availability zone should be serviced by a pool of object storage proxy servers which will provide access to data stored on the object nodes. Object proxies in each region should leverage local read and write affinity so that access to objects is facilitated by local storage resources wherever possible. We recommend that upstream load balancing be deployed to ensure that proxy services can be distributed across the multiple zones and, in some cases, it may be necessary to make use of third party solutions to aid with geographical distribution of services." +#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml:203(para) +msgid "Each Object Storage zone should be self-contained within its own availability zone. Each availability zone should have independent access to network, power and cooling infrastructure to ensure uninterrupted access to data. In addition, each availability zone should be serviced by a pool of Object Storage proxy servers which will provide access to data stored on the object nodes. Object proxies in each region should leverage local read and write affinity so that access to objects is facilitated by local storage resources wherever possible. We recommend that upstream load balancing be deployed to ensure that proxy services can be distributed across the multiple zones and, in some cases, it may be necessary to make use of third party solutions to aid with geographical distribution of services." msgstr "" -#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml:212(para) -msgid "A zone within an object storage cluster is a logical division. A zone can be represented as a disk within a single node, the node itself, a group of nodes in a rack, an entire rack, a data center or even a geographic region. Deciding on the proper zone design is crucial for allowing the object storage cluster to scale while providing an available and redundant storage system. Furthermore, it may be necessary to configure storage policies that have different requirements with regards to replicas, retention and other factors that could heavily affect the design of storage in a specific zone." +#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml:217(para) +msgid "A zone within an Object Storage cluster is a logical division. A zone can be represented as any of the following:" msgstr "" -#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml:224(title) +#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml:221(para) +msgid "A disk within a single node" +msgstr "" + +#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml:226(para) +msgid "One zone per node" +msgstr "" + +#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml:231(para) +msgid "Zone per collection of nodes" +msgstr "" + +#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml:236(para) +msgid "Multiple racks" +msgstr "" + +#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml:241(para) +msgid "Multiple DCs" +msgstr "" + +#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml:246(para) +msgid "Deciding the proper zone design is crucial for allowing the Object Storage cluster to scale while providing an available and redundant storage system. It may be necessary to configure storage policies that have different requirements with regards to replicas, retention and other factors that could heavily affect the design of storage in a specific zone." +msgstr "" + +#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml:257(title) msgid "Scaling storage services" msgstr "" -#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml:225(para) -msgid "Adding storage capacity and bandwidth is a very different process when comparing the block and object storage services. While adding block storage capacity is a relatively simple process, adding capacity and bandwidth to the object storage systems is a complex task that requires careful planning and consideration during the design phase." +#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml:258(para) +msgid "Adding storage capacity and bandwidth is a very different process when comparing the Block and Object Storage services. While adding Block Storage capacity is a relatively simple process, adding capacity and bandwidth to the Object Storage systems is a complex task that requires careful planning and consideration during the design phase." msgstr "" -#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml:232(title) +#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml:265(title) msgid "Scaling Block Storage" msgstr "" -#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml:233(para) -msgid "Block storage pools can be upgraded to add storage capacity rather easily without interruption to the overall block storage service. Nodes can be added to the pool by simply installing and configuring the appropriate hardware and software and then allowing that node to report in to the proper storage pool via the message bus. This is because block storage nodes report into the scheduler service advertising their availability. Once the node is online and available tenants can make use of those storage resources instantly." +#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml:266(para) +msgid "Block Storage pools can be upgraded to add storage capacity rather easily without interruption to the overall Block Storage service. Nodes can be added to the pool by simply installing and configuring the appropriate hardware and software and then allowing that node to report in to the proper storage pool via the message bus. This is because Block Storage nodes report into the scheduler service advertising their availability. Once the node is online and available tenants can make use of those storage resources instantly." msgstr "" -#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml:243(para) -msgid "In some cases, the demand on block storage from instances may exhaust the available network bandwidth. As a result, design network infrastructure that services block storage resources in such a way that capacity and bandwidth can be added relatively easily. This often involves the use of dynamic routing protocols or advanced networking solutions to allow capacity to be added to downstream devices easily. Both the front-end and back-end storage network designs should encompass the ability to quickly and easily add capacity and bandwidth." +#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml:276(para) +msgid "In some cases, the demand on Block Storage from instances may exhaust the available network bandwidth. As a result, design network infrastructure that services Block Storage resources in such a way that capacity and bandwidth can be added relatively easily. This often involves the use of dynamic routing protocols or advanced networking solutions to allow capacity to be added to downstream devices easily. Both the front-end and back-end storage network designs should encompass the ability to quickly and easily add capacity and bandwidth." msgstr "" -#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml:254(title) +#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml:288(title) msgid "Scaling Object Storage" msgstr "" -#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml:255(para) -msgid "Adding back-end storage capacity to an object storage cluster requires careful planning and consideration. In the design phase it is important to determine the maximum partition power required by the object storage service, which determines the maximum number of partitions which can exist. Object storage distributes data among all available storage, but a partition cannot span more than one disk, so the maximum number of partitions can only be as high as the number of disks." +#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml:289(para) +msgid "Adding back-end storage capacity to an Object Storage cluster requires careful planning and consideration. In the design phase it is important to determine the maximum partition power required by the Object Storage service, which determines the maximum number of partitions which can exist. Object Storage distributes data among all available storage, but a partition cannot span more than one disk, so the maximum number of partitions can only be as high as the number of disks." msgstr "" -#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml:264(para) -msgid "For example, a system that starts with a single disk and a partition power of 3 can have 8 (2^3) partitions. Adding a second disk means that each will (usually) have 4 partitions. The one-disk-per-partition limit means that this system can never have more than 8 disks, limiting its scalability. However, a system that starts with a single disk and a partition power of 10 can have up to 1024 (2^10) disks." +#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml:298(para) +msgid "For example, a system that starts with a single disk and a partition power of 3 can have 8 (2^3) partitions. Adding a second disk means that each will have 4 partitions. The one-disk-per-partition limit means that this system can never have more than 8 disks, limiting its scalability. However, a system that starts with a single disk and a partition power of 10 can have up to 1024 (2^10) disks." msgstr "" -#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml:271(para) -msgid "As back-end storage capacity is added to the system, the partition maps cause data to be redistributed amongst storage nodes. In some cases, this replication can consist of extremely large data sets. In these cases, it is recommended to make use of back-end replication links which will not contend with tenants' access to data." +#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml:305(para) +msgid "As back-end storage capacity is added to the system, the partition maps cause data to be redistributed amongst storage nodes. In some cases, this replication can consist of extremely large data sets. In these cases, we recommended making use of back-end replication links which will not contend with tenants' access to data." msgstr "" -#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml:277(para) -msgid "As more tenants begin to access data within the cluster and their data sets grow it will become necessary to add front-end bandwidth to service data access requests. Adding front-end bandwidth to an object storage cluster requires careful planning and design of the object storage proxies that will be used by tenants to gain access to the data, along with the high availability solutions that enable easy scaling of the proxy layer. It is recommended to design a front-end load balancing layer that tenants and consumers use to gain access to data stored within the cluster. This load balancing layer may be distributed across zones, regions or even across geographic boundaries, which may also require that the design encompass geo-location solutions." +#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml:311(para) +msgid "As more tenants begin to access data within the cluster and their data sets grow it will become necessary to add front-end bandwidth to service data access requests. Adding front-end bandwidth to an Object Storage cluster requires careful planning and design of the Object Storage proxies that will be used by tenants to gain access to the data, along with the high availability solutions that enable easy scaling of the proxy layer. We recommend designing a front-end load balancing layer that tenants and consumers use to gain access to data stored within the cluster. This load balancing layer may be distributed across zones, regions or even across geographic boundaries, which may also require that the design encompass geo-location solutions." msgstr "" -#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml:290(para) +#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml:324(para) msgid "In some cases, adding bandwidth and capacity to the network resources servicing requests between proxy servers and storage nodes will be required. For this reason, the network architecture used for access to storage nodes and proxy servers should make use of a design which is scalable." msgstr "" @@ -5616,7 +5668,7 @@ msgid "@@image: '../figures/Storage_Database_+_Object5.png'; md5=a0cb2374c3515b8 msgstr "" #: ./doc/arch-design/storage_focus/section_prescriptive_examples_storage_focus.xml:9(para) -msgid "Storage-focused architectures are highly dependent on the specific use case. Three specific example use cases are discussed in this section:" +msgid "Storage-focused architecture highly depends on the specific use case. Three specific example use cases are discussed in this section:" msgstr "" #: ./doc/arch-design/storage_focus/section_prescriptive_examples_storage_focus.xml:14(para) @@ -5652,7 +5704,7 @@ msgid "Network:" msgstr "" #: ./doc/arch-design/storage_focus/section_prescriptive_examples_storage_focus.xml:48(para) -msgid "10 GbE horizontally scalable spine leaf back end storage and front end network." +msgid "10 GbE horizontally scalable spine leaf back-end storage and front end network." msgstr "" #: ./doc/arch-design/storage_focus/section_prescriptive_examples_storage_focus.xml:52(para) ./doc/arch-design/storage_focus/section_prescriptive_examples_storage_focus.xml:157(para) @@ -5676,11 +5728,11 @@ msgid "2x10 GbE bonded front end" msgstr "" #: ./doc/arch-design/storage_focus/section_prescriptive_examples_storage_focus.xml:69(para) ./doc/arch-design/storage_focus/section_prescriptive_examples_storage_focus.xml:178(para) -msgid "2x10 GbE back end bonds" +msgid "2x10 GbE back-end bonds" msgstr "" #: ./doc/arch-design/storage_focus/section_prescriptive_examples_storage_focus.xml:72(para) ./doc/arch-design/storage_focus/section_prescriptive_examples_storage_focus.xml:181(para) -msgid "Approximately 60 Gb of total bandwidth to the back end storage cluster" +msgid "Approximately 60 Gb of total bandwidth to the back-end storage cluster" msgstr "" #: ./doc/arch-design/storage_focus/section_prescriptive_examples_storage_focus.xml:77(para) @@ -5696,7 +5748,7 @@ msgid "Analytics of large data sets are highly dependent on the performance of t msgstr "" #: ./doc/arch-design/storage_focus/section_prescriptive_examples_storage_focus.xml:88(para) -msgid "One potential solution to this problem is the implentation of storage systems designed for performance. Parallel file systems have previously filled this need in the HPC space and as a result could be considered for large scale performance-orientated systems." +msgid "One potential solution to this problem is the implementation of storage systems designed for performance. Parallel file systems have previously filled this need in the HPC space and as a result could be considered for large scale performance-orientated systems." msgstr "" #: ./doc/arch-design/storage_focus/section_prescriptive_examples_storage_focus.xml:92(para) @@ -5736,7 +5788,7 @@ msgid "Using Ceph as an applicable example, a potential architecture would have msgstr "" #: ./doc/arch-design/storage_focus/section_prescriptive_examples_storage_focus.xml:153(para) -msgid "10 GbE horizontally scalable spine leaf back end storage and front end network" +msgid "10 GbE horizontally scalable spine leaf back-end storage and front-end network" msgstr "" #: ./doc/arch-design/storage_focus/section_prescriptive_examples_storage_focus.xml:160(para) diff --git a/doc/arch-design/locale/zh_CN.po b/doc/arch-design/locale/zh_CN.po index 5f45d587df..1e962a9a04 100644 --- a/doc/arch-design/locale/zh_CN.po +++ b/doc/arch-design/locale/zh_CN.po @@ -8,8 +8,8 @@ msgid "" msgstr "" "Project-Id-Version: OpenStack Manuals\n" -"POT-Creation-Date: 2015-03-03 19:38+0000\n" -"PO-Revision-Date: 2015-03-03 06:33+0000\n" +"POT-Creation-Date: 2015-03-04 23:12+0000\n" +"PO-Revision-Date: 2015-03-04 23:14+0000\n" "Last-Translator: openstackjenkins \n" "Language-Team: Chinese (China) (http://www.transifex.com/projects/p/openstack-manuals-i18n/language/zh_CN/)\n" "MIME-Version: 1.0\n" @@ -10501,355 +10501,399 @@ msgid "" "different use cases." msgstr "努力尝试构建一个基于行业标准核心的灵活设计。实现这个的一个办法，可能是通过使用不同的后端服务于不同的使用场景。" -#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml11(para) +#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml9(para) msgid "" -"Maintenance tasks: The storage solution should take into account storage " -"maintenance and the impact on underlying workloads." -msgstr "维护任务：存储的解决方案需要考虑存储的维护以及其对底层负载的影响。" +"Operational factors affect the design choices for a general purpose cloud, " +"and operations staff receive tasks regarding the maintenance of cloud " +"environments for larger installations." +msgstr "" + +#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml14(term) +msgid "Maintenance tasks" +msgstr "" #: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml16(para) msgid "" -"Reliability and availability: Reliability and availability depends on wide " -"area network availability and on the level of precautions taken by the " -"service provider." -msgstr "可靠性和可用性：可靠性和可用性依赖于广域网的可用性以及服务提供商采取的预防措施的级别。" +"The storage solution should take into account storage maintenance and the " +"impact on underlying workloads." +msgstr "" -#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml22(para) +#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml22(term) +msgid "Reliability and availability" +msgstr "" + +#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml24(para) msgid "" -"Flexibility: Organizations need to have the flexibility to choose between " -"off-premise and on-premise cloud storage options. This concept relies on " -"relevant decision criteria that is complementary to initial direct cost " -"savings potential. For example, continuity of operations, disaster recovery," -" security, and records retention laws, regulations, and policies." -msgstr "灵活性：组织需要有选择off-premise和on-premise云存储属性的灵活性。此概念依赖于相关的决策条件，它可以互补，会在初始时有直接的成本节约潜力。举例，持续的维护、灾难恢复、安全、记录保留规定、法规以及规则。" +"Reliability and availability depend on wide area network availability and on" +" the level of precautions taken by the service provider." +msgstr "" -#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml32(para) +#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml31(term) +msgid "Flexibility" +msgstr "" + +#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml33(para) msgid "" -"In a cloud environment with very high demands on storage resources, it " -"becomes vitally important to ensure that monitoring and alerting services " -"have been installed and configured to provide a real-time view into the " -"health and performance of the storage systems. Using an integrated " -"management console, or other dashboards capable of visualizing SNMP data, " -"will be helpful in discovering and resolving issues that might arise within " -"the storage cluster. An example of this is Ceph's Calamari." -msgstr "在对存储资源有非常高要求的云环境中，确保在环境中安装了监控和警报服务并且将它们进行配置以提供存储系统实时的健康状态和性能状态的信息，是非常之重要的。使用集成的管理控制台，或者能够将 SNMP 数据可视化的面板程序，能够帮助发现和解决存储集群中可能出现的问题。一个例子是 Ceph 的 Calamari。" +"Organizations need to have the flexibility to choose between off-premise and" +" on-premise cloud storage options. This concept relies on relevant decision " +"criteria that is complementary to initial direct cost savings potential. For" +" example, continuity of operations, disaster recovery, security, and records" +" retention laws, regulations, and policies." +msgstr "" -#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml41(para) +#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml44(para) +msgid "" +"Monitoring and alerting services are vitally important in cloud environments" +" with high demands on storage resources. These services provide a real-time " +"view into the health and performance of the storage systems. An integrated " +"management console, or other dashboards capable of visualizing SNMP data, is" +" helpful when discovering and resolving issues that arise within the storage" +" cluster." +msgstr "" + +#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml51(para) msgid "A storage-focused cloud design should include:" msgstr "存储型的云设计需要包括：" -#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml44(para) +#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml54(para) msgid "Monitoring of physical hardware resources." msgstr "监测物理硬件资源。" -#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml47(para) +#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml57(para) msgid "" "Monitoring of environmental resources such as temperature and humidity." msgstr "监测诸如温度和湿度等的环境信息。" -#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml51(para) +#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml61(para) msgid "" "Monitoring of storage resources such as available storage, memory and CPU." msgstr "监测诸如可用存储空间、内存和 CPU 等存储资源信息。" -#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml55(para) +#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml65(para) msgid "" "Monitoring of advanced storage performance data to ensure that storage " "systems are performing as expected." msgstr "监测高级的存储性能数据，以确保存储系统正常运转。" -#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml60(para) +#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml70(para) msgid "" "Monitoring of network resources for service disruptions which would affect " "access to storage." msgstr "监测网络资源情况，关注可能影响存储访问的网络服务中断问题。" -#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml65(para) +#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml75(para) msgid "Centralized log collection." msgstr "日志集中收集" -#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml68(para) +#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml78(para) msgid "Log analytics capabilities." msgstr "日志分析能力。" -#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml71(para) +#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml81(para) msgid "" "Ticketing system (or integration with a ticketing system) to track issues." msgstr "票务系统(或者与其它票务系统的集成)以跟踪问题。" -#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml75(para) +#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml85(para) msgid "" "Alerting and notification of responsible teams or automated systems which " "will remediate problems with storage as they arise." msgstr "对负责团队的警报和通知，或者能够在存储出现问题时能够修复问题的自动化系统。" -#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml80(para) +#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml90(para) msgid "" "Network Operations Center (NOC) staffed and always available to resolve " "issues." msgstr "配备有网络运营中心(NOC)员工并保持工作状态以解决问题。" -#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml85(title) +#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml96(title) msgid "Management efficiency" msgstr "管理效率" -#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml86(para) +#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml97(para) msgid "" -"When designing a storage solution at scale, ease of management of the " -"storage devices is an important consideration. Within a storage cluster, " -"operations personnel will often be required to replace failed drives or " -"nodes and provide ongoing maintenance of the storage hardware. When the " -"cloud is designed and planned properly, the process can be performed in a " -"seamless and organized manner that does not have an impact on operational " -"efficiency." -msgstr "设计一个适用于大规模的存储解决方案时，对存储设备的管理的便利程度是很重要的一个考虑因素。在一个存储集群中，运营人员会经常需要替换失效的驱动器或者节点，并且不断进行存储硬件的维护工作。当云架构被适当地设计和计划时，以上过程能够被无缝且有序地执行，并且不会对运营的效率造成影响。" +"Operations personnel will often be required to replace failed drives or " +"nodes and provide ongoing maintenance of the storage hardware." +msgstr "" -#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml94(para) +#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml99(para) msgid "" "Provisioning and configuration of new or upgraded storage is another " "important consideration when it comes to management of resources. The " -"ability to easily deploy, configure, and manage storage hardware will result" -" in a solution which is easy to manage. This also makes use of management " -"systems that can automate other pieces of the overall solution. For example," -" replication, retention, data backup and recovery." -msgstr "准备和配置新增或者升级的存储，是另外一个关于管理存储资源的重要考虑因素。方便地部署、配置以及管理存储硬件的能力，能够造就一个容易管理的解决方案。这同样也利用了能够将整个解决方案中的其它部分组件自动化的管理系统。例如，复制、保管、数据备份和恢复。" +"ability to easily deploy, configure, and manage storage hardware results in " +"a solution that is easy to manage. This also makes use of management systems" +" that can automate other pieces of the overall solution. For example, " +"replication, retention, data backup and recovery." +msgstr "" -#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml102(title) +#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml109(title) msgid "Application awareness" msgstr "应用的可知性" -#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml103(para) +#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml110(para) msgid "" -"When designing applications that will leverage storage solutions in the " -"cloud, design the application to be aware of the underlying storage " -"subsystem and the features available. As an example, when creating an " -"application that requires replication, we recommend that the application be " -"designed to detect whether replication is a feature natively available in " -"the storage subsystem. In the event that replication is not available, the " -"application can be designed to react in a manner such that it will be able " -"to provide its own replication services. An application that is designed to " -"be aware of the underlying storage systems can be deployed in a wide variety" -" of infrastructures and still have the same basic behavior regardless of the" -" differences in the underlying infrastructure." -msgstr "当设计在云中利用存储解决方案的应用时，需要将应用设计成为能够觉察到底层的存储子系统的存在以及其可用的特性。举例来说，当创建一个需要副本数据的应用时，我们建议将应用设计成为能够检测副本复制是否是底层存储子系统的原生特性。在复制功能不是底层存储系统的特性的情况下，才将应用设计成为自身能够提供副本复制服务。一个被设计为能够觉察到底层存储系统的应用，同样可以在很大范围的基础设施中部署，并且依然拥有一些最基本的行为，而不管底层的基础设施有什么不同。" +"Well-designed applications should be aware of underlying storage subsystems," +" in order to use cloud storage solutions effectively." +msgstr "" -#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml118(title) +#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml112(para) +msgid "" +"If natively available replication is not available, the application must be " +"able to be modified by operations personnel so that they can provide their " +"own replication service. In the event that replication is unavailable, " +"operations personnel can design applications to react such that they can " +"provide their own replication services. An application designed to detect " +"underlying storage systems can function in a wide variety of " +"infrastructures, and still have the same basic behavior regardless of the " +"differences in the underlying infrastructure." +msgstr "" + +#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml124(title) msgid "Fault tolerance and availability" msgstr "容错和可用性" -#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml119(para) +#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml125(para) msgid "" "Designing for fault tolerance and availability of storage systems in an " -"OpenStack cloud is vastly different when comparing the block storage and " -"object storage services. The object storage service is designed to have " +"OpenStack cloud is vastly different when comparing the Block Storage and " +"Object Storage services. The Object Storage service is designed to have " "consistency and partition tolerance as a function of the application. " "Therefore, it does not have any reliance on hardware RAID controllers to " -"provide redundancy for physical disks. In contrast, block storage resource " -"nodes are commonly configured with advanced RAID controllers and high " -"performance disks that are designed to provide fault tolerance at the " -"hardware level." -msgstr "在 OpenStack 云中为存储系统的容错和可用性进行设计，对于块存储和对象存储服务来说，是有很大的不同的。对象存储服务具有一致性以及区块容错，能够作为应用的功能。因此，它并不依赖于硬件 RAID 控制器提供的物理磁盘冗余。与此相对的，块存储资源节点通常都配备有高级的 RAID 控制器以及高性能的磁盘，被设计为能够在硬件层面上提供容错。" +"provide redundancy for physical disks." +msgstr "" -#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml130(para) -msgid "" -"In cases where applications require extreme performance out of block storage" -" devices, we recommend you deploy high performing storage solutions such as " -"SSD disk drives or flash storage systems. When considering these solutions, " -"it is important to consider the availability of software and support to ease" -" with the hardware and software integration process." -msgstr "在应用要求发挥块存储设备的极端性能的场景下，我们建议您部署高性能的存储方案，例如SSD 磁盘驱动器或者闪存存储系统。在考虑这些解决方案时，对简化硬件和软件集成过程的软件可用性和支持情况进行考虑，也是很重要的。" +#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml134(title) +msgid "Block Storage fault tolerance and availability" +msgstr "" -#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml137(para) +#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml135(para) msgid "" -"In environments that place extreme demands on block storage, it is advisable" +"Block Storage resource nodes are commonly configured with advanced RAID " +"controllers and high performance disks that are designed to provide fault " +"tolerance at the hardware level." +msgstr "" + +#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml139(para) +msgid "" +"Deploy high performing storage solutions such as SSD disk drives or flash " +"storage systems in cases where applications require extreme performance out " +"of Block Storage devices." +msgstr "" + +#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml142(para) +msgid "" +"In environments that place extreme demands on Block Storage, it is advisable" " to take advantage of multiple storage pools. In this case, each pool of " "devices should have a similar hardware design and disk configuration across " "all hardware nodes in that pool. This allows for a design that provides " -"applications with access to a wide variety of block storage pools, each with" +"applications with access to a wide variety of Block Storage pools, each with" " their own redundancy, availability, and performance characteristics. When " "deploying multiple pools of storage it is also important to consider the " -"impact on the block storage scheduler which is responsible for provisioning " +"impact on the Block Storage scheduler which is responsible for provisioning " "storage across resource nodes. Ensuring that applications can schedule " "volumes in multiple regions, each with their own network, power, and cooling" " infrastructure, can give tenants the ability to build fault tolerant " "applications that will be distributed across multiple availability zones." -msgstr "在对块存储具有极端需求的环境下，我们建议利用多个存储池所带来的好处。在这种场景中，每个设备池，在池中的所有硬件节点上，必须都具有相似的硬件设计以及磁盘配置。这使得设计能够为应用提供到多个块存储池的访问，每个存储池都有其自身的冗余、可用性和性能特点。部署多个存储池时，对负责在资源节点上准备存储的块存储调度器的影响，也是一个重要的考虑因素。确保应用能够将其存储卷分散到不同的区域中，每个区域具有其自身的网络、电源以及冷却基础设施，能够给予租户建立具有容错性应用的能力。该应用会被分布到多个可用区域中。" +msgstr "" -#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml152(para) +#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml157(para) msgid "" -"In addition to the block storage resource nodes, it is important to design " +"In addition to the Block Storage resource nodes, it is important to design " "for high availability and redundancy of the APIs and related services that " -"are responsible for provisioning and providing access to storage. It is " -"recommended to design a layer of hardware or software load balancers in " -"order to achieve high availability of the appropriate REST API services to " -"provide uninterrupted service. In some cases, it may also be necessary to " -"deploy an additional layer of load balancing to provide access to back-end " -"database services responsible for servicing and storing the state of block " -"storage volumes. Designing a highly available database solution to store the" -" Block Storage databases is also recommended. A number of highly available " -"database solutions such as Galera and MariaDB can be leveraged to help keep " -"database services online to provide uninterrupted access so that tenants can" -" manage block storage volumes." -msgstr "在块存储资源节点之外，为 API 以及相关的负责准备存储和提供到存储的访问的服务的高可用性和冗余进行设计也非常重要。我们建议设计中包含一个硬件或者软件的负载均衡器层，以实现相关 REST API 服务的高可用性，从而实现提供不中断的服务。某些情况下，可能还需要部署一个额外的负载均衡层，以提供到后端数据库服务的访问，该后端数据库负责提供以及保存块存储卷的状态信息。我们同样建议设计一个高可用的数据库解决方案来存放块存储的数据库。当前有许多的高可用数据库的解决方案，比如说 Galera 和 MariaDB，能够被用以帮助保持数据库服务在线，以提供不间断的访问服务，保证租户能够管理块存储卷。" +"are responsible for provisioning and providing access to storage. We " +"recommend desiging a layer of hardware or software load balancers in order " +"to achieve high availability of the appropriate REST API services to provide" +" uninterrupted service. In some cases, it may also be necessary to deploy an" +" additional layer of load balancing to provide access to back-end database " +"services responsible for servicing and storing the state of Block Storage " +"volumes. We also recommend designing a highly available database solution to" +" store the Block Storage databases. A number of highly available database " +"solutions such as Galera and MariaDB can be leveraged to help keep database " +"services online to provide uninterrupted access so that tenants can manage " +"Block Storage volumes." +msgstr "" -#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml168(para) +#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml173(para) msgid "" -"In a cloud with extreme demands on block storage the network architecture " +"In a cloud with extreme demands on Block Storage, the network architecture " "should take into account the amount of East-West bandwidth that will be " "required for instances to make use of the available storage resources. " "Network devices selected should support jumbo frames for transferring large " "blocks of data. In some cases, it may be necessary to create an additional " "back-end storage network dedicated to providing connectivity between " -"instances and block storage resources so that there is no contention of " +"instances and Block Storage resources so that there is no contention of " "network resources." -msgstr "在对块存储具有极端需求的云环境中，网络的架构需要考虑东西向的带宽流量，这些带宽是实例使用可用的存储资源所必需的。所选择的网络设备必须支持巨型帧以传输大块的数据。某些情况下，可能还需要创建额外的后端存储网络，专用于为实例和块存储资源之间提供网络连接，来保证没有对于网络资源的争抢。" +msgstr "" -#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml178(title) +#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml184(title) msgid "Object Storage fault tolerance and availability" msgstr "对象存储容错和可用性" -#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml180(para) +#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml185(para) msgid "" "While consistency and partition tolerance are both inherent features of the " -"object storage service, it is important to design the overall storage " -"architecture to ensure that those goals can be met by the system being " -"implemented. The OpenStack object storage service places a specific number " +"Object Storage service, it is important to design the overall storage " +"architecture to ensure that those goals are met by the system being " +"implemented. The OpenStack Object Storage service places a specific number " "of data replicas as objects on resource nodes. These replicas are " "distributed throughout the cluster based on a consistent hash ring which " "exists on all nodes in the cluster." -msgstr "虽然一致性和区块容错性都是对象存储服务的内生特性，对整个存储架构进行设计，以确保要实施的系统能够满足这些目标依然还是很重要的。OpenStack 对象存储服务将特定数量的数据副本作为对象存放与资源节点上。这些副本分布在整个集群之中，基于存在于集群中所有节点上的一致性哈希环。" +msgstr "" -#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml188(para) +#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml193(para) msgid "" -"The object storage system should be designed with sufficient number of zones" +"The Object Storage system should be designed with sufficient number of zones" " to provide quorum for the number of replicas defined. As an example, with " "three replicas configured in the Swift cluster, the recommended number of " -"zones to configure within the object storage cluster in order to achieve " +"zones to configure within the Object Storage cluster in order to achieve " "quorum is 5. While it is possible to deploy a solution with fewer zones, the" " implied risk of doing so is that some data may not be available and API " "requests to certain objects stored in the cluster might fail. For this " -"reason, ensure the number of zones in the object storage cluster is properly" +"reason, ensure the number of zones in the Object Storage cluster is properly" " accounted for." -msgstr "对象存储系统必须设计得拥有充足的区域提供法定数量，为所定义的复制份数。举个例子，在一个swift集群中配置了三份复制，那么建议区域数量是5。当然，也可以部署时少于这个数，但是这有数据不可用的风险以及API请求无法应答。基于这个原因，在对象存储系统中要确保正确的数量。" +msgstr "" -#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml198(para) +#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml203(para) msgid "" -"Each object storage zone should be self-contained within its own " +"Each Object Storage zone should be self-contained within its own " "availability zone. Each availability zone should have independent access to " "network, power and cooling infrastructure to ensure uninterrupted access to " "data. In addition, each availability zone should be serviced by a pool of " -"object storage proxy servers which will provide access to data stored on the" +"Object Storage proxy servers which will provide access to data stored on the" " object nodes. Object proxies in each region should leverage local read and " "write affinity so that access to objects is facilitated by local storage " "resources wherever possible. We recommend that upstream load balancing be " "deployed to ensure that proxy services can be distributed across the " "multiple zones and, in some cases, it may be necessary to make use of third " "party solutions to aid with geographical distribution of services." -msgstr "每个对象存储区域须包含到其自身的可用区域里。每个可用区域须拥有独立的访问网络、电力和制冷等基础设施，确保访问数据不会中断。另外，每个可用区域须服务于对象存储池代理服务，而代理服务提供访问存放在对象节点的数据。在每个region的对象代理应充分利用本地的读写，所以尽可能的访问本地存储资源。我们建议在上游的负载均衡的部署要确保代理服务是分布在不同的区域的。在一些情况下，有必要使用第三方的解决方案来处理跨地域分布式服务。" +msgstr "" -#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml212(para) +#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml217(para) msgid "" -"A zone within an object storage cluster is a logical division. A zone can be" -" represented as a disk within a single node, the node itself, a group of " -"nodes in a rack, an entire rack, a data center or even a geographic region. " -"Deciding on the proper zone design is crucial for allowing the object " -"storage cluster to scale while providing an available and redundant storage " -"system. Furthermore, it may be necessary to configure storage policies that " -"have different requirements with regards to replicas, retention and other " -"factors that could heavily affect the design of storage in a specific zone." -msgstr "对象存储集群内的区域是一个逻辑上的划分。一个区域可以是由单个节点上的一块磁盘，也可以是节点本身，也可以是一个机柜中的几台节点，也可以是单独的整个机柜，也可是一个数据中心，甚至是跨地域的region。决定合适的区域设计的关键是对象存储集群的扩展，还能同时提供可靠和冗余的存储系统。进一步讲，也许还需要根据不同的需求配置存储的策略，这些策略包括副本，保留以及其它在特定区域会严重影响到存储设计的因素。" +"A zone within an Object Storage cluster is a logical division. A zone can be" +" represented as any of the following:" +msgstr "" -#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml224(title) +#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml221(para) +msgid "A disk within a single node" +msgstr "" + +#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml226(para) +msgid "One zone per node" +msgstr "" + +#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml231(para) +msgid "Zone per collection of nodes" +msgstr "" + +#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml236(para) +msgid "Multiple racks" +msgstr "" + +#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml241(para) +msgid "Multiple DCs" +msgstr "" + +#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml246(para) +msgid "" +"Deciding the proper zone design is crucial for allowing the Object Storage " +"cluster to scale while providing an available and redundant storage system. " +"It may be necessary to configure storage policies that have different " +"requirements with regards to replicas, retention and other factors that " +"could heavily affect the design of storage in a specific zone." +msgstr "" + +#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml257(title) msgid "Scaling storage services" msgstr "扩展存储服务" -#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml225(para) +#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml258(para) msgid "" "Adding storage capacity and bandwidth is a very different process when " -"comparing the block and object storage services. While adding block storage " +"comparing the Block and Object Storage services. While adding Block Storage " "capacity is a relatively simple process, adding capacity and bandwidth to " -"the object storage systems is a complex task that requires careful planning " +"the Object Storage systems is a complex task that requires careful planning " "and consideration during the design phase." -msgstr "将块存储和对象存储服务相比较，增加存储容量和带宽是完全不同的流程。增加块存储的容量是一个相对简单的过程，增加对象存储系统的容量和带宽是一个复杂的任务，需要经过精心的规划和周全的考虑。" +msgstr "" -#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml232(title) +#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml265(title) msgid "Scaling Block Storage" msgstr "扩展块存储" -#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml233(para) +#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml266(para) msgid "" -"Block storage pools can be upgraded to add storage capacity rather easily " -"without interruption to the overall block storage service. Nodes can be " +"Block Storage pools can be upgraded to add storage capacity rather easily " +"without interruption to the overall Block Storage service. Nodes can be " "added to the pool by simply installing and configuring the appropriate " "hardware and software and then allowing that node to report in to the proper" -" storage pool via the message bus. This is because block storage nodes " +" storage pool via the message bus. This is because Block Storage nodes " "report into the scheduler service advertising their availability. Once the " "node is online and available tenants can make use of those storage resources" " instantly." -msgstr "块存储池增加存储容量的升级较简单而且毋须中断整个块存储服务。节点添加到池中仅通过简单的安装和配置合适的软硬件，然后允许节点通过消息总线报告给对应的池即可。这是因为块存储节点报告给调度器服务表明他们可用。一旦节点处于在线状态，可用的租户立马就可以使用它的存储资源。" +msgstr "" -#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml243(para) +#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml276(para) msgid "" -"In some cases, the demand on block storage from instances may exhaust the " +"In some cases, the demand on Block Storage from instances may exhaust the " "available network bandwidth. As a result, design network infrastructure that" -" services block storage resources in such a way that capacity and bandwidth " +" services Block Storage resources in such a way that capacity and bandwidth " "can be added relatively easily. This often involves the use of dynamic " "routing protocols or advanced networking solutions to allow capacity to be " "added to downstream devices easily. Both the front-end and back-end storage " "network designs should encompass the ability to quickly and easily add " "capacity and bandwidth." -msgstr "在一些情形下，来自实例对块存储的需求会耗尽可用的网络带宽。因此，设计网络基础设施时，考虑到如此的块存储资源使用一定得很容易的增加容量和带宽。这通常涉及到使用动态路由协议或者是高级网络解决方案允许轻松添加下游设备以增加容量。无论是前端存储网络设计还是后端存储网络设计都得围绕着快速和容易添加容量和带宽的能力来展开。" +msgstr "" -#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml254(title) +#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml288(title) msgid "Scaling Object Storage" msgstr "扩展对象存储" -#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml255(para) +#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml289(para) msgid "" -"Adding back-end storage capacity to an object storage cluster requires " +"Adding back-end storage capacity to an Object Storage cluster requires " "careful planning and consideration. In the design phase it is important to " -"determine the maximum partition power required by the object storage " +"determine the maximum partition power required by the Object Storage " "service, which determines the maximum number of partitions which can exist. " -"Object storage distributes data among all available storage, but a partition" +"Object Storage distributes data among all available storage, but a partition" " cannot span more than one disk, so the maximum number of partitions can " "only be as high as the number of disks." -msgstr "为对象存储集群增加后端容量需要谨慎的规划和考虑。在设计阶段，决定最大partition power非常重要，这由对象存储服务所需要，它直接决定可以提供最大数量的分区。对象存储分发数据到所有的可用存储上，但是一个分区不可以再分到一块磁盘之外的地方，所以分区的最大数量只能是磁盘的数量。" +msgstr "" -#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml264(para) +#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml298(para) msgid "" "For example, a system that starts with a single disk and a partition power " "of 3 can have 8 (2^3) partitions. Adding a second disk means that each will " -"(usually) have 4 partitions. The one-disk-per-partition limit means that " -"this system can never have more than 8 disks, limiting its scalability. " -"However, a system that starts with a single disk and a partition power of 10" -" can have up to 1024 (2^10) disks." -msgstr "例如，一个系统开始使用单个磁盘，partition power是3，那么可以有8(2^3) 个分区。增加第二块磁盘意味着每块将(使用)拥有4个分区。一盘一分区的限制意味着此系统不可能拥有超过8块磁盘，它的扩展性受限。因此，一个系统开始时使用单个磁盘，且partition power是10的话可以使用1024(2^10)个磁盘。" +"have 4 partitions. The one-disk-per-partition limit means that this system " +"can never have more than 8 disks, limiting its scalability. However, a " +"system that starts with a single disk and a partition power of 10 can have " +"up to 1024 (2^10) disks." +msgstr "" -#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml271(para) +#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml305(para) msgid "" "As back-end storage capacity is added to the system, the partition maps " "cause data to be redistributed amongst storage nodes. In some cases, this " -"replication can consist of extremely large data sets. In these cases, it is " -"recommended to make use of back-end replication links which will not contend" -" with tenants' access to data." -msgstr "为系统的后端存储增加了容量后，分区映射会带来数据重新分发到存储节点，在一些情况下，这些复制会带来超大的数据集合，在此种情况下，建议使用后端复制链接，它也不会阻断租户访问数据。" +"replication can consist of extremely large data sets. In these cases, we " +"recommended making use of back-end replication links which will not contend " +"with tenants' access to data." +msgstr "" -#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml277(para) +#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml311(para) msgid "" "As more tenants begin to access data within the cluster and their data sets " "grow it will become necessary to add front-end bandwidth to service data " -"access requests. Adding front-end bandwidth to an object storage cluster " -"requires careful planning and design of the object storage proxies that will" +"access requests. Adding front-end bandwidth to an Object Storage cluster " +"requires careful planning and design of the Object Storage proxies that will" " be used by tenants to gain access to the data, along with the high " -"availability solutions that enable easy scaling of the proxy layer. It is " -"recommended to design a front-end load balancing layer that tenants and " +"availability solutions that enable easy scaling of the proxy layer. We " +"recommend designing a front-end load balancing layer that tenants and " "consumers use to gain access to data stored within the cluster. This load " "balancing layer may be distributed across zones, regions or even across " "geographic boundaries, which may also require that the design encompass geo-" "location solutions." -msgstr "当越来越多的租户开始访问对象存储集群的数据，他们的数据开始不断的增长时，就有必要为服务增加前端带宽以应对不断的访问需求。为对象存储集群增加前端带宽要谨慎规划，设计对象存储代理供租户访问数据使用，为代理层设计高可用解决方案且可轻松扩展等等，建议设计一前端负载均衡层，为租户和最终消费者提供更加可靠的访问数据方式，这个负载均衡层可以是分发到跨区域，跨region，甚至是跨地域，这要视实际对地理位置解决方案的需求而定。" +msgstr "" -#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml290(para) +#: ./doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml324(para) msgid "" "In some cases, adding bandwidth and capacity to the network resources " "servicing requests between proxy servers and storage nodes will be required." @@ -10886,9 +10930,9 @@ msgstr "@@image: '../figures/Storage_Database_+_Object5.png'; md5=a0cb2374c3515b #: ./doc/arch-design/storage_focus/section_prescriptive_examples_storage_focus.xml9(para) msgid "" -"Storage-focused architectures are highly dependent on the specific use case." -" Three specific example use cases are discussed in this section:" -msgstr "存储型的架构十分依赖于其目标的明确应用场景。本节讨论了三种不同使用场景的例子：" +"Storage-focused architecture highly depends on the specific use case. Three " +"specific example use cases are discussed in this section:" +msgstr "" #: ./doc/arch-design/storage_focus/section_prescriptive_examples_storage_focus.xml14(para) msgid "An object store with a RESTful interface" @@ -10932,9 +10976,9 @@ msgstr "网络：" #: ./doc/arch-design/storage_focus/section_prescriptive_examples_storage_focus.xml48(para) msgid "" -"10 GbE horizontally scalable spine leaf back end storage and front end " +"10 GbE horizontally scalable spine leaf back-end storage and front end " "network." -msgstr "10 GbE 可水平扩展的分布式核心后端存储及前端网络。" +msgstr "" #: ./doc/arch-design/storage_focus/section_prescriptive_examples_storage_focus.xml52(para) #: ./doc/arch-design/storage_focus/section_prescriptive_examples_storage_focus.xml157(para) @@ -10963,13 +11007,13 @@ msgstr "2x10 GbE 绑定的前端" #: ./doc/arch-design/storage_focus/section_prescriptive_examples_storage_focus.xml69(para) #: ./doc/arch-design/storage_focus/section_prescriptive_examples_storage_focus.xml178(para) -msgid "2x10 GbE back end bonds" -msgstr "2x10 GbE 绑定的后端" +msgid "2x10 GbE back-end bonds" +msgstr "" #: ./doc/arch-design/storage_focus/section_prescriptive_examples_storage_focus.xml72(para) #: ./doc/arch-design/storage_focus/section_prescriptive_examples_storage_focus.xml181(para) -msgid "Approximately 60 Gb of total bandwidth to the back end storage cluster" -msgstr "到后端存储集群大约 60 Gb 的总带宽" +msgid "Approximately 60 Gb of total bandwidth to the back-end storage cluster" +msgstr "" #: ./doc/arch-design/storage_focus/section_prescriptive_examples_storage_focus.xml77(para) msgid "" @@ -10990,11 +11034,11 @@ msgstr "对大规模数据集的分析十分依赖于存储系统的性能。有 #: ./doc/arch-design/storage_focus/section_prescriptive_examples_storage_focus.xml88(para) msgid "" -"One potential solution to this problem is the implentation of storage " +"One potential solution to this problem is the implementation of storage " "systems designed for performance. Parallel file systems have previously " "filled this need in the HPC space and as a result could be considered for " "large scale performance-orientated systems." -msgstr "这个问题的一个解决方案是部署一个设计时便将性能考虑在内的存储系统。传统上来说，并行文件系统填补了 HPC 空间里的这个需要，在适用的时候，可以作为大规模面向性能的系统的一个备份的方案考虑。" +msgstr "" #: ./doc/arch-design/storage_focus/section_prescriptive_examples_storage_focus.xml92(para) msgid "" @@ -11065,9 +11109,9 @@ msgstr "跟上面的例子相关的 Ceph 的一个可能架构需要如下组件 #: ./doc/arch-design/storage_focus/section_prescriptive_examples_storage_focus.xml153(para) msgid "" -"10 GbE horizontally scalable spine leaf back end storage and front end " +"10 GbE horizontally scalable spine leaf back-end storage and front-end " "network" -msgstr "10 GbE 可水平扩展的分布式核心后端存储及前端网络。" +msgstr "" #: ./doc/arch-design/storage_focus/section_prescriptive_examples_storage_focus.xml160(para) msgid "5 storage servers for caching layer 24x1 TB SSD" diff --git a/doc/common/locale/common.pot b/doc/common/locale/common.pot index cded1167a4..84044ca2d5 100644 --- a/doc/common/locale/common.pot +++ b/doc/common/locale/common.pot @@ -1,7 +1,7 @@ msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" -"POT-Creation-Date: 2015-03-04 06:11+0000\n" +"POT-Creation-Date: 2015-03-05 06:11+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -356,7 +356,7 @@ msgid "Configure instances at boot" msgstr "" #: ./doc/common/section_user-data.xml:8(para) -msgid "When you boot instances in an OpenStack cloud, you can use user data or cloud-init to automatically configure instances at boot time. You might want to install some packages, start services, or manage your instance by using a Puppet or Chef server." +msgid "When you boot instances in an OpenStack cloud, you can use user data or cloud-init to automatically configure instances at boot time. You might want to install some packages, start services, or manage your instance by using a Puppet or Chef server." msgstr "" #: ./doc/common/section_user-data.xml:14(title) @@ -464,7 +464,7 @@ msgid "Example: Configure instances with Chef" msgstr "" #: ./doc/common/section_user-data.xml:176(para) -msgid "This cloud-init user data example, based on doc/examples/cloud-config/chef.txt and intended for use in an Ubuntu image, adds the Chef apt repository, installs Chef, connects to a Chef server at https://chefserver.example.com:4000, and installs Apache:" +msgid "This cloud-init user data example, based on doc/examples/cloud-config/chef.txt and intended for use in an Ubuntu image, adds the Chef apt repository, installs Chef, connects to a Chef server at https://chefserver.example.com/organizations/myorg/, and installs Apache:" msgstr "" #. When image changes, this message will be marked fuzzy or untranslated for you. diff --git a/doc/common/locale/fr.po b/doc/common/locale/fr.po index 24914ecd18..c41784814c 100644 --- a/doc/common/locale/fr.po +++ b/doc/common/locale/fr.po @@ -19,8 +19,8 @@ msgid "" msgstr "" "Project-Id-Version: OpenStack Manuals\n" -"POT-Creation-Date: 2015-03-03 19:39+0000\n" -"PO-Revision-Date: 2015-03-03 19:53+0000\n" +"POT-Creation-Date: 2015-03-04 23:13+0000\n" +"PO-Revision-Date: 2015-03-04 15:38+0000\n" "Last-Translator: openstackjenkins \n" "Language-Team: French (http://www.transifex.com/projects/p/openstack-manuals-i18n/language/fr/)\n" "MIME-Version: 1.0\n" @@ -1006,8 +1006,8 @@ msgid "" "cloud-init to automatically configure instances at boot " "time. You might want to install some packages, start services, or manage " "your instance by using a Puppet or Chef" -" server." +"open-source\">Puppet or Chef server." msgstr "" #: ./doc/common/section_user-data.xml14(title) @@ -1187,7 +1187,8 @@ msgid "" "init/trunk/view/head:/doc/examples/cloud-config-chef.txt\">doc/examples" "/cloud-config/chef.txt and intended for use in an Ubuntu image, adds " "the Chef apt repository, installs Chef, connects to a Chef server at " -"https://chefserver.example.com:4000, and installs Apache:" +"https://chefserver.example.com/organizations/myorg/, and " +"installs Apache:" msgstr "" #. When image changes, this message will be marked fuzzy or untranslated for diff --git a/doc/common/locale/ja.po b/doc/common/locale/ja.po index 0e236b82ce..8a361654b9 100644 --- a/doc/common/locale/ja.po +++ b/doc/common/locale/ja.po @@ -7,8 +7,8 @@ msgid "" msgstr "" "Project-Id-Version: OpenStack Manuals\n" -"POT-Creation-Date: 2015-03-03 19:39+0000\n" -"PO-Revision-Date: 2015-03-03 20:01+0000\n" +"POT-Creation-Date: 2015-03-04 23:13+0000\n" +"PO-Revision-Date: 2015-03-04 15:38+0000\n" "Last-Translator: openstackjenkins \n" "Language-Team: Japanese (http://www.transifex.com/projects/p/openstack-manuals-i18n/language/ja/)\n" "MIME-Version: 1.0\n" @@ -994,8 +994,8 @@ msgid "" "cloud-init to automatically configure instances at boot " "time. You might want to install some packages, start services, or manage " "your instance by using a Puppet or Chef" -" server." +"open-source\">Puppet or Chef server." msgstr "" #: ./doc/common/section_user-data.xml14(title) @@ -1175,7 +1175,8 @@ msgid "" "init/trunk/view/head:/doc/examples/cloud-config-chef.txt\">doc/examples" "/cloud-config/chef.txt and intended for use in an Ubuntu image, adds " "the Chef apt repository, installs Chef, connects to a Chef server at " -"https://chefserver.example.com:4000, and installs Apache:" +"https://chefserver.example.com/organizations/myorg/, and " +"installs Apache:" msgstr "" #. When image changes, this message will be marked fuzzy or untranslated for diff --git a/doc/common/locale/zh_CN.po b/doc/common/locale/zh_CN.po index 248fc6630c..7f899bbadc 100644 --- a/doc/common/locale/zh_CN.po +++ b/doc/common/locale/zh_CN.po @@ -10,8 +10,8 @@ msgid "" msgstr "" "Project-Id-Version: OpenStack Manuals\n" -"POT-Creation-Date: 2015-03-03 19:39+0000\n" -"PO-Revision-Date: 2015-03-03 20:01+0000\n" +"POT-Creation-Date: 2015-03-04 23:13+0000\n" +"PO-Revision-Date: 2015-03-04 15:38+0000\n" "Last-Translator: openstackjenkins \n" "Language-Team: Chinese (China) (http://www.transifex.com/projects/p/openstack-manuals-i18n/language/zh_CN/)\n" "MIME-Version: 1.0\n" @@ -997,8 +997,8 @@ msgid "" "cloud-init to automatically configure instances at boot " "time. You might want to install some packages, start services, or manage " "your instance by using a Puppet or Chef" -" server." +"open-source\">Puppet or Chef server." msgstr "" #: ./doc/common/section_user-data.xml14(title) @@ -1178,7 +1178,8 @@ msgid "" "init/trunk/view/head:/doc/examples/cloud-config-chef.txt\">doc/examples" "/cloud-config/chef.txt and intended for use in an Ubuntu image, adds " "the Chef apt repository, installs Chef, connects to a Chef server at " -"https://chefserver.example.com:4000, and installs Apache:" +"https://chefserver.example.com/organizations/myorg/, and " +"installs Apache:" msgstr "" #. When image changes, this message will be marked fuzzy or untranslated for diff --git a/doc/install-guide/locale/install-guide.pot b/doc/install-guide/locale/install-guide.pot index 9bffaf82c0..6d28524b9e 100644 --- a/doc/install-guide/locale/install-guide.pot +++ b/doc/install-guide/locale/install-guide.pot @@ -1,7 +1,7 @@ msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" -"POT-Creation-Date: 2015-03-04 06:11+0000\n" +"POT-Creation-Date: 2015-03-05 06:12+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -448,11 +448,11 @@ msgid "Add ceilometer to the pipeline para msgstr "" #: ./doc/install-guide/section_ceilometer-swift.xml:49(para) -msgid "Add the system user swift to the system group ceilometer to give Object Storage access to the ceilometer.conf file." +msgid "Add ResellerAdmin to the operator_roles parameter of that same file:" msgstr "" -#: ./doc/install-guide/section_ceilometer-swift.xml:55(para) -msgid "Add ResellerAdmin to the operator_roles parameter of that same file:" +#: ./doc/install-guide/section_ceilometer-swift.xml:54(para) +msgid "Add the system user swift to the system group ceilometer to give Object Storage access to the ceilometer.conf file." msgstr "" #: ./doc/install-guide/section_ceilometer-swift.xml:60(para) @@ -3204,7 +3204,7 @@ msgid "Add the Data processing service" msgstr "" #: ./doc/install-guide/ch_sahara.xml:8(para) -msgid "The Data processing service (sahara) enables users to provide a scalable data processing stack and associated management interfaces. This includes provision and operation of data processing clusters as well as scheduling and operation of data processing jobs." +msgid "The Data processing service (sahara) enables users to provide a scalable data processing stack and associated management interfaces. This includes provisioning and operation of data processing clusters as well as scheduling and operation of data processing jobs." msgstr "" #. When image changes, this message will be marked fuzzy or untranslated for you. diff --git a/doc/install-guide/locale/ja.po b/doc/install-guide/locale/ja.po index 6393557bc0..ab59797dc9 100644 --- a/doc/install-guide/locale/ja.po +++ b/doc/install-guide/locale/ja.po @@ -5,9 +5,9 @@ msgid "" msgstr "" "Project-Id-Version: OpenStack Manuals\n" -"POT-Creation-Date: 2015-03-03 19:39+0000\n" -"PO-Revision-Date: 2015-03-04 04:00+0000\n" -"Last-Translator: Tomoyuki KATO \n" +"POT-Creation-Date: 2015-03-04 23:13+0000\n" +"PO-Revision-Date: 2015-03-04 07:27+0000\n" +"Last-Translator: openstackjenkins \n" "Language-Team: Japanese (http://www.transifex.com/projects/p/openstack-manuals-i18n/language/ja/)\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" @@ -969,17 +969,17 @@ msgstr "ceilometer を同じファイルの pipeline #: ./doc/install-guide/section_ceilometer-swift.xml49(para) msgid "" +"Add ResellerAdmin to the " +"operator_roles parameter of that same file:" +msgstr "同じファイルの operator_roles パラメーターに ResellerAdmin を追加します。" + +#: ./doc/install-guide/section_ceilometer-swift.xml54(para) +msgid "" "Add the system user swift to the system group " "ceilometer to give Object Storage access to the " "ceilometer.conf file." msgstr "システムユーザー swift をシステムグループ ceilometer に追加して、Object Storage による ceilometer.conf へのアクセス権を与えます。" -#: ./doc/install-guide/section_ceilometer-swift.xml55(para) -msgid "" -"Add ResellerAdmin to the " -"operator_roles parameter of that same file:" -msgstr "同じファイルの operator_roles パラメーターに ResellerAdmin を追加します。" - #: ./doc/install-guide/section_ceilometer-swift.xml60(para) msgid "Restart the service with its new settings:" msgstr "新しい設定を用いてサービスを再起動します。" @@ -5386,9 +5386,9 @@ msgstr "Data processing の追加" msgid "" "The Data processing service (sahara) enables users to provide a scalable " "data processing stack and associated management interfaces. This includes " -"provision and operation of data processing clusters as well as scheduling " -"and operation of data processing jobs." -msgstr "Data processing (sahara) は、ユーザーがスケーラブルなデータ処理スタックと関連する管理インターフェースを提供できます。これには、データ処理クラスターの展開および運用、データ処理ジョブのスケジュールおよび運用を含みます。" +"provisioning and operation of data processing clusters as well as scheduling" +" and operation of data processing jobs." +msgstr "" #. When image changes, this message will be marked fuzzy or untranslated for #. you. diff --git a/doc/install-guide/locale/ko_KR.po b/doc/install-guide/locale/ko_KR.po index 7d237e34ea..e52c02086d 100644 --- a/doc/install-guide/locale/ko_KR.po +++ b/doc/install-guide/locale/ko_KR.po @@ -17,8 +17,8 @@ msgid "" msgstr "" "Project-Id-Version: OpenStack Manuals\n" -"POT-Creation-Date: 2015-03-03 19:39+0000\n" -"PO-Revision-Date: 2015-03-03 06:31+0000\n" +"POT-Creation-Date: 2015-03-04 23:13+0000\n" +"PO-Revision-Date: 2015-03-04 07:27+0000\n" "Last-Translator: openstackjenkins \n" "Language-Team: Korean (Korea) (http://www.transifex.com/projects/p/openstack-manuals-i18n/language/ko_KR/)\n" "MIME-Version: 1.0\n" @@ -981,17 +981,17 @@ msgstr "같은 파일의 pipeline 매개 변수에 c #: ./doc/install-guide/section_ceilometer-swift.xml49(para) msgid "" +"Add ResellerAdmin to the " +"operator_roles parameter of that same file:" +msgstr "" + +#: ./doc/install-guide/section_ceilometer-swift.xml54(para) +msgid "" "Add the system user swift to the system group " "ceilometer to give Object Storage access to the " "ceilometer.conf file." msgstr "" -#: ./doc/install-guide/section_ceilometer-swift.xml55(para) -msgid "" -"Add ResellerAdmin to the " -"operator_roles parameter of that same file:" -msgstr "" - #: ./doc/install-guide/section_ceilometer-swift.xml60(para) msgid "Restart the service with its new settings:" msgstr "새로운 설정을 반영하기 위해 다시 시작 하십시오:" @@ -5398,8 +5398,8 @@ msgstr "" msgid "" "The Data processing service (sahara) enables users to provide a scalable " "data processing stack and associated management interfaces. This includes " -"provision and operation of data processing clusters as well as scheduling " -"and operation of data processing jobs." +"provisioning and operation of data processing clusters as well as scheduling" +" and operation of data processing jobs." msgstr "" #. When image changes, this message will be marked fuzzy or untranslated for diff --git a/doc/install-guide/locale/pt_BR.po b/doc/install-guide/locale/pt_BR.po index f23def7e73..299ea397ee 100644 --- a/doc/install-guide/locale/pt_BR.po +++ b/doc/install-guide/locale/pt_BR.po @@ -13,8 +13,8 @@ msgid "" msgstr "" "Project-Id-Version: OpenStack Manuals\n" -"POT-Creation-Date: 2015-03-03 19:39+0000\n" -"PO-Revision-Date: 2015-03-03 06:31+0000\n" +"POT-Creation-Date: 2015-03-04 23:13+0000\n" +"PO-Revision-Date: 2015-03-04 07:27+0000\n" "Last-Translator: openstackjenkins \n" "Language-Team: Portuguese (Brazil) (http://www.transifex.com/projects/p/openstack-manuals-i18n/language/pt_BR/)\n" "MIME-Version: 1.0\n" @@ -977,17 +977,17 @@ msgstr "Adicione ceilometer ao parâmetro pipelineResellerAdmin to the " +"operator_roles parameter of that same file:" +msgstr "Adicione ResellerAdmin ao parâmetro operator_roles do mesmo arquivo:" + +#: ./doc/install-guide/section_ceilometer-swift.xml54(para) +msgid "" "Add the system user swift to the system group " "ceilometer to give Object Storage access to the " "ceilometer.conf file." msgstr "Adicione o usuário do sistema swift ao grupo de sistema ceilometer para dar acesso para o Object Storage ao arquivo ceilometer.conf." -#: ./doc/install-guide/section_ceilometer-swift.xml55(para) -msgid "" -"Add ResellerAdmin to the " -"operator_roles parameter of that same file:" -msgstr "Adicione ResellerAdmin ao parâmetro operator_roles do mesmo arquivo:" - #: ./doc/install-guide/section_ceilometer-swift.xml60(para) msgid "Restart the service with its new settings:" msgstr "Reinicie o serviço com as novas configurações:" @@ -5394,9 +5394,9 @@ msgstr "Adicionar o serviço de Processamento de Dados" msgid "" "The Data processing service (sahara) enables users to provide a scalable " "data processing stack and associated management interfaces. This includes " -"provision and operation of data processing clusters as well as scheduling " -"and operation of data processing jobs." -msgstr "O serviço de Processamento de Dados (sahara) habilita os usuários a fornecer uma pilha escalável de processamento de dados e interfaces de gerenciamento associadas. Isto inclui o provisionamento de clusters de processamento de dados, bem como agendamento e operação de tarefas de processamento de dados." +"provisioning and operation of data processing clusters as well as scheduling" +" and operation of data processing jobs." +msgstr "" #. When image changes, this message will be marked fuzzy or untranslated for #. you. diff --git a/doc/install-guide/locale/ru.po b/doc/install-guide/locale/ru.po index 00a2234797..54caf0ee06 100644 --- a/doc/install-guide/locale/ru.po +++ b/doc/install-guide/locale/ru.po @@ -10,8 +10,8 @@ msgid "" msgstr "" "Project-Id-Version: OpenStack Manuals\n" -"POT-Creation-Date: 2015-03-03 19:39+0000\n" -"PO-Revision-Date: 2015-03-03 06:31+0000\n" +"POT-Creation-Date: 2015-03-04 23:13+0000\n" +"PO-Revision-Date: 2015-03-04 07:27+0000\n" "Last-Translator: openstackjenkins \n" "Language-Team: Russian (http://www.transifex.com/projects/p/openstack-manuals-i18n/language/ru/)\n" "MIME-Version: 1.0\n" @@ -974,17 +974,17 @@ msgstr "" #: ./doc/install-guide/section_ceilometer-swift.xml49(para) msgid "" +"Add ResellerAdmin to the " +"operator_roles parameter of that same file:" +msgstr "Добавьте ResellerAdmin в параметр operator_roles того же файла:" + +#: ./doc/install-guide/section_ceilometer-swift.xml54(para) +msgid "" "Add the system user swift to the system group " "ceilometer to give Object Storage access to the " "ceilometer.conf file." msgstr "" -#: ./doc/install-guide/section_ceilometer-swift.xml55(para) -msgid "" -"Add ResellerAdmin to the " -"operator_roles parameter of that same file:" -msgstr "Добавьте ResellerAdmin в параметр operator_roles того же файла:" - #: ./doc/install-guide/section_ceilometer-swift.xml60(para) msgid "Restart the service with its new settings:" msgstr "Перезагрузите службу для принятия изменений:" @@ -5391,8 +5391,8 @@ msgstr "Добавление службы Обработки Данных" msgid "" "The Data processing service (sahara) enables users to provide a scalable " "data processing stack and associated management interfaces. This includes " -"provision and operation of data processing clusters as well as scheduling " -"and operation of data processing jobs." +"provisioning and operation of data processing clusters as well as scheduling" +" and operation of data processing jobs." msgstr "" #. When image changes, this message will be marked fuzzy or untranslated for