Imported Translations from Transifex
Change-Id: Idd6ca5efec90570d9270f449bd5c207ab9cea23b
This commit is contained in:
OpenStack Proposal Bot
parent
95c796bf5d
commit
d51cee9d37
@ -1,7 +1,7 @@
|
||||
msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: PACKAGE VERSION\n"
|
||||
"POT-Creation-Date: 2014-07-22 06:10+0000\n"
|
||||
"POT-Creation-Date: 2014-07-25 06:08+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"
|
||||
@ -6507,7 +6507,7 @@ msgid "Configure multiple-storage back ends"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/blockstorage/section_multi_backend.xml:8(para)
|
||||
msgid "When you configure multiple-storage back ends, you can create several back-end storage solutions that serve the same OpenStack Compute configuration and one <systemitem class=\"service\">cinder-volume</systemitem> is launched for each back end."
|
||||
msgid "When you configure multiple-storage back ends, you can create several back-end storage solutions that serve the same OpenStack Compute configuration and one <systemitem class=\"service\">cinder-volume</systemitem> is launched for each back-end storage or back-end storage pool."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/blockstorage/section_multi_backend.xml:12(para)
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: PACKAGE VERSION\n"
|
||||
"POT-Creation-Date: 2014-07-24 06:08+0000\n"
|
||||
"POT-Creation-Date: 2014-07-25 06:08+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"
|
||||
@ -246,7 +246,7 @@ msgid "NoSQL - A NoSQL or Not Only SQL database provides a mechanism for storage
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/ch_glossary.xml:374(para)
|
||||
msgid "Open vSwitch - Open vSwitch is a production quality, multilayer virtual switch licensed under the open source Apache 2.0 license. It is designed to enable massive network automation through programmatic extension, while still supporting standard management interfaces and protocols (e.g. NetFlow, sFlow, SPAN, RSPAN, CLI, LACP, 802.1ag)."
|
||||
msgid "Open vSwitch - Open vSwitch is a production quality, multilayer virtual switch licensed under the open source Apache 2.0 license. It is designed to enable massive network automation through programmatic extension, while still supporting standard management interfaces and protocols (for example NetFlow, sFlow, SPAN, RSPAN, CLI, LACP, 802.1ag)."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/ch_glossary.xml:383(para)
|
||||
@ -429,7 +429,7 @@ msgstr ""
|
||||
msgid "Compute Focused"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/ch_references.xml:8(title) ./doc/arch-design/compute_focus/section_prescriptive_examples_compute_focus.xml:115(title)
|
||||
#: ./doc/arch-design/ch_references.xml:8(title) ./doc/arch-design/compute_focus/section_prescriptive_examples_compute_focus.xml:121(title)
|
||||
msgid "References"
|
||||
msgstr ""
|
||||
|
||||
@ -663,71 +663,71 @@ msgstr ""
|
||||
|
||||
#. When image changes, this message will be marked fuzzy or untranslated for you.
|
||||
#. It doesn't matter what you translate it to: it's not used at all.
|
||||
#: ./doc/arch-design/multi_site/section_architecture_multi_site.xml:20(None)
|
||||
#: ./doc/arch-design/multi_site/section_architecture_multi_site.xml:21(None)
|
||||
msgid "@@image: '../images/Multi-Site_shared_keystone_horizon_swift1.png'; md5=c443da33089971595104cd918f40d339"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/multi_site/section_architecture_multi_site.xml:7(title) ./doc/arch-design/network_focus/section_architecture_network_focus.xml:7(title) ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:8(title) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:8(title) ./doc/arch-design/hybrid/section_architecture_hybrid.xml:8(title) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:7(title)
|
||||
#: ./doc/arch-design/multi_site/section_architecture_multi_site.xml:8(title) ./doc/arch-design/network_focus/section_architecture_network_focus.xml:7(title) ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:8(title) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:8(title) ./doc/arch-design/hybrid/section_architecture_hybrid.xml:8(title) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:7(title)
|
||||
msgid "Architecture"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/multi_site/section_architecture_multi_site.xml:8(para)
|
||||
#: ./doc/arch-design/multi_site/section_architecture_multi_site.xml:9(para)
|
||||
msgid "This graphic is a high level diagram of a multiple site OpenStack architecture. Each site is an OpenStack cloud but it may be necessary to architect the sites on different versions. For example, if the second site is intended to be a replacement for the first site, they would be different. Another common design would be a private OpenStack cloud with replicated site that would be used for high availability or disaster recovery. The most important design decision is how to configure the storage. It can be configured as a single shared pool or separate pools, depending on the user and technical requirements."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/multi_site/section_architecture_multi_site.xml:24(title)
|
||||
#: ./doc/arch-design/multi_site/section_architecture_multi_site.xml:25(title)
|
||||
msgid "OpenStack Services Architecture"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/multi_site/section_architecture_multi_site.xml:25(para)
|
||||
#: ./doc/arch-design/multi_site/section_architecture_multi_site.xml:26(para)
|
||||
msgid "The OpenStack Identity service, which is used by all other OpenStack components for authorization and the catalog of service endpoints, supports the concept of regions. A region is a logical construct that can be used to group OpenStack services that are in close proximity to one another. The concept of regions is flexible; it may can contain OpenStack service endpoints located within a distinct geographic region, or regions. It may be smaller in scope, where a region is a single rack within a data center or even a single blade chassis, with multiple regions existing in adjacent racks in the same data center."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/multi_site/section_architecture_multi_site.xml:35(para)
|
||||
#: ./doc/arch-design/multi_site/section_architecture_multi_site.xml:36(para)
|
||||
msgid "The majority of OpenStack components are designed to run within the context of a single region. The OpenStack Compute service is designed to manage compute resources within a region, with support for subdivisions of compute resources by using Availability Zones and Cells. The OpenStack Networking service can be used to manage network resources in the same broadcast domain or collection of switches that are linked. The OpenStack Block Storage service controls storage resources within a region with all storage resources residing on the same storage network. Like the OpenStack Compute service, the OpenStack Block Storage Service also supports the Availability Zone construct,which can be used to subdivide storage resources."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/multi_site/section_architecture_multi_site.xml:47(para)
|
||||
#: ./doc/arch-design/multi_site/section_architecture_multi_site.xml:48(para)
|
||||
msgid "The OpenStack Dashboard, OpenStack Identity Service, and OpenStack Object Storage services are components that can each be deployed centrally in order to serve multiple regions."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/multi_site/section_architecture_multi_site.xml:52(title) ./doc/arch-design/multi_site/section_user_requirements_multi_site.xml:152(para) ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:18(para) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:18(para)
|
||||
#: ./doc/arch-design/multi_site/section_architecture_multi_site.xml:53(title) ./doc/arch-design/multi_site/section_user_requirements_multi_site.xml:152(para) ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:18(para) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:18(para)
|
||||
msgid "Storage"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/multi_site/section_architecture_multi_site.xml:53(para)
|
||||
#: ./doc/arch-design/multi_site/section_architecture_multi_site.xml:54(para)
|
||||
msgid "With multiple OpenStack regions, having a single OpenStack Object Storage Service endpoint that delivers shared file storage for all regions is desirable. The Object Storage service internally replicates files to multiple nodes. The advantages of this are that, if a file placed into the Object Storage service is visible to all regions, it can be used by applications or workloads in any or all of the regions. This simplifies high availability failover and disaster recovery rollback."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/multi_site/section_architecture_multi_site.xml:61(para)
|
||||
#: ./doc/arch-design/multi_site/section_architecture_multi_site.xml:62(para)
|
||||
msgid "In order to scale the Object Storage service to meet the workload of multiple regions, multiple proxy workers are run and load-balanced, storage nodes are installed in each region, and the entire Object Storage Service can be fronted by an HTTP caching layer. This is done so client requests for objects can be served out of caches rather than directly from the storage modules themselves, reducing the actual load on the storage network. In addition to an HTTP caching layer, use a caching layer like Memcache to cache objects between the proxy and storage nodes."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/multi_site/section_architecture_multi_site.xml:70(para)
|
||||
#: ./doc/arch-design/multi_site/section_architecture_multi_site.xml:71(para)
|
||||
msgid "If the cloud is designed without a single Object Storage Service endpoint for multiple regions, and instead a separate Object Storage Service endpoint is made available in each region, applications are required to handle synchronization (if desired) and other management operations to ensure consistency across the nodes. For some applications, having multiple Object Storage Service endpoints located in the same region as the application may be desirable due to reduced latency, cross region bandwidth, and ease of deployment."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/multi_site/section_architecture_multi_site.xml:79(para)
|
||||
#: ./doc/arch-design/multi_site/section_architecture_multi_site.xml:80(para)
|
||||
msgid "For the Block Storage service, the most important decisions are the selection of the storage technology and whether or not a dedicated network is used to carry storage traffic from the storage service to the compute nodes."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/multi_site/section_architecture_multi_site.xml:85(title) ./doc/arch-design/compute_focus/section_tech_considerations_compute_focus.xml:413(para)
|
||||
#: ./doc/arch-design/multi_site/section_architecture_multi_site.xml:86(title) ./doc/arch-design/compute_focus/section_tech_considerations_compute_focus.xml:413(para)
|
||||
msgid "Networking"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/multi_site/section_architecture_multi_site.xml:86(para)
|
||||
#: ./doc/arch-design/multi_site/section_architecture_multi_site.xml:87(para)
|
||||
msgid "When connecting multiple regions together there are several design considerations. The overlay network technology choice determines how packets are transmitted between regions and how the logical network and addresses present to the application. If there are security or regulatory requirements, encryption should be implemented to secure the traffic between regions. For networking inside a region, the overlay network technology for tenant networks is equally important. The overlay technology and the network traffic of an application generates or receives can be either complementary or be at cross purpose. For example, using an overlay technology for an application that transmits a large amount of small packets could add excessive latency or overhead to each packet if not configured properly."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/multi_site/section_architecture_multi_site.xml:101(title)
|
||||
#: ./doc/arch-design/multi_site/section_architecture_multi_site.xml:102(title)
|
||||
msgid "Dependencies"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/multi_site/section_architecture_multi_site.xml:102(para)
|
||||
#: ./doc/arch-design/multi_site/section_architecture_multi_site.xml:103(para)
|
||||
msgid "The architecture for a multi-site installation of OpenStack is dependent on a number of factors. One major dependency to consider is storage. When designing the storage system, the storage mechanism needs to be determined. Once the storage type is determined, how it will be accessed is critical. For example, it is recommended that storage should utilize a dedicated network. Another concern is how the storage is configured to protect the data. For example, the recovery point objective (RPO) and the recovery time objective (RTO). How quickly can the recovery from a fault be completed, will determine how often the replication of data be required. Ensure that enough storage is allocated to support the data protection strategy."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/multi_site/section_architecture_multi_site.xml:114(para)
|
||||
#: ./doc/arch-design/multi_site/section_architecture_multi_site.xml:115(para)
|
||||
msgid "Networking decisions include the encapsulation mechanism that will be used for the tenant networks, how large the broadcast domains should be, and the contracted SLAs for the interconnects."
|
||||
msgstr ""
|
||||
|
||||
@ -1182,7 +1182,7 @@ msgid "Some possible use cases include:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/network_focus/section_introduction_network_focus.xml:21(para)
|
||||
msgid "Content Delivery Network: This could include streaming video, photographs or any other cloud based repository of data that is distributed to a large number of end users. Mass market streaming video will be very heavily affected by the network configurations that would affect latency, bandwidth, and the distribution of instances. Not all video streaming is consumer focused. For example, multicast videos (used for media, press conferences, corporate presentations, web conferencing services, etc.) can also utilize a content delivery network. Content delivery will be affected by the location of the video repository and its relationship to end users. Performance is also affected by network throughput of the backend systems, as well as the WAN architecture and the cache methodology."
|
||||
msgid "Content Delivery Network: This could include streaming video, photographs or any other cloud based repository of data that is distributed to a large number of end users. Mass market streaming video will be very heavily affected by the network configurations that would affect latency, bandwidth, and the distribution of instances. Not all video streaming is consumer focused. For example, multicast videos (used for media, press conferences, corporate presentations, web conferencing services, and so on) can also utilize a content delivery network. Content delivery will be affected by the location of the video repository and its relationship to end users. Performance is also affected by network throughput of the backend systems, as well as the WAN architecture and the cache methodology."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/network_focus/section_introduction_network_focus.xml:39(para)
|
||||
@ -2010,7 +2010,7 @@ msgid "As is the case with storage architecture, selecting a network architectur
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:403(para)
|
||||
msgid "As an example, selecting Cisco networking hardware implies that the architecture will be using Cisco networking software (IOS, NX-OS, etc.). Conversely, selecting Arista networking hardware means the network devices will use the Arista networking software called Extensible Operating System (EOS). In addition, there are more subtle design impacts that need to be considered. The selection of certain networking hardware (and therefore the networking software) could affect the management tools that can be used. There are exceptions to this; the rise of \"open\" networking software that supports a range of networking hardware means that there are instances where the relationship between networking hardware and networking software are not as tightly defined. An example of this type of software is Cumulus Linux, which is capable of running on a number of switch vendor’s hardware solutions."
|
||||
msgid "As an example, selecting Cisco networking hardware implies that the architecture will be using Cisco networking software like IOS or NX-OS. Conversely, selecting Arista networking hardware means the network devices will use the Arista networking software called Extensible Operating System (EOS). In addition, there are more subtle design impacts that need to be considered. The selection of certain networking hardware (and therefore the networking software) could affect the management tools that can be used. There are exceptions to this; the rise of \"open\" networking software that supports a range of networking hardware means that there are instances where the relationship between networking hardware and networking software are not as tightly defined. An example of this type of software is Cumulus Linux, which is capable of running on a number of switch vendor’s hardware solutions."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:419(para) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:404(para) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:268(para)
|
||||
@ -2435,31 +2435,31 @@ msgstr ""
|
||||
msgid "OpenStack Object Storage for serving static objects such as images."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_prescriptive_example_general_purpose.xml:60(para)
|
||||
msgid "<placeholder-1/>Running up to 140 web instances and the small number of MariaDB instances requires 292 vCPUs available, as well as 584 GB RAM. On a typical 1U server using dual-socket hex-core Intel CPUs with Hyperthreading, and assuming 2:1 CPU overcommit ratio, this would require 8 OpenStack Compute nodes."
|
||||
#: ./doc/arch-design/generalpurpose/section_prescriptive_example_general_purpose.xml:63(para)
|
||||
msgid "Running up to 140 web instances and the small number of MariaDB instances requires 292 vCPUs available, as well as 584 GB RAM. On a typical 1U server using dual-socket hex-core Intel CPUs with Hyperthreading, and assuming 2:1 CPU overcommit ratio, this would require 8 OpenStack Compute nodes."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_prescriptive_example_general_purpose.xml:68(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_prescriptive_example_general_purpose.xml:69(para)
|
||||
msgid "The web application instances run from local storage on each of the OpenStack Compute nodes. The web application instances are stateless, meaning that any of the instances can fail and the application will continue to function."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_prescriptive_example_general_purpose.xml:72(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_prescriptive_example_general_purpose.xml:73(para)
|
||||
msgid "MariaDB server instances store their data on shared enterprise storage, such as NetApp or Solidfire devices. If a MariaDB instance fails, storage would be expected to be re-attached to another instance and rejoined to the Galera cluster."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_prescriptive_example_general_purpose.xml:77(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_prescriptive_example_general_purpose.xml:78(para)
|
||||
msgid "Logs from the web application servers are shipped to OpenStack Object Storage for later processing and archiving."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_prescriptive_example_general_purpose.xml:80(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_prescriptive_example_general_purpose.xml:81(para)
|
||||
msgid "In this scenario, additional capabilities can be realized by moving static web content to be served from OpenStack Object Storage containers, and backing the OpenStack Image Service with OpenStack Object Storage. Note that an increase in OpenStack Object Storage means that network bandwidth needs to be taken in to consideration. It is best to run OpenStack Object Storage with network connections offering 10 GbE or better connectivity."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_prescriptive_example_general_purpose.xml:88(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_prescriptive_example_general_purpose.xml:89(para)
|
||||
msgid "There is also a potential to leverage the Orchestration and Telemetry OpenStack modules to provide an auto-scaling, orchestrated web application environment. Defining the web applications in Heat Orchestration Templates (HOT) would negate the reliance on the scripted Puppet solution currently employed."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_prescriptive_example_general_purpose.xml:94(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_prescriptive_example_general_purpose.xml:95(para)
|
||||
msgid "OpenStack Networking can be used to control hardware load balancers through the use of plug-ins and the Networking API. This would allow a user to control hardware load balance pools and instances as members in these pools, but their use in production environments must be carefully weighed against current stability."
|
||||
msgstr ""
|
||||
|
||||
@ -3966,19 +3966,19 @@ msgid "Although direct billing is not required, OpenStack Telemetry is used to p
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/compute_focus/section_prescriptive_examples_compute_focus.xml:110(para)
|
||||
msgid "Additional monitoring tools in use include Flume (http://flume.apache.org/), Elastic Search, Kibana (http://www.elasticsearch.org/overview/kibana/), and the CERN developed Lemon (http://lemon.web.cern.ch/lemon/index.shtml) project."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/compute_focus/section_prescriptive_examples_compute_focus.xml:116(para)
|
||||
msgid "The authors of the Architecture Design Guide would like to thank CERN for publicly documenting their OpenStack deployment in these resources, which formed the basis for this chapter:"
|
||||
msgid "Additional monitoring tools in use include <link href=\"http://flume.apache.org/\">Flume</link>, <link href=\"http://www.elasticsearch.org/\">Elastic Search</link>, <link href=\"http://www.elasticsearch.org/overview/kibana/\">Kibana</link>, and the CERN developed <link href=\"http://lemon.web.cern.ch/lemon/index.shtml\">Lemon</link> project."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/compute_focus/section_prescriptive_examples_compute_focus.xml:122(para)
|
||||
msgid "http://openstack-in-production.blogspot.fr/"
|
||||
msgid "The authors of the Architecture Design Guide would like to thank CERN for publicly documenting their OpenStack deployment in these resources, which formed the basis for this chapter:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/compute_focus/section_prescriptive_examples_compute_focus.xml:125(para)
|
||||
msgid "http://www.openstack.org/assets/presentation-media/Deep-Dive-into-the-CERN-Cloud-Infrastructure.pdf"
|
||||
#: ./doc/arch-design/compute_focus/section_prescriptive_examples_compute_focus.xml:128(link)
|
||||
msgid "http://openstack-in-production.blogspot.fr"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/compute_focus/section_prescriptive_examples_compute_focus.xml:133(link)
|
||||
msgid "Deep dive into the CERN Cloud Infrastructure"
|
||||
msgstr ""
|
||||
|
||||
#. When image changes, this message will be marked fuzzy or untranslated for you.
|
||||
|
||||
@ -7,9 +7,9 @@
|
||||
msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: OpenStack Manuals\n"
|
||||
"POT-Creation-Date: 2014-07-24 02:16+0000\n"
|
||||
"PO-Revision-Date: 2014-07-24 02:16+0000\n"
|
||||
"Last-Translator: openstackjenkins <jenkins@openstack.org>\n"
|
||||
"POT-Creation-Date: 2014-07-25 00:50+0000\n"
|
||||
"PO-Revision-Date: 2014-07-24 10:30+0000\n"
|
||||
"Last-Translator: Tomoyuki KATO <tomo@dream.daynight.jp>\n"
|
||||
"Language-Team: Japanese (http://www.transifex.com/projects/p/openstack-manuals-i18n/language/ja/)\n"
|
||||
"MIME-Version: 1.0\n"
|
||||
"Content-Type: text/plain; charset=UTF-8\n"
|
||||
@ -1875,11 +1875,11 @@ msgstr "ドキュメント変更履歴"
|
||||
|
||||
#: ./doc/common/section_dochistory.xml9(para)
|
||||
msgid "This version of the guide replaces and obsoletes all earlier versions."
|
||||
msgstr ""
|
||||
msgstr "このバージョンのガイドはすべての旧バージョンを置き換え、廃止します。"
|
||||
|
||||
#: ./doc/common/section_dochistory.xml10(para)
|
||||
msgid "The following table describes the most recent changes:"
|
||||
msgstr ""
|
||||
msgstr "以下の表はもっとも最近の変更点を記載しています。"
|
||||
|
||||
#: ./doc/common/section_cli_neutron_manage_networks.xml7(title)
|
||||
msgid "Create and manage networks"
|
||||
@ -5545,19 +5545,19 @@ msgstr "注意"
|
||||
|
||||
#: ./doc/common/section_conventions.xml9(para)
|
||||
msgid "Notices take these forms:"
|
||||
msgstr ""
|
||||
msgstr "注意には以下の種類があります。"
|
||||
|
||||
#: ./doc/common/section_conventions.xml11(para)
|
||||
msgid "A handy tip or reminder."
|
||||
msgstr ""
|
||||
msgstr "簡単なヒントや備忘録です。"
|
||||
|
||||
#: ./doc/common/section_conventions.xml14(para)
|
||||
msgid "Something you must be aware of before proceeding."
|
||||
msgstr ""
|
||||
msgstr "続行する前に注意する必要があるものです。"
|
||||
|
||||
#: ./doc/common/section_conventions.xml17(para)
|
||||
msgid "Critical information about the risk of data loss or security issues."
|
||||
msgstr ""
|
||||
msgstr "データ損失やセキュリティ問題のリスクに関する致命的な情報です。"
|
||||
|
||||
#: ./doc/common/section_conventions.xml21(title)
|
||||
msgid "Command prompts"
|
||||
@ -5566,20 +5566,20 @@ msgstr "コマンドプロンプト"
|
||||
#: ./doc/common/section_conventions.xml24(emphasis)
|
||||
#: ./doc/common/section_conventions.xml31(emphasis)
|
||||
msgid "<placeholder-1/> prompt"
|
||||
msgstr ""
|
||||
msgstr "<placeholder-1/> プロンプト"
|
||||
|
||||
#: ./doc/common/section_conventions.xml26(para)
|
||||
msgid ""
|
||||
"Any user, including the <literal>root</literal> user, can run commands that "
|
||||
"are prefixed with the <placeholder-1/> prompt."
|
||||
msgstr ""
|
||||
msgstr "<literal>root</literal> ユーザーを含むすべてのユーザーが、<placeholder-1/> プロンプトから始まるコマンドを実行できます。"
|
||||
|
||||
#: ./doc/common/section_conventions.xml33(para)
|
||||
msgid ""
|
||||
"The <literal>root</literal> user must run commands that are prefixed with "
|
||||
"the <placeholder-1/> prompt. You can also prefix these commands with the "
|
||||
"<placeholder-2/> command, if available, to run them."
|
||||
msgstr ""
|
||||
msgstr "<literal>root</literal> ユーザーは、<placeholder-1/> プロンプトから始まるコマンドを実行する必要があります。利用可能ならば、これらを実行するために、<placeholder-2/> コマンドを使用できます。"
|
||||
|
||||
#: ./doc/common/section_cli_glance_manage_images.xml8(title)
|
||||
msgid "Manage images"
|
||||
@ -6580,7 +6580,7 @@ msgstr ""
|
||||
|
||||
#: ./doc/common/section_cli_overview.xml109(td)
|
||||
msgid "Creates and manages Hadoop clusters on OpenStack."
|
||||
msgstr ""
|
||||
msgstr "OpenStack に Hadoop クラスターを作成、管理します。"
|
||||
|
||||
#: ./doc/common/section_cli_overview.xml113(para)
|
||||
msgid "An OpenStack <placeholder-1/> client is in development."
|
||||
@ -10235,38 +10235,38 @@ msgstr "サーバー名を取得するために、インスタンスを一覧表
|
||||
#: ./doc/common/section_cli_nova_manage_images.xml25(para)
|
||||
msgid ""
|
||||
"In this example, the instance is named <literal>myCirrosServer</literal>."
|
||||
msgstr ""
|
||||
msgstr "この例では、インスタンス名が <literal>myCirrosServer</literal> です。"
|
||||
|
||||
#: ./doc/common/section_cli_nova_manage_images.xml28(para)
|
||||
msgid "Use this instance to create a snapshot:"
|
||||
msgstr ""
|
||||
msgstr "スナップショットを作成するために、このインスタンスを使用します。"
|
||||
|
||||
#: ./doc/common/section_cli_nova_manage_images.xml30(para)
|
||||
msgid ""
|
||||
"The command creates a snapshot and automatically uploads the image to your "
|
||||
"repository."
|
||||
msgstr ""
|
||||
msgstr "このコマンドは、スナップショットを作成し、イメージをリポジトリーに自動的にアップロードします。"
|
||||
|
||||
#: ./doc/common/section_cli_nova_manage_images.xml33(para)
|
||||
msgid ""
|
||||
"For snapshots that you create from an instance that was booted from a "
|
||||
"volume:"
|
||||
msgstr ""
|
||||
msgstr "ボリュームから起動したインスタンスからスナップショットを作成する場合:"
|
||||
|
||||
#: ./doc/common/section_cli_nova_manage_images.xml37(para)
|
||||
msgid ""
|
||||
"The snapshot is based on the volume that is attached to the instance through"
|
||||
" the Block Storage service."
|
||||
msgstr ""
|
||||
msgstr "スナップショットが、Block Storage 経由でインスタンスに接続されているボリュームをベースにしています。"
|
||||
|
||||
#: ./doc/common/section_cli_nova_manage_images.xml41(para)
|
||||
msgid "No data is uploaded to the Image Service."
|
||||
msgstr ""
|
||||
msgstr "データが Image Service に何もアップロードされません。"
|
||||
|
||||
#: ./doc/common/section_cli_nova_manage_images.xml44(para)
|
||||
msgid ""
|
||||
"You can find information about the snapshot in the properties of the image."
|
||||
msgstr ""
|
||||
msgstr "イメージのプロパティにスナップショットに関する情報を見つけられます。"
|
||||
|
||||
#: ./doc/common/section_cli_nova_manage_images.xml91(para)
|
||||
msgid ""
|
||||
@ -12982,7 +12982,7 @@ msgstr "OpenStack API を使用するために、HTTP/1.1、RESTful ウェブサ
|
||||
|
||||
#: ./doc/common/ch_using_openstack_overview.xml40(title)
|
||||
msgid "Who should read this book?"
|
||||
msgstr ""
|
||||
msgstr "誰がこのドキュメントを読むべきでしょうか?"
|
||||
|
||||
#: ./doc/common/ch_using_openstack_overview.xml41(para)
|
||||
msgid ""
|
||||
@ -12992,7 +12992,7 @@ msgid ""
|
||||
"CLI based tools. While this book includes some information about using "
|
||||
"Python to create and manage cloud resources, Python knowledge is not a pre-"
|
||||
"requisite for reading this book."
|
||||
msgstr ""
|
||||
msgstr "このドキュメントは、ソフトウェア開発や研究のために、仮想マシンやクラウドのリソースを使用する、すべての人のために書かれています。数年間の Linux 系ツール群の経験を持ち、GUI と CUI のツールに慣れているとよいでしょう。このドキュメントは、クラウドのリソースを作成および管理するために、Python を使用した情報を含みますが、このドキュメントを理解するために、Python の知識は必ずしも必要ありません。"
|
||||
|
||||
#: ./doc/common/ch_using_openstack_overview.xml46(para)
|
||||
msgid ""
|
||||
|
||||
File diff suppressed because it is too large
Load Diff
File diff suppressed because one or more lines are too long
@ -5,8 +5,8 @@
|
||||
msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: OpenStack Manuals\n"
|
||||
"POT-Creation-Date: 2014-07-24 02:16+0000\n"
|
||||
"PO-Revision-Date: 2014-07-23 06:46+0000\n"
|
||||
"POT-Creation-Date: 2014-07-25 00:50+0000\n"
|
||||
"PO-Revision-Date: 2014-07-25 00:48+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"
|
||||
@ -153,7 +153,7 @@ msgstr "<literal>[DEFAULT]</literal> セクションに初期管理トークン
|
||||
|
||||
#: ./doc/install-guide/section_keystone-install.xml60(replaceable)
|
||||
#: ./doc/install-guide/section_keystone-users.xml31(replaceable)
|
||||
#: ./doc/install-guide/section_trove-install.xml125(replaceable)
|
||||
#: ./doc/install-guide/section_trove-install.xml130(replaceable)
|
||||
msgid "ADMIN_TOKEN"
|
||||
msgstr "ADMIN_TOKEN"
|
||||
|
||||
@ -256,22 +256,24 @@ msgstr "<literal>[database]</literal> セクションに、データベースの
|
||||
#: ./doc/install-guide/section_neutron-ml2-compute-node.xml290(replaceable)
|
||||
#: ./doc/install-guide/section_neutron-ml2-compute-node.xml318(replaceable)
|
||||
#: ./doc/install-guide/section_neutron-ml2-compute-node.xml323(replaceable)
|
||||
#: ./doc/install-guide/section_keystone-openrc.xml27(replaceable)
|
||||
#: ./doc/install-guide/section_keystone-openrc.xml37(replaceable)
|
||||
#: ./doc/install-guide/section_basics-networking-nova.xml204(replaceable)
|
||||
#: ./doc/install-guide/section_trove-install.xml72(replaceable)
|
||||
#: ./doc/install-guide/section_trove-install.xml73(replaceable)
|
||||
#: ./doc/install-guide/section_trove-install.xml74(replaceable)
|
||||
#: ./doc/install-guide/section_trove-install.xml75(replaceable)
|
||||
#: ./doc/install-guide/section_trove-install.xml76(replaceable)
|
||||
#: ./doc/install-guide/section_trove-install.xml77(replaceable)
|
||||
#: ./doc/install-guide/section_trove-install.xml100(replaceable)
|
||||
#: ./doc/install-guide/section_trove-install.xml102(replaceable)
|
||||
#: ./doc/install-guide/section_trove-install.xml104(replaceable)
|
||||
#: ./doc/install-guide/section_trove-install.xml120(replaceable)
|
||||
#: ./doc/install-guide/section_trove-install.xml201(replaceable)
|
||||
#: ./doc/install-guide/section_trove-install.xml78(replaceable)
|
||||
#: ./doc/install-guide/section_trove-install.xml79(replaceable)
|
||||
#: ./doc/install-guide/section_trove-install.xml80(replaceable)
|
||||
#: ./doc/install-guide/section_trove-install.xml81(replaceable)
|
||||
#: ./doc/install-guide/section_trove-install.xml82(replaceable)
|
||||
#: ./doc/install-guide/section_trove-install.xml105(replaceable)
|
||||
#: ./doc/install-guide/section_trove-install.xml107(replaceable)
|
||||
#: ./doc/install-guide/section_trove-install.xml109(replaceable)
|
||||
#: ./doc/install-guide/section_trove-install.xml125(replaceable)
|
||||
#: ./doc/install-guide/section_trove-install.xml206(replaceable)
|
||||
#: ./doc/install-guide/section_trove-install.xml227(replaceable)
|
||||
#: ./doc/install-guide/section_trove-install.xml228(replaceable)
|
||||
#: ./doc/install-guide/section_trove-install.xml229(replaceable)
|
||||
#: ./doc/install-guide/section_trove-install.xml211(replaceable)
|
||||
#: ./doc/install-guide/section_trove-install.xml232(replaceable)
|
||||
#: ./doc/install-guide/section_trove-install.xml233(replaceable)
|
||||
#: ./doc/install-guide/section_trove-install.xml234(replaceable)
|
||||
#: ./doc/install-guide/section_neutron-ml2-controller-node.xml50(replaceable)
|
||||
#: ./doc/install-guide/section_neutron-ml2-controller-node.xml51(replaceable)
|
||||
#: ./doc/install-guide/section_neutron-ml2-controller-node.xml52(replaceable)
|
||||
@ -732,11 +734,11 @@ msgstr "<filename>/etc/cinder/cinder.conf</filename> ファイルの <literal>[D
|
||||
#: ./doc/install-guide/section_cinder-node.xml179(replaceable)
|
||||
#: ./doc/install-guide/section_neutron-ml2-compute-node.xml115(replaceable)
|
||||
#: ./doc/install-guide/section_neutron-ml2-compute-node.xml135(replaceable)
|
||||
#: ./doc/install-guide/section_trove-install.xml86(replaceable)
|
||||
#: ./doc/install-guide/section_trove-install.xml106(replaceable)
|
||||
#: ./doc/install-guide/section_trove-install.xml108(replaceable)
|
||||
#: ./doc/install-guide/section_trove-install.xml110(replaceable)
|
||||
#: ./doc/install-guide/section_trove-install.xml202(replaceable)
|
||||
#: ./doc/install-guide/section_trove-install.xml91(replaceable)
|
||||
#: ./doc/install-guide/section_trove-install.xml111(replaceable)
|
||||
#: ./doc/install-guide/section_trove-install.xml113(replaceable)
|
||||
#: ./doc/install-guide/section_trove-install.xml115(replaceable)
|
||||
#: ./doc/install-guide/section_trove-install.xml207(replaceable)
|
||||
#: ./doc/install-guide/section_neutron-ml2-controller-node.xml194(replaceable)
|
||||
#: ./doc/install-guide/section_neutron-ml2-controller-node.xml210(replaceable)
|
||||
#: ./doc/install-guide/section_nova-compute-install.xml49(replaceable)
|
||||
@ -1108,9 +1110,10 @@ msgstr "<literal>admin</literal> ユーザーを作成します。"
|
||||
#: ./doc/install-guide/section_keystone-verify.xml38(replaceable)
|
||||
#: ./doc/install-guide/section_keystone-verify.xml60(replaceable)
|
||||
#: ./doc/install-guide/section_keystone-verify.xml77(replaceable)
|
||||
#: ./doc/install-guide/section_trove-install.xml124(replaceable)
|
||||
#: ./doc/install-guide/section_trove-install.xml153(replaceable)
|
||||
#: ./doc/install-guide/section_trove-install.xml204(replaceable)
|
||||
#: ./doc/install-guide/section_keystone-openrc.xml26(replaceable)
|
||||
#: ./doc/install-guide/section_trove-install.xml129(replaceable)
|
||||
#: ./doc/install-guide/section_trove-install.xml158(replaceable)
|
||||
#: ./doc/install-guide/section_trove-install.xml209(replaceable)
|
||||
msgid "ADMIN_PASS"
|
||||
msgstr "ADMIN_PASS"
|
||||
|
||||
@ -1196,6 +1199,7 @@ msgstr "<literal>demo</literal> ユーザーを作成します。"
|
||||
#: ./doc/install-guide/section_keystone-verify.xml89(replaceable)
|
||||
#: ./doc/install-guide/section_keystone-verify.xml101(replaceable)
|
||||
#: ./doc/install-guide/ch_clients.xml41(replaceable)
|
||||
#: ./doc/install-guide/section_keystone-openrc.xml36(replaceable)
|
||||
msgid "DEMO_PASS"
|
||||
msgstr "DEMO_PASS"
|
||||
|
||||
@ -4998,6 +5002,70 @@ msgstr "Open vSwitch エージェントを起動し、システム起動時に
|
||||
msgid "Restart the Open vSwitch (OVS) agent:"
|
||||
msgstr "Open vSwitch (OVS) エージェントを再起動します。"
|
||||
|
||||
#: ./doc/install-guide/section_keystone-openrc.xml7(title)
|
||||
msgid "Create OpenStack client environment scripts"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/install-guide/section_keystone-openrc.xml8(para)
|
||||
msgid ""
|
||||
"The previous section used a combination of environment variables and command"
|
||||
" options to interact with the Identity service via the <placeholder-1/> "
|
||||
"client. To increase efficiency of client operations, OpenStack supports "
|
||||
"simple client environment scripts also known as OpenRC files. These scripts "
|
||||
"typically contain common options for all clients, but also support unique "
|
||||
"options. For more information, see the <link "
|
||||
"href=\"http://docs.openstack.org/user-"
|
||||
"guide/content/cli_openrc.html\">OpenStack User Guide</link>."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/install-guide/section_keystone-openrc.xml16(title)
|
||||
msgid "To create the scripts"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/install-guide/section_keystone-openrc.xml17(para)
|
||||
msgid ""
|
||||
"Create client environment scripts for the <literal>admin</literal> and "
|
||||
"<literal>demo</literal> tenants and users. Future portions of this guide "
|
||||
"reference these scripts to load appropriate credentials for client "
|
||||
"operations."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/install-guide/section_keystone-openrc.xml22(para)
|
||||
msgid ""
|
||||
"Edit the <filename>admin-openrc.sh</filename> file and add the following "
|
||||
"content:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/install-guide/section_keystone-openrc.xml28(para)
|
||||
msgid ""
|
||||
"Replace <literal>ADMIN_PASS</literal> with the password you chose for the "
|
||||
"<literal>admin</literal> user in the Identity service."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/install-guide/section_keystone-openrc.xml32(para)
|
||||
msgid ""
|
||||
"Edit the <filename>demo-openrc.sh</filename> file and add the following "
|
||||
"content:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/install-guide/section_keystone-openrc.xml38(para)
|
||||
msgid ""
|
||||
"Replace <literal>DEMO_PASS</literal> with the password you chose for the "
|
||||
"<literal>demo</literal> user in the Identity service."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/install-guide/section_keystone-openrc.xml43(title)
|
||||
msgid "To load client environment scripts"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/install-guide/section_keystone-openrc.xml45(para)
|
||||
msgid ""
|
||||
"To run clients as a certain tenant and user, you can simply load the "
|
||||
"associated client environment script prior to running them. For example, to "
|
||||
"load the location of the Identity service and <literal>admin</literal> "
|
||||
"tenant and user credentials:"
|
||||
msgstr ""
|
||||
|
||||
#. When image changes, this message will be marked fuzzy or untranslated for
|
||||
#. you.
|
||||
#. It doesn't matter what you translate it to: it's not used at all.
|
||||
@ -5062,139 +5130,149 @@ msgid ""
|
||||
"Identity."
|
||||
msgstr "本章は、すでに OpenStack 環境が動作していること、少なくとも Compute、Image Service、Identity がインストールされていることを仮定しています。"
|
||||
|
||||
#: ./doc/install-guide/section_trove-install.xml16(para)
|
||||
#: ./doc/install-guide/section_trove-install.xml18(para)
|
||||
msgid "If you want to do backup and restore, you also need Object Storage."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/install-guide/section_trove-install.xml21(para)
|
||||
msgid ""
|
||||
"If you want to provision datastores on block-storage volumes, you also need "
|
||||
"Block Storage."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/install-guide/section_trove-install.xml24(para)
|
||||
msgid "To install the Database module on the controller:"
|
||||
msgstr "Database モジュールをコントローラーにインストールする方法:"
|
||||
|
||||
#: ./doc/install-guide/section_trove-install.xml19(para)
|
||||
#: ./doc/install-guide/section_trove-install.xml27(para)
|
||||
msgid "Install required packages:"
|
||||
msgstr "必要パッケージをインストールします。"
|
||||
|
||||
#: ./doc/install-guide/section_trove-install.xml26(para)
|
||||
#: ./doc/install-guide/section_trove-install.xml34(para)
|
||||
msgid ""
|
||||
"Respond to the prompts for <link linkend=\"debconf-dbconfig-"
|
||||
"common\">database management</link> and <link linkend=\"debconf-"
|
||||
"Respond to the prompts for <link href=\"debconf-dbconfig-common\">database "
|
||||
"management</link> and <link href=\"debconf-"
|
||||
"keystone_authtoken\"><literal>[keystone_authtoken]</literal> "
|
||||
"settings</link>, and <link linkend=\"debconf-api-endpoints\">API "
|
||||
"settings</link>, and <link href=\"debconf-api-endpoints\">API "
|
||||
"endpoint</link> registration. The <placeholder-1/> command runs "
|
||||
"automatically."
|
||||
msgstr "<link linkend=\"debconf-dbconfig-common\">データベース管理</link>、<link linkend=\"debconf-keystone_authtoken\"><literal>[keystone_authtoken]</literal> 設定</link>、<link linkend=\"debconf-api-endpoints\">API エンドポイント</link>登録に関するプロンプトに答えます。<placeholder-1/> コマンドが自動的に実行されます。"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/install-guide/section_trove-install.xml35(para)
|
||||
#: ./doc/install-guide/section_trove-install.xml40(para)
|
||||
msgid "Prepare OpenStack:"
|
||||
msgstr "OpenStack を準備します。"
|
||||
|
||||
#: ./doc/install-guide/section_trove-install.xml38(para)
|
||||
#: ./doc/install-guide/section_trove-install.xml43(para)
|
||||
msgid "Source the <filename>admin-openrc.sh</filename> file."
|
||||
msgstr "<filename>admin-openrc.sh</filename> ファイルを読み込みます。"
|
||||
|
||||
#: ./doc/install-guide/section_trove-install.xml43(para)
|
||||
#: ./doc/install-guide/section_trove-install.xml48(para)
|
||||
msgid ""
|
||||
"Create a <literal>trove</literal> user that Compute uses to authenticate "
|
||||
"with the Identity service. Use the <literal>service</literal> tenant and "
|
||||
"give the user the <literal>admin</literal> role:"
|
||||
msgstr "Compute が Identity Service で認証するために使用する <literal>trove</literal> ユーザーを作成します。<literal>service</literal> プロジェクトを使用し、ユーザーに <literal>admin</literal> ロールを与えます。"
|
||||
|
||||
#: ./doc/install-guide/section_trove-install.xml48(replaceable)
|
||||
#: ./doc/install-guide/section_trove-install.xml53(replaceable)
|
||||
msgid "TROVE_PASS"
|
||||
msgstr "TROVE_PASS"
|
||||
|
||||
#: ./doc/install-guide/section_trove-install.xml49(replaceable)
|
||||
#: ./doc/install-guide/section_trove-install.xml54(replaceable)
|
||||
msgid "trove@example.com"
|
||||
msgstr "trove@example.com"
|
||||
|
||||
#: ./doc/install-guide/section_trove-install.xml57(para)
|
||||
#: ./doc/install-guide/section_trove-install.xml62(para)
|
||||
msgid ""
|
||||
"Edit the following configuration files, taking the below actions for each "
|
||||
"file:"
|
||||
msgstr "以下の設定ファイルを編集します。各ファイルを次のようにします。"
|
||||
|
||||
#: ./doc/install-guide/section_trove-install.xml60(filename)
|
||||
#: ./doc/install-guide/section_trove-install.xml65(filename)
|
||||
msgid "trove.conf"
|
||||
msgstr "trove.conf"
|
||||
|
||||
#: ./doc/install-guide/section_trove-install.xml61(filename)
|
||||
#: ./doc/install-guide/section_trove-install.xml66(filename)
|
||||
msgid "trove-taskmanager.conf"
|
||||
msgstr "trove-taskmanager.conf"
|
||||
|
||||
#: ./doc/install-guide/section_trove-install.xml62(filename)
|
||||
#: ./doc/install-guide/section_trove-install.xml67(filename)
|
||||
msgid "trove-conductor.conf"
|
||||
msgstr "trove-conductor.conf"
|
||||
|
||||
#: ./doc/install-guide/section_trove-install.xml66(para)
|
||||
#: ./doc/install-guide/section_trove-install.xml71(para)
|
||||
msgid ""
|
||||
"Edit the <literal>[DEFAULT]</literal> section of each file and set "
|
||||
"appropriate values for the OpenStack service URLs, logging and messaging "
|
||||
"configuration, and SQL connections:"
|
||||
msgstr "各ファイルの <literal>[DEFAULT]</literal> セクションを編集し、OpenStack のサービスの URL、ロギング、メッセージングの設定、SQL 接続に対して、適切な値を設定します。"
|
||||
|
||||
#: ./doc/install-guide/section_trove-install.xml76(literal)
|
||||
#: ./doc/install-guide/section_trove-install.xml81(literal)
|
||||
msgid "TROVE_DBPASS"
|
||||
msgstr "TROVE_DBPASS"
|
||||
|
||||
#: ./doc/install-guide/section_trove-install.xml81(para)
|
||||
#: ./doc/install-guide/section_trove-install.xml86(para)
|
||||
msgid ""
|
||||
"Configure the Database module to use the RabbitMQ message broker by setting "
|
||||
"the rabbit_password in the <literal>[DEFAULT]</literal> configuration group "
|
||||
"of each file:"
|
||||
msgstr "各ファイルの <literal>[DEFAULT]</literal> 設定グループに rabbit_password を設定し、Database モジュールが RabbitMQ メッセージブローカーを使用するよう設定します。"
|
||||
|
||||
#: ./doc/install-guide/section_trove-install.xml91(para)
|
||||
#: ./doc/install-guide/section_trove-install.xml96(para)
|
||||
msgid ""
|
||||
"Set these configuration keys to configure the Database module to use the "
|
||||
"RabbitMQ message broker:"
|
||||
msgstr "Database モジュールが RabbitMQ メッセージブローカーを使用するよう設定するために、これらの設定キーを設定します。"
|
||||
|
||||
#: ./doc/install-guide/section_trove-install.xml116(para)
|
||||
#: ./doc/install-guide/section_trove-install.xml121(para)
|
||||
msgid ""
|
||||
"Edit the <literal>[filter:authtoken]</literal> section of the <filename>api-"
|
||||
"paste.ini</filename> file so it matches the listing shown below:"
|
||||
msgstr "<filename>api-paste.ini</filename> ファイルの <literal>[filter:authtoken]</literal> セクションを編集し、以下に示すものと一致するようにします。"
|
||||
|
||||
#: ./doc/install-guide/section_trove-install.xml130(para)
|
||||
#: ./doc/install-guide/section_trove-install.xml135(para)
|
||||
msgid ""
|
||||
"Edit the <filename>trove.conf</filename> file so it includes appropriate "
|
||||
"values for the default datastore and network label regex as shown below:"
|
||||
msgstr "<filename>trove.conf</filename> ファイルを編集し、デフォルトのデータストアおよびネットワークラベルの正規表現に、以下に示すように適切な値を設定します。"
|
||||
|
||||
#: ./doc/install-guide/section_trove-install.xml143(para)
|
||||
#: ./doc/install-guide/section_trove-install.xml148(para)
|
||||
msgid ""
|
||||
"Edit the <filename>trove-taskmanager.conf</filename> file so it includes the"
|
||||
" appropriate service credentials required to connect to the OpenStack "
|
||||
"Compute service as shown below:"
|
||||
msgstr "以下に示すように <filename>trove-taskmanager.conf</filename> ファイルを編集し、OpenStack Compute サービスに接続するために必要となるサービスのクレデンシャルを適切に設定します。"
|
||||
|
||||
#: ./doc/install-guide/section_trove-install.xml159(para)
|
||||
#: ./doc/install-guide/section_trove-install.xml164(para)
|
||||
msgid "Prepare the trove admin database:"
|
||||
msgstr "trove 管理データベースを準備します。"
|
||||
|
||||
#: ./doc/install-guide/section_trove-install.xml167(para)
|
||||
#: ./doc/install-guide/section_trove-install.xml172(para)
|
||||
msgid "Prepare the Database service:"
|
||||
msgstr "Database サービスを準備します。"
|
||||
|
||||
#: ./doc/install-guide/section_trove-install.xml170(para)
|
||||
#: ./doc/install-guide/section_trove-install.xml175(para)
|
||||
msgid "Initialize the database:"
|
||||
msgstr "データベースを初期化します。"
|
||||
|
||||
#: ./doc/install-guide/section_trove-install.xml174(para)
|
||||
#: ./doc/install-guide/section_trove-install.xml182(para)
|
||||
#: ./doc/install-guide/section_trove-install.xml179(para)
|
||||
#: ./doc/install-guide/section_trove-install.xml187(para)
|
||||
msgid ""
|
||||
"Create a datastore. You need to create a separate datastore for each type of"
|
||||
" database you want to use, for example, MySQL, MongoDB, Cassandra. This "
|
||||
"example shows you how to create a datastore for a MySQL database:"
|
||||
msgstr "データストアを作成します。使用したいデータベースの種類に応じて、別々のデータストアを作成する必要があります。例えば、MySQL、MongoDB、Cassandra です。この例は、MySQL データベース用のデータストアを作成する方法です。"
|
||||
|
||||
#: ./doc/install-guide/section_trove-install.xml188(para)
|
||||
#: ./doc/install-guide/section_trove-install.xml193(para)
|
||||
msgid "Create a trove image."
|
||||
msgstr "trove イメージを作成します。"
|
||||
|
||||
#: ./doc/install-guide/section_trove-install.xml189(para)
|
||||
#: ./doc/install-guide/section_trove-install.xml194(para)
|
||||
msgid ""
|
||||
"Create an image for the type of database you want to use, for example, "
|
||||
"MySQL, MongoDB, Cassandra."
|
||||
msgstr "使用したいデータベースの種類に応じてイメージを作成します。例えば、MySQL、MongoDB、Cassandra です。"
|
||||
|
||||
#: ./doc/install-guide/section_trove-install.xml191(para)
|
||||
#: ./doc/install-guide/section_trove-install.xml196(para)
|
||||
msgid ""
|
||||
"This image must have the trove guest agent installed, and it must have the "
|
||||
"<filename>trove-guestagent.conf</filename> file configured to connect to "
|
||||
@ -5203,37 +5281,37 @@ msgid ""
|
||||
"you are using to build your image:"
|
||||
msgstr "このイメージは trove ゲストエージェントがインストールされている必要があります。お使いの OpenStack 環境に接続するために、<filename>trove-guestagent.conf</filename> ファイルを設定する必要があります。<filename>trove-guestagent.conf</filename> ファイルを正しく設定するために、イメージ構築用に使用しているゲストインスタンスでこれらの手順を実行します。"
|
||||
|
||||
#: ./doc/install-guide/section_trove-install.xml200(para)
|
||||
#: ./doc/install-guide/section_trove-install.xml205(para)
|
||||
msgid "Add the following lines to <filename>trove-guestagent.conf</filename>:"
|
||||
msgstr "以下の行を <filename>trove-guestagent.conf</filename> に追加します。"
|
||||
|
||||
#: ./doc/install-guide/section_trove-install.xml212(para)
|
||||
#: ./doc/install-guide/section_trove-install.xml217(para)
|
||||
msgid ""
|
||||
"Update the datastore to use the new image, using the <placeholder-1/> "
|
||||
"command."
|
||||
msgstr "新しいイメージを使用するために、<placeholder-1/> コマンドを使用して、データストアを更新します。"
|
||||
|
||||
#: ./doc/install-guide/section_trove-install.xml214(para)
|
||||
#: ./doc/install-guide/section_trove-install.xml219(para)
|
||||
msgid "This example shows you how to create a MySQL 5.5 datastore:"
|
||||
msgstr "この例は MySQL 5.5 データストアを作成する方法です。"
|
||||
|
||||
#: ./doc/install-guide/section_trove-install.xml216(replaceable)
|
||||
#: ./doc/install-guide/section_trove-install.xml221(replaceable)
|
||||
msgid "glance_image_ID"
|
||||
msgstr "glance_image_ID"
|
||||
|
||||
#: ./doc/install-guide/section_trove-install.xml220(para)
|
||||
#: ./doc/install-guide/section_trove-install.xml225(para)
|
||||
msgid ""
|
||||
"You must register the Database module with the Identity service so that "
|
||||
"other OpenStack services can locate it. Register the service and specify the"
|
||||
" endpoint:"
|
||||
msgstr "他の OpenStack サービスから使用できるように、Database モジュールを Identity Service に登録します。サービスを登録し、エンドポイントを指定します。"
|
||||
|
||||
#: ./doc/install-guide/section_trove-install.xml233(para)
|
||||
#: ./doc/install-guide/section_trove-install.xml238(para)
|
||||
msgid ""
|
||||
"Start Database services and configure them to start when the system boots:"
|
||||
msgstr "Database サービスを起動し、システム起動時に起動するよう設定します。"
|
||||
|
||||
#: ./doc/install-guide/section_trove-install.xml236(para)
|
||||
#: ./doc/install-guide/section_trove-install.xml241(para)
|
||||
msgid "Restart Database services:"
|
||||
msgstr "Database サービスを再起動します。"
|
||||
|
||||
|
||||
@ -7,9 +7,9 @@
|
||||
msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: OpenStack Manuals\n"
|
||||
"POT-Creation-Date: 2014-07-24 02:16+0000\n"
|
||||
"PO-Revision-Date: 2014-07-23 15:31+0000\n"
|
||||
"Last-Translator: openstackjenkins <jenkins@openstack.org>\n"
|
||||
"POT-Creation-Date: 2014-07-25 00:50+0000\n"
|
||||
"PO-Revision-Date: 2014-07-24 09:50+0000\n"
|
||||
"Last-Translator: Tomoyuki KATO <tomo@dream.daynight.jp>\n"
|
||||
"Language-Team: Japanese (http://www.transifex.com/projects/p/openstack-manuals-i18n/language/ja/)\n"
|
||||
"MIME-Version: 1.0\n"
|
||||
"Content-Type: text/plain; charset=UTF-8\n"
|
||||
@ -3357,7 +3357,7 @@ msgstr ""
|
||||
|
||||
#: ./doc/user-guide/section_cli_trove.xml128(title)
|
||||
msgid "MySQL example"
|
||||
msgstr ""
|
||||
msgstr "MySQL の例"
|
||||
|
||||
#: ./doc/user-guide/section_cli_trove.xml129(para)
|
||||
msgid ""
|
||||
@ -3930,11 +3930,11 @@ msgstr ""
|
||||
|
||||
#: ./doc/user-guide/section_cli_trove.xml695(replaceable)
|
||||
msgid "CONFIG_GROUP_ID"
|
||||
msgstr ""
|
||||
msgstr "CONFIG_GROUP_ID"
|
||||
|
||||
#: ./doc/user-guide/section_cli_trove.xml695(replaceable)
|
||||
msgid "DB_INSTANCE_ID"
|
||||
msgstr ""
|
||||
msgstr "DB_INSTANCE_ID"
|
||||
|
||||
#: ./doc/user-guide/section_cli_trove.xml698(title)
|
||||
msgid "Re-examine the database configuration"
|
||||
|
||||
Loading…
Reference in New Issue
Block a user