diff --git a/doc/admin-guide-cloud/source/locale/admin-guide-cloud.pot b/doc/admin-guide-cloud/source/locale/admin-guide-cloud.pot index 1bae8f758b..cb19b41f7b 100644 --- a/doc/admin-guide-cloud/source/locale/admin-guide-cloud.pot +++ b/doc/admin-guide-cloud/source/locale/admin-guide-cloud.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Cloud Administrator Guide 0.9\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2015-12-24 06:12+0000\n" +"POT-Creation-Date: 2015-12-30 06:12+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -4712,71 +4712,71 @@ msgstr "" msgid "Define roles or policies in the :file:`policy.json` file::" msgstr "" -#: ../compute-images-instances.rst:242 +#: ../compute-images-instances.rst:243 msgid "" "For each parameter, use ``\"rule:restricted\"`` to restrict access to all " "users or ``\"role:admin\"`` to limit access to administrator roles. For " "example::" msgstr "" -#: ../compute-images-instances.rst:249 +#: ../compute-images-instances.rst:250 msgid "" "Define which roles or policies can manage which properties in a property " "protections configuration file. For example::" msgstr "" -#: ../compute-images-instances.rst:270 +#: ../compute-images-instances.rst:271 msgid "A value of ``@`` allows the corresponding operation for a property." msgstr "" -#: ../compute-images-instances.rst:272 +#: ../compute-images-instances.rst:273 msgid "A value of ``!`` disallows the corresponding operation for a property." msgstr "" -#: ../compute-images-instances.rst:275 +#: ../compute-images-instances.rst:276 msgid "" "In the :file:`glance-api.conf` file, define the location of a property " "protections configuration file::" msgstr "" -#: ../compute-images-instances.rst:280 +#: ../compute-images-instances.rst:281 msgid "" "This file contains the rules for property protections and the roles and " "policies associated with it." msgstr "" -#: ../compute-images-instances.rst:283 +#: ../compute-images-instances.rst:284 msgid "By default, property protections are not enforced." msgstr "" -#: ../compute-images-instances.rst:285 +#: ../compute-images-instances.rst:286 msgid "" "If you specify a file name value and the file is not found, the `glance-api` " "service does not start." msgstr "" -#: ../compute-images-instances.rst:288 ../compute-images-instances.rst:298 +#: ../compute-images-instances.rst:289 ../compute-images-instances.rst:299 msgid "" "To view a sample configuration file, see `glance-api.conf `__." msgstr "" -#: ../compute-images-instances.rst:291 +#: ../compute-images-instances.rst:292 msgid "" "Optionally, in the :file:`glance-api.conf` file, specify whether roles or " "policies are used in the property protections configuration file::" msgstr "" -#: ../compute-images-instances.rst:296 +#: ../compute-images-instances.rst:297 msgid "The default is ``roles``." msgstr "" -#: ../compute-images-instances.rst:302 +#: ../compute-images-instances.rst:303 msgid "Image download: how it works" msgstr "" -#: ../compute-images-instances.rst:303 +#: ../compute-images-instances.rst:304 msgid "" "Prior to starting a virtual machine, the virtual machine image used must be " "transferred to the compute node from the Image service. How this works can " @@ -4784,7 +4784,7 @@ msgid "" "service." msgstr "" -#: ../compute-images-instances.rst:308 +#: ../compute-images-instances.rst:309 msgid "" "Typically, the Compute service will use the image identifier passed to it by " "the scheduler service and request the image from the Image API. Though " @@ -4795,7 +4795,7 @@ msgid "" "the compute node." msgstr "" -#: ../compute-images-instances.rst:316 +#: ../compute-images-instances.rst:317 msgid "" "It is possible to set up the Object Storage node on a separate network, and " "still allow image traffic to flow between the Compute and Object Storage " @@ -4803,7 +4803,7 @@ msgid "" "configuration to allow block storage traffic to reach the Compute node." msgstr "" -#: ../compute-images-instances.rst:322 +#: ../compute-images-instances.rst:323 msgid "" "Certain back ends support a more direct method, where on request the Image " "service will return a URL that can be used to download the image directly " @@ -4813,7 +4813,7 @@ msgid "" "conf` file on compute nodes." msgstr "" -#: ../compute-images-instances.rst:329 +#: ../compute-images-instances.rst:330 msgid "" "Compute nodes also implement caching of images, meaning that if an image has " "been used before it won't necessarily be downloaded every time. Information " @@ -4822,11 +4822,11 @@ msgid "" "reference/content/>`__." msgstr "" -#: ../compute-images-instances.rst:336 +#: ../compute-images-instances.rst:337 msgid "Instance building blocks" msgstr "" -#: ../compute-images-instances.rst:338 +#: ../compute-images-instances.rst:339 msgid "" "In OpenStack, the base operating system is usually copied from an image " "stored in the OpenStack Image service. This results in an ephemeral instance " @@ -4834,7 +4834,7 @@ msgid "" "shutdown." msgstr "" -#: ../compute-images-instances.rst:343 +#: ../compute-images-instances.rst:344 msgid "" "You can also put an operating system on a persistent volume in Compute or " "the Block Storage volume system. This gives a more traditional, persistent " @@ -4844,46 +4844,46 @@ msgstr "" # #-#-#-#-# compute_arch.pot (Cloud Administrator Guide 0.9) #-#-#-#-# # #-#-#-#-# compute-images-instances.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -#: ../compute-images-instances.rst:364 ../compute_arch.rst:259 +#: ../compute-images-instances.rst:365 ../compute_arch.rst:265 msgid "The displayed image attributes are:" msgstr "" -#: ../compute-images-instances.rst:367 +#: ../compute-images-instances.rst:368 msgid "Automatically generated UUID of the image." msgstr "" # #-#-#-#-# compute_arch.pot (Cloud Administrator Guide 0.9) #-#-#-#-# # #-#-#-#-# compute-images-instances.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -#: ../compute-images-instances.rst:367 ../compute_arch.rst:262 +#: ../compute-images-instances.rst:368 ../compute_arch.rst:268 msgid "``ID``" msgstr "" -#: ../compute-images-instances.rst:370 +#: ../compute-images-instances.rst:371 msgid "Free form, human-readable name for the image." msgstr "" # #-#-#-#-# compute_arch.pot (Cloud Administrator Guide 0.9) #-#-#-#-# # #-#-#-#-# compute-images-instances.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -#: ../compute-images-instances.rst:370 ../compute_arch.rst:265 +#: ../compute-images-instances.rst:371 ../compute_arch.rst:271 msgid "``Name``" msgstr "" # #-#-#-#-# compute_arch.pot (Cloud Administrator Guide 0.9) #-#-#-#-# # #-#-#-#-# compute-images-instances.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -#: ../compute-images-instances.rst:373 ../compute_arch.rst:268 +#: ../compute-images-instances.rst:374 ../compute_arch.rst:274 msgid "" "The status of the image. Images marked ``ACTIVE`` are available for use." msgstr "" # #-#-#-#-# compute_arch.pot (Cloud Administrator Guide 0.9) #-#-#-#-# # #-#-#-#-# compute-images-instances.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -#: ../compute-images-instances.rst:374 ../compute_arch.rst:269 +#: ../compute-images-instances.rst:375 ../compute_arch.rst:275 msgid "``Status``" msgstr "" # #-#-#-#-# compute_arch.pot (Cloud Administrator Guide 0.9) #-#-#-#-# # #-#-#-#-# compute-images-instances.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -#: ../compute-images-instances.rst:377 ../compute_arch.rst:272 +#: ../compute-images-instances.rst:378 ../compute_arch.rst:278 msgid "" "For images that are created as snapshots of running instances, this is the " "UUID of the instance the snapshot derives from. For uploaded images, this " @@ -4892,21 +4892,21 @@ msgstr "" # #-#-#-#-# compute_arch.pot (Cloud Administrator Guide 0.9) #-#-#-#-# # #-#-#-#-# compute-images-instances.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -#: ../compute-images-instances.rst:379 ../compute_arch.rst:274 +#: ../compute-images-instances.rst:380 ../compute_arch.rst:280 msgid "``Server``" msgstr "" -#: ../compute-images-instances.rst:381 +#: ../compute-images-instances.rst:382 msgid "" "Virtual hardware templates are called ``flavors``. The default installation " "provides five predefined flavors." msgstr "" -#: ../compute-images-instances.rst:384 +#: ../compute-images-instances.rst:385 msgid "For a list of flavors that are available on your system, run:" msgstr "" -#: ../compute-images-instances.rst:399 +#: ../compute-images-instances.rst:400 msgid "" "By default, administrative users can configure the flavors. You can change " "this behavior by redefining the access controls for ``compute_extension:" @@ -4914,18 +4914,18 @@ msgid "" "server." msgstr "" -#: ../compute-images-instances.rst:406 +#: ../compute-images-instances.rst:407 msgid "Instance management tools" msgstr "" -#: ../compute-images-instances.rst:408 +#: ../compute-images-instances.rst:409 msgid "" "OpenStack provides command-line, web interface, and API-based instance " "management tools. Third-party management tools are also available, using " "either the native API or the provided EC2-compatible API." msgstr "" -#: ../compute-images-instances.rst:412 +#: ../compute-images-instances.rst:413 msgid "" "The OpenStack python-novaclient package provides a basic command-line " "utility, which uses the :command:`nova` command. This is available as a " @@ -4933,18 +4933,18 @@ msgid "" "version using the pip python package installer:" msgstr "" -#: ../compute-images-instances.rst:421 +#: ../compute-images-instances.rst:422 msgid "" "For more information about python-novaclient and other command-line tools, " "see the `OpenStack End User Guide `__." msgstr "" -#: ../compute-images-instances.rst:427 +#: ../compute-images-instances.rst:428 msgid "Control where instances run" msgstr "" -#: ../compute-images-instances.rst:428 +#: ../compute-images-instances.rst:429 msgid "" "The `OpenStack Configuration Reference `__ provides detailed information on controlling " @@ -4953,7 +4953,7 @@ msgid "" "performance inter-instance communications." msgstr "" -#: ../compute-images-instances.rst:435 +#: ../compute-images-instances.rst:436 msgid "" "Administrative users can specify which compute node their instances run on. " "To do this, specify the ``--availability-zone AVAILABILITY_ZONE:" @@ -8973,14 +8973,21 @@ msgid "" "openstack.org/liberty/config-reference/content/ configuring-ec2-api.html>`__." msgstr "" -#: ../compute_arch.rst:202 +#: ../compute_arch.rst:204 +msgid "" +"Nova in tree EC2-compatible API is deprecated. The `ec2-api project `_ is working on implementation of " +"EC2 API." +msgstr "" + +#: ../compute_arch.rst:208 msgid "" "Numerous third-party tools and language-specific SDKs can be used to " "interact with OpenStack clouds, using both native and compatibility APIs. " "Some of the more popular third-party tools are:" msgstr "" -#: ../compute_arch.rst:207 +#: ../compute_arch.rst:213 msgid "" "A popular open source command-line tool for interacting with the EC2 API. " "This is convenient for multi-cloud environments where EC2 is the common API, " @@ -8989,11 +8996,11 @@ msgid "" "eucalyptus/4.1.2/index.html#shared/euca2ools_section.html>`__." msgstr "" -#: ../compute_arch.rst:211 +#: ../compute_arch.rst:217 msgid "Euca2ools" msgstr "" -#: ../compute_arch.rst:214 +#: ../compute_arch.rst:220 msgid "" "A Firefox browser add-on that provides a graphical interface to many popular " "public and private cloud technologies, including OpenStack. For more " @@ -9001,48 +9008,48 @@ msgid "" ">`__." msgstr "" -#: ../compute_arch.rst:217 +#: ../compute_arch.rst:223 msgid "Hybridfox" msgstr "" -#: ../compute_arch.rst:220 +#: ../compute_arch.rst:226 msgid "" "A Python library for interacting with Amazon Web Services. It can be used to " "access OpenStack through the EC2 compatibility API. For more information, " "see the `boto project page on GitHub `__." msgstr "" -#: ../compute_arch.rst:223 +#: ../compute_arch.rst:229 msgid "boto" msgstr "" -#: ../compute_arch.rst:226 +#: ../compute_arch.rst:232 msgid "" "A Ruby cloud services library. It provides methods for interacting with a " "large number of cloud and virtualization platforms, including OpenStack. For " "more information, see the `fog site `__." msgstr "" -#: ../compute_arch.rst:229 +#: ../compute_arch.rst:235 msgid "fog" msgstr "" -#: ../compute_arch.rst:232 +#: ../compute_arch.rst:238 msgid "" "A PHP SDK designed to work with most OpenStack- based cloud deployments, as " "well as Rackspace public cloud. For more information, see the `php-opencloud " "site `__." msgstr "" -#: ../compute_arch.rst:235 +#: ../compute_arch.rst:241 msgid "php-opencloud" msgstr "" -#: ../compute_arch.rst:238 +#: ../compute_arch.rst:244 msgid "Building blocks" msgstr "" -#: ../compute_arch.rst:239 +#: ../compute_arch.rst:245 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 " @@ -9055,15 +9062,15 @@ msgid "" "list of available images on your system, run::" msgstr "" -#: ../compute_arch.rst:262 +#: ../compute_arch.rst:268 msgid "Automatically generated UUID of the image" msgstr "" -#: ../compute_arch.rst:265 +#: ../compute_arch.rst:271 msgid "Free form, human-readable name for image" msgstr "" -#: ../compute_arch.rst:276 +#: ../compute_arch.rst:282 msgid "" "Virtual hardware templates are called ``flavors``. The default installation " "provides five flavors. By default, these are configurable by admin users, " @@ -9072,32 +9079,32 @@ msgid "" "``compute-api`` server." msgstr "" -#: ../compute_arch.rst:282 +#: ../compute_arch.rst:288 msgid "For a list of flavors that are available on your system::" msgstr "" -#: ../compute_arch.rst:296 +#: ../compute_arch.rst:302 msgid "Compute service architecture" msgstr "" -#: ../compute_arch.rst:297 +#: ../compute_arch.rst:303 msgid "" "These basic categories describe the service architecture and information " "about the cloud controller." msgstr "" -#: ../compute_arch.rst:300 +#: ../compute_arch.rst:306 msgid "**API server**" msgstr "" -#: ../compute_arch.rst:302 +#: ../compute_arch.rst:308 msgid "" "At the heart of the cloud framework is an API server, which makes command " "and control of the hypervisor, storage, and networking programmatically " "available to users." msgstr "" -#: ../compute_arch.rst:306 +#: ../compute_arch.rst:312 msgid "" "The API endpoints are basic HTTP web services which handle authentication, " "authorization, and basic command and control functions using various API " @@ -9107,11 +9114,11 @@ msgid "" "in." msgstr "" -#: ../compute_arch.rst:313 +#: ../compute_arch.rst:319 msgid "**Message queue**" msgstr "" -#: ../compute_arch.rst:315 +#: ../compute_arch.rst:321 msgid "" "A messaging queue brokers the interaction between compute nodes " "(processing), the networking controllers (software which controls network " @@ -9121,7 +9128,7 @@ msgid "" "through multiple API endpoints." msgstr "" -#: ../compute_arch.rst:322 +#: ../compute_arch.rst:328 msgid "" "A typical message passing event begins with the API server receiving a " "request from a user. The API server authenticates the user and ensures that " @@ -9136,60 +9143,60 @@ msgid "" "necessary during the process." msgstr "" -#: ../compute_arch.rst:335 +#: ../compute_arch.rst:341 msgid "**Compute worker**" msgstr "" -#: ../compute_arch.rst:337 +#: ../compute_arch.rst:343 msgid "" "Compute workers manage computing instances on host machines. The API " "dispatches commands to compute workers to complete these tasks:" msgstr "" -#: ../compute_arch.rst:340 +#: ../compute_arch.rst:346 msgid "Run instances" msgstr "" -#: ../compute_arch.rst:342 +#: ../compute_arch.rst:348 msgid "Terminate instances" msgstr "" -#: ../compute_arch.rst:344 +#: ../compute_arch.rst:350 msgid "Reboot instances" msgstr "" -#: ../compute_arch.rst:346 +#: ../compute_arch.rst:352 msgid "Attach volumes" msgstr "" -#: ../compute_arch.rst:348 +#: ../compute_arch.rst:354 msgid "Detach volumes" msgstr "" -#: ../compute_arch.rst:350 +#: ../compute_arch.rst:356 msgid "Get console output" msgstr "" -#: ../compute_arch.rst:352 +#: ../compute_arch.rst:358 msgid "**Network Controller**" msgstr "" -#: ../compute_arch.rst:354 +#: ../compute_arch.rst:360 msgid "" "The Network Controller manages the networking resources on host machines. " "The API server dispatches commands through the message queue, which are " "subsequently processed by Network Controllers. Specific operations include:" msgstr "" -#: ../compute_arch.rst:359 +#: ../compute_arch.rst:365 msgid "Allocating fixed IP addresses" msgstr "" -#: ../compute_arch.rst:361 +#: ../compute_arch.rst:367 msgid "Configuring VLANs for projects" msgstr "" -#: ../compute_arch.rst:363 +#: ../compute_arch.rst:369 msgid "Configuring networks for compute nodes" msgstr "" @@ -9774,7 +9781,7 @@ msgstr "" msgid "Name you want to use for this data store." msgstr "" -#: ../database.rst:111 ../database.rst:154 ../database.rst:171 +#: ../database.rst:111 ../database.rst:154 ../database.rst:177 msgid "``mysql``" msgstr "" @@ -9790,7 +9797,7 @@ msgid "" "explicitly request a specific version." msgstr "" -#: ../database.rst:118 ../database.rst:183 +#: ../database.rst:118 ../database.rst:189 msgid "``\"\"``" msgstr "" @@ -9800,7 +9807,7 @@ msgid "" "string." msgstr "" -#: ../database.rst:125 ../database.rst:196 +#: ../database.rst:125 ../database.rst:202 msgid "Example:" msgstr "" @@ -9849,54 +9856,78 @@ msgid "" msgstr "" #: ../database.rst:165 -msgid "mysql" -msgstr "" - -#: ../database.rst:166 -msgid "redis" -msgstr "" - -#: ../database.rst:167 -msgid "mongodb" -msgstr "" - -#: ../database.rst:168 msgid "cassandra" msgstr "" -#: ../database.rst:169 +#: ../database.rst:166 msgid "couchbase" msgstr "" +#: ../database.rst:167 +msgid "couchdb" +msgstr "" + +#: ../database.rst:168 +msgid "db2" +msgstr "" + +#: ../database.rst:169 +msgid "mariadb" +msgstr "" + #: ../database.rst:170 +msgid "mongodb" +msgstr "" + +#: ../database.rst:171 +msgid "mysql" +msgstr "" + +#: ../database.rst:172 msgid "percona" msgstr "" #: ../database.rst:173 -msgid "glance ID" +msgid "postgresql" msgstr "" #: ../database.rst:174 +msgid "pxc" +msgstr "" + +#: ../database.rst:175 +msgid "redis" +msgstr "" + +#: ../database.rst:176 +msgid "vertica" +msgstr "" + +#: ../database.rst:179 +msgid "glance ID" +msgstr "" + +#: ../database.rst:180 msgid "" "The ID of the guest image you just added to the Image service. You can get " "this ID by using the glance :command:`image-show` IMAGE_NAME command." msgstr "" -#: ../database.rst:177 +#: ../database.rst:183 msgid "bb75f870-0c33-4907-8467-1367f8cb15b6" msgstr "" -#: ../database.rst:179 +#: ../database.rst:185 msgid "packages" msgstr "" -#: ../database.rst:180 +#: ../database.rst:186 msgid "" "If you want to put additional packages on each guest that you create with " "this data store version, you can list the package names here." msgstr "" -#: ../database.rst:185 +#: ../database.rst:191 msgid "" "In this example, the guest image already contains all the required packages, " "so leave this argument empty." @@ -9904,59 +9935,59 @@ msgstr "" # #-#-#-#-# database.pot (Cloud Administrator Guide 0.9) #-#-#-#-# # #-#-#-#-# ts-eql-volume-size.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -#: ../database.rst:188 ../ts-eql-volume-size.rst:112 +#: ../database.rst:194 ../ts-eql-volume-size.rst:112 msgid "active" msgstr "" -#: ../database.rst:190 +#: ../database.rst:196 msgid "Set this to either 1 or 0:" msgstr "" -#: ../database.rst:190 +#: ../database.rst:196 msgid "``1`` = active" msgstr "" -#: ../database.rst:191 +#: ../database.rst:197 msgid "``0`` = disabled" msgstr "" -#: ../database.rst:192 +#: ../database.rst:198 msgid "1" msgstr "" -#: ../database.rst:202 +#: ../database.rst:208 msgid "" "**Optional.** Set your new version as the default version. To do this, use " "the :command:`trove-manage` :command:`datastore_update` command again, this " "time specifying the version you just created." msgstr "" -#: ../database.rst:210 +#: ../database.rst:216 msgid "**Load validation rules for configuration groups**" msgstr "" -#: ../database.rst:214 +#: ../database.rst:220 msgid "**Applies only to MySQL and Percona data stores**" msgstr "" -#: ../database.rst:216 +#: ../database.rst:222 msgid "" "If you just created a MySQL or Percona data store, then you need to load the " "appropriate validation rules, as described in this step." msgstr "" -#: ../database.rst:219 +#: ../database.rst:225 msgid "If you just created a different data store, skip this step." msgstr "" -#: ../database.rst:221 +#: ../database.rst:227 msgid "" "**Background.** You can manage database configuration tasks by using " "configuration groups. Configuration groups let you set configuration " "parameters, in bulk, on one or more databases." msgstr "" -#: ../database.rst:225 +#: ../database.rst:231 msgid "" "When you set up a configuration group using the trove :command:" "`configuration-create` command, this command compares the configuration " @@ -9964,43 +9995,43 @@ msgid "" "stored in the ``validation-rules.json`` file." msgstr "" -#: ../database.rst:234 +#: ../database.rst:240 msgid "Operating System" msgstr "" -#: ../database.rst:235 +#: ../database.rst:241 msgid "Location of :file:`validation-rules.json`" msgstr "" # #-#-#-#-# database.pot (Cloud Administrator Guide 0.9) #-#-#-#-# # #-#-#-#-# networking_adv-features.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -#: ../database.rst:236 ../networking_adv-features.rst:627 +#: ../database.rst:242 ../networking_adv-features.rst:627 msgid "Notes" msgstr "" -#: ../database.rst:238 +#: ../database.rst:244 msgid "Ubuntu 14.04" msgstr "" -#: ../database.rst:239 +#: ../database.rst:245 msgid ":file:`/usr/lib/python2.7/dist-packages/trove/templates/DATASTORE_NAME`" msgstr "" -#: ../database.rst:240 ../database.rst:246 +#: ../database.rst:246 ../database.rst:252 msgid "" "DATASTORE_NAME is the name of either the MySQL data store or the Percona " "data store. This is typically either ``mysql`` or ``percona``." msgstr "" -#: ../database.rst:244 +#: ../database.rst:250 msgid "RHEL 7, CentOS 7, Fedora 20, and Fedora 21" msgstr "" -#: ../database.rst:245 +#: ../database.rst:251 msgid ":file:`/usr/lib/python2.7/site-packages/trove/templates/DATASTORE_NAME`" msgstr "" -#: ../database.rst:251 +#: ../database.rst:257 msgid "" "Therefore, as part of creating a data store, you need to load the " "``validation-rules.json`` file, using the :command:`trove-manage` :command:" @@ -10008,55 +10039,55 @@ msgid "" "following arguments:" msgstr "" -#: ../database.rst:256 +#: ../database.rst:262 msgid "Data store name" msgstr "" -#: ../database.rst:257 +#: ../database.rst:263 msgid "Data store version" msgstr "" -#: ../database.rst:258 +#: ../database.rst:264 msgid "Full path to the ``validation-rules.json`` file" msgstr "" -#: ../database.rst:262 +#: ../database.rst:268 msgid "" "This example loads the ``validation-rules.json`` file for a MySQL database " "on Ubuntu 14.04:" msgstr "" -#: ../database.rst:269 +#: ../database.rst:275 msgid "**Validate data store**" msgstr "" -#: ../database.rst:271 +#: ../database.rst:277 msgid "" "To validate your new data store and version, start by listing the data " "stores on your system:" msgstr "" -#: ../database.rst:284 +#: ../database.rst:290 msgid "" "Take the ID of the MySQL data store and pass it in with the :command:" "`datastore-version-list` command:" msgstr "" -#: ../database.rst:297 +#: ../database.rst:303 msgid "Configure a cluster" msgstr "" -#: ../database.rst:299 +#: ../database.rst:305 msgid "" "An administrative user can configure various characteristics of a MongoDB " "cluster." msgstr "" -#: ../database.rst:302 +#: ../database.rst:308 msgid "**Query routers and config servers**" msgstr "" -#: ../database.rst:304 +#: ../database.rst:310 msgid "" "**Background.** Each cluster includes at least one query router and one " "config server. Query routers and config servers count against your quota. " @@ -10064,30 +10095,30 @@ msgid "" "and config server(s)." msgstr "" -#: ../database.rst:309 +#: ../database.rst:315 msgid "" "**Configuration.** By default, the system creates one query router and one " "config server per cluster. You can change this by editing the ``/etc/trove/" "trove.conf`` file. These settings are in the ``mongodb`` section of the file:" msgstr "" -#: ../database.rst:318 +#: ../database.rst:324 msgid "Setting" msgstr "" -#: ../database.rst:319 +#: ../database.rst:325 msgid "Valid values are:" msgstr "" -#: ../database.rst:321 +#: ../database.rst:327 msgid "num_config_servers_per_cluster" msgstr "" -#: ../database.rst:322 ../database.rst:325 +#: ../database.rst:328 ../database.rst:331 msgid "1 or 3" msgstr "" -#: ../database.rst:324 +#: ../database.rst:330 msgid "num_query_routers_per_cluster" msgstr "" @@ -14954,7 +14985,7 @@ msgstr "" # #-#-#-#-# networking_config-agents.pot (Cloud Administrator Guide 0.9) #-#-#-#-# # #-#-#-#-# networking_introduction.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -#: ../networking_config-agents.rst:363 ../networking_introduction.rst:202 +#: ../networking_config-agents.rst:363 ../networking_introduction.rst:203 msgid "Create the required tables in the database:" msgstr "" @@ -15964,43 +15995,42 @@ msgid "" "the VM2 instance:" msgstr "" -#: ../networking_introduction.rst:177 -msgid "**To enable FWaaS**" +#: ../networking_introduction.rst:178 +msgid "Enable FWaaS" msgstr "" -#: ../networking_introduction.rst:179 -msgid "FWaaS management options are also available in the OpenStack dashboard." +#: ../networking_introduction.rst:180 +msgid "FWaaS management options are also available in the Dashboard." msgstr "" -#: ../networking_introduction.rst:181 +#: ../networking_introduction.rst:182 msgid "Enable the FWaaS plug-in in the ``/etc/neutron/neutron.conf`` file:" msgstr "" -#: ../networking_introduction.rst:198 +#: ../networking_introduction.rst:199 msgid "" "On Ubuntu, modify the ``[fwaas]`` section in the ``/etc/neutron/fwaas_driver." "ini`` file instead of ``/etc/neutron/neutron.conf``." msgstr "" -#: ../networking_introduction.rst:208 +#: ../networking_introduction.rst:209 msgid "" -"Enable the option in the ``/usr/share/openstack-dashboard/" -"openstack_dashboard/ local/local_settings.py`` file, which is typically " +"Enable the option in the ``local_settings.py`` file, which is typically " "located on the controller node:" msgstr "" -#: ../networking_introduction.rst:221 +#: ../networking_introduction.rst:220 msgid "Apply the settings by restarting the web server." msgstr "" -#: ../networking_introduction.rst:223 +#: ../networking_introduction.rst:222 msgid "" "Restart the ``neutron-l3-agent`` and ``neutron-server`` services to apply " "the settings." msgstr "" #: ../networking_introduction.rst:226 -msgid "**To configure Firewall-as-a-Service**" +msgid "Configure Firewall-as-a-Service" msgstr "" #: ../networking_introduction.rst:228 @@ -16013,68 +16043,68 @@ msgstr "" msgid "Create a firewall rule:" msgstr "" -#: ../networking_introduction.rst:238 +#: ../networking_introduction.rst:239 msgid "" "The Networking client requires a protocol value; if the rule is protocol " "agnostic, you can use the ``any`` value." msgstr "" -#: ../networking_introduction.rst:241 +#: ../networking_introduction.rst:242 msgid "Create a firewall policy:" msgstr "" -#: ../networking_introduction.rst:248 +#: ../networking_introduction.rst:249 msgid "" "Separate firewall rule IDs or names with spaces. The order in which you " "specify the rules is important." msgstr "" -#: ../networking_introduction.rst:251 +#: ../networking_introduction.rst:252 msgid "" "You can create a firewall policy without any rules and add rules later, as " "follows:" msgstr "" -#: ../networking_introduction.rst:254 +#: ../networking_introduction.rst:255 msgid "To add multiple rules, use the update operation." msgstr "" -#: ../networking_introduction.rst:256 +#: ../networking_introduction.rst:257 msgid "To add a single rule, use the insert-rule operation." msgstr "" -#: ../networking_introduction.rst:258 +#: ../networking_introduction.rst:259 msgid "" "For more details, see `Networking command-line client `__ in the OpenStack " +"org/cli-reference/content/neutronclient_commands." +"html#neutronclient_subcommand_firewall-policy-create>`_ in the OpenStack " "Command-Line Interface Reference." msgstr "" -#: ../networking_introduction.rst:266 +#: ../networking_introduction.rst:265 msgid "" "FWaaS always adds a default ``deny all`` rule at the lowest precedence of " "each policy. Consequently, a firewall policy with no rules blocks all " "traffic by default." msgstr "" -#: ../networking_introduction.rst:270 +#: ../networking_introduction.rst:269 msgid "Create a firewall:" msgstr "" -#: ../networking_introduction.rst:278 +#: ../networking_introduction.rst:277 msgid "" "The firewall remains in PENDING\\_CREATE state until you create a Networking " "router and attach an interface to it." msgstr "" #: ../networking_introduction.rst:281 -msgid "**Allowed-address-pairs.**" +msgid "Allowed-address-pairs" msgstr "" #: ../networking_introduction.rst:283 msgid "" -"``Allowed-address-pairs`` enables you to specify mac_address/" +"``Allowed-address-pairs`` enables you to specify mac_address and " "ip_address(cidr) pairs that pass through a port regardless of subnet. This " "enables the use of protocols such as VRRP, which floats an IP address " "between two instances to enable fast data plane failover." diff --git a/doc/arch-design/source/locale/arch-design.pot b/doc/arch-design/source/locale/arch-design.pot index fc6b90e137..ac0d99d396 100644 --- a/doc/arch-design/source/locale/arch-design.pot +++ b/doc/arch-design/source/locale/arch-design.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Architecture Design Guide 0.9\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2015-11-30 06:07+0000\n" +"POT-Creation-Date: 2015-12-30 06:12+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -5596,11 +5596,17 @@ msgstr "" #: ../massively-scalable-technical-considerations.rst:101 msgid "" -"In this example the cloud is divided into two regions, one for each site, " -"with two availability zones in each based on the power layout of the data " -"centers. A number of host aggregates enable targeting of virtual machine " -"instances using flavors, that require special capabilities shared by the " -"target hosts such as SSDs, 10 GbE networks, or GPU cards." +"In this example, the cloud is divided into two regions, an API cell and " +"three child cells for each region, with three availability zones in each " +"cell based on the power layout of the data centers. The below figure " +"describes the relationship between them within one region." +msgstr "" + +#: ../massively-scalable-technical-considerations.rst:108 +msgid "" +"A number of host aggregates enable targeting of virtual machine instances " +"using flavors, that require special capabilities shared by the target hosts " +"such as SSDs, 10 GbE networks, or GPU cards." msgstr "" #: ../massively-scalable-user-requirements.rst:4 diff --git a/doc/config-reference/source/locale/config-reference.pot b/doc/config-reference/source/locale/config-reference.pot index 6cc462cbbe..a9b0804d72 100644 --- a/doc/config-reference/source/locale/config-reference.pot +++ b/doc/config-reference/source/locale/config-reference.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Configuration Reference 0.9\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2015-12-28 06:13+0000\n" +"POT-Creation-Date: 2015-12-30 06:12+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -1045,7 +1045,7 @@ msgstr "" #: ../block-storage/drivers/solidfire-volume-driver.rst:54 #: ../block-storage/drivers/violin-v6000-driver.rst:47 #: ../block-storage/drivers/violin-v7000-driver.rst:38 -#: ../block-storage/drivers/vmware-vmdk-driver.rst:202 +#: ../block-storage/drivers/vmware-vmdk-driver.rst:206 #: ../block-storage/drivers/xio-volume-driver.rst:19 #: ../block-storage/drivers/zfssa-iscsi-driver.rst:103 #: ../block-storage/drivers/zfssa-nfs-driver.rst:15 @@ -1455,7 +1455,7 @@ msgstr "" #: ../block-storage/drivers/solidfire-volume-driver.rst:56 #: ../block-storage/drivers/violin-v6000-driver.rst:49 #: ../block-storage/drivers/violin-v7000-driver.rst:40 -#: ../block-storage/drivers/vmware-vmdk-driver.rst:206 +#: ../block-storage/drivers/vmware-vmdk-driver.rst:210 #: ../block-storage/drivers/zfssa-nfs-driver.rst:17 msgid "Create, delete, attach, and detach volumes." msgstr "" @@ -1479,7 +1479,7 @@ msgstr "" #: ../block-storage/drivers/solidfire-volume-driver.rst:58 #: ../block-storage/drivers/violin-v6000-driver.rst:51 #: ../block-storage/drivers/violin-v7000-driver.rst:42 -#: ../block-storage/drivers/vmware-vmdk-driver.rst:215 +#: ../block-storage/drivers/vmware-vmdk-driver.rst:219 #: ../block-storage/drivers/xio-volume-driver.rst:25 msgid "Create, list, and delete volume snapshots." msgstr "" @@ -1502,7 +1502,7 @@ msgstr "" #: ../block-storage/drivers/solidfire-volume-driver.rst:66 #: ../block-storage/drivers/violin-v6000-driver.rst:59 #: ../block-storage/drivers/violin-v7000-driver.rst:50 -#: ../block-storage/drivers/vmware-vmdk-driver.rst:238 +#: ../block-storage/drivers/vmware-vmdk-driver.rst:242 #: ../block-storage/drivers/zfssa-nfs-driver.rst:29 msgid "Clone a volume." msgstr "" @@ -1515,7 +1515,7 @@ msgstr "" #: ../block-storage/drivers/quobyte-driver.rst:49 #: ../block-storage/drivers/scality-sofs-driver.rst:38 #: ../block-storage/drivers/sheepdog-driver.rst:37 -#: ../block-storage/drivers/vmware-vmdk-driver.rst:32 +#: ../block-storage/drivers/vmware-vmdk-driver.rst:36 #: ../block-storage/drivers/zfssa-iscsi-driver.rst:16 #: ../compute/hypervisor-vmware.rst:205 ../compute/hypervisor-vmware.rst:249 #: ../shared-file-systems/drivers/quobyte-driver.rst:39 @@ -1758,7 +1758,7 @@ msgstr "" #: ../block-storage/drivers/solidfire-volume-driver.rst:60 #: ../block-storage/drivers/violin-v6000-driver.rst:53 #: ../block-storage/drivers/violin-v7000-driver.rst:44 -#: ../block-storage/drivers/vmware-vmdk-driver.rst:221 +#: ../block-storage/drivers/vmware-vmdk-driver.rst:225 #: ../block-storage/drivers/zfssa-nfs-driver.rst:21 msgid "Create a volume from a snapshot." msgstr "" @@ -1781,7 +1781,7 @@ msgstr "" #: ../block-storage/drivers/solidfire-volume-driver.rst:62 #: ../block-storage/drivers/violin-v6000-driver.rst:55 #: ../block-storage/drivers/violin-v7000-driver.rst:46 -#: ../block-storage/drivers/vmware-vmdk-driver.rst:223 +#: ../block-storage/drivers/vmware-vmdk-driver.rst:227 #: ../block-storage/drivers/zfssa-nfs-driver.rst:25 msgid "Copy an image to a volume." msgstr "" @@ -1803,7 +1803,7 @@ msgstr "" #: ../block-storage/drivers/solidfire-volume-driver.rst:64 #: ../block-storage/drivers/violin-v6000-driver.rst:57 #: ../block-storage/drivers/violin-v7000-driver.rst:48 -#: ../block-storage/drivers/vmware-vmdk-driver.rst:231 +#: ../block-storage/drivers/vmware-vmdk-driver.rst:235 #: ../block-storage/drivers/zfssa-nfs-driver.rst:27 msgid "Copy a volume to an image." msgstr "" @@ -1826,7 +1826,7 @@ msgstr "" #: ../block-storage/drivers/solidfire-volume-driver.rst:68 #: ../block-storage/drivers/violin-v6000-driver.rst:61 #: ../block-storage/drivers/violin-v7000-driver.rst:52 -#: ../block-storage/drivers/vmware-vmdk-driver.rst:263 +#: ../block-storage/drivers/vmware-vmdk-driver.rst:267 #: ../block-storage/drivers/zfssa-iscsi-driver.rst:111 #: ../block-storage/drivers/zfssa-nfs-driver.rst:23 msgid "Extend a volume." @@ -3292,7 +3292,7 @@ msgid "Possible Values:" msgstr "" #: ../block-storage/drivers/emc-vnx-driver.rst:447 -#: ../block-storage/drivers/vmware-vmdk-driver.rst:91 +#: ../block-storage/drivers/vmware-vmdk-driver.rst:95 msgid "``thick``" msgstr "" @@ -3305,7 +3305,7 @@ msgid "Run the following commands to create a ``thick`` volume type:" msgstr "" #: ../block-storage/drivers/emc-vnx-driver.rst:458 -#: ../block-storage/drivers/vmware-vmdk-driver.rst:88 +#: ../block-storage/drivers/vmware-vmdk-driver.rst:92 msgid "``thin``" msgstr "" @@ -8794,42 +8794,77 @@ msgid "How to use the NFS driver" msgstr "" #: ../block-storage/drivers/nfs-volume-driver.rst:56 -msgid "" -"Access to one or more NFS servers. Creating an NFS server is outside the " -"scope of this document. This example assumes access to the following NFS " -"servers and mount points:" +msgid "Creating an NFS server is outside the scope of this document." msgstr "" -#: ../block-storage/drivers/nfs-volume-driver.rst:60 -msgid "192.168.1.200:/storage" +#: ../block-storage/drivers/nfs-volume-driver.rst:59 +msgid "Configure with one NFS server" msgstr "" #: ../block-storage/drivers/nfs-volume-driver.rst:61 -msgid "192.168.1.201:/storage" -msgstr "" - -#: ../block-storage/drivers/nfs-volume-driver.rst:62 -msgid "192.168.1.202:/storage" -msgstr "" - -#: ../block-storage/drivers/nfs-volume-driver.rst:64 msgid "" -"This example demonstrates the use of with this driver with multiple NFS " -"servers. Multiple servers are not required. One is usually enough." +"This example assumes access to the following NFS server and mount point:" +msgstr "" + +#: ../block-storage/drivers/nfs-volume-driver.rst:63 +#: ../block-storage/drivers/nfs-volume-driver.rst:92 +msgid "192.168.1.200:/storage" +msgstr "" + +#: ../block-storage/drivers/nfs-volume-driver.rst:65 +msgid "This example demonstrates the usage of this driver with one NFS server." msgstr "" #: ../block-storage/drivers/nfs-volume-driver.rst:67 msgid "" +"Set the ``nas_ip`` option to the IP address or host name of your NFS server, " +"and the ``nas_share_path`` option to the NFS export path:" +msgstr "" + +#: ../block-storage/drivers/nfs-volume-driver.rst:76 +msgid "Configure with multiple NFS servers" +msgstr "" + +#: ../block-storage/drivers/nfs-volume-driver.rst:80 +msgid "" +"You can use the multiple NFS servers with `cinder multi back ends `_ feature. Configure the :ref:" +"`enabled_backends ` option with mutliple values, and use the " +"``nas_ip`` and ``nas_share`` options for each back end as described above." +msgstr "" + +#: ../block-storage/drivers/nfs-volume-driver.rst:86 +msgid "" +"The below example is another method to use multiple NFS servers, and " +"demonstrates the usage of this driver with multiple NFS servers. Multiple " +"servers are not required. One is usually enough." +msgstr "" + +#: ../block-storage/drivers/nfs-volume-driver.rst:90 +msgid "" +"This example assumes access to the following NFS servers and mount points:" +msgstr "" + +#: ../block-storage/drivers/nfs-volume-driver.rst:93 +msgid "192.168.1.201:/storage" +msgstr "" + +#: ../block-storage/drivers/nfs-volume-driver.rst:94 +msgid "192.168.1.202:/storage" +msgstr "" + +#: ../block-storage/drivers/nfs-volume-driver.rst:96 +msgid "" "Add your list of NFS servers to the file you specified with the " "``nfs_shares_config`` option. For example, if the value of this option was " "set to ``/etc/cinder/shares.txt`` file, then:" msgstr "" -#: ../block-storage/drivers/nfs-volume-driver.rst:78 +#: ../block-storage/drivers/nfs-volume-driver.rst:107 msgid "Comments are allowed in this file. They begin with a ``#``." msgstr "" -#: ../block-storage/drivers/nfs-volume-driver.rst:80 +#: ../block-storage/drivers/nfs-volume-driver.rst:109 msgid "" "Configure the ``nfs_mount_point_base`` option. This is a directory where " "``cinder-volume`` mounts all NFS shares stored in the ``shares.txt`` file. " @@ -8837,28 +8872,28 @@ msgid "" "the default value of ``$state_path/mnt``." msgstr "" -#: ../block-storage/drivers/nfs-volume-driver.rst:85 +#: ../block-storage/drivers/nfs-volume-driver.rst:114 msgid "" "Start the ``cinder-volume`` service. ``/var/lib/cinder/nfs`` should now " "contain a directory for each NFS share specified in the ``shares.txt`` file. " "The name of each directory is a hashed name:" msgstr "" -#: ../block-storage/drivers/nfs-volume-driver.rst:96 +#: ../block-storage/drivers/nfs-volume-driver.rst:125 msgid "You can now create volumes as you normally would:" msgstr "" -#: ../block-storage/drivers/nfs-volume-driver.rst:104 +#: ../block-storage/drivers/nfs-volume-driver.rst:133 msgid "" "This volume can also be attached and deleted just like other volumes. " "However, snapshotting is **not** supported." msgstr "" -#: ../block-storage/drivers/nfs-volume-driver.rst:108 +#: ../block-storage/drivers/nfs-volume-driver.rst:137 msgid "NFS driver notes" msgstr "" -#: ../block-storage/drivers/nfs-volume-driver.rst:110 +#: ../block-storage/drivers/nfs-volume-driver.rst:139 msgid "" "``cinder-volume`` manages the mounting of the NFS shares as well as volume " "creation on the shares. Keep this in mind when planning your OpenStack " @@ -8869,21 +8904,21 @@ msgid "" "more than one NFS server." msgstr "" -#: ../block-storage/drivers/nfs-volume-driver.rst:118 +#: ../block-storage/drivers/nfs-volume-driver.rst:147 msgid "" "Because data is stored in a file and not actually on a block storage device, " "you might not see the same IO performance as you would with a traditional " "block storage driver. Please test accordingly." msgstr "" -#: ../block-storage/drivers/nfs-volume-driver.rst:122 +#: ../block-storage/drivers/nfs-volume-driver.rst:151 msgid "" "Despite possible IO performance loss, having volume data stored in a file " "might be beneficial. For example, backing up volumes can be as easy as " "copying the volume files." msgstr "" -#: ../block-storage/drivers/nfs-volume-driver.rst:128 +#: ../block-storage/drivers/nfs-volume-driver.rst:157 msgid "Regular IO flushing and syncing still stands." msgstr "" @@ -9420,12 +9455,12 @@ msgid "" msgstr "" #: ../block-storage/drivers/scality-sofs-driver.rst:33 -#: ../block-storage/drivers/vmware-vmdk-driver.rst:244 +#: ../block-storage/drivers/vmware-vmdk-driver.rst:248 msgid "Backup a volume." msgstr "" #: ../block-storage/drivers/scality-sofs-driver.rst:35 -#: ../block-storage/drivers/vmware-vmdk-driver.rst:251 +#: ../block-storage/drivers/vmware-vmdk-driver.rst:255 msgid "Restore backup to new or existing volume." msgstr "" @@ -9951,17 +9986,21 @@ msgid "" "as NFS, iSCSI, FiberChannel, and vSAN." msgstr "" -#: ../block-storage/drivers/vmware-vmdk-driver.rst:13 +#: ../block-storage/drivers/vmware-vmdk-driver.rst:14 +msgid "The VMware VMDK driver requires vCenter version 5.1 at minimum." +msgstr "" + +#: ../block-storage/drivers/vmware-vmdk-driver.rst:17 msgid "Functional context" msgstr "" -#: ../block-storage/drivers/vmware-vmdk-driver.rst:15 +#: ../block-storage/drivers/vmware-vmdk-driver.rst:19 msgid "" "The VMware VMDK driver connects to vCenter, through which it can dynamically " "access all the data stores visible from the ESX hosts in the managed cluster." msgstr "" -#: ../block-storage/drivers/vmware-vmdk-driver.rst:18 +#: ../block-storage/drivers/vmware-vmdk-driver.rst:22 msgid "" "When you create a volume, the VMDK driver creates a VMDK file on demand. " "The VMDK file creation completes only when the volume is subsequently " @@ -9970,20 +10009,20 @@ msgid "" "service creates the VMDK file, attach a volume to the target instance." msgstr "" -#: ../block-storage/drivers/vmware-vmdk-driver.rst:24 +#: ../block-storage/drivers/vmware-vmdk-driver.rst:28 msgid "" "The running vSphere VM is automatically reconfigured to attach the VMDK file " "as an extra disk. Once attached, you can log in to the running vSphere VM to " "rescan and discover this extra disk." msgstr "" -#: ../block-storage/drivers/vmware-vmdk-driver.rst:28 +#: ../block-storage/drivers/vmware-vmdk-driver.rst:32 msgid "" "With the update to ESX version 6.0, the VMDK driver now supports NFS version " "4.1." msgstr "" -#: ../block-storage/drivers/vmware-vmdk-driver.rst:34 +#: ../block-storage/drivers/vmware-vmdk-driver.rst:38 msgid "" "The recommended volume driver for OpenStack Block Storage is the VMware " "vCenter VMDK driver. When you configure the driver, you must match it with " @@ -9991,17 +10030,17 @@ msgid "" "point to the same server." msgstr "" -#: ../block-storage/drivers/vmware-vmdk-driver.rst:39 +#: ../block-storage/drivers/vmware-vmdk-driver.rst:43 msgid "" "In the ``nova.conf`` file, use this option to define the Compute driver:" msgstr "" -#: ../block-storage/drivers/vmware-vmdk-driver.rst:45 +#: ../block-storage/drivers/vmware-vmdk-driver.rst:49 msgid "" "In the ``cinder.conf`` file, use this option to define the volume driver:" msgstr "" -#: ../block-storage/drivers/vmware-vmdk-driver.rst:52 +#: ../block-storage/drivers/vmware-vmdk-driver.rst:56 msgid "" "The following table lists various options that the drivers support for the " "OpenStack Block Storage configuration (``cinder.conf``):" @@ -10009,32 +10048,32 @@ msgstr "" # #-#-#-#-# block-storage.pot (Configuration Reference 0.9) #-#-#-#-# # #-#-#-#-# compute.pot (Configuration Reference 0.9) #-#-#-#-# -#: ../block-storage/drivers/vmware-vmdk-driver.rst:58 +#: ../block-storage/drivers/vmware-vmdk-driver.rst:62 #: ../compute/hypervisor-vmware.rst:510 msgid "VMDK disk type" msgstr "" -#: ../block-storage/drivers/vmware-vmdk-driver.rst:60 +#: ../block-storage/drivers/vmware-vmdk-driver.rst:64 msgid "" "The VMware VMDK drivers support the creation of VMDK disk file types " "``thin``, ``lazyZeroedThick`` (sometimes called thick or flat), or " "``eagerZeroedThick``." msgstr "" -#: ../block-storage/drivers/vmware-vmdk-driver.rst:63 +#: ../block-storage/drivers/vmware-vmdk-driver.rst:67 msgid "" "A thin virtual disk is allocated and zeroed on demand as the space is used. " "Unused space on a Thin disk is available to other users." msgstr "" -#: ../block-storage/drivers/vmware-vmdk-driver.rst:66 +#: ../block-storage/drivers/vmware-vmdk-driver.rst:70 msgid "" "A lazy zeroed thick virtual disk will have all space allocated at disk " "creation. This reserves the entire disk space, so it is not available to " "other users at any time." msgstr "" -#: ../block-storage/drivers/vmware-vmdk-driver.rst:70 +#: ../block-storage/drivers/vmware-vmdk-driver.rst:74 msgid "" "An eager zeroed thick virtual disk is similar to a lazy zeroed thick disk, " "in that the entire disk is allocated at creation. However, in this type, any " @@ -10043,70 +10082,70 @@ msgid "" "with stale data on physical media." msgstr "" -#: ../block-storage/drivers/vmware-vmdk-driver.rst:76 +#: ../block-storage/drivers/vmware-vmdk-driver.rst:80 msgid "" "Use the ``vmware:vmdk_type`` extra spec key with the appropriate value to " "specify the VMDK disk file type. This table shows the mapping between the " "extra spec entry and the VMDK disk file type:" msgstr "" -#: ../block-storage/drivers/vmware-vmdk-driver.rst:83 +#: ../block-storage/drivers/vmware-vmdk-driver.rst:87 msgid "Disk file type" msgstr "" -#: ../block-storage/drivers/vmware-vmdk-driver.rst:84 -#: ../block-storage/drivers/vmware-vmdk-driver.rst:121 +#: ../block-storage/drivers/vmware-vmdk-driver.rst:88 +#: ../block-storage/drivers/vmware-vmdk-driver.rst:125 msgid "Extra spec key" msgstr "" -#: ../block-storage/drivers/vmware-vmdk-driver.rst:85 -#: ../block-storage/drivers/vmware-vmdk-driver.rst:122 +#: ../block-storage/drivers/vmware-vmdk-driver.rst:89 +#: ../block-storage/drivers/vmware-vmdk-driver.rst:126 msgid "Extra spec value" msgstr "" # #-#-#-#-# block-storage.pot (Configuration Reference 0.9) #-#-#-#-# # #-#-#-#-# compute.pot (Configuration Reference 0.9) #-#-#-#-# -#: ../block-storage/drivers/vmware-vmdk-driver.rst:86 +#: ../block-storage/drivers/vmware-vmdk-driver.rst:90 #: ../compute/hypervisor-vmware.rst:513 msgid "thin" msgstr "" -#: ../block-storage/drivers/vmware-vmdk-driver.rst:87 -#: ../block-storage/drivers/vmware-vmdk-driver.rst:90 -#: ../block-storage/drivers/vmware-vmdk-driver.rst:93 +#: ../block-storage/drivers/vmware-vmdk-driver.rst:91 +#: ../block-storage/drivers/vmware-vmdk-driver.rst:94 +#: ../block-storage/drivers/vmware-vmdk-driver.rst:97 msgid "``vmware:vmdk_type``" msgstr "" -#: ../block-storage/drivers/vmware-vmdk-driver.rst:89 +#: ../block-storage/drivers/vmware-vmdk-driver.rst:93 msgid "lazyZeroedThick" msgstr "" -#: ../block-storage/drivers/vmware-vmdk-driver.rst:92 +#: ../block-storage/drivers/vmware-vmdk-driver.rst:96 msgid "eagerZeroedThick" msgstr "" -#: ../block-storage/drivers/vmware-vmdk-driver.rst:94 +#: ../block-storage/drivers/vmware-vmdk-driver.rst:98 msgid "``eagerZeroedThick``" msgstr "" -#: ../block-storage/drivers/vmware-vmdk-driver.rst:96 +#: ../block-storage/drivers/vmware-vmdk-driver.rst:100 msgid "" "If you do not specify a ``vmdk_type`` extra spec entry, the disk file type " "will default to ``thin``." msgstr "" -#: ../block-storage/drivers/vmware-vmdk-driver.rst:99 +#: ../block-storage/drivers/vmware-vmdk-driver.rst:103 msgid "" "The following example shows how to create a ``lazyZeroedThick`` VMDK volume " "by using the appropriate ``vmdk_type``:" msgstr "" -#: ../block-storage/drivers/vmware-vmdk-driver.rst:109 -#: ../block-storage/drivers/vmware-vmdk-driver.rst:120 +#: ../block-storage/drivers/vmware-vmdk-driver.rst:113 +#: ../block-storage/drivers/vmware-vmdk-driver.rst:124 msgid "Clone type" msgstr "" -#: ../block-storage/drivers/vmware-vmdk-driver.rst:111 +#: ../block-storage/drivers/vmware-vmdk-driver.rst:115 msgid "" "With the VMware VMDK drivers, you can create a volume from another source " "volume or a snapshot point. The VMware vCenter VMDK driver supports the " @@ -10115,42 +10154,42 @@ msgid "" "mapping for clone types:" msgstr "" -#: ../block-storage/drivers/vmware-vmdk-driver.rst:123 +#: ../block-storage/drivers/vmware-vmdk-driver.rst:127 msgid "full" msgstr "" -#: ../block-storage/drivers/vmware-vmdk-driver.rst:124 -#: ../block-storage/drivers/vmware-vmdk-driver.rst:127 +#: ../block-storage/drivers/vmware-vmdk-driver.rst:128 +#: ../block-storage/drivers/vmware-vmdk-driver.rst:131 msgid "``vmware:clone_type``" msgstr "" -#: ../block-storage/drivers/vmware-vmdk-driver.rst:125 +#: ../block-storage/drivers/vmware-vmdk-driver.rst:129 msgid "``full``" msgstr "" -#: ../block-storage/drivers/vmware-vmdk-driver.rst:126 +#: ../block-storage/drivers/vmware-vmdk-driver.rst:130 msgid "linked/fast" msgstr "" -#: ../block-storage/drivers/vmware-vmdk-driver.rst:128 +#: ../block-storage/drivers/vmware-vmdk-driver.rst:132 msgid "``linked``" msgstr "" -#: ../block-storage/drivers/vmware-vmdk-driver.rst:130 +#: ../block-storage/drivers/vmware-vmdk-driver.rst:134 msgid "If you do not specify the clone type, the default is ``full``." msgstr "" -#: ../block-storage/drivers/vmware-vmdk-driver.rst:132 +#: ../block-storage/drivers/vmware-vmdk-driver.rst:136 msgid "" "The following example shows linked cloning from a source volume, which is " "created from an image:" msgstr "" -#: ../block-storage/drivers/vmware-vmdk-driver.rst:145 +#: ../block-storage/drivers/vmware-vmdk-driver.rst:149 msgid "Use vCenter storage policies to specify back-end data stores" msgstr "" -#: ../block-storage/drivers/vmware-vmdk-driver.rst:147 +#: ../block-storage/drivers/vmware-vmdk-driver.rst:151 msgid "" "This section describes how to configure back-end data stores using storage " "policies. In vCenter 5.5 and greater, you can create one or more storage " @@ -10159,7 +10198,7 @@ msgid "" "property with the ``vmware:storage_profile`` key." msgstr "" -#: ../block-storage/drivers/vmware-vmdk-driver.rst:153 +#: ../block-storage/drivers/vmware-vmdk-driver.rst:157 msgid "" "For example, assume a storage policy in vCenter named ``gold_policy.`` and a " "Block Storage volume type named ``vol1`` with the extra spec key ``vmware:" @@ -10168,7 +10207,7 @@ msgid "" "stores that match the ``gold_policy`` storage policy." msgstr "" -#: ../block-storage/drivers/vmware-vmdk-driver.rst:159 +#: ../block-storage/drivers/vmware-vmdk-driver.rst:163 msgid "" "The Block Storage back-end configuration for vSphere data stores is " "automatically determined based on the vCenter configuration. If you " @@ -10177,45 +10216,45 @@ msgid "" "stores is automatically supported." msgstr "" -#: ../block-storage/drivers/vmware-vmdk-driver.rst:167 +#: ../block-storage/drivers/vmware-vmdk-driver.rst:171 msgid "" "You must configure any data stores that you configure for the Block Storage " "service for the Compute service." msgstr "" -#: ../block-storage/drivers/vmware-vmdk-driver.rst:170 +#: ../block-storage/drivers/vmware-vmdk-driver.rst:174 msgid "**To configure back-end data stores by using storage policies**" msgstr "" -#: ../block-storage/drivers/vmware-vmdk-driver.rst:172 +#: ../block-storage/drivers/vmware-vmdk-driver.rst:176 msgid "In vCenter, tag the data stores to be used for the back end." msgstr "" -#: ../block-storage/drivers/vmware-vmdk-driver.rst:174 +#: ../block-storage/drivers/vmware-vmdk-driver.rst:178 msgid "" "OpenStack also supports policies that are created by using vendor-specific " "capabilities; for example vSAN-specific storage policies." msgstr "" -#: ../block-storage/drivers/vmware-vmdk-driver.rst:179 +#: ../block-storage/drivers/vmware-vmdk-driver.rst:183 msgid "" "The tag value serves as the policy. For details, see :ref:`vmware-spbm`." msgstr "" -#: ../block-storage/drivers/vmware-vmdk-driver.rst:181 +#: ../block-storage/drivers/vmware-vmdk-driver.rst:185 msgid "" "Set the extra spec key ``vmware:storage_profile`` in the desired Block " "Storage volume types to the policy name that you created in the previous " "step." msgstr "" -#: ../block-storage/drivers/vmware-vmdk-driver.rst:185 +#: ../block-storage/drivers/vmware-vmdk-driver.rst:189 msgid "" "Optionally, for the ``vmware_host_version`` parameter, enter the version " "number of your vSphere platform. For example, ``5.5``." msgstr "" -#: ../block-storage/drivers/vmware-vmdk-driver.rst:188 +#: ../block-storage/drivers/vmware-vmdk-driver.rst:192 msgid "" "This setting overrides the default location for the corresponding WSDL file. " "Among other scenarios, you can use this setting to prevent WSDL error " @@ -10225,82 +10264,82 @@ msgstr "" # #-#-#-#-# block-storage.pot (Configuration Reference 0.9) #-#-#-#-# # #-#-#-#-# image-service.pot (Configuration Reference 0.9) #-#-#-#-# -#: ../block-storage/drivers/vmware-vmdk-driver.rst:193 +#: ../block-storage/drivers/vmware-vmdk-driver.rst:197 #: ../image-service/image_service_backends.rst:131 msgid "Complete the other vCenter configuration parameters as appropriate." msgstr "" -#: ../block-storage/drivers/vmware-vmdk-driver.rst:197 +#: ../block-storage/drivers/vmware-vmdk-driver.rst:201 msgid "" "Any volume that is created without an associated policy (that is to say, " "without an associated volume type that specifies ``vmware:storage_profile`` " "extra spec), there is no policy-based placement for that volume." msgstr "" -#: ../block-storage/drivers/vmware-vmdk-driver.rst:204 +#: ../block-storage/drivers/vmware-vmdk-driver.rst:208 msgid "The VMware vCenter VMDK driver supports these operations:" msgstr "" -#: ../block-storage/drivers/vmware-vmdk-driver.rst:210 +#: ../block-storage/drivers/vmware-vmdk-driver.rst:214 msgid "" "When a volume is attached to an instance, a reconfigure operation is " "performed on the instance to add the volume's VMDK to it. The user must " "manually rescan and mount the device from within the guest operating system." msgstr "" -#: ../block-storage/drivers/vmware-vmdk-driver.rst:219 +#: ../block-storage/drivers/vmware-vmdk-driver.rst:223 msgid "Allowed only if volume is not attached to an instance." msgstr "" -#: ../block-storage/drivers/vmware-vmdk-driver.rst:227 +#: ../block-storage/drivers/vmware-vmdk-driver.rst:231 msgid "" "Only images in ``vmdk`` disk format with ``bare`` container format are " "supported. The ``vmware_disktype`` property of the image can be " "``preallocated``, ``sparse``, ``streamOptimized`` or ``thin``." msgstr "" -#: ../block-storage/drivers/vmware-vmdk-driver.rst:235 +#: ../block-storage/drivers/vmware-vmdk-driver.rst:239 msgid "Allowed only if the volume is not attached to an instance." msgstr "" -#: ../block-storage/drivers/vmware-vmdk-driver.rst:236 +#: ../block-storage/drivers/vmware-vmdk-driver.rst:240 msgid "This operation creates a ``streamOptimized`` disk image." msgstr "" -#: ../block-storage/drivers/vmware-vmdk-driver.rst:242 +#: ../block-storage/drivers/vmware-vmdk-driver.rst:246 msgid "Supported only if the source volume is not attached to an instance." msgstr "" -#: ../block-storage/drivers/vmware-vmdk-driver.rst:248 +#: ../block-storage/drivers/vmware-vmdk-driver.rst:252 msgid "" "This operation creates a backup of the volume in ``streamOptimized`` disk " "format." msgstr "" -#: ../block-storage/drivers/vmware-vmdk-driver.rst:255 +#: ../block-storage/drivers/vmware-vmdk-driver.rst:259 msgid "Supported only if the existing volume doesn't contain snapshots." msgstr "" -#: ../block-storage/drivers/vmware-vmdk-driver.rst:257 +#: ../block-storage/drivers/vmware-vmdk-driver.rst:261 msgid "Change the type of a volume." msgstr "" -#: ../block-storage/drivers/vmware-vmdk-driver.rst:261 +#: ../block-storage/drivers/vmware-vmdk-driver.rst:265 msgid "This operation is supported only if the volume state is ``available``." msgstr "" -#: ../block-storage/drivers/vmware-vmdk-driver.rst:269 +#: ../block-storage/drivers/vmware-vmdk-driver.rst:273 msgid "Storage policy-based configuration in vCenter" msgstr "" -#: ../block-storage/drivers/vmware-vmdk-driver.rst:271 +#: ../block-storage/drivers/vmware-vmdk-driver.rst:275 msgid "" "You can configure Storage Policy-Based Management (SPBM) profiles for " "vCenter data stores supporting the Compute, Image service, and Block Storage " "components of an OpenStack implementation." msgstr "" -#: ../block-storage/drivers/vmware-vmdk-driver.rst:275 +#: ../block-storage/drivers/vmware-vmdk-driver.rst:279 msgid "" "In a vSphere OpenStack deployment, SPBM enables you to delegate several data " "stores for storage, which reduces the risk of running out of storage space. " @@ -10308,100 +10347,100 @@ msgid "" "storage space." msgstr "" -#: ../block-storage/drivers/vmware-vmdk-driver.rst:281 +#: ../block-storage/drivers/vmware-vmdk-driver.rst:285 msgid "Prerequisites" msgstr "" -#: ../block-storage/drivers/vmware-vmdk-driver.rst:283 +#: ../block-storage/drivers/vmware-vmdk-driver.rst:287 msgid "Determine the data stores to be used by the SPBM policy." msgstr "" -#: ../block-storage/drivers/vmware-vmdk-driver.rst:285 +#: ../block-storage/drivers/vmware-vmdk-driver.rst:289 msgid "" "Determine the tag that identifies the data stores in the OpenStack component " "configuration." msgstr "" -#: ../block-storage/drivers/vmware-vmdk-driver.rst:288 +#: ../block-storage/drivers/vmware-vmdk-driver.rst:292 msgid "" "Create separate policies or sets of data stores for separate OpenStack " "components." msgstr "" -#: ../block-storage/drivers/vmware-vmdk-driver.rst:292 +#: ../block-storage/drivers/vmware-vmdk-driver.rst:296 msgid "Create storage policies in vCenter" msgstr "" -#: ../block-storage/drivers/vmware-vmdk-driver.rst:294 +#: ../block-storage/drivers/vmware-vmdk-driver.rst:298 msgid "In vCenter, create the tag that identifies the data stores:" msgstr "" -#: ../block-storage/drivers/vmware-vmdk-driver.rst:296 +#: ../block-storage/drivers/vmware-vmdk-driver.rst:300 msgid "From the :guilabel:`Home` screen, click :guilabel:`Tags`." msgstr "" -#: ../block-storage/drivers/vmware-vmdk-driver.rst:298 +#: ../block-storage/drivers/vmware-vmdk-driver.rst:302 msgid "Specify a name for the tag." msgstr "" -#: ../block-storage/drivers/vmware-vmdk-driver.rst:300 +#: ../block-storage/drivers/vmware-vmdk-driver.rst:304 msgid "Specify a tag category. For example, ``spbm-cinder``." msgstr "" -#: ../block-storage/drivers/vmware-vmdk-driver.rst:302 +#: ../block-storage/drivers/vmware-vmdk-driver.rst:306 msgid "Apply the tag to the data stores to be used by the SPBM policy." msgstr "" -#: ../block-storage/drivers/vmware-vmdk-driver.rst:306 +#: ../block-storage/drivers/vmware-vmdk-driver.rst:310 msgid "" "For details about creating tags in vSphere, see the `vSphere documentation " "`__." msgstr "" -#: ../block-storage/drivers/vmware-vmdk-driver.rst:310 +#: ../block-storage/drivers/vmware-vmdk-driver.rst:314 msgid "" "In vCenter, create a tag-based storage policy that uses one or more tags to " "identify a set of data stores." msgstr "" -#: ../block-storage/drivers/vmware-vmdk-driver.rst:315 +#: ../block-storage/drivers/vmware-vmdk-driver.rst:319 msgid "" "For details about creating storage policies in vSphere, see the `vSphere " "documentation `__." msgstr "" -#: ../block-storage/drivers/vmware-vmdk-driver.rst:320 +#: ../block-storage/drivers/vmware-vmdk-driver.rst:324 msgid "Data store selection" msgstr "" -#: ../block-storage/drivers/vmware-vmdk-driver.rst:322 +#: ../block-storage/drivers/vmware-vmdk-driver.rst:326 msgid "" "If storage policy is enabled, the driver initially selects all the data " "stores that match the associated storage policy." msgstr "" -#: ../block-storage/drivers/vmware-vmdk-driver.rst:325 +#: ../block-storage/drivers/vmware-vmdk-driver.rst:329 msgid "" "If two or more data stores match the storage policy, the driver chooses a " "data store that is connected to the maximum number of hosts." msgstr "" -#: ../block-storage/drivers/vmware-vmdk-driver.rst:328 +#: ../block-storage/drivers/vmware-vmdk-driver.rst:332 msgid "" "In case of ties, the driver chooses the data store with lowest space " "utilization, where space utilization is defined by the ``(1-freespace/" "totalspace)`` meters." msgstr "" -#: ../block-storage/drivers/vmware-vmdk-driver.rst:332 +#: ../block-storage/drivers/vmware-vmdk-driver.rst:336 msgid "" "These actions reduce the number of volume migrations while attaching the " "volume to instances." msgstr "" -#: ../block-storage/drivers/vmware-vmdk-driver.rst:335 +#: ../block-storage/drivers/vmware-vmdk-driver.rst:339 msgid "" "The volume must be migrated if the ESX host for the instance cannot access " "the data store that contains the volume." @@ -11948,7 +11987,7 @@ msgstr "" # #-#-#-#-# compute.pot (Configuration Reference 0.9) #-#-#-#-# # #-#-#-#-# networking.pot (Configuration Reference 0.9) #-#-#-#-# -#: ../compute.rst:3 ../networking/networking_options_reference.rst:277 +#: ../compute.rst:3 ../networking/networking_options_reference.rst:275 msgid "Compute" msgstr "" @@ -15527,7 +15566,7 @@ msgstr "" # #-#-#-#-# compute.pot (Configuration Reference 0.9) #-#-#-#-# # #-#-#-#-# networking.pot (Configuration Reference 0.9) #-#-#-#-# #: ../compute/hypervisor-xen-api.rst:353 -#: ../networking/networking_options_reference.rst:255 +#: ../networking/networking_options_reference.rst:253 msgid "Agent" msgstr "" @@ -16605,7 +16644,7 @@ msgstr "" # #-#-#-#-# database-service.pot (Configuration Reference 0.9) #-#-#-#-# # #-#-#-#-# networking.pot (Configuration Reference 0.9) #-#-#-#-# # #-#-#-#-# orchestration.pot (Configuration Reference 0.9) #-#-#-#-# -#: ../compute/rpc.rst:35 ../database-service/databaseservice_rpc.rst:18 +#: ../compute/rpc.rst:35 ../database-service/databaseservice_rpc.rst:19 #: ../networking/networking_options_reference.rst:180 #: ../orchestration/orchestration_rpc.rst:35 msgid "Configure Qpid" @@ -16653,7 +16692,7 @@ msgstr "" # #-#-#-#-# networking.pot (Configuration Reference 0.9) #-#-#-#-# # #-#-#-#-# orchestration.pot (Configuration Reference 0.9) #-#-#-#-# #: ../compute/rpc.rst:78 ../networking/networking_options_reference.rst:219 -#: ../orchestration/orchestration_rpc.rst:78 +#: ../orchestration/orchestration_rpc.rst:73 msgid "" "By default, TCP is used as the transport. To enable SSL, set the " "``qpid_protocol`` option:" @@ -16669,9 +16708,9 @@ msgstr "" # #-#-#-#-# database-service.pot (Configuration Reference 0.9) #-#-#-#-# # #-#-#-#-# networking.pot (Configuration Reference 0.9) #-#-#-#-# # #-#-#-#-# orchestration.pot (Configuration Reference 0.9) #-#-#-#-# -#: ../compute/rpc.rst:91 ../database-service/databaseservice_rpc.rst:25 +#: ../compute/rpc.rst:91 ../database-service/databaseservice_rpc.rst:27 #: ../networking/networking_options_reference.rst:233 -#: ../orchestration/orchestration_rpc.rst:92 +#: ../orchestration/orchestration_rpc.rst:87 msgid "Configure ZeroMQ" msgstr "" @@ -16686,16 +16725,16 @@ msgstr "" # #-#-#-#-# database-service.pot (Configuration Reference 0.9) #-#-#-#-# # #-#-#-#-# networking.pot (Configuration Reference 0.9) #-#-#-#-# # #-#-#-#-# orchestration.pot (Configuration Reference 0.9) #-#-#-#-# -#: ../compute/rpc.rst:100 ../database-service/databaseservice_rpc.rst:32 -#: ../networking/networking_options_reference.rst:245 -#: ../orchestration/orchestration_rpc.rst:102 +#: ../compute/rpc.rst:100 ../database-service/databaseservice_rpc.rst:35 +#: ../networking/networking_options_reference.rst:243 +#: ../orchestration/orchestration_rpc.rst:97 msgid "Configure messaging" msgstr "" #: ../compute/rpc.rst:102 msgid "" "Use these options to configure the ``RabbitMQ`` and ``Qpid`` messaging " -"drivers." +"drivers in the ``nova.conf`` file." msgstr "" # #-#-#-#-# compute.pot (Configuration Reference 0.9) #-#-#-#-# @@ -18661,26 +18700,27 @@ msgid "" msgstr "" #: ../database-service/databaseservice_rpc.rst:13 -msgid "Use these options to configure the RabbitMQ messaging system:" +msgid "" +"Use these options to configure the RabbitMQ messaging system in the ``trove." +"conf`` file:" msgstr "" -#: ../database-service/databaseservice_rpc.rst:20 -msgid "Use these options to configure the Qpid messaging system:" +#: ../database-service/databaseservice_rpc.rst:21 +msgid "" +"Use these options to configure the Qpid messaging system in the ``trove." +"conf`` file:" msgstr "" -#: ../database-service/databaseservice_rpc.rst:27 -msgid "Use these options to configure the ZeroMQ messaging system:" +#: ../database-service/databaseservice_rpc.rst:29 +msgid "" +"Use these options to configure the ZeroMQ messaging system in the ``trove." +"conf`` file:" msgstr "" -# #-#-#-#-# database-service.pot (Configuration Reference 0.9) #-#-#-#-# -# #-#-#-#-# networking.pot (Configuration Reference 0.9) #-#-#-#-# -# #-#-#-#-# orchestration.pot (Configuration Reference 0.9) #-#-#-#-# -#: ../database-service/databaseservice_rpc.rst:34 -#: ../networking/networking_options_reference.rst:247 -#: ../orchestration/orchestration_rpc.rst:104 +#: ../database-service/databaseservice_rpc.rst:37 msgid "" "Use these common options to configure the RabbitMQ, Qpid, and ZeroMq " -"messaging drivers:" +"messaging drivers in the ``trove.conf`` file:" msgstr "" #: ../firewalls-default-ports.rst:0 @@ -19635,7 +19675,8 @@ msgstr "" #: ../image-service/image_service_rpc.rst:11 msgid "" "The following tables contain settings to configure the messaging middleware " -"for the Image service:" +"for the Image service. Use these options to configure the messaging drivers " +"in the ``glance-api.conf`` and ``glance-registry.conf`` files:" msgstr "" #: ../image-service/sample-configuration-files.rst:3 @@ -20175,7 +20216,7 @@ msgid "" "retries for RabbitMQ, and define the size of the RPC thread pool. To monitor " "notifications through RabbitMQ, you must set the ``notification_driver`` " "option to ``neutron.openstack.common.notifier.rpc_notifier`` in the " -"``neutron.conf`` file:" +"``neutron.conf`` file." msgstr "" #: ../networking/networking_options_reference.rst:182 @@ -20200,7 +20241,7 @@ msgstr "" # #-#-#-#-# networking.pot (Configuration Reference 0.9) #-#-#-#-# # #-#-#-#-# orchestration.pot (Configuration Reference 0.9) #-#-#-#-# #: ../networking/networking_options_reference.rst:203 -#: ../orchestration/orchestration_rpc.rst:61 +#: ../orchestration/orchestration_rpc.rst:58 msgid "" "If the Qpid broker listens on a port other than the AMQP default of 5672, " "you must set the ``qpid_port`` option to that value:" @@ -20209,16 +20250,13 @@ msgstr "" # #-#-#-#-# networking.pot (Configuration Reference 0.9) #-#-#-#-# # #-#-#-#-# orchestration.pot (Configuration Reference 0.9) #-#-#-#-# #: ../networking/networking_options_reference.rst:210 -#: ../orchestration/orchestration_rpc.rst:70 +#: ../orchestration/orchestration_rpc.rst:65 msgid "" "If you configure the Qpid broker to require authentication, you must add a " "user name and password to the configuration:" msgstr "" -# #-#-#-#-# networking.pot (Configuration Reference 0.9) #-#-#-#-# -# #-#-#-#-# orchestration.pot (Configuration Reference 0.9) #-#-#-#-# #: ../networking/networking_options_reference.rst:226 -#: ../orchestration/orchestration_rpc.rst:85 msgid "" "Use these additional options to configure the Qpid messaging driver for " "OpenStack Oslo RPC. These options are used infrequently." @@ -20228,148 +20266,154 @@ msgstr "" msgid "" "Use these options to configure the ZeroMQ messaging system for OpenStack " "Oslo RPC. ZeroMQ is not the default messaging system, so you must enable it " -"by setting the ``rpc_backend`` option in the ``neutron.conf`` file:" +"by setting the ``rpc_backend`` option in the ``neutron.conf`` file." msgstr "" -#: ../networking/networking_options_reference.rst:257 +#: ../networking/networking_options_reference.rst:245 +msgid "" +"Use these common options to configure the RabbitMQ, Qpid, and ZeroMq " +"messaging drivers in the ``neutron.conf`` file." +msgstr "" + +#: ../networking/networking_options_reference.rst:255 msgid "Use the following options to alter agent-related settings." msgstr "" -#: ../networking/networking_options_reference.rst:262 +#: ../networking/networking_options_reference.rst:260 msgid "API" msgstr "" -#: ../networking/networking_options_reference.rst:264 +#: ../networking/networking_options_reference.rst:262 msgid "Use the following options to alter API-related settings." msgstr "" -#: ../networking/networking_options_reference.rst:269 +#: ../networking/networking_options_reference.rst:267 msgid "Token authentication" msgstr "" -#: ../networking/networking_options_reference.rst:271 +#: ../networking/networking_options_reference.rst:269 msgid "Use the following options to alter token authentication settings." msgstr "" -#: ../networking/networking_options_reference.rst:279 +#: ../networking/networking_options_reference.rst:277 msgid "Use the following options to alter Compute-related settings." msgstr "" -#: ../networking/networking_options_reference.rst:284 +#: ../networking/networking_options_reference.rst:282 msgid "CORS" msgstr "" -#: ../networking/networking_options_reference.rst:286 +#: ../networking/networking_options_reference.rst:284 msgid "Use the following options to alter CORS-related settings." msgstr "" -#: ../networking/networking_options_reference.rst:291 +#: ../networking/networking_options_reference.rst:289 msgid "Database" msgstr "" -#: ../networking/networking_options_reference.rst:293 -#: ../networking/networking_options_reference.rst:300 +#: ../networking/networking_options_reference.rst:291 +#: ../networking/networking_options_reference.rst:298 msgid "Use the following options to alter Database-related settings." msgstr "" -#: ../networking/networking_options_reference.rst:298 +#: ../networking/networking_options_reference.rst:296 #: ../networking/sample-configuration-files.rst:67 msgid "DHCP agent" msgstr "" -#: ../networking/networking_options_reference.rst:305 +#: ../networking/networking_options_reference.rst:303 msgid "Distributed virtual router" msgstr "" -#: ../networking/networking_options_reference.rst:307 +#: ../networking/networking_options_reference.rst:305 msgid "Use the following options to alter DVR-related settings." msgstr "" -#: ../networking/networking_options_reference.rst:313 +#: ../networking/networking_options_reference.rst:311 msgid "Firewall-as-a-Service driver" msgstr "" -#: ../networking/networking_options_reference.rst:315 +#: ../networking/networking_options_reference.rst:313 msgid "" "Use the following options in the ``fwaas_driver.ini`` file for the FWaaS " "driver." msgstr "" -#: ../networking/networking_options_reference.rst:323 +#: ../networking/networking_options_reference.rst:321 msgid "Load-Balancer-as-a-Service configuration options" msgstr "" -#: ../networking/networking_options_reference.rst:325 +#: ../networking/networking_options_reference.rst:323 msgid "" "Use the following options in the ``neutron_lbaas.conf`` file for the LBaaS " "agent." msgstr "" -#: ../networking/networking_options_reference.rst:330 +#: ../networking/networking_options_reference.rst:328 msgid "" "Use the following options in the ``lbaas_agent.ini`` file for the LBaaS " "agent." msgstr "" -#: ../networking/networking_options_reference.rst:335 +#: ../networking/networking_options_reference.rst:333 msgid "" "Use the following options in the ``services_lbaas.conf`` file for the LBaaS " "agent." msgstr "" -#: ../networking/networking_options_reference.rst:342 +#: ../networking/networking_options_reference.rst:340 msgid "VPN-as-a-Service configuration options" msgstr "" -#: ../networking/networking_options_reference.rst:344 +#: ../networking/networking_options_reference.rst:342 msgid "" "Use the following options in the ``vpnaas_agent.ini`` file for the VPNaaS " "agent." msgstr "" -#: ../networking/networking_options_reference.rst:353 +#: ../networking/networking_options_reference.rst:351 msgid "IPv6 router advertisement" msgstr "" -#: ../networking/networking_options_reference.rst:355 +#: ../networking/networking_options_reference.rst:353 msgid "Use the following options to alter IPv6 RA settings." msgstr "" -#: ../networking/networking_options_reference.rst:360 +#: ../networking/networking_options_reference.rst:358 msgid "L3 agent" msgstr "" -#: ../networking/networking_options_reference.rst:362 +#: ../networking/networking_options_reference.rst:360 msgid "" "Use the following options in the ``l3_agent.ini`` file for the L3 agent." msgstr "" -#: ../networking/networking_options_reference.rst:368 +#: ../networking/networking_options_reference.rst:366 msgid "Logging" msgstr "" -#: ../networking/networking_options_reference.rst:370 +#: ../networking/networking_options_reference.rst:368 msgid "Use the following options to alter logging settings." msgstr "" -#: ../networking/networking_options_reference.rst:375 +#: ../networking/networking_options_reference.rst:373 msgid "Metadata Agent" msgstr "" -#: ../networking/networking_options_reference.rst:377 +#: ../networking/networking_options_reference.rst:375 msgid "" "Use the following options in the ``metadata_agent.ini`` file for the " "Metadata agent." msgstr "" -#: ../networking/networking_options_reference.rst:384 +#: ../networking/networking_options_reference.rst:382 msgid "" "Previously, the neutron metadata agent connected to a neutron server via " "REST API using a neutron client. This is ineffective because keystone is " "then fully involved into the authentication process and gets overloaded." msgstr "" -#: ../networking/networking_options_reference.rst:389 +#: ../networking/networking_options_reference.rst:387 msgid "" "The neutron metadata agent has been reworked to use RPC by default to " "connect to a server since Kilo release. This is a typical way of interacting " @@ -20377,7 +20421,7 @@ msgid "" "metadata RPC then neutron client will be used." msgstr "" -#: ../networking/networking_options_reference.rst:397 +#: ../networking/networking_options_reference.rst:395 msgid "" "Do not run the ``neutron-ns-metadata-proxy`` proxy namespace as root on a " "node with the L3 agent running. In OpenStack Kilo and newer, you can change " @@ -20386,66 +20430,66 @@ msgid "" "options." msgstr "" -#: ../networking/networking_options_reference.rst:404 +#: ../networking/networking_options_reference.rst:402 msgid "Metering Agent" msgstr "" -#: ../networking/networking_options_reference.rst:406 +#: ../networking/networking_options_reference.rst:404 msgid "" "Use the following options in the ``metering_agent.ini`` file for the " "Metering agent." msgstr "" -#: ../networking/networking_options_reference.rst:412 +#: ../networking/networking_options_reference.rst:410 msgid "Nova" msgstr "" -#: ../networking/networking_options_reference.rst:414 +#: ../networking/networking_options_reference.rst:412 msgid "" "Use the following options in the ``neutron.conf`` file to change nova-" "related settings." msgstr "" -#: ../networking/networking_options_reference.rst:420 +#: ../networking/networking_options_reference.rst:418 msgid "Policy" msgstr "" -#: ../networking/networking_options_reference.rst:422 +#: ../networking/networking_options_reference.rst:420 msgid "" "Use the following options in the ``neutron.conf`` file to change policy " "settings." msgstr "" -#: ../networking/networking_options_reference.rst:428 +#: ../networking/networking_options_reference.rst:426 msgid "Quotas" msgstr "" -#: ../networking/networking_options_reference.rst:430 +#: ../networking/networking_options_reference.rst:428 msgid "" "Use the following options in the ``neutron.conf`` file for the quota system." msgstr "" -#: ../networking/networking_options_reference.rst:436 +#: ../networking/networking_options_reference.rst:434 msgid "Scheduler" msgstr "" -#: ../networking/networking_options_reference.rst:438 +#: ../networking/networking_options_reference.rst:436 msgid "" "Use the following options in the ``neutron.conf`` file to change scheduler " "settings." msgstr "" -#: ../networking/networking_options_reference.rst:444 +#: ../networking/networking_options_reference.rst:442 msgid "Security Groups" msgstr "" -#: ../networking/networking_options_reference.rst:446 +#: ../networking/networking_options_reference.rst:444 msgid "" "Use the following options in the configuration file for your driver to " "change security group settings." msgstr "" -#: ../networking/networking_options_reference.rst:453 +#: ../networking/networking_options_reference.rst:451 msgid "" "Now Networking uses iptables to achieve security group functions. In L2 " "agent with ``enable_ipset`` option enabled, it makes use of IPset to improve " @@ -20453,7 +20497,7 @@ msgid "" "insensitive to the number of elements." msgstr "" -#: ../networking/networking_options_reference.rst:458 +#: ../networking/networking_options_reference.rst:456 msgid "" "When a port is created, L2 agent will add an additional IPset chain to it's " "iptables chain, if the security group that this port belongs to has rules " @@ -20461,7 +20505,7 @@ msgid "" "added to the ipset chain." msgstr "" -#: ../networking/networking_options_reference.rst:463 +#: ../networking/networking_options_reference.rst:461 msgid "" "If a member of a security group is changed, it used to reload iptables rules " "which is expensive. However, when IPset option is enabled on L2 agent, it " @@ -20469,7 +20513,7 @@ msgid "" "changed, it should just update an IPset." msgstr "" -#: ../networking/networking_options_reference.rst:471 +#: ../networking/networking_options_reference.rst:469 msgid "" "A single default security group has been introduced in order to avoid race " "conditions when creating a tenant's default security group. The race " @@ -22497,7 +22541,7 @@ msgid "" "retries for RabbitMQ, and define the size of the RPC thread pool. To monitor " "notifications through RabbitMQ, you must set the ``notification_driver`` " "option to ``heat.openstack.common.notifier.rpc_notifier`` in the ``heat." -"conf`` file:" +"conf`` file." msgstr "" #: ../orchestration/orchestration_rpc.rst:37 @@ -22507,24 +22551,37 @@ msgid "" "setting the ``rpc_backend`` option in the ``heat.conf`` file:" msgstr "" -#: ../orchestration/orchestration_rpc.rst:48 +#: ../orchestration/orchestration_rpc.rst:45 msgid "" "This critical option points the compute nodes to the Qpid broker (server). " "Set the ``qpid_hostname`` option to the host name where the broker runs in " "the ``heat.conf`` file." msgstr "" -#: ../orchestration/orchestration_rpc.rst:54 +#: ../orchestration/orchestration_rpc.rst:51 msgid "The ``qpid_hostname`` option accepts a host name or IP address value." msgstr "" -#: ../orchestration/orchestration_rpc.rst:94 +#: ../orchestration/orchestration_rpc.rst:80 +msgid "" +"Use these additional options to configure the Qpid messaging driver for " +"OpenStack Oslo RPC. These options are used infrequently in the ``heat.conf`` " +"file." +msgstr "" + +#: ../orchestration/orchestration_rpc.rst:89 msgid "" "Use these options to configure the ZeroMQ messaging system for OpenStack " "Oslo RPC. ZeroMQ is not the default messaging system, so you must enable it " "by setting the ``rpc_backend`` option in the ``heat.conf`` file." msgstr "" +#: ../orchestration/orchestration_rpc.rst:99 +msgid "" +"Use these common options to configure the RabbitMQ, Qpid, and ZeroMq " +"messaging drivers in the ``heat.conf`` file." +msgstr "" + #: ../policy-json-file.rst:3 msgid "The policy.json file" msgstr "" @@ -39489,28 +39546,38 @@ msgid "(BoolOpt) Specifies that the volume not be formatted during creation." msgstr "" #: ../tables/cinder-storwize.rst:47 -msgid "``storwize_svc_vol_rsize`` = ``2``" +msgid "``storwize_svc_flashcopy_rate`` = ``50``" msgstr "" #: ../tables/cinder-storwize.rst:48 msgid "" -"(IntOpt) Storage system space-efficiency parameter for volumes (percentage)" +"(IntOpt) Specifies the storwize Flashcopy rate to be used when creating a " +"full volume copy." msgstr "" #: ../tables/cinder-storwize.rst:49 -msgid "``storwize_svc_vol_warning`` = ``0``" +msgid "``storwize_svc_vol_rsize`` = ``2``" msgstr "" #: ../tables/cinder-storwize.rst:50 msgid "" -"(IntOpt) Storage system threshold for volume capacity warnings (percentage)" +"(IntOpt) Storage system space-efficiency parameter for volumes (percentage)" msgstr "" #: ../tables/cinder-storwize.rst:51 -msgid "``storwize_svc_volpool_name`` = ``volpool``" +msgid "``storwize_svc_vol_warning`` = ``0``" msgstr "" #: ../tables/cinder-storwize.rst:52 +msgid "" +"(IntOpt) Storage system threshold for volume capacity warnings (percentage)" +msgstr "" + +#: ../tables/cinder-storwize.rst:53 +msgid "``storwize_svc_volpool_name`` = ``volpool``" +msgstr "" + +#: ../tables/cinder-storwize.rst:54 msgid "(StrOpt) Storage system storage pool for volumes" msgstr "" diff --git a/doc/networking-guide/source/locale/ja/LC_MESSAGES/networking-guide.po b/doc/networking-guide/source/locale/ja/LC_MESSAGES/networking-guide.po index 374f7bf1d0..ddf24e6b94 100644 --- a/doc/networking-guide/source/locale/ja/LC_MESSAGES/networking-guide.po +++ b/doc/networking-guide/source/locale/ja/LC_MESSAGES/networking-guide.po @@ -15,11 +15,11 @@ msgid "" msgstr "" "Project-Id-Version: Networking Guide 0.9\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2015-12-13 01:49+0000\n" +"POT-Creation-Date: 2015-12-29 23:18+0000\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" -"PO-Revision-Date: 2015-12-12 06:56+0000\n" +"PO-Revision-Date: 2015-12-29 04:08+0000\n" "Last-Translator: Akihiro Motoki \n" "Language: ja\n" "Plural-Forms: nplurals=1; plural=0;\n" @@ -3397,10 +3397,10 @@ msgstr "エージェント (OVS) 側:" msgid "" "On each compute node edit the file :file:`/etc/neutron/plugins/ml2/" -"ml2_conf_sriov.ini`:" +"sriov_agent.ini`:" msgstr "" -"各コンピュートノードで :file:`/etc/neutron/plugins/ml2/ml2_conf_sriov.ini` " -"ファイルを編集します。" +"各コンピュートノードで :file:`/etc/neutron/plugins/ml2/sriov_agent.ini` ファ" +"イルを編集します。" msgid "On each compute node, create the VFs via the PCI SYS interface:" msgstr "" diff --git a/doc/networking-guide/source/locale/networking-guide.pot b/doc/networking-guide/source/locale/networking-guide.pot index 67c2390022..6c7d66f330 100644 --- a/doc/networking-guide/source/locale/networking-guide.pot +++ b/doc/networking-guide/source/locale/networking-guide.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Networking Guide 0.9\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2015-12-11 06:14+0000\n" +"POT-Creation-Date: 2015-12-30 06:13+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -1875,7 +1875,7 @@ msgstr "" #: ../adv_config_sriov.rst:277 msgid "" "On each compute node edit the file :file:`/etc/neutron/plugins/ml2/" -"ml2_conf_sriov.ini`:" +"sriov_agent.ini`:" msgstr "" #: ../adv_config_sriov.rst:289 diff --git a/doc/user-guide/source/locale/ja/LC_MESSAGES/user-guide.po b/doc/user-guide/source/locale/ja/LC_MESSAGES/user-guide.po index 559842426e..841c35afa7 100644 --- a/doc/user-guide/source/locale/ja/LC_MESSAGES/user-guide.po +++ b/doc/user-guide/source/locale/ja/LC_MESSAGES/user-guide.po @@ -18,11 +18,11 @@ msgid "" msgstr "" "Project-Id-Version: End User Guide 1.0.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2015-12-24 22:35+0000\n" +"POT-Creation-Date: 2015-12-29 23:18+0000\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" -"PO-Revision-Date: 2015-12-25 05:10+0000\n" +"PO-Revision-Date: 2015-12-29 04:11+0000\n" "Last-Translator: Akihiro Motoki \n" "Language: ja\n" "Plural-Forms: nplurals=1; plural=0;\n" @@ -2692,12 +2692,12 @@ msgstr "" msgid "" "For details on creating images, see `Creating images manually `__ in the *OpenStack " +"openstack.org/image-guide/create-images-manually.html>`_ in the *OpenStack " "Virtual Machine Image Guide*." msgstr "" "イメージ作成の詳細は、*OpenStack 仮想マシンイメージガイド* の `イメージの手動" "作成 `__ を参照してください。" +"html>`_ を参照してください。" msgid "" "For each NIC on the node, you must create an interface, specifying the " @@ -3390,8 +3390,8 @@ msgstr "" msgid "Images (glance)" msgstr "Images (glance)" -msgid "Images uploaded to the OpenStack Image service." -msgstr "OpenStack Image service にアップロードされたイメージ。" +msgid "Images uploaded to the Image service." +msgstr "Image service にアップロードされたイメージ。" # #-#-#-#-# cli_nova_configure_access_security_for_instances.pot (End User # Guide 1.0.0) #-#-#-#-# @@ -5286,9 +5286,6 @@ msgstr "" msgid "Select a volume from which to create a snapshot." msgstr "スナップショットを作成するボリュームを選択します。" -msgid "Select an image and click :guilabel:`Launch Instance`." -msgstr "イメージを選択して :guilabel:`インスタンスの起動` をクリックします。" - msgid "Select an instance." msgstr "インスタンスを選択します。" @@ -5544,13 +5541,6 @@ msgstr "" "に、ソース仮想マシンをシャットダウンします。必要に応じて、インスタンスを一覧" "表示して、インスタンスの名前を確認します。" -msgid "" -"Since you are launching an instance from an image, :guilabel:`Boot from " -"image` is chosen by default." -msgstr "" -"イメージからインスタンスを起動するため、:guilabel:`イメージから起動` が初めか" -"ら選択されています。" - msgid "Some cloud providers allow only administrators to perform this task." msgstr "いくつかのクラウドプロバイダーは管理者のみがこの作業を実行できます。" @@ -5749,13 +5739,6 @@ msgstr "" ":guilabel:`IP アドレス` の項目は自動的に入力されますが、:guilabel:`+` ボタン" "をクリックして、新しい IP アドレスを追加できます。" -msgid "" -"The :guilabel:`Instances` tab shows the instance's name, its private and " -"public IP addresses, size, status, task, and power state." -msgstr "" -":guilabel:`インスタンス` タブに、インスタンス名、プライベート IP アドレス、パ" -"ブリック IP アドレス、大きさ、状態、処理、電源状態が表示されます。" - msgid "" "The :guilabel:`Router Name` and :guilabel:`Router ID` fields are " "automatically updated." @@ -6164,13 +6147,6 @@ msgid "" "The container and object name in the format: ``CONTAINER_NAME/OBJECT_NAME``." msgstr "``CONTAINER_NAME/OBJECT_NAME`` 形式のコンテナー名とオブジェクト名。" -msgid "" -"The dashboard shows the images that have been uploaded to OpenStack Image " -"service and are available for this project." -msgstr "" -"このダッシュボードでは、OpenStack Image service にアップロードされたイメージ" -"および、指定したプロジェクトで利用可能なイメージを表示します。 " - msgid "" "The dashboard shows the instance to which the volume is now attached and the " "device name." diff --git a/doc/user-guide/source/locale/user-guide.pot b/doc/user-guide/source/locale/user-guide.pot index 2f8ac2721e..3fcf01c201 100644 --- a/doc/user-guide/source/locale/user-guide.pot +++ b/doc/user-guide/source/locale/user-guide.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: End User Guide 1.0.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2015-12-25 06:14+0000\n" +"POT-Creation-Date: 2015-12-30 06:13+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -703,7 +703,7 @@ msgstr "" # #-#-#-#-# cli_cheat_sheet.pot (End User Guide 1.0.0) #-#-#-#-# # #-#-#-#-# dashboard_launch_instances.pot (End User Guide 1.0.0) #-#-#-#-# -#: ../cli_cheat_sheet.rst:144 ../dashboard_launch_instances.rst:230 +#: ../cli_cheat_sheet.rst:144 ../dashboard_launch_instances.rst:233 msgid "Create an instance snapshot" msgstr "" @@ -917,20 +917,24 @@ msgid "" msgstr "" #: ../cli_config_drive.rst:31 +msgid "Also, the Bare Matal service supports the configuration drive." +msgstr "" + +#: ../cli_config_drive.rst:33 msgid "" "To use configuration drive with libvirt, XenServer, or VMware, you must " "first install the genisoimage package on each compute host. Otherwise, " "instances do not boot properly." msgstr "" -#: ../cli_config_drive.rst:35 +#: ../cli_config_drive.rst:37 msgid "" "Use the ``mkisofs_cmd`` flag to set the path where you install the " "genisoimage program. If genisoimage is in same path as the ``nova-compute`` " "service, you do not need to set this flag." msgstr "" -#: ../cli_config_drive.rst:39 +#: ../cli_config_drive.rst:41 msgid "" "To use configuration drive with Hyper-V, you must set the ``mkisofs_cmd`` " "value to the full path to an ``mkisofs.exe`` installation. Additionally, you " @@ -938,11 +942,18 @@ msgid "" "to the full path to an :command:`qemu-img` command installation." msgstr "" -#: ../cli_config_drive.rst:45 +#: ../cli_config_drive.rst:47 +msgid "" +"To use configuration drive with the Bare Metal service, you do not need to " +"prepare anything because the Bare Metal service treats the configuration " +"drive properly." +msgstr "" + +#: ../cli_config_drive.rst:51 msgid "**Image requirements**" msgstr "" -#: ../cli_config_drive.rst:47 +#: ../cli_config_drive.rst:53 msgid "" "An image built with a recent version of the cloud-init package can " "automatically access metadata passed through the configuration drive. The " @@ -950,7 +961,7 @@ msgid "" "such as Red Hat Enterprise Linux." msgstr "" -#: ../cli_config_drive.rst:52 +#: ../cli_config_drive.rst:58 msgid "" "If an image does not have the cloud-init package installed, you must " "customize the image to run a script that mounts the configuration drive on " @@ -959,24 +970,24 @@ msgid "" "data is organized on the configuration drive." msgstr "" -#: ../cli_config_drive.rst:58 +#: ../cli_config_drive.rst:64 msgid "" "If you use Xen with a configuration drive, use the ``xenapi_disable_agent`` " "configuration parameter to disable the agent." msgstr "" -#: ../cli_config_drive.rst:62 +#: ../cli_config_drive.rst:68 msgid "**Guidelines**" msgstr "" -#: ../cli_config_drive.rst:64 +#: ../cli_config_drive.rst:70 msgid "" "Do not rely on the presence of the EC2 metadata in the configuration drive, " "because this content might be removed in a future release. For example, do " "not rely on files in the ``ec2`` directory." msgstr "" -#: ../cli_config_drive.rst:68 +#: ../cli_config_drive.rst:74 msgid "" "When you create images that access configuration drive data and multiple " "directories are under the ``openstack`` directory, always select the highest " @@ -986,36 +997,36 @@ msgid "" "present." msgstr "" -#: ../cli_config_drive.rst:76 +#: ../cli_config_drive.rst:82 msgid "Enable and access the configuration drive" msgstr "" -#: ../cli_config_drive.rst:78 +#: ../cli_config_drive.rst:84 msgid "" "To enable the configuration drive, pass the ``--config-drive true`` " "parameter to the :command:`nova boot` command." msgstr "" -#: ../cli_config_drive.rst:81 +#: ../cli_config_drive.rst:87 msgid "" "The following example enables the configuration drive and passes user data, " "two files, and two key/value metadata pairs, all of which are accessible " "from the configuration drive:" msgstr "" -#: ../cli_config_drive.rst:93 +#: ../cli_config_drive.rst:99 msgid "" "You can also configure the Compute service to always create a configuration " "drive by setting the following option in the ``/etc/nova/nova.conf`` file:" msgstr "" -#: ../cli_config_drive.rst:103 +#: ../cli_config_drive.rst:109 msgid "" "If a user passes the ``--config-drive true`` flag to the :command:`nova " "boot` command, an administrator cannot disable the configuration drive." msgstr "" -#: ../cli_config_drive.rst:107 +#: ../cli_config_drive.rst:113 msgid "" "If your guest operating system supports accessing disk by label, you can " "mount the configuration drive as the ``/dev/disk/by-label/" @@ -1023,56 +1034,56 @@ msgid "" "configuration drive has the ``config-2`` volume label:" msgstr "" -#: ../cli_config_drive.rst:120 +#: ../cli_config_drive.rst:126 msgid "" "Ensure that you use at least version 0.3.1 of CirrOS for configuration drive " "support." msgstr "" -#: ../cli_config_drive.rst:123 +#: ../cli_config_drive.rst:129 msgid "" "If your guest operating system does not use ``udev``, the ``/dev/disk/by-" "label`` directory is not present." msgstr "" -#: ../cli_config_drive.rst:126 +#: ../cli_config_drive.rst:132 msgid "" "You can use the :command:`blkid` command to identify the block device that " "corresponds to the configuration drive. For example, when you boot the " "CirrOS image with the ``m1.tiny`` flavor, the device is ``/dev/vdb``:" msgstr "" -#: ../cli_config_drive.rst:139 +#: ../cli_config_drive.rst:145 msgid "Once identified, you can mount the device:" msgstr "" -#: ../cli_config_drive.rst:147 +#: ../cli_config_drive.rst:153 msgid "Configuration drive contents" msgstr "" -#: ../cli_config_drive.rst:149 +#: ../cli_config_drive.rst:155 msgid "" "In this example, the contents of the configuration drive are as follows::" msgstr "" -#: ../cli_config_drive.rst:163 +#: ../cli_config_drive.rst:169 msgid "" "The files that appear on the configuration drive depend on the arguments " "that you pass to the :command:`nova boot` command." msgstr "" -#: ../cli_config_drive.rst:167 +#: ../cli_config_drive.rst:173 msgid "OpenStack metadata format" msgstr "" -#: ../cli_config_drive.rst:169 +#: ../cli_config_drive.rst:175 msgid "" "The following example shows the contents of the ``openstack/2012-08-10/" "meta_data.json`` and ``openstack/latest/meta_data.json`` files. These files " "are identical. The file contents are formatted for readability." msgstr "" -#: ../cli_config_drive.rst:201 +#: ../cli_config_drive.rst:207 msgid "" "Note the effect of the ``--file /etc/network/interfaces=/home/myuser/" "instance-interfaces`` argument that was passed to the :command:`nova boot` " @@ -1081,22 +1092,22 @@ msgid "" "``/etc/network/interfaces`` in the ``meta_data.json`` file." msgstr "" -#: ../cli_config_drive.rst:209 +#: ../cli_config_drive.rst:215 msgid "EC2 metadata format" msgstr "" -#: ../cli_config_drive.rst:211 +#: ../cli_config_drive.rst:217 msgid "" "The following example shows the contents of the ``ec2/2009-04-04/meta-data." "json`` and the ``ec2/latest/meta-data.json`` files. These files are " "identical. The file contents are formatted to improve readability." msgstr "" -#: ../cli_config_drive.rst:253 +#: ../cli_config_drive.rst:259 msgid "User data" msgstr "" -#: ../cli_config_drive.rst:255 +#: ../cli_config_drive.rst:261 msgid "" "The ``openstack/2012-08-10/user_data``, ``openstack/latest/user_data``, " "``ec2/2009-04-04/user-data``, and ``ec2/latest/user-data`` file are present " @@ -1104,25 +1115,25 @@ msgid "" "passed to the :command:`nova boot` command." msgstr "" -#: ../cli_config_drive.rst:261 +#: ../cli_config_drive.rst:267 msgid "Configuration drive format" msgstr "" -#: ../cli_config_drive.rst:263 +#: ../cli_config_drive.rst:269 msgid "" "The default format of the configuration drive as an ISO 9660 file system. To " "explicitly specify the ISO 9660 format, add the following line to the ``/etc/" "nova/nova.conf`` file:" msgstr "" -#: ../cli_config_drive.rst:271 +#: ../cli_config_drive.rst:277 msgid "" "By default, you cannot attach the configuration drive image as a CD drive " "instead of as a disk drive. To attach a CD drive, add the following line to " "the ``/etc/nova/nova.conf`` file:" msgstr "" -#: ../cli_config_drive.rst:279 +#: ../cli_config_drive.rst:285 msgid "" "For legacy reasons, you can configure the configuration drive to use VFAT " "format instead of ISO 9660. It is unlikely that you would require VFAT " @@ -1131,11 +1142,11 @@ msgid "" "nova.conf`` file:" msgstr "" -#: ../cli_config_drive.rst:289 +#: ../cli_config_drive.rst:295 msgid "If you choose VFAT, the configuration drive is 64 MB." msgstr "" -#: ../cli_config_drive.rst:293 +#: ../cli_config_drive.rst:299 msgid "" "In current version (Liberty) of OpenStack Compute, live migration with " "``config_drive`` on local disk is forbidden due to the bug in libvirt of " @@ -1365,86 +1376,94 @@ msgstr "" msgid "The command returns the following output:" msgstr "" -#: ../cli_create_and_manage_stacks.rst:50 +#: ../cli_create_and_manage_stacks.rst:52 +msgid "" +"When you run the :command:`heat stack-create` command with the :option:`--" +"poll` option, it prints the :command:`heat stack-show` output first, and " +"then continously prints the events in log format until the stack completes " +"its action with success or failure." +msgstr "" + +#: ../cli_create_and_manage_stacks.rst:57 msgid "" "You can also use the :command:`template-validate` command to validate a " "template file without creating a stack from it." msgstr "" -#: ../cli_create_and_manage_stacks.rst:55 +#: ../cli_create_and_manage_stacks.rst:62 msgid "" "Previous versions of the heat client used :command:`validate` instead of :" "command:`template-validate`, but it has been deprecated in favor of :command:" "`template-validate`." msgstr "" -#: ../cli_create_and_manage_stacks.rst:59 +#: ../cli_create_and_manage_stacks.rst:66 msgid "To do so, run the following command:" msgstr "" -#: ../cli_create_and_manage_stacks.rst:65 +#: ../cli_create_and_manage_stacks.rst:72 msgid "If validation fails, the response returns an error message." msgstr "" -#: ../cli_create_and_manage_stacks.rst:68 +#: ../cli_create_and_manage_stacks.rst:75 msgid "Get information about stacks" msgstr "" -#: ../cli_create_and_manage_stacks.rst:70 +#: ../cli_create_and_manage_stacks.rst:77 msgid "" "To explore the state and history of a particular stack, you can run a number " "of commands." msgstr "" -#: ../cli_create_and_manage_stacks.rst:73 +#: ../cli_create_and_manage_stacks.rst:80 msgid "" "To see which stacks are visible to the current user, run the following " "command:" msgstr "" -#: ../cli_create_and_manage_stacks.rst:87 +#: ../cli_create_and_manage_stacks.rst:94 msgid "To show the details of a stack, run the following command:" msgstr "" -#: ../cli_create_and_manage_stacks.rst:93 +#: ../cli_create_and_manage_stacks.rst:100 msgid "" "A stack consists of a collection of resources. To list the resources and " "their status, run the following command:" msgstr "" -#: ../cli_create_and_manage_stacks.rst:106 +#: ../cli_create_and_manage_stacks.rst:113 msgid "" "To show the details for a specific resource in a stack, run the following " "command:" msgstr "" -#: ../cli_create_and_manage_stacks.rst:113 +#: ../cli_create_and_manage_stacks.rst:120 msgid "" "Some resources have associated metadata which can change throughout the life " "cycle of a resource. Show the metadata by running the following command:" msgstr "" -#: ../cli_create_and_manage_stacks.rst:121 +#: ../cli_create_and_manage_stacks.rst:128 msgid "" "A series of events is generated during the life cycle of a stack. To display " "life cycle events, run the following command:" msgstr "" -#: ../cli_create_and_manage_stacks.rst:135 +#: ../cli_create_and_manage_stacks.rst:142 msgid "To show the details for a particular event, run the following command:" msgstr "" -#: ../cli_create_and_manage_stacks.rst:143 +#: ../cli_create_and_manage_stacks.rst:150 msgid "Update a stack" msgstr "" -#: ../cli_create_and_manage_stacks.rst:145 +#: ../cli_create_and_manage_stacks.rst:152 msgid "" "To update an existing stack from a modified template file, run a command " "like the following command:" msgstr "" -#: ../cli_create_and_manage_stacks.rst:161 +#: ../cli_create_and_manage_stacks.rst:168 msgid "" "Some resources are updated in-place, while others are replaced with new " "resources." @@ -4697,9 +4716,9 @@ msgstr "" #: ../dashboard_create_networks.rst:19 ../dashboard_create_networks.rst:72 #: ../dashboard_databases.rst:60 ../dashboard_databases.rst:115 #: ../dashboard_databases.rst:146 ../dashboard_databases.rst:175 -#: ../dashboard_databases.rst:198 ../dashboard_launch_instances.rst:33 -#: ../dashboard_launch_instances.rst:217 ../dashboard_launch_instances.rst:232 -#: ../dashboard_launch_instances.rst:254 ../dashboard_manage_containers.rst:19 +#: ../dashboard_databases.rst:198 ../dashboard_launch_instances.rst:19 +#: ../dashboard_launch_instances.rst:220 ../dashboard_launch_instances.rst:235 +#: ../dashboard_launch_instances.rst:257 ../dashboard_manage_containers.rst:19 #: ../dashboard_manage_containers.rst:41 ../dashboard_manage_containers.rst:75 #: ../dashboard_manage_containers.rst:99 #: ../dashboard_manage_containers.rst:129 @@ -4725,8 +4744,8 @@ msgstr "" #: ../configure_access_and_security_for_instances.rst:130 #: ../configure_access_and_security_for_instances.rst:188 #: ../dashboard_create_networks.rst:21 ../dashboard_create_networks.rst:74 -#: ../dashboard_launch_instances.rst:35 ../dashboard_launch_instances.rst:219 -#: ../dashboard_launch_instances.rst:234 ../dashboard_launch_instances.rst:256 +#: ../dashboard_launch_instances.rst:21 ../dashboard_launch_instances.rst:222 +#: ../dashboard_launch_instances.rst:237 ../dashboard_launch_instances.rst:259 #: ../dashboard_manage_containers.rst:21 ../dashboard_manage_containers.rst:43 #: ../dashboard_manage_containers.rst:77 #: ../dashboard_manage_containers.rst:101 @@ -5471,7 +5490,9 @@ msgid "" "in your environment." msgstr "" -#: ../dashboard_databases.rst:69 +# #-#-#-#-# dashboard_databases.pot (End User Guide 1.0.0) #-#-#-#-# +# #-#-#-#-# dashboard_launch_instances.pot (End User Guide 1.0.0) #-#-#-#-# +#: ../dashboard_databases.rst:69 ../dashboard_launch_instances.rst:29 msgid "Click :guilabel:`Launch Instance`." msgstr "" @@ -5613,7 +5634,7 @@ msgstr "" # #-#-#-#-# dashboard_databases.pot (End User Guide 1.0.0) #-#-#-#-# # #-#-#-#-# dashboard_launch_instances.pot (End User Guide 1.0.0) #-#-#-#-# -#: ../dashboard_databases.rst:162 ../dashboard_launch_instances.rst:178 +#: ../dashboard_databases.rst:162 ../dashboard_launch_instances.rst:157 msgid "Click :guilabel:`Launch`." msgstr "" @@ -5678,17 +5699,17 @@ msgstr "" msgid "Launch and manage instances" msgstr "" -#: ../dashboard_launch_instances.rst:4 +#: ../dashboard_launch_instances.rst:5 msgid "" "Instances are virtual machines that run inside the cloud. You can launch an " "instance from the following sources:" msgstr "" -#: ../dashboard_launch_instances.rst:7 -msgid "Images uploaded to the OpenStack Image service." +#: ../dashboard_launch_instances.rst:8 +msgid "Images uploaded to the Image service." msgstr "" -#: ../dashboard_launch_instances.rst:9 +#: ../dashboard_launch_instances.rst:10 msgid "" "Image that you have copied to a persistent volume. The instance launches " "from the volume, which is provided by the ``cinder-volume`` API through " @@ -5696,114 +5717,74 @@ msgid "" msgstr "" #: ../dashboard_launch_instances.rst:14 +msgid "Instance snapshot that you took." +msgstr "" + +#: ../dashboard_launch_instances.rst:17 msgid "Launch an instance" msgstr "" -#: ../dashboard_launch_instances.rst:16 -msgid "When you launch an instance from a volume, note the following steps:" -msgstr "" - -#: ../dashboard_launch_instances.rst:18 -msgid "" -"To select the volume from which to launch, launch an instance from an " -"arbitrary image on the volume. The arbitrary image that you select does not " -"boot. Instead, it is replaced by the image on the volume that you choose in " -"the next steps." -msgstr "" - -#: ../dashboard_launch_instances.rst:23 -msgid "" -"To boot a Xen image from a volume, the image you launch in must be the same " -"type, fully virtualized or paravirtualized, as the one on the volume." -msgstr "" - -#: ../dashboard_launch_instances.rst:27 -msgid "" -"Select the volume or volume snapshot from which to boot. Enter a device " -"name. Enter ``vda`` for KVM images or ``xvda`` for Xen images." -msgstr "" - -#: ../dashboard_launch_instances.rst:30 -msgid "" -"When you launch an instance from an image, OpenStack creates a local copy of " -"the image on the compute node where the instance starts." -msgstr "" - -# #-#-#-#-# dashboard_launch_instances.pot (End User Guide 1.0.0) #-#-#-#-# -# #-#-#-#-# dashboard_manage_images.pot (End User Guide 1.0.0) #-#-#-#-# -#: ../dashboard_launch_instances.rst:37 ../dashboard_manage_images.rst:33 -#: ../dashboard_manage_images.rst:126 +#: ../dashboard_launch_instances.rst:23 ../dashboard_launch_instances.rst:261 msgid "" "On the :guilabel:`Project` tab, open the :guilabel:`Compute` tab and click :" -"guilabel:`Images` category." +"guilabel:`Instances` category." msgstr "" -#: ../dashboard_launch_instances.rst:40 +#: ../dashboard_launch_instances.rst:26 msgid "" -"The dashboard shows the images that have been uploaded to OpenStack Image " -"service and are available for this project." +"The dashboard shows the instances with its name, its private and floating IP " +"addresses, size, status, task, power state, and so on." msgstr "" -#: ../dashboard_launch_instances.rst:43 -msgid "" -"For details on creating images, see `Creating images manually `__ in the *OpenStack " -"Virtual Machine Image Guide*." -msgstr "" - -#: ../dashboard_launch_instances.rst:47 -msgid "Select an image and click :guilabel:`Launch Instance`." -msgstr "" - -#: ../dashboard_launch_instances.rst:49 +#: ../dashboard_launch_instances.rst:31 msgid "" "In the :guilabel:`Launch Instance` dialog box, specify the following values:" msgstr "" -#: ../dashboard_launch_instances.rst:51 +#: ../dashboard_launch_instances.rst:33 msgid ":guilabel:`Details` tab" msgstr "" -#: ../dashboard_launch_instances.rst:54 +#: ../dashboard_launch_instances.rst:36 msgid "" "By default, this value is set to the availability zone given by the cloud " "provider (for example, ``us-west`` or ``apac-south``). For some cases, it " "could be ``nova``." msgstr "" -#: ../dashboard_launch_instances.rst:56 +#: ../dashboard_launch_instances.rst:38 msgid "Availability Zone" msgstr "" -#: ../dashboard_launch_instances.rst:59 +#: ../dashboard_launch_instances.rst:41 msgid "Assign a name to the virtual machine." msgstr "" -#: ../dashboard_launch_instances.rst:63 +#: ../dashboard_launch_instances.rst:45 msgid "The name you assign here becomes the initial host name of the server." msgstr "" -#: ../dashboard_launch_instances.rst:66 +#: ../dashboard_launch_instances.rst:48 msgid "" "After the server is built, if you change the server name in the API or " "change the host name directly, the names are not updated in the dashboard." msgstr "" -#: ../dashboard_launch_instances.rst:70 +#: ../dashboard_launch_instances.rst:52 msgid "" "Server names are not guaranteed to be unique when created so you could have " "two instances with the same host name." msgstr "" -#: ../dashboard_launch_instances.rst:71 +#: ../dashboard_launch_instances.rst:53 msgid "Instance Name" msgstr "" -#: ../dashboard_launch_instances.rst:74 +#: ../dashboard_launch_instances.rst:56 msgid "Specify the size of the instance to launch." msgstr "" -#: ../dashboard_launch_instances.rst:78 +#: ../dashboard_launch_instances.rst:60 msgid "" "The flavor is selected based on the size of the image selected for launching " "an instance. For example, while creating an image, if you have entered the " @@ -5811,55 +5792,55 @@ msgid "" "the image, the default flavor is ``m1.small``." msgstr "" -#: ../dashboard_launch_instances.rst:82 +#: ../dashboard_launch_instances.rst:64 msgid "Flavor" msgstr "" -#: ../dashboard_launch_instances.rst:85 +#: ../dashboard_launch_instances.rst:67 msgid "" "To launch multiple instances, enter a value greater than ``1``. The default " "is ``1``." msgstr "" -#: ../dashboard_launch_instances.rst:86 +#: ../dashboard_launch_instances.rst:68 msgid "Instance Count" msgstr "" -#: ../dashboard_launch_instances.rst:89 +#: ../dashboard_launch_instances.rst:71 msgid "Your options are:" msgstr "" -#: ../dashboard_launch_instances.rst:92 +#: ../dashboard_launch_instances.rst:74 msgid "" "If you choose this option, a new field for :guilabel:`Image Name` displays. " "You can select the image from the list." msgstr "" -#: ../dashboard_launch_instances.rst:93 +#: ../dashboard_launch_instances.rst:75 msgid "Boot from image" msgstr "" -#: ../dashboard_launch_instances.rst:96 +#: ../dashboard_launch_instances.rst:78 msgid "" "If you choose this option, a new field for :guilabel:`Instance Snapshot` " "displays. You can select the snapshot from the list." msgstr "" -#: ../dashboard_launch_instances.rst:97 +#: ../dashboard_launch_instances.rst:79 msgid "Boot from snapshot" msgstr "" -#: ../dashboard_launch_instances.rst:100 +#: ../dashboard_launch_instances.rst:82 msgid "" "If you choose this option, a new field for :guilabel:`Volume` displays. You " "can select the volume from the list." msgstr "" -#: ../dashboard_launch_instances.rst:101 +#: ../dashboard_launch_instances.rst:83 msgid "Boot from volume" msgstr "" -#: ../dashboard_launch_instances.rst:104 +#: ../dashboard_launch_instances.rst:86 msgid "" "With this option, you can boot from an image and create a volume by entering " "the :guilabel:`Device Size` and :guilabel:`Device Name` for your volume. " @@ -5867,11 +5848,11 @@ msgid "" "terminating the instance." msgstr "" -#: ../dashboard_launch_instances.rst:107 +#: ../dashboard_launch_instances.rst:89 msgid "Boot from image (creates a new volume)" msgstr "" -#: ../dashboard_launch_instances.rst:110 +#: ../dashboard_launch_instances.rst:92 msgid "" "Using this option, you can boot from a volume snapshot and create a new " "volume by choosing :guilabel:`Volume Snapshot` from a list and adding a :" @@ -5879,43 +5860,37 @@ msgid "" "Terminate` option to delete the volume on terminating the instance." msgstr "" -#: ../dashboard_launch_instances.rst:114 +#: ../dashboard_launch_instances.rst:96 msgid "Boot from volume snapshot (creates a new volume)" msgstr "" -#: ../dashboard_launch_instances.rst:116 -msgid "" -"Since you are launching an instance from an image, :guilabel:`Boot from " -"image` is chosen by default." -msgstr "" - -#: ../dashboard_launch_instances.rst:117 +#: ../dashboard_launch_instances.rst:96 msgid "Instance Boot Source" msgstr "" -#: ../dashboard_launch_instances.rst:120 +#: ../dashboard_launch_instances.rst:99 msgid "" "This field changes based on your previous selection. If you have chosen to " "launch an instance using an image, the :guilabel:`Image Name` field " "displays. Select the image name from the dropdown list." msgstr "" -#: ../dashboard_launch_instances.rst:122 +#: ../dashboard_launch_instances.rst:101 msgid "Image Name" msgstr "" -#: ../dashboard_launch_instances.rst:125 +#: ../dashboard_launch_instances.rst:104 msgid "" "This field changes based on your previous selection. If you have chosen to " "launch an instance using a snapshot, the :guilabel:`Instance Snapshot` field " "displays. Select the snapshot name from the dropdown list." msgstr "" -#: ../dashboard_launch_instances.rst:128 +#: ../dashboard_launch_instances.rst:107 msgid "Instance Snapshot" msgstr "" -#: ../dashboard_launch_instances.rst:131 +#: ../dashboard_launch_instances.rst:110 msgid "" "This field changes based on your previous selection. If you have chosen to " "launch an instance using a volume, the :guilabel:`Volume` field displays. " @@ -5924,224 +5899,256 @@ msgid "" "option." msgstr "" -#: ../dashboard_launch_instances.rst:135 +#: ../dashboard_launch_instances.rst:114 msgid "Volume" msgstr "" -#: ../dashboard_launch_instances.rst:137 +#: ../dashboard_launch_instances.rst:116 msgid ":guilabel:`Access & Security` tab" msgstr "" -#: ../dashboard_launch_instances.rst:140 +#: ../dashboard_launch_instances.rst:119 msgid "Specify a key pair." msgstr "" -#: ../dashboard_launch_instances.rst:142 +#: ../dashboard_launch_instances.rst:121 msgid "" "If the image uses a static root password or a static key set (neither is " "recommended), you do not need to provide a key pair to launch the instance." msgstr "" -#: ../dashboard_launch_instances.rst:144 +#: ../dashboard_launch_instances.rst:123 msgid "Key Pair" msgstr "" -#: ../dashboard_launch_instances.rst:147 +#: ../dashboard_launch_instances.rst:126 msgid "Activate the security groups that you want to assign to the instance." msgstr "" -#: ../dashboard_launch_instances.rst:149 +#: ../dashboard_launch_instances.rst:128 msgid "" "Security groups are a kind of cloud firewall that define which incoming " "network traffic is forwarded to instances." msgstr "" -#: ../dashboard_launch_instances.rst:152 +#: ../dashboard_launch_instances.rst:131 msgid "" "If you have not created any security groups, you can assign only the default " "security group to the instance." msgstr "" -#: ../dashboard_launch_instances.rst:153 +#: ../dashboard_launch_instances.rst:132 msgid "Security Groups" msgstr "" -#: ../dashboard_launch_instances.rst:155 +#: ../dashboard_launch_instances.rst:134 msgid ":guilabel:`Networking` tab" msgstr "" -#: ../dashboard_launch_instances.rst:158 +#: ../dashboard_launch_instances.rst:137 msgid "" "To add a network to the instance, click the :guilabel:`+` in the :guilabel:" "`Available Networks` field." msgstr "" -#: ../dashboard_launch_instances.rst:159 +#: ../dashboard_launch_instances.rst:138 msgid "Selected Networks" msgstr "" -#: ../dashboard_launch_instances.rst:161 +#: ../dashboard_launch_instances.rst:140 msgid ":guilabel:`Post-Creation` tab" msgstr "" -#: ../dashboard_launch_instances.rst:164 +#: ../dashboard_launch_instances.rst:143 msgid "Specify a customization script that runs after your instance launches." msgstr "" -#: ../dashboard_launch_instances.rst:165 +#: ../dashboard_launch_instances.rst:144 msgid "Customization Script Source" msgstr "" -#: ../dashboard_launch_instances.rst:167 +#: ../dashboard_launch_instances.rst:146 msgid ":guilabel:`Advanced Options` tab" msgstr "" -#: ../dashboard_launch_instances.rst:170 +#: ../dashboard_launch_instances.rst:149 msgid "Select the type of disk partition from the dropdown list:" msgstr "" -#: ../dashboard_launch_instances.rst:173 +#: ../dashboard_launch_instances.rst:152 msgid "Automatic" msgstr "" -#: ../dashboard_launch_instances.rst:173 +#: ../dashboard_launch_instances.rst:152 msgid "Entire disk is single partition and automatically resizes." msgstr "" -#: ../dashboard_launch_instances.rst:176 +#: ../dashboard_launch_instances.rst:155 msgid "Disk Partition" msgstr "" -#: ../dashboard_launch_instances.rst:176 +#: ../dashboard_launch_instances.rst:155 msgid "Faster build times but requires manual partitioning." msgstr "" -#: ../dashboard_launch_instances.rst:176 +#: ../dashboard_launch_instances.rst:155 msgid "Manual" msgstr "" -#: ../dashboard_launch_instances.rst:180 +#: ../dashboard_launch_instances.rst:159 msgid "The instance starts on a compute node in the cloud." msgstr "" -#: ../dashboard_launch_instances.rst:182 -msgid "" -"The :guilabel:`Instances` tab shows the instance's name, its private and " -"public IP addresses, size, status, task, and power state." -msgstr "" - -#: ../dashboard_launch_instances.rst:185 +#: ../dashboard_launch_instances.rst:163 msgid "" "If you did not provide a key pair, security groups, or rules, users can " "access the instance only from inside the cloud through VNC. Even pinging the " "instance is not possible without an ICMP rule configured." msgstr "" -#: ../dashboard_launch_instances.rst:190 +#: ../dashboard_launch_instances.rst:167 +msgid "" +"You can also launch an instance from the :guilabel:`Images` or :guilabel:" +"`Volumes` category when you launch an instance from an image or a volume " +"respectively." +msgstr "" + +#: ../dashboard_launch_instances.rst:171 +msgid "" +"When you launch an instance from an image, OpenStack creates a local copy of " +"the image on the compute node where the instance starts." +msgstr "" + +#: ../dashboard_launch_instances.rst:174 +msgid "" +"For details on creating images, see `Creating images manually `_ in the *OpenStack " +"Virtual Machine Image Guide*." +msgstr "" + +#: ../dashboard_launch_instances.rst:178 +msgid "When you launch an instance from a volume, note the following steps:" +msgstr "" + +#: ../dashboard_launch_instances.rst:180 +msgid "" +"To select the volume from which to launch, launch an instance from an " +"arbitrary image on the volume. The arbitrary image that you select does not " +"boot. Instead, it is replaced by the image on the volume that you choose in " +"the next steps." +msgstr "" + +#: ../dashboard_launch_instances.rst:185 +msgid "" +"To boot a Xen image from a volume, the image you launch in must be the same " +"type, fully virtualized or paravirtualized, as the one on the volume." +msgstr "" + +#: ../dashboard_launch_instances.rst:189 +msgid "" +"Select the volume or volume snapshot from which to boot. Enter a device " +"name. Enter ``vda`` for KVM images or ``xvda`` for Xen images." +msgstr "" + +#: ../dashboard_launch_instances.rst:193 msgid "Connect to your instance by using SSH" msgstr "" -#: ../dashboard_launch_instances.rst:192 +#: ../dashboard_launch_instances.rst:195 msgid "" "To use SSH to connect to your instance, you use the downloaded keypair file." msgstr "" -#: ../dashboard_launch_instances.rst:197 +#: ../dashboard_launch_instances.rst:200 msgid "The user name is ``ubuntu`` for the Ubuntu cloud images on TryStack." msgstr "" -#: ../dashboard_launch_instances.rst:199 +#: ../dashboard_launch_instances.rst:202 msgid "Copy the IP address for your instance." msgstr "" -#: ../dashboard_launch_instances.rst:201 +#: ../dashboard_launch_instances.rst:204 msgid "" "Use the :command:`ssh` command to make a secure connection to the instance. " "For example:" msgstr "" -#: ../dashboard_launch_instances.rst:208 +#: ../dashboard_launch_instances.rst:211 msgid "At the prompt, type ``yes``." msgstr "" -#: ../dashboard_launch_instances.rst:211 +#: ../dashboard_launch_instances.rst:214 msgid "Track usage for instances" msgstr "" -#: ../dashboard_launch_instances.rst:213 +#: ../dashboard_launch_instances.rst:216 msgid "" "You can track usage for instances for each project. You can track costs per " "month by showing meters like number of vCPUs, disks, RAM, and uptime for all " "your instances." msgstr "" -#: ../dashboard_launch_instances.rst:221 +#: ../dashboard_launch_instances.rst:224 msgid "" "On the :guilabel:`Project` tab, open the :guilabel:`Compute` tab and click :" "guilabel:`Overview` category." msgstr "" -#: ../dashboard_launch_instances.rst:224 +#: ../dashboard_launch_instances.rst:227 msgid "" "To query the instance usage for a month, select a month and click :guilabel:" "`Submit`." msgstr "" -#: ../dashboard_launch_instances.rst:227 +#: ../dashboard_launch_instances.rst:230 msgid "To download a summary, click :guilabel:`Download CSV Summary`." msgstr "" -#: ../dashboard_launch_instances.rst:236 +#: ../dashboard_launch_instances.rst:239 msgid "" "On the :guilabel:`Project` tab, open the :guilabel:`Compute` tab and click " "the :guilabel:`Instances` category." msgstr "" -#: ../dashboard_launch_instances.rst:239 +#: ../dashboard_launch_instances.rst:242 msgid "Select the instance from which to create a snapshot." msgstr "" # #-#-#-#-# dashboard_launch_instances.pot (End User Guide 1.0.0) #-#-#-#-# # #-#-#-#-# dashboard_manage_volumes.pot (End User Guide 1.0.0) #-#-#-#-# -#: ../dashboard_launch_instances.rst:241 ../dashboard_manage_volumes.rst:120 +#: ../dashboard_launch_instances.rst:244 ../dashboard_manage_volumes.rst:120 msgid "In the :guilabel:`Actions` column, click :guilabel:`Create Snapshot`." msgstr "" -#: ../dashboard_launch_instances.rst:243 +#: ../dashboard_launch_instances.rst:246 msgid "" "In the :guilabel:`Create Snapshot` dialog box, enter a name for the " "snapshot, and click :guilabel:`Create Snapshot`." msgstr "" -#: ../dashboard_launch_instances.rst:246 +#: ../dashboard_launch_instances.rst:249 msgid "The Images category shows the instance snapshot." msgstr "" -#: ../dashboard_launch_instances.rst:248 +#: ../dashboard_launch_instances.rst:251 msgid "" "To launch an instance from the snapshot, select the snapshot and click :" "guilabel:`Launch`. Proceed with launching an instance." msgstr "" -#: ../dashboard_launch_instances.rst:252 +#: ../dashboard_launch_instances.rst:255 msgid "Manage an instance" msgstr "" -#: ../dashboard_launch_instances.rst:258 -msgid "" -"On the :guilabel:`Project` tab, open the :guilabel:`Compute` tab and click :" -"guilabel:`Instances` category." -msgstr "" - -#: ../dashboard_launch_instances.rst:261 +#: ../dashboard_launch_instances.rst:264 msgid "Select an instance." msgstr "" -#: ../dashboard_launch_instances.rst:263 +#: ../dashboard_launch_instances.rst:266 msgid "In the menu list in the :guilabel:`Actions` column, select the state." msgstr "" -#: ../dashboard_launch_instances.rst:265 +#: ../dashboard_launch_instances.rst:268 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 " @@ -6405,6 +6412,12 @@ msgstr "" msgid "Follow this procedure to upload an image to a project:" msgstr "" +#: ../dashboard_manage_images.rst:33 ../dashboard_manage_images.rst:126 +msgid "" +"On the :guilabel:`Project` tab, open the :guilabel:`Compute` tab and click :" +"guilabel:`Images` category." +msgstr "" + #: ../dashboard_manage_images.rst:36 ../dashboard_manage_images.rst:88 msgid "Click :guilabel:`Create Image`." msgstr ""