Imported Translations from Zanata

For more information about this automatic import see:
https://wiki.openstack.org/wiki/Translations/Infrastructure

Change-Id: I6c77298fba046ea80a2dd34d40d33d123936e882
This commit is contained in:
OpenStack Proposal Bot 2015-09-19 06:19:21 +00:00
parent 3752173bb6
commit 261a2500cf
4 changed files with 67 additions and 112 deletions

View File

@ -11,7 +11,7 @@
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"POT-Creation-Date: 2015-09-18 05:23+0000\n"
"POT-Creation-Date: 2015-09-18 21:47+0000\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
@ -551,11 +551,6 @@ msgstr ""
"集成的一系列的 SSD 所支撑,或者是一个类似于 Ceph 或者 Gluster 之类的存储平"
"台。"
msgid ""
"A storage-focused OpenStack design architecture typically uses the following "
"components:"
msgstr "在存储型OpenStack架构设计中下列组件是典型使用的"
msgid "A storage-focused cloud design should include:"
msgstr "存储型的云设计需要包括:"
@ -907,14 +902,6 @@ msgstr "使用Hadoop或其他分布式数据处理程序来分析大数据"
msgid "Block Storage fault tolerance and availability"
msgstr "块存储的容错和可用性"
msgid ""
"Block Storage resource nodes are commonly configured with advanced RAID "
"controllers and high performance disks to provide fault tolerance at the "
"hardware level."
msgstr ""
"块存储资源节点通常都配备有高级的 RAID 控制器以及高性能的磁盘,被设计为能够在"
"硬件层面上提供容错。"
msgid ""
"Block storage also takes advantage of a number of enterprise storage "
"solutions. These are addressed via a plug-in driver developed by the "
@ -1397,21 +1384,6 @@ msgstr ""
"设计一个适用于运行虚拟桌面的基础设施是一个与为其它大部分虚拟化任务进行设计大"
"不相同的工作。该基础设施设计时必须考虑到各种因素,比如以下例子:"
msgid ""
"Designing for fault tolerance and availability of storage systems in an "
"OpenStack cloud is vastly different when comparing the Block Storage and "
"Object Storage services. The Object Storage service design features "
"consistency and partition tolerance as a function of the application. "
"Therefore, it does not have any reliance on hardware RAID controllers to "
"provide redundancy for physical disks."
msgstr ""
"在 OpenStack 云中为存储系统的容错和可用性进行设计,对于块存储和对象存储服务来"
"说,是有很大的不同的。对象存储服务具>有一致性以及区块容错,能够作为应用的功"
"能。因此,它并不依赖于硬件 RAID 控制器提供的物理磁盘冗余。与此相对的,块存储"
"资源节点\n"
"通常都配备有高级的 RAID 控制器以及高性能的磁盘,被设计为能够在硬件层面上提供"
"容错。"
msgid "Designing for the cloud"
msgstr "设计云"
@ -1516,16 +1488,6 @@ msgid ""
"selected network hardware."
msgstr "确保物理数据中心为选择的网络硬件提供了必要的电力。"
msgid ""
"Ensure that the physical data center provides the necessary power for the "
"selected network hardware. This is not typically 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 ""
"确保物理数据中心为所选择的网络硬件提供了必要的电力。对于机柜顶端型(ToR)交换机"
"没有什么影响但是spine交换机的叶和fabric以及排尾交换机(EoR)就可能发生问题,"
"假如电力不足的话。"
msgid ""
"Ensure that, if storage protocols other than Ethernet are part of the "
"storage solution, the appropriate hardware has been selected. If a "
@ -1711,16 +1673,6 @@ msgstr ""
"以启动25个实例那么此用户在两个region加起来就可以启动50个实例。但是不可以这"
"么相加因为配额只在一个region生效。"
msgid ""
"For example, many sled servers offer four independent dual-socket nodes in "
"2U for a total of 8 CPU sockets in 2U. However, the dual-socket limitation "
"on individual nodes may not be sufficient to offset their additional cost "
"and configuration complexity."
msgstr ""
"举例来说,很多雪撬服>务器提供在2U的空间置放4个独立的双插槽CPU,即2U服务器拥有8"
"颗CPU尽管如此分离节点的双插槽限制不足以抵消它们额外带来的开销和配置的复杂"
"性。"
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 "
@ -1983,15 +1935,6 @@ msgstr ""
"如果这是必须的,那么对应的服务器硬件就需要配置以支持冗余的情况。用户的需求也"
"是决定是否采用全冗余网络基础设施的关键。"
msgid ""
"If you require any of these software packages, the design must account 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 ""
"如果这些软件包都需要的话,设计必须计算额外的资源使用率(CPU内存存储以及网"
"络带宽)。其他一些潜在影响设计的有:"
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 "
@ -2530,9 +2473,6 @@ msgstr ""
msgid "Management"
msgstr "管理"
msgid "Management efficiency"
msgstr "管理效率"
msgid "Management software"
msgstr "管理软件"
@ -2627,10 +2567,6 @@ msgstr "监测网络资源情况,关注可能影响存储访问的网络服务
msgid "Monitoring of physical hardware resources."
msgstr "监测物理硬件资源。"
msgid ""
"Monitoring of storage resources such as available storage, memory and CPU."
msgstr "监测诸如可用存储空间、内存和 CPU 等存储资源信息。"
msgid "More mature, established"
msgstr "更加成熟,稳定的"
@ -2643,18 +2579,6 @@ msgstr ""
"OpenStack组件通常需要访问后端的数据库服务以存放状态和配置信息。选择合适的后端"
"数据库以满足可用性和容错的需求这是OpenStack服务所要求的。"
msgid ""
"Most blade servers typically support dual-socket multi-core CPUs. Choose "
"either full width or full height blades to avoid the limit. High density "
"blade servers support up to 16 servers in only 10 rack units using half "
"height or half width blades."
msgstr ""
"大多数的刀片服务器都支持双插槽、多核的CPU的。要避免去选择“全宽”或“全高”的刀"
"片它们会损失服务器密度。举个例子使用高密度的刀片服务器如HP BladeSystem"
"和Dell ,它们都使用半高的刀片可支持16台服务器且仅占用10个机柜单元它相比"
"于全高的刀片有效的减低了50%的密度因为全高的刀片在每10个机柜单元仅可以放置8"
"台服务器。"
msgid "Multi-hypervisor example"
msgstr "多种类型宿主机的例子"
@ -3221,12 +3145,6 @@ msgstr ""
msgid "Operational costs"
msgstr "运营成本"
msgid ""
"Operations personnel are often required to replace failed drives or nodes "
"and provide ongoing maintenance of the storage hardware."
msgstr ""
"运营人员会经常需要替换失效的驱动器或者节点,并且不断进行存储硬件的维护工作。"
msgid "Operator requirements"
msgstr "运营者的需求"
@ -3377,19 +3295,6 @@ msgstr "供应商可用性或实现细节"
msgid "Providing a simple database"
msgstr "提供一简单的数据库"
msgid ""
"Provisioning and configuration of new or upgraded storage is another "
"important consideration when it comes to management of resources. The "
"ability to easily deploy, configure, and manage storage hardware results in "
"a solution that is easy to manage. This also makes use of management systems "
"that can automate other pieces of the overall solution. For example, "
"replication, retention, data backup and recovery."
msgstr ""
"准备和配置新增或者升级的存储,是另外一个关于管理存储资源的重要考虑因素。方便"
"地部署、配置以及管理存储硬件的能力,能够造就一个容易管理的解决方案。这同样也"
"利用了能够将整个解决方案中的其它部分组件自动化的管理系统。例如,复制、保管、"
"数据备份和恢复。"
msgid "Proxy:"
msgstr "代理:"
@ -4982,14 +4887,6 @@ msgstr ""
"用Pacemaker会影响到设计假定有至少2台控制器基础设施其中一个节点可在待机模"
"式下运行的某些服务。"
msgid ""
"While OpenStack is a fairly complete collection of software projects for "
"building a platform for cloud services, you may need to add other pieces of "
"software."
msgstr ""
"OpenStack为了构建一个平台提供云服务是完全公平的收集软件的项目。在任何给定的"
"OpenStack设计中都需要考虑那些附加的软件。"
msgid ""
"While consistency and partition tolerance are both inherent features of the "
"Object Storage service, it is important to design the overall storage "

View File

@ -1,7 +1,7 @@
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"POT-Creation-Date: 2015-09-15 06:28+0000\n"
"POT-Creation-Date: 2015-09-19 06:16+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"
@ -11532,7 +11532,7 @@ msgid "<emphasis>Monitor (MON)</emphasis>. A lightweight daemon that handles all
msgstr ""
#: ./doc/config-reference/block-storage/drivers/ceph-rbd-volume-driver.xml:58(para)
msgid "Ceph developers recommend that you use <systemitem>Btrfs</systemitem> as a file system for storage. XFS might be a better alternative for production environments;XFS is an excellent alternative to Btrfs. The ext4 file system is also compatible but does not exploit the power of Ceph."
msgid "Ceph developers recommend XFS for production deployments, <systemitem>Btrfs</systemitem> for testing, development, and any non-critical deployments. Btrfs has the correct feature set and roadmap to serve Ceph in the long-term, but XFS and ext4 provide the necessary stability for todays deployments."
msgstr ""
#: ./doc/config-reference/block-storage/drivers/ceph-rbd-volume-driver.xml:63(para)

View File

@ -4,16 +4,17 @@
# Tomoyuki KATO <tomo@dream.daynight.jp>, 2013-2015
#
#
# Akihiro Motoki <amotoki@gmail.com>, 2015. #zanata
# OpenStack Infra <zanata@openstack.org>, 2015. #zanata
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"POT-Creation-Date: 2015-09-16 12:29+0000\n"
"POT-Creation-Date: 2015-09-18 21:48+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-04 11:17+0000\n"
"Last-Translator: Tomoyuki KATO <tomo@dream.daynight.jp>\n"
"PO-Revision-Date: 2015-09-18 06:59+0000\n"
"Last-Translator: Akihiro Motoki <amotoki@gmail.com>\n"
"Language-Team: Japanese (http://www.transifex.com/openstack/openstack-"
"manuals-i18n/language/ja/)\n"
"Language: ja\n"
@ -1751,6 +1752,10 @@ msgstr ""
"ケージをインストールし、その場所を <placeholder-2/> に伝える必要があります。"
"FreeBSD 10.1 の場合、これらのコマンドを実行します。"
msgid "In a CentOS image, the login account is <literal>centos</literal>."
msgstr ""
"CentOS イメージの場合、ログインアカウントは <literal>centos</literal> です。"
msgid ""
"In a CirrOS image, the login account is <literal>cirros</literal>. The "
"password is <literal>cubswin:)</literal>"

View File

@ -10,18 +10,19 @@
# Tomoyuki KATO <tomo@dream.daynight.jp>, 2013-2015
# yfukuda <fukuda.yuko@jp.fujitsu.com>, 2014
# ykatabam <ykatabam@redhat.com>, 2014
# Akihiro Motoki <amotoki@gmail.com>, 2015. #zanata
# KATO Tomoyuki <kato.tomoyuki@jp.fujitsu.com>, 2015. #zanata
# OpenStack Infra <zanata@openstack.org>, 2015. #zanata
msgid ""
msgstr ""
"Project-Id-Version: Admin User Guide 1.0.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2015-09-18 05:24+0000\n"
"POT-Creation-Date: 2015-09-18 21:49+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-16 01:05+0000\n"
"Last-Translator: KATO Tomoyuki <kato.tomoyuki@jp.fujitsu.com>\n"
"PO-Revision-Date: 2015-09-18 06:58+0000\n"
"Last-Translator: Akihiro Motoki <amotoki@gmail.com>\n"
"Language-Team: Japanese (http://www.transifex.com/openstack/openstack-"
"manuals-i18n/language/ja/)\n"
"Language: ja\n"
@ -1052,6 +1053,17 @@ msgstr "フレーバー"
msgid "Flavor ID"
msgstr "フレーバー ID"
msgid ""
"Flavors can also determine on which compute host a flavor can be used to "
"launch an instance. For information about customizing flavors, refer to the "
"`OpenStack Cloud Administrator Guide <http://docs.openstack.org/admin-guide-"
"cloud/compute-flavors.html>`_."
msgstr ""
"フレーバーは、インスタンスを起動するために使用できるコンピュートホストを決め"
"ることもできます。フレーバーのカスタマイズの詳細は、`OpenStack Cloud "
"Administrator Guide <http://docs.openstack.org/admin-guide-cloud/compute-"
"flavors.html>`_ を参照してください。"
msgid "For a list of optional parameters, run this command::"
msgstr "オプションパラメーターの一覧は、このコマンドを実行します。"
@ -1070,6 +1082,17 @@ msgstr ""
"イメージ作成の詳細は `仮想マシンイメージガイド <http://docs.openstack.org/ja/"
"image-guide/content/>`_ を参照してください。"
msgid ""
"For details on creating public networks using OpenStack Networking "
"(``neutron``), refer to the `OpenStack Cloud Administrator Guide <http://"
"docs.openstack.org/admin-guide-cloud/networking_adv-features.html>`_ . No "
"floating IP addresses are created by default in OpenStack Networking."
msgstr ""
"OpenStack Networking (``neutron``) を用いてパブリックネットワークを作成する方"
"法は、`OpenStack Cloud Administrator Guide <http://docs.openstack.org/admin-"
"guide-cloud/networking_adv-features.html>`_ を参照してください。Floating IP "
"アドレスは、OpenStack Networking のデフォルトで作成されません。"
msgid "For each item in the list, run the swift **download -o -** command."
msgstr "一覧の各項目に対して、swift **download -o -** コマンドを実行します。"
@ -1095,6 +1118,15 @@ msgstr "例:"
msgid "For example::"
msgstr "例::"
msgid ""
"For information about supporting metadata keys, see the `OpenStack Cloud "
"Administrator Guide <http://docs.openstack.org/admin-guide-cloud/compute-"
"flavors.html>`__."
msgstr ""
"メタデータキーのサポートに関する詳細は、`OpenStack Cloud Administrator Guide "
"<http://docs.openstack.org/admin-guide-cloud/compute-flavors.html>`__ を参照"
"してください。"
msgid "For information about the:"
msgstr "詳細は以下のとおりです。"
@ -1260,6 +1292,27 @@ msgstr ""
"EC2 互換 API を使用することにより、アクセスを自動化したり、ツールを構築したり"
"して、リソースやサービスを管理できます。"
msgid ""
"In addition, you can set or unset ``extra_spec`` for the existing flavor. "
"The ``extra_spec`` metadata keys can influence the instance directly when it "
"is launched. If a flavor sets the ``extra_spec key/value quota:"
"vif_outbound_peak=65536``, the instance's out bound peak bandwidth I/O "
"should be LTE 512 Mbps. There are several aspects that can work for an "
"instance including **CPU limits**, **Disk tuning**, **Bandwidth I/O**, "
"**Watchdog behavior**, and **Random-number generator**. For information "
"about supporting metadata keys, see the `OpenStack Cloud Administrator Guide "
"<http://docs.openstack.org/admin-guide-cloud/compute-flavors.html>`__."
msgstr ""
"さらに、既存のフレーバーの ``extra_spec`` を設定または設定解除できます。"
"``extra_spec`` メタデータキーは、インスタンスの起動時に直接反映されます。フ"
"レーバーに ``extra_spec key/value quota:vif_outbound_peak=65536`` が設定され"
"ていると、インスタンスの送信ピーク帯域 I/O は LTE 512 Mbps にすべきです。"
"**CPU 制限**、**ディスクチューニング**、**帯域 I/O**, **ウォッチドッグの挙動"
"**、**乱数生成器** など、インスタンスに機能する、いくつかの観点があります。メ"
"タデータキーのサポートの詳細は、`OpenStack Cloud Administrator Guide <http://"
"docs.openstack.org/admin-guide-cloud/compute-flavors.html>`__ を参照してくだ"
"さい。"
msgid ""
"In the :guilabel:`Add/Remove Hosts to Aggregate` dialog box, click **+** to "
"assign a host to an aggregate. Click **-** to remove a host that is assigned "