Imported Translations from Zanata
For more information about this automatic import see: https://wiki.openstack.org/wiki/Translations/Infrastructure Change-Id: Ia3ddd050bd4744a22c666558135184d9acc1e839
This commit is contained in:
OpenStack Proposal Bot
parent
36144bcd8e
commit
1446e9ec54
@ -8,7 +8,7 @@ msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: Cloud Administrator Guide 0.9\n"
|
||||
"Report-Msgid-Bugs-To: \n"
|
||||
"POT-Creation-Date: 2015-09-16 17:47+0000\n"
|
||||
"POT-Creation-Date: 2015-09-18 06:18+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"
|
||||
@ -1191,7 +1191,7 @@ msgstr ""
|
||||
msgid "*1085276160*"
|
||||
msgstr ""
|
||||
|
||||
#: ../blockstorage_volume_backups.rst:113
|
||||
#: ../blockstorage_volume_backups.rst:118
|
||||
msgid ""
|
||||
"*MOUNT_OPTIONS* is a comma-separated string of NFS mount options as detailed "
|
||||
"in the NFS man page."
|
||||
@ -1710,7 +1710,7 @@ msgid ""
|
||||
"that are available across the regions."
|
||||
msgstr ""
|
||||
|
||||
#: ../blockstorage_volume_backups.rst:53
|
||||
#: ../blockstorage_volume_backups.rst:58
|
||||
msgid ""
|
||||
"A new configure option ``backup_swift_block_size`` is introduced into :file:"
|
||||
"`cinder.conf` for the default Swift backup driver. This is the size in bytes "
|
||||
@ -2613,7 +2613,7 @@ msgstr ""
|
||||
msgid "Alternatively, use the API directly:"
|
||||
msgstr ""
|
||||
|
||||
#: ../blockstorage_volume_backups.rst:78
|
||||
#: ../blockstorage_volume_backups.rst:83
|
||||
msgid ""
|
||||
"Alternatively, you can export and save the metadata of selected volume "
|
||||
"backups. Doing so precludes the need to back up the entire Block Storage "
|
||||
@ -3321,7 +3321,7 @@ msgid ""
|
||||
"migration`."
|
||||
msgstr ""
|
||||
|
||||
#: ../blockstorage_volume_backups.rst:73
|
||||
#: ../blockstorage_volume_backups.rst:78
|
||||
msgid ""
|
||||
"Because volume backups are dependent on the Block Storage database, you must "
|
||||
"also back up your Block Storage database regularly to ensure data recovery."
|
||||
@ -3585,6 +3585,10 @@ msgid ""
|
||||
"levels of the corresponding modules can be found in the table referred above."
|
||||
msgstr ""
|
||||
|
||||
#: ../blockstorage_image_volume_cache.rst:64
|
||||
msgid "By default they will be set to 0, which means unlimited."
|
||||
msgstr ""
|
||||
|
||||
#: ../compute-service-groups.rst:23
|
||||
msgid ""
|
||||
"By default, Compute uses the database driver to track if a node is live. In "
|
||||
@ -3635,7 +3639,7 @@ msgid ""
|
||||
"user to modify it."
|
||||
msgstr ""
|
||||
|
||||
#: ../blockstorage_volume_backups.rst:90
|
||||
#: ../blockstorage_volume_backups.rst:95
|
||||
msgid "By default, the swift object store is used for the backup repository."
|
||||
msgstr ""
|
||||
|
||||
@ -3796,6 +3800,12 @@ msgstr ""
|
||||
msgid "CUPS(Compute Us\\ age Per Second) index data of the system"
|
||||
msgstr ""
|
||||
|
||||
#: ../blockstorage_image_volume_cache.rst:75
|
||||
msgid ""
|
||||
"Cache actions will trigger Telemetry messages. There are several that will "
|
||||
"be sent."
|
||||
msgstr ""
|
||||
|
||||
#: ../dashboard_sessions.rst:175
|
||||
msgid "Cached database"
|
||||
msgstr ""
|
||||
@ -4474,6 +4484,14 @@ msgstr ""
|
||||
msgid "Configure the Identity service with SSL"
|
||||
msgstr ""
|
||||
|
||||
#: ../blockstorage_image_volume_cache.rst:48
|
||||
msgid "Configure the Image-Volume cache"
|
||||
msgstr ""
|
||||
|
||||
#: ../blockstorage_image_volume_cache.rst:22
|
||||
msgid "Configure the Internal Tenant"
|
||||
msgstr ""
|
||||
|
||||
#: ../keystone_caching_layer.rst:121
|
||||
msgid "Configure the Memcached back end example"
|
||||
msgstr ""
|
||||
@ -6327,7 +6345,10 @@ msgid ""
|
||||
"bandwidth of ``lvmdriver-1`` up to 100 MiB/s:"
|
||||
msgstr ""
|
||||
|
||||
# #-#-#-#-# blockstorage-driver-filter-weighing.pot (Cloud Administrator Guide 0.9) #-#-#-#-#
|
||||
# #-#-#-#-# blockstorage_image_volume_cache.pot (Cloud Administrator Guide 0.9) #-#-#-#-#
|
||||
#: ../blockstorage-driver-filter-weighing.rst:56
|
||||
#: ../blockstorage_image_volume_cache.rst:36
|
||||
msgid "Example :file:`cinder.conf` configuration file::"
|
||||
msgstr ""
|
||||
|
||||
@ -7052,6 +7073,12 @@ msgstr ""
|
||||
msgid "For every node running a ``nova-*`` service, install python-netaddr:"
|
||||
msgstr ""
|
||||
|
||||
#: ../blockstorage_image_volume_cache.rst:66
|
||||
msgid ""
|
||||
"For example, a configuration which would limit the max size to 200 GB and 50 "
|
||||
"cache entries will be configured as::"
|
||||
msgstr ""
|
||||
|
||||
#: ../objectstorage_ringbuilder.rst:74
|
||||
msgid ""
|
||||
"For example, consider a 3-node cluster of machines with equal-size disks; "
|
||||
@ -7275,7 +7302,7 @@ msgid ""
|
||||
"User Guide."
|
||||
msgstr ""
|
||||
|
||||
#: ../blockstorage_volume_backups.rst:87
|
||||
#: ../blockstorage_volume_backups.rst:92
|
||||
msgid ""
|
||||
"For more information about how to export and import volume backup metadata, "
|
||||
"see the section called :ref:`volume_backups_export_import`."
|
||||
@ -7429,7 +7456,7 @@ msgid ""
|
||||
"reboots:"
|
||||
msgstr ""
|
||||
|
||||
#: ../blockstorage_volume_backups.rst:102
|
||||
#: ../blockstorage_volume_backups.rst:107
|
||||
msgid ""
|
||||
"For the ``backup_share`` option, replace *HOST* with the DNS resolvable host "
|
||||
"name or the IP address of the storage server for the NFS share, and "
|
||||
@ -8100,13 +8127,20 @@ msgid ""
|
||||
"chain is also in PEM format."
|
||||
msgstr ""
|
||||
|
||||
#: ../blockstorage_volume_backups.rst:92
|
||||
#: ../blockstorage_volume_backups.rst:97
|
||||
msgid ""
|
||||
"If instead you want to use an NFS export as the backup repository, add the "
|
||||
"following configuration options to the ``[DEFAULT]`` section of the :file:"
|
||||
"`cinder.conf` file and restart the Block Storage services:"
|
||||
msgstr ""
|
||||
|
||||
#: ../blockstorage_image_volume_cache.rst:95
|
||||
msgid ""
|
||||
"If needed, you can delete these volumes manually to clear the cache. By "
|
||||
"using the standard volume deletion APIs, the Block Storage service will "
|
||||
"clean up correctly."
|
||||
msgstr ""
|
||||
|
||||
#: ../networking_config-agents.rst:106
|
||||
msgid ""
|
||||
"If no dnsmasq process for subnet's network is launched, Networking will "
|
||||
@ -8479,7 +8513,7 @@ msgid ""
|
||||
"this error."
|
||||
msgstr ""
|
||||
|
||||
#: ../blockstorage_volume_backups.rst:83
|
||||
#: ../blockstorage_volume_backups.rst:88
|
||||
msgid ""
|
||||
"If you specify a UUID encryption key when setting up the volume "
|
||||
"specifications, the backup metadata ensures that the key will remain valid "
|
||||
@ -8632,6 +8666,10 @@ msgstr ""
|
||||
msgid "Image properties and property protection"
|
||||
msgstr ""
|
||||
|
||||
#: ../blockstorage_image_volume_cache.rst:6
|
||||
msgid "Image-Volume cache"
|
||||
msgstr ""
|
||||
|
||||
#: ../compute-images-instances.rst:3
|
||||
msgid "Images and instances"
|
||||
msgstr ""
|
||||
@ -8826,6 +8864,12 @@ msgid ""
|
||||
"network interface depending on the expected workload and desired performance."
|
||||
msgstr ""
|
||||
|
||||
#: ../blockstorage_image_volume_cache.rst:92
|
||||
msgid ""
|
||||
"In normal usage there should be no need for manual intervention with the "
|
||||
"cache. The entries and their backing Image-Volumes are managed automatically."
|
||||
msgstr ""
|
||||
|
||||
#: ../telemetry-measurements.rst:788
|
||||
msgid ""
|
||||
"In order to access Ceph from Telemetry, you need to specify a ``service "
|
||||
@ -10095,6 +10139,10 @@ msgstr ""
|
||||
msgid "Manage volumes"
|
||||
msgstr ""
|
||||
|
||||
#: ../blockstorage_image_volume_cache.rst:90
|
||||
msgid "Managing cached Image-Volumes"
|
||||
msgstr ""
|
||||
|
||||
#: ../compute-euca2ools.rst:5
|
||||
msgid "Managing the cloud with euca2ools"
|
||||
msgstr ""
|
||||
@ -10745,8 +10793,10 @@ msgstr ""
|
||||
msgid "Notification options"
|
||||
msgstr ""
|
||||
|
||||
# #-#-#-#-# blockstorage_image_volume_cache.pot (Cloud Administrator Guide 0.9) #-#-#-#-#
|
||||
# #-#-#-#-# networking_adv-operational-features.pot (Cloud Administrator Guide 0.9) #-#-#-#-#
|
||||
# #-#-#-#-# telemetry-data-collection.pot (Cloud Administrator Guide 0.9) #-#-#-#-#
|
||||
#: ../blockstorage_image_volume_cache.rst:73
|
||||
#: ../networking_adv-operational-features.rst:48
|
||||
#: ../telemetry-data-collection.rst:27 ../telemetry-data-collection.rst:38
|
||||
msgid "Notifications"
|
||||
@ -11267,6 +11317,14 @@ msgid ""
|
||||
"virtual capacities for thin provisioning using the oversubscription ratio."
|
||||
msgstr ""
|
||||
|
||||
#: ../blockstorage_image_volume_cache.rst:8
|
||||
msgid ""
|
||||
"OpenStack Block Storage has an optional Image cache which can dramatically "
|
||||
"improve the performance of creating a volume from an image. The improvement "
|
||||
"depends on many factors, primarily how quickly the configured back end can "
|
||||
"clone a volume."
|
||||
msgstr ""
|
||||
|
||||
#: ../blockstorage_glusterfs_backend.rst:169
|
||||
msgid "OpenStack Block Storage is now configured to use a GlusterFS back end."
|
||||
msgstr ""
|
||||
@ -14279,6 +14337,15 @@ msgstr ""
|
||||
msgid "The Image service supports these back-end stores:"
|
||||
msgstr ""
|
||||
|
||||
#: ../blockstorage_image_volume_cache.rst:24
|
||||
msgid ""
|
||||
"The Image-Volume cache requires that the Internal Tenant be configured for "
|
||||
"the Block Storage services. This tenant will own the cached image-volumes so "
|
||||
"they can be managed like normal users including tools like volume quotas. "
|
||||
"This protects normal users from having to see the cached image-volumes, but "
|
||||
"does not make them globally hidden."
|
||||
msgstr ""
|
||||
|
||||
#: ../networking_introduction.rst:320
|
||||
msgid ""
|
||||
"The Internet Key Exchange (IKE) policy that identifies the authentication "
|
||||
@ -15135,6 +15202,13 @@ msgid ""
|
||||
"also report a volume size of 1.01 GB::"
|
||||
msgstr ""
|
||||
|
||||
#: ../blockstorage_image_volume_cache.rst:43
|
||||
msgid ""
|
||||
"The actual user and project that are configured for the Internal Tenant do "
|
||||
"not require any special privileges. They can be the Block Storage service "
|
||||
"tenant or can be any normal project and user."
|
||||
msgstr ""
|
||||
|
||||
#: ../compute-configuring-migrations.rst:397
|
||||
msgid ""
|
||||
"The added compute node and the host will shut down to join the host to the "
|
||||
@ -15277,6 +15351,12 @@ msgstr ""
|
||||
msgid "The browser or client connects to the proxy."
|
||||
msgstr ""
|
||||
|
||||
#: ../blockstorage_image_volume_cache.rst:18
|
||||
msgid ""
|
||||
"The cache itself is configurable per back end and will contain the most "
|
||||
"recently used images."
|
||||
msgstr ""
|
||||
|
||||
#: ../telemetry-data-collection.rst:784
|
||||
msgid "The calculation is limited to meters with the same interval."
|
||||
msgstr ""
|
||||
@ -15804,7 +15884,11 @@ msgstr ""
|
||||
#: ../blockstorage_volume_backups.rst:50
|
||||
msgid ""
|
||||
"The first backup of a volume has to be a full backup. Attempting to do an "
|
||||
"incremental backup without any existing backups will fail."
|
||||
"incremental backup without any existing backups will fail. There is an "
|
||||
"``is_incremental`` flag that indicates whether a backup is incremental when "
|
||||
"showing details on the backup. Another flag, ``has_dependent_backups``, "
|
||||
"returned when showing backup details, will indicate whether the backup has "
|
||||
"dependent backups. If it is true, attempting to delete this backup will fail."
|
||||
msgstr ""
|
||||
|
||||
#: ../telemetry-data-retrieval.rst:357
|
||||
@ -16421,7 +16505,7 @@ msgid ""
|
||||
"that the default values work fine in most cases."
|
||||
msgstr ""
|
||||
|
||||
#: ../blockstorage_volume_backups.rst:126
|
||||
#: ../blockstorage_volume_backups.rst:131
|
||||
msgid ""
|
||||
"The option ``backup_compression_algorithm`` can be set to ``bz2`` or "
|
||||
"``None``. The latter can be a useful setting when the server providing the "
|
||||
@ -16429,7 +16513,7 @@ msgid ""
|
||||
"on the backup data."
|
||||
msgstr ""
|
||||
|
||||
#: ../blockstorage_volume_backups.rst:131
|
||||
#: ../blockstorage_volume_backups.rst:136
|
||||
msgid ""
|
||||
"The option ``backup_file_size`` must be a multiple of "
|
||||
"``backup_sha_block_size_bytes``. It is effectively the maximum file size to "
|
||||
@ -17372,7 +17456,14 @@ msgid ""
|
||||
"meaningfully determine the alarm state."
|
||||
msgstr ""
|
||||
|
||||
#: ../blockstorage_volume_backups.rst:116
|
||||
#: ../blockstorage_image_volume_cache.rst:57
|
||||
msgid ""
|
||||
"There are optional configuration settings that can limit the size of the "
|
||||
"cache. These can also be scoped per back end or in the default options in :"
|
||||
"file:`cinder.conf`::"
|
||||
msgstr ""
|
||||
|
||||
#: ../blockstorage_volume_backups.rst:121
|
||||
msgid ""
|
||||
"There are several other options whose default values may be overridden as "
|
||||
"appropriate for your environment:"
|
||||
@ -17672,6 +17763,10 @@ msgid ""
|
||||
"encryption; session data is still readable by an attacker."
|
||||
msgstr ""
|
||||
|
||||
#: ../blockstorage_image_volume_cache.rst:55
|
||||
msgid "This can be scoped per back end definition or in the default options."
|
||||
msgstr ""
|
||||
|
||||
#: ../identity_troubleshoot.rst:151
|
||||
msgid ""
|
||||
"This can present a problem when you run the Identity daemon under the "
|
||||
@ -17696,7 +17791,7 @@ msgid ""
|
||||
"instance. This includes all compute nodes."
|
||||
msgstr ""
|
||||
|
||||
#: ../blockstorage_volume_backups.rst:61
|
||||
#: ../blockstorage_volume_backups.rst:66
|
||||
msgid ""
|
||||
"This command also returns a backup ID. Use this backup ID when restoring the "
|
||||
"volume::"
|
||||
@ -18658,6 +18753,18 @@ msgid ""
|
||||
"``[neutron]`` section in :file:`nova.conf`."
|
||||
msgstr ""
|
||||
|
||||
#: ../blockstorage_image_volume_cache.rst:30
|
||||
msgid ""
|
||||
"To enable the Block Storage services to have access to an Internal Tenant, "
|
||||
"set the following options in the :file:`cinder.conf` file::"
|
||||
msgstr ""
|
||||
|
||||
#: ../blockstorage_image_volume_cache.rst:50
|
||||
msgid ""
|
||||
"To enable the Image-Volume cache, set the following configuration option in :"
|
||||
"file:`cinder.conf`::"
|
||||
msgstr ""
|
||||
|
||||
#: ../telemetry-data-collection.rst:385
|
||||
msgid ""
|
||||
"To enable the compute agent to run multiple instances simultaneously with "
|
||||
@ -20299,6 +20406,14 @@ msgid ""
|
||||
"all egress. Rules can be added to this group in order to change the behavior."
|
||||
msgstr ""
|
||||
|
||||
#: ../blockstorage_image_volume_cache.rst:13
|
||||
msgid ""
|
||||
"When a volume is first created from an image, a new cached image-volume will "
|
||||
"be created that is owned by the Block Storage Internal Tenant. Subsequent "
|
||||
"requests to create volumes from that image will clone the cached version "
|
||||
"instead of downloading the image contents and copying data to the volume."
|
||||
msgstr ""
|
||||
|
||||
#: ../objectstorage_ringbuilder.rst:187
|
||||
msgid ""
|
||||
"When building a new ring from an old ring, the ring builder recalculates the "
|
||||
@ -20331,11 +20446,11 @@ msgid ""
|
||||
"options are used."
|
||||
msgstr ""
|
||||
|
||||
#: ../blockstorage_volume_backups.rst:66
|
||||
#: ../blockstorage_volume_backups.rst:71
|
||||
msgid "When restoring from a full backup, it is a full restore."
|
||||
msgstr ""
|
||||
|
||||
#: ../blockstorage_volume_backups.rst:68
|
||||
#: ../blockstorage_volume_backups.rst:73
|
||||
msgid ""
|
||||
"When restoring from an incremental backup, a list of backups is built based "
|
||||
"on the IDs of the parent backups. A full restore is performed based on the "
|
||||
@ -21982,6 +22097,25 @@ msgstr ""
|
||||
msgid "``html5proxy_port = 6082``"
|
||||
msgstr ""
|
||||
|
||||
#: ../blockstorage_image_volume_cache.rst:85
|
||||
msgid ""
|
||||
"``image_volume_cache.evict`` - A cached image-volume has been deleted from "
|
||||
"the cache."
|
||||
msgstr ""
|
||||
|
||||
#: ../blockstorage_image_volume_cache.rst:82
|
||||
msgid ""
|
||||
"``image_volume_cache.hit`` - A volume is being created from an image which "
|
||||
"was found in the cache and the fast path can be taken."
|
||||
msgstr ""
|
||||
|
||||
#: ../blockstorage_image_volume_cache.rst:78
|
||||
msgid ""
|
||||
"``image_volume_cache.miss`` - A volume is being created from an image which "
|
||||
"was not found in the cache. Typically this will mean a new cache entry would "
|
||||
"be created for it."
|
||||
msgstr ""
|
||||
|
||||
#: ../objectstorage-monitoring.rst:174
|
||||
msgid ""
|
||||
"``increment(self, metric, sample_rate=1)`` Increments the given counter "
|
||||
|
||||
File diff suppressed because it is too large
Load Diff
@ -11,7 +11,7 @@
|
||||
msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: PACKAGE VERSION\n"
|
||||
"POT-Creation-Date: 2015-09-16 12:28+0000\n"
|
||||
"POT-Creation-Date: 2015-09-18 05:23+0000\n"
|
||||
"MIME-Version: 1.0\n"
|
||||
"Content-Type: text/plain; charset=UTF-8\n"
|
||||
"Content-Transfer-Encoding: 8bit\n"
|
||||
@ -434,28 +434,6 @@ msgstr ""
|
||||
"通用型OpenStack云的设计，使核心的OpenStack服务的互相紧密配合为最终用户提供广"
|
||||
"泛的服务。在通用型云中建议的OpenStack核心服务有："
|
||||
|
||||
msgid ""
|
||||
"A general purpose OpenStack deployment consists of more than just OpenStack-"
|
||||
"specific components. A typical deployment involves services that provide "
|
||||
"supporting functionality, including databases and message queues, and may "
|
||||
"also involve software to provide high availability of the OpenStack "
|
||||
"environment. Design decisions around the underlying message queue might "
|
||||
"affect the required number of controller services, as well as the technology "
|
||||
"to provide highly resilient database functionality, such as MariaDB with "
|
||||
"Galera. In such a scenario, replication of services relies on quorum. "
|
||||
"Therefore, the underlying database nodes, for example, should consist of at "
|
||||
"least 3 nodes to account for the recovery of a failed Galera node. When "
|
||||
"increasing the number of nodes to support a feature of the software, "
|
||||
"consideration of rack space and switch port density becomes important."
|
||||
msgstr ""
|
||||
"通用型OpenStack的软件部署不仅仅是OpenStack特定的组件。一个典型的部署，如提供"
|
||||
"支撑功能的服务，须包含数据库，消息队列，以及为OpenStack环境提供高可用的软件。"
|
||||
"设计的决定围绕着底层的消息队列会影响到控制器服务的多寡，正如技术上为数据库提"
|
||||
"供高弹性功能，例如在MariaDB之上使用Galera。在这些场景中，服务的复制依赖于预订"
|
||||
"的机器数，因此，考虑数据库的\n"
|
||||
"节点，例如，至少需要3个节点才可满足Galera节点的失效恢复。随着节点数量的增加，"
|
||||
"以支持软件的特性，考虑机柜的空间和交换机的端口显得非常的重要。"
|
||||
|
||||
msgid ""
|
||||
"A general purpose cloud is designed to have a range of potential uses or "
|
||||
"functions; not specialized for specific use cases. General purpose "
|
||||
@ -613,11 +591,6 @@ msgid ""
|
||||
msgstr ""
|
||||
"对象存储集群内的区域是一个逻辑上的划分。一个区域可以是下列情形中的任意之一："
|
||||
|
||||
msgid ""
|
||||
"API availability guarantees implying multiple infrastructure services, and "
|
||||
"highly available load balancers."
|
||||
msgstr "由多基础设施服务和高可用负载均衡实现API可用性保证。"
|
||||
|
||||
msgid "Active archive, backups and hierarchical storage management."
|
||||
msgstr "活跃归档、备份和分级存储管理"
|
||||
|
||||
@ -800,25 +773,6 @@ msgstr "应用的可知性"
|
||||
msgid "Application cloud readiness"
|
||||
msgstr "为云准备好应用程序"
|
||||
|
||||
msgid ""
|
||||
"Application design must also be factored into the capabilities of the "
|
||||
"underlying cloud infrastructure. If the compute hosts do not provide a "
|
||||
"seamless live migration capability, then it must be expected that when a "
|
||||
"compute host fails, that instance and any data local to that instance will "
|
||||
"be deleted. Conversely, when providing an expectation to users that "
|
||||
"instances have a high-level of uptime guarantees, the infrastructure must be "
|
||||
"deployed in a way that eliminates any single point of failure when a compute "
|
||||
"host disappears. This may include utilizing shared file systems on "
|
||||
"enterprise storage or OpenStack Block storage to provide a level of "
|
||||
"guarantee to match service features."
|
||||
msgstr ""
|
||||
"应用程序的设计也必须记入到云基础设施的能力之中。如果计算主机不能提供无缝的活"
|
||||
"迁移功能，就必须预料到一旦计算节点失效，运行在其上的实例，以及其中的数据，都"
|
||||
"不可访问。反过来讲，提供给用户的是具有高级别的运行时间保证的实例，基础设施必"
|
||||
"须被部署为没有任何的单点故障，即使是某计算主机消失，也得马上有其他主机顶上。"
|
||||
"这需要构建在企业级存储的共享文件系统之上，或者是OpenStack块存储，以满足保证级"
|
||||
"别和对应的服务匹配。"
|
||||
|
||||
msgid "Application momentum"
|
||||
msgstr "应用增长"
|
||||
|
||||
@ -1464,9 +1418,6 @@ msgstr "设计云"
|
||||
msgid "Designing network resources"
|
||||
msgstr "规划网络资源"
|
||||
|
||||
msgid "Designing storage 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, "
|
||||
@ -1585,20 +1536,6 @@ msgstr ""
|
||||
"应的硬件。如果选择了中心化的存储阵列，hypervisor若访问镜像存储就得能够连接到"
|
||||
"阵列。"
|
||||
|
||||
msgid ""
|
||||
"Ensure your deployment has adequate back-up capabilities. As an example, in "
|
||||
"a deployment that has two infrastructure controller nodes, the design should "
|
||||
"include controller availability. In the event of the loss of a single "
|
||||
"controller, cloud services will run from a single controller in the event of "
|
||||
"failure. Where the design has higher availability requirements, it is "
|
||||
"important to meet those requirements by designing the proper redundancy and "
|
||||
"availability of controller nodes."
|
||||
msgstr ""
|
||||
"确保用户的部署有足够的后备能力。举例来说，部署是拥有两台基础设施的控制器节"
|
||||
"点，此设计须包括控制器可用。一旦丢失单个控制器这种事件发生，云服务将会停止对"
|
||||
"外服务。当有高可用需求的设计时，解决此需求的办法就是准备冗余的、高可用的控制"
|
||||
"器节点。"
|
||||
|
||||
msgid ""
|
||||
"Environments operating at massive scale typically need their regions or "
|
||||
"sites subdivided further without exposing the requirement to specify the "
|
||||
@ -1774,23 +1711,6 @@ msgstr ""
|
||||
"以启动25个实例，那么此用户在两个region加起来就可以启动50个实例。但是不可以这"
|
||||
"么相加，因为配额只在一个region生效。"
|
||||
|
||||
msgid ""
|
||||
"For example, if a compute host failed, this would be an operational "
|
||||
"consideration; requiring the restoration of instances from a snapshot or re-"
|
||||
"spawning an instance. The overall application design is impacted, general "
|
||||
"purpose clouds should not need to provide abilities to migrate instances "
|
||||
"from one host to another. Additional considerations need to be made around "
|
||||
"supporting instance migration if the expectation is that the application "
|
||||
"will be designed to tolerate failure. Extra support services, including "
|
||||
"shared storage attached to compute hosts, might need to be deployed in this "
|
||||
"example."
|
||||
msgstr ""
|
||||
"举例来说，如果计算主机失效，这就是运维要考虑的；需要将之前运行在其上的实例从"
|
||||
"快照中恢复或者重新建一个一模一样的实例。整个应用程序的设计都会被影响，通用型"
|
||||
"云不强求有提供将一个实例从一台主机迁移到另外一台主机的能力。假如用户期望其应"
|
||||
"用是被设计为容错的，那么就要额外考虑支持实例的迁移，也需要额外的支持服务，包"
|
||||
"括共享存储挂载到计算主机，就需要被部署。"
|
||||
|
||||
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 "
|
||||
@ -1801,18 +1721,6 @@ msgstr ""
|
||||
"颗CPU，尽管如此，分离节点的双插槽限制不足以抵消它们额外带来的开销和配置的复杂"
|
||||
"性。"
|
||||
|
||||
msgid ""
|
||||
"For example, web application instances may run on a public network presented "
|
||||
"through OpenStack Networking that has 1 GbE capability, whereas the back-end "
|
||||
"database uses an OpenStack Networking network that has 10GbE capability to "
|
||||
"replicate its data or, in some cases, the design may incorporate link "
|
||||
"aggregation for greater throughput."
|
||||
msgstr ""
|
||||
"例如，web应用的实例在公网上运行的是OpenStack网络中的1 GbE，但是其后端的数据库"
|
||||
"使用的是OpenStack网络的10 GbE以复制数据，在某些情况下，为了更大的吞吐量使用聚"
|
||||
"合链接这\n"
|
||||
"样的设计。"
|
||||
|
||||
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 "
|
||||
@ -1997,9 +1905,6 @@ msgstr ""
|
||||
msgid "How this book is organized"
|
||||
msgstr "本书是如何组织的"
|
||||
|
||||
msgid "However, depending on the use case, these could be optional."
|
||||
msgstr "尽管如此，依赖于用例，这些是可选。"
|
||||
|
||||
msgid "Hybrid"
|
||||
msgstr "混合云"
|
||||
|
||||
@ -2141,23 +2046,6 @@ msgstr ""
|
||||
"的数据。某些情况下，可能还需要创建额外的后端存储网络，专用于为实例和块存储资"
|
||||
"源之间提供网络连接，来保证没有对于网络资源的争抢。"
|
||||
|
||||
msgid ""
|
||||
"In a general purpose OpenStack cloud, the requirements of the network help "
|
||||
"determine performance capabilities. For example, small deployments may "
|
||||
"employ 1 Gigabit Ethernet (GbE) networking, whereas larger installations "
|
||||
"serving multiple departments or many users would be better architected with "
|
||||
"10GbE networking. The performance of the running instances will be limited "
|
||||
"by these speeds. It is possible to design OpenStack environments that run a "
|
||||
"mix of networking capabilities. By utilizing the different interface speeds, "
|
||||
"the users of the OpenStack environment can choose networks that are fit for "
|
||||
"their purpose."
|
||||
msgstr ""
|
||||
"通用型OpenStack云，网络的需求其实帮助决定了其本身的性能能力。例如，小的部署环"
|
||||
"境使用千兆以太网(GbE)，大型的部署环境或者许多用户就要求使用10 GbE。运行着的实"
|
||||
"例性能收到了它们的速度限制。设计OpenStack环境，让它拥有可以运行混合网络的能力"
|
||||
"是可能的。通过利用不同速度的网卡，OpenStack环境的用户可以选择不同的网络去满足"
|
||||
"不同的目的。"
|
||||
|
||||
msgid ""
|
||||
"In a mixed hypervisor environment, specific aggregates of compute resources, "
|
||||
"each with defined capabilities, enable workloads to utilize software and "
|
||||
@ -2472,15 +2360,6 @@ msgid ""
|
||||
"applications to achieve suitable performance."
|
||||
msgstr "对于一些应用来说，可能需要引入第3方的缓存层以实现合意的性能。"
|
||||
|
||||
msgid ""
|
||||
"It's important to understand that user authentication requests include "
|
||||
"sensitive information including user names, passwords and authentication "
|
||||
"tokens. For this reason, placing the API services behind hardware that "
|
||||
"performs SSL termination is strongly recommended."
|
||||
msgstr ""
|
||||
"理解用户的认证需要一些敏感信息如用户名、密码和认证令牌是非常重要的。基于这个"
|
||||
"原因，强烈建议将认证的API服务隐藏在基于硬件的SSL终端之后。"
|
||||
|
||||
msgid "KVM (and QEMU)"
|
||||
msgstr "KVM (and QEMU)"
|
||||
|
||||
@ -2511,18 +2390,6 @@ msgstr ""
|
||||
"存储性能 (spindles/core), 内存可用性 (RAM/core), 网络带宽 (Gbps/core), 以及整"
|
||||
"个的CPU性能 (CPU/core)."
|
||||
|
||||
msgid ""
|
||||
"Knowing when and where to implement redundancy and high availability is "
|
||||
"directly affected by expectations set by the terms of the Service Level "
|
||||
"Agreements (SLAs). SLAs are contractual obligations that provide assurances "
|
||||
"for service availability. They define the levels of availability that drive "
|
||||
"the technical design, often with penalties for not meeting contractual "
|
||||
"obligations."
|
||||
msgstr ""
|
||||
"服务水平协议(SLA)的设定，就是知道何时以及何地实现冗余和高可用会直接影响到预"
|
||||
"期。SLA是提供保证服务可用性合同义务。他们定义的可用性级别驱动着技术的设计，若"
|
||||
"不能实现合同义务，则会得到相应的惩罚。"
|
||||
|
||||
msgid "LXC"
|
||||
msgstr "LXC"
|
||||
|
||||
@ -2650,17 +2517,6 @@ msgstr ""
|
||||
msgid "Maintainability"
|
||||
msgstr "可维护性"
|
||||
|
||||
msgid ""
|
||||
"Maintaining OpenStack installations requires a variety of technical skills. "
|
||||
"For example, if you are to incorporate features into an architecture and "
|
||||
"design that reduce the operations burden, it is advised to automate the "
|
||||
"operations functions. It may, however, be beneficial to use third party "
|
||||
"management companies with special expertise in managing OpenStack deployment."
|
||||
msgstr ""
|
||||
"维护OpenStack安装需要大量的技术技能。例如，如果用户既做架构有设计试图减轻运维"
|
||||
"的负担，那一定建议运维自动化。或许用第三方管理公司的专长去管理OpenStack部署也"
|
||||
"是不错的选择。"
|
||||
|
||||
msgid "Maintenance tasks"
|
||||
msgstr "维护任务："
|
||||
|
||||
@ -2933,10 +2789,6 @@ msgstr "网络建议的总结"
|
||||
msgid "Network redundancy protocols"
|
||||
msgstr "网络冗余协议"
|
||||
|
||||
msgid ""
|
||||
"Network security policies requirements need to be factored in to deployments."
|
||||
msgstr "网络安全规则的需求需要在部署时被处理。"
|
||||
|
||||
msgid "Network service offerings"
|
||||
msgstr "网络服务提供"
|
||||
|
||||
@ -3093,22 +2945,6 @@ msgstr ""
|
||||
msgid "On-demand and self-service application"
|
||||
msgstr "按需或自服务应用"
|
||||
|
||||
msgid ""
|
||||
"One of the benefits of OpenStack Object Storage is the ability to mix and "
|
||||
"match drives by making use of weighting within the swift ring. When "
|
||||
"designing your swift storage cluster, we recommend making use of the most "
|
||||
"cost effective storage solution available at the time. Many server chassis "
|
||||
"on the market can hold 60 or more drives in 4U of rack space, therefore we "
|
||||
"recommend maximizing the amount of storage per rack unit at the best cost "
|
||||
"per terabyte. Furthermore, we do not recommend the use of RAID controllers "
|
||||
"in an object storage node."
|
||||
msgstr ""
|
||||
"OpenStack对象存储一个亮点就是有混搭设备的能力，基于swift环的加权机制。当用户"
|
||||
"设计一个swift存储集群时，建议将大部分>的成本花在存储上，保证永久可用。市场上"
|
||||
"多数的服务器使用4U，可容纳60块甚至更多的磁盘驱动器，因此建议在1U空间内置放最"
|
||||
"多的驱动器，就是最好的每TB花费。进一步的建议，在对象存储节点上没必要使用RAID"
|
||||
"控制器。"
|
||||
|
||||
msgid ""
|
||||
"One potential solution to this problem is the implementation of storage "
|
||||
"systems designed for performance. Parallel file systems have previously "
|
||||
@ -3297,17 +3133,6 @@ msgstr ""
|
||||
"通常在OpenStack的设计中是不包括共享存储的，但是在高可用的设计中，为了特定的实"
|
||||
"现一些组件会用得到共享存储。"
|
||||
|
||||
msgid ""
|
||||
"OpenStack has two independent storage services to consider, each with its "
|
||||
"own specific design requirements and goals. In addition to services which "
|
||||
"provide storage as their primary function, there are additional design "
|
||||
"considerations with regard to compute and controller nodes which will affect "
|
||||
"the overall cloud architecture."
|
||||
msgstr ""
|
||||
"OpenStack有两个独立的存储服务需要考虑，且每个都拥有自己特别的设计需求和目标。"
|
||||
"除了提供存储服务是他们的主要功能之外，在整个云架构中，需要额外考虑的是它们对"
|
||||
"计算/控制节点的影响。"
|
||||
|
||||
msgid "OpenStack hosted SDN controller: <placeholder-1/>"
|
||||
msgstr "OpenStack 上运行 SDN 控制器：<placeholder-1/>"
|
||||
|
||||
@ -3433,15 +3258,6 @@ msgstr "覆盖网络"
|
||||
msgid "Performance"
|
||||
msgstr "性能"
|
||||
|
||||
msgid ""
|
||||
"Performance of an OpenStack deployment is dependent on a number of factors "
|
||||
"related to the infrastructure and controller services. The user requirements "
|
||||
"can be split into general network performance, performance of compute "
|
||||
"resources, and performance of storage systems."
|
||||
msgstr ""
|
||||
"OpenStack的性能取决于和基础设施有关的因素的多少以及控制器服务的多少。按照用户"
|
||||
"需求性能可归类为通用网络性能，计算资源性能，以及存储系统性能。"
|
||||
|
||||
msgid ""
|
||||
"Performance of the controller services is not limited to processing power, "
|
||||
"but restrictions may emerge in serving concurrent users. Ensure that the "
|
||||
@ -3705,26 +3521,6 @@ msgstr "资源容量"
|
||||
msgid "Response time to the Compute API"
|
||||
msgstr "计算API的响应时间"
|
||||
|
||||
msgid ""
|
||||
"Revenue opportunities for a cloud will vary greatly based on the intended "
|
||||
"use case of that particular cloud. Some general purpose clouds are built for "
|
||||
"commercial customer facing products, but there are alternatives that might "
|
||||
"make the general purpose cloud the right choice. For example, a small cloud "
|
||||
"service provider (CSP) might want to build a general purpose cloud rather "
|
||||
"than a massively scalable cloud because they do not have the deep financial "
|
||||
"resources needed, or because they do not, or will not, know in advance the "
|
||||
"purposes for which their customers are going to use the cloud. For some "
|
||||
"users, the advantages cloud itself offers mean an enhancement of revenue "
|
||||
"opportunity. For others, the fact that a general purpose cloud provides only "
|
||||
"baseline functionality will be a disincentive for use, leading to a "
|
||||
"potential stagnation of potential revenue opportunities."
|
||||
msgstr ""
|
||||
"赢利空间对于云来说是个最基本的义务。一些通用型云为商业客户构建产品，但也有替"
|
||||
"代品，可能使通用云的正确选择。例如，一个小型的云服务提供商(CSP)会构建一个通用"
|
||||
"云而放弃大规模的扩展云，也许是因为没有足够的财力支撑，有或许是因为无法得知客"
|
||||
"户使用云的目的是什么。对于一些用户来说，高级云本身就意味着赢利。但是另外一些"
|
||||
"用户，通用型云所提供的基本功能会阻碍使用，导致潜在的收入机会的停滞。"
|
||||
|
||||
msgid "Revenue opportunity"
|
||||
msgstr "赢利空间"
|
||||
|
||||
@ -3779,9 +3575,6 @@ msgstr ""
|
||||
"能够分析当前或者目标 OpenStack 设计中的各种不同，并确定哪些地方将会出现潜在的"
|
||||
"冲突或者还存在差距。"
|
||||
|
||||
msgid "SLA terms that will affect the design include:"
|
||||
msgstr "影响设计的SLA术语包括："
|
||||
|
||||
msgid "SUSE Linux Enterprise Server (SLES)"
|
||||
msgstr "SUSE Linux Enterprise Server (SLES)"
|
||||
|
||||
@ -4253,20 +4046,6 @@ msgstr ""
|
||||
"href=\"https://wiki.openstack.org/wiki/TripleO\"> https://wiki.openstack.org/"
|
||||
"wiki/TripleO</link> 了解该项目的更多信息。"
|
||||
|
||||
msgid ""
|
||||
"The ability to deliver services or products within a flexible time frame is "
|
||||
"a common business factor when building a general purpose cloud. In today's "
|
||||
"high-speed business world, the ability to deliver a product in six months "
|
||||
"instead of two years is a driving force behind the decision to build general "
|
||||
"purpose clouds. General purpose clouds allow users to self-provision and "
|
||||
"gain access to compute, network, and storage resources on-demand thus "
|
||||
"decreasing time to market."
|
||||
msgstr ""
|
||||
"当构建一个通用型云时，有能力在灵活的时间内交付服务或产品，是业务普遍的一个情"
|
||||
"形。在今天高速发展的商务世界里，拥有在6个月内交付一款产品去替代2年完成的能"
|
||||
"力，这驱动着背后的决策者们决定构建通用型云。通用型云实现用户自服务，按需求获"
|
||||
"得访问计算、网络、存储资源，这将大大节省上线时间。"
|
||||
|
||||
msgid "The author team includes:"
|
||||
msgstr "作者团队成员有："
|
||||
|
||||
@ -4410,28 +4189,6 @@ msgstr ""
|
||||
"这包括能够提供集群、日志、监测及预警等的软件。在此目录什么因素决定选择什么软"
|
||||
"件包已经超出了本书的范围。"
|
||||
|
||||
msgid ""
|
||||
"The features offered through the OpenStack cloud platform determine the best "
|
||||
"choice of a hypervisor. As an example, for a general purpose cloud that "
|
||||
"predominantly supports a Microsoft-based migration, or is managed by staff "
|
||||
"that has a particular skill for managing certain hypervisors and operating "
|
||||
"systems, Hyper-V would be the best available choice. While the decision to "
|
||||
"use Hyper-V does not limit the ability to run alternative operating systems, "
|
||||
"be mindful of those that are deemed supported. Each different hypervisor "
|
||||
"also has their own hardware requirements which may affect the decisions "
|
||||
"around designing a general purpose cloud. For example, to utilize the live "
|
||||
"migration feature of VMware, vMotion, this requires an installation of "
|
||||
"vCenter/vSphere and the use of the ESXi hypervisor, which increases the "
|
||||
"infrastructure requirements."
|
||||
msgstr ""
|
||||
"通过OpenStack云平台提供的特性决定了选择最佳的hyperviosr。举个例子，要使通用型"
|
||||
"云主要支持基于微软的迁移，或工作人员>所管理的是需要特定技能的去管理hypervisor"
|
||||
"或操作系统，Hyper-V也许是最好的选择。即使是决定了使用Hyper-V，这也并不意味着"
|
||||
"不可以去管理相关的操作系统，要记得OpenStack是支持多种hypervisor的。在设计通用"
|
||||
"型用时需要考虑到不同的hypervisor有他们特定的硬件需>求。例如欲整合VMware的特"
|
||||
"性：活迁移，那么就需要安装安装vMotion,给ESXi hypervisor所使用的VCenter/"
|
||||
"vSphere，这即是增加的基础设施需求。"
|
||||
|
||||
msgid ""
|
||||
"The following user considerations are written from the perspective of the "
|
||||
"cloud builder, not from the perspective of the end user."
|
||||
@ -4494,15 +4251,6 @@ msgstr ""
|
||||
"服务控制单一region中的存储资源，且这些资源须在统一存储网络中。和OpenStack计算"
|
||||
"服务一样，OpenStack块存储服务同样支持可用区域的构造，用于往下拆分存储资源。"
|
||||
|
||||
msgid ""
|
||||
"The management security domain is where services interact. Sometimes "
|
||||
"referred to as the \"control plane\", the networks in this domain transport "
|
||||
"confidential data such as configuration parameters, user names, and "
|
||||
"passwords. In most deployments this domain is considered trusted."
|
||||
msgstr ""
|
||||
"管理安全域即是服务交互的集中地，想一下“控制面板”，在此域中网络传输的都是机密"
|
||||
"的数据，比如配置参数、用户名称、密码等。多数部署此域为信任的。"
|
||||
|
||||
msgid ""
|
||||
"The management tools used for Ubuntu and Kinstance differ from the "
|
||||
"management tools for VMware vSphere. Although both OS and hypervisor "
|
||||
@ -4606,15 +4354,6 @@ msgid ""
|
||||
"different:"
|
||||
msgstr "升级多区域环境的流程没有什么特别的不一样："
|
||||
|
||||
msgid ""
|
||||
"The public security domain is an entirely untrusted area of the cloud "
|
||||
"infrastructure. It can refer to the Internet as a whole or simply to "
|
||||
"networks over which you have no authority. This domain should always be "
|
||||
"considered untrusted."
|
||||
msgstr ""
|
||||
"公有安全域对于云基础设施是完全不可信任的区域。正如将内部暴露给整个互联网，或"
|
||||
"者是没有认证的简单网络。此域一定不可以被信任。"
|
||||
|
||||
msgid ""
|
||||
"The relative purchase price of the hardware weighted against the level of "
|
||||
"design effort needed to build the system."
|
||||
@ -4706,21 +4445,6 @@ msgstr ""
|
||||
msgid "These security domains are:"
|
||||
msgstr "这些安全域有："
|
||||
|
||||
msgid ""
|
||||
"These security domains can be mapped to an OpenStack deployment "
|
||||
"individually, or combined. For example, some deployment topologies combine "
|
||||
"both guest and data domains onto one physical network, whereas in other "
|
||||
"cases these networks are physically separated. In each case, the cloud "
|
||||
"operator should be aware of the appropriate security concerns. Security "
|
||||
"domains should be mapped out against your specific OpenStack deployment "
|
||||
"topology. The domains and their trust requirements depend upon whether the "
|
||||
"cloud instance is public, private, or hybrid."
|
||||
msgstr ""
|
||||
"这些安全域可以映射给分开的OpenStack部署，也可以是合并的。例如，一些部署的拓扑"
|
||||
"合并了客户机和数据域在同一物理网络，其他一些情况的网络是物理分离的。无论那种"
|
||||
"情况，云运维人员必须意识到适当的安全问题。安全域须制定出针对特定的OpenStack部"
|
||||
"署拓扑。所谓的域和其信任的需求取决于云的实例是公有的，私有的，还是混合的。"
|
||||
|
||||
msgid ""
|
||||
"Think efficiency: Inefficient designs will not scale. Efficient designs "
|
||||
"become cheaper as they scale. Kill off unneeded components or capacity."
|
||||
@ -4819,21 +4543,6 @@ msgstr ""
|
||||
"数据复制多少份保存(默认情况是3份)。每份复制的数据最好独立的可用区域中，有独立"
|
||||
"的电源、冷却设备以及网络资源。"
|
||||
|
||||
msgid ""
|
||||
"To be able to support and maintain an installation, OpenStack cloud "
|
||||
"management requires operations staff to understand and comprehend design "
|
||||
"architecture content. The operations and engineering staff skill level, and "
|
||||
"level of separation, are dependent on size and purpose of the installation. "
|
||||
"Large cloud service providers, or telecom providers, are more likely to be "
|
||||
"managed by a specially trained, dedicated operations organization. Smaller "
|
||||
"implementations are more likely to rely on support staff that need to take "
|
||||
"on combined engineering, design and operations functions."
|
||||
msgstr ""
|
||||
"为了能够在安装之后能够支持和维护，OpenStack云管理需要运维人员理解设计架构内"
|
||||
"容。运维人员和工程师人员的技能级别，以及他们之间的界限，依赖于安装的规模大小"
|
||||
"和目的。大型的云服务提供商或者电信运营商，会有针对性的培训，专门的运维部门，"
|
||||
"小型的实现的话，支持人员通常是工程师、设计师、和运维人员的合体。"
|
||||
|
||||
msgid ""
|
||||
"To effectively run cloud installations, initial downtime planning includes "
|
||||
"creating processes and architectures that support the following:"
|
||||
@ -4882,23 +4591,6 @@ msgstr "考虑的主题有："
|
||||
msgid "Tunable networking components"
|
||||
msgstr "可调联网组件"
|
||||
|
||||
msgid ""
|
||||
"Typically used for compute instance-to-instance traffic, the guest security "
|
||||
"domain handles compute data generated by instances on the cloud but not "
|
||||
"services that support the operation of the cloud, such as API calls. Public "
|
||||
"cloud providers and private cloud providers who do not have stringent "
|
||||
"controls on instance use or who allow unrestricted Internet access to "
|
||||
"instances should consider this domain to be untrusted. Private cloud "
|
||||
"providers may want to consider this network as internal and therefore "
|
||||
"trusted only if they have controls in place to assert that they trust "
|
||||
"instances and all their tenants."
|
||||
msgstr ""
|
||||
"典型的用户计算服务中的实例对实际的互联互通，客户安全域，在云中掌握着由实例生"
|
||||
"成的计算机数据，但是不可以通过云来访问，包括应用程序接口调用。公有云或私有云"
|
||||
"提供商不会严格的控制实例的使用，以及谁受限访问互联网，所以应指定此域是不可信"
|
||||
"任的。或许私有云提供商可以稍宽松点，因为是内部网络，还有就是它可以控制所有的"
|
||||
"实例和租户。"
|
||||
|
||||
msgid "Ubuntu"
|
||||
msgstr "Ubuntu"
|
||||
|
||||
@ -5079,17 +4771,6 @@ msgstr "虚拟化网络拓扑"
|
||||
msgid "Voice over IP (VoIP)"
|
||||
msgstr "IP 语音(VoIP)"
|
||||
|
||||
msgid ""
|
||||
"We do not recommended investing in enterprise class drives for an OpenStack "
|
||||
"Object Storage cluster. The consistency and partition tolerance "
|
||||
"characteristics of OpenStack Object Storage will ensure that data stays up "
|
||||
"to date and survives hardware faults without the use of any specialized data "
|
||||
"replication devices."
|
||||
msgstr ""
|
||||
"我们并不建议为OpenStack对象存储投资企业级的设备。OpenStack对象存储的一致性和"
|
||||
"分区容错保证的数据的更新，即使是在硬件损坏的情况下仍能保证数据可用，而这都无"
|
||||
"须特别的数据复制设备。"
|
||||
|
||||
msgid ""
|
||||
"We recommend building a development and operations organization that is "
|
||||
"responsible for creating desired features, diagnosing and resolving issues, "
|
||||
@ -5207,27 +4888,6 @@ msgstr ""
|
||||
"性，所以复制数据将会影响到整个系统的性能。在此例中，存储网络使用10 GbE(或更"
|
||||
"高)网络是我们所建议的。"
|
||||
|
||||
msgid ""
|
||||
"When deploying OpenStack in an enterprise as a private cloud it is usually "
|
||||
"behind the firewall and within the trusted network alongside existing "
|
||||
"systems. Users of the cloud are, traditionally, employees that are bound by "
|
||||
"the security requirements set forth by the company. This tends to push most "
|
||||
"of the security domains towards a more trusted model. However, when "
|
||||
"deploying OpenStack in a public facing role, no assumptions can be made and "
|
||||
"the attack vectors significantly increase. For example, the API endpoints, "
|
||||
"along with the software behind them, become vulnerable to bad actors wanting "
|
||||
"to gain unauthorized access or prevent access to services, which could lead "
|
||||
"to loss of data, functionality, and reputation. These services must be "
|
||||
"protected against through auditing and appropriate filtering."
|
||||
msgstr ""
|
||||
"在一个企业部署OpenStack为私有云，通常是安置在防火墙之后，和原来的系统一并认为"
|
||||
"是可信任网络。云的用户即是原来的员工，由公司本来的安全需求所约束。这导致推动"
|
||||
"大部分的安全域趋向信任模式。但是，当部署OpenStack为面向公用的角色时，不要心存"
|
||||
"侥幸，它被攻击的几率大大增加。例如，应用程序接口端点，以及其背后的软件，很容"
|
||||
"易成为一些坏人下手的地方，获得未经授权的访问服务或者阻止其他人访问正常的服"
|
||||
"务，这可能会导致丢失数据、程序失效，乃至名声。这些服务必须被保护，通过审计以"
|
||||
"及适当的过滤来实现。"
|
||||
|
||||
msgid ""
|
||||
"When designing OpenStack Block Storage resource nodes, it is helpful to "
|
||||
"understand the workloads and requirements that will drive the use of block "
|
||||
|
||||
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
@ -1,7 +1,7 @@
|
||||
msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: PACKAGE VERSION\n"
|
||||
"POT-Creation-Date: 2015-09-04 06:18+0000\n"
|
||||
"POT-Creation-Date: 2015-09-18 06:19+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"
|
||||
@ -1711,123 +1711,127 @@ msgstr ""
|
||||
msgid "CentOS 7 images"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml:31(title)
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml:30(para)
|
||||
msgid "In a CentOS image, the login account is <literal>centos</literal>."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml:34(title)
|
||||
msgid "CirrOS (test) images"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml:32(para)
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml:35(para)
|
||||
msgid "CirrOS is a minimal Linux distribution that was designed for use as a test image on clouds such as OpenStack Compute. You can download a CirrOS image in various formats from the <link xlink:href=\"https://download.cirros-cloud.net\">CirrOS download page</link>."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml:41(para)
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml:44(para)
|
||||
msgid "In a CirrOS image, the login account is <literal>cirros</literal>. The password is <literal>cubswin:)</literal>"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml:36(para)
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml:39(para)
|
||||
msgid "If your deployment uses QEMU or KVM, we recommend using the images in qcow2 format. The most recent 64-bit qcow2 image as of this writing is <link xlink:href=\"http://download.cirros-cloud.net/0.3.4/cirros-0.3.4-x86_64-disk.img\">cirros-0.3.4-x86_64-disk.img</link>. <placeholder-1/>"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml:47(title)
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml:50(title)
|
||||
msgid "Official Ubuntu images"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml:48(para)
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml:51(para)
|
||||
msgid "Canonical maintains an <link xlink:href=\"http://cloud-images.ubuntu.com/\">official set of Ubuntu-based images</link>."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml:50(para)
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml:53(para)
|
||||
msgid "Images are arranged by Ubuntu release, and by image release date, with \"current\" being the most recent. For example, the page that contains the most recently built image for Ubuntu 14.04 \"Trusty Tahr\" is <link xlink:href=\"http://cloud-images.ubuntu.com/trusty/current/\">http://cloud-images.ubuntu.com/trusty/current/</link>. Scroll to the bottom of the page for links to images that can be downloaded directly."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml:60(para)
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml:63(para)
|
||||
msgid "In an Ubuntu cloud image, the login account is <literal>ubuntu</literal>."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml:56(para)
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml:59(para)
|
||||
msgid "If your deployment uses QEMU or KVM, we recommend using the images in qcow2 format. The most recent version of the 64-bit QCOW2 image for Ubuntu 14.04 is <link xlink:href=\"http://uec-images.ubuntu.com/trusty/current/trusty-server-cloudimg-amd64-disk1.img\">trusty-server-cloudimg-amd64-disk1.img</link>.<placeholder-1/>"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml:65(title)
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml:68(title)
|
||||
msgid "Official Red Hat Enterprise Linux images"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml:66(para)
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml:69(para)
|
||||
msgid "Red Hat maintains official Red Hat Enterprise Linux cloud images. A valid Red Hat Enterprise Linux subscription is required to download these images."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml:75(link)
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml:78(link)
|
||||
msgid "Red Hat Enterprise Linux 7 KVM Guest Image"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml:81(link)
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml:84(link)
|
||||
msgid "Red Hat Enterprise Linux 6 KVM Guest Image"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml:86(para)
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml:89(para)
|
||||
msgid "In a RHEL image, the login account is <literal>cloud-user</literal>."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml:92(title)
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml:95(title)
|
||||
msgid "Official Fedora images"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml:99(para)
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml:102(para)
|
||||
msgid "In a Fedora image, the login account is <literal>fedora</literal>."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml:93(para)
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml:96(para)
|
||||
msgid "The Fedora project maintains a list of official cloud images at <link xlink:href=\"https://getfedora.org/en/cloud/download/\"/>. The images include the <systemitem class=\"process\">cloud-init</systemitem> utility to support key and user data injection. The default user name is <systemitem class=\"username\">fedora</systemitem>. <placeholder-1/>"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml:103(title)
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml:106(title)
|
||||
msgid "Official openSUSE and SLES images"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml:104(para)
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml:107(para)
|
||||
msgid "SUSE provides images for <link xlink:href=\"http://download.opensuse.org/repositories/Cloud:/Images:/\">openSUSE</link>. For SUSE Linux Enterprise Server (SLES), custom images can be built with a web-based tool called <link xlink:href=\"http://susestudio.com\">SUSE Studio</link>. SUSE Studio can also be used to build custom openSUSE images."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml:110(title)
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml:113(title)
|
||||
msgid "Official Debian images"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml:111(para)
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml:114(para)
|
||||
msgid "Since January 2015, <link xlink:href=\"http://cdimage.debian.org/cdimage/openstack/\">Debian provides images for direct download</link>. They are now made at the same time as the CD and DVD images of Debian. However, until Debian 8.0 (aka Jessie) is out, these images are the weekly built images of the testing distribution."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml:117(para)
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml:120(para)
|
||||
msgid "If you wish to build your own images of Debian 7.0 (aka Wheezy, the current stable release of Debian), you can use the package which is used to build the official Debian images. It is named <package>openstack-debian-images</package>, and it provides a simple script for building them. This package is available in Debian Unstable, Debian Jessie, and through the wheezy-backports repositories. To produce a Wheezy image, simply run: <placeholder-1/>"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml:125(para)
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml:128(para)
|
||||
msgid "If building the image for Wheezy, packages like <package>cloud-init</package>, <package>cloud-utils</package> or <package>cloud-initramfs-growroot</package> will be pulled from wheezy-backports. Also, the current version of <package>bootlogd</package> in Wheezy doesn't support logging to multiple consoles, which is needed so that both the OpenStack Dashboard console and the <placeholder-1/> console works. However, a <link xlink:href=\"http://archive.gplhost.com/debian/pool/juno-backports/main/s/sysvinit/bootlogd_2.88dsf-41+deb7u2_amd64.deb\"> fixed version is available from the non-official GPLHost repository</link>. To install it on top of the image, it is possible to use the <placeholder-2/> option of the <placeholder-3/> script, with this kind of script as parameter: <placeholder-4/>"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml:145(para)
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml:148(para)
|
||||
msgid "In a Debian image, the login account is <literal>admin</literal>."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml:149(title)
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml:152(title)
|
||||
msgid "Official images from other Linux distributions"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml:150(para)
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml:153(para)
|
||||
msgid "As of this writing, we are not aware of other distributions that provide images for download."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml:153(title)
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml:156(title)
|
||||
msgid "Rackspace Cloud Builders (multiple distros) images"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml:155(para)
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml:158(para)
|
||||
msgid "Rackspace Cloud Builders maintains a list of pre-built images from various distributions (Red Hat, CentOS, Fedora, Ubuntu). Links to these images can be found at <link xlink:href=\"https://github.com/rackerjoe/oz-image-build\">rackerjoe/oz-image-build on GitHub</link>."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml:161(title)
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml:164(title)
|
||||
msgid "Microsoft Windows images"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml:162(para)
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml:165(para)
|
||||
msgid "Cloudbase Solutions hosts an <link xlink:href=\"http://www.cloudbase.it/ws2012r2/\">OpenStack Windows Server 2012 Standard Evaluation image</link> that runs on Hyper-V, KVM, and XenServer/XCP."
|
||||
msgstr ""
|
||||
|
||||
|
||||
@ -6,10 +6,11 @@
|
||||
#
|
||||
#
|
||||
# OpenStack Infra <zanata@openstack.org>, 2015. #zanata
|
||||
# actionchen <chenqioulin_1983@163.com>, 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 05:24+0000\n"
|
||||
"MIME-Version: 1.0\n"
|
||||
"Content-Type: text/plain; charset=UTF-8\n"
|
||||
"Content-Transfer-Encoding: 8bit\n"
|
||||
@ -1184,6 +1185,17 @@ msgstr ""
|
||||
"作为替代的，你应该编辑 <filename>/etc/default/grub</filename> 文件并修改 "
|
||||
"<literal>GRUB_CMDLINE_LINUX_DEFAULT</literal> 的值： <placeholder-1/>"
|
||||
|
||||
msgid ""
|
||||
"If both the XenAPI agent and <package>cloud-init</package> are present in an "
|
||||
"image, <package>cloud-init</package> handles ssh-key injection. The system "
|
||||
"assumes <package>cloud-init</package> is present when the image has the "
|
||||
"<literal>cloud_init_installed </literal> property."
|
||||
msgstr ""
|
||||
"如果镜像内同时包含 XenAPI 和 <package>cloud-init</package> 包，"
|
||||
"<package>cloud-init</package>包处理ssh-key的注入。当镜像有 "
|
||||
"<literal>cloud_init_installed </literal> 属性的时候系统假设镜像已经安装"
|
||||
"<package>cloud-init</package> 包。"
|
||||
|
||||
msgid ""
|
||||
"If building the image for Wheezy, packages like <package>cloud-init</"
|
||||
"package>, <package>cloud-utils</package> or <package>cloud-initramfs-"
|
||||
@ -3291,6 +3303,17 @@ msgstr ""
|
||||
"在创建 Ubuntu 镜像时，<placeholder-1/> 必须明确的配置元数据源。OpenStack 元数"
|
||||
"据服务仿效 Amazon EC2 元数据服务。"
|
||||
|
||||
msgid ""
|
||||
"When converting an image file with Windows OS, ensure the virtio driver is "
|
||||
"installed. Otherwise, you will get a blue screen of death or BSOD when "
|
||||
"launching the image due to lack of the virtio driver. Another option is to "
|
||||
"set the image properties as below when you update the image in glance to "
|
||||
"avoid this issue, but it will reduce performance significantly."
|
||||
msgstr ""
|
||||
"当转换一个Windows系统的镜像文件时，需确保镜像内系统已安装好virtio驱动。否则，"
|
||||
"在你启动虚拟机时会由于缺少virtio驱动遇到蓝屏死机。另外避免这个问题的方法是按"
|
||||
"如下命令通过更新glance服务中镜像属性，但是这个方法会明显的降低磁盘性能。"
|
||||
|
||||
msgid ""
|
||||
"When creating Block Storage volumes from images, also consider your "
|
||||
"configured image properties. If you alter the core image properties, you "
|
||||
|
||||
@ -8,7 +8,7 @@ msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: Networking Guide 0.9\n"
|
||||
"Report-Msgid-Bugs-To: \n"
|
||||
"POT-Creation-Date: 2015-09-15 06:28+0000\n"
|
||||
"POT-Creation-Date: 2015-09-18 06:20+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"
|
||||
@ -1644,7 +1644,7 @@ msgstr ""
|
||||
#: ../misc_add_ha_for_DHCP.rst:10
|
||||
msgid ""
|
||||
"FIXME: Content needs to be written; see DHCP agents (http://docs.openstack."
|
||||
"org/admin-guide-cloud/content/app_demo_multi_dhcp_agents.html)"
|
||||
"org/admin-guide-cloud/networking_multi-dhcp-agents.html)"
|
||||
msgstr ""
|
||||
|
||||
# #-#-#-#-# adv_config_FwaaS.pot (Networking Guide 0.9) #-#-#-#-#
|
||||
@ -4526,9 +4526,11 @@ msgid ""
|
||||
"change the behavior."
|
||||
msgstr ""
|
||||
|
||||
# #-#-#-#-# adv_config_FwaaS.pot (Networking Guide 0.9) #-#-#-#-#
|
||||
# #-#-#-#-# adv_config_LBaaS.pot (Networking Guide 0.9) #-#-#-#-#
|
||||
#: ../adv_config_FwaaS.rst:5 ../adv_config_LBaaS.rst:5
|
||||
#: ../adv_config_FwaaS.rst:5
|
||||
msgid "See the following URL:"
|
||||
msgstr ""
|
||||
|
||||
#: ../adv_config_LBaaS.rst:5
|
||||
msgid "See the following URLs:"
|
||||
msgstr ""
|
||||
|
||||
@ -4585,8 +4587,8 @@ msgstr ""
|
||||
|
||||
#: ../config_ml2_plug_in.rst:28
|
||||
msgid ""
|
||||
"Similar info in: http://docs.openstack.org/admin-guide-cloud/content/tenant-"
|
||||
"provider-networks.html"
|
||||
"Similar info in: http://docs.openstack.org/admin-guide-cloud/networking_adv-"
|
||||
"features.html#provider-networks"
|
||||
msgstr ""
|
||||
|
||||
#: ../adv_config_ipv6.rst:36
|
||||
@ -7501,35 +7503,34 @@ msgid ""
|
||||
"the exclude_devices parameter as follows:"
|
||||
msgstr ""
|
||||
|
||||
#: ../adv_config_FwaaS.rst:10
|
||||
msgid "http://docs.openstack.org/admin-guide-cloud/content/fwaas.html"
|
||||
msgstr ""
|
||||
|
||||
#: ../adv_config_FwaaS.rst:7
|
||||
msgid ""
|
||||
"http://docs.openstack.org/admin-guide-cloud/content/install_neutron-fwaas-"
|
||||
"agent.html"
|
||||
msgstr ""
|
||||
|
||||
#: ../adv_config_LBaaS.rst:11
|
||||
msgid ""
|
||||
"http://docs.openstack.org/admin-guide-cloud/content/install_neutron-lbaas-"
|
||||
"agent.html"
|
||||
msgstr ""
|
||||
|
||||
#: ../adv_config_LBaaS.rst:9
|
||||
msgid "http://docs.openstack.org/admin-guide-cloud/content/lbaas_workflow.html"
|
||||
"http://docs.openstack.org/admin-guide-cloud/networking_adv-features."
|
||||
"html#basic-load-balancer-as-a-service-operations"
|
||||
msgstr ""
|
||||
|
||||
#: ../adv_config_operational.rst:10
|
||||
msgid ""
|
||||
"http://docs.openstack.org/admin-guide-cloud/content/section_adv_logging.html"
|
||||
"http://docs.openstack.org/admin-guide-cloud/networking_adv-operational-"
|
||||
"features.html#logging-settings"
|
||||
msgstr ""
|
||||
|
||||
#: ../adv_config_LBaaS.rst:9
|
||||
msgid ""
|
||||
"http://docs.openstack.org/admin-guide-cloud/networking_config-agents."
|
||||
"html#configure-load-balancer-as-a-service-lbaas"
|
||||
msgstr ""
|
||||
|
||||
#: ../adv_config_FwaaS.rst:7
|
||||
msgid ""
|
||||
"http://docs.openstack.org/admin-guide-cloud/networking_introduction."
|
||||
"html#firewall-as-a-service-fwaas-overview"
|
||||
msgstr ""
|
||||
|
||||
#: ../adv_config_LBaaS.rst:7
|
||||
msgid ""
|
||||
"http://docs.openstack.org/admin-guide-cloud/content/section_lbaas-overview."
|
||||
"html"
|
||||
"http://docs.openstack.org/admin-guide-cloud/networking_introduction."
|
||||
"html#load-balancer-as-a-service-lbaas-overview"
|
||||
msgstr ""
|
||||
|
||||
#: ../adv_config_debugging.rst:24
|
||||
|
||||
@ -16,7 +16,7 @@ msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: Admin User Guide 1.0.0\n"
|
||||
"Report-Msgid-Bugs-To: \n"
|
||||
"POT-Creation-Date: 2015-09-16 12:29+0000\n"
|
||||
"POT-Creation-Date: 2015-09-18 05:24+0000\n"
|
||||
"MIME-Version: 1.0\n"
|
||||
"Content-Type: text/plain; charset=UTF-8\n"
|
||||
"Content-Transfer-Encoding: 8bit\n"
|
||||
@ -1052,17 +1052,6 @@ 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/content/>`_."
|
||||
msgstr ""
|
||||
"フレーバーは、インスタンスを起動するために使用できるコンピュートホストを決め"
|
||||
"ることもできます。フレーバーのカスタマイズの詳細は、`OpenStack Cloud "
|
||||
"Administrator Guide <http://docs.openstack.org/admin-guide-cloud/content/>`_ "
|
||||
"を参照してください。"
|
||||
|
||||
msgid "For a list of optional parameters, run this command::"
|
||||
msgstr "オプションパラメーターの一覧は、このコマンドを実行します。"
|
||||
|
||||
@ -1081,17 +1070,6 @@ 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/content/>`_. 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/content/>`_ を参照してください。Floating IP アドレスは、"
|
||||
"OpenStack Networking のデフォルトで作成されません。"
|
||||
|
||||
msgid "For each item in the list, run the swift **download -o -** command."
|
||||
msgstr "一覧の各項目に対して、swift **download -o -** コマンドを実行します。"
|
||||
|
||||
@ -1117,15 +1095,6 @@ 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/content/"
|
||||
"customize-flavors.html>`__."
|
||||
msgstr ""
|
||||
"メタデータキーのサポートに関する詳細は、`OpenStack Cloud Administrator Guide "
|
||||
"<http://docs.openstack.org/admin-guide-cloud/content/customize-flavors."
|
||||
"html>`__ を参照してください。"
|
||||
|
||||
msgid "For information about the:"
|
||||
msgstr "詳細は以下のとおりです。"
|
||||
|
||||
@ -1291,28 +1260,6 @@ 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/content/customize-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/content/customize-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 "
|
||||
|
||||
@ -8,7 +8,7 @@ msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: Admin User Guide 1.0.0\n"
|
||||
"Report-Msgid-Bugs-To: \n"
|
||||
"POT-Creation-Date: 2015-09-12 06:18+0000\n"
|
||||
"POT-Creation-Date: 2015-09-18 06:20+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"
|
||||
@ -1092,7 +1092,7 @@ 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/content/>`_."
|
||||
"cloud/compute-flavors.html>`_."
|
||||
msgstr ""
|
||||
|
||||
#: ../cli_manage_flavors.rst:103 ../cli_manage_flavors.rst:125
|
||||
@ -1116,8 +1116,8 @@ msgstr ""
|
||||
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/content/>`_. No floating IP addresses "
|
||||
"are created by default in OpenStack Networking."
|
||||
"docs.openstack.org/admin-guide-cloud/networking_adv-features.html>`_ . No "
|
||||
"floating IP addresses are created by default in OpenStack Networking."
|
||||
msgstr ""
|
||||
|
||||
#: ../analyzing-log-files-with-swift-cli.rst:176
|
||||
@ -1157,8 +1157,8 @@ msgstr ""
|
||||
#: ../dashboard_manage_flavors.rst:148
|
||||
msgid ""
|
||||
"For information about supporting metadata keys, see the `OpenStack Cloud "
|
||||
"Administrator Guide <http://docs.openstack.org/admin-guide-cloud/content/"
|
||||
"customize-flavors.html>`__."
|
||||
"Administrator Guide <http://docs.openstack.org/admin-guide-cloud/compute-"
|
||||
"flavors.html>`__."
|
||||
msgstr ""
|
||||
|
||||
#: ../cli_admin_manage_stacks.rst:19
|
||||
@ -1309,8 +1309,7 @@ msgid ""
|
||||
"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/content/customize-flavors."
|
||||
"html>`__."
|
||||
"<http://docs.openstack.org/admin-guide-cloud/compute-flavors.html>`__."
|
||||
msgstr ""
|
||||
|
||||
#: ../dashboard_manage_host_aggregates.rst:72
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user