Imported Translations from Transifex
For more information about this automatic import see: https://wiki.openstack.org/wiki/Translations/Infrastructure Change-Id: Id58094bab2714c477d59a90f37993e54df849925
This commit is contained in:
parent
51a56b8001
commit
d124b9e7f2
@ -1,7 +1,7 @@
|
||||
msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: PACKAGE VERSION\n"
|
||||
"POT-Creation-Date: 2015-01-22 06:14+0000\n"
|
||||
"POT-Creation-Date: 2015-01-27 06:11+0000\n"
|
||||
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
|
||||
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
|
||||
"Language-Team: LANGUAGE <LL@li.org>\n"
|
||||
@ -531,7 +531,7 @@ msgid "packages"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/ch_database.xml:210(para)
|
||||
msgid "If you want to put additional packages on the each guest that you create with this datastore version, you can list the package names here."
|
||||
msgid "If you want to put additional packages on each guest that you create with this datastore version, you can list the package names here."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/ch_database.xml:214(para)
|
||||
@ -1346,87 +1346,87 @@ msgstr ""
|
||||
msgid "For a list of flavors that are available on your system:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/ch_compute.xml:397(title)
|
||||
#: ./doc/admin-guide-cloud/ch_compute.xml:396(title)
|
||||
msgid "Compute service architecture"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/ch_compute.xml:398(para)
|
||||
#: ./doc/admin-guide-cloud/ch_compute.xml:397(para)
|
||||
msgid "These basic categories describe the service architecture and information about the cloud controller."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/ch_compute.xml:401(title)
|
||||
#: ./doc/admin-guide-cloud/ch_compute.xml:400(title)
|
||||
msgid "API server"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/ch_compute.xml:402(para)
|
||||
#: ./doc/admin-guide-cloud/ch_compute.xml:401(para)
|
||||
msgid "At the heart of the cloud framework is an API server, which makes command and control of the hypervisor, storage, and networking programmatically available to users."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/ch_compute.xml:405(para)
|
||||
#: ./doc/admin-guide-cloud/ch_compute.xml:404(para)
|
||||
msgid "The API endpoints are basic HTTP web services which handle authentication, authorization, and basic command and control functions using various API interfaces under the Amazon, Rackspace, and related models. This enables API compatibility with multiple existing tool sets created for interaction with offerings from other vendors. This broad compatibility prevents vendor lock-in."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/ch_compute.xml:416(title)
|
||||
#: ./doc/admin-guide-cloud/ch_compute.xml:415(title)
|
||||
msgid "Message queue"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/ch_compute.xml:417(para)
|
||||
#: ./doc/admin-guide-cloud/ch_compute.xml:416(para)
|
||||
msgid "A messaging queue brokers the interaction between compute nodes (processing), the networking controllers (software which controls network infrastructure), API endpoints, the scheduler (determines which physical hardware to allocate to a virtual resource), and similar components. Communication to and from the cloud controller is handled by HTTP requests through multiple API endpoints."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/ch_compute.xml:426(para)
|
||||
#: ./doc/admin-guide-cloud/ch_compute.xml:425(para)
|
||||
msgid "A typical message passing event begins with the API server receiving a request from a user. The API server authenticates the user and ensures that they are permitted to issue the subject command. The availability of objects implicated in the request is evaluated and, if available, the request is routed to the queuing engine for the relevant workers. Workers continually listen to the queue based on their role, and occasionally their type host name. When an applicable work request arrives on the queue, the worker takes assignment of the task and begins executing it. Upon completion, a response is dispatched to the queue which is received by the API server and relayed to the originating user. Database entries are queried, added, or removed as necessary during the process."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/ch_compute.xml:442(title)
|
||||
#: ./doc/admin-guide-cloud/ch_compute.xml:441(title)
|
||||
msgid "Compute worker"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/ch_compute.xml:443(para)
|
||||
#: ./doc/admin-guide-cloud/ch_compute.xml:442(para)
|
||||
msgid "Compute workers manage computing instances on host machines. The API dispatches commands to compute workers to complete these tasks:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/ch_compute.xml:448(para)
|
||||
#: ./doc/admin-guide-cloud/ch_compute.xml:447(para)
|
||||
msgid "Run instances"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/ch_compute.xml:451(para)
|
||||
#: ./doc/admin-guide-cloud/ch_compute.xml:450(para)
|
||||
msgid "Terminate instances"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/ch_compute.xml:454(para)
|
||||
#: ./doc/admin-guide-cloud/ch_compute.xml:453(para)
|
||||
msgid "Reboot instances"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/ch_compute.xml:457(para)
|
||||
#: ./doc/admin-guide-cloud/ch_compute.xml:456(para)
|
||||
msgid "Attach volumes"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/ch_compute.xml:460(para)
|
||||
#: ./doc/admin-guide-cloud/ch_compute.xml:459(para)
|
||||
msgid "Detach volumes"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/ch_compute.xml:463(para)
|
||||
#: ./doc/admin-guide-cloud/ch_compute.xml:462(para)
|
||||
msgid "Get console output"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/ch_compute.xml:468(title)
|
||||
#: ./doc/admin-guide-cloud/ch_compute.xml:467(title)
|
||||
msgid "Network Controller"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/ch_compute.xml:469(para)
|
||||
#: ./doc/admin-guide-cloud/ch_compute.xml:468(para)
|
||||
msgid "The Network Controller manages the networking resources on host machines. The API server dispatches commands through the message queue, which are subsequently processed by Network Controllers. Specific operations include:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/ch_compute.xml:476(para)
|
||||
#: ./doc/admin-guide-cloud/ch_compute.xml:475(para)
|
||||
msgid "Allocate fixed IP addresses"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/ch_compute.xml:479(para)
|
||||
#: ./doc/admin-guide-cloud/ch_compute.xml:478(para)
|
||||
msgid "Configuring VLANs for projects"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/ch_compute.xml:482(para)
|
||||
#: ./doc/admin-guide-cloud/ch_compute.xml:481(para)
|
||||
msgid "Configuring networks for compute nodes"
|
||||
msgstr ""
|
||||
|
||||
|
@ -8,8 +8,8 @@
|
||||
msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: OpenStack Manuals\n"
|
||||
"POT-Creation-Date: 2015-01-25 10:36+0000\n"
|
||||
"PO-Revision-Date: 2015-01-25 14:31+0000\n"
|
||||
"POT-Creation-Date: 2015-01-26 23:17+0000\n"
|
||||
"PO-Revision-Date: 2015-01-27 03:40+0000\n"
|
||||
"Last-Translator: johnwoo_lee <lijiangsheng1@gmail.com>\n"
|
||||
"Language-Team: Chinese (China) (http://www.transifex.com/projects/p/openstack-manuals-i18n/language/zh_CN/)\n"
|
||||
"MIME-Version: 1.0\n"
|
||||
@ -1457,7 +1457,7 @@ msgstr ""
|
||||
|
||||
#: ./doc/arch-design/multi_site/section_user_requirements_multi_site.xml72(title)
|
||||
msgid "Consistency of images and templates across different sites"
|
||||
msgstr ""
|
||||
msgstr "镜像和模板在跨不同站点时要保持一致性。"
|
||||
|
||||
#: ./doc/arch-design/multi_site/section_user_requirements_multi_site.xml74(para)
|
||||
msgid ""
|
||||
@ -2073,7 +2073,7 @@ msgstr ""
|
||||
#: ./doc/arch-design/compute_focus/section_tech_considerations_compute_focus.xml215(title)
|
||||
#: ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml230(title)
|
||||
msgid "Utilization"
|
||||
msgstr ""
|
||||
msgstr "量力而行"
|
||||
|
||||
#: ./doc/arch-design/multi_site/section_tech_considerations_multi_site.xml80(para)
|
||||
msgid ""
|
||||
@ -6729,7 +6729,7 @@ msgid ""
|
||||
"expected that extra supporting services are also deployed, such as shared "
|
||||
"storage attached to hosts to aid in recovery and resiliency of services in "
|
||||
"order to meet strict SLAs."
|
||||
msgstr ""
|
||||
msgstr "设计一个计算型云时,是可以接受实例没有从一台主机迁移到另外主机的能力的。因为应用程序的开发者们希望能够在应用程序内部掌控失效状况。相反的,一个计算型云应根据业务需求部署可提供外加的弹性,在此场景下,希望外加的支撑服务已经部署,诸如给主机挂接共享存储以提供紧急恢复和弹性服务,来满足服务水平协议。"
|
||||
|
||||
#: ./doc/arch-design/compute_focus/section_operational_considerations_compute_focus.xml90(para)
|
||||
msgid ""
|
||||
@ -6743,7 +6743,7 @@ msgid ""
|
||||
" effect on network and other data center resources, so factor in this "
|
||||
"increase when reaching rack capacity or when extra network switches are "
|
||||
"required."
|
||||
msgstr ""
|
||||
msgstr "为OpenStack云增加额外的容量是很轻松横向扩展的过程,像其它配置好的节点一样会自动挂接到OpenStack云。请记住,尽管如此,但也请在必要的时候才去增加节点到合适的可用域和主机聚合。在增加额外的节点到现有的环境中时,我们建议尽可能的使用相同(或类似)的CPU型号的主机,否则原来支持的在线迁移就可能失效。横向扩展hypervisor主机也会直接影响到网络和其它数据中心的资源,所以得考虑这种增长,例如当达到机架容量上限或需要额外的网络交换机时。"
|
||||
|
||||
#: ./doc/arch-design/compute_focus/section_operational_considerations_compute_focus.xml102(para)
|
||||
msgid ""
|
||||
@ -6753,7 +6753,7 @@ msgid ""
|
||||
"add extra needed capacity depending on whether the running applications are "
|
||||
"more CPU intensive or memory based (as would be expected in a compute-"
|
||||
"focused OpenStack cloud)."
|
||||
msgstr ""
|
||||
msgstr "计算主机有时也需要根据需求来增加内部组件,这一过程通常叫做纵向扩展。换一个更多核的CPU,或者给服务器增加内存,可以帮助增加额外需要的容量,当然具体得看所运行的应用程序是需要多少CPU和内存(正如计算型云所期望的)。"
|
||||
|
||||
#: ./doc/arch-design/compute_focus/section_operational_considerations_compute_focus.xml109(para)
|
||||
msgid ""
|
||||
@ -6766,7 +6766,7 @@ msgid ""
|
||||
"when a compute host fails. In a compute-focused OpenStack design "
|
||||
"architecture, increasing the CPU overcommit ratio increases the potential "
|
||||
"for noisy neighbor issues and is not recommended."
|
||||
msgstr ""
|
||||
msgstr "另外一个属性是评估平均负载和增加运行在计算环境中的实例数量,即通过调整超分配比例。但这仅适合于某些环境,更改CPU超分配比例会带来负面影响而且会增加影响到其他组件的风险,记住这点很重要。增加超分配比例带来的风险有,当一个计算主机宕机会引发除其本机运行的实例之外更多的实例会失效。在计算型OpenStack设计架构中,增加CPU超分配比例会增加破坏系统的风险,这是我们不建议的。"
|
||||
|
||||
#: ./doc/arch-design/compute_focus/section_user_requirements_compute_focus.xml13(para)
|
||||
msgid ""
|
||||
@ -6897,7 +6897,7 @@ msgid ""
|
||||
"storage intensive, nor are they consistently network intensive. The network "
|
||||
"and storage may be heavily utilized while loading a data set into the "
|
||||
"computational cluster, but they are not otherwise intensive."
|
||||
msgstr ""
|
||||
msgstr "对于计算型OpenStack云的硬件选择来说,必须能够响应计算密集的负载。计算型的定义就是对处理器和内存资源的极限需求。计算型OpenStack架构设计的硬件选择必须能够体现出处理计算密集的负载能力,要知道它不是存储密集也不是重型的网络负载。也许在载入数据到计算集群时会对网络和存储产生很重的负载,但是这不能当作存储型或网络型,它们有另外的考虑。"
|
||||
|
||||
#: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml30(para)
|
||||
#: ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml156(para)
|
||||
@ -6914,7 +6914,7 @@ msgid ""
|
||||
"capacity and expandability can increase cost but decreases server density. "
|
||||
"Decreasing cost can mean decreasing supportability, server density, resource"
|
||||
" capacity, and expandability."
|
||||
msgstr ""
|
||||
msgstr "为达到期望的目的而决定最佳设计需要对一些因素作出取舍和平衡。举例来说,增加服务器密度意味着牺牲资源的容量或扩展性。增加资源容量或扩展性又增加了开销但是降低了服务器密度。减少开销又意味着减低支持力度,服务器密度,资源容量和扩展性。"
|
||||
|
||||
#: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml68(para)
|
||||
msgid ""
|
||||
@ -6924,7 +6924,7 @@ msgid ""
|
||||
"hardware will need to be configured to provide enough network connectivity "
|
||||
"and storage capacity to meet minimum user requirements, but they are not the"
|
||||
" primary consideration."
|
||||
msgstr ""
|
||||
msgstr "为一个计算型云选择硬件,重点要看服务器硬件是否可以提供更多的CPU插槽,更多的CPU核的数量,以及更多的内存,至于网络连接和存储容量就显得次要一些。硬件需要的配置以提供足够的网络连接和存储容量满足用户的最低需求即可,但是这不是主要需要考虑的。"
|
||||
|
||||
#: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml74(para)
|
||||
msgid ""
|
||||
@ -6941,7 +6941,7 @@ msgid ""
|
||||
" to 16 servers in only 10 rack units using half-height blades, suddenly "
|
||||
"decreases the density by 50% by selecting full-height blades resulting in "
|
||||
"only 8 servers per 10 rack units."
|
||||
msgstr ""
|
||||
msgstr "大多数的刀片服务器都支持双插槽、多核的CPU的。要避免去选择“全宽”或“全高”的刀片,它们会损失服务器密度。举个例子,使用高密度的刀片服务器,如HP BladeSystem和Dell PowerEgde M1000e),它们都使用半高的刀片,可支持16台服务器,且仅占用10个机柜单元,它相比于全高的刀片有效的减低了50%的密度,因为全高的刀片在每10个机柜单元仅可以放置8台服务器。"
|
||||
|
||||
#: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml88(para)
|
||||
msgid ""
|
||||
@ -6989,7 +6989,7 @@ msgstr ""
|
||||
msgid ""
|
||||
"The following facts will strongly influence server hardware selection for a "
|
||||
"compute-focused OpenStack design architecture:"
|
||||
msgstr ""
|
||||
msgstr "下列因素会严重影响到计算型OpenStack架构设计的服务器硬件选择:"
|
||||
|
||||
#: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml131(para)
|
||||
msgid ""
|
||||
@ -7249,7 +7249,7 @@ msgid ""
|
||||
" the chosen operating system and hypervisor combination. For example, if the"
|
||||
" design uses Link Aggregation Control Protocol (LACP), the hypervisor needs "
|
||||
"to support it."
|
||||
msgstr ""
|
||||
msgstr "操作系统(OS)和hypervisor对于整个设计有着深刻的影响。选择一个特定的操作系统和hypervisor能够直接影响到服务器硬件的选择。确保存储硬件和拓扑支持选择好的操作系统和Hypervisor组合。也得确保网络硬件的选择和拓扑可在选定的操作系统和Hypervisor组合下正常工作。例如,如果设计中使用了链路聚合控制协议(LACP)的话,操作系统和hypervisor都需要支持它才可正常工作。"
|
||||
|
||||
#: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml398(para)
|
||||
msgid ""
|
||||
@ -7268,7 +7268,7 @@ msgid ""
|
||||
"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 ""
|
||||
msgstr "取决于所选择的hypervisor,运维人员需要经过适当的培训和掌握相关的知识才能支持所选择的操作系统和Hypervisor组合。如果运维人员没有经过培训以及相关知识的话,那么就需要提供给他们培训,这在设计中是需要额外的开销的。"
|
||||
|
||||
#: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml432(para)
|
||||
msgid ""
|
||||
@ -7403,14 +7403,14 @@ msgid ""
|
||||
"components will 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 ""
|
||||
msgstr "对于计算型OpenStack云来说,OpenStack基础设施组件需要高可用。如果在设计中没有考虑硬件的负载均衡,那么就得考虑网络软件包,如HAProxy。"
|
||||
|
||||
#: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml552(para)
|
||||
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 ""
|
||||
msgstr "所选择的支撑软件解决方案会影响到整个OpenStack云的设计,它们包括能够提供集群、日志、监测以及预警的软件。"
|
||||
|
||||
#: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml555(para)
|
||||
msgid ""
|
||||
@ -7422,7 +7422,7 @@ msgid ""
|
||||
"OpenStack High Availability Guide provides more details on the installation "
|
||||
"and configuration of Corosync and Pacemaker, should these packages need to "
|
||||
"be included in the design."
|
||||
msgstr ""
|
||||
msgstr "在集群软件中如 Corosync和Pacemaker在可用性需求中占主流。包含(不包含)这些软件包是主要决定的,要使云基础设施具有高可用的话,当然在部署之后会带来复杂的配置。OpenStack 高可用指南 提供了更加详细的安装和配置Corosync和Pacemaker,所以在设计中这些软件包需要被包含。"
|
||||
|
||||
#: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml563(para)
|
||||
msgid ""
|
||||
@ -7444,7 +7444,7 @@ msgid ""
|
||||
"for the additional resource consumption (CPU, RAM, storage, and network "
|
||||
"bandwidth for a log aggregation solution, for example). Some other potential"
|
||||
" design impacts include:"
|
||||
msgstr ""
|
||||
msgstr "如果任何这些软件包被需要,那么设计就可以当作额外的资源计入用的到它们的(举例,为日志聚合解决方案所需要的CPU,内存,存储以及网络带宽)。其它一些潜在影响设计的有:"
|
||||
|
||||
#: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml590(para)
|
||||
msgid ""
|
||||
@ -7459,7 +7459,7 @@ msgid ""
|
||||
"available using an available technology which can accomplish that goal. Some"
|
||||
" of the more common software solutions used include Galera, MariaDB and "
|
||||
"MySQL with multi-master replication."
|
||||
msgstr ""
|
||||
msgstr "大部分的OpenStack组件都需要访问后端的数据库服务,以存放状态和配置信息。选择一个合适的后端数据库可以满足可用性和容错是OpenStack服务所必须的。OpenStack服务支持连接由SQLAlchemy所支持的任何数据库,尽管如此,绝大多数的数据库部署还是使用MySQL或其变种。我们建议提供后端服务的数据库做到高可用,使用一些可用的技术手段,多数使用的软件解决方案是使用包括Galera,MariaDB以及多主节点复制的MySQL。"
|
||||
|
||||
#. When image changes, this message will be marked fuzzy or untranslated for
|
||||
#. you.
|
||||
@ -7616,7 +7616,7 @@ msgid ""
|
||||
" having instant access to new resources as they are required. Consequently, "
|
||||
"this means planning should be delivered for typical usage, but also more "
|
||||
"importantly, for sudden bursts in usage."
|
||||
msgstr ""
|
||||
msgstr "当规划扩展云的计算服务时面临一个关键的挑战,那就是云基础设施要求的弹性。在过去,新的用户或客户被强制计划,而且必须提前提出对基础设施的需求,然后进入采购流程。云计算时代的用户,按照他们所需要的,及时的获得资源。所以,这也意味着规划只能交付典型常规的使用,但是更为重要的是,能够经受的住突然来临的突破性的使用。"
|
||||
|
||||
#: ./doc/arch-design/compute_focus/section_tech_considerations_compute_focus.xml116(para)
|
||||
msgid ""
|
||||
@ -7625,7 +7625,7 @@ msgid ""
|
||||
"dissatisfied users. Planning for cloud expansion too aggressively can lead "
|
||||
"to unexpected underutilization of the cloud and funds spent on operating "
|
||||
"infrastructure that is not being used efficiently."
|
||||
msgstr ""
|
||||
msgstr "扩展规划是一个颇为微妙的平衡行为。规划过于保守会导致想不到的超额认购,还会导致用户很不满。规划过去激进又会导致没有有效利用云,以及资金花在了一个未被有效使用的运营基础设施上。"
|
||||
|
||||
#: ./doc/arch-design/compute_focus/section_tech_considerations_compute_focus.xml122(para)
|
||||
msgid ""
|
||||
@ -7634,7 +7634,7 @@ msgid ""
|
||||
"delivered, not the average speed or capacity of the cloud. Using this "
|
||||
"information to model performance results in capacity enables users to more "
|
||||
"accurately determine the current and future capacity of the cloud."
|
||||
msgstr ""
|
||||
msgstr "关键是认真的监测云运行时的使用量的高峰和低谷。目的是测量那些服务可以被无障碍的交付,并非什么平均速度或云的容量。基于此信息来模拟容量结果,确保用户更加准确的决定当前和未来的云的容量。"
|
||||
|
||||
#: ./doc/arch-design/compute_focus/section_tech_considerations_compute_focus.xml129(title)
|
||||
msgid "CPU and RAM"
|
||||
@ -7742,13 +7742,13 @@ msgstr "使用图形处理单元(GPU),可大大有益于高性能计算任务
|
||||
msgid ""
|
||||
"Cryptographic routines that benefit from the availability of hardware random"
|
||||
" number generators to avoid entropy starvation."
|
||||
msgstr ""
|
||||
msgstr "Cryptographic routines 受益于硬件随机数生成器,以避免entropy starvation。"
|
||||
|
||||
#: ./doc/arch-design/compute_focus/section_tech_considerations_compute_focus.xml202(para)
|
||||
msgid ""
|
||||
"Database management systems that benefit from the availability of SSDs for "
|
||||
"ephemeral storage to maximize read/write time when it is required."
|
||||
msgstr ""
|
||||
msgstr "给临时存储使用SSD硬盘,可大大有益于数据库管理系统,可加速其读写速度。"
|
||||
|
||||
#: ./doc/arch-design/compute_focus/section_tech_considerations_compute_focus.xml207(para)
|
||||
msgid ""
|
||||
@ -7758,7 +7758,7 @@ msgid ""
|
||||
" careful consideration must be given to whether all compute nodes, or just a"
|
||||
" subset which is targetable using flavors, need the additional customization"
|
||||
" to support the desired workloads."
|
||||
msgstr ""
|
||||
msgstr "主机聚合是用于一组共享相似特性的主机,其中包括硬件的相似性。在一个云部署中增加特殊的硬件,其实会给每个节点增加开销。所以仔细的考虑好是否给所有的硬件都增加,或者是为那些有需要的创建单独的flavor,使用这些flavor的实例运行在定制过的计算主机中。"
|
||||
|
||||
#: ./doc/arch-design/compute_focus/section_tech_considerations_compute_focus.xml216(para)
|
||||
msgid ""
|
||||
@ -7813,7 +7813,7 @@ msgid ""
|
||||
"The infrastructure of a cloud should not be shared, so that it is possible "
|
||||
"for the workloads to consume as many resources as are made available, and "
|
||||
"accommodations should be made to provide large scale workloads."
|
||||
msgstr ""
|
||||
msgstr "云的基础设施不应该被共享,因为有可能发生资源不足的情形,所以要保证资源的可用并能用于负载,而且备用于提供有朝一日的大规模扩展。"
|
||||
|
||||
#: ./doc/arch-design/compute_focus/section_tech_considerations_compute_focus.xml262(para)
|
||||
msgid ""
|
||||
@ -7821,7 +7821,7 @@ msgid ""
|
||||
"that are launched. Time limits range from seconds, minutes to hours, and as "
|
||||
"a result it is considered difficult to predict when resources will be used, "
|
||||
"for how long, and even which resources will be used."
|
||||
msgstr ""
|
||||
msgstr "批处理的持续时间取决于启动的分离任务。时间限制区间可以是秒,可以是分钟,也可以是小时,这样的结果就是增加了考虑的难度,比如预测什么时候资源会被使用?使用多久?那些资源会被用到?"
|
||||
|
||||
#: ./doc/arch-design/compute_focus/section_tech_considerations_compute_focus.xml269(para)
|
||||
msgid ""
|
||||
@ -7917,7 +7917,7 @@ msgid ""
|
||||
"Due to the nature of the workloads that will be used in this scenario, a "
|
||||
"number of components will be highly beneficial in a Compute-focused cloud. "
|
||||
"This includes the typical OpenStack components:"
|
||||
msgstr ""
|
||||
msgstr "由于在计算型云场景中使用的负载的性质,很多组件都会用的到。下面是典型的OpenStack组件:"
|
||||
|
||||
#: ./doc/arch-design/compute_focus/section_tech_considerations_compute_focus.xml367(para)
|
||||
msgid "OpenStack Compute (nova)"
|
||||
@ -11508,7 +11508,7 @@ msgstr ""
|
||||
msgid ""
|
||||
"OS-Hypervisor combination: Ensure that the selected logging, monitoring, or "
|
||||
"alerting tools support the proposed OS-hypervisor combination."
|
||||
msgstr ""
|
||||
msgstr "操作系统-Hypervisor组合:确保所选择的日志系统,监测系统,或预警工具都是被此组合所支持的。"
|
||||
|
||||
#: ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml632(para)
|
||||
msgid ""
|
||||
@ -11523,7 +11523,7 @@ msgid ""
|
||||
"MySQL is generally considered to be the de facto database for OpenStack, "
|
||||
"however, other compatible databases are also known to work. Note, however, "
|
||||
"that Telemetry uses MongoDB."
|
||||
msgstr ""
|
||||
msgstr "MySQL是OpenStack通常考虑的后端数据库,其它和MySQL兼容的数据也同样可以很好的工作。记住,Telemetry使用的是MongoDB。"
|
||||
|
||||
#: ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml641(para)
|
||||
msgid ""
|
||||
|
@ -1,7 +1,7 @@
|
||||
msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: PACKAGE VERSION\n"
|
||||
"POT-Creation-Date: 2015-01-21 06:13+0000\n"
|
||||
"POT-Creation-Date: 2015-01-27 06:11+0000\n"
|
||||
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
|
||||
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
|
||||
"Language-Team: LANGUAGE <LL@li.org>\n"
|
||||
@ -1647,7 +1647,7 @@ msgid "A deployment allows input values to be specified which map to the inputs
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/hot-reference/generated/openstack.xml:3044(para)
|
||||
msgid "Whenever this resource goes to an IN_PROGRESS state, it creates an ephemeral config that includes the inputs values plus a number of extra inputs which have names prefixed with deploy_. The extra inputs relate to the current state of the stack, along with the information and credentials required to signal back the deployment results."
|
||||
msgid "Whenever this resource goes to an IN_PROGRESS state, it creates an ephemeral config that includes the input values plus a number of extra inputs which have names prefixed with deploy_. The extra inputs relate to the current state of the stack, along with the information and credentials required to signal back the deployment results."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/hot-reference/generated/openstack.xml:3049(para)
|
||||
|
@ -7,8 +7,8 @@
|
||||
msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: OpenStack Manuals\n"
|
||||
"POT-Creation-Date: 2015-01-20 04:54+0000\n"
|
||||
"PO-Revision-Date: 2015-01-19 19:54+0000\n"
|
||||
"POT-Creation-Date: 2015-01-26 23:18+0000\n"
|
||||
"PO-Revision-Date: 2015-01-26 21:39+0000\n"
|
||||
"Last-Translator: openstackjenkins <jenkins@openstack.org>\n"
|
||||
"Language-Team: French (http://www.transifex.com/projects/p/openstack-manuals-i18n/language/fr/)\n"
|
||||
"MIME-Version: 1.0\n"
|
||||
@ -3149,12 +3149,12 @@ msgstr "Support Xen Para-virtualisé dans le kernel (Hyperviseur Xen seulement)"
|
||||
#: ./doc/image-guide/ch_openstack_images.xml442(para)
|
||||
msgid ""
|
||||
"Prior to Linux kernel version 3.0, the mainline branch of the Linux kernel "
|
||||
"did not have support paravirtualized Xen virtual machine instances (what Xen"
|
||||
" calls DomU guests). If you are running the Xen hypervisor with "
|
||||
"did not have support for paravirtualized Xen virtual machine instances (what"
|
||||
" Xen calls DomU guests). If you are running the Xen hypervisor with "
|
||||
"paravirtualization, and you want to create an image for an older Linux "
|
||||
"distribution that has a pre 3.0 kernel, you must ensure that the image boots"
|
||||
" a kernel that has been compiled with Xen support."
|
||||
msgstr "Avant la version 3.0 du noyau Linux, la branche principale du kernel Linux ne disposait pas de support para-virtualisé Xen pour les instances de machines virtuelles (ce que Xen appelle des invités DomU). Si vous utilisez l'hyperviseur Xen avec la para-virtualisation, et que vous souhaitez créer une image pour une distribution de Linux plus ancienne ayant un kernel en-dessous de 3.0, vous devez vous assurer que l'image démarre un kernel qui a été compilé avec le support Xen."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/image-guide/ch_openstack_images.xml452(title)
|
||||
msgid "Manage the image cache"
|
||||
|
@ -1,7 +1,7 @@
|
||||
msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: PACKAGE VERSION\n"
|
||||
"POT-Creation-Date: 2015-01-20 06:13+0000\n"
|
||||
"POT-Creation-Date: 2015-01-27 06:11+0000\n"
|
||||
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
|
||||
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
|
||||
"Language-Team: LANGUAGE <LL@li.org>\n"
|
||||
@ -2110,7 +2110,7 @@ msgid "Paravirtualized Xen support in the kernel (Xen hypervisor only)"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/image-guide/ch_openstack_images.xml:442(para)
|
||||
msgid "Prior to Linux kernel version 3.0, the mainline branch of the Linux kernel did not have support paravirtualized Xen virtual machine instances (what Xen calls DomU guests). If you are running the Xen hypervisor with paravirtualization, and you want to create an image for an older Linux distribution that has a pre 3.0 kernel, you must ensure that the image boots a kernel that has been compiled with Xen support."
|
||||
msgid "Prior to Linux kernel version 3.0, the mainline branch of the Linux kernel did not have support for paravirtualized Xen virtual machine instances (what Xen calls DomU guests). If you are running the Xen hypervisor with paravirtualization, and you want to create an image for an older Linux distribution that has a pre 3.0 kernel, you must ensure that the image boots a kernel that has been compiled with Xen support."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/image-guide/ch_openstack_images.xml:452(title)
|
||||
|
@ -6,8 +6,8 @@
|
||||
msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: OpenStack Manuals\n"
|
||||
"POT-Creation-Date: 2015-01-20 04:54+0000\n"
|
||||
"PO-Revision-Date: 2015-01-19 19:54+0000\n"
|
||||
"POT-Creation-Date: 2015-01-26 23:18+0000\n"
|
||||
"PO-Revision-Date: 2015-01-26 21:39+0000\n"
|
||||
"Last-Translator: openstackjenkins <jenkins@openstack.org>\n"
|
||||
"Language-Team: Japanese (http://www.transifex.com/projects/p/openstack-manuals-i18n/language/ja/)\n"
|
||||
"MIME-Version: 1.0\n"
|
||||
@ -3148,12 +3148,12 @@ msgstr "カーネルの準仮想化 Xen サポート (Xen ハイパーバイザ
|
||||
#: ./doc/image-guide/ch_openstack_images.xml442(para)
|
||||
msgid ""
|
||||
"Prior to Linux kernel version 3.0, the mainline branch of the Linux kernel "
|
||||
"did not have support paravirtualized Xen virtual machine instances (what Xen"
|
||||
" calls DomU guests). If you are running the Xen hypervisor with "
|
||||
"did not have support for paravirtualized Xen virtual machine instances (what"
|
||||
" Xen calls DomU guests). If you are running the Xen hypervisor with "
|
||||
"paravirtualization, and you want to create an image for an older Linux "
|
||||
"distribution that has a pre 3.0 kernel, you must ensure that the image boots"
|
||||
" a kernel that has been compiled with Xen support."
|
||||
msgstr "Linux カーネルバージョン 3.0 以前は、メインラインのブランチが準仮想化 Xen 仮想マシンインスタンス (Xen が DomU ゲストを呼び出します) をサポートしません。準仮想化で Xen を動かしていて、カーネル 3.0 以前の古い Linux イメージを作成したい場合、カーネルが Xen サポートありでコンパイルされていることを確認する必要があります。"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/image-guide/ch_openstack_images.xml452(title)
|
||||
msgid "Manage the image cache"
|
||||
|
3465
doc/image-guide/locale/zh_CN.po
Normal file
3465
doc/image-guide/locale/zh_CN.po
Normal file
File diff suppressed because it is too large
Load Diff
Loading…
x
Reference in New Issue
Block a user