Imported Translations from Transifex

For more information about this automatic import see: https://wiki.openstack.org/wiki/Translations/Infrastructure Change-Id: I7859a0d51e027d7f09b5b52764ff42fe8fc8a6cc
2015-01-29 06:30:37 +00:00 · 2015-01-29 06:30:37 +00:00 · 1449867b84
commit 1449867b84
parent 6ef5c48af0
7 changed files with 66 additions and 66 deletions
--- a/doc/arch-design/locale/zh_CN.po
+++ b/doc/arch-design/locale/zh_CN.po
@ -8,8 +8,8 @@
 msgid ""
 msgstr ""
 "Project-Id-Version: OpenStack Manuals\n"
-"POT-Creation-Date: 2015-01-27 14:07+0000\n"
-"PO-Revision-Date: 2015-01-28 04:21+0000\n"
+"POT-Creation-Date: 2015-01-28 21:14+0000\n"
+"PO-Revision-Date: 2015-01-29 03:36+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"
@ -6964,7 +6964,7 @@ 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 ""
+msgstr "2U机架式服务器提供四插槽、多核CPU的支持，但是它相应的降低了服务器密度(相当于1U机架式服务器的一半)。"

 #: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml108(para)
 msgid ""
@ -6972,7 +6972,7 @@ msgid ""
 "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 ""
+msgstr "大型机架式服务器，比如4U服务器，可提供更为强大的CPU容量。通常支持4个甚至8个CPU插槽。拥有很强的扩展性，但是这些服务器会带来低密度，以及更加昂贵的开销。"

 #: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml115(para)
 msgid ""
@ -6983,7 +6983,7 @@ msgid ""
 "sockets in 2U. However, the dual-socket limitation on individual nodes may "
 "not be sufficient to offset their additional cost and configuration "
 "complexity."
-msgstr ""
+msgstr "“雪撬服务器”(支持在单个2U或3U的空间放置多个独立的服务器)增加的密度超过典型的1U-2U机架服务器，举例来说，很多雪撬服务器提供在2U的空间置放4个独立的双插槽CPU,即2U服务器拥有8颗CPU，尽管如此，分离节点的双插槽限制不足以抵消它们额外带来的开销和配置的复杂性。"

 #: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml124(para)
 msgid ""
@ -6997,7 +6997,7 @@ msgid ""
 " RAM over-subscription ratios are also lower. More hosts will be required to"
 " support the anticipated scale due to instance density being lower, "
 "especially if the design uses dual-socket hardware designs."
-msgstr ""
+msgstr "在此架构中实例密度要被考虑为低，因此CPU和内存的超额认购比例也要低。为了支持实例低密度的预期扩展需要更多的主机，尤其是设计中使用了双插槽的硬件。"

 #: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml141(para)
 msgid ""
@ -7006,7 +7006,7 @@ msgid ""
 "will decrease host density, which increases rack count. This configuration "
 "may affect the network requirements, the number of power connections, and "
 "possibly impact the cooling requirements."
-msgstr ""
+msgstr "解决高主机计数的另外的办法是使用四路平台。这样的话降低了主机密度，也增加了机架数，这样的配置会影响到网络需求，电源连接数量，还有可能影响的制冷需求。"

 #: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml150(term)
 #: ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml295(term)
@ -7019,7 +7019,7 @@ msgid ""
 "sled, or 1U server designs because of lower host density (by using 2U, 3U or"
 " even 4U server designs). For data centers with older infrastructure, this "
 "may be a desirable feature."
-msgstr ""
+msgstr "电力和制冷的密度需求要低于刀片、雪撬或1U服务器，因为(使用2U,3U甚至4U服务器)拥有更低的主机密度。对于数据中心内有旧的基础设施，这是非常有用的特性。"

 #: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml160(para)
 msgid ""
@ -7056,7 +7056,7 @@ msgid ""
 "compute-intensive workloads, minimizing the delays that the CPU experiences "
 "while fetching data from the storage can have a significant impact on the "
 "overall performance of the application."
-msgstr ""
+msgstr "性能的解决方案也是一重量级的角色，可以通过存储I-O的延迟需求来测量。在计算型OpenStack云，存储延迟是个主要考虑的对象。在一些计算密集型负载中，从存储中获取数据时的最小延迟CPU都会影响到应用的整个性能。"

 #: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml196(para)
 msgid ""
@ -7066,7 +7066,7 @@ msgid ""
 "degrading performance as it expands would not be considered scalable. On the"
 " other hand, a solution that continues to perform well at maximum expansion "
 "would be considered scalable."
-msgstr ""
+msgstr "此节参考术语\"扩展性“，来解释存储解决方案的表现可扩展到最大规模是怎么个好法。一个存储解决方案在小型配置时表现良好，但是在规模扩展的过程中性能降低，这就不是好的扩展性，也不会被考虑。换句话说，一个解决方案只有在规模扩展最大性能没有任何的降低才是好的扩展性。"

 #: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml208(para)
 msgid ""
@ -7075,7 +7075,7 @@ msgid ""
 "solution that only scales to 10PB. Note that this metric is related to, but "
 "different from, scalability, which is a measure of the solution's "
 "performance as it expands."
-msgstr ""
+msgstr "规模扩展性是指在整个解决方案的扩张的整体能力。一个存储解决方案可以扩展到50PB，一定比仅能扩展到10PB的规模扩展性强，也会更加倾向于前者。记住一点，规模扩展性和通常所说的扩展性有关系，但是不一样，扩展性更加强调的是在规模扩展的过程中表现出来的性能衡量。"

 #: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml217(para)
 msgid ""
@ -7084,7 +7084,7 @@ msgid ""
 "instance storage and reduce CPU delays caused by waiting for the storage "
 "will increase performance. Consider using RAID controller cards in compute "
 "hosts to improve the performance of the underlying disk subsystem."
-msgstr ""
+msgstr "对于计算型OpenStack云来说，存储的延迟是主要应该考虑的。使用固态硬盘(SSD)以使实例存储延迟最小以及减少由于等待存储产生的CPU延迟，可大大提升性能。考虑让计算主机的磁盘子系统使用RAID控制卡对改善性能也大有帮助。"

 #: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml223(para)
 msgid ""
@ -7101,7 +7101,7 @@ msgid ""
 "direct-attached storage (DAS) in the servers may be an appropriate choice. "
 "If so, then the server hardware needs to be configured to support the "
 "storage solution."
-msgstr ""
+msgstr "存储架构的选择，以及存储硬件的选择(如果可以的话)，上面列出的几个因素是相互有冲突的，需评估决定。如果是横向扩展解决方案的选择诸如(Ceph，GlusterFS，或类似的),如果是单一的，高扩展性的，那么选择中心化的存储阵列就没错。如果中心存储阵列能够满足需求，那么硬件的决定就是如何选择阵列供应商的事情了。使用商业硬件和开源软件来构建存储阵列也是完全可能的，只是需要构建这样的系统需要专业的人员罢了。反过来说，一个横向扩展的存储解决方案使用直接挂接存储(DAS)给服务器也许是个恰当的选择。如果是这样的话，服务器硬件就需要配置以支持此种存储解决方案。"

 #: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml237(para)
 msgid ""
@ -7118,7 +7118,7 @@ msgid ""
 " array. Connectivity could affect latency and thus performance, so check "
 "that the network characteristics will minimize latency to boost the overall "
 "performance of the design."
-msgstr ""
+msgstr "根据所选择的存储解决方案，要确保它的连接和存储解决方案的需求是匹配的。如果是选择了中心化的存储阵列，决定有多少台hypervisor会连接到此阵列中是很重要的。连接会影响到延迟以及它们的性能，所以监测网络因素以达到最小延迟，提升整体的性能。"

 #: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml254(term)
 #: ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml130(term)
@ -7142,7 +7142,7 @@ msgid ""
 "throughout is optimized. While it is not likely that a compute-focused cloud"
 " will have major data I-O to and from storage, this is an important factor "
 "to consider."
-msgstr ""
+msgstr "为了改善整体的性能，要确保存储解决方案是整个被优化过的。虽然从一个计算型云的角度讲不太可能有从存储过来的重型数据，考虑到这是一个重要的因素就够了。"

 #: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml270(term)
 msgid "Server Hardware"
@ -7153,7 +7153,7 @@ msgid ""
 "If the solution uses DAS, this impacts, and is not limited to, the server "
 "hardware choice that will ripple into host density, instance density, power "
 "density, OS-hypervisor, and management tools."
-msgstr ""
+msgstr "如果解决方案中使用了DAS，这会影响到但不限于，服务器硬件的选择会波及到主机密度、实例密度、电力密度、操作系统-hypervisor、以及管理工具。"

 #: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml279(para)
 msgid ""
@ -7161,7 +7161,7 @@ msgid ""
 " of migration between hosts, use of a shared storage file-system to store "
 "instance ephemeral data should be employed to ensure that compute services "
 "can run uninterrupted in the event of a node failure."
-msgstr ""
+msgstr "当实例有高可用的需求时，或者实例需要拥有在主机间迁移的能力，使用共享存储或共享文件系统存放实例历史数据，确保计算服务在节点宕机的情况下不会中断。"

 #: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml300(para)
 msgid ""
@ -7174,7 +7174,7 @@ msgid ""
 "that must also 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 ""
+msgstr "网络的设计会受到物理空间的影响，需要提供足够的端口数。一个占用1U机柜空间的可提供48个 10GbE端口的交换机，显而易见的要比占用2U机柜空间的仅提供24个 10GbE端口的交换机有着更高的端口密度。高端口密度是首先选择的，因为其可以为计算和存储省下机柜空间。这也会引起人们的思考，容错的情况呢？电力密度？高密度的交换机更加的昂贵，也应该被考虑使用，但是没有必要覆盖设计中所有的网络，要视实际情况而定。"

 #: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml315(para)
 msgid ""
@ -7190,7 +7190,7 @@ msgid ""
 "switches. If this is a requirement, the hardware will need to support this "
 "configuration. User requirements will determine if a completely redundant "
 "network infrastructure is required."
-msgstr ""
+msgstr "网络硬件冗余级别需求会被用户对高可用和开销的考虑所影响。网络冗余可以是增加双电力供应也可以是结对的交换机。如果这是必须的，那么对应的服务器硬件就需要配置以支持冗余的情况。用户的需求也是决定是否采用全冗余网络基础设施的关键。"

 #: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml335(para)
 msgid ""
@ -7198,7 +7198,7 @@ msgid ""
 "selected network hardware. This is not an issue for top of rack (ToR) "
 "switches, but may be an issue for spine switches in a leaf and spine fabric,"
 " or end of row (EoR) switches."
-msgstr ""
+msgstr "确保物理数据中心为所选择的网络硬件提供了必要的电力。对于机柜顶端型(ToR)交换机没有什么影响，但是spine交换机的叶和fabric以及排尾(EoR)交换机就可能发生问题，假如电力不足的话。"

 #: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml343(para)
 msgid ""
@ -7207,7 +7207,7 @@ msgid ""
 "architecture. Once these key considerations have been decided, the proper "
 "network can be designed to best serve the workloads being placed in the "
 "cloud."
-msgstr ""
+msgstr "首先了解附加因素和用户是非常重要的，因为这些附加因素会严重影响到云的网络架构。一旦这些关键因素已经决定，适当的网络可以被设计的更好，以满足云中的工作负载。"

 #: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml348(para)
 msgid ""
@ -7223,7 +7223,7 @@ msgid ""
 " cost, therefore we recommend to weigh the cost versus the benefit gained "
 "from utilizing and deploying redundant network switches and using bonded "
 "interfaces at the host level."
-msgstr ""
+msgstr "我们建议设计网络架构时使用扩展性网络模式，让增加容量和带宽变得更加容易。一个较好的例子是使用leaf-spline模式，在此类型网络设计中，它可轻松增加额外的带宽以及横向的扩展。选择网络硬件非常重要，是否能满足端口数的需求？端口速度？以及端口密度。评估网络架构是否值得提供冗余也很重要，毕竟增加网络的可用性和冗余是要花钱的，因此，我们建议用户作出取舍，一边是钱，另一边是部署冗余的网络交换机以及主机级别的网卡bond。"

 #: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml364(para)
 msgid ""
@ -7260,7 +7260,7 @@ msgid ""
 "impact on cost due to support contracts. On the other hand, business or "
 "application requirements might dictate a specific or commercially supported "
 "hypervisor."
-msgstr ""
+msgstr "选择商业支持的hypervisor如微软的Hyper-V，和选择社区支持的开源hypervisor如kinstance或Xen，在开销模式上是完全不同的。甚至在开源解决方案也表现不同，如选择Ubuntu而不是RedHat(或类似)在支持上有着不同的开销。换句话说，业务和应用的需求主宰着选用特殊的或商业支持的hypervisor。"

 #: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml411(para)
 msgid ""
@ -7276,7 +7276,7 @@ msgid ""
 "scale and performance requirements. The chosen architecture will need to "
 "meet the targeted instance-host ratios with the selected OS-hypervisor "
 "combination."
-msgstr ""
+msgstr "确保所选择的操作系统和hypervisor组合能够满足扩展和性能的需求。所选择的架构需要满足目标实例-主机的比例。"

 #: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml442(para)
 msgid ""
@ -7285,7 +7285,7 @@ msgid ""
 "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 ""
+msgstr "确保设计能够在维护负载需求时能够容纳正常的所安装的应用的安全补丁。为操作系统-hypervisor组合打安全补丁的频率会影响>到性能，而且补丁的安装流程也会影响到维护工作。"

 #: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml453(para)
 #: ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml485(para)
@ -7295,7 +7295,7 @@ msgid ""
 "available with specific OSs or hypervisors. For example, if certain features"
 " are not available, the design might need to be modified to meet the user "
 "requirements."
-msgstr ""
+msgstr "决定什么特性是OpenStack所需要的。这通常是由所选择的操作系统-hypervisor组合来决定的。一些特性仅在某些特定的操作系统或hypervisor中存在。例如，如果某个特性无法实现，设计就得更改，因为用户需求最大。"

 #: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml464(para)
 msgid ""
@ -7305,7 +7305,7 @@ msgid ""
 "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 ""
+msgstr "在整个设计中(若有必要)考虑此操作系统和Hypervisor组合和另外的操作系统和hypervisor怎么互动，甚至包括和其它的软件。操作某一操作系统-hypervisor组合的故障排除工具，和操作其他的操作系统-hypervisor组合也许根本就不一样，那结果就是，设计时就需要交付能够使这两者工具集都能工作的工具。\""

 #: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml478(para)
 msgid ""
@ -7318,7 +7318,7 @@ msgid ""
 "the architecture uses a replacement for OpenStack Object Storage for its "
 "storage component, this could potentially have significant impacts on the "
 "rest of the design."
-msgstr ""
+msgstr "在设计和部署中选择包含什么OpenStack组件是着显著的影响。有一些组件是必选的(例如计算和镜像服务)，还有一些组件是可选的，举例来说，一些设计中不需要Orchestration模块，忽略掉Heat组件对整个系统没啥影响。还有其他情况，如架构中使用的存储组件不是OpenStack 对象存储，这就会对设计中的其它组件有着很大的影响。"

 #: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml487(para)
 msgid ""
@ -7362,7 +7362,7 @@ msgid ""
 "onto instances running in a compute-focused cloud. However, there may be "
 "some situations where the need for performance dictates that a block storage"
 " component be used to improve data I-O."
-msgstr ""
+msgstr "OpenStack块存储可能不被纳入计算型设计中，由于持久性块存储并非在此类型负载中有显著的需求，此类型是指在计算型云中运行的实例。尽管如此，有一些情况需要突出性能的表现，那么块存储组件的使用也许可以改善数据I-O。"

 #: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml518(para)
 msgid ""
@ -7374,7 +7374,7 @@ msgid ""
 "use Orchestration to spin up a large number of instances to perform the "
 "compute-intensive processing, including Orchestration in a compute-focused "
 "architecture design is strongly recommended."
-msgstr ""
+msgstr "排除一些特定的OpenStack组件会让其他组件的功能受到限制。如果在一个设计中有Orchestration模块但是没有包括Telemetry模块，那么此设计就无法使用Orchestration带来自动伸缩功能的优点(Orchestration需要Telemetery提供监测数据)。用户使用Orchestration在计算密集型处理任务时可自动启动大量的实例，因此强烈建议在计算型架构设计中使用Orchestration。"

 #: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml530(para)
 msgid ""
@ -7382,7 +7382,7 @@ msgid ""
 "building a platform for cloud services, there are invariably additional "
 "pieces of software that might need to be added to any given OpenStack "
 "design."
-msgstr ""
+msgstr "话说OpenStack是一个为构建云服务平台的软件项目，完全公平的收集各类软件，所以有大家都在用的其它软件包，可以在给定的OpenStack设计中按需添加。"

 #: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml536(para)
 msgid ""
@ -7395,7 +7395,7 @@ msgid ""
 "(<link href=\"http://docs.openstack.org/high-availability-"
 "guide/content\">http://docs.openstack.org/high-availability-"
 "guide/content</link>)."
-msgstr ""
+msgstr "OpenStack网络为实例提供各种各样的网络服务。另外有许多网络软件包用于管理OpenStack组件自身。这里举一些例子，可提供负载均衡，网络冗余协议或路由守护进程，关于这些软件包更加详细的描述细节都在<citetitle>OpenStack 高可用指南</citetitle> (<link href=\"http://docs.openstack.org/high-availability-guide/content\">http://docs.openstack.org/high-availability-guide/content</link>)中找到。"

 #: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml545(para)
 msgid ""
@ -8081,7 +8081,7 @@ msgid ""
 "simplify the management of the center's compute resources with a view to "
 "doubling compute capacity through the addition of an additional data center "
 "in 2013 while maintaining the same levels of compute staff."
-msgstr ""
+msgstr "为了支持越来越多的相关大型强子对撞机(LHC)实验的计算重度使用者,CERN 最终选用了使用SCientific Linux和 RDO部署的OpenStack云。这些努力的目的是简化中心计算资源的管理，在2013年增加了额外的数据中心，计算能力增长了一倍，但是维护人员确依然是原有的水平。"

 #: ./doc/arch-design/compute_focus/section_prescriptive_examples_compute_focus.xml54(para)
 msgid ""
@ -11122,7 +11122,7 @@ msgstr ""
 msgid ""
 "Ensure that the storage solution throughput is optimized based on "
 "application requirements."
-msgstr ""
+msgstr "要确保存储解决方案是基于应用的需求整个被优化。"

 #: ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml147(para)
 msgid ""
@ -11225,7 +11225,7 @@ msgstr ""
 msgid ""
 "Other factors that will strongly influence server hardware selection for a "
 "storage-focused OpenStack design architecture:"
-msgstr ""
+msgstr "其它对于一个存储型OpenStack架构设计的服务器硬件选择有重大影响的因素有："

 #: ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml276(para)
 msgid ""
@ -11362,7 +11362,7 @@ msgid ""
 "combinations are supported by OpenStack, there will naturally be very "
 "different impacts to the rest of the design as a result of the selection of "
 "one combination versus the other."
-msgstr ""
+msgstr "Ubuntu和Kinstance的管理工具和VMware vSphere的管理工具是不一样的。尽管OpenStack对它们都支持。这也会对其他的设计有着非常不同的影响，结果就是选择了一种组合，然后再据此做出后面的选择。"

 #: ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml462(para)
 msgid ""
@ -11410,7 +11410,7 @@ 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 ""
+msgstr "一个存储型设计也许需要使用Orchestration，能够启动带块设备卷的实例，以满足存储密集型任务处理。"

 #: ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml526(para)
 msgid ""
--- a/doc/config-reference/locale/config-reference.pot
+++ b/doc/config-reference/locale/config-reference.pot
@ -1,7 +1,7 @@
 msgid ""
 msgstr ""
 "Project-Id-Version: PACKAGE VERSION\n"
-"POT-Creation-Date: 2015-01-20 06:12+0000\n"
+"POT-Creation-Date: 2015-01-29 06:29+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"
@ -8867,7 +8867,7 @@ msgid "OpenStack projects use AMQP, an open standard for messaging middleware. O
 msgstr ""

 #: ./doc/config-reference/compute/section_rpc.xml:17(para)
-msgid "OpenStack Oslo RPC uses <application>RabbitMQ</application> by default. Use these options to configure the <application>RabbitMQ</application> message system. The <literal>rpc_backend</literal> option is not required as long as <application>RabbitMQ</application> is the default messaging system. However, if it is included the configuration, you must set it to <literal>nova.openstack.common.rpc.impl_kombu</literal>."
+msgid "OpenStack Oslo RPC uses <application>RabbitMQ</application> by default. Use these options to configure the <application>RabbitMQ</application> message system. The <literal>rpc_backend</literal> option is not required as long as <application>RabbitMQ</application> is the default messaging system. However, if it is included the configuration, you must set it to <literal>rabbit</literal>."
 msgstr ""

 #: ./doc/config-reference/compute/section_rpc.xml:26(para)
--- a/doc/glossary/locale/ko_KR.po
+++ b/doc/glossary/locale/ko_KR.po
@ -8,8 +8,8 @@
 msgid ""
 msgstr ""
 "Project-Id-Version: OpenStack Manuals\n"
-"POT-Creation-Date: 2015-01-20 20:43+0000\n"
-"PO-Revision-Date: 2015-01-20 19:01+0000\n"
+"POT-Creation-Date: 2015-01-28 21:14+0000\n"
+"PO-Revision-Date: 2015-01-28 16:20+0000\n"
 "Last-Translator: Ian Y. Choi <ianyrchoi@gmail.com>\n"
 "Language-Team: Korean (Korea) (http://www.transifex.com/projects/p/openstack-manuals-i18n/language/ko_KR/)\n"
 "MIME-Version: 1.0\n"
@ -777,7 +777,7 @@ msgstr "인증 노드"

 #: ./doc/glossary/glossary-terms.xml785(para)
 msgid "An Object Storage node that provides authorization services."
-msgstr ""
+msgstr "인증 서비스를 제공하는 오브젝트 스토리지 노드"

 #: ./doc/glossary/glossary-terms.xml791(glossterm)
 #: ./doc/glossary/glossary-terms.xml793(primary)
@ -788,7 +788,7 @@ msgstr "AuthZ"
 msgid ""
 "The Identity Service component that provides high-level authorization "
 "services."
-msgstr ""
+msgstr "고수준 권한 부여 서비스를 제공하는 Identity 서비스"

 #: ./doc/glossary/glossary-terms.xml803(glossterm)
 #: ./doc/glossary/glossary-terms.xml805(primary)
@ -799,23 +799,23 @@ msgstr "자동 ACK"
 msgid ""
 "Configuration setting within RabbitMQ that enables or disables message "
 "acknowledgment. Enabled by default."
-msgstr ""
+msgstr "메시지를 수락할 것인지에 대해 활성화 또는 비활성화를 RabbitMQ 내에서 구성하며, 디폴트로 활성화됨"

 #: ./doc/glossary/glossary-terms.xml815(glossterm)
 #: ./doc/glossary/glossary-terms.xml817(primary)
 msgid "auto declare"
-msgstr ""
+msgstr "자동 선언"

 #: ./doc/glossary/glossary-terms.xml821(para)
 msgid ""
 "A Compute RabbitMQ setting that determines whether a message exchange is "
 "automatically created when the program starts."
-msgstr ""
+msgstr "컴퓨트 RabbitMQ 설정으로 메시지 교환이 프로그램 시작시 자동으로 생성되는지 결정"

 #: ./doc/glossary/glossary-terms.xml827(glossterm)
 #: ./doc/glossary/glossary-terms.xml829(primary)
 msgid "availability zone"
-msgstr "사용 가능한 존"
+msgstr "가용 존"

 #: ./doc/glossary/glossary-terms.xml833(para)
 msgid ""
@ -8100,7 +8100,7 @@ msgstr ""
 #: ./doc/glossary/glossary-terms.xml8863(glossterm)
 #: ./doc/glossary/glossary-terms.xml8865(primary)
 msgid "vSphere"
-msgstr ""
+msgstr "vSphere"

 #: ./doc/glossary/glossary-terms.xml8877(title)
 msgid "W"
--- a/doc/image-guide/locale/fr.po
+++ b/doc/image-guide/locale/fr.po
@ -7,8 +7,8 @@
 msgid ""
 msgstr ""
 "Project-Id-Version: OpenStack Manuals\n"
-"POT-Creation-Date: 2015-01-26 23:18+0000\n"
-"PO-Revision-Date: 2015-01-26 21:39+0000\n"
+"POT-Creation-Date: 2015-01-28 21:14+0000\n"
+"PO-Revision-Date: 2015-01-28 19:06+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"
@ -1764,10 +1764,10 @@ msgstr "Ecrire un script pour prendre la clé publique (si pas de cloud-init)"
 msgid ""
 "If you are not able to install the <systemitem class=\"service\">cloud-"
 "init</systemitem> package in your image, to fetch the ssh public key and add"
-" it to the root account, edit the <filename>/etc/rc.local</filename> file "
-"and add the following lines before the line <literal>touch "
+" it to the root account, edit the <filename>/etc/rc.d/rc.local</filename> "
+"file and add the following lines before the line <literal>touch "
 "/var/lock/subsys/local</literal>:"
-msgstr "Si vous n'êtes pas en mesure d'installer le package <systemitem class=\"service\">cloud-init</systemitem> dans votre image, pour prendre la clé publique et l'ajouter au compte root, éditez le fichier <filename>/etc/rc.local</filename> et ajoutez les lignes suivantes avant la ligne <literal>touch /var/lock/subsys/local</literal>:"
+msgstr ""

 #: ./doc/image-guide/section_centos-example.xml266(para)
 msgid ""
--- a/doc/image-guide/locale/image-guide.pot
+++ b/doc/image-guide/locale/image-guide.pot
@ -1,7 +1,7 @@
 msgid ""
 msgstr ""
 "Project-Id-Version: PACKAGE VERSION\n"
-"POT-Creation-Date: 2015-01-27 06:11+0000\n"
+"POT-Creation-Date: 2015-01-29 06:29+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"
@ -1202,7 +1202,7 @@ msgid "Write a script to fetch the public key (if no cloud-init)"
 msgstr ""

 #: ./doc/image-guide/section_centos-example.xml:238(para)
-msgid "If you are not able to install the <systemitem class=\"service\">cloud-init</systemitem> package in your image, to fetch the ssh public key and add it to the root account, edit the <filename>/etc/rc.local</filename> file and add the following lines before the line <literal>touch /var/lock/subsys/local</literal>:"
+msgid "If you are not able to install the <systemitem class=\"service\">cloud-init</systemitem> package in your image, to fetch the ssh public key and add it to the root account, edit the <filename>/etc/rc.d/rc.local</filename> file and add the following lines before the line <literal>touch /var/lock/subsys/local</literal>:"
 msgstr ""

 #: ./doc/image-guide/section_centos-example.xml:266(para)
--- a/doc/image-guide/locale/ja.po
+++ b/doc/image-guide/locale/ja.po
@ -6,8 +6,8 @@
 msgid ""
 msgstr ""
 "Project-Id-Version: OpenStack Manuals\n"
-"POT-Creation-Date: 2015-01-26 23:18+0000\n"
-"PO-Revision-Date: 2015-01-26 21:39+0000\n"
+"POT-Creation-Date: 2015-01-28 21:14+0000\n"
+"PO-Revision-Date: 2015-01-28 19:06+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"
@ -1763,10 +1763,10 @@ msgstr "公開鍵取得のスクリプトの書き込み (cloud-init なしの
 msgid ""
 "If you are not able to install the <systemitem class=\"service\">cloud-"
 "init</systemitem> package in your image, to fetch the ssh public key and add"
-" it to the root account, edit the <filename>/etc/rc.local</filename> file "
-"and add the following lines before the line <literal>touch "
+" it to the root account, edit the <filename>/etc/rc.d/rc.local</filename> "
+"file and add the following lines before the line <literal>touch "
 "/var/lock/subsys/local</literal>:"
-msgstr "<systemitem class=\"service\">cloud-init</systemitem> パッケージをインストールできない場合、SSH 公開鍵を取得し、それを root アカウントに追加するために、<filename>/etc/rc.local</filename> ファイルを編集し、<literal>touch /var/lock/subsys/local</literal> 行の前に以下の行を追加します。"
+msgstr ""

 #: ./doc/image-guide/section_centos-example.xml266(para)
 msgid ""
--- a/doc/image-guide/locale/zh_CN.po
+++ b/doc/image-guide/locale/zh_CN.po
@ -4,9 +4,9 @@
 msgid ""
 msgstr ""
 "Project-Id-Version: OpenStack Manuals\n"
-"POT-Creation-Date: 2015-01-27 14:08+0000\n"
-"PO-Revision-Date: 2015-01-27 06:41+0000\n"
-"Last-Translator: 秋林 <chenqioulin_1983@163.com>\n"
+"POT-Creation-Date: 2015-01-28 21:14+0000\n"
+"PO-Revision-Date: 2015-01-28 19:06+0000\n"
+"Last-Translator: openstackjenkins <jenkins@openstack.org>\n"
 "Language-Team: Chinese (China) (http://www.transifex.com/projects/p/openstack-manuals-i18n/language/zh_CN/)\n"
 "MIME-Version: 1.0\n"
 "Content-Type: text/plain; charset=UTF-8\n"
@ -1761,10 +1761,10 @@ msgstr "编写脚本获取公钥（如果未使用cloud-init）"
 msgid ""
 "If you are not able to install the <systemitem class=\"service\">cloud-"
 "init</systemitem> package in your image, to fetch the ssh public key and add"
-" it to the root account, edit the <filename>/etc/rc.local</filename> file "
-"and add the following lines before the line <literal>touch "
+" it to the root account, edit the <filename>/etc/rc.d/rc.local</filename> "
+"file and add the following lines before the line <literal>touch "
 "/var/lock/subsys/local</literal>:"
-msgstr "如果你不能安装 <systemitem class=\"service\">cloud-init</systemitem> 包到镜像里，获取 ssh 公钥并存放到 root 账户的方法是，编辑 <filename>/etc/rc.local</filename> 文件并添加以下的内容到 <literal>touch /var/lock/subsys/local</literal> 一行之前。"
+msgstr ""

 #: ./doc/image-guide/section_centos-example.xml266(para)
 msgid ""