openstack/openstack-manuals
Code Issues Proposed changes

Imported Translations from Transifex

Browse Source 
Change-Id: I8694f063e3dce09781d01dc193d9155a45197da6
This commit is contained in:
OpenStack Proposal Bot 2014-08-15 06:10:10 +00:00
parent d8c951c6f1
commit 57fd5becf4
23 changed files with 18678 additions and 14414 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

418
doc/admin-guide-cloud/locale/admin-guide-cloud.pot
View File

@ -1,7 +1,7 @@
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"POT-Creation-Date: 2014-08-05 06:09+0000\n"
"POT-Creation-Date: 2014-08-15 06:09+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"
@ -151,7 +151,7 @@ msgid "Note that these logging methods may safely be called anywhere you have a
msgstr ""
#: ./doc/admin-guide-cloud/section_object-storage-monitoring.xml:287(para)
msgid "The development team of StatsD wanted to use the <link href=\"https://github.com/sivy/py-statsd\">pystatsd</link> client library (not to be confused with a <link href=\"https://github.com/sivy/py-statsd\">similar-looking project</link> also hosted on GitHub), but the released version on PyPi was missing two desired features the latest version in GitHub had: the ability to configure a metrics prefix in the client object and a convenience method for sending timing data between “now” and a “start” timestamp you already have. So they just implemented a simple StatsD client library from scratch with the same interface. This has the nice fringe benefit of not introducing another external library dependency into Object Storage."
msgid "The development team of StatsD wanted to use the <link href=\"https://github.com/sivy/py-statsd\">pystatsd</link> client library (not to be confused with a <link href=\"https://github.com/sivy/py-statsd\">similar-looking project</link> also hosted on GitHub), but the released version on PyPI was missing two desired features the latest version in GitHub had: the ability to configure a metrics prefix in the client object and a convenience method for sending timing data between “now” and a “start” timestamp you already have. So they just implemented a simple StatsD client library from scratch with the same interface. This has the nice fringe benefit of not introducing another external library dependency into Object Storage."
msgstr ""
#: ./doc/admin-guide-cloud/section_object-storage-admin.xml:7(title)
@ -430,219 +430,219 @@ msgstr ""
msgid "Identity concepts"
msgstr ""
#: ./doc/admin-guide-cloud/ch_identity_mgmt.xml:32(title)
#: ./doc/admin-guide-cloud/ch_identity_mgmt.xml:33(title)
msgid "User CRUD"
msgstr ""
#: ./doc/admin-guide-cloud/ch_identity_mgmt.xml:33(para)
#: ./doc/admin-guide-cloud/ch_identity_mgmt.xml:34(para)
msgid "Identity provides a user CRUD filter that can be added to the public_api pipeline. This user CRUD filter enables users to use a HTTP PATCH to change their own password. To enable this extension you should define a <literal>user_crud_extension</literal> filter, insert it after the <literal>*_body</literal> middleware and before the <literal>public_service</literal> application in the public_api WSGI pipeline in <filename>keystone.conf</filename>. For example:"
msgstr ""
#: ./doc/admin-guide-cloud/ch_identity_mgmt.xml:47(para)
#: ./doc/admin-guide-cloud/ch_identity_mgmt.xml:48(para)
msgid "Each user can then change their own password with a HTTP PATCH:"
msgstr ""
#: ./doc/admin-guide-cloud/ch_identity_mgmt.xml:48(replaceable)
#: ./doc/admin-guide-cloud/ch_identity_mgmt.xml:49(replaceable)
msgid "USERID"
msgstr ""
#: ./doc/admin-guide-cloud/ch_identity_mgmt.xml:49(replaceable)
#: ./doc/admin-guide-cloud/ch_identity_mgmt.xml:50(replaceable)
msgid "AUTHTOKENID"
msgstr ""
#: ./doc/admin-guide-cloud/ch_identity_mgmt.xml:50(para)
msgid "In addition to changing their password, all current tokens for the user are deleted (if the back end is KVS or sql)."
#: ./doc/admin-guide-cloud/ch_identity_mgmt.xml:51(para)
msgid "In addition to changing their password, all current tokens for the user are deleted (if the back end is KVS or SQL)."
msgstr ""
#: ./doc/admin-guide-cloud/ch_identity_mgmt.xml:52(para)
#: ./doc/admin-guide-cloud/ch_identity_mgmt.xml:53(para)
msgid "Only use a KVS back end for tokens when testing."
msgstr ""
#: ./doc/admin-guide-cloud/ch_identity_mgmt.xml:55(title)
#: ./doc/admin-guide-cloud/ch_identity_mgmt.xml:56(title)
msgid "Logging"
msgstr ""
#: ./doc/admin-guide-cloud/ch_identity_mgmt.xml:56(para)
#: ./doc/admin-guide-cloud/ch_identity_mgmt.xml:57(para)
msgid "You configure logging externally to the rest of Identity. The file specifying the logging configuration is in the <literal>[DEFAULT]</literal> section of the <filename>keystone.conf</filename> file under <literal>log_config</literal>. To route logging through syslog, set <literal>use_syslog=true</literal> option in the <literal>[DEFAULT]</literal> section."
msgstr ""
#: ./doc/admin-guide-cloud/ch_identity_mgmt.xml:62(para)
#: ./doc/admin-guide-cloud/ch_identity_mgmt.xml:63(para)
msgid "A sample logging file is available with the project in the <filename>etc/logging.conf.sample</filename> directory. Like other OpenStack projects, Identity uses the Python logging module, which includes extensive configuration options that let you define the output levels and formats."
msgstr ""
#: ./doc/admin-guide-cloud/ch_identity_mgmt.xml:67(para)
#: ./doc/admin-guide-cloud/ch_identity_mgmt.xml:68(para)
msgid "Review the <filename>etc/keystone.conf</filename> sample configuration files that are distributed with the Identity Service. For example, each server application has its own configuration file."
msgstr ""
#: ./doc/admin-guide-cloud/ch_identity_mgmt.xml:71(para)
#: ./doc/admin-guide-cloud/ch_identity_mgmt.xml:72(para)
msgid "For services that have separate paste-deploy <filename>.ini</filename> files, you can configure <literal>auth_token</literal> middleware in the <literal>[keystone_authtoken]</literal> section in the main configuration file, such as <filename>nova.conf</filename>. For example in Compute, you can remove the middleware parameters from <filename>api-paste.ini</filename>, as follows:"
msgstr ""
#: ./doc/admin-guide-cloud/ch_identity_mgmt.xml:81(para)
#: ./doc/admin-guide-cloud/ch_identity_mgmt.xml:82(para)
msgid "Set these values in the <filename>nova.conf</filename> file:"
msgstr ""
#: ./doc/admin-guide-cloud/ch_identity_mgmt.xml:96(para)
#: ./doc/admin-guide-cloud/ch_identity_mgmt.xml:97(para)
msgid "Middleware parameters in paste config take priority. You must remove them to use values in the <literal>[keystone_authtoken]</literal> section."
msgstr ""
#: ./doc/admin-guide-cloud/ch_identity_mgmt.xml:102(title)
#: ./doc/admin-guide-cloud/ch_identity_mgmt.xml:103(title)
msgid "Monitoring"
msgstr ""
#: ./doc/admin-guide-cloud/ch_identity_mgmt.xml:103(para)
#: ./doc/admin-guide-cloud/ch_identity_mgmt.xml:104(para)
msgid "Identity provides some basic request and response monitoring statistics out of the box."
msgstr ""
#: ./doc/admin-guide-cloud/ch_identity_mgmt.xml:105(para)
#: ./doc/admin-guide-cloud/ch_identity_mgmt.xml:106(para)
msgid "Enable data collection by defining a <literal>stats_monitoring</literal> filter and including it at the beginning of any desired WSGI pipelines:"
msgstr ""
#: ./doc/admin-guide-cloud/ch_identity_mgmt.xml:113(para)
#: ./doc/admin-guide-cloud/ch_identity_mgmt.xml:114(para)
msgid "Enable the reporting of collected data by defining a <literal>stats_reporting</literal> filter and including it near the end of your <literal>admin_api</literal> WSGI pipeline (After <literal>*_body</literal> middleware and before <literal>*_extension</literal> filters is recommended):"
msgstr ""
#: ./doc/admin-guide-cloud/ch_identity_mgmt.xml:123(para)
#: ./doc/admin-guide-cloud/ch_identity_mgmt.xml:124(para)
msgid "Query the admin API for statistics using:"
msgstr ""
#: ./doc/admin-guide-cloud/ch_identity_mgmt.xml:125(para)
#: ./doc/admin-guide-cloud/ch_identity_mgmt.xml:126(para)
msgid "Reset collected data using:"
msgstr ""
#: ./doc/admin-guide-cloud/ch_identity_mgmt.xml:130(title)
#: ./doc/admin-guide-cloud/ch_identity_mgmt.xml:131(title)
msgid "Start the Identity services"
msgstr ""
#: ./doc/admin-guide-cloud/ch_identity_mgmt.xml:131(para)
#: ./doc/admin-guide-cloud/ch_identity_mgmt.xml:132(para)
msgid "To start the services for Identity, run the following command:"
msgstr ""
#: ./doc/admin-guide-cloud/ch_identity_mgmt.xml:134(para)
#: ./doc/admin-guide-cloud/ch_identity_mgmt.xml:135(para)
msgid "This command starts two wsgi.Server instances configured by the <filename>keystone.conf</filename> file as described previously. One of these wsgi servers is <literal>admin</literal> (the administration API) and the other is <literal>main</literal> (the primary/public API interface). Both run in a single process."
msgstr ""
#: ./doc/admin-guide-cloud/ch_identity_mgmt.xml:142(title)
#: ./doc/admin-guide-cloud/ch_identity_mgmt.xml:143(title)
msgid "Example usage"
msgstr ""
#: ./doc/admin-guide-cloud/ch_identity_mgmt.xml:143(para)
#: ./doc/admin-guide-cloud/ch_identity_mgmt.xml:144(para)
msgid "The <literal>keystone</literal> client is set up to expect commands in the general form of <literal>keystone</literal><literal>command</literal><literal>argument</literal>, followed by flag-like keyword arguments to provide additional (often optional) information. For example, the command <literal>user-list</literal> and <literal>tenant-create</literal> can be invoked as follows:"
msgstr ""
#: ./doc/admin-guide-cloud/ch_identity_mgmt.xml:173(title)
#: ./doc/admin-guide-cloud/ch_identity_mgmt.xml:174(title)
msgid "Authentication middleware with user name and password"
msgstr ""
#: ./doc/admin-guide-cloud/ch_identity_mgmt.xml:175(para)
#: ./doc/admin-guide-cloud/ch_identity_mgmt.xml:176(para)
msgid "You can also configure Identity authentication middleware using the <option>admin_user</option> and <option>admin_password</option> options. When using the <option>admin_user</option> and <option>admin_password</option> options the <option>admin_token</option> parameter is optional. If <option>admin_token</option> is specified, it is used only if the specified token is still valid."
msgstr ""
#: ./doc/admin-guide-cloud/ch_identity_mgmt.xml:183(para)
#: ./doc/admin-guide-cloud/ch_identity_mgmt.xml:184(para)
msgid "For services that have a separate paste-deploy .ini file, you can configure the authentication middleware in the <literal>[keystone_authtoken]</literal> section of the main configuration file, such as <filename>nova.conf</filename>. In Compute, for example, you can remove the middleware parameters from <filename>api-paste.ini</filename>, as follows:"
msgstr ""
#: ./doc/admin-guide-cloud/ch_identity_mgmt.xml:192(para)
#: ./doc/admin-guide-cloud/ch_identity_mgmt.xml:193(para)
msgid "And set the following values in <filename>nova.conf</filename> as follows:"
msgstr ""
#: ./doc/admin-guide-cloud/ch_identity_mgmt.xml:207(para)
#: ./doc/admin-guide-cloud/ch_identity_mgmt.xml:208(para)
msgid "The middleware parameters in the paste config take priority. You must remove them to use the values in the [keystone_authtoken] section."
msgstr ""
#: ./doc/admin-guide-cloud/ch_identity_mgmt.xml:211(para)
#: ./doc/admin-guide-cloud/ch_identity_mgmt.xml:212(para)
msgid "This sample paste config filter makes use of the <option>admin_user</option> and <option>admin_password</option> options:"
msgstr ""
#: ./doc/admin-guide-cloud/ch_identity_mgmt.xml:224(para)
#: ./doc/admin-guide-cloud/ch_identity_mgmt.xml:225(para)
msgid "Using this option requires an admin tenant/role relationship. The admin user is granted access to the admin role on the admin tenant."
msgstr ""
#: ./doc/admin-guide-cloud/ch_identity_mgmt.xml:230(title)
#: ./doc/admin-guide-cloud/ch_identity_mgmt.xml:231(title)
msgid "Identity API protection with role-based access control (RBAC)"
msgstr ""
#: ./doc/admin-guide-cloud/ch_identity_mgmt.xml:232(para)
#: ./doc/admin-guide-cloud/ch_identity_mgmt.xml:233(para)
msgid "Like most OpenStack projects, Identity supports the protection of its APIs by defining policy rules based on an RBAC approach. Identity stores a reference to a policy JSON file in the main Identity configuration file, <filename>keystone.conf</filename>. Typically this file is named <filename>policy.json</filename>, and it contains the rules for which roles have access to certain actions in defined services."
msgstr ""
#: ./doc/admin-guide-cloud/ch_identity_mgmt.xml:238(para)
#: ./doc/admin-guide-cloud/ch_identity_mgmt.xml:239(para)
msgid "Each Identity API v3 call has a line in the policy file that dictates which level of governance of access applies."
msgstr ""
#: ./doc/admin-guide-cloud/ch_identity_mgmt.xml:240(replaceable)
#: ./doc/admin-guide-cloud/ch_identity_mgmt.xml:241(replaceable)
msgid "API_NAME"
msgstr ""
#: ./doc/admin-guide-cloud/ch_identity_mgmt.xml:240(replaceable)
#: ./doc/admin-guide-cloud/ch_identity_mgmt.xml:241(replaceable)
msgid "RULE_STATEMENT"
msgstr ""
#: ./doc/admin-guide-cloud/ch_identity_mgmt.xml:240(replaceable)
#: ./doc/admin-guide-cloud/ch_identity_mgmt.xml:241(replaceable)
msgid "MATCH_STATEMENT"
msgstr ""
#: ./doc/admin-guide-cloud/ch_identity_mgmt.xml:241(para) ./doc/admin-guide-cloud/blockstorage/section_glusterfs_backend.xml:56(para) ./doc/admin-guide-cloud/blockstorage/section_glusterfs_backend.xml:106(para) ./doc/admin-guide-cloud/blockstorage/section_nfs_backend.xml:54(para) ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:164(para)
#: ./doc/admin-guide-cloud/ch_identity_mgmt.xml:242(para) ./doc/admin-guide-cloud/blockstorage/section_glusterfs_backend.xml:56(para) ./doc/admin-guide-cloud/blockstorage/section_glusterfs_backend.xml:106(para) ./doc/admin-guide-cloud/blockstorage/section_nfs_backend.xml:54(para) ./doc/admin-guide-cloud/compute/section_trusted-compute-pools.xml:79(para) ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:164(para)
msgid "Where:"
msgstr ""
#: ./doc/admin-guide-cloud/ch_identity_mgmt.xml:242(para)
#: ./doc/admin-guide-cloud/ch_identity_mgmt.xml:243(para)
msgid "<code><replaceable>RULE_STATEMENT</replaceable></code> can contain <code><replaceable>RULE_STATEMENT</replaceable></code> or <code><replaceable>MATCH_STATEMENT</replaceable></code>."
msgstr ""
#: ./doc/admin-guide-cloud/ch_identity_mgmt.xml:243(para)
#: ./doc/admin-guide-cloud/ch_identity_mgmt.xml:244(para)
msgid "<code><replaceable>MATCH_STATEMENT</replaceable></code> is a set of identifiers that must match between the token provided by the caller of the API and the parameters or target entities of the API call in question. For example:"
msgstr ""
#: ./doc/admin-guide-cloud/ch_identity_mgmt.xml:247(para)
#: ./doc/admin-guide-cloud/ch_identity_mgmt.xml:248(para)
msgid "Indicates that to create a user, you must have the admin role in your token and the <literal>domain_id</literal> in your token (which implies this must be a domain-scoped token) must match the <literal>domain_id</literal> in the user object that you are trying to create. In other words, you must have the admin role on the domain in which you are creating the user, and the token that you use must be scoped to that domain."
msgstr ""
#: ./doc/admin-guide-cloud/ch_identity_mgmt.xml:253(para)
#: ./doc/admin-guide-cloud/ch_identity_mgmt.xml:254(para)
msgid "Each component of a match statement uses this format:"
msgstr ""
#: ./doc/admin-guide-cloud/ch_identity_mgmt.xml:254(replaceable)
#: ./doc/admin-guide-cloud/ch_identity_mgmt.xml:255(replaceable)
msgid "ATTRIB_FROM_TOKEN"
msgstr ""
#: ./doc/admin-guide-cloud/ch_identity_mgmt.xml:254(replaceable)
#: ./doc/admin-guide-cloud/ch_identity_mgmt.xml:255(replaceable)
msgid "CONSTANT"
msgstr ""
#: ./doc/admin-guide-cloud/ch_identity_mgmt.xml:254(replaceable)
#: ./doc/admin-guide-cloud/ch_identity_mgmt.xml:255(replaceable)
msgid "ATTRIB_RELATED_TO_API_CALL"
msgstr ""
#: ./doc/admin-guide-cloud/ch_identity_mgmt.xml:255(para)
#: ./doc/admin-guide-cloud/ch_identity_mgmt.xml:256(para)
msgid "The Identity service expects these attributes:"
msgstr ""
#: ./doc/admin-guide-cloud/ch_identity_mgmt.xml:256(para)
#: ./doc/admin-guide-cloud/ch_identity_mgmt.xml:257(para)
msgid "Attributes from token: <literal>user_id</literal>, the <literal>domain_id</literal> or <literal>project_id</literal> depending on the scope, and the list of roles you have within that scope."
msgstr ""
#: ./doc/admin-guide-cloud/ch_identity_mgmt.xml:258(para)
#: ./doc/admin-guide-cloud/ch_identity_mgmt.xml:259(para)
msgid "Attributes related to API call: Any parameters passed into the API call are available, along with any filters specified in the query string. You reference attributes of objects passed with an object.attribute syntax (such as, <literal>user.domain_id</literal>). The target objects of an API are also available using a target.object.attribute syntax. For instance:"
msgstr ""
#: ./doc/admin-guide-cloud/ch_identity_mgmt.xml:265(para)
#: ./doc/admin-guide-cloud/ch_identity_mgmt.xml:266(para)
msgid "would ensure that Identity only deletes the user object in the same domain as the provided token."
msgstr ""
#: ./doc/admin-guide-cloud/ch_identity_mgmt.xml:267(para)
#: ./doc/admin-guide-cloud/ch_identity_mgmt.xml:268(para)
msgid "Every target object has an `id` and a `name` available as `target.<replaceable>OBJECT</replaceable>.id` and `target.<replaceable>OBJECT</replaceable>.name`. Identity retrieves other attributes from the database, and the attributes vary between object types. The Identity service filters out some database fields, such as user passwords."
msgstr ""
#: ./doc/admin-guide-cloud/ch_identity_mgmt.xml:272(para)
#: ./doc/admin-guide-cloud/ch_identity_mgmt.xml:273(para)
msgid "List of object attributes:"
msgstr ""
#: ./doc/admin-guide-cloud/ch_identity_mgmt.xml:302(para)
#: ./doc/admin-guide-cloud/ch_identity_mgmt.xml:303(para)
msgid "The default <filename>policy.json</filename> file supplied provides a somewhat basic example of API protection, and does not assume any particular use of domains. Refer to <filename>policy.v3cloudsample.json</filename> as an example of multi-domain configuration installations where a cloud provider wants to delegate administration of the contents of a domain to a particular admin domain. This example policy file also shows the use of an admin_domain to allow a cloud provider to enable cloud administrators to have wider access across the APIs."
msgstr ""
#: ./doc/admin-guide-cloud/ch_identity_mgmt.xml:311(para)
#: ./doc/admin-guide-cloud/ch_identity_mgmt.xml:312(para)
msgid "A clean installation could start with the standard policy file, to allow creation of the admin_domain with the first users within it. You could then obtain the domain_id of the admin domain, paste the ID into a modified version of <filename>policy.v3cloudsample.json</filename>, and then enable it as the main policy file."
msgstr ""
@ -691,7 +691,7 @@ msgid "The <literal>scheduler</literal> is used to select the most suitable comp
msgstr ""
#: ./doc/admin-guide-cloud/ch_compute.xml:60(para)
msgid "Compute uses a messaging-based, <literal>shared nothing</literal> architecture. All major components exist on multiple servers, including the compute, volume, and network controllers, and the object store or image service. The state of the entire system is stored in a database. The cloud controller communicates with the internal object store using HTTP, but it communicates with the scheduler, network controller, and volume controller using AMQP (advanced message queueing protocol). To avoid blocking a component while waiting for a response, Compute uses asynchronous calls, with a callback that is triggered when a response is received."
msgid "Compute uses a messaging-based, <literal>shared nothing</literal> architecture. All major components exist on multiple servers, including the compute, volume, and network controllers, and the object store or image service. The state of the entire system is stored in a database. The cloud controller communicates with the internal object store using HTTP, but it communicates with the scheduler, network controller, and volume controller using AMQP (advanced message queuing protocol). To avoid blocking a component while waiting for a response, Compute uses asynchronous calls, with a callback that is triggered when a response is received."
msgstr ""
#: ./doc/admin-guide-cloud/ch_compute.xml:69(title)
@ -875,7 +875,7 @@ msgid "Building blocks"
msgstr ""
#: ./doc/admin-guide-cloud/ch_compute.xml:317(para)
msgid "In OpenStack the base operating system is usually copied from an image stored in the OpenStack Image Service. This is the most common case and results in an ephemeral instance that starts from a known template state and loses all accumulated states on virtual machine deletion. It is also possible to put an operating system on a persistent volume in the Cinder volume system. This gives a more traditional persistent system that accumulates states, which are preserved on the Cinder volume across the deletion and re-creation of the virutal machine. To get a list of available images on your system run: <placeholder-1/>"
msgid "In OpenStack the base operating system is usually copied from an image stored in the OpenStack Image Service. This is the most common case and results in an ephemeral instance that starts from a known template state and loses all accumulated states on virtual machine deletion. It is also possible to put an operating system on a persistent volume in the Cinder volume system. This gives a more traditional persistent system that accumulates states, which are preserved on the Cinder volume across the deletion and re-creation of the virtual machine. To get a list of available images on your system run: <placeholder-1/>"
msgstr ""
#: ./doc/admin-guide-cloud/ch_compute.xml:337(para) ./doc/admin-guide-cloud/compute/section_compute-instance-building-blocks.xml:24(para)
@ -1017,7 +1017,7 @@ msgid "Introduction to Networking"
msgstr ""
#: ./doc/admin-guide-cloud/networking/section_networking_introduction.xml:8(para)
msgid "The Networking service, code-named neutron, provides an API that lets you define network connectivity and addressing in the cloud. The Networking service enables operators to leverage different networking technologies to power their cloud networking. The Networking service also provides an API to configure and manage a variety of network services ranging from L3 forwarding and NAT to load balancing, edge firewalls, and IPSEC VPN."
msgid "The Networking service, code-named neutron, provides an API that lets you define network connectivity and addressing in the cloud. The Networking service enables operators to leverage different networking technologies to power their cloud networking. The Networking service also provides an API to configure and manage a variety of network services ranging from L3 forwarding and NAT to load balancing, edge firewalls, and IPsec VPN."
msgstr ""
#: ./doc/admin-guide-cloud/networking/section_networking_introduction.xml:16(para)
@ -1631,7 +1631,7 @@ msgid "Update the plug-in configuration file <filename>/etc/neutron/plugins/linu
msgstr ""
#: ./doc/admin-guide-cloud/networking/section_networking-multi-dhcp-agents.xml:99(title)
msgid "HostA and Hostb: L2 agent"
msgid "HostA and HostB: L2 agent"
msgstr ""
#: ./doc/admin-guide-cloud/networking/section_networking-multi-dhcp-agents.xml:122(para)
@ -5249,7 +5249,7 @@ msgid "OpenStack Networking server with plug-in"
msgstr ""
#: ./doc/admin-guide-cloud/networking/section_networking-adv-config.xml:12(para)
msgid "This web server runs the OpenStack Networking API Web Server. It laods a plug-in and passes the API calls to the plug-in for processing. The <systemitem class=\"service\">neutron-server</systemitem> service receives one or more configuration files as input. For example:"
msgid "This web server runs the OpenStack Networking API Web Server. It loads a plug-in and passes the API calls to the plug-in for processing. The <systemitem class=\"service\">neutron-server</systemitem> service receives one or more configuration files as input. For example:"
msgstr ""
#: ./doc/admin-guide-cloud/networking/section_networking-adv-config.xml:16(replaceable) ./doc/admin-guide-cloud/networking/section_networking-adv-config.xml:38(replaceable) ./doc/admin-guide-cloud/networking/section_networking-adv-config.xml:109(replaceable) ./doc/admin-guide-cloud/networking/section_networking-adv-config.xml:155(replaceable) ./doc/admin-guide-cloud/networking/section_networking-adv-config.xml:309(replaceable)
@ -5429,7 +5429,7 @@ msgid "L3 agent"
msgstr ""
#: ./doc/admin-guide-cloud/networking/section_networking-adv-config.xml:153(para)
msgid "You can run an L3 agent that enables layer 3 forwarding and floating IP support."
msgid "You can run an L3 agent that enables layer-3 forwarding and floating IP support."
msgstr ""
#: ./doc/admin-guide-cloud/networking/section_networking-adv-config.xml:154(para)
@ -5561,7 +5561,7 @@ msgid "L3 metering agent"
msgstr ""
#: ./doc/admin-guide-cloud/networking/section_networking-adv-config.xml:307(para)
msgid "You can run an L3 metering agent that enables layer 3 traffic metering. In general, you should launch the metering agent on all nodes that run the L3 agent:"
msgid "You can run an L3 metering agent that enables layer-3 traffic metering. In general, you should launch the metering agent on all nodes that run the L3 agent:"
msgstr ""
#: ./doc/admin-guide-cloud/networking/section_networking-adv-config.xml:309(replaceable)
@ -6490,6 +6490,118 @@ msgstr ""
msgid "Enables bind checking. Requires use of X.509 as the authentication mechanism for tokens:"
msgstr ""
#: ./doc/admin-guide-cloud/identity/section_caching-layer.xml:8(title)
msgid "Caching layer"
msgstr ""
#: ./doc/admin-guide-cloud/identity/section_caching-layer.xml:9(para)
msgid "OpenStack Identity supports a caching layer that is above the configurable subsystems (for example, token, assignment). OpenStack Identity uses the <link href=\"http://dogpilecache.readthedocs.org/en/latest/\"><literal>dogpile.cache</literal></link> library which allows flexible cache backends. The majority of the caching configuration options are set in the <literal>[cache]</literal> section of the <filename>keystone.conf</filename> file. However, each section that has the capability to be cached usually has a caching boolean value that toggles caching."
msgstr ""
#: ./doc/admin-guide-cloud/identity/section_caching-layer.xml:17(para)
msgid "So to enable only the token backend caching, set the values as follows:"
msgstr ""
#: ./doc/admin-guide-cloud/identity/section_caching-layer.xml:26(para)
msgid "For the Juno release, the default setting is enabled for subsystem caching, but the global toggle is disabled. As a result, no caching in available unless the global toggle for <literal>[cache]</literal> is enabled by setting the value to <literal>true</literal>."
msgstr ""
#: ./doc/admin-guide-cloud/identity/section_caching-layer.xml:31(title)
msgid "Caching for tokens and tokens validation"
msgstr ""
#: ./doc/admin-guide-cloud/identity/section_caching-layer.xml:32(para)
msgid "The token system has a separate <literal>cache_time</literal> configuration option, that can be set to a value above or below the global <literal>expiration_time</literal> default, allowing for different caching behavior from the other systems in OpenStack Identity. This option is set in the <literal>[token]</literal> section of the configuration file."
msgstr ""
#: ./doc/admin-guide-cloud/identity/section_caching-layer.xml:39(para)
msgid "The token revocation list cache time is handled by the configuration option <literal>revocation_cache_time</literal> in the <literal>[token]</literal> section. The revocation list is refreshed whenever a token is revoked. It typically sees significantly more requests than specific token retrievals or token validation calls."
msgstr ""
#: ./doc/admin-guide-cloud/identity/section_caching-layer.xml:46(para)
msgid "Here is a list of actions that are affected by the cached time: getting a new token, revoking tokens, validating tokens, checking v2 tokens, and checking v3 tokens."
msgstr ""
#: ./doc/admin-guide-cloud/identity/section_caching-layer.xml:49(para)
msgid "The delete token API calls invalidate the cache for the tokens being acted upon, as well as invalidating the cache for the revoked token list and the validate/check token calls."
msgstr ""
#: ./doc/admin-guide-cloud/identity/section_caching-layer.xml:52(para)
msgid "Token caching is configurable independently of the <literal>revocation_list</literal> caching. Lifted expiration checks from the token drivers to the token manager. This ensures that cached tokens will still raise a <literal>TokenNotFound</literal> flag when expired."
msgstr ""
#: ./doc/admin-guide-cloud/identity/section_caching-layer.xml:56(para)
msgid "For cache consistency, all token IDs are transformed into the short token hash at the provider and token driver level. Some methods have access to the full ID (PKI Tokens), and some methods do not. Cache invalidation is inconsistent without token ID normalization."
msgstr ""
#: ./doc/admin-guide-cloud/identity/section_caching-layer.xml:62(title)
msgid "Caching around assignment CRUD"
msgstr ""
#: ./doc/admin-guide-cloud/identity/section_caching-layer.xml:63(para)
msgid "The assignment system has a separate <literal>cache_time</literal> configuration option, that can be set to a value above or below the global <literal>expiration_time</literal> default, allowing for different caching behavior from the other systems in Identity service. This option is set in the <literal>[assignment]</literal> section of the configuration file."
msgstr ""
#: ./doc/admin-guide-cloud/identity/section_caching-layer.xml:68(para)
msgid "Currently <literal>assignment</literal> has caching for <literal>project</literal>, <literal>domain</literal>, and <literal>role</literal> specific requests (primarily around the CRUD actions). Caching is currently not implemented on grants. The <literal>list</literal> methods are not subject to caching."
msgstr ""
#: ./doc/admin-guide-cloud/identity/section_caching-layer.xml:73(para)
msgid "Here is a list of actions that are affected by the assignment: assign domain API, assign project API, and assign role API."
msgstr ""
#: ./doc/admin-guide-cloud/identity/section_caching-layer.xml:75(para)
msgid "The create, update, and delete actions for domains, projects and roles will perform proper invalidations of the cached methods listed above."
msgstr ""
#: ./doc/admin-guide-cloud/identity/section_caching-layer.xml:79(para)
msgid "If a read-only <literal>assignment</literal> back end is in use, the cache will not immediately reflect changes on the back end. Any given change may take up to the <literal>cache_time</literal> (if set in the <literal>[assignment]</literal> section of the configuration file) or the global <literal>expiration_time</literal> (set in the <literal>[cache]</literal> section of the configuration file) before it is reflected. If this type of delay (when using a read-only <literal>assignment</literal> backend) is an issue, it is recommended that caching be disabled on <literal>assignment</literal>. To disable caching specifically on <literal>assignment</literal>, in the <literal>[assignment]</literal> section of the configuration set <literal>caching</literal> to <literal>False</literal>."
msgstr ""
#: ./doc/admin-guide-cloud/identity/section_caching-layer.xml:93(para)
msgid "For more information about the different backends (and configuration options), see:"
msgstr ""
#: ./doc/admin-guide-cloud/identity/section_caching-layer.xml:96(literal)
msgid "dogpile.cache.backends.memory"
msgstr ""
#: ./doc/admin-guide-cloud/identity/section_caching-layer.xml:98(literal)
msgid "dogpile.cache.backends.memcached"
msgstr ""
#: ./doc/admin-guide-cloud/identity/section_caching-layer.xml:99(para)
msgid "The memory backend is not suitable for use in a production environment."
msgstr ""
#: ./doc/admin-guide-cloud/identity/section_caching-layer.xml:101(literal)
msgid "dogpile.cache.backends.redis"
msgstr ""
#: ./doc/admin-guide-cloud/identity/section_caching-layer.xml:103(literal)
msgid "dogpile.cache.backends.file"
msgstr ""
#: ./doc/admin-guide-cloud/identity/section_caching-layer.xml:104(literal)
msgid "keystone.common.cache.backends.mongo"
msgstr ""
#: ./doc/admin-guide-cloud/identity/section_caching-layer.xml:107(title)
msgid "Configure the Memcached backend"
msgstr ""
#: ./doc/admin-guide-cloud/identity/section_caching-layer.xml:108(para)
msgid "The following example shows how to configure the memcached backend:"
msgstr ""
#: ./doc/admin-guide-cloud/identity/section_caching-layer.xml:113(replaceable)
msgid "127.0.0.1"
msgstr ""
#: ./doc/admin-guide-cloud/identity/section_caching-layer.xml:114(para)
msgid "You need to specify the URL to reach the <literal>memcached</literal> instance with the <literal>backend_argument</literal> parameter."
msgstr ""
#: ./doc/admin-guide-cloud/blockstorage/section_ts_HTTP_bad_req_in_cinder_vol_log.xml:7(title) ./doc/admin-guide-cloud/blockstorage/section_ts_failed_attach_vol_after_detach.xml:7(title)
msgid "Failed to attach volume after detaching"
msgstr ""
@ -7451,7 +7563,7 @@ msgid "Issues with <literal>state_path</literal> and <literal>volumes_dir</liter
msgstr ""
#: ./doc/admin-guide-cloud/blockstorage/section_ts_cinder_config.xml:113(para)
msgid "The OpenStack Block Storage uses <placeholder-1/> as the default iscsi helper and implements persistent targets. This means that in the case of a tgt restart or even a node reboot your existing volumes on that node will be restored automatically with their original IQN."
msgid "The OpenStack Block Storage uses <placeholder-1/> as the default iSCSI helper and implements persistent targets. This means that in the case of a tgt restart or even a node reboot your existing volumes on that node will be restored automatically with their original IQN."
msgstr ""
#: ./doc/admin-guide-cloud/blockstorage/section_ts_cinder_config.xml:118(para)
@ -7610,6 +7722,138 @@ msgstr ""
msgid "The following values in the <filename>/etc/nova/nova.conf</filename> file (on every node) are required for the <systemitem>memcache</systemitem> driver:"
msgstr ""
#. When image changes, this message will be marked fuzzy or untranslated for you.
#. It doesn't matter what you translate it to: it's not used at all.
#: ./doc/admin-guide-cloud/compute/section_trusted-compute-pools.xml:46(None) ./doc/admin-guide-cloud/compute/section_trusted-compute-pools.xml:51(None)
msgid "@@image: '../../common/figures/OpenStackTrustedComputePool1.png'; md5=858fbd6148b927723cea5ad2c88d54bd"
msgstr ""
#. When image changes, this message will be marked fuzzy or untranslated for you.
#. It doesn't matter what you translate it to: it's not used at all.
#: ./doc/admin-guide-cloud/compute/section_trusted-compute-pools.xml:151(None) ./doc/admin-guide-cloud/compute/section_trusted-compute-pools.xml:156(None)
msgid "@@image: '../../common/figures/OpenStackTrustedComputePool2.png'; md5=077261c595464638c4b3fcc92b6afb9a"
msgstr ""
#: ./doc/admin-guide-cloud/compute/section_trusted-compute-pools.xml:7(title)
msgid "Trusted compute pools"
msgstr ""
#: ./doc/admin-guide-cloud/compute/section_trusted-compute-pools.xml:8(para)
msgid "Trusted compute pools enable administrators to designate a group of compute hosts as trusted. These hosts use hardware-based security features, such as the Intel Trusted Execution Technology (TXT), to provide an additional level of security. Combined with an external stand-alone, web-based remote attestation server, cloud providers can ensure that the compute node runs only software with verified measurements and can ensure a secure cloud stack."
msgstr ""
#: ./doc/admin-guide-cloud/compute/section_trusted-compute-pools.xml:14(para)
msgid "Using the trusted compute pools, cloud subscribers can request services to run on verified compute nodes."
msgstr ""
#: ./doc/admin-guide-cloud/compute/section_trusted-compute-pools.xml:16(para)
msgid "The remote attestation server performs node verification as follows:"
msgstr ""
#: ./doc/admin-guide-cloud/compute/section_trusted-compute-pools.xml:20(para)
msgid "Compute nodes boot with Intel TXT technology enabled."
msgstr ""
#: ./doc/admin-guide-cloud/compute/section_trusted-compute-pools.xml:24(para)
msgid "The compute node BIOS, hypervisor, and OS are measured."
msgstr ""
#: ./doc/admin-guide-cloud/compute/section_trusted-compute-pools.xml:28(para)
msgid "Measured data is sent to the attestation server when challenged by the attestation server."
msgstr ""
#: ./doc/admin-guide-cloud/compute/section_trusted-compute-pools.xml:32(para)
msgid "The attestation server verifies those measurements against a good and known database to determine node trustworthiness."
msgstr ""
#: ./doc/admin-guide-cloud/compute/section_trusted-compute-pools.xml:36(para)
msgid "A description of how to set up an attestation service is beyond the scope of this document. For an open source project that you can use to implement an attestation service, see the <link href=\"https://github.com/OpenAttestation/OpenAttestation\">Open Attestation</link> project."
msgstr ""
#: ./doc/admin-guide-cloud/compute/section_trusted-compute-pools.xml:55(title)
msgid "Configure Compute to use trusted compute pools"
msgstr ""
#: ./doc/admin-guide-cloud/compute/section_trusted-compute-pools.xml:58(para)
msgid "Enable scheduling support for trusted compute pools by adding the following lines in the <literal>DEFAULT</literal> section in the <filename>/etc/nova/nova.conf</filename> file:"
msgstr ""
#: ./doc/admin-guide-cloud/compute/section_trusted-compute-pools.xml:67(para)
msgid "Specify the connection information for your attestation service by adding the following lines to the <literal>trusted_computing</literal> section in the <filename>/etc/nova/nova.conf</filename> file:"
msgstr ""
#: ./doc/admin-guide-cloud/compute/section_trusted-compute-pools.xml:82(term)
msgid "server"
msgstr ""
#: ./doc/admin-guide-cloud/compute/section_trusted-compute-pools.xml:84(para)
msgid "Host name or IP address of the host that runs the attestation service."
msgstr ""
#: ./doc/admin-guide-cloud/compute/section_trusted-compute-pools.xml:89(term)
msgid "port"
msgstr ""
#: ./doc/admin-guide-cloud/compute/section_trusted-compute-pools.xml:91(para)
msgid "HTTPS port for the attestation service."
msgstr ""
#: ./doc/admin-guide-cloud/compute/section_trusted-compute-pools.xml:95(term)
msgid "server_ca_file"
msgstr ""
#: ./doc/admin-guide-cloud/compute/section_trusted-compute-pools.xml:97(para)
msgid "Certificate file used to verify the attestation server's identity."
msgstr ""
#: ./doc/admin-guide-cloud/compute/section_trusted-compute-pools.xml:102(term)
msgid "api_url"
msgstr ""
#: ./doc/admin-guide-cloud/compute/section_trusted-compute-pools.xml:104(para)
msgid "The attestation service's URL path."
msgstr ""
#: ./doc/admin-guide-cloud/compute/section_trusted-compute-pools.xml:108(term)
msgid "auth_blob"
msgstr ""
#: ./doc/admin-guide-cloud/compute/section_trusted-compute-pools.xml:110(para)
msgid "An authentication blob, which is required by the attestation service."
msgstr ""
#: ./doc/admin-guide-cloud/compute/section_trusted-compute-pools.xml:118(para)
msgid "Restart the <systemitem class=\"service\">nova-compute</systemitem> and <systemitem class=\"service\">nova-scheduler</systemitem> services."
msgstr ""
#: ./doc/admin-guide-cloud/compute/section_trusted-compute-pools.xml:125(title)
msgid "Configuration reference"
msgstr ""
#: ./doc/admin-guide-cloud/compute/section_trusted-compute-pools.xml:126(para)
msgid "To customize the trusted compute pools, use the following configuration option settings:"
msgstr ""
#: ./doc/admin-guide-cloud/compute/section_trusted-compute-pools.xml:133(title)
msgid "Specify trusted flavors"
msgstr ""
#: ./doc/admin-guide-cloud/compute/section_trusted-compute-pools.xml:134(para)
msgid "To designate hosts as trusted:"
msgstr ""
#: ./doc/admin-guide-cloud/compute/section_trusted-compute-pools.xml:137(para)
msgid "Configure one or more flavors as trusted by using the <placeholder-1/> command. For example, to set the <literal>m1.tiny</literal> flavor as trusted:"
msgstr ""
#: ./doc/admin-guide-cloud/compute/section_trusted-compute-pools.xml:142(para)
msgid "Request that your instance be run on a trusted host, by specifying a trusted flavor when booting the instance. For example:"
msgstr ""
#: ./doc/admin-guide-cloud/compute/section_trusted-compute-pools.xml:146(title)
msgid "Trusted compute pool"
msgstr ""
#: ./doc/admin-guide-cloud/compute/section_compute-instance-building-blocks.xml:7(title)
msgid "Instance building blocks"
msgstr ""
@ -8361,7 +8605,7 @@ msgid "Services:"
msgstr ""
#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:20(para)
msgid "<systemitem class=\"service\">nova-api</systemitem>. Receives XML requests and sends them to the rest of the system. It is a wsgi app that routes and authenticate requests. It supports the EC2 and OpenStack APIs. There is a <filename>nova-api.conf</filename> file created when you install Compute."
msgid "<systemitem class=\"service\">nova-api</systemitem>. Receives XML requests and sends them to the rest of the system. It is a WSGI app that routes and authenticate requests. It supports the EC2 and OpenStack APIs. There is a <filename>nova-api.conf</filename> file created when you install Compute."
msgstr ""
#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:27(para)
@ -8927,7 +9171,7 @@ msgid "HTTP"
msgstr ""
#: ./doc/admin-guide-cloud/compute/section_compute-image-mgt.xml:57(para)
msgid "OpenStack Image Service can read virtual machine images that are available on the internet using HTTP. This store is read only."
msgid "OpenStack Image Service can read virtual machine images that are available on the Internet using HTTP. This store is read only."
msgstr ""
#: ./doc/admin-guide-cloud/compute/section_compute-image-mgt.xml:63(term)
@ -9038,6 +9282,46 @@ msgstr ""
msgid "(ListOpt) Comma-separated list containing first the Filter class to use, followed by that Filter arguments (which vary depending on the Filter class selected)."
msgstr ""
#: ./doc/admin-guide-cloud/compute/section_compute_config-firewalls.xml:7(title)
msgid "Compute service node firewall requirements"
msgstr ""
#: ./doc/admin-guide-cloud/compute/section_compute_config-firewalls.xml:8(para)
msgid "Console connections for virtual machines, whether direct or through a proxy, are received on ports <literal>5900</literal> to <literal>5999</literal>. You must configure the firewall on each Compute service node to enable network traffic on these ports."
msgstr ""
#: ./doc/admin-guide-cloud/compute/section_compute_config-firewalls.xml:12(title)
msgid "Configure the service-node firewall"
msgstr ""
#: ./doc/admin-guide-cloud/compute/section_compute_config-firewalls.xml:13(para)
msgid "On the server that hosts the Compute service, log in as <systemitem>root</systemitem>."
msgstr ""
#: ./doc/admin-guide-cloud/compute/section_compute_config-firewalls.xml:15(para)
msgid "Edit the <filename>/etc/sysconfig/iptables</filename> file."
msgstr ""
#: ./doc/admin-guide-cloud/compute/section_compute_config-firewalls.xml:21(para)
msgid "Add an INPUT rule that allows TCP traffic on ports that range from <literal>5900</literal> to <literal>5999</literal>:"
msgstr ""
#: ./doc/admin-guide-cloud/compute/section_compute_config-firewalls.xml:27(para)
msgid "The new rule must appear before any INPUT rules that REJECT traffic."
msgstr ""
#: ./doc/admin-guide-cloud/compute/section_compute_config-firewalls.xml:33(para)
msgid "Save the changes to the <filename>/etc/sysconfig/iptables</filename> file."
msgstr ""
#: ./doc/admin-guide-cloud/compute/section_compute_config-firewalls.xml:39(para)
msgid "Restart the <systemitem>iptables</systemitem> service to ensure that the change takes effect."
msgstr ""
#: ./doc/admin-guide-cloud/compute/section_compute_config-firewalls.xml:46(para)
msgid "The <systemitem>iptables</systemitem> firewall now enables incoming connections to the Compute services. Repeat this process for each Compute service node."
msgstr ""
#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:5(title)
msgid "Configure migrations"
msgstr ""

1504
doc/arch-design/locale/arch-design.pot
View File

File diff suppressed because it is too large Load Diff

330
doc/cli-reference/locale/cli-reference.pot
View File

File diff suppressed because one or more lines are too long

1276
doc/common/locale/common.pot
View File

File diff suppressed because one or more lines are too long

1781
doc/common/locale/fr.po
View File

File diff suppressed because it is too large Load Diff

1789
doc/common/locale/ja.po
View File

File diff suppressed because it is too large Load Diff

517
doc/config-reference/locale/config-reference.pot
View File

@ -1,7 +1,7 @@
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"POT-Creation-Date: 2014-07-29 06:09+0000\n"
"POT-Creation-Date: 2014-08-15 06:09+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"
@ -1329,6 +1329,74 @@ msgstr ""
msgid "neutron-server"
msgstr ""
#: ./doc/config-reference/networking/section_rpc-for-networking.xml:8(title) ./doc/config-reference/compute/section_rpc.xml:8(title)
msgid "Configure the Oslo RPC messaging system"
msgstr ""
#: ./doc/config-reference/networking/section_rpc-for-networking.xml:10(para) ./doc/config-reference/orchestration/section_orchestration-rpc.xml:8(para)
msgid "OpenStack projects use an open standard for messaging middleware known as AMQP. This messaging middleware enables the OpenStack services that run on multiple servers to talk to each other. OpenStack Oslo RPC supports three implementations of AMQP: <application>RabbitMQ</application>, <application>Qpid</application>, and <application>ZeroMQ</application>."
msgstr ""
#: ./doc/config-reference/networking/section_rpc-for-networking.xml:19(title) ./doc/config-reference/database-service/section-databaseservice-rpc.xml:17(title) ./doc/config-reference/orchestration/section_orchestration-rpc.xml:17(title) ./doc/config-reference/compute/section_rpc.xml:16(title)
msgid "Configure RabbitMQ"
msgstr ""
#: ./doc/config-reference/networking/section_rpc-for-networking.xml:21(para)
msgid "OpenStack Oslo RPC uses <application>RabbitMQ</application> by default. Use these options to configure the <application>RabbitMQ</application> message system. The <option>rpc_backend</option> option is optional as long as <application>RabbitMQ</application> is the default messaging system. However, if it is included the configuration, you must set it to <literal>neutron.openstack.common.rpc.impl_kombu</literal>."
msgstr ""
#: ./doc/config-reference/networking/section_rpc-for-networking.xml:35(para)
msgid "Use these options to configure the <application>RabbitMQ</application> messaging system. You can configure messaging communication for different installation scenarios, tune retries for RabbitMQ, and define the size of the RPC thread pool. To monitor notifications through RabbitMQ, you must set the <option>notification_driver</option> option to <literal>neutron.notifier.rabbit_notifier</literal> in the <filename>neutron.conf</filename> file:"
msgstr ""
#: ./doc/config-reference/networking/section_rpc-for-networking.xml:46(title) ./doc/config-reference/database-service/section-databaseservice-rpc.xml:24(title) ./doc/config-reference/orchestration/section_orchestration-rpc.xml:42(title) ./doc/config-reference/compute/section_rpc.xml:40(title)
msgid "Configure Qpid"
msgstr ""
#: ./doc/config-reference/networking/section_rpc-for-networking.xml:47(para)
msgid "Use these options to configure the <application>Qpid</application> messaging system for OpenStack Oslo RPC. <application>Qpid</application> is not the default messaging system, so you must enable it by setting the <option>rpc_backend</option> option in the <filename>neutron.conf</filename> file:"
msgstr ""
#: ./doc/config-reference/networking/section_rpc-for-networking.xml:56(para)
msgid "This critical option points the compute nodes to the <application>Qpid</application> broker (server). Set the <option>qpid_hostname</option> option to the host name where the broker runs in the <filename>neutron.conf</filename> file."
msgstr ""
#: ./doc/config-reference/networking/section_rpc-for-networking.xml:62(para) ./doc/config-reference/compute/section_rpc.xml:53(para)
msgid "The <option>--qpid_hostname</option> option accepts a host name or IP address value."
msgstr ""
#: ./doc/config-reference/networking/section_rpc-for-networking.xml:69(para) ./doc/config-reference/orchestration/section_orchestration-rpc.xml:61(para) ./doc/config-reference/compute/section_rpc.xml:57(para)
msgid "If the <application>Qpid</application> broker listens on a port other than the AMQP default of <literal>5672</literal>, you must set the <option>qpid_port</option> option to that value:"
msgstr ""
#: ./doc/config-reference/networking/section_rpc-for-networking.xml:78(para) ./doc/config-reference/orchestration/section_orchestration-rpc.xml:68(para) ./doc/config-reference/compute/section_rpc.xml:62(para)
msgid "If you configure the <application>Qpid</application> broker to require authentication, you must add a user name and password to the configuration:"
msgstr ""
#: ./doc/config-reference/networking/section_rpc-for-networking.xml:87(para) ./doc/config-reference/orchestration/section_orchestration-rpc.xml:74(para) ./doc/config-reference/compute/section_rpc.xml:67(para)
msgid "By default, TCP is used as the transport. To enable SSL, set the <option>qpid_protocol</option> option:"
msgstr ""
#: ./doc/config-reference/networking/section_rpc-for-networking.xml:94(para) ./doc/config-reference/orchestration/section_orchestration-rpc.xml:79(para)
msgid "Use these additional options to configure the Qpid messaging driver for OpenStack Oslo RPC. These options are used infrequently."
msgstr ""
#: ./doc/config-reference/networking/section_rpc-for-networking.xml:102(title) ./doc/config-reference/orchestration/section_orchestration-rpc.xml:87(title) ./doc/config-reference/compute/section_rpc.xml:76(title)
msgid "Configure ZeroMQ"
msgstr ""
#: ./doc/config-reference/networking/section_rpc-for-networking.xml:103(para)
msgid "Use these options to configure the <application>ZeroMQ</application> messaging system for OpenStack Oslo RPC. <application>ZeroMQ</application> is not the default messaging system, so you must enable it by setting the <option>rpc_backend</option> option in the <filename>neutron.conf</filename> file:"
msgstr ""
#: ./doc/config-reference/networking/section_rpc-for-networking.xml:112(title) ./doc/config-reference/database-service/section-databaseservice-rpc.xml:38(title) ./doc/config-reference/orchestration/section_orchestration-rpc.xml:97(title) ./doc/config-reference/compute/section_rpc.xml:86(title)
msgid "Configure messaging"
msgstr ""
#: ./doc/config-reference/networking/section_rpc-for-networking.xml:114(para) ./doc/config-reference/database-service/section-databaseservice-rpc.xml:40(para) ./doc/config-reference/orchestration/section_orchestration-rpc.xml:99(para)
msgid "Use these common options to configure the <application>RabbitMQ</application>, <application>Qpid</application>, and <application>ZeroMq</application> messaging drivers:"
msgstr ""
#: ./doc/config-reference/telemetry/section_telemetry-sample-configuration-files.xml:6(title)
msgid "Telemetry sample configuration files"
msgstr ""
@ -2430,7 +2498,7 @@ msgstr ""
msgid "The Huawei driver supports the iSCSI and Fibre Channel connections and enables OceanStor T series unified storage, OceanStor Dorado high-performance storage, and OceanStor HVS high-end storage to provide block storage services for OpenStack."
msgstr ""
#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:11(title) ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:34(title) ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:24(title) ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:42(title) ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:66(title) ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:325(title) ./doc/config-reference/block-storage/drivers/emc-vnx-direct-driver.xml:33(title) ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:231(title) ./doc/config-reference/block-storage/drivers/hds-hnas-driver.xml:24(title)
#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:11(title) ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:34(title) ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:24(title) ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:42(title) ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:66(title) ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:325(title) ./doc/config-reference/block-storage/drivers/prophetstor-dpl-driver.xml:12(title) ./doc/config-reference/block-storage/drivers/emc-vnx-direct-driver.xml:33(title) ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:231(title) ./doc/config-reference/block-storage/drivers/hds-hnas-driver.xml:24(title)
msgid "Supported operations"
msgstr ""
@ -4316,6 +4384,106 @@ msgstr ""
msgid "Add server associations on the VSA with the associated CHAPS and initiator information. The name should correspond to the <parameter>hostname</parameter> of the <parameter>nova-compute</parameter> node. For Xen, this is the hypervisor host name. To do this, use either CLIQ or the Centralized Management Console."
msgstr ""
#: ./doc/config-reference/block-storage/drivers/prophetstor-dpl-driver.xml:6(title)
msgid "ProphetStor DPL Fibre Channel and iSCSI drivers"
msgstr ""
#: ./doc/config-reference/block-storage/drivers/prophetstor-dpl-driver.xml:7(para)
msgid "The <literal>DPLFCDriver</literal> and <literal>DPLISCSIDriver</literal> drivers run volume operations by communicating with the ProphetStor DPL storage system over HTTPS."
msgstr ""
#: ./doc/config-reference/block-storage/drivers/prophetstor-dpl-driver.xml:15(para)
msgid "Volume create/delete."
msgstr ""
#: ./doc/config-reference/block-storage/drivers/prophetstor-dpl-driver.xml:18(para)
msgid "Volume attach/detach."
msgstr ""
#: ./doc/config-reference/block-storage/drivers/prophetstor-dpl-driver.xml:21(para)
msgid "Snapshot create/delete."
msgstr ""
#: ./doc/config-reference/block-storage/drivers/prophetstor-dpl-driver.xml:24(para)
msgid "Create volume from snapshot."
msgstr ""
#: ./doc/config-reference/block-storage/drivers/prophetstor-dpl-driver.xml:27(para)
msgid "Get volume stats."
msgstr ""
#: ./doc/config-reference/block-storage/drivers/prophetstor-dpl-driver.xml:30(para)
msgid "Clone volume."
msgstr ""
#: ./doc/config-reference/block-storage/drivers/prophetstor-dpl-driver.xml:33(para)
msgid "Extend volume."
msgstr ""
#: ./doc/config-reference/block-storage/drivers/prophetstor-dpl-driver.xml:36(para)
msgid "Copy image to volume."
msgstr ""
#: ./doc/config-reference/block-storage/drivers/prophetstor-dpl-driver.xml:39(para)
msgid "Copy volume to image."
msgstr ""
#: ./doc/config-reference/block-storage/drivers/prophetstor-dpl-driver.xml:44(title)
msgid "Enable the Fibre Channel or iSCSI drivers"
msgstr ""
#: ./doc/config-reference/block-storage/drivers/prophetstor-dpl-driver.xml:45(para)
msgid "The <literal>DPLFCDriver</literal> and <literal>DPLISCSIDriver</literal> are installed with the OpenStack software."
msgstr ""
#: ./doc/config-reference/block-storage/drivers/prophetstor-dpl-driver.xml:50(para)
msgid "Query DPL pool id for configure <literal>dpl_pool</literal> of the <filename>cinder.conf</filename>."
msgstr ""
#: ./doc/config-reference/block-storage/drivers/prophetstor-dpl-driver.xml:54(para)
msgid "Logon onto the DPL storage system with administrator access."
msgstr ""
#: ./doc/config-reference/block-storage/drivers/prophetstor-dpl-driver.xml:56(replaceable) ./doc/config-reference/block-storage/drivers/prophetstor-dpl-driver.xml:77(replaceable)
msgid "DPL IP ADDRESS"
msgstr ""
#: ./doc/config-reference/block-storage/drivers/prophetstor-dpl-driver.xml:59(para)
msgid "View the current usable pool id."
msgstr ""
#: ./doc/config-reference/block-storage/drivers/prophetstor-dpl-driver.xml:64(para)
msgid "Use <literal>d5bd40b58ea84e9da09dcf25a01fdc07</literal> to config the <literal>dpl_pool</literal> of <filename>/etc/cinder/cinder.conf</filename>."
msgstr ""
#: ./doc/config-reference/block-storage/drivers/prophetstor-dpl-driver.xml:69(para)
msgid "Other management command can reference by command help <placeholder-1/>."
msgstr ""
#: ./doc/config-reference/block-storage/drivers/prophetstor-dpl-driver.xml:73(para)
msgid "Make the following changes on the volume node <filename>/etc/cinder/cinder.conf</filename> file."
msgstr ""
#: ./doc/config-reference/block-storage/drivers/prophetstor-dpl-driver.xml:80(replaceable) ./doc/config-reference/compute/section_compute-cells.xml:316(replaceable)
msgid "USERNAME"
msgstr ""
#: ./doc/config-reference/block-storage/drivers/prophetstor-dpl-driver.xml:83(replaceable) ./doc/config-reference/compute/section_compute-cells.xml:316(replaceable)
msgid "PASSWORD"
msgstr ""
#: ./doc/config-reference/block-storage/drivers/prophetstor-dpl-driver.xml:101(para)
msgid "Save the changes to the <filename>/etc/cinder/cinder.conf</filename> file and restart the <systemitem class=\"service\">cinder-volume</systemitem> service."
msgstr ""
#: ./doc/config-reference/block-storage/drivers/prophetstor-dpl-driver.xml:107(para)
msgid "The ProphetStor Fibre Channel or iSCSI drivers are now enabled on your OpenStack system. If you experience problems, review the Block Storage service log files for errors."
msgstr ""
#: ./doc/config-reference/block-storage/drivers/prophetstor-dpl-driver.xml:111(para)
msgid "The following table contains the options supported by the ProphetStor DPL driver."
msgstr ""
#: ./doc/config-reference/block-storage/drivers/glusterfs-driver.xml:6(title)
msgid "GlusterFS driver"
msgstr ""
@ -6674,18 +6842,10 @@ msgstr ""
msgid "OpenStack projects use an open standard for messaging middleware known as AMQP. This messaging middleware enables the OpenStack services that run on multiple servers to talk to each other. OpenStack Trove RPC supports three implementations of AMQP: <application>RabbitMQ</application>, <application>Qpid</application>, and <application>ZeroMQ</application>."
msgstr ""
#: ./doc/config-reference/database-service/section-databaseservice-rpc.xml:17(title) ./doc/config-reference/orchestration/section_orchestration-rpc.xml:17(title)
msgid "Configure RabbitMQ"
msgstr ""
#: ./doc/config-reference/database-service/section-databaseservice-rpc.xml:18(para)
msgid "Use these options to configure the <application>RabbitMQ</application> messaging system:"
msgstr ""
#: ./doc/config-reference/database-service/section-databaseservice-rpc.xml:24(title) ./doc/config-reference/orchestration/section_orchestration-rpc.xml:42(title)
msgid "Configure Qpid"
msgstr ""
#: ./doc/config-reference/database-service/section-databaseservice-rpc.xml:25(para)
msgid "Use these options to configure the <application>Qpid</application> messaging system:"
msgstr ""
@ -6698,18 +6858,6 @@ msgstr ""
msgid "Use these options to configure the <application>ZeroMq</application> messaging system:"
msgstr ""
#: ./doc/config-reference/database-service/section-databaseservice-rpc.xml:38(title) ./doc/config-reference/orchestration/section_orchestration-rpc.xml:97(title)
msgid "Configure messaging"
msgstr ""
#: ./doc/config-reference/database-service/section-databaseservice-rpc.xml:40(para) ./doc/config-reference/orchestration/section_orchestration-rpc.xml:99(para)
msgid "Use these common options to configure the <application>RabbitMQ</application>, <application>Qpid</application>, and <application>ZeroMq</application> messaging drivers:"
msgstr ""
#: ./doc/config-reference/orchestration/section_orchestration-rpc.xml:8(para)
msgid "OpenStack projects use an open standard for messaging middleware known as AMQP. This messaging middleware enables the OpenStack services that run on multiple servers to talk to each other. OpenStack Oslo RPC supports three implementations of AMQP: <application>RabbitMQ</application>, <application>Qpid</application>, and <application>ZeroMQ</application>."
msgstr ""
#: ./doc/config-reference/orchestration/section_orchestration-rpc.xml:19(para)
msgid "OpenStack Oslo RPC uses <application>RabbitMQ</application> by default. Use these options to configure the <application>RabbitMQ</application> message system. The <option>rpc_backend</option> option is optional as long as <application>RabbitMQ</application> is the default messaging system. However, if it is included in the configuration, you must set it to <literal>heat.openstack.common.rpc.impl_kombu</literal>."
msgstr ""
@ -6730,26 +6878,6 @@ msgstr ""
msgid "The <option>qpid_hostname</option> option accepts a host name or IP address value."
msgstr ""
#: ./doc/config-reference/orchestration/section_orchestration-rpc.xml:61(para)
msgid "If the <application>Qpid</application> broker listens on a port other than the AMQP default of <literal>5672</literal>, you must set the <option>qpid_port</option> option to that value:"
msgstr ""
#: ./doc/config-reference/orchestration/section_orchestration-rpc.xml:68(para)
msgid "If you configure the <application>Qpid</application> broker to require authentication, you must add a user name and password to the configuration:"
msgstr ""
#: ./doc/config-reference/orchestration/section_orchestration-rpc.xml:74(para)
msgid "By default, TCP is used as the transport. To enable SSL, set the <option>qpid_protocol</option> option:"
msgstr ""
#: ./doc/config-reference/orchestration/section_orchestration-rpc.xml:79(para)
msgid "Use these additional options to configure the Qpid messaging driver for OpenStack Oslo RPC. These options are used infrequently."
msgstr ""
#: ./doc/config-reference/orchestration/section_orchestration-rpc.xml:87(title)
msgid "Configure ZeroMQ"
msgstr ""
#: ./doc/config-reference/orchestration/section_orchestration-rpc.xml:88(para)
msgid "Use these options to configure the <application>ZeroMQ</application> messaging system for OpenStack Oslo RPC. <application>ZeroMQ</application> is not the default messaging system, so you must enable it by setting the <option>rpc_backend</option> option in the <filename>heat.conf</filename> file:"
msgstr ""
@ -7078,6 +7206,54 @@ msgstr ""
msgid "Local <link href=\"http://en.wikipedia.org/wiki/Logical_Volume_Manager_(Linux)\">LVM volumes</link> can also be used. Set <literal>images_volume_group = nova_local</literal> where <literal>nova_local</literal> is the name of the LVM group you have created."
msgstr ""
#: ./doc/config-reference/compute/section_xapi-ami-setup.xml:8(title)
msgid "Prepare for AMI type images"
msgstr ""
#: ./doc/config-reference/compute/section_xapi-ami-setup.xml:9(para)
msgid "To support AMI type images in your OpenStack installation, you must create a <filename>/boot/guest</filename> directory inside Dom0. The OpenStack VM extracts the kernel and ramdisk from the AKI and ARI images puts them in this location."
msgstr ""
#: ./doc/config-reference/compute/section_xapi-ami-setup.xml:13(para)
msgid "OpenStack maintains the contents of this directory and its size should not increase during normal operation. However, in case of power failures or accidental shutdowns, some files might be left over. To prevent these files from filling the Dom0 disk, set up this directory as a symlink that points to a subdirectory of the local SR."
msgstr ""
#: ./doc/config-reference/compute/section_xapi-ami-setup.xml:19(para)
msgid "Run these commands in Dom0 to achieve this setup:"
msgstr ""
#: ./doc/config-reference/compute/section_rpc.xml:9(para)
msgid "OpenStack projects use AMQP, an open standard for messaging middleware. OpenStack services that run on multiple servers to talk to each other. OpenStack Oslo RPC supports three implementations of AMQP: <application>RabbitMQ</application>, <application>Qpid</application>, and <application>ZeroMQ</application>."
msgstr ""
#: ./doc/config-reference/compute/section_rpc.xml:17(para)
msgid "OpenStack Oslo RPC uses <application>RabbitMQ</application> by default. Use these options to configure the <application>RabbitMQ</application> message system. The <literal>rpc_backend</literal> option is not required as long as <application>RabbitMQ</application> is the default messaging system. However, if it is included the configuration, you must set it to <literal>nova.openstack.common.rpc.impl_kombu</literal>."
msgstr ""
#: ./doc/config-reference/compute/section_rpc.xml:26(para)
msgid "You can use these additional options to configure the <application>RabbitMQ</application> messaging system. You can configure messaging communication for different installation scenarios, tune retries for RabbitMQ, and define the size of the RPC thread pool. To monitor notifications through RabbitMQ, you must set the <option>notification_driver</option> option to <literal>nova.notifier.rabbit_notifier</literal> in the <filename>nova.conf</filename> file. The default for sending usage data is sixty seconds plus a random number of seconds from zero to sixty."
msgstr ""
#: ./doc/config-reference/compute/section_rpc.xml:41(para)
msgid "Use these options to configure the <application>Qpid</application> messaging system for OpenStack Oslo RPC. <application>Qpid</application> is not the default messaging system, so you must enable it by setting the <option>rpc_backend</option> option in the <filename>nova.conf</filename> file."
msgstr ""
#: ./doc/config-reference/compute/section_rpc.xml:48(para)
msgid "This critical option points the compute nodes to the <application>Qpid</application> broker (server). Set <option>qpid_hostname</option> to the host name where the broker runs in the <filename>nova.conf</filename> file."
msgstr ""
#: ./doc/config-reference/compute/section_rpc.xml:70(para)
msgid "This table lists additional options that you use to configure the Qpid messaging driver for OpenStack Oslo RPC. These options are used infrequently."
msgstr ""
#: ./doc/config-reference/compute/section_rpc.xml:77(para)
msgid "Use these options to configure the <application>ZeroMQ</application> messaging system for OpenStack Oslo RPC. <application>ZeroMQ</application> is not the default messaging system, so you must enable it by setting the <option>rpc_backend</option> option in the <filename>nova.conf</filename> file."
msgstr ""
#: ./doc/config-reference/compute/section_rpc.xml:87(para)
msgid "Use these options to configure the <application>RabbitMQ</application> and <application>Qpid</application> messaging drivers."
msgstr ""
#: ./doc/config-reference/compute/section_compute-configure-db.xml:6(title)
msgid "Database configuration"
msgstr ""
@ -7666,15 +7842,6 @@ msgstr ""
msgid "To customize the Baremetal driver, use the configuration option settings documented in <xref linkend=\"config_table_nova_baremetal\"/>."
msgstr ""
#: ./doc/config-reference/compute/section_compute-configure-console.xml:6(title)
msgid "Configure remote console access"
msgstr ""
#. <?dbhtml stop-chunking?>
#: ./doc/config-reference/compute/section_compute-configure-console.xml:8(para)
msgid "OpenStack has two main methods for providing a remote console or remote desktop access to guest Virtual Machines. They are VNC, and SPICE HTML5 and can be used either through the OpenStack dashboard and the command line. Best practice is to select one or the other to run."
msgstr ""
#: ./doc/config-reference/compute/section_hypervisor_lxc.xml:7(title)
msgid "LXC (Linux containers)"
msgstr ""
@ -7925,7 +8092,7 @@ msgstr ""
msgid "How long in seconds to wait for replies from calls between cells."
msgstr ""
#: ./doc/config-reference/compute/section_compute-cells.xml:81(term) ./doc/config-reference/compute/section_compute-cells.xml:208(option)
#: ./doc/config-reference/compute/section_compute-cells.xml:81(option) ./doc/config-reference/compute/section_compute-cells.xml:208(option)
msgid "scheduler_filter_classes"
msgstr ""
@ -7933,7 +8100,7 @@ msgstr ""
msgid "Filter classes that the cells scheduler should use. By default, uses \"<literal>nova.cells.filters.all_filters</literal>\" to map to all cells filters included with Compute."
msgstr ""
#: ./doc/config-reference/compute/section_compute-cells.xml:91(term) ./doc/config-reference/compute/section_compute-cells.xml:219(option) ./doc/config-reference/compute/section_compute-scheduler.xml:673(literal) ./doc/config-reference/compute/section_compute-scheduler.xml:787(literal)
#: ./doc/config-reference/compute/section_compute-cells.xml:91(option) ./doc/config-reference/compute/section_compute-cells.xml:219(option) ./doc/config-reference/compute/section_compute-scheduler.xml:673(literal) ./doc/config-reference/compute/section_compute-scheduler.xml:787(literal)
msgid "scheduler_weight_classes"
msgstr ""
@ -7941,7 +8108,7 @@ msgstr ""
msgid "Weight classes that the scheduler for cells uses. By default, uses <literal>nova.cells.weights.all_weighers</literal> to map to all cells weight algorithms included with Compute."
msgstr ""
#: ./doc/config-reference/compute/section_compute-cells.xml:100(term) ./doc/config-reference/compute/section_compute-scheduler.xml:651(literal) ./doc/config-reference/compute/section_compute-scheduler.xml:654(option) ./doc/config-reference/compute/section_compute-scheduler.xml:777(literal) ./doc/config-reference/compute/section_compute-scheduler.xml:780(option)
#: ./doc/config-reference/compute/section_compute-cells.xml:100(option) ./doc/config-reference/compute/section_compute-scheduler.xml:651(literal) ./doc/config-reference/compute/section_compute-scheduler.xml:654(option) ./doc/config-reference/compute/section_compute-scheduler.xml:777(literal) ./doc/config-reference/compute/section_compute-scheduler.xml:780(option)
msgid "ram_weight_multiplier"
msgstr ""
@ -8073,14 +8240,6 @@ msgstr ""
msgid "Cells store all inter-cell communication data, including user names and passwords, in the database. Because the cells data is not updated very frequently, use the <option>[cells]cells_config</option> option to specify a JSON file to store cells data. With this configuration, the database is no longer consulted when reloading the cells data. The file must have columns present in the Cell model (excluding common database fields and the <option>id</option> column). You must specify the queue connection information through a <option>transport_url</option> field, instead of <option>username</option>, <option>password</option>, and so on. The <option>transport_url</option> has the following form:"
msgstr ""
#: ./doc/config-reference/compute/section_compute-cells.xml:316(replaceable)
msgid "USERNAME"
msgstr ""
#: ./doc/config-reference/compute/section_compute-cells.xml:316(replaceable)
msgid "PASSWORD"
msgstr ""
#: ./doc/config-reference/compute/section_compute-cells.xml:316(replaceable)
msgid "HOSTNAME"
msgstr ""
@ -8161,6 +8320,30 @@ msgstr ""
msgid "The second command, <placeholder-1/>, may take a while."
msgstr ""
#: ./doc/config-reference/compute/section_xapi-resize-setup.xml:8(title)
msgid "Modify Dom0 for resize/migration support"
msgstr ""
#: ./doc/config-reference/compute/section_xapi-resize-setup.xml:9(para)
msgid "To resize servers with XenServer and XCP, you must:"
msgstr ""
#: ./doc/config-reference/compute/section_xapi-resize-setup.xml:12(para)
msgid "Establish a root trust between all hypervisor nodes of your deployment:"
msgstr ""
#: ./doc/config-reference/compute/section_xapi-resize-setup.xml:14(para)
msgid "To do so, generate an ssh key-pair with the <placeholder-1/> command. Ensure that each of your dom0's <filename>authorized_keys</filename> file (located in <filename>/root/.ssh/authorized_keys</filename>) contains the public key fingerprint (located in <filename>/root/.ssh/id_rsa.pub</filename>)."
msgstr ""
#: ./doc/config-reference/compute/section_xapi-resize-setup.xml:23(para)
msgid "Provide an <filename>/images</filename> mount point to the dom0 for your hypervisor:"
msgstr ""
#: ./doc/config-reference/compute/section_xapi-resize-setup.xml:25(para)
msgid "Dom0 space is at a premium so creating a directory in dom0 is potentially dangerous and likely to fail especially when you resize large servers. The least you can do is to symlink <filename>/images</filename> to your local storage SR. The following instructions work for an English-based installation of XenServer (and XCP) and in the case of ext3-based SR (with which the resize functionality is known to work correctly)."
msgstr ""
#. When image changes, this message will be marked fuzzy or untranslated for you.
#. It doesn't matter what you translate it to: it's not used at all.
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:42(None)
@ -8563,7 +8746,7 @@ msgstr ""
msgid "A <systemitem class=\"service\">nova-compute</systemitem> service can control one or more clusters containing multiple ESX hosts, making <systemitem class=\"service\">nova-compute</systemitem> a critical service from a high availability perspective. Because the host that runs <systemitem class=\"service\">nova-compute</systemitem> can fail while the vCenter and ESX still run, you must protect the <systemitem class=\"service\">nova-compute</systemitem> service against host failures."
msgstr ""
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:606(para) ./doc/config-reference/compute/section_hypervisor_vmware.xml:1038(para)
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:606(para)
msgid "Many <filename>nova.conf</filename> options are relevant to libvirt but do not apply to this driver."
msgstr ""
@ -8871,43 +9054,11 @@ msgstr ""
msgid "When using the VMwareVCDriver (vCenter) with OpenStack Compute with vSphere version 5.0 or earlier, <filename>nova.conf</filename> must include the following extra config option:"
msgstr ""
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:1010(title)
msgid "VMware ESX driver"
msgstr ""
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:1011(para)
msgid "This section covers details of using the VMwareESXDriver. The ESX Driver has not been extensively tested and is not recommended. To configure the VMware vCenter driver instead, see <xref linkend=\"VMwareVCDriver_details\"/>."
msgstr ""
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:1016(para)
msgid "The VMware ESX driver has been deprecated in the Icehouse release and will be removed with the Juno release."
msgstr ""
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:1021(title)
msgid "VMwareESXDriver configuration options"
msgstr ""
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:1022(para)
msgid "When you use the VMwareESXDriver (no vCenter) with OpenStack Compute, add the following VMware-specific configuration options to the <filename>nova.conf</filename> file:"
msgstr ""
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:1034(para)
msgid "Remember that you must have one <systemitem class=\"service\">nova-compute</systemitem> service for each ESXi host. It is recommended that this host run as a VM on the same ESXi host that it manages."
msgstr ""
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:1043(title)
msgid "Requirements and limitations"
msgstr ""
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:1044(para)
msgid "The ESXDriver cannot use many of the vSphere platform advanced capabilities, namely vMotion, high availability, and DRS."
msgstr ""
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:1050(title) ./doc/config-reference/compute/section_compute-scheduler.xml:817(title)
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:1010(title) ./doc/config-reference/compute/section_compute-scheduler.xml:817(title)
msgid "Configuration reference"
msgstr ""
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:1051(para)
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:1011(para)
msgid "To customize the VMware driver, use the configuration option settings documented in <xref linkend=\"config_table_nova_vmware\"/>."
msgstr ""
@ -9831,6 +9982,178 @@ msgstr ""
msgid "The <filename>rootwrap.conf</filename> file defines configuration values used by the rootwrap script when the Compute service needs to escalate its privileges to those of the root user."
msgstr ""
#: ./doc/config-reference/compute/section_xen-install.xml:7(title)
msgid "Install XenServer and XCP"
msgstr ""
#: ./doc/config-reference/compute/section_xen-install.xml:9(para)
msgid "Before you can run OpenStack with XCP or XenServer, you must install the software on <link href=\"http://docs.vmd.citrix.com/XenServer/6.0.0/1.0/en_gb/installation.html#sys_requirements\">an appropriate server</link>."
msgstr ""
#: ./doc/config-reference/compute/section_xen-install.xml:14(para)
msgid "Xen is a type 1 hypervisor: When your server starts, Xen is the first software that runs. Consequently, you must install XenServer or XCP before you install the operating system where you want to run OpenStack code. The OpenStack services then run in a virtual machine that you install on top of XenServer."
msgstr ""
#: ./doc/config-reference/compute/section_xen-install.xml:21(para)
msgid "Before you can install your system, decide whether to install a free or paid edition of Citrix XenServer or Xen Cloud Platform from Xen.org. Download the software from these locations:"
msgstr ""
#: ./doc/config-reference/compute/section_xen-install.xml:29(link)
msgid "http://www.citrix.com/XenServer/download"
msgstr ""
#: ./doc/config-reference/compute/section_xen-install.xml:34(link)
msgid "http://www.xen.org/download/xcp/index.html"
msgstr ""
#: ./doc/config-reference/compute/section_xen-install.xml:37(para)
msgid "When you install many servers, you might find it easier to perform <link href=\"http://docs.vmd.citrix.com/XenServer/6.0.0/1.0/en_gb/installation.html#pxe_boot_install\">PXE boot installations of XenServer or XCP</link>. You can also package any post-installation changes that you want to make to your XenServer by <link href=\"http://docs.vmd.citrix.com/XenServer/6.0.0/1.0/en_gb/supplemental_pack_ddk.html\">creating your own XenServer supplemental pack</link>."
msgstr ""
#: ./doc/config-reference/compute/section_xen-install.xml:47(para)
msgid "You can also install the <package>xcp-xenapi</package> package on Debian-based distributions to get XCP. However, this is not as mature or feature complete as above distributions. This modifies your boot loader to first boot Xen and boot your existing OS on top of Xen as Dom0. The xapi daemon runs in Dom0. Find more details at <link href=\"http://wiki.xen.org/wiki/Project_Kronos\">http://wiki.xen.org/wiki/Project_Kronos</link>."
msgstr ""
#: ./doc/config-reference/compute/section_xen-install.xml:56(para)
msgid "Make sure you use the EXT type of storage repository (SR). Features that require access to VHD files (such as copy on write, snapshot and migration) do not work when you use the LVM SR. Storage repository (SR) is a XenAPI-specific term relating to the physical storage where virtual disks are stored."
msgstr ""
#: ./doc/config-reference/compute/section_xen-install.xml:62(para)
msgid "On the XenServer/XCP installation screen, choose the <guilabel>XenDesktop Optimized</guilabel> option. If you use an answer file, make sure you use <literal>srtype=\"ext\"</literal> in the <option>installation</option> tag of the answer file."
msgstr ""
#: ./doc/config-reference/compute/section_xen-install.xml:70(title)
msgid "Post-installation steps"
msgstr ""
#: ./doc/config-reference/compute/section_xen-install.xml:71(para)
msgid "Complete these steps to install OpenStack in your XenServer system:"
msgstr ""
#: ./doc/config-reference/compute/section_xen-install.xml:75(para)
msgid "For resize and migrate functionality, complete the changes described in the <citetitle>Configure resize</citetitle> section in the <link href=\"http://docs.openstack.org/trunk/config-reference/content/\"><citetitle>OpenStack Configuration Reference</citetitle></link>."
msgstr ""
#: ./doc/config-reference/compute/section_xen-install.xml:83(para)
msgid "Install the VIF isolation rules to help prevent mac and IP address spoofing."
msgstr ""
#: ./doc/config-reference/compute/section_xen-install.xml:87(para)
msgid "Install the XenAPI plug-ins. See the following section."
msgstr ""
#: ./doc/config-reference/compute/section_xen-install.xml:91(para)
msgid "To support AMI type images, you must set up <literal>/boot/guest</literal> symlink/directory in Dom0. For detailed instructions, see next section."
msgstr ""
#: ./doc/config-reference/compute/section_xen-install.xml:97(para)
msgid "To support resize/migration, set up an ssh trust relation between your XenServer hosts, and ensure <literal>/images</literal> is properly set up. See next section for more details."
msgstr ""
#: ./doc/config-reference/compute/section_xen-install.xml:103(para)
msgid "Create a Paravirtualized virtual machine that can run the OpenStack compute code."
msgstr ""
#: ./doc/config-reference/compute/section_xen-install.xml:107(para)
msgid "Install and configure the <systemitem class=\"service\">nova-compute</systemitem> in the above virtual machine."
msgstr ""
#: ./doc/config-reference/compute/section_xen-install.xml:112(para)
msgid "For more information, see how DevStack performs the last three steps for developer deployments. For more information about DevStack, see <citetitle>Getting Started With XenServer and Devstack</citetitle> (<link href=\"https://github.com/openstack-dev/devstack/blob/master/tools/xen/README.md\">https://github.com/openstack-dev/devstack/blob/master/tools/xen/README.md</link>). Find more information about the first step, see <citetitle>Multi Tenancy Networking Protections in XenServer</citetitle> (<link href=\"https://github.com/openstack/nova/blob/master/plugins/xenserver/doc/networking.rst\">https://github.com/openstack/nova/blob/master/plugins/xenserver/doc/networking.rst</link>). For information about how to install the XenAPI plug-ins, see <citetitle>XenAPI README</citetitle> (<link href=\"https://github.com/openstack/nova/blob/master/plugins/xenserver/xenapi/README\">https://github.com/openstack/nova/blob/master/plugins/xenserver/xenapi/README</link>)."
msgstr ""
#: ./doc/config-reference/compute/section_xen-install.xml:132(title)
msgid "Xen boot from ISO"
msgstr ""
#: ./doc/config-reference/compute/section_xen-install.xml:133(para)
msgid "XenServer, through the XenAPI integration with OpenStack, provides a feature to boot instances from an ISO file. To activate the Boot From ISO feature, you must configure the SR elements on XenServer host, as follows:"
msgstr ""
#: ./doc/config-reference/compute/section_xen-install.xml:140(para)
msgid "Create an ISO-typed SR, such as an NFS ISO library, for instance. For this, using XenCenter is a simple method. You must export an NFS volume from a remote NFS server. Make sure it is exported in read-write mode."
msgstr ""
#: ./doc/config-reference/compute/section_xen-install.xml:147(para)
msgid "On the compute host, find and record the uuid of this ISO SR:"
msgstr ""
#: ./doc/config-reference/compute/section_xen-install.xml:152(para)
msgid "Locate the uuid of the NFS ISO library:"
msgstr ""
#: ./doc/config-reference/compute/section_xen-install.xml:156(para)
msgid "Set the uuid and configuration. Even if an NFS mount point is not local, you must specify <literal>local-storage-iso</literal>."
msgstr ""
#: ./doc/config-reference/compute/section_xen-install.xml:162(para)
msgid "Make sure the host-uuid from <literal>xe pbd-list</literal> equals the uuid of the host you found previously:"
msgstr ""
#: ./doc/config-reference/compute/section_xen-install.xml:168(para)
msgid "You can now add images through the OpenStack Image Service with <literal>disk-format=iso</literal>, and boot them in OpenStack Compute:"
msgstr ""
#: ./doc/config-reference/compute/section_xapi-install-plugins.xml:8(title)
msgid "Install the XenAPI plug-ins"
msgstr ""
#: ./doc/config-reference/compute/section_xapi-install-plugins.xml:9(para)
msgid "When you use Xen as the hypervisor for OpenStack Compute, you can install a Python script (or any executable) on the host side, and call that through the XenAPI. These scripts are called plug-ins. The XenAPI plug-ins live in the nova code repository. These plug-ins have to be copied to the Dom0 for the hypervisor, to the appropriate directory, where xapi can find them. There are several options for the installation. The important thing is to ensure that the version of the plug-ins are in line with the nova installation by only installing plug-ins from a matching nova repository."
msgstr ""
#: ./doc/config-reference/compute/section_xapi-install-plugins.xml:20(title)
msgid "Manually install the plug-in"
msgstr ""
#: ./doc/config-reference/compute/section_xapi-install-plugins.xml:23(para)
msgid "Create temporary files/directories:"
msgstr ""
#: ./doc/config-reference/compute/section_xapi-install-plugins.xml:28(para)
msgid "Get the source from github. The example assumes the master branch is used. Amend the URL to match the version being used:"
msgstr ""
#: ./doc/config-reference/compute/section_xapi-install-plugins.xml:33(para)
msgid "(Alternatively) To use the official Ubuntu packages, use the following commands to get the nova code base:"
msgstr ""
#: ./doc/config-reference/compute/section_xapi-install-plugins.xml:40(para)
msgid "Copy the plug-ins to the hypervisor:"
msgstr ""
#: ./doc/config-reference/compute/section_xapi-install-plugins.xml:45(para)
msgid "Remove the temporary files/directories:"
msgstr ""
#: ./doc/config-reference/compute/section_xapi-install-plugins.xml:52(title)
msgid "Package a XenServer supplemental pack"
msgstr ""
#: ./doc/config-reference/compute/section_xapi-install-plugins.xml:53(para)
msgid "Follow these steps to produce a supplemental pack from the nova sources, and package it as a XenServer supplemental pack."
msgstr ""
#: ./doc/config-reference/compute/section_xapi-install-plugins.xml:58(para)
msgid "Create RPM packages. Given you have the nova sources. Use one of the methods in <xref linkend=\"manual_install\"/>:"
msgstr ""
#: ./doc/config-reference/compute/section_xapi-install-plugins.xml:63(para)
msgid "These commands leave an <filename>.rpm</filename> file in the <filename>rpmbuild/RPMS/noarch/</filename> directory."
msgstr ""
#: ./doc/config-reference/compute/section_xapi-install-plugins.xml:69(para)
msgid "Pack the RPM packages to a Supplemental Pack, using the XenServer DDK (the following command should be issued on the XenServer DDK virtual appliance, after the produced rpm file has been copied over):"
msgstr ""
#: ./doc/config-reference/compute/section_xapi-install-plugins.xml:82(para)
msgid "This command produces an <filename>.iso</filename> file in the output directory specified. Copy that file to the hypervisor."
msgstr ""
#: ./doc/config-reference/compute/section_xapi-install-plugins.xml:88(para)
msgid "Install the Supplemental Pack. Log in to the hypervisor, and issue:"
msgstr ""
#: ./doc/config-reference/compute/section_compute-hypervisors.xml:6(title)
msgid "Hypervisors"
msgstr ""

4486
doc/glossary/locale/de.po
View File

File diff suppressed because it is too large Load Diff

3328
doc/glossary/locale/glossary.pot
View File

File diff suppressed because it is too large Load Diff

4490
doc/glossary/locale/ja.po
View File

File diff suppressed because it is too large Load Diff

4486
doc/glossary/locale/ko_KR.po
View File

File diff suppressed because it is too large Load Diff

8
doc/high-availability-guide/locale/ja.po
View File

@ -4,9 +4,9 @@
msgid ""
msgstr ""
"Project-Id-Version: OpenStack Manuals\n"
"POT-Creation-Date: 2014-08-06 13:08+0000\n"
"PO-Revision-Date: 2014-08-06 06:12+0000\n"
"Last-Translator: openstackjenkins <jenkins@openstack.org>\n"
"POT-Creation-Date: 2014-08-15 05:33+0000\n"
"PO-Revision-Date: 2014-08-11 17:49+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"
@ -644,7 +644,7 @@ msgid ""
"href=\"http://www.percona.com/\">http://www.percona.com/</link>) also work "
"with Galera. You also have the option to use PostgreSQL, which has its own "
"replication, or another database HA option."
msgstr ""
msgstr "MySQL/Galera は、データベースを高可用化する唯一の方法ではありません。MariaDB (<link href=\"https://mariadb.org/\">https://mariadb.org/</link>) や Percona (<link href=\"http://www.percona.com/\">http://www.percona.com/</link>) も Galera と一緒に動作します。PostgreSQL を使用することもできます。独自のレプリケーション機能や他のデータベース高可用化の方法があります。"
#: ./doc/high-availability-guide/ha_aa_network/section_run_neutron_l3_agent.xml7(title)
msgid "Run neutron L3 agent"

3210
doc/image-guide/locale/fr.po Normal file
View File

File diff suppressed because it is too large Load Diff

224
doc/image-guide/locale/image-guide.pot
View File

@ -1,7 +1,7 @@
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"POT-Creation-Date: 2014-08-06 06:09+0000\n"
"POT-Creation-Date: 2014-08-15 06:09+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"
@ -30,7 +30,7 @@ msgid "Sysprep"
msgstr ""
#: ./doc/image-guide/section_windows-example.xml:20(para)
msgid "Microsoft has a special tool called <link href=\"http://technet.microsoft.com/en-us/library/cc766049(v=ws.10).aspx\">Sysprep</link> that must be run inside of a Windows guest to prepare it for use as a virtual machine image. On Windows 2012 server, invoke sysprep, as follows: <placeholder-1/>"
msgid "Microsoft has a special tool called <link href=\"http://technet.microsoft.com/en-us/library/cc766049(v=ws.10).aspx\">Sysprep</link> that must be run inside of a Windows guest to prepare it for use as a virtual machine image. On Windows, invoke sysprep, as follows: <placeholder-1/>"
msgstr ""
#: ./doc/image-guide/section_windows-example.xml:27(title)
@ -817,31 +817,31 @@ msgstr ""
#. When image changes, this message will be marked fuzzy or untranslated for you.
#. It doesn't matter what you translate it to: it's not used at all.
#: ./doc/image-guide/section_centos-example.xml:62(None) ./doc/image-guide/section_centos-example.xml:65(None)
#: ./doc/image-guide/section_centos-example.xml:71(None) ./doc/image-guide/section_centos-example.xml:74(None)
msgid "@@image: 'figures/centos-install.png'; md5=013b5be9e167ee27e674859ba4869d89"
msgstr ""
#. When image changes, this message will be marked fuzzy or untranslated for you.
#. It doesn't matter what you translate it to: it's not used at all.
#: ./doc/image-guide/section_centos-example.xml:75(None)
#: ./doc/image-guide/section_centos-example.xml:84(None)
msgid "@@image: 'figures/centos-tcpip.png'; md5=fe0324d0d74368d1920c243fd72747fd"
msgstr ""
#. When image changes, this message will be marked fuzzy or untranslated for you.
#. It doesn't matter what you translate it to: it's not used at all.
#: ./doc/image-guide/section_centos-example.xml:84(None)
#: ./doc/image-guide/section_centos-example.xml:93(None)
msgid "@@image: 'figures/install-method.png'; md5=1d60286d52f6b385a5d15ae042858893"
msgstr ""
#. When image changes, this message will be marked fuzzy or untranslated for you.
#. It doesn't matter what you translate it to: it's not used at all.
#: ./doc/image-guide/section_centos-example.xml:97(None)
#: ./doc/image-guide/section_centos-example.xml:106(None)
msgid "@@image: 'figures/url-setup.png'; md5=b2f3b4a3552ad175575f5eb78e63dfd8"
msgstr ""
#. When image changes, this message will be marked fuzzy or untranslated for you.
#. It doesn't matter what you translate it to: it's not used at all.
#: ./doc/image-guide/section_centos-example.xml:148(None)
#: ./doc/image-guide/section_centos-example.xml:157(None)
msgid "@@image: 'figures/centos-complete.png'; md5=1b2c6a2e45a9ae52a5f6338ae74b1e54"
msgstr ""
@ -890,238 +890,246 @@ msgid "Start the installation process using either <placeholder-1/> or <placehol
msgstr ""
#: ./doc/image-guide/section_centos-example.xml:42(para)
msgid "Assume that the name of your virtual machine image is <literal>centos-6.4</literal>; you need this name when you use <placeholder-1/> commands to manipulate the state of the image."
msgid "Assume that:"
msgstr ""
#: ./doc/image-guide/section_centos-example.xml:45(para)
msgid "The name of your virtual machine image is <literal>centos-6.4</literal>; you need this name when you use <placeholder-1/> commands to manipulate the state of the image."
msgstr ""
#: ./doc/image-guide/section_centos-example.xml:50(para)
msgid "You saved the netinstall ISO image to the <filename>/data/isos</filename> directory."
msgstr ""
#: ./doc/image-guide/section_centos-example.xml:53(para)
msgid "If you use <placeholder-1/>, the commands should look something like this:"
msgstr ""
#: ./doc/image-guide/section_centos-example.xml:56(title) ./doc/image-guide/section_centos-example.xml:137(title)
#: ./doc/image-guide/section_centos-example.xml:65(title) ./doc/image-guide/section_centos-example.xml:146(title)
msgid "Step through the installation"
msgstr ""
#: ./doc/image-guide/section_centos-example.xml:57(para)
#: ./doc/image-guide/section_centos-example.xml:66(para)
msgid "At the initial Installer boot menu, choose the <guilabel>Install or upgrade an existing system</guilabel> option. Step through the installation prompts. Accept the defaults."
msgstr ""
#: ./doc/image-guide/section_centos-example.xml:70(title)
#: ./doc/image-guide/section_centos-example.xml:79(title)
msgid "Configure TCP/IP"
msgstr ""
#: ./doc/image-guide/section_centos-example.xml:71(para)
#: ./doc/image-guide/section_centos-example.xml:80(para)
msgid "The default TCP/IP settings are fine. In particular, ensure that Enable IPv4 support is enabled with DHCP, which is the default."
msgstr ""
#: ./doc/image-guide/section_centos-example.xml:80(title)
#: ./doc/image-guide/section_centos-example.xml:89(title)
msgid "Point the installer to a CentOS web server"
msgstr ""
#: ./doc/image-guide/section_centos-example.xml:81(para)
#: ./doc/image-guide/section_centos-example.xml:90(para)
msgid "Choose URL as the installation method."
msgstr ""
#: ./doc/image-guide/section_centos-example.xml:87(para)
#: ./doc/image-guide/section_centos-example.xml:96(para)
msgid "Depending on the version of CentOS, the net installer requires that the user specify either a URL or the web site and a CentOS directory that corresponds to one of the CentOS mirrors. If the installer asks for a single URL, a valid URL might be <literal>http://mirror.umd.edu/centos/6/os/x86_64</literal>."
msgstr ""
#: ./doc/image-guide/section_centos-example.xml:92(para)
#: ./doc/image-guide/section_centos-example.xml:101(para)
msgid "Consider using other mirrors as an alternative to <literal>mirror.umd.edu</literal>."
msgstr ""
#: ./doc/image-guide/section_centos-example.xml:100(para)
#: ./doc/image-guide/section_centos-example.xml:109(para)
msgid "If the installer asks for web site name and CentOS directory separately, you might enter:"
msgstr ""
#: ./doc/image-guide/section_centos-example.xml:104(para)
#: ./doc/image-guide/section_centos-example.xml:113(para)
msgid "Web site name: <literal>mirror.umd.edu</literal>"
msgstr ""
#: ./doc/image-guide/section_centos-example.xml:107(para)
#: ./doc/image-guide/section_centos-example.xml:116(para)
msgid "CentOS directory: <literal>centos/6/os/x86_64</literal>"
msgstr ""
#: ./doc/image-guide/section_centos-example.xml:110(para)
#: ./doc/image-guide/section_centos-example.xml:119(para)
msgid "See <link href=\"http://www.centos.org/download/mirrors/\">CentOS mirror page</link> to get a full list of mirrors, click on the \"HTTP\" link of a mirror to retrieve the web site name of a mirror."
msgstr ""
#: ./doc/image-guide/section_centos-example.xml:115(title)
#: ./doc/image-guide/section_centos-example.xml:124(title)
msgid "Storage devices"
msgstr ""
#: ./doc/image-guide/section_centos-example.xml:116(para)
#: ./doc/image-guide/section_centos-example.xml:125(para)
msgid "If prompted about which type of devices your installation uses, choose <guilabel>Basic Storage Devices</guilabel>."
msgstr ""
#: ./doc/image-guide/section_centos-example.xml:120(title) ./doc/image-guide/section_ubuntu-example.xml:44(title)
#: ./doc/image-guide/section_centos-example.xml:129(title) ./doc/image-guide/section_ubuntu-example.xml:47(title)
msgid "Hostname"
msgstr ""
#: ./doc/image-guide/section_centos-example.xml:121(para)
#: ./doc/image-guide/section_centos-example.xml:130(para)
msgid "The installer may ask you to choose a host name. The default (<literal>localhost.localdomain</literal>) is fine. You install the <systemitem class=\"service\">cloud-init</systemitem> package later, which sets the host name on boot when a new instance is provisioned using this image."
msgstr ""
#: ./doc/image-guide/section_centos-example.xml:127(title) ./doc/image-guide/section_ubuntu-example.xml:61(title)
#: ./doc/image-guide/section_centos-example.xml:136(title) ./doc/image-guide/section_ubuntu-example.xml:64(title)
msgid "Partition the disks"
msgstr ""
#: ./doc/image-guide/section_centos-example.xml:128(para)
#: ./doc/image-guide/section_centos-example.xml:137(para)
msgid "There are different options for partitioning the disks. The default installation uses LVM partitions, and creates three partitions (<filename>/boot</filename>, <filename>/</filename>, swap), which works fine. Alternatively, you might want to create a single ext4 partition that is mounted to \"<literal>/</literal>\", which also works fine."
msgstr ""
#: ./doc/image-guide/section_centos-example.xml:133(para)
#: ./doc/image-guide/section_centos-example.xml:142(para)
msgid "If unsure, use the default partition scheme for the installer because no scheme is better than another."
msgstr ""
#: ./doc/image-guide/section_centos-example.xml:138(para)
#: ./doc/image-guide/section_centos-example.xml:147(para)
msgid "Step through the installation, using the default options. The simplest thing to do is to choose the \"Basic Server\" install (may be called \"Server\" install on older versions of CentOS), which installs an SSH server."
msgstr ""
#: ./doc/image-guide/section_centos-example.xml:143(title) ./doc/image-guide/section_ubuntu-example.xml:98(title)
#: ./doc/image-guide/section_centos-example.xml:152(title) ./doc/image-guide/section_ubuntu-example.xml:101(title)
msgid "Detach the CD-ROM and reboot"
msgstr ""
#: ./doc/image-guide/section_centos-example.xml:144(para)
#: ./doc/image-guide/section_centos-example.xml:153(para)
msgid "After the install completes, the <guilabel>Congratulations, your CentOS installation is complete</guilabel> screen appears."
msgstr ""
#: ./doc/image-guide/section_centos-example.xml:154(replaceable) ./doc/image-guide/section_centos-example.xml:313(replaceable) ./doc/image-guide/section_ubuntu-example.xml:114(replaceable) ./doc/image-guide/section_ubuntu-example.xml:193(replaceable)
#: ./doc/image-guide/section_centos-example.xml:163(replaceable) ./doc/image-guide/section_centos-example.xml:322(replaceable) ./doc/image-guide/section_ubuntu-example.xml:117(replaceable) ./doc/image-guide/section_ubuntu-example.xml:196(replaceable)
msgid "vm-image"
msgstr ""
#: ./doc/image-guide/section_centos-example.xml:151(para)
#: ./doc/image-guide/section_centos-example.xml:160(para)
msgid "To eject a disk by using the <placeholder-1/> command, libvirt requires that you attach an empty disk at the same target that the CDROM was previously attached, which should be <literal>hdc</literal>. You can confirm the appropriate target using the <placeholder-2/> command."
msgstr ""
#: ./doc/image-guide/section_centos-example.xml:168(para)
#: ./doc/image-guide/section_centos-example.xml:177(para)
msgid "Run the following commands from the host to eject the disk and reboot using virsh, as root. If you are using virt-manager, the commands below will work, but you can also use the GUI to detach and reboot it by manually stopping and starting."
msgstr ""
#: ./doc/image-guide/section_centos-example.xml:176(title) ./doc/image-guide/section_ubuntu-example.xml:143(title)
#: ./doc/image-guide/section_centos-example.xml:185(title) ./doc/image-guide/section_ubuntu-example.xml:146(title)
msgid "Log in to newly created image"
msgstr ""
#: ./doc/image-guide/section_centos-example.xml:177(para)
#: ./doc/image-guide/section_centos-example.xml:186(para)
msgid "When you boot for the first time after installation, you might be prompted about authentication tools. Select <guilabel>Exit</guilabel>. Then, log in as root."
msgstr ""
#: ./doc/image-guide/section_centos-example.xml:181(title)
#: ./doc/image-guide/section_centos-example.xml:190(title)
msgid "Install the ACPI service"
msgstr ""
#: ./doc/image-guide/section_centos-example.xml:182(para)
#: ./doc/image-guide/section_centos-example.xml:191(para)
msgid "To enable the hypervisor to reboot or shutdown an instance, you must install and run the <systemitem class=\"service\">acpid</systemitem> service on the guest system."
msgstr ""
#: ./doc/image-guide/section_centos-example.xml:186(para)
#: ./doc/image-guide/section_centos-example.xml:195(para)
msgid "Run the following commands inside the CentOS guest to install the ACPI service and configure it to start when the system boots:"
msgstr ""
#: ./doc/image-guide/section_centos-example.xml:193(title)
#: ./doc/image-guide/section_centos-example.xml:202(title)
msgid "Configure to fetch metadata"
msgstr ""
#: ./doc/image-guide/section_centos-example.xml:194(para)
#: ./doc/image-guide/section_centos-example.xml:203(para)
msgid "An instance must interact with the metadata service to perform several tasks on start up. For example, the instance must get the ssh public key and run the user data script. To ensure that the instance performs these tasks, use one of these methods:"
msgstr ""
#: ./doc/image-guide/section_centos-example.xml:199(para)
#: ./doc/image-guide/section_centos-example.xml:208(para)
msgid "Install a <systemitem class=\"service\">cloud-init</systemitem> RPM, which is a port of the Ubuntu <link href=\"https://launchpad.net/cloud-init\">cloud-init</link> package. This is the recommended approach."
msgstr ""
#: ./doc/image-guide/section_centos-example.xml:204(para)
#: ./doc/image-guide/section_centos-example.xml:213(para)
msgid "Modify <filename>/etc/rc.local</filename> to fetch desired information from the metadata service, as described in the next section."
msgstr ""
#: ./doc/image-guide/section_centos-example.xml:210(title)
#: ./doc/image-guide/section_centos-example.xml:219(title)
msgid "Use cloud-init to fetch the public key"
msgstr ""
#: ./doc/image-guide/section_centos-example.xml:211(para)
#: ./doc/image-guide/section_centos-example.xml:220(para)
msgid "The <systemitem class=\"service\">cloud-init</systemitem> package automatically fetches the public key from the metadata server and places the key in an account. You can install <systemitem class=\"service\">cloud-init</systemitem> inside the CentOS guest by adding the EPEL repo:"
msgstr ""
#: ./doc/image-guide/section_centos-example.xml:217(para)
#: ./doc/image-guide/section_centos-example.xml:226(para)
msgid "The account varies by distribution. On Ubuntu-based virtual machines, the account is called <literal>ubuntu</literal>. On Fedora-based virtual machines, the account is called <literal>ec2-user</literal>."
msgstr ""
#: ./doc/image-guide/section_centos-example.xml:220(para)
#: ./doc/image-guide/section_centos-example.xml:229(para)
msgid "You can change the name of the account used by <systemitem class=\"service\">cloud-init</systemitem> by editing the <filename>/etc/cloud/cloud.cfg</filename> file and adding a line with a different user. For example, to configure <systemitem class=\"service\">cloud-init</systemitem> to put the key in an account named <literal>admin</literal>, add this line to the configuration file:"
msgstr ""
#: ./doc/image-guide/section_centos-example.xml:228(title)
#: ./doc/image-guide/section_centos-example.xml:237(title)
msgid "Write a script to fetch the public key (if no cloud-init)"
msgstr ""
#: ./doc/image-guide/section_centos-example.xml:229(para)
#: ./doc/image-guide/section_centos-example.xml:238(para)
msgid "If you are not able to install the <systemitem class=\"service\">cloud-init</systemitem> package in your image, to fetch the ssh public key and add it to the root account, edit the <filename>/etc/rc.local</filename> file and add the following lines before the line <literal>touch /var/lock/subsys/local</literal>:"
msgstr ""
#: ./doc/image-guide/section_centos-example.xml:257(para)
#: ./doc/image-guide/section_centos-example.xml:266(para)
msgid "Some VNC clients replace the colon (<literal>:</literal>) with a semicolon (<literal>;</literal>) and the underscore (<literal>_</literal>) with a hyphen (<literal>-</literal>). Make sure to specify <literal>http:</literal> and not <literal>http;</literal>. Make sure to specify <literal>authorized_keys</literal> and not <literal>authorized-keys</literal>."
msgstr ""
#: ./doc/image-guide/section_centos-example.xml:265(para)
#: ./doc/image-guide/section_centos-example.xml:274(para)
msgid "The previous script only gets the ssh public key from the metadata server. It does not get user data, which is optional data that can be passed by the user when requesting a new instance. User data is often used to run a custom script when an instance boots."
msgstr ""
#: ./doc/image-guide/section_centos-example.xml:269(para)
#: ./doc/image-guide/section_centos-example.xml:278(para)
msgid "As the OpenStack metadata service is compatible with version 2009-04-04 of the Amazon EC2 metadata service, consult the Amazon EC2 documentation on <link href=\"http://docs.amazonwebservices.com/AWSEC2/2009-04-04/UserGuide/AESDG-chapter-instancedata.html\">Using Instance Metadata</link> for details on how to get user data."
msgstr ""
#: ./doc/image-guide/section_centos-example.xml:276(title)
#: ./doc/image-guide/section_centos-example.xml:285(title)
msgid "Disable the zeroconf route"
msgstr ""
#: ./doc/image-guide/section_centos-example.xml:277(para)
#: ./doc/image-guide/section_centos-example.xml:286(para)
msgid "For the instance to access the metadata service, you must disable the default zeroconf route:"
msgstr ""
#: ./doc/image-guide/section_centos-example.xml:282(title)
#: ./doc/image-guide/section_centos-example.xml:291(title)
msgid "Configure console"
msgstr ""
#: ./doc/image-guide/section_centos-example.xml:283(para)
#: ./doc/image-guide/section_centos-example.xml:292(para)
msgid "For the <placeholder-1/> command to work properly on CentOS 6.<replaceable>x</replaceable>, you might need to add the following lines to the <filename>/boot/grub/menu.lst</filename> file:"
msgstr ""
#: ./doc/image-guide/section_centos-example.xml:289(replaceable)
#: ./doc/image-guide/section_centos-example.xml:298(replaceable)
msgid "..."
msgstr ""
#: ./doc/image-guide/section_centos-example.xml:292(title) ./doc/image-guide/section_ubuntu-example.xml:173(title)
#: ./doc/image-guide/section_centos-example.xml:301(title) ./doc/image-guide/section_ubuntu-example.xml:176(title)
msgid "Shut down the instance"
msgstr ""
#: ./doc/image-guide/section_centos-example.xml:293(para) ./doc/image-guide/section_ubuntu-example.xml:174(para)
#: ./doc/image-guide/section_centos-example.xml:302(para) ./doc/image-guide/section_ubuntu-example.xml:177(para)
msgid "From inside the instance, as root:"
msgstr ""
#: ./doc/image-guide/section_centos-example.xml:297(title) ./doc/image-guide/section_ubuntu-example.xml:178(title)
#: ./doc/image-guide/section_centos-example.xml:306(title) ./doc/image-guide/section_ubuntu-example.xml:181(title)
msgid "Clean up (remove MAC address details)"
msgstr ""
#: ./doc/image-guide/section_centos-example.xml:298(para)
#: ./doc/image-guide/section_centos-example.xml:307(para)
msgid "The operating system records the MAC address of the virtual ethernet card in locations such as <filename>/etc/sysconfig/network-scripts/ifcfg-eth0</filename> and <filename>/etc/udev/rules.d/70-persistent-net.rules</filename> during the instance process. However, each time the image boots up, the virtual ethernet card will have a different MAC address, so this information must be deleted from the configuration file."
msgstr ""
#: ./doc/image-guide/section_centos-example.xml:304(para) ./doc/image-guide/section_ubuntu-example.xml:184(para)
#: ./doc/image-guide/section_centos-example.xml:313(para) ./doc/image-guide/section_ubuntu-example.xml:187(para)
msgid "There is a utility called <placeholder-1/>, that performs various cleanup tasks such as removing the MAC address references. It will clean up a virtual machine image in place:"
msgstr ""
#: ./doc/image-guide/section_centos-example.xml:310(title) ./doc/image-guide/section_ubuntu-example.xml:190(title)
#: ./doc/image-guide/section_centos-example.xml:319(title) ./doc/image-guide/section_ubuntu-example.xml:193(title)
msgid "Undefine the libvirt domain"
msgstr ""
#: ./doc/image-guide/section_centos-example.xml:311(para)
#: ./doc/image-guide/section_centos-example.xml:320(para)
msgid "Now that you can upload the image to the Image Service, you no longer need to have this virtual machine image managed by libvirt. Use the <placeholder-1/> command to inform libvirt:"
msgstr ""
#: ./doc/image-guide/section_centos-example.xml:317(title) ./doc/image-guide/section_ubuntu-example.xml:197(title)
#: ./doc/image-guide/section_centos-example.xml:326(title) ./doc/image-guide/section_ubuntu-example.xml:200(title)
msgid "Image is complete"
msgstr ""
#: ./doc/image-guide/section_centos-example.xml:318(para)
#: ./doc/image-guide/section_centos-example.xml:327(para)
msgid "The underlying image file that you created with <placeholder-1/> is ready to be uploaded. For example, you can upload the <filename>/tmp/centos-6.4.qcow2</filename> image to the Image Service."
msgstr ""
@ -1415,177 +1423,177 @@ msgstr ""
#. When image changes, this message will be marked fuzzy or untranslated for you.
#. It doesn't matter what you translate it to: it's not used at all.
#: ./doc/image-guide/section_ubuntu-example.xml:39(None)
#: ./doc/image-guide/section_ubuntu-example.xml:42(None)
msgid "@@image: 'figures/ubuntu-install.png'; md5=a1f2ab707b7bc3122e20e6e0e4580887"
msgstr ""
#. When image changes, this message will be marked fuzzy or untranslated for you.
#. It doesn't matter what you translate it to: it's not used at all.
#: ./doc/image-guide/section_ubuntu-example.xml:83(None)
#: ./doc/image-guide/section_ubuntu-example.xml:86(None)
msgid "@@image: 'figures/ubuntu-software-selection.png'; md5=423be828f701345f7d20551a39f24271"
msgstr ""
#. When image changes, this message will be marked fuzzy or untranslated for you.
#. It doesn't matter what you translate it to: it's not used at all.
#: ./doc/image-guide/section_ubuntu-example.xml:93(None)
#: ./doc/image-guide/section_ubuntu-example.xml:96(None)
msgid "@@image: 'figures/ubuntu-grub.png'; md5=e46a46bd4044483da7cd07de2ff1ddbc"
msgstr ""
#. When image changes, this message will be marked fuzzy or untranslated for you.
#. It doesn't matter what you translate it to: it's not used at all.
#: ./doc/image-guide/section_ubuntu-example.xml:104(None)
#: ./doc/image-guide/section_ubuntu-example.xml:107(None)
msgid "@@image: 'figures/ubuntu-finished.png'; md5=750be1d6a71b4186be563c049043e3a4"
msgstr ""
#: ./doc/image-guide/section_ubuntu-example.xml:4(title)
#: ./doc/image-guide/section_ubuntu-example.xml:7(title)
msgid "Example: Ubuntu image"
msgstr ""
#: ./doc/image-guide/section_ubuntu-example.xml:5(para)
#: ./doc/image-guide/section_ubuntu-example.xml:8(para)
msgid "This example installs a Ubuntu 14.04 (Trusty Tahr) image. To create an image for a different version of Ubuntu, follow these steps with the noted differences."
msgstr ""
#: ./doc/image-guide/section_ubuntu-example.xml:8(title)
#: ./doc/image-guide/section_ubuntu-example.xml:11(title)
msgid "Download an Ubuntu install ISO"
msgstr ""
#: ./doc/image-guide/section_ubuntu-example.xml:9(para)
#: ./doc/image-guide/section_ubuntu-example.xml:12(para)
msgid "Because the goal is to make the smallest possible base image, this example uses the network installation ISO. The Ubuntu 64-bit 14.04 network installer ISO is at <link href=\"http://archive.ubuntu.com/ubuntu/dists/trusty/main/installer-amd64/current/images/netboot/mini.iso\">http://archive.ubuntu.com/ubuntu/dists/trusty/main/installer-amd64/current/images/netboot/mini.iso</link>."
msgstr ""
#: ./doc/image-guide/section_ubuntu-example.xml:15(title)
#: ./doc/image-guide/section_ubuntu-example.xml:18(title)
msgid "Start the install process"
msgstr ""
#: ./doc/image-guide/section_ubuntu-example.xml:16(para)
#: ./doc/image-guide/section_ubuntu-example.xml:19(para)
msgid "Start the installation process by using either <placeholder-1/> or <placeholder-2/> as described in the previous section. If you use <placeholder-3/>, do not forget to connect your VNC client to the virtual machine."
msgstr ""
#: ./doc/image-guide/section_ubuntu-example.xml:20(para)
#: ./doc/image-guide/section_ubuntu-example.xml:23(para)
msgid "Assume that the name of your virtual machine image is <literal>ubuntu-14.04</literal>, which you need to know when you use <placeholder-1/> commands to manipulate the state of the image."
msgstr ""
#: ./doc/image-guide/section_ubuntu-example.xml:23(para)
#: ./doc/image-guide/section_ubuntu-example.xml:26(para)
msgid "If you are using <placeholder-1/>, the commands should look something like this:"
msgstr ""
#: ./doc/image-guide/section_ubuntu-example.xml:34(title) ./doc/image-guide/section_ubuntu-example.xml:56(title)
#: ./doc/image-guide/section_ubuntu-example.xml:37(title) ./doc/image-guide/section_ubuntu-example.xml:59(title)
msgid "Step through the install"
msgstr ""
#: ./doc/image-guide/section_ubuntu-example.xml:35(para)
#: ./doc/image-guide/section_ubuntu-example.xml:38(para)
msgid "At the initial Installer boot menu, choose the <guilabel>Install</guilabel> option. Step through the install prompts, the defaults should be fine."
msgstr ""
#: ./doc/image-guide/section_ubuntu-example.xml:45(para)
#: ./doc/image-guide/section_ubuntu-example.xml:48(para)
msgid "The installer may ask you to choose a hostname. The default (<literal>ubuntu</literal>) is fine. We will install the cloud-init package later, which will set the hostname on boot when a new instance is provisioned using this image."
msgstr ""
#: ./doc/image-guide/section_ubuntu-example.xml:52(title)
#: ./doc/image-guide/section_ubuntu-example.xml:55(title)
msgid "Select a mirror"
msgstr ""
#: ./doc/image-guide/section_ubuntu-example.xml:53(para)
#: ./doc/image-guide/section_ubuntu-example.xml:56(para)
msgid "The default mirror proposed by the installer should be fine."
msgstr ""
#: ./doc/image-guide/section_ubuntu-example.xml:57(para)
#: ./doc/image-guide/section_ubuntu-example.xml:60(para)
msgid "Step through the install, using the default options. When prompted for a user name, the default (<systemitem class=\"username\">ubuntu</systemitem>) is fine."
msgstr ""
#: ./doc/image-guide/section_ubuntu-example.xml:62(para)
#: ./doc/image-guide/section_ubuntu-example.xml:65(para)
msgid "There are different options for partitioning the disks. The default installation will use LVM partitions, and will create three partitions (<filename>/boot</filename>, <filename>/</filename>, swap), and this will work fine. Alternatively, you may wish to create a single ext4 partition, mounted to \"<literal>/</literal>\", should also work fine."
msgstr ""
#: ./doc/image-guide/section_ubuntu-example.xml:67(para)
#: ./doc/image-guide/section_ubuntu-example.xml:70(para)
msgid "If unsure, we recommend you use the installer's default partition scheme, since there is no clear advantage to one scheme or another."
msgstr ""
#: ./doc/image-guide/section_ubuntu-example.xml:71(title)
#: ./doc/image-guide/section_ubuntu-example.xml:74(title)
msgid "Automatic updates"
msgstr ""
#: ./doc/image-guide/section_ubuntu-example.xml:72(para)
msgid "The Ubuntu installer will ask how you want to manage upgrades on your system. This option depends on your specific use case. If your virtual machine instances will be connected to the internet, we recommend \"Install security updates automatically\"."
#: ./doc/image-guide/section_ubuntu-example.xml:75(para)
msgid "The Ubuntu installer will ask how you want to manage upgrades on your system. This option depends on your specific use case. If your virtual machine instances will be connected to the Internet, we recommend \"Install security updates automatically\"."
msgstr ""
#: ./doc/image-guide/section_ubuntu-example.xml:77(title)
#: ./doc/image-guide/section_ubuntu-example.xml:80(title)
msgid "Software selection: OpenSSH server"
msgstr ""
#: ./doc/image-guide/section_ubuntu-example.xml:78(para)
#: ./doc/image-guide/section_ubuntu-example.xml:81(para)
msgid "Choose \"OpenSSH server\"so that you will be able to SSH into the virtual machine when it launches inside of an OpenStack cloud."
msgstr ""
#: ./doc/image-guide/section_ubuntu-example.xml:88(title)
#: ./doc/image-guide/section_ubuntu-example.xml:91(title)
msgid "Install GRUB boot loader"
msgstr ""
#: ./doc/image-guide/section_ubuntu-example.xml:89(para)
#: ./doc/image-guide/section_ubuntu-example.xml:92(para)
msgid "Select \"Yes\" when asked about installing the GRUB boot loader to the master boot record."
msgstr ""
#: ./doc/image-guide/section_ubuntu-example.xml:99(para)
#: ./doc/image-guide/section_ubuntu-example.xml:102(para)
msgid "Select the defaults for all of the remaining options. When the installation is complete, you will be prompted to remove the CD-ROM."
msgstr ""
#: ./doc/image-guide/section_ubuntu-example.xml:108(para)
#: ./doc/image-guide/section_ubuntu-example.xml:111(para)
msgid "When you hit \"Continue\" the virtual machine will shut down, even though it says it will reboot."
msgstr ""
#: ./doc/image-guide/section_ubuntu-example.xml:111(para)
#: ./doc/image-guide/section_ubuntu-example.xml:114(para)
msgid "To eject a disk using <placeholder-1/>, libvirt requires that you attach an empty disk at the same target that the CDROM was previously attached, which should be <literal>hdc</literal>. You can confirm the appropriate target using the <placeholder-2/> command."
msgstr ""
#: ./doc/image-guide/section_ubuntu-example.xml:128(para)
#: ./doc/image-guide/section_ubuntu-example.xml:131(para)
msgid "Run the following commands in the host as root to start up the machine again as paused, eject the disk and resume. If you are using virt-manager, you may use the GUI instead."
msgstr ""
#: ./doc/image-guide/section_ubuntu-example.xml:135(para)
#: ./doc/image-guide/section_ubuntu-example.xml:138(para)
msgid "In the previous example, you paused the instance paused, ejected the disk, and unpaused the instance. In theory, you could have ejected the disk at the <guilabel>Installation complete</guilabel> screen. However, our testing indicates that the Ubuntu installer locks the drive so that it cannot be ejected at that point."
msgstr ""
#: ./doc/image-guide/section_ubuntu-example.xml:144(para)
#: ./doc/image-guide/section_ubuntu-example.xml:147(para)
msgid "When you boot for the first time after install, it may ask you about authentication tools, you can just choose 'Exit'. Then, log in as root using the root password you specified."
msgstr ""
#: ./doc/image-guide/section_ubuntu-example.xml:149(title)
#: ./doc/image-guide/section_ubuntu-example.xml:152(title)
msgid "Install cloud-init"
msgstr ""
#: ./doc/image-guide/section_ubuntu-example.xml:150(para)
#: ./doc/image-guide/section_ubuntu-example.xml:153(para)
msgid "The <placeholder-1/> script starts on instance boot and will search for a metadata provider to fetch a public key from. The public key will be placed in the default user account for the image."
msgstr ""
#: ./doc/image-guide/section_ubuntu-example.xml:153(para)
#: ./doc/image-guide/section_ubuntu-example.xml:156(para)
msgid "Install the <package>cloud-init</package> package:"
msgstr ""
#: ./doc/image-guide/section_ubuntu-example.xml:155(para)
#: ./doc/image-guide/section_ubuntu-example.xml:158(para)
msgid "When building Ubuntu images <placeholder-1/> must be explicitly configured for the metadata source in use. The OpenStack metadata server emulates the EC2 metadata service used by images in Amazon EC2."
msgstr ""
#: ./doc/image-guide/section_ubuntu-example.xml:158(para)
#: ./doc/image-guide/section_ubuntu-example.xml:161(para)
msgid "To set the metadata source to be used by the image run the <placeholder-1/> command against the <package>cloud-init</package> package. When prompted select the <literal>EC2</literal> data source:"
msgstr ""
#: ./doc/image-guide/section_ubuntu-example.xml:163(para)
#: ./doc/image-guide/section_ubuntu-example.xml:166(para)
msgid "The account varies by distribution. On Ubuntu-based virtual machines, the account is called \"ubuntu\". On Fedora-based virtual machines, the account is called \"ec2-user\"."
msgstr ""
#: ./doc/image-guide/section_ubuntu-example.xml:166(para)
#: ./doc/image-guide/section_ubuntu-example.xml:169(para)
msgid "You can change the name of the account used by cloud-init by editing the <filename>/etc/cloud/cloud.cfg</filename> file and adding a line with a different user. For example, to configure cloud-init to put the key in an account named \"admin\", edit the config file so it has the line:"
msgstr ""
#: ./doc/image-guide/section_ubuntu-example.xml:179(para)
#: ./doc/image-guide/section_ubuntu-example.xml:182(para)
msgid "The operating system records the MAC address of the virtual ethernet card in locations such as <filename>/etc/udev/rules.d/70-persistent-net.rules</filename> during the instance process. However, each time the image boots up, the virtual ethernet card will have a different MAC address, so this information must be deleted from the configuration file."
msgstr ""
#: ./doc/image-guide/section_ubuntu-example.xml:191(para)
#: ./doc/image-guide/section_ubuntu-example.xml:194(para)
msgid "Now that the image is ready to be uploaded to the Image Service, you no longer need to have this virtual machine image managed by libvirt. Use the <placeholder-1/> command to inform libvirt:"
msgstr ""
#: ./doc/image-guide/section_ubuntu-example.xml:198(para)
#: ./doc/image-guide/section_ubuntu-example.xml:201(para)
msgid "The underlying image file that you created with <placeholder-1/>, such as <filename>/tmp/trusty.qcow2</filename>, is now ready for uploading to the OpenStack Image Service."
msgstr ""

372
doc/image-guide/locale/ja.po
View File

File diff suppressed because it is too large Load Diff

110
doc/install-guide/locale/install-guide.pot
View File

File diff suppressed because one or more lines are too long

183
doc/install-guide/locale/ja.po
View File

@ -5,8 +5,8 @@
msgid ""
msgstr ""
"Project-Id-Version: OpenStack Manuals\n"
"POT-Creation-Date: 2014-08-05 15:21+0000\n"
"PO-Revision-Date: 2014-08-05 07:07+0000\n"
"POT-Creation-Date: 2014-08-15 05:33+0000\n"
"PO-Revision-Date: 2014-08-15 05:19+0000\n"
"Last-Translator: openstackjenkins <jenkins@openstack.org>\n"
"Language-Team: Japanese (http://www.transifex.com/projects/p/openstack-manuals-i18n/language/ja/)\n"
"MIME-Version: 1.0\n"
@ -217,7 +217,7 @@ msgstr "<literal>[database]</literal> セクションに、データベースの
#: ./doc/install-guide/section_ceilometer-install.xml239(replaceable)
#: ./doc/install-guide/section_ceilometer-install.xml240(replaceable)
#: ./doc/install-guide/section_ceilometer-install.xml241(replaceable)
#: ./doc/install-guide/section_basics-ntp.xml74(replaceable)
#: ./doc/install-guide/section_basics-ntp.xml83(replaceable)
#: ./doc/install-guide/section_nova-controller-install.xml72(replaceable)
#: ./doc/install-guide/section_nova-controller-install.xml73(replaceable)
#: ./doc/install-guide/section_nova-controller-install.xml74(replaceable)
@ -466,9 +466,9 @@ msgstr "データベース"
msgid ""
"Most OpenStack services require a database to store information. These "
"examples use a MySQL database that runs on the controller node. You must "
"install the MySQL database on the controller node. You must install the "
"MySQL Python library on any additional nodes that access MySQL."
msgstr "多くの OpenStack サービスは情報を保存するためにデータベースを必要とします。これらの例はコントローラーノードで MySQL データベースを使用します。コントローラーノードに MySQL データベースをインストールする必要があります。MySQL にアクセスする他のノードすべてに MySQL Python ライブラリをインストールする必要があります。"
"install the MySQL database on the controller node. You must also install the"
" MySQL Python library on any additional nodes that access MySQL."
msgstr ""
#: ./doc/install-guide/section_basics-database.xml15(para)
msgid ""
@ -481,8 +481,11 @@ msgid ""
msgstr "多くの OpenStack サービスは情報を保存するためにデータベースを必要とします。このガイドはコントローラーノードで実行するために SUSE Linux Enterprise Server で MySQL データベースを、openSUSE で互換データベースを使用します。この openSUSE 用の互換データベースは MariaDB です。コントローラーノードに MariaDB データベースをインストールする必要があります。MySQL または MariaDB にアクセスするすべてのノードに MySQL Python ライブラリをインストールする必要があります。"
#: ./doc/install-guide/section_basics-database.xml24(title)
msgid "Controller setup"
msgstr "コントローラーのセットアップ"
#: ./doc/install-guide/section_basics-networking-neutron.xml48(title)
#: ./doc/install-guide/section_basics-ntp.xml15(title)
#: ./doc/install-guide/section_basics-networking-nova.xml44(title)
msgid "Controller node"
msgstr "コントローラーノード"
#: ./doc/install-guide/section_basics-database.xml25(para)
msgid ""
@ -566,14 +569,15 @@ msgid ""
msgstr "<phrase os=\"rhel;centos;fedora;opensuse;sles\">root データベースパスワードをまだ設定していなければ、パスワードのプロンプトが出たときに、そのまま <keycap>ENTER</keycap> を押します。</phrase> このコマンドはデータベース環境をセキュアにするための多くのオプションを示します。他に良い理由がなければ、すべてのプロンプトに <placeholder-1/> と答えます。"
#: ./doc/install-guide/section_basics-database.xml109(title)
msgid "Node setup"
msgstr "ノードのセットアップ"
#: ./doc/install-guide/section_basics-ntp.xml66(title)
msgid "Other nodes"
msgstr ""
#: ./doc/install-guide/section_basics-database.xml110(para)
msgid ""
"On all nodes other than the controller node, install the MySQL Python "
"library:"
msgstr "コントローラーノード以外のすべてのノードに MySQL Python ライブラリをインストールします。"
"On nodes other than the controller node, you only need to install the MySQL "
"Python library:"
msgstr ""
#: ./doc/install-guide/section_cinder-controller.xml7(title)
msgid "Configure a Block Storage service controller"
@ -1372,7 +1376,7 @@ msgstr "ボリュームノードで:"
#: ./doc/install-guide/section_glance-verify.xml7(title)
#: ./doc/install-guide/section_keystone-verify.xml7(title)
#: ./doc/install-guide/section_heat-verify.xml7(title)
#: ./doc/install-guide/section_basics-ntp.xml95(title)
#: ./doc/install-guide/section_basics-ntp.xml104(title)
#: ./doc/install-guide/section_nova-verify.xml7(title)
msgid "Verify operation"
msgstr "運用の検証"
@ -1511,11 +1515,6 @@ msgid ""
"recommend using a local terminal session for these procedures."
msgstr "ネットワークインターフェースを再設定すると、ネットワーク接続性が中断されます。これらの手順はローカルの端末セッションを使用することを推奨します。"
#: ./doc/install-guide/section_basics-networking-neutron.xml48(title)
#: ./doc/install-guide/section_basics-networking-nova.xml44(title)
msgid "Controller node"
msgstr "コントローラーノード"
#: ./doc/install-guide/section_basics-networking-neutron.xml50(title)
#: ./doc/install-guide/section_basics-networking-neutron.xml85(title)
#: ./doc/install-guide/section_basics-networking-neutron.xml167(title)
@ -1710,16 +1709,16 @@ msgstr "接続性の検証"
#: ./doc/install-guide/section_basics-networking-neutron.xml214(para)
#: ./doc/install-guide/section_basics-networking-nova.xml154(para)
msgid ""
"We recommend that you verify network connectivity to the internet and among "
"We recommend that you verify network connectivity to the Internet and among "
"the nodes before proceeding further."
msgstr "続行する前に、インターネットとノード間のネットワーク接続性を検証することを推奨します。"
msgstr ""
#: ./doc/install-guide/section_basics-networking-neutron.xml218(para)
#: ./doc/install-guide/section_basics-networking-nova.xml158(para)
msgid ""
"From the <emphasis>controller</emphasis> node, <placeholder-1/> a site on "
"the internet:"
msgstr "<emphasis>controller</emphasis> ノードから、インターネットのサイトに <placeholder-1/> します。"
"the Internet:"
msgstr ""
#: ./doc/install-guide/section_basics-networking-neutron.xml232(para)
msgid ""
@ -1746,8 +1745,8 @@ msgstr "compute1"
#: ./doc/install-guide/section_basics-networking-neutron.xml262(para)
msgid ""
"From the <emphasis>network</emphasis> node, <placeholder-1/> a site on the "
"internet:"
msgstr "<emphasis>network</emphasis> ノードから、インターネットのサイトに <placeholder-1/> します。"
"Internet:"
msgstr ""
#: ./doc/install-guide/section_basics-networking-neutron.xml276(para)
msgid ""
@ -1765,8 +1764,8 @@ msgstr "<emphasis>network</emphasis> ノードから、<emphasis>compute</emphas
#: ./doc/install-guide/section_basics-networking-nova.xml187(para)
msgid ""
"From the <emphasis>compute</emphasis> node, <placeholder-1/> a site on the "
"internet:"
msgstr "<emphasis>compute</emphasis> ノードから、インターネットのサイトに <placeholder-1/> します。"
"Internet:"
msgstr ""
#: ./doc/install-guide/section_basics-networking-neutron.xml320(para)
#: ./doc/install-guide/section_basics-networking-nova.xml201(para)
@ -1979,13 +1978,13 @@ msgstr "初期ネットワークの作成"
msgid ""
"Before launching your first instance, you must create the necessary virtual "
"network infrastructure to which the instance will connect. This network "
"typically provides internet access <emphasis>from</emphasis> instances. You "
"can enable internet access <emphasis>to</emphasis> individual instances "
"typically provides Internet access <emphasis>from</emphasis> instances. You "
"can enable Internet access <emphasis>to</emphasis> individual instances "
"using a <glossterm>floating IP address</glossterm> and suitable "
"<glossterm>security group</glossterm> rules. The <literal>admin</literal> "
"tenant owns this network because it provides external network access for "
"multiple tenants."
msgstr "インスタンスの起動前に、インスタンスが接続するために必要な仮想ネットワークを作成する必要があります。このネットワークは、一般的にインスタンス<emphasis>から</emphasis>インターネットにアクセスできます。<glossterm baseform=\"floating IP address\">Floating IP アドレス</glossterm>と<glossterm baseform=\"security group\">セキュリティグループ</glossterm>ルールを使用して、個々のインスタンス<emphasis>へと</emphasis>インターネットからアクセス可能にできます。<literal>admin</literal> プロジェクトは、複数のプロジェクトに対して外部ネットワークを提供するため、このネットワークを所有します。"
msgstr ""
#: ./doc/install-guide/section_nova-networking-initial-network.xml17(para)
msgid ""
@ -2994,24 +2993,17 @@ msgstr "Network Time Protocol (NTP)"
msgid ""
"You must install <glossterm baseform=\"Network Time Protocol "
"(NTP)\">NTP</glossterm> to properly synchronize services among nodes. We "
"recommend that you configure the controller node to reference upstream "
"servers and other nodes to reference the controller node."
msgstr "サービスをノード間で適切に同期するために、<glossterm baseform=\"Network Time Protocol (NTP)\">NTP</glossterm> をインストールする必要があります。コントローラーノードが上位のサーバーを参照し、他のコードがコントローラーノードを参照するよう設定することを推奨します。"
#: ./doc/install-guide/section_basics-ntp.xml15(title)
#: ./doc/install-guide/section_nova-networking-controller-node.xml7(title)
#: ./doc/install-guide/section_neutron-ml2-controller-node.xml7(title)
#: ./doc/install-guide/section_neutron-ovs-controller-node.xml7(title)
msgid "Configure controller node"
msgstr "コントローラーノードの設定"
"recommend that you configure the controller node to reference more accurate "
"(lower stratum) servers and other nodes to reference the controller node."
msgstr ""
#: ./doc/install-guide/section_basics-ntp.xml17(title)
#: ./doc/install-guide/section_basics-ntp.xml59(title)
#: ./doc/install-guide/section_basics-ntp.xml68(title)
msgid "To install the NTP service"
msgstr "NTP サービスのインストール方法"
#: ./doc/install-guide/section_basics-ntp.xml25(title)
#: ./doc/install-guide/section_basics-ntp.xml67(title)
#: ./doc/install-guide/section_basics-ntp.xml76(title)
msgid "To configure the NTP service"
msgstr "NTP サービスの設定方法"
@ -3024,100 +3016,103 @@ msgid ""
msgstr "コントローラーノードはデフォルトで、パブリックなサーバープール経由で時刻同期します。しかしながらオプションとして、自組織により提供されるサーバーを参照するために、<filename>/etc/ntp.conf</filename> ファイルを編集することもできます。"
#: ./doc/install-guide/section_basics-ntp.xml31(para)
#: ./doc/install-guide/section_basics-ntp.xml71(para)
msgid "Edit the <filename>/etc/ntp.conf</filename> file:"
msgstr "<filename>/etc/ntp.conf</filename> ファイルを編集します。"
#: ./doc/install-guide/section_basics-ntp.xml32(para)
msgid ""
"Add, change, or remove the <literal>server</literal> keys as necessary for "
"your environment. Replace <replaceable>NTP_SERVER</replaceable> with the "
"hostname or IP address of suitable NTP server."
msgstr "環境の必要に応じて、<literal>server</literal> を追加、変更、削除します。<replaceable>NTP_SERVER</replaceable を適切な NTP サーバーのホスト名や IP アドレスで置き換えます。"
"Edit the <filename>/etc/ntp.conf</filename> file and add, change, or remove "
"the following keys as necessary for your environment:"
msgstr ""
#: ./doc/install-guide/section_basics-ntp.xml36(replaceable)
#: ./doc/install-guide/section_basics-ntp.xml34(replaceable)
msgid "NTP_SERVER"
msgstr "NTP_SERVER"
#: ./doc/install-guide/section_basics-ntp.xml38(para)
#: ./doc/install-guide/section_basics-ntp.xml76(para)
#: ./doc/install-guide/section_basics-ntp.xml37(para)
msgid ""
"Replace <replaceable>NTP_SERVER</replaceable> with the hostname or IP "
"address of a suitable more accurate (lower stratum) NTP server. The "
"configuration supports multiple <literal>server</literal> keys."
msgstr ""
#: ./doc/install-guide/section_basics-ntp.xml42(para)
msgid ""
"For the <literal>restrict</literal> keys, you essentially remove the "
"<literal>nopeer</literal> and <literal>noquery</literal> options."
msgstr ""
#: ./doc/install-guide/section_basics-ntp.xml47(para)
#: ./doc/install-guide/section_basics-ntp.xml85(para)
msgid ""
"Remove the <filename>/var/lib/ntp/ntp.conf.dhcp</filename> file if it "
"exists."
msgstr "<filename>/var/lib/ntp/ntp.conf.dhcp</filename> が存在すれば、削除します。"
#: ./doc/install-guide/section_basics-ntp.xml43(para)
#: ./doc/install-guide/section_basics-ntp.xml81(para)
#: ./doc/install-guide/section_basics-ntp.xml52(para)
#: ./doc/install-guide/section_basics-ntp.xml90(para)
msgid "Restart the NTP service:"
msgstr "NTP サービスを再起動します。"
#: ./doc/install-guide/section_basics-ntp.xml47(para)
#: ./doc/install-guide/section_basics-ntp.xml85(para)
#: ./doc/install-guide/section_basics-ntp.xml56(para)
#: ./doc/install-guide/section_basics-ntp.xml94(para)
msgid "Start the NTP service and configure it to start when the system boots:"
msgstr "NTP サービスを起動し、システム起動時に起動するよう設定します。"
#: ./doc/install-guide/section_basics-ntp.xml57(title)
msgid "Configure other nodes"
msgstr "他のノードの設定"
#: ./doc/install-guide/section_basics-ntp.xml68(para)
#: ./doc/install-guide/section_basics-ntp.xml77(para)
msgid ""
"Configure the network and compute nodes to reference the controller node."
msgstr "ネットワークノードとコンピュートノードがコントローラーノードを参照するよう設定します。"
#: ./doc/install-guide/section_basics-ntp.xml72(para)
#: ./doc/install-guide/section_basics-ntp.xml80(para)
msgid "Edit the <filename>/etc/ntp.conf</filename> file:"
msgstr "<filename>/etc/ntp.conf</filename> ファイルを編集します。"
#: ./doc/install-guide/section_basics-ntp.xml81(para)
msgid ""
"Comment out or remove all but one <literal>server</literal> key and change "
"it to reference the controller node."
msgstr "1 つの <literal>server</literal> キー以外をすべてコメントアウトまたは削除します。このキーは、コントローラーノードを参照するよう変更します。"
#: ./doc/install-guide/section_basics-ntp.xml96(para)
#: ./doc/install-guide/section_basics-ntp.xml105(para)
msgid ""
"We recommend that you verify NTP synchronization before proceeding further. "
"Some nodes, particularly those that reference the controller node, can take "
"several minutes to synchronize."
msgstr "続行する前に、NTP 同期について検証することを推奨します。いくつかのノード、とくにコントローラーノードを参照するノードは、同期に数分かかる可能性があります。"
#: ./doc/install-guide/section_basics-ntp.xml100(title)
msgid "To verify NTP synchronization"
msgstr "NTP 同期の検証方法"
#: ./doc/install-guide/section_basics-ntp.xml102(para)
#: ./doc/install-guide/section_basics-ntp.xml117(para)
#: ./doc/install-guide/section_basics-ntp.xml110(para)
#: ./doc/install-guide/section_basics-ntp.xml125(para)
msgid "Run this command on the <emphasis>controller</emphasis> node:"
msgstr "このコマンドを<emphasis>コントローラー</emphasis>ノードで実行します。"
#: ./doc/install-guide/section_basics-ntp.xml109(para)
#: ./doc/install-guide/section_basics-ntp.xml117(para)
msgid ""
"Contents in the <emphasis>remote</emphasis> column should indicate the "
"hostname or IP address of one or more NTP servers."
msgstr "<emphasis>remote</emphasis> 列の内容は、1 つ以上の NTP サーバーのホスト名や IP アドレスを意味するでしょう。"
#: ./doc/install-guide/section_basics-ntp.xml112(para)
#: ./doc/install-guide/section_basics-ntp.xml136(para)
#: ./doc/install-guide/section_basics-ntp.xml120(para)
#: ./doc/install-guide/section_basics-ntp.xml144(para)
msgid ""
"Contents in the <emphasis>refid</emphasis> column typically reference IP "
"addresses of upstream servers."
msgstr "<emphasis>refid</emphasis> 列の内容は、一般的に上位のサーバーの IP アドレスを参照します。"
#: ./doc/install-guide/section_basics-ntp.xml124(para)
#: ./doc/install-guide/section_basics-ntp.xml132(para)
msgid ""
"Contents in the <emphasis>condition</emphasis> column should indicate "
"<literal>sys.peer</literal> for at least one server."
msgstr "<emphasis>condition</emphasis> 列の内容は、少なくとも 1 つのサーバーの <literal>sys.peer</literal> を意味するでしょう。"
#: ./doc/install-guide/section_basics-ntp.xml128(para)
#: ./doc/install-guide/section_basics-ntp.xml141(para)
#: ./doc/install-guide/section_basics-ntp.xml136(para)
#: ./doc/install-guide/section_basics-ntp.xml149(para)
msgid "Run this command on <emphasis>all other</emphasis> nodes:"
msgstr "このコマンドを<emphasis>他のすべての</emphasis>ノードで実行します。"
#: ./doc/install-guide/section_basics-ntp.xml133(para)
#: ./doc/install-guide/section_basics-ntp.xml141(para)
msgid ""
"Contents in the <emphasis>remote</emphasis> column should indicate the "
"hostname of the controller node."
msgstr "<emphasis>remote</emphasis> 列の内容は、コントローラーノードのホスト名を意味するでしょう。"
#: ./doc/install-guide/section_basics-ntp.xml147(para)
#: ./doc/install-guide/section_basics-ntp.xml155(para)
msgid ""
"Contents in the <emphasis>condition</emphasis> column should indicate "
"<literal>sys.peer</literal>."
@ -3158,16 +3153,16 @@ msgstr "外部ネットワーク"
#: ./doc/install-guide/section_neutron-initial-networks.xml30(para)
msgid ""
"The external network typically provides internet access for your instances. "
"By default, this network only allows internet access "
"The external network typically provides Internet access for your instances. "
"By default, this network only allows Internet access "
"<emphasis>from</emphasis> instances using <glossterm>Network Address "
"Translation (NAT)</glossterm>. You can enable internet access "
"Translation (NAT)</glossterm>. You can enable Internet access "
"<emphasis>to</emphasis> individual instances using a <glossterm>floating IP "
"address</glossterm> and suitable <glossterm>security group</glossterm> "
"rules. The <literal>admin</literal> tenant owns this network because it "
"provides external network access for multiple tenants. You must also enable "
"sharing to allow access by those tenants."
msgstr "一般的に外部ネットワークにより、インスタンスにインターネットアクセスが提供されます。デフォルトでこのネットワークのみにより、インスタンス<emphasis>から </emphasis><glossterm baseform=\"Network Address Translation (NAT)\">NAT</glossterm> を使用して、インターネットへのアクセスが許可されます。<glossterm baseform=\"floating IP address\">Floating IP アドレス</glossterm>と適切な<glossterm baseform=\"security group\">セキュリティグループ</glossterm>ルールを使用して、個々のインスタンス<emphasis>へと</emphasis>インターネットからアクセス可能にできます。<literal>admin</literal> プロジェクトは、複数のプロジェクトに対して外部ネットワークを提供するため、このネットワークを所有します。これらのプロジェクトによりアクセスを許可するために、共有を有効化する必要があります。"
msgstr ""
#: ./doc/install-guide/section_neutron-initial-networks.xml44(title)
msgid "To create the external network"
@ -5473,6 +5468,12 @@ msgid ""
"must make sense of it even if the prompts appear in an illogical order."
msgstr "パッケージは事前の依存関係を必要としません。<systemitem class=\"library\">dbconfig-common</systemitem> がすでにシステムにインストールされていれば、すべてのプロンプトが表示されます。しかしながら、<systemitem class=\"library\">debconf</systemitem> 画面が表示される順番を定義できません。プロンプトが非論理的な順番で表示されたときでさえ、ユーザーはその意味を理解する必要があります。"
#: ./doc/install-guide/section_nova-networking-controller-node.xml7(title)
#: ./doc/install-guide/section_neutron-ml2-controller-node.xml7(title)
#: ./doc/install-guide/section_neutron-ovs-controller-node.xml7(title)
msgid "Configure controller node"
msgstr "コントローラーノードの設定"
#: ./doc/install-guide/section_nova-networking-controller-node.xml8(para)
msgid ""
"Legacy networking primarily involves compute nodes. However, you must "
@ -7667,23 +7668,23 @@ msgstr "オプションとして、コントローラーノードは、Block Sto
#: ./doc/install-guide/ch_overview.xml67(para)
msgid ""
"The network node runs the Networking plug-in, layer 2 agent, and several "
"layer 3 agents that provision and operate tenant networks. Layer 2 services "
"include provisioning of virtual networks and tunnels. Layer 3 services "
"The network node runs the Networking plug-in, layer-2 agent, and several "
"layer-3 agents that provision and operate tenant networks. Layer-2 services "
"include provisioning of virtual networks and tunnels. Layer-3 services "
"include routing, <glossterm baseform=\"Network Address Translation "
"(NAT)\">NAT</glossterm> , and <glossterm>DHCP</glossterm>. This node also "
"handles external (internet) connectivity for tenant virtual machines or "
"(NAT)\">NAT</glossterm>, and <glossterm>DHCP</glossterm>. This node also "
"handles external (Internet) connectivity for tenant virtual machines or "
"instances."
msgstr "ネットワークノードは Networking プラグインエージェント、L2 エージェント、いくつかの L3 エージェントを実行します。これらはプロジェクトのネットワークを展開、運用します。L2 サービスには、仮想ネットワーク、トンネルの展開が含まれます。L3 サービスには、ルーティング、<glossterm baseform=\"Network Address Translation (NAT)\">NAT</glossterm>、<glossterm>DHCP</glossterm> が含まれます。このノードは、プロジェクトの仮想マシンやインスタンス用の外部 (インターネット) 接続も処理します。"
msgstr ""
#: ./doc/install-guide/ch_overview.xml77(para)
msgid ""
"The compute node runs the hypervisor portion of Compute, which operates "
"tenant virtual machines or instances. By default Compute uses KVM as the "
"hypervisor. The compute node also runs the Networking plug-in and layer 2 "
"hypervisor. The compute node also runs the Networking plug-in and layer-2 "
"agent which operate tenant networks and implement security groups. You can "
"run more than one compute node."
msgstr "コンピュートノードは、プロジェクトの仮想マシンやインスタンスを運転する Compute のハイパーバイザー部分を実行します。Compute はハイパーバイザーとして標準で KVM を使用します。コンピュートノードは、プロジェクトのネットワークを運転し、セキュリティグループを実装する、Networking プラグインと L2 エージェントも実行します。複数のコンピュートノードを実行することもできます。"
msgstr ""
#: ./doc/install-guide/ch_overview.xml83(para)
#: ./doc/install-guide/ch_overview.xml132(para)

2120
doc/networking-guide/locale/networking-guide.pot
View File

File diff suppressed because it is too large Load Diff

174
doc/user-guide-admin/locale/ja.po
View File

@ -4,9 +4,9 @@
msgid ""
msgstr ""
"Project-Id-Version: OpenStack Manuals\n"
"POT-Creation-Date: 2014-07-27 05:14+0000\n"
"PO-Revision-Date: 2014-07-24 18:05+0000\n"
"Last-Translator: Tomoyuki KATO <tomo@dream.daynight.jp>\n"
"POT-Creation-Date: 2014-08-15 05:33+0000\n"
"PO-Revision-Date: 2014-08-09 17:01+0000\n"
"Last-Translator: openstackjenkins <jenkins@openstack.org>\n"
"Language-Team: Japanese (http://www.transifex.com/projects/p/openstack-manuals-i18n/language/ja/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
@ -375,6 +375,7 @@ msgstr "groupName"
#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml81(para)
#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml101(para)
#: ./doc/user-guide-admin/section_cli_nova_specify_host.xml17(para)
#: ./doc/user-guide-admin/section_cli_keystone_services.xml102(para)
msgid "For example:"
msgstr "例:"
@ -2308,6 +2309,7 @@ msgstr "ROLE_ID"
#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml345(replaceable)
#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml365(replaceable)
#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml370(replaceable)
#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml60(replaceable)
#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml212(replaceable)
msgid "TENANT_ID"
msgstr "TENANT_ID"
@ -3113,6 +3115,172 @@ msgid ""
"<guibutton>Delete Users</guibutton> to confirm the deletion."
msgstr "<guilabel>ユーザーの削除の確認</guilabel>ウィンドウで、削除の確認をするために<guibutton>ユーザーの削除</guibutton>をクリックします。"
#: ./doc/user-guide-admin/section_cli_keystone_services.xml8(title)
msgid "Create and manage services and service users"
msgstr "サービスとサービスユーザーの作成と管理"
#: ./doc/user-guide-admin/section_cli_keystone_services.xml9(para)
msgid "The Identity Service enables you to define services, as follows:"
msgstr "Identity により、以下のようなサービスを定義できます。"
#: ./doc/user-guide-admin/section_cli_keystone_services.xml13(para)
msgid ""
"Service catalog template. The Identity Service acts as a service catalog of "
"endpoints for other OpenStack services. The "
"<literal>etc/default_catalog.templates</literal> template file defines the "
"endpoints for services. When the Identity Service uses a template file back "
"end, any changes that are made to the endpoints are cached. These changes do"
" not persist when you restart the service or reboot the machine."
msgstr "サービスカタログテンプレート。Identity は、他の OpenStack サービスのエンドポイントのサービスカタログとして動作します。<literal>etc/default_catalog.templates</literal> テンプレートファイルは、サービスのエンドポイントを定義します。Identity がテンプレートファイルバックエンドを使用するとき、エンドポイントに対して実行された変更はすべてキャッシュされます。サービスの再起動やマシンの再起動をしたとき、これらの変更は保持されません。"
#: ./doc/user-guide-admin/section_cli_keystone_services.xml24(para)
msgid ""
"A SQL back end for the catalog service. When the Identity Service is online,"
" you must add the services to the catalog. When you deploy a system for "
"production, use the SQL back end."
msgstr "カタログサービスの SQL バックエンド。Identity がオンラインのとき、サービスをカタログに追加する必要があります。システムを本番環境に導入するとき、SQL バックエンドを使用します。"
#: ./doc/user-guide-admin/section_cli_keystone_services.xml30(para)
msgid ""
"The <literal>auth_token</literal> middleware supports the use of either a "
"shared secret or users for each service."
msgstr "<literal>auth_token</literal> ミドルウェアは、共有シークレットの使用、各サービス用のユーザーの使用をサポートします。"
#: ./doc/user-guide-admin/section_cli_keystone_services.xml33(para)
msgid ""
"To authenticate users against the Identity Service, you must create a "
"service user for each OpenStack service. For example, create a service user "
"for the Compute, Block Storage, and Networking services."
msgstr "Identity に対してユーザーを認証するために、各 OpenStack サービスのサービスユーザーを作成する必要があります。例えば、Compute、Block Storage、Networking のサービスのサービスユーザーを作成します。"
#: ./doc/user-guide-admin/section_cli_keystone_services.xml37(para)
msgid ""
"To configure the OpenStack services with service users, create a project for"
" all services and create users for each service. Assign the admin role to "
"each service user and project pair. This role enables users to validate "
"tokens and authenticate and authorize other user requests."
msgstr "サービスユーザーを持つ OpenStack サービスを設定するために、すべてのサービスのプロジェクトを作成し、各サービスのユーザーを作成します。各サービスユーザーとプロジェクトのペアに admin ロールを割り当てます。このロールにより、ユーザーがトークンを検証し、他のユーザーのリクエストを認証、認可できます。"
#: ./doc/user-guide-admin/section_cli_keystone_services.xml43(title)
msgid "Create a service"
msgstr "サービスの作成"
#: ./doc/user-guide-admin/section_cli_keystone_services.xml46(para)
msgid "List the available services:"
msgstr "利用可能なサービスを一覧表示します。"
#: ./doc/user-guide-admin/section_cli_keystone_services.xml60(para)
msgid "To create a service, run this command:"
msgstr "サービスを作成するために、このコマンドを実行します。"
#: ./doc/user-guide-admin/section_cli_keystone_services.xml61(replaceable)
msgid "service_name"
msgstr "service_name"
#: ./doc/user-guide-admin/section_cli_keystone_services.xml61(replaceable)
msgid "service_type"
msgstr "service_type"
#: ./doc/user-guide-admin/section_cli_keystone_services.xml61(replaceable)
msgid "service_description"
msgstr "service_description"
#: ./doc/user-guide-admin/section_cli_keystone_services.xml62(para)
msgid "The arguments are:"
msgstr "引数は以下のとおりです。"
#: ./doc/user-guide-admin/section_cli_keystone_services.xml65(para)
msgid ""
"<code><replaceable>service_name</replaceable></code>. The unique name of the"
" new service."
msgstr "<code><replaceable>service_name</replaceable></code>。新しいサービスの一意な名前。"
#: ./doc/user-guide-admin/section_cli_keystone_services.xml69(para)
msgid ""
"<code><replaceable>service_type</replaceable></code>. The service type, such"
" as <code>identity</code>, <code>compute</code>, <code>network</code>, "
"<code>image</code>, <code>object-store</code> or any other service "
"identifier string."
msgstr "<code><replaceable>service_type</replaceable></code>。<code>identity</code>、<code>compute</code>、<code>network</code>、<code>image</code>、<code>object-store</code>、他のサービス識別文字列などのサービス種別。"
#: ./doc/user-guide-admin/section_cli_keystone_services.xml79(para)
msgid ""
"<code><replaceable>service_description</replaceable></code>. The description"
" of the service."
msgstr "<code><replaceable>service_description</replaceable></code>。サービスの説明。"
#: ./doc/user-guide-admin/section_cli_keystone_services.xml83(para)
msgid ""
"For example, to create a <literal>swift</literal> service of type <literal"
">object-store</literal>, run this command:"
msgstr "例えば、<literal>object-store</literal> 種別の <literal>swift</literal> サービスを作成するために、このコマンドを実行します。"
#: ./doc/user-guide-admin/section_cli_keystone_services.xml99(para)
msgid "To get details for a service, run this command:"
msgstr "サービスの詳細を取得するために、このコマンドを実行します。"
#: ./doc/user-guide-admin/section_cli_keystone_services.xml101(replaceable)
msgid "service_ID"
msgstr "service_ID"
#: ./doc/user-guide-admin/section_cli_keystone_services.xml117(title)
msgid "Create service users"
msgstr "サービスユーザーの作成"
#: ./doc/user-guide-admin/section_cli_keystone_services.xml120(para)
msgid ""
"Create a project for the service users. Typically, this project is named "
"<literal>service</literal>, but choose any name you like:"
msgstr "サービスユーザーのプロジェクトを作成します。このプロジェクトは一般的に、<literal>service</literal> という名前ですが、お好きなものを利用できます。"
#: ./doc/user-guide-admin/section_cli_keystone_services.xml125(para)
msgid "The output shows the ID for the project."
msgstr "この出力はプロジェクトの ID を表示します。"
#: ./doc/user-guide-admin/section_cli_keystone_services.xml126(para)
msgid ""
"Make a note of this ID. You need it to create service users and assign "
"roles."
msgstr "この ID を記録します。サービスユーザーの作成とロールの割り当てに必要になります。"
#: ./doc/user-guide-admin/section_cli_keystone_services.xml138(para)
msgid "Create service users for the relevant services for your deployment."
msgstr "お使いの環境に関連するサービス用のサービスユーザーを作成します。"
#: ./doc/user-guide-admin/section_cli_keystone_services.xml142(para)
msgid ""
"To assign the admin role to the service user-project pairs, run this command"
" to get the ID of the admin role:"
msgstr "サービスユーザーとプロジェクトのペアに admin ロールを割り当てるために、admin ロールの ID を取得するために、このコマンドを実行します。"
#: ./doc/user-guide-admin/section_cli_keystone_services.xml158(para)
msgid "Assign the admin role to the user-project pair:"
msgstr "ユーザーとプロジェクトのペアに admin ロールを割り当てます。"
#: ./doc/user-guide-admin/section_cli_keystone_services.xml160(replaceable)
msgid "SERVICE_USER_ID"
msgstr "SERVICE_USER_ID"
#: ./doc/user-guide-admin/section_cli_keystone_services.xml160(replaceable)
msgid "ADMIN_ROLE_ID"
msgstr "ADMIN_ROLE_ID"
#: ./doc/user-guide-admin/section_cli_keystone_services.xml160(replaceable)
msgid "SERVICE_PROJECT_ID"
msgstr "SERVICE_PROJECT_ID"
#: ./doc/user-guide-admin/section_cli_keystone_services.xml165(title)
msgid "Delete a service"
msgstr "サービスの削除"
#: ./doc/user-guide-admin/section_cli_keystone_services.xml166(para)
msgid "To delete a specified service, specify its ID:"
msgstr "指定したサービスを削除するために、その ID を指定します。"
#: ./doc/user-guide-admin/section_cli_keystone_services.xml167(replaceable)
msgid "SERVICE_ID"
msgstr "SERVICE_ID"
#: ./doc/user-guide-admin/section_cli_admin_manage_environment.xml7(title)
msgid "Manage the OpenStack environment"
msgstr "OpenStack 環境の管理"

138
doc/user-guide-admin/locale/user-guide-admin.pot
View File

@ -1,7 +1,7 @@
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"POT-Creation-Date: 2014-07-27 06:09+0000\n"
"POT-Creation-Date: 2014-08-15 06:09+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"
@ -261,7 +261,7 @@ msgstr ""
msgid "groupName"
msgstr ""
#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml:76(para) ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml:112(para) ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml:175(para) ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml:196(para) ./doc/user-guide-admin/section_cli_nova_floating_ips.xml:69(para) ./doc/user-guide-admin/section_cli_nova_floating_ips.xml:104(para) ./doc/user-guide-admin/section_cli_cinder_quotas.xml:81(para) ./doc/user-guide-admin/section_cli_cinder_quotas.xml:101(para) ./doc/user-guide-admin/section_cli_nova_specify_host.xml:17(para)
#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml:76(para) ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml:112(para) ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml:175(para) ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml:196(para) ./doc/user-guide-admin/section_cli_nova_floating_ips.xml:69(para) ./doc/user-guide-admin/section_cli_nova_floating_ips.xml:104(para) ./doc/user-guide-admin/section_cli_cinder_quotas.xml:81(para) ./doc/user-guide-admin/section_cli_cinder_quotas.xml:101(para) ./doc/user-guide-admin/section_cli_nova_specify_host.xml:17(para) ./doc/user-guide-admin/section_cli_keystone_services.xml:102(para)
msgid "For example:"
msgstr ""
@ -1687,7 +1687,7 @@ msgstr ""
msgid "ROLE_ID"
msgstr ""
#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml:341(replaceable) ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml:345(replaceable) ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml:365(replaceable) ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml:370(replaceable) ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml:212(replaceable)
#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml:341(replaceable) ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml:345(replaceable) ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml:365(replaceable) ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml:370(replaceable) ./doc/user-guide-admin/section_cli_cinder_quotas.xml:60(replaceable) ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml:212(replaceable)
msgid "TENANT_ID"
msgstr ""
@ -2289,6 +2289,138 @@ msgstr ""
msgid "In the <guilabel>Confirm Delete Users</guilabel> window, click <guibutton>Delete Users</guibutton> to confirm the deletion."
msgstr ""
#: ./doc/user-guide-admin/section_cli_keystone_services.xml:8(title)
msgid "Create and manage services and service users"
msgstr ""
#: ./doc/user-guide-admin/section_cli_keystone_services.xml:9(para)
msgid "The Identity Service enables you to define services, as follows:"
msgstr ""
#: ./doc/user-guide-admin/section_cli_keystone_services.xml:13(para)
msgid "Service catalog template. The Identity Service acts as a service catalog of endpoints for other OpenStack services. The <literal>etc/default_catalog.templates</literal> template file defines the endpoints for services. When the Identity Service uses a template file back end, any changes that are made to the endpoints are cached. These changes do not persist when you restart the service or reboot the machine."
msgstr ""
#: ./doc/user-guide-admin/section_cli_keystone_services.xml:24(para)
msgid "A SQL back end for the catalog service. When the Identity Service is online, you must add the services to the catalog. When you deploy a system for production, use the SQL back end."
msgstr ""
#: ./doc/user-guide-admin/section_cli_keystone_services.xml:30(para)
msgid "The <literal>auth_token</literal> middleware supports the use of either a shared secret or users for each service."
msgstr ""
#: ./doc/user-guide-admin/section_cli_keystone_services.xml:33(para)
msgid "To authenticate users against the Identity Service, you must create a service user for each OpenStack service. For example, create a service user for the Compute, Block Storage, and Networking services."
msgstr ""
#: ./doc/user-guide-admin/section_cli_keystone_services.xml:37(para)
msgid "To configure the OpenStack services with service users, create a project for all services and create users for each service. Assign the admin role to each service user and project pair. This role enables users to validate tokens and authenticate and authorize other user requests."
msgstr ""
#: ./doc/user-guide-admin/section_cli_keystone_services.xml:43(title)
msgid "Create a service"
msgstr ""
#: ./doc/user-guide-admin/section_cli_keystone_services.xml:46(para)
msgid "List the available services:"
msgstr ""
#: ./doc/user-guide-admin/section_cli_keystone_services.xml:60(para)
msgid "To create a service, run this command:"
msgstr ""
#: ./doc/user-guide-admin/section_cli_keystone_services.xml:61(replaceable)
msgid "service_name"
msgstr ""
#: ./doc/user-guide-admin/section_cli_keystone_services.xml:61(replaceable)
msgid "service_type"
msgstr ""
#: ./doc/user-guide-admin/section_cli_keystone_services.xml:61(replaceable)
msgid "service_description"
msgstr ""
#: ./doc/user-guide-admin/section_cli_keystone_services.xml:62(para)
msgid "The arguments are:"
msgstr ""
#: ./doc/user-guide-admin/section_cli_keystone_services.xml:65(para)
msgid "<code><replaceable>service_name</replaceable></code>. The unique name of the new service."
msgstr ""
#: ./doc/user-guide-admin/section_cli_keystone_services.xml:69(para)
msgid "<code><replaceable>service_type</replaceable></code>. The service type, such as <code>identity</code>, <code>compute</code>, <code>network</code>, <code>image</code>, <code>object-store</code> or any other service identifier string."
msgstr ""
#: ./doc/user-guide-admin/section_cli_keystone_services.xml:79(para)
msgid "<code><replaceable>service_description</replaceable></code>. The description of the service."
msgstr ""
#: ./doc/user-guide-admin/section_cli_keystone_services.xml:83(para)
msgid "For example, to create a <literal>swift</literal> service of type <literal>object-store</literal>, run this command:"
msgstr ""
#: ./doc/user-guide-admin/section_cli_keystone_services.xml:99(para)
msgid "To get details for a service, run this command:"
msgstr ""
#: ./doc/user-guide-admin/section_cli_keystone_services.xml:101(replaceable)
msgid "service_ID"
msgstr ""
#: ./doc/user-guide-admin/section_cli_keystone_services.xml:117(title)
msgid "Create service users"
msgstr ""
#: ./doc/user-guide-admin/section_cli_keystone_services.xml:120(para)
msgid "Create a project for the service users. Typically, this project is named <literal>service</literal>, but choose any name you like:"
msgstr ""
#: ./doc/user-guide-admin/section_cli_keystone_services.xml:125(para)
msgid "The output shows the ID for the project."
msgstr ""
#: ./doc/user-guide-admin/section_cli_keystone_services.xml:126(para)
msgid "Make a note of this ID. You need it to create service users and assign roles."
msgstr ""
#: ./doc/user-guide-admin/section_cli_keystone_services.xml:138(para)
msgid "Create service users for the relevant services for your deployment."
msgstr ""
#: ./doc/user-guide-admin/section_cli_keystone_services.xml:142(para)
msgid "To assign the admin role to the service user-project pairs, run this command to get the ID of the admin role:"
msgstr ""
#: ./doc/user-guide-admin/section_cli_keystone_services.xml:158(para)
msgid "Assign the admin role to the user-project pair:"
msgstr ""
#: ./doc/user-guide-admin/section_cli_keystone_services.xml:160(replaceable)
msgid "SERVICE_USER_ID"
msgstr ""
#: ./doc/user-guide-admin/section_cli_keystone_services.xml:160(replaceable)
msgid "ADMIN_ROLE_ID"
msgstr ""
#: ./doc/user-guide-admin/section_cli_keystone_services.xml:160(replaceable)
msgid "SERVICE_PROJECT_ID"
msgstr ""
#: ./doc/user-guide-admin/section_cli_keystone_services.xml:165(title)
msgid "Delete a service"
msgstr ""
#: ./doc/user-guide-admin/section_cli_keystone_services.xml:166(para)
msgid "To delete a specified service, specify its ID:"
msgstr ""
#: ./doc/user-guide-admin/section_cli_keystone_services.xml:167(replaceable)
msgid "SERVICE_ID"
msgstr ""
#: ./doc/user-guide-admin/section_cli_admin_manage_environment.xml:7(title)
msgid "Manage the OpenStack environment"
msgstr ""

792
doc/user-guide/locale/fr.po
View File

@ -11,9 +11,9 @@
msgid ""
msgstr ""
"Project-Id-Version: OpenStack Manuals\n"
"POT-Creation-Date: 2014-08-07 23:43+0000\n"
"PO-Revision-Date: 2014-08-07 20:10+0000\n"
"Last-Translator: Frédéric <frosmont@free.fr>\n"
"POT-Creation-Date: 2014-08-15 05:33+0000\n"
"PO-Revision-Date: 2014-08-14 06:30+0000\n"
"Last-Translator: Andreas Jaeger <jaegerandi@gmail.com>\n"
"Language-Team: French (http://www.transifex.com/projects/p/openstack-manuals-i18n/language/fr/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
@ -21,6 +21,497 @@ msgstr ""
"Language: fr\n"
"Plural-Forms: nplurals=2; plural=(n > 1);\n"
#: ./doc/user-guide/section_cli_nova_reboot.xml7(title)
msgid "Reboot an instance"
msgstr "Redémarrer une instance"
#: ./doc/user-guide/section_cli_nova_reboot.xml8(para)
msgid ""
"You can soft or hard reboot a running instance. A soft reboot attempts a "
"graceful shut down and restart of the instance. A hard reboot power cycles "
"the instance."
msgstr ""
#: ./doc/user-guide/section_cli_nova_reboot.xml11(para)
msgid "By default, when you reboot a server, it is a soft reboot."
msgstr "Par défaut, quand vous redémarrez un serveur, c'est un redémarrage logiciel."
#: ./doc/user-guide/section_cli_nova_reboot.xml12(replaceable)
#: ./doc/user-guide/section_cli_nova_reboot.xml14(replaceable)
#: ./doc/user-guide/app_cheat_sheet.xml176(replaceable)
msgid "SERVER"
msgstr "SERVEUR"
#: ./doc/user-guide/section_cli_nova_reboot.xml13(para)
msgid ""
"To perform a hard reboot, pass the <parameter>--hard</parameter> parameter, "
"as follows:"
msgstr ""
#: ./doc/user-guide/section_cli_nova_boot.xml7(title)
msgid "Launch instances"
msgstr "Lancer les instances"
#: ./doc/user-guide/section_cli_nova_boot.xml8(para)
#: ./doc/user-guide/section_dashboard_launch_instances.xml8(para)
msgid "Instances are virtual machines that run inside the cloud."
msgstr "Les instances sont des machines virtuelles individuelles qui tournent dans le cloud."
#: ./doc/user-guide/section_cli_nova_boot.xml10(para)
msgid "Before you can launch an instance, gather the following parameters:"
msgstr "Avant de lancer une instance, ramassez les paramètres suivants:"
#: ./doc/user-guide/section_cli_nova_boot.xml14(para)
msgid ""
"The <emphasis role=\"bold\">instance source</emphasis> can be an image, "
"snapshot, or block storage volume that contains an image or snapshot."
msgstr ""
#: ./doc/user-guide/section_cli_nova_boot.xml19(para)
msgid "A <emphasis role=\"bold\">name</emphasis> for your instance."
msgstr ""
#: ./doc/user-guide/section_cli_nova_boot.xml22(para)
msgid ""
"The <emphasis role=\"bold\">flavor</emphasis> for your instance, which "
"defines the compute, memory, and storage capacity of nova computing "
"instances. A flavor is an available hardware configuration for a server. It "
"defines the size of a virtual server that can be launched."
msgstr ""
#: ./doc/user-guide/section_cli_nova_boot.xml30(para)
msgid ""
"Any <emphasis role=\"bold\">user data</emphasis> files. A user data file is "
"a special key in the metadata service that holds a file that cloud-aware "
"applications in the guest instance can access. For example, one application "
"that uses user data is the <link "
"href=\"https://help.ubuntu.com/community/CloudInit\">cloud-init</link> "
"system, which is an open-source package from Ubuntu that is available on "
"various Linux distributions and that handles early initialization of a cloud"
" instance."
msgstr ""
#: ./doc/user-guide/section_cli_nova_boot.xml43(para)
msgid ""
"Access and security credentials, which include one or both of the following "
"credentials:"
msgstr ""
#: ./doc/user-guide/section_cli_nova_boot.xml47(para)
msgid ""
"A <emphasis role=\"bold\">key pair</emphasis> for your instance, which are "
"SSH credentials that are injected into images when they are launched. For "
"the key pair to be successfully injected, the image must contain the "
"<literal>cloud-init</literal> package. Create at least one key pair for each"
" project. If you already have generated a key pair with an external tool, "
"you can import it into OpenStack. You can use the key pair for multiple "
"instances that belong to that project."
msgstr ""
#: ./doc/user-guide/section_cli_nova_boot.xml61(para)
msgid ""
"A <emphasis role=\"bold\">security group</emphasis> that defines which "
"incoming network traffic is forwarded to instances. Security groups hold a "
"set of firewall policies, known as <emphasis role=\"italic\">security group "
"rules</emphasis>."
msgstr ""
#: ./doc/user-guide/section_cli_nova_boot.xml72(para)
msgid ""
"If needed, you can assign a <emphasis role=\"bold\">floating (public) IP "
"address</emphasis> to a running instance."
msgstr ""
#: ./doc/user-guide/section_cli_nova_boot.xml77(para)
msgid ""
"You can also attach a block storage device, or <emphasis "
"role=\"bold\">volume</emphasis>, for persistent storage."
msgstr ""
#: ./doc/user-guide/section_cli_nova_boot.xml83(para)
#: ./doc/user-guide/section_cli_nova_configure_instances.xml62(para)
msgid ""
"Instances that use the default security group cannot, by default, be "
"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 ""
#: ./doc/user-guide/section_cli_nova_boot.xml88(para)
#: ./doc/user-guide/section_cli_nova_configure_instances.xml66(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 "Vous pouvez aussi attribuer une adresse IP flottante à une instance en cours d'exécution pour la rendre accessible depuis l'extérieur du cloud. Voir <xref linkend=\"manage_ip_addresses\"/>."
#: ./doc/user-guide/section_cli_nova_boot.xml92(para)
msgid ""
"After you gather the parameters that you need to launch an instance, you can"
" launch it from an <link linkend=\"launch_from_image\">image</link> or a "
"<link linkend=\"boot_from_volume\">volume</link>. You can launch an instance"
" directly from one of the available OpenStack images or from an image that "
"you have copied to a persistent volume. The OpenStack Image Service provides"
" a pool of images that are accessible to members of different projects."
msgstr ""
#: ./doc/user-guide/section_cli_nova_boot.xml102(title)
msgid "Gather parameters to launch an instance"
msgstr "Pour lancer une instance, ramassez les paramètres"
#: ./doc/user-guide/section_cli_nova_boot.xml104(para)
msgid "Before you begin, source the OpenStack RC file."
msgstr ""
#: ./doc/user-guide/section_cli_nova_boot.xml107(para)
msgid "List the available flavors:"
msgstr "Listez les types d'instances disponibles:"
#: ./doc/user-guide/section_cli_nova_boot.xml109(para)
msgid "Note the ID of the flavor that you want to use for your instance:"
msgstr ""
#: ./doc/user-guide/section_cli_nova_boot.xml122(para)
msgid "List the available images:"
msgstr "Lister les images disponibles:"
#: ./doc/user-guide/section_cli_nova_boot.xml124(para)
msgid "Note the ID of the image from which you want to boot your instance:"
msgstr ""
#: ./doc/user-guide/section_cli_nova_boot.xml132(para)
msgid ""
"You can also filter the image list by using <placeholder-1/> to find a "
"specific image, as follows:"
msgstr ""
#: ./doc/user-guide/section_cli_nova_boot.xml139(para)
msgid "List the available security groups:"
msgstr "Listez les groupes de sécurité disponibles:"
#: ./doc/user-guide/section_cli_nova_boot.xml141(para)
msgid ""
"If you are an admin user, specify the <option>--all-tenants</option> "
"parameter to list groups for all tenants."
msgstr ""
#: ./doc/user-guide/section_cli_nova_boot.xml146(para)
msgid ""
"Note the ID of the security group that you want to use for your instance:"
msgstr ""
#: ./doc/user-guide/section_cli_nova_boot.xml152(para)
msgid ""
"If you have not created any security groups, you can assign the instance to "
"only the default security group."
msgstr "Si vous n'avez pas créer de groupe de sécurité, vous ne pourrez qu'assigner l'instance au groupe de sécurité par défaut."
#: ./doc/user-guide/section_cli_nova_boot.xml155(para)
msgid "You can view rules for a specified security group:"
msgstr ""
#: ./doc/user-guide/section_cli_nova_boot.xml160(para)
msgid ""
"List the available key pairs and note the name of the key pair that you use "
"for SSH access."
msgstr ""
#: ./doc/user-guide/section_cli_nova_boot.xml169(title)
msgid "Launch an instance from an image"
msgstr "Lancer une instance depuis une image"
#: ./doc/user-guide/section_cli_nova_boot.xml172(para)
msgid ""
"After you gather required parameters, run the following command to launch an"
" instance. Specify the server name, flavor ID, and image ID."
msgstr ""
#: ./doc/user-guide/section_cli_nova_boot.xml175(para)
msgid ""
"Optionally, you can provide a key name for access control and a security "
"group for security. You can also include metadata key and value pairs. For "
"example, you can add a description for your server by providing the "
"<parameter>--meta description=\"My Server\"</parameter> parameter."
msgstr ""
#: ./doc/user-guide/section_cli_nova_boot.xml182(para)
msgid ""
"You can pass user data in a local file at instance launch by using the "
"<parameter>--user-data <replaceable>USER-DATA-FILE</replaceable></parameter>"
" parameter."
msgstr ""
#: ./doc/user-guide/section_cli_nova_boot.xml187(replaceable)
msgid "FLAVOR_ID"
msgstr "FLAVOR_ID"
#: ./doc/user-guide/section_cli_nova_boot.xml187(replaceable)
msgid "IMAGE_ID"
msgstr "IMAGE_ID"
#: ./doc/user-guide/section_cli_nova_boot.xml187(replaceable)
#: ./doc/user-guide/section_cli_nova_configure_instances.xml77(replaceable)
#: ./doc/user-guide/section_cli_nova_configure_instances.xml99(replaceable)
msgid "KEY_NAME"
msgstr "KEY_NAME"
#: ./doc/user-guide/section_cli_nova_boot.xml188(replaceable)
msgid "USER_DATA_FILE"
msgstr ""
#: ./doc/user-guide/section_cli_nova_boot.xml188(replaceable)
msgid "SEC_GROUP"
msgstr ""
#: ./doc/user-guide/section_cli_nova_boot.xml188(replaceable)
msgid "KEY=VALUE"
msgstr "KEY=VALUE"
#: ./doc/user-guide/section_cli_nova_boot.xml189(replaceable)
#: ./doc/user-guide/app_cheat_sheet.xml167(replaceable)
#: ./doc/user-guide/section_cli_nova_startstop.xml15(replaceable)
#: ./doc/user-guide/section_cli_nova_startstop.xml19(replaceable)
#: ./doc/user-guide/section_cli_nova_startstop.xml36(replaceable)
#: ./doc/user-guide/section_cli_nova_startstop.xml41(replaceable)
#: ./doc/user-guide/section_cli_nova_get_console.xml9(replaceable)
msgid "INSTANCE_NAME"
msgstr "NOM_INSTANCE"
#: ./doc/user-guide/section_cli_nova_boot.xml190(para)
msgid ""
"The following command launches the <literal>MyCirrosServer</literal> "
"instance with the <literal>m1.small</literal> flavor (ID of "
"<literal>1</literal>), <literal>cirros-0.3.2-x86_64-uec</literal> image (ID "
"of <literal>397e713c-b95b-4186-ad46-6126863ea0a9</literal>), "
"<literal>default</literal> security group, <literal>KeyPair01</literal> key,"
" and a user data file called <filename>cloudinit.file</filename>:"
msgstr ""
#: ./doc/user-guide/section_cli_nova_boot.xml203(replaceable)
msgid "myCirrosServer"
msgstr ""
#: ./doc/user-guide/section_cli_nova_boot.xml204(para)
msgid ""
"Depending on the parameters that you provide, the command returns a list of "
"server properties."
msgstr ""
#: ./doc/user-guide/section_cli_nova_boot.xml207(para)
msgid ""
"A status of <literal>BUILD</literal> indicates that the instance has "
"started, but is not yet online."
msgstr "L'état <literal>BUILD</literal> indique que l'instance a demarré, mais qu'elle n'est pas en ligne."
#: ./doc/user-guide/section_cli_nova_boot.xml210(para)
msgid ""
"A status of <literal>ACTIVE</literal> indicates that the instance is active."
msgstr "L'état <literal>ACTIVE</literal> indique que l'instance est active."
#: ./doc/user-guide/section_cli_nova_boot.xml242(para)
msgid ""
"Copy the server ID value from the <literal>id</literal> field in the output."
" You use this ID to get details for or delete your server."
msgstr ""
#: ./doc/user-guide/section_cli_nova_boot.xml246(para)
msgid ""
"Copy the administrative password value from the <literal>adminPass</literal>"
" field. You use this value to log in to your server."
msgstr ""
#: ./doc/user-guide/section_cli_nova_boot.xml250(para)
msgid ""
"You can also place arbitrary local files into the instance file system at "
"creation time by using the <option>--file &lt;dst-path=src-path&gt;</option>"
" option. You can store up to five files. For example, if you have a special "
"authorized keys file named <filename>special_authorized_keysfile</filename> "
"that you want to put on the instance rather than using the regular SSH key "
"injection, you can use the <option>--file</option> option as shown in the "
"following example:"
msgstr ""
#: ./doc/user-guide/section_cli_nova_boot.xml267(para)
msgid "Check if the instance is online:"
msgstr "Vérifier que l'instance est en ligne:"
#: ./doc/user-guide/section_cli_nova_boot.xml269(para)
msgid ""
"The list shows the ID, name, status, and private (and if assigned, public) "
"IP addresses for all instances in the project to which you belong:"
msgstr ""
#: ./doc/user-guide/section_cli_nova_boot.xml279(para)
msgid "If the status for the instance is ACTIVE, the instance is online."
msgstr "Si l'état de l'instance est actif, l'instance est en ligne."
#: ./doc/user-guide/section_cli_nova_boot.xml281(para)
msgid ""
"To view the available options for the <placeholder-1/> command, run the "
"following command:"
msgstr "Pour voir les options disponibles pour la <placeholder-1/> commande, exécutez la commande suivante: "
#: ./doc/user-guide/section_cli_nova_boot.xml288(para)
msgid ""
"If you did not provide a key pair, security groups, or rules, you can access"
" the instance only from inside the cloud through VNC. Even pinging the "
"instance is not possible."
msgstr ""
#: ./doc/user-guide/section_cli_nova_baremetal.xml7(title)
msgid "Manage bare-metal nodes"
msgstr ""
#: ./doc/user-guide/section_cli_nova_baremetal.xml8(para)
msgid ""
"The bare-metal driver for OpenStack Compute manages provisioning of physical"
" hardware by using common cloud APIs and tools such as Orchestration (Heat)."
" The use case for this driver is for single tenant clouds such as a high-"
"performance computing cluster or for deploying OpenStack itself."
msgstr ""
#: ./doc/user-guide/section_cli_nova_baremetal.xml12(para)
msgid ""
"If you use the bare-metal driver, you must create a network interface and "
"add it to a bare-metal node. Then, you can launch an instance from a bare-"
"metal image."
msgstr ""
#: ./doc/user-guide/section_cli_nova_baremetal.xml15(para)
msgid ""
"Development efforts are focused on moving the driver out of the Compute code"
" base in the Icehouse release."
msgstr ""
#: ./doc/user-guide/section_cli_nova_baremetal.xml17(para)
msgid ""
"You can list and delete bare-metal nodes. When you delete a node, any "
"associated network interfaces are removed. You can list and remove network "
"interfaces that are associated with a bare-metal node."
msgstr ""
#: ./doc/user-guide/section_cli_nova_baremetal.xml21(title)
msgid "Commands"
msgstr "Commandes"
#: ./doc/user-guide/section_cli_nova_baremetal.xml22(para)
msgid "The following commands can be used to manage bare-metal nodes."
msgstr ""
#: ./doc/user-guide/section_cli_nova_baremetal.xml24(para)
msgid "<placeholder-1/>. Adds a network interface to a bare-metal node."
msgstr ""
#: ./doc/user-guide/section_cli_nova_baremetal.xml28(para)
msgid ""
"<placeholder-1/>. Lists network interfaces associated with a bare-metal "
"node."
msgstr ""
#: ./doc/user-guide/section_cli_nova_baremetal.xml32(para)
msgid "<placeholder-1/>. Removes a network interface from a bare-metal node."
msgstr ""
#: ./doc/user-guide/section_cli_nova_baremetal.xml36(para)
msgid "<placeholder-1/>. Creates a bare-metal node."
msgstr ""
#: ./doc/user-guide/section_cli_nova_baremetal.xml40(para)
msgid ""
"<placeholder-1/>. Removes a bare-metal node and any associated interfaces."
msgstr ""
#: ./doc/user-guide/section_cli_nova_baremetal.xml44(para)
msgid "<placeholder-1/>. Lists available bare-metal nodes."
msgstr ""
#: ./doc/user-guide/section_cli_nova_baremetal.xml48(para)
msgid "<placeholder-1/>. Shows information about a bare-metal node."
msgstr ""
#: ./doc/user-guide/section_cli_nova_baremetal.xml53(title)
msgid "Create a bare-metal node"
msgstr ""
#: ./doc/user-guide/section_cli_nova_baremetal.xml54(para)
msgid ""
"When you create a bare-metal node, your PM address, user name, and password "
"should match those that are configured in your hardware's BIOS/IPMI "
"configuration."
msgstr ""
#: ./doc/user-guide/section_cli_nova_baremetal.xml59(para)
msgid ""
"The following example shows the command and results from creating a node "
"with the PM address <filename>1.2.3.4</filename>, the PM user name "
"<systemitem class=\"username\">ipmi</systemitem>, and password "
"<literal>ipmi</literal>."
msgstr ""
#: ./doc/user-guide/section_cli_nova_baremetal.xml81(title)
msgid "Add a network interface to the node:"
msgstr ""
#: ./doc/user-guide/section_cli_nova_baremetal.xml82(para)
msgid ""
"For each NIC on the node, you must create an interface, specifying the "
"interface's MAC address."
msgstr ""
#: ./doc/user-guide/section_cli_nova_baremetal.xml94(title)
msgid "Launch an instance from a bare-metal image:"
msgstr ""
#: ./doc/user-guide/section_cli_nova_baremetal.xml96(para)
msgid ""
"A bare-metal instance is an instance created directly on a physical machine "
"without any virtualization layer running underneath it. Nova retains power "
"control via IPMI. In some situations, Nova may retain network control via "
"Neutron and OpenFlow."
msgstr ""
#: ./doc/user-guide/section_cli_nova_baremetal.xml109(para)
msgid ""
"Set the <parameter>--availability_zone</parameter> parameter to specify "
"which zone or node to use to start the server. Separate the zone from the "
"host name with a comma. For example:"
msgstr ""
#: ./doc/user-guide/section_cli_nova_baremetal.xml112(replaceable)
msgid "HOST"
msgstr "HOST"
#: ./doc/user-guide/section_cli_nova_baremetal.xml112(replaceable)
msgid "NODE"
msgstr ""
#: ./doc/user-guide/section_cli_nova_baremetal.xml113(para)
msgid ""
"<literal>host</literal> is optional for the "
"<literal>--availability_zone</literal> parameter. You can specify simply "
"<literal>zone:,node</literal>. You must still use the comma."
msgstr ""
#: ./doc/user-guide/section_cli_nova_baremetal.xml120(title)
msgid "List bare-metal nodes and interfaces:"
msgstr ""
#: ./doc/user-guide/section_cli_nova_baremetal.xml122(para)
msgid ""
"Use the <placeholder-1/> command to view all bare-metal nodes and "
"interfaces. When a node is in use, its status includes the UUID of the "
"instance that runs on it:"
msgstr ""
#: ./doc/user-guide/section_cli_nova_baremetal.xml132(title)
msgid "Show details for a bare-metal node:"
msgstr ""
#: ./doc/user-guide/section_cli_nova_baremetal.xml133(para)
msgid ""
"Use the <placeholder-1/> command to view the details for a bare-metal node."
msgstr ""
#: ./doc/user-guide/section_cli_heat.xml8(title)
msgid "Create and manage stacks"
msgstr "Créer et gérer des piles"
@ -1651,10 +2142,6 @@ msgstr "Démarrer une instance en utilisant les noms d'un type d'instance et d'u
msgid "FLAVOR"
msgstr "TYPE D'INSTANCE"
#: ./doc/user-guide/app_cheat_sheet.xml167(replaceable)
msgid "INSTANCE_NAME"
msgstr "NOM_INSTANCE"
#: ./doc/user-guide/app_cheat_sheet.xml173(td)
msgid "Login to instance"
msgstr "Connexion à une instance"
@ -1667,10 +2154,6 @@ msgstr ""
msgid "USER"
msgstr "UTILISATEUR"
#: ./doc/user-guide/app_cheat_sheet.xml176(replaceable)
msgid "SERVER"
msgstr "SERVEUR"
#: ./doc/user-guide/app_cheat_sheet.xml179(para)
msgid ""
"Note, in CirrOS the password for user <literal>cirros</literal> is "
@ -2319,21 +2802,6 @@ msgstr ""
msgid "Rules are automatically enforced as soon as you create or modify them."
msgstr "Les règles sont automatiquement appliquées dès que vous créez ou modifiez."
#: ./doc/user-guide/section_cli_nova_configure_instances.xml62(para)
msgid ""
"Instances that use the default security group cannot, by default, be "
"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 ""
#: ./doc/user-guide/section_cli_nova_configure_instances.xml66(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 "Vous pouvez aussi attribuer une adresse IP flottante à une instance en cours d'exécution pour la rendre accessible depuis l'extérieur du cloud. Voir <xref linkend=\"manage_ip_addresses\"/>."
#: ./doc/user-guide/section_cli_nova_configure_instances.xml71(title)
#: ./doc/user-guide/section_dashboard_access_and_security.xml137(title)
msgid "Add a key pair"
@ -2347,11 +2815,6 @@ msgstr "Vous pouvez générer une paire de clés ou télécharger une clé publi
msgid "To generate a key pair, run the following command:"
msgstr "Pour générer une paire de clés, exécuter la commande suivante:"
#: ./doc/user-guide/section_cli_nova_configure_instances.xml77(replaceable)
#: ./doc/user-guide/section_cli_nova_configure_instances.xml99(replaceable)
msgid "KEY_NAME"
msgstr "KEY_NAME"
#: ./doc/user-guide/section_cli_nova_configure_instances.xml77(replaceable)
#: ./doc/user-guide/section_cli_nova_configure_instances.xml88(replaceable)
msgid "MY_KEY"
@ -2698,6 +3161,108 @@ msgid ""
"instance, it is automatically disassociated from that instance."
msgstr ""
#: ./doc/user-guide/section_cli_nova_startstop.xml7(title)
msgid "Stop and start an instance"
msgstr "Démarrer et arrêter une instance"
#: ./doc/user-guide/section_cli_nova_startstop.xml8(para)
msgid "Use one of the following methods to stop and start an instance."
msgstr "Utilisez une des méthodes suivantes pour arrêter et démarrer une instance :"
#: ./doc/user-guide/section_cli_nova_startstop.xml11(title)
msgid "Pause and unpause an instance"
msgstr ""
#: ./doc/user-guide/section_cli_nova_startstop.xml14(para)
msgid "To pause an instance, run the following command:"
msgstr ""
#: ./doc/user-guide/section_cli_nova_startstop.xml16(para)
msgid ""
"This command stores the state of the VM in RAM. A paused instance continues "
"to run in a frozen state."
msgstr ""
#: ./doc/user-guide/section_cli_nova_startstop.xml18(para)
msgid "To unpause the instance, run the following command:"
msgstr ""
#: ./doc/user-guide/section_cli_nova_startstop.xml24(title)
msgid "Suspend and resume an instance"
msgstr "Suspend and Resume (suspendre et reprendre)"
#: ./doc/user-guide/section_cli_nova_startstop.xml26(para)
msgid ""
"Administrative users might want to suspend an instance if it is infrequently"
" used or to perform system maintenance. When you suspend an instance, its VM"
" state is stored on disk, all memory is written to disk, and the virtual "
"machine is stopped. Suspending an instance is similar to placing a device in"
" hibernation; memory and vCPUs become available to create other instances."
msgstr ""
#: ./doc/user-guide/section_cli_nova_startstop.xml34(para)
msgid ""
"To initiate a hypervisor-level suspend operation, run the following command:"
msgstr ""
#: ./doc/user-guide/section_cli_nova_startstop.xml39(para)
msgid "To resume a suspended instance, run the following command:"
msgstr ""
#: ./doc/user-guide/section_cli_nova_startstop.xml46(title)
msgid "Shelve and unshelve an instance"
msgstr ""
#: ./doc/user-guide/section_cli_nova_startstop.xml47(para)
msgid ""
"Shelving is useful if you have an instance that you are not using, but would"
" like retain in your list of servers. For example, you can stop an instance "
"at the end of a work week, and resume work again at the start of the next "
"week. All associated data and resources are kept; however, anything still in"
" memory is not retained. If a shelved instance is no longer needed, it can "
"also be entirely removed."
msgstr ""
#: ./doc/user-guide/section_cli_nova_startstop.xml52(para)
msgid "You can complete the following shelving tasks:"
msgstr ""
#: ./doc/user-guide/section_cli_nova_startstop.xml54(term)
msgid "Shelve an instance"
msgstr ""
#: ./doc/user-guide/section_cli_nova_startstop.xml55(para)
msgid ""
"Shuts down the instance, and stores it together with associated data and "
"resources (a snapshot is taken if not volume backed). Anything in memory is "
"lost. Use the following command:"
msgstr ""
#: ./doc/user-guide/section_cli_nova_startstop.xml58(replaceable)
#: ./doc/user-guide/section_cli_nova_startstop.xml63(replaceable)
#: ./doc/user-guide/section_cli_nova_startstop.xml70(replaceable)
msgid "SERVERNAME"
msgstr ""
#: ./doc/user-guide/section_cli_nova_startstop.xml61(term)
msgid "Unshelve an instance"
msgstr ""
#: ./doc/user-guide/section_cli_nova_startstop.xml62(para)
msgid "Restores the instance:"
msgstr ""
#: ./doc/user-guide/section_cli_nova_startstop.xml66(term)
msgid "Remove a shelved instance"
msgstr ""
#: ./doc/user-guide/section_cli_nova_startstop.xml67(para)
msgid ""
"Removes the instance from the server; data and resource associations are "
"deleted. If an instance is no longer needed, you can move that instance off "
"the hypervisor in order to minimize resource usage:"
msgstr ""
#: ./doc/user-guide/section_cli_nova_manage_instances.xml7(title)
msgid "Manage instances and hosts"
msgstr "Gérer les instances et les hôtes"
@ -2719,11 +3284,11 @@ msgstr ""
#: ./doc/user-guide/bk-user-guide.xml9(title)
msgid "OpenStack End User Guide"
msgstr "Fin du Guide Utilisateur d'OpenStack"
msgstr "Guide Utilisateur Final d'OpenStack"
#: ./doc/user-guide/bk-user-guide.xml10(titleabbrev)
msgid "End User Guide"
msgstr "Fin du Guide Utilisateur"
msgstr "Guide Utilisateur Final"
#: ./doc/user-guide/bk-user-guide.xml18(orgname)
#: ./doc/user-guide/bk-user-guide.xml23(holder)
@ -2765,7 +3330,7 @@ msgstr ""
#: ./doc/user-guide/bk-user-guide.xml56(date)
msgid "2014-04-17"
msgstr ""
msgstr "2014-04-17"
#: ./doc/user-guide/bk-user-guide.xml60(para)
msgid ""
@ -3216,15 +3781,37 @@ msgstr "Pour des raisons historiques, vous pouvez configurer le disque de config
msgid "If you choose VFAT, the configuration drive is 64MB."
msgstr "Si vous choisissez VFAT, le lecteur de configuration est de 64 Mo."
#: ./doc/user-guide/section_cli_nova_config-drive.xml248(title)
msgid "Configuration drive reference"
msgstr "Référence du lecteur de configuration"
#: ./doc/user-guide/section_cli_nova_terminate.xml7(title)
msgid "Delete an instance"
msgstr "Supprimer une instance "
#: ./doc/user-guide/section_cli_nova_config-drive.xml249(para)
#: ./doc/user-guide/section_cli_nova_terminate.xml8(para)
msgid "When you no longer need an instance, you can delete it."
msgstr "Lorsque vous n'avez plus besoin d'une instance, vous pouvez la supprimer."
#: ./doc/user-guide/section_cli_nova_terminate.xml10(para)
msgid "List all instances:"
msgstr "Listez tous les instances:"
#: ./doc/user-guide/section_cli_nova_terminate.xml20(para)
msgid ""
"The following table shows the configuration options for the configuration "
"drive."
msgstr "Le tableau suivant affiche les options de configuration pour le lecteur de configuration."
"Run the <placeholder-1/> command to delete the instance. The following "
"example shows deletion of the <filename>newServer</filename> instance, which"
" is in <literal>ERROR</literal> state:"
msgstr ""
#: ./doc/user-guide/section_cli_nova_terminate.xml23(para)
msgid "The command does not notify that your server was deleted."
msgstr "Vous ne recevrez aucune notification indiquant la suppression du server."
#: ./doc/user-guide/section_cli_nova_terminate.xml24(para)
msgid ""
"To verify that the server was deleted, run the <placeholder-1/> command:"
msgstr ""
#: ./doc/user-guide/section_cli_nova_terminate.xml32(para)
msgid "The deleted instance does not appear in the list."
msgstr "L'instance qui a été supprimée ne s'affiche pas dans la liste."
#: ./doc/user-guide/section_cli_trove.xml9(title)
msgid "Create and manage databases"
@ -3470,6 +4057,7 @@ msgid ""
msgstr "Vous pouvez maintenant accéder à la nouvelle base de donnée que vous venez juste de créer (myDB) en utilisant les commandes typiques d'accès à une base de donnée. Dans cet exemple MySQL, remplacer <replaceable>ADRESSE_IP</replaceable> avec <literal>172.16.200.2</literal>. "
#: ./doc/user-guide/section_cli_trove.xml239(replaceable)
#: ./doc/user-guide/section_cli_nova_search_ip.xml11(replaceable)
msgid "IP_ADDRESS"
msgstr "ADDRESSE_IP"
@ -4020,10 +4608,6 @@ msgstr "Supprimer un groupe de configuration, en utilisant la commande trove <pl
msgid "Launch and manage instances"
msgstr "Lancer et gérer l'instances"
#: ./doc/user-guide/section_dashboard_launch_instances.xml8(para)
msgid "Instances are virtual machines that run inside the cloud."
msgstr "Les instances sont des machines virtuelles individuelles qui tournent dans le cloud."
#: ./doc/user-guide/section_dashboard_launch_instances.xml10(para)
msgid ""
"You can <link linkend=\"dashboard_launch_instances_from_image\">launch an "
@ -4156,6 +4740,48 @@ msgid ""
" reboot, or terminate it."
msgstr "Vous pouvez redimensionner ou reconstruire une instance. Vous pouvez aussi choisir d'afficher le journal de la console de l'instance. Suivant l'état courant de l'instance, vous pouvez faire une pause, reprendre, suspendre, faire un redémarrage soft ou hard ou mettre fin à l'instance. "
#: ./doc/user-guide/section_cli_nova_userdata.xml7(title)
msgid "Provide user data to instances"
msgstr ""
#: ./doc/user-guide/section_cli_nova_userdata.xml8(para)
msgid ""
"A <glossterm baseform=\"user data\">user data</glossterm> file is a special "
"key in the metadata service that holds a file that cloud-aware applications "
"in the guest instance can access. For example, one application that uses "
"user data is the <link href=\"https://help.ubuntu.com/community/CloudInit"
"\">cloud-init</link> system, which is an open-source package from Ubuntu "
"that is available on various Linux distributions and which handles early "
"initialization of a cloud instance."
msgstr ""
#: ./doc/user-guide/section_cli_nova_userdata.xml15(para)
msgid ""
"You can place user data in a local file and pass it through the <parameter"
">--user-data &lt;user-data-file&gt;</parameter> parameter at instance "
"creation:"
msgstr ""
#: ./doc/user-guide/section_cli_nova_get_console.xml7(title)
msgid "Access an instance through a console"
msgstr ""
#: ./doc/user-guide/section_cli_nova_get_console.xml8(para)
msgid ""
"To access an instance through a VNC console, run the following command:"
msgstr ""
#: ./doc/user-guide/section_cli_nova_get_console.xml10(para)
msgid "The command returns a URL from which you can access your instance:"
msgstr ""
#: ./doc/user-guide/section_cli_nova_get_console.xml16(para)
msgid ""
"To access an instance through a non-VNC console, specify the "
"<parameter>novnc</parameter> parameter instead of the "
"<parameter>xvpvnc</parameter> parameter."
msgstr ""
#: ./doc/user-guide/ch_cli.xml10(title)
msgid "OpenStack command-line clients"
msgstr "Openstack line de commande clients"
@ -4466,6 +5092,31 @@ msgid ""
"load a custom authentication back end:"
msgstr ""
#: ./doc/user-guide/section_cli_nova_search_ip.xml7(title)
msgid "Search for an instance using IP address"
msgstr ""
#: ./doc/user-guide/section_cli_nova_search_ip.xml8(para)
msgid ""
"You can search for an instance using the IP address parameter, "
"<literal>--ip</literal>, with the <placeholder-1/> command."
msgstr ""
#: ./doc/user-guide/section_cli_nova_search_ip.xml11(parameter)
#: ./doc/user-guide/section_cli_nova_search_ip.xml14(parameter)
msgid "ip"
msgstr ""
#: ./doc/user-guide/section_cli_nova_search_ip.xml12(para)
msgid ""
"The following example shows the results of a search on "
"<filename>10.0.0.4</filename>."
msgstr ""
#: ./doc/user-guide/section_cli_nova_search_ip.xml14(replaceable)
msgid "10.0.0.4"
msgstr ""
#: ./doc/user-guide/section_dashboard_stacks.xml7(title)
msgid "Launch and manage stacks"
msgstr "Lancer et gérer des piles"
@ -5171,6 +5822,57 @@ msgstr "HTTP/1.1"
msgid "JSON and XML data serialization formats"
msgstr "Formats de sérialisation des données JSON et XML"
#: ./doc/user-guide/section_cli_nova_resizerebuild.xml7(title)
msgid "Change the size of your server"
msgstr "Changez la taille de votre serveur"
#: ./doc/user-guide/section_cli_nova_resizerebuild.xml8(para)
msgid "You change the size of a server by changing its flavor."
msgstr "Vous changez la taille d'un serveur en changeant son type d'instance."
#: ./doc/user-guide/section_cli_nova_resizerebuild.xml11(para)
msgid ""
"Show information about your server, including its size, which is shown as "
"the value of the flavor property."
msgstr ""
#: ./doc/user-guide/section_cli_nova_resizerebuild.xml44(para)
msgid "The size (flavor) of the server is <literal>m1.small (2)</literal>."
msgstr ""
#: ./doc/user-guide/section_cli_nova_resizerebuild.xml47(para)
msgid "List the available flavors with the following command:"
msgstr ""
#: ./doc/user-guide/section_cli_nova_resizerebuild.xml60(para)
msgid ""
"To resize the server, pass the server ID or name and the new flavor to the "
"<placeholder-1/> command. Include the <literal>--poll</literal> parameter to"
" report the resize progress."
msgstr ""
#: ./doc/user-guide/section_cli_nova_resizerebuild.xml68(para)
msgid "Show the status for your server:"
msgstr "Montrer l'état de votre serveur:"
#: ./doc/user-guide/section_cli_nova_resizerebuild.xml75(para)
msgid "When the resize completes, the status becomes VERIFY_RESIZE."
msgstr ""
#: ./doc/user-guide/section_cli_nova_resizerebuild.xml78(para)
msgid "Confirm the resize:"
msgstr ""
#: ./doc/user-guide/section_cli_nova_resizerebuild.xml80(para)
#: ./doc/user-guide/section_cli_nova_resizerebuild.xml86(para)
msgid "The server status becomes ACTIVE."
msgstr ""
#: ./doc/user-guide/section_cli_nova_resizerebuild.xml83(para)
msgid ""
"If the resize fails or does not work as expected, you can revert the resize:"
msgstr ""
#: ./doc/user-guide/section_cli_swift_howto.xml7(title)
msgid "Manage objects and containers"
msgstr "Gérer les objets et conteneurs"

784
doc/user-guide/locale/ja.po
View File

@ -7,8 +7,8 @@
msgid ""
msgstr ""
"Project-Id-Version: OpenStack Manuals\n"
"POT-Creation-Date: 2014-07-31 21:35+0000\n"
"PO-Revision-Date: 2014-07-30 04:20+0000\n"
"POT-Creation-Date: 2014-08-15 05:33+0000\n"
"PO-Revision-Date: 2014-08-11 17:49+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"
@ -17,6 +17,497 @@ msgstr ""
"Language: ja\n"
"Plural-Forms: nplurals=1; plural=0;\n"
#: ./doc/user-guide/section_cli_nova_reboot.xml7(title)
msgid "Reboot an instance"
msgstr "インスタンスの再起動"
#: ./doc/user-guide/section_cli_nova_reboot.xml8(para)
msgid ""
"You can soft or hard reboot a running instance. A soft reboot attempts a "
"graceful shut down and restart of the instance. A hard reboot power cycles "
"the instance."
msgstr "実行中のインスタンスのソフトリブートまたはハードリブートを行うことができます。ソフトリブートは、グレースフルシャットダウンの後インスタンスの再起動を試行します。ハードリブートは、インスタンスの電源を一旦切って再投入します。"
#: ./doc/user-guide/section_cli_nova_reboot.xml11(para)
msgid "By default, when you reboot a server, it is a soft reboot."
msgstr "デフォルトでは、サーバーをリブートする場合ソフトリブートとなっています。"
#: ./doc/user-guide/section_cli_nova_reboot.xml12(replaceable)
#: ./doc/user-guide/section_cli_nova_reboot.xml14(replaceable)
#: ./doc/user-guide/app_cheat_sheet.xml176(replaceable)
msgid "SERVER"
msgstr "SERVER"
#: ./doc/user-guide/section_cli_nova_reboot.xml13(para)
msgid ""
"To perform a hard reboot, pass the <parameter>--hard</parameter> parameter, "
"as follows:"
msgstr "ハードリブートを実行するには、以下のように <parameter>--hard</parameter> パラメーターを指定します。"
#: ./doc/user-guide/section_cli_nova_boot.xml7(title)
msgid "Launch instances"
msgstr "インスタンスの起動"
#: ./doc/user-guide/section_cli_nova_boot.xml8(para)
#: ./doc/user-guide/section_dashboard_launch_instances.xml8(para)
msgid "Instances are virtual machines that run inside the cloud."
msgstr "インスタンスはクラウド内で動作する仮想マシンです。"
#: ./doc/user-guide/section_cli_nova_boot.xml10(para)
msgid "Before you can launch an instance, gather the following parameters:"
msgstr "インスタンスを起動する前に、以下のパラメーターの情報を集めます。"
#: ./doc/user-guide/section_cli_nova_boot.xml14(para)
msgid ""
"The <emphasis role=\"bold\">instance source</emphasis> can be an image, "
"snapshot, or block storage volume that contains an image or snapshot."
msgstr "<emphasis role=\"bold\">インスタンスのソース</emphasis>は、イメージやスナップショットを含む、イメージ、スナップショット、ブロックストレージです。"
#: ./doc/user-guide/section_cli_nova_boot.xml19(para)
msgid "A <emphasis role=\"bold\">name</emphasis> for your instance."
msgstr "お使いのインスタンスの<emphasis role=\"bold\">名前</emphasis>。"
#: ./doc/user-guide/section_cli_nova_boot.xml22(para)
msgid ""
"The <emphasis role=\"bold\">flavor</emphasis> for your instance, which "
"defines the compute, memory, and storage capacity of nova computing "
"instances. A flavor is an available hardware configuration for a server. It "
"defines the size of a virtual server that can be launched."
msgstr "インスタンスの<emphasis role=\"bold\">フレーバー</emphasis>。nova コンピューティングインスタンスのコンピュート、メモリー、ストレージ容量を定義します。フレーバーは、サーバーが使用可能なハードウェア設定で、起動可能な仮想サーバーのサイズを定義します。"
#: ./doc/user-guide/section_cli_nova_boot.xml30(para)
msgid ""
"Any <emphasis role=\"bold\">user data</emphasis> files. A user data file is "
"a special key in the metadata service that holds a file that cloud-aware "
"applications in the guest instance can access. For example, one application "
"that uses user data is the <link "
"href=\"https://help.ubuntu.com/community/CloudInit\">cloud-init</link> "
"system, which is an open-source package from Ubuntu that is available on "
"various Linux distributions and that handles early initialization of a cloud"
" instance."
msgstr "任意の<emphasis role=\"bold\">ユーザーデータ</emphasis>。ユーザーデータファイルは、メタデータサービス内の特別キーで、ゲストインスタンスにあるクラウド対応アプリケーションがアクセス可能なファイルを保持します。例えば、ユーザーデータを使用するアプリケーションの 1 つは <link href=\"https://help.ubuntu.com/community/CloudInit\">cloud-init</link> システムです。これは、さまざまな Linux ディストリビューションで利用可能な Ubuntu 発祥のオープンソースパッケージです。クラウドインスタンスの初期設定を処理します。"
#: ./doc/user-guide/section_cli_nova_boot.xml43(para)
msgid ""
"Access and security credentials, which include one or both of the following "
"credentials:"
msgstr "アクセス、セキュリティクレデンシャル。以下のクレデンシャルの 1 つまたは両方が含まれます。"
#: ./doc/user-guide/section_cli_nova_boot.xml47(para)
msgid ""
"A <emphasis role=\"bold\">key pair</emphasis> for your instance, which are "
"SSH credentials that are injected into images when they are launched. For "
"the key pair to be successfully injected, the image must contain the "
"<literal>cloud-init</literal> package. Create at least one key pair for each"
" project. If you already have generated a key pair with an external tool, "
"you can import it into OpenStack. You can use the key pair for multiple "
"instances that belong to that project."
msgstr "インスタンスの<emphasis role=\"bold\">キーペア</emphasis>。イメージ起動時にイメージに注入される SSH 認証情報です。キーペアを正常にインジェクトさせるためには、イメージに <literal>cloud-init</literal> パッケージがインストールされている必要があります。プロジェクトごとにキーペアを最低でも 1 つ作成します。すでに外部のツールでキーペアを生成している場合は、OpenStack にそのキーペアをインポートすることができます。プロジェクトに所属する複数のインスタンスに対して、キーペアを使用することができます。"
#: ./doc/user-guide/section_cli_nova_boot.xml61(para)
msgid ""
"A <emphasis role=\"bold\">security group</emphasis> that defines which "
"incoming network traffic is forwarded to instances. Security groups hold a "
"set of firewall policies, known as <emphasis role=\"italic\">security group "
"rules</emphasis>."
msgstr "<emphasis role=\"bold\">セキュリティグループ</emphasis>。どの受信ネットワークトラフィックがインスタンスに転送されるのかを定義します。セキュリティグループは、<emphasis role=\"italic\">セキュリティグループルール</emphasis>と呼ばれるファイアウォールポリシーを保持しています。"
#: ./doc/user-guide/section_cli_nova_boot.xml72(para)
msgid ""
"If needed, you can assign a <emphasis role=\"bold\">floating (public) IP "
"address</emphasis> to a running instance."
msgstr "必要に応じて、実行中のインスタンスに <emphasis role=\"bold\">Floating (パブリック) IP アドレス</emphasis>を割り当てられます。"
#: ./doc/user-guide/section_cli_nova_boot.xml77(para)
msgid ""
"You can also attach a block storage device, or <emphasis "
"role=\"bold\">volume</emphasis>, for persistent storage."
msgstr "永続ストレージ用に、ブロックストレージデバイス、<emphasis role=\"bold\">ボリューム</emphasis>を接続することもできます。"
#: ./doc/user-guide/section_cli_nova_boot.xml83(para)
#: ./doc/user-guide/section_cli_nova_configure_instances.xml62(para)
msgid ""
"Instances that use the default security group cannot, by default, be "
"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 "デフォルトのセキュリティグループを使用するインスタンスは、デフォルトでクラウド外の IP アドレスからアクセスできません。これらの IP アドレスがインスタンスにアクセスしたければ、デフォルトのセキュリティグループのルールを編集する必要があります。"
#: ./doc/user-guide/section_cli_nova_boot.xml88(para)
#: ./doc/user-guide/section_cli_nova_configure_instances.xml66(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 "また、実行中のインスタンスに Flating IP アドレスを割り当て、クラウド外からアクセスできるようにすることも可能です。<xref linkend=\"manage_ip_addresses\"/>を参照してください。"
#: ./doc/user-guide/section_cli_nova_boot.xml92(para)
msgid ""
"After you gather the parameters that you need to launch an instance, you can"
" launch it from an <link linkend=\"launch_from_image\">image</link> or a "
"<link linkend=\"boot_from_volume\">volume</link>. You can launch an instance"
" directly from one of the available OpenStack images or from an image that "
"you have copied to a persistent volume. The OpenStack Image Service provides"
" a pool of images that are accessible to members of different projects."
msgstr "インスタンスを起動するために必要なパラメーターを収集した後、<link linkend=\"launch_from_image\">イメージ</link>や<link linkend=\"boot_from_volume\">ボリューム</link>から起動できます。\n利用可能な OpenStack イメージの 1 つまたは永続ボリュームにコピーしたイメージから直接インスタンスを起動することができます。OpenStack Image Service は、別のプロジェクトのメンバーがアクセスできるイメージのプールを提供します。"
#: ./doc/user-guide/section_cli_nova_boot.xml102(title)
msgid "Gather parameters to launch an instance"
msgstr "インスタンスを起動するためのパラメーター情報の収集"
#: ./doc/user-guide/section_cli_nova_boot.xml104(para)
msgid "Before you begin, source the OpenStack RC file."
msgstr "開始前に OpenStack RC ファイルを読み込みます。"
#: ./doc/user-guide/section_cli_nova_boot.xml107(para)
msgid "List the available flavors:"
msgstr "利用可能なフレーバーを表示します。"
#: ./doc/user-guide/section_cli_nova_boot.xml109(para)
msgid "Note the ID of the flavor that you want to use for your instance:"
msgstr "インスタンスに使用するフレーバーの ID をメモします。"
#: ./doc/user-guide/section_cli_nova_boot.xml122(para)
msgid "List the available images:"
msgstr "利用可能なイメージを表示します。"
#: ./doc/user-guide/section_cli_nova_boot.xml124(para)
msgid "Note the ID of the image from which you want to boot your instance:"
msgstr "インスタンスを起動するイメージの ID をメモします。"
#: ./doc/user-guide/section_cli_nova_boot.xml132(para)
msgid ""
"You can also filter the image list by using <placeholder-1/> to find a "
"specific image, as follows:"
msgstr "以下のように、<placeholder-1/> を使用してイメージ一覧をフィルタリングして、特定のイメージを検索することができます。"
#: ./doc/user-guide/section_cli_nova_boot.xml139(para)
msgid "List the available security groups:"
msgstr "利用可能なセキュリティグループを表示します。"
#: ./doc/user-guide/section_cli_nova_boot.xml141(para)
msgid ""
"If you are an admin user, specify the <option>--all-tenants</option> "
"parameter to list groups for all tenants."
msgstr "管理ユーザーの場合、<option>--all-tenants</option> パラメーターを指定してテナントすべてのグループを表示します。"
#: ./doc/user-guide/section_cli_nova_boot.xml146(para)
msgid ""
"Note the ID of the security group that you want to use for your instance:"
msgstr "インスタンスに使用するセキュリティグループの ID をメモします。"
#: ./doc/user-guide/section_cli_nova_boot.xml152(para)
msgid ""
"If you have not created any security groups, you can assign the instance to "
"only the default security group."
msgstr "セキュリティグループを作成していない場合、Default のセキュリティグループのみにインスタンスを割り当てることができます。"
#: ./doc/user-guide/section_cli_nova_boot.xml155(para)
msgid "You can view rules for a specified security group:"
msgstr "指定したセキュリティグループのルールを表示できます。"
#: ./doc/user-guide/section_cli_nova_boot.xml160(para)
msgid ""
"List the available key pairs and note the name of the key pair that you use "
"for SSH access."
msgstr "利用可能なキーペアを一覧表示し、SSH アクセスに使用するキーペアの名前を記録します。"
#: ./doc/user-guide/section_cli_nova_boot.xml169(title)
msgid "Launch an instance from an image"
msgstr "イメージからのインスタンスの起動"
#: ./doc/user-guide/section_cli_nova_boot.xml172(para)
msgid ""
"After you gather required parameters, run the following command to launch an"
" instance. Specify the server name, flavor ID, and image ID."
msgstr "必要なパラメーターの収集後、インスタンスを起動するために、以下のコマンドを実行します。サーバー名、フレーバー ID、イメージ ID を指定します。"
#: ./doc/user-guide/section_cli_nova_boot.xml175(para)
msgid ""
"Optionally, you can provide a key name for access control and a security "
"group for security. You can also include metadata key and value pairs. For "
"example, you can add a description for your server by providing the "
"<parameter>--meta description=\"My Server\"</parameter> parameter."
msgstr "オプションで、セキュリティとしてアクセス制御やセキュリティグループのキー名を指定することができます。また、メタデータキーや値のペアを含めることも可能です。例えば、<parameter>--meta description=\"My Server\"</parameter> パラメーターを指定してサーバーの説明を追加します。"
#: ./doc/user-guide/section_cli_nova_boot.xml182(para)
msgid ""
"You can pass user data in a local file at instance launch by using the "
"<parameter>--user-data <replaceable>USER-DATA-FILE</replaceable></parameter>"
" parameter."
msgstr "<parameter>--user-data <replaceable>USER-DATA-FILE</replaceable></parameter> パラメーターを使用して、インスタンスの起動時にローカルファイルのユーザーデータを指定することができます。"
#: ./doc/user-guide/section_cli_nova_boot.xml187(replaceable)
msgid "FLAVOR_ID"
msgstr "FLAVOR_ID"
#: ./doc/user-guide/section_cli_nova_boot.xml187(replaceable)
msgid "IMAGE_ID"
msgstr "IMAGE_ID"
#: ./doc/user-guide/section_cli_nova_boot.xml187(replaceable)
#: ./doc/user-guide/section_cli_nova_configure_instances.xml77(replaceable)
#: ./doc/user-guide/section_cli_nova_configure_instances.xml99(replaceable)
msgid "KEY_NAME"
msgstr "KEY_NAME"
#: ./doc/user-guide/section_cli_nova_boot.xml188(replaceable)
msgid "USER_DATA_FILE"
msgstr "USER_DATA_FILE"
#: ./doc/user-guide/section_cli_nova_boot.xml188(replaceable)
msgid "SEC_GROUP"
msgstr "SEC_GROUP"
#: ./doc/user-guide/section_cli_nova_boot.xml188(replaceable)
msgid "KEY=VALUE"
msgstr "KEY=VALUE"
#: ./doc/user-guide/section_cli_nova_boot.xml189(replaceable)
#: ./doc/user-guide/app_cheat_sheet.xml167(replaceable)
#: ./doc/user-guide/section_cli_nova_startstop.xml15(replaceable)
#: ./doc/user-guide/section_cli_nova_startstop.xml19(replaceable)
#: ./doc/user-guide/section_cli_nova_startstop.xml36(replaceable)
#: ./doc/user-guide/section_cli_nova_startstop.xml41(replaceable)
#: ./doc/user-guide/section_cli_nova_get_console.xml9(replaceable)
msgid "INSTANCE_NAME"
msgstr "INSTANCE_NAME"
#: ./doc/user-guide/section_cli_nova_boot.xml190(para)
msgid ""
"The following command launches the <literal>MyCirrosServer</literal> "
"instance with the <literal>m1.small</literal> flavor (ID of "
"<literal>1</literal>), <literal>cirros-0.3.2-x86_64-uec</literal> image (ID "
"of <literal>397e713c-b95b-4186-ad46-6126863ea0a9</literal>), "
"<literal>default</literal> security group, <literal>KeyPair01</literal> key,"
" and a user data file called <filename>cloudinit.file</filename>:"
msgstr "以下のコマンドは、<literal>MyCirrosServer</literal> インスタンスを、<literal>m1.small</literal> フレーバー (ID <literal>1</literal>)、<literal>cirros-0.3.2-x86_64-uec</literal> イメージ (ID <literal>397e713c-b95b-4186-ad46-6126863ea0a9</literal>)、<literal>default</literal> セキュリティグループ、<literal>KeyPair01</literal> キー、<filename>cloudinit.file</filename> という名前のユーザーデータファイルで起動します。"
#: ./doc/user-guide/section_cli_nova_boot.xml203(replaceable)
msgid "myCirrosServer"
msgstr "myCirrosServer"
#: ./doc/user-guide/section_cli_nova_boot.xml204(para)
msgid ""
"Depending on the parameters that you provide, the command returns a list of "
"server properties."
msgstr "指定のパラメーターにより、コマンドはサーバーのプロパティ一覧を返します。"
#: ./doc/user-guide/section_cli_nova_boot.xml207(para)
msgid ""
"A status of <literal>BUILD</literal> indicates that the instance has "
"started, but is not yet online."
msgstr "<literal>BUILD</literal> の状態は、インスタンスが起動しているがオンラインにはなっていないことを示しています。"
#: ./doc/user-guide/section_cli_nova_boot.xml210(para)
msgid ""
"A status of <literal>ACTIVE</literal> indicates that the instance is active."
msgstr "<literal>ACTIVE</literal> の状態は、インスタンスがアクティブであることを示しています。"
#: ./doc/user-guide/section_cli_nova_boot.xml242(para)
msgid ""
"Copy the server ID value from the <literal>id</literal> field in the output."
" You use this ID to get details for or delete your server."
msgstr "出力の <literal>id</literal> フィールドからサーバー ID の値をコピーします。この ID を使用して詳細を取得するか、サーバーを削除します。"
#: ./doc/user-guide/section_cli_nova_boot.xml246(para)
msgid ""
"Copy the administrative password value from the <literal>adminPass</literal>"
" field. You use this value to log in to your server."
msgstr "<literal>adminPass</literal> フィールドから管理者パスワードの値をコピーして、この値を使用してサーバーにログインします。"
#: ./doc/user-guide/section_cli_nova_boot.xml250(para)
msgid ""
"You can also place arbitrary local files into the instance file system at "
"creation time by using the <option>--file &lt;dst-path=src-path&gt;</option>"
" option. You can store up to five files. For example, if you have a special "
"authorized keys file named <filename>special_authorized_keysfile</filename> "
"that you want to put on the instance rather than using the regular SSH key "
"injection, you can use the <option>--file</option> option as shown in the "
"following example:"
msgstr "インスタンス作成時に <option>--file &lt;dst-path=src-path&gt;</option> オプションを用いて、任意のローカルファイルをインスタンスのファイルシステムの中に置けます。5 ファイルまで保存できます。例えば、ある理由により通常の SSH 鍵の注入ではなく、インスタンスに置きたい <filename>special_authorized_keysfile</filename> という名前の特別な認証済み鍵を持っていれば、以下の例で示したように <option>--file</option> オプションを使用できます。"
#: ./doc/user-guide/section_cli_nova_boot.xml267(para)
msgid "Check if the instance is online:"
msgstr "インスタンスがオンラインになっているかどうかをチェックします。"
#: ./doc/user-guide/section_cli_nova_boot.xml269(para)
msgid ""
"The list shows the ID, name, status, and private (and if assigned, public) "
"IP addresses for all instances in the project to which you belong:"
msgstr "覧では、所属するプロジェクトの全インスタンスの ID、名前、状態、プライベート (割り当てられている場合パブリックも) IP アドレスが表示されます。"
#: ./doc/user-guide/section_cli_nova_boot.xml279(para)
msgid "If the status for the instance is ACTIVE, the instance is online."
msgstr "インスタンスの状態が ACTIVE の場合、インスタンスはオンラインです。"
#: ./doc/user-guide/section_cli_nova_boot.xml281(para)
msgid ""
"To view the available options for the <placeholder-1/> command, run the "
"following command:"
msgstr "<placeholder-1/> コマンドで利用可能なオプションを確認するには、以下のコマンドを実行します。"
#: ./doc/user-guide/section_cli_nova_boot.xml288(para)
msgid ""
"If you did not provide a key pair, security groups, or rules, you can access"
" the instance only from inside the cloud through VNC. Even pinging the "
"instance is not possible."
msgstr "キーペア、セキュリティグループ、またはルールを指定しない場合、VNC 経由でクラウド内からしかインスタンスにアクセスすることができません。インスタンスの ping さえも不可となっています。"
#: ./doc/user-guide/section_cli_nova_baremetal.xml7(title)
msgid "Manage bare-metal nodes"
msgstr "ベアメタルノードの管理"
#: ./doc/user-guide/section_cli_nova_baremetal.xml8(para)
msgid ""
"The bare-metal driver for OpenStack Compute manages provisioning of physical"
" hardware by using common cloud APIs and tools such as Orchestration (Heat)."
" The use case for this driver is for single tenant clouds such as a high-"
"performance computing cluster or for deploying OpenStack itself."
msgstr "OpenStack Compute のベアメタルドライバーは、Orchestration (Heat) のような、一般的なクラウド API やツールを使用することにより、物理サーバーへの配備を管理できます。このドライバーのユースケースは、HPC クラスターのような単一テナントクラウドや OpenStack 自身のデプロイメントの用途です。"
#: ./doc/user-guide/section_cli_nova_baremetal.xml12(para)
msgid ""
"If you use the bare-metal driver, you must create a network interface and "
"add it to a bare-metal node. Then, you can launch an instance from a bare-"
"metal image."
msgstr "ベアメタルドライバーを使用する場合、ネットワークインターフェースを作成し、それをベアメタルノードに追加する必要があります。その後、ベアメタルイメージからインスタンスを起動できます。"
#: ./doc/user-guide/section_cli_nova_baremetal.xml15(para)
msgid ""
"Development efforts are focused on moving the driver out of the Compute code"
" base in the Icehouse release."
msgstr "開発は、Icehouse リリースで Compute のコードからこのドライバーを外に出すことに注力しています。"
#: ./doc/user-guide/section_cli_nova_baremetal.xml17(para)
msgid ""
"You can list and delete bare-metal nodes. When you delete a node, any "
"associated network interfaces are removed. You can list and remove network "
"interfaces that are associated with a bare-metal node."
msgstr "ベアメタルノードの一覧表示や削除が可能です。ノードを削除すると、関連付けられているネットワークインターフェースも削除されます。ベアメタルノードに関連付けられているネットワークインターフェースを一覧表示、削除することができます。"
#: ./doc/user-guide/section_cli_nova_baremetal.xml21(title)
msgid "Commands"
msgstr "コマンド"
#: ./doc/user-guide/section_cli_nova_baremetal.xml22(para)
msgid "The following commands can be used to manage bare-metal nodes."
msgstr "以下のコマンドは、ベアメタルノードを管理するために使用できます。"
#: ./doc/user-guide/section_cli_nova_baremetal.xml24(para)
msgid "<placeholder-1/>. Adds a network interface to a bare-metal node."
msgstr "<placeholder-1/>。ベアメタルノードにネットワークインターフェースを追加します。"
#: ./doc/user-guide/section_cli_nova_baremetal.xml28(para)
msgid ""
"<placeholder-1/>. Lists network interfaces associated with a bare-metal "
"node."
msgstr "<placeholder-1/>。ベアメタルノードに関連付けられているネットワークインターフェースを表示します。"
#: ./doc/user-guide/section_cli_nova_baremetal.xml32(para)
msgid "<placeholder-1/>. Removes a network interface from a bare-metal node."
msgstr "<placeholder-1/>。ベアメタルノードからネットワークインターフェースを削除します。"
#: ./doc/user-guide/section_cli_nova_baremetal.xml36(para)
msgid "<placeholder-1/>. Creates a bare-metal node."
msgstr "<placeholder-1/>。ベアメタルノードを作成します。"
#: ./doc/user-guide/section_cli_nova_baremetal.xml40(para)
msgid ""
"<placeholder-1/>. Removes a bare-metal node and any associated interfaces."
msgstr "<placeholder-1/>。ベアメタルノードと関連付けられているインターフェースを削除します。"
#: ./doc/user-guide/section_cli_nova_baremetal.xml44(para)
msgid "<placeholder-1/>. Lists available bare-metal nodes."
msgstr "<placeholder-1/>。使用可能なベアメタルノードを表示します。"
#: ./doc/user-guide/section_cli_nova_baremetal.xml48(para)
msgid "<placeholder-1/>. Shows information about a bare-metal node."
msgstr "<placeholder-1/>。ベアメタルノードの情報を表示します。"
#: ./doc/user-guide/section_cli_nova_baremetal.xml53(title)
msgid "Create a bare-metal node"
msgstr "ベアメタルノードの作成"
#: ./doc/user-guide/section_cli_nova_baremetal.xml54(para)
msgid ""
"When you create a bare-metal node, your PM address, user name, and password "
"should match those that are configured in your hardware's BIOS/IPMI "
"configuration."
msgstr "ベアメタルノードの作成時、物理マシンのアドレス、ユーザー名、パスワードが、ハードウェアの BIOS/IPMI に設定されたものと一致する必要があります。"
#: ./doc/user-guide/section_cli_nova_baremetal.xml59(para)
msgid ""
"The following example shows the command and results from creating a node "
"with the PM address <filename>1.2.3.4</filename>, the PM user name "
"<systemitem class=\"username\">ipmi</systemitem>, and password "
"<literal>ipmi</literal>."
msgstr "以下の例は、物理マシンアドレス <filename>1.2.3.4</filename>、ユーザー名 <systemitem class=\"username\">ipmi</systemitem>、パスワード <literal>ipmi</literal> を持つノードを作成するコマンドと実行結果です。"
#: ./doc/user-guide/section_cli_nova_baremetal.xml81(title)
msgid "Add a network interface to the node:"
msgstr "ベアメタルノードにネットワークインターフェースを追加します。"
#: ./doc/user-guide/section_cli_nova_baremetal.xml82(para)
msgid ""
"For each NIC on the node, you must create an interface, specifying the "
"interface's MAC address."
msgstr "ノードの各 NIC は、インターフェースの MAC アドレスを指定して、インターフェースを作成する必要があります。"
#: ./doc/user-guide/section_cli_nova_baremetal.xml94(title)
msgid "Launch an instance from a bare-metal image:"
msgstr "ベアメタルイメージからインスタンスを起動します。"
#: ./doc/user-guide/section_cli_nova_baremetal.xml96(para)
msgid ""
"A bare-metal instance is an instance created directly on a physical machine "
"without any virtualization layer running underneath it. Nova retains power "
"control via IPMI. In some situations, Nova may retain network control via "
"Neutron and OpenFlow."
msgstr "ベアメタルインスタンスは、物理マシンに直接作成されたインスタンスです。基盤として仮想化レイヤーを持っていません。Nova は IPMI 経由で電源を制御します。いくつかの場合、Nova は Neutron や OpenFlow 経由でネットワークを制御するかもしれません。"
#: ./doc/user-guide/section_cli_nova_baremetal.xml109(para)
msgid ""
"Set the <parameter>--availability_zone</parameter> parameter to specify "
"which zone or node to use to start the server. Separate the zone from the "
"host name with a comma. For example:"
msgstr "<parameter>--availability_zone</parameter> パラメーターを設定して、サーバーを起動するゾーンまたはノードを指定します。ホスト名とゾーンはコンマで区切ります。例えば以下のようになります。"
#: ./doc/user-guide/section_cli_nova_baremetal.xml112(replaceable)
msgid "HOST"
msgstr "HOST"
#: ./doc/user-guide/section_cli_nova_baremetal.xml112(replaceable)
msgid "NODE"
msgstr "NODE"
#: ./doc/user-guide/section_cli_nova_baremetal.xml113(para)
msgid ""
"<literal>host</literal> is optional for the "
"<literal>--availability_zone</literal> parameter. You can specify simply "
"<literal>zone:,node</literal>. You must still use the comma."
msgstr "<literal>host</literal> は <literal>--availability_zone</literal> パラメーターのオプションです。単に <literal>zone:,node</literal> と指定することもできます。コンマを使用することもできます。"
#: ./doc/user-guide/section_cli_nova_baremetal.xml120(title)
msgid "List bare-metal nodes and interfaces:"
msgstr "以下のように、ベアメタルノードとインターフェースを一覧表示します。"
#: ./doc/user-guide/section_cli_nova_baremetal.xml122(para)
msgid ""
"Use the <placeholder-1/> command to view all bare-metal nodes and "
"interfaces. When a node is in use, its status includes the UUID of the "
"instance that runs on it:"
msgstr "すべてのベアメタルノードとインターフェースを表示するために、<placeholder-1/> コマンドを使用します。ノードが使用中の場合、実行されているインスタンスの UUID もステータスに含められます。"
#: ./doc/user-guide/section_cli_nova_baremetal.xml132(title)
msgid "Show details for a bare-metal node:"
msgstr "ベアメタルノードの詳細を表示します。"
#: ./doc/user-guide/section_cli_nova_baremetal.xml133(para)
msgid ""
"Use the <placeholder-1/> command to view the details for a bare-metal node."
msgstr "ベアメタルノードの詳細を表示するために、<placeholder-1/> コマンドを使用します。"
#: ./doc/user-guide/section_cli_heat.xml8(title)
msgid "Create and manage stacks"
msgstr "スタックの管理と作成"
@ -1647,10 +2138,6 @@ msgstr "フレーバーとイメージ名 (名前が一意な場合) を用い
msgid "FLAVOR"
msgstr "FLAVOR"
#: ./doc/user-guide/app_cheat_sheet.xml167(replaceable)
msgid "INSTANCE_NAME"
msgstr "INSTANCE_NAME"
#: ./doc/user-guide/app_cheat_sheet.xml173(td)
msgid "Login to instance"
msgstr "インスタンスへのログイン"
@ -1663,10 +2150,6 @@ msgstr "NETNS_NAME"
msgid "USER"
msgstr "USER"
#: ./doc/user-guide/app_cheat_sheet.xml176(replaceable)
msgid "SERVER"
msgstr "SERVER"
#: ./doc/user-guide/app_cheat_sheet.xml179(para)
msgid ""
"Note, in CirrOS the password for user <literal>cirros</literal> is "
@ -2315,21 +2798,6 @@ msgstr "<emphasis role=\"bold\">仮想マシンでの宛て先ポート番号</e
msgid "Rules are automatically enforced as soon as you create or modify them."
msgstr "ルールは、作成または変更後すぐに自動的に有効になります。"
#: ./doc/user-guide/section_cli_nova_configure_instances.xml62(para)
msgid ""
"Instances that use the default security group cannot, by default, be "
"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 "デフォルトのセキュリティグループを使用するインスタンスは、デフォルトでクラウド外の IP アドレスからアクセスできません。これらの IP アドレスがインスタンスにアクセスしたければ、デフォルトのセキュリティグループのルールを編集する必要があります。"
#: ./doc/user-guide/section_cli_nova_configure_instances.xml66(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 "また、実行中のインスタンスに Flating IP アドレスを割り当て、クラウド外からアクセスできるようにすることも可能です。<xref linkend=\"manage_ip_addresses\"/>を参照してください。"
#: ./doc/user-guide/section_cli_nova_configure_instances.xml71(title)
#: ./doc/user-guide/section_dashboard_access_and_security.xml137(title)
msgid "Add a key pair"
@ -2343,11 +2811,6 @@ msgstr "キーペアの生成や既存の公開鍵のアップロードが可能
msgid "To generate a key pair, run the following command:"
msgstr "キーペアを生成するために、以下のコマンドを実行します。"
#: ./doc/user-guide/section_cli_nova_configure_instances.xml77(replaceable)
#: ./doc/user-guide/section_cli_nova_configure_instances.xml99(replaceable)
msgid "KEY_NAME"
msgstr "KEY_NAME"
#: ./doc/user-guide/section_cli_nova_configure_instances.xml77(replaceable)
#: ./doc/user-guide/section_cli_nova_configure_instances.xml88(replaceable)
msgid "MY_KEY"
@ -2694,6 +3157,108 @@ msgid ""
"instance, it is automatically disassociated from that instance."
msgstr "IP アドレスは、すべてのプロジェクトで利用できるように IP アドレスのプールに戻されます。IP アドレスが実行中のインスタンスにまだ割り当てられていると、そのインスタンスから自動的に割り当て解除されます。"
#: ./doc/user-guide/section_cli_nova_startstop.xml7(title)
msgid "Stop and start an instance"
msgstr "インスタンスの停止と起動"
#: ./doc/user-guide/section_cli_nova_startstop.xml8(para)
msgid "Use one of the following methods to stop and start an instance."
msgstr "以下の手段の 1 つを使用して、インスタンスを停止して起動します。"
#: ./doc/user-guide/section_cli_nova_startstop.xml11(title)
msgid "Pause and unpause an instance"
msgstr "インスタンスの一時停止と一時停止解除"
#: ./doc/user-guide/section_cli_nova_startstop.xml14(para)
msgid "To pause an instance, run the following command:"
msgstr "インスタンスを一時停止するには以下のコマンドを実行します。"
#: ./doc/user-guide/section_cli_nova_startstop.xml16(para)
msgid ""
"This command stores the state of the VM in RAM. A paused instance continues "
"to run in a frozen state."
msgstr "このコマンドは、RAM に仮想マシンの状態を保存します。一時停止となったインスタンスは、一時停止した状態で実行が継続されます。"
#: ./doc/user-guide/section_cli_nova_startstop.xml18(para)
msgid "To unpause the instance, run the following command:"
msgstr "インスタンスを一時停止解除するには以下のコマンドを実行します。"
#: ./doc/user-guide/section_cli_nova_startstop.xml24(title)
msgid "Suspend and resume an instance"
msgstr "インスタンスの休止と再開"
#: ./doc/user-guide/section_cli_nova_startstop.xml26(para)
msgid ""
"Administrative users might want to suspend an instance if it is infrequently"
" used or to perform system maintenance. When you suspend an instance, its VM"
" state is stored on disk, all memory is written to disk, and the virtual "
"machine is stopped. Suspending an instance is similar to placing a device in"
" hibernation; memory and vCPUs become available to create other instances."
msgstr "頻繁でない場合やシステムメンテナンスを実行する場合、管理ユーザーがインスタンスを休止したいかもしれません。インスタンスを休止すると、仮想マシンの状態はディスクに保存され、メモリーはすべてディスクに書き込まれて、仮想マシンが停止します。インスタンスの休止は、デバイスの休止状態に似ていますが、他のインスタンスを作成するために、メモリーや仮想 CPU が解放されます。"
#: ./doc/user-guide/section_cli_nova_startstop.xml34(para)
msgid ""
"To initiate a hypervisor-level suspend operation, run the following command:"
msgstr "ハイパーバイザーレベルの休止操作を開始するには、以下のコマンドを実行します。"
#: ./doc/user-guide/section_cli_nova_startstop.xml39(para)
msgid "To resume a suspended instance, run the following command:"
msgstr "休止中のインスタンスを再開するには以下のコマンドを実行します。"
#: ./doc/user-guide/section_cli_nova_startstop.xml46(title)
msgid "Shelve and unshelve an instance"
msgstr "インスタンスの退避と復元"
#: ./doc/user-guide/section_cli_nova_startstop.xml47(para)
msgid ""
"Shelving is useful if you have an instance that you are not using, but would"
" like retain in your list of servers. For example, you can stop an instance "
"at the end of a work week, and resume work again at the start of the next "
"week. All associated data and resources are kept; however, anything still in"
" memory is not retained. If a shelved instance is no longer needed, it can "
"also be entirely removed."
msgstr "使用していないけれど、サーバー一覧に残しておきたいインスタンスを退避することは有用です。例えば、仕事の週末にインスタンスを停止でき、翌週に再び再開できます。すべての関連するデータとリソースは保持されます。しかしながら、メモリーの内容は失われます。退避したインスタンスが必要なくなれば、完全に削除することもできます。"
#: ./doc/user-guide/section_cli_nova_startstop.xml52(para)
msgid "You can complete the following shelving tasks:"
msgstr "以下の退避作業を実行できます。"
#: ./doc/user-guide/section_cli_nova_startstop.xml54(term)
msgid "Shelve an instance"
msgstr "インスタンスの退避"
#: ./doc/user-guide/section_cli_nova_startstop.xml55(para)
msgid ""
"Shuts down the instance, and stores it together with associated data and "
"resources (a snapshot is taken if not volume backed). Anything in memory is "
"lost. Use the following command:"
msgstr "インスタンスをシャットダウンし、関連するデータとリソース (ボリュームがバックアップされていなければ、スナップショットが取得されます) を一緒に保存します。メモリーの内容はすべて失われます。以下のコマンドを使用します。"
#: ./doc/user-guide/section_cli_nova_startstop.xml58(replaceable)
#: ./doc/user-guide/section_cli_nova_startstop.xml63(replaceable)
#: ./doc/user-guide/section_cli_nova_startstop.xml70(replaceable)
msgid "SERVERNAME"
msgstr "SERVERNAME"
#: ./doc/user-guide/section_cli_nova_startstop.xml61(term)
msgid "Unshelve an instance"
msgstr "インスタンスの復元"
#: ./doc/user-guide/section_cli_nova_startstop.xml62(para)
msgid "Restores the instance:"
msgstr "インスタンスを復元します。"
#: ./doc/user-guide/section_cli_nova_startstop.xml66(term)
msgid "Remove a shelved instance"
msgstr "退避済みインスタンスの削除"
#: ./doc/user-guide/section_cli_nova_startstop.xml67(para)
msgid ""
"Removes the instance from the server; data and resource associations are "
"deleted. If an instance is no longer needed, you can move that instance off "
"the hypervisor in order to minimize resource usage:"
msgstr "サーバーからインスタンスを削除します。データとリソースの関連づけが削除されます。インスタンスが必要なくなれば、リソース使用量を最小化するために、ハイパーバイザーからインスタンスを削除できます。"
#: ./doc/user-guide/section_cli_nova_manage_instances.xml7(title)
msgid "Manage instances and hosts"
msgstr "インスタンスとホストの管理"
@ -3212,15 +3777,37 @@ msgstr "レガシー関連の理由から、config ドライブを ISO 9660 で
msgid "If you choose VFAT, the configuration drive is 64MB."
msgstr "VFAT を選択する場合、コンフィグドライブは 64MB になります。 "
#: ./doc/user-guide/section_cli_nova_config-drive.xml248(title)
msgid "Configuration drive reference"
msgstr "コンフィグドライブのリファレンス"
#: ./doc/user-guide/section_cli_nova_terminate.xml7(title)
msgid "Delete an instance"
msgstr "インスタンスの削除"
#: ./doc/user-guide/section_cli_nova_config-drive.xml249(para)
#: ./doc/user-guide/section_cli_nova_terminate.xml8(para)
msgid "When you no longer need an instance, you can delete it."
msgstr "インスタンスが必要なくなった場合、インスタンスを削除できます。"
#: ./doc/user-guide/section_cli_nova_terminate.xml10(para)
msgid "List all instances:"
msgstr "すべてのインスタンスを一覧表示します。"
#: ./doc/user-guide/section_cli_nova_terminate.xml20(para)
msgid ""
"The following table shows the configuration options for the configuration "
"drive."
msgstr "以下の表はコンフィグドライブの全オプションを示します。"
"Run the <placeholder-1/> command to delete the instance. The following "
"example shows deletion of the <filename>newServer</filename> instance, which"
" is in <literal>ERROR</literal> state:"
msgstr "インスタンスを削除するには <placeholder-1/>コマンドを実行します。以下の例は、<literal>ERROR</literal> 状態の <filename>newServer</filename> インスタンスを削除しています。"
#: ./doc/user-guide/section_cli_nova_terminate.xml23(para)
msgid "The command does not notify that your server was deleted."
msgstr "このコマンドでは、インスタンスの削除に関する通知はありません。"
#: ./doc/user-guide/section_cli_nova_terminate.xml24(para)
msgid ""
"To verify that the server was deleted, run the <placeholder-1/> command:"
msgstr "サーバーが削除されたことを検証するために、<placeholder-1/> コマンドを"
#: ./doc/user-guide/section_cli_nova_terminate.xml32(para)
msgid "The deleted instance does not appear in the list."
msgstr "この一覧には、削除したインスタンスの表示がなくなっています。"
#: ./doc/user-guide/section_cli_trove.xml9(title)
msgid "Create and manage databases"
@ -3466,6 +4053,7 @@ msgid ""
msgstr "これで、一般的なデータベースアクセスコマンドを使用して、作成した新しいデータベース (myDB) にアクセスできます。この MySQL の例では、<replaceable>IP_ADDRESS</replaceable> を <literal>172.16.200.2</literal> に置き換えます。"
#: ./doc/user-guide/section_cli_trove.xml239(replaceable)
#: ./doc/user-guide/section_cli_nova_search_ip.xml11(replaceable)
msgid "IP_ADDRESS"
msgstr "IP_ADDRESS"
@ -4016,10 +4604,6 @@ msgstr "trove <placeholder-1/> コマンドを使用して、設定グループ
msgid "Launch and manage instances"
msgstr "インスタンスの起動と管理"
#: ./doc/user-guide/section_dashboard_launch_instances.xml8(para)
msgid "Instances are virtual machines that run inside the cloud."
msgstr "インスタンスはクラウド内で動作する仮想マシンです。"
#: ./doc/user-guide/section_dashboard_launch_instances.xml10(para)
msgid ""
"You can <link linkend=\"dashboard_launch_instances_from_image\">launch an "
@ -4152,6 +4736,48 @@ msgid ""
" reboot, or terminate it."
msgstr "インスタンスのリサイズや再構築をできます。インスタンスのコンソールログを表示するため、インスタンスやセキュリティグループを編集するためにも選択できます。インスタンスの現在の状態によって、インスタンスを一時停止、再開、サスペンド、ソフトリブート、ハードリブート、終了できます。"
#: ./doc/user-guide/section_cli_nova_userdata.xml7(title)
msgid "Provide user data to instances"
msgstr "インスタンスへのユーザーデータの提供"
#: ./doc/user-guide/section_cli_nova_userdata.xml8(para)
msgid ""
"A <glossterm baseform=\"user data\">user data</glossterm> file is a special "
"key in the metadata service that holds a file that cloud-aware applications "
"in the guest instance can access. For example, one application that uses "
"user data is the <link href=\"https://help.ubuntu.com/community/CloudInit"
"\">cloud-init</link> system, which is an open-source package from Ubuntu "
"that is available on various Linux distributions and which handles early "
"initialization of a cloud instance."
msgstr "<glossterm baseform=\"user data\">ユーザーデータ</glossterm>ファイルは、メタデータサービス内の特別キーで、ゲストインスタンスにあるクラウド対応アプリケーションがアクセス可能なファイルを保持します。例えば、ユーザーデータを使用するアプリケーションの 1 つは <link href=\"https://help.ubuntu.com/community/CloudInit\">cloud-init</link> システムです。これは、さまざまな Linux ディストリビューションで利用可能な Ubuntu 発祥のオープンソースパッケージです。クラウドインスタンスの初期設定を処理します。"
#: ./doc/user-guide/section_cli_nova_userdata.xml15(para)
msgid ""
"You can place user data in a local file and pass it through the <parameter"
">--user-data &lt;user-data-file&gt;</parameter> parameter at instance "
"creation:"
msgstr "インスタンス作成時に <parameter>--user-data &lt;user-data-file&gt;</parameter> パラメーターを使用して、ローカルファイルのユーザーデータを渡すことができます。"
#: ./doc/user-guide/section_cli_nova_get_console.xml7(title)
msgid "Access an instance through a console"
msgstr "コンソール経由のインスタンスへのアクセス"
#: ./doc/user-guide/section_cli_nova_get_console.xml8(para)
msgid ""
"To access an instance through a VNC console, run the following command:"
msgstr "VNC コンソール経由でインスタンスにアクセスするには、以下のコマンドを実行します。"
#: ./doc/user-guide/section_cli_nova_get_console.xml10(para)
msgid "The command returns a URL from which you can access your instance:"
msgstr "このコマンドは、インスタンスにアクセスするための URL を返します。"
#: ./doc/user-guide/section_cli_nova_get_console.xml16(para)
msgid ""
"To access an instance through a non-VNC console, specify the "
"<parameter>novnc</parameter> parameter instead of the "
"<parameter>xvpvnc</parameter> parameter."
msgstr "VNC 以外のコンソール経由でインスタンスにアクセスするために、<parameter>xvpvnc</parameter> パラメーターの代わりに <parameter>novnc</parameter> パラメーターを指定します。"
#: ./doc/user-guide/ch_cli.xml10(title)
msgid "OpenStack command-line clients"
msgstr "OpenStack コマンドラインクライアント"
@ -4462,6 +5088,31 @@ msgid ""
"load a custom authentication back end:"
msgstr "<literal>OS_AUTH_SYSTEM</literal> 環境変数を設定した場合、カスタム認証バックエンドを読み込む必要があるかどうかを判断するために、Python スクリプトでこの変数を確認します。"
#: ./doc/user-guide/section_cli_nova_search_ip.xml7(title)
msgid "Search for an instance using IP address"
msgstr "IP アドレスを用いたインスタンスの検索"
#: ./doc/user-guide/section_cli_nova_search_ip.xml8(para)
msgid ""
"You can search for an instance using the IP address parameter, "
"<literal>--ip</literal>, with the <placeholder-1/> command."
msgstr "<placeholder-1/> コマンドの <literal>--ip</literal> オプションを用いて、IP アドレスをパラメーターにして、インスタンスを検索できます。"
#: ./doc/user-guide/section_cli_nova_search_ip.xml11(parameter)
#: ./doc/user-guide/section_cli_nova_search_ip.xml14(parameter)
msgid "ip"
msgstr "ip"
#: ./doc/user-guide/section_cli_nova_search_ip.xml12(para)
msgid ""
"The following example shows the results of a search on "
"<filename>10.0.0.4</filename>."
msgstr "以下の例は、<filename>10.0.0.4</filename> の検索結果です。"
#: ./doc/user-guide/section_cli_nova_search_ip.xml14(replaceable)
msgid "10.0.0.4"
msgstr "10.0.0.4"
#: ./doc/user-guide/section_dashboard_stacks.xml7(title)
msgid "Launch and manage stacks"
msgstr "スタックの起動と管理"
@ -5167,6 +5818,57 @@ msgstr "HTTP/1.1"
msgid "JSON and XML data serialization formats"
msgstr "JSON および XML データシリアライズ形式"
#: ./doc/user-guide/section_cli_nova_resizerebuild.xml7(title)
msgid "Change the size of your server"
msgstr "サーバーの大きさの変更"
#: ./doc/user-guide/section_cli_nova_resizerebuild.xml8(para)
msgid "You change the size of a server by changing its flavor."
msgstr "フレーバーを変更することでサーバーの大きさを変更します。"
#: ./doc/user-guide/section_cli_nova_resizerebuild.xml11(para)
msgid ""
"Show information about your server, including its size, which is shown as "
"the value of the flavor property."
msgstr "サーバーの情報 (大きさなど) を表示します。フレーバーのプロパティ値として表示されます。"
#: ./doc/user-guide/section_cli_nova_resizerebuild.xml44(para)
msgid "The size (flavor) of the server is <literal>m1.small (2)</literal>."
msgstr "サーバーの大きさ (フレーバー) は <literal>m1.small (2)</literal> です。"
#: ./doc/user-guide/section_cli_nova_resizerebuild.xml47(para)
msgid "List the available flavors with the following command:"
msgstr "以下のコマンドを用いて、利用可能なフレーバーを一覧表示します。"
#: ./doc/user-guide/section_cli_nova_resizerebuild.xml60(para)
msgid ""
"To resize the server, pass the server ID or name and the new flavor to the "
"<placeholder-1/> command. Include the <literal>--poll</literal> parameter to"
" report the resize progress."
msgstr "サーバーのリサイズには、サーバー ID または名前、新しいフレーバーを <placeholder-1/> コマンドに指定します。リサイズの進捗をレポートさせるには、<literal>--poll</literal> パラメーターを含めます。"
#: ./doc/user-guide/section_cli_nova_resizerebuild.xml68(para)
msgid "Show the status for your server:"
msgstr "サーバーの状態を表示します。"
#: ./doc/user-guide/section_cli_nova_resizerebuild.xml75(para)
msgid "When the resize completes, the status becomes VERIFY_RESIZE."
msgstr "リサイズが完了すると、状態が VERIFY_RESIZE に変わります。"
#: ./doc/user-guide/section_cli_nova_resizerebuild.xml78(para)
msgid "Confirm the resize:"
msgstr "リサイズされたことを確認します。"
#: ./doc/user-guide/section_cli_nova_resizerebuild.xml80(para)
#: ./doc/user-guide/section_cli_nova_resizerebuild.xml86(para)
msgid "The server status becomes ACTIVE."
msgstr "サーバーの状態が ACTIVE に変わります。"
#: ./doc/user-guide/section_cli_nova_resizerebuild.xml83(para)
msgid ""
"If the resize fails or does not work as expected, you can revert the resize:"
msgstr "リサイズに失敗した場合や予想通りにリサイズが行われなかった場合、リサイズを元に戻すことができます。"
#: ./doc/user-guide/section_cli_swift_howto.xml7(title)
msgid "Manage objects and containers"
msgstr "オブジェクトとコンテナーの管理"

572
doc/user-guide/locale/user-guide.pot
View File

@ -1,7 +1,7 @@
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"POT-Creation-Date: 2014-07-28 06:08+0000\n"
"POT-Creation-Date: 2014-08-15 06:09+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"
@ -9,6 +9,350 @@ msgstr ""
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#: ./doc/user-guide/section_cli_nova_reboot.xml:7(title)
msgid "Reboot an instance"
msgstr ""
#: ./doc/user-guide/section_cli_nova_reboot.xml:8(para)
msgid "You can soft or hard reboot a running instance. A soft reboot attempts a graceful shut down and restart of the instance. A hard reboot power cycles the instance."
msgstr ""
#: ./doc/user-guide/section_cli_nova_reboot.xml:11(para)
msgid "By default, when you reboot a server, it is a soft reboot."
msgstr ""
#: ./doc/user-guide/section_cli_nova_reboot.xml:12(replaceable) ./doc/user-guide/section_cli_nova_reboot.xml:14(replaceable) ./doc/user-guide/app_cheat_sheet.xml:176(replaceable)
msgid "SERVER"
msgstr ""
#: ./doc/user-guide/section_cli_nova_reboot.xml:13(para)
msgid "To perform a hard reboot, pass the <parameter>--hard</parameter> parameter, as follows:"
msgstr ""
#: ./doc/user-guide/section_cli_nova_boot.xml:7(title)
msgid "Launch instances"
msgstr ""
#: ./doc/user-guide/section_cli_nova_boot.xml:8(para) ./doc/user-guide/section_dashboard_launch_instances.xml:8(para)
msgid "Instances are virtual machines that run inside the cloud."
msgstr ""
#: ./doc/user-guide/section_cli_nova_boot.xml:10(para)
msgid "Before you can launch an instance, gather the following parameters:"
msgstr ""
#: ./doc/user-guide/section_cli_nova_boot.xml:14(para)
msgid "The <emphasis role=\"bold\">instance source</emphasis> can be an image, snapshot, or block storage volume that contains an image or snapshot."
msgstr ""
#: ./doc/user-guide/section_cli_nova_boot.xml:19(para)
msgid "A <emphasis role=\"bold\">name</emphasis> for your instance."
msgstr ""
#: ./doc/user-guide/section_cli_nova_boot.xml:22(para)
msgid "The <emphasis role=\"bold\">flavor</emphasis> for your instance, which defines the compute, memory, and storage capacity of nova computing instances. A flavor is an available hardware configuration for a server. It defines the size of a virtual server that can be launched."
msgstr ""
#: ./doc/user-guide/section_cli_nova_boot.xml:30(para)
msgid "Any <emphasis role=\"bold\">user data</emphasis> files. A user data file is a special key in the metadata service that holds a file that cloud-aware applications in the guest instance can access. For example, one application that uses user data is the <link href=\"https://help.ubuntu.com/community/CloudInit\">cloud-init</link> system, which is an open-source package from Ubuntu that is available on various Linux distributions and that handles early initialization of a cloud instance."
msgstr ""
#: ./doc/user-guide/section_cli_nova_boot.xml:43(para)
msgid "Access and security credentials, which include one or both of the following credentials:"
msgstr ""
#: ./doc/user-guide/section_cli_nova_boot.xml:47(para)
msgid "A <emphasis role=\"bold\">key pair</emphasis> for your instance, which are SSH credentials that are injected into images when they are launched. For the key pair to be successfully injected, the image must contain the <literal>cloud-init</literal> package. Create at least one key pair for each project. If you already have generated a key pair with an external tool, you can import it into OpenStack. You can use the key pair for multiple instances that belong to that project."
msgstr ""
#: ./doc/user-guide/section_cli_nova_boot.xml:61(para)
msgid "A <emphasis role=\"bold\">security group</emphasis> that defines which incoming network traffic is forwarded to instances. Security groups hold a set of firewall policies, known as <emphasis role=\"italic\">security group rules</emphasis>."
msgstr ""
#: ./doc/user-guide/section_cli_nova_boot.xml:72(para)
msgid "If needed, you can assign a <emphasis role=\"bold\">floating (public) IP address</emphasis> to a running instance."
msgstr ""
#: ./doc/user-guide/section_cli_nova_boot.xml:77(para)
msgid "You can also attach a block storage device, or <emphasis role=\"bold\">volume</emphasis>, for persistent storage."
msgstr ""
#: ./doc/user-guide/section_cli_nova_boot.xml:83(para) ./doc/user-guide/section_cli_nova_configure_instances.xml:62(para)
msgid "Instances that use the default security group cannot, by default, be 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 ""
#: ./doc/user-guide/section_cli_nova_boot.xml:88(para) ./doc/user-guide/section_cli_nova_configure_instances.xml:66(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 ""
#: ./doc/user-guide/section_cli_nova_boot.xml:92(para)
msgid "After you gather the parameters that you need to launch an instance, you can launch it from an <link linkend=\"launch_from_image\">image</link> or a <link linkend=\"boot_from_volume\">volume</link>. You can launch an instance directly from one of the available OpenStack images or from an image that you have copied to a persistent volume. The OpenStack Image Service provides a pool of images that are accessible to members of different projects."
msgstr ""
#: ./doc/user-guide/section_cli_nova_boot.xml:102(title)
msgid "Gather parameters to launch an instance"
msgstr ""
#: ./doc/user-guide/section_cli_nova_boot.xml:104(para)
msgid "Before you begin, source the OpenStack RC file."
msgstr ""
#: ./doc/user-guide/section_cli_nova_boot.xml:107(para)
msgid "List the available flavors:"
msgstr ""
#: ./doc/user-guide/section_cli_nova_boot.xml:109(para)
msgid "Note the ID of the flavor that you want to use for your instance:"
msgstr ""
#: ./doc/user-guide/section_cli_nova_boot.xml:122(para)
msgid "List the available images:"
msgstr ""
#: ./doc/user-guide/section_cli_nova_boot.xml:124(para)
msgid "Note the ID of the image from which you want to boot your instance:"
msgstr ""
#: ./doc/user-guide/section_cli_nova_boot.xml:132(para)
msgid "You can also filter the image list by using <placeholder-1/> to find a specific image, as follows:"
msgstr ""
#: ./doc/user-guide/section_cli_nova_boot.xml:139(para)
msgid "List the available security groups:"
msgstr ""
#: ./doc/user-guide/section_cli_nova_boot.xml:141(para)
msgid "If you are an admin user, specify the <option>--all-tenants</option> parameter to list groups for all tenants."
msgstr ""
#: ./doc/user-guide/section_cli_nova_boot.xml:146(para)
msgid "Note the ID of the security group that you want to use for your instance:"
msgstr ""
#: ./doc/user-guide/section_cli_nova_boot.xml:152(para)
msgid "If you have not created any security groups, you can assign the instance to only the default security group."
msgstr ""
#: ./doc/user-guide/section_cli_nova_boot.xml:155(para)
msgid "You can view rules for a specified security group:"
msgstr ""
#: ./doc/user-guide/section_cli_nova_boot.xml:160(para)
msgid "List the available key pairs and note the name of the key pair that you use for SSH access."
msgstr ""
#: ./doc/user-guide/section_cli_nova_boot.xml:169(title)
msgid "Launch an instance from an image"
msgstr ""
#: ./doc/user-guide/section_cli_nova_boot.xml:172(para)
msgid "After you gather required parameters, run the following command to launch an instance. Specify the server name, flavor ID, and image ID."
msgstr ""
#: ./doc/user-guide/section_cli_nova_boot.xml:175(para)
msgid "Optionally, you can provide a key name for access control and a security group for security. You can also include metadata key and value pairs. For example, you can add a description for your server by providing the <parameter>--meta description=\"My Server\"</parameter> parameter."
msgstr ""
#: ./doc/user-guide/section_cli_nova_boot.xml:182(para)
msgid "You can pass user data in a local file at instance launch by using the <parameter>--user-data <replaceable>USER-DATA-FILE</replaceable></parameter> parameter."
msgstr ""
#: ./doc/user-guide/section_cli_nova_boot.xml:187(replaceable)
msgid "FLAVOR_ID"
msgstr ""
#: ./doc/user-guide/section_cli_nova_boot.xml:187(replaceable)
msgid "IMAGE_ID"
msgstr ""
#: ./doc/user-guide/section_cli_nova_boot.xml:187(replaceable) ./doc/user-guide/section_cli_nova_configure_instances.xml:77(replaceable) ./doc/user-guide/section_cli_nova_configure_instances.xml:99(replaceable)
msgid "KEY_NAME"
msgstr ""
#: ./doc/user-guide/section_cli_nova_boot.xml:188(replaceable)
msgid "USER_DATA_FILE"
msgstr ""
#: ./doc/user-guide/section_cli_nova_boot.xml:188(replaceable)
msgid "SEC_GROUP"
msgstr ""
#: ./doc/user-guide/section_cli_nova_boot.xml:188(replaceable)
msgid "KEY=VALUE"
msgstr ""
#: ./doc/user-guide/section_cli_nova_boot.xml:189(replaceable) ./doc/user-guide/app_cheat_sheet.xml:167(replaceable) ./doc/user-guide/section_cli_nova_startstop.xml:15(replaceable) ./doc/user-guide/section_cli_nova_startstop.xml:19(replaceable) ./doc/user-guide/section_cli_nova_startstop.xml:36(replaceable) ./doc/user-guide/section_cli_nova_startstop.xml:41(replaceable) ./doc/user-guide/section_cli_nova_get_console.xml:9(replaceable)
msgid "INSTANCE_NAME"
msgstr ""
#: ./doc/user-guide/section_cli_nova_boot.xml:190(para)
msgid "The following command launches the <literal>MyCirrosServer</literal> instance with the <literal>m1.small</literal> flavor (ID of <literal>1</literal>), <literal>cirros-0.3.2-x86_64-uec</literal> image (ID of <literal>397e713c-b95b-4186-ad46-6126863ea0a9</literal>), <literal>default</literal> security group, <literal>KeyPair01</literal> key, and a user data file called <filename>cloudinit.file</filename>:"
msgstr ""
#: ./doc/user-guide/section_cli_nova_boot.xml:203(replaceable)
msgid "myCirrosServer"
msgstr ""
#: ./doc/user-guide/section_cli_nova_boot.xml:204(para)
msgid "Depending on the parameters that you provide, the command returns a list of server properties."
msgstr ""
#: ./doc/user-guide/section_cli_nova_boot.xml:207(para)
msgid "A status of <literal>BUILD</literal> indicates that the instance has started, but is not yet online."
msgstr ""
#: ./doc/user-guide/section_cli_nova_boot.xml:210(para)
msgid "A status of <literal>ACTIVE</literal> indicates that the instance is active."
msgstr ""
#: ./doc/user-guide/section_cli_nova_boot.xml:242(para)
msgid "Copy the server ID value from the <literal>id</literal> field in the output. You use this ID to get details for or delete your server."
msgstr ""
#: ./doc/user-guide/section_cli_nova_boot.xml:246(para)
msgid "Copy the administrative password value from the <literal>adminPass</literal> field. You use this value to log in to your server."
msgstr ""
#: ./doc/user-guide/section_cli_nova_boot.xml:250(para)
msgid "You can also place arbitrary local files into the instance file system at creation time by using the <option>--file &lt;dst-path=src-path&gt;</option> option. You can store up to five files. For example, if you have a special authorized keys file named <filename>special_authorized_keysfile</filename> that you want to put on the instance rather than using the regular SSH key injection, you can use the <option>--file</option> option as shown in the following example:"
msgstr ""
#: ./doc/user-guide/section_cli_nova_boot.xml:267(para)
msgid "Check if the instance is online:"
msgstr ""
#: ./doc/user-guide/section_cli_nova_boot.xml:269(para)
msgid "The list shows the ID, name, status, and private (and if assigned, public) IP addresses for all instances in the project to which you belong:"
msgstr ""
#: ./doc/user-guide/section_cli_nova_boot.xml:279(para)
msgid "If the status for the instance is ACTIVE, the instance is online."
msgstr ""
#: ./doc/user-guide/section_cli_nova_boot.xml:281(para)
msgid "To view the available options for the <placeholder-1/> command, run the following command:"
msgstr ""
#: ./doc/user-guide/section_cli_nova_boot.xml:288(para)
msgid "If you did not provide a key pair, security groups, or rules, you can access the instance only from inside the cloud through VNC. Even pinging the instance is not possible."
msgstr ""
#: ./doc/user-guide/section_cli_nova_baremetal.xml:7(title)
msgid "Manage bare-metal nodes"
msgstr ""
#: ./doc/user-guide/section_cli_nova_baremetal.xml:8(para)
msgid "The bare-metal driver for OpenStack Compute manages provisioning of physical hardware by using common cloud APIs and tools such as Orchestration (Heat). The use case for this driver is for single tenant clouds such as a high-performance computing cluster or for deploying OpenStack itself."
msgstr ""
#: ./doc/user-guide/section_cli_nova_baremetal.xml:12(para)
msgid "If you use the bare-metal driver, you must create a network interface and add it to a bare-metal node. Then, you can launch an instance from a bare-metal image."
msgstr ""
#: ./doc/user-guide/section_cli_nova_baremetal.xml:15(para)
msgid "Development efforts are focused on moving the driver out of the Compute code base in the Icehouse release."
msgstr ""
#: ./doc/user-guide/section_cli_nova_baremetal.xml:17(para)
msgid "You can list and delete bare-metal nodes. When you delete a node, any associated network interfaces are removed. You can list and remove network interfaces that are associated with a bare-metal node."
msgstr ""
#: ./doc/user-guide/section_cli_nova_baremetal.xml:21(title)
msgid "Commands"
msgstr ""
#: ./doc/user-guide/section_cli_nova_baremetal.xml:22(para)
msgid "The following commands can be used to manage bare-metal nodes."
msgstr ""
#: ./doc/user-guide/section_cli_nova_baremetal.xml:24(para)
msgid "<placeholder-1/>. Adds a network interface to a bare-metal node."
msgstr ""
#: ./doc/user-guide/section_cli_nova_baremetal.xml:28(para)
msgid "<placeholder-1/>. Lists network interfaces associated with a bare-metal node."
msgstr ""
#: ./doc/user-guide/section_cli_nova_baremetal.xml:32(para)
msgid "<placeholder-1/>. Removes a network interface from a bare-metal node."
msgstr ""
#: ./doc/user-guide/section_cli_nova_baremetal.xml:36(para)
msgid "<placeholder-1/>. Creates a bare-metal node."
msgstr ""
#: ./doc/user-guide/section_cli_nova_baremetal.xml:40(para)
msgid "<placeholder-1/>. Removes a bare-metal node and any associated interfaces."
msgstr ""
#: ./doc/user-guide/section_cli_nova_baremetal.xml:44(para)
msgid "<placeholder-1/>. Lists available bare-metal nodes."
msgstr ""
#: ./doc/user-guide/section_cli_nova_baremetal.xml:48(para)
msgid "<placeholder-1/>. Shows information about a bare-metal node."
msgstr ""
#: ./doc/user-guide/section_cli_nova_baremetal.xml:53(title)
msgid "Create a bare-metal node"
msgstr ""
#: ./doc/user-guide/section_cli_nova_baremetal.xml:54(para)
msgid "When you create a bare-metal node, your PM address, user name, and password should match those that are configured in your hardware's BIOS/IPMI configuration."
msgstr ""
#: ./doc/user-guide/section_cli_nova_baremetal.xml:59(para)
msgid "The following example shows the command and results from creating a node with the PM address <filename>1.2.3.4</filename>, the PM user name <systemitem class=\"username\">ipmi</systemitem>, and password <literal>ipmi</literal>."
msgstr ""
#: ./doc/user-guide/section_cli_nova_baremetal.xml:81(title)
msgid "Add a network interface to the node:"
msgstr ""
#: ./doc/user-guide/section_cli_nova_baremetal.xml:82(para)
msgid "For each NIC on the node, you must create an interface, specifying the interface's MAC address."
msgstr ""
#: ./doc/user-guide/section_cli_nova_baremetal.xml:94(title)
msgid "Launch an instance from a bare-metal image:"
msgstr ""
#: ./doc/user-guide/section_cli_nova_baremetal.xml:96(para)
msgid "A bare-metal instance is an instance created directly on a physical machine without any virtualization layer running underneath it. Nova retains power control via IPMI. In some situations, Nova may retain network control via Neutron and OpenFlow."
msgstr ""
#: ./doc/user-guide/section_cli_nova_baremetal.xml:109(para)
msgid "Set the <parameter>--availability_zone</parameter> parameter to specify which zone or node to use to start the server. Separate the zone from the host name with a comma. For example:"
msgstr ""
#: ./doc/user-guide/section_cli_nova_baremetal.xml:112(replaceable)
msgid "HOST"
msgstr ""
#: ./doc/user-guide/section_cli_nova_baremetal.xml:112(replaceable)
msgid "NODE"
msgstr ""
#: ./doc/user-guide/section_cli_nova_baremetal.xml:113(para)
msgid "<literal>host</literal> is optional for the <literal>--availability_zone</literal> parameter. You can specify simply <literal>zone:,node</literal>. You must still use the comma."
msgstr ""
#: ./doc/user-guide/section_cli_nova_baremetal.xml:120(title)
msgid "List bare-metal nodes and interfaces:"
msgstr ""
#: ./doc/user-guide/section_cli_nova_baremetal.xml:122(para)
msgid "Use the <placeholder-1/> command to view all bare-metal nodes and interfaces. When a node is in use, its status includes the UUID of the instance that runs on it:"
msgstr ""
#: ./doc/user-guide/section_cli_nova_baremetal.xml:132(title)
msgid "Show details for a bare-metal node:"
msgstr ""
#: ./doc/user-guide/section_cli_nova_baremetal.xml:133(para)
msgid "Use the <placeholder-1/> command to view the details for a bare-metal node."
msgstr ""
#: ./doc/user-guide/section_cli_heat.xml:8(title)
msgid "Create and manage stacks"
msgstr ""
@ -1261,10 +1605,6 @@ msgstr ""
msgid "FLAVOR"
msgstr ""
#: ./doc/user-guide/app_cheat_sheet.xml:167(replaceable)
msgid "INSTANCE_NAME"
msgstr ""
#: ./doc/user-guide/app_cheat_sheet.xml:173(td)
msgid "Login to instance"
msgstr ""
@ -1277,10 +1617,6 @@ msgstr ""
msgid "USER"
msgstr ""
#: ./doc/user-guide/app_cheat_sheet.xml:176(replaceable)
msgid "SERVER"
msgstr ""
#: ./doc/user-guide/app_cheat_sheet.xml:179(para)
msgid "Note, in CirrOS the password for user <literal>cirros</literal> is \"cubswin:)\" without the quotes."
msgstr ""
@ -1777,14 +2113,6 @@ msgstr ""
msgid "Rules are automatically enforced as soon as you create or modify them."
msgstr ""
#: ./doc/user-guide/section_cli_nova_configure_instances.xml:62(para)
msgid "Instances that use the default security group cannot, by default, be 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 ""
#: ./doc/user-guide/section_cli_nova_configure_instances.xml:66(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 ""
#: ./doc/user-guide/section_cli_nova_configure_instances.xml:71(title) ./doc/user-guide/section_dashboard_access_and_security.xml:137(title)
msgid "Add a key pair"
msgstr ""
@ -1797,10 +2125,6 @@ msgstr ""
msgid "To generate a key pair, run the following command:"
msgstr ""
#: ./doc/user-guide/section_cli_nova_configure_instances.xml:77(replaceable) ./doc/user-guide/section_cli_nova_configure_instances.xml:99(replaceable)
msgid "KEY_NAME"
msgstr ""
#: ./doc/user-guide/section_cli_nova_configure_instances.xml:77(replaceable) ./doc/user-guide/section_cli_nova_configure_instances.xml:88(replaceable)
msgid "MY_KEY"
msgstr ""
@ -2045,6 +2369,86 @@ msgstr ""
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 ""
#: ./doc/user-guide/section_cli_nova_startstop.xml:7(title)
msgid "Stop and start an instance"
msgstr ""
#: ./doc/user-guide/section_cli_nova_startstop.xml:8(para)
msgid "Use one of the following methods to stop and start an instance."
msgstr ""
#: ./doc/user-guide/section_cli_nova_startstop.xml:11(title)
msgid "Pause and unpause an instance"
msgstr ""
#: ./doc/user-guide/section_cli_nova_startstop.xml:14(para)
msgid "To pause an instance, run the following command:"
msgstr ""
#: ./doc/user-guide/section_cli_nova_startstop.xml:16(para)
msgid "This command stores the state of the VM in RAM. A paused instance continues to run in a frozen state."
msgstr ""
#: ./doc/user-guide/section_cli_nova_startstop.xml:18(para)
msgid "To unpause the instance, run the following command:"
msgstr ""
#: ./doc/user-guide/section_cli_nova_startstop.xml:24(title)
msgid "Suspend and resume an instance"
msgstr ""
#: ./doc/user-guide/section_cli_nova_startstop.xml:26(para)
msgid "Administrative users might want to suspend an instance if it is infrequently used or to perform system maintenance. When you suspend an instance, its VM state is stored on disk, all memory is written to disk, and the virtual machine is stopped. Suspending an instance is similar to placing a device in hibernation; memory and vCPUs become available to create other instances."
msgstr ""
#: ./doc/user-guide/section_cli_nova_startstop.xml:34(para)
msgid "To initiate a hypervisor-level suspend operation, run the following command:"
msgstr ""
#: ./doc/user-guide/section_cli_nova_startstop.xml:39(para)
msgid "To resume a suspended instance, run the following command:"
msgstr ""
#: ./doc/user-guide/section_cli_nova_startstop.xml:46(title)
msgid "Shelve and unshelve an instance"
msgstr ""
#: ./doc/user-guide/section_cli_nova_startstop.xml:47(para)
msgid "Shelving is useful if you have an instance that you are not using, but would like retain in your list of servers. For example, you can stop an instance at the end of a work week, and resume work again at the start of the next week. All associated data and resources are kept; however, anything still in memory is not retained. If a shelved instance is no longer needed, it can also be entirely removed."
msgstr ""
#: ./doc/user-guide/section_cli_nova_startstop.xml:52(para)
msgid "You can complete the following shelving tasks:"
msgstr ""
#: ./doc/user-guide/section_cli_nova_startstop.xml:54(term)
msgid "Shelve an instance"
msgstr ""
#: ./doc/user-guide/section_cli_nova_startstop.xml:55(para)
msgid "Shuts down the instance, and stores it together with associated data and resources (a snapshot is taken if not volume backed). Anything in memory is lost. Use the following command:"
msgstr ""
#: ./doc/user-guide/section_cli_nova_startstop.xml:58(replaceable) ./doc/user-guide/section_cli_nova_startstop.xml:63(replaceable) ./doc/user-guide/section_cli_nova_startstop.xml:70(replaceable)
msgid "SERVERNAME"
msgstr ""
#: ./doc/user-guide/section_cli_nova_startstop.xml:61(term)
msgid "Unshelve an instance"
msgstr ""
#: ./doc/user-guide/section_cli_nova_startstop.xml:62(para)
msgid "Restores the instance:"
msgstr ""
#: ./doc/user-guide/section_cli_nova_startstop.xml:66(term)
msgid "Remove a shelved instance"
msgstr ""
#: ./doc/user-guide/section_cli_nova_startstop.xml:67(para)
msgid "Removes the instance from the server; data and resource associations are deleted. If an instance is no longer needed, you can move that instance off the hypervisor in order to minimize resource usage:"
msgstr ""
#: ./doc/user-guide/section_cli_nova_manage_instances.xml:7(title)
msgid "Manage instances and hosts"
msgstr ""
@ -2413,12 +2817,32 @@ msgstr ""
msgid "If you choose VFAT, the configuration drive is 64MB."
msgstr ""
#: ./doc/user-guide/section_cli_nova_config-drive.xml:248(title)
msgid "Configuration drive reference"
#: ./doc/user-guide/section_cli_nova_terminate.xml:7(title)
msgid "Delete an instance"
msgstr ""
#: ./doc/user-guide/section_cli_nova_config-drive.xml:249(para)
msgid "The following table shows the configuration options for the configuration drive."
#: ./doc/user-guide/section_cli_nova_terminate.xml:8(para)
msgid "When you no longer need an instance, you can delete it."
msgstr ""
#: ./doc/user-guide/section_cli_nova_terminate.xml:10(para)
msgid "List all instances:"
msgstr ""
#: ./doc/user-guide/section_cli_nova_terminate.xml:20(para)
msgid "Run the <placeholder-1/> command to delete the instance. The following example shows deletion of the <filename>newServer</filename> instance, which is in <literal>ERROR</literal> state:"
msgstr ""
#: ./doc/user-guide/section_cli_nova_terminate.xml:23(para)
msgid "The command does not notify that your server was deleted."
msgstr ""
#: ./doc/user-guide/section_cli_nova_terminate.xml:24(para)
msgid "To verify that the server was deleted, run the <placeholder-1/> command:"
msgstr ""
#: ./doc/user-guide/section_cli_nova_terminate.xml:32(para)
msgid "The deleted instance does not appear in the list."
msgstr ""
#: ./doc/user-guide/section_cli_trove.xml:9(title)
@ -2617,7 +3041,7 @@ msgstr ""
msgid "You can now access the new database you just created (myDB) by using typical database access commands. In this MySQL example, replace <replaceable>IP_ADDRESS</replaceable> with <literal>172.16.200.2</literal>."
msgstr ""
#: ./doc/user-guide/section_cli_trove.xml:239(replaceable)
#: ./doc/user-guide/section_cli_trove.xml:239(replaceable) ./doc/user-guide/section_cli_nova_search_ip.xml:11(replaceable)
msgid "IP_ADDRESS"
msgstr ""
@ -3013,10 +3437,6 @@ msgstr ""
msgid "Launch and manage instances"
msgstr ""
#: ./doc/user-guide/section_dashboard_launch_instances.xml:8(para)
msgid "Instances are virtual machines that run inside the cloud."
msgstr ""
#: ./doc/user-guide/section_dashboard_launch_instances.xml:10(para)
msgid "You can <link linkend=\"dashboard_launch_instances_from_image\">launch an instance</link> from the following sources:"
msgstr ""
@ -3113,6 +3533,34 @@ msgstr ""
msgid "You can resize or rebuild an instance. You can also choose to view the instance console log, edit instance or the security groups. Depending on the current state of the instance, you can pause, resume, suspend, soft or hard reboot, or terminate it."
msgstr ""
#: ./doc/user-guide/section_cli_nova_userdata.xml:7(title)
msgid "Provide user data to instances"
msgstr ""
#: ./doc/user-guide/section_cli_nova_userdata.xml:8(para)
msgid "A <glossterm baseform=\"user data\">user data</glossterm> file is a special key in the metadata service that holds a file that cloud-aware applications in the guest instance can access. For example, one application that uses user data is the <link href=\"https://help.ubuntu.com/community/CloudInit\">cloud-init</link> system, which is an open-source package from Ubuntu that is available on various Linux distributions and which handles early initialization of a cloud instance."
msgstr ""
#: ./doc/user-guide/section_cli_nova_userdata.xml:15(para)
msgid "You can place user data in a local file and pass it through the <parameter>--user-data &lt;user-data-file&gt;</parameter> parameter at instance creation:"
msgstr ""
#: ./doc/user-guide/section_cli_nova_get_console.xml:7(title)
msgid "Access an instance through a console"
msgstr ""
#: ./doc/user-guide/section_cli_nova_get_console.xml:8(para)
msgid "To access an instance through a VNC console, run the following command:"
msgstr ""
#: ./doc/user-guide/section_cli_nova_get_console.xml:10(para)
msgid "The command returns a URL from which you can access your instance:"
msgstr ""
#: ./doc/user-guide/section_cli_nova_get_console.xml:16(para)
msgid "To access an instance through a non-VNC console, specify the <parameter>novnc</parameter> parameter instead of the <parameter>xvpvnc</parameter> parameter."
msgstr ""
#: ./doc/user-guide/ch_cli.xml:10(title)
msgid "OpenStack command-line clients"
msgstr ""
@ -3361,6 +3809,26 @@ msgstr ""
msgid "If you set the <literal>OS_AUTH_SYSTEM</literal> environment variable, check for this variable in your Python script to determine whether you need to load a custom authentication back end:"
msgstr ""
#: ./doc/user-guide/section_cli_nova_search_ip.xml:7(title)
msgid "Search for an instance using IP address"
msgstr ""
#: ./doc/user-guide/section_cli_nova_search_ip.xml:8(para)
msgid "You can search for an instance using the IP address parameter, <literal>--ip</literal>, with the <placeholder-1/> command."
msgstr ""
#: ./doc/user-guide/section_cli_nova_search_ip.xml:11(parameter) ./doc/user-guide/section_cli_nova_search_ip.xml:14(parameter)
msgid "ip"
msgstr ""
#: ./doc/user-guide/section_cli_nova_search_ip.xml:12(para)
msgid "The following example shows the results of a search on <filename>10.0.0.4</filename>."
msgstr ""
#: ./doc/user-guide/section_cli_nova_search_ip.xml:14(replaceable)
msgid "10.0.0.4"
msgstr ""
#: ./doc/user-guide/section_dashboard_stacks.xml:7(title)
msgid "Launch and manage stacks"
msgstr ""
@ -3905,6 +4373,50 @@ msgstr ""
msgid "JSON and XML data serialization formats"
msgstr ""
#: ./doc/user-guide/section_cli_nova_resizerebuild.xml:7(title)
msgid "Change the size of your server"
msgstr ""
#: ./doc/user-guide/section_cli_nova_resizerebuild.xml:8(para)
msgid "You change the size of a server by changing its flavor."
msgstr ""
#: ./doc/user-guide/section_cli_nova_resizerebuild.xml:11(para)
msgid "Show information about your server, including its size, which is shown as the value of the flavor property."
msgstr ""
#: ./doc/user-guide/section_cli_nova_resizerebuild.xml:44(para)
msgid "The size (flavor) of the server is <literal>m1.small (2)</literal>."
msgstr ""
#: ./doc/user-guide/section_cli_nova_resizerebuild.xml:47(para)
msgid "List the available flavors with the following command:"
msgstr ""
#: ./doc/user-guide/section_cli_nova_resizerebuild.xml:60(para)
msgid "To resize the server, pass the server ID or name and the new flavor to the <placeholder-1/> command. Include the <literal>--poll</literal> parameter to report the resize progress."
msgstr ""
#: ./doc/user-guide/section_cli_nova_resizerebuild.xml:68(para)
msgid "Show the status for your server:"
msgstr ""
#: ./doc/user-guide/section_cli_nova_resizerebuild.xml:75(para)
msgid "When the resize completes, the status becomes VERIFY_RESIZE."
msgstr ""
#: ./doc/user-guide/section_cli_nova_resizerebuild.xml:78(para)
msgid "Confirm the resize:"
msgstr ""
#: ./doc/user-guide/section_cli_nova_resizerebuild.xml:80(para) ./doc/user-guide/section_cli_nova_resizerebuild.xml:86(para)
msgid "The server status becomes ACTIVE."
msgstr ""
#: ./doc/user-guide/section_cli_nova_resizerebuild.xml:83(para)
msgid "If the resize fails or does not work as expected, you can revert the resize:"
msgstr ""
#: ./doc/user-guide/section_cli_swift_howto.xml:7(title)
msgid "Manage objects and containers"
msgstr ""