openstack/openstack-manuals
Code Issues Proposed changes

Imported Translations from Transifex

Browse Source 
Change-Id: I17ba3b7eb2016e52fec90ebcec19bbd7ddb2f72a
This commit is contained in:
OpenStack Proposal Bot 2014-06-05 06:07:46 +00:00
parent 726fa1da31
commit 92b93d02f2
7 changed files with 699 additions and 628 deletions
doc
common/locale
common.potfr.poja.po
config-reference/locale
config-reference.pot
install-guide/locale
install-guide.potja.po
user-guide/locale
ja.po

150
doc/common/locale/common.pot

@ -1,7 +1,7 @@
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"POT-Creation-Date: 2014-06-03 06:11+0000\n"
"POT-Creation-Date: 2014-06-05 06:07+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"
@ -7262,87 +7262,99 @@ msgid "Database service overview"
msgstr ""
#: ./doc/common/section_getstart_trove.xml:6(para)
msgid "The Database service provides scalable and reliable cloud provisioning functionality for both relational and non-relational database engines. Users can quickly and easily utilize database features without the burden of handling complex administrative tasks. Cloud users and database administrators can provision and manage multiple database instances as needed."
msgstr ""
#: ./doc/common/section_getstart_trove.xml:7(para)
msgid "The Database service provides resource isolation at high performance levels, and automates complex administrative tasks such as deployment, configuration, patching, backups, restores, and monitoring."
msgstr ""
#: ./doc/common/section_getstart_trove.xml:9(title)
msgid "Process flow example."
msgstr ""
#: ./doc/common/section_getstart_trove.xml:9(para)
msgid "Here is a high-level process flow example for using Database services:"
msgid "The Database service provides scalable and reliable cloud provisioning functionality for both relational and non-relational database engines. Users can quickly and easily use database features without the burden of handling complex administrative tasks. Cloud users and database administrators can provision and manage multiple database instances as needed."
msgstr ""
#: ./doc/common/section_getstart_trove.xml:12(para)
msgid "Administrator sets up infrastructure:"
msgid "The Database service provides resource isolation at high performance levels, and automates complex administrative tasks such as deployment, configuration, patching, backups, restores, and monitoring."
msgstr ""
#: ./doc/common/section_getstart_trove.xml:15(para)
msgid "OpenStack administrator installs the Database service."
#: ./doc/common/section_getstart_trove.xml:16(title)
msgid "Process flow example"
msgstr ""
#: ./doc/common/section_getstart_trove.xml:18(para)
msgid "She creates one image for each type of database the administrator wants to have (one for MySQL, one for MongoDB, and so on)."
#: ./doc/common/section_getstart_trove.xml:17(para)
msgid "This example is a high-level process flow for using Database services:"
msgstr ""
#: ./doc/common/section_getstart_trove.xml:23(para)
msgid "OpenStack administrator updates the datastore to use the new images, using the <placeholder-1/> command."
#: ./doc/common/section_getstart_trove.xml:21(para)
msgid "The OpenStack Administrator configures the basic infrastructure using the following steps:"
msgstr ""
#: ./doc/common/section_getstart_trove.xml:30(para)
msgid "End user uses database service:"
#: ./doc/common/section_getstart_trove.xml:25(para)
msgid "Install the Database service."
msgstr ""
#: ./doc/common/section_getstart_trove.xml:33(para)
msgid "Now that the basic infrastructure is set up, an end user can create a Trove instance (database) whenever the user wants, using the <placeholder-1/> command."
#: ./doc/common/section_getstart_trove.xml:28(para)
msgid "Create an image for each type of database. For example, one for MySQL and one for MongoDB."
msgstr ""
#: ./doc/common/section_getstart_trove.xml:41(replaceable)
msgid "instanceID"
#: ./doc/common/section_getstart_trove.xml:32(para)
msgid "Use the <placeholder-1/> command to import images and offer them to tenants."
msgstr ""
#: ./doc/common/section_getstart_trove.xml:39(para)
msgid "The end user gets the IP address of the Trove instance by using the <placeholder-1/> command to get the ID of the instance, and then using the <placeholder-2/> command to get the IP address."
#: ./doc/common/section_getstart_trove.xml:38(para)
msgid "The OpenStack end user deploys the Database service using the following steps:"
msgstr ""
#: ./doc/common/section_getstart_trove.xml:44(para)
msgid "The end user can now access the Trove instance using typical database access commands. MySQL example:"
#: ./doc/common/section_getstart_trove.xml:42(para)
msgid "Create a Database service instance using the <placeholder-1/> command."
msgstr ""
#: ./doc/common/section_getstart_trove.xml:45(replaceable)
msgid "trove_ip_address"
#: ./doc/common/section_getstart_trove.xml:47(para)
msgid "Use the <placeholder-1/> command to get the ID of the instance, followed by the <placeholder-2/> command to get the IP address of it."
msgstr ""
#: ./doc/common/section_getstart_trove.xml:51(title)
msgid "Components:"
#: ./doc/common/section_getstart_trove.xml:52(para)
msgid "Access the Database service instance using typical database access commands. For example, with MySQL:"
msgstr ""
#: ./doc/common/section_getstart_trove.xml:51(para)
#: ./doc/common/section_getstart_trove.xml:54(replaceable)
msgid "TROVE_IP_ADDRESS"
msgstr ""
#: ./doc/common/section_getstart_trove.xml:59(para)
msgid "The Database service includes the following components:"
msgstr ""
#: ./doc/common/section_getstart_trove.xml:55(para)
msgid "<code>python-troveclient</code> command-line client. A CLI that communicates with the <code>trove-api</code> component."
#: ./doc/common/section_getstart_trove.xml:62(term)
msgid "<code>python-troveclient</code> command-line client"
msgstr ""
#: ./doc/common/section_getstart_trove.xml:58(para)
msgid "<code>trove-api</code> component. Provides an OpenStack-native RESTful API that supports JSON to provision and manage Trove instances."
#: ./doc/common/section_getstart_trove.xml:63(para)
msgid "A CLI that communicates with the <code>trove-api</code> component."
msgstr ""
#: ./doc/common/section_getstart_trove.xml:62(para)
msgid "<code>trove-conductor</code> service. Runs on the host, and receives messages from guest instances that want to update information on the host."
msgstr ""
#: ./doc/common/section_getstart_trove.xml:65(para)
msgid "<code>trove-taskmanager</code> service. Instruments the complex system flows that support provisioning instances, managing the lifecycle of instances, and performing operations on instances."
#: ./doc/common/section_getstart_trove.xml:67(term)
msgid "<code>trove-api</code> component"
msgstr ""
#: ./doc/common/section_getstart_trove.xml:68(para)
msgid "<code>trove-guestagent</code> service. Runs within the guest instance. Manages and performs operations on the database itself."
msgid "Provides an OpenStack-native RESTful API that supports JSON to provision and manage Trove instances."
msgstr ""
#: ./doc/common/section_getstart_trove.xml:72(term)
msgid "<code>trove-conductor</code> service"
msgstr ""
#: ./doc/common/section_getstart_trove.xml:73(para)
msgid "Runs on the host, and receives messages from guest instances that want to update information on the host."
msgstr ""
#: ./doc/common/section_getstart_trove.xml:77(term)
msgid "<code>trove-taskmanager</code> service"
msgstr ""
#: ./doc/common/section_getstart_trove.xml:78(para)
msgid "Instruments the complex system flows that support provisioning instances, managing the lifecycle of instances, and performing operations on instances."
msgstr ""
#: ./doc/common/section_getstart_trove.xml:83(term)
msgid "<code>trove-guestagent</code> service"
msgstr ""
#: ./doc/common/section_getstart_trove.xml:84(para)
msgid "Runs within the guest instance. Manages and performs operations on the database itself."
msgstr ""
#: ./doc/common/section_keystone_db_sync.xml:6(title)
@ -13456,7 +13468,7 @@ msgstr ""
msgid "The common agents are L3 (layer 3), DHCP (dynamic host IP addressing), and a plug-in agent."
msgstr ""
#: ./doc/common/section_getstart_networking.xml:31(term) ./doc/common/section_getstart_block-storage.xml:35(term)
#: ./doc/common/section_getstart_networking.xml:31(term) ./doc/common/section_getstart_block-storage.xml:43(term)
msgid "Messaging queue"
msgstr ""
@ -13557,41 +13569,41 @@ msgid "OpenStack Block Storage"
msgstr ""
#: ./doc/common/section_getstart_block-storage.xml:6(para)
msgid "OpenStack Block Storage enables management of volumes, volume snapshots, and volume types. It consists of the following components:"
msgstr ""
#: ./doc/common/section_getstart_block-storage.xml:11(systemitem)
msgid "cinder-api"
msgid "The Openstack Block Storage service (cinder) adds persistent storage to a virtual machine. Block Storage provides an infrastructure for managing volumes, and interacts with OpenStack Compute to provide volumes for instances. The service also enables management of volume snapshots, and volume types."
msgstr ""
#: ./doc/common/section_getstart_block-storage.xml:12(para)
msgid "Accepts API requests and routes them to <systemitem class=\"service\">cinder-volume</systemitem> for action."
msgid "The Block Storage service consists of the following components:"
msgstr ""
#: ./doc/common/section_getstart_block-storage.xml:17(systemitem)
#: ./doc/common/section_getstart_block-storage.xml:16(systemitem)
msgid "cinder-api"
msgstr ""
#: ./doc/common/section_getstart_block-storage.xml:17(para)
msgid "Accepts API requests, and routes them to the <systemitem class=\"service\">cinder-volume</systemitem> for action."
msgstr ""
#: ./doc/common/section_getstart_block-storage.xml:22(systemitem)
msgid "cinder-volume"
msgstr ""
#: ./doc/common/section_getstart_block-storage.xml:18(para)
msgid "Responds to requests to read from and write to the OpenStack Block Storage database to maintain state, interacting with other processes (like <systemitem class=\"service\">cinder-scheduler</systemitem>) through a message queue and directly upon block storage providing hardware or software. It can interact with a variety of storage providers through a driver architecture."
#: ./doc/common/section_getstart_block-storage.xml:23(para)
msgid "Interacts directly with the Block Storage service, and processes such as the <systemitem class=\"service\">cinder-scheduler</systemitem>. It also interacts with these processes through a message queue. The <systemitem>cinder-volume service</systemitem> responds to read and write requests sent to the Block Storage service to maintain state. It can interact with a variety of storage providers through a driver architecture."
msgstr ""
#: ./doc/common/section_getstart_block-storage.xml:28(term)
#: ./doc/common/section_getstart_block-storage.xml:35(term)
msgid "<systemitem class=\"service\">cinder-scheduler</systemitem> daemon"
msgstr ""
#: ./doc/common/section_getstart_block-storage.xml:30(para)
msgid "Like the <systemitem class=\"service\">nova-scheduler</systemitem>, picks the optimal block storage provider node on which to create the volume."
#: ./doc/common/section_getstart_block-storage.xml:37(para)
msgid "Selects the optimal storage provider node on which to create the volume. A similar component to the <systemitem class=\"service\">nova-scheduler</systemitem>."
msgstr ""
#: ./doc/common/section_getstart_block-storage.xml:36(para)
#: ./doc/common/section_getstart_block-storage.xml:44(para)
msgid "Routes information between the Block Storage processes."
msgstr ""
#: ./doc/common/section_getstart_block-storage.xml:40(para)
msgid "OpenStack Block Storage interacts with OpenStack Compute to provide volumes for instances."
msgstr ""
#: ./doc/common/section_dashboard-configure-vnc-window.xml:6(title)
msgid "Change the size of the dashboard VNC window"
msgstr ""
@ -15961,7 +15973,7 @@ msgid "controller"
msgstr ""
#: ./doc/common/section_config_format.xml:32(para)
msgid "Options can have different type for values. The comments in the sample config files always mention these. The following types are used by OpenStack:"
msgid "Options can have different types for values. The comments in the sample config files always mention these. The following types are used by OpenStack:"
msgstr ""
#: ./doc/common/section_config_format.xml:39(term)
@ -16033,7 +16045,7 @@ msgid "Configuration options for the database that stores the state of the OpenS
msgstr ""
#: ./doc/common/section_config_format.xml:128(para)
msgid "Configuration options are grouped by section. Most configuration file supports at least the following sections: <placeholder-1/>"
msgid "Configuration options are grouped by section. Most configuration files support at least the following sections: <placeholder-1/>"
msgstr ""
#: ./doc/common/section_config_format.xml:158(title)
@ -17022,7 +17034,7 @@ msgid "You cannot change the default outbound behavior."
msgstr ""
#: ./doc/common/section_cli_nova_secgroups.xml:66(para)
msgid "The security group rules control the incoming traffic that can access the instances in the group, while all outbound traffic is automatically allowed. <placeholder-1/>Every security group rule is a policy that allows you to specify inbound connections that can access the instance by source address, destination port, and IP protocol (TCP, UDP or ICMP). Currently, you cannot manage ipv6 and other protocols through the security rules, making them permitted by default. To manage such protocols, you can deploy a firewall in front of your OpenStack cloud to control other types of traffic. The command requires the following arguments for both TCP and UDP rules:"
msgid "The security group rules control the incoming traffic that can access the instances in the group, while all outbound traffic is automatically allowed. <placeholder-1/>Every security group rule is a policy that allows you to specify inbound connections that can access the instance by source address, destination port, and IP protocol (TCP, UDP or ICMP). Currently, you cannot manage IPv6 and other protocols through the security rules, making them permitted by default. To manage such protocols, you can deploy a firewall in front of your OpenStack cloud to control other types of traffic. The command requires the following arguments for both TCP and UDP rules:"
msgstr ""
#: ./doc/common/section_cli_nova_secgroups.xml:84(emphasis) ./doc/common/section_cli_nova_secgroups.xml:124(emphasis) ./doc/common/section_cli_nova_secgroups.xml:209(emphasis)
@ -17086,7 +17098,7 @@ msgid "The CIDR notation"
msgstr ""
#: ./doc/common/section_cli_nova_secgroups.xml:165(para)
msgid "That notation allows you to specify a base IP address and a suffix that designates the number of significant bits in the IP address used to identify the network. For example, by specifying a <literal>88.170.60.32/27</literal>, you specify <literal>88.170.60.32</literal> as the <emphasis role=\"bold\">base IP</emphasis> and <literal>27</literal> as the <emphasis role=\"bold\">suffix</emphasis>. Because you use an IPV4 format, only 5 bits are available for the host part (32 minus 27). The <literal>0.0.0.0/0</literal> notation means you allow the entire IPV4 range, which allows all addresses."
msgid "That notation allows you to specify a base IP address and a suffix that designates the number of significant bits in the IP address used to identify the network. For example, by specifying a <literal>88.170.60.32/27</literal>, you specify <literal>88.170.60.32</literal> as the <emphasis role=\"bold\">base IP</emphasis> and <literal>27</literal> as the <emphasis role=\"bold\">suffix</emphasis>. Because you use an IPv4 format, only 5 bits are available for the host part (32 minus 27). The <literal>0.0.0.0/0</literal> notation means you allow the entire IPv4 range, which allows all addresses."
msgstr ""
#: ./doc/common/section_cli_nova_secgroups.xml:179(para)

225
doc/common/locale/fr.po

@ -1,9 +1,9 @@
#
# Translators:
# alexis.monville <alexis.monville@ayeba.fr>, 2013
# alexis.monville <alexis.monville@ayeba.fr>, 2013
# Alexis Monville <alexis.monville@ayeba.fr>, 2013
# Alexis Monville <alexis.monville@ayeba.fr>, 2013
# brouchouse <brouchouse@gmail.com>, 2014
# c <cverheyd@hotmail.com>, 2013
# Corinne Verheyde <cverheyd@hotmail.com>, 2013
# Christophe kryskool <christophe.chauvet@gmail.com>, 2013
# codegin, 2013
# codegin, 2013
@ -12,14 +12,14 @@
# Jérôme Fenal <jfenal@gmail.com>, 2013
# Kamel_CW <yamani.kamel@gmail.com>, 2014
# cloudwatt_l10n <l10n@cloudwatt.com>, 2014
# steff00 <stephane.eveillard@gmail.com>, 2013
# EVEILLARD <stephane.eveillard@gmail.com>, 2013
# Kamel_CW <yamani.kamel@gmail.com>, 2014
# zencloud <genevieve.ribot@gmail.com>, 2013
# RIBOT GENEVIEVE <genevieve.ribot@gmail.com>, 2013
msgid ""
msgstr ""
"Project-Id-Version: OpenStack Manuals\n"
"POT-Creation-Date: 2014-06-03 02:30+0000\n"
"PO-Revision-Date: 2014-06-03 02:40+0000\n"
"POT-Creation-Date: 2014-06-04 20:34+0000\n"
"PO-Revision-Date: 2014-06-04 20:33+0000\n"
"Last-Translator: openstackjenkins <jenkins@openstack.org>\n"
"Language-Team: French (http://www.transifex.com/projects/p/openstack-manuals-i18n/language/fr/)\n"
"MIME-Version: 1.0\n"
@ -10463,116 +10463,123 @@ msgstr ""
msgid ""
"The Database service provides scalable and reliable cloud provisioning "
"functionality for both relational and non-relational database engines. Users"
" can quickly and easily utilize database features without the burden of "
"handling complex administrative tasks. Cloud users and database "
"administrators can provision and manage multiple database instances as "
"needed."
" can quickly and easily use database features without the burden of handling"
" complex administrative tasks. Cloud users and database administrators can "
"provision and manage multiple database instances as needed."
msgstr ""
#: ./doc/common/section_getstart_trove.xml7(para)
#: ./doc/common/section_getstart_trove.xml12(para)
msgid ""
"The Database service provides resource isolation at high performance levels,"
" and automates complex administrative tasks such as deployment, "
"configuration, patching, backups, restores, and monitoring."
msgstr ""
#: ./doc/common/section_getstart_trove.xml9(title)
msgid "Process flow example."
#: ./doc/common/section_getstart_trove.xml16(title)
msgid "Process flow example"
msgstr ""
#: ./doc/common/section_getstart_trove.xml9(para)
msgid "Here is a high-level process flow example for using Database services:"
#: ./doc/common/section_getstart_trove.xml17(para)
msgid "This example is a high-level process flow for using Database services:"
msgstr ""
#: ./doc/common/section_getstart_trove.xml12(para)
msgid "Administrator sets up infrastructure:"
msgstr ""
#: ./doc/common/section_getstart_trove.xml15(para)
msgid "OpenStack administrator installs the Database service."
msgstr ""
#: ./doc/common/section_getstart_trove.xml18(para)
#: ./doc/common/section_getstart_trove.xml21(para)
msgid ""
"She creates one image for each type of database the administrator wants to "
"have (one for MySQL, one for MongoDB, and so on)."
"The OpenStack Administrator configures the basic infrastructure using the "
"following steps:"
msgstr ""
#: ./doc/common/section_getstart_trove.xml23(para)
#: ./doc/common/section_getstart_trove.xml25(para)
msgid "Install the Database service."
msgstr ""
#: ./doc/common/section_getstart_trove.xml28(para)
msgid ""
"OpenStack administrator updates the datastore to use the new images, using "
"the <placeholder-1/> command."
"Create an image for each type of database. For example, one for MySQL and "
"one for MongoDB."
msgstr ""
#: ./doc/common/section_getstart_trove.xml30(para)
msgid "End user uses database service:"
msgstr ""
#: ./doc/common/section_getstart_trove.xml33(para)
#: ./doc/common/section_getstart_trove.xml32(para)
msgid ""
"Now that the basic infrastructure is set up, an end user can create a Trove "
"instance (database) whenever the user wants, using the <placeholder-1/> "
"command."
"Use the <placeholder-1/> command to import images and offer them to tenants."
msgstr ""
#: ./doc/common/section_getstart_trove.xml41(replaceable)
msgid "instanceID"
msgstr ""
#: ./doc/common/section_getstart_trove.xml39(para)
#: ./doc/common/section_getstart_trove.xml38(para)
msgid ""
"The end user gets the IP address of the Trove instance by using the "
"<placeholder-1/> command to get the ID of the instance, and then using the "
"<placeholder-2/> command to get the IP address."
"The OpenStack end user deploys the Database service using the following "
"steps:"
msgstr ""
#: ./doc/common/section_getstart_trove.xml44(para)
#: ./doc/common/section_getstart_trove.xml42(para)
msgid "Create a Database service instance using the <placeholder-1/> command."
msgstr ""
#: ./doc/common/section_getstart_trove.xml47(para)
msgid ""
"The end user can now access the Trove instance using typical database access"
" commands. MySQL example:"
"Use the <placeholder-1/> command to get the ID of the instance, followed by "
"the <placeholder-2/> command to get the IP address of it."
msgstr ""
#: ./doc/common/section_getstart_trove.xml45(replaceable)
msgid "trove_ip_address"
#: ./doc/common/section_getstart_trove.xml52(para)
msgid ""
"Access the Database service instance using typical database access commands."
" For example, with MySQL:"
msgstr ""
#: ./doc/common/section_getstart_trove.xml51(title)
msgid "Components:"
#: ./doc/common/section_getstart_trove.xml54(replaceable)
msgid "TROVE_IP_ADDRESS"
msgstr ""
#: ./doc/common/section_getstart_trove.xml51(para)
#: ./doc/common/section_getstart_trove.xml59(para)
msgid "The Database service includes the following components:"
msgstr ""
#: ./doc/common/section_getstart_trove.xml55(para)
msgid ""
"<code>python-troveclient</code> command-line client. A CLI that communicates"
" with the <code>trove-api</code> component."
#: ./doc/common/section_getstart_trove.xml62(term)
msgid "<code>python-troveclient</code> command-line client"
msgstr ""
#: ./doc/common/section_getstart_trove.xml58(para)
msgid ""
"<code>trove-api</code> component. Provides an OpenStack-native RESTful API "
"that supports JSON to provision and manage Trove instances."
#: ./doc/common/section_getstart_trove.xml63(para)
msgid "A CLI that communicates with the <code>trove-api</code> component."
msgstr ""
#: ./doc/common/section_getstart_trove.xml62(para)
msgid ""
"<code>trove-conductor</code> service. Runs on the host, and receives "
"messages from guest instances that want to update information on the host."
msgstr ""
#: ./doc/common/section_getstart_trove.xml65(para)
msgid ""
"<code>trove-taskmanager</code> service. Instruments the complex system flows"
" that support provisioning instances, managing the lifecycle of instances, "
"and performing operations on instances."
#: ./doc/common/section_getstart_trove.xml67(term)
msgid "<code>trove-api</code> component"
msgstr ""
#: ./doc/common/section_getstart_trove.xml68(para)
msgid ""
"<code>trove-guestagent</code> service. Runs within the guest instance. "
"Manages and performs operations on the database itself."
"Provides an OpenStack-native RESTful API that supports JSON to provision and"
" manage Trove instances."
msgstr ""
#: ./doc/common/section_getstart_trove.xml72(term)
msgid "<code>trove-conductor</code> service"
msgstr ""
#: ./doc/common/section_getstart_trove.xml73(para)
msgid ""
"Runs on the host, and receives messages from guest instances that want to "
"update information on the host."
msgstr ""
#: ./doc/common/section_getstart_trove.xml77(term)
msgid "<code>trove-taskmanager</code> service"
msgstr ""
#: ./doc/common/section_getstart_trove.xml78(para)
msgid ""
"Instruments the complex system flows that support provisioning instances, "
"managing the lifecycle of instances, and performing operations on instances."
msgstr ""
#: ./doc/common/section_getstart_trove.xml83(term)
msgid "<code>trove-guestagent</code> service"
msgstr ""
#: ./doc/common/section_getstart_trove.xml84(para)
msgid ""
"Runs within the guest instance. Manages and performs operations on the "
"database itself."
msgstr ""
#: ./doc/common/section_keystone_db_sync.xml6(title)
@ -18534,7 +18541,7 @@ msgid ""
msgstr ""
#: ./doc/common/section_getstart_networking.xml31(term)
#: ./doc/common/section_getstart_block-storage.xml35(term)
#: ./doc/common/section_getstart_block-storage.xml43(term)
msgid "Messaging queue"
msgstr ""
@ -18686,54 +18693,56 @@ msgstr ""
#: ./doc/common/section_getstart_block-storage.xml6(para)
msgid ""
"OpenStack Block Storage enables management of volumes, volume snapshots, and"
" volume types. It consists of the following components:"
msgstr ""
#: ./doc/common/section_getstart_block-storage.xml11(systemitem)
msgid "cinder-api"
"The Openstack Block Storage service (cinder) adds persistent storage to a "
"virtual machine. Block Storage provides an infrastructure for managing "
"volumes, and interacts with OpenStack Compute to provide volumes for "
"instances. The service also enables management of volume snapshots, and "
"volume types."
msgstr ""
#: ./doc/common/section_getstart_block-storage.xml12(para)
msgid "The Block Storage service consists of the following components:"
msgstr ""
#: ./doc/common/section_getstart_block-storage.xml16(systemitem)
msgid "cinder-api"
msgstr ""
#: ./doc/common/section_getstart_block-storage.xml17(para)
msgid ""
"Accepts API requests and routes them to <systemitem class=\"service"
"Accepts API requests, and routes them to the <systemitem class=\"service"
"\">cinder-volume</systemitem> for action."
msgstr ""
#: ./doc/common/section_getstart_block-storage.xml17(systemitem)
#: ./doc/common/section_getstart_block-storage.xml22(systemitem)
msgid "cinder-volume"
msgstr ""
#: ./doc/common/section_getstart_block-storage.xml18(para)
#: ./doc/common/section_getstart_block-storage.xml23(para)
msgid ""
"Responds to requests to read from and write to the OpenStack Block Storage "
"database to maintain state, interacting with other processes (like "
"<systemitem class=\"service\">cinder-scheduler</systemitem>) through a "
"message queue and directly upon block storage providing hardware or "
"software. It can interact with a variety of storage providers through a "
"driver architecture."
"Interacts directly with the Block Storage service, and processes such as the"
" <systemitem class=\"service\">cinder-scheduler</systemitem>. It also "
"interacts with these processes through a message queue. The <systemitem"
">cinder-volume service</systemitem> responds to read and write requests sent"
" to the Block Storage service to maintain state. It can interact with a "
"variety of storage providers through a driver architecture."
msgstr ""
#: ./doc/common/section_getstart_block-storage.xml28(term)
#: ./doc/common/section_getstart_block-storage.xml35(term)
msgid "<systemitem class=\"service\">cinder-scheduler</systemitem> daemon"
msgstr ""
#: ./doc/common/section_getstart_block-storage.xml30(para)
#: ./doc/common/section_getstart_block-storage.xml37(para)
msgid ""
"Like the <systemitem class=\"service\">nova-scheduler</systemitem>, picks "
"the optimal block storage provider node on which to create the volume."
"Selects the optimal storage provider node on which to create the volume. A "
"similar component to the <systemitem class=\"service\">nova-"
"scheduler</systemitem>."
msgstr ""
#: ./doc/common/section_getstart_block-storage.xml36(para)
#: ./doc/common/section_getstart_block-storage.xml44(para)
msgid "Routes information between the Block Storage processes."
msgstr ""
#: ./doc/common/section_getstart_block-storage.xml40(para)
msgid ""
"OpenStack Block Storage interacts with OpenStack Compute to provide volumes "
"for instances."
msgstr ""
#: ./doc/common/section_dashboard-configure-vnc-window.xml6(title)
msgid "Change the size of the dashboard VNC window"
msgstr ""
@ -22022,7 +22031,7 @@ msgstr "controller"
#: ./doc/common/section_config_format.xml32(para)
msgid ""
"Options can have different type for values. The comments in the sample "
"Options can have different types for values. The comments in the sample "
"config files always mention these. The following types are used by "
"OpenStack:"
msgstr ""
@ -22349,8 +22358,8 @@ msgstr ""
#: ./doc/common/section_config_format.xml128(para)
msgid ""
"Configuration options are grouped by section. Most configuration file "
"supports at least the following sections: <placeholder-1/>"
"Configuration options are grouped by section. Most configuration files "
"support at least the following sections: <placeholder-1/>"
msgstr ""
#: ./doc/common/section_config_format.xml158(title)
@ -23657,7 +23666,7 @@ msgid ""
" <placeholder-1/>Every security group rule is a policy that allows you to "
"specify inbound connections that can access the instance by source address, "
"destination port, and IP protocol (TCP, UDP or ICMP). Currently, you cannot "
"manage ipv6 and other protocols through the security rules, making them "
"manage IPv6 and other protocols through the security rules, making them "
"permitted by default. To manage such protocols, you can deploy a firewall in"
" front of your OpenStack cloud to control other types of traffic. The "
"command requires the following arguments for both TCP and UDP rules:"
@ -23745,9 +23754,9 @@ msgid ""
"<literal>88.170.60.32/27</literal>, you specify "
"<literal>88.170.60.32</literal> as the <emphasis role=\"bold\">base "
"IP</emphasis> and <literal>27</literal> as the <emphasis "
"role=\"bold\">suffix</emphasis>. Because you use an IPV4 format, only 5 bits"
"role=\"bold\">suffix</emphasis>. Because you use an IPv4 format, only 5 bits"
" are available for the host part (32 minus 27). The "
"<literal>0.0.0.0/0</literal> notation means you allow the entire IPV4 range,"
"<literal>0.0.0.0/0</literal> notation means you allow the entire IPv4 range,"
" which allows all addresses."
msgstr ""

325
doc/common/locale/ja.po

@ -1,15 +1,15 @@
#
# Translators:
# Akihiro MOTOKI <amotoki@gmail.com>, 2013
# jaegerandi <jaegerandi@gmail.com>, 2014
# Akihiro Motoki <amotoki@gmail.com>, 2013
# Andreas Jaeger <jaegerandi@gmail.com>, 2014
# Tomoyuki KATO <tomo@dream.daynight.jp>, 2012-2014
# tmak <t.makabe@gmail.com>, 2013-2014
# Toru Makabe <t.makabe@gmail.com>, 2013-2014
msgid ""
msgstr ""
"Project-Id-Version: OpenStack Manuals\n"
"POT-Creation-Date: 2014-06-03 02:30+0000\n"
"PO-Revision-Date: 2014-06-03 02:40+0000\n"
"Last-Translator: openstackjenkins <jenkins@openstack.org>\n"
"POT-Creation-Date: 2014-06-04 20:34+0000\n"
"PO-Revision-Date: 2014-06-05 04:20+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"
@ -4901,14 +4901,14 @@ msgid ""
"accessed from any IP address outside of the cloud. If you want those IP "
"addresses to access the instances, you must modify the rules for the default"
" security group."
msgstr ""
msgstr "デフォルトのセキュリティグループを使用するインスタンスは、デフォルトでクラウド外の IP アドレスからアクセスできません。これらの IP アドレスがインスタンスにアクセスしたければ、デフォルトのセキュリティグループのルールを編集する必要があります。"
#: ./doc/common/section_cli_nova_boot.xml87(para)
msgid ""
"You can also assign a floating IP address to a running instance to make it "
"accessible from outside the cloud. See <xref "
"linkend=\"manage_ip_addresses\"/>."
msgstr ""
msgstr "また、実行中のインスタンスに Flating IP アドレスを割り当て、クラウド外からアクセスできるようにすることも可能です。<xref linkend=\"manage_ip_addresses\"/>を参照してください。"
#: ./doc/common/section_cli_nova_boot.xml91(para)
msgid ""
@ -9214,7 +9214,7 @@ msgstr ""
#: ./doc/common/section_cli_nova_images.xml6(title)
msgid "Manage images with the nova client"
msgstr ""
msgstr "nova クライアントを用いたイメージの管理"
#: ./doc/common/section_cli_nova_images.xml7(para)
msgid ""
@ -9236,7 +9236,7 @@ msgstr "ボリュームを接続したインスタンスからスナップショ
#: ./doc/common/section_cli_nova_images.xml16(title)
msgid "To create an image"
msgstr ""
msgstr "イメージの作成方法"
#: ./doc/common/section_cli_nova_images.xml18(para)
#: ./doc/common/section_cli_nova_manage_images.xml17(para)
@ -9248,7 +9248,7 @@ msgid ""
"For more information, see the <link href=\"http://docs.openstack.org/trunk"
"/openstack-ops/content/snapsnots.html\">Taking Snapshots</link> in the "
"<citetitle>OpenStack Operations Guide</citetitle>."
msgstr ""
msgstr "詳細は <citetitle>OpenStack Operations Guide</citetitle> の <link href=\"http://docs.openstack.org/trunk/openstack-ops/content/snapsnots.html\">Taking Snapshots</link> を参照してください。"
#: ./doc/common/section_cli_nova_images.xml26(para)
msgid "To create the image, list instances to get the server ID:"
@ -9281,7 +9281,7 @@ msgstr "イメージの状態は <literal>SAVING</literal> から <literal>ACTIV
#: ./doc/common/section_cli_nova_images.xml86(title)
msgid "To launch an instance from your image"
msgstr ""
msgstr "イメージからのインスタンスの起動方法"
#: ./doc/common/section_cli_nova_images.xml89(para)
msgid ""
@ -10452,117 +10452,124 @@ msgstr "Database の概要"
msgid ""
"The Database service provides scalable and reliable cloud provisioning "
"functionality for both relational and non-relational database engines. Users"
" can quickly and easily utilize database features without the burden of "
"handling complex administrative tasks. Cloud users and database "
"administrators can provision and manage multiple database instances as "
"needed."
msgstr "Database は、リレーショナルデータベースと非リレーショナルデータベースの両方のエンジン向けにスケール可能な信頼できるクラウド展開機能を提供します。ユーザーは、複雑な管理作業を実行することなく、迅速かつ容易にデータベース機能を利用できます。クラウドのユーザーとデータベース管理者は、必要に応じて複数のデータベースインスタンスを展開、管理できます。"
" can quickly and easily use database features without the burden of handling"
" complex administrative tasks. Cloud users and database administrators can "
"provision and manage multiple database instances as needed."
msgstr ""
#: ./doc/common/section_getstart_trove.xml7(para)
#: ./doc/common/section_getstart_trove.xml12(para)
msgid ""
"The Database service provides resource isolation at high performance levels,"
" and automates complex administrative tasks such as deployment, "
"configuration, patching, backups, restores, and monitoring."
msgstr "Database は、高性能にリソースを分割でき、配備、設定、パッチ適用、バックアップ、リストア、監視などの複雑な管理作業を自動化します。"
#: ./doc/common/section_getstart_trove.xml9(title)
msgid "Process flow example."
msgstr "プロセスフロー例。"
#: ./doc/common/section_getstart_trove.xml16(title)
msgid "Process flow example"
msgstr ""
#: ./doc/common/section_getstart_trove.xml9(para)
msgid "Here is a high-level process flow example for using Database services:"
msgstr "これは、Database のサービスを利用するための、高レベルなプロセスフローの例です。"
#: ./doc/common/section_getstart_trove.xml17(para)
msgid "This example is a high-level process flow for using Database services:"
msgstr ""
#: ./doc/common/section_getstart_trove.xml12(para)
msgid "Administrator sets up infrastructure:"
msgstr "管理者がインフラストラクチャーをセットアップします。"
#: ./doc/common/section_getstart_trove.xml15(para)
msgid "OpenStack administrator installs the Database service."
msgstr "OpenStack 管理者が Database をインストールします。"
#: ./doc/common/section_getstart_trove.xml18(para)
#: ./doc/common/section_getstart_trove.xml21(para)
msgid ""
"She creates one image for each type of database the administrator wants to "
"have (one for MySQL, one for MongoDB, and so on)."
msgstr "管理者が使用したいデータベース種別ごとのイメージを作成します。例えば、MySQL、MongoDB などです。"
"The OpenStack Administrator configures the basic infrastructure using the "
"following steps:"
msgstr ""
#: ./doc/common/section_getstart_trove.xml23(para)
#: ./doc/common/section_getstart_trove.xml25(para)
msgid "Install the Database service."
msgstr ""
#: ./doc/common/section_getstart_trove.xml28(para)
msgid ""
"OpenStack administrator updates the datastore to use the new images, using "
"the <placeholder-1/> command."
msgstr "OpenStack 管理者は、新しいイメージを使用するために、<placeholder-1/> コマンドを使用して、データストアを更新します。"
"Create an image for each type of database. For example, one for MySQL and "
"one for MongoDB."
msgstr ""
#: ./doc/common/section_getstart_trove.xml30(para)
msgid "End user uses database service:"
msgstr "エンドユーザーがデータベースのサービスを使用します。"
#: ./doc/common/section_getstart_trove.xml33(para)
#: ./doc/common/section_getstart_trove.xml32(para)
msgid ""
"Now that the basic infrastructure is set up, an end user can create a Trove "
"instance (database) whenever the user wants, using the <placeholder-1/> "
"command."
msgstr "ここまでに基本的なインフラストラクチャーがセットアップされました。エンドユーザーが、使用したいときに <placeholder-1/> コマンドを使用して、Trove インスタンス (データベース) を作成できます。"
"Use the <placeholder-1/> command to import images and offer them to tenants."
msgstr ""
#: ./doc/common/section_getstart_trove.xml41(replaceable)
msgid "instanceID"
msgstr "instanceID"
#: ./doc/common/section_getstart_trove.xml39(para)
#: ./doc/common/section_getstart_trove.xml38(para)
msgid ""
"The end user gets the IP address of the Trove instance by using the "
"<placeholder-1/> command to get the ID of the instance, and then using the "
"<placeholder-2/> command to get the IP address."
msgstr "エンドユーザーは、インスタンスの ID を取得するために <placeholder-1/> コマンドを使用し、IP アドレスを取得するために <placeholder-2/> コマンドを使用することにより、Trove インスタンスの IP アドレスを取得します。"
"The OpenStack end user deploys the Database service using the following "
"steps:"
msgstr ""
#: ./doc/common/section_getstart_trove.xml44(para)
#: ./doc/common/section_getstart_trove.xml42(para)
msgid "Create a Database service instance using the <placeholder-1/> command."
msgstr ""
#: ./doc/common/section_getstart_trove.xml47(para)
msgid ""
"The end user can now access the Trove instance using typical database access"
" commands. MySQL example:"
msgstr "エンドユーザーは、一般的なデータベースアクセスコマンドを使用して、Trove インスタンスにアクセスできます。MySQL の例:"
"Use the <placeholder-1/> command to get the ID of the instance, followed by "
"the <placeholder-2/> command to get the IP address of it."
msgstr ""
#: ./doc/common/section_getstart_trove.xml45(replaceable)
msgid "trove_ip_address"
msgstr "trove_ip_address"
#: ./doc/common/section_getstart_trove.xml52(para)
msgid ""
"Access the Database service instance using typical database access commands."
" For example, with MySQL:"
msgstr ""
#: ./doc/common/section_getstart_trove.xml51(title)
msgid "Components:"
msgstr "コンポーネント:"
#: ./doc/common/section_getstart_trove.xml54(replaceable)
msgid "TROVE_IP_ADDRESS"
msgstr ""
#: ./doc/common/section_getstart_trove.xml51(para)
#: ./doc/common/section_getstart_trove.xml59(para)
msgid "The Database service includes the following components:"
msgstr "Database は以下のコンポーネントを含みます。"
#: ./doc/common/section_getstart_trove.xml55(para)
msgid ""
"<code>python-troveclient</code> command-line client. A CLI that communicates"
" with the <code>trove-api</code> component."
msgstr "<code>python-troveclient</code> コマンドラインクライアント。<code>trove-api</code> コンポーネントと通信する CLI。"
#: ./doc/common/section_getstart_trove.xml62(term)
msgid "<code>python-troveclient</code> command-line client"
msgstr ""
#: ./doc/common/section_getstart_trove.xml58(para)
msgid ""
"<code>trove-api</code> component. Provides an OpenStack-native RESTful API "
"that supports JSON to provision and manage Trove instances."
msgstr "<code>trove-api</code> コンポーネント。Trove インスタンスを展開、管理するために JSON をサポートする、OpenStack ネイティブ RESTful API を提供します。"
#: ./doc/common/section_getstart_trove.xml63(para)
msgid "A CLI that communicates with the <code>trove-api</code> component."
msgstr ""
#: ./doc/common/section_getstart_trove.xml62(para)
msgid ""
"<code>trove-conductor</code> service. Runs on the host, and receives "
"messages from guest instances that want to update information on the host."
msgstr "<code>trove-conductor</code> サービス。ホストで実行し、ホストに情報をアップロードしたいゲストインスタンスからのメッセージを受け取ります。"
#: ./doc/common/section_getstart_trove.xml65(para)
msgid ""
"<code>trove-taskmanager</code> service. Instruments the complex system flows"
" that support provisioning instances, managing the lifecycle of instances, "
"and performing operations on instances."
msgstr "<code>trove-taskmanager</code> サービス。インスタンスの展開、インスタンスのライフサイクルの管理、インスタンス上の処理の実行をサポートする複雑なシステムフローを備えます。"
#: ./doc/common/section_getstart_trove.xml67(term)
msgid "<code>trove-api</code> component"
msgstr ""
#: ./doc/common/section_getstart_trove.xml68(para)
msgid ""
"<code>trove-guestagent</code> service. Runs within the guest instance. "
"Manages and performs operations on the database itself."
msgstr "<code>trove-guestagent</code> サービス。ゲストインスタンスの中で実行します。データベース自身の処理を管理、実行します。"
"Provides an OpenStack-native RESTful API that supports JSON to provision and"
" manage Trove instances."
msgstr ""
#: ./doc/common/section_getstart_trove.xml72(term)
msgid "<code>trove-conductor</code> service"
msgstr ""
#: ./doc/common/section_getstart_trove.xml73(para)
msgid ""
"Runs on the host, and receives messages from guest instances that want to "
"update information on the host."
msgstr ""
#: ./doc/common/section_getstart_trove.xml77(term)
msgid "<code>trove-taskmanager</code> service"
msgstr ""
#: ./doc/common/section_getstart_trove.xml78(para)
msgid ""
"Instruments the complex system flows that support provisioning instances, "
"managing the lifecycle of instances, and performing operations on instances."
msgstr ""
#: ./doc/common/section_getstart_trove.xml83(term)
msgid "<code>trove-guestagent</code> service"
msgstr ""
#: ./doc/common/section_getstart_trove.xml84(para)
msgid ""
"Runs within the guest instance. Manages and performs operations on the "
"database itself."
msgstr ""
#: ./doc/common/section_keystone_db_sync.xml6(title)
msgid "Migrate the Identity Service database"
@ -16215,7 +16222,7 @@ msgid ""
"href=\"http://docs.openstack.org/cli-"
"reference/content/index.html\">OpenStack Command-Line Interface "
"Reference</link>."
msgstr ""
msgstr "以下の表は、イメージのプロパティを変更するために、<placeholder-1/> コマンドと <placeholder-2/> コマンドで使用できるオプション引数の一覧です。詳細は <link href=\"http://docs.openstack.org/cli-reference/content/index.html\">OpenStack Command-Line Interface Reference</link> の Image Service の章を参照してください。"
#: ./doc/common/section_cli_glance_manage_images.xml126(parameter)
msgid "--name NAME"
@ -16365,13 +16372,13 @@ msgstr "人間が理解しやすい形式でイメージの容量を表示しま
msgid ""
"The following example shows the command that you would use to upload a "
"CentOS 6.3 image in qcow2 format and configure it for public access:"
msgstr ""
msgstr "以下の例は、CentOS 6.3 イメージを qcow2 形式でアップロードし、パブリックなアクセス用に設定するために使用するコマンドを表します。"
#: ./doc/common/section_cli_glance_manage_images.xml267(para)
msgid ""
"The following example shows how to update an existing image with a "
"properties that describe the disk bus, the CD-ROM bus, and the VIF model:"
msgstr ""
msgstr "以下の例は、ディスクバス、CD-ROM バス、VIF モデルのプロパティを指定して、既存のイメージを更新する方法を表します。"
#: ./doc/common/section_cli_glance_manage_images.xml274(para)
msgid ""
@ -16383,7 +16390,7 @@ msgid ""
"models. The disadvantage of this approach is that it is not possible to run "
"operating systems that lack virtio drivers, for example, BSD, Solaris, and "
"older versions of Linux and Windows."
msgstr ""
msgstr "libvirt 仮想化ツールは現在、設定されたハイパーバイザー種別 (<filename>/etc/nova/nova.conf</filename> の <literal>libvirt_type</literal>) に基づいて、ディスク、CD-ROM、VIF のデバイスモデルを判断します。最適なパフォーマンスのために、libvirt はデフォルトでディスクと VIF (NIC) のモデルに virtio を使用します。この方法の欠点は、BSD、Solaris、古い Linux、古い Windows のような virtio ドライバーを持たないオペレーティングシステムを実行できないことです。"
#: ./doc/common/section_cli_glance_manage_images.xml280(para)
msgid ""
@ -16396,7 +16403,7 @@ msgstr "サポートされていないディスクや CD-ROM バスモデルを
msgid ""
"The valid model values depend on the <literal>libvirt_type</literal> "
"setting, as shown in the following tables."
msgstr ""
msgstr "有効なモデルの値は、以下の表にあるように <literal>libvirt_type</literal> 設定により左右されます。"
#: ./doc/common/section_cli_glance_manage_images.xml287(caption)
msgid "Disk and CD-ROM bus model values"
@ -16485,7 +16492,7 @@ msgstr "VirtualVmxnet"
msgid ""
"If you encounter problems in creating an image in Image Service or Compute, "
"the following information may help you troubleshoot the creation process."
msgstr ""
msgstr "Image Service や Compute でイメージの作成に関する問題に遭遇した場合、以下の情報が作成プロセスのトラブルシュートに役立つかもしれません。"
#: ./doc/common/section_cli_glance_manage_images.xml415(para)
msgid ""
@ -17648,21 +17655,21 @@ msgid ""
"Each OpenStack project provides a command-line client, which enables you to "
"access the project API through easy-to-use commands. For example, the "
"Compute service provides a nova command-line client."
msgstr ""
msgstr "各 OpenStack プロジェクトは、使いやすいコマンドからプロジェクトの API にアクセスできる、コマンドラインクライアントを提供しています。例えば、Compute は nova コマンドラインクライアントを提供しています。"
#: ./doc/common/section_cli_overview.xml13(para)
msgid ""
"You can run the commands from the command line, or include the commands "
"within scripts to automate tasks. If you provide OpenStack credentials, such"
" as your user name and password, you can run these commands on any computer."
msgstr ""
msgstr "コマンドライン、または作業を自動化するスクリプトの中からコマンドを実行できます。ユーザー名とパスワードのような、OpenStack のクレデンシャルを指定すると、どのコンピューターでもこれらのコマンドを実行できます。"
#: ./doc/common/section_cli_overview.xml19(para)
msgid ""
"Internally, each command uses cURL command-line tools, which embed API "
"requests. OpenStack APIs are RESTful APIs, and use the HTTP protocol. They "
"include methods, URIs, media types, and response codes."
msgstr ""
msgstr "内部的に、各コマンドは API リクエストを組み込んだ cURL コマンドラインツールを使用します。OpenStack API は HTTP プロトコルを使用する RESTful API です。メソッド、URI、メディアタイプ、応答コードなどが含まれます。"
#: ./doc/common/section_cli_overview.xml24(para)
msgid ""
@ -17670,7 +17677,7 @@ msgid ""
"OS X systems. On some client commands, you can specify a <placeholder-1/> "
"parameter to show the underlying API request for the command. This is a good"
" way to become familiar with the OpenStack API calls."
msgstr ""
msgstr "OpenStack API はオープンソースの Python クライアントです。Linux や Mac OS X のシステムで実行できます。いくつかのクライアントコマンドでは、コマンドのベースになる API リクエストを表示するために、<placeholder-1/> パラメーターを指定できます。これは OpenStack API コールに慣れるために良い方法です。"
#: ./doc/common/section_cli_overview.xml30(para)
msgid ""
@ -18523,7 +18530,7 @@ msgid ""
msgstr ""
#: ./doc/common/section_getstart_networking.xml31(term)
#: ./doc/common/section_getstart_block-storage.xml35(term)
#: ./doc/common/section_getstart_block-storage.xml43(term)
msgid "Messaging queue"
msgstr ""
@ -18675,54 +18682,56 @@ msgstr "OpenStack Block Storage"
#: ./doc/common/section_getstart_block-storage.xml6(para)
msgid ""
"OpenStack Block Storage enables management of volumes, volume snapshots, and"
" volume types. It consists of the following components:"
msgstr ""
#: ./doc/common/section_getstart_block-storage.xml11(systemitem)
msgid "cinder-api"
"The Openstack Block Storage service (cinder) adds persistent storage to a "
"virtual machine. Block Storage provides an infrastructure for managing "
"volumes, and interacts with OpenStack Compute to provide volumes for "
"instances. The service also enables management of volume snapshots, and "
"volume types."
msgstr ""
#: ./doc/common/section_getstart_block-storage.xml12(para)
msgid "The Block Storage service consists of the following components:"
msgstr ""
#: ./doc/common/section_getstart_block-storage.xml16(systemitem)
msgid "cinder-api"
msgstr ""
#: ./doc/common/section_getstart_block-storage.xml17(para)
msgid ""
"Accepts API requests and routes them to <systemitem class=\"service"
"Accepts API requests, and routes them to the <systemitem class=\"service"
"\">cinder-volume</systemitem> for action."
msgstr ""
#: ./doc/common/section_getstart_block-storage.xml17(systemitem)
#: ./doc/common/section_getstart_block-storage.xml22(systemitem)
msgid "cinder-volume"
msgstr ""
#: ./doc/common/section_getstart_block-storage.xml18(para)
#: ./doc/common/section_getstart_block-storage.xml23(para)
msgid ""
"Responds to requests to read from and write to the OpenStack Block Storage "
"database to maintain state, interacting with other processes (like "
"<systemitem class=\"service\">cinder-scheduler</systemitem>) through a "
"message queue and directly upon block storage providing hardware or "
"software. It can interact with a variety of storage providers through a "
"driver architecture."
"Interacts directly with the Block Storage service, and processes such as the"
" <systemitem class=\"service\">cinder-scheduler</systemitem>. It also "
"interacts with these processes through a message queue. The <systemitem"
">cinder-volume service</systemitem> responds to read and write requests sent"
" to the Block Storage service to maintain state. It can interact with a "
"variety of storage providers through a driver architecture."
msgstr ""
#: ./doc/common/section_getstart_block-storage.xml28(term)
#: ./doc/common/section_getstart_block-storage.xml35(term)
msgid "<systemitem class=\"service\">cinder-scheduler</systemitem> daemon"
msgstr ""
#: ./doc/common/section_getstart_block-storage.xml30(para)
#: ./doc/common/section_getstart_block-storage.xml37(para)
msgid ""
"Like the <systemitem class=\"service\">nova-scheduler</systemitem>, picks "
"the optimal block storage provider node on which to create the volume."
"Selects the optimal storage provider node on which to create the volume. A "
"similar component to the <systemitem class=\"service\">nova-"
"scheduler</systemitem>."
msgstr ""
#: ./doc/common/section_getstart_block-storage.xml36(para)
#: ./doc/common/section_getstart_block-storage.xml44(para)
msgid "Routes information between the Block Storage processes."
msgstr ""
#: ./doc/common/section_getstart_block-storage.xml40(para)
msgid ""
"OpenStack Block Storage interacts with OpenStack Compute to provide volumes "
"for instances."
msgstr ""
#: ./doc/common/section_dashboard-configure-vnc-window.xml6(title)
msgid "Change the size of the dashboard VNC window"
msgstr ""
@ -19941,7 +19950,7 @@ msgid ""
"Administrative users can use the <guilabel>Admin</guilabel> tab to view "
"usage and to manage instances, volumes, flavors, images, projects, users, "
"services, and quotas."
msgstr ""
msgstr "管理ユーザーは、使用状況を表示するため、インスタンス、ボリューム、フレーバー、イメージ、プロジェクト、ユーザー、サービス、クォータを管理するために、<guilabel>管理</guilabel>タブを使用できます。"
#: ./doc/common/section_dashboard_access.xml209(title)
msgid "Admin tab"
@ -19973,7 +19982,7 @@ msgstr "日次レポート"
#: ./doc/common/section_dashboard_access.xml271(para)
msgid "View the daily report."
msgstr ""
msgstr "日時レポートを表示します。"
#: ./doc/common/section_dashboard_access.xml275(guilabel)
msgid "Stats"
@ -21428,26 +21437,26 @@ msgstr ""
#: ./doc/common/section_cli_nova_manage_images.xml6(title)
msgid "Create an image (nova)"
msgstr ""
msgstr "イメージの作成 (nova)"
#: ./doc/common/section_cli_nova_manage_images.xml7(para)
msgid ""
"You can use the <placeholder-1/> client to take a snapshot of a running "
"instance to create an image."
msgstr ""
msgstr "イメージを作成するために、実行中のインスタンスのスナップショットを取得するために、<placeholder-1/> クライアントを使用できます。"
#: ./doc/common/section_cli_nova_manage_images.xml9(para)
msgid ""
"To minimize the potential for data loss and ensure that you create an "
"accurate image, you should shut down the instance before you take a "
"snapshot."
msgstr ""
msgstr "データ損失の可能性を最小化し、確実に正確なイメージを作成するために、スナップショットを取得する前に、インスタンスを停止すべきです。"
#: ./doc/common/section_cli_nova_manage_images.xml12(para)
msgid ""
"You cannot create a snapshot from an instance that has an attached volume. "
"Detach the volume, create the image, and remount the volume."
msgstr ""
msgstr "ボリュームを接続したインスタンスからスナップショットを作成できません。ボリュームを切断し、イメージを作成し、ボリュームを再マウントします。"
#: ./doc/common/section_cli_nova_manage_images.xml18(para)
msgid ""
@ -21458,25 +21467,25 @@ msgstr "詳細情報は、<citetitle>OpenStack 運用ガイド</citetitle> の<l
#: ./doc/common/section_cli_nova_manage_images.xml24(para)
msgid "List instances to get the server name:"
msgstr ""
msgstr "サーバー名を取得するために、インスタンスを一覧表示します。"
#: ./doc/common/section_cli_nova_manage_images.xml31(para)
msgid ""
"In this example, the server is named <literal>myCirrosServer</literal>."
msgstr ""
msgstr "この例では、サーバー名が <literal>myCirrosServer</literal> です。"
#: ./doc/common/section_cli_nova_manage_images.xml33(para)
msgid ""
"Use this server to create a snapshot: <placeholder-1/>The command creates a "
"qemu snapshot and automatically uploads the image to your repository. Only "
"the tenant that creates the image has access to it."
msgstr ""
msgstr "このサーバーを使用して、スナップショットを作成します。<placeholder-1/> このコマンドは、qemu スナップショットを作成して、お使いのリポジトリにイメージを自動的にアップロードします。イメージを作成したテナントのみ、そのイメージにアクセスすることができます。"
#: ./doc/common/section_cli_nova_manage_images.xml81(para)
msgid ""
"To launch an instance from your image, include the image ID and flavor ID, "
"as in the following example:"
msgstr ""
msgstr "イメージからインスタンスを起動するには、以下の例のように、イメージ ID とフレーバー ID を含めます。"
#: ./doc/common/section_keystone-concepts-group-management.xml6(title)
msgid "Groups"
@ -21629,14 +21638,14 @@ msgid ""
"Most Linux distributions include packaged versions of the command-line "
"clients that you can install directly, see <xref "
"linkend=\"cli_clients_install_packages\"/>."
msgstr ""
msgstr "多くの Linux ディストリビューションは、コマンドラインクライアントのパッケージを持っており、直接インストールできます。<xref linkend=\"cli_clients_install_packages\"/>を参照してください。"
#: ./doc/common/section_cli_install.xml17(para)
msgid ""
"If you need to install the command-line packages source packages, the "
"following table lists the software that you need to have to run the command-"
"line clients, and provides installation instructions as needed."
msgstr ""
msgstr "コマンドラインパッケージのソースパッケージをインストールする必要がある場合、以下の表がコマンドラインクライアントを実行するために必要となるソフトウェアの一覧です。必要に応じてインストール手順が書かれています。"
#: ./doc/common/section_cli_install.xml24(caption)
msgid "Prerequisite software"
@ -21697,7 +21706,7 @@ msgid ""
"latest version of the clients from the <link "
"href=\"http://pypi.python.org/\">Python Package Index</link>, and lets you "
"update or remove the packages later on."
msgstr ""
msgstr "Linux、Mac OS X、Microsoft Windows システムにクライアントをインストールするために、<package>pip</package> を使用します。これは使いやすく、必ず <link href=\"http://pypi.python.org/\">Python Package Index</link> から最新バージョンのクライアントを取得します。後からパッケージの更新や削除ができます。"
#: ./doc/common/section_cli_install.xml81(para)
msgid ""
@ -21724,7 +21733,7 @@ msgstr "<filename>C:\\Python27\\Scripts</filename> ディレクトリが <litera
#: ./doc/common/section_cli_install.xml106(title)
msgid "Ubuntu and Debian"
msgstr "Ubuntu と Debian"
msgstr "Ubuntu、Debian"
#: ./doc/common/section_cli_install.xml112(title)
msgid "Red Hat Enterprise Linux, CentOS, or Fedora"
@ -21737,11 +21746,11 @@ msgid ""
"available in <link href=\"http://openstack.redhat.com/\">RDO</link> that "
"enable <package>yum</package> to install the clients as described in <xref "
"linkend=\"cli_clients_install_packages\"/>."
msgstr ""
msgstr "パッケージをインストールするために <package>yum</package> を使用できます。 <placeholder-1/> <xref linkend=\"cli_clients_install_packages\"/>に記載されているとおり、クライアントをインストールするために <package>yum</package> を使用できる、クライアントパッケージが <link href=\"http://openstack.redhat.com/\">RDO</link> にあります。"
#: ./doc/common/section_cli_install.xml125(title)
msgid "SUSE Linux Enterprise Linux 11"
msgstr ""
msgstr "SUSE Linux Enterprise Linux 11"
#: ./doc/common/section_cli_install.xml126(para)
msgid ""
@ -21753,7 +21762,7 @@ msgid ""
"client installation: <placeholder-2/> There are also packaged versions of "
"the clients available that enable <package>zypper</package> to install the "
"clients as described in <xref linkend=\"cli_clients_install_packages\"/>."
msgstr ""
msgstr "<link href=\"https://build.opensuse.org/package/show?package=python-pip&amp;project=Cloud:OpenStack:Master\">Open Build Service にあるパッケージ</link>により、パッケージをインストールするために <package>zypper</package> を使用できます。まず、Open Build Service リポジトリを追加します。 <placeholder-1/> 次に、<package>pip</package> をインストールし、クライアントのインストールを管理するために使用します。 <placeholder-2/> <xref linkend=\"cli_clients_install_packages\"/>に記載されているとおり、<package>zypper</package> がクライアントをインストールできるようにするために、クライアントのパッケージバージョンを利用できます。"
#: ./doc/common/section_cli_install.xml141(title)
msgid "openSUSE"
@ -21765,7 +21774,7 @@ msgid ""
"installation: <placeholder-1/> There are also packaged versions of the "
"clients available that enable <package>zypper</package> to install the "
"clients as described in <xref linkend=\"cli_clients_install_packages\"/>"
msgstr ""
msgstr "<package>pip</package> をインストールし、クライアントのインストールを管理するために使用できます。 <placeholder-1/> <xref linkend=\"cli_clients_install_packages\"/>に記載されているとおり、<package>zypper</package> がクライアントをインストールできるようにするために、クライアントのパッケージバージョンを利用できます。"
#: ./doc/common/section_cli_install.xml157(title)
msgid "Install the clients"
@ -21865,7 +21874,7 @@ msgstr "パッケージからのインストール"
msgid ""
"RDO, openSUSE and SUSE Linux Enterprise have client packages that can be "
"installed without <filename>pip</filename>."
msgstr ""
msgstr "RDO、openSUSE、SUSE Linux Enterprise は、<filename>pip</filename> を使用せずにインストールできるクライアントパッケージがあります。"
#: ./doc/common/section_cli_install.xml227(para)
msgid ""
@ -21878,7 +21887,7 @@ msgstr "Red Hat Enterprise Linux、CentOS、Fedora の場合、<link href=\"http
msgid ""
"For openSUSE, use <package>zypper</package> to install the clients from the "
"distribution packages Service: <placeholder-1/>"
msgstr ""
msgstr "openSUSE の場合、ディストリビューションのパッケージサービスからクライアントをインストールするために <package>zypper</package> を使用します。<placeholder-1/>"
#: ./doc/common/section_cli_install.xml237(para)
msgid ""
@ -21886,7 +21895,7 @@ msgid ""
"the clients from the distribution packages in the Open Build Service. First,"
" add the Open Build Service repository: <placeholder-1/> Then you can "
"install the packages: <placeholder-2/>"
msgstr ""
msgstr "SUSE Linux Enterprise Server の場合、Open Build Service にあるディストリビューションのパッケージからクライアントをインストールするために <package>zypper</package> を使用します。"
#: ./doc/common/section_cli_install.xml248(title)
msgid "Upgrade or remove clients"
@ -22011,7 +22020,7 @@ msgstr "controller"
#: ./doc/common/section_config_format.xml32(para)
msgid ""
"Options can have different type for values. The comments in the sample "
"Options can have different types for values. The comments in the sample "
"config files always mention these. The following types are used by "
"OpenStack:"
msgstr ""
@ -22338,8 +22347,8 @@ msgstr ""
#: ./doc/common/section_config_format.xml128(para)
msgid ""
"Configuration options are grouped by section. Most configuration file "
"supports at least the following sections: <placeholder-1/>"
"Configuration options are grouped by section. Most configuration files "
"support at least the following sections: <placeholder-1/>"
msgstr ""
#: ./doc/common/section_config_format.xml158(title)
@ -23646,7 +23655,7 @@ msgid ""
" <placeholder-1/>Every security group rule is a policy that allows you to "
"specify inbound connections that can access the instance by source address, "
"destination port, and IP protocol (TCP, UDP or ICMP). Currently, you cannot "
"manage ipv6 and other protocols through the security rules, making them "
"manage IPv6 and other protocols through the security rules, making them "
"permitted by default. To manage such protocols, you can deploy a firewall in"
" front of your OpenStack cloud to control other types of traffic. The "
"command requires the following arguments for both TCP and UDP rules:"
@ -23734,9 +23743,9 @@ msgid ""
"<literal>88.170.60.32/27</literal>, you specify "
"<literal>88.170.60.32</literal> as the <emphasis role=\"bold\">base "
"IP</emphasis> and <literal>27</literal> as the <emphasis "
"role=\"bold\">suffix</emphasis>. Because you use an IPV4 format, only 5 bits"
"role=\"bold\">suffix</emphasis>. Because you use an IPv4 format, only 5 bits"
" are available for the host part (32 minus 27). The "
"<literal>0.0.0.0/0</literal> notation means you allow the entire IPV4 range,"
"<literal>0.0.0.0/0</literal> notation means you allow the entire IPv4 range,"
" which allows all addresses."
msgstr ""

74
doc/config-reference/locale/config-reference.pot

@ -1,7 +1,7 @@
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"POT-Creation-Date: 2014-06-04 06:07+0000\n"
"POT-Creation-Date: 2014-06-05 06:07+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"
@ -1193,7 +1193,7 @@ msgstr ""
msgid "Log files used by Networking services"
msgstr ""
#: ./doc/config-reference/networking/section_networking-log-files.xml:16(td) ./doc/config-reference/dashboard/section_dashboard-log-files.xml:19(td) ./doc/config-reference/block-storage/section_cinder-log-files.xml:17(td) ./doc/config-reference/compute/section_nova-log-files.xml:17(td)
#: ./doc/config-reference/networking/section_networking-log-files.xml:16(td) ./doc/config-reference/dashboard/section_dashboard-log-files.xml:20(td) ./doc/config-reference/block-storage/section_cinder-log-files.xml:17(td) ./doc/config-reference/compute/section_nova-log-files.xml:17(td)
msgid "Log file"
msgstr ""
@ -1306,7 +1306,7 @@ msgid "pipeline.yaml"
msgstr ""
#: ./doc/config-reference/telemetry/section_telemetry-sample-configuration-files.xml:27(para)
msgid "Pipelines describe a coupling between sources of samples and the corresponding sinks for transformation and publication of these data. They are defined in the <filename>pipeline.yaml</filename> file."
msgid "Pipelines describe a coupling between sources of samples and the corresponding sinks for transformation and publication of the data. They are defined in the <filename>pipeline.yaml</filename> file."
msgstr ""
#: ./doc/config-reference/telemetry/section_telemetry-sample-configuration-files.xml:36(para)
@ -1354,7 +1354,7 @@ msgid "Cross-origin resource sharing"
msgstr ""
#: ./doc/config-reference/object-storage/section_object-storage-cors.xml:7(para)
msgid "Cross-Origin Resource Sharing (CORS) is a mechanism to allow code running in a browser (JavaScript for example) to make requests to a domain other then the one from where it originated. OpenStack Object Storage supports CORS requests to containers and objects within the containers using metadata held on the container."
msgid "Cross-Origin Resource Sharing (CORS) is a mechanism that allows code running in a browser (JavaScript for example) to make requests to a domain, other than the one it was originated from. OpenStack Object Storage supports CORS requests to containers and objects within the containers using metadata held on the container."
msgstr ""
#: ./doc/config-reference/object-storage/section_object-storage-cors.xml:11(para)
@ -1378,7 +1378,7 @@ msgid "Default configuration options are set in the `[DEFAULT]` section, and any
msgstr ""
#: ./doc/config-reference/object-storage/section_object-storage-general-service-conf.xml:19(para)
msgid "Configuration for servers and daemons can be expressed together in the same file for each type of server, or separately. If a required section for the service trying to start is missing there will be an error. Sections not used by the service are ignored."
msgid "Configuration for servers and daemons can be expressed together in the same file for each type of server, or separately. If a required section for the service trying to start is missing, there will be an error. Sections not used by the service are ignored."
msgstr ""
#: ./doc/config-reference/object-storage/section_object-storage-general-service-conf.xml:25(para)
@ -1394,7 +1394,7 @@ msgid "If you omit the object-auditor section, this file cannot be used as the c
msgstr ""
#: ./doc/config-reference/object-storage/section_object-storage-general-service-conf.xml:67(para)
msgid "If the configuration path is a directory instead of a file all of the files in the directory with the file extension \".conf\" will be combined to generate the configuration object which is delivered to the Object Storage service. This is referred to generally as \"directory-based configuration\"."
msgid "If the configuration path is a directory instead of a file, all of the files in the directory with the file extension \".conf\" will be combined to generate the configuration object which is delivered to the Object Storage service. This is referred to generally as \"directory-based configuration\"."
msgstr ""
#: ./doc/config-reference/object-storage/section_object-storage-general-service-conf.xml:74(para)
@ -1911,7 +1911,7 @@ msgid "Alternatively, if you have configured the Ubuntu Cloud Archive, you may u
msgstr ""
#: ./doc/config-reference/object-storage/section_configure_s3.xml:49(para)
msgid "To add this middleware to your configuration, add the <systemitem>swift3</systemitem> middleware in front of the <systemitem>swauth</systemitem> middleware, and before any other middleware that look at Object Storage requests (like rate limiting)."
msgid "To add this middleware to your configuration, add the <systemitem>swift3</systemitem> middleware in front of the <systemitem>swauth</systemitem> middleware, and before any other middleware that looks at Object Storage requests (like rate limiting)."
msgstr ""
#: ./doc/config-reference/object-storage/section_configure_s3.xml:52(para)
@ -1927,7 +1927,7 @@ msgid "Now you can send commands to the endpoint, such as:"
msgstr ""
#: ./doc/config-reference/object-storage/section_configure_s3.xml:68(para)
msgid "To set up your client, ensure you are using the ec2 credentials, which can be downloaded from the <guilabel>API Endpoints</guilabel> tab of the dashboard. The host should also point to the Object Storage storage node's hostname. It also will have to use the old-style calling format, and not the hostname-based container format. Here is an example client setup using the Python boto library on a locally installed all-in-one Object Storage installation."
msgid "To set up your client, ensure you are using the ec2 credentials, which can be downloaded from the <guilabel>API Endpoints</guilabel> tab of the dashboard. The host should also point to the Object Storage node's hostname. It also will have to use the old-style calling format, and not the hostname-based container format. Here is an example client setup using the Python boto library on a locally installed all-in-one Object Storage installation."
msgstr ""
#: ./doc/config-reference/object-storage/section_object-storage-listendpoints.xml:6(title)
@ -2027,35 +2027,39 @@ msgid "The <filename>nova_policy.json</filename> file must match the Compute <fi
msgstr ""
#: ./doc/config-reference/dashboard/section_dashboard-log-files.xml:6(title)
msgid "Log files used by the dashboard"
msgid "Dashboard log files"
msgstr ""
#: ./doc/config-reference/dashboard/section_dashboard-log-files.xml:7(para)
msgid "The dashboard is served to users through the Apache web server (<systemitem>httpd</systemitem>). As a result, logs relating to the dashboard appear in the following files in the <filename>/var/log/httpd</filename> or <filename>/var/log/apache2</filename> directory of where the dashboard is hosted."
msgid "The dashboard is served to users through the Apache web server (<systemitem>httpd</systemitem>)."
msgstr ""
#: ./doc/config-reference/dashboard/section_dashboard-log-files.xml:14(caption)
msgid "Log files used by the dashboard/httpd"
#: ./doc/config-reference/dashboard/section_dashboard-log-files.xml:9(para)
msgid "As a result, dashboard-related logs appear in files in the <filename>/var/log/httpd</filename> or <filename>/var/log/apache2</filename> directory on the system where the dashboard is hosted. The following table describes these files:"
msgstr ""
#: ./doc/config-reference/dashboard/section_dashboard-log-files.xml:22(td) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:309(th) ./doc/config-reference/block-storage/drivers/ibm-gpfs-volume-driver.xml:80(th) ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:322(td) ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:206(th) ./doc/config-reference/block-storage/drivers/coraid-driver.xml:358(th) ./doc/config-reference/compute/section_compute-scheduler.xml:614(th) ./doc/config-reference/compute/section_compute-scheduler.xml:695(th)
#: ./doc/config-reference/dashboard/section_dashboard-log-files.xml:15(caption)
msgid "Dashboard/httpd log files"
msgstr ""
#: ./doc/config-reference/dashboard/section_dashboard-log-files.xml:21(td) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:309(th) ./doc/config-reference/block-storage/drivers/ibm-gpfs-volume-driver.xml:80(th) ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:322(td) ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:206(th) ./doc/config-reference/block-storage/drivers/coraid-driver.xml:358(th) ./doc/config-reference/compute/section_compute-scheduler.xml:614(th) ./doc/config-reference/compute/section_compute-scheduler.xml:695(th)
msgid "Description"
msgstr ""
#: ./doc/config-reference/dashboard/section_dashboard-log-files.xml:30(filename)
#: ./doc/config-reference/dashboard/section_dashboard-log-files.xml:26(filename)
msgid "access_log"
msgstr ""
#: ./doc/config-reference/dashboard/section_dashboard-log-files.xml:32(td)
msgid "This file logs all attempts to access the web server."
#: ./doc/config-reference/dashboard/section_dashboard-log-files.xml:27(td)
msgid "Logs all attempts to access the web server."
msgstr ""
#: ./doc/config-reference/dashboard/section_dashboard-log-files.xml:38(filename)
#: ./doc/config-reference/dashboard/section_dashboard-log-files.xml:30(filename)
msgid "error_log"
msgstr ""
#: ./doc/config-reference/dashboard/section_dashboard-log-files.xml:40(td)
msgid "This file logs all unsuccessful attempts to access the web server, along with the reason each attempt/request failed."
#: ./doc/config-reference/dashboard/section_dashboard-log-files.xml:31(td)
msgid "Logs all unsuccessful attempts to access the web server, along with the reason that each attempt failed."
msgstr ""
#: ./doc/config-reference/block-storage/section_misc.xml:6(title)
@ -6339,7 +6343,7 @@ msgid "The Ceph backup driver backs up volumes of any type to a Ceph back-end st
msgstr ""
#: ./doc/config-reference/block-storage/backup/ceph-backup-driver.xml:11(para)
msgid "For source Ceph RBD volumes, you can perform backups within the same Ceph pool (not recommended) and backups between different Ceph pools and between different Ceph clusters."
msgid "For source Ceph RBD volumes, you can perform backups within the same Ceph pool (not recommended). You can also perform backups between different Ceph pools and between different Ceph clusters."
msgstr ""
#: ./doc/config-reference/block-storage/backup/ceph-backup-driver.xml:15(para)
@ -6687,11 +6691,11 @@ msgid "The Image Service has two APIs: the user-facing API, and the registry API
msgstr ""
#: ./doc/config-reference/image-service/section_image-service-api.xml:10(para)
msgid "Both of the APIs currently have two major versions, v1 and v2. It is possible to run either or both version, by setting appropriate values of <literal>enable_v1_api</literal>, <literal>enable_v2_api</literal>, <literal>enable_v1_registry</literal> and <literal>enable_v2_registry</literal>. If the v2 API is used, running <systemitem class=\"service\">glance-registry</systemitem> is optional, as v2 of <systemitem class=\"service\">glance-api</systemitem> can connect directly to the database."
msgid "Both of the APIs currently have two major versions, v1 and v2. It is possible to run either or both versions, by setting appropriate values of <literal>enable_v1_api</literal>, <literal>enable_v2_api</literal>, <literal>enable_v1_registry</literal> and <literal>enable_v2_registry</literal>. If the v2 API is used, running <systemitem class=\"service\">glance-registry</systemitem> is optional, as v2 of <systemitem class=\"service\">glance-api</systemitem> can connect directly to the database."
msgstr ""
#: ./doc/config-reference/image-service/section_image-service-api.xml:18(para)
msgid "Tables of all options used to configure the APIs, including enabling SSL and modifying WSGI settings are found below."
msgid "Tables of all the options used to configure the APIs, including enabling SSL and modifying WSGI settings are found below."
msgstr ""
#: ./doc/config-reference/image-service/section_image-service-backends.xml:6(title)
@ -8640,7 +8644,7 @@ msgid "Have sufficient RAM available (<literal>RamFilter</literal>)."
msgstr ""
#: ./doc/config-reference/compute/section_compute-scheduler.xml:47(para)
msgid "Are capable of servicing the request (<literal>ComputeFilter</literal>)."
msgid "Capable of servicing the request (<literal>ComputeFilter</literal>)."
msgstr ""
#: ./doc/config-reference/compute/section_compute-scheduler.xml:51(para)
@ -8724,7 +8728,7 @@ msgid "Matches properties defined in an image's metadata against those of aggreg
msgstr ""
#: ./doc/config-reference/compute/section_compute-scheduler.xml:155(para)
msgid "If a host belongs to an aggregate and the aggregate defines one or more metadata that match an image's properties, that host is a candidate to boot the image's instance."
msgid "If a host belongs to an aggregate and the aggregate defines one or more metadata that matches an image's properties, that host is a candidate to boot the image's instance."
msgstr ""
#: ./doc/config-reference/compute/section_compute-scheduler.xml:160(para)
@ -8812,7 +8816,7 @@ msgid "CoreFilter"
msgstr ""
#: ./doc/config-reference/compute/section_compute-scheduler.xml:255(para)
msgid "Only schedule instances on hosts if there are sufficient CPU cores available. If this filter is not set, the scheduler may over provision a host based on cores (for example, the virtual cores running on an instance may exceed the physical cores)."
msgid "Only schedules instances on hosts if there are sufficient CPU cores available. If this filter is not set, the scheduler may over-provision a host based on cores (for example, the virtual cores running on an instance may exceed the physical cores)."
msgstr ""
#: ./doc/config-reference/compute/section_compute-scheduler.xml:260(para)
@ -8836,7 +8840,7 @@ msgid "DifferentHostFilter"
msgstr ""
#: ./doc/config-reference/compute/section_compute-scheduler.xml:286(para)
msgid "Schedule the instance on a different host from a set of instances. To take advantage of this filter, the requester must pass a scheduler hint, using <literal>different_host</literal> as the key and a list of instance uuids as the value. This filter is the opposite of the <literal>SameHostFilter</literal>. Using the <placeholder-1/> command-line tool, use the <literal>--hint</literal> flag. For example:"
msgid "Schedules the instance on a different host from a set of instances. To take advantage of this filter, the requester must pass a scheduler hint, using <literal>different_host</literal> as the key and a list of instance uuids as the value. This filter is the opposite of the <literal>SameHostFilter</literal>. Using the <placeholder-1/> command-line tool, use the <literal>--hint</literal> flag. For example:"
msgstr ""
#: ./doc/config-reference/compute/section_compute-scheduler.xml:298(para)
@ -8848,7 +8852,7 @@ msgid "DiskFilter"
msgstr ""
#: ./doc/config-reference/compute/section_compute-scheduler.xml:305(para)
msgid "Only schedule instances on hosts if there is sufficient disk space available for root and ephemeral storage."
msgid "Only schedules instances on hosts if there is sufficient disk space available for root and ephemeral storage."
msgstr ""
#: ./doc/config-reference/compute/section_compute-scheduler.xml:308(para)
@ -8856,7 +8860,7 @@ msgid "This filter can be configured to allow a fixed amount of disk overcommitm
msgstr ""
#: ./doc/config-reference/compute/section_compute-scheduler.xml:315(para)
msgid "Adjusting this value to greater than 1.0 enables scheduling instances while over committing disk resources on the node. This might be desirable if you use an image format that is sparse or copy on write such that each virtual instance does not require a 1:1 allocation of virtual disk to physical storage."
msgid "Adjusting this value to greater than 1.0 enables scheduling instances while over committing disk resources on the node. This might be desirable if you use an image format that is sparse or copy on write so that each virtual instance does not require a 1:1 allocation of virtual disk to physical storage."
msgstr ""
#: ./doc/config-reference/compute/section_compute-scheduler.xml:323(title)
@ -9004,7 +9008,7 @@ msgid "RamFilter"
msgstr ""
#: ./doc/config-reference/compute/section_compute-scheduler.xml:474(para)
msgid "Only schedule instances on hosts that have sufficient RAM available. If this filter is not set, the scheduler may over provision a host based on RAM (for example, the RAM allocated by virtual machine instances may exceed the physical RAM)."
msgid "Only schedules instances on hosts that have sufficient RAM available. If this filter is not set, the scheduler may over provision a host based on RAM (for example, the RAM allocated by virtual machine instances may exceed the physical RAM)."
msgstr ""
#: ./doc/config-reference/compute/section_compute-scheduler.xml:479(para)
@ -9020,7 +9024,7 @@ msgid "RetryFilter"
msgstr ""
#: ./doc/config-reference/compute/section_compute-scheduler.xml:492(para)
msgid "Filter out hosts that have already been attempted for scheduling purposes. If the scheduler selects a host to respond to a service request, and the host fails to respond to the request, this filter prevents the scheduler from retrying that host for the service request."
msgid "Filters out hosts that have already been attempted for scheduling purposes. If the scheduler selects a host to respond to a service request, and the host fails to respond to the request, this filter prevents the scheduler from retrying that host for the service request."
msgstr ""
#: ./doc/config-reference/compute/section_compute-scheduler.xml:498(para)
@ -9032,7 +9036,7 @@ msgid "SameHostFilter"
msgstr ""
#: ./doc/config-reference/compute/section_compute-scheduler.xml:505(para)
msgid "Schedule the instance on the same host as another instance in a set of instances. To take advantage of this filter, the requester must pass a scheduler hint, using <literal>same_host</literal> as the key and a list of instance uuids as the value. This filter is the opposite of the <literal>DifferentHostFilter</literal>. Using the <placeholder-1/> command-line tool, use the <literal>--hint</literal> flag:"
msgid "Schedules the instance on the same host as another instance in a set of instances. To take advantage of this filter, the requester must pass a scheduler hint, using <literal>same_host</literal> as the key and a list of instance uuids as the value. This filter is the opposite of the <literal>DifferentHostFilter</literal>. Using the <placeholder-1/> command-line tool, use the <literal>--hint</literal> flag:"
msgstr ""
#: ./doc/config-reference/compute/section_compute-scheduler.xml:522(title)
@ -9060,7 +9064,7 @@ msgid "SimpleCIDRAffinityFilter"
msgstr ""
#: ./doc/config-reference/compute/section_compute-scheduler.xml:551(para)
msgid "Schedule the instance based on host IP subnet range. To take advantage of this filter, the requester must specify a range of valid IP address in CIDR format, by passing two scheduler hints:"
msgid "Schedules the instance based on host IP subnet range. To take advantage of this filter, the requester must specify a range of valid IP address in CIDR format, by passing two scheduler hints:"
msgstr ""
#: ./doc/config-reference/compute/section_compute-scheduler.xml:557(literal)
@ -9260,7 +9264,7 @@ msgid "Hypervisors"
msgstr ""
#: ./doc/config-reference/compute/section_compute-hypervisors.xml:7(para)
msgid "OpenStack Compute supports many hypervisors, which might make it difficult for you to choose one. Most installations use only one hypervisor. However you can use <xref linkend=\"computefilter\"/> and <xref linkend=\"imagepropertiesfilter\"/> to schedule to different hypervisors within the same installation. The following links help you choose a hypervisor. See <link href=\"http://wiki.openstack.org/HypervisorSupportMatrix\">http://wiki.openstack.org/HypervisorSupportMatrix</link> for a detailed list of features and support across the hypervisors."
msgid "OpenStack Compute supports many hypervisors, which might make it difficult for you to choose one. Most installations use only one hypervisor. However, you can use <xref linkend=\"computefilter\"/> and <xref linkend=\"imagepropertiesfilter\"/> to schedule different hypervisors within the same installation. The following links help you choose a hypervisor. See <link href=\"http://wiki.openstack.org/HypervisorSupportMatrix\">http://wiki.openstack.org/HypervisorSupportMatrix</link> for a detailed list of features and support across the hypervisors."
msgstr ""
#: ./doc/config-reference/compute/section_compute-hypervisors.xml:18(para)
@ -9304,7 +9308,7 @@ msgid "Hypervisor configuration basics"
msgstr ""
#: ./doc/config-reference/compute/section_compute-hypervisors.xml:79(para)
msgid "The node where the <systemitem class=\"service\">nova-compute</systemitem> service is installed and running is the machine that runs all the virtual machines, referred to as the compute node in this guide."
msgid "The node where the <systemitem class=\"service\">nova-compute</systemitem> service is installed and operates on the same node that runs all of the virtual machines. This is referred to as the compute node in this guide."
msgstr ""
#: ./doc/config-reference/compute/section_compute-hypervisors.xml:83(para)
@ -9316,7 +9320,7 @@ msgid "Here are the general <filename>nova.conf</filename> options that are used
msgstr ""
#: ./doc/config-reference/compute/section_compute-hypervisors.xml:90(para)
msgid "Specific options for particular hypervisors can be found in following sections."
msgid "Specific options for particular hypervisors can be found in the following sections."
msgstr ""
#: ./doc/config-reference/compute/section_compute-conductor.xml:7(title)

162
doc/install-guide/locale/install-guide.pot

File diff suppressed because one or more lines are too long

235
doc/install-guide/locale/ja.po

@ -5,8 +5,8 @@
msgid ""
msgstr ""
"Project-Id-Version: OpenStack Manuals\n"
"POT-Creation-Date: 2014-06-03 23:53+0000\n"
"PO-Revision-Date: 2014-06-03 06:51+0000\n"
"POT-Creation-Date: 2014-06-04 20:34+0000\n"
"PO-Revision-Date: 2014-06-04 22:11+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"
@ -136,12 +136,12 @@ msgstr "KEYSTONE_DBPASS"
#: ./doc/install-guide/section_ceilometer-nova.xml122(replaceable)
#: ./doc/install-guide/section_nova-controller.xml44(replaceable)
#: ./doc/install-guide/section_nova-controller.xml59(replaceable)
#: ./doc/install-guide/section_nova-controller.xml139(replaceable)
#: ./doc/install-guide/section_nova-controller.xml140(replaceable)
#: ./doc/install-guide/section_nova-controller.xml141(replaceable)
#: ./doc/install-guide/section_nova-controller.xml160(replaceable)
#: ./doc/install-guide/section_nova-controller.xml177(replaceable)
#: ./doc/install-guide/section_nova-controller.xml178(replaceable)
#: ./doc/install-guide/section_nova-controller.xml179(replaceable)
#: ./doc/install-guide/section_nova-controller.xml151(replaceable)
#: ./doc/install-guide/section_nova-controller.xml168(replaceable)
#: ./doc/install-guide/section_nova-controller.xml169(replaceable)
#: ./doc/install-guide/section_nova-controller.xml170(replaceable)
#: ./doc/install-guide/section_basics-networking-neutron.xml277(replaceable)
#: ./doc/install-guide/section_basics-networking-neutron.xml321(replaceable)
#: ./doc/install-guide/section_neutron-ovs-compute-node.xml143(replaceable)
@ -208,15 +208,15 @@ msgstr "KEYSTONE_DBPASS"
#: ./doc/install-guide/section_neutron-ml2-compute-node.xml328(replaceable)
#: ./doc/install-guide/section_neutron-ml2-compute-node.xml333(replaceable)
#: ./doc/install-guide/section_basics-networking-nova.xml202(replaceable)
#: ./doc/install-guide/section_nova-compute.xml73(replaceable)
#: ./doc/install-guide/section_nova-compute.xml74(replaceable)
#: ./doc/install-guide/section_nova-compute.xml75(replaceable)
#: ./doc/install-guide/section_nova-compute.xml93(replaceable)
#: ./doc/install-guide/section_nova-compute.xml94(replaceable)
#: ./doc/install-guide/section_nova-compute.xml106(replaceable)
#: ./doc/install-guide/section_nova-compute.xml131(replaceable)
#: ./doc/install-guide/section_nova-compute.xml143(replaceable)
#: ./doc/install-guide/section_nova-compute.xml151(replaceable)
#: ./doc/install-guide/section_nova-compute.xml154(replaceable)
#: ./doc/install-guide/section_nova-compute.xml89(replaceable)
#: ./doc/install-guide/section_nova-compute.xml90(replaceable)
#: ./doc/install-guide/section_nova-compute.xml102(replaceable)
#: ./doc/install-guide/section_nova-compute.xml127(replaceable)
#: ./doc/install-guide/section_nova-compute.xml139(replaceable)
#: ./doc/install-guide/section_nova-compute.xml147(replaceable)
#: ./doc/install-guide/section_nova-compute.xml150(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)
@ -277,12 +277,13 @@ msgstr "KEYSTONE_DBPASS"
#: ./doc/install-guide/section_heat-install.xml113(replaceable)
#: ./doc/install-guide/section_heat-install.xml116(replaceable)
#: ./doc/install-guide/section_heat-install.xml122(replaceable)
#: ./doc/install-guide/section_heat-install.xml133(replaceable)
#: ./doc/install-guide/section_heat-install.xml134(replaceable)
#: ./doc/install-guide/section_heat-install.xml135(replaceable)
#: ./doc/install-guide/section_heat-install.xml128(replaceable)
#: ./doc/install-guide/section_heat-install.xml139(replaceable)
#: ./doc/install-guide/section_heat-install.xml140(replaceable)
#: ./doc/install-guide/section_heat-install.xml141(replaceable)
#: ./doc/install-guide/section_heat-install.xml142(replaceable)
#: ./doc/install-guide/section_heat-install.xml146(replaceable)
#: ./doc/install-guide/section_heat-install.xml147(replaceable)
#: ./doc/install-guide/section_heat-install.xml148(replaceable)
#: ./doc/install-guide/section_neutron-ml2-network-node.xml65(replaceable)
#: ./doc/install-guide/section_neutron-ml2-network-node.xml67(replaceable)
#: ./doc/install-guide/section_neutron-ml2-network-node.xml97(replaceable)
@ -704,8 +705,8 @@ msgstr "<filename>/etc/cinder/cinder.conf</filename> ファイルの <literal>[D
#: ./doc/install-guide/section_cinder-node.xml174(replaceable)
#: ./doc/install-guide/section_neutron-ml2-compute-node.xml116(replaceable)
#: ./doc/install-guide/section_neutron-ml2-compute-node.xml139(replaceable)
#: ./doc/install-guide/section_nova-compute.xml115(replaceable)
#: ./doc/install-guide/section_nova-compute.xml121(replaceable)
#: ./doc/install-guide/section_nova-compute.xml111(replaceable)
#: ./doc/install-guide/section_nova-compute.xml117(replaceable)
#: ./doc/install-guide/section_trove-install.xml105(replaceable)
#: ./doc/install-guide/section_trove-install.xml125(replaceable)
#: ./doc/install-guide/section_trove-install.xml127(replaceable)
@ -897,13 +898,13 @@ msgstr "<package>cinder-common</package> パッケージはこれらの画面を
#: ./doc/install-guide/section_debconf-dbconfig-common.xml127(para)
msgid ""
"By default in Debian, the MySQL server is only accessible from localhost "
"using the socket file, or 127.0.0.1. To access it over network, users must "
"edit <filename>/etc/mysql/my.cnf</filename> and edit the "
"By default in Debian, you can access the MySQL server from either localhost "
"through the socket file or 127.0.0.1. To access it over the network, you "
"must edit the <filename>/etc/mysql/my.cnf</filename> file, and the "
"<literal>mysql.user</literal> table. To do so, Debian provides a helper "
"script located in the <package>openstack-deploy</package> package. To use "
"it, install the package and run:"
msgstr "Debian の場合デフォルトで、MySQL サーバーはソケットファイルを使用してローカルホスト、127.0.0.1 からのみアクセスできます。ネットワーク経由でアクセスする場合、ユーザーは <filename>/etc/mysql/my.cnf</filename> を編集し、<literal>mysql.user</literal> テーブルを編集する必要があります。このために、Debian は <package>openstack-deploy</package> パッケージにヘルパースクリプトを提供しています。使用する場合、このパッケージをインストールし、以下を実行します。"
"script in the <package>openstack-deploy</package> package. To use it, "
"install the package and run:"
msgstr "Debian の場合デフォルトで、ソケットファイルを使用してローカルホスト、または 127.0.0.1 のみから、MySQL サーバーにアクセスできます。ネットワーク経由でアクセスする場合、ユーザーは <filename>/etc/mysql/my.cnf</filename> ファイルと <literal>mysql.user</literal> テーブルを編集する必要があります。このために、Debian は <package>openstack-deploy</package> パッケージでヘルパースクリプトを提供しています。使用する場合、このパッケージをインストールし、以下を実行します。"
#: ./doc/install-guide/section_debconf-dbconfig-common.xml134(para)
msgid ""
@ -981,7 +982,7 @@ msgstr "<literal>ceilometer</literal> を同じファイルの <literal>pipeline
#: ./doc/install-guide/section_ceilometer-swift.xml41(para)
#: ./doc/install-guide/section_ceilometer-nova.xml137(para)
#: ./doc/install-guide/section_heat-install.xml180(para)
#: ./doc/install-guide/section_heat-install.xml186(para)
msgid "Restart the service with its new settings:"
msgstr "新しい設定を用いてサービスを再起動します。"
@ -1198,7 +1199,7 @@ msgstr "<filename>/etc/nova/nova.conf</filename> ファイルを編集し、<lit
#: ./doc/install-guide/section_ceilometer-nova.xml53(para)
#: ./doc/install-guide/section_neutron-ml2-compute-node.xml378(para)
#: ./doc/install-guide/section_nova-compute.xml208(para)
#: ./doc/install-guide/section_nova-compute.xml204(para)
msgid "Restart the Compute service:"
msgstr "Compute Service を再起動します。"
@ -1336,7 +1337,7 @@ msgid ""
msgstr "Compute が Qpid メッセージブローカーを使用するよう設定するために、これらの設定キーを設定します。"
#: ./doc/install-guide/section_nova-controller.xml62(para)
#: ./doc/install-guide/section_nova-compute.xml107(para)
#: ./doc/install-guide/section_nova-compute.xml103(para)
msgid ""
"Configure the Compute service to use the RabbitMQ message broker by setting "
"these configuration keys in the <literal>[DEFAULT]</literal> configuration "
@ -1398,10 +1399,10 @@ msgid ""
msgstr "Compute が Identity Service で認証するために使用する <literal>nova</literal> ユーザーを作成します。<literal>service</literal> プロジェクトを使用し、ユーザーに <literal>admin</literal> ロールを与えます。"
#: ./doc/install-guide/section_nova-controller.xml132(replaceable)
#: ./doc/install-guide/section_nova-controller.xml146(replaceable)
#: ./doc/install-guide/section_nova-controller.xml166(replaceable)
#: ./doc/install-guide/section_nova-compute.xml80(replaceable)
#: ./doc/install-guide/section_nova-compute.xml99(replaceable)
#: ./doc/install-guide/section_nova-controller.xml145(replaceable)
#: ./doc/install-guide/section_nova-controller.xml157(replaceable)
#: ./doc/install-guide/section_nova-compute.xml79(replaceable)
#: ./doc/install-guide/section_nova-compute.xml95(replaceable)
#: ./doc/install-guide/section_neutron-ml2-controller-node.xml234(replaceable)
#: ./doc/install-guide/section_neutron-ml2-controller-node.xml258(replaceable)
msgid "NOVA_PASS"
@ -1418,32 +1419,26 @@ msgid ""
"Compute password."
msgstr "コントローラーで実行している Identity Service でこれらのクレデンシャルを使用するよう Compute を設定します。<replaceable>NOVA_PASS</replaceable> をお使いの Compute パスワードで置き換えます。"
#: ./doc/install-guide/section_nova-controller.xml147(para)
msgid ""
"Edit the <literal>[DEFAULT]</literal> section in the "
"<filename>/etc/nova/nova.conf</filename> file to add this key:"
msgstr "このキーを追加するために <filename>/etc/nova/nova.conf</filename> ファイルの <literal>[DEFAULT]</literal> セクションを編集します。"
#: ./doc/install-guide/section_nova-controller.xml155(para)
#: ./doc/install-guide/section_nova-controller.xml146(para)
msgid "Add these keys to the <literal>[keystone_authtoken]</literal> section:"
msgstr "これらのキーを <literal>[keystone_authtoken]</literal> セクションに追加します。"
#: ./doc/install-guide/section_nova-controller.xml169(para)
#: ./doc/install-guide/section_nova-controller.xml160(para)
msgid ""
"You must register Compute with the Identity Service so that other OpenStack "
"services can locate it. Register the service and specify the endpoint:"
msgstr "他の OpenStack サービスから使用できるように、Compute を Identity Service に登録します。サービスを登録し、エンドポイントを指定します。"
#: ./doc/install-guide/section_nova-controller.xml182(para)
#: ./doc/install-guide/section_nova-controller.xml173(para)
msgid ""
"Start Compute services and configure them to start when the system boots:"
msgstr "Compute サービスを起動し、システム起動時に起動するよう設定します。"
#: ./doc/install-guide/section_nova-controller.xml185(para)
#: ./doc/install-guide/section_nova-controller.xml176(para)
msgid "Restart Compute services:"
msgstr "Compute サービスを再起動します。"
#: ./doc/install-guide/section_nova-controller.xml206(para)
#: ./doc/install-guide/section_nova-controller.xml197(para)
msgid "To verify your configuration, list available images:"
msgstr "設定を検証するために、使用可能なイメージを一覧表示します。"
@ -2027,8 +2022,8 @@ msgid ""
msgstr "このガイドで定義する必要のあるパスワードの完全な一覧は以下です。 <table rules=\"all\"><caption>パスワード</caption><thead><tr><th>パスワード名</th><th>説明</th></tr></thead><tbody><tr><td>データベースパスワード (変数を使用しません)</td><td>データベースの root パスワード</td></tr><tr os=\"ubuntu;opensuse;sles\"><td><literal><replaceable>RABBIT_PASS</replaceable></literal></td><td>RabbitMQ の guest ユーザーのパスワード</td></tr><tr><td><literal><replaceable>KEYSTONE_DBPASS</replaceable></literal></td><td>Identity Service のデータベースのパスワード</td></tr><tr><td><literal><replaceable>DEMO_PASS</replaceable></literal></td><td><literal>demo</literal> ユーザーのパスワード</td></tr><tr><td><literal><replaceable>ADMIN_PASS</replaceable></literal></td><td><literal>admin</literal> ユーザーのパスワード</td></tr><tr><td><literal><replaceable>GLANCE_DBPASS</replaceable></literal></td><td>Image Service のデータベースのパスワード</td></tr><tr><td><literal><replaceable>GLANCE_PASS</replaceable></literal></td><td>Image Service の <literal>glance</literal> ユーザーのパスワード</td></tr><tr><td><literal><replaceable>NOVA_DBPASS</replaceable></literal></td><td>Compute Service のデータベースのパスワード</td></tr><tr><td><literal><replaceable>NOVA_PASS</replaceable></literal></td><td>Compute Service の <literal>nova</literal> ユーザーのパスワード</td></tr><tr><td><literal><replaceable>DASH_DBPASS</replaceable></literal></td><td>Dashboard のデータベースのパスワード</td></tr><tr><td><literal><replaceable>CINDER_DBPASS</replaceable></literal></td><td>Block Storage Service のデータベースのパスワード</td></tr><tr><td><literal><replaceable>CINDER_PASS</replaceable></literal></td><td>Block Storage Service の <literal>cinder</literal> ユーザーのパスワード</td></tr><tr><td><literal><replaceable>NEUTRON_DBPASS</replaceable></literal></td><td>Networking Service のデータベースのパスワード</td></tr><tr><td><literal><replaceable>NEUTRON_PASS</replaceable></literal></td><td>Networking Service の <literal>neutron</literal> ユーザーのパスワード</td></tr><tr><td><literal><replaceable>HEAT_DBPASS</replaceable></literal></td><td>Orchestration Service のデータベースのパスワード</td></tr><tr><td><literal><replaceable>HEAT_PASS</replaceable></literal></td><td>Orchestration Service の <literal>heat</literal> ユーザーのパスワード</td></tr><tr><td><literal><replaceable>CEILOMETER_DBPASS</replaceable></literal></td><td>Telemetry Service のデータベースのパスワード</td></tr><tr><td><literal><replaceable>CEILOMETER_PASS</replaceable></literal></td><td>Telemetry Service の <literal>ceilometer</literal> ユーザーのパスワード</td></tr><tr><td><literal><replaceable>TROVE_DBPASS</replaceable></literal></td><td>Database サービスのデータベースパスワード</td></tr><tr><td><literal><replaceable>TROVE_PASS</replaceable></literal></td><td>Database サービスのユーザー <literal>trove</literal> のパスワード</td></tr></tbody></table>"
#: ./doc/install-guide/ch_keystone.xml6(title)
msgid "Configure the Identity Service"
msgstr "Identity Service の設定"
msgid "Add the Identity service"
msgstr "Identity の追加"
#: ./doc/install-guide/ch_swift.xml6(title)
msgid "Add Object Storage"
@ -3630,7 +3625,15 @@ msgstr "一般ユーザー用の <filename>demo-openrc.sh</filename>: <placehold
msgid "Basic environment configuration"
msgstr "環境の基本設定"
#: ./doc/install-guide/ch_basics.xml6(para)
#: ./doc/install-guide/ch_basics.xml8(para)
msgid ""
"The trunk version of this guide focuses on the future Juno release and may "
"not work for the current Icehouse release. If you want to install Icehouse, "
"please use the <link href=\"http://docs.openstack.org\">Icehouse "
"version</link> of this guide instead."
msgstr "このガイドの trunk バージョンは、将来の Juno リリースに注力し、現行の Icehouse リリースに対応していないかもしれません。Icehouse をインストールしたい場合、このガイドの <link href=\"http://docs.openstack.org\">Icehouse バージョン</link>を使用してください。"
#: ./doc/install-guide/ch_basics.xml17(para)
msgid ""
"This chapter explains how to configure each node in the <link linkend"
"=\"architecture_example-architectures\">example architectures</link> "
@ -3640,7 +3643,7 @@ msgid ""
"with OpenStack Networking (neutron)</link>."
msgstr "本章は、<link linkend=\"architecture_example-architectures\">アーキテクチャー例</link>にある各ノードを設定する方法について説明します。<link linkend=\"example-architecture-with-legacy-networking\"> レガシーネットワークを持つ 2 ノードアーキテクチャー</link>と<link linkend=\"example-architecture-with-neutron-networking\">OpenStack Networking (neutron) を持つ 3 ノードアーキテクチャー</link>があります。"
#: ./doc/install-guide/ch_basics.xml13(para)
#: ./doc/install-guide/ch_basics.xml24(para)
msgid ""
"Although most environments include OpenStack Identity, Image Service, "
"Compute, at least one networking service, and the dashboard, OpenStack "
@ -3650,7 +3653,7 @@ msgid ""
"without at least OpenStack Image Service and Compute."
msgstr "ほとんどの環境には、OpenStack Identity、Image Service、Compute、少なくとも 1 つのネットワークサービス、ダッシュボードがありますが、OpenStack Object Storage は他のほとんどのサービスと独立して動作できます。Object Storage のみを含むユースケースの場合、<xref linkend=\"object-storage-system-requirements\"/> まで進めます。しかしながらダッシュボードは、少なくとも OpenStack Image Service と Compute がないと動作しません。"
#: ./doc/install-guide/ch_basics.xml22(para)
#: ./doc/install-guide/ch_basics.xml33(para)
msgid ""
"You must use an account with administrative privileges to configure each "
"node. Either run the commands as the <literal>root</literal> user or "
@ -5186,74 +5189,74 @@ msgstr "セキュリティの理由から、Linux カーネルは通常のユー
msgid "Edit the <filename>/etc/nova/nova.conf</filename> configuration file:"
msgstr "<filename>/etc/nova/nova.conf</filename> 設定ファイルを編集します。"
#: ./doc/install-guide/section_nova-compute.xml81(para)
#: ./doc/install-guide/section_nova-compute.xml80(para)
msgid ""
"Edit the <filename>/etc/nova/nova.conf</filename> configuration file and add"
" these lines to the appropriate sections:"
msgstr "<filename>/etc/nova/nova.conf</filename> 設定ファイルを編集し、これらの行を適切なセクションに追加します。"
#: ./doc/install-guide/section_nova-compute.xml102(para)
#: ./doc/install-guide/section_nova-compute.xml98(para)
msgid ""
"Configure the Compute service to use the Qpid message broker by setting "
"these configuration keys:"
msgstr "これらの設定キーを設定することにより、Compute サービスが Qpid メッセージブローカーを使用するよう設定します。"
#: ./doc/install-guide/section_nova-compute.xml116(para)
#: ./doc/install-guide/section_nova-compute.xml112(para)
msgid ""
"Configure the Compute service to use the RabbitMQ message broker by setting "
"these configuration keys:"
msgstr "これらの設定キーを設定することにより、Compute サービスが RabbitMQ メッセージブローカーを使用するよう設定します。"
#: ./doc/install-guide/section_nova-compute.xml125(para)
#: ./doc/install-guide/section_nova-compute.xml121(para)
msgid "Configure Compute to provide remote console access to instances."
msgstr "インスタンスへのリモートコンソールアクセスを提供するよう Compute を設定します。"
#: ./doc/install-guide/section_nova-compute.xml132(para)
#: ./doc/install-guide/section_nova-compute.xml128(para)
msgid ""
"Edit <filename>/etc/nova/nova.conf</filename> and add the following keys "
"under the <literal>[DEFAULT]</literal> section:"
msgstr "<filename>/etc/nova/nova.conf</filename> を編集し、以下のキーを <literal>[DEFAULT]</literal> セクションに追加します。"
#: ./doc/install-guide/section_nova-compute.xml146(para)
#: ./doc/install-guide/section_nova-compute.xml142(para)
msgid ""
"Specify the host that runs the Image Service.<phrase os=\"ubuntu;debian\"> "
"Edit <filename>/etc/nova/nova.conf</filename> file and add these lines to "
"the <literal>[DEFAULT]</literal> section:</phrase>"
msgstr "Image Service を実行するホストを指定します。<phrase os=\"ubuntu;debian\"><filename>/etc/nova/nova.conf</filename> ファイルを編集し、これらの行を <literal>[DEFAULT]</literal> セクションに追加します。</phrase>"
#: ./doc/install-guide/section_nova-compute.xml157(para)
#: ./doc/install-guide/section_nova-compute.xml153(para)
msgid ""
"You must determine whether your system's processor and/or hypervisor support"
" hardware acceleration for virtual machines."
msgstr "お使いのシステムのプロセッサーとハイパーバイザーが仮想マシンのハードウェア支援機能をサポートするかどうか確認する必要があります。"
#: ./doc/install-guide/section_nova-compute.xml159(para)
#: ./doc/install-guide/section_nova-compute.xml178(para)
#: ./doc/install-guide/section_nova-compute.xml155(para)
#: ./doc/install-guide/section_nova-compute.xml174(para)
#: ./doc/install-guide/section_basics-queue.xml74(para)
msgid "Run the following command:"
msgstr "以下のコマンドを実行します。"
#: ./doc/install-guide/section_nova-compute.xml161(para)
#: ./doc/install-guide/section_nova-compute.xml157(para)
msgid ""
"If this command returns a value of <emphasis>one or greater</emphasis>, your"
" system supports hardware acceleration which typically requires no "
"additional configuration."
msgstr "このコマンドが <emphasis>1 以上</emphasis>の値を返したならば、お使いのシステムがハードウェア支援機能をサポートし、一般的に追加の設定は必要ありません。"
#: ./doc/install-guide/section_nova-compute.xml165(para)
#: ./doc/install-guide/section_nova-compute.xml161(para)
msgid ""
"If this command returns a value of <emphasis>zero</emphasis>, your system "
"does not support hardware acceleration and you must configure "
"<literal>libvirt</literal> to use QEMU instead of KVM."
msgstr "このコマンドが <emphasis>0</emphasis> を返す場合、お使いのシステムはハードウェア支援機能をサポートしません。<literal>libvirt</literal> は KVM の代わりに QEMU を使用する必要があります。"
#: ./doc/install-guide/section_nova-compute.xml170(para)
#: ./doc/install-guide/section_nova-compute.xml166(para)
msgid ""
"Edit the <literal>[libvirt]</literal> section in the <filename>/etc/nova"
"/nova-compute.conf</filename> file to modify this key:"
msgstr "このキーを変更するために <filename>/etc/nova/nova-compute.conf</filename> ファイルの <literal>[libvirt]</literal> セクションを編集します。"
#: ./doc/install-guide/section_nova-compute.xml183(para)
#: ./doc/install-guide/section_nova-compute.xml179(para)
msgid ""
"On Ubuntu 12.04, kernels backported from newer releases may not "
"automatically load the KVM modules for hardware acceleration when the system"
@ -5261,25 +5264,25 @@ msgid ""
"message in the <filename>/var/log/nova/nova-compute.log</filename> file:"
msgstr "Ubuntu 12.04 の場合、新しいカーネルからバックポートされたカーネルは、システム起動時に KVM のハードウェア支援機能のモジュールを自動的に読み込まない可能性があります。この場合、インスタンスの起動に失敗し、以下のメッセージが <filename>/var/log/nova/nova-compute.log</filename> ファイルに記録されます。"
#: ./doc/install-guide/section_nova-compute.xml189(para)
#: ./doc/install-guide/section_nova-compute.xml185(para)
msgid ""
"As a workaround for this issue, you must add the appropriate module for your"
" system to the <filename>/etc/modules</filename> file."
msgstr "この問題の回避策として、お使いのシステム用の適切なモジュールを <filename>/etc/modules</filename> ファイルに追加する必要があります。"
#: ./doc/install-guide/section_nova-compute.xml192(para)
#: ./doc/install-guide/section_nova-compute.xml188(para)
msgid "For systems with Intel processors, run the following command:"
msgstr "Intel プロセッサーのシステムの場合、以下のコマンドを実行します。"
#: ./doc/install-guide/section_nova-compute.xml195(para)
#: ./doc/install-guide/section_nova-compute.xml191(para)
msgid "For systems with AMD processors, run the following command:"
msgstr "AMD プロセッサーのシステムの場合、以下のコマンドを実行します。"
#: ./doc/install-guide/section_nova-compute.xml201(para)
#: ./doc/install-guide/section_nova-compute.xml197(para)
msgid "Remove the SQLite database created by the packages:"
msgstr "パッケージにより作成された SQLite データベースを削除します。"
#: ./doc/install-guide/section_nova-compute.xml205(para)
#: ./doc/install-guide/section_nova-compute.xml201(para)
msgid ""
"Start the Compute service and configure it to start when the system boots:"
msgstr "Compute サービスを起動し、システム起動時に起動するよう設定します。"
@ -6498,51 +6501,57 @@ msgstr "Orchestration Service のクレデンシャルを追加するために
#: ./doc/install-guide/section_heat-install.xml125(para)
msgid ""
"Edit the <filename>/etc/heat/heat.conf</filename> file to change the "
"<literal>[ec2authtoken]</literal> sections:"
msgstr "<filename>/etc/heat/heat.conf</filename> ファイルを編集し、<literal>[ec2authtoken]</literal> セクションを変更します。"
#: ./doc/install-guide/section_heat-install.xml131(para)
msgid ""
"Register the Heat and CloudFormation APIs with the Identity Service so that "
"other OpenStack services can locate these APIs. Register the services and "
"specify the endpoints:"
msgstr "他の OpenStack サービスから使用できるように、Heat と CloudFormation API を Identity Service に登録します。サービスを登録し、エンドポイントを指定します。"
#: ./doc/install-guide/section_heat-install.xml145(para)
#: ./doc/install-guide/section_heat-install.xml151(para)
msgid "Create the <literal>heat_stack_user</literal> role."
msgstr "<literal>heat_stack_user</literal> ロールを作成します。"
#: ./doc/install-guide/section_heat-install.xml146(para)
#: ./doc/install-guide/section_heat-install.xml152(para)
msgid ""
"This role is used as the default role for users created by the Orchestration"
" module."
msgstr "このロールは、Orchestration モジュールにより作成されたユーザーのデフォルトのロールとして使用されます。"
#: ./doc/install-guide/section_heat-install.xml148(para)
#: ./doc/install-guide/section_heat-install.xml154(para)
msgid ""
"Run the following command to create the <literal>heat_stack_user</literal> "
"role:"
msgstr "<literal>heat_stack_user</literal> ロールを作成するために、以下のコマンドを実行します。"
#: ./doc/install-guide/section_heat-install.xml153(para)
#: ./doc/install-guide/section_heat-install.xml159(para)
msgid "Configure the metadata and waitcondition servers' URLs."
msgstr "メタデータと待機条件のサーバーの URL を設定します。"
#: ./doc/install-guide/section_heat-install.xml154(para)
#: ./doc/install-guide/section_heat-install.xml160(para)
msgid ""
"Edit the <filename>/etc/heat/heat.conf</filename> file and modify the "
"following options in the <literal>[DEFAULT]</literal> section:"
msgstr "<filename>/etc/heat/heat.conf</filename> ファイルを編集し、<literal>[DEFAULT]</literal> セクションの以下のオプションを変更します。"
#: ./doc/install-guide/section_heat-install.xml160(replaceable)
#: ./doc/install-guide/section_heat-install.xml163(replaceable)
#: ./doc/install-guide/section_heat-install.xml168(replaceable)
#: ./doc/install-guide/section_heat-install.xml170(replaceable)
#: ./doc/install-guide/section_heat-install.xml166(replaceable)
#: ./doc/install-guide/section_heat-install.xml169(replaceable)
#: ./doc/install-guide/section_heat-install.xml174(replaceable)
#: ./doc/install-guide/section_heat-install.xml176(replaceable)
msgid "10.0.0.11"
msgstr "10.0.0.11"
#: ./doc/install-guide/section_heat-install.xml164(para)
#: ./doc/install-guide/section_heat-install.xml170(para)
msgid ""
"Run the following commands to modify the <literal>[DEFAULT]</literal> "
"section of the <filename>/etc/heat/heat.conf</filename> file:"
msgstr "<filename>/etc/heat/heat.conf</filename> ファイルの <literal>[DEFAULT]</literal> セクションを変更するために、以下のコマンドを実行します。"
#: ./doc/install-guide/section_heat-install.xml172(para)
#: ./doc/install-guide/section_heat-install.xml178(para)
msgid ""
"The example uses the IP address of the controller (10.0.0.11) instead of the"
" <literal>controller</literal> host name since our example architecture does"
@ -6550,7 +6559,7 @@ msgid ""
"controller host name if you choose to use it in the URLs."
msgstr "このアーキテクチャー例は DNS サーバーを持たないため、この例は <literal>controller</literal> というホスト名の代わりに IP アドレス (10.0.0.11) を使用します。URL にホスト名を使用する場合、インスタンスがコントローラーのホスト名を名前解決できることを確認してください。"
#: ./doc/install-guide/section_heat-install.xml186(para)
#: ./doc/install-guide/section_heat-install.xml192(para)
msgid ""
"Start the <systemitem class=\"service\">heat-api</systemitem>, <systemitem "
"class=\"service\">heat-api-cfn</systemitem> and <systemitem class=\"service"
@ -6898,23 +6907,27 @@ msgstr "2012"
msgid "2013"
msgstr "2013"
#: ./doc/install-guide/bk-openstack-install-guide.xml33(holder)
#: ./doc/install-guide/bk-openstack-install-guide.xml33(year)
msgid "2014"
msgstr "2014"
#: ./doc/install-guide/bk-openstack-install-guide.xml34(holder)
msgid "OpenStack Foundation"
msgstr "OpenStack Foundation"
#: ./doc/install-guide/bk-openstack-install-guide.xml35(releaseinfo)
msgid "icehouse"
msgstr "icehouse"
#: ./doc/install-guide/bk-openstack-install-guide.xml36(releaseinfo)
msgid "juno"
msgstr "juno"
#: ./doc/install-guide/bk-openstack-install-guide.xml36(productname)
#: ./doc/install-guide/bk-openstack-install-guide.xml37(productname)
msgid "OpenStack Installation Guide"
msgstr "OpenStack インストールガイド"
#: ./doc/install-guide/bk-openstack-install-guide.xml40(remark)
#: ./doc/install-guide/bk-openstack-install-guide.xml41(remark)
msgid "Copyright details are filled in by the template."
msgstr "Copyright details are filled in by the template."
#: ./doc/install-guide/bk-openstack-install-guide.xml45(para)
#: ./doc/install-guide/bk-openstack-install-guide.xml46(para)
msgid ""
"The OpenStack® system consists of several key projects that you install "
"separately but that work together depending on your cloud needs. These "
@ -6934,91 +6947,99 @@ msgid ""
" sample configuration files are included."
msgstr "OpenStack® システムはいくつかの主要なプロジェクトから構成されます。これらは別々にインストールできますが、クラウドの要件に応じて一緒に使用できます。Compute、Identity Service、Networking、Image Service、Block Storage、Object Storage、Telemetry、Orchestration、Database があります。これらのプロジェクトを別々にインストールできます。スタンドアローンまたは全体を接続するよう設定できます。<phrase os=\"debian\">このガイドは Debian 7.0 (コード名: Wheezy) で利用可能なパッケージを使用してインストールしていきます。</phrase><phrase os=\"ubuntu\">このガイドは Ubuntu 12.04 (LTS)、14.04 (LTS) で利用可能なパッケージを使用してインストールしていきます。</phrase><phrase os=\"rhel;centos;fedora\">このガイドは EPEL リポジトリから Fedora 20、Red Hat Enterprise Linux、その派生物で利用可能なパッケージを使用して OpenStack をインストールする方法を説明します。</phrase><phrase os=\"opensuse\">Open Build Service Cloud リポジトリから openSUSE で利用可能なパッケージを使用して OpenStack をインストールする方法を説明します。</phrase>設定オプションの説明とサンプル設定ファイルが含まれます。"
#: ./doc/install-guide/bk-openstack-install-guide.xml73(date)
#: ./doc/install-guide/bk-openstack-install-guide.xml74(date)
msgid "2014-06-03"
msgstr "2014-06-03"
#: ./doc/install-guide/bk-openstack-install-guide.xml78(para)
msgid "Start documentation for Juno."
msgstr "Juno 向けドキュメント化を開始しました。"
#: ./doc/install-guide/bk-openstack-install-guide.xml85(date)
msgid "2014-04-16"
msgstr "2014-04-16"
#: ./doc/install-guide/bk-openstack-install-guide.xml77(para)
#: ./doc/install-guide/bk-openstack-install-guide.xml89(para)
msgid ""
"Update for Icehouse, rework Networking setup to use ML2 as plugin, add new "
"chapter for Database Service setup, improved basic configuration."
msgstr "Icehouse 向け更新。Networking のセットアップを ML2 プラグインを使用するよう再構成。Database Service のセットアップに関する章の追加。基本的な設定の改善。"
#: ./doc/install-guide/bk-openstack-install-guide.xml86(date)
#: ./doc/install-guide/bk-openstack-install-guide.xml98(date)
msgid "2013-10-25"
msgstr "2013-10-25"
#: ./doc/install-guide/bk-openstack-install-guide.xml90(para)
#: ./doc/install-guide/bk-openstack-install-guide.xml102(para)
msgid "Added initial Debian support."
msgstr "Debian の初期サポートの追加。"
#: ./doc/install-guide/bk-openstack-install-guide.xml96(date)
#: ./doc/install-guide/bk-openstack-install-guide.xml108(date)
msgid "2013-10-17"
msgstr "2013-10-17"
#: ./doc/install-guide/bk-openstack-install-guide.xml100(para)
#: ./doc/install-guide/bk-openstack-install-guide.xml112(para)
msgid "Havana release."
msgstr "Havana リリース。"
#: ./doc/install-guide/bk-openstack-install-guide.xml106(date)
#: ./doc/install-guide/bk-openstack-install-guide.xml118(date)
msgid "2013-10-16"
msgstr "2013-10-16"
#: ./doc/install-guide/bk-openstack-install-guide.xml110(para)
#: ./doc/install-guide/bk-openstack-install-guide.xml122(para)
msgid "Add support for SUSE Linux Enterprise."
msgstr "SUSE Linux Enterprise のサポートの追加。"
#: ./doc/install-guide/bk-openstack-install-guide.xml117(date)
#: ./doc/install-guide/bk-openstack-install-guide.xml129(date)
msgid "2013-10-08"
msgstr "2013-10-08"
#: ./doc/install-guide/bk-openstack-install-guide.xml121(para)
#: ./doc/install-guide/bk-openstack-install-guide.xml133(para)
msgid "Complete reorganization for Havana."
msgstr "Havana 向け再構成の完了。"
#: ./doc/install-guide/bk-openstack-install-guide.xml128(date)
#: ./doc/install-guide/bk-openstack-install-guide.xml140(date)
msgid "2013-09-09"
msgstr "2013-09-09"
#: ./doc/install-guide/bk-openstack-install-guide.xml132(para)
#: ./doc/install-guide/bk-openstack-install-guide.xml144(para)
msgid "Build also for openSUSE."
msgstr "openSUSE 版の作成。"
#: ./doc/install-guide/bk-openstack-install-guide.xml138(date)
#: ./doc/install-guide/bk-openstack-install-guide.xml150(date)
msgid "2013-08-01"
msgstr "2013-08-01"
#: ./doc/install-guide/bk-openstack-install-guide.xml142(para)
#: ./doc/install-guide/bk-openstack-install-guide.xml154(para)
msgid ""
"Fixes to Object Storage verification steps. Fix bug <link "
"href=\"https://bugs.launchpad.net/openstack-"
"manuals/+bug/1207347\">1207347</link>."
msgstr "Object Storage 検証手順の修正。バグ <link href=\"https://bugs.launchpad.net/openstack-manuals/+bug/1207347\">1207347</link> の修正。"
#: ./doc/install-guide/bk-openstack-install-guide.xml151(date)
#: ./doc/install-guide/bk-openstack-install-guide.xml163(date)
msgid "2013-07-25"
msgstr "2013-07-25"
#: ./doc/install-guide/bk-openstack-install-guide.xml155(para)
#: ./doc/install-guide/bk-openstack-install-guide.xml167(para)
msgid ""
"Adds creation of cinder user and addition to the service tenant. Fix bug "
"<link href=\"https://bugs.launchpad.net/openstack-"
"manuals/+bug/1205057\">1205057</link>."
msgstr "cinder ユーザーの作成と service プロジェクトへの追加。バグ <link href=\"https://bugs.launchpad.net/openstack-manuals/+bug/1205057\">1205057</link> の修正。"
#: ./doc/install-guide/bk-openstack-install-guide.xml165(date)
#: ./doc/install-guide/bk-openstack-install-guide.xml177(date)
msgid "2013-05-08"
msgstr "2013-05-08"
#: ./doc/install-guide/bk-openstack-install-guide.xml169(para)
#: ./doc/install-guide/bk-openstack-install-guide.xml181(para)
msgid "Updated the book title for consistency."
msgstr "一貫性のために文書名の更新。"
#: ./doc/install-guide/bk-openstack-install-guide.xml176(date)
#: ./doc/install-guide/bk-openstack-install-guide.xml188(date)
msgid "2013-05-02"
msgstr "2013-05-02"
#: ./doc/install-guide/bk-openstack-install-guide.xml180(para)
#: ./doc/install-guide/bk-openstack-install-guide.xml192(para)
msgid "Updated cover and fixed small errors in appendix."
msgstr "表紙の更新と付録の小さなミスの修正。"

156
doc/user-guide/locale/ja.po

@ -6,8 +6,8 @@
msgid ""
msgstr ""
"Project-Id-Version: OpenStack Manuals\n"
"POT-Creation-Date: 2014-06-03 23:53+0000\n"
"PO-Revision-Date: 2014-06-04 05:40+0000\n"
"POT-Creation-Date: 2014-06-04 20:34+0000\n"
"PO-Revision-Date: 2014-06-05 04:41+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"
@ -37,7 +37,7 @@ msgid ""
"The templates enable creation of most OpenStack resource types, such as "
"instances, floating IP addresses, volumes, security groups, and users. The "
"resources, once created, are referred to as stacks."
msgstr ""
msgstr "これらの柔軟なテンプレート言語により、アプリケーション開発者は、インフラストラクチャ、サービス、アプリケーションの配備を記述し、自動化できます。テンプレートは、インスタンス、Floating IP アドレス、ボリューム、セキュリティグループ、ユーザーなどの、ほとんどの OpenStack リソースを作成できます。リソースが作成されると、スタックとして参照されます。"
#: ./doc/user-guide/section_cli_heat.xml19(para)
#: ./doc/user-guide/section_dashboard_stacks.xml23(para)
@ -47,7 +47,7 @@ msgid ""
" Template Guide</link> in the <link "
"href=\"http://docs.openstack.org/developer/heat/\">Heat developer "
"documentation</link>."
msgstr ""
msgstr "テンプレート言語は、<link href=\"http://docs.openstack.org/developer/heat/\">Heat developer documentation</link> の <link href=\"http://docs.openstack.org/developer/heat/template_guide/index.html\">the Template Guide</link> に記載されています。"
#: ./doc/user-guide/section_cli_heat.xml25(title)
msgid "Create a stack from an example template file"
@ -100,7 +100,7 @@ msgstr "テンプレートファイルからスタックを作成することな
msgid ""
"Previous versions of the heat client used <placeholder-1/> instead of "
"<placeholder-2/>, but it has been deprecated in favor of <placeholder-3/>."
msgstr ""
msgstr "前のバージョンの heat クライアントは、<placeholder-2/> の代わりに <placeholder-1/> を使用しましたが、 <placeholder-3/> のために非推奨になりました。"
#: ./doc/user-guide/section_cli_heat.xml58(para)
msgid "To do so, run the following command:"
@ -437,7 +437,7 @@ msgstr "コンピュート"
msgid ""
"To use the information in this section, you must be familiar with OpenStack "
"Compute."
msgstr ""
msgstr "このセクションにある情報を使用する場合、OpenStack Compute に慣れている必要があります。"
#: ./doc/user-guide/section_sdk_nova.xml10(title)
#: ./doc/user-guide/section_sdk_neutron.xml14(title)
@ -448,7 +448,7 @@ msgstr "環境変数の設定"
msgid ""
"To set up environmental variables and authenticate against Compute API "
"endpoints, see <xref linkend=\"sdk_auth\"/>."
msgstr ""
msgstr "環境変数をセットアップし、Compute API エンドポイントに対して認証するために、<xref linkend=\"sdk_auth\"/> を参照してください。"
#: ./doc/user-guide/section_sdk_nova.xml16(title)
msgid "Get OpenStack credentials (API v2)"
@ -555,7 +555,7 @@ msgid ""
"Get the flavor and image to use to create a server. This code uses the "
"<literal>cirros</literal> image, the <literal>m1.tiny</literal> flavor, and "
"the <literal>private</literal> network:"
msgstr ""
msgstr "サーバーを作成するために、使用するフレーバーとイメージを取得します。このコードは、<literal>cirros</literal> イメージ、<literal>m1.tiny</literal> フレーバー、<literal>private</literal> ネットワークを使用します。"
#: ./doc/user-guide/section_sdk_nova.xml112(para)
msgid "To create the server, use the network, image, and flavor:"
@ -565,7 +565,7 @@ msgstr "サーバーを作成し、ネットワーク、イメージ、フレー
msgid ""
"Sleep for five seconds and determine whether the server/vm was created by "
"calling <literal>nova_client.servers.list()</literal>:"
msgstr ""
msgstr "5 秒間スリープします。そして、 <literal>nova_client.servers.list()</literal> を呼び出すことにより、サーバー/仮想マシンが作成されたかどうかを確認します。"
#: ./doc/user-guide/section_sdk_nova.xml129(title)
msgid "Create server code listing"
@ -622,7 +622,7 @@ msgstr "サーバーの更新 (API v2)"
msgid ""
"The following program updates the name of a server (VM) by using the Compute"
" API v2."
msgstr ""
msgstr "以下のプログラムは、Compute API v2 を用いてサーバー (VM) の名前を更新します。"
#: ./doc/user-guide/section_sdk_nova.xml248(title)
msgid "To update a server"
@ -651,17 +651,17 @@ msgstr "<literal>server_id</literal> を使用してサーバーインスタン
msgid ""
"Call <code>server.update</code> on the server object with the new value for "
"<literal>name</literal> variable:"
msgstr ""
msgstr "<literal>name</literal> 変数の新しい値を用いて、server オブジェクトの <code>server.update</code> を呼び出します。"
#: ./doc/user-guide/section_sdk_nova.xml297(para)
msgid "Get the updated instance of the server:"
msgstr ""
msgstr "サーバーの更新されたインスタンスを取得します。"
#: ./doc/user-guide/section_sdk_nova.xml301(para)
msgid ""
"Call <literal>print_server</literal> again to check the update server "
"details:"
msgstr ""
msgstr "更新したサーバーの詳細を確認するために、再度 <literal>print_server</literal> を呼び出します。"
#: ./doc/user-guide/section_sdk_nova.xml308(title)
msgid "Update server code listing"
@ -703,7 +703,7 @@ msgstr "<literal>nova_client.flavors</literal> オブジェクトの <literal>l
msgid ""
"Print the flavor details, id and name by calling "
"<literal>print_flavors</literal>:"
msgstr ""
msgstr "<literal>print_flavors</literal> を呼び出し、フレーバーの詳細、ID、名前を表示します。"
#: ./doc/user-guide/section_sdk_nova.xml377(title)
msgid "List flavors code listing"
@ -717,7 +717,7 @@ msgstr "Floating IP の一覧表示 (API v2)"
msgid ""
"The following program lists the floating IPs and their details by using the "
"Compute API v2."
msgstr ""
msgstr "以下のプログラムは、Compute API v2 を用いて Floating IP アドレスとその詳細を一覧表示します。"
#: ./doc/user-guide/section_sdk_nova.xml396(title)
msgid "To list floating IPs"
@ -727,19 +727,19 @@ msgstr "Floating IP の一覧表示方法"
msgid ""
"The <literal>print_values_ip</literal> method is defined in "
"<filename>utils.py</filename> and prints the floating_ip object details:"
msgstr ""
msgstr "<literal>print_values_ip</literal> メソッドは、<filename>utils.py</filename> で定義され、floating_ip オブジェクトの詳細を表示します。"
#: ./doc/user-guide/section_sdk_nova.xml428(para)
msgid ""
"List floating IPs by calling <literal>list()</literal> on "
"<literal>nova_client.floating_ips</literal> object:"
msgstr ""
msgstr "<literal>nova_client.floating_ips</literal> オブジェクトの <literal>list()</literal> を呼び出すことにより、Floating IP を一覧表示します。"
#: ./doc/user-guide/section_sdk_nova.xml435(para)
msgid ""
"Print the floating IP object details by calling "
"<literal>print_values_ip</literal>:"
msgstr ""
msgstr "<literal>print_values_ip</literal> を呼び出すことにより、Floating IP オブジェクトの詳細を表示します。"
#: ./doc/user-guide/section_sdk_nova.xml441(title)
msgid "List floating IPs code listing"
@ -767,13 +767,13 @@ msgstr "<literal>print_hosts</literal> メソッドは、<filename>utils.py</fil
msgid ""
"List hosts by calling <literal>list()</literal> on "
"<literal>nova_client.hosts</literal> object:"
msgstr ""
msgstr "<literal>nova_client.hosts</literal> オブジェクトの <literal>list()</literal> を呼び出すことにより、ホストを一覧表示します。"
#: ./doc/user-guide/section_sdk_nova.xml495(para)
msgid ""
"Print the host object details by calling "
"<literal>print_hosts(host_list)</literal>:"
msgstr ""
msgstr "<literal>print_hosts(host_list)</literal> を呼び出すことにより、ホストオブジェクトの詳細を表示します。"
#: ./doc/user-guide/section_sdk_nova.xml501(title)
msgid "List hosts code listing"
@ -1112,7 +1112,7 @@ msgid ""
"within the cloud. For information about creating image files, see the <link "
"href=\"http://docs.openstack.org/image-guide/content/\"><citetitle>OpenStack"
" Virtual Machine Image Guide</citetitle></link>."
msgstr ""
msgstr "仮想マシンイメージは、このドキュメントでは単にイメージと言いますが、そこにインストールされたブート可能なオペレーティングシステムを持つ仮想ディスクを含む単一のファイルです。イメージは、クラウド内で仮想マシンインスタンスを作成するために使用されます。イメージファイルの作成に関する詳細は、<link href=\"http://docs.openstack.org/image-guide/content/\"><citetitle>OpenStack Virtual Machine Image Guide</citetitle></link> を参照してください。"
#: ./doc/user-guide/section_dashboard_manage_images.xml15(para)
msgid ""
@ -1121,7 +1121,7 @@ msgid ""
"images to cloud administrators or operators only. If you have the "
"appropriate privileges, you can use the dashboard to upload and manage "
"images in the <guilabel>admin</guilabel> project."
msgstr ""
msgstr "お使いのロールに応じて、仮想マシンイメージをアップロード、管理する権限があるかもしれません。運用者は、イメージのアップロードや管理をクラウド管理者や運用者のみに制限するかもしれません。適切な権限を持っていれば、ダッシュボードの <guilabel>admin</guilabel> プロジェクトで、イメージをアップロードおよび管理できます。"
#: ./doc/user-guide/section_dashboard_manage_images.xml22(para)
msgid ""
@ -1137,7 +1137,7 @@ msgstr "イメージのアップロード"
#: ./doc/user-guide/section_dashboard_manage_images.xml29(para)
msgid "Follow this procedure to upload an image to a project."
msgstr ""
msgstr "イメージをプロジェクトにアップロードするために、この手順に従います。"
#: ./doc/user-guide/section_dashboard_manage_images.xml33(para)
#: ./doc/user-guide/section_dashboard_manage_images.xml159(para)
@ -1217,7 +1217,7 @@ msgid ""
"enter the location URL of the image in the <guilabel>Image "
"Location</guilabel> field. or browse to the image file on your system and "
"add it."
msgstr ""
msgstr "<guilabel>イメージのソース/guilabel>の選択内容に応じて、<guilabel>イメージの場所</guilabel>の項目にイメージの URL を入力するか、お使いのシステムにあるイメージファイルを参照して追加します。"
#: ./doc/user-guide/section_dashboard_manage_images.xml97(guilabel)
msgid "Format"
@ -1960,7 +1960,7 @@ msgid ""
"store any type of file, including VM images, backups, archives, or media "
"files. In the OpenStack Dashboard, you can only manage containers and "
"objects."
msgstr ""
msgstr "OpenStack Object Storage は、API アクセス可能な、分散ストレージプラットフォームです。アプリケーションに直接統合できます。また、仮想マシンイメージ、バックアップ、アーカイブ、メディアファイルなど、あらゆる種類のファイルを保存するために使用されます。OpenStack Dashboard では、コンテナーとオブジェクトのみを管理できます。"
#: ./doc/user-guide/section_dashboard_manage_containers.xml13(para)
msgid ""
@ -1968,7 +1968,7 @@ msgid ""
"manner similar to a Windows folder or Linux file directory, though they "
"cannot be nested. An object in OpenStack consists of the file to be stored "
"in the container and any accompanying metadata."
msgstr ""
msgstr "OpenStack Object Storage では、コンテナーがオブジェクト用のストレージを提供します。Windows のフォルダーや Linux のディレクトリと同じ方法で提供されますが、入れ子構造にできません。OpenStack におけるオブジェクトは、コンテナーに保存するためのファイルと、付随するメタデータから構成されます。"
#: ./doc/user-guide/section_dashboard_manage_containers.xml22(para)
#: ./doc/user-guide/section_dashboard_manage_containers.xml44(para)
@ -1989,7 +1989,7 @@ msgstr "<guibutton>コンテナーの作成</guibutton>をクリックします
msgid ""
"In the Create Container dialog box, enter a name for the container, and then"
" click<guibutton>Create Container</guibutton>."
msgstr ""
msgstr "コンテナーの作成ダイアログで、コンテナーの名前を入力し、<guibutton>コンテナーの作成</guibutton>をクリックします。"
#: ./doc/user-guide/section_dashboard_manage_containers.xml34(para)
msgid "You have successfully created a container."
@ -2025,7 +2025,7 @@ msgid ""
"The Upload Object To Container: <replaceable>&lt;name&gt;</replaceable> "
"dialog box is displayed. <replaceable>&lt;name&gt;</replaceable> is the name"
" of the container to which you are uploading the object."
msgstr ""
msgstr "コンテナーへのオブジェクトのアップロード: <replaceable>&lt;name&gt;</replaceable> ダイアログボックスが表示されます。<replaceable>&lt;name&gt;</replaceable> は、オブジェクトをアップロードするコンテナーの名前です。"
#: ./doc/user-guide/section_dashboard_manage_containers.xml59(para)
#: ./doc/user-guide/section_dashboard_manage_containers.xml159(para)
@ -2083,25 +2083,25 @@ msgstr "<guibutton>▼</guibutton>をクリックし、ドロップダウンリ
#: ./doc/user-guide/section_dashboard_manage_containers.xml114(para)
msgid "In the Copy Object: launch dialog box, enter the following values:"
msgstr ""
msgstr "オブジェクトのコピー: ダイアログボックスを起動し、以下の値を入力します。"
#: ./doc/user-guide/section_dashboard_manage_containers.xml119(para)
msgid ""
"<guilabel>Destination Container</guilabel>: Choose the destination container"
" from the list."
msgstr ""
msgstr "<guilabel>宛先コンテナー</guilabel>: 一覧から宛先コンテナーを選択します。"
#: ./doc/user-guide/section_dashboard_manage_containers.xml123(para)
msgid ""
"<guilabel>Path</guilabel>: Specify a path in which the new copy should be "
"stored inside of the selected container."
msgstr ""
msgstr "<guilabel>パス</guilabel>: 選択したコンテナー内に保存する新規コピーのパスを指定します。"
#: ./doc/user-guide/section_dashboard_manage_containers.xml128(para)
msgid ""
"<guilabel>Destination object name</guilabel>: Enter a name for the object in"
" the new container."
msgstr ""
msgstr "<guilabel>宛先オブジェクト名</guilabel>: 新しいコンテナーにおけるオブジェクトの名前を入力します。"
#: ./doc/user-guide/section_dashboard_manage_containers.xml136(para)
msgid "Click <guibutton>Copy Object</guibutton>."
@ -2109,7 +2109,7 @@ msgstr "<guibutton>オブジェクトのコピー</guibutton>をクリックし
#: ./doc/user-guide/section_dashboard_manage_containers.xml140(title)
msgid "To create a metadata-only object without a file"
msgstr ""
msgstr "ファイルなしのメタデータ専用オブジェクトの作成方法"
#: ./doc/user-guide/section_dashboard_manage_containers.xml141(para)
msgid ""
@ -2117,17 +2117,17 @@ msgid ""
"upload the file later when it is ready. This temporary object acts a place-"
"holder for a new object, and enables the user to share object metadata and "
"URL info in advance."
msgstr ""
msgstr "利用可能なファイルを持たないコンテナーに新しいオブジェクトを作成できます。後から準備ができたときにファイルをアップロードできます。この一時的なオブジェクトは、新しいオブジェクトのプレースホルダーとして動作します。これにより、ユーザーがオブジェクトのメタデータを共有し、先に URL 情報を共有できるようになります。"
#: ./doc/user-guide/section_dashboard_manage_containers.xml166(title)
msgid "To create a pseudo-folder"
msgstr ""
msgstr "擬似フォルダーの作成方法"
#: ./doc/user-guide/section_dashboard_manage_containers.xml167(para)
msgid ""
"Pseudo-folders are similar to folders in your desktop operating system. They"
" are virtual collections defined by a common prefix on the object's name."
msgstr ""
msgstr "擬似フォルダーは、お使いのデスクトップオペレーティングシステムにおけるフォルダーと同じようなものです。オブジェクトの名前にある共通の接頭辞により定義される仮想的なコレクションです。"
#: ./doc/user-guide/section_dashboard_manage_containers.xml178(para)
msgid "Click <guibutton>Create Pseudo-folder</guibutton>."
@ -2139,7 +2139,7 @@ msgid ""
"</replaceable> dialog box is displayed. <replaceable>&lt;name&gt; "
"</replaceable> is the name of the container to which you are uploading the "
"object."
msgstr ""
msgstr "コンテナー <replaceable>&lt;name&gt; </replaceable> における擬似フォルダーの作成ダイアログボックスが表示されます。<replaceable>&lt;name&gt; </replaceable> は、オブジェクトをアップロードするコンテナーの名前です。"
#: ./doc/user-guide/section_dashboard_manage_containers.xml187(para)
msgid "Enter a name for the pseudo-folder."
@ -2237,14 +2237,14 @@ msgid ""
"role=\"italic\">key pair</emphasis>, which provides SSH access to your "
"instance. For this to work, the image must contain the <literal>cloud-"
"init</literal> package."
msgstr ""
msgstr "仮想マシンの起動時、インスタンスに SSH アクセスできるようにするための、<emphasis role=\"italic\">キーペア</emphasis>を注入できます。これを動作させるために、イメージに <literal>cloud-init</literal> パッケージをインストールしておく必要があります。"
#: ./doc/user-guide/section_cli_nova_configure_instances.xml16(para)
msgid ""
"You create at least one key pair for each project. You can use the key pair "
"for multiple instances that belong to that project. If you generate a key "
"pair with an external tool, you can import it into OpenStack."
msgstr ""
msgstr "各プロジェクトに少なくとも 1 つのキーペアを作成します。そのプロジェクトに属する複数のインスタンスに対してそのキーペアを使用できます。外部ツールを用いてキーペアを生成した場合、OpenStack にインポートできます。"
#: ./doc/user-guide/section_cli_nova_configure_instances.xml19(para)
msgid ""
@ -2260,7 +2260,7 @@ msgid ""
"more security groups to it. If you do not create security groups, new "
"instances are automatically assigned to the default security group, unless "
"you explicitly specify a different security group."
msgstr ""
msgstr "<emphasis role=\"italic\">セキュリティグループ</emphasis> は、インスタンスへアクセスが可能なトラフィックの種別を制限するために使用するネットワークのアクセスルールを名前を付けてまとめたものです。インスタンスを起動して、1 つまたは複数のセキュリティグループをインスタンスに割り当てることができます。セキュリティグループを作成しない場合、新しいインスタンスには明示的に別のセキュリティグループを指定しない限り、自動的に Default のセキュリティグループが割り当てられます。"
#: ./doc/user-guide/section_cli_nova_configure_instances.xml27(para)
msgid ""
@ -2269,7 +2269,7 @@ msgid ""
"that is not matched by a rule is denied access by default. You can add rules"
" to or remove rules from a security group, and you can modify rules for the "
"default and any other security group."
msgstr ""
msgstr "セキュリティグループごとに割り当てた <emphasis role=\"italic\">ルール</emphasis> は、グループ内のインスタンスへのトラフィックを制御します。デフォルトでは、ルールと合致しない受信トラフィックは、拒否されます。セキュリティグループへルールを追加することも、セキュリティグループからルールを削除することも可能です。デフォルトのルールやその他のセキュリティグループのルールを変更することができます。"
#: ./doc/user-guide/section_cli_nova_configure_instances.xml33(para)
msgid ""
@ -2278,7 +2278,7 @@ msgid ""
"allow access to instances through SSH, to ping instances, or to allow UDP "
"traffic; for example, for a DNS server running on an instance. You specify "
"the following parameters for rules:"
msgstr ""
msgstr "セキュリティグループのルールを変更して、別のポートやプロトコルからインスタンスにアクセスすることができます。例えば、SSH 経由でのインスタンスへのアクセス、ping、UDP トラフィックの許可 (例: インスタンス上で実行中の DNS) などができるようにルールを変更することができます。ルールについては以下のパラメーターを指定します。"
#: ./doc/user-guide/section_cli_nova_configure_instances.xml41(para)
msgid ""
@ -2299,7 +2299,7 @@ msgid ""
"Define a port range. To open a single port only, enter the same value twice."
" ICMP does not support ports; instead, you enter values to define the codes "
"and types of ICMP traffic to be allowed."
msgstr ""
msgstr "<emphasis role=\"bold\">仮想マシンでの宛て先ポート番号</emphasis>。ポートの範囲を定義します。ポート 1 つのみを開くには、同じ値を 2 回入力します。ICMP はポートに対応していないため、許可する ICMP トラフィックのコードおよび種別を定義する値を代わりに入力します。"
#: ./doc/user-guide/section_cli_nova_configure_instances.xml58(para)
msgid "Rules are automatically enforced as soon as you create or modify them."
@ -2311,14 +2311,14 @@ msgid ""
"accessed from any IP address outside of the cloud. If you want those IP "
"addresses to access the instances, you must modify the rules for the default"
" security group."
msgstr ""
msgstr "デフォルトのセキュリティグループを使用するインスタンスは、デフォルトでクラウド外の IP アドレスからアクセスできません。これらの IP アドレスがインスタンスにアクセスしたければ、デフォルトのセキュリティグループのルールを編集する必要があります。"
#: ./doc/user-guide/section_cli_nova_configure_instances.xml65(para)
msgid ""
"You can also assign a floating IP address to a running instance to make it "
"accessible from outside the cloud. See <xref "
"linkend=\"manage_ip_addresses\"/>."
msgstr ""
msgstr "また、実行中のインスタンスに Flating IP アドレスを割り当て、クラウド外からアクセスできるようにすることも可能です。<xref linkend=\"manage_ip_addresses\"/>を参照してください。"
#: ./doc/user-guide/section_cli_nova_configure_instances.xml70(title)
#: ./doc/user-guide/section_dashboard_access_and_security.xml136(title)
@ -2349,13 +2349,13 @@ msgid ""
"<replaceable>KEY_NAME</replaceable>, writes the private key to the "
"<filename>.pem</filename> file that you specify, and registers the public "
"key at the Nova database."
msgstr ""
msgstr "このコマンドは、指定した <replaceable>KEY_NAME</replaceable> という名前のキーペアを生成し、秘密鍵を <filename>.pem</filename> ファイルに書き込み、公開鍵を Nova データベースに登録します。"
#: ./doc/user-guide/section_cli_nova_configure_instances.xml84(para)
msgid ""
"To set the permissions of the <filename>.pem</filename> file so that only "
"you can read and write to it, run the following command:"
msgstr ""
msgstr "あなただけが読み書きできるよう、<filename>.pem</filename> ファイルのパーミッションを設定するために、以下のコマンドを実行します。"
#: ./doc/user-guide/section_cli_nova_configure_instances.xml92(title)
#: ./doc/user-guide/section_dashboard_access_and_security.xml166(title)
@ -2367,20 +2367,20 @@ msgid ""
"If you have already generated a key pair and the public key is located at "
"<filename>~/.ssh/id_rsa.pub</filename>, run the following command to upload "
"the public key:"
msgstr ""
msgstr "すでにキーペアを生成し、公開鍵が <filename>~/.ssh/id_rsa.pub</filename> にある場合、以下のコマンドでこの公開鍵をアップロードします。"
#: ./doc/user-guide/section_cli_nova_configure_instances.xml99(para)
msgid ""
"The command registers the public key at the Nova database and names the key "
"pair the name that you specify for "
"<literal><replaceable>KEY_NAME</replaceable></literal>."
msgstr ""
msgstr "このコマンドは、Nova データベースに公開鍵を登録して、キーペアの名前を指定した <literal><replaceable>KEY_NAME</replaceable></literal> にします。"
#: ./doc/user-guide/section_cli_nova_configure_instances.xml104(para)
msgid ""
"To ensure that the key pair has been successfully imported, list key pairs "
"as follows:"
msgstr ""
msgstr "キーペアが正常にインポートされたことを確認するために、以下のとおりキーペアを一覧表示します。"
#: ./doc/user-guide/section_cli_nova_configure_instances.xml111(title)
#: ./doc/user-guide/section_sdk_configure_instances.xml72(title)
@ -2391,7 +2391,7 @@ msgstr "セキュリティグループの作成と管理"
msgid ""
"To list the security groups for the current project, including descriptions,"
" enter the following command:"
msgstr ""
msgstr "現在のプロジェクトのセキュリティグループと説明を一覧表示するために、以下のコマンドを入力します。"
#: ./doc/user-guide/section_cli_nova_configure_instances.xml119(para)
msgid ""
@ -2435,7 +2435,7 @@ msgid ""
"Modify security group rules with the <placeholder-1/> commands. Before you "
"begin, source the OpenStack RC file. For details, see <xref "
"linkend=\"cli_openrc\"/>."
msgstr ""
msgstr "<placeholder-1/> コマンドを用いてセキュリティグループのルールを編集します。開始する前に、OpenStack RC ファイルを読み込みます。詳細は <xref linkend=\"cli_openrc\"/> を参照してください。"
#: ./doc/user-guide/section_cli_nova_configure_instances.xml145(para)
msgid "To list the rules for a security group, run the following command:"
@ -2456,7 +2456,7 @@ msgstr "CIDR 表記で IP サブネット <filename>0.0.0.0/0</filename> とし
msgid ""
"Allow access only from IP addresses from other security groups (source "
"groups) to access the specified port:"
msgstr ""
msgstr "他のセキュリティグループからの IP アドレス (ソースグループ) のみが指定したポートにアクセスできるようにします。"
#: ./doc/user-guide/section_cli_nova_configure_instances.xml164(replaceable)
#: ./doc/user-guide/section_cli_nova_configure_instances.xml184(replaceable)
@ -2554,13 +2554,13 @@ msgstr ""
#: ./doc/user-guide/section_cli_nova_floating_ips.xml26(para)
msgid "Disassociate a floating IP address from an instance in the project."
msgstr ""
msgstr "プロジェクトのインスタンスから Floating IP アドレスの割り当てを解除します。"
#: ./doc/user-guide/section_cli_nova_floating_ips.xml29(para)
msgid ""
"Delete a floating IP from the project; deleting a floating IP automatically "
"deletes that IP's associations."
msgstr ""
msgstr "プロジェクトから Floating IP アドレスを削除します。Floating IP アドレスの削除により、その IP の割り当てが自動的に解除されます。"
#: ./doc/user-guide/section_cli_nova_floating_ips.xml34(para)
msgid "Use the <placeholder-1/> commands to manage floating IP addresses."
@ -2572,19 +2572,19 @@ msgstr "Floating IP アドレスの情報の表示"
#: ./doc/user-guide/section_cli_nova_floating_ips.xml40(para)
msgid "To list all pools that provide floating IP addresses, run:"
msgstr ""
msgstr "Floating IP アドレスを提供するプールをすべて表示するために、以下を実行します。"
#: ./doc/user-guide/section_cli_nova_floating_ips.xml48(para)
msgid ""
"If this list is empty, the cloud administrator must configure a pool of "
"floating IP addresses."
msgstr ""
msgstr "これが空白の場合、クラウド管理者は Floating IP アドレスのプールを設定する必要があります。"
#: ./doc/user-guide/section_cli_nova_floating_ips.xml51(para)
msgid ""
"To list all floating IP addresses that are allocated to the current project,"
" run:"
msgstr ""
msgstr "現在のプロジェクトに確保されている、すべての Floating IP アドレスを一覧表示するために、以下を実行します。"
#: ./doc/user-guide/section_cli_nova_floating_ips.xml59(para)
msgid ""
@ -2592,15 +2592,15 @@ msgid ""
"command outputs the floating IP address, the ID for the instance to which "
"the floating IP address is assigned, the associated fixed IP address, and "
"the pool from which the floating IP address was allocated."
msgstr ""
msgstr "現在のプロジェクトに確保されている各 Floating IP アドレスに対して、このコマンドは、Floating IP アドレス、Floating IP アドレスが割り当てられたインスタンスの ID、関連付けられた固定 IP アドレス、Floating IP アドレスが確保されたプールを出力します。"
#: ./doc/user-guide/section_cli_nova_floating_ips.xml67(title)
msgid "Associate floating IP addresses"
msgstr ""
msgstr "Floating IP アドレスの割り当て"
#: ./doc/user-guide/section_cli_nova_floating_ips.xml68(para)
msgid "You can assign a floating IP address to a project and to an instance."
msgstr ""
msgstr "Floating IP アドレスをプロジェクトやインスタンスに割り当てられます。"
#: ./doc/user-guide/section_cli_nova_floating_ips.xml71(para)
msgid ""
@ -2615,7 +2615,7 @@ msgid ""
"If more than one IP address pool is available, you can specify the pool from"
" which to allocate the IP address, using the pool's name. For example, to "
"allocate a floating IP address from the <literal>test</literal> pool, run:"
msgstr ""
msgstr "IP アドレスのプールが 1 つ以上利用可能な場合、どちらのプールから IP アドレスを確保するのかを、プールの名前を使用して指定します。例えば、Floating IP アドレスを <literal>test</literal> プールから確保するために、以下を実行します。"
#: ./doc/user-guide/section_cli_nova_floating_ips.xml88(para)
msgid ""
@ -2625,7 +2625,7 @@ msgstr ""
#: ./doc/user-guide/section_cli_nova_floating_ips.xml99(para)
msgid "Associate an IP address with an instance in the project, as follows:"
msgstr ""
msgstr "以下のように、IP アドレスをプロジェクトのインスタンスに割り当てます。"
#: ./doc/user-guide/section_cli_nova_floating_ips.xml100(replaceable)
#: ./doc/user-guide/section_cli_nova_floating_ips.xml118(replaceable)
@ -2646,20 +2646,20 @@ msgstr "例えば"
#: ./doc/user-guide/section_cli_nova_floating_ips.xml105(para)
msgid "Notice that the instance is now associated with two IP addresses:"
msgstr ""
msgstr "これで 2 つの IP アドレスがインスタンスに関連付けられていることに気が付くでしょう。"
#: ./doc/user-guide/section_cli_nova_floating_ips.xml113(para)
msgid ""
"After you associate the IP address and configure security group rules for "
"the instance, the instance is publicly available at the floating IP address."
msgstr ""
msgstr "インスタンスに IP アドレスを割り当てて、セキュリティグループルールを設定してから、インスタンスを Floating IP アドレスで公開します。"
#: ./doc/user-guide/section_cli_nova_floating_ips.xml115(para)
msgid ""
"If an instance is connected to multiple networks, you can associate a "
"floating IP address with a specific fixed IP address using the optional "
"<parameter>--fixed-address</parameter> parameter:"
msgstr ""
msgstr "インスタンスが複数のネットワークに接続されている場合、オプションの <parameter>--fixed-address</parameter> パラメーターを使用して、指定した固定 IP アドレスに Floating IP アドレスを関連付けられます。"
#: ./doc/user-guide/section_cli_nova_floating_ips.xml118(replaceable)
msgid "FIXED_IP_ADDRESS"
@ -2675,14 +2675,14 @@ msgstr "以下のように、Floating IP アドレスをインスタンスから
#: ./doc/user-guide/section_cli_nova_floating_ips.xml131(para)
msgid "Release the floating IP address from the current project, as follows:"
msgstr ""
msgstr "以下のとおり、現在のプロジェクトから Floating IP アドレスを解放します。"
#: ./doc/user-guide/section_cli_nova_floating_ips.xml133(para)
msgid ""
"The IP address is returned to the pool of IP addresses that is available for"
" all projects. If the IP address is still associated with a running "
"instance, it is automatically disassociated from that instance."
msgstr ""
msgstr "IP アドレスは、すべてのプロジェクトで利用できるように IP アドレスのプールに戻されます。IP アドレスが実行中のインスタンスにまだ割り当てられていると、そのインスタンスから自動的に割り当て解除されます。"
#: ./doc/user-guide/section_cli_nova_manage_instances.xml6(title)
msgid "Manage instances and hosts"
@ -2857,7 +2857,7 @@ msgstr ""
msgid ""
"Use the <placeholder-1/> command to confirm that the instance shows a "
"<literal>SHUTOFF</literal> status."
msgstr ""
msgstr "インスタンスが<literal>停止</literal>状態になっていることを確認するために、<placeholder-1/> コマンドを使用します。"
#: ./doc/user-guide/section_cli_nova_migrate_instances.xml59(para)
msgid ""
@ -2957,7 +2957,7 @@ msgstr "要件とガイドライン"
msgid ""
"To use the configuration drive, you must follow the following requirements "
"for the compute host and image."
msgstr ""
msgstr "コンフィグドライブを使用するために、コンピュートホストとイメージに関する以下の要件を満たす必要があります。"
#: ./doc/user-guide/section_cli_nova_config-drive.xml31(title)
msgid "Compute host requirements"
@ -3083,7 +3083,7 @@ msgid ""
"label/<replaceable>configurationDriveVolumeLabel</replaceable></filename> "
"device. In the following example, the configuration drive has the "
"<filename>config-2</filename> volume label."
msgstr ""
msgstr "お使いのゲストオペレーティングシステムが、ラベルによるディスクアクセスをサポートしている場合、コンフィグドライブを <filename>/dev/disk/by-label/<replaceable>configurationDriveVolumeLabel</replaceable></filename> デバイスとしてマウントできます。以下の例は、コンフィグドライブが <filename>config-2</filename> ボリュームラベルを持ちます。"
#: ./doc/user-guide/section_cli_nova_config-drive.xml142(para)
msgid ""
@ -3674,7 +3674,7 @@ msgid ""
"Query API that is compatible with CloudFormation and the native OpenStack "
"<glossterm>Heat Orchestration Template (HOT)</glossterm> format through a "
"REST API."
msgstr ""
msgstr "OpenStack Orchestration は、複数から構成されたクラウドアプリケーションを統合するために使用できるサービスです。このサービスは、CloudFormation 互換の Query API 経由の Amazon Web Services (AWS) CloudFormation テンプレート形式、REST API 経由のネイティブ OpenStack <glossterm>Heat Orchestration Template (HOT)</glossterm> 形式の使用をサポートします。"
#: ./doc/user-guide/section_dashboard_stacks.xml30(title)
msgid "Launch a stack"
@ -3772,7 +3772,7 @@ msgstr "失敗時のロールバック"
msgid ""
"Select this check box if you want if you want the service to roll back "
"changes if the stack fails to launch."
msgstr ""
msgstr "スタックの起動に失敗した場合に、サービスの変更をロールバックしたければ、このチェックボックスを選択します。"
#: ./doc/user-guide/section_dashboard_stacks.xml101(guilabel)
msgid "Password for user \"demo\""
@ -4071,7 +4071,7 @@ msgid ""
"address can also be attached to an instance. Unlike fixed IP addresses, "
"floating IP addresses are able to have their associations modified at any "
"time, regardless of the state of the instances involved."
msgstr ""
msgstr "インスタンスを OpenStack に作成したとき、インスタンスに割り当てられるネットワーク上の固定 IP アドレスが自動的に割り当てられます。この IP アドレスは、インスタンスが終了するまで、インスタンスに割り当てられたままです。しかしながら、固定 IP アドレスに加えて、Floating IP アドレスもインスタンスに割り当てられます。固定 IP アドレスと異なり、Floating IP アドレスは、インスタンスの状態に関わらず、いつでも関連付けを変更できます。"
#: ./doc/user-guide/section_dashboard_access_and_security.xml35(title)
msgid "Add a rule to the default security group"
@ -4234,7 +4234,7 @@ msgid ""
"<filename>*.ppk</filename>. For more information see the <link "
"href=\"http://winscp.net/eng/docs/ui_puttygen\">WinSCP web page for "
"PuTTYgen</link>."
msgstr ""
msgstr "Windows コンピューターからダッシュボードを使用している場合、<filename>*.pem</filename> ファイルを読み込むために PuTTYgen を使用し、<filename>*.ppk</filename> に変換して保存します。詳細は <link href=\"http://winscp.net/eng/docs/ui_puttygen\">WinSCP web page for PuTTYgen</link> を参照してください。"
#: ./doc/user-guide/section_dashboard_access_and_security.xml209(para)
msgid "To make the key pair known to SSH, run the <placeholder-1/> command."
@ -4598,7 +4598,7 @@ msgid ""
" this value is set to the availability zone given by the cloud provider (for"
" example, <literal>us-west</literal> or <literal>apac-south</literal>). For "
"some cases, it could be <literal>nova</literal>."
msgstr ""
msgstr "<guilabel>アベイラビリティゾーン</guilabel>を一覧から選択します。この値はデフォルトで、クラウドプロバイダーにより指定されたアベイラビリティゾーンに設定されます (例えば、<literal>us-west</literal>、<literal>apac-south</literal>)。<literal>nova</literal> となっている場合もあります。"
#: ./doc/user-guide/section_dashboard_manage_volumes.xml107(guilabel)
msgid "Volume"
@ -4614,7 +4614,7 @@ msgstr "このオプションを選択する場合、<guilabel>ソースとし
msgid ""
"Options to use a snapshot or a volume as the source for a volume are "
"displayed only if there are existing snapshots or volumes."
msgstr ""
msgstr "ソースとしてスナップショットの利用、ソースとしてボリュームの利用のオプションは、既存のスナップショットやボリュームが存在する場合のみ表示されます。"
#: ./doc/user-guide/section_dashboard_manage_volumes.xml127(para)
msgid ""
@ -4641,7 +4641,7 @@ msgstr "インスタンスに追加するボリュームを選択し、<guibutto
msgid ""
"In the <guilabel>Manage Volume Attachments</guilabel> dialog box, select an "
"instance."
msgstr ""
msgstr "<guilabel>ボリュームの接続の管理</guilabel>ダイアログボックスで、インスタンスを選択します。"
#: ./doc/user-guide/section_dashboard_manage_volumes.xml148(para)
msgid ""