openstack/openstack-manuals
Code Issues Proposed changes
d2f306e218
openstack-manuals/doc/arch-design/locale/zh_CN.po
OpenStack Proposal Bot 6ee25be6ef Imported Translations from Zanata 
For more information about this automatic import see:
https://wiki.openstack.org/wiki/Translations/Infrastructure

Change-Id: Ibc5ad69983686618e043d21b3fbf63d7554adecc
2015-09-26 06:18:48 +00:00

4975 lines
230 KiB
Plaintext
Raw Blame History

This file contains ambiguous Unicode characters

This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

# Translators:
# apporc watson <appleorchard2000@gmail.com>, 2015
# Chen Peng <goldenarmour@sina.com>, 2015
# Hunt Xu <mhuntxu@gmail.com>, 2015
# johnwoo_lee <lijiangsheng1@gmail.com>, 2015
# Hunt Xu <mhuntxu@gmail.com>, 2015
# 颜海峰 <yanheven@gmail.com>, 2015
#
#
# OpenStack Infra <zanata@openstack.org>, 2015. #zanata
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"POT-Creation-Date: 2015-09-26 04:56+0000\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"PO-Revision-Date: 2015-09-02 02:18+0000\n"
"Last-Translator: openstackjenkins <jenkins@openstack.org>\n"
"Language-Team: Chinese (China) (http://www.transifex.com/openstack/openstack-"
"manuals-i18n/language/zh_CN/)\n"
"Language: zh-CN\n"
"Plural-Forms: nplurals=1; plural=0;\n"
"X-Generator: Zanata 3.7.1\n"
msgid ""
"10 GbE horizontally scalable spine leaf back-end storage and front end "
"network."
msgstr "10 GbE 可水平扩展的分布式核心后端存储及前端网络。"
msgid ""
"10 GbE horizontally scalable spine leaf back-end storage and front-end "
"network"
msgstr "10 GbE 可水平扩展的分布式核心后端存储及前端网络。"
msgid "100 PB Tape"
msgstr "100 PB 磁带"
msgid "120 PB HDD"
msgstr "120 PB 硬盘"
msgid "1600 = (16 (number of physical cores)) / 2"
msgstr "1600 = (16 x (物理核数)) / 2"
msgid ""
"1U rack-mounted servers have the ability to offer greater server density "
"than a blade server solution, but are often limited to dual-socket, multi-"
"core CPU configurations."
msgstr ""
"1U机架式服务器要比刀片服务解决方案提供更大的服务器密度。但是会有双CPU插槽、多"
"核CPU配置的限制。"
msgid ""
"1U rack-mounted servers occupy only a single rack unit. Their benefits "
"include high density, support for dual-socket multi-core CPUs, and support "
"for reasonable RAM amounts. This form factor offers limited storage "
"capacity, limited network capacity, and limited expandability."
msgstr ""
"1U机架式服务器仅占用1U的机柜空间，他们的有点包括高密度，支持双插槽多核的CPU，"
"支持内存扩展。局限性就是，有限的存储容量、有限的网络容量，以及有限的可扩展"
"性。"
msgid "2.5 Mega Watts"
msgstr "2.5 晚瓦特"
msgid "20000 cores"
msgstr "20000 个核"
msgid "2014"
msgstr "2014"
msgid "2014-07-21"
msgstr "2014-07-21"
msgid "2014-10-15"
msgstr "2014-10-15"
msgid "2015"
msgstr "2015"
msgid ""
"2U rack-mounted servers offer the expanded storage and networking capacity "
"that 1U servers tend to lack, but with a corresponding decrease in server "
"density (half the density offered by 1U rack-mounted servers)."
msgstr ""
"2U的机架式服务器相比1U服务器，提供可扩展的存储和网络容量，但是相应的降低了服"
"务器密度(1U机架式服务器密度的一半)"
msgid ""
"2U rack-mounted servers provide quad-socket, multi-core CPU support but with "
"a corresponding decrease in server density (half the density offered by 1U "
"rack-mounted servers)."
msgstr ""
"2U机架式服务器提供四插槽、多核CPU的支持，但是它相应的降低了服务器密度(相当于"
"1U机架式服务器的一半)。"
msgid "2x10 GbE back-end bonds"
msgstr "2x10 GbE 后端绑定"
msgid "2x10 GbE bonded front end"
msgstr "2x10 GbE 绑定的前端"
msgid "3.5 Mega Watts"
msgstr "3.5 万瓦特"
msgid "310 TB Memory"
msgstr "310 TB 内存"
msgid "3x proxies"
msgstr "3x 代理"
msgid "5 storage servers for caching layer 24x1 TB SSD"
msgstr "5 台作为缓存池的存储服务器，每台 24x1 TB SSD"
msgid "6 PB HDD"
msgstr "6 PB 硬盘"
msgid "91000 cores"
msgstr "91000 个核"
msgid ""
"<glossterm baseform=\"cell\">Cells</glossterm> provide the ability to "
"subdivide the compute portion of an OpenStack installation, including "
"regions, while still exposing a single endpoint. Each region has an API cell "
"along with a number of compute cells where the workloads actually run. Each "
"cell has its own database and message queue setup (ideally clustered), "
"providing the ability to subdivide the load on these subsystems, improving "
"overall performance."
msgstr ""
"<glossterm baseform=\"cell\">单元</glossterm>提供了对一个 OpenStack 环境，也"
"包括区域中的计算部分进行细分的功能，同时保持对外的展现仍然为单个入口点。在每"
"个区域中将会为一系列实际承担负载的计算单元创建一个 API 单元。每个单元拥有其自"
"己的数据库和消息队列(理想情况下是集群化的)，并提供将负载细分到这些子系统中的"
"功能，以提高整体性能。"
msgid ""
"<glossterm>Orchestration</glossterm> module (<glossterm>heat</glossterm>)"
msgstr ""
"<glossterm>Orchestration</glossterm> 模块 (<glossterm>heat</glossterm>)"
msgid ""
"<glossterm>Telemetry</glossterm> module (<glossterm>ceilometer</glossterm>)"
msgstr ""
"<glossterm>Telemetry</glossterm> module (<glossterm>ceilometer</glossterm>)"
msgid ""
"<link linkend=\"arch-guide-openstack-on-openstack\">OpenStack on OpenStack</"
"link>: describes building a multi-tiered cloud by running OpenStack on top "
"of an OpenStack installation."
msgstr ""
"<link linkend=\"arch-guide-openstack-on-openstack\">OpenStack 上的 "
"OpenStack</link>：一些机构认为通过在一个 OpenStack 部署之上运行 OpenStack 的"
"方式来构建多层次的云有其技术上的意义。"
msgid ""
"<link linkend=\"desktop-as-a-service\">Desktop-as-a-Service</link>: "
"describes running a virtualized desktop environment in a cloud "
"(<glossterm>Desktop-as-a-Service</glossterm>). This applies to private and "
"public clouds."
msgstr ""
"<link linkend=\"desktop-as-a-service\">桌面即服务</link>：这是为希望在云环境"
"中运行(<glossterm>桌面即服务</glossterm>)所准备的，在私有云以及公有云的情景下"
"都可用。"
msgid ""
"<link linkend=\"software-defined-networking-sdn\">Software-defined "
"networking (SDN)</link>: describes both running an SDN controller from "
"within OpenStack as well as participating in a software-defined network."
msgstr ""
"<link linkend=\"software-defined-networking-sdn\">软件定义网络(SDN)</link>："
"这种场景详细介绍了在 OpenStack 之中运行 SDN 控制器以及 OpenStack 加入到一个软"
"件定义的网络中的情况。"
msgid ""
"<link linkend=\"specialized-hardware\">Specialized hardware</link>: "
"describes the use of specialized hardware devices from within the OpenStack "
"environment."
msgstr ""
"<link linkend=\"specialized-hardware\">专门的硬件</link>：有一些非常特别的情"
"况可能需要在 OpenStack 环境中使用专门的硬件设备。"
msgid ""
"<link linkend=\"specialized-networking-example\">Specialized networking</"
"link>: describes running networking-oriented software that may involve "
"reading packets directly from the wire or participating in routing protocols."
msgstr ""
"<link linkend=\"specialized-networking-example\">特殊的网络应用</link>：此节"
"介绍运行可能涉及直接从网线上读取数据包或者参与路由协议的面向联网的软件。"
#. When image changes, this message will be marked fuzzy or untranslated for you.
#. It doesn't matter what you translate it to: it's not used at all.
msgid ""
"@@image: '../figures/Compute_NSX.png'; md5=1745487faf16b74b13f80ffd837f43a0"
msgstr ""
"@@image: '../figures/Compute_NSX.png'; md5=1745487faf16b74b13f80ffd837f43a0"
#. When image changes, this message will be marked fuzzy or untranslated for you.
#. It doesn't matter what you translate it to: it's not used at all.
msgid ""
"@@image: '../figures/Compute_Tech_Bin_Packing_CPU_optimized1.png'; "
"md5=45084140c29e59a459d6b0af9b47642a"
msgstr ""
"@@image: '../figures/Compute_Tech_Bin_Packing_CPU_optimized1.png'; "
"md5=45084140c29e59a459d6b0af9b47642a"
#. When image changes, this message will be marked fuzzy or untranslated for you.
#. It doesn't matter what you translate it to: it's not used at all.
msgid ""
"@@image: '../figures/Compute_Tech_Bin_Packing_General1.png'; "
"md5=34f2f0b656a66124016d2484fb96068b"
msgstr ""
"@@image: '../figures/Compute_Tech_Bin_Packing_General1.png'; "
"md5=34f2f0b656a66124016d2484fb96068b"
#. When image changes, this message will be marked fuzzy or untranslated for you.
#. It doesn't matter what you translate it to: it's not used at all.
msgid ""
"@@image: '../figures/General_Architecture3.png'; "
"md5=278d469e1d026634b3682209c454bff1"
msgstr ""
"@@image: '../figures/General_Architecture3.png'; "
"md5=278d469e1d026634b3682209c454bff1"
#. When image changes, this message will be marked fuzzy or untranslated for you.
#. It doesn't matter what you translate it to: it's not used at all.
msgid ""
"@@image: '../figures/Generic_CERN_Architecture.png'; "
"md5=f5ec57432a0b3bd35efeaa25e84d9947"
msgstr ""
"@@image: '../figures/Generic_CERN_Architecture.png'; "
"md5=f5ec57432a0b3bd35efeaa25e84d9947"
#. When image changes, this message will be marked fuzzy or untranslated for you.
#. It doesn't matter what you translate it to: it's not used at all.
msgid ""
"@@image: '../figures/Generic_CERN_Example.png'; "
"md5=268e2171493d49ff3cc791071a98b49e"
msgstr ""
"@@image: '../figures/Generic_CERN_Example.png'; "
"md5=268e2171493d49ff3cc791071a98b49e"
#. When image changes, this message will be marked fuzzy or untranslated for you.
#. It doesn't matter what you translate it to: it's not used at all.
msgid ""
"@@image: '../figures/Massively_Scalable_Cells_+_regions_+_azs.png'; "
"md5=87d08365fefde431d6d055daf17d7d0e"
msgstr ""
"@@image: '../figures/Massively_Scalable_Cells_+_regions_+_azs.png'; "
"md5=87d08365fefde431d6d055daf17d7d0e"
#. When image changes, this message will be marked fuzzy or untranslated for you.
#. It doesn't matter what you translate it to: it's not used at all.
msgid ""
"@@image: '../figures/Multi-Cloud_Priv-AWS4.png'; "
"md5=3bba96b0b6ac0341a05581b00160ff17"
msgstr ""
"@@image: '../figures/Multi-Cloud_Priv-AWS4.png'; "
"md5=3bba96b0b6ac0341a05581b00160ff17"
#. When image changes, this message will be marked fuzzy or untranslated for you.
#. It doesn't matter what you translate it to: it's not used at all.
msgid ""
"@@image: '../figures/Multi-Cloud_Priv-Pub3.png'; "
"md5=8fdb44f876665e2aa1bd793607c4537e"
msgstr ""
"@@image: '../figures/Multi-Cloud_Priv-Pub3.png'; "
"md5=8fdb44f876665e2aa1bd793607c4537e"
#. When image changes, this message will be marked fuzzy or untranslated for you.
#. It doesn't matter what you translate it to: it's not used at all.
msgid ""
"@@image: '../figures/Multi-Cloud_failover2.png'; "
"md5=5a7be4a15d381288659c7268dff6724b"
msgstr ""
"@@image: '../figures/Multi-Cloud_failover2.png'; "
"md5=5a7be4a15d381288659c7268dff6724b"
#. When image changes, this message will be marked fuzzy or untranslated for you.
#. It doesn't matter what you translate it to: it's not used at all.
msgid ""
"@@image: '../figures/Multi-Site_Customer_Edge.png'; "
"md5=01850cf774e7075bd7202c6e7f087f36"
msgstr ""
"@@image: '../figures/Multi-Site_Customer_Edge.png'; "
"md5=01850cf774e7075bd7202c6e7f087f36"
#. When image changes, this message will be marked fuzzy or untranslated for you.
#. It doesn't matter what you translate it to: it's not used at all.
msgid ""
"@@image: '../figures/Multi-Site_shared_keystone1.png'; "
"md5=eaef18e7f04eec7e3f8968ad69aed7d3"
msgstr ""
"@@image: '../figures/Multi-Site_shared_keystone1.png'; "
"md5=eaef18e7f04eec7e3f8968ad69aed7d3"
#. When image changes, this message will be marked fuzzy or untranslated for you.
#. It doesn't matter what you translate it to: it's not used at all.
msgid ""
"@@image: '../figures/Multi-Site_shared_keystone_horizon_swift1.png'; "
"md5=fb80511b491731906fb54d5a1f029f91"
msgstr ""
"@@image: '../figures/Multi-Site_shared_keystone_horizon_swift1.png'; "
"md5=fb80511b491731906fb54d5a1f029f91"
#. When image changes, this message will be marked fuzzy or untranslated for you.
#. It doesn't matter what you translate it to: it's not used at all.
msgid ""
"@@image: '../figures/Multi-site_Geo_Redundant_LB.png'; "
"md5=c94a96f6084c2e50a0eb6846f6fde479"
msgstr ""
"@@image: '../figures/Multi-site_Geo_Redundant_LB.png'; "
"md5=c94a96f6084c2e50a0eb6846f6fde479"
#. When image changes, this message will be marked fuzzy or untranslated for you.
#. It doesn't matter what you translate it to: it's not used at all.
msgid ""
"@@image: '../figures/Network_Cloud_Storage2.png'; "
"md5=3cd3ce6b19b20ecd7d22af03731cc7cd"
msgstr ""
"@@image: '../figures/Network_Cloud_Storage2.png'; "
"md5=3cd3ce6b19b20ecd7d22af03731cc7cd"
#. When image changes, this message will be marked fuzzy or untranslated for you.
#. It doesn't matter what you translate it to: it's not used at all.
msgid ""
"@@image: '../figures/Network_Web_Services1.png'; "
"md5=7ad46189444753336edd957108a1a92b"
msgstr ""
"@@image: '../figures/Network_Web_Services1.png'; "
"md5=7ad46189444753336edd957108a1a92b"
#. When image changes, this message will be marked fuzzy or untranslated for you.
#. It doesn't matter what you translate it to: it's not used at all.
msgid ""
"@@image: '../figures/Special_case_SDN_external.png'; "
"md5=12d9e840a0a10a5abcf1a2c1f6f80965"
msgstr ""
"@@image: '../figures/Special_case_SDN_external.png'; "
"md5=12d9e840a0a10a5abcf1a2c1f6f80965"
#. When image changes, this message will be marked fuzzy or untranslated for you.
#. It doesn't matter what you translate it to: it's not used at all.
msgid ""
"@@image: '../figures/Special_case_SDN_hosted.png'; "
"md5=93f5e5b90b5aea50d24a098ba80c805d"
msgstr ""
"@@image: '../figures/Special_case_SDN_hosted.png'; "
"md5=93f5e5b90b5aea50d24a098ba80c805d"
#. When image changes, this message will be marked fuzzy or untranslated for you.
#. It doesn't matter what you translate it to: it's not used at all.
msgid ""
"@@image: '../figures/Specialized_Hardware2.png'; "
"md5=f8477d5d015f4c6d4fcd56d511f14ef9"
msgstr ""
"@@image: '../figures/Specialized_Hardware2.png'; "
"md5=f8477d5d015f4c6d4fcd56d511f14ef9"
#. When image changes, this message will be marked fuzzy or untranslated for you.
#. It doesn't matter what you translate it to: it's not used at all.
msgid ""
"@@image: '../figures/Specialized_OOO.png'; "
"md5=65a8e3666ebf09a0145c61bc1d472144"
msgstr ""
"@@image: '../figures/Specialized_OOO.png'; "
"md5=65a8e3666ebf09a0145c61bc1d472144"
#. When image changes, this message will be marked fuzzy or untranslated for you.
#. It doesn't matter what you translate it to: it's not used at all.
msgid ""
"@@image: '../figures/Specialized_VDI1.png'; "
"md5=77729426d59881476de9a03e1ee8a22c"
msgstr ""
"@@image: '../figures/Specialized_VDI1.png'; "
"md5=77729426d59881476de9a03e1ee8a22c"
#. When image changes, this message will be marked fuzzy or untranslated for you.
#. It doesn't matter what you translate it to: it's not used at all.
msgid ""
"@@image: '../figures/Storage_Database_+_Object5.png'; "
"md5=a0cb2374c3515b8f3203ebdc7bb7dbbf"
msgstr ""
"@@image: '../figures/Storage_Database_+_Object5.png'; "
"md5=a0cb2374c3515b8f3203ebdc7bb7dbbf"
#. When image changes, this message will be marked fuzzy or untranslated for you.
#. It doesn't matter what you translate it to: it's not used at all.
msgid ""
"@@image: '../figures/Storage_Hadoop3.png'; "
"md5=bdc6373caede70b37209de260616b255"
msgstr ""
"@@image: '../figures/Storage_Hadoop3.png'; "
"md5=bdc6373caede70b37209de260616b255"
#. When image changes, this message will be marked fuzzy or untranslated for you.
#. It doesn't matter what you translate it to: it's not used at all.
msgid ""
"@@image: '../figures/Storage_Object.png'; "
"md5=ad0b4ee39c96ab081a368ef7857479a5"
msgstr ""
"@@image: '../figures/Storage_Object.png'; "
"md5=ad0b4ee39c96ab081a368ef7857479a5"
msgid ""
"A common requirement is to define different roles for the different cloud "
"administration functions. An example would be a requirement to segregate the "
"duties and permissions by site."
msgstr ""
"一个常见的需求是为不同的云管理功能定义不同的角色。此例即是站点需要合并职责和"
"权限的需求。"
msgid ""
"A complete list of supported hypervisors and their capabilities can be found "
"at <link xlink:href=\"https://wiki.openstack.org/wiki/HypervisorSupportMatrix"
"\">OpenStack Hypervisor Support Matrix</link>."
msgstr ""
"支持hypervisor和它们的兼容性的完整列表可以从<link xlink:href=\\\"https://"
"wiki.openstack.org/wiki/HypervisorSupportMatrix\\\">https://wiki.openstack."
"org/wiki/HypervisorSupportMatrix</link>页面找到。"
msgid "A disk within a single node"
msgstr "单个节点上的一块磁盘"
msgid ""
"A firewall, switches and load balancers on the public facing network "
"connections."
msgstr "防火墙、交换机、以及负载均衡设备在公网中直接面向全网的连接。"
msgid ""
"A general purpose OpenStack cloud design should incorporate the core "
"OpenStack services to provide a wide range of services to end-users. The "
"OpenStack core services recommended in a general purpose cloud are:"
msgstr ""
"通用型OpenStack云的设计，使核心的OpenStack服务的互相紧密配合为最终用户提供广"
"泛的服务。在通用型云中建议的OpenStack核心服务有："
msgid ""
"A general purpose cloud is designed to have a range of potential uses or "
"functions; not specialized for specific use cases. General purpose "
"architecture is designed to address 80% of potential use cases available. "
"The infrastructure, in itself, is a specific use case, enabling it to be "
"used as a base model for the design process. General purpose clouds are "
"designed to be platforms that are suited for general purpose applications."
msgstr ""
"通用型云被设计为有一系列潜在用途或功能，不是为特殊的用例特殊设计。通用型架构"
"是为满足80%用例而设计的。基础设施其本身就是一非常特别的用例，在设计过程将之用"
"于基本模型未尝不可。通用型云被设计为适合通用应用的平台。"
msgid ""
"A general purpose cloud may also include OpenStack <glossterm>Object "
"Storage</glossterm> (<glossterm>swift</glossterm>). OpenStack "
"<glossterm>Block Storage</glossterm> (<glossterm>cinder</glossterm>). These "
"may be selected to provide storage to applications and instances."
msgstr ""
"通用型云还包括OpenStack <glossterm>对象存储</glossterm> (<glossterm>swift</"
"glossterm>).。选择OpenStack <glossterm>块存储</glossterm> "
"(<glossterm>cinder</glossterm>) 是为应用和实例提供持久性的存储，"
msgid ""
"A hybrid cloud architecture involves multiple vendors and technical "
"architectures. These architectures may be more expensive to deploy and "
"maintain. Operational costs can be higher because of the need for more "
"sophisticated orchestration and brokerage tools than in other architectures. "
"In contrast, overall operational costs might be lower by virtue of using a "
"cloud brokerage tool to deploy the workloads to the most cost effective "
"platform."
msgstr ""
"混合云架构涉及到多个提供商和技术架构。这些架构也许为部署和维护付出高额的费"
"用。运维花费更高的原因在于相比与其它架构需要更多复杂的编排以及额外的工具。相"
"比之下，整体运营成本可能在最具成本效益的平台中使用云运营工具部署负载会降低。"
msgid ""
"A measure of how many servers can fit into a given measure of physical "
"space, such as a rack unit [U]."
msgstr ""
"关于多少台服务器能够放下到一个给定尺寸的物理空间的量度，比如一个机柜单位[U]。"
msgid ""
"A network designed on layer-2 protocols has advantages over one designed on "
"layer-3 protocols. In spite of the difficulties of using a bridge to perform "
"the network role of a router, many vendors, customers, and service providers "
"choose to use Ethernet in as many parts of their networks as possible. The "
"benefits of selecting a layer-2 design are:"
msgstr ""
"基于二层协议设计的网络相比基于三层协议设计的网络有一定优势。尽管使用桥接来扮"
"演路由的网络角色有困难，很多厂商、客户以及服务提供商都选择尽可能多地在他们的"
"网络中使用以太网。选择二层网络设计的好处在于："
msgid ""
"A relationship exists between the size of the compute environment and the "
"supporting OpenStack infrastructure controller nodes requiring support."
msgstr ""
"计算环境的规模和支撑它的OpenStack基础设施控制器节点之间的关系是确定的。"
msgid ""
"A requirement for high availability architecture to meet customer SLA "
"requirements."
msgstr "对于实现高可用架构以满足客户服务等级协议(SLA)需求的要求。"
msgid ""
"A requirement for vendor independence. To avoid hardware or software vendor "
"lock-in, the design should not rely on specific features of a vendor's "
"router or switch."
msgstr ""
"对厂商独立性的需要。要避免硬件或者软件的厂商选择受到限制，设计不应该依赖于某"
"个厂商的路由或者交换机的独特特性。"
msgid "A requirement to be tolerant of rack level failure."
msgstr "对于容忍机柜级别的故障的要求。"
msgid ""
"A requirement to design for cost efficient operations to take advantage of "
"massive scale."
msgstr "对于实现低成本运营以便获益于大规模扩展的设计的需要。"
msgid ""
"A requirement to ensure that there is no single point of failure in the "
"cloud ecosystem."
msgstr "对于保证整个云生态系统中没有单点故障的需要。"
msgid ""
"A requirement to massively scale the ecosystem to support millions of end "
"users."
msgstr "对于大规模地扩展生态系统以满足百万级别终端用户的需要。"
msgid ""
"A requirement to maximize flexibility to architect future production "
"environments."
msgstr "对于最大化灵活性以便构架出未来的生产环境的要求。"
msgid "A requirement to support indeterminate platforms and applications."
msgstr "对于支持不确定的平台和应用的要求。"
msgid ""
"A security domain comprises users, applications, servers or networks that "
"share common trust requirements and expectations within a system. Typically "
"they have the same authentication and authorization requirements and users."
msgstr ""
"一个安全域在一个系统下包括让用户、应用、服务器和网络共享通用的信任需求和预"
"期。典型情况是他们有相同的认证和授权的需求和用户。"
msgid "A shared application development platform"
msgstr "共享的应用开发平台"
msgid ""
"A storage system presents a LUN backed by a set of SSDs using a traditional "
"storage array with OpenStack Block Storage integration or a storage platform "
"such as Ceph or Gluster."
msgstr ""
"一个存储系统被用以抛出 LUN，其后端由通过使用传统的存储阵列与 OpenStack 块存储"
"集成的一系列的 SSD 所支撑，或者是一个类似于 Ceph 或者 Gluster 之类的存储平"
"台。"
msgid "A storage-focused cloud design should include:"
msgstr "存储型的云设计需要包括："
msgid ""
"A storage-focused design might require the ability to use Orchestration to "
"launch instances with Block Storage volumes to perform storage-intensive "
"processing."
msgstr ""
"一个存储型设计也许需要使用Orchestration，能够启动带块设备卷的实例，以满足存储"
"密集型任务处理。"
msgid "A three-node MariaDB and Galera cluster, each with 4 vCPUs and 8 GB RAM"
msgstr "MariaDB安装在3个节点并组成Galera集群，每节点拥有4 vCPU和8GB内存"
msgid "A web application runtime environment"
msgstr "一个web应用程序运行时环境"
msgid ""
"A well thought-out auditing strategy is important in order to be able to "
"quickly track down issues. Keeping track of changes made to security groups "
"and tenant changes can be useful in rolling back the changes if they affect "
"production. For example, if all security group rules for a tenant "
"disappeared, the ability to quickly track down the issue would be important "
"for operational and legal reasons."
msgstr ""
"为了能够快速的追查问题，一个经过好的经过深思熟虑的审计策略是非常重要的。对于"
"安全组和租户的变动保持跟踪，在生产环境中可用于回滚，例如，如果一个租户的安全"
"组规则消失了，能够快速追查问题的能力对于运维来说很重要。"
msgid ""
"A zone within an Object Storage cluster is a logical division. Any of the "
"following may represent a zone:"
msgstr ""
"对象存储集群内的区域是一个逻辑上的划分。一个区域可以是下列情形中的任意之一："
msgid "Active archive, backups and hierarchical storage management."
msgstr "活跃归档、备份和分级存储管理"
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 ""
"将块存储和对象存储服务相比较，增加存储容量和带宽是完全不同的流程。增加块存储"
"的容量是一个相对简单的过程，增加对象存储系统的容量和带宽是一个复杂的任务，需"
"要经过精心的规划和周全的考虑。"
msgid ""
"Additional capabilities can be realized by moving static web content to be "
"served from OpenStack Object Storage containers, and backing the OpenStack "
"Image service with OpenStack Object Storage."
msgstr ""
"附加功能可实现将静态的web内容迁移到OpenStack对象存储中，且使用OpenStack对象存"
"储作为OpenStack镜像服务的后端。"
msgid "Additional considerations"
msgstr "额外的考虑因素"
msgid "Additional hardware"
msgstr "额外的硬件"
msgid ""
"Additional monitoring tools in use include <link xlink:href=\"http://flume."
"apache.org/\">Flume</link>, <link xlink:href=\"http://www.elasticsearch.org/"
"\">Elastic Search</link>, <link xlink:href=\"http://www.elasticsearch.org/"
"overview/kibana/\">Kibana</link>, and the CERN developed <link xlink:href="
"\"http://lemon.web.cern.ch/lemon/index.shtml\">Lemon</link> project."
msgstr ""
"另外使用的监测工具有<link xlink:href=\"http://flume.apache.org/\">Flume</"
"link>, <link xlink:href=\"http://www.elasticsearch.org/\">Elastic Search</"
"link>, <link xlink:href=\"http://www.elasticsearch.org/overview/kibana/"
"\">Kibana</link>, 以及CERN开发的项目<link xlink:href=\"http://lemon.web.cern."
"ch/lemon/index.shtml\">Lemon</link>。"
msgid "Agility"
msgstr "敏捷性"
msgid "Alerting"
msgstr "警告"
msgid ""
"Alerting and notification of responsible teams or automated systems which "
"remediate problems with storage as they arise."
msgstr ""
"对负责团队的警报和通知，或者能够在存储出现问题时能够修复问题的自动化系统。"
msgid ""
"Alexandra Settle (Rackspace) <link xlink:href=\"http://twitter.com/dewsday"
"\">@dewsday</link>"
msgstr ""
"Alexandra Settle (Rackspace) <link xlink:href=\"http://twitter.com/dewsday"
"\">@dewsday</link>"
msgid ""
"All nodes within an OpenStack cloud require network connectivity. In some "
"cases, nodes require access to more than one network segment. The design "
"must encompass sufficient network capacity and bandwidth to ensure that all "
"communications within the cloud, both north-south and east-west traffic have "
"sufficient resources available."
msgstr ""
"一个OpenStack云中所有的节点都需要网络连接。在一些情况下，节点需要访问多个网"
"段。云的设计必须围绕充足的网络容量和带宽去确保所有的通信，无论南北流量还是东"
"西流量都需要有充足的资源可用。"
msgid "Also consider several specialized components:"
msgstr "也会考虑一些特别的组件："
msgid ""
"Although most OpenStack architecture designs fall into one of the seven "
"major scenarios outlined in other sections (compute focused, network "
"focused, storage focused, general purpose, multi-site, hybrid cloud, and "
"massively scalable), there are a few use cases that do not fit into these "
"categories. This section discusses these specialized cases and provide some "
"additional details and design considerations for each use case:"
msgstr ""
"尽管大多数的 OpenStack 架构设计都能归类于其它章节中描述的七种主要场景(计算密"
"集型、网络密集型、存储密集型、通用设计、多站点、混合云以及可大规模扩展)，仍然"
"存在其他一些场景独特到无法归类入主要场景中的任何一个之中。本章将讨论一些这种"
"特殊的应用场景，以及每种场景的细节和设计的考虑因素。"
msgid ""
"An OpenStack general purpose cloud is often considered a starting point for "
"building a cloud deployment. They are designed to balance the components and "
"do not emphasize any particular aspect of the overall computing environment. "
"Cloud design must give equal weight to the compute, network, and storage "
"components. General purpose clouds are found in private, public, and hybrid "
"environments, lending themselves to many different use cases."
msgstr ""
"OpenStack通用型云通常被认为是构建一个云的起点。它们被设计为平衡的组件以及在整"
"体的计算环境中不强调某个特定的领域。云的设计必须对计算、网络、存储等组件作必"
"要的公平权衡。通用型云可以是私有云，也可以是公有云，当然也可以混合的环境，自"
"身可以适用于各种用例。"
msgid ""
"An external load balancing service was used and not the LBaaS in OpenStack "
"because the solution in OpenStack is not redundant and does not have any "
"awareness of geo location."
msgstr ""
"一个额外的负载均衡服务将被使用，而不是OpenStack的LBaaS,因为OpenStack的LBaaS在"
"OpenStack中不是冗余的解决方案而且不具有地理位置的任何特征。"
msgid ""
"An important consideration in running at massive scale is projecting growth "
"and utilization trends in order to plan capital expenditures for the short "
"and long term. Gather utilization meters for compute, network, and storage, "
"along with historical records of these meters. While securing major anchor "
"tenants can lead to rapid jumps in the utilization rates of all resources, "
"the steady adoption of the cloud inside an organization or by consumers in a "
"public offering also creates a steady trend of increased utilization."
msgstr ""
"在大规模场景下运行 OpenStack 还有一个重要的考虑因素，是要对增长和利用率趋势进"
"行规划，从而为短期和长期计划资本性支出。这需要计算、网络以及存储等资源的利用"
"率的测量数据，以及这些数据的历史记录。固定的大客户租户可能造成所有资源的利用"
"率有个迅速的增长，在一个组织内部的对其内部云，或者在公有云上的用户对公开提供"
"的服务等的稳定增长的部署及使用，则会使得利用率出现一个稳定的增长趋势。"
msgid "An object store with a RESTful interface"
msgstr "一个带有 RESTful 接口的对象存储"
msgid ""
"An online classified advertising company wants to run web applications "
"consisting of Tomcat, Nginx and MariaDB in a private cloud. To be able to "
"meet policy requirements, the cloud infrastructure will run in their own "
"data center. The company has predictable load requirements, but requires "
"scaling to cope with nightly increases in demand. Their current environment "
"does not have the flexibility to align with their goal of running an open "
"source API environment. The current environment consists of the following:"
msgstr ""
"一家在线的广告公司，名称暂时保密，打算基于私有云方式运行他们的web应用，属于网"
"站典型的架构：Tomcat + Nginx + MariaDB。 为了迎合他们的合规性需求，云基础设施"
"运行在他们自己的数据中心。公司对负载需求有过预测，但是仍然提出了预防突发性的"
"需求而能够灵活扩展。他们目前的环境不具有灵活的调整目标到运行开源的应用程序接"
"口环境。目前的环境是如下面这样："
msgid "An organization with a diverse geographic footprint."
msgstr "一个有不同地域认证的组织"
msgid ""
"Another consideration regarding network is the fact that legacy networking "
"is entirely managed by the cloud operator; tenants do not have control over "
"network resources. If tenants require the ability to manage and create "
"network resources such as network segments and subnets, it will be necessary "
"to install the OpenStack Networking service to provide network access to "
"instances."
msgstr ""
"另外的考虑是关于基于遗留网络的网络的管理是由云运维人员负责的。租户对网络资源"
"没有控制权。如果租户希望有管理和创建网络资源的能力，如创建、管理一个网段或子"
"网，那么就有必要安装OpenStack网络服务，以提供租户访问网络。"
msgid ""
"Another kind of NAT that may be useful is protocol NAT. In some cases it may "
"be desirable to use only IPv6 addresses on instances and operate either an "
"instance or an external service to provide a NAT-based transition technology "
"such as NAT64 and DNS64. This provides the ability to have a globally "
"routable IPv6 address while only consuming IPv4 addresses as necessary or in "
"a shared manner."
msgstr ""
"另外一种可能有用的 NAT 是协议 NAT。某些情况下，可能需要在实例中只使用 IPv6 地"
"址，然后让一个实例或者外部的服务来提供基于 NAT 的转换技术，比如说 NAT64 和 "
"DNS64。这使得实例都有全局可达的 IPv6 地址，同时只在必要的情况下，或者以共享的"
"方式使用 IPv4 地址。"
msgid ""
"Anthony Veiga (Comcast) <link xlink:href=\"http://twitter.com/daaelar"
"\">@daaelar</link>"
msgstr ""
"Anthony Veiga (Comcast) <link xlink:href=\"http://twitter.com/daaelar"
"\">@daaelar</link>"
msgid "Application awareness"
msgstr "应用的可知性"
msgid "Application cloud readiness"
msgstr "为云准备好应用程序"
msgid "Application momentum"
msgstr "应用增长"
msgid "Application readiness"
msgstr "应用准备"
msgid ""
"Appropriate <literal>user_data</literal> to populate the central DNS servers "
"upon instance launch."
msgstr "当实例启动时，中心DNS服务器会填写合适的<literal>user_data</literal>。"
msgid ""
"Appropriate Telemetry alarms that maintain state of the application and "
"allow for handling of region or instance failure."
msgstr "正确的Telemetry警告，维护着应用的状态且允许掌控region或实例失效。"
msgid "Approximate capacity"
msgstr "大体的容量"
msgid "Approximately 60 Gb of total bandwidth to the back-end storage cluster"
msgstr "到后端存储集群大约 60 Gb 的总带宽"
msgid "Architecture"
msgstr "架构"
msgid "Architecture Guide"
msgstr "架构指南"
msgid ""
"As a baseline product, general purpose clouds do not provide optimized "
"performance for any particular function. While a general purpose cloud "
"should provide enough performance to satisfy average user considerations, "
"performance is not a general purpose cloud customer driver."
msgstr ""
"作为基础产品，通用型云并不对任何特定的功能提供优化性能。虽然通用型云希望能够"
"提供足够的性能以满足所以用户的考虑，但是性能本身并不是通用型云所关注的。"
msgid ""
"As of 2011 CERN operated these two compute centers in Europe with plans to "
"add a third."
msgstr "CERN在2011年准备在欧洲建立第三个数据中心。"
msgid ""
"As you add back-end storage capacity to the system, the partition maps "
"redistribute data amongst the storage nodes. In some cases, this replication "
"consists of extremely large data sets. In these cases, we recommend using "
"back-end replication links that do not contend with tenants' access to data."
msgstr ""
"为系统的后端存储增加了容量后，分区映射会带来数据重新分发到存储节点，在一些情"
"况下，这些复制会带来超大的数据集合，在此种情况下，建议使用后端复制链接，它也"
"不会阻断租户访问数据。"
msgid ""
"Assessing the average workloads and increasing the number of instances that "
"can run within the compute environment by adjusting the overcommit ratio is "
"another option. It is important to remember that changing the CPU overcommit "
"ratio can have a detrimental effect and cause a potential increase in a "
"noisy neighbor. The additional risk of increasing the overcommit ratio is "
"more instances failing when a compute host fails."
msgstr ""
"通过评估平均负载，在计算环境中调整超分配比例来增加运行实例的数量是另外一个办"
"法。重要的是记住，改变CPU超分配比例有负面影响以及引起其它实例故障。加大超分配"
"的比例另外的风险是当计算节点失效后会引发更多的实例失效。"
msgid "Asymmetric links"
msgstr "非对称连接"
msgid ""
"At large scale, management of data operations is a resource intensive "
"process for an organization. Hierarchical storage management (HSM) systems "
"and data grids help annotate and report a baseline data valuation to make "
"intelligent decisions and automate data decisions. HSM enables automated "
"tiering and movement, as well as orchestration of data operations. A data "
"grid is an architecture, or set of services evolving technology, that brings "
"together sets of services enabling users to manage large data sets."
msgstr ""
"在规模到达一定的程度时，数据操作的管理对于整个组织来说就会是一个资源密集型的"
"过程。分级存储管理(HSM)系统以及数据网格能够帮助对数据评估的基准值作出注解以及"
"报告，从而做出正确的决定以及自动化该数据决策。HSM 支持自动化的排列和移动，以"
"及数据操作的协调编排。数据网格是一个架构，或者是一项不断发展的服务集合技术，"
"此项技术能够将多个服务协调到一起，让用户能够管理大规模的数据集合。"
msgid "Auditing"
msgstr "审计"
msgid "Authentication between sites"
msgstr "站点之间的认证"
msgid "Availability"
msgstr "可用性"
msgid "Availability zones"
msgstr "可用域"
msgid ""
"Availability zones provide another mechanism for subdividing an installation "
"or region. They are, in effect, host aggregates exposed for (optional) "
"explicit targeting by users."
msgstr ""
"可用域为细分一个 OpenStack 部署或者区域提供了另外一种机制。实际上，这是明确展"
"现给用户(可选项)的主机聚合。"
msgid "Bare-metal"
msgstr "裸金属"
msgid ""
"Be paranoid: Design for defense in depth and zero tolerance by building in "
"security at every level and between every component. Trust no one."
msgstr ""
"保持偏执：深度设计防御，通过构建在每一层和每个组件之间的安全确保零差错。不信"
"任任何人。"
msgid ""
"Beth Cohen (Verizon) <link xlink:href=\"http://twitter.com/bfcohen"
"\">@bfcohen</link>"
msgstr ""
"Beth Cohen (Verizon) <link xlink:href=\"http://twitter.com/bfcohen"
"\">@bfcohen</link>"
msgid ""
"Between 120 and 140 installations of Nginx and Tomcat, each with 2 vCPUs and "
"4 GB of RAM"
msgstr ""
"Nginx和Tomcat的安装量在120和140之间，每个应用的实例是2 虚拟CPU和4 GB内存"
msgid "Big data"
msgstr "大数据"
msgid "Big data analytics using Hadoop or other distributed data stores"
msgstr "使用Hadoop或其他分布式数据处理程序来分析大数据"
msgid "Block Storage fault tolerance and availability"
msgstr "块存储的容错和可用性"
msgid ""
"Block storage also takes advantage of a number of enterprise storage "
"solutions. These are addressed via a plug-in driver developed by the "
"hardware vendor. A large number of enterprise storage plug-in drivers ship "
"out-of-the-box with OpenStack Block Storage (and many more available via "
"third party channels). General purpose clouds are more likely to use "
"directly attached storage in the majority of block storage nodes, deeming it "
"necessary to provide additional levels of service to tenants which can only "
"be provided by enterprise class storage solutions."
msgstr ""
"块存储还可以利用一些企业级存储解决方案的优势。由硬件厂商开发的插件驱动得以实"
"现。基于OpenStack块存储有大量的企业存储写了它们带外的插件驱动(也有很大一部分"
"是通过第三方渠道来实现的)。作为通用型云使用的是直接挂载存储到块存储节点，如果"
"未来需要为租户提供额外级别的块存储，只须增加企业级的存储解决方案即可。"
msgid ""
"Boot storms, when a high volume of logins occur in a short period of time"
msgstr "启动风暴，再很短的时间内发生了大量的虚拟机同时启动的事"
msgid "Broker"
msgstr "代理"
msgid "Budapest, Hungary"
msgstr "匈牙利布达佩斯"
msgid "Bursting from a private cloud to a public cloud"
msgstr "从私有云突破到公有云"
msgid "Bursting to a public non-OpenStack cloud"
msgstr "突破到一个不是OpenStack的公有云"
msgid "Bursting workloads from private to public OpenStack clouds"
msgstr "从私有云突破负载到公有的OpenStack云"
msgid "Bursting workloads from private to public non-OpenStack clouds"
msgstr "从私有云突破负载到公有的非OpenStack云"
msgid "Business or technical diversity"
msgstr "业务或技术的多样性"
msgid ""
"By definition, a cloud provides end users with the ability to self-provision "
"computing power, storage, networks, and software in a simple and flexible "
"way. The user must be able to scale their resources up to a substantial "
"level without disrupting the underlying host operations. One of the benefits "
"of using a general purpose cloud architecture is the ability to start with "
"limited resources and increase them over time as the user demand grows."
msgstr ""
"根据定义，云提供给最终用户通过简单灵活的方式自适应的计算能力、存储、网络和软"
"件的能力。用户必须能够在不破坏底层主机操作的情况下扩展资源到满足自身。使用通"
"用型云架构的一个优点就是，在有限的资源下启动，随着时间的增加和用户的需求增长"
"而轻松扩张的能力。"
msgid "CPU allocation ratio: 16:1"
msgstr "CPU 超分配比例: 16:1"
msgid "CPU and RAM"
msgstr "CPU 和内存"
msgid "CPU-intensive"
msgstr "CPU密集型"
msgid "Capacity"
msgstr "容量"
msgid "Capacity constraints for a general purpose cloud environment include:"
msgstr "在通用型云环境中的容量限制包括："
msgid "Capacity planning"
msgstr "容量计划"
msgid ""
"Care must be taken when deciding network functionality. Currently, OpenStack "
"supports both the legacy networking (nova-network) system and the newer, "
"extensible OpenStack Networking (neutron). Both have their pros and cons "
"when it comes to providing highly available access. Legacy networking, which "
"provides networking access maintained in the OpenStack Compute code, "
"provides a feature that removes a single point of failure when it comes to "
"routing, and this feature is currently missing in OpenStack Networking. The "
"effect of legacy networking’s multi-host functionality restricts failure "
"domains to the host running that instance."
msgstr ""
"当决定网络功能的时候务必小心谨慎。当前的OpenStack不仅支持遗留网络(nova-"
"network)系统还支持新的，可扩展的OpenStack网络(neutron)。二者在提供高可用访问"
"时有各自的优缺点。遗留网络提供的网络服务的代码是由OpenStack计算来维护的，它可"
"提供移除来自路由的单点故障特性，但是此特性在当前的Openstack网络中不被支持。遗"
"留网络的多主机功能受限于仅在运行实例的主机，一旦失效，此实例将无法被访问。"
msgid "CentOS"
msgstr "CentOS"
msgid "Centralized log collection."
msgstr "日志集中收集"
msgid ""
"Certain hardware form factors may better suit a general purpose OpenStack "
"cloud due to the requirement for equal (or nearly equal) balance of "
"resources. Server hardware must provide the following:"
msgstr ""
"确定硬件的形式，也许更适合通用型OpenStack云，因为通用型有对资源的对等(接近对"
"等)平衡的需求。服务器硬件须提供如下资源平衡细节描述："
msgid ""
"Certain use cases may benefit from exposure to additional devices on the "
"compute node. Examples might include:"
msgstr ""
"在计算节点中使用一些额外的设备对于某些用例有着显著的益处。举几个常见的例子："
msgid "Challenges"
msgstr "挑战"
msgid "Choice of hypervisor"
msgstr "选择Hypervisor"
msgid "Choice of operating system"
msgstr "选择操作系统"
msgid "Cloud storage"
msgstr "云存储"
msgid ""
"Cloud storage consists of many distributed, synonymous resources, which are "
"often referred to as integrated storage clouds. Cloud storage is highly "
"fault tolerant through redundancy and the distribution of data. It is highly "
"durable through the creation of versioned copies, and can be consistent with "
"regard to data replicas."
msgstr ""
"云存储由很多分散的但是同质化的资源所组成，并且通常被称为集成存储云。云存储具"
"有非常高的容错能力，这是通过冗余以及数据的分布存储实现的。通过创建版本化的副"
"本，云存储是非常耐用的，而且对于数据的副本来说，其一致性也是非常高的。"
msgid ""
"Cloud storage is a model of data storage that stores digital data in logical "
"pools and physical storage that spans across multiple servers and locations. "
"Cloud storage commonly refers to a hosted object storage service, however "
"the term also includes other types of data storage that are available as a "
"service, for example block storage."
msgstr ""
"云存储是一种数据存储的模型。这种模型下电子数据存放在逻辑的存储池之中，物理的"
"存储设备则分布在多个服务器或者地点之中。云存储一般来说指的是所支持的对象存储"
"服务，然而，随着发展，这个概念包括了其它能够作为服务提供的数据存储，比如块存"
"储。"
msgid "Cloud storage peering."
msgstr "云存储配对。"
msgid ""
"Cloud storage runs on virtualized infrastructure and resembles broader cloud "
"computing in terms of accessible interfaces, elasticity, scalability, multi-"
"tenancy, and metered resources. You can use cloud storage services from an "
"off-premises service or deploy on-premises."
msgstr ""
"云存储是运行在虚拟化基础设施之上的，并且在可访问接口、弹性、可扩展性、多租户"
"以及可测量资源方面都类似于更广泛意义上的云计算。云存储服务可以是场外的服务，"
"也可以在内部进行部署。"
msgid ""
"Cloud users expect a fully self-service and on-demand consumption model. "
"When an OpenStack cloud reaches the \"massively scalable\" size, expect "
"consumption \"as a service\" in each and every way."
msgstr ""
"云用户同样希望拥有一个完全自服务的和按需消费的模型。当一个 OpenStack 云达"
"到“可大规模扩展”的大小时，意味着它也是被希望以每一方面都“作为服务”来进行消费"
"的。"
msgid "Clustering"
msgstr "集群"
msgid "Common uses of a general purpose cloud include:"
msgstr "通常使用通用性的云包括："
msgid ""
"Companies operating a massively scalable OpenStack cloud also require that "
"operational expenditures (OpEx) be minimized as much as possible. We "
"recommend using cloud-optimized hardware when managing operational overhead. "
"Some of the factors to consider include power, cooling, and the physical "
"design of the chassis. Through customization, it is possible to optimize the "
"hardware and systems for this type of workload because of the scale of these "
"implementations."
msgstr ""
"运营可大规模扩展云的公司，同样也要求业务费用(OpEx)尽可能最小化。需要对运营开"
"销进行管理的时候，我们则建议使用为云场景进行过优化的硬件。还有一些需要考虑的"
"因素包括电源、冷却系统，以及甚至是底架的物理设计。由于这类实现的规模之大，定"
"制硬件和系统以确保它们是优化过的适合完成相关类型的工作，是非常可能的一件事"
"情。"
msgid ""
"Company A has an established data center with a substantial amount of "
"hardware. Migrating the workloads to a public cloud is not feasible."
msgstr ""
"A公司已经拥有显著数量的硬件的数据中心，将负载迁移到公有云中不是可行的方式。"
msgid "Complex, multiple agents"
msgstr "复杂，多个代理程序"
msgid "Complexity"
msgstr "复杂性"
msgid "Compliance and geo-location"
msgstr "合规性和地理位置"
msgid "Components"
msgstr "组件"
msgid "Compute"
msgstr "计算"
msgid "Compute (nova)"
msgstr "计算 (nova)"
msgid "Compute (server) hardware selection"
msgstr "计算(服务器)硬件选择"
msgid "Compute analytics with Data processing service"
msgstr "带数据处理服务的计算分析"
msgid "Compute analytics with parallel file systems"
msgstr "使用并行文件系统的计算分析"
msgid ""
"Compute capacity (CPU cores and RAM capacity) is a secondary consideration "
"for selecting server hardware. As a result, the required server hardware "
"must supply adequate CPU sockets, additional CPU cores, and more RAM; "
"network connectivity and storage capacity are not as critical. The hardware "
"needs to provide enough network connectivity and storage capacity to meet "
"the user requirements, however they are not the primary consideration."
msgstr ""
"在选择服务器硬件时计算能力(CPU核和内存容量)是次要考虑的,服务器硬件必须能够提"
"供更多的CPU插槽，更多的CPU核的数量，以及更多的内存，至于网络连接和存储容量就"
"显得次要一些。硬件需要的配置以提供足够的网络连接和存储容量满足用户的最低需求"
"即可，但是这不是主要需要考虑的。"
msgid "Compute focused"
msgstr "计算型"
msgid "Compute host"
msgstr "计算主机"
msgid ""
"Compute host components can also be upgraded to account for increases in "
"demand; this is known as vertical scaling. Upgrading CPUs with more cores, "
"or increasing the overall server memory, can add extra needed capacity "
"depending on whether the running applications are more CPU intensive or "
"memory intensive."
msgstr ""
"计算主机可以按需求来进行相应的组件升级，这就是传说中的纵向扩展。升级更多核的"
"CPU,增加整台服务器的内存，要视运行的应用是需要CPU更紧张，还是需要内存更急切，"
"以及需要多少。"
msgid "Compute limits"
msgstr "计算限制"
msgid ""
"Compute nodes automatically attach to OpenStack clouds, resulting in a "
"horizontally scaling process when adding extra compute capacity to an "
"OpenStack cloud. Additional processes are required to place nodes into "
"appropriate availability zones and host aggregates. When adding additional "
"compute nodes to environments, ensure identical or functional compatible "
"CPUs are used, otherwise live migration features will break. It is necessary "
"to add rack capacity or network switches as scaling out compute hosts "
"directly affects network and datacenter resources."
msgstr ""
"计算节点自动挂接到OpenStack云，结果就是为OpenStack云添加更多的计算容量，亦即"
"是横向扩展。此流程需要节点是安置在合适的可用区域并且是支持主机聚合。当添加额"
"外的计算节点到环境中时，要确保CPU类型的兼容性，否则可能会使活迁移的功能失效。"
"扩展计算节点直接的结果会影响到网络及数据中心的其他资源，因为需要增加机柜容量"
"以及交换机。"
msgid "Compute resources"
msgstr "计算资源"
msgid ""
"Configuration management tools such as Puppet and Chef enable operations "
"staff to categorize systems into groups based on their roles and thus create "
"configurations and system states that the provisioning system enforces. "
"Systems that fall out of the defined state due to errors or failures are "
"quickly removed from the pool of active nodes and replaced."
msgstr ""
"类似 Puppet 和 Chef 等配置管理工具允许运维人员将系统按照它们的角色进行分组，"
"然后通过配置准备系统，对它们分别创建配置文件以及保证系统的状态。由于错误或者"
"故障而离开预定义的状态的系统很快就会被从活动节点池中移除，并被替换。"
msgid ""
"Connecting specialized network applications to their required resources "
"alters the design of an OpenStack installation. Installations that rely on "
"overlay networks are unable to support a routing participant, and may also "
"block layer-2 listeners."
msgstr ""
"将特殊的网络应用连接至它们所需要的资源能够改变 OpenStack 部署的设计。基于覆盖"
"网络的部署是无法支持路由参与者应用的，而且也可能阻挡二层网络监听者应用。"
msgid "Connectivity"
msgstr "连通性"
msgid ""
"Consideration must be taken when managing the users of the system for both "
"public and private clouds. The identity service allows for LDAP to be part "
"of the authentication process. Including such systems in an OpenStack "
"deployment may ease user management if integrating into existing systems."
msgstr ""
"无论是公有云还是私有云，管理用户的系统必须认真的考虑。身份认证服务允许LDAP作"
"为认证流程的一部分。Including such systems in an OpenStack deployment may "
"ease user management if integrating into existing systems."
msgid "Consistency of images and templates across different sites"
msgstr "镜像和模板在跨不同站点时要保持一致性。"
msgid "Content delivery network"
msgstr "内容分发网络"
msgid "Content distribution."
msgstr "内容分发。"
msgid "Continuous integration/continuous deployment (CI/CD)"
msgstr "持续集成/持续部署(CI/CD)"
msgid "Controller infrastructure"
msgstr "控制器基础设施"
msgid "Controlling traffic with routing metrics is straightforward."
msgstr "使用路由度量进行流量控制非常直观。"
msgid "Copyright details are filled in by the template."
msgstr "版权信息来自于模板"
msgid "Cost"
msgstr "成本"
msgid ""
"Cryptographic routines that benefit from the availability of hardware random "
"number generators to avoid entropy starvation."
msgstr ""
"Cryptographic routines 受益于硬件随机数生成器，以避免entropy starvation。"
msgid "Dashboard (horizon)"
msgstr "仪表盘 (horizon)"
msgid "Data"
msgstr "数据"
msgid "Data analytics with parallel file systems."
msgstr "基于并行文件系统的数据分析。"
msgid "Data center"
msgstr "数据中心"
msgid ""
"Data centers have a specified amount of power fed to a given rack or set of "
"racks. Older data centers may have a power density as power as low as 20 "
"AMPs per rack, while more recent data centers can be architected to support "
"power densities as high as 120 AMP per rack. The selected server hardware "
"must take power density into account."
msgstr ""
"数据中心拥有一定的电源以满足指定的机架或几组机架。老的数据中心拥有的电源密度"
"一个低于每机架20AMP。近年来数据中心通常支持电源密度为高于每机架120 AMP。选择"
"过的服务器硬件必须将电源密度纳入考虑范围。"
msgid ""
"Data compliance policies governing certain types of information needing to "
"reside in certain locations due to regulatory issues - and more importantly, "
"cannot reside in other locations for the same reason."
msgstr ""
"数据合规性-基于常规某些类型的数据需要放在某些位置，同样的原因，不能放在其他位"
"置更加的重要。"
msgid "Data grids"
msgstr "数据网格"
msgid ""
"Data grids are helpful when answering questions around data valuation. Data "
"grids improve decision making through correlation of access patterns, "
"ownership, and business-unit revenue with other metadata values to deliver "
"actionable information about data."
msgstr ""
"数据网格在准确解答关于数据评估的问题方面非常有帮助。当前的信息科学方面的一个"
"根本的挑战就是确定哪些数据值得保存，数据应该在哪个级别的访问和性能上存在，以"
"及数据保留在存储系统当中的时间应该多长。数据网格，通过研究访问模式、所有权、"
"商业单位\n"
"收益以及其它的元数据的值等的相关性，帮助做出相关的决定，提供关于数据的可行信"
"息。"
msgid ""
"Data locality, in which specific data or functionality should be close to "
"users."
msgstr "数据所在地应该接近用户,特别是一些特殊数据或者功能"
msgid ""
"Data ownership policies governing the possession and responsibility for data."
msgstr "管理数据的所有权和责任的数据所有权政策。"
msgid ""
"Data retention policies ensuring storage of persistent data and records "
"management to meet data archival requirements."
msgstr "确保持久化数据的保管和记录管理以符合数据档案化需求的数据保留政策。"
msgid ""
"Data sovereignty policies governing the storage of data in foreign countries "
"or otherwise separate jurisdictions."
msgstr "管理位于外国或者其它辖区的数据存储问题的数据独立性政策。"
msgid "Database software"
msgstr "数据库软件"
msgid ""
"Databases are a common workload that benefit from high performance storage "
"back ends. Although enterprise storage is not a requirement, many "
"environments have existing storage that OpenStack cloud can use as back "
"ends. You can create a storage pool to provide block devices with OpenStack "
"Block Storage for instances as well as object interfaces. In this example, "
"the database I-O requirements are high and demand storage presented from a "
"fast SSD pool."
msgstr ""
"数据库是一种常见的能够从高性能数据后端中获益的负载。尽管企业级的存储并不在需"
"求中，很多环境都已经拥有能够被用作 OpenStack 云后端的存储。如下图中所示，可以"
"划分出一个存储池出来，使用 OpenStack 块存储向实例提供块设备，同样也可以提供对"
"象存储\n"
"接口。在这个例子中，数据库的 I-O 需求非常高，所需的存储是从一个高速的 SSD 池"
"中抛出来的。"
msgid "Databases."
msgstr "数据库。"
msgid "Dependencies"
msgstr "依赖"
msgid ""
"Depending on the selected hypervisor, staff should have the appropriate "
"training and knowledge to support the selected OS and hypervisor "
"combination. If they do not, training will need to be provided which could "
"have a cost impact on the design."
msgstr ""
"依赖于所选定的hypervisor，相关工作人员需要受过对应的培训以及接受相关的知识，"
"才可支持所选定的操作系统和hpervisor组合。如果没有的话，那么在设计中就得考虑培"
"训的提供是需要另外的开销的。"
msgid ""
"Deploying an OpenStack installation using OpenStack Networking with a "
"provider network allows direct layer-2 connectivity to an upstream "
"networking device. This design provides the layer-2 connectivity required to "
"communicate via Intermediate System-to-Intermediate System (ISIS) protocol "
"or to pass packets controlled by an OpenFlow controller. Using the multiple "
"layer-2 plug-in with an agent such as <glossterm>Open vSwitch</glossterm> "
"allows a private connection through a VLAN directly to a specific port in a "
"layer-3 device. This allows a BGP point-to-point link to join the autonomous "
"system. Avoid using layer-3 plug-ins as they divide the broadcast domain and "
"prevent router adjacencies from forming."
msgstr ""
"使用带有提供商网络的 OpenStack 联网方式进行 OpenStack 的部署可以允许直接到上"
"游网络设备的二层网络连接。这种设计提供了通过中间系统到中间系统(ISIS)协议进行"
"通信，或者传输由 OpenFlow 控制器所控制的网络包等功能所需要的二层联网要求。使"
"用比如 <glossterm>Open vSwitch</glossterm> 这类的带有代理程序的多种二层网络插"
"件能够允许通过 VLAN 直接到三层设备上的特定端口的私有连接。这使得之后会加入自"
"治系统的 BGP 点对点连接能够存在。应该尽量避免使用三层网络的插件，因为它们会分"
"隔广播域并且阻止邻接路由器的形成。"
msgid ""
"Design a dense multi-path network core to support multi-directional scaling "
"and flexibility."
msgstr "设计一个密集的多路径网络核心以支持多个方向的扩展和确保灵活性。"
msgid ""
"Design decisions made in each of these areas impacts the rest of the "
"OpenStack architecture design."
msgstr "上述选择项的任何一个设计决定都会影响到其余两个的OpenStack架构设计。"
msgid "Design impacts"
msgstr "对设计的影响"
msgid "Designing OpenStack Block Storage"
msgstr "规划OpenStack块存储"
msgid "Designing OpenStack Object Storage"
msgstr "规划OpenStack对象存储"
msgid ""
"Designing an infrastructure that is suitable to host virtual desktops is a "
"very different task to that of most virtual workloads. For example, the "
"design must consider:"
msgstr ""
"设计一个适用于运行虚拟桌面的基础设施是一个与为其它大部分虚拟化任务进行设计大"
"不相同的工作。该基础设施设计时必须考虑到各种因素，比如以下例子："
msgid "Designing for the cloud"
msgstr "设计云"
msgid "Designing network resources"
msgstr "规划网络资源"
msgid ""
"Designs that incorporate the use of multiple clouds, such as a private cloud "
"and a public cloud offering, are described in the \"Multi-Cloud\" scenario, "
"see <xref linkend=\"multi_site\"/>."
msgstr ""
"设计使用多个云，例如提供一个私有云和公有云的混合，有关“多云”的描述场景，请参"
"考<xref linkend=\"multi_site\"/>。"
msgid "Desktop-as-a-Service"
msgstr "桌面即服务"
msgid ""
"Despite the existence of SLAs, things break: servers go down, network "
"connections are disrupted, or too many tenants on a server make a server "
"unusable. An application must be sturdy enough to contend with these issues."
msgstr ""
"尽管有服务水平协议(SLA)的存在,但是还是会有一些坏的事情发生：服务器宕机，网络"
"连接发生紊乱，多个租户无法访问服务。应用程序必须足够的稳固，以应对上述事情的"
"发生。"
msgid "Determine if the use case has consistent or highly variable latency."
msgstr "决定的是如果用例中拥有并行或高度变化的延迟。"
msgid "Determine the most effective configuration for block storage network."
msgstr "确定块存储网络的最高效配置。"
msgid "Determining whether an application is cloud-ready"
msgstr "决定那些应用程序是可在云中运行"
msgid "Development and testing"
msgstr "开发和测试"
msgid "Diagram"
msgstr "图示"
msgid "Differing SLAs"
msgstr "服务水平协议比较"
msgid "Disaster recovery"
msgstr "灾难恢复"
msgid ""
"Divide and conquer: Pursue partitioning and parallel layering wherever "
"possible. Make components as small and portable as possible. Use load "
"balancing between layers."
msgstr ""
"分离和征服：尽可能分区和并行的分层。尽可能的确保组件足够小且可移植。在层之间"
"使用负载均衡。"
msgid "Docker"
msgstr "Docker"
msgid "Documentation"
msgstr "文档"
msgid "Downtime"
msgstr "宕机时间"
msgid "Durability and resilience"
msgstr "耐久性和弹性"
msgid ""
"Each compute cell provides a complete compute installation, complete with "
"full database and queue installations, scheduler, conductor, and multiple "
"compute hosts. The cells scheduler handles placement of user requests from "
"the single API endpoint to a specific cell from those available. The normal "
"filter scheduler then handles placement within the cell."
msgstr ""
"每个计算单元提供一整个完整的计算环境，包括完整的数据库及消息队列部署、调度"
"器，管理器以及多个计算主机。单元调度器将会把从单个 API 入口点上收到的用户请"
"求，安排到从可用的单元中选出的一个特定单元上。单元内部常规的过滤调度器将负责"
"其内部的这种安排。"
msgid ""
"Ensure that selected OS and hypervisor combinations meet the appropriate "
"scale and performance requirements. The chosen architecture will need to "
"meet the targeted instance-host ratios with the selected OS-hypervisor "
"combinations."
msgstr ""
"确保所选择的操作系统和Hypervisor组合能满足相应的扩展和性能需求。所选择的架构"
"需要满足依据所选择的操作系统-hypervisor组合目标实例-主机比例。"
msgid ""
"Ensure that the design can accommodate regular periodic installations of "
"application security patches while maintaining required workloads. The "
"frequency of security patches for the proposed OS-hypervisor combination "
"will have an impact on performance and the patch installation process could "
"affect maintenance windows."
msgstr ""
"确保设计能够在维护负载需求时能够容纳正常的所安装的应用的安全补丁。为操作系统-"
"hypervisor组合打安全补丁的频率会影响到性能，而且补丁的安装流程也会影响到维护"
"工作。"
msgid ""
"Ensure that the physical data center provides the necessary power for the "
"selected network hardware."
msgstr "确保物理数据中心为选择的网络硬件提供了必要的电力。"
msgid ""
"Ensure that, if storage protocols other than Ethernet are part of the "
"storage solution, the appropriate hardware has been selected. If a "
"centralized storage array is selected, ensure that the hypervisor will be "
"able to connect to that storage array for image storage."
msgstr ""
"确保连通性，如果存储协议作为存储解决方案的一部分使用的是非以太网，那么选择相"
"应的硬件。如果选择了中心化的存储阵列，hypervisor若访问镜像存储就得能够连接到"
"阵列。"
msgid ""
"Environments operating at massive scale typically need their regions or "
"sites subdivided further without exposing the requirement to specify the "
"failure domain to the user. This provides the ability to further divide the "
"installation into failure domains while also providing a logical unit for "
"maintenance and the addition of new hardware. At hyperscale, instead of "
"adding single compute nodes, administrators can add entire racks or even "
"groups of racks at a time with each new addition of nodes exposed via one of "
"the segregation concepts mentioned herein."
msgstr ""
"在大规模场景下运行的环境需要更加细分其区域和站点，同时又不能要求用户指定故障"
"域。者提供了将整个部署更加细分到故障域的能力，同时也为维护和新硬件的添加提供"
"了逻辑上的单元。在超大规模的环境中，管理员可能一次性添加整个机柜或者甚至是一"
"组机柜上的机器，而不是添加单台计算节点。这样子的节点添加过程，将会用到这里所"
"提到的隔离概念。"
msgid "Equal (or nearly equal) balance of compute capacity (RAM and CPU)"
msgstr "计算容量(内存和CPU)对等(或接近对等)"
msgid ""
"Ethernet frames can carry any kind of packet. Networking at layer 2 is "
"independent of the layer-3 protocol."
msgstr "以太网帧能够承载任何类型的包。二层上的联网独立于三层协议之外。"
msgid ""
"Ethernet frames contain all the essentials for networking. These include, "
"but are not limited to, globally unique source addresses, globally unique "
"destination addresses, and error control."
msgstr ""
"以太网帧包含了所有联网所需的要素。这些要素包括但不限于，全局唯一的源地址，全"
"局唯一的目标地址，以及错误控制。"
msgid "Example applications deployed with cloud storage characteristics:"
msgstr "以下是云存储类型的应用部署的例子："
msgid ""
"Excluding certain OpenStack components can limit or constrain the "
"functionality of other components. For example, if the architecture includes "
"Orchestration but excludes Telemetry, then the design will not be able to "
"take advantage of Orchestrations' auto scaling functionality. It is "
"important to research the component interdependencies in conjunction with "
"the technical requirements before deciding on the final architecture."
msgstr ""
"去除某些OpenStack组件会导致其他组件的功能受限。举例，如果架构中包含了编排但是"
"去除了Telmetry，那么这个设计就无法使用编排的自动扩展功能。在决定最终架构之"
"前，研究组件间的内部依赖是很重要的技术需求。"
msgid ""
"Excluding certain OpenStack components may limit or constrain the "
"functionality of other components. If a design opts to include Orchestration "
"but exclude Telemetry, then the design cannot take advantage of "
"Orchestration's auto scaling functionality (which relies on information from "
"Telemetry). Due to the fact that you can use Orchestration to spin up a "
"large number of instances to perform the compute-intensive processing, we "
"strongly recommend including Orchestration in a compute-focused architecture "
"design."
msgstr ""
"排除一些特定的OpenStack组件会让其他组件的功能受到限制。如果在一个设计中有"
"Orchestration模块但是没有包括Telemetry模块，那么此设计就无法使用Orchestration"
"带来自动伸缩功能的优点(Orchestration需要Telemetery提供监测数据)。用户使用"
"Orchestration在计算密集型处理任务时可自动启动大量的实例，因此强烈建议在计算型"
"架构设计中使用Orchestration。"
msgid "Expandability"
msgstr "延伸性"
msgid "Expansion planning"
msgstr "扩展计划"
msgid "Fault tolerance"
msgstr "容错"
msgid "Fault tolerance and availability"
msgstr "容错和可用性"
msgid ""
"Federated cloud, enabling users to choose resources from multiple providers"
msgstr "联合云,允许用户从不同的提供商那选择资源"
msgid "File or object storage"
msgstr "文件或对象存储"
msgid ""
"Financial factors are a primary concern for any organization. Cost is an "
"important criterion as general purpose clouds are considered the baseline "
"from which all other cloud architecture environments derive. General purpose "
"clouds do not always provide the most cost-effective environment for "
"specialized applications or situations. Unless razor-thin margins and costs "
"have been mandated as a critical factor, cost should not be the sole "
"consideration when choosing or designing a general purpose architecture."
msgstr ""
"财务问题对任何组织来说都是头等大事。开销是一个重要的标准，通用型云以此作为基"
"本，其它云架构环境以此作为参考。通用型云一般不会为特殊的应用或情况提供较划算"
"的环境，除非是不赚钱或者成本已经定了，当选择或设计一个通用架构时开销才不是唯"
"一考虑的。"
msgid "Firewall functionality"
msgstr "防火墙功能"
msgid "Firewalls"
msgstr "防火墙"
msgid "Flat or VLAN"
msgstr "Flat 或者 VLAN"
msgid "Flat, VLAN, Overlays, L2-L3, SDN"
msgstr "Flat、VLAN、覆盖网络、二层到三层、软件定义网络(SDN)"
msgid "Flexibility"
msgstr "灵活性："
msgid ""
"For a company interested in building a commercial public cloud offering "
"based on OpenStack, the general purpose architecture model might be the best "
"choice. Designers are not always going to know the purposes or workloads for "
"which the end users will use the cloud."
msgstr ""
"对于一家公司对基于OpenStack构建一个商业公有云有兴趣的话，通用型架构模式也许是"
"最好的选择。设计者毋须知道最终用户使用云的目的和具体负载。"
msgid ""
"For a deeper discussion on many of these topics, refer to the <link xlink:"
"href=\"http://docs.openstack.org/ops\"><citetitle>OpenStack Operations "
"Guide</citetitle></link>."
msgstr ""
"有关这些题目的更加深入的讨论，请参考 <link xlink:href=\"http://docs."
"openstack.org/ops\"><citetitle>OpenStack 运维实战</citetitle></link>"
msgid ""
"For a general purpose OpenStack cloud, the OpenStack infrastructure "
"components need to be highly available. If the design does not include "
"hardware load balancing, networking software packages like HAProxy will need "
"to be included."
msgstr ""
"对于通用型OpenStack云来说，基础设施组件需要高可用。如果设计时没有包括硬件的负"
"载均衡器，那么就得包含网络软件包如HAProxy。"
msgid ""
"For a user of a massively scalable OpenStack public cloud, there are no "
"expectations for control over security, performance, or availability. Users "
"expect only SLAs related to uptime of API services, and very basic SLAs for "
"services offered. It is the user's responsibility to address these issues on "
"their own. The exception to this expectation is the rare case of a massively "
"scalable cloud infrastructure built for a private or government organization "
"that has specific requirements."
msgstr ""
"对于一个可大规模扩展的 OpenStack 公有云的用户来说，对于安全性、性能以及可用性"
"的控制需求并没有那么强烈。只有与 API 服务的正常运行时间相关的 SLA，以及所提供"
"的服务非常基本的 SLA，是所需要的。用户明白解决这些问题是他们自己的责任。这种"
"期望的例外是一个非常罕见的场景：该可大规模扩展的云是为了一个有特别需求的私有"
"或者政府组织而构建的。"
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 has 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)个磁盘。"
msgid ""
"For example, given a cloud with two regions, if the operator grants a user a "
"quota of 25 instances in each region then that user may launch a total of 50 "
"instances spread across both regions. They may not, however, launch more "
"than 25 instances in any single region."
msgstr ""
"举例来说，一个云有两个region，如果运维人员给某个用户的配额是在每个region中可"
"以启动25个实例，那么此用户在两个region加起来就可以启动50个实例。但是不可以这"
"么相加，因为配额只在一个region生效。"
msgid ""
"For many use cases the proximity of the user to their workloads has a direct "
"influence on the performance of the application and therefore should be "
"taken into consideration in the design. Certain applications require zero to "
"minimal latency that can only be achieved by deploying the cloud in multiple "
"locations. These locations could be in different data centers, cities, "
"countries or geographical regions, depending on the user requirement and "
"location of the users."
msgstr ""
"对于很多案例来说用户的负载会直接影响到其应用的性能，因此需要将此纳入考虑范"
"围。欲确保应用的延迟为零或尽可能的最小化，多地点唯一的实现就是在部署云时。这"
"些地点可以是不同的数据中心，不同的城市，不同的国家或地理位置，取决于用户需求"
"和当地用户。"
msgid ""
"For more information OpenStack Security, see the <link xlink:href=\"http://"
"docs.openstack.org/security-guide/\"><citetitle>OpenStack Security Guide</"
"citetitle></link>"
msgstr ""
"更多关于OpenStack安全的信息，请访问<link xlink:href=\"http://docs.openstack."
"org/security-guide/\"><citetitle>OpenStack 安全指南</citetitle></link>。"
msgid ""
"For more information on high availability in OpenStack, see the <link xlink:"
"href=\"http://docs.openstack.org/high-availability-guide"
"\"><citetitle>OpenStack High Availability Guide</citetitle></link>."
msgstr ""
"关于OpenStack高可用更多信息，请阅读 <link xlink:href=\"http://docs.openstack."
"org/high-availability-guide\"><citetitle>OpenStack 高可用指南</citetitle></"
"link>."
msgid ""
"For network focused applications the future is the IPv6 protocol. IPv6 "
"increases the address space significantly, fixes long standing issues in the "
"IPv4 protocol, and will become essential for network focused applications in "
"the future."
msgstr ""
"对于关注网络方面的应用来说，未来将是 IPv6 协议的天下。IPv6 显著地扩大了地址空"
"间，解决了 IPv4 协议长久以来存在的问题，并且将会成为未来面向网络应用的重要乃"
"至本质部分。"
msgid "Functionality"
msgstr "功能"
msgid ""
"General content storage and synchronization. An example of this is private "
"dropbox."
msgstr "通用内容存储和同步。比如私有的 dropbox。"
msgid "General purpose"
msgstr "通用型"
msgid ""
"General purpose OpenStack cloud has multiple options. The key factors that "
"will have an influence on selection of storage hardware for a general "
"purpose OpenStack cloud are as follows:"
msgstr "通用型OpenStack云有很多属性，影响存储硬件的选择的关键因素有以下："
msgid ""
"General purpose clouds are limited to the most basic components, but they "
"can include additional resources such as:"
msgstr "通用型云被限制在了大部分的基本组件，但是可以包含下面增加的资源，例如："
msgid "Geneva, Switzerland"
msgstr "瑞士日内瓦"
msgid "Geo-location sensitive data."
msgstr "地理位置敏感数据"
msgid "Geo-redundant load balancing"
msgstr "地理冗余负载均衡"
msgid "Growth and capacity planning"
msgstr "增长和容量计划"
msgid "Guest"
msgstr "客户机"
msgid ""
"Hands off: Leverage automation to increase consistency and quality and "
"reduce response times."
msgstr "放手：自动化可以增加一致性、质量以及减少响应的时间。"
msgid ""
"Hardware decisions are also made in relation to network architecture and "
"facilities planning. These factors play heavily into the overall "
"architecture of an OpenStack cloud."
msgstr ""
"许多额外的硬件决策会影响到网络的架构和设施的规划。这些问题在OpenStack云的整个"
"架构中扮演非常重要的角色。"
msgid ""
"Hardware resources selected for the resource nodes should be capable of "
"supporting enough storage for the cloud services. Defining the initial "
"requirements and ensuring the design can support adding capacity is "
"important. Hardware nodes selected for object storage should be capable of "
"support a large number of inexpensive disks with no reliance on RAID "
"controller cards. Hardware nodes selected for block storage should be "
"capable of supporting high speed storage solutions and RAID controller cards "
"to provide performance and redundancy to storage at a hardware level. "
"Selecting hardware RAID controllers that automatically repair damaged arrays "
"will assist with the replacement and repair of degraded or destroyed storage "
"devices."
msgstr ""
"对于资源节点的硬件选择来说，须为云服务提供足够的存储。定义初始的需求和确保设"
"计是支持增加的能力是很重要的。为对象存储选择硬件节点须支持大量的廉价磁盘，无"
"须冗余，无须RAID控制卡。为块存储选择硬件节点须具备支持高速存储解决方案，拥有"
"RAID控制卡保证性能，以及在硬件层的冗余能力。选择硬件RAID控制器，是其可以自动"
"修复损坏的阵列，以帮助人工的介入，替代及修复已经降级或损坏的存储设备。"
msgid "Hardware selection involves three key areas:"
msgstr "硬件选择分为三大块："
msgid ""
"Here are some guidelines to keep in mind when designing an application for "
"the cloud:"
msgstr "这里有一些原则忠告，在为一个应用设计云的时候请时刻铭记："
msgid "High availability"
msgstr "高可用"
msgid "High availability (HA)"
msgstr "高可用(HA)"
msgid "High availability across clouds (for technical diversity)"
msgstr "跨云的高可用性(技术多样)"
msgid "High availability issues"
msgstr "高可用问题"
msgid "High performance computing (HPC)"
msgstr "高性能计算(HPC)"
msgid ""
"High performance computing jobs that benefit from the availability of "
"graphics processing units (GPUs) for general-purpose computing."
msgstr "使用图形处理单元(GPU)，可大大有益于高性能计算任务。"
msgid "High performance database"
msgstr "高性能数据库"
msgid "High performance database with Database service"
msgstr "带数据库服务的高性能数据库"
msgid "High speed and high volume transactional systems"
msgstr "高速及大量数据的事务性系统"
msgid "Host aggregates"
msgstr "主机聚合"
msgid ""
"Host aggregates enable partitioning of OpenStack Compute deployments into "
"logical groups for load balancing and instance distribution. You can also "
"use host aggregates to further partition an availability zone. Consider a "
"cloud which might use host aggregates to partition an availability zone into "
"groups of hosts that either share common resources, such as storage and "
"network, or have a special property, such as trusted computing hardware. You "
"cannot target host aggregates explicitly. Instead, select instance flavors "
"that map to host aggregate metadata. These flavors target host aggregates "
"implicitly."
msgstr ""
"主机聚合使得能够将 OpenStack 计算部署划分成逻辑上的分组以实现负载均衡和实例的"
"分布。主机聚合也可以被用于对一个可用域进行更进一步的划分，想象一下一个云环境"
"可能使用主机聚合将可用域中的主机进行分组，分组依据的规则可能是主机共享资源，"
"比如存储和网络，或者主机有特别的属性，比如可信计算硬件。主机聚合并不是明显面"
"向用户的，相反，是通过选择实例类型来实现的，这些实例的类型都带有额外的规格信"
"息，映射到主机聚合的元数据上。"
msgid "Host density"
msgstr "主机密度"
msgid ""
"How the particular storage architecture will be used is critical for "
"determining the architecture. Some of the configurations that will influence "
"the architecture include whether it will be used by the hypervisors for "
"ephemeral instance storage or if OpenStack Object Storage will use it for "
"object storage."
msgstr ""
"特定的存储架构如何使用是决定架构的关键。一些配置将直接影响到架构，包括用于"
"hypervisor的临时实例存储，OpenStack对象存储使用它来作为对象存储服务。"
msgid "How this book is organized"
msgstr "本书是如何组织的"
msgid "Hybrid"
msgstr "混合云"
msgid "Hyper-V"
msgstr "Hyper-V"
msgid "Hypervisor"
msgstr "虚拟机管理程序"
msgid "IP addresses"
msgstr "IP 地址"
msgid "Identity (keystone)"
msgstr "认证 (keystone)"
msgid ""
"If an SDN implementation requires layer-2 access because it directly "
"manipulates switches, we do not recommend running an overlay network or a "
"layer-3 agent. If the controller resides within an OpenStack installation, "
"it may be necessary to build an ML2 plug-in and schedule the controller "
"instances to connect to tenant VLANs that then talk directly to the switch "
"hardware. Alternatively, depending on the external device support, use a "
"tunnel that terminates at the switch hardware itself."
msgstr ""
"如果一个 SDN 的实现由于它需要直接管理和操作交换机因而要求-2层网络的连接，那么"
"就不建议运行覆盖网络或者-3层网络的代理程序。假如 SDN 控制器运行在 OpenStack "
"环境之中，则可能需要创建一个 ML2 插件并且将该控制器实例调度到能够连接至能够直"
"接与交换机硬件进行通信的租户 VLAN。另一个可能的方式是，基于外部硬件设备的支持"
"情况，使用一端终结在交换机硬件之上的网络隧道。"
msgid ""
"If high availability is a requirement to provide continuous infrastructure "
"operations, a basic requirement of high availability should be defined."
msgstr ""
"如果高可用是提供持续基础设施运营的需求，那么高可用的基本需求就应该被定义。"
msgid ""
"If natively available replication is not available, operations personnel "
"must be able to modify the application 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 ""
"当创建一个需要副本数据的应用时，我们建议将应用设计成为能够检测副本复制是否是"
"底层存储子系统的原生特性。在复制功能不是底层存储系统的特性的情况下，才将应用"
"设计成为自身能够提供副本复制服务。一个被设计为能够觉察到底层存储系统的应用，"
"同样可以在很大范围的基础设施中部署，并且依然拥有一些最基本的行为，而不管底层"
"的基础设施有什么不同。"
msgid ""
"If the solution is a scale-out storage architecture that includes DAS, it "
"will affect the server hardware selection. This could ripple into the "
"decisions that affect host density, instance density, power density, OS-"
"hypervisor, management tools and others."
msgstr ""
"如果是一个囊括了DAS的横向存储架构的解决方案，它将影响到服务器硬件的选择。这会"
"波及到决策，因为影响了主机密度，实例密度，电源密度，操作系统-Hypervisor，管理"
"工具及更多。"
msgid ""
"If these software packages are required, the design must account for the "
"additional resource consumption (CPU, RAM, storage, and network bandwidth). "
"Some other potential design impacts include:"
msgstr ""
"如果这些软件包都需要的话，设计必须计算额外的资源使用率(CPU，内存，存储以及网"
"络带宽)。其他一些潜在影响设计的有："
msgid ""
"If this is a requirement, the hardware must support this configuration. User "
"requirements determine if a completely redundant network infrastructure is "
"required."
msgstr ""
"如果这是必须的，那么对应的服务器硬件就需要配置以支持冗余的情况。用户的需求也"
"是决定是否采用全冗余网络基础设施的关键。"
msgid ""
"If you require direct access to a specific device, PCI pass-through enables "
"you to dedicate the device to a single instance per hypervisor. You must "
"define a flavor that has the PCI device specifically in order to properly "
"schedule instances. More information regarding PCI pass-through, including "
"instructions for implementing and using it, is available at <link xlink:href="
"\"https://wiki.openstack.org/wiki/"
"Pci_passthrough#How_to_check_PCI_status_with_PCI_api_patches\"> https://wiki."
"openstack.org/wiki/Pci_passthrough</link>."
msgstr ""
"如果需要直接使用某个特定的设备，可以通过使用 PCI 穿透技术将设备指定至每个宿主"
"机上的单个实例。OpenStack 管理员需要定义一个明确具有 PCI 设备以便适当调度实例"
"的实例类别。关于 PCI 穿透的更多信息，包括实施与使用的说明，请参考 <link "
"xlink:href=\"https://wiki.openstack.org/wiki/"
"Pci_passthrough#How_to_check_PCI_status_with_PCI_api_patches\"> https://wiki."
"openstack.org/wiki/Pci_passthrough</link>。"
msgid "Image (glance)"
msgstr "镜像 (glance)"
msgid "Image disk utilization"
msgstr "镜像磁盘使用"
msgid "Image portability"
msgstr "镜像移植"
msgid ""
"In OpenStack, the infrastructure is integral to providing services and "
"should always be available, especially when operating with SLAs. Ensuring "
"network availability is accomplished by designing the network architecture "
"so that no single point of failure exists. A consideration of the number of "
"switches, routes and redundancies of power should be factored into core "
"infrastructure, as well as the associated bonding of networks to provide "
"diverse routes to your highly available switch infrastructure."
msgstr ""
"在OpenStack架构下，基础设施是作为一个整体提供服务的，必须保证可用性，尤其是建"
"立了服务水平协议。确保网络的可用性，在完成设计网络架构后不可以有单点故障存"
"在。考虑使用多个交换机、路由器以及冗余的电源是必须考虑的，这是核心基础设施，"
"使用bonding网卡、提供多个路由、交换机高可用等。"
msgid ""
"In a cloud with extreme demands on Block Storage, the network architecture "
"should take into account the amount of East-West bandwidth required for "
"instances to make use of the available storage resources. The selected "
"network devices 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 ""
"在对块存储具有极端需求的云环境中，网络的架构需要考虑东西向的带宽流量，这些带"
"宽是实例使用可用的存储资源所必需的。所选择的网络设备必须支持巨型帧以传输大块"
"的数据。某些情况下，可能还需要创建额外的后端存储网络，专用于为实例和块存储资"
"源之间提供网络连接，来保证没有对于网络资源的争抢。"
msgid ""
"In a mixed hypervisor environment, specific aggregates of compute resources, "
"each with defined capabilities, enable workloads to utilize software and "
"hardware specific to their particular requirements. This functionality can "
"be exposed explicitly to the end user, or accessed through defined metadata "
"within a particular flavor of an instance."
msgstr ""
"在混合的hypervisor环境中，等于聚合了计算资源，但是各个hypervisor定义了各自的"
"能力，以及它们分别对软、硬件特殊的需求等。这些功能需要明确暴露给最终用户，或"
"者通过为实例类型定义的元数据来访问。"
msgid ""
"In environments that place extreme demands on Block Storage, we recommend "
"using 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 are "
"distributed across multiple availability zones."
msgstr ""
"在对块存储具有极端需求的环境下，我们建议利用多个存储池所带来的好处。在这种场"
"景中，每个设备池，在池中的所有硬件节点上，必须都具有相似的硬件设计以及磁盘配"
"置。这使得设计能够为应用提供到多个块存储池的访问，每个存储池都有其自身的冗"
"余、可用性\n"
"和性能特点。部署多个存储池时，对负责在资源节点上准备存储的块存储调度器的影"
"响，也是一个重要的考虑因素。确保应用能够将其存储卷分散到不同的区域中，每个区"
"域具有其自身的网络、电源以及冷却基础设施，能够给予租户建立具有容错性应用的能"
"力。该应用会被分布到多个可用区域中。"
msgid ""
"In order to scale the Object Storage service to meet the workload of "
"multiple regions, multiple proxy workers are run and load-balanced, storage "
"nodes are installed in each region, and the entire Object Storage Service "
"can be fronted by an HTTP caching layer. This is done so client requests for "
"objects can be served out of caches rather than directly from the storage "
"modules themselves, reducing the actual load on the storage network. In "
"addition to an HTTP caching layer, use a caching layer like Memcache to "
"cache objects between the proxy and storage nodes."
msgstr ""
"为满足多region的负载理应扩展对象存储服务，那么多个代理运行，且拥有负载均衡，"
"在每个region都安装存储节点，对象存储服务的入口前端配置HTTP缓存层都是必要的。"
"这样的话，客户端请求对象时会访问缓存而不是直接到存储模块，可有效较少存储网络"
"的负载。另外在HTTP缓存层，在代理和存储节点之间使用诸如Memcache可缓存对象。"
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 you can add capacity and "
"bandwidth easily. This often involves the use of dynamic routing protocols "
"or advanced networking solutions to add capacity 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 ""
"在一些情形下，来自实例对块存储的需求会耗尽可用的网络带宽。因此，设计网络基础"
"设施时，考虑到如此的块存储资源使用一定得很容易的增加容量和带宽。这通常涉及到"
"使用动态路由协议或者是高级网络解决方案允许轻松添加下游设备以增加容量。无论是"
"前端存储网络设计还是后端存储网络设计都得围绕着快速和容易添加容量和带宽的能力"
"来展开。"
msgid ""
"In some cases, the resolution to the problem is ultimately to deploy a more "
"recent version of OpenStack. Alternatively, when you must resolve an issue "
"in a production environment where rebuilding the entire environment is not "
"an option, it is sometimes possible to deploy updates to specific underlying "
"components in order to resolve issues or gain significant performance "
"improvements. Although this may appear to expose the deployment to increased "
"risk and instability, in many cases it could be an undiscovered issue."
msgstr ""
"某种情况下，问题的最终解决办法会是部署一套更新版本的 OpenStack。所幸的是，当"
"在一个不可能整个推倒重建的生产环境要解决这样的问题的时候，还可以只重新部署能"
"够解决问题或者能够使得性能明显提高的底层组件的新版本。虽然这乍看起来像是可能"
"给部署带来更高的风险和不稳定性，但是大多数情况下这并不是什么问题。"
msgid ""
"In some cases, you must add bandwidth and capacity to the network resources "
"servicing requests between proxy servers and storage nodes. 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 ""
"一些情况下，要求给代理服务和存储节点之间的网络资源服务增加带宽和容量。基于这"
"个原因，用于访问存储节点和代理服务的网络架构要设计的具有扩展性。"
msgid ""
"In the case of running TripleO, the underlying OpenStack cloud deploys the "
"Compute nodes as bare-metal. You then deploy OpenStack on these Compute bare-"
"metal servers with the appropriate hypervisor, such as KVM."
msgstr ""
"在运行 TripleO 的场景下，底层的 OpenStack 环境以裸金属的方式部署计算节点。然"
"后 OpenStack 将会被部署在这些计算的裸金属服务器上，并使用诸如 KVM 之类的管理"
"程序。"
msgid ""
"In the case of running smaller OpenStack clouds for testing purposes, where "
"performance is not a critical factor, you can use QEMU instead. It is also "
"possible to run a KVM hypervisor in an instance (see <link xlink:href="
"\"http://davejingtian.org/2014/03/30/nested-kvm-just-for-fun/\"> http://"
"davejingtian.org/2014/03/30/nested-kvm-just-for-fun/</link>), though this is "
"not a supported configuration, and could be a complex solution for such a "
"use case."
msgstr ""
"如果是要为测试目的运行小规模的 OpenStack 云环境，并且性能不是关键的考虑因素的"
"情况下，则 QEMU 可以被作为替代使用。在实例中运行一个 KVM 的宿主机是可能的(参"
"考<link xlink:href=\"http://davejingtian.org/2014/03/30/nested-kvm-just-for-"
"fun/\"> http://davejingtian.org/2014/03/30/nested-kvm-just-for-fun/</link>)，"
"但这不是被支持的配置方式，并且对这样一个使用场景来说，也会是一个复杂的解决方"
"案。"
msgid ""
"In the planning and design phases of the build out, it is important to "
"include the operation's function. Operational factors affect the design "
"choices for a general purpose cloud, and operations staff are often tasked "
"with the maintenance of cloud environments for larger installations."
msgstr ""
"在构建过程中的规划和设计阶段，能够考虑到运维的内容显得异常的重要。对通用型云"
"来说，运维因素影响着设计的选择，而且运维人员担任着维护云环境的任务，以及最初"
"大规模的安装、部署。"
msgid ""
"In this architecture, instance density and CPU-RAM oversubscription are "
"lower. You require more hosts to support the anticipated scale, especially "
"if the design uses dual-socket hardware designs."
msgstr ""
"在此架构中实例密度要被考虑为低，因此CPU和内存的超额认购比例也要低。为了支持实"
"例低密度的预期扩展需要更多的主机，尤其是设计中使用了双插槽的硬件。"
msgid ""
"In this example the cloud is divided into two regions, one for each site, "
"with two availability zones in each based on the power layout of the data "
"centers. A number of host aggregates enable targeting of virtual machine "
"instances using flavors, that require special capabilities shared by the "
"target hosts such as SSDs, 10GbE networks, or GPU cards."
msgstr ""
"在这个例子中，整个云被划分为两个区域，每个地点各一个，每个区域之中又有两个基"
"于数据中心中的电源安排而划分的可用域。其中一系列的主机聚合也被定义以允许通过"
"使用实例规格来指向虚拟机实例，这要求目标主机需要共享诸如 SSD、10GbE 网络或者"
"显卡等特别的硬件和功能。"
msgid ""
"In this example, Ceph presents a Swift-compatible REST interface, as well as "
"a block level storage from a distributed storage cluster. It is highly "
"flexible and has features that enable reduced cost of operations such as "
"self healing and auto balancing. Using erasure coded pools are a suitable "
"way of maximizing the amount of usable space."
msgstr ""
"选用 Ceph 以抛出 Swift 兼容的 REST 接口，同样的也从一个分布式的存储集群中提供"
"了块级别的存储。Ceph 非常的灵活，并且具有能够降低运营成本的许多特性，比如说自"
"动修复以及自动平衡。Ceph 中的 erasure coded 池被用以最大化可用空间的量。"
msgid ""
"Inclusion of clustering software, such as Corosync or Pacemaker, is "
"determined primarily by the availability requirements. The impact of "
"including (or not including) these software packages is primarily determined "
"by the availability of the cloud infrastructure and the complexity of "
"supporting the configuration after it is deployed. The <link xlink:href="
"\"http://docs.openstack.org/high-availability-guide/\"><citetitle>OpenStack "
"High Availability Guide</citetitle></link> provides more details on the "
"installation and configuration of Corosync and Pacemaker, should these "
"packages need to be included in the design."
msgstr ""
"在集群软件中如 Corosync和Pacemaker在可用性需求中占主流。包含(不包含)这些软件"
"包是主要决定的，要使云基础设施具有高可用的话，当然在部署之后会带来复杂的配"
"置。<link xlink:href=\"http://docs.openstack.org/high-availability-guide/"
"\"><citetitle>OpenStack 高可用指南</citetitle></link> 提供了更加详细的安装和"
"配置Corosync和Pacemaker，所以在设计中这些软件包需要被包含。 "
msgid "Incorporate edits to follow OpenStack style."
msgstr "参与编辑请遵照OpenStack风格。"
msgid ""
"Increasing OpenStack Object Storage means network bandwidth needs to be "
"taken into consideration. Running OpenStack Object Storage with network "
"connections offering 10 GbE or better connectivity is advised."
msgstr ""
"增加OpenStack对象存储同时也意味着需要考虑更大的带宽。运行OpenStack对象存储，"
"请使用10 GbE或更高的网络连接。"
msgid ""
"Increasing server density means sacrificing resource capacity or "
"expandability, however, increasing resource capacity and expandability "
"increases cost and decreases server density. As a result, determining the "
"best server hardware for a general purpose OpenStack architecture means "
"understanding how choice of form factor will impact the rest of the design. "
"The following list outlines the form factors to choose from:"
msgstr ""
"增加服务器密度意味这损失资源容量和扩展性，同理，增加资源容量和扩展性会增加开"
"销和减少服务器密度。结果就是，为通用型OpenStack架构决定最合适的服务器硬件意味"
"着怎么选择都会影响到其他设计。从以下列表元素中作出选择："
msgid ""
"Increasing the size of the supporting compute environment increases the "
"network traffic and messages, adding load to the controller or networking "
"nodes. Effective monitoring of the environment will help with capacity "
"decisions on scaling."
msgstr ""
"增加支持计算环境的规模，会增加网络流量、消息，也会增加控制器和网络节点的负"
"载。有效的监测整个环境，对决定扩展容量很有帮助。"
msgid "Infrastructure segregation"
msgstr "基础设施隔离"
msgid ""
"Infrastructure-as-a-Service offerings, including OpenStack, use flavors to "
"provide standardized views of virtual machine resource requirements that "
"simplify the problem of scheduling instances while making the best use of "
"the available physical resources."
msgstr ""
"基础设施即服务所提供的，包括OpenStack，使用类型来提供标准的虚拟机资源需求视"
"图，为分配实例时能够充分利用可用的物理资源提供了简单的解决办法。"
msgid "Initial release."
msgstr "初始版"
msgid ""
"Input-Output performance requirements require researching and modeling "
"before deciding on a final storage framework. Running benchmarks for Input-"
"Output performance provides a baseline for expected performance levels. If "
"these tests include details, then the resulting data can help model behavior "
"and results during different workloads. Running scripted smaller benchmarks "
"during the life cycle of the architecture helps record the system health at "
"different points in time. The data from these scripted benchmarks assist in "
"future scoping and gaining a deeper understanding of an organization's needs."
msgstr ""
"在对最终的存储框架做出决定之前，需要对输入-输出的性能需求进行研究并将其模型"
"化。为输入-输出性能运行一些检测能够提供一个大致的预期中性能水平的基准。假如测"
"试能够包含详细信息，比如说，在对象存储系统中的对象大小，或者对象存储以及块存"
"储的不同\n"
"容量级别，那么测试得出来的数据就能够帮助对不同的负载之下的行为和结果进行模型"
"化。在架构的生命周期中运行小规模脚本化的测试能够帮助在不同时间点及时记录系统"
"的健康状态。这些脚本化测试得出的数据，能够在以后对整个组织的需要进行研究和深"
"入了解的时候提供帮助。"
msgid "Instance and image locations"
msgstr "实例和镜像存放地"
msgid "Instance density"
msgstr "实例密度"
msgid ""
"Insufficient disk capacity could also have a negative effect on overall "
"performance including CPU and memory usage. Depending on the back-end "
"architecture of the OpenStack Block Storage layer, capacity includes adding "
"disk shelves to enterprise storage systems or installing additional block "
"storage nodes. Upgrading directly attached storage installed in compute "
"hosts, and adding capacity to the shared storage for additional ephemeral "
"storage to instances, may be necessary."
msgstr ""
"磁盘容量不足会给整个性能带来负面影响，会波及到CPU和内存的使用。这取决于后端架"
"构的OpenStack块存储层，可以是为企业级存储系统增加磁盘，也可以是安装新的块存储"
"节点，也可以是为计算主机直接挂接存储，也可以为实例从共享存储中添加临时空间。"
"都有可能。"
msgid "Intended audience"
msgstr "目标读者"
msgid "Internal consumption (private) cloud"
msgstr "内部消费(私有)云"
msgid "Interoperability"
msgstr "互操作性"
msgid ""
"Interoperability and integration with OpenStack can be paramount in deciding "
"on a storage hardware and storage management platform. Interoperability and "
"integration includes factors such as OpenStack Block Storage "
"interoperability, OpenStack Object Storage compatibility, and hypervisor "
"compatibility (which affects the ability to use storage for ephemeral "
"instance storage)."
msgstr ""
"与 OpenStack 系统的互动性和集成情况，在决定存储硬件和存储管理平台的选择上，可"
"能是最为重要的。这里所说的互动性和集成度，包括比如与 OpenStack 块存储的互操作"
"性、与 OpenStack 对象存储的兼容性，以及与虚拟机管理程序的兼容性(影响为临时的"
"实例使用存储的能力)等因素。"
msgid "Introduction"
msgstr "介绍"
msgid "Isolate virtual networks using encapsulation technologies."
msgstr "使用封装技术隔离虚拟网络。"
msgid ""
"It can be difficult to troubleshoot a network without IP addresses and ICMP."
msgstr "解决一个没有 IP 地址和 ICMP 的网络上的问题可能会很困难。"
msgid ""
"It is important to know that layer 2 has a very limited set of network "
"management tools. It is very difficult to control traffic, as it does not "
"have mechanisms to manage the network or shape the traffic, and network "
"troubleshooting is very difficult. One reason for this difficulty is network "
"devices have no IP addresses. As a result, there is no reasonable way to "
"check network delay in a layer-2 network."
msgstr ""
"很重要的一点是，必须意识到二层网络上用于网络管理的工具非常有限。因此控制流量"
"非常困难，由于二层网络没有管理网络或者对流量进行整形的机制，解决网络问题也非"
"常困难。其中一个原因是网络设备没有 IP 地址。因此，在二层网络中没有合理的方式"
"来检查网络延迟。"
msgid ""
"It is possible to gain more performance out of a single storage system by "
"using specialized network technologies such as RDMA, SRP, iSER and SCST. The "
"specifics for using these technologies is beyond the scope of this book."
msgstr ""
"使用特定的网络技术如RDMA,SRP,iSER或SCST来提高单个存储系统的性能是可能，但是讨"
"论这些技术已经超出了本书的范围。"
msgid ""
"It may be necessary to implement a 3rd-party caching layer for some "
"applications to achieve suitable performance."
msgstr "对于一些应用来说，可能需要引入第3方的缓存层以实现合意的性能。"
msgid "KVM (and QEMU)"
msgstr "KVM (and QEMU)"
msgid ""
"Kenneth Hui (EMC) <link xlink:href=\"http://twitter.com/hui_kenneth"
"\">@hui_kenneth</link>"
msgstr ""
"Kenneth Hui (EMC) <link xlink:href=\"http://twitter.com/hui_kenneth"
"\">@hui_kenneth</link>"
msgid ""
"Kevin Jackson (Rackspace) <link xlink:href=\"http://twitter.com/"
"itarchitectkev\">@itarchitectkev</link>"
msgstr ""
"Kevin Jackson (Rackspace) <link xlink:href=\"http://twitter.com/"
"itarchitectkev\">@itarchitectkev</link>"
msgid "Key considerations for the selection of networking hardware include:"
msgstr "选择网络硬件主要考虑应包括："
msgid ""
"Key hardware specifications are also crucial to the performance of user "
"instances. Be sure to consider budget and performance needs, including "
"storage performance (spindles/core), memory availability (RAM/core), network "
"bandwidth (Gbps/core), and overall CPU performance (CPU/core)."
msgstr ""
"关键的硬件规格也是确保用户实例的性能的指标。请确保考虑好预算和性能需求，包括"
"存储性能 (spindles/core), 内存可用性 (RAM/core), 网络带宽 (Gbps/core), 以及整"
"个的CPU性能 (CPU/core)."
msgid "LXC"
msgstr "LXC"
msgid "Lab test bed"
msgstr "测试实验平台"
msgid ""
"Larger rack-mounted servers, such as 4U servers, often provide even greater "
"CPU capacity, commonly supporting four or even eight CPU sockets. These "
"servers have greater expandability, but such servers have much lower server "
"density and are often more expensive."
msgstr ""
"大型机架式服务器，比如4U服务器，可提供更为强大的CPU容量。通常支持4个甚至8个"
"CPU插槽。拥有很强的扩展性，但是这些服务器会带来低密度，以及更加昂贵的开销。"
msgid ""
"Larger rack-mounted servers, such as 4U servers, often provide even greater "
"CPU capacity. Commonly supporting four or even eight CPU sockets. These "
"servers have greater expandability but such servers have much lower server "
"density and usually greater hardware cost."
msgstr ""
"大型机架式服务器，比如4U服务器，可提供更为强大的CPU容量。通常支持4个甚至8个"
"CPU插槽。拥有很强的扩展性，但是这些服务器会带来低密度，以及更加昂贵的开销。"
msgid ""
"Larger rack-mounted servers, such as 4U servers, will tend to offer even "
"greater CPU capacity, often supporting four or even eight CPU sockets. These "
"servers often have much greater expandability so will provide the best "
"option for upgradability. This means, however, that the servers have a much "
"lower server density and a much greater hardware cost."
msgstr ""
"高U的机架式服务器，比如4U的服务器，可提供更多的CPU容量，通常可提供四个甚至8个"
"CPU插槽。这些服务器拥有非常强的可扩展性，还拥有升级的最好条件。尽管如此，它们"
"也意味着低密度和更高的开销。"
msgid "Latency"
msgstr "延迟"
msgid ""
"Layer-2 Ethernet usage has these advantages over layer-3 IP network usage:"
msgstr "使用二层以太网相对于使用三层 IP 网络有如下优势："
msgid "Layer-2 architecture limitations"
msgstr "二层架构的局限性"
msgid "Layer-3 architecture advantages"
msgstr "三层架构的优势"
msgid "Layer-3 architecture limitations"
msgstr "三层架构的局限性"
msgid ""
"Layer-3 networks provide the same level of resiliency and scalability as the "
"Internet."
msgstr "三层网络提供了与因特网相同的弹性及可扩展性。"
msgid "Legacy networking (nova-network)"
msgstr "传统联网方式(nova-network)"
msgid "Legal requirements"
msgstr "法律需求"
msgid ""
"Leveraging Orchestration and Telemetry modules is also a potential issue "
"when providing auto-scaling, orchestrated web application environments. "
"Defining the web applications in <glossterm baseform=\"Heat Orchestration "
"Template (HOT)\">Heat Orchestration Templates (HOT)</glossterm> negates the "
"reliance on the current scripted Puppet solution."
msgstr ""
"借助于Orchestration和Telemetry模块可以为web应用环境提供自动扩展的能力。使用"
"Puppet脚本定义web应用的 <glossterm baseform=\"Heat Orchestration Template "
"(HOT)\">Heat Orchestration Templates (HOT)</glossterm>即可实现。"
msgid ""
"Leveraging existing monitoring systems is an effective check to ensure "
"OpenStack environments can be monitored."
msgstr "借助已有的监测系统是一种有效的检查，确保OpenStack环境可以被监测。"
msgid "Licensing"
msgstr "许可"
msgid ""
"Likely to be fully symmetric. Because replication originates from any node "
"and might target multiple other nodes algorithmically, it is less likely for "
"this traffic to have a larger volume in any specific direction. However this "
"traffic might interfere with north-south traffic."
msgstr ""
"很可能是完全对称的网络。因为根据算法来说，复制行为可能从任何节点发起并指向多"
"个其他节点，某个特定方向的流量更大的情况不大可能发生。然而，这些流量也可能干"
"扰到南北向的流量。"
msgid "Load balancers"
msgstr "负载均衡器"
msgid "Load balancing"
msgstr "负载均衡"
msgid "Load balancing functionality"
msgstr "负载均衡功能"
msgid "Location-local service"
msgstr "本地服务"
msgid "Log analytics capabilities."
msgstr "日志分析能力。"
msgid "Logging"
msgstr "日志记录"
msgid "Logging and monitoring"
msgstr "记录日志和监测"
msgid ""
"Logs from the web application servers are shipped to OpenStack Object "
"Storage for processing and archiving."
msgstr "将web应用的日志放在OpenStack对象存储中，用来集中处理和归档。"
msgid ""
"MLAG, often used for switch redundancy, is a proprietary solution that does "
"not scale beyond two devices and forces vendor lock-in."
msgstr ""
"通常被用于实现交换机冗余的 MLAG 是私有的解决方案，不能扩展至两个设备以上，并"
"且迫使得厂商的选择受到限制。"
msgid "Maintainability"
msgstr "可维护性"
msgid "Maintenance tasks"
msgstr "维护任务："
msgid ""
"Maish Saidel-Keesing (Cisco) <link xlink:href=\"http://twitter.com/maishsk"
"\">@maishsk</link>"
msgstr ""
"Maish Saidel-Keesing (Cisco) <link xlink:href=\"http://twitter.com/maishsk"
"\">@maishsk</link>"
msgid "Management"
msgstr "管理"
msgid "Management software"
msgstr "管理软件"
msgid "Management software includes software for providing:"
msgstr "管理软件所包含的能够提供的软件："
msgid "Management tools"
msgstr "管理工具"
msgid ""
"Many jurisdictions have legislative and regulatory requirements governing "
"the storage and management of data in cloud environments. Common areas of "
"regulation include:"
msgstr ""
"很多辖区对于云环境中的数据的保管及管理都有相关的法律上或者监管上的要求。这些"
"规章的常见领域包括："
msgid ""
"MariaDB server instances store their data on shared enterprise storage, such "
"as NetApp or Solidfire devices. If a MariaDB instance fails, storage would "
"be expected to be re-attached to another instance and rejoined to the Galera "
"cluster."
msgstr ""
"MariaDB服务器实例将数据存储在共享存储中，使用企业级存储，有NetApp和Solidfire"
"的设备。如果一个MariaDB的实例宕掉，另外一个实例会重新挂接原来的存储，且重新加"
"入到Galera集群中。"
msgid "Massively scalable"
msgstr "可大规模扩展的类型"
msgid ""
"Massively scalable OpenStack clouds have the following user requirements:"
msgstr "可大规模扩展的 OpenStack 云有如下的一些用户需求："
msgid ""
"Massively scalable OpenStack clouds require extensive metering and "
"monitoring functionality to maximize the operational efficiency by keeping "
"the operator informed about the status and state of the infrastructure. This "
"includes full scale metering of the hardware and software status. A "
"corresponding framework of logging and alerting is also required to store "
"and enable operations to act on the meters provided by the metering and "
"monitoring solutions. The cloud operator also needs a solution that uses the "
"data provided by the metering and monitoring solution to provide capacity "
"planning and capacity trending analysis."
msgstr ""
"可大规模扩展的 OpenStack 云需要全面的测量及监控功能，通过保持运营人员能够清楚"
"知悉基础设施的状态，以达到最大化业务效率的目的。这包括对硬件和软件状态的全面"
"测度。同样的也需要一个相应的日志和警报框架，用以保存由测量和监控解决方案所提"
"供的数据，并允许针对测量得出的数据采取相应的动作。云运营商还需要一个能够使用"
"测量和监控方案所提供的数据进行容量计划以及容量趋势分析的解决方案。"
msgid "Media streaming."
msgstr "媒体流。"
msgid ""
"Memcached is a distributed memory object caching system, and Redis is a key-"
"value store. Both are deployed on general purpose clouds to assist in "
"alleviating load to the Identity service. The memcached service caches "
"tokens, and due to its distributed nature it can help alleviate some "
"bottlenecks to the underlying authentication system. Using memcached or "
"Redis does not affect the overall design of your architecture as they tend "
"to be deployed onto the infrastructure nodes providing the OpenStack "
"services."
msgstr ""
"Memcached是一个分布式的内存对象缓存系统，Redia是一个key-value存储系统。在通用"
"型云中使用这两个系统来减轻认证服务的负载。memcached服务缓存令牌，基于它天生的"
"分布式特性可以缓减授权系统的瓶颈。使用memcached或Redis不会影响到用户的架构设"
"计，虽然它们会部署到基础设施节点中为OpenStack提供服务。"
msgid "Methodology"
msgstr "方法论"
msgid "MongoDB has its own design considerations for high availability."
msgstr "MongoDB尤其自身的设计考虑，回馈就是可让数据库高可用。"
msgid "Monitoring"
msgstr "监控"
msgid ""
"Monitoring of advanced storage performance data to ensure that storage "
"systems are performing as expected."
msgstr "监测高级的存储性能数据，以确保存储系统正常运转。"
msgid "Monitoring of environmental resources such as temperature and humidity."
msgstr "监测诸如温度和湿度等的环境信息。"
msgid ""
"Monitoring of network resources for service disruptions which would affect "
"access to storage."
msgstr "监测网络资源情况，关注可能影响存储访问的网络服务中断问题。"
msgid "Monitoring of physical hardware resources."
msgstr "监测物理硬件资源。"
msgid "More mature, established"
msgstr "更加成熟，稳定的"
msgid ""
"Most OpenStack components require access to back-end database services to "
"store state and configuration information. Choose an appropriate back-end "
"database which satisfies the availability and fault tolerance requirements "
"of the OpenStack services."
msgstr ""
"OpenStack组件通常需要访问后端的数据库服务以存放状态和配置信息。选择合适的后端"
"数据库以满足可用性和容错的需求，这是OpenStack服务所要求的。"
msgid "Multi-hypervisor example"
msgstr "多种类型宿主机的例子"
msgid "Multi-site"
msgstr "多区域"
msgid "Multi-tier topologies"
msgstr "具有多层拓扑"
msgid "Multiple DCs"
msgstr "多数据中心"
msgid ""
"Multiple network links should be deployed between sites to provide "
"redundancy for all components. This includes storage replication, which "
"should be isolated to a dedicated network or VLAN with the ability to assign "
"QoS to control the replication traffic or provide priority for this traffic. "
"Note that if the data store is highly changeable, the network requirements "
"could have a significant effect on the operational cost of maintaining the "
"sites."
msgstr ""
"多网络链路应该在站点之间部署，以提供所有组件的冗余。这其中包括存储的复制，存"
"储应该使用专用网络隔离，或者使用VLAN的QoS功能来控制复制流量，或者为该流量提供"
"高的优先级。记住，如果数据存储经常改动，网络的需求就会显著影响到维护站点的运"
"维成本。"
msgid "Multiple racks"
msgstr "多个机柜"
msgid ""
"MySQL is the default database for OpenStack, but other compatible databases "
"are available."
msgstr ""
"MySQL是OpenStack通常考虑的后端数据库，其它和MySQL兼容的数据也同样可以很好的工"
"作。"
msgid ""
"Native support is not a constraint on the choice of OS; users are free to "
"choose just about any Linux distribution (or even Microsoft Windows) and "
"install OpenStack directly from source (or compile their own packages). "
"However, many organizations will prefer to install OpenStack from "
"distribution-supplied packages or repositories (although using the "
"distribution vendor's OpenStack packages might be a requirement for support)."
msgstr ""
"原生并非是限制到某些操作系统，用户仍然可以自己选择Linux的任何发行版(甚至是微"
"软的Windows),然后从源码安装OpenStack(或者编译为某个发行版的包)。尽管如此，事"
"实上多数组织还是会从发行版支持的包或仓库去安装OpenStack(使用分发商的OpenStack"
"软件包也许需要他们的支持)。"
msgid "Network"
msgstr "网络"
msgid "Network Operation Center"
msgstr "网络操作中心"
msgid ""
"Network Operations Center (NOC) staffed and always available to resolve "
"issues."
msgstr "配备有网络运营中心(NOC)员工并保持工作状态以解决问题。"
msgid "Network architecture"
msgstr "网络架构"
msgid "Network capacity (number and speed of links)"
msgstr "网络容量(连接数量和速度)"
msgid "Network connectivity"
msgstr "网络连通性"
msgid "Network considerations"
msgstr "网络考虑"
msgid "Network focused"
msgstr "网络型"
msgid "Network functions"
msgstr "网络功能"
msgid ""
"Network functions is a broad category but encompasses workloads that support "
"the rest of a system's network. These workloads tend to consist of large "
"amounts of small packets that are very short lived, such as DNS queries or "
"SNMP traps. These messages need to arrive quickly and do not deal with "
"packet loss as there can be a very large volume of them. There are a few "
"extra considerations to take into account for this type of workload and this "
"can change a configuration all the way to the hypervisor level. For an "
"application that generates 10 TCP sessions per user with an average "
"bandwidth of 512 kilobytes per second per flow and expected user count of "
"ten thousand concurrent users, the expected bandwidth plan is approximately "
"4.88 gigabits per second."
msgstr ""
"网络功能的话题比较宽泛，但通常是指围绕在为系统的其他部分的网络提供支持的目的"
"的工作。这类网络负载通常都是由大量的存活期比较短的小网络包组成的，例如 DNS 请"
"求或者 SNMP 陷阱等。这类消息需要很快地到达并且由于可能非常大量而不关注丢包的"
"问题。这类型的负载还有一些额外的考虑因素需要顾及，并且可能改变直到宿主机级别"
"的网络配置。假设一个应用为每个用户生成 10 个 TCP 会话，每个数据流的速度平均"
"是 512 Kbps，而预期用户的数量是 1 万个用户同时使用，预期总计的带宽计划将达到"
"大约 4.88 Gbps。"
msgid ""
"Network hardware: The network hardware selection needs to be supported by "
"the logging, monitoring, and alerting software."
msgstr ""
"网络硬件：网络硬件的选择，要看其支持日志系统、监测系统以及预警系统的情况。"
msgid "Network management functions"
msgstr "网络管理功能"
msgid "Network misconfigurations"
msgstr "错误的网络配置"
msgid "Network overlays or virtual local area networks (VLANs)"
msgstr "网络覆盖或者(VLANs)"
msgid "Network performance"
msgstr "网络性能"
msgid ""
"Network performance can be boosted considerably by implementing hardware "
"load balancers to provide front-end service to the cloud APIs. The hardware "
"load balancers also perform SSL termination if that is a requirement of your "
"environment. When implementing SSL offloading, it is important to understand "
"the SSL offloading capabilities of the devices selected."
msgstr ""
"网络的性能可以考虑有硬件的负载均衡来帮助实现，为云抛出的API提供前端的服务。硬"
"件负载均衡通常也提供SSL终端，如果用户的环境有需求的话。当实现SSL减负时，理解"
"SSL减负的能力来选择硬件，这点很重要。"
msgid "Network recommendations overview"
msgstr "网络建议的总结"
msgid "Network redundancy protocols"
msgstr "网络冗余协议"
msgid "Network service offerings"
msgstr "网络服务提供"
msgid "Network services"
msgstr "网络服务"
msgid "Network tuning"
msgstr "网络调优"
msgid ""
"Network uptime guarantees affecting switch design, which might require "
"redundant switching and power."
msgstr ""
"网络运行时间保证影响这交换机的设计，需要交换机的冗余，以及其电源的冗余。"
msgid "Network:"
msgstr "网络："
msgid "Networking"
msgstr "网络"
msgid "Networking (neutron)"
msgstr "网络 (neutron)"
msgid ""
"Networking at the frame level says nothing about the presence or absence of "
"IP addresses at the packet level. Almost all ports, links, and devices on a "
"network of LAN switches still have IP addresses, as do all the source and "
"destination hosts. There are many reasons for the continued need for IP "
"addressing. The largest one is the need to manage the network. A device or "
"link without an IP address is usually invisible to most management "
"applications. Utilities including remote access for diagnostics, file "
"transfer of configurations and software, and similar applications cannot run "
"without IP addresses as well as MAC addresses."
msgstr ""
"数据帧级别上的联网与数据包级别上的 IP 地址存在与否并没有关系。几乎所有端口、"
"链路以及在 LAN 交换机构成的网络上的设备仍然有其 IP 地址，同样地，所有的源和目"
"标主机也都有。有很多原因需要继续保留 IP 地址。其中最大的一个理由是网络管理上"
"的需要。一个没有 IP 地址的设备或者连接通常对于大多数的管理程序来说是不可见"
"的。包括远程接入的诊断工具、用于传输配置和软件的文件传输工具以及其它类似的应"
"用程序都不能够在没有 IP 地址或者 MAC 地址的情况下运行。"
msgid "Networking hardware selection"
msgstr "网络硬件选择"
msgid "Networking resources"
msgstr "网络资源"
msgid "Networking software"
msgstr "联网软件"
msgid "Newer, maturing"
msgstr "更新，正在发展不断成熟中"
msgid ""
"Nick Chase (Mirantis) <link xlink:href=\"http://twitter.com/NickChase"
"\">@NickChase</link>"
msgstr ""
"Nick Chase (Mirantis) <link xlink:href=\"http://twitter.com/NickChase"
"\">@NickChase</link>"
msgid "No multi-tier topologies"
msgstr "没有多层拓扑"
msgid "No plug-in support"
msgstr "没有插件支持"
msgid "No predefined usage model"
msgstr "非预先定义的使用模型"
msgid "Non-standard features"
msgstr "非标准特性"
msgid "Number of VLANs is limited to 4096."
msgstr "VLAN 的数目被限制在 4096。"
msgid ""
"OS selection also directly influences hypervisor selection. A cloud "
"architect who selects Ubuntu, RHEL, or SLES has some flexibility in "
"hypervisor; KVM, Xen, and LXC are supported virtualization methods available "
"under OpenStack Compute (nova) on these Linux distributions. However, a "
"cloud architect who selects Hyper-V is limited to Windows Servers. "
"Similarly, a cloud architect who selects XenServer is limited to the CentOS-"
"based dom0 operating system provided with XenServer."
msgstr ""
"操作系统的选择会直接影响到hypervisor的选择。一个云架构会选择Ubuntu,RHEL,或"
"SLES等，它们都拥有灵活的hypervisor可供选择，同时也被OpenStack 计算(nova)所支"
"持，如KVM,Xen,LXC等虚拟化。一个云架构若选择了Hyper-V,那么只能使用Windows服务"
"器版本。同样的，一个云架构若选择了XenServer,也限制到基于CenOS dom0操作系统。"
msgid ""
"OS-Hypervisor combination: Ensure that the selected logging, monitoring, or "
"alerting tools support the proposed OS-hypervisor combination."
msgstr ""
"操作系统-Hypervisor组合：确保所选择的日志系统，监测系统，或预警工具都是被此组"
"合所支持的。"
msgid ""
"OS-hypervisor combination: Ensure that the selected logging, monitoring, or "
"alerting tools support the proposed OS-hypervisor combination."
msgstr ""
"操作系统-hypervisor组合：确保选择的日志、监测、告警等工具支持打算组合的操作系"
"统-Hypervisor。"
msgid "Object Storage (swift)"
msgstr "对象存储(Swift)"
msgid "Object Storage fault tolerance and availability"
msgstr "对象存储容错和可用性"
msgid ""
"Object storage nodes should be designed so that the number of requests does "
"not hinder the performance of the cluster. The object storage service is a "
"chatty protocol, therefore making use of multiple processors that have "
"higher core counts will ensure the IO requests do not inundate the server."
msgstr ""
"对象存储节点应该被设计为在集群中不至于区区几个请求就拖性能后腿的样子。对象存"
"储服务是一种频繁交互的协议，因此确定使用多个处理器，而且要多核的，这样才可确"
"保不至于因为IO请求将服务器搞垮。"
msgid ""
"On large layer-2 networks, configuring ARP learning can also be complicated. "
"The setting for the MAC address timer on switches is critical and, if set "
"incorrectly, can cause significant performance problems. As an example, the "
"Cisco default MAC address timer is extremely long. Migrating MACs to "
"different physical locations to support instance migration can be a "
"significant problem. In this case, the network information maintained in the "
"switches could be out of sync with the new location of the instance."
msgstr ""
"在大规模的二层网络上，配置 ARP 学习也可能很复杂。交换机上的 MAC 地址超时设置"
"非常关键，并且，错误的设置可能引起严重的性能问题。例如 Cisco 交换机上的 MAC "
"地址的超时时间非常长。迁移 MAC 地址到另外的物理位置以实现实例的迁移就可能是一"
"个显著的问题。这种情形下，交换机中维护的网络信息与实例的新位置信息就会不同"
"步。"
msgid ""
"On the other hand, a scale-out storage solution that uses direct-attached "
"storage (DAS) in the servers may be an appropriate choice. This requires "
"configuration of the server hardware to support the storage solution."
msgstr ""
"反过来说，一个横向扩展的存储解决方案使用直接挂接存储(DAS)给服务器也许是个恰当"
"的选择。如果是这样的话，服务器硬件就需要配置以支持此种存储解决方案。"
msgid ""
"On the surface, the equations reveal the need for 200 physical cores and "
"80TB of storage for /var/lib/nova/instances/. However, it is also important "
"to look at patterns of usage to estimate the load that the API services, "
"database servers, and queue servers are likely to encounter."
msgstr ""
"表面上，公式的计算结果是需要200个物理核和80TB的存储，这些可在路径/var/lib/"
"nova/instances/中找到。尽管如此，另外还得重点看着其他负载的使用量，诸如API服"
"务，数据库服务，队列服务等，它们同样需要被计入总体。"
msgid "On-demand and self-service application"
msgstr "按需或自服务应用"
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 are suitable for large scale "
"performance-orientated systems."
msgstr ""
"这个问题的一个解决方案是部署一个设计时便将性能考虑在内的存储系统。传统上来"
"说，并行文件系统填补了 HPC 空间里的这个需要，在适用的时候，可以作为大规模面向"
"性能的系统的一个备份的方案考虑。"
msgid "One zone per node"
msgstr "每节点就是一个zone"
msgid "OpenStack"
msgstr "OpenStack"
msgid "OpenStack <glossterm>Compute</glossterm> (<glossterm>nova</glossterm>)"
msgstr "OpenStack <glossterm>计算</glossterm> (<glossterm>nova</glossterm>)"
msgid ""
"OpenStack <glossterm>Identity</glossterm> (<glossterm>keystone</glossterm>)"
msgstr ""
"OpenStack <glossterm>认证</glossterm> (<glossterm>keystone</glossterm>)"
msgid ""
"OpenStack <glossterm>Image service</glossterm> (<glossterm>glance</"
"glossterm>)"
msgstr ""
"OpenStack <glossterm>镜像服务</glossterm> (<glossterm>glance</glossterm>)"
msgid ""
"OpenStack <glossterm>Networking</glossterm> (<glossterm>neutron</glossterm>)"
msgstr "OpenStack <glossterm>网络</glossterm> (<glossterm>neutron</glossterm>)"
msgid ""
"OpenStack <glossterm>dashboard</glossterm> (<glossterm>horizon</glossterm>)"
msgstr ""
"OpenStack <glossterm>仪表盘</glossterm> (<glossterm>horizon</glossterm>)"
msgid "OpenStack Architecture Design Guide"
msgstr "OpenStack 架构设计指南"
msgid "OpenStack Block Storage (cinder)"
msgstr "OpenStack 块存储(cinder)"
msgid ""
"OpenStack Block Storage for use by compute instances, requiring persistent "
"storage (such as databases for dynamic sites)."
msgstr ""
"OpenStack块存储为计算实例所使用，需要持久性存储(正如数据库对于动态站点)。"
msgid "OpenStack Compute (nova)"
msgstr "OpenStack 计算(nova)"
msgid ""
"OpenStack Compute (nova) (including the use of multiple hypervisor drivers)"
msgstr "OpenStack 计算 (nova) (包括使用多hypervisor驱动)"
msgid "OpenStack Compute nodes running the KVM hypervisor."
msgstr "OpenStack计算节点运行着KVM的hypervisor。"
msgid "OpenStack Compute running KVM hypervisor"
msgstr "运行着 KVM 宿主机的 OpenStack 计算服务"
msgid ""
"OpenStack Controller service running Image, Identity, Networking, combined "
"with support services such as MariaDB and RabbitMQ, configured for high "
"availability on at least three controller nodes."
msgstr ""
"OpenStack控制器运行着诸如镜像服务、认证服务、以及网络服务等，支撑它们的服务有"
"诸如：MariaDB、RabbitMQ，至少有三台控制器节点配置为高可用。"
msgid ""
"OpenStack Controller services (Image, Identity, Networking and supporting "
"services such as MariaDB and RabbitMQ)"
msgstr ""
"OpenStack 控制服务(镜像服务、认证服务、网络服务以及例如 MariaDB 和 RabbitMQ "
"之类的支撑服务)"
msgid "OpenStack Foundation"
msgstr "OpenStack基金会"
msgid "OpenStack Identity (keystone)"
msgstr "OpenStack 认证(keystone)"
msgid "OpenStack Networking"
msgstr "OpenStack 联网方式(neutron)"
msgid "OpenStack Networking (neutron)"
msgstr "OpenStack 网络 (neutron)"
msgid ""
"OpenStack Networking (neutron) is a first class networking service that "
"gives full control over creation of virtual network resources to tenants. "
"This is often accomplished in the form of tunneling protocols which will "
"establish encapsulated communication paths over existing network "
"infrastructure in order to segment tenant traffic. These methods vary "
"depending on the specific implementation, but some of the more common "
"methods include tunneling over GRE, encapsulating with VXLAN, and VLAN tags."
msgstr ""
"OpenStack网络 (neutron) 是第一次实现为租户提供全部的控制权来建立虚拟网络资源"
"的网络服务。为了实现给租户流量分段，通常是基于已有的网络基础设施来封装通信路"
"径，即以隧道协议的方式。这些方法严重依赖与特殊的实现方式，大多数通用的方式包"
"括GRE隧道，VXLAN封\n"
"装以及VLAN标签。"
msgid "OpenStack Networking (neutron) or legacy networking (nova-network)"
msgstr "OpenStack 网络 (neutron) 或遗留网路服务 (nova-network)"
msgid ""
"OpenStack Networking and legacy networking both have their advantages and "
"disadvantages. They are both valid and supported options that fit different "
"network deployment models described in the <citetitle><link xlink:href="
"\"http://docs.openstack.org/openstack-ops/content/network_design."
"html#network_deployment_options\">OpenStack Operations Guide</link></"
"citetitle>."
msgstr ""
"OpenStack网络和遗留网络各有各的优点和缺点。它们有效的和支持的属性适合不同的网"
"络部署模式，详细描述见<citetitle><link xlink:href=\\\"http://docs.openstack."
"org/openstack-ops/content/network_design.html#network_deployment_options"
"\">OpenStack 运维指南</link></citetitle>。"
msgid ""
"OpenStack Networking can be used to control hardware load balancers through "
"the use of plug-ins and the Networking API. This allows users to control "
"hardware load balance pools and instances as members in these pools, but "
"their use in production environments must be carefully weighed against "
"current stability."
msgstr ""
"OpenStack网络可以通过使用插件和网络的应用程序接口控制硬件负载均衡器。允许用户"
"控制硬件负载均衡池以及作为池的成员的实例，但是使用它们在生产环境的话要小心权"
"衡它的稳定程度。"
msgid ""
"OpenStack Networking versus legacy networking (nova-network) considerations"
msgstr "OpenStack 联网方式对传统联网(nova-network) 的考虑"
msgid "OpenStack Object Storage"
msgstr "OpenStack 对象存储"
msgid "OpenStack Object Storage (swift) (or another object storage solution)"
msgstr "OpenStack 对象存储 (swift) (或者是另外的对象存储解决方案)"
msgid "OpenStack Object Storage for serving static objects (such as images)."
msgstr "OpenStack对象存储为静态对象(例如镜像)服务。"
msgid ""
"OpenStack clouds require appropriate monitoring platforms to ensure errors "
"are caught and managed appropriately. Specific meters that are critically "
"important to monitor include:"
msgstr ""
"OpenStack云需要合适的检测平台来确保错误可以及时捕获，能够更好的管理。一些特别"
"的计量值需要重点监测的有："
msgid "OpenStack compatibility"
msgstr "OpenStack 兼容性"
msgid "OpenStack components"
msgstr "OpenStack 组件"
msgid ""
"OpenStack components often require access to back-end database services to "
"store state and configuration information. Selecting an appropriate back-end "
"database that satisfies the availability and fault tolerance requirements of "
"the OpenStack services is required. OpenStack services supports connecting "
"to a database that is supported by the SQLAlchemy python drivers, however, "
"most common database deployments make use of MySQL or variations of it. We "
"recommend that the database, which provides back-end service within a "
"general purpose cloud, be made highly available when using an available "
"technology which can accomplish that goal."
msgstr ""
"OpenStack组件通常需要访问后端的数据库服务以存放状态和配置信息。选择合适的后端"
"数据库以满足可用性和容错的需求，这是OpenStack服务所要求的。OpenStack服务支持"
"的连接数据库的方式是由SQLAlchemy python所驱动，尽管如此，绝大多数部署还是使用"
"MySQL或其变种。我们建议为通用型云提供后端服务的数据库使用高可用技术确保其高可"
"用，方可达到架构设计的目标。"
msgid "OpenStack dashboard (horizon)"
msgstr "OpenStack GUI界面 (horizon)"
msgid ""
"OpenStack design, generally, does not include shared storage. However, for "
"some high availability designs, certain components might require it "
"depending on the specific implementation."
msgstr ""
"通常在OpenStack的设计中是不包括共享存储的，但是在高可用的设计中，为了特定的实"
"现一些组件会用得到共享存储。"
msgid "OpenStack hosted SDN controller: <placeholder-1/>"
msgstr "OpenStack 上运行 SDN 控制器：<placeholder-1/>"
msgid ""
"OpenStack lends itself to deployment in a highly available manner where it "
"is expected that at least 2 servers be utilized. These can run all the "
"services involved from the message queuing service, for example RabbitMQ or "
"QPID, and an appropriately deployed database service such as MySQL or "
"MariaDB. As services in the cloud are scaled out, back-end services will "
"need to scale too. Monitoring and reporting on server utilization and "
"response times, as well as load testing your systems, will help determine "
"scale out decisions."
msgstr ""
"OpenStack其本身的部署是期望高可用的，实现此需要至少两台服务器来完成。他们可以"
"运行所有的服务，由消息队列服务连接起来，消息队列服务如RabbitMQ或QPID，还需要"
"部署一个合适的数据库服务如MySQL或MariaDB。在云中所有的服务都是可横向扩展的，"
"其实后端的服务同样需要扩展。检测和报告在服务器上的使用和采集，以及负载测试，"
"都可以帮助作出横向扩展的决定。"
msgid "OpenStack on OpenStack"
msgstr "OpenStack 上的 OpenStack"
msgid "OpenStack participating in an SDN controller network: <placeholder-1/>"
msgstr "OpenStack 加入到 SDN 控制器所控制的网络中：<placeholder-1/>"
msgid "OpenStack services architecture"
msgstr "OpenStack服务架构"
msgid ""
"OpenStack services support massive horizontal scale. Be aware that this is "
"not the case for the entire supporting infrastructure. This is particularly "
"a problem for the database management systems and message queues that "
"OpenStack services use for data storage and remote procedure call "
"communications."
msgstr ""
"幸运的是，OpenStack 的服务是被设计为能够支持水平上大规模的环境的。需要清楚的"
"是这并不是整个支撑基础设施的问题。准确的说，这只是好些 OpenStack 的服务进行数"
"据存储以及远程过程调用通信所用到的数据库管理系统和消息队列的问题。"
msgid ""
"OpenStack supports a wide variety of hypervisors, one or more of which can "
"be used in a single cloud. These hypervisors include:"
msgstr ""
"OpenStack支持多种Hypervisor,在单一的云中可以有一种或多种。这些Hypervisor包"
"括："
msgid "Operating system (OS) and hypervisor"
msgstr "操作系统(OS)和虚拟机管理软件"
msgid ""
"Operating system (OS) selection plays a large role in the design and "
"architecture of a cloud. There are a number of OSes which have native "
"support for OpenStack including:"
msgstr ""
"操作系统(OS)的选择在云的设计和架构中扮演着重要的角色。有许多操作系统是原生就"
"支持OpenStack的，它们是："
msgid "Operating system and application image store."
msgstr "操作系统和应用镜像存储。"
msgid "Operating system and hypervisor"
msgstr "操作系统和虚拟机管理软件"
msgid "Operating systems and their compatibility with the OpenStack hypervisor"
msgstr "操作系统以及和 OpenStack hypervisor的兼容性"
msgid "Operational considerations"
msgstr "运营因素"
msgid ""
"Operational considerations determine the requirements for logging, "
"monitoring, and alerting. Each of these sub-categories includes options. For "
"example, in the logging sub-category you could select Logstash, Splunk, Log "
"Insight, or another log aggregation-consolidation tool. Store logs in a "
"centralized location to facilitate performing analytics against the data. "
"Log data analytics engines can also provide automation and issue "
"notification, by providing a mechanism to both alert and automatically "
"attempt to remediate some of the more commonly known issues."
msgstr ""
"对日志、监测以及报警的需求是由运维考虑决定的。它们的每个子类别都包含了大量的"
"属性。举例，在日志子类别中，某些情况考虑使用Logstash,Splunk，instanceware "
"Log Insight等，或者其他的日志聚合-合并工具。日志需要存放在中心地带，使分析数"
"据变得更为简单。日志数据分析引擎亦得提供自动化和问题通知，通过提供一致的预警"
"和自动修复某些常见的已知问题。"
msgid "Operational costs"
msgstr "运营成本"
msgid "Operator requirements"
msgstr "运营者的需求"
msgid "Orchestration (heat)"
msgstr "编排 (heat)"
msgid "Orchestration module"
msgstr "编排模块"
msgid ""
"Organizations need to determine if it is logical to create their own clouds "
"internally. Using a private cloud, organizations are able to maintain "
"complete control over architectural and cloud components."
msgstr ""
"组织需要决定在内部建立自己的云的逻辑。私有云的使用，组织需要维护整个架构中的"
"控制点以及组件。"
msgid ""
"Outside of the traditional data center the limitations of layer-2 network "
"architectures become more obvious."
msgstr "在传统数据中心之外，二层网络架构的局限性更加明显。"
msgid "Overlay interconnects for joining separated tenant networks"
msgstr "覆盖网络之间的相互连接以连接分离的租户网络"
msgid "Overlay networks"
msgstr "覆盖网络"
msgid "Performance"
msgstr "性能"
msgid ""
"Performance of the controller services is not limited to processing power, "
"but restrictions may emerge in serving concurrent users. Ensure that the "
"APIs and Horizon services are load tested to ensure that you are able to "
"serve your customers. Particular attention should be made to the OpenStack "
"Identity Service (Keystone), which provides the authentication and "
"authorization for all services, both internally to OpenStack itself and to "
"end-users. This service can lead to a degradation of overall performance if "
"this is not sized appropriately."
msgstr ""
"控制器服务的性能不仅仅限于处理器的强大能力，也受限于所服务的并发用户。确认应"
"用程序接口和Horizon服务的负载测试可以>承受来自用户客户的压力。要特别关注"
"OpenStack认证服务(Keystone)的负载，Keystone为所有服务提供认证和授权，无论是最"
"终用户还是OpenStack的内部服务。如果此控制器服务没有正确的被设计，会导致整个环"
"境的性能低下。"
msgid "Performance tuning"
msgstr "性能调优"
msgid "Persistent block storage."
msgstr "持久化的块存储。"
msgid ""
"Physical data centers have limited physical space, power, and cooling. The "
"number of hosts (or hypervisors) that can be fitted into a given metric "
"(rack, rack unit, or floor tile) is another important method of sizing. "
"Floor weight is an often overlooked consideration. The data center floor "
"must be able to support the weight of the proposed number of hosts within a "
"rack or set of racks. These factors need to be applied as part of the host "
"density calculation and server hardware selection."
msgstr ""
"物理数据中心【相对应的有虚拟数据中心，译者注】受到物理空间、电源以及制冷的限"
"制。主机(hypervisor)的数量需要适应所给定的条件(机架，机架单元，地板)，这是另"
"外一个重要衡量规模大小的办法。地板受重通常是一个被忽视的因素。数据中心的地板"
"必须能够支撑一定数量的主机，当然是放在一个机架或一组机架中。这些因素都需要作"
"为主机密度计算的一部分和服务器硬件的选择来考虑，并需要通过。"
msgid "Planned (maintenance)"
msgstr "计划内(维护)"
msgid "Platform-as-a-Service (PaaS)"
msgstr "平台即服务(PaaS)"
msgid "Plug-in support for 3rd parties"
msgstr "有第三方的插件支持"
msgid "Policy management"
msgstr "规则管理"
msgid "Port count"
msgstr "端口数目"
msgid "Port density"
msgstr "端口密度"
msgid "Port speed"
msgstr "端口速度"
msgid "Possible solutions"
msgstr "可能的解决方案"
msgid "Possible solutions: deployment"
msgstr "可能的解决方案：部署"
msgid "Possible solutions: hypervisor"
msgstr "可能的解决方案：宿主机"
msgid "Power and cooling density"
msgstr "电源和制冷密度"
msgid "Power density"
msgstr "电源密度"
msgid "Power requirements"
msgstr "电力要求"
msgid "Preparing for the future: IPv6 support"
msgstr "为将来做准备：IPv6 支持"
msgid "Prescriptive example"
msgstr "示例"
msgid "Prescriptive examples"
msgstr "示例"
msgid "Private (non-routable) and public (floating) IP addresses"
msgstr "私有(不可路由到达)及公有(浮动) IP 地址"
msgid ""
"Projecting growth for storage, networking, and compute is only one aspect of "
"a growth plan for running OpenStack at massive scale. Growing and nurturing "
"development and operational staff is an additional consideration. Sending "
"team members to OpenStack conferences, meetup events, and encouraging active "
"participation in the mailing lists and committees is a very important way to "
"maintain skills and forge relationships in the community. For a list of "
"OpenStack training providers in the marketplace, see: <link xlink:href="
"\"http://www.openstack.org/marketplace/training/\">http://www.openstack.org/"
"marketplace/training/</link>."
msgstr ""
"对存储、网络以及计算等资源的增长进行规划只是为大规模运行 OpenStack 进行的扩展"
"规划的一个方面。对于开发及运维人员的增长以及能力的培养，也是一个重要的考虑因"
"素。让团队的成员参加 OpenStack 大型会议和聚会，鼓励团队成员积极参与邮件列表以"
"及委员会的讨论等，都是让他们保持技能领先并与社区建立良好关系的非常重要的方"
"式。另外，这里还有一个市场上提供 OpenStack 相关技能培训的机构的列表：<link "
"xlink:href=\"http://www.openstack.org/marketplace/training/\">http://www."
"openstack.org/marketplace/training/</link>."
msgid "Protocol support"
msgstr "协议支持"
msgid "Provider API changes"
msgstr "提供者 API 变化"
msgid "Provider availability or implementation details"
msgstr "供应商可用性或实现细节"
msgid "Providing a simple database"
msgstr "提供一简单的数据库"
msgid "Proxy:"
msgstr "代理："
msgid "Public"
msgstr "公有"
msgid "Public cloud"
msgstr "公有云"
msgid ""
"Put your eggs in multiple baskets: Leverage multiple providers, geographic "
"regions and availability zones to accommodate for local availability issues. "
"Design for portability."
msgstr ""
"将鸡蛋放在多个篮子里：考虑多个供应商，基于地理分区不同的数据中心，多可用的"
"zones以容纳本地存在的隐患。可移植性的设计。"
msgid "Quota management"
msgstr "配额管理"
msgid "RAM allocation ratio: 1.5:1"
msgstr "RAM 超分配比例: 1.5:1"
msgid "RAM-intensive"
msgstr "内存密集型"
msgid "REST proxy:"
msgstr "REST 代理："
msgid ""
"Rack-mounted servers that support multiple independent servers in a single "
"2U or 3U enclosure, \"sled servers\", deliver increased density as compared "
"to a typical 1U-2U rack-mounted servers."
msgstr ""
"“雪撬服务器”,支持在单个2U或3U的空间放置多个独立的服务器,增加的密度超过典型的"
"1U-2U机架服务器，"
msgid "Raw block storage"
msgstr "Raw 块存储"
msgid "Red Hat Enterprise Linux (RHEL)"
msgstr "红帽企业Linux(RHEL)"
msgid "Reduced overhead of the IP hierarchy."
msgstr "减少了 IP 层的开销"
msgid "Redundancy"
msgstr "冗余"
msgid ""
"Redundancy and availability requirements impact the decision to use a RAID "
"controller card in block storage nodes. The input-output per second (IOPS) "
"demand of your application will influence whether or not you should use a "
"RAID controller, and which level of RAID is required. Making use of higher "
"performing RAID volumes is suggested when considering performance. However, "
"where redundancy of block storage volumes is more important we recommend "
"making use of a redundant RAID configuration such as RAID 5 or RAID 6. Some "
"specialized features, such as automated replication of block storage "
"volumes, may require the use of third-party plug-ins and enterprise block "
"storage solutions in order to provide the high demand on storage. "
"Furthermore, where extreme performance is a requirement it may also be "
"necessary to make use of high speed SSD disk drives' high performing flash "
"storage solutions."
msgstr ""
"决定在块存储节点中使用RAID控制卡主要取决于应用程序对冗余和可用性的需求。应用"
"如果对每秒输入输出(IOPS)有很高的要求，不仅得使用RAID控制器，还得配置RAID的级"
"别值，当性能是重要因素时，建议使用高级别的RAID值，相对比的情况是，如果冗余的"
"因素考虑更多谢，那么就使用冗余RAID配置，比如RAID5或RAID6。一些特殊的特性，例"
"如自动复制块存储卷，需要使用第三方插件和企业级的块存储解决方案，以满足此高级"
"需求。进一步讲，如果有对性能有极致的要求，可以考虑使用告诉的SSD磁盘，即高性能"
"的flash存储解决方案。"
msgid "Redundant networking: ToR switch high availability risk analysis"
msgstr "冗余网络：柜顶交换机高可用风险分析"
msgid "References"
msgstr "参考"
msgid "Reliability"
msgstr "可靠性"
msgid "Reliability and availability"
msgstr "可靠性和可用性："
msgid ""
"Reliability and availability depend on wide area network availability and on "
"the level of precautions taken by the service provider."
msgstr "可靠性和可用性依赖于广域网的可用性以及服务提供商采取的预防措施的级别。"
msgid "Remaining licensing details are filled in by the template."
msgstr "其余的授权细节来自于模版"
msgid "Replication"
msgstr "重复"
msgid ""
"Repurposing an existing OpenStack environment to be massively scalable is a "
"formidable task. When building a massively scalable environment from the "
"ground up, ensure you build the initial deployment with the same principles "
"and choices that apply as the environment grows. For example, a good "
"approach is to deploy the first site as a multi-site environment. This "
"enables you to use the same deployment and segregation methods as the "
"environment grows to separate locations across dedicated links or wide area "
"networks. In a hyperscale cloud, scale trumps redundancy. Modify "
"applications with this in mind, relying on the scale and homogeneity of the "
"environment to provide reliability rather than redundant infrastructure "
"provided by non-commodity hardware solutions."
msgstr ""
"将一个现存的为其他目的而设计的 OpenStack 环境改造成为可大规模扩展的类型，是一"
"项艰巨的任务。当从头建造一个可大规模扩展的环境时，需要确保初始的部署也是依据"
"不管环境如何增长依然能够适用的原则和选择而建造的。举例来说，在只在第一个地点"
"进行部署的时候，就将整个环境当作是一个多点环境进行部署，就是一个比较好的方"
"式，因为这使得相同的部署及隔离方法，随着环境的扩展，也能够在其它不同的地点被"
"使用，这些地点之间通过专门的线路或者广域网进行连接。在超大规模的环境中，扩展"
"胜过冗余。这种场景下的应用必须依据这个原则进行修改，依赖于整个环境的规模和扩"
"展性和同质性以提供可靠性，而不是使用非商品的硬件解决方案提供的冗余基础设施。"
msgid ""
"Resiliency of overall system and individual components are going to be "
"dictated by the requirements of the SLA, meaning designing for high "
"availability (HA) can have cost ramifications."
msgstr ""
"保持弹性的系统，松耦合的组件，都是SLA的需求，这也意味着设计高可用(HA)需要花费"
"更多。"
msgid "Resource capacity"
msgstr "资源容量"
msgid "Response time to the Compute API"
msgstr "计算API的响应时间"
msgid "Revenue opportunity"
msgstr "赢利空间"
msgid "Risk mitigation and management considerations"
msgstr "风险规避和管理考虑"
msgid "Risks"
msgstr "风险"
msgid "Routing daemons"
msgstr "路由守护进程"
msgid "Routing through or avoiding specific networks"
msgstr "使路由通过或者避免通过某个特定网络"
msgid ""
"Running OpenStack at massive scale requires striking a balance between "
"stability and features. For example, it might be tempting to run an older "
"stable release branch of OpenStack to make deployments easier. However, when "
"running at massive scale, known issues that may be of some concern or only "
"have minimal impact in smaller deployments could become pain points. Recent "
"releases may address well known issues. The OpenStack community can help "
"resolve reported issues by applying the collective expertise of the "
"OpenStack developers."
msgstr ""
"在大规模的场景下运行 OpenStack 需要在稳定性与功能之间做好平衡。比如说，选择比"
"较旧的稳定版本的 OpenStack 以便使得部署更容易看起来比较令人动心。然而在大规模"
"部署的场景之下，对小规模部署造成的困扰不大或者甚至没有什么影响的已知问题，对"
"于大规模的部署来说都可能是缺陷。假如该问题是广为人知的，在通常情况下它可能在"
"较新的发布版本中被解决了。OpenStack 社区能够运用 OpenStack 社区开发者的集体智"
"慧，帮助解决报告到社区中的问题。"
msgid ""
"Running up to 140 web instances and the small number of MariaDB instances "
"requires 292 vCPUs available, as well as 584 GB RAM. On a typical 1U server "
"using dual-socket hex-core Intel CPUs with Hyperthreading, and assuming 2:1 "
"CPU overcommit ratio, this would require 8 OpenStack Compute nodes."
msgstr ""
"运行140个web实例以及少量的MariaDB实例需要292颗vCPU,以及584GB内存。在典型的1U"
"的服务器，使用双socket，16核，开启超线程的IntelCPU，计算为2:1的CPU超分配比"
"例，可以得出需要8台这样的OpenStack计算节点。"
msgid ""
"SDN is a relatively new concept that is not yet standardized, so SDN systems "
"come in a variety of different implementations. Because of this, a truly "
"prescriptive architecture is not feasible. Instead, examine the differences "
"between an existing and a planned OpenStack design and determine where "
"potential conflicts and gaps exist."
msgstr ""
"相对来说，SDN 是一个比较新的，仍未被标准化的概念，所以 SDN 系统可能来自很多不"
"同的具体实现。因此，一个真正意义上示范性架构是目前无法给出的。相反的，我们只"
"能够分析当前或者目标 OpenStack 设计中的各种不同，并确定哪些地方将会出现潜在的"
"冲突或者还存在差距。"
msgid "SUSE Linux Enterprise Server (SLES)"
msgstr "SUSE Linux Enterprise Server (SLES)"
msgid "Scalability"
msgstr "可扩展性"
msgid ""
"Scalability refers to how the storage solution performs as it expands to its "
"maximum size. Storage solutions that perform well in small configurations "
"but have degraded performance in large configurations are not scalable. A "
"solution that performs well at maximum expansion is scalable. Large "
"deployments require a storage solution that performs well as it expands."
msgstr ""
"此节参考术语\"扩展性“，来解释存储解决方案的表现可扩展到最大规模是怎么个好法。"
"一个存储解决方案在小型配置时表现良好，但是在规模扩展的过程中性能降低，这就不"
"是好的扩展性，也不会被考虑。换句话说，一个解决方案只有在规模扩展最大性能没有"
"任何的降低才是好的扩展性。"
msgid ""
"Scalability, along with expandability, is a major consideration in a general "
"purpose OpenStack cloud. It might be difficult to predict the final intended "
"size of the implementation as there are no established usage patterns for a "
"general purpose cloud. It might become necessary to expand the initial "
"deployment in order to accommodate growth and user demand."
msgstr ""
"可扩展性是通用型OpenStack云主要考虑的因素。正因为通用型云没有固定的使用模式，"
"也许导致预测最终的使用大小是很困难的。也许就有必要增加初始部署规模以应对数据"
"增长和用户需求。"
msgid "Scale"
msgstr "规模"
msgid "Scale and performance"
msgstr "规模和性能"
msgid "Scales well"
msgstr "能够很好地扩展"
msgid "Scaling Block Storage"
msgstr "扩展块存储"
msgid "Scaling Object Storage"
msgstr "扩展对象存储"
msgid "Scaling requires 3rd party plug-ins"
msgstr "需要第三方插件进行扩展"
msgid "Scaling storage services"
msgstr "扩展存储服务"
msgid ""
"Scaling storage solutions in a storage-focused OpenStack architecture design "
"is driven by initial requirements, including <glossterm>IOPS</glossterm>, "
"capacity, bandwidth, and future needs. Planning capacity based on projected "
"needs over the course of a budget cycle is important for a design. The "
"architecture should balance cost and capacity, while also allowing "
"flexibility to implement new technologies and methods as they become "
"available."
msgstr ""
"在一个存储型的 OpenStack 架构设计当中，存储解决方案的规模，是由初始的需求，包"
"括 <glossterm>IOPS</glossterm>、容量以及带宽等，以及未来的需要所决定的。对于"
"一个设计来说，在整个预算周期之中，基于项目需要而计划容量，是很重要的。理想情"
"况下，所选择的架构必须在成本以及容量之间做出平衡，同时又必须提供足够的灵活"
"性，以便在新技术和方法可用时实现它们。"
msgid ""
"Scott Lowe (VMware) <link xlink:href=\"http://twitter.com/scott_lowe"
"\">@scott_lowe</link>"
msgstr ""
"Scott Lowe (VMware) <link xlink:href=\"http://twitter.com/scott_lowe"
"\">@scott_lowe</link>"
msgid ""
"Sean Collins (Comcast) <link xlink:href=\"http://twitter.com/sc68cal"
"\">@sc68cal</link>"
msgstr ""
"Sean Collins (Comcast) <link xlink:href=\"http://twitter.com/sc68cal"
"\">@sc68cal</link>"
msgid ""
"Sean Winn (Cloudscaling) <link xlink:href=\"http://twitter.com/seanmwinn"
"\">@seanmwinn</link>"
msgstr ""
"Sean Winn (Cloudscaling) <link xlink:href=\"http://twitter.com/seanmwinn"
"\">@seanmwinn</link>"
msgid ""
"Sebastian Gutierrez (Red Hat) <link xlink:href=\"http://twitter.com/gutseb"
"\">@gutseb</link>"
msgstr ""
"Sebastian Gutierrez (Red Hat) <link xlink:href=\"http://twitter.com/gutseb"
"\">@gutseb</link>"
msgid "Security"
msgstr "安全性"
msgid "Security levels"
msgstr "安全级别"
msgid ""
"Security should be implemented according to asset, threat, and vulnerability "
"risk assessment matrices. For cloud domains that require increased computer "
"security, network security, or information security, a general purpose cloud "
"is not considered an appropriate choice."
msgstr ""
"安全应根据资产，威胁和脆弱性风险评估矩阵来实现。对于云领域来说，更加增加了计"
"算安全、网络安全和信息安全等的需求。通用型云不被认为是恰当的选择。"
msgid "Segregation example"
msgstr "隔离的例子"
msgid ""
"Selected supplemental software solution impacts and affects the overall "
"OpenStack cloud design. This includes software for providing clustering, "
"logging, monitoring and alerting."
msgstr ""
"选择支撑软件解决方案影响着整个OpenStack云设计过程。这些软件可提供诸如集群、日"
"志、监控以及告警。"
msgid ""
"Selecting a commercially supported hypervisor, such as Microsoft Hyper-V, "
"will result in a different cost model rather than community-supported open "
"source hypervisors including <glossterm baseform=\"kernel-based VM "
"(KVM)\">KVM</glossterm>, Kinstance or <glossterm>Xen</glossterm>. When "
"comparing open source OS solutions, choosing Ubuntu over Red Hat (or vice "
"versa) will have an impact on cost due to support contracts."
msgstr ""
"选择商业支持的hypervisor，诸如微软 Hyper-V，和使用社区支持的开源hypervisor相"
"比，在开销方面有很大的差别。开源的hypervisor有<glossterm baseform=\"kernel-"
"based VM (KVM)\">KVM</glossterm>, Kinstance or <glossterm>Xen</glossterm>。当"
"比较开源操作系统解决方案时，选择了Ubuntu而不是红帽(反之亦然)，由于支持的合同"
"不同，开销也会不一样。"
msgid "Selecting networking hardware"
msgstr "选择网络硬件"
msgid "Selecting storage hardware"
msgstr "选择存储硬件"
msgid ""
"Selecting 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 ""
"决定合适的区域设计的关键是对象存储集群的扩展，还能同时提供可靠和冗余的存储系"
"统。进一步讲，也许还需要根据不同的需求配置存储的策略，这些策略包括副本，保留"
"以及其它在特定区域会严重影响到存储设计的因素。"
msgid "Selection of OpenStack software components"
msgstr "选择OpenStack软件组件"
msgid "Selection of supplemental software"
msgstr "选择支撑软件"
msgid "Separation of duties"
msgstr "职责分工"
msgid "Server density"
msgstr "服务器密度"
msgid "Server hardware"
msgstr "服务器硬件"
msgid "Signal processing for network function virtualization (NFV)"
msgstr "专门处理网络功能虚拟化(NFV)"
msgid ""
"Similarly, the default RAM allocation ratio of 1.5:1 means that the "
"scheduler allocates instances to a physical node as long as the total amount "
"of RAM associated with the instances is less than 1.5 times the amount of "
"RAM available on the physical node."
msgstr ""
"同样的，默认的内存超分配比例是1.5:1，这意味着调度器为实例分配的内存总量要少于"
"物理节点内存的1.5倍。"
msgid "Simple, single agent"
msgstr "简单，单独一个代理程序"
msgid "Single Point Of Failure (SPOF)"
msgstr "单点故障(SPOF)"
msgid "Site loss and recovery"
msgstr "站点失效和恢复"
msgid ""
"Sizing is an important consideration for a general purpose OpenStack cloud. "
"The expected or anticipated number of instances that each hypervisor can "
"host is a common meter used in sizing the deployment. The selected server "
"hardware needs to support the expected or anticipated instance density."
msgstr ""
"对于通用型OpenStack云来说规模大小是一个很重要的考虑因素。预料或预期在每个"
"hypervisor上可以运行多少实例，是部署中衡量大小的一个普遍元素。选择服务器硬件"
"需要支持预期的实例密度。"
msgid "Skills and training"
msgstr "技能和培训"
msgid "Software bundles"
msgstr "软件集合"
msgid "Software selection"
msgstr "软件选择"
msgid ""
"Software selection for a general purpose OpenStack architecture design needs "
"to include these three areas:"
msgstr "软件选择对于通用型 OpenStack 架构设计来说需要包括以下三个方面："
msgid "Software to provide load balancing"
msgstr "提供负载均衡的软件"
msgid "Software-defined networking"
msgstr "软件定义网络"
msgid ""
"Software-defined networking (SDN) is the separation of the data plane and "
"control plane. SDN is a popular method of managing and controlling packet "
"flows within networks. SDN uses overlays or directly controlled layer-2 "
"devices to determine flow paths, and as such presents challenges to a cloud "
"environment. Some designers may wish to run their controllers within an "
"OpenStack installation. Others may wish to have their installations "
"participate in an SDN-controlled network."
msgstr ""
"软件定义网络(SDN)指的是网络数据转发平面以及控制平面的隔离。SDN 已经成为在网络"
"中管理及控制网络包流的流行方案。SDN 使用覆盖网络或者直接控制的-2层网络设备来"
"监测网络流的路径，这对云环境提出了一些挑战。有些设计者可能希望在 OpenStack 环"
"境中运行他们的控制器。另外一些则可能希望将他们的 OpenStack 环境加入到一个 由 "
"SDN 方式进行控制的网络之中。"
msgid "Solutions"
msgstr "解决方案"
msgid ""
"Solutions that employ Galera/MariaDB require at least three MySQL nodes."
msgstr "解决方案采用Galera/MariaDB，需要至少3个MySQL节点。"
msgid ""
"Some applications that interact with a network require specialized "
"connectivity. Applications such as a looking glass require the ability to "
"connect to a BGP peer, or route participant applications may need to join a "
"network at a layer 2 level."
msgstr ""
"有些与网络进行互动的应用需要更加专门的连接。类似于 looking glass 之类的应用需"
"要连接到 BGP 节点，或者路由参与者应用可能需要在2层上加入一个网络。"
msgid ""
"Some areas that could be impacted by the selection of OS and hypervisor "
"include:"
msgstr "可能受到 OS 和虚拟管理程序的选择所影响的一些领域包括："
msgid ""
"Some of the key considerations that should be included in the selection of "
"networking hardware include:"
msgstr "选择联网硬件时需要考虑的一些关键因素包括："
msgid ""
"Some of the key technical considerations that are critical to a storage-"
"focused OpenStack design architecture include:"
msgstr "对存储型的 OpenStack 设计架构来说比较关键的一些技术上的考虑因素包括："
msgid ""
"Some of these software packages are described in more detail in the "
"<citetitle>OpenStack High Availability Guide</citetitle> (refer to the <link "
"xlink:href=\"http://docs.openstack.org/high-availability-guide/content/ch-"
"network.html\">Network controller cluster stack chapter</link> of the "
"OpenStack High Availability Guide)."
msgstr ""
"这些软件包更加详细的描述可参考 <citetitle>OpenStack高可用指南</citetitle> 中"
"的(<link xlink:href=\"http://docs.openstack.org/high-availability-guide/"
"content/ch-network.html\">Network 控制器集群</link> 章节)。"
msgid "Some possible use cases include:"
msgstr "可能的用例方案包括："
msgid ""
"Some server hardware form factors are better suited to storage-focused "
"designs than others. The following is a list of these form factors:"
msgstr ""
"一些服务器硬件的因素更加适合其他类型的，但是CPU和内存的能力拥有最高的优先级。"
msgid ""
"Some use cases that might indicate a need for a multi-site deployment of "
"OpenStack include:"
msgstr "一些应该使用多区域布署的案例可能会有以下特征:"
msgid "Special considerations"
msgstr "特殊因素"
msgid "Specialized cases"
msgstr "特殊场景"
msgid "Specialized hardware"
msgstr "专门的硬件"
msgid "Specialized networking example"
msgstr "特殊网络应用的例子"
msgid "Speed"
msgstr "速度"
msgid ""
"Staff must have training with the chosen hypervisor. Consider the cost of "
"training when choosing a solution. The support of a commercial product such "
"as Red Hat, SUSE, or Windows, is the responsibility of the OS vendor. If an "
"open source platform is chosen, the support comes from in-house resources."
msgstr ""
"无论选择那个hypervisor,相关的技术人员都要经过适当的培训和知识积累，才可以支持"
"所选择的操作系统和hypervisor组合。如果这些维护人员没有培训过，那么就得提供，"
"当然它会影响到设计中的之处。另外一个考虑的方面就是关于操作系统-hypervisor的支"
"持问题，商业产品如Red Hat，SUSE或Windows等的支持是由操作系统供应商来支持的，"
"如果选用了开源的平台，支持大部分得来自于内部资源。无论何种决定，都会影响到设"
"计时的支出。"
msgid ""
"Stay close: Reduce latency by moving highly interactive components and data "
"near each other."
msgstr "贴近原则：通过移动高度密切的组件和相似数据靠近以减少延迟。"
msgid ""
"Stephen Gordon (Red Hat) <link xlink:href=\"http://twitter.com/xsgordon"
"\">@xsgordon</link>"
msgstr ""
"Stephen Gordon (Red Hat) <link xlink:href=\"http://twitter.com/xsgordon"
"\">@xsgordon</link>"
msgid "Storage"
msgstr "存储"
msgid "Storage architecture"
msgstr "存储架构"
msgid ""
"Storage can be a significant portion of the overall system cost. For an "
"organization that is concerned with vendor support, a commercial storage "
"solution is advisable, although it comes with a higher price tag. If initial "
"capital expenditure requires minimization, designing a system based on "
"commodity hardware would apply. The trade-off is potentially higher support "
"costs and a greater risk of incompatibility and interoperability issues."
msgstr ""
"存储在整个系统的开销中占有很大一部分。对于一个组织来说关心的是提供商的支持，"
"以及更加倾向于商业的存储解决方案，尽管它们的价格是很高。假如最初的投入希望是"
"最少的，基于普通的硬件来设计系统也是可接受的，这就是权衡问题，一个是潜在的高"
"支持成本，还有兼容性和互操作性的高风险问题。"
msgid ""
"Storage capacity (gigabytes or terabytes as well as Input/Output Operations "
"Per Second (<glossterm>IOPS</glossterm>)"
msgstr "存储能力(每秒输入/输入操作(<glossterm>IOPS</glossterm>)，GB或TB）"
msgid "Storage focused"
msgstr "存储型"
msgid "Storage hardware:"
msgstr "存储硬件："
msgid "Storage limits"
msgstr "存储限制"
msgid "Storage management"
msgstr "存储管理"
msgid "Storage performance"
msgstr "存储性能"
msgid "Storage-intensive"
msgstr "存储密集型"
msgid "Structure"
msgstr "结构"
msgid "Supplemental software"
msgstr "增强软件"
msgid "Support"
msgstr "支持"
msgid "Support and maintainability"
msgstr "支持和维护"
msgid "Supportability"
msgstr "受支持程度"
msgid "Supported features"
msgstr "支持的特性"
msgid ""
"Swift is a highly scalable object store that is part of the OpenStack "
"project. This diagram explains the example architecture: <placeholder-1/>"
msgstr ""
"Swift 是一个高度可扩展的对象存储，同时它也是 OpenStack 项目中的一部分。以下是"
"说明示例架构的一幅图示：<placeholder-1/>"
msgid ""
"Technical cloud architecture requirements should be weighted against the "
"business requirements."
msgstr "技术云架构需求相比业务需求，比重占得更多一些。"
msgid "Technical considerations"
msgstr "技术因素"
msgid "Technical requirements"
msgstr "技术需求"
msgid "Telemetry module"
msgstr "计量模块"
msgid "Telemetry module (ceilometer)"
msgstr "Telemetry 模块 (ceilometer)"
msgid "Telemetry uses MongoDB."
msgstr "Telemetry 使用MongoDB。"
msgid ""
"The Controller infrastructure nodes provide management services to the end-"
"user as well as providing services internally for the operating of the "
"cloud. The Controllers run message queuing services that carry system "
"messages between each service. Performance issues related to the message bus "
"would lead to delays in sending that message to where it needs to go. The "
"result of this condition would be delays in operation functions such as "
"spinning up and deleting instances, provisioning new storage volumes and "
"managing network resources. Such delays could adversely affect an "
"application’s ability to react to certain conditions, especially when using "
"auto-scaling features. It is important to properly design the hardware used "
"to run the controller infrastructure as outlined above in the Hardware "
"Selection section."
msgstr ""
"控制器基础设施节点为最终用户提供的管理服务，以及在云内部为运维提供服务。控制"
"器较典型的现象，就是运行消息队列服务，在每个服务之间携带传递系统消息。性能问"
"题常和消息总线有关，它会延迟发送的消息到应该去的地方。这种情况的结果就是延迟"
"了实际操作的功能，如启动或删除实例、分配一个新的存储卷、管理网络资源。类似的"
"延迟会严重影响到应用的反应能力，尤其是使用了自动扩展这样的特性。所以运行控制"
"器基础设施的硬件设计是头等重要的，具体参考上述硬件选择一节。"
msgid ""
"The OS-hypervisor needs to be interoperable with other features and services "
"in the OpenStack design in order to meet the user requirements."
msgstr ""
"在OpenStack的设计中，为满足用户需求，需要操作系统的hypervisor在彼此的特性和服"
"务中要有互操作性。"
msgid ""
"The OpenStack dashboard, OpenStack Identity, and OpenStack Object Storage "
"services are components that can each be deployed centrally in order to "
"serve multiple regions."
msgstr ""
"OpenStack GUI，OpenStack认证，以及OpenStack对象存储等服务为了服务于多区域，这"
"些组件需要部署在中心化位置。"
msgid ""
"The OpenStack services themselves should be deployed across multiple servers "
"that do not represent a single point of failure. Ensuring API availability "
"can be achieved by placing these services behind highly available load "
"balancers that have multiple OpenStack servers as members."
msgstr ""
"OpenStack自身的那些服务需要在跨多个服务器上部署，不能出现单点故障。确保应用程"
"序接口的可用性，作为多个OpenStack服务的成员放在高可用负载均衡的后面。"
msgid ""
"The OpenStack-on-OpenStack project (<glossterm>TripleO</glossterm>) "
"addresses this issue. Currently, however, the project does not completely "
"cover nested stacks. For more information, see <link xlink:href=\"https://"
"wiki.openstack.org/wiki/TripleO\"> https://wiki.openstack.org/wiki/TripleO</"
"link>."
msgstr ""
"目前，OpenStack-on-OpenStack 项目(<glossterm>TripleO</glossterm)能够解决这个"
"问题，然而，这个项目并未完全覆盖嵌套 OpenStack 的场景。请参考 <link xlink:"
"href=\"https://wiki.openstack.org/wiki/TripleO\"> https://wiki.openstack.org/"
"wiki/TripleO</link> 了解该项目的更多信息。"
msgid "The author team includes:"
msgstr "作者团队成员有："
msgid ""
"The availability design requirements determine the selection of Clustering "
"Software, such as Corosync or Pacemaker. The availability of the cloud "
"infrastructure and the complexity of supporting the configuration after "
"deployment determines the impact of including these software packages. The "
"<citetitle>OpenStack High Availability Guide</citetitle> provides more "
"details on the installation and configuration of Corosync and Pacemaker."
msgstr ""
"在集群软件中如 Corosync和Pacemaker在可用性需求中占主流。包含这些软件包是主要"
"决定的，要使云基础设施具有高可用的话，当然在部署之后会带来复杂的配置。"
"<citetitle>OpenStack 高可用指南</citetitle></link> 提供了更加详细的安装和配置"
"Corosync和Pacemaker，所以在设计中这些软件包需要被包含。 "
msgid "The bleeding edge"
msgstr "最前沿"
msgid ""
"The choice of hardware specifications used in compute nodes including CPU, "
"memory and disk type directly affects the performance of the instances. "
"Other factors which can directly affect performance include tunable "
"parameters within the OpenStack services, for example the overcommit ratio "
"applied to resources. The defaults in OpenStack Compute set a 16:1 over-"
"commit of the CPU and 1.5 over-commit of the memory. Running at such high "
"ratios leads to an increase in \"noisy-neighbor\" activity. Care must be "
"taken when sizing your Compute environment to avoid this scenario. For "
"running general purpose OpenStack environments it is possible to keep to the "
"defaults, but make sure to monitor your environment as usage increases."
msgstr ""
"为计算节点选择硬件规格包括CPU,内存和磁盘类型，会直接影响到实例的性能。另外直"
"接影响性能的情形是为OpenStack服务优化参数，例如资源的超分配比例。默认情况下"
"OpenStack计算设置16:1为CPU的超分配比例，内存为1.5:1。运行跟高比例的超分配即会"
"导致有些服务无法启动。调整您的计算环境时，为了避免这种情况下必须小心。运行一"
"个通用型的OpenStack环境保持默认配置就可以，但是也要检测用户的环境中使用量的增"
"加。"
msgid ""
"The chosen high availability database solution changes according to the "
"selected database. MySQL, for example, provides several options. Use a "
"replication technology such as Galera for active-active clustering. For "
"active-passive use some form of shared storage. Each of these potential "
"solutions has an impact on the design:"
msgstr ""
"为数据库提供高可用的解决方案选择将改变基于何种数据库。如果是选择了MySQL,有几"
"种方案可供选择，如果是主-主模式集群，则使用 Galera复制技术；如果是主-备模式则"
"必须使用共享存储。每个潜在的方案都会影响到架构的设计："
msgid ""
"The cloud user expects repeatable, dependable, and deterministic processes "
"for launching and deploying cloud resources. You could deliver this through "
"a web-based interface or publicly available API endpoints. All appropriate "
"options for requesting cloud resources must be available through some type "
"of user interface, a command-line interface (CLI), or API endpoints."
msgstr ""
"云用户希望对云资源进行启动和部署有可重复的、可靠的以及可确定的操作过程。这些"
"功能可以通过基于 web 的接口或者公开可用的 API 入口抛出。对云资源进行请求的所"
"有相应选项应该通过某种类型的用户接口展现给用户，比如命令行接口(CLI)或者API 入"
"口。"
msgid ""
"The cloud user's requirements and expectations that determine the cloud "
"design focus on the consumption model. The user expects to consume cloud "
"resources in an automated and deterministic way, without any need for "
"knowledge of the capacity, scalability, or other attributes of the cloud's "
"underlying infrastructure."
msgstr ""
"可能与想像中一致，用以确定设计方案的云用户的需求以及期望，都是关注于消费模型"
"之上的。用户希望能够以一种自动化的和确定的方式来使用云中的资源，而不需要以任"
"何对容量、可扩展性或者其它关于该云的底层基础设施的属性的了解作为前提。"
msgid ""
"The company runs hardware load balancers and multiple web applications "
"serving their websites, and orchestrates environments using combinations of "
"scripts and Puppet. The website generates large amounts of log data daily "
"that requires archiving."
msgstr ""
"公司的网站运行着基于硬件的负载均衡服务器和多个web应用服务，且他们的编排环境是"
"混合使用Puppet和脚本。网站每天都会产生大量的日志文件需要归档。"
msgid ""
"The cost of components affects which storage architecture and hardware you "
"choose."
msgstr "使用什么存储架构和选择什么硬件将影响着开销。"
msgid ""
"The data security domain is concerned primarily with information pertaining "
"to the storage services within OpenStack. Much of the data that crosses this "
"network has high integrity and confidentiality requirements and, depending "
"on the type of deployment, may also have strong availability requirements. "
"The trust level of this network is heavily dependent on other deployment "
"decisions."
msgstr ""
"数据安全域主要关心的是OpenStack存储服务相关的信息。多数通过此网络的数据具有高"
"度机密的要求，甚至在某些类型的部署中，还有高可用的需求。此网络的信任级别高度"
"依赖于其他部署的决定。"
msgid ""
"The default CPU allocation ratio of 16:1 means that the scheduler allocates "
"up to 16 virtual cores per physical core. For example, if a physical node "
"has 12 cores, the scheduler sees 192 available virtual cores. With typical "
"flavor definitions of 4 virtual cores per instance, this ratio would provide "
"48 instances on a physical node."
msgstr ""
"默认的CPU超分配比例是16:1,这意味着调度器可以为每个物理核分配16个虚拟核。举例"
"来说，如果物理节点有12个核，调度器就拥有192个虚拟核。在典型的flavor定义中，每"
"实例4个虚拟核，那么此超分配比例可以在此物理节点上提供48个实例。"
msgid ""
"The design architecture of a massively scalable OpenStack cloud must address "
"considerations around physical facilities such as space, floor weight, rack "
"height and type, environmental considerations, power usage and power usage "
"efficiency (PUE), and physical security."
msgstr ""
"关于诸如空间、底部负重、机柜高度及类型、环境性因素、电源使用及其使用效率"
"(PUE)，以及物理上的安全性等等相关的物理设施的考虑因素，也应该在可大规模扩展"
"的 OpenStack 云的设计架构中一并进行考虑并解决。"
msgid ""
"The design will require networking hardware that has the requisite port "
"count."
msgstr "设计要求网络硬件有充足的端口数目。"
msgid ""
"The example REST interface, presented as a traditional Object store running "
"on traditional spindles, does not require a high performance caching tier."
msgstr ""
"所展现的 REST 接口不需要一个高性能的缓存层，并且被作为一个运行在传统设备\n"
"上的传统的对象存储抛出。"
msgid ""
"The example below shows a REST interface without a high performance "
"requirement."
msgstr "本例描绘了没有高性能需求的 REST 接口。"
msgid ""
"The factors for determining which software packages in this category to "
"select is outside the scope of this design guide."
msgstr ""
"这包括能够提供集群、日志、监测及预警等的软件。在此目录什么因素决定选择什么软"
"件包已经超出了本书的范围。"
msgid ""
"The following user considerations are written from the perspective of the "
"cloud builder, not from the perspective of the end user."
msgstr "以下用户考量的内容来自于云构建者的记录，并非最终用户。"
msgid ""
"The hardware requirements and configuration are similar to those of the High "
"Performance Database example below. In this case, the architecture uses "
"Ceph's Swift-compatible REST interface, features that allow for connecting a "
"caching pool to allow for acceleration of the presented pool."
msgstr ""
"实际的硬件需求以及配置与下面的高性能数据库例子相似。在这个场景中，采用的架构"
"使用了 Ceph 的 Swift 兼容 REST 接口，以及允许连接至一个缓存池以加速展现出来的"
"池的特性。"
msgid "The hardware selection covers three areas:"
msgstr "硬件选择涵盖三个方面："
msgid ""
"The lack of a pre-defined usage model enables the user to run a wide variety "
"of applications without having to know the application requirements in "
"advance. This provides a degree of independence and flexibility that no "
"other cloud scenarios are able to provide."
msgstr ""
"由于缺少预先定义的使用模型，导致用户在根本不知道应用需求的情况运行各式各样的"
"应用。这里（OpenStack 通用型云，译者注）提供的独立性和灵活性的深度，也就只能"
"是这么多了，不能提供更多的云场景。"
msgid ""
"The latency of storage I/O requests indicates performance. Performance "
"requirements affect which solution you choose."
msgstr "存储I/O请求的延迟影响着性能。解决方案的选择会影响到性能的需求。"
msgid ""
"The level of network hardware redundancy required is influenced by the user "
"requirements for high availability and cost considerations. Network "
"redundancy can be achieved by adding redundant power supplies or paired "
"switches. If this is a requirement, the hardware will need to support this "
"configuration."
msgstr ""
"网络硬件的冗余级别需求是受用户对于高可用和开销考虑的影响的。网络冗余可以由增"
"加冗余的电力供应和结对的交换机来实现，加入遇到这样的需求，硬件需要支持冗余的"
"配置。"
msgid ""
"The majority of OpenStack components are designed to run within the context "
"of a single region. The OpenStack Compute service is designed to manage "
"compute resources within a region, with support for subdivisions of compute "
"resources by using availability zones and cells. The OpenStack Networking "
"service can be used to manage network resources in the same broadcast domain "
"or collection of switches that are linked. The OpenStack Block Storage "
"service controls storage resources within a region with all storage "
"resources residing on the same storage network. Like the OpenStack Compute "
"service, the OpenStack Block Storage service also supports the availability "
"zone construct which can be used to subdivide storage resources."
msgstr ""
"多数的OpenStack组件被设计为运行在单个region上下文中。OpenStack计算服务被设计"
"为在一个region中管理计算资源，支持使用可用区域和单元来往下拆分。OpenStack网络"
"服务可用于在同一广播域中或者说相互连接的交换机来管理网路资源。OpenStack块存储"
"服务控制单一region中的存储资源，且这些资源须在统一存储网络中。和OpenStack计算"
"服务一样，OpenStack块存储服务同样支持可用区域的构造，用于往下拆分存储资源。"
msgid ""
"The management tools used for Ubuntu and Kinstance differ from the "
"management tools for VMware vSphere. Although both OS and hypervisor "
"combinations are supported by OpenStack, there will be very different "
"impacts to the rest of the design as a result of the selection of one "
"combination versus the other."
msgstr ""
"Ubuntu和Kinstance的管理工具和VMware vSphere的管理工具是不一样的。尽管"
"OpenStack支持它们所有的操作系统和hypervisor组合。这也会对其他的设计有着非常不"
"同的影响，结果就是选择了一种组合再作出选择。"
msgid ""
"The network design should encompass a physical and logical network design "
"that can be easily expanded upon. Network hardware should offer the "
"appropriate types of interfaces and speeds that are required by the hardware "
"nodes."
msgstr ""
"网络设计须围绕物理网路和逻辑网络能够轻松扩展的设计来开展。网络硬件须提供给服"
"务器节点所需要的合适的接口类型和速度。"
msgid ""
"The network design will be affected by the physical space that is required "
"to provide the requisite port count. A higher port density is preferred, as "
"it leaves more rack space for compute or storage components that may be "
"required by the design. This can also lead into concerns about fault domains "
"and power density that should be considered. Higher density switches are "
"more expensive and should also be considered, as it is important not to over "
"design the network if it is not required."
msgstr ""
"由于端口数量的需求，就需要更大的物理空间，以至于会影响到网络的设计。一旦首选"
"敲定了高端口密度，在设计中就得考虑为计算和存储留下机架空间。进一步还得考虑容"
"错设备和电力密度。高密度的交换机会非常的昂贵，亦需考虑在内，当然如若不是刚性"
"需求，这个是没有设计网络本身重要。"
msgid ""
"The networking hardware must support the proposed network speed, for "
"example: 1GbE, 10GbE, or 40GbE (or even 100GbE)."
msgstr ""
"网络硬件必须支持常见的网络速度，例如：1GbE、10GbE 或者 40GbE(甚至是 100GbE)。"
msgid ""
"The number of CPU cores, how much RAM, or how much storage a given server "
"delivers."
msgstr "CPU核数，多少内存，或者多少存储可以交付。"
msgid "The number of MACs stored in switch tables is limited."
msgstr "存储在交换表中的 MAC 地址数目是有限的。"
msgid ""
"The number of additional resources you can add to a server before it reaches "
"capacity."
msgstr "在达到容量之前用户可以增加服务器来增加资源的数量。"
msgid ""
"The number of organizations running at massive scales is a small proportion "
"of the OpenStack community, therefore it is important to share related "
"issues with the community and be a vocal advocate for resolving them. Some "
"issues only manifest when operating at large scale, and the number of "
"organizations able to duplicate and validate an issue is small, so it is "
"important to document and dedicate resources to their resolution."
msgstr ""
"当出现问题的时候，在差不多规模场景下运行 OpenStack 的组织的数量，相对于整个 "
"OpenStack 社区来说，是极小的一个比例，因此很重要的一件事情是要与社区分享所遇"
"到的问题，并且在社区中积极倡导将这些问题解决。有些问题可能只在大规模部署的场"
"景下才会出现，所以能够重现和验证该问题的组织是为数不多的，因此将问题良好地文"
"档化并且为问题的解决贡献一些必要的资源，是尤为重要的。"
msgid "The performance of the applications running on virtual desktops"
msgstr "在提供的虚拟桌面中运行的应用的性能"
msgid ""
"The physical space required to provide the requisite port count affects the "
"network design. A switch that provides 48 10GbE ports in 1U has a much "
"higher port density than a switch that provides 24 10GbE ports in 2U. On a "
"general scale, a higher port density leaves more rack space for compute or "
"storage components which is preferred. It is also important to consider "
"fault domains and power density. Finally, higher density switches are more "
"expensive, therefore it is important not to over design the network."
msgstr ""
"网络的设计会受到物理空间的影响，需要提供足够的端口数。一个占用1U机柜空间的可"
"提供48个 10GbE端口的交换机，显而易见的要比占用2U机柜空间的仅提供24个 10GbE端"
"口的交换机有着更高的端口密度。高端口密度是首先选择的，因为其可以为计算和存储"
"省下机柜空间。这也会引起人们的思考，容错的情况呢？电力密度？高密度的交换机更"
"加的昂贵，也应该被考虑使用，但是没有必要覆盖设计中所有的网络，要视实际情况而"
"定。"
msgid ""
"The power and cooling density requirements might be lower than with blade, "
"sled, or 1U server designs due to lower host density (by using 2U, 3U or "
"even 4U server designs). For data centers with older infrastructure, this "
"might be a desirable feature."
msgstr ""
"电力和制冷的密度需求要低于刀片、雪撬或1U服务器，因为(使用2U,3U甚至4U服务器)拥"
"有更低的主机密度。对于数据中心内有旧的基础设施，这是非常有用的特性。"
msgid "The primary factors that play into OS-hypervisor selection include:"
msgstr "影响操作系统-hypervisor选择的主要因素包括："
msgid ""
"The process for upgrading a multi-site environment is not significantly "
"different:"
msgstr "升级多区域环境的流程没有什么特别的不一样："
msgid ""
"The relative purchase price of the hardware weighted against the level of "
"design effort needed to build the system."
msgstr "相对硬件的购买价格，与构建系统所需要的设计功力的级别成反比。"
msgid ""
"The selected OS-hypervisor combination needs to be supported by OpenStack."
msgstr "选择操作系统-虚拟机管理程序组合需要OpenStack支持。"
msgid ""
"The selected supplemental software solution impacts and affects the overall "
"OpenStack cloud design. This includes software for providing clustering, "
"logging, monitoring and alerting."
msgstr ""
"所选择的支撑软件解决方案会影响到整个OpenStack云的设计，它们包括能够提供集群、"
"日志、监测以及预警的软件。"
msgid ""
"The selection of OS-hypervisor combination first and foremost needs to "
"support the user requirements."
msgstr "选择操作系统-虚拟机管理程序组合，首先且最重要的是支持用户的需求。"
msgid ""
"The software selection process plays a large role in the architecture of a "
"general purpose cloud. The following have a large impact on the design of "
"the cloud:"
msgstr ""
"软件筛选的过程在通用型云架构中扮演了重要角色。下列的选择都会在设计云时产生重"
"大的影响。"
msgid "The solution would consist of the following OpenStack components:"
msgstr "解决方案将由下列OpenStack组件组成："
msgid ""
"The starting point is the core count of the cloud. By applying relevant "
"ratios, the user can gather information about:"
msgstr "其出发点是云计算的核心数量。通过相关的比例，用户可以收集有关信息："
msgid ""
"The storage solution should take into account storage maintenance and the "
"impact on underlying workloads."
msgstr "存储的解决方案需要考虑存储的维护以及其对底层负载的影响。"
msgid ""
"The user requires networking hardware that has the requisite port count."
msgstr "用户将会对网络设备有充足的端口数有需求。"
msgid ""
"The web application instances run from local storage on each of the "
"OpenStack Compute nodes. The web application instances are stateless, "
"meaning that any of the instances can fail and the application will continue "
"to function."
msgstr ""
"web应用实例均运行在每个OpenStack计算节点的本地存储之上。所有的web应用实例都是"
"无状态的，也就是意味着任何的实例宕掉，都不会影响到整体功能的继续服务。"
msgid ""
"There are a variety of well tested tools, for example ICMP, to monitor and "
"manage traffic."
msgstr "有很多经过完善测试的工具，例如 ICMP，来监控和管理流量。"
msgid ""
"There are several factors to take into consideration when looking at whether "
"an application is a good fit for the cloud."
msgstr "寻找适合于在云中运行的应用，还是有几种方法可以考虑的。"
msgid ""
"There are special considerations around erasure coded pools. For example, "
"higher computational requirements and limitations on the operations allowed "
"on an object; erasure coded pools do not support partial writes."
msgstr ""
"请注意关于 erasure coded 池的使用有特殊的考虑因素，比如说，更高的计算要求以及"
"对象上所允许的操作限制。另外，部分写入在 erasure coded 的池中也不被支持。"
msgid ""
"There is also some customization of the filter scheduler that handles "
"placement within the cells:"
msgstr "在cell里的可以定制的过滤器："
msgid ""
"There is no single best practice architecture for the networking hardware "
"supporting a general purpose OpenStack cloud that will apply to all "
"implementations. Some of the key factors that will have a strong influence "
"on selection of networking hardware include:"
msgstr ""
"网络硬件没有单一的最佳实践架构以支持一个通用型OpenStack云，让它满足所有的实"
"现。一些在选择网络硬件时有重大影响的关键元素包括："
msgid "These security domains are:"
msgstr "这些安全域有："
msgid ""
"Think efficiency: Inefficient designs will not scale. Efficient designs "
"become cheaper as they scale. Kill off unneeded components or capacity."
msgstr ""
"考虑效率：低效的设计将不可扩展。高效的设计可以无须花费多少钱即可轻松扩展。去"
"掉那些不需要的组件或容量。"
msgid ""
"Think elasticity: Increasing resources should result in a proportional "
"increase in performance and scalability. Decreasing resources should have "
"the opposite effect."
msgstr ""
"保持弹性：随着增加的资源，确保结果是增加的性能和扩展。减少资源要没有负面影"
"响。"
msgid ""
"This application prioritizes the north-south traffic over east-west traffic: "
"the north-south traffic involves customer-facing data."
msgstr ""
"此应用将南北向的流量的优先级设置得比东西向的流量的优先级更高：南北向的流量与"
"面向客户的数据相关。"
msgid ""
"This decreases density by 50% (only 8 servers in 10 U) if a full width or "
"full height option is used."
msgstr ""
"它相比于全高的刀片有效的减低了50%的密度，因为全高的刀片在(每10个机柜单元仅可"
"以放置8台服务器)。"
msgid "This example uses the following components:"
msgstr "此例使用了如下组件："
msgid ""
"This list expands upon the potential impacts for including a particular "
"storage architecture (and corresponding storage hardware) into the design "
"for a general purpose OpenStack cloud:"
msgstr ""
"这个列表扩展了在设计通用型OpenStack云可能产生的影响，包括对特定存储架构(以及"
"相应的存储硬件)"
msgid ""
"This may be an issue for spine switches in a leaf and spine fabric, or end "
"of row (EoR) switches."
msgstr "这可能会给脊柱交换机的叶和面带来问题，同样排尾(EoR)交换机也会有问题。"
msgid ""
"This may cause issues for organizations that have preferred vendor policies "
"or concerns with support and hardware warranties of non-tier 1 vendors."
msgstr ""
"这会给企业带来额外的问题：重新评估供应商的政策，支持的力度是否够，非1线供应商"
"的硬件质量保证等。"
msgid ""
"This multi-site scenario likely includes one or more of the other scenarios "
"in this book with the additional requirement of having the workloads in two "
"or more locations. The following are some possible scenarios:"
msgstr ""
"此多区域场景在本书中有一个或多个其他类似的场景，另外在两个或多个地点的额外负"
"载需求。下面是可能一样的场景："
msgid ""
"This system can provide additional performance. For example, in the database "
"example below, a portion of the SSD pool can act as a block device to the "
"Database server. In the high performance analytics example, the inline SSD "
"cache layer accelerates the REST interface."
msgstr ""
"这种类型的系统也能够在其他场景下提供额外的性能。比如说，在下面的数据库例子"
"中，SSD 池中的一部分可以作为数据库服务器的块设备。在高性能分析的例子中，REST "
"接口将会被内联的 SSD 缓存层所加速。"
msgid "Throughput"
msgstr "吞吐量"
msgid ""
"Ticketing system (or integration with a ticketing system) to track issues."
msgstr "票务系统(或者与其它票务系统的集成)以跟踪问题。"
msgid "Time to market"
msgstr "上线时间"
msgid "Time-to-market"
msgstr "上线时间"
msgid ""
"To effectively run cloud installations, initial downtime planning includes "
"creating processes and architectures that support the following:"
msgstr "为有效的运行云，开始计划宕机包括建立流程和支持的架构有下列内容："
msgid ""
"To ensure that access to nodes within the cloud is not interrupted, we "
"recommend that the network architecture identify any single points of "
"failure and provide some level of redundancy or fault tolerance. With regard "
"to the network infrastructure itself, this often involves use of networking "
"protocols such as LACP, VRRP or others to achieve a highly available network "
"connection. In addition, it is important to consider the networking "
"implications on API availability. In order to ensure that the APIs, and "
"potentially other services in the cloud are highly available, we recommend "
"you design a load balancing solution within the network architecture to "
"accommodate for these requirements."
msgstr ""
"为确保云内部访问节点不会被中断，我们建议网络架构不要存在单点故障，应该提供一"
"定级别的冗余和容错。网络基础设施本身就能提供一部分，比如使用网络协议诸如LACP,"
"VRRP或其他的保证网络连接的高可用。另外，考虑网络实现的API可用亦非常重要。为了"
"确保云中的API以及其它服务高可用，我们建议用户设计网络架构的负载均衡解决方案，"
"以满足这些需求。"
msgid ""
"To obtain greater than dual-socket support in a 1U rack-mount form factor, "
"customers need to buy their systems from Original Design Manufacturers "
"(ODMs) or second-tier manufacturers."
msgstr ""
"要想使1U的服务器支持超过2个插槽，用户需要通过原始设计制造商(ODM)或二线制造商"
"来购买。"
msgid ""
"To reap the benefits of OpenStack, you should plan, design, and architect "
"your cloud properly, taking user's needs into account and understanding the "
"use cases."
msgstr ""
"欲充分利用OpenStack的优点，用户需要精心准备规划、设计及架构。认真纳入用户的需"
"求、揣摩透一些用例。"
msgid "Tools considerations"
msgstr "工具考量"
msgid "Topics to consider include:"
msgstr "考虑的主题有："
msgid "Tunable networking components"
msgstr "可调联网组件"
msgid "Ubuntu"
msgstr "Ubuntu"
msgid ""
"Ubuntu and Kinstance use different management tools than VMware vSphere. "
"Although both OS and hypervisor combinations are supported by OpenStack, "
"there are varying impacts to the rest of the design as a result of the "
"selection of one combination versus the other."
msgstr ""
"Ubuntu和Kinstance的管理工具和VMware vSphere的管理工具是不一样的。尽管"
"OpenStack对它们都支持。这也会对其他的设计有着非常不同的影响，结果就是选择了一"
"种组合，然后再据此做出后面的选择。"
msgid ""
"Unfortunately, Compute is the only OpenStack service that provides good "
"support for cells. In addition, cells do not adequately support some "
"standard OpenStack functionality such as security groups and host "
"aggregates. Due to their relative newness and specialized use, cells receive "
"relatively little testing in the OpenStack gate. Despite these issues, cells "
"play an important role in well known OpenStack installations operating at "
"massive scale, such as those at CERN and Rackspace."
msgstr ""
"使用单元的缺点是这种解决方案在 OpenStack 的服务中，只有计算服务支持得比较好。"
"并且，这种方案也不能够支持一些相对基础的 OpenStack 功能，例如安全组和主机聚"
"合。由于这种方案比较新，并且用途相对特别，在 OpenStack 之中对这种方案的测试也"
"相对比较有限。即使存在种种的这些问题，单元还是在一些著名的大规模 OpenStack 环"
"境中被使用了，包括 CERN 和 Rackspace 中的那些。"
msgid "Unplanned (system faults)"
msgstr "计划外(系统出错)"
msgid ""
"Unstructured data store for services. For example, social media back-end "
"storage."
msgstr "某些服务的非结构化数据存储。比如社交媒体的后端存储。"
msgid "Upgrade OpenStack Block Storage (cinder) at each site."
msgstr "在每个区域升级OpenStack块存储 (cinder)。"
msgid "Upgrade OpenStack Block Storage (cinder)."
msgstr "升级 OpenStack 块存储 (cinder)。"
msgid ""
"Upgrade OpenStack Compute (nova), including networking components, at each "
"site."
msgstr "在每个区域升级OpenStack计算(nova),包括网络组件。"
msgid "Upgrade OpenStack Compute (nova), including networking components."
msgstr "升级 OpenStack 计算 (nova), 包括网络组件。"
msgid "Upgrade the OpenStack Identity service (keystone)."
msgstr "升级OpenStack认证服务 (keystone)."
msgid ""
"Upgrade the OpenStack dashboard (horizon), at each site or in the single "
"central location if it is shared."
msgstr ""
"在每个区域升级OpenStack GUI程序(horizon),或者假如它是共享的话，仅升级单个的数"
"据中心即可。"
msgid "Upgrade the OpenStack dashboard (horizon)."
msgstr "升级 OpenStack GUI程序 (horizon)。"
msgid "Upgrade the shared OpenStack Identity service (keystone) deployment."
msgstr "升级 OpenStack 认证共享服务 (keystone) 。"
msgid "Upgrades"
msgstr "升级"
msgid "Upper-layer services"
msgstr "上层服务"
msgid "Usage"
msgstr "用量"
msgid ""
"Use cases that benefit from scale-out rather than scale-up approaches are "
"good candidates for general purpose cloud architecture."
msgstr "在通用型云架构中，用例能够明确感受到横向扩展带来好处远远大于纵向扩展。"
msgid "Use eBGP to connect to the Internet up-link."
msgstr "使用 eBGP 连接至因特网上行链路。"
msgid ""
"Use hierarchical addressing because it is the only viable option to scale "
"network ecosystem."
msgstr ""
"使用具有层次结构的地址分配机制，因为这是扩展网络生态环境的唯一可行选项。"
msgid "Use iBGP to flatten the internal traffic on the layer-3 mesh."
msgstr "在三层网络上使用 iBGP 将内部网络流量扁平化。"
msgid ""
"Use of DAS impacts the server hardware choice and affects host density, "
"instance density, power density, OS-hypervisor, and management tools."
msgstr ""
"如果解决方案中使用了DAS，这会影响到但不限于，服务器硬件的选择会波及到主机密"
"度、实例密度、电力密度、操作系统-hypervisor、以及管理工具。"
msgid "Use traffic shaping for performance tuning."
msgstr "使用流量整形工具调整网络性能。"
msgid ""
"Use virtual networking to isolate instance service network traffic from the "
"management and internal network traffic."
msgstr "使用虚拟联网将实例服务网络流量从管理及内部网络流量中隔离出来。"
msgid "User requirements"
msgstr "用户需求"
msgid ""
"User requirements for high availability and cost considerations influence "
"the required level of network hardware redundancy. Achieve network "
"redundancy by adding redundant power supplies or paired switches."
msgstr ""
"网络硬件冗余级别需求会被用户对高可用和开销的考虑所影响。网络冗余可以是增加双"
"电力供应也可以是结对的交换机。"
msgid ""
"Users will want to combine using the internal cloud with access to an "
"external cloud. If that case is likely, it might be worth exploring the "
"possibility of taking a multi-cloud approach with regard to at least some of "
"the architectural elements."
msgstr ""
"用户打算既使用内部云又可访问外部云的组合。假如遇到类似的用例，也许值得一试的"
"就是基于多个云的途径，考虑至少多个架构要点。"
msgid ""
"Using Ceph as an applicable example, a potential architecture would have the "
"following requirements:"
msgstr "跟上面的例子相关的 Ceph 的一个可能架构需要如下组件："
msgid "Utilization"
msgstr "量力而行"
msgid "VLANs are an easy mechanism for isolating networks."
msgstr "VLAN 是一个简单的用于网络隔离的机制。"
msgid "Video Conference or web conference"
msgstr "视频会议和 web 会议"
msgid ""
"Vinny Valdez (Red Hat) <link xlink:href=\"http://twitter.com/VinnyValdez"
"\">@VinnyValdez</link>"
msgstr ""
"Vinny Valdez (Red Hat) <link xlink:href=\"http://twitter.com/VinnyValdez"
"\">@VinnyValdez</link>"
msgid ""
"Virtual Desktop Infrastructure (VDI) is a service that hosts user desktop "
"environments on remote servers. This application is very sensitive to "
"network latency and requires a high performance compute environment. "
"Traditionally these types of services do not use cloud environments because "
"few clouds support such a demanding workload for user-facing applications. "
"As cloud environments become more robust, vendors are starting to provide "
"services that provide virtual desktops in the cloud. OpenStack may soon "
"provide the infrastructure for these types of deployments."
msgstr ""
"虚拟桌面基础设施(VDI)是在远程服务器上提供用户桌面环境的服务。此类应用对于网络"
"延迟非常敏感并且需要一个高性能的计算环境。传统上这类环境并未成放到云环境之"
"中，因为极少的云环境会支持如此程度暴露给终端用户的高要求负载。近来，随着云环"
"境的稳定性越来越高，云厂商们开始提供能够在云中运行虚拟桌面的服务。在不远的将"
"来，OpenStack 便能够作为运行虚拟桌面基础设施的底层设施，不管是内部的，还是在"
"云端。"
msgid "Virtual compute resources"
msgstr "虚拟计算资源"
msgid "Virtual desktop infrastructure (VDI)"
msgstr "虚拟桌面基础设施(VDI)"
msgid "Virtual-machine disk image library"
msgstr "虚拟机磁盘镜像库"
msgid "Virtualized network topologies"
msgstr "虚拟化网络拓扑"
msgid "Voice over IP (VoIP)"
msgstr "IP 语音(VoIP)"
msgid ""
"We recommend building a development and operations organization that is "
"responsible for creating desired features, diagnosing and resolving issues, "
"and building the infrastructure for large scale continuous integration tests "
"and continuous deployment. This helps catch bugs early and makes deployments "
"faster and easier. In addition to development resources, we also recommend "
"the recruitment of experts in the fields of message queues, databases, "
"distributed systems, networking, cloud, and storage."
msgstr ""
"我们的建议是组织一个开发和运营的团队，由他们来负责开发所需要的特性，调试以及"
"解决问题，并建造用以进行大规模持续集成测试以及持续部署的基础设施。这能够及早"
"地发现缺陷以及使得部署更快和更加简单。除了开发的资源之外，我们也建议招聘消息"
"队列、数据库、分布式系统、网络、云以及存储方面的专家人员。"
msgid ""
"We recommend general purpose clouds use hypervisors that support the most "
"general purpose use cases, such as KVM and Xen. More specific hypervisors "
"should be chosen to account for specific functionality or a supported "
"feature requirement. In some cases, there may also be a mandated requirement "
"to run software on a certified hypervisor including solutions from VMware, "
"Microsoft, and Citrix."
msgstr ""
"通用型云须确保使用的hypervisor可以支持多数通用目的的用例，例如KVM或Xen。更多"
"特定的hypervisor需要根据特定的功能和支持特性需求来做出选择。在一些情况下，也"
"许是授权所需，需要运行的软件必须是在认证的hpervisor中，比如来自VMware，微软和"
"思杰的产品。"
msgid ""
"We would like to thank VMware for their generous hospitality, as well as our "
"employers, Cisco, Cloudscaling, Comcast, EMC, Mirantis, Rackspace, Red Hat, "
"Verizon, and VMware, for enabling us to contribute our time. We would "
"especially like to thank Anne Gentle and Kenneth Hui for all of their "
"shepherding and organization in making this happen."
msgstr ""
"我们非常感谢VMware的盛情款待，以及我们的雇主，Cisco, Cloudscaling,Comcast,"
"EMC,Mirantis,Rackspace,Red Hat, Verizon和VMware,能够让我们花时间做点有意义的"
"事情。尤其感谢Anne Gentle 和 Kenneth Hui，由于二位的领导和组织，才有此书诞生"
"的机会。"
msgid "Web Servers, running Apache."
msgstr "Web服务，运行 Apache。"
msgid "Web portals or web services"
msgstr "web 门户或 web 服务"
msgid ""
"When building a general purpose cloud, you should follow the <glossterm "
"baseform=\"IaaS\">Infrastructure-as-a-Service (IaaS)</glossterm> model; a "
"platform best suited for use cases with simple requirements. General purpose "
"cloud user requirements are not complex. However, it is important to capture "
"them even if the project has minimum business and technical requirements, "
"such as a proof of concept (PoC), or a small lab platform."
msgstr ""
"当构建通用型云时，用户需要遵循 <glossterm baseform=\"IaaS\">Infrastructure-"
"as-a-Service (IaaS)</glossterm>模式，基于简单的需求为用户寻求最合适的平台。通"
"用型云的用户需求并不复杂。尽管如此，也要谨慎对待，即使项目是较小的业务，或者"
"诸如概念验证、小型实验平台等技术需求。"
msgid ""
"When building a storage-focused OpenStack architecture, strive to build a "
"flexible design based on an industry standard core. One way of accomplishing "
"this might be through the use of different back ends serving different use "
"cases."
msgstr ""
"当尝试构建一个基于行业标准核心的灵活设计时，实现这个的一个办法，可能是通过使"
"用不同的后端服务于不同的使用场景。"
msgid ""
"When connecting multiple regions together there are several design "
"considerations. The overlay network technology choice determines how packets "
"are transmitted between regions and how the logical network and addresses "
"present to the application. If there are security or regulatory "
"requirements, encryption should be implemented to secure the traffic between "
"regions. For networking inside a region, the overlay network technology for "
"tenant networks is equally important. The overlay technology and the network "
"traffic of an application generates or receives can be either complementary "
"or be at cross purpose. For example, using an overlay technology for an "
"application that transmits a large amount of small packets could add "
"excessive latency or overhead to each packet if not configured properly."
msgstr ""
"当连接多个region到一起时需要考虑很多设计因素。覆盖网络技术的选择决定了网络包"
"如何在region之间传输，以及如何给应用赋予逻辑网络和地址。如果有安全或监管需"
"求，还得使用加密技术实现region之间的安全传输。在region内部网络，租户网络的覆"
"盖网络技术亦同等重要，网络覆盖技术和应用生成或接受的网络流量可以是互补的或者"
"交叉目的。例如，使用覆盖技术为一个应用，而中间传输使用了大量的小网络包，如果"
"配置不当会引起大量的延迟或增大每个包的开销。"
msgid ""
"When considering performance of OpenStack Block Storage, hardware and "
"architecture choice is important. Block Storage can use enterprise back-end "
"systems such as NetApp or EMC, scale out storage such as GlusterFS and Ceph, "
"or simply use the capabilities of directly attached storage in the nodes "
"themselves. Block Storage may be deployed so that traffic traverses the host "
"network, which could affect, and be adversely affected by, the front-side "
"API traffic performance. As such, consider using a dedicated data storage "
"network with dedicated interfaces on the Controller and Compute hosts."
msgstr ""
"当考虑OpenStack块设备的性能时，硬件和架构的选择就显得非常重要。块存储可以使用"
"企业级后端系统如NetApp或EMC的产品，也可以使用横向扩展存储如GlusterFS和Ceph，"
"更可以是简单的在节点上直接附加的存储。块存储或许是云所关注的贯穿主机网络的部"
"署，又或许是前端应用程序接口所关注的流量性能。无论怎么，都得在控制器和计算主"
"机上考虑使用专用的数据存储网络和专用的接口。"
msgid ""
"When considering performance of OpenStack Object Storage, a number of design "
"choices will affect performance. A user’s access to the Object Storage is "
"through the proxy services, which sit behind hardware load balancers. By the "
"very nature of a highly resilient storage system, replication of the data "
"would affect performance of the overall system. In this case, 10 GbE (or "
"better) networking is recommended throughout the storage network "
"architecture."
msgstr ""
"当考虑OpenStack对象存储的性能时，有几样设计选择会影响到性能。用户访问对象存储"
"是通过代理服务，它通常是在硬件负载均衡之后。由于高弹性是此存储系统的天生特"
"性，所以复制数据将会影响到整个系统的性能。在此例中，存储网络使用10 GbE(或更"
"高)网络是我们所建议的。"
msgid ""
"When designing OpenStack Block Storage resource nodes, it is helpful to "
"understand the workloads and requirements that will drive the use of block "
"storage in the cloud. We recommend designing block storage pools so that "
"tenants can choose appropriate storage solutions for their applications. By "
"creating multiple storage pools of different types, in conjunction with "
"configuring an advanced storage scheduler for the block storage service, it "
"is possible to provide tenants with a large catalog of storage services with "
"a variety of performance levels and redundancy options."
msgstr ""
"当设计OpenStack块存储资源节点时，有助于理解负载和需求，即在云中使用块存储。由"
"于通用型云的使用模式经常是未知的。在>此建议设计块存储池做到租户可以根据他们的"
"应用来选择不同的存储。创建多个不同类型的存储池，得与块存储服务配置高级的存储"
"调度相结合，才可能为租户提供基于多种不同性能级别和冗余属性的大型目录存储服"
"务。"
msgid ""
"When designing hardware resources for OpenStack Object Storage, the primary "
"goal is to maximize the amount of storage in each resource node while also "
"ensuring that the cost per terabyte is kept to a minimum. This often "
"involves utilizing servers which can hold a large number of spinning disks. "
"Whether choosing to use 2U server form factors with directly attached "
"storage or an external chassis that holds a larger number of drives, the "
"main goal is to maximize the storage available in each node."
msgstr ""
"当为OpenStack对象存储设计硬件资源时，首要的目标就尽可能的为每个资源节点加上最"
"多的存储，当然也要在每TB的花费上保持最低。这往往涉及到了利用服务器的容纳大量"
"的磁盘。无论是选择使用2U服务器直接挂载磁盘，还是选择外挂大量的磁盘驱动，主要"
"的目标还是为每个节点得到最多的存储。"
msgid ""
"When determining capacity options be sure to take into account not just the "
"technical issues, but also the economic or operational issues that might "
"arise from specific decisions."
msgstr ""
"当决定容量要算计的不仅仅是技术问题，还要考虑经济和运营问题，这些都可能会带来"
"更多麻烦。"
msgid ""
"When selecting network devices, be aware that making this decision based on "
"the greatest port density often comes with a drawback. Aggregation switches "
"and routers have not all kept pace with Top of Rack switches and may induce "
"bottlenecks on north-south traffic. As a result, it may be possible for "
"massive amounts of downstream network utilization to impact upstream network "
"devices, impacting service to the cloud. Since OpenStack does not currently "
"provide a mechanism for traffic shaping or rate limiting, it is necessary to "
"implement these features at the network hardware level."
msgstr ""
"选择网络设备时，必须意识到基于最大的端口密度所做出的决定通常也有一个弊端。聚"
"合交换以及路由并不能完全满足柜顶交换机的需要，这可能引起南北向流量上的瓶颈。"
"其结果是，大量的下行网络使用可能影响上行网络设备，从而影响云中的服务。由于 "
"OpenStack 目前并未提供流量整形或者速度限制的机制，有必要在网络硬件的级别上实"
"现这些特性。"
msgid ""
"When using OpenStack Networking, the OpenStack controller servers or "
"separate Networking hosts handle routing. For a deployment that requires "
"features available in only Networking, it is possible to remove this "
"restriction by using third party software that helps maintain highly "
"available L3 routes. Doing so allows for common APIs to control network "
"hardware, or to provide complex multi-tier web applications in a secure "
"manner. It is also possible to completely remove routing from Networking, "
"and instead rely on hardware routing capabilities. In this case, the "
"switching infrastructure must support L3 routing."
msgstr ""
"另一方面，当使用OpenStack网络时，OpenStack控制器服务器或者是分离的网络主机掌"
"控路由。对于部署来说，需要在网络中满足此特性，有可能使用第三方软件来协助维护"
"高可用的3层路由。这么做允许通常的应用程序接口来控制网络硬件，或者基于安全的行"
"为提供复杂多层的web应用。从OpenStack网络中完全移除路由是可以的，取而代之的是"
"硬件的路由能力。在此情况下，交换基础设施必须支持3层路由。"
msgid ""
"Where instances and images will be stored will influence the architecture."
msgstr "实例和镜像存放在哪里会影响到架构。"
msgid ""
"Where many general purpose deployments use hardware load balancers to "
"provide highly available API access and SSL termination, software solutions, "
"for example HAProxy, can also be considered. It is vital to ensure that such "
"software implementations are also made highly available. High availability "
"can be achieved by using software such as Keepalived or Pacemaker with "
"Corosync. Pacemaker and Corosync can provide active-active or active-passive "
"highly available configuration depending on the specific service in the "
"OpenStack environment. Using this software can affect the design as it "
"assumes at least a 2-node controller infrastructure where one of those nodes "
"may be running certain services in standby mode."
msgstr ""
"多数的通用型部署使用硬件的负载均衡来提供API访问高可用和SSL终端，但是软件的解"
"决方案也要考虑到，比如HAProxy。至关重要的是软件实现的高可用也很靠谱。这些高可"
"用的软件Keepalived或基于Corosync的Pacemaker。Pacemaker和Corosync配合起来可以"
"提供双活或者单活的高可用配置，至于是否双活取决于OpenStack环境中特别的服务。使"
"用Pacemaker会影响到设计，假定有至少2台控制器基础设施，其中一个节点可在待机模"
"式下运行的某些服务。"
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 the implemented system meets those goals. 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 对象存储服务将特"
"定数量的数据副本作为对象存放与资源节点上。这些副本分布在整个集群之中，基于存"
"在于集群\n"
"中所有节点上的一致性哈希环。"
msgid ""
"While constructing a multi-site OpenStack environment is the goal of this "
"guide, the real test is whether an application can utilize it."
msgstr ""
"构建一个多区域OpenStack环境是本书的目的，但真正的考验来自于能否有一个应用能够"
"利用好。"
msgid ""
"While the cloud user can be completely unaware of the underlying "
"infrastructure of the cloud and its attributes, the operator must build and "
"support the infrastructure for operating at scale. This presents a very "
"demanding set of requirements for building such a cloud from the operator's "
"perspective:"
msgstr ""
"用户对于云的底层基础设施以及属性应该是完全不清楚的，然而，运营者却必须能够构"
"建并且支持该基础设施，也应该了解在大规模的情况下如何操作它。这从运营者的角度"
"提出了关于构建这样一个云的一系列相当强烈的需求："
msgid "Why and how we wrote this book"
msgstr "我们为什么及如何写作此书"
msgid "Workload characteristics"
msgstr "负载特性"
msgid ""
"Workload characteristics may also influence hardware choices and flavor "
"configuration, particularly where they present different ratios of CPU "
"versus RAM versus HDD requirements."
msgstr ""
"负载的特点常会影响到硬件的选择和实例类型的配置，尤其是他们有不同的CPU、内存、"
"硬盘的比例需求。"
msgid "Workload considerations"
msgstr "负载考虑"
msgid "XCP/XenServer"
msgstr "XCP/XenServer"
msgid ""
"You must weigh the dimensions against each other to determine the best "
"design for the desired purpose. For example, increasing server density can "
"mean sacrificing resource capacity or expandability. Increasing resource "
"capacity and expandability can increase cost but decrease server density. "
"Decreasing cost often means decreasing supportability, server density, "
"resource capacity, and expandability."
msgstr ""
"为达到期望的目的而决定最佳设计需要对一些因素作出取舍和平衡。举例来说，增加服"
"务器密度意味着牺牲资源的容量或扩展性。增加资源容量或扩展性又增加了开销但是降"
"低了服务器密度。减少开销又意味着减低支持力度，服务器密度，资源容量和扩展性。"
msgid ""
"You will need to consider how the OS and hypervisor combination interactions "
"with other operating systems and hypervisors, including other software "
"solutions. Operational troubleshooting tools for one OS-hypervisor "
"combination may differ from the tools used for another OS-hypervisor "
"combination and, as a result, the design will need to address if the two "
"sets of tools need to interoperate."
msgstr ""
"用户需要考虑此操作系统和Hypervisor组合和另外的操作系统和hypervisor怎么互动，"
"甚至包括和其它的软件。操作某一操作系统-hypervisor组合的故障排除工具，和操作其"
"他的操作系统-hypervisor组合也许根本就不一样，那结果就是，设计时就需要交付能够"
"使这两者工具集都能工作的工具。"
msgid "Zone per collection of nodes"
msgstr "Zone是多个节点的集合"
msgid "current"
msgstr "当前最新"
msgid "east-west traffic"
msgstr "东西向流量"
msgid "north-south traffic"
msgstr "南北向流量"
#. Put one translator per line, in the form of NAME <EMAIL>, YEAR1, YEAR2
msgid "translator-credits"
msgstr ""
"apporc watson <appleorchard2000@gmail.com>, 2015\n"
"Hunt Xu <mhuntxu@gmail.com>, 2015\n"
"johnwoo_lee <lijiangsheng1@gmail.com>, 2015\n"
"颜海峰 <yanheven@gmail.com>, 2015"
msgid "vSphere (vCenter and ESXi)"
msgstr "vSphere (vCenter and ESXi)"
View Git Blame Copy Permalink