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 23c5d84443..e880fa1d98 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-10-04 06:16+0000\n" +"POT-Creation-Date: 2015-10-08 06:29+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -16,451 +16,371 @@ msgstr "" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" -#: ../objectstorage_auditors.rst:14 +#: ../baremetal.rst:8 +msgid "Bare Metal" +msgstr "" + +#: ../baremetal.rst:10 +msgid "The Bare Metal service provides physical hardware management features." +msgstr "" + +# #-#-#-#-# baremetal.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +# #-#-#-#-# database.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +# #-#-#-#-# orchestration-introduction.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +#: ../baremetal.rst:13 ../database.rst:13 ../orchestration-introduction.rst:3 +msgid "Introduction" +msgstr "" + +#: ../baremetal.rst:15 msgid "" -"\"-z\" means to only check for zero-byte files at 1000 files per second." +"The Bare Metal service provides physical hardware as opposed to virtual " +"machines and provides several reference drivers which leverage common " +"technologies like PXE and IPMI, to cover a wide range of hardware. The " +"pluggable driver architecture also allows vendor-specific drivers to be " +"added for improved performance or functionality not provided by reference " +"drivers. The Bare Metal service makes physical servers as easy to provision " +"as virtual machines in a cloud, which in turn will open up new avenues for " +"enterprises and service providers." msgstr "" -#: ../telemetry-measurements.rst:122 ../telemetry-measurements.rst:216 -#: ../telemetry-measurements.rst:449 ../telemetry-measurements.rst:452 -#: ../telemetry-measurements.rst:455 ../telemetry-measurements.rst:458 -#: ../telemetry-measurements.rst:461 ../telemetry-measurements.rst:557 -#: ../telemetry-measurements.rst:561 ../telemetry-measurements.rst:565 -#: ../telemetry-measurements.rst:655 -msgid "%" +# #-#-#-#-# baremetal.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +# #-#-#-#-# compute_arch.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +# #-#-#-#-# telemetry-system-architecture.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +#: ../baremetal.rst:26 ../compute_arch.rst:3 +#: ../telemetry-system-architecture.rst:5 +msgid "System architecture" msgstr "" -#: ../networking_adv-features.rst:706 -msgid "'permit' or 'deny'" +#: ../baremetal.rst:28 +msgid "The Bare Metal module is composed of the following components:" msgstr "" -#: ../compute-remote-console-access.rst:157 -msgid "(BoolOpt) Become a daemon (background process)" +#: ../baremetal.rst:30 +msgid "A RESTful API service" msgstr "" -#: ../compute-security.rst:114 -msgid "(BoolOpt) Disable SSL cert verification for Attestation service" +#: ../baremetal.rst:32 +msgid "A conductor service" msgstr "" -#: ../compute-remote-console-access.rst:169 -msgid "(BoolOpt) Disallow non-encrypted connections" +#: ../baremetal.rst:34 +msgid "Various drivers that support heterogeneous hardware" msgstr "" -#: ../compute-remote-console-access.rst:181 -msgid "(BoolOpt) Enable VNC related features" +#: ../baremetal.rst:36 +msgid "A message queue" msgstr "" -#: ../compute-remote-console-access.rst:38 -msgid "(BoolOpt) Enable spice guest agent support" +#: ../baremetal.rst:38 +msgid "A database for storing information about the resources" msgstr "" -#: ../compute-remote-console-access.rst:40 -msgid "(BoolOpt) Enable spice related features" +#: ../baremetal.rst:43 +msgid "Bare Metal deployment" msgstr "" -#: ../compute-remote-console-access.rst:165 -msgid "(BoolOpt) Record sessions to FILE.[session_number]" +#: ../baremetal.rst:45 +msgid "PXE deploy process" msgstr "" -#: ../compute-remote-console-access.rst:167 -msgid "(BoolOpt) Source is ipv6" +#: ../baremetal.rst:47 +msgid "Agent deploy process" msgstr "" -#: ../compute-networking-nova.rst:320 -msgid "(BoolOpt) Use IPv6" +#: ../blockstorage-api-throughput.rst:3 +msgid "Increase Block Storage API service throughput" msgstr "" -#: ../compute-security.rst:112 -msgid "(IntOpt) Attestation status cache valid period length" -msgstr "" - -#: ../compute-networking-nova.rst:528 +#: ../blockstorage-api-throughput.rst:5 msgid "" -"(IntOpt) Number of workers for metadata service. The default will be the " -"number of CPUs available." +"By default, the Block Storage API service runs in one process. This limits " +"the number of API requests that the Block Storage service can process at any " +"given time. In a production environment, you should increase the Block " +"Storage API throughput by allowing the Block Storage API service to run in " +"as many processes as the machine capacity allows." msgstr "" -#: ../compute-remote-console-access.rst:47 -#: ../compute-remote-console-access.rst:163 -msgid "(IntOpt) Port on which to listen for incoming requests" -msgstr "" - -#: ../compute-networking-nova.rst:526 -msgid "(IntOpt) The port for the metadata API port" -msgstr "" - -#: ../compute-networking-nova.rst:522 -msgid "(IntOpt) The port on which the metadata API will listen." -msgstr "" - -#: ../compute-networking-nova.rst:512 +#: ../blockstorage-api-throughput.rst:13 msgid "" -"(IntOpt) Time in seconds to cache metadata; 0 to disable metadata caching " -"entirely (not recommended). Increasing this should improve response times of " -"the metadata API when under heavy load. Higher values may increase memory " -"usage and result in longer times for host metadata changes to take effect." +"The Block Storage API service is named ``openstack-cinder-api`` on the " +"following distributions: CentOS, Fedora, openSUSE, Red Hat Enterprise Linux, " +"and SUSE Linux Enterprise. In Ubuntu and Debian distributions, the Block " +"Storage API service is named ``cinder-api``." msgstr "" -#: ../compute-remote-console-access.rst:175 -msgid "(IntOpt) VNC starting port" -msgstr "" - -#: ../keystone_certificates_for_pki.rst:175 -msgid "(Keystone token) signing certificate in PEM format" -msgstr "" - -#: ../compute-root-wrap-reference.rst:99 +#: ../blockstorage-api-throughput.rst:18 msgid "" -"(ListOpt) Comma-separated list containing the filter class to use, followed " -"by the Filter arguments (which vary depending on the Filter class selected)." +"To do so, use the Block Storage API service option ``osapi_volume_workers``. " +"This option allows you to specify the number of API service workers (or OS " +"processes) to launch for the Block Storage API service." msgstr "" -#: ../compute-root-wrap-reference.rst:60 +#: ../blockstorage-api-throughput.rst:22 msgid "" -"(ListOpt) Comma-separated list of directories containing filter definition " -"files. Defines where rootwrap filters are stored. Directories defined on " -"this line should all exist, and be owned and writable only by the root user." +"To configure this option, open the :file:`/etc/cinder/cinder.conf` " +"configuration file and set the ``osapi_volume_workers`` configuration key to " +"the number of CPU cores/threads on a machine." msgstr "" -#: ../keystone_use_trusts.rst:56 -msgid "(Optional) Comprised of the start time and end time for the trust." -msgstr "" - -#: ../telemetry-events.rst:147 +# #-#-#-#-# blockstorage-api-throughput.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +# #-#-#-#-# blockstorage_glusterfs_backend.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +# #-#-#-#-# blockstorage_nfs_backend.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +#: ../blockstorage-api-throughput.rst:26 +#: ../blockstorage_glusterfs_backend.rst:152 +#: ../blockstorage_glusterfs_backend.rst:186 +#: ../blockstorage_nfs_backend.rst:65 ../blockstorage_nfs_backend.rst:91 +#: ../blockstorage_nfs_backend.rst:107 ../blockstorage_nfs_backend.rst:139 msgid "" -"(Optional) The data type for this trait. Valid options are: ``text``, " -"``int``, ``float``, and ``datetime``. Defaults to ``text`` if not specified." +"On distributions that include ``openstack-config``, you can configure this " +"by running the following command instead::" msgstr "" -#: ../telemetry-events.rst:152 +#: ../blockstorage-api-throughput.rst:32 +msgid "Replace ``CORES`` with the number of CPU cores/threads on a machine." +msgstr "" + +#: ../blockstorage-boot-from-volume.rst:3 +msgid "Boot from volume" +msgstr "" + +#: ../blockstorage-boot-from-volume.rst:5 msgid "" -"(Optional) Used to execute simple programmatic conversions on the value in a " -"notification field." +"In some cases, you can store and run instances from inside volumes. For " +"information, see the `Launch an instance from a volume`_ section in the " +"`OpenStack End User Guide`_." msgstr "" -#: ../compute-security.rst:110 -msgid "(StrOpt) Attestation authorization blob - must change" +#: ../blockstorage-consistency-groups.rst:6 +msgid "Consistency groups" msgstr "" -#: ../compute-security.rst:120 -msgid "(StrOpt) Attestation server Cert file for Identity verification" -msgstr "" - -#: ../compute-security.rst:118 -msgid "(StrOpt) Attestation server HTTP" -msgstr "" - -#: ../compute-security.rst:116 -msgid "(StrOpt) Attestation server port" -msgstr "" - -#: ../compute-security.rst:108 -msgid "(StrOpt) Attestation web API URL" -msgstr "" - -#: ../compute-networking-nova.rst:318 -msgid "(StrOpt) Backend to use for IPv6 generation" -msgstr "" - -#: ../compute-networking-nova.rst:316 -msgid "(StrOpt) Default IPv6 gateway" -msgstr "" - -#: ../compute-networking-nova.rst:530 -msgid "(StrOpt) Driver to use for vendor data" -msgstr "" - -#: ../compute-networking-nova.rst:532 -msgid "(StrOpt) File to load JSON formatted vendor data from" -msgstr "" - -#: ../compute-networking-nova.rst:314 -msgid "(StrOpt) Fixed IPv6 address block" -msgstr "" - -#: ../compute-remote-console-access.rst:45 -#: ../compute-remote-console-access.rst:161 -msgid "(StrOpt) Host on which to listen for incoming requests" -msgstr "" - -#: ../compute-remote-console-access.rst:51 -msgid "(StrOpt) IP address on which instance spice server should listen" -msgstr "" - -#: ../compute-remote-console-access.rst:186 -msgid "(StrOpt) IP address on which instance vncservers should listen" -msgstr "" - -#: ../compute-remote-console-access.rst:49 -msgid "(StrOpt) Keymap for spice" -msgstr "" - -#: ../compute-remote-console-access.rst:183 +#: ../blockstorage-consistency-groups.rst:8 msgid "" -"(StrOpt) Location of VNC console proxy, in the form \"http://127.0.0.1:6080/" -"vnc_auto.html\"" +"Consistency group support is available in OpenStack Block Storage. The " +"support is added for creating snapshots of consistency groups. This feature " +"leverages the storage level consistency technology. It allows snapshots of " +"multiple volumes in the same consistency group to be taken at the same point-" +"in-time to ensure data consistency. The consistency group operations can be " +"performed using the Block Storage command line." msgstr "" -#: ../compute-remote-console-access.rst:191 +#: ../blockstorage-consistency-groups.rst:17 msgid "" -"(StrOpt) Location of nova xvp VNC console proxy, in the form " -"\"http://127.0.0.1:6081/console\"" +"Only Block Storage V2 API supports consistency groups. You can specify ``--" +"os-volume-api-version 2`` when using Block Storage command line for " +"consistency group operations." msgstr "" -#: ../compute-remote-console-access.rst:42 +#: ../blockstorage-consistency-groups.rst:21 msgid "" -"(StrOpt) Location of spice HTML5 console proxy, in the form " -"\"http://127.0.0.1:6082/spice_auto.html\"" +"Before using consistency groups, make sure the Block Storage driver that you " +"are running has consistency group support by reading the Block Storage " +"manual or consulting the driver maintainer. There are a small number of " +"drivers that have implemented this feature. The default LVM driver does not " +"support consistency groups yet because the consistency technology is not " +"available at the storage level." msgstr "" -#: ../compute-networking-nova.rst:524 -msgid "(StrOpt) OpenStack metadata service manager" -msgstr "" - -#: ../compute-remote-console-access.rst:171 -msgid "(StrOpt) Run webserver on same port. Serve files from DIR." -msgstr "" - -#: ../compute-remote-console-access.rst:159 -msgid "(StrOpt) SSL key file (if separate from cert)" -msgstr "" - -#: ../compute-networking-nova.rst:518 -msgid "(StrOpt) The IP address for the metadata API server" -msgstr "" - -#: ../compute-networking-nova.rst:520 -msgid "(StrOpt) The IP address on which the metadata API will listen." -msgstr "" - -#: ../compute-remote-console-access.rst:53 +#: ../blockstorage-consistency-groups.rst:28 msgid "" -"(StrOpt) The address to which proxy clients (like nova-spicehtml5proxy) " -"should connect" +"Before using consistency groups, you must change policies for the " +"consistency group APIs in the :file:`/etc/cinder/policy.json` file. By " +"default, the consistency group APIs are disabled. Enable them before running " +"consistency group operations." msgstr "" -#: ../compute-remote-console-access.rst:188 +#: ../blockstorage-consistency-groups.rst:33 +msgid "Here are existing policy entries for consistency groups::" +msgstr "" + +#: ../blockstorage-consistency-groups.rst:45 +msgid "Remove ``group:nobody`` to enable these APIs::" +msgstr "" + +#: ../blockstorage-consistency-groups.rst:57 +msgid "Restart Block Storage API service after changing policies." +msgstr "" + +#: ../blockstorage-consistency-groups.rst:59 +msgid "The following consistency group operations are supported:" +msgstr "" + +#: ../blockstorage-consistency-groups.rst:61 +msgid "Create a consistency group, given volume types." +msgstr "" + +#: ../blockstorage-consistency-groups.rst:65 msgid "" -"(StrOpt) The address to which proxy clients (like nova-xvpvncproxy) should " -"connect" +"A consistency group can support more than one volume type. The scheduler is " +"responsible for finding a back end that can support all given volume types." msgstr "" -#: ../compute-root-wrap-reference.rst:57 ../compute-root-wrap-reference.rst:96 -msgid "(Type) Description" -msgstr "" - -#: ../compute-live-migration-usage.rst:176 -msgid "(total)" -msgstr "" - -#: ../compute-live-migration-usage.rst:178 -msgid "(used_max)" -msgstr "" - -#: ../compute-live-migration-usage.rst:177 -msgid "(used_now)" -msgstr "" - -#: ../compute_arch.rst:299 -msgid "**API server**" -msgstr "" - -#: ../compute-manage-logs.rst:190 -msgid "**Accessing the serial console on an instance**" -msgstr "" - -#: ../objectstorage_components.rst:162 -msgid "**Accounts and containers**" -msgstr "" - -#: ../objectstorage_components.rst:17 +#: ../blockstorage-consistency-groups.rst:69 msgid "" -"**Accounts and containers.** Each account and container are individual " -"databases that are distributed across the cluster. An account database " -"contains the list of containers in that account. A container database " -"contains the list of objects in that container." +"A consistency group can only contain volumes hosted by the same back end." msgstr "" -#: ../telemetry-data-collection.rst:762 -msgid "**Accumulator transformer**" -msgstr "" - -#: ../database.rst:132 -msgid "**Add a version to the new datastore**" -msgstr "" - -# #-#-#-#-# keystone_integrate_identity_backend_ldap.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -# #-#-#-#-# keystone_integrate_with_ldap.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -#: ../keystone_integrate_identity_backend_ldap.rst:180 -#: ../keystone_integrate_with_ldap.rst:81 -msgid "**Additional LDAP integration settings**" -msgstr "" - -#: ../keystone_integrate_assignment_backend_ldap.rst:88 -msgid "**Additional LDAP integration settings.**" -msgstr "" - -#: ../networking_use.rst:171 -msgid "**Advanced Networking operations**" -msgstr "" - -#: ../networking_use.rst:268 -msgid "**Advanced VM creation operations**" -msgstr "" - -#: ../telemetry-data-collection.rst:725 -msgid "**Aggregator transformer**" -msgstr "" - -#: ../networking_introduction.rst:272 -msgid "**Allowed-address-pairs.**" -msgstr "" - -#: ../database.rst:213 -msgid "**Applies only to MySQL and Percona datastores**" -msgstr "" - -#: ../database.rst:297 +#: ../blockstorage-consistency-groups.rst:72 msgid "" -"**Background.** Each cluster includes at least one query router and one " -"config server. Query routers and config servers count against your quota. " -"When you delete a cluster, the system deletes the associated query router(s) " -"and config server(s)." +"A consistency group is empty upon its creation. Volumes need to be created " +"and added to it later." msgstr "" -#: ../database.rst:220 +#: ../blockstorage-consistency-groups.rst:75 +msgid "Show a consistency group." +msgstr "" + +#: ../blockstorage-consistency-groups.rst:77 +msgid "List consistency groups." +msgstr "" + +#: ../blockstorage-consistency-groups.rst:79 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." +"Create a volume and add it to a consistency group, given volume type and " +"consistency group id." msgstr "" -#: ../networking_use.rst:216 -msgid "**Basic Compute and Networking operations**" +#: ../blockstorage-consistency-groups.rst:82 +msgid "Create a snapshot for a consistency group." msgstr "" -#: ../networking_adv-features.rst:0 -msgid "**Basic L3 Operations**" +#: ../blockstorage-consistency-groups.rst:84 +msgid "Show a snapshot of a consistency group." msgstr "" -#: ../networking_adv-features.rst:0 -msgid "**Basic L3 operations**" +#: ../blockstorage-consistency-groups.rst:86 +msgid "List consistency group snapshots." msgstr "" -#: ../networking_use.rst:79 -msgid "**Basic Networking operations**" +#: ../blockstorage-consistency-groups.rst:88 +msgid "Delete a snapshot of a consistency group." msgstr "" -#: ../networking_adv-features.rst:0 -msgid "**Basic VMware NSX QoS operations**" +#: ../blockstorage-consistency-groups.rst:90 +msgid "Delete a consistency group." msgstr "" -#: ../networking_introduction.rst:284 -msgid "**Basic allowed-address-pairs operations.**" +#: ../blockstorage-consistency-groups.rst:92 +msgid "Modify a consistency group." msgstr "" -#: ../networking_config-agents.rst:518 -msgid "**Basic operations on Networking agents**" -msgstr "" - -#: ../networking_adv-features.rst:0 -msgid "**Basic security group operations**" -msgstr "" - -#: ../compute-node-down.rst:203 -msgid "**Begin recovery**" -msgstr "" - -#: ../networking_adv-features.rst:0 -msgid "**Big Switch Router rule attributes**" -msgstr "" - -#: ../compute-configuring-migrations.rst:36 +#: ../blockstorage-consistency-groups.rst:94 msgid "" -"**Block live migration**. No shared storage is required. Incompatible with " -"read-only devices such as CD-ROMs and `Configuration Drive (config\\_drive) " -"`_." +"Create a consistency group from the snapshot of another consistency group." msgstr "" -#: ../compute-configuring-migrations.rst:335 +#: ../blockstorage-consistency-groups.rst:97 +msgid "Create a consistency group from a source consistency group." +msgstr "" + +#: ../blockstorage-consistency-groups.rst:99 msgid "" -"**Compatible XenServer hypervisors**. For more information, see the " -"`Requirements for Creating Resource Pools `_ " -"section of the XenServer Administrator's Guide." +"The following operations are not allowed if a volume is in a consistency " +"group:" msgstr "" -#: ../compute-configuring-migrations.rst:406 +#: ../blockstorage-consistency-groups.rst:102 +msgid "Volume migration." +msgstr "" + +#: ../blockstorage-consistency-groups.rst:104 +msgid "Volume retype." +msgstr "" + +#: ../blockstorage-consistency-groups.rst:106 +msgid "Volume deletion." +msgstr "" + +#: ../blockstorage-consistency-groups.rst:110 +msgid "A consistency group has to be deleted as a whole with all the volumes." +msgstr "" + +#: ../blockstorage-consistency-groups.rst:113 msgid "" -"**Compatible XenServer hypervisors**. The hypervisors must support the " -"Storage XenMotion feature. See your XenServer manual to make sure your " -"edition has this feature." +"The following operations are not allowed if a volume snapshot is in a " +"consistency group snapshot:" msgstr "" -#: ../telemetry-data-retrieval.rst:77 -msgid "**Complex query**" +#: ../blockstorage-consistency-groups.rst:116 +msgid "Volume snapshot deletion." msgstr "" -#: ../compute_arch.rst:334 -msgid "**Compute worker**" -msgstr "" - -#: ../networking_adv-features.rst:0 +#: ../blockstorage-consistency-groups.rst:120 msgid "" -"**Configuration options for tuning operational status synchronization in the " -"NSX plug-in**" +"A consistency group snapshot has to be deleted as a whole with all the " +"volume snapshots." msgstr "" -#: ../database.rst:302 +#: ../blockstorage-consistency-groups.rst:123 +msgid "The details of consistency group operations are shown in the following." +msgstr "" + +#: ../blockstorage-consistency-groups.rst:125 +msgid "**Create a consistency group**::" +msgstr "" + +#: ../blockstorage-consistency-groups.rst:135 msgid "" -"**Configuration.** By default, the system creates one query router and one " -"config server per cluster. You can change this by editing the :file:`/etc/" -"trove/trove.conf` file. These settings are in the ``mongodb`` section of the " -"file:" +"The parameter ``volume-types`` is required. It can be a list of names or " +"UUIDs of volume types separated by commas without spaces in between. For " +"example, ``volumetype1,volumetype2,volumetype3.``." msgstr "" -#: ../blockstorage_glusterfs_backend.rst:81 -msgid "**Configure Block Storage to use a GlusterFS back end**" +#: ../blockstorage-consistency-groups.rst:154 +msgid "**Show a consistency group**::" msgstr "" -#: ../blockstorage_nfs_backend.rst:27 -msgid "**Configure Block Storage to use an NFS storage back end**" +#: ../blockstorage-consistency-groups.rst:169 +msgid "**List consistency groups**::" msgstr "" -#: ../blockstorage_glusterfs_backend.rst:40 -msgid "**Configure GlusterFS for OpenStack Block Storage**" +#: ../blockstorage-consistency-groups.rst:180 +msgid "**Create a volume and add it to a consistency group**:" msgstr "" -#: ../compute-security.rst:45 -msgid "**Configuring Compute to use trusted compute pools**" +#: ../blockstorage-consistency-groups.rst:184 +msgid "" +"When creating a volume and adding it to a consistency group, a volume type " +"and a consistency group id must be provided. This is because a consistency " +"group can support more than one volume type." msgstr "" -#: ../compute-manage-logs.rst:142 -msgid "**Configuring read-write serial console access**" +#: ../blockstorage-consistency-groups.rst:221 +msgid "**Create a snapshot for a consistency group**::" msgstr "" -#: ../compute-default-ports.rst:14 -msgid "**Configuring the service-node firewall**" +#: ../blockstorage-consistency-groups.rst:236 +msgid "**Show a snapshot of a consistency group**::" msgstr "" -#: ../compute-configuring-migrations.rst:127 -msgid "**Configuring your system**" +#: ../blockstorage-consistency-groups.rst:240 +msgid "**List consistency group snapshots**::" msgstr "" -#: ../networking_introduction.rst:136 -msgid "**Connection limits**" +#: ../blockstorage-consistency-groups.rst:253 +msgid "**Delete a snapshot of a consistency group**::" msgstr "" -#: ../keystone_integrate_with_ldap.rst:145 -msgid "**Connection pooling for end user authentication**" +#: ../blockstorage-consistency-groups.rst:257 +msgid "**Delete a consistency group**:" msgstr "" -#: ../keystone_integrate_with_ldap.rst:128 -msgid "**Connection pooling**" +#: ../blockstorage-consistency-groups.rst:261 +msgid "" +"The force flag is needed when there are volumes in the consistency group::" msgstr "" -#: ../blockstorage-consistency-groups.rst:302 -msgid "**Create a consistency group from a source consistency group**::" +#: ../blockstorage-consistency-groups.rst:266 +msgid "**Modify a consistency group**::" +msgstr "" + +#: ../blockstorage-consistency-groups.rst:275 +msgid "" +"The parameter ``CG`` is required. It can be a name or UUID of a consistency " +"group. UUID1,UUID2,...... are UUIDs of one or more volumes to be added to " +"the consistency group, separated by commas. Default is None. UUID3," +"UUId4,...... are UUIDs of one or more volumes to be removed from the " +"consistency group, separated by commas. Default is None." msgstr "" #: ../blockstorage-consistency-groups.rst:288 @@ -469,740 +389,1030 @@ msgid "" "group**::" msgstr "" -#: ../blockstorage-consistency-groups.rst:125 -msgid "**Create a consistency group**::" -msgstr "" - -#: ../blockstorage-consistency-groups.rst:221 -msgid "**Create a snapshot for a consistency group**::" -msgstr "" - -#: ../database.rst:41 -msgid "**Create a trove image**" -msgstr "" - -#: ../blockstorage-consistency-groups.rst:180 -msgid "**Create a volume and add it to a consistency group**:" -msgstr "" - -#: ../database.rst:95 -msgid "**Create the datastore**" -msgstr "" - -#: ../keystone_integrate_with_ldap.rst:112 -msgid "**Debug**" -msgstr "" - -#: ../keystone_use_trusts.rst:45 -msgid "**Delegation depth**" -msgstr "" - -#: ../blockstorage-consistency-groups.rst:257 -msgid "**Delete a consistency group**:" -msgstr "" - -#: ../blockstorage-consistency-groups.rst:253 -msgid "**Delete a snapshot of a consistency group**::" -msgstr "" - -#: ../telemetry-data-collection.rst:816 -msgid "**Delta transformer**" -msgstr "" - -#: ../compute-remote-console-access.rst:0 -msgid "**Description of SPICE configuration options**" -msgstr "" - -#: ../compute-remote-console-access.rst:0 -msgid "**Description of VNC configuration options**" -msgstr "" - -#: ../objectstorage-troubleshoot.rst:0 +#: ../blockstorage-consistency-groups.rst:296 msgid "" -"**Description of configuration options for [drive-audit] in drive-audit." -"conf**" +"The parameter ``CGSNAPSHOT`` is a name or UUID of a snapshot of a " +"consistency group::" msgstr "" -#: ../compute-security.rst:0 -msgid "**Description of trusted computing configuration options**" +#: ../blockstorage-consistency-groups.rst:302 +msgid "**Create a consistency group from a source consistency group**::" msgstr "" -#: ../networking_multi-dhcp-agents.rst:452 -msgid "**Disable and remove an agent**" -msgstr "" - -#: ../keystone_use_trusts.rst:55 -msgid "**Duration**" -msgstr "" - -#: ../compute-security.rst:148 -msgid "**Enabling SSL encryption**" -msgstr "" - -#: ../keystone_use_trusts.rst:53 -msgid "**Endpoints**" -msgstr "" - -#: ../compute_arch.rst:129 -msgid "**Ephemeral storage**" -msgstr "" - -#: ../networking_auth.rst:75 +#: ../blockstorage-consistency-groups.rst:309 msgid "" -"**Field-based rules** evaluate successfully if a field of the resource " -"specified in the current request matches a specific value. For instance ``" -"\"field:networks:shared=True\"`` is successful if the ``shared`` attribute " -"of the ``network`` resource is set to true." +"The parameter ``SOURCECG`` is a name or UUID of a source consistency group::" msgstr "" -#: ../compute-root-wrap-reference.rst:0 -msgid "**Filters configuration options**" +#: ../blockstorage-driver-filter-weighing.rst:6 +msgid "Configure and use driver filter and weighing for scheduler" msgstr "" -#: ../networking_adv-features.rst:94 -msgid "**GRE network**" -msgstr "" - -#: ../networking_auth.rst:80 +#: ../blockstorage-driver-filter-weighing.rst:8 msgid "" -"**Generic rules** compare an attribute in the resource with an attribute " -"extracted from the user's security credentials and evaluates successfully if " -"the comparison is successful. For instance ``\"tenant_id:%(tenant_id)s\"`` " -"is successful if the tenant identifier in the resource is equal to the " -"tenant identifier of the user submitting the request." +"OpenStack Block Storage enables you to choose a volume back end based on " +"back-end specific properties by using the DriverFilter and GoodnessWeigher " +"for the scheduler. The driver filter and weigher scheduling can help ensure " +"that the scheduler chooses the best back end based on requested volume " +"properties as well as various back-end specific properties." msgstr "" -#: ../networking_multi-dhcp-agents.rst:381 -msgid "**HA of DHCP agents**" +#: ../blockstorage-driver-filter-weighing.rst:16 +msgid "What is driver filter and weigher and when to use it" msgstr "" -#: ../networking_multi-dhcp-agents.rst:130 -msgid "**HostA and HostB: DHCP agent**" -msgstr "" - -#: ../networking_multi-dhcp-agents.rst:85 -msgid "**HostA and HostB: L2 agent**" -msgstr "" - -#: ../networking_multi-dhcp-agents.rst:51 -msgid "**Hosts for demo**" -msgstr "" - -#: ../compute-configuring-migrations.rst:66 -msgid "**Hypervisor:** KVM with libvirt" -msgstr "" - -#: ../compute-networking-nova.rst:271 -msgid "**IPv6 configuration options**" -msgstr "" - -#: ../compute-flavors.rst:34 -msgid "**Identity Service configuration file sections**" -msgstr "" - -#: ../compute-configuring-migrations.rst:74 -msgid "**Instances:** Instance can be migrated with iSCSI-based volumes." -msgstr "" - -#: ../networking_adv-config.rst:34 -msgid "**Linux Bridge**" -msgstr "" - -#: ../blockstorage-consistency-groups.rst:240 -msgid "**List consistency group snapshots**::" -msgstr "" - -#: ../blockstorage-consistency-groups.rst:169 -msgid "**List consistency groups**::" -msgstr "" - -#: ../compute-configuring-migrations.rst:29 +#: ../blockstorage-driver-filter-weighing.rst:18 msgid "" -"**Live migration** (or 'true live migration'). Almost no instance downtime. " -"Useful when the instances must be kept running during the migration. The " -"different types of live migration are:" +"The driver filter and weigher gives you the ability to more finely control " +"how the OpenStack Block Storage scheduler chooses the best back end to use " +"when handling a volume request. One example scenario where using the driver " +"filter and weigher can be if a back end that utilizes thin-provisioning is " +"used. The default filters use the ``free capacity`` property to determine " +"the best back end, but that is not always perfect. If a back end has the " +"ability to provide a more accurate back-end specific value you can use that " +"as part of the weighing. Another example of when the driver filter and " +"weigher can prove useful is if a back end exists where there is a hard limit " +"of 1000 volumes. The maximum volume size is 500 GB. Once 75% of the total " +"space is occupied the performance of the back end degrades. The driver " +"filter and weigher can provide a way for these limits to be checked for." msgstr "" -#: ../database.rst:209 -msgid "**Load validation rules for configuration groups**" +#: ../blockstorage-driver-filter-weighing.rst:33 +msgid "Enable driver filter and weighing" msgstr "" -#: ../telemetry-alarms.rst:99 -msgid "**Log actions**" -msgstr "" - -#: ../networking_multi-dhcp-agents.rst:181 -msgid "**Manage agents in neutron deployment**" -msgstr "" - -#: ../networking_multi-dhcp-agents.rst:310 -msgid "**Manage assignment of networks to DHCP agent**" -msgstr "" - -#: ../networking_introduction.rst:129 -msgid "**Management**" -msgstr "" - -#: ../compute-manage-the-cloud.rst:19 -msgid "**Managing the cloud with nova client**" -msgstr "" - -#: ../compute_arch.rst:312 -msgid "**Message queue**" -msgstr "" - -#: ../telemetry-measurements.rst:99 ../telemetry-measurements.rst:432 -#: ../telemetry-measurements.rst:666 ../telemetry-measurements.rst:699 -#: ../telemetry-measurements.rst:754 ../telemetry-measurements.rst:912 -#: ../telemetry-measurements.rst:975 ../telemetry-measurements.rst:1255 -#: ../telemetry-measurements.rst:1324 -msgid "**Meters added in the Icehouse release or earlier**" -msgstr "" - -#: ../telemetry-measurements.rst:486 ../telemetry-measurements.rst:530 -#: ../telemetry-measurements.rst:707 ../telemetry-measurements.rst:841 -#: ../telemetry-measurements.rst:1061 ../telemetry-measurements.rst:1139 -#: ../telemetry-measurements.rst:1204 ../telemetry-measurements.rst:1281 -msgid "**Meters added in the Juno release**" -msgstr "" - -#: ../telemetry-measurements.rst:539 ../telemetry-measurements.rst:591 -#: ../telemetry-measurements.rst:715 ../telemetry-measurements.rst:804 -#: ../telemetry-measurements.rst:894 ../telemetry-measurements.rst:1095 -#: ../telemetry-measurements.rst:1150 ../telemetry-measurements.rst:1214 -#: ../telemetry-measurements.rst:1304 -msgid "**Meters added in the Kilo release**" -msgstr "" - -#: ../telemetry-measurements.rst:353 -msgid "**Meters added in the Liberty release**" -msgstr "" - -#: ../telemetry-measurements.rst:198 -msgid "**Meters added or hypervisor support changed in the Juno release**" -msgstr "" - -#: ../telemetry-measurements.rst:288 -msgid "**Meters added or hypervisor support changed in the Kilo release**" -msgstr "" - -#: ../telemetry-measurements.rst:346 -msgid "**Meters deprecated in the Kilo release**" -msgstr "" - -#: ../compute-live-migration-usage.rst:22 -msgid "**Migrating instances**" -msgstr "" - -#: ../blockstorage-consistency-groups.rst:266 -msgid "**Modify a consistency group**::" -msgstr "" - -#: ../networking_introduction.rst:124 -msgid "**Monitors**" -msgstr "" - -#: ../telemetry-data-collection.rst:772 -msgid "**Muli meter arithmetic transformer**" -msgstr "" - -#: ../compute_arch.rst:351 -msgid "**Network Controller**" -msgstr "" - -#: ../networking_introduction.rst:31 -msgid "**Network**" -msgstr "" - -#: ../networking_introduction.rst:43 -msgid "**Networking resources**" -msgstr "" - -#: ../telemetry-measurements.rst:575 -msgid "**New Name**" -msgstr "" - -#: ../compute-configuring-migrations.rst:24 +#: ../blockstorage-driver-filter-weighing.rst:35 msgid "" -"**Non-live migration** (sometimes referred to simply as 'migration'). The " -"instance is shut down for a period of time to be moved to another " -"hypervisor. In this case, the instance recognizes that it was rebooted." +"To enable the driver filter, set the ``scheduler_default_filters`` option in " +"the :file:`cinder.conf` file to ``DriverFilter`` or add it to the list if " +"other filters are already present." msgstr "" -#: ../compute-configuring-migrations.rst:76 -msgid "**Notes**" -msgstr "" - -#: ../objectstorage_arch.rst:65 -msgid "**Object Storage (swift)**" -msgstr "" - -#: ../objectstorage_arch.rst:20 -msgid "**Object Storage architecture**" -msgstr "" - -#: ../objectstorage_components.rst:32 -msgid "**Object Storage building blocks**" -msgstr "" - -#: ../objectstorage_components.rst:270 -msgid "**Object Storage in use**" -msgstr "" - -#: ../objectstorage_components.rst:22 -msgid "**Objects.** The data itself." -msgstr "" - -#: ../networking_adv-config.rst:28 -msgid "**Open vSwitch**" -msgstr "" - -#: ../networking_auth.rst:24 +#: ../blockstorage-driver-filter-weighing.rst:39 msgid "" -"**Operation-based** policies specify access criteria for specific " -"operations, possibly with fine-grained control over specific attributes." +"To enable the goodness filter as a weigher, set the " +"``scheduler_default_weighers`` option in the :file:`cinder.conf` file to " +"``GoodnessWeigher`` or add it to the list if other weighers are already " +"present." msgstr "" -#: ../database.rst:201 +#: ../blockstorage-driver-filter-weighing.rst:44 msgid "" -"**Optional.** Set your new version as the default version. To do this, use " -"the trove-manage :command:`datastore_update` command again, this time " -"specifying the version you just created." +"You can choose to use the ``DriverFilter`` without the ``GoodnessWeigher`` " +"or vice-versa. The filter and weigher working together, however, create the " +"most benefits when helping the scheduler choose an ideal back end." msgstr "" -#: ../keystone_configure_with_SSL.rst:53 -msgid "**Options**" -msgstr "" - -#: ../telemetry-measurements.rst:575 -msgid "**Original Name**" -msgstr "" - -#: ../objectstorage_components.rst:197 -msgid "**Partitions**" -msgstr "" - -#: ../objectstorage_components.rst:24 +#: ../blockstorage-driver-filter-weighing.rst:51 msgid "" -"**Partitions.** A partition stores objects, account databases, and container " -"databases and helps manage locations where data lives in the cluster." +"The support for the ``DriverFilter`` and ``GoodnessWeigher`` is optional for " +"back ends. If you are using a back end that does not support the filter and " +"weigher functionality you may not get the full benefit." msgstr "" -#: ../compute-admin-password-injection.rst:61 -msgid "**Password injection and Windows images (all hypervisors)**" +# #-#-#-#-# blockstorage-driver-filter-weighing.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +# #-#-#-#-# blockstorage_image_volume_cache.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +#: ../blockstorage-driver-filter-weighing.rst:56 +#: ../blockstorage_image_volume_cache.rst:36 +msgid "Example :file:`cinder.conf` configuration file::" msgstr "" -#: ../compute-admin-password-injection.rst:55 -msgid "**Password injection and XenAPI (XenServer/XCP)**" -msgstr "" - -#: ../compute-admin-password-injection.rst:33 -msgid "**Password injection on libvirt-based hypervisors**" -msgstr "" - -#: ../compute-admin-password-injection.rst:13 -msgid "**Password injection using the dashboard**" -msgstr "" - -#: ../compute_arch.rst:159 -msgid "**Persistent volume**" -msgstr "" - -#: ../networking_introduction.rst:37 -msgid "**Port**" -msgstr "" - -#: ../compute-configuring-migrations.rst:64 -#: ../compute-configuring-migrations.rst:333 -msgid "**Prerequisites**" -msgstr "" - -#: ../keystone_use_trusts.rst:32 -msgid "**Privileges**" -msgstr "" - -#: ../networking_adv-features.rst:44 -msgid "**Provider extension terminology**" -msgstr "" - -#: ../networking_adv-features.rst:0 -msgid "**Provider network attributes**" -msgstr "" - -#: ../objectstorage_components.rst:8 -msgid "**Proxy servers.** Handle all of the incoming API requests." -msgstr "" - -#: ../compute-remote-console-access.rst:315 +#: ../blockstorage-driver-filter-weighing.rst:63 msgid "" -"**Q: How do I adjust the dimensions of the VNC window image in the OpenStack " -"dashboard?**" +"It is useful to use the other filters and weighers available in OpenStack in " +"combination with these custom ones. For example, the ``CapacityFilter`` and " +"``CapacityWeigher`` can be combined with these." msgstr "" -#: ../compute-remote-console-access.rst:264 +#: ../blockstorage-driver-filter-weighing.rst:69 +msgid "Defining your own filter and goodness functions" +msgstr "" + +#: ../blockstorage-driver-filter-weighing.rst:71 msgid "" -"**Q: I want VNC support in the OpenStack dashboard. What services do I need?" -"**" +"You can define your own filter and goodness functions through the use of " +"various properties that OpenStack Block Storage has exposed. Properties " +"exposed include information about the volume request being made, ``volume" +"\\_type`` settings, and back-end specific information about drivers. All of " +"these allow for a lot of control over how the ideal back end for a volume " +"request will be decided." msgstr "" -#: ../compute-remote-console-access.rst:277 +#: ../blockstorage-driver-filter-weighing.rst:78 msgid "" -"**Q: My VNC proxy worked fine during my all-in-one test, but now it doesn't " -"work on multi host. Why?**" +"The ``filter_function`` option is a string defining an equation that will " +"determine whether a back end should be considered as a potential candidate " +"in the scheduler." msgstr "" -#: ../compute-remote-console-access.rst:330 +#: ../blockstorage-driver-filter-weighing.rst:82 msgid "" -"**Q: My noVNC connections failed with ValidationError: Origin header " -"protocol does not match. Why?**" +"The ``goodness_function`` option is a string defining an equation that will " +"rate the quality of the potential host (0 to 100, 0 lowest, 100 highest)." msgstr "" -#: ../compute-remote-console-access.rst:310 +#: ../blockstorage-driver-filter-weighing.rst:88 msgid "" -"**Q: My noVNC does not work with recent versions of web browsers. Why?**" +"Default values for the filter and goodness functions will be used for each " +"back end if you do not define them yourself. If complete control is desired " +"then a filter and goodness function should be defined for each of the back " +"ends in the :file:`cinder.conf` file." msgstr "" -#: ../compute-remote-console-access.rst:257 +#: ../blockstorage-driver-filter-weighing.rst:95 +msgid "Supported operations in filter and goodness functions" +msgstr "" + +#: ../blockstorage-driver-filter-weighing.rst:97 msgid "" -"**Q: What is the difference between ``nova-xvpvncproxy`` and ``nova-" -"novncproxy``?**" +"Below is a table of all the operations currently usable in custom filter and " +"goodness functions created by you:" msgstr "" -#: ../compute-remote-console-access.rst:270 +#: ../blockstorage-driver-filter-weighing.rst:101 +msgid "Operations" +msgstr "" + +# #-#-#-#-# blockstorage-driver-filter-weighing.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +# #-#-#-#-# compute-manage-logs.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +# #-#-#-#-# networking_adv-features.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +# #-#-#-#-# telemetry-measurements.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +#: ../blockstorage-driver-filter-weighing.rst:101 +#: ../compute-manage-logs.rst:203 ../networking_adv-features.rst:128 +#: ../telemetry-measurements.rst:31 ../telemetry-measurements.rst:97 +#: ../telemetry-measurements.rst:430 ../telemetry-measurements.rst:484 +#: ../telemetry-measurements.rst:528 ../telemetry-measurements.rst:589 +#: ../telemetry-measurements.rst:664 ../telemetry-measurements.rst:697 +#: ../telemetry-measurements.rst:752 ../telemetry-measurements.rst:802 +#: ../telemetry-measurements.rst:839 ../telemetry-measurements.rst:910 +#: ../telemetry-measurements.rst:973 ../telemetry-measurements.rst:1059 +#: ../telemetry-measurements.rst:1137 ../telemetry-measurements.rst:1202 +#: ../telemetry-measurements.rst:1253 ../telemetry-measurements.rst:1279 +#: ../telemetry-measurements.rst:1302 ../telemetry-measurements.rst:1322 +msgid "Type" +msgstr "" + +#: ../blockstorage-driver-filter-weighing.rst:103 +msgid "+, -, \\*, /, ^" +msgstr "" + +#: ../blockstorage-driver-filter-weighing.rst:103 +msgid "standard math" +msgstr "" + +#: ../blockstorage-driver-filter-weighing.rst:105 +msgid "logic" +msgstr "" + +#: ../blockstorage-driver-filter-weighing.rst:105 +msgid "not, and, or, &, \\|, !" +msgstr "" + +#: ../blockstorage-driver-filter-weighing.rst:107 +msgid ">, >=, <, <=, ==, <>, !=" +msgstr "" + +#: ../blockstorage-driver-filter-weighing.rst:107 +msgid "equality" +msgstr "" + +#: ../blockstorage-driver-filter-weighing.rst:109 +msgid "+, -" +msgstr "" + +#: ../blockstorage-driver-filter-weighing.rst:109 +msgid "sign" +msgstr "" + +#: ../blockstorage-driver-filter-weighing.rst:111 +msgid "ternary" +msgstr "" + +#: ../blockstorage-driver-filter-weighing.rst:111 +msgid "x ? a : b" +msgstr "" + +#: ../blockstorage-driver-filter-weighing.rst:113 +msgid "abs(x), max(x, y), min(x, y)" +msgstr "" + +#: ../blockstorage-driver-filter-weighing.rst:113 +msgid "math helper functions" +msgstr "" + +#: ../blockstorage-driver-filter-weighing.rst:118 msgid "" -"**Q: When I use ``nova get-vnc-console`` or click on the VNC tab of the " -"OpenStack dashboard, it hangs. Why?**" +"Syntax errors in filter or goodness strings defined by you will cause errors " +"to be thrown at volume request time." msgstr "" -#: ../keystone_integrate_with_ldap.rst:88 -msgid "**Query option**" +#: ../blockstorage-driver-filter-weighing.rst:122 +msgid "Available properties when creating custom functions" msgstr "" -#: ../database.rst:295 -msgid "**Query routers and config servers**" -msgstr "" - -#: ../networking_adv-features.rst:530 -msgid "**Recommended values for max_lp_per_bridged_ls**" -msgstr "" - -#: ../database.rst:65 -msgid "**Register image with Image service**" -msgstr "" - -#: ../objectstorage_components.rst:231 -msgid "**Replication**" -msgstr "" - -#: ../networking_auth.rst:28 +#: ../blockstorage-driver-filter-weighing.rst:124 msgid "" -"**Resource-based** policies specify whether access to specific resource is " -"granted or not according to the permissions configured for the resource " -"(currently available only for the network resource). The actual " -"authorization policies enforced in Networking might vary from deployment to " -"deployment." +"There are various properties that can be used in either the " +"``filter_function`` or the ``goodness_function`` strings. The properties " +"allow access to volume info, qos settings, extra specs, and so on." msgstr "" -#: ../objectstorage_components.rst:10 -msgid "**Rings.** Map logical names of data to locations on particular disks." -msgstr "" - -#: ../networking_auth.rst:71 +#: ../blockstorage-driver-filter-weighing.rst:128 msgid "" -"**Role-based rules** evaluate successfully if the user who submits the " -"request has the specified role. For instance ``\"role:admin\"`` is " -"successful if the user who submits the request is an administrator." +"The following properties and their sub-properties are currently available " +"for use:" msgstr "" -#: ../compute-system-admin.rst:36 -msgid "**Services**" +#: ../blockstorage-driver-filter-weighing.rst:132 +msgid "Host stats for a back end" msgstr "" -#: ../networking_introduction.rst:141 -msgid "**Session persistence**" +#: ../blockstorage-driver-filter-weighing.rst:134 +msgid "The host's name" msgstr "" -#: ../networking_multi-dhcp-agents.rst:157 -msgid "**Settings**" +#: ../blockstorage-driver-filter-weighing.rst:134 +msgid "host" msgstr "" -#: ../compute-configuring-migrations.rst:339 -msgid "**Shared storage**. An NFS export, visible to all XenServer hosts." +#: ../blockstorage-driver-filter-weighing.rst:137 +msgid "The volume back end name" msgstr "" -#: ../compute-configuring-migrations.rst:33 +#: ../blockstorage-driver-filter-weighing.rst:137 +msgid "volume\\_backend\\_name" +msgstr "" + +#: ../blockstorage-driver-filter-weighing.rst:140 +msgid "The vendor name" +msgstr "" + +#: ../blockstorage-driver-filter-weighing.rst:140 +msgid "vendor\\_name" +msgstr "" + +#: ../blockstorage-driver-filter-weighing.rst:143 +msgid "The driver version" +msgstr "" + +#: ../blockstorage-driver-filter-weighing.rst:143 +msgid "driver\\_version" +msgstr "" + +#: ../blockstorage-driver-filter-weighing.rst:146 +msgid "The storage protocol" +msgstr "" + +#: ../blockstorage-driver-filter-weighing.rst:146 +msgid "storage\\_protocol" +msgstr "" + +#: ../blockstorage-driver-filter-weighing.rst:149 +msgid "Boolean signifying whether QoS is supported" +msgstr "" + +#: ../blockstorage-driver-filter-weighing.rst:149 +msgid "QoS\\_support" +msgstr "" + +#: ../blockstorage-driver-filter-weighing.rst:152 +msgid "The total capacity in GB" +msgstr "" + +#: ../blockstorage-driver-filter-weighing.rst:152 +msgid "total\\_capacity\\_gb" +msgstr "" + +#: ../blockstorage-driver-filter-weighing.rst:155 +msgid "The allocated capacity in GB" +msgstr "" + +#: ../blockstorage-driver-filter-weighing.rst:155 +msgid "allocated\\_capacity\\_gb" +msgstr "" + +#: ../blockstorage-driver-filter-weighing.rst:158 +msgid "The reserved storage percentage" +msgstr "" + +#: ../blockstorage-driver-filter-weighing.rst:158 +msgid "reserved\\_percentage" +msgstr "" + +#: ../blockstorage-driver-filter-weighing.rst:161 +msgid "Capabilities specific to a back end" +msgstr "" + +#: ../blockstorage-driver-filter-weighing.rst:163 msgid "" -"**Shared storage-based live migration**. Both hypervisors have access to " -"shared storage." +"These properties are determined by the specific back end you are creating " +"filter and goodness functions for. Some back ends may not have any " +"properties available here." msgstr "" -#: ../compute-configuring-migrations.rst:68 +#: ../blockstorage-driver-filter-weighing.rst:168 +msgid "Requested volume properties" +msgstr "" + +#: ../blockstorage-driver-filter-weighing.rst:171 +msgid "Status for the requested volume" +msgstr "" + +# #-#-#-#-# blockstorage-driver-filter-weighing.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +# #-#-#-#-# compute-live-migration-usage.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +#: ../blockstorage-driver-filter-weighing.rst:171 +#: ../compute-live-migration-usage.rst:75 +msgid "status" +msgstr "" + +#: ../blockstorage-driver-filter-weighing.rst:174 +msgid "The volume type ID" +msgstr "" + +#: ../blockstorage-driver-filter-weighing.rst:174 +msgid "volume\\_type\\_id" +msgstr "" + +#: ../blockstorage-driver-filter-weighing.rst:177 +msgid "The display name of the volume" +msgstr "" + +#: ../blockstorage-driver-filter-weighing.rst:177 +msgid "display\\_name" +msgstr "" + +#: ../blockstorage-driver-filter-weighing.rst:180 +msgid "Any metadata the volume has" +msgstr "" + +#: ../blockstorage-driver-filter-weighing.rst:180 +msgid "volume\\_metadata" +msgstr "" + +#: ../blockstorage-driver-filter-weighing.rst:183 +msgid "Any reservations the volume has" +msgstr "" + +#: ../blockstorage-driver-filter-weighing.rst:183 +msgid "reservations" +msgstr "" + +#: ../blockstorage-driver-filter-weighing.rst:186 +msgid "The volume's user ID" +msgstr "" + +#: ../blockstorage-driver-filter-weighing.rst:186 +msgid "user\\_id" +msgstr "" + +#: ../blockstorage-driver-filter-weighing.rst:189 +msgid "The attach status for the volume" +msgstr "" + +#: ../blockstorage-driver-filter-weighing.rst:189 +msgid "attach\\_status" +msgstr "" + +#: ../blockstorage-driver-filter-weighing.rst:192 +msgid "The volume's display description" +msgstr "" + +#: ../blockstorage-driver-filter-weighing.rst:192 +msgid "display\\_description" +msgstr "" + +#: ../blockstorage-driver-filter-weighing.rst:195 +msgid "The volume's ID" +msgstr "" + +# #-#-#-#-# blockstorage-driver-filter-weighing.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +# #-#-#-#-# compute-live-migration-usage.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +#: ../blockstorage-driver-filter-weighing.rst:195 +#: ../compute-live-migration-usage.rst:68 +msgid "id" +msgstr "" + +#: ../blockstorage-driver-filter-weighing.rst:198 +msgid "The volume's replication status" +msgstr "" + +#: ../blockstorage-driver-filter-weighing.rst:198 +msgid "replication\\_status" +msgstr "" + +#: ../blockstorage-driver-filter-weighing.rst:201 +msgid "The volume's snapshot ID" +msgstr "" + +#: ../blockstorage-driver-filter-weighing.rst:201 +msgid "snapshot\\_id" +msgstr "" + +#: ../blockstorage-driver-filter-weighing.rst:204 +msgid "The volume's encryption key ID" +msgstr "" + +#: ../blockstorage-driver-filter-weighing.rst:204 +msgid "encryption\\_key\\_id" +msgstr "" + +#: ../blockstorage-driver-filter-weighing.rst:207 +msgid "The source volume ID" +msgstr "" + +#: ../blockstorage-driver-filter-weighing.rst:207 +msgid "source\\_volid" +msgstr "" + +#: ../blockstorage-driver-filter-weighing.rst:210 +msgid "Any admin metadata for this volume" +msgstr "" + +#: ../blockstorage-driver-filter-weighing.rst:210 +msgid "volume\\_admin\\_metadata" +msgstr "" + +#: ../blockstorage-driver-filter-weighing.rst:213 +msgid "The source replication ID" +msgstr "" + +#: ../blockstorage-driver-filter-weighing.rst:213 +msgid "source\\_replicaid" +msgstr "" + +#: ../blockstorage-driver-filter-weighing.rst:216 +msgid "The consistency group ID" +msgstr "" + +#: ../blockstorage-driver-filter-weighing.rst:216 +msgid "consistencygroup\\_id" +msgstr "" + +#: ../blockstorage-driver-filter-weighing.rst:219 +msgid "The size of the volume in GB" +msgstr "" + +#: ../blockstorage-driver-filter-weighing.rst:219 +msgid "size" +msgstr "" + +#: ../blockstorage-driver-filter-weighing.rst:222 +msgid "General metadata" +msgstr "" + +#: ../blockstorage-driver-filter-weighing.rst:222 +msgid "metadata" +msgstr "" + +#: ../blockstorage-driver-filter-weighing.rst:224 msgid "" -"**Shared storage:** :file:`NOVA-INST-DIR/instances/` (for example, :file:`/" -"var/lib/nova/instances`) has to be mounted by shared storage. This guide " -"uses NFS but other options, including the `OpenStack Gluster Connector " -"`_ are " -"available." +"The property most used from here will most likely be the ``size`` sub-" +"property." msgstr "" -#: ../blockstorage-consistency-groups.rst:154 -msgid "**Show a consistency group**::" +#: ../blockstorage-driver-filter-weighing.rst:227 +msgid "Extra specs for the requested volume type" msgstr "" -#: ../blockstorage-consistency-groups.rst:236 -msgid "**Show a snapshot of a consistency group**::" +#: ../blockstorage-driver-filter-weighing.rst:229 +#: ../blockstorage-driver-filter-weighing.rst:236 +msgid "View the available properties for volume types by running::" msgstr "" -#: ../telemetry-data-retrieval.rst:43 -msgid "**Simple query**" +#: ../blockstorage-driver-filter-weighing.rst:234 +msgid "Current QoS specs for the requested volume type" msgstr "" -#: ../compute-security.rst:122 -msgid "**Specifying trusted flavors**" +#: ../blockstorage-driver-filter-weighing.rst:240 +msgid "" +"In order to access these properties in a custom string use the following " +"format:" msgstr "" -#: ../networking_introduction.rst:34 -msgid "**Subnet**" +#: ../blockstorage-driver-filter-weighing.rst:243 +msgid "``.``" msgstr "" -#: ../compute-networking-nova.rst:249 -msgid "**Switch into IPv4/IPv6 dual-stack mode**" +#: ../blockstorage-driver-filter-weighing.rst:246 +msgid "Driver filter and weigher usage examples" msgstr "" -#: ../networking_multi-dhcp-agents.rst:436 -msgid "**Test the HA**" +#: ../blockstorage-driver-filter-weighing.rst:248 +msgid "" +"Below are examples for using the filter and weigher separately, together, " +"and using driver-specific properties." msgstr "" -#: ../objectstorage_components.rst:92 -msgid "**The ring**" +#: ../blockstorage-driver-filter-weighing.rst:251 +msgid "" +"Example :file:`cinder.conf` file configuration for customizing the filter " +"function::" msgstr "" -#: ../blockstorage_backup_disks.rst:44 -msgid "**To back up Block Storage service disks**" +#: ../blockstorage-driver-filter-weighing.rst:268 +msgid "" +"The above example will filter volumes to different back ends depending on " +"the size of the requested volume. Default OpenStack Block Storage scheduler " +"weighing is done. Volumes with a size less than 10 GB are sent to lvm-1 and " +"volumes with a size greater than or equal to 10 GB are sent to lvm-2." msgstr "" -#: ../networking_introduction.rst:217 -msgid "**To configure Firewall-as-a-Service**" +#: ../blockstorage-driver-filter-weighing.rst:274 +msgid "" +"Example :file:`cinder.conf` file configuration for customizing the goodness " +"function::" msgstr "" -#: ../networking_config-agents.rst:327 -msgid "**To configure LBaas with Open vSwitch or Linux Bridge plug-in**" +#: ../blockstorage-driver-filter-weighing.rst:291 +msgid "" +"The above example will determine the goodness rating of a back end based off " +"of the requested volume's size. Default OpenStack Block Storage scheduler " +"filtering is done. The example shows how the ternary if statement can be " +"used in a filter or goodness function. If a requested volume is of size " +"10 GB then lvm-1 is rated as 50 and lvm-2 is rated as 100. In this case " +"lvm-2 wins. If a requested volume is of size 3 GB then lvm-1 is rated 100 " +"and lvm-2 is rated 25. In this case lvm-1 would win." msgstr "" -#: ../keystone_secure_identity_to_ldap_backend.rst:12 -msgid "**To configure TLS encryption on LDAP traffic**" +#: ../blockstorage-driver-filter-weighing.rst:299 +msgid "" +"Example :file:`cinder.conf` file configuration for customizing both the " +"filter and goodness functions::" msgstr "" -#: ../compute-images-instances.rst:174 -msgid "**To configure property protection**" +#: ../blockstorage-driver-filter-weighing.rst:319 +msgid "" +"The above example combines the techniques from the first two examples. The " +"best back end is now decided based off of the total capacity of the back end " +"and the requested volume's size." msgstr "" -#: ../objectstorage_tenant_specific_image_storage.rst:15 -msgid "**To configure tenant-specific image locations**" +#: ../blockstorage-driver-filter-weighing.rst:323 +msgid "" +"Example :file:`cinder.conf` file configuration for accessing driver specific " +"properties::" msgstr "" -#: ../networking_config-identity.rst:5 -msgid "**To configure the Identity service for use with Networking**" +#: ../blockstorage-driver-filter-weighing.rst:351 +msgid "" +"The above is an example of how back-end specific properties can be used in " +"the filter and goodness functions. In this example the LVM driver's " +"``total_volumes`` capability is being used to determine which host gets used " +"during a volume request. In the above example, lvm-1 and lvm-2 will handle " +"volume requests for all volumes with a size less than 5 GB. The lvm-1 host " +"will have priority until it contains three or more volumes. After than lvm-2 " +"will have priority until it contains eight or more volumes. The lvm-3 will " +"collect all volumes greater or equal to 5 GB as well as all volumes once " +"lvm-1 and lvm-2 lose priority." msgstr "" -#: ../database.rst:39 -msgid "**To create a datastore**" +#: ../blockstorage-lio-iscsi-support.rst:3 +msgid "Use LIO iSCSI support" +msgstr "" + +#: ../blockstorage-lio-iscsi-support.rst:5 +msgid "" +"The default mode for the ``iscsi_helper`` tool is ``tgtadm``. To use LIO " +"iSCSI, install the ``python-rtslib`` package, and set " +"``iscsi_helper=lioadm`` in the :file:`cinder.conf` file." +msgstr "" + +#: ../blockstorage-lio-iscsi-support.rst:9 +msgid "" +"Once configured, you can use the :command:`cinder-rtstool` command to manage " +"the volumes. This command enables you to create, delete, and verify volumes " +"and determine targets and add iSCSI initiators to the system." +msgstr "" + +# #-#-#-#-# blockstorage-manage-volumes.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +# #-#-#-#-# compute-manage-volumes.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +#: ../blockstorage-manage-volumes.rst:3 ../compute-manage-volumes.rst:3 +msgid "Manage volumes" +msgstr "" + +#: ../blockstorage-manage-volumes.rst:5 +msgid "" +"The default OpenStack Block Storage service implementation is an iSCSI " +"solution that uses Logical Volume Manager (LVM) for Linux." +msgstr "" + +#: ../blockstorage-manage-volumes.rst:10 +msgid "" +"The OpenStack Block Storage service is not a shared storage solution like a " +"Network Attached Storage (NAS) of NFS volumes, where you can attach a volume " +"to multiple servers. With the OpenStack Block Storage service, you can " +"attach a volume to only one instance at a time." +msgstr "" + +#: ../blockstorage-manage-volumes.rst:16 +msgid "" +"The OpenStack Block Storage service also provides drivers that enable you to " +"use several vendors' back-end storage devices, in addition to or instead of " +"the base LVM implementation." +msgstr "" + +#: ../blockstorage-manage-volumes.rst:20 +msgid "" +"This high-level procedure shows you how to create and attach a volume to a " +"server instance." msgstr "" #: ../blockstorage-manage-volumes.rst:23 msgid "**To create and attach a volume to an instance**" msgstr "" -#: ../keystone_integrate_with_ldap.rst:57 -msgid "**To define the destination LDAP server**" -msgstr "" - -#: ../networking_introduction.rst:170 -msgid "**To enable FWaaS**" -msgstr "" - -#: ../networking_config-agents.rst:62 -msgid "**To install and configure the DHCP agent**" -msgstr "" - -#: ../networking_config-agents.rst:191 -msgid "**To install the L3 agent for all other plug-ins**" -msgstr "" - -#: ../networking_config-agents.rst:426 +#: ../blockstorage-manage-volumes.rst:25 msgid "" -"**To install the OpenStack Networking Hyper-V agent and configure the node**" +"Configure the OpenStack Compute and the OpenStack Block Storage services " +"through the :file:`cinder.conf` file." msgstr "" -#: ../networking_config-agents.rst:274 -msgid "**To install the metering agent and configure the node**" -msgstr "" - -#: ../keystone_integrate_assignment_backend_ldap.rst:27 -msgid "**To integrate assignment back ends with LDAP**" -msgstr "" - -#: ../keystone_integrate_identity_backend_ldap.rst:76 -msgid "**To integrate multiple Identity back ends with LDAP**" -msgstr "" - -#: ../keystone_integrate_identity_backend_ldap.rst:17 -msgid "**To integrate one Identity back end with LDAP**" -msgstr "" - -#: ../networking_config-agents.rst:38 -msgid "**To set up each node for the NSX plug-in**" -msgstr "" - -#: ../keystone_use_trusts.rst:19 -msgid "**Trustee**" -msgstr "" - -#: ../keystone_use_trusts.rst:11 -msgid "**Trustor**" -msgstr "" - -#: ../telemetry-data-collection.rst:695 -msgid "**Unit conversion transformer**" -msgstr "" - -#: ../keystone_use_trusts.rst:24 -msgid "**User ID**" -msgstr "" - -#: ../compute-configuring-migrations.rst:352 -msgid "**Using shared storage live migrations with XenServer Hypervisors**" -msgstr "" - -#: ../networking_adv-features.rst:73 -msgid "**VLAN network**" -msgstr "" - -#: ../database.rst:266 -msgid "**Validate datastore**" -msgstr "" - -#: ../networking_adv-features.rst:101 -msgid "**Virtual Extensible LAN (VXLAN) network**" -msgstr "" - -#: ../compute-configuring-migrations.rst:40 +#: ../blockstorage-manage-volumes.rst:27 msgid "" -"**Volume-backed live migration**. Instances are backed by volumes rather " -"than ephemeral disk, no shared storage is required, and migration is " -"supported (currently only available for libvirt-based hypervisors)." +"Use the :command:`cinder create` command to create a volume. This command " +"creates an LV into the volume group (VG) ``cinder-volumes``." msgstr "" -#: ../telemetry-alarms.rst:92 -msgid "**Webhooks**" -msgstr "" - -#: ../objectstorage_components.rst:141 -msgid "**Zones**" -msgstr "" - -#: ../objectstorage_components.rst:13 +#: ../blockstorage-manage-volumes.rst:29 msgid "" -"**Zones.** Isolate data from other zones. A failure in one zone doesn't " -"impact the rest of the cluster because data is replicated across zones." +"Use the nova :command:`volume-attach` command to attach the volume to an " +"instance. This command creates a unique iSCSI IQN that is exposed to the " +"compute node." msgstr "" -#: ../compute-remote-console-access.rst:154 -msgid "**[DEFAULT]**" -msgstr "" - -#: ../compute-remote-console-access.rst:172 -msgid "**[vmware]**" -msgstr "" - -#: ../compute-remote-console-access.rst:178 -msgid "**[vnc]**" -msgstr "" - -#: ../networking_multi-dhcp-agents.rst:56 -msgid "**controlnode: neutron server**" -msgstr "" - -#: ../networking_arch.rst:37 -msgid "**dhcp agent** (``neutron-dhcp-agent``)" -msgstr "" - -#: ../compute-service-groups.rst:66 -msgid "**evzookeeper**" -msgstr "" - -#: ../networking_adv-features.rst:84 -msgid "**flat network**" -msgstr "" - -#: ../networking_arch.rst:41 -msgid "**l3 agent** (``neutron-l3-agent``)" -msgstr "" - -#: ../networking_adv-features.rst:89 -msgid "**local network**" -msgstr "" - -#: ../networking_arch.rst:46 -msgid "**metering agent** (``neutron-metering-agent``)" -msgstr "" - -#: ../compute-live-migration-usage.rst:0 -msgid "**nova service-list**" -msgstr "" - -#: ../compute-manage-volumes.rst:0 -msgid "**nova volume commands**" -msgstr "" - -#: ../networking_config-identity.rst:0 -msgid "**nova.conf API and credential settings**" -msgstr "" - -#: ../networking_config-identity.rst:229 -msgid "**nova.conf metadata settings**" -msgstr "" - -#: ../networking_config-identity.rst:204 -msgid "**nova.conf security group settings**" -msgstr "" - -#: ../networking_adv-features.rst:56 -msgid "**physical network**" -msgstr "" - -#: ../networking_arch.rst:31 -msgid "**plug-in agent** (``neutron-*-agent``)" -msgstr "" - -#: ../networking_adv-features.rst:67 -msgid "**provider network**" -msgstr "" - -#: ../compute-service-groups.rst:63 -msgid "**python-zookeeper**" -msgstr "" - -#: ../compute-root-wrap-reference.rst:0 -msgid "**rootwrap.conf configuration options**" -msgstr "" - -#: ../networking_adv-features.rst:63 -msgid "**tenant network**" -msgstr "" - -#: ../networking_adv-features.rst:49 -msgid "**virtual network**" -msgstr "" - -#: ../ts-eql-volume-size.rst:113 -msgid "*1085276160*" -msgstr "" - -#: ../blockstorage_get_capabilities.rst:21 +#: ../blockstorage-manage-volumes.rst:33 msgid "" -"*Capabilities:* What the current deployed back end in Cinder is able to do. " -"These correspond to extra specs." +"The compute node, which runs the instance, now has an active iSCSI session " +"and new local storage (usually a :file:`/dev/sdX` disk)." +msgstr "" + +#: ../blockstorage-manage-volumes.rst:36 +msgid "" +"Libvirt uses that local storage as storage for the instance. The instance " +"gets a new disk (usually a :file:`/dev/vdX` disk)." +msgstr "" + +#: ../blockstorage-manage-volumes.rst:39 +msgid "" +"For this particular walk through, one cloud controller runs ``nova-api``, " +"``nova-scheduler``, ``nova-objectstore``, ``nova-network`` and ``cinder-*`` " +"services. Two additional compute nodes run ``nova-compute``. The walk " +"through uses a custom partitioning scheme that carves out 60 GB of space and " +"labels it as LVM. The network uses the ``FlatManager`` and " +"``NetworkManager`` settings for OpenStack Compute." +msgstr "" + +#: ../blockstorage-manage-volumes.rst:47 +msgid "" +"The network mode does not interfere with OpenStack Block Storage operations, " +"but you must set up networking for Block Storage to work. For details, see :" +"ref:`networking`." +msgstr "" + +#: ../blockstorage-manage-volumes.rst:51 +msgid "" +"To set up Compute to use volumes, ensure that Block Storage is installed " +"along with ``lvm2``. This guide describes how to troubleshoot your " +"installation and back up your Compute volumes." +msgstr "" + +#: ../blockstorage-troubleshoot.rst:3 +msgid "Troubleshoot your installation" +msgstr "" + +#: ../blockstorage-troubleshoot.rst:5 +msgid "" +"This section provides useful tips to help you troubleshoot your Block " +"Storage installation." +msgstr "" + +# #-#-#-#-# blockstorage.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +# #-#-#-#-# compute-images-instances.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +#: ../blockstorage.rst:5 ../compute-images-instances.rst:130 +msgid "Block Storage" +msgstr "" + +#: ../blockstorage.rst:7 +msgid "" +"The OpenStack Block Storage service works through the interaction of a " +"series of daemon processes named ``cinder-*`` that reside persistently on " +"the host machine or machines. The binaries can all be run from a single " +"node, or spread across multiple nodes. They can also be run on the same node " +"as other OpenStack services." +msgstr "" + +#: ../blockstorage.rst:13 +msgid "" +"To administer the OpenStack Block Storage service, it is helpful to " +"understand a number of concepts. You must make certain choices when you " +"configure the Block Storage service in OpenStack. The bulk of the options " +"come down to two choices, single node or multi-node install. You can read a " +"longer discussion about `Storage Decisions`_ in the `OpenStack Operations " +"Guide`_." +msgstr "" + +#: ../blockstorage.rst:20 +msgid "" +"OpenStack Block Storage enables you to add extra block-level storage to your " +"OpenStack Compute instances. This service is similar to the Amazon EC2 " +"Elastic Block Storage (EBS) offering." +msgstr "" + +#: ../blockstorage_backup_disks.rst:3 +msgid "Back up Block Storage service disks" +msgstr "" + +#: ../blockstorage_backup_disks.rst:5 +msgid "" +"While you can use the LVM snapshot to create snapshots, you can also use it " +"to back up your volumes. By using LVM snapshot, you reduce the size of the " +"backup; only existing data is backed up instead of the entire volume." +msgstr "" + +#: ../blockstorage_backup_disks.rst:10 +msgid "" +"To back up a volume, you must create a snapshot of it. An LVM snapshot is " +"the exact copy of a logical volume, which contains data in a frozen state. " +"This prevents data corruption, because data cannot be manipulated during the " +"volume creation process. Remember that the volumes created through a :" +"command:`nova volume-create` command exist in an LVM logical volume." +msgstr "" + +#: ../blockstorage_backup_disks.rst:17 +msgid "" +"You must also make sure that the operating system is not using the volume, " +"and that all data has been flushed on the guest file systems. This usually " +"means that those file systems have to be unmounted during the snapshot " +"creation. They can be mounted again as soon as the logical volume snapshot " +"has been created." +msgstr "" + +#: ../blockstorage_backup_disks.rst:23 +msgid "" +"Before you create the snapshot, you must have enough space to save it. As a " +"precaution, you should have at least twice as much space as the potential " +"snapshot size. If insufficient space is available, the snapshot might become " +"corrupted." +msgstr "" + +#: ../blockstorage_backup_disks.rst:28 +msgid "" +"For this example, assume that a 100 GB volume named ``volume-00000001`` was " +"created for an instance while only 4 GB are used. This example uses these " +"commands to back up only those 4 GB:" +msgstr "" + +#: ../blockstorage_backup_disks.rst:32 +msgid ":command:`lvm2` command. Directly manipulates the volumes." +msgstr "" + +#: ../blockstorage_backup_disks.rst:34 +msgid "" +":command:`kpartx` command. Discovers the partition table created inside the " +"instance." +msgstr "" + +#: ../blockstorage_backup_disks.rst:37 +msgid ":command:`tar` command. Creates a minimum-sized backup." +msgstr "" + +#: ../blockstorage_backup_disks.rst:39 +msgid "" +":command:`sha1sum` command. Calculates the backup checksum to check its " +"consistency." +msgstr "" + +#: ../blockstorage_backup_disks.rst:42 +msgid "You can apply this process to volumes of any size." +msgstr "" + +#: ../blockstorage_backup_disks.rst:44 +msgid "**To back up Block Storage service disks**" +msgstr "" + +#: ../blockstorage_backup_disks.rst:46 +msgid "Create a snapshot of a used volume" +msgstr "" + +#: ../blockstorage_backup_disks.rst:48 +msgid "Use this command to list all volumes" +msgstr "" + +#: ../blockstorage_backup_disks.rst:54 +msgid "" +"Create the snapshot; you can do this while the volume is attached to an " +"instance::" +msgstr "" + +#: ../blockstorage_backup_disks.rst:60 +msgid "" +"Use the :option:`--snapshot` configuration option to tell LVM that you want " +"a snapshot of an already existing volume. The command includes the size of " +"the space reserved for the snapshot volume, the name of the snapshot, and " +"the path of an already existing volume. Generally, this path is :file:`/dev/" +"cinder-volumes/VOLUME_NAME`." +msgstr "" + +#: ../blockstorage_backup_disks.rst:66 +msgid "" +"The size does not have to be the same as the volume of the snapshot. The :" +"option:`--size` parameter defines the space that LVM reserves for the " +"snapshot volume. As a precaution, the size should be the same as that of the " +"original volume, even if the whole space is not currently used by the " +"snapshot." +msgstr "" + +#: ../blockstorage_backup_disks.rst:72 +msgid "Run the :command:`lvdisplay` command again to verify the snapshot::" +msgstr "" + +#: ../blockstorage_backup_disks.rst:111 +msgid "Partition table discovery" +msgstr "" + +#: ../blockstorage_backup_disks.rst:113 +msgid "" +"To exploit the snapshot with the :command:`tar` command, mount your " +"partition on the Block Storage service server." +msgstr "" + +#: ../blockstorage_backup_disks.rst:116 +msgid "" +"The :command:`kpartx` utility discovers and maps table partitions. You can " +"use it to view partitions that are created inside the instance. Without " +"using the partitions created inside instances, you cannot see its content " +"and create efficient backups." +msgstr "" + +#: ../blockstorage_backup_disks.rst:127 +msgid "" +"On a Debian-based distribution, you can use the :command:`apt-get install " +"kpartx` command to install :command:`kpartx`." +msgstr "" + +#: ../blockstorage_backup_disks.rst:131 +msgid "" +"If the tools successfully find and map the partition table, no errors are " +"returned." +msgstr "" + +#: ../blockstorage_backup_disks.rst:134 +msgid "To check the partition table map, run this command::" +msgstr "" + +#: ../blockstorage_backup_disks.rst:138 +msgid "" +"You can see the ``cinder--volumes-volume--00000001--snapshot1`` partition." +msgstr "" + +#: ../blockstorage_backup_disks.rst:141 +msgid "" +"If you created more than one partition on that volume, you see several " +"partitions; for example: ``cinder--volumes-volume--00000001--snapshot2``, " +"``cinder--volumes-volume--00000001--snapshot3``, and so on." +msgstr "" + +#: ../blockstorage_backup_disks.rst:146 +msgid "Mount your partition" +msgstr "" + +#: ../blockstorage_backup_disks.rst:152 +msgid "If the partition mounts successfully, no errors are returned." +msgstr "" + +#: ../blockstorage_backup_disks.rst:154 +msgid "" +"You can directly access the data inside the instance. If a message prompts " +"you for a partition or you cannot mount it, determine whether enough space " +"was allocated for the snapshot or the :command:`kpartx` command failed to " +"discover the partition table." +msgstr "" + +#: ../blockstorage_backup_disks.rst:159 +msgid "Allocate more space to the snapshot and try the process again." +msgstr "" + +#: ../blockstorage_backup_disks.rst:161 +msgid "Use the :command:`tar` command to create archives" +msgstr "" + +#: ../blockstorage_backup_disks.rst:163 +msgid "Create a backup of the volume::" +msgstr "" + +#: ../blockstorage_backup_disks.rst:168 +msgid "" +"This command creates a :file:`tar.gz` file that contains the data, *and data " +"only*. This ensures that you do not waste space by backing up empty sectors." +msgstr "" + +#: ../blockstorage_backup_disks.rst:172 +msgid "Checksum calculation I" +msgstr "" + +#: ../blockstorage_backup_disks.rst:174 +msgid "" +"You should always have the checksum for your backup files. When you transfer " +"the same file over the network, you can run a checksum calculation to ensure " +"that your file was not corrupted during its transfer. The checksum is a " +"unique ID for a file. If the checksums are different, the file is corrupted." +msgstr "" + +#: ../blockstorage_backup_disks.rst:180 +msgid "" +"Run this command to run a checksum for your file and save the result to a " +"file::" +msgstr "" + +#: ../blockstorage_backup_disks.rst:187 +msgid "" +"Use the :command:`sha1sum` command carefully because the time it takes to " +"complete the calculation is directly proportional to the size of the file." +msgstr "" + +#: ../blockstorage_backup_disks.rst:191 +msgid "" +"For files larger than around 4 to 6 GB, and depending on your CPU, the " +"process might take a long time." +msgstr "" + +#: ../blockstorage_backup_disks.rst:194 +msgid "After work cleaning" +msgstr "" + +#: ../blockstorage_backup_disks.rst:196 +msgid "" +"Now that you have an efficient and consistent backup, use this command to " +"clean up the file system:" +msgstr "" + +#: ../blockstorage_backup_disks.rst:199 +msgid "Unmount the volume::" +msgstr "" + +#: ../blockstorage_backup_disks.rst:203 +msgid "Delete the partition table::" +msgstr "" + +#: ../blockstorage_backup_disks.rst:207 +msgid "Remove the snapshot::" +msgstr "" + +#: ../blockstorage_backup_disks.rst:211 +msgid "Repeat these steps for all your volumes." +msgstr "" + +#: ../blockstorage_backup_disks.rst:213 +msgid "Automate your backups" +msgstr "" + +#: ../blockstorage_backup_disks.rst:215 +msgid "" +"Because more and more volumes might be allocated to your Block Storage " +"service, you might want to automate your backups. The `SCR_5005_V01_NUAC-" +"OPENSTACK-EBS-volumes-backup.sh`_ script assists you with this task. The " +"script performs the operations from the previous example, but also provides " +"a mail report and runs the backup based on the ``backups_retention_days`` " +"setting." +msgstr "" + +#: ../blockstorage_backup_disks.rst:222 +msgid "Launch this script from the server that runs the Block Storage service." +msgstr "" + +#: ../blockstorage_backup_disks.rst:224 +msgid "This example shows a mail report::" +msgstr "" + +#: ../blockstorage_backup_disks.rst:240 +msgid "" +"The script also enables you to SSH to your instances and run a :command:" +"`mysqldump` command into them. To make this work, enable the connection to " +"the Compute project keys. If you do not want to run the :command:`mysqldump` " +"command, you can add ``enable_mysql_dump=0`` to the script to turn off this " +"functionality." +msgstr "" + +#: ../blockstorage_get_capabilities.rst:6 +msgid "Get capabilities" +msgstr "" + +#: ../blockstorage_get_capabilities.rst:8 +msgid "" +"When an administrator configures *volume type* and *extra specs* of storage " +"on the back end, the administrator has to read the right documentation that " +"corresponds to the version of the storage back end. Deep knowledge of " +"storage is also required." +msgstr "" + +#: ../blockstorage_get_capabilities.rst:13 +msgid "" +"OpenStack Block Storage enables administrators to configure *volume type* " +"and *extra specs* without specific knowledge of the storage back end." +msgstr "" + +#: ../blockstorage_get_capabilities.rst:17 +msgid "*Volume Type:* A group of volume policies." msgstr "" #: ../blockstorage_get_capabilities.rst:18 @@ -1212,522 +1422,1187 @@ msgid "" "creation time." msgstr "" -#: ../blockstorage_volume_backups.rst:125 +#: ../blockstorage_get_capabilities.rst:21 msgid "" -"*MOUNT_OPTIONS* is a comma-separated string of NFS mount options as detailed " -"in the NFS man page." +"*Capabilities:* What the current deployed back end in Cinder is able to do. " +"These correspond to extra specs." msgstr "" -#: ../blockstorage_get_capabilities.rst:17 -msgid "*Volume Type:* A group of volume policies." +#: ../blockstorage_get_capabilities.rst:25 +msgid "Usage of cinder client" msgstr "" -#: ../telemetry-alarms.rst:248 +#: ../blockstorage_get_capabilities.rst:27 msgid "" -"*or*, simply that an alarm evaluation cycle hasn't kicked off since the " -"alarm was created (by default, alarms are evaluated once per minute)." +"When an administrator wants to define new volume types for their OpenStack " +"cloud, the administrator would fetch a list of ``capabilities`` for a " +"particular back end using the cinder client." msgstr "" -#: ../telemetry-alarms.rst:245 +#: ../blockstorage_get_capabilities.rst:31 +msgid "First, get a list of the services::" +msgstr "" + +#: ../blockstorage_get_capabilities.rst:41 msgid "" -"*or*, that the identified instance is not visible to the user/tenant owning " -"the alarm" +"With one of the listed hosts, pass that to ``get-capabilities``, then the " +"administrator can obtain volume stats and also back end ``capabilities`` as " +"listed below." msgstr "" -#: ../blockstorage-driver-filter-weighing.rst:109 -msgid "+, -" +#: ../blockstorage_get_capabilities.rst:75 +msgid "Usage of REST API" msgstr "" -#: ../blockstorage-driver-filter-weighing.rst:103 -msgid "+, -, \\*, /, ^" -msgstr "" - -#: ../compute-live-migration-usage.rst:60 -#: ../compute-live-migration-usage.rst:64 -#: ../compute-live-migration-usage.rst:77 -#: ../compute-live-migration-usage.rst:80 -#: ../compute-live-migration-usage.rst:84 -#: ../compute-live-migration-usage.rst:96 -msgid "..." -msgstr "" - -#: ../networking_adv-features.rst:621 -msgid "0 seconds" -msgstr "" - -#: ../database.rst:193 -msgid "1" -msgstr "" - -#: ../database.rst:315 ../database.rst:318 -msgid "1 or 3" -msgstr "" - -#: ../networking_adv-features.rst:628 -msgid "1 second" -msgstr "" - -#: ../networking_adv-features.rst:612 -msgid "10 seconds" -msgstr "" - -#: ../networking_adv-features.rst:541 -msgid "10,000" -msgstr "" - -#: ../networking_adv-features.rst:535 -msgid "2.x" -msgstr "" - -#: ../compute-live-migration-usage.rst:118 -#: ../compute-live-migration-usage.rst:125 -msgid "2014-03-25T10:33:25.000000" -msgstr "" - -#: ../compute-live-migration-usage.rst:132 -msgid "2014-03-25T10:33:27.000000" -msgstr "" - -#: ../compute-live-migration-usage.rst:139 -#: ../compute-live-migration-usage.rst:146 -#: ../compute-live-migration-usage.rst:153 -msgid "2014-03-25T10:33:31.000000" -msgstr "" - -#: ../compute-live-migration-usage.rst:182 -#: ../compute-live-migration-usage.rst:183 -#: ../compute-live-migration-usage.rst:184 -#: ../compute-live-migration-usage.rst:185 -msgid "21284" -msgstr "" - -#: ../networking_adv-features.rst:537 -msgid "3.0.x" -msgstr "" - -#: ../networking_adv-features.rst:539 -msgid "3.1.x" -msgstr "" - -#: ../networking_adv-features.rst:541 -msgid "3.2.x" -msgstr "" - -#: ../compute-live-migration-usage.rst:181 -msgid "32232" -msgstr "" - -#: ../compute-live-migration-usage.rst:188 -#: ../compute-live-migration-usage.rst:189 -#: ../compute-live-migration-usage.rst:190 -msgid "422" -msgstr "" - -#: ../compute-live-migration-usage.rst:187 -msgid "442" -msgstr "" - -#: ../networking_adv-features.rst:537 ../networking_adv-features.rst:539 -msgid "5,000" -msgstr "" - -#: ../networking_adv-features.rst:635 -msgid "500 resources" -msgstr "" - -#: ../networking_adv-features.rst:535 -msgid "64" -msgstr "" - -#: ../compute-live-migration-usage.rst:186 -msgid "878" -msgstr "" - -#: ../blockstorage_backup_disks.rst:34 +#: ../blockstorage_get_capabilities.rst:76 msgid "" -":command:`kpartx` command. Discovers the partition table created inside the " -"instance." +"New endpoint to ``get capabilities`` list for specific storage back end is " +"also available. For more details, refer to the Block Storage API reference." msgstr "" -#: ../blockstorage_backup_disks.rst:32 -msgid ":command:`lvm2` command. Directly manipulates the volumes." +#: ../blockstorage_get_capabilities.rst:79 +msgid "API request::" msgstr "" -#: ../blockstorage_backup_disks.rst:39 +#: ../blockstorage_get_capabilities.rst:83 +msgid "Example of return value::" +msgstr "" + +#: ../blockstorage_glusterfs_backend.rst:3 +msgid "Configure a GlusterFS back end" +msgstr "" + +#: ../blockstorage_glusterfs_backend.rst:5 msgid "" -":command:`sha1sum` command. Calculates the backup checksum to check its " -"consistency." +"This section explains how to configure OpenStack Block Storage to use " +"GlusterFS as a back end. You must be able to access the GlusterFS shares " +"from the server that hosts the ``cinder`` volume service." msgstr "" -#: ../blockstorage_backup_disks.rst:37 -msgid ":command:`tar` command. Creates a minimum-sized backup." -msgstr "" - -#: ../compute-manage-logs.rst:62 -msgid ":file:`/etc/cinder/cinder.conf`" -msgstr "" - -#: ../compute-manage-logs.rst:58 -msgid ":file:`/etc/glance/glance-api.conf`" -msgstr "" - -#: ../compute-manage-logs.rst:60 -msgid ":file:`/etc/glance/glance-registry.conf`" -msgstr "" - -#: ../compute-manage-logs.rst:56 -msgid ":file:`/etc/keystone/keystone.conf`" -msgstr "" - -#: ../compute-manage-logs.rst:54 -msgid ":file:`/etc/nova/nova.conf`" -msgstr "" - -#: ../database.rst:238 -msgid ":file:`/usr/lib/python2.7/dist-packages/trove/templates/DATASTORE_NAME`" -msgstr "" - -#: ../database.rst:244 -msgid ":file:`/usr/lib/python2.7/site-packages/trove/templates/DATASTORE_NAME`" -msgstr "" - -#: ../keystone_certificates_for_pki.rst:181 -msgid ":file:`cacert.pem`" -msgstr "" - -#: ../keystone_certificates_for_pki.rst:175 -msgid ":file:`signing_cert.pem`" -msgstr "" - -#: ../keystone_certificates_for_pki.rst:178 -msgid ":file:`signing_key.pem`" -msgstr "" - -#: ../database.rst:111 ../database.rst:150 -msgid ":option:`--config-file=/etc/trove/trove.conf`" -msgstr "" - -#: ../networking_adv-features.rst:406 +#: ../blockstorage_glusterfs_backend.rst:11 msgid "" -":option:`--provider` is an optional argument. If not used, the pool is " -"created with default provider for LBaaS service. You should configure the " -"default provider in the ``[service_providers]`` section of :file:`neutron." -"conf` file. If no default provider is specified for LBaaS, the :option:`--" -"provider` parameter is required for pool creation." +"The cinder volume service is named ``openstack-cinder-volume`` on the " +"following distributions:" msgstr "" -#: ../index.rst:39 -msgid ":ref:`search`" +# #-#-#-#-# blockstorage_glusterfs_backend.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +# #-#-#-#-# blockstorage_nfs_backend.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +#: ../blockstorage_glusterfs_backend.rst:14 +#: ../blockstorage_glusterfs_backend.rst:135 +#: ../blockstorage_nfs_backend.rst:14 ../blockstorage_nfs_backend.rst:73 +msgid "CentOS" msgstr "" -#: ../networking_introduction.rst:317 +# #-#-#-#-# blockstorage_glusterfs_backend.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +# #-#-#-#-# blockstorage_nfs_backend.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +#: ../blockstorage_glusterfs_backend.rst:16 +#: ../blockstorage_glusterfs_backend.rst:137 +#: ../blockstorage_nfs_backend.rst:16 ../blockstorage_nfs_backend.rst:75 +msgid "Fedora" +msgstr "" + +# #-#-#-#-# blockstorage_glusterfs_backend.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +# #-#-#-#-# blockstorage_nfs_backend.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +#: ../blockstorage_glusterfs_backend.rst:18 +#: ../blockstorage_glusterfs_backend.rst:139 +#: ../blockstorage_nfs_backend.rst:18 ../blockstorage_nfs_backend.rst:77 +msgid "openSUSE" +msgstr "" + +# #-#-#-#-# blockstorage_glusterfs_backend.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +# #-#-#-#-# blockstorage_nfs_backend.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +#: ../blockstorage_glusterfs_backend.rst:20 +#: ../blockstorage_glusterfs_backend.rst:141 +#: ../blockstorage_nfs_backend.rst:20 ../blockstorage_nfs_backend.rst:79 +msgid "Red Hat Enterprise Linux" +msgstr "" + +# #-#-#-#-# blockstorage_glusterfs_backend.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +# #-#-#-#-# blockstorage_nfs_backend.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +#: ../blockstorage_glusterfs_backend.rst:22 +#: ../blockstorage_glusterfs_backend.rst:143 +#: ../blockstorage_nfs_backend.rst:22 ../blockstorage_nfs_backend.rst:81 +msgid "SUSE Linux Enterprise" +msgstr "" + +# #-#-#-#-# blockstorage_glusterfs_backend.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +# #-#-#-#-# blockstorage_nfs_backend.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +#: ../blockstorage_glusterfs_backend.rst:24 ../blockstorage_nfs_backend.rst:24 msgid "" -":term:`service`. A parent object that associates VPN with a specific subnet " -"and router." +"In Ubuntu and Debian distributions, the ``cinder`` volume service is named " +"``cinder-volume``." msgstr "" -#: ../blockstorage-driver-filter-weighing.rst:107 -msgid ">, >=, <, <=, ==, <>, !=" -msgstr "" - -#: ../compute_arch.rst:213 +#: ../blockstorage_glusterfs_backend.rst:27 msgid "" -"A Firefox browser add-on that provides a graphical interface to many popular " -"public and private cloud technologies, including OpenStack. For more " -"information, see the `hybridfox site `__." +"Mounting GlusterFS volumes requires utilities and libraries from the " +"``glusterfs-fuse`` package. This package must be installed on all systems " +"that will access volumes backed by GlusterFS." msgstr "" -#: ../compute_arch.rst:231 +#: ../blockstorage_glusterfs_backend.rst:33 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 `__." +"The utilities and libraries required for mounting GlusterFS volumes on " +"Ubuntu and Debian distributions are available from the ``glusterfs-client`` " +"package instead." msgstr "" -#: ../compute_arch.rst:219 +#: ../blockstorage_glusterfs_backend.rst:37 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 `__." +"For information on how to install and configure GlusterFS, refer to the " +"`GlusterDocumentation`_ page." msgstr "" -#: ../baremetal.rst:30 -msgid "A RESTful API service" +#: ../blockstorage_glusterfs_backend.rst:40 +msgid "**Configure GlusterFS for OpenStack Block Storage**" msgstr "" -#: ../compute_arch.rst:225 +#: ../blockstorage_glusterfs_backend.rst:42 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 `__." +"The GlusterFS server must also be configured accordingly in order to allow " +"OpenStack Block Storage to use GlusterFS shares:" msgstr "" -#: ../telemetry-events.rst:40 -msgid "A UUID for the event." +#: ../blockstorage_glusterfs_backend.rst:45 +msgid "Log in as ``root`` to the GlusterFS server." msgstr "" -#: ../compute-remote-console-access.rst:121 -msgid "A ``nova-consoleauth`` process. Typically runs on the controller host." -msgstr "" - -#: ../compute_arch.rst:20 +#: ../blockstorage_glusterfs_backend.rst:47 msgid "" -"A ``volume controller`` provides fast and permanent block-level storage for " -"the compute servers." +"Set each Gluster volume to use the same UID and GID as the ``cinder`` user::" msgstr "" -#: ../networking_introduction.rst:34 -msgid "A block of v4 or v6 IP addresses and associated configuration state." +# #-#-#-#-# blockstorage_glusterfs_backend.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +# #-#-#-#-# blockstorage_nfs_backend.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +# #-#-#-#-# compute-flavors.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +# #-#-#-#-# identity_service_api_protection.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +# #-#-#-#-# keystone_secure_identity_to_ldap_backend.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +#: ../blockstorage_glusterfs_backend.rst:52 +#: ../blockstorage_glusterfs_backend.rst:96 ../blockstorage_nfs_backend.rst:41 +#: ../compute-flavors.rst:264 ../compute-flavors.rst:285 +#: ../identity_service_api_protection.rst:19 +#: ../keystone_secure_identity_to_ldap_backend.rst:62 +msgid "Where:" msgstr "" -#: ../identity_service_api_protection.rst:124 +#: ../blockstorage_glusterfs_backend.rst:54 +msgid "VOL_NAME is the Gluster volume name." +msgstr "" + +#: ../blockstorage_glusterfs_backend.rst:56 +msgid "CINDER_UID is the UID of the ``cinder`` user." +msgstr "" + +#: ../blockstorage_glusterfs_backend.rst:58 +msgid "CINDER_GID is the GID of the ``cinder`` user." +msgstr "" + +#: ../blockstorage_glusterfs_backend.rst:62 msgid "" -"A clean installation could start with the standard policy file, to allow " -"creation of the :code:`admin_domain` with the first users within it. You " -"could then obtain the :code:`domain_id` of the admin domain, paste the ID " -"into a modified version of :file:`policy.v3cloudsample.json`, and then " -"enable it as the main policy file." +"The default UID and GID of the ``cinder`` user is 165 on most distributions." msgstr "" -#: ../objectstorage_components.rst:250 +#: ../blockstorage_glusterfs_backend.rst:65 msgid "" -"A client uses the REST API to make a HTTP request to PUT an object into an " -"existing container. The cluster receives the request. First, the system must " -"figure out where the data is going to go. To do this, the account name, " -"container name, and object name are all used to determine the partition " -"where this object should live." +"Configure each Gluster volume to accept ``libgfapi`` connections. To do " +"this, set each Gluster volume to allow insecure ports::" msgstr "" -#: ../compute-node-down.rst:157 -msgid "A cloud controller (nova-api, nova-objectstore, nova-network)" -msgstr "" - -#: ../identity_concepts.rst:42 +#: ../blockstorage_glusterfs_backend.rst:70 msgid "" -"A command-line interface for several OpenStack services including the " -"Identity API. For example, a user can run the :command:`openstack service " -"create` and :command:`openstack endpoint create` commands to register " -"services in her OpenStack installation." +"Enable client connections from unprivileged ports. To do this, add the " +"following line to :file:`/etc/glusterfs/glusterd.vol`::" msgstr "" -#: ../telemetry-data-collection.rst:294 +#: ../blockstorage_glusterfs_backend.rst:75 +msgid "Restart the ``glusterd`` service::" +msgstr "" + +#: ../blockstorage_glusterfs_backend.rst:81 +msgid "**Configure Block Storage to use a GlusterFS back end**" +msgstr "" + +#: ../blockstorage_glusterfs_backend.rst:83 +msgid "After you configure the GlusterFS service, complete these steps:" +msgstr "" + +#: ../blockstorage_glusterfs_backend.rst:85 +msgid "Log in as ``root`` to the system hosting the Block Storage service." +msgstr "" + +#: ../blockstorage_glusterfs_backend.rst:87 +msgid "Create a text file named :file:`glusterfs` in :file:`/etc/cinder/`." +msgstr "" + +#: ../blockstorage_glusterfs_backend.rst:89 msgid "" -"A compute agent instance has to be installed on each and every compute node, " -"installation instructions can be found in the `Install the Compute agent for " -"Telemetry `__ section in the OpenStack " -"Installation Guide." +"Add an entry to :file:`/etc/cinder/glusterfs` for each GlusterFS share that " +"OpenStack Block Storage should use for back end storage. Each entry should " +"be a separate line, and should use the following format::" msgstr "" -#: ../compute-node-down.rst:159 -msgid "A compute node (nova-compute)" +#: ../blockstorage_glusterfs_backend.rst:98 +msgid "HOST is the IP address or host name of the Red Hat Storage server." msgstr "" -#: ../baremetal.rst:32 -msgid "A conductor service" -msgstr "" - -#: ../objectstorage_features.rst:27 +#: ../blockstorage_glusterfs_backend.rst:100 msgid "" -"A configurable number of accounts, containers and object copies for high " -"availability." +"VOL_NAME is the name of an existing and accessible volume on the GlusterFS " +"server." msgstr "" -#: ../networking_introduction.rst:37 +#: ../blockstorage_glusterfs_backend.rst:105 msgid "" -"A connection point for attaching a single device, such as the NIC of a " -"virtual server, to a virtual network. Also describes the associated network " -"configuration, such as the MAC and IP addresses to be used on that port." +"Optionally, if your environment requires additional mount options for a " +"share, you can add them to the share's entry::" msgstr "" -#: ../blockstorage-consistency-groups.rst:69 +#: ../blockstorage_glusterfs_backend.rst:110 +msgid "Replace OPTIONS with a comma-separated list of mount options." +msgstr "" + +#: ../blockstorage_glusterfs_backend.rst:112 msgid "" -"A consistency group can only contain volumes hosted by the same back end." +"Set :file:`/etc/cinder/glusterfs` to be owned by the root user and the " +"``cinder`` group::" msgstr "" -#: ../blockstorage-consistency-groups.rst:65 +#: ../blockstorage_glusterfs_backend.rst:117 msgid "" -"A consistency group can support more than one volume type. The scheduler is " -"responsible for finding a back end that can support all given volume types." +"Set :file:`/etc/cinder/glusterfs` to be readable by members of the " +"``cinder`` group::" msgstr "" -#: ../blockstorage-consistency-groups.rst:110 -msgid "A consistency group has to be deleted as a whole with all the volumes." -msgstr "" - -#: ../blockstorage-consistency-groups.rst:72 +#: ../blockstorage_glusterfs_backend.rst:122 msgid "" -"A consistency group is empty upon its creation. Volumes need to be created " -"and added to it later." +"Configure OpenStack Block Storage to use the :file:`/etc/cinder/glusterfs` " +"file created earlier. To do so, open the :file:`/etc/cinder/cinder.conf` " +"configuration file and set the ``glusterfs_shares_config`` configuration key " +"to :file:`/etc/cinder/glusterfs`." msgstr "" -#: ../blockstorage-consistency-groups.rst:120 +#: ../blockstorage_glusterfs_backend.rst:127 msgid "" -"A consistency group snapshot has to be deleted as a whole with all the " -"volume snapshots." +"On distributions that include openstack-config, you can configure this by " +"running the following command instead::" msgstr "" -#: ../identity_concepts.rst:49 +#: ../blockstorage_glusterfs_backend.rst:133 +msgid "The following distributions include ``openstack-config``:" +msgstr "" + +#: ../blockstorage_glusterfs_backend.rst:147 msgid "" -"A container that groups or isolates resources or identity objects. Depending " -"on the service operator, a project might map to a customer, account, " -"organization, or tenant." +"Configure OpenStack Block Storage to use the correct volume driver, namely " +"``cinder.volume.drivers.glusterfs``. To do so, open the :file:`/etc/cinder/" +"cinder.conf` configuration file and set the ``volume_driver`` configuration " +"key to ``cinder.volume.drivers.glusterfs``." msgstr "" -#: ../networking_config-plugins.rst:143 +# #-#-#-#-# blockstorage_glusterfs_backend.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +# #-#-#-#-# blockstorage_nfs_backend.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +#: ../blockstorage_glusterfs_backend.rst:158 +#: ../blockstorage_nfs_backend.rst:113 +msgid "You can now restart the service to apply the configuration." +msgstr "" + +# #-#-#-#-# blockstorage_glusterfs_backend.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +# #-#-#-#-# blockstorage_nfs_backend.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +#: ../blockstorage_glusterfs_backend.rst:160 +#: ../blockstorage_nfs_backend.rst:115 msgid "" -"A controller API endpoint consists of the IP address and port for the " -"controller; if you omit the port, port 443 is used. If multiple API " -"endpoints are specified, it is up to the user to ensure that all these " -"endpoints belong to the same controller cluster. The OpenStack Networking " -"VMware NSX-mh plug-in does not perform this check, and results might be " -"unpredictable." +"To restart the ``cinder`` volume service on CentOS, Fedora, openSUSE, Red " +"Hat Enterprise Linux, or SUSE Linux Enterprise, run::" msgstr "" -#: ../objectstorage-monitoring.rst:77 +# #-#-#-#-# blockstorage_glusterfs_backend.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +# #-#-#-#-# blockstorage_nfs_backend.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +#: ../blockstorage_glusterfs_backend.rst:165 +#: ../blockstorage_nfs_backend.rst:121 +msgid "To restart the ``cinder`` volume service on Ubuntu or Debian, run::" +msgstr "" + +#: ../blockstorage_glusterfs_backend.rst:169 +msgid "OpenStack Block Storage is now configured to use a GlusterFS back end." +msgstr "" + +#: ../blockstorage_glusterfs_backend.rst:173 msgid "" -"A counter increase by the bytes transferred for a meter like ``tfer.obj." -"PUT.201``." +"In :file:`/etc/cinder/cinder.conf`, the ``glusterfs_sparsed_volumes`` " +"configuration key determines whether volumes are created as sparse files and " +"grown as needed or fully allocated up front. The default and recommended " +"value of this key is true, which ensures volumes are initially created as " +"sparse files." msgstr "" -#: ../objectstorage-monitoring.rst:65 +#: ../blockstorage_glusterfs_backend.rst:179 msgid "" -"A counter increment for a meter like ``obj.GET.200`` or ``cont.PUT.404``." +"Setting ``glusterfs_sparsed_volumes`` to false will result in volumes being " +"fully allocated at the time of creation. This leads to increased delays in " +"volume creation." msgstr "" -#: ../networking_config-agents.rst:11 +#: ../blockstorage_glusterfs_backend.rst:183 msgid "" -"A data-forwarding node typically has a network interface with an IP address " -"on the management network and another interface on the data network." +"However, should you choose to set glusterfs_sparsed_volumes to false, you " +"can do so directly in :file:`/etc/cinder/cinder.conf`." msgstr "" -#: ../baremetal.rst:38 -msgid "A database for storing information about the resources" -msgstr "" - -#: ../compute-security.rst:37 +#: ../blockstorage_glusterfs_backend.rst:194 msgid "" -"A description of how to set up an attestation service is beyond the scope of " -"this document. For an open source project that you can use to implement an " -"attestation service, see the `Open Attestation `__ project." +"If a client host has SELinux enabled, the ``virt_use_fusefs`` boolean should " +"also be enabled if the host requires access to GlusterFS volumes on an " +"instance. To enable this Boolean, run the following command as the ``root`` " +"user::" msgstr "" -#: ../compute-flavors.rst:39 +#: ../blockstorage_glusterfs_backend.rst:201 msgid "" -"A descriptive name. XX.SIZE_NAME is typically not required, though some " -"third party tools may rely on it." +"This command also makes the Boolean persistent across reboots. Run this " +"command on all client hosts that require access to GlusterFS volumes on an " +"instance. This includes all compute nodes." msgstr "" -#: ../identity_concepts.rst:84 +#: ../blockstorage_glusterfs_removal.rst:8 +msgid "Gracefully remove a GlusterFS volume from usage" +msgstr "" + +#: ../blockstorage_glusterfs_removal.rst:10 msgid "" -"A digital representation of a person, system, or service that uses OpenStack " -"cloud services. The Identity service validates that incoming requests are " -"made by the user who claims to be making the call. Users have a login and " -"can access resources by using assigned tokens. Users can be directly " -"assigned to a particular project and behave as if they are contained in that " -"project." +"Configuring the ``cinder`` volume service to use GlusterFS involves creating " +"a shares file (for example, :file:`/etc/cinder/glusterfs`). This shares file " +"lists each GlusterFS volume (with its corresponding storage server) that the " +"``cinder`` volume service can use for back end storage." msgstr "" -#: ../compute-node-down.rst:153 +#: ../blockstorage_glusterfs_removal.rst:15 msgid "" -"A disaster could happen to several components of your architecture (for " -"example, a disk crash, network loss, or a power failure). In this example, " -"the following components are configured:" +"To remove a GlusterFS volume from usage as a back end, delete the volume's " +"corresponding entry from the shares file. After doing so, restart the Block " +"Storage services." msgstr "" -#: ../compute-images-instances.rst:147 -msgid "A distributed storage system for QEMU/KVM." -msgstr "" - -#: ../telemetry-events.rst:36 +#: ../blockstorage_glusterfs_removal.rst:19 msgid "" -"A dotted string defining what event occurred such as ``\"compute.instance." -"resize.start\"``." +"To restart the Block Storage services on CentOS, Fedora, openSUSE, Red Hat " +"Enterprise Linux, or SUSE Linux Enterprise, run::" msgstr "" -#: ../telemetry-events.rst:46 +#: ../blockstorage_glusterfs_removal.rst:24 +msgid "To restart the Block Storage services on Ubuntu or Debian, run::" +msgstr "" + +#: ../blockstorage_glusterfs_removal.rst:28 msgid "" -"A flat mapping of key-value pairs which describe the event. The event's " -"traits contain most of the details of the event. Traits are typed, and can " -"be strings, integers, floats, or datetimes." +"Restarting the Block Storage services will prevent the ``cinder`` volume " +"service from exporting the deleted GlusterFS volume. This will prevent any " +"instances from mounting the volume from that point onwards." msgstr "" -#: ../objectstorage_ringbuilder.rst:98 +#: ../blockstorage_glusterfs_removal.rst:32 msgid "" -"A fractional replica count is for the whole ring and not for individual " -"partitions. It indicates the average number of replicas for each partition. " -"For example, a replica count of 3.2 means that 20 percent of partitions have " -"four replicas and 80 percent have three replicas." +"However, the removed GlusterFS volume might still be mounted on an instance " +"at this point. Typically, this is the case when the volume was already " +"mounted while its entry was deleted from the shares file. Whenever this " +"occurs, you will have to unmount the volume as normal after the Block " +"Storage services are restarted." msgstr "" -#: ../telemetry-alarms.rst:184 +#: ../blockstorage_image_volume_cache.rst:6 +msgid "Image-Volume cache" +msgstr "" + +#: ../blockstorage_image_volume_cache.rst:8 msgid "" -"A free-text description of the alarm (defaults to a synopsis of the alarm " -"rule)." +"OpenStack Block Storage has an optional Image cache which can dramatically " +"improve the performance of creating a volume from an image. The improvement " +"depends on many factors, primarily how quickly the configured back end can " +"clone a volume." msgstr "" -#: ../compute-root-wrap-reference.rst:19 +#: ../blockstorage_image_volume_cache.rst:13 msgid "" -"A generic ``sudoers`` entry lets the Compute user run :command:`nova-" -"rootwrap` as root. The :command:`nova-rootwrap` code looks for filter " -"definition directories in its configuration file, and loads command filters " -"from them. It then checks if the command requested by Compute matches one of " -"those filters and, if so, executes the command (as root). If no filter " -"matches, it denies the request." +"When a volume is first created from an image, a new cached image-volume will " +"be created that is owned by the Block Storage Internal Tenant. Subsequent " +"requests to create volumes from that image will clone the cached version " +"instead of downloading the image contents and copying data to the volume." msgstr "" -#: ../identity_concepts.rst:334 +#: ../blockstorage_image_volume_cache.rst:18 msgid "" -"A group is a collection of users in a domain. Administrators can create " -"groups and add users to them. A role can then be assigned to the group, " -"rather than individual users. Groups were introduced with the Identity API " -"v3." +"The cache itself is configurable per back end and will contain the most " +"recently used images." msgstr "" -#: ../telemetry-alarms.rst:56 +#: ../blockstorage_image_volume_cache.rst:22 +msgid "Configure the Internal Tenant" +msgstr "" + +#: ../blockstorage_image_volume_cache.rst:24 msgid "" -"A key associated concept is the notion of *dimensioning* which defines the " -"set of matching meters that feed into an alarm evaluation. Recall that " -"meters are per-resource-instance, so in the simplest case an alarm might be " -"defined over a particular meter applied to all resources visible to a " -"particular user. More useful however would be the option to explicitly " -"select which specific resources you are interested in alarming on." +"The Image-Volume cache requires that the Internal Tenant be configured for " +"the Block Storage services. This tenant will own the cached image-volumes so " +"they can be managed like normal users including tools like volume quotas. " +"This protects normal users from having to see the cached image-volumes, but " +"does not make them globally hidden." msgstr "" -#: ../keystone_use_trusts.rst:48 -msgid "A list of endpoints associated with the delegation." -msgstr "" - -#: ../baremetal.rst:36 -msgid "A message queue" -msgstr "" - -#: ../compute_arch.rst:314 +#: ../blockstorage_image_volume_cache.rst:30 msgid "" -"A messaging queue brokers the interaction between compute nodes " -"(processing), the networking controllers (software which controls network " -"infrastructure), API endpoints, the scheduler (determines which physical " -"hardware to allocate to a virtual resource), and similar components. " -"Communication to and from the cloud controller is handled by HTTP requests " -"through multiple API endpoints." +"To enable the Block Storage services to have access to an Internal Tenant, " +"set the following options in the :file:`cinder.conf` file::" msgstr "" -#: ../networking_adv-features.rst:56 +#: ../blockstorage_image_volume_cache.rst:43 msgid "" -"A network connecting virtualization hosts (such as compute nodes) with each " -"other and with other network resources. Each physical network might support " -"multiple virtual networks. The provider extension and the plug-in " -"configurations identify physical networks using simple string names." +"The actual user and project that are configured for the Internal Tenant do " +"not require any special privileges. They can be the Block Storage service " +"tenant or can be any normal project and user." msgstr "" -#: ../identity_concepts.rst:29 +#: ../blockstorage_image_volume_cache.rst:48 +msgid "Configure the Image-Volume cache" +msgstr "" + +#: ../blockstorage_image_volume_cache.rst:50 msgid "" -"A network-accessible address, usually a URL, through which you can access a " -"service. If you are using an extension for templates, you can create an " -"endpoint template that represents the templates of all consumable services " -"that are available across the regions." +"To enable the Image-Volume cache, set the following configuration option in :" +"file:`cinder.conf`::" +msgstr "" + +#: ../blockstorage_image_volume_cache.rst:55 +msgid "This can be scoped per back end definition or in the default options." +msgstr "" + +#: ../blockstorage_image_volume_cache.rst:57 +msgid "" +"There are optional configuration settings that can limit the size of the " +"cache. These can also be scoped per back end or in the default options in :" +"file:`cinder.conf`::" +msgstr "" + +#: ../blockstorage_image_volume_cache.rst:64 +msgid "By default they will be set to 0, which means unlimited." +msgstr "" + +#: ../blockstorage_image_volume_cache.rst:66 +msgid "" +"For example, a configuration which would limit the max size to 200 GB and 50 " +"cache entries will be configured as::" +msgstr "" + +# #-#-#-#-# blockstorage_image_volume_cache.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +# #-#-#-#-# networking_adv-operational-features.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +# #-#-#-#-# telemetry-data-collection.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +#: ../blockstorage_image_volume_cache.rst:73 +#: ../networking_adv-operational-features.rst:48 +#: ../telemetry-data-collection.rst:27 ../telemetry-data-collection.rst:38 +msgid "Notifications" +msgstr "" + +#: ../blockstorage_image_volume_cache.rst:75 +msgid "" +"Cache actions will trigger Telemetry messages. There are several that will " +"be sent." +msgstr "" + +#: ../blockstorage_image_volume_cache.rst:78 +msgid "" +"``image_volume_cache.miss`` - A volume is being created from an image which " +"was not found in the cache. Typically this will mean a new cache entry would " +"be created for it." +msgstr "" + +#: ../blockstorage_image_volume_cache.rst:82 +msgid "" +"``image_volume_cache.hit`` - A volume is being created from an image which " +"was found in the cache and the fast path can be taken." +msgstr "" + +#: ../blockstorage_image_volume_cache.rst:85 +msgid "" +"``image_volume_cache.evict`` - A cached image-volume has been deleted from " +"the cache." +msgstr "" + +#: ../blockstorage_image_volume_cache.rst:90 +msgid "Managing cached Image-Volumes" +msgstr "" + +#: ../blockstorage_image_volume_cache.rst:92 +msgid "" +"In normal usage there should be no need for manual intervention with the " +"cache. The entries and their backing Image-Volumes are managed automatically." +msgstr "" + +#: ../blockstorage_image_volume_cache.rst:95 +msgid "" +"If needed, you can delete these volumes manually to clear the cache. By " +"using the standard volume deletion APIs, the Block Storage service will " +"clean up correctly." +msgstr "" + +# #-#-#-#-# blockstorage_multi_backend.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +# #-#-#-#-# blockstorage_volume_number_weigher.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +#: ../blockstorage_multi_backend.rst:8 +#: ../blockstorage_volume_number_weigher.rst:25 +msgid "Configure multiple-storage back ends" +msgstr "" + +#: ../blockstorage_multi_backend.rst:10 +msgid "" +"When you configure multiple-storage back ends, you can create several back-" +"end storage solutions that serve the same OpenStack Compute configuration " +"and one ``cinder-volume`` is launched for each back-end storage or back-end " +"storage pool." +msgstr "" + +#: ../blockstorage_multi_backend.rst:15 +msgid "" +"In a multiple-storage back-end configuration, each back end has a name " +"(``volume_backend_name``). Several back ends can have the same name. In that " +"case, the scheduler properly decides which back end the volume has to be " +"created in." +msgstr "" + +#: ../blockstorage_multi_backend.rst:20 +msgid "" +"The name of the back end is declared as an extra-specification of a volume " +"type (such as, ``volume_backend_name=LVM``). When a volume is created, the " +"scheduler chooses an appropriate back end to handle the request, according " +"to the volume type specified by the user." +msgstr "" + +#: ../blockstorage_multi_backend.rst:26 +msgid "Enable multiple-storage back ends" +msgstr "" + +#: ../blockstorage_multi_backend.rst:28 +msgid "" +"To enable a multiple-storage back ends, you must set the `enabled_backends` " +"flag in the :file:`cinder.conf` file. This flag defines the names (separated " +"by a comma) of the configuration groups for the different back ends: one " +"name is associated to one configuration group for a back end (such as, " +"``[lvmdriver-1]``)." +msgstr "" + +#: ../blockstorage_multi_backend.rst:36 +msgid "" +"The configuration group name is not related to the ``volume_backend_name``." +msgstr "" + +#: ../blockstorage_multi_backend.rst:40 +msgid "" +"After setting the `enabled_backends` flag on an existing cinder service, and " +"restarting the Block Storage services, the original ``host`` service is " +"replaced with a new host service. The new service appears with a name like " +"``host@backend``. Use::" +msgstr "" + +#: ../blockstorage_multi_backend.rst:47 +msgid "to convert current block devices to the new hostname." +msgstr "" + +#: ../blockstorage_multi_backend.rst:49 +msgid "" +"The options for a configuration group must be defined in the group (or " +"default options are used). All the standard Block Storage configuration " +"options (``volume_group``, ``volume_driver``, and so on) might be used in a " +"configuration group. Configuration values in the ``[DEFAULT]`` configuration " +"group are not used." +msgstr "" + +#: ../blockstorage_multi_backend.rst:55 +msgid "These examples show three back ends:" +msgstr "" + +#: ../blockstorage_multi_backend.rst:74 +msgid "" +"In this configuration, ``lvmdriver-1`` and ``lvmdriver-2`` have the same " +"``volume_backend_name``. If a volume creation requests the ``LVM`` back end " +"name, the scheduler uses the capacity filter scheduler to choose the most " +"suitable driver, which is either ``lvmdriver-1`` or ``lvmdriver-2``. The " +"capacity filter scheduler is enabled by default. The next section provides " +"more information. In addition, this example presents a ``lvmdriver-3`` back " +"end." +msgstr "" + +#: ../blockstorage_multi_backend.rst:84 +msgid "" +"For Fiber Channel drivers that support multipath, the configuration group " +"requires the ``use_multipath_for_image_xfer=true`` option. In the example " +"below, you can see details for HP 3PAR and EMC Fiber Channel drivers." +msgstr "" + +#: ../blockstorage_multi_backend.rst:103 +msgid "Configure Block Storage scheduler multi back end" +msgstr "" + +#: ../blockstorage_multi_backend.rst:105 +msgid "" +"You must enable the `filter_scheduler` option to use multiple-storage back " +"ends. The filter scheduler:" +msgstr "" + +#: ../blockstorage_multi_backend.rst:108 +msgid "" +"Filters the available back ends. By default, ``AvailabilityZoneFilter``, " +"``CapacityFilter`` and ``CapabilitiesFilter`` are enabled." +msgstr "" + +#: ../blockstorage_multi_backend.rst:111 +msgid "" +"Weights the previously filtered back ends. By default, the `CapacityWeigher` " +"option is enabled. When this option is enabled, the filter scheduler assigns " +"the highest weight to back ends with the most available capacity." +msgstr "" + +#: ../blockstorage_multi_backend.rst:116 +msgid "" +"The scheduler uses filters and weights to pick the best back end to handle " +"the request. The scheduler uses volume types to explicitly create volumes on " +"specific back ends." +msgstr "" + +# #-#-#-#-# blockstorage_multi_backend.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +# #-#-#-#-# blockstorage_volume_number_weigher.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +#: ../blockstorage_multi_backend.rst:124 +#: ../blockstorage_volume_number_weigher.rst:51 +msgid "Volume type" +msgstr "" + +#: ../blockstorage_multi_backend.rst:126 +msgid "" +"Before using it, a volume type has to be declared to Block Storage. This can " +"be done by the following command::" +msgstr "" + +#: ../blockstorage_multi_backend.rst:131 +msgid "" +"Then, an extra-specification has to be created to link the volume type to a " +"back end name. Run this command::" +msgstr "" + +#: ../blockstorage_multi_backend.rst:137 +msgid "" +"This example creates a ``lvm`` volume type with " +"``volume_backend_name=LVM_iSCSI`` as extra-specifications." +msgstr "" + +#: ../blockstorage_multi_backend.rst:140 +msgid "Create another volume type::" +msgstr "" + +#: ../blockstorage_multi_backend.rst:147 +msgid "" +"This second volume type is named ``lvm_gold`` and has ``LVM_iSCSI_b`` as " +"back end name." +msgstr "" + +#: ../blockstorage_multi_backend.rst:152 +msgid "To list the extra-specifications, use this command::" +msgstr "" + +#: ../blockstorage_multi_backend.rst:158 +msgid "" +"If a volume type points to a ``volume_backend_name`` that does not exist in " +"the Block Storage configuration, the ``filter_scheduler`` returns an error " +"that it cannot find a valid host with the suitable back end." +msgstr "" + +# #-#-#-#-# blockstorage_multi_backend.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +# #-#-#-#-# blockstorage_volume_number_weigher.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +#: ../blockstorage_multi_backend.rst:164 +#: ../blockstorage_volume_number_weigher.rst:65 +msgid "Usage" +msgstr "" + +#: ../blockstorage_multi_backend.rst:166 +msgid "" +"When you create a volume, you must specify the volume type. The extra-" +"specifications of the volume type are used to determine which back end has " +"to be used." +msgstr "" + +#: ../blockstorage_multi_backend.rst:174 +msgid "" +"Considering the :file:`cinder.conf` described previously, the scheduler " +"creates this volume on ``lvmdriver-1`` or ``lvmdriver-2``." +msgstr "" + +#: ../blockstorage_multi_backend.rst:181 +msgid "This second volume is created on ``lvmdriver-3``." +msgstr "" + +#: ../blockstorage_nfs_backend.rst:3 +msgid "Configure an NFS storage back end" +msgstr "" + +#: ../blockstorage_nfs_backend.rst:5 +msgid "" +"This section explains how to configure OpenStack Block Storage to use NFS " +"storage. You must be able to access the NFS shares from the server that " +"hosts the ``cinder`` volume service." +msgstr "" + +#: ../blockstorage_nfs_backend.rst:11 +msgid "" +"The ``cinder`` volume service is named ``openstack-cinder-volume`` on the " +"following distributions:" +msgstr "" + +#: ../blockstorage_nfs_backend.rst:27 +msgid "**Configure Block Storage to use an NFS storage back end**" +msgstr "" + +#: ../blockstorage_nfs_backend.rst:29 +msgid "Log in as ``root`` to the system hosting the ``cinder`` volume service." +msgstr "" + +#: ../blockstorage_nfs_backend.rst:32 +msgid "Create a text file named :file:`nfsshares` in :file:`/etc/cinder/`." +msgstr "" + +#: ../blockstorage_nfs_backend.rst:34 +msgid "" +"Add an entry to :file:`/etc/cinder/nfsshares` for each NFS share that the " +"``cinder`` volume service should use for back end storage. Each entry should " +"be a separate line, and should use the following format:" +msgstr "" + +#: ../blockstorage_nfs_backend.rst:39 +msgid "``HOST:SHARE``" +msgstr "" + +#: ../blockstorage_nfs_backend.rst:43 +msgid "HOST is the IP address or host name of the NFS server." +msgstr "" + +#: ../blockstorage_nfs_backend.rst:45 +msgid "SHARE is the absolute path to an existing and accessible NFS share." +msgstr "" + +#: ../blockstorage_nfs_backend.rst:49 +msgid "" +"Set :file:`/etc/cinder/nfsshares` to be owned by the ``root`` user and the " +"``cinder`` group::" +msgstr "" + +#: ../blockstorage_nfs_backend.rst:54 +msgid "" +"Set :file:`/etc/cinder/nfsshares` to be readable by members of the cinder " +"group::" +msgstr "" + +#: ../blockstorage_nfs_backend.rst:59 +msgid "" +"Configure the cinder volume service to use the :file:`/etc/cinder/nfsshares` " +"file created earlier. To do so, open the :file:`/etc/cinder/cinder.conf` " +"configuration file and set the ``nfs_shares_config`` configuration key to :" +"file:`/etc/cinder/nfsshares`." +msgstr "" + +#: ../blockstorage_nfs_backend.rst:71 +msgid "The following distributions include openstack-config:" +msgstr "" + +#: ../blockstorage_nfs_backend.rst:85 +msgid "" +"Optionally, provide any additional NFS mount options required in your " +"environment in the ``nfs_mount_options`` configuration key of :file:`/etc/" +"cinder/cinder.conf`. If your NFS shares do not require any additional mount " +"options (or if you are unsure), skip this step." +msgstr "" + +#: ../blockstorage_nfs_backend.rst:97 +msgid "" +"Replace OPTIONS with the mount options to be used when accessing NFS shares. " +"See the manual page for NFS for more information on available mount options " +"(:command:`man nfs`)." +msgstr "" + +#: ../blockstorage_nfs_backend.rst:101 +msgid "" +"Configure the ``cinder`` volume service to use the correct volume driver, " +"namely cinder.volume.drivers.nfs.NfsDriver. To do so, open the :file:`/etc/" +"cinder/cinder.conf` configuration file and set the volume_driver " +"configuration key to ``cinder.volume.drivers.nfs.NfsDriver``." +msgstr "" + +#: ../blockstorage_nfs_backend.rst:127 +msgid "" +"The ``nfs_sparsed_volumes`` configuration key determines whether volumes are " +"created as sparse files and grown as needed or fully allocated up front. The " +"default and recommended value is ``true``, which ensures volumes are " +"initially created as sparse files." +msgstr "" + +#: ../blockstorage_nfs_backend.rst:132 +msgid "" +"Setting ``nfs_sparsed_volumes`` to ``false`` will result in volumes being " +"fully allocated at the time of creation. This leads to increased delays in " +"volume creation." +msgstr "" + +#: ../blockstorage_nfs_backend.rst:136 +msgid "" +"However, should you choose to set ``nfs_sparsed_volumes`` to false, you can " +"do so directly in :file:`/etc/cinder/cinder.conf`." +msgstr "" + +#: ../blockstorage_nfs_backend.rst:147 +msgid "" +"If a client host has SELinux enabled, the ``virt_use_nfs`` boolean should " +"also be enabled if the host requires access to NFS volumes on an instance. " +"To enable this boolean, run the following command as the ``root`` user::" +msgstr "" + +#: ../blockstorage_nfs_backend.rst:154 +msgid "" +"This command also makes the boolean persistent across reboots. Run this " +"command on all client hosts that require access to NFS volumes on an " +"instance. This includes all compute nodes." +msgstr "" + +#: ../blockstorage_over_subscription.rst:6 +msgid "Oversubscription in thin provisioning" +msgstr "" + +#: ../blockstorage_over_subscription.rst:8 +msgid "" +"OpenStack Block Storage enables you to choose a volume back end based on " +"virtual capacities for thin provisioning using the oversubscription ratio." +msgstr "" + +#: ../blockstorage_over_subscription.rst:11 +msgid "" +"A reference implementation is provided for the default LVM driver. The " +"illustration below uses the LVM driver as an example." +msgstr "" + +#: ../blockstorage_over_subscription.rst:15 +msgid "Configure oversubscription settings" +msgstr "" + +#: ../blockstorage_over_subscription.rst:17 +msgid "" +"To support oversubscription in thin provisioning, a flag " +"``max_over_subscription_ratio`` is introduced into :file:`cinder.conf`. This " +"is a float representation of the oversubscription ratio when thin " +"provisioning is involved. Default ratio is 20.0, meaning provisioned " +"capacity can be 20 times of the total physical capacity. A ratio of 10.5 " +"means provisioned capacity can be 10.5 times of the total physical capacity. " +"A ratio of 1.0 means provisioned capacity cannot exceed the total physical " +"capacity. A ratio lower than 1.0 is ignored and the default value is used " +"instead." +msgstr "" + +#: ../blockstorage_over_subscription.rst:29 +msgid "" +"``max_over_subscription_ratio`` can be configured for each back end when " +"multiple-storage back ends are enabled. It is provided as a reference " +"implementation and is used by the LVM driver. However, it is not a " +"requirement for a driver to use this option from :file:`cinder.conf`." +msgstr "" + +#: ../blockstorage_over_subscription.rst:34 +msgid "" +"``max_over_subscription_ratio`` is for configuring a back end. For a driver " +"that supports multiple pools per back end, it can report this ratio for each " +"pool. The LVM driver does not support multiple pools." +msgstr "" + +#: ../blockstorage_over_subscription.rst:38 +msgid "" +"The existing ``reserved_percentage`` flag is used to prevent over " +"provisioning. This flag represents the percentage of the back-end capacity " +"that is reserved." +msgstr "" + +#: ../blockstorage_over_subscription.rst:43 +msgid "" +"There is a change on how ``reserved_percentage`` is used. It was measured " +"against the free capacity in the past. Now it is measured against the total " +"capacity." +msgstr "" + +#: ../blockstorage_over_subscription.rst:48 +msgid "Capabilities" +msgstr "" + +#: ../blockstorage_over_subscription.rst:50 +msgid "Drivers can report the following capabilities for a back end or a pool:" +msgstr "" + +#: ../blockstorage_over_subscription.rst:60 +msgid "" +"Where ``PROVISIONED_CAPACITY`` is the apparent allocated space indicating " +"how much capacity has been provisioned and ``MAX_RATIO`` is the maximum " +"oversubscription ratio. For the LVM driver, it is " +"``max_over_subscription_ratio`` in :file:`cinder.conf`." +msgstr "" + +#: ../blockstorage_over_subscription.rst:65 +msgid "" +"Two capabilities are added here to allow a back end or pool to claim support " +"for thin provisioning, or thick provisioning, or both." +msgstr "" + +#: ../blockstorage_over_subscription.rst:68 +msgid "" +"The LVM driver reports ``thin_provisioning_support=True`` and " +"``thick_provisioning_support=False`` if the ``lvm_type`` flag in :file:" +"`cinder.conf` is ``thin``. Otherwise it reports " +"``thin_provisioning_support=False`` and ``thick_provisioning_support=True``." +msgstr "" + +#: ../blockstorage_over_subscription.rst:74 +msgid "Volume type extra specs" +msgstr "" + +#: ../blockstorage_over_subscription.rst:76 +msgid "" +"If volume type is provided as part of the volume creation request, it can " +"have the following extra specs defined:" +msgstr "" + +#: ../blockstorage_over_subscription.rst:87 +msgid "" +"``capabilities`` scope key before ``thin_provisioning_support`` and " +"``thick_provisioning_support`` is not required. So the following works too:" +msgstr "" + +#: ../blockstorage_over_subscription.rst:96 +msgid "" +"The above extra specs are used by the scheduler to find a back end that " +"supports thin provisioning, thick provisioning, or both to match the needs " +"of a specific volume type." +msgstr "" + +#: ../blockstorage_over_subscription.rst:101 +msgid "Capacity filter" +msgstr "" + +#: ../blockstorage_over_subscription.rst:103 +msgid "" +"In the capacity filter, ``max_over_subscription_ratio`` is used when " +"choosing a back end if ``thin_provisioning_support`` is True and " +"``max_over_subscription_ratio`` is greater than 1.0." +msgstr "" + +#: ../blockstorage_over_subscription.rst:108 +msgid "Capacity weigher" +msgstr "" + +#: ../blockstorage_over_subscription.rst:110 +msgid "" +"In the capacity weigher, virtual free capacity is used for ranking if " +"``thin_provisioning_support`` is True. Otherwise, real free capacity will be " +"used as before." +msgstr "" + +#: ../blockstorage_ratelimit_volume_copy_bandwidth.rst:8 +msgid "Rate-limit volume copy bandwidth" +msgstr "" + +#: ../blockstorage_ratelimit_volume_copy_bandwidth.rst:10 +msgid "" +"When you create a new volume from an image or an existing volume, or when " +"you upload a volume image to the Image service, large data copy may stress " +"disk and network bandwidth. To mitigate slow down of data access from the " +"instances, OpenStack Block Storage supports rate-limiting of volume data " +"copy bandwidth." +msgstr "" + +#: ../blockstorage_ratelimit_volume_copy_bandwidth.rst:17 +msgid "Configure volume copy bandwidth limit" +msgstr "" + +#: ../blockstorage_ratelimit_volume_copy_bandwidth.rst:19 +msgid "" +"To configure the volume copy bandwidth limit, set the " +"``volume_copy_bps_limit`` option in the configuration groups for each back " +"end in the :file:`cinder.conf` file. This option takes the integer of " +"maximum bandwidth allowed for volume data copy in byte per second. If this " +"option is set to ``0``, the rate-limit is disabled." +msgstr "" + +#: ../blockstorage_ratelimit_volume_copy_bandwidth.rst:25 +msgid "" +"While multiple volume data copy operations are running in the same back end, " +"the specified bandwidth is divided to each copy." +msgstr "" + +#: ../blockstorage_ratelimit_volume_copy_bandwidth.rst:28 +msgid "" +"Example :file:`cinder.conf` configuration file to limit volume copy " +"bandwidth of ``lvmdriver-1`` up to 100 MiB/s:" +msgstr "" + +#: ../blockstorage_ratelimit_volume_copy_bandwidth.rst:42 +msgid "" +"This feature requires libcgroup to set up blkio cgroup for disk I/O " +"bandwidth limit. The libcgroup is provided by the cgroup-bin package in " +"Debian and Ubuntu, or by the libcgroup-tools package in Fedora, Red Hat " +"Enterprise Linux, CentOS, openSUSE, and SUSE Linux Enterprise." +msgstr "" + +#: ../blockstorage_ratelimit_volume_copy_bandwidth.rst:49 +msgid "" +"Some back ends which use remote file systems such as NFS are not supported " +"by this feature." +msgstr "" + +#: ../blockstorage_volume_backed_image.rst:6 +msgid "Volume-backed image" +msgstr "" + +#: ../blockstorage_volume_backed_image.rst:8 +msgid "" +"OpenStack Block Storage can quickly create a volume from an image that " +"refers to a volume storing image data (Image-Volume). Compared to the other " +"stores such as file and swift, creating a volume from a Volume-backed image " +"performs better when the block storage driver supports efficient volume " +"cloning." +msgstr "" + +#: ../blockstorage_volume_backed_image.rst:13 +msgid "" +"If the image is set to public in the Image service, the volume data can be " +"shared among tenants." +msgstr "" + +#: ../blockstorage_volume_backed_image.rst:17 +msgid "Configure the Volume-backed image" +msgstr "" + +#: ../blockstorage_volume_backed_image.rst:19 +msgid "" +"Volume-backed image feature requires locations information from the cinder " +"store of the Image service. To enable the Image service to use the cinder " +"store, add ``cinder`` to the ``stores`` option in the ``glance_store`` " +"section of the :file:`glance-api.conf` file::" +msgstr "" + +#: ../blockstorage_volume_backed_image.rst:26 +msgid "" +"To expose locations information, set the following options in the " +"``DEFAULT`` section of the :file:`glance-api.conf` file::" +msgstr "" + +#: ../blockstorage_volume_backed_image.rst:31 +msgid "" +"To enable the Block Storage services to create a new volume by cloning " +"Image- Volume, set the following options in the ``DEFAULT`` section of the :" +"file:`cinder.conf` file. For example::" +msgstr "" + +#: ../blockstorage_volume_backed_image.rst:38 +msgid "" +"To enable the :command:`cinder upload-to-image` command to create an image " +"that refers an Image-Volume, set the following options in each back-end " +"section of the :file:`cinder.conf` file::" +msgstr "" + +#: ../blockstorage_volume_backed_image.rst:44 +msgid "" +"By default, the :command:`upload-to-image` command creates the Image-Volume " +"in the current tenant. To store the Image-Volume into the internal tenant, " +"set the following options in each back-end section of the :file:`cinder." +"conf` file::" +msgstr "" + +#: ../blockstorage_volume_backed_image.rst:52 +msgid "Creating a Volume-backed image" +msgstr "" + +#: ../blockstorage_volume_backed_image.rst:54 +msgid "" +"To register an existing volume as a new Volume-backed image, use the " +"following commands::" +msgstr "" + +#: ../blockstorage_volume_backed_image.rst:61 +msgid "" +"If the ``image_upload_use_cinder_backend`` option is enabled, the following " +"command creates a new Image-Volume by cloning the specified volume and then " +"registers its location to a new image. The disk format and the container " +"format must be raw and bare (default). Otherwise, the image is uploaded to " +"the default store of the Image service.::" +msgstr "" + +#: ../blockstorage_volume_backed_image.rst:70 +msgid "" +"Currently, the cinder store of the Image services does not support uploading " +"and downloading of image data. By this limitation, Volume-backed images can " +"only be used to create a new volume." +msgstr "" + +#: ../blockstorage_volume_backups.rst:8 +msgid "Back up and restore volumes" +msgstr "" + +#: ../blockstorage_volume_backups.rst:10 +msgid "" +"The **cinder** command-line interface provides the tools for creating a " +"volume backup. You can restore a volume from a backup as long as the " +"backup's associated database information (or backup metadata) is intact in " +"the Block Storage database." +msgstr "" + +#: ../blockstorage_volume_backups.rst:15 +msgid "Run this command to create a backup of a volume::" +msgstr "" + +#: ../blockstorage_volume_backups.rst:19 +msgid "" +"Where *VOLUME* is the name or ID of the volume, ``incremental`` is a flag " +"that indicates whether an incremental backup should be performed, and " +"``force`` is a flag that allows or disallows backup of a volume when the " +"volume is attached to an instance." +msgstr "" + +#: ../blockstorage_volume_backups.rst:24 +msgid "" +"Without the ``incremental`` flag, a full backup is created by default. With " +"the ``incremental`` flag, an incremental backup is created." +msgstr "" + +#: ../blockstorage_volume_backups.rst:27 +msgid "" +"Without the ``force`` flag, the volume will be backed up only if its status " +"is ``available``. With the ``force`` flag, the volume will be backed up " +"whether its status is ``available`` or ``in-use``. A volume is ``in-use`` " +"when it is attached to an instance. The backup of an ``in-use`` volume means " +"your data is crash consistent. The ``force`` flag is False by default." +msgstr "" + +#: ../blockstorage_volume_backups.rst:36 +msgid "" +"The ``incremental`` and ``force`` flags are only available for block storage " +"API v2. You have to specify [--os-volume-api-version 2] in the **cinder** " +"command-line interface to use this parameter." +msgstr "" + +#: ../blockstorage_volume_backups.rst:41 +msgid "The ``force`` flag is new in OpenStack Liberty." +msgstr "" + +#: ../blockstorage_volume_backups.rst:43 +msgid "" +"The incremental backup is based on a parent backup which is an existing " +"backup with the latest timestamp. The parent backup can be a full backup or " +"an incremental backup depending on the timestamp." +msgstr "" + +#: ../blockstorage_volume_backups.rst:50 +msgid "" +"The first backup of a volume has to be a full backup. Attempting to do an " +"incremental backup without any existing backups will fail. There is an " +"``is_incremental`` flag that indicates whether a backup is incremental when " +"showing details on the backup. Another flag, ``has_dependent_backups``, " +"returned when showing backup details, will indicate whether the backup has " +"dependent backups. If it is true, attempting to delete this backup will fail." msgstr "" #: ../blockstorage_volume_backups.rst:58 @@ -1741,367 +2616,112 @@ msgid "" "``backup_swift_object_size``." msgstr "" -#: ../compute-images-instances.rst:67 +#: ../blockstorage_volume_backups.rst:66 msgid "" -"A new empty ephemeral disk is also created, labeled ``vdb`` in this diagram. " -"This disk is destroyed when you delete the instance." +"This command also returns a backup ID. Use this backup ID when restoring the " +"volume::" msgstr "" -#: ../telemetry-data-collection.rst:779 +#: ../blockstorage_volume_backups.rst:71 +msgid "When restoring from a full backup, it is a full restore." +msgstr "" + +#: ../blockstorage_volume_backups.rst:73 msgid "" -"A new sample is created with the properties described in the ``target`` " -"section of the transformer's configuration. The sample's volume is the " -"result of the provided expression. The calculation is performed on samples " -"from the same resource." +"When restoring from an incremental backup, a list of backups is built based " +"on the IDs of the parent backups. A full restore is performed based on the " +"full backup first, then restore is done based on the incremental backup, " +"laying on top of it in order." msgstr "" -#: ../telemetry-data-collection.rst:875 +#: ../blockstorage_volume_backups.rst:78 msgid "" -"A notification message may contain multiple meters. You can use ``*`` in the " -"meter definition to capture all the meters and generate samples " -"respectively. You can use wild cards as shown in the following example::" +"You can view a backup list with the :command:`cinder backup-list` command. " +"Optional arguments to clarify the status of your backups include: running " +"``--name``, ``--status``, and ``--volume-id`` to filter through backups by " +"the specified name, status, or volume-id. Search with ``--all-tenants`` for " +"details of the tenants associated with the listed backups." msgstr "" -#: ../networking_adv-features.rst:41 +#: ../blockstorage_volume_backups.rst:85 msgid "" -"A number of terms are used in the provider extension and in the " -"configuration of plug-ins supporting the provider extension:" +"Because volume backups are dependent on the Block Storage database, you must " +"also back up your Block Storage database regularly to ensure data recovery." msgstr "" -#: ../objectstorage_components.rst:175 +#: ../blockstorage_volume_backups.rst:90 msgid "" -"A partition is a collection of stored data, including account databases, " -"container databases, and objects. Partitions are core to the replication " -"system." +"Alternatively, you can export and save the metadata of selected volume " +"backups. Doing so precludes the need to back up the entire Block Storage " +"database. This is useful if you need only a small subset of volumes to " +"survive a catastrophic database failure." msgstr "" -#: ../telemetry-events.rst:134 +#: ../blockstorage_volume_backups.rst:95 msgid "" -"A path specification for the field(s) in the notification you wish to " -"extract for this trait. Specifications can be written to match multiple " -"possible fields. By default the value will be the first such field. The " -"paths can be specified with a dot syntax (``payload.host``). Square bracket " -"syntax (``payload[host]``) is also supported. In either case, if the key for " -"the field you are looking for contains special characters, like ``.``, it " -"will need to be quoted (with double or single quotes): ``payload." -"image_meta.’org.openstack__1__architecture’``. The syntax used for the field " -"specification is a variant of `JSONPath `__" +"If you specify a UUID encryption key when setting up the volume " +"specifications, the backup metadata ensures that the key will remain valid " +"when you back up and restore the volume." msgstr "" -#: ../objectstorage_account_reaper.rst:43 +#: ../blockstorage_volume_backups.rst:99 msgid "" -"A persistent error state may prevent the deletion of an object or container. " -"If this happens, you will see a message in the log, for example::" +"For more information about how to export and import volume backup metadata, " +"see the section called :ref:`volume_backups_export_import`." msgstr "" -#: ../compute_arch.rst:186 +#: ../blockstorage_volume_backups.rst:102 +msgid "By default, the swift object store is used for the backup repository." +msgstr "" + +#: ../blockstorage_volume_backups.rst:104 msgid "" -"A persistent volume does not provide concurrent access from multiple " -"instances. That type of configuration requires a traditional network file " -"system like NFS, or CIFS, or a cluster file system such as GlusterFS. These " -"systems can be built within an OpenStack cluster, or provisioned outside of " -"it, but OpenStack software does not provide these features." +"If instead you want to use an NFS export as the backup repository, add the " +"following configuration options to the ``[DEFAULT]`` section of the :file:" +"`cinder.conf` file and restart the Block Storage services:" msgstr "" -#: ../compute_arch.rst:161 +#: ../blockstorage_volume_backups.rst:114 msgid "" -"A persistent volume is represented by a persistent virtualized block device " -"independent of any particular instance, and provided by OpenStack Block " -"Storage." +"For the ``backup_share`` option, replace *HOST* with the DNS resolvable host " +"name or the IP address of the storage server for the NFS share, and " +"*EXPORT_PATH* with the path to that share. If your environment requires that " +"non-default mount options be specified for the share, set these as follows:" msgstr "" -#: ../identity_concepts.rst:61 +#: ../blockstorage_volume_backups.rst:125 msgid "" -"A personality with a defined set of user rights and privileges to perform a " -"specific set of operations. The Identity service issues a token that " -"includes a list of roles to a user. When a user calls a service, that " -"service interprets the set of user roles and determines to which operations " -"or resources each role grants access." +"*MOUNT_OPTIONS* is a comma-separated string of NFS mount options as detailed " +"in the NFS man page." msgstr "" -#: ../networking_config-agents.rst:291 -msgid "A plug-in that uses LinuxBridge:" -msgstr "" - -#: ../networking_adv-features.rst:711 +#: ../blockstorage_volume_backups.rst:128 msgid "" -"A plus-separated (+) list of next-hop IP addresses. For example, " -"``1.1.1.1+1.1.1.2``." +"There are several other options whose default values may be overridden as " +"appropriate for your environment:" msgstr "" -#: ../compute_arch.rst:206 +#: ../blockstorage_volume_backups.rst:138 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, " -"or for transitioning from EC2-based clouds to OpenStack. For more " -"information, see the `euca2ools site `__." +"The option ``backup_compression_algorithm`` can be set to ``bz2`` or " +"``None``. The latter can be a useful setting when the server providing the " +"share for the backup repository itself performs deduplication or compression " +"on the backup data." msgstr "" -#: ../keystone_integrate_identity_backend_ldap.rst:156 +#: ../blockstorage_volume_backups.rst:143 msgid "" -"A read-only implementation is recommended for LDAP integration. These " -"permissions are applied to object types in the :file:`/etc/keystone/domains/" -"keystone.DOMAIN_NAME.conf` file:" +"The option ``backup_file_size`` must be a multiple of " +"``backup_sha_block_size_bytes``. It is effectively the maximum file size to " +"be used, given your environment, to hold backup data. Volumes larger than " +"this will be stored in multiple files in the backup repository. The " +"``backup_sha_block_size_bytes`` option determines the size of blocks from " +"the cinder volume being backed up on which digital signatures are calculated " +"in order to enable incremental backup capability." msgstr "" -#: ../keystone_integrate_identity_backend_ldap.rst:52 -msgid "" -"A read-only implementation is recommended for LDAP integration. These " -"permissions are applied to object types in the :file:`keystone.conf`:" -msgstr "" - -#: ../keystone_integrate_assignment_backend_ldap.rst:63 -msgid "" -"A read-only implementation is recommended for LDAP integration. These " -"permissions are applied to object types in the ``keystone.conf`` file:" -msgstr "" - -#: ../blockstorage_over_subscription.rst:11 -msgid "" -"A reference implementation is provided for the default LVM driver. The " -"illustration below uses the LVM driver as an example." -msgstr "" - -#: ../objectstorage_components.rst:279 -msgid "" -"A request comes in for an account/container/object. Using the same " -"consistent hashing, the partition name is generated. A lookup in the ring " -"reveals which storage nodes contain that partition. A request is made to one " -"of the storage nodes to fetch the object and, if that fails, requests are " -"made to the other nodes." -msgstr "" - -#: ../cross_project_cors.rst:125 -msgid "" -"A request was received from the origin 'http://foo.com', however this origin " -"was not found in the permitted list. The cause may be a superfluous port " -"notation (ports 80 and 443 do not need to be specified). To correct, ensure " -"that the configuration property for this host is identical to the host " -"indicated in the log message." -msgstr "" - -#: ../cross_project_cors.rst:137 -msgid "" -"A request was received with the header 'X-Custom-Header', which is not " -"permitted. Add this header to the :code:`allow_headers` configuration " -"property." -msgstr "" - -#: ../objectstorage_account_reaper.rst:8 -msgid "" -"A reseller marks an account for deletion by issuing a ``DELETE`` request on " -"the account's storage URL. This action sets the ``status`` column of the " -"account\\_stat table in the account database and replicas to ``DELETED``, " -"marking the account's data for deletion." -msgstr "" - -#: ../objectstorage_components.rst:59 -msgid "" -"A ring represents a mapping between the names of entities stored on disk and " -"their physical locations. There are separate rings for accounts, containers, " -"and objects. When other components need to perform any operation on an " -"object, container, or account, they need to interact with the appropriate " -"ring to determine their location in the cluster." -msgstr "" - -#: ../networking_auth.rst:89 -msgid "" -"A rule that evaluates successfully if the current user is an administrator " -"or the owner of the resource specified in the request (tenant identifier is " -"equal)." -msgstr "" - -#: ../identity_logging.rst:11 -msgid "" -"A sample logging configuration file is available with the project in :file:" -"`etc/logging.conf.sample`. Like other OpenStack projects, Identity uses the " -"Python logging module, which provides extensive configuration options that " -"let you define the output levels and formats." -msgstr "" - -#: ../telemetry-data-collection.rst:510 -msgid "" -"A sink, on the other hand, is a consumer of data, providing logic for the " -"transformation and publication of data emitted from related sources." -msgstr "" - -#: ../telemetry-alarms.rst:43 -msgid "" -"A sliding time window to indicate how far back into the recent past you want " -"to look." -msgstr "" - -#: ../telemetry-data-collection.rst:489 -msgid "" -"A source is a producer of data: samples or events. In effect, it is a set of " -"pollsters or notification handlers emitting datapoints for a set of matching " -"meters and event types." -msgstr "" - -#: ../orchestration-stack-domain-users.rst:45 -msgid "" -"A special OpenStack Identity service domain is created. For example, the one " -"called ``heat`` and the ID is set in the ``stack_user_domain`` option in :" -"file:`heat.conf`." -msgstr "" - -#: ../telemetry-data-collection.rst:848 -msgid "A standard meter definition looks like the following::" -msgstr "" - -#: ../telemetry-alarms.rst:38 -msgid "" -"A static threshold value with a comparison operator such as greater than or " -"less than." -msgstr "" - -#: ../telemetry-alarms.rst:41 -msgid "A statistic selection to aggregate the data." -msgstr "" - -#: ../compute-node-down.rst:161 -msgid "" -"A storage area network (SAN) used by OpenStack Block Storage (cinder-volumes)" -msgstr "" - -#: ../telemetry-data-collection.rst:176 -msgid "" -"A subset of Object Store statistics requires additional middleware to be " -"installed behind the proxy of Object Store. This additional component emits " -"notifications containing data-flow-oriented meters, namely the ``storage." -"objects.(incoming|outgoing).bytes values``. The list of these meters are " -"listed in :ref:`telemetry-object-storage-meter`, marked with " -"``notification`` as origin." -msgstr "" - -#: ../compute_arch.rst:111 -msgid "" -"A tenant limits users' access to particular images. Each user is assigned a " -"user name and password. Keypairs granting access to an instance are enabled " -"for each user, but quotas are set, so that each tenant can control resource " -"consumption across available hardware resources." -msgstr "" - -#: ../telemetry-events.rst:43 -msgid "A timestamp of when the event occurred in the system." -msgstr "" - -#: ../telemetry-data-collection.rst:727 -msgid "" -"A transformer that sums up the incoming samples until enough samples have " -"come in or a timeout has been reached." -msgstr "" - -#: ../orchestration-auth-model.rst:59 -msgid "" -"A trust is an OpenStack Identity extension that provides a method to enable " -"delegation, and optionally impersonation via OpenStack Identity. The key " -"terminology is *trustor* (the user delegating) and *trustee* (the user being " -"delegated to)." -msgstr "" - -#: ../compute-remote-console-access.rst:119 -msgid "A typical deployment has the following components:" -msgstr "" - -#: ../compute_arch.rst:321 -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 " -"they are permitted to issue the subject command. The availability of objects " -"implicated in the request is evaluated and, if available, the request is " -"routed to the queuing engine for the relevant workers. Workers continually " -"listen to the queue based on their role, and occasionally their type host " -"name. When an applicable work request arrives on the queue, the worker takes " -"assignment of the task and begins executing it. Upon completion, a response " -"is dispatched to the queue which is received by the API server and relayed " -"to the originating user. Database entries are queried, added, or removed as " -"necessary during the process." -msgstr "" - -#: ../cross_project_cors.rst:132 -msgid "" -"A user agent has requested permission to perform a DELETE request, however " -"the CORS configuration for the domain does not permit this. To correct, add " -"this method to the :code:`allow_methods` configuration property." -msgstr "" - -#: ../identity_concepts.rst:161 -msgid "" -"A user can have different roles in different tenants. For example, Alice " -"might also have the ``admin`` role in the ``Cyberdyne`` tenant. A user can " -"also have multiple roles in the same tenant." -msgstr "" - -#: ../compute-remote-console-access.rst:69 -msgid "" -"A user connects to the API and gets an ``access_url`` such as, ``http://ip:" -"port/?token=xyz``." -msgstr "" - -#: ../orchestration-stack-domain-users.rst:48 -msgid "" -"A user with sufficient permissions to create and delete projects and users " -"in the ``heat`` domain is created." -msgstr "" - -#: ../networking_adv-features.rst:696 ../networking_adv-features.rst:701 -msgid "A valid CIDR or one of the keywords 'any' or 'external'" -msgstr "" - -#: ../compute-images-instances.rst:272 -msgid "A value of ``!`` disallows the corresponding operation for a property." -msgstr "" - -#: ../compute-images-instances.rst:270 -msgid "A value of ``@`` allows the corresponding operation for a property." -msgstr "" - -#: ../networking_adv-features.rst:67 -msgid "" -"A virtual network administratively created to map to a specific network in " -"the data center, typically to enable direct access to non-OpenStack " -"resources on that network. Tenants can be given access to provider networks." -msgstr "" - -#: ../networking_adv-features.rst:94 -msgid "" -"A virtual network implemented as network packets encapsulated using GRE. GRE " -"networks are also referred to as *tunnels*. GRE tunnel packets are routed by " -"the IP routing table for the host, so GRE networks are not associated by " -"Networking with specific physical networks." -msgstr "" - -#: ../networking_adv-features.rst:73 -msgid "" -"A virtual network implemented as packets on a specific physical network " -"containing IEEE 802.1Q headers with a specific VID field value. VLAN " -"networks sharing the same physical network are isolated from each other at " -"L2 and can even have overlapping IP address spaces. Each distinct physical " -"network supporting VLAN networks is treated as a separate VLAN trunk, with a " -"distinct space of VID values. Valid VID values are 1 through 4094." -msgstr "" - -#: ../networking_adv-features.rst:84 -msgid "" -"A virtual network implemented as packets on a specific physical network " -"containing no IEEE 802.1Q header. Each physical network can realize at most " -"one flat network." -msgstr "" - -#: ../networking_adv-features.rst:63 -msgid "" -"A virtual network that a tenant or an administrator creates. The physical " -"details of the network are not exposed to the tenant." -msgstr "" - -#: ../networking_adv-features.rst:89 -msgid "" -"A virtual network that allows communication within each host, but not across " -"a network. Local networks are intended mainly for single-node test " -"scenarios, but can have other uses." +#: ../blockstorage_volume_backups_export_import.rst:8 +msgid "Export and import backup metadata" msgstr "" #: ../blockstorage_volume_backups_export_import.rst:11 @@ -2111,53 +2731,1968 @@ msgid "" "the database used by the Block Storage service." msgstr "" -#: ../compute-remote-console-access.rst:333 +#: ../blockstorage_volume_backups_export_import.rst:17 msgid "" -"A: Make sure the ``base_url`` match your TLS setting. If you are using https " -"console connections, make sure that the value of ``novncproxy_base_url`` is " -"set explicitly where the ``nova-novncproxy`` service is running." +"For information about how to back up and restore a volume, see the section " +"called :ref:`volume_backups`." msgstr "" -#: ../compute-remote-console-access.rst:273 +#: ../blockstorage_volume_backups_export_import.rst:20 msgid "" -"A: Make sure you are running ``nova-consoleauth`` (in addition to ``nova-" -"novncproxy``). The proxies rely on ``nova-consoleauth`` to validate tokens, " -"and waits for a reply from them until a timeout is reached." +"You can, however, export the metadata of a volume backup. To do so, run this " +"command as an OpenStack ``admin`` user (presumably, after creating a volume " +"backup)::" msgstr "" -#: ../compute-remote-console-access.rst:312 +#: ../blockstorage_volume_backups_export_import.rst:26 msgid "" -"A: Make sure you have installed ``python-numpy``, which is required to " -"support a newer version of the WebSocket protocol (HyBi-07+)." +"Where *BACKUP_ID* is the volume backup's ID. This command should return the " +"backup's corresponding database information as encoded string metadata." msgstr "" -#: ../compute-remote-console-access.rst:280 +#: ../blockstorage_volume_backups_export_import.rst:29 msgid "" -"A: The default options work for an all-in-one install, but changes must be " -"made on your compute hosts once you start to build a cluster. As an example, " -"suppose you have two servers:" +"Exporting and storing this encoded string metadata allows you to completely " +"restore the backup, even in the event of a catastrophic database failure. " +"This will preclude the need to back up the entire Block Storage database, " +"particularly if you only need to keep complete backups of a small subset of " +"volumes." msgstr "" -#: ../compute-remote-console-access.rst:318 +#: ../blockstorage_volume_backups_export_import.rst:35 msgid "" -"A: These values are hard-coded in a Django HTML template. To alter them, " -"edit the :file:`_detail_vnc.html` template file. The location of this file " -"varies based on Linux distribution. On Ubuntu 14.04, the file is at ``/usr/" -"share/pyshared/horizon/dashboards/nova/instances/templates/instances/" -"_detail_vnc.html``." +"If you have placed encryption on your volumes, the encryption will still be " +"in place when you restore the volume if a UUID encryption key is specified " +"when creating volumes. Using backup metadata support, UUID keys set up for a " +"volume (or volumes) will remain valid when you restore a backed-up volume. " +"The restored volume will remain encrypted, and will be accessible with your " +"credentials." msgstr "" -#: ../compute-remote-console-access.rst:267 +#: ../blockstorage_volume_backups_export_import.rst:42 msgid "" -"A: You need ``nova-novncproxy``, ``nova-consoleauth``, and correctly " -"configured compute hosts." +"In addition, having a volume backup and its backup metadata also provides " +"volume portability. Specifically, backing up a volume and exporting its " +"metadata will allow you to restore the volume on a completely different " +"Block Storage database, or even on a different cloud service. To do so, " +"first import the backup metadata to the Block Storage database and then " +"restore the backup." msgstr "" -#: ../compute-remote-console-access.rst:260 +#: ../blockstorage_volume_backups_export_import.rst:49 msgid "" -"A: ``nova-xvpvncproxy``, which ships with OpenStack Compute, is a proxy that " -"supports a simple Java client. nova-novncproxy uses noVNC to provide VNC " -"support through a web browser." +"To import backup metadata, run the following command as an OpenStack " +"``admin``::" +msgstr "" + +#: ../blockstorage_volume_backups_export_import.rst:54 +msgid "Where *METADATA* is the backup metadata exported earlier." +msgstr "" + +#: ../blockstorage_volume_backups_export_import.rst:56 +msgid "" +"Once you have imported the backup metadata into a Block Storage database, " +"restore the volume (see the section called :ref:`volume_backups`)." +msgstr "" + +#: ../blockstorage_volume_migration.rst:8 +msgid "Migrate volumes" +msgstr "" + +#: ../blockstorage_volume_migration.rst:10 +msgid "" +"OpenStack has the ability to migrate volumes between back-ends which support " +"its volume-type. Migrating a volume transparently moves its data from the " +"current back-end for the volume to a new one. This is an administrator " +"function, and can be used for functions including storage evacuation (for " +"maintenance or decommissioning), or manual optimizations (for example, " +"performance, reliability, or cost)." +msgstr "" + +#: ../blockstorage_volume_migration.rst:17 +msgid "These workflows are possible for a migration:" +msgstr "" + +#: ../blockstorage_volume_migration.rst:19 +msgid "" +"If the storage can migrate the volume on its own, it is given the " +"opportunity to do so. This allows the Block Storage driver to enable " +"optimizations that the storage might be able to perform. If the back-end is " +"not able to perform the migration, the Block Storage uses one of two generic " +"flows, as follows." +msgstr "" + +#: ../blockstorage_volume_migration.rst:25 +msgid "" +"If the volume is not attached, the Block Storage service creates a volume " +"and copies the data from the original to the new volume." +msgstr "" + +#: ../blockstorage_volume_migration.rst:30 +msgid "" +"While most back-ends support this function, not all do. See the driver " +"documentation in the `OpenStack Configuration Reference `__ for more details." +msgstr "" + +#: ../blockstorage_volume_migration.rst:35 +msgid "" +"If the volume is attached to a VM instance, the Block Storage creates a " +"volume, and calls Compute to copy the data from the original to the new " +"volume. Currently this is supported only by the Compute libvirt driver." +msgstr "" + +#: ../blockstorage_volume_migration.rst:39 +msgid "" +"As an example, this scenario shows two LVM back-ends and migrates an " +"attached volume from one to the other. This scenario uses the third " +"migration flow." +msgstr "" + +#: ../blockstorage_volume_migration.rst:42 +msgid "First, list the available back-ends:" +msgstr "" + +#: ../blockstorage_volume_migration.rst:63 +msgid "Only Block Storage V2 API supports :command:`get-pools`." +msgstr "" + +#: ../blockstorage_volume_migration.rst:65 +msgid "You can also get available back-ends like following:" +msgstr "" + +#: ../blockstorage_volume_migration.rst:73 +msgid "" +"But it needs to add pool name in the end. For example, " +"``server1@lvmstorage-1#zone1``." +msgstr "" + +#: ../blockstorage_volume_migration.rst:76 +msgid "" +"Next, as the admin user, you can see the current status of the volume " +"(replace the example ID with your own):" +msgstr "" + +#: ../blockstorage_volume_migration.rst:107 +msgid "Note these attributes:" +msgstr "" + +#: ../blockstorage_volume_migration.rst:109 +msgid "``os-vol-host-attr:host`` - the volume's current back-end." +msgstr "" + +#: ../blockstorage_volume_migration.rst:110 +msgid "" +"``os-vol-mig-status-attr:migstat`` - the status of this volume's migration " +"(None means that a migration is not currently in progress)." +msgstr "" + +#: ../blockstorage_volume_migration.rst:112 +msgid "" +"``os-vol-mig-status-attr:name_id`` - the volume ID that this volume's name " +"on the back-end is based on. Before a volume is ever migrated, its name on " +"the back-end storage may be based on the volume's ID (see the " +"``volume_name_template`` configuration parameter). For example, if " +"``volume_name_template`` is kept as the default value (``volume-%s``), your " +"first LVM back-end has a logical volume named ``volume-6088f80a-f116-4331-" +"ad48-9afb0dfb196c``. During the course of a migration, if you create a " +"volume and copy over the data, the volume get the new name but keeps its " +"original ID. This is exposed by the ``name_id`` attribute." +msgstr "" + +#: ../blockstorage_volume_migration.rst:125 +msgid "" +"If you plan to decommission a block storage node, you must stop the " +"``cinder`` volume service on the node after performing the migration." +msgstr "" + +#: ../blockstorage_volume_migration.rst:128 +msgid "" +"On nodes that run CentOS, Fedora, openSUSE, Red Hat Enterprise Linux, or " +"SUSE Linux Enterprise, run:" +msgstr "" + +#: ../blockstorage_volume_migration.rst:136 +msgid "On nodes that run Ubuntu or Debian, run:" +msgstr "" + +#: ../blockstorage_volume_migration.rst:143 +msgid "" +"Stopping the cinder volume service will prevent volumes from being allocated " +"to the node." +msgstr "" + +#: ../blockstorage_volume_migration.rst:146 +msgid "Migrate this volume to the second LVM back-end:" +msgstr "" + +#: ../blockstorage_volume_migration.rst:153 +msgid "" +"You can use the :command:`cinder show` command to see the status of the " +"migration. While migrating, the ``migstat`` attribute shows states such as " +"``migrating`` or ``completing``. On error, ``migstat`` is set to None and " +"the host attribute shows the original ``host``. On success, in this example, " +"the output looks like:" +msgstr "" + +#: ../blockstorage_volume_migration.rst:183 +msgid "" +"Note that ``migstat`` is None, host is the new host, and ``name_id`` holds " +"the ID of the volume created by the migration. If you look at the second LVM " +"back end, you find the logical volume ``volume-133d1f56-9ffc-4f57-8798-" +"d5217d851862``." +msgstr "" + +#: ../blockstorage_volume_migration.rst:190 +msgid "" +"The migration is not visible to non-admin users (for example, through the " +"volume ``status``). However, some operations are not allowed while a " +"migration is taking place, such as attaching/detaching a volume and deleting " +"a volume. If a user performs such an action during a migration, an error is " +"returned." +msgstr "" + +#: ../blockstorage_volume_migration.rst:198 +msgid "Migrating volumes that have snapshots are currently not allowed." +msgstr "" + +#: ../blockstorage_volume_number_weigher.rst:8 +msgid "Configure and use volume number weigher" +msgstr "" + +#: ../blockstorage_volume_number_weigher.rst:10 +msgid "" +"OpenStack Block Storage enables you to choose a volume back end according to " +"``free_capacity`` and ``allocated_capacity``. The volume number weigher " +"feature lets the scheduler choose a volume back end based on its volume " +"number in the volume back end. This can provide another means to improve the " +"volume back ends' I/O balance and the volumes' I/O performance." +msgstr "" + +#: ../blockstorage_volume_number_weigher.rst:17 +msgid "Enable volume number weigher" +msgstr "" + +#: ../blockstorage_volume_number_weigher.rst:19 +msgid "" +"To enable a volume number weigher, set the ``scheduler_default_weighers`` to " +"``VolumeNumberWeigher`` flag in the :file:`cinder.conf` file to define " +"``VolumeNumberWeigher`` as the selected weigher." +msgstr "" + +#: ../blockstorage_volume_number_weigher.rst:28 +msgid "" +"To configure ``VolumeNumberWeigher``, use ``LVMVolumeDriver`` as the volume " +"driver." +msgstr "" + +#: ../blockstorage_volume_number_weigher.rst:31 +msgid "" +"This configuration defines two LVM volume groups: ``stack-volumes`` with 10 " +"GB capacity and ``stack-volumes-1`` with 60 GB capacity. This example " +"configuration defines two back ends:" +msgstr "" + +#: ../blockstorage_volume_number_weigher.rst:53 +msgid "Define a volume type in Block Storage::" +msgstr "" + +#: ../blockstorage_volume_number_weigher.rst:57 +msgid "" +"Create an extra specification that links the volume type to a back-end name::" +msgstr "" + +#: ../blockstorage_volume_number_weigher.rst:61 +msgid "" +"This example creates a lvm volume type with ``volume_backend_name=LVM`` as " +"extra specifications." +msgstr "" + +#: ../blockstorage_volume_number_weigher.rst:67 +msgid "" +"To create six 1-GB volumes, run the :command:`cinder create --volume-type " +"lvm 1` command six times::" +msgstr "" + +#: ../blockstorage_volume_number_weigher.rst:72 +msgid "" +"This command creates three volumes in ``stack-volumes`` and three volumes in " +"``stack-volumes-1``." +msgstr "" + +#: ../blockstorage_volume_number_weigher.rst:75 +msgid "List the available volumes::" +msgstr "" + +#: ../compute-admin-password-injection.rst:5 +msgid "Injecting the administrator password" +msgstr "" + +#: ../compute-admin-password-injection.rst:7 +msgid "" +"Compute can generate a random administrator (root) password and inject that " +"password into an instance. If this feature is enabled, users can run :" +"command:`ssh` to an instance without an :command:`ssh` keypair. The random " +"password appears in the output of the :command:`nova boot` command. You can " +"also view and set the admin password from the dashboard." +msgstr "" + +#: ../compute-admin-password-injection.rst:13 +msgid "**Password injection using the dashboard**" +msgstr "" + +#: ../compute-admin-password-injection.rst:15 +msgid "" +"By default, the dashboard will display the ``admin`` password and allow the " +"user to modify it." +msgstr "" + +#: ../compute-admin-password-injection.rst:18 +msgid "" +"If you do not want to support password injection, disable the password " +"fields by editing the dashboard's :file:`local_settings` file. On Fedora/" +"RHEL/CentOS, the file location is :file:`/etc/openstack-dashboard/" +"local_settings`. On Ubuntu and Debian, it is :file:`/etc/openstack-dashboard/" +"local_settings.py`. On openSUSE and SUSE Linux Enterprise Server, it is :" +"file:`/srv/www/openstack-dashboard/openstack_dashboard/local/local_settings." +"py`" +msgstr "" + +#: ../compute-admin-password-injection.rst:33 +msgid "**Password injection on libvirt-based hypervisors**" +msgstr "" + +#: ../compute-admin-password-injection.rst:35 +msgid "" +"For hypervisors that use the libvirt back end (such as KVM, QEMU, and LXC), " +"admin password injection is disabled by default. To enable it, set this " +"option in :file:`/etc/nova/nova.conf`:" +msgstr "" + +#: ../compute-admin-password-injection.rst:44 +msgid "" +"When enabled, Compute will modify the password of the admin account by " +"editing the :file:`/etc/shadow` file inside the virtual machine instance." +msgstr "" + +#: ../compute-admin-password-injection.rst:49 +msgid "" +"Users can only use :command:`ssh` to access the instance by using the admin " +"password if the virtual machine image is a Linux distribution, and it has " +"been configured to allow users to use :command:`ssh` as the root user. This " +"is not the case for `Ubuntu cloud images`_ which, by default, does not allow " +"users to use :command:`ssh` to access the root account." +msgstr "" + +#: ../compute-admin-password-injection.rst:55 +msgid "**Password injection and XenAPI (XenServer/XCP)**" +msgstr "" + +#: ../compute-admin-password-injection.rst:57 +msgid "" +"When using the XenAPI hypervisor back end, Compute uses the XenAPI agent to " +"inject passwords into guests. The virtual machine image must be configured " +"with the agent for password injection to work." +msgstr "" + +#: ../compute-admin-password-injection.rst:61 +msgid "**Password injection and Windows images (all hypervisors)**" +msgstr "" + +#: ../compute-admin-password-injection.rst:65 +msgid "" +"For Windows virtual machines, configure the Windows image to retrieve the " +"admin password on boot by installing an agent such as `cloudbase-init`_." +msgstr "" + +#: ../compute-configuring-migrations.rst:5 +msgid "Configure migrations" +msgstr "" + +#: ../compute-configuring-migrations.rst:12 +msgid "" +"Only cloud administrators can perform live migrations. If your cloud is " +"configured to use cells, you can perform live migration within but not " +"between cells." +msgstr "" + +#: ../compute-configuring-migrations.rst:16 +msgid "" +"Migration enables an administrator to move a virtual-machine instance from " +"one compute host to another. This feature is useful when a compute host " +"requires maintenance. Migration can also be useful to redistribute the load " +"when many VM instances are running on a specific physical machine." +msgstr "" + +#: ../compute-configuring-migrations.rst:22 +msgid "The migration types are:" +msgstr "" + +#: ../compute-configuring-migrations.rst:24 +msgid "" +"**Non-live migration** (sometimes referred to simply as 'migration'). The " +"instance is shut down for a period of time to be moved to another " +"hypervisor. In this case, the instance recognizes that it was rebooted." +msgstr "" + +#: ../compute-configuring-migrations.rst:29 +msgid "" +"**Live migration** (or 'true live migration'). Almost no instance downtime. " +"Useful when the instances must be kept running during the migration. The " +"different types of live migration are:" +msgstr "" + +#: ../compute-configuring-migrations.rst:33 +msgid "" +"**Shared storage-based live migration**. Both hypervisors have access to " +"shared storage." +msgstr "" + +#: ../compute-configuring-migrations.rst:36 +msgid "" +"**Block live migration**. No shared storage is required. Incompatible with " +"read-only devices such as CD-ROMs and `Configuration Drive (config\\_drive) " +"`_." +msgstr "" + +#: ../compute-configuring-migrations.rst:40 +msgid "" +"**Volume-backed live migration**. Instances are backed by volumes rather " +"than ephemeral disk, no shared storage is required, and migration is " +"supported (currently only available for libvirt-based hypervisors)." +msgstr "" + +#: ../compute-configuring-migrations.rst:45 +msgid "" +"The following sections describe how to configure your hosts and compute " +"nodes for migrations by using the KVM and XenServer hypervisors." +msgstr "" + +#: ../compute-configuring-migrations.rst:51 +msgid "KVM-Libvirt" +msgstr "" + +#: ../compute-configuring-migrations.rst:59 +#: ../compute-configuring-migrations.rst:331 +msgid "Shared storage" +msgstr "" + +#: ../compute-configuring-migrations.rst:64 +#: ../compute-configuring-migrations.rst:333 +msgid "**Prerequisites**" +msgstr "" + +#: ../compute-configuring-migrations.rst:66 +msgid "**Hypervisor:** KVM with libvirt" +msgstr "" + +#: ../compute-configuring-migrations.rst:68 +msgid "" +"**Shared storage:** :file:`NOVA-INST-DIR/instances/` (for example, :file:`/" +"var/lib/nova/instances`) has to be mounted by shared storage. This guide " +"uses NFS but other options, including the `OpenStack Gluster Connector " +"`_ are " +"available." +msgstr "" + +#: ../compute-configuring-migrations.rst:74 +msgid "**Instances:** Instance can be migrated with iSCSI-based volumes." +msgstr "" + +#: ../compute-configuring-migrations.rst:76 +msgid "**Notes**" +msgstr "" + +#: ../compute-configuring-migrations.rst:78 +msgid "" +"Because the Compute service does not use the libvirt live migration " +"functionality by default, guests are suspended before migration and might " +"experience several minutes of downtime. For details, see `Enabling true live " +"migration`." +msgstr "" + +#: ../compute-configuring-migrations.rst:83 +msgid "" +"Compute calculates the amount of downtime required using the RAM size of the " +"disk being migrated, in accordance with the ``live_migration_downtime`` " +"configuration parameters. Migration downtime is measured in steps, with an " +"exponential backoff between each step. This means that the maximum downtime " +"between each step starts off small, and is increased in ever larger amounts " +"as Compute waits for the migration to complete. This gives the guest a " +"chance to complete the migration successfully, with a minimum amount of " +"downtime." +msgstr "" + +#: ../compute-configuring-migrations.rst:92 +msgid "" +"This guide assumes the default value for ``instances_path`` in your :file:" +"`nova.conf` file (:file:`NOVA-INST-DIR/instances`). If you have changed the " +"``state_path`` or ``instances_path`` variables, modify the commands " +"accordingly." +msgstr "" + +#: ../compute-configuring-migrations.rst:97 +msgid "" +"You must specify ``vncserver_listen=0.0.0.0`` or live migration will not " +"work correctly." +msgstr "" + +#: ../compute-configuring-migrations.rst:100 +msgid "" +"You must specify the ``instances_path`` in each node that runs nova-compute. " +"The mount point for ``instances_path`` must be the same value for each node, " +"or live migration will not work correctly." +msgstr "" + +#: ../compute-configuring-migrations.rst:108 +msgid "Example Compute installation environment" +msgstr "" + +#: ../compute-configuring-migrations.rst:110 +msgid "" +"Prepare at least three servers. In this example, we refer to the servers as " +"``HostA``, ``HostB``, and ``HostC``:" +msgstr "" + +#: ../compute-configuring-migrations.rst:113 +msgid "" +"``HostA`` is the Cloud Controller, and should run these services: nova-api, " +"nova-scheduler, ``nova-network``, cinder-volume, and ``nova-objectstore``." +msgstr "" + +#: ../compute-configuring-migrations.rst:117 +msgid "``HostB`` and ``HostC`` are the compute nodes that run nova-compute." +msgstr "" + +#: ../compute-configuring-migrations.rst:120 +msgid "" +"Ensure that ``NOVA-INST-DIR`` (set with ``state_path`` in the :file:`nova." +"conf` file) is the same on all hosts." +msgstr "" + +#: ../compute-configuring-migrations.rst:123 +msgid "" +"In this example, ``HostA`` is the NFSv4 server that exports ``NOVA-INST-DIR/" +"instances`` directory. ``HostB`` and ``HostC`` are NFSv4 clients that mount " +"``HostA``." +msgstr "" + +#: ../compute-configuring-migrations.rst:127 +msgid "**Configuring your system**" +msgstr "" + +#: ../compute-configuring-migrations.rst:129 +msgid "" +"Configure your DNS or ``/etc/hosts`` and ensure it is consistent across all " +"hosts. Make sure that the three hosts can perform name resolution with each " +"other. As a test, use the :command:`ping` command to ping each host from one " +"another:" +msgstr "" + +#: ../compute-configuring-migrations.rst:140 +msgid "" +"Ensure that the UID and GID of your Compute and libvirt users are identical " +"between each of your servers. This ensures that the permissions on the NFS " +"mount works correctly." +msgstr "" + +#: ../compute-configuring-migrations.rst:144 +msgid "" +"Ensure you can access SSH without a password and without " +"StrictHostKeyChecking between ``HostB`` and ``HostC`` as ``nova`` user (set " +"with the owner of nova-compute service). Direct access from one compute host " +"to another is needed to copy the VM file across. It is also needed to detect " +"if the source and target compute nodes share a storage subsystem." +msgstr "" + +#: ../compute-configuring-migrations.rst:151 +msgid "" +"Export ``NOVA-INST-DIR/instances`` from ``HostA``, and ensure it is readable " +"and writable by the Compute user on ``HostB`` and ``HostC``." +msgstr "" + +#: ../compute-configuring-migrations.rst:154 +msgid "" +"For more information, see: `SettingUpNFSHowTo `_ or `CentOS/Red Hat: Setup NFS v4.0 File " +"Server `_" +msgstr "" + +#: ../compute-configuring-migrations.rst:157 +msgid "" +"Configure the NFS server at ``HostA`` by adding the following line to the :" +"file:`/etc/exports` file:" +msgstr "" + +#: ../compute-configuring-migrations.rst:164 +msgid "" +"Change the subnet mask (``255.255.0.0``) to the appropriate value to include " +"the IP addresses of ``HostB`` and ``HostC``. Then restart the NFS server:" +msgstr "" + +#: ../compute-configuring-migrations.rst:173 +msgid "" +"On both compute nodes, enable the 'execute/search' bit on your shared " +"directory to allow qemu to be able to use the images within the directories. " +"On all hosts, run the following command:" +msgstr "" + +#: ../compute-configuring-migrations.rst:181 +msgid "" +"Configure NFS on ``HostB`` and ``HostC`` by adding the following line to " +"the :file:`/etc/fstab` file" +msgstr "" + +#: ../compute-configuring-migrations.rst:188 +msgid "Ensure that you can mount the exported directory" +msgstr "" + +#: ../compute-configuring-migrations.rst:194 +msgid "" +"Check that ``HostA`` can see the :file:`NOVA-INST-DIR/instances/` directory" +msgstr "" + +#: ../compute-configuring-migrations.rst:202 +msgid "" +"Perform the same check on ``HostB`` and ``HostC``, paying special attention " +"to the permissions (Compute should be able to write)" +msgstr "" + +#: ../compute-configuring-migrations.rst:221 +msgid "" +"Update the libvirt configurations so that the calls can be made securely. " +"These methods enable remote access over TCP and are not documented here." +msgstr "" + +#: ../compute-configuring-migrations.rst:225 +msgid "SSH tunnel to libvirtd's UNIX socket" +msgstr "" + +#: ../compute-configuring-migrations.rst:227 +msgid "libvirtd TCP socket, with GSSAPI/Kerberos for auth+data encryption" +msgstr "" + +#: ../compute-configuring-migrations.rst:229 +msgid "" +"libvirtd TCP socket, with TLS for encryption and x509 client certs for " +"authentication" +msgstr "" + +#: ../compute-configuring-migrations.rst:232 +msgid "" +"libvirtd TCP socket, with TLS for encryption and Kerberos for authentication" +msgstr "" + +#: ../compute-configuring-migrations.rst:235 +msgid "" +"Restart libvirt. After you run the command, ensure that libvirt is " +"successfully restarted" +msgstr "" + +#: ../compute-configuring-migrations.rst:244 +msgid "" +"Configure your firewall to allow libvirt to communicate between nodes. By " +"default, libvirt listens on TCP port 16509, and an ephemeral TCP range from " +"49152 to 49261 is used for the KVM communications. Based on the secure " +"remote access TCP configuration you chose, be careful which ports you open, " +"and always understand who has access. For information about ports that are " +"used with libvirt, see the `libvirt documentation `_." +msgstr "" + +#: ../compute-configuring-migrations.rst:252 +msgid "" +"Configure the downtime required for the migration by adjusting these " +"parameters in the :file:`nova.conf` file:" +msgstr "" + +#: ../compute-configuring-migrations.rst:261 +msgid "" +"The ``live_migration_downtime`` parameter sets the maximum permitted " +"downtime for a live migration, in milliseconds. This setting defaults to 500 " +"milliseconds." +msgstr "" + +#: ../compute-configuring-migrations.rst:265 +msgid "" +"The ``live_migration_downtime_steps`` parameter sets the total number of " +"incremental steps to reach the maximum downtime value. This setting defaults " +"to 10 steps." +msgstr "" + +#: ../compute-configuring-migrations.rst:269 +msgid "" +"The ``live_migration_downtime_delay`` parameter sets the amount of time to " +"wait between each step, in seconds. This setting defaults to 75 seconds." +msgstr "" + +#: ../compute-configuring-migrations.rst:272 +msgid "" +"You can now configure other options for live migration. In most cases, you " +"will not need to configure any options. For advanced configuration options, " +"see the `OpenStack Configuration Reference Guide `_." +msgstr "" + +#: ../compute-configuring-migrations.rst:281 +msgid "Enabling true live migration" +msgstr "" + +#: ../compute-configuring-migrations.rst:283 +msgid "" +"Prior to the Kilo release, the Compute service did not use the libvirt live " +"migration function by default. To enable this function, add the following " +"line to the ``[libvirt]`` section of the :file:`nova.conf` file:" +msgstr "" + +#: ../compute-configuring-migrations.rst:291 +msgid "" +"On versions older than Kilo, the Compute service does not use libvirt's live " +"migration by default because there is a risk that the migration process will " +"never end. This can happen if the guest operating system uses blocks on the " +"disk faster than they can be migrated." +msgstr "" + +#: ../compute-configuring-migrations.rst:299 +#: ../compute-configuring-migrations.rst:404 +msgid "Block migration" +msgstr "" + +#: ../compute-configuring-migrations.rst:301 +msgid "" +"Configuring KVM for block migration is exactly the same as the above " +"configuration in :ref:`configuring-migrations-kvm-shared-storage` the " +"section called shared storage, except that ``NOVA-INST-DIR/instances`` is " +"local to each host rather than shared. No NFS client or server configuration " +"is required." +msgstr "" + +#: ../compute-configuring-migrations.rst:309 +#: ../compute-configuring-migrations.rst:413 +msgid "" +"To use block migration, you must use the :option:`--block-migrate` parameter " +"with the live migration command." +msgstr "" + +#: ../compute-configuring-migrations.rst:312 +msgid "" +"Block migration is incompatible with read-only devices such as CD-ROMs and " +"`Configuration Drive (config_drive) `_." +msgstr "" + +#: ../compute-configuring-migrations.rst:315 +msgid "" +"Since the ephemeral drives are copied over the network in block migration, " +"migrations of instances with heavy I/O loads may never complete if the " +"drives are writing faster than the data can be copied over the network." +msgstr "" + +#: ../compute-configuring-migrations.rst:323 +msgid "XenServer" +msgstr "" + +#: ../compute-configuring-migrations.rst:335 +msgid "" +"**Compatible XenServer hypervisors**. For more information, see the " +"`Requirements for Creating Resource Pools `_ " +"section of the XenServer Administrator's Guide." +msgstr "" + +#: ../compute-configuring-migrations.rst:339 +msgid "**Shared storage**. An NFS export, visible to all XenServer hosts." +msgstr "" + +#: ../compute-configuring-migrations.rst:343 +msgid "" +"For the supported NFS versions, see the `NFS VHD `_ section of the " +"XenServer Administrator's Guide." +msgstr "" + +#: ../compute-configuring-migrations.rst:347 +msgid "" +"To use shared storage live migration with XenServer hypervisors, the hosts " +"must be joined to a XenServer pool. To create that pool, a host aggregate " +"must be created with specific metadata. This metadata is used by the XAPI " +"plug-ins to establish the pool." +msgstr "" + +#: ../compute-configuring-migrations.rst:352 +msgid "**Using shared storage live migrations with XenServer Hypervisors**" +msgstr "" + +#: ../compute-configuring-migrations.rst:354 +msgid "" +"Add an NFS VHD storage to your master XenServer, and set it as the default " +"storage repository. For more information, see NFS VHD in the XenServer " +"Administrator's Guide." +msgstr "" + +#: ../compute-configuring-migrations.rst:358 +msgid "" +"Configure all compute nodes to use the default storage repository (``sr``) " +"for pool operations. Add this line to your :file:`nova.conf` configuration " +"files on all compute nodes:" +msgstr "" + +#: ../compute-configuring-migrations.rst:366 +msgid "" +"Create a host aggregate. This command creates the aggregate, and then " +"displays a table that contains the ID of the new aggregate" +msgstr "" + +#: ../compute-configuring-migrations.rst:373 +msgid "Add metadata to the aggregate, to mark it as a hypervisor pool" +msgstr "" + +#: ../compute-configuring-migrations.rst:381 +msgid "Make the first compute node part of that aggregate" +msgstr "" + +#: ../compute-configuring-migrations.rst:387 +msgid "The host is now part of a XenServer pool." +msgstr "" + +#: ../compute-configuring-migrations.rst:389 +msgid "Add hosts to the pool" +msgstr "" + +#: ../compute-configuring-migrations.rst:397 +msgid "" +"The added compute node and the host will shut down to join the host to the " +"XenServer pool. The operation will fail if any server other than the compute " +"node is running or suspended on the host." +msgstr "" + +#: ../compute-configuring-migrations.rst:406 +msgid "" +"**Compatible XenServer hypervisors**. The hypervisors must support the " +"Storage XenMotion feature. See your XenServer manual to make sure your " +"edition has this feature." +msgstr "" + +#: ../compute-configuring-migrations.rst:416 +msgid "" +"Block migration works only with EXT local storage storage repositories, and " +"the server must not have any volumes attached." +msgstr "" + +#: ../compute-default-ports.rst:5 +msgid "Compute service node firewall requirements" +msgstr "" + +#: ../compute-default-ports.rst:7 +msgid "" +"Console connections for virtual machines, whether direct or through a proxy, " +"are received on ports ``5900`` to ``5999``. The firewall on each Compute " +"service node must allow network traffic on these ports." +msgstr "" + +#: ../compute-default-ports.rst:11 +msgid "" +"This procedure modifies the iptables firewall to allow incoming connections " +"to the Compute services." +msgstr "" + +#: ../compute-default-ports.rst:14 +msgid "**Configuring the service-node firewall**" +msgstr "" + +#: ../compute-default-ports.rst:16 +msgid "Log in to the server that hosts the Compute service, as root." +msgstr "" + +#: ../compute-default-ports.rst:18 +msgid "" +"Edit the :file:`/etc/sysconfig/iptables` file, to add an INPUT rule that " +"allows TCP traffic on ports from ``5900`` to ``5999``. Make sure the new " +"rule appears before any INPUT rules that REJECT traffic:" +msgstr "" + +#: ../compute-default-ports.rst:26 +msgid "" +"Save the changes to :file:`/etc/sysconfig/iptables` file, and restart the " +"iptables service to pick up the changes:" +msgstr "" + +#: ../compute-default-ports.rst:33 +msgid "Repeat this process for each Compute service node." +msgstr "" + +#: ../compute-euca2ools.rst:5 +msgid "Managing the cloud with euca2ools" +msgstr "" + +#: ../compute-euca2ools.rst:7 +msgid "" +"The ``euca2ools`` command-line tool provides a command line interface to EC2 " +"API calls. For more information about ``euca2ools``, see `https://www." +"eucalyptus.com/docs/eucalyptus/4.1.2/index.html `__." +msgstr "" + +#: ../compute-flavors.rst:5 +msgid "Flavors" +msgstr "" + +#: ../compute-flavors.rst:7 +msgid "" +"Admin users can use the :command:`nova flavor-` commands to customize and " +"manage flavors. To see the available flavor-related commands, run:" +msgstr "" + +#: ../compute-flavors.rst:24 +msgid "" +"Configuration rights can be delegated to additional users by redefining the " +"access controls for ``compute_extension:flavormanage`` in :file:`/etc/nova/" +"policy.json` on the nova-api server." +msgstr "" + +#: ../compute-flavors.rst:29 +msgid "" +"To modify an existing flavor in the dashboard, you must delete the flavor " +"and create a modified one with the same name." +msgstr "" + +#: ../compute-flavors.rst:32 +msgid "Flavors define these elements:" +msgstr "" + +# #-#-#-#-# compute-flavors.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +# #-#-#-#-# compute-manage-volumes.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +# #-#-#-#-# compute-networking-nova.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +# #-#-#-#-# compute-remote-console-access.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +# #-#-#-#-# compute-security.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +# #-#-#-#-# database.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +# #-#-#-#-# networking_adv-features.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +# #-#-#-#-# networking_arch.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +# #-#-#-#-# networking_introduction.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +# #-#-#-#-# networking_multi-dhcp-agents.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +# #-#-#-#-# objectstorage-troubleshoot.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +# #-#-#-#-# telemetry-measurements.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +#: ../compute-flavors.rst:35 ../compute-manage-volumes.rst:14 +#: ../compute-networking-nova.rst:310 ../compute-networking-nova.rst:508 +#: ../compute-remote-console-access.rst:36 +#: ../compute-remote-console-access.rst:153 ../compute-security.rst:104 +#: ../database.rst:107 ../database.rst:145 ../networking_adv-features.rst:47 +#: ../networking_adv-features.rst:130 ../networking_adv-features.rst:693 +#: ../networking_arch.rst:29 ../networking_introduction.rst:29 +#: ../networking_introduction.rst:122 ../networking_multi-dhcp-agents.rst:40 +#: ../objectstorage-troubleshoot.rst:62 ../telemetry-measurements.rst:31 +msgid "Description" +msgstr "" + +#: ../compute-flavors.rst:35 +msgid "Element" +msgstr "" + +#: ../compute-flavors.rst:37 +msgid "" +"A descriptive name. XX.SIZE_NAME is typically not required, though some " +"third party tools may rely on it." +msgstr "" + +# #-#-#-#-# compute-flavors.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +# #-#-#-#-# compute-live-migration-usage.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +# #-#-#-#-# telemetry-measurements.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +# #-#-#-#-# ts-eql-volume-size.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +#: ../compute-flavors.rst:37 ../compute-live-migration-usage.rst:35 +#: ../telemetry-measurements.rst:97 ../telemetry-measurements.rst:430 +#: ../telemetry-measurements.rst:484 ../telemetry-measurements.rst:528 +#: ../telemetry-measurements.rst:589 ../telemetry-measurements.rst:664 +#: ../telemetry-measurements.rst:697 ../telemetry-measurements.rst:752 +#: ../telemetry-measurements.rst:802 ../telemetry-measurements.rst:839 +#: ../telemetry-measurements.rst:910 ../telemetry-measurements.rst:973 +#: ../telemetry-measurements.rst:1059 ../telemetry-measurements.rst:1137 +#: ../telemetry-measurements.rst:1202 ../telemetry-measurements.rst:1253 +#: ../telemetry-measurements.rst:1279 ../telemetry-measurements.rst:1302 +#: ../telemetry-measurements.rst:1322 ../ts-eql-volume-size.rst:110 +msgid "Name" +msgstr "" + +#: ../compute-flavors.rst:40 +msgid "Memory_MB" +msgstr "" + +#: ../compute-flavors.rst:40 +msgid "Virtual machine memory in megabytes." +msgstr "" + +#: ../compute-flavors.rst:42 +msgid "Disk" +msgstr "" + +#: ../compute-flavors.rst:42 +msgid "" +"Virtual root disk size in gigabytes. This is an ephemeral di\\ sk that the " +"base image is copied into. When booting from a p\\ ersistent volume it is " +"not used. The \"0\" size is a special c\\ ase which uses the native base " +"image size as the size of the ephemeral root volume." +msgstr "" + +#: ../compute-flavors.rst:48 +msgid "Ephemeral" +msgstr "" + +#: ../compute-flavors.rst:48 +msgid "" +"Specifies the size of a secondary ephemeral data disk. This is an empty, " +"unformatted disk and exists only for the life o\\ f the instance." +msgstr "" + +#: ../compute-flavors.rst:52 +msgid "Optional swap space allocation for the instance." +msgstr "" + +#: ../compute-flavors.rst:52 +msgid "Swap" +msgstr "" + +#: ../compute-flavors.rst:54 +msgid "Number of virtual CPUs presented to the instance." +msgstr "" + +#: ../compute-flavors.rst:54 +msgid "VCPUs" +msgstr "" + +#: ../compute-flavors.rst:56 +msgid "" +"Optional property allows created servers to have a different bandwidth cap " +"than that defined in the network they are att\\ ached to. This factor is " +"multiplied by the rxtx_base propert\\ y of the network. Default value is " +"1.0. That is, the same as attached network. This parameter is only available " +"for Xen or NSX based systems." +msgstr "" + +#: ../compute-flavors.rst:56 +msgid "RXTX_Factor" +msgstr "" + +#: ../compute-flavors.rst:63 +msgid "" +"Boolean value, whether flavor is available to all users or p\\ rivate to the " +"tenant it was created in. Defaults to True." +msgstr "" + +#: ../compute-flavors.rst:63 +msgid "Is_Public" +msgstr "" + +#: ../compute-flavors.rst:66 +msgid "" +"Key and value pairs that define on which compute nodes a fla\\ vor can run. " +"These pairs must match corresponding pairs on t\\ he compute nodes. Use to " +"implement special resources, such a\\ s flavors that run on only compute " +"nodes with GPU hardware." +msgstr "" + +#: ../compute-flavors.rst:66 +msgid "extra_specs" +msgstr "" + +#: ../compute-flavors.rst:74 +msgid "" +"Flavor customization can be limited by the hypervisor in use. For example " +"the libvirt driver enables quotas on CPUs available to a VM, disk tuning, " +"bandwidth I/O, watchdog behavior, random number generator device control, " +"and instance VIF traffic control." +msgstr "" + +#: ../compute-flavors.rst:80 +msgid "" +"You can configure the CPU limits with control parameters with the ``nova`` " +"client. For example, to configure the I/O limit, use:" +msgstr "" + +#: ../compute-flavors.rst:88 +msgid "" +"Use these optional parameters to control weight shares, enforcement " +"intervals for runtime quotas, and a quota for maximum allowed bandwidth:" +msgstr "" + +#: ../compute-flavors.rst:92 +msgid "" +"``cpu_shares``. Specifies the proportional weighted share for the domain. If " +"this element is omitted, the service defaults to the OS provided defaults. " +"There is no unit for the value; it is a relative measure based on the " +"setting of other VMs. For example, a VM configured with value 2048 gets " +"twice as much CPU time as a VM configured with value 1024." +msgstr "" + +#: ../compute-flavors.rst:99 +msgid "" +"``cpu_shares_level``. On VMWare, specifies the allocation level. Can be " +"``custom``, ``high``, ``normal``, or ``low``. If you choose ``custom``, set " +"the number of shares using ``cpu_shares_share``." +msgstr "" + +#: ../compute-flavors.rst:103 +msgid "" +"``cpu_period``. Specifies the enforcement interval (unit: microseconds) for " +"QEMU and LXC hypervisors. Within a period, each VCPU of the domain is not " +"allowed to consume more than the quota worth of runtime. The value should be " +"in range ``[1000, 1000000]``. A period with value 0 means no value." +msgstr "" + +#: ../compute-flavors.rst:109 +msgid "" +"``cpu_limit``. Specifies the upper limit for VMware machine CPU allocation " +"in MHz. This parameter ensures that a machine never uses more than the " +"defined amount of CPU time. It can be used to enforce a limit on the " +"machine's CPU performance." +msgstr "" + +#: ../compute-flavors.rst:114 +msgid "" +"``cpu_reservation``. Specifies the guaranteed minimum CPU reservation in MHz " +"for VMware. This means that if needed, the machine will definitely get " +"allocated the reserved amount of CPU cycles." +msgstr "" + +#: ../compute-flavors.rst:119 +msgid "" +"``cpu_quota``. Specifies the maximum allowed bandwidth (unit: microseconds). " +"A domain with a negative-value quota indicates that the domain has infinite " +"bandwidth, which means that it is not bandwidth controlled. The value should " +"be in range ``[1000, 18446744073709551]`` or less than 0. A quota with value " +"0 means no value. You can use this feature to ensure that all vCPUs run at " +"the same speed. For example:" +msgstr "" + +#: ../compute-flavors.rst:132 +msgid "" +"In this example, the instance of ``m1.low_cpu`` can only consume a maximum " +"of 50% CPU of a physical CPU computing capability." +msgstr "" + +#: ../compute-flavors.rst:133 +msgid "CPU limits" +msgstr "" + +#: ../compute-flavors.rst:136 +msgid "" +"Using disk I/O quotas, you can set maximum disk write to 10 MB per second " +"for a VM user. For example:" +msgstr "" + +#: ../compute-flavors.rst:143 +msgid "The disk I/O options are:" +msgstr "" + +#: ../compute-flavors.rst:145 +msgid "disk\\_read\\_bytes\\_sec" +msgstr "" + +#: ../compute-flavors.rst:147 +msgid "disk\\_read\\_iops\\_sec" +msgstr "" + +#: ../compute-flavors.rst:149 +msgid "disk\\_write\\_bytes\\_sec" +msgstr "" + +#: ../compute-flavors.rst:151 +msgid "disk\\_write\\_iops\\_sec" +msgstr "" + +#: ../compute-flavors.rst:153 +msgid "disk\\_total\\_bytes\\_sec" +msgstr "" + +#: ../compute-flavors.rst:155 +msgid "Disk tuning" +msgstr "" + +#: ../compute-flavors.rst:155 +msgid "disk\\_total\\_iops\\_sec" +msgstr "" + +#: ../compute-flavors.rst:158 +msgid "The vif I/O options are:" +msgstr "" + +#: ../compute-flavors.rst:160 +msgid "vif\\_inbound\\_ average" +msgstr "" + +#: ../compute-flavors.rst:162 +msgid "vif\\_inbound\\_burst" +msgstr "" + +#: ../compute-flavors.rst:164 +msgid "vif\\_inbound\\_peak" +msgstr "" + +#: ../compute-flavors.rst:166 +msgid "vif\\_outbound\\_ average" +msgstr "" + +#: ../compute-flavors.rst:168 +msgid "vif\\_outbound\\_burst" +msgstr "" + +#: ../compute-flavors.rst:170 +msgid "vif\\_outbound\\_peak" +msgstr "" + +#: ../compute-flavors.rst:172 +msgid "" +"Incoming and outgoing traffic can be shaped independently. The bandwidth " +"element can have at most, one inbound and at most, one outbound child " +"element. If you leave any of these child elements out, no quality of service " +"(QoS) is applied on that traffic direction. So, if you want to shape only " +"the network's incoming traffic, use inbound only (and vice versa). Each " +"element has one mandatory attribute average, which specifies the average bit " +"rate on the interface being shaped." +msgstr "" + +#: ../compute-flavors.rst:181 +msgid "" +"There are also two optional attributes (integer): ``peak``, which specifies " +"the maximum rate at which a bridge can send data (kilobytes/second), and " +"``burst``, the amount of bytes that can be burst at peak speed (kilobytes). " +"The rate is shared equally within domains connected to the network." +msgstr "" + +#: ../compute-flavors.rst:187 +msgid "" +"Below example sets network traffic bandwidth limits for existing flavor as " +"follow:" +msgstr "" + +#: ../compute-flavors.rst:190 +msgid "Outbound traffic:" +msgstr "" + +#: ../compute-flavors.rst:192 ../compute-flavors.rst:200 +msgid "average: 256 Mbps (32768 kilobytes/second)" +msgstr "" + +#: ../compute-flavors.rst:194 ../compute-flavors.rst:202 +msgid "peak: 512 Mbps (65536 kilobytes/second)" +msgstr "" + +#: ../compute-flavors.rst:196 ../compute-flavors.rst:204 +msgid "burst: 65536 kilobytes" +msgstr "" + +#: ../compute-flavors.rst:198 +msgid "Inbound traffic:" +msgstr "" + +#: ../compute-flavors.rst:218 +msgid "" +"All the speed limit values in above example are specified in kilobytes/" +"second. And burst values are in kilobytes." +msgstr "" + +#: ../compute-flavors.rst:219 +msgid "Bandwidth I/O" +msgstr "" + +#: ../compute-flavors.rst:222 +msgid "" +"For the libvirt driver, you can enable and set the behavior of a virtual " +"hardware watchdog device for each flavor. Watchdog devices keep an eye on " +"the guest server, and carry out the configured action, if the server hangs. " +"The watchdog uses the i6300esb device (emulating a PCI Intel 6300ESB). If " +"``hw:watchdog_action`` is not specified, the watchdog is disabled." +msgstr "" + +#: ../compute-flavors.rst:229 +msgid "To set the behavior, use:" +msgstr "" + +#: ../compute-flavors.rst:235 +msgid "Valid ACTION values are:" +msgstr "" + +#: ../compute-flavors.rst:237 +msgid "``disabled``—(default) The device is not attached." +msgstr "" + +#: ../compute-flavors.rst:239 +msgid "``reset``—Forcefully reset the guest." +msgstr "" + +#: ../compute-flavors.rst:241 +msgid "``poweroff``—Forcefully power off the guest." +msgstr "" + +#: ../compute-flavors.rst:243 +msgid "``pause``—Pause the guest." +msgstr "" + +#: ../compute-flavors.rst:245 +msgid "``none``—Only enable the watchdog; do nothing if the server hangs." +msgstr "" + +#: ../compute-flavors.rst:250 +msgid "" +"Watchdog behavior set using a specific image's properties will override " +"behavior set using flavors." +msgstr "" + +#: ../compute-flavors.rst:251 +msgid "Watchdog behavior" +msgstr "" + +#: ../compute-flavors.rst:254 +msgid "" +"If a random-number generator device has been added to the instance through " +"its image properties, the device can be enabled and configured using:" +msgstr "" + +#: ../compute-flavors.rst:266 +msgid "" +"RATE-BYTES—(Integer) Allowed amount of bytes that the guest can read from " +"the host's entropy per period." +msgstr "" + +#: ../compute-flavors.rst:269 +msgid "RATE-PERIOD—(Integer) Duration of the read period in seconds." +msgstr "" + +#: ../compute-flavors.rst:269 +msgid "Random-number generator" +msgstr "" + +#: ../compute-flavors.rst:272 +msgid "" +"For the libvirt driver, you can define the topology of the processors in the " +"virtual machine using properties. The properties with ``max`` limit the " +"number that can be selected by the user with image properties." +msgstr "" + +#: ../compute-flavors.rst:287 +msgid "" +"FLAVOR-SOCKETS—(Integer) The number of sockets for the guest VM. By this is " +"set to the number of vCPUs requested." +msgstr "" + +#: ../compute-flavors.rst:290 +msgid "" +"FLAVOR-CORES—(Integer) The number of cores per socket for the guest VM. By " +"this is set to 1." +msgstr "" + +#: ../compute-flavors.rst:293 +msgid "" +"FLAVOR-THREADS—(Integer) The number of threads per core for the guest VM. By " +"this is set to 1." +msgstr "" + +#: ../compute-flavors.rst:294 +msgid "CPU toplogy" +msgstr "" + +#: ../compute-flavors.rst:297 +msgid "" +"Flavors can also be assigned to particular projects. By default, a flavor is " +"public and available to all projects. Private flavors are only accessible to " +"those on the access list and are invisible to other projects. To create and " +"assign a private flavor to a project, run these commands:" +msgstr "" + +#: ../compute-flavors.rst:305 +msgid "Project private flavors" +msgstr "" + +#: ../compute-images-instances.rst:3 +msgid "Images and instances" +msgstr "" + +#: ../compute-images-instances.rst:6 +msgid "" +"Disk images provide templates for virtual machine file systems. The Image " +"service controls storage and management of images." +msgstr "" + +#: ../compute-images-instances.rst:9 +msgid "" +"Instances are the individual virtual machines that run on physical compute " +"nodes. Users can launch any number of instances from the same image. Each " +"launched instance runs from a copy of the base image so that any changes " +"made to the instance do not affect the base image. You can take snapshots of " +"running instances to create an image based on the current disk state of a " +"particular instance. The Compute service manages instances." +msgstr "" + +#: ../compute-images-instances.rst:17 +msgid "" +"When you launch an instance, you must choose a ``flavor``, which represents " +"a set of virtual resources. Flavors define how many virtual CPUs an instance " +"has, the amount of RAM available to it, and the size of its ephemeral disks. " +"Users must select from the set of available flavors defined on their cloud. " +"OpenStack provides a number of predefined flavors that you can edit or add " +"to." +msgstr "" + +#: ../compute-images-instances.rst:26 +msgid "" +"For more information about creating and troubleshooting images, see the " +"`OpenStack Virtual Machine Image Guide `__." +msgstr "" + +#: ../compute-images-instances.rst:30 +msgid "" +"For more information about image configuration options, see the `Image " +"services `__ section of the OpenStack " +"Configuration Reference." +msgstr "" + +#: ../compute-images-instances.rst:35 +msgid "" +"For more information about flavors, see :ref:`compute-flavors` or `Flavors " +"`__ in the " +"OpenStack Operations Guide." +msgstr "" + +#: ../compute-images-instances.rst:39 +msgid "" +"You can add and remove additional resources from running instances, such as " +"persistent volume storage, or public IP addresses. The example used in this " +"chapter is of a typical virtual system within an OpenStack cloud. It uses " +"the ``cinder-volume`` service, which provides persistent block storage, " +"instead of the ephemeral storage provided by the selected instance flavor." +msgstr "" + +#: ../compute-images-instances.rst:46 +msgid "" +"This diagram shows the system state prior to launching an instance. The " +"image store, fronted by the Image service (glance) has a number of " +"predefined images. Inside the cloud, a compute node contains the available " +"vCPU, memory, and local disk resources. Additionally, the ``cinder-volume`` " +"service provides a number of predefined volumes." +msgstr "" + +#: ../compute-images-instances.rst:52 +msgid "|Base image state with no running instances|" +msgstr "" + +#: ../compute-images-instances.rst:54 +msgid "" +"To launch an instance select an image, flavor, and any optional attributes. " +"The selected flavor provides a root volume, labeled ``vda`` in this diagram, " +"and additional ephemeral storage, labeled ``vdb``. In this example, the " +"``cinder-volume`` store is mapped to the third virtual disk on this " +"instance, ``vdc``." +msgstr "" + +#: ../compute-images-instances.rst:60 +msgid "|Instance creation from image and runtime state|" +msgstr "" + +#: ../compute-images-instances.rst:62 +msgid "" +"The base image is copied from the image store to the local disk. The local " +"disk is the first disk that the instance accesses, labeled ``vda`` in this " +"diagram. Your instances will start up faster if you use smaller images, as " +"less data needs to be copied across the network." +msgstr "" + +#: ../compute-images-instances.rst:67 +msgid "" +"A new empty ephemeral disk is also created, labeled ``vdb`` in this diagram. " +"This disk is destroyed when you delete the instance." +msgstr "" + +#: ../compute-images-instances.rst:70 +msgid "" +"The compute node connects to the attached ``cinder-volume`` using ISCSI. The " +"``cinder-volume`` is mapped to the third disk, labeled ``vdc`` in this " +"diagram. After the compute node provisions the vCPU and memory resources, " +"the instance boots up from root volume ``vda``. The instance runs, and " +"changes data on the disks (highlighted in red on the diagram). If the volume " +"store is located on a separate network, the ``my_block_storage_ip`` option " +"specified in the storage node configuration file directs image traffic to " +"the compute node." +msgstr "" + +#: ../compute-images-instances.rst:81 +msgid "" +"Some details in this example scenario might be different in your " +"environment. For example, you might use a different type of back-end " +"storage, or different network protocols. One common variant is that the " +"ephemeral storage used for volumes ``vda`` and ``vdb`` could be backed by " +"network storage rather than a local disk." +msgstr "" + +#: ../compute-images-instances.rst:87 +msgid "" +"When the instance is deleted, the state is reclaimed with the exception of " +"the persistent volume. The ephemeral storage is purged; memory and vCPU " +"resources are released. The image remains unchanged throughout this process." +msgstr "" + +#: ../compute-images-instances.rst:92 +msgid "|End state of image and volume after instance exits|" +msgstr "" + +#: ../compute-images-instances.rst:96 +msgid "Image management" +msgstr "" + +#: ../compute-images-instances.rst:98 +msgid "" +"The OpenStack Image service discovers, registers, and retrieves virtual " +"machine images. The service also includes a RESTful API that allows you to " +"query VM image metadata and retrieve the actual image with HTTP requests. " +"For more information about the API, see the `OpenStack API Complete " +"Reference `__ and the `Python " +"API `__." +msgstr "" + +#: ../compute-images-instances.rst:106 +msgid "" +"The OpenStack Image service can be controlled using a command-line tool. For " +"more information about using the OpenStack Image command-line tool, see the " +"`Manage Images `__ section in the OpenStack End User Guide." +msgstr "" + +#: ../compute-images-instances.rst:112 +msgid "" +"Virtual images that have been made available through the Image service can " +"be stored in a variety of ways. In order to use these services, you must " +"have a working installation of the Image service, with a working endpoint, " +"and users that have been created in OpenStack Identity. Additionally, you " +"must meet the environment variables required by the Compute and Image " +"service clients." +msgstr "" + +#: ../compute-images-instances.rst:119 +msgid "The Image service supports these back-end stores:" +msgstr "" + +#: ../compute-images-instances.rst:122 +msgid "" +"The OpenStack Image service stores virtual machine images in the file system " +"back end by default. This simple back end writes image files to the local " +"file system." +msgstr "" + +#: ../compute-images-instances.rst:124 +msgid "File system" +msgstr "" + +# #-#-#-#-# compute-images-instances.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +# #-#-#-#-# objectstorage.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +#: ../compute-images-instances.rst:127 ../objectstorage.rst:3 +msgid "Object Storage" +msgstr "" + +#: ../compute-images-instances.rst:127 +msgid "The OpenStack highly available service for storing objects." +msgstr "" + +#: ../compute-images-instances.rst:130 +msgid "The OpenStack highly available service for storing blocks." +msgstr "" + +#: ../compute-images-instances.rst:133 +msgid "ESX/ESXi or vCenter Server target system." +msgstr "" + +#: ../compute-images-instances.rst:133 +msgid "VMware" +msgstr "" + +#: ../compute-images-instances.rst:136 +msgid "S3" +msgstr "" + +#: ../compute-images-instances.rst:136 +msgid "The Amazon S3 service." +msgstr "" + +#: ../compute-images-instances.rst:139 +msgid "" +"OpenStack Image service can read virtual machine images that are available " +"on the Internet using HTTP. This store is read only." +msgstr "" + +#: ../compute-images-instances.rst:140 +msgid "HTTP" +msgstr "" + +#: ../compute-images-instances.rst:143 +msgid "" +"Stores images inside of a Ceph storage cluster using Ceph's RBD interface." +msgstr "" + +#: ../compute-images-instances.rst:144 +msgid "RADOS block device (RBD)" +msgstr "" + +#: ../compute-images-instances.rst:147 +msgid "A distributed storage system for QEMU/KVM." +msgstr "" + +#: ../compute-images-instances.rst:147 +msgid "Sheepdog" +msgstr "" + +#: ../compute-images-instances.rst:150 +msgid "Stores images using MongoDB." +msgstr "" + +#: ../compute-images-instances.rst:151 +msgid "GridFS" +msgstr "" + +#: ../compute-images-instances.rst:154 +msgid "Image properties and property protection" +msgstr "" + +#: ../compute-images-instances.rst:155 +msgid "" +"An image property is a key and value pair that the cloud administrator or " +"the image owner attaches to an OpenStack Image service image, as follows:" +msgstr "" + +#: ../compute-images-instances.rst:159 +msgid "" +"The cloud administrator defines core properties, such as the image name." +msgstr "" + +#: ../compute-images-instances.rst:162 +msgid "" +"The cloud administrator and the image owner can define additional " +"properties, such as licensing and billing information." +msgstr "" + +#: ../compute-images-instances.rst:165 +msgid "" +"The cloud administrator can configure any property as protected, which " +"limits which policies or user roles can perform CRUD operations on that " +"property. Protected properties are generally additional properties to which " +"only cloud administrators have access." +msgstr "" + +#: ../compute-images-instances.rst:170 +msgid "" +"For unprotected image properties, the cloud administrator can manage core " +"properties and the image owner can manage additional properties." +msgstr "" + +#: ../compute-images-instances.rst:174 +msgid "**To configure property protection**" +msgstr "" + +#: ../compute-images-instances.rst:176 +msgid "" +"To configure property protection, the cloud administrator completes these " +"steps:" +msgstr "" + +#: ../compute-images-instances.rst:179 +msgid "Define roles or policies in the :file:`policy.json` file::" +msgstr "" + +#: ../compute-images-instances.rst:242 +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 +msgid "" +"Define which roles or policies can manage which properties in a property " +"protections configuration file. For example::" +msgstr "" + +#: ../compute-images-instances.rst:270 +msgid "A value of ``@`` allows the corresponding operation for a property." +msgstr "" + +#: ../compute-images-instances.rst:272 +msgid "A value of ``!`` disallows the corresponding operation for a property." +msgstr "" + +#: ../compute-images-instances.rst:275 +msgid "" +"In the :file:`glance-api.conf` file, define the location of a property " +"protections configuration file::" +msgstr "" + +#: ../compute-images-instances.rst:280 +msgid "" +"This file contains the rules for property protections and the roles and " +"policies associated with it." +msgstr "" + +#: ../compute-images-instances.rst:283 +msgid "By default, property protections are not enforced." +msgstr "" + +#: ../compute-images-instances.rst:285 +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 +msgid "" +"To view a sample configuration file, see `glance-api.conf `__." +msgstr "" + +#: ../compute-images-instances.rst:291 +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 +msgid "The default is ``roles``." +msgstr "" + +#: ../compute-images-instances.rst:302 +msgid "Image download: how it works" +msgstr "" + +#: ../compute-images-instances.rst:303 +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 " +"change depending on the settings chosen for the compute node and the Image " +"service." +msgstr "" + +#: ../compute-images-instances.rst:308 +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 " +"images are not stored in glance—rather in a back end, which could be Object " +"Storage, a filesystem or any other supported method—the connection is made " +"from the compute node to the Image service and the image is transferred over " +"this connection. The Image service streams the image from the back end to " +"the compute node." +msgstr "" + +#: ../compute-images-instances.rst:316 +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 " +"nodes. Configure the ``my_block_storage_ip`` option in the storage node " +"configuration to allow block storage traffic to reach the Compute node." +msgstr "" + +#: ../compute-images-instances.rst:322 +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 " +"from the back-end store. Currently the only store to support the direct " +"download approach is the filesystem store. It can be configured using the " +"``filesystems`` option in the ``image_file_url`` section of the :file:`nova." +"conf` file on compute nodes." +msgstr "" + +#: ../compute-images-instances.rst:329 +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 " +"on the configuration options for caching on compute nodes can be found in " +"the `Configuration Reference `__." +msgstr "" + +#: ../compute-images-instances.rst:336 +msgid "Instance building blocks" +msgstr "" + +#: ../compute-images-instances.rst:338 +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 " +"that starts from a known template state and loses all accumulated states on " +"shutdown." +msgstr "" + +#: ../compute-images-instances.rst:343 +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 " +"system that accumulates states that are preserved across restarts. To get a " +"list of available images on your system, run:" +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:258 +msgid "The displayed image attributes are:" +msgstr "" + +#: ../compute-images-instances.rst:367 +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:261 +msgid "``ID``" +msgstr "" + +#: ../compute-images-instances.rst:370 +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:264 +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:267 +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:268 +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:271 +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 " +"field is blank." +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:273 +msgid "``Server``" +msgstr "" + +#: ../compute-images-instances.rst:381 +msgid "" +"Virtual hardware templates are called ``flavors``. The default installation " +"provides five predefined flavors." +msgstr "" + +#: ../compute-images-instances.rst:384 +msgid "For a list of flavors that are available on your system, run:" +msgstr "" + +#: ../compute-images-instances.rst:399 +msgid "" +"By default, administrative users can configure the flavors. You can change " +"this behavior by redefining the access controls for ``compute_extension:" +"flavormanage`` in :file:`/etc/nova/policy.json` on the ``compute-api`` " +"server." +msgstr "" + +#: ../compute-images-instances.rst:406 +msgid "Instance management tools" +msgstr "" + +#: ../compute-images-instances.rst:408 +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 +msgid "" +"The OpenStack python-novaclient package provides a basic command-line " +"utility, which uses the :command:`nova` command. This is available as a " +"native package for most Linux distributions, or you can install the latest " +"version using the pip python package installer:" +msgstr "" + +#: ../compute-images-instances.rst:421 +msgid "" +"For more information about python-novaclient and other command-line tools, " +"see the `OpenStack End User Guide `__." +msgstr "" + +#: ../compute-images-instances.rst:427 +msgid "Control where instances run" +msgstr "" + +#: ../compute-images-instances.rst:428 +msgid "" +"The `OpenStack Configuration Reference `__ provides detailed information on controlling " +"where your instances run, including ensuring a set of instances run on " +"different compute nodes for service resiliency or on the same node for high " +"performance inter-instance communications." +msgstr "" + +#: ../compute-images-instances.rst:435 +msgid "" +"Administrative users can specify which compute node their instances run on. " +"To do this, specify the ``--availability-zone AVAILABILITY_ZONE:" +"COMPUTE_HOST`` parameter." +msgstr "" + +#: ../compute-live-migration-usage.rst:0 +msgid "**nova service-list**" +msgstr "" + +#: ../compute-live-migration-usage.rst:5 +msgid "Migrate instances" +msgstr "" + +#: ../compute-live-migration-usage.rst:7 +msgid "" +"This section discusses how to migrate running instances from one OpenStack " +"Compute server to another OpenStack Compute server." +msgstr "" + +#: ../compute-live-migration-usage.rst:10 +msgid "Before starting a migration, review the Configure migrations section." +msgstr "" + +#: ../compute-live-migration-usage.rst:22 +msgid "**Migrating instances**" +msgstr "" + +#: ../compute-live-migration-usage.rst:24 +msgid "Check the ID of the instance to be migrated:" +msgstr "" + +#: ../compute-live-migration-usage.rst:34 +msgid "ID" +msgstr "" + +# #-#-#-#-# compute-live-migration-usage.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +# #-#-#-#-# ts-eql-volume-size.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +#: ../compute-live-migration-usage.rst:36 +#: ../compute-live-migration-usage.rst:109 ../ts-eql-volume-size.rst:110 +msgid "Status" +msgstr "" + +#: ../compute-live-migration-usage.rst:37 +msgid "Networks" +msgstr "" + +#: ../compute-live-migration-usage.rst:38 +#: ../compute-live-migration-usage.rst:88 +msgid "d1df1b5a-70c4-4fed-98b7-423362f2c47c" +msgstr "" + +#: ../compute-live-migration-usage.rst:39 +#: ../compute-live-migration-usage.rst:90 +msgid "vm1" msgstr "" #: ../compute-live-migration-usage.rst:40 @@ -2166,20 +4701,653 @@ msgstr "" msgid "ACTIVE" msgstr "" -#: ../blockstorage_get_capabilities.rst:79 -msgid "API request::" +#: ../compute-live-migration-usage.rst:41 +msgid "private=a.b.c.d" msgstr "" -#: ../compute-remote-console-access.rst:105 -msgid "About nova-consoleauth" +#: ../compute-live-migration-usage.rst:42 +msgid "d693db9e-a7cf-45ef-a7c9-b3ecb5f22645" msgstr "" -#: ../index.rst:6 -msgid "Abstract" +#: ../compute-live-migration-usage.rst:43 +msgid "vm2" msgstr "" -#: ../objectstorage_arch.rst:6 -msgid "Access tier" +#: ../compute-live-migration-usage.rst:45 +msgid "private=e.f.g.h" +msgstr "" + +#: ../compute-live-migration-usage.rst:47 +msgid "" +"Check the information associated with the instance. In this example, ``vm1`` " +"is running on ``HostB``:" +msgstr "" + +#: ../compute-live-migration-usage.rst:58 +msgid "Property" +msgstr "" + +# #-#-#-#-# compute-live-migration-usage.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +# #-#-#-#-# networking_adv-config.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +#: ../compute-live-migration-usage.rst:59 ../networking_adv-config.rst:26 +msgid "Value" +msgstr "" + +#: ../compute-live-migration-usage.rst:60 +#: ../compute-live-migration-usage.rst:64 +#: ../compute-live-migration-usage.rst:77 +#: ../compute-live-migration-usage.rst:80 +#: ../compute-live-migration-usage.rst:84 +#: ../compute-live-migration-usage.rst:96 +msgid "..." +msgstr "" + +#: ../compute-live-migration-usage.rst:62 +msgid "OS-EXT-SRV-ATTR:host" +msgstr "" + +#: ../compute-live-migration-usage.rst:66 +msgid "flavor" +msgstr "" + +# #-#-#-#-# compute-live-migration-usage.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +# #-#-#-#-# database.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +# #-#-#-#-# telemetry-data-collection.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +#: ../compute-live-migration-usage.rst:71 ../database.rst:112 +#: ../telemetry-data-collection.rst:686 +msgid "name" +msgstr "" + +#: ../compute-live-migration-usage.rst:73 +msgid "private network" +msgstr "" + +# #-#-#-#-# compute-live-migration-usage.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +# #-#-#-#-# networking_multi-dhcp-agents.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +#: ../compute-live-migration-usage.rst:82 +#: ../compute-live-migration-usage.rst:135 +#: ../networking_multi-dhcp-agents.rst:48 +msgid "HostB" +msgstr "" + +#: ../compute-live-migration-usage.rst:86 +msgid "m1.tiny" +msgstr "" + +#: ../compute-live-migration-usage.rst:92 +msgid "a.b.c.d" +msgstr "" + +#: ../compute-live-migration-usage.rst:98 +msgid "" +"Select the compute node the instance will be migrated to. In this example, " +"we will migrate the instance to ``HostC``, because nova-compute is running " +"on it:" +msgstr "" + +#: ../compute-live-migration-usage.rst:106 +msgid "Binary" +msgstr "" + +# #-#-#-#-# compute-live-migration-usage.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +# #-#-#-#-# networking_multi-dhcp-agents.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +#: ../compute-live-migration-usage.rst:107 +#: ../networking_multi-dhcp-agents.rst:39 +msgid "Host" +msgstr "" + +#: ../compute-live-migration-usage.rst:108 +msgid "Zone" +msgstr "" + +#: ../compute-live-migration-usage.rst:110 +msgid "State" +msgstr "" + +#: ../compute-live-migration-usage.rst:111 +msgid "Updated_at" +msgstr "" + +#: ../compute-live-migration-usage.rst:112 +msgid "Disabled Reason" +msgstr "" + +#: ../compute-live-migration-usage.rst:113 +msgid "nova-consoleauth" +msgstr "" + +# #-#-#-#-# compute-live-migration-usage.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +# #-#-#-#-# networking_multi-dhcp-agents.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +#: ../compute-live-migration-usage.rst:114 +#: ../compute-live-migration-usage.rst:121 +#: ../compute-live-migration-usage.rst:128 +#: ../compute-live-migration-usage.rst:149 +#: ../networking_multi-dhcp-agents.rst:46 +msgid "HostA" +msgstr "" + +#: ../compute-live-migration-usage.rst:115 +#: ../compute-live-migration-usage.rst:122 +#: ../compute-live-migration-usage.rst:129 +#: ../compute-live-migration-usage.rst:150 +msgid "internal" +msgstr "" + +# #-#-#-#-# compute-live-migration-usage.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +# #-#-#-#-# telemetry-alarms.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +#: ../compute-live-migration-usage.rst:116 +#: ../compute-live-migration-usage.rst:123 +#: ../compute-live-migration-usage.rst:130 +#: ../compute-live-migration-usage.rst:137 +#: ../compute-live-migration-usage.rst:144 +#: ../compute-live-migration-usage.rst:151 ../telemetry-alarms.rst:189 +msgid "enabled" +msgstr "" + +#: ../compute-live-migration-usage.rst:117 +#: ../compute-live-migration-usage.rst:124 +#: ../compute-live-migration-usage.rst:131 +#: ../compute-live-migration-usage.rst:138 +#: ../compute-live-migration-usage.rst:145 +#: ../compute-live-migration-usage.rst:152 +msgid "up" +msgstr "" + +#: ../compute-live-migration-usage.rst:118 +#: ../compute-live-migration-usage.rst:125 +msgid "2014-03-25T10:33:25.000000" +msgstr "" + +#: ../compute-live-migration-usage.rst:120 +msgid "nova-scheduler" +msgstr "" + +#: ../compute-live-migration-usage.rst:127 +msgid "nova-conductor" +msgstr "" + +#: ../compute-live-migration-usage.rst:132 +msgid "2014-03-25T10:33:27.000000" +msgstr "" + +#: ../compute-live-migration-usage.rst:134 +#: ../compute-live-migration-usage.rst:141 +msgid "nova-compute" +msgstr "" + +#: ../compute-live-migration-usage.rst:136 +#: ../compute-live-migration-usage.rst:143 +msgid "nova" +msgstr "" + +#: ../compute-live-migration-usage.rst:139 +#: ../compute-live-migration-usage.rst:146 +#: ../compute-live-migration-usage.rst:153 +msgid "2014-03-25T10:33:31.000000" +msgstr "" + +#: ../compute-live-migration-usage.rst:142 +#: ../compute-live-migration-usage.rst:171 +#: ../compute-live-migration-usage.rst:172 +#: ../compute-live-migration-usage.rst:173 +#: ../compute-live-migration-usage.rst:174 +#: ../compute-live-migration-usage.rst:175 +msgid "HostC" +msgstr "" + +#: ../compute-live-migration-usage.rst:148 +msgid "nova-cert" +msgstr "" + +#: ../compute-live-migration-usage.rst:156 +msgid "Check that ``HostC`` has enough resources for migration:" +msgstr "" + +#: ../compute-live-migration-usage.rst:166 +msgid "HOST" +msgstr "" + +#: ../compute-live-migration-usage.rst:167 +msgid "PROJECT" +msgstr "" + +# #-#-#-#-# compute-live-migration-usage.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +# #-#-#-#-# telemetry-measurements.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +#: ../compute-live-migration-usage.rst:168 ../telemetry-measurements.rst:119 +msgid "cpu" +msgstr "" + +#: ../compute-live-migration-usage.rst:169 +msgid "memory_mb" +msgstr "" + +#: ../compute-live-migration-usage.rst:170 +msgid "disk_bg" +msgstr "" + +#: ../compute-live-migration-usage.rst:176 +msgid "(total)" +msgstr "" + +#: ../compute-live-migration-usage.rst:177 +msgid "(used_now)" +msgstr "" + +#: ../compute-live-migration-usage.rst:178 +msgid "(used_max)" +msgstr "" + +#: ../compute-live-migration-usage.rst:179 +msgid "p1" +msgstr "" + +#: ../compute-live-migration-usage.rst:180 +msgid "p2" +msgstr "" + +#: ../compute-live-migration-usage.rst:181 +msgid "32232" +msgstr "" + +#: ../compute-live-migration-usage.rst:182 +#: ../compute-live-migration-usage.rst:183 +#: ../compute-live-migration-usage.rst:184 +#: ../compute-live-migration-usage.rst:185 +msgid "21284" +msgstr "" + +#: ../compute-live-migration-usage.rst:186 +msgid "878" +msgstr "" + +#: ../compute-live-migration-usage.rst:187 +msgid "442" +msgstr "" + +#: ../compute-live-migration-usage.rst:188 +#: ../compute-live-migration-usage.rst:189 +#: ../compute-live-migration-usage.rst:190 +msgid "422" +msgstr "" + +#: ../compute-live-migration-usage.rst:192 +msgid "``cpu``: Number of CPUs" +msgstr "" + +#: ../compute-live-migration-usage.rst:194 +msgid "``memory_mb``: Total amount of memory, in MB" +msgstr "" + +#: ../compute-live-migration-usage.rst:196 +msgid "``disk_gb``: Total amount of space for NOVA-INST-DIR/instances, in GB" +msgstr "" + +#: ../compute-live-migration-usage.rst:198 +msgid "" +"In this table, the first row shows the total amount of resources available " +"on the physical server. The second line shows the currently used resources. " +"The third line shows the maximum used resources. The fourth line and below " +"shows the resources available for each project." +msgstr "" + +#: ../compute-live-migration-usage.rst:203 +msgid "Migrate the instance using the :command:`nova live-migration` command:" +msgstr "" + +#: ../compute-live-migration-usage.rst:209 +msgid "" +"In this example, SERVER can be the ID or name of the instance. Another " +"example:" +msgstr "" + +#: ../compute-live-migration-usage.rst:219 +msgid "" +"When using live migration to move workloads between Icehouse and Juno " +"compute nodes, it may cause data loss because libvirt live migration with " +"shared block storage was buggy (potential loss of data) before version 3.32. " +"This issue can be solved when we upgrade to RPC API version 4.0." +msgstr "" + +#: ../compute-live-migration-usage.rst:225 +msgid "" +"Check that the instance has been migrated successfully, using :command:`nova " +"list`. If the instance is still running on ``HostB``, check the log files " +"at :file:`src/dest` for nova-compute and nova-scheduler to determine why." +msgstr "" + +# #-#-#-#-# compute-manage-logs.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +# #-#-#-#-# identity_logging.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +#: ../compute-manage-logs.rst:5 ../identity_logging.rst:3 +msgid "Logging" +msgstr "" + +#: ../compute-manage-logs.rst:8 +msgid "Logging module" +msgstr "" + +#: ../compute-manage-logs.rst:10 +msgid "" +"Logging behavior can be changed by creating a configuration file. To specify " +"the configuration file, add this line to the :file:`/etc/nova/nova.conf` " +"file:" +msgstr "" + +#: ../compute-manage-logs.rst:18 +msgid "" +"To change the logging level, add ``DEBUG``, ``INFO``, ``WARNING``, or " +"``ERROR`` as a parameter." +msgstr "" + +#: ../compute-manage-logs.rst:21 +msgid "" +"The logging configuration file is an INI-style configuration file, which " +"must contain a section called ``logger_nova``. This controls the behavior of " +"the logging facility in the ``nova-*`` services. For example:" +msgstr "" + +#: ../compute-manage-logs.rst:33 +msgid "" +"This example sets the debugging level to ``INFO`` (which is less verbose " +"than the default ``DEBUG`` setting)." +msgstr "" + +#: ../compute-manage-logs.rst:36 +msgid "" +"For more about the logging configuration syntax, including the ``handlers`` " +"and ``quaname`` variables, see the `Python documentation `__ on " +"logging configuration files." +msgstr "" + +#: ../compute-manage-logs.rst:41 +msgid "" +"For an example :file:`logging.conf` file with various defined handlers, see " +"the `OpenStack Configuration Reference `__." +msgstr "" + +#: ../compute-manage-logs.rst:45 +msgid "Syslog" +msgstr "" + +#: ../compute-manage-logs.rst:47 +msgid "" +"OpenStack Compute services can send logging information to syslog. This is " +"useful if you want to use rsyslog to forward logs to a remote machine. " +"Separately configure the Compute service (nova), the Identity service " +"(keystone), the Image service (glance), and, if you are using it, the Block " +"Storage service (cinder) to send log messages to syslog. Open these " +"configuration files:" +msgstr "" + +#: ../compute-manage-logs.rst:54 +msgid ":file:`/etc/nova/nova.conf`" +msgstr "" + +#: ../compute-manage-logs.rst:56 +msgid ":file:`/etc/keystone/keystone.conf`" +msgstr "" + +#: ../compute-manage-logs.rst:58 +msgid ":file:`/etc/glance/glance-api.conf`" +msgstr "" + +#: ../compute-manage-logs.rst:60 +msgid ":file:`/etc/glance/glance-registry.conf`" +msgstr "" + +#: ../compute-manage-logs.rst:62 +msgid ":file:`/etc/cinder/cinder.conf`" +msgstr "" + +#: ../compute-manage-logs.rst:64 +msgid "In each configuration file, add these lines:" +msgstr "" + +#: ../compute-manage-logs.rst:73 +msgid "" +"In addition to enabling syslog, these settings also turn off verbose and " +"debugging output from the log." +msgstr "" + +#: ../compute-manage-logs.rst:78 +msgid "" +"Although this example uses the same local facility for each service " +"(``LOG_LOCAL0``, which corresponds to syslog facility ``LOCAL0``), we " +"recommend that you configure a separate local facility for each service, as " +"this provides better isolation and more flexibility. For example, you can " +"capture logging information at different severity levels for different " +"services. syslog allows you to define up to eight local facilities, " +"``LOCAL0, LOCAL1, ..., LOCAL7``. For more information, see the syslog " +"documentation." +msgstr "" + +#: ../compute-manage-logs.rst:88 +msgid "Rsyslog" +msgstr "" + +#: ../compute-manage-logs.rst:90 +msgid "" +"rsyslog is useful for setting up a centralized log server across multiple " +"machines. This section briefly describe the configuration to set up an " +"rsyslog server. A full treatment of rsyslog is beyond the scope of this " +"book. This section assumes rsyslog has already been installed on your hosts " +"(it is installed by default on most Linux distributions)." +msgstr "" + +#: ../compute-manage-logs.rst:97 +msgid "" +"This example provides a minimal configuration for :file:`/etc/rsyslog.conf` " +"on the log server host, which receives the log files" +msgstr "" + +#: ../compute-manage-logs.rst:106 +msgid "" +"Add a filter rule to :file:`/etc/rsyslog.conf` which looks for a host name. " +"This example uses COMPUTE_01 as the compute host name:" +msgstr "" + +#: ../compute-manage-logs.rst:113 +msgid "" +"On each compute host, create a file named :file:`/etc/rsyslog.d/60-nova." +"conf`, with the following content:" +msgstr "" + +#: ../compute-manage-logs.rst:123 +msgid "" +"Once you have created the file, restart the rsyslog service. Error-level log " +"messages on the compute hosts should now be sent to the log server." +msgstr "" + +#: ../compute-manage-logs.rst:127 +msgid "Serial console" +msgstr "" + +#: ../compute-manage-logs.rst:129 +msgid "" +"The serial console provides a way to examine kernel output and other system " +"messages during troubleshooting if the instance lacks network connectivity." +msgstr "" + +#: ../compute-manage-logs.rst:133 +msgid "" +"OpenStack Icehouse and earlier supports read-only access using the serial " +"console using the ``os-GetSerialOutput`` server action. Most cloud images " +"enable this feature by default. For more information, see :ref:`compute-" +"common-errors-and-fixes`." +msgstr "" + +#: ../compute-manage-logs.rst:138 +msgid "" +"OpenStack Juno and later supports read-write access using the serial console " +"using the ``os-GetSerialConsole`` server action. This feature also requires " +"a websocket client to access the serial console." +msgstr "" + +#: ../compute-manage-logs.rst:142 +msgid "**Configuring read-write serial console access**" +msgstr "" + +#: ../compute-manage-logs.rst:144 +msgid "On a compute node, edit the :file:`/etc/nova/nova.conf` file:" +msgstr "" + +#: ../compute-manage-logs.rst:146 +msgid "In the ``[serial_console]`` section, enable the serial console:" +msgstr "" + +#: ../compute-manage-logs.rst:154 +msgid "" +"In the ``[serial_console]`` section, configure the serial console proxy " +"similar to graphical console proxies:" +msgstr "" + +#: ../compute-manage-logs.rst:165 +msgid "" +"The ``base_url`` option specifies the base URL that clients receive from the " +"API upon requesting a serial console. Typically, this refers to the host " +"name of the controller node." +msgstr "" + +#: ../compute-manage-logs.rst:169 +msgid "" +"The ``listen`` option specifies the network interface nova-compute should " +"listen on for virtual console connections. Typically, 0.0.0.0 will enable " +"listening on all interfaces." +msgstr "" + +#: ../compute-manage-logs.rst:173 +msgid "" +"The ``proxyclient_address`` option specifies which network interface the " +"proxy should connect to. Typically, this refers to the IP address of the " +"management interface." +msgstr "" + +#: ../compute-manage-logs.rst:177 +msgid "" +"When you enable read-write serial console access, Compute will add serial " +"console information to the Libvirt XML file for the instance. For example:" +msgstr "" + +#: ../compute-manage-logs.rst:190 +msgid "**Accessing the serial console on an instance**" +msgstr "" + +#: ../compute-manage-logs.rst:192 +msgid "" +"Use the :command:`nova get-serial-proxy` command to retrieve the websocket " +"URL for the serial console on the instance:" +msgstr "" + +#: ../compute-manage-logs.rst:204 +msgid "Url" +msgstr "" + +#: ../compute-manage-logs.rst:205 +msgid "serial" +msgstr "" + +#: ../compute-manage-logs.rst:206 +msgid "ws://127.0.0.1:6083/?token=18510769-71ad-4e5a-8348-4218b5613b3d" +msgstr "" + +#: ../compute-manage-logs.rst:208 +msgid "Alternatively, use the API directly:" +msgstr "" + +#: ../compute-manage-logs.rst:221 +msgid "" +"Use Python websocket with the URL to generate ``.send``, ``.recv``, and ``." +"fileno`` methods for serial console access. For example:" +msgstr "" + +#: ../compute-manage-logs.rst:231 +msgid "" +"Alternatively, use a `Python websocket client `__." +msgstr "" + +#: ../compute-manage-logs.rst:235 +msgid "" +"When you enable the serial console, typical instance logging using the :" +"command:`nova console-log` command is disabled. Kernel output and other " +"system messages will not be visible unless you are actively viewing the " +"serial console." +msgstr "" + +#: ../compute-manage-the-cloud.rst:5 +msgid "Manage the cloud" +msgstr "" + +#: ../compute-manage-the-cloud.rst:12 +msgid "" +"System administrators can use :command:`nova` client and :command:" +"`euca2ools` commands to manage their clouds." +msgstr "" + +#: ../compute-manage-the-cloud.rst:15 +msgid "" +"``nova`` client and ``euca2ools`` can be used by all users, though specific " +"commands might be restricted by Role Based Access Control in the Identity " +"Service." +msgstr "" + +#: ../compute-manage-the-cloud.rst:19 +msgid "**Managing the cloud with nova client**" +msgstr "" + +#: ../compute-manage-the-cloud.rst:21 +msgid "" +"The python-novaclient package provides a ``nova`` shell that enables Compute " +"API interactions from the command line. Install the client, and provide your " +"user name and password (which can be set as environment variables for " +"convenience), for the ability to administer the cloud from the command line." +msgstr "" + +#: ../compute-manage-the-cloud.rst:27 +msgid "" +"To install python-novaclient, download the tarball from `http://pypi.python." +"org/pypi/python-novaclient/#downloads `__ and then install it in your favorite Python " +"environment:" +msgstr "" + +#: ../compute-manage-the-cloud.rst:37 +msgid "As root, run:" +msgstr "" + +#: ../compute-manage-the-cloud.rst:43 +msgid "Confirm the installation was successful:" +msgstr "" + +#: ../compute-manage-the-cloud.rst:62 +msgid "" +"Running :command:`nova help` returns a list of ``nova`` commands and " +"parameters. To get help for a subcommand, run:" +msgstr "" + +#: ../compute-manage-the-cloud.rst:69 +msgid "" +"For a complete list of ``nova`` commands and parameters, see the `OpenStack " +"Command-Line Reference `__." +msgstr "" + +#: ../compute-manage-the-cloud.rst:72 +msgid "" +"Set the required parameters as environment variables to make running " +"commands easier. For example, you can add :option:`--os-username` as a " +"``nova`` option, or set it as an environment variable. To set the user name, " +"password, and tenant as environment variables, use:" +msgstr "" + +#: ../compute-manage-the-cloud.rst:83 +msgid "" +"The Identity service will give you an authentication endpoint, which Compute " +"recognizes as ``OS_AUTH_URL``:" +msgstr "" + +#: ../compute-manage-users.rst:5 +msgid "Manage Compute users" msgstr "" #: ../compute-manage-users.rst:7 @@ -2191,343 +5359,313 @@ msgid "" "user." msgstr "" -#: ../objectstorage_features.rst:36 +#: ../compute-manage-users.rst:13 msgid "" -"Account management: Create, add, verify, and delete users; Container " -"management: Upload, download, and verify; Monitoring: Capacity, host, " -"network, log trawling, and cluster health." +"To begin using Compute, you must create a user with the Identity service." msgstr "" -#: ../objectstorage_account_reaper.rst:3 -msgid "Account reaper" +#: ../compute-manage-volumes.rst:0 +msgid "**nova volume commands**" msgstr "" -#: ../objectstorage_features.rst:22 -msgid "Account/container/object structure" -msgstr "" - -#: ../objectstorage_components.rst:151 -msgid "Accounts and containers" -msgstr "" - -#: ../telemetry-data-collection.rst:611 -msgid "Accumulator" -msgstr "" - -#: ../networking_use.rst:183 -msgid "Action" -msgstr "" - -#: ../telemetry-measurements.rst:1083 -msgid "Active connecti\\ ons on a LB" -msgstr "" - -#: ../telemetry-measurements.rst:1024 -msgid "Active entries in table" -msgstr "" - -#: ../compute-manage-logs.rst:106 +#: ../compute-manage-volumes.rst:5 msgid "" -"Add a filter rule to :file:`/etc/rsyslog.conf` which looks for a host name. " -"This example uses COMPUTE_01 as the compute host name:" +"Depending on the setup of your cloud provider, they may give you an endpoint " +"to use to manage volumes, or there may be an extension under the covers. In " +"either case, you can use the ``nova`` CLI to manage volumes." msgstr "" -#: ../compute-networking-nova.rst:276 -msgid "" -"Add a fixed range for IPv6 addresses to the :command:`nova network-create` " -"command. Specify ``public`` or ``private`` after the ``network-create`` " -"parameter." +# #-#-#-#-# compute-manage-volumes.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +# #-#-#-#-# networking_adv-features.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +# #-#-#-#-# networking_config-agents.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +# #-#-#-#-# networking_use.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +#: ../compute-manage-volumes.rst:13 ../networking_adv-features.rst:207 +#: ../networking_adv-features.rst:357 ../networking_adv-features.rst:492 +#: ../networking_adv-features.rst:784 ../networking_config-agents.rst:492 +#: ../networking_use.rst:47 ../networking_use.rst:123 +#: ../networking_use.rst:183 ../networking_use.rst:241 +msgid "Command" msgstr "" -#: ../compute-manage-volumes.rst:28 -msgid "Add a new snapshot." +#: ../compute-manage-volumes.rst:15 +msgid "volume-attach" +msgstr "" + +#: ../compute-manage-volumes.rst:16 +msgid "Attach a volume to a server." +msgstr "" + +#: ../compute-manage-volumes.rst:17 +msgid "volume-create" msgstr "" #: ../compute-manage-volumes.rst:18 msgid "Add a new volume." msgstr "" -#: ../identity_concepts.rst:347 -msgid "Add a user to a group" +#: ../compute-manage-volumes.rst:19 +msgid "volume-delete" msgstr "" -#: ../compute-configuring-migrations.rst:354 +#: ../compute-manage-volumes.rst:20 +msgid "Remove a volume." +msgstr "" + +#: ../compute-manage-volumes.rst:21 +msgid "volume-detach" +msgstr "" + +#: ../compute-manage-volumes.rst:22 +msgid "Detach a volume from a server." +msgstr "" + +#: ../compute-manage-volumes.rst:23 +msgid "volume-list" +msgstr "" + +#: ../compute-manage-volumes.rst:24 +msgid "List all the volumes." +msgstr "" + +#: ../compute-manage-volumes.rst:25 +msgid "volume-show" +msgstr "" + +#: ../compute-manage-volumes.rst:26 +msgid "Show details about a volume." +msgstr "" + +#: ../compute-manage-volumes.rst:27 +msgid "volume-snapshot-create" +msgstr "" + +#: ../compute-manage-volumes.rst:28 +msgid "Add a new snapshot." +msgstr "" + +#: ../compute-manage-volumes.rst:29 +msgid "volume-snapshot-delete" +msgstr "" + +#: ../compute-manage-volumes.rst:30 +msgid "Remove a snapshot." +msgstr "" + +#: ../compute-manage-volumes.rst:31 +msgid "volume-snapshot-list" +msgstr "" + +#: ../compute-manage-volumes.rst:32 +msgid "List all the snapshots." +msgstr "" + +#: ../compute-manage-volumes.rst:33 +msgid "volume-snapshot-show" +msgstr "" + +#: ../compute-manage-volumes.rst:34 +msgid "Show details about a snapshot." +msgstr "" + +#: ../compute-manage-volumes.rst:35 +msgid "volume-type-create" +msgstr "" + +#: ../compute-manage-volumes.rst:36 +msgid "Create a new volume type." +msgstr "" + +#: ../compute-manage-volumes.rst:37 +msgid "volume-type-delete" +msgstr "" + +#: ../compute-manage-volumes.rst:38 +msgid "Delete a specific flavor" +msgstr "" + +#: ../compute-manage-volumes.rst:39 +msgid "volume-type-list" +msgstr "" + +#: ../compute-manage-volumes.rst:40 +msgid "Print a list of available 'volume types'." +msgstr "" + +#: ../compute-manage-volumes.rst:41 +msgid "volume-update" +msgstr "" + +#: ../compute-manage-volumes.rst:42 +msgid "Update an attached volume." +msgstr "" + +#: ../compute-manage-volumes.rst:46 +msgid "For example, to list IDs and names of Compute volumes, run:" +msgstr "" + +#: ../compute-networking-nova.rst:0 +msgid "Description of IPv6 configuration options" +msgstr "" + +#: ../compute-networking-nova.rst:0 +msgid "Description of metadata configuration options" +msgstr "" + +#: ../compute-networking-nova.rst:3 +msgid "Networking with nova-network" +msgstr "" + +#: ../compute-networking-nova.rst:5 msgid "" -"Add an NFS VHD storage to your master XenServer, and set it as the default " -"storage repository. For more information, see NFS VHD in the XenServer " -"Administrator's Guide." +"Understanding the networking configuration options helps you design the best " +"configuration for your Compute instances." msgstr "" -#: ../blockstorage_glusterfs_backend.rst:89 +#: ../compute-networking-nova.rst:8 msgid "" -"Add an entry to :file:`/etc/cinder/glusterfs` for each GlusterFS share that " -"OpenStack Block Storage should use for back end storage. Each entry should " -"be a separate line, and should use the following format::" +"You can choose to either install and configure nova-network or use the " +"OpenStack Networking service (neutron). This section contains a brief " +"overview of nova-network. For more information about OpenStack Networking, " +"see :ref:`networking`." msgstr "" -#: ../blockstorage_nfs_backend.rst:34 +#: ../compute-networking-nova.rst:14 +msgid "Networking concepts" +msgstr "" + +#: ../compute-networking-nova.rst:16 msgid "" -"Add an entry to :file:`/etc/cinder/nfsshares` for each NFS share that the " -"``cinder`` volume service should use for back end storage. Each entry should " -"be a separate line, and should use the following format:" +"Compute assigns a private IP address to each VM instance. Compute makes a " +"distinction between fixed IPs and floating IP. Fixed IPs are IP addresses " +"that are assigned to an instance on creation and stay the same until the " +"instance is explicitly terminated. Floating IPs are addresses that can be " +"dynamically associated with an instance. A floating IP address can be " +"disassociated and associated with another instance at any time. A user can " +"reserve a floating IP for their project." msgstr "" -#: ../compute-networking-nova.rst:695 -msgid "Add entries to the list:" -msgstr "" - -#: ../compute-configuring-migrations.rst:389 -msgid "Add hosts to the pool" -msgstr "" - -#: ../compute-configuring-migrations.rst:373 -msgid "Add metadata to the aggregate, to mark it as a hypervisor pool" -msgstr "" - -#: ../networking_config-identity.rst:12 -msgid "Add the following function to your :file:`.bashrc` file:" -msgstr "" - -#: ../objectstorage_ringbuilder.rst:133 +#: ../compute-networking-nova.rst:26 msgid "" -"Additionally, the ``swift-ring-builder X.builder create`` command can now " -"take a decimal argument for the number of replicas." +"Currently, Compute with ``nova-network`` only supports Linux bridge " +"networking that allows virtual interfaces to connect to the outside network " +"through the physical interface." msgstr "" -#: ../ts-eql-volume-size.rst:6 +#: ../compute-networking-nova.rst:30 msgid "" -"Addressing discrepancies in reported volume sizes for EqualLogic storage" +"The network controller with ``nova-network`` provides virtual networks to " +"enable compute servers to interact with each other and with the public " +"network. Compute with ``nova-network`` supports the following network modes, " +"which are implemented as Network Manager types:" msgstr "" -#: ../compute-flavors.rst:7 +#: ../compute-networking-nova.rst:36 msgid "" -"Admin users can use the :command:`nova flavor-` commands to customize and " -"manage flavors. To see the available flavor-related commands, run:" +"In this mode, a network administrator specifies a subnet. IP addresses for " +"VM instances are assigned from the subnet, and then injected into the image " +"on launch. Each instance receives a fixed IP address from the pool of " +"available addresses. A system administrator must create the Linux networking " +"bridge (typically named ``br100``, although this is configurable) on the " +"systems running the ``nova-network`` service. All instances of the system " +"are attached to the same bridge, which is configured manually by the network " +"administrator." msgstr "" -#: ../networking_use.rst:91 -msgid "Administrative operations" +#: ../compute-networking-nova.rst:44 +msgid "Flat Network Manager" msgstr "" -#: ../compute-images-instances.rst:435 +#: ../compute-networking-nova.rst:48 msgid "" -"Administrative users can specify which compute node their instances run on. " -"To do this, specify the ``--availability-zone AVAILABILITY_ZONE:" -"COMPUTE_HOST`` parameter." +"Configuration injection currently only works on Linux-style systems that " +"keep networking configuration in :file:`/etc/network/interfaces`." msgstr "" -#: ../compute-networking-nova.rst:774 -msgid "Administrative/Public access to your instances" -msgstr "" - -#: ../compute-security.rst:14 +#: ../compute-networking-nova.rst:53 msgid "" -"Administrators can designate a group of compute hosts as trusted using " -"trusted compute pools. The trusted hosts use hardware-based security " -"features, such as the Intel Trusted Execution Technology (TXT), to provide " -"an additional level of security. Combined with an external stand-alone, web-" -"based remote attestation server, cloud providers can ensure that the compute " -"node runs only software with verified measurements and can ensure a secure " -"cloud stack." +"In this mode, OpenStack starts a DHCP server (dnsmasq) to allocate IP " +"addresses to VM instances from the specified subnet, in addition to manually " +"configuring the networking bridge. IP addresses for VM instances are " +"assigned from a subnet specified by the network administrator." msgstr "" -#: ../compute-networking-nova.rst:216 +#: ../compute-networking-nova.rst:59 msgid "" -"Administrators can specify the starting point IP address to reserve with the " -"DHCP server (in the format n.n.n.n) with this command:" +"Like flat mode, all instances are attached to a single bridge on the compute " +"node. Additionally, a DHCP server configures instances depending on single-/" +"multi-host mode, alongside each ``nova-network``. In this mode, Compute does " +"a bit more configuration. It attempts to bridge into an Ethernet device " +"(``flat_interface``, eth0 by default). For every instance, Compute allocates " +"a fixed IP address and configures dnsmasq with the MAC ID and IP address for " +"the VM. dnsmasq does not take part in the IP address allocation process, it " +"only hands out IPs according to the mapping done by Compute. Instances " +"receive their fixed IPs with the :command:`dhcpdiscover` command. These IPs " +"are not assigned to any of the host's network interfaces, only to the guest-" +"side interface for the VM." msgstr "" -#: ../networking_use.rst:117 -msgid "Advanced Networking operations" -msgstr "" - -#: ../networking_use.rst:235 -msgid "Advanced VM creation operations" -msgstr "" - -#: ../networking_adv-config.rst:3 -msgid "Advanced configuration options" -msgstr "" - -#: ../networking_adv-features.rst:3 -msgid "Advanced features through API extensions" -msgstr "" - -#: ../networking_adv-operational-features.rst:3 -msgid "Advanced operational features" -msgstr "" - -#: ../networking_config-agents.rst:118 +#: ../compute-networking-nova.rst:72 msgid "" -"After a certain, configured timeframe, networks uncouple from DHCP agents " -"when the agents are no longer in use. You can configure the DHCP agent to " -"automatically detach from a network when the agent is out of service, or no " -"longer needed." +"In any setup with flat networking, the hosts providing the ``nova-network`` " +"service are responsible for forwarding traffic from the private network. " +"They also run and configure dnsmasq as a DHCP server listening on this " +"bridge, usually on IP address 10.0.0.1 (see :ref:`compute-dnsmasq`). Compute " +"can determine the NAT entries for each network, although sometimes NAT is " +"not used, such as when the network has been configured with all public IPs, " +"or if a hardware router is used (which is a high availability option). In " +"this case, hosts need to have ``br100`` configured and physically connected " +"to any other nodes that are hosting VMs. You must set the " +"``flat_network_bridge`` option or create networks with the bridge parameter " +"in order to avoid raising an error. Compute nodes have iptables or ebtables " +"entries created for each project and instance to protect against MAC ID or " +"IP address spoofing and ARP poisoning." msgstr "" -#: ../dashboard_sessions.rst:135 +#: ../compute-networking-nova.rst:86 +msgid "Flat DHCP Network Manager" +msgstr "" + +#: ../compute-networking-nova.rst:90 msgid "" -"After configuring the :file:`local_settings` file as shown, you can run the " -"``manage.py syncdb`` command to populate this newly created database::" +"In single-host Flat DHCP mode you will be able to ping VMs through their " +"fixed IP from the ``nova-network`` node, but you cannot ping them from the " +"compute nodes. This is expected behavior." msgstr "" -#: ../networking_multi-dhcp-agents.rst:492 +#: ../compute-networking-nova.rst:96 msgid "" -"After deletion, if you restart the DHCP agent, it appears on the agent list " -"again." +"This is the default mode for OpenStack Compute. In this mode, Compute " +"creates a VLAN and bridge for each tenant. For multiple-machine " +"installations, the VLAN Network Mode requires a switch that supports VLAN " +"tagging (IEEE 802.1Q). The tenant gets a range of private IPs that are only " +"accessible from inside the VLAN. In order for a user to access the instances " +"in their tenant, a special VPN instance (code named cloudpipe) needs to be " +"created. Compute generates a certificate and key for the user to access the " +"VPN and starts the VPN automatically. It provides a private network segment " +"for each tenant's instances that can be accessed through a dedicated VPN " +"connection from the internet. In this mode, each tenant gets its own VLAN, " +"Linux networking bridge, and subnet." msgstr "" -#: ../networking_config-agents.rst:50 +#: ../compute-networking-nova.rst:109 msgid "" -"After following the NSX Administrator Guide, use the page for this " -"Hypervisor in the NSX Manager GUI to confirm that the node is properly " -"connected to the NSX Controller Cluster and that the NSX Controller Cluster " -"can see the ``br-int`` integration bridge." +"The subnets are specified by the network administrator, and are assigned " +"dynamically to a tenant when required. A DHCP server is started for each " +"VLAN to pass out IP addresses to VM instances from the subnet assigned to " +"the tenant. All instances belonging to one tenant are bridged into the same " +"VLAN for that tenant. OpenStack Compute creates the Linux networking bridges " +"and VLANs when required." msgstr "" -#: ../objectstorage-troubleshoot.rst:158 +#: ../compute-networking-nova.rst:115 +msgid "VLAN Network Manager" +msgstr "" + +#: ../compute-networking-nova.rst:117 msgid "" -"After it validates, save the builder and create a new ``account.builder``:" -msgstr "" - -#: ../compute-node-down.rst:184 -msgid "After power is recovered and all hardware components have restarted:" -msgstr "" - -#: ../blockstorage_multi_backend.rst:40 -msgid "" -"After setting the `enabled_backends` flag on an existing cinder service, and " -"restarting the Block Storage services, the original ``host`` service is " -"replaced with a new host service. The new service appears with a name like " -"``host@backend``. Use::" -msgstr "" - -#: ../keystone_certificates_for_pki.rst:235 -msgid "" -"After the old certificate reads as expired, you can safely remove the old " -"signing certificate from the file." -msgstr "" - -#: ../telemetry-data-retrieval.rst:39 -msgid "" -"After validating the query parameters, the processing is done on the " -"database side in the case of most database back ends in order to achieve " -"better performance." -msgstr "" - -#: ../blockstorage_backup_disks.rst:194 -msgid "After work cleaning" -msgstr "" - -#: ../blockstorage_glusterfs_backend.rst:83 -msgid "After you configure the GlusterFS service, complete these steps:" -msgstr "" - -#: ../networking_use.rst:26 -msgid "" -"After you install and configure Networking, tenants and administrators can " -"perform create-read-update-delete (CRUD) API networking operations by using " -"the Networking API directly or neutron command-line interface (CLI). The " -"neutron CLI is a wrapper around the Networking API. Every Networking API " -"call has a corresponding neutron command." -msgstr "" - -#: ../networking_arch.rst:29 -msgid "Agent" -msgstr "" - -#: ../baremetal.rst:47 -msgid "Agent deploy process" -msgstr "" - -#: ../telemetry-measurements.rst:645 -msgid "Aggregated numb\\ er of blocks re\\ ceived to block device" -msgstr "" - -#: ../telemetry-measurements.rst:650 -msgid "Aggregated numb\\ er of blocks se\\ nt to block dev\\ ice" -msgstr "" - -#: ../telemetry-data-collection.rst:613 -msgid "Aggregator" -msgstr "" - -#: ../telemetry-alarms.rst:80 -msgid "Alarm actions" -msgstr "" - -#: ../telemetry-alarms.rst:125 -msgid "Alarm creation" -msgstr "" - -#: ../telemetry-alarms.rst:26 -msgid "Alarm definitions" -msgstr "" - -#: ../telemetry-alarms.rst:303 -msgid "Alarm deletion" -msgstr "" - -#: ../telemetry-alarms.rst:54 -msgid "Alarm dimensioning" -msgstr "" - -#: ../telemetry-alarms.rst:74 -msgid "Alarm evaluation" -msgstr "" - -#: ../telemetry-alarms.rst:146 -msgid "" -"Alarm names must be unique for the alarms associated with an individual " -"project. The cloud administrator can limit the maximum resulting actions for " -"three different states, and the ability for a normal user to create ``log://" -"`` and ``test://`` notifiers is disabled. This prevents unintentional " -"consumption of disk and memory resources by the Telemetry service." -msgstr "" - -#: ../telemetry-alarms.rst:224 -msgid "Alarm retrieval" -msgstr "" - -#: ../telemetry-alarms.rst:262 -msgid "Alarm update" -msgstr "" - -#: ../telemetry-alarms.rst:5 -msgid "Alarms" -msgstr "" - -#: ../telemetry-alarms.rst:76 -msgid "" -"Alarms are evaluated by the ``alarm-evaluator`` service on a periodic basis, " -"defaulting to once every minute." -msgstr "" - -#: ../telemetry-alarms.rst:7 -msgid "" -"Alarms provide user-oriented Monitoring-as-a-Service for resources running " -"on OpenStack. This type of monitoring ensures you can automatically scale in " -"or out a group of instances through the Orchestration module, but you can " -"also use alarms for general-purpose awareness of your cloud resources' " -"health." -msgstr "" - -#: ../keystone_certificates_for_pki.rst:108 -msgid "" -"All certificate and key files must be in Privacy Enhanced Mail (PEM) format" -msgstr "" - -#: ../compute-node-down.rst:317 -msgid "All instances are restarted with euca2ools." -msgstr "" - -#: ../compute-networking-nova.rst:153 -msgid "" -"All machines must have a public and internal network interface (controlled " -"by these options: ``public_interface`` for the public interface, and " -"``flat_interface`` and ``vlan_interface`` for the internal interface with " -"flat or VLAN managers). This guide refers to the public network as the " -"external network and the private network as the internal or tenant network." +"These network managers can co-exist in a cloud system. However, because you " +"cannot select the type of network for a given tenant, you cannot configure " +"multiple network types in a single Compute installation." msgstr "" #: ../compute-networking-nova.rst:121 @@ -2563,174 +5701,1328 @@ msgid "" "``br100``." msgstr "" -#: ../objectstorage_characteristics.rst:12 -msgid "All objects have their own metadata." -msgstr "" - -#: ../objectstorage_characteristics.rst:9 +#: ../compute-networking-nova.rst:146 msgid "" -"All objects stored are replicated 3✕ in as-unique-as-possible zones, which " -"can be defined as a group of drives, a node, a rack, and so on." +"The internal network interface is used for communication with VMs. The " +"interface should not have an IP address attached to it before OpenStack " +"installation, it serves only as a fabric where the actual endpoints are VMs " +"and dnsmasq. Additionally, the internal network interface must be in " +"``promiscuous`` mode, so that it can receive packets whose target MAC " +"address is the guest VM, not the host." msgstr "" -#: ../objectstorage_characteristics.rst:7 -msgid "All objects stored in Object Storage have a URL." -msgstr "" - -#: ../telemetry-data-collection.rst:39 +#: ../compute-networking-nova.rst:153 msgid "" -"All the services send notifications about the executed operations or system " -"state in OpenStack. Several notifications carry information that can be " -"metered, like the CPU time of a VM instance created by OpenStack Compute " -"service." +"All machines must have a public and internal network interface (controlled " +"by these options: ``public_interface`` for the public interface, and " +"``flat_interface`` and ``vlan_interface`` for the internal interface with " +"flat or VLAN managers). This guide refers to the public network as the " +"external network and the private network as the internal or tenant network." msgstr "" -#: ../compute-flavors.rst:220 +#: ../compute-networking-nova.rst:160 msgid "" -"All the speed limit values in above example are specified in kilobytes/" -"second. And burst values are in kilobytes." +"For flat and flat DHCP modes, use the :command:`nova network-create` command " +"to create a network:" msgstr "" -#: ../blockstorage_backup_disks.rst:159 -msgid "Allocate more space to the snapshot and try the process again." +#: ../compute-networking-nova.rst:169 +msgid "specifies the network subnet." msgstr "" -#: ../networking_introduction.rst:118 +#: ../compute-networking-nova.rst:170 msgid "" -"Allocates requests to the instance with the least number of active " -"connections." +"specifies a range of fixed IP addresses to allocate, and can be a subset of " +"the ``--fixed-range-v4`` argument." msgstr "" -#: ../compute_arch.rst:358 -msgid "Allocating fixed IP addresses" -msgstr "" - -#: ../ts_cinder_config.rst:132 +#: ../compute-networking-nova.rst:173 msgid "" -"Along with the ``volumes_dir`` option, the iSCSI target driver also needs to " -"be configured to look in the correct place for the persistent files. This is " -"a simple entry in the :file:`/etc/tgt/conf.d` file that you should have set " -"when you installed OpenStack. If issues occur, verify that you have a :file:" -"`/etc/tgt/conf.d/cinder.conf` file." +"specifies the bridge device to which this network is connected on every " +"compute node." msgstr "" -#: ../keystone_certificates_for_pki.rst:204 -msgid "" -"Also, when copying the necessary files to a different server for replicating " -"the functionality, the entire directory of files is needed, not just the key " -"and cert files." +#: ../compute-networking-nova.rst:174 +msgid "This example uses the following parameters:" msgstr "" -#: ../networking_config-plugins.rst:157 +#: ../compute-networking-nova.rst:179 +msgid "DHCP server: dnsmasq" +msgstr "" + +#: ../compute-networking-nova.rst:181 msgid "" -"Alternatively the transport zone identifier can be retrieved by query the " -"NSX-mh API: ``/ws.v1/transport-zone``" +"The Compute service uses `dnsmasq `__ as the DHCP server when using either Flat DHCP Network Manager or " +"VLAN Network Manager. For Compute to operate in IPv4/IPv6 dual-stack mode, " +"use at least dnsmasq v2.63. The ``nova-network`` service is responsible for " +"starting dnsmasq processes." +msgstr "" + +#: ../compute-networking-nova.rst:188 +msgid "" +"The behavior of dnsmasq can be customized by creating a dnsmasq " +"configuration file. Specify the configuration file using the " +"``dnsmasq_config_file`` configuration option:" +msgstr "" + +#: ../compute-networking-nova.rst:196 +msgid "" +"For more information about creating a dnsmasq configuration file, see the " +"`OpenStack Configuration Reference `__, and `the dnsmasq documentation `__." +msgstr "" + +#: ../compute-networking-nova.rst:202 +msgid "" +"dnsmasq also acts as a caching DNS server for instances. You can specify the " +"DNS server that dnsmasq uses by setting the ``dns_server`` configuration " +"option in :file:`/etc/nova/nova.conf`. This example configures dnsmasq to " +"use Google's public DNS server:" +msgstr "" + +#: ../compute-networking-nova.rst:211 +msgid "" +"dnsmasq logs to syslog (typically :file:`/var/log/syslog` or :file:`/var/log/" +"messages`, depending on Linux distribution). Logs can be useful for " +"troubleshooting, especially in a situation where VM instances boot " +"successfully but are not reachable over the network." +msgstr "" + +#: ../compute-networking-nova.rst:216 +msgid "" +"Administrators can specify the starting point IP address to reserve with the " +"DHCP server (in the format n.n.n.n) with this command:" +msgstr "" + +#: ../compute-networking-nova.rst:223 +msgid "" +"This reservation only affects which IP address the VMs start at, not the " +"fixed IP addresses that ``nova-network`` places on the bridges." +msgstr "" + +#: ../compute-networking-nova.rst:228 +msgid "Configure Compute to use IPv6 addresses" +msgstr "" + +#: ../compute-networking-nova.rst:230 +msgid "" +"If you are using OpenStack Compute with ``nova-network``, you can put " +"Compute into dual-stack mode, so that it uses both IPv4 and IPv6 addresses " +"for communication. In dual-stack mode, instances can acquire their IPv6 " +"global unicast address by using a stateless address auto-configuration " +"mechanism [RFC 4862/2462]. IPv4/IPv6 dual-stack mode works with both " +"``VlanManager`` and ``FlatDHCPManager`` networking modes." +msgstr "" + +#: ../compute-networking-nova.rst:238 +msgid "" +"In ``VlanManager`` networking mode, each project uses a different 64-bit " +"global routing prefix. In ``FlatDHCPManager`` mode, all instances use one 64-" +"bit global routing prefix." +msgstr "" + +#: ../compute-networking-nova.rst:242 +msgid "" +"This configuration was tested with virtual machine images that have an IPv6 " +"stateless address auto-configuration capability. This capability is required " +"for any VM to run with an IPv6 address. You must use an EUI-64 address for " +"stateless address auto-configuration. Each node that executes a ``nova-*`` " +"service must have ``python-netaddr`` and ``radvd`` installed." +msgstr "" + +#: ../compute-networking-nova.rst:249 +msgid "**Switch into IPv4/IPv6 dual-stack mode**" +msgstr "" + +#: ../compute-networking-nova.rst:251 +msgid "For every node running a ``nova-*`` service, install python-netaddr:" +msgstr "" + +#: ../compute-networking-nova.rst:257 +msgid "" +"For every node running ``nova-network``, install ``radvd`` and configure " +"IPv6 networking:" +msgstr "" + +#: ../compute-networking-nova.rst:266 +msgid "" +"On all nodes, edit the :file:`nova.conf` file and specify ``use_ipv6 = " +"True``." +msgstr "" + +#: ../compute-networking-nova.rst:269 +msgid "Restart all ``nova-*`` services." +msgstr "" + +#: ../compute-networking-nova.rst:271 +msgid "**IPv6 configuration options**" +msgstr "" + +#: ../compute-networking-nova.rst:273 +msgid "" +"You can use the following options with the :command:`nova network-create` " +"command:" +msgstr "" + +#: ../compute-networking-nova.rst:276 +msgid "" +"Add a fixed range for IPv6 addresses to the :command:`nova network-create` " +"command. Specify ``public`` or ``private`` after the ``network-create`` " +"parameter." +msgstr "" + +#: ../compute-networking-nova.rst:285 +msgid "" +"Set the IPv6 global routing prefix by using the ``--fixed_range_v6`` " +"parameter. The default value for the parameter is ``fd00::/48``." +msgstr "" + +#: ../compute-networking-nova.rst:289 +msgid "" +"When you use ``FlatDHCPManager``, the command uses the original ``--" +"fixed_range_v6`` value. For example:" +msgstr "" + +#: ../compute-networking-nova.rst:297 +msgid "" +"When you use ``VlanManager``, the command increments the subnet ID to create " +"subnet prefixes. Guest VMs use this prefix to generate their IPv6 global " +"unicast address. For example:" +msgstr "" + +# #-#-#-#-# compute-networking-nova.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +# #-#-#-#-# compute-remote-console-access.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +# #-#-#-#-# compute-security.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +# #-#-#-#-# objectstorage-troubleshoot.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +#: ../compute-networking-nova.rst:309 ../compute-networking-nova.rst:507 +#: ../compute-remote-console-access.rst:152 ../compute-security.rst:103 +#: ../objectstorage-troubleshoot.rst:61 +msgid "Configuration option = Default value" +msgstr "" + +#: ../compute-networking-nova.rst:311 ../compute-networking-nova.rst:509 +msgid "[DEFAULT]" +msgstr "" + +#: ../compute-networking-nova.rst:313 +msgid "fixed_range_v6 = fd00::/48" +msgstr "" + +#: ../compute-networking-nova.rst:314 +msgid "(StrOpt) Fixed IPv6 address block" +msgstr "" + +#: ../compute-networking-nova.rst:315 +msgid "gateway_v6 = None" +msgstr "" + +#: ../compute-networking-nova.rst:316 +msgid "(StrOpt) Default IPv6 gateway" +msgstr "" + +#: ../compute-networking-nova.rst:317 +msgid "ipv6_backend = rfc2462" +msgstr "" + +#: ../compute-networking-nova.rst:318 +msgid "(StrOpt) Backend to use for IPv6 generation" +msgstr "" + +#: ../compute-networking-nova.rst:319 +msgid "use_ipv6 = False" +msgstr "" + +#: ../compute-networking-nova.rst:320 +msgid "(BoolOpt) Use IPv6" +msgstr "" + +#: ../compute-networking-nova.rst:323 +msgid "Metadata service" +msgstr "" + +#: ../compute-networking-nova.rst:325 +msgid "" +"Compute uses a metadata service for virtual machine instances to retrieve " +"instance-specific data. Instances access the metadata service at " +"``http://169.254.169.254``. The metadata service supports two sets of APIs: " +"an OpenStack metadata API and an EC2-compatible API. Both APIs are versioned " +"by date." +msgstr "" + +#: ../compute-networking-nova.rst:331 +msgid "" +"To retrieve a list of supported versions for the OpenStack metadata API, " +"make a GET request to ``http://169.254.169.254/openstack``:" +msgstr "" + +#: ../compute-networking-nova.rst:342 +msgid "" +"To list supported versions for the EC2-compatible metadata API, make a GET " +"request to ``http://169.254.169.254``:" +msgstr "" + +#: ../compute-networking-nova.rst:359 +msgid "" +"If you write a consumer for one of these APIs, always attempt to access the " +"most recent API version supported by your consumer first, then fall back to " +"an earlier version if the most recent one is not available." +msgstr "" + +#: ../compute-networking-nova.rst:363 +msgid "" +"Metadata from the OpenStack API is distributed in JSON format. To retrieve " +"the metadata, make a GET request to ``http://169.254.169.254/" +"openstack/2012-08-10/meta_data.json``:" +msgstr "" + +#: ../compute-networking-nova.rst:393 +msgid "" +"Instances also retrieve user data (passed as the ``user_data`` parameter in " +"the API call or by the ``--user_data`` flag in the :command:`nova boot` " +"command) through the metadata service, by making a GET request to " +"``http://169.254.169.254/openstack/2012-08-10/user_data``:" +msgstr "" + +#: ../compute-networking-nova.rst:404 +msgid "" +"The metadata service has an API that is compatible with version 2009-04-04 " +"of the `Amazon EC2 metadata service `__. This means " +"that virtual machine images designed for EC2 will work properly with " +"OpenStack." +msgstr "" + +#: ../compute-networking-nova.rst:410 +msgid "" +"The EC2 API exposes a separate URL for each metadata element. Retrieve a " +"listing of these elements by making a GET query to " +"``http://169.254.169.254/2009-04-04/meta-data/``:" +msgstr "" + +#: ../compute-networking-nova.rst:451 +msgid "" +"Instances can retrieve the public SSH key (identified by keypair name when a " +"user requests a new instance) by making a GET request to " +"``http://169.254.169.254/2009-04-04/meta-data/public-keys/0/openssh-key``:" +msgstr "" + +#: ../compute-networking-nova.rst:463 +msgid "" +"Instances can retrieve user data by making a GET request to " +"``http://169.254.169.254/2009-04-04/user-data``:" +msgstr "" + +#: ../compute-networking-nova.rst:472 +msgid "" +"The metadata service is implemented by either the nova-api service or the " +"nova-api-metadata service. Note that the nova-api-metadata service is " +"generally only used when running in multi-host mode, as it retrieves " +"instance-specific metadata. If you are running the nova-api service, you " +"must have ``metadata`` as one of the elements listed in the ``enabled_apis`` " +"configuration option in :file:`/etc/nova/nova.conf`. The default " +"``enabled_apis`` configuration setting includes the metadata service, so you " +"should not need to modify it." +msgstr "" + +#: ../compute-networking-nova.rst:481 +msgid "" +"Hosts access the service at ``169.254.169.254:80``, and this is translated " +"to ``metadata_host:metadata_port`` by an iptables rule established by the " +"``nova-network`` service. In multi-host mode, you can set ``metadata_host`` " +"to ``127.0.0.1``." +msgstr "" + +#: ../compute-networking-nova.rst:486 +msgid "" +"For instances to reach the metadata service, the ``nova-network`` service " +"must configure iptables to NAT port ``80`` of the ``169.254.169.254`` " +"address to the IP address specified in ``metadata_host`` (this defaults to ``" +"$my_ip``, which is the IP address of the ``nova-network`` service) and port " +"specified in ``metadata_port`` (which defaults to ``8775``) in :file:`/etc/" +"nova/nova.conf`." +msgstr "" + +#: ../compute-networking-nova.rst:495 +msgid "" +"The ``metadata_host`` configuration option must be an IP address, not a host " +"name." +msgstr "" + +#: ../compute-networking-nova.rst:498 +msgid "" +"The default Compute service settings assume that ``nova-network`` and ``nova-" +"api`` are running on the same host. If this is not the case, in the :file:`/" +"etc/nova/nova.conf` file on the host running ``nova-network``, set the " +"``metadata_host`` configuration option to the IP address of the host where " +"nova-api is running." +msgstr "" + +#: ../compute-networking-nova.rst:511 +msgid "metadata_cache_expiration = 15" +msgstr "" + +#: ../compute-networking-nova.rst:512 +msgid "" +"(IntOpt) Time in seconds to cache metadata; 0 to disable metadata caching " +"entirely (not recommended). Increasing this should improve response times of " +"the metadata API when under heavy load. Higher values may increase memory " +"usage and result in longer times for host metadata changes to take effect." +msgstr "" + +#: ../compute-networking-nova.rst:517 +msgid "metadata_host = $my_ip" +msgstr "" + +#: ../compute-networking-nova.rst:518 +msgid "(StrOpt) The IP address for the metadata API server" +msgstr "" + +#: ../compute-networking-nova.rst:519 +msgid "metadata_listen = 0.0.0.0" +msgstr "" + +#: ../compute-networking-nova.rst:520 +msgid "(StrOpt) The IP address on which the metadata API will listen." +msgstr "" + +#: ../compute-networking-nova.rst:521 +msgid "metadata_listen_port = 8775" +msgstr "" + +#: ../compute-networking-nova.rst:522 +msgid "(IntOpt) The port on which the metadata API will listen." +msgstr "" + +#: ../compute-networking-nova.rst:523 +msgid "metadata_manager = nova.api.manager.MetadataManager" +msgstr "" + +#: ../compute-networking-nova.rst:524 +msgid "(StrOpt) OpenStack metadata service manager" +msgstr "" + +#: ../compute-networking-nova.rst:525 +msgid "metadata_port = 8775" +msgstr "" + +#: ../compute-networking-nova.rst:526 +msgid "(IntOpt) The port for the metadata API port" +msgstr "" + +#: ../compute-networking-nova.rst:527 +msgid "metadata_workers = None" +msgstr "" + +#: ../compute-networking-nova.rst:528 +msgid "" +"(IntOpt) Number of workers for metadata service. The default will be the " +"number of CPUs available." +msgstr "" + +#: ../compute-networking-nova.rst:529 +msgid "" +"vendordata_driver = nova.api.metadata.vendordata_json.JsonFileVendorData" +msgstr "" + +#: ../compute-networking-nova.rst:530 +msgid "(StrOpt) Driver to use for vendor data" +msgstr "" + +#: ../compute-networking-nova.rst:531 +msgid "vendordata_jsonfile_path = None" +msgstr "" + +#: ../compute-networking-nova.rst:532 +msgid "(StrOpt) File to load JSON formatted vendor data from" +msgstr "" + +#: ../compute-networking-nova.rst:535 +msgid "Enable ping and SSH on VMs" +msgstr "" + +#: ../compute-networking-nova.rst:537 +msgid "" +"You need to enable ``ping`` and ``ssh`` on your VMs for network access. This " +"can be done with either the :command:`nova` or :command:`euca2ools` commands." +msgstr "" + +#: ../compute-networking-nova.rst:543 +msgid "" +"Run these commands as root only if the credentials used to interact with " +"nova-api are in :file:`/root/.bashrc`. If the EC2 credentials in the :file:`." +"bashrc` file are for an unprivileged user, you must run these commands as " +"that user instead." +msgstr "" + +#: ../compute-networking-nova.rst:548 +msgid "Enable ping and SSH with :command:`nova` commands:" +msgstr "" + +#: ../compute-networking-nova.rst:555 +msgid "Enable ping and SSH with ``euca2ools``:" +msgstr "" + +#: ../compute-networking-nova.rst:562 +msgid "" +"If you have run these commands and still cannot ping or SSH your instances, " +"check the number of running ``dnsmasq`` processes, there should be two. If " +"not, kill the processes and restart the service with these commands:" +msgstr "" + +#: ../compute-networking-nova.rst:573 +msgid "Configure public (floating) IP addresses" +msgstr "" + +#: ../compute-networking-nova.rst:575 +msgid "" +"This section describes how to configure floating IP addresses with ``nova-" +"network``. For information about doing this with OpenStack Networking, see :" +"ref:`L3-routing-and-NAT`." +msgstr "" + +#: ../compute-networking-nova.rst:580 +msgid "Private and public IP addresses" +msgstr "" + +#: ../compute-networking-nova.rst:582 +msgid "" +"In this section, the term floating IP address is used to refer to an IP " +"address, usually public, that you can dynamically add to a running virtual " +"instance." +msgstr "" + +#: ../compute-networking-nova.rst:586 +msgid "" +"Every virtual instance is automatically assigned a private IP address. You " +"can choose to assign a public (or floating) IP address instead. OpenStack " +"Compute uses network address translation (NAT) to assign floating IPs to " +"virtual instances." +msgstr "" + +#: ../compute-networking-nova.rst:591 +msgid "" +"To be able to assign a floating IP address, edit the :file:`/etc/nova/nova." +"conf` file to specify which interface the ``nova-network`` service should " +"bind public IP addresses to:" +msgstr "" + +#: ../compute-networking-nova.rst:599 +msgid "" +"If you make changes to the :file:`/etc/nova/nova.conf` file while the ``nova-" +"network`` service is running, you will need to restart the service to pick " +"up the changes." +msgstr "" + +#: ../compute-networking-nova.rst:605 +msgid "" +"Floating IPs are implemented by using a source NAT (SNAT rule in iptables), " +"so security groups can sometimes display inconsistent behavior if VMs use " +"their floating IP to communicate with other VMs, particularly on the same " +"physical host. Traffic from VM to VM across the fixed network does not have " +"this issue, and so this is the recommended setup. To ensure that traffic " +"does not get SNATed to the floating range, explicitly set:" +msgstr "" + +#: ../compute-networking-nova.rst:617 +msgid "" +"The ``x.x.x.x/y`` value specifies the range of floating IPs for each pool of " +"floating IPs that you define. This configuration is also required if the VMs " +"in the source group have floating IPs." +msgstr "" + +#: ../compute-networking-nova.rst:622 +msgid "Enable IP forwarding" +msgstr "" + +#: ../compute-networking-nova.rst:624 +msgid "" +"IP forwarding is disabled by default on most Linux distributions. You will " +"need to enable it in order to use floating IPs." +msgstr "" + +#: ../compute-networking-nova.rst:629 +msgid "" +"IP forwarding only needs to be enabled on the nodes that run ``nova-" +"network``. However, you will need to enable it on all compute nodes if you " +"use ``multi_host`` mode." +msgstr "" + +#: ../compute-networking-nova.rst:633 +msgid "To check if IP forwarding is enabled, run:" msgstr "" #: ../compute-networking-nova.rst:640 ../compute-networking-nova.rst:655 msgid "Alternatively, run:" msgstr "" -#: ../compute-manage-logs.rst:231 +#: ../compute-networking-nova.rst:647 +msgid "In these examples, IP forwarding is disabled." +msgstr "" + +#: ../compute-networking-nova.rst:649 +msgid "To enable IP forwarding dynamically, run:" +msgstr "" + +#: ../compute-networking-nova.rst:661 msgid "" -"Alternatively, use a `Python websocket client `__." +"To make the changes permanent, edit the ``/etc/sysctl.conf`` file and update " +"the IP forwarding setting:" msgstr "" -#: ../compute-manage-logs.rst:208 -msgid "Alternatively, use the API directly:" +#: ../compute-networking-nova.rst:668 +msgid "Save the file and run this command to apply the changes:" msgstr "" -#: ../blockstorage_volume_backups.rst:90 +#: ../compute-networking-nova.rst:674 +msgid "You can also apply the changes by restarting the network service:" +msgstr "" + +#: ../compute-networking-nova.rst:676 +msgid "on Ubuntu, Debian:" +msgstr "" + +#: ../compute-networking-nova.rst:682 +msgid "on RHEL, Fedora, CentOS, openSUSE and SLES:" +msgstr "" + +#: ../compute-networking-nova.rst:689 +msgid "Create a list of available floating IP addresses" +msgstr "" + +#: ../compute-networking-nova.rst:691 msgid "" -"Alternatively, you can export and save the metadata of selected volume " -"backups. Doing so precludes the need to back up the entire Block Storage " -"database. This is useful if you need only a small subset of volumes to " -"survive a catastrophic database failure." +"Compute maintains a list of floating IP addresses that are available for " +"assigning to instances. Use the :command:`nova-manage floating` commands to " +"perform floating IP operations:" msgstr "" -#: ../compute-manage-logs.rst:78 +#: ../compute-networking-nova.rst:695 +msgid "Add entries to the list:" +msgstr "" + +#: ../compute-networking-nova.rst:701 +msgid "List the floating IP addresses in the pool:" +msgstr "" + +#: ../compute-networking-nova.rst:707 +msgid "Create specific floating IPs for either a single address or a subnet:" +msgstr "" + +#: ../compute-networking-nova.rst:714 msgid "" -"Although this example uses the same local facility for each service " -"(``LOG_LOCAL0``, which corresponds to syslog facility ``LOCAL0``), we " -"recommend that you configure a separate local facility for each service, as " -"this provides better isolation and more flexibility. For example, you can " -"capture logging information at different severity levels for different " -"services. syslog allows you to define up to eight local facilities, " -"``LOCAL0, LOCAL1, ..., LOCAL7``. For more information, see the syslog " -"documentation." +"Remove floating IP addresses using the same parameters as the create command:" msgstr "" -#: ../telemetry-measurements.rst:1326 -msgid "Amount of energy" -msgstr "" - -#: ../telemetry-data-collection.rst:400 +#: ../compute-networking-nova.rst:721 msgid "" -"An IPMI agent instance could be installed on each and every compute node " -"with IPMI support, except when the node is managed by the Bare metal service " -"and the ``conductor.send_sensor_data`` option is set to ``true`` in the Bare " -"metal service. It is no harm to install this agent on a compute node without " -"IPMI or Intel Node Manager support, as the agent checks for the hardware and " -"if none is available, returns empty data. It is suggested that you install " -"the IPMI agent only on an IPMI capable node for performance reasons." +"For more information about how administrators can associate floating IPs " +"with instances, see `Manage IP addresses `__ in the OpenStack Admin " +"User Guide." msgstr "" -#: ../identity_concepts.rst:19 +#: ../compute-networking-nova.rst:727 +msgid "Automatically add floating IPs" +msgstr "" + +#: ../compute-networking-nova.rst:729 msgid "" -"An Identity service API v3 entity. Represents a collection of projects and " -"users that defines administrative boundaries for the management of Identity " -"entities. A domain, which can represent an individual, company, or operator-" -"owned space, exposes administrative activities directly to system users. " -"Users can be granted the administrator role for a domain. A domain " -"administrator can create projects, users, and groups in a domain and assign " -"roles to users and groups in a domain." +"You can configure ``nova-network`` to automatically allocate and assign a " +"floating IP address to virtual instances when they are launched. Add this " +"line to the :file:`/etc/nova/nova.conf` file:" msgstr "" -#: ../identity_concepts.rst:35 +#: ../compute-networking-nova.rst:737 +msgid "Save the file, and restart ``nova-network``" +msgstr "" + +#: ../compute-networking-nova.rst:741 msgid "" -"An Identity service API v3 entity. Represents a collection of users that are " -"owned by a domain. A group role granted to a domain or project applies to " -"all users in the group. Adding users to, or removing users from, a group " -"respectively grants, or revokes, their role and authentication to the " -"associated domain or project." +"If this option is enabled, but all floating IP addresses have already been " +"allocated, the :command:`nova boot` command will fail." msgstr "" -#: ../identity_concepts.rst:54 +#: ../compute-networking-nova.rst:745 +msgid "Remove a network from a project" +msgstr "" + +#: ../compute-networking-nova.rst:747 msgid "" -"An Identity service API v3 entity. Represents a general division in an " -"OpenStack deployment. You can associate zero or more sub-regions with a " -"region to make a tree-like structured hierarchy. Although a region does not " -"have a geographical connotation, a deployment can use a geographical name " -"for a region, such as ``us-east``." +"You cannot delete a network that has been associated to a project. This " +"section describes the procedure for dissociating it so that it can be " +"deleted." msgstr "" -#: ../networking_adv-features.rst:49 +#: ../compute-networking-nova.rst:751 msgid "" -"An Networking L2 network (identified by a UUID and optional name) whose " -"ports can be attached as vNICs to Compute instances and to various " -"Networking agents. The Open vSwitch and Linux Bridge plug-ins each support " -"several different mechanisms to realize virtual networks." +"In order to disassociate the network, you will need the ID of the project it " +"has been associated to. To get the project ID, you will need to be an " +"administrator." msgstr "" -#: ../networking_config-agents.rst:285 -msgid "An OVS-based plug-in such as OVS, NSX, NEC, BigSwitch/Floodlight:" -msgstr "" - -#: ../objectstorage-monitoring.rst:8 +#: ../compute-networking-nova.rst:755 msgid "" -"An OpenStack Object Storage cluster is a collection of many daemons that " -"work together across many nodes. With so many different components, you must " -"be able to tell what is going on inside the cluster. Tracking server-level " -"meters like CPU utilization, load, memory consumption, disk usage and " -"utilization, and so on is necessary, but not sufficient." +"Disassociate the network from the project using the :command:`scrub` " +"command, with the project ID as the final parameter:" msgstr "" -#: ../identity_concepts.rst:69 +#: ../compute-networking-nova.rst:763 +msgid "Multiple interfaces for instances (multinic)" +msgstr "" + +#: ../compute-networking-nova.rst:765 msgid "" -"An OpenStack service, such as Compute (nova), Object Storage (swift), or " -"Image service (glance), that provides one or more endpoints through which " -"users can access resources and perform operations." +"The multinic feature allows you to use more than one interface with your " +"instances. This is useful in several scenarios:" +msgstr "" + +#: ../compute-networking-nova.rst:768 +msgid "SSL Configurations (VIPs)" +msgstr "" + +#: ../compute-networking-nova.rst:770 +msgid "Services failover/HA" +msgstr "" + +#: ../compute-networking-nova.rst:772 +msgid "Bandwidth Allocation" +msgstr "" + +#: ../compute-networking-nova.rst:774 +msgid "Administrative/Public access to your instances" +msgstr "" + +#: ../compute-networking-nova.rst:776 +msgid "" +"Each VIP represents a separate network with its own IP block. Every network " +"mode has its own set of changes regarding multinic usage:" +msgstr "" + +#: ../compute-networking-nova.rst:779 +msgid "|multinic flat manager|" +msgstr "" + +#: ../compute-networking-nova.rst:781 +msgid "|multinic flatdhcp manager|" +msgstr "" + +#: ../compute-networking-nova.rst:783 +msgid "|multinic VLAN manager|" +msgstr "" + +#: ../compute-networking-nova.rst:786 +msgid "Using multinic" +msgstr "" + +#: ../compute-networking-nova.rst:788 +msgid "" +"In order to use multinic, create two networks, and attach them to the tenant " +"(named ``project`` on the command line):" +msgstr "" + +#: ../compute-networking-nova.rst:796 +msgid "" +"Each new instance will now receive two IP addresses from their respective " +"DHCP servers:" +msgstr "" + +#: ../compute-networking-nova.rst:810 +msgid "" +"Make sure you start the second interface on the instance, or it won't be " +"reachable through the second IP." +msgstr "" + +#: ../compute-networking-nova.rst:813 +msgid "" +"This example demonstrates how to set up the interfaces within the instance. " +"This is the configuration that needs to be applied inside the image." +msgstr "" + +#: ../compute-networking-nova.rst:817 +msgid "Edit the :file:`/etc/network/interfaces` file:" +msgstr "" + +#: ../compute-networking-nova.rst:832 +msgid "" +"If the Virtual Network Service Neutron is installed, you can specify the " +"networks to attach to the interfaces by using the ``--nic`` flag with the :" +"command:`nova` command:" +msgstr "" + +#: ../compute-networking-nova.rst:841 +msgid "Troubleshooting Networking" +msgstr "" + +#: ../compute-networking-nova.rst:844 +msgid "Cannot reach floating IPs" +msgstr "" + +#: ../compute-networking-nova.rst:846 +msgid "If you cannot reach your instances through the floating IP address:" +msgstr "" + +#: ../compute-networking-nova.rst:848 +msgid "" +"Check that the default security group allows ICMP (ping) and SSH (port 22), " +"so that you can reach the instances:" +msgstr "" + +#: ../compute-networking-nova.rst:861 +msgid "" +"Check the NAT rules have been added to iptables on the node that is running " +"``nova-network``:" +msgstr "" + +#: ../compute-networking-nova.rst:870 +msgid "" +"Check that the public address (`68.99.26.170 <68.99.26.170>`__ in this " +"example), has been added to your public interface. You should see the " +"address in the listing when you use the :command:`ip addr` command:" +msgstr "" + +#: ../compute-networking-nova.rst:886 +msgid "" +"You cannot use ``SSH`` to access an instance with a public IP from within " +"the same server because the routing configuration does not allow it." +msgstr "" + +#: ../compute-networking-nova.rst:890 +msgid "" +"Use ``tcpdump`` to identify if packets are being routed to the inbound " +"interface on the compute host. If the packets are reaching the compute hosts " +"but the connection is failing, the issue may be that the packet is being " +"dropped by reverse path filtering. Try disabling reverse-path filtering on " +"the inbound interface. For example, if the inbound interface is ``eth2``, " +"run:" +msgstr "" + +#: ../compute-networking-nova.rst:901 +msgid "" +"If this solves the problem, add the following line to :file:`/etc/sysctl." +"conf` so that the reverse-path filter is persistent:" +msgstr "" + +#: ../compute-networking-nova.rst:909 +msgid "Temporarily disable firewall" +msgstr "" + +#: ../compute-networking-nova.rst:911 +msgid "" +"To help debug networking issues with reaching VMs, you can disable the " +"firewall by setting this option in :file:`/etc/nova/nova.conf`:" +msgstr "" + +#: ../compute-networking-nova.rst:918 +msgid "" +"We strongly recommend you remove this line to re-enable the firewall once " +"your networking issues have been resolved." +msgstr "" + +#: ../compute-networking-nova.rst:922 +msgid "Packet loss from instances to nova-network server (VLANManager mode)" +msgstr "" + +#: ../compute-networking-nova.rst:924 +msgid "" +"If you can access your instances with ``SSH`` but the network to your " +"instance is slow, or if you find that running certain operations are slower " +"than they should be (for example, ``sudo``), packet loss could be occurring " +"on the connection to the instance." +msgstr "" + +#: ../compute-networking-nova.rst:929 +msgid "" +"Packet loss can be caused by Linux networking configuration settings related " +"to bridges. Certain settings can cause packets to be dropped between the " +"VLAN interface (for example, ``vlan100``) and the associated bridge " +"interface (for example, ``br100``) on the host running ``nova-network``." +msgstr "" + +#: ../compute-networking-nova.rst:935 +msgid "" +"One way to check whether this is the problem is to open three terminals and " +"run the following commands:" +msgstr "" + +#: ../compute-networking-nova.rst:938 +msgid "" +"In the first terminal, on the host running ``nova-network``, use ``tcpdump`` " +"on the VLAN interface to monitor DNS-related traffic (UDP, port 53). As " +"root, run:" +msgstr "" + +#: ../compute-networking-nova.rst:946 +msgid "" +"In the second terminal, also on the host running ``nova-network``, use " +"``tcpdump`` to monitor DNS-related traffic on the bridge interface. As root, " +"run:" +msgstr "" + +#: ../compute-networking-nova.rst:954 +msgid "" +"In the third terminal, use ``SSH`` to access the instance and generate DNS " +"requests by using the :command:`nslookup` command:" +msgstr "" + +#: ../compute-networking-nova.rst:961 +msgid "" +"The symptoms may be intermittent, so try running :command:`nslookup` " +"multiple times. If the network configuration is correct, the command should " +"return immediately each time. If it is not correct, the command hangs for " +"several seconds before returning." +msgstr "" + +#: ../compute-networking-nova.rst:966 +msgid "" +"If the :command:`nslookup` command sometimes hangs, and there are packets " +"that appear in the first terminal but not the second, then the problem may " +"be due to filtering done on the bridges. Try disabling filtering, and " +"running these commands as root:" +msgstr "" + +#: ../compute-networking-nova.rst:977 +msgid "" +"If this solves your issue, add the following line to :file:`/etc/sysctl." +"conf` so that the changes are persistent:" +msgstr "" + +#: ../compute-networking-nova.rst:987 +msgid "KVM: Network connectivity works initially, then fails" +msgstr "" + +#: ../compute-networking-nova.rst:989 +msgid "" +"With KVM hypervisors, instances running Ubuntu 12.04 sometimes lose network " +"connectivity after functioning properly for a period of time. Try loading " +"the ``vhost_net`` kernel module as a workaround for this issue (see `bug " +"#997978 `__) . This kernel module may also `improve network performance `__ on KVM. To load the kernel module:" +msgstr "" + +#: ../compute-networking-nova.rst:1004 +msgid "Loading the module has no effect on running instances." +msgstr "" + +#: ../compute-node-down.rst:5 +msgid "Recover from a failed compute node" +msgstr "" + +#: ../compute-node-down.rst:7 +msgid "" +"If Compute is deployed with a shared file system, and a node fails, there " +"are several methods to quickly recover from the failure. This section " +"discusses manual recovery." +msgstr "" + +#: ../compute-node-down.rst:12 +msgid "Evacuate instances" +msgstr "" + +#: ../compute-node-down.rst:13 +msgid "" +"If a cloud compute node fails due to a hardware malfunction or another " +"reason, you can evacuate instances using the :command:`nova evacuate` " +"command. See the `Admin User Guide `__." +msgstr "" + +#: ../compute-node-down.rst:22 +msgid "Manual recovery" +msgstr "" + +#: ../compute-node-down.rst:23 +msgid "Use this procedure to recover a failed compute node manually:" +msgstr "" + +#: ../compute-node-down.rst:25 +msgid "" +"Identify the VMs on the affected hosts. To do this, you can use a " +"combination of :command:`nova list` and :command:`nova show` or :command:" +"`euca-describe-instances`. For example, this command displays information " +"about instance i-000015b9 that is running on node np-rcc54:" +msgstr "" + +#: ../compute-node-down.rst:35 +msgid "" +"Query the Compute database to check the status of the host. This example " +"converts an EC2 API instance ID into an OpenStack ID. If you use the :" +"command:`nova` commands, you can substitute the ID directly (the output in " +"this example has been truncated):" +msgstr "" + +#: ../compute-node-down.rst:63 +msgid "" +"The credentials for your database can be found in :file:`/etc/nova.conf`." +msgstr "" + +#: ../compute-node-down.rst:66 +msgid "" +"Decide which compute host the affected VM should be moved to, and run this " +"database command to move the VM to the new host:" +msgstr "" + +#: ../compute-node-down.rst:73 +msgid "" +"If you are using a hypervisor that relies on libvirt (such as KVM), update " +"the :file:`libvirt.xml` file (found in :file:`/var/lib/nova/instances/" +"[instance ID]`) with these changes:" +msgstr "" + +#: ../compute-node-down.rst:77 +msgid "" +"Change the ``DHCPSERVER`` value to the host IP address of the new compute " +"host." +msgstr "" + +#: ../compute-node-down.rst:80 +msgid "Update the VNC IP to `0.0.0.0`" +msgstr "" + +#: ../compute-node-down.rst:82 +msgid "Reboot the VM:" +msgstr "" + +#: ../compute-node-down.rst:88 +msgid "" +"The database update and :command:`nova reboot` command should be all that is " +"required to recover a VM from a failed host. However, if you continue to " +"have problems try recreating the network filter configuration using " +"``virsh``, restarting the Compute services, or updating the ``vm_state`` and " +"``power_state`` in the Compute database." +msgstr "" + +#: ../compute-node-down.rst:97 +msgid "Recover from a UID/GID mismatch" +msgstr "" + +#: ../compute-node-down.rst:99 +msgid "" +"In some cases, files on your compute node can end up using the wrong UID or " +"GID. This can happen when running OpenStack Compute, using a shared file " +"system, or with an automated configuration tool. This can cause a number of " +"problems, such as inability to perform live migrations, or start virtual " +"machines." +msgstr "" + +#: ../compute-node-down.rst:105 +msgid "This procedure runs on nova-compute hosts, based on the KVM hypervisor:" +msgstr "" + +#: ../compute-node-down.rst:107 +msgid "" +"Set the nova UID in :file:`/etc/passwd` to the same number on all hosts (for " +"example, 112)." +msgstr "" + +#: ../compute-node-down.rst:112 +msgid "" +"Make sure you choose UIDs or GIDs that are not in use for other users or " +"groups." +msgstr "" + +#: ../compute-node-down.rst:115 +msgid "" +"Set the ``libvirt-qemu`` UID in :file:`/etc/passwd` to the same number on " +"all hosts (for example, 119)." +msgstr "" + +#: ../compute-node-down.rst:118 +msgid "" +"Set the ``nova`` group in :file:`/etc/group` file to the same number on all " +"hosts (for example, 120)." +msgstr "" + +#: ../compute-node-down.rst:121 +msgid "" +"Set the ``libvirtd`` group in :file:`/etc/group` file to the same number on " +"all hosts (for example, 119)." +msgstr "" + +#: ../compute-node-down.rst:124 +msgid "Stop the services on the compute node." +msgstr "" + +#: ../compute-node-down.rst:126 +msgid "Change all the files owned by user or group nova. For example:" +msgstr "" + +#: ../compute-node-down.rst:134 +msgid "Repeat all steps for the :file:`libvirt-qemu` files, if required." +msgstr "" + +#: ../compute-node-down.rst:136 +msgid "Restart the services." +msgstr "" + +#: ../compute-node-down.rst:138 +msgid "" +"Run the :command:`find` command to verify that all files use the correct " +"identifiers." +msgstr "" + +#: ../compute-node-down.rst:144 +msgid "Recover cloud after disaster" +msgstr "" + +#: ../compute-node-down.rst:146 +msgid "" +"This section covers procedures for managing your cloud after a disaster, and " +"backing up persistent storage volumes. Backups are mandatory, even outside " +"of disaster scenarios." +msgstr "" + +#: ../compute-node-down.rst:150 +msgid "" +"For a definition of a disaster recovery plan (DRP), see `http://en.wikipedia." +"org/wiki/Disaster\\_Recovery\\_Plan `_." +msgstr "" + +#: ../compute-node-down.rst:153 +msgid "" +"A disaster could happen to several components of your architecture (for " +"example, a disk crash, network loss, or a power failure). In this example, " +"the following components are configured:" +msgstr "" + +#: ../compute-node-down.rst:157 +msgid "A cloud controller (nova-api, nova-objectstore, nova-network)" +msgstr "" + +#: ../compute-node-down.rst:159 +msgid "A compute node (nova-compute)" +msgstr "" + +#: ../compute-node-down.rst:161 +msgid "" +"A storage area network (SAN) used by OpenStack Block Storage (cinder-volumes)" +msgstr "" + +#: ../compute-node-down.rst:164 +msgid "" +"The worst disaster for a cloud is power loss, which applies to all three " +"components. Before a power loss:" +msgstr "" + +#: ../compute-node-down.rst:167 +msgid "" +"Create an active iSCSI session from the SAN to the cloud controller (used " +"for the ``cinder-volumes`` LVM's VG)." +msgstr "" + +#: ../compute-node-down.rst:170 +msgid "" +"Create an active iSCSI session from the cloud controller to the compute node " +"(managed by cinder-volume)." +msgstr "" + +#: ../compute-node-down.rst:173 +msgid "" +"Create an iSCSI session for every volume (so 14 EBS volumes requires 14 " +"iSCSI sessions)." +msgstr "" + +#: ../compute-node-down.rst:176 +msgid "" +"Create iptables or ebtables rules from the cloud controller to the compute " +"node. This allows access from the cloud controller to the running instance." +msgstr "" + +#: ../compute-node-down.rst:180 +msgid "" +"Save the current state of the database, the current state of the running " +"instances, and the attached volumes (mount point, volume ID, volume status, " +"etc), at least from the cloud controller to the compute node." +msgstr "" + +#: ../compute-node-down.rst:184 +msgid "After power is recovered and all hardware components have restarted:" +msgstr "" + +#: ../compute-node-down.rst:186 +msgid "The iSCSI session from the SAN to the cloud no longer exists." +msgstr "" + +#: ../compute-node-down.rst:188 +msgid "" +"The iSCSI session from the cloud controller to the compute node no longer " +"exists." +msgstr "" + +#: ../compute-node-down.rst:191 +msgid "" +"The iptables and ebtables from the cloud controller to the compute node are " +"recreated. This is because nova-network reapplies configurations on boot." +msgstr "" + +#: ../compute-node-down.rst:195 +msgid "Instances are no longer running." +msgstr "" + +#: ../compute-node-down.rst:197 +msgid "" +"Note that instances will not be lost, because neither ``destroy`` nor " +"``terminate`` was invoked. The files for the instances will remain on the " +"compute node." +msgstr "" + +#: ../compute-node-down.rst:201 +msgid "The database has not been updated." +msgstr "" + +#: ../compute-node-down.rst:203 +msgid "**Begin recovery**" +msgstr "" + +#: ../compute-node-down.rst:207 +msgid "" +"Do not add any extra steps to this procedure, or perform the steps out of " +"order." +msgstr "" + +#: ../compute-node-down.rst:210 +msgid "" +"Check the current relationship between the volume and its instance, so that " +"you can recreate the attachment." +msgstr "" + +#: ../compute-node-down.rst:213 +msgid "" +"This information can be found using the :command:`nova volume-list` command. " +"Note that the ``nova`` client also includes the ability to get volume " +"information from OpenStack Block Storage." +msgstr "" + +#: ../compute-node-down.rst:217 +msgid "" +"Update the database to clean the stalled state. Do this for every volume, " +"using these queries:" +msgstr "" + +#: ../compute-node-down.rst:228 +msgid "Use :command:`nova volume-list` commands to list all volumes." +msgstr "" + +#: ../compute-node-down.rst:230 +msgid "" +"Restart the instances using the :command:`nova reboot INSTANCE` command." +msgstr "" + +#: ../compute-node-down.rst:234 +msgid "" +"Some instances will completely reboot and become reachable, while some might " +"stop at the plymouth stage. This is expected behavior, DO NOT reboot a " +"second time." +msgstr "" + +#: ../compute-node-down.rst:238 +msgid "" +"Instance state at this stage depends on whether you added an `/etc/fstab` " +"entry for that volume. Images built with the cloud-init package remain in a " +"``pending`` state, while others skip the missing volume and start. This step " +"is performed in order to ask Compute to reboot every instance, so that the " +"stored state is preserved. It does not matter if not all instances come up " +"successfully. For more information about cloud-init, see `help.ubuntu.com/" +"community/CloudInit/ `__." +msgstr "" + +#: ../compute-node-down.rst:247 +msgid "" +"Reattach the volumes to their respective instances, if required, using the :" +"command:`nova volume-attach` command. This example uses a file of listed " +"volumes to reattach them:" +msgstr "" + +#: ../compute-node-down.rst:264 +msgid "" +"Instances that were stopped at the plymouth stage will now automatically " +"continue booting and start normally. Instances that previously started " +"successfully will now be able to see the volume." +msgstr "" + +#: ../compute-node-down.rst:268 +msgid "Log in to the instances with SSH and reboot them." +msgstr "" + +#: ../compute-node-down.rst:270 +msgid "" +"If some services depend on the volume, or if a volume has an entry in fstab, " +"you should now be able to restart the instance. Restart directly from the " +"instance itself, not through ``nova``:" +msgstr "" + +#: ../compute-node-down.rst:278 +msgid "" +"When you are planning for and performing a disaster recovery, follow these " +"tips:" +msgstr "" + +#: ../compute-node-down.rst:281 +msgid "" +"Use the ``errors=remount`` parameter in the :file:`fstab` file to prevent " +"data corruption." +msgstr "" + +#: ../compute-node-down.rst:284 +msgid "" +"This parameter will cause the system to disable the ability to write to the " +"disk if it detects an I/O error. This configuration option should be added " +"into the cinder-volume server (the one which performs the iSCSI connection " +"to the SAN), and into the instances' :file:`fstab` files." +msgstr "" + +#: ../compute-node-down.rst:290 +msgid "" +"Do not add the entry for the SAN's disks to the cinder-volume's :file:" +"`fstab` file." +msgstr "" + +#: ../compute-node-down.rst:293 +msgid "" +"Some systems hang on that step, which means you could lose access to your " +"cloud-controller. To re-run the session manually, run this command before " +"performing the mount:" +msgstr "" + +#: ../compute-node-down.rst:301 +msgid "" +"On your instances, if you have the whole ``/home/`` directory on the disk, " +"leave a user's directory with the user's bash files and the :file:" +"`authorized_keys` file (instead of emptying the ``/home`` directory and " +"mapping the disk on it)." +msgstr "" + +#: ../compute-node-down.rst:306 +msgid "" +"This allows you to connect to the instance even without the volume attached, " +"if you allow only connections through public keys." +msgstr "" + +#: ../compute-node-down.rst:309 +msgid "" +"If you want to script the disaster recovery plan (DRP), a bash script is " +"available from `https://github.com/Razique `_ which performs the following steps:" +msgstr "" + +#: ../compute-node-down.rst:313 +msgid "An array is created for instances and their attached volumes." +msgstr "" + +#: ../compute-node-down.rst:315 +msgid "The MySQL database is updated." +msgstr "" + +#: ../compute-node-down.rst:317 +msgid "All instances are restarted with euca2ools." +msgstr "" + +#: ../compute-node-down.rst:319 +msgid "The volumes are reattached." msgstr "" #: ../compute-node-down.rst:321 @@ -2738,847 +7030,231 @@ msgid "" "An SSH connection is performed into every instance using Compute credentials." msgstr "" -#: ../compute_arch.rst:16 +#: ../compute-node-down.rst:324 msgid "" -"An ``auth manager`` provides authentication and authorization services when " -"used with the Compute system; you can also use OpenStack Identity as a " -"separate authentication service instead." +"The script includes a ``test mode``, which allows you to perform that whole " +"sequence for only one instance." msgstr "" -#: ../telemetry-alarms.rst:199 +#: ../compute-node-down.rst:327 msgid "" -"An action to invoke when the alarm state transitions to ``insufficient " -"data``." +"To reproduce the power loss, connect to the compute node which runs that " +"instance and close the iSCSI session. Do not detach the volume using the :" +"command:`nova volume-detach` command, manually close the iSCSI session. This " +"example closes an iSCSI session with the number 15:" msgstr "" -#: ../telemetry-alarms.rst:196 -msgid "An action to invoke when the alarm state transitions to ``ok``." +#: ../compute-node-down.rst:336 +msgid "Do not forget the ``-r`` flag. Otherwise, you will close all sessions." msgstr "" -#: ../database.rst:292 +#: ../compute-remote-console-access.rst:0 +msgid "**Description of SPICE configuration options**" +msgstr "" + +#: ../compute-remote-console-access.rst:0 +msgid "**Description of VNC configuration options**" +msgstr "" + +#: ../compute-remote-console-access.rst:3 +msgid "Configure remote console access" +msgstr "" + +#: ../compute-remote-console-access.rst:5 msgid "" -"An administrative user can configure various characteristics of a MongoDB " -"cluster." +"To provide a remote console or remote desktop access to guest virtual " +"machines, use VNC or SPICE HTML5 through either the OpenStack dashboard or " +"the command line. Best practice is to select one or the other to run." msgstr "" -#: ../database.rst:30 +#: ../compute-remote-console-access.rst:10 +msgid "SPICE console" +msgstr "" + +#: ../compute-remote-console-access.rst:12 msgid "" -"An administrative user can create datastores for a variety of databases." +"OpenStack Compute supports VNC consoles to guests. The VNC protocol is " +"fairly limited, lacking support for multiple monitors, bi-directional audio, " +"reliable cut-and-paste, video streaming and more. SPICE is a new protocol " +"that aims to address the limitations in VNC and provide good remote desktop " +"support." msgstr "" -#: ../networking_multi-dhcp-agents.rst:454 +#: ../compute-remote-console-access.rst:18 msgid "" -"An administrator might want to disable an agent if a system hardware or " -"software upgrade is planned. Some agents that support scheduling also " -"support disabling and enabling agents, such as L3 and DHCP agents. After the " -"agent is disabled, the scheduler does not schedule new resources to the " -"agent. After the agent is disabled, you can safely remove the agent. Remove " -"the resources on the agent before you delete the agent." +"SPICE support in OpenStack Compute shares a similar architecture to the VNC " +"implementation. The OpenStack dashboard uses a SPICE-HTML5 widget in its " +"console tab that communicates to the ``nova-spicehtml5proxy`` service by " +"using SPICE-over-websockets. The ``nova-spicehtml5proxy`` service " +"communicates directly with the hypervisor process by using SPICE." msgstr "" -#: ../telemetry-alarms.rst:305 +#: ../compute-remote-console-access.rst:24 msgid "" -"An alarm that is no longer required can be disabled so that it is no longer " -"actively evaluated:" +"VNC must be explicitly disabled to get access to the SPICE console. Set the " +"``vnc_enabled`` option to ``False`` in the ``[DEFAULT]`` section to disable " +"the VNC console." msgstr "" -#: ../identity_concepts.rst:75 +#: ../compute-remote-console-access.rst:28 msgid "" -"An alpha-numeric text string that enables access to OpenStack APIs and " -"resources. A token may be revoked at any time and is valid for a finite " -"duration. While OpenStack Identity supports token-based authentication in " -"this release, it intends to support additional protocols in the future. " -"OpenStack Identity is an integration service that does not aspire to be a " -"full-fledged identity store and management solution." +"Use the following options to configure SPICE as the console for OpenStack " +"Compute:" msgstr "" -#: ../keystone_integrate_assignment_backend_ldap.rst:137 +#: ../compute-remote-console-access.rst:35 +msgid "Spice configuration option = Default value" +msgstr "" + +#: ../compute-remote-console-access.rst:37 +msgid "``agent_enabled = True``" +msgstr "" + +#: ../compute-remote-console-access.rst:38 +msgid "(BoolOpt) Enable spice guest agent support" +msgstr "" + +#: ../compute-remote-console-access.rst:39 +msgid "``enabled = False``" +msgstr "" + +#: ../compute-remote-console-access.rst:40 +msgid "(BoolOpt) Enable spice related features" +msgstr "" + +#: ../compute-remote-console-access.rst:41 +msgid "``html5proxy_base_url = http://127.0.0.1:6082/spice_auto.html``" +msgstr "" + +#: ../compute-remote-console-access.rst:42 msgid "" -"An alternative method to determine if a project is enabled or not is to " -"check if that project is a member of the emulation group." +"(StrOpt) Location of spice HTML5 console proxy, in the form " +"\"http://127.0.0.1:6082/spice_auto.html\"" msgstr "" -#: ../keystone_integrate_identity_backend_ldap.rst:232 +#: ../compute-remote-console-access.rst:44 +msgid "``html5proxy_host = 0.0.0.0``" +msgstr "" + +#: ../compute-remote-console-access.rst:45 +#: ../compute-remote-console-access.rst:161 +msgid "(StrOpt) Host on which to listen for incoming requests" +msgstr "" + +#: ../compute-remote-console-access.rst:46 +msgid "``html5proxy_port = 6082``" +msgstr "" + +#: ../compute-remote-console-access.rst:47 +#: ../compute-remote-console-access.rst:163 +msgid "(IntOpt) Port on which to listen for incoming requests" +msgstr "" + +#: ../compute-remote-console-access.rst:48 +msgid "``keymap = en-us``" +msgstr "" + +#: ../compute-remote-console-access.rst:49 +msgid "(StrOpt) Keymap for spice" +msgstr "" + +#: ../compute-remote-console-access.rst:50 +msgid "``server_listen = 127.0.0.1``" +msgstr "" + +#: ../compute-remote-console-access.rst:51 +msgid "(StrOpt) IP address on which instance spice server should listen" +msgstr "" + +#: ../compute-remote-console-access.rst:52 +msgid "``server_proxyclient_address = 127.0.0.1``" +msgstr "" + +#: ../compute-remote-console-access.rst:53 msgid "" -"An alternative method to determine if a user is enabled or not is by " -"checking if that user is a member of the emulation group." +"(StrOpt) The address to which proxy clients (like nova-spicehtml5proxy) " +"should connect" msgstr "" -#: ../compute-node-down.rst:313 -msgid "An array is created for instances and their attached volumes." +#: ../compute-remote-console-access.rst:57 +msgid "VNC console proxy" msgstr "" -#: ../compute-security.rst:92 -msgid "An authentication blob, required by the attestation service." -msgstr "" - -#: ../networking_auth.rst:61 +#: ../compute-remote-console-access.rst:59 msgid "" -"An authorization policy can be composed by one or more rules. If more rules " -"are specified then the evaluation policy succeeds if any of the rules " -"evaluates successfully; if an API operation matches multiple policies, then " -"all the policies must evaluate successfully. Also, authorization rules are " -"recursive. Once a rule is matched, the rule(s) can be resolved to another " -"rule, until a terminal rule is reached." +"The VNC proxy is an OpenStack component that enables compute service users " +"to access their instances through VNC clients." msgstr "" -#: ../telemetry-alarms.rst:207 +#: ../compute-remote-console-access.rst:64 msgid "" -"An example of creating a combination alarm, based on the combined state of " -"two underlying alarms:" +"The web proxy console URLs do not support the websocket protocol scheme " +"(ws://) on python versions less than 2.7.4." msgstr "" -#: ../telemetry-alarms.rst:127 +#: ../compute-remote-console-access.rst:67 +msgid "The VNC console connection works as follows:" +msgstr "" + +#: ../compute-remote-console-access.rst:69 msgid "" -"An example of creating a threshold-oriented alarm, based on an upper bound " -"on the CPU utilization for a particular instance:" +"A user connects to the API and gets an ``access_url`` such as, ``http://ip:" +"port/?token=xyz``." msgstr "" -#: ../compute-images-instances.rst:155 +#: ../compute-remote-console-access.rst:72 +msgid "The user pastes the URL in a browser or uses it as a client parameter." +msgstr "" + +#: ../compute-remote-console-access.rst:75 +msgid "The browser or client connects to the proxy." +msgstr "" + +#: ../compute-remote-console-access.rst:77 msgid "" -"An image property is a key and value pair that the cloud administrator or " -"the image owner attaches to an OpenStack Image service image, as follows:" +"The proxy talks to ``nova-consoleauth`` to authorize the token for the user, " +"and maps the token to the *private* host and port of the VNC server for an " +"instance." msgstr "" -#: ../networking_introduction.rst:31 +#: ../compute-remote-console-access.rst:81 msgid "" -"An isolated L2 segment, analogous to VLAN in the physical networking world." +"The compute host specifies the address that the proxy should use to connect " +"through the :file:`nova.conf` file option, " +"``vncserver_proxyclient_address``. In this way, the VNC proxy works as a " +"bridge between the public network and private host network." msgstr "" -#: ../identity_auth_token_middleware.rst:24 -msgid "And set the following values in :file:`nova.conf` as follows:" -msgstr "" - -#: ../objectstorage_components.rst:110 +#: ../compute-remote-console-access.rst:86 msgid "" -"Another configurable value is the replica count, which indicates how many of " -"the partition-device assignments make up a single ring. For a given " -"partition number, each replica's device will not be in the same zone as any " -"other replica's device. Zones can be used to group devices based on physical " -"locations, power separations, network separations, or any other attribute " -"that would improve the availability of multiple replicas at the same time." +"The proxy initiates the connection to VNC server and continues to proxy " +"until the session ends." msgstr "" -#: ../telemetry-measurements.rst:507 +#: ../compute-remote-console-access.rst:89 msgid "" -"Another way of gathering IPMI based data is to use IPMI sensors " -"independently from the Bare metal service's components. Same meters as :ref:" -"`telemetry-bare-metal-service` could be fetched except that origin is " -"``Pollster`` instead of ``Notification``." +"The proxy also tunnels the VNC protocol over WebSockets so that the " +"``noVNC`` client can talk to VNC servers. In general, the VNC proxy:" msgstr "" -#: ../blockstorage-driver-filter-weighing.rst:210 -msgid "Any admin metadata for this volume" -msgstr "" - -#: ../identity_service_api_protection.rst:61 -msgid "Any filters specified in the query string" -msgstr "" - -#: ../blockstorage-driver-filter-weighing.rst:180 -msgid "Any metadata the volume has" -msgstr "" - -#: ../identity_service_api_protection.rst:60 -msgid "Any parameters passed into the API call" -msgstr "" - -#: ../blockstorage-driver-filter-weighing.rst:183 -msgid "Any reservations the volume has" -msgstr "" - -#: ../telemetry-alarms.rst:82 +#: ../compute-remote-console-access.rst:92 msgid "" -"Any state transition of individual alarm (to ``ok``, ``alarm``, or " -"``insufficient data``) may have one or more actions associated with it. " -"These actions effectively send a signal to a consumer that the state " -"transition has occurred, and provide some additional context. This includes " -"the new and previous states, with some reason data describing the " -"disposition with respect to the threshold, the number of datapoints involved " -"and most recent of these. State transitions are detected by the ``alarm-" -"evaluator``, whereas the ``alarm-notifier`` effects the actual notification " -"action." +"Bridges between the public network where the clients live and the private " +"network where VNC servers live." msgstr "" -#: ../keystone_certificates_for_pki.rst:225 +#: ../compute-remote-console-access.rst:95 +msgid "Mediates token authentication." +msgstr "" + +#: ../compute-remote-console-access.rst:97 msgid "" -"Append the new ``signing_cert`` to the old ``signing_cert``. Ensure the old " -"certificate is in the file first." +"Transparently deals with hypervisor-specific connection details to provide a " +"uniform client experience." msgstr "" -#: ../networking_config-agents.rst:394 -msgid "" -"Apply the settings by restarting the neutron-server and neutron-lbaas-agent " -"services." -msgstr "" - -#: ../networking_config-agents.rst:414 -msgid "" -"Apply the settings by restarting the web server. You can now view the Load " -"Balancer management options in the Project view in the dashboard." -msgstr "" - -#: ../database.rst:106 ../database.rst:144 -msgid "Argument" -msgstr "" - -#: ../telemetry-data-collection.rst:615 -msgid "Arithmetic" -msgstr "" - -#: ../networking_config-identity.rst:252 -msgid "" -"As a precaution, even when using ``metadata_proxy_shared_secret``, we " -"recommend that you do not expose metadata using the same nova-api instances " -"that are used for tenants. Instead, you should run a dedicated set of nova-" -"api instances for metadata that are available only on your management " -"network. Whether a given nova-api instance exposes metadata APIs is " -"determined by the value of ``enabled_apis`` in its :file:`nova.conf`." -msgstr "" - -#: ../blockstorage_volume_migration.rst:39 -msgid "" -"As an example, this scenario shows two LVM back-ends and migrates an " -"attached volume from one to the other. This scenario uses the third " -"migration flow." -msgstr "" - -#: ../telemetry-troubleshooting-guide.rst:28 -msgid "" -"As it can be seen in `Bug 1355809 `__, the wrong ordering of service startup can result in data " -"loss." -msgstr "" - -#: ../telemetry-data-retrieval.rst:313 -msgid "" -"As it can be seen on the output above, the result set contains samples for " -"only one instance of the two." -msgstr "" - -#: ../telemetry-data-retrieval.rst:274 -msgid "" -"As it was described above, the whole set of samples can be retrieved that " -"are stored for a meter or filtering the result set by using one of the " -"available query types. The request for all the samples of the ``cpu`` meter " -"without any additional filtering looks like the following::" -msgstr "" - -#: ../objectstorage_components.rst:130 -msgid "" -"As mentioned earlier, everything in Object Storage is stored, by default, " -"three times. Swift will place each replica \"as-uniquely-as-possible\" to " -"ensure both high availability and high durability. This means that when " -"choosing a replica location, Object Storage chooses a server in an unused " -"zone before an unused server in a zone that already has a replica of the " -"data." -msgstr "" - -# #-#-#-#-# telemetry-best-practices.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -# #-#-#-#-# telemetry-data-retrieval.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -#: ../telemetry-best-practices.rst:84 ../telemetry-data-retrieval.rst:431 -msgid "" -"As of the Liberty release, the number of items returned will be restricted " -"to the value defined by ``default_api_return_limit`` in the :file:" -"`ceilometer.conf` configuration file. Alternatively, the value can be set " -"per query by passing ``limit`` option in request." -msgstr "" - -#: ../telemetry-data-retrieval.rst:128 -msgid "" -"As opposed to the simple query, complex query is available via a separate " -"API endpoint. For more information see the `Telemetry v2 Web API Reference " -"`__." -msgstr "" - -#: ../networking_config-plugins.rst:57 -msgid "As root, run this command:" -msgstr "" - -#: ../compute-manage-the-cloud.rst:37 -msgid "As root, run:" -msgstr "" - -#: ../telemetry-data-retrieval.rst:333 -msgid "" -"As the complex query functionality provides the possibility of using complex " -"operators, it is possible to retrieve a subset of samples for a given VM " -"instance. To request for the first six samples for the ``cpu`` and ``disk." -"read.bytes`` meters, the following command should be invoked::" -msgstr "" - -#: ../telemetry-data-collection.rst:257 -msgid "" -"As the name of this agent shows, it is a central component in the Telemetry " -"architecture. This agent is responsible for polling public REST APIs to " -"retrieve additional information on OpenStack resources not already surfaced " -"via notifications, and also for polling hardware resources over SNMP." -msgstr "" - -#: ../identity_troubleshoot.rst:169 -msgid "" -"As you generate tokens, the token database table on the Identity server " -"grows. To clear the token table, an administrative user must run the " -"``keystone-manage token_flush`` command to flush the tokens. When you flush " -"tokens, expired tokens are deleted and traceability is eliminated." -msgstr "" - -#: ../networking_multi-dhcp-agents.rst:341 -msgid "Assign a network to a given DHCP agent." -msgstr "" - -#: ../identity_concepts.rst:357 -msgid "Assign a role on a domain to a group" -msgstr "" - -#: ../identity_concepts.rst:355 -msgid "Assign a role on a tenant to a group" -msgstr "" - -#: ../keystone_integrate_assignment_backend_ldap.rst:134 -msgid "Assignment attribute mapping" -msgstr "" - -#: ../networking_adv-features.rst:431 -msgid "Associates a health monitor with pool." -msgstr "" - -#: ../networking_adv-features.rst:497 -msgid "Associates a queue with a network." -msgstr "" - -#: ../networking_adv-features.rst:417 -msgid "Associates two web servers with pool." -msgstr "" - -#: ../keystone_certificates_for_pki.rst:172 -msgid "Assuming you have the following already:" -msgstr "" - -#: ../telemetry-data-collection.rst:597 -msgid "" -"At least one of the above variations should be included in the meters " -"section. Included and excluded meters cannot co-exist in the same pipeline. " -"Wildcard and included meters cannot co-exist in the same pipeline definition " -"section." -msgstr "" - -#: ../telemetry-alarms.rst:64 -msgid "" -"At one extreme you might have narrowly dimensioned alarms where this " -"selection would have only a single target (identified by resource ID). At " -"the other extreme, you could have widely dimensioned alarms where this " -"selection identifies many resources over which the statistic is aggregated. " -"For example all instances booted from a particular image or all instances " -"with matching user metadata (the latter is how the Orchestration module " -"identifies autoscaling groups)." -msgstr "" - -#: ../orchestration-auth-model.rst:48 -msgid "" -"At some later stage, Orchestration retrieves the credentials and requests " -"another token on behalf of the user. The token is not limited in scope and " -"provides access to all the roles of the stack owner." -msgstr "" - -#: ../compute_arch.rst:301 -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 "" - -#: ../database.rst:123 -msgid "" -"At this point, you do not yet have a default version, so pass in an empty " -"string." -msgstr "" - -#: ../compute-manage-volumes.rst:16 -msgid "Attach a volume to a server." -msgstr "" - -#: ../compute_arch.rst:345 -msgid "Attach volumes" -msgstr "" - -#: ../telemetry-measurements.rst:730 -msgid "Attaching the v\\ olume to an ins\\ tance" -msgstr "" - -# #-#-#-#-# networking_adv-features.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -# #-#-#-#-# networking_config-identity.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -#: ../networking_adv-features.rst:127 ../networking_adv-features.rst:690 -#: ../networking_config-identity.rst:166 -msgid "Attribute name" -msgstr "" - -#: ../identity_service_api_protection.rst:48 -msgid "Attributes from token:" -msgstr "" - -#: ../identity_service_api_protection.rst:57 -msgid "Attributes related to API call:" -msgstr "" - -#: ../identity_concepts.rst:11 -msgid "Authentication" -msgstr "" - -#: ../networking_auth.rst:5 -msgid "Authentication and authorization" -msgstr "" - -#: ../identity_auth_token_middleware.rst:2 -msgid "Authentication middleware with user name and password" -msgstr "" - -#: ../orchestration-auth-model.rst:112 -msgid "Authorization model configuration" -msgstr "" - -#: ../orchestration-auth-model.rst:22 -msgid "Authorization with OpenStack Identity trusts." -msgstr "" - -#: ../blockstorage_backup_disks.rst:213 -msgid "Automate your backups" -msgstr "" - -#: ../compute-networking-nova.rst:727 -msgid "Automatically add floating IPs" -msgstr "" - -#: ../compute_arch.rst:261 -msgid "Automatically generated UUID of the image" -msgstr "" - -#: ../compute-images-instances.rst:367 -msgid "Automatically generated UUID of the image." -msgstr "" - -#: ../blockstorage-driver-filter-weighing.rst:122 -msgid "Available properties when creating custom functions" -msgstr "" - -#: ../telemetry-measurements.rst:623 -msgid "Available swap space size" -msgstr "" - -#: ../telemetry-measurements.rst:122 ../telemetry-measurements.rst:216 -msgid "Average CPU utilisation" -msgstr "" - -#: ../telemetry-measurements.rst:304 -msgid "Average disk io\\ ps" -msgstr "" - -#: ../telemetry-measurements.rst:311 -msgid "Average disk io\\ ps per device" -msgstr "" - -#: ../telemetry-measurements.rst:301 -msgid "Average disk la\\ tency" -msgstr "" - -#: ../telemetry-measurements.rst:307 -msgid "Average disk la\\ tency per device" -msgstr "" - -#: ../telemetry-data-retrieval.rst:143 -msgid "Average of the sample volumes over each period." -msgstr "" - -#: ../telemetry-measurements.rst:168 ../telemetry-measurements.rst:268 -msgid "Average rate of incoming bytes" -msgstr "" - -#: ../telemetry-measurements.rst:184 ../telemetry-measurements.rst:278 -msgid "Average rate of incoming packets" -msgstr "" - -#: ../telemetry-measurements.rst:176 ../telemetry-measurements.rst:273 -msgid "Average rate of outgoing bytes" -msgstr "" - -#: ../telemetry-measurements.rst:193 ../telemetry-measurements.rst:283 -msgid "Average rate of outgoing packets" -msgstr "" - -#: ../telemetry-measurements.rst:133 ../telemetry-measurements.rst:236 -msgid "Average rate of read requests" -msgstr "" - -#: ../telemetry-measurements.rst:147 ../telemetry-measurements.rst:221 -#: ../telemetry-measurements.rst:254 -msgid "Average rate of reads" -msgstr "" - -#: ../telemetry-measurements.rst:140 ../telemetry-measurements.rst:245 -msgid "Average rate of write requests" -msgstr "" - -#: ../telemetry-measurements.rst:154 ../telemetry-measurements.rst:226 -#: ../telemetry-measurements.rst:263 -msgid "Average rate of writes" -msgstr "" - -#: ../telemetry-measurements.rst:144 ../telemetry-measurements.rst:151 -#: ../telemetry-measurements.rst:164 ../telemetry-measurements.rst:172 -#: ../telemetry-measurements.rst:250 ../telemetry-measurements.rst:259 -#: ../telemetry-measurements.rst:314 ../telemetry-measurements.rst:318 -#: ../telemetry-measurements.rst:324 ../telemetry-measurements.rst:329 -#: ../telemetry-measurements.rst:334 ../telemetry-measurements.rst:340 -#: ../telemetry-measurements.rst:626 ../telemetry-measurements.rst:630 -#: ../telemetry-measurements.rst:685 ../telemetry-measurements.rst:688 -#: ../telemetry-measurements.rst:759 ../telemetry-measurements.rst:765 -#: ../telemetry-measurements.rst:768 ../telemetry-measurements.rst:779 -#: ../telemetry-measurements.rst:808 ../telemetry-measurements.rst:822 -#: ../telemetry-measurements.rst:963 ../telemetry-measurements.rst:989 -#: ../telemetry-measurements.rst:992 ../telemetry-measurements.rst:1045 -#: ../telemetry-measurements.rst:1087 ../telemetry-measurements.rst:1091 -msgid "B" -msgstr "" - -#: ../telemetry-measurements.rst:147 ../telemetry-measurements.rst:154 -#: ../telemetry-measurements.rst:168 ../telemetry-measurements.rst:176 -#: ../telemetry-measurements.rst:221 ../telemetry-measurements.rst:226 -#: ../telemetry-measurements.rst:254 ../telemetry-measurements.rst:263 -#: ../telemetry-measurements.rst:268 ../telemetry-measurements.rst:273 -msgid "B/s" -msgstr "" - -#: ../blockstorage_backup_disks.rst:3 -msgid "Back up Block Storage service disks" -msgstr "" - -#: ../blockstorage_volume_backups.rst:8 -msgid "Back up and restore volumes" -msgstr "" - -#: ../compute-networking-nova.rst:772 -msgid "Bandwidth Allocation" -msgstr "" - -#: ../compute-flavors.rst:221 -msgid "Bandwidth I/O" -msgstr "" - -#: ../baremetal.rst:8 -msgid "Bare Metal" -msgstr "" - -#: ../baremetal.rst:43 -msgid "Bare Metal deployment" -msgstr "" - -# #-#-#-#-# telemetry-data-collection.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -# #-#-#-#-# telemetry-measurements.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -#: ../telemetry-data-collection.rst:69 ../telemetry-measurements.rst:468 -msgid "Bare metal service" -msgstr "" - -#: ../telemetry-best-practices.rst:14 -msgid "" -"Based on your needs, you can edit the :file:`pipeline.yaml` configuration " -"file to include a selected number of meters while disregarding the rest." -msgstr "" - -#: ../networking_use.rst:177 -msgid "Basic Compute and Networking operations" -msgstr "" - -#: ../networking_adv-features.rst:772 -msgid "Basic L3 metering operations" -msgstr "" - -#: ../networking_adv-features.rst:193 -msgid "Basic L3 operations" -msgstr "" - -#: ../networking_adv-features.rst:393 -msgid "Basic Load-Balancer-as-a-Service operations" -msgstr "" - -#: ../networking_use.rst:36 -msgid "Basic Networking operations" -msgstr "" - -#: ../networking_adv-features.rst:482 -msgid "Basic VMware NSX QoS operations" -msgstr "" - -#: ../telemetry-system-architecture.rst:150 -msgid "Basic network meters" -msgstr "" - -#: ../networking_config-agents.rst:486 -msgid "Basic operations on agents" -msgstr "" - -#: ../networking_adv-features.rst:347 -msgid "Basic security group operations" -msgstr "" - -#: ../keystone_integrate_assignment_backend_ldap.rst:15 -msgid "" -"Be aware of domain-specific back end limitations when configuring OpenStack " -"Identity. The OpenStack Identity service does not support domain-specific " -"assignment back ends. Using LDAP as an assignment back end is not " -"recommended." -msgstr "" - -#: ../compute-root-wrap-reference.rst:28 -msgid "" -"Be aware of issues with using NFS and root-owned files. The NFS share must " -"be configured with the ``no_root_squash`` option enabled, in order for " -"rootwrap to work correctly." -msgstr "" - -#: ../objectstorage_arch.rst:28 -msgid "" -"Because access servers are collocated in their own tier, you can scale out " -"read/write access regardless of the storage capacity. For example, if a " -"cluster is on the public Internet, requires SSL termination, and has a high " -"demand for data access, you can provision many access servers. However, if " -"the cluster is on a private network and used primarily for archival " -"purposes, you need fewer access servers." -msgstr "" - -#: ../objectstorage_replication.rst:5 -msgid "" -"Because each replica in Object Storage functions independently and clients " -"generally require only a simple majority of nodes to respond to consider an " -"operation successful, transient failures like network partitions can quickly " -"cause replicas to diverge. These differences are eventually reconciled by " -"asynchronous, peer-to-peer replicator processes. The replicator processes " -"traverse their local file systems and concurrently perform operations in a " -"manner that balances load across physical disks." -msgstr "" - -#: ../blockstorage_backup_disks.rst:215 -msgid "" -"Because more and more volumes might be allocated to your Block Storage " -"service, you might want to automate your backups. The `SCR_5005_V01_NUAC-" -"OPENSTACK-EBS-volumes-backup.sh`_ script assists you with this task. The " -"script performs the operations from the previous example, but also provides " -"a mail report and runs the backup based on the ``backups_retention_days`` " -"setting." -msgstr "" - -#: ../compute-configuring-migrations.rst:78 -msgid "" -"Because the Compute service does not use the libvirt live migration " -"functionality by default, guests are suspended before migration and might " -"experience several minutes of downtime. For details, see `Enabling true live " -"migration`." -msgstr "" - -#: ../blockstorage_volume_backups.rst:85 -msgid "" -"Because volume backups are dependent on the Block Storage database, you must " -"also back up your Block Storage database regularly to ensure data recovery." -msgstr "" - -#: ../compute-live-migration-usage.rst:10 -msgid "Before starting a migration, review the Configure migrations section." -msgstr "" - -#: ../blockstorage-consistency-groups.rst:21 -msgid "" -"Before using consistency groups, make sure the Block Storage driver that you " -"are running has consistency group support by reading the Block Storage " -"manual or consulting the driver maintainer. There are a small number of " -"drivers that have implemented this feature. The default LVM driver does not " -"support consistency groups yet because the consistency technology is not " -"available at the storage level." -msgstr "" - -#: ../blockstorage-consistency-groups.rst:28 -msgid "" -"Before using consistency groups, you must change policies for the " -"consistency group APIs in the :file:`/etc/cinder/policy.json` file. By " -"default, the consistency group APIs are disabled. Enable them before running " -"consistency group operations." -msgstr "" - -#: ../blockstorage_multi_backend.rst:126 -msgid "" -"Before using it, a volume type has to be declared to Block Storage. This can " -"be done by the following command::" -msgstr "" - -#: ../blockstorage_backup_disks.rst:23 -msgid "" -"Before you create the snapshot, you must have enough space to save it. As a " -"precaution, you should have at least twice as much space as the potential " -"snapshot size. If insufficient space is available, the snapshot might become " -"corrupted." -msgstr "" - -#: ../networking_arch.rst:5 -msgid "" -"Before you deploy Networking, it is useful to understand the Networking " -"services and how they interact with the OpenStack components." -msgstr "" - -#: ../networking_config-agents.rst:420 -msgid "" -"Before you install the OpenStack Networking Hyper-V L2 agent on a Hyper-V " -"compute node, ensure the compute node has been configured correctly using " -"these `instructions `__." -msgstr "" - -#: ../blockstorage-driver-filter-weighing.rst:248 -msgid "" -"Below are examples for using the filter and weigher separately, together, " -"and using driver-specific properties." -msgstr "" - -#: ../compute-flavors.rst:189 -msgid "" -"Below example sets network traffic bandwidth limits for existing flavor as " -"follow:" -msgstr "" - -#: ../blockstorage-driver-filter-weighing.rst:97 -msgid "" -"Below is a table of all the operations currently usable in custom filter and " -"goodness functions created by you:" -msgstr "" - -#: ../objectstorage_features.rst:10 -msgid "Benefits" -msgstr "" - -#: ../telemetry-measurements.rst:524 -msgid "" -"Besides generic IPMI sensor data, the following Intel Node Manager meters " -"are recorded from capable platform:" -msgstr "" - -#: ../telemetry-system-architecture.rst:60 -msgid "" -"Besides the ``ceilometer-agent-compute`` and the ``ceilometer-agent-ipmi`` " -"services, all the other services are placed on one or more controller nodes." -msgstr "" - -#: ../networking_adv-features.rst:672 -msgid "" -"Big Switch allows router rules to be added to each tenant router. These " -"rules can be used to enforce routing policies such as denying traffic " -"between subnets or traffic to external networks. By enforcing these at the " -"router level, network segmentation policies can be enforced across many VMs " -"that have differing security groups." -msgstr "" - -#: ../networking_adv-features.rst:665 -msgid "Big Switch plug-in extensions" -msgstr "" - -#: ../networking_adv-features.rst:670 -msgid "Big Switch router rules" -msgstr "" - -#: ../networking_adv-features.rst:727 -msgid "Big Switch router rules operations" -msgstr "" - -#: ../networking_config-agents.rst:168 -msgid "" -"Big Switch/Floodlight plug-in, which supports both the open source " -"`Floodlight `__ controller and " -"the proprietary Big Switch controller." -msgstr "" - -#: ../compute-live-migration-usage.rst:106 -msgid "Binary" -msgstr "" - -# #-#-#-#-# blockstorage.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -# #-#-#-#-# compute-images-instances.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -#: ../blockstorage.rst:5 ../compute-images-instances.rst:130 -msgid "Block Storage" -msgstr "" - -#: ../telemetry-data-collection.rst:930 -msgid "Block Storage audit script setup to get notifications" -msgstr "" - -#: ../compute-configuring-migrations.rst:299 -#: ../compute-configuring-migrations.rst:404 -msgid "Block migration" -msgstr "" - -#: ../compute-configuring-migrations.rst:312 -msgid "" -"Block migration is incompatible with read-only devices such as CD-ROMs and " -"`Configuration Drive (config_drive) `_." -msgstr "" - -#: ../compute-configuring-migrations.rst:416 -msgid "" -"Block migration works only with EXT local storage storage repositories, and " -"the server must not have any volumes attached." -msgstr "" - -#: ../compute_arch.rst:125 -msgid "Block storage" -msgstr "" - -#: ../networking_adv-features.rst:750 -msgid "Block traffic between two subnets while allowing everything else:" -msgstr "" - -#: ../blockstorage-driver-filter-weighing.rst:149 -msgid "Boolean signifying whether QoS is supported" -msgstr "" - -#: ../compute-flavors.rst:65 -msgid "" -"Boolean value, whether flavor is available to all users or p\\ rivate to the " -"tenant it was created in. Defaults to True." -msgstr "" - -#: ../networking_adv-features.rst:647 -msgid "Boolean; no constraint." -msgstr "" - -#: ../networking_multi-dhcp-agents.rst:383 -msgid "" -"Boot a VM on net2. Let both DHCP agents host ``net2``. Fail the agents in " -"turn to see if the VM can still get the desired IP." -msgstr "" - -#: ../networking_multi-dhcp-agents.rst:386 -msgid "Boot a VM on net2:" -msgstr "" - -#: ../blockstorage-boot-from-volume.rst:3 -msgid "Boot from volume" -msgstr "" - -#: ../networking_use.rst:259 -msgid "" -"Boots a VM that connects to all networks that are accessible to the tenant " -"who submits the request (without the ``--nic`` option)." -msgstr "" - -#: ../networking_use.rst:189 -msgid "Boots a VM with a single NIC on a selected Networking network." -msgstr "" - -#: ../networking_use.rst:250 -msgid "" -"Boots a VM with a specific IP address. Note that you cannot use the ``--num-" -"instances`` parameter in this case." -msgstr "" - -#: ../networking_use.rst:243 -msgid "Boots a VM with multiple NICs." +#: ../compute-remote-console-access.rst:105 +msgid "About nova-consoleauth" msgstr "" #: ../compute-remote-console-access.rst:107 @@ -3589,58 +7265,814 @@ msgid "" "consoleauth`` service in a cluster configuration." msgstr "" -#: ../cross_project_cors.rst:23 +#: ../compute-remote-console-access.rst:112 msgid "" -"Both the Object Storage and dashboard projects provide CORS support that is " -"not covered by this document. For those, please refer to their respective " -"implementations:" +"Do not confuse the ``nova-consoleauth`` shared service with ``nova-" +"console``, which is a XenAPI-specific service that most recent VNC proxy " +"architectures do not use." msgstr "" -#: ../telemetry-data-collection.rst:321 +#: ../compute-remote-console-access.rst:117 +msgid "Typical deployment" +msgstr "" + +#: ../compute-remote-console-access.rst:119 +msgid "A typical deployment has the following components:" +msgstr "" + +#: ../compute-remote-console-access.rst:121 +msgid "A ``nova-consoleauth`` process. Typically runs on the controller host." +msgstr "" + +#: ../compute-remote-console-access.rst:123 msgid "" -"Both the central and the compute agent can run in an HA deployment, which " -"means that multiple instances of these services can run in parallel with " -"workload partitioning among these running instances." +"One or more ``nova-novncproxy`` services. Supports browser-based noVNC " +"clients. For simple deployments, this service typically runs on the same " +"machine as ``nova-api`` because it operates as a proxy between the public " +"network and the private compute host network." msgstr "" -#: ../compute-remote-console-access.rst:92 +#: ../compute-remote-console-access.rst:128 msgid "" -"Bridges between the public network where the clients live and the private " -"network where VNC servers live." +"One or more ``nova-xvpvncproxy`` services. Supports the special Java client " +"discussed here. For simple deployments, this service typically runs on the " +"same machine as ``nova-api`` because it acts as a proxy between the public " +"network and the private compute host network." msgstr "" -#: ../objectstorage_ringbuilder.rst:152 -msgid "Build the ring" -msgstr "" - -#: ../compute_arch.rst:237 -msgid "Building blocks" -msgstr "" - -#: ../objectstorage_features.rst:35 -msgid "Built-in management utilities" -msgstr "" - -#: ../objectstorage_features.rst:25 -msgid "Built-in replication 3✕ + data redundancy (compared with 2✕ on RAID)" -msgstr "" - -#: ../blockstorage_volume_migration.rst:73 +#: ../compute-remote-console-access.rst:133 msgid "" -"But it needs to add pool name in the end. For example, " -"``server1@lvmstorage-1#zone1``." +"One or more compute hosts. These compute hosts must have correctly " +"configured options, as follows." msgstr "" -#: ../telemetry-troubleshooting-guide.rst:17 +#: ../compute-remote-console-access.rst:137 +msgid "VNC configuration options" +msgstr "" + +#: ../compute-remote-console-access.rst:139 msgid "" -"By default ``stderr`` is used as standard output for the log messages. It " -"can be changed to either a log file or syslog. The ``debug`` and ``verbose`` " -"options are also set to false in the default settings, the default log " -"levels of the corresponding modules can be found in the table referred above." +"To customize the VNC console, use the following configuration options in " +"your :file:`nova.conf`:" msgstr "" -#: ../blockstorage_image_volume_cache.rst:64 -msgid "By default they will be set to 0, which means unlimited." +#: ../compute-remote-console-access.rst:144 +msgid "" +"To support :ref:`live migration `, " +"you cannot specify a specific IP address for ``vncserver_listen``, because " +"that IP address does not exist on the destination host." +msgstr "" + +#: ../compute-remote-console-access.rst:154 +msgid "**[DEFAULT]**" +msgstr "" + +#: ../compute-remote-console-access.rst:156 +msgid "``daemon = False``" +msgstr "" + +#: ../compute-remote-console-access.rst:157 +msgid "(BoolOpt) Become a daemon (background process)" +msgstr "" + +#: ../compute-remote-console-access.rst:158 +msgid "``key = None``" +msgstr "" + +#: ../compute-remote-console-access.rst:159 +msgid "(StrOpt) SSL key file (if separate from cert)" +msgstr "" + +#: ../compute-remote-console-access.rst:160 +msgid "``novncproxy_host = 0.0.0.0``" +msgstr "" + +#: ../compute-remote-console-access.rst:162 +msgid "``novncproxy_port = 6080``" +msgstr "" + +#: ../compute-remote-console-access.rst:164 +msgid "``record = False``" +msgstr "" + +#: ../compute-remote-console-access.rst:165 +msgid "(BoolOpt) Record sessions to FILE.[session_number]" +msgstr "" + +#: ../compute-remote-console-access.rst:166 +msgid "``source_is_ipv6 = False``" +msgstr "" + +#: ../compute-remote-console-access.rst:167 +msgid "(BoolOpt) Source is ipv6" +msgstr "" + +#: ../compute-remote-console-access.rst:168 +msgid "``ssl_only = False``" +msgstr "" + +#: ../compute-remote-console-access.rst:169 +msgid "(BoolOpt) Disallow non-encrypted connections" +msgstr "" + +#: ../compute-remote-console-access.rst:170 +msgid "``web = /usr/share/spice-html5``" +msgstr "" + +#: ../compute-remote-console-access.rst:171 +msgid "(StrOpt) Run webserver on same port. Serve files from DIR." +msgstr "" + +#: ../compute-remote-console-access.rst:172 +msgid "**[vmware]**" +msgstr "" + +#: ../compute-remote-console-access.rst:174 +msgid "``vnc_port = 5900``" +msgstr "" + +#: ../compute-remote-console-access.rst:175 +msgid "(IntOpt) VNC starting port" +msgstr "" + +#: ../compute-remote-console-access.rst:176 +msgid "``vnc_port_total = 10000``" +msgstr "" + +#: ../compute-remote-console-access.rst:177 +msgid "vnc_port_total = 10000" +msgstr "" + +#: ../compute-remote-console-access.rst:178 +msgid "**[vnc]**" +msgstr "" + +#: ../compute-remote-console-access.rst:180 +msgid "enabled = True" +msgstr "" + +#: ../compute-remote-console-access.rst:181 +msgid "(BoolOpt) Enable VNC related features" +msgstr "" + +#: ../compute-remote-console-access.rst:182 +msgid "novncproxy_base_url = http://127.0.0.1:6080/vnc_auto.html" +msgstr "" + +#: ../compute-remote-console-access.rst:183 +msgid "" +"(StrOpt) Location of VNC console proxy, in the form \"http://127.0.0.1:6080/" +"vnc_auto.html\"" +msgstr "" + +#: ../compute-remote-console-access.rst:185 +msgid "vncserver_listen = 127.0.0.1" +msgstr "" + +#: ../compute-remote-console-access.rst:186 +msgid "(StrOpt) IP address on which instance vncservers should listen" +msgstr "" + +#: ../compute-remote-console-access.rst:187 +msgid "vncserver_proxyclient_address = 127.0.0.1" +msgstr "" + +#: ../compute-remote-console-access.rst:188 +msgid "" +"(StrOpt) The address to which proxy clients (like nova-xvpvncproxy) should " +"connect" +msgstr "" + +#: ../compute-remote-console-access.rst:190 +msgid "xvpvncproxy_base_url = http://127.0.0.1:6081/console" +msgstr "" + +#: ../compute-remote-console-access.rst:191 +msgid "" +"(StrOpt) Location of nova xvp VNC console proxy, in the form " +"\"http://127.0.0.1:6081/console\"" +msgstr "" + +#: ../compute-remote-console-access.rst:196 +msgid "" +"The ``vncserver_proxyclient_address`` defaults to ``127.0.0.1``, which is " +"the address of the compute host that Compute instructs proxies to use when " +"connecting to instance servers." +msgstr "" + +#: ../compute-remote-console-access.rst:200 +msgid "For all-in-one XenServer domU deployments, set this to ``169.254.0.1.``" +msgstr "" + +#: ../compute-remote-console-access.rst:203 +msgid "" +"For multi-host XenServer domU deployments, set to a ``dom0 management IP`` " +"on the same network as the proxies." +msgstr "" + +#: ../compute-remote-console-access.rst:206 +msgid "" +"For multi-host libvirt deployments, set to a host management IP on the same " +"network as the proxies." +msgstr "" + +#: ../compute-remote-console-access.rst:210 +msgid "nova-novncproxy (noVNC)" +msgstr "" + +#: ../compute-remote-console-access.rst:212 +msgid "" +"You must install the noVNC package, which contains the ``nova-novncproxy`` " +"service. As root, run the following command:" +msgstr "" + +#: ../compute-remote-console-access.rst:219 +msgid "The service starts automatically on installation." +msgstr "" + +#: ../compute-remote-console-access.rst:221 +msgid "To restart the service, run:" +msgstr "" + +#: ../compute-remote-console-access.rst:227 +msgid "" +"The configuration option parameter should point to your :file:`nova.conf` " +"file, which includes the message queue server address and credentials." +msgstr "" + +#: ../compute-remote-console-access.rst:230 +msgid "By default, ``nova-novncproxy`` binds on ``0.0.0.0:6080``." +msgstr "" + +#: ../compute-remote-console-access.rst:232 +msgid "" +"To connect the service to your Compute deployment, add the following " +"configuration options to your :file:`nova.conf`:" +msgstr "" + +#: ../compute-remote-console-access.rst:235 +msgid "``vncserver_listen=0.0.0.0``" +msgstr "" + +#: ../compute-remote-console-access.rst:237 +msgid "" +"Specifies the address on which the VNC service should bind. Make sure it is " +"assigned one of the compute node interfaces. This address is the one used by " +"your domain file." +msgstr "" + +#: ../compute-remote-console-access.rst:247 +msgid "To use live migration, use the 0.0.0.0 address." +msgstr "" + +#: ../compute-remote-console-access.rst:249 +msgid "``vncserver_proxyclient_address=127.0.0.1``" +msgstr "" + +#: ../compute-remote-console-access.rst:251 +msgid "" +"The address of the compute host that Compute instructs proxies to use when " +"connecting to instance ``vncservers``." +msgstr "" + +#: ../compute-remote-console-access.rst:255 +msgid "Frequently asked questions about VNC access to virtual machines" +msgstr "" + +#: ../compute-remote-console-access.rst:257 +msgid "" +"**Q: What is the difference between ``nova-xvpvncproxy`` and ``nova-" +"novncproxy``?**" +msgstr "" + +#: ../compute-remote-console-access.rst:260 +msgid "" +"A: ``nova-xvpvncproxy``, which ships with OpenStack Compute, is a proxy that " +"supports a simple Java client. nova-novncproxy uses noVNC to provide VNC " +"support through a web browser." +msgstr "" + +#: ../compute-remote-console-access.rst:264 +msgid "" +"**Q: I want VNC support in the OpenStack dashboard. What services do I need?" +"**" +msgstr "" + +#: ../compute-remote-console-access.rst:267 +msgid "" +"A: You need ``nova-novncproxy``, ``nova-consoleauth``, and correctly " +"configured compute hosts." +msgstr "" + +#: ../compute-remote-console-access.rst:270 +msgid "" +"**Q: When I use ``nova get-vnc-console`` or click on the VNC tab of the " +"OpenStack dashboard, it hangs. Why?**" +msgstr "" + +#: ../compute-remote-console-access.rst:273 +msgid "" +"A: Make sure you are running ``nova-consoleauth`` (in addition to ``nova-" +"novncproxy``). The proxies rely on ``nova-consoleauth`` to validate tokens, " +"and waits for a reply from them until a timeout is reached." +msgstr "" + +#: ../compute-remote-console-access.rst:277 +msgid "" +"**Q: My VNC proxy worked fine during my all-in-one test, but now it doesn't " +"work on multi host. Why?**" +msgstr "" + +#: ../compute-remote-console-access.rst:280 +msgid "" +"A: The default options work for an all-in-one install, but changes must be " +"made on your compute hosts once you start to build a cluster. As an example, " +"suppose you have two servers:" +msgstr "" + +#: ../compute-remote-console-access.rst:289 +msgid "" +"Your :file:`nova-compute` configuration file must set the following values:" +msgstr "" + +#: ../compute-remote-console-access.rst:304 +msgid "" +"``novncproxy_base_url`` and ``xvpvncproxy_base_url`` use a public IP; this " +"is the URL that is ultimately returned to clients, which generally do not " +"have access to your private network. Your PROXYSERVER must be able to reach " +"``vncserver_proxyclient_address``, because that is the address over which " +"the VNC connection is proxied." +msgstr "" + +#: ../compute-remote-console-access.rst:310 +msgid "" +"**Q: My noVNC does not work with recent versions of web browsers. Why?**" +msgstr "" + +#: ../compute-remote-console-access.rst:312 +msgid "" +"A: Make sure you have installed ``python-numpy``, which is required to " +"support a newer version of the WebSocket protocol (HyBi-07+)." +msgstr "" + +#: ../compute-remote-console-access.rst:315 +msgid "" +"**Q: How do I adjust the dimensions of the VNC window image in the OpenStack " +"dashboard?**" +msgstr "" + +#: ../compute-remote-console-access.rst:318 +msgid "" +"A: These values are hard-coded in a Django HTML template. To alter them, " +"edit the :file:`_detail_vnc.html` template file. The location of this file " +"varies based on Linux distribution. On Ubuntu 14.04, the file is at ``/usr/" +"share/pyshared/horizon/dashboards/nova/instances/templates/instances/" +"_detail_vnc.html``." +msgstr "" + +#: ../compute-remote-console-access.rst:324 +msgid "Modify the ``width`` and ``height`` options, as follows:" +msgstr "" + +#: ../compute-remote-console-access.rst:330 +msgid "" +"**Q: My noVNC connections failed with ValidationError: Origin header " +"protocol does not match. Why?**" +msgstr "" + +#: ../compute-remote-console-access.rst:333 +msgid "" +"A: Make sure the ``base_url`` match your TLS setting. If you are using https " +"console connections, make sure that the value of ``novncproxy_base_url`` is " +"set explicitly where the ``nova-novncproxy`` service is running." +msgstr "" + +#: ../compute-root-wrap-reference.rst:0 +msgid "**Filters configuration options**" +msgstr "" + +#: ../compute-root-wrap-reference.rst:0 +msgid "**rootwrap.conf configuration options**" +msgstr "" + +#: ../compute-root-wrap-reference.rst:5 +msgid "Secure with rootwrap" +msgstr "" + +#: ../compute-root-wrap-reference.rst:7 +msgid "" +"Rootwrap allows unprivileged users to safely run Compute actions as the root " +"user. Compute previously used :command:`sudo` for this purpose, but this was " +"difficult to maintain, and did not allow advanced filters. The :command:" +"`rootwrap` command replaces :command:`sudo` for Compute." +msgstr "" + +#: ../compute-root-wrap-reference.rst:12 +msgid "" +"To use rootwrap, prefix the Compute command with :command:`nova-rootwrap`. " +"For example:" +msgstr "" + +#: ../compute-root-wrap-reference.rst:19 +msgid "" +"A generic ``sudoers`` entry lets the Compute user run :command:`nova-" +"rootwrap` as root. The :command:`nova-rootwrap` code looks for filter " +"definition directories in its configuration file, and loads command filters " +"from them. It then checks if the command requested by Compute matches one of " +"those filters and, if so, executes the command (as root). If no filter " +"matches, it denies the request." +msgstr "" + +#: ../compute-root-wrap-reference.rst:28 +msgid "" +"Be aware of issues with using NFS and root-owned files. The NFS share must " +"be configured with the ``no_root_squash`` option enabled, in order for " +"rootwrap to work correctly." +msgstr "" + +#: ../compute-root-wrap-reference.rst:32 +msgid "" +"Rootwrap is fully controlled by the root user. The root user owns the " +"sudoers entry which allows Compute to run a specific rootwrap executable as " +"root, and only with a specific configuration file (which should also be " +"owned by root). The :command:`nova-rootwrap` command imports the Python " +"modules it needs from a cleaned, system-default PYTHONPATH. The root-owned " +"configuration file points to root-owned filter definition directories, which " +"contain root-owned filters definition files. This chain ensures that the " +"Compute user itself is not in control of the configuration or modules used " +"by the :command:`nova-rootwrap` executable." +msgstr "" + +#: ../compute-root-wrap-reference.rst:44 +msgid "" +"Rootwrap is configured using the :file:`rootwrap.conf` file. Because it's in " +"the trusted security path, it must be owned and writable by only the root " +"user. The file's location is specified in both the sudoers entry and in the :" +"file:`nova.conf` configuration file with the ``rootwrap_config=entry`` " +"parameter." +msgstr "" + +#: ../compute-root-wrap-reference.rst:50 +msgid "" +"The :file:`rootwrap.conf` file uses an INI file format with these sections " +"and parameters:" +msgstr "" + +#: ../compute-root-wrap-reference.rst:56 ../compute-root-wrap-reference.rst:95 +msgid "Configuration option=Default value" +msgstr "" + +#: ../compute-root-wrap-reference.rst:57 ../compute-root-wrap-reference.rst:96 +msgid "(Type) Description" +msgstr "" + +#: ../compute-root-wrap-reference.rst:58 +msgid "[DEFAULT] filters\\_path=/etc/nova/rootwrap.d,/usr/share/nova/rootwrap" +msgstr "" + +#: ../compute-root-wrap-reference.rst:60 +msgid "" +"(ListOpt) Comma-separated list of directories containing filter definition " +"files. Defines where rootwrap filters are stored. Directories defined on " +"this line should all exist, and be owned and writable only by the root user." +msgstr "" + +#: ../compute-root-wrap-reference.rst:67 +msgid "" +"If the root wrapper is not performing correctly, you can add a workaround " +"option into the :file:`nova.conf` configuration file. This workaround re-" +"configures the root wrapper configuration to fall back to running commands " +"as sudo, and is a Kilo release feature." +msgstr "" + +#: ../compute-root-wrap-reference.rst:72 +msgid "" +"Including this workaround in your configuration file safeguards your " +"environment from issues that can impair root wrapper performance. Tool " +"changes that have impacted `Python Build Reasonableness (PBR) `__ for example, are a known issue " +"that affects root wrapper performance." +msgstr "" + +#: ../compute-root-wrap-reference.rst:78 +msgid "" +"To set up this workaround, configure the ``disable_rootwrap`` option in the " +"``[workaround]`` section of the :file:`nova.conf` configuration file." +msgstr "" + +#: ../compute-root-wrap-reference.rst:81 +msgid "" +"The filters definition files contain lists of filters that rootwrap will use " +"to allow or deny a specific command. They are generally suffixed by ``." +"filters`` . Since they are in the trusted security path, they need to be " +"owned and writable only by the root user. Their location is specified in " +"the :file:`rootwrap.conf` file." +msgstr "" + +#: ../compute-root-wrap-reference.rst:87 +msgid "" +"Filter definition files use an INI file format with a ``[Filters]`` section " +"and several lines, each with a unique parameter name, which should be " +"different for each filter you define:" +msgstr "" + +#: ../compute-root-wrap-reference.rst:97 +msgid "[Filters] filter\\_name=kpartx: CommandFilter, /sbin/kpartx, root" +msgstr "" + +#: ../compute-root-wrap-reference.rst:99 +msgid "" +"(ListOpt) Comma-separated list containing the filter class to use, followed " +"by the Filter arguments (which vary depending on the Filter class selected)." +msgstr "" + +#: ../compute-security.rst:0 +msgid "**Description of trusted computing configuration options**" +msgstr "" + +#: ../compute-security.rst:5 +msgid "Security hardening" +msgstr "" + +#: ../compute-security.rst:7 +msgid "" +"OpenStack Compute can be integrated with various third-party technologies to " +"increase security. For more information, see the `OpenStack Security Guide " +"`_." +msgstr "" + +#: ../compute-security.rst:12 +msgid "Trusted compute pools" +msgstr "" + +#: ../compute-security.rst:14 +msgid "" +"Administrators can designate a group of compute hosts as trusted using " +"trusted compute pools. The trusted hosts use hardware-based security " +"features, such as the Intel Trusted Execution Technology (TXT), to provide " +"an additional level of security. Combined with an external stand-alone, web-" +"based remote attestation server, cloud providers can ensure that the compute " +"node runs only software with verified measurements and can ensure a secure " +"cloud stack." +msgstr "" + +#: ../compute-security.rst:22 +msgid "" +"Trusted compute pools provide the ability for cloud subscribers to request " +"services run only on verified compute nodes." +msgstr "" + +#: ../compute-security.rst:25 +msgid "The remote attestation server performs node verification like this:" +msgstr "" + +#: ../compute-security.rst:27 +msgid "Compute nodes boot with Intel TXT technology enabled." +msgstr "" + +#: ../compute-security.rst:29 +msgid "The compute node BIOS, hypervisor, and operating system are measured." +msgstr "" + +#: ../compute-security.rst:31 +msgid "" +"When the attestation server challenges the compute node, the measured data " +"is sent to the attestation server." +msgstr "" + +#: ../compute-security.rst:34 +msgid "" +"The attestation server verifies the measurements against a known good " +"database to determine node trustworthiness." +msgstr "" + +#: ../compute-security.rst:37 +msgid "" +"A description of how to set up an attestation service is beyond the scope of " +"this document. For an open source project that you can use to implement an " +"attestation service, see the `Open Attestation `__ project." +msgstr "" + +# #-#-#-#-# compute-security.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +# #-#-#-#-# networking_multi-dhcp-agents.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +#: ../compute-security.rst:43 ../networking_multi-dhcp-agents.rst:31 +msgid "|image0|" +msgstr "" + +#: ../compute-security.rst:45 +msgid "**Configuring Compute to use trusted compute pools**" +msgstr "" + +#: ../compute-security.rst:47 +msgid "" +"Enable scheduling support for trusted compute pools by adding these lines to " +"the ``DEFAULT`` section of the :file:`/etc/nova/nova.conf` file:" +msgstr "" + +#: ../compute-security.rst:57 +msgid "" +"Specify the connection information for your attestation service by adding " +"these lines to the ``trusted_computing`` section of the :file:`/etc/nova/" +"nova.conf` file:" +msgstr "" + +# #-#-#-#-# compute-security.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +# #-#-#-#-# database.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +#: ../compute-security.rst:76 ../database.rst:108 ../database.rst:146 +msgid "In this example:" +msgstr "" + +#: ../compute-security.rst:79 +msgid "Host name or IP address of the host that runs the attestation service" +msgstr "" + +#: ../compute-security.rst:80 +msgid "server" +msgstr "" + +#: ../compute-security.rst:83 +msgid "HTTPS port for the attestation service" +msgstr "" + +# #-#-#-#-# compute-security.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +# #-#-#-#-# telemetry-measurements.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +#: ../compute-security.rst:83 ../telemetry-measurements.rst:934 +#: ../telemetry-measurements.rst:937 ../telemetry-measurements.rst:940 +#: ../telemetry-measurements.rst:980 +msgid "port" +msgstr "" + +#: ../compute-security.rst:86 +msgid "Certificate file used to verify the attestation server's identity" +msgstr "" + +#: ../compute-security.rst:86 +msgid "server_ca_file" +msgstr "" + +#: ../compute-security.rst:89 +msgid "The attestation service's URL path" +msgstr "" + +#: ../compute-security.rst:89 +msgid "api_url" +msgstr "" + +#: ../compute-security.rst:92 +msgid "An authentication blob, required by the attestation service." +msgstr "" + +#: ../compute-security.rst:92 +msgid "auth_blob" +msgstr "" + +#: ../compute-security.rst:94 +msgid "" +"Save the file, and restart the nova-compute and nova-scheduler services to " +"pick up the changes." +msgstr "" + +#: ../compute-security.rst:97 +msgid "" +"To customize the trusted compute pools, use these configuration option " +"settings:" +msgstr "" + +#: ../compute-security.rst:105 +msgid "[trusted_computing]" +msgstr "" + +#: ../compute-security.rst:107 +msgid "attestation_api_url = /OpenAttestationWebServices/V1.0" +msgstr "" + +#: ../compute-security.rst:108 +msgid "(StrOpt) Attestation web API URL" +msgstr "" + +#: ../compute-security.rst:109 +msgid "attestation_auth_blob = None" +msgstr "" + +#: ../compute-security.rst:110 +msgid "(StrOpt) Attestation authorization blob - must change" +msgstr "" + +#: ../compute-security.rst:111 +msgid "attestation_auth_timeout = 60" +msgstr "" + +#: ../compute-security.rst:112 +msgid "(IntOpt) Attestation status cache valid period length" +msgstr "" + +#: ../compute-security.rst:113 +msgid "attestation_insecure_ssl = False" +msgstr "" + +#: ../compute-security.rst:114 +msgid "(BoolOpt) Disable SSL cert verification for Attestation service" +msgstr "" + +#: ../compute-security.rst:115 +msgid "attestation_port = 8443" +msgstr "" + +#: ../compute-security.rst:116 +msgid "(StrOpt) Attestation server port" +msgstr "" + +#: ../compute-security.rst:117 +msgid "attestation_server = None" +msgstr "" + +#: ../compute-security.rst:118 +msgid "(StrOpt) Attestation server HTTP" +msgstr "" + +#: ../compute-security.rst:119 +msgid "attestation_server_ca_file = None" +msgstr "" + +#: ../compute-security.rst:120 +msgid "(StrOpt) Attestation server Cert file for Identity verification" +msgstr "" + +#: ../compute-security.rst:122 +msgid "**Specifying trusted flavors**" +msgstr "" + +#: ../compute-security.rst:124 +msgid "" +"Flavors can be designated as trusted using the ``nova flavor-key set`` " +"command. In this example, the ``m1.tiny`` flavor is being set as trusted:" +msgstr "" + +#: ../compute-security.rst:132 +msgid "" +"You can request that your instance is run on a trusted host by specifying a " +"trusted flavor when booting the instance:" +msgstr "" + +#: ../compute-security.rst:139 +msgid "|Trusted compute pool|" +msgstr "" + +#: ../compute-security.rst:146 +msgid "Encrypt Compute metadata traffic" +msgstr "" + +#: ../compute-security.rst:148 +msgid "**Enabling SSL encryption**" +msgstr "" + +#: ../compute-security.rst:150 +msgid "" +"OpenStack supports encrypting Compute metadata traffic with HTTPS. Enable " +"SSL encryption in the :file:`metadata_agent.ini` file." +msgstr "" + +#: ../compute-security.rst:153 +msgid "Enable the HTTPS protocol::" +msgstr "" + +#: ../compute-security.rst:157 +msgid "" +"Determine whether insecure SSL connections are accepted for Compute metadata " +"server requests. The default value is ``False``::" +msgstr "" + +#: ../compute-security.rst:162 +msgid "Specify the path to the client certificate::" +msgstr "" + +#: ../compute-security.rst:166 +msgid "Specify the path to the private key::" +msgstr "" + +#: ../compute-service-groups.rst:5 +msgid "Configure Compute service groups" +msgstr "" + +#: ../compute-service-groups.rst:7 +msgid "" +"The Compute service must know the status of each compute node to effectively " +"manage and use them. This can include events like a user launching a new VM, " +"the scheduler sending a request to a live node, or a query to the " +"ServiceGroup API to determine if a node is live." +msgstr "" + +#: ../compute-service-groups.rst:12 +msgid "" +"When a compute worker running the nova-compute daemon starts, it calls the " +"join API to join the compute group. Any service (such as the scheduler) can " +"query the group's membership and the status of its nodes. Internally, the " +"ServiceGroup client driver automatically updates the compute worker status." +msgstr "" + +#: ../compute-service-groups.rst:21 +msgid "Database ServiceGroup driver" msgstr "" #: ../compute-service-groups.rst:23 @@ -3651,556 +8083,233 @@ msgid "" "timeout (``service_down_time``) to determine if a node is dead." msgstr "" -#: ../telemetry-best-practices.rst:18 +#: ../compute-service-groups.rst:29 msgid "" -"By default, Telemetry service polls the service APIs every 10 minutes. You " -"can change the polling interval on a per meter basis by editing the :file:" -"`pipeline.yaml` configuration file." +"The driver has limitations, which can be problematic depending on your " +"environment. If a lot of compute worker nodes need to be checked, the " +"database can be put under heavy load, which can cause the timeout to " +"trigger, and a live node could incorrectly be considered dead. By default, " +"the timeout is 60 seconds. Reducing the timeout value can help in this " +"situation, but you must also make the database update more frequently, which " +"again increases the database workload." msgstr "" -#: ../compute-remote-console-access.rst:230 -msgid "By default, ``nova-novncproxy`` binds on ``0.0.0.0:6080``." -msgstr "" - -#: ../compute-images-instances.rst:399 +#: ../compute-service-groups.rst:37 msgid "" -"By default, administrative users can configure the flavors. You can change " -"this behavior by redefining the access controls for ``compute_extension:" -"flavormanage`` in :file:`/etc/nova/policy.json` on the ``compute-api`` " -"server." +"The database contains data that is both transient (such as whether the node " +"is alive) and persistent (such as entries for VM owners). With the " +"ServiceGroup abstraction, Compute can treat each type separately." msgstr "" -#: ../telemetry-alarms.rst:319 -msgid "By default, alarm history is retained for deleted alarms." +#: ../compute-service-groups.rst:44 +msgid "ZooKeeper ServiceGroup driver" msgstr "" -#: ../compute-images-instances.rst:283 -msgid "By default, property protections are not enforced." -msgstr "" - -#: ../blockstorage_volume_backed_image.rst:44 +#: ../compute-service-groups.rst:46 msgid "" -"By default, the :command:`upload-to-image` command creates the Image-Volume " -"in the current tenant. To store the Image-Volume into the internal tenant, " -"set the following options in each back-end section of the :file:`cinder." -"conf` file::" +"The ZooKeeper ServiceGroup driver works by using ZooKeeper ephemeral nodes. " +"ZooKeeper, unlike databases, is a distributed system, with its load divided " +"among several servers. On a compute worker node, the driver can establish a " +"ZooKeeper session, then create an ephemeral znode in the group directory. " +"Ephemeral znodes have the same lifespan as the session. If the worker node " +"or the nova-compute daemon crashes, or a network partition is in place " +"between the worker and the ZooKeeper server quorums, the ephemeral znodes " +"are removed automatically. The driver can be given group membership by " +"running the :command:`ls` command in the group directory." msgstr "" -#: ../blockstorage-api-throughput.rst:5 +#: ../compute-service-groups.rst:57 msgid "" -"By default, the Block Storage API service runs in one process. This limits " -"the number of API requests that the Block Storage service can process at any " -"given time. In a production environment, you should increase the Block " -"Storage API throughput by allowing the Block Storage API service to run in " -"as many processes as the machine capacity allows." +"The ZooKeeper driver requires the ZooKeeper servers and client libraries. " +"Setting up ZooKeeper servers is outside the scope of this guide (for more " +"information, see `Apache Zookeeper `_). These " +"client-side Python libraries must be installed on every compute node:" msgstr "" -#: ../compute-admin-password-injection.rst:15 +#: ../compute-service-groups.rst:63 +msgid "**python-zookeeper**" +msgstr "" + +#: ../compute-service-groups.rst:63 +msgid "The official Zookeeper Python binding" +msgstr "" + +#: ../compute-service-groups.rst:66 +msgid "**evzookeeper**" +msgstr "" + +#: ../compute-service-groups.rst:66 +msgid "This library makes the binding work with the eventlet threading model." +msgstr "" + +#: ../compute-service-groups.rst:68 msgid "" -"By default, the dashboard will display the ``admin`` password and allow the " -"user to modify it." +"This example assumes the ZooKeeper server addresses and ports are " +"``192.168.2.1:2181``, ``192.168.2.2:2181``, and ``192.168.2.3:2181``." msgstr "" -#: ../blockstorage_volume_backups.rst:102 -msgid "By default, the swift object store is used for the backup repository." -msgstr "" - -#: ../objectstorage-admin.rst:5 +#: ../compute-service-groups.rst:71 msgid "" -"By understanding Object Storage concepts, you can better monitor and " -"administer your storage solution. The majority of the administration " -"information is maintained in developer documentation at `docs.openstack.org/" -"developer/swift/ `__." +"These values in the :file:`/etc/nova/nova.conf` file are required on every " +"node for the ZooKeeper driver:" msgstr "" -#: ../cross_project_cors.rst:151 +#: ../compute-service-groups.rst:82 msgid "" -"By using ``curl`` or a similar tool, you can trigger a CORS response with a " -"properly constructed HTTP request. An example request and response might " -"look like this." +"For Compute Service groups customization options, see the `OpenStack " +"Configuration Reference Guide `_." msgstr "" -#: ../telemetry-measurements.rst:1045 -msgid "Bytes received" +#: ../compute-service-groups.rst:89 +msgid "Memcache ServiceGroup driver" msgstr "" -#: ../telemetry-measurements.rst:626 -msgid "Bytes received by network inte\\ rface" -msgstr "" - -#: ../telemetry-measurements.rst:989 -msgid "Bytes received on port" -msgstr "" - -#: ../telemetry-measurements.rst:630 -msgid "Bytes sent by n\\ etwork interface" -msgstr "" - -#: ../telemetry-measurements.rst:963 -msgid "Bytes through t\\ his l3 metering label" -msgstr "" - -#: ../telemetry-measurements.rst:992 -msgid "Bytes transmitt\\ ed on port" -msgstr "" - -#: ../telemetry-measurements.rst:494 ../telemetry-measurements.rst:535 -#: ../telemetry-measurements.rst:541 ../telemetry-measurements.rst:544 -msgid "C" -msgstr "" - -#: ../telemetry-measurements.rst:547 -msgid "CFM" -msgstr "" - -#: ../blockstorage_glusterfs_backend.rst:58 -msgid "CINDER_GID is the GID of the ``cinder`` user." -msgstr "" - -#: ../blockstorage_glusterfs_backend.rst:56 -msgid "CINDER_UID is the UID of the ``cinder`` user." -msgstr "" - -#: ../cross_project_cors.rst:113 +#: ../compute-service-groups.rst:91 msgid "" -"CORS is very easy to get wrong, as even one incorrect property will violate " -"the prescribed contract. Here are some steps you can take to troubleshoot " -"your configuration." +"The memcache ServiceGroup driver uses memcached, a distributed memory object " +"caching system that is used to increase site performance. For more details, " +"see `memcached.org `_." msgstr "" -#: ../cross_project_cors.rst:100 +#: ../compute-service-groups.rst:95 msgid "" -"CORS specifies a wildcard character `*`, which permits access to all user " -"agents, regardless of domain, protocol, or host. While there are valid use " -"cases for this approach, it also permits a malicious actor to create a " -"convincing facsimile of a user interface, and trick users into revealing " -"authentication credentials. Please carefully evaluate your use case and the " -"relevant documentation for any risk to your organization." +"To use the memcache driver, you must install memcached. You might already " +"have it installed, as the same driver is also used for the OpenStack Object " +"Storage and OpenStack dashboard. If you need to install memcached, see the " +"instructions in the `OpenStack Installation Guide `_." msgstr "" -#: ../telemetry-measurements.rst:557 -msgid "CPU CUPS utiliz\\ ation of the system" -msgstr "" - -#: ../telemetry-measurements.rst:458 -msgid "CPU I/O wait percentage" -msgstr "" - -#: ../telemetry-measurements.rst:446 -msgid "CPU I/O wait time" -msgstr "" - -#: ../telemetry-measurements.rst:434 -msgid "CPU frequency" -msgstr "" - -#: ../telemetry-measurements.rst:655 -msgid "CPU idle percen\\ tage" -msgstr "" - -#: ../telemetry-measurements.rst:452 -msgid "CPU idle percentage" -msgstr "" - -#: ../telemetry-measurements.rst:440 -msgid "CPU idle time" -msgstr "" - -#: ../telemetry-measurements.rst:449 -msgid "CPU kernel percentage" -msgstr "" - -#: ../telemetry-measurements.rst:437 -msgid "CPU kernel time" -msgstr "" - -#: ../compute-flavors.rst:135 -msgid "CPU limits" -msgstr "" - -#: ../telemetry-measurements.rst:593 -msgid "CPU load in the past 1 minute" -msgstr "" - -#: ../telemetry-measurements.rst:599 -msgid "CPU load in the past 10 minutes" -msgstr "" - -#: ../telemetry-measurements.rst:596 -msgid "CPU load in the past 5 minutes" -msgstr "" - -#: ../telemetry-measurements.rst:119 -msgid "CPU time used" -msgstr "" - -#: ../telemetry-measurements.rst:355 -msgid "CPU time used s\\ ince previous d\\ atapoint" -msgstr "" - -#: ../compute-flavors.rst:296 -msgid "CPU toplogy" -msgstr "" - -#: ../telemetry-measurements.rst:455 -msgid "CPU user mode percentage" -msgstr "" - -#: ../telemetry-measurements.rst:443 -msgid "CPU user mode time" -msgstr "" - -#: ../telemetry-measurements.rst:461 -msgid "CPU utilisation" -msgstr "" - -#: ../telemetry-measurements.rst:1015 -msgid "CRC errors rece\\ ived on port" -msgstr "" - -#: ../telemetry-measurements.rst:552 -msgid "CUPS" -msgstr "" - -#: ../telemetry-measurements.rst:552 -msgid "CUPS(Compute Us\\ age Per Second) index data of the system" -msgstr "" - -#: ../blockstorage_image_volume_cache.rst:75 +#: ../compute-service-groups.rst:100 msgid "" -"Cache actions will trigger Telemetry messages. There are several that will " -"be sent." +"These values in the :file:`/etc/nova/nova.conf` file are required on every " +"node for the memcache driver:" msgstr "" -#: ../dashboard_sessions.rst:175 -msgid "Cached database" +#: ../compute-system-admin.rst:5 +msgid "System administration" msgstr "" -#: ../telemetry-measurements.rst:617 -msgid "Cached physical memory size" -msgstr "" - -#: ../keystone_caching_layer.rst:70 -msgid "Caching around assignment CRUD" -msgstr "" - -#: ../keystone_caching_layer.rst:37 -msgid "Caching for tokens and tokens validation" -msgstr "" - -#: ../keystone_caching_layer.rst:4 -msgid "Caching layer" -msgstr "" - -#: ../identity_concepts.rst:311 +#: ../compute-system-admin.rst:25 msgid "" -"Can be run in a WSGI-capable web server such as Apache httpd to provide the " -"Identity service. The service and administrative APIs are run as separate " -"instances of the WSGI service." +"To effectively administer Compute, you must understand how the different " +"installed nodes interact with each other. Compute can be installed in many " +"different ways using multiple servers, but generally multiple compute nodes " +"control the virtual servers and a cloud controller node contains the " +"remaining Compute services." msgstr "" -#: ../ts_no_emulator_x86_64.rst:3 -msgid "Cannot find suitable emulator for x86_64" -msgstr "" - -#: ../compute-networking-nova.rst:844 -msgid "Cannot reach floating IPs" -msgstr "" - -#: ../blockstorage_over_subscription.rst:48 -msgid "Capabilities" -msgstr "" - -#: ../blockstorage-driver-filter-weighing.rst:161 -msgid "Capabilities specific to a back end" -msgstr "" - -#: ../blockstorage_over_subscription.rst:101 -msgid "Capacity filter" -msgstr "" - -#: ../blockstorage_over_subscription.rst:108 -msgid "Capacity weigher" -msgstr "" - -#: ../objectstorage-troubleshoot.rst:77 +#: ../compute-system-admin.rst:31 msgid "" -"Caps the length of log lines to the value given; no limit if set to 0, the " -"default." +"The Compute cloud works using a series of daemon processes named nova-\\* " +"that exist persistently on the host machine. These binaries can all run on " +"the same machine or be spread out on multiple boxes in a large deployment. " +"The responsibilities of services and drivers are:" msgstr "" -#: ../telemetry-data-retrieval.rst:352 +#: ../compute-system-admin.rst:36 +msgid "**Services**" +msgstr "" + +#: ../compute-system-admin.rst:39 msgid "" -"Ceilometer also captures data as Events, which represents the state of a " -"resource. Refer to :doc:`/telemetry-events` for more information regarding " -"Events." +"receives XML requests and sends them to the rest of the system. A WSGI app " +"routes and authenticates requests. Supports the EC2 and OpenStack APIs. A :" +"file:`nova.conf` configuration file is created when Compute is installed." msgstr "" -# #-#-#-#-# blockstorage_glusterfs_backend.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -# #-#-#-#-# blockstorage_nfs_backend.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -#: ../blockstorage_glusterfs_backend.rst:14 -#: ../blockstorage_glusterfs_backend.rst:135 -#: ../blockstorage_nfs_backend.rst:14 ../blockstorage_nfs_backend.rst:73 -msgid "CentOS" +#: ../compute-system-admin.rst:42 +msgid "``nova-api``" msgstr "" -#: ../telemetry-data-collection.rst:256 -msgid "Central agent" +#: ../compute-system-admin.rst:45 +msgid "``nova-cert``" msgstr "" -#: ../telemetry-measurements.rst:785 -msgid "Ceph Object Storage" +#: ../compute-system-admin.rst:45 +msgid "manages certificates." msgstr "" -#: ../compute-images-instances.rst:322 +#: ../compute-system-admin.rst:48 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 " -"from the back-end store. Currently the only store to support the direct " -"download approach is the filesystem store. It can be configured using the " -"``filesystems`` option in the ``image_file_url`` section of the :file:`nova." -"conf` file on compute nodes." +"manages virtual machines. Loads a Service object, and exposes the public " +"methods on ComputeManager through a Remote Procedure Call (RPC)." msgstr "" -#: ../telemetry-data-collection.rst:1001 +#: ../compute-system-admin.rst:50 +msgid "``nova-compute``" +msgstr "" + +#: ../compute-system-admin.rst:53 msgid "" -"Certain databases support native TTL expiration. In cases where this is not " -"possible, a command-line script, which you can use for this purpose is " -"ceilometer-expirer. You can run it in a cron job, which helps to keep your " -"database in a consistent state." +"provides database-access support for Compute nodes (thereby reducing " +"security risks)." msgstr "" -#: ../keystone_configure_with_SSL.rst:13 -msgid "Certificate Authority chain to validate against." +#: ../compute-system-admin.rst:54 +msgid "``nova-conductor``" msgstr "" -#: ../networking_introduction.rst:78 +#: ../compute-system-admin.rst:57 +msgid "``nova-consoleauth``" +msgstr "" + +#: ../compute-system-admin.rst:57 +msgid "manages console authentication." +msgstr "" + +#: ../compute-system-admin.rst:60 msgid "" -"Certificate file that is used when you securely start the Networking API " -"server." +"a simple file-based storage system for images that replicates most of the S3 " +"API. It can be replaced with OpenStack Image service and either a simple " +"image manager or OpenStack Object Storage as the virtual machine image " +"storage facility. It must exist on the same node as nova-compute." msgstr "" -#: ../compute-security.rst:86 -msgid "Certificate file used to verify the attestation server's identity" +#: ../compute-system-admin.rst:64 +msgid "``nova-objectstore``" msgstr "" -#: ../keystone_certificates_for_pki.rst:56 +#: ../compute-system-admin.rst:67 msgid "" -"Certificate subject (auto generated certificate) for token signing. Default " -"is ``/C=US/ST=Unset/L=Unset/O=Unset/CN=www.example.com``." +"manages floating and fixed IPs, DHCP, bridging and VLANs. Loads a Service " +"object which exposes the public methods on one of the subclasses of " +"NetworkManager. Different networking strategies are available by changing " +"the ``network_manager`` configuration option to ``FlatManager``, " +"``FlatDHCPManager``, or ``VLANManager`` (defaults to ``VLANManager`` if " +"nothing is specified)." msgstr "" -#: ../keystone_certificates_for_pki.rst:3 -msgid "Certificates for PKI" +#: ../compute-system-admin.rst:72 +msgid "``nova-network``" msgstr "" -#: ../compute-node-down.rst:126 -msgid "Change all the files owned by user or group nova. For example:" +#: ../compute-system-admin.rst:75 +msgid "dispatches requests for new virtual machines to the correct node." msgstr "" -#: ../ts_cinder_config.rst:165 +#: ../compute-system-admin.rst:76 +msgid "``nova-scheduler``" +msgstr "" + +#: ../compute-system-admin.rst:79 msgid "" -"Change contents of the :file:`/etc/tgt/targets.conf` from ``include /etc/tgt/" -"conf.d/*.conf`` to ``include /etc/tgt/conf.d/cinder_tgt.conf``, as follows:" +"provides a VNC proxy for browsers, allowing VNC consoles to access virtual " +"machines." msgstr "" -#: ../ts-duplicate-3par-host.rst:23 +#: ../compute-system-admin.rst:80 +msgid "``nova-novncproxy``" +msgstr "" + +#: ../compute-system-admin.rst:84 msgid "" -"Change the 3PAR host name to match the one that OpenStack expects. The 3PAR " -"host constructed by the driver uses just the local hostname, not the fully " -"qualified domain name (FQDN) of the compute host. For example, if the FQDN " -"was *myhost.example.com*, just *myhost* would be used as the 3PAR hostname. " -"IP addresses are not allowed as host names on the 3PAR storage server." -msgstr "" - -#: ../compute-node-down.rst:77 -msgid "" -"Change the ``DHCPSERVER`` value to the host IP address of the new compute " -"host." -msgstr "" - -#: ../networking_config-agents.rst:399 -msgid "" -"Change the ``enable_lb`` option to ``True`` in the :file:`local_settings` " -"file (on Fedora, RHEL, and CentOS: :file:`/etc/openstack-dashboard/" -"local_settings`, on Ubuntu and Debian: :file:`/etc/openstack-dashboard/" -"local_settings.py`, and on openSUSE and SLES: :file:`/srv/www/openstack-" -"dashboard/openstack_dashboard/local/local_settings .py`):" -msgstr "" - -#: ../compute-configuring-migrations.rst:164 -msgid "" -"Change the subnet mask (``255.255.0.0``) to the appropriate value to include " -"the IP addresses of ``HostB`` and ``HostC``. Then restart the NFS server:" -msgstr "" - -#: ../objectstorage_ringbuilder.rst:129 -msgid "" -"Changes take effect after the ring is rebalanced. Therefore, if you intend " -"to change from 3 replicas to 3.01 but you accidentally type 2.01, no data is " -"lost." -msgstr "" - -#: ../telemetry-measurements.rst:35 -msgid "Changing over time (bandwidth)" -msgstr "" - -#: ../compute-configuring-migrations.rst:194 -msgid "" -"Check that ``HostA`` can see the :file:`NOVA-INST-DIR/instances/` directory" -msgstr "" - -#: ../compute-live-migration-usage.rst:156 -msgid "Check that ``HostC`` has enough resources for migration:" -msgstr "" - -#: ../compute-networking-nova.rst:848 -msgid "" -"Check that the default security group allows ICMP (ping) and SSH (port 22), " -"so that you can reach the instances:" -msgstr "" - -#: ../compute-live-migration-usage.rst:225 -msgid "" -"Check that the instance has been migrated successfully, using :command:`nova " -"list`. If the instance is still running on ``HostB``, check the log files " -"at :file:`src/dest` for nova-compute and nova-scheduler to determine why." -msgstr "" - -#: ../compute-networking-nova.rst:870 -msgid "" -"Check that the public address (`68.99.26.170 <68.99.26.170>`__ in this " -"example), has been added to your public interface. You should see the " -"address in the listing when you use the :command:`ip addr` command:" -msgstr "" - -#: ../compute-live-migration-usage.rst:24 -msgid "Check the ID of the instance to be migrated:" -msgstr "" - -#: ../compute-networking-nova.rst:861 -msgid "" -"Check the NAT rules have been added to iptables on the node that is running " -"``nova-network``:" -msgstr "" - -#: ../compute-node-down.rst:210 -msgid "" -"Check the current relationship between the volume and its instance, so that " -"you can recreate the attachment." -msgstr "" - -#: ../compute-live-migration-usage.rst:47 -msgid "" -"Check the information associated with the instance. In this example, ``vm1`` " -"is running on ``HostB``:" -msgstr "" - -#: ../cross_project_cors.rst:118 -msgid "Check the service log" -msgstr "" - -#: ../networking_use.rst:185 -msgid "Checks available networks." -msgstr "" - -#: ../blockstorage_backup_disks.rst:172 -msgid "Checksum calculation I" -msgstr "" - -#: ../networking_adv-features.rst:292 -msgid "Clears the gateway." -msgstr "" - -#: ../keystone_configure_with_SSL.rst:35 -msgid "Client authentication with keystone-all" -msgstr "" - -#: ../networking_use.rst:19 -msgid "" -"Cloud administrators and tenants can use OpenStack Networking to build rich " -"network topologies. Cloud administrators can create network connectivity on " -"behalf of tenants." -msgstr "" - -#: ../networking_use.rst:272 -msgid "" -"Cloud images that distribution vendors offer usually have only one active " -"NIC configured. When you boot with multiple NICs, you must configure " -"additional interfaces on the image or the NICS are not reachable." -msgstr "" - -#: ../objectstorage_arch.rst:3 -msgid "Cluster architecture" -msgstr "" - -#: ../telemetry-measurements.rst:1283 -msgid "Cluster was successfully created" -msgstr "" - -#: ../telemetry-measurements.rst:1292 -msgid "Cluster was successfully deleted" -msgstr "" - -#: ../telemetry-measurements.rst:1288 -msgid "Cluster was successfully updated" -msgstr "" - -#: ../telemetry-data-collection.rst:16 -msgid "" -"Collected data can be stored in the form of samples or events in the " -"supported databases, listed in :ref:`telemetry-supported-databases`." -msgstr "" - -#: ../telemetry-measurements.rst:1018 -msgid "Collisions on p\\ ort" -msgstr "" - -#: ../telemetry-alarms.rst:47 -msgid "Combination rule alarms" -msgstr "" - -# #-#-#-#-# compute-manage-volumes.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -# #-#-#-#-# networking_adv-features.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -# #-#-#-#-# networking_config-agents.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -# #-#-#-#-# networking_use.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -#: ../compute-manage-volumes.rst:13 ../networking_adv-features.rst:207 -#: ../networking_adv-features.rst:357 ../networking_adv-features.rst:492 -#: ../networking_adv-features.rst:784 ../networking_config-agents.rst:492 -#: ../networking_use.rst:47 ../networking_use.rst:123 -#: ../networking_use.rst:183 ../networking_use.rst:241 -msgid "Command" -msgstr "" - -#: ../networking_multi-dhcp-agents.rst:140 -msgid "Commands in agent management and scheduler extensions" -msgstr "" - -#: ../identity_auth_token_middleware.rst:47 -msgid "" -"Comment out any :code:`auth_host`, :code:`auth_port`, and :code:" -"`auth_protocol` options because the :code:`identity_uri` option replaces " -"them." -msgstr "" - -#: ../identity_auth_token_middleware.rst:71 -msgid "" -"Comment out any ``auth_host``, ``auth_port``, and ``auth_protocol`` options " -"because the ``identity_uri`` option replaces them." -msgstr "" - -#: ../telemetry-data-retrieval.rst:114 -msgid "" -"Complex query supports specifying a list of ``orderby`` expressions. This " -"means that the result of the query can be ordered based on the field names " -"provided in this list. When multiple keys are defined for the ordering, " -"these will be applied sequentially in the order of the specification. The " -"second expression will be applied on the groups for which the values of the " -"first expression are the same. The ordering can be ascending or descending." -msgstr "" - -#: ../objectstorage_components.rst:3 -msgid "Components" +"Some services have drivers that change how the service implements its core " +"functionality. For example, the nova-compute service supports drivers that " +"let you choose which hypervisor type it can use. nova-network and nova-" +"scheduler also have drivers." msgstr "" # #-#-#-#-# compute.pot (Cloud Administrator Guide 0.9) #-#-#-#-# @@ -4209,58 +8318,12 @@ msgstr "" msgid "Compute" msgstr "" -#: ../networking_arch.rst:59 +#: ../compute.rst:5 msgid "" -"Compute (nova) interacts with Networking through calls to its standard API. " -"As part of creating a VM, the nova-compute service communicates with the " -"Networking API to plug each virtual NIC on the VM into a particular network." -msgstr "" - -#: ../telemetry-data-collection.rst:286 -msgid "Compute agent" -msgstr "" - -#: ../compute-networking-nova.rst:16 -msgid "" -"Compute assigns a private IP address to each VM instance. Compute makes a " -"distinction between fixed IPs and floating IP. Fixed IPs are IP addresses " -"that are assigned to an instance on creation and stay the same until the " -"instance is explicitly terminated. Floating IPs are addresses that can be " -"dynamically associated with an instance. A floating IP address can be " -"disassociated and associated with another instance at any time. A user can " -"reserve a floating IP for their project." -msgstr "" - -#: ../compute-configuring-migrations.rst:83 -msgid "" -"Compute calculates the amount of downtime required using the RAM size of the " -"disk being migrated, in accordance with the ``live_migration_downtime`` " -"configuration parameters. Migration downtime is measured in steps, with an " -"exponential backoff between each step. This means that the maximum downtime " -"between each step starts off small, and is increased in ever larger amounts " -"as Compute waits for the migration to complete. This gives the guest a " -"chance to complete the migration successfully, with a minimum amount of " -"downtime." -msgstr "" - -#: ../compute-admin-password-injection.rst:7 -msgid "" -"Compute can generate a random administrator (root) password and inject that " -"password into an instance. If this feature is enabled, users can run :" -"command:`ssh` to an instance without an :command:`ssh` keypair. The random " -"password appears in the output of the :command:`nova boot` command. You can " -"also view and set the admin password from the dashboard." -msgstr "" - -#: ../compute_arch.rst:43 -msgid "" -"Compute controls hypervisors through an API server. Selecting the best " -"hypervisor to use can be difficult, and you must take budget, resource " -"constraints, supported features, and required technical specifications into " -"account. However, the majority of OpenStack development is done on systems " -"using KVM and Xen-based hypervisors. For a detailed list of features and " -"support across different hypervisors, see http://wiki.openstack.org/" -"HypervisorSupportMatrix." +"The OpenStack Compute service allows you to control an Infrastructure-as-a-" +"Service (IaaS) cloud computing platform. It gives you control over instances " +"and networks, and allows you to manage access to the cloud through users and " +"projects." msgstr "" #: ../compute.rst:10 @@ -4270,39 +8333,48 @@ msgid "" "your host operating system, and exposes functionality over a web-based API." msgstr "" -#: ../compute-networking-nova.rst:691 +#: ../compute_arch.rst:5 +msgid "OpenStack Compute contains several main components." +msgstr "" + +#: ../compute_arch.rst:7 msgid "" -"Compute maintains a list of floating IP addresses that are available for " -"assigning to instances. Use the :command:`nova-manage floating` commands to " -"perform floating IP operations:" +"The :term:`cloud controller` represents the global state and interacts with " +"the other components. The ``API server`` acts as the web services front end " +"for the cloud controller. The ``compute controller`` provides compute server " +"resources and usually also contains the Compute service." msgstr "" -#: ../ts-failed-connect-vol-FC-SAN.rst:11 +#: ../compute_arch.rst:13 msgid "" -"Compute node failed to connect to a volume in a Fibre Channel (FC) SAN " -"configuration. The WWN may not be zoned correctly in your FC SAN that links " -"the compute host to the storage array::" +"The ``object store`` is an optional component that provides storage " +"services; you can also use OpenStack Object Storage instead." msgstr "" -#: ../compute-images-instances.rst:329 +#: ../compute_arch.rst:16 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 " -"on the configuration options for caching on compute nodes can be found in " -"the `Configuration Reference `__." +"An ``auth manager`` provides authentication and authorization services when " +"used with the Compute system; you can also use OpenStack Identity as a " +"separate authentication service instead." msgstr "" -#: ../compute-security.rst:27 -msgid "Compute nodes boot with Intel TXT technology enabled." +#: ../compute_arch.rst:20 +msgid "" +"A ``volume controller`` provides fast and permanent block-level storage for " +"the compute servers." msgstr "" -#: ../compute_arch.rst:295 -msgid "Compute service architecture" +#: ../compute_arch.rst:23 +msgid "" +"The ``network controller`` provides virtual networks to enable compute " +"servers to interact with each other and with the public network. You can " +"also use OpenStack Networking instead." msgstr "" -#: ../compute-default-ports.rst:5 -msgid "Compute service node firewall requirements" +#: ../compute_arch.rst:27 +msgid "" +"The ``scheduler`` is used to select the most suitable compute controller to " +"host an instance." msgstr "" #: ../compute_arch.rst:30 @@ -4318,13 +8390,425 @@ msgid "" "when a response is received." msgstr "" -#: ../compute-networking-nova.rst:325 +#: ../compute_arch.rst:42 +msgid "Hypervisors" +msgstr "" + +#: ../compute_arch.rst:43 msgid "" -"Compute uses a metadata service for virtual machine instances to retrieve " -"instance-specific data. Instances access the metadata service at " -"``http://169.254.169.254``. The metadata service supports two sets of APIs: " -"an OpenStack metadata API and an EC2-compatible API. Both APIs are versioned " -"by date." +"Compute controls hypervisors through an API server. Selecting the best " +"hypervisor to use can be difficult, and you must take budget, resource " +"constraints, supported features, and required technical specifications into " +"account. However, the majority of OpenStack development is done on systems " +"using KVM and Xen-based hypervisors. For a detailed list of features and " +"support across different hypervisors, see http://wiki.openstack.org/" +"HypervisorSupportMatrix." +msgstr "" + +#: ../compute_arch.rst:51 +msgid "" +"You can also orchestrate clouds using multiple hypervisors in different " +"availability zones. Compute supports the following hypervisors:" +msgstr "" + +#: ../compute_arch.rst:54 +msgid "`Baremetal `__" +msgstr "" + +#: ../compute_arch.rst:56 +msgid "`Docker `__" +msgstr "" + +# #-#-#-#-# compute_arch.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +# #-#-#-#-# telemetry-system-architecture.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +#: ../compute_arch.rst:58 ../telemetry-system-architecture.rst:133 +msgid "" +"`Hyper-V `__" +msgstr "" + +# #-#-#-#-# compute_arch.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +# #-#-#-#-# telemetry-system-architecture.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +#: ../compute_arch.rst:60 ../telemetry-system-architecture.rst:118 +msgid "" +"`Kernel-based Virtual Machine (KVM) `__" +msgstr "" + +# #-#-#-#-# compute_arch.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +# #-#-#-#-# telemetry-system-architecture.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +#: ../compute_arch.rst:63 ../telemetry-system-architecture.rst:123 +msgid "`Linux Containers (LXC) `__" +msgstr "" + +#: ../compute_arch.rst:65 +msgid "`Quick Emulator (QEMU) `__" +msgstr "" + +#: ../compute_arch.rst:67 +msgid "`User Mode Linux (UML) `__" +msgstr "" + +#: ../compute_arch.rst:69 +msgid "" +"`VMware vSphere `__" +msgstr "" + +#: ../compute_arch.rst:72 +msgid "`Xen `__" +msgstr "" + +#: ../compute_arch.rst:74 +msgid "" +"For more information about hypervisors, see the `Hypervisors `__ section in the OpenStack Configuration Reference." +msgstr "" + +#: ../compute_arch.rst:79 +msgid "Tenants, users, and roles" +msgstr "" + +#: ../compute_arch.rst:80 +msgid "" +"The Compute system is designed to be used by different consumers in the form " +"of tenants on a shared system, and role-based access assignments. Roles " +"control the actions that a user is allowed to perform." +msgstr "" + +#: ../compute_arch.rst:84 +msgid "" +"Tenants are isolated resource containers that form the principal " +"organizational structure within the Compute service. They consist of an " +"individual VLAN, and volumes, instances, images, keys, and users. A user can " +"specify the tenant by appending ``project_id`` to their access key. If no " +"tenant is specified in the API request, Compute attempts to use a tenant " +"with the same ID as the user." +msgstr "" + +#: ../compute_arch.rst:91 +msgid "For tenants, you can use quota controls to limit the:" +msgstr "" + +#: ../compute_arch.rst:93 +msgid "Number of volumes that can be launched." +msgstr "" + +#: ../compute_arch.rst:95 +msgid "Number of processor cores and the amount of RAM that can be allocated." +msgstr "" + +#: ../compute_arch.rst:98 +msgid "" +"Floating IP addresses assigned to any instance when it launches. This allows " +"instances to have the same publicly accessible IP addresses." +msgstr "" + +#: ../compute_arch.rst:101 +msgid "" +"Fixed IP addresses assigned to the same instance when it launches. This " +"allows instances to have the same publicly or privately accessible IP " +"addresses." +msgstr "" + +#: ../compute_arch.rst:105 +msgid "" +"Roles control the actions a user is allowed to perform. By default, most " +"actions do not require a particular role, but you can configure them by " +"editing the :file:`policy.json` file for user roles. For example, a rule can " +"be defined so that a user must have the ``admin`` role in order to be able " +"to allocate a public IP address." +msgstr "" + +#: ../compute_arch.rst:111 +msgid "" +"A tenant limits users' access to particular images. Each user is assigned a " +"user name and password. Keypairs granting access to an instance are enabled " +"for each user, but quotas are set, so that each tenant can control resource " +"consumption across available hardware resources." +msgstr "" + +#: ../compute_arch.rst:119 +msgid "" +"Earlier versions of OpenStack used the term ``project`` instead of " +"``tenant``. Because of this legacy terminology, some command-line tools use " +"``--project_id`` where you would normally expect to enter a tenant ID." +msgstr "" + +#: ../compute_arch.rst:125 +msgid "Block storage" +msgstr "" + +#: ../compute_arch.rst:126 +msgid "" +"OpenStack provides two classes of block storage: ephemeral storage and " +"persistent volume." +msgstr "" + +#: ../compute_arch.rst:129 +msgid "**Ephemeral storage**" +msgstr "" + +#: ../compute_arch.rst:131 +msgid "" +"Ephemeral storage includes a root ephemeral volume and an additional " +"ephemeral volume." +msgstr "" + +#: ../compute_arch.rst:134 +msgid "" +"The root disk is associated with an instance, and exists only for the life " +"of this very instance. Generally, it is used to store an instance's root " +"file system, persists across the guest operating system reboots, and is " +"removed on an instance deletion. The amount of the root ephemeral volume is " +"defined by the flavor of an instance." +msgstr "" + +#: ../compute_arch.rst:140 +msgid "" +"In addition to the ephemeral root volume, all default types of flavors, " +"except ``m1.tiny``, which is the smallest one, provide an additional " +"ephemeral block device sized between 20 and 160 GB (a configurable value to " +"suit an environment). It is represented as a raw block device with no " +"partition table or file system. A cloud-aware operating system can discover, " +"format, and mount such a storage device. OpenStack Compute defines the " +"default file system for different operating systems as Ext4 for Linux " +"distributions, VFAT for non-Linux and non-Windows operating systems, and " +"NTFS for Windows. However, it is possible to specify any other filesystem " +"type by using ``virt_mkfs`` or ``default_ephemeral_format`` configuration " +"options." +msgstr "" + +#: ../compute_arch.rst:154 +msgid "" +"For example, the ``cloud-init`` package included into an Ubuntu's stock " +"cloud image, by default, formats this space as an Ext4 file system and " +"mounts it on :file:`/mnt`. This is a cloud-init feature, and is not an " +"OpenStack mechanism. OpenStack only provisions the raw storage." +msgstr "" + +#: ../compute_arch.rst:159 +msgid "**Persistent volume**" +msgstr "" + +#: ../compute_arch.rst:161 +msgid "" +"A persistent volume is represented by a persistent virtualized block device " +"independent of any particular instance, and provided by OpenStack Block " +"Storage." +msgstr "" + +#: ../compute_arch.rst:165 +msgid "" +"Only a single configured instance can access a persistent volume. Multiple " +"instances cannot access a persistent volume. This type of configuration " +"requires a traditional network file system to allow multiple instances " +"accessing the persistent volume. It also requires a traditional network file " +"system like NFS, CIFS, or a cluster file system such as GlusterFS. These " +"systems can be built within an OpenStack cluster, or provisioned outside of " +"it, but OpenStack software does not provide these features." +msgstr "" + +#: ../compute_arch.rst:174 +msgid "" +"You can configure a persistent volume as bootable and use it to provide a " +"persistent virtual instance similar to the traditional non-cloud-based " +"virtualization system. It is still possible for the resulting instance to " +"keep ephemeral storage, depending on the flavor selected. In this case, the " +"root file system can be on the persistent volume, and its state is " +"maintained, even if the instance is shut down. For more information about " +"this type of configuration, see the `OpenStack Configuration Reference " +"`__." +msgstr "" + +#: ../compute_arch.rst:186 +msgid "" +"A persistent volume does not provide concurrent access from multiple " +"instances. That type of configuration requires a traditional network file " +"system like NFS, or CIFS, or a cluster file system such as GlusterFS. These " +"systems can be built within an OpenStack cluster, or provisioned outside of " +"it, but OpenStack software does not provide these features." +msgstr "" + +#: ../compute_arch.rst:194 +msgid "EC2 compatibility API" +msgstr "" + +#: ../compute_arch.rst:195 +msgid "" +"In addition to the native compute API, OpenStack provides an EC2-compatible " +"API. This API allows EC2 legacy workflows built for EC2 to work with " +"OpenStack. For more information and configuration options about this " +"compatibility API, see the `OpenStack Configuration Reference `__." +msgstr "" + +#: ../compute_arch.rst:201 +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:206 +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, " +"or for transitioning from EC2-based clouds to OpenStack. For more " +"information, see the `euca2ools site `__." +msgstr "" + +#: ../compute_arch.rst:210 +msgid "Euca2ools" +msgstr "" + +#: ../compute_arch.rst:213 +msgid "" +"A Firefox browser add-on that provides a graphical interface to many popular " +"public and private cloud technologies, including OpenStack. For more " +"information, see the `hybridfox site `__." +msgstr "" + +#: ../compute_arch.rst:216 +msgid "Hybridfox" +msgstr "" + +#: ../compute_arch.rst:219 +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:222 +msgid "boto" +msgstr "" + +#: ../compute_arch.rst:225 +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:228 +msgid "fog" +msgstr "" + +#: ../compute_arch.rst:231 +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:234 +msgid "php-opencloud" +msgstr "" + +#: ../compute_arch.rst:237 +msgid "Building blocks" +msgstr "" + +#: ../compute_arch.rst:238 +msgid "" +"In OpenStack the base operating system is usually copied from an image " +"stored in the OpenStack Image service. This is the most common case and " +"results in an ephemeral instance that starts from a known template state and " +"loses all accumulated states on virtual machine deletion. It is also " +"possible to put an operating system on a persistent volume in the OpenStack " +"Block Storage volume system. This gives a more traditional persistent system " +"that accumulates states which are preserved on the OpenStack Block Storage " +"volume across the deletion and re-creation of the virtual machine. To get a " +"list of available images on your system, run::" +msgstr "" + +#: ../compute_arch.rst:261 +msgid "Automatically generated UUID of the image" +msgstr "" + +#: ../compute_arch.rst:264 +msgid "Free form, human-readable name for image" +msgstr "" + +#: ../compute_arch.rst:275 +msgid "" +"Virtual hardware templates are called ``flavors``. The default installation " +"provides five flavors. By default, these are configurable by admin users, " +"however that behavior can be changed by redefining the access controls for " +"``compute_extension:flavormanage`` in :file:`/etc/nova/policy.json` on the " +"``compute-api`` server." +msgstr "" + +#: ../compute_arch.rst:281 +msgid "For a list of flavors that are available on your system::" +msgstr "" + +#: ../compute_arch.rst:295 +msgid "Compute service architecture" +msgstr "" + +#: ../compute_arch.rst:296 +msgid "" +"These basic categories describe the service architecture and information " +"about the cloud controller." +msgstr "" + +#: ../compute_arch.rst:299 +msgid "**API server**" +msgstr "" + +#: ../compute_arch.rst:301 +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:305 +msgid "" +"The API endpoints are basic HTTP web services which handle authentication, " +"authorization, and basic command and control functions using various API " +"interfaces under the Amazon, Rackspace, and related models. This enables API " +"compatibility with multiple existing tool sets created for interaction with " +"offerings from other vendors. This broad compatibility prevents vendor lock-" +"in." +msgstr "" + +#: ../compute_arch.rst:312 +msgid "**Message queue**" +msgstr "" + +#: ../compute_arch.rst:314 +msgid "" +"A messaging queue brokers the interaction between compute nodes " +"(processing), the networking controllers (software which controls network " +"infrastructure), API endpoints, the scheduler (determines which physical " +"hardware to allocate to a virtual resource), and similar components. " +"Communication to and from the cloud controller is handled by HTTP requests " +"through multiple API endpoints." +msgstr "" + +#: ../compute_arch.rst:321 +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 " +"they are permitted to issue the subject command. The availability of objects " +"implicated in the request is evaluated and, if available, the request is " +"routed to the queuing engine for the relevant workers. Workers continually " +"listen to the queue based on their role, and occasionally their type host " +"name. When an applicable work request arrives on the queue, the worker takes " +"assignment of the task and begins executing it. Upon completion, a response " +"is dispatched to the queue which is received by the API server and relayed " +"to the originating user. Database entries are queried, added, or removed as " +"necessary during the process." +msgstr "" + +#: ../compute_arch.rst:334 +msgid "**Compute worker**" msgstr "" #: ../compute_arch.rst:336 @@ -4333,84 +8817,5298 @@ msgid "" "dispatches commands to compute workers to complete these tasks:" msgstr "" -# #-#-#-#-# networking_config-identity.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -# #-#-#-#-# networking_multi-dhcp-agents.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -#: ../networking_config-identity.rst:207 ../networking_config-identity.rst:232 -#: ../networking_multi-dhcp-agents.rst:54 -msgid "Configuration" +#: ../compute_arch.rst:339 +msgid "Run instances" msgstr "" -#: ../networking_use.rst:17 -msgid "Configuration files are in the :file:`/etc/neutron` directory." +#: ../compute_arch.rst:341 +msgid "Terminate instances" msgstr "" -#: ../compute-networking-nova.rst:48 +#: ../compute_arch.rst:343 +msgid "Reboot instances" +msgstr "" + +#: ../compute_arch.rst:345 +msgid "Attach volumes" +msgstr "" + +#: ../compute_arch.rst:347 +msgid "Detach volumes" +msgstr "" + +#: ../compute_arch.rst:349 +msgid "Get console output" +msgstr "" + +#: ../compute_arch.rst:351 +msgid "**Network Controller**" +msgstr "" + +#: ../compute_arch.rst:353 msgid "" -"Configuration injection currently only works on Linux-style systems that " -"keep networking configuration in :file:`/etc/network/interfaces`." +"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-networking-nova.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -# #-#-#-#-# compute-remote-console-access.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -# #-#-#-#-# compute-security.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -# #-#-#-#-# objectstorage-troubleshoot.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -#: ../compute-networking-nova.rst:309 ../compute-networking-nova.rst:507 -#: ../compute-remote-console-access.rst:152 ../compute-security.rst:103 -#: ../objectstorage-troubleshoot.rst:61 -msgid "Configuration option = Default value" +#: ../compute_arch.rst:358 +msgid "Allocating fixed IP addresses" msgstr "" -#: ../compute-root-wrap-reference.rst:56 ../compute-root-wrap-reference.rst:95 -msgid "Configuration option=Default value" +#: ../compute_arch.rst:360 +msgid "Configuring VLANs for projects" msgstr "" -#: ../compute-flavors.rst:24 +#: ../compute_arch.rst:362 +msgid "Configuring networks for compute nodes" +msgstr "" + +#: ../cross_project.rst:3 +msgid "Cross-project features" +msgstr "" + +#: ../cross_project.rst:5 msgid "" -"Configuration rights can be delegated to additional users by redefining the " -"access controls for ``compute_extension:flavormanage`` in :file:`/etc/nova/" -"policy.json` on the nova-api server." +"Many features are common to all the OpenStack services and are consistent in " +"their configuration and deployment patterns. Unless explicitly noted, you " +"can safely assume that the features in this chapter are supported and " +"configured in a consistent manner." msgstr "" -#: ../networking_config-plugins.rst:12 -msgid "Configure Big Switch (Floodlight REST Proxy) plug-in" +#: ../cross_project_cors.rst:5 +msgid "Cross-origin resource sharing" msgstr "" -#: ../blockstorage_multi_backend.rst:103 -msgid "Configure Block Storage scheduler multi back end" +#: ../cross_project_cors.rst:8 +msgid "This is a new feature in OpenStack Liberty." msgstr "" -#: ../networking_config-plugins.rst:48 -msgid "Configure Brocade plug-in" +#: ../cross_project_cors.rst:10 +msgid "" +"OpenStack supports :term:`Cross-Origin Resource Sharing (CORS)`, a W3C " +"specification defining a contract by which the single-origin policy of a " +"user agent (usually a browser) may be relaxed. It permits it's javascript " +"engine to access an API that does not reside on the same domain, protocol, " +"or port." msgstr "" -#: ../compute-service-groups.rst:5 -msgid "Configure Compute service groups" +#: ../cross_project_cors.rst:15 +msgid "" +"This feature is most useful to organizations which maintain one or more " +"custom user interfaces for OpenStack, as it permits those interfaces to " +"access the services directly, rather than requiring an intermediate proxy " +"server. It can, however, also be misused by malicious actors; please review " +"the security advisory below for more information." msgstr "" -#: ../compute-networking-nova.rst:228 -msgid "Configure Compute to use IPv6 addresses" +#: ../cross_project_cors.rst:23 +msgid "" +"Both the Object Storage and dashboard projects provide CORS support that is " +"not covered by this document. For those, please refer to their respective " +"implementations:" msgstr "" -#: ../networking_config-agents.rst:56 -msgid "Configure DHCP agent" +#: ../cross_project_cors.rst:27 +msgid "" +"`CORS in Object Storage `_" msgstr "" -#: ../networking_config-agents.rst:418 -msgid "Configure Hyper-V L2 agent" +#: ../cross_project_cors.rst:28 +msgid "" +"`CORS in dashboard `_" msgstr "" -#: ../networking_config-identity.rst:3 -msgid "Configure Identity service for Networking" +#: ../cross_project_cors.rst:32 +msgid "Enabling CORS with configuration" +msgstr "" + +#: ../cross_project_cors.rst:34 +msgid "" +"In most cases, CORS support is built directly into the service itself. To " +"enable it, simply follow the configuration options exposed in the default " +"configuration file, or add it yourself according to the pattern below." +msgstr "" + +#: ../cross_project_cors.rst:48 +msgid "" +"This method also enables you to define multiple origins. To express this in " +"your configuration file, first begin with a :code:`[cors]` group as above, " +"into which you place your default configuration values. Then, add as many " +"additional configuration groups as necessary, naming them :code:`[cors." +"{something}]` (each name must be unique). The purpose of the suffix to :code:" +"`cors.` is legibility, we recommend using a reasonable human-readable string:" +msgstr "" + +#: ../cross_project_cors.rst:76 +msgid "Enabling CORS with PasteDeploy" +msgstr "" + +#: ../cross_project_cors.rst:78 +msgid "" +"In other services, CORS is configured via PasteDeploy. In this case, you " +"must first make sure that OpenStack's :code:`oslo_middleware` package " +"(version 2.4.0 or later) is available in the Python environment that is " +"running the service. Then, add the following configuration block to your :" +"file:`paste.ini` file." +msgstr "" + +#: ../cross_project_cors.rst:95 +msgid "To add another domain, simply add another filter." +msgstr "" + +#: ../cross_project_cors.rst:98 +msgid "Security concerns" +msgstr "" + +#: ../cross_project_cors.rst:100 +msgid "" +"CORS specifies a wildcard character `*`, which permits access to all user " +"agents, regardless of domain, protocol, or host. While there are valid use " +"cases for this approach, it also permits a malicious actor to create a " +"convincing facsimile of a user interface, and trick users into revealing " +"authentication credentials. Please carefully evaluate your use case and the " +"relevant documentation for any risk to your organization." +msgstr "" + +#: ../cross_project_cors.rst:107 +msgid "" +"The CORS specification does not support using this wildcard as a part of a " +"URI. Setting allowed-origin to `*` would work, while :code:`*.openstack.org` " +"would not." +msgstr "" + +#: ../cross_project_cors.rst:112 +msgid "Troubleshooting" +msgstr "" + +#: ../cross_project_cors.rst:113 +msgid "" +"CORS is very easy to get wrong, as even one incorrect property will violate " +"the prescribed contract. Here are some steps you can take to troubleshoot " +"your configuration." +msgstr "" + +#: ../cross_project_cors.rst:118 +msgid "Check the service log" +msgstr "" + +#: ../cross_project_cors.rst:120 +msgid "" +"The CORS middleware used by OpenStack provides verbose debug logging that " +"should reveal most configuration problems. Here are some example log " +"messages, and how to resolve them." +msgstr "" + +#: ../cross_project_cors.rst:125 +msgid "" +"A request was received from the origin 'http://foo.com', however this origin " +"was not found in the permitted list. The cause may be a superfluous port " +"notation (ports 80 and 443 do not need to be specified). To correct, ensure " +"that the configuration property for this host is identical to the host " +"indicated in the log message." +msgstr "" + +#: ../cross_project_cors.rst:129 +msgid "``CORS request from origin 'http://foo.com' not permitted.``" +msgstr "" + +#: ../cross_project_cors.rst:132 +msgid "" +"A user agent has requested permission to perform a DELETE request, however " +"the CORS configuration for the domain does not permit this. To correct, add " +"this method to the :code:`allow_methods` configuration property." +msgstr "" + +#: ../cross_project_cors.rst:134 +msgid "``Request method 'DELETE' not in permitted list: GET,PUT,POST``" +msgstr "" + +#: ../cross_project_cors.rst:137 +msgid "" +"A request was received with the header 'X-Custom-Header', which is not " +"permitted. Add this header to the :code:`allow_headers` configuration " +"property." +msgstr "" + +#: ../cross_project_cors.rst:139 +msgid "" +"``Request header 'X-Custom-Header' not in permitted list: X-Other-Header``" +msgstr "" + +#: ../cross_project_cors.rst:142 +msgid "Open your browser's console log" +msgstr "" + +#: ../cross_project_cors.rst:144 +msgid "" +"Most browsers provide helpful debug output when a CORS request is rejected. " +"Usually this happens when a request was successful, but the return headers " +"on the response do not permit access to a property which the browser is " +"trying to access." +msgstr "" + +#: ../cross_project_cors.rst:150 +msgid "Manually construct a CORS request" +msgstr "" + +#: ../cross_project_cors.rst:151 +msgid "" +"By using ``curl`` or a similar tool, you can trigger a CORS response with a " +"properly constructed HTTP request. An example request and response might " +"look like this." +msgstr "" + +#: ../cross_project_cors.rst:155 +msgid "Request::" +msgstr "" + +#: ../cross_project_cors.rst:159 +msgid "Response::" +msgstr "" + +#: ../cross_project_cors.rst:169 +msgid "" +"If the service does not return any access control headers, check the service " +"log, such as :code:`/var/log/upstart/ironic-api.log` for an indication on " +"what went wrong." +msgstr "" + +#: ../dashboard.rst:3 +msgid "Dashboard" +msgstr "" + +#: ../dashboard.rst:5 +msgid "" +"The OpenStack dashboard is a web-based interface that allows you to manage " +"OpenStack resources and services. The dashboard allows you to interact with " +"the OpenStack Compute cloud controller using the OpenStack APIs. For more " +"information about installing and configuring the dashboard, see the " +"`OpenStack Installation Guide `__ for your operating system." +msgstr "" + +#: ../dashboard.rst:20 +msgid "" +"To deploy the dashboard, see the `OpenStack dashboard documentation `__." +msgstr "" + +#: ../dashboard.rst:22 +msgid "" +"To launch instances with the dashboard, see the `OpenStack End User Guide " +"`__." +msgstr "" + +#: ../dashboard_sessions.rst:6 +msgid "Set up session storage for the Dashboard" +msgstr "" + +#: ../dashboard_sessions.rst:8 +msgid "" +"The dashboard uses `Django sessions framework `__ to handle user session data. However, " +"you can use any available session back end. You customize the session back " +"end through the ``SESSION_ENGINE`` setting in your :file:`local_settings` " +"file (on Fedora/RHEL/ CentOS: :file:`/etc/openstack-dashboard/" +"local_settings`, on Ubuntu and Debian: :file:`/etc/openstack-dashboard/" +"local_settings.py`, and on openSUSE: :file:`/srv/www/openstack-dashboard/" +"openstack_dashboard/local/local_settings.py`)." +msgstr "" + +#: ../dashboard_sessions.rst:17 +msgid "" +"After architecting and implementing the core OpenStack services and other " +"required services, combined with the Dashboard service steps below, users " +"and administrators can use the OpenStack dashboard. Refer to the `OpenStack " +"Dashboard `__ chapter " +"of the User Guide for further instructions on logging in to the Dashboard." +msgstr "" + +#: ../dashboard_sessions.rst:25 +msgid "" +"The following sections describe the pros and cons of each option as it " +"pertains to deploying the Dashboard." +msgstr "" + +#: ../dashboard_sessions.rst:29 +msgid "Local memory cache" +msgstr "" + +#: ../dashboard_sessions.rst:30 +msgid "" +"Local memory storage is the quickest and easiest session back end to set up, " +"as it has no external dependencies whatsoever. It has the following " +"significant drawbacks:" +msgstr "" + +#: ../dashboard_sessions.rst:34 +msgid "No shared storage across processes or workers." +msgstr "" + +#: ../dashboard_sessions.rst:35 +msgid "No persistence after a process terminates." +msgstr "" + +#: ../dashboard_sessions.rst:37 +msgid "" +"The local memory back end is enabled as the default for Horizon solely " +"because it has no dependencies. It is not recommended for production use, or " +"even for serious development work. Enabled by::" +msgstr "" + +#: ../dashboard_sessions.rst:48 +msgid "" +"You can use applications such as Memcached or Redis for external caching. " +"These applications offer persistence and shared storage and are useful for " +"small-scale deployments and development." +msgstr "" + +#: ../dashboard_sessions.rst:53 +msgid "Memcached" +msgstr "" + +#: ../dashboard_sessions.rst:54 +msgid "" +"Memcached is a high-performance and distributed memory object caching system " +"providing in-memory key-value store for small chunks of arbitrary data." +msgstr "" + +#: ../dashboard_sessions.rst:58 ../dashboard_sessions.rst:78 +msgid "Requirements:" +msgstr "" + +#: ../dashboard_sessions.rst:60 +msgid "Memcached service running and accessible." +msgstr "" + +#: ../dashboard_sessions.rst:61 +msgid "Python module ``python-memcached`` installed." +msgstr "" + +#: ../dashboard_sessions.rst:63 ../dashboard_sessions.rst:83 +msgid "Enabled by::" +msgstr "" + +#: ../dashboard_sessions.rst:74 +msgid "Redis" +msgstr "" + +#: ../dashboard_sessions.rst:75 +msgid "" +"Redis is an open source, BSD licensed, advanced key-value store. It is often " +"referred to as a data structure server." +msgstr "" + +#: ../dashboard_sessions.rst:80 +msgid "Redis service running and accessible." +msgstr "" + +#: ../dashboard_sessions.rst:81 +msgid "Python modules ``redis`` and ``django-redis`` installed." +msgstr "" + +#: ../dashboard_sessions.rst:97 +msgid "Initialize and configure the database" +msgstr "" + +#: ../dashboard_sessions.rst:98 +msgid "" +"Database-backed sessions are scalable, persistent, and can be made high-" +"concurrency and highly-available." +msgstr "" + +#: ../dashboard_sessions.rst:101 +msgid "" +"However, database-backed sessions are one of the slower session storages and " +"incur a high overhead under heavy usage. Proper configuration of your " +"database deployment can also be a substantial undertaking and is far beyond " +"the scope of this documentation." +msgstr "" + +#: ../dashboard_sessions.rst:106 +msgid "Start the mysql command-line client::" +msgstr "" + +#: ../dashboard_sessions.rst:110 +msgid "Enter the MySQL root user's password when prompted." +msgstr "" + +#: ../dashboard_sessions.rst:111 +msgid "To configure the MySQL database, create the dash database::" +msgstr "" + +#: ../dashboard_sessions.rst:115 +msgid "" +"Create a MySQL user for the newly created dash database that has full " +"control of the database. Replace DASH\\_DBPASS with a password for the new " +"user::" +msgstr "" + +#: ../dashboard_sessions.rst:122 +msgid "Enter ``quit`` at the ``mysql>`` prompt to exit MySQL." +msgstr "" + +#: ../dashboard_sessions.rst:124 +msgid "" +"In the :file:`local_settings` file (on Fedora/RHEL/CentOS: :file:`/etc/" +"openstack-dashboard/local_settings`, on Ubuntu/Debian: :file:`/etc/openstack-" +"dashboard/local_settings.py`, and on openSUSE: :file:`/srv/www/openstack-" +"dashboard/openstack_dashboard/local/local_settings.py`), change these " +"options::" +msgstr "" + +#: ../dashboard_sessions.rst:143 +msgid "" +"After configuring the :file:`local_settings` file as shown, you can run the " +"``manage.py syncdb`` command to populate this newly created database::" +msgstr "" + +#: ../dashboard_sessions.rst:148 +msgid "" +"Note on openSUSE the path is :file:`/srv/www/openstack-dashboard/manage.py`." +msgstr "" + +#: ../dashboard_sessions.rst:150 +msgid "The following output is returned::" +msgstr "" + +#: ../dashboard_sessions.rst:157 +msgid "" +"To avoid a warning when you restart Apache on Ubuntu, create a :file:" +"`blackhole` directory in the Dashboard directory, as follows::" +msgstr "" + +#: ../dashboard_sessions.rst:162 +msgid "Restart and refresh Apache:" +msgstr "" + +#: ../dashboard_sessions.rst:164 +msgid "On Ubuntu::" +msgstr "" + +#: ../dashboard_sessions.rst:168 +msgid "On Fedora/RHEL/CentOS::" +msgstr "" + +#: ../dashboard_sessions.rst:173 +msgid "On openSUSE::" +msgstr "" + +#: ../dashboard_sessions.rst:177 +msgid "" +"On Ubuntu, restart the nova-api service to ensure that the API server can " +"connect to the Dashboard without error::" +msgstr "" + +#: ../dashboard_sessions.rst:183 +msgid "Cached database" +msgstr "" + +#: ../dashboard_sessions.rst:184 +msgid "" +"To mitigate the performance issues of database queries, you can use the " +"Django ``cached_db`` session back end, which utilizes both your database and " +"caching infrastructure to perform write-through caching and efficient " +"retrieval." +msgstr "" + +#: ../dashboard_sessions.rst:189 +msgid "" +"Enable this hybrid setting by configuring both your database and cache, as " +"discussed previously. Then, set the following value::" +msgstr "" + +#: ../dashboard_sessions.rst:195 +msgid "Cookies" +msgstr "" + +#: ../dashboard_sessions.rst:196 +msgid "" +"If you use Django 1.4 or later, the ``signed_cookies`` back end avoids " +"server load and scaling problems." +msgstr "" + +#: ../dashboard_sessions.rst:199 +msgid "" +"This back end stores session data in a cookie, which is stored by the user's " +"browser. The back end uses a cryptographic signing technique to ensure " +"session data is not tampered with during transport. This is not the same as " +"encryption; session data is still readable by an attacker." +msgstr "" + +#: ../dashboard_sessions.rst:204 +msgid "" +"The pros of this engine are that it requires no additional dependencies or " +"infrastructure overhead, and it scales indefinitely as long as the quantity " +"of session data being stored fits into a normal cookie." +msgstr "" + +#: ../dashboard_sessions.rst:208 +msgid "" +"The biggest downside is that it places session data into storage on the " +"user's machine and transports it over the wire. It also limits the quantity " +"of session data that can be stored." +msgstr "" + +#: ../dashboard_sessions.rst:212 +msgid "" +"See the Django `cookie-based sessions `__ documentation." +msgstr "" + +# #-#-#-#-# database.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +# #-#-#-#-# telemetry-data-collection.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +#: ../database.rst:8 ../telemetry-data-collection.rst:1044 +msgid "Database" +msgstr "" + +#: ../database.rst:10 +msgid "The Database service provides database management features." +msgstr "" + +#: ../database.rst:15 +msgid "" +"The Database service provides scalable and reliable cloud provisioning " +"functionality for both relational and non-relational database engines. Users " +"can quickly and easily use database features without the burden of handling " +"complex administrative tasks. Cloud users and database administrators can " +"provision and manage multiple database instances as needed." +msgstr "" + +#: ../database.rst:22 +msgid "" +"The Database service provides resource isolation at high performance levels, " +"and automates complex administrative tasks such as deployment, " +"configuration, patching, backups, restores, and monitoring." +msgstr "" + +#: ../database.rst:28 +msgid "Create a datastore" +msgstr "" + +#: ../database.rst:30 +msgid "" +"An administrative user can create datastores for a variety of databases." +msgstr "" + +#: ../database.rst:33 +msgid "" +"This section assumes you do not yet have a MySQL datastore, and shows you " +"how to create a MySQL datastore and populate it with a MySQL 5.5 datastore " +"version." +msgstr "" + +#: ../database.rst:39 +msgid "**To create a datastore**" +msgstr "" + +#: ../database.rst:41 +msgid "**Create a trove image**" +msgstr "" + +#: ../database.rst:43 +msgid "" +"Create an image for the type of database you want to use, for example, " +"MySQL, MongoDB, Cassandra." +msgstr "" + +#: ../database.rst:46 +msgid "" +"This image must have the trove guest agent installed, and it must have the :" +"file:`trove-guestagent.conf` file configured to connect to your OpenStack " +"environment. To configure :file:`trove-guestagent.conf`, add the following " +"lines to :file:`trove-guestagent.conf` on the guest instance you are using " +"to build your image:" +msgstr "" + +#: ../database.rst:62 +msgid "" +"This example assumes you have created a MySQL 5.5 image called ``mysql-5.5." +"qcow2``." +msgstr "" + +#: ../database.rst:65 +msgid "**Register image with Image service**" +msgstr "" + +#: ../database.rst:67 +msgid "You need to register your guest image with the Image service." +msgstr "" + +#: ../database.rst:69 +msgid "" +"In this example, you use the glance :command:`image-create` command to " +"register a ``mysql-5.5.qcow2`` image::" +msgstr "" + +#: ../database.rst:95 +msgid "**Create the datastore**" +msgstr "" + +#: ../database.rst:97 +msgid "" +"Create the datastore that will house the new image. To do this, use the :" +"command:`trove-manage` :command:`datastore_update` command." +msgstr "" + +#: ../database.rst:100 ../database.rst:138 +msgid "This example uses the following arguments:" +msgstr "" + +#: ../database.rst:106 ../database.rst:144 +msgid "Argument" +msgstr "" + +#: ../database.rst:109 ../database.rst:148 +msgid "config file" +msgstr "" + +#: ../database.rst:110 ../database.rst:149 +msgid "The configuration file to use." +msgstr "" + +#: ../database.rst:111 ../database.rst:150 +msgid ":option:`--config-file=/etc/trove/trove.conf`" +msgstr "" + +#: ../database.rst:113 +msgid "Name you want to use for this datastore." +msgstr "" + +#: ../database.rst:114 ../database.rst:155 ../database.rst:172 +msgid "``mysql``" +msgstr "" + +#: ../database.rst:115 +msgid "default version" +msgstr "" + +#: ../database.rst:116 +msgid "" +"You can attach multiple versions/images to a datastore. For example, you " +"might have a MySQL 5.5 version and a MySQL 5.6 version. You can designate " +"one version as the default, which the system uses if a user does not " +"explicitly request a specific version." +msgstr "" + +#: ../database.rst:121 ../database.rst:184 +msgid "``\"\"``" +msgstr "" + +#: ../database.rst:123 +msgid "" +"At this point, you do not yet have a default version, so pass in an empty " +"string." +msgstr "" + +# #-#-#-#-# database.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +# #-#-#-#-# objectstorage_ringbuilder.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +#: ../database.rst:128 ../database.rst:197 +#: ../objectstorage_ringbuilder.rst:105 +msgid "Example::" +msgstr "" + +#: ../database.rst:132 +msgid "**Add a version to the new datastore**" +msgstr "" + +#: ../database.rst:134 +msgid "" +"Now that you have a MySQL datastore, you can add a version to it, using the " +"trove-manage :command:`datastore_version_update` command. The version " +"indicates which guest image to use." +msgstr "" + +#: ../database.rst:152 +msgid "datastore" +msgstr "" + +#: ../database.rst:153 +msgid "" +"The name of the datastore you just created via trove-manage :command:" +"`datastore_update`." +msgstr "" + +#: ../database.rst:157 +msgid "version name" +msgstr "" + +#: ../database.rst:158 +msgid "The name of the version you are adding to the datastore." +msgstr "" + +#: ../database.rst:159 +msgid "``mysql-5.5``" +msgstr "" + +#: ../database.rst:161 +msgid "datastore manager" +msgstr "" + +#: ../database.rst:162 +msgid "" +"Which datastore manager to use for this version. Typically, the datastore " +"manager is identified by one of the following strings, depending on the " +"database:" +msgstr "" + +#: ../database.rst:166 +msgid "mysql" +msgstr "" + +#: ../database.rst:167 +msgid "redis" +msgstr "" + +#: ../database.rst:168 +msgid "mongodb" +msgstr "" + +#: ../database.rst:169 +msgid "cassandra" +msgstr "" + +#: ../database.rst:170 +msgid "couchbase" +msgstr "" + +#: ../database.rst:171 +msgid "percona" +msgstr "" + +#: ../database.rst:174 +msgid "glance ID" +msgstr "" + +#: ../database.rst:175 +msgid "" +"The ID of the guest image you just added to the Identity service. You can " +"get this ID by using the glance :command:`image-show` IMAGE_NAME command." +msgstr "" + +#: ../database.rst:178 +msgid "bb75f870-0c33-4907-8467-1367f8cb15b6" +msgstr "" + +#: ../database.rst:180 +msgid "packages" +msgstr "" + +#: ../database.rst:181 +msgid "" +"If you want to put additional packages on each guest that you create with " +"this datastore version, you can list the package names here." +msgstr "" + +#: ../database.rst:186 +msgid "" +"In this example, the guest image already contains all the required packages, " +"so leave this argument empty." +msgstr "" + +# #-#-#-#-# database.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +# #-#-#-#-# ts-eql-volume-size.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +#: ../database.rst:189 ../ts-eql-volume-size.rst:113 +msgid "active" +msgstr "" + +#: ../database.rst:191 +msgid "Set this to either 1 or 0:" +msgstr "" + +#: ../database.rst:191 +msgid "``1`` = active" +msgstr "" + +#: ../database.rst:192 +msgid "``0`` = disabled" +msgstr "" + +#: ../database.rst:193 +msgid "1" +msgstr "" + +#: ../database.rst:201 +msgid "" +"**Optional.** Set your new version as the default version. To do this, use " +"the trove-manage :command:`datastore_update` command again, this time " +"specifying the version you just created." +msgstr "" + +#: ../database.rst:209 +msgid "**Load validation rules for configuration groups**" +msgstr "" + +#: ../database.rst:213 +msgid "**Applies only to MySQL and Percona datastores**" +msgstr "" + +#: ../database.rst:215 +msgid "" +"If you just created a MySQL or Percona datastore, then you need to load the " +"appropriate validation rules, as described in this step." +msgstr "" + +#: ../database.rst:218 +msgid "If you just created a different datastore, skip this step." +msgstr "" + +#: ../database.rst:220 +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:224 +msgid "" +"When you set up a configuration group using the trove :command:" +"`configuration-create` command, this command compares the configuration " +"values you are setting against a list of valid configuration values that are " +"stored in the :file:`validation-rules.json` file." +msgstr "" + +#: ../database.rst:233 +msgid "Operating System" +msgstr "" + +#: ../database.rst:234 +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:235 ../networking_adv-features.rst:609 +msgid "Notes" +msgstr "" + +#: ../database.rst:237 +msgid "Ubuntu 14.04" +msgstr "" + +#: ../database.rst:238 +msgid ":file:`/usr/lib/python2.7/dist-packages/trove/templates/DATASTORE_NAME`" +msgstr "" + +#: ../database.rst:239 ../database.rst:245 +msgid "" +"DATASTORE_NAME is the name of either the MySQL datastore or the Percona " +"datastore. This is typically either ``mysql`` or ``percona``." +msgstr "" + +#: ../database.rst:243 +msgid "RHEL 7, CentOS 7, Fedora 20, and Fedora 21" +msgstr "" + +#: ../database.rst:244 +msgid ":file:`/usr/lib/python2.7/site-packages/trove/templates/DATASTORE_NAME`" +msgstr "" + +#: ../database.rst:250 +msgid "" +"Therefore, as part of creating a datastore, you need to load the :file:" +"`validation-rules.json` file, using the :command:`trove-manage` :command:" +"`db_load_datastore_config_parameters` command. This command takes the " +"following arguments:" +msgstr "" + +#: ../database.rst:255 +msgid "Datastore name" +msgstr "" + +#: ../database.rst:256 +msgid "Datastore version" +msgstr "" + +#: ../database.rst:257 +msgid "Full path to the :file:`validation-rules.json` file" +msgstr "" + +#: ../database.rst:261 +msgid "" +"This example loads the :file:`validation-rules.json` file for a MySQL " +"database on Ubuntu 14.04::" +msgstr "" + +#: ../database.rst:266 +msgid "**Validate datastore**" +msgstr "" + +#: ../database.rst:268 +msgid "" +"To validate your new datastore and version, start by listing the datastores " +"on your system::" +msgstr "" + +#: ../database.rst:279 +msgid "" +"Take the ID of the MySQL datastore and pass it in with the :command:" +"`datastore-version-list` command::" +msgstr "" + +#: ../database.rst:290 +msgid "Configure a cluster" +msgstr "" + +#: ../database.rst:292 +msgid "" +"An administrative user can configure various characteristics of a MongoDB " +"cluster." +msgstr "" + +#: ../database.rst:295 +msgid "**Query routers and config servers**" +msgstr "" + +#: ../database.rst:297 +msgid "" +"**Background.** Each cluster includes at least one query router and one " +"config server. Query routers and config servers count against your quota. " +"When you delete a cluster, the system deletes the associated query router(s) " +"and config server(s)." +msgstr "" + +#: ../database.rst:302 +msgid "" +"**Configuration.** By default, the system creates one query router and one " +"config server per cluster. You can change this by editing the :file:`/etc/" +"trove/trove.conf` file. These settings are in the ``mongodb`` section of the " +"file:" +msgstr "" + +#: ../database.rst:311 +msgid "Setting" +msgstr "" + +#: ../database.rst:312 +msgid "Valid values are:" +msgstr "" + +#: ../database.rst:314 +msgid "num_config_servers_per_cluster" +msgstr "" + +#: ../database.rst:315 ../database.rst:318 +msgid "1 or 3" +msgstr "" + +#: ../database.rst:317 +msgid "num_query_routers_per_cluster" +msgstr "" + +#: ../identity_auth_token_middleware.rst:2 +msgid "Authentication middleware with user name and password" +msgstr "" + +#: ../identity_auth_token_middleware.rst:4 +msgid "" +"You can also configure Identity authentication middleware using the :code:" +"`admin_user` and :code:`admin_password` options." +msgstr "" + +#: ../identity_auth_token_middleware.rst:9 +msgid "" +"The :code:`admin_token` option is deprecated and no longer used for " +"configuring auth_token middleware." +msgstr "" + +#: ../identity_auth_token_middleware.rst:12 +msgid "" +"For services that have a separate paste-deploy :file:`.ini` file, you can " +"configure the authentication middleware in the ``[keystone_authtoken]`` " +"section of the main configuration file, such as :file:`nova.conf`. In " +"Compute, for example, you can remove the middleware parameters from :file:" +"`api-paste.ini`, as follows:" +msgstr "" + +#: ../identity_auth_token_middleware.rst:24 +msgid "And set the following values in :file:`nova.conf` as follows:" +msgstr "" + +#: ../identity_auth_token_middleware.rst:41 +msgid "" +"The middleware parameters in the paste config take priority. You must remove " +"them to use the values in the ``[keystone_authtoken]`` section." +msgstr "" + +#: ../identity_auth_token_middleware.rst:47 +msgid "" +"Comment out any :code:`auth_host`, :code:`auth_port`, and :code:" +"`auth_protocol` options because the :code:`identity_uri` option replaces " +"them." +msgstr "" + +#: ../identity_auth_token_middleware.rst:51 +msgid "" +"This sample paste config filter makes use of the :code:`admin_user` and :" +"code:`admin_password` options:" +msgstr "" + +#: ../identity_auth_token_middleware.rst:66 +msgid "" +"Using this option requires an admin tenant/role relationship. The admin user " +"is granted access to the admin role on the admin tenant." +msgstr "" + +#: ../identity_auth_token_middleware.rst:71 +msgid "" +"Comment out any ``auth_host``, ``auth_port``, and ``auth_protocol`` options " +"because the ``identity_uri`` option replaces them." +msgstr "" + +#: ../identity_concepts.rst:3 +msgid "Identity concepts" +msgstr "" + +#: ../identity_concepts.rst:6 +msgid "" +"The process of confirming the identity of a user. To confirm an incoming " +"request, OpenStack Identity validates a set of credentials that the user " +"supplies. Initially, these credentials are a user name and password or a " +"user name and API key. When OpenStack Identity validates user credentials, " +"it issues an authentication token that the user provides in subsequent " +"requests." +msgstr "" + +#: ../identity_concepts.rst:11 +msgid "Authentication" +msgstr "" + +#: ../identity_concepts.rst:14 +msgid "" +"Data that confirms the identity of the user. For example, user name and " +"password, user name and API key, or an authentication token that the " +"Identity service provides." +msgstr "" + +#: ../identity_concepts.rst:16 +msgid "Credentials" +msgstr "" + +#: ../identity_concepts.rst:19 +msgid "" +"An Identity service API v3 entity. Represents a collection of projects and " +"users that defines administrative boundaries for the management of Identity " +"entities. A domain, which can represent an individual, company, or operator-" +"owned space, exposes administrative activities directly to system users. " +"Users can be granted the administrator role for a domain. A domain " +"administrator can create projects, users, and groups in a domain and assign " +"roles to users and groups in a domain." +msgstr "" + +#: ../identity_concepts.rst:26 +msgid "Domain" +msgstr "" + +#: ../identity_concepts.rst:29 +msgid "" +"A network-accessible address, usually a URL, through which you can access a " +"service. If you are using an extension for templates, you can create an " +"endpoint template that represents the templates of all consumable services " +"that are available across the regions." +msgstr "" + +#: ../identity_concepts.rst:32 +msgid "Endpoint" +msgstr "" + +#: ../identity_concepts.rst:35 +msgid "" +"An Identity service API v3 entity. Represents a collection of users that are " +"owned by a domain. A group role granted to a domain or project applies to " +"all users in the group. Adding users to, or removing users from, a group " +"respectively grants, or revokes, their role and authentication to the " +"associated domain or project." +msgstr "" + +# #-#-#-#-# identity_concepts.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +# #-#-#-#-# networking_adv-features.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +#: ../identity_concepts.rst:39 ../networking_adv-features.rst:606 +msgid "Group" +msgstr "" + +#: ../identity_concepts.rst:42 +msgid "" +"A command-line interface for several OpenStack services including the " +"Identity API. For example, a user can run the :command:`openstack service " +"create` and :command:`openstack endpoint create` commands to register " +"services in her OpenStack installation." +msgstr "" + +#: ../identity_concepts.rst:46 +msgid "OpenStackClient" +msgstr "" + +#: ../identity_concepts.rst:49 +msgid "" +"A container that groups or isolates resources or identity objects. Depending " +"on the service operator, a project might map to a customer, account, " +"organization, or tenant." +msgstr "" + +#: ../identity_concepts.rst:51 +msgid "Project" +msgstr "" + +#: ../identity_concepts.rst:54 +msgid "" +"An Identity service API v3 entity. Represents a general division in an " +"OpenStack deployment. You can associate zero or more sub-regions with a " +"region to make a tree-like structured hierarchy. Although a region does not " +"have a geographical connotation, a deployment can use a geographical name " +"for a region, such as ``us-east``." +msgstr "" + +#: ../identity_concepts.rst:58 +msgid "Region" +msgstr "" + +#: ../identity_concepts.rst:61 +msgid "" +"A personality with a defined set of user rights and privileges to perform a " +"specific set of operations. The Identity service issues a token that " +"includes a list of roles to a user. When a user calls a service, that " +"service interprets the set of user roles and determines to which operations " +"or resources each role grants access." +msgstr "" + +#: ../identity_concepts.rst:66 +msgid "Role" +msgstr "" + +#: ../identity_concepts.rst:69 +msgid "" +"An OpenStack service, such as Compute (nova), Object Storage (swift), or " +"Image service (glance), that provides one or more endpoints through which " +"users can access resources and perform operations." +msgstr "" + +#: ../identity_concepts.rst:72 +msgid "Service" +msgstr "" + +#: ../identity_concepts.rst:75 +msgid "" +"An alpha-numeric text string that enables access to OpenStack APIs and " +"resources. A token may be revoked at any time and is valid for a finite " +"duration. While OpenStack Identity supports token-based authentication in " +"this release, it intends to support additional protocols in the future. " +"OpenStack Identity is an integration service that does not aspire to be a " +"full-fledged identity store and management solution." +msgstr "" + +#: ../identity_concepts.rst:81 +msgid "Token" +msgstr "" + +#: ../identity_concepts.rst:84 +msgid "" +"A digital representation of a person, system, or service that uses OpenStack " +"cloud services. The Identity service validates that incoming requests are " +"made by the user who claims to be making the call. Users have a login and " +"can access resources by using assigned tokens. Users can be directly " +"assigned to a particular project and behave as if they are contained in that " +"project." +msgstr "" + +#: ../identity_concepts.rst:89 +msgid "User" +msgstr "" + +#: ../identity_concepts.rst:92 +msgid "User management" +msgstr "" + +#: ../identity_concepts.rst:94 +msgid "Identity user management examples:" +msgstr "" + +#: ../identity_concepts.rst:96 +msgid "Create a user named ``alice``:" +msgstr "" + +#: ../identity_concepts.rst:102 +msgid "Create a project named ``acme``:" +msgstr "" + +#: ../identity_concepts.rst:108 +msgid "Create a domain named ``emea``:" +msgstr "" + +#: ../identity_concepts.rst:114 +msgid "Create a role named ``compute-user``:" +msgstr "" + +#: ../identity_concepts.rst:122 +msgid "" +"Individual services, such as Compute and the Image service, assign meaning " +"to roles. In the Identity service, a role is simply a name." +msgstr "" + +#: ../identity_concepts.rst:126 +msgid "" +"The Identity service assigns a tenant and a role to a user. You might assign " +"the ``compute-user`` role to the ``alice`` user in the ``acme`` tenant:" +msgstr "" + +#: ../identity_concepts.rst:161 +msgid "" +"A user can have different roles in different tenants. For example, Alice " +"might also have the ``admin`` role in the ``Cyberdyne`` tenant. A user can " +"also have multiple roles in the same tenant." +msgstr "" + +#: ../identity_concepts.rst:165 +msgid "" +"The :file:`/etc/[SERVICE_CODENAME]/policy.json` file controls the tasks that " +"users can perform for a given service. For example, the :file:`/etc/nova/" +"policy.json` file specifies the access policy for the Compute service, the :" +"file:`/etc/glance/policy.json` file specifies the access policy for the " +"Image service, and the :file:`/etc/keystone/policy.json` file specifies the " +"access policy for the Identity service." +msgstr "" + +#: ../identity_concepts.rst:173 +msgid "" +"The default :file:`policy.json` files in the Compute, Identity, and Image " +"services recognize only the ``admin`` role. Any user with any role in a " +"tenant can access all operations that do not require the ``admin`` role." +msgstr "" + +#: ../identity_concepts.rst:178 +msgid "" +"To restrict users from performing operations in, for example, the Compute " +"service, you must create a role in the Identity service and then modify the :" +"file:`/etc/nova/policy.json` file so that this role is required for Compute " +"operations." +msgstr "" + +#: ../identity_concepts.rst:183 +msgid "" +"For example, the following line in the :file:`/etc/nova/policy.json` file " +"does not restrict which users can create volumes:" +msgstr "" + +#: ../identity_concepts.rst:190 +msgid "" +"If the user has any role in a tenant, he can create volumes in that tenant." +msgstr "" + +#: ../identity_concepts.rst:193 +msgid "" +"To restrict the creation of volumes to users who have the ``compute-user`` " +"role in a particular tenant, you add ``\"role:compute-user\"``:" +msgstr "" + +#: ../identity_concepts.rst:200 +msgid "" +"To restrict all Compute service requests to require this role, the resulting " +"file looks like:" +msgstr "" + +#: ../identity_concepts.rst:305 +msgid "Service management" +msgstr "" + +#: ../identity_concepts.rst:307 +msgid "" +"The Identity service provides identity, token, catalog, and policy services. " +"It consists of:" +msgstr "" + +#: ../identity_concepts.rst:311 +msgid "" +"Can be run in a WSGI-capable web server such as Apache httpd to provide the " +"Identity service. The service and administrative APIs are run as separate " +"instances of the WSGI service." +msgstr "" + +#: ../identity_concepts.rst:313 +msgid "keystone Web Server Gateway Interface (WSGI) service" +msgstr "" + +#: ../identity_concepts.rst:316 +msgid "" +"Each has a pluggable back end that allow different ways to use the " +"particular service. Most support standard back ends like LDAP or SQL." +msgstr "" + +#: ../identity_concepts.rst:317 +msgid "Identity service functions" +msgstr "" + +#: ../identity_concepts.rst:320 +msgid "" +"Starts both the service and administrative APIs in a single process. Using " +"federation with keystone-all is not supported. keystone-all is deprecated in " +"favor of the WSGI service." +msgstr "" + +#: ../identity_concepts.rst:322 +msgid "keystone-all" +msgstr "" + +#: ../identity_concepts.rst:324 +msgid "" +"The Identity service also maintains a user that corresponds to each service, " +"such as, a user named ``nova`` for the Compute service, and a special " +"service tenant called ``service``." +msgstr "" + +#: ../identity_concepts.rst:328 +msgid "" +"For information about how to create services and endpoints, see the " +"`OpenStack Admin User Guide `__." +msgstr "" + +#: ../identity_concepts.rst:332 +msgid "Groups" +msgstr "" + +#: ../identity_concepts.rst:334 +msgid "" +"A group is a collection of users in a domain. Administrators can create " +"groups and add users to them. A role can then be assigned to the group, " +"rather than individual users. Groups were introduced with the Identity API " +"v3." +msgstr "" + +#: ../identity_concepts.rst:339 +msgid "Identity API V3 provides the following group-related operations:" +msgstr "" + +#: ../identity_concepts.rst:341 +msgid "Create a group" +msgstr "" + +#: ../identity_concepts.rst:343 +msgid "Delete a group" +msgstr "" + +#: ../identity_concepts.rst:345 +msgid "Update a group (change its name or description)" +msgstr "" + +#: ../identity_concepts.rst:347 +msgid "Add a user to a group" +msgstr "" + +#: ../identity_concepts.rst:349 +msgid "Remove a user from a group" +msgstr "" + +#: ../identity_concepts.rst:351 +msgid "List group members" +msgstr "" + +#: ../identity_concepts.rst:353 +msgid "List groups for a user" +msgstr "" + +#: ../identity_concepts.rst:355 +msgid "Assign a role on a tenant to a group" +msgstr "" + +#: ../identity_concepts.rst:357 +msgid "Assign a role on a domain to a group" +msgstr "" + +#: ../identity_concepts.rst:359 +msgid "Query role assignments to groups" +msgstr "" + +#: ../identity_concepts.rst:363 +msgid "" +"The Identity service server might not allow all operations. For example, if " +"you use the Identity server with the LDAP Identity back end and group " +"updates are disabled, a request to create, delete, or update a group fails." +msgstr "" + +#: ../identity_concepts.rst:368 +msgid "Here are a couple of examples:" +msgstr "" + +#: ../identity_concepts.rst:370 +msgid "" +"Group A is granted Role A on Tenant A. If User A is a member of Group A, " +"when User A gets a token scoped to Tenant A, the token also includes Role A." +msgstr "" + +#: ../identity_concepts.rst:374 +msgid "" +"Group B is granted Role B on Domain B. If User B is a member of Domain B, if " +"User B gets a token scoped to Domain B, the token also includes Role B." +msgstr "" + +#: ../identity_example_usage.rst:3 +msgid "Example usage" +msgstr "" + +#: ../identity_example_usage.rst:5 +msgid "" +"The ``keystone`` client is set up to expect commands in the general form of " +"``keystone command argument``, followed by flag-like keyword arguments to " +"provide additional (often optional) information. For example, the :command:" +"`user-list` and :command:`tenant-create` commands can be invoked as follows:" +msgstr "" + +#: ../identity_logging.rst:5 +msgid "" +"You configure logging externally to the rest of Identity. The name of the " +"file specifying the logging configuration is set using the ``log_config`` " +"option in the ``[DEFAULT]`` section of the :file:`keystone.conf` file. To " +"route logging through syslog, set ``use_syslog=true`` in the ``[DEFAULT]`` " +"section." +msgstr "" + +#: ../identity_logging.rst:11 +msgid "" +"A sample logging configuration file is available with the project in :file:" +"`etc/logging.conf.sample`. Like other OpenStack projects, Identity uses the " +"Python logging module, which provides extensive configuration options that " +"let you define the output levels and formats." +msgstr "" + +#: ../identity_management.rst:5 +msgid "Identity management" +msgstr "" + +#: ../identity_management.rst:7 +msgid "" +"OpenStack Identity, code-named keystone, is the default identity management " +"system for OpenStack. After you install Identity, you configure it through " +"the :file:`/etc/keystone/keystone.conf` configuration file and, possibly, a " +"separate logging configuration file. You initialize data into Identity by " +"using the ``keystone`` command-line client." +msgstr "" + +#: ../identity_service_api_protection.rst:3 +msgid "Identity API protection with role-based access control (RBAC)" +msgstr "" + +#: ../identity_service_api_protection.rst:5 +msgid "" +"Like most OpenStack projects, Identity supports the protection of its APIs " +"by defining policy rules based on an RBAC approach. Identity stores a " +"reference to a policy JSON file in the main Identity configuration file, :" +"file:`keystone.conf`. Typically this file is named ``policy.json``, and " +"contains the rules for which roles have access to certain actions in defined " +"services." +msgstr "" + +#: ../identity_service_api_protection.rst:12 +msgid "" +"Each Identity API v3 call has a line in the policy file that dictates which " +"level of governance of access applies." +msgstr "" + +#: ../identity_service_api_protection.rst:21 +msgid "" +"``RULE_STATEMENT`` can contain ``RULE_STATEMENT`` or ``MATCH_STATEMENT``." +msgstr "" + +#: ../identity_service_api_protection.rst:24 +msgid "" +"``MATCH_STATEMENT`` is a set of identifiers that must match between the " +"token provided by the caller of the API and the parameters or target " +"entities of the API call in question. For example:" +msgstr "" + +#: ../identity_service_api_protection.rst:32 +msgid "" +"Indicates that to create a user, you must have the admin role in your token. " +"The :code:`domain_id` in your token must match the :code:`domain_id` in the " +"user object that you are trying to create, which implies this must be a " +"domain-scoped token. In other words, you must have the admin role on the " +"domain in which you are creating the user, and the token that you use must " +"be scoped to that domain." +msgstr "" + +#: ../identity_service_api_protection.rst:40 +msgid "Each component of a match statement uses this format:" +msgstr "" + +#: ../identity_service_api_protection.rst:46 +msgid "The Identity service expects these attributes:" +msgstr "" + +#: ../identity_service_api_protection.rst:48 +msgid "Attributes from token:" +msgstr "" + +# #-#-#-#-# identity_service_api_protection.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +# #-#-#-#-# telemetry-data-retrieval.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +#: ../identity_service_api_protection.rst:50 +#: ../telemetry-data-retrieval.rst:154 +msgid "``user_id``" +msgstr "" + +#: ../identity_service_api_protection.rst:51 +msgid "``domain_id``" +msgstr "" + +# #-#-#-#-# identity_service_api_protection.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +# #-#-#-#-# telemetry-data-retrieval.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +#: ../identity_service_api_protection.rst:52 +#: ../telemetry-data-retrieval.rst:150 +msgid "``project_id``" +msgstr "" + +#: ../identity_service_api_protection.rst:54 +msgid "" +"The ``project_id`` attribute requirement depends on the scope, and the list " +"of roles you have within that scope." +msgstr "" + +#: ../identity_service_api_protection.rst:57 +msgid "Attributes related to API call:" +msgstr "" + +#: ../identity_service_api_protection.rst:59 +msgid "``user.domain_id``" +msgstr "" + +#: ../identity_service_api_protection.rst:60 +msgid "Any parameters passed into the API call" +msgstr "" + +#: ../identity_service_api_protection.rst:61 +msgid "Any filters specified in the query string" +msgstr "" + +#: ../identity_service_api_protection.rst:63 +msgid "" +"You reference attributes of objects passed with an object.attribute syntax " +"(such as, ``user.domain_id``). The target objects of an API are also " +"available using a target.object.attribute syntax. For instance:" +msgstr "" + +#: ../identity_service_api_protection.rst:71 +msgid "" +"would ensure that Identity only deletes the user object in the same domain " +"as the provided token." +msgstr "" + +#: ../identity_service_api_protection.rst:74 +msgid "" +"Every target object has an ``id`` and a ``name`` available as ``target." +"OBJECT.id`` and ``target.OBJECT.name``. Identity retrieves other attributes " +"from the database, and the attributes vary between object types. The " +"Identity service filters out some database fields, such as user passwords." +msgstr "" + +#: ../identity_service_api_protection.rst:80 +msgid "List of object attributes:" +msgstr "" + +#: ../identity_service_api_protection.rst:115 +msgid "" +"The default :file:`policy.json` file supplied provides a somewhat basic " +"example of API protection, and does not assume any particular use of " +"domains. Refer to :file:`policy.v3cloudsample.json` as an example of multi-" +"domain configuration installations where a cloud provider wants to delegate " +"administration of the contents of a domain to a particular :code:`admin " +"domain`. This example policy file also shows the use of an :code:" +"`admin_domain` to allow a cloud provider to enable cloud administrators to " +"have wider access across the APIs." +msgstr "" + +#: ../identity_service_api_protection.rst:124 +msgid "" +"A clean installation could start with the standard policy file, to allow " +"creation of the :code:`admin_domain` with the first users within it. You " +"could then obtain the :code:`domain_id` of the admin domain, paste the ID " +"into a modified version of :file:`policy.v3cloudsample.json`, and then " +"enable it as the main policy file." +msgstr "" + +#: ../identity_start.rst:2 +msgid "Start the Identity services" +msgstr "" + +#: ../identity_start.rst:4 +msgid "To start the services for Identity, run the following command:" +msgstr "" + +#: ../identity_start.rst:10 +msgid "" +"This command starts two wsgi.Server instances configured by the :file:" +"`keystone.conf` file as described previously. One of these wsgi servers is :" +"code:`admin` (the administration API) and the other is :code:`main` (the " +"primary/public API interface). Both run in a single process." +msgstr "" + +#: ../identity_troubleshoot.rst:3 +msgid "Troubleshoot the Identity service" +msgstr "" + +#: ../identity_troubleshoot.rst:5 +msgid "" +"To troubleshoot the Identity service, review the logs in the ``/var/log/" +"keystone/keystone.log`` file." +msgstr "" + +#: ../identity_troubleshoot.rst:13 +msgid "" +"The logs show the components that have come in to the WSGI request, and " +"ideally show an error that explains why an authorization request failed. If " +"you do not see the request in the logs, run keystone with the :option:`--" +"debug` parameter. Pass the :option:`--debug` parameter before the command " +"parameters." +msgstr "" + +#: ../identity_troubleshoot.rst:20 +msgid "Debug PKI middleware" +msgstr "" + +#: ../identity_troubleshoot.rst:22 +msgid "" +"If you receive an ``Invalid OpenStack Identity Credentials`` message when " +"you talk to an OpenStack service, it might be caused by the changeover from " +"UUID tokens to PKI tokens in the Grizzly release. Learn how to troubleshoot " +"this error." +msgstr "" + +#: ../identity_troubleshoot.rst:27 +msgid "" +"The PKI-based token validation scheme relies on certificates from Identity " +"that are fetched through HTTP and stored in a local directory. The location " +"for this directory is specified by the ``signing_dir`` configuration option. " +"In your services configuration file, look for a section like this:" +msgstr "" + +#: ../identity_troubleshoot.rst:43 +msgid "" +"The first thing to check is that the ``signing_dir`` does, in fact, exist. " +"If it does, check for certificate files:" +msgstr "" + +#: ../identity_troubleshoot.rst:59 +msgid "" +"This directory contains two certificates and the token revocation list. If " +"these files are not present, your service cannot fetch them from Identity. " +"To troubleshoot, try to talk to Identity to make sure it correctly serves " +"files, as follows:" +msgstr "" + +#: ../identity_troubleshoot.rst:68 +msgid "This command fetches the signing certificate:" +msgstr "" + +#: ../identity_troubleshoot.rst:83 +msgid "Note the expiration dates of the certificate:" +msgstr "" + +#: ../identity_troubleshoot.rst:90 +msgid "" +"The token revocation list is updated once a minute, but the certificates are " +"not. One possible problem is that the certificates are the wrong files or " +"garbage. You can remove these files and run another command against your " +"server; they are fetched on demand." +msgstr "" + +#: ../identity_troubleshoot.rst:95 +msgid "" +"The Identity service log should show the access of the certificate files. " +"You might have to turn up your logging levels. Set ``debug = True`` and " +"``verbose = True`` in your Identity configuration file and restart the " +"Identity server." +msgstr "" + +#: ../identity_troubleshoot.rst:107 +msgid "" +"If the files do not appear in your directory after this, it is likely one of " +"the following issues:" +msgstr "" + +#: ../identity_troubleshoot.rst:110 +msgid "" +"Your service is configured incorrectly and cannot talk to Identity. Check " +"the ``auth_port`` and ``auth_host`` values and make sure that you can talk " +"to that service through cURL, as shown previously." +msgstr "" + +#: ../identity_troubleshoot.rst:114 +msgid "" +"Your signing directory is not writable. Use the ``chmod`` command to change " +"its permissions so that the service (POSIX) user can write to it. Verify the " +"change through ``su`` and ``touch`` commands." +msgstr "" + +#: ../identity_troubleshoot.rst:118 +msgid "The SELinux policy is denying access to the directory." +msgstr "" + +#: ../identity_troubleshoot.rst:120 +msgid "" +"SELinux troubles often occur when you use Fedora or RHEL-based packages and " +"you choose configuration options that do not match the standard policy. Run " +"the ``setenforce permissive`` command. If that makes a difference, you " +"should relabel the directory. If you are using a sub-directory of the ``/var/" +"cache/`` directory, run the following command:" +msgstr "" + +#: ../identity_troubleshoot.rst:130 +msgid "" +"If you are not using a ``/var/cache`` sub-directory, you should. Modify the " +"``signing_dir`` configuration option for your service and restart." +msgstr "" + +#: ../identity_troubleshoot.rst:133 +msgid "" +"Set back to ``setenforce enforcing`` to confirm that your changes solve the " +"problem." +msgstr "" + +#: ../identity_troubleshoot.rst:136 +msgid "" +"If your certificates are fetched on demand, the PKI validation is working " +"properly. Most likely, the token from Identity is not valid for the " +"operation you are attempting to perform, and your user needs a different " +"role for the operation." +msgstr "" + +#: ../identity_troubleshoot.rst:142 +msgid "Debug signing key file errors" +msgstr "" + +#: ../identity_troubleshoot.rst:144 +msgid "" +"If an error occurs when the signing key file opens, it is possible that the " +"person who ran the ``keystone-manage pki_setup`` command to generate " +"certificates and keys did not use the correct user. When you run the " +"``keystone-manage pki_setup`` command, Identity generates a set of " +"certificates and keys in ``/etc/keystone/ssl*``, which is owned by ``root:" +"root``." +msgstr "" + +#: ../identity_troubleshoot.rst:151 +msgid "" +"This can present a problem when you run the Identity daemon under the " +"keystone user account (nologin) when you try to run PKI. Unless you run the " +"``chown`` command against the files ``keystone:keystone``, or run the " +"``keystone-manage pki_setup`` command with the :option:`--keystone-user` " +"and :option:`--keystone-group` parameters, you will get an error. For " +"example:" +msgstr "" + +#: ../identity_troubleshoot.rst:167 +msgid "Flush expired tokens from the token database table" +msgstr "" + +#: ../identity_troubleshoot.rst:169 +msgid "" +"As you generate tokens, the token database table on the Identity server " +"grows. To clear the token table, an administrative user must run the " +"``keystone-manage token_flush`` command to flush the tokens. When you flush " +"tokens, expired tokens are deleted and traceability is eliminated." +msgstr "" + +#: ../identity_troubleshoot.rst:174 +msgid "" +"Use ``cron`` to schedule this command to run frequently based on your " +"workload. For large workloads, running it every minute is recommended." +msgstr "" + +#: ../identity_user_crud.rst:3 +msgid "User CRUD" +msgstr "" + +#: ../identity_user_crud.rst:5 +msgid "" +"Identity provides a user CRUD (Create, Read, Update, and Delete) filter that " +"can be added to the ``public_api`` pipeline. The user CRUD filter enables " +"users to use a HTTP PATCH to change their own password. To enable this " +"extension you should define a :code:`user_crud_extension` filter, insert it " +"after the \"option:`*_body` middleware and before the ``public_service`` " +"application in the ``public_api`` WSGI pipeline in :file:`keystone-paste." +"ini`. For example:" +msgstr "" + +#: ../identity_user_crud.rst:22 +msgid "Each user can then change their own password with a HTTP PATCH::" +msgstr "" + +#: ../identity_user_crud.rst:27 +msgid "" +"In addition to changing their password, all current tokens for the user are " +"invalidated." +msgstr "" + +#: ../identity_user_crud.rst:32 +msgid "Only use a KVS back end for tokens when testing." +msgstr "" + +#: ../index.rst:3 +msgid "OpenStack Cloud Administrator Guide" +msgstr "" + +#: ../index.rst:6 +msgid "Abstract" +msgstr "" + +#: ../index.rst:8 +msgid "" +"OpenStack offers open source software for cloud administrators to manage and " +"troubleshoot an OpenStack cloud." +msgstr "" + +#: ../index.rst:11 +msgid "" +"This guide documents OpenStack Kilo, OpenStack Juno, and OpenStack Icehouse " +"releases." +msgstr "" + +#: ../index.rst:15 +msgid "Contents" +msgstr "" + +#: ../index.rst:37 +msgid "Search in this guide" +msgstr "" + +#: ../index.rst:39 +msgid ":ref:`search`" +msgstr "" + +#: ../keystone_caching_layer.rst:4 +msgid "Caching layer" +msgstr "" + +#: ../keystone_caching_layer.rst:6 +msgid "" +"OpenStack Identity supports a caching layer that is above the configurable " +"subsystems (for example, token, assignment). OpenStack Identity uses the " +"`dogpile.cache `__ library " +"which allows flexible cache back ends. The majority of the caching " +"configuration options are set in the ``[cache]`` section of the :file:" +"`keystone.conf` file. However, each section that has the capability to be " +"cached usually has a caching boolean value that toggles caching." +msgstr "" + +#: ../keystone_caching_layer.rst:15 +msgid "" +"So to enable only the token back end caching, set the values as follows:" +msgstr "" + +#: ../keystone_caching_layer.rst:31 +msgid "" +"Since the Juno release, the default setting is enabled for subsystem " +"caching, but the global toggle is disabled. As a result, no caching in " +"available unless the global toggle for ``[cache]`` is enabled by setting the " +"value to ``true``." +msgstr "" + +#: ../keystone_caching_layer.rst:37 +msgid "Caching for tokens and tokens validation" +msgstr "" + +#: ../keystone_caching_layer.rst:39 +msgid "" +"The token system has a separate ``cache_time`` configuration option, that " +"can be set to a value above or below the global ``expiration_time`` default, " +"allowing for different caching behavior from the other systems in OpenStack " +"Identity. This option is set in the ``[token]`` section of the configuration " +"file." +msgstr "" + +#: ../keystone_caching_layer.rst:45 +msgid "" +"The token revocation list cache time is handled by the configuration option " +"``revocation_cache_time`` in the ``[token]`` section. The revocation list is " +"refreshed whenever a token is revoked. It typically sees significantly more " +"requests than specific token retrievals or token validation calls." +msgstr "" + +#: ../keystone_caching_layer.rst:51 +msgid "" +"Here is a list of actions that are affected by the cached time: getting a " +"new token, revoking tokens, validating tokens, checking v2 tokens, and " +"checking v3 tokens." +msgstr "" + +#: ../keystone_caching_layer.rst:55 +msgid "" +"The delete token API calls invalidate the cache for the tokens being acted " +"upon, as well as invalidating the cache for the revoked token list and the " +"validate/check token calls." +msgstr "" + +#: ../keystone_caching_layer.rst:59 +msgid "" +"Token caching is configurable independently of the ``revocation_list`` " +"caching. Lifted expiration checks from the token drivers to the token " +"manager. This ensures that cached tokens will still raise a " +"``TokenNotFound`` flag when expired." +msgstr "" + +#: ../keystone_caching_layer.rst:64 +msgid "" +"For cache consistency, all token IDs are transformed into the short token " +"hash at the provider and token driver level. Some methods have access to the " +"full ID (PKI Tokens), and some methods do not. Cache invalidation is " +"inconsistent without token ID normalization." +msgstr "" + +#: ../keystone_caching_layer.rst:70 +msgid "Caching around assignment CRUD" +msgstr "" + +#: ../keystone_caching_layer.rst:72 +msgid "" +"The assignment system has a separate ``cache_time`` configuration option, " +"that can be set to a value above or below the global ``expiration_time`` " +"default, allowing for different caching behavior from the other systems in " +"Identity service. This option is set in the ``[assignment]`` section of the " +"configuration file." +msgstr "" + +#: ../keystone_caching_layer.rst:78 +msgid "" +"Currently ``assignment`` has caching for ``project``, ``domain``, and " +"``role`` specific requests (primarily around the CRUD actions). Caching is " +"currently not implemented on grants. The ``list`` methods are not subject to " +"caching." +msgstr "" + +#: ../keystone_caching_layer.rst:83 +msgid "" +"Here is a list of actions that are affected by the assignment: assign domain " +"API, assign project API, and assign role API." +msgstr "" + +#: ../keystone_caching_layer.rst:86 +msgid "" +"The create, update, and delete actions for domains, projects and roles will " +"perform proper invalidations of the cached methods listed above." +msgstr "" + +#: ../keystone_caching_layer.rst:91 +msgid "" +"If a read-only ``assignment`` back end is in use, the cache will not " +"immediately reflect changes on the back end. Any given change may take up to " +"the ``cache_time`` (if set in the ``[assignment]`` section of the " +"configuration file) or the global ``expiration_time`` (set in the " +"``[cache]`` section of the configuration file) before it is reflected. If " +"this type of delay (when using a read-only ``assignment`` back end) is an " +"issue, it is recommended that caching be disabled on ``assignment``. To " +"disable caching specifically on ``assignment``, in the ``[assignment]`` " +"section of the configuration set ``caching`` to ``False``." +msgstr "" + +#: ../keystone_caching_layer.rst:102 +msgid "" +"For more information about the different back ends (and configuration " +"options), see:" +msgstr "" + +#: ../keystone_caching_layer.rst:105 +msgid "" +"`dogpile.cache.backends.memory `__" +msgstr "" + +#: ../keystone_caching_layer.rst:107 +msgid "" +"`dogpile.cache.backends.memcached `__" +msgstr "" + +#: ../keystone_caching_layer.rst:111 +msgid "" +"The memory back end is not suitable for use in a production environment." +msgstr "" + +#: ../keystone_caching_layer.rst:114 +msgid "" +"`dogpile.cache.backends.redis `__" +msgstr "" + +#: ../keystone_caching_layer.rst:116 +msgid "" +"`dogpile.cache.backends.file `__" +msgstr "" + +#: ../keystone_caching_layer.rst:118 +msgid "``keystone.common.cache.backends.mongo``" +msgstr "" + +#: ../keystone_caching_layer.rst:121 +msgid "Configure the Memcached back end example" +msgstr "" + +#: ../keystone_caching_layer.rst:123 +msgid "The following example shows how to configure the memcached back end:" +msgstr "" + +#: ../keystone_caching_layer.rst:134 +msgid "" +"You need to specify the URL to reach the ``memcached`` instance with the " +"``backend_argument`` parameter." +msgstr "" + +#: ../keystone_certificates_for_pki.rst:3 +msgid "Certificates for PKI" +msgstr "" + +#: ../keystone_certificates_for_pki.rst:5 +msgid "" +"PKI stands for Public Key Infrastructure. Tokens are documents, " +"cryptographically signed using the X509 standard. In order to work correctly " +"token generation requires a public/private key pair. The public key must be " +"signed in an X509 certificate, and the certificate used to sign it must be " +"available as a Certificate Authority (CA) certificate. These files can be " +"generated either using the ``keystone-manage`` utility, or externally " +"generated. The files need to be in the locations specified by the top level " +"Identity service configuration file :file:`keystone.conf` as specified in " +"the above section. Additionally, the private key should only be readable by " +"the system user that will run the Identity service." +msgstr "" + +#: ../keystone_certificates_for_pki.rst:20 +msgid "" +"The certificates can be world readable, but the private key cannot be. The " +"private key should only be readable by the account that is going to sign " +"tokens. When generating files with the :command:`keystone-manage pki_setup` " +"command, your best option is to run as the pki user. If you run :command:" +"`keystone-manage` as root, you can append :option:`--keystone-user` and :" +"option:`--keystone-group` parameters to set the user name and group keystone " +"is going to run under." +msgstr "" + +#: ../keystone_certificates_for_pki.rst:28 +msgid "" +"The values that specify where to read the certificates are under the " +"``[signing]`` section of the configuration file. The configuration values " +"are:" +msgstr "" + +#: ../keystone_certificates_for_pki.rst:33 +msgid "" +"Location of certificate used to verify tokens. Default is :file:`/etc/" +"keystone/ssl/certs/signing_cert.pem`." +msgstr "" + +# #-#-#-#-# keystone_certificates_for_pki.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +# #-#-#-#-# keystone_configure_with_SSL.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +#: ../keystone_certificates_for_pki.rst:34 +#: ../keystone_configure_with_SSL.rst:59 +msgid "``certfile``" +msgstr "" + +#: ../keystone_certificates_for_pki.rst:37 +msgid "" +"Location of private key used to sign tokens. Default is :file:`/etc/keystone/" +"ssl/private/signing_key.pem`." +msgstr "" + +# #-#-#-#-# keystone_certificates_for_pki.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +# #-#-#-#-# keystone_configure_with_SSL.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +#: ../keystone_certificates_for_pki.rst:38 +#: ../keystone_configure_with_SSL.rst:64 +msgid "``keyfile``" +msgstr "" + +#: ../keystone_certificates_for_pki.rst:41 +msgid "" +"Location of certificate for the authority that issued the above certificate. " +"Default is :file:`/etc/keystone/ssl/certs/ca.pem`." +msgstr "" + +# #-#-#-#-# keystone_certificates_for_pki.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +# #-#-#-#-# keystone_configure_with_SSL.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +#: ../keystone_certificates_for_pki.rst:43 +#: ../keystone_configure_with_SSL.rst:67 +msgid "``ca_certs``" +msgstr "" + +#: ../keystone_certificates_for_pki.rst:46 +msgid "" +"Location of the private key used by the CA. Default is :file:`/etc/keystone/" +"ssl/private/cakey.pem`." +msgstr "" + +#: ../keystone_certificates_for_pki.rst:47 +msgid "``ca_key``" +msgstr "" + +#: ../keystone_certificates_for_pki.rst:50 +msgid "Default is ``2048``." +msgstr "" + +#: ../keystone_certificates_for_pki.rst:50 +msgid "``key_size``" +msgstr "" + +#: ../keystone_certificates_for_pki.rst:53 +msgid "Default is ``3650``." +msgstr "" + +#: ../keystone_certificates_for_pki.rst:53 +msgid "``valid_days``" +msgstr "" + +#: ../keystone_certificates_for_pki.rst:56 +msgid "" +"Certificate subject (auto generated certificate) for token signing. Default " +"is ``/C=US/ST=Unset/L=Unset/O=Unset/CN=www.example.com``." +msgstr "" + +#: ../keystone_certificates_for_pki.rst:57 +msgid "``cert_subject``" +msgstr "" + +#: ../keystone_certificates_for_pki.rst:59 +msgid "" +"When generating certificates with the :command:`keystone-manage pki_setup` " +"command, the ``ca_key``, ``key_size``, and ``valid_days`` configuration " +"options are used." +msgstr "" + +#: ../keystone_certificates_for_pki.rst:63 +msgid "" +"If the :command:`keystone-manage pki_setup` command is not used to generate " +"certificates, or you are providing your own certificates, these values do " +"not need to be set." +msgstr "" + +#: ../keystone_certificates_for_pki.rst:67 +msgid "" +"If ``provider=keystone.token.providers.uuid.Provider`` in the ``[token]`` " +"section of the keystone configuration, a typical token looks like " +"``53f7f6ef0cc344b5be706bcc8b1479e1``. If ``provider=keystone.token.providers." +"pki.Provider``, a typical token is a much longer string, such as::" +msgstr "" + +#: ../keystone_certificates_for_pki.rst:102 +msgid "Sign certificate issued by external CA" +msgstr "" + +#: ../keystone_certificates_for_pki.rst:104 +msgid "" +"You can use a signing certificate issued by an external CA instead of " +"generated by ``keystone-manage``. However, a certificate issued by an " +"external CA must satisfy the following conditions:" +msgstr "" + +#: ../keystone_certificates_for_pki.rst:108 +msgid "" +"All certificate and key files must be in Privacy Enhanced Mail (PEM) format" +msgstr "" + +#: ../keystone_certificates_for_pki.rst:111 +msgid "Private key files must not be protected by a password" +msgstr "" + +#: ../keystone_certificates_for_pki.rst:113 +msgid "" +"When using a signing certificate issued by an external CA, you do not need " +"to specify ``key_size``, ``valid_days``, and ``ca_password`` as they will be " +"ignored." +msgstr "" + +#: ../keystone_certificates_for_pki.rst:117 +msgid "" +"The basic workflow for using a signing certificate issued by an external CA " +"involves:" +msgstr "" + +#: ../keystone_certificates_for_pki.rst:120 +msgid "Request Signing Certificate from External CA" +msgstr "" + +#: ../keystone_certificates_for_pki.rst:122 +msgid "Convert certificate and private key to PEM if needed" +msgstr "" + +#: ../keystone_certificates_for_pki.rst:124 +msgid "Install External Signing Certificate" +msgstr "" + +#: ../keystone_certificates_for_pki.rst:127 +msgid "Request a signing certificate from an external CA" +msgstr "" + +#: ../keystone_certificates_for_pki.rst:129 +msgid "" +"One way to request a signing certificate from an external CA is to first " +"generate a PKCS #10 Certificate Request Syntax (CRS) using OpenSSL CLI." +msgstr "" + +#: ../keystone_certificates_for_pki.rst:132 +msgid "" +"Create a certificate request configuration file. For example, create the :" +"file:`cert_req.conf` file, as follows:" +msgstr "" + +#: ../keystone_certificates_for_pki.rst:155 +msgid "" +"Then generate a CRS with OpenSSL CLI. **Do not encrypt the generated private " +"key. You must use the -nodes option.**" +msgstr "" + +# #-#-#-#-# keystone_certificates_for_pki.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +# #-#-#-#-# objectstorage_ringbuilder.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +#: ../keystone_certificates_for_pki.rst:158 +#: ../objectstorage_ringbuilder.rst:119 +msgid "For example::" +msgstr "" + +#: ../keystone_certificates_for_pki.rst:163 +msgid "" +"If everything is successful, you should end up with :file:`signing_cert_req." +"pem` and :file:`signing_key.pem`. Send :file:`signing_cert_req.pem` to your " +"CA to request a token signing certificate and make sure to ask the " +"certificate to be in PEM format. Also, make sure your trusted CA certificate " +"chain is also in PEM format." +msgstr "" + +#: ../keystone_certificates_for_pki.rst:170 +msgid "Install an external signing certificate" +msgstr "" + +#: ../keystone_certificates_for_pki.rst:172 +msgid "Assuming you have the following already:" +msgstr "" + +#: ../keystone_certificates_for_pki.rst:175 +msgid "(Keystone token) signing certificate in PEM format" +msgstr "" + +#: ../keystone_certificates_for_pki.rst:175 +msgid ":file:`signing_cert.pem`" +msgstr "" + +#: ../keystone_certificates_for_pki.rst:178 +msgid ":file:`signing_key.pem`" +msgstr "" + +#: ../keystone_certificates_for_pki.rst:178 +msgid "Corresponding (non-encrypted) private key in PEM format" +msgstr "" + +#: ../keystone_certificates_for_pki.rst:181 +msgid ":file:`cacert.pem`" +msgstr "" + +#: ../keystone_certificates_for_pki.rst:181 +msgid "Trust CA certificate chain in PEM format" +msgstr "" + +#: ../keystone_certificates_for_pki.rst:183 +msgid "Copy the above to your certificate directory. For example:" +msgstr "" + +#: ../keystone_certificates_for_pki.rst:195 +msgid "Make sure the certificate directory is only accessible by root." +msgstr "" + +#: ../keystone_certificates_for_pki.rst:199 +msgid "" +"The procedure of copying the key and cert files may be improved if done " +"after first running :command:`keystone-manage pki_setup` since this command " +"also creates other needed files, such as the :file:`index.txt` and :file:" +"`serial` files." +msgstr "" + +#: ../keystone_certificates_for_pki.rst:204 +msgid "" +"Also, when copying the necessary files to a different server for replicating " +"the functionality, the entire directory of files is needed, not just the key " +"and cert files." +msgstr "" + +#: ../keystone_certificates_for_pki.rst:208 +msgid "" +"If your certificate directory path is different from the default :file:`/etc/" +"keystone/ssl/certs`, make sure it is reflected in the ``[signing]`` section " +"of the configuration file." +msgstr "" + +#: ../keystone_certificates_for_pki.rst:213 +msgid "Switching out expired signing certificates" +msgstr "" + +#: ../keystone_certificates_for_pki.rst:215 +msgid "" +"The following procedure details how to switch out expired signing " +"certificates with no cloud outages." +msgstr "" + +#: ../keystone_certificates_for_pki.rst:218 +msgid "Generate a new signing key." +msgstr "" + +#: ../keystone_certificates_for_pki.rst:220 +msgid "Generate a new certificate request." +msgstr "" + +#: ../keystone_certificates_for_pki.rst:222 +msgid "" +"Sign the new certificate with the existing CA to generate a new " +"``signing_cert``." +msgstr "" + +#: ../keystone_certificates_for_pki.rst:225 +msgid "" +"Append the new ``signing_cert`` to the old ``signing_cert``. Ensure the old " +"certificate is in the file first." +msgstr "" + +#: ../keystone_certificates_for_pki.rst:228 +msgid "" +"Remove all signing certificates from all your hosts to force OpenStack " +"Compute to download the new ``signing_cert``." +msgstr "" + +#: ../keystone_certificates_for_pki.rst:231 +msgid "" +"Replace the old signing key with the new signing key. Move the new signing " +"certificate above the old certificate in the ``signing_cert`` file." +msgstr "" + +#: ../keystone_certificates_for_pki.rst:235 +msgid "" +"After the old certificate reads as expired, you can safely remove the old " +"signing certificate from the file." +msgstr "" + +#: ../keystone_configure_with_SSL.rst:3 +msgid "Configure the Identity service with SSL" +msgstr "" + +#: ../keystone_configure_with_SSL.rst:5 +msgid "You can configure the Identity service to support two-way SSL." +msgstr "" + +#: ../keystone_configure_with_SSL.rst:7 +msgid "You must obtain the x509 certificates externally and configure them." +msgstr "" + +#: ../keystone_configure_with_SSL.rst:9 +msgid "" +"The Identity service provides a set of sample certificates in the :file:" +"`examples/pki/certs` and :file:`examples/pki/private` directories:" +msgstr "" + +#: ../keystone_configure_with_SSL.rst:13 +msgid "Certificate Authority chain to validate against." +msgstr "" + +#: ../keystone_configure_with_SSL.rst:13 +msgid "cacert.pem" +msgstr "" + +#: ../keystone_configure_with_SSL.rst:16 +msgid "Public certificate for Identity service server." +msgstr "" + +#: ../keystone_configure_with_SSL.rst:16 +msgid "ssl\\_cert.pem" +msgstr "" + +#: ../keystone_configure_with_SSL.rst:19 +msgid "Public and private certificate for Identity service middleware/client." +msgstr "" + +#: ../keystone_configure_with_SSL.rst:20 +msgid "middleware.pem" +msgstr "" + +#: ../keystone_configure_with_SSL.rst:23 +msgid "Private key for the CA." +msgstr "" + +#: ../keystone_configure_with_SSL.rst:23 +msgid "cakey.pem" +msgstr "" + +#: ../keystone_configure_with_SSL.rst:26 +msgid "Private key for the Identity service server." +msgstr "" + +#: ../keystone_configure_with_SSL.rst:26 +msgid "ssl\\_key.pem" +msgstr "" + +#: ../keystone_configure_with_SSL.rst:30 +msgid "" +"You can choose names for these certificates. You can also combine public/" +"private keys in the same file, if you wish. These certificates are provided " +"as an example." +msgstr "" + +#: ../keystone_configure_with_SSL.rst:35 +msgid "Client authentication with keystone-all" +msgstr "" + +#: ../keystone_configure_with_SSL.rst:37 +msgid "" +"When running ``keystone-all``, the server can be configured to enable SSL " +"with client authentication using the following instructions. Modify the " +"``[eventlet_server_ssl]`` section in the :file:`/etc/keystone/keystone.conf` " +"file. The following SSL configuration example uses the included sample " +"certificates:" +msgstr "" + +#: ../keystone_configure_with_SSL.rst:53 +msgid "**Options**" +msgstr "" + +#: ../keystone_configure_with_SSL.rst:56 +msgid "True enables SSL. Default is False." +msgstr "" + +#: ../keystone_configure_with_SSL.rst:56 +msgid "``enable``" +msgstr "" + +#: ../keystone_configure_with_SSL.rst:59 +msgid "Path to the Identity service public certificate file." +msgstr "" + +#: ../keystone_configure_with_SSL.rst:62 +msgid "" +"Path to the Identity service private certificate file. If you include the " +"private key in the certfile, you can omit the keyfile." +msgstr "" + +#: ../keystone_configure_with_SSL.rst:67 +msgid "Path to the CA trust chain." +msgstr "" + +#: ../keystone_configure_with_SSL.rst:70 +msgid "Requires client certificate. Default is False." +msgstr "" + +#: ../keystone_configure_with_SSL.rst:70 +msgid "``cert_required``" +msgstr "" + +#: ../keystone_configure_with_SSL.rst:72 +msgid "" +"When running the Identity service as a WSGI service in a web server such as " +"Apache httpd, this configuration is done in the web server instead. In this " +"case the options in the ``[eventlet_server_ssl]`` section are ignored." +msgstr "" + +#: ../keystone_external_authentication.rst:3 +msgid "External authentication with Identity" +msgstr "" + +#: ../keystone_external_authentication.rst:5 +msgid "" +"When Identity runs in ``apache-httpd``, you can use external authentication " +"methods that differ from the authentication provided by the identity store " +"back end. For example, you can use an SQL identity back end together with " +"X.509 authentication and Kerberos, instead of using the user name and " +"password combination." +msgstr "" + +#: ../keystone_external_authentication.rst:12 +msgid "Use HTTPD authentication" +msgstr "" + +#: ../keystone_external_authentication.rst:14 +msgid "" +"Web servers, like Apache HTTP, support many methods of authentication. " +"Identity can allow the web server to perform the authentication. The web " +"server then passes the authenticated user to Identity by using the " +"``REMOTE_USER`` environment variable. This user must already exist in the " +"Identity back end to get a token from the controller. To use this method, " +"Identity should run on ``apache-httpd``." +msgstr "" + +#: ../keystone_external_authentication.rst:22 +msgid "Use X.509" +msgstr "" + +#: ../keystone_external_authentication.rst:24 +msgid "" +"The following Apache configuration snippet authenticates the user based on a " +"valid X.509 certificate from a known CA::" +msgstr "" + +#: ../keystone_integrate_assignment_backend_ldap.rst:5 +msgid "Integrate assignment back end with LDAP" +msgstr "" + +#: ../keystone_integrate_assignment_backend_ldap.rst:7 +msgid "" +"When you configure the OpenStack Identity service to use LDAP servers, you " +"can split authentication and authorization using the *assignment* feature. " +"Integrating the *assignment* back end with LDAP allows administrators to use " +"projects (tenant), roles, domains, and role assignments in LDAP." +msgstr "" + +#: ../keystone_integrate_assignment_backend_ldap.rst:15 +msgid "" +"Be aware of domain-specific back end limitations when configuring OpenStack " +"Identity. The OpenStack Identity service does not support domain-specific " +"assignment back ends. Using LDAP as an assignment back end is not " +"recommended." +msgstr "" + +#: ../keystone_integrate_assignment_backend_ldap.rst:23 +msgid "" +"For OpenStack Identity assignments to access LDAP servers, you must define " +"the destination LDAP server in the :file:`keystone.conf` file. For more " +"information, see :ref:`integrate-identity-with-ldap`." +msgstr "" + +#: ../keystone_integrate_assignment_backend_ldap.rst:27 +msgid "**To integrate assignment back ends with LDAP**" +msgstr "" + +#: ../keystone_integrate_assignment_backend_ldap.rst:29 +msgid "" +"Enable the assignment driver. In the ``[assignment]`` section, set the " +"``driver`` configuration key to ``keystone.assignment.backends.sql." +"Assignment``:" +msgstr "" + +#: ../keystone_integrate_assignment_backend_ldap.rst:40 +msgid "" +"Create the organizational units (OU) in the LDAP directory, and define their " +"corresponding location in the ``keystone.conf`` file:" +msgstr "" + +#: ../keystone_integrate_assignment_backend_ldap.rst:55 +msgid "" +"These schema attributes are extensible for compatibility with various " +"schemas. For example, this entry maps to the groupOfNames attribute in " +"Active Directory:" +msgstr "" + +#: ../keystone_integrate_assignment_backend_ldap.rst:63 +msgid "" +"A read-only implementation is recommended for LDAP integration. These " +"permissions are applied to object types in the ``keystone.conf`` file:" +msgstr "" + +# #-#-#-#-# keystone_integrate_assignment_backend_ldap.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +# #-#-#-#-# keystone_integrate_identity_backend_ldap.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +#: ../keystone_integrate_assignment_backend_ldap.rst:78 +#: ../keystone_integrate_identity_backend_ldap.rst:67 +#: ../keystone_integrate_identity_backend_ldap.rst:171 +msgid "Restart the OpenStack Identity service::" +msgstr "" + +# #-#-#-#-# keystone_integrate_assignment_backend_ldap.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +# #-#-#-#-# keystone_integrate_identity_backend_ldap.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +# #-#-#-#-# keystone_integrate_with_ldap.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +#: ../keystone_integrate_assignment_backend_ldap.rst:85 +#: ../keystone_integrate_identity_backend_ldap.rst:73 +#: ../keystone_integrate_identity_backend_ldap.rst:177 +#: ../keystone_integrate_identity_backend_ldap.rst:252 +#: ../keystone_integrate_with_ldap.rst:166 +msgid "" +"During service restart, authentication and authorization are unavailable." +msgstr "" + +#: ../keystone_integrate_assignment_backend_ldap.rst:88 +msgid "**Additional LDAP integration settings.**" +msgstr "" + +#: ../keystone_integrate_assignment_backend_ldap.rst:90 +msgid "" +"Set these options in the :file:`/etc/keystone/keystone.conf` file for a " +"single LDAP server, or :file:`/etc/keystone/domains/keystone.DOMAIN_NAME." +"conf` files for multiple back ends." +msgstr "" + +# #-#-#-#-# keystone_integrate_assignment_backend_ldap.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +# #-#-#-#-# keystone_integrate_identity_backend_ldap.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +#: ../keystone_integrate_assignment_backend_ldap.rst:95 +#: ../keystone_integrate_identity_backend_ldap.rst:188 +msgid "Use filters to control the scope of data presented through LDAP." +msgstr "" + +#: ../keystone_integrate_assignment_backend_ldap.rst:107 +msgid "Filtering method" +msgstr "" + +# #-#-#-#-# keystone_integrate_assignment_backend_ldap.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +# #-#-#-#-# keystone_integrate_identity_backend_ldap.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +#: ../keystone_integrate_assignment_backend_ldap.rst:107 +#: ../keystone_integrate_identity_backend_ldap.rst:195 +msgid "Filters" +msgstr "" + +#: ../keystone_integrate_assignment_backend_ldap.rst:110 +msgid "" +"Mask account status values (include any additional attribute mappings) for " +"compatibility with various directory services. Superfluous accounts are " +"filtered with user\\_filter." +msgstr "" + +# #-#-#-#-# keystone_integrate_assignment_backend_ldap.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +# #-#-#-#-# keystone_integrate_identity_backend_ldap.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +#: ../keystone_integrate_assignment_backend_ldap.rst:114 +#: ../keystone_integrate_identity_backend_ldap.rst:202 +msgid "Setting attribute ignore to list of attributes stripped off on update." +msgstr "" + +#: ../keystone_integrate_assignment_backend_ldap.rst:134 +msgid "Assignment attribute mapping" +msgstr "" + +#: ../keystone_integrate_assignment_backend_ldap.rst:137 +msgid "" +"An alternative method to determine if a project is enabled or not is to " +"check if that project is a member of the emulation group." +msgstr "" + +#: ../keystone_integrate_assignment_backend_ldap.rst:140 +msgid "" +"Use DN of the group entry to hold enabled projects when using enabled " +"emulation." +msgstr "" + +# #-#-#-#-# keystone_integrate_assignment_backend_ldap.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +# #-#-#-#-# keystone_integrate_identity_backend_ldap.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +#: ../keystone_integrate_assignment_backend_ldap.rst:147 +#: ../keystone_integrate_identity_backend_ldap.rst:243 +msgid "Enabled emulation" +msgstr "" + +#: ../keystone_integrate_identity_backend_ldap.rst:5 +msgid "Integrate Identity back end with LDAP" +msgstr "" + +#: ../keystone_integrate_identity_backend_ldap.rst:7 +msgid "" +"The Identity back end contains information for users, groups, and group " +"member lists. Integrating the Identity back end with LDAP allows " +"administrators to use users and groups in LDAP." +msgstr "" + +#: ../keystone_integrate_identity_backend_ldap.rst:13 +msgid "" +"For OpenStack Identity service to access LDAP servers, you must define the " +"destination LDAP server in the ``keystone.conf`` file. For more information, " +"see :ref:`integrate-identity-with-ldap`." +msgstr "" + +#: ../keystone_integrate_identity_backend_ldap.rst:17 +msgid "**To integrate one Identity back end with LDAP**" +msgstr "" + +#: ../keystone_integrate_identity_backend_ldap.rst:19 +msgid "" +"Enable the LDAP Identity driver in the ``keystone.conf`` file. This allows " +"LDAP as an identity back end:" +msgstr "" + +#: ../keystone_integrate_identity_backend_ldap.rst:29 +msgid "" +"Create the organizational units (OU) in the LDAP directory, and define the " +"corresponding location in the :file:`keystone.conf` file:" +msgstr "" + +#: ../keystone_integrate_identity_backend_ldap.rst:44 +#: ../keystone_integrate_identity_backend_ldap.rst:148 +msgid "" +"These schema attributes are extensible for compatibility with various " +"schemas. For example, this entry maps to the person attribute in Active " +"Directory:" +msgstr "" + +#: ../keystone_integrate_identity_backend_ldap.rst:52 +msgid "" +"A read-only implementation is recommended for LDAP integration. These " +"permissions are applied to object types in the :file:`keystone.conf`:" +msgstr "" + +#: ../keystone_integrate_identity_backend_ldap.rst:76 +msgid "**To integrate multiple Identity back ends with LDAP**" +msgstr "" + +#: ../keystone_integrate_identity_backend_ldap.rst:78 +msgid "" +"Set the following options in the :file:`/etc/keystone/keystone.conf` file:" +msgstr "" + +#: ../keystone_integrate_identity_backend_ldap.rst:80 +msgid "Enable the LDAP driver:" +msgstr "" + +#: ../keystone_integrate_identity_backend_ldap.rst:88 +msgid "Enable domain-specific drivers:" +msgstr "" + +#: ../keystone_integrate_identity_backend_ldap.rst:96 +msgid "Restart the service::" +msgstr "" + +#: ../keystone_integrate_identity_backend_ldap.rst:100 +msgid "" +"List the domains using the dashboard, or the OpenStackClient CLI. Refer to " +"the `Command List `__ for a list of OpenStackClient commands." +msgstr "" + +#: ../keystone_integrate_identity_backend_ldap.rst:105 +msgid "Create domains using OpenStack dashboard, or the OpenStackClient CLI." +msgstr "" + +#: ../keystone_integrate_identity_backend_ldap.rst:107 +msgid "" +"For each domain, create a domain-specific configuration file in the :file:`/" +"etc/keystone/domains` directory. Use the file naming convention :file:" +"`keystone.DOMAIN_NAME.conf`, where DOMAIN\\_NAME is the domain name assigned " +"in the previous step." +msgstr "" + +#: ../keystone_integrate_identity_backend_ldap.rst:114 +msgid "" +"The options set in the :file:`/etc/keystone/domains/keystone.DOMAIN_NAME." +"conf` file will override options in the :file:`/etc/keystone/keystone.conf` " +"file." +msgstr "" + +#: ../keystone_integrate_identity_backend_ldap.rst:118 +msgid "" +"Define the destination LDAP server in the :file:`/etc/keystone/domains/" +"keystone.DOMAIN_NAME.conf` file. For example:" +msgstr "" + +#: ../keystone_integrate_identity_backend_ldap.rst:132 +msgid "" +"Create the organizational units (OU) in the LDAP directories, and define " +"their corresponding locations in the :file:`/etc/keystone/domains/keystone." +"DOMAIN_NAME.conf` file. For example:" +msgstr "" + +#: ../keystone_integrate_identity_backend_ldap.rst:156 +msgid "" +"A read-only implementation is recommended for LDAP integration. These " +"permissions are applied to object types in the :file:`/etc/keystone/domains/" +"keystone.DOMAIN_NAME.conf` file:" +msgstr "" + +# #-#-#-#-# keystone_integrate_identity_backend_ldap.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +# #-#-#-#-# keystone_integrate_with_ldap.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +#: ../keystone_integrate_identity_backend_ldap.rst:180 +#: ../keystone_integrate_with_ldap.rst:81 +msgid "**Additional LDAP integration settings**" +msgstr "" + +# #-#-#-#-# keystone_integrate_identity_backend_ldap.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +# #-#-#-#-# keystone_integrate_with_ldap.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +#: ../keystone_integrate_identity_backend_ldap.rst:182 +#: ../keystone_integrate_with_ldap.rst:83 +msgid "" +"Set these options in the :file:`/etc/keystone/keystone.conf` file for a " +"single LDAP server, or :file:`/etc/keystone/domains/keystone.DOMAIN_NAME." +"conf` files for multiple back ends. Example configurations appear below each " +"setting summary:" +msgstr "" + +#: ../keystone_integrate_identity_backend_ldap.rst:198 +msgid "" +"Mask account status values (include any additional attribute mappings) for " +"compatibility with various directory services. Superfluous accounts are " +"filtered with ``user_filter``." +msgstr "" + +#: ../keystone_integrate_identity_backend_ldap.rst:205 +msgid "" +"For example, you can mask Active Directory account status attributes in the :" +"file:`keystone.conf` file:" +msgstr "" + +#: ../keystone_integrate_identity_backend_ldap.rst:229 +msgid "Identity attribute mapping" +msgstr "" + +#: ../keystone_integrate_identity_backend_ldap.rst:232 +msgid "" +"An alternative method to determine if a user is enabled or not is by " +"checking if that user is a member of the emulation group." +msgstr "" + +#: ../keystone_integrate_identity_backend_ldap.rst:235 +msgid "" +"Use DN of the group entry to hold enabled user when using enabled emulation." +msgstr "" + +# #-#-#-#-# keystone_integrate_identity_backend_ldap.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +# #-#-#-#-# keystone_integrate_with_ldap.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +#: ../keystone_integrate_identity_backend_ldap.rst:245 +#: ../keystone_integrate_with_ldap.rst:159 +msgid "" +"When you have finished configuration, restart the OpenStack Identity " +"service::" +msgstr "" + +#: ../keystone_integrate_with_ldap.rst:5 +msgid "Integrate Identity with LDAP" +msgstr "" + +#: ../keystone_integrate_with_ldap.rst:14 +msgid "" +"The OpenStack Identity service supports integration with existing LDAP " +"directories for authentication and authorization services." +msgstr "" + +#: ../keystone_integrate_with_ldap.rst:17 +msgid "" +"When the OpenStack Identity service is configured to use LDAP back ends, you " +"can split authentication (using the *identity* feature) and authorization " +"(using the *assignment* feature)." +msgstr "" + +#: ../keystone_integrate_with_ldap.rst:21 +msgid "" +"The *identity* feature enables administrators to manage users and groups by " +"each domain or the OpenStack Identity service entirely." +msgstr "" + +#: ../keystone_integrate_with_ldap.rst:24 +msgid "" +"The *assignment* feature enables administrators to manage project role " +"authorization using the OpenStack Identity service SQL database, while " +"providing user authentication through the LDAP directory." +msgstr "" + +#: ../keystone_integrate_with_ldap.rst:30 +msgid "" +"For the OpenStack Identity service to access LDAP servers, you must enable " +"the ``authlogin_nsswitch_use_ldap`` boolean value for SELinux on the " +"Openstack Identity server. To enable and make the option persistent across " +"reboots, set the following boolean value as the root user:" +msgstr "" + +#: ../keystone_integrate_with_ldap.rst:40 +msgid "" +"Identity configuration is split into two separate back ends; identity (back " +"end for users and groups), and assignments (back end for domains, projects, " +"roles, role assignments). To configure Identity, set options in the :file:`/" +"etc/keystone/keystone.conf` file. See :ref:`integrate-identity-backend-ldap` " +"for Identity back end configuration examples and :ref:`integrate-assignment-" +"backend-ldap` for assignment back end configuration examples. Modify these " +"examples as needed." +msgstr "" + +#: ../keystone_integrate_with_ldap.rst:50 +msgid "" +"Multiple back ends are supported. You can integrate the OpenStack Identity " +"service with a single LDAP server (configure both identity and assignments " +"to LDAP, or set identity and assignments back end with SQL or LDAP), or " +"multiple back ends using domain-specific configuration files." +msgstr "" + +#: ../keystone_integrate_with_ldap.rst:57 +msgid "**To define the destination LDAP server**" +msgstr "" + +#: ../keystone_integrate_with_ldap.rst:59 +msgid "Define the destination LDAP server in the :file:`keystone.conf` file:" +msgstr "" + +#: ../keystone_integrate_with_ldap.rst:72 +msgid "" +"Configure ``dumb_member`` to true if your environment requires the " +"``use_dumb_member`` variable." +msgstr "" + +#: ../keystone_integrate_with_ldap.rst:88 +msgid "**Query option**" +msgstr "" + +#: ../keystone_integrate_with_ldap.rst:93 +msgid "" +"Use ``query_scope`` to control the scope level of data presented (search " +"only the first level or search an entire sub-tree) through LDAP." +msgstr "" + +#: ../keystone_integrate_with_ldap.rst:96 +msgid "" +"Use ``page_size`` to control the maximum results per page. A value of zero " +"disables paging." +msgstr "" + +#: ../keystone_integrate_with_ldap.rst:98 +msgid "" +"Use ``alias_dereferencing`` to control the LDAP dereferencing option for " +"queries." +msgstr "" + +#: ../keystone_integrate_with_ldap.rst:100 +msgid "" +"Use ``chase_referrals`` to override the system's default referral chasing " +"behavior for queries." +msgstr "" + +#: ../keystone_integrate_with_ldap.rst:112 +msgid "**Debug**" +msgstr "" + +#: ../keystone_integrate_with_ldap.rst:114 +msgid "" +"Use ``debug_level`` to set the LDAP debugging level for LDAP calls. A value " +"of zero means that debugging is not enabled." +msgstr "" + +#: ../keystone_integrate_with_ldap.rst:125 +msgid "" +"This value is a bitmask, consult your LDAP documentation for possible values." +msgstr "" + +#: ../keystone_integrate_with_ldap.rst:128 +msgid "**Connection pooling**" +msgstr "" + +#: ../keystone_integrate_with_ldap.rst:130 +msgid "" +"Use ``use_pool`` to enable LDAP connection pooling. Configure connection " +"pool size, maximum retry, reconnect trials, timeout (-1 indicates indefinite " +"wait) and lifetime in seconds." +msgstr "" + +#: ../keystone_integrate_with_ldap.rst:145 +msgid "**Connection pooling for end user authentication**" +msgstr "" + +#: ../keystone_integrate_with_ldap.rst:147 +msgid "" +"Use ``use_auth_pool`` to enable LDAP connection pooling for end user " +"authentication. Configure connection pool size and lifetime in seconds." +msgstr "" + +#: ../keystone_secure_identity_to_ldap_backend.rst:2 +msgid "Secure the OpenStack Identity service connection to an LDAP back end" +msgstr "" + +#: ../keystone_secure_identity_to_ldap_backend.rst:4 +msgid "" +"The Identity service supports the use of TLS to encrypt LDAP traffic. Before " +"configuring this, you must first verify where your certificate authority " +"file is located. For more information, see the `OpenStack Security Guide SSL " +"introduction `_." +msgstr "" + +#: ../keystone_secure_identity_to_ldap_backend.rst:10 +msgid "Once you verify the location of your certificate authority file:" +msgstr "" + +#: ../keystone_secure_identity_to_ldap_backend.rst:12 +msgid "**To configure TLS encryption on LDAP traffic**" +msgstr "" + +#: ../keystone_secure_identity_to_ldap_backend.rst:14 +msgid "Open the :file:`/etc/keystone/keystone.conf` configuration file." +msgstr "" + +#: ../keystone_secure_identity_to_ldap_backend.rst:16 +msgid "Find the ``[ldap]`` section." +msgstr "" + +#: ../keystone_secure_identity_to_ldap_backend.rst:18 +msgid "" +"In the ``[ldap]`` section, set the ``use_tls`` configuration key to " +"``True``. Doing so will enable TLS." +msgstr "" + +#: ../keystone_secure_identity_to_ldap_backend.rst:21 +msgid "" +"Configure the Identity service to use your certificate authorities file. To " +"do so, set the ``tls_cacertfile`` configuration key in the ``ldap`` section " +"to the certificate authorities file's path." +msgstr "" + +#: ../keystone_secure_identity_to_ldap_backend.rst:27 +msgid "" +"You can also set the ``tls_cacertdir`` (also in the ``ldap`` section) to the " +"directory where all certificate authorities files are kept. If both " +"``tls_cacertfile`` and ``tls_cacertdir`` are set, then the latter will be " +"ignored." +msgstr "" + +#: ../keystone_secure_identity_to_ldap_backend.rst:32 +msgid "" +"Specify what client certificate checks to perform on incoming TLS sessions " +"from the LDAP server. To do so, set the ``tls_req_cert`` configuration key " +"in the ``[ldap]`` section to ``demand``, ``allow``, or ``never``:" +msgstr "" + +#: ../keystone_secure_identity_to_ldap_backend.rst:40 +msgid "" +"``demand`` - The LDAP server always recieves certificate requests. The " +"session terminates if no certificate is provided, or if the certificate " +"provided cannot be verified against the existing certificate authorities " +"file." +msgstr "" + +#: ../keystone_secure_identity_to_ldap_backend.rst:44 +msgid "" +"``allow`` - The LDAP server always recieves certificate requests. The " +"session will proceed as normal even if a certificate is not provided. If a " +"certificate is provided but it cannot be verified against the existing " +"certificate authorities file, the certificate will be ignored and the " +"session will proceed as normal." +msgstr "" + +#: ../keystone_secure_identity_to_ldap_backend.rst:50 +msgid "``never`` - A certificate will never be requested." +msgstr "" + +#: ../keystone_secure_identity_to_ldap_backend.rst:52 +msgid "" +"On distributions that include openstack-config, you can configure TLS " +"encryption on LDAP traffic by running the following commands instead::" +msgstr "" + +#: ../keystone_secure_identity_to_ldap_backend.rst:64 +msgid "" +"``CA_FILE`` is the absolute path to the certificate authorities file that " +"should be used to encrypt LDAP traffic." +msgstr "" + +#: ../keystone_secure_identity_to_ldap_backend.rst:67 +msgid "" +"``CERT_BEHAVIOR`` specifies what client certificate checks to perform on an " +"incoming TLS session from the LDAP server (``demand``, ``allow``, or " +"``never``)." msgstr "" #: ../keystone_token-binding.rst:3 msgid "Configure Identity service for token binding" msgstr "" +#: ../keystone_token-binding.rst:5 +msgid "" +"Token binding embeds information from an external authentication mechanism, " +"such as a Kerberos server or X.509 certificate, inside a token. By using " +"token binding, a client can enforce the use of a specified external " +"authentication mechanism with the token. This additional security mechanism " +"ensures that if a token is stolen, for example, it is not usable without " +"external authentication." +msgstr "" + +#: ../keystone_token-binding.rst:12 +msgid "" +"You configure the authentication types for a token binding in the :file:" +"`keystone.conf` file:" +msgstr "" + +#: ../keystone_token-binding.rst:21 +msgid "or" +msgstr "" + +#: ../keystone_token-binding.rst:29 +msgid "Currently ``kerberos`` and ``x509`` are supported." +msgstr "" + +#: ../keystone_token-binding.rst:31 +msgid "" +"To enforce checking of token binding, set the ``enforce_token_bind`` option " +"to one of these modes:" +msgstr "" + +#: ../keystone_token-binding.rst:35 +msgid "Disables token bind checking." +msgstr "" + +#: ../keystone_token-binding.rst:35 +msgid "``disabled``" +msgstr "" + +#: ../keystone_token-binding.rst:38 +msgid "" +"Enables bind checking. If a token is bound to an unknown authentication " +"mechanism, the server ignores it. The default is this mode." +msgstr "" + +#: ../keystone_token-binding.rst:40 +msgid "``permissive``" +msgstr "" + +#: ../keystone_token-binding.rst:43 +msgid "" +"Enables bind checking. If a token is bound to an unknown authentication " +"mechanism, the server rejects it." +msgstr "" + +#: ../keystone_token-binding.rst:44 +msgid "``strict``" +msgstr "" + +#: ../keystone_token-binding.rst:47 +msgid "" +"Enables bind checking. Requires use of at least authentication mechanism for " +"tokens." +msgstr "" + +#: ../keystone_token-binding.rst:48 +msgid "``required``" +msgstr "" + +#: ../keystone_token-binding.rst:51 +msgid "" +"Enables bind checking. Requires use of kerberos as the authentication " +"mechanism for tokens:" +msgstr "" + +#: ../keystone_token-binding.rst:58 +msgid "``kerberos``" +msgstr "" + +#: ../keystone_token-binding.rst:61 +msgid "" +"Enables bind checking. Requires use of X.509 as the authentication mechanism " +"for tokens:" +msgstr "" + +#: ../keystone_token-binding.rst:67 +msgid "``x509``" +msgstr "" + +#: ../keystone_use_trusts.rst:3 +msgid "Use trusts" +msgstr "" + +#: ../keystone_use_trusts.rst:5 +msgid "" +"OpenStack Identity manages authentication and authorization. A trust is an " +"OpenStack Identity extension that enables delegation and, optionally, " +"impersonation through ``keystone``. A trust extension defines a relationship " +"between:" +msgstr "" + +#: ../keystone_use_trusts.rst:11 +msgid "**Trustor**" +msgstr "" + +#: ../keystone_use_trusts.rst:11 +msgid "The user delegating a limited set of their own rights to another user." +msgstr "" + +#: ../keystone_use_trusts.rst:14 +msgid "The user trust is being delegated to, for a limited time." +msgstr "" + +#: ../keystone_use_trusts.rst:16 +msgid "" +"The trust can eventually allow the trustee to impersonate the trustor. For " +"security reasons, some safeties are added. For example, if a trustor loses a " +"given role, any trusts the user issued with that role, and the related " +"tokens, are automatically revoked." +msgstr "" + +#: ../keystone_use_trusts.rst:19 +msgid "**Trustee**" +msgstr "" + +#: ../keystone_use_trusts.rst:21 +msgid "The delegation parameters are:" +msgstr "" + +#: ../keystone_use_trusts.rst:24 +msgid "**User ID**" +msgstr "" + +#: ../keystone_use_trusts.rst:24 +msgid "The user IDs for the trustor and trustee." +msgstr "" + +#: ../keystone_use_trusts.rst:27 +msgid "" +"The delegated privileges are a combination of a tenant ID and a number of " +"roles that must be a subset of the roles assigned to the trustor." +msgstr "" + +#: ../keystone_use_trusts.rst:31 +msgid "" +"If you omit all privileges, nothing is delegated. You cannot delegate " +"everything." +msgstr "" + +#: ../keystone_use_trusts.rst:32 +msgid "**Privileges**" +msgstr "" + +#: ../keystone_use_trusts.rst:35 +msgid "" +"Defines whether or not the delegation is recursive. If it is recursive, " +"defines the delegation chain length." +msgstr "" + +#: ../keystone_use_trusts.rst:38 +msgid "Specify one of the following values:" +msgstr "" + +#: ../keystone_use_trusts.rst:40 +msgid "``0``. The delegate cannot delegate these permissions further." +msgstr "" + +#: ../keystone_use_trusts.rst:42 +msgid "" +"``1``. The delegate can delegate the permissions to any set of delegates but " +"the latter cannot delegate further." +msgstr "" + +#: ../keystone_use_trusts.rst:45 +msgid "**Delegation depth**" +msgstr "" + +#: ../keystone_use_trusts.rst:45 +msgid "``inf``. The delegation is infinitely recursive." +msgstr "" + +#: ../keystone_use_trusts.rst:48 +msgid "A list of endpoints associated with the delegation." +msgstr "" + +#: ../keystone_use_trusts.rst:50 +msgid "" +"This parameter further restricts the delegation to the specified endpoints " +"only. If you omit the endpoints, the delegation is useless. A special value " +"of ``all_endpoints`` allows the trust to be used by all endpoints associated " +"with the delegated tenant." +msgstr "" + +#: ../keystone_use_trusts.rst:53 +msgid "**Endpoints**" +msgstr "" + +#: ../keystone_use_trusts.rst:55 +msgid "**Duration**" +msgstr "" + +#: ../keystone_use_trusts.rst:56 +msgid "(Optional) Comprised of the start time and end time for the trust." +msgstr "" + +#: ../networking.rst:5 +msgid "Networking" +msgstr "" + +#: ../networking.rst:7 +msgid "" +"Learn OpenStack Networking concepts, architecture, and basic and advanced " +"``neutron`` and ``nova`` command-line interface (CLI) commands." +msgstr "" + +#: ../networking_adv-config.rst:3 +msgid "Advanced configuration options" +msgstr "" + +#: ../networking_adv-config.rst:5 +msgid "" +"This section describes advanced configuration options for various system " +"components. For example, configuration options where the default works but " +"that the user wants to customize options. After installing from packages, ``" +"$NEUTRON_CONF_DIR`` is :file:`/etc/neutron`." +msgstr "" + +#: ../networking_adv-config.rst:11 +msgid "L3 metering agent" +msgstr "" + +#: ../networking_adv-config.rst:13 +msgid "" +"You can run an L3 metering agent that enables layer-3 traffic metering. In " +"general, you should launch the metering agent on all nodes that run the L3 " +"agent:" +msgstr "" + +#: ../networking_adv-config.rst:22 +msgid "" +"You must configure a driver that matches the plug-in that runs on the " +"service. The driver adds metering to the routing interface." +msgstr "" + +#: ../networking_adv-config.rst:26 +msgid "Option" +msgstr "" + +#: ../networking_adv-config.rst:28 +msgid "**Open vSwitch**" +msgstr "" + +#: ../networking_adv-config.rst:30 ../networking_adv-config.rst:36 +msgid "interface\\_driver ($NEUTRON\\_CONF\\_DIR/metering\\_agent.ini)" +msgstr "" + +#: ../networking_adv-config.rst:31 +msgid "neutron.agent.linux.interface. OVSInterfaceDriver" +msgstr "" + +#: ../networking_adv-config.rst:34 +msgid "**Linux Bridge**" +msgstr "" + +#: ../networking_adv-config.rst:37 +msgid "neutron.agent.linux.interface. BridgeInterfaceDriver" +msgstr "" + +#: ../networking_adv-config.rst:42 +msgid "Namespace" +msgstr "" + +#: ../networking_adv-config.rst:44 +msgid "" +"The metering agent and the L3 agent must have the same network namespaces " +"configuration." +msgstr "" + +#: ../networking_adv-config.rst:49 +msgid "" +"If the Linux installation does not support network namespaces, you must " +"disable network namespaces in the L3 metering configuration file. The " +"default value of the ``use_namespaces`` option is ``True``." +msgstr "" + +#: ../networking_adv-config.rst:59 +msgid "L3 metering driver" +msgstr "" + +#: ../networking_adv-config.rst:61 +msgid "" +"You must configure any driver that implements the metering abstraction. " +"Currently the only available implementation uses iptables for metering." +msgstr "" + +#: ../networking_adv-config.rst:70 +msgid "L3 metering service driver" +msgstr "" + +#: ../networking_adv-config.rst:72 +msgid "" +"To enable L3 metering, you must set the following option in the :file:" +"`neutron.conf` file on the host that runs neutron-server:" +msgstr "" + +#: ../networking_adv-features.rst:0 +msgid "**Basic L3 Operations**" +msgstr "" + +#: ../networking_adv-features.rst:0 +msgid "**Basic L3 operations**" +msgstr "" + +#: ../networking_adv-features.rst:0 +msgid "**Basic VMware NSX QoS operations**" +msgstr "" + +#: ../networking_adv-features.rst:0 +msgid "**Basic security group operations**" +msgstr "" + +#: ../networking_adv-features.rst:0 +msgid "**Big Switch Router rule attributes**" +msgstr "" + +#: ../networking_adv-features.rst:0 +msgid "" +"**Configuration options for tuning operational status synchronization in the " +"NSX plug-in**" +msgstr "" + +#: ../networking_adv-features.rst:0 +msgid "**Provider network attributes**" +msgstr "" + +#: ../networking_adv-features.rst:3 +msgid "Advanced features through API extensions" +msgstr "" + +#: ../networking_adv-features.rst:5 +msgid "" +"Several plug-ins implement API extensions that provide capabilities similar " +"to what was available in nova-network. These plug-ins are likely to be of " +"interest to the OpenStack community." +msgstr "" + +#: ../networking_adv-features.rst:10 +msgid "Provider networks" +msgstr "" + +#: ../networking_adv-features.rst:12 +msgid "" +"Networks can be categorized as either tenant networks or provider networks. " +"Tenant networks are created by normal users and details about how they are " +"physically realized are hidden from those users. Provider networks are " +"created with administrative credentials, specifying the details of how the " +"network is physically realized, usually to match some existing network in " +"the data center." +msgstr "" + +#: ../networking_adv-features.rst:19 +msgid "" +"Provider networks enable cloud administrators to create Networking networks " +"that map directly to the physical networks in the data center. This is " +"commonly used to give tenants direct access to a public network that can be " +"used to reach the Internet. It might also be used to integrate with VLANs in " +"the network that already have a defined meaning (for example, enable a VM " +"from the marketing department to be placed on the same VLAN as bare-metal " +"marketing hosts in the same data center)." +msgstr "" + +#: ../networking_adv-features.rst:27 +msgid "" +"The provider extension allows administrators to explicitly manage the " +"relationship between Networking virtual networks and underlying physical " +"mechanisms such as VLANs and tunnels. When this extension is supported, " +"Networking client users with administrative privileges see additional " +"provider attributes on all virtual networks and are able to specify these " +"attributes in order to create provider networks." +msgstr "" + +#: ../networking_adv-features.rst:34 +msgid "" +"The provider extension is supported by the Open vSwitch and Linux Bridge " +"plug-ins. Configuration of these plug-ins requires familiarity with this " +"extension." +msgstr "" + +#: ../networking_adv-features.rst:39 +msgid "Terminology" +msgstr "" + +#: ../networking_adv-features.rst:41 +msgid "" +"A number of terms are used in the provider extension and in the " +"configuration of plug-ins supporting the provider extension:" +msgstr "" + +#: ../networking_adv-features.rst:44 +msgid "**Provider extension terminology**" +msgstr "" + +#: ../networking_adv-features.rst:47 +msgid "Term" +msgstr "" + +#: ../networking_adv-features.rst:49 +msgid "**virtual network**" +msgstr "" + +#: ../networking_adv-features.rst:49 +msgid "" +"An Networking L2 network (identified by a UUID and optional name) whose " +"ports can be attached as vNICs to Compute instances and to various " +"Networking agents. The Open vSwitch and Linux Bridge plug-ins each support " +"several different mechanisms to realize virtual networks." +msgstr "" + +#: ../networking_adv-features.rst:56 +msgid "**physical network**" +msgstr "" + +#: ../networking_adv-features.rst:56 +msgid "" +"A network connecting virtualization hosts (such as compute nodes) with each " +"other and with other network resources. Each physical network might support " +"multiple virtual networks. The provider extension and the plug-in " +"configurations identify physical networks using simple string names." +msgstr "" + +#: ../networking_adv-features.rst:63 +msgid "**tenant network**" +msgstr "" + +#: ../networking_adv-features.rst:63 +msgid "" +"A virtual network that a tenant or an administrator creates. The physical " +"details of the network are not exposed to the tenant." +msgstr "" + +#: ../networking_adv-features.rst:67 +msgid "**provider network**" +msgstr "" + +#: ../networking_adv-features.rst:67 +msgid "" +"A virtual network administratively created to map to a specific network in " +"the data center, typically to enable direct access to non-OpenStack " +"resources on that network. Tenants can be given access to provider networks." +msgstr "" + +#: ../networking_adv-features.rst:73 +msgid "**VLAN network**" +msgstr "" + +#: ../networking_adv-features.rst:73 +msgid "" +"A virtual network implemented as packets on a specific physical network " +"containing IEEE 802.1Q headers with a specific VID field value. VLAN " +"networks sharing the same physical network are isolated from each other at " +"L2 and can even have overlapping IP address spaces. Each distinct physical " +"network supporting VLAN networks is treated as a separate VLAN trunk, with a " +"distinct space of VID values. Valid VID values are 1 through 4094." +msgstr "" + +#: ../networking_adv-features.rst:84 +msgid "**flat network**" +msgstr "" + +#: ../networking_adv-features.rst:84 +msgid "" +"A virtual network implemented as packets on a specific physical network " +"containing no IEEE 802.1Q header. Each physical network can realize at most " +"one flat network." +msgstr "" + +#: ../networking_adv-features.rst:89 +msgid "**local network**" +msgstr "" + +#: ../networking_adv-features.rst:89 +msgid "" +"A virtual network that allows communication within each host, but not across " +"a network. Local networks are intended mainly for single-node test " +"scenarios, but can have other uses." +msgstr "" + +#: ../networking_adv-features.rst:94 +msgid "**GRE network**" +msgstr "" + +#: ../networking_adv-features.rst:94 +msgid "" +"A virtual network implemented as network packets encapsulated using GRE. GRE " +"networks are also referred to as *tunnels*. GRE tunnel packets are routed by " +"the IP routing table for the host, so GRE networks are not associated by " +"Networking with specific physical networks." +msgstr "" + +#: ../networking_adv-features.rst:101 +msgid "**Virtual Extensible LAN (VXLAN) network**" +msgstr "" + +#: ../networking_adv-features.rst:102 +msgid "" +"VXLAN is a proposed encapsulation protocol for running an overlay network on " +"existing Layer 3 infrastructure. An overlay network is a virtual network " +"that is built on top of existing network Layer 2 and Layer 3 technologies to " +"support elastic compute architectures." +msgstr "" + +#: ../networking_adv-features.rst:110 +msgid "" +"The ML2, Open vSwitch, and Linux Bridge plug-ins support VLAN networks, flat " +"networks, and local networks. Only the ML2 and Open vSwitch plug-ins " +"currently support GRE and VXLAN networks, provided that the required " +"features exist in the hosts Linux kernel, Open vSwitch, and iproute2 " +"packages." +msgstr "" + +#: ../networking_adv-features.rst:117 +msgid "Provider attributes" +msgstr "" + +#: ../networking_adv-features.rst:119 +msgid "" +"The provider extension extends the Networking network resource with these " +"attributes:" +msgstr "" + +# #-#-#-#-# networking_adv-features.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +# #-#-#-#-# networking_config-identity.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +#: ../networking_adv-features.rst:127 ../networking_adv-features.rst:690 +#: ../networking_config-identity.rst:166 +msgid "Attribute name" +msgstr "" + +#: ../networking_adv-features.rst:129 +msgid "Default Value" +msgstr "" + +#: ../networking_adv-features.rst:131 +msgid "provider: network\\_type" +msgstr "" + +#: ../networking_adv-features.rst:132 ../networking_adv-features.rst:143 +msgid "String" +msgstr "" + +#: ../networking_adv-features.rst:133 ../networking_adv-features.rst:152 +msgid "N/A" +msgstr "" + +#: ../networking_adv-features.rst:134 +msgid "" +"The physical mechanism by which the virtual network is implemented. Possible " +"values are ``flat``, ``vlan``, ``local``, ``gre``, and ``vxlan``, " +"corresponding to flat networks, VLAN networks, local networks, GRE networks, " +"and VXLAN networks as defined above. All types of provider networks can be " +"created by administrators, while tenant networks can be implemented as " +"``vlan``, ``gre``, ``vxlan``, or ``local`` network types depending on plug-" +"in configuration." +msgstr "" + +#: ../networking_adv-features.rst:142 +msgid "provider: physical_network" +msgstr "" + +#: ../networking_adv-features.rst:144 +msgid "" +"If a physical network named \"default\" has been configured and if provider:" +"network_type is ``flat`` or ``vlan``, then \"default\" is used." +msgstr "" + +#: ../networking_adv-features.rst:147 +msgid "" +"The name of the physical network over which the virtual network is " +"implemented for flat and VLAN networks. Not applicable to the ``local`` or " +"``gre`` network types." +msgstr "" + +#: ../networking_adv-features.rst:150 +msgid "provider:segmentation_id" +msgstr "" + +#: ../networking_adv-features.rst:151 +msgid "Integer" +msgstr "" + +#: ../networking_adv-features.rst:153 +msgid "" +"For VLAN networks, the VLAN VID on the physical network that realizes the " +"virtual network. Valid VLAN VIDs are 1 through 4094. For GRE networks, the " +"tunnel ID. Valid tunnel IDs are any 32 bit unsigned integer. Not applicable " +"to the ``flat`` or ``local`` network types." +msgstr "" + +#: ../networking_adv-features.rst:159 +msgid "" +"To view or set provider extended attributes, a client must be authorized for " +"the ``extension:provider_network:view`` and ``extension:provider_network:" +"set`` actions in the Networking policy configuration. The default Networking " +"configuration authorizes both actions for users with the admin role. An " +"authorized client or an administrative user can view and set the provider " +"extended attributes through Networking API calls. See the section called :" +"ref:`Authentication and authorization` for details on policy configuration." +msgstr "" + +#: ../networking_adv-features.rst:171 +msgid "L3 routing and NAT" +msgstr "" + +#: ../networking_adv-features.rst:173 +msgid "" +"The Networking API provides abstract L2 network segments that are decoupled " +"from the technology used to implement the L2 network. Networking includes an " +"API extension that provides abstract L3 routers that API users can " +"dynamically provision and configure. These Networking routers can connect " +"multiple L2 Networking networks and can also provide a gateway that connects " +"one or more private L2 networks to a shared external network. For example, a " +"public network for access to the Internet. See the *OpenStack Configuration " +"Reference* for details on common models of deploying Networking L3 routers." +msgstr "" + +#: ../networking_adv-features.rst:183 +msgid "" +"The L3 router provides basic NAT capabilities on gateway ports that uplink " +"the router to external networks. This router SNATs all traffic by default " +"and supports floating IPs, which creates a static one-to-one mapping from a " +"public IP on the external network to a private IP on one of the other " +"subnets attached to the router. This allows a tenant to selectively expose " +"VMs on private networks to other hosts on the external network (and often to " +"all hosts on the Internet). You can allocate and map floating IPs from one " +"port to another, as needed." +msgstr "" + +#: ../networking_adv-features.rst:193 +msgid "Basic L3 operations" +msgstr "" + +#: ../networking_adv-features.rst:195 +msgid "" +"External networks are visible to all users. However, the default policy " +"settings enable only administrative users to create, update, and delete " +"external networks." +msgstr "" + +#: ../networking_adv-features.rst:199 +msgid "" +"This table shows example neutron commands that enable you to complete basic " +"L3 operations:" +msgstr "" + +# #-#-#-#-# networking_adv-features.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +# #-#-#-#-# networking_config-agents.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +# #-#-#-#-# networking_use.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +#: ../networking_adv-features.rst:206 ../networking_adv-features.rst:356 +#: ../networking_adv-features.rst:491 ../networking_adv-features.rst:783 +#: ../networking_config-agents.rst:492 ../networking_use.rst:47 +#: ../networking_use.rst:123 ../networking_use.rst:241 +msgid "Operation" +msgstr "" + +#: ../networking_adv-features.rst:208 +msgid "Creates external networks." +msgstr "" + +#: ../networking_adv-features.rst:213 +msgid "Lists external networks." +msgstr "" + +#: ../networking_adv-features.rst:217 +msgid "" +"Creates an internal-only router that connects to multiple L2 networks " +"privately." +msgstr "" + +#: ../networking_adv-features.rst:227 +msgid "" +"Connects a router to an external network, which enables that router to act " +"as a NAT gateway for external connectivity." +msgstr "" + +#: ../networking_adv-features.rst:233 +msgid "" +"The router obtains an interface with the gateway_ip address of the subnet " +"and this interface is attached to a port on the L2 Networking network " +"associated with the subnet. The router also gets a gateway interface to the " +"specified external network. This provides SNAT connectivity to the external " +"network as well as support for floating IPs allocated on that external " +"networks. Commonly an external network maps to a network in the provider." +msgstr "" + +#: ../networking_adv-features.rst:241 +msgid "Lists routers." +msgstr "" + +#: ../networking_adv-features.rst:245 +msgid "Shows information for a specified router." +msgstr "" + +#: ../networking_adv-features.rst:249 +msgid "Shows all internal interfaces for a router." +msgstr "" + +#: ../networking_adv-features.rst:254 +msgid "" +"Identifies the PORT_ID that represents the VM NIC to which the floating IP " +"should map." +msgstr "" + +#: ../networking_adv-features.rst:260 +msgid "" +"This port must be on an Networking subnet that is attached to a router " +"uplinked to the external network used to create the floating IP." +"Conceptually, this is because the router must be able to perform the " +"Destination NAT (DNAT) rewriting of packets from the floating IP address " +"(chosen from a subnet on the external network) to the internal fixed IP " +"(chosen from a private subnet that is behind the router)." +msgstr "" + +#: ../networking_adv-features.rst:267 +msgid "Creates a floating IP address and associates it with a port." +msgstr "" + +#: ../networking_adv-features.rst:272 +msgid "" +"Creates a floating IP address and associates it with a port, in a single " +"step." +msgstr "" + +#: ../networking_adv-features.rst:276 +msgid "Lists floating IPs" +msgstr "" + +#: ../networking_adv-features.rst:280 +msgid "Finds floating IP for a specified VM port." +msgstr "" + +#: ../networking_adv-features.rst:284 +msgid "Disassociates a floating IP address." +msgstr "" + +#: ../networking_adv-features.rst:288 +msgid "Deletes the floating IP address." +msgstr "" + +#: ../networking_adv-features.rst:292 +msgid "Clears the gateway." +msgstr "" + +#: ../networking_adv-features.rst:296 +msgid "Removes the interfaces from the router." +msgstr "" + +#: ../networking_adv-features.rst:300 +msgid "Deletes the router." +msgstr "" + +#: ../networking_adv-features.rst:306 +msgid "Security groups" +msgstr "" + +#: ../networking_adv-features.rst:308 +msgid "" +"Security groups and security group rules allows administrators and tenants " +"the ability to specify the type of traffic and direction (ingress/egress) " +"that is allowed to pass through a port. A security group is a container for " +"security group rules." +msgstr "" + +#: ../networking_adv-features.rst:313 +msgid "" +"When a port is created in Networking it is associated with a security group. " +"If a security group is not specified the port is associated with a 'default' " +"security group. By default, this group drops all ingress traffic and allows " +"all egress. Rules can be added to this group in order to change the behavior." +msgstr "" + +#: ../networking_adv-features.rst:319 +msgid "" +"To use the Compute security group APIs or use Compute to orchestrate the " +"creation of ports for instances on specific security groups, you must " +"complete additional configuration. You must configure the :file:`/etc/nova/" +"nova.conf` file and set the ``security_group_api=neutron`` option on every " +"node that runs nova-compute and nova-api. After you make this change, " +"restart nova-api and nova-compute to pick up this change. Then, you can use " +"both the Compute and OpenStack Network security group APIs at the same time." +msgstr "" + +#: ../networking_adv-features.rst:330 +msgid "" +"To use the Compute security group API with Networking, the Networking plug-" +"in must implement the security group API. The following plug-ins currently " +"implement this: ML2, Open vSwitch, Linux Bridge, NEC, and VMware NSX." +msgstr "" + +#: ../networking_adv-features.rst:335 +msgid "" +"You must configure the correct firewall driver in the ``securitygroup`` " +"section of the plug-in/agent configuration file. Some plug-ins and agents, " +"such as Linux Bridge Agent and Open vSwitch Agent, use the no-operation " +"driver as the default, which results in non-working security groups." +msgstr "" + +#: ../networking_adv-features.rst:341 +msgid "" +"When using the security group API through Compute, security groups are " +"applied to all ports on an instance. The reason for this is that Compute " +"security group APIs are instances based and not port based as Networking." +msgstr "" + +#: ../networking_adv-features.rst:347 +msgid "Basic security group operations" +msgstr "" + +#: ../networking_adv-features.rst:349 +msgid "" +"This table shows example neutron commands that enable you to complete basic " +"security group operations:" +msgstr "" + +#: ../networking_adv-features.rst:358 +msgid "Creates a security group for our web servers." +msgstr "" + +#: ../networking_adv-features.rst:362 +msgid "Lists security groups." +msgstr "" + +#: ../networking_adv-features.rst:366 +msgid "Creates a security group rule to allow port 80 ingress." +msgstr "" + +#: ../networking_adv-features.rst:371 +msgid "Lists security group rules." +msgstr "" + +#: ../networking_adv-features.rst:375 +msgid "Deletes a security group rule." +msgstr "" + +#: ../networking_adv-features.rst:379 +msgid "Deletes a security group." +msgstr "" + +#: ../networking_adv-features.rst:383 +msgid "Creates a port and associates two security groups." +msgstr "" + +#: ../networking_adv-features.rst:387 +msgid "Removes security groups from a port." +msgstr "" + +#: ../networking_adv-features.rst:393 +msgid "Basic Load-Balancer-as-a-Service operations" +msgstr "" + +#: ../networking_adv-features.rst:397 +msgid "" +"The Load-Balancer-as-a-Service (LBaaS) API provisions and configures load " +"balancers. The reference implementation is based on the HAProxy software " +"load balancer." +msgstr "" + +#: ../networking_adv-features.rst:401 +msgid "" +"This list shows example neutron commands that enable you to complete basic " +"LBaaS operations:" +msgstr "" + +#: ../networking_adv-features.rst:404 +msgid "Creates a load balancer pool by using specific provider." +msgstr "" + +#: ../networking_adv-features.rst:406 +msgid "" +":option:`--provider` is an optional argument. If not used, the pool is " +"created with default provider for LBaaS service. You should configure the " +"default provider in the ``[service_providers]`` section of :file:`neutron." +"conf` file. If no default provider is specified for LBaaS, the :option:`--" +"provider` parameter is required for pool creation." +msgstr "" + +#: ../networking_adv-features.rst:417 +msgid "Associates two web servers with pool." +msgstr "" + +#: ../networking_adv-features.rst:424 +msgid "" +"Creates a health monitor that checks to make sure our instances are still " +"running on the specified protocol-port." +msgstr "" + +#: ../networking_adv-features.rst:431 +msgid "Associates a health monitor with pool." +msgstr "" + +#: ../networking_adv-features.rst:437 +msgid "" +"Creates a virtual IP (VIP) address that, when accessed through the load " +"balancer, directs the requests to one of the pool members." +msgstr "" + +#: ../networking_adv-features.rst:446 +msgid "Plug-in specific extensions" +msgstr "" + +#: ../networking_adv-features.rst:448 +msgid "" +"Each vendor can choose to implement additional API extensions to the core " +"API. This section describes the extensions for each plug-in." +msgstr "" + +#: ../networking_adv-features.rst:452 +msgid "VMware NSX extensions" +msgstr "" + +#: ../networking_adv-features.rst:454 +msgid "These sections explain NSX plug-in extensions." +msgstr "" + +#: ../networking_adv-features.rst:457 +msgid "VMware NSX QoS extension" +msgstr "" + +#: ../networking_adv-features.rst:459 +msgid "" +"The VMware NSX QoS extension rate-limits network ports to guarantee a " +"specific amount of bandwidth for each port. This extension, by default, is " +"only accessible by a tenant with an admin role but is configurable through " +"the :file:`policy.json` file. To use this extension, create a queue and " +"specify the min/max bandwidth rates (kbps) and optionally set the QoS " +"Marking and DSCP value (if your network fabric uses these values to make " +"forwarding decisions). Once created, you can associate a queue with a " +"network. Then, when ports are created on that network they are automatically " +"created and associated with the specific queue size that was associated with " +"the network. Because one size queue for a every port on a network might not " +"be optimal, a scaling factor from the nova flavor ``rxtx_factor`` is passed " +"in from Compute when creating the port to scale the queue." +msgstr "" + +#: ../networking_adv-features.rst:473 +msgid "" +"Lastly, if you want to set a specific baseline QoS policy for the amount of " +"bandwidth a single port can use (unless a network queue is specified with " +"the network a port is created on) a default queue can be created in " +"Networking which then causes ports created to be associated with a queue of " +"that size times the rxtx scaling factor. Note that after a network or " +"default queue is specified, queues are added to ports that are subsequently " +"created but are not added to existing ports." +msgstr "" + +#: ../networking_adv-features.rst:482 +msgid "Basic VMware NSX QoS operations" +msgstr "" + +#: ../networking_adv-features.rst:484 +msgid "" +"This table shows example neutron commands that enable you to complete basic " +"queue operations:" +msgstr "" + +#: ../networking_adv-features.rst:493 +msgid "Creates QoS queue (admin-only)." +msgstr "" + +#: ../networking_adv-features.rst:497 +msgid "Associates a queue with a network." +msgstr "" + +#: ../networking_adv-features.rst:501 +msgid "Creates a default system queue." +msgstr "" + +#: ../networking_adv-features.rst:505 +msgid "Lists QoS queues." +msgstr "" + +#: ../networking_adv-features.rst:509 +msgid "Deletes a QoS queue." +msgstr "" + +#: ../networking_adv-features.rst:515 +msgid "VMware NSX provider networks extension" +msgstr "" + +#: ../networking_adv-features.rst:517 +msgid "" +"Provider networks can be implemented in different ways by the underlying NSX " +"platform." +msgstr "" + +#: ../networking_adv-features.rst:520 +msgid "" +"The *FLAT* and *VLAN* network types use bridged transport connectors. These " +"network types enable the attachment of large number of ports. To handle the " +"increased scale, the NSX plug-in can back a single OpenStack Network with a " +"chain of NSX logical switches. You can specify the maximum number of ports " +"on each logical switch in this chain on the ``max_lp_per_bridged_ls`` " +"parameter, which has a default value of 5,000." +msgstr "" + +#: ../networking_adv-features.rst:527 +msgid "" +"The recommended value for this parameter varies with the NSX version running " +"in the back-end, as shown in the following table." +msgstr "" + +#: ../networking_adv-features.rst:530 +msgid "**Recommended values for max_lp_per_bridged_ls**" +msgstr "" + +#: ../networking_adv-features.rst:533 +msgid "NSX version" +msgstr "" + +#: ../networking_adv-features.rst:533 +msgid "Recommended Value" +msgstr "" + +#: ../networking_adv-features.rst:535 +msgid "2.x" +msgstr "" + +#: ../networking_adv-features.rst:535 +msgid "64" +msgstr "" + +#: ../networking_adv-features.rst:537 +msgid "3.0.x" +msgstr "" + +#: ../networking_adv-features.rst:537 ../networking_adv-features.rst:539 +msgid "5,000" +msgstr "" + +#: ../networking_adv-features.rst:539 +msgid "3.1.x" +msgstr "" + +#: ../networking_adv-features.rst:541 +msgid "10,000" +msgstr "" + +#: ../networking_adv-features.rst:541 +msgid "3.2.x" +msgstr "" + +#: ../networking_adv-features.rst:544 +msgid "" +"In addition to these network types, the NSX plug-in also supports a special " +"*l3_ext* network type, which maps external networks to specific NSX gateway " +"services as discussed in the next section." +msgstr "" + +#: ../networking_adv-features.rst:549 +msgid "VMware NSX L3 extension" +msgstr "" + +#: ../networking_adv-features.rst:551 +msgid "" +"NSX exposes its L3 capabilities through gateway services which are usually " +"configured out of band from OpenStack. To use NSX with L3 capabilities, " +"first create an L3 gateway service in the NSX Manager. Next, in :file:`/etc/" +"neutron/plugins/vmware/nsx.ini` set ``default_l3_gw_service_uuid`` to this " +"value. By default, routers are mapped to this gateway service." +msgstr "" + +#: ../networking_adv-features.rst:559 +msgid "VMware NSX L3 extension operations" +msgstr "" + +#: ../networking_adv-features.rst:561 +msgid "Create external network and map it to a specific NSX gateway service:" +msgstr "" + +#: ../networking_adv-features.rst:568 +msgid "Terminate traffic on a specific VLAN from a NSX gateway service:" +msgstr "" + +#: ../networking_adv-features.rst:576 +msgid "Operational status synchronization in the VMware NSX plug-in" +msgstr "" + +#: ../networking_adv-features.rst:578 +msgid "" +"Starting with the Havana release, the VMware NSX plug-in provides an " +"asynchronous mechanism for retrieving the operational status for neutron " +"resources from the NSX back-end; this applies to *network*, *port*, and " +"*router* resources." +msgstr "" + +#: ../networking_adv-features.rst:583 +msgid "" +"The back-end is polled periodically and the status for every resource is " +"retrieved; then the status in the Networking database is updated only for " +"the resources for which a status change occurred. As operational status is " +"now retrieved asynchronously, performance for ``GET`` operations is " +"consistently improved." +msgstr "" + +#: ../networking_adv-features.rst:589 +msgid "" +"Data to retrieve from the back-end are divided in chunks in order to avoid " +"expensive API requests; this is achieved leveraging NSX APIs response paging " +"capabilities. The minimum chunk size can be specified using a configuration " +"option; the actual chunk size is then determined dynamically according to: " +"total number of resources to retrieve, interval between two synchronization " +"task runs, minimum delay between two subsequent requests to the NSX back-end." +msgstr "" + +#: ../networking_adv-features.rst:597 +msgid "" +"The operational status synchronization can be tuned or disabled using the " +"configuration options reported in this table; it is however worth noting " +"that the default values work fine in most cases." +msgstr "" + +#: ../networking_adv-features.rst:605 +msgid "Option name" +msgstr "" + +#: ../networking_adv-features.rst:607 +msgid "Default value" +msgstr "" + +#: ../networking_adv-features.rst:608 +msgid "Type and constraints" +msgstr "" + +#: ../networking_adv-features.rst:610 +msgid "``state_sync_interval``" +msgstr "" + +#: ../networking_adv-features.rst:611 ../networking_adv-features.rst:620 +#: ../networking_adv-features.rst:627 ../networking_adv-features.rst:634 +#: ../networking_adv-features.rst:645 +msgid "``nsx_sync``" +msgstr "" + +#: ../networking_adv-features.rst:612 +msgid "10 seconds" +msgstr "" + +#: ../networking_adv-features.rst:613 ../networking_adv-features.rst:636 +msgid "Integer; no constraint." +msgstr "" + +#: ../networking_adv-features.rst:614 +msgid "" +"Interval in seconds between two run of the synchronization task. If the " +"synchronization task takes more than ``state_sync_interval`` seconds to " +"execute, a new instance of the task is started as soon as the other is " +"completed. Setting the value for this option to 0 will disable the " +"synchronization task." +msgstr "" + +#: ../networking_adv-features.rst:619 +msgid "``max_random_sync_delay``" +msgstr "" + +#: ../networking_adv-features.rst:621 +msgid "0 seconds" +msgstr "" + +#: ../networking_adv-features.rst:622 +msgid "Integer. Must not exceed ``min_sync_req_delay``" +msgstr "" + +#: ../networking_adv-features.rst:623 +msgid "" +"When different from zero, a random delay between 0 and " +"``max_random_sync_delay`` will be added before processing the next chunk." +msgstr "" + +#: ../networking_adv-features.rst:626 +msgid "``min_sync_req_delay``" +msgstr "" + +#: ../networking_adv-features.rst:628 +msgid "1 second" +msgstr "" + +#: ../networking_adv-features.rst:629 +msgid "Integer. Must not exceed ``state_sync_interval``." +msgstr "" + +#: ../networking_adv-features.rst:630 +msgid "" +"The value of this option can be tuned according to the observed load on the " +"NSX controllers. Lower values will result in faster synchronization, but " +"might increase the load on the controller cluster." +msgstr "" + +#: ../networking_adv-features.rst:633 +msgid "``min_chunk_size``" +msgstr "" + +#: ../networking_adv-features.rst:635 +msgid "500 resources" +msgstr "" + +#: ../networking_adv-features.rst:637 +msgid "" +"Minimum number of resources to retrieve from the back-end for each " +"synchronization chunk. The expected number of synchronization chunks is " +"given by the ratio between ``state_sync_interval`` and " +"``min_sync_req_delay``. This size of a chunk might increase if the total " +"number of resources is such that more than ``min_chunk_size`` resources must " +"be fetched in one chunk with the current number of chunks." +msgstr "" + +#: ../networking_adv-features.rst:644 +msgid "``always_read_status``" +msgstr "" + +#: ../networking_adv-features.rst:646 +msgid "False" +msgstr "" + +#: ../networking_adv-features.rst:647 +msgid "Boolean; no constraint." +msgstr "" + +#: ../networking_adv-features.rst:648 +msgid "" +"When this option is enabled, the operational status will always be retrieved " +"from the NSX back-end ad every ``GET`` request. In this case it is advisable " +"to disable the synchronization task." +msgstr "" + +#: ../networking_adv-features.rst:652 +msgid "" +"When running multiple OpenStack Networking server instances, the status " +"synchronization task should not run on every node; doing so sends " +"unnecessary traffic to the NSX back-end and performs unnecessary DB " +"operations. Set the ``state_sync_interval`` configuration option to a non-" +"zero value exclusively on a node designated for back-end status " +"synchronization." +msgstr "" + +#: ../networking_adv-features.rst:659 +msgid "" +"The ``fields=status`` parameter in Networking API requests always triggers " +"an explicit query to the NSX back end, even when you enable asynchronous " +"state synchronization. For example, ``GET /v2.0/networks/NET_ID?" +"fields=status&fields=name``." +msgstr "" + +#: ../networking_adv-features.rst:665 +msgid "Big Switch plug-in extensions" +msgstr "" + +#: ../networking_adv-features.rst:667 +msgid "" +"This section explains the Big Switch neutron plug-in-specific extension." +msgstr "" + +#: ../networking_adv-features.rst:670 +msgid "Big Switch router rules" +msgstr "" + +#: ../networking_adv-features.rst:672 +msgid "" +"Big Switch allows router rules to be added to each tenant router. These " +"rules can be used to enforce routing policies such as denying traffic " +"between subnets or traffic to external networks. By enforcing these at the " +"router level, network segmentation policies can be enforced across many VMs " +"that have differing security groups." +msgstr "" + +#: ../networking_adv-features.rst:679 +msgid "Router rule attributes" +msgstr "" + +#: ../networking_adv-features.rst:681 +msgid "" +"Each tenant router has a set of router rules associated with it. Each router " +"rule has the attributes in this table. Router rules and their attributes can " +"be set using the :command:`neutron router-update` command, through the " +"horizon interface or the Networking API." +msgstr "" + +# #-#-#-#-# networking_adv-features.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +# #-#-#-#-# networking_config-identity.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +#: ../networking_adv-features.rst:691 ../networking_config-identity.rst:167 +msgid "Required" +msgstr "" + +#: ../networking_adv-features.rst:692 +msgid "Input type" +msgstr "" + +#: ../networking_adv-features.rst:694 +msgid "source" +msgstr "" + +# #-#-#-#-# networking_adv-features.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +# #-#-#-#-# telemetry-data-collection.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +#: ../networking_adv-features.rst:695 ../networking_adv-features.rst:700 +#: ../networking_adv-features.rst:705 ../telemetry-data-collection.rst:1046 +#: ../telemetry-data-collection.rst:1050 +msgid "Yes" +msgstr "" + +#: ../networking_adv-features.rst:696 ../networking_adv-features.rst:701 +msgid "A valid CIDR or one of the keywords 'any' or 'external'" +msgstr "" + +#: ../networking_adv-features.rst:697 +msgid "" +"The network that a packet's source IP must match for the rule to be applied." +msgstr "" + +#: ../networking_adv-features.rst:699 +msgid "destination" +msgstr "" + +#: ../networking_adv-features.rst:702 +msgid "" +"The network that a packet's destination IP must match for the rule to be " +"applied." +msgstr "" + +#: ../networking_adv-features.rst:704 +msgid "action" +msgstr "" + +#: ../networking_adv-features.rst:706 +msgid "'permit' or 'deny'" +msgstr "" + +#: ../networking_adv-features.rst:707 +msgid "" +"Determines whether or not the matched packets will allowed to cross the " +"router." +msgstr "" + +#: ../networking_adv-features.rst:709 +msgid "nexthop" +msgstr "" + +# #-#-#-#-# networking_adv-features.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +# #-#-#-#-# telemetry-data-collection.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +#: ../networking_adv-features.rst:710 ../telemetry-data-collection.rst:1054 +#: ../telemetry-data-collection.rst:1058 +msgid "No" +msgstr "" + +#: ../networking_adv-features.rst:711 +msgid "" +"A plus-separated (+) list of next-hop IP addresses. For example, " +"``1.1.1.1+1.1.1.2``." +msgstr "" + +#: ../networking_adv-features.rst:713 +msgid "" +"Overrides the default virtual router used to handle traffic for packets that " +"match the rule." +msgstr "" + +#: ../networking_adv-features.rst:717 +msgid "Order of rule processing" +msgstr "" + +#: ../networking_adv-features.rst:719 +msgid "" +"The order of router rules has no effect. Overlapping rules are evaluated " +"using longest prefix matching on the source and destination fields. The " +"source field is matched first so it always takes higher precedence over the " +"destination field. In other words, longest prefix matching is used on the " +"destination field only if there are multiple matching rules with the same " +"source." +msgstr "" + +#: ../networking_adv-features.rst:727 +msgid "Big Switch router rules operations" +msgstr "" + +#: ../networking_adv-features.rst:729 +msgid "" +"Router rules are configured with a router update operation in OpenStack " +"Networking. The update overrides any previous rules so all rules must be " +"provided at the same time." +msgstr "" + +#: ../networking_adv-features.rst:733 +msgid "" +"Update a router with rules to permit traffic by default but block traffic " +"from external networks to the 10.10.10.0/24 subnet:" +msgstr "" + +#: ../networking_adv-features.rst:742 +msgid "Specify alternate next-hop addresses for a specific subnet:" +msgstr "" + +#: ../networking_adv-features.rst:750 +msgid "Block traffic between two subnets while allowing everything else:" +msgstr "" + +#: ../networking_adv-features.rst:759 +msgid "L3 metering" +msgstr "" + +#: ../networking_adv-features.rst:761 +msgid "" +"The L3 metering API extension enables administrators to configure IP ranges " +"and assign a specified label to them to be able to measure traffic that goes " +"through a virtual router." +msgstr "" + +#: ../networking_adv-features.rst:765 +msgid "" +"The L3 metering extension is decoupled from the technology that implements " +"the measurement. Two abstractions have been added: One is the metering label " +"that can contain metering rules. Because a metering label is associated with " +"a tenant, all virtual routers in this tenant are associated with this label." +msgstr "" + +#: ../networking_adv-features.rst:772 +msgid "Basic L3 metering operations" +msgstr "" + +#: ../networking_adv-features.rst:774 +msgid "Only administrators can manage the L3 metering labels and rules." +msgstr "" + +#: ../networking_adv-features.rst:776 +msgid "" +"This table shows example :command:`neutron` commands that enable you to " +"complete basic L3 metering operations:" +msgstr "" + +#: ../networking_adv-features.rst:785 +msgid "Creates a metering label." +msgstr "" + +#: ../networking_adv-features.rst:789 +msgid "Lists metering labels." +msgstr "" + +#: ../networking_adv-features.rst:793 +msgid "Shows information for a specified label." +msgstr "" + +#: ../networking_adv-features.rst:798 +msgid "Deletes a metering label." +msgstr "" + +#: ../networking_adv-features.rst:803 +msgid "Creates a metering rule." +msgstr "" + +# #-#-#-#-# networking_adv-features.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +# #-#-#-#-# networking_config-agents.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +# #-#-#-#-# networking_config-identity.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +# #-#-#-#-# networking_use.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +#: ../networking_adv-features.rst:809 ../networking_adv-features.rst:833 +#: ../networking_config-agents.rst:94 ../networking_config-identity.rst:53 +#: ../networking_config-identity.rst:75 ../networking_use.rst:101 +msgid "For example:" +msgstr "" + +#: ../networking_adv-features.rst:816 +msgid "Lists metering all label rules." +msgstr "" + +#: ../networking_adv-features.rst:820 +msgid "Shows information for a specified label rule." +msgstr "" + +#: ../networking_adv-features.rst:824 +msgid "Deletes a metering label rule." +msgstr "" + +#: ../networking_adv-features.rst:828 +msgid "Lists the value of created metering label rules." +msgstr "" + +#: ../networking_adv-operational-features.rst:3 +msgid "Advanced operational features" +msgstr "" + +#: ../networking_adv-operational-features.rst:6 +msgid "Logging settings" +msgstr "" + +#: ../networking_adv-operational-features.rst:8 +msgid "" +"Networking components use Python logging module to do logging. Logging " +"configuration can be provided in :file:`neutron.conf` or as command-line " +"options. Command options override ones in :file:`neutron.conf`." +msgstr "" + +#: ../networking_adv-operational-features.rst:12 +msgid "" +"To configure logging for Networking components, use one of these methods:" +msgstr "" + +#: ../networking_adv-operational-features.rst:15 +msgid "Provide logging settings in a logging configuration file." +msgstr "" + +#: ../networking_adv-operational-features.rst:17 +msgid "" +"See `Python logging how-to `__ to " +"learn more about logging." +msgstr "" + +#: ../networking_adv-operational-features.rst:21 +msgid "Provide logging setting in :file:`neutron.conf`." +msgstr "" + +#: ../networking_adv-operational-features.rst:50 +msgid "" +"Notifications can be sent when Networking resources such as network, subnet " +"and port are created, updated or deleted." +msgstr "" + +#: ../networking_adv-operational-features.rst:54 +msgid "Notification options" +msgstr "" + +#: ../networking_adv-operational-features.rst:56 +msgid "" +"To support DHCP agent, rpc\\_notifier driver must be set. To set up the " +"notification, edit notification options in :file:`neutron.conf`:" +msgstr "" + +#: ../networking_adv-operational-features.rst:71 +msgid "Setting cases" +msgstr "" + +#: ../networking_adv-operational-features.rst:74 +msgid "Logging and RPC" +msgstr "" + +#: ../networking_adv-operational-features.rst:76 +msgid "" +"These options configure the Networking server to send notifications through " +"logging and RPC. The logging options are described in OpenStack " +"Configuration Reference . RPC notifications go to ``notifications.info`` " +"queue bound to a topic exchange defined by ``control_exchange`` in :file:" +"`neutron.conf`." +msgstr "" + +#: ../networking_adv-operational-features.rst:124 +msgid "Multiple RPC topics" +msgstr "" + +#: ../networking_adv-operational-features.rst:126 +msgid "" +"These options configure the Networking server to send notifications to " +"multiple RPC topics. RPC notifications go to ``notifications_one.info`` and " +"``notifications_two.info`` queues bound to a topic exchange defined by " +"``control_exchange`` in :file:`neutron.conf`." +msgstr "" + +#: ../networking_arch.rst:3 +msgid "Networking architecture" +msgstr "" + +#: ../networking_arch.rst:5 +msgid "" +"Before you deploy Networking, it is useful to understand the Networking " +"services and how they interact with the OpenStack components." +msgstr "" + +#: ../networking_arch.rst:9 +msgid "Overview" +msgstr "" + +#: ../networking_arch.rst:11 +msgid "" +"Networking is a standalone component in the OpenStack modular architecture. " +"It's positioned alongside OpenStack components such as Compute, Image " +"service, Identity, or dashboard. Like those components, a deployment of " +"Networking often involves deploying several services to a variety of hosts." +msgstr "" + +#: ../networking_arch.rst:17 +msgid "" +"The Networking server uses the neutron-server daemon to expose the " +"Networking API and enable administration of the configured Networking plug-" +"in. Typically, the plug-in requires access to a database for persistent " +"storage (also similar to other OpenStack services)." +msgstr "" + +#: ../networking_arch.rst:22 +msgid "" +"If your deployment uses a controller host to run centralized Compute " +"components, you can deploy the Networking server to that same host. However, " +"Networking is entirely standalone and can be deployed to a dedicated host. " +"Depending on your configuration, Networking can also include the following " +"agents:" +msgstr "" + +#: ../networking_arch.rst:29 +msgid "Agent" +msgstr "" + +#: ../networking_arch.rst:31 +msgid "**plug-in agent** (``neutron-*-agent``)" +msgstr "" + +#: ../networking_arch.rst:32 +msgid "" +"Runs on each hypervisor to perform local vSwitch configuration. The agent " +"that runs, depends on the plug-in that you use. Certain plug-ins do not " +"require an agent." +msgstr "" + +#: ../networking_arch.rst:37 +msgid "**dhcp agent** (``neutron-dhcp-agent``)" +msgstr "" + +#: ../networking_arch.rst:38 +msgid "" +"Provides DHCP services to tenant networks. Required by certain plug-ins." +msgstr "" + +#: ../networking_arch.rst:41 +msgid "**l3 agent** (``neutron-l3-agent``)" +msgstr "" + +#: ../networking_arch.rst:42 +msgid "" +"Provides L3/NAT forwarding to provide external network access for VMs on " +"tenant networks. Required by certain plug-ins." +msgstr "" + +#: ../networking_arch.rst:46 +msgid "**metering agent** (``neutron-metering-agent``)" +msgstr "" + +#: ../networking_arch.rst:47 +msgid "Provides L3 traffic metering for tenant networks." +msgstr "" + +#: ../networking_arch.rst:51 +msgid "" +"These agents interact with the main neutron process through RPC (for " +"example, RabbitMQ or Qpid) or through the standard Networking API. In " +"addition, Networking integrates with OpenStack components in a number of " +"ways:" +msgstr "" + +#: ../networking_arch.rst:56 +msgid "" +"Networking relies on the Identity service (keystone) for the authentication " +"and authorization of all API requests." +msgstr "" + +#: ../networking_arch.rst:59 +msgid "" +"Compute (nova) interacts with Networking through calls to its standard API. " +"As part of creating a VM, the nova-compute service communicates with the " +"Networking API to plug each virtual NIC on the VM into a particular network." +msgstr "" + +#: ../networking_arch.rst:64 +msgid "" +"The dashboard (horizon) integrates with the Networking API, enabling " +"administrators and tenant users to create and manage network services " +"through a web-based GUI." +msgstr "" + +#: ../networking_arch.rst:69 +msgid "VMware NSX integration" +msgstr "" + +#: ../networking_arch.rst:71 +msgid "" +"OpenStack Networking uses the NSX plug-in to integrate with an existing " +"VMware vCenter deployment. When installed on the network nodes, the NSX plug-" +"in enables a NSX controller to centrally manage configuration settings and " +"push them to managed network nodes. Network nodes are considered managed " +"when they're added as hypervisors to the NSX controller." +msgstr "" + +#: ../networking_arch.rst:78 +msgid "" +"The diagrams below depict some VMware NSX deployment examples. The first " +"diagram illustrates the traffic flow between VMs on separate Compute nodes, " +"and the second diagram between two VMs on a single Compute node. Note the " +"placement of the VMware NSX plug-in and the neutron-server service on the " +"network node. The green arrow indicates the management relationship between " +"the NSX controller and the network node." +msgstr "" + +#: ../networking_arch.rst:85 +msgid "|VMware NSX deployment example - two Compute nodes|" +msgstr "" + +#: ../networking_arch.rst:87 +msgid "|VMware NSX deployment example - single Compute node|" +msgstr "" + +#: ../networking_auth.rst:5 +msgid "Authentication and authorization" +msgstr "" + +#: ../networking_auth.rst:7 +msgid "" +"Networking uses the Identity service as the default authentication service. " +"When the Identity service is enabled, users who submit requests to the " +"Networking service must provide an authentication token in ``X-Auth-Token`` " +"request header. Users obtain this token by authenticating with the Identity " +"service endpoint. For more information about authentication with the " +"Identity service, see `OpenStack Identity service API v2.0 Reference `__. When the Identity " +"service is enabled, it is not mandatory to specify the tenant ID for " +"resources in create requests because the tenant ID is derived from the " +"authentication token." +msgstr "" + +#: ../networking_auth.rst:19 +msgid "" +"The default authorization settings only allow administrative users to create " +"resources on behalf of a different tenant. Networking uses information " +"received from Identity to authorize user requests. Networking handles two " +"kind of authorization policies:" +msgstr "" + +#: ../networking_auth.rst:24 +msgid "" +"**Operation-based** policies specify access criteria for specific " +"operations, possibly with fine-grained control over specific attributes." +msgstr "" + +#: ../networking_auth.rst:28 +msgid "" +"**Resource-based** policies specify whether access to specific resource is " +"granted or not according to the permissions configured for the resource " +"(currently available only for the network resource). The actual " +"authorization policies enforced in Networking might vary from deployment to " +"deployment." +msgstr "" + +#: ../networking_auth.rst:34 +msgid "" +"The policy engine reads entries from the :file:`policy.json` file. The " +"actual location of this file might vary from distribution to distribution. " +"Entries can be updated while the system is running, and no service restart " +"is required. Every time the policy file is updated, the policies are " +"automatically reloaded. Currently the only way of updating such policies is " +"to edit the policy file. In this section, the terms *policy* and *rule* " +"refer to objects that are specified in the same way in the policy file. " +"There are no syntax differences between a rule and a policy. A policy is " +"something that is matched directly from the Networking policy engine. A rule " +"is an element in a policy, which is evaluated. For instance in " +"``create_subnet: [[\"admin_or_network_owner\"]]``, *create_subnet* is a " +"policy, and *admin_or_network_owner* is a rule." +msgstr "" + +#: ../networking_auth.rst:48 +msgid "" +"Policies are triggered by the Networking policy engine whenever one of them " +"matches a Networking API operation or a specific attribute being used in a " +"given operation. For instance the ``create_subnet`` policy is triggered " +"every time a ``POST /v2.0/subnets`` request is sent to the Networking " +"server; on the other hand ``create_network:shared`` is triggered every time " +"the *shared* attribute is explicitly specified (and set to a value different " +"from its default) in a ``POST /v2.0/networks`` request. It is also worth " +"mentioning that policies can also be related to specific API extensions; for " +"instance ``extension:provider_network:set`` is triggered if the attributes " +"defined by the Provider Network extensions are specified in an API request." +msgstr "" + +#: ../networking_auth.rst:61 +msgid "" +"An authorization policy can be composed by one or more rules. If more rules " +"are specified then the evaluation policy succeeds if any of the rules " +"evaluates successfully; if an API operation matches multiple policies, then " +"all the policies must evaluate successfully. Also, authorization rules are " +"recursive. Once a rule is matched, the rule(s) can be resolved to another " +"rule, until a terminal rule is reached." +msgstr "" + +#: ../networking_auth.rst:68 +msgid "" +"The Networking policy engine currently defines the following kinds of " +"terminal rules:" +msgstr "" + +#: ../networking_auth.rst:71 +msgid "" +"**Role-based rules** evaluate successfully if the user who submits the " +"request has the specified role. For instance ``\"role:admin\"`` is " +"successful if the user who submits the request is an administrator." +msgstr "" + +#: ../networking_auth.rst:75 +msgid "" +"**Field-based rules** evaluate successfully if a field of the resource " +"specified in the current request matches a specific value. For instance ``" +"\"field:networks:shared=True\"`` is successful if the ``shared`` attribute " +"of the ``network`` resource is set to true." +msgstr "" + +#: ../networking_auth.rst:80 +msgid "" +"**Generic rules** compare an attribute in the resource with an attribute " +"extracted from the user's security credentials and evaluates successfully if " +"the comparison is successful. For instance ``\"tenant_id:%(tenant_id)s\"`` " +"is successful if the tenant identifier in the resource is equal to the " +"tenant identifier of the user submitting the request." +msgstr "" + +#: ../networking_auth.rst:87 +msgid "This extract is from the default :file:`policy.json` file:" +msgstr "" + +#: ../networking_auth.rst:89 +msgid "" +"A rule that evaluates successfully if the current user is an administrator " +"or the owner of the resource specified in the request (tenant identifier is " +"equal)." +msgstr "" + +#: ../networking_auth.rst:127 +msgid "" +"The default policy that is always evaluated if an API operation does not " +"match any of the policies in ``policy.json``." +msgstr "" + +#: ../networking_auth.rst:165 +msgid "" +"This policy evaluates successfully if either *admin\\_or\\_owner*, or " +"*shared* evaluates successfully." +msgstr "" + +#: ../networking_auth.rst:180 +msgid "" +"This policy restricts the ability to manipulate the *shared* attribute for a " +"network to administrators only." +msgstr "" + +#: ../networking_auth.rst:205 +msgid "" +"This policy restricts the ability to manipulate the *mac\\_address* " +"attribute for a port only to administrators and the owner of the network " +"where the port is attached." +msgstr "" + +#: ../networking_auth.rst:233 +msgid "" +"In some cases, some operations are restricted to administrators only. This " +"example shows you how to modify a policy file to permit tenants to define " +"networks, see their resources, and permit administrative users to perform " +"all other operations:" +msgstr "" + +#: ../networking_config-agents.rst:3 +msgid "Configure neutron agents" +msgstr "" + +#: ../networking_config-agents.rst:5 +msgid "" +"Plug-ins typically have requirements for particular software that must be " +"run on each node that handles data packets. This includes any node that runs " +"nova-compute and nodes that run dedicated OpenStack Networking service " +"agents such as ``neutron-dhcp-agent``, ``neutron-l3-agent``, ``neutron-" +"metering-agent`` or ``neutron-lbaas-agent``." +msgstr "" + +#: ../networking_config-agents.rst:11 +msgid "" +"A data-forwarding node typically has a network interface with an IP address " +"on the management network and another interface on the data network." +msgstr "" + +#: ../networking_config-agents.rst:15 +msgid "" +"This section shows you how to install and configure a subset of the " +"available plug-ins, which might include the installation of switching " +"software (for example, Open vSwitch) and as agents used to communicate with " +"the neutron-server process running elsewhere in the data center." +msgstr "" + +#: ../networking_config-agents.rst:21 +msgid "Configure data-forwarding nodes" +msgstr "" + +#: ../networking_config-agents.rst:24 +msgid "Node set up: NSX plug-in" +msgstr "" + +#: ../networking_config-agents.rst:26 +msgid "" +"If you use the NSX plug-in, you must also install Open vSwitch on each data-" +"forwarding node. However, you do not need to install an additional agent on " +"each node." +msgstr "" + +#: ../networking_config-agents.rst:32 +msgid "" +"It is critical that you run an Open vSwitch version that is compatible with " +"the current version of the NSX Controller software. Do not use the Open " +"vSwitch version that is installed by default on Ubuntu. Instead, use the " +"Open vSwitch version that is provided on the VMware support portal for your " +"NSX Controller version." +msgstr "" + +#: ../networking_config-agents.rst:38 +msgid "**To set up each node for the NSX plug-in**" +msgstr "" + +#: ../networking_config-agents.rst:40 +msgid "" +"Ensure that each data-forwarding node has an IP address on the management " +"network, and an IP address on the data network that is used for tunneling " +"data traffic. For full details on configuring your forwarding node, see the " +"``NSX Administrator Guide``." +msgstr "" + +#: ../networking_config-agents.rst:45 +msgid "" +"Use the ``NSX Administrator Guide`` to add the node as a Hypervisor by using " +"the NSX Manager GUI. Even if your forwarding node has no VMs and is only " +"used for services agents like ``neutron-dhcp-agent`` or ``neutron-lbaas-" +"agent``, it should still be added to NSX as a Hypervisor." +msgstr "" + +#: ../networking_config-agents.rst:50 +msgid "" +"After following the NSX Administrator Guide, use the page for this " +"Hypervisor in the NSX Manager GUI to confirm that the node is properly " +"connected to the NSX Controller Cluster and that the NSX Controller Cluster " +"can see the ``br-int`` integration bridge." +msgstr "" + +#: ../networking_config-agents.rst:56 +msgid "Configure DHCP agent" +msgstr "" + +#: ../networking_config-agents.rst:58 +msgid "" +"The DHCP service agent is compatible with all existing plug-ins and is " +"required for all deployments where VMs should automatically receive IP " +"addresses through DHCP." +msgstr "" + +#: ../networking_config-agents.rst:62 +msgid "**To install and configure the DHCP agent**" +msgstr "" + +#: ../networking_config-agents.rst:64 +msgid "" +"You must configure the host running the neutron-dhcp-agent as a data " +"forwarding node according to the requirements for your plug-in." +msgstr "" + +#: ../networking_config-agents.rst:67 +msgid "Install the DHCP agent:" +msgstr "" + +#: ../networking_config-agents.rst:73 +msgid "" +"Update any options in the :file:`/etc/neutron/dhcp_agent.ini` file that " +"depend on the plug-in in use. See the sub-sections." +msgstr "" + +#: ../networking_config-agents.rst:78 +msgid "" +"If you reboot a node that runs the DHCP agent, you must run the :command:" +"`neutron-ovs-cleanup` command before the neutron-dhcp-agent service starts." +msgstr "" + +#: ../networking_config-agents.rst:82 +msgid "" +"On Red Hat, SUSE, and Ubuntu based systems, the ``neutron-ovs-cleanup`` " +"service runs the :command:`neutron-ovs-cleanup` command automatically. " +"However, on Debian-based systems, you must manually run this command or " +"write your own system script that runs on boot before the ``neutron-dhcp-" +"agent`` service starts." +msgstr "" + +#: ../networking_config-agents.rst:88 +msgid "" +"Networking dhcp-agent can use `dnsmasq `__ driver which supports stateful and stateless DHCPv6 for subnets " +"created with ``--ipv6_address_mode`` set to ``dhcpv6-stateful`` or ``dhcpv6-" +"stateless``." +msgstr "" + +#: ../networking_config-agents.rst:106 +msgid "" +"If no dnsmasq process for subnet's network is launched, Networking will " +"launch a new one on subnet's dhcp port in ``qdhcp-XXX`` namespace. If " +"previous dnsmasq process is already launched, restart dnsmasq with a new " +"configuration." +msgstr "" + +#: ../networking_config-agents.rst:111 +msgid "" +"Networking will update dnsmasq process and restart it when subnet gets " +"updated." +msgstr "" + +#: ../networking_config-agents.rst:116 +msgid "For dhcp-agent to operate in IPv6 mode use at least dnsmasq v2.63." +msgstr "" + +#: ../networking_config-agents.rst:118 +msgid "" +"After a certain, configured timeframe, networks uncouple from DHCP agents " +"when the agents are no longer in use. You can configure the DHCP agent to " +"automatically detach from a network when the agent is out of service, or no " +"longer needed." +msgstr "" + +#: ../networking_config-agents.rst:123 +msgid "" +"This feature applies to all plug-ins that support DHCP scaling. For more " +"information, see the `DHCP agent configuration options `__ listed in the OpenStack Configuration Reference." +msgstr "" + +#: ../networking_config-agents.rst:130 +msgid "DHCP agent setup: OVS plug-in" +msgstr "" + +#: ../networking_config-agents.rst:132 +msgid "" +"These DHCP agent options are required in the :file:`/etc/neutron/dhcp_agent." +"ini` file for the OVS plug-in:" +msgstr "" + +#: ../networking_config-agents.rst:143 +msgid "DHCP agent setup: NSX plug-in" +msgstr "" + +#: ../networking_config-agents.rst:145 +msgid "" +"These DHCP agent options are required in the :file:`/etc/neutron/dhcp_agent." +"ini` file for the NSX plug-in:" +msgstr "" + #: ../networking_config-agents.rst:157 msgid "Configure L3 agent" msgstr "" +#: ../networking_config-agents.rst:159 +msgid "" +"The OpenStack Networking service has a widely used API extension to allow " +"administrators and tenants to create routers to interconnect L2 networks, " +"and floating IPs to make ports on private networks publicly accessible." +msgstr "" + +#: ../networking_config-agents.rst:164 +msgid "" +"Many plug-ins rely on the L3 service agent to implement the L3 " +"functionality. However, the following plug-ins already have built-in L3 " +"capabilities:" +msgstr "" + +#: ../networking_config-agents.rst:168 +msgid "" +"Big Switch/Floodlight plug-in, which supports both the open source " +"`Floodlight `__ controller and " +"the proprietary Big Switch controller." +msgstr "" + +#: ../networking_config-agents.rst:174 +msgid "" +"Only the proprietary BigSwitch controller implements L3 functionality. When " +"using Floodlight as your OpenFlow controller, L3 functionality is not " +"available." +msgstr "" + +#: ../networking_config-agents.rst:178 +msgid "IBM SDN-VE plug-in" +msgstr "" + +#: ../networking_config-agents.rst:180 +msgid "MidoNet plug-in" +msgstr "" + +#: ../networking_config-agents.rst:182 +msgid "NSX plug-in" +msgstr "" + +#: ../networking_config-agents.rst:184 +msgid "PLUMgrid plug-in" +msgstr "" + +#: ../networking_config-agents.rst:188 +msgid "" +"Do not configure or use neutron-l3-agent if you use one of these plug-ins." +msgstr "" + +#: ../networking_config-agents.rst:191 +msgid "**To install the L3 agent for all other plug-ins**" +msgstr "" + +#: ../networking_config-agents.rst:193 +msgid "Install the neutron-l3-agent binary on the network node:" +msgstr "" + +#: ../networking_config-agents.rst:199 +msgid "" +"To uplink the node that runs neutron-l3-agent to the external network, " +"create a bridge named \"br-ex\" and attach the NIC for the external network " +"to this bridge." +msgstr "" + +#: ../networking_config-agents.rst:203 +msgid "" +"For example, with Open vSwitch and NIC eth1 connected to the external " +"network, run:" +msgstr "" + +#: ../networking_config-agents.rst:211 +msgid "" +"Do not manually configure an IP address on the NIC connected to the external " +"network for the node running neutron-l3-agent. Rather, you must have a range " +"of IP addresses from the external network that can be used by OpenStack " +"Networking for routers that uplink to the external network. This range must " +"be large enough to have an IP address for each router in the deployment, as " +"well as each floating IP." +msgstr "" + +#: ../networking_config-agents.rst:218 +msgid "" +"The neutron-l3-agent uses the Linux IP stack and iptables to perform L3 " +"forwarding and NAT. In order to support multiple routers with potentially " +"overlapping IP addresses, neutron-l3-agent defaults to using Linux network " +"namespaces to provide isolated forwarding contexts. As a result, the IP " +"addresses of routers are not visible simply by running the :command:`ip addr " +"list` or :command:`ifconfig` command on the node. Similarly, you cannot " +"directly :command:`ping` fixed IPs." +msgstr "" + +#: ../networking_config-agents.rst:226 +msgid "" +"To do either of these things, you must run the command within a particular " +"network namespace for the router. The namespace has the name ``qrouter-" +"ROUTER_UUID``. These example commands run in the router namespace with UUID " +"47af3868-0fa8-4447-85f6-1304de32153b:" +msgstr "" + +#: ../networking_config-agents.rst:241 +msgid "" +"For iproute version 3.12.0 and above, networking namespaces are configured " +"to be deleted by default. This behavior can be changed for both DHCP and L3 " +"agents. The configuration files are :file:`/etc/neutron/dhcp_agent.ini` and :" +"file:`/etc/neutron/l3_agent.ini` respectively." +msgstr "" + +#: ../networking_config-agents.rst:247 +msgid "" +"For DHCP namespace the configuration key: ``dhcp_delete_namespaces = True``. " +"You can set it to False in case namespaces cannot be deleted cleanly on the " +"host running the DHCP agent." +msgstr "" + +#: ../networking_config-agents.rst:252 +msgid "" +"For L3 namespace, the configuration key: ``router_delete_namespaces = " +"True``. You can set it to False in case namespaces cannot be deleted cleanly " +"on the host running the L3 agent." +msgstr "" + +#: ../networking_config-agents.rst:259 +msgid "" +"If you reboot a node that runs the L3 agent, you must run the :command:" +"`neutron-ovs-cleanup` command before the neutron-l3-agent service starts." +msgstr "" + +#: ../networking_config-agents.rst:263 +msgid "" +"On Red Hat, SUSE and Ubuntu based systems, the neutron-ovs-cleanup service " +"runs the :command:`neutron-ovs-cleanup` command automatically. However, on " +"Debian-based systems, you must manually run this command or write your own " +"system script that runs on boot before the neutron-l3-agent service starts." +msgstr "" + +#: ../networking_config-agents.rst:270 +msgid "Configure metering agent" +msgstr "" + +#: ../networking_config-agents.rst:272 +msgid "The Neutron Metering agent resides beside neutron-l3-agent." +msgstr "" + +#: ../networking_config-agents.rst:274 +msgid "**To install the metering agent and configure the node**" +msgstr "" + +#: ../networking_config-agents.rst:276 +msgid "Install the agent by running:" +msgstr "" + +#: ../networking_config-agents.rst:282 +msgid "" +"If you use one of the following plug-ins, you need to configure the metering " +"agent with these lines as well:" +msgstr "" + +#: ../networking_config-agents.rst:285 +msgid "An OVS-based plug-in such as OVS, NSX, NEC, BigSwitch/Floodlight:" +msgstr "" + +#: ../networking_config-agents.rst:291 +msgid "A plug-in that uses LinuxBridge:" +msgstr "" + +#: ../networking_config-agents.rst:298 +msgid "To use the reference implementation, you must set:" +msgstr "" + +#: ../networking_config-agents.rst:305 +msgid "" +"Set the ``service_plugins`` option in the :file:`/etc/neutron/neutron.conf` " +"file on the host that runs neutron-server:" +msgstr "" + +#: ../networking_config-agents.rst:312 +msgid "" +"If this option is already defined, add ``metering`` to the list, using a " +"comma as separator. For example:" +msgstr "" + #: ../networking_config-agents.rst:320 msgid "Configure Load-Balancer-as-a-Service (LBaaS)" msgstr "" @@ -4422,530 +14120,119 @@ msgid "" "LBaaS for OVS-based plug-ins, including BigSwitch, Floodlight, NEC, and NSX." msgstr "" -#: ../compute-configuring-migrations.rst:181 +#: ../networking_config-agents.rst:327 +msgid "**To configure LBaas with Open vSwitch or Linux Bridge plug-in**" +msgstr "" + +#: ../networking_config-agents.rst:329 +msgid "Install the agent:" +msgstr "" + +#: ../networking_config-agents.rst:335 msgid "" -"Configure NFS on ``HostB`` and ``HostC`` by adding the following line to " -"the :file:`/etc/fstab` file" +"Enable the HAProxy plug-in by using the ``service_provider`` option in the :" +"file:`/etc/neutron/neutron.conf` file:" msgstr "" -#: ../networking_config-plugins.rst:96 -msgid "Configure NSX-mh plug-in" -msgstr "" - -#: ../blockstorage_glusterfs_backend.rst:122 +#: ../networking_config-agents.rst:346 msgid "" -"Configure OpenStack Block Storage to use the :file:`/etc/cinder/glusterfs` " -"file created earlier. To do so, open the :file:`/etc/cinder/cinder.conf` " -"configuration file and set the ``glusterfs_shares_config`` configuration key " -"to :file:`/etc/cinder/glusterfs`." +"The ``service_provider`` option is already defined in the :file:`/usr/share/" +"neutron/neutron-dist.conf` file on Red Hat based systems. Do not define it " +"in :file:`neutron.conf` otherwise the Networking services will fail to " +"restart." msgstr "" -#: ../blockstorage_glusterfs_backend.rst:147 +#: ../networking_config-agents.rst:351 msgid "" -"Configure OpenStack Block Storage to use the correct volume driver, namely " -"``cinder.volume.drivers.glusterfs``. To do so, open the :file:`/etc/cinder/" -"cinder.conf` configuration file and set the ``volume_driver`` configuration " -"key to ``cinder.volume.drivers.glusterfs``." +"Enable the load-balancing plug-in by using the ``service_plugins`` option in " +"the :file:`/etc/neutron/neutron.conf` file:" msgstr "" -#: ../networking_config-plugins.rst:223 -msgid "Configure PLUMgrid plug-in" -msgstr "" - -#: ../networking_introduction.rst:66 -msgid "Configure SSL support for networking API" -msgstr "" - -#: ../keystone_integrate_with_ldap.rst:72 +#: ../networking_config-agents.rst:358 msgid "" -"Configure ``dumb_member`` to true if your environment requires the " -"``use_dumb_member`` variable." +"If this option is already defined, add ``lbaas`` to the list, using a comma " +"as separator. For example:" msgstr "" -#: ../blockstorage_glusterfs_backend.rst:3 -msgid "Configure a GlusterFS back end" -msgstr "" - -#: ../database.rst:290 -msgid "Configure a cluster" -msgstr "" - -#: ../compute-configuring-migrations.rst:358 +#: ../networking_config-agents.rst:365 msgid "" -"Configure all compute nodes to use the default storage repository (``sr``) " -"for pool operations. Add this line to your :file:`nova.conf` configuration " -"files on all compute nodes:" +"Enable the HAProxy load balancer in the :file:`/etc/neutron/lbaas_agent.ini` " +"file:" msgstr "" -#: ../blockstorage_nfs_backend.rst:3 -msgid "Configure an NFS storage back end" -msgstr "" - -#: ../blockstorage-driver-filter-weighing.rst:6 -msgid "Configure and use driver filter and weighing for scheduler" -msgstr "" - -#: ../blockstorage_volume_number_weigher.rst:8 -msgid "Configure and use volume number weigher" -msgstr "" - -#: ../networking_config-agents.rst:21 -msgid "Configure data-forwarding nodes" -msgstr "" - -#: ../blockstorage_glusterfs_backend.rst:65 +#: ../networking_config-agents.rst:373 msgid "" -"Configure each Gluster volume to accept ``libgfapi`` connections. To do " -"this, set each Gluster volume to allow insecure ports::" +"Select the required driver in the :file:`/etc/neutron/lbaas_agent.ini` file:" msgstr "" -#: ../networking_config-identity.rst:218 -msgid "Configure metadata" +#: ../networking_config-agents.rst:376 +msgid "Enable the Open vSwitch LBaaS driver:" msgstr "" -#: ../networking_config-agents.rst:270 -msgid "Configure metering agent" +#: ../networking_config-agents.rst:382 +msgid "Or, enable the Linux Bridge LBaaS driver:" msgstr "" -#: ../compute-configuring-migrations.rst:5 -msgid "Configure migrations" +# #-#-#-#-# networking_config-agents.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +# #-#-#-#-# networking_introduction.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +#: ../networking_config-agents.rst:388 ../networking_introduction.rst:196 +msgid "Create the required tables in the database:" msgstr "" -# #-#-#-#-# blockstorage_multi_backend.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -# #-#-#-#-# blockstorage_volume_number_weigher.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -#: ../blockstorage_multi_backend.rst:8 -#: ../blockstorage_volume_number_weigher.rst:25 -msgid "Configure multiple-storage back ends" -msgstr "" - -#: ../networking_config-agents.rst:3 -msgid "Configure neutron agents" -msgstr "" - -#: ../blockstorage_over_subscription.rst:15 -msgid "Configure oversubscription settings" -msgstr "" - -#: ../compute-networking-nova.rst:573 -msgid "Configure public (floating) IP addresses" -msgstr "" - -#: ../compute-remote-console-access.rst:3 -msgid "Configure remote console access" -msgstr "" - -#: ../networking_config-identity.rst:192 -msgid "Configure security groups" -msgstr "" - -#: ../objectstorage_tenant_specific_image_storage.rst:17 +#: ../networking_config-agents.rst:394 msgid "" -"Configure swift as your ``default_store`` in the :file:`glance-api.conf` " -"file." +"Apply the settings by restarting the neutron-server and neutron-lbaas-agent " +"services." msgstr "" -#: ../objectstorage_tenant_specific_image_storage.rst:3 -msgid "Configure tenant-specific image locations with Object Storage" +#: ../networking_config-agents.rst:397 +msgid "Enable load balancing in the Project section of the dashboard." msgstr "" -#: ../keystone_secure_identity_to_ldap_backend.rst:21 +#: ../networking_config-agents.rst:399 msgid "" -"Configure the Identity service to use your certificate authorities file. To " -"do so, set the ``tls_cacertfile`` configuration key in the ``ldap`` section " -"to the certificate authorities file's path." +"Change the ``enable_lb`` option to ``True`` in the :file:`local_settings` " +"file (on Fedora, RHEL, and CentOS: :file:`/etc/openstack-dashboard/" +"local_settings`, on Ubuntu and Debian: :file:`/etc/openstack-dashboard/" +"local_settings.py`, and on openSUSE and SLES: :file:`/srv/www/openstack-" +"dashboard/openstack_dashboard/local/local_settings .py`):" msgstr "" -#: ../keystone_configure_with_SSL.rst:3 -msgid "Configure the Identity service with SSL" -msgstr "" - -#: ../blockstorage_image_volume_cache.rst:48 -msgid "Configure the Image-Volume cache" -msgstr "" - -#: ../blockstorage_image_volume_cache.rst:22 -msgid "Configure the Internal Tenant" -msgstr "" - -#: ../keystone_caching_layer.rst:121 -msgid "Configure the Memcached back end example" -msgstr "" - -#: ../compute-configuring-migrations.rst:157 +#: ../networking_config-agents.rst:414 msgid "" -"Configure the NFS server at ``HostA`` by adding the following line to the :" -"file:`/etc/exports` file:" +"Apply the settings by restarting the web server. You can now view the Load " +"Balancer management options in the Project view in the dashboard." msgstr "" -#: ../blockstorage-manage-volumes.rst:25 +#: ../networking_config-agents.rst:418 +msgid "Configure Hyper-V L2 agent" +msgstr "" + +#: ../networking_config-agents.rst:420 msgid "" -"Configure the OpenStack Compute and the OpenStack Block Storage services " -"through the :file:`cinder.conf` file." +"Before you install the OpenStack Networking Hyper-V L2 agent on a Hyper-V " +"compute node, ensure the compute node has been configured correctly using " +"these `instructions `__." msgstr "" -#: ../blockstorage_volume_backed_image.rst:17 -msgid "Configure the Volume-backed image" -msgstr "" - -#: ../blockstorage_nfs_backend.rst:101 +#: ../networking_config-agents.rst:426 msgid "" -"Configure the ``cinder`` volume service to use the correct volume driver, " -"namely cinder.volume.drivers.nfs.NfsDriver. To do so, open the :file:`/etc/" -"cinder/cinder.conf` configuration file and set the volume_driver " -"configuration key to ``cinder.volume.drivers.nfs.NfsDriver``." +"**To install the OpenStack Networking Hyper-V agent and configure the node**" msgstr "" -#: ../blockstorage_nfs_backend.rst:59 -msgid "" -"Configure the cinder volume service to use the :file:`/etc/cinder/nfsshares` " -"file created earlier. To do so, open the :file:`/etc/cinder/cinder.conf` " -"configuration file and set the ``nfs_shares_config`` configuration key to :" -"file:`/etc/cinder/nfsshares`." +#: ../networking_config-agents.rst:428 +msgid "Download the OpenStack Networking code from the repository:" msgstr "" -#: ../compute-configuring-migrations.rst:252 -msgid "" -"Configure the downtime required for the migration by adjusting these " -"parameters in the :file:`nova.conf` file:" -msgstr "" - -#: ../blockstorage_ratelimit_volume_copy_bandwidth.rst:17 -msgid "Configure volume copy bandwidth limit" -msgstr "" - -#: ../compute-configuring-migrations.rst:129 -msgid "" -"Configure your DNS or ``/etc/hosts`` and ensure it is consistent across all " -"hosts. Make sure that the three hosts can perform name resolution with each " -"other. As a test, use the :command:`ping` command to ping each host from one " -"another:" -msgstr "" - -#: ../compute-configuring-migrations.rst:244 -msgid "" -"Configure your firewall to allow libvirt to communicate between nodes. By " -"default, libvirt listens on TCP port 16509, and an ephemeral TCP range from " -"49152 to 49261 is used for the KVM communications. Based on the secure " -"remote access TCP configuration you chose, be careful which ports you open, " -"and always understand who has access. For information about ports that are " -"used with libvirt, see the `libvirt documentation `_." -msgstr "" - -#: ../compute-configuring-migrations.rst:301 -msgid "" -"Configuring KVM for block migration is exactly the same as the above " -"configuration in :ref:`configuring-migrations-kvm-shared-storage` the " -"section called shared storage, except that ``NOVA-INST-DIR/instances`` is " -"local to each host rather than shared. No NFS client or server configuration " -"is required." -msgstr "" - -#: ../compute_arch.rst:360 -msgid "Configuring VLANs for projects" -msgstr "" - -#: ../compute_arch.rst:362 -msgid "Configuring networks for compute nodes" -msgstr "" - -#: ../blockstorage_glusterfs_removal.rst:10 -msgid "" -"Configuring the ``cinder`` volume service to use GlusterFS involves creating " -"a shares file (for example, :file:`/etc/cinder/glusterfs`). This shares file " -"lists each GlusterFS volume (with its corresponding storage server) that the " -"``cinder`` volume service can use for back end storage." -msgstr "" - -#: ../compute-manage-the-cloud.rst:43 -msgid "Confirm the installation was successful:" -msgstr "" - -#: ../networking_adv-features.rst:227 -msgid "" -"Connects a router to an external network, which enables that router to act " -"as a NAT gateway for external connectivity." -msgstr "" - -#: ../blockstorage_multi_backend.rst:174 -msgid "" -"Considering the :file:`cinder.conf` described previously, the scheduler " -"creates this volume on ``lvmdriver-1`` or ``lvmdriver-2``." -msgstr "" - -#: ../blockstorage-consistency-groups.rst:8 -msgid "" -"Consistency group support is available in OpenStack Block Storage. The " -"support is added for creating snapshots of consistency groups. This feature " -"leverages the storage level consistency technology. It allows snapshots of " -"multiple volumes in the same consistency group to be taken at the same point-" -"in-time to ensure data consistency. The consistency group operations can be " -"performed using the Block Storage command line." -msgstr "" - -#: ../blockstorage-consistency-groups.rst:6 -msgid "Consistency groups" -msgstr "" - -#: ../compute-default-ports.rst:7 -msgid "" -"Console connections for virtual machines, whether direct or through a proxy, " -"are received on ports ``5900`` to ``5999``. The firewall on each Compute " -"service node must allow network traffic on these ports." -msgstr "" - -#: ../telemetry-system-architecture.rst:40 -msgid "Consumes AMQP messages from other OpenStack services." -msgstr "" - -#: ../telemetry-system-architecture.rst:43 -msgid "" -"Consumes AMQP notifications from the agents, then dispatches these data to " -"the appropriate data store." -msgstr "" - -#: ../ts-eql-volume-size.rst:110 -msgid "Container Format" -msgstr "" - -#: ../telemetry-data-retrieval.rst:320 -msgid "" -"Contains the filter expression for the query in the form of: ``{complex_op: " -"[{simple_op: {field_name: value}}]}``." -msgstr "" - -#: ../telemetry-data-retrieval.rst:324 -msgid "" -"Contains the list of ``orderby`` expressions in the form of: ``[{field_name: " -"direction}, {field_name: direction}]``." -msgstr "" - -#: ../index.rst:15 -msgid "Contents" -msgstr "" - -#: ../compute-images-instances.rst:427 -msgid "Control where instances run" -msgstr "" - -#: ../keystone_certificates_for_pki.rst:122 -msgid "Convert certificate and private key to PEM if needed" -msgstr "" - -#: ../dashboard_sessions.rst:187 -msgid "Cookies" +#: ../networking_config-agents.rst:435 +msgid "Install the OpenStack Networking Hyper-V Agent:" msgstr "" #: ../networking_config-agents.rst:442 msgid "Copy the :file:`policy.json` file:" msgstr "" -#: ../keystone_certificates_for_pki.rst:183 -msgid "Copy the above to your certificate directory. For example:" -msgstr "" - -#: ../networking_use.rst:24 -msgid "Core Networking API features" -msgstr "" - -#: ../keystone_certificates_for_pki.rst:178 -msgid "Corresponding (non-encrypted) private key in PEM format" -msgstr "" - -#: ../objectstorage-monitoring.rst:37 -msgid "Count of \"async\\_pendings\" (deferred container updates) on disk." -msgstr "" - -#: ../telemetry-data-retrieval.rst:146 -msgid "" -"Count of distinct values in each period identified by a key specified as the " -"parameter of this aggregate function. The supported parameter values are:" -msgstr "" - -#: ../objectstorage-monitoring.rst:34 -msgid "Count of each type of quarantined file: Account, container, or object." -msgstr "" - -#: ../dashboard_sessions.rst:107 -msgid "" -"Create a MySQL user for the newly created dash database that has full " -"control of the database. Replace DASH\\_DBPASS with a password for the new " -"user::" -msgstr "" - -#: ../blockstorage_backup_disks.rst:163 -msgid "Create a backup of the volume::" -msgstr "" - -#: ../keystone_certificates_for_pki.rst:132 -msgid "" -"Create a certificate request configuration file. For example, create the :" -"file:`cert_req.conf` file, as follows:" -msgstr "" - -#: ../blockstorage-consistency-groups.rst:97 -msgid "Create a consistency group from a source consistency group." -msgstr "" - -#: ../blockstorage-consistency-groups.rst:94 -msgid "" -"Create a consistency group from the snapshot of another consistency group." -msgstr "" - -#: ../blockstorage-consistency-groups.rst:61 -msgid "Create a consistency group, given volume types." -msgstr "" - -#: ../database.rst:28 -msgid "Create a datastore" -msgstr "" - -#: ../identity_concepts.rst:108 -msgid "Create a domain named ``emea``:" -msgstr "" - -#: ../networking_introduction.rst:232 -msgid "Create a firewall policy:" -msgstr "" - -#: ../networking_introduction.rst:222 -msgid "Create a firewall rule:" -msgstr "" - -#: ../networking_introduction.rst:261 -msgid "Create a firewall:" -msgstr "" - -#: ../identity_concepts.rst:341 -msgid "Create a group" -msgstr "" - -#: ../compute-configuring-migrations.rst:366 -msgid "" -"Create a host aggregate. This command creates the aggregate, and then " -"displays a table that contains the ID of the new aggregate" -msgstr "" - -#: ../compute-networking-nova.rst:689 -msgid "Create a list of available floating IP addresses" -msgstr "" - -#: ../ts-eql-volume-size.rst:82 -msgid "Create a new image from this volume:" -msgstr "" - -#: ../compute-manage-volumes.rst:36 -msgid "Create a new volume type." -msgstr "" - -#: ../ts-eql-volume-size.rst:118 -msgid "" -"Create a new volume using the previous image (``image_id 3020a21d-ba37-4495 " -"-8899-07fc201161b9`` in this example) as the source. Set the target volume " -"size to 1 GB; this is the size reported by the ``cinder`` tool when you " -"uploaded the volume to the Image service:" -msgstr "" - -#: ../ts-eql-volume-size.rst:25 -msgid "" -"Create a new volume. Note the ID and size of the volume. In the following " -"example, the ID and size are ``74cf9c04-4543-47ae-a937-a9b7c6c921e7`` and " -"``1``, respectively:" -msgstr "" - -#: ../networking_introduction.rst:286 -msgid "Create a port with a specified allowed address pairs:" -msgstr "" - -#: ../identity_concepts.rst:102 -msgid "Create a project named ``acme``:" -msgstr "" - -#: ../identity_concepts.rst:114 -msgid "Create a role named ``compute-user``:" -msgstr "" - -#: ../blockstorage-consistency-groups.rst:82 -msgid "Create a snapshot for a consistency group." -msgstr "" - -#: ../blockstorage_backup_disks.rst:46 -msgid "Create a snapshot of a used volume" -msgstr "" - -#: ../blockstorage_glusterfs_backend.rst:87 -msgid "Create a text file named :file:`glusterfs` in :file:`/etc/cinder/`." -msgstr "" - -#: ../blockstorage_nfs_backend.rst:32 -msgid "Create a text file named :file:`nfsshares` in :file:`/etc/cinder/`." -msgstr "" - -#: ../identity_concepts.rst:96 -msgid "Create a user named ``alice``:" -msgstr "" - -#: ../blockstorage-consistency-groups.rst:79 -msgid "" -"Create a volume and add it to a consistency group, given volume type and " -"consistency group id." -msgstr "" - -#: ../compute-node-down.rst:167 -msgid "" -"Create an active iSCSI session from the SAN to the cloud controller (used " -"for the ``cinder-volumes`` LVM's VG)." -msgstr "" - -#: ../compute-node-down.rst:170 -msgid "" -"Create an active iSCSI session from the cloud controller to the compute node " -"(managed by cinder-volume)." -msgstr "" - -#: ../blockstorage_volume_number_weigher.rst:57 -msgid "" -"Create an extra specification that links the volume type to a back-end name::" -msgstr "" - -#: ../compute-node-down.rst:173 -msgid "" -"Create an iSCSI session for every volume (so 14 EBS volumes requires 14 " -"iSCSI sessions)." -msgstr "" - -#: ../database.rst:43 -msgid "" -"Create an image for the type of database you want to use, for example, " -"MySQL, MongoDB, Cassandra." -msgstr "" - -#: ../blockstorage_multi_backend.rst:140 -msgid "Create another volume type::" -msgstr "" - -#: ../ts_cinder_config.rst:25 -msgid "Create commands are listed in the ``cinder-api`` log." -msgstr "" - -#: ../keystone_integrate_identity_backend_ldap.rst:105 -msgid "Create domains using OpenStack dashboard, or the OpenStackClient CLI." -msgstr "" - -#: ../networking_adv-features.rst:561 -msgid "Create external network and map it to a specific NSX gateway service:" -msgstr "" - -#: ../compute-node-down.rst:176 -msgid "" -"Create iptables or ebtables rules from the cloud controller to the compute " -"node. This allows access from the cloud controller to the running instance." -msgstr "" - -#: ../compute-networking-nova.rst:707 -msgid "Create specific floating IPs for either a single address or a subnet:" -msgstr "" - #: ../networking_config-agents.rst:448 msgid "" "Create the :file:`C:\\etc\\neutron-hyperv-agent.conf` file and add the " @@ -4954,24 +14241,145 @@ msgid "" "html>`__. Here is a sample config file:" msgstr "" -#: ../networking_config-identity.rst:36 -msgid "Create the Networking service endpoint entry" +#: ../networking_config-agents.rst:478 +msgid "Start the OpenStack Networking Hyper-V agent:" +msgstr "" + +#: ../networking_config-agents.rst:486 +msgid "Basic operations on agents" +msgstr "" + +#: ../networking_config-agents.rst:488 +msgid "" +"This table shows examples of Networking commands that enable you to complete " +"basic operations on agents:" +msgstr "" + +#: ../networking_config-agents.rst:494 +msgid "List all available agents." +msgstr "" + +#: ../networking_config-agents.rst:496 +msgid "``$ neutron agent-list``" +msgstr "" + +#: ../networking_config-agents.rst:498 +msgid "Show information of a given agent." +msgstr "" + +#: ../networking_config-agents.rst:501 +msgid "``$ neutron agent-show AGENT_ID``" +msgstr "" + +#: ../networking_config-agents.rst:503 +msgid "" +"Update the admin status and description for a specified agent. The command " +"can be used to enable and disable agents by using ``--admin-state-up`` " +"parameter set to ``False`` or ``True``." +msgstr "" + +#: ../networking_config-agents.rst:509 +msgid "``$ neutron agent-update --admin`` ``-state-up False AGENT_ID``" +msgstr "" + +#: ../networking_config-agents.rst:512 +msgid "Delete a given agent. Consider disabling the agent before deletion." +msgstr "" + +#: ../networking_config-agents.rst:515 +msgid "``$ neutron agent-delete AGENT_ID``" +msgstr "" + +#: ../networking_config-agents.rst:518 +msgid "**Basic operations on Networking agents**" +msgstr "" + +#: ../networking_config-agents.rst:520 +msgid "" +"See the `OpenStack Command-Line Interface Reference `__ for more information on Networking " +"commands." +msgstr "" + +#: ../networking_config-identity.rst:0 +msgid "**nova.conf API and credential settings**" +msgstr "" + +#: ../networking_config-identity.rst:3 +msgid "Configure Identity service for Networking" +msgstr "" + +#: ../networking_config-identity.rst:5 +msgid "**To configure the Identity service for use with Networking**" +msgstr "" + +#: ../networking_config-identity.rst:7 +msgid "Create the ``get_id()`` function" +msgstr "" + +#: ../networking_config-identity.rst:9 +msgid "" +"The ``get_id()`` function stores the ID of created objects, and removes the " +"need to copy and paste object IDs in later steps:" +msgstr "" + +#: ../networking_config-identity.rst:12 +msgid "Add the following function to your :file:`.bashrc` file:" +msgstr "" + +#: ../networking_config-identity.rst:20 +msgid "Source the :file:`.bashrc` file:" msgstr "" #: ../networking_config-identity.rst:26 msgid "Create the Networking service entry" msgstr "" +#: ../networking_config-identity.rst:28 +msgid "" +"Networking must be available in the Compute service catalog. Create the " +"service:" +msgstr "" + +#: ../networking_config-identity.rst:36 +msgid "Create the Networking service endpoint entry" +msgstr "" + +#: ../networking_config-identity.rst:38 +msgid "" +"The way that you create a Networking endpoint entry depends on whether you " +"are using the SQL or the template catalog driver:" +msgstr "" + +#: ../networking_config-identity.rst:41 +msgid "" +"If you use the *SQL driver*, run the following command with the specified " +"region (``$REGION``), IP address of the Networking server (``$IP``), and " +"service ID (``$NEUTRON_SERVICE_ID``, obtained in the previous step)." +msgstr "" + +#: ../networking_config-identity.rst:63 +msgid "" +"If you are using the *template driver*, specify the following parameters in " +"your Compute catalog template file (:file:`default_catalog.templates`), " +"along with the region (``$REGION``) and IP address of the Networking server " +"(``$IP``)." +msgstr "" + #: ../networking_config-identity.rst:84 msgid "Create the Networking service user" msgstr "" -#: ../networking_config-identity.rst:91 -msgid "Create the ``admin`` role:" +#: ../networking_config-identity.rst:86 +msgid "" +"You must provide admin user credentials that Compute and some internal " +"Networking components can use to access the Networking API. Create a special " +"``service`` tenant and a ``neutron`` user within this tenant, and assign an " +"``admin`` role to this role." msgstr "" -#: ../networking_config-identity.rst:7 -msgid "Create the ``get_id()`` function" +#: ../networking_config-identity.rst:91 +msgid "Create the ``admin`` role:" msgstr "" #: ../networking_config-identity.rst:97 @@ -4982,14 +14390,818 @@ msgstr "" msgid "Create the ``service`` tenant:" msgstr "" -#: ../database.rst:97 -msgid "" -"Create the datastore that will house the new image. To do this, use the :" -"command:`trove-manage` :command:`datastore_update` command." +#: ../networking_config-identity.rst:111 +msgid "Establish the relationship among the tenant, user, and role:" msgstr "" -#: ../orchestration-stack-domain-users.rst:60 -msgid "Create the domain:" +#: ../networking_config-identity.rst:118 +msgid "" +"For information about how to create service entries and users, see the " +"OpenStack Installation Guide for your distribution (`docs.openstack.org " +"`__)." +msgstr "" + +#: ../networking_config-identity.rst:125 +msgid "" +"If you use Networking, do not run the Compute nova-network service (like you " +"do in traditional Compute deployments). Instead, Compute delegates most " +"network-related decisions to Networking. Compute proxies tenant-facing API " +"calls to manage security groups and floating IPs to Networking APIs. " +"However, operator-facing tools such as nova-manage, are not proxied and " +"should not be used." +msgstr "" + +#: ../networking_config-identity.rst:134 +msgid "" +"When you configure networking, you must use this guide. Do not rely on " +"Compute networking documentation or past experience with Compute. If a :" +"command:`nova` command or configuration option related to networking is not " +"mentioned in this guide, the command is probably not supported for use with " +"Networking. In particular, you cannot use CLI tools like ``nova-manage`` and " +"``nova`` to manage networks or IP addressing, including both fixed and " +"floating IPs, with Networking." +msgstr "" + +#: ../networking_config-identity.rst:144 +msgid "" +"Uninstall nova-network and reboot any physical nodes that have been running " +"nova-network before using them to run Networking. Inadvertently running the " +"nova-network process while using Networking can cause problems, as can stale " +"iptables rules pushed down by previously running nova-network." +msgstr "" + +#: ../networking_config-identity.rst:150 +msgid "" +"To ensure that Compute works properly with Networking (rather than the " +"legacy nova-network mechanism), you must adjust settings in the :file:`nova." +"conf` configuration file." +msgstr "" + +#: ../networking_config-identity.rst:155 +msgid "Networking API and credential configuration" +msgstr "" + +#: ../networking_config-identity.rst:157 +msgid "" +"Each time you provision or de-provision a VM in Compute, nova-\\* services " +"communicate with Networking using the standard API. For this to happen, you " +"must configure the following items in the :file:`nova.conf` file (used by " +"each nova-compute and nova-api instance)." +msgstr "" + +#: ../networking_config-identity.rst:168 +msgid "``[DEFAULT] network_api_class``" +msgstr "" + +#: ../networking_config-identity.rst:169 +msgid "" +"Modify from the default to ``nova.network.neutronv2.api.API``, to indicate " +"that Networking should be used rather than the traditional nova-network " +"networking model." +msgstr "" + +#: ../networking_config-identity.rst:172 +msgid "``[neutron] url``" +msgstr "" + +#: ../networking_config-identity.rst:173 +msgid "" +"Update to the hostname/IP and port of the neutron-server instance for this " +"deployment." +msgstr "" + +#: ../networking_config-identity.rst:175 +msgid "``[neutron] auth_strategy``" +msgstr "" + +#: ../networking_config-identity.rst:176 +msgid "Keep the default ``keystone`` value for all production deployments." +msgstr "" + +#: ../networking_config-identity.rst:177 +msgid "``[neutron] admin_tenant_name``" +msgstr "" + +#: ../networking_config-identity.rst:178 +msgid "" +"Update to the name of the service tenant created in the above section on " +"Identity configuration." +msgstr "" + +#: ../networking_config-identity.rst:180 +msgid "``[neutron] admin_username``" +msgstr "" + +#: ../networking_config-identity.rst:181 +msgid "" +"Update to the name of the user created in the above section on Identity " +"configuration." +msgstr "" + +#: ../networking_config-identity.rst:183 +msgid "``[neutron] admin_password``" +msgstr "" + +#: ../networking_config-identity.rst:184 +msgid "" +"Update to the password of the user created in the above section on Identity " +"configuration." +msgstr "" + +#: ../networking_config-identity.rst:186 +msgid "``[neutron] admin_auth_url``" +msgstr "" + +#: ../networking_config-identity.rst:187 +msgid "" +"Update to the Identity server IP and port. This is the Identity (keystone) " +"admin API server IP and port value, and not the Identity service API IP and " +"port." +msgstr "" + +#: ../networking_config-identity.rst:192 +msgid "Configure security groups" +msgstr "" + +#: ../networking_config-identity.rst:194 +msgid "" +"The Networking service provides security group functionality using a " +"mechanism that is more flexible and powerful than the security group " +"capabilities built into Compute. Therefore, if you use Networking, you " +"should always disable built-in security groups and proxy all security group " +"calls to the Networking API. If you do not, security policies will conflict " +"by being simultaneously applied by both services." +msgstr "" + +#: ../networking_config-identity.rst:201 +msgid "" +"To proxy security groups to Networking, use the following configuration " +"values in :file:`nova.conf`:" +msgstr "" + +#: ../networking_config-identity.rst:204 +msgid "**nova.conf security group settings**" +msgstr "" + +# #-#-#-#-# networking_config-identity.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +# #-#-#-#-# networking_multi-dhcp-agents.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +#: ../networking_config-identity.rst:207 ../networking_config-identity.rst:232 +#: ../networking_multi-dhcp-agents.rst:54 +msgid "Configuration" +msgstr "" + +#: ../networking_config-identity.rst:207 ../networking_config-identity.rst:232 +msgid "Item" +msgstr "" + +#: ../networking_config-identity.rst:209 +msgid "" +"Update to ``nova.virt.firewall.NoopFirewallDriver``, so that nova-compute " +"does not perform iptables-based filtering itself." +msgstr "" + +#: ../networking_config-identity.rst:209 +msgid "``firewall_driver``" +msgstr "" + +#: ../networking_config-identity.rst:213 +msgid "" +"Update to ``neutron``, so that all security group requests are proxied to " +"the Network Service." +msgstr "" + +#: ../networking_config-identity.rst:213 +msgid "``security_group_api``" +msgstr "" + +#: ../networking_config-identity.rst:218 +msgid "Configure metadata" +msgstr "" + +#: ../networking_config-identity.rst:220 +msgid "" +"The Compute service allows VMs to query metadata associated with a VM by " +"making a web request to a special 169.254.169.254 address. Networking " +"supports proxying those requests to nova-api, even when the requests are " +"made from isolated networks, or from multiple networks that use overlapping " +"IP addresses." +msgstr "" + +#: ../networking_config-identity.rst:226 +msgid "" +"To enable proxying the requests, you must update the following fields in " +"``[neutron]`` section in :file:`nova.conf`." +msgstr "" + +#: ../networking_config-identity.rst:229 +msgid "**nova.conf metadata settings**" +msgstr "" + +#: ../networking_config-identity.rst:234 +msgid "" +"Update to ``true``, otherwise nova-api will not properly respond to requests " +"from the neutron-metadata-agent." +msgstr "" + +#: ../networking_config-identity.rst:234 +msgid "``service_metadata_proxy``" +msgstr "" + +#: ../networking_config-identity.rst:238 +msgid "" +"Update to a string \"password\" value. You must also configure the same " +"value in the ``metadata_agent.ini`` file, to authenticate requests made for " +"metadata." +msgstr "" + +#: ../networking_config-identity.rst:238 +msgid "``metadata_proxy_shared_secret``" +msgstr "" + +#: ../networking_config-identity.rst:243 +msgid "" +"The default value of an empty string in both files will allow metadata to " +"function, but will not be secure if any non-trusted entities have access to " +"the metadata APIs exposed by nova-api." +msgstr "" + +#: ../networking_config-identity.rst:252 +msgid "" +"As a precaution, even when using ``metadata_proxy_shared_secret``, we " +"recommend that you do not expose metadata using the same nova-api instances " +"that are used for tenants. Instead, you should run a dedicated set of nova-" +"api instances for metadata that are available only on your management " +"network. Whether a given nova-api instance exposes metadata APIs is " +"determined by the value of ``enabled_apis`` in its :file:`nova.conf`." +msgstr "" + +#: ../networking_config-identity.rst:261 +msgid "Example nova.conf (for nova-compute and nova-api)" +msgstr "" + +#: ../networking_config-identity.rst:263 +msgid "" +"Example values for the above settings, assuming a cloud controller node " +"running Compute and Networking with an IP address of 192.168.1.2:" +msgstr "" + +#: ../networking_config-plugins.rst:3 +msgid "Plug-in configurations" +msgstr "" + +#: ../networking_config-plugins.rst:5 +msgid "" +"For configurations options, see `Networking configuration options `__ in Configuration Reference. These sections explain how to " +"configure specific plug-ins." +msgstr "" + +#: ../networking_config-plugins.rst:12 +msgid "Configure Big Switch (Floodlight REST Proxy) plug-in" +msgstr "" + +#: ../networking_config-plugins.rst:14 +msgid "Edit the :file:`/etc/neutron/neutron.conf` file and add this line:" +msgstr "" + +#: ../networking_config-plugins.rst:20 +msgid "" +"In the :file:`/etc/neutron/neutron.conf` file, set the ``service_plugins`` " +"option:" +msgstr "" + +#: ../networking_config-plugins.rst:27 +msgid "" +"Edit the :file:`/etc/neutron/plugins/bigswitch/restproxy.ini` file for the " +"plug-in and specify a comma-separated list of controller\\_ip:port pairs:" +msgstr "" + +#: ../networking_config-plugins.rst:34 +msgid "" +"For database configuration, see `Install Networking Services `__ in the Installation Guide in the `OpenStack Documentation " +"index `__. (The link defaults to the Ubuntu " +"version.)" +msgstr "" + +#: ../networking_config-plugins.rst:41 +msgid "Restart neutron-server to apply the settings:" +msgstr "" + +#: ../networking_config-plugins.rst:48 +msgid "Configure Brocade plug-in" +msgstr "" + +#: ../networking_config-plugins.rst:50 +msgid "" +"Install the Brocade-modified Python netconf client (ncclient) library, which " +"is available at https://github.com/brocade/ncclient:" +msgstr "" + +#: ../networking_config-plugins.rst:57 +msgid "As root, run this command:" +msgstr "" + +#: ../networking_config-plugins.rst:63 +msgid "" +"Edit the :file:`/etc/neutron/neutron.conf` file and set the following option:" +msgstr "" + +#: ../networking_config-plugins.rst:70 +msgid "" +"Edit the :file:`/etc/neutron/plugins/brocade/brocade.ini` file for the " +"Brocade plug-in and specify the admin user name, password, and IP address of " +"the Brocade switch:" +msgstr "" + +#: ../networking_config-plugins.rst:82 +msgid "" +"For database configuration, see `Install Networking Services `__ in any of the Installation Guides in the `OpenStack " +"Documentation index `__. (The link defaults to " +"the Ubuntu version.)" +msgstr "" + +#: ../networking_config-plugins.rst:89 ../networking_config-plugins.rst:248 +msgid "Restart the neutron-server service to apply the settings:" +msgstr "" + +#: ../networking_config-plugins.rst:96 +msgid "Configure NSX-mh plug-in" +msgstr "" + +#: ../networking_config-plugins.rst:98 +msgid "" +"The instructions in this section refer to the VMware NSX-mh platform, " +"formerly known as Nicira NVP." +msgstr "" + +#: ../networking_config-plugins.rst:101 +msgid "Install the NSX plug-in:" +msgstr "" + +#: ../networking_config-plugins.rst:107 ../networking_config-plugins.rst:225 +msgid "Edit the :file:`/etc/neutron/neutron.conf` file and set this line:" +msgstr "" + +#: ../networking_config-plugins.rst:113 +msgid "Example :file:`neutron.conf`: file for NSX-mh integration:" +msgstr "" + +#: ../networking_config-plugins.rst:121 +msgid "" +"To configure the NSX-mh controller cluster for OpenStack Networking, locate " +"the ``[default]`` section in the :file:`/etc/neutron/plugins/vmware/nsx.ini` " +"file and add the following entries:" +msgstr "" + +#: ../networking_config-plugins.rst:126 +msgid "" +"To establish and configure the connection with the controller cluster you " +"must set some parameters, including NSX-mh API endpoints, access " +"credentials, and optionally specify settings for HTTP timeouts, redirects " +"and retries in case of connection failures:" +msgstr "" + +#: ../networking_config-plugins.rst:140 +msgid "" +"To ensure correct operations, the ``nsx_user`` user must have administrator " +"credentials on the NSX-mh platform." +msgstr "" + +#: ../networking_config-plugins.rst:143 +msgid "" +"A controller API endpoint consists of the IP address and port for the " +"controller; if you omit the port, port 443 is used. If multiple API " +"endpoints are specified, it is up to the user to ensure that all these " +"endpoints belong to the same controller cluster. The OpenStack Networking " +"VMware NSX-mh plug-in does not perform this check, and results might be " +"unpredictable." +msgstr "" + +#: ../networking_config-plugins.rst:150 +msgid "" +"When you specify multiple API endpoints, the plug-in takes care of load " +"balancing requests on the various API endpoints." +msgstr "" + +#: ../networking_config-plugins.rst:153 +msgid "" +"The UUID of the NSX-mh transport zone that should be used by default when a " +"tenant creates a network. You can get this value from the Transport Zones " +"page for the NSX-mh manager:" +msgstr "" + +#: ../networking_config-plugins.rst:157 +msgid "" +"Alternatively the transport zone identifier can be retrieved by query the " +"NSX-mh API: ``/ws.v1/transport-zone``" +msgstr "" + +#: ../networking_config-plugins.rst:170 +msgid "" +"Ubuntu packaging currently does not update the neutron init script to point " +"to the NSX-mh configuration file. Instead, you must manually update :file:`/" +"etc/default/neutron-server` to add this line:" +msgstr "" + +#: ../networking_config-plugins.rst:179 ../networking_config-plugins.rst:243 +msgid "" +"For database configuration, see `Install Networking Services `__ in the Installation Guide." +msgstr "" + +#: ../networking_config-plugins.rst:184 +msgid "Restart neutron-server to apply settings:" +msgstr "" + +#: ../networking_config-plugins.rst:192 +msgid "" +"The neutron NSX-mh plug-in does not implement initial re-synchronization of " +"Neutron resources. Therefore resources that might already exist in the " +"database when Neutron is switched to the NSX-mh plug-in will not be created " +"on the NSX-mh backend upon restart." +msgstr "" + +#: ../networking_config-plugins.rst:198 +msgid "Example :file:`nsx.ini` file:" +msgstr "" + +#: ../networking_config-plugins.rst:223 +msgid "Configure PLUMgrid plug-in" +msgstr "" + +#: ../networking_config-plugins.rst:231 +msgid "" +"Edit the [PLUMgridDirector] section in the :file:`/etc/neutron/plugins/" +"plumgrid/plumgrid.ini` file and specify the IP address, port, admin user " +"name, and password of the PLUMgrid Director:" +msgstr "" + +#: ../networking_introduction.rst:3 +msgid "Introduction to Networking" +msgstr "" + +#: ../networking_introduction.rst:5 +msgid "" +"The Networking service, code-named neutron, provides an API that lets you " +"define network connectivity and addressing in the cloud. The Networking " +"service enables operators to leverage different networking technologies to " +"power their cloud networking. The Networking service also provides an API to " +"configure and manage a variety of network services ranging from L3 " +"forwarding and NAT to load balancing, edge firewalls, and IPsec VPN." +msgstr "" + +#: ../networking_introduction.rst:13 +msgid "" +"For a detailed description of the Networking API abstractions and their " +"attributes, see the `OpenStack Networking API v2.0 Reference `__." +msgstr "" + +#: ../networking_introduction.rst:18 +msgid "Networking API" +msgstr "" + +#: ../networking_introduction.rst:20 +msgid "" +"Networking is a virtual network service that provides a powerful API to " +"define the network connectivity and IP addressing that devices from other " +"services, such as Compute, use." +msgstr "" + +#: ../networking_introduction.rst:24 +msgid "" +"The Compute API has a virtual server abstraction to describe computing " +"resources. Similarly, the Networking API has virtual network, subnet, and " +"port abstractions to describe networking resources." +msgstr "" + +# #-#-#-#-# networking_introduction.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +# #-#-#-#-# telemetry-measurements.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +#: ../networking_introduction.rst:29 ../telemetry-measurements.rst:97 +#: ../telemetry-measurements.rst:430 ../telemetry-measurements.rst:484 +#: ../telemetry-measurements.rst:528 ../telemetry-measurements.rst:589 +#: ../telemetry-measurements.rst:664 ../telemetry-measurements.rst:697 +#: ../telemetry-measurements.rst:752 ../telemetry-measurements.rst:802 +#: ../telemetry-measurements.rst:839 ../telemetry-measurements.rst:910 +#: ../telemetry-measurements.rst:973 ../telemetry-measurements.rst:1059 +#: ../telemetry-measurements.rst:1137 ../telemetry-measurements.rst:1202 +#: ../telemetry-measurements.rst:1253 ../telemetry-measurements.rst:1279 +#: ../telemetry-measurements.rst:1302 ../telemetry-measurements.rst:1322 +msgid "Resource" +msgstr "" + +#: ../networking_introduction.rst:31 +msgid "**Network**" +msgstr "" + +#: ../networking_introduction.rst:31 +msgid "" +"An isolated L2 segment, analogous to VLAN in the physical networking world." +msgstr "" + +#: ../networking_introduction.rst:34 +msgid "**Subnet**" +msgstr "" + +#: ../networking_introduction.rst:34 +msgid "A block of v4 or v6 IP addresses and associated configuration state." +msgstr "" + +#: ../networking_introduction.rst:37 +msgid "**Port**" +msgstr "" + +#: ../networking_introduction.rst:37 +msgid "" +"A connection point for attaching a single device, such as the NIC of a " +"virtual server, to a virtual network. Also describes the associated network " +"configuration, such as the MAC and IP addresses to be used on that port." +msgstr "" + +#: ../networking_introduction.rst:43 +msgid "**Networking resources**" +msgstr "" + +#: ../networking_introduction.rst:45 +msgid "" +"To configure rich network topologies, you can create and configure networks " +"and subnets and instruct other OpenStack services like Compute to attach " +"virtual devices to ports on these networks." +msgstr "" + +#: ../networking_introduction.rst:49 +msgid "" +"In particular, Networking supports each tenant having multiple private " +"networks and enables tenants to choose their own IP addressing scheme, even " +"if those IP addresses overlap with those that other tenants use." +msgstr "" + +#: ../networking_introduction.rst:53 +msgid "The Networking service:" +msgstr "" + +#: ../networking_introduction.rst:55 +msgid "" +"Enables advanced cloud networking use cases, such as building multi-tiered " +"web applications and enabling migration of applications to the cloud without " +"changing IP addresses." +msgstr "" + +#: ../networking_introduction.rst:59 +msgid "" +"Offers flexibility for the cloud administrator to customize network " +"offerings." +msgstr "" + +#: ../networking_introduction.rst:62 +msgid "" +"Enables developers to extend the Networking API. Over time, the extended " +"functionality becomes part of the core Networking API." +msgstr "" + +#: ../networking_introduction.rst:66 +msgid "Configure SSL support for networking API" +msgstr "" + +#: ../networking_introduction.rst:68 +msgid "" +"OpenStack Networking supports SSL for the Networking API server. By default, " +"SSL is disabled but you can enable it in the :file:`neutron.conf` file." +msgstr "" + +#: ../networking_introduction.rst:72 +msgid "Set these options to configure SSL:" +msgstr "" + +#: ../networking_introduction.rst:75 +msgid "Enables SSL on the networking API server." +msgstr "" + +#: ../networking_introduction.rst:75 +msgid "``use_ssl = True``" +msgstr "" + +#: ../networking_introduction.rst:78 +msgid "" +"Certificate file that is used when you securely start the Networking API " +"server." +msgstr "" + +#: ../networking_introduction.rst:79 +msgid "``ssl_cert_file = PATH_TO_CERTFILE``" +msgstr "" + +#: ../networking_introduction.rst:82 +msgid "" +"Private key file that is used when you securely start the Networking API " +"server." +msgstr "" + +#: ../networking_introduction.rst:83 +msgid "``ssl_key_file = PATH_TO_KEYFILE``" +msgstr "" + +#: ../networking_introduction.rst:86 +msgid "" +"Optional. CA certificate file that is used when you securely start the " +"Networking API server. This file verifies connecting clients. Set this " +"option when API clients must authenticate to the API server by using SSL " +"certificates that are signed by a trusted CA." +msgstr "" + +#: ../networking_introduction.rst:89 +msgid "``ssl_ca_file = PATH_TO_CAFILE``" +msgstr "" + +#: ../networking_introduction.rst:92 +msgid "" +"The value of TCP\\_KEEPIDLE, in seconds, for each server socket when " +"starting the API server. Not supported on OS X." +msgstr "" + +#: ../networking_introduction.rst:93 +msgid "``tcp_keepidle = 600``" +msgstr "" + +#: ../networking_introduction.rst:96 +msgid "Number of seconds to keep retrying to listen." +msgstr "" + +#: ../networking_introduction.rst:96 +msgid "``retry_until_window = 30``" +msgstr "" + +#: ../networking_introduction.rst:99 +msgid "Number of backlog requests with which to configure the socket." +msgstr "" + +#: ../networking_introduction.rst:99 +msgid "``backlog = 4096``" +msgstr "" + +#: ../networking_introduction.rst:102 +msgid "Load-Balancer-as-a-Service (LBaaS) overview" +msgstr "" + +#: ../networking_introduction.rst:104 +msgid "" +"Load-Balancer-as-a-Service (LBaaS) enables Networking to distribute incoming " +"requests evenly among designated instances. This distribution ensures that " +"the workload is shared predictably among instances and enables more " +"effective use of system resources. Use one of these load balancing methods " +"to distribute incoming requests:" +msgstr "" + +#: ../networking_introduction.rst:111 +msgid "Rotates requests evenly between multiple instances." +msgstr "" + +#: ../networking_introduction.rst:111 +msgid "Round robin" +msgstr "" + +#: ../networking_introduction.rst:114 +msgid "" +"Requests from a unique source IP address are consistently directed to the " +"same instance." +msgstr "" + +#: ../networking_introduction.rst:115 +msgid "Source IP" +msgstr "" + +#: ../networking_introduction.rst:118 +msgid "" +"Allocates requests to the instance with the least number of active " +"connections." +msgstr "" + +#: ../networking_introduction.rst:119 +msgid "Least connections" +msgstr "" + +#: ../networking_introduction.rst:122 +msgid "Feature" +msgstr "" + +#: ../networking_introduction.rst:124 +msgid "**Monitors**" +msgstr "" + +#: ../networking_introduction.rst:124 +msgid "" +"LBaaS provides availability monitoring with the ``ping``, TCP, HTTP and " +"HTTPS GET methods. Monitors are implemented to determine whether pool " +"members are available to handle requests." +msgstr "" + +#: ../networking_introduction.rst:129 +msgid "**Management**" +msgstr "" + +#: ../networking_introduction.rst:129 +msgid "" +"LBaaS is managed using a variety of tool sets. The REST API is available for " +"programmatic administration and scripting. Users perform administrative " +"management of load balancers through either the CLI (``neutron``) or the " +"OpenStack dashboard." +msgstr "" + +#: ../networking_introduction.rst:136 +msgid "**Connection limits**" +msgstr "" + +#: ../networking_introduction.rst:136 +msgid "" +"Ingress traffic can be shaped with *connection limits*. This feature allows " +"workload control, and can also assist with mitigating DoS (Denial of " +"Service) attacks." +msgstr "" + +#: ../networking_introduction.rst:141 +msgid "**Session persistence**" +msgstr "" + +#: ../networking_introduction.rst:141 +msgid "" +"LBaaS supports session persistence by ensuring incoming requests are routed " +"to the same instance within a pool of multiple instances. LBaaS supports " +"routing decisions based on cookies and source IP address." +msgstr "" + +#: ../networking_introduction.rst:150 +msgid "Firewall-as-a-Service (FWaaS) overview" +msgstr "" + +#: ../networking_introduction.rst:152 +msgid "" +"The Firewall-as-a-Service (FWaaS) plug-in adds perimeter firewall management " +"to Networking. FWaaS uses iptables to apply firewall policy to all " +"Networking routers within a project. FWaaS supports one firewall policy and " +"logical firewall instance per project." +msgstr "" + +#: ../networking_introduction.rst:157 +msgid "" +"Whereas security groups operate at the instance-level, FWaaS operates at the " +"perimeter to filter traffic at the neutron router." +msgstr "" + +#: ../networking_introduction.rst:162 +msgid "" +"FWaaS is currently in technical preview; untested operation is not " +"recommended." +msgstr "" + +#: ../networking_introduction.rst:165 +msgid "" +"The example diagram illustrates the flow of ingress and egress traffic for " +"the VM2 instance:" +msgstr "" + +#: ../networking_introduction.rst:168 +msgid "|FWaaS architecture|" +msgstr "" + +#: ../networking_introduction.rst:170 +msgid "**To enable FWaaS**" +msgstr "" + +#: ../networking_introduction.rst:172 +msgid "FWaaS management options are also available in the OpenStack dashboard." +msgstr "" + +#: ../networking_introduction.rst:174 +msgid "Enable the FWaaS plug-in in the :file:`/etc/neutron/neutron.conf` file:" +msgstr "" + +#: ../networking_introduction.rst:192 +msgid "" +"On Ubuntu, modify the ``[fwaas]`` section in the :file:`/etc/neutron/" +"fwaas_driver.ini` file instead of :file:`/etc/neutron/neutron.conf`." +msgstr "" + +#: ../networking_introduction.rst:202 +msgid "" +"Enable the option in the :file:`/usr/share/openstack-dashboard/" +"openstack_dashboard/local/local_settings.py` file, which is typically " +"located on the controller node:" +msgstr "" + +#: ../networking_introduction.rst:214 +msgid "" +"Restart the neutron-l3-agent and neutron-server services to apply the " +"settings." +msgstr "" + +#: ../networking_introduction.rst:217 +msgid "**To configure Firewall-as-a-Service**" msgstr "" #: ../networking_introduction.rst:219 @@ -4998,259 +15210,75 @@ msgid "" "create a firewall that applies the policy." msgstr "" -#: ../keystone_integrate_identity_backend_ldap.rst:132 +#: ../networking_introduction.rst:222 +msgid "Create a firewall rule:" +msgstr "" + +#: ../networking_introduction.rst:229 msgid "" -"Create the organizational units (OU) in the LDAP directories, and define " -"their corresponding locations in the :file:`/etc/keystone/domains/keystone." -"DOMAIN_NAME.conf` file. For example:" +"The Networking client requires a protocol value; if the rule is protocol " +"agnostic, you can use the ``any`` value." msgstr "" -#: ../keystone_integrate_identity_backend_ldap.rst:29 +#: ../networking_introduction.rst:232 +msgid "Create a firewall policy:" +msgstr "" + +#: ../networking_introduction.rst:239 msgid "" -"Create the organizational units (OU) in the LDAP directory, and define the " -"corresponding location in the :file:`keystone.conf` file:" +"Separate firewall rule IDs or names with spaces. The order in which you " +"specify the rules is important." msgstr "" -#: ../keystone_integrate_assignment_backend_ldap.rst:40 +#: ../networking_introduction.rst:242 msgid "" -"Create the organizational units (OU) in the LDAP directory, and define their " -"corresponding location in the ``keystone.conf`` file:" +"You can create a firewall policy without any rules and add rules later, as " +"follows:" msgstr "" -# #-#-#-#-# networking_config-agents.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -# #-#-#-#-# networking_introduction.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -#: ../networking_config-agents.rst:388 ../networking_introduction.rst:196 -msgid "Create the required tables in the database:" +#: ../networking_introduction.rst:245 +msgid "To add multiple rules, use the update operation." msgstr "" -#: ../blockstorage_backup_disks.rst:54 +#: ../networking_introduction.rst:247 +msgid "To add a single rule, use the insert-rule operation." +msgstr "" + +#: ../networking_introduction.rst:249 msgid "" -"Create the snapshot; you can do this while the volume is attached to an " -"instance::" +"For more details, see `Networking command-line client `__ in the OpenStack " +"Command-Line Interface Reference." msgstr "" -#: ../orchestration-stack-domain-users.rst:79 -msgid "Create the user::" -msgstr "" - -#: ../networking_adv-features.rst:493 -msgid "Creates QoS queue (admin-only)." -msgstr "" - -#: ../networking_adv-features.rst:501 -msgid "Creates a default system queue." -msgstr "" - -#: ../networking_adv-features.rst:272 +#: ../networking_introduction.rst:257 msgid "" -"Creates a floating IP address and associates it with a port, in a single " -"step." +"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_adv-features.rst:267 -msgid "Creates a floating IP address and associates it with a port." +#: ../networking_introduction.rst:261 +msgid "Create a firewall:" msgstr "" -#: ../networking_adv-features.rst:424 +#: ../networking_introduction.rst:269 msgid "" -"Creates a health monitor that checks to make sure our instances are still " -"running on the specified protocol-port." +"The firewall remains in PENDING\\_CREATE state until you create a Networking " +"router and attach an interface to it." msgstr "" -#: ../networking_adv-features.rst:404 -msgid "Creates a load balancer pool by using specific provider." +#: ../networking_introduction.rst:272 +msgid "**Allowed-address-pairs.**" msgstr "" -#: ../networking_adv-features.rst:785 -msgid "Creates a metering label." -msgstr "" - -#: ../networking_adv-features.rst:803 -msgid "Creates a metering rule." -msgstr "" - -#: ../networking_use.rst:125 -msgid "Creates a network that all tenants can use." -msgstr "" - -#: ../networking_use.rst:49 -msgid "Creates a network." -msgstr "" - -#: ../networking_adv-features.rst:383 -msgid "Creates a port and associates two security groups." -msgstr "" - -#: ../networking_adv-features.rst:358 -msgid "Creates a security group for our web servers." -msgstr "" - -#: ../networking_adv-features.rst:366 -msgid "Creates a security group rule to allow port 80 ingress." -msgstr "" - -#: ../networking_use.rst:137 -msgid "Creates a subnet that has no gateway IP address." -msgstr "" - -#: ../networking_use.rst:53 -msgid "Creates a subnet that is associated with net1." -msgstr "" - -#: ../networking_use.rst:143 -msgid "Creates a subnet with DHCP disabled." -msgstr "" - -#: ../networking_use.rst:131 -msgid "Creates a subnet with a specified gateway IP address." -msgstr "" - -#: ../networking_use.rst:157 -msgid "Creates a subnet with a specified set of dns name servers." -msgstr "" - -#: ../networking_adv-features.rst:437 +#: ../networking_introduction.rst:274 msgid "" -"Creates a virtual IP (VIP) address that, when accessed through the load " -"balancer, directs the requests to one of the pool members." -msgstr "" - -#: ../networking_adv-features.rst:217 -msgid "" -"Creates an internal-only router that connects to multiple L2 networks " -"privately." -msgstr "" - -#: ../networking_adv-features.rst:208 -msgid "Creates external networks." -msgstr "" - -#: ../blockstorage_volume_backed_image.rst:52 -msgid "Creating a Volume-backed image" -msgstr "" - -#: ../telemetry-measurements.rst:738 -msgid "Creation of the snapshot" -msgstr "" - -#: ../telemetry-measurements.rst:717 -msgid "Creation of the volume" -msgstr "" - -#: ../telemetry-measurements.rst:957 -msgid "Creation reques\\ ts for this IP" -msgstr "" - -#: ../telemetry-measurements.rst:917 -msgid "Creation reques\\ ts for this net\\ work" -msgstr "" - -#: ../telemetry-measurements.rst:937 -msgid "Creation reques\\ ts for this port" -msgstr "" - -#: ../telemetry-measurements.rst:946 -msgid "Creation reques\\ ts for this rou\\ ter" -msgstr "" - -#: ../telemetry-measurements.rst:927 -msgid "Creation reques\\ ts for this sub\\ net" -msgstr "" - -#: ../identity_concepts.rst:16 -msgid "Credentials" -msgstr "" - -#: ../cross_project_cors.rst:5 -msgid "Cross-origin resource sharing" -msgstr "" - -#: ../cross_project.rst:3 -msgid "Cross-project features" -msgstr "" - -#: ../telemetry-measurements.rst:119 ../telemetry-measurements.rst:144 -#: ../telemetry-measurements.rst:151 ../telemetry-measurements.rst:164 -#: ../telemetry-measurements.rst:172 ../telemetry-measurements.rst:180 -#: ../telemetry-measurements.rst:189 ../telemetry-measurements.rst:232 -#: ../telemetry-measurements.rst:241 ../telemetry-measurements.rst:250 -#: ../telemetry-measurements.rst:259 ../telemetry-measurements.rst:437 -#: ../telemetry-measurements.rst:440 ../telemetry-measurements.rst:443 -#: ../telemetry-measurements.rst:446 -msgid "Cumu\\ lative" -msgstr "" - -#: ../telemetry-measurements.rst:130 ../telemetry-measurements.rst:137 -#: ../telemetry-measurements.rst:626 ../telemetry-measurements.rst:630 -#: ../telemetry-measurements.rst:633 ../telemetry-measurements.rst:637 -#: ../telemetry-measurements.rst:641 ../telemetry-measurements.rst:645 -#: ../telemetry-measurements.rst:650 -msgid "Cumul\\ ative" -msgstr "" - -#: ../telemetry-measurements.rst:983 ../telemetry-measurements.rst:986 -#: ../telemetry-measurements.rst:989 ../telemetry-measurements.rst:992 -#: ../telemetry-measurements.rst:995 ../telemetry-measurements.rst:998 -#: ../telemetry-measurements.rst:1001 ../telemetry-measurements.rst:1004 -#: ../telemetry-measurements.rst:1007 ../telemetry-measurements.rst:1011 -#: ../telemetry-measurements.rst:1015 ../telemetry-measurements.rst:1018 -#: ../telemetry-measurements.rst:1042 ../telemetry-measurements.rst:1045 -#: ../telemetry-measurements.rst:1079 ../telemetry-measurements.rst:1087 -#: ../telemetry-measurements.rst:1091 -msgid "Cumula\\ tive" -msgstr "" - -# #-#-#-#-# telemetry-data-collection.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -# #-#-#-#-# telemetry-measurements.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -#: ../telemetry-data-collection.rst:453 ../telemetry-measurements.rst:33 -#: ../telemetry-measurements.rst:1326 -msgid "Cumulative" -msgstr "" - -#: ../blockstorage-driver-filter-weighing.rst:234 -msgid "Current QoS specs for the requested volume type" -msgstr "" - -#: ../telemetry-measurements.rst:532 -msgid "Current power of the system" -msgstr "" - -#: ../telemetry-measurements.rst:498 -msgid "Current reading from sensor" -msgstr "" - -#: ../telemetry-measurements.rst:535 -msgid "Current tempera\\ ture of the system" -msgstr "" - -#: ../keystone_caching_layer.rst:78 -msgid "" -"Currently ``assignment`` has caching for ``project``, ``domain``, and " -"``role`` specific requests (primarily around the CRUD actions). Caching is " -"currently not implemented on grants. The ``list`` methods are not subject to " -"caching." -msgstr "" - -#: ../keystone_token-binding.rst:29 -msgid "Currently ``kerberos`` and ``x509`` are supported." -msgstr "" - -#: ../compute-networking-nova.rst:26 -msgid "" -"Currently, Compute with ``nova-network`` only supports Linux bridge " -"networking that allows virtual interfaces to connect to the outside network " -"through the physical interface." -msgstr "" - -#: ../orchestration-auth-model.rst:18 -msgid "Currently, Orchestration provides two kinds of authorization models:" -msgstr "" - -#: ../objectstorage_arch.rst:73 -msgid "" -"Currently, a 2 TB or 3 TB SATA disk delivers good performance for the price. " -"You can use desktop-grade drives if you have responsive remote hands in the " -"datacenter and enterprise-grade drives if you don't." +"``Allowed-address-pairs`` enable you to specify mac_address/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." msgstr "" #: ../networking_introduction.rst:281 @@ -5259,6 +15287,952 @@ msgid "" "allowed-address-pairs extension." msgstr "" +#: ../networking_introduction.rst:284 +msgid "**Basic allowed-address-pairs operations.**" +msgstr "" + +#: ../networking_introduction.rst:286 +msgid "Create a port with a specified allowed address pairs:" +msgstr "" + +#: ../networking_introduction.rst:293 +msgid "Update a port by adding allowed address pairs:" +msgstr "" + +#: ../networking_introduction.rst:302 +msgid "" +"In releases earlier than Juno, OpenStack Networking prevents setting an " +"allowed address pair on a port that matches the MAC address and one of the " +"fixed IP addresses of the port." +msgstr "" + +#: ../networking_introduction.rst:310 +msgid "Virtual-Private-Network-as-a-Service (VPNaaS)" +msgstr "" + +#: ../networking_introduction.rst:312 +msgid "" +"The VPNaaS extension enables OpenStack tenants to extend private networks " +"across the internet." +msgstr "" + +#: ../networking_introduction.rst:315 +msgid "This extension introduces these resources:" +msgstr "" + +#: ../networking_introduction.rst:317 +msgid "" +":term:`service`. A parent object that associates VPN with a specific subnet " +"and router." +msgstr "" + +#: ../networking_introduction.rst:320 +msgid "" +"The Internet Key Exchange (IKE) policy that identifies the authentication " +"and encryption algorithm to use during phase one and two negotiation of a " +"VPN connection." +msgstr "" + +#: ../networking_introduction.rst:324 +msgid "" +"The IP security policy that specifies the authentication and encryption " +"algorithm and encapsulation mode to use for the established VPN connection." +msgstr "" + +#: ../networking_introduction.rst:328 +msgid "" +"Details for the site-to-site IPsec connection, including the peer CIDRs, " +"MTU, authentication mode, peer address, DPD settings, and status." +msgstr "" + +#: ../networking_introduction.rst:331 +msgid "This initial implementation of the VPNaaS extension provides:" +msgstr "" + +#: ../networking_introduction.rst:333 +msgid "Site-to-site VPN that connects two private networks." +msgstr "" + +#: ../networking_introduction.rst:335 +msgid "Multiple VPN connections per tenant." +msgstr "" + +#: ../networking_introduction.rst:337 +msgid "" +"IKEv1 policy support with 3des, aes-128, aes-256, or aes-192 encryption." +msgstr "" + +#: ../networking_introduction.rst:339 +msgid "" +"IPSec policy support with 3des, aes-128, aes-192, or aes-256 encryption, " +"sha1 authentication, ESP, AH, or AH-ESP transform protocol, and tunnel or " +"transport mode encapsulation." +msgstr "" + +#: ../networking_introduction.rst:343 +msgid "" +"Dead Peer Detection (DPD) with hold, clear, restart, disabled, or restart-by-" +"peer actions." +msgstr "" + +#: ../networking_multi-dhcp-agents.rst:3 +msgid "Scalable and highly available DHCP agents" +msgstr "" + +#: ../networking_multi-dhcp-agents.rst:5 +msgid "" +"This section describes how to use the agent management (alias agent) and " +"scheduler (alias agent_scheduler) extensions for DHCP agents scalability and " +"HA." +msgstr "" + +#: ../networking_multi-dhcp-agents.rst:11 +msgid "" +"Use the :command:`neutron ext-list` client command to check if these " +"extensions are enabled:" +msgstr "" + +#: ../networking_multi-dhcp-agents.rst:33 +msgid "There will be three hosts in the setup." +msgstr "" + +#: ../networking_multi-dhcp-agents.rst:41 +msgid "OpenStack controller host - controlnod" +msgstr "" + +#: ../networking_multi-dhcp-agents.rst:42 +msgid "" +"Runs the Networking, Identity, and Compute services that are required to " +"deploy VMs. The node must have at least one network interface that is " +"connected to the Management Network. Note that ``nova-network`` should not " +"be running because it is replaced by Neutron." +msgstr "" + +#: ../networking_multi-dhcp-agents.rst:47 +msgid "Runs ``nova-compute``, the Neutron L2 agent and DHCP agent" +msgstr "" + +#: ../networking_multi-dhcp-agents.rst:49 +msgid "Same as HostA" +msgstr "" + +#: ../networking_multi-dhcp-agents.rst:51 +msgid "**Hosts for demo**" +msgstr "" + +#: ../networking_multi-dhcp-agents.rst:56 +msgid "**controlnode: neutron server**" +msgstr "" + +#: ../networking_multi-dhcp-agents.rst:58 +#: ../networking_multi-dhcp-agents.rst:87 +msgid "Neutron configuration file :file:`/etc/neutron/neutron.conf`:" +msgstr "" + +#: ../networking_multi-dhcp-agents.rst:70 +#: ../networking_multi-dhcp-agents.rst:98 +msgid "" +"Update the plug-in configuration file :file:`/etc/neutron/plugins/" +"linuxbridge/linuxbridge_conf.ini`:" +msgstr "" + +#: ../networking_multi-dhcp-agents.rst:85 +msgid "**HostA and HostB: L2 agent**" +msgstr "" + +#: ../networking_multi-dhcp-agents.rst:113 +msgid "Update the nova configuration file :file:`/etc/nova/nova.conf`:" +msgstr "" + +#: ../networking_multi-dhcp-agents.rst:130 +msgid "**HostA and HostB: DHCP agent**" +msgstr "" + +#: ../networking_multi-dhcp-agents.rst:132 +msgid "Update the DHCP configuration file :file:`/etc/neutron/dhcp_agent.ini`:" +msgstr "" + +#: ../networking_multi-dhcp-agents.rst:140 +msgid "Commands in agent management and scheduler extensions" +msgstr "" + +#: ../networking_multi-dhcp-agents.rst:142 +msgid "" +"The following commands require the tenant running the command to have an " +"admin role." +msgstr "" + +#: ../networking_multi-dhcp-agents.rst:147 +msgid "" +"Ensure that the following environment variables are set. These are used by " +"the various clients to access the Identity service." +msgstr "" + +#: ../networking_multi-dhcp-agents.rst:157 +msgid "**Settings**" +msgstr "" + +#: ../networking_multi-dhcp-agents.rst:159 +msgid "To experiment, you need VMs and a neutron network:" +msgstr "" + +#: ../networking_multi-dhcp-agents.rst:181 +msgid "**Manage agents in neutron deployment**" +msgstr "" + +#: ../networking_multi-dhcp-agents.rst:183 +msgid "" +"Every agent that supports these extensions will register itself with the " +"neutron server when it starts up." +msgstr "" + +#: ../networking_multi-dhcp-agents.rst:186 +msgid "List all agents:" +msgstr "" + +#: ../networking_multi-dhcp-agents.rst:201 +msgid "" +"The output shows information for four agents. The ``alive`` field shows " +"``:-)`` if the agent reported its state within the period defined by the " +"``agent_down_time`` option in the :file:`neutron.conf` file. Otherwise the " +"``alive`` is ``xxx``." +msgstr "" + +#: ../networking_multi-dhcp-agents.rst:206 +msgid "List the DHCP agents that host a specified network:" +msgstr "" + +#: ../networking_multi-dhcp-agents.rst:208 +msgid "" +"In some deployments, one DHCP agent is not enough to hold all network data. " +"In addition, you must have a backup for it even when the deployment is " +"small. The same network can be assigned to more than one DHCP agent and one " +"DHCP agent can host more than one network." +msgstr "" + +#: ../networking_multi-dhcp-agents.rst:213 +msgid "List DHCP agents that host a specified network:" +msgstr "" + +#: ../networking_multi-dhcp-agents.rst:225 +msgid "List the networks hosted by a given DHCP agent:" +msgstr "" + +#: ../networking_multi-dhcp-agents.rst:227 +msgid "This command is to show which networks a given dhcp agent is managing." +msgstr "" + +#: ../networking_multi-dhcp-agents.rst:241 +msgid "Show agent details." +msgstr "" + +#: ../networking_multi-dhcp-agents.rst:243 +msgid "The :command:`agent-show` command shows details for a specified agent:" +msgstr "" + +#: ../networking_multi-dhcp-agents.rst:273 +msgid "" +"In this output, ``heartbeat_timestamp`` is the time on the neutron server. " +"You do not need to synchronize all agents to this time for this extension to " +"run correctly. ``configurations`` describes the static configuration for the " +"agent or run time data. This agent is a DHCP agent and it hosts one network, " +"one subnet, and three ports." +msgstr "" + +#: ../networking_multi-dhcp-agents.rst:279 +msgid "" +"Different types of agents show different details. The following output shows " +"information for a Linux bridge agent:" +msgstr "" + +#: ../networking_multi-dhcp-agents.rst:307 +msgid "" +"The output shows ``bridge-mapping`` and the number of virtual network " +"devices on this L2 agent." +msgstr "" + +#: ../networking_multi-dhcp-agents.rst:310 +msgid "**Manage assignment of networks to DHCP agent**" +msgstr "" + +#: ../networking_multi-dhcp-agents.rst:312 +msgid "" +"Now that you have run the :command:`net-list-on-dhcp-agent` and :command:" +"`dhcp-agent-list-hosting-net` commands, you can add a network to a DHCP " +"agent and remove one from it." +msgstr "" + +#: ../networking_multi-dhcp-agents.rst:316 +msgid "Default scheduling." +msgstr "" + +#: ../networking_multi-dhcp-agents.rst:318 +msgid "" +"When you create a network with one port, you can schedule it to an active " +"DHCP agent. If many active DHCP agents are running, select one randomly. You " +"can design more sophisticated scheduling algorithms in the same way as nova-" +"schedule later on." +msgstr "" + +#: ../networking_multi-dhcp-agents.rst:336 +msgid "" +"It is allocated to DHCP agent on HostA. If you want to validate the behavior " +"through the :command:`dnsmasq` command, you must create a subnet for the " +"network because the DHCP agent starts the dnsmasq service only if there is a " +"DHCP." +msgstr "" + +#: ../networking_multi-dhcp-agents.rst:341 +msgid "Assign a network to a given DHCP agent." +msgstr "" + +#: ../networking_multi-dhcp-agents.rst:343 +msgid "To add another DHCP agent to host the network, run this command:" +msgstr "" + +#: ../networking_multi-dhcp-agents.rst:360 +msgid "Remove a network from a specified DHCP agent." +msgstr "" + +#: ../networking_multi-dhcp-agents.rst:362 +msgid "" +"This command is the sibling command for the previous one. Remove ``net2`` " +"from the DHCP agent for HostA:" +msgstr "" + +#: ../networking_multi-dhcp-agents.rst:378 +msgid "" +"You can see that only the DHCP agent for HostB is hosting the ``net2`` " +"network." +msgstr "" + +#: ../networking_multi-dhcp-agents.rst:381 +msgid "**HA of DHCP agents**" +msgstr "" + +#: ../networking_multi-dhcp-agents.rst:383 +msgid "" +"Boot a VM on net2. Let both DHCP agents host ``net2``. Fail the agents in " +"turn to see if the VM can still get the desired IP." +msgstr "" + +#: ../networking_multi-dhcp-agents.rst:386 +msgid "Boot a VM on net2:" +msgstr "" + +#: ../networking_multi-dhcp-agents.rst:421 +msgid "Make sure both DHCP agents hosting 'net2':" +msgstr "" + +#: ../networking_multi-dhcp-agents.rst:423 +msgid "Use the previous commands to assign the network to agents." +msgstr "" + +#: ../networking_multi-dhcp-agents.rst:436 +msgid "**Test the HA**" +msgstr "" + +#: ../networking_multi-dhcp-agents.rst:438 +msgid "" +"Log in to the ``myserver4`` VM, and run ``udhcpc``, ``dhclient`` or other " +"DHCP client." +msgstr "" + +#: ../networking_multi-dhcp-agents.rst:441 +msgid "" +"Stop the DHCP agent on HostA. Besides stopping the ``neutron-dhcp-agent`` " +"binary, you must stop the ``dnsmasq`` processes." +msgstr "" + +#: ../networking_multi-dhcp-agents.rst:444 +msgid "Run a DHCP client in VM to see if it can get the wanted IP." +msgstr "" + +#: ../networking_multi-dhcp-agents.rst:446 +msgid "Stop the DHCP agent on HostB too." +msgstr "" + +#: ../networking_multi-dhcp-agents.rst:448 +msgid "Run ``udhcpc`` in the VM; it cannot get the wanted IP." +msgstr "" + +#: ../networking_multi-dhcp-agents.rst:450 +msgid "Start DHCP agent on HostB. The VM gets the wanted IP again." +msgstr "" + +#: ../networking_multi-dhcp-agents.rst:452 +msgid "**Disable and remove an agent**" +msgstr "" + +#: ../networking_multi-dhcp-agents.rst:454 +msgid "" +"An administrator might want to disable an agent if a system hardware or " +"software upgrade is planned. Some agents that support scheduling also " +"support disabling and enabling agents, such as L3 and DHCP agents. After the " +"agent is disabled, the scheduler does not schedule new resources to the " +"agent. After the agent is disabled, you can safely remove the agent. Remove " +"the resources on the agent before you delete the agent." +msgstr "" + +#: ../networking_multi-dhcp-agents.rst:461 +msgid "To run the following commands, you must stop the DHCP agent on HostA." +msgstr "" + +#: ../networking_multi-dhcp-agents.rst:492 +msgid "" +"After deletion, if you restart the DHCP agent, it appears on the agent list " +"again." +msgstr "" + +#: ../networking_use.rst:3 +msgid "Use Networking" +msgstr "" + +#: ../networking_use.rst:5 +msgid "" +"You can manage OpenStack Networking services by using the service command. " +"For example:" +msgstr "" + +#: ../networking_use.rst:15 +msgid "Log files are in the :file:`/var/log/neutron` directory." +msgstr "" + +#: ../networking_use.rst:17 +msgid "Configuration files are in the :file:`/etc/neutron` directory." +msgstr "" + +#: ../networking_use.rst:19 +msgid "" +"Cloud administrators and tenants can use OpenStack Networking to build rich " +"network topologies. Cloud administrators can create network connectivity on " +"behalf of tenants." +msgstr "" + +#: ../networking_use.rst:24 +msgid "Core Networking API features" +msgstr "" + +#: ../networking_use.rst:26 +msgid "" +"After you install and configure Networking, tenants and administrators can " +"perform create-read-update-delete (CRUD) API networking operations by using " +"the Networking API directly or neutron command-line interface (CLI). The " +"neutron CLI is a wrapper around the Networking API. Every Networking API " +"call has a corresponding neutron command." +msgstr "" + +#: ../networking_use.rst:32 +msgid "" +"The CLI includes a number of options. For details, see the `OpenStack End " +"User Guide `__." +msgstr "" + +#: ../networking_use.rst:36 +msgid "Basic Networking operations" +msgstr "" + +#: ../networking_use.rst:38 +msgid "" +"To learn about advanced capabilities available through the neutron command-" +"line interface (CLI), read the networking section in the `OpenStack End User " +"Guide `__." +msgstr "" + +#: ../networking_use.rst:43 +msgid "" +"This table shows example neutron commands that enable you to complete basic " +"network operations:" +msgstr "" + +#: ../networking_use.rst:49 +msgid "Creates a network." +msgstr "" + +#: ../networking_use.rst:51 +msgid "``$ neutron net-create net1``" +msgstr "" + +#: ../networking_use.rst:53 +msgid "Creates a subnet that is associated with net1." +msgstr "" + +#: ../networking_use.rst:56 +msgid "``$ neutron subnet-create`` ``net1 10.0.0.0/24``" +msgstr "" + +#: ../networking_use.rst:59 +msgid "Lists ports for a specified tenant." +msgstr "" + +#: ../networking_use.rst:62 +msgid "``$ neutron port-list``" +msgstr "" + +#: ../networking_use.rst:64 +msgid "" +"Lists ports for a specified tenant and displays the ``id``, ``fixed_ips``, " +"and ``device_owner`` columns." +msgstr "" + +#: ../networking_use.rst:71 +msgid "``$ neutron port-list -c id`` ``-c fixed_ips -c device_owner``" +msgstr "" + +#: ../networking_use.rst:74 +msgid "Shows information for a specified port." +msgstr "" + +#: ../networking_use.rst:76 +msgid "``$ neutron port-show PORT_ID``" +msgstr "" + +#: ../networking_use.rst:79 +msgid "**Basic Networking operations**" +msgstr "" + +#: ../networking_use.rst:83 +msgid "" +"The ``device_owner`` field describes who owns the port. A port whose " +"``device_owner`` begins with:" +msgstr "" + +#: ../networking_use.rst:86 +msgid "``network`` is created by Networking." +msgstr "" + +#: ../networking_use.rst:88 +msgid "``compute`` is created by Compute." +msgstr "" + +#: ../networking_use.rst:91 +msgid "Administrative operations" +msgstr "" + +#: ../networking_use.rst:93 +msgid "" +"The cloud administrator can run any :command:`neutron` command on behalf of " +"tenants by specifying an Identity ``tenant_id`` in the command, as follows:" +msgstr "" + +#: ../networking_use.rst:109 +msgid "" +"To view all tenant IDs in Identity, run the following command as an Identity " +"service admin user:" +msgstr "" + +#: ../networking_use.rst:117 +msgid "Advanced Networking operations" +msgstr "" + +#: ../networking_use.rst:119 +msgid "" +"This table shows example Networking commands that enable you to complete " +"advanced network operations:" +msgstr "" + +#: ../networking_use.rst:125 +msgid "Creates a network that all tenants can use." +msgstr "" + +#: ../networking_use.rst:128 +msgid "``$ neutron net-create`` ``--shared public-net``" +msgstr "" + +#: ../networking_use.rst:131 +msgid "Creates a subnet with a specified gateway IP address." +msgstr "" + +#: ../networking_use.rst:134 +msgid "``$ neutron subnet-create`` ``--gateway 10.0.0.254 net1 10.0.0.0/24``" +msgstr "" + +#: ../networking_use.rst:137 +msgid "Creates a subnet that has no gateway IP address." +msgstr "" + +#: ../networking_use.rst:140 +msgid "``$ neutron subnet-create`` ``--no-gateway net1 10.0.0.0/24``" +msgstr "" + +#: ../networking_use.rst:143 +msgid "Creates a subnet with DHCP disabled." +msgstr "" + +#: ../networking_use.rst:146 +msgid "``$ neutron subnet-create`` ``net1 10.0.0.0/24 --enable-dhcp False``" +msgstr "" + +#: ../networking_use.rst:149 +msgid "Specified set of host routes." +msgstr "" + +#: ../networking_use.rst:151 +msgid "" +"``$ neutron subnet-create`` ``test-net1 40.0.0.0/24 --host-routes`` " +"``type=dict list=true`` ``destination=40.0.1.0/24,`` ``nexthop=40.0.0.2``" +msgstr "" + +#: ../networking_use.rst:157 +msgid "Creates a subnet with a specified set of dns name servers." +msgstr "" + +#: ../networking_use.rst:161 +msgid "" +"``$ neutron subnet-create test-net1`` ``40.0.0.0/24 --dns-nameservers`` " +"``list=true 8.8.4.4 8.8.8.8``" +msgstr "" + +#: ../networking_use.rst:165 +msgid "Displays all ports and IPs allocated on a network." +msgstr "" + +#: ../networking_use.rst:168 +msgid "``$ neutron port-list --network_id NET_ID``" +msgstr "" + +#: ../networking_use.rst:171 +msgid "**Advanced Networking operations**" +msgstr "" + +#: ../networking_use.rst:174 +msgid "Use Compute with Networking" +msgstr "" + +#: ../networking_use.rst:177 +msgid "Basic Compute and Networking operations" +msgstr "" + +#: ../networking_use.rst:179 +msgid "" +"This table shows example neutron and nova commands that enable you to " +"complete basic VM networking operations:" +msgstr "" + +#: ../networking_use.rst:183 +msgid "Action" +msgstr "" + +#: ../networking_use.rst:185 +msgid "Checks available networks." +msgstr "" + +#: ../networking_use.rst:187 +msgid "``$ neutron net-list``" +msgstr "" + +#: ../networking_use.rst:189 +msgid "Boots a VM with a single NIC on a selected Networking network." +msgstr "" + +#: ../networking_use.rst:192 +msgid "" +"``$ nova boot --image IMAGE --flavor`` ``FLAVOR --nic net-id=NET_ID VM_NAME``" +msgstr "" + +#: ../networking_use.rst:195 +msgid "" +"Searches for ports with a ``device_id`` that matches the Compute instance " +"UUID. See :ref: `Create and delete VMs`" +msgstr "" + +#: ../networking_use.rst:200 +msgid "``$ neutron port-list --device_id VM_ID``" +msgstr "" + +#: ../networking_use.rst:202 +msgid "Searches for ports, but shows onlythe ``mac_address`` of the port." +msgstr "" + +#: ../networking_use.rst:206 +msgid "``$ neutron port-list --field`` ``mac_address --device_id VM_ID``" +msgstr "" + +#: ../networking_use.rst:209 +msgid "Temporarily disables a port from sending traffic." +msgstr "" + +#: ../networking_use.rst:212 +msgid "``$ neutron port-update PORT_ID`` ``--admin_state_up False``" +msgstr "" + +#: ../networking_use.rst:216 +msgid "**Basic Compute and Networking operations**" +msgstr "" + +#: ../networking_use.rst:220 +msgid "The ``device_id`` can also be a logical router ID." +msgstr "" + +#: ../networking_use.rst:224 +msgid "" +"When you boot a Compute VM, a port on the network that corresponds to the VM " +"NIC is automatically created and associated with the default security group. " +"You can configure `security group rules <#enabling_ping_and_ssh>`__ to " +"enable users to access the VM." +msgstr "" + +#: ../networking_use.rst:235 +msgid "Advanced VM creation operations" +msgstr "" + +#: ../networking_use.rst:237 +msgid "" +"This table shows example nova and neutron commands that enable you to " +"complete advanced VM creation operations:" +msgstr "" + +#: ../networking_use.rst:243 +msgid "Boots a VM with multiple NICs." +msgstr "" + +#: ../networking_use.rst:246 +msgid "" +"``$ nova boot --image IMAGE --flavor`` ``FLAVOR --nic net-id=NET1-ID --nic`` " +"``net-id=NET2-ID VM_NAME``" +msgstr "" + +#: ../networking_use.rst:250 +msgid "" +"Boots a VM with a specific IP address. Note that you cannot use the ``--num-" +"instances`` parameter in this case." +msgstr "" + +#: ../networking_use.rst:256 +msgid "``$ nova boot --image IMAGE --flavor``" +msgstr "" + +#: ../networking_use.rst:256 +msgid "``FLAVOR --nic net-id=NET-ID,`` ``v4-fixed-ip=IP-ADDR VM_NAME``" +msgstr "" + +#: ../networking_use.rst:259 +msgid "" +"Boots a VM that connects to all networks that are accessible to the tenant " +"who submits the request (without the ``--nic`` option)." +msgstr "" + +#: ../networking_use.rst:264 +msgid "``$ nova boot --image IMAGE --flavor`` ``FLAVOR VM_NAME``" +msgstr "" + +#: ../networking_use.rst:268 +msgid "**Advanced VM creation operations**" +msgstr "" + +#: ../networking_use.rst:272 +msgid "" +"Cloud images that distribution vendors offer usually have only one active " +"NIC configured. When you boot with multiple NICs, you must configure " +"additional interfaces on the image or the NICS are not reachable." +msgstr "" + +#: ../networking_use.rst:277 +msgid "" +"The following Debian/Ubuntu-based example shows how to set up the interfaces " +"within the instance in the ``/etc/network/interfaces`` file. You must apply " +"this configuration to the image." +msgstr "" + +#: ../networking_use.rst:294 +msgid "Enable ping and SSH on VMs (security groups)" +msgstr "" + +#: ../networking_use.rst:296 +msgid "" +"You must configure security group rules depending on the type of plug-in you " +"are using. If you are using a plug-in that:" +msgstr "" + +#: ../networking_use.rst:299 +msgid "" +"Implements Networking security groups, you can configure security group " +"rules directly by using the :command:`neutron security-group-rule-create` " +"command. This example enables ``ping`` and ``ssh`` access to your VMs." +msgstr "" + +#: ../networking_use.rst:313 +msgid "" +"Does not implement Networking security groups, you can configure security " +"group rules by using the :command:`nova secgroup-add-rule` or :command:`euca-" +"authorize` command. These :command:`nova` commands enable ``ping`` and " +"``ssh`` access to your VMs." +msgstr "" + +#: ../networking_use.rst:325 +msgid "" +"If your plug-in implements Networking security groups, you can also leverage " +"Compute security groups by setting ``security_group_api = neutron`` in the :" +"file:`nova.conf` file. After you set this option, all Compute security group " +"commands are proxied to Networking." +msgstr "" + +#: ../objectstorage-admin.rst:3 +msgid "System administration for Object Storage" +msgstr "" + +#: ../objectstorage-admin.rst:5 +msgid "" +"By understanding Object Storage concepts, you can better monitor and " +"administer your storage solution. The majority of the administration " +"information is maintained in developer documentation at `docs.openstack.org/" +"developer/swift/ `__." +msgstr "" + +#: ../objectstorage-admin.rst:10 +msgid "" +"See the `OpenStack Configuration Reference `__ for a list of configuration options for Object " +"Storage." +msgstr "" + +#: ../objectstorage-monitoring.rst:3 +msgid "Object Storage monitoring" +msgstr "" + +#: ../objectstorage-monitoring.rst:5 +msgid "" +"Excerpted from a blog post by `Darrell Bishop `__" +msgstr "" + +#: ../objectstorage-monitoring.rst:8 +msgid "" +"An OpenStack Object Storage cluster is a collection of many daemons that " +"work together across many nodes. With so many different components, you must " +"be able to tell what is going on inside the cluster. Tracking server-level " +"meters like CPU utilization, load, memory consumption, disk usage and " +"utilization, and so on is necessary, but not sufficient." +msgstr "" + +#: ../objectstorage-monitoring.rst:14 +msgid "" +"What are different daemons are doing on each server? What is the volume of " +"object replication on node8? How long is it taking? Are there errors? If so, " +"when did they happen?" +msgstr "" + +#: ../objectstorage-monitoring.rst:18 +msgid "" +"In such a complex ecosystem, you can use multiple approaches to get the " +"answers to these questions. This section describes several approaches." +msgstr "" + +#: ../objectstorage-monitoring.rst:22 +msgid "Swift Recon" +msgstr "" + +#: ../objectstorage-monitoring.rst:24 +msgid "" +"The Swift Recon middleware (see http://swift.openstack.org/admin_guide." +"html#cluster-telemetry-and-monitoring) provides general machine statistics, " +"such as load average, socket statistics, ``/proc/meminfo`` contents, and so " +"on, as well as Swift-specific meters:" +msgstr "" + +#: ../objectstorage-monitoring.rst:30 +msgid "The MD5 sum of each ring file." +msgstr "" + +#: ../objectstorage-monitoring.rst:32 +msgid "The most recent object replication time." +msgstr "" + +#: ../objectstorage-monitoring.rst:34 +msgid "Count of each type of quarantined file: Account, container, or object." +msgstr "" + +#: ../objectstorage-monitoring.rst:37 +msgid "Count of \"async\\_pendings\" (deferred container updates) on disk." +msgstr "" + +#: ../objectstorage-monitoring.rst:39 +msgid "" +"Swift Recon is middleware that is installed in the object servers pipeline " +"and takes one required option: A local cache directory. To track " +"``async_pendings``, you must set up an additional cron job for each object " +"server. You access data by either sending HTTP requests directly to the " +"object server or using the ``swift-recon`` command-line client." +msgstr "" + +#: ../objectstorage-monitoring.rst:46 +msgid "" +"There are some good Object Storage cluster statistics but the general server " +"meters overlap with existing server monitoring systems. To get the Swift-" +"specific meters into a monitoring system, they must be polled. Swift Recon " +"essentially acts as a middleware meters collector. The process that feeds " +"meters to your statistics system, such as ``collectd`` and ``gmond``, " +"probably already runs on the storage node. So, you can choose to either talk " +"to Swift Recon or collect the meters directly." +msgstr "" + +#: ../objectstorage-monitoring.rst:56 +msgid "Swift-Informant" +msgstr "" + +#: ../objectstorage-monitoring.rst:58 +msgid "" +"Florian Hines developed the Swift-Informant middleware (see https://github." +"com/pandemicsyn/swift-informant) to get real-time visibility into Object " +"Storage client requests. It sits in the pipeline for the proxy server, and " +"after each request to the proxy server, sends three meters to a StatsD " +"server (see http://codeascraft.etsy.com/2011/02/15/measure-anything-measure-" +"everything/):" +msgstr "" + +#: ../objectstorage-monitoring.rst:65 +msgid "" +"A counter increment for a meter like ``obj.GET.200`` or ``cont.PUT.404``." +msgstr "" + +#: ../objectstorage-monitoring.rst:68 +msgid "" +"Timing data for a meter like ``acct.GET.200`` or ``obj.GET.200``. [The " +"README says the meters look like ``duration.acct.GET.200``, but I do not see " +"the ``duration`` in the code. I am not sure what the Etsy server does but " +"our StatsD server turns timing meters into five derivative meters with new " +"segments appended, so it probably works as coded. The first meter turns into " +"``acct.GET.200.lower``, ``acct.GET.200.upper``, ``acct.GET.200.mean``, " +"``acct.GET.200.upper_90``, and ``acct.GET.200.count``]." +msgstr "" + +#: ../objectstorage-monitoring.rst:77 +msgid "" +"A counter increase by the bytes transferred for a meter like ``tfer.obj." +"PUT.201``." +msgstr "" + +#: ../objectstorage-monitoring.rst:80 +msgid "" +"This is good for getting a feel for the quality of service clients are " +"experiencing with the timing meters, as well as getting a feel for the " +"volume of the various permutations of request server type, command, and " +"response code. Swift-Informant also requires no change to core Object " +"Storage code because it is implemented as middleware. However, it gives you " +"no insight into the workings of the cluster past the proxy server. If the " +"responsiveness of one storage node degrades, you can only see that some of " +"your requests are bad, either as high latency or error status codes. You do " +"not know exactly why or where that request tried to go. Maybe the container " +"server in question was on a good node but the object server was on a " +"different, poorly-performing node." +msgstr "" + +#: ../objectstorage-monitoring.rst:93 +msgid "Statsdlog" +msgstr "" + +#: ../objectstorage-monitoring.rst:95 +msgid "" +"Florian's `Statsdlog `__ project " +"increments StatsD counters based on logged events. Like Swift-Informant, it " +"is also non-intrusive, but statsdlog can track events from all Object " +"Storage daemons, not just proxy-server. The daemon listens to a UDP stream " +"of syslog messages and StatsD counters are incremented when a log line " +"matches a regular expression. Meter names are mapped to regex match patterns " +"in a JSON file, allowing flexible configuration of what meters are extracted " +"from the log stream." +msgstr "" + #: ../objectstorage-monitoring.rst:104 msgid "" "Currently, only the first matching regex triggers a StatsD counter " @@ -5275,1064 +16249,371 @@ msgid "" "prevent a time delay between events and sending data to StatsD." msgstr "" -#: ../blockstorage_volume_backed_image.rst:70 +#: ../objectstorage-monitoring.rst:118 msgid "" -"Currently, the cinder store of the Image services does not support uploading " -"and downloading of image data. By this limitation, Volume-backed images can " -"only be used to create a new volume." +"The next section describes another method for gathering Object Storage " +"operational meters." msgstr "" -#: ../database.rst:239 ../database.rst:245 +#: ../objectstorage-monitoring.rst:122 +msgid "Swift StatsD logging" +msgstr "" + +#: ../objectstorage-monitoring.rst:124 msgid "" -"DATASTORE_NAME is the name of either the MySQL datastore or the Percona " -"datastore. This is typically either ``mysql`` or ``percona``." +"StatsD (see http://codeascraft.etsy.com/2011/02/15/measure-anything-measure-" +"everything/) was designed for application code to be deeply instrumented; " +"meters are sent in real-time by the code that just noticed or did something. " +"The overhead of sending a meter is extremely low: a ``sendto`` of one UDP " +"packet. If that overhead is still too high, the StatsD client library can " +"send only a random portion of samples and StatsD approximates the actual " +"number when flushing meters upstream." msgstr "" -#: ../telemetry-data-collection.rst:1023 -msgid "DB2 NoSQL" -msgstr "" - -#: ../telemetry-data-collection.rst:1023 -msgid "DB2 NoSQL does not have native TTL nor ceilometer-expirer support." -msgstr "" - -#: ../telemetry-system-architecture.rst:99 +#: ../objectstorage-monitoring.rst:133 msgid "" -"DB2 nosql support is deprecated as of Liberty and will be removed in Mitaka " -"as the product is no longer in development." +"To avoid the problems inherent with middleware-based monitoring and after-" +"the-fact log processing, the sending of StatsD meters is integrated into " +"Object Storage itself. The submitted change set (see https://review." +"openstack.org/#change,6058) currently reports 124 meters across 15 Object " +"Storage daemons and the tempauth middleware. Details of the meters tracked " +"are in the `Administrator's Guide `__." msgstr "" -#: ../networking_config-agents.rst:143 -msgid "DHCP agent setup: NSX plug-in" -msgstr "" - -#: ../networking_config-agents.rst:130 -msgid "DHCP agent setup: OVS plug-in" -msgstr "" - -#: ../compute-networking-nova.rst:179 -msgid "DHCP server: dnsmasq" -msgstr "" - -#: ../dashboard.rst:3 -msgid "Dashboard" -msgstr "" - -#: ../objectstorage_components.rst:71 +#: ../objectstorage-monitoring.rst:141 msgid "" -"Data can be isolated into zones in the ring. Each partition replica is " -"guaranteed to reside in a different zone. A zone could represent a drive, a " -"server, a cabinet, a switch, or even a data center." +"The sending of meters is integrated with the logging framework. To enable, " +"configure ``log_statsd_host`` in the relevant config file. You can also " +"specify the port and a default sample rate. The specified default sample " +"rate is used unless a specific call to a statsd logging method (see the list " +"below) overrides it. Currently, no logging calls override the sample rate, " +"but it is conceivable that some meters may require accuracy (sample\\_rate " +"== 1) while others may not." msgstr "" -# #-#-#-#-# telemetry-best-practices.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -# #-#-#-#-# telemetry-data-collection.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -#: ../telemetry-best-practices.rst:9 ../telemetry-data-collection.rst:8 -msgid "Data collection" -msgstr "" - -#: ../telemetry-data-collection.rst:483 -msgid "Data collection and processing" -msgstr "" - -#: ../objectstorage_characteristics.rst:23 -msgid "Data doesn't have to be migrate to an entirely new storage system." -msgstr "" - -#: ../telemetry-data-collection.rst:497 +#: ../objectstorage-monitoring.rst:157 msgid "" -"Data gathered can be used for different purposes, which can impact how " -"frequently it needs to be published. Typically, a meter published for " -"billing purposes needs to be updated every 30 minutes while the same meter " -"may be needed for performance tuning every minute." +"Then the LogAdapter object returned by ``get_logger()``, usually stored in " +"``self.logger``, has these new methods:" msgstr "" -#: ../telemetry-measurements.rst:1274 -msgid "Data processing service for OpenStack" -msgstr "" - -#: ../objectstorage_features.rst:57 -msgid "Data protection and recovery for VM data." -msgstr "" - -#: ../telemetry-data-retrieval.rst:3 -msgid "Data retrieval" -msgstr "" - -#: ../telemetry-best-practices.rst:62 -msgid "Data storage" -msgstr "" - -#: ../identity_concepts.rst:14 +#: ../objectstorage-monitoring.rst:160 msgid "" -"Data that confirms the identity of the user. For example, user name and " -"password, user name and API key, or an authentication token that the " -"Identity service provides." +"``set_statsd_prefix(self, prefix)`` Sets the client library stat prefix " +"value which gets prefixed to every meter. The default prefix is the \"name\" " +"of the logger such as \"object-server\", \"container-auditor\", and so on. " +"This is currently used to turn \"proxy-server\" into one of \"proxy-server." +"Account\", \"proxy-server.Container\", or \"proxy-server.Object\" as soon as " +"the Controller object is determined and instantiated for the request." msgstr "" -#: ../networking_adv-features.rst:589 +#: ../objectstorage-monitoring.rst:168 msgid "" -"Data to retrieve from the back-end are divided in chunks in order to avoid " -"expensive API requests; this is achieved leveraging NSX APIs response paging " -"capabilities. The minimum chunk size can be specified using a configuration " -"option; the actual chunk size is then determined dynamically according to: " -"total number of resources to retrieve, interval between two synchronization " -"task runs, minimum delay between two subsequent requests to the NSX back-end." +"``update_stats(self, metric, amount, sample_rate=1)`` Increments the " +"supplied meter by the given amount. This is used when you need to add or " +"subtract more that one from a counter, like incrementing \"suffix.hashes\" " +"by the number of computed hashes in the object replicator." msgstr "" -# #-#-#-#-# database.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -# #-#-#-#-# telemetry-data-collection.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -#: ../database.rst:8 ../telemetry-data-collection.rst:1009 -msgid "Database" -msgstr "" - -#: ../compute-service-groups.rst:21 -msgid "Database ServiceGroup driver" -msgstr "" - -#: ../telemetry-data-collection.rst:988 -msgid "Database dispatcher" -msgstr "" - -#: ../objectstorage_replication.rst:43 ../objectstorage_replication.rst:49 -msgid "Database replication" -msgstr "" - -#: ../objectstorage_replication.rst:50 +#: ../objectstorage-monitoring.rst:174 msgid "" -"Database replication completes a low-cost hash comparison to determine " -"whether two replicas already match. Normally, this check can quickly verify " -"that most databases in the system are already synchronized. If the hashes " -"differ, the replicator synchronizes the databases by sharing records added " -"since the last synchronization point." +"``increment(self, metric, sample_rate=1)`` Increments the given counter " +"meter by one." msgstr "" -#: ../dashboard_sessions.rst:90 +#: ../objectstorage-monitoring.rst:177 msgid "" -"Database-backed sessions are scalable, persistent, and can be made high-" -"concurrency and highly-available." +"``decrement(self, metric, sample_rate=1)`` Lowers the given counter meter by " +"one." msgstr "" -#: ../database.rst:255 -msgid "Datastore name" -msgstr "" - -#: ../database.rst:256 -msgid "Datastore version" -msgstr "" - -#: ../networking_introduction.rst:343 +#: ../objectstorage-monitoring.rst:180 msgid "" -"Dead Peer Detection (DPD) with hold, clear, restart, disabled, or restart-by-" -"peer actions." +"``timing(self, metric, timing_ms, sample_rate=1)`` Record that the given " +"meter took the supplied number of milliseconds." msgstr "" -#: ../identity_troubleshoot.rst:20 -msgid "Debug PKI middleware" -msgstr "" - -#: ../identity_troubleshoot.rst:142 -msgid "Debug signing key file errors" -msgstr "" - -#: ../compute-node-down.rst:66 +#: ../objectstorage-monitoring.rst:183 msgid "" -"Decide which compute host the affected VM should be moved to, and run this " -"database command to move the VM to the new host:" +"``timing_since(self, metric, orig_time, sample_rate=1)`` Convenience method " +"to record a timing meter whose value is \"now\" minus an existing timestamp." msgstr "" -#: ../networking_adv-features.rst:129 -msgid "Default Value" -msgstr "" - -#: ../keystone_certificates_for_pki.rst:50 -msgid "Default is ``2048``." -msgstr "" - -#: ../keystone_certificates_for_pki.rst:53 -msgid "Default is ``3650``." -msgstr "" - -#: ../networking_multi-dhcp-agents.rst:316 -msgid "Default scheduling." -msgstr "" - -#: ../networking_adv-features.rst:607 -msgid "Default value" -msgstr "" - -#: ../blockstorage-driver-filter-weighing.rst:88 +#: ../objectstorage-monitoring.rst:187 msgid "" -"Default values for the filter and goodness functions will be used for each " -"back end if you do not define them yourself. If complete control is desired " -"then a filter and goodness function should be defined for each of the back " -"ends in the :file:`cinder.conf` file." +"Note that these logging methods may safely be called anywhere you have a " +"logger object. If StatsD logging has not been configured, the methods are no-" +"ops. This avoids messy conditional logic each place a meter is recorded. " +"These example usages show the new logging methods:" msgstr "" -#: ../blockstorage_volume_number_weigher.rst:53 -msgid "Define a volume type in Block Storage::" -msgstr "" - -#: ../compute-images-instances.rst:179 -msgid "Define roles or policies in the :file:`policy.json` file::" -msgstr "" - -#: ../keystone_integrate_with_ldap.rst:59 -msgid "Define the destination LDAP server in the :file:`keystone.conf` file:" -msgstr "" - -#: ../keystone_integrate_identity_backend_ldap.rst:118 +#: ../objectstorage-monitoring.rst:238 msgid "" -"Define the destination LDAP server in the :file:`/etc/keystone/domains/" -"keystone.DOMAIN_NAME.conf` file. For example:" +"The development team of StatsD wanted to use the `pystatsd `__ client library (not to be confused with a `similar-" +"looking project `__ also hosted on " +"GitHub), but the released version on PyPI was missing two desired features " +"the latest version in GitHub had: the ability to configure a meters prefix " +"in the client object and a convenience method for sending timing data " +"between \"now\" and a \"start\" timestamp you already have. So they just " +"implemented a simple StatsD client library from scratch with the same " +"interface. This has the nice fringe benefit of not introducing another " +"external library dependency into Object Storage." msgstr "" -#: ../compute-images-instances.rst:249 +#: ../objectstorage-troubleshoot.rst:0 msgid "" -"Define which roles or policies can manage which properties in a property " -"protections configuration file. For example::" +"**Description of configuration options for [drive-audit] in drive-audit." +"conf**" msgstr "" -#: ../keystone_use_trusts.rst:35 +#: ../objectstorage-troubleshoot.rst:3 +msgid "Troubleshoot Object Storage" +msgstr "" + +#: ../objectstorage-troubleshoot.rst:5 msgid "" -"Defines whether or not the delegation is recursive. If it is recursive, " -"defines the delegation chain length." -msgstr "" - -#: ../blockstorage-driver-filter-weighing.rst:69 -msgid "Defining your own filter and goodness functions" -msgstr "" - -#: ../blockstorage-consistency-groups.rst:90 -msgid "Delete a consistency group." -msgstr "" - -#: ../networking_config-agents.rst:512 -msgid "Delete a given agent. Consider disabling the agent before deletion." -msgstr "" - -#: ../identity_concepts.rst:343 -msgid "Delete a group" -msgstr "" - -#: ../blockstorage-consistency-groups.rst:88 -msgid "Delete a snapshot of a consistency group." -msgstr "" - -#: ../compute-manage-volumes.rst:38 -msgid "Delete a specific flavor" -msgstr "" - -#: ../blockstorage_backup_disks.rst:203 -msgid "Delete the partition table::" -msgstr "" - -#: ../networking_adv-features.rst:509 -msgid "Deletes a QoS queue." -msgstr "" - -#: ../networking_adv-features.rst:824 -msgid "Deletes a metering label rule." -msgstr "" - -#: ../networking_adv-features.rst:798 -msgid "Deletes a metering label." -msgstr "" - -#: ../networking_adv-features.rst:375 -msgid "Deletes a security group rule." -msgstr "" - -#: ../networking_adv-features.rst:379 -msgid "Deletes a security group." -msgstr "" - -#: ../networking_adv-features.rst:288 -msgid "Deletes the floating IP address." -msgstr "" - -#: ../networking_adv-features.rst:300 -msgid "Deletes the router." -msgstr "" - -#: ../objectstorage_account_reaper.rst:34 -msgid "" -"Deleting an account is simple. For each account container, all objects are " -"deleted and then the container is deleted. Deletion requests that fail will " -"not stop the overall process but will cause the overall process to fail " -"eventually (for example, if an object delete times out, you will not be able " -"to delete the container or the account). The account reaper keeps trying to " -"delete an account until it is empty, at which point the database reclaim " -"process within the db\\_replicator will remove the database files." -msgstr "" - -#: ../telemetry-measurements.rst:741 -msgid "Deletion of the snapshot" -msgstr "" - -#: ../telemetry-measurements.rst:720 -msgid "Deletion of the volume" -msgstr "" - -# #-#-#-#-# telemetry-data-collection.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -# #-#-#-#-# telemetry-measurements.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -#: ../telemetry-data-collection.rst:451 ../telemetry-data-collection.rst:621 -#: ../telemetry-measurements.rst:35 ../telemetry-measurements.rst:355 -#: ../telemetry-measurements.rst:676 ../telemetry-measurements.rst:679 -#: ../telemetry-measurements.rst:682 ../telemetry-measurements.rst:685 -#: ../telemetry-measurements.rst:688 ../telemetry-measurements.rst:717 -#: ../telemetry-measurements.rst:720 ../telemetry-measurements.rst:723 -#: ../telemetry-measurements.rst:727 ../telemetry-measurements.rst:730 -#: ../telemetry-measurements.rst:734 ../telemetry-measurements.rst:738 -#: ../telemetry-measurements.rst:741 ../telemetry-measurements.rst:765 -#: ../telemetry-measurements.rst:768 ../telemetry-measurements.rst:771 -#: ../telemetry-measurements.rst:843 ../telemetry-measurements.rst:846 -#: ../telemetry-measurements.rst:849 ../telemetry-measurements.rst:852 -#: ../telemetry-measurements.rst:855 ../telemetry-measurements.rst:858 -#: ../telemetry-measurements.rst:861 ../telemetry-measurements.rst:864 -#: ../telemetry-measurements.rst:867 ../telemetry-measurements.rst:870 -#: ../telemetry-measurements.rst:873 ../telemetry-measurements.rst:876 -#: ../telemetry-measurements.rst:879 ../telemetry-measurements.rst:882 -#: ../telemetry-measurements.rst:885 ../telemetry-measurements.rst:888 -#: ../telemetry-measurements.rst:891 ../telemetry-measurements.rst:896 -#: ../telemetry-measurements.rst:900 ../telemetry-measurements.rst:917 -#: ../telemetry-measurements.rst:921 ../telemetry-measurements.rst:927 -#: ../telemetry-measurements.rst:931 ../telemetry-measurements.rst:937 -#: ../telemetry-measurements.rst:940 ../telemetry-measurements.rst:946 -#: ../telemetry-measurements.rst:950 ../telemetry-measurements.rst:957 -#: ../telemetry-measurements.rst:960 ../telemetry-measurements.rst:963 -#: ../telemetry-measurements.rst:1097 ../telemetry-measurements.rst:1101 -#: ../telemetry-measurements.rst:1105 ../telemetry-measurements.rst:1109 -#: ../telemetry-measurements.rst:1113 ../telemetry-measurements.rst:1117 -#: ../telemetry-measurements.rst:1121 ../telemetry-measurements.rst:1126 -#: ../telemetry-measurements.rst:1152 ../telemetry-measurements.rst:1156 -#: ../telemetry-measurements.rst:1160 ../telemetry-measurements.rst:1165 -#: ../telemetry-measurements.rst:1174 ../telemetry-measurements.rst:1179 -#: ../telemetry-measurements.rst:1188 ../telemetry-measurements.rst:1192 -#: ../telemetry-measurements.rst:1216 ../telemetry-measurements.rst:1220 -#: ../telemetry-measurements.rst:1224 ../telemetry-measurements.rst:1229 -#: ../telemetry-measurements.rst:1238 ../telemetry-measurements.rst:1243 -#: ../telemetry-measurements.rst:1257 ../telemetry-measurements.rst:1260 -#: ../telemetry-measurements.rst:1263 ../telemetry-measurements.rst:1266 -#: ../telemetry-measurements.rst:1269 ../telemetry-measurements.rst:1283 -#: ../telemetry-measurements.rst:1288 ../telemetry-measurements.rst:1292 -msgid "Delta" -msgstr "" - -#: ../compute-manage-volumes.rst:5 -msgid "" -"Depending on the setup of your cloud provider, they may give you an endpoint " -"to use to manage volumes, or there may be an extension under the covers. In " -"either case, you can use the ``nova`` CLI to manage volumes." -msgstr "" - -# #-#-#-#-# compute-flavors.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -# #-#-#-#-# compute-manage-volumes.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -# #-#-#-#-# compute-networking-nova.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -# #-#-#-#-# compute-remote-console-access.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -# #-#-#-#-# compute-security.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -# #-#-#-#-# database.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -# #-#-#-#-# networking_adv-features.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -# #-#-#-#-# networking_arch.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -# #-#-#-#-# networking_introduction.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -# #-#-#-#-# networking_multi-dhcp-agents.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -# #-#-#-#-# objectstorage-troubleshoot.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -# #-#-#-#-# telemetry-measurements.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -#: ../compute-flavors.rst:37 ../compute-manage-volumes.rst:14 -#: ../compute-networking-nova.rst:310 ../compute-networking-nova.rst:508 -#: ../compute-remote-console-access.rst:36 -#: ../compute-remote-console-access.rst:153 ../compute-security.rst:104 -#: ../database.rst:107 ../database.rst:145 ../networking_adv-features.rst:47 -#: ../networking_adv-features.rst:130 ../networking_adv-features.rst:693 -#: ../networking_arch.rst:29 ../networking_introduction.rst:29 -#: ../networking_introduction.rst:122 ../networking_multi-dhcp-agents.rst:40 -#: ../objectstorage-troubleshoot.rst:62 ../telemetry-measurements.rst:31 -msgid "Description" -msgstr "" - -#: ../compute-networking-nova.rst:0 -msgid "Description of IPv6 configuration options" -msgstr "" - -#: ../compute-networking-nova.rst:0 -msgid "Description of metadata configuration options" -msgstr "" - -#: ../compute-manage-volumes.rst:22 -msgid "Detach a volume from a server." -msgstr "" - -#: ../compute_arch.rst:347 -msgid "Detach volumes" -msgstr "" - -#: ../telemetry-measurements.rst:734 -msgid "Detaching the v\\ olume from an i\\ nstance" -msgstr "" - -#: ../networking_introduction.rst:328 -msgid "" -"Details for the site-to-site IPsec connection, including the peer CIDRs, " -"MTU, authentication mode, peer address, DPD settings, and status." -msgstr "" - -#: ../objectstorage_features.rst:40 -msgid "Detect drive failures preempting data corruption." -msgstr "" - -#: ../objectstorage-troubleshoot.rst:49 -msgid "Detect failed drives" -msgstr "" - -#: ../orchestration-stack-domain-users.rst:16 -msgid "" -"Detect signal completion of some action, typically configuration of software " -"on a VM after it is booted (because OpenStack Compute moves the state of a " -"VM to \"Active\" as soon as it spawns it, not when Orchestration has fully " -"configured it)." -msgstr "" - -#: ../compute-security.rst:157 -msgid "" -"Determine whether insecure SSL connections are accepted for Compute metadata " -"server requests. The default value is ``False``::" -msgstr "" - -#: ../telemetry-system-architecture.rst:47 -msgid "" -"Determines when alarms fire due to the associated statistic trend crossing a " -"threshold over a sliding time window." -msgstr "" - -#: ../networking_adv-features.rst:707 -msgid "" -"Determines whether or not the matched packets will allowed to cross the " -"router." -msgstr "" - -#: ../objectstorage_characteristics.rst:38 -msgid "" -"Developers can either write directly to the Swift API or use one of the many " -"client libraries that exist for all of the popular programming languages, " -"such as Java, Python, Ruby, and C#. Amazon S3 and RackSpace Cloud Files " -"users should be very familiar with Object Storage. Users new to object " -"storage systems will have to adjust to a different approach and mindset than " -"those required for a traditional filesystem." -msgstr "" - -#: ../objectstorage_characteristics.rst:14 -msgid "" -"Developers interact with the object storage system through a RESTful HTTP " -"API." -msgstr "" - -#: ../networking_multi-dhcp-agents.rst:279 -msgid "" -"Different types of agents show different details. The following output shows " -"information for a Linux bridge agent:" -msgstr "" - -#: ../objectstorage_features.rst:44 -msgid "Direct object access" -msgstr "" - -#: ../objectstorage-troubleshoot.rst:64 -msgid "Directory devices are mounted under" -msgstr "" - -#: ../objectstorage-troubleshoot.rst:84 -msgid "Directory where stats for a few items will be stored" -msgstr "" - -#: ../compute-live-migration-usage.rst:112 -msgid "Disabled Reason" -msgstr "" - -#: ../keystone_token-binding.rst:35 -msgid "Disables token bind checking." -msgstr "" - -#: ../compute-networking-nova.rst:755 -msgid "" -"Disassociate the network from the project using the :command:`scrub` " -"command, with the project ID as the final parameter:" -msgstr "" - -#: ../networking_adv-features.rst:284 -msgid "Disassociates a floating IP address." -msgstr "" - -#: ../telemetry-measurements.rst:37 -msgid "" -"Discrete items (floating IPs, image uploads) and fluctuating values (disk I/" -"O)" -msgstr "" - -#: ../compute-flavors.rst:44 -msgid "Disk" -msgstr "" - -#: ../ts-eql-volume-size.rst:110 -msgid "Disk Format" -msgstr "" - -#: ../compute-images-instances.rst:6 -msgid "" -"Disk images provide templates for virtual machine file systems. The Image " -"service controls storage and management of images." -msgstr "" - -#: ../compute-flavors.rst:157 -msgid "Disk tuning" -msgstr "" - -#: ../networking_use.rst:165 -msgid "Displays all ports and IPs allocated on a network." -msgstr "" - -#: ../compute-node-down.rst:207 -msgid "" -"Do not add any extra steps to this procedure, or perform the steps out of " -"order." -msgstr "" - -#: ../compute-node-down.rst:290 -msgid "" -"Do not add the entry for the SAN's disks to the cinder-volume's :file:" -"`fstab` file." -msgstr "" - -#: ../networking_config-agents.rst:188 -msgid "" -"Do not configure or use neutron-l3-agent if you use one of these plug-ins." -msgstr "" - -#: ../compute-remote-console-access.rst:112 -msgid "" -"Do not confuse the ``nova-consoleauth`` shared service with ``nova-" -"console``, which is a XenAPI-specific service that most recent VNC proxy " -"architectures do not use." -msgstr "" - -#: ../telemetry-data-collection.rst:417 -msgid "" -"Do not deploy both the IPMI agent and the Bare metal service on one compute " -"node. If ``conductor.send_sensor_data`` is set, this misconfiguration causes " -"duplicated IPMI sensor samples." -msgstr "" - -#: ../compute-node-down.rst:336 -msgid "Do not forget the ``-r`` flag. Otherwise, you will close all sessions." -msgstr "" - -#: ../networking_config-agents.rst:211 -msgid "" -"Do not manually configure an IP address on the NIC connected to the external " -"network for the node running neutron-l3-agent. Rather, you must have a range " -"of IP addresses from the external network that can be used by OpenStack " -"Networking for routers that uplink to the external network. This range must " -"be large enough to have an IP address for each router in the deployment, as " -"well as each floating IP." -msgstr "" - -#: ../networking_use.rst:313 -msgid "" -"Does not implement Networking security groups, you can configure security " -"group rules by using the :command:`nova secgroup-add-rule` or :command:`euca-" -"authorize` command. These :command:`nova` commands enable ``ping`` and " -"``ssh`` access to your VMs." -msgstr "" - -#: ../identity_concepts.rst:26 -msgid "Domain" -msgstr "" - -#: ../objectstorage_components.rst:277 -msgid "Download" -msgstr "" - -#: ../networking_config-agents.rst:428 -msgid "Download the OpenStack Networking code from the repository:" -msgstr "" - -#: ../objectstorage_features.rst:39 -msgid "Drive auditing" +"For Object Storage, everything is logged in :file:`/var/log/syslog` (or :" +"file:`messages` on some distros). Several settings enable further " +"customization of logging, such as ``log_name``, ``log_facility``, and " +"``log_level``, within the object server configuration files." msgstr "" #: ../objectstorage-troubleshoot.rst:11 msgid "Drive failure" msgstr "" -#: ../blockstorage-driver-filter-weighing.rst:246 -msgid "Driver filter and weigher usage examples" -msgstr "" - -#: ../blockstorage_over_subscription.rst:50 -msgid "Drivers can report the following capabilities for a back end or a pool:" -msgstr "" - -#: ../telemetry-measurements.rst:995 -msgid "Drops received on port" -msgstr "" - -#: ../telemetry-measurements.rst:998 -msgid "Drops transmitt\\ ed on port" -msgstr "" - -#: ../ts-duplicate-3par-host.rst:6 -msgid "Duplicate 3PAR host" -msgstr "" - -#: ../telemetry-measurements.rst:1033 -msgid "Duration of flow" -msgstr "" - -#: ../telemetry-measurements.rst:1038 -msgid "Duration of flow in nanoseconds" -msgstr "" - -#: ../telemetry-measurements.rst:1035 -msgid "Duration of flow in seconds" -msgstr "" - -#: ../telemetry-measurements.rst:1021 -msgid "Duration of tab\\ le" -msgstr "" - -# #-#-#-#-# keystone_integrate_assignment_backend_ldap.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -# #-#-#-#-# keystone_integrate_identity_backend_ldap.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -# #-#-#-#-# keystone_integrate_with_ldap.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -#: ../keystone_integrate_assignment_backend_ldap.rst:85 -#: ../keystone_integrate_identity_backend_ldap.rst:73 -#: ../keystone_integrate_identity_backend_ldap.rst:177 -#: ../keystone_integrate_identity_backend_ldap.rst:252 -#: ../keystone_integrate_with_ldap.rst:166 +#: ../objectstorage-troubleshoot.rst:13 msgid "" -"During service restart, authentication and authorization are unavailable." +"In the event that a drive has failed, the first step is to make sure the " +"drive is unmounted. This will make it easier for Object Storage to work " +"around the failure until it has been resolved. If the drive is going to be " +"replaced immediately, then it is just best to replace the drive, format it, " +"remount it, and let replication fill it up." msgstr "" -#: ../compute_arch.rst:194 -msgid "EC2 compatibility API" -msgstr "" - -#: ../compute-images-instances.rst:133 -msgid "ESX/ESXi or vCenter Server target system." -msgstr "" - -#: ../identity_service_api_protection.rst:12 +#: ../objectstorage-troubleshoot.rst:19 msgid "" -"Each Identity API v3 call has a line in the policy file that dictates which " -"level of governance of access applies." +"If you cannot replace the drive immediately, then it is best to leave it " +"unmounted, and remove the drive from the ring. This will allow all the " +"replicas that were on that drive to be replicated elsewhere until the drive " +"is replaced. Once the drive is replaced, it can be re-added to the ring." msgstr "" -#: ../compute-networking-nova.rst:776 +#: ../objectstorage-troubleshoot.rst:25 msgid "" -"Each VIP represents a separate network with its own IP block. Every network " -"mode has its own set of changes regarding multinic usage:" +"You can look at error messages in :file:`/var/log/kern.log` for hints of " +"drive failure." msgstr "" -#: ../objectstorage_components.rst:153 +#: ../objectstorage-troubleshoot.rst:29 +msgid "Server failure" +msgstr "" + +#: ../objectstorage-troubleshoot.rst:31 msgid "" -"Each account and container is an individual SQLite database that is " -"distributed across the cluster. An account database contains the list of " -"containers in that account. A container database contains the list of " -"objects in that container." +"If a server is having hardware issues, it is a good idea to make sure the " +"Object Storage services are not running. This will allow Object Storage to " +"work around the failure while you troubleshoot." msgstr "" -#: ../identity_service_api_protection.rst:40 -msgid "Each component of a match statement uses this format:" -msgstr "" - -#: ../objectstorage_ringbuilder.rst:164 +#: ../objectstorage-troubleshoot.rst:35 msgid "" -"Each device is also assigned a random tiebreaker value that is used when two " -"devices desire the same number of partitions. This tiebreaker is not stored " -"on disk anywhere, and so two different rings created with the same " -"parameters will have different partition assignments. For repeatable " -"partition assignments, ``RingBuilder.rebalance()`` takes an optional seed " -"value that seeds the Python pseudo-random number generator." +"If the server just needs a reboot, or a small amount of work that should " +"only last a couple of hours, then it is probably best to let Object Storage " +"work around the failure and get the machine fixed and back online. When the " +"machine comes back online, replication will make sure that anything that is " +"missing during the downtime will get updated." msgstr "" -#: ../telemetry-events.rst:117 -msgid "Each event definition is a mapping with two keys:" -msgstr "" - -#: ../identity_concepts.rst:316 +#: ../objectstorage-troubleshoot.rst:41 msgid "" -"Each has a pluggable back end that allow different ways to use the " -"particular service. Most support standard back ends like LDAP or SQL." +"If the server has more serious issues, then it is probably best to remove " +"all of the server's devices from the ring. Once the server has been repaired " +"and is back online, the server's devices can be added back into the ring. It " +"is important that the devices are reformatted before putting them back into " +"the ring as it is likely to be responsible for a different set of partitions " +"than before." msgstr "" -#: ../compute-networking-nova.rst:796 +#: ../objectstorage-troubleshoot.rst:49 +msgid "Detect failed drives" +msgstr "" + +#: ../objectstorage-troubleshoot.rst:51 msgid "" -"Each new instance will now receive two IP addresses from their respective " -"DHCP servers:" +"It has been our experience that when a drive is about to fail, error " +"messages appear in :file:`/var/log/kern.log`. There is a script called " +"``swift-drive-audit`` that can be run via cron to watch for bad drives. If " +"errors are detected, it will unmount the bad drive, so that Object Storage " +"can work around it. The script takes a configuration file with the following " +"settings:" msgstr "" -#: ../telemetry-data-collection.rst:493 +#: ../objectstorage-troubleshoot.rst:63 +msgid "``device_dir = /srv/node``" +msgstr "" + +#: ../objectstorage-troubleshoot.rst:64 +msgid "Directory devices are mounted under" +msgstr "" + +#: ../objectstorage-troubleshoot.rst:65 +msgid "``error_limit = 1``" +msgstr "" + +#: ../objectstorage-troubleshoot.rst:66 +msgid "Number of errors to find before a device is unmounted" +msgstr "" + +#: ../objectstorage-troubleshoot.rst:67 +msgid "``log_address = /dev/log``" +msgstr "" + +#: ../objectstorage-troubleshoot.rst:68 +msgid "Location where syslog sends the logs to" +msgstr "" + +#: ../objectstorage-troubleshoot.rst:69 +msgid "``log_facility = LOG_LOCAL0``" +msgstr "" + +#: ../objectstorage-troubleshoot.rst:70 +msgid "Syslog log facility" +msgstr "" + +#: ../objectstorage-troubleshoot.rst:71 +msgid "``log_file_pattern = /var/log/kern.*[!.][!g][!z]``" +msgstr "" + +#: ../objectstorage-troubleshoot.rst:72 msgid "" -"Each source configuration encapsulates name matching, polling interval " -"determination, optional resource enumeration or discovery, and mapping to " -"one or more sinks for publication." +"Location of the log file with globbing pattern to check against device " +"errors locate device blocks with errors in the log file" msgstr "" -#: ../networking_adv-features.rst:681 +#: ../objectstorage-troubleshoot.rst:74 +msgid "``log_level = INFO``" +msgstr "" + +#: ../objectstorage-troubleshoot.rst:75 +msgid "Logging level" +msgstr "" + +#: ../objectstorage-troubleshoot.rst:76 +msgid "``log_max_line_length = 0``" +msgstr "" + +#: ../objectstorage-troubleshoot.rst:77 msgid "" -"Each tenant router has a set of router rules associated with it. Each router " -"rule has the attributes in this table. Router rules and their attributes can " -"be set using the :command:`neutron router-update` command, through the " -"horizon interface or the Networking API." +"Caps the length of log lines to the value given; no limit if set to 0, the " +"default." msgstr "" -#: ../networking_config-identity.rst:157 +#: ../objectstorage-troubleshoot.rst:79 +msgid "``log_to_console = False``" +msgstr "" + +#: ../objectstorage-troubleshoot.rst:80 ../objectstorage-troubleshoot.rst:86 +#: ../objectstorage-troubleshoot.rst:88 +msgid "No help text available for this option." +msgstr "" + +#: ../objectstorage-troubleshoot.rst:81 +msgid "``minutes = 60``" +msgstr "" + +#: ../objectstorage-troubleshoot.rst:82 +msgid "Number of minutes to look back in :file:`/var/log/kern.log`" +msgstr "" + +#: ../objectstorage-troubleshoot.rst:83 +msgid "``recon_cache_path = /var/cache/swift``" +msgstr "" + +#: ../objectstorage-troubleshoot.rst:84 +msgid "Directory where stats for a few items will be stored" +msgstr "" + +#: ../objectstorage-troubleshoot.rst:85 +msgid "``regex_pattern_1 = \\berror\\b.*\\b(dm-[0-9]{1,2}\\d?)\\b``" +msgstr "" + +#: ../objectstorage-troubleshoot.rst:87 +msgid "``unmount_failed_device = True``" +msgstr "" + +#: ../objectstorage-troubleshoot.rst:92 msgid "" -"Each time you provision or de-provision a VM in Compute, nova-\\* services " -"communicate with Networking using the standard API. For this to happen, you " -"must configure the following items in the :file:`nova.conf` file (used by " -"each nova-compute and nova-api instance)." -msgstr "" - -#: ../telemetry-events.rst:131 -msgid "Each trait definition is a mapping with the following keys:" -msgstr "" - -#: ../identity_user_crud.rst:22 -msgid "Each user can then change their own password with a HTTP PATCH::" -msgstr "" - -#: ../networking_adv-features.rst:448 -msgid "" -"Each vendor can choose to implement additional API extensions to the core " -"API. This section describes the extensions for each plug-in." -msgstr "" - -#: ../compute_arch.rst:119 -msgid "" -"Earlier versions of OpenStack used the term ``project`` instead of " -"``tenant``. Because of this legacy terminology, some command-line tools use " -"``--project_id`` where you would normally expect to enter a tenant ID." -msgstr "" - -#: ../objectstorage_features.rst:29 -msgid "Easily add capacity (unlike RAID resize)" -msgstr "" - -#: ../compute-networking-nova.rst:817 -msgid "Edit the :file:`/etc/network/interfaces` file:" -msgstr "" - -#: ../networking_config-plugins.rst:14 -msgid "Edit the :file:`/etc/neutron/neutron.conf` file and add this line:" -msgstr "" - -#: ../networking_config-plugins.rst:63 -msgid "" -"Edit the :file:`/etc/neutron/neutron.conf` file and set the following option:" -msgstr "" - -#: ../networking_config-plugins.rst:107 ../networking_config-plugins.rst:225 -msgid "Edit the :file:`/etc/neutron/neutron.conf` file and set this line:" -msgstr "" - -#: ../networking_config-plugins.rst:27 -msgid "" -"Edit the :file:`/etc/neutron/plugins/bigswitch/restproxy.ini` file for the " -"plug-in and specify a comma-separated list of controller\\_ip:port pairs:" -msgstr "" - -#: ../networking_config-plugins.rst:70 -msgid "" -"Edit the :file:`/etc/neutron/plugins/brocade/brocade.ini` file for the " -"Brocade plug-in and specify the admin user name, password, and IP address of " -"the Brocade switch:" -msgstr "" - -#: ../compute-default-ports.rst:18 -msgid "" -"Edit the :file:`/etc/sysconfig/iptables` file, to add an INPUT rule that " -"allows TCP traffic on ports from ``5900`` to ``5999``. Make sure the new " -"rule appears before any INPUT rules that REJECT traffic:" -msgstr "" - -#: ../networking_config-plugins.rst:231 -msgid "" -"Edit the [PLUMgridDirector] section in the :file:`/etc/neutron/plugins/" -"plumgrid/plumgrid.ini` file and specify the IP address, port, admin user " -"name, and password of the PLUMgrid Director:" -msgstr "" - -#: ../objectstorage_features.rst:30 -msgid "Elastic data scaling with ease ." -msgstr "" - -#: ../compute-flavors.rst:37 -msgid "Element" +"This script has only been tested on Ubuntu 10.04; use with caution on other " +"operating systems in production." msgstr "" #: ../objectstorage-troubleshoot.rst:96 msgid "Emergency recovery of ring builder files" msgstr "" -#: ../compute-networking-nova.rst:622 -msgid "Enable IP forwarding" -msgstr "" - -#: ../blockstorage_glusterfs_backend.rst:70 +#: ../objectstorage-troubleshoot.rst:98 msgid "" -"Enable client connections from unprivileged ports. To do this, add the " -"following line to :file:`/etc/glusterfs/glusterd.vol`::" +"You should always keep a backup of swift ring builder files. However, if an " +"emergency occurs, this procedure may assist in returning your cluster to an " +"operational state." msgstr "" -#: ../objectstorage_features.rst:45 -msgid "Enable direct browser access to content, such as for a control panel." -msgstr "" - -#: ../keystone_integrate_identity_backend_ldap.rst:88 -msgid "Enable domain-specific drivers:" -msgstr "" - -#: ../blockstorage-driver-filter-weighing.rst:33 -msgid "Enable driver filter and weighing" -msgstr "" - -#: ../networking_config-agents.rst:397 -msgid "Enable load balancing in the Project section of the dashboard." -msgstr "" - -#: ../blockstorage_multi_backend.rst:26 -msgid "Enable multiple-storage back ends" -msgstr "" - -#: ../compute-networking-nova.rst:535 -msgid "Enable ping and SSH on VMs" -msgstr "" - -#: ../networking_use.rst:294 -msgid "Enable ping and SSH on VMs (security groups)" -msgstr "" - -#: ../compute-networking-nova.rst:548 -msgid "Enable ping and SSH with :command:`nova` commands:" -msgstr "" - -#: ../compute-networking-nova.rst:555 -msgid "Enable ping and SSH with ``euca2ools``:" -msgstr "" - -#: ../compute-security.rst:47 +#: ../objectstorage-troubleshoot.rst:102 msgid "" -"Enable scheduling support for trusted compute pools by adding these lines to " -"the ``DEFAULT`` section of the :file:`/etc/nova/nova.conf` file:" +"Using existing swift tools, there is no way to recover a builder file from " +"a :file:`ring.gz` file. However, if you have a knowledge of Python, it is " +"possible to construct a builder file that is pretty close to the one you " +"have lost." msgstr "" -#: ../networking_introduction.rst:174 -msgid "Enable the FWaaS plug-in in the :file:`/etc/neutron/neutron.conf` file:" -msgstr "" - -#: ../networking_config-agents.rst:365 +#: ../objectstorage-troubleshoot.rst:109 msgid "" -"Enable the HAProxy load balancer in the :file:`/etc/neutron/lbaas_agent.ini` " -"file:" +"This procedure is a last-resort for emergency circumstances. It requires " +"knowledge of the swift python code and may not succeed." msgstr "" -#: ../networking_config-agents.rst:335 +#: ../objectstorage-troubleshoot.rst:112 +msgid "Load the ring and a new ringbuilder object in a Python REPL:" +msgstr "" + +#: ../objectstorage-troubleshoot.rst:120 +msgid "Start copying the data we have in the ring into the builder:" +msgstr "" + +#: ../objectstorage-troubleshoot.rst:144 msgid "" -"Enable the HAProxy plug-in by using the ``service_provider`` option in the :" -"file:`/etc/neutron/neutron.conf` file:" +"For ``min_part_hours`` you either have to remember what the value you used " +"was, or just make up a new one:" msgstr "" -#: ../compute-security.rst:153 -msgid "Enable the HTTPS protocol::" -msgstr "" - -#: ../keystone_integrate_identity_backend_ldap.rst:19 +#: ../objectstorage-troubleshoot.rst:151 msgid "" -"Enable the LDAP Identity driver in the ``keystone.conf`` file. This allows " -"LDAP as an identity back end:" +"Validate the builder. If this raises an exception, check your previous code:" msgstr "" -#: ../keystone_integrate_identity_backend_ldap.rst:80 -msgid "Enable the LDAP driver:" -msgstr "" - -#: ../networking_config-agents.rst:376 -msgid "Enable the Open vSwitch LBaaS driver:" -msgstr "" - -#: ../keystone_integrate_assignment_backend_ldap.rst:29 +#: ../objectstorage-troubleshoot.rst:158 msgid "" -"Enable the assignment driver. In the ``[assignment]`` section, set the " -"``driver`` configuration key to ``keystone.assignment.backends.sql." -"Assignment``:" +"After it validates, save the builder and create a new ``account.builder``:" msgstr "" -#: ../networking_config-agents.rst:351 +#: ../objectstorage-troubleshoot.rst:167 msgid "" -"Enable the load-balancing plug-in by using the ``service_plugins`` option in " -"the :file:`/etc/neutron/neutron.conf` file:" +"You should now have a file called :file:`account.builder` in the current " +"working directory. Run :command:`swift-ring-builder account.builder " +"write_ring` and compare the new :file:`account.ring.gz` to the :file:" +"`account.ring.gz` that you started from. They probably are not byte-for-byte " +"identical, but if you load them in a REPL and their ``_replica2part2dev_id`` " +"and ``devs`` attributes are the same (or nearly so), then you are in good " +"shape." msgstr "" -#: ../networking_introduction.rst:202 +#: ../objectstorage-troubleshoot.rst:175 msgid "" -"Enable the option in the :file:`/usr/share/openstack-dashboard/" -"openstack_dashboard/local/local_settings.py` file, which is typically " -"located on the controller node:" -msgstr "" - -#: ../dashboard_sessions.rst:181 -msgid "" -"Enable this hybrid setting by configuring both your database and cache, as " -"discussed previously. Then, set the following value::" -msgstr "" - -#: ../blockstorage_volume_number_weigher.rst:17 -msgid "Enable volume number weigher" -msgstr "" - -#: ../dashboard_sessions.rst:55 ../dashboard_sessions.rst:75 -msgid "Enabled by::" -msgstr "" - -# #-#-#-#-# keystone_integrate_assignment_backend_ldap.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -# #-#-#-#-# keystone_integrate_identity_backend_ldap.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -#: ../keystone_integrate_assignment_backend_ldap.rst:147 -#: ../keystone_integrate_identity_backend_ldap.rst:243 -msgid "Enabled emulation" -msgstr "" - -#: ../networking_introduction.rst:75 -msgid "Enables SSL on the networking API server." -msgstr "" - -#: ../networking_introduction.rst:55 -msgid "" -"Enables advanced cloud networking use cases, such as building multi-tiered " -"web applications and enabling migration of applications to the cloud without " -"changing IP addresses." -msgstr "" - -#: ../keystone_token-binding.rst:38 -msgid "" -"Enables bind checking. If a token is bound to an unknown authentication " -"mechanism, the server ignores it. The default is this mode." -msgstr "" - -#: ../keystone_token-binding.rst:43 -msgid "" -"Enables bind checking. If a token is bound to an unknown authentication " -"mechanism, the server rejects it." -msgstr "" - -#: ../keystone_token-binding.rst:61 -msgid "" -"Enables bind checking. Requires use of X.509 as the authentication mechanism " -"for tokens:" -msgstr "" - -#: ../keystone_token-binding.rst:47 -msgid "" -"Enables bind checking. Requires use of at least authentication mechanism for " -"tokens." -msgstr "" - -#: ../keystone_token-binding.rst:51 -msgid "" -"Enables bind checking. Requires use of kerberos as the authentication " -"mechanism for tokens:" -msgstr "" - -#: ../networking_introduction.rst:62 -msgid "" -"Enables developers to extend the Networking API. Over time, the extended " -"functionality becomes part of the core Networking API." -msgstr "" - -#: ../cross_project_cors.rst:76 -msgid "Enabling CORS with PasteDeploy" -msgstr "" - -#: ../cross_project_cors.rst:32 -msgid "Enabling CORS with configuration" -msgstr "" - -#: ../compute-configuring-migrations.rst:281 -msgid "Enabling true live migration" -msgstr "" - -#: ../compute-security.rst:146 -msgid "Encrypt Compute metadata traffic" -msgstr "" - -#: ../identity_concepts.rst:32 -msgid "Endpoint" -msgstr "" - -#: ../telemetry-measurements.rst:1318 -msgid "Energy" -msgstr "" - -#: ../telemetry-data-collection.rst:273 -msgid "" -"Energy consumption meters via `Kwapi `__ " -"framework" -msgstr "" - -#: ../compute-configuring-migrations.rst:120 -msgid "" -"Ensure that ``NOVA-INST-DIR`` (set with ``state_path`` in the :file:`nova." -"conf` file) is the same on all hosts." -msgstr "" - -#: ../networking_config-agents.rst:40 -msgid "" -"Ensure that each data-forwarding node has an IP address on the management " -"network, and an IP address on the data network that is used for tunneling " -"data traffic. For full details on configuring your forwarding node, see the " -"``NSX Administrator Guide``." -msgstr "" - -#: ../compute-configuring-migrations.rst:140 -msgid "" -"Ensure that the UID and GID of your Compute and libvirt users are identical " -"between each of your servers. This ensures that the permissions on the NFS " -"mount works correctly." -msgstr "" - -#: ../networking_multi-dhcp-agents.rst:147 -msgid "" -"Ensure that the following environment variables are set. These are used by " -"the various clients to access the Identity service." -msgstr "" - -#: ../compute-configuring-migrations.rst:188 -msgid "Ensure that you can mount the exported directory" -msgstr "" - -#: ../compute-configuring-migrations.rst:144 -msgid "" -"Ensure you can access SSH without a password and without " -"StrictHostKeyChecking between ``HostB`` and ``HostC`` as ``nova`` user (set " -"with the owner of nova-compute service). Direct access from one compute host " -"to another is needed to copy the VM file across. It is also needed to detect " -"if the source and target compute nodes share a storage subsystem." -msgstr "" - -#: ../dashboard_sessions.rst:114 -msgid "Enter ``quit`` at the ``mysql>`` prompt to exit MySQL." -msgstr "" - -#: ../dashboard_sessions.rst:102 -msgid "Enter the MySQL root user's password when prompted." -msgstr "" - -#: ../compute-flavors.rst:50 -msgid "Ephemeral" -msgstr "" - -#: ../compute_arch.rst:131 -msgid "" -"Ephemeral storage includes a root ephemeral volume and an additional " -"ephemeral volume." +"Repeat the procedure for :file:`container.ring.gz` and :file:`object.ring." +"gz`, and you might get usable builder files." msgstr "" #: ../objectstorage_EC.rst:3 @@ -6350,702 +16631,1203 @@ msgid "" "html>`_ for more details." msgstr "" -#: ../telemetry-measurements.rst:1001 -msgid "Errors received on port" -msgstr "" - -#: ../telemetry-measurements.rst:1004 -msgid "Errors transmit\\ ted on port" -msgstr "" - -#: ../networking_config-identity.rst:111 -msgid "Establish the relationship among the tenant, user, and role:" -msgstr "" - -#: ../compute_arch.rst:210 -msgid "Euca2ools" -msgstr "" - -#: ../compute-node-down.rst:12 -msgid "Evacuate instances" -msgstr "" - -#: ../telemetry.rst:7 +#: ../objectstorage_EC.rst:14 msgid "" -"Even in the cloud industry, providers must use a multi-step process for " -"billing. The required steps to bill for usage in a cloud environment are " -"metering, rating, and billing. Because the provider's requirements may be " -"far too specific for a shared solution, rating and billing solutions cannot " -"be designed in a common module that satisfies all. Providing users with " -"measurements on cloud services is required to meet the \"measured service\" " -"definition of cloud computing." +"There is no external API related to erasure coding. Create a container using " +"a Storage Policy; the interaction with the cluster is the same as any other " +"durability policy. Because support implements as a Storage Policy, you can " +"isolate all storage devices that associate with your cluster's erasure " +"coding capability. It is entirely possible to share devices between storage " +"policies, but for erasure coding it may make more sense to use not only " +"separate devices but possibly even entire nodes dedicated for erasure coding." msgstr "" -#: ../telemetry-events.rst:16 -msgid "Event configuration" -msgstr "" - -#: ../telemetry-events.rst:71 -msgid "Event conversion" -msgstr "" - -#: ../telemetry-events.rst:106 -msgid "Event definitions format" -msgstr "" - -#: ../telemetry-events.rst:55 -msgid "Event indexing" -msgstr "" - -#: ../telemetry-events.rst:31 -msgid "Event structure" -msgstr "" - -#: ../telemetry-data-collection.rst:59 -msgid "Event types" -msgstr "" - -#: ../telemetry-events.rst:3 -msgid "Events" -msgstr "" - -#: ../telemetry-events.rst:32 +#: ../objectstorage_EC.rst:24 msgid "" -"Events captured by the Telemetry module are represented by five key " -"attributes:" +"The erasure code support in Object Storage is considered beta in Kilo. Most " +"major functionality is included, but it has not been tested or validated at " +"large scale. This feature relies on `ssync` for durability. We recommend " +"deployers do extensive testing and not deploy production data using an " +"erasure code storage policy. If any bugs are found during testing, please " +"report them to https://bugs.launchpad.net/swift" msgstr "" -#: ../networking_multi-dhcp-agents.rst:183 +#: ../objectstorage_account_reaper.rst:3 +msgid "Account reaper" +msgstr "" + +#: ../objectstorage_account_reaper.rst:5 msgid "" -"Every agent that supports these extensions will register itself with the " -"neutron server when it starts up." +"In the background, the account reaper removes data from the deleted accounts." msgstr "" -#: ../identity_service_api_protection.rst:74 +#: ../objectstorage_account_reaper.rst:8 msgid "" -"Every target object has an ``id`` and a ``name`` available as ``target." -"OBJECT.id`` and ``target.OBJECT.name``. Identity retrieves other attributes " -"from the database, and the attributes vary between object types. The " -"Identity service filters out some database fields, such as user passwords." +"A reseller marks an account for deletion by issuing a ``DELETE`` request on " +"the account's storage URL. This action sets the ``status`` column of the " +"account\\_stat table in the account database and replicas to ``DELETED``, " +"marking the account's data for deletion." msgstr "" -#: ../compute-networking-nova.rst:586 +#: ../objectstorage_account_reaper.rst:13 msgid "" -"Every virtual instance is automatically assigned a private IP address. You " -"can choose to assign a public (or floating) IP address instead. OpenStack " -"Compute uses network address translation (NAT) to assign floating IPs to " -"virtual instances." +"Typically, a specific retention time or undelete are not provided. However, " +"you can set a ``delay_reaping`` value in the ``[account-reaper]`` section of " +"the :file:`account-server.conf` file to delay the actual deletion of data. " +"At this time, to undelete you have to update the account database replicas " +"directly, setting the status column to an empty string and updating the put" +"\\_timestamp to be greater than the delete\\_timestamp." msgstr "" -#: ../blockstorage_ratelimit_volume_copy_bandwidth.rst:28 +#: ../objectstorage_account_reaper.rst:23 msgid "" -"Example :file:`cinder.conf` configuration file to limit volume copy " -"bandwidth of ``lvmdriver-1`` up to 100 MiB/s:" +"It is on the development to-do list to write a utility that performs this " +"task, preferably through a REST call." msgstr "" -# #-#-#-#-# blockstorage-driver-filter-weighing.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -# #-#-#-#-# blockstorage_image_volume_cache.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -#: ../blockstorage-driver-filter-weighing.rst:56 -#: ../blockstorage_image_volume_cache.rst:36 -msgid "Example :file:`cinder.conf` configuration file::" -msgstr "" - -#: ../blockstorage-driver-filter-weighing.rst:323 +#: ../objectstorage_account_reaper.rst:26 msgid "" -"Example :file:`cinder.conf` file configuration for accessing driver specific " -"properties::" +"The account reaper runs on each account server and scans the server " +"occasionally for account databases marked for deletion. It only fires up on " +"the accounts for which the server is the primary node, so that multiple " +"account servers aren't trying to do it simultaneously. Using multiple " +"servers to delete one account might improve the deletion speed but requires " +"coordination to avoid duplication. Speed really is not a big concern with " +"data deletion, and large accounts aren't deleted often." msgstr "" -#: ../blockstorage-driver-filter-weighing.rst:299 +#: ../objectstorage_account_reaper.rst:34 msgid "" -"Example :file:`cinder.conf` file configuration for customizing both the " -"filter and goodness functions::" +"Deleting an account is simple. For each account container, all objects are " +"deleted and then the container is deleted. Deletion requests that fail will " +"not stop the overall process but will cause the overall process to fail " +"eventually (for example, if an object delete times out, you will not be able " +"to delete the container or the account). The account reaper keeps trying to " +"delete an account until it is empty, at which point the database reclaim " +"process within the db\\_replicator will remove the database files." msgstr "" -#: ../blockstorage-driver-filter-weighing.rst:251 +#: ../objectstorage_account_reaper.rst:43 msgid "" -"Example :file:`cinder.conf` file configuration for customizing the filter " -"function::" +"A persistent error state may prevent the deletion of an object or container. " +"If this happens, you will see a message in the log, for example::" msgstr "" -#: ../blockstorage-driver-filter-weighing.rst:274 +#: ../objectstorage_account_reaper.rst:48 msgid "" -"Example :file:`cinder.conf` file configuration for customizing the goodness " -"function::" +"You can control when this is logged with the ``reap_warn_after`` value in " +"the ``[account-reaper]`` section of the :file:`account-server.conf` file. " +"The default value is 30 days." msgstr "" -#: ../networking_config-plugins.rst:113 -msgid "Example :file:`neutron.conf`: file for NSX-mh integration:" +#: ../objectstorage_arch.rst:3 +msgid "Cluster architecture" msgstr "" -#: ../networking_config-plugins.rst:198 -msgid "Example :file:`nsx.ini` file:" +#: ../objectstorage_arch.rst:6 +msgid "Access tier" msgstr "" -#: ../compute-configuring-migrations.rst:108 -msgid "Example Compute installation environment" -msgstr "" - -#: ../telemetry-data-collection.rst:788 ../telemetry-data-collection.rst:821 -msgid "Example configuration::" -msgstr "" - -#: ../networking_config-identity.rst:261 -msgid "Example nova.conf (for nova-compute and nova-api)" -msgstr "" - -#: ../blockstorage_get_capabilities.rst:83 -msgid "Example of return value::" -msgstr "" - -#: ../identity_example_usage.rst:3 -msgid "Example usage" -msgstr "" - -#: ../networking_config-identity.rst:263 +#: ../objectstorage_arch.rst:7 msgid "" -"Example values for the above settings, assuming a cloud controller node " -"running Compute and Networking with an IP address of 192.168.1.2:" +"Large-scale deployments segment off an access tier, which is considered the " +"Object Storage system's central hub. The access tier fields the incoming API " +"requests from clients and moves data in and out of the system. This tier " +"consists of front-end load balancers, ssl-terminators, and authentication " +"services. It runs the (distributed) brain of the Object Storage system: the " +"proxy server processes." msgstr "" -# #-#-#-#-# database.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -# #-#-#-#-# objectstorage_ringbuilder.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -#: ../database.rst:128 ../database.rst:197 -#: ../objectstorage_ringbuilder.rst:105 -msgid "Example::" -msgstr "" - -#: ../objectstorage-monitoring.rst:5 +#: ../objectstorage_arch.rst:15 msgid "" -"Excerpted from a blog post by `Darrell Bishop `__" +"If you want to use OpenStack Identity API v3 for authentication, you have " +"the following options available in :file:`/etc/swift/dispersion.conf`: " +"``auth_version``, ``user_domain_name``, ``project_domain_name``, and " +"``project_name``." msgstr "" -#: ../telemetry-measurements.rst:953 -msgid "Existence of IP" +#: ../objectstorage_arch.rst:20 +msgid "**Object Storage architecture**" msgstr "" -#: ../telemetry-measurements.rst:1067 -msgid "Existence of a LB VIP" -msgstr "" - -#: ../telemetry-measurements.rst:1075 -msgid "Existence of a LB health probe" -msgstr "" - -#: ../telemetry-measurements.rst:1071 -msgid "Existence of a LB member" -msgstr "" - -#: ../telemetry-measurements.rst:1063 -msgid "Existence of a LB pool" -msgstr "" - -#: ../telemetry-measurements.rst:1141 -msgid "Existence of a VPN" -msgstr "" - -#: ../telemetry-measurements.rst:1206 -msgid "Existence of a firewall" -msgstr "" - -#: ../telemetry-measurements.rst:1210 -msgid "Existence of a firewall policy" -msgstr "" - -#: ../telemetry-measurements.rst:1234 -msgid "Existence of a firewall rule" -msgstr "" - -#: ../telemetry-measurements.rst:1145 -msgid "Existence of an IPSec connection" -msgstr "" - -#: ../telemetry-measurements.rst:1170 -msgid "Existence of an IPSec policy" -msgstr "" - -#: ../telemetry-measurements.rst:1184 -msgid "Existence of an Ike policy" -msgstr "" - -#: ../telemetry-measurements.rst:101 ../telemetry-measurements.rst:200 -msgid "Existence of instance" -msgstr "" - -#: ../telemetry-measurements.rst:105 ../telemetry-measurements.rst:205 -#: ../telemetry-measurements.rst:348 -msgid "Existence of instance (OpenStack types)" -msgstr "" - -#: ../telemetry-measurements.rst:914 -msgid "Existence of ne\\ twork" -msgstr "" - -#: ../telemetry-measurements.rst:934 ../telemetry-measurements.rst:980 -msgid "Existence of po\\ rt" -msgstr "" - -#: ../telemetry-measurements.rst:943 -msgid "Existence of ro\\ uter" -msgstr "" - -#: ../telemetry-measurements.rst:924 -msgid "Existence of su\\ bnet" -msgstr "" - -#: ../telemetry-measurements.rst:977 -msgid "Existence of sw\\ itch" -msgstr "" - -#: ../telemetry-measurements.rst:668 -msgid "Existence of the image" -msgstr "" - -#: ../telemetry-measurements.rst:709 -msgid "Existence of the snapshot" -msgstr "" - -#: ../telemetry-measurements.rst:701 -msgid "Existence of the volume" -msgstr "" - -#: ../telemetry-best-practices.rst:27 +#: ../objectstorage_arch.rst:28 msgid "" -"Expand the configuration to have greater control over different meter " -"intervals." +"Because access servers are collocated in their own tier, you can scale out " +"read/write access regardless of the storage capacity. For example, if a " +"cluster is on the public Internet, requires SSL termination, and has a high " +"demand for data access, you can provision many access servers. However, if " +"the cluster is on a private network and used primarily for archival " +"purposes, you need fewer access servers." msgstr "" -#: ../objectstorage_features.rst:41 -msgid "Expiring objects" -msgstr "" - -#: ../compute-configuring-migrations.rst:151 +#: ../objectstorage_arch.rst:35 msgid "" -"Export ``NOVA-INST-DIR/instances`` from ``HostA``, and ensure it is readable " -"and writable by the Compute user on ``HostB`` and ``HostC``." +"Since this is an HTTP addressable storage service, you may incorporate a " +"load balancer into the access tier." msgstr "" -#: ../blockstorage_volume_backups_export_import.rst:8 -msgid "Export and import backup metadata" -msgstr "" - -#: ../blockstorage_volume_backups_export_import.rst:29 +#: ../objectstorage_arch.rst:38 msgid "" -"Exporting and storing this encoded string metadata allows you to completely " -"restore the backup, even in the event of a catastrophic database failure. " -"This will preclude the need to back up the entire Block Storage database, " -"particularly if you only need to keep complete backups of a small subset of " -"volumes." -msgstr "" - -#: ../telemetry-data-collection.rst:813 -msgid "" -"Expression evaluation gracefully handles NaNs and exceptions. In such a case " -"it does not create a new sample but only logs a warning." -msgstr "" - -#: ../keystone_external_authentication.rst:3 -msgid "External authentication with Identity" -msgstr "" - -#: ../networking_adv-features.rst:195 -msgid "" -"External networks are visible to all users. However, the default policy " -"settings enable only administrative users to create, update, and delete " -"external networks." -msgstr "" - -#: ../blockstorage-driver-filter-weighing.rst:227 -msgid "Extra specs for the requested volume type" -msgstr "" - -#: ../compute-flavors.rst:292 -msgid "" -"FLAVOR-CORES—(Integer) The number of cores per socket for the guest VM. By " -"this is set to 1." -msgstr "" - -#: ../compute-flavors.rst:289 -msgid "" -"FLAVOR-SOCKETS—(Integer) The number of sockets for the guest VM. By this is " -"set to the number of vCPUs requested." -msgstr "" - -#: ../compute-flavors.rst:295 -msgid "" -"FLAVOR-THREADS—(Integer) The number of threads per core for the guest VM. By " -"this is set to 1." -msgstr "" - -#: ../networking_introduction.rst:257 -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:162 -msgid "" -"FWaaS is currently in technical preview; untested operation is not " -"recommended." -msgstr "" - -#: ../networking_introduction.rst:172 -msgid "FWaaS management options are also available in the OpenStack dashboard." +"Typically, the tier consists of a collection of 1U servers. These machines " +"use a moderate amount of RAM and are network I/O intensive. Since these " +"systems field each incoming API request, you should provision them with two " +"high-throughput (10GbE) interfaces - one for the incoming \"front-end\" " +"requests and the other for the \"back-end\" access to the object storage " +"nodes to put and fetch data." msgstr "" #: ../objectstorage_arch.rst:46 ../objectstorage_arch.rst:78 msgid "Factors to consider" msgstr "" +#: ../objectstorage_arch.rst:47 +msgid "" +"For most publicly facing deployments as well as private deployments " +"available across a wide-reaching corporate network, you use SSL to encrypt " +"traffic to the client. SSL adds significant processing load to establish " +"sessions between clients, which is why you have to provision more capacity " +"in the access layer. SSL may not be required for private deployments on " +"trusted networks." +msgstr "" + +#: ../objectstorage_arch.rst:55 +msgid "Storage nodes" +msgstr "" + +#: ../objectstorage_arch.rst:56 +msgid "" +"In most configurations, each of the five zones should have an equal amount " +"of storage capacity. Storage nodes use a reasonable amount of memory and " +"CPU. Metadata needs to be readily available to return objects quickly. The " +"object stores run services not only to field incoming requests from the " +"access tier, but to also run replicators, auditors, and reapers. You can " +"provision object stores provisioned with single gigabit or 10 gigabit " +"network interface depending on the expected workload and desired performance." +msgstr "" + +#: ../objectstorage_arch.rst:65 +msgid "**Object Storage (swift)**" +msgstr "" + +#: ../objectstorage_arch.rst:73 +msgid "" +"Currently, a 2 TB or 3 TB SATA disk delivers good performance for the price. " +"You can use desktop-grade drives if you have responsive remote hands in the " +"datacenter and enterprise-grade drives if you don't." +msgstr "" + +#: ../objectstorage_arch.rst:79 +msgid "" +"You should keep in mind the desired I/O performance for single-threaded " +"requests . This system does not use RAID, so a single disk handles each " +"request for an object. Disk performance impacts single-threaded response " +"rates." +msgstr "" + +#: ../objectstorage_arch.rst:84 +msgid "" +"To achieve apparent higher throughput, the object storage system is designed " +"to handle concurrent uploads/downloads. The network I/O capacity (1GbE, " +"bonded 1GbE pair, or 10GbE) should match your desired concurrent throughput " +"needs for reads and writes." +msgstr "" + +#: ../objectstorage_auditors.rst:3 +msgid "Object Auditor" +msgstr "" + +#: ../objectstorage_auditors.rst:5 +msgid "" +"On system failures, the XFS file system can sometimes truncate files it is " +"trying to write and produce zero-byte files. The object-auditor will catch " +"these problems but in the case of a system crash it is advisable to run an " +"extra, less rate limited sweep, to check for these specific files. You can " +"run this command as follows::" +msgstr "" + +#: ../objectstorage_auditors.rst:14 +msgid "" +"\"-z\" means to only check for zero-byte files at 1000 files per second." +msgstr "" + +#: ../objectstorage_auditors.rst:16 +msgid "" +"It is useful to run the object auditor on a specific device or set of " +"devices. You can run the object-auditor once as follows::" +msgstr "" + +#: ../objectstorage_auditors.rst:23 +msgid "" +"This will run the object auditor on only the sda and sdb devices. This " +"parameter accepts a comma separated list of values." +msgstr "" + +#: ../objectstorage_characteristics.rst:3 +msgid "Object Storage characteristics" +msgstr "" + +#: ../objectstorage_characteristics.rst:5 +msgid "The key characteristics of Object Storage are that:" +msgstr "" + +#: ../objectstorage_characteristics.rst:7 +msgid "All objects stored in Object Storage have a URL." +msgstr "" + +#: ../objectstorage_characteristics.rst:9 +msgid "" +"All objects stored are replicated 3✕ in as-unique-as-possible zones, which " +"can be defined as a group of drives, a node, a rack, and so on." +msgstr "" + +#: ../objectstorage_characteristics.rst:12 +msgid "All objects have their own metadata." +msgstr "" + +#: ../objectstorage_characteristics.rst:14 +msgid "" +"Developers interact with the object storage system through a RESTful HTTP " +"API." +msgstr "" + +#: ../objectstorage_characteristics.rst:17 +msgid "Object data can be located anywhere in the cluster." +msgstr "" + +#: ../objectstorage_characteristics.rst:19 +msgid "" +"The cluster scales by adding additional nodes without sacrificing " +"performance, which allows a more cost-effective linear storage expansion " +"than fork-lift upgrades." +msgstr "" + +#: ../objectstorage_characteristics.rst:23 +msgid "Data doesn't have to be migrate to an entirely new storage system." +msgstr "" + +#: ../objectstorage_characteristics.rst:25 +msgid "New nodes can be added to the cluster without downtime." +msgstr "" + #: ../objectstorage_characteristics.rst:27 msgid "Failed nodes and disks can be swapped out without downtime." msgstr "" -#: ../ts_vol_attach_miss_sg_scan.rst:3 -msgid "Failed to Attach Volume, Missing sg_scan" -msgstr "" - -#: ../ts-failed-attach-vol-after-detach.rst:11 -msgid "Failed to attach a volume after detaching the same volume." -msgstr "" - -#: ../ts-failed-attach-vol-after-detach.rst:6 -msgid "Failed to attach volume after detaching" -msgstr "" - -#: ../ts_vol_attach_miss_sg_scan.rst:8 +#: ../objectstorage_characteristics.rst:29 msgid "" -"Failed to attach volume to an instance, ``sg_scan`` file not found. This " -"warning and error occur when the sg3-utils package is not installed on the " -"compute node. The IDs in your message are unique to your system:" +"It runs on industry-standard hardware, such as Dell, HP, and Supermicro." msgstr "" -#: ../ts-failed-attach-vol-no-sysfsutils.rst:6 -msgid "Failed to attach volume, systool is not installed" +#: ../objectstorage_characteristics.rst:34 +msgid "Object Storage (swift)" msgstr "" -#: ../ts-failed-connect-vol-FC-SAN.rst:6 -msgid "Failed to connect volume in FC SAN" -msgstr "" - -#: ../ts_cinder_config.rst:153 +#: ../objectstorage_characteristics.rst:38 msgid "" -"Failed to create iscsi target error in the :file:`cinder-volume.log` file." +"Developers can either write directly to the Swift API or use one of the many " +"client libraries that exist for all of the popular programming languages, " +"such as Java, Python, Ruby, and C#. Amazon S3 and RackSpace Cloud Files " +"users should be very familiar with Object Storage. Users new to object " +"storage systems will have to adjust to a different approach and mindset than " +"those required for a traditional filesystem." msgstr "" -#: ../networking_adv-features.rst:646 -msgid "False" +#: ../objectstorage_components.rst:3 +msgid "Components" msgstr "" -#: ../telemetry-measurements.rst:488 ../telemetry-measurements.rst:491 -msgid "Fan rounds per minute (RPM)" +#: ../objectstorage_components.rst:5 +msgid "" +"The components that enable Object Storage to deliver high availability, high " +"durability, and high concurrency are:" msgstr "" -#: ../networking_introduction.rst:122 -msgid "Feature" +#: ../objectstorage_components.rst:8 +msgid "**Proxy servers.** Handle all of the incoming API requests." msgstr "" -#: ../objectstorage_features.rst:9 -msgid "Features" +#: ../objectstorage_components.rst:10 +msgid "**Rings.** Map logical names of data to locations on particular disks." +msgstr "" + +#: ../objectstorage_components.rst:13 +msgid "" +"**Zones.** Isolate data from other zones. A failure in one zone doesn't " +"impact the rest of the cluster because data is replicated across zones." +msgstr "" + +#: ../objectstorage_components.rst:17 +msgid "" +"**Accounts and containers.** Each account and container are individual " +"databases that are distributed across the cluster. An account database " +"contains the list of containers in that account. A container database " +"contains the list of objects in that container." +msgstr "" + +#: ../objectstorage_components.rst:22 +msgid "**Objects.** The data itself." +msgstr "" + +#: ../objectstorage_components.rst:24 +msgid "" +"**Partitions.** A partition stores objects, account databases, and container " +"databases and helps manage locations where data lives in the cluster." +msgstr "" + +#: ../objectstorage_components.rst:32 +msgid "**Object Storage building blocks**" +msgstr "" + +#: ../objectstorage_components.rst:39 +msgid "Proxy servers" +msgstr "" + +#: ../objectstorage_components.rst:41 +msgid "" +"Proxy servers are the public face of Object Storage and handle all of the " +"incoming API requests. Once a proxy server receives a request, it determines " +"the storage node based on the object's URL, for example, https://swift." +"example.com/v1/account/container/object. Proxy servers also coordinate " +"responses, handle failures, and coordinate timestamps." +msgstr "" + +#: ../objectstorage_components.rst:47 +msgid "" +"Proxy servers use a shared-nothing architecture and can be scaled as needed " +"based on projected workloads. A minimum of two proxy servers should be " +"deployed for redundancy. If one proxy server fails, the others take over." +msgstr "" + +#: ../objectstorage_components.rst:52 +msgid "" +"For more information concerning proxy server configuration, please see the " +"`Configuration Reference `__." +msgstr "" + +#: ../objectstorage_components.rst:57 +msgid "Rings" +msgstr "" + +#: ../objectstorage_components.rst:59 +msgid "" +"A ring represents a mapping between the names of entities stored on disk and " +"their physical locations. There are separate rings for accounts, containers, " +"and objects. When other components need to perform any operation on an " +"object, container, or account, they need to interact with the appropriate " +"ring to determine their location in the cluster." +msgstr "" + +#: ../objectstorage_components.rst:65 +msgid "" +"The ring maintains this mapping using zones, devices, partitions, and " +"replicas. Each partition in the ring is replicated, by default, three times " +"across the cluster, and partition locations are stored in the mapping " +"maintained by the ring. The ring is also responsible for determining which " +"devices are used for handoff in failure scenarios." +msgstr "" + +#: ../objectstorage_components.rst:71 +msgid "" +"Data can be isolated into zones in the ring. Each partition replica is " +"guaranteed to reside in a different zone. A zone could represent a drive, a " +"server, a cabinet, a switch, or even a data center." +msgstr "" + +#: ../objectstorage_components.rst:75 +msgid "" +"The partitions of the ring are equally divided among all of the devices in " +"the Object Storage installation. When partitions need to be moved around " +"(for example, if a device is added to the cluster), the ring ensures that a " +"minimum number of partitions are moved at a time, and only one replica of a " +"partition is moved at a time." +msgstr "" + +#: ../objectstorage_components.rst:81 +msgid "" +"You can use weights to balance the distribution of partitions on drives " +"across the cluster. This can be useful, for example, when differently sized " +"drives are used in a cluster." +msgstr "" + +#: ../objectstorage_components.rst:85 +msgid "" +"The ring is used by the proxy server and several background processes (like " +"replication)." +msgstr "" + +#: ../objectstorage_components.rst:92 +msgid "**The ring**" +msgstr "" + +#: ../objectstorage_components.rst:98 +msgid "" +"These rings are externally managed, in that the server processes themselves " +"do not modify the rings, they are instead given new rings modified by other " +"tools." +msgstr "" + +#: ../objectstorage_components.rst:102 +msgid "" +"The ring uses a configurable number of bits from an MD5 hash for a path as a " +"partition index that designates a device. The number of bits kept from the " +"hash is known as the partition power, and 2 to the partition power indicates " +"the partition count. Partitioning the full MD5 hash ring allows other parts " +"of the cluster to work in batches of items at once which ends up either more " +"efficient or at least less complex than working with each item separately or " +"the entire cluster all at once." +msgstr "" + +#: ../objectstorage_components.rst:110 +msgid "" +"Another configurable value is the replica count, which indicates how many of " +"the partition-device assignments make up a single ring. For a given " +"partition number, each replica's device will not be in the same zone as any " +"other replica's device. Zones can be used to group devices based on physical " +"locations, power separations, network separations, or any other attribute " +"that would improve the availability of multiple replicas at the same time." +msgstr "" + +#: ../objectstorage_components.rst:119 +msgid "Zones" +msgstr "" + +#: ../objectstorage_components.rst:121 +msgid "" +"Object Storage allows configuring zones in order to isolate failure " +"boundaries. Each data replica resides in a separate zone, if possible. At " +"the smallest level, a zone could be a single drive or a grouping of a few " +"drives. If there were five object storage servers, then each server would " +"represent its own zone. Larger deployments would have an entire rack (or " +"multiple racks) of object servers, each representing a zone. The goal of " +"zones is to allow the cluster to tolerate significant outages of storage " +"servers without losing all replicas of the data." +msgstr "" + +#: ../objectstorage_components.rst:130 +msgid "" +"As mentioned earlier, everything in Object Storage is stored, by default, " +"three times. Swift will place each replica \"as-uniquely-as-possible\" to " +"ensure both high availability and high durability. This means that when " +"choosing a replica location, Object Storage chooses a server in an unused " +"zone before an unused server in a zone that already has a replica of the " +"data." +msgstr "" + +#: ../objectstorage_components.rst:141 +msgid "**Zones**" +msgstr "" + +#: ../objectstorage_components.rst:147 +msgid "" +"When a disk fails, replica data is automatically distributed to the other " +"zones to ensure there are three copies of the data." +msgstr "" + +#: ../objectstorage_components.rst:151 +msgid "Accounts and containers" +msgstr "" + +#: ../objectstorage_components.rst:153 +msgid "" +"Each account and container is an individual SQLite database that is " +"distributed across the cluster. An account database contains the list of " +"containers in that account. A container database contains the list of " +"objects in that container." +msgstr "" + +#: ../objectstorage_components.rst:162 +msgid "**Accounts and containers**" +msgstr "" + +#: ../objectstorage_components.rst:168 +msgid "" +"To keep track of object data locations, each account in the system has a " +"database that references all of its containers, and each container database " +"references each object." +msgstr "" + +#: ../objectstorage_components.rst:173 +msgid "Partitions" +msgstr "" + +#: ../objectstorage_components.rst:175 +msgid "" +"A partition is a collection of stored data, including account databases, " +"container databases, and objects. Partitions are core to the replication " +"system." +msgstr "" + +#: ../objectstorage_components.rst:179 +msgid "" +"Think of a partition as a bin moving throughout a fulfillment center " +"warehouse. Individual orders get thrown into the bin. The system treats that " +"bin as a cohesive entity as it moves throughout the system. A bin is easier " +"to deal with than many little things. It makes for fewer moving parts " +"throughout the system." +msgstr "" + +#: ../objectstorage_components.rst:185 +msgid "" +"System replicators and object uploads/downloads operate on partitions. As " +"the system scales up, its behavior continues to be predictable because the " +"number of partitions is a fixed number." +msgstr "" + +#: ../objectstorage_components.rst:189 +msgid "" +"Implementing a partition is conceptually simple, a partition is just a " +"directory sitting on a disk with a corresponding hash table of what it " +"contains." +msgstr "" + +#: ../objectstorage_components.rst:197 +msgid "**Partitions**" +msgstr "" + +#: ../objectstorage_components.rst:204 +msgid "Replicators" +msgstr "" + +#: ../objectstorage_components.rst:206 +msgid "" +"In order to ensure that there are three copies of the data everywhere, " +"replicators continuously examine each partition. For each local partition, " +"the replicator compares it against the replicated copies in the other zones " +"to see if there are any differences." +msgstr "" + +#: ../objectstorage_components.rst:211 +msgid "" +"The replicator knows if replication needs to take place by examining hashes. " +"A hash file is created for each partition, which contains hashes of each " +"directory in the partition. Each of the three hash files is compared. For a " +"given partition, the hash files for each of the partition's copies are " +"compared. If the hashes are different, then it is time to replicate, and the " +"directory that needs to be replicated is copied over." +msgstr "" + +#: ../objectstorage_components.rst:219 +msgid "" +"This is where partitions come in handy. With fewer things in the system, " +"larger chunks of data are transferred around (rather than lots of little TCP " +"connections, which is inefficient) and there is a consistent number of " +"hashes to compare." +msgstr "" + +#: ../objectstorage_components.rst:224 +msgid "" +"The cluster eventually has a consistent behavior where the newest data has a " +"priority." +msgstr "" + +#: ../objectstorage_components.rst:231 +msgid "**Replication**" +msgstr "" + +#: ../objectstorage_components.rst:237 +msgid "" +"If a zone goes down, one of the nodes containing a replica notices and " +"proactively copies data to a handoff location." +msgstr "" + +#: ../objectstorage_components.rst:241 +msgid "Use cases" +msgstr "" + +#: ../objectstorage_components.rst:243 +msgid "" +"The following sections show use cases for object uploads and downloads and " +"introduce the components." +msgstr "" + +#: ../objectstorage_components.rst:248 +msgid "Upload" +msgstr "" + +#: ../objectstorage_components.rst:250 +msgid "" +"A client uses the REST API to make a HTTP request to PUT an object into an " +"existing container. The cluster receives the request. First, the system must " +"figure out where the data is going to go. To do this, the account name, " +"container name, and object name are all used to determine the partition " +"where this object should live." +msgstr "" + +#: ../objectstorage_components.rst:256 +msgid "" +"Then a lookup in the ring figures out which storage nodes contain the " +"partitions in question." +msgstr "" + +#: ../objectstorage_components.rst:259 +msgid "" +"The data is then sent to each storage node where it is placed in the " +"appropriate partition. At least two of the three writes must be successful " +"before the client is notified that the upload was successful." +msgstr "" + +#: ../objectstorage_components.rst:263 +msgid "" +"Next, the container database is updated asynchronously to reflect that there " +"is a new object in it." +msgstr "" + +#: ../objectstorage_components.rst:270 +msgid "**Object Storage in use**" +msgstr "" + +#: ../objectstorage_components.rst:277 +msgid "Download" +msgstr "" + +#: ../objectstorage_components.rst:279 +msgid "" +"A request comes in for an account/container/object. Using the same " +"consistent hashing, the partition name is generated. A lookup in the ring " +"reveals which storage nodes contain that partition. A request is made to one " +"of the storage nodes to fetch the object and, if that fails, requests are " +"made to the other nodes." msgstr "" #: ../objectstorage_features.rst:3 msgid "Features and benefits" msgstr "" -# #-#-#-#-# blockstorage_glusterfs_backend.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -# #-#-#-#-# blockstorage_nfs_backend.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -#: ../blockstorage_glusterfs_backend.rst:16 -#: ../blockstorage_glusterfs_backend.rst:137 -#: ../blockstorage_nfs_backend.rst:16 ../blockstorage_nfs_backend.rst:75 -msgid "Fedora" +#: ../objectstorage_features.rst:9 +msgid "Features" msgstr "" -#: ../telemetry-data-collection.rst:1038 -msgid "File dispatcher" +#: ../objectstorage_features.rst:10 +msgid "Benefits" msgstr "" -#: ../compute-images-instances.rst:124 -msgid "File system" +#: ../objectstorage_features.rst:11 +msgid "Leverages commodity hardware" msgstr "" -#: ../compute-root-wrap-reference.rst:87 +#: ../objectstorage_features.rst:12 +msgid "No lock-in, lower price/GB." +msgstr "" + +#: ../objectstorage_features.rst:13 +msgid "HDD/node failure agnostic" +msgstr "" + +#: ../objectstorage_features.rst:14 +msgid "Self-healing, reliable, data redundancy protects from failures." +msgstr "" + +#: ../objectstorage_features.rst:15 +msgid "Unlimited storage" +msgstr "" + +#: ../objectstorage_features.rst:16 msgid "" -"Filter definition files use an INI file format with a ``[Filters]`` section " -"and several lines, each with a unique parameter name, which should be " -"different for each filter you define:" +"Large and flat namespace, highly scalable read/write access, able to serve " +"content directly from storage system." msgstr "" -#: ../keystone_integrate_assignment_backend_ldap.rst:107 -msgid "Filtering method" +#: ../objectstorage_features.rst:18 +msgid "Multi-dimensional scalability" msgstr "" -# #-#-#-#-# keystone_integrate_assignment_backend_ldap.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -# #-#-#-#-# keystone_integrate_identity_backend_ldap.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -#: ../keystone_integrate_assignment_backend_ldap.rst:107 -#: ../keystone_integrate_identity_backend_ldap.rst:195 -msgid "Filters" -msgstr "" - -#: ../blockstorage_multi_backend.rst:108 +#: ../objectstorage_features.rst:19 msgid "" -"Filters the available back ends. By default, ``AvailabilityZoneFilter``, " -"``CapacityFilter`` and ``CapabilitiesFilter`` are enabled." +"Scale-out architecture: Scale vertically and horizontally-distributed " +"storage. Backs up and archives large amounts of data with linear performance." msgstr "" -#: ../keystone_secure_identity_to_ldap_backend.rst:16 -msgid "Find the ``[ldap]`` section." +#: ../objectstorage_features.rst:22 +msgid "Account/container/object structure" msgstr "" -#: ../networking_adv-features.rst:280 -msgid "Finds floating IP for a specified VM port." -msgstr "" - -#: ../telemetry-measurements.rst:1198 -msgid "Firewall as a Service (FWaaS)" -msgstr "" - -#: ../telemetry-measurements.rst:1224 -msgid "Firewall policy was created" -msgstr "" - -#: ../telemetry-measurements.rst:1229 -msgid "Firewall policy was updated" -msgstr "" - -#: ../telemetry-measurements.rst:1238 -msgid "Firewall rule w\\ as created" -msgstr "" - -#: ../telemetry-measurements.rst:1243 -msgid "Firewall rule w\\ as updated" -msgstr "" - -#: ../telemetry-measurements.rst:1216 -msgid "Firewall was cr\\ eated" -msgstr "" - -#: ../telemetry-measurements.rst:1220 -msgid "Firewall was up\\ dated" -msgstr "" - -#: ../telemetry-system-architecture.rst:152 -msgid "Firewall-as-a-Service (FWaaS) meters" -msgstr "" - -#: ../networking_introduction.rst:150 -msgid "Firewall-as-a-Service (FWaaS) overview" -msgstr "" - -#: ../blockstorage_get_capabilities.rst:31 -msgid "First, get a list of the services::" -msgstr "" - -#: ../blockstorage_volume_migration.rst:42 -msgid "First, list the available back-ends:" -msgstr "" - -#: ../compute_arch.rst:101 +#: ../objectstorage_features.rst:23 msgid "" -"Fixed IP addresses assigned to the same instance when it launches. This " -"allows instances to have the same publicly or privately accessible IP " -"addresses." +"No nesting, not a traditional file system: Optimized for scale, it scales to " +"multiple petabytes and billions of objects." msgstr "" -#: ../compute-networking-nova.rst:86 -msgid "Flat DHCP Network Manager" +#: ../objectstorage_features.rst:25 +msgid "Built-in replication 3✕ + data redundancy (compared with 2✕ on RAID)" msgstr "" -#: ../compute-networking-nova.rst:44 -msgid "Flat Network Manager" -msgstr "" - -#: ../compute-flavors.rst:76 +#: ../objectstorage_features.rst:27 msgid "" -"Flavor customization can be limited by the hypervisor in use. For example " -"the libvirt driver enables quotas on CPUs available to a VM, disk tuning, " -"bandwidth I/O, watchdog behavior, random number generator device control, " -"and instance VIF traffic control." +"A configurable number of accounts, containers and object copies for high " +"availability." msgstr "" -#: ../compute-flavors.rst:5 -msgid "Flavors" +#: ../objectstorage_features.rst:29 +msgid "Easily add capacity (unlike RAID resize)" msgstr "" -#: ../compute-flavors.rst:299 +#: ../objectstorage_features.rst:30 +msgid "Elastic data scaling with ease ." +msgstr "" + +#: ../objectstorage_features.rst:31 +msgid "No central database" +msgstr "" + +#: ../objectstorage_features.rst:32 +msgid "Higher performance, no bottlenecks." +msgstr "" + +#: ../objectstorage_features.rst:33 +msgid "RAID not required" +msgstr "" + +#: ../objectstorage_features.rst:34 +msgid "Handle many small, random reads and writes efficiently." +msgstr "" + +#: ../objectstorage_features.rst:35 +msgid "Built-in management utilities" +msgstr "" + +#: ../objectstorage_features.rst:36 msgid "" -"Flavors can also be assigned to particular projects. By default, a flavor is " -"public and available to all projects. Private flavors are only accessible to " -"those on the access list and are invisible to other projects. To create and " -"assign a private flavor to a project, run these commands:" +"Account management: Create, add, verify, and delete users; Container " +"management: Upload, download, and verify; Monitoring: Capacity, host, " +"network, log trawling, and cluster health." msgstr "" -#: ../compute-security.rst:124 +#: ../objectstorage_features.rst:39 +msgid "Drive auditing" +msgstr "" + +#: ../objectstorage_features.rst:40 +msgid "Detect drive failures preempting data corruption." +msgstr "" + +#: ../objectstorage_features.rst:41 +msgid "Expiring objects" +msgstr "" + +#: ../objectstorage_features.rst:42 msgid "" -"Flavors can be designated as trusted using the ``nova flavor-key set`` " -"command. In this example, the ``m1.tiny`` flavor is being set as trusted:" +"Users can set an expiration time or a TTL on an object to control access." msgstr "" -#: ../compute-flavors.rst:32 -msgid "Flavors define these elements:" +#: ../objectstorage_features.rst:44 +msgid "Direct object access" msgstr "" -#: ../compute_arch.rst:98 +#: ../objectstorage_features.rst:45 +msgid "Enable direct browser access to content, such as for a control panel." +msgstr "" + +#: ../objectstorage_features.rst:47 +msgid "Realtime visibility into client requests" +msgstr "" + +#: ../objectstorage_features.rst:48 +msgid "Know what users are requesting." +msgstr "" + +#: ../objectstorage_features.rst:49 +msgid "Supports S3 API" +msgstr "" + +#: ../objectstorage_features.rst:50 +msgid "Utilize tools that were designed for the popular S3 API." +msgstr "" + +#: ../objectstorage_features.rst:51 +msgid "Restrict containers per account" +msgstr "" + +#: ../objectstorage_features.rst:52 +msgid "Limit access to control usage by user." +msgstr "" + +#: ../objectstorage_features.rst:53 +msgid "Support for NetApp, Nexenta, Solidfire" +msgstr "" + +#: ../objectstorage_features.rst:54 +msgid "Unified support for block volumes using a variety of storage systems." +msgstr "" + +#: ../objectstorage_features.rst:56 +msgid "Snapshot and backup API for block volumes." +msgstr "" + +#: ../objectstorage_features.rst:57 +msgid "Data protection and recovery for VM data." +msgstr "" + +#: ../objectstorage_features.rst:58 +msgid "Standalone volume API available" +msgstr "" + +#: ../objectstorage_features.rst:59 +msgid "Separate endpoint and API for integration with other compute systems." +msgstr "" + +#: ../objectstorage_features.rst:61 +msgid "Integration with Compute" +msgstr "" + +#: ../objectstorage_features.rst:62 msgid "" -"Floating IP addresses assigned to any instance when it launches. This allows " -"instances to have the same publicly accessible IP addresses." +"Fully integrated with Compute for attaching block volumes and reporting on " +"usage." msgstr "" -#: ../compute-networking-nova.rst:605 +#: ../objectstorage_intro.rst:3 +msgid "Introduction to Object Storage" +msgstr "" + +#: ../objectstorage_intro.rst:5 msgid "" -"Floating IPs are implemented by using a source NAT (SNAT rule in iptables), " -"so security groups can sometimes display inconsistent behavior if VMs use " -"their floating IP to communicate with other VMs, particularly on the same " -"physical host. Traffic from VM to VM across the fixed network does not have " -"this issue, and so this is the recommended setup. To ensure that traffic " -"does not get SNATed to the floating range, explicitly set:" +"OpenStack Object Storage (code-named swift) is open source software for " +"creating redundant, scalable data storage using clusters of standardized " +"servers to store petabytes of accessible data. It is a long-term storage " +"system for large amounts of static data that can be retrieved, leveraged, " +"and updated. Object Storage uses a distributed architecture with no central " +"point of control, providing greater scalability, redundancy, and permanence. " +"Objects are written to multiple hardware devices, with the OpenStack " +"software responsible for ensuring data replication and integrity across the " +"cluster. Storage clusters scale horizontally by adding new nodes. Should a " +"node fail, OpenStack works to replicate its content from other active nodes. " +"Because OpenStack uses software logic to ensure data replication and " +"distribution across different devices, inexpensive commodity hard drives and " +"servers can be used in lieu of more expensive equipment." msgstr "" -#: ../objectstorage-monitoring.rst:58 +#: ../objectstorage_intro.rst:20 msgid "" -"Florian Hines developed the Swift-Informant middleware (see https://github." -"com/pandemicsyn/swift-informant) to get real-time visibility into Object " -"Storage client requests. It sits in the pipeline for the proxy server, and " -"after each request to the proxy server, sends three meters to a StatsD " -"server (see http://codeascraft.etsy.com/2011/02/15/measure-anything-measure-" -"everything/):" +"Object Storage is ideal for cost effective, scale-out storage. It provides a " +"fully distributed, API-accessible storage platform that can be integrated " +"directly into applications or used for backup, archiving, and data retention." msgstr "" -#: ../objectstorage-monitoring.rst:95 +#: ../objectstorage_replication.rst:3 +msgid "Replication" +msgstr "" + +#: ../objectstorage_replication.rst:5 msgid "" -"Florian's `Statsdlog `__ project " -"increments StatsD counters based on logged events. Like Swift-Informant, it " -"is also non-intrusive, but statsdlog can track events from all Object " -"Storage daemons, not just proxy-server. The daemon listens to a UDP stream " -"of syslog messages and StatsD counters are incremented when a log line " -"matches a regular expression. Meter names are mapped to regex match patterns " -"in a JSON file, allowing flexible configuration of what meters are extracted " -"from the log stream." +"Because each replica in Object Storage functions independently and clients " +"generally require only a simple majority of nodes to respond to consider an " +"operation successful, transient failures like network partitions can quickly " +"cause replicas to diverge. These differences are eventually reconciled by " +"asynchronous, peer-to-peer replicator processes. The replicator processes " +"traverse their local file systems and concurrently perform operations in a " +"manner that balances load across physical disks." msgstr "" -#: ../identity_troubleshoot.rst:167 -msgid "Flush expired tokens from the token database table" -msgstr "" - -#: ../ts_no_emulator_x86_64.rst:17 +#: ../objectstorage_replication.rst:14 msgid "" -"Follow the instructions in the `enabling KVM section `__ of the " -"Configuration Reference to enable hardware virtualization support in your " -"BIOS." +"Replication uses a push model, with records and files generally only being " +"copied from local to remote replicas. This is important because data on the " +"node might not belong there (as in the case of hand offs and ring changes), " +"and a replicator cannot know which data it should pull in from elsewhere in " +"the cluster. Any node that contains data must ensure that data gets to where " +"it belongs. The ring handles replica placement." msgstr "" -#: ../compute-service-groups.rst:82 +#: ../objectstorage_replication.rst:21 msgid "" -"For Compute Service groups customization options, see the `OpenStack " -"Configuration Reference Guide `_." +"To replicate deletions in addition to creations, every deleted record or " +"file in the system is marked by a tombstone. The replication process cleans " +"up tombstones after a time period known as the *consistency window*. This " +"window defines the duration of the replication and how long transient " +"failure can remove a node from the cluster. Tombstone cleanup must be tied " +"to replication to reach replica convergence." msgstr "" -#: ../networking_config-agents.rst:247 +#: ../objectstorage_replication.rst:28 msgid "" -"For DHCP namespace the configuration key: ``dhcp_delete_namespaces = True``. " -"You can set it to False in case namespaces cannot be deleted cleanly on the " -"host running the DHCP agent." +"If a replicator detects that a remote drive has failed, the replicator uses " +"the ``get_more_nodes`` interface for the ring to choose an alternate node " +"with which to synchronize. The replicator can maintain desired levels of " +"replication during disk failures, though some replicas might not be in an " +"immediately usable location." msgstr "" -#: ../blockstorage_multi_backend.rst:84 +#: ../objectstorage_replication.rst:36 msgid "" -"For Fiber Channel drivers that support multipath, the configuration group " -"requires the ``use_multipath_for_image_xfer=true`` option. In the example " -"below, you can see details for HP 3PAR and EMC Fiber Channel drivers." +"The replicator does not maintain desired levels of replication when failures " +"such as entire node failures occur; most failures are transient." msgstr "" -#: ../networking_config-agents.rst:252 +#: ../objectstorage_replication.rst:40 +msgid "The main replication types are:" +msgstr "" + +#: ../objectstorage_replication.rst:43 ../objectstorage_replication.rst:49 +msgid "Database replication" +msgstr "" + +#: ../objectstorage_replication.rst:43 +msgid "Replicates containers and objects." +msgstr "" + +#: ../objectstorage_replication.rst:46 ../objectstorage_replication.rst:75 +msgid "Object replication" +msgstr "" + +#: ../objectstorage_replication.rst:46 +msgid "Replicates object data." +msgstr "" + +#: ../objectstorage_replication.rst:50 msgid "" -"For L3 namespace, the configuration key: ``router_delete_namespaces = " -"True``. You can set it to False in case namespaces cannot be deleted cleanly " -"on the host running the L3 agent." +"Database replication completes a low-cost hash comparison to determine " +"whether two replicas already match. Normally, this check can quickly verify " +"that most databases in the system are already synchronized. If the hashes " +"differ, the replicator synchronizes the databases by sharing records added " +"since the last synchronization point." msgstr "" -#: ../objectstorage-troubleshoot.rst:5 +#: ../objectstorage_replication.rst:56 msgid "" -"For Object Storage, everything is logged in :file:`/var/log/syslog` (or :" -"file:`messages` on some distros). Several settings enable further " -"customization of logging, such as ``log_name``, ``log_facility``, and " -"``log_level``, within the object server configuration files." +"This synchronization point is a high water mark that notes the last record " +"at which two databases were known to be synchronized, and is stored in each " +"database as a tuple of the remote database ID and record ID. Database IDs " +"are unique across all replicas of the database, and record IDs are " +"monotonically increasing integers. After all new records are pushed to the " +"remote database, the entire synchronization table of the local database is " +"pushed, so the remote database can guarantee that it is synchronized with " +"everything with which the local database was previously synchronized." msgstr "" -#: ../keystone_integrate_assignment_backend_ldap.rst:23 +#: ../objectstorage_replication.rst:66 msgid "" -"For OpenStack Identity assignments to access LDAP servers, you must define " -"the destination LDAP server in the :file:`keystone.conf` file. For more " -"information, see :ref:`integrate-identity-with-ldap`." +"If a replica is missing, the whole local database file is transmitted to the " +"peer by using rsync(1) and is assigned a new unique ID." msgstr "" -#: ../keystone_integrate_identity_backend_ldap.rst:13 +#: ../objectstorage_replication.rst:69 msgid "" -"For OpenStack Identity service to access LDAP servers, you must define the " -"destination LDAP server in the ``keystone.conf`` file. For more information, " -"see :ref:`integrate-identity-with-ldap`." +"In practice, database replication can process hundreds of databases per " +"concurrency setting per second (up to the number of available CPUs or disks) " +"and is bound by the number of database transactions that must be performed." msgstr "" -#: ../networking_adv-features.rst:153 +#: ../objectstorage_replication.rst:76 msgid "" -"For VLAN networks, the VLAN VID on the physical network that realizes the " -"virtual network. Valid VLAN VIDs are 1 through 4094. For GRE networks, the " -"tunnel ID. Valid tunnel IDs are any 32 bit unsigned integer. Not applicable " -"to the ``flat`` or ``local`` network types." +"The initial implementation of object replication performed an rsync to push " +"data from a local partition to all remote servers where it was expected to " +"reside. While this worked at small scale, replication times skyrocketed once " +"directory structures could no longer be held in RAM. This scheme was " +"modified to save a hash of the contents for each suffix directory to a per-" +"partition hashes file. The hash for a suffix directory is no longer valid " +"when the contents of that suffix directory is modified." msgstr "" -#: ../compute-admin-password-injection.rst:65 +#: ../objectstorage_replication.rst:85 msgid "" -"For Windows virtual machines, configure the Windows image to retrieve the " -"admin password on boot by installing an agent such as `cloudbase-init`_." +"The object replication process reads in hash files and calculates any " +"invalidated hashes. Then, it transmits the hashes to each remote server that " +"should hold the partition, and only suffix directories with differing hashes " +"on the remote server are rsynced. After pushing files to the remote server, " +"the replication process notifies it to recalculate hashes for the rsynced " +"suffix directories." msgstr "" -#: ../objectstorage-troubleshoot.rst:144 +#: ../objectstorage_replication.rst:92 msgid "" -"For ``min_part_hours`` you either have to remember what the value you used " -"was, or just make up a new one:" +"The number of uncached directories that object replication must traverse, " +"usually as a result of invalidated suffix directory hashes, impedes " +"performance. To provide acceptable replication speeds, object replication is " +"designed to invalidate around 2 percent of the hash space on a normal node " +"each day." msgstr "" -#: ../compute-manage-the-cloud.rst:69 +#: ../objectstorage_ringbuilder.rst:3 +msgid "Ring-builder" +msgstr "" + +#: ../objectstorage_ringbuilder.rst:5 msgid "" -"For a complete list of ``nova`` commands and parameters, see the `OpenStack " -"Command-Line Reference `__." +"Use the swift-ring-builder utility to build and manage rings. This utility " +"assigns partitions to devices and writes an optimized Python structure to a " +"gzipped, serialized file on disk for transmission to the servers. The server " +"processes occasionally check the modification time of the file and reload in-" +"memory copies of the ring structure as needed. If you use a slightly older " +"version of the ring, one of the three replicas for a partition subset will " +"be incorrect because of the way the ring-builder manages changes to the " +"ring. You can work around this issue." msgstr "" -#: ../compute-node-down.rst:150 +#: ../objectstorage_ringbuilder.rst:15 msgid "" -"For a definition of a disaster recovery plan (DRP), see `http://en.wikipedia." -"org/wiki/Disaster\\_Recovery\\_Plan `_." +"The ring-builder also keeps its own builder file with the ring information " +"and additional data required to build future rings. It is very important to " +"keep multiple backup copies of these builder files. One option is to copy " +"the builder files out to every server while copying the ring files " +"themselves. Another is to upload the builder files into the cluster itself. " +"If you lose the builder file, you have to create a new ring from scratch. " +"Nearly all partitions would be assigned to different devices and, therefore, " +"nearly all of the stored data would have to be replicated to new locations. " +"So, recovery from a builder file loss is possible, but data would be " +"unreachable for an extended time." msgstr "" -#: ../networking_introduction.rst:13 +#: ../objectstorage_ringbuilder.rst:27 +msgid "Ring data structure" +msgstr "" + +#: ../objectstorage_ringbuilder.rst:28 msgid "" -"For a detailed description of the Networking API abstractions and their " -"attributes, see the `OpenStack Networking API v2.0 Reference `__." +"The ring data structure consists of three top level fields: a list of " +"devices in the cluster, a list of lists of device ids indicating partition " +"to device assignments, and an integer indicating the number of bits to shift " +"an MD5 hash to calculate the partition for the hash." msgstr "" -#: ../compute-images-instances.rst:384 -msgid "For a list of flavors that are available on your system, run:" +#: ../objectstorage_ringbuilder.rst:34 +msgid "Partition assignment list" msgstr "" -#: ../compute_arch.rst:281 -msgid "For a list of flavors that are available on your system::" -msgstr "" - -#: ../telemetry-data-collection.rst:61 +#: ../objectstorage_ringbuilder.rst:35 msgid "" -"For a more detailed list of Compute notifications please check the `System " -"Usage Data Data wiki page `__." +"This is a list of ``array('H')`` of devices ids. The outermost list contains " +"an ``array('H')`` for each replica. Each ``array('H')`` has a length equal " +"to the partition count for the ring. Each integer in the ``array('H')`` is " +"an index into the above list of devices. The partition list is known " +"internally to the Ring class as ``_replica2part2dev_id``." +msgstr "" + +#: ../objectstorage_ringbuilder.rst:41 +msgid "" +"So, to create a list of device dictionaries assigned to a partition, the " +"Python code would look like::" +msgstr "" + +#: ../objectstorage_ringbuilder.rst:47 +msgid "" +"That code is a little simplistic because it does not account for the removal " +"of duplicate devices. If a ring has more replicas than devices, a partition " +"will have more than one replica on a device." +msgstr "" + +#: ../objectstorage_ringbuilder.rst:51 +msgid "" +"``array('H')`` is used for memory conservation as there may be millions of " +"partitions." +msgstr "" + +#: ../objectstorage_ringbuilder.rst:55 +msgid "Overload" +msgstr "" + +#: ../objectstorage_ringbuilder.rst:57 +msgid "" +"The ring builder tries to keep replicas as far apart as possible while still " +"respecting device weights. When it can not do both, the overload factor " +"determines what happens. Each device takes an extra fraction of its desired " +"partitions to allow for replica dispersion; after that extra fraction is " +"exhausted, replicas are placed closer together than optimal." +msgstr "" + +#: ../objectstorage_ringbuilder.rst:64 +msgid "" +"The overload factor lets the operator trade off replica dispersion " +"(durability) against data dispersion (uniform disk usage)." +msgstr "" + +#: ../objectstorage_ringbuilder.rst:67 +msgid "" +"The default overload factor is 0, so device weights are strictly followed." +msgstr "" + +#: ../objectstorage_ringbuilder.rst:70 +msgid "" +"With an overload factor of 0.1, each device accepts 10% more partitions than " +"it otherwise would, but only if it needs to maintain partition dispersion." +msgstr "" + +#: ../objectstorage_ringbuilder.rst:74 +msgid "" +"For example, consider a 3-node cluster of machines with equal-size disks; " +"node A has 12 disks, node B has 12 disks, and node C has 11 disks. The ring " +"has an overload factor of 0.1 (10%)." +msgstr "" + +#: ../objectstorage_ringbuilder.rst:78 +msgid "" +"Without the overload, some partitions would end up with replicas only on " +"nodes A and B. However, with the overload, every device can accept up to 10% " +"more partitions for the sake of dispersion. The missing disk in C means " +"there is one disk's worth of partitions to spread across the remaining 11 " +"disks, which gives each disk in C an extra 9.09% load. Since this is less " +"than the 10% overload, there is one replica of each partition on each node." +msgstr "" + +#: ../objectstorage_ringbuilder.rst:86 +msgid "" +"However, this does mean that the disks in node C have more data than the " +"disks in nodes A and B. If 80% full is the warning threshold for the " +"cluster, node C's disks reach 80% full while A and B's disks are only 72.7% " +"full." +msgstr "" + +#: ../objectstorage_ringbuilder.rst:93 +msgid "Replica counts" +msgstr "" + +#: ../objectstorage_ringbuilder.rst:94 +msgid "" +"To support the gradual change in replica counts, a ring can have a real " +"number of replicas and is not restricted to an integer number of replicas." +msgstr "" + +#: ../objectstorage_ringbuilder.rst:98 +msgid "" +"A fractional replica count is for the whole ring and not for individual " +"partitions. It indicates the average number of replicas for each partition. " +"For example, a replica count of 3.2 means that 20 percent of partitions have " +"four replicas and 80 percent have three replicas." +msgstr "" + +#: ../objectstorage_ringbuilder.rst:103 +msgid "The replica count is adjustable." +msgstr "" + +#: ../objectstorage_ringbuilder.rst:110 +msgid "" +"You must rebalance the replica ring in globally distributed clusters. " +"Operators of these clusters generally want an equal number of replicas and " +"regions. Therefore, when an operator adds or removes a region, the operator " +"adds or removes a replica. Removing unneeded replicas saves on the cost of " +"disks." +msgstr "" + +#: ../objectstorage_ringbuilder.rst:116 +msgid "" +"You can gradually increase the replica count at a rate that does not " +"adversely affect cluster performance." +msgstr "" + +#: ../objectstorage_ringbuilder.rst:129 +msgid "" +"Changes take effect after the ring is rebalanced. Therefore, if you intend " +"to change from 3 replicas to 3.01 but you accidentally type 2.01, no data is " +"lost." +msgstr "" + +#: ../objectstorage_ringbuilder.rst:133 +msgid "" +"Additionally, the ``swift-ring-builder X.builder create`` command can now " +"take a decimal argument for the number of replicas." +msgstr "" + +#: ../objectstorage_ringbuilder.rst:137 +msgid "Partition shift value" +msgstr "" + +#: ../objectstorage_ringbuilder.rst:138 +msgid "" +"The partition shift value is known internally to the Ring class as " +"``_part_shift``. This value is used to shift an MD5 hash to calculate the " +"partition where the data for that hash should reside. Only the top four " +"bytes of the hash is used in this process. For example, to compute the " +"partition for the :file:`/account/container/object` path using Python::" msgstr "" #: ../objectstorage_ringbuilder.rst:148 @@ -7054,15 +17836,544 @@ msgid "" "- P``." msgstr "" -#: ../compute-remote-console-access.rst:200 -msgid "For all-in-one XenServer domU deployments, set this to ``169.254.0.1.``" +#: ../objectstorage_ringbuilder.rst:152 +msgid "Build the ring" msgstr "" -#: ../compute-manage-logs.rst:41 +#: ../objectstorage_ringbuilder.rst:153 +msgid "The ring builder process includes these high-level steps:" +msgstr "" + +#: ../objectstorage_ringbuilder.rst:155 msgid "" -"For an example :file:`logging.conf` file with various defined handlers, see " -"the `OpenStack Configuration Reference `__." +"The utility calculates the number of partitions to assign to each device " +"based on the weight of the device. For example, for a partition at the power " +"of 20, the ring has 1,048,576 partitions. One thousand devices of equal " +"weight each want 1,048.576 partitions. The devices are sorted by the number " +"of partitions they desire and kept in order throughout the initialization " +"process." +msgstr "" + +#: ../objectstorage_ringbuilder.rst:164 +msgid "" +"Each device is also assigned a random tiebreaker value that is used when two " +"devices desire the same number of partitions. This tiebreaker is not stored " +"on disk anywhere, and so two different rings created with the same " +"parameters will have different partition assignments. For repeatable " +"partition assignments, ``RingBuilder.rebalance()`` takes an optional seed " +"value that seeds the Python pseudo-random number generator." +msgstr "" + +#: ../objectstorage_ringbuilder.rst:172 +msgid "" +"The ring builder assigns each partition replica to the device that requires " +"most partitions at that point while keeping it as far away as possible from " +"other replicas. The ring builder prefers to assign a replica to a device in " +"a region that does not already have a replica. If no such region is " +"available, the ring builder searches for a device in a different zone, or on " +"a different server. If it does not find one, it looks for a device with no " +"replicas. Finally, if all options are exhausted, the ring builder assigns " +"the replica to the device that has the fewest replicas already assigned." +msgstr "" + +#: ../objectstorage_ringbuilder.rst:184 +msgid "" +"The ring builder assigns multiple replicas to one device only if the ring " +"has fewer devices than it has replicas." +msgstr "" + +#: ../objectstorage_ringbuilder.rst:187 +msgid "" +"When building a new ring from an old ring, the ring builder recalculates the " +"desired number of partitions that each device wants." +msgstr "" + +#: ../objectstorage_ringbuilder.rst:190 +msgid "" +"The ring builder unassigns partitions and gathers these partitions for " +"reassignment, as follows:" +msgstr "" + +#: ../objectstorage_ringbuilder.rst:193 +msgid "" +"The ring builder unassigns any assigned partitions from any removed devices " +"and adds these partitions to the gathered list." +msgstr "" + +#: ../objectstorage_ringbuilder.rst:195 +msgid "" +"The ring builder unassigns any partition replicas that can be spread out for " +"better durability and adds these partitions to the gathered list." +msgstr "" + +#: ../objectstorage_ringbuilder.rst:198 +msgid "" +"The ring builder unassigns random partitions from any devices that have more " +"partitions than they need and adds these partitions to the gathered list." +msgstr "" + +#: ../objectstorage_ringbuilder.rst:202 +msgid "" +"The ring builder reassigns the gathered partitions to devices by using a " +"similar method to the one described previously." +msgstr "" + +#: ../objectstorage_ringbuilder.rst:205 +msgid "" +"When the ring builder reassigns a replica to a partition, the ring builder " +"records the time of the reassignment. The ring builder uses this value when " +"it gathers partitions for reassignment so that no partition is moved twice " +"in a configurable amount of time. The RingBuilder class knows this " +"configurable amount of time as ``min_part_hours``. The ring builder ignores " +"this restriction for replicas of partitions on removed devices because " +"removal of a device happens on device failure only, and reassignment is the " +"only choice." +msgstr "" + +#: ../objectstorage_ringbuilder.rst:214 +msgid "" +"These steps do not always perfectly rebalance a ring due to the random " +"nature of gathering partitions for reassignment. To help reach a more " +"balanced ring, the rebalance process is repeated until near perfect (less " +"than 1 percent off) or when the balance does not improve by at least 1 " +"percent (indicating we probably cannot get perfect balance due to wildly " +"imbalanced zones or too many partitions recently moved)." +msgstr "" + +#: ../objectstorage_tenant_specific_image_storage.rst:3 +msgid "Configure tenant-specific image locations with Object Storage" +msgstr "" + +#: ../objectstorage_tenant_specific_image_storage.rst:5 +msgid "" +"For some deployers, it is not ideal to store all images in one place to " +"enable all tenants and users to access them. You can configure the Image " +"service to store image data in tenant-specific image locations. Then, only " +"the following tenants can use the Image service to access the created image:" +msgstr "" + +#: ../objectstorage_tenant_specific_image_storage.rst:11 +msgid "The tenant who owns the image" +msgstr "" + +#: ../objectstorage_tenant_specific_image_storage.rst:12 +msgid "" +"Tenants that are defined in ``swift_store_admin_tenants`` and that have " +"admin-level accounts" +msgstr "" + +#: ../objectstorage_tenant_specific_image_storage.rst:15 +msgid "**To configure tenant-specific image locations**" +msgstr "" + +#: ../objectstorage_tenant_specific_image_storage.rst:17 +msgid "" +"Configure swift as your ``default_store`` in the :file:`glance-api.conf` " +"file." +msgstr "" + +#: ../objectstorage_tenant_specific_image_storage.rst:20 +msgid "Set these configuration options in the :file:`glance-api.conf` file:" +msgstr "" + +#: ../objectstorage_tenant_specific_image_storage.rst:23 +msgid "" +"Set to ``True`` to enable tenant-specific storage locations. Default is " +"``False``." +msgstr "" + +#: ../objectstorage_tenant_specific_image_storage.rst:24 +msgid "swift_store_multi_tenant" +msgstr "" + +#: ../objectstorage_tenant_specific_image_storage.rst:27 +msgid "" +"Specify a list of tenant IDs that can grant read and write access to all " +"Object Storage containers that are created by the Image service." +msgstr "" + +#: ../objectstorage_tenant_specific_image_storage.rst:28 +msgid "swift_store_admin_tenants" +msgstr "" + +#: ../objectstorage_tenant_specific_image_storage.rst:30 +msgid "" +"With this configuration, images are stored in an Object Storage service " +"(swift) endpoint that is pulled from the service catalog for the " +"authenticated user." +msgstr "" + +#: ../orchestration-auth-model.rst:8 +msgid "Orchestration authorization model" +msgstr "" + +#: ../orchestration-auth-model.rst:11 +msgid "" +"Orchestration authorization model defines the process of authorization that " +"orchestration module uses to authorize requests during so called deferred " +"operations. The typical example of such operation is autoscaling group " +"update when Orchestration requests other components (OpenStack Compute, " +"Openstack Networking or others) to extend (reduce) capacity of autoscaling " +"group." +msgstr "" + +#: ../orchestration-auth-model.rst:18 +msgid "Currently, Orchestration provides two kinds of authorization models:" +msgstr "" + +#: ../orchestration-auth-model.rst:20 +msgid "Password authorization," +msgstr "" + +#: ../orchestration-auth-model.rst:22 +msgid "Authorization with OpenStack Identity trusts." +msgstr "" + +#: ../orchestration-auth-model.rst:25 +msgid "Password authorization" +msgstr "" + +#: ../orchestration-auth-model.rst:27 +msgid "" +"Password authorization is the initial authorization model that was supported " +"by Orchestration module. This kind of authorization requires from a user to " +"pass a password to Orchestration. Orchestration stores the encrypted " +"password in the database and uses it for deferred operations." +msgstr "" + +#: ../orchestration-auth-model.rst:33 +msgid "The following steps are executed for password authorization:" +msgstr "" + +#: ../orchestration-auth-model.rst:35 +msgid "" +"User requests a stack creation, providing a token and username/password " +"(python-heatclient or OpenStack dashboard normally requests the token for " +"you)." +msgstr "" + +#: ../orchestration-auth-model.rst:39 +msgid "" +"If the stack contains any resources marked as requiring deferred operations, " +"orchestration engine will fail validation checks if no username/password is " +"provided." +msgstr "" + +#: ../orchestration-auth-model.rst:43 +msgid "The username/password are encrypted and stored in the Orchestration DB." +msgstr "" + +#: ../orchestration-auth-model.rst:46 +msgid "Stack creation is completed." +msgstr "" + +#: ../orchestration-auth-model.rst:48 +msgid "" +"At some later stage, Orchestration retrieves the credentials and requests " +"another token on behalf of the user. The token is not limited in scope and " +"provides access to all the roles of the stack owner." +msgstr "" + +#: ../orchestration-auth-model.rst:54 +msgid "Keystone trusts authorization" +msgstr "" + +#: ../orchestration-auth-model.rst:56 +msgid "" +"OpenStack Identity trusts is a new authorization method available since the " +"Icehouse release." +msgstr "" + +#: ../orchestration-auth-model.rst:59 +msgid "" +"A trust is an OpenStack Identity extension that provides a method to enable " +"delegation, and optionally impersonation via OpenStack Identity. The key " +"terminology is *trustor* (the user delegating) and *trustee* (the user being " +"delegated to)." +msgstr "" + +#: ../orchestration-auth-model.rst:64 +msgid "" +"To create a trust, the *trustor* (in this case, the user creating the stack " +"in Orchestration module) provides OpenStack Identity with the following " +"information:" +msgstr "" + +#: ../orchestration-auth-model.rst:68 +msgid "" +"The ID of the *trustee* (who you want to delegate to, in this case, the " +"Orchestration module user)." +msgstr "" + +#: ../orchestration-auth-model.rst:71 +msgid "" +"The roles to be delegated (configurable via the ``heat.conf``, but it needs " +"to contain whatever roles are required to perform the deferred operations on " +"the users behalf, for example, launching an OpenStack Compute instance in " +"response to an AutoScaling event)." +msgstr "" + +#: ../orchestration-auth-model.rst:76 +msgid "Whether to enable impersonation." +msgstr "" + +#: ../orchestration-auth-model.rst:78 +msgid "" +"OpenStack Identity then provides a trust_id, which can be consumed by *only* " +"the trustee to obtain a *trust scoped token*. This token is limited in scope " +"such that the trustee has limited access to those roles delegated, along " +"with effective impersonation of the trustor user if it was selected when " +"creating the trust. More information is available in the :ref:`Identity " +"management ` section." +msgstr "" + +#: ../orchestration-auth-model.rst:86 +msgid "The following steps are executed for trusts authorization:" +msgstr "" + +#: ../orchestration-auth-model.rst:88 +msgid "User creates a stack via an API request (only the token is required)." +msgstr "" + +#: ../orchestration-auth-model.rst:91 +msgid "" +"Orchestration uses the token to create a trust between the stack owner " +"(trustor) and the Orchestration module user (trustee), delegating a special " +"role (or roles) as defined in the *trusts_delegated_roles* list in the " +"Orchestration configuration file. By default, Orchestration module sets all " +"the roles from trustor available for trustee. Deployers may modify this list " +"to reflect local RBAC policy, for example, to ensure the heat process can " +"only access those services expected while impersonating a stack owner." +msgstr "" + +#: ../orchestration-auth-model.rst:101 +msgid "Orchestration stores the encrypted *trust id* in the Orchestration DB." +msgstr "" + +#: ../orchestration-auth-model.rst:104 +msgid "" +"When a deferred operation is required, Orchestration retrieves the *trust " +"id* and requests a trust scoped token which enables the service user to " +"impersonate the stack owner for the duration of the deferred operation, for " +"example, to launch some OpenStack Compute instances on behalf of the stack " +"owner in response to an AutoScaling event." +msgstr "" + +#: ../orchestration-auth-model.rst:112 +msgid "Authorization model configuration" +msgstr "" + +#: ../orchestration-auth-model.rst:114 +msgid "" +"Password authorization model had been the default authorization model " +"enabled for the Orchestration module before the Kilo release. Since the Kilo " +"release, the trusts authorization model has been enabled by default." +msgstr "" + +#: ../orchestration-auth-model.rst:119 +msgid "" +"To enable the password authorization model, the following change should be " +"made in ``heat.conf``:" +msgstr "" + +#: ../orchestration-auth-model.rst:126 +msgid "" +"To enable the trusts authorization model, the following change should be " +"made in ``heat.conf``:" +msgstr "" + +#: ../orchestration-auth-model.rst:133 +msgid "" +"To specify the trustor roles that it delegates to trustee during " +"authorization, the ``trusts_delegated_roles`` parameter should be specified " +"in ``heat.conf``. If ``trusts_delegated_roles`` is not defined, then all the " +"trustor roles are delegated to trustee." +msgstr "" + +#: ../orchestration-auth-model.rst:140 +msgid "" +"The trustor delegated roles should be pre-configured in the OpenStack " +"Identity before using it in the Orchestration module." +msgstr "" + +#: ../orchestration-introduction.rst:5 +msgid "" +"Orchestration is a tool for orchestrating clouds that automatically " +"configures and deploys resources in stacks. Such deployments can be simple — " +"like deploying WordPress on Ubuntu with an SQL back end. And they can be " +"quite complex, like launching a group of servers that autoscale: starting " +"and stopping based on realtime CPU loading information from the Telemetry " +"module." +msgstr "" + +#: ../orchestration-introduction.rst:12 +msgid "" +"Orchestration stacks are defined with templates, which are non-procedural " +"documents describing tasks in terms of resources, parameters, inputs, " +"constraints and dependencies. When Orchestration module was originally " +"introduced, it worked with AWS CloudFormation templates, which are in JSON " +"format." +msgstr "" + +#: ../orchestration-introduction.rst:18 +msgid "" +"Now, Orchestration also executes HOT (Heat Orchestration Template) templates " +"written in YAML: a terse notation that loosely follows Python/Ruby-type " +"structural conventions (colons, returns, indentation), so it is more easy to " +"write, parse, grep, generate with tools, and maintain source-code management " +"systems." +msgstr "" + +#: ../orchestration-introduction.rst:24 +msgid "" +"Orchestration can be accessed via the CLI, and using RESTful queries. " +"Orchestration module provides both an OpenStack-native REST API and a " +"CloudFormation-compatible Query API. Orchestration is also integrated with " +"OpenStack dashboard in order to launch stacks from templates through a web " +"interface." +msgstr "" + +#: ../orchestration-introduction.rst:30 +msgid "" +"For more details on how to use Orchestration module through a command line, " +"see `OpenStack Command-Line Interface Reference`_." +msgstr "" + +#: ../orchestration-stack-domain-users.rst:7 +msgid "Stack domain users" +msgstr "" + +#: ../orchestration-stack-domain-users.rst:9 +msgid "" +"Orchestration stack domain users allows Orchestration module to authorize " +"inside VMs booted and execute the following operations:" +msgstr "" + +#: ../orchestration-stack-domain-users.rst:12 +msgid "" +"Provide metadata to agents inside instances, which poll for changes and " +"apply the configuration expressed in the metadata to the instance." +msgstr "" + +#: ../orchestration-stack-domain-users.rst:16 +msgid "" +"Detect signal completion of some action, typically configuration of software " +"on a VM after it is booted (because OpenStack Compute moves the state of a " +"VM to \"Active\" as soon as it spawns it, not when Orchestration has fully " +"configured it)." +msgstr "" + +#: ../orchestration-stack-domain-users.rst:21 +msgid "" +"Provide application level status or meters from inside the instance. For " +"example, allow AutoScaling actions to be performed in response to some " +"measure of performance or quality of service." +msgstr "" + +#: ../orchestration-stack-domain-users.rst:25 +msgid "" +"Orchestration provides APIs which enable all of these things, but all of " +"those APIs require some sort of authentication. For example, credentials to " +"access the instance agent is running on. The heat-cfntools agents use signed " +"requests, which requires an ec2 keypair created via OpenStack Identity, " +"which is then used to sign requests to the Orchestration CloudFormation and " +"CloudWatch compatible APIs, which are authenticated by Orchestration via " +"signature validation (which uses the OpenStack Identity ec2tokens " +"extension). Stack domain users allow to encapsulate all stack-defined users " +"(users created as a result of things contained in an Orchestration template) " +"in a separate domain which is created specifically to contain things related " +"only to the Orchestration stacks. A user is created which is the *domain " +"admin*, and Orchestration uses that user to manage the lifecycle of the " +"users in the stack *user domain*." +msgstr "" + +#: ../orchestration-stack-domain-users.rst:41 +msgid "Stack domain users configuration" +msgstr "" + +#: ../orchestration-stack-domain-users.rst:43 +msgid "To configure stack domain users the following steps shall be executed:" +msgstr "" + +#: ../orchestration-stack-domain-users.rst:45 +msgid "" +"A special OpenStack Identity service domain is created. For example, the one " +"called ``heat`` and the ID is set in the ``stack_user_domain`` option in :" +"file:`heat.conf`." +msgstr "" + +#: ../orchestration-stack-domain-users.rst:48 +msgid "" +"A user with sufficient permissions to create and delete projects and users " +"in the ``heat`` domain is created." +msgstr "" + +#: ../orchestration-stack-domain-users.rst:50 +msgid "" +"The username and password for the domain admin user is set in :file:`heat." +"conf` (``stack_domain_admin`` and ``stack_domain_admin_password``). This " +"user administers *stack domain users* on behalf of stack owners, so they no " +"longer need to be admins themselves, and the risk of this escalation path is " +"limited because the ``heat_domain_admin`` is only given administrative " +"permission for the ``heat`` domain." +msgstr "" + +#: ../orchestration-stack-domain-users.rst:58 +msgid "You must complete the following steps to setup stack domain users:" +msgstr "" + +#: ../orchestration-stack-domain-users.rst:60 +msgid "Create the domain:" +msgstr "" + +#: ../orchestration-stack-domain-users.rst:62 +msgid "" +"``$OS_TOKEN`` refers to a token. For example, the service admin token or " +"some other valid token for a user with sufficient roles to create users and " +"domains. ``$KS_ENDPOINT_V3`` refers to the v3 OpenStack Identity endpoint " +"(for example, ``http://keystone_address:5000/v3`` where *keystone_address* " +"is the IP address or resolvable name for the OpenStack Identity service)." +msgstr "" + +#: ../orchestration-stack-domain-users.rst:76 +msgid "" +"The domain ID is returned by this command, and is referred to as ``" +"$HEAT_DOMAIN_ID`` below." +msgstr "" + +#: ../orchestration-stack-domain-users.rst:79 +msgid "Create the user::" +msgstr "" + +#: ../orchestration-stack-domain-users.rst:86 +msgid "" +"The user ID is returned by this command and is referred to as ``" +"$DOMAIN_ADMIN_ID`` below." +msgstr "" + +#: ../orchestration-stack-domain-users.rst:89 +msgid "Make the user a domain admin::" +msgstr "" + +#: ../orchestration-stack-domain-users.rst:95 +msgid "" +"Then you need to add the domain ID, username and password from these steps " +"to :file:`heat.conf`:" +msgstr "" + +#: ../orchestration-stack-domain-users.rst:106 +msgid "Usage workflow" +msgstr "" + +#: ../orchestration-stack-domain-users.rst:108 +msgid "The following steps will be executed during stack creation:" +msgstr "" + +#: ../orchestration-stack-domain-users.rst:110 +msgid "" +"Orchestration creates a new *stack domain project* in the ``heat`` domain if " +"the stack contains any resources which require creation of a *stack domain " +"user*." msgstr "" #: ../orchestration-stack-domain-users.rst:114 @@ -7076,8 +18387,1380 @@ msgid "" "ref:`OpenStack Identity documentation ` for more info)." msgstr "" +#: ../orchestration-stack-domain-users.rst:124 +msgid "" +"When API requests are processed, Orchestration does an internal lookup and " +"allows stack details for a given stack to be retrieved from the database for " +"both the stack owner's project (the default API path to the stack) and the " +"stack domain project, subject to the :file:`policy.json` restrictions." +msgstr "" + +#: ../orchestration-stack-domain-users.rst:130 +msgid "" +"To clarify that last point, that means there are now two paths which can " +"result in retrieval of the same data via the Orchestration API. The example " +"for resource-metadata is below::" +msgstr "" + +#: ../orchestration-stack-domain-users.rst:137 +msgid "or::" +msgstr "" + +#: ../orchestration-stack-domain-users.rst:142 +msgid "" +"The stack owner uses the former (via ``heat resource-metadata {stack_name} " +"{resource_name}``), and any agents in the instance use the latter." +msgstr "" + +#: ../orchestration.rst:5 +msgid "Orchestration" +msgstr "" + +#: ../orchestration.rst:7 +msgid "" +"Orchestration is an orchestration engine that provides the possibility to " +"launch multiple composite cloud applications based on templates in the form " +"of text files that can be treated like code. A native Heat Orchestration " +"Template (HOT) format is evolving, but it also endeavors to provide " +"compatibility with the AWS CloudFormation template format, so that many " +"existing CloudFormation templates can be launched on OpenStack." +msgstr "" + +#: ../telemetry-alarms.rst:5 +msgid "Alarms" +msgstr "" + +#: ../telemetry-alarms.rst:7 +msgid "" +"Alarms provide user-oriented Monitoring-as-a-Service for resources running " +"on OpenStack. This type of monitoring ensures you can automatically scale in " +"or out a group of instances through the Orchestration module, but you can " +"also use alarms for general-purpose awareness of your cloud resources' " +"health." +msgstr "" + +#: ../telemetry-alarms.rst:13 +msgid "These alarms follow a tri-state model:" +msgstr "" + +#: ../telemetry-alarms.rst:16 +msgid "The rule governing the alarm has been evaluated as ``False``." +msgstr "" + +#: ../telemetry-alarms.rst:16 +msgid "ok" +msgstr "" + +#: ../telemetry-alarms.rst:19 +msgid "The rule governing the alarm have been evaluated as ``True``." +msgstr "" + +#: ../telemetry-alarms.rst:19 +msgid "alarm" +msgstr "" + +#: ../telemetry-alarms.rst:22 +msgid "" +"There are not enough datapoints available in the evaluation periods to " +"meaningfully determine the alarm state." +msgstr "" + +#: ../telemetry-alarms.rst:23 +msgid "insufficient data" +msgstr "" + +#: ../telemetry-alarms.rst:26 +msgid "Alarm definitions" +msgstr "" + +#: ../telemetry-alarms.rst:28 +msgid "" +"The definition of an alarm provides the rules that govern when a state " +"transition should occur, and the actions to be taken thereon. The nature of " +"these rules depend on the alarm type." +msgstr "" + +#: ../telemetry-alarms.rst:33 +msgid "Threshold rule alarms" +msgstr "" + +#: ../telemetry-alarms.rst:35 +msgid "" +"For conventional threshold-oriented alarms, state transitions are governed " +"by:" +msgstr "" + +#: ../telemetry-alarms.rst:38 +msgid "" +"A static threshold value with a comparison operator such as greater than or " +"less than." +msgstr "" + +#: ../telemetry-alarms.rst:41 +msgid "A statistic selection to aggregate the data." +msgstr "" + +#: ../telemetry-alarms.rst:43 +msgid "" +"A sliding time window to indicate how far back into the recent past you want " +"to look." +msgstr "" + +#: ../telemetry-alarms.rst:47 +msgid "Combination rule alarms" +msgstr "" + +#: ../telemetry-alarms.rst:49 +msgid "" +"The Telemetry module also supports the concept of a meta-alarm, which " +"aggregates over the current state of a set of underlying basic alarms " +"combined via a logical operator (AND or OR)." +msgstr "" + +#: ../telemetry-alarms.rst:54 +msgid "Alarm dimensioning" +msgstr "" + +#: ../telemetry-alarms.rst:56 +msgid "" +"A key associated concept is the notion of *dimensioning* which defines the " +"set of matching meters that feed into an alarm evaluation. Recall that " +"meters are per-resource-instance, so in the simplest case an alarm might be " +"defined over a particular meter applied to all resources visible to a " +"particular user. More useful however would be the option to explicitly " +"select which specific resources you are interested in alarming on." +msgstr "" + +#: ../telemetry-alarms.rst:64 +msgid "" +"At one extreme you might have narrowly dimensioned alarms where this " +"selection would have only a single target (identified by resource ID). At " +"the other extreme, you could have widely dimensioned alarms where this " +"selection identifies many resources over which the statistic is aggregated. " +"For example all instances booted from a particular image or all instances " +"with matching user metadata (the latter is how the Orchestration module " +"identifies autoscaling groups)." +msgstr "" + +#: ../telemetry-alarms.rst:74 +msgid "Alarm evaluation" +msgstr "" + +#: ../telemetry-alarms.rst:76 +msgid "" +"Alarms are evaluated by the ``alarm-evaluator`` service on a periodic basis, " +"defaulting to once every minute." +msgstr "" + +#: ../telemetry-alarms.rst:80 +msgid "Alarm actions" +msgstr "" + +#: ../telemetry-alarms.rst:82 +msgid "" +"Any state transition of individual alarm (to ``ok``, ``alarm``, or " +"``insufficient data``) may have one or more actions associated with it. " +"These actions effectively send a signal to a consumer that the state " +"transition has occurred, and provide some additional context. This includes " +"the new and previous states, with some reason data describing the " +"disposition with respect to the threshold, the number of datapoints involved " +"and most recent of these. State transitions are detected by the ``alarm-" +"evaluator``, whereas the ``alarm-notifier`` effects the actual notification " +"action." +msgstr "" + +#: ../telemetry-alarms.rst:92 +msgid "**Webhooks**" +msgstr "" + +#: ../telemetry-alarms.rst:94 +msgid "" +"These are the *de facto* notification type used by Telemetry alarming and " +"simply involve an HTTP POST request being sent to an endpoint, with a " +"request body containing a description of the state transition encoded as a " +"JSON fragment." +msgstr "" + +#: ../telemetry-alarms.rst:99 +msgid "**Log actions**" +msgstr "" + +#: ../telemetry-alarms.rst:101 +msgid "" +"These are a lightweight alternative to webhooks, whereby the state " +"transition is simply logged by the ``alarm-notifier``, and are intended " +"primarily for testing purposes." +msgstr "" + +#: ../telemetry-alarms.rst:106 +msgid "Workload partitioning" +msgstr "" + +#: ../telemetry-alarms.rst:108 +msgid "" +"The alarm evaluation process uses the same mechanism for workload " +"partitioning as the central and compute agents. The `Tooz `_ library provides the coordination within the groups " +"of service instances. For further information about this approach, see the " +"section called :ref:`Support for HA deployment of the central and compute " +"agent services `." +msgstr "" + +#: ../telemetry-alarms.rst:116 +msgid "" +"To use this workload partitioning solution set the ``evaluation_service`` " +"option to ``default``. For more information, see the alarm section in the " +"`OpenStack Configuration Reference `_." +msgstr "" + +#: ../telemetry-alarms.rst:122 +msgid "Using alarms" +msgstr "" + +#: ../telemetry-alarms.rst:125 +msgid "Alarm creation" +msgstr "" + +#: ../telemetry-alarms.rst:127 +msgid "" +"An example of creating a threshold-oriented alarm, based on an upper bound " +"on the CPU utilization for a particular instance:" +msgstr "" + +#: ../telemetry-alarms.rst:140 +msgid "" +"This creates an alarm that will fire when the average CPU utilization for an " +"individual instance exceeds 70% for three consecutive 10 minute periods. The " +"notification in this case is simply a log message, though it could " +"alternatively be a webhook URL." +msgstr "" + +#: ../telemetry-alarms.rst:146 +msgid "" +"Alarm names must be unique for the alarms associated with an individual " +"project. The cloud administrator can limit the maximum resulting actions for " +"three different states, and the ability for a normal user to create ``log://" +"`` and ``test://`` notifiers is disabled. This prevents unintentional " +"consumption of disk and memory resources by the Telemetry service." +msgstr "" + +#: ../telemetry-alarms.rst:154 +msgid "" +"The sliding time window over which the alarm is evaluated is 30 minutes in " +"this example. This window is not clamped to wall-clock time boundaries, " +"rather it's anchored on the current time for each evaluation cycle, and " +"continually creeps forward as each evaluation cycle rolls around (by " +"default, this occurs every minute)." +msgstr "" + +#: ../telemetry-alarms.rst:160 +msgid "" +"The period length is set to 600s in this case to reflect the out-of-the-box " +"default cadence for collection of the associated meter. This period matching " +"illustrates an important general principal to keep in mind for alarms:" +msgstr "" + +#: ../telemetry-alarms.rst:166 +msgid "" +"The alarm period should be a whole number multiple (1 or more) of the " +"interval configured in the pipeline corresponding to the target meter." +msgstr "" + +#: ../telemetry-alarms.rst:170 +msgid "" +"Otherwise the alarm will tend to flit in and out of the ``insufficient " +"data`` state due to the mismatch between the actual frequency of datapoints " +"in the metering store and the statistics queries used to compare against the " +"alarm threshold. If a shorter alarm period is needed, then the corresponding " +"interval should be adjusted in the :file:`pipeline.yaml` file." +msgstr "" + +#: ../telemetry-alarms.rst:177 +msgid "" +"Other notable alarm attributes that may be set on creation, or via a " +"subsequent update, include:" +msgstr "" + +#: ../telemetry-alarms.rst:181 +msgid "The initial alarm state (defaults to ``insufficient data``)." +msgstr "" + +#: ../telemetry-alarms.rst:181 +msgid "state" +msgstr "" + +#: ../telemetry-alarms.rst:184 +msgid "" +"A free-text description of the alarm (defaults to a synopsis of the alarm " +"rule)." +msgstr "" + +#: ../telemetry-alarms.rst:185 +msgid "description" +msgstr "" + +#: ../telemetry-alarms.rst:188 +msgid "" +"True if evaluation and actioning is to be enabled for this alarm (defaults " +"to True)." +msgstr "" + +#: ../telemetry-alarms.rst:192 +msgid "" +"True if actions should be repeatedly notified while the alarm remains in the " +"target state (defaults to False)." +msgstr "" + +#: ../telemetry-alarms.rst:193 +msgid "repeat-actions" +msgstr "" + +#: ../telemetry-alarms.rst:196 +msgid "An action to invoke when the alarm state transitions to ``ok``." +msgstr "" + +#: ../telemetry-alarms.rst:196 +msgid "ok-action" +msgstr "" + +#: ../telemetry-alarms.rst:199 +msgid "" +"An action to invoke when the alarm state transitions to ``insufficient " +"data``." +msgstr "" + +#: ../telemetry-alarms.rst:200 +msgid "insufficient-data-action" +msgstr "" + +#: ../telemetry-alarms.rst:203 +msgid "" +"Used to restrict evaluation of the alarm to certain times of the day or days " +"of the week (expressed as ``cron`` expression with an optional timezone)." +msgstr "" + +#: ../telemetry-alarms.rst:205 +msgid "time-constraint" +msgstr "" + +#: ../telemetry-alarms.rst:207 +msgid "" +"An example of creating a combination alarm, based on the combined state of " +"two underlying alarms:" +msgstr "" + +#: ../telemetry-alarms.rst:218 +msgid "" +"This creates an alarm that will fire when either one of two underlying " +"alarms transition into the alarm state. The notification in this case is a " +"webhook call. Any number of underlying alarms can be combined in this way, " +"using either ``and`` or ``or``." +msgstr "" + +#: ../telemetry-alarms.rst:224 +msgid "Alarm retrieval" +msgstr "" + +#: ../telemetry-alarms.rst:226 +msgid "" +"You can display all your alarms via (some attributes are omitted for " +"brevity):" +msgstr "" + +#: ../telemetry-alarms.rst:238 +msgid "" +"In this case, the state is reported as ``insufficient data`` which could " +"indicate that:" +msgstr "" + +#: ../telemetry-alarms.rst:241 +msgid "" +"meters have not yet been gathered about this instance over the evaluation " +"window into the recent past (for example a brand-new instance)" +msgstr "" + +#: ../telemetry-alarms.rst:245 +msgid "" +"*or*, that the identified instance is not visible to the user/tenant owning " +"the alarm" +msgstr "" + +#: ../telemetry-alarms.rst:248 +msgid "" +"*or*, simply that an alarm evaluation cycle hasn't kicked off since the " +"alarm was created (by default, alarms are evaluated once per minute)." +msgstr "" + +#: ../telemetry-alarms.rst:253 +msgid "" +"The visibility of alarms depends on the role and project associated with the " +"user issuing the query:" +msgstr "" + +#: ../telemetry-alarms.rst:256 +msgid "admin users see *all* alarms, regardless of the owner" +msgstr "" + +#: ../telemetry-alarms.rst:258 +msgid "" +"on-admin users see only the alarms associated with their project (as per the " +"normal tenant segregation in OpenStack)" +msgstr "" + +#: ../telemetry-alarms.rst:262 +msgid "Alarm update" +msgstr "" + +#: ../telemetry-alarms.rst:264 +msgid "" +"Once the state of the alarm has settled down, we might decide that we set " +"that bar too low with 70%, in which case the threshold (or most any other " +"alarm attribute) can be updated thusly:" +msgstr "" + +#: ../telemetry-alarms.rst:272 +msgid "" +"The change will take effect from the next evaluation cycle, which by default " +"occurs every minute." +msgstr "" + +#: ../telemetry-alarms.rst:275 +msgid "" +"Most alarm attributes can be changed in this way, but there is also a " +"convenient short-cut for getting and setting the alarm state:" +msgstr "" + +#: ../telemetry-alarms.rst:283 +msgid "" +"Over time the state of the alarm may change often, especially if the " +"threshold is chosen to be close to the trending value of the statistic. You " +"can follow the history of an alarm over its lifecycle via the audit API:" +msgstr "" + +#: ../telemetry-alarms.rst:303 +msgid "Alarm deletion" +msgstr "" + +#: ../telemetry-alarms.rst:305 +msgid "" +"An alarm that is no longer required can be disabled so that it is no longer " +"actively evaluated:" +msgstr "" + +#: ../telemetry-alarms.rst:312 +msgid "or even deleted permanently (an irreversible step):" +msgstr "" + +#: ../telemetry-alarms.rst:319 +msgid "By default, alarm history is retained for deleted alarms." +msgstr "" + +#: ../telemetry-best-practices.rst:2 +msgid "Telemetry best practices" +msgstr "" + +#: ../telemetry-best-practices.rst:4 +msgid "" +"The following are some suggested best practices to follow when deploying and " +"configuring the Telemetry service. The best practices are divided into data " +"collection and storage." +msgstr "" + +# #-#-#-#-# telemetry-best-practices.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +# #-#-#-#-# telemetry-data-collection.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +#: ../telemetry-best-practices.rst:9 ../telemetry-data-collection.rst:8 +msgid "Data collection" +msgstr "" + +#: ../telemetry-best-practices.rst:11 +msgid "" +"The Telemetry module collects a continuously growing set of data. Not all " +"the data will be relevant for a cloud administrator to monitor." +msgstr "" + +#: ../telemetry-best-practices.rst:14 +msgid "" +"Based on your needs, you can edit the :file:`pipeline.yaml` configuration " +"file to include a selected number of meters while disregarding the rest." +msgstr "" + +#: ../telemetry-best-practices.rst:18 +msgid "" +"By default, Telemetry service polls the service APIs every 10 minutes. You " +"can change the polling interval on a per meter basis by editing the :file:" +"`pipeline.yaml` configuration file." +msgstr "" + +#: ../telemetry-best-practices.rst:24 +msgid "" +"If the polling interval is too short, it will likely cause increase of " +"stored data and the stress on the service APIs." +msgstr "" + +#: ../telemetry-best-practices.rst:27 +msgid "" +"Expand the configuration to have greater control over different meter " +"intervals." +msgstr "" + +#: ../telemetry-best-practices.rst:32 +msgid "For more information, see the :ref:`telemetry-pipeline-configuration`." +msgstr "" + +#: ../telemetry-best-practices.rst:35 +msgid "" +"If you are using the Kilo version of Telemetry, you can delay or adjust " +"polling requests by enabling the jitter support. This adds a random delay on " +"how the polling agents send requests to the service APIs. To enable jitter, " +"set ``shuffle_time_before_polling_task`` in the :file:`ceilometer.conf` " +"configuration file to an integer greater than 0." +msgstr "" + +#: ../telemetry-best-practices.rst:42 +msgid "" +"If you are using Juno or later releases, based on the number of resources " +"that will be polled, you can add additional central and compute agents as " +"necessary. The agents are designed to scale horizontally." +msgstr "" + +#: ../telemetry-best-practices.rst:49 +msgid "For more information see, :ref:`ha-deploy-services`." +msgstr "" + +#: ../telemetry-best-practices.rst:51 +msgid "" +"If you are using Juno or later releases, use the ``notifier://`` publisher " +"rather than ``rpc://`` as there is a certain level of overhead that comes " +"with RPC." +msgstr "" + +#: ../telemetry-best-practices.rst:57 +msgid "" +"For more information on RPC overhead, see `RPC overhead info `__." +msgstr "" + +#: ../telemetry-best-practices.rst:62 +msgid "Data storage" +msgstr "" + +#: ../telemetry-best-practices.rst:64 +msgid "" +"We recommend that you avoid open-ended queries. In order to get better " +"performance you can use reasonable time ranges and/or other query " +"constraints for retrieving measurements." +msgstr "" + +#: ../telemetry-best-practices.rst:68 +msgid "" +"For example, this open-ended query might return an unpredictable amount of " +"data:" +msgstr "" + +#: ../telemetry-best-practices.rst:75 +msgid "" +"Whereas, this well-formed query returns a more reasonable amount of data, " +"hence better performance:" +msgstr "" + +# #-#-#-#-# telemetry-best-practices.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +# #-#-#-#-# telemetry-data-retrieval.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +#: ../telemetry-best-practices.rst:84 ../telemetry-data-retrieval.rst:431 +msgid "" +"As of the Liberty release, the number of items returned will be restricted " +"to the value defined by ``default_api_return_limit`` in the :file:" +"`ceilometer.conf` configuration file. Alternatively, the value can be set " +"per query by passing ``limit`` option in request." +msgstr "" + +#: ../telemetry-best-practices.rst:89 +msgid "" +"You can install the API behind ``mod_wsgi``, as it provides more settings to " +"tweak, like ``threads`` and ``processes`` in case of ``WSGIDaemon``." +msgstr "" + +#: ../telemetry-best-practices.rst:95 +msgid "" +"For more information on how to configure ``mod_wsgi``, see the `Telemetry " +"Install Documentation `__." +msgstr "" + +#: ../telemetry-best-practices.rst:99 +msgid "" +"The collection service provided by the Telemetry project is not intended to " +"be an archival service. Set a Time to Live (TTL) value to expire data and " +"minimize the database size. If you would like to keep your data for longer " +"time period, you may consider storing it in a data warehouse outside of " +"Telemetry." +msgstr "" + +#: ../telemetry-best-practices.rst:107 +msgid "" +"For more information on how to set the TTL, see :ref:`telemetry-storing-" +"samples`." +msgstr "" + +#: ../telemetry-best-practices.rst:110 +msgid "" +"We recommend that you do not use SQLAlchemy back end prior to the Juno " +"release, as it previously contained extraneous relationships to handle " +"deprecated data models. This resulted in extremely poor query performance." +msgstr "" + +#: ../telemetry-best-practices.rst:115 +msgid "" +"We recommend that you do not run MongoDB on the same node as the controller. " +"Keep it on a separate node optimized for fast storage for better " +"performance. Also it is advisable for the MongoDB node to have a lot of " +"memory." +msgstr "" + +#: ../telemetry-best-practices.rst:122 +msgid "" +"For more information on how much memory you need, see `MongoDB FAQ `__." +msgstr "" + +#: ../telemetry-best-practices.rst:125 +msgid "" +"Use replica sets in MongoDB. Replica sets provide high availability through " +"automatic failover. If your primary node fails, MongoDB will elect a " +"secondary node to replace the primary node, and your cluster will remain " +"functional." +msgstr "" + +#: ../telemetry-best-practices.rst:130 +msgid "" +"For more information on replica sets, see the `MongoDB replica sets docs " +"`__." +msgstr "" + +#: ../telemetry-best-practices.rst:133 +msgid "" +"Use sharding in MongoDB. Sharding helps in storing data records across " +"multiple machines and is the MongoDB’s approach to meet the demands of data " +"growth." +msgstr "" + +#: ../telemetry-best-practices.rst:137 +msgid "" +"For more information on sharding, see the `MongoDB sharding docs `__." +msgstr "" + +#: ../telemetry-data-collection.rst:10 +msgid "" +"The main responsibility of Telemetry in OpenStack is to collect information " +"about the system that can be used by billing systems or interpreted by " +"analytic tooling. The original focus, regarding to the collected data, was " +"on the counters that can be used for billing, but the range is getting wider " +"continuously." +msgstr "" + +#: ../telemetry-data-collection.rst:16 +msgid "" +"Collected data can be stored in the form of samples or events in the " +"supported databases, listed in :ref:`telemetry-supported-databases`." +msgstr "" + +#: ../telemetry-data-collection.rst:19 +msgid "" +"Samples can have various sources regarding to the needs and configuration of " +"Telemetry, which requires multiple methods to collect data." +msgstr "" + +#: ../telemetry-data-collection.rst:23 +msgid "The available data collection mechanisms are:" +msgstr "" + +#: ../telemetry-data-collection.rst:26 +msgid "" +"Processing notifications from other OpenStack services, by consuming " +"messages from the configured message queue system." +msgstr "" + +#: ../telemetry-data-collection.rst:30 +msgid "" +"Retrieve information directly from the hypervisor or from the host machine " +"using SNMP, or by using the APIs of other OpenStack services." +msgstr "" + +#: ../telemetry-data-collection.rst:32 ../telemetry-data-collection.rst:207 +msgid "Polling" +msgstr "" + +#: ../telemetry-data-collection.rst:35 +msgid "Pushing samples via the RESTful API of Telemetry." +msgstr "" + +#: ../telemetry-data-collection.rst:35 +msgid "RESTful API" +msgstr "" + +#: ../telemetry-data-collection.rst:39 +msgid "" +"All the services send notifications about the executed operations or system " +"state in OpenStack. Several notifications carry information that can be " +"metered, like the CPU time of a VM instance created by OpenStack Compute " +"service." +msgstr "" + +#: ../telemetry-data-collection.rst:44 +msgid "" +"The Telemetry module has a separate agent that is responsible for consuming " +"notifications, namely the notification agent. This component is responsible " +"for consuming from the message bus and transforming notifications into " +"events and measurement samples. Beginning in the Liberty release, the " +"notification agent is responsible for all data processing such as " +"transformations and publishing. After processing, the data is sent via AMQP " +"to the collector service or any external service, which is responsible for " +"persisting the data into the configured database back end." +msgstr "" + +#: ../telemetry-data-collection.rst:54 +msgid "" +"The different OpenStack services emit several notifications about the " +"various types of events that happen in the system during normal operation. " +"Not all these notifications are consumed by the Telemetry module, as the " +"intention is only to capture the billable events and notifications that can " +"be used for monitoring or profiling purposes. The notification agent filters " +"by the event type, that is contained by each notification message. The " +"following table contains the event types by each OpenStack service that are " +"transformed to samples by Telemetry." +msgstr "" + +#: ../telemetry-data-collection.rst:64 +msgid "Event types" +msgstr "" + +# #-#-#-#-# telemetry-data-collection.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +# #-#-#-#-# telemetry-measurements.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +#: ../telemetry-data-collection.rst:64 ../telemetry-data-collection.rst:1044 +#: ../telemetry-measurements.rst:97 ../telemetry-measurements.rst:430 +#: ../telemetry-measurements.rst:484 ../telemetry-measurements.rst:528 +#: ../telemetry-measurements.rst:589 ../telemetry-measurements.rst:664 +#: ../telemetry-measurements.rst:697 ../telemetry-measurements.rst:752 +#: ../telemetry-measurements.rst:802 ../telemetry-measurements.rst:839 +#: ../telemetry-measurements.rst:910 ../telemetry-measurements.rst:973 +#: ../telemetry-measurements.rst:1059 ../telemetry-measurements.rst:1137 +#: ../telemetry-measurements.rst:1202 ../telemetry-measurements.rst:1253 +#: ../telemetry-measurements.rst:1279 ../telemetry-measurements.rst:1302 +#: ../telemetry-measurements.rst:1322 +msgid "Note" +msgstr "" + +#: ../telemetry-data-collection.rst:64 +msgid "OpenStack service" +msgstr "" + +#: ../telemetry-data-collection.rst:66 +msgid "" +"For a more detailed list of Compute notifications please check the `System " +"Usage Data Data wiki page `__." +msgstr "" + +# #-#-#-#-# telemetry-data-collection.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +# #-#-#-#-# telemetry-measurements.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +#: ../telemetry-data-collection.rst:66 ../telemetry-measurements.rst:93 +msgid "OpenStack Compute" +msgstr "" + +#: ../telemetry-data-collection.rst:66 +msgid "scheduler.run\\_insta\\ nce.scheduled" +msgstr "" + +#: ../telemetry-data-collection.rst:69 +msgid "scheduler.select\\_\\ destinations" +msgstr "" + +#: ../telemetry-data-collection.rst:72 +msgid "compute.instance.\\*" +msgstr "" + +# #-#-#-#-# telemetry-data-collection.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +# #-#-#-#-# telemetry-measurements.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +#: ../telemetry-data-collection.rst:74 ../telemetry-measurements.rst:468 +msgid "Bare metal service" +msgstr "" + +#: ../telemetry-data-collection.rst:74 +msgid "hardware.ipmi.\\*" +msgstr "" + +# #-#-#-#-# telemetry-data-collection.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +# #-#-#-#-# telemetry-measurements.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +#: ../telemetry-data-collection.rst:76 ../telemetry-measurements.rst:660 +msgid "OpenStack Image service" +msgstr "" + +#: ../telemetry-data-collection.rst:76 +msgid "" +"The required configuration for Image service can be found in `Configure the " +"Image service for Telemetry section `__ section in the " +"OpenStack Installation Guide." +msgstr "" + +# #-#-#-#-# telemetry-data-collection.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +# #-#-#-#-# telemetry-measurements.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +#: ../telemetry-data-collection.rst:76 ../telemetry-measurements.rst:676 +msgid "image.update" +msgstr "" + +# #-#-#-#-# telemetry-data-collection.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +# #-#-#-#-# telemetry-measurements.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +#: ../telemetry-data-collection.rst:78 ../telemetry-measurements.rst:679 +msgid "image.upload" +msgstr "" + +# #-#-#-#-# telemetry-data-collection.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +# #-#-#-#-# telemetry-measurements.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +#: ../telemetry-data-collection.rst:80 ../telemetry-measurements.rst:682 +msgid "image.delete" +msgstr "" + +#: ../telemetry-data-collection.rst:82 +msgid "image.send" +msgstr "" + +# #-#-#-#-# telemetry-data-collection.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +# #-#-#-#-# telemetry-measurements.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +#: ../telemetry-data-collection.rst:87 ../telemetry-data-collection.rst:268 +#: ../telemetry-measurements.rst:906 +msgid "OpenStack Networking" +msgstr "" + +#: ../telemetry-data-collection.rst:87 +msgid "floatingip.create.end" +msgstr "" + +#: ../telemetry-data-collection.rst:89 +msgid "floatingip.update.\\*" +msgstr "" + +#: ../telemetry-data-collection.rst:91 +msgid "floatingip.exists" +msgstr "" + +#: ../telemetry-data-collection.rst:93 +msgid "network.create.end" +msgstr "" + +#: ../telemetry-data-collection.rst:95 +msgid "network.update.\\*" +msgstr "" + +#: ../telemetry-data-collection.rst:97 +msgid "network.exists" +msgstr "" + +#: ../telemetry-data-collection.rst:99 +msgid "port.create.end" +msgstr "" + +#: ../telemetry-data-collection.rst:101 +msgid "port.update.\\*" +msgstr "" + +#: ../telemetry-data-collection.rst:103 +msgid "port.exists" +msgstr "" + +#: ../telemetry-data-collection.rst:105 +msgid "router.create.end" +msgstr "" + +#: ../telemetry-data-collection.rst:107 +msgid "router.update.\\*" +msgstr "" + +#: ../telemetry-data-collection.rst:109 +msgid "router.exists" +msgstr "" + +#: ../telemetry-data-collection.rst:111 +msgid "subnet.create.end" +msgstr "" + +#: ../telemetry-data-collection.rst:113 +msgid "subnet.update.\\*" +msgstr "" + +#: ../telemetry-data-collection.rst:115 +msgid "subnet.exists" +msgstr "" + +#: ../telemetry-data-collection.rst:117 +msgid "l3.meter" +msgstr "" + +# #-#-#-#-# telemetry-data-collection.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +# #-#-#-#-# telemetry-measurements.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +#: ../telemetry-data-collection.rst:119 ../telemetry-measurements.rst:1249 +msgid "Orchestration module" +msgstr "" + +#: ../telemetry-data-collection.rst:119 +msgid "orchestration.stack\\ .create.end" +msgstr "" + +#: ../telemetry-data-collection.rst:122 +msgid "orchestration.stack\\ .update.end" +msgstr "" + +#: ../telemetry-data-collection.rst:125 +msgid "orchestration.stack\\ .delete.end" +msgstr "" + +#: ../telemetry-data-collection.rst:128 +msgid "orchestration.stack\\ .resume.end" +msgstr "" + +#: ../telemetry-data-collection.rst:131 +msgid "orchestration.stack\\ .suspend.end" +msgstr "" + +# #-#-#-#-# telemetry-data-collection.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +# #-#-#-#-# telemetry-measurements.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +#: ../telemetry-data-collection.rst:134 ../telemetry-data-collection.rst:272 +#: ../telemetry-measurements.rst:693 +msgid "OpenStack Block Storage" +msgstr "" + +#: ../telemetry-data-collection.rst:134 +msgid "" +"The required configuration for Block Storage service can be found in the " +"`Add the Block Storage service agent for Telemetry section `__ section in the OpenStack Installation Guide." +msgstr "" + +#: ../telemetry-data-collection.rst:134 +msgid "volume.exists" +msgstr "" + +#: ../telemetry-data-collection.rst:136 +msgid "volume.create.\\*" +msgstr "" + +#: ../telemetry-data-collection.rst:138 +msgid "volume.delete.\\*" +msgstr "" + +#: ../telemetry-data-collection.rst:140 +msgid "volume.update.\\*" +msgstr "" + +#: ../telemetry-data-collection.rst:142 +msgid "volume.resize.\\*" +msgstr "" + +#: ../telemetry-data-collection.rst:144 +msgid "volume.attach.\\*" +msgstr "" + +#: ../telemetry-data-collection.rst:146 +msgid "volume.detach.\\*" +msgstr "" + +#: ../telemetry-data-collection.rst:148 +msgid "snapshot.exists" +msgstr "" + +#: ../telemetry-data-collection.rst:150 +msgid "snapshot.create.\\*" +msgstr "" + +#: ../telemetry-data-collection.rst:152 +msgid "snapshot.delete.\\*" +msgstr "" + +#: ../telemetry-data-collection.rst:154 +msgid "snapshot.update.\\*" +msgstr "" + +#: ../telemetry-data-collection.rst:159 +msgid "" +"Some services require additional configuration to emit the notifications " +"using the correct control exchange on the message queue and so forth. These " +"configuration needs are referred in the above table for each OpenStack " +"service that needs it." +msgstr "" + +#: ../telemetry-data-collection.rst:164 +msgid "" +"Specific notifications from the Compute service are important for " +"administrators and users. Configuring nova_notifications in the :file:`nova." +"conf` file allows administrators to respond to events rapidly. For more " +"information on configuring notifications for the compute service, see " +"`Chapter 11 on Telemetry services `__ in the OpenStack " +"Installation Guide." +msgstr "" + +#: ../telemetry-data-collection.rst:175 +msgid "" +"When the ``store_events`` option is set to True in :file:`ceilometer.conf`, " +"Prior to the Kilo release, the notification agent needed database access in " +"order to work properly." +msgstr "" + +#: ../telemetry-data-collection.rst:180 +msgid "Middleware for the OpenStack Object Storage service" +msgstr "" + +#: ../telemetry-data-collection.rst:181 +msgid "" +"A subset of Object Store statistics requires additional middleware to be " +"installed behind the proxy of Object Store. This additional component emits " +"notifications containing data-flow-oriented meters, namely the ``storage." +"objects.(incoming|outgoing).bytes values``. The list of these meters are " +"listed in :ref:`telemetry-object-storage-meter`, marked with " +"``notification`` as origin." +msgstr "" + +#: ../telemetry-data-collection.rst:188 +msgid "" +"The instructions on how to install this middleware can be found in " +"`Configure the Object Storage service for Telemetry `__ section " +"in the OpenStack Installation Guide." +msgstr "" + +#: ../telemetry-data-collection.rst:194 +msgid "Telemetry middleware" +msgstr "" + +#: ../telemetry-data-collection.rst:195 +msgid "" +"Telemetry provides the capability of counting the HTTP requests and " +"responses for each API endpoint in OpenStack. This is achieved by storing a " +"sample for each event marked as ``audit.http.request``, ``audit.http." +"response``, ``http.request`` or ``http.response``." +msgstr "" + +#: ../telemetry-data-collection.rst:200 +msgid "" +"It is recommended that these notifications be consumed as events rather than " +"samples to better index the appropriate values and avoid massive load on the " +"Metering database. If preferred, Telemetry can consume these events as " +"samples if the services are configured to emit ``http.*`` notifications." +msgstr "" + +#: ../telemetry-data-collection.rst:208 +msgid "" +"The Telemetry module is intended to store a complex picture of the " +"infrastructure. This goal requires additional information than what is " +"provided by the events and notifications published by each service. Some " +"information is not emitted directly, like resource usage of the VM instances." +msgstr "" + +#: ../telemetry-data-collection.rst:214 +msgid "" +"Therefore Telemetry uses another method to gather this data by polling the " +"infrastructure including the APIs of the different OpenStack services and " +"other assets, like hypervisors. The latter case requires closer interaction " +"with the compute hosts. To solve this issue, Telemetry uses an agent based " +"architecture to fulfill the requirements against the data collection." +msgstr "" + +#: ../telemetry-data-collection.rst:221 +msgid "" +"There are three types of agents supporting the polling mechanism, the " +"compute agent, the central agent, and the IPMI agent. Under the hood, all " +"the types of polling agents are the same ``ceilometer-polling`` agent, " +"except that they load different polling plug-ins (pollsters) from different " +"namespaces to gather data. The following subsections give further " +"information regarding the architectural and configuration details of these " +"components." +msgstr "" + +#: ../telemetry-data-collection.rst:229 +msgid "Running ceilometer-agent-compute is exactly the same as::" +msgstr "" + +#: ../telemetry-data-collection.rst:234 +msgid "Running ceilometer-agent-central is exactly the same as::" +msgstr "" + +#: ../telemetry-data-collection.rst:239 +msgid "Running ceilometer-agent-ipmi is exactly the same as::" +msgstr "" + +#: ../telemetry-data-collection.rst:244 +msgid "" +"In addition to loading all the polling plug-ins registered in the specified " +"namespaces, the ceilometer-polling agent can also specify the polling plug-" +"ins to be loaded by using the ``pollster-list`` option::" +msgstr "" + +#: ../telemetry-data-collection.rst:253 +msgid "HA deployment is NOT supported if the ``pollster-list`` option is used." +msgstr "" + +#: ../telemetry-data-collection.rst:258 +msgid "The ceilometer-polling service is available since Kilo release." +msgstr "" + +#: ../telemetry-data-collection.rst:261 +msgid "Central agent" +msgstr "" + +#: ../telemetry-data-collection.rst:262 +msgid "" +"This agent is responsible for polling public REST APIs to retrieve " +"additional information on OpenStack resources not already surfaced via " +"notifications, and also for polling hardware resources over SNMP." +msgstr "" + +#: ../telemetry-data-collection.rst:266 +msgid "The following services can be polled with this agent:" +msgstr "" + +# #-#-#-#-# telemetry-data-collection.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +# #-#-#-#-# telemetry-measurements.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +#: ../telemetry-data-collection.rst:270 ../telemetry-measurements.rst:748 +msgid "OpenStack Object Storage" +msgstr "" + +#: ../telemetry-data-collection.rst:274 +msgid "Hardware resources via SNMP" +msgstr "" + +#: ../telemetry-data-collection.rst:276 +msgid "" +"Energy consumption meters via `Kwapi `__ " +"framework" +msgstr "" + +#: ../telemetry-data-collection.rst:279 +msgid "" +"To install and configure this service use the `Install the Telemetry module " +"`__ section in the OpenStack Installation Guide." +msgstr "" + +#: ../telemetry-data-collection.rst:283 +msgid "" +"The central agent does not need direct database connection. The samples " +"collected by this agent are sent via AMQP to the notification agent to be " +"processed." +msgstr "" + +#: ../telemetry-data-collection.rst:289 +msgid "" +"Prior to the Liberty release, data from the polling agents was processed " +"locally and published accordingly rather than by the notification agent." +msgstr "" + +#: ../telemetry-data-collection.rst:293 +msgid "Compute agent" +msgstr "" + +#: ../telemetry-data-collection.rst:294 +msgid "" +"This agent is responsible for collecting resource usage data of VM instances " +"on individual compute nodes within an OpenStack deployment. This mechanism " +"requires a closer interaction with the hypervisor, therefore a separate " +"agent type fulfills the collection of the related meters, which is placed on " +"the host machines to locally retrieve this information." +msgstr "" + +#: ../telemetry-data-collection.rst:301 +msgid "" +"A compute agent instance has to be installed on each and every compute node, " +"installation instructions can be found in the `Install the Compute agent for " +"Telemetry `__ section in the OpenStack " +"Installation Guide." +msgstr "" + +#: ../telemetry-data-collection.rst:307 +msgid "" +"Just like the central agent, this component also does not need a direct " +"database connection. The samples are sent via AMQP to the notification agent." +msgstr "" + +#: ../telemetry-data-collection.rst:310 +msgid "" +"The list of supported hypervisors can be found in :ref:`telemetry-supported-" +"hypervisors`. The compute agent uses the API of the hypervisor installed on " +"the compute hosts. Therefore the supported meters may be different in case " +"of each virtualization back end, as each inspection tool provides a " +"different set of meters." +msgstr "" + +#: ../telemetry-data-collection.rst:316 +msgid "" +"The list of collected meters can be found in :ref:`telemetry-compute-" +"meters`. The support column provides the information that which meter is " +"available for each hypervisor supported by the Telemetry module." +msgstr "" + +#: ../telemetry-data-collection.rst:322 +msgid "Telemetry supports Libvirt, which hides the hypervisor under it." +msgstr "" + +#: ../telemetry-data-collection.rst:327 +msgid "IPMI agent" +msgstr "" + +#: ../telemetry-data-collection.rst:328 +msgid "" +"This agent is responsible for collecting IPMI sensor data and Intel Node " +"Manager data on individual compute nodes within an OpenStack deployment. " +"This agent requires an IPMI capable node with the ipmitool utility " +"installed, which is commonly used for IPMI control on various Linux " +"distributions." +msgstr "" + +#: ../telemetry-data-collection.rst:333 +msgid "" +"An IPMI agent instance could be installed on each and every compute node " +"with IPMI support, except when the node is managed by the Bare metal service " +"and the ``conductor.send_sensor_data`` option is set to ``true`` in the Bare " +"metal service. It is no harm to install this agent on a compute node without " +"IPMI or Intel Node Manager support, as the agent checks for the hardware and " +"if none is available, returns empty data. It is suggested that you install " +"the IPMI agent only on an IPMI capable node for performance reasons." +msgstr "" + +#: ../telemetry-data-collection.rst:342 +msgid "" +"Just like the central agent, this component also does not need direct " +"database access. The samples are sent via AMQP to the notification agent." +msgstr "" + +#: ../telemetry-data-collection.rst:345 +msgid "" +"The list of collected meters can be found in :ref:`telemetry-bare-metal-" +"service`." +msgstr "" + +#: ../telemetry-data-collection.rst:350 +msgid "" +"Do not deploy both the IPMI agent and the Bare metal service on one compute " +"node. If ``conductor.send_sensor_data`` is set, this misconfiguration causes " +"duplicated IPMI sensor samples." +msgstr "" + +#: ../telemetry-data-collection.rst:358 +msgid "Support for HA deployment" +msgstr "" + +#: ../telemetry-data-collection.rst:359 +msgid "" +"Both the polling agents and notification agents can run in an HA deployment, " +"which means that multiple instances of these services can run in parallel " +"with workload partitioning among these running instances." +msgstr "" + +#: ../telemetry-data-collection.rst:363 +msgid "" +"The `Tooz `__ library provides the " +"coordination within the groups of service instances. It provides an API " +"above several back ends that can be used for building distributed " +"applications." +msgstr "" + #: ../telemetry-data-collection.rst:368 msgid "" +"Tooz supports `various drivers `__ including the following back end solutions:" +msgstr "" + +#: ../telemetry-data-collection.rst:372 +msgid "" +"`Zookeeper `__. Recommended solution by the " +"Tooz project." +msgstr "" + +#: ../telemetry-data-collection.rst:375 +msgid "`Redis `__. Recommended solution by the Tooz project." +msgstr "" + +#: ../telemetry-data-collection.rst:378 +msgid "`Memcached `__. Recommended for testing." +msgstr "" + +#: ../telemetry-data-collection.rst:380 +msgid "" +"You must configure a supported Tooz driver for the HA deployment of the " +"Telemetry services." +msgstr "" + +#: ../telemetry-data-collection.rst:383 +msgid "" +"For information about the required configuration options that have to be set " +"in the :file:`ceilometer.conf` configuration file for both the central and " +"compute agents, see the `Coordination section `__ in " +"the OpenStack Configuration Reference." +msgstr "" + +#: ../telemetry-data-collection.rst:390 +msgid "Notification agent HA deployment" +msgstr "" + +#: ../telemetry-data-collection.rst:391 +msgid "" +"In the Kilo release, workload partitioning support was added to the " +"notification agent. This is particularly useful as the pipeline processing " +"is handled exclusively by the notification agent now which may result in a " +"larger amount of load." +msgstr "" + +#: ../telemetry-data-collection.rst:396 +msgid "" +"To enable workload partitioning by notification agent, the ``backend_url`` " +"option must be set in the :file:`ceilometer.conf` configuration file. " +"Additionally, ``workload_partitioning`` should be enabled in the " +"`Notification section `__ in the OpenStack " +"Configuration Reference." +msgstr "" + +#: ../telemetry-data-collection.rst:403 +msgid "" +"In Liberty, the notification agent creates multiple queues to divide the " +"workload across all active agents. The number of queues can be controled by " +"the ``pipeline_processing_queues`` option in the :file:`ceilometer.conf` " +"configuration file. A larger value will result in better distribution of " +"tasks but will also require more memory and longer startup time. It is " +"recommended to have a value approximately three times the number of active " +"notification agents. At a minimum, the value should be equal to the number " +"of active agents." +msgstr "" + +#: ../telemetry-data-collection.rst:413 +msgid "Polling agent HA deployment" +msgstr "" + +#: ../telemetry-data-collection.rst:417 +msgid "" +"Without the ``backend_url`` option being set only one instance of both the " +"central and compute agent service is able to run and function correctly." +msgstr "" + +#: ../telemetry-data-collection.rst:421 +msgid "" +"The availability check of the instances is provided by heartbeat messages. " +"When the connection with an instance is lost, the workload will be " +"reassigned within the remained instances in the next polling cycle." +msgstr "" + +#: ../telemetry-data-collection.rst:428 +msgid "" +"``Memcached`` uses a ``timeout`` value, which should always be set to a " +"value that is higher than the ``heartbeat`` value set for Telemetry." +msgstr "" + +#: ../telemetry-data-collection.rst:432 +msgid "" "For backward compatibility and supporting existing deployments, the central " "agent configuration also supports using different configuration files for " "groups of service instances of this type that are running in parallel. For " @@ -7087,79 +19770,7 @@ msgid "" "telemetry.html>`__ in the OpenStack Configuration Reference." msgstr "" -#: ../keystone_caching_layer.rst:64 -msgid "" -"For cache consistency, all token IDs are transformed into the short token " -"hash at the provider and token driver level. Some methods have access to the " -"full ID (PKI Tokens), and some methods do not. Cache invalidation is " -"inconsistent without token ID normalization." -msgstr "" - -#: ../networking_config-plugins.rst:5 -msgid "" -"For configurations options, see `Networking configuration options `__ in Configuration Reference. These sections explain how to " -"configure specific plug-ins." -msgstr "" - -#: ../telemetry-alarms.rst:35 -msgid "" -"For conventional threshold-oriented alarms, state transitions are governed " -"by:" -msgstr "" - -#: ../networking_config-plugins.rst:34 -msgid "" -"For database configuration, see `Install Networking Services `__ in the Installation Guide in the `OpenStack Documentation " -"index `__. (The link defaults to the Ubuntu " -"version.)" -msgstr "" - -#: ../networking_config-plugins.rst:179 ../networking_config-plugins.rst:243 -msgid "" -"For database configuration, see `Install Networking Services `__ in the Installation Guide." -msgstr "" - -#: ../networking_config-plugins.rst:82 -msgid "" -"For database configuration, see `Install Networking Services `__ in any of the Installation Guides in the `OpenStack " -"Documentation index `__. (The link defaults to " -"the Ubuntu version.)" -msgstr "" - -#: ../telemetry-system-architecture.rst:130 -msgid "" -"For details about hypervisor support in libvirt please check the `Libvirt " -"API support matrix `__." -msgstr "" - -#: ../networking_config-agents.rst:116 -msgid "For dhcp-agent to operate in IPv6 mode use at least dnsmasq v2.63." -msgstr "" - -#: ../keystone_integrate_identity_backend_ldap.rst:107 -msgid "" -"For each domain, create a domain-specific configuration file in the :file:`/" -"etc/keystone/domains` directory. Use the file naming convention :file:" -"`keystone.DOMAIN_NAME.conf`, where DOMAIN\\_NAME is the domain name assigned " -"in the previous step." -msgstr "" - -#: ../compute-images-instances.rst:242 -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 "" - -#: ../telemetry-data-collection.rst:378 +#: ../telemetry-data-collection.rst:442 msgid "" "For each sub-group of the central agent pool with the same " "``partitioning_group_prefix`` a disjoint subset of meters must be polled, " @@ -7169,509 +19780,70 @@ msgid "" "processing`." msgstr "" -#: ../compute-networking-nova.rst:257 +#: ../telemetry-data-collection.rst:449 msgid "" -"For every node running ``nova-network``, install ``radvd`` and configure " -"IPv6 networking:" +"To enable the compute agent to run multiple instances simultaneously with " +"workload partitioning, the ``workload_partitioning`` option has to be set to " +"``True`` under the `Compute section `__ in the :file:" +"`ceilometer.conf` configuration file." msgstr "" -#: ../compute-networking-nova.rst:251 -msgid "For every node running a ``nova-*`` service, install python-netaddr:" +#: ../telemetry-data-collection.rst:457 +msgid "Send samples to Telemetry" msgstr "" -#: ../blockstorage_image_volume_cache.rst:66 +#: ../telemetry-data-collection.rst:458 msgid "" -"For example, a configuration which would limit the max size to 200 GB and 50 " -"cache entries will be configured as::" +"While most parts of the data collection in the Telemetry module are " +"automated, Telemetry provides the possibility to submit samples via the REST " +"API to allow users to send custom samples into this module." msgstr "" -#: ../objectstorage_ringbuilder.rst:74 +#: ../telemetry-data-collection.rst:462 msgid "" -"For example, consider a 3-node cluster of machines with equal-size disks; " -"node A has 12 disks, node B has 12 disks, and node C has 11 disks. The ring " -"has an overload factor of 0.1 (10%)." +"This option makes it possible to send any kind of samples without the need " +"of writing extra code lines or making configuration changes." msgstr "" -#: ../compute_arch.rst:154 +#: ../telemetry-data-collection.rst:465 msgid "" -"For example, the ``cloud-init`` package included into an Ubuntu's stock " -"cloud image, by default, formats this space as an Ext4 file system and " -"mounts it on :file:`/mnt`. This is a cloud-init feature, and is not an " -"OpenStack mechanism. OpenStack only provisions the raw storage." +"The samples that can be sent to Telemetry are not limited to the actual " +"existing meters. There is a possibility to provide data for any new, " +"customer defined counter by filling out all the required fields of the POST " +"request." msgstr "" -#: ../identity_concepts.rst:183 +#: ../telemetry-data-collection.rst:470 msgid "" -"For example, the following line in the :file:`/etc/nova/policy.json` file " -"does not restrict which users can create volumes:" +"If the sample corresponds to an existing meter, then the fields like ``meter-" +"type`` and meter name should be matched accordingly." msgstr "" -#: ../telemetry-data-collection.rst:911 -msgid "For example, the meter definition for existence meters is as follows::" -msgstr "" - -#: ../telemetry-best-practices.rst:68 +#: ../telemetry-data-collection.rst:473 msgid "" -"For example, this open-ended query might return an unpredictable amount of " -"data:" +"The required fields for sending a sample using the command line client are:" msgstr "" -#: ../compute-manage-volumes.rst:46 -msgid "For example, to list IDs and names of Compute volumes, run:" +#: ../telemetry-data-collection.rst:476 +msgid "ID of the corresponding resource. (``--resource-id``)" msgstr "" -#: ../networking_config-agents.rst:203 -msgid "" -"For example, with Open vSwitch and NIC eth1 connected to the external " -"network, run:" +#: ../telemetry-data-collection.rst:478 +msgid "Name of meter. (``--meter-name``)" msgstr "" -#: ../keystone_integrate_identity_backend_ldap.rst:205 -msgid "" -"For example, you can mask Active Directory account status attributes in the :" -"file:`keystone.conf` file:" +#: ../telemetry-data-collection.rst:480 +msgid "Type of meter. (``--meter-type``)" msgstr "" -# #-#-#-#-# networking_adv-features.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -# #-#-#-#-# networking_config-agents.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -# #-#-#-#-# networking_config-identity.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -# #-#-#-#-# networking_use.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -#: ../networking_adv-features.rst:809 ../networking_adv-features.rst:833 -#: ../networking_config-agents.rst:94 ../networking_config-identity.rst:53 -#: ../networking_config-identity.rst:75 ../networking_use.rst:101 -msgid "For example:" -msgstr "" - -# #-#-#-#-# keystone_certificates_for_pki.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -# #-#-#-#-# objectstorage_ringbuilder.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -#: ../keystone_certificates_for_pki.rst:158 -#: ../objectstorage_ringbuilder.rst:119 -msgid "For example::" -msgstr "" - -#: ../blockstorage_backup_disks.rst:191 -msgid "" -"For files larger than around 4 to 6 GB, and depending on your CPU, the " -"process might take a long time." -msgstr "" - -#: ../compute-networking-nova.rst:160 -msgid "" -"For flat and flat DHCP modes, use the :command:`nova network-create` command " -"to create a network:" -msgstr "" - -#: ../telemetry-data-retrieval.rst:459 -msgid "" -"For further details about the python-ceilometerclient package, see the " -"`Python bindings to the OpenStack Ceilometer API `__ reference." -msgstr "" - -#: ../compute-admin-password-injection.rst:35 -msgid "" -"For hypervisors that use the libvirt back end (such as KVM, QEMU, and LXC), " -"admin password injection is disabled by default. To enable it, set this " -"option in :file:`/etc/nova/nova.conf`:" -msgstr "" - -# #-#-#-#-# compute_arch.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -# #-#-#-#-# compute-images-instances.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -#: ../compute_arch.rst:271 ../compute-images-instances.rst:377 -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 " -"field is blank." -msgstr "" - -#: ../blockstorage_volume_backups_export_import.rst:17 -msgid "" -"For information about how to back up and restore a volume, see the section " -"called :ref:`volume_backups`." -msgstr "" - -#: ../networking_config-identity.rst:118 -msgid "" -"For information about how to create service entries and users, see the " -"OpenStack Installation Guide for your distribution (`docs.openstack.org " -"`__)." -msgstr "" - -#: ../identity_concepts.rst:328 -msgid "" -"For information about how to create services and endpoints, see the " -"`OpenStack Admin User Guide `__." -msgstr "" - -#: ../telemetry-data-collection.rst:345 -msgid "" -"For information about the required configuration options that have to be set " -"in the :file:`ceilometer.conf` configuration file for both the central and " -"compute agents, see the `Coordination section `__ in " -"the OpenStack Configuration Reference." -msgstr "" - -#: ../blockstorage_glusterfs_backend.rst:37 -msgid "" -"For information on how to install and configure GlusterFS, refer to the " -"`GlusterDocumentation`_ page." -msgstr "" - -#: ../compute-networking-nova.rst:486 -msgid "" -"For instances to reach the metadata service, the ``nova-network`` service " -"must configure iptables to NAT port ``80`` of the ``169.254.169.254`` " -"address to the IP address specified in ``metadata_host`` (this defaults to ``" -"$my_ip``, which is the IP address of the ``nova-network`` service) and port " -"specified in ``metadata_port`` (which defaults to ``8775``) in :file:`/etc/" -"nova/nova.conf`." -msgstr "" - -#: ../networking_config-agents.rst:241 -msgid "" -"For iproute version 3.12.0 and above, networking namespaces are configured " -"to be deleted by default. This behavior can be changed for both DHCP and L3 " -"agents. The configuration files are :file:`/etc/neutron/dhcp_agent.ini` and :" -"file:`/etc/neutron/l3_agent.ini` respectively." -msgstr "" - -#: ../telemetry-data-collection.rst:574 -msgid "" -"For meters, which have variants identified by a complex name field, use the " -"wildcard symbol to select all, e.g. for \"instance:m1.tiny\", use \"instance:" -"\\*\"." -msgstr "" - -#: ../compute-manage-logs.rst:36 -msgid "" -"For more about the logging configuration syntax, including the ``handlers`` " -"and ``quaname`` variables, see the `Python documentation `__ on " -"logging configuration files." -msgstr "" - -#: ../telemetry-troubleshooting-guide.rst:103 -msgid "" -"For more details check the bug report `Bug 1351841 `__." -msgstr "" - -#: ../orchestration-introduction.rst:30 -msgid "" -"For more details on how to use Orchestration module through a command line, " -"see `OpenStack Command-Line Interface Reference`_." -msgstr "" - -#: ../networking_introduction.rst:249 -msgid "" -"For more details, see `Networking command-line client `__ in the OpenStack " -"Command-Line Interface Reference." -msgstr "" - -#: ../telemetry-data-retrieval.rst:330 -msgid "" -"For more information about complex queries see :ref:`Complex query `." -msgstr "" - -#: ../compute-networking-nova.rst:196 -msgid "" -"For more information about creating a dnsmasq configuration file, see the " -"`OpenStack Configuration Reference `__, and `the dnsmasq documentation `__." -msgstr "" - -#: ../compute-images-instances.rst:26 -msgid "" -"For more information about creating and troubleshooting images, see the " -"`OpenStack Virtual Machine Image Guide `__." -msgstr "" - -#: ../compute-images-instances.rst:35 -msgid "" -"For more information about flavors, see :ref:`compute-flavors` or `Flavors " -"`__ in the " -"OpenStack Operations Guide." -msgstr "" - -#: ../compute-networking-nova.rst:721 -msgid "" -"For more information about how administrators can associate floating IPs " -"with instances, see `Manage IP addresses `__ in the OpenStack Admin " -"User Guide." -msgstr "" - -#: ../blockstorage_volume_backups.rst:99 -msgid "" -"For more information about how to export and import volume backup metadata, " -"see the section called :ref:`volume_backups_export_import`." -msgstr "" - -#: ../compute_arch.rst:74 -msgid "" -"For more information about hypervisors, see the `Hypervisors `__ section in the OpenStack Configuration Reference." -msgstr "" - -#: ../compute-images-instances.rst:30 -msgid "" -"For more information about image configuration options, see the `Image " -"services `__ section of the OpenStack " -"Configuration Reference." -msgstr "" - -#: ../compute-images-instances.rst:421 -msgid "" -"For more information about python-novaclient and other command-line tools, " -"see the `OpenStack End User Guide `__." -msgstr "" - -#: ../keystone_caching_layer.rst:102 -msgid "" -"For more information about the different back ends (and configuration " -"options), see:" -msgstr "" - -#: ../objectstorage_components.rst:52 -msgid "" -"For more information concerning proxy server configuration, please see the " -"`Configuration Reference `__." -msgstr "" - -#: ../telemetry-best-practices.rst:57 -msgid "" -"For more information on RPC overhead, see `RPC overhead info `__." -msgstr "" - -#: ../telemetry-best-practices.rst:122 -msgid "" -"For more information on how much memory you need, see `MongoDB FAQ `__." -msgstr "" - -#: ../telemetry-best-practices.rst:95 -msgid "" -"For more information on how to configure ``mod_wsgi``, see the `Telemetry " -"Install Documentation `__." -msgstr "" - -#: ../telemetry-best-practices.rst:107 -msgid "" -"For more information on how to set the TTL, see :ref:`telemetry-storing-" -"samples`." -msgstr "" - -#: ../telemetry-best-practices.rst:130 -msgid "" -"For more information on replica sets, see the `MongoDB replica sets docs " -"`__." -msgstr "" - -#: ../telemetry-best-practices.rst:137 -msgid "" -"For more information on sharding, see the `MongoDB sharding docs `__." -msgstr "" - -#: ../telemetry-best-practices.rst:49 -msgid "For more information see, :ref:`ha-deploy-services`." -msgstr "" - -#: ../telemetry-best-practices.rst:32 -msgid "For more information, see the :ref:`telemetry-pipeline-configuration`." -msgstr "" - -#: ../compute-configuring-migrations.rst:154 -msgid "" -"For more information, see: `SettingUpNFSHowTo `_ or `CentOS/Red Hat: Setup NFS v4.0 File " -"Server `_" -msgstr "" - -#: ../objectstorage_arch.rst:47 -msgid "" -"For most publicly facing deployments as well as private deployments " -"available across a wide-reaching corporate network, you use SSL to encrypt " -"traffic to the client. SSL adds significant processing load to establish " -"sessions between clients, which is why you have to provision more capacity " -"in the access layer. SSL may not be required for private deployments on " -"trusted networks." -msgstr "" - -#: ../compute-remote-console-access.rst:203 -msgid "" -"For multi-host XenServer domU deployments, set to a ``dom0 management IP`` " -"on the same network as the proxies." -msgstr "" - -#: ../compute-remote-console-access.rst:206 -msgid "" -"For multi-host libvirt deployments, set to a host management IP on the same " -"network as the proxies." -msgstr "" - -#: ../identity_auth_token_middleware.rst:12 -msgid "" -"For services that have a separate paste-deploy :file:`.ini` file, you can " -"configure the authentication middleware in the ``[keystone_authtoken]`` " -"section of the main configuration file, such as :file:`nova.conf`. In " -"Compute, for example, you can remove the middleware parameters from :file:" -"`api-paste.ini`, as follows:" -msgstr "" - -#: ../objectstorage_tenant_specific_image_storage.rst:5 -msgid "" -"For some deployers, it is not ideal to store all images in one place to " -"enable all tenants and users to access them. You can configure the Image " -"service to store image data in tenant-specific image locations. Then, only " -"the following tenants can use the Image service to access the created image:" -msgstr "" - -#: ../telemetry-measurements.rst:68 -msgid "" -"For specifying the new header, you need to set ``metadata_headers`` option " -"under the ``[filter:ceilometer]`` section in ``proxy-server.conf`` under the " -"``swift`` folder. You can use this additional data for instance to " -"distinguish external and internal users." -msgstr "" - -#: ../compute_arch.rst:91 -msgid "For tenants, you can use quota controls to limit the:" -msgstr "" - -#: ../keystone_integrate_with_ldap.rst:30 -msgid "" -"For the OpenStack Identity service to access LDAP servers, you must enable " -"the ``authlogin_nsswitch_use_ldap`` boolean value for SELinux on the " -"Openstack Identity server. To enable and make the option persistent across " -"reboots, set the following boolean value as the root user:" -msgstr "" - -#: ../blockstorage_volume_backups.rst:114 -msgid "" -"For the ``backup_share`` option, replace *HOST* with the DNS resolvable host " -"name or the IP address of the storage server for the NFS share, and " -"*EXPORT_PATH* with the path to that share. If your environment requires that " -"non-default mount options be specified for the share, set these as follows:" -msgstr "" - -#: ../compute-flavors.rst:274 -msgid "" -"For the libvirt driver, you can define the topology of the processors in the " -"virtual machine using properties. The properties with ``max`` limit the " -"number that can be selected by the user with image properties." -msgstr "" - -#: ../compute-flavors.rst:224 -msgid "" -"For the libvirt driver, you can enable and set the behavior of a virtual " -"hardware watchdog device for each flavor. Watchdog devices keep an eye on " -"the guest server, and carry out the configured action, if the server hangs. " -"The watchdog uses the i6300esb device (emulating a PCI Intel 6300ESB). If " -"``hw:watchdog_action`` is not specified, the watchdog is disabled." -msgstr "" - -#: ../telemetry-troubleshooting-guide.rst:64 -msgid "" -"For the list of meters that are originated from notifications, see the " -"`Telemetry Measurements Reference `__." -msgstr "" - -#: ../telemetry-data-collection.rst:1052 -msgid "" -"For the list of options that you need to set, see the `dispatcher_gnocchi " -"section `__ in the OpenStack Configuration " -"Reference." -msgstr "" - -#: ../compute-configuring-migrations.rst:343 -msgid "" -"For the supported NFS versions, see the `NFS VHD `_ section of the " -"XenServer Administrator's Guide." -msgstr "" - -#: ../blockstorage_backup_disks.rst:28 -msgid "" -"For this example, assume that a 100 GB volume named ``volume-00000001`` was " -"created for an instance while only 4 GB are used. This example uses these " -"commands to back up only those 4 GB:" -msgstr "" - -#: ../blockstorage-manage-volumes.rst:39 -msgid "" -"For this particular walk through, one cloud controller runs ``nova-api``, " -"``nova-scheduler``, ``nova-objectstore``, ``nova-network`` and ``cinder-*`` " -"services. Two additional compute nodes run ``nova-compute``. The walk " -"through uses a custom partitioning scheme that carves out 60 GB of space and " -"labels it as LVM. The network uses the ``FlatManager`` and " -"``NetworkManager`` settings for OpenStack Compute." -msgstr "" - -#: ../compute-images-instances.rst:170 -msgid "" -"For unprotected image properties, the cloud administrator can manage core " -"properties and the image owner can manage additional properties." -msgstr "" - -#: ../telemetry-measurements.rst:1007 -msgid "Frame alignment errors receive\\ d on port" -msgstr "" - -#: ../compute_arch.rst:264 -msgid "Free form, human-readable name for image" -msgstr "" - -#: ../compute-images-instances.rst:370 -msgid "Free form, human-readable name for the image." -msgstr "" - -#: ../compute-remote-console-access.rst:255 -msgid "Frequently asked questions about VNC access to virtual machines" -msgstr "" - -#: ../database.rst:257 -msgid "Full path to the :file:`validation-rules.json` file" -msgstr "" - -#: ../objectstorage_features.rst:62 -msgid "" -"Fully integrated with Compute for attaching block volumes and reporting on " -"usage." -msgstr "" - -#: ../telemetry-data-retrieval.rst:28 -msgid "" -"Further information about the available API endpoints can be found in the " -"`Telemetry API Reference `__." -msgstr "" - -#: ../telemetry-measurements.rst:158 ../telemetry-measurements.rst:161 -#: ../telemetry-measurements.rst:704 ../telemetry-measurements.rst:712 -msgid "GB" +#: ../telemetry-data-collection.rst:482 +msgid "Predefined meter types:" msgstr "" # #-#-#-#-# telemetry-data-collection.pot (Cloud Administrator Guide 0.9) #-#-#-#-# # #-#-#-#-# telemetry-measurements.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -#: ../telemetry-data-collection.rst:449 ../telemetry-measurements.rst:37 +#: ../telemetry-data-collection.rst:484 ../telemetry-measurements.rst:37 #: ../telemetry-measurements.rst:101 ../telemetry-measurements.rst:105 #: ../telemetry-measurements.rst:109 ../telemetry-measurements.rst:113 #: ../telemetry-measurements.rst:122 ../telemetry-measurements.rst:126 @@ -7736,419 +19908,1357 @@ msgstr "" msgid "Gauge" msgstr "" -#: ../blockstorage-driver-filter-weighing.rst:222 -msgid "General metadata" +# #-#-#-#-# telemetry-data-collection.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +# #-#-#-#-# telemetry-measurements.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +#: ../telemetry-data-collection.rst:486 ../telemetry-data-collection.rst:656 +#: ../telemetry-measurements.rst:35 ../telemetry-measurements.rst:355 +#: ../telemetry-measurements.rst:676 ../telemetry-measurements.rst:679 +#: ../telemetry-measurements.rst:682 ../telemetry-measurements.rst:685 +#: ../telemetry-measurements.rst:688 ../telemetry-measurements.rst:717 +#: ../telemetry-measurements.rst:720 ../telemetry-measurements.rst:723 +#: ../telemetry-measurements.rst:727 ../telemetry-measurements.rst:730 +#: ../telemetry-measurements.rst:734 ../telemetry-measurements.rst:738 +#: ../telemetry-measurements.rst:741 ../telemetry-measurements.rst:765 +#: ../telemetry-measurements.rst:768 ../telemetry-measurements.rst:771 +#: ../telemetry-measurements.rst:843 ../telemetry-measurements.rst:846 +#: ../telemetry-measurements.rst:849 ../telemetry-measurements.rst:852 +#: ../telemetry-measurements.rst:855 ../telemetry-measurements.rst:858 +#: ../telemetry-measurements.rst:861 ../telemetry-measurements.rst:864 +#: ../telemetry-measurements.rst:867 ../telemetry-measurements.rst:870 +#: ../telemetry-measurements.rst:873 ../telemetry-measurements.rst:876 +#: ../telemetry-measurements.rst:879 ../telemetry-measurements.rst:882 +#: ../telemetry-measurements.rst:885 ../telemetry-measurements.rst:888 +#: ../telemetry-measurements.rst:891 ../telemetry-measurements.rst:896 +#: ../telemetry-measurements.rst:900 ../telemetry-measurements.rst:917 +#: ../telemetry-measurements.rst:921 ../telemetry-measurements.rst:927 +#: ../telemetry-measurements.rst:931 ../telemetry-measurements.rst:937 +#: ../telemetry-measurements.rst:940 ../telemetry-measurements.rst:946 +#: ../telemetry-measurements.rst:950 ../telemetry-measurements.rst:957 +#: ../telemetry-measurements.rst:960 ../telemetry-measurements.rst:963 +#: ../telemetry-measurements.rst:1097 ../telemetry-measurements.rst:1101 +#: ../telemetry-measurements.rst:1105 ../telemetry-measurements.rst:1109 +#: ../telemetry-measurements.rst:1113 ../telemetry-measurements.rst:1117 +#: ../telemetry-measurements.rst:1121 ../telemetry-measurements.rst:1126 +#: ../telemetry-measurements.rst:1152 ../telemetry-measurements.rst:1156 +#: ../telemetry-measurements.rst:1160 ../telemetry-measurements.rst:1165 +#: ../telemetry-measurements.rst:1174 ../telemetry-measurements.rst:1179 +#: ../telemetry-measurements.rst:1188 ../telemetry-measurements.rst:1192 +#: ../telemetry-measurements.rst:1216 ../telemetry-measurements.rst:1220 +#: ../telemetry-measurements.rst:1224 ../telemetry-measurements.rst:1229 +#: ../telemetry-measurements.rst:1238 ../telemetry-measurements.rst:1243 +#: ../telemetry-measurements.rst:1257 ../telemetry-measurements.rst:1260 +#: ../telemetry-measurements.rst:1263 ../telemetry-measurements.rst:1266 +#: ../telemetry-measurements.rst:1269 ../telemetry-measurements.rst:1283 +#: ../telemetry-measurements.rst:1288 ../telemetry-measurements.rst:1292 +msgid "Delta" msgstr "" -#: ../keystone_certificates_for_pki.rst:220 -msgid "Generate a new certificate request." +# #-#-#-#-# telemetry-data-collection.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +# #-#-#-#-# telemetry-measurements.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +#: ../telemetry-data-collection.rst:488 ../telemetry-measurements.rst:33 +#: ../telemetry-measurements.rst:1326 +msgid "Cumulative" msgstr "" -#: ../keystone_certificates_for_pki.rst:218 -msgid "Generate a new signing key." +#: ../telemetry-data-collection.rst:490 +msgid "Unit of meter. (``--meter-unit``)" msgstr "" -#: ../blockstorage_get_capabilities.rst:6 -msgid "Get capabilities" +#: ../telemetry-data-collection.rst:492 +msgid "Volume of sample. (``--sample-volume``)" msgstr "" -#: ../compute_arch.rst:349 -msgid "Get console output" +#: ../telemetry-data-collection.rst:494 +msgid "" +"To send samples to Telemetry using the command line client, the following " +"command should be invoked::" +msgstr "" + +#: ../telemetry-data-collection.rst:518 +msgid "Data collection and processing" +msgstr "" + +#: ../telemetry-data-collection.rst:519 +msgid "" +"The mechanism by which data is collected and processed is called a pipeline. " +"Pipelines, at the configuration level, describe a coupling between sources " +"of data and the corresponding sinks for transformation and publication of " +"data." +msgstr "" + +#: ../telemetry-data-collection.rst:524 +msgid "" +"A source is a producer of data: samples or events. In effect, it is a set of " +"pollsters or notification handlers emitting datapoints for a set of matching " +"meters and event types." +msgstr "" + +#: ../telemetry-data-collection.rst:528 +msgid "" +"Each source configuration encapsulates name matching, polling interval " +"determination, optional resource enumeration or discovery, and mapping to " +"one or more sinks for publication." +msgstr "" + +#: ../telemetry-data-collection.rst:532 +msgid "" +"Data gathered can be used for different purposes, which can impact how " +"frequently it needs to be published. Typically, a meter published for " +"billing purposes needs to be updated every 30 minutes while the same meter " +"may be needed for performance tuning every minute." +msgstr "" + +#: ../telemetry-data-collection.rst:539 +msgid "" +"Rapid polling cadences should be avoided, as it results in a huge amount of " +"data in a short time frame, which may negatively affect the performance of " +"both Telemetry and the underlying database back end. We therefore strongly " +"recommend you do not use small granularity values like 10 seconds." +msgstr "" + +#: ../telemetry-data-collection.rst:545 +msgid "" +"A sink, on the other hand, is a consumer of data, providing logic for the " +"transformation and publication of data emitted from related sources." +msgstr "" + +#: ../telemetry-data-collection.rst:548 +msgid "" +"In effect, a sink describes a chain of handlers. The chain starts with zero " +"or more transformers and ends with one or more publishers. The first " +"transformer in the chain is passed data from the corresponding source, takes " +"some action such as deriving rate of change, performing unit conversion, or " +"aggregating, before passing the modified data to the next step that is " +"described in :ref:`telemetry-publishers`." +msgstr "" + +#: ../telemetry-data-collection.rst:558 +msgid "Pipeline configuration" +msgstr "" + +#: ../telemetry-data-collection.rst:559 +msgid "" +"Pipeline configuration by default, is stored in separate configuration " +"files, called :file:`pipeline.yaml` and :file:`event_pipeline.yaml`, next to " +"the :file:`ceilometer.conf` file. The meter pipeline and event pipeline " +"configuration files can be set by the ``pipeline_cfg_file`` and " +"``event_pipeline_cfg_file`` options listed in the `Description of " +"configuration options for api table `__ section in the " +"OpenStack Configuration Reference respectively. Multiple pipelines can be " +"defined in one pipeline configuration file." +msgstr "" + +#: ../telemetry-data-collection.rst:569 +msgid "The meter pipeline definition looks like the following::" +msgstr "" + +#: ../telemetry-data-collection.rst:587 +msgid "" +"The interval parameter in the sources section should be defined in seconds. " +"It determines the polling cadence of sample injection into the pipeline, " +"where samples are produced under the direct control of an agent." +msgstr "" + +#: ../telemetry-data-collection.rst:592 +msgid "" +"There are several ways to define the list of meters for a pipeline source. " +"The list of valid meters can be found in :ref:`telemetry-measurements`. " +"There is a possibility to define all the meters, or just included or " +"excluded meters, with which a source should operate:" +msgstr "" + +#: ../telemetry-data-collection.rst:597 +msgid "" +"To include all meters, use the ``*`` wildcard symbol. It is highly advisable " +"to select only the meters that you intend on using to avoid flooding the " +"metering database with unused data." +msgstr "" + +#: ../telemetry-data-collection.rst:601 +msgid "To define the list of meters, use either of the following:" +msgstr "" + +#: ../telemetry-data-collection.rst:603 +msgid "To define the list of included meters, use the ``meter_name`` syntax." +msgstr "" + +#: ../telemetry-data-collection.rst:606 +msgid "To define the list of excluded meters, use the ``!meter_name`` syntax." +msgstr "" + +#: ../telemetry-data-collection.rst:609 +msgid "" +"For meters, which have variants identified by a complex name field, use the " +"wildcard symbol to select all, e.g. for \"instance:m1.tiny\", use \"instance:" +"\\*\"." +msgstr "" + +#: ../telemetry-data-collection.rst:615 +msgid "" +"Please be aware that we do not have any duplication check between pipelines " +"and if you add a meter to multiple pipelines then it is assumed the " +"duplication is intentional and may be stored multiple times according to the " +"specified sinks." +msgstr "" + +#: ../telemetry-data-collection.rst:620 +msgid "The above definition methods can be used in the following combinations:" +msgstr "" + +#: ../telemetry-data-collection.rst:622 +msgid "Use only the wildcard symbol." +msgstr "" + +#: ../telemetry-data-collection.rst:624 +msgid "Use the list of included meters." +msgstr "" + +#: ../telemetry-data-collection.rst:626 +msgid "Use the list of excluded meters." +msgstr "" + +#: ../telemetry-data-collection.rst:628 +msgid "Use wildcard symbol with the list of excluded meters." +msgstr "" + +#: ../telemetry-data-collection.rst:632 +msgid "" +"At least one of the above variations should be included in the meters " +"section. Included and excluded meters cannot co-exist in the same pipeline. " +"Wildcard and included meters cannot co-exist in the same pipeline definition " +"section." +msgstr "" + +#: ../telemetry-data-collection.rst:637 +msgid "" +"The optional resources section of a pipeline source allows a static list of " +"resource URLs to be configured for polling." +msgstr "" + +#: ../telemetry-data-collection.rst:640 +msgid "" +"The transformers section of a pipeline sink provides the possibility to add " +"a list of transformer definitions. The available transformers are:" +msgstr "" + +#: ../telemetry-data-collection.rst:644 +msgid "Name of transformer" +msgstr "" + +#: ../telemetry-data-collection.rst:644 +msgid "Reference name for configuration" +msgstr "" + +#: ../telemetry-data-collection.rst:646 +msgid "Accumulator" +msgstr "" + +#: ../telemetry-data-collection.rst:646 +msgid "accumulator" +msgstr "" + +#: ../telemetry-data-collection.rst:648 +msgid "Aggregator" +msgstr "" + +#: ../telemetry-data-collection.rst:648 +msgid "aggregator" +msgstr "" + +#: ../telemetry-data-collection.rst:650 +msgid "Arithmetic" +msgstr "" + +#: ../telemetry-data-collection.rst:650 +msgid "arithmetic" +msgstr "" + +#: ../telemetry-data-collection.rst:652 +msgid "Rate of change" +msgstr "" + +#: ../telemetry-data-collection.rst:652 +msgid "rate\\_of\\_change" +msgstr "" + +#: ../telemetry-data-collection.rst:654 +msgid "Unit conversion" +msgstr "" + +#: ../telemetry-data-collection.rst:654 +msgid "unit\\_conversion" +msgstr "" + +#: ../telemetry-data-collection.rst:656 +msgid "delta" +msgstr "" + +#: ../telemetry-data-collection.rst:659 +msgid "" +"The publishers section contains the list of publishers, where the samples " +"data should be sent after the possible transformations." +msgstr "" + +#: ../telemetry-data-collection.rst:662 +msgid "Similarly, the event pipeline definition looks like the following::" +msgstr "" + +#: ../telemetry-data-collection.rst:676 +msgid "The event filter uses the same filtering logic as the meter pipeline." +msgstr "" + +#: ../telemetry-data-collection.rst:681 +msgid "Transformers" +msgstr "" + +#: ../telemetry-data-collection.rst:683 +msgid "The definition of transformers can contain the following fields:" +msgstr "" + +#: ../telemetry-data-collection.rst:686 +msgid "Name of the transformer." +msgstr "" + +#: ../telemetry-data-collection.rst:689 +msgid "Parameters of the transformer." +msgstr "" + +#: ../telemetry-data-collection.rst:689 +msgid "parameters" +msgstr "" + +#: ../telemetry-data-collection.rst:691 +msgid "" +"The parameters section can contain transformer specific fields, like source " +"and target fields with different subfields in case of the rate of change, " +"which depends on the implementation of the transformer." +msgstr "" + +#: ../telemetry-data-collection.rst:695 +msgid "" +"In the case of the transformer that creates the ``cpu_util`` meter, the " +"definition looks like the following::" +msgstr "" + +#: ../telemetry-data-collection.rst:707 +msgid "" +"The rate of change the transformer generates is the ``cpu_util`` meter from " +"the sample values of the ``cpu`` counter, which represents cumulative CPU " +"time in nanoseconds. The transformer definition above defines a scale factor " +"(for nanoseconds and multiple CPUs), which is applied before the " +"transformation derives a sequence of gauge samples with unit '%', from " +"sequential values of the ``cpu`` meter." +msgstr "" + +#: ../telemetry-data-collection.rst:714 +msgid "" +"The definition for the disk I/O rate, which is also generated by the rate of " +"change transformer::" +msgstr "" + +#: ../telemetry-data-collection.rst:730 +msgid "**Unit conversion transformer**" +msgstr "" + +#: ../telemetry-data-collection.rst:732 +msgid "" +"Transformer to apply a unit conversion. It takes the volume of the meter and " +"multiplies it with the given ``scale`` expression. Also supports " +"``map_from`` and ``map_to`` like the rate of change transformer." +msgstr "" + +#: ../telemetry-data-collection.rst:736 +msgid "Sample configuration::" +msgstr "" + +#: ../telemetry-data-collection.rst:746 +msgid "With ``map_from`` and ``map_to`` ::" +msgstr "" + +#: ../telemetry-data-collection.rst:760 +msgid "**Aggregator transformer**" +msgstr "" + +#: ../telemetry-data-collection.rst:762 +msgid "" +"A transformer that sums up the incoming samples until enough samples have " +"come in or a timeout has been reached." +msgstr "" + +#: ../telemetry-data-collection.rst:765 +msgid "" +"Timeout can be specified with the ``retention_time`` option. If we want to " +"flush the aggregation after a set number of samples have been aggregated, we " +"can specify the size parameter." +msgstr "" + +#: ../telemetry-data-collection.rst:769 +msgid "" +"The volume of the created sample is the sum of the volumes of samples that " +"came into the transformer. Samples can be aggregated by the attributes " +"``project_id``, ``user_id`` and ``resource_metadata``. To aggregate by the " +"chosen attributes, specify them in the configuration and set which value of " +"the attribute to take for the new sample (first to take the first sample's " +"attribute, last to take the last sample's attribute, and drop to discard the " +"attribute)." +msgstr "" + +#: ../telemetry-data-collection.rst:777 +msgid "" +"To aggregate 60s worth of samples by ``resource_metadata`` and keep the " +"``resource_metadata`` of the latest received sample::" +msgstr "" + +#: ../telemetry-data-collection.rst:786 +msgid "" +"To aggregate each 15 samples by ``user_id`` and ``resource_metadata`` and " +"keep the ``user_id`` of the first received sample and drop the " +"``resource_metadata``::" +msgstr "" + +#: ../telemetry-data-collection.rst:797 +msgid "**Accumulator transformer**" +msgstr "" + +#: ../telemetry-data-collection.rst:799 +msgid "" +"This transformer simply caches the samples until enough samples have arrived " +"and then flushes them all down the pipeline at once::" +msgstr "" + +#: ../telemetry-data-collection.rst:807 +msgid "**Muli meter arithmetic transformer**" +msgstr "" + +#: ../telemetry-data-collection.rst:809 +msgid "" +"This transformer enables us to perform arithmetic calculations over one or " +"more meters and/or their metadata, for example::" +msgstr "" + +#: ../telemetry-data-collection.rst:814 +msgid "" +"A new sample is created with the properties described in the ``target`` " +"section of the transformer's configuration. The sample's volume is the " +"result of the provided expression. The calculation is performed on samples " +"from the same resource." +msgstr "" + +#: ../telemetry-data-collection.rst:821 +msgid "The calculation is limited to meters with the same interval." +msgstr "" + +#: ../telemetry-data-collection.rst:823 ../telemetry-data-collection.rst:856 +msgid "Example configuration::" +msgstr "" + +#: ../telemetry-data-collection.rst:834 +msgid "" +"To demonstrate the use of metadata, here is the implementation of a silly " +"meter that shows average CPU time per core::" +msgstr "" + +#: ../telemetry-data-collection.rst:848 +msgid "" +"Expression evaluation gracefully handles NaNs and exceptions. In such a case " +"it does not create a new sample but only logs a warning." +msgstr "" + +#: ../telemetry-data-collection.rst:851 +msgid "**Delta transformer**" +msgstr "" + +#: ../telemetry-data-collection.rst:853 +msgid "" +"This transformer calculates the change between two sample datapoints of a " +"resource. It can be configured to capture only the positive growth deltas." +msgstr "" + +#: ../telemetry-data-collection.rst:868 +msgid "Meter definitions" +msgstr "" + +#: ../telemetry-data-collection.rst:869 +msgid "" +"The Telemetry module collects a subset of the meters by filtering " +"notifications emitted by other OpenStack services. Starting with the Liberty " +"release, you can find the meter definitions in a separate configuration " +"file, called :file:`ceilometer/meter/data/meter.yaml`. This enables " +"operators/administrators to add new meters to Telemetry project by updating " +"the :file:`meter.yaml` file without any need for additional code changes." +msgstr "" + +#: ../telemetry-data-collection.rst:878 +msgid "" +"The :file:`meter.yaml` file should be modified with care. Unless intended do " +"not remove any existing meter definitions from the file. Also, the collected " +"meters can differ in some cases from what is referenced in the documentation." +msgstr "" + +#: ../telemetry-data-collection.rst:883 +msgid "A standard meter definition looks like the following::" +msgstr "" + +#: ../telemetry-data-collection.rst:895 +msgid "" +"The definition above shows a simple meter definition with some fields, from " +"which ``name``, ``event_type``, ``type``, ``unit``, and ``volume`` are " +"required. If there is a match on the event type, samples are generated for " +"the meter." +msgstr "" + +#: ../telemetry-data-collection.rst:900 +msgid "" +"If you take a look at the :file:`meter.yaml` file, it contains the sample " +"definitions for all the meters that Telemetry is collecting from " +"notifications. The value of each field is specified by using json path in " +"order to find the right value from the notification message. In order to be " +"able to specify the right field you need to be aware of the format of the " +"consumed notification. The values that need to be searched in the " +"notification message are set with a json path starting with ``$.`` For " +"instance, if you need the ``size`` information from the payload you can " +"define it like ``$.payload.size``." +msgstr "" + +#: ../telemetry-data-collection.rst:910 +msgid "" +"A notification message may contain multiple meters. You can use ``*`` in the " +"meter definition to capture all the meters and generate samples " +"respectively. You can use wild cards as shown in the following example::" +msgstr "" + +#: ../telemetry-data-collection.rst:925 +msgid "" +"In the above example, the ``name`` field is a json path with matching a list " +"of meter names defined in the notification message." +msgstr "" + +#: ../telemetry-data-collection.rst:928 +msgid "" +"You can even use complex operations on json paths. In the following example, " +"``volume`` and ``resource_id`` fields perform an arithmetic and string " +"concatenation::" +msgstr "" + +#: ../telemetry-data-collection.rst:942 +msgid "" +"You will find some existence meters in the :file:`meter.yaml`. These meters " +"have a ``volume`` as ``1`` and are at the bottom of the yaml file with a " +"note suggesting that these will be removed in Mitaka release." +msgstr "" + +#: ../telemetry-data-collection.rst:946 +msgid "For example, the meter definition for existence meters is as follows::" +msgstr "" + +#: ../telemetry-data-collection.rst:960 +msgid "" +"These meters are not loaded by default. To load these meters, flip the " +"`disable_non_metric_meters` option in the :file:`ceilometer.conf` file." +msgstr "" + +#: ../telemetry-data-collection.rst:965 +msgid "Block Storage audit script setup to get notifications" +msgstr "" + +#: ../telemetry-data-collection.rst:966 +msgid "" +"If you want to collect OpenStack Block Storage notification on demand, you " +"can use ``cinder-volume-usage-audit`` from OpenStack Block Storage. This " +"script becomes available when you install OpenStack Block Storage, so you " +"can use it without any specific settings and you don't need to authenticate " +"to access the data. To use it, you must run this command in the following " +"format::" +msgstr "" + +#: ../telemetry-data-collection.rst:976 +msgid "" +"This script outputs what volumes or snapshots were created, deleted, or " +"exists in a given period of time and some information about these volumes or " +"snapshots. Information about the existence and size of volumes and snapshots " +"is store in the Telemetry module. This data is also stored as an event which " +"is the recommended usage as it provides better indexing of data." +msgstr "" + +#: ../telemetry-data-collection.rst:983 +msgid "" +"Using this script via cron you can get notifications periodically, for " +"example, every 5 minutes::" +msgstr "" + +#: ../telemetry-data-collection.rst:991 +msgid "Storing samples" +msgstr "" + +#: ../telemetry-data-collection.rst:992 +msgid "" +"The Telemetry module has a separate service that is responsible for " +"persisting the data that comes from the pollsters or is received as " +"notifications. The data can be stored in a file or a database back end, for " +"which the list of supported databases can be found in :ref:`telemetry-" +"supported-databases`. The data can also be sent to an external data store by " +"using an HTTP dispatcher." +msgstr "" + +#: ../telemetry-data-collection.rst:999 +msgid "" +"The ``ceilometer-collector`` service receives the data as messages from the " +"message bus of the configured AMQP service. It sends these datapoints " +"without any modification to the configured target. The service has to run on " +"a host machine from which it has access to the configured dispatcher." +msgstr "" + +#: ../telemetry-data-collection.rst:1007 +msgid "Multiple dispatchers can be configured for Telemetry at one time." +msgstr "" + +#: ../telemetry-data-collection.rst:1009 +msgid "" +"Multiple ``ceilometer-collector`` processes can be run at a time. It is also " +"supported to start multiple worker threads per collector process. The " +"``collector_workers`` configuration option has to be modified in the " +"`Collector section `__ of the :file:`ceilometer.conf` " +"configuration file." +msgstr "" + +#: ../telemetry-data-collection.rst:1018 +msgid "" +"Prior to the Juno release, it is not recommended to use multiple workers per " +"collector process when using PostgreSQL as the database back end." +msgstr "" + +#: ../telemetry-data-collection.rst:1023 +msgid "Database dispatcher" +msgstr "" + +#: ../telemetry-data-collection.rst:1024 +msgid "" +"When the database dispatcher is configured as data store, you have the " +"option to set a ``time_to_live`` option (ttl) for samples. By default the " +"time to live value for samples is set to -1, which means that they are kept " +"in the database forever." +msgstr "" + +#: ../telemetry-data-collection.rst:1029 +msgid "" +"The time to live value is specified in seconds. Each sample has a time " +"stamp, and the ``ttl`` value indicates that a sample will be deleted from " +"the database when the number of seconds has elapsed since that sample " +"reading was stamped. For example, if the time to live is set to 600, all " +"samples older than 600 seconds will be purged from the database." +msgstr "" + +#: ../telemetry-data-collection.rst:1036 +msgid "" +"Certain databases support native TTL expiration. In cases where this is not " +"possible, a command-line script, which you can use for this purpose is " +"ceilometer-expirer. You can run it in a cron job, which helps to keep your " +"database in a consistent state." +msgstr "" + +#: ../telemetry-data-collection.rst:1041 +msgid "The level of support differs in case of the configured back end:" +msgstr "" + +#: ../telemetry-data-collection.rst:1044 +msgid "TTL value support" msgstr "" #: ../telemetry-data-collection.rst:1046 -msgid "Gnocchi dispatcher" +msgid "MongoDB" msgstr "" -#: ../blockstorage_glusterfs_removal.rst:8 -msgid "Gracefully remove a GlusterFS volume from usage" -msgstr "" - -#: ../compute-images-instances.rst:151 -msgid "GridFS" -msgstr "" - -# #-#-#-#-# identity_concepts.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -# #-#-#-#-# networking_adv-features.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -#: ../identity_concepts.rst:39 ../networking_adv-features.rst:606 -msgid "Group" -msgstr "" - -#: ../identity_concepts.rst:370 +#: ../telemetry-data-collection.rst:1046 msgid "" -"Group A is granted Role A on Tenant A. If User A is a member of Group A, " -"when User A gets a token scoped to Tenant A, the token also includes Role A." +"MongoDB has native TTL support for deleting samples that are older than the " +"configured ttl value." msgstr "" -#: ../identity_concepts.rst:374 +#: ../telemetry-data-collection.rst:1050 +msgid "SQL-based back ends" +msgstr "" + +#: ../telemetry-data-collection.rst:1050 msgid "" -"Group B is granted Role B on Domain B. If User B is a member of Domain B, if " -"User B gets a token scoped to Domain B, the token also includes Role B." +"ceilometer-expirer has to be used for deleting samples and its related data " +"from the database." msgstr "" -#: ../telemetry-measurements.rst:861 -msgid "Group is created" -msgstr "" - -#: ../telemetry-measurements.rst:864 -msgid "Group is deleted" -msgstr "" - -#: ../telemetry-measurements.rst:867 -msgid "Group is updated" -msgstr "" - -#: ../identity_concepts.rst:332 -msgid "Groups" -msgstr "" - -#: ../telemetry-data-collection.rst:248 -msgid "HA deployment is NOT supported if the ``pollster-list`` option is used." -msgstr "" - -#: ../telemetry-data-collection.rst:1019 +#: ../telemetry-data-collection.rst:1054 msgid "HBase" msgstr "" -#: ../objectstorage_features.rst:13 -msgid "HDD/node failure agnostic" +#: ../telemetry-data-collection.rst:1054 +msgid "" +"Telemetry's HBase support does not include native TTL nor ceilometer-expirer " +"support." msgstr "" -#: ../compute-live-migration-usage.rst:166 -msgid "HOST" +#: ../telemetry-data-collection.rst:1058 +msgid "DB2 NoSQL" msgstr "" -#: ../blockstorage_nfs_backend.rst:43 -msgid "HOST is the IP address or host name of the NFS server." +#: ../telemetry-data-collection.rst:1058 +msgid "DB2 NoSQL does not have native TTL nor ceilometer-expirer support." msgstr "" -#: ../blockstorage_glusterfs_backend.rst:98 -msgid "HOST is the IP address or host name of the Red Hat Storage server." -msgstr "" - -#: ../compute-images-instances.rst:140 -msgid "HTTP" -msgstr "" - -#: ../ts-HTTP-bad-req-in-cinder-vol-log.rst:6 -msgid "HTTP bad request in cinder volume log" -msgstr "" - -#: ../telemetry-data-collection.rst:1028 +#: ../telemetry-data-collection.rst:1063 msgid "HTTP dispatcher" msgstr "" -#: ../compute-security.rst:83 -msgid "HTTPS port for the attestation service" -msgstr "" - -#: ../objectstorage_features.rst:34 -msgid "Handle many small, random reads and writes efficiently." -msgstr "" - -#: ../telemetry-data-collection.rst:271 -msgid "Hardware resources via SNMP" -msgstr "" - -#: ../identity_concepts.rst:368 -msgid "Here are a couple of examples:" -msgstr "" - -#: ../blockstorage-consistency-groups.rst:33 -msgid "Here are existing policy entries for consistency groups::" -msgstr "" - -#: ../keystone_caching_layer.rst:83 +#: ../telemetry-data-collection.rst:1064 msgid "" -"Here is a list of actions that are affected by the assignment: assign domain " -"API, assign project API, and assign role API." +"The Telemetry module supports sending samples to an external HTTP target. " +"The samples are sent without any modification. To set this option as the " +"collector's target, the ``dispatcher`` has to be changed to ``http`` in the :" +"file:`ceilometer.conf` configuration file. For the list of options that you " +"need to set, see the see the `dispatcher_http section `__ in the OpenStack Configuration Reference." msgstr "" -#: ../keystone_caching_layer.rst:51 +#: ../telemetry-data-collection.rst:1073 +msgid "File dispatcher" +msgstr "" + +#: ../telemetry-data-collection.rst:1074 msgid "" -"Here is a list of actions that are affected by the cached time: getting a " -"new token, revoking tokens, validating tokens, checking v2 tokens, and " -"checking v3 tokens." +"You can store samples in a file by setting the ``dispatcher`` option in the :" +"file:`ceilometer.conf` file. For the list of configuration options, see the " +"`dispatcher_file section `__ in the OpenStack " +"Configuration Reference." msgstr "" -#: ../objectstorage_features.rst:32 -msgid "Higher performance, no bottlenecks." +#: ../telemetry-data-collection.rst:1081 +msgid "Gnocchi dispatcher" msgstr "" -# #-#-#-#-# compute-live-migration-usage.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -# #-#-#-#-# networking_multi-dhcp-agents.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -#: ../compute-live-migration-usage.rst:107 -#: ../networking_multi-dhcp-agents.rst:39 -msgid "Host" -msgstr "" - -#: ../compute-security.rst:79 -msgid "Host name or IP address of the host that runs the attestation service" -msgstr "" - -#: ../ts_non_existent_host.rst:21 +#: ../telemetry-data-collection.rst:1082 msgid "" -"Host names constructed by the driver use just the local hostname, not the " -"fully qualified domain name (FQDN) of the Compute host. For example, if the " -"FQDN was **myhost.example.com**, just **myhost** would be used as the 3PAR " -"hostname. IP addresses are not allowed as host names on the 3PAR storage " -"server." +"The Telemetry module supports sending the metering data to Gnocchi back end " +"through the gnocchi dispatcher. To set this option as the target, change the " +"``dispatcher`` to ``gnocchi`` in the :file:`ceilometer.conf` configuration " +"file." msgstr "" -#: ../blockstorage-driver-filter-weighing.rst:132 -msgid "Host stats for a back end" -msgstr "" - -# #-#-#-#-# compute-live-migration-usage.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -# #-#-#-#-# networking_multi-dhcp-agents.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -#: ../compute-live-migration-usage.rst:114 -#: ../compute-live-migration-usage.rst:121 -#: ../compute-live-migration-usage.rst:128 -#: ../compute-live-migration-usage.rst:149 -#: ../networking_multi-dhcp-agents.rst:46 -msgid "HostA" -msgstr "" - -# #-#-#-#-# compute-live-migration-usage.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -# #-#-#-#-# networking_multi-dhcp-agents.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -#: ../compute-live-migration-usage.rst:82 -#: ../compute-live-migration-usage.rst:135 -#: ../networking_multi-dhcp-agents.rst:48 -msgid "HostB" -msgstr "" - -#: ../compute-live-migration-usage.rst:142 -#: ../compute-live-migration-usage.rst:171 -#: ../compute-live-migration-usage.rst:172 -#: ../compute-live-migration-usage.rst:173 -#: ../compute-live-migration-usage.rst:174 -#: ../compute-live-migration-usage.rst:175 -msgid "HostC" -msgstr "" - -#: ../compute-networking-nova.rst:481 +#: ../telemetry-data-collection.rst:1087 msgid "" -"Hosts access the service at ``169.254.169.254:80``, and this is translated " -"to ``metadata_host:metadata_port`` by an iptables rule established by the " -"``nova-network`` service. In multi-host mode, you can set ``metadata_host`` " -"to ``127.0.0.1``." +"For the list of options that you need to set, see the `dispatcher_gnocchi " +"section `__ in the OpenStack Configuration " +"Reference." msgstr "" -#: ../dashboard_sessions.rst:93 +#: ../telemetry-data-retrieval.rst:3 +msgid "Data retrieval" +msgstr "" + +#: ../telemetry-data-retrieval.rst:5 msgid "" -"However, database-backed sessions are one of the slower session storages and " -"incur a high overhead under heavy usage. Proper configuration of your " -"database deployment can also be a substantial undertaking and is far beyond " -"the scope of this documentation." +"The Telemetry module offers several mechanisms from which the persisted data " +"can be accessed. As described in :ref:`telemetry-system-architecture` and " +"in :ref:`telemetry-data-collection`, the collected information can be stored " +"in one or more database back ends, which are hidden by the Telemetry RESTful " +"API." msgstr "" -#: ../blockstorage_nfs_backend.rst:136 +#: ../telemetry-data-retrieval.rst:12 msgid "" -"However, should you choose to set ``nfs_sparsed_volumes`` to false, you can " -"do so directly in :file:`/etc/cinder/cinder.conf`." +"It is highly recommended not to access directly the database and read or " +"modify any data in it. The API layer hides all the changes in the actual " +"database schema and provides a standard interface to expose the samples, " +"alarms and so forth." msgstr "" -#: ../blockstorage_glusterfs_backend.rst:183 +#: ../telemetry-data-retrieval.rst:18 +msgid "Telemetry v2 API" +msgstr "" + +#: ../telemetry-data-retrieval.rst:19 msgid "" -"However, should you choose to set glusterfs_sparsed_volumes to false, you " -"can do so directly in :file:`/etc/cinder/cinder.conf`." +"The Telemetry module provides a RESTful API, from which the collected " +"samples and all the related information can be retrieved, like the list of " +"meters, alarm definitions and so forth." msgstr "" -#: ../blockstorage_glusterfs_removal.rst:32 +#: ../telemetry-data-retrieval.rst:23 msgid "" -"However, the removed GlusterFS volume might still be mounted on an instance " -"at this point. Typically, this is the case when the volume was already " -"mounted while its entry was deleted from the shares file. Whenever this " -"occurs, you will have to unmount the volume as normal after the Block " -"Storage services are restarted." +"The Telemetry API URL can be retrieved from the service catalog provided by " +"OpenStack Identity, which is populated during the installation process. The " +"API access needs a valid token and proper permission to retrieve data, as " +"described in :ref:`telemetry-users-roles-tenants`." msgstr "" -#: ../objectstorage_ringbuilder.rst:86 +#: ../telemetry-data-retrieval.rst:28 msgid "" -"However, this does mean that the disks in node C have more data than the " -"disks in nodes A and B. If 80% full is the warning threshold for the " -"cluster, node C's disks reach 80% full while A and B's disks are only 72.7% " -"full." +"Further information about the available API endpoints can be found in the " +"`Telemetry API Reference `__." msgstr "" -#: ../compute_arch.rst:216 -msgid "Hybridfox" +#: ../telemetry-data-retrieval.rst:33 +msgid "Query" msgstr "" -#: ../telemetry-measurements.rst:301 ../telemetry-measurements.rst:304 -#: ../telemetry-measurements.rst:307 ../telemetry-measurements.rst:311 -msgid "Hyper-V" -msgstr "" - -#: ../compute_arch.rst:42 -msgid "Hypervisors" -msgstr "" - -#: ../networking_config-agents.rst:178 -msgid "IBM SDN-VE plug-in" -msgstr "" - -#: ../compute-live-migration-usage.rst:34 -msgid "ID" -msgstr "" - -#: ../telemetry-data-collection.rst:441 -msgid "ID of the corresponding resource. (``--resource-id``)" -msgstr "" - -#: ../networking_introduction.rst:337 +#: ../telemetry-data-retrieval.rst:34 msgid "" -"IKEv1 policy support with 3des, aes-128, aes-256, or aes-192 encryption." +"The API provides some additional functionalities, like querying the " +"collected data set. For the samples and alarms API endpoints, both simple " +"and complex query styles are available, whereas for the other endpoints only " +"simple queries are supported." msgstr "" -#: ../telemetry-measurements.rst:565 -msgid "IO CUPS utilization of the system" -msgstr "" - -#: ../compute-networking-nova.rst:624 +#: ../telemetry-data-retrieval.rst:39 msgid "" -"IP forwarding is disabled by default on most Linux distributions. You will " -"need to enable it in order to use floating IPs." +"After validating the query parameters, the processing is done on the " +"database side in the case of most database back ends in order to achieve " +"better performance." msgstr "" -#: ../compute-networking-nova.rst:629 +#: ../telemetry-data-retrieval.rst:43 +msgid "**Simple query**" +msgstr "" + +#: ../telemetry-data-retrieval.rst:45 msgid "" -"IP forwarding only needs to be enabled on the nodes that run ``nova-" -"network``. However, you will need to enable it on all compute nodes if you " -"use ``multi_host`` mode." +"Many of the API endpoints accept a query filter argument, which should be a " +"list of data structures that consist of the following items:" msgstr "" -#: ../telemetry-data-collection.rst:394 -msgid "IPMI agent" +#: ../telemetry-data-retrieval.rst:48 +msgid "``field``" msgstr "" -#: ../telemetry-measurements.rst:506 -msgid "IPMI based meters" +#: ../telemetry-data-retrieval.rst:50 +msgid "``op``" msgstr "" -#: ../telemetry-measurements.rst:1160 -msgid "IPSec connection was created" +#: ../telemetry-data-retrieval.rst:52 +msgid "``value``" msgstr "" -#: ../telemetry-measurements.rst:1165 -msgid "IPSec connection was updated" +#: ../telemetry-data-retrieval.rst:54 +msgid "``type``" msgstr "" -#: ../networking_introduction.rst:339 +#: ../telemetry-data-retrieval.rst:56 msgid "" -"IPSec policy support with 3des, aes-128, aes-192, or aes-256 encryption, " -"sha1 authentication, ESP, AH, or AH-ESP transform protocol, and tunnel or " -"transport mode encapsulation." +"Regardless of the endpoint on which the filter is applied on, it will always " +"target the fields of the `Sample type `__." msgstr "" -#: ../telemetry-measurements.rst:1174 -msgid "IPSec policy was reated" -msgstr "" - -#: ../telemetry-measurements.rst:1179 -msgid "IPSec policy was updated" -msgstr "" - -#: ../networking_adv-features.rst:254 +#: ../telemetry-data-retrieval.rst:60 msgid "" -"Identifies the PORT_ID that represents the VM NIC to which the floating IP " -"should map." +"Several fields of the API endpoints accept shorter names than the ones " +"defined in the reference. The API will do the transformation internally and " +"return the output with the fields that are listed in the `API reference " +"`__. The " +"fields are the following:" msgstr "" -#: ../compute-node-down.rst:25 +#: ../telemetry-data-retrieval.rst:66 +msgid "``project_id``: project" +msgstr "" + +#: ../telemetry-data-retrieval.rst:68 +msgid "``resource_id``: resource" +msgstr "" + +#: ../telemetry-data-retrieval.rst:70 +msgid "``user_id``: user" +msgstr "" + +#: ../telemetry-data-retrieval.rst:72 msgid "" -"Identify the VMs on the affected hosts. To do this, you can use a " -"combination of :command:`nova list` and :command:`nova show` or :command:" -"`euca-describe-instances`. For example, this command displays information " -"about instance i-000015b9 that is running on node np-rcc54:" +"When a filter argument contains multiple constraints of the above form, a " +"logical ``AND`` relation between them is implied." msgstr "" -#: ../identity_concepts.rst:339 -msgid "Identity API V3 provides the following group-related operations:" +#: ../telemetry-data-retrieval.rst:77 +msgid "**Complex query**" msgstr "" -#: ../identity_service_api_protection.rst:3 -msgid "Identity API protection with role-based access control (RBAC)" -msgstr "" - -#: ../keystone_integrate_identity_backend_ldap.rst:229 -msgid "Identity attribute mapping" -msgstr "" - -#: ../identity_concepts.rst:3 -msgid "Identity concepts" -msgstr "" - -#: ../keystone_integrate_with_ldap.rst:40 +#: ../telemetry-data-retrieval.rst:79 msgid "" -"Identity configuration is split into two separate back ends; identity (back " -"end for users and groups), and assignments (back end for domains, projects, " -"roles, role assignments). To configure Identity, set options in the :file:`/" -"etc/keystone/keystone.conf` file. See :ref:`integrate-identity-backend-ldap` " -"for Identity back end configuration examples and :ref:`integrate-assignment-" -"backend-ldap` for assignment back end configuration examples. Modify these " -"examples as needed." +"The filter expressions of the complex query feature operate on the fields of " +"``Sample``, ``Alarm`` and ``AlarmChange`` types. The following comparison " +"operators are supported:" msgstr "" -#: ../identity_management.rst:5 -msgid "Identity management" +#: ../telemetry-data-retrieval.rst:83 +msgid "``=``" msgstr "" -#: ../identity_user_crud.rst:5 +#: ../telemetry-data-retrieval.rst:85 +msgid "``!=``" +msgstr "" + +#: ../telemetry-data-retrieval.rst:87 +msgid "``<``" +msgstr "" + +#: ../telemetry-data-retrieval.rst:89 +msgid "``<=``" +msgstr "" + +#: ../telemetry-data-retrieval.rst:91 +msgid "``>``" +msgstr "" + +#: ../telemetry-data-retrieval.rst:93 +msgid "``>=``" +msgstr "" + +#: ../telemetry-data-retrieval.rst:95 +msgid "The following logical operators can be used:" +msgstr "" + +#: ../telemetry-data-retrieval.rst:97 +msgid "``and``" +msgstr "" + +#: ../telemetry-data-retrieval.rst:99 +msgid "``or``" +msgstr "" + +#: ../telemetry-data-retrieval.rst:101 +msgid "``not``" +msgstr "" + +#: ../telemetry-data-retrieval.rst:105 msgid "" -"Identity provides a user CRUD (Create, Read, Update, and Delete) filter that " -"can be added to the ``public_api`` pipeline. The user CRUD filter enables " -"users to use a HTTP PATCH to change their own password. To enable this " -"extension you should define a :code:`user_crud_extension` filter, insert it " -"after the \"option:`*_body` middleware and before the ``public_service`` " -"application in the ``public_api`` WSGI pipeline in :file:`keystone-paste." -"ini`. For example:" +"The ``not`` operator has different behavior in MongoDB and in the SQLAlchemy-" +"based database engines. If the ``not`` operator is applied on a non existent " +"metadata field then the result depends on the database engine. In case of " +"MongoDB, it will return every sample as the ``not`` operator is evaluated " +"true for every sample where the given field does not exist. On the other " +"hand the SQL-based database engine will return an empty result because of " +"the underlying ``join`` operation." msgstr "" -#: ../identity_concepts.rst:317 -msgid "Identity service functions" -msgstr "" - -#: ../identity_concepts.rst:94 -msgid "Identity user management examples:" -msgstr "" - -#: ../compute-node-down.rst:7 +#: ../telemetry-data-retrieval.rst:114 msgid "" -"If Compute is deployed with a shared file system, and a node fails, there " -"are several methods to quickly recover from the failure. This section " -"discusses manual recovery." +"Complex query supports specifying a list of ``orderby`` expressions. This " +"means that the result of the query can be ordered based on the field names " +"provided in this list. When multiple keys are defined for the ordering, " +"these will be applied sequentially in the order of the specification. The " +"second expression will be applied on the groups for which the values of the " +"first expression are the same. The ordering can be ascending or descending." msgstr "" -#: ../keystone_certificates_for_pki.rst:67 -msgid "" -"If ``provider=keystone.token.providers.uuid.Provider`` in the ``[token]`` " -"section of the keystone configuration, a typical token looks like " -"``53f7f6ef0cc344b5be706bcc8b1479e1``. If ``provider=keystone.token.providers." -"pki.Provider``, a typical token is a much longer string, such as::" +#: ../telemetry-data-retrieval.rst:122 +msgid "The number of returned items can be bounded using the ``limit`` option." msgstr "" -#: ../blockstorage_glusterfs_backend.rst:194 -msgid "" -"If a client host has SELinux enabled, the ``virt_use_fusefs`` boolean should " -"also be enabled if the host requires access to GlusterFS volumes on an " -"instance. To enable this Boolean, run the following command as the ``root`` " -"user::" +#: ../telemetry-data-retrieval.rst:124 +msgid "The ``filter``, ``orderby`` and ``limit`` fields are optional." msgstr "" -#: ../blockstorage_nfs_backend.rst:147 +#: ../telemetry-data-retrieval.rst:128 msgid "" -"If a client host has SELinux enabled, the ``virt_use_nfs`` boolean should " -"also be enabled if the host requires access to NFS volumes on an instance. " -"To enable this boolean, run the following command as the ``root`` user::" +"As opposed to the simple query, complex query is available via a separate " +"API endpoint. For more information see the `Telemetry v2 Web API Reference " +"`__." msgstr "" -#: ../compute-node-down.rst:13 +#: ../telemetry-data-retrieval.rst:133 +msgid "Statistics" +msgstr "" + +#: ../telemetry-data-retrieval.rst:134 msgid "" -"If a cloud compute node fails due to a hardware malfunction or another " -"reason, you can evacuate instances using the :command:`nova evacuate` " -"command. See the `Admin User Guide `__." +"The sample data can be used in various ways for several purposes, like " +"billing or profiling. In external systems the data is often used in the form " +"of aggregated statistics. The Telemetry API provides several built-in " +"functions to make some basic calculations available without any additional " +"coding." +msgstr "" + +#: ../telemetry-data-retrieval.rst:140 +msgid "Telemetry supports the following statistics and aggregation functions:" +msgstr "" + +#: ../telemetry-data-retrieval.rst:143 +msgid "Average of the sample volumes over each period." +msgstr "" + +#: ../telemetry-data-retrieval.rst:143 +msgid "``avg``" +msgstr "" + +#: ../telemetry-data-retrieval.rst:146 +msgid "" +"Count of distinct values in each period identified by a key specified as the " +"parameter of this aggregate function. The supported parameter values are:" +msgstr "" + +#: ../telemetry-data-retrieval.rst:152 +msgid "``resource_id``" +msgstr "" + +#: ../telemetry-data-retrieval.rst:154 +msgid "``cardinality``" +msgstr "" + +#: ../telemetry-data-retrieval.rst:158 +msgid "The ``aggregate.param`` option is required." +msgstr "" + +#: ../telemetry-data-retrieval.rst:161 +msgid "Number of samples in each period." +msgstr "" + +#: ../telemetry-data-retrieval.rst:161 +msgid "``count``" +msgstr "" + +#: ../telemetry-data-retrieval.rst:164 +msgid "Maximum of the sample volumes in each period." +msgstr "" + +#: ../telemetry-data-retrieval.rst:164 +msgid "``max``" +msgstr "" + +#: ../telemetry-data-retrieval.rst:167 +msgid "Minimum of the sample volumes in each period." +msgstr "" + +#: ../telemetry-data-retrieval.rst:167 +msgid "``min``" +msgstr "" + +#: ../telemetry-data-retrieval.rst:170 +msgid "Standard deviation of the sample volumes in each period." +msgstr "" + +#: ../telemetry-data-retrieval.rst:170 +msgid "``stddev``" +msgstr "" + +#: ../telemetry-data-retrieval.rst:173 +msgid "Sum of the sample volumes over each period." +msgstr "" + +#: ../telemetry-data-retrieval.rst:173 +msgid "``sum``" +msgstr "" + +#: ../telemetry-data-retrieval.rst:175 +msgid "" +"The simple query and the statistics functionality can be used together in a " +"single API request." +msgstr "" + +#: ../telemetry-data-retrieval.rst:179 +msgid "Telemetry command line client and SDK" +msgstr "" + +#: ../telemetry-data-retrieval.rst:180 +msgid "" +"The Telemetry module provides a command line client, with which the " +"collected data is available just as the alarm definition and retrieval " +"options. The client uses the Telemetry RESTful API in order to execute the " +"requested operations." +msgstr "" + +#: ../telemetry-data-retrieval.rst:185 +msgid "" +"To be able to use the ``ceilometer`` command, the python-ceilometerclient " +"package needs to be installed and configured properly. For details about the " +"installation process, see the `Telemetry chapter `__ in the " +"OpenStack Installation Guide." +msgstr "" + +#: ../telemetry-data-retrieval.rst:193 +msgid "" +"The Telemetry module captures the user-visible resource usage data. " +"Therefore the database will not contain any data without the existence of " +"these resources, like VM images in the OpenStack Image service." +msgstr "" + +#: ../telemetry-data-retrieval.rst:198 +msgid "" +"Similarly to other OpenStack command line clients, the ``ceilometer`` client " +"uses OpenStack Identity for authentication. The proper credentials and ``--" +"auth_url`` parameter have to be defined via command line parameters or " +"environment variables." +msgstr "" + +#: ../telemetry-data-retrieval.rst:203 +msgid "" +"This section provides some examples without the aim of completeness. These " +"commands can be used for instance for validating an installation of " +"Telemetry." +msgstr "" + +#: ../telemetry-data-retrieval.rst:207 +msgid "" +"To retrieve the list of collected meters, the following command should be " +"used::" +msgstr "" + +#: ../telemetry-data-retrieval.rst:225 +msgid "" +"The ``ceilometer`` command was run with ``admin`` rights, which means that " +"all the data is accessible in the database. For more information about " +"access right see :ref:`telemetry-users-roles-tenants`. As it can be seen in " +"the above example, there are two VM instances existing in the system, as " +"there are VM instance related meters on the top of the result list. The " +"existence of these meters does not indicate that these instances are running " +"at the time of the request. The result contains the currently collected " +"meters per resource, in an ascending order based on the name of the meter." +msgstr "" + +#: ../telemetry-data-retrieval.rst:234 +msgid "" +"Samples are collected for each meter that is present in the list of meters, " +"except in case of instances that are not running or deleted from the " +"OpenStack Compute database. If an instance is no more existing and there is " +"``time_to_live`` value is set in the :file:`ceilometer.conf` configuration " +"file, then a group of samples are deleted in each expiration cycle. When the " +"last sample is deleted for a meter, the database can be cleaned up by " +"running ceilometer-expirer and the meter will not be present in the list " +"above anymore. For more information about the expiration procedure see :ref:" +"`telemetry-storing-samples`." +msgstr "" + +#: ../telemetry-data-retrieval.rst:244 +msgid "" +"The Telemetry API supports simple query on the meter endpoint. The query " +"functionality has the following syntax::" +msgstr "" + +#: ../telemetry-data-retrieval.rst:249 +msgid "" +"The following command needs to be invoked to request the meters of one VM " +"instance::" +msgstr "" + +#: ../telemetry-data-retrieval.rst:274 +msgid "" +"As it was described above, the whole set of samples can be retrieved that " +"are stored for a meter or filtering the result set by using one of the " +"available query types. The request for all the samples of the ``cpu`` meter " +"without any additional filtering looks like the following::" +msgstr "" + +#: ../telemetry-data-retrieval.rst:292 +msgid "" +"The result set of the request contains the samples for both instances " +"ordered by the timestamp field in the default descending order." +msgstr "" + +#: ../telemetry-data-retrieval.rst:295 +msgid "" +"The simple query makes it possible to retrieve only a subset of the " +"collected samples. The following command can be executed to request the " +"``cpu`` samples of only one of the VM instances::" +msgstr "" + +#: ../telemetry-data-retrieval.rst:313 +msgid "" +"As it can be seen on the output above, the result set contains samples for " +"only one instance of the two." +msgstr "" + +#: ../telemetry-data-retrieval.rst:316 +msgid "" +"The ``ceilometer query-samples`` command is used to execute rich queries. " +"This command accepts the following parameters:" +msgstr "" + +#: ../telemetry-data-retrieval.rst:320 +msgid "" +"Contains the filter expression for the query in the form of: ``{complex_op: " +"[{simple_op: {field_name: value}}]}``." +msgstr "" + +#: ../telemetry-data-retrieval.rst:321 +msgid "``--filter``" +msgstr "" + +#: ../telemetry-data-retrieval.rst:324 +msgid "" +"Contains the list of ``orderby`` expressions in the form of: ``[{field_name: " +"direction}, {field_name: direction}]``." +msgstr "" + +#: ../telemetry-data-retrieval.rst:325 +msgid "``--orderby``" +msgstr "" + +#: ../telemetry-data-retrieval.rst:328 +msgid "Specifies the maximum number of samples to return." +msgstr "" + +#: ../telemetry-data-retrieval.rst:328 +msgid "``--limit``" +msgstr "" + +#: ../telemetry-data-retrieval.rst:330 +msgid "" +"For more information about complex queries see :ref:`Complex query `." +msgstr "" + +#: ../telemetry-data-retrieval.rst:333 +msgid "" +"As the complex query functionality provides the possibility of using complex " +"operators, it is possible to retrieve a subset of samples for a given VM " +"instance. To request for the first six samples for the ``cpu`` and ``disk." +"read.bytes`` meters, the following command should be invoked::" +msgstr "" + +#: ../telemetry-data-retrieval.rst:352 +msgid "" +"Ceilometer also captures data as Events, which represents the state of a " +"resource. Refer to :doc:`/telemetry-events` for more information regarding " +"Events." +msgstr "" + +#: ../telemetry-data-retrieval.rst:356 +msgid "" +"To retrieve a list of recent events that occurred in the system, the " +"following command can be executed:" +msgstr "" + +#: ../telemetry-data-retrieval.rst:390 +msgid "" +"In Liberty, the data returned corresponds to the role and user. Non-admin " +"users will only returned events that are scoped to them. Admin users will be " +"returned all events related to the project they administer as well as all " +"unscoped events." +msgstr "" + +#: ../telemetry-data-retrieval.rst:395 +msgid "" +"Similar to querying meters, additional filter parameters can be given to " +"retrieve specific events:" +msgstr "" + +#: ../telemetry-data-retrieval.rst:438 +msgid "Telemetry python bindings" +msgstr "" + +#: ../telemetry-data-retrieval.rst:439 +msgid "" +"The command line client library provides python bindings in order to use the " +"Telemetry Python API directly from python programs." +msgstr "" + +#: ../telemetry-data-retrieval.rst:442 +msgid "" +"The first step in setting up the client is to create a client instance with " +"the proper credentials::" +msgstr "" + +#: ../telemetry-data-retrieval.rst:448 +msgid "" +"The ``VERSION`` parameter can be ``1`` or ``2``, specifying the API version " +"to be used." +msgstr "" + +#: ../telemetry-data-retrieval.rst:451 +msgid "The method calls look like the following::" +msgstr "" + +#: ../telemetry-data-retrieval.rst:459 +msgid "" +"For further details about the python-ceilometerclient package, see the " +"`Python bindings to the OpenStack Ceilometer API `__ reference." +msgstr "" + +#: ../telemetry-data-retrieval.rst:467 +msgid "Publishers" +msgstr "" + +#: ../telemetry-data-retrieval.rst:468 +msgid "" +"The Telemetry module provides several transport methods to forward the data " +"collected to the ceilometer-collector service or to an external system. The " +"consumers of this data are widely different, like monitoring systems, for " +"which data loss is acceptable and billing systems, which require reliable " +"data transportation. Telemetry provides methods to fulfill the requirements " +"of both kind of systems, as it is described below." +msgstr "" + +#: ../telemetry-data-retrieval.rst:476 +msgid "" +"The publisher component makes it possible to persist the data into storage " +"through the message bus or to send it to one or more external consumers. One " +"chain can contain multiple publishers." +msgstr "" + +#: ../telemetry-data-retrieval.rst:480 +msgid "" +"To solve the above mentioned problem, the notion of multi-publisher can be " +"configured for each datapoint within the Telemetry module, allowing the same " +"technical meter or event to be published multiple times to multiple " +"destinations, each potentially using a different transport." +msgstr "" + +#: ../telemetry-data-retrieval.rst:485 +msgid "" +"Publishers can be specified in the ``publishers`` section for each pipeline " +"(for further details about pipelines see :ref:`data-collection-and-" +"processing`) that is defined in the `pipeline.yaml `__ file." +msgstr "" + +#: ../telemetry-data-retrieval.rst:492 +msgid "The following publisher types are supported:" +msgstr "" + +#: ../telemetry-data-retrieval.rst:495 +msgid "" +"It can be specified in the form of ``notifier://?" +"option1=value1&option2=value2``. It emits data over AMQP using oslo." +"messaging. This is the recommended method of publishing." +msgstr "" + +#: ../telemetry-data-retrieval.rst:498 +msgid "notifier" +msgstr "" + +#: ../telemetry-data-retrieval.rst:501 +msgid "" +"It can be specified in the form of ``rpc://?option1=value1&option2=value2``. " +"It emits metering data over lossy AMQP. This method is synchronous and may " +"experience performance issues. This publisher is deprecated in Liberty in " +"favour of the notifier publisher." +msgstr "" + +#: ../telemetry-data-retrieval.rst:505 +msgid "rpc" +msgstr "" + +#: ../telemetry-data-retrieval.rst:508 +msgid "" +"It can be specified in the form of ``udp://:/``. It emits " +"metering data for over UDP." +msgstr "" + +#: ../telemetry-data-retrieval.rst:509 +msgid "udp" +msgstr "" + +#: ../telemetry-data-retrieval.rst:512 +msgid "" +"It can be specified in the form of ``file://path?" +"option1=value1&option2=value2``. This publisher records metering data into a " +"file." +msgstr "" + +#: ../telemetry-data-retrieval.rst:514 +msgid "file" msgstr "" #: ../telemetry-data-retrieval.rst:518 @@ -8158,158 +21268,286 @@ msgid "" "Telemetry." msgstr "" -#: ../networking_adv-features.rst:144 +#: ../telemetry-data-retrieval.rst:523 msgid "" -"If a physical network named \"default\" has been configured and if provider:" -"network_type is ``flat`` or ``vlan``, then \"default\" is used." +"It can be specified in the form of: ``kafka://kafka_broker_ip: " +"kafka_broker_port?topic=kafka_topic &option1=value1``." msgstr "" -#: ../compute-flavors.rst:256 -msgid "" -"If a random-number generator device has been added to the instance through " -"its image properties, the device can be enabled and configured using:" +#: ../telemetry-data-retrieval.rst:527 +msgid "This publisher sends metering data to a kafka broker." msgstr "" -#: ../keystone_caching_layer.rst:91 -msgid "" -"If a read-only ``assignment`` back end is in use, the cache will not " -"immediately reflect changes on the back end. Any given change may take up to " -"the ``cache_time`` (if set in the ``[assignment]`` section of the " -"configuration file) or the global ``expiration_time`` (set in the " -"``[cache]`` section of the configuration file) before it is reflected. If " -"this type of delay (when using a read-only ``assignment`` back end) is an " -"issue, it is recommended that caching be disabled on ``assignment``. To " -"disable caching specifically on ``assignment``, in the ``[assignment]`` " -"section of the configuration set ``caching`` to ``False``." +#: ../telemetry-data-retrieval.rst:527 +msgid "kafka" msgstr "" -#: ../objectstorage_replication.rst:66 +#: ../telemetry-data-retrieval.rst:531 msgid "" -"If a replica is missing, the whole local database file is transmitted to the " -"peer by using rsync(1) and is assigned a new unique ID." +"If the topic parameter is missing, this publisher brings out metering data " +"under a topic name, ``ceilometer``. When the port number is not specified, " +"this publisher uses 9092 as the broker's port." msgstr "" -#: ../objectstorage_replication.rst:28 +#: ../telemetry-data-retrieval.rst:536 msgid "" -"If a replicator detects that a remote drive has failed, the replicator uses " -"the ``get_more_nodes`` interface for the ring to choose an alternate node " -"with which to synchronize. The replicator can maintain desired levels of " -"replication during disk failures, though some replicas might not be in an " -"immediately usable location." +"The following options are available for ``rpc`` and ``notifier``. The policy " +"option can be used by ``kafka`` publisher:" msgstr "" -#: ../objectstorage-troubleshoot.rst:31 +#: ../telemetry-data-retrieval.rst:540 msgid "" -"If a server is having hardware issues, it is a good idea to make sure the " -"Object Storage services are not running. This will allow Object Storage to " -"work around the failure while you troubleshoot." +"The value of it is 1. It is used for publishing the samples on additional " +"``metering_topic.sample_name`` topic queue besides the default " +"``metering_topic`` queue." msgstr "" -#: ../blockstorage_multi_backend.rst:158 -msgid "" -"If a volume type points to a ``volume_backend_name`` that does not exist in " -"the Block Storage configuration, the ``filter_scheduler`` returns an error " -"that it cannot find a valid host with the suitable back end." +#: ../telemetry-data-retrieval.rst:542 +msgid "``per_meter_topic``" msgstr "" -#: ../objectstorage_components.rst:237 +#: ../telemetry-data-retrieval.rst:545 msgid "" -"If a zone goes down, one of the nodes containing a replica notices and " -"proactively copies data to a handoff location." +"It is used for configuring the behavior for the case, when the publisher " +"fails to send the samples, where the possible predefined values are the " +"following:" msgstr "" -#: ../identity_troubleshoot.rst:144 -msgid "" -"If an error occurs when the signing key file opens, it is possible that the " -"person who ran the ``keystone-manage pki_setup`` command to generate " -"certificates and keys did not use the correct user. When you run the " -"``keystone-manage pki_setup`` command, Identity generates a set of " -"certificates and keys in ``/etc/keystone/ssl*``, which is owned by ``root:" -"root``." +#: ../telemetry-data-retrieval.rst:550 +msgid "Used for waiting and blocking until the samples have been sent." msgstr "" -#: ../keystone_certificates_for_pki.rst:163 -msgid "" -"If everything is successful, you should end up with :file:`signing_cert_req." -"pem` and :file:`signing_key.pem`. Send :file:`signing_cert_req.pem` to your " -"CA to request a token signing certificate and make sure to ask the " -"certificate to be in PEM format. Also, make sure your trusted CA certificate " -"chain is also in PEM format." +#: ../telemetry-data-retrieval.rst:550 +msgid "default" msgstr "" -#: ../blockstorage_volume_backups.rst:104 -msgid "" -"If instead you want to use an NFS export as the backup repository, add the " -"following configuration options to the ``[DEFAULT]`` section of the :file:" -"`cinder.conf` file and restart the Block Storage services:" +#: ../telemetry-data-retrieval.rst:553 +msgid "Used for dropping the samples which are failed to be sent." msgstr "" -#: ../blockstorage_image_volume_cache.rst:95 -msgid "" -"If needed, you can delete these volumes manually to clear the cache. By " -"using the standard volume deletion APIs, the Block Storage service will " -"clean up correctly." +#: ../telemetry-data-retrieval.rst:553 +msgid "drop" msgstr "" -#: ../networking_config-agents.rst:106 +#: ../telemetry-data-retrieval.rst:556 msgid "" -"If no dnsmasq process for subnet's network is launched, Networking will " -"launch a new one on subnet's dhcp port in ``qdhcp-XXX`` namespace. If " -"previous dnsmasq process is already launched, restart dnsmasq with a new " -"configuration." +"Used for creating an in-memory queue and retrying to send the samples on the " +"queue on the next samples publishing period (the queue length can be " +"configured with ``max_queue_length``, where 1024 is the default value)." msgstr "" -#: ../compute-node-down.rst:270 -msgid "" -"If some services depend on the volume, or if a volume has an entry in fstab, " -"you should now be able to restart the instance. Restart directly from the " -"instance itself, not through ``nova``:" +#: ../telemetry-data-retrieval.rst:559 +msgid "``policy``" msgstr "" -#: ../telemetry-troubleshooting-guide.rst:59 -msgid "" -"If the **ceilometer-agent-notification** service is not installed and " -"started, samples originating from notifications will not be generated. In " -"case of the lack of notification based samples, the state of this service " -"and the log file of Telemetry should be checked first." +#: ../telemetry-data-retrieval.rst:559 +msgid "queue" msgstr "" -#: ../keystone_certificates_for_pki.rst:63 +#: ../telemetry-data-retrieval.rst:561 msgid "" -"If the :command:`keystone-manage pki_setup` command is not used to generate " -"certificates, or you are providing your own certificates, these values do " -"not need to be set." +"The following option is additionally available for the ``notifier`` " +"publisher:" msgstr "" -#: ../compute-networking-nova.rst:966 +#: ../telemetry-data-retrieval.rst:564 msgid "" -"If the :command:`nslookup` command sometimes hangs, and there are packets " -"that appear in the first terminal but not the second, then the problem may " -"be due to filtering done on the bridges. Try disabling filtering, and " -"running these commands as root:" +"The topic name of queue to publish to. Setting this will override the " +"default topic defined by ``metering_topic`` and ``event_topic`` options. " +"This option can be used to support multiple consumers. Support for this " +"feature was added in Kilo." msgstr "" -#: ../networking_adv-config.rst:49 -msgid "" -"If the Linux installation does not support network namespaces, you must " -"disable network namespaces in the L3 metering configuration file. The " -"default value of the ``use_namespaces`` option is ``True``." +#: ../telemetry-data-retrieval.rst:567 +msgid "``topic``" msgstr "" -#: ../compute-networking-nova.rst:832 -msgid "" -"If the Virtual Network Service Neutron is installed, you can specify the " -"networks to attach to the interfaces by using the ``--nic`` flag with the :" -"command:`nova` command:" +#: ../telemetry-data-retrieval.rst:569 +msgid "The following options are available for the ``file`` publisher:" msgstr "" -#: ../blockstorage_volume_backed_image.rst:61 +#: ../telemetry-data-retrieval.rst:572 msgid "" -"If the ``image_upload_use_cinder_backend`` option is enabled, the following " -"command creates a new Image-Volume by cloning the specified volume and then " -"registers its location to a new image. The disk format and the container " -"format must be raw and bare (default). Otherwise, the image is uploaded to " -"the default store of the Image service.::" +"When this option is greater than zero, it will cause a rollover. When the " +"size is about to be exceeded, the file is closed and a new file is silently " +"opened for output. If its value is zero, rollover never occurs." +msgstr "" + +#: ../telemetry-data-retrieval.rst:575 +msgid "``max_bytes``" +msgstr "" + +#: ../telemetry-data-retrieval.rst:578 +msgid "" +"If this value is non-zero, an extension will be appended to the filename of " +"the old log, as '.1', '.2', and so forth until the specified value is " +"reached. The file that is written and contains the newest data is always the " +"one that is specified without any extensions." +msgstr "" + +#: ../telemetry-data-retrieval.rst:582 +msgid "``backup_count``" +msgstr "" + +#: ../telemetry-data-retrieval.rst:584 +msgid "" +"The default publisher is ``notifier``, without any additional options " +"specified. A sample ``publishers`` section in the :file:`/etc/ceilometer/" +"pipeline.yaml` looks like the following::" +msgstr "" + +#: ../telemetry-events.rst:3 +msgid "Events" +msgstr "" + +#: ../telemetry-events.rst:5 +msgid "" +"In addition to meters, the Telemetry module collects events triggered within " +"an OpenStack environment. This section provides a brief summary of the " +"events format in the Telemetry module." +msgstr "" + +#: ../telemetry-events.rst:9 +msgid "" +"While a sample represents a single, numeric datapoint within a time-series, " +"an event is a broader concept that represents the state of a resource at a " +"point in time. The state may be described using various data types including " +"non-numeric data such as an instance's flavor. In general, events represent " +"any action made in the OpenStack system." +msgstr "" + +#: ../telemetry-events.rst:16 +msgid "Event configuration" +msgstr "" + +#: ../telemetry-events.rst:17 +msgid "" +"To enable the creation and storage of events in the Telemetry module " +"``store_events`` option needs to be set to ``True``. For further " +"configuration options, see the event section in the `OpenStack Configuration " +"Reference `__." +msgstr "" + +#: ../telemetry-events.rst:24 +msgid "" +"It is advisable to set ``disable_non_metric_meters`` to ``True`` when " +"enabling events in the Telemetry module. The Telemetry module historically " +"represented events as metering data, which may create duplication of data if " +"both events and non-metric meters are enabled." +msgstr "" + +#: ../telemetry-events.rst:31 +msgid "Event structure" +msgstr "" + +#: ../telemetry-events.rst:32 +msgid "" +"Events captured by the Telemetry module are represented by five key " +"attributes:" +msgstr "" + +#: ../telemetry-events.rst:36 +msgid "" +"A dotted string defining what event occurred such as ``\"compute.instance." +"resize.start\"``." +msgstr "" + +#: ../telemetry-events.rst:37 ../telemetry-events.rst:125 +msgid "event\\_type" +msgstr "" + +#: ../telemetry-events.rst:40 +msgid "A UUID for the event." +msgstr "" + +#: ../telemetry-events.rst:40 +msgid "message\\_id" +msgstr "" + +#: ../telemetry-events.rst:43 +msgid "A timestamp of when the event occurred in the system." +msgstr "" + +#: ../telemetry-events.rst:43 +msgid "generated" +msgstr "" + +#: ../telemetry-events.rst:46 +msgid "" +"A flat mapping of key-value pairs which describe the event. The event's " +"traits contain most of the details of the event. Traits are typed, and can " +"be strings, integers, floats, or datetimes." +msgstr "" + +#: ../telemetry-events.rst:48 ../telemetry-events.rst:129 +msgid "traits" +msgstr "" + +#: ../telemetry-events.rst:51 +msgid "" +"Mainly for auditing purpose, the full event message can be stored " +"(unindexed) for future evaluation." +msgstr "" + +# #-#-#-#-# telemetry-events.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +# #-#-#-#-# ts-eql-volume-size.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +#: ../telemetry-events.rst:52 ../ts-eql-volume-size.rst:113 +msgid "raw" +msgstr "" + +#: ../telemetry-events.rst:55 +msgid "Event indexing" +msgstr "" + +#: ../telemetry-events.rst:56 +msgid "" +"The general philosophy of notifications in OpenStack is to emit any and all " +"data someone might need, and let the consumer filter out what they are not " +"interested in. In order to make processing simpler and more efficient, the " +"notifications are stored and processed within Ceilometer as events. The " +"notification payload, which can be an arbitrarily complex JSON data " +"structure, is converted to a flat set of key-value pairs. This conversion is " +"specified by a config file." +msgstr "" + +#: ../telemetry-events.rst:66 +msgid "" +"The event format is meant for efficient processing and querying. Storage of " +"complete notifications for auditing purposes can be enabled by configuring " +"``store_raw`` option." +msgstr "" + +#: ../telemetry-events.rst:71 +msgid "Event conversion" +msgstr "" + +#: ../telemetry-events.rst:72 +msgid "" +"The conversion from notifications to events is driven by a configuration " +"file defined by the ``definitions_cfg_file`` in the :file:`ceilometer.conf` " +"configuration file." +msgstr "" + +#: ../telemetry-events.rst:76 +msgid "" +"This includes descriptions of how to map fields in the notification body to " +"Traits, and optional plug-ins for doing any programmatic translations " +"(splitting a string, forcing case)." +msgstr "" + +#: ../telemetry-events.rst:80 +msgid "" +"The mapping of notifications to events is defined per event\\_type, which " +"can be wildcarded. Traits are added to events if the corresponding fields in " +"the notification exist and are non-null." +msgstr "" + +#: ../telemetry-events.rst:86 +msgid "" +"The default definition file included with the Telemetry module contains a " +"list of known notifications and useful traits. The mappings provided can be " +"modified to include more or less data according to user requirements." msgstr "" #: ../telemetry-events.rst:91 @@ -8323,705 +21561,146 @@ msgid "" "dropped." msgstr "" -#: ../ts_cinder_config.rst:138 -msgid "If the file is not present, create it with this command" -msgstr "" - -#: ../identity_troubleshoot.rst:107 -msgid "" -"If the files do not appear in your directory after this, it is likely one of " -"the following issues:" -msgstr "" - -#: ../blockstorage_volume_backed_image.rst:13 -msgid "" -"If the image is set to public in the Image service, the volume data can be " -"shared among tenants." -msgstr "" - -#: ../blockstorage_backup_disks.rst:152 -msgid "If the partition mounts successfully, no errors are returned." -msgstr "" - -#: ../telemetry-best-practices.rst:24 -msgid "" -"If the polling interval is too short, it will likely cause increase of " -"stored data and the stress on the service APIs." -msgstr "" - -#: ../compute-root-wrap-reference.rst:67 -msgid "" -"If the root wrapper is not performing correctly, you can add a workaround " -"option into the :file:`nova.conf` configuration file. This workaround re-" -"configures the root wrapper configuration to fall back to running commands " -"as sudo, and is a Kilo release feature." -msgstr "" - -#: ../telemetry-data-collection.rst:435 -msgid "" -"If the sample corresponds to an existing meter, then the fields like ``meter-" -"type`` and meter name should be matched accordingly." -msgstr "" - -#: ../objectstorage-troubleshoot.rst:41 -msgid "" -"If the server has more serious issues, then it is probably best to remove " -"all of the server's devices from the ring. Once the server has been repaired " -"and is back online, the server's devices can be added back into the ring. It " -"is important that the devices are reformatted before putting them back into " -"the ring as it is likely to be responsible for a different set of partitions " -"than before." -msgstr "" - -#: ../objectstorage-troubleshoot.rst:35 -msgid "" -"If the server just needs a reboot, or a small amount of work that should " -"only last a couple of hours, then it is probably best to let Object Storage " -"work around the failure and get the machine fixed and back online. When the " -"machine comes back online, replication will make sure that anything that is " -"missing during the downtime will get updated." -msgstr "" - -#: ../cross_project_cors.rst:169 -msgid "" -"If the service does not return any access control headers, check the service " -"log, such as :code:`/var/log/upstart/ironic-api.log` for an indication on " -"what went wrong." -msgstr "" - -#: ../orchestration-auth-model.rst:39 -msgid "" -"If the stack contains any resources marked as requiring deferred operations, " -"orchestration engine will fail validation checks if no username/password is " -"provided." -msgstr "" - -#: ../blockstorage_volume_migration.rst:19 -msgid "" -"If the storage can migrate the volume on its own, it is given the " -"opportunity to do so. This allows the Block Storage driver to enable " -"optimizations that the storage might be able to perform. If the back-end is " -"not able to perform the migration, the Block Storage uses one of two generic " -"flows, as follows." -msgstr "" - -#: ../blockstorage_backup_disks.rst:131 -msgid "" -"If the tools successfully find and map the partition table, no errors are " -"returned." -msgstr "" - -#: ../telemetry-data-retrieval.rst:531 -msgid "" -"If the topic parameter is missing, this publisher brings out metering data " -"under a topic name, ``ceilometer``. When the port number is not specified, " -"this publisher uses 9092 as the broker's port." -msgstr "" - -#: ../identity_concepts.rst:190 -msgid "" -"If the user has any role in a tenant, he can create volumes in that tenant." -msgstr "" - -#: ../blockstorage_volume_migration.rst:35 -msgid "" -"If the volume is attached to a VM instance, the Block Storage creates a " -"volume, and calls Compute to copy the data from the original to the new " -"volume. Currently this is supported only by the Compute libvirt driver." -msgstr "" - -#: ../blockstorage_volume_migration.rst:25 -msgid "" -"If the volume is not attached, the Block Storage service creates a volume " -"and copies the data from the original to the new volume." -msgstr "" - -#: ../networking_config-agents.rst:358 -msgid "" -"If this option is already defined, add ``lbaas`` to the list, using a comma " -"as separator. For example:" -msgstr "" - -#: ../networking_config-agents.rst:312 -msgid "" -"If this option is already defined, add ``metering`` to the list, using a " -"comma as separator. For example:" -msgstr "" - -#: ../compute-networking-nova.rst:741 -msgid "" -"If this option is enabled, but all floating IP addresses have already been " -"allocated, the :command:`nova boot` command will fail." -msgstr "" - -#: ../compute-networking-nova.rst:901 -msgid "" -"If this solves the problem, add the following line to :file:`/etc/sysctl." -"conf` so that the reverse-path filter is persistent:" -msgstr "" - -#: ../compute-networking-nova.rst:977 -msgid "" -"If this solves your issue, add the following line to :file:`/etc/sysctl." -"conf` so that the changes are persistent:" -msgstr "" - -#: ../telemetry-data-retrieval.rst:578 -msgid "" -"If this value is non-zero, an extension will be appended to the filename of " -"the old log, as '.1', '.2', and so forth until the specified value is " -"reached. The file that is written and contains the newest data is always the " -"one that is specified without any extensions." -msgstr "" - -#: ../blockstorage_over_subscription.rst:76 -msgid "" -"If volume type is provided as part of the volume creation request, it can " -"have the following extra specs defined:" -msgstr "" - -#: ../identity_troubleshoot.rst:130 -msgid "" -"If you are not using a ``/var/cache`` sub-directory, you should. Modify the " -"``signing_dir`` configuration option for your service and restart." -msgstr "" - -#: ../telemetry-best-practices.rst:42 -msgid "" -"If you are using Juno or later releases, based on the number of resources " -"that will be polled, you can add additional central and compute agents as " -"necessary. The agents are designed to scale horizontally." -msgstr "" - -#: ../telemetry-best-practices.rst:51 -msgid "" -"If you are using Juno or later releases, use the ``notifier://`` publisher " -"rather than ``rpc://`` as there is a certain level of overhead that comes " -"with RPC." -msgstr "" - -#: ../compute-networking-nova.rst:230 -msgid "" -"If you are using OpenStack Compute with ``nova-network``, you can put " -"Compute into dual-stack mode, so that it uses both IPv4 and IPv6 addresses " -"for communication. In dual-stack mode, instances can acquire their IPv6 " -"global unicast address by using a stateless address auto-configuration " -"mechanism [RFC 4862/2462]. IPv4/IPv6 dual-stack mode works with both " -"``VlanManager`` and ``FlatDHCPManager`` networking modes." -msgstr "" - -#: ../compute-node-down.rst:73 -msgid "" -"If you are using a hypervisor that relies on libvirt (such as KVM), update " -"the :file:`libvirt.xml` file (found in :file:`/var/lib/nova/instances/" -"[instance ID]`) with these changes:" -msgstr "" - -#: ../networking_config-identity.rst:63 -msgid "" -"If you are using the *template driver*, specify the following parameters in " -"your Compute catalog template file (:file:`default_catalog.templates`), " -"along with the region (``$REGION``) and IP address of the Networking server " -"(``$IP``)." -msgstr "" - -#: ../telemetry-best-practices.rst:35 -msgid "" -"If you are using the Kilo version of Telemetry, you can delay or adjust " -"polling requests by enabling the jitter support. This adds a random delay on " -"how the polling agents send requests to the service APIs. To enable jitter, " -"set ``shuffle_time_before_polling_task`` in the :file:`ceilometer.conf` " -"configuration file to an integer greater than 0." -msgstr "" - -#: ../compute-networking-nova.rst:924 -msgid "" -"If you can access your instances with ``SSH`` but the network to your " -"instance is slow, or if you find that running certain operations are slower " -"than they should be (for example, ``sudo``), packet loss could be occurring " -"on the connection to the instance." -msgstr "" - -#: ../compute-networking-nova.rst:846 -msgid "If you cannot reach your instances through the floating IP address:" -msgstr "" - -#: ../objectstorage-troubleshoot.rst:19 -msgid "" -"If you cannot replace the drive immediately, then it is best to leave it " -"unmounted, and remove the drive from the ring. This will allow all the " -"replicas that were on that drive to be replicated elsewhere until the drive " -"is replaced. Once the drive is replaced, it can be re-added to the ring." -msgstr "" - -#: ../blockstorage_backup_disks.rst:141 -msgid "" -"If you created more than one partition on that volume, you see several " -"partitions; for example: ``cinder--volumes-volume--00000001--snapshot2``, " -"``cinder--volumes-volume--00000001--snapshot3``, and so on." -msgstr "" - -#: ../compute-admin-password-injection.rst:18 -msgid "" -"If you do not want to support password injection, disable the password " -"fields by editing the dashboard's :file:`local_settings` file. On Fedora/" -"RHEL/CentOS, the file location is :file:`/etc/openstack-dashboard/" -"local_settings`. On Ubuntu and Debian, it is :file:`/etc/openstack-dashboard/" -"local_settings.py`. On openSUSE and SUSE Linux Enterprise Server, it is :" -"file:`/srv/www/openstack-dashboard/openstack_dashboard/local/local_settings." -"py`" -msgstr "" - -#: ../blockstorage_volume_backups_export_import.rst:35 -msgid "" -"If you have placed encryption on your volumes, the encryption will still be " -"in place when you restore the volume if a UUID encryption key is specified " -"when creating volumes. Using backup metadata support, UUID keys set up for a " -"volume (or volumes) will remain valid when you restore a backed-up volume. " -"The restored volume will remain encrypted, and will be accessible with your " -"credentials." -msgstr "" - -#: ../compute-networking-nova.rst:562 -msgid "" -"If you have run these commands and still cannot ping or SSH your instances, " -"check the number of running ``dnsmasq`` processes, there should be two. If " -"not, kill the processes and restart the service with these commands:" -msgstr "" - -#: ../database.rst:215 -msgid "" -"If you just created a MySQL or Percona datastore, then you need to load the " -"appropriate validation rules, as described in this step." -msgstr "" - -#: ../database.rst:218 -msgid "If you just created a different datastore, skip this step." -msgstr "" - -#: ../compute-networking-nova.rst:599 -msgid "" -"If you make changes to the :file:`/etc/nova/nova.conf` file while the ``nova-" -"network`` service is running, you will need to restart the service to pick " -"up the changes." -msgstr "" - -#: ../keystone_use_trusts.rst:31 -msgid "" -"If you omit all privileges, nothing is delegated. You cannot delegate " -"everything." -msgstr "" - -#: ../blockstorage_volume_migration.rst:125 -msgid "" -"If you plan to decommission a block storage node, you must stop the " -"``cinder`` volume service on the node after performing the migration." -msgstr "" - -#: ../networking_config-agents.rst:78 -msgid "" -"If you reboot a node that runs the DHCP agent, you must run the :command:" -"`neutron-ovs-cleanup` command before the neutron-dhcp-agent service starts." -msgstr "" - -#: ../networking_config-agents.rst:259 -msgid "" -"If you reboot a node that runs the L3 agent, you must run the :command:" -"`neutron-ovs-cleanup` command before the neutron-l3-agent service starts." -msgstr "" - -#: ../identity_troubleshoot.rst:22 -msgid "" -"If you receive an ``Invalid OpenStack Identity Credentials`` message when " -"you talk to an OpenStack service, it might be caused by the changeover from " -"UUID tokens to PKI tokens in the Grizzly release. Learn how to troubleshoot " -"this error." -msgstr "" - -#: ../blockstorage_volume_backups.rst:95 -msgid "" -"If you specify a UUID encryption key when setting up the volume " -"specifications, the backup metadata ensures that the key will remain valid " -"when you back up and restore the volume." -msgstr "" - -#: ../compute-images-instances.rst:285 -msgid "" -"If you specify a file name value and the file is not found, the `glance-api` " -"service does not start." -msgstr "" - -#: ../telemetry-data-collection.rst:865 -msgid "" -"If you take a look at the :file:`meter.yaml` file, it contains the sample " -"definitions for all the meters that Telemetry is collecting from " -"notifications. The value of each field is specified by using json path in " -"order to find the right value from the notification message. In order to be " -"able to specify the right field you need to be aware of the format of the " -"consumed notification. The values that need to be searched in the " -"notification message are set with a json path starting with ``$.`` For " -"instance, if you need the ``size`` information from the payload you can " -"define it like ``$.payload.size``." -msgstr "" - -#: ../dashboard_sessions.rst:188 -msgid "" -"If you use Django 1.4 or later, the ``signed_cookies`` back end avoids " -"server load and scaling problems." -msgstr "" - -#: ../networking_config-identity.rst:125 -msgid "" -"If you use Networking, do not run the Compute nova-network service (like you " -"do in traditional Compute deployments). Instead, Compute delegates most " -"network-related decisions to Networking. Compute proxies tenant-facing API " -"calls to manage security groups and floating IPs to Networking APIs. " -"However, operator-facing tools such as nova-manage, are not proxied and " -"should not be used." -msgstr "" - -#: ../networking_config-agents.rst:282 -msgid "" -"If you use one of the following plug-ins, you need to configure the metering " -"agent with these lines as well:" -msgstr "" - -#: ../networking_config-identity.rst:41 -msgid "" -"If you use the *SQL driver*, run the following command with the specified " -"region (``$REGION``), IP address of the Networking server (``$IP``), and " -"service ID (``$NEUTRON_SERVICE_ID``, obtained in the previous step)." -msgstr "" - -#: ../networking_config-agents.rst:26 -msgid "" -"If you use the NSX plug-in, you must also install Open vSwitch on each data-" -"forwarding node. However, you do not need to install an additional agent on " -"each node." -msgstr "" - -#: ../telemetry-data-collection.rst:931 -msgid "" -"If you want to collect OpenStack Block Storage notification on demand, you " -"can use ``cinder-volume-usage-audit`` from OpenStack Block Storage. This " -"script becomes available when you install OpenStack Block Storage, so you " -"can use it without any specific settings and you don't need to authenticate " -"to access the data. To use it, you must run this command in the following " -"format::" -msgstr "" - -#: ../database.rst:181 -msgid "" -"If you want to put additional packages on each guest that you create with " -"this datastore version, you can list the package names here." -msgstr "" - -#: ../compute-node-down.rst:309 -msgid "" -"If you want to script the disaster recovery plan (DRP), a bash script is " -"available from `https://github.com/Razique `_ which performs the following steps:" -msgstr "" - -#: ../objectstorage_arch.rst:15 -msgid "" -"If you want to use OpenStack Identity API v3 for authentication, you have " -"the following options available in :file:`/etc/swift/dispersion.conf`: " -"``auth_version``, ``user_domain_name``, ``project_domain_name``, and " -"``project_name``." -msgstr "" - -#: ../compute-networking-nova.rst:359 -msgid "" -"If you write a consumer for one of these APIs, always attempt to access the " -"most recent API version supported by your consumer first, then fall back to " -"an earlier version if the most recent one is not available." -msgstr "" - -#: ../keystone_certificates_for_pki.rst:208 -msgid "" -"If your certificate directory path is different from the default :file:`/etc/" -"keystone/ssl/certs`, make sure it is reflected in the ``[signing]`` section " -"of the configuration file." -msgstr "" - -#: ../identity_troubleshoot.rst:136 -msgid "" -"If your certificates are fetched on demand, the PKI validation is working " -"properly. Most likely, the token from Identity is not valid for the " -"operation you are attempting to perform, and your user needs a different " -"role for the operation." -msgstr "" - -#: ../networking_arch.rst:22 -msgid "" -"If your deployment uses a controller host to run centralized Compute " -"components, you can deploy the Networking server to that same host. However, " -"Networking is entirely standalone and can be deployed to a dedicated host. " -"Depending on your configuration, Networking can also include the following " -"agents:" -msgstr "" - -#: ../networking_use.rst:325 -msgid "" -"If your plug-in implements Networking security groups, you can also leverage " -"Compute security groups by setting ``security_group_api = neutron`` in the :" -"file:`nova.conf` file. After you set this option, all Compute security group " -"commands are proxied to Networking." -msgstr "" - -#: ../telemetry-measurements.rst:1188 -msgid "Ike policy was created" -msgstr "" - -#: ../telemetry-measurements.rst:1192 -msgid "Ike policy was updated" -msgstr "" - -#: ../compute-images-instances.rst:302 -msgid "Image download: how it works" -msgstr "" - -#: ../telemetry-measurements.rst:685 -msgid "Image is downlo\\ aded" -msgstr "" - -#: ../telemetry-measurements.rst:688 -msgid "Image is served out" -msgstr "" - -#: ../compute-images-instances.rst:96 -msgid "Image management" -msgstr "" - -#: ../compute-images-instances.rst:154 -msgid "Image properties and property protection" -msgstr "" - -#: ../blockstorage_image_volume_cache.rst:6 -msgid "Image-Volume cache" -msgstr "" - -#: ../compute-images-instances.rst:3 -msgid "Images and instances" -msgstr "" - -#: ../objectstorage_components.rst:189 -msgid "" -"Implementing a partition is conceptually simple, a partition is just a " -"directory sitting on a disk with a corresponding hash table of what it " -"contains." -msgstr "" - -#: ../networking_use.rst:299 -msgid "" -"Implements Networking security groups, you can configure security group " -"rules directly by using the :command:`neutron security-group-rule-create` " -"command. This example enables ``ping`` and ``ssh`` access to your VMs." -msgstr "" - -#: ../blockstorage_glusterfs_backend.rst:173 -msgid "" -"In :file:`/etc/cinder/cinder.conf`, the ``glusterfs_sparsed_volumes`` " -"configuration key determines whether volumes are created as sparse files and " -"grown as needed or fully allocated up front. The default and recommended " -"value of this key is true, which ensures volumes are initially created as " -"sparse files." -msgstr "" - -#: ../telemetry-data-retrieval.rst:390 +#: ../telemetry-events.rst:99 msgid "" -"In Liberty, the data returned corresponds to the role and user. Non-admin " -"users will only returned events that are scoped to them. Admin users will be " -"returned all events related to the project they administer as well as all " -"unscoped events." +"The basic set of traits (all are TEXT type) that will be added to all events " +"if the notification has the relevant data are: service (notification's " +"publisher), tenant\\_id, and request\\_id. These do not have to be specified " +"in the event definition, they are automatically added, but their definitions " +"can be overridden for a given event\\_type." msgstr "" -#: ../compute_arch.rst:238 -msgid "" -"In OpenStack the base operating system is usually copied from an image " -"stored in the OpenStack Image service. This is the most common case and " -"results in an ephemeral instance that starts from a known template state and " -"loses all accumulated states on virtual machine deletion. It is also " -"possible to put an operating system on a persistent volume in the OpenStack " -"Block Storage volume system. This gives a more traditional persistent system " -"that accumulates states which are preserved on the OpenStack Block Storage " -"volume across the deletion and re-creation of the virtual machine. To get a " -"list of available images on your system, run::" +#: ../telemetry-events.rst:106 +msgid "Event definitions format" msgstr "" -#: ../compute-images-instances.rst:338 +#: ../telemetry-events.rst:107 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 " -"that starts from a known template state and loses all accumulated states on " -"shutdown." +"The event definitions file is in YAML format. It consists of a list of event " +"definitions, which are mappings. Order is significant, the list of " +"definitions is scanned in reverse order to find a definition which matches " +"the notification's event\\_type. That definition will be used to generate " +"the event. The reverse ordering is done because it is common to want to have " +"a more general wildcarded definition (such as ``compute.instance.*``) with a " +"set of traits common to all of those events, with a few more specific event " +"definitions afterwards that have all of the above traits, plus a few more." msgstr "" -# #-#-#-#-# blockstorage_glusterfs_backend.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -# #-#-#-#-# blockstorage_nfs_backend.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -#: ../blockstorage_glusterfs_backend.rst:24 ../blockstorage_nfs_backend.rst:24 -msgid "" -"In Ubuntu and Debian distributions, the ``cinder`` volume service is named " -"``cinder-volume``." +#: ../telemetry-events.rst:117 +msgid "Each event definition is a mapping with two keys:" msgstr "" -#: ../compute-networking-nova.rst:238 +#: ../telemetry-events.rst:120 msgid "" -"In ``VlanManager`` networking mode, each project uses a different 64-bit " -"global routing prefix. In ``FlatDHCPManager`` mode, all instances use one 64-" -"bit global routing prefix." +"This is a list (or a string, which will be taken as a 1 element list) of " +"event\\_types this definition will handle. These can be wildcarded with unix " +"shell glob syntax. An exclusion listing (starting with a ``!``) will exclude " +"any types listed from matching. If only exclusions are listed, the " +"definition will match anything not matching the exclusions." msgstr "" -#: ../blockstorage_multi_backend.rst:15 +#: ../telemetry-events.rst:128 msgid "" -"In a multiple-storage back-end configuration, each back end has a name " -"(``volume_backend_name``). Several back ends can have the same name. In that " -"case, the scheduler properly decides which back end the volume has to be " -"created in." +"This is a mapping, the keys are the trait names, and the values are trait " +"definitions." msgstr "" -#: ../identity_user_crud.rst:27 -msgid "" -"In addition to changing their password, all current tokens for the user are " -"invalidated." +#: ../telemetry-events.rst:131 +msgid "Each trait definition is a mapping with the following keys:" msgstr "" -#: ../compute-manage-logs.rst:73 +#: ../telemetry-events.rst:134 msgid "" -"In addition to enabling syslog, these settings also turn off verbose and " -"debugging output from the log." +"A path specification for the field(s) in the notification you wish to " +"extract for this trait. Specifications can be written to match multiple " +"possible fields. By default the value will be the first such field. The " +"paths can be specified with a dot syntax (``payload.host``). Square bracket " +"syntax (``payload[host]``) is also supported. In either case, if the key for " +"the field you are looking for contains special characters, like ``.``, it " +"will need to be quoted (with double or single quotes): ``payload." +"image_meta.’org.openstack__1__architecture’``. The syntax used for the field " +"specification is a variant of `JSONPath `__" msgstr "" -#: ../telemetry-data-collection.rst:239 -msgid "" -"In addition to loading all the polling plug-ins registered in the specified " -"namespaces, the ceilometer-polling agent can also specify the polling plug-" -"ins to be loaded by using the ``pollster-list`` option::" +#: ../telemetry-events.rst:144 +msgid "fields" msgstr "" -#: ../telemetry-events.rst:5 +#: ../telemetry-events.rst:147 msgid "" -"In addition to meters, the Telemetry module collects events triggered within " -"an OpenStack environment. This section provides a brief summary of the " -"events format in the Telemetry module." +"(Optional) The data type for this trait. Valid options are: ``text``, " +"``int``, ``float``, and ``datetime``. Defaults to ``text`` if not specified." msgstr "" -#: ../telemetry.rst:21 -msgid "" -"In addition to system measurements, the Telemetry module also captures event " -"notifications triggered when various actions are executed in the OpenStack " -"system. This data is captured as Events and stored alongside metering data." +#: ../telemetry-events.rst:149 +msgid "type" msgstr "" -#: ../compute_arch.rst:140 +#: ../telemetry-events.rst:152 msgid "" -"In addition to the ephemeral root volume, all default types of flavors, " -"except ``m1.tiny``, which is the smallest one, provide an additional " -"ephemeral block device sized between 20 and 160 GB (a configurable value to " -"suit an environment). It is represented as a raw block device with no " -"partition table or file system. A cloud-aware operating system can discover, " -"format, and mount such a storage device. OpenStack Compute defines the " -"default file system for different operating systems as Ext4 for Linux " -"distributions, VFAT for non-Linux and non-Windows operating systems, and " -"NTFS for Windows. However, it is possible to specify any other filesystem " -"type by using ``virt_mkfs`` or ``default_ephemeral_format`` configuration " -"options." +"(Optional) Used to execute simple programmatic conversions on the value in a " +"notification field." msgstr "" -#: ../compute_arch.rst:195 -msgid "" -"In addition to the native compute API, OpenStack provides an EC2-compatible " -"API. This API allows EC2 legacy workflows built for EC2 to work with " -"OpenStack. For more information and configuration options about this " -"compatibility API, see the `OpenStack Configuration Reference `__." +#: ../telemetry-events.rst:152 +msgid "plugin" msgstr "" -#: ../networking_adv-features.rst:544 -msgid "" -"In addition to these network types, the NSX plug-in also supports a special " -"*l3_ext* network type, which maps external networks to specific NSX gateway " -"services as discussed in the next section." +#: ../telemetry-measurements.rst:5 +msgid "Measurements" msgstr "" -#: ../blockstorage_volume_backups_export_import.rst:42 +#: ../telemetry-measurements.rst:7 msgid "" -"In addition, having a volume backup and its backup metadata also provides " -"volume portability. Specifically, backing up a volume and exporting its " -"metadata will allow you to restore the volume on a completely different " -"Block Storage database, or even on a different cloud service. To do so, " -"first import the backup metadata to the Block Storage database and then " -"restore the backup." +"The Telemetry module collects meters within an OpenStack deployment. This " +"section provides a brief summary about meters format and origin and also " +"contains the list of available meters." msgstr "" -#: ../compute-networking-nova.rst:72 +#: ../telemetry-measurements.rst:11 msgid "" -"In any setup with flat networking, the hosts providing the ``nova-network`` " -"service are responsible for forwarding traffic from the private network. " -"They also run and configure dnsmasq as a DHCP server listening on this " -"bridge, usually on IP address 10.0.0.1 (see :ref:`compute-dnsmasq`). Compute " -"can determine the NAT entries for each network, although sometimes NAT is " -"not used, such as when the network has been configured with all public IPs, " -"or if a hardware router is used (which is a high availability option). In " -"this case, hosts need to have ``br100`` configured and physically connected " -"to any other nodes that are hosting VMs. You must set the " -"``flat_network_bridge`` option or create networks with the bridge parameter " -"in order to avoid raising an error. Compute nodes have iptables or ebtables " -"entries created for each project and instance to protect against MAC ID or " -"IP address spoofing and ARP poisoning." -msgstr "" - -#: ../compute-manage-logs.rst:64 -msgid "In each configuration file, add these lines:" +"Telemetry collects meters by polling the infrastructure elements and also by " +"consuming the notifications emitted by other OpenStack services. For more " +"information about the polling mechanism and notifications see :ref:" +"`telemetry-data-collection`. There are several meters which are collected by " +"polling and by consuming. The origin for each meter is listed in the tables " +"below." msgstr "" -#: ../telemetry-data-collection.rst:513 +#: ../telemetry-measurements.rst:20 msgid "" -"In effect, a sink describes a chain of handlers. The chain starts with zero " -"or more transformers and ends with one or more publishers. The first " -"transformer in the chain is passed data from the corresponding source, takes " -"some action such as deriving rate of change, performing unit conversion, or " -"aggregating, before passing the modified data to the next step that is " -"described in :ref:`telemetry-publishers`." +"You may need to configure Telemetry or other OpenStack services in order to " +"be able to collect all the samples you need. For further information about " +"configuration requirements see the `Telemetry chapter `__ in the " +"OpenStack Installation Guide. Also check the `Telemetry manual installation " +"`__ " +"description." msgstr "" -#: ../cross_project_cors.rst:34 -msgid "" -"In most cases, CORS support is built directly into the service itself. To " -"enable it, simply follow the configuration options exposed in the default " -"configuration file, or add it yourself according to the pattern below." +#: ../telemetry-measurements.rst:28 +msgid "Telemetry uses the following meter types:" msgstr "" -#: ../objectstorage_arch.rst:56 -msgid "" -"In most configurations, each of the five zones should have an equal amount " -"of storage capacity. Storage nodes use a reasonable amount of memory and " -"CPU. Metadata needs to be readily available to return objects quickly. The " -"object stores run services not only to field incoming requests from the " -"access tier, but to also run replicators, auditors, and reapers. You can " -"provision object stores provisioned with single gigabit or 10 gigabit " -"network interface depending on the expected workload and desired performance." +#: ../telemetry-measurements.rst:33 +msgid "Increasing over time (instance hours)" msgstr "" -#: ../blockstorage_image_volume_cache.rst:92 -msgid "" -"In normal usage there should be no need for manual intervention with the " -"cache. The entries and their backing Image-Volumes are managed automatically." +#: ../telemetry-measurements.rst:35 +msgid "Changing over time (bandwidth)" msgstr "" -#: ../telemetry-measurements.rst:794 +#: ../telemetry-measurements.rst:37 msgid "" -"In order to access Ceph from Telemetry, you need to specify a ``service " -"group`` for ``radosgw`` in the ``ceilometer.conf`` configuration file along " -"with ``access_key`` and ``secret_key`` of the ``admin`` user mentioned above." +"Discrete items (floating IPs, image uploads) and fluctuating values (disk I/" +"O)" msgstr "" -#: ../blockstorage-driver-filter-weighing.rst:240 +#: ../telemetry-measurements.rst:43 msgid "" -"In order to access these properties in a custom string use the following " -"format:" +"Telemetry provides the possibility to store metadata for samples. This " +"metadata can be extended for OpenStack Compute and OpenStack Object Storage." msgstr "" #: ../telemetry-measurements.rst:47 @@ -9034,1311 +21713,30 @@ msgid "" "command look like the following::" msgstr "" -#: ../compute-networking-nova.rst:751 +#: ../telemetry-measurements.rst:56 msgid "" -"In order to disassociate the network, you will need the ID of the project it " -"has been associated to. To get the project ID, you will need to be an " -"administrator." +"The other option is to set the ``reserved_metadata_keys`` to the list of " +"metadata keys that you would like to be included in ``resource_metadata`` of " +"the instance related samples that are collected for OpenStack Compute. This " +"option is included in the ``DEFAULT`` section of the :file:`ceilometer.conf` " +"configuration file." msgstr "" -#: ../objectstorage_components.rst:206 +#: ../telemetry-measurements.rst:62 msgid "" -"In order to ensure that there are three copies of the data everywhere, " -"replicators continuously examine each partition. For each local partition, " -"the replicator compares it against the replicated copies in the other zones " -"to see if there are any differences." +"You might also specify headers whose values will be stored along with the " +"sample data of OpenStack Object Storage. The additional information is also " +"stored under ``resource_metadata``. The format of the new field is " +"``resource_metadata.http_header_$name``, where ``$name`` is the name of the " +"header with ``-`` replaced by ``_``." msgstr "" -#: ../telemetry-measurements.rst:786 +#: ../telemetry-measurements.rst:68 msgid "" -"In order to gather meters from Ceph, you have to install and configure the " -"Ceph Object Gateway (radosgw) as it is described in the `Installation Manual " -"`__. You have to enable `usage " -"logging `__ in " -"order to get the related meters from Ceph. You will also need an ``admin`` " -"user with ``users``, ``buckets``, ``metadata`` and ``usage`` ``caps`` " -"configured." -msgstr "" - -#: ../ts_cinder_config.rst:115 -msgid "" -"In order to make this possible the iSCSI target information needs to be " -"stored in a file on creation that can be queried in case of restart of the " -"``tgt daemon``. By default, Block Storage uses a ``state_path`` variable, " -"which if installing with Yum or APT should be set to :file:`/var/lib/cinder/" -"`. The next part is the ``volumes_dir`` variable, by default this just " -"simply appends a :file:`volumes` directory to the ``state_path``. The result " -"is a file-tree :file:`/var/lib/cinder/volumes/`." -msgstr "" - -#: ../compute-networking-nova.rst:788 -msgid "" -"In order to use multinic, create two networks, and attach them to the tenant " -"(named ``project`` on the command line):" -msgstr "" - -#: ../cross_project_cors.rst:78 -msgid "" -"In other services, CORS is configured via PasteDeploy. In this case, you " -"must first make sure that OpenStack's :code:`oslo_middleware` package " -"(version 2.4.0 or later) is available in the Python environment that is " -"running the service. Then, add the following configuration block to your :" -"file:`paste.ini` file." -msgstr "" - -#: ../networking_introduction.rst:49 -msgid "" -"In particular, Networking supports each tenant having multiple private " -"networks and enables tenants to choose their own IP addressing scheme, even " -"if those IP addresses overlap with those that other tenants use." -msgstr "" - -#: ../objectstorage_replication.rst:69 -msgid "" -"In practice, database replication can process hundreds of databases per " -"concurrency setting per second (up to the number of available CPUs or disks) " -"and is bound by the number of database transactions that must be performed." -msgstr "" - -#: ../networking_introduction.rst:302 -msgid "" -"In releases earlier than Juno, OpenStack Networking prevents setting an " -"allowed address pair on a port that matches the MAC address and one of the " -"fixed IP addresses of the port." -msgstr "" - -#: ../compute-networking-nova.rst:90 -msgid "" -"In single-host Flat DHCP mode you will be able to ping VMs through their " -"fixed IP from the ``nova-network`` node, but you cannot ping them from the " -"compute nodes. This is expected behavior." -msgstr "" - -#: ../compute-node-down.rst:99 -msgid "" -"In some cases, files on your compute node can end up using the wrong UID or " -"GID. This can happen when running OpenStack Compute, using a shared file " -"system, or with an automated configuration tool. This can cause a number of " -"problems, such as inability to perform live migrations, or start virtual " -"machines." -msgstr "" - -#: ../networking_auth.rst:233 -msgid "" -"In some cases, some operations are restricted to administrators only. This " -"example shows you how to modify a policy file to permit tenants to define " -"networks, see their resources, and permit administrative users to perform " -"all other operations:" -msgstr "" - -#: ../blockstorage-boot-from-volume.rst:5 -msgid "" -"In some cases, you can store and run instances from inside volumes. For " -"information, see the `Launch an instance from a volume`_ section in the " -"`OpenStack End User Guide`_." -msgstr "" - -#: ../networking_multi-dhcp-agents.rst:208 -msgid "" -"In some deployments, one DHCP agent is not enough to hold all network data. " -"In addition, you must have a backup for it even when the deployment is " -"small. The same network can be assigned to more than one DHCP agent and one " -"DHCP agent can host more than one network." -msgstr "" - -#: ../objectstorage-monitoring.rst:18 -msgid "" -"In such a complex ecosystem, you can use multiple approaches to get the " -"answers to these questions. This section describes several approaches." -msgstr "" - -#: ../networking_config-plugins.rst:20 -msgid "" -"In the :file:`/etc/neutron/neutron.conf` file, set the ``service_plugins`` " -"option:" -msgstr "" - -#: ../compute-images-instances.rst:275 -msgid "" -"In the :file:`glance-api.conf` file, define the location of a property " -"protections configuration file::" -msgstr "" - -#: ../dashboard_sessions.rst:116 -msgid "" -"In the :file:`local_settings` file (on Fedora/RHEL/CentOS: :file:`/etc/" -"openstack-dashboard/local_settings`, on Ubuntu/Debian: :file:`/etc/openstack-" -"dashboard/local_settings.py`, and on openSUSE: :file:`/srv/www/openstack-" -"dashboard/openstack_dashboard/local/local_settings.py`), change these " -"options::" -msgstr "" - -#: ../telemetry-troubleshooting-guide.rst:55 -msgid "" -"In the Icehouse release of OpenStack a new service was introduced to be " -"responsible for consuming notifications that are coming from other OpenStack " -"services." -msgstr "" - -#: ../keystone_secure_identity_to_ldap_backend.rst:18 -msgid "" -"In the ``[ldap]`` section, set the ``use_tls`` configuration key to " -"``True``. Doing so will enable TLS." -msgstr "" - -#: ../compute-manage-logs.rst:154 -msgid "" -"In the ``[serial_console]`` section, configure the serial console proxy " -"similar to graphical console proxies:" -msgstr "" - -#: ../compute-manage-logs.rst:146 -msgid "In the ``[serial_console]`` section, enable the serial console:" -msgstr "" - -#: ../telemetry-data-collection.rst:890 -msgid "" -"In the above example, the ``name`` field is a json path with matching a list " -"of meter names defined in the notification message." -msgstr "" - -#: ../objectstorage_account_reaper.rst:5 -msgid "" -"In the background, the account reaper removes data from the deleted accounts." -msgstr "" - -#: ../blockstorage_over_subscription.rst:103 -msgid "" -"In the capacity filter, ``max_over_subscription_ratio`` is used when " -"choosing a back end if ``thin_provisioning_support`` is True and " -"``max_over_subscription_ratio`` is greater than 1.0." -msgstr "" - -#: ../blockstorage_over_subscription.rst:110 -msgid "" -"In the capacity weigher, virtual free capacity is used for ranking if " -"``thin_provisioning_support`` is True. Otherwise, real free capacity will be " -"used as before." -msgstr "" - -#: ../telemetry-data-collection.rst:660 -msgid "" -"In the case of the transformer that creates the ``cpu_util`` meter, the " -"definition looks like the following::" -msgstr "" - -#: ../objectstorage-troubleshoot.rst:13 -msgid "" -"In the event that a drive has failed, the first step is to make sure the " -"drive is unmounted. This will make it easier for Object Storage to work " -"around the failure until it has been resolved. If the drive is going to be " -"replaced immediately, then it is just best to replace the drive, format it, " -"remount it, and let replication fill it up." -msgstr "" - -#: ../compute-networking-nova.rst:938 -msgid "" -"In the first terminal, on the host running ``nova-network``, use ``tcpdump`` " -"on the VLAN interface to monitor DNS-related traffic (UDP, port 53). As " -"root, run:" -msgstr "" - -#: ../compute-networking-nova.rst:946 -msgid "" -"In the second terminal, also on the host running ``nova-network``, use " -"``tcpdump`` to monitor DNS-related traffic on the bridge interface. As root, " -"run:" -msgstr "" - -#: ../compute-networking-nova.rst:954 -msgid "" -"In the third terminal, use ``SSH`` to access the instance and generate DNS " -"requests by using the :command:`nslookup` command:" -msgstr "" - -#: ../compute-networking-nova.rst:647 -msgid "In these examples, IP forwarding is disabled." -msgstr "" - -#: ../telemetry-alarms.rst:238 -msgid "" -"In this case, the state is reported as ``insufficient data`` which could " -"indicate that:" -msgstr "" - -#: ../blockstorage_multi_backend.rst:74 -msgid "" -"In this configuration, ``lvmdriver-1`` and ``lvmdriver-2`` have the same " -"``volume_backend_name``. If a volume creation requests the ``LVM`` back end " -"name, the scheduler uses the capacity filter scheduler to choose the most " -"suitable driver, which is either ``lvmdriver-1`` or ``lvmdriver-2``. The " -"capacity filter scheduler is enabled by default. The next section provides " -"more information. In addition, this example presents a ``lvmdriver-3`` back " -"end." -msgstr "" - -#: ../compute-live-migration-usage.rst:209 -msgid "" -"In this example, SERVER can be the ID or name of the instance. Another " -"example:" -msgstr "" - -#: ../compute-configuring-migrations.rst:123 -msgid "" -"In this example, ``HostA`` is the NFSv4 server that exports ``NOVA-INST-DIR/" -"instances`` directory. ``HostB`` and ``HostC`` are NFSv4 clients that mount " -"``HostA``." -msgstr "" - -#: ../database.rst:186 -msgid "" -"In this example, the guest image already contains all the required packages, " -"so leave this argument empty." -msgstr "" - -#: ../compute-flavors.rst:134 -msgid "" -"In this example, the instance of ``m1.low_cpu`` can only consume a maximum " -"of 50% CPU of a physical CPU computing capability." -msgstr "" - -#: ../database.rst:69 -msgid "" -"In this example, you use the glance :command:`image-create` command to " -"register a ``mysql-5.5.qcow2`` image::" -msgstr "" - -# #-#-#-#-# compute-security.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -# #-#-#-#-# database.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -#: ../compute-security.rst:76 ../database.rst:108 ../database.rst:146 -msgid "In this example:" -msgstr "" - -#: ../compute-networking-nova.rst:53 -msgid "" -"In this mode, OpenStack starts a DHCP server (dnsmasq) to allocate IP " -"addresses to VM instances from the specified subnet, in addition to manually " -"configuring the networking bridge. IP addresses for VM instances are " -"assigned from a subnet specified by the network administrator." -msgstr "" - -#: ../compute-networking-nova.rst:36 -msgid "" -"In this mode, a network administrator specifies a subnet. IP addresses for " -"VM instances are assigned from the subnet, and then injected into the image " -"on launch. Each instance receives a fixed IP address from the pool of " -"available addresses. A system administrator must create the Linux networking " -"bridge (typically named ``br100``, although this is configurable) on the " -"systems running the ``nova-network`` service. All instances of the system " -"are attached to the same bridge, which is configured manually by the network " -"administrator." -msgstr "" - -#: ../networking_multi-dhcp-agents.rst:273 -msgid "" -"In this output, ``heartbeat_timestamp`` is the time on the neutron server. " -"You do not need to synchronize all agents to this time for this extension to " -"run correctly. ``configurations`` describes the static configuration for the " -"agent or run time data. This agent is a DHCP agent and it hosts one network, " -"one subnet, and three ports." -msgstr "" - -#: ../compute-networking-nova.rst:582 -msgid "" -"In this section, the term floating IP address is used to refer to an IP " -"address, usually public, that you can dynamically add to a running virtual " -"instance." -msgstr "" - -#: ../compute-live-migration-usage.rst:198 -msgid "" -"In this table, the first row shows the total amount of resources available " -"on the physical server. The second line shows the currently used resources. " -"The third line shows the maximum used resources. The fourth line and below " -"shows the resources available for each project." -msgstr "" - -#: ../compute-flavors.rst:200 -msgid "Inbound traffic:" -msgstr "" - -#: ../compute-root-wrap-reference.rst:72 -msgid "" -"Including this workaround in your configuration file safeguards your " -"environment from issues that can impair root wrapper performance. Tool " -"changes that have impacted `Python Build Reasonableness (PBR) `__ for example, are a known issue " -"that affects root wrapper performance." -msgstr "" - -#: ../compute-flavors.rst:174 -msgid "" -"Incoming and outgoing traffic can be shaped independently. The bandwidth " -"element can have at most, one inbound and at most, one outbound child " -"element. If you leave any of these child elements out, no quality of service " -"(QoS) is applied on that traffic direction. So, if you want to shape only " -"the network's incoming traffic, use inbound only (and vice versa). Each " -"element has one mandatory attribute average, which specifies the average bit " -"rate on the interface being shaped." -msgstr "" - -#: ../blockstorage-api-throughput.rst:3 -msgid "Increase Block Storage API service throughput" -msgstr "" - -#: ../telemetry-measurements.rst:33 -msgid "Increasing over time (instance hours)" -msgstr "" - -#: ../identity_service_api_protection.rst:32 -msgid "" -"Indicates that to create a user, you must have the admin role in your token. " -"The :code:`domain_id` in your token must match the :code:`domain_id` in the " -"user object that you are trying to create, which implies this must be a " -"domain-scoped token. In other words, you must have the admin role on the " -"domain in which you are creating the user, and the token that you use must " -"be scoped to that domain." -msgstr "" - -#: ../identity_concepts.rst:122 -msgid "" -"Individual services, such as Compute and the Image service, assign meaning " -"to roles. In the Identity service, a role is simply a name." -msgstr "" - -#: ../networking_introduction.rst:136 -msgid "" -"Ingress traffic can be shaped with *connection limits*. This feature allows " -"workload control, and can also assist with mitigating DoS (Denial of " -"Service) attacks." -msgstr "" - -#: ../dashboard_sessions.rst:89 -msgid "Initialize and configure the database" -msgstr "" - -#: ../telemetry-system-architecture.rst:51 -msgid "" -"Initiates alarm actions, for example calling out to a webhook with a " -"description of the alarm state transition." -msgstr "" - -#: ../compute-admin-password-injection.rst:5 -msgid "Injecting the administrator password" -msgstr "" - -#: ../telemetry-measurements.rst:541 -msgid "Inlet temperatu\\ re of the system" -msgstr "" - -#: ../networking_adv-features.rst:692 -msgid "Input type" -msgstr "" - -#: ../keystone_certificates_for_pki.rst:124 -msgid "Install External Signing Certificate" -msgstr "" - -#: ../keystone_certificates_for_pki.rst:170 -msgid "Install an external signing certificate" -msgstr "" - -#: ../networking_config-plugins.rst:50 -msgid "" -"Install the Brocade-modified Python netconf client (ncclient) library, which " -"is available at https://github.com/brocade/ncclient:" -msgstr "" - -#: ../networking_config-agents.rst:67 -msgid "Install the DHCP agent:" -msgstr "" - -#: ../networking_config-plugins.rst:101 -msgid "Install the NSX plug-in:" -msgstr "" - -#: ../networking_config-agents.rst:435 -msgid "Install the OpenStack Networking Hyper-V Agent:" -msgstr "" - -#: ../networking_config-agents.rst:276 -msgid "Install the agent by running:" -msgstr "" - -#: ../networking_config-agents.rst:329 -msgid "Install the agent:" -msgstr "" - -#: ../networking_config-agents.rst:193 -msgid "Install the neutron-l3-agent binary on the network node:" -msgstr "" - -#: ../compute-images-instances.rst:336 -msgid "Instance building blocks" -msgstr "" - -#: ../compute-images-instances.rst:406 -msgid "Instance management tools" -msgstr "" - -#: ../compute-node-down.rst:238 -msgid "" -"Instance state at this stage depends on whether you added an `/etc/fstab` " -"entry for that volume. Images built with the cloud-init package remain in a " -"``pending`` state, while others skip the missing volume and start. This step " -"is performed in order to ask Compute to reboot every instance, so that the " -"stored state is preserved. It does not matter if not all instances come up " -"successfully. For more information about cloud-init, see `help.ubuntu.com/" -"community/CloudInit/ `__." -msgstr "" - -#: ../compute-networking-nova.rst:393 -msgid "" -"Instances also retrieve user data (passed as the ``user_data`` parameter in " -"the API call or by the ``--user_data`` flag in the :command:`nova boot` " -"command) through the metadata service, by making a GET request to " -"``http://169.254.169.254/openstack/2012-08-10/user_data``:" -msgstr "" - -#: ../compute-node-down.rst:195 -msgid "Instances are no longer running." -msgstr "" - -#: ../compute-images-instances.rst:9 -msgid "" -"Instances are the individual virtual machines that run on physical compute " -"nodes. Users can launch any number of instances from the same image. Each " -"launched instance runs from a copy of the base image so that any changes " -"made to the instance do not affect the base image. You can take snapshots of " -"running instances to create an image based on the current disk state of a " -"particular instance. The Compute service manages instances." -msgstr "" - -#: ../compute-networking-nova.rst:451 -msgid "" -"Instances can retrieve the public SSH key (identified by keypair name when a " -"user requests a new instance) by making a GET request to " -"``http://169.254.169.254/2009-04-04/meta-data/public-keys/0/openssh-key``:" -msgstr "" - -#: ../compute-networking-nova.rst:463 -msgid "" -"Instances can retrieve user data by making a GET request to " -"``http://169.254.169.254/2009-04-04/user-data``:" -msgstr "" - -#: ../compute-node-down.rst:264 -msgid "" -"Instances that were stopped at the plymouth stage will now automatically " -"continue booting and start normally. Instances that previously started " -"successfully will now be able to see the volume." -msgstr "" - -#: ../networking_adv-features.rst:151 -msgid "Integer" -msgstr "" - -#: ../networking_adv-features.rst:622 -msgid "Integer. Must not exceed ``min_sync_req_delay``" -msgstr "" - -#: ../networking_adv-features.rst:629 -msgid "Integer. Must not exceed ``state_sync_interval``." -msgstr "" - -#: ../networking_adv-features.rst:613 ../networking_adv-features.rst:636 -msgid "Integer; no constraint." -msgstr "" - -#: ../keystone_integrate_identity_backend_ldap.rst:5 -msgid "Integrate Identity back end with LDAP" -msgstr "" - -#: ../keystone_integrate_with_ldap.rst:5 -msgid "Integrate Identity with LDAP" -msgstr "" - -#: ../keystone_integrate_assignment_backend_ldap.rst:5 -msgid "Integrate assignment back end with LDAP" -msgstr "" - -#: ../objectstorage_features.rst:61 -msgid "Integration with Compute" -msgstr "" - -#: ../networking_adv-features.rst:614 -msgid "" -"Interval in seconds between two run of the synchronization task. If the " -"synchronization task takes more than ``state_sync_interval`` seconds to " -"execute, a new instance of the task is started as soon as the other is " -"completed. Setting the value for this option to 0 will disable the " -"synchronization task." -msgstr "" - -# #-#-#-#-# baremetal.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -# #-#-#-#-# database.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -# #-#-#-#-# orchestration-introduction.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -#: ../baremetal.rst:13 ../database.rst:13 ../orchestration-introduction.rst:3 -msgid "Introduction" -msgstr "" - -#: ../networking_introduction.rst:3 -msgid "Introduction to Networking" -msgstr "" - -#: ../objectstorage_intro.rst:3 -msgid "Introduction to Object Storage" -msgstr "" - -#: ../compute-flavors.rst:65 -msgid "Is_Public" -msgstr "" - -#: ../ts_cinder_config.rst:108 -msgid "Issues with ``state_path`` and ``volumes_dir`` settings." -msgstr "" - -#: ../telemetry-data-retrieval.rst:512 -msgid "" -"It can be specified in the form of ``file://path?" -"option1=value1&option2=value2``. This publisher records metering data into a " -"file." -msgstr "" - -#: ../telemetry-data-retrieval.rst:495 -msgid "" -"It can be specified in the form of ``notifier://?" -"option1=value1&option2=value2``. It emits data over AMQP using oslo." -"messaging. This is the recommended method of publishing." -msgstr "" - -#: ../telemetry-data-retrieval.rst:501 -msgid "" -"It can be specified in the form of ``rpc://?option1=value1&option2=value2``. " -"It emits metering data over lossy AMQP. This method is synchronous and may " -"experience performance issues. This publisher is deprecated in Liberty in " -"favour of the notifier publisher." -msgstr "" - -#: ../telemetry-data-retrieval.rst:508 -msgid "" -"It can be specified in the form of ``udp://:/``. It emits " -"metering data for over UDP." -msgstr "" - -#: ../telemetry-data-retrieval.rst:523 -msgid "" -"It can be specified in the form of: ``kafka://kafka_broker_ip: " -"kafka_broker_port?topic=kafka_topic &option1=value1``." -msgstr "" - -#: ../objectstorage-troubleshoot.rst:51 -msgid "" -"It has been our experience that when a drive is about to fail, error " -"messages appear in :file:`/var/log/kern.log`. There is a script called " -"``swift-drive-audit`` that can be run via cron to watch for bad drives. If " -"errors are detected, it will unmount the bad drive, so that Object Storage " -"can work around it. The script takes a configuration file with the following " -"settings:" -msgstr "" - -#: ../telemetry-events.rst:24 -msgid "" -"It is advisable to set ``disable_non_metric_meters`` to ``True`` when " -"enabling events in the Telemetry module. The Telemetry module historically " -"represented events as metering data, which may create duplication of data if " -"both events and non-metric meters are enabled." -msgstr "" - -#: ../networking_multi-dhcp-agents.rst:336 -msgid "" -"It is allocated to DHCP agent on HostA. If you want to validate the behavior " -"through the :command:`dnsmasq` command, you must create a subnet for the " -"network because the DHCP agent starts the dnsmasq service only if there is a " -"DHCP." -msgstr "" - -#: ../networking_config-agents.rst:32 -msgid "" -"It is critical that you run an Open vSwitch version that is compatible with " -"the current version of the NSX Controller software. Do not use the Open " -"vSwitch version that is installed by default on Ubuntu. Instead, use the " -"Open vSwitch version that is provided on the VMware support portal for your " -"NSX Controller version." -msgstr "" - -#: ../telemetry-data-retrieval.rst:12 -msgid "" -"It is highly recommended not to access directly the database and read or " -"modify any data in it. The API layer hides all the changes in the actual " -"database schema and provides a standard interface to expose the samples, " -"alarms and so forth." -msgstr "" - -#: ../objectstorage_account_reaper.rst:23 -msgid "" -"It is on the development to-do list to write a utility that performs this " -"task, preferably through a REST call." -msgstr "" - -#: ../compute-images-instances.rst:316 -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 " -"nodes. Configure the ``my_block_storage_ip`` option in the storage node " -"configuration to allow block storage traffic to reach the Compute node." -msgstr "" - -#: ../telemetry-data-collection.rst:195 -msgid "" -"It is recommended that these notifications be consumed as events rather than " -"samples to better index the appropriate values and avoid massive load on the " -"Metering database. If preferred, Telemetry can consume these events as " -"samples if the services are configured to emit ``http.*`` notifications." -msgstr "" - -#: ../telemetry-data-retrieval.rst:545 -msgid "" -"It is used for configuring the behavior for the case, when the publisher " -"fails to send the samples, where the possible predefined values are the " -"following:" -msgstr "" - -#: ../objectstorage_auditors.rst:16 -msgid "" -"It is useful to run the object auditor on a specific device or set of " -"devices. You can run the object-auditor once as follows::" -msgstr "" - -#: ../blockstorage-driver-filter-weighing.rst:63 -msgid "" -"It is useful to use the other filters and weighers available in OpenStack in " -"combination with these custom ones. For example, the ``CapacityFilter`` and " -"``CapacityWeigher`` can be combined with these." -msgstr "" - -#: ../objectstorage_characteristics.rst:29 -msgid "" -"It runs on industry-standard hardware, such as Dell, HP, and Supermicro." -msgstr "" - -#: ../networking_config-identity.rst:207 ../networking_config-identity.rst:232 -msgid "Item" -msgstr "" - -#: ../telemetry-data-collection.rst:300 -msgid "" -"Just like the central agent, this component also does not need a direct " -"database connection. The samples are sent via AMQP to the collector." -msgstr "" - -#: ../telemetry-data-collection.rst:409 -msgid "" -"Just like the central agent, this component also does not need direct " -"database access. The samples are sent via AMQP to the collector." -msgstr "" - -#: ../telemetry-measurements.rst:602 ../telemetry-measurements.rst:605 -#: ../telemetry-measurements.rst:608 ../telemetry-measurements.rst:611 -#: ../telemetry-measurements.rst:614 ../telemetry-measurements.rst:617 -#: ../telemetry-measurements.rst:620 ../telemetry-measurements.rst:623 -msgid "KB" -msgstr "" - -#: ../compute-configuring-migrations.rst:51 -msgid "KVM-Libvirt" -msgstr "" - -#: ../compute-networking-nova.rst:987 -msgid "KVM: Network connectivity works initially, then fails" -msgstr "" - -#: ../networking_config-identity.rst:176 -msgid "Keep the default ``keystone`` value for all production deployments." -msgstr "" - -#: ../telemetry-measurements.rst:1298 -msgid "Key Value Store module" -msgstr "" - -#: ../compute-flavors.rst:68 -msgid "" -"Key and value pairs that define on which compute nodes a fla\\ vor can run. " -"These pairs must match corresponding pairs on t\\ he compute nodes. Use to " -"implement special resources, such a\\ s flavors that run on only compute " -"nodes with GPU hardware." -msgstr "" - -#: ../orchestration-auth-model.rst:54 -msgid "Keystone trusts authorization" -msgstr "" - -#: ../objectstorage_features.rst:48 -msgid "Know what users are requesting." -msgstr "" - -#: ../networking_adv-features.rst:759 -msgid "L3 metering" -msgstr "" - -#: ../networking_adv-config.rst:11 -msgid "L3 metering agent" -msgstr "" - -#: ../networking_adv-config.rst:59 -msgid "L3 metering driver" -msgstr "" - -#: ../networking_adv-config.rst:70 -msgid "L3 metering service driver" -msgstr "" - -#: ../networking_adv-features.rst:171 -msgid "L3 routing and NAT" -msgstr "" - -#: ../telemetry-measurements.rst:1105 -msgid "LB VIP was crea\\ ted" -msgstr "" - -#: ../telemetry-measurements.rst:1109 -msgid "LB VIP was upda\\ ted" -msgstr "" - -#: ../telemetry-measurements.rst:1121 -msgid "LB health probe was created" -msgstr "" - -#: ../telemetry-measurements.rst:1126 -msgid "LB health probe was updated" -msgstr "" - -#: ../telemetry-measurements.rst:1113 -msgid "LB member was c\\ reated" -msgstr "" - -#: ../telemetry-measurements.rst:1117 -msgid "LB member was u\\ pdated" -msgstr "" - -#: ../telemetry-measurements.rst:1097 -msgid "LB pool was cre\\ ated" -msgstr "" - -#: ../telemetry-measurements.rst:1101 -msgid "LB pool was upd\\ ated" -msgstr "" - -#: ../networking_introduction.rst:129 -msgid "" -"LBaaS is managed using a variety of tool sets. The REST API is available for " -"programmatic administration and scripting. Users perform administrative " -"management of load balancers through either the CLI (``neutron``) or the " -"OpenStack dashboard." -msgstr "" - -#: ../networking_introduction.rst:124 -msgid "" -"LBaaS provides availability monitoring with the ``ping``, TCP, HTTP and " -"HTTPS GET methods. Monitors are implemented to determine whether pool " -"members are available to handle requests." -msgstr "" - -#: ../networking_introduction.rst:141 -msgid "" -"LBaaS supports session persistence by ensuring incoming requests are routed " -"to the same instance within a pool of multiple instances. LBaaS supports " -"routing decisions based on cookies and source IP address." -msgstr "" - -#: ../objectstorage_features.rst:16 -msgid "" -"Large and flat namespace, highly scalable read/write access, able to serve " -"content directly from storage system." -msgstr "" - -#: ../objectstorage_arch.rst:7 -msgid "" -"Large-scale deployments segment off an access tier, which is considered the " -"Object Storage system's central hub. The access tier fields the incoming API " -"requests from clients and moves data in and out of the system. This tier " -"consists of front-end load balancers, ssl-terminators, and authentication " -"services. It runs the (distributed) brain of the Object Storage system: the " -"proxy server processes." -msgstr "" - -#: ../networking_adv-features.rst:473 -msgid "" -"Lastly, if you want to set a specific baseline QoS policy for the amount of " -"bandwidth a single port can use (unless a network queue is specified with " -"the network a port is created on) a default queue can be created in " -"Networking which then causes ports created to be associated with a queue of " -"that size times the rxtx scaling factor. Note that after a network or " -"default queue is specified, queues are added to ports that are subsequently " -"created but are not added to existing ports." -msgstr "" - -#: ../blockstorage_backup_disks.rst:222 -msgid "Launch this script from the server that runs the Block Storage service." -msgstr "" - -#: ../networking.rst:7 -msgid "" -"Learn OpenStack Networking concepts, architecture, and basic and advanced " -"``neutron`` and ``nova`` command-line interface (CLI) commands." -msgstr "" - -#: ../networking_introduction.rst:119 -msgid "Least connections" -msgstr "" - -#: ../objectstorage_features.rst:11 -msgid "Leverages commodity hardware" -msgstr "" - -#: ../telemetry-measurements.rst:296 ../telemetry-measurements.rst:314 -#: ../telemetry-measurements.rst:318 ../telemetry-measurements.rst:324 -#: ../telemetry-measurements.rst:329 ../telemetry-measurements.rst:334 -#: ../telemetry-measurements.rst:340 -msgid "Libvirt" -msgstr "" - -#: ../blockstorage-manage-volumes.rst:36 -msgid "" -"Libvirt uses that local storage as storage for the instance. The instance " -"gets a new disk (usually a :file:`/dev/vdX` disk)." -msgstr "" - -#: ../telemetry-measurements.rst:109 ../telemetry-measurements.rst:119 -#: ../telemetry-measurements.rst:126 ../telemetry-measurements.rst:130 -#: ../telemetry-measurements.rst:137 ../telemetry-measurements.rst:144 -#: ../telemetry-measurements.rst:151 ../telemetry-measurements.rst:158 -#: ../telemetry-measurements.rst:161 ../telemetry-measurements.rst:164 -#: ../telemetry-measurements.rst:172 ../telemetry-measurements.rst:180 -#: ../telemetry-measurements.rst:189 ../telemetry-measurements.rst:232 -#: ../telemetry-measurements.rst:241 ../telemetry-measurements.rst:250 -#: ../telemetry-measurements.rst:259 ../telemetry-measurements.rst:355 -msgid "Libvirt, Hyper-V" -msgstr "" - -#: ../telemetry-measurements.rst:101 ../telemetry-measurements.rst:105 -#: ../telemetry-measurements.rst:122 ../telemetry-measurements.rst:133 -#: ../telemetry-measurements.rst:140 ../telemetry-measurements.rst:147 -#: ../telemetry-measurements.rst:154 ../telemetry-measurements.rst:168 -#: ../telemetry-measurements.rst:176 ../telemetry-measurements.rst:184 -#: ../telemetry-measurements.rst:193 ../telemetry-measurements.rst:236 -#: ../telemetry-measurements.rst:245 ../telemetry-measurements.rst:254 -#: ../telemetry-measurements.rst:263 -msgid "Libvirt, Hyper-V, vSphere" -msgstr "" - -#: ../telemetry-measurements.rst:200 ../telemetry-measurements.rst:205 -#: ../telemetry-measurements.rst:216 ../telemetry-measurements.rst:221 -#: ../telemetry-measurements.rst:226 ../telemetry-measurements.rst:268 -#: ../telemetry-measurements.rst:273 ../telemetry-measurements.rst:278 -#: ../telemetry-measurements.rst:283 ../telemetry-measurements.rst:290 -#: ../telemetry-measurements.rst:348 -msgid "Libvirt, Hyper-V, vSphere, XenAPI" -msgstr "" - -#: ../compute-networking-nova.rst:59 -msgid "" -"Like flat mode, all instances are attached to a single bridge on the compute " -"node. Additionally, a DHCP server configures instances depending on single-/" -"multi-host mode, alongside each ``nova-network``. In this mode, Compute does " -"a bit more configuration. It attempts to bridge into an Ethernet device " -"(``flat_interface``, eth0 by default). For every instance, Compute allocates " -"a fixed IP address and configures dnsmasq with the MAC ID and IP address for " -"the VM. dnsmasq does not take part in the IP address allocation process, it " -"only hands out IPs according to the mapping done by Compute. Instances " -"receive their fixed IPs with the :command:`dhcpdiscover` command. These IPs " -"are not assigned to any of the host's network interfaces, only to the guest-" -"side interface for the VM." -msgstr "" - -#: ../identity_service_api_protection.rst:5 -msgid "" -"Like most OpenStack projects, Identity supports the protection of its APIs " -"by defining policy rules based on an RBAC approach. Identity stores a " -"reference to a policy JSON file in the main Identity configuration file, :" -"file:`keystone.conf`. Typically this file is named ``policy.json``, and " -"contains the rules for which roles have access to certain actions in defined " -"services." -msgstr "" - -#: ../objectstorage_features.rst:52 -msgid "Limit access to control usage by user." -msgstr "" - -#: ../networking_multi-dhcp-agents.rst:213 -msgid "List DHCP agents that host a specified network:" -msgstr "" - -#: ../networking_multi-dhcp-agents.rst:186 -msgid "List all agents:" -msgstr "" - -#: ../networking_config-agents.rst:494 -msgid "List all available agents." -msgstr "" - -#: ../compute-manage-volumes.rst:32 -msgid "List all the snapshots." -msgstr "" - -#: ../compute-manage-volumes.rst:24 -msgid "List all the volumes." -msgstr "" - -#: ../blockstorage-consistency-groups.rst:86 -msgid "List consistency group snapshots." -msgstr "" - -#: ../blockstorage-consistency-groups.rst:77 -msgid "List consistency groups." -msgstr "" - -#: ../identity_concepts.rst:351 -msgid "List group members" -msgstr "" - -#: ../identity_concepts.rst:353 -msgid "List groups for a user" -msgstr "" - -#: ../identity_service_api_protection.rst:80 -msgid "List of object attributes:" -msgstr "" - -#: ../networking_multi-dhcp-agents.rst:206 -msgid "List the DHCP agents that host a specified network:" -msgstr "" - -#: ../blockstorage_volume_number_weigher.rst:75 -msgid "List the available volumes::" -msgstr "" - -#: ../keystone_integrate_identity_backend_ldap.rst:100 -msgid "" -"List the domains using the dashboard, or the OpenStackClient CLI. Refer to " -"the `Command List `__ for a list of OpenStackClient commands." -msgstr "" - -#: ../compute-networking-nova.rst:701 -msgid "List the floating IP addresses in the pool:" -msgstr "" - -#: ../networking_multi-dhcp-agents.rst:225 -msgid "List the networks hosted by a given DHCP agent:" -msgstr "" - -#: ../networking_adv-features.rst:505 -msgid "Lists QoS queues." -msgstr "" - -#: ../networking_adv-features.rst:213 -msgid "Lists external networks." -msgstr "" - -#: ../networking_adv-features.rst:276 -msgid "Lists floating IPs" -msgstr "" - -#: ../networking_adv-features.rst:816 -msgid "Lists metering all label rules." -msgstr "" - -#: ../networking_adv-features.rst:789 -msgid "Lists metering labels." -msgstr "" - -#: ../networking_use.rst:64 -msgid "" -"Lists ports for a specified tenant and displays the ``id``, ``fixed_ips``, " -"and ``device_owner`` columns." -msgstr "" - -#: ../networking_use.rst:59 -msgid "Lists ports for a specified tenant." -msgstr "" - -#: ../networking_adv-features.rst:241 -msgid "Lists routers." -msgstr "" - -#: ../networking_adv-features.rst:371 -msgid "Lists security group rules." -msgstr "" - -#: ../networking_adv-features.rst:362 -msgid "Lists security groups." -msgstr "" - -#: ../networking_adv-features.rst:828 -msgid "Lists the value of created metering label rules." -msgstr "" - -#: ../objectstorage-troubleshoot.rst:112 -msgid "Load the ring and a new ringbuilder object in a Python REPL:" -msgstr "" - -#: ../telemetry-measurements.rst:1055 -msgid "Load-Balancer-as-a-Service (LBaaS)" -msgstr "" - -#: ../networking_introduction.rst:104 -msgid "" -"Load-Balancer-as-a-Service (LBaaS) enables Networking to distribute incoming " -"requests evenly among designated instances. This distribution ensures that " -"the workload is shared predictably among instances and enables more " -"effective use of system resources. Use one of these load balancing methods " -"to distribute incoming requests:" -msgstr "" - -#: ../telemetry-system-architecture.rst:154 -msgid "Load-Balancer-as-a-Service (LBaaS) meters" -msgstr "" - -#: ../networking_introduction.rst:102 -msgid "Load-Balancer-as-a-Service (LBaaS) overview" -msgstr "" - -#: ../compute-networking-nova.rst:1004 -msgid "Loading the module has no effect on running instances." -msgstr "" - -#: ../dashboard_sessions.rst:21 -msgid "Local memory cache" -msgstr "" - -#: ../dashboard_sessions.rst:22 -msgid "" -"Local memory storage is the quickest and easiest session back end to set up, " -"as it has no external dependencies whatsoever. It has the following " -"significant drawbacks:" -msgstr "" - -#: ../database.rst:234 -msgid "Location of :file:`validation-rules.json`" -msgstr "" - -#: ../keystone_certificates_for_pki.rst:41 -msgid "" -"Location of certificate for the authority that issued the above certificate. " -"Default is :file:`/etc/keystone/ssl/certs/ca.pem`." -msgstr "" - -#: ../keystone_certificates_for_pki.rst:33 -msgid "" -"Location of certificate used to verify tokens. Default is :file:`/etc/" -"keystone/ssl/certs/signing_cert.pem`." -msgstr "" - -#: ../keystone_certificates_for_pki.rst:37 -msgid "" -"Location of private key used to sign tokens. Default is :file:`/etc/keystone/" -"ssl/private/signing_key.pem`." -msgstr "" - -#: ../objectstorage-troubleshoot.rst:72 -msgid "" -"Location of the log file with globbing pattern to check against device " -"errors locate device blocks with errors in the log file" -msgstr "" - -#: ../keystone_certificates_for_pki.rst:46 -msgid "" -"Location of the private key used by the CA. Default is :file:`/etc/keystone/" -"ssl/private/cakey.pem`." -msgstr "" - -#: ../objectstorage-troubleshoot.rst:68 -msgid "Location where syslog sends the logs to" -msgstr "" - -#: ../networking_use.rst:15 -msgid "Log files are in the :file:`/var/log/neutron` directory." -msgstr "" - -#: ../blockstorage_glusterfs_backend.rst:45 -msgid "Log in as ``root`` to the GlusterFS server." -msgstr "" - -#: ../blockstorage_glusterfs_backend.rst:85 -msgid "Log in as ``root`` to the system hosting the Block Storage service." -msgstr "" - -#: ../blockstorage_nfs_backend.rst:29 -msgid "Log in as ``root`` to the system hosting the ``cinder`` volume service." -msgstr "" - -#: ../networking_multi-dhcp-agents.rst:438 -msgid "" -"Log in to the ``myserver4`` VM, and run ``udhcpc``, ``dhclient`` or other " -"DHCP client." -msgstr "" - -#: ../compute-node-down.rst:268 -msgid "Log in to the instances with SSH and reboot them." -msgstr "" - -#: ../compute-default-ports.rst:16 -msgid "Log in to the server that hosts the Compute service, as root." -msgstr "" - -# #-#-#-#-# compute-manage-logs.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -# #-#-#-#-# identity_logging.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -#: ../compute-manage-logs.rst:5 ../identity_logging.rst:3 -msgid "Logging" -msgstr "" - -#: ../networking_adv-operational-features.rst:74 -msgid "Logging and RPC" -msgstr "" - -#: ../compute-manage-logs.rst:10 -msgid "" -"Logging behavior can be changed by creating a configuration file. To specify " -"the configuration file, add this line to the :file:`/etc/nova/nova.conf` " -"file:" -msgstr "" - -#: ../telemetry-troubleshooting-guide.rst:5 -msgid "Logging in Telemetry" -msgstr "" - -#: ../objectstorage-troubleshoot.rst:75 -msgid "Logging level" -msgstr "" - -#: ../compute-manage-logs.rst:8 -msgid "Logging module" -msgstr "" - -#: ../networking_adv-operational-features.rst:6 -msgid "Logging settings" -msgstr "" - -#: ../telemetry-measurements.rst:1027 -msgid "Lookup packets for table" -msgstr "" - -#: ../telemetry-measurements.rst:109 ../telemetry-measurements.rst:113 -#: ../telemetry-measurements.rst:210 ../telemetry-measurements.rst:290 -#: ../telemetry-measurements.rst:296 -msgid "MB" -msgstr "" - -#: ../telemetry-measurements.rst:434 -msgid "MHz" -msgstr "" - -#: ../telemetry-events.rst:51 -msgid "" -"Mainly for auditing purpose, the full event message can be stored " -"(unindexed) for future evaluation." -msgstr "" - -#: ../networking_multi-dhcp-agents.rst:421 -msgid "Make sure both DHCP agents hosting 'net2':" -msgstr "" - -#: ../keystone_certificates_for_pki.rst:195 -msgid "Make sure the certificate directory is only accessible by root." -msgstr "" - -#: ../compute-node-down.rst:112 -msgid "" -"Make sure you choose UIDs or GIDs that are not in use for other users or " -"groups." -msgstr "" - -#: ../compute-networking-nova.rst:810 -msgid "" -"Make sure you start the second interface on the instance, or it won't be " -"reachable through the second IP." -msgstr "" - -#: ../compute-configuring-migrations.rst:381 -msgid "Make the first compute node part of that aggregate" -msgstr "" - -#: ../orchestration-stack-domain-users.rst:89 -msgid "Make the user a domain admin::" -msgstr "" - -#: ../compute-manage-users.rst:5 -msgid "Manage Compute users" -msgstr "" - -#: ../compute-manage-the-cloud.rst:5 -msgid "Manage the cloud" -msgstr "" - -# #-#-#-#-# blockstorage-manage-volumes.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -# #-#-#-#-# compute-manage-volumes.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -#: ../blockstorage-manage-volumes.rst:3 ../compute-manage-volumes.rst:3 -msgid "Manage volumes" -msgstr "" - -#: ../blockstorage_image_volume_cache.rst:90 -msgid "Managing cached Image-Volumes" -msgstr "" - -#: ../compute-euca2ools.rst:5 -msgid "Managing the cloud with euca2ools" -msgstr "" - -#: ../compute-node-down.rst:22 -msgid "Manual recovery" -msgstr "" - -#: ../cross_project_cors.rst:150 -msgid "Manually construct a CORS request" -msgstr "" - -#: ../cross_project.rst:5 -msgid "" -"Many features are common to all the OpenStack services and are consistent in " -"their configuration and deployment patterns. Unless explicitly noted, you " -"can safely assume that the features in this chapter are supported and " -"configured in a consistent manner." -msgstr "" - -#: ../telemetry-data-retrieval.rst:45 -msgid "" -"Many of the API endpoints accept a query filter argument, which should be a " -"list of data structures that consist of the following items:" -msgstr "" - -#: ../networking_config-agents.rst:164 -msgid "" -"Many plug-ins rely on the L3 service agent to implement the L3 " -"functionality. However, the following plug-ins already have built-in L3 " -"capabilities:" -msgstr "" - -#: ../keystone_integrate_identity_backend_ldap.rst:198 -msgid "" -"Mask account status values (include any additional attribute mappings) for " -"compatibility with various directory services. Superfluous accounts are " -"filtered with ``user_filter``." -msgstr "" - -#: ../keystone_integrate_assignment_backend_ldap.rst:110 -msgid "" -"Mask account status values (include any additional attribute mappings) for " -"compatibility with various directory services. Superfluous accounts are " -"filtered with user\\_filter." -msgstr "" - -#: ../telemetry-data-retrieval.rst:164 -msgid "Maximum of the sample volumes in each period." -msgstr "" - -#: ../telemetry-measurements.rst:5 -msgid "Measurements" +"For specifying the new header, you need to set ``metadata_headers`` option " +"under the ``[filter:ceilometer]`` section in ``proxy-server.conf`` under the " +"``swift`` folder. You can use this additional data for instance to " +"distinguish external and internal users." msgstr "" #: ../telemetry-measurements.rst:73 @@ -10347,1574 +21745,22 @@ msgid "" "notifications that this module consumes." msgstr "" -#: ../compute-remote-console-access.rst:95 -msgid "Mediates token authentication." -msgstr "" - -#: ../compute-service-groups.rst:89 -msgid "Memcache ServiceGroup driver" -msgstr "" - -#: ../dashboard_sessions.rst:45 -msgid "Memcached" -msgstr "" - -#: ../dashboard_sessions.rst:46 -msgid "" -"Memcached is a high-performance and distributed memory object caching system " -"providing in-memory key-value store for small chunks of arbitrary data." -msgstr "" - -#: ../dashboard_sessions.rst:52 -msgid "Memcached service running and accessible." -msgstr "" - -#: ../telemetry-measurements.rst:561 -msgid "Memory CUPS utilization of the system" -msgstr "" - -#: ../compute-flavors.rst:42 -msgid "Memory_MB" -msgstr "" - -#: ../compute-networking-nova.rst:363 -msgid "" -"Metadata from the OpenStack API is distributed in JSON format. To retrieve " -"the metadata, make a GET request to ``http://169.254.169.254/" -"openstack/2012-08-10/meta_data.json``:" -msgstr "" - -#: ../compute-networking-nova.rst:323 -msgid "Metadata service" -msgstr "" - -#: ../telemetry-data-collection.rst:833 -msgid "Meter definitions" -msgstr "" - -#: ../telemetry-measurements.rst:573 -msgid "Meters renamed in the Kilo release" -msgstr "" - -#: ../telemetry-data-collection.rst:175 -msgid "Middleware for the OpenStack Object Storage service" -msgstr "" - -#: ../networking_config-agents.rst:180 -msgid "MidoNet plug-in" -msgstr "" - -#: ../compute-live-migration-usage.rst:5 -msgid "Migrate instances" -msgstr "" - -#: ../compute-live-migration-usage.rst:203 -msgid "Migrate the instance using the :command:`nova live-migration` command:" -msgstr "" - -#: ../blockstorage_volume_migration.rst:146 -msgid "Migrate this volume to the second LVM back-end:" -msgstr "" - -#: ../blockstorage_volume_migration.rst:8 -msgid "Migrate volumes" -msgstr "" - -#: ../blockstorage_volume_migration.rst:198 -msgid "Migrating volumes that have snapshots are currently not allowed." -msgstr "" - -#: ../compute-configuring-migrations.rst:16 -msgid "" -"Migration enables an administrator to move a virtual-machine instance from " -"one compute host to another. This feature is useful when a compute host " -"requires maintenance. Migration can also be useful to redistribute the load " -"when many VM instances are running on a specific physical machine." -msgstr "" - -#: ../networking_adv-features.rst:637 -msgid "" -"Minimum number of resources to retrieve from the back-end for each " -"synchronization chunk. The expected number of synchronization chunks is " -"given by the ratio between ``state_sync_interval`` and " -"``min_sync_req_delay``. This size of a chunk might increase if the total " -"number of resources is such that more than ``min_chunk_size`` resources must " -"be fetched in one chunk with the current number of chunks." -msgstr "" - -#: ../telemetry-data-retrieval.rst:167 -msgid "Minimum of the sample volumes in each period." -msgstr "" - -#: ../blockstorage-consistency-groups.rst:92 -msgid "Modify a consistency group." -msgstr "" - -#: ../networking_config-identity.rst:169 -msgid "" -"Modify from the default to ``nova.network.neutronv2.api.API``, to indicate " -"that Networking should be used rather than the traditional nova-network " -"networking model." -msgstr "" - -#: ../compute-remote-console-access.rst:324 -msgid "Modify the ``width`` and ``height`` options, as follows:" -msgstr "" - -#: ../telemetry-data-collection.rst:1011 -msgid "MongoDB" -msgstr "" - -#: ../telemetry-data-collection.rst:1011 -msgid "" -"MongoDB has native TTL support for deleting samples that are older than the " -"configured ttl value." -msgstr "" - -#: ../ts_cinder_config.rst:8 -msgid "" -"Most Block Storage errors are caused by incorrect volume configurations that " -"result in volume creation failures. To resolve these failures, review these " -"logs:" -msgstr "" - -#: ../telemetry-alarms.rst:275 -msgid "" -"Most alarm attributes can be changed in this way, but there is also a " -"convenient short-cut for getting and setting the alarm state:" -msgstr "" - -#: ../cross_project_cors.rst:144 -msgid "" -"Most browsers provide helpful debug output when a CORS request is rejected. " -"Usually this happens when a request was successful, but the return headers " -"on the response do not permit access to a property which the browser is " -"trying to access." -msgstr "" - -#: ../blockstorage_backup_disks.rst:146 -msgid "Mount your partition" -msgstr "" - -#: ../blockstorage_glusterfs_backend.rst:27 -msgid "" -"Mounting GlusterFS volumes requires utilities and libraries from the " -"``glusterfs-fuse`` package. This package must be installed on all systems " -"that will access volumes backed by GlusterFS." -msgstr "" - -#: ../objectstorage_features.rst:18 -msgid "Multi-dimensional scalability" -msgstr "" - -#: ../ts_multipath_warn.rst:3 -msgid "Multipath call failed exit" -msgstr "" - -#: ../ts_multipath_warn.rst:8 -msgid "" -"Multipath call failed exit. This warning occurs in the Compute log if you do " -"not have the optional ``multipath-tools`` package installed on the compute " -"node. This is an optional package and the volume attachment does work " -"without the multipath tools installed. If the ``multipath-tools`` package is " -"installed on the compute node, it is used to perform the volume attachment. " -"The IDs in your message are unique to your system." -msgstr "" - -#: ../networking_adv-operational-features.rst:124 -msgid "Multiple RPC topics" -msgstr "" - -#: ../networking_introduction.rst:335 -msgid "Multiple VPN connections per tenant." -msgstr "" - -#: ../telemetry-data-collection.rst:974 -msgid "" -"Multiple ``ceilometer-collector`` processes can be run at a time. It is also " -"supported to start multiple worker threads per collector process. The " -"``collector_workers`` configuration option has to be modified in the " -"`Collector section `__ of the :file:`ceilometer.conf` " -"configuration file." -msgstr "" - -#: ../keystone_integrate_with_ldap.rst:50 -msgid "" -"Multiple back ends are supported. You can integrate the OpenStack Identity " -"service with a single LDAP server (configure both identity and assignments " -"to LDAP, or set identity and assignments back end with SQL or LDAP), or " -"multiple back ends using domain-specific configuration files." -msgstr "" - -#: ../telemetry-system-architecture.rst:80 -msgid "" -"Multiple database back ends can be configured in order to store events, " -"samples and alarms separately." -msgstr "" - -#: ../telemetry-data-collection.rst:972 -msgid "Multiple dispatchers can be configured for Telemetry at one time." -msgstr "" - -#: ../compute-networking-nova.rst:763 -msgid "Multiple interfaces for instances (multinic)" -msgstr "" - -#: ../networking_adv-features.rst:133 ../networking_adv-features.rst:152 -msgid "N/A" -msgstr "" - -#: ../networking_adv-features.rst:551 -msgid "" -"NSX exposes its L3 capabilities through gateway services which are usually " -"configured out of band from OpenStack. To use NSX with L3 capabilities, " -"first create an L3 gateway service in the NSX Manager. Next, in :file:`/etc/" -"neutron/plugins/vmware/nsx.ini` set ``default_l3_gw_service_uuid`` to this " -"value. By default, routers are mapped to this gateway service." -msgstr "" - -#: ../networking_config-agents.rst:182 -msgid "NSX plug-in" -msgstr "" - -#: ../networking_adv-features.rst:533 -msgid "NSX version" -msgstr "" - -# #-#-#-#-# compute-flavors.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -# #-#-#-#-# compute-live-migration-usage.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -# #-#-#-#-# telemetry-measurements.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -# #-#-#-#-# ts-eql-volume-size.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -#: ../compute-flavors.rst:39 ../compute-live-migration-usage.rst:35 -#: ../telemetry-measurements.rst:97 ../telemetry-measurements.rst:430 -#: ../telemetry-measurements.rst:484 ../telemetry-measurements.rst:528 -#: ../telemetry-measurements.rst:589 ../telemetry-measurements.rst:664 -#: ../telemetry-measurements.rst:697 ../telemetry-measurements.rst:752 -#: ../telemetry-measurements.rst:802 ../telemetry-measurements.rst:839 -#: ../telemetry-measurements.rst:910 ../telemetry-measurements.rst:973 -#: ../telemetry-measurements.rst:1059 ../telemetry-measurements.rst:1137 -#: ../telemetry-measurements.rst:1202 ../telemetry-measurements.rst:1253 -#: ../telemetry-measurements.rst:1279 ../telemetry-measurements.rst:1302 -#: ../telemetry-measurements.rst:1322 ../ts-eql-volume-size.rst:110 -msgid "Name" -msgstr "" - -#: ../telemetry-data-collection.rst:443 -msgid "Name of meter. (``--meter-name``)" -msgstr "" - -#: ../telemetry-data-collection.rst:651 -msgid "Name of the transformer." -msgstr "" - -#: ../telemetry-data-collection.rst:609 -msgid "Name of transformer" -msgstr "" - -#: ../database.rst:113 -msgid "Name you want to use for this datastore." -msgstr "" - -#: ../networking_adv-config.rst:42 -msgid "Namespace" -msgstr "" - -#: ../networking.rst:5 -msgid "Networking" -msgstr "" - -#: ../networking_introduction.rst:18 -msgid "Networking API" -msgstr "" - -#: ../networking_config-identity.rst:155 -msgid "Networking API and credential configuration" -msgstr "" - -#: ../networking_arch.rst:3 -msgid "Networking architecture" -msgstr "" - -#: ../networking_adv-operational-features.rst:8 -msgid "" -"Networking components use Python logging module to do logging. Logging " -"configuration can be provided in :file:`neutron.conf` or as command-line " -"options. Command options override ones in :file:`neutron.conf`." -msgstr "" - -#: ../compute-networking-nova.rst:14 -msgid "Networking concepts" -msgstr "" - -#: ../networking_config-agents.rst:88 -msgid "" -"Networking dhcp-agent can use `dnsmasq `__ driver which supports stateful and stateless DHCPv6 for subnets " -"created with ``--ipv6_address_mode`` set to ``dhcpv6-stateful`` or ``dhcpv6-" -"stateless``." -msgstr "" - -#: ../networking_arch.rst:11 -msgid "" -"Networking is a standalone component in the OpenStack modular architecture. " -"It's positioned alongside OpenStack components such as Compute, Image " -"service, Identity, or dashboard. Like those components, a deployment of " -"Networking often involves deploying several services to a variety of hosts." -msgstr "" - -#: ../networking_introduction.rst:20 -msgid "" -"Networking is a virtual network service that provides a powerful API to " -"define the network connectivity and IP addressing that devices from other " -"services, such as Compute, use." -msgstr "" - -#: ../networking_config-identity.rst:28 -msgid "" -"Networking must be available in the Compute service catalog. Create the " -"service:" -msgstr "" - -#: ../networking_arch.rst:56 -msgid "" -"Networking relies on the Identity service (keystone) for the authentication " -"and authorization of all API requests." -msgstr "" - -#: ../networking_auth.rst:7 -msgid "" -"Networking uses the Identity service as the default authentication service. " -"When the Identity service is enabled, users who submit requests to the " -"Networking service must provide an authentication token in ``X-Auth-Token`` " -"request header. Users obtain this token by authenticating with the Identity " -"service endpoint. For more information about authentication with the " -"Identity service, see `OpenStack Identity service API v2.0 Reference `__. When the Identity " -"service is enabled, it is not mandatory to specify the tenant ID for " -"resources in create requests because the tenant ID is derived from the " -"authentication token." -msgstr "" - -#: ../networking_config-agents.rst:111 -msgid "" -"Networking will update dnsmasq process and restart it when subnet gets " -"updated." -msgstr "" - -#: ../compute-networking-nova.rst:3 -msgid "Networking with nova-network" -msgstr "" - -#: ../compute-live-migration-usage.rst:37 -msgid "Networks" -msgstr "" - -#: ../networking_adv-features.rst:12 -msgid "" -"Networks can be categorized as either tenant networks or provider networks. " -"Tenant networks are created by normal users and details about how they are " -"physically realized are hidden from those users. Provider networks are " -"created with administrative credentials, specifying the details of how the " -"network is physically realized, usually to match some existing network in " -"the data center." -msgstr "" - -#: ../networking_multi-dhcp-agents.rst:58 -#: ../networking_multi-dhcp-agents.rst:87 -msgid "Neutron configuration file :file:`/etc/neutron/neutron.conf`:" -msgstr "" - -#: ../blockstorage_get_capabilities.rst:76 -msgid "" -"New endpoint to ``get capabilities`` list for specific storage back end is " -"also available. For more details, refer to the Block Storage API reference." -msgstr "" - -#: ../objectstorage_characteristics.rst:25 -msgid "New nodes can be added to the cluster without downtime." -msgstr "" - -#: ../blockstorage_volume_migration.rst:76 -msgid "" -"Next, as the admin user, you can see the current status of the volume " -"(replace the example ID with your own):" -msgstr "" - -#: ../objectstorage_components.rst:263 -msgid "" -"Next, the container database is updated asynchronously to reflect that there " -"is a new object in it." -msgstr "" - -# #-#-#-#-# networking_adv-features.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -# #-#-#-#-# telemetry-data-collection.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -#: ../networking_adv-features.rst:710 ../telemetry-data-collection.rst:1019 -#: ../telemetry-data-collection.rst:1023 -msgid "No" -msgstr "" - -#: ../objectstorage_features.rst:31 -msgid "No central database" -msgstr "" - -#: ../objectstorage-troubleshoot.rst:80 ../objectstorage-troubleshoot.rst:86 -#: ../objectstorage-troubleshoot.rst:88 -msgid "No help text available for this option." -msgstr "" - -#: ../objectstorage_features.rst:12 -msgid "No lock-in, lower price/GB." -msgstr "" - -#: ../objectstorage_features.rst:23 -msgid "" -"No nesting, not a traditional file system: Optimized for scale, it scales to " -"multiple petabytes and billions of objects." -msgstr "" - -#: ../dashboard_sessions.rst:27 -msgid "No persistence after a process terminates." -msgstr "" - -#: ../dashboard_sessions.rst:26 -msgid "No shared storage across processes or workers." -msgstr "" - -#: ../ts_cinder_config.rst:144 -msgid "No sign of attach call in the ``cinder-api log``." -msgstr "" - -#: ../networking_config-agents.rst:24 -msgid "Node set up: NSX plug-in" -msgstr "" - -#: ../ts_non_existent_vlun.rst:3 -msgid "Non-existent VLUN" -msgstr "" - -#: ../ts_non_existent_host.rst:3 -msgid "Non-existent host" -msgstr "" - -# #-#-#-#-# telemetry-data-collection.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -# #-#-#-#-# telemetry-measurements.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -#: ../telemetry-data-collection.rst:59 ../telemetry-data-collection.rst:1009 -#: ../telemetry-measurements.rst:97 ../telemetry-measurements.rst:430 -#: ../telemetry-measurements.rst:484 ../telemetry-measurements.rst:528 -#: ../telemetry-measurements.rst:589 ../telemetry-measurements.rst:664 -#: ../telemetry-measurements.rst:697 ../telemetry-measurements.rst:752 -#: ../telemetry-measurements.rst:802 ../telemetry-measurements.rst:839 -#: ../telemetry-measurements.rst:910 ../telemetry-measurements.rst:973 -#: ../telemetry-measurements.rst:1059 ../telemetry-measurements.rst:1137 -#: ../telemetry-measurements.rst:1202 ../telemetry-measurements.rst:1253 -#: ../telemetry-measurements.rst:1279 ../telemetry-measurements.rst:1302 -#: ../telemetry-measurements.rst:1322 -msgid "Note" -msgstr "" - -#: ../dashboard_sessions.rst:140 -msgid "" -"Note on openSUSE the path is :file:`/srv/www/openstack-dashboard/manage.py`." -msgstr "" - -#: ../blockstorage_volume_migration.rst:183 -msgid "" -"Note that ``migstat`` is None, host is the new host, and ``name_id`` holds " -"the ID of the volume created by the migration. If you look at the second LVM " -"back end, you find the logical volume ``volume-133d1f56-9ffc-4f57-8798-" -"d5217d851862``." -msgstr "" - -#: ../compute-node-down.rst:197 -msgid "" -"Note that instances will not be lost, because neither ``destroy`` nor " -"``terminate`` was invoked. The files for the instances will remain on the " -"compute node." -msgstr "" - -#: ../objectstorage-monitoring.rst:187 -msgid "" -"Note that these logging methods may safely be called anywhere you have a " -"logger object. If StatsD logging has not been configured, the methods are no-" -"ops. This avoids messy conditional logic each place a meter is recorded. " -"These example usages show the new logging methods:" -msgstr "" - -#: ../identity_troubleshoot.rst:83 -msgid "Note the expiration dates of the certificate:" -msgstr "" - -#: ../blockstorage_volume_migration.rst:107 -msgid "Note these attributes:" -msgstr "" - -# #-#-#-#-# database.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -# #-#-#-#-# networking_adv-features.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -#: ../database.rst:235 ../networking_adv-features.rst:609 -msgid "Notes" -msgstr "" - -#: ../telemetry-measurements.rst:109 ../telemetry-measurements.rst:126 -#: ../telemetry-measurements.rst:158 ../telemetry-measurements.rst:161 -#: ../telemetry-measurements.rst:765 ../telemetry-measurements.rst:768 -#: ../telemetry-measurements.rst:771 -msgid "Notific\\ ation" -msgstr "" - -#: ../telemetry-measurements.rst:101 ../telemetry-measurements.rst:105 -#: ../telemetry-measurements.rst:200 ../telemetry-measurements.rst:205 -#: ../telemetry-measurements.rst:348 -msgid "Notific\\ ation, Pollster" -msgstr "" - -#: ../telemetry-measurements.rst:676 ../telemetry-measurements.rst:679 -#: ../telemetry-measurements.rst:682 ../telemetry-measurements.rst:685 -#: ../telemetry-measurements.rst:688 ../telemetry-measurements.rst:701 -#: ../telemetry-measurements.rst:704 ../telemetry-measurements.rst:709 -#: ../telemetry-measurements.rst:712 ../telemetry-measurements.rst:717 -#: ../telemetry-measurements.rst:720 ../telemetry-measurements.rst:723 -#: ../telemetry-measurements.rst:727 ../telemetry-measurements.rst:730 -#: ../telemetry-measurements.rst:734 ../telemetry-measurements.rst:738 -#: ../telemetry-measurements.rst:741 ../telemetry-measurements.rst:843 -#: ../telemetry-measurements.rst:846 ../telemetry-measurements.rst:849 -#: ../telemetry-measurements.rst:852 ../telemetry-measurements.rst:855 -#: ../telemetry-measurements.rst:858 ../telemetry-measurements.rst:861 -#: ../telemetry-measurements.rst:864 ../telemetry-measurements.rst:867 -#: ../telemetry-measurements.rst:870 ../telemetry-measurements.rst:873 -#: ../telemetry-measurements.rst:876 ../telemetry-measurements.rst:879 -#: ../telemetry-measurements.rst:882 ../telemetry-measurements.rst:885 -#: ../telemetry-measurements.rst:888 ../telemetry-measurements.rst:891 -#: ../telemetry-measurements.rst:896 ../telemetry-measurements.rst:900 -#: ../telemetry-measurements.rst:914 ../telemetry-measurements.rst:917 -#: ../telemetry-measurements.rst:921 ../telemetry-measurements.rst:924 -#: ../telemetry-measurements.rst:927 ../telemetry-measurements.rst:931 -#: ../telemetry-measurements.rst:934 ../telemetry-measurements.rst:937 -#: ../telemetry-measurements.rst:940 ../telemetry-measurements.rst:943 -#: ../telemetry-measurements.rst:946 ../telemetry-measurements.rst:950 -#: ../telemetry-measurements.rst:957 ../telemetry-measurements.rst:960 -#: ../telemetry-measurements.rst:963 ../telemetry-measurements.rst:1097 -#: ../telemetry-measurements.rst:1101 ../telemetry-measurements.rst:1105 -#: ../telemetry-measurements.rst:1109 ../telemetry-measurements.rst:1113 -#: ../telemetry-measurements.rst:1117 ../telemetry-measurements.rst:1121 -#: ../telemetry-measurements.rst:1126 ../telemetry-measurements.rst:1152 -#: ../telemetry-measurements.rst:1156 ../telemetry-measurements.rst:1160 -#: ../telemetry-measurements.rst:1165 ../telemetry-measurements.rst:1174 -#: ../telemetry-measurements.rst:1179 ../telemetry-measurements.rst:1188 -#: ../telemetry-measurements.rst:1192 ../telemetry-measurements.rst:1216 -#: ../telemetry-measurements.rst:1220 ../telemetry-measurements.rst:1224 -#: ../telemetry-measurements.rst:1229 ../telemetry-measurements.rst:1234 -#: ../telemetry-measurements.rst:1238 ../telemetry-measurements.rst:1243 -msgid "Notifica\\ tion" -msgstr "" - -#: ../telemetry-measurements.rst:668 ../telemetry-measurements.rst:672 -#: ../telemetry-measurements.rst:953 ../telemetry-measurements.rst:1063 -#: ../telemetry-measurements.rst:1067 ../telemetry-measurements.rst:1071 -#: ../telemetry-measurements.rst:1075 ../telemetry-measurements.rst:1141 -#: ../telemetry-measurements.rst:1145 ../telemetry-measurements.rst:1170 -#: ../telemetry-measurements.rst:1184 ../telemetry-measurements.rst:1206 -#: ../telemetry-measurements.rst:1210 -msgid "Notifica\\ tion, Po\\ llster" -msgstr "" - -#: ../telemetry-measurements.rst:434 ../telemetry-measurements.rst:437 -#: ../telemetry-measurements.rst:440 ../telemetry-measurements.rst:443 -#: ../telemetry-measurements.rst:446 ../telemetry-measurements.rst:449 -#: ../telemetry-measurements.rst:452 ../telemetry-measurements.rst:455 -#: ../telemetry-measurements.rst:458 ../telemetry-measurements.rst:461 -#: ../telemetry-measurements.rst:488 ../telemetry-measurements.rst:491 -#: ../telemetry-measurements.rst:494 ../telemetry-measurements.rst:498 -#: ../telemetry-measurements.rst:501 ../telemetry-measurements.rst:1257 -#: ../telemetry-measurements.rst:1260 ../telemetry-measurements.rst:1263 -#: ../telemetry-measurements.rst:1266 ../telemetry-measurements.rst:1269 -#: ../telemetry-measurements.rst:1283 ../telemetry-measurements.rst:1288 -#: ../telemetry-measurements.rst:1292 ../telemetry-measurements.rst:1306 -#: ../telemetry-measurements.rst:1309 ../telemetry-measurements.rst:1312 -msgid "Notification" -msgstr "" - -#: ../telemetry-troubleshooting-guide.rst:53 -msgid "Notification agent" -msgstr "" - -#: ../networking_adv-operational-features.rst:54 -msgid "Notification options" -msgstr "" - -# #-#-#-#-# blockstorage_image_volume_cache.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -# #-#-#-#-# networking_adv-operational-features.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -# #-#-#-#-# telemetry-data-collection.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -#: ../blockstorage_image_volume_cache.rst:73 -#: ../networking_adv-operational-features.rst:48 -#: ../telemetry-data-collection.rst:27 ../telemetry-data-collection.rst:38 -msgid "Notifications" -msgstr "" - -#: ../networking_adv-operational-features.rst:50 -msgid "" -"Notifications can be sent when Networking resources such as network, subnet " -"and port are created, updated or deleted." -msgstr "" - -#: ../database.rst:134 -msgid "" -"Now that you have a MySQL datastore, you can add a version to it, using the " -"trove-manage :command:`datastore_version_update` command. The version " -"indicates which guest image to use." -msgstr "" - -#: ../blockstorage_backup_disks.rst:196 -msgid "" -"Now that you have an efficient and consistent backup, use this command to " -"clean up the file system:" -msgstr "" - -#: ../networking_multi-dhcp-agents.rst:312 -msgid "" -"Now that you have run the :command:`net-list-on-dhcp-agent` and :command:" -"`dhcp-agent-list-hosting-net` commands, you can add a network to a DHCP " -"agent and remove one from it." -msgstr "" - -#: ../orchestration-introduction.rst:18 -msgid "" -"Now, Orchestration also executes HOT (Heat Orchestration Template) templates " -"written in YAML: a terse notation that loosely follows Python/Ruby-type " -"structural conventions (colons, returns, indentation), so it is more easy to " -"write, parse, grep, generate with tools, and maintain source-code management " -"systems." -msgstr "" - -#: ../telemetry-measurements.rst:814 -msgid "Number of API r\\ equests against Ceph Object Ga\\ teway (radosgw)" -msgstr "" - -#: ../telemetry-measurements.rst:771 -msgid "Number of API r\\ equests against OpenStack Obje\\ ct Storage" -msgstr "" - -#: ../networking_introduction.rst:99 -msgid "Number of backlog requests with which to configure the socket." -msgstr "" - -#: ../telemetry-measurements.rst:762 ../telemetry-measurements.rst:811 -msgid "Number of conta\\ iners" -msgstr "" - -#: ../telemetry-measurements.rst:682 -msgid "Number of delet\\ es on the image" -msgstr "" - -#: ../objectstorage-troubleshoot.rst:66 -msgid "Number of errors to find before a device is unmounted" -msgstr "" - -#: ../telemetry-measurements.rst:1087 -msgid "Number of incom\\ ing Bytes" -msgstr "" - -#: ../telemetry-measurements.rst:765 -msgid "Number of incom\\ ing bytes" -msgstr "" - -#: ../telemetry-measurements.rst:164 -msgid "Number of incoming bytes" -msgstr "" - -#: ../telemetry-measurements.rst:180 -msgid "Number of incoming packets" -msgstr "" - -#: ../telemetry-measurements.rst:1312 -msgid "Number of indices created in a table" -msgstr "" - -#: ../objectstorage-troubleshoot.rst:82 -msgid "Number of minutes to look back in :file:`/var/log/kern.log`" -msgstr "" - -#: ../telemetry-measurements.rst:756 -msgid "Number of objec\\ ts" -msgstr "" - -#: ../telemetry-measurements.rst:776 ../telemetry-measurements.rst:819 -msgid "Number of objec\\ ts in container" -msgstr "" - -#: ../telemetry-measurements.rst:806 -msgid "Number of objects" -msgstr "" - -#: ../telemetry-measurements.rst:1091 -msgid "Number of outgo\\ ing Bytes" -msgstr "" - -#: ../telemetry-measurements.rst:768 -msgid "Number of outgo\\ ing bytes" -msgstr "" - -#: ../telemetry-measurements.rst:172 -msgid "Number of outgoing bytes" -msgstr "" - -#: ../telemetry-measurements.rst:189 -msgid "Number of outgoing packets" -msgstr "" - -#: ../compute_arch.rst:95 -msgid "Number of processor cores and the amount of RAM that can be allocated." -msgstr "" - -#: ../telemetry-measurements.rst:130 ../telemetry-measurements.rst:232 -msgid "Number of read requests" -msgstr "" - -#: ../telemetry-measurements.rst:637 -msgid "Number of recei\\ ved datagrams" -msgstr "" - -#: ../telemetry-data-retrieval.rst:161 -msgid "Number of samples in each period." -msgstr "" - -#: ../networking_introduction.rst:96 -msgid "Number of seconds to keep retrying to listen." -msgstr "" - -#: ../telemetry-measurements.rst:641 -msgid "Number of sent datagrams" -msgstr "" - -#: ../telemetry-measurements.rst:676 -msgid "Number of updat\\ es on the image" -msgstr "" - -#: ../telemetry-measurements.rst:679 -msgid "Number of uploa\\ ds on the image" -msgstr "" - -#: ../telemetry-measurements.rst:126 -msgid "Number of virtual CPUs allocated to the instance" -msgstr "" - -#: ../compute-flavors.rst:56 -msgid "Number of virtual CPUs presented to the instance." -msgstr "" - -#: ../compute_arch.rst:93 -msgid "Number of volumes that can be launched." -msgstr "" - -#: ../telemetry-measurements.rst:137 ../telemetry-measurements.rst:241 -msgid "Number of write requests" -msgstr "" - -#: ../compute_arch.rst:201 -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-live-migration-usage.rst:62 -msgid "OS-EXT-SRV-ATTR:host" -msgstr "" - -#: ../objectstorage_auditors.rst:3 -msgid "Object Auditor" -msgstr "" - -# #-#-#-#-# compute-images-instances.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -# #-#-#-#-# objectstorage.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -#: ../compute-images-instances.rst:127 ../objectstorage.rst:3 -msgid "Object Storage" -msgstr "" - -#: ../objectstorage_characteristics.rst:34 -msgid "Object Storage (swift)" -msgstr "" - -#: ../objectstorage_components.rst:121 -msgid "" -"Object Storage allows configuring zones in order to isolate failure " -"boundaries. Each data replica resides in a separate zone, if possible. At " -"the smallest level, a zone could be a single drive or a grouping of a few " -"drives. If there were five object storage servers, then each server would " -"represent its own zone. Larger deployments would have an entire rack (or " -"multiple racks) of object servers, each representing a zone. The goal of " -"zones is to allow the cluster to tolerate significant outages of storage " -"servers without losing all replicas of the data." -msgstr "" - -#: ../objectstorage_characteristics.rst:3 -msgid "Object Storage characteristics" -msgstr "" - -#: ../objectstorage_intro.rst:20 -msgid "" -"Object Storage is ideal for cost effective, scale-out storage. It provides a " -"fully distributed, API-accessible storage platform that can be integrated " -"directly into applications or used for backup, archiving, and data retention." -msgstr "" - -#: ../objectstorage-monitoring.rst:3 -msgid "Object Storage monitoring" -msgstr "" - -#: ../objectstorage_characteristics.rst:17 -msgid "Object data can be located anywhere in the cluster." -msgstr "" - -#: ../objectstorage_replication.rst:46 ../objectstorage_replication.rst:75 -msgid "Object replication" -msgstr "" - -#: ../networking_introduction.rst:59 -msgid "" -"Offers flexibility for the cloud administrator to customize network " -"offerings." -msgstr "" - -#: ../dashboard_sessions.rst:160 -msgid "On Fedora/RHEL/CentOS::" -msgstr "" - -#: ../networking_config-agents.rst:263 -msgid "" -"On Red Hat, SUSE and Ubuntu based systems, the neutron-ovs-cleanup service " -"runs the :command:`neutron-ovs-cleanup` command automatically. However, on " -"Debian-based systems, you must manually run this command or write your own " -"system script that runs on boot before the neutron-l3-agent service starts." -msgstr "" - -#: ../networking_config-agents.rst:82 -msgid "" -"On Red Hat, SUSE, and Ubuntu based systems, the ``neutron-ovs-cleanup`` " -"service runs the :command:`neutron-ovs-cleanup` command automatically. " -"However, on Debian-based systems, you must manually run this command or " -"write your own system script that runs on boot before the ``neutron-dhcp-" -"agent`` service starts." -msgstr "" - -#: ../networking_introduction.rst:192 -msgid "" -"On Ubuntu, modify the ``[fwaas]`` section in the :file:`/etc/neutron/" -"fwaas_driver.ini` file instead of :file:`/etc/neutron/neutron.conf`." -msgstr "" - -#: ../dashboard_sessions.rst:169 -msgid "" -"On Ubuntu, restart the nova-api service to ensure that the API server can " -"connect to the dashboard without error::" -msgstr "" - -#: ../dashboard_sessions.rst:156 -msgid "On Ubuntu::" -msgstr "" - -#: ../blockstorage_backup_disks.rst:127 -msgid "" -"On a Debian-based distribution, you can use the :command:`apt-get install " -"kpartx` command to install :command:`kpartx`." -msgstr "" - -#: ../compute-manage-logs.rst:144 -msgid "On a compute node, edit the :file:`/etc/nova/nova.conf` file:" -msgstr "" - -#: ../compute-networking-nova.rst:266 -msgid "" -"On all nodes, edit the :file:`nova.conf` file and specify ``use_ipv6 = " -"True``." -msgstr "" - -#: ../compute-configuring-migrations.rst:173 -msgid "" -"On both compute nodes, enable the 'execute/search' bit on your shared " -"directory to allow qemu to be able to use the images within the directories. " -"On all hosts, run the following command:" -msgstr "" - -# #-#-#-#-# blockstorage-api-throughput.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -# #-#-#-#-# blockstorage_glusterfs_backend.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -# #-#-#-#-# blockstorage_nfs_backend.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -#: ../blockstorage-api-throughput.rst:26 -#: ../blockstorage_glusterfs_backend.rst:152 -#: ../blockstorage_glusterfs_backend.rst:186 -#: ../blockstorage_nfs_backend.rst:65 ../blockstorage_nfs_backend.rst:91 -#: ../blockstorage_nfs_backend.rst:107 ../blockstorage_nfs_backend.rst:139 -msgid "" -"On distributions that include ``openstack-config``, you can configure this " -"by running the following command instead::" -msgstr "" - -#: ../keystone_secure_identity_to_ldap_backend.rst:52 -msgid "" -"On distributions that include openstack-config, you can configure TLS " -"encryption on LDAP traffic by running the following commands instead::" -msgstr "" - -#: ../blockstorage_glusterfs_backend.rst:127 -msgid "" -"On distributions that include openstack-config, you can configure this by " -"running the following command instead::" -msgstr "" - -#: ../compute-manage-logs.rst:113 -msgid "" -"On each compute host, create a file named :file:`/etc/rsyslog.d/60-nova." -"conf`, with the following content:" -msgstr "" - -#: ../blockstorage_volume_migration.rst:128 -msgid "" -"On nodes that run CentOS, Fedora, openSUSE, Red Hat Enterprise Linux, or " -"SUSE Linux Enterprise, run:" -msgstr "" - -#: ../blockstorage_volume_migration.rst:136 -msgid "On nodes that run Ubuntu or Debian, run:" -msgstr "" - -#: ../dashboard_sessions.rst:165 -msgid "On openSUSE::" -msgstr "" - -#: ../objectstorage_auditors.rst:5 -msgid "" -"On system failures, the XFS file system can sometimes truncate files it is " -"trying to write and produce zero-byte files. The object-auditor will catch " -"these problems but in the case of a system crash it is advisable to run an " -"extra, less rate limited sweep, to check for these specific files. You can " -"run this command as follows::" -msgstr "" - -#: ../ts_no_emulator_x86_64.rst:14 -msgid "" -"On the KVM host, run ``cat /proc/cpuinfo``. Make sure the ``vmx`` or ``svm`` " -"flags are set." -msgstr "" - -#: ../compute-configuring-migrations.rst:291 -msgid "" -"On versions older than Kilo, the Compute service does not use libvirt's live " -"migration by default because there is a risk that the migration process will " -"never end. This can happen if the guest operating system uses blocks on the " -"disk faster than they can be migrated." -msgstr "" - -#: ../compute-node-down.rst:301 -msgid "" -"On your instances, if you have the whole ``/home/`` directory on the disk, " -"leave a user's directory with the user's bash files and the :file:" -"`authorized_keys` file (instead of emptying the ``/home`` directory and " -"mapping the disk on it)." -msgstr "" - -#: ../blockstorage-lio-iscsi-support.rst:9 -msgid "" -"Once configured, you can use the :command:`cinder-rtstool` command to manage " -"the volumes. This command enables you to create, delete, and verify volumes " -"and determine targets and add iSCSI initiators to the system." -msgstr "" - -#: ../telemetry-alarms.rst:264 -msgid "" -"Once the state of the alarm has settled down, we might decide that we set " -"that bar too low with 70%, in which case the threshold (or most any other " -"alarm attribute) can be updated thusly:" -msgstr "" - -#: ../compute-manage-logs.rst:123 -msgid "" -"Once you have created the file, restart the rsyslog service. Error-level log " -"messages on the compute hosts should now be sent to the log server." -msgstr "" - -#: ../blockstorage_volume_backups_export_import.rst:56 -msgid "" -"Once you have imported the backup metadata into a Block Storage database, " -"restore the volume (see the section called :ref:`volume_backups`)." -msgstr "" - -#: ../keystone_secure_identity_to_ldap_backend.rst:10 -msgid "Once you verify the location of your certificate authority file:" -msgstr "" - -#: ../compute-remote-console-access.rst:123 -msgid "" -"One or more ``nova-novncproxy`` services. Supports browser-based noVNC " -"clients. For simple deployments, this service typically runs on the same " -"machine as ``nova-api`` because it operates as a proxy between the public " -"network and the private compute host network." -msgstr "" - -#: ../compute-remote-console-access.rst:128 -msgid "" -"One or more ``nova-xvpvncproxy`` services. Supports the special Java client " -"discussed here. For simple deployments, this service typically runs on the " -"same machine as ``nova-api`` because it acts as a proxy between the public " -"network and the private compute host network." -msgstr "" - -#: ../compute-remote-console-access.rst:133 -msgid "" -"One or more compute hosts. These compute hosts must have correctly " -"configured options, as follows." -msgstr "" - -#: ../compute-networking-nova.rst:935 -msgid "" -"One way to check whether this is the problem is to open three terminals and " -"run the following commands:" -msgstr "" - -#: ../keystone_certificates_for_pki.rst:129 -msgid "" -"One way to request a signing certificate from an external CA is to first " -"generate a PKCS #10 Certificate Request Syntax (CRS) using OpenSSL CLI." -msgstr "" - -#: ../blockstorage_volume_migration.rst:63 -msgid "Only Block Storage V2 API supports :command:`get-pools`." -msgstr "" - -#: ../blockstorage-consistency-groups.rst:17 -msgid "" -"Only Block Storage V2 API supports consistency groups. You can specify ``--" -"os-volume-api-version 2`` when using Block Storage command line for " -"consistency group operations." -msgstr "" - -#: ../compute_arch.rst:165 -msgid "" -"Only a single configured instance can access a persistent volume. Multiple " -"instances cannot access a persistent volume. This type of configuration " -"requires a traditional network file system to allow multiple instances " -"accessing the persistent volume. It also requires a traditional network file " -"system like NFS, CIFS, or a cluster file system such as GlusterFS. These " -"systems can be built within an OpenStack cluster, or provisioned outside of " -"it, but OpenStack software does not provide these features." -msgstr "" - -#: ../networking_adv-features.rst:774 -msgid "Only administrators can manage the L3 metering labels and rules." -msgstr "" - -#: ../compute-configuring-migrations.rst:12 -msgid "" -"Only cloud administrators can perform live migrations. If your cloud is " -"configured to use cells, you can perform live migration within but not " -"between cells." -msgstr "" - -#: ../networking_config-agents.rst:174 -msgid "" -"Only the proprietary BigSwitch controller implements L3 functionality. When " -"using Floodlight as your OpenFlow controller, L3 functionality is not " -"available." -msgstr "" - -#: ../identity_user_crud.rst:32 -msgid "Only use a KVS back end for tokens when testing." -msgstr "" - -#: ../keystone_secure_identity_to_ldap_backend.rst:14 -msgid "Open the :file:`/etc/keystone/keystone.conf` configuration file." -msgstr "" - -#: ../cross_project_cors.rst:142 -msgid "Open your browser's console log" -msgstr "" - -# #-#-#-#-# telemetry-data-collection.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -# #-#-#-#-# telemetry-measurements.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -#: ../telemetry-data-collection.rst:129 ../telemetry-data-collection.rst:269 -#: ../telemetry-measurements.rst:693 -msgid "OpenStack Block Storage" -msgstr "" - -#: ../blockstorage_volume_backed_image.rst:8 -msgid "" -"OpenStack Block Storage can quickly create a volume from an image that " -"refers to a volume storing image data (Image-Volume). Compared to the other " -"stores such as file and swift, creating a volume from a Volume-backed image " -"performs better when the block storage driver supports efficient volume " -"cloning." -msgstr "" - -#: ../blockstorage_get_capabilities.rst:13 -msgid "" -"OpenStack Block Storage enables administrators to configure *volume type* " -"and *extra specs* without specific knowledge of the storage back end." -msgstr "" - -#: ../blockstorage.rst:20 -msgid "" -"OpenStack Block Storage enables you to add extra block-level storage to your " -"OpenStack Compute instances. This service is similar to the Amazon EC2 " -"Elastic Block Storage (EBS) offering." -msgstr "" - -#: ../blockstorage_volume_number_weigher.rst:10 -msgid "" -"OpenStack Block Storage enables you to choose a volume back end according to " -"``free_capacity`` and ``allocated_capacity``. The volume number weigher " -"feature lets the scheduler choose a volume back end based on its volume " -"number in the volume back end. This can provide another means to improve the " -"volume back ends' I/O balance and the volumes' I/O performance." -msgstr "" - -#: ../blockstorage-driver-filter-weighing.rst:8 -msgid "" -"OpenStack Block Storage enables you to choose a volume back end based on " -"back-end specific properties by using the DriverFilter and GoodnessWeigher " -"for the scheduler. The driver filter and weigher scheduling can help ensure " -"that the scheduler chooses the best back end based on requested volume " -"properties as well as various back-end specific properties." -msgstr "" - -#: ../blockstorage_over_subscription.rst:8 -msgid "" -"OpenStack Block Storage enables you to choose a volume back end based on " -"virtual capacities for thin provisioning using the oversubscription ratio." -msgstr "" - -#: ../blockstorage_image_volume_cache.rst:8 -msgid "" -"OpenStack Block Storage has an optional Image cache which can dramatically " -"improve the performance of creating a volume from an image. The improvement " -"depends on many factors, primarily how quickly the configured back end can " -"clone a volume." -msgstr "" - -#: ../blockstorage_glusterfs_backend.rst:169 -msgid "OpenStack Block Storage is now configured to use a GlusterFS back end." -msgstr "" - -#: ../index.rst:3 -msgid "OpenStack Cloud Administrator Guide" -msgstr "" - -# #-#-#-#-# telemetry-data-collection.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -# #-#-#-#-# telemetry-measurements.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -#: ../telemetry-data-collection.rst:61 ../telemetry-measurements.rst:93 -msgid "OpenStack Compute" -msgstr "" - -#: ../compute-security.rst:7 -msgid "" -"OpenStack Compute can be integrated with various third-party technologies to " -"increase security. For more information, see the `OpenStack Security Guide " -"`_." -msgstr "" - -#: ../compute_arch.rst:5 -msgid "OpenStack Compute contains several main components." -msgstr "" - -#: ../telemetry-measurements.rst:418 -msgid "" -"OpenStack Compute is capable of collecting ``CPU`` related meters from the " -"compute host machines. In order to use that you need to set the " -"``compute_monitors`` option to ``ComputeDriverCPUMonitor`` in the :file:" -"`nova.conf` configuration file. For further information see the Compute " -"configuration section in the `Compute chapter `__ of the " -"OpenStack Configuration Reference." -msgstr "" - -#: ../compute-manage-logs.rst:47 -msgid "" -"OpenStack Compute services can send logging information to syslog. This is " -"useful if you want to use rsyslog to forward logs to a remote machine. " -"Separately configure the Compute service (nova), the Identity service " -"(keystone), the Image service (glance), and, if you are using it, the Block " -"Storage service (cinder) to send log messages to syslog. Open these " -"configuration files:" -msgstr "" - -#: ../compute-remote-console-access.rst:12 -msgid "" -"OpenStack Compute supports VNC consoles to guests. The VNC protocol is " -"fairly limited, lacking support for multiple monitors, bi-directional audio, " -"reliable cut-and-paste, video streaming and more. SPICE is a new protocol " -"that aims to address the limitations in VNC and provide good remote desktop " -"support." -msgstr "" - -#: ../compute-manage-logs.rst:133 -msgid "" -"OpenStack Icehouse and earlier supports read-only access using the serial " -"console using the ``os-GetSerialOutput`` server action. Most cloud images " -"enable this feature by default. For more information, see :ref:`compute-" -"common-errors-and-fixes`." -msgstr "" - -#: ../telemetry-measurements.rst:835 -msgid "OpenStack Identity" -msgstr "" - -#: ../telemetry-troubleshooting-guide.rst:84 -msgid "" -"OpenStack Identity is about to change API version from v2 to v3. The " -"``adminURL`` endpoint (which is available via the port: ``35357``) supports " -"only the v3 version, while the other two supports both." -msgstr "" - -#: ../keystone_use_trusts.rst:5 -msgid "" -"OpenStack Identity manages authentication and authorization. A trust is an " -"OpenStack Identity extension that enables delegation and, optionally, " -"impersonation through ``keystone``. A trust extension defines a relationship " -"between:" -msgstr "" - -#: ../keystone_caching_layer.rst:6 -msgid "" -"OpenStack Identity supports a caching layer that is above the configurable " -"subsystems (for example, token, assignment). OpenStack Identity uses the " -"`dogpile.cache `__ library " -"which allows flexible cache back ends. The majority of the caching " -"configuration options are set in the ``[cache]`` section of the :file:" -"`keystone.conf` file. However, each section that has the capability to be " -"cached usually has a caching boolean value that toggles caching." -msgstr "" - -#: ../orchestration-auth-model.rst:78 -msgid "" -"OpenStack Identity then provides a trust_id, which can be consumed by *only* " -"the trustee to obtain a *trust scoped token*. This token is limited in scope " -"such that the trustee has limited access to those roles delegated, along " -"with effective impersonation of the trustor user if it was selected when " -"creating the trust. More information is available in the :ref:`Identity " -"management ` section." -msgstr "" - -#: ../orchestration-auth-model.rst:56 -msgid "" -"OpenStack Identity trusts is a new authorization method available since the " -"Icehouse release." -msgstr "" - -#: ../identity_management.rst:7 -msgid "" -"OpenStack Identity, code-named keystone, is the default identity management " -"system for OpenStack. After you install Identity, you configure it through " -"the :file:`/etc/keystone.conf` configuration file and, possibly, a separate " -"logging configuration file. You initialize data into Identity by using the " -"``keystone`` command-line client." -msgstr "" - -# #-#-#-#-# telemetry-data-collection.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -# #-#-#-#-# telemetry-measurements.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -#: ../telemetry-data-collection.rst:71 ../telemetry-measurements.rst:660 -msgid "OpenStack Image service" -msgstr "" - -#: ../compute-images-instances.rst:139 -msgid "" -"OpenStack Image service can read virtual machine images that are available " -"on the Internet using HTTP. This store is read only." -msgstr "" - -#: ../compute-manage-logs.rst:138 -msgid "" -"OpenStack Juno and later supports read-write access using the serial console " -"using the ``os-GetSerialConsole`` server action. This feature also requires " -"a websocket client to access the serial console." -msgstr "" - -# #-#-#-#-# telemetry-data-collection.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -# #-#-#-#-# telemetry-measurements.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -#: ../telemetry-data-collection.rst:82 ../telemetry-data-collection.rst:265 -#: ../telemetry-measurements.rst:906 -msgid "OpenStack Networking" -msgstr "" - -#: ../networking_introduction.rst:68 -msgid "" -"OpenStack Networking supports SSL for the Networking API server. By default, " -"SSL is disabled but you can enable it in the :file:`neutron.conf` file." -msgstr "" - -#: ../networking_arch.rst:71 -msgid "" -"OpenStack Networking uses the NSX plug-in to integrate with an existing " -"VMware vCenter deployment. When installed on the network nodes, the NSX plug-" -"in enables a NSX controller to centrally manage configuration settings and " -"push them to managed network nodes. Network nodes are considered managed " -"when they're added as hypervisors to the NSX controller." -msgstr "" - -#: ../telemetry-system-architecture.rst:148 -msgid "OpenStack Networking:" -msgstr "" - -# #-#-#-#-# telemetry-data-collection.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -# #-#-#-#-# telemetry-measurements.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -#: ../telemetry-data-collection.rst:267 ../telemetry-measurements.rst:748 -msgid "OpenStack Object Storage" -msgstr "" - -#: ../objectstorage_intro.rst:5 -msgid "" -"OpenStack Object Storage (code-named swift) is open source software for " -"creating redundant, scalable data storage using clusters of standardized " -"servers to store petabytes of accessible data. It is a long-term storage " -"system for large amounts of static data that can be retrieved, leveraged, " -"and updated. Object Storage uses a distributed architecture with no central " -"point of control, providing greater scalability, redundancy, and permanence. " -"Objects are written to multiple hardware devices, with the OpenStack " -"software responsible for ensuring data replication and integrity across the " -"cluster. Storage clusters scale horizontally by adding new nodes. Should a " -"node fail, OpenStack works to replicate its content from other active nodes. " -"Because OpenStack uses software logic to ensure data replication and " -"distribution across different devices, inexpensive commodity hard drives and " -"servers can be used in lieu of more expensive equipment." -msgstr "" - -#: ../networking_multi-dhcp-agents.rst:41 -msgid "OpenStack controller host - controlnod" -msgstr "" - -#: ../blockstorage_volume_migration.rst:10 -msgid "" -"OpenStack has the ability to migrate volumes between back-ends which support " -"its volume-type. Migrating a volume transparently moves its data from the " -"current back-end for the volume to a new one. This is an administrator " -"function, and can be used for functions including storage evacuation (for " -"maintenance or decommissioning), or manual optimizations (for example, " -"performance, reliability, or cost)." -msgstr "" - -#: ../index.rst:8 -msgid "" -"OpenStack offers open source software for cloud administrators to manage and " -"troubleshoot an OpenStack cloud." -msgstr "" - -#: ../compute-images-instances.rst:408 -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_arch.rst:126 -msgid "" -"OpenStack provides two classes of block storage: ephemeral storage and " -"persistent volume." -msgstr "" - -#: ../telemetry-data-collection.rst:59 -msgid "OpenStack service" -msgstr "" - -#: ../cross_project_cors.rst:10 -msgid "" -"OpenStack supports :term:`Cross-Origin Resource Sharing (CORS)`, a W3C " -"specification defining a contract by which the single-origin policy of a " -"user agent (usually a browser) may be relaxed. It permits it's javascript " -"engine to access an API that does not reside on the same domain, protocol, " -"or port." -msgstr "" - -#: ../compute-security.rst:150 -msgid "" -"OpenStack supports encrypting Compute metadata traffic with HTTPS. Enable " -"SSL encryption in the :file:`metadata_agent.ini` file." -msgstr "" - -#: ../identity_concepts.rst:46 -msgid "OpenStackClient" -msgstr "" - -#: ../database.rst:233 -msgid "Operating System" -msgstr "" - -# #-#-#-#-# networking_adv-features.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -# #-#-#-#-# networking_config-agents.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -# #-#-#-#-# networking_use.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -#: ../networking_adv-features.rst:206 ../networking_adv-features.rst:356 -#: ../networking_adv-features.rst:491 ../networking_adv-features.rst:783 -#: ../networking_config-agents.rst:492 ../networking_use.rst:47 -#: ../networking_use.rst:123 ../networking_use.rst:241 -msgid "Operation" -msgstr "" - -#: ../networking_adv-features.rst:576 -msgid "Operational status synchronization in the VMware NSX plug-in" -msgstr "" - -#: ../blockstorage-driver-filter-weighing.rst:101 -msgid "Operations" -msgstr "" - -#: ../networking_adv-config.rst:26 -msgid "Option" -msgstr "" - -#: ../networking_adv-features.rst:605 -msgid "Option name" -msgstr "" - -#: ../compute-flavors.rst:58 -msgid "" -"Optional property allows created servers to have a different bandwidth cap " -"than that defined in the network they are att\\ ached to. This factor is " -"multiplied by the rxtx_base propert\\ y of the network. Default value is " -"1.0. That is, the same as attached network. This parameter is only available " -"for Xen or NSX based systems." -msgstr "" - -#: ../compute-flavors.rst:54 -msgid "Optional swap space allocation for the instance." -msgstr "" - -#: ../networking_introduction.rst:86 -msgid "" -"Optional. CA certificate file that is used when you securely start the " -"Networking API server. This file verifies connecting clients. Set this " -"option when API clients must authenticate to the API server by using SSL " -"certificates that are signed by a trusted CA." -msgstr "" - -#: ../blockstorage_glusterfs_backend.rst:105 -msgid "" -"Optionally, if your environment requires additional mount options for a " -"share, you can add them to the share's entry::" -msgstr "" - -#: ../compute-images-instances.rst:291 -msgid "" -"Optionally, in the :file:`glance-api.conf` file, specify whether roles or " -"policies are used in the property protections configuration file::" -msgstr "" - -#: ../blockstorage_nfs_backend.rst:85 -msgid "" -"Optionally, provide any additional NFS mount options required in your " -"environment in the ``nfs_mount_options`` configuration key of :file:`/etc/" -"cinder/cinder.conf`. If your NFS shares do not require any additional mount " -"options (or if you are unsure), skip this step." -msgstr "" - -#: ../networking_config-agents.rst:382 -msgid "Or, enable the Linux Bridge LBaaS driver:" -msgstr "" - -#: ../orchestration.rst:5 -msgid "Orchestration" -msgstr "" - -#: ../orchestration-auth-model.rst:8 -msgid "Orchestration authorization model" -msgstr "" - -#: ../orchestration-auth-model.rst:11 -msgid "" -"Orchestration authorization model defines the process of authorization that " -"orchestration module uses to authorize requests during so called deferred " -"operations. The typical example of such operation is autoscaling group " -"update when Orchestration requests other components (OpenStack Compute, " -"Openstack Networking or others) to extend (reduce) capacity of autoscaling " -"group." -msgstr "" - -#: ../orchestration-introduction.rst:24 -msgid "" -"Orchestration can be accessed via the CLI, and using RESTful queries. " -"Orchestration module provides both an OpenStack-native REST API and a " -"CloudFormation-compatible Query API. Orchestration is also integrated with " -"OpenStack dashboard in order to launch stacks from templates through a web " -"interface." -msgstr "" - -#: ../orchestration-stack-domain-users.rst:110 -msgid "" -"Orchestration creates a new *stack domain project* in the ``heat`` domain if " -"the stack contains any resources which require creation of a *stack domain " -"user*." -msgstr "" - -#: ../orchestration-introduction.rst:5 -msgid "" -"Orchestration is a tool for orchestrating clouds that automatically " -"configures and deploys resources in stacks. Such deployments can be simple — " -"like deploying WordPress on Ubuntu with an SQL back end. And they can be " -"quite complex, like launching a group of servers that autoscale: starting " -"and stopping based on realtime CPU loading information from the Telemetry " -"module." -msgstr "" - -#: ../orchestration.rst:7 -msgid "" -"Orchestration is an orchestration engine that provides the possibility to " -"launch multiple composite cloud applications based on templates in the form " -"of text files that can be treated like code. A native Heat Orchestration " -"Template (HOT) format is evolving, but it also endeavors to provide " -"compatibility with the AWS CloudFormation template format, so that many " -"existing CloudFormation templates can be launched on OpenStack." -msgstr "" - -# #-#-#-#-# telemetry-data-collection.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -# #-#-#-#-# telemetry-measurements.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -#: ../telemetry-data-collection.rst:114 ../telemetry-measurements.rst:1249 -msgid "Orchestration module" -msgstr "" - -#: ../orchestration-stack-domain-users.rst:25 -msgid "" -"Orchestration provides APIs which enable all of these things, but all of " -"those APIs require some sort of authentication. For example, credentials to " -"access the instance agent is running on. The heat-cfntools agents use signed " -"requests, which requires an ec2 keypair created via OpenStack Identity, " -"which is then used to sign requests to the Orchestration CloudFormation and " -"CloudWatch compatible APIs, which are authenticated by Orchestration via " -"signature validation (which uses the OpenStack Identity ec2tokens " -"extension). Stack domain users allow to encapsulate all stack-defined users " -"(users created as a result of things contained in an Orchestration template) " -"in a separate domain which is created specifically to contain things related " -"only to the Orchestration stacks. A user is created which is the *domain " -"admin*, and Orchestration uses that user to manage the lifecycle of the " -"users in the stack *user domain*." -msgstr "" - -#: ../orchestration-stack-domain-users.rst:9 -msgid "" -"Orchestration stack domain users allows Orchestration module to authorize " -"inside VMs booted and execute the following operations:" -msgstr "" - -#: ../orchestration-introduction.rst:12 -msgid "" -"Orchestration stacks are defined with templates, which are non-procedural " -"documents describing tasks in terms of resources, parameters, inputs, " -"constraints and dependencies. When Orchestration module was originally " -"introduced, it worked with AWS CloudFormation templates, which are in JSON " -"format." -msgstr "" - -#: ../orchestration-auth-model.rst:101 -msgid "Orchestration stores the encrypted *trust id* in the Orchestration DB." -msgstr "" - -#: ../orchestration-auth-model.rst:91 -msgid "" -"Orchestration uses the token to create a trust between the stack owner " -"(trustor) and the Orchestration module user (trustee), delegating a special " -"role (or roles) as defined in the *trusts_delegated_roles* list in the " -"Orchestration configuration file. By default, Orchestration module sets all " -"the roles from trustor available for trustee. Deployers may modify this list " -"to reflect local RBAC policy, for example, to ensure the heat process can " -"only access those services expected while impersonating a stack owner." -msgstr "" - -#: ../networking_adv-features.rst:717 -msgid "Order of rule processing" +#: ../telemetry-measurements.rst:78 +msgid "" +"The Telemetry module supports storing notifications as events. This " +"functionality was added later, therefore the list of meters still contains " +"existence type and other event related items. The proper way of using " +"Telemetry is to configure it to use the event store and turn off the " +"collection of the event related meters. For further information about events " +"see `Events section `__ in the Telemetry documentation. For further information about how " +"to turn on and off meters see :ref:`telemetry-pipeline-configuration`. " +"Please also note that currently no migration is available to move the " +"already existing event type samples to the event store." +msgstr "" + +#: ../telemetry-measurements.rst:94 +msgid "The following meters are collected for OpenStack Compute:" msgstr "" #: ../telemetry-measurements.rst:97 ../telemetry-measurements.rst:430 @@ -11930,266 +21776,119 @@ msgstr "" msgid "Origin" msgstr "" -#: ../telemetry-alarms.rst:177 -msgid "" -"Other notable alarm attributes that may be set on creation, or via a " -"subsequent update, include:" +#: ../telemetry-measurements.rst:97 +msgid "Support" msgstr "" -#: ../telemetry-alarms.rst:170 -msgid "" -"Otherwise the alarm will tend to flit in and out of the ``insufficient " -"data`` state due to the mismatch between the actual frequency of datapoints " -"in the metering store and the statistics queries used to compare against the " -"alarm threshold. If a shorter alarm period is needed, then the corresponding " -"interval should be adjusted in the :file:`pipeline.yaml` file." +#: ../telemetry-measurements.rst:97 ../telemetry-measurements.rst:430 +#: ../telemetry-measurements.rst:484 ../telemetry-measurements.rst:528 +#: ../telemetry-measurements.rst:589 ../telemetry-measurements.rst:664 +#: ../telemetry-measurements.rst:697 ../telemetry-measurements.rst:752 +#: ../telemetry-measurements.rst:802 ../telemetry-measurements.rst:839 +#: ../telemetry-measurements.rst:910 ../telemetry-measurements.rst:973 +#: ../telemetry-measurements.rst:1059 ../telemetry-measurements.rst:1137 +#: ../telemetry-measurements.rst:1202 ../telemetry-measurements.rst:1253 +#: ../telemetry-measurements.rst:1279 ../telemetry-measurements.rst:1302 +#: ../telemetry-measurements.rst:1322 +msgid "Unit" msgstr "" -#: ../compute-flavors.rst:192 -msgid "Outbound traffic:" +#: ../telemetry-measurements.rst:99 ../telemetry-measurements.rst:432 +#: ../telemetry-measurements.rst:666 ../telemetry-measurements.rst:699 +#: ../telemetry-measurements.rst:754 ../telemetry-measurements.rst:912 +#: ../telemetry-measurements.rst:975 ../telemetry-measurements.rst:1255 +#: ../telemetry-measurements.rst:1324 +msgid "**Meters added in the Icehouse release or earlier**" msgstr "" -#: ../telemetry-measurements.rst:544 -msgid "Outlet temperat\\ ure of the system" +#: ../telemetry-measurements.rst:101 ../telemetry-measurements.rst:200 +msgid "Existence of instance" msgstr "" -#: ../telemetry-alarms.rst:283 -msgid "" -"Over time the state of the alarm may change often, especially if the " -"threshold is chosen to be close to the trending value of the statistic. You " -"can follow the history of an alarm over its lifecycle via the audit API:" +#: ../telemetry-measurements.rst:101 ../telemetry-measurements.rst:105 +#: ../telemetry-measurements.rst:122 ../telemetry-measurements.rst:133 +#: ../telemetry-measurements.rst:140 ../telemetry-measurements.rst:147 +#: ../telemetry-measurements.rst:154 ../telemetry-measurements.rst:168 +#: ../telemetry-measurements.rst:176 ../telemetry-measurements.rst:184 +#: ../telemetry-measurements.rst:193 ../telemetry-measurements.rst:236 +#: ../telemetry-measurements.rst:245 ../telemetry-measurements.rst:254 +#: ../telemetry-measurements.rst:263 +msgid "Libvirt, Hyper-V, vSphere" msgstr "" -#: ../objectstorage_ringbuilder.rst:55 -msgid "Overload" +#: ../telemetry-measurements.rst:101 ../telemetry-measurements.rst:105 +#: ../telemetry-measurements.rst:200 ../telemetry-measurements.rst:205 +#: ../telemetry-measurements.rst:348 +msgid "Notific\\ ation, Pollster" msgstr "" -#: ../networking_adv-features.rst:713 -msgid "" -"Overrides the default virtual router used to handle traffic for packets that " -"match the rule." +#: ../telemetry-measurements.rst:101 ../telemetry-measurements.rst:105 +msgid "inst\\ ance" msgstr "" -#: ../telemetry-measurements.rst:1011 -msgid "Overrun errors received on port" +#: ../telemetry-measurements.rst:101 ../telemetry-measurements.rst:200 +msgid "instance" msgstr "" -#: ../blockstorage_over_subscription.rst:6 -msgid "Oversubscription in thin provisioning" +#: ../telemetry-measurements.rst:101 ../telemetry-measurements.rst:105 +#: ../telemetry-measurements.rst:109 ../telemetry-measurements.rst:113 +#: ../telemetry-measurements.rst:119 ../telemetry-measurements.rst:122 +#: ../telemetry-measurements.rst:126 ../telemetry-measurements.rst:130 +#: ../telemetry-measurements.rst:133 ../telemetry-measurements.rst:137 +#: ../telemetry-measurements.rst:140 ../telemetry-measurements.rst:144 +#: ../telemetry-measurements.rst:147 ../telemetry-measurements.rst:151 +#: ../telemetry-measurements.rst:154 ../telemetry-measurements.rst:158 +#: ../telemetry-measurements.rst:161 ../telemetry-measurements.rst:200 +#: ../telemetry-measurements.rst:205 ../telemetry-measurements.rst:210 +#: ../telemetry-measurements.rst:216 ../telemetry-measurements.rst:221 +#: ../telemetry-measurements.rst:226 ../telemetry-measurements.rst:290 +#: ../telemetry-measurements.rst:296 ../telemetry-measurements.rst:301 +#: ../telemetry-measurements.rst:304 ../telemetry-measurements.rst:314 +#: ../telemetry-measurements.rst:318 ../telemetry-measurements.rst:324 +#: ../telemetry-measurements.rst:348 ../telemetry-measurements.rst:355 +msgid "instance ID" msgstr "" -#: ../networking_arch.rst:9 -msgid "Overview" +#: ../telemetry-measurements.rst:105 ../telemetry-measurements.rst:205 +#: ../telemetry-measurements.rst:348 +msgid "Existence of instance (OpenStack types)" msgstr "" -#: ../keystone_certificates_for_pki.rst:5 -msgid "" -"PKI stands for Public Key Infrastructure. Tokens are documents, " -"cryptographically signed using the X509 standard. In order to work correctly " -"token generation requires a public/private key pair. The public key must be " -"signed in an X509 certificate, and the certificate used to sign it must be " -"available as a Certificate Authority (CA) certificate. These files can be " -"generated either using the ``keystone-manage`` utility, or externally " -"generated. The files need to be in the locations specified by the top level " -"Identity service configuration file :file:`keystone.conf` as specified in " -"the above section. Additionally, the private key should only be readable by " -"the system user that will run the Identity service." +#: ../telemetry-measurements.rst:105 +msgid "instance:\\ " msgstr "" -#: ../networking_config-agents.rst:184 -msgid "PLUMgrid plug-in" +#: ../telemetry-measurements.rst:109 ../telemetry-measurements.rst:119 +#: ../telemetry-measurements.rst:126 ../telemetry-measurements.rst:130 +#: ../telemetry-measurements.rst:137 ../telemetry-measurements.rst:144 +#: ../telemetry-measurements.rst:151 ../telemetry-measurements.rst:158 +#: ../telemetry-measurements.rst:161 ../telemetry-measurements.rst:164 +#: ../telemetry-measurements.rst:172 ../telemetry-measurements.rst:180 +#: ../telemetry-measurements.rst:189 ../telemetry-measurements.rst:232 +#: ../telemetry-measurements.rst:241 ../telemetry-measurements.rst:250 +#: ../telemetry-measurements.rst:259 ../telemetry-measurements.rst:355 +msgid "Libvirt, Hyper-V" msgstr "" -#: ../compute-live-migration-usage.rst:167 -msgid "PROJECT" +#: ../telemetry-measurements.rst:109 ../telemetry-measurements.rst:113 +#: ../telemetry-measurements.rst:210 ../telemetry-measurements.rst:290 +#: ../telemetry-measurements.rst:296 +msgid "MB" msgstr "" -#: ../baremetal.rst:45 -msgid "PXE deploy process" +#: ../telemetry-measurements.rst:109 ../telemetry-measurements.rst:126 +#: ../telemetry-measurements.rst:158 ../telemetry-measurements.rst:161 +#: ../telemetry-measurements.rst:765 ../telemetry-measurements.rst:768 +#: ../telemetry-measurements.rst:771 +msgid "Notific\\ ation" msgstr "" -#: ../compute-networking-nova.rst:929 -msgid "" -"Packet loss can be caused by Linux networking configuration settings related " -"to bridges. Certain settings can cause packets to be dropped between the " -"VLAN interface (for example, ``vlan100``) and the associated bridge " -"interface (for example, ``br100``) on the host running ``nova-network``." +#: ../telemetry-measurements.rst:109 +msgid "Volume of RAM allocated to the instance" msgstr "" -#: ../compute-networking-nova.rst:922 -msgid "Packet loss from instances to nova-network server (VLANManager mode)" -msgstr "" - -#: ../telemetry-measurements.rst:1030 -msgid "Packets matches for table" -msgstr "" - -#: ../telemetry-measurements.rst:983 -msgid "Packets receive\\ d on port" -msgstr "" - -#: ../telemetry-measurements.rst:1042 -msgid "Packets received" -msgstr "" - -#: ../telemetry-measurements.rst:986 -msgid "Packets transmi\\ tted on port" -msgstr "" - -#: ../telemetry-data-collection.rst:654 -msgid "Parameters of the transformer." -msgstr "" - -#: ../objectstorage_ringbuilder.rst:34 -msgid "Partition assignment list" -msgstr "" - -#: ../objectstorage_ringbuilder.rst:137 -msgid "Partition shift value" -msgstr "" - -#: ../blockstorage_backup_disks.rst:111 -msgid "Partition table discovery" -msgstr "" - -#: ../objectstorage_components.rst:173 -msgid "Partitions" -msgstr "" - -#: ../orchestration-auth-model.rst:25 -msgid "Password authorization" -msgstr "" - -#: ../orchestration-auth-model.rst:27 -msgid "" -"Password authorization is the initial authorization model that was supported " -"by Orchestration module. This kind of authorization requires from a user to " -"pass a password to Orchestration. Orchestration stores the encrypted " -"password in the database and uses it for deferred operations." -msgstr "" - -#: ../orchestration-auth-model.rst:114 -msgid "" -"Password authorization model had been the default authorization model " -"enabled for the Orchestration module before the Kilo release. Since the Kilo " -"release, the trusts authorization model has been enabled by default." -msgstr "" - -#: ../orchestration-auth-model.rst:20 -msgid "Password authorization," -msgstr "" - -#: ../keystone_configure_with_SSL.rst:67 -msgid "Path to the CA trust chain." -msgstr "" - -#: ../keystone_configure_with_SSL.rst:62 -msgid "" -"Path to the Identity service private certificate file. If you include the " -"private key in the certfile, you can omit the keyfile." -msgstr "" - -#: ../keystone_configure_with_SSL.rst:59 -msgid "Path to the Identity service public certificate file." -msgstr "" - -#: ../compute-configuring-migrations.rst:202 -msgid "" -"Perform the same check on ``HostB`` and ``HostC``, paying special attention " -"to the permissions (Compute should be able to write)" -msgstr "" - -#: ../telemetry-measurements.rst:614 -msgid "Physical memory buffer size" -msgstr "" - -#: ../telemetry-data-collection.rst:523 -msgid "Pipeline configuration" -msgstr "" - -#: ../telemetry-data-collection.rst:524 -msgid "" -"Pipeline configuration by default, is stored in separate configuration " -"files, called :file:`pipeline.yaml` and :file:`event_pipeline.yaml`, next to " -"the :file:`ceilometer.conf` file. The meter pipeline and event pipeline " -"configuration files can be set by the ``pipeline_cfg_file`` and " -"``event_pipeline_cfg_file`` options listed in the `Description of " -"configuration options for api table `__ section in the " -"OpenStack Configuration Reference respectively. Multiple pipelines can be " -"defined in one pipeline configuration file." -msgstr "" - -#: ../telemetry-data-collection.rst:580 -msgid "" -"Please be aware that we do not have any duplication check between pipelines " -"and if you add a meter to multiple pipelines then it is assumed the " -"duplication is intentional and may be stored multiple times according to the " -"specified sinks." -msgstr "" - -#: ../networking_config-plugins.rst:3 -msgid "Plug-in configurations" -msgstr "" - -#: ../networking_adv-features.rst:446 -msgid "Plug-in specific extensions" -msgstr "" - -#: ../networking_config-agents.rst:5 -msgid "" -"Plug-ins typically have requirements for particular software that must be " -"run on each node that handles data packets. This includes any node that runs " -"nova-compute and nodes that run dedicated OpenStack Networking service " -"agents such as ``neutron-dhcp-agent``, ``neutron-l3-agent``, ``neutron-" -"metering-agent`` or ``neutron-lbaas-agent``." -msgstr "" - -#: ../networking_auth.rst:48 -msgid "" -"Policies are triggered by the Networking policy engine whenever one of them " -"matches a Networking API operation or a specific attribute being used in a " -"given operation. For instance the ``create_subnet`` policy is triggered " -"every time a ``POST /v2.0/subnets`` request is sent to the Networking " -"server; on the other hand ``create_network:shared`` is triggered every time " -"the *shared* attribute is explicitly specified (and set to a value different " -"from its default) in a ``POST /v2.0/networks`` request. It is also worth " -"mentioning that policies can also be related to specific API extensions; for " -"instance ``extension:provider_network:set`` is triggered if the attributes " -"defined by the Provider Network extensions are specified in an API request." -msgstr "" - -#: ../telemetry-data-collection.rst:32 ../telemetry-data-collection.rst:202 -msgid "Polling" -msgstr "" - -#: ../telemetry-system-architecture.rst:18 -msgid "" -"Polls for different kinds of meter data by using the polling plug-ins " -"(pollsters) registered in different namespaces. It provides a single polling " -"interface across different namespaces." -msgstr "" - -#: ../telemetry-system-architecture.rst:29 -msgid "" -"Polls the local hypervisor or libvirt daemon to acquire performance data for " -"the local instances, messages and emits the data as AMQP messages, by using " -"the polling plug-ins (pollsters) registered in the compute polling namespace." -msgstr "" - -#: ../telemetry-system-architecture.rst:35 -msgid "" -"Polls the local node with IPMI support, in order to acquire IPMI sensor data " -"and Intel Node Manager data, by using the polling plug-ins (pollsters) " -"registered in the IPMI polling namespace." -msgstr "" - -#: ../telemetry-system-architecture.rst:23 -msgid "" -"Polls the public RESTful APIs of other OpenStack services such as Compute " -"service and Image service, in order to keep tabs on resource existence, by " -"using the polling plug-ins (pollsters) registered in the central polling " -"namespace." +#: ../telemetry-measurements.rst:109 +msgid "memory" msgstr "" #: ../telemetry-measurements.rst:113 ../telemetry-measurements.rst:119 @@ -12253,10999 +21952,317 @@ msgstr "" msgid "Pollster" msgstr "" -#: ../telemetry-measurements.rst:1328 -msgid "Power consumption" -msgstr "" - -#: ../telemetry-data-collection.rst:447 -msgid "Predefined meter types:" -msgstr "" - -#: ../compute-configuring-migrations.rst:110 -msgid "" -"Prepare at least three servers. In this example, we refer to the servers as " -"``HostA``, ``HostB``, and ``HostC``:" -msgstr "" - -#: ../telemetry-system-architecture.rst:14 -msgid "" -"Presents aggregated metering data to consumers (such as billing engines, " -"analytics tools and so forth)." -msgstr "" - -#: ../compute-manage-volumes.rst:40 -msgid "Print a list of available 'volume types'." -msgstr "" - -#: ../compute-images-instances.rst:303 -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 " -"change depending on the settings chosen for the compute node and the Image " -"service." -msgstr "" - -#: ../telemetry-data-collection.rst:983 -msgid "" -"Prior to the Juno release, it is not recommended to use multiple workers per " -"collector process when using PostgreSQL as the database back end." -msgstr "" - -#: ../compute-configuring-migrations.rst:283 -msgid "" -"Prior to the Kilo release, the Compute service did not use the libvirt live " -"migration function by default. To enable this function, add the following " -"line to the ``[libvirt]`` section of the :file:`nova.conf` file:" -msgstr "" - -#: ../compute-networking-nova.rst:580 -msgid "Private and public IP addresses" -msgstr "" - -#: ../networking_introduction.rst:82 -msgid "" -"Private key file that is used when you securely start the Networking API " -"server." -msgstr "" - -#: ../keystone_certificates_for_pki.rst:111 -msgid "Private key files must not be protected by a password" -msgstr "" - -#: ../keystone_configure_with_SSL.rst:23 -msgid "Private key for the CA." -msgstr "" - -#: ../keystone_configure_with_SSL.rst:26 -msgid "Private key for the Identity service server." -msgstr "" - -# #-#-#-#-# ts-duplicate-3par-host.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -# #-#-#-#-# ts-eql-volume-size.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -# #-#-#-#-# ts-failed-attach-vol-after-detach.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -# #-#-#-#-# ts-failed-attach-vol-no-sysfsutils.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -# #-#-#-#-# ts-failed-connect-vol-FC-SAN.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -# #-#-#-#-# ts-HTTP-bad-req-in-cinder-vol-log.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -# #-#-#-#-# ts_multipath_warn.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -# #-#-#-#-# ts_no_emulator_x86_64.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -# #-#-#-#-# ts_non_existent_host.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -# #-#-#-#-# ts_non_existent_vlun.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -# #-#-#-#-# ts_vol_attach_miss_sg_scan.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -#: ../ts-duplicate-3par-host.rst:9 ../ts-eql-volume-size.rst:9 -#: ../ts-failed-attach-vol-after-detach.rst:9 -#: ../ts-failed-attach-vol-no-sysfsutils.rst:9 -#: ../ts-failed-connect-vol-FC-SAN.rst:9 -#: ../ts-HTTP-bad-req-in-cinder-vol-log.rst:9 ../ts_multipath_warn.rst:6 -#: ../ts_no_emulator_x86_64.rst:6 ../ts_non_existent_host.rst:6 -#: ../ts_non_existent_vlun.rst:6 ../ts_vol_attach_miss_sg_scan.rst:6 -msgid "Problem" -msgstr "" - -#: ../telemetry-data-collection.rst:26 -msgid "" -"Processing notifications from other OpenStack services, by consuming " -"messages from the configured message queue system." -msgstr "" - -#: ../identity_concepts.rst:51 -msgid "Project" -msgstr "" - -#: ../telemetry-measurements.rst:879 -msgid "Project is crea\\ ted" -msgstr "" - -#: ../telemetry-measurements.rst:882 -msgid "Project is dele\\ ted" -msgstr "" - -#: ../telemetry-measurements.rst:885 -msgid "Project is upda\\ ted" -msgstr "" - -#: ../compute-flavors.rst:307 -msgid "Project private flavors" -msgstr "" - -#: ../compute-live-migration-usage.rst:58 -msgid "Property" -msgstr "" - -#: ../orchestration-stack-domain-users.rst:21 -msgid "" -"Provide application level status or meters from inside the instance. For " -"example, allow AutoScaling actions to be performed in response to some " -"measure of performance or quality of service." -msgstr "" - -#: ../networking_adv-operational-features.rst:21 -msgid "Provide logging setting in :file:`neutron.conf`." -msgstr "" - -#: ../networking_adv-operational-features.rst:15 -msgid "Provide logging settings in a logging configuration file." -msgstr "" - -#: ../orchestration-stack-domain-users.rst:12 -msgid "" -"Provide metadata to agents inside instances, which poll for changes and " -"apply the configuration expressed in the metadata to the instance." -msgstr "" - -#: ../networking_adv-features.rst:117 -msgid "Provider attributes" -msgstr "" - -#: ../networking_adv-features.rst:10 -msgid "Provider networks" -msgstr "" - -#: ../networking_adv-features.rst:517 -msgid "" -"Provider networks can be implemented in different ways by the underlying NSX " -"platform." -msgstr "" - -#: ../networking_adv-features.rst:19 -msgid "" -"Provider networks enable cloud administrators to create Networking networks " -"that map directly to the physical networks in the data center. This is " -"commonly used to give tenants direct access to a public network that can be " -"used to reach the Internet. It might also be used to integrate with VLANs in " -"the network that already have a defined meaning (for example, enable a VM " -"from the marketing department to be placed on the same VLAN as bare-metal " -"marketing hosts in the same data center)." -msgstr "" - -#: ../networking_arch.rst:38 -msgid "" -"Provides DHCP services to tenant networks. Required by certain plug-ins." -msgstr "" - -#: ../networking_arch.rst:47 -msgid "Provides L3 traffic metering for tenant networks." -msgstr "" - -#: ../networking_arch.rst:42 -msgid "" -"Provides L3/NAT forwarding to provide external network access for VMs on " -"tenant networks. Required by certain plug-ins." -msgstr "" - -#: ../objectstorage_components.rst:39 -msgid "Proxy servers" -msgstr "" - -#: ../objectstorage_components.rst:41 -msgid "" -"Proxy servers are the public face of Object Storage and handle all of the " -"incoming API requests. Once a proxy server receives a request, it determines " -"the storage node based on the object's URL, for example, https://swift." -"example.com/v1/account/container/object. Proxy servers also coordinate " -"responses, handle failures, and coordinate timestamps." -msgstr "" - -#: ../objectstorage_components.rst:47 -msgid "" -"Proxy servers use a shared-nothing architecture and can be scaled as needed " -"based on projected workloads. A minimum of two proxy servers should be " -"deployed for redundancy. If one proxy server fails, the others take over." -msgstr "" - -#: ../keystone_configure_with_SSL.rst:19 -msgid "Public and private certificate for Identity service middleware/client." -msgstr "" - -#: ../keystone_configure_with_SSL.rst:16 -msgid "Public certificate for Identity service server." -msgstr "" - -#: ../telemetry-data-retrieval.rst:467 -msgid "Publishers" -msgstr "" - -#: ../telemetry-data-retrieval.rst:485 -msgid "" -"Publishers can be specified in the ``publishers`` section for each pipeline " -"(for further details about pipelines see :ref:`data-collection-and-" -"processing`) that is defined in the `pipeline.yaml `__ file." -msgstr "" - -#: ../telemetry-data-collection.rst:35 -msgid "Pushing samples via the RESTful API of Telemetry." -msgstr "" - -#: ../dashboard_sessions.rst:53 -msgid "Python module ``python-memcached`` installed." -msgstr "" - -#: ../dashboard_sessions.rst:73 -msgid "Python modules ``redis`` and ``django-redis`` installed." -msgstr "" - -#: ../blockstorage-driver-filter-weighing.rst:149 -msgid "QoS\\_support" -msgstr "" - -#: ../telemetry-data-retrieval.rst:33 -msgid "Query" -msgstr "" - -#: ../identity_concepts.rst:359 -msgid "Query role assignments to groups" -msgstr "" - -#: ../compute-node-down.rst:35 -msgid "" -"Query the Compute database to check the status of the host. This example " -"converts an EC2 API instance ID into an OpenStack ID. If you use the :" -"command:`nova` commands, you can substitute the ID directly (the output in " -"this example has been truncated):" -msgstr "" - -#: ../compute-images-instances.rst:144 -msgid "RADOS block device (RBD)" -msgstr "" - -#: ../objectstorage_features.rst:33 -msgid "RAID not required" -msgstr "" - -#: ../compute-flavors.rst:268 -msgid "" -"RATE-BYTES—(Integer) Allowed amount of bytes that the guest can read from " -"the host's entropy per period." -msgstr "" - -#: ../compute-flavors.rst:271 -msgid "RATE-PERIOD—(Integer) Duration of the read period in seconds." -msgstr "" - -#: ../telemetry-data-collection.rst:35 -msgid "RESTful API" -msgstr "" - -#: ../database.rst:243 -msgid "RHEL 7, CentOS 7, Fedora 20, and Fedora 21" -msgstr "" - -#: ../telemetry-measurements.rst:488 ../telemetry-measurements.rst:491 -msgid "RPM" -msgstr "" - -#: ../compute-flavors.rst:58 -msgid "RXTX_Factor" -msgstr "" - -#: ../compute-flavors.rst:271 -msgid "Random-number generator" -msgstr "" - -#: ../telemetry-data-collection.rst:504 -msgid "" -"Rapid polling cadences should be avoided, as it results in a huge amount of " -"data in a short time frame, which may negatively affect the performance of " -"both Telemetry and the underlying database back end. We therefore strongly " -"recommend you do not use small granularity values like 10 seconds." -msgstr "" - -#: ../telemetry-data-collection.rst:617 -msgid "Rate of change" -msgstr "" - -#: ../blockstorage_ratelimit_volume_copy_bandwidth.rst:8 -msgid "Rate-limit volume copy bandwidth" -msgstr "" - -#: ../objectstorage_features.rst:47 -msgid "Realtime visibility into client requests" -msgstr "" - -#: ../compute-node-down.rst:247 -msgid "" -"Reattach the volumes to their respective instances, if required, using the :" -"command:`nova volume-attach` command. This example uses a file of listed " -"volumes to reattach them:" -msgstr "" - -#: ../compute_arch.rst:343 -msgid "Reboot instances" -msgstr "" - -#: ../compute-node-down.rst:82 -msgid "Reboot the VM:" -msgstr "" - -#: ../networking_adv-features.rst:533 -msgid "Recommended Value" -msgstr "" - -#: ../telemetry-troubleshooting-guide.rst:71 -msgid "Recommended ``auth_url`` to be used" -msgstr "" - -#: ../telemetry-troubleshooting-guide.rst:26 -msgid "Recommended order of starting services" -msgstr "" - -#: ../compute-node-down.rst:144 -msgid "Recover cloud after disaster" -msgstr "" - -#: ../compute-node-down.rst:97 -msgid "Recover from a UID/GID mismatch" -msgstr "" - -#: ../compute-node-down.rst:5 -msgid "Recover from a failed compute node" -msgstr "" - -# #-#-#-#-# blockstorage_glusterfs_backend.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -# #-#-#-#-# blockstorage_nfs_backend.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -#: ../blockstorage_glusterfs_backend.rst:20 -#: ../blockstorage_glusterfs_backend.rst:141 -#: ../blockstorage_nfs_backend.rst:20 ../blockstorage_nfs_backend.rst:79 -msgid "Red Hat Enterprise Linux" -msgstr "" - -#: ../dashboard_sessions.rst:66 -msgid "Redis" -msgstr "" - -#: ../dashboard_sessions.rst:67 -msgid "" -"Redis is an open source, BSD licensed, advanced key-value store. It is often " -"referred to as a data structure server." -msgstr "" - -#: ../dashboard_sessions.rst:72 -msgid "Redis service running and accessible." -msgstr "" - -#: ../telemetry-data-collection.rst:609 -msgid "Reference name for configuration" -msgstr "" - -#: ../telemetry-data-retrieval.rst:56 -msgid "" -"Regardless of the endpoint on which the filter is applied on, it will always " -"target the fields of the `Sample type `__." -msgstr "" - -#: ../identity_concepts.rst:58 -msgid "Region" -msgstr "" - -#: ../blockstorage-consistency-groups.rst:45 -msgid "Remove ``group:nobody`` to enable these APIs::" -msgstr "" - -#: ../compute-networking-nova.rst:745 -msgid "Remove a network from a project" -msgstr "" - -#: ../networking_multi-dhcp-agents.rst:360 -msgid "Remove a network from a specified DHCP agent." -msgstr "" - -#: ../compute-manage-volumes.rst:30 -msgid "Remove a snapshot." -msgstr "" - -#: ../identity_concepts.rst:349 -msgid "Remove a user from a group" -msgstr "" - -#: ../compute-manage-volumes.rst:20 -msgid "Remove a volume." -msgstr "" - -#: ../keystone_certificates_for_pki.rst:228 -msgid "" -"Remove all signing certificates from all your hosts to force OpenStack " -"Compute to download the new ``signing_cert``." -msgstr "" - -#: ../compute-networking-nova.rst:714 -msgid "" -"Remove floating IP addresses using the same parameters as the create command:" -msgstr "" - -#: ../blockstorage_backup_disks.rst:207 -msgid "Remove the snapshot::" -msgstr "" - -#: ../networking_adv-features.rst:387 -msgid "Removes security groups from a port." -msgstr "" - -#: ../networking_adv-features.rst:296 -msgid "Removes the interfaces from the router." -msgstr "" - -#: ../compute-node-down.rst:134 -msgid "Repeat all steps for the :file:`libvirt-qemu` files, if required." -msgstr "" - -#: ../objectstorage-troubleshoot.rst:175 -msgid "" -"Repeat the procedure for :file:`container.ring.gz` and :file:`object.ring." -"gz`, and you might get usable builder files." -msgstr "" - -#: ../blockstorage_backup_disks.rst:211 -msgid "Repeat these steps for all your volumes." -msgstr "" - -#: ../compute-default-ports.rst:33 -msgid "Repeat this process for each Compute service node." -msgstr "" - -#: ../blockstorage_glusterfs_backend.rst:110 -msgid "Replace OPTIONS with a comma-separated list of mount options." -msgstr "" - -#: ../blockstorage_nfs_backend.rst:97 -msgid "" -"Replace OPTIONS with the mount options to be used when accessing NFS shares. " -"See the manual page for NFS for more information on available mount options " -"(:command:`man nfs`)." -msgstr "" - -#: ../blockstorage-api-throughput.rst:32 -msgid "Replace ``CORES`` with the number of CPU cores/threads on a machine." -msgstr "" - -#: ../keystone_certificates_for_pki.rst:231 -msgid "" -"Replace the old signing key with the new signing key. Move the new signing " -"certificate above the old certificate in the ``signing_cert`` file." -msgstr "" - -#: ../objectstorage_ringbuilder.rst:93 -msgid "Replica counts" -msgstr "" - -#: ../objectstorage_replication.rst:43 -msgid "Replicates containers and objects." -msgstr "" - -#: ../objectstorage_replication.rst:46 -msgid "Replicates object data." -msgstr "" - -#: ../objectstorage_replication.rst:3 -msgid "Replication" -msgstr "" - -#: ../objectstorage_replication.rst:14 -msgid "" -"Replication uses a push model, with records and files generally only being " -"copied from local to remote replicas. This is important because data on the " -"node might not belong there (as in the case of hand offs and ring changes), " -"and a replicator cannot know which data it should pull in from elsewhere in " -"the cluster. Any node that contains data must ensure that data gets to where " -"it belongs. The ring handles replica placement." -msgstr "" - -#: ../objectstorage_components.rst:204 -msgid "Replicators" -msgstr "" - -#: ../keystone_certificates_for_pki.rst:120 -msgid "Request Signing Certificate from External CA" -msgstr "" - -#: ../keystone_certificates_for_pki.rst:127 -msgid "Request a signing certificate from an external CA" -msgstr "" - -#: ../cross_project_cors.rst:155 -msgid "Request::" -msgstr "" - -#: ../blockstorage-driver-filter-weighing.rst:168 -msgid "Requested volume properties" -msgstr "" - -#: ../networking_introduction.rst:114 -msgid "" -"Requests from a unique source IP address are consistently directed to the " -"same instance." -msgstr "" - -# #-#-#-#-# networking_adv-features.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -# #-#-#-#-# networking_config-identity.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -#: ../networking_adv-features.rst:691 ../networking_config-identity.rst:167 -msgid "Required" -msgstr "" - -#: ../dashboard_sessions.rst:50 ../dashboard_sessions.rst:70 -msgid "Requirements:" -msgstr "" - -#: ../keystone_configure_with_SSL.rst:70 -msgid "Requires client certificate. Default is False." -msgstr "" - -# #-#-#-#-# networking_introduction.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -# #-#-#-#-# telemetry-measurements.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -#: ../networking_introduction.rst:29 ../telemetry-measurements.rst:97 -#: ../telemetry-measurements.rst:430 ../telemetry-measurements.rst:484 -#: ../telemetry-measurements.rst:528 ../telemetry-measurements.rst:589 -#: ../telemetry-measurements.rst:664 ../telemetry-measurements.rst:697 -#: ../telemetry-measurements.rst:752 ../telemetry-measurements.rst:802 -#: ../telemetry-measurements.rst:839 ../telemetry-measurements.rst:910 -#: ../telemetry-measurements.rst:973 ../telemetry-measurements.rst:1059 -#: ../telemetry-measurements.rst:1137 ../telemetry-measurements.rst:1202 -#: ../telemetry-measurements.rst:1253 ../telemetry-measurements.rst:1279 -#: ../telemetry-measurements.rst:1302 ../telemetry-measurements.rst:1322 -msgid "Resource" -msgstr "" - -#: ../cross_project_cors.rst:159 -msgid "Response::" -msgstr "" - -#: ../blockstorage-consistency-groups.rst:57 -msgid "Restart Block Storage API service after changing policies." -msgstr "" - -#: ../ts_cinder_config.rst:175 -msgid "" -"Restart ``tgt`` and ``cinder-*`` services so they pick up the new " -"configuration." -msgstr "" - -#: ../compute-networking-nova.rst:269 -msgid "Restart all ``nova-*`` services." -msgstr "" - -#: ../dashboard_sessions.rst:154 -msgid "Restart and refresh Apache:" -msgstr "" - -#: ../compute-configuring-migrations.rst:235 -msgid "" -"Restart libvirt. After you run the command, ensure that libvirt is " -"successfully restarted" -msgstr "" - -#: ../networking_config-plugins.rst:184 -msgid "Restart neutron-server to apply settings:" -msgstr "" - -#: ../networking_config-plugins.rst:41 -msgid "Restart neutron-server to apply the settings:" -msgstr "" - -# #-#-#-#-# keystone_integrate_assignment_backend_ldap.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -# #-#-#-#-# keystone_integrate_identity_backend_ldap.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -#: ../keystone_integrate_assignment_backend_ldap.rst:78 -#: ../keystone_integrate_identity_backend_ldap.rst:67 -#: ../keystone_integrate_identity_backend_ldap.rst:171 -msgid "Restart the OpenStack Identity service::" -msgstr "" - -#: ../blockstorage_glusterfs_backend.rst:75 -msgid "Restart the ``glusterd`` service::" -msgstr "" - -#: ../compute-node-down.rst:230 -msgid "" -"Restart the instances using the :command:`nova reboot INSTANCE` command." -msgstr "" - -#: ../networking_introduction.rst:214 -msgid "" -"Restart the neutron-l3-agent and neutron-server services to apply the " -"settings." -msgstr "" - -#: ../networking_config-plugins.rst:89 ../networking_config-plugins.rst:248 -msgid "Restart the neutron-server service to apply the settings:" -msgstr "" - -#: ../keystone_integrate_identity_backend_ldap.rst:96 -msgid "Restart the service::" -msgstr "" - -#: ../compute-node-down.rst:136 -msgid "Restart the services." -msgstr "" - -#: ../blockstorage_glusterfs_removal.rst:28 -msgid "" -"Restarting the Block Storage services will prevent the ``cinder`` volume " -"service from exporting the deleted GlusterFS volume. This will prevent any " -"instances from mounting the volume from that point onwards." -msgstr "" - -#: ../objectstorage_features.rst:51 -msgid "Restrict containers per account" -msgstr "" - -#: ../telemetry-data-collection.rst:30 -msgid "" -"Retrieve information directly from the hypervisor or from the host machine " -"using SNMP, or by using the APIs of other OpenStack services." -msgstr "" - -#: ../objectstorage_ringbuilder.rst:27 -msgid "Ring data structure" -msgstr "" - -#: ../objectstorage_ringbuilder.rst:3 -msgid "Ring-builder" -msgstr "" - -#: ../objectstorage_components.rst:57 -msgid "Rings" -msgstr "" - -#: ../identity_concepts.rst:66 -msgid "Role" -msgstr "" - -#: ../telemetry-measurements.rst:896 -msgid "Role is added to an actor on a target" -msgstr "" - -#: ../telemetry-measurements.rst:870 -msgid "Role is created" -msgstr "" - -#: ../telemetry-measurements.rst:873 -msgid "Role is deleted" -msgstr "" - -#: ../telemetry-measurements.rst:900 -msgid "Role is removed from an actor on a target" -msgstr "" - -#: ../telemetry-measurements.rst:876 -msgid "Role is updated" -msgstr "" - -#: ../compute_arch.rst:105 -msgid "" -"Roles control the actions a user is allowed to perform. By default, most " -"actions do not require a particular role, but you can configure them by " -"editing the :file:`policy.json` file for user roles. For example, a rule can " -"be defined so that a user must have the ``admin`` role in order to be able " -"to allocate a public IP address." -msgstr "" - -#: ../compute-root-wrap-reference.rst:7 -msgid "" -"Rootwrap allows unprivileged users to safely run Compute actions as the root " -"user. Compute previously used :command:`sudo` for this purpose, but this was " -"difficult to maintain, and did not allow advanced filters. The :command:" -"`rootwrap` command replaces :command:`sudo` for Compute." -msgstr "" - -#: ../compute-root-wrap-reference.rst:44 -msgid "" -"Rootwrap is configured using the :file:`rootwrap.conf` file. Because it's in " -"the trusted security path, it must be owned and writable by only the root " -"user. The file's location is specified in both the sudoers entry and in the :" -"file:`nova.conf` configuration file with the ``rootwrap_config=entry`` " -"parameter." -msgstr "" - -#: ../compute-root-wrap-reference.rst:32 -msgid "" -"Rootwrap is fully controlled by the root user. The root user owns the " -"sudoers entry which allows Compute to run a specific rootwrap executable as " -"root, and only with a specific configuration file (which should also be " -"owned by root). The :command:`nova-rootwrap` command imports the Python " -"modules it needs from a cleaned, system-default PYTHONPATH. The root-owned " -"configuration file points to root-owned filter definition directories, which " -"contain root-owned filters definition files. This chain ensures that the " -"Compute user itself is not in control of the configuration or modules used " -"by the :command:`nova-rootwrap` executable." -msgstr "" - -#: ../networking_introduction.rst:111 -msgid "Rotates requests evenly between multiple instances." -msgstr "" - -#: ../networking_introduction.rst:111 -msgid "Round robin" -msgstr "" - -#: ../networking_adv-features.rst:679 -msgid "Router rule attributes" -msgstr "" - -#: ../networking_adv-features.rst:729 -msgid "" -"Router rules are configured with a router update operation in OpenStack " -"Networking. The update overrides any previous rules so all rules must be " -"provided at the same time." -msgstr "" - -#: ../compute-manage-logs.rst:88 -msgid "Rsyslog" -msgstr "" - -#: ../networking_multi-dhcp-agents.rst:448 -msgid "Run ``udhcpc`` in the VM; it cannot get the wanted IP." -msgstr "" - -#: ../networking_multi-dhcp-agents.rst:444 -msgid "Run a DHCP client in VM to see if it can get the wanted IP." -msgstr "" - -#: ../compute_arch.rst:339 -msgid "Run instances" -msgstr "" - -#: ../compute-node-down.rst:138 -msgid "" -"Run the :command:`find` command to verify that all files use the correct " -"identifiers." -msgstr "" - -#: ../blockstorage_backup_disks.rst:72 -msgid "Run the :command:`lvdisplay` command again to verify the snapshot::" -msgstr "" - -#: ../ts_multipath_warn.rst:25 -msgid "" -"Run the following command on the compute node to install the ``multipath-" -"tools`` packages." -msgstr "" - -#: ../ts-failed-attach-vol-no-sysfsutils.rst:26 -msgid "" -"Run the following command on the compute node to install the ``sysfsutils`` " -"packages::" -msgstr "" - -#: ../compute-networking-nova.rst:543 -msgid "" -"Run these commands as root only if the credentials used to interact with " -"nova-api are in :file:`/root/.bashrc`. If the EC2 credentials in the :file:`." -"bashrc` file are for an unprivileged user, you must run these commands as " -"that user instead." -msgstr "" - -#: ../ts_vol_attach_miss_sg_scan.rst:25 -msgid "Run this command on the compute node to install the sg3-utils package:" -msgstr "" - -#: ../blockstorage_volume_backups.rst:15 -msgid "Run this command to create a backup of a volume::" -msgstr "" - -#: ../blockstorage_backup_disks.rst:180 -msgid "" -"Run this command to run a checksum for your file and save the result to a " -"file::" -msgstr "" - -#: ../compute-manage-the-cloud.rst:62 -msgid "" -"Running :command:`nova help` returns a list of ``nova`` commands and " -"parameters. To get help for a subcommand, run:" -msgstr "" - -#: ../telemetry-data-collection.rst:229 -msgid "Running ceilometer-agent-central is exactly the same as::" -msgstr "" - -#: ../telemetry-data-collection.rst:224 -msgid "Running ceilometer-agent-compute is exactly the same as::" -msgstr "" - -#: ../telemetry-data-collection.rst:234 -msgid "Running ceilometer-agent-ipmi is exactly the same as::" -msgstr "" - -#: ../networking_multi-dhcp-agents.rst:47 -msgid "Runs ``nova-compute``, the Neutron L2 agent and DHCP agent" -msgstr "" - -#: ../networking_arch.rst:32 -msgid "" -"Runs on each hypervisor to perform local vSwitch configuration. The agent " -"that runs, depends on the plug-in that you use. Certain plug-ins do not " -"require an agent." -msgstr "" - -#: ../networking_multi-dhcp-agents.rst:42 -msgid "" -"Runs the Networking, Identity, and Compute services that are required to " -"deploy VMs. The node must have at least one network interface that is " -"connected to the Management Network. Note that ``nova-network`` should not " -"be running because it is replaced by Neutron." -msgstr "" - -#: ../compute-images-instances.rst:136 -msgid "S3" -msgstr "" - -#: ../telemetry-system-architecture.rst:158 -msgid "SDN controller meters:" -msgstr "" - -#: ../telemetry-measurements.rst:969 -msgid "SDN controllers" -msgstr "" - -#: ../identity_troubleshoot.rst:120 -msgid "" -"SELinux troubles often occur when you use Fedora or RHEL-based packages and " -"you choose configuration options that do not match the standard policy. Run " -"the ``setenforce permissive`` command. If that makes a difference, you " -"should relabel the directory. If you are using a sub-directory of the ``/var/" -"cache/`` directory, run the following command:" -msgstr "" - -#: ../blockstorage_nfs_backend.rst:45 -msgid "SHARE is the absolute path to an existing and accessible NFS share." -msgstr "" - -#: ../telemetry-measurements.rst:581 -msgid "SNMP based meters" -msgstr "" - -#: ../compute-remote-console-access.rst:10 -msgid "SPICE console" -msgstr "" - -#: ../compute-remote-console-access.rst:18 -msgid "" -"SPICE support in OpenStack Compute shares a similar architecture to the VNC " -"implementation. The OpenStack dashboard uses a SPICE-HTML5 widget in its " -"console tab that communicates to the ``nova-spicehtml5proxy`` service by " -"using SPICE-over-websockets. The ``nova-spicehtml5proxy`` service " -"communicates directly with the hypervisor process by using SPICE." -msgstr "" - -#: ../telemetry-data-collection.rst:1015 -msgid "SQL-based back ends" -msgstr "" - -#: ../compute-configuring-migrations.rst:225 -msgid "SSH tunnel to libvirtd's UNIX socket" -msgstr "" - -#: ../compute-networking-nova.rst:768 -msgid "SSL Configurations (VIPs)" -msgstr "" - -# #-#-#-#-# blockstorage_glusterfs_backend.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -# #-#-#-#-# blockstorage_nfs_backend.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -#: ../blockstorage_glusterfs_backend.rst:22 -#: ../blockstorage_glusterfs_backend.rst:143 -#: ../blockstorage_nfs_backend.rst:22 ../blockstorage_nfs_backend.rst:81 -msgid "SUSE Linux Enterprise" -msgstr "" - -#: ../networking_multi-dhcp-agents.rst:49 -msgid "Same as HostA" -msgstr "" - -#: ../telemetry-data-collection.rst:701 -msgid "Sample configuration::" -msgstr "" - -#: ../telemetry-data-retrieval.rst:234 -msgid "" -"Samples are collected for each meter that is present in the list of meters, " -"except in case of instances that are not running or deleted from the " -"OpenStack Compute database. If an instance is no more existing and there is " -"``time_to_live`` value is set in the :file:`ceilometer.conf` configuration " -"file, then a group of samples are deleted in each expiration cycle. When the " -"last sample is deleted for a meter, the database can be cleaned up by " -"running ceilometer-expirer and the meter will not be present in the list " -"above anymore. For more information about the expiration procedure see :ref:" -"`telemetry-storing-samples`." -msgstr "" - -#: ../telemetry-data-collection.rst:19 -msgid "" -"Samples can have various sources regarding to the needs and configuration of " -"Telemetry, which requires multiple methods to collect data." -msgstr "" - -#: ../compute-default-ports.rst:26 -msgid "" -"Save the changes to :file:`/etc/sysconfig/iptables` file, and restart the " -"iptables service to pick up the changes:" -msgstr "" - -#: ../compute-node-down.rst:180 -msgid "" -"Save the current state of the database, the current state of the running " -"instances, and the attached volumes (mount point, volume ID, volume status, " -"etc), at least from the cloud controller to the compute node." -msgstr "" - -#: ../compute-networking-nova.rst:668 -msgid "Save the file and run this command to apply the changes:" -msgstr "" - -#: ../compute-networking-nova.rst:737 -msgid "Save the file, and restart ``nova-network``" -msgstr "" - -#: ../compute-security.rst:94 -msgid "" -"Save the file, and restart the nova-compute and nova-scheduler services to " -"pick up the changes." -msgstr "" - -#: ../networking_multi-dhcp-agents.rst:3 -msgid "Scalable and highly available DHCP agents" -msgstr "" - -#: ../objectstorage_features.rst:19 -msgid "" -"Scale-out architecture: Scale vertically and horizontally-distributed " -"storage. Backs up and archives large amounts of data with linear performance." -msgstr "" - -#: ../index.rst:37 -msgid "Search in this guide" -msgstr "" - -#: ../networking_use.rst:195 -msgid "" -"Searches for ports with a ``device_id`` that matches the Compute instance " -"UUID. See :ref: `Create and delete VMs`" -msgstr "" - -#: ../networking_use.rst:202 -msgid "Searches for ports, but shows onlythe ``mac_address`` of the port." -msgstr "" - -#: ../keystone_secure_identity_to_ldap_backend.rst:2 -msgid "Secure the OpenStack Identity service connection to an LDAP back end" -msgstr "" - -#: ../compute-root-wrap-reference.rst:5 -msgid "Secure with rootwrap" -msgstr "" - -#: ../cross_project_cors.rst:98 -msgid "Security concerns" -msgstr "" - -#: ../networking_adv-features.rst:306 -msgid "Security groups" -msgstr "" - -#: ../networking_adv-features.rst:308 -msgid "" -"Security groups and security group rules allows administrators and tenants " -"the ability to specify the type of traffic and direction (ingress/egress) " -"that is allowed to pass through a port. A security group is a container for " -"security group rules." -msgstr "" - -#: ../compute-security.rst:5 -msgid "Security hardening" -msgstr "" - -#: ../networking_adv-operational-features.rst:17 -msgid "" -"See `Python logging how-to `__ to " -"learn more about logging." -msgstr "" - -#: ../dashboard_sessions.rst:204 -msgid "" -"See the Django `cookie-based sessions `__ documentation." -msgstr "" - -#: ../networking_config-agents.rst:520 -msgid "" -"See the `OpenStack Command-Line Interface Reference `__ for more information on Networking " -"commands." -msgstr "" - -#: ../objectstorage-admin.rst:10 -msgid "" -"See the `OpenStack Configuration Reference `__ for a list of configuration options for Object " -"Storage." -msgstr "" - -#: ../compute-live-migration-usage.rst:98 -msgid "" -"Select the compute node the instance will be migrated to. In this example, " -"we will migrate the instance to ``HostC``, because nova-compute is running " -"on it:" -msgstr "" - -#: ../networking_config-agents.rst:373 -msgid "" -"Select the required driver in the :file:`/etc/neutron/lbaas_agent.ini` file:" -msgstr "" - -#: ../objectstorage_features.rst:14 -msgid "Self-healing, reliable, data redundancy protects from failures." -msgstr "" - -#: ../telemetry-data-collection.rst:422 -msgid "Send samples to Telemetry" -msgstr "" - -#: ../telemetry-measurements.rst:633 -msgid "Sending error o\\ f network inter\\ face" -msgstr "" - -#: ../objectstorage_features.rst:59 -msgid "Separate endpoint and API for integration with other compute systems." -msgstr "" - -#: ../networking_introduction.rst:239 -msgid "" -"Separate firewall rule IDs or names with spaces. The order in which you " -"specify the rules is important." -msgstr "" - -#: ../compute-manage-logs.rst:127 -msgid "Serial console" -msgstr "" - -#: ../objectstorage-troubleshoot.rst:29 -msgid "Server failure" -msgstr "" - -#: ../identity_concepts.rst:72 -msgid "Service" -msgstr "" - -#: ../identity_concepts.rst:305 -msgid "Service management" -msgstr "" - -#: ../compute-networking-nova.rst:770 -msgid "Services failover/HA" -msgstr "" - -#: ../blockstorage_glusterfs_backend.rst:112 -msgid "" -"Set :file:`/etc/cinder/glusterfs` to be owned by the root user and the " -"``cinder`` group::" -msgstr "" - -#: ../blockstorage_glusterfs_backend.rst:117 -msgid "" -"Set :file:`/etc/cinder/glusterfs` to be readable by members of the " -"``cinder`` group::" -msgstr "" - -#: ../blockstorage_nfs_backend.rst:49 -msgid "" -"Set :file:`/etc/cinder/nfsshares` to be owned by the ``root`` user and the " -"``cinder`` group::" -msgstr "" - -#: ../blockstorage_nfs_backend.rst:54 -msgid "" -"Set :file:`/etc/cinder/nfsshares` to be readable by members of the cinder " -"group::" -msgstr "" - -#: ../identity_troubleshoot.rst:133 -msgid "" -"Set back to ``setenforce enforcing`` to confirm that your changes solve the " -"problem." -msgstr "" - -#: ../blockstorage_glusterfs_backend.rst:47 -msgid "" -"Set each Gluster volume to use the same UID and GID as the ``cinder`` user::" -msgstr "" - -#: ../compute-networking-nova.rst:285 -msgid "" -"Set the IPv6 global routing prefix by using the ``--fixed_range_v6`` " -"parameter. The default value for the parameter is ``fd00::/48``." -msgstr "" - -#: ../compute-node-down.rst:115 -msgid "" -"Set the ``libvirt-qemu`` UID in :file:`/etc/passwd` to the same number on " -"all hosts (for example, 119)." -msgstr "" - -#: ../compute-node-down.rst:121 -msgid "" -"Set the ``libvirtd`` group in :file:`/etc/group` file to the same number on " -"all hosts (for example, 119)." -msgstr "" - -#: ../compute-node-down.rst:118 -msgid "" -"Set the ``nova`` group in :file:`/etc/group` file to the same number on all " -"hosts (for example, 120)." -msgstr "" - -#: ../networking_config-agents.rst:305 -msgid "" -"Set the ``service_plugins`` option in the :file:`/etc/neutron/neutron.conf` " -"file on the host that runs neutron-server:" -msgstr "" - -#: ../keystone_integrate_identity_backend_ldap.rst:78 -msgid "" -"Set the following options in the :file:`/etc/keystone/keystone.conf` file:" -msgstr "" - -#: ../compute-node-down.rst:107 -msgid "" -"Set the nova UID in :file:`/etc/passwd` to the same number on all hosts (for " -"example, 112)." -msgstr "" - -#: ../compute-manage-the-cloud.rst:72 -msgid "" -"Set the required parameters as environment variables to make running " -"commands easier. For example, you can add :option:`--os-username` as a " -"``nova`` option, or set it as an environment variable. To set the user name, " -"password, and tenant as environment variables, use:" -msgstr "" - -#: ../objectstorage_tenant_specific_image_storage.rst:20 -msgid "Set these configuration options in the :file:`glance-api.conf` file:" -msgstr "" - -#: ../keystone_integrate_assignment_backend_ldap.rst:90 -msgid "" -"Set these options in the :file:`/etc/keystone/keystone.conf` file for a " -"single LDAP server, or :file:`/etc/keystone/domains/keystone.DOMAIN_NAME." -"conf` files for multiple back ends." -msgstr "" - -# #-#-#-#-# keystone_integrate_identity_backend_ldap.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -# #-#-#-#-# keystone_integrate_with_ldap.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -#: ../keystone_integrate_identity_backend_ldap.rst:182 -#: ../keystone_integrate_with_ldap.rst:83 -msgid "" -"Set these options in the :file:`/etc/keystone/keystone.conf` file for a " -"single LDAP server, or :file:`/etc/keystone/domains/keystone.DOMAIN_NAME." -"conf` files for multiple back ends. Example configurations appear below each " -"setting summary:" -msgstr "" - -#: ../networking_introduction.rst:72 -msgid "Set these options to configure SSL:" -msgstr "" - -#: ../database.rst:191 -msgid "Set this to either 1 or 0:" -msgstr "" - -#: ../objectstorage_tenant_specific_image_storage.rst:23 -msgid "" -"Set to ``True`` to enable tenant-specific storage locations. Default is " -"``False``." -msgstr "" - -#: ../dashboard_sessions.rst:6 -msgid "Set up session storage for the dashboard" -msgstr "" - -#: ../database.rst:311 -msgid "Setting" -msgstr "" - -#: ../blockstorage_glusterfs_backend.rst:179 -msgid "" -"Setting ``glusterfs_sparsed_volumes`` to false will result in volumes being " -"fully allocated at the time of creation. This leads to increased delays in " -"volume creation." -msgstr "" - -#: ../blockstorage_nfs_backend.rst:132 -msgid "" -"Setting ``nfs_sparsed_volumes`` to ``false`` will result in volumes being " -"fully allocated at the time of creation. This leads to increased delays in " -"volume creation." -msgstr "" - -# #-#-#-#-# keystone_integrate_assignment_backend_ldap.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -# #-#-#-#-# keystone_integrate_identity_backend_ldap.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -#: ../keystone_integrate_assignment_backend_ldap.rst:114 -#: ../keystone_integrate_identity_backend_ldap.rst:202 -msgid "Setting attribute ignore to list of attributes stripped off on update." -msgstr "" - -#: ../networking_adv-operational-features.rst:71 -msgid "Setting cases" -msgstr "" - -#: ../telemetry-data-retrieval.rst:60 -msgid "" -"Several fields of the API endpoints accept shorter names than the ones " -"defined in the reference. The API will do the transformation internally and " -"return the output with the fields that are listed in the `API reference " -"`__. The " -"fields are the following:" -msgstr "" - -#: ../networking_adv-features.rst:5 -msgid "" -"Several plug-ins implement API extensions that provide capabilities similar " -"to what was available in nova-network. These plug-ins are likely to be of " -"interest to the OpenStack community." -msgstr "" - -#: ../compute-configuring-migrations.rst:59 -#: ../compute-configuring-migrations.rst:331 -msgid "Shared storage" -msgstr "" - -#: ../compute-images-instances.rst:147 -msgid "Sheepdog" -msgstr "" - -#: ../blockstorage-consistency-groups.rst:75 -msgid "Show a consistency group." -msgstr "" - -#: ../blockstorage-consistency-groups.rst:84 -msgid "Show a snapshot of a consistency group." -msgstr "" - -#: ../networking_multi-dhcp-agents.rst:241 -msgid "Show agent details." -msgstr "" - -#: ../compute-manage-volumes.rst:34 -msgid "Show details about a snapshot." -msgstr "" - -#: ../compute-manage-volumes.rst:26 -msgid "Show details about a volume." -msgstr "" - -#: ../networking_config-agents.rst:498 -msgid "Show information of a given agent." -msgstr "" - -#: ../networking_adv-features.rst:249 -msgid "Shows all internal interfaces for a router." -msgstr "" - -#: ../networking_adv-features.rst:820 -msgid "Shows information for a specified label rule." -msgstr "" - -#: ../networking_adv-features.rst:793 -msgid "Shows information for a specified label." -msgstr "" - -#: ../networking_use.rst:74 -msgid "Shows information for a specified port." -msgstr "" - -#: ../networking_adv-features.rst:245 -msgid "Shows information for a specified router." -msgstr "" - -#: ../keystone_certificates_for_pki.rst:102 -msgid "Sign certificate issued by external CA" -msgstr "" - -#: ../keystone_certificates_for_pki.rst:222 -msgid "" -"Sign the new certificate with the existing CA to generate a new " -"``signing_cert``." -msgstr "" - -#: ../telemetry-data-retrieval.rst:395 -msgid "" -"Similar to querying meters, additional filter parameters can be given to " -"retrieve specific events:" -msgstr "" - -#: ../telemetry-data-retrieval.rst:198 -msgid "" -"Similarly to other OpenStack command line clients, the ``ceilometer`` client " -"uses OpenStack Identity for authentication. The proper credentials and ``--" -"auth_url`` parameter have to be defined via command line parameters or " -"environment variables." -msgstr "" - -#: ../telemetry-data-collection.rst:627 -msgid "Similarly, the event pipeline definition looks like the following::" -msgstr "" - -#: ../keystone_caching_layer.rst:31 -msgid "" -"Since the Juno release, the default setting is enabled for subsystem " -"caching, but the global toggle is disabled. As a result, no caching in " -"available unless the global toggle for ``[cache]`` is enabled by setting the " -"value to ``true``." -msgstr "" - -#: ../compute-configuring-migrations.rst:315 -msgid "" -"Since the ephemeral drives are copied over the network in block migration, " -"migrations of instances with heavy I/O loads may never complete if the " -"drives are writing faster than the data can be copied over the network." -msgstr "" - -#: ../objectstorage_arch.rst:35 -msgid "" -"Since this is an HTTP addressable storage service, you may incorporate a " -"load balancer into the access tier." -msgstr "" - -#: ../networking_introduction.rst:333 -msgid "Site-to-site VPN that connects two private networks." -msgstr "" - -#: ../ts-eql-volume-size.rst:110 -msgid "Size" -msgstr "" - -#: ../telemetry-measurements.rst:161 -msgid "Size of ephemeral disk" -msgstr "" - -#: ../telemetry-measurements.rst:158 -msgid "Size of root disk" -msgstr "" - -#: ../telemetry-measurements.rst:712 -msgid "Size of the sna\\ pshot" -msgstr "" - -#: ../telemetry-measurements.rst:672 -msgid "Size of the upl\\ oaded image" -msgstr "" - -#: ../telemetry-measurements.rst:704 -msgid "Size of the vol\\ ume" -msgstr "" - -#: ../objectstorage_features.rst:56 -msgid "Snapshot and backup API for block volumes." -msgstr "" - -#: ../keystone_caching_layer.rst:15 -msgid "" -"So to enable only the token back end caching, set the values as follows:" -msgstr "" - -#: ../objectstorage_ringbuilder.rst:41 -msgid "" -"So, to create a list of device dictionaries assigned to a partition, the " -"Python code would look like::" -msgstr "" - -# #-#-#-#-# ts-duplicate-3par-host.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -# #-#-#-#-# ts-eql-volume-size.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -# #-#-#-#-# ts-failed-attach-vol-after-detach.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -# #-#-#-#-# ts-failed-attach-vol-no-sysfsutils.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -# #-#-#-#-# ts-failed-connect-vol-FC-SAN.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -# #-#-#-#-# ts-HTTP-bad-req-in-cinder-vol-log.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -# #-#-#-#-# ts_multipath_warn.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -# #-#-#-#-# ts_no_emulator_x86_64.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -# #-#-#-#-# ts_non_existent_host.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -# #-#-#-#-# ts_non_existent_vlun.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -# #-#-#-#-# ts_vol_attach_miss_sg_scan.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -#: ../ts-duplicate-3par-host.rst:21 ../ts-eql-volume-size.rst:135 -#: ../ts-failed-attach-vol-after-detach.rst:14 -#: ../ts-failed-attach-vol-no-sysfsutils.rst:24 -#: ../ts-failed-connect-vol-FC-SAN.rst:27 -#: ../ts-HTTP-bad-req-in-cinder-vol-log.rst:44 ../ts_multipath_warn.rst:23 -#: ../ts_no_emulator_x86_64.rst:12 ../ts_non_existent_host.rst:19 -#: ../ts_non_existent_vlun.rst:18 ../ts_vol_attach_miss_sg_scan.rst:22 -msgid "Solution" -msgstr "" - -#: ../blockstorage_ratelimit_volume_copy_bandwidth.rst:49 -msgid "" -"Some back ends which use remote file systems such as NFS are not supported " -"by this feature." -msgstr "" - -#: ../compute-images-instances.rst:81 -msgid "" -"Some details in this example scenario might be different in your " -"environment. For example, you might use a different type of back-end " -"storage, or different network protocols. One common variant is that the " -"ephemeral storage used for volumes ``vda`` and ``vdb`` could be backed by " -"network storage rather than a local disk." -msgstr "" - -#: ../compute-node-down.rst:234 -msgid "" -"Some instances will completely reboot and become reachable, while some might " -"stop at the plymouth stage. This is expected behavior, DO NOT reboot a " -"second time." -msgstr "" - -#: ../compute-system-admin.rst:84 -msgid "" -"Some services have drivers that change how the service implements its core " -"functionality. For example, the nova-compute service supports drivers that " -"let you choose which hypervisor type it can use. nova-network and nova-" -"scheduler also have drivers." -msgstr "" - -#: ../telemetry-data-collection.rst:154 -msgid "" -"Some services require additional configuration to emit the notifications " -"using the correct control exchange on the message queue and so forth. These " -"configuration needs are referred in the above table for each OpenStack " -"service that needs it." -msgstr "" - -#: ../compute-node-down.rst:293 -msgid "" -"Some systems hang on that step, which means you could lose access to your " -"cloud-controller. To re-run the session manually, run this command before " -"performing the mount:" -msgstr "" - -#: ../networking_introduction.rst:115 -msgid "Source IP" -msgstr "" - -#: ../networking_config-identity.rst:20 -msgid "Source the :file:`.bashrc` file:" -msgstr "" - -#: ../telemetry-data-collection.rst:159 -msgid "" -"Specific notifications from the Compute service are important for " -"administrators and users. Configuring nova_notifications in the :file:`nova." -"conf` file allows administrators to respond to events rapidly. For more " -"information on configuring notifications for the compute service, see " -"`Chapter 11 on Telemetry services `__ in the OpenStack " -"Installation Guide." -msgstr "" - -#: ../networking_use.rst:149 -msgid "Specified set of host routes." -msgstr "" - -#: ../compute-remote-console-access.rst:237 -msgid "" -"Specifies the address on which the VNC service should bind. Make sure it is " -"assigned one of the compute node interfaces. This address is the one used by " -"your domain file." -msgstr "" - -#: ../telemetry-data-retrieval.rst:328 -msgid "Specifies the maximum number of samples to return." -msgstr "" - -#: ../compute-flavors.rst:50 -msgid "" -"Specifies the size of a secondary ephemeral data disk. This is an empty, " -"unformatted disk and exists only for the life o\\ f the instance." -msgstr "" - -#: ../objectstorage_tenant_specific_image_storage.rst:27 -msgid "" -"Specify a list of tenant IDs that can grant read and write access to all " -"Object Storage containers that are created by the Image service." -msgstr "" - -#: ../networking_adv-features.rst:742 -msgid "Specify alternate next-hop addresses for a specific subnet:" -msgstr "" - -#: ../keystone_use_trusts.rst:38 -msgid "Specify one of the following values:" -msgstr "" - -#: ../compute-security.rst:57 -msgid "" -"Specify the connection information for your attestation service by adding " -"these lines to the ``trusted_computing`` section of the :file:`/etc/nova/" -"nova.conf` file:" -msgstr "" - -#: ../compute-security.rst:162 -msgid "Specify the path to the client certificate::" -msgstr "" - -#: ../compute-security.rst:166 -msgid "Specify the path to the private key::" -msgstr "" - -#: ../keystone_secure_identity_to_ldap_backend.rst:32 -msgid "" -"Specify what client certificate checks to perform on incoming TLS sessions " -"from the LDAP server. To do so, set the ``tls_req_cert`` configuration key " -"in the ``[ldap]`` section to ``demand``, ``allow``, or ``never``:" -msgstr "" - -#: ../compute-remote-console-access.rst:35 -msgid "Spice configuration option = Default value" -msgstr "" - -#: ../orchestration-auth-model.rst:46 -msgid "Stack creation is completed." -msgstr "" - -#: ../orchestration-stack-domain-users.rst:7 -msgid "Stack domain users" -msgstr "" - -#: ../orchestration-stack-domain-users.rst:41 -msgid "Stack domain users configuration" -msgstr "" - -#: ../telemetry-measurements.rst:1257 -msgid "Stack was success\\ fully created" -msgstr "" - -#: ../telemetry-measurements.rst:1263 -msgid "Stack was success\\ fully deleted" -msgstr "" - -#: ../telemetry-measurements.rst:1266 -msgid "Stack was success\\ fully resumed" -msgstr "" - -#: ../telemetry-measurements.rst:1269 -msgid "Stack was success\\ fully suspended" -msgstr "" - -#: ../telemetry-measurements.rst:1260 -msgid "Stack was success\\ fully updated" -msgstr "" - -#: ../objectstorage_features.rst:58 -msgid "Standalone volume API available" -msgstr "" - -#: ../telemetry-data-retrieval.rst:170 -msgid "Standard deviation of the sample volumes in each period." -msgstr "" - -#: ../networking_multi-dhcp-agents.rst:450 -msgid "Start DHCP agent on HostB. The VM gets the wanted IP again." -msgstr "" - -#: ../objectstorage-troubleshoot.rst:120 -msgid "Start copying the data we have in the ring into the builder:" -msgstr "" - -#: ../identity_start.rst:2 -msgid "Start the Identity services" -msgstr "" - -#: ../networking_config-agents.rst:478 -msgid "Start the OpenStack Networking Hyper-V agent:" -msgstr "" - -#: ../dashboard_sessions.rst:98 -msgid "Start the mysql command-line client::" -msgstr "" - -#: ../networking_adv-features.rst:578 -msgid "" -"Starting with the Havana release, the VMware NSX plug-in provides an " -"asynchronous mechanism for retrieving the operational status for neutron " -"resources from the NSX back-end; this applies to *network*, *port*, and " -"*router* resources." -msgstr "" - -#: ../identity_concepts.rst:320 -msgid "" -"Starts both the service and administrative APIs in a single process. Using " -"federation with keystone-all is not supported. keystone-all is deprecated in " -"favor of the WSGI service." -msgstr "" - -#: ../compute-live-migration-usage.rst:110 -msgid "State" -msgstr "" - -#: ../telemetry-data-retrieval.rst:133 -msgid "Statistics" -msgstr "" - -#: ../objectstorage-monitoring.rst:124 -msgid "" -"StatsD (see http://codeascraft.etsy.com/2011/02/15/measure-anything-measure-" -"everything/) was designed for application code to be deeply instrumented; " -"meters are sent in real-time by the code that just noticed or did something. " -"The overhead of sending a meter is extremely low: a ``sendto`` of one UDP " -"packet. If that overhead is still too high, the StatsD client library can " -"send only a random portion of samples and StatsD approximates the actual " -"number when flushing meters upstream." -msgstr "" - -#: ../objectstorage-monitoring.rst:93 -msgid "Statsdlog" -msgstr "" - -# #-#-#-#-# compute-live-migration-usage.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -# #-#-#-#-# ts-eql-volume-size.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -#: ../compute-live-migration-usage.rst:36 -#: ../compute-live-migration-usage.rst:109 ../ts-eql-volume-size.rst:110 -msgid "Status" -msgstr "" - -#: ../blockstorage-driver-filter-weighing.rst:171 -msgid "Status for the requested volume" -msgstr "" - -#: ../networking_multi-dhcp-agents.rst:441 -msgid "" -"Stop the DHCP agent on HostA. Besides stopping the ``neutron-dhcp-agent`` " -"binary, you must stop the ``dnsmasq`` processes." -msgstr "" - -#: ../networking_multi-dhcp-agents.rst:446 -msgid "Stop the DHCP agent on HostB too." -msgstr "" - -#: ../compute-node-down.rst:124 -msgid "Stop the services on the compute node." -msgstr "" - -#: ../blockstorage_volume_migration.rst:143 -msgid "" -"Stopping the cinder volume service will prevent volumes from being allocated " -"to the node." -msgstr "" - -#: ../objectstorage_arch.rst:55 -msgid "Storage nodes" -msgstr "" - -#: ../compute-images-instances.rst:143 -msgid "" -"Stores images inside of a Ceph storage cluster using Ceph's RBD interface." -msgstr "" - -#: ../compute-images-instances.rst:150 -msgid "Stores images using MongoDB." -msgstr "" - -#: ../telemetry-data-collection.rst:956 -msgid "Storing samples" -msgstr "" - -#: ../networking_adv-features.rst:132 ../networking_adv-features.rst:143 -msgid "String" -msgstr "" - -#: ../telemetry-data-retrieval.rst:173 -msgid "Sum of the sample volumes over each period." -msgstr "" - -#: ../telemetry-measurements.rst:97 -msgid "Support" -msgstr "" - -#: ../telemetry-data-collection.rst:320 -msgid "Support for HA deployment of the central and compute agent services" -msgstr "" - -#: ../objectstorage_features.rst:53 -msgid "Support for NetApp, Nexenta, Solidfire" -msgstr "" - -#: ../telemetry-system-architecture.rst:73 -msgid "Supported databases" -msgstr "" - -#: ../telemetry-system-architecture.rst:107 -msgid "Supported hypervisors" -msgstr "" - -#: ../telemetry-system-architecture.rst:143 -msgid "Supported networking services" -msgstr "" - -#: ../blockstorage-driver-filter-weighing.rst:95 -msgid "Supported operations in filter and goodness functions" -msgstr "" - -#: ../objectstorage_features.rst:49 -msgid "Supports S3 API" -msgstr "" - -#: ../compute-flavors.rst:54 -msgid "Swap" -msgstr "" - -#: ../objectstorage-monitoring.rst:22 -msgid "Swift Recon" -msgstr "" - -#: ../objectstorage-monitoring.rst:39 -msgid "" -"Swift Recon is middleware that is installed in the object servers pipeline " -"and takes one required option: A local cache directory. To track " -"``async_pendings``, you must set up an additional cron job for each object " -"server. You access data by either sending HTTP requests directly to the " -"object server or using the ``swift-recon`` command-line client." -msgstr "" - -#: ../objectstorage-monitoring.rst:122 -msgid "Swift StatsD logging" -msgstr "" - -#: ../objectstorage-monitoring.rst:56 -msgid "Swift-Informant" -msgstr "" - -#: ../keystone_certificates_for_pki.rst:213 -msgid "Switching out expired signing certificates" -msgstr "" - -#: ../blockstorage-driver-filter-weighing.rst:118 -msgid "" -"Syntax errors in filter or goodness strings defined by you will cause errors " -"to be thrown at volume request time." -msgstr "" - -#: ../compute-manage-logs.rst:45 -msgid "Syslog" -msgstr "" - -#: ../objectstorage-troubleshoot.rst:70 -msgid "Syslog log facility" -msgstr "" - -#: ../compute-system-admin.rst:5 -msgid "System administration" -msgstr "" - -#: ../objectstorage-admin.rst:3 -msgid "System administration for Object Storage" -msgstr "" - -#: ../compute-manage-the-cloud.rst:12 -msgid "" -"System administrators can use :command:`nova` client and :command:" -"`euca2ools` commands to manage their clouds." -msgstr "" - -# #-#-#-#-# baremetal.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -# #-#-#-#-# compute_arch.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -# #-#-#-#-# telemetry-system-architecture.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -#: ../baremetal.rst:26 ../compute_arch.rst:3 -#: ../telemetry-system-architecture.rst:5 -msgid "System architecture" -msgstr "" - -#: ../objectstorage_components.rst:185 -msgid "" -"System replicators and object uploads/downloads operate on partitions. As " -"the system scales up, its behavior continues to be predictable because the " -"number of partitions is a fixed number." -msgstr "" - -#: ../telemetry-data-collection.rst:1009 -msgid "TTL value support" -msgstr "" - -#: ../telemetry-measurements.rst:1306 -msgid "Table was succe\\ ssfully created" -msgstr "" - -#: ../telemetry-measurements.rst:1309 -msgid "Table was succe\\ ssfully deleted" -msgstr "" - -#: ../database.rst:279 -msgid "" -"Take the ID of the MySQL datastore and pass it in with the :command:" -"`datastore-version-list` command::" -msgstr "" - -#: ../telemetry.rst:5 -msgid "Telemetry" -msgstr "" - -#: ../telemetry-best-practices.rst:2 -msgid "Telemetry best practices" -msgstr "" - -#: ../telemetry-measurements.rst:469 -msgid "" -"Telemetry captures notifications that are emitted by the Bare metal service. " -"The source of the notifications are IPMI sensors that collect data from the " -"host machine." -msgstr "" - -#: ../telemetry-measurements.rst:11 -msgid "" -"Telemetry collects meters by polling the infrastructure elements and also by " -"consuming the notifications emitted by other OpenStack services. For more " -"information about the polling mechanism and notifications see :ref:" -"`telemetry-data-collection`. There are several meters which are collected by " -"polling and by consuming. The origin for each meter is listed in the tables " -"below." -msgstr "" - -#: ../telemetry-data-retrieval.rst:179 -msgid "Telemetry command line client and SDK" -msgstr "" - -#: ../telemetry-system-architecture.rst:145 -msgid "" -"Telemetry is able to retrieve information from OpenStack Networking and " -"external networking services:" -msgstr "" - -#: ../telemetry-data-collection.rst:189 -msgid "Telemetry middleware" -msgstr "" - -#: ../telemetry-data-collection.rst:190 -msgid "" -"Telemetry provides the capability of counting the HTTP requests and " -"responses for each API endpoint in OpenStack. This is achieved by storing a " -"sample for each event marked as ``audit.http.request``, ``audit.http." -"response``, ``http.request`` or ``http.response``." -msgstr "" - -#: ../telemetry-measurements.rst:43 -msgid "" -"Telemetry provides the possibility to store metadata for samples. This " -"metadata can be extended for OpenStack Compute and OpenStack Object Storage." -msgstr "" - -#: ../telemetry-data-retrieval.rst:438 -msgid "Telemetry python bindings" -msgstr "" - -#: ../telemetry-data-collection.rst:315 -msgid "Telemetry supports Libvirt, which hides the hypervisor under it." -msgstr "" - -#: ../telemetry-measurements.rst:582 -msgid "" -"Telemetry supports gathering SNMP based generic host meters. In order to be " -"able to collect this data you need to run smpd on each target host." -msgstr "" - -#: ../telemetry-data-retrieval.rst:140 -msgid "Telemetry supports the following statistics and aggregation functions:" -msgstr "" - -#: ../telemetry-measurements.rst:28 -msgid "Telemetry uses the following meter types:" -msgstr "" - -#: ../telemetry-data-retrieval.rst:18 -msgid "Telemetry v2 API" -msgstr "" - -#: ../telemetry-data-collection.rst:1019 -msgid "" -"Telemetry's HBase support does not include native TTL nor ceilometer-expirer " -"support." -msgstr "" - -#: ../telemetry-measurements.rst:494 -msgid "Temperate reading from sensor" -msgstr "" - -#: ../compute-networking-nova.rst:909 -msgid "Temporarily disable firewall" -msgstr "" - -#: ../networking_use.rst:209 -msgid "Temporarily disables a port from sending traffic." -msgstr "" - -#: ../compute_arch.rst:84 -msgid "" -"Tenants are isolated resource containers that form the principal " -"organizational structure within the Compute service. They consist of an " -"individual VLAN, and volumes, instances, images, keys, and users. A user can " -"specify the tenant by appending ``project_id`` to their access key. If no " -"tenant is specified in the API request, Compute attempts to use a tenant " -"with the same ID as the user." -msgstr "" - -#: ../objectstorage_tenant_specific_image_storage.rst:12 -msgid "" -"Tenants that are defined in ``swift_store_admin_tenants`` and that have " -"admin-level accounts" -msgstr "" - -#: ../compute_arch.rst:79 -msgid "Tenants, users, and roles" -msgstr "" - -#: ../networking_adv-features.rst:47 -msgid "Term" -msgstr "" - -#: ../compute_arch.rst:341 -msgid "Terminate instances" -msgstr "" - -#: ../networking_adv-features.rst:568 -msgid "Terminate traffic on a specific VLAN from a NSX gateway service:" -msgstr "" - -#: ../networking_adv-features.rst:39 -msgid "Terminology" -msgstr "" - -#: ../objectstorage_ringbuilder.rst:47 -msgid "" -"That code is a little simplistic because it does not account for the removal " -"of duplicate devices. If a ring has more replicas than devices, a partition " -"will have more than one replica on a device." -msgstr "" - -#: ../blockstorage_volume_backups.rst:10 -msgid "" -"The **cinder** command-line interface provides the tools for creating a " -"volume backup. You can restore a volume from a backup as long as the " -"backup's associated database information (or backup metadata) is intact in " -"the Block Storage database." -msgstr "" - -#: ../networking_adv-features.rst:520 -msgid "" -"The *FLAT* and *VLAN* network types use bridged transport connectors. These " -"network types enable the attachment of large number of ports. To handle the " -"increased scale, the NSX plug-in can back a single OpenStack Network with a " -"chain of NSX logical switches. You can specify the maximum number of ports " -"on each logical switch in this chain on the ``max_lp_per_bridged_ls`` " -"parameter, which has a default value of 5,000." -msgstr "" - -#: ../keystone_integrate_with_ldap.rst:24 -msgid "" -"The *assignment* feature enables administrators to manage project role " -"authorization using the OpenStack Identity service SQL database, while " -"providing user authentication through the LDAP directory." -msgstr "" - -#: ../keystone_integrate_with_ldap.rst:21 -msgid "" -"The *identity* feature enables administrators to manage users and groups by " -"each domain or the OpenStack Identity service entirely." -msgstr "" - -#: ../identity_auth_token_middleware.rst:9 -msgid "" -"The :code:`admin_token` option is deprecated and no longer used for " -"configuring auth_token middleware." -msgstr "" - -#: ../networking_multi-dhcp-agents.rst:243 -msgid "The :command:`agent-show` command shows details for a specified agent:" -msgstr "" - -#: ../blockstorage_backup_disks.rst:116 -msgid "" -"The :command:`kpartx` utility discovers and maps table partitions. You can " -"use it to view partitions that are created inside the instance. Without " -"using the partitions created inside instances, you cannot see its content " -"and create efficient backups." -msgstr "" - -#: ../identity_concepts.rst:165 -msgid "" -"The :file:`/etc/[SERVICE_CODENAME]/policy.json` file controls the tasks that " -"users can perform for a given service. For example, the :file:`/etc/nova/" -"policy.json` file specifies the access policy for the Compute service, the :" -"file:`/etc/glance/policy.json` file specifies the access policy for the " -"Image service, and the :file:`/etc/keystone/policy.json` file specifies the " -"access policy for the Identity service." -msgstr "" - -#: ../telemetry-data-collection.rst:843 -msgid "" -"The :file:`meter.yaml` file should be modified with care. Unless intended do " -"not remove any existing meter definitions from the file. Also, the collected " -"meters can differ in some cases from what is referenced in the documentation." -msgstr "" - -#: ../compute-root-wrap-reference.rst:50 -msgid "" -"The :file:`rootwrap.conf` file uses an INI file format with these sections " -"and parameters:" -msgstr "" - -#: ../compute_arch.rst:7 -msgid "" -"The :term:`cloud controller` represents the global state and interacts with " -"the other components. The ``API server`` acts as the web services front end " -"for the cloud controller. The ``compute controller`` provides compute server " -"resources and usually also contains the Compute service." -msgstr "" - -#: ../compute_arch.rst:305 -msgid "" -"The API endpoints are basic HTTP web services which handle authentication, " -"authorization, and basic command and control functions using various API " -"interfaces under the Amazon, Rackspace, and related models. This enables API " -"compatibility with multiple existing tool sets created for interaction with " -"offerings from other vendors. This broad compatibility prevents vendor lock-" -"in." -msgstr "" - -#: ../telemetry-data-retrieval.rst:34 -msgid "" -"The API provides some additional functionalities, like querying the " -"collected data set. For the samples and alarms API endpoints, both simple " -"and complex query styles are available, whereas for the other endpoints only " -"simple queries are supported." -msgstr "" - -#: ../compute-images-instances.rst:136 -msgid "The Amazon S3 service." -msgstr "" - -#: ../baremetal.rst:28 -msgid "The Bare Metal module is composed of the following components:" -msgstr "" - -#: ../baremetal.rst:15 -msgid "" -"The Bare Metal service provides physical hardware as opposed to virtual " -"machines and provides several reference drivers which leverage common " -"technologies like PXE and IPMI, to cover a wide range of hardware. The " -"pluggable driver architecture also allows vendor-specific drivers to be " -"added for improved performance or functionality not provided by reference " -"drivers. The Bare Metal service makes physical servers as easy to provision " -"as virtual machines in a cloud, which in turn will open up new avenues for " -"enterprises and service providers." -msgstr "" - -#: ../baremetal.rst:10 -msgid "The Bare Metal service provides physical hardware management features." -msgstr "" - -#: ../blockstorage-api-throughput.rst:13 -msgid "" -"The Block Storage API service is named ``openstack-cinder-api`` on the " -"following distributions: CentOS, Fedora, openSUSE, Red Hat Enterprise Linux, " -"and SUSE Linux Enterprise. In Ubuntu and Debian distributions, the Block " -"Storage API service is named ``cinder-api``." -msgstr "" - -#: ../networking_use.rst:32 -msgid "" -"The CLI includes a number of options. For details, see the `OpenStack End " -"User Guide `__." -msgstr "" - -#: ../cross_project_cors.rst:120 -msgid "" -"The CORS middleware used by OpenStack provides verbose debug logging that " -"should reveal most configuration problems. Here are some example log " -"messages, and how to resolve them." -msgstr "" - -#: ../cross_project_cors.rst:107 -msgid "" -"The CORS specification does not support using this wildcard as a part of a " -"URI. Setting allowed-origin to `*` would work, while :code:`*.openstack.org` " -"would not." -msgstr "" - -#: ../networking_introduction.rst:24 -msgid "" -"The Compute API has a virtual server abstraction to describe computing " -"resources. Similarly, the Networking API has virtual network, subnet, and " -"port abstractions to describe networking resources." -msgstr "" - -#: ../compute-system-admin.rst:31 -msgid "" -"The Compute cloud works using a series of daemon processes named nova-\\* " -"that exist persistently on the host machine. These binaries can all run on " -"the same machine or be spread out on multiple boxes in a large deployment. " -"The responsibilities of services and drivers are:" -msgstr "" - -#: ../networking_config-identity.rst:220 -msgid "" -"The Compute service allows VMs to query metadata associated with a VM by " -"making a web request to a special 169.254.169.254 address. Networking " -"supports proxying those requests to nova-api, even when the requests are " -"made from isolated networks, or from multiple networks that use overlapping " -"IP addresses." -msgstr "" - -#: ../compute-service-groups.rst:7 -msgid "" -"The Compute service must know the status of each compute node to effectively " -"manage and use them. This can include events like a user launching a new VM, " -"the scheduler sending a request to a live node, or a query to the " -"ServiceGroup API to determine if a node is live." -msgstr "" - -#: ../compute-networking-nova.rst:181 -msgid "" -"The Compute service uses `dnsmasq `__ as the DHCP server when using either Flat DHCP Network Manager or " -"VLAN Network Manager. For Compute to operate in IPv4/IPv6 dual-stack mode, " -"use at least dnsmasq v2.63. The ``nova-network`` service is responsible for " -"starting dnsmasq processes." -msgstr "" - -#: ../compute_arch.rst:80 -msgid "" -"The Compute system is designed to be used by different consumers in the form " -"of tenants on a shared system, and role-based access assignments. Roles " -"control the actions that a user is allowed to perform." -msgstr "" - -#: ../networking_config-agents.rst:58 -msgid "" -"The DHCP service agent is compatible with all existing plug-ins and is " -"required for all deployments where VMs should automatically receive IP " -"addresses through DHCP." -msgstr "" - -#: ../database.rst:10 -msgid "The Database service provides database management features." -msgstr "" - -#: ../database.rst:22 -msgid "" -"The Database service provides resource isolation at high performance levels, " -"and automates complex administrative tasks such as deployment, " -"configuration, patching, backups, restores, and monitoring." -msgstr "" - -#: ../database.rst:15 -msgid "" -"The Database service provides scalable and reliable cloud provisioning " -"functionality for both relational and non-relational database engines. Users " -"can quickly and easily use database features without the burden of handling " -"complex administrative tasks. Cloud users and database administrators can " -"provision and manage multiple database instances as needed." -msgstr "" - -#: ../compute-networking-nova.rst:410 -msgid "" -"The EC2 API exposes a separate URL for each metadata element. Retrieve a " -"listing of these elements by making a GET query to " -"``http://169.254.169.254/2009-04-04/meta-data/``:" -msgstr "" - -#: ../networking_introduction.rst:152 -msgid "" -"The Firewall-as-a-Service (FWaaS) plug-in adds perimeter firewall management " -"to Networking. FWaaS uses iptables to apply firewall policy to all " -"Networking routers within a project. FWaaS supports one firewall policy and " -"logical firewall instance per project." -msgstr "" - -#: ../blockstorage_glusterfs_backend.rst:42 -msgid "" -"The GlusterFS server must also be configured accordingly in order to allow " -"OpenStack Block Storage to use GlusterFS shares:" -msgstr "" - -#: ../orchestration-auth-model.rst:68 -msgid "" -"The ID of the *trustee* (who you want to delegate to, in this case, the " -"Orchestration module user)." -msgstr "" - -#: ../database.rst:175 -msgid "" -"The ID of the guest image you just added to the Identity service. You can " -"get this ID by using the glance :command:`image-show` IMAGE_NAME command." -msgstr "" - -#: ../networking_introduction.rst:324 -msgid "" -"The IP security policy that specifies the authentication and encryption " -"algorithm and encapsulation mode to use for the established VPN connection." -msgstr "" - -#: ../keystone_integrate_identity_backend_ldap.rst:7 -msgid "" -"The Identity back end contains information for users, groups, and group " -"member lists. Integrating the Identity back end with LDAP allows " -"administrators to use users and groups in LDAP." -msgstr "" - -#: ../identity_concepts.rst:324 -msgid "" -"The Identity service also maintains a user that corresponds to each service, " -"such as, a user named ``nova`` for the Compute service, and a special " -"service tenant called ``service``." -msgstr "" - -#: ../identity_concepts.rst:126 -msgid "" -"The Identity service assigns a tenant and a role to a user. You might assign " -"the ``compute-user`` role to the ``alice`` user in the ``acme`` tenant:" -msgstr "" - -#: ../identity_service_api_protection.rst:46 -msgid "The Identity service expects these attributes:" -msgstr "" - -#: ../identity_troubleshoot.rst:95 -msgid "" -"The Identity service log should show the access of the certificate files. " -"You might have to turn up your logging levels. Set ``debug = True`` and " -"``verbose = True`` in your Identity configuration file and restart the " -"Identity server." -msgstr "" - -#: ../keystone_configure_with_SSL.rst:9 -msgid "" -"The Identity service provides a set of sample certificates in the :file:" -"`examples/pki/certs` and :file:`examples/pki/private` directories:" -msgstr "" - -#: ../identity_concepts.rst:307 -msgid "" -"The Identity service provides identity, token, catalog, and policy services. " -"It consists of:" -msgstr "" - -#: ../identity_concepts.rst:363 -msgid "" -"The Identity service server might not allow all operations. For example, if " -"you use the Identity server with the LDAP Identity back end and group " -"updates are disabled, a request to create, delete, or update a group fails." -msgstr "" - -#: ../keystone_secure_identity_to_ldap_backend.rst:4 -msgid "" -"The Identity service supports the use of TLS to encrypt LDAP traffic. Before " -"configuring this, you must first verify where your certificate authority " -"file is located. For more information, see the `OpenStack Security Guide SSL " -"introduction `_." -msgstr "" - -#: ../compute-manage-the-cloud.rst:83 -msgid "" -"The Identity service will give you an authentication endpoint, which Compute " -"recognizes as ``OS_AUTH_URL``:" -msgstr "" - -#: ../compute-images-instances.rst:119 -msgid "The Image service supports these back-end stores:" -msgstr "" - -#: ../blockstorage_image_volume_cache.rst:24 -msgid "" -"The Image-Volume cache requires that the Internal Tenant be configured for " -"the Block Storage services. This tenant will own the cached image-volumes so " -"they can be managed like normal users including tools like volume quotas. " -"This protects normal users from having to see the cached image-volumes, but " -"does not make them globally hidden." -msgstr "" - -#: ../networking_introduction.rst:320 -msgid "" -"The Internet Key Exchange (IKE) policy that identifies the authentication " -"and encryption algorithm to use during phase one and two negotiation of a " -"VPN connection." -msgstr "" - -#: ../networking_adv-features.rst:761 -msgid "" -"The L3 metering API extension enables administrators to configure IP ranges " -"and assign a specified label to them to be able to measure traffic that goes " -"through a virtual router." -msgstr "" - -#: ../networking_adv-features.rst:765 -msgid "" -"The L3 metering extension is decoupled from the technology that implements " -"the measurement. Two abstractions have been added: One is the metering label " -"that can contain metering rules. Because a metering label is associated with " -"a tenant, all virtual routers in this tenant are associated with this label." -msgstr "" - -#: ../networking_adv-features.rst:183 -msgid "" -"The L3 router provides basic NAT capabilities on gateway ports that uplink " -"the router to external networks. This router SNATs all traffic by default " -"and supports floating IPs, which creates a static one-to-one mapping from a " -"public IP on the external network to a private IP on one of the other " -"subnets attached to the router. This allows a tenant to selectively expose " -"VMs on private networks to other hosts on the external network (and often to " -"all hosts on the Internet). You can allocate and map floating IPs from one " -"port to another, as needed." -msgstr "" - -#: ../blockstorage_over_subscription.rst:68 -msgid "" -"The LVM driver reports ``thin_provisioning_support=True`` and " -"``thick_provisioning_support=False`` if the ``lvm_type`` flag in :file:" -"`cinder.conf` is ``thin``. Otherwise it reports " -"``thin_provisioning_support=False`` and ``thick_provisioning_support=True``." -msgstr "" - -#: ../networking_adv-features.rst:397 -msgid "" -"The Load-Balancer-as-a-Service (LBaaS) API provisions and configures load " -"balancers. The reference implementation is based on the HAProxy software " -"load balancer." -msgstr "" - -#: ../objectstorage-monitoring.rst:30 -msgid "The MD5 sum of each ring file." -msgstr "" - -#: ../networking_adv-features.rst:110 -msgid "" -"The ML2, Open vSwitch, and Linux Bridge plug-ins support VLAN networks, flat " -"networks, and local networks. Only the ML2 and Open vSwitch plug-ins " -"currently support GRE and VXLAN networks, provided that the required " -"features exist in the hosts Linux kernel, Open vSwitch, and iproute2 " -"packages." -msgstr "" - -#: ../compute-node-down.rst:315 -msgid "The MySQL database is updated." -msgstr "" - -#: ../compute_arch.rst:353 -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 "" - -#: ../networking_adv-features.rst:173 -msgid "" -"The Networking API provides abstract L2 network segments that are decoupled " -"from the technology used to implement the L2 network. Networking includes an " -"API extension that provides abstract L3 routers that API users can " -"dynamically provision and configure. These Networking routers can connect " -"multiple L2 Networking networks and can also provide a gateway that connects " -"one or more private L2 networks to a shared external network. For example, a " -"public network for access to the Internet. See the *OpenStack Configuration " -"Reference* for details on common models of deploying Networking L3 routers." -msgstr "" - -#: ../networking_introduction.rst:229 -msgid "" -"The Networking client requires a protocol value; if the rule is protocol " -"agnostic, you can use the ``any`` value." -msgstr "" - -#: ../networking_auth.rst:68 -msgid "" -"The Networking policy engine currently defines the following kinds of " -"terminal rules:" -msgstr "" - -#: ../networking_arch.rst:17 -msgid "" -"The Networking server uses the neutron-server daemon to expose the " -"Networking API and enable administration of the configured Networking plug-" -"in. Typically, the plug-in requires access to a database for persistent " -"storage (also similar to other OpenStack services)." -msgstr "" - -#: ../networking_config-identity.rst:194 -msgid "" -"The Networking service provides security group functionality using a " -"mechanism that is more flexible and powerful than the security group " -"capabilities built into Compute. Therefore, if you use Networking, you " -"should always disable built-in security groups and proxy all security group " -"calls to the Networking API. If you do not, security policies will conflict " -"by being simultaneously applied by both services." -msgstr "" - -#: ../networking_introduction.rst:5 -msgid "" -"The Networking service, code-named neutron, provides an API that lets you " -"define network connectivity and addressing in the cloud. The Networking " -"service enables operators to leverage different networking technologies to " -"power their cloud networking. The Networking service also provides an API to " -"configure and manage a variety of network services ranging from L3 " -"forwarding and NAT to load balancing, edge firewalls, and IPsec VPN." -msgstr "" - -#: ../networking_introduction.rst:53 -msgid "The Networking service:" -msgstr "" - -#: ../networking_config-agents.rst:272 -msgid "The Neutron Metering agent resides beside neutron-l3-agent." -msgstr "" - -#: ../blockstorage-manage-volumes.rst:16 -msgid "" -"The OpenStack Block Storage service also provides drivers that enable you to " -"use several vendors' back-end storage devices, in addition to or instead of " -"the base LVM implementation." -msgstr "" - -#: ../blockstorage-manage-volumes.rst:10 -msgid "" -"The OpenStack Block Storage service is not a shared storage solution like a " -"Network Attached Storage (NAS) of NFS volumes, where you can attach a volume " -"to multiple servers. With the OpenStack Block Storage service, you can " -"attach a volume to only one instance at a time." -msgstr "" - -#: ../blockstorage.rst:7 -msgid "" -"The OpenStack Block Storage service works through the interaction of a " -"series of daemon processes named ``cinder-*`` that reside persistently on " -"the host machine or machines. The binaries can all be run from a single " -"node, or spread across multiple nodes. They can also be run on the same node " -"as other OpenStack services." -msgstr "" - -#: ../ts_cinder_config.rst:110 -msgid "" -"The OpenStack Block Storage uses ``tgtd`` as the default iSCSI helper and " -"implements persistent targets. This means that in the case of a ``tgt`` " -"restart or even a node reboot your existing volumes on that node will be " -"restored automatically with their original IQN." -msgstr "" - -#: ../compute.rst:5 -msgid "" -"The OpenStack Compute service allows you to control an Infrastructure-as-a-" -"Service (IaaS) cloud computing platform. It gives you control over instances " -"and networks, and allows you to manage access to the cloud through users and " -"projects." -msgstr "" - -#: ../keystone_integrate_with_ldap.rst:14 -msgid "" -"The OpenStack Identity service supports integration with existing LDAP " -"directories for authentication and authorization services." -msgstr "" - -#: ../compute-images-instances.rst:106 -msgid "" -"The OpenStack Image service can be controlled using a command-line tool. For " -"more information about using the OpenStack Image command-line tool, see the " -"`Manage Images `__ section in the OpenStack End User Guide." -msgstr "" - -#: ../compute-images-instances.rst:98 -msgid "" -"The OpenStack Image service discovers, registers, and retrieves virtual " -"machine images. The service also includes a RESTful API that allows you to " -"query VM image metadata and retrieve the actual image with HTTP requests. " -"For more information about the API, see the `OpenStack API Complete " -"Reference `__ and the `Python " -"API `__." -msgstr "" - -#: ../compute-images-instances.rst:122 -msgid "" -"The OpenStack Image service stores virtual machine images in the file system " -"back end by default. This simple back end writes image files to the local " -"file system." -msgstr "" - -#: ../networking_config-agents.rst:159 -msgid "" -"The OpenStack Networking service has a widely used API extension to allow " -"administrators and tenants to create routers to interconnect L2 networks, " -"and floating IPs to make ports on private networks publicly accessible." -msgstr "" - -#: ../dashboard.rst:5 -msgid "" -"The OpenStack dashboard is a web-based interface that allows you to manage " -"OpenStack resources and services. The dashboard allows you to interact with " -"the OpenStack Compute cloud controller using the OpenStack APIs. For more " -"information about installing and configuring the dashboard, see the " -"`OpenStack Installation Guide `__ for your " -"operating system." -msgstr "" - -#: ../compute-images-instances.rst:130 -msgid "The OpenStack highly available service for storing blocks." -msgstr "" - -#: ../compute-images-instances.rst:127 -msgid "The OpenStack highly available service for storing objects." -msgstr "" - -#: ../compute-images-instances.rst:412 -msgid "" -"The OpenStack python-novaclient package provides a basic command-line " -"utility, which uses the :command:`nova` command. This is available as a " -"native package for most Linux distributions, or you can install the latest " -"version using the pip python package installer:" -msgstr "" - -#: ../identity_troubleshoot.rst:27 -msgid "" -"The PKI-based token validation scheme relies on certificates from Identity " -"that are fetched through HTTP and stored in a local directory. The location " -"for this directory is specified by the ``signing_dir`` configuration option. " -"In your services configuration file, look for a section like this:" -msgstr "" - -#: ../identity_troubleshoot.rst:118 -msgid "The SELinux policy is denying access to the directory." -msgstr "" - -#: ../objectstorage-monitoring.rst:24 -msgid "" -"The Swift Recon middleware (see http://swift.openstack.org/admin_guide." -"html#cluster-telemetry-and-monitoring) provides general machine statistics, " -"such as load average, socket statistics, ``/proc/meminfo`` contents, and so " -"on, as well as Swift-specific meters:" -msgstr "" - -#: ../telemetry-data-retrieval.rst:23 -msgid "" -"The Telemetry API URL can be retrieved from the service catalog provided by " -"OpenStack Identity, which is populated during the installation process. The " -"API access needs a valid token and proper permission to retrieve data, as " -"described in :ref:`telemetry-users-roles-tenants`." -msgstr "" - -#: ../telemetry-data-retrieval.rst:244 -msgid "" -"The Telemetry API supports simple query on the meter endpoint. The query " -"functionality has the following syntax::" -msgstr "" - -#: ../telemetry-system-architecture.rst:64 -msgid "" -"The Telemetry architecture highly depends on the AMQP service both for " -"consuming notifications coming from OpenStack services and internal " -"communication." -msgstr "" - -#: ../telemetry-troubleshooting-guide.rst:88 -msgid "" -"The Telemetry command line client is not adapted to the v3 version of the " -"OpenStack Identity API. If the ``adminURL`` is used as ``os_auth_url``, the :" -"command:`ceilometer` command results in the following error message:" -msgstr "" - -#: ../telemetry-alarms.rst:49 -msgid "" -"The Telemetry module also supports the concept of a meta-alarm, which " -"aggregates over the current state of a set of underlying basic alarms " -"combined via a logical operator (AND or OR)." -msgstr "" - -#: ../telemetry-data-retrieval.rst:193 -msgid "" -"The Telemetry module captures the user-visible resource usage data. " -"Therefore the database will not contain any data without the existence of " -"these resources, like VM images in the OpenStack Image service." -msgstr "" - -#: ../telemetry-best-practices.rst:11 -msgid "" -"The Telemetry module collects a continuously growing set of data. Not all " -"the data will be relevant for a cloud administrator to monitor." -msgstr "" - -#: ../telemetry-data-collection.rst:834 -msgid "" -"The Telemetry module collects a subset of the meters by filtering " -"notifications emitted by other OpenStack services. Starting with the Liberty " -"release, you can find the meter definitions in a separate configuration " -"file, called :file:`ceilometer/meter/data/meter.yaml`. This enables " -"operators/administrators to add new meters to Telemetry project by updating " -"the :file:`meter.yaml` file without any need for additional code changes." -msgstr "" - -#: ../telemetry-system-architecture.rst:109 -msgid "" -"The Telemetry module collects information about the virtual machines, which " -"requires close connection to the hypervisor that runs on the compute hosts." -msgstr "" - -#: ../telemetry-measurements.rst:7 -msgid "" -"The Telemetry module collects meters within an OpenStack deployment. This " -"section provides a brief summary about meters format and origin and also " -"contains the list of available meters." -msgstr "" - -#: ../telemetry-data-collection.rst:44 -msgid "" -"The Telemetry module has a separate agent that is responsible for consuming " -"notifications, namely the notification agent. This component is responsible " -"for consuming from the message bus and transforming notifications into " -"events and measurement samples." -msgstr "" - -#: ../telemetry-data-collection.rst:957 -msgid "" -"The Telemetry module has a separate service that is responsible for " -"persisting the data that comes from the pollsters or is received as " -"notifications. The data can be stored in a file or a database back end, for " -"which the list of supported databases can be found in :ref:`telemetry-" -"supported-databases`. The data can also be sent to an external data store by " -"using an HTTP dispatcher." -msgstr "" - -#: ../telemetry-troubleshooting-guide.rst:7 -msgid "" -"The Telemetry module has similar log settings as the other OpenStack " -"services. Multiple options are available to change the target of logging, " -"the format of the log entries and the log levels." -msgstr "" - -#: ../telemetry-system-architecture.rst:11 -msgid "The Telemetry module is built from the following agents and services:" -msgstr "" - -#: ../telemetry-data-collection.rst:203 -msgid "" -"The Telemetry module is intended to store a complex picture of the " -"infrastructure. This goal requires additional information than what is " -"provided by the events and notifications published by each service. Some " -"information is not emitted directly, like resource usage of the VM instances." -msgstr "" - -#: ../telemetry-data-retrieval.rst:5 -msgid "" -"The Telemetry module offers several mechanisms from which the persisted data " -"can be accessed. As described in :ref:`telemetry-system-architecture` and " -"in :ref:`telemetry-data-collection`, the collected information can be stored " -"in one or more database back ends, which are hidden by the Telemetry RESTful " -"API." -msgstr "" - -#: ../telemetry-data-retrieval.rst:19 -msgid "" -"The Telemetry module provides a RESTful API, from which the collected " -"samples and all the related information can be retrieved, like the list of " -"meters, alarm definitions and so forth." -msgstr "" - -#: ../telemetry-data-retrieval.rst:180 -msgid "" -"The Telemetry module provides a command line client, with which the " -"collected data is available just as the alarm definition and retrieval " -"options. The client uses the Telemetry RESTful API in order to execute the " -"requested operations." -msgstr "" - -#: ../telemetry-data-retrieval.rst:468 -msgid "" -"The Telemetry module provides several transport methods to forward the data " -"collected to the ceilometer-collector service or to an external system. The " -"consumers of this data are widely different, like monitoring systems, for " -"which data loss is acceptable and billing systems, which require reliable " -"data transportation. Telemetry provides methods to fulfill the requirements " -"of both kind of systems, as it is described below." -msgstr "" - -#: ../telemetry-data-collection.rst:1029 -msgid "" -"The Telemetry module supports sending samples to an external HTTP target. " -"The samples are sent without any modification. To set this option as the " -"collector's target, the ``dispatcher`` has to be changed to ``http`` in the :" -"file:`ceilometer.conf` configuration file. For the list of options that you " -"need to set, see the see the `dispatcher_http section `__ in the OpenStack Configuration Reference." -msgstr "" - -#: ../telemetry-data-collection.rst:1047 -msgid "" -"The Telemetry module supports sending the metering data to Gnocchi back end " -"through the gnocchi dispatcher. To set this option as the target, change the " -"``dispatcher`` to ``gnocchi`` in the :file:`ceilometer.conf` configuration " -"file." -msgstr "" - -#: ../telemetry-measurements.rst:78 -msgid "" -"The Telemetry module supports storing notifications as events. This " -"functionality was added later, therefore the list of meters still contains " -"existence type and other event related items. The proper way of using " -"Telemetry is to configure it to use the event store and turn off the " -"collection of the event related meters. For further information about events " -"see `Events section `__ in the Telemetry documentation. For further information about how " -"to turn on and off meters see :ref:`telemetry-pipeline-configuration`. " -"Please also note that currently no migration is available to move the " -"already existing event type samples to the event store." -msgstr "" - -#: ../telemetry-measurements.rst:376 -msgid "" -"The Telemetry module supports to create new meters by using transformers. " -"For more details about transformers see :ref:`telemetry-transformers`. Among " -"the meters gathered from libvirt and Hyper-V there are a few ones which are " -"generated from other meters. The list of meters that are created by using " -"the ``rate_of_change`` transformer from the above table is the following:" -msgstr "" - -#: ../telemetry-system-architecture.rst:7 -msgid "" -"The Telemetry module uses an agent-based architecture. Several modules " -"combine their responsibilities to collect data, store samples in a database, " -"or provide an API service for handling incoming requests." -msgstr "" - -#: ../telemetry.rst:15 -msgid "" -"The Telemetry module was originally designed to support billing systems for " -"OpenStack cloud resources. This project only covers the metering portion of " -"the required processing for billing. This module collects information about " -"the system and stores it in the form of samples in order to provide data " -"about anything that can be billed." -msgstr "" - -#: ../networking_config-plugins.rst:153 -msgid "" -"The UUID of the NSX-mh transport zone that should be used by default when a " -"tenant creates a network. You can get this value from the Transport Zones " -"page for the NSX-mh manager:" -msgstr "" - -#: ../networking_adv-features.rst:459 -msgid "" -"The VMware NSX QoS extension rate-limits network ports to guarantee a " -"specific amount of bandwidth for each port. This extension, by default, is " -"only accessible by a tenant with an admin role but is configurable through " -"the :file:`policy.json` file. To use this extension, create a queue and " -"specify the min/max bandwidth rates (kbps) and optionally set the QoS " -"Marking and DSCP value (if your network fabric uses these values to make " -"forwarding decisions). Once created, you can associate a queue with a " -"network. Then, when ports are created on that network they are automatically " -"created and associated with the specific queue size that was associated with " -"the network. Because one size queue for a every port on a network might not " -"be optimal, a scaling factor from the nova flavor ``rxtx_factor`` is passed " -"in from Compute when creating the port to scale the queue." -msgstr "" - -#: ../compute-remote-console-access.rst:67 -msgid "The VNC console connection works as follows:" -msgstr "" - -#: ../compute-remote-console-access.rst:59 -msgid "" -"The VNC proxy is an OpenStack component that enables compute service users " -"to access their instances through VNC clients." -msgstr "" - -#: ../networking_introduction.rst:312 -msgid "" -"The VPNaaS extension enables OpenStack tenants to extend private networks " -"across the internet." -msgstr "" - -#: ../compute-service-groups.rst:46 -msgid "" -"The ZooKeeper ServiceGroup driver works by using ZooKeeper ephemeral nodes. " -"ZooKeeper, unlike databases, is a distributed system, with its load divided " -"among several servers. On a compute worker node, the driver can establish a " -"ZooKeeper session, then create an ephemeral znode in the group directory. " -"Ephemeral znodes have the same lifespan as the session. If the worker node " -"or the nova-compute daemon crashes, or a network partition is in place " -"between the worker and the ZooKeeper server quorums, the ephemeral znodes " -"are removed automatically. The driver can be given group membership by " -"running the :command:`ls` command in the group directory." -msgstr "" - -#: ../compute-service-groups.rst:57 -msgid "" -"The ZooKeeper driver requires the ZooKeeper servers and client libraries. " -"Setting up ZooKeeper servers is outside the scope of this guide (for more " -"information, see `Apache Zookeeper `_). These " -"client-side Python libraries must be installed on every compute node:" -msgstr "" - -#: ../compute-images-instances.rst:428 -msgid "" -"The `OpenStack Configuration Reference `__ provides detailed information on controlling " -"where your instances run, including ensuring a set of instances run on " -"different compute nodes for service resiliency or on the same node for high " -"performance inter-instance communications." -msgstr "" - -#: ../telemetry-data-collection.rst:325 -msgid "" -"The `Tooz `__ library provides the " -"coordination within the groups of service instances. It provides an API " -"above several back ends that can be used for building distributed " -"applications." -msgstr "" - -#: ../telemetry-data-retrieval.rst:448 -msgid "" -"The ``VERSION`` parameter can be ``1`` or ``2``, specifying the API version " -"to be used." -msgstr "" - -#: ../telemetry-data-retrieval.rst:158 -msgid "The ``aggregate.param`` option is required." -msgstr "" - -#: ../compute-manage-logs.rst:165 -msgid "" -"The ``base_url`` option specifies the base URL that clients receive from the " -"API upon requesting a serial console. Typically, this refers to the host " -"name of the controller node." -msgstr "" - -#: ../telemetry-data-retrieval.rst:316 -msgid "" -"The ``ceilometer query-samples`` command is used to execute rich queries. " -"This command accepts the following parameters:" -msgstr "" - -#: ../telemetry-data-collection.rst:964 -msgid "" -"The ``ceilometer-collector`` service receives the data as messages from the " -"message bus of the configured AMQP service. It sends these datapoints " -"without any modification to the configured target. The service has to run on " -"a host machine from which it has access to the configured dispatcher." -msgstr "" - -#: ../telemetry-system-architecture.rst:56 -msgid "" -"The ``ceilometer-polling`` service is available since the Kilo release. It " -"is intended to replace ceilometer-agent-central, ceilometer-agent-compute, " -"and ceilometer-agent-ipmi." -msgstr "" - -#: ../telemetry-data-retrieval.rst:225 -msgid "" -"The ``ceilometer`` command was run with ``admin`` rights, which means that " -"all the data is accessible in the database. For more information about " -"access right see :ref:`telemetry-users-roles-tenants`. As it can be seen in " -"the above example, there are two VM instances existing in the system, as " -"there are VM instance related meters on the top of the result list. The " -"existence of these meters does not indicate that these instances are running " -"at the time of the request. The result contains the currently collected " -"meters per resource, in an ascending order based on the name of the meter." -msgstr "" - -#: ../blockstorage_nfs_backend.rst:11 -msgid "" -"The ``cinder`` volume service is named ``openstack-cinder-volume`` on the " -"following distributions:" -msgstr "" - -#: ../networking_use.rst:220 -msgid "The ``device_id`` can also be a logical router ID." -msgstr "" - -#: ../networking_use.rst:83 -msgid "" -"The ``device_owner`` field describes who owns the port. A port whose " -"``device_owner`` begins with:" -msgstr "" - -#: ../compute-euca2ools.rst:7 -msgid "" -"The ``euca2ools`` command-line tool provides a command line interface to EC2 " -"API calls. For more information about ``euca2ools``, see `https://www." -"eucalyptus.com/docs/eucalyptus/4.1.2/index.html `__." -msgstr "" - -#: ../networking_adv-features.rst:659 -msgid "" -"The ``fields=status`` parameter in Networking API requests always triggers " -"an explicit query to the NSX back end, even when you enable asynchronous " -"state synchronization. For example, ``GET /v2.0/networks/NET_ID?" -"fields=status&fields=name``." -msgstr "" - -#: ../blockstorage-driver-filter-weighing.rst:78 -msgid "" -"The ``filter_function`` option is a string defining an equation that will " -"determine whether a back end should be considered as a potential candidate " -"in the scheduler." -msgstr "" - -#: ../telemetry-data-retrieval.rst:124 -msgid "The ``filter``, ``orderby`` and ``limit`` fields are optional." -msgstr "" - -#: ../blockstorage_volume_backups.rst:41 -msgid "The ``force`` flag is new in OpenStack Liberty." -msgstr "" - -#: ../networking_config-identity.rst:9 -msgid "" -"The ``get_id()`` function stores the ID of created objects, and removes the " -"need to copy and paste object IDs in later steps:" -msgstr "" - -#: ../blockstorage-driver-filter-weighing.rst:82 -msgid "" -"The ``goodness_function`` option is a string defining an equation that will " -"rate the quality of the potential host (0 to 100, 0 lowest, 100 highest)." -msgstr "" - -#: ../ts_non_existent_vlun.rst:20 -msgid "" -"The ``hp3par_domain`` configuration items either need to be updated to use " -"the domain the 3PAR host currently resides in, or the 3PAR host needs to be " -"moved to the domain that the volume was created in." -msgstr "" - -#: ../blockstorage_volume_backups.rst:36 -msgid "" -"The ``incremental`` and ``force`` flags are only available for block storage " -"API v2. You have to specify [--os-volume-api-version 2] in the **cinder** " -"command-line interface to use this parameter." -msgstr "" - -#: ../telemetry-measurements.rst:364 -msgid "" -"The ``instance:`` meter can be replaced by using extra parameters in " -"both the samples and statistics queries. Sample queries look like the " -"following::" -msgstr "" - -#: ../identity_example_usage.rst:5 -msgid "" -"The ``keystone`` client is set up to expect commands in the general form of " -"``keystone command argument``, followed by flag-like keyword arguments to " -"provide additional (often optional) information. For example, the :command:" -"`user-list` and :command:`tenant-create` commands can be invoked as follows:" -msgstr "" - -#: ../compute-manage-logs.rst:169 -msgid "" -"The ``listen`` option specifies the network interface nova-compute should " -"listen on for virtual console connections. Typically, 0.0.0.0 will enable " -"listening on all interfaces." -msgstr "" - -#: ../compute-configuring-migrations.rst:269 -msgid "" -"The ``live_migration_downtime_delay`` parameter sets the amount of time to " -"wait between each step, in seconds. This setting defaults to 75 seconds." -msgstr "" - -#: ../compute-configuring-migrations.rst:265 -msgid "" -"The ``live_migration_downtime_steps`` parameter sets the total number of " -"incremental steps to reach the maximum downtime value. This setting defaults " -"to 10 steps." -msgstr "" - -#: ../compute-configuring-migrations.rst:261 -msgid "" -"The ``live_migration_downtime`` parameter sets the maximum permitted " -"downtime for a live migration, in milliseconds. This setting defaults to 500 " -"milliseconds." -msgstr "" - -#: ../compute-networking-nova.rst:495 -msgid "" -"The ``metadata_host`` configuration option must be an IP address, not a host " -"name." -msgstr "" - -#: ../compute_arch.rst:23 -msgid "" -"The ``network controller`` provides virtual networks to enable compute " -"servers to interact with each other and with the public network. You can " -"also use OpenStack Networking instead." -msgstr "" - -#: ../blockstorage_nfs_backend.rst:127 -msgid "" -"The ``nfs_sparsed_volumes`` configuration key determines whether volumes are " -"created as sparse files and grown as needed or fully allocated up front. The " -"default and recommended value is ``true``, which ensures volumes are " -"initially created as sparse files." -msgstr "" - -#: ../telemetry-data-retrieval.rst:105 -msgid "" -"The ``not`` operator has different behavior in MongoDB and in the SQLAlchemy-" -"based database engines. If the ``not`` operator is applied on a non existent " -"metadata field then the result depends on the database engine. In case of " -"MongoDB, it will return every sample as the ``not`` operator is evaluated " -"true for every sample where the given field does not exist. On the other " -"hand the SQL-based database engine will return an empty result because of " -"the underlying ``join`` operation." -msgstr "" - -#: ../compute_arch.rst:13 -msgid "" -"The ``object store`` is an optional component that provides storage " -"services; you can also use OpenStack Object Storage instead." -msgstr "" - -#: ../identity_service_api_protection.rst:54 -msgid "" -"The ``project_id`` attribute requirement depends on the scope, and the list " -"of roles you have within that scope." -msgstr "" - -#: ../compute-manage-logs.rst:173 -msgid "" -"The ``proxyclient_address`` option specifies which network interface the " -"proxy should connect to. Typically, this refers to the IP address of the " -"management interface." -msgstr "" - -#: ../compute_arch.rst:27 -msgid "" -"The ``scheduler`` is used to select the most suitable compute controller to " -"host an instance." -msgstr "" - -#: ../networking_config-agents.rst:346 -msgid "" -"The ``service_provider`` option is already defined in the :file:`/usr/share/" -"neutron/neutron-dist.conf` file on Red Hat based systems. Do not define it " -"in :file:`neutron.conf` otherwise the Networking services will fail to " -"restart." -msgstr "" - -#: ../telemetry-measurements.rst:829 -msgid "" -"The ``usage`` related information may not be updated right after an upload " -"or download, because the Ceph Object Gateway needs time to update the usage " -"properties. For instance, the default configuration needs approximately 30 " -"minutes to generate the usage logs." -msgstr "" - -#: ../compute-remote-console-access.rst:196 -msgid "" -"The ``vncserver_proxyclient_address`` defaults to ``127.0.0.1``, which is " -"the address of the compute host that Compute instructs proxies to use when " -"connecting to instance servers." -msgstr "" - -#: ../compute-networking-nova.rst:617 -msgid "" -"The ``x.x.x.x/y`` value specifies the range of floating IPs for each pool of " -"floating IPs that you define. This configuration is also required if the VMs " -"in the source group have floating IPs." -msgstr "" - -#: ../telemetry-data-collection.rst:585 -msgid "The above definition methods can be used in the following combinations:" -msgstr "" - -#: ../blockstorage-driver-filter-weighing.rst:319 -msgid "" -"The above example combines the techniques from the first two examples. The " -"best back end is now decided based off of the total capacity of the back end " -"and the requested volume's size." -msgstr "" - -#: ../blockstorage-driver-filter-weighing.rst:291 -msgid "" -"The above example will determine the goodness rating of a back end based off " -"of the requested volume's size. Default OpenStack Block Storage scheduler " -"filtering is done. The example shows how the ternary if statement can be " -"used in a filter or goodness function. If a requested volume is of size " -"10 GB then lvm-1 is rated as 50 and lvm-2 is rated as 100. In this case " -"lvm-2 wins. If a requested volume is of size 3 GB then lvm-1 is rated 100 " -"and lvm-2 is rated 25. In this case lvm-1 would win." -msgstr "" - -#: ../blockstorage-driver-filter-weighing.rst:268 -msgid "" -"The above example will filter volumes to different back ends depending on " -"the size of the requested volume. Default OpenStack Block Storage scheduler " -"weighing is done. Volumes with a size less than 10 GB are sent to lvm-1 and " -"volumes with a size greater than or equal to 10 GB are sent to lvm-2." -msgstr "" - -#: ../blockstorage_over_subscription.rst:96 -msgid "" -"The above extra specs are used by the scheduler to find a back end that " -"supports thin provisioning, thick provisioning, or both to match the needs " -"of a specific volume type." -msgstr "" - -#: ../blockstorage-driver-filter-weighing.rst:351 -msgid "" -"The above is an example of how back-end specific properties can be used in " -"the filter and goodness functions. In this example the LVM driver's " -"``total_volumes`` capability is being used to determine which host gets used " -"during a volume request. In the above example, lvm-1 and lvm-2 will handle " -"volume requests for all volumes with a size less than 5 GB. The lvm-1 host " -"will have priority until it contains three or more volumes. After than lvm-2 " -"will have priority until it contains eight or more volumes. The lvm-3 will " -"collect all volumes greater or equal to 5 GB as well as all volumes once " -"lvm-1 and lvm-2 lose priority." -msgstr "" - -#: ../objectstorage_account_reaper.rst:26 -msgid "" -"The account reaper runs on each account server and scans the server " -"occasionally for account databases marked for deletion. It only fires up on " -"the accounts for which the server is the primary node, so that multiple " -"account servers aren't trying to do it simultaneously. Using multiple " -"servers to delete one account might improve the deletion speed but requires " -"coordination to avoid duplication. Speed really is not a big concern with " -"data deletion, and large accounts aren't deleted often." -msgstr "" - -#: ../ts-eql-volume-size.rst:54 -msgid "" -"The actual size (``VolReserve``) is 1.01 GB. The EQL Group Manager should " -"also report a volume size of 1.01 GB::" -msgstr "" - -#: ../blockstorage_image_volume_cache.rst:43 -msgid "" -"The actual user and project that are configured for the Internal Tenant do " -"not require any special privileges. They can be the Block Storage service " -"tenant or can be any normal project and user." -msgstr "" - -#: ../compute-configuring-migrations.rst:397 -msgid "" -"The added compute node and the host will shut down to join the host to the " -"XenServer pool. The operation will fail if any server other than the compute " -"node is running or suspended on the host." -msgstr "" - -#: ../compute-remote-console-access.rst:251 -msgid "" -"The address of the compute host that Compute instructs proxies to use when " -"connecting to instance ``vncservers``." -msgstr "" - -#: ../telemetry-alarms.rst:108 -msgid "" -"The alarm evaluation process uses the same mechanism for workload " -"partitioning as the central and compute agents. The `Tooz `_ library provides the coordination within the groups " -"of service instances. For further information about this approach, see the " -"section called :ref:`Support for HA deployment of the central and compute " -"agent services `." -msgstr "" - -#: ../telemetry-alarms.rst:166 -msgid "" -"The alarm period should be a whole number multiple (1 or more) of the " -"interval configured in the pipeline corresponding to the target meter." -msgstr "" - -#: ../blockstorage-driver-filter-weighing.rst:155 -msgid "The allocated capacity in GB" -msgstr "" - -#: ../telemetry-measurements.rst:318 -msgid "" -"The amount of d\\ isk occupied by the instance o\\ n the host mach\\ ine" -msgstr "" - -#: ../telemetry-measurements.rst:334 -msgid "" -"The amount of d\\ isk per device occupied by the instance on th\\ e host " -"machine" -msgstr "" - -#: ../telemetry-measurements.rst:329 -msgid "The amount of d\\ isk per device that the instan\\ ce can see" -msgstr "" - -#: ../telemetry-measurements.rst:314 -msgid "The amount of d\\ isk that the in\\ stance can see" -msgstr "" - -#: ../keystone_caching_layer.rst:72 -msgid "" -"The assignment system has a separate ``cache_time`` configuration option, " -"that can be set to a value above or below the global ``expiration_time`` " -"default, allowing for different caching behavior from the other systems in " -"Identity service. This option is set in the ``[assignment]`` section of the " -"configuration file." -msgstr "" - -#: ../blockstorage-driver-filter-weighing.rst:189 -msgid "The attach status for the volume" -msgstr "" - -#: ../ts-eql-volume-size.rst:131 -msgid "" -"The attempt to create a new volume based on the size reported by the " -"``cinder`` tool will then fail." -msgstr "" - -#: ../compute-security.rst:34 -msgid "" -"The attestation server verifies the measurements against a known good " -"database to determine node trustworthiness." -msgstr "" - -#: ../compute-security.rst:89 -msgid "The attestation service's URL path" -msgstr "" - -#: ../telemetry-data-collection.rst:357 -msgid "" -"The availability check of the instances is provided by heartbeat messages. " -"When the connection with an instance is lost, the workload will be " -"reassigned within the remained instances in the next polling cycle." -msgstr "" - -#: ../telemetry-data-collection.rst:23 -msgid "The available data collection mechanisms are:" -msgstr "" - -#: ../networking_adv-features.rst:583 -msgid "" -"The back-end is polled periodically and the status for every resource is " -"retrieved; then the status in the Networking database is updated only for " -"the resources for which a status change occurred. As operational status is " -"now retrieved asynchronously, performance for ``GET`` operations is " -"consistently improved." -msgstr "" - -#: ../compute-images-instances.rst:62 -msgid "" -"The base image is copied from the image store to the local disk. The local " -"disk is the first disk that the instance accesses, labeled ``vda`` in this " -"diagram. Your instances will start up faster if you use smaller images, as " -"less data needs to be copied across the network." -msgstr "" - -#: ../telemetry-events.rst:99 -msgid "" -"The basic set of traits (all are TEXT type) that will be added to all events " -"if the notification has the relevant data are: service (notification's " -"publisher), tenant\\_id, and request\\_id. These do not have to be specified " -"in the event definition, they are automatically added, but their definitions " -"can be overridden for a given event\\_type." -msgstr "" - -#: ../keystone_certificates_for_pki.rst:117 -msgid "" -"The basic workflow for using a signing certificate issued by an external CA " -"involves:" -msgstr "" - -#: ../compute-networking-nova.rst:188 -msgid "" -"The behavior of dnsmasq can be customized by creating a dnsmasq " -"configuration file. Specify the configuration file using the " -"``dnsmasq_config_file`` configuration option:" -msgstr "" - -#: ../dashboard_sessions.rst:200 -msgid "" -"The biggest downside is that it places session data into storage on the " -"user's machine and transports it over the wire. It also limits the quantity " -"of session data that can be stored." -msgstr "" - -#: ../compute-remote-console-access.rst:75 -msgid "The browser or client connects to the proxy." -msgstr "" - -#: ../blockstorage_image_volume_cache.rst:18 -msgid "" -"The cache itself is configurable per back end and will contain the most " -"recently used images." -msgstr "" - -#: ../telemetry-data-collection.rst:786 -msgid "The calculation is limited to meters with the same interval." -msgstr "" - -#: ../telemetry-data-collection.rst:253 -msgid "The ceilometer-polling service is available since Kilo release." -msgstr "" - -#: ../telemetry-data-collection.rst:280 -msgid "" -"The central agent does not need direct database connection. The samples " -"collected by this agent are sent via AMQP to the collector service or any " -"external service, which is responsible for persisting the data into the " -"configured database back end." -msgstr "" - -#: ../keystone_certificates_for_pki.rst:20 -msgid "" -"The certificates can be world readable, but the private key cannot be. The " -"private key should only be readable by the account that is going to sign " -"tokens. When generating files with the :command:`keystone-manage pki_setup` " -"command, your best option is to run as the pki user. If you run :command:" -"`keystone-manage` as root, you can append :option:`--keystone-user` and :" -"option:`--keystone-group` parameters to set the user name and group keystone " -"is going to run under." -msgstr "" - -#: ../telemetry-alarms.rst:272 -msgid "" -"The change will take effect from the next evaluation cycle, which by default " -"occurs every minute." -msgstr "" - -#: ../blockstorage_glusterfs_backend.rst:11 -msgid "" -"The cinder volume service is named ``openstack-cinder-volume`` on the " -"following distributions:" -msgstr "" - -#: ../ts_cinder_config.rst:16 -msgid "" -"The cinder-api log is useful for determining if you have endpoint or " -"connectivity issues. If you send a request to create a volume and it fails, " -"review the cinder-api log to determine whether the request made it to the " -"Block Storage service. If the request is logged and you see no errors or " -"tracebacks, check the cinder-volume log for errors or tracebacks." -msgstr "" - -#: ../compute-images-instances.rst:162 -msgid "" -"The cloud administrator and the image owner can define additional " -"properties, such as licensing and billing information." -msgstr "" - -#: ../compute-images-instances.rst:165 -msgid "" -"The cloud administrator can configure any property as protected, which " -"limits which policies or user roles can perform CRUD operations on that " -"property. Protected properties are generally additional properties to which " -"only cloud administrators have access." -msgstr "" - -#: ../networking_use.rst:93 -msgid "" -"The cloud administrator can run any :command:`neutron` command on behalf of " -"tenants by specifying an Identity ``tenant_id`` in the command, as follows:" -msgstr "" - -#: ../compute-images-instances.rst:159 -msgid "" -"The cloud administrator defines core properties, such as the image name." -msgstr "" - -#: ../objectstorage_components.rst:224 -msgid "" -"The cluster eventually has a consistent behavior where the newest data has a " -"priority." -msgstr "" - -#: ../objectstorage_characteristics.rst:19 -msgid "" -"The cluster scales by adding additional nodes without sacrificing " -"performance, which allows a more cost-effective linear storage expansion " -"than fork-lift upgrades." -msgstr "" - -#: ../telemetry-best-practices.rst:99 -msgid "" -"The collection service provided by the Telemetry project is not intended to " -"be an archival service. Set a Time to Live (TTL) value to expire data and " -"minimize the database size. If you would like to keep your data for longer " -"time period, you may consider storing it in a data warehouse outside of " -"Telemetry." -msgstr "" - -#: ../telemetry-data-retrieval.rst:439 -msgid "" -"The command line client library provides python bindings in order to use the " -"Telemetry Python API directly from python programs." -msgstr "" - -#: ../objectstorage_components.rst:5 -msgid "" -"The components that enable Object Storage to deliver high availability, high " -"durability, and high concurrency are:" -msgstr "" - -#: ../compute-remote-console-access.rst:81 -msgid "" -"The compute host specifies the address that the proxy should use to connect " -"through the :file:`nova.conf` file option, " -"``vncserver_proxyclient_address``. In this way, the VNC proxy works as a " -"bridge between the public network and private host network." -msgstr "" - -#: ../compute-security.rst:29 -msgid "The compute node BIOS, hypervisor, and operating system are measured." -msgstr "" - -#: ../compute-images-instances.rst:70 -msgid "" -"The compute node connects to the attached ``cinder-volume`` using ISCSI. The " -"``cinder-volume`` is mapped to the third disk, labeled ``vdc`` in this " -"diagram. After the compute node provisions the vCPU and memory resources, " -"the instance boots up from root volume ``vda``. The instance runs, and " -"changes data on the disks (highlighted in red on the diagram). If the volume " -"store is located on a separate network, the ``my_block_storage_ip`` option " -"specified in the storage node configuration file directs image traffic to " -"the compute node." -msgstr "" - -#: ../blockstorage-manage-volumes.rst:33 -msgid "" -"The compute node, which runs the instance, now has an active iSCSI session " -"and new local storage (usually a :file:`/dev/sdX` disk)." -msgstr "" - -#: ../database.rst:110 ../database.rst:149 -msgid "The configuration file to use." -msgstr "" - -#: ../blockstorage_multi_backend.rst:36 -msgid "" -"The configuration group name is not related to the ``volume_backend_name``." -msgstr "" - -#: ../compute-remote-console-access.rst:227 -msgid "" -"The configuration option parameter should point to your :file:`nova.conf` " -"file, which includes the message queue server address and credentials." -msgstr "" - -#: ../blockstorage-driver-filter-weighing.rst:216 -msgid "The consistency group ID" -msgstr "" - -#: ../telemetry-events.rst:72 -msgid "" -"The conversion from notifications to events is driven by a configuration " -"file defined by the ``definitions_cfg_file`` in the :file:`ceilometer.conf` " -"configuration file." -msgstr "" - -#: ../keystone_caching_layer.rst:86 -msgid "" -"The create, update, and delete actions for domains, projects and roles will " -"perform proper invalidations of the cached methods listed above." -msgstr "" - -#: ../telemetry-system-architecture.rst:181 -msgid "" -"The creation of alarm definitions also highly depends on the role of the " -"user, who initiated the action. Further details about :ref:`telemetry-" -"alarms` handling can be found in this guide." -msgstr "" - -#: ../compute-node-down.rst:63 -msgid "" -"The credentials for your database can be found in :file:`/etc/nova.conf`." -msgstr "" - -#: ../networking_arch.rst:64 -msgid "" -"The dashboard (horizon) integrates with the Networking API, enabling " -"administrators and tenant users to create and manage network services " -"through a web-based GUI." -msgstr "" - -#: ../ts-eql-volume-size.rst:168 -msgid "" -"The dashboard suggests a suitable size when you create a new volume based on " -"a volume-backed image." -msgstr "" - -#: ../dashboard_sessions.rst:8 -msgid "" -"The dashboard uses `Django sessions framework `__ to handle user session data. However, " -"you can use any available session back end. You customize the session back " -"end through the ``SESSION_ENGINE`` setting in your :file:`local_settings` " -"file (on Fedora/RHEL/ CentOS: :file:`/etc/openstack-dashboard/" -"local_settings`, on Ubuntu and Debian: :file:`/etc/openstack-dashboard/" -"local_settings.py`, and on openSUSE: :file:`/srv/www/openstack-dashboard/" -"openstack_dashboard/local/local_settings.py`)." -msgstr "" - -#: ../objectstorage_components.rst:259 -msgid "" -"The data is then sent to each storage node where it is placed in the " -"appropriate partition. At least two of the three writes must be successful " -"before the client is notified that the upload was successful." -msgstr "" - -#: ../compute-service-groups.rst:37 -msgid "" -"The database contains data that is both transient (such as whether the node " -"is alive) and persistent (such as entries for VM owners). With the " -"ServiceGroup abstraction, Compute can treat each type separately." -msgstr "" - -#: ../compute-node-down.rst:201 -msgid "The database has not been updated." -msgstr "" - -#: ../compute-node-down.rst:88 -msgid "" -"The database update and :command:`nova reboot` command should be all that is " -"required to recover a VM from a failed host. However, if you continue to " -"have problems try recreating the network filter configuration using " -"``virsh``, restarting the Compute services, or updating the ``vm_state`` and " -"``power_state`` in the Compute database." -msgstr "" - -#: ../identity_service_api_protection.rst:115 -msgid "" -"The default :file:`policy.json` file supplied provides a somewhat basic " -"example of API protection, and does not assume any particular use of " -"domains. Refer to :file:`policy.v3cloudsample.json` as an example of multi-" -"domain configuration installations where a cloud provider wants to delegate " -"administration of the contents of a domain to a particular :code:`admin " -"domain`. This example policy file also shows the use of an :code:" -"`admin_domain` to allow a cloud provider to enable cloud administrators to " -"have wider access across the APIs." -msgstr "" - -#: ../identity_concepts.rst:173 -msgid "" -"The default :file:`policy.json` files in the Compute, Identity, and Image " -"services recognize only the ``admin`` role. Any user with any role in a " -"tenant can access all operations that do not require the ``admin`` role." -msgstr "" - -#: ../compute-networking-nova.rst:498 -msgid "" -"The default Compute service settings assume that ``nova-network`` and ``nova-" -"api`` are running on the same host. If this is not the case, in the :file:`/" -"etc/nova/nova.conf` file on the host running ``nova-network``, set the " -"``metadata_host`` configuration option to the IP address of the host where " -"nova-api is running." -msgstr "" - -#: ../blockstorage-manage-volumes.rst:5 -msgid "" -"The default OpenStack Block Storage service implementation is an iSCSI " -"solution that uses Logical Volume Manager (LVM) for Linux." -msgstr "" - -#: ../blockstorage_glusterfs_backend.rst:62 -msgid "" -"The default UID and GID of the ``cinder`` user is 165 on most distributions." -msgstr "" - -#: ../networking_auth.rst:19 -msgid "" -"The default authorization settings only allow administrative users to create " -"resources on behalf of a different tenant. Networking uses information " -"received from Identity to authorize user requests. Networking handles two " -"kind of authorization policies:" -msgstr "" - -#: ../telemetry-events.rst:86 -msgid "" -"The default definition file included with the Telemetry module contains a " -"list of known notifications and useful traits. The mappings provided can be " -"modified to include more or less data according to user requirements." -msgstr "" - -#: ../compute-images-instances.rst:296 -msgid "The default is ``roles``." -msgstr "" - -#: ../blockstorage-lio-iscsi-support.rst:5 -msgid "" -"The default mode for the ``iscsi_helper`` tool is ``tgtadm``. To use LIO " -"iSCSI, install the ``python-rtslib`` package, and set " -"``iscsi_helper=lioadm`` in the :file:`cinder.conf` file." -msgstr "" - -#: ../objectstorage_ringbuilder.rst:67 -msgid "" -"The default overload factor is 0, so device weights are strictly followed." -msgstr "" - -#: ../networking_auth.rst:127 -msgid "" -"The default policy that is always evaluated if an API operation does not " -"match any of the policies in ``policy.json``." -msgstr "" - -#: ../telemetry-data-retrieval.rst:584 -msgid "" -"The default publisher is ``notifier``, without any additional options " -"specified. A sample ``publishers`` section in the :file:`/etc/ceilometer/" -"pipeline.yaml` looks like the following::" -msgstr "" - -#: ../networking_config-identity.rst:243 -msgid "" -"The default value of an empty string in both files will allow metadata to " -"function, but will not be secure if any non-trusted entities have access to " -"the metadata APIs exposed by nova-api." -msgstr "" - -#: ../telemetry-data-collection.rst:860 -msgid "" -"The definition above shows a simple meter definition with some fields, from " -"which ``name``, ``event_type``, ``type``, ``unit``, and ``volume`` are " -"required. If there is a match on the event type, samples are generated for " -"the meter." -msgstr "" - -#: ../telemetry-data-collection.rst:679 -msgid "" -"The definition for the disk I/O rate, which is also generated by the rate of " -"change transformer::" -msgstr "" - -#: ../telemetry-alarms.rst:28 -msgid "" -"The definition of an alarm provides the rules that govern when a state " -"transition should occur, and the actions to be taken thereon. The nature of " -"these rules depend on the alarm type." -msgstr "" - -#: ../telemetry-data-collection.rst:648 -msgid "The definition of transformers can contain the following fields:" -msgstr "" - -#: ../keystone_use_trusts.rst:27 -msgid "" -"The delegated privileges are a combination of a tenant ID and a number of " -"roles that must be a subset of the roles assigned to the trustor." -msgstr "" - -#: ../keystone_use_trusts.rst:21 -msgid "The delegation parameters are:" -msgstr "" - -#: ../keystone_caching_layer.rst:55 -msgid "" -"The delete token API calls invalidate the cache for the tokens being acted " -"upon, as well as invalidating the cache for the revoked token list and the " -"validate/check token calls." -msgstr "" - -#: ../blockstorage-consistency-groups.rst:123 -msgid "The details of consistency group operations are shown in the following." -msgstr "" - -#: ../objectstorage-monitoring.rst:238 -msgid "" -"The development team of StatsD wanted to use the `pystatsd `__ client library (not to be confused with a `similar-" -"looking project `__ also hosted on " -"GitHub), but the released version on PyPI was missing two desired features " -"the latest version in GitHub had: the ability to configure a meters prefix " -"in the client object and a convenience method for sending timing data " -"between \"now\" and a \"start\" timestamp you already have. So they just " -"implemented a simple StatsD client library from scratch with the same " -"interface. This has the nice fringe benefit of not introducing another " -"external library dependency into Object Storage." -msgstr "" - -#: ../networking_arch.rst:78 -msgid "" -"The diagrams below depict some VMware NSX deployment examples. The first " -"diagram illustrates the traffic flow between VMs on separate Compute nodes, " -"and the second diagram between two VMs on a single Compute node. Note the " -"placement of the VMware NSX plug-in and the neutron-server service on the " -"network node. The green arrow indicates the management relationship between " -"the NSX controller and the network node." -msgstr "" - -#: ../telemetry-data-collection.rst:49 -msgid "" -"The different OpenStack services emit several notifications about the " -"various types of events that happen in the system during normal operation. " -"Not all these notifications are consumed by the Telemetry module, as the " -"intention is only to capture the billable events and notifications that can " -"be used for monitoring or profiling purposes. The notification agent filters " -"by the event type, that is contained by each notification message. The " -"following table contains the event types by each OpenStack service that are " -"transformed to samples by Telemetry." -msgstr "" - -#: ../compute-flavors.rst:145 -msgid "The disk I/O options are:" -msgstr "" - -#: ../blockstorage-driver-filter-weighing.rst:177 -msgid "The display name of the volume" -msgstr "" - -# #-#-#-#-# compute_arch.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -# #-#-#-#-# compute-images-instances.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -#: ../compute_arch.rst:258 ../compute-images-instances.rst:364 -msgid "The displayed image attributes are:" -msgstr "" - -#: ../orchestration-stack-domain-users.rst:76 -msgid "" -"The domain ID is returned by this command, and is referred to as ``" -"$HEAT_DOMAIN_ID`` below." -msgstr "" - -#: ../blockstorage-driver-filter-weighing.rst:18 -msgid "" -"The driver filter and weigher gives you the ability to more finely control " -"how the OpenStack Block Storage scheduler chooses the best back end to use " -"when handling a volume request. One example scenario where using the driver " -"filter and weigher can be if a back end that utilizes thin-provisioning is " -"used. The default filters use the ``free capacity`` property to determine " -"the best back end, but that is not always perfect. If a back end has the " -"ability to provide a more accurate back-end specific value you can use that " -"as part of the weighing. Another example of when the driver filter and " -"weigher can prove useful is if a back end exists where there is a hard limit " -"of 1000 volumes. The maximum volume size is 500 GB. Once 75% of the total " -"space is occupied the performance of the back end degrades. The driver " -"filter and weigher can provide a way for these limits to be checked for." -msgstr "" - -#: ../compute-service-groups.rst:29 -msgid "" -"The driver has limitations, which can be problematic depending on your " -"environment. If a lot of compute worker nodes need to be checked, the " -"database can be put under heavy load, which can cause the timeout to " -"trigger, and a live node could incorrectly be considered dead. By default, " -"the timeout is 60 seconds. Reducing the timeout value can help in this " -"situation, but you must also make the database update more frequently, which " -"again increases the database workload." -msgstr "" - -#: ../blockstorage-driver-filter-weighing.rst:143 -msgid "The driver version" -msgstr "" - -#: ../objectstorage_EC.rst:24 -msgid "" -"The erasure code support in Object Storage is considered beta in Kilo. Most " -"major functionality is included, but it has not been tested or validated at " -"large scale. This feature relies on `ssync` for durability. We recommend " -"deployers do extensive testing and not deploy production data using an " -"erasure code storage policy. If any bugs are found during testing, please " -"report them to https://bugs.launchpad.net/swift" -msgstr "" - -#: ../telemetry-events.rst:107 -msgid "" -"The event definitions file is in YAML format. It consists of a list of event " -"definitions, which are mappings. Order is significant, the list of " -"definitions is scanned in reverse order to find a definition which matches " -"the notification's event\\_type. That definition will be used to generate " -"the event. The reverse ordering is done because it is common to want to have " -"a more general wildcarded definition (such as ``compute.instance.*``) with a " -"set of traits common to all of those events, with a few more specific event " -"definitions afterwards that have all of the above traits, plus a few more." -msgstr "" - -#: ../telemetry-data-collection.rst:641 -msgid "The event filter uses the same filtering logic as the meter pipeline." -msgstr "" - -#: ../telemetry-events.rst:66 -msgid "" -"The event format is meant for efficient processing and querying. Storage of " -"complete notifications for auditing purposes can be enabled by configuring " -"``store_raw`` option." -msgstr "" - -#: ../networking_introduction.rst:165 -msgid "" -"The example diagram illustrates the flow of ingress and egress traffic for " -"the VM2 instance:" -msgstr "" - -#: ../blockstorage_over_subscription.rst:38 -msgid "" -"The existing ``reserved_percentage`` flag is used to prevent over " -"provisioning. This flag represents the percentage of the back-end capacity " -"that is reserved." -msgstr "" - -#: ../telemetry-data-retrieval.rst:79 -msgid "" -"The filter expressions of the complex query feature operate on the fields of " -"``Sample``, ``Alarm`` and ``AlarmChange`` types. The following comparison " -"operators are supported:" -msgstr "" - -#: ../compute-root-wrap-reference.rst:81 -msgid "" -"The filters definition files contain lists of filters that rootwrap will use " -"to allow or deny a specific command. They are generally suffixed by ``." -"filters`` . Since they are in the trusted security path, they need to be " -"owned and writable only by the root user. Their location is specified in " -"the :file:`rootwrap.conf` file." -msgstr "" - -#: ../networking_introduction.rst:269 -msgid "" -"The firewall remains in PENDING\\_CREATE state until you create a Networking " -"router and attach an interface to it." -msgstr "" - -#: ../blockstorage_volume_backups.rst:50 -msgid "" -"The first backup of a volume has to be a full backup. Attempting to do an " -"incremental backup without any existing backups will fail. There is an " -"``is_incremental`` flag that indicates whether a backup is incremental when " -"showing details on the backup. Another flag, ``has_dependent_backups``, " -"returned when showing backup details, will indicate whether the backup has " -"dependent backups. If it is true, attempting to delete this backup will fail." -msgstr "" - -#: ../telemetry-data-retrieval.rst:442 -msgid "" -"The first step in setting up the client is to create a client instance with " -"the proper credentials::" -msgstr "" - -#: ../identity_troubleshoot.rst:43 -msgid "" -"The first thing to check is that the ``signing_dir`` does, in fact, exist. " -"If it does, check for certificate files:" -msgstr "" - -#: ../keystone_external_authentication.rst:24 -msgid "" -"The following Apache configuration snippet authenticates the user based on a " -"valid X.509 certificate from a known CA::" -msgstr "" - -#: ../networking_use.rst:277 -msgid "" -"The following Debian/Ubuntu-based example shows how to set up the interfaces " -"within the instance in the ``/etc/network/interfaces`` file. You must apply " -"this configuration to the image." -msgstr "" - -#: ../telemetry-best-practices.rst:4 -msgid "" -"The following are some suggested best practices to follow when deploying and " -"configuring the Telemetry service. The best practices are divided into data " -"collection and storage." -msgstr "" - -#: ../telemetry-data-retrieval.rst:249 -msgid "" -"The following command needs to be invoked to request the meters of one VM " -"instance::" -msgstr "" - -#: ../networking_multi-dhcp-agents.rst:142 -msgid "" -"The following commands require the tenant running the command to have an " -"admin role." -msgstr "" - -#: ../blockstorage-consistency-groups.rst:59 -msgid "The following consistency group operations are supported:" -msgstr "" - -#: ../blockstorage_glusterfs_backend.rst:133 -msgid "The following distributions include ``openstack-config``:" -msgstr "" - -#: ../blockstorage_nfs_backend.rst:71 -msgid "The following distributions include openstack-config:" -msgstr "" - -#: ../telemetry-measurements.rst:1319 -msgid "The following energy related meters are available:" -msgstr "" - -#: ../keystone_caching_layer.rst:123 -msgid "The following example shows how to configure the memcached back end:" -msgstr "" - -#: ../telemetry-measurements.rst:426 -msgid "" -"The following host machine related meters are collected for OpenStack " -"Compute:" -msgstr "" - -#: ../telemetry-system-architecture.rst:115 -msgid "" -"The following hypervisors are supported via `Libvirt `__:" -msgstr "" - -#: ../telemetry-data-retrieval.rst:95 -msgid "The following logical operators can be used:" -msgstr "" - -#: ../telemetry-measurements.rst:585 -msgid "" -"The following meters are available about the host machines by using SNMP:" -msgstr "" - -#: ../telemetry-measurements.rst:799 -msgid "The following meters are collected for Ceph Object Storage:" -msgstr "" - -#: ../telemetry-measurements.rst:1199 -msgid "The following meters are collected for FWaaS:" -msgstr "" - -#: ../telemetry-measurements.rst:1056 -msgid "The following meters are collected for LBaaS:" -msgstr "" - -#: ../telemetry-measurements.rst:694 -msgid "The following meters are collected for OpenStack Block Storage:" -msgstr "" - -#: ../telemetry-measurements.rst:94 -msgid "The following meters are collected for OpenStack Compute:" -msgstr "" - -#: ../telemetry-measurements.rst:836 -msgid "The following meters are collected for OpenStack Identity:" -msgstr "" - -#: ../telemetry-measurements.rst:661 -msgid "The following meters are collected for OpenStack Image service:" -msgstr "" - -#: ../telemetry-measurements.rst:907 -msgid "The following meters are collected for OpenStack Networking:" -msgstr "" - -#: ../telemetry-measurements.rst:749 -msgid "The following meters are collected for OpenStack Object Storage:" -msgstr "" - -#: ../telemetry-measurements.rst:970 -msgid "The following meters are collected for SDN:" -msgstr "" - -#: ../telemetry-measurements.rst:1134 -msgid "The following meters are collected for VPNaaS:" -msgstr "" - -#: ../telemetry-measurements.rst:1275 -msgid "" -"The following meters are collected for the Data processing service for " -"OpenStack:" -msgstr "" - -#: ../telemetry-measurements.rst:1299 -msgid "The following meters are collected for the Key Value Store module:" -msgstr "" - -#: ../telemetry-measurements.rst:1250 -msgid "The following meters are collected for the Orchestration module:" -msgstr "" - -#: ../telemetry-measurements.rst:481 -msgid "The following meters are recorded for the Bare metal service:" -msgstr "" - -#: ../blockstorage-consistency-groups.rst:99 -msgid "" -"The following operations are not allowed if a volume is in a consistency " -"group:" -msgstr "" - -#: ../blockstorage-consistency-groups.rst:113 -msgid "" -"The following operations are not allowed if a volume snapshot is in a " -"consistency group snapshot:" -msgstr "" - -#: ../telemetry-data-retrieval.rst:561 -msgid "" -"The following option is additionally available for the ``notifier`` " -"publisher:" -msgstr "" - -#: ../telemetry-data-retrieval.rst:536 -msgid "" -"The following options are available for ``rpc`` and ``notifier``. The policy " -"option can be used by ``kafka`` publisher:" -msgstr "" - -#: ../telemetry-data-retrieval.rst:569 -msgid "The following options are available for the ``file`` publisher:" -msgstr "" - -#: ../dashboard_sessions.rst:142 -msgid "The following output is returned::" -msgstr "" - -#: ../keystone_certificates_for_pki.rst:215 -msgid "" -"The following procedure details how to switch out expired signing " -"certificates with no cloud outages." -msgstr "" - -#: ../blockstorage-driver-filter-weighing.rst:128 -msgid "" -"The following properties and their sub-properties are currently available " -"for use:" -msgstr "" - -#: ../telemetry-data-retrieval.rst:492 -msgid "The following publisher types are supported:" -msgstr "" - -#: ../compute-configuring-migrations.rst:45 -msgid "" -"The following sections describe how to configure your hosts and compute " -"nodes for migrations by using the KVM and XenServer hypervisors." -msgstr "" - -#: ../dashboard_sessions.rst:17 -msgid "" -"The following sections describe the pros and cons of each option as it " -"pertains to deploying the dashboard." -msgstr "" - -#: ../objectstorage_components.rst:243 -msgid "" -"The following sections show use cases for object uploads and downloads and " -"introduce the components." -msgstr "" - -#: ../telemetry-data-collection.rst:263 -msgid "The following services can be polled with this agent:" -msgstr "" - -#: ../orchestration-auth-model.rst:33 -msgid "The following steps are executed for password authorization:" -msgstr "" - -#: ../orchestration-auth-model.rst:86 -msgid "The following steps are executed for trusts authorization:" -msgstr "" - -#: ../orchestration-stack-domain-users.rst:108 -msgid "The following steps will be executed during stack creation:" -msgstr "" - -#: ../blockstorage-consistency-groups.rst:261 -msgid "" -"The force flag is needed when there are volumes in the consistency group::" -msgstr "" - -#: ../telemetry-events.rst:56 -msgid "" -"The general philosophy of notifications in OpenStack is to emit any and all " -"data someone might need, and let the consumer filter out what they are not " -"interested in. In order to make processing simpler and more efficient, the " -"notifications are stored and processed within Ceilometer as events. The " -"notification payload, which can be an arbitrarily complex JSON data " -"structure, is converted to a flat set of key-value pairs. This conversion is " -"specified by a config file." -msgstr "" - -#: ../compute-configuring-migrations.rst:387 -msgid "The host is now part of a XenServer pool." -msgstr "" - -#: ../blockstorage-driver-filter-weighing.rst:134 -msgid "The host's name" -msgstr "" - -#: ../compute-node-down.rst:186 -msgid "The iSCSI session from the SAN to the cloud no longer exists." -msgstr "" - -#: ../compute-node-down.rst:188 -msgid "" -"The iSCSI session from the cloud controller to the compute node no longer " -"exists." -msgstr "" - -#: ../blockstorage_volume_backups.rst:43 -msgid "" -"The incremental backup is based on a parent backup which is an existing " -"backup with the latest timestamp. The parent backup can be a full backup or " -"an incremental backup depending on the timestamp." -msgstr "" - -#: ../telemetry-alarms.rst:181 -msgid "The initial alarm state (defaults to ``insufficient data``)." -msgstr "" - -#: ../objectstorage_replication.rst:76 -msgid "" -"The initial implementation of object replication performed an rsync to push " -"data from a local partition to all remote servers where it was expected to " -"reside. While this worked at small scale, replication times skyrocketed once " -"directory structures could no longer be held in RAM. This scheme was " -"modified to save a hash of the contents for each suffix directory to a per-" -"partition hashes file. The hash for a suffix directory is no longer valid " -"when the contents of that suffix directory is modified." -msgstr "" - -#: ../networking_config-plugins.rst:98 -msgid "" -"The instructions in this section refer to the VMware NSX-mh platform, " -"formerly known as Nicira NVP." -msgstr "" - -#: ../telemetry-data-collection.rst:183 -msgid "" -"The instructions on how to install this middleware can be found in " -"`Configure the Object Storage service for Telemetry `__ section " -"in the OpenStack Installation Guide." -msgstr "" - -#: ../compute-networking-nova.rst:146 -msgid "" -"The internal network interface is used for communication with VMs. The " -"interface should not have an IP address attached to it before OpenStack " -"installation, it serves only as a fabric where the actual endpoints are VMs " -"and dnsmasq. Additionally, the internal network interface must be in " -"``promiscuous`` mode, so that it can receive packets whose target MAC " -"address is the guest VM, not the host." -msgstr "" - -#: ../telemetry-data-collection.rst:552 -msgid "" -"The interval parameter in the sources section should be defined in seconds. " -"It determines the polling cadence of sample injection into the pipeline, " -"where samples are produced under the direct control of an agent." -msgstr "" - -#: ../compute-node-down.rst:191 -msgid "" -"The iptables and ebtables from the cloud controller to the compute node are " -"recreated. This is because nova-network reapplies configurations on boot." -msgstr "" - -#: ../objectstorage_characteristics.rst:5 -msgid "The key characteristics of Object Storage are that:" -msgstr "" - -#: ../telemetry-data-collection.rst:1006 -msgid "The level of support differs in case of the configured back end:" -msgstr "" - -#: ../telemetry-data-collection.rst:412 -msgid "" -"The list of collected meters can be found in :ref:`telemetry-bare-metal-" -"service`." -msgstr "" - -#: ../telemetry-data-collection.rst:309 -msgid "" -"The list of collected meters can be found in :ref:`telemetry-compute-" -"meters`. The support column provides the information that which meter is " -"available for each hypervisor supported by the Telemetry module." -msgstr "" - -#: ../telemetry.rst:26 -msgid "" -"The list of meters is continuously growing, which makes it possible to use " -"the data collected by Telemetry for different purposes, other than billing. " -"For example, the autoscaling feature in the Orchestration module can be " -"triggered by alarms this module sets and then gets notified within Telemetry." -msgstr "" - -#: ../telemetry-system-architecture.rst:83 -msgid "The list of supported database back ends:" -msgstr "" - -#: ../telemetry-data-collection.rst:303 -msgid "" -"The list of supported hypervisors can be found in :ref:`telemetry-supported-" -"hypervisors`. The compute agent uses the API of the hypervisor installed on " -"the compute hosts. Therefore the supported meters may be different in case " -"of each virtualization back end, as each inspection tool provides a " -"different set of meters." -msgstr "" - -#: ../telemetry-system-architecture.rst:113 -msgid "The list of supported hypervisors is:" -msgstr "" - -#: ../dashboard_sessions.rst:29 -msgid "" -"The local memory back end is enabled as the default for Horizon solely " -"because it has no dependencies. It is not recommended for production use, or " -"even for serious development work. Enabled by::" -msgstr "" - -#: ../telemetry-troubleshooting-guide.rst:11 -msgid "" -"The log settings can be changed in :file:`ceilometer.conf`. The list of " -"configuration options are listed in the logging configuration options table " -"in the `Telemetry section `__ in the *OpenStack " -"Configuration Reference*." -msgstr "" - -#: ../compute-manage-logs.rst:21 -msgid "" -"The logging configuration file is an INI-style configuration file, which " -"must contain a section called ``logger_nova``. This controls the behavior of " -"the logging facility in the ``nova-*`` services. For example:" -msgstr "" - -#: ../identity_troubleshoot.rst:13 -msgid "" -"The logs show the components that have come in to the WSGI request, and " -"ideally show an error that explains why an authorization request failed. If " -"you do not see the request in the logs, run keystone with the :option:`--" -"debug` parameter. Pass the :option:`--debug` parameter before the command " -"parameters." -msgstr "" - -#: ../objectstorage_replication.rst:40 -msgid "The main replication types are:" -msgstr "" - -#: ../telemetry-data-collection.rst:10 -msgid "" -"The main responsibility of Telemetry in OpenStack is to collect information " -"about the system that can be used by billing systems or interpreted by " -"analytic tooling. The original focus, regarding to the collected data, was " -"on the counters that can be used for billing, but the range is getting wider " -"continuously." -msgstr "" - -#: ../telemetry-events.rst:80 -msgid "" -"The mapping of notifications to events is defined per event\\_type, which " -"can be wildcarded. Traits are added to events if the corresponding fields in " -"the notification exist and are non-null." -msgstr "" - -#: ../telemetry-data-collection.rst:484 -msgid "" -"The mechanism by which data is collected and processed is called a pipeline. " -"Pipelines, at the configuration level, describe a coupling between sources " -"of data and the corresponding sinks for transformation and publication of " -"data." -msgstr "" - -#: ../compute-service-groups.rst:91 -msgid "" -"The memcache ServiceGroup driver uses memcached, a distributed memory object " -"caching system that is used to increase site performance. For more details, " -"see `memcached.org `_." -msgstr "" - -#: ../keystone_caching_layer.rst:111 -msgid "" -"The memory back end is not suitable for use in a production environment." -msgstr "" - -#: ../compute-networking-nova.rst:404 -msgid "" -"The metadata service has an API that is compatible with version 2009-04-04 " -"of the `Amazon EC2 metadata service `__. This means " -"that virtual machine images designed for EC2 will work properly with " -"OpenStack." -msgstr "" - -#: ../compute-networking-nova.rst:472 -msgid "" -"The metadata service is implemented by either the nova-api service or the " -"nova-api-metadata service. Note that the nova-api-metadata service is " -"generally only used when running in multi-host mode, as it retrieves " -"instance-specific metadata. If you are running the nova-api service, you " -"must have ``metadata`` as one of the elements listed in the ``enabled_apis`` " -"configuration option in :file:`/etc/nova/nova.conf`. The default " -"``enabled_apis`` configuration setting includes the metadata service, so you " -"should not need to modify it." -msgstr "" - -#: ../telemetry-data-collection.rst:534 -msgid "The meter pipeline definition looks like the following::" -msgstr "" - -#: ../networking_adv-config.rst:44 -msgid "" -"The metering agent and the L3 agent must have the same network namespaces " -"configuration." -msgstr "" - -#: ../telemetry-data-retrieval.rst:451 -msgid "The method calls look like the following::" -msgstr "" - -#: ../identity_auth_token_middleware.rst:41 -msgid "" -"The middleware parameters in the paste config take priority. You must remove " -"them to use the values in the ``[keystone_authtoken]`` section." -msgstr "" - -#: ../blockstorage_volume_migration.rst:190 -msgid "" -"The migration is not visible to non-admin users (for example, through the " -"volume ``status``). However, some operations are not allowed while a " -"migration is taking place, such as attaching/detaching a volume and deleting " -"a volume. If a user performs such an action during a migration, an error is " -"returned." -msgstr "" - -#: ../compute-configuring-migrations.rst:22 -msgid "The migration types are:" -msgstr "" - -#: ../objectstorage-monitoring.rst:32 -msgid "The most recent object replication time." -msgstr "" - -#: ../compute-networking-nova.rst:765 -msgid "" -"The multinic feature allows you to use more than one interface with your " -"instances. This is useful in several scenarios:" -msgstr "" - -#: ../blockstorage_multi_backend.rst:20 -msgid "" -"The name of the back end is declared as an extra-specification of a volume " -"type (such as, ``volume_backend_name=LVM``). When a volume is created, the " -"scheduler chooses an appropriate back end to handle the request, according " -"to the volume type specified by the user." -msgstr "" - -#: ../database.rst:153 -msgid "" -"The name of the datastore you just created via trove-manage :command:" -"`datastore_update`." -msgstr "" - -#: ../networking_adv-features.rst:147 -msgid "" -"The name of the physical network over which the virtual network is " -"implemented for flat and VLAN networks. Not applicable to the ``local`` or " -"``gre`` network types." -msgstr "" - -#: ../database.rst:158 -msgid "The name of the version you are adding to the datastore." -msgstr "" - -#: ../ts-failed-connect-vol-FC-SAN.rst:29 -msgid "" -"The network administrator must configure the FC SAN fabric by correctly " -"zoning the WWN (port names) from your compute node HBAs." -msgstr "" - -#: ../compute-networking-nova.rst:30 -msgid "" -"The network controller with ``nova-network`` provides virtual networks to " -"enable compute servers to interact with each other and with the public " -"network. Compute with ``nova-network`` supports the following network modes, " -"which are implemented as Network Manager types:" -msgstr "" - -#: ../blockstorage-manage-volumes.rst:47 -msgid "" -"The network mode does not interfere with OpenStack Block Storage operations, " -"but you must set up networking for Block Storage to work. For details, see :" -"ref:`networking`." -msgstr "" - -#: ../networking_adv-features.rst:702 -msgid "" -"The network that a packet's destination IP must match for the rule to be " -"applied." -msgstr "" - -#: ../networking_adv-features.rst:697 -msgid "" -"The network that a packet's source IP must match for the rule to be applied." -msgstr "" - -#: ../networking_config-plugins.rst:192 -msgid "" -"The neutron NSX-mh plug-in does not implement initial re-synchronization of " -"Neutron resources. Therefore resources that might already exist in the " -"database when Neutron is switched to the NSX-mh plug-in will not be created " -"on the NSX-mh backend upon restart." -msgstr "" - -#: ../networking_config-agents.rst:218 -msgid "" -"The neutron-l3-agent uses the Linux IP stack and iptables to perform L3 " -"forwarding and NAT. In order to support multiple routers with potentially " -"overlapping IP addresses, neutron-l3-agent defaults to using Linux network " -"namespaces to provide isolated forwarding contexts. As a result, the IP " -"addresses of routers are not visible simply by running the :command:`ip addr " -"list` or :command:`ifconfig` command on the node. Similarly, you cannot " -"directly :command:`ping` fixed IPs." -msgstr "" - -#: ../objectstorage-monitoring.rst:118 -msgid "" -"The next section describes another method for gathering Object Storage " -"operational meters." -msgstr "" - -#: ../telemetry-data-retrieval.rst:122 -msgid "The number of returned items can be bounded using the ``limit`` option." -msgstr "" - -#: ../objectstorage_replication.rst:92 -msgid "" -"The number of uncached directories that object replication must traverse, " -"usually as a result of invalidated suffix directory hashes, impedes " -"performance. To provide acceptable replication speeds, object replication is " -"designed to invalidate around 2 percent of the hash space on a normal node " -"each day." -msgstr "" - -#: ../objectstorage_replication.rst:85 -msgid "" -"The object replication process reads in hash files and calculates any " -"invalidated hashes. Then, it transmits the hashes to each remote server that " -"should hold the partition, and only suffix directories with differing hashes " -"on the remote server are rsynced. After pushing files to the remote server, " -"the replication process notifies it to recalculate hashes for the rsynced " -"suffix directories." -msgstr "" - -#: ../compute-service-groups.rst:63 -msgid "The official Zookeeper Python binding" -msgstr "" - -#: ../networking_adv-features.rst:597 -msgid "" -"The operational status synchronization can be tuned or disabled using the " -"configuration options reported in this table; it is however worth noting " -"that the default values work fine in most cases." -msgstr "" - -#: ../blockstorage_volume_backups.rst:138 -msgid "" -"The option ``backup_compression_algorithm`` can be set to ``bz2`` or " -"``None``. The latter can be a useful setting when the server providing the " -"share for the backup repository itself performs deduplication or compression " -"on the backup data." -msgstr "" - -#: ../blockstorage_volume_backups.rst:143 -msgid "" -"The option ``backup_file_size`` must be a multiple of " -"``backup_sha_block_size_bytes``. It is effectively the maximum file size to " -"be used, given your environment, to hold backup data. Volumes larger than " -"this will be stored in multiple files in the backup repository. The " -"``backup_sha_block_size_bytes`` option determines the size of blocks from " -"the cinder volume being backed up on which digital signatures are calculated " -"in order to enable incremental backup capability." -msgstr "" - -#: ../telemetry-data-collection.rst:602 -msgid "" -"The optional resources section of a pipeline source allows a static list of " -"resource URLs to be configured for polling." -msgstr "" - -#: ../blockstorage_multi_backend.rst:49 -msgid "" -"The options for a configuration group must be defined in the group (or " -"default options are used). All the standard Block Storage configuration " -"options (``volume_group``, ``volume_driver``, and so on) might be used in a " -"configuration group. Configuration values in the ``[DEFAULT]`` configuration " -"group are not used." -msgstr "" - -#: ../keystone_integrate_identity_backend_ldap.rst:114 -msgid "" -"The options set in the :file:`/etc/keystone/domains/keystone.DOMAIN_NAME." -"conf` file will override options in the :file:`/etc/keystone/keystone.conf` " -"file." -msgstr "" - -#: ../networking_adv-features.rst:719 -msgid "" -"The order of router rules has no effect. Overlapping rules are evaluated " -"using longest prefix matching on the source and destination fields. The " -"source field is matched first so it always takes higher precedence over the " -"destination field. In other words, longest prefix matching is used on the " -"destination field only if there are multiple matching rules with the same " -"source." -msgstr "" - -#: ../telemetry-system-architecture.rst:75 -msgid "" -"The other key external component of Telemetry is the database, where events, " -"samples, alarm definitions and alarms are stored." -msgstr "" - -#: ../telemetry-measurements.rst:56 -msgid "" -"The other option is to set the ``reserved_metadata_keys`` to the list of " -"metadata keys that you would like to be included in ``resource_metadata`` of " -"the instance related samples that are collected for OpenStack Compute. This " -"option is included in the ``DEFAULT`` section of the :file:`ceilometer.conf` " -"configuration file." -msgstr "" - -#: ../networking_multi-dhcp-agents.rst:307 -msgid "" -"The output shows ``bridge-mapping`` and the number of virtual network " -"devices on this L2 agent." -msgstr "" - -#: ../networking_multi-dhcp-agents.rst:201 -msgid "" -"The output shows information for four agents. The ``alive`` field shows " -"``:-)`` if the agent reported its state within the period defined by the " -"``agent_down_time`` option in the :file:`neutron.conf` file. Otherwise the " -"``alive`` is ``xxx``." -msgstr "" - -#: ../objectstorage_ringbuilder.rst:64 -msgid "" -"The overload factor lets the operator trade off replica dispersion " -"(durability) against data dispersion (uniform disk usage)." -msgstr "" - -#: ../blockstorage-consistency-groups.rst:296 -msgid "" -"The parameter ``CGSNAPSHOT`` is a name or UUID of a snapshot of a " -"consistency group::" -msgstr "" - -#: ../blockstorage-consistency-groups.rst:275 -msgid "" -"The parameter ``CG`` is required. It can be a name or UUID of a consistency " -"group. UUID1,UUID2,...... are UUIDs of one or more volumes to be added to " -"the consistency group, separated by commas. Default is None. UUID3," -"UUId4,...... are UUIDs of one or more volumes to be removed from the " -"consistency group, separated by commas. Default is None." -msgstr "" - -#: ../blockstorage-consistency-groups.rst:309 -msgid "" -"The parameter ``SOURCECG`` is a name or UUID of a source consistency group::" -msgstr "" - -#: ../blockstorage-consistency-groups.rst:135 -msgid "" -"The parameter ``volume-types`` is required. It can be a list of names or " -"UUIDs of volume types separated by commas without spaces in between. For " -"example, ``volumetype1,volumetype2,volumetype3.``." -msgstr "" - -#: ../telemetry-data-collection.rst:656 -msgid "" -"The parameters section can contain transformer specific fields, like source " -"and target fields with different subfields in case of the rate of change, " -"which depends on the implementation of the transformer." -msgstr "" - -#: ../objectstorage_ringbuilder.rst:138 -msgid "" -"The partition shift value is known internally to the Ring class as " -"``_part_shift``. This value is used to shift an MD5 hash to calculate the " -"partition where the data for that hash should reside. Only the top four " -"bytes of the hash is used in this process. For example, to compute the " -"partition for the :file:`/account/container/object` path using Python::" -msgstr "" - -#: ../objectstorage_components.rst:75 -msgid "" -"The partitions of the ring are equally divided among all of the devices in " -"the Object Storage installation. When partitions need to be moved around " -"(for example, if a device is added to the cluster), the ring ensures that a " -"minimum number of partitions are moved at a time, and only one replica of a " -"partition is moved at a time." -msgstr "" - -#: ../telemetry-alarms.rst:160 -msgid "" -"The period length is set to 600s in this case to reflect the out-of-the-box " -"default cadence for collection of the associated meter. This period matching " -"illustrates an important general principal to keep in mind for alarms:" -msgstr "" - -#: ../ts_cinder_config.rst:130 -msgid "The persistent tgt include file." -msgstr "" - -#: ../networking_adv-features.rst:134 -msgid "" -"The physical mechanism by which the virtual network is implemented. Possible " -"values are ``flat``, ``vlan``, ``local``, ``gre``, and ``vxlan``, " -"corresponding to flat networks, VLAN networks, local networks, GRE networks, " -"and VXLAN networks as defined above. All types of provider networks can be " -"created by administrators, while tenant networks can be implemented as " -"``vlan``, ``gre``, ``vxlan``, or ``local`` network types depending on plug-" -"in configuration." -msgstr "" - -#: ../telemetry-measurements.rst:340 -msgid "" -"The physical si\\ ze in bytes of the image conta\\ iner on the hos\\ t per " -"device" -msgstr "" - -#: ../telemetry-measurements.rst:324 -msgid "The physical si\\ ze in bytes of the image conta\\ iner on the host" -msgstr "" - -#: ../networking_auth.rst:34 -msgid "" -"The policy engine reads entries from the :file:`policy.json` file. The " -"actual location of this file might vary from distribution to distribution. " -"Entries can be updated while the system is running, and no service restart " -"is required. Every time the policy file is updated, the policies are " -"automatically reloaded. Currently the only way of updating such policies is " -"to edit the policy file. In this section, the terms *policy* and *rule* " -"refer to objects that are specified in the same way in the policy file. " -"There are no syntax differences between a rule and a policy. A policy is " -"something that is matched directly from the Networking policy engine. A rule " -"is an element in a policy, which is evaluated. For instance in " -"``create_subnet: [[\"admin_or_network_owner\"]]``, *create_subnet* is a " -"policy, and *admin_or_network_owner* is a rule." -msgstr "" - -#: ../telemetry-troubleshooting-guide.rst:41 -msgid "" -"The possibility of this issue to happen is higher, when the polling interval " -"is set to a relatively short period. In order to avoid this situation, the " -"recommended order of service startup is to start or restart the **ceilometer-" -"collector** service after the message queue. All the other Telemetry " -"services should be started or restarted after and the **ceilometer-agent-" -"compute** should be the last in the sequence, as this component emits " -"metering messages in order to send the samples to the collector." -msgstr "" - -#: ../keystone_certificates_for_pki.rst:199 -msgid "" -"The procedure of copying the key and cert files may be improved if done " -"after first running :command:`keystone-manage pki_setup` since this command " -"also creates other needed files, such as the :file:`index.txt` and :file:" -"`serial` files." -msgstr "" - -#: ../identity_concepts.rst:6 -msgid "" -"The process of confirming the identity of a user. To confirm an incoming " -"request, OpenStack Identity validates a set of credentials that the user " -"supplies. Initially, these credentials are a user name and password or a " -"user name and API key. When OpenStack Identity validates user credentials, " -"it issues an authentication token that the user provides in subsequent " -"requests." -msgstr "" - -#: ../blockstorage-driver-filter-weighing.rst:224 -msgid "" -"The property most used from here will most likely be the ``size`` sub-" -"property." -msgstr "" - -#: ../dashboard_sessions.rst:196 -msgid "" -"The pros of this engine are that it requires no additional dependencies or " -"infrastructure overhead, and it scales indefinitely as long as the quantity " -"of session data being stored fits into a normal cookie." -msgstr "" - -#: ../networking_adv-features.rst:27 -msgid "" -"The provider extension allows administrators to explicitly manage the " -"relationship between Networking virtual networks and underlying physical " -"mechanisms such as VLANs and tunnels. When this extension is supported, " -"Networking client users with administrative privileges see additional " -"provider attributes on all virtual networks and are able to specify these " -"attributes in order to create provider networks." -msgstr "" - -#: ../networking_adv-features.rst:119 -msgid "" -"The provider extension extends the Networking network resource with these " -"attributes:" -msgstr "" - -#: ../networking_adv-features.rst:34 -msgid "" -"The provider extension is supported by the Open vSwitch and Linux Bridge " -"plug-ins. Configuration of these plug-ins requires familiarity with this " -"extension." -msgstr "" - -#: ../compute-remote-console-access.rst:89 -msgid "" -"The proxy also tunnels the VNC protocol over WebSockets so that the " -"``noVNC`` client can talk to VNC servers. In general, the VNC proxy:" -msgstr "" - -#: ../compute-remote-console-access.rst:86 -msgid "" -"The proxy initiates the connection to VNC server and continues to proxy " -"until the session ends." -msgstr "" - -#: ../compute-remote-console-access.rst:77 -msgid "" -"The proxy talks to ``nova-consoleauth`` to authorize the token for the user, " -"and maps the token to the *private* host and port of the VNC server for an " -"instance." -msgstr "" - -#: ../telemetry-data-retrieval.rst:476 -msgid "" -"The publisher component makes it possible to persist the data into storage " -"through the message bus or to send it to one or more external consumers. One " -"chain can contain multiple publishers." -msgstr "" - -#: ../telemetry-data-collection.rst:624 -msgid "" -"The publishers section contains the list of publishers, where the samples " -"data should be sent after the possible transformations." -msgstr "" - -#: ../compute-manage-the-cloud.rst:21 -msgid "" -"The python-novaclient package provides a ``nova`` shell that enables Compute " -"API interactions from the command line. Install the client, and provide your " -"user name and password (which can be set as environment variables for " -"convenience), for the ability to administer the cloud from the command line." -msgstr "" - -#: ../telemetry-data-collection.rst:672 -msgid "" -"The rate of change the transformer generates is the ``cpu_util`` meter from " -"the sample values of the ``cpu`` counter, which represents cumulative CPU " -"time in nanoseconds. The transformer definition above defines a scale factor " -"(for nanoseconds and multiple CPUs), which is applied before the " -"transformation derives a sequence of gauge samples with unit '%', from " -"sequential values of the ``cpu`` meter." -msgstr "" - -#: ../networking_adv-features.rst:527 -msgid "" -"The recommended value for this parameter varies with the NSX version running " -"in the back-end, as shown in the following table." -msgstr "" - -#: ../compute-security.rst:25 -msgid "The remote attestation server performs node verification like this:" -msgstr "" - -#: ../objectstorage_ringbuilder.rst:103 -msgid "The replica count is adjustable." -msgstr "" - -#: ../objectstorage_replication.rst:36 -msgid "" -"The replicator does not maintain desired levels of replication when failures " -"such as entire node failures occur; most failures are transient." -msgstr "" - -#: ../objectstorage_components.rst:211 -msgid "" -"The replicator knows if replication needs to take place by examining hashes. " -"A hash file is created for each partition, which contains hashes of each " -"directory in the partition. Each of the three hash files is compared. For a " -"given partition, the hash files for each of the partition's copies are " -"compared. If the hashes are different, then it is time to replicate, and the " -"directory that needs to be replicated is copied over." -msgstr "" - -#: ../telemetry-data-collection.rst:129 -msgid "" -"The required configuration for Block Storage service can be found in the " -"`Add the Block Storage service agent for Telemetry section `__ section in the OpenStack Installation Guide." -msgstr "" - -#: ../telemetry-data-collection.rst:71 -msgid "" -"The required configuration for Image service can be found in `Configure the " -"Image service for Telemetry section `__ section in the " -"OpenStack Installation Guide." -msgstr "" - -#: ../telemetry-data-collection.rst:438 -msgid "" -"The required fields for sending a sample using the command line client are:" -msgstr "" - -#: ../blockstorage-driver-filter-weighing.rst:158 -msgid "The reserved storage percentage" -msgstr "" - -#: ../telemetry-data-retrieval.rst:292 -msgid "" -"The result set of the request contains the samples for both instances " -"ordered by the timestamp field in the default descending order." -msgstr "" - -#: ../objectstorage_ringbuilder.rst:172 -msgid "" -"The ring builder assigns each partition replica to the device that requires " -"most partitions at that point while keeping it as far away as possible from " -"other replicas. The ring builder prefers to assign a replica to a device in " -"a region that does not already have a replica. If no such region is " -"available, the ring builder searches for a device in a different zone, or on " -"a different server. If it does not find one, it looks for a device with no " -"replicas. Finally, if all options are exhausted, the ring builder assigns " -"the replica to the device that has the fewest replicas already assigned." -msgstr "" - -#: ../objectstorage_ringbuilder.rst:184 -msgid "" -"The ring builder assigns multiple replicas to one device only if the ring " -"has fewer devices than it has replicas." -msgstr "" - -#: ../objectstorage_ringbuilder.rst:153 -msgid "The ring builder process includes these high-level steps:" -msgstr "" - -#: ../objectstorage_ringbuilder.rst:202 -msgid "" -"The ring builder reassigns the gathered partitions to devices by using a " -"similar method to the one described previously." -msgstr "" - -#: ../objectstorage_ringbuilder.rst:57 -msgid "" -"The ring builder tries to keep replicas as far apart as possible while still " -"respecting device weights. When it can not do both, the overload factor " -"determines what happens. Each device takes an extra fraction of its desired " -"partitions to allow for replica dispersion; after that extra fraction is " -"exhausted, replicas are placed closer together than optimal." -msgstr "" - -#: ../objectstorage_ringbuilder.rst:193 -msgid "" -"The ring builder unassigns any assigned partitions from any removed devices " -"and adds these partitions to the gathered list." -msgstr "" - -#: ../objectstorage_ringbuilder.rst:195 -msgid "" -"The ring builder unassigns any partition replicas that can be spread out for " -"better durability and adds these partitions to the gathered list." -msgstr "" - -#: ../objectstorage_ringbuilder.rst:190 -msgid "" -"The ring builder unassigns partitions and gathers these partitions for " -"reassignment, as follows:" -msgstr "" - -#: ../objectstorage_ringbuilder.rst:198 -msgid "" -"The ring builder unassigns random partitions from any devices that have more " -"partitions than they need and adds these partitions to the gathered list." -msgstr "" - -#: ../objectstorage_ringbuilder.rst:28 -msgid "" -"The ring data structure consists of three top level fields: a list of " -"devices in the cluster, a list of lists of device ids indicating partition " -"to device assignments, and an integer indicating the number of bits to shift " -"an MD5 hash to calculate the partition for the hash." -msgstr "" - -#: ../objectstorage_components.rst:85 -msgid "" -"The ring is used by the proxy server and several background processes (like " -"replication)." -msgstr "" - -#: ../objectstorage_components.rst:65 -msgid "" -"The ring maintains this mapping using zones, devices, partitions, and " -"replicas. Each partition in the ring is replicated, by default, three times " -"across the cluster, and partition locations are stored in the mapping " -"maintained by the ring. The ring is also responsible for determining which " -"devices are used for handoff in failure scenarios." -msgstr "" - -#: ../objectstorage_components.rst:102 -msgid "" -"The ring uses a configurable number of bits from an MD5 hash for a path as a " -"partition index that designates a device. The number of bits kept from the " -"hash is known as the partition power, and 2 to the partition power indicates " -"the partition count. Partitioning the full MD5 hash ring allows other parts " -"of the cluster to work in batches of items at once which ends up either more " -"efficient or at least less complex than working with each item separately or " -"the entire cluster all at once." -msgstr "" - -#: ../objectstorage_ringbuilder.rst:15 -msgid "" -"The ring-builder also keeps its own builder file with the ring information " -"and additional data required to build future rings. It is very important to " -"keep multiple backup copies of these builder files. One option is to copy " -"the builder files out to every server while copying the ring files " -"themselves. Another is to upload the builder files into the cluster itself. " -"If you lose the builder file, you have to create a new ring from scratch. " -"Nearly all partitions would be assigned to different devices and, therefore, " -"nearly all of the stored data would have to be replicated to new locations. " -"So, recovery from a builder file loss is possible, but data would be " -"unreachable for an extended time." -msgstr "" - -#: ../orchestration-auth-model.rst:71 -msgid "" -"The roles to be delegated (configurable via the ``heat.conf``, but it needs " -"to contain whatever roles are required to perform the deferred operations on " -"the users behalf, for example, launching an OpenStack Compute instance in " -"response to an AutoScaling event)." -msgstr "" - -#: ../compute_arch.rst:134 -msgid "" -"The root disk is associated with an instance, and exists only for the life " -"of this very instance. Generally, it is used to store an instance's root " -"file system, persists across the guest operating system reboots, and is " -"removed on an instance deletion. The amount of the root ephemeral volume is " -"defined by the flavor of an instance." -msgstr "" - -#: ../networking_adv-features.rst:233 -msgid "" -"The router obtains an interface with the gateway_ip address of the subnet " -"and this interface is attached to a port on the L2 Networking network " -"associated with the subnet. The router also gets a gateway interface to the " -"specified external network. This provides SNAT connectivity to the external " -"network as well as support for floating IPs allocated on that external " -"networks. Commonly an external network maps to a network in the provider." -msgstr "" - -#: ../telemetry-alarms.rst:16 -msgid "The rule governing the alarm has been evaluated as ``False``." -msgstr "" - -#: ../telemetry-alarms.rst:19 -msgid "The rule governing the alarm have been evaluated as ``True``." -msgstr "" - -#: ../telemetry-data-retrieval.rst:134 -msgid "" -"The sample data can be used in various ways for several purposes, like " -"billing or profiling. In external systems the data is often used in the form " -"of aggregated statistics. The Telemetry API provides several built-in " -"functions to make some basic calculations available without any additional " -"coding." -msgstr "" - -#: ../telemetry-data-collection.rst:430 -msgid "" -"The samples that can be sent to Telemetry are not limited to the actual " -"existing meters. There is a possibility to provide data for any new, " -"customer defined counter by filling out all the required fields of the POST " -"request." -msgstr "" - -#: ../blockstorage_multi_backend.rst:116 -msgid "" -"The scheduler uses filters and weights to pick the best back end to handle " -"the request. The scheduler uses volume types to explicitly create volumes on " -"specific back ends." -msgstr "" - -#: ../blockstorage_backup_disks.rst:240 -msgid "" -"The script also enables you to SSH to your instances and run a :command:" -"`mysqldump` command into them. To make this work, enable the connection to " -"the Compute project keys. If you do not want to run the :command:`mysqldump` " -"command, you can add ``enable_mysql_dump=0`` to the script to turn off this " -"functionality." -msgstr "" - -#: ../compute-node-down.rst:324 -msgid "" -"The script includes a ``test mode``, which allows you to perform that whole " -"sequence for only one instance." -msgstr "" - -#: ../telemetry.rst:32 -msgid "" -"The sections in this document contain information about the architecture and " -"usage of Telemetry. The first section contains a brief summary about the " -"system architecture used in a typical OpenStack deployment. The second " -"section describes the data collection mechanisms. You can also read about " -"alarming to understand how alarm definitions can be posted to Telemetry and " -"what actions can happen if an alarm is raised. The last section contains a " -"troubleshooting guide, which mentions error situations and possible " -"solutions to the problems." -msgstr "" - -#: ../objectstorage-monitoring.rst:141 -msgid "" -"The sending of meters is integrated with the logging framework. To enable, " -"configure ``log_statsd_host`` in the relevant config file. You can also " -"specify the port and a default sample rate. The specified default sample " -"rate is used unless a specific call to a statsd logging method (see the list " -"below) overrides it. Currently, no logging calls override the sample rate, " -"but it is conceivable that some meters may require accuracy (sample\\_rate " -"== 1) while others may not." -msgstr "" - -#: ../telemetry-measurements.rst:475 -msgid "" -"The sensor data is not available in the Bare metal service by default. To " -"enable the meters and configure this module to emit notifications about the " -"measured values see the `Installation Guide `__ for the Bare metal service." -msgstr "" - -#: ../compute-manage-logs.rst:129 -msgid "" -"The serial console provides a way to examine kernel output and other system " -"messages during troubleshooting if the instance lacks network connectivity." -msgstr "" - -#: ../telemetry-troubleshooting-guide.rst:79 -msgid "" -"The service catalog provided by OpenStack Identity contains the URLs that " -"are available for authentication. The URLs have different ``port``\\s, based " -"on whether the type of the given URL is ``public``, ``internal`` or " -"``admin``." -msgstr "" - -#: ../compute-remote-console-access.rst:219 -msgid "The service starts automatically on installation." -msgstr "" - -#: ../telemetry-data-retrieval.rst:175 -msgid "" -"The simple query and the statistics functionality can be used together in a " -"single API request." -msgstr "" - -#: ../telemetry-data-retrieval.rst:295 -msgid "" -"The simple query makes it possible to retrieve only a subset of the " -"collected samples. The following command can be executed to request the " -"``cpu`` samples of only one of the VM instances::" -msgstr "" - -#: ../blockstorage_backup_disks.rst:66 -msgid "" -"The size does not have to be the same as the volume of the snapshot. The :" -"option:`--size` parameter defines the space that LVM reserves for the " -"snapshot volume. As a precaution, the size should be the same as that of the " -"original volume, even if the whole space is not currently used by the " -"snapshot." -msgstr "" - -#: ../blockstorage-driver-filter-weighing.rst:219 -msgid "The size of the volume in GB" -msgstr "" - -#: ../telemetry-alarms.rst:154 -msgid "" -"The sliding time window over which the alarm is evaluated is 30 minutes in " -"this example. This window is not clamped to wall-clock time boundaries, " -"rather it's anchored on the current time for each evaluation cycle, and " -"continually creeps forward as each evaluation cycle rolls around (by " -"default, this occurs every minute)." -msgstr "" - -#: ../blockstorage-driver-filter-weighing.rst:213 -msgid "The source replication ID" -msgstr "" - -#: ../blockstorage-driver-filter-weighing.rst:207 -msgid "The source volume ID" -msgstr "" - -#: ../orchestration-stack-domain-users.rst:142 -msgid "" -"The stack owner uses the former (via ``heat resource-metadata {stack_name} " -"{resource_name}``), and any agents in the instance use the latter." -msgstr "" - -# #-#-#-#-# compute_arch.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -# #-#-#-#-# compute-images-instances.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -#: ../compute_arch.rst:267 ../compute-images-instances.rst:373 -msgid "" -"The status of the image. Images marked ``ACTIVE`` are available for use." -msgstr "" - -#: ../blockstorage-driver-filter-weighing.rst:146 -msgid "The storage protocol" -msgstr "" - -#: ../compute-networking-nova.rst:109 -msgid "" -"The subnets are specified by the network administrator, and are assigned " -"dynamically to a tenant when required. A DHCP server is started for each " -"VLAN to pass out IP addresses to VM instances from the subnet assigned to " -"the tenant. All instances belonging to one tenant are bridged into the same " -"VLAN for that tenant. OpenStack Compute creates the Linux networking bridges " -"and VLANs when required." -msgstr "" - -#: ../blockstorage-driver-filter-weighing.rst:51 -msgid "" -"The support for the ``DriverFilter`` and ``GoodnessWeigher`` is optional for " -"back ends. If you are using a back end that does not support the filter and " -"weigher functionality you may not get the full benefit." -msgstr "" - -#: ../compute-networking-nova.rst:961 -msgid "" -"The symptoms may be intermittent, so try running :command:`nslookup` " -"multiple times. If the network configuration is correct, the command should " -"return immediately each time. If it is not correct, the command hangs for " -"several seconds before returning." -msgstr "" - -#: ../telemetry-system-architecture.rst:177 -msgid "" -"The system uses two roles:`admin` and `non-admin`. The authorization happens " -"before processing each API request. The amount of returned data depends on " -"the role the requestor owns." -msgstr "" - -#: ../objectstorage_tenant_specific_image_storage.rst:11 -msgid "The tenant who owns the image" -msgstr "" - -#: ../telemetry-data-collection.rst:994 -msgid "" -"The time to live value is specified in seconds. Each sample has a time " -"stamp, and the ``ttl`` value indicates that a sample will be deleted from " -"the database when the number of seconds has elapsed since that sample " -"reading was stamped. For example, if the time to live is set to 600, all " -"samples older than 600 seconds will be purged from the database." -msgstr "" - -#: ../keystone_caching_layer.rst:45 -msgid "" -"The token revocation list cache time is handled by the configuration option " -"``revocation_cache_time`` in the ``[token]`` section. The revocation list is " -"refreshed whenever a token is revoked. It typically sees significantly more " -"requests than specific token retrievals or token validation calls." -msgstr "" - -#: ../identity_troubleshoot.rst:90 -msgid "" -"The token revocation list is updated once a minute, but the certificates are " -"not. One possible problem is that the certificates are the wrong files or " -"garbage. You can remove these files and run another command against your " -"server; they are fetched on demand." -msgstr "" - -#: ../keystone_caching_layer.rst:39 -msgid "" -"The token system has a separate ``cache_time`` configuration option, that " -"can be set to a value above or below the global ``expiration_time`` default, " -"allowing for different caching behavior from the other systems in OpenStack " -"Identity. This option is set in the ``[token]`` section of the configuration " -"file." -msgstr "" - -#: ../telemetry-data-retrieval.rst:564 -msgid "" -"The topic name of queue to publish to. Setting this will override the " -"default topic defined by ``metering_topic`` and ``event_topic`` options. " -"This option can be used to support multiple consumers. Support for this " -"feature was added in Kilo." -msgstr "" - -#: ../blockstorage-driver-filter-weighing.rst:152 -msgid "The total capacity in GB" -msgstr "" - -#: ../telemetry-data-collection.rst:605 -msgid "" -"The transformers section of a pipeline sink provides the possibility to add " -"a list of transformer definitions. The available transformers are:" -msgstr "" - -#: ../keystone_use_trusts.rst:16 -msgid "" -"The trust can eventually allow the trustee to impersonate the trustor. For " -"security reasons, some safeties are added. For example, if a trustor loses a " -"given role, any trusts the user issued with that role, and the related " -"tokens, are automatically revoked." -msgstr "" - -#: ../orchestration-auth-model.rst:140 -msgid "" -"The trustor delegated roles should be pre-configured in the OpenStack " -"Identity before using it in the Orchestration module." -msgstr "" - -#: ../orchestration-stack-domain-users.rst:86 -msgid "" -"The user ID is returned by this command and is referred to as ``" -"$DOMAIN_ADMIN_ID`` below." -msgstr "" - -#: ../keystone_use_trusts.rst:24 -msgid "The user IDs for the trustor and trustee." -msgstr "" - -#: ../keystone_use_trusts.rst:11 -msgid "The user delegating a limited set of their own rights to another user." -msgstr "" - -#: ../compute-remote-console-access.rst:72 -msgid "The user pastes the URL in a browser or uses it as a client parameter." -msgstr "" - -#: ../keystone_use_trusts.rst:14 -msgid "The user trust is being delegated to, for a limited time." -msgstr "" - -#: ../orchestration-stack-domain-users.rst:50 -msgid "" -"The username and password for the domain admin user is set in :file:`heat." -"conf` (``stack_domain_admin`` and ``stack_domain_admin_password``). This " -"user administers *stack domain users* on behalf of stack owners, so they no " -"longer need to be admins themselves, and the risk of this escalation path is " -"limited because the ``heat_domain_admin`` is only given administrative " -"permission for the ``heat`` domain." -msgstr "" - -#: ../orchestration-auth-model.rst:43 -msgid "The username/password are encrypted and stored in the Orchestration DB." -msgstr "" - -#: ../blockstorage_glusterfs_backend.rst:33 -msgid "" -"The utilities and libraries required for mounting GlusterFS volumes on " -"Ubuntu and Debian distributions are available from the ``glusterfs-client`` " -"package instead." -msgstr "" - -#: ../objectstorage_ringbuilder.rst:155 -msgid "" -"The utility calculates the number of partitions to assign to each device " -"based on the weight of the device. For example, for a partition at the power " -"of 20, the ring has 1,048,576 partitions. One thousand devices of equal " -"weight each want 1,048.576 partitions. The devices are sorted by the number " -"of partitions they desire and kept in order throughout the initialization " -"process." -msgstr "" - -#: ../networking_introduction.rst:92 -msgid "" -"The value of TCP\\_KEEPIDLE, in seconds, for each server socket when " -"starting the API server. Not supported on OS X." -msgstr "" - -#: ../telemetry-data-retrieval.rst:540 -msgid "" -"The value of it is 1. It is used for publishing the samples on additional " -"``metering_topic.sample_name`` topic queue besides the default " -"``metering_topic`` queue." -msgstr "" - -#: ../networking_adv-features.rst:630 -msgid "" -"The value of this option can be tuned according to the observed load on the " -"NSX controllers. Lower values will result in faster synchronization, but " -"might increase the load on the controller cluster." -msgstr "" - -#: ../keystone_certificates_for_pki.rst:28 -msgid "" -"The values that specify where to read the certificates are under the " -"``[signing]`` section of the configuration file. The configuration values " -"are:" -msgstr "" - -#: ../blockstorage-driver-filter-weighing.rst:140 -msgid "The vendor name" -msgstr "" - -#: ../compute-flavors.rst:160 -msgid "The vif I/O options are:" -msgstr "" - -#: ../telemetry-alarms.rst:253 -msgid "" -"The visibility of alarms depends on the role and project associated with the " -"user issuing the query:" -msgstr "" - -#: ../blockstorage-driver-filter-weighing.rst:137 -msgid "The volume back end name" -msgstr "" - -#: ../telemetry-data-collection.rst:734 -msgid "" -"The volume of the created sample is the sum of the volumes of samples that " -"came into the transformer. Samples can be aggregated by the attributes " -"``project_id``, ``user_id`` and ``resource_metadata``. To aggregate by the " -"chosen attributes, specify them in the configuration and set which value of " -"the attribute to take for the new sample (first to take the first sample's " -"attribute, last to take the last sample's attribute, and drop to discard the " -"attribute)." -msgstr "" - -#: ../blockstorage-driver-filter-weighing.rst:174 -msgid "The volume type ID" -msgstr "" - -#: ../blockstorage-driver-filter-weighing.rst:195 -msgid "The volume's ID" -msgstr "" - -#: ../blockstorage-driver-filter-weighing.rst:192 -msgid "The volume's display description" -msgstr "" - -#: ../blockstorage-driver-filter-weighing.rst:204 -msgid "The volume's encryption key ID" -msgstr "" - -#: ../blockstorage-driver-filter-weighing.rst:198 -msgid "The volume's replication status" -msgstr "" - -#: ../blockstorage-driver-filter-weighing.rst:201 -msgid "The volume's snapshot ID" -msgstr "" - -#: ../blockstorage-driver-filter-weighing.rst:186 -msgid "The volume's user ID" -msgstr "" - -#: ../compute-node-down.rst:319 -msgid "The volumes are reattached." -msgstr "" - -#: ../networking_config-identity.rst:38 -msgid "" -"The way that you create a Networking endpoint entry depends on whether you " -"are using the SQL or the template catalog driver:" -msgstr "" - -#: ../compute-remote-console-access.rst:64 -msgid "" -"The web proxy console URLs do not support the websocket protocol scheme " -"(ws://) on python versions less than 2.7.4." -msgstr "" - -#: ../compute-node-down.rst:164 -msgid "" -"The worst disaster for a cloud is power loss, which applies to all three " -"components. Before a power loss:" -msgstr "" - -#: ../objectstorage_components.rst:256 -msgid "" -"Then a lookup in the ring figures out which storage nodes contain the " -"partitions in question." -msgstr "" - -#: ../keystone_certificates_for_pki.rst:155 -msgid "" -"Then generate a CRS with OpenSSL CLI. **Do not encrypt the generated private " -"key. You must use the -nodes option.**" -msgstr "" - -#: ../objectstorage-monitoring.rst:157 -msgid "" -"Then the LogAdapter object returned by ``get_logger()``, usually stored in " -"``self.logger``, has these new methods:" -msgstr "" - -#: ../orchestration-stack-domain-users.rst:95 -msgid "" -"Then you need to add the domain ID, username and password from these steps " -"to :file:`heat.conf`:" -msgstr "" - -#: ../blockstorage_multi_backend.rst:131 -msgid "" -"Then, an extra-specification has to be created to link the volume type to a " -"back end name. Run this command::" -msgstr "" - -#: ../compute-flavors.rst:183 -msgid "" -"There are also two optional attributes (integer): ``peak``, which specifies " -"the maximum rate at which a bridge can send data (kilobytes/second), and " -"``burst``, the amount of bytes that can be burst at peak speed (kilobytes). " -"The rate is shared equally within domains connected to the network." -msgstr "" - -#: ../telemetry-alarms.rst:22 -msgid "" -"There are not enough datapoints available in the evaluation periods to " -"meaningfully determine the alarm state." -msgstr "" - -#: ../blockstorage_image_volume_cache.rst:57 -msgid "" -"There are optional configuration settings that can limit the size of the " -"cache. These can also be scoped per back end or in the default options in :" -"file:`cinder.conf`::" -msgstr "" - -#: ../blockstorage_volume_backups.rst:128 -msgid "" -"There are several other options whose default values may be overridden as " -"appropriate for your environment:" -msgstr "" - -#: ../telemetry-data-collection.rst:557 -msgid "" -"There are several ways to define the list of meters for a pipeline source. " -"The list of valid meters can be found in :ref:`telemetry-measurements`. " -"There is a possibility to define all the meters, or just included or " -"excluded meters, with which a source should operate:" -msgstr "" - -#: ../objectstorage-monitoring.rst:46 -msgid "" -"There are some good Object Storage cluster statistics but the general server " -"meters overlap with existing server monitoring systems. To get the Swift-" -"specific meters into a monitoring system, they must be polled. Swift Recon " -"essentially acts as a middleware meters collector. The process that feeds " -"meters to your statistics system, such as ``collectd`` and ``gmond``, " -"probably already runs on the storage node. So, you can choose to either talk " -"to Swift Recon or collect the meters directly." -msgstr "" - -#: ../telemetry-data-collection.rst:216 -msgid "" -"There are three types of agents supporting the polling mechanism, the " -"compute agent, the central agent, and the IPMI agent. Under the hood, all " -"the types of polling agents are the same ``ceilometer-polling`` agent, " -"except that they load different polling plug-ins (pollsters) from different " -"namespaces to gather data. The following subsections give further " -"information regarding the architectural and configuration details of these " -"components." -msgstr "" - -#: ../blockstorage-driver-filter-weighing.rst:124 -msgid "" -"There are various properties that can be used in either the " -"``filter_function`` or the ``goodness_function`` strings. The properties " -"allow access to volume info, qos settings, extra specs, and so on." -msgstr "" - -#: ../blockstorage_over_subscription.rst:43 -msgid "" -"There is a change on how ``reserved_percentage`` is used. It was measured " -"against the free capacity in the past. Now it is measured against the total " -"capacity." -msgstr "" - -#: ../ts-eql-volume-size.rst:11 -msgid "" -"There is a discrepancy between both the actual volume size in EqualLogic " -"(EQL) storage and the image size in the Image service, with what is reported " -"OpenStack database. This could lead to confusion if a user is creating " -"volumes from an image that was uploaded from an EQL volume (through the " -"Image service). The image size is slightly larger than the target volume " -"size; this is because EQL size reporting accounts for additional storage " -"used by EQL for internal volume metadata." -msgstr "" - -#: ../objectstorage_EC.rst:14 -msgid "" -"There is no external API related to erasure coding. Create a container using " -"a Storage Policy; the interaction with the cluster is the same as any other " -"durability policy. Because support implements as a Storage Policy, you can " -"isolate all storage devices that associate with your cluster's erasure " -"coding capability. It is entirely possible to share devices between storage " -"policies, but for erasure coding it may make more sense to use not only " -"separate devices but possibly even entire nodes dedicated for erasure coding." -msgstr "" - -#: ../networking_multi-dhcp-agents.rst:33 -msgid "There will be three hosts in the setup." -msgstr "" - -#: ../telemetry-data-collection.rst:209 -msgid "" -"Therefore Telemetry uses another method to gather this data by polling the " -"infrastructure including the APIs of the different OpenStack services and " -"other assets, like hypervisors. The latter case requires closer interaction " -"with the compute hosts. To solve this issue, Telemetry uses an agent based " -"architecture to fulfill the requirements against the data collection." -msgstr "" - -#: ../telemetry-troubleshooting-guide.rst:99 -msgid "" -"Therefore when specifying the ``os_auth_url`` parameter on the command line " -"or by using environment variable, use the ``internalURL`` or ``publicURL``." -msgstr "" - -#: ../database.rst:250 -msgid "" -"Therefore, as part of creating a datastore, you need to load the :file:" -"`validation-rules.json` file, using the :command:`trove-manage` :command:" -"`db_load_datastore_config_parameters` command. This command takes the " -"following arguments:" -msgstr "" - -#: ../networking_config-agents.rst:145 -msgid "" -"These DHCP agent options are required in the :file:`/etc/neutron/dhcp_agent." -"ini` file for the NSX plug-in:" -msgstr "" - -#: ../networking_config-agents.rst:132 -msgid "" -"These DHCP agent options are required in the :file:`/etc/neutron/dhcp_agent." -"ini` file for the OVS plug-in:" -msgstr "" - -#: ../networking_arch.rst:51 -msgid "" -"These agents interact with the main neutron process through RPC (for " -"example, RabbitMQ or Qpid) or through the standard Networking API. In " -"addition, Networking integrates with OpenStack components in a number of " -"ways:" -msgstr "" - -#: ../telemetry-alarms.rst:13 -msgid "These alarms follow a tri-state model:" -msgstr "" - -#: ../telemetry-alarms.rst:101 -msgid "" -"These are a lightweight alternative to webhooks, whereby the state " -"transition is simply logged by the ``alarm-notifier``, and are intended " -"primarily for testing purposes." -msgstr "" - -#: ../telemetry-alarms.rst:94 -msgid "" -"These are the *de facto* notification type used by Telemetry alarming and " -"simply involve an HTTP POST request being sent to an endpoint, with a " -"request body containing a description of the state transition encoded as a " -"JSON fragment." -msgstr "" - -#: ../compute_arch.rst:296 -msgid "" -"These basic categories describe the service architecture and information " -"about the cloud controller." -msgstr "" - -#: ../ts_cinder_config.rst:105 -msgid "" -"These common issues might occur during configuration. To correct, use these " -"suggested solutions." -msgstr "" - -#: ../ts_cinder_config.rst:27 -msgid "" -"These entries in the :file:`cinder.openstack.common.log` file can be used to " -"assist in troubleshooting your block storage configuration." -msgstr "" - -#: ../ts-HTTP-bad-req-in-cinder-vol-log.rst:11 -msgid "These errors appear in the :file:`cinder-volume.log` file::" -msgstr "" - -#: ../blockstorage_multi_backend.rst:55 -msgid "These examples show three back ends:" -msgstr "" - -#: ../telemetry-measurements.rst:1051 -msgid "" -"These meters are available for OpenFlow based switches. In order to enable " -"these meters, each driver needs to be properly configured." -msgstr "" - -#: ../telemetry-data-collection.rst:925 -msgid "" -"These meters are not loaded by default. To load these meters, flip the " -"`disable_non_metric_meters` option in the :file:`ceilometer.conf` file." -msgstr "" - -#: ../compute-networking-nova.rst:117 -msgid "" -"These network managers can co-exist in a cloud system. However, because you " -"cannot select the type of network for a given tenant, you cannot configure " -"multiple network types in a single Compute installation." -msgstr "" - -#: ../networking_adv-operational-features.rst:76 -msgid "" -"These options configure the Networking server to send notifications through " -"logging and RPC. The logging options are described in OpenStack " -"Configuration Reference . RPC notifications go to ``notifications.info`` " -"queue bound to a topic exchange defined by ``control_exchange`` in :file:" -"`neutron.conf`." -msgstr "" - -#: ../networking_adv-operational-features.rst:126 -msgid "" -"These options configure the Networking server to send notifications to " -"multiple RPC topics. RPC notifications go to ``notifications_one.info`` and " -"``notifications_two.info`` queues bound to a topic exchange defined by " -"``control_exchange`` in :file:`neutron.conf`." -msgstr "" - -#: ../blockstorage-driver-filter-weighing.rst:163 -msgid "" -"These properties are determined by the specific back end you are creating " -"filter and goodness functions for. Some back ends may not have any " -"properties available here." -msgstr "" - -#: ../objectstorage_components.rst:98 -msgid "" -"These rings are externally managed, in that the server processes themselves " -"do not modify the rings, they are instead given new rings modified by other " -"tools." -msgstr "" - -#: ../keystone_integrate_assignment_backend_ldap.rst:55 -msgid "" -"These schema attributes are extensible for compatibility with various " -"schemas. For example, this entry maps to the groupOfNames attribute in " -"Active Directory:" -msgstr "" - -#: ../keystone_integrate_identity_backend_ldap.rst:44 -#: ../keystone_integrate_identity_backend_ldap.rst:148 -msgid "" -"These schema attributes are extensible for compatibility with various " -"schemas. For example, this entry maps to the person attribute in Active " -"Directory:" -msgstr "" - -#: ../networking_adv-features.rst:454 -msgid "These sections explain NSX plug-in extensions." -msgstr "" - -#: ../objectstorage_ringbuilder.rst:214 -msgid "" -"These steps do not always perfectly rebalance a ring due to the random " -"nature of gathering partitions for reassignment. To help reach a more " -"balanced ring, the rebalance process is repeated until near perfect (less " -"than 1 percent off) or when the balance does not improve by at least 1 " -"percent (indicating we probably cannot get perfect balance due to wildly " -"imbalanced zones or too many partitions recently moved)." -msgstr "" - -#: ../compute-service-groups.rst:71 -msgid "" -"These values in the :file:`/etc/nova/nova.conf` file are required on every " -"node for the ZooKeeper driver:" -msgstr "" - -#: ../compute-service-groups.rst:100 -msgid "" -"These values in the :file:`/etc/nova/nova.conf` file are required on every " -"node for the memcache driver:" -msgstr "" - -#: ../blockstorage_volume_migration.rst:17 -msgid "These workflows are possible for a migration:" -msgstr "" - -#: ../objectstorage_components.rst:179 -msgid "" -"Think of a partition as a bin moving throughout a fulfillment center " -"warehouse. Individual orders get thrown into the bin. The system treats that " -"bin as a cohesive entity as it moves throughout the system. A bin is easier " -"to deal with than many little things. It makes for fewer moving parts " -"throughout the system." -msgstr "" - -#: ../telemetry-data-collection.rst:395 -msgid "" -"This agent is responsible for collecting IPMI sensor data and Intel Node " -"Manager data on individual compute nodes within an OpenStack deployment. " -"This agent requires an IPMI capable node with the ipmitool utility " -"installed, which is commonly used for IPMI control on various Linux " -"distributions." -msgstr "" - -#: ../telemetry-data-collection.rst:287 -msgid "" -"This agent is responsible for collecting resource usage data of VM instances " -"on individual compute nodes within an OpenStack deployment. This mechanism " -"requires a closer interaction with the hypervisor, therefore a separate " -"agent type fulfills the collection of the related meters, which is placed on " -"the host machines to locally retrieve this information." -msgstr "" - -#: ../compute-node-down.rst:306 -msgid "" -"This allows you to connect to the instance even without the volume attached, " -"if you allow only connections through public keys." -msgstr "" - -#: ../dashboard_sessions.rst:191 -msgid "" -"This back end stores session data in a cookie, which is stored by the user's " -"browser. The back end uses a cryptographic signing technique to ensure " -"session data is not tampered with during transport. This is not the same as " -"encryption; session data is still readable by an attacker." -msgstr "" - -#: ../blockstorage_image_volume_cache.rst:55 -msgid "This can be scoped per back end definition or in the default options." -msgstr "" - -#: ../identity_troubleshoot.rst:151 -msgid "" -"This can present a problem when you run the Identity daemon under the " -"keystone user account (nologin) when you try to run PKI. Unless you run the " -"``chown`` command against the files ``keystone:keystone``, or run the " -"``keystone-manage pki_setup`` command with the :option:`--keystone-user` " -"and :option:`--keystone-group` parameters, you will get an error. For " -"example:" -msgstr "" - -#: ../blockstorage_glusterfs_backend.rst:201 -msgid "" -"This command also makes the Boolean persistent across reboots. Run this " -"command on all client hosts that require access to GlusterFS volumes on an " -"instance. This includes all compute nodes." -msgstr "" - -#: ../blockstorage_nfs_backend.rst:154 -msgid "" -"This command also makes the boolean persistent across reboots. Run this " -"command on all client hosts that require access to NFS volumes on an " -"instance. This includes all compute nodes." -msgstr "" - -#: ../blockstorage_volume_backups.rst:66 -msgid "" -"This command also returns a backup ID. Use this backup ID when restoring the " -"volume::" -msgstr "" - -#: ../blockstorage_backup_disks.rst:168 -msgid "" -"This command creates a :file:`tar.gz` file that contains the data, *and data " -"only*. This ensures that you do not waste space by backing up empty sectors." -msgstr "" - -#: ../blockstorage_volume_number_weigher.rst:72 -msgid "" -"This command creates three volumes in ``stack-volumes`` and three volumes in " -"``stack-volumes-1``." -msgstr "" - -#: ../identity_troubleshoot.rst:68 -msgid "This command fetches the signing certificate:" -msgstr "" - -#: ../networking_multi-dhcp-agents.rst:362 -msgid "" -"This command is the sibling command for the previous one. Remove ``net2`` " -"from the DHCP agent for HostA:" -msgstr "" - -#: ../networking_multi-dhcp-agents.rst:227 -msgid "This command is to show which networks a given dhcp agent is managing." -msgstr "" - -#: ../identity_start.rst:10 -msgid "" -"This command starts two wsgi.Server instances configured by the :file:" -"`keystone.conf` file as described previously. One of these wsgi servers is :" -"code:`admin` (the administration API) and the other is :code:`main` (the " -"primary/public API interface). Both run in a single process." -msgstr "" - -#: ../blockstorage_volume_number_weigher.rst:31 -msgid "" -"This configuration defines two LVM volume groups: ``stack-volumes`` with 10 " -"GB capacity and ``stack-volumes-1`` with 60 GB capacity. This example " -"configuration defines two back ends:" -msgstr "" - -#: ../compute-networking-nova.rst:242 -msgid "" -"This configuration was tested with virtual machine images that have an IPv6 " -"stateless address auto-configuration capability. This capability is required " -"for any VM to run with an IPv6 address. You must use an EUI-64 address for " -"stateless address auto-configuration. Each node that executes a ``nova-*`` " -"service must have ``python-netaddr`` and ``radvd`` installed." -msgstr "" - -#: ../telemetry-alarms.rst:218 -msgid "" -"This creates an alarm that will fire when either one of two underlying " -"alarms transition into the alarm state. The notification in this case is a " -"webhook call. Any number of underlying alarms can be combined in this way, " -"using either ``and`` or ``or``." -msgstr "" - -#: ../telemetry-alarms.rst:140 -msgid "" -"This creates an alarm that will fire when the average CPU utilization for an " -"individual instance exceeds 70% for three consecutive 10 minute periods. The " -"notification in this case is simply a log message, though it could " -"alternatively be a webhook URL." -msgstr "" - -#: ../compute-images-instances.rst:46 -msgid "" -"This diagram shows the system state prior to launching an instance. The " -"image store, fronted by the Image service (glance) has a number of " -"predefined images. Inside the cloud, a compute node contains the available " -"vCPU, memory, and local disk resources. Additionally, the ``cinder-volume`` " -"service provides a number of predefined volumes." -msgstr "" - -#: ../identity_troubleshoot.rst:59 -msgid "" -"This directory contains two certificates and the token revocation list. If " -"these files are not present, your service cannot fetch them from Identity. " -"To troubleshoot, try to talk to Identity to make sure it correctly serves " -"files, as follows:" -msgstr "" - -#: ../ts_non_existent_host.rst:8 -msgid "" -"This error could be caused by a volume being exported outside of OpenStack " -"using a host name different from the system name that OpenStack expects. " -"This error could be displayed with the IQN if the host was exported using " -"iSCSI." -msgstr "" - -#: ../ts-duplicate-3par-host.rst:11 -msgid "" -"This error may be caused by a volume being exported outside of OpenStack " -"using a host name different from the system name that OpenStack expects. " -"This error could be displayed with the IQN if the host was exported using " -"iSCSI::" -msgstr "" - -#: ../ts_non_existent_vlun.rst:8 -msgid "" -"This error occurs if the 3PAR host exists with the correct host name that " -"the OpenStack Block Storage drivers expect but the volume was created in a " -"different Domain." -msgstr "" - -#: ../compute-service-groups.rst:68 -msgid "" -"This example assumes the ZooKeeper server addresses and ports are " -"``192.168.2.1:2181``, ``192.168.2.2:2181``, and ``192.168.2.3:2181``." -msgstr "" - -#: ../database.rst:62 -msgid "" -"This example assumes you have created a MySQL 5.5 image called ``mysql-5.5." -"qcow2``." -msgstr "" - -#: ../blockstorage_multi_backend.rst:137 -msgid "" -"This example creates a ``lvm`` volume type with " -"``volume_backend_name=LVM_iSCSI`` as extra-specifications." -msgstr "" - -#: ../blockstorage_volume_number_weigher.rst:61 -msgid "" -"This example creates a lvm volume type with ``volume_backend_name=LVM`` as " -"extra specifications." -msgstr "" - -#: ../compute-networking-nova.rst:813 -msgid "" -"This example demonstrates how to set up the interfaces within the instance. " -"This is the configuration that needs to be applied inside the image." -msgstr "" - -#: ../database.rst:261 -msgid "" -"This example loads the :file:`validation-rules.json` file for a MySQL " -"database on Ubuntu 14.04::" -msgstr "" - -#: ../compute-manage-logs.rst:97 -msgid "" -"This example provides a minimal configuration for :file:`/etc/rsyslog.conf` " -"on the log server host, which receives the log files" -msgstr "" - -#: ../compute-manage-logs.rst:33 -msgid "" -"This example sets the debugging level to ``INFO`` (which is less verbose " -"than the default ``DEBUG`` setting)." -msgstr "" - -#: ../blockstorage_backup_disks.rst:224 -msgid "This example shows a mail report::" -msgstr "" - -#: ../database.rst:100 ../database.rst:138 -msgid "This example uses the following arguments:" -msgstr "" - -#: ../compute-networking-nova.rst:174 -msgid "This example uses the following parameters:" -msgstr "" - -#: ../networking_introduction.rst:315 -msgid "This extension introduces these resources:" -msgstr "" - -#: ../networking_auth.rst:87 -msgid "This extract is from the default :file:`policy.json` file:" -msgstr "" - -#: ../networking_config-agents.rst:123 -msgid "" -"This feature applies to all plug-ins that support DHCP scaling. For more " -"information, see the `DHCP agent configuration options `__ listed in the OpenStack Configuration Reference." -msgstr "" - -#: ../cross_project_cors.rst:15 -msgid "" -"This feature is most useful to organizations which maintain one or more " -"custom user interfaces for OpenStack, as it permits those interfaces to " -"access the services directly, rather than requiring an intermediate proxy " -"server. It can, however, also be misused by malicious actors; please review " -"the security advisory below for more information." -msgstr "" - -#: ../blockstorage_ratelimit_volume_copy_bandwidth.rst:42 -msgid "" -"This feature requires libcgroup to set up blkio cgroup for disk I/O " -"bandwidth limit. The libcgroup is provided by the cgroup-bin package in " -"Debian and Ubuntu, or by the libcgroup-tools package in Fedora, Red Hat " -"Enterprise Linux, CentOS, openSUSE, and SUSE Linux Enterprise." -msgstr "" - -#: ../compute-images-instances.rst:280 -msgid "" -"This file contains the rules for property protections and the roles and " -"policies associated with it." -msgstr "" - -#: ../compute-configuring-migrations.rst:92 -msgid "" -"This guide assumes the default value for ``instances_path`` in your :file:" -"`nova.conf` file (:file:`NOVA-INST-DIR/instances`). If you have changed the " -"``state_path`` or ``instances_path`` variables, modify the commands " -"accordingly." -msgstr "" - -#: ../index.rst:11 -msgid "" -"This guide documents OpenStack Kilo, OpenStack Juno, and OpenStack Icehouse " -"releases." -msgstr "" - -#: ../blockstorage-manage-volumes.rst:20 -msgid "" -"This high-level procedure shows you how to create and attach a volume to a " -"server instance." -msgstr "" - -#: ../database.rst:46 -msgid "" -"This image must have the trove guest agent installed, and it must have the :" -"file:`trove-guestagent.conf` file configured to connect to your OpenStack " -"environment. To configure :file:`trove-guestagent.conf`, add the following " -"lines to :file:`trove-guestagent.conf` on the guest instance you are using " -"to build your image:" -msgstr "" - -#: ../telemetry-events.rst:76 -msgid "" -"This includes descriptions of how to map fields in the notification body to " -"Traits, and optional plug-ins for doing any programmatic translations " -"(splitting a string, forcing case)." -msgstr "" - -#: ../compute-node-down.rst:213 -msgid "" -"This information can be found using the :command:`nova volume-list` command. " -"Note that the ``nova`` client also includes the ability to get volume " -"information from OpenStack Block Storage." -msgstr "" - -#: ../networking_introduction.rst:331 -msgid "This initial implementation of the VPNaaS extension provides:" -msgstr "" - -#: ../telemetry-events.rst:120 -msgid "" -"This is a list (or a string, which will be taken as a 1 element list) of " -"event\\_types this definition will handle. These can be wildcarded with unix " -"shell glob syntax. An exclusion listing (starting with a ``!``) will exclude " -"any types listed from matching. If only exclusions are listed, the " -"definition will match anything not matching the exclusions." -msgstr "" - -#: ../objectstorage_ringbuilder.rst:35 -msgid "" -"This is a list of ``array('H')`` of devices ids. The outermost list contains " -"an ``array('H')`` for each replica. Each ``array('H')`` has a length equal " -"to the partition count for the ring. Each integer in the ``array('H')`` is " -"an index into the above list of devices. The partition list is known " -"internally to the Ring class as ``_replica2part2dev_id``." -msgstr "" - -#: ../telemetry-events.rst:128 -msgid "" -"This is a mapping, the keys are the trait names, and the values are trait " -"definitions." -msgstr "" - -#: ../cross_project_cors.rst:8 -msgid "This is a new feature in OpenStack Liberty." -msgstr "" - -#: ../objectstorage-monitoring.rst:80 -msgid "" -"This is good for getting a feel for the quality of service clients are " -"experiencing with the timing meters, as well as getting a feel for the " -"volume of the various permutations of request server type, command, and " -"response code. Swift-Informant also requires no change to core Object " -"Storage code because it is implemented as middleware. However, it gives you " -"no insight into the workings of the cluster past the proxy server. If the " -"responsiveness of one storage node degrades, you can only see that some of " -"your requests are bad, either as high latency or error status codes. You do " -"not know exactly why or where that request tried to go. Maybe the container " -"server in question was on a good node but the object server was on a " -"different, poorly-performing node." -msgstr "" - -#: ../ts_cinder_config.rst:146 -msgid "" -"This is most likely going to be a minor adjustment to your :file:`nova.conf` " -"file. Make sure that your :file:`nova.conf` has this entry" -msgstr "" - -#: ../compute-networking-nova.rst:96 -msgid "" -"This is the default mode for OpenStack Compute. In this mode, Compute " -"creates a VLAN and bridge for each tenant. For multiple-machine " -"installations, the VLAN Network Mode requires a switch that supports VLAN " -"tagging (IEEE 802.1Q). The tenant gets a range of private IPs that are only " -"accessible from inside the VLAN. In order for a user to access the instances " -"in their tenant, a special VPN instance (code named cloudpipe) needs to be " -"created. Compute generates a certificate and key for the user to access the " -"VPN and starts the VPN automatically. It provides a private network segment " -"for each tenant's instances that can be accessed through a dedicated VPN " -"connection from the internet. In this mode, each tenant gets its own VLAN, " -"Linux networking bridge, and subnet." -msgstr "" - -#: ../objectstorage_components.rst:219 -msgid "" -"This is where partitions come in handy. With fewer things in the system, " -"larger chunks of data are transferred around (rather than lots of little TCP " -"connections, which is inefficient) and there is a consistent number of " -"hashes to compare." -msgstr "" - -#: ../compute-service-groups.rst:66 -msgid "This library makes the binding work with the eventlet threading model." -msgstr "" - -#: ../networking_adv-features.rst:401 -msgid "" -"This list shows example neutron commands that enable you to complete basic " -"LBaaS operations:" -msgstr "" - -#: ../cross_project_cors.rst:48 -msgid "" -"This method also enables you to define multiple origins. To express this in " -"your configuration file, first begin with a :code:`[cors]` group as above, " -"into which you place your default configuration values. Then, add as many " -"additional configuration groups as necessary, naming them :code:`[cors." -"{something}]` (each name must be unique). The purpose of the suffix to :code:" -"`cors.` is legibility, we recommend using a reasonable human-readable string:" -msgstr "" - -#: ../telemetry-system-architecture.rst:171 -msgid "" -"This module of OpenStack uses OpenStack Identity for authenticating and " -"authorizing users. The required configuration options are listed in the " -"`Telemetry section `__ in the *OpenStack Configuration " -"Reference*." -msgstr "" - -#: ../telemetry-data-collection.rst:427 -msgid "" -"This option makes it possible to send any kind of samples without the need " -"of writing extra code lines or making configuration changes." -msgstr "" - -#: ../keystone_use_trusts.rst:50 -msgid "" -"This parameter further restricts the delegation to the specified endpoints " -"only. If you omit the endpoints, the delegation is useless. A special value " -"of ``all_endpoints`` allows the trust to be used by all endpoints associated " -"with the delegated tenant." -msgstr "" - -#: ../compute-node-down.rst:284 -msgid "" -"This parameter will cause the system to disable the ability to write to the " -"disk if it detects an I/O error. This configuration option should be added " -"into the cinder-volume server (the one which performs the iSCSI connection " -"to the SAN), and into the instances' :file:`fstab` files." -msgstr "" - -#: ../networking_auth.rst:165 -msgid "" -"This policy evaluates successfully if either *admin\\_or\\_owner*, or " -"*shared* evaluates successfully." -msgstr "" - -#: ../networking_auth.rst:205 -msgid "" -"This policy restricts the ability to manipulate the *mac\\_address* " -"attribute for a port only to administrators and the owner of the network " -"where the port is attached." -msgstr "" - -#: ../networking_auth.rst:180 -msgid "" -"This policy restricts the ability to manipulate the *shared* attribute for a " -"network to administrators only." -msgstr "" - -#: ../networking_adv-features.rst:260 -msgid "" -"This port must be on an Networking subnet that is attached to a router " -"uplinked to the external network used to create the floating IP." -"Conceptually, this is because the router must be able to perform the " -"Destination NAT (DNAT) rewriting of packets from the floating IP address " -"(chosen from a subnet on the external network) to the internal fixed IP " -"(chosen from a private subnet that is behind the router)." -msgstr "" - -#: ../ts-eql-volume-size.rst:21 -msgid "" -"This procedure assumes that the EQL array is provisioned, and that " -"appropriate configuration settings have been included in :file:`/etc/cinder/" -"cinder.conf` to connect to the EQL array." -msgstr "" - -#: ../objectstorage-troubleshoot.rst:109 -msgid "" -"This procedure is a last-resort for emergency circumstances. It requires " -"knowledge of the swift python code and may not succeed." -msgstr "" - -#: ../compute-default-ports.rst:11 -msgid "" -"This procedure modifies the iptables firewall to allow incoming connections " -"to the Compute services." -msgstr "" - -#: ../compute-node-down.rst:105 -msgid "This procedure runs on nova-compute hosts, based on the KVM hypervisor:" -msgstr "" - -#: ../telemetry-data-retrieval.rst:527 -msgid "This publisher sends metering data to a kafka broker." -msgstr "" - -#: ../compute-networking-nova.rst:223 -msgid "" -"This reservation only affects which IP address the VMs start at, not the " -"fixed IP addresses that ``nova-network`` places on the bridges." -msgstr "" - -#: ../identity_auth_token_middleware.rst:51 -msgid "" -"This sample paste config filter makes use of the :code:`admin_user` and :" -"code:`admin_password` options:" -msgstr "" - -#: ../objectstorage-troubleshoot.rst:92 -msgid "" -"This script has only been tested on Ubuntu 10.04; use with caution on other " -"operating systems in production." -msgstr "" - -#: ../telemetry-data-collection.rst:941 -msgid "" -"This script outputs what volumes or snapshots were created, deleted, or " -"exists in a given period of time and some information about these volumes or " -"snapshots. Information about the existence and size of volumes and snapshots " -"is store in the Telemetry module. This data is also stored as an event which " -"is the recommended usage as it provides better indexing of data." -msgstr "" - -#: ../blockstorage_multi_backend.rst:181 -msgid "This second volume is created on ``lvmdriver-3``." -msgstr "" - -#: ../blockstorage_multi_backend.rst:147 -msgid "" -"This second volume type is named ``lvm_gold`` and has ``LVM_iSCSI_b`` as " -"back end name." -msgstr "" - -#: ../database.rst:33 -msgid "" -"This section assumes you do not yet have a MySQL datastore, and shows you " -"how to create a MySQL datastore and populate it with a MySQL 5.5 datastore " -"version." -msgstr "" - -#: ../compute-node-down.rst:146 -msgid "" -"This section covers procedures for managing your cloud after a disaster, and " -"backing up persistent storage volumes. Backups are mandatory, even outside " -"of disaster scenarios." -msgstr "" - -#: ../networking_adv-config.rst:5 -msgid "" -"This section describes advanced configuration options for various system " -"components. For example, configuration options where the default works but " -"that the user wants to customize options. After installing from packages, ``" -"$NEUTRON_CONF_DIR`` is :file:`/etc/neutron`." -msgstr "" - -#: ../compute-networking-nova.rst:575 -msgid "" -"This section describes how to configure floating IP addresses with ``nova-" -"network``. For information about doing this with OpenStack Networking, see :" -"ref:`L3-routing-and-NAT`." -msgstr "" - -#: ../networking_multi-dhcp-agents.rst:5 -msgid "" -"This section describes how to use the agent management (alias agent) and " -"scheduler (alias agent_scheduler) extensions for DHCP agents scalability and " -"HA." -msgstr "" - -#: ../compute-live-migration-usage.rst:7 -msgid "" -"This section discusses how to migrate running instances from one OpenStack " -"Compute server to another OpenStack Compute server." -msgstr "" - -#: ../blockstorage_glusterfs_backend.rst:5 -msgid "" -"This section explains how to configure OpenStack Block Storage to use " -"GlusterFS as a back end. You must be able to access the GlusterFS shares " -"from the server that hosts the ``cinder`` volume service." -msgstr "" - -#: ../blockstorage_nfs_backend.rst:5 -msgid "" -"This section explains how to configure OpenStack Block Storage to use NFS " -"storage. You must be able to access the NFS shares from the server that " -"hosts the ``cinder`` volume service." -msgstr "" - -#: ../networking_adv-features.rst:667 -msgid "" -"This section explains the Big Switch neutron plug-in-specific extension." -msgstr "" - -#: ../telemetry-data-retrieval.rst:203 -msgid "" -"This section provides some examples without the aim of completeness. These " -"commands can be used for instance for validating an installation of " -"Telemetry." -msgstr "" - -#: ../blockstorage-troubleshoot.rst:5 -msgid "" -"This section provides useful tips to help you troubleshoot your Block " -"Storage installation." -msgstr "" - -#: ../networking_config-agents.rst:15 -msgid "" -"This section shows you how to install and configure a subset of the " -"available plug-ins, which might include the installation of switching " -"software (for example, Open vSwitch) and as agents used to communicate with " -"the neutron-server process running elsewhere in the data center." -msgstr "" - -#: ../objectstorage_replication.rst:56 -msgid "" -"This synchronization point is a high water mark that notes the last record " -"at which two databases were known to be synchronized, and is stored in each " -"database as a tuple of the remote database ID and record ID. Database IDs " -"are unique across all replicas of the database, and record IDs are " -"monotonically increasing integers. After all new records are pushed to the " -"remote database, the entire synchronization table of the local database is " -"pushed, so the remote database can guarantee that it is synchronized with " -"everything with which the local database was previously synchronized." -msgstr "" - -#: ../networking_adv-features.rst:776 -msgid "" -"This table shows example :command:`neutron` commands that enable you to " -"complete basic L3 metering operations:" -msgstr "" - -#: ../networking_use.rst:119 -msgid "" -"This table shows example Networking commands that enable you to complete " -"advanced network operations:" -msgstr "" - -#: ../networking_use.rst:179 -msgid "" -"This table shows example neutron and nova commands that enable you to " -"complete basic VM networking operations:" -msgstr "" - -#: ../networking_adv-features.rst:199 -msgid "" -"This table shows example neutron commands that enable you to complete basic " -"L3 operations:" -msgstr "" - -#: ../networking_use.rst:43 -msgid "" -"This table shows example neutron commands that enable you to complete basic " -"network operations:" -msgstr "" - -#: ../networking_adv-features.rst:484 -msgid "" -"This table shows example neutron commands that enable you to complete basic " -"queue operations:" -msgstr "" - -#: ../networking_adv-features.rst:349 -msgid "" -"This table shows example neutron commands that enable you to complete basic " -"security group operations:" -msgstr "" - -#: ../networking_use.rst:237 -msgid "" -"This table shows example nova and neutron commands that enable you to " -"complete advanced VM creation operations:" -msgstr "" - -#: ../networking_config-agents.rst:488 -msgid "" -"This table shows examples of Networking commands that enable you to complete " -"basic operations on agents:" -msgstr "" - -#: ../telemetry-data-collection.rst:818 -msgid "" -"This transformer calculates the change between two sample datapoints of a " -"resource. It can be configured to capture only the positive growth deltas." -msgstr "" - -#: ../telemetry-data-collection.rst:774 -msgid "" -"This transformer enables us to perform arithmetic calculations over one or " -"more meters and/or their metadata, for example::" -msgstr "" - -#: ../telemetry-data-collection.rst:764 -msgid "" -"This transformer simply caches the samples until enough samples have arrived " -"and then flushes them all down the pipeline at once::" -msgstr "" - -#: ../keystone_integrate_with_ldap.rst:125 -msgid "" -"This value is a bitmask, consult your LDAP documentation for possible values." -msgstr "" - -#: ../ts-failed-attach-vol-no-sysfsutils.rst:11 -msgid "" -"This warning and error occurs if you do not have the required ``sysfsutils`` " -"package installed on the compute node::" -msgstr "" - -#: ../objectstorage_auditors.rst:23 -msgid "" -"This will run the object auditor on only the sda and sdb devices. This " -"parameter accepts a comma separated list of values." -msgstr "" - -#: ../telemetry-alarms.rst:33 -msgid "Threshold rule alarms" -msgstr "" - -#: ../telemetry-data-collection.rst:730 -msgid "" -"Timeout can be specified with the ``retention_time`` option. If we want to " -"flush the aggregation after a set number of samples have been aggregated, we " -"can specify the size parameter." -msgstr "" - -#: ../objectstorage-monitoring.rst:68 -msgid "" -"Timing data for a meter like ``acct.GET.200`` or ``obj.GET.200``. [The " -"README says the meters look like ``duration.acct.GET.200``, but I do not see " -"the ``duration`` in the code. I am not sure what the Etsy server does but " -"our StatsD server turns timing meters into five derivative meters with new " -"segments appended, so it probably works as coded. The first meter turns into " -"``acct.GET.200.lower``, ``acct.GET.200.upper``, ``acct.GET.200.mean``, " -"``acct.GET.200.upper_90``, and ``acct.GET.200.count``]." -msgstr "" - -#: ../objectstorage_arch.rst:84 -msgid "" -"To achieve apparent higher throughput, the object storage system is designed " -"to handle concurrent uploads/downloads. The network I/O capacity (1GbE, " -"bonded 1GbE pair, or 10GbE) should match your desired concurrent throughput " -"needs for reads and writes." -msgstr "" - -#: ../networking_introduction.rst:247 -msgid "To add a single rule, use the insert-rule operation." -msgstr "" - -#: ../networking_multi-dhcp-agents.rst:343 -msgid "To add another DHCP agent to host the network, run this command:" -msgstr "" - -#: ../cross_project_cors.rst:95 -msgid "To add another domain, simply add another filter." -msgstr "" - -#: ../networking_introduction.rst:245 -msgid "To add multiple rules, use the update operation." -msgstr "" - -#: ../blockstorage.rst:13 -msgid "" -"To administer the OpenStack Block Storage service, it is helpful to " -"understand a number of concepts. You must make certain choices when you " -"configure the Block Storage service in OpenStack. The bulk of the options " -"come down to two choices, single node or multi-node install. You can read a " -"longer discussion about `Storage Decisions`_ in the `OpenStack Operations " -"Guide`_." -msgstr "" - -#: ../telemetry-data-collection.rst:742 -msgid "" -"To aggregate 60s worth of samples by ``resource_metadata`` and keep the " -"``resource_metadata`` of the latest received sample::" -msgstr "" - -#: ../telemetry-data-collection.rst:751 -msgid "" -"To aggregate each 15 samples by ``user_id`` and ``resource_metadata`` and " -"keep the ``user_id`` of the first received sample and drop the " -"``resource_metadata``::" -msgstr "" - -#: ../dashboard_sessions.rst:149 -msgid "" -"To avoid a warning when you restart Apache on Ubuntu, create a :file:" -"`blackhole` directory in the dashboard directory, as follows::" -msgstr "" - -#: ../telemetry-measurements.rst:518 -msgid "" -"To avoid duplication of metering data and unnecessary load on the IPMI " -"interface, do not deploy the IPMI agent on nodes that are managed by the " -"Bare metal service and keep the ``conductor.send_sensor_data`` option set to " -"``False`` in the :file:`ironic.conf` configuration file." -msgstr "" - -#: ../objectstorage-monitoring.rst:133 -msgid "" -"To avoid the problems inherent with middleware-based monitoring and after-" -"the-fact log processing, the sending of StatsD meters is integrated into " -"Object Storage itself. The submitted change set (see https://review." -"openstack.org/#change,6058) currently reports 124 meters across 15 Object " -"Storage daemons and the tempauth middleware. Details of the meters tracked " -"are in the `Administrator's Guide `__." -msgstr "" - -#: ../blockstorage_backup_disks.rst:10 -msgid "" -"To back up a volume, you must create a snapshot of it. An LVM snapshot is " -"the exact copy of a logical volume, which contains data in a frozen state. " -"This prevents data corruption, because data cannot be manipulated during the " -"volume creation process. Remember that the volumes created through a :" -"command:`nova volume-create` command exist in an LVM logical volume." -msgstr "" - -#: ../compute-networking-nova.rst:591 -msgid "" -"To be able to assign a floating IP address, edit the :file:`/etc/nova/nova." -"conf` file to specify which interface the ``nova-network`` service should " -"bind public IP addresses to:" -msgstr "" - -#: ../telemetry-data-retrieval.rst:185 -msgid "" -"To be able to use the ``ceilometer`` command, the python-ceilometerclient " -"package needs to be installed and configured properly. For details about the " -"installation process, see the `Telemetry chapter `__ in the " -"OpenStack Installation Guide." -msgstr "" - -#: ../compute-manage-users.rst:13 -msgid "" -"To begin using Compute, you must create a user with the Identity service." -msgstr "" - -#: ../compute-manage-logs.rst:18 -msgid "" -"To change the logging level, add ``DEBUG``, ``INFO``, ``WARNING``, or " -"``ERROR`` as a parameter." -msgstr "" - -#: ../compute-networking-nova.rst:633 -msgid "To check if IP forwarding is enabled, run:" -msgstr "" - -#: ../blockstorage_backup_disks.rst:134 -msgid "To check the partition table map, run this command::" -msgstr "" - -#: ../orchestration-stack-domain-users.rst:130 -msgid "" -"To clarify that last point, that means there are now two paths which can " -"result in retrieval of the same data via the Orchestration API. The example " -"for resource-metadata is below::" -msgstr "" - -#: ../blockstorage_volume_number_weigher.rst:28 -msgid "" -"To configure ``VolumeNumberWeigher``, use ``LVMVolumeDriver`` as the volume " -"driver." -msgstr "" - -#: ../networking_adv-operational-features.rst:12 -msgid "" -"To configure logging for Networking components, use one of these methods:" -msgstr "" - -#: ../compute-images-instances.rst:176 -msgid "" -"To configure property protection, the cloud administrator completes these " -"steps:" -msgstr "" - -#: ../networking_introduction.rst:45 -msgid "" -"To configure rich network topologies, you can create and configure networks " -"and subnets and instruct other OpenStack services like Compute to attach " -"virtual devices to ports on these networks." -msgstr "" - -#: ../orchestration-stack-domain-users.rst:43 -msgid "To configure stack domain users the following steps shall be executed:" -msgstr "" - -#: ../dashboard_sessions.rst:103 -msgid "To configure the MySQL database, create the dash database::" -msgstr "" - -#: ../networking_config-plugins.rst:121 -msgid "" -"To configure the NSX-mh controller cluster for OpenStack Networking, locate " -"the ``[default]`` section in the :file:`/etc/neutron/plugins/vmware/nsx.ini` " -"file and add the following entries:" -msgstr "" - -#: ../blockstorage_ratelimit_volume_copy_bandwidth.rst:19 -msgid "" -"To configure the volume copy bandwidth limit, set the " -"``volume_copy_bps_limit`` option in the configuration groups for each back " -"end in the :file:`cinder.conf` file. This option takes the integer of " -"maximum bandwidth allowed for volume data copy in byte per second. If this " -"option is set to ``0``, the rate-limit is disabled." -msgstr "" - -#: ../blockstorage-api-throughput.rst:22 -msgid "" -"To configure this option, open the :file:`/etc/cinder/cinder.conf` " -"configuration file and set the ``osapi_volume_workers`` configuration key to " -"the number of CPU cores/threads on a machine." -msgstr "" - -#: ../compute-remote-console-access.rst:232 -msgid "" -"To connect the service to your Compute deployment, add the following " -"configuration options to your :file:`nova.conf`:" -msgstr "" - -#: ../orchestration-auth-model.rst:64 -msgid "" -"To create a trust, the *trustor* (in this case, the user creating the stack " -"in Orchestration module) provides OpenStack Identity with the following " -"information:" -msgstr "" - -#: ../blockstorage_volume_number_weigher.rst:67 -msgid "" -"To create six 1-GB volumes, run the :command:`cinder create --volume-type " -"lvm 1` command six times::" -msgstr "" - -#: ../compute-remote-console-access.rst:139 -msgid "" -"To customize the VNC console, use the following configuration options in " -"your :file:`nova.conf`:" -msgstr "" - -#: ../compute-security.rst:97 -msgid "" -"To customize the trusted compute pools, use these configuration option " -"settings:" -msgstr "" - -#: ../telemetry-data-collection.rst:571 -msgid "To define the list of excluded meters, use the ``!meter_name`` syntax." -msgstr "" - -#: ../telemetry-data-collection.rst:568 -msgid "To define the list of included meters, use the ``meter_name`` syntax." -msgstr "" - -#: ../telemetry-data-collection.rst:566 -msgid "To define the list of meters, use either of the following:" -msgstr "" - -#: ../telemetry-data-collection.rst:799 -msgid "" -"To demonstrate the use of metadata, here is the implementation of a silly " -"meter that shows average CPU time per core::" -msgstr "" - -#: ../dashboard.rst:19 -msgid "" -"To deploy the dashboard, see the `OpenStack dashboard documentation `__." -msgstr "" - -#: ../networking_config-agents.rst:226 -msgid "" -"To do either of these things, you must run the command within a particular " -"network namespace for the router. The namespace has the name ``qrouter-" -"ROUTER_UUID``. These example commands run in the router namespace with UUID " -"47af3868-0fa8-4447-85f6-1304de32153b:" -msgstr "" - -#: ../blockstorage-api-throughput.rst:18 -msgid "" -"To do so, use the Block Storage API service option ``osapi_volume_workers``. " -"This option allows you to specify the number of API service workers (or OS " -"processes) to launch for the Block Storage API service." -msgstr "" - -#: ../compute-system-admin.rst:25 -msgid "" -"To effectively administer Compute, you must understand how the different " -"installed nodes interact with each other. Compute can be installed in many " -"different ways using multiple servers, but generally multiple compute nodes " -"control the virtual servers and a cloud controller node contains the " -"remaining Compute services." -msgstr "" - -#: ../compute-networking-nova.rst:649 -msgid "To enable IP forwarding dynamically, run:" -msgstr "" - -#: ../networking_adv-config.rst:72 -msgid "" -"To enable L3 metering, you must set the following option in the :file:" -"`neutron.conf` file on the host that runs neutron-server:" -msgstr "" - -#: ../blockstorage_multi_backend.rst:28 -msgid "" -"To enable a multiple-storage back ends, you must set the `enabled_backends` " -"flag in the :file:`cinder.conf` file. This flag defines the names (separated " -"by a comma) of the configuration groups for the different back ends: one " -"name is associated to one configuration group for a back end (such as, " -"``[lvmdriver-1]``)." -msgstr "" - -#: ../blockstorage_volume_number_weigher.rst:19 -msgid "" -"To enable a volume number weigher, set the ``scheduler_default_weighers`` to " -"``VolumeNumberWeigher`` flag in the :file:`cinder.conf` file to define " -"``VolumeNumberWeigher`` as the selected weigher." -msgstr "" - -#: ../networking_config-identity.rst:226 -msgid "" -"To enable proxying the requests, you must update the following fields in " -"``[neutron]`` section in :file:`nova.conf`." -msgstr "" - -#: ../blockstorage_volume_backed_image.rst:38 -msgid "" -"To enable the :command:`cinder upload-to-image` command to create an image " -"that refers an Image-Volume, set the following options in each back-end " -"section of the :file:`cinder.conf` file::" -msgstr "" - -#: ../blockstorage_volume_backed_image.rst:31 -msgid "" -"To enable the Block Storage services to create a new volume by cloning " -"Image- Volume, set the following options in the ``DEFAULT`` section of the :" -"file:`cinder.conf` file. For example::" -msgstr "" - -#: ../blockstorage_image_volume_cache.rst:30 -msgid "" -"To enable the Block Storage services to have access to an Internal Tenant, " -"set the following options in the :file:`cinder.conf` file::" -msgstr "" - -#: ../blockstorage_image_volume_cache.rst:50 -msgid "" -"To enable the Image-Volume cache, set the following configuration option in :" -"file:`cinder.conf`::" -msgstr "" - -#: ../telemetry-data-collection.rst:385 -msgid "" -"To enable the compute agent to run multiple instances simultaneously with " -"workload partitioning, the ``workload_partitioning`` option has to be set to " -"``True`` under the `Compute section `__ in the :file:" -"`ceilometer.conf` configuration file." -msgstr "" - -#: ../telemetry-events.rst:17 -msgid "" -"To enable the creation and storage of events in the Telemetry module " -"``store_events`` option needs to be set to ``True``. For further " -"configuration options, see the event section in the `OpenStack Configuration " -"Reference `__." -msgstr "" - -#: ../blockstorage-driver-filter-weighing.rst:35 -msgid "" -"To enable the driver filter, set the ``scheduler_default_filters`` option in " -"the :file:`cinder.conf` file to ``DriverFilter`` or add it to the list if " -"other filters are already present." -msgstr "" - -#: ../blockstorage-driver-filter-weighing.rst:39 -msgid "" -"To enable the goodness filter as a weigher, set the " -"``scheduler_default_weighers`` option in the :file:`cinder.conf` file to " -"``GoodnessWeigher`` or add it to the list if other weighers are already " -"present." -msgstr "" - -#: ../telemetry-measurements.rst:411 -msgid "" -"To enable the libvirt ``memory.usage`` support, you need to install libvirt " -"version 1.1.1+, QEMU version 1.5+, and you also need to prepare suitable " -"balloon driver in the image. It is applicable particularly for Windows " -"guests, most modern Linux distributions already have it built in. Telemetry " -"is not able to fetch the ``memory.usage`` samples without the image balloon " -"driver." -msgstr "" - -#: ../orchestration-auth-model.rst:119 -msgid "" -"To enable the password authorization model, the following change should be " -"made in ``heat.conf``:" -msgstr "" - -#: ../orchestration-auth-model.rst:126 -msgid "" -"To enable the trusts authorization model, the following change should be " -"made in ``heat.conf``:" -msgstr "" - -#: ../keystone_token-binding.rst:31 -msgid "" -"To enforce checking of token binding, set the ``enforce_token_bind`` option " -"to one of these modes:" -msgstr "" - -#: ../networking_config-plugins.rst:140 -msgid "" -"To ensure correct operations, the ``nsx_user`` user must have administrator " -"credentials on the NSX-mh platform." -msgstr "" - -#: ../networking_config-identity.rst:150 -msgid "" -"To ensure that Compute works properly with Networking (rather than the " -"legacy nova-network mechanism), you must adjust settings in the :file:`nova." -"conf` configuration file." -msgstr "" - -#: ../networking_config-plugins.rst:126 -msgid "" -"To establish and configure the connection with the controller cluster you " -"must set some parameters, including NSX-mh API endpoints, access " -"credentials, and optionally specify settings for HTTP timeouts, redirects " -"and retries in case of connection failures:" -msgstr "" - -#: ../networking_multi-dhcp-agents.rst:159 -msgid "To experiment, you need VMs and a neutron network:" -msgstr "" - -#: ../blockstorage_backup_disks.rst:113 -msgid "" -"To exploit the snapshot with the :command:`tar` command, mount your " -"partition on the Block Storage service server." -msgstr "" - -#: ../blockstorage_volume_backed_image.rst:26 -msgid "" -"To expose locations information, set the following options in the " -"``DEFAULT`` section of the :file:`glance-api.conf` file::" -msgstr "" - -#: ../compute-networking-nova.rst:911 -msgid "" -"To help debug networking issues with reaching VMs, you can disable the " -"firewall by setting this option in :file:`/etc/nova/nova.conf`:" -msgstr "" - -#: ../blockstorage_volume_backups_export_import.rst:49 -msgid "" -"To import backup metadata, run the following command as an OpenStack " -"``admin``::" -msgstr "" - -#: ../telemetry-data-collection.rst:562 -msgid "" -"To include all meters, use the ``*`` wildcard symbol. It is highly advisable " -"to select only the meters that you intend on using to avoid flooding the " -"metering database with unused data." -msgstr "" - -#: ../telemetry-data-collection.rst:276 -msgid "" -"To install and configure this service use the `Install the Telemetry module " -"`__ section in the OpenStack Installation Guide." -msgstr "" - -#: ../compute-manage-the-cloud.rst:27 -msgid "" -"To install python-novaclient, download the tarball from `http://pypi.python." -"org/pypi/python-novaclient/#downloads `__ and then install it in your favorite Python " -"environment:" -msgstr "" - -#: ../objectstorage_components.rst:168 -msgid "" -"To keep track of object data locations, each account in the system has a " -"database that references all of its containers, and each container database " -"references each object." -msgstr "" - -#: ../compute-images-instances.rst:54 -msgid "" -"To launch an instance select an image, flavor, and any optional attributes. " -"The selected flavor provides a root volume, labeled ``vda`` in this diagram, " -"and additional ephemeral storage, labeled ``vdb``. In this example, the " -"``cinder-volume`` store is mapped to the third virtual disk on this " -"instance, ``vdc``." -msgstr "" - -#: ../dashboard.rst:21 -msgid "" -"To launch instances with the dashboard, see the `OpenStack End User Guide " -"`__." -msgstr "" - -#: ../networking_use.rst:38 -msgid "" -"To learn about advanced capabilities available through the neutron command-" -"line interface (CLI), read the networking section in the `OpenStack End User " -"Guide `__." -msgstr "" - -#: ../compute-networking-nova.rst:342 -msgid "" -"To list supported versions for the EC2-compatible metadata API, make a GET " -"request to ``http://169.254.169.254``:" -msgstr "" - -#: ../blockstorage_multi_backend.rst:152 -msgid "To list the extra-specifications, use this command::" -msgstr "" - -#: ../compute-networking-nova.rst:661 -msgid "" -"To make the changes permanent, edit the ``/etc/sysctl.conf`` file and update " -"the IP forwarding setting:" -msgstr "" - -#: ../dashboard_sessions.rst:176 -msgid "" -"To mitigate the performance issues of database queries, you can use the " -"Django ``cached_db`` session back end, which utilizes both your database and " -"caching infrastructure to perform write-through caching and efficient " -"retrieval." -msgstr "" - -#: ../compute-flavors.rst:29 -msgid "" -"To modify an existing flavor in the dashboard, you must delete the flavor " -"and create a modified one with the same name." -msgstr "" - -#: ../compute-remote-console-access.rst:5 -msgid "" -"To provide a remote console or remote desktop access to guest virtual " -"machines, use VNC or SPICE HTML5 through either the OpenStack dashboard or " -"the command line. Best practice is to select one or the other to run." -msgstr "" - -#: ../networking_config-identity.rst:201 -msgid "" -"To proxy security groups to Networking, use the following configuration " -"values in :file:`nova.conf`:" -msgstr "" - -#: ../blockstorage_volume_backed_image.rst:54 -msgid "" -"To register an existing volume as a new Volume-backed image, use the " -"following commands::" -msgstr "" - -#: ../blockstorage_glusterfs_removal.rst:15 -msgid "" -"To remove a GlusterFS volume from usage as a back end, delete the volume's " -"corresponding entry from the shares file. After doing so, restart the Block " -"Storage services." -msgstr "" - -#: ../objectstorage_replication.rst:21 -msgid "" -"To replicate deletions in addition to creations, every deleted record or " -"file in the system is marked by a tombstone. The replication process cleans " -"up tombstones after a time period known as the *consistency window*. This " -"window defines the duration of the replication and how long transient " -"failure can remove a node from the cluster. Tombstone cleanup must be tied " -"to replication to reach replica convergence." -msgstr "" - -#: ../ts-eql-volume-size.rst:19 -msgid "To reproduce the issue follow the steps in the following procedure." -msgstr "" - -#: ../compute-node-down.rst:327 -msgid "" -"To reproduce the power loss, connect to the compute node which runs that " -"instance and close the iSCSI session. Do not detach the volume using the :" -"command:`nova volume-detach` command, manually close the iSCSI session. This " -"example closes an iSCSI session with the number 15:" -msgstr "" - -#: ../blockstorage_glusterfs_removal.rst:19 -msgid "" -"To restart the Block Storage services on CentOS, Fedora, openSUSE, Red Hat " -"Enterprise Linux, or SUSE Linux Enterprise, run::" -msgstr "" - -#: ../blockstorage_glusterfs_removal.rst:24 -msgid "To restart the Block Storage services on Ubuntu or Debian, run::" -msgstr "" - -# #-#-#-#-# blockstorage_glusterfs_backend.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -# #-#-#-#-# blockstorage_nfs_backend.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -#: ../blockstorage_glusterfs_backend.rst:160 -#: ../blockstorage_nfs_backend.rst:115 -msgid "" -"To restart the ``cinder`` volume service on CentOS, Fedora, openSUSE, Red " -"Hat Enterprise Linux, or SUSE Linux Enterprise, run::" -msgstr "" - -# #-#-#-#-# blockstorage_glusterfs_backend.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -# #-#-#-#-# blockstorage_nfs_backend.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -#: ../blockstorage_glusterfs_backend.rst:165 -#: ../blockstorage_nfs_backend.rst:121 -msgid "To restart the ``cinder`` volume service on Ubuntu or Debian, run::" -msgstr "" - -#: ../compute-remote-console-access.rst:221 -msgid "To restart the service, run:" -msgstr "" - -#: ../identity_concepts.rst:200 -msgid "" -"To restrict all Compute service requests to require this role, the resulting " -"file looks like:" -msgstr "" - -#: ../identity_concepts.rst:193 -msgid "" -"To restrict the creation of volumes to users who have the ``compute-user`` " -"role in a particular tenant, you add ``\"role:compute-user\"``:" -msgstr "" - -#: ../identity_concepts.rst:178 -msgid "" -"To restrict users from performing operations in, for example, the Compute " -"service, you must create a role in the Identity service and then modify the :" -"file:`/etc/nova/policy.json` file so that this role is required for Compute " -"operations." -msgstr "" - -#: ../telemetry-data-retrieval.rst:356 -msgid "" -"To retrieve a list of recent events that occurred in the system, the " -"following command can be executed:" -msgstr "" - -#: ../compute-networking-nova.rst:331 -msgid "" -"To retrieve a list of supported versions for the OpenStack metadata API, " -"make a GET request to ``http://169.254.169.254/openstack``:" -msgstr "" - -#: ../telemetry-data-retrieval.rst:207 -msgid "" -"To retrieve the list of collected meters, the following command should be " -"used::" -msgstr "" - -#: ../networking_multi-dhcp-agents.rst:461 -msgid "To run the following commands, you must stop the DHCP agent on HostA." -msgstr "" - -#: ../telemetry-data-collection.rst:459 -msgid "" -"To send samples to Telemetry using the command line client, the following " -"command should be invoked::" -msgstr "" - -#: ../compute-flavors.rst:231 -msgid "To set the behavior, use:" -msgstr "" - -#: ../blockstorage-manage-volumes.rst:51 -msgid "" -"To set up Compute to use volumes, ensure that Block Storage is installed " -"along with ``lvm2``. This guide describes how to troubleshoot your " -"installation and back up your Compute volumes." -msgstr "" - -#: ../compute-root-wrap-reference.rst:78 -msgid "" -"To set up this workaround, configure the ``disable_rootwrap`` option in the " -"``[workaround]`` section of the :file:`nova.conf` configuration file." -msgstr "" - -#: ../telemetry-data-retrieval.rst:480 -msgid "" -"To solve the above mentioned problem, the notion of multi-publisher can be " -"configured for each datapoint within the Telemetry module, allowing the same " -"technical meter or event to be published multiple times to multiple " -"destinations, each potentially using a different transport." -msgstr "" - -#: ../orchestration-auth-model.rst:133 -msgid "" -"To specify the trustor roles that it delegates to trustee during " -"authorization, the ``trusts_delegated_roles`` parameter should be specified " -"in ``heat.conf``. If ``trusts_delegated_roles`` is not defined, then all the " -"trustor roles are delegated to trustee." -msgstr "" - -#: ../identity_start.rst:4 -msgid "To start the services for Identity, run the following command:" -msgstr "" - -#: ../compute-remote-console-access.rst:144 -msgid "" -"To support :ref:`live migration `, " -"you cannot specify a specific IP address for ``vncserver_listen``, because " -"that IP address does not exist on the destination host." -msgstr "" - -#: ../networking_adv-operational-features.rst:56 -msgid "" -"To support DHCP agent, rpc\\_notifier driver must be set. To set up the " -"notification, edit notification options in :file:`neutron.conf`:" -msgstr "" - -#: ../blockstorage_over_subscription.rst:17 -msgid "" -"To support oversubscription in thin provisioning, a flag " -"``max_over_subscription_ratio`` is introduced into :file:`cinder.conf`. This " -"is a float representation of the oversubscription ratio when thin " -"provisioning is involved. Default ratio is 20.0, meaning provisioned " -"capacity can be 20 times of the total physical capacity. A ratio of 10.5 " -"means provisioned capacity can be 10.5 times of the total physical capacity. " -"A ratio of 1.0 means provisioned capacity cannot exceed the total physical " -"capacity. A ratio lower than 1.0 is ignored and the default value is used " -"instead." -msgstr "" - -#: ../objectstorage_ringbuilder.rst:94 -msgid "" -"To support the gradual change in replica counts, a ring can have a real " -"number of replicas and is not restricted to an integer number of replicas." -msgstr "" - -#: ../identity_troubleshoot.rst:5 -msgid "" -"To troubleshoot the Identity service, review the logs in the ``/var/log/" -"keystone/keystone.log`` file." -msgstr "" - -#: ../networking_config-agents.rst:199 -msgid "" -"To uplink the node that runs neutron-l3-agent to the external network, " -"create a bridge named \"br-ex\" and attach the NIC for the external network " -"to this bridge." -msgstr "" - -#: ../compute-configuring-migrations.rst:309 -#: ../compute-configuring-migrations.rst:413 -msgid "" -"To use block migration, you must use the :option:`--block-migrate` parameter " -"with the live migration command." -msgstr "" - -#: ../compute-remote-console-access.rst:247 -msgid "To use live migration, use the 0.0.0.0 address." -msgstr "" - -#: ../compute-root-wrap-reference.rst:12 -msgid "" -"To use rootwrap, prefix the Compute command with :command:`nova-rootwrap`. " -"For example:" -msgstr "" - -#: ../compute-configuring-migrations.rst:347 -msgid "" -"To use shared storage live migration with XenServer hypervisors, the hosts " -"must be joined to a XenServer pool. To create that pool, a host aggregate " -"must be created with specific metadata. This metadata is used by the XAPI " -"plug-ins to establish the pool." -msgstr "" - -#: ../networking_adv-features.rst:330 -msgid "" -"To use the Compute security group API with Networking, the Networking plug-" -"in must implement the security group API. The following plug-ins currently " -"implement this: ML2, Open vSwitch, Linux Bridge, NEC, and VMware NSX." -msgstr "" - -#: ../networking_adv-features.rst:319 -msgid "" -"To use the Compute security group APIs or use Compute to orchestrate the " -"creation of ports for instances on specific security groups, you must " -"complete additional configuration. You must configure the :file:`/etc/nova/" -"nova.conf` file and set the ``security_group_api=neutron`` option on every " -"node that runs nova-compute and nova-api. After you make this change, " -"restart nova-api and nova-compute to pick up this change. Then, you can use " -"both the Compute and OpenStack Network security group APIs at the same time." -msgstr "" - -#: ../compute-service-groups.rst:95 -msgid "" -"To use the memcache driver, you must install memcached. You might already " -"have it installed, as the same driver is also used for the OpenStack Object " -"Storage and OpenStack dashboard. If you need to install memcached, see the " -"instructions in the `OpenStack Installation Guide `_." -msgstr "" - -#: ../networking_config-agents.rst:298 -msgid "To use the reference implementation, you must set:" -msgstr "" - -#: ../telemetry-alarms.rst:116 -msgid "" -"To use this workload partitioning solution set the ``evaluation_service`` " -"option to ``default``. For more information, see the alarm section in the " -"`OpenStack Configuration Reference `_." -msgstr "" - -#: ../database.rst:268 -msgid "" -"To validate your new datastore and version, start by listing the datastores " -"on your system::" -msgstr "" - -#: ../compute-images-instances.rst:288 ../compute-images-instances.rst:298 -msgid "" -"To view a sample configuration file, see `glance-api.conf `__." -msgstr "" - -#: ../networking_use.rst:109 -msgid "" -"To view all tenant IDs in Identity, run the following command as an Identity " -"service admin user:" -msgstr "" - -#: ../networking_adv-features.rst:159 -msgid "" -"To view or set provider extended attributes, a client must be authorized for " -"the ``extension:provider_network:view`` and ``extension:provider_network:" -"set`` actions in the Networking policy configuration. The default Networking " -"configuration authorizes both actions for users with the admin role. An " -"authorized client or an administrative user can view and set the provider " -"extended attributes through Networking API calls. See the section called :" -"ref:`Authentication and authorization` for details on policy configuration." -msgstr "" - -#: ../ts-eql-volume-size.rst:137 -msgid "" -"To work around this problem, increase the target size of the new image to " -"the next whole number. In the problem example, you created a 1 GB volume to " -"be used as volume-backed image, so a new volume using this volume-backed " -"image should use a size of 2 GB:" -msgstr "" - -#: ../identity_concepts.rst:81 -msgid "Token" -msgstr "" - -#: ../keystone_token-binding.rst:5 -msgid "" -"Token binding embeds information from an external authentication mechanism, " -"such as a Kerberos server or X.509 certificate, inside a token. By using " -"token binding, a client can enforce the use of a specified external " -"authentication mechanism with the token. This additional security mechanism " -"ensures that if a token is stolen, for example, it is not usable without " -"external authentication." -msgstr "" - -#: ../keystone_caching_layer.rst:59 -msgid "" -"Token caching is configurable independently of the ``revocation_list`` " -"caching. Lifted expiration checks from the token drivers to the token " -"manager. This ensures that cached tokens will still raise a " -"``TokenNotFound`` flag when expired." -msgstr "" - -#: ../telemetry-data-collection.rst:330 -msgid "" -"Tooz supports `various drivers `__ including the following back end solutions:" -msgstr "" - -#: ../telemetry-measurements.rst:1079 -msgid "Total connectio\\ ns on a LB" -msgstr "" - -#: ../telemetry-measurements.rst:602 -msgid "Total disk size" -msgstr "" - -#: ../telemetry-measurements.rst:608 -msgid "Total physical memory size" -msgstr "" - -#: ../telemetry-measurements.rst:759 ../telemetry-measurements.rst:808 -msgid "Total size of s\\ tored objects" -msgstr "" - -#: ../telemetry-measurements.rst:779 -msgid "Total size of s\\ tored objects i\\ n container" -msgstr "" - -#: ../telemetry-measurements.rst:822 -msgid "Total size of s\\ tored objects in container" -msgstr "" - -#: ../telemetry-measurements.rst:620 -msgid "Total swap space size" -msgstr "" - -#: ../telemetry-data-collection.rst:697 -msgid "" -"Transformer to apply a unit conversion. It takes the volume of the meter and " -"multiplies it with the given ``scale`` expression. Also supports " -"``map_from`` and ``map_to`` like the rate of change transformer." -msgstr "" - -#: ../telemetry-data-collection.rst:646 -msgid "Transformers" -msgstr "" - -#: ../compute-remote-console-access.rst:97 -msgid "" -"Transparently deals with hypervisor-specific connection details to provide a " -"uniform client experience." -msgstr "" - -#: ../objectstorage-troubleshoot.rst:3 -msgid "Troubleshoot Object Storage" -msgstr "" - -#: ../telemetry-troubleshooting-guide.rst:2 -msgid "Troubleshoot Telemetry" -msgstr "" - -#: ../ts_cinder_config.rst:6 -msgid "Troubleshoot the Block Storage configuration" -msgstr "" - -#: ../identity_troubleshoot.rst:3 -msgid "Troubleshoot the Identity service" -msgstr "" - -#: ../blockstorage-troubleshoot.rst:3 -msgid "Troubleshoot your installation" -msgstr "" - -#: ../cross_project_cors.rst:112 -msgid "Troubleshooting" -msgstr "" - -#: ../compute-networking-nova.rst:841 -msgid "Troubleshooting Networking" -msgstr "" - -#: ../keystone_configure_with_SSL.rst:56 -msgid "True enables SSL. Default is False." -msgstr "" - -#: ../telemetry-alarms.rst:192 -msgid "" -"True if actions should be repeatedly notified while the alarm remains in the " -"target state (defaults to False)." -msgstr "" - -#: ../telemetry-alarms.rst:188 -msgid "" -"True if evaluation and actioning is to be enabled for this alarm (defaults " -"to True)." -msgstr "" - -#: ../keystone_certificates_for_pki.rst:181 -msgid "Trust CA certificate chain in PEM format" -msgstr "" - -#: ../telemetry-measurements.rst:888 -msgid "Trust is created" -msgstr "" - -#: ../telemetry-measurements.rst:891 -msgid "Trust is deleted" -msgstr "" - -#: ../compute-security.rst:12 -msgid "Trusted compute pools" -msgstr "" - -#: ../compute-security.rst:22 -msgid "" -"Trusted compute pools provide the ability for cloud subscribers to request " -"services run only on verified compute nodes." -msgstr "" - -#: ../blockstorage_over_subscription.rst:65 -msgid "" -"Two capabilities are added here to allow a back end or pool to claim support " -"for thin provisioning, or thick provisioning, or both." -msgstr "" - -# #-#-#-#-# blockstorage-driver-filter-weighing.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -# #-#-#-#-# compute-manage-logs.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -# #-#-#-#-# networking_adv-features.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -# #-#-#-#-# telemetry-measurements.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -#: ../blockstorage-driver-filter-weighing.rst:101 -#: ../compute-manage-logs.rst:203 ../networking_adv-features.rst:128 -#: ../telemetry-measurements.rst:31 ../telemetry-measurements.rst:97 -#: ../telemetry-measurements.rst:430 ../telemetry-measurements.rst:484 -#: ../telemetry-measurements.rst:528 ../telemetry-measurements.rst:589 -#: ../telemetry-measurements.rst:664 ../telemetry-measurements.rst:697 -#: ../telemetry-measurements.rst:752 ../telemetry-measurements.rst:802 -#: ../telemetry-measurements.rst:839 ../telemetry-measurements.rst:910 -#: ../telemetry-measurements.rst:973 ../telemetry-measurements.rst:1059 -#: ../telemetry-measurements.rst:1137 ../telemetry-measurements.rst:1202 -#: ../telemetry-measurements.rst:1253 ../telemetry-measurements.rst:1279 -#: ../telemetry-measurements.rst:1302 ../telemetry-measurements.rst:1322 -msgid "Type" -msgstr "" - -#: ../networking_adv-features.rst:608 -msgid "Type and constraints" -msgstr "" - -#: ../telemetry-data-collection.rst:445 -msgid "Type of meter. (``--meter-type``)" -msgstr "" - -#: ../compute-remote-console-access.rst:117 -msgid "Typical deployment" -msgstr "" - -#: ../objectstorage_account_reaper.rst:13 -msgid "" -"Typically, a specific retention time or undelete are not provided. However, " -"you can set a ``delay_reaping`` value in the ``[account-reaper]`` section of " -"the :file:`account-server.conf` file to delay the actual deletion of data. " -"At this time, to undelete you have to update the account database replicas " -"directly, setting the status column to an empty string and updating the put" -"\\_timestamp to be greater than the delete\\_timestamp." -msgstr "" - -#: ../compute-images-instances.rst:308 -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 " -"images are not stored in glance—rather in a back end, which could be Object " -"Storage, a filesystem or any other supported method—the connection is made " -"from the compute node to the Image service and the image is transferred over " -"this connection. The Image service streams the image from the back end to " -"the compute node." -msgstr "" - -#: ../objectstorage_arch.rst:38 -msgid "" -"Typically, the tier consists of a collection of 1U servers. These machines " -"use a moderate amount of RAM and are network I/O intensive. Since these " -"systems field each incoming API request, you should provision them with two " -"high-throughput (10GbE) interfaces - one for the incoming \"front-end\" " -"requests and the other for the \"back-end\" access to the object storage " -"nodes to put and fetch data." -msgstr "" - -#: ../database.rst:237 -msgid "Ubuntu 14.04" -msgstr "" - -#: ../networking_config-plugins.rst:170 -msgid "" -"Ubuntu packaging currently does not update the neutron init script to point " -"to the NSX-mh configuration file. Instead, you must manually update :file:`/" -"etc/default/neutron-server` to add this line:" -msgstr "" - -#: ../compute-networking-nova.rst:5 -msgid "" -"Understanding the networking configuration options helps you design the best " -"configuration for your Compute instances." -msgstr "" - -#: ../objectstorage_features.rst:54 -msgid "Unified support for block volumes using a variety of storage systems." -msgstr "" - -#: ../networking_config-identity.rst:144 -msgid "" -"Uninstall nova-network and reboot any physical nodes that have been running " -"nova-network before using them to run Networking. Inadvertently running the " -"nova-network process while using Networking can cause problems, as can stale " -"iptables rules pushed down by previously running nova-network." -msgstr "" - -#: ../telemetry-measurements.rst:97 ../telemetry-measurements.rst:430 -#: ../telemetry-measurements.rst:484 ../telemetry-measurements.rst:528 -#: ../telemetry-measurements.rst:589 ../telemetry-measurements.rst:664 -#: ../telemetry-measurements.rst:697 ../telemetry-measurements.rst:752 -#: ../telemetry-measurements.rst:802 ../telemetry-measurements.rst:839 -#: ../telemetry-measurements.rst:910 ../telemetry-measurements.rst:973 -#: ../telemetry-measurements.rst:1059 ../telemetry-measurements.rst:1137 -#: ../telemetry-measurements.rst:1202 ../telemetry-measurements.rst:1253 -#: ../telemetry-measurements.rst:1279 ../telemetry-measurements.rst:1302 -#: ../telemetry-measurements.rst:1322 -msgid "Unit" -msgstr "" - -#: ../telemetry-data-collection.rst:619 -msgid "Unit conversion" -msgstr "" - -#: ../telemetry-data-collection.rst:455 -msgid "Unit of meter. (``--meter-unit``)" -msgstr "" - -#: ../objectstorage_features.rst:15 -msgid "Unlimited storage" -msgstr "" - -#: ../blockstorage_backup_disks.rst:199 -msgid "Unmount the volume::" -msgstr "" - -#: ../identity_concepts.rst:345 -msgid "Update a group (change its name or description)" -msgstr "" - -#: ../networking_introduction.rst:293 -msgid "Update a port by adding allowed address pairs:" -msgstr "" - -#: ../networking_adv-features.rst:733 -msgid "" -"Update a router with rules to permit traffic by default but block traffic " -"from external networks to the 10.10.10.0/24 subnet:" -msgstr "" - -#: ../compute-manage-volumes.rst:42 -msgid "Update an attached volume." -msgstr "" - -#: ../networking_config-agents.rst:73 -msgid "" -"Update any options in the :file:`/etc/neutron/dhcp_agent.ini` file that " -"depend on the plug-in in use. See the sub-sections." -msgstr "" - -#: ../telemetry-measurements.rst:960 -msgid "Update requests for this IP" -msgstr "" - -#: ../telemetry-measurements.rst:921 -msgid "Update requests for this network" -msgstr "" - -#: ../telemetry-measurements.rst:940 -msgid "Update requests for this port" -msgstr "" - -#: ../telemetry-measurements.rst:950 -msgid "Update requests for this router" -msgstr "" - -#: ../telemetry-measurements.rst:931 -msgid "Update requests for this subnet" -msgstr "" - -#: ../networking_multi-dhcp-agents.rst:132 -msgid "Update the DHCP configuration file :file:`/etc/neutron/dhcp_agent.ini`:" -msgstr "" - -#: ../compute-node-down.rst:80 -msgid "Update the VNC IP to `0.0.0.0`" -msgstr "" - -#: ../networking_config-agents.rst:503 -msgid "" -"Update the admin status and description for a specified agent. The command " -"can be used to enable and disable agents by using ``--admin-state-up`` " -"parameter set to ``False`` or ``True``." -msgstr "" - -#: ../compute-node-down.rst:217 -msgid "" -"Update the database to clean the stalled state. Do this for every volume, " -"using these queries:" -msgstr "" - -#: ../compute-configuring-migrations.rst:221 -msgid "" -"Update the libvirt configurations so that the calls can be made securely. " -"These methods enable remote access over TCP and are not documented here." -msgstr "" - -#: ../telemetry-measurements.rst:723 -msgid "Update the name or description of the volume" -msgstr "" - -#: ../networking_multi-dhcp-agents.rst:113 -msgid "Update the nova configuration file :file:`/etc/nova/nova.conf`:" -msgstr "" - -#: ../networking_multi-dhcp-agents.rst:70 -#: ../networking_multi-dhcp-agents.rst:98 -msgid "" -"Update the plug-in configuration file :file:`/etc/neutron/plugins/" -"linuxbridge/linuxbridge_conf.ini`:" -msgstr "" - -#: ../telemetry-measurements.rst:727 -msgid "Update the size of the volume" -msgstr "" - -#: ../networking_config-identity.rst:213 -msgid "" -"Update to ``neutron``, so that all security group requests are proxied to " -"the Network Service." -msgstr "" - -#: ../networking_config-identity.rst:209 -msgid "" -"Update to ``nova.virt.firewall.NoopFirewallDriver``, so that nova-compute " -"does not perform iptables-based filtering itself." -msgstr "" - -#: ../networking_config-identity.rst:234 -msgid "" -"Update to ``true``, otherwise nova-api will not properly respond to requests " -"from the neutron-metadata-agent." -msgstr "" - -#: ../networking_config-identity.rst:238 -msgid "" -"Update to a string \"password\" value. You must also configure the same " -"value in the ``metadata_agent.ini`` file, to authenticate requests made for " -"metadata." -msgstr "" - -#: ../networking_config-identity.rst:187 -msgid "" -"Update to the Identity server IP and port. This is the Identity (keystone) " -"admin API server IP and port value, and not the Identity service API IP and " -"port." -msgstr "" - -#: ../networking_config-identity.rst:173 -msgid "" -"Update to the hostname/IP and port of the neutron-server instance for this " -"deployment." -msgstr "" - -#: ../networking_config-identity.rst:178 -msgid "" -"Update to the name of the service tenant created in the above section on " -"Identity configuration." -msgstr "" - -#: ../networking_config-identity.rst:181 -msgid "" -"Update to the name of the user created in the above section on Identity " -"configuration." -msgstr "" - -#: ../networking_config-identity.rst:184 -msgid "" -"Update to the password of the user created in the above section on Identity " -"configuration." -msgstr "" - -#: ../compute-live-migration-usage.rst:111 -msgid "Updated_at" -msgstr "" - -#: ../objectstorage_components.rst:248 -msgid "Upload" -msgstr "" - -#: ../compute-manage-logs.rst:204 -msgid "Url" -msgstr "" - -# #-#-#-#-# blockstorage_multi_backend.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -# #-#-#-#-# blockstorage_volume_number_weigher.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -#: ../blockstorage_multi_backend.rst:164 -#: ../blockstorage_volume_number_weigher.rst:65 -msgid "Usage" -msgstr "" - -#: ../blockstorage_get_capabilities.rst:75 -msgid "Usage of REST API" -msgstr "" - -#: ../blockstorage_get_capabilities.rst:25 -msgid "Usage of cinder client" -msgstr "" - -#: ../orchestration-stack-domain-users.rst:106 -msgid "Usage workflow" -msgstr "" - -#: ../compute-node-down.rst:228 -msgid "Use :command:`nova volume-list` commands to list all volumes." -msgstr "" - -#: ../networking_use.rst:174 -msgid "Use Compute with Networking" -msgstr "" - -#: ../keystone_integrate_assignment_backend_ldap.rst:140 -msgid "" -"Use DN of the group entry to hold enabled projects when using enabled " -"emulation." -msgstr "" - -#: ../keystone_integrate_identity_backend_ldap.rst:235 -msgid "" -"Use DN of the group entry to hold enabled user when using enabled emulation." -msgstr "" - -#: ../keystone_external_authentication.rst:12 -msgid "Use HTTPD authentication" -msgstr "" - -#: ../blockstorage-lio-iscsi-support.rst:3 -msgid "Use LIO iSCSI support" -msgstr "" - -#: ../networking_use.rst:3 -msgid "Use Networking" -msgstr "" - -#: ../compute-manage-logs.rst:221 -msgid "" -"Use Python websocket with the URL to generate ``.send``, ``.recv``, and ``." -"fileno`` methods for serial console access. For example:" -msgstr "" - -#: ../keystone_external_authentication.rst:22 -msgid "Use X.509" -msgstr "" - -#: ../keystone_integrate_with_ldap.rst:98 -msgid "" -"Use ``alias_dereferencing`` to control the LDAP dereferencing option for " -"queries." -msgstr "" - -#: ../keystone_integrate_with_ldap.rst:100 -msgid "" -"Use ``chase_referrals`` to override the system's default referral chasing " -"behavior for queries." -msgstr "" - -#: ../identity_troubleshoot.rst:174 -msgid "" -"Use ``cron`` to schedule this command to run frequently based on your " -"workload. For large workloads, running it every minute is recommended." -msgstr "" - -#: ../keystone_integrate_with_ldap.rst:114 -msgid "" -"Use ``debug_level`` to set the LDAP debugging level for LDAP calls. A value " -"of zero means that debugging is not enabled." -msgstr "" - -#: ../keystone_integrate_with_ldap.rst:96 -msgid "" -"Use ``page_size`` to control the maximum results per page. A value of zero " -"disables paging." -msgstr "" - -#: ../keystone_integrate_with_ldap.rst:93 -msgid "" -"Use ``query_scope`` to control the scope level of data presented (search " -"only the first level or search an entire sub-tree) through LDAP." -msgstr "" - -#: ../compute-networking-nova.rst:890 -msgid "" -"Use ``tcpdump`` to identify if packets are being routed to the inbound " -"interface on the compute host. If the packets are reaching the compute hosts " -"but the connection is failing, the issue may be that the packet is being " -"dropped by reverse path filtering. Try disabling reverse-path filtering on " -"the inbound interface. For example, if the inbound interface is ``eth2``, " -"run:" -msgstr "" - -#: ../keystone_integrate_with_ldap.rst:147 -msgid "" -"Use ``use_auth_pool`` to enable LDAP connection pooling for end user " -"authentication. Configure connection pool size and lifetime in seconds." -msgstr "" - -#: ../keystone_integrate_with_ldap.rst:130 -msgid "" -"Use ``use_pool`` to enable LDAP connection pooling. Configure connection " -"pool size, maximum retry, reconnect trials, timeout (-1 indicates indefinite " -"wait) and lifetime in seconds." -msgstr "" - -#: ../objectstorage_components.rst:241 -msgid "Use cases" -msgstr "" - -# #-#-#-#-# keystone_integrate_assignment_backend_ldap.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -# #-#-#-#-# keystone_integrate_identity_backend_ldap.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -#: ../keystone_integrate_assignment_backend_ldap.rst:95 -#: ../keystone_integrate_identity_backend_ldap.rst:188 -msgid "Use filters to control the scope of data presented through LDAP." -msgstr "" - -#: ../telemetry-data-collection.rst:587 -msgid "Use only the wildcard symbol." -msgstr "" - -#: ../telemetry-best-practices.rst:125 -msgid "" -"Use replica sets in MongoDB. Replica sets provide high availability through " -"automatic failover. If your primary node fails, MongoDB will elect a " -"secondary node to replace the primary node, and your cluster will remain " -"functional." -msgstr "" - -#: ../telemetry-best-practices.rst:133 -msgid "" -"Use sharding in MongoDB. Sharding helps in storing data records across " -"multiple machines and is the MongoDB’s approach to meet the demands of data " -"growth." -msgstr "" - -#: ../blockstorage-manage-volumes.rst:27 -msgid "" -"Use the :command:`cinder create` command to create a volume. This command " -"creates an LV into the volume group (VG) ``cinder-volumes``." -msgstr "" - -#: ../networking_multi-dhcp-agents.rst:11 -msgid "" -"Use the :command:`neutron ext-list` client command to check if these " -"extensions are enabled:" -msgstr "" - -#: ../compute-manage-logs.rst:192 -msgid "" -"Use the :command:`nova get-serial-proxy` command to retrieve the websocket " -"URL for the serial console on the instance:" -msgstr "" - -#: ../blockstorage_backup_disks.rst:187 -msgid "" -"Use the :command:`sha1sum` command carefully because the time it takes to " -"complete the calculation is directly proportional to the size of the file." -msgstr "" - -#: ../blockstorage_backup_disks.rst:161 -msgid "Use the :command:`tar` command to create archives" -msgstr "" - -#: ../blockstorage_backup_disks.rst:60 -msgid "" -"Use the :option:`--snapshot` configuration option to tell LVM that you want " -"a snapshot of an already existing volume. The command includes the size of " -"the space reserved for the snapshot volume, the name of the snapshot, and " -"the path of an already existing volume. Generally, this path is :file:`/dev/" -"cinder-volumes/VOLUME_NAME`." -msgstr "" - -#: ../networking_config-agents.rst:45 -msgid "" -"Use the ``NSX Administrator Guide`` to add the node as a Hypervisor by using " -"the NSX Manager GUI. Even if your forwarding node has no VMs and is only " -"used for services agents like ``neutron-dhcp-agent`` or ``neutron-lbaas-" -"agent``, it should still be added to NSX as a Hypervisor." -msgstr "" - -#: ../compute-node-down.rst:281 -msgid "" -"Use the ``errors=remount`` parameter in the :file:`fstab` file to prevent " -"data corruption." -msgstr "" - -#: ../compute-remote-console-access.rst:28 -msgid "" -"Use the following options to configure SPICE as the console for OpenStack " -"Compute:" -msgstr "" - -#: ../telemetry-data-collection.rst:591 -msgid "Use the list of excluded meters." -msgstr "" - -#: ../telemetry-data-collection.rst:589 -msgid "Use the list of included meters." -msgstr "" - -#: ../blockstorage-manage-volumes.rst:29 -msgid "" -"Use the nova :command:`volume-attach` command to attach the volume to an " -"instance. This command creates a unique iSCSI IQN that is exposed to the " -"compute node." -msgstr "" - -#: ../networking_multi-dhcp-agents.rst:423 -msgid "Use the previous commands to assign the network to agents." -msgstr "" - -#: ../objectstorage_ringbuilder.rst:5 -msgid "" -"Use the swift-ring-builder utility to build and manage rings. This utility " -"assigns partitions to devices and writes an optimized Python structure to a " -"gzipped, serialized file on disk for transmission to the servers. The server " -"processes occasionally check the modification time of the file and reload in-" -"memory copies of the ring structure as needed. If you use a slightly older " -"version of the ring, one of the three replicas for a partition subset will " -"be incorrect because of the way the ring-builder manages changes to the " -"ring. You can work around this issue." -msgstr "" - -#: ../compute-flavors.rst:90 -msgid "" -"Use these optional parameters to control weight shares, enforcement " -"intervals for runtime quotas, and a quota for maximum allowed bandwidth:" -msgstr "" - -#: ../blockstorage_backup_disks.rst:48 -msgid "Use this command to list all volumes" -msgstr "" - -#: ../compute-node-down.rst:23 -msgid "Use this procedure to recover a failed compute node manually:" -msgstr "" - -#: ../keystone_use_trusts.rst:3 -msgid "Use trusts" -msgstr "" - -#: ../telemetry-data-collection.rst:593 -msgid "Use wildcard symbol with the list of excluded meters." -msgstr "" - -#: ../telemetry-measurements.rst:605 -msgid "Used disk size" -msgstr "" - -#: ../telemetry-data-retrieval.rst:556 -msgid "" -"Used for creating an in-memory queue and retrying to send the samples on the " -"queue on the next samples publishing period (the queue length can be " -"configured with ``max_queue_length``, where 1024 is the default value)." -msgstr "" - -#: ../telemetry-data-retrieval.rst:553 -msgid "Used for dropping the samples which are failed to be sent." -msgstr "" - -#: ../telemetry-data-retrieval.rst:550 -msgid "Used for waiting and blocking until the samples have been sent." -msgstr "" - -#: ../telemetry-measurements.rst:611 -msgid "Used physical m\\ emory size" -msgstr "" - -#: ../telemetry-alarms.rst:203 -msgid "" -"Used to restrict evaluation of the alarm to certain times of the day or days " -"of the week (expressed as ``cron`` expression with an optional timezone)." -msgstr "" - -#: ../identity_concepts.rst:89 -msgid "User" -msgstr "" - -#: ../identity_user_crud.rst:3 -msgid "User CRUD" -msgstr "" - -#: ../orchestration-auth-model.rst:88 -msgid "User creates a stack via an API request (only the token is required)." -msgstr "" - -#: ../telemetry-measurements.rst:849 -msgid "User failed to authenticate" -msgstr "" - -#: ../telemetry-measurements.rst:852 -msgid "User is created" -msgstr "" - -#: ../telemetry-measurements.rst:855 -msgid "User is deleted" -msgstr "" - -#: ../telemetry-measurements.rst:858 -msgid "User is updated" -msgstr "" - -#: ../identity_concepts.rst:92 -msgid "User management" -msgstr "" - -#: ../telemetry-measurements.rst:846 -msgid "User pending au\\ thentication" -msgstr "" - -#: ../orchestration-auth-model.rst:35 -msgid "" -"User requests a stack creation, providing a token and username/password " -"(python-heatclient or OpenStack dashboard normally requests the token for " -"you)." -msgstr "" - -#: ../telemetry-measurements.rst:843 -msgid "User successful\\ ly authenticated" -msgstr "" - -#: ../compute-admin-password-injection.rst:49 -msgid "" -"Users can only use :command:`ssh` to access the instance by using the admin " -"password if the virtual machine image is a Linux distribution, and it has " -"been configured to allow users to use :command:`ssh` as the root user. This " -"is not the case for `Ubuntu cloud images`_ which, by default, does not allow " -"users to use :command:`ssh` to access the root account." -msgstr "" - -#: ../objectstorage_features.rst:42 -msgid "" -"Users can set an expiration time or a TTL on an object to control access." -msgstr "" - -#: ../telemetry-system-architecture.rst:169 -msgid "Users, roles and tenants" -msgstr "" - -#: ../telemetry-alarms.rst:122 -msgid "Using alarms" -msgstr "" - -#: ../compute-flavors.rst:138 -msgid "" -"Using disk I/O quotas, you can set maximum disk write to 10 MB per second " -"for a VM user. For example:" -msgstr "" - -#: ../objectstorage-troubleshoot.rst:102 -msgid "" -"Using existing swift tools, there is no way to recover a builder file from " -"a :file:`ring.gz` file. However, if you have a knowledge of Python, it is " -"possible to construct a builder file that is pretty close to the one you " -"have lost." -msgstr "" - -#: ../compute-networking-nova.rst:786 -msgid "Using multinic" -msgstr "" - -#: ../identity_auth_token_middleware.rst:66 -msgid "" -"Using this option requires an admin tenant/role relationship. The admin user " -"is granted access to the admin role on the admin tenant." -msgstr "" - -#: ../telemetry-data-collection.rst:948 -msgid "" -"Using this script via cron you can get notifications periodically, for " -"example, every 5 minutes::" -msgstr "" - -#: ../objectstorage_features.rst:50 -msgid "Utilize tools that were designed for the popular S3 API." -msgstr "" - -#: ../telemetry-measurements.rst:501 -msgid "V" -msgstr "" - -#: ../compute-flavors.rst:56 -msgid "VCPUs" -msgstr "" - -#: ../compute-networking-nova.rst:115 -msgid "VLAN Network Manager" -msgstr "" - -#: ../compute-images-instances.rst:133 -msgid "VMware" -msgstr "" - -#: ../networking_adv-features.rst:549 -msgid "VMware NSX L3 extension" -msgstr "" - -#: ../networking_adv-features.rst:559 -msgid "VMware NSX L3 extension operations" -msgstr "" - -#: ../networking_adv-features.rst:457 -msgid "VMware NSX QoS extension" -msgstr "" - -#: ../networking_adv-features.rst:452 -msgid "VMware NSX extensions" -msgstr "" - -#: ../networking_arch.rst:69 -msgid "VMware NSX integration" -msgstr "" - -#: ../networking_adv-features.rst:515 -msgid "VMware NSX provider networks extension" -msgstr "" - -#: ../compute-remote-console-access.rst:137 -msgid "VNC configuration options" -msgstr "" - -#: ../compute-remote-console-access.rst:57 -msgid "VNC console proxy" -msgstr "" - -#: ../compute-remote-console-access.rst:24 -msgid "" -"VNC must be explicitly disabled to get access to the SPICE console. Set the " -"``vnc_enabled`` option to ``False`` in the ``[DEFAULT]`` section to disable " -"the VNC console." -msgstr "" - -#: ../blockstorage_glusterfs_backend.rst:54 -msgid "VOL_NAME is the Gluster volume name." -msgstr "" - -#: ../blockstorage_glusterfs_backend.rst:100 -msgid "" -"VOL_NAME is the name of an existing and accessible volume on the GlusterFS " -"server." -msgstr "" - -#: ../telemetry-measurements.rst:1133 -msgid "VPN as a Service (VPNaaS)" -msgstr "" - -#: ../telemetry-measurements.rst:1152 -msgid "VPN was created" -msgstr "" - -#: ../telemetry-measurements.rst:1156 -msgid "VPN was updated" -msgstr "" - -#: ../telemetry-system-architecture.rst:156 -msgid "VPN-as-a-Service (VPNaaS) meters" -msgstr "" - -#: ../networking_adv-features.rst:102 -msgid "" -"VXLAN is a proposed encapsulation protocol for running an overlay network on " -"existing Layer 3 infrastructure. An overlay network is a virtual network " -"that is built on top of existing network Layer 2 and Layer 3 technologies to " -"support elastic compute architectures." -msgstr "" - -#: ../compute-flavors.rst:237 -msgid "Valid ACTION values are:" -msgstr "" - -#: ../database.rst:312 -msgid "Valid values are:" -msgstr "" - -#: ../objectstorage-troubleshoot.rst:151 -msgid "" -"Validate the builder. If this raises an exception, check your previous code:" -msgstr "" - -# #-#-#-#-# compute-live-migration-usage.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -# #-#-#-#-# networking_adv-config.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -#: ../compute-live-migration-usage.rst:59 ../networking_adv-config.rst:26 -msgid "Value" -msgstr "" - -#: ../baremetal.rst:34 -msgid "Various drivers that support heterogeneous hardware" -msgstr "" - -#: ../ts-eql-volume-size.rst:51 -msgid "" -"Verify the volume size on the EQL array by using its command-line interface." -msgstr "" - -#: ../blockstorage-driver-filter-weighing.rst:229 -#: ../blockstorage-driver-filter-weighing.rst:236 -msgid "View the available properties for volume types by running::" -msgstr "" - -#: ../compute_arch.rst:275 -msgid "" -"Virtual hardware templates are called ``flavors``. The default installation " -"provides five flavors. By default, these are configurable by admin users, " -"however that behavior can be changed by redefining the access controls for " -"``compute_extension:flavormanage`` in :file:`/etc/nova/policy.json` on the " -"``compute-api`` server." -msgstr "" - -#: ../compute-images-instances.rst:381 -msgid "" -"Virtual hardware templates are called ``flavors``. The default installation " -"provides five predefined flavors." -msgstr "" - -#: ../compute-images-instances.rst:112 -msgid "" -"Virtual images that have been made available through the Image service can " -"be stored in a variety of ways. In order to use these services, you must " -"have a working installation of the Image service, with a working endpoint, " -"and users that have been created in OpenStack Identity. Additionally, you " -"must meet the environment variables required by the Compute and Image " -"service clients." -msgstr "" - -#: ../compute-flavors.rst:42 -msgid "Virtual machine memory in megabytes." -msgstr "" - -#: ../compute-flavors.rst:44 -msgid "" -"Virtual root disk size in gigabytes. This is an ephemeral di\\ sk that the " -"base image is copied into. When booting from a p\\ ersistent volume it is " -"not used. The \"0\" size is a special c\\ ase which uses the native base " -"image size as the size of the ephemeral root volume." -msgstr "" - -#: ../networking_introduction.rst:310 -msgid "Virtual-Private-Network-as-a-Service (VPNaaS)" -msgstr "" - -#: ../telemetry-measurements.rst:501 -msgid "Voltage reading from sensor" -msgstr "" - -#: ../blockstorage-consistency-groups.rst:106 -msgid "Volume deletion." -msgstr "" - -#: ../blockstorage-consistency-groups.rst:102 -msgid "Volume migration." -msgstr "" - -#: ../telemetry-measurements.rst:109 -msgid "Volume of RAM allocated to the instance" -msgstr "" - -#: ../telemetry-measurements.rst:296 -msgid "Volume of RAM u\\ sed by the inst\\ ance on the phy\\ sical machine" -msgstr "" - -#: ../telemetry-measurements.rst:290 -msgid "" -"Volume of RAM used by the inst\\ ance from the amount of its allocated memory" -msgstr "" - #: ../telemetry-measurements.rst:113 ../telemetry-measurements.rst:210 msgid "" "Volume of RAM used by the instance from the amount of its allocated memory" msgstr "" -#: ../telemetry-measurements.rst:144 ../telemetry-measurements.rst:250 -msgid "Volume of reads" +#: ../telemetry-measurements.rst:113 ../telemetry-measurements.rst:210 +#: ../telemetry-measurements.rst:290 +msgid "memory.\\ usage" msgstr "" -#: ../telemetry-data-collection.rst:457 -msgid "Volume of sample. (``--sample-volume``)" +#: ../telemetry-measurements.rst:113 +msgid "vSphere" msgstr "" -#: ../telemetry-measurements.rst:151 ../telemetry-measurements.rst:259 -msgid "Volume of writes" -msgstr "" - -#: ../blockstorage-consistency-groups.rst:104 -msgid "Volume retype." -msgstr "" - -#: ../blockstorage-consistency-groups.rst:116 -msgid "Volume snapshot deletion." -msgstr "" - -# #-#-#-#-# blockstorage_multi_backend.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -# #-#-#-#-# blockstorage_volume_number_weigher.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -#: ../blockstorage_multi_backend.rst:124 -#: ../blockstorage_volume_number_weigher.rst:51 -msgid "Volume type" -msgstr "" - -#: ../blockstorage_over_subscription.rst:74 -msgid "Volume type extra specs" -msgstr "" - -#: ../blockstorage_volume_backed_image.rst:6 -msgid "Volume-backed image" -msgstr "" - -#: ../blockstorage_volume_backed_image.rst:19 -msgid "" -"Volume-backed image feature requires locations information from the cinder " -"store of the Image service. To enable the Image service to use the cinder " -"store, add ``cinder`` to the ``stores`` option in the ``glance_store`` " -"section of the :file:`glance-api.conf` file::" -msgstr "" - -#: ../telemetry-measurements.rst:547 -msgid "Volumetric airf\\ low of the syst\\ em, expressed as 1/10th of CFM" -msgstr "" - -#: ../telemetry-measurements.rst:498 ../telemetry-measurements.rst:532 -#: ../telemetry-measurements.rst:1328 -msgid "W" -msgstr "" - -#: ../compute-flavors.rst:253 -msgid "Watchdog behavior" -msgstr "" - -#: ../compute-flavors.rst:252 -msgid "" -"Watchdog behavior set using a specific image's properties will override " -"behavior set using flavors." -msgstr "" - -#: ../telemetry-best-practices.rst:64 -msgid "" -"We recommend that you avoid open-ended queries. In order to get better " -"performance you can use reasonable time ranges and/or other query " -"constraints for retrieving measurements." -msgstr "" - -#: ../telemetry-best-practices.rst:115 -msgid "" -"We recommend that you do not run MongoDB on the same node as the controller. " -"Keep it on a separate node optimized for fast storage for better " -"performance. Also it is advisable for the MongoDB node to have a lot of " -"memory." -msgstr "" - -#: ../telemetry-best-practices.rst:110 -msgid "" -"We recommend that you do not use SQLAlchemy back end prior to the Juno " -"release, as it previously contained extraneous relationships to handle " -"deprecated data models. This resulted in extremely poor query performance." -msgstr "" - -#: ../compute-networking-nova.rst:918 -msgid "" -"We strongly recommend you remove this line to re-enable the firewall once " -"your networking issues have been resolved." -msgstr "" - -#: ../keystone_external_authentication.rst:14 -msgid "" -"Web servers, like Apache HTTP, support many methods of authentication. " -"Identity can allow the web server to perform the authentication. The web " -"server then passes the authenticated user to Identity by using the " -"``REMOTE_USER`` environment variable. This user must already exist in the " -"Identity back end to get a token from the controller. To use this method, " -"Identity should run on ``apache-httpd``." -msgstr "" - -#: ../blockstorage_multi_backend.rst:111 -msgid "" -"Weights the previously filtered back ends. By default, the `CapacityWeigher` " -"option is enabled. When this option is enabled, the filter scheduler assigns " -"the highest weight to back ends with the most available capacity." -msgstr "" - -#: ../objectstorage-monitoring.rst:14 -msgid "" -"What are different daemons are doing on each server? What is the volume of " -"object replication on node8? How long is it taking? Are there errors? If so, " -"when did they happen?" -msgstr "" - -#: ../blockstorage-driver-filter-weighing.rst:16 -msgid "What is driver filter and weigher and when to use it" -msgstr "" - -#: ../orchestration-stack-domain-users.rst:124 -msgid "" -"When API requests are processed, Orchestration does an internal lookup and " -"allows stack details for a given stack to be retrieved from the database for " -"both the stack owner's project (the default API path to the stack) and the " -"stack domain project, subject to the :file:`policy.json` restrictions." -msgstr "" - -#: ../keystone_external_authentication.rst:5 -msgid "" -"When Identity runs in ``apache-httpd``, you can use external authentication " -"methods that differ from the authentication provided by the identity store " -"back end. For example, you can use an SQL identity back end together with " -"X.509 authentication and Kerberos, instead of using the user name and " -"password combination." -msgstr "" - -#: ../compute-service-groups.rst:12 -msgid "" -"When a compute worker running the nova-compute daemon starts, it calls the " -"join API to join the compute group. Any service (such as the scheduler) can " -"query the group's membership and the status of its nodes. Internally, the " -"ServiceGroup client driver automatically updates the compute worker status." -msgstr "" - -#: ../orchestration-auth-model.rst:104 -msgid "" -"When a deferred operation is required, Orchestration retrieves the *trust " -"id* and requests a trust scoped token which enables the service user to " -"impersonate the stack owner for the duration of the deferred operation, for " -"example, to launch some OpenStack Compute instances on behalf of the stack " -"owner in response to an AutoScaling event." -msgstr "" - -#: ../objectstorage_components.rst:147 -msgid "" -"When a disk fails, replica data is automatically distributed to the other " -"zones to ensure there are three copies of the data." -msgstr "" - -#: ../telemetry-data-retrieval.rst:72 -msgid "" -"When a filter argument contains multiple constraints of the above form, a " -"logical ``AND`` relation between them is implied." -msgstr "" - -#: ../networking_adv-features.rst:313 -msgid "" -"When a port is created in Networking it is associated with a security group. " -"If a security group is not specified the port is associated with a 'default' " -"security group. By default, this group drops all ingress traffic and allows " -"all egress. Rules can be added to this group in order to change the behavior." -msgstr "" - -#: ../blockstorage_image_volume_cache.rst:13 -msgid "" -"When a volume is first created from an image, a new cached image-volume will " -"be created that is owned by the Block Storage Internal Tenant. Subsequent " -"requests to create volumes from that image will clone the cached version " -"instead of downloading the image contents and copying data to the volume." -msgstr "" - -#: ../blockstorage_get_capabilities.rst:8 -msgid "" -"When an administrator configures *volume type* and *extra specs* of storage " -"on the back end, the administrator has to read the right documentation that " -"corresponds to the version of the storage back end. Deep knowledge of " -"storage is also required." -msgstr "" - -#: ../blockstorage_get_capabilities.rst:27 -msgid "" -"When an administrator wants to define new volume types for their OpenStack " -"cloud, the administrator would fetch a list of ``capabilities`` for a " -"particular back end using the cinder client." -msgstr "" - -#: ../objectstorage_ringbuilder.rst:187 -msgid "" -"When building a new ring from an old ring, the ring builder recalculates the " -"desired number of partitions that each device wants." -msgstr "" - -#: ../blockstorage-consistency-groups.rst:184 -msgid "" -"When creating a volume and adding it to a consistency group, a volume type " -"and a consistency group id must be provided. This is because a consistency " -"group can support more than one volume type." -msgstr "" - -#: ../networking_adv-features.rst:623 -msgid "" -"When different from zero, a random delay between 0 and " -"``max_random_sync_delay`` will be added before processing the next chunk." -msgstr "" - -#: ../compute-admin-password-injection.rst:44 -msgid "" -"When enabled, Compute will modify the password of the admin account by " -"editing the :file:`/etc/shadow` file inside the virtual machine instance." -msgstr "" - -#: ../keystone_certificates_for_pki.rst:59 -msgid "" -"When generating certificates with the :command:`keystone-manage pki_setup` " -"command, the ``ca_key``, ``key_size``, and ``valid_days`` configuration " -"options are used." -msgstr "" - -#: ../blockstorage_volume_backups.rst:71 -msgid "When restoring from a full backup, it is a full restore." -msgstr "" - -#: ../blockstorage_volume_backups.rst:73 -msgid "" -"When restoring from an incremental backup, a list of backups is built based " -"on the IDs of the parent backups. A full restore is performed based on the " -"full backup first, then restore is done based on the incremental backup, " -"laying on top of it in order." -msgstr "" - -#: ../keystone_configure_with_SSL.rst:37 -msgid "" -"When running ``keystone-all``, the server can be configured to enable SSL " -"with client authentication using the following instructions. Modify the " -"``[eventlet_server_ssl]`` section in the :file:`/etc/keystone.conf` file. " -"The following SSL configuration example uses the included sample " -"certificates:" -msgstr "" - -#: ../networking_adv-features.rst:652 -msgid "" -"When running multiple OpenStack Networking server instances, the status " -"synchronization task should not run on every node; doing so sends " -"unnecessary traffic to the NSX back-end and performs unnecessary DB " -"operations. Set the ``state_sync_interval`` configuration option to a non-" -"zero value exclusively on a node designated for back-end status " -"synchronization." -msgstr "" - -#: ../keystone_configure_with_SSL.rst:72 -msgid "" -"When running the Identity service as a WSGI service in a web server such as " -"Apache httpd, this configuration is done in the web server instead. In this " -"case the options in the ``[eventlet_server_ssl]`` section are ignored." -msgstr "" - -#: ../keystone_integrate_with_ldap.rst:17 -msgid "" -"When the OpenStack Identity service is configured to use LDAP back ends, you " -"can split authentication (using the *identity* feature) and authorization " -"(using the *assignment* feature)." -msgstr "" - -#: ../telemetry-data-collection.rst:170 -msgid "" -"When the ``store_events`` option is set to True in :file:`ceilometer.conf`, " -"the notification agent needs database access in order to work properly." -msgstr "" - -#: ../compute-security.rst:31 -msgid "" -"When the attestation server challenges the compute node, the measured data " -"is sent to the attestation server." -msgstr "" - -#: ../telemetry-data-collection.rst:989 -msgid "" -"When the database dispatcher is configured as data store, you have the " -"option to set a ``time_to_live`` option (ttl) for samples. By default the " -"time to live value for samples is set to -1, which means that they are kept " -"in the database forever." -msgstr "" - -#: ../compute-images-instances.rst:87 -msgid "" -"When the instance is deleted, the state is reclaimed with the exception of " -"the persistent volume. The ephemeral storage is purged; memory and vCPU " -"resources are released. The image remains unchanged throughout this process." -msgstr "" - -#: ../objectstorage_ringbuilder.rst:205 -msgid "" -"When the ring builder reassigns a replica to a partition, the ring builder " -"records the time of the reassignment. The ring builder uses this value when " -"it gathers partitions for reassignment so that no partition is moved twice " -"in a configurable amount of time. The RingBuilder class knows this " -"configurable amount of time as ``min_part_hours``. The ring builder ignores " -"this restriction for replicas of partitions on removed devices because " -"removal of a device happens on device failure only, and reassignment is the " -"only choice." -msgstr "" - -#: ../telemetry-troubleshooting-guide.rst:32 -msgid "" -"When the services are started for the first time or in line with the message " -"queue service restart, it takes time while the **ceilometer-collector** " -"service establishes the connection and joins or rejoins to the configured " -"exchanges. Therefore, if the **ceilometer-agent-compute**, **ceilometer-" -"agent-central**, and the **ceilometer-agent-notification** services are " -"started before the **ceilometer-collector** service, the **ceilometer-" -"collector** service may lose some messages while connecting to the message " -"queue service." -msgstr "" - -#: ../networking_adv-features.rst:648 -msgid "" -"When this option is enabled, the operational status will always be retrieved " -"from the NSX back-end ad every ``GET`` request. In this case it is advisable " -"to disable the synchronization task." -msgstr "" - -#: ../telemetry-data-retrieval.rst:572 -msgid "" -"When this option is greater than zero, it will cause a rollover. When the " -"size is about to be exceeded, the file is closed and a new file is silently " -"opened for output. If its value is zero, rollover never occurs." -msgstr "" - -#: ../keystone_certificates_for_pki.rst:113 -msgid "" -"When using a signing certificate issued by an external CA, you do not need " -"to specify ``key_size``, ``valid_days``, and ``ca_password`` as they will be " -"ignored." -msgstr "" - -#: ../compute-live-migration-usage.rst:219 -msgid "" -"When using live migration to move workloads between Icehouse and Juno " -"compute nodes, it may cause data loss because libvirt live migration with " -"shared block storage was buggy (potential loss of data) before version 3.32. " -"This issue can be solved when we upgrade to RPC API version 4.0." -msgstr "" - -#: ../telemetry-troubleshooting-guide.rst:73 -msgid "" -"When using the Telemetry command line client, the credentials and the " -"``os_auth_url`` have to be set in order for the client to authenticate " -"against OpenStack Identity. For further details about the credentials that " -"have to be provided see the `Telemetry Python API `__." -msgstr "" - -#: ../compute-admin-password-injection.rst:57 -msgid "" -"When using the XenAPI hypervisor back end, Compute uses the XenAPI agent to " -"inject passwords into guests. The virtual machine image must be configured " -"with the agent for password injection to work." -msgstr "" - -#: ../networking_adv-features.rst:341 -msgid "" -"When using the security group API through Compute, security groups are " -"applied to all ports on an instance. The reason for this is that Compute " -"security group APIs are instances based and not port based as Networking." -msgstr "" - -#: ../compute-node-down.rst:278 -msgid "" -"When you are planning for and performing a disaster recovery, follow these " -"tips:" -msgstr "" - -#: ../ts_no_emulator_x86_64.rst:8 -msgid "" -"When you attempt to create a VM, the error shows the VM is in the ``BUILD`` " -"then ``ERROR`` state." -msgstr "" - -#: ../networking_use.rst:224 -msgid "" -"When you boot a Compute VM, a port on the network that corresponds to the VM " -"NIC is automatically created and associated with the default security group. " -"You can configure `security group rules <#enabling_ping_and_ssh>`__ to " -"enable users to access the VM." -msgstr "" - -#: ../blockstorage_multi_backend.rst:10 -msgid "" -"When you configure multiple-storage back ends, you can create several back-" -"end storage solutions that serve the same OpenStack Compute configuration " -"and one ``cinder-volume`` is launched for each back-end storage or back-end " -"storage pool." -msgstr "" - -#: ../networking_config-identity.rst:134 -msgid "" -"When you configure networking, you must use this guide. Do not rely on " -"Compute networking documentation or past experience with Compute. If a :" -"command:`nova` command or configuration option related to networking is not " -"mentioned in this guide, the command is probably not supported for use with " -"Networking. In particular, you cannot use CLI tools like ``nova-manage`` and " -"``nova`` to manage networks or IP addressing, including both fixed and " -"floating IPs, with Networking." -msgstr "" - -#: ../keystone_integrate_assignment_backend_ldap.rst:7 -msgid "" -"When you configure the OpenStack Identity service to use LDAP servers, you " -"can split authentication and authorization using the *assignment* feature. " -"Integrating the *assignment* back end with LDAP allows administrators to use " -"projects (tenant), roles, domains, and role assignments in LDAP." -msgstr "" - -#: ../networking_multi-dhcp-agents.rst:318 -msgid "" -"When you create a network with one port, you can schedule it to an active " -"DHCP agent. If many active DHCP agents are running, select one randomly. You " -"can design more sophisticated scheduling algorithms in the same way as nova-" -"schedule later on." -msgstr "" - -#: ../blockstorage_ratelimit_volume_copy_bandwidth.rst:10 -msgid "" -"When you create a new volume from an image or an existing volume, or when " -"you upload a volume image to the Image service, large data copy may stress " -"disk and network bandwidth. To mitigate slow down of data access from the " -"instances, OpenStack Block Storage supports rate-limiting of volume data " -"copy bandwidth." -msgstr "" - -#: ../blockstorage_multi_backend.rst:166 -msgid "" -"When you create a volume, you must specify the volume type. The extra-" -"specifications of the volume type are used to determine which back end has " -"to be used." -msgstr "" - -#: ../compute-manage-logs.rst:177 -msgid "" -"When you enable read-write serial console access, Compute will add serial " -"console information to the Libvirt XML file for the instance. For example:" -msgstr "" - -#: ../compute-manage-logs.rst:235 -msgid "" -"When you enable the serial console, typical instance logging using the :" -"command:`nova console-log` command is disabled. Kernel output and other " -"system messages will not be visible unless you are actively viewing the " -"serial console." -msgstr "" - -# #-#-#-#-# keystone_integrate_identity_backend_ldap.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -# #-#-#-#-# keystone_integrate_with_ldap.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -#: ../keystone_integrate_identity_backend_ldap.rst:245 -#: ../keystone_integrate_with_ldap.rst:159 -msgid "" -"When you have finished configuration, restart the OpenStack Identity " -"service::" -msgstr "" - -#: ../compute-images-instances.rst:17 -msgid "" -"When you launch an instance, you must choose a ``flavor``, which represents " -"a set of virtual resources. Flavors define how many virtual CPUs an instance " -"has, the amount of RAM available to it, and the size of its ephemeral disks. " -"Users must select from the set of available flavors defined on their cloud. " -"OpenStack provides a number of predefined flavors that you can edit or add " -"to." -msgstr "" - -#: ../database.rst:224 -msgid "" -"When you set up a configuration group using the trove :command:" -"`configuration-create` command, this command compares the configuration " -"values you are setting against a list of valid configuration values that are " -"stored in the :file:`validation-rules.json` file." -msgstr "" - -#: ../networking_config-plugins.rst:150 -msgid "" -"When you specify multiple API endpoints, the plug-in takes care of load " -"balancing requests on the various API endpoints." -msgstr "" - -#: ../ts-eql-volume-size.rst:104 -msgid "" -"When you uploaded the volume in the previous step, the Image service " -"reported the volume's size as ``1`` (GB). However, when using ``glance image-" -"list`` to list the image, the displayed size is 1085276160 bytes, or roughly " -"1.01 GB:" -msgstr "" - -#: ../compute-networking-nova.rst:289 -msgid "" -"When you use ``FlatDHCPManager``, the command uses the original ``--" -"fixed_range_v6`` value. For example:" -msgstr "" - -#: ../compute-networking-nova.rst:297 -msgid "" -"When you use ``VlanManager``, the command increments the subnet ID to create " -"subnet prefixes. Guest VMs use this prefix to generate their IPv6 global " -"unicast address. For example:" -msgstr "" - -#: ../blockstorage_volume_backups_export_import.rst:26 -msgid "" -"Where *BACKUP_ID* is the volume backup's ID. This command should return the " -"backup's corresponding database information as encoded string metadata." -msgstr "" - -#: ../blockstorage_volume_backups_export_import.rst:54 -msgid "Where *METADATA* is the backup metadata exported earlier." -msgstr "" - -#: ../blockstorage_volume_backups.rst:19 -msgid "" -"Where *VOLUME* is the name or ID of the volume, ``incremental`` is a flag " -"that indicates whether an incremental backup should be performed, and " -"``force`` is a flag that allows or disallows backup of a volume when the " -"volume is attached to an instance." -msgstr "" - -#: ../blockstorage_over_subscription.rst:60 -msgid "" -"Where ``PROVISIONED_CAPACITY`` is the apparent allocated space indicating " -"how much capacity has been provisioned and ``MAX_RATIO`` is the maximum " -"oversubscription ratio. For the LVM driver, it is " -"``max_over_subscription_ratio`` in :file:`cinder.conf`." -msgstr "" - -# #-#-#-#-# blockstorage_glusterfs_backend.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -# #-#-#-#-# blockstorage_nfs_backend.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -# #-#-#-#-# compute-flavors.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -# #-#-#-#-# identity_service_api_protection.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -# #-#-#-#-# keystone_secure_identity_to_ldap_backend.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -#: ../blockstorage_glusterfs_backend.rst:52 -#: ../blockstorage_glusterfs_backend.rst:96 ../blockstorage_nfs_backend.rst:41 -#: ../compute-flavors.rst:266 ../compute-flavors.rst:287 -#: ../identity_service_api_protection.rst:19 -#: ../keystone_secure_identity_to_ldap_backend.rst:62 -msgid "Where:" -msgstr "" - -#: ../networking_introduction.rst:157 -msgid "" -"Whereas security groups operate at the instance-level, FWaaS operates at the " -"perimeter to filter traffic at the neutron router." -msgstr "" - -#: ../telemetry-best-practices.rst:75 -msgid "" -"Whereas, this well-formed query returns a more reasonable amount of data, " -"hence better performance:" -msgstr "" - -#: ../orchestration-auth-model.rst:76 -msgid "Whether to enable impersonation." -msgstr "" - -#: ../database.rst:162 -msgid "" -"Which datastore manager to use for this version. Typically, the datastore " -"manager is identified by one of the following strings, depending on the " -"database:" -msgstr "" - -#: ../telemetry-events.rst:9 -msgid "" -"While a sample represents a single, numeric datapoint within a time-series, " -"an event is a broader concept that represents the state of a resource at a " -"point in time. The state may be described using various data types including " -"non-numeric data such as an instance's flavor. In general, events represent " -"any action made in the OpenStack system." -msgstr "" - -#: ../blockstorage_volume_migration.rst:30 -msgid "" -"While most back-ends support this function, not all do. See the driver " -"documentation in the `OpenStack Configuration Reference `__ for more details." -msgstr "" - -#: ../telemetry-data-collection.rst:423 -msgid "" -"While most parts of the data collection in the Telemetry module are " -"automated, Telemetry provides the possibility to submit samples via the REST " -"API to allow users to send custom samples into this module." -msgstr "" - -#: ../blockstorage_ratelimit_volume_copy_bandwidth.rst:25 -msgid "" -"While multiple volume data copy operations are running in the same back end, " -"the specified bandwidth is divided to each copy." -msgstr "" - -#: ../ts_cinder_config.rst:124 -msgid "" -"While the installer should handle all this, it can go wrong. If you have " -"trouble creating volumes and this directory does not exist you should see an " -"error message in the ``cinder-volume`` log indicating that the " -"``volumes_dir`` does not exist, and it should provide information about " -"which path it was looking for." -msgstr "" - -#: ../blockstorage_backup_disks.rst:5 -msgid "" -"While you can use the LVM snapshot to create snapshots, you can also use it " -"to back up your volumes. By using LVM snapshot, you reduce the size of the " -"backup; only existing data is backed up instead of the entire volume." -msgstr "" - -#: ../compute-networking-nova.rst:989 -msgid "" -"With KVM hypervisors, instances running Ubuntu 12.04 sometimes lose network " -"connectivity after functioning properly for a period of time. Try loading " -"the ``vhost_net`` kernel module as a workaround for this issue (see `bug " -"#997978 `__) . This kernel module may also `improve network performance `__ on KVM. To load the kernel module:" -msgstr "" - -#: ../telemetry-data-collection.rst:711 -msgid "With ``map_from`` and ``map_to`` ::" -msgstr "" - -#: ../objectstorage_ringbuilder.rst:70 -msgid "" -"With an overload factor of 0.1, each device accepts 10% more partitions than " -"it otherwise would, but only if it needs to maintain partition dispersion." -msgstr "" - -#: ../blockstorage_get_capabilities.rst:41 -msgid "" -"With one of the listed hosts, pass that to ``get-capabilities``, then the " -"administrator can obtain volume stats and also back end ``capabilities`` as " -"listed below." -msgstr "" - -#: ../objectstorage_tenant_specific_image_storage.rst:30 -msgid "" -"With this configuration, images are stored in an Object Storage service " -"(swift) endpoint that is pulled from the service catalog for the " -"authenticated user." -msgstr "" - -#: ../telemetry-data-collection.rst:353 -msgid "" -"Without the ``backend_url`` option being set only one instance of both the " -"central and compute agent service is able to run and function correctly." -msgstr "" - -#: ../blockstorage_volume_backups.rst:27 -msgid "" -"Without the ``force`` flag, the volume will be backed up only if its status " -"is ``available``. With the ``force`` flag, the volume will be backed up " -"whether its status is ``available`` or ``in-use``. A volume is ``in-use`` " -"when it is attached to an instance. The backup of an ``in-use`` volume means " -"your data is crash consistent. The ``force`` flag is False by default." -msgstr "" - -#: ../blockstorage_volume_backups.rst:24 -msgid "" -"Without the ``incremental`` flag, a full backup is created by default. With " -"the ``incremental`` flag, an incremental backup is created." -msgstr "" - -#: ../objectstorage_ringbuilder.rst:78 -msgid "" -"Without the overload, some partitions would end up with replicas only on " -"nodes A and B. However, with the overload, every device can accept up to 10% " -"more partitions for the sake of dispersion. The missing disk in C means " -"there is one disk's worth of partitions to spread across the remaining 11 " -"disks, which gives each disk in C an extra 9.09% load. Since this is less " -"than the 10% overload, there is one replica of each partition on each node." -msgstr "" - -#: ../telemetry-alarms.rst:106 -msgid "Workload partitioning" -msgstr "" - -#: ../compute-configuring-migrations.rst:323 -msgid "XenServer" -msgstr "" - -# #-#-#-#-# networking_adv-features.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -# #-#-#-#-# telemetry-data-collection.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -#: ../networking_adv-features.rst:695 ../networking_adv-features.rst:700 -#: ../networking_adv-features.rst:705 ../telemetry-data-collection.rst:1011 -#: ../telemetry-data-collection.rst:1015 -msgid "Yes" -msgstr "" - -#: ../compute-images-instances.rst:39 -msgid "" -"You can add and remove additional resources from running instances, such as " -"persistent volume storage, or public IP addresses. The example used in this " -"chapter is of a typical virtual system within an OpenStack cloud. It uses " -"the ``cinder-volume`` service, which provides persistent block storage, " -"instead of the ephemeral storage provided by the selected instance flavor." -msgstr "" - -#: ../compute-networking-nova.rst:674 -msgid "You can also apply the changes by restarting the network service:" -msgstr "" - -#: ../identity_auth_token_middleware.rst:4 -msgid "" -"You can also configure Identity authentication middleware using the :code:" -"`admin_user` and :code:`admin_password` options." -msgstr "" - -#: ../blockstorage_volume_migration.rst:65 -msgid "You can also get available back-ends like following:" -msgstr "" - -#: ../compute_arch.rst:51 -msgid "" -"You can also orchestrate clouds using multiple hypervisors in different " -"availability zones. Compute supports the following hypervisors:" -msgstr "" - -#: ../compute-images-instances.rst:343 -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 " -"system that accumulates states that are preserved across restarts. To get a " -"list of available images on your system, run:" -msgstr "" - -#: ../keystone_secure_identity_to_ldap_backend.rst:27 -msgid "" -"You can also set the ``tls_cacertdir`` (also in the ``ldap`` section) to the " -"directory where all certificate authorities files are kept. If both " -"``tls_cacertfile`` and ``tls_cacertdir`` are set, then the latter will be " -"ignored." -msgstr "" - -#: ../blockstorage_backup_disks.rst:42 -msgid "You can apply this process to volumes of any size." -msgstr "" - -#: ../database.rst:116 -msgid "" -"You can attach multiple versions/images to a datastore. For example, you " -"might have a MySQL 5.5 version and a MySQL 5.6 version. You can designate " -"one version as the default, which the system uses if a user does not " -"explicitly request a specific version." -msgstr "" - -#: ../keystone_configure_with_SSL.rst:30 -msgid "" -"You can choose names for these certificates. You can also combine public/" -"private keys in the same file, if you wish. These certificates are provided " -"as an example." -msgstr "" - -#: ../compute-networking-nova.rst:8 -msgid "" -"You can choose to either install and configure nova-network or use the " -"OpenStack Networking service (neutron). This section contains a brief " -"overview of nova-network. For more information about OpenStack Networking, " -"see :ref:`networking`." -msgstr "" - -#: ../blockstorage-driver-filter-weighing.rst:44 -msgid "" -"You can choose to use the ``DriverFilter`` without the ``GoodnessWeigher`` " -"or vice-versa. The filter and weigher working together, however, create the " -"most benefits when helping the scheduler choose an ideal back end." -msgstr "" - -#: ../compute-networking-nova.rst:729 -msgid "" -"You can configure ``nova-network`` to automatically allocate and assign a " -"floating IP address to virtual instances when they are launched. Add this " -"line to the :file:`/etc/nova/nova.conf` file:" -msgstr "" - -#: ../compute_arch.rst:174 -msgid "" -"You can configure a persistent volume as bootable and use it to provide a " -"persistent virtual instance similar to the traditional non-cloud-based " -"virtualization system. It is still possible for the resulting instance to " -"keep ephemeral storage, depending on the flavor selected. In this case, the " -"root file system can be on the persistent volume, and its state is " -"maintained, even if the instance is shut down. For more information about " -"this type of configuration, see the `OpenStack Configuration Reference " -"`__." -msgstr "" - -#: ../compute-flavors.rst:82 -msgid "" -"You can configure the CPU limits with control parameters with the ``nova`` " -"client. For example, to configure the I/O limit, use:" -msgstr "" - -#: ../keystone_configure_with_SSL.rst:5 -msgid "You can configure the Identity service to support two-way SSL." -msgstr "" - -#: ../objectstorage_account_reaper.rst:48 -msgid "" -"You can control when this is logged with the ``reap_warn_after`` value in " -"the ``[account-reaper]`` section of the :file:`account-server.conf` file. " -"The default value is 30 days." -msgstr "" - -#: ../networking_introduction.rst:242 -msgid "" -"You can create a firewall policy without any rules and add rules later, as " -"follows:" -msgstr "" - -#: ../blockstorage-driver-filter-weighing.rst:71 -msgid "" -"You can define your own filter and goodness functions through the use of " -"various properties that OpenStack Block Storage has exposed. Properties " -"exposed include information about the volume request being made, ``volume" -"\\_type`` settings, and back-end specific information about drivers. All of " -"these allow for a lot of control over how the ideal back end for a volume " -"request will be decided." -msgstr "" - -#: ../blockstorage_backup_disks.rst:154 -msgid "" -"You can directly access the data inside the instance. If a message prompts " -"you for a partition or you cannot mount it, determine whether enough space " -"was allocated for the snapshot or the :command:`kpartx` command failed to " -"discover the partition table." -msgstr "" - -#: ../telemetry-alarms.rst:226 -msgid "" -"You can display all your alarms via (some attributes are omitted for " -"brevity):" -msgstr "" - -#: ../telemetry-data-collection.rst:893 -msgid "" -"You can even use complex operations on json paths. In the following example, " -"``volume`` and ``resource_id`` fields perform an arithmetic and string " -"concatenation::" -msgstr "" - -#: ../objectstorage_ringbuilder.rst:116 -msgid "" -"You can gradually increase the replica count at a rate that does not " -"adversely affect cluster performance." -msgstr "" - -#: ../telemetry-best-practices.rst:89 -msgid "" -"You can install the API behind ``mod_wsgi``, as it provides more settings to " -"tweak, like ``threads`` and ``processes`` in case of ``WSGIDaemon``." -msgstr "" - -#: ../objectstorage-troubleshoot.rst:25 -msgid "" -"You can look at error messages in :file:`/var/log/kern.log` for hints of " -"drive failure." -msgstr "" - -#: ../networking_use.rst:5 -msgid "" -"You can manage OpenStack Networking services by using the service command. " -"For example:" -msgstr "" - -#: ../compute-configuring-migrations.rst:272 -msgid "" -"You can now configure other options for live migration. In most cases, you " -"will not need to configure any options. For advanced configuration options, " -"see the `OpenStack Configuration Reference Guide `_." -msgstr "" - -# #-#-#-#-# blockstorage_glusterfs_backend.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -# #-#-#-#-# blockstorage_nfs_backend.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -#: ../blockstorage_glusterfs_backend.rst:158 -#: ../blockstorage_nfs_backend.rst:113 -msgid "You can now restart the service to apply the configuration." -msgstr "" - -#: ../compute-security.rst:132 -msgid "" -"You can request that your instance is run on a trusted host by specifying a " -"trusted flavor when booting the instance:" -msgstr "" - -#: ../telemetry.rst:42 -msgid "" -"You can retrieve the collected samples in three different ways: with the " -"REST API, with the command line interface, or with the Metering tab on an " -"OpenStack dashboard." -msgstr "" - -#: ../networking_adv-config.rst:13 -msgid "" -"You can run an L3 metering agent that enables layer-3 traffic metering. In " -"general, you should launch the metering agent on all nodes that run the L3 " -"agent:" -msgstr "" - -#: ../networking_multi-dhcp-agents.rst:378 -msgid "" -"You can see that only the DHCP agent for HostB is hosting the ``net2`` " -"network." -msgstr "" - -#: ../blockstorage_backup_disks.rst:138 -msgid "" -"You can see the ``cinder--volumes-volume--00000001--snapshot1`` partition." -msgstr "" - -#: ../telemetry-data-collection.rst:1039 -msgid "" -"You can store samples in a file by setting the ``dispatcher`` option in the :" -"file:`ceilometer.conf` file. For the list of configuration options, see the " -"`dispatcher_file section `__ in the OpenStack " -"Configuration Reference." -msgstr "" - -#: ../ts-eql-volume-size.rst:171 -msgid "You can then check this new volume into the EQL array::" -msgstr "" - -#: ../keystone_certificates_for_pki.rst:104 -msgid "" -"You can use a signing certificate issued by an external CA instead of " -"generated by ``keystone-manage``. However, a certificate issued by an " -"external CA must satisfy the following conditions:" -msgstr "" - -#: ../dashboard_sessions.rst:40 -msgid "" -"You can use applications such as Memcached or Redis for external caching. " -"These applications offer persistence and shared storage and are useful for " -"small-scale deployments and development." -msgstr "" - -#: ../blockstorage_volume_migration.rst:153 -msgid "" -"You can use the :command:`cinder show` command to see the status of the " -"migration. While migrating, the ``migstat`` attribute shows states such as " -"``migrating`` or ``completing``. On error, ``migstat`` is set to None and " -"the host attribute shows the original ``host``. On success, in this example, " -"the output looks like:" -msgstr "" - -#: ../compute-networking-nova.rst:273 -msgid "" -"You can use the following options with the :command:`nova network-create` " -"command:" -msgstr "" - -#: ../objectstorage_components.rst:81 -msgid "" -"You can use weights to balance the distribution of partitions on drives " -"across the cluster. This can be useful, for example, when differently sized " -"drives are used in a cluster." -msgstr "" - -#: ../blockstorage_volume_backups.rst:78 -msgid "" -"You can view a backup list with the :command:`cinder backup-list` command. " -"Optional arguments to clarify the status of your backups include: running " -"``--name``, ``--status``, and ``--volume-id`` to filter through backups by " -"the specified name, status, or volume-id. Search with ``--all-tenants`` for " -"details of the tenants associated with the listed backups." -msgstr "" - -#: ../blockstorage_volume_backups_export_import.rst:20 -msgid "" -"You can, however, export the metadata of a volume backup. To do so, run this " -"command as an OpenStack ``admin`` user (presumably, after creating a volume " -"backup)::" -msgstr "" - -#: ../compute-networking-nova.rst:747 -msgid "" -"You cannot delete a network that has been associated to a project. This " -"section describes the procedure for dissociating it so that it can be " -"deleted." -msgstr "" - -#: ../compute-networking-nova.rst:886 -msgid "" -"You cannot use ``SSH`` to access an instance with a public IP from within " -"the same server because the routing configuration does not allow it." -msgstr "" - -#: ../identity_logging.rst:5 -msgid "" -"You configure logging externally to the rest of Identity. The name of the " -"file specifying the logging configuration is set using the ``log_config`` " -"option in the ``[DEFAULT]`` section of the :file:`keystone.conf` file. To " -"route logging through syslog, set ``use_syslog=true`` in the ``[DEFAULT]`` " -"section." -msgstr "" - -#: ../keystone_token-binding.rst:12 -msgid "" -"You configure the authentication types for a token binding in the :file:" -"`keystone.conf` file:" -msgstr "" - -#: ../telemetry-measurements.rst:20 -msgid "" -"You may need to configure Telemetry or other OpenStack services in order to " -"be able to collect all the samples you need. For further information about " -"configuration requirements see the `Telemetry chapter `__ in the " -"OpenStack Installation Guide. Also check the `Telemetry manual installation " -"`__ " -"description." -msgstr "" - -#: ../ts-failed-attach-vol-after-detach.rst:34 -msgid "" -"You might also have this problem after attaching and detaching the same " -"volume from the same VM with the same mount point multiple times. In this " -"case, restart the KVM host." -msgstr "" - -#: ../telemetry-measurements.rst:62 -msgid "" -"You might also specify headers whose values will be stored along with the " -"sample data of OpenStack Object Storage. The additional information is also " -"stored under ``resource_metadata``. The format of the new field is " -"``resource_metadata.http_header_$name``, where ``$name`` is the name of the " -"header with ``-`` replaced by ``_``." -msgstr "" - -#: ../ts_cinder_config.rst:162 -msgid "" -"You might see this error in :file:`cinder-volume.log` after trying to create " -"a volume that is 1 GB. To fix this issue:" -msgstr "" - -#: ../blockstorage_backup_disks.rst:17 -msgid "" -"You must also make sure that the operating system is not using the volume, " -"and that all data has been flushed on the guest file systems. This usually " -"means that those file systems have to be unmounted during the snapshot " -"creation. They can be mounted again as soon as the logical volume snapshot " -"has been created." -msgstr "" - -#: ../ts-failed-attach-vol-after-detach.rst:16 -msgid "" -"You must change the device name on the ``nova-attach`` command. The VM might " -"not clean up after a ``nova-detach`` command runs. This example shows how " -"the ``nova-attach`` command fails when you use the ``vdb``, ``vdc``, or " -"``vdd`` device names::" -msgstr "" - -#: ../orchestration-stack-domain-users.rst:58 -msgid "You must complete the following steps to setup stack domain users:" -msgstr "" - -#: ../networking_adv-config.rst:22 -msgid "" -"You must configure a driver that matches the plug-in that runs on the " -"service. The driver adds metering to the routing interface." -msgstr "" - -#: ../telemetry-data-collection.rst:342 -msgid "" -"You must configure a supported Tooz driver for the HA deployment of the " -"Telemetry services." -msgstr "" - -#: ../networking_adv-config.rst:61 -msgid "" -"You must configure any driver that implements the metering abstraction. " -"Currently the only available implementation uses iptables for metering." -msgstr "" - -#: ../networking_use.rst:296 -msgid "" -"You must configure security group rules depending on the type of plug-in you " -"are using. If you are using a plug-in that:" -msgstr "" - -#: ../networking_adv-features.rst:335 -msgid "" -"You must configure the correct firewall driver in the ``securitygroup`` " -"section of the plug-in/agent configuration file. Some plug-ins and agents, " -"such as Linux Bridge Agent and Open vSwitch Agent, use the no-operation " -"driver as the default, which results in non-working security groups." -msgstr "" - -#: ../networking_config-agents.rst:64 -msgid "" -"You must configure the host running the neutron-dhcp-agent as a data " -"forwarding node according to the requirements for your plug-in." -msgstr "" - -#: ../blockstorage_multi_backend.rst:105 -msgid "" -"You must enable the `filter_scheduler` option to use multiple-storage back " -"ends. The filter scheduler:" -msgstr "" - -#: ../compute-remote-console-access.rst:212 -msgid "" -"You must install the noVNC package, which contains the ``nova-novncproxy`` " -"service. As root, run the following command:" -msgstr "" - -#: ../keystone_configure_with_SSL.rst:7 -msgid "You must obtain the x509 certificates externally and configure them." -msgstr "" - -#: ../networking_config-identity.rst:86 -msgid "" -"You must provide admin user credentials that Compute and some internal " -"Networking components can use to access the Networking API. Create a special " -"``service`` tenant and a ``neutron`` user within this tenant, and assign an " -"``admin`` role to this role." -msgstr "" - -#: ../objectstorage_ringbuilder.rst:110 -msgid "" -"You must rebalance the replica ring in globally distributed clusters. " -"Operators of these clusters generally want an equal number of replicas and " -"regions. Therefore, when an operator adds or removes a region, the operator " -"adds or removes a replica. Removing unneeded replicas saves on the cost of " -"disks." -msgstr "" - -#: ../compute-configuring-migrations.rst:97 -msgid "" -"You must specify ``vncserver_listen=0.0.0.0`` or live migration will not " -"work correctly." -msgstr "" - -#: ../compute-configuring-migrations.rst:100 -msgid "" -"You must specify the ``instances_path`` in each node that runs nova-compute. " -"The mount point for ``instances_path`` must be the same value for each node, " -"or live migration will not work correctly." -msgstr "" - -#: ../telemetry-measurements.rst:512 -msgid "" -"You need to deploy the ceilometer-agent-ipmi on each IPMI-capable node in " -"order to poll local sensor data. For further information about the IPMI " -"agent see :ref:`telemetry-ipmi-agent`." -msgstr "" - -#: ../compute-networking-nova.rst:537 -msgid "" -"You need to enable ``ping`` and ``ssh`` on your VMs for network access. This " -"can be done with either the :command:`nova` or :command:`euca2ools` commands." -msgstr "" - -#: ../database.rst:67 -msgid "You need to register your guest image with the Image service." -msgstr "" - -#: ../keystone_caching_layer.rst:134 -msgid "" -"You need to specify the URL to reach the ``memcached`` instance with the " -"``backend_argument`` parameter." -msgstr "" - -#: ../ts-HTTP-bad-req-in-cinder-vol-log.rst:46 -msgid "" -"You need to update your copy of the :file:`hp_3par_fc.py` driver which " -"contains the synchronization code." -msgstr "" - -#: ../identity_service_api_protection.rst:63 -msgid "" -"You reference attributes of objects passed with an object.attribute syntax " -"(such as, ``user.domain_id``). The target objects of an API are also " -"available using a target.object.attribute syntax. For instance:" -msgstr "" - -#: ../blockstorage_backup_disks.rst:174 -msgid "" -"You should always have the checksum for your backup files. When you transfer " -"the same file over the network, you can run a checksum calculation to ensure " -"that your file was not corrupted during its transfer. The checksum is a " -"unique ID for a file. If the checksums are different, the file is corrupted." -msgstr "" - -#: ../objectstorage-troubleshoot.rst:98 -msgid "" -"You should always keep a backup of swift ring builder files. However, if an " -"emergency occurs, this procedure may assist in returning your cluster to an " -"operational state." -msgstr "" - -#: ../objectstorage_arch.rst:79 -msgid "" -"You should keep in mind the desired I/O performance for single-threaded " -"requests . This system does not use RAID, so a single disk handles each " -"request for an object. Disk performance impacts single-threaded response " -"rates." -msgstr "" - -#: ../objectstorage-troubleshoot.rst:167 -msgid "" -"You should now have a file called :file:`account.builder` in the current " -"working directory. Run :command:`swift-ring-builder account.builder " -"write_ring` and compare the new :file:`account.ring.gz` to the :file:" -"`account.ring.gz` that you started from. They probably are not byte-for-byte " -"identical, but if you load them in a REPL and their ``_replica2part2dev_id`` " -"and ``devs`` attributes are the same (or nearly so), then you are in good " -"shape." -msgstr "" - -#: ../telemetry-data-collection.rst:907 -msgid "" -"You will find some existence meters in the :file:`meter.yaml`. These meters " -"have a ``volume`` as ``1`` and are at the bottom of the yaml file with a " -"note suggesting that these will be removed in Mitaka release." -msgstr "" - -#: ../compute-remote-console-access.rst:289 -msgid "" -"Your :file:`nova-compute` configuration file must set the following values:" -msgstr "" - -#: ../identity_troubleshoot.rst:110 -msgid "" -"Your service is configured incorrectly and cannot talk to Identity. Check " -"the ``auth_port`` and ``auth_host`` values and make sure that you can talk " -"to that service through cURL, as shown previously." -msgstr "" - -#: ../identity_troubleshoot.rst:114 -msgid "" -"Your signing directory is not writable. Use the ``chmod`` command to change " -"its permissions so that the service (POSIX) user can write to it. Verify the " -"change through ``su`` and ``touch`` commands." -msgstr "" - -#: ../compute-live-migration-usage.rst:108 -msgid "Zone" -msgstr "" - -#: ../objectstorage_components.rst:119 -msgid "Zones" -msgstr "" - -#: ../compute-service-groups.rst:44 -msgid "ZooKeeper ServiceGroup driver" -msgstr "" - -#: ../compute-networking-nova.rst:311 ../compute-networking-nova.rst:509 -msgid "[DEFAULT]" -msgstr "" - -#: ../compute-root-wrap-reference.rst:58 -msgid "[DEFAULT] filters\\_path=/etc/nova/rootwrap.d,/usr/share/nova/rootwrap" -msgstr "" - -#: ../compute-root-wrap-reference.rst:97 -msgid "[Filters] filter\\_name=kpartx: CommandFilter, /sbin/kpartx, root" -msgstr "" - -#: ../compute-security.rst:105 -msgid "[trusted_computing]" -msgstr "" - -#: ../compute_arch.rst:54 -msgid "`Baremetal `__" -msgstr "" - -#: ../cross_project_cors.rst:27 -msgid "" -"`CORS in Object Storage `_" -msgstr "" - -#: ../cross_project_cors.rst:28 -msgid "" -"`CORS in dashboard `_" -msgstr "" - -#: ../telemetry-system-architecture.rst:95 -msgid "`DB2(deprecated) `__" -msgstr "" - -#: ../compute_arch.rst:56 -msgid "`Docker `__" -msgstr "" - -#: ../telemetry-system-architecture.rst:85 -msgid "`ElasticSearch (events only) `__" -msgstr "" - -#: ../telemetry-system-architecture.rst:93 -msgid "`HBase `__" -msgstr "" - -# #-#-#-#-# compute_arch.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -# #-#-#-#-# telemetry-system-architecture.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -#: ../compute_arch.rst:58 ../telemetry-system-architecture.rst:133 -msgid "" -"`Hyper-V `__" -msgstr "" - -# #-#-#-#-# compute_arch.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -# #-#-#-#-# telemetry-system-architecture.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -#: ../compute_arch.rst:60 ../telemetry-system-architecture.rst:118 -msgid "" -"`Kernel-based Virtual Machine (KVM) `__" -msgstr "" - -# #-#-#-#-# compute_arch.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -# #-#-#-#-# telemetry-system-architecture.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -#: ../compute_arch.rst:63 ../telemetry-system-architecture.rst:123 -msgid "`Linux Containers (LXC) `__" -msgstr "" - -#: ../telemetry-data-collection.rst:340 -msgid "`Memcached `__. Recommended for testing." -msgstr "" - -#: ../telemetry-system-architecture.rst:87 -msgid "`MongoDB `__" -msgstr "" - -#: ../telemetry-system-architecture.rst:89 -msgid "`MySQL `__" -msgstr "" - -#: ../telemetry-system-architecture.rst:162 -msgid "`OpenContrail `__" -msgstr "" - -#: ../telemetry-system-architecture.rst:160 -msgid "`OpenDaylight `__" -msgstr "" - -#: ../telemetry-system-architecture.rst:91 -msgid "`PostgreSQL `__" -msgstr "" - -#: ../telemetry-system-architecture.rst:121 -msgid "`Quick Emulator (QEMU) `__" -msgstr "" - -#: ../compute_arch.rst:65 -msgid "`Quick Emulator (QEMU) `__" -msgstr "" - -#: ../telemetry-data-collection.rst:337 -msgid "`Redis `__. Recommended solution by the Tooz project." -msgstr "" - -#: ../compute_arch.rst:67 -msgid "`User Mode Linux (UML) `__" -msgstr "" - -#: ../telemetry-system-architecture.rst:125 -msgid "`User-mode Linux (UML) `__" -msgstr "" - -#: ../telemetry-system-architecture.rst:137 -msgid "" -"`VMWare vSphere `__" -msgstr "" - -#: ../compute_arch.rst:69 -msgid "" -"`VMware vSphere `__" -msgstr "" - -#: ../telemetry-system-architecture.rst:135 -msgid "`XEN `__" -msgstr "" - -#: ../compute_arch.rst:72 -msgid "`Xen `__" -msgstr "" - -#: ../telemetry-data-collection.rst:334 -msgid "" -"`Zookeeper `__. Recommended solution by the " -"Tooz project." -msgstr "" - -#: ../telemetry-data-retrieval.rst:85 -msgid "``!=``" -msgstr "" - -#: ../database.rst:121 ../database.rst:184 -msgid "``\"\"``" -msgstr "" - -#: ../networking_config-agents.rst:515 -msgid "``$ neutron agent-delete AGENT_ID``" -msgstr "" - -#: ../networking_config-agents.rst:496 -msgid "``$ neutron agent-list``" -msgstr "" - -#: ../networking_config-agents.rst:501 -msgid "``$ neutron agent-show AGENT_ID``" -msgstr "" - -#: ../networking_config-agents.rst:509 -msgid "``$ neutron agent-update --admin`` ``-state-up False AGENT_ID``" -msgstr "" - -#: ../networking_use.rst:51 -msgid "``$ neutron net-create net1``" -msgstr "" - -#: ../networking_use.rst:128 -msgid "``$ neutron net-create`` ``--shared public-net``" -msgstr "" - -#: ../networking_use.rst:187 -msgid "``$ neutron net-list``" -msgstr "" - -#: ../networking_use.rst:200 -msgid "``$ neutron port-list --device_id VM_ID``" -msgstr "" - -#: ../networking_use.rst:206 -msgid "``$ neutron port-list --field`` ``mac_address --device_id VM_ID``" -msgstr "" - -#: ../networking_use.rst:168 -msgid "``$ neutron port-list --network_id NET_ID``" -msgstr "" - -#: ../networking_use.rst:71 -msgid "``$ neutron port-list -c id`` ``-c fixed_ips -c device_owner``" -msgstr "" - -#: ../networking_use.rst:62 -msgid "``$ neutron port-list``" -msgstr "" - -#: ../networking_use.rst:76 -msgid "``$ neutron port-show PORT_ID``" -msgstr "" - -#: ../networking_use.rst:212 -msgid "``$ neutron port-update PORT_ID`` ``--admin_state_up False``" -msgstr "" - -#: ../networking_use.rst:161 -msgid "" -"``$ neutron subnet-create test-net1`` ``40.0.0.0/24 --dns-nameservers`` " -"``list=true 8.8.4.4 8.8.8.8``" -msgstr "" - -#: ../networking_use.rst:134 -msgid "``$ neutron subnet-create`` ``--gateway 10.0.0.254 net1 10.0.0.0/24``" -msgstr "" - -#: ../networking_use.rst:140 -msgid "``$ neutron subnet-create`` ``--no-gateway net1 10.0.0.0/24``" -msgstr "" - -#: ../networking_use.rst:146 -msgid "``$ neutron subnet-create`` ``net1 10.0.0.0/24 --enable-dhcp False``" -msgstr "" - -#: ../networking_use.rst:56 -msgid "``$ neutron subnet-create`` ``net1 10.0.0.0/24``" -msgstr "" - -#: ../networking_use.rst:151 -msgid "" -"``$ neutron subnet-create`` ``test-net1 40.0.0.0/24 --host-routes`` " -"``type=dict list=true`` ``destination=40.0.1.0/24,`` ``nexthop=40.0.0.2``" -msgstr "" - -#: ../networking_use.rst:256 -msgid "``$ nova boot --image IMAGE --flavor``" -msgstr "" - -#: ../networking_use.rst:246 -msgid "" -"``$ nova boot --image IMAGE --flavor`` ``FLAVOR --nic net-id=NET1-ID --nic`` " -"``net-id=NET2-ID VM_NAME``" -msgstr "" - -#: ../networking_use.rst:192 -msgid "" -"``$ nova boot --image IMAGE --flavor`` ``FLAVOR --nic net-id=NET_ID VM_NAME``" -msgstr "" - -#: ../networking_use.rst:264 -msgid "``$ nova boot --image IMAGE --flavor`` ``FLAVOR VM_NAME``" -msgstr "" - -#: ../orchestration-stack-domain-users.rst:62 -msgid "" -"``$OS_TOKEN`` refers to a token. For example, the service admin token or " -"some other valid token for a user with sufficient roles to create users and " -"domains. ``$KS_ENDPOINT_V3`` refers to the v3 OpenStack Identity endpoint " -"(for example, ``http://keystone_address:5000/v3`` where *keystone_address* " -"is the IP address or resolvable name for the OpenStack Identity service)." -msgstr "" - -#: ../telemetry-data-retrieval.rst:321 -msgid "``--filter``" -msgstr "" - -#: ../telemetry-data-retrieval.rst:328 -msgid "``--limit``" -msgstr "" - -#: ../telemetry-data-retrieval.rst:325 -msgid "``--orderby``" -msgstr "" - -#: ../database.rst:192 -msgid "``0`` = disabled" -msgstr "" - -#: ../keystone_use_trusts.rst:40 -msgid "``0``. The delegate cannot delegate these permissions further." -msgstr "" - -#: ../database.rst:191 -msgid "``1`` = active" -msgstr "" - -#: ../keystone_use_trusts.rst:42 -msgid "" -"``1``. The delegate can delegate the permissions to any set of delegates but " -"the latter cannot delegate further." -msgstr "" - -#: ../telemetry-data-retrieval.rst:89 -msgid "``<=``" -msgstr "" - -#: ../telemetry-data-retrieval.rst:87 -msgid "``<``" -msgstr "" - -#: ../blockstorage-driver-filter-weighing.rst:243 -msgid "``.``" -msgstr "" - -#: ../telemetry-data-retrieval.rst:83 -msgid "``=``" -msgstr "" - -#: ../telemetry-data-retrieval.rst:93 -msgid "``>=``" -msgstr "" - -#: ../telemetry-data-retrieval.rst:91 -msgid "``>``" -msgstr "" - -#: ../networking_introduction.rst:274 -msgid "" -"``Allowed-address-pairs`` enable you to specify mac_address/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." -msgstr "" - -#: ../keystone_secure_identity_to_ldap_backend.rst:64 -msgid "" -"``CA_FILE`` is the absolute path to the certificate authorities file that " -"should be used to encrypt LDAP traffic." -msgstr "" - -#: ../keystone_secure_identity_to_ldap_backend.rst:67 -msgid "" -"``CERT_BEHAVIOR`` specifies what client certificate checks to perform on an " -"incoming TLS session from the LDAP server (``demand``, ``allow``, or " -"``never``)." -msgstr "" - -#: ../cross_project_cors.rst:129 -msgid "``CORS request from origin 'http://foo.com' not permitted.``" -msgstr "" - -#: ../networking_use.rst:256 -msgid "``FLAVOR --nic net-id=NET-ID,`` ``v4-fixed-ip=IP-ADDR VM_NAME``" -msgstr "" - -#: ../blockstorage_nfs_backend.rst:39 -msgid "``HOST:SHARE``" -msgstr "" - -#: ../compute-configuring-migrations.rst:113 -msgid "" -"``HostA`` is the Cloud Controller, and should run these services: nova-api, " -"nova-scheduler, ``nova-network``, cinder-volume, and ``nova-objectstore``." -msgstr "" - -#: ../compute-configuring-migrations.rst:117 -msgid "``HostB`` and ``HostC`` are the compute nodes that run nova-compute." -msgstr "" - -# #-#-#-#-# compute_arch.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -# #-#-#-#-# compute-images-instances.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -#: ../compute_arch.rst:261 ../compute-images-instances.rst:367 -msgid "``ID``" -msgstr "" - -#: ../identity_service_api_protection.rst:24 -msgid "" -"``MATCH_STATEMENT`` is a set of identifiers that must match between the " -"token provided by the caller of the API and the parameters or target " -"entities of the API call in question. For example:" -msgstr "" - -#: ../telemetry-data-collection.rst:364 -msgid "" -"``Memcached`` uses a ``timeout`` value, which should always be set to a " -"value that is higher than the ``heartbeat`` value set for Telemetry." -msgstr "" - -# #-#-#-#-# compute_arch.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -# #-#-#-#-# compute-images-instances.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -#: ../compute_arch.rst:264 ../compute-images-instances.rst:370 -msgid "``Name``" -msgstr "" - -#: ../identity_service_api_protection.rst:21 -msgid "" -"``RULE_STATEMENT`` can contain ``RULE_STATEMENT`` or ``MATCH_STATEMENT``." -msgstr "" - -#: ../cross_project_cors.rst:139 -msgid "" -"``Request header 'X-Custom-Header' not in permitted list: X-Other-Header``" -msgstr "" - -#: ../cross_project_cors.rst:134 -msgid "``Request method 'DELETE' not in permitted list: GET,PUT,POST``" -msgstr "" - -# #-#-#-#-# compute_arch.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -# #-#-#-#-# compute-images-instances.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -#: ../compute_arch.rst:273 ../compute-images-instances.rst:379 -msgid "``Server``" -msgstr "" - -# #-#-#-#-# compute_arch.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -# #-#-#-#-# compute-images-instances.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -#: ../compute_arch.rst:268 ../compute-images-instances.rst:374 -msgid "``Status``" -msgstr "" - -#: ../networking_config-identity.rst:168 -msgid "``[DEFAULT] network_api_class``" -msgstr "" - -#: ../networking_config-identity.rst:186 -msgid "``[neutron] admin_auth_url``" -msgstr "" - -#: ../networking_config-identity.rst:183 -msgid "``[neutron] admin_password``" -msgstr "" - -#: ../networking_config-identity.rst:177 -msgid "``[neutron] admin_tenant_name``" -msgstr "" - -#: ../networking_config-identity.rst:180 -msgid "``[neutron] admin_username``" -msgstr "" - -#: ../networking_config-identity.rst:175 -msgid "``[neutron] auth_strategy``" -msgstr "" - -#: ../networking_config-identity.rst:172 -msgid "``[neutron] url``" -msgstr "" - -#: ../compute-remote-console-access.rst:37 -msgid "``agent_enabled = True``" -msgstr "" - -#: ../keystone_secure_identity_to_ldap_backend.rst:44 -msgid "" -"``allow`` - The LDAP server always recieves certificate requests. The " -"session will proceed as normal even if a certificate is not provided. If a " -"certificate is provided but it cannot be verified against the existing " -"certificate authorities file, the certificate will be ignored and the " -"session will proceed as normal." -msgstr "" - -#: ../networking_adv-features.rst:644 -msgid "``always_read_status``" -msgstr "" - -#: ../telemetry-data-retrieval.rst:97 -msgid "``and``" -msgstr "" - -#: ../objectstorage_ringbuilder.rst:51 -msgid "" -"``array('H')`` is used for memory conservation as there may be millions of " -"partitions." -msgstr "" - -#: ../telemetry-data-retrieval.rst:143 -msgid "``avg``" -msgstr "" - -#: ../networking_introduction.rst:99 -msgid "``backlog = 4096``" -msgstr "" - -#: ../telemetry-data-retrieval.rst:582 -msgid "``backup_count``" -msgstr "" - -# #-#-#-#-# keystone_certificates_for_pki.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -# #-#-#-#-# keystone_configure_with_SSL.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -#: ../keystone_certificates_for_pki.rst:43 -#: ../keystone_configure_with_SSL.rst:67 -msgid "``ca_certs``" -msgstr "" - -#: ../keystone_certificates_for_pki.rst:47 -msgid "``ca_key``" -msgstr "" - -#: ../blockstorage_over_subscription.rst:87 -msgid "" -"``capabilities`` scope key before ``thin_provisioning_support`` and " -"``thick_provisioning_support`` is not required. So the following works too:" -msgstr "" - -#: ../telemetry-data-retrieval.rst:154 -msgid "``cardinality``" -msgstr "" - -#: ../keystone_configure_with_SSL.rst:70 -msgid "``cert_required``" -msgstr "" - -#: ../keystone_certificates_for_pki.rst:57 -msgid "``cert_subject``" -msgstr "" - -# #-#-#-#-# keystone_certificates_for_pki.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -# #-#-#-#-# keystone_configure_with_SSL.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -#: ../keystone_certificates_for_pki.rst:34 -#: ../keystone_configure_with_SSL.rst:59 -msgid "``certfile``" -msgstr "" - -#: ../networking_use.rst:88 -msgid "``compute`` is created by Compute." -msgstr "" - -#: ../telemetry-data-retrieval.rst:161 -msgid "``count``" -msgstr "" - -#: ../compute-flavors.rst:111 -msgid "" -"``cpu_limit``. Specifies the upper limit for VMware machine CPU allocation " -"in MHz. This parameter ensures that a machine never uses more than the " -"defined amount of CPU time. It can be used to enforce a limit on the " -"machine's CPU performance." -msgstr "" - -#: ../compute-flavors.rst:105 -msgid "" -"``cpu_period``. Specifies the enforcement interval (unit: microseconds) for " -"QEMU and LXC hypervisors. Within a period, each VCPU of the domain is not " -"allowed to consume more than the quota worth of runtime. The value should be " -"in range ``[1000, 1000000]``. A period with value 0 means no value." -msgstr "" - -#: ../compute-flavors.rst:121 -msgid "" -"``cpu_quota``. Specifies the maximum allowed bandwidth (unit: microseconds). " -"A domain with a negative-value quota indicates that the domain has infinite " -"bandwidth, which means that it is not bandwidth controlled. The value should " -"be in range ``[1000, 18446744073709551]`` or less than 0. A quota with value " -"0 means no value. You can use this feature to ensure that all vCPUs run at " -"the same speed. For example:" -msgstr "" - -#: ../compute-flavors.rst:116 -msgid "" -"``cpu_reservation``. Specifies the guaranteed minimum CPU reservation in MHz " -"for VMware. This means that if needed, the machine will definitely get " -"allocated the reserved amount of CPU cycles." -msgstr "" - -#: ../compute-flavors.rst:101 -msgid "" -"``cpu_shares_level``. On VMWare, specifies the allocation level. Can be " -"``custom``, ``high``, ``normal``, or ``low``. If you choose ``custom``, set " -"the number of shares using ``cpu_shares_share``." -msgstr "" - -#: ../compute-flavors.rst:94 -msgid "" -"``cpu_shares``. Specifies the proportional weighted share for the domain. If " -"this element is omitted, the service defaults to the OS provided defaults. " -"There is no unit for the value; it is a relative measure based on the " -"setting of other VMs. For example, a VM configured with value 2048 gets " -"twice as much CPU time as a VM configured with value 1024." -msgstr "" - -#: ../compute-live-migration-usage.rst:192 -msgid "``cpu``: Number of CPUs" -msgstr "" - -#: ../compute-remote-console-access.rst:156 -msgid "``daemon = False``" -msgstr "" - -#: ../objectstorage-monitoring.rst:177 -msgid "" -"``decrement(self, metric, sample_rate=1)`` Lowers the given counter meter by " -"one." -msgstr "" - -#: ../keystone_secure_identity_to_ldap_backend.rst:40 -msgid "" -"``demand`` - The LDAP server always recieves certificate requests. The " -"session terminates if no certificate is provided, or if the certificate " -"provided cannot be verified against the existing certificate authorities " -"file." -msgstr "" - -#: ../objectstorage-troubleshoot.rst:63 -msgid "``device_dir = /srv/node``" -msgstr "" - -#: ../keystone_token-binding.rst:35 -msgid "``disabled``" -msgstr "" - -#: ../compute-flavors.rst:239 -msgid "``disabled``—(default) The device is not attached." -msgstr "" - -#: ../compute-live-migration-usage.rst:196 -msgid "``disk_gb``: Total amount of space for NOVA-INST-DIR/instances, in GB" -msgstr "" - -#: ../identity_service_api_protection.rst:51 -msgid "``domain_id``" -msgstr "" - -#: ../keystone_configure_with_SSL.rst:56 -msgid "``enable``" -msgstr "" - -#: ../compute-remote-console-access.rst:39 -msgid "``enabled = False``" -msgstr "" - -#: ../objectstorage-troubleshoot.rst:65 -msgid "``error_limit = 1``" -msgstr "" - -#: ../telemetry-data-retrieval.rst:48 -msgid "``field``" -msgstr "" - -#: ../networking_config-identity.rst:209 -msgid "``firewall_driver``" -msgstr "" - -#: ../compute-remote-console-access.rst:41 -msgid "``html5proxy_base_url = http://127.0.0.1:6082/spice_auto.html``" -msgstr "" - -#: ../compute-remote-console-access.rst:44 -msgid "``html5proxy_host = 0.0.0.0``" -msgstr "" - -#: ../compute-remote-console-access.rst:46 -msgid "``html5proxy_port = 6082``" -msgstr "" - -#: ../blockstorage_image_volume_cache.rst:85 -msgid "" -"``image_volume_cache.evict`` - A cached image-volume has been deleted from " -"the cache." -msgstr "" - -#: ../blockstorage_image_volume_cache.rst:82 -msgid "" -"``image_volume_cache.hit`` - A volume is being created from an image which " -"was found in the cache and the fast path can be taken." -msgstr "" - -#: ../blockstorage_image_volume_cache.rst:78 -msgid "" -"``image_volume_cache.miss`` - A volume is being created from an image which " -"was not found in the cache. Typically this will mean a new cache entry would " -"be created for it." -msgstr "" - -#: ../objectstorage-monitoring.rst:174 -msgid "" -"``increment(self, metric, sample_rate=1)`` Increments the given counter " -"meter by one." -msgstr "" - -#: ../keystone_use_trusts.rst:45 -msgid "``inf``. The delegation is infinitely recursive." -msgstr "" - -#: ../keystone_token-binding.rst:58 -msgid "``kerberos``" -msgstr "" - -#: ../compute-remote-console-access.rst:158 -msgid "``key = None``" -msgstr "" - -#: ../keystone_certificates_for_pki.rst:50 -msgid "``key_size``" -msgstr "" - -# #-#-#-#-# keystone_certificates_for_pki.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -# #-#-#-#-# keystone_configure_with_SSL.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -#: ../keystone_certificates_for_pki.rst:38 -#: ../keystone_configure_with_SSL.rst:64 -msgid "``keyfile``" -msgstr "" - -#: ../compute-remote-console-access.rst:48 -msgid "``keymap = en-us``" -msgstr "" - -#: ../keystone_caching_layer.rst:118 -msgid "``keystone.common.cache.backends.mongo``" -msgstr "" - -#: ../objectstorage-troubleshoot.rst:67 -msgid "``log_address = /dev/log``" -msgstr "" - -#: ../objectstorage-troubleshoot.rst:69 -msgid "``log_facility = LOG_LOCAL0``" -msgstr "" - -#: ../objectstorage-troubleshoot.rst:71 -msgid "``log_file_pattern = /var/log/kern.*[!.][!g][!z]``" -msgstr "" - -#: ../objectstorage-troubleshoot.rst:74 -msgid "``log_level = INFO``" -msgstr "" - -#: ../objectstorage-troubleshoot.rst:76 -msgid "``log_max_line_length = 0``" -msgstr "" - -#: ../objectstorage-troubleshoot.rst:79 -msgid "``log_to_console = False``" -msgstr "" - -#: ../telemetry-data-retrieval.rst:575 -msgid "``max_bytes``" -msgstr "" - -#: ../blockstorage_over_subscription.rst:29 -msgid "" -"``max_over_subscription_ratio`` can be configured for each back end when " -"multiple-storage back ends are enabled. It is provided as a reference " -"implementation and is used by the LVM driver. However, it is not a " -"requirement for a driver to use this option from :file:`cinder.conf`." -msgstr "" - -#: ../blockstorage_over_subscription.rst:34 -msgid "" -"``max_over_subscription_ratio`` is for configuring a back end. For a driver " -"that supports multiple pools per back end, it can report this ratio for each " -"pool. The LVM driver does not support multiple pools." -msgstr "" - -#: ../networking_adv-features.rst:619 -msgid "``max_random_sync_delay``" -msgstr "" - -#: ../telemetry-data-retrieval.rst:164 -msgid "``max``" -msgstr "" - -#: ../compute-live-migration-usage.rst:194 -msgid "``memory_mb``: Total amount of memory, in MB" -msgstr "" - -#: ../networking_config-identity.rst:238 -msgid "``metadata_proxy_shared_secret``" -msgstr "" - -#: ../networking_adv-features.rst:633 -msgid "``min_chunk_size``" -msgstr "" - -#: ../networking_adv-features.rst:626 -msgid "``min_sync_req_delay``" -msgstr "" - -#: ../telemetry-data-retrieval.rst:167 -msgid "``min``" -msgstr "" - -#: ../objectstorage-troubleshoot.rst:81 -msgid "``minutes = 60``" -msgstr "" - -#: ../database.rst:159 -msgid "``mysql-5.5``" -msgstr "" - -#: ../database.rst:114 ../database.rst:155 ../database.rst:172 -msgid "``mysql``" -msgstr "" - -#: ../networking_use.rst:86 -msgid "``network`` is created by Networking." -msgstr "" - -#: ../keystone_secure_identity_to_ldap_backend.rst:50 -msgid "``never`` - A certificate will never be requested." -msgstr "" - -#: ../compute-flavors.rst:247 -msgid "``none``—Only enable the watchdog; do nothing if the server hangs." -msgstr "" - -#: ../telemetry-data-retrieval.rst:101 -msgid "``not``" -msgstr "" - -#: ../compute-system-admin.rst:42 -msgid "``nova-api``" -msgstr "" - -#: ../compute-system-admin.rst:45 -msgid "``nova-cert``" -msgstr "" - -#: ../compute-system-admin.rst:50 -msgid "``nova-compute``" -msgstr "" - -#: ../compute-system-admin.rst:54 -msgid "``nova-conductor``" -msgstr "" - -#: ../compute-system-admin.rst:57 -msgid "``nova-consoleauth``" -msgstr "" - -#: ../compute-system-admin.rst:72 -msgid "``nova-network``" -msgstr "" - -#: ../compute-system-admin.rst:80 -msgid "``nova-novncproxy``" -msgstr "" - -#: ../compute-system-admin.rst:64 -msgid "``nova-objectstore``" -msgstr "" - -#: ../compute-system-admin.rst:76 -msgid "``nova-scheduler``" -msgstr "" - -#: ../compute-manage-the-cloud.rst:15 -msgid "" -"``nova`` client and ``euca2ools`` can be used by all users, though specific " -"commands might be restricted by Role Based Access Control in the Identity " -"Service." -msgstr "" - -#: ../compute-remote-console-access.rst:304 -msgid "" -"``novncproxy_base_url`` and ``xvpvncproxy_base_url`` use a public IP; this " -"is the URL that is ultimately returned to clients, which generally do not " -"have access to your private network. Your PROXYSERVER must be able to reach " -"``vncserver_proxyclient_address``, because that is the address over which " -"the VNC connection is proxied." -msgstr "" - -#: ../compute-remote-console-access.rst:160 -msgid "``novncproxy_host = 0.0.0.0``" -msgstr "" - -#: ../compute-remote-console-access.rst:162 -msgid "``novncproxy_port = 6080``" -msgstr "" - -#: ../networking_adv-features.rst:611 ../networking_adv-features.rst:620 -#: ../networking_adv-features.rst:627 ../networking_adv-features.rst:634 -#: ../networking_adv-features.rst:645 -msgid "``nsx_sync``" -msgstr "" - -#: ../telemetry-data-retrieval.rst:50 -msgid "``op``" -msgstr "" - -#: ../telemetry-data-retrieval.rst:99 -msgid "``or``" -msgstr "" - -#: ../blockstorage_volume_migration.rst:109 -msgid "``os-vol-host-attr:host`` - the volume's current back-end." -msgstr "" - -#: ../blockstorage_volume_migration.rst:110 -msgid "" -"``os-vol-mig-status-attr:migstat`` - the status of this volume's migration " -"(None means that a migration is not currently in progress)." -msgstr "" - -#: ../blockstorage_volume_migration.rst:112 -msgid "" -"``os-vol-mig-status-attr:name_id`` - the volume ID that this volume's name " -"on the back-end is based on. Before a volume is ever migrated, its name on " -"the back-end storage may be based on the volume's ID (see the " -"``volume_name_template`` configuration parameter). For example, if " -"``volume_name_template`` is kept as the default value (``volume-%s``), your " -"first LVM back-end has a logical volume named ``volume-6088f80a-f116-4331-" -"ad48-9afb0dfb196c``. During the course of a migration, if you create a " -"volume and copy over the data, the volume get the new name but keeps its " -"original ID. This is exposed by the ``name_id`` attribute." -msgstr "" - -#: ../compute-flavors.rst:245 -msgid "``pause``—Pause the guest." -msgstr "" - -#: ../telemetry-data-retrieval.rst:542 -msgid "``per_meter_topic``" -msgstr "" - -#: ../keystone_token-binding.rst:40 -msgid "``permissive``" -msgstr "" - -#: ../telemetry-data-retrieval.rst:559 -msgid "``policy``" -msgstr "" - -#: ../compute-flavors.rst:243 -msgid "``poweroff``—Forcefully power off the guest." -msgstr "" - -# #-#-#-#-# identity_service_api_protection.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -# #-#-#-#-# telemetry-data-retrieval.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -#: ../identity_service_api_protection.rst:52 -#: ../telemetry-data-retrieval.rst:150 -msgid "``project_id``" -msgstr "" - -#: ../telemetry-data-retrieval.rst:66 -msgid "``project_id``: project" -msgstr "" - -#: ../objectstorage-troubleshoot.rst:83 -msgid "``recon_cache_path = /var/cache/swift``" -msgstr "" - -#: ../compute-remote-console-access.rst:164 -msgid "``record = False``" -msgstr "" - -#: ../objectstorage-troubleshoot.rst:85 -msgid "``regex_pattern_1 = \\berror\\b.*\\b(dm-[0-9]{1,2}\\d?)\\b``" -msgstr "" - -#: ../keystone_token-binding.rst:48 -msgid "``required``" -msgstr "" - -#: ../compute-flavors.rst:241 -msgid "``reset``—Forcefully reset the guest." -msgstr "" - -#: ../telemetry-data-retrieval.rst:152 -msgid "``resource_id``" -msgstr "" - -#: ../telemetry-data-retrieval.rst:68 -msgid "``resource_id``: resource" -msgstr "" - -#: ../networking_introduction.rst:96 -msgid "``retry_until_window = 30``" -msgstr "" - -#: ../networking_config-identity.rst:213 -msgid "``security_group_api``" -msgstr "" - -#: ../compute-remote-console-access.rst:50 -msgid "``server_listen = 127.0.0.1``" -msgstr "" - -#: ../compute-remote-console-access.rst:52 -msgid "``server_proxyclient_address = 127.0.0.1``" -msgstr "" - -#: ../networking_config-identity.rst:234 -msgid "``service_metadata_proxy``" -msgstr "" - -#: ../objectstorage-monitoring.rst:160 -msgid "" -"``set_statsd_prefix(self, prefix)`` Sets the client library stat prefix " -"value which gets prefixed to every meter. The default prefix is the \"name\" " -"of the logger such as \"object-server\", \"container-auditor\", and so on. " -"This is currently used to turn \"proxy-server\" into one of \"proxy-server." -"Account\", \"proxy-server.Container\", or \"proxy-server.Object\" as soon as " -"the Controller object is determined and instantiated for the request." -msgstr "" - -#: ../compute-remote-console-access.rst:166 -msgid "``source_is_ipv6 = False``" -msgstr "" - -#: ../networking_introduction.rst:89 -msgid "``ssl_ca_file = PATH_TO_CAFILE``" -msgstr "" - -#: ../networking_introduction.rst:79 -msgid "``ssl_cert_file = PATH_TO_CERTFILE``" -msgstr "" - -#: ../networking_introduction.rst:83 -msgid "``ssl_key_file = PATH_TO_KEYFILE``" -msgstr "" - -#: ../compute-remote-console-access.rst:168 -msgid "``ssl_only = False``" -msgstr "" - -#: ../networking_adv-features.rst:610 -msgid "``state_sync_interval``" -msgstr "" - -#: ../telemetry-data-retrieval.rst:170 -msgid "``stddev``" -msgstr "" - -#: ../keystone_token-binding.rst:44 -msgid "``strict``" -msgstr "" - -#: ../telemetry-data-retrieval.rst:173 -msgid "``sum``" -msgstr "" - -#: ../networking_introduction.rst:93 -msgid "``tcp_keepidle = 600``" -msgstr "" - -#: ../objectstorage-monitoring.rst:180 -msgid "" -"``timing(self, metric, timing_ms, sample_rate=1)`` Record that the given " -"meter took the supplied number of milliseconds." -msgstr "" - -#: ../objectstorage-monitoring.rst:183 -msgid "" -"``timing_since(self, metric, orig_time, sample_rate=1)`` Convenience method " -"to record a timing meter whose value is \"now\" minus an existing timestamp." -msgstr "" - -#: ../telemetry-data-retrieval.rst:567 -msgid "``topic``" -msgstr "" - -#: ../telemetry-data-retrieval.rst:54 -msgid "``type``" -msgstr "" - -#: ../objectstorage-troubleshoot.rst:87 -msgid "``unmount_failed_device = True``" -msgstr "" - -#: ../objectstorage-monitoring.rst:168 -msgid "" -"``update_stats(self, metric, amount, sample_rate=1)`` Increments the " -"supplied meter by the given amount. This is used when you need to add or " -"subtract more that one from a counter, like incrementing \"suffix.hashes\" " -"by the number of computed hashes in the object replicator." -msgstr "" - -#: ../networking_introduction.rst:75 -msgid "``use_ssl = True``" -msgstr "" - -#: ../identity_service_api_protection.rst:59 -msgid "``user.domain_id``" -msgstr "" - -# #-#-#-#-# identity_service_api_protection.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -# #-#-#-#-# telemetry-data-retrieval.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -#: ../identity_service_api_protection.rst:50 -#: ../telemetry-data-retrieval.rst:154 -msgid "``user_id``" -msgstr "" - -#: ../telemetry-data-retrieval.rst:70 -msgid "``user_id``: user" -msgstr "" - -#: ../keystone_certificates_for_pki.rst:53 -msgid "``valid_days``" -msgstr "" - -#: ../telemetry-data-retrieval.rst:52 -msgid "``value``" -msgstr "" - -#: ../compute-remote-console-access.rst:174 -msgid "``vnc_port = 5900``" -msgstr "" - -#: ../compute-remote-console-access.rst:176 -msgid "``vnc_port_total = 10000``" -msgstr "" - -#: ../compute-remote-console-access.rst:235 -msgid "``vncserver_listen=0.0.0.0``" -msgstr "" - -#: ../compute-remote-console-access.rst:249 -msgid "``vncserver_proxyclient_address=127.0.0.1``" -msgstr "" - -#: ../compute-remote-console-access.rst:170 -msgid "``web = /usr/share/spice-html5``" -msgstr "" - -#: ../keystone_token-binding.rst:67 -msgid "``x509``" -msgstr "" - -#: ../keystone_caching_layer.rst:116 -msgid "" -"`dogpile.cache.backends.file `__" -msgstr "" - -#: ../keystone_caching_layer.rst:107 -msgid "" -"`dogpile.cache.backends.memcached `__" -msgstr "" - -#: ../keystone_caching_layer.rst:105 -msgid "" -"`dogpile.cache.backends.memory `__" -msgstr "" - -#: ../keystone_caching_layer.rst:114 -msgid "" -"`dogpile.cache.backends.redis `__" -msgstr "" - -#: ../compute-system-admin.rst:60 -msgid "" -"a simple file-based storage system for images that replicates most of the S3 " -"API. It can be replaced with OpenStack Image service and either a simple " -"image manager or OpenStack Object Storage as the virtual machine image " -"storage facility. It must exist on the same node as nova-compute." -msgstr "" - -#: ../compute-live-migration-usage.rst:92 -msgid "a.b.c.d" -msgstr "" - -#: ../blockstorage-driver-filter-weighing.rst:113 -msgid "abs(x), max(x, y), min(x, y)" -msgstr "" - -#: ../telemetry-data-collection.rst:611 -msgid "accumulator" -msgstr "" - -#: ../networking_adv-features.rst:704 -msgid "action" -msgstr "" - -# #-#-#-#-# database.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -# #-#-#-#-# ts-eql-volume-size.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -#: ../database.rst:189 ../ts-eql-volume-size.rst:113 -msgid "active" -msgstr "" - -#: ../telemetry-alarms.rst:256 -msgid "admin users see *all* alarms, regardless of the owner" -msgstr "" - -#: ../telemetry-data-collection.rst:613 -msgid "aggregator" -msgstr "" - -#: ../telemetry-alarms.rst:19 -msgid "alarm" -msgstr "" - -#: ../blockstorage-driver-filter-weighing.rst:155 -msgid "allocated\\_capacity\\_gb" -msgstr "" - -#: ../compute-security.rst:89 -msgid "api_url" -msgstr "" - -#: ../telemetry-data-collection.rst:615 -msgid "arithmetic" -msgstr "" - -#: ../blockstorage-driver-filter-weighing.rst:189 -msgid "attach\\_status" -msgstr "" - -#: ../compute-security.rst:107 -msgid "attestation_api_url = /OpenAttestationWebServices/V1.0" -msgstr "" - -#: ../compute-security.rst:109 -msgid "attestation_auth_blob = None" -msgstr "" - -#: ../compute-security.rst:111 -msgid "attestation_auth_timeout = 60" -msgstr "" - -#: ../compute-security.rst:113 -msgid "attestation_insecure_ssl = False" -msgstr "" - -#: ../compute-security.rst:115 -msgid "attestation_port = 8443" -msgstr "" - -#: ../compute-security.rst:117 -msgid "attestation_server = None" -msgstr "" - -#: ../compute-security.rst:119 -msgid "attestation_server_ca_file = None" -msgstr "" - -#: ../compute-security.rst:92 -msgid "auth_blob" -msgstr "" - -#: ../compute-flavors.rst:194 ../compute-flavors.rst:202 -msgid "average: 256 Mbps (32768 kilobytes/second)" -msgstr "" - -#: ../telemetry-measurements.rst:963 -msgid "bandwidth" -msgstr "" - -#: ../ts-eql-volume-size.rst:113 -msgid "bare" -msgstr "" - -#: ../database.rst:178 -msgid "bb75f870-0c33-4907-8467-1367f8cb15b6" -msgstr "" - -#: ../telemetry-measurements.rst:645 ../telemetry-measurements.rst:650 -msgid "bloc\\ ks" -msgstr "" - -#: ../compute_arch.rst:222 -msgid "boto" -msgstr "" - -#: ../compute-flavors.rst:198 ../compute-flavors.rst:206 -msgid "burst: 65536 kilobytes" -msgstr "" - -#: ../keystone_configure_with_SSL.rst:13 -msgid "cacert.pem" -msgstr "" - -#: ../keystone_configure_with_SSL.rst:23 -msgid "cakey.pem" -msgstr "" - -#: ../database.rst:169 -msgid "cassandra" -msgstr "" - -#: ../telemetry-system-architecture.rst:26 -msgid "ceilometer-agent-central" -msgstr "" - -#: ../telemetry-system-architecture.rst:32 -msgid "ceilometer-agent-compute" -msgstr "" - -#: ../telemetry-system-architecture.rst:37 -msgid "ceilometer-agent-ipmi" -msgstr "" - -#: ../telemetry-system-architecture.rst:40 -msgid "ceilometer-agent-notification" -msgstr "" - -#: ../telemetry-system-architecture.rst:48 -msgid "ceilometer-alarm-evaluator" -msgstr "" - -#: ../telemetry-system-architecture.rst:58 -msgid "ceilometer-alarm-notifier" -msgstr "" - -#: ../telemetry-system-architecture.rst:15 -msgid "ceilometer-api" -msgstr "" - -#: ../telemetry-system-architecture.rst:44 -msgid "ceilometer-collector" -msgstr "" - -#: ../telemetry-data-collection.rst:1015 -msgid "" -"ceilometer-expirer has to be used for deleting samples and its related data " -"from the database." -msgstr "" - -#: ../telemetry-system-architecture.rst:20 -msgid "ceilometer-polling" -msgstr "" - -#: ../ts_cinder_config.rst:12 -msgid "cinder-api log (:file:`/var/log/cinder/api.log`)" -msgstr "" - -#: ../ts_cinder_config.rst:14 -msgid "cinder-volume log (:file:`/var/log/cinder/volume.log`)" -msgstr "" - -#: ../telemetry-measurements.rst:1283 ../telemetry-measurements.rst:1288 -#: ../telemetry-measurements.rst:1292 -msgid "cluster" -msgstr "" - -#: ../telemetry-measurements.rst:1283 ../telemetry-measurements.rst:1288 -#: ../telemetry-measurements.rst:1292 -msgid "cluster ID" -msgstr "" - -#: ../telemetry-measurements.rst:1283 -msgid "cluster.create" -msgstr "" - -#: ../telemetry-measurements.rst:1292 -msgid "cluster.delete" -msgstr "" - -#: ../telemetry-measurements.rst:1288 -msgid "cluster.update" -msgstr "" - -#: ../telemetry-data-collection.rst:67 -msgid "compute.instance.\\*" -msgstr "" - -#: ../telemetry-measurements.rst:434 -msgid "compute.node.cpu.\\ frequency" -msgstr "" - -#: ../telemetry-measurements.rst:452 -msgid "compute.node.cpu.\\ idle.percent" -msgstr "" - -#: ../telemetry-measurements.rst:440 -msgid "compute.node.cpu.\\ idle.time" -msgstr "" - -#: ../telemetry-measurements.rst:458 -msgid "compute.node.cpu.\\ iowait.percent" +#: ../telemetry-measurements.rst:119 +msgid "CPU time used" msgstr "" +#: ../telemetry-measurements.rst:119 ../telemetry-measurements.rst:144 +#: ../telemetry-measurements.rst:151 ../telemetry-measurements.rst:164 +#: ../telemetry-measurements.rst:172 ../telemetry-measurements.rst:180 +#: ../telemetry-measurements.rst:189 ../telemetry-measurements.rst:232 +#: ../telemetry-measurements.rst:241 ../telemetry-measurements.rst:250 +#: ../telemetry-measurements.rst:259 ../telemetry-measurements.rst:437 +#: ../telemetry-measurements.rst:440 ../telemetry-measurements.rst:443 #: ../telemetry-measurements.rst:446 -msgid "compute.node.cpu.\\ iowait.time" +msgid "Cumu\\ lative" msgstr "" -#: ../telemetry-measurements.rst:449 -msgid "compute.node.cpu.\\ kernel.percent" +#: ../telemetry-measurements.rst:119 ../telemetry-measurements.rst:355 +#: ../telemetry-measurements.rst:437 ../telemetry-measurements.rst:440 +#: ../telemetry-measurements.rst:443 ../telemetry-measurements.rst:446 +#: ../telemetry-measurements.rst:1038 +msgid "ns" msgstr "" -#: ../telemetry-measurements.rst:437 -msgid "compute.node.cpu.\\ kernel.time" +#: ../telemetry-measurements.rst:122 ../telemetry-measurements.rst:216 +#: ../telemetry-measurements.rst:449 ../telemetry-measurements.rst:452 +#: ../telemetry-measurements.rst:455 ../telemetry-measurements.rst:458 +#: ../telemetry-measurements.rst:461 ../telemetry-measurements.rst:557 +#: ../telemetry-measurements.rst:561 ../telemetry-measurements.rst:565 +#: ../telemetry-measurements.rst:655 +msgid "%" msgstr "" -#: ../telemetry-measurements.rst:461 -msgid "compute.node.cpu.\\ percent" -msgstr "" - -#: ../telemetry-measurements.rst:455 -msgid "compute.node.cpu.\\ user.percent" -msgstr "" - -#: ../telemetry-measurements.rst:443 -msgid "compute.node.cpu.\\ user.time" -msgstr "" - -#: ../database.rst:109 ../database.rst:148 -msgid "config file" -msgstr "" - -#: ../telemetry-measurements.rst:1079 ../telemetry-measurements.rst:1083 -msgid "connec\\ tion" -msgstr "" - -#: ../telemetry-measurements.rst:1145 ../telemetry-measurements.rst:1160 -#: ../telemetry-measurements.rst:1165 -msgid "connection ID" -msgstr "" - -#: ../blockstorage-driver-filter-weighing.rst:216 -msgid "consistencygroup\\_id" -msgstr "" - -#: ../telemetry-measurements.rst:762 -msgid "conta\\ iner" -msgstr "" - -#: ../telemetry-measurements.rst:811 -msgid "contai\\ ner" -msgstr "" - -#: ../database.rst:170 -msgid "couchbase" -msgstr "" - -#: ../telemetry-measurements.rst:304 ../telemetry-measurements.rst:311 -msgid "coun\\ t/s" -msgstr "" - -#: ../telemetry-measurements.rst:1018 -msgid "count" -msgstr "" - -# #-#-#-#-# compute-live-migration-usage.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -# #-#-#-#-# telemetry-measurements.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -#: ../compute-live-migration-usage.rst:168 ../telemetry-measurements.rst:119 -msgid "cpu" -msgstr "" - -#: ../telemetry-measurements.rst:355 -msgid "cpu.delta" -msgstr "" - -#: ../telemetry-measurements.rst:383 -msgid "cpu\\_util" +#: ../telemetry-measurements.rst:122 ../telemetry-measurements.rst:216 +msgid "Average CPU utilisation" msgstr "" #: ../telemetry-measurements.rst:122 ../telemetry-measurements.rst:216 msgid "cpu_util" msgstr "" -#: ../telemetry-measurements.rst:498 -msgid "current sensor" +#: ../telemetry-measurements.rst:126 +msgid "Number of virtual CPUs allocated to the instance" msgstr "" -#: ../compute-live-migration-usage.rst:38 -#: ../compute-live-migration-usage.rst:88 -msgid "d1df1b5a-70c4-4fed-98b7-423362f2c47c" +#: ../telemetry-measurements.rst:126 +msgid "vcpu" msgstr "" -#: ../compute-live-migration-usage.rst:42 -msgid "d693db9e-a7cf-45ef-a7c9-b3ecb5f22645" +#: ../telemetry-measurements.rst:126 +msgid "vcpus" msgstr "" -#: ../telemetry-measurements.rst:637 ../telemetry-measurements.rst:641 -msgid "data\\ grams" +#: ../telemetry-measurements.rst:130 ../telemetry-measurements.rst:137 +#: ../telemetry-measurements.rst:626 ../telemetry-measurements.rst:630 +#: ../telemetry-measurements.rst:633 ../telemetry-measurements.rst:637 +#: ../telemetry-measurements.rst:641 ../telemetry-measurements.rst:645 +#: ../telemetry-measurements.rst:650 +msgid "Cumul\\ ative" msgstr "" -#: ../database.rst:152 -msgid "datastore" +#: ../telemetry-measurements.rst:130 ../telemetry-measurements.rst:232 +msgid "Number of read requests" msgstr "" -#: ../database.rst:161 -msgid "datastore manager" +#: ../telemetry-measurements.rst:130 +msgid "disk.read\\ .requests" msgstr "" -#: ../telemetry-data-retrieval.rst:550 -msgid "default" +#: ../telemetry-measurements.rst:130 ../telemetry-measurements.rst:137 +#: ../telemetry-measurements.rst:232 ../telemetry-measurements.rst:241 +msgid "req\\ uest" msgstr "" -#: ../database.rst:115 -msgid "default version" +#: ../telemetry-measurements.rst:133 ../telemetry-measurements.rst:236 +msgid "Average rate of read requests" msgstr "" -#: ../telemetry-data-collection.rst:621 -msgid "delta" +#: ../telemetry-measurements.rst:133 +msgid "disk.read\\ .requests\\ .rate" msgstr "" -#: ../telemetry-alarms.rst:185 -msgid "description" +#: ../telemetry-measurements.rst:133 ../telemetry-measurements.rst:140 +#: ../telemetry-measurements.rst:236 ../telemetry-measurements.rst:245 +msgid "requ\\ est/s" msgstr "" -#: ../networking_adv-features.rst:699 -msgid "destination" +#: ../telemetry-measurements.rst:137 ../telemetry-measurements.rst:241 +msgid "Number of write requests" +msgstr "" + +#: ../telemetry-measurements.rst:137 +msgid "disk.writ\\ e.requests" +msgstr "" + +#: ../telemetry-measurements.rst:140 ../telemetry-measurements.rst:245 +msgid "Average rate of write requests" +msgstr "" + +#: ../telemetry-measurements.rst:140 +msgid "disk.writ\\ e.request\\ s.rate" +msgstr "" + +#: ../telemetry-measurements.rst:144 ../telemetry-measurements.rst:151 +#: ../telemetry-measurements.rst:164 ../telemetry-measurements.rst:172 +#: ../telemetry-measurements.rst:250 ../telemetry-measurements.rst:259 +#: ../telemetry-measurements.rst:314 ../telemetry-measurements.rst:318 +#: ../telemetry-measurements.rst:324 ../telemetry-measurements.rst:329 +#: ../telemetry-measurements.rst:334 ../telemetry-measurements.rst:340 +#: ../telemetry-measurements.rst:626 ../telemetry-measurements.rst:630 +#: ../telemetry-measurements.rst:685 ../telemetry-measurements.rst:688 +#: ../telemetry-measurements.rst:759 ../telemetry-measurements.rst:765 +#: ../telemetry-measurements.rst:768 ../telemetry-measurements.rst:779 +#: ../telemetry-measurements.rst:808 ../telemetry-measurements.rst:822 +#: ../telemetry-measurements.rst:963 ../telemetry-measurements.rst:989 +#: ../telemetry-measurements.rst:992 ../telemetry-measurements.rst:1045 +#: ../telemetry-measurements.rst:1087 ../telemetry-measurements.rst:1091 +msgid "B" +msgstr "" + +#: ../telemetry-measurements.rst:144 ../telemetry-measurements.rst:250 +msgid "Volume of reads" +msgstr "" + +#: ../telemetry-measurements.rst:144 +msgid "disk.read\\ .bytes" +msgstr "" + +#: ../telemetry-measurements.rst:147 ../telemetry-measurements.rst:221 +#: ../telemetry-measurements.rst:254 +msgid "Average rate of reads" +msgstr "" + +#: ../telemetry-measurements.rst:147 ../telemetry-measurements.rst:154 +#: ../telemetry-measurements.rst:168 ../telemetry-measurements.rst:176 +#: ../telemetry-measurements.rst:221 ../telemetry-measurements.rst:226 +#: ../telemetry-measurements.rst:254 ../telemetry-measurements.rst:263 +#: ../telemetry-measurements.rst:268 ../telemetry-measurements.rst:273 +msgid "B/s" +msgstr "" + +#: ../telemetry-measurements.rst:147 ../telemetry-measurements.rst:221 +msgid "disk.read\\ .bytes.\\ rate" +msgstr "" + +#: ../telemetry-measurements.rst:151 ../telemetry-measurements.rst:259 +msgid "Volume of writes" +msgstr "" + +#: ../telemetry-measurements.rst:151 +msgid "disk.writ\\ e.bytes" +msgstr "" + +#: ../telemetry-measurements.rst:154 ../telemetry-measurements.rst:226 +#: ../telemetry-measurements.rst:263 +msgid "Average rate of writes" +msgstr "" + +#: ../telemetry-measurements.rst:154 +msgid "disk.writ\\ e.bytes.\\ rate" +msgstr "" + +#: ../telemetry-measurements.rst:158 ../telemetry-measurements.rst:161 +#: ../telemetry-measurements.rst:704 ../telemetry-measurements.rst:712 +msgid "GB" +msgstr "" + +#: ../telemetry-measurements.rst:158 +msgid "Size of root disk" +msgstr "" + +#: ../telemetry-measurements.rst:158 +msgid "disk.root\\ .size" +msgstr "" + +#: ../telemetry-measurements.rst:161 +msgid "Size of ephemeral disk" +msgstr "" + +#: ../telemetry-measurements.rst:161 +msgid "disk.ephe\\ meral.size" +msgstr "" + +#: ../telemetry-measurements.rst:164 +msgid "Number of incoming bytes" +msgstr "" + +#: ../telemetry-measurements.rst:164 ../telemetry-measurements.rst:168 +#: ../telemetry-measurements.rst:172 ../telemetry-measurements.rst:176 +#: ../telemetry-measurements.rst:180 ../telemetry-measurements.rst:184 +#: ../telemetry-measurements.rst:189 ../telemetry-measurements.rst:193 +#: ../telemetry-measurements.rst:268 ../telemetry-measurements.rst:273 +#: ../telemetry-measurements.rst:278 ../telemetry-measurements.rst:283 +#: ../telemetry-measurements.rst:626 ../telemetry-measurements.rst:630 +#: ../telemetry-measurements.rst:633 +msgid "interface ID" +msgstr "" + +#: ../telemetry-measurements.rst:164 +msgid "network.\\ incoming.\\ bytes" +msgstr "" + +#: ../telemetry-measurements.rst:168 ../telemetry-measurements.rst:268 +msgid "Average rate of incoming bytes" +msgstr "" + +#: ../telemetry-measurements.rst:168 ../telemetry-measurements.rst:268 +msgid "network.\\ incoming.\\ bytes.rate" +msgstr "" + +#: ../telemetry-measurements.rst:172 +msgid "Number of outgoing bytes" +msgstr "" + +#: ../telemetry-measurements.rst:172 +msgid "network.\\ outgoing\\ .bytes" +msgstr "" + +#: ../telemetry-measurements.rst:176 ../telemetry-measurements.rst:273 +msgid "Average rate of outgoing bytes" +msgstr "" + +#: ../telemetry-measurements.rst:176 ../telemetry-measurements.rst:273 +msgid "network.\\ outgoing.\\ bytes.rate" +msgstr "" + +#: ../telemetry-measurements.rst:180 +msgid "Number of incoming packets" +msgstr "" + +#: ../telemetry-measurements.rst:180 +msgid "network.\\ incoming| .packets" +msgstr "" + +#: ../telemetry-measurements.rst:180 ../telemetry-measurements.rst:189 +msgid "pac\\ ket" +msgstr "" + +#: ../telemetry-measurements.rst:184 ../telemetry-measurements.rst:278 +msgid "Average rate of incoming packets" +msgstr "" + +#: ../telemetry-measurements.rst:184 +msgid "network.\\ incoming\\ .packets\\ .rate" +msgstr "" + +#: ../telemetry-measurements.rst:184 ../telemetry-measurements.rst:278 +#: ../telemetry-measurements.rst:283 +msgid "pack\\ et/s" +msgstr "" + +#: ../telemetry-measurements.rst:189 +msgid "Number of outgoing packets" +msgstr "" + +#: ../telemetry-measurements.rst:189 +msgid "network.\\ outpoing\\ .packets" +msgstr "" + +#: ../telemetry-measurements.rst:193 ../telemetry-measurements.rst:283 +msgid "Average rate of outgoing packets" +msgstr "" + +#: ../telemetry-measurements.rst:193 +msgid "network.\\ outgoing\\ .packets\\ .rate" +msgstr "" + +#: ../telemetry-measurements.rst:193 +msgid "pac\\ ket/s" +msgstr "" + +#: ../telemetry-measurements.rst:198 +msgid "**Meters added or hypervisor support changed in the Juno release**" +msgstr "" + +#: ../telemetry-measurements.rst:200 ../telemetry-measurements.rst:205 +#: ../telemetry-measurements.rst:216 ../telemetry-measurements.rst:221 +#: ../telemetry-measurements.rst:226 ../telemetry-measurements.rst:268 +#: ../telemetry-measurements.rst:273 ../telemetry-measurements.rst:278 +#: ../telemetry-measurements.rst:283 ../telemetry-measurements.rst:290 +#: ../telemetry-measurements.rst:348 +msgid "Libvirt, Hyper-V, vSphere, XenAPI" +msgstr "" + +#: ../telemetry-measurements.rst:200 ../telemetry-measurements.rst:205 +#: ../telemetry-measurements.rst:348 +msgid "ins\\ tance" +msgstr "" + +#: ../telemetry-measurements.rst:205 ../telemetry-measurements.rst:348 +msgid "instance\\ :" +msgstr "" + +#: ../telemetry-measurements.rst:210 +msgid "vSphere, XenAPI" +msgstr "" + +#: ../telemetry-measurements.rst:226 +msgid "disk.\\ write.\\ bytes.rate" msgstr "" #: ../telemetry-measurements.rst:232 ../telemetry-measurements.rst:236 @@ -23259,42 +22276,6 @@ msgstr "" msgid "disk ID" msgstr "" -#: ../telemetry-measurements.rst:226 -msgid "disk.\\ write.\\ bytes.rate" -msgstr "" - -#: ../telemetry-measurements.rst:318 -msgid "disk.all\\ ocation" -msgstr "" - -#: ../telemetry-measurements.rst:314 -msgid "disk.cap\\ acity" -msgstr "" - -#: ../telemetry-measurements.rst:334 -msgid "disk.dev\\ ice.allo\\ cation" -msgstr "" - -#: ../telemetry-measurements.rst:329 -msgid "disk.dev\\ ice.capa\\ city" -msgstr "" - -#: ../telemetry-measurements.rst:311 -msgid "disk.dev\\ ice.iops" -msgstr "" - -#: ../telemetry-measurements.rst:307 -msgid "disk.dev\\ ice.late\\ ncy" -msgstr "" - -#: ../telemetry-measurements.rst:250 -msgid "disk.dev\\ ice.read\\ .bytes" -msgstr "" - -#: ../telemetry-measurements.rst:254 -msgid "disk.dev\\ ice.read\\ .bytes .rate" -msgstr "" - #: ../telemetry-measurements.rst:232 msgid "disk.dev\\ ice.read\\ .requests" msgstr "" @@ -23303,18 +22284,6 @@ msgstr "" msgid "disk.dev\\ ice.read\\ .requests\\ .rate" msgstr "" -#: ../telemetry-measurements.rst:340 -msgid "disk.dev\\ ice.usag\\ e" -msgstr "" - -#: ../telemetry-measurements.rst:259 -msgid "disk.dev\\ ice.write\\ .bytes" -msgstr "" - -#: ../telemetry-measurements.rst:263 -msgid "disk.dev\\ ice.write\\ .bytes .rate" -msgstr "" - #: ../telemetry-measurements.rst:241 msgid "disk.dev\\ ice.write\\ .requests" msgstr "" @@ -23323,422 +22292,289 @@ msgstr "" msgid "disk.dev\\ ice.write\\ .requests\\ .rate" msgstr "" -#: ../telemetry-measurements.rst:397 -msgid "disk.device.read.bytes.rate" +#: ../telemetry-measurements.rst:250 +msgid "disk.dev\\ ice.read\\ .bytes" msgstr "" -#: ../telemetry-measurements.rst:393 -msgid "disk.device.read.requests.rate" +#: ../telemetry-measurements.rst:254 +msgid "disk.dev\\ ice.read\\ .bytes .rate" msgstr "" -#: ../telemetry-measurements.rst:399 -msgid "disk.device.write.bytes.rate" +#: ../telemetry-measurements.rst:259 +msgid "disk.dev\\ ice.write\\ .bytes" msgstr "" -#: ../telemetry-measurements.rst:395 -msgid "disk.device.write.requests.rate" +#: ../telemetry-measurements.rst:263 +msgid "disk.dev\\ ice.write\\ .bytes .rate" msgstr "" -#: ../telemetry-measurements.rst:161 -msgid "disk.ephe\\ meral.size" +#: ../telemetry-measurements.rst:278 +msgid "network.\\ incoming.\\ packets.\\ rate" msgstr "" -#: ../telemetry-measurements.rst:304 -msgid "disk.iop\\ s" +#: ../telemetry-measurements.rst:283 +msgid "network.\\ outgoing.\\ packets.\\ rate" +msgstr "" + +#: ../telemetry-measurements.rst:288 +msgid "**Meters added or hypervisor support changed in the Kilo release**" +msgstr "" + +#: ../telemetry-measurements.rst:290 +msgid "" +"Volume of RAM used by the inst\\ ance from the amount of its allocated memory" +msgstr "" + +#: ../telemetry-measurements.rst:296 ../telemetry-measurements.rst:314 +#: ../telemetry-measurements.rst:318 ../telemetry-measurements.rst:324 +#: ../telemetry-measurements.rst:329 ../telemetry-measurements.rst:334 +#: ../telemetry-measurements.rst:340 +msgid "Libvirt" +msgstr "" + +#: ../telemetry-measurements.rst:296 +msgid "Volume of RAM u\\ sed by the inst\\ ance on the phy\\ sical machine" +msgstr "" + +#: ../telemetry-measurements.rst:296 +msgid "memory.r\\ esident" +msgstr "" + +#: ../telemetry-measurements.rst:301 +msgid "Average disk la\\ tency" +msgstr "" + +#: ../telemetry-measurements.rst:301 ../telemetry-measurements.rst:304 +#: ../telemetry-measurements.rst:307 ../telemetry-measurements.rst:311 +msgid "Hyper-V" msgstr "" #: ../telemetry-measurements.rst:301 msgid "disk.lat\\ ency" msgstr "" -#: ../telemetry-measurements.rst:389 -msgid "disk.read.bytes.rate" +#: ../telemetry-measurements.rst:301 ../telemetry-measurements.rst:307 +msgid "ms" msgstr "" -#: ../telemetry-measurements.rst:385 -msgid "disk.read.requests.rate" +#: ../telemetry-measurements.rst:304 +msgid "Average disk io\\ ps" msgstr "" -#: ../telemetry-measurements.rst:144 -msgid "disk.read\\ .bytes" +#: ../telemetry-measurements.rst:304 ../telemetry-measurements.rst:311 +msgid "coun\\ t/s" msgstr "" -#: ../telemetry-measurements.rst:147 ../telemetry-measurements.rst:221 -msgid "disk.read\\ .bytes.\\ rate" +#: ../telemetry-measurements.rst:304 +msgid "disk.iop\\ s" msgstr "" -#: ../telemetry-measurements.rst:130 -msgid "disk.read\\ .requests" +#: ../telemetry-measurements.rst:307 +msgid "Average disk la\\ tency per device" msgstr "" -#: ../telemetry-measurements.rst:133 -msgid "disk.read\\ .requests\\ .rate" +#: ../telemetry-measurements.rst:307 +msgid "disk.dev\\ ice.late\\ ncy" msgstr "" -#: ../telemetry-measurements.rst:158 -msgid "disk.root\\ .size" +#: ../telemetry-measurements.rst:311 +msgid "Average disk io\\ ps per device" +msgstr "" + +#: ../telemetry-measurements.rst:311 +msgid "disk.dev\\ ice.iops" +msgstr "" + +#: ../telemetry-measurements.rst:314 +msgid "The amount of d\\ isk that the in\\ stance can see" +msgstr "" + +#: ../telemetry-measurements.rst:314 +msgid "disk.cap\\ acity" +msgstr "" + +#: ../telemetry-measurements.rst:318 +msgid "" +"The amount of d\\ isk occupied by the instance o\\ n the host mach\\ ine" +msgstr "" + +#: ../telemetry-measurements.rst:318 +msgid "disk.all\\ ocation" +msgstr "" + +#: ../telemetry-measurements.rst:324 +msgid "The physical si\\ ze in bytes of the image conta\\ iner on the host" msgstr "" #: ../telemetry-measurements.rst:324 msgid "disk.usa\\ ge" msgstr "" -#: ../telemetry-measurements.rst:151 -msgid "disk.writ\\ e.bytes" +#: ../telemetry-measurements.rst:329 +msgid "The amount of d\\ isk per device that the instan\\ ce can see" msgstr "" -#: ../telemetry-measurements.rst:154 -msgid "disk.writ\\ e.bytes.\\ rate" +#: ../telemetry-measurements.rst:329 +msgid "disk.dev\\ ice.capa\\ city" msgstr "" -#: ../telemetry-measurements.rst:140 -msgid "disk.writ\\ e.request\\ s.rate" +#: ../telemetry-measurements.rst:334 +msgid "" +"The amount of d\\ isk per device occupied by the instance on th\\ e host " +"machine" msgstr "" -#: ../telemetry-measurements.rst:137 -msgid "disk.writ\\ e.requests" +#: ../telemetry-measurements.rst:334 +msgid "disk.dev\\ ice.allo\\ cation" msgstr "" -#: ../telemetry-measurements.rst:391 -msgid "disk.write.bytes.rate" +#: ../telemetry-measurements.rst:340 +msgid "" +"The physical si\\ ze in bytes of the image conta\\ iner on the hos\\ t per " +"device" +msgstr "" + +#: ../telemetry-measurements.rst:340 +msgid "disk.dev\\ ice.usag\\ e" +msgstr "" + +#: ../telemetry-measurements.rst:346 +msgid "**Meters deprecated in the Kilo release**" +msgstr "" + +#: ../telemetry-measurements.rst:353 +msgid "**Meters added in the Liberty release**" +msgstr "" + +#: ../telemetry-measurements.rst:355 +msgid "CPU time used s\\ ince previous d\\ atapoint" +msgstr "" + +#: ../telemetry-measurements.rst:355 +msgid "cpu.delta" +msgstr "" + +#: ../telemetry-measurements.rst:364 +msgid "" +"The ``instance:`` meter can be replaced by using extra parameters in " +"both the samples and statistics queries. Sample queries look like the " +"following::" +msgstr "" + +#: ../telemetry-measurements.rst:376 +msgid "" +"The Telemetry module supports to create new meters by using transformers. " +"For more details about transformers see :ref:`telemetry-transformers`. Among " +"the meters gathered from libvirt and Hyper-V there are a few ones which are " +"generated from other meters. The list of meters that are created by using " +"the ``rate_of_change`` transformer from the above table is the following:" +msgstr "" + +#: ../telemetry-measurements.rst:383 +msgid "cpu\\_util" +msgstr "" + +#: ../telemetry-measurements.rst:385 +msgid "disk.read.requests.rate" msgstr "" #: ../telemetry-measurements.rst:387 msgid "disk.write.requests.rate" msgstr "" -#: ../compute-flavors.rst:147 -msgid "disk\\_read\\_bytes\\_sec" +#: ../telemetry-measurements.rst:389 +msgid "disk.read.bytes.rate" msgstr "" -#: ../compute-flavors.rst:149 -msgid "disk\\_read\\_iops\\_sec" +#: ../telemetry-measurements.rst:391 +msgid "disk.write.bytes.rate" msgstr "" -#: ../compute-flavors.rst:155 -msgid "disk\\_total\\_bytes\\_sec" +#: ../telemetry-measurements.rst:393 +msgid "disk.device.read.requests.rate" msgstr "" -#: ../compute-flavors.rst:157 -msgid "disk\\_total\\_iops\\_sec" +#: ../telemetry-measurements.rst:395 +msgid "disk.device.write.requests.rate" msgstr "" -#: ../compute-flavors.rst:151 -msgid "disk\\_write\\_bytes\\_sec" +#: ../telemetry-measurements.rst:397 +msgid "disk.device.read.bytes.rate" msgstr "" -#: ../compute-flavors.rst:153 -msgid "disk\\_write\\_iops\\_sec" +#: ../telemetry-measurements.rst:399 +msgid "disk.device.write.bytes.rate" msgstr "" -#: ../compute-live-migration-usage.rst:170 -msgid "disk_bg" +#: ../telemetry-measurements.rst:401 +msgid "network.incoming.bytes.rate" msgstr "" -#: ../compute-system-admin.rst:75 -msgid "dispatches requests for new virtual machines to the correct node." +#: ../telemetry-measurements.rst:403 +msgid "network.outgoing.bytes.rate" msgstr "" -#: ../blockstorage-driver-filter-weighing.rst:192 -msgid "display\\_description" +#: ../telemetry-measurements.rst:405 +msgid "network.incoming.packets.rate" msgstr "" -#: ../blockstorage-driver-filter-weighing.rst:177 -msgid "display\\_name" +#: ../telemetry-measurements.rst:407 +msgid "network.outgoing.packets.rate" msgstr "" -#: ../compute-networking-nova.rst:202 +#: ../telemetry-measurements.rst:411 msgid "" -"dnsmasq also acts as a caching DNS server for instances. You can specify the " -"DNS server that dnsmasq uses by setting the ``dns_server`` configuration " -"option in :file:`/etc/nova/nova.conf`. This example configures dnsmasq to " -"use Google's public DNS server:" +"To enable the libvirt ``memory.usage`` support, you need to install libvirt " +"version 1.1.1+, QEMU version 1.5+, and you also need to prepare suitable " +"balloon driver in the image. It is applicable particularly for Windows " +"guests, most modern Linux distributions already have it built in. Telemetry " +"is not able to fetch the ``memory.usage`` samples without the image balloon " +"driver." msgstr "" -#: ../compute-networking-nova.rst:211 +#: ../telemetry-measurements.rst:418 msgid "" -"dnsmasq logs to syslog (typically :file:`/var/log/syslog` or :file:`/var/log/" -"messages`, depending on Linux distribution). Logs can be useful for " -"troubleshooting, especially in a situation where VM instances boot " -"successfully but are not reachable over the network." +"OpenStack Compute is capable of collecting ``CPU`` related meters from the " +"compute host machines. In order to use that you need to set the " +"``compute_monitors`` option to ``ComputeDriverCPUMonitor`` in the :file:" +"`nova.conf` configuration file. For further information see the Compute " +"configuration section in the `Compute chapter `__ of the " +"OpenStack Configuration Reference." msgstr "" -#: ../blockstorage-driver-filter-weighing.rst:143 -msgid "driver\\_version" +#: ../telemetry-measurements.rst:426 +msgid "" +"The following host machine related meters are collected for OpenStack " +"Compute:" msgstr "" -#: ../telemetry-data-retrieval.rst:553 -msgid "drop" +#: ../telemetry-measurements.rst:434 +msgid "CPU frequency" msgstr "" -# #-#-#-#-# compute-live-migration-usage.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -# #-#-#-#-# telemetry-alarms.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -#: ../compute-live-migration-usage.rst:116 -#: ../compute-live-migration-usage.rst:123 -#: ../compute-live-migration-usage.rst:130 -#: ../compute-live-migration-usage.rst:137 -#: ../compute-live-migration-usage.rst:144 -#: ../compute-live-migration-usage.rst:151 ../telemetry-alarms.rst:189 -msgid "enabled" -msgstr "" - -#: ../compute-remote-console-access.rst:180 -msgid "enabled = True" -msgstr "" - -#: ../blockstorage-driver-filter-weighing.rst:204 -msgid "encryption\\_key\\_id" -msgstr "" - -#: ../telemetry-measurements.rst:1326 -msgid "energy" -msgstr "" - -#: ../telemetry-measurements.rst:1024 -msgid "entry" -msgstr "" - -#: ../blockstorage-driver-filter-weighing.rst:107 -msgid "equality" -msgstr "" - -#: ../telemetry-events.rst:37 ../telemetry-events.rst:125 -msgid "event\\_type" -msgstr "" - -#: ../compute-flavors.rst:68 -msgid "extra_specs" +#: ../telemetry-measurements.rst:434 +msgid "MHz" msgstr "" +#: ../telemetry-measurements.rst:434 ../telemetry-measurements.rst:437 +#: ../telemetry-measurements.rst:440 ../telemetry-measurements.rst:443 +#: ../telemetry-measurements.rst:446 ../telemetry-measurements.rst:449 +#: ../telemetry-measurements.rst:452 ../telemetry-measurements.rst:455 +#: ../telemetry-measurements.rst:458 ../telemetry-measurements.rst:461 #: ../telemetry-measurements.rst:488 ../telemetry-measurements.rst:491 -msgid "fan sensor" +#: ../telemetry-measurements.rst:494 ../telemetry-measurements.rst:498 +#: ../telemetry-measurements.rst:501 ../telemetry-measurements.rst:1257 +#: ../telemetry-measurements.rst:1260 ../telemetry-measurements.rst:1263 +#: ../telemetry-measurements.rst:1266 ../telemetry-measurements.rst:1269 +#: ../telemetry-measurements.rst:1283 ../telemetry-measurements.rst:1288 +#: ../telemetry-measurements.rst:1292 ../telemetry-measurements.rst:1306 +#: ../telemetry-measurements.rst:1309 ../telemetry-measurements.rst:1312 +msgid "Notification" msgstr "" -#: ../telemetry-events.rst:144 -msgid "fields" -msgstr "" - -#: ../telemetry-data-retrieval.rst:514 -msgid "file" -msgstr "" - -#: ../telemetry-measurements.rst:1210 ../telemetry-measurements.rst:1224 -#: ../telemetry-measurements.rst:1229 -msgid "firewa\\ ll_pol\\ icy" -msgstr "" - -#: ../telemetry-measurements.rst:1234 ../telemetry-measurements.rst:1238 -#: ../telemetry-measurements.rst:1243 -msgid "firewa\\ ll_rule" -msgstr "" - -#: ../telemetry-measurements.rst:1206 ../telemetry-measurements.rst:1216 -#: ../telemetry-measurements.rst:1220 -msgid "firewall" -msgstr "" - -#: ../telemetry-measurements.rst:1206 ../telemetry-measurements.rst:1210 -#: ../telemetry-measurements.rst:1216 ../telemetry-measurements.rst:1220 -msgid "firewall ID" -msgstr "" - -#: ../compute-networking-nova.rst:313 -msgid "fixed_range_v6 = fd00::/48" -msgstr "" - -#: ../compute-live-migration-usage.rst:66 -msgid "flavor" -msgstr "" - -#: ../telemetry-data-collection.rst:82 -msgid "floatingip.create.end" -msgstr "" - -#: ../telemetry-data-collection.rst:86 -msgid "floatingip.exists" -msgstr "" - -#: ../telemetry-data-collection.rst:84 -msgid "floatingip.update.\\*" -msgstr "" - -#: ../telemetry-measurements.rst:1033 -msgid "flow" -msgstr "" - -#: ../compute_arch.rst:228 -msgid "fog" -msgstr "" - -#: ../compute-networking-nova.rst:315 -msgid "gateway_v6 = None" -msgstr "" - -#: ../telemetry-events.rst:43 -msgid "generated" -msgstr "" - -#: ../database.rst:174 -msgid "glance ID" -msgstr "" - -#: ../telemetry-measurements.rst:861 ../telemetry-measurements.rst:864 -#: ../telemetry-measurements.rst:867 -msgid "group" -msgstr "" - -#: ../telemetry-measurements.rst:861 ../telemetry-measurements.rst:864 -#: ../telemetry-measurements.rst:867 -msgid "group ID" -msgstr "" - -#: ../telemetry-measurements.rst:599 -msgid "hardware.cpu.load.\\ 10min" -msgstr "" - -#: ../telemetry-measurements.rst:593 -msgid "hardware.cpu.load.\\ 1min" -msgstr "" - -#: ../telemetry-measurements.rst:596 -msgid "hardware.cpu.load.\\ 5min" -msgstr "" - -#: ../telemetry-measurements.rst:602 -msgid "hardware.disk.size\\ .total" -msgstr "" - -#: ../telemetry-measurements.rst:605 -msgid "hardware.disk.size\\ .used" -msgstr "" - -#: ../telemetry-data-collection.rst:69 -msgid "hardware.ipmi.\\*" -msgstr "" - -#: ../telemetry-measurements.rst:488 ../telemetry-measurements.rst:491 -msgid "hardware.ipmi.fan" -msgstr "" - -#: ../telemetry-measurements.rst:577 -msgid "hardware.ipmi.node.inlet_temperature" -msgstr "" - -#: ../telemetry-measurements.rst:577 -msgid "hardware.ipmi.node.temperature" -msgstr "" - -#: ../telemetry-measurements.rst:547 -msgid "hardware.ipmi.node\\ .airflow" -msgstr "" - -#: ../telemetry-measurements.rst:557 -msgid "hardware.ipmi.node\\ .cpu_util" -msgstr "" - -#: ../telemetry-measurements.rst:552 -msgid "hardware.ipmi.node\\ .cups" -msgstr "" - -#: ../telemetry-measurements.rst:541 -msgid "hardware.ipmi.node\\ .inlet_temperature" -msgstr "" - -#: ../telemetry-measurements.rst:565 -msgid "hardware.ipmi.node\\ .io_util" -msgstr "" - -#: ../telemetry-measurements.rst:561 -msgid "hardware.ipmi.node\\ .mem_util" -msgstr "" - -#: ../telemetry-measurements.rst:544 -msgid "hardware.ipmi.node\\ .outlet_temperature" -msgstr "" - -#: ../telemetry-measurements.rst:532 -msgid "hardware.ipmi.node\\ .power" -msgstr "" - -#: ../telemetry-measurements.rst:535 -msgid "hardware.ipmi.node\\ .temperature" -msgstr "" - -#: ../telemetry-measurements.rst:498 -msgid "hardware.ipmi\\ .current" -msgstr "" - -#: ../telemetry-measurements.rst:494 -msgid "hardware.ipmi\\ .temperature" -msgstr "" - -#: ../telemetry-measurements.rst:501 -msgid "hardware.ipmi\\ .voltage" -msgstr "" - -#: ../telemetry-measurements.rst:614 -msgid "hardware.memory.bu\\ ffer" -msgstr "" - -#: ../telemetry-measurements.rst:617 -msgid "hardware.memory.ca\\ ched" -msgstr "" - -#: ../telemetry-measurements.rst:623 -msgid "hardware.memory.sw\\ ap.avail" -msgstr "" - -#: ../telemetry-measurements.rst:620 -msgid "hardware.memory.sw\\ ap.total" -msgstr "" - -#: ../telemetry-measurements.rst:608 -msgid "hardware.memory.to\\ tal" -msgstr "" - -#: ../telemetry-measurements.rst:611 -msgid "hardware.memory.us\\ ed" -msgstr "" - -#: ../telemetry-measurements.rst:626 -msgid "hardware.network.i\\ ncoming.bytes" -msgstr "" - -#: ../telemetry-measurements.rst:637 -msgid "hardware.network.i\\ p.incoming.datagra\\ ms" -msgstr "" - -#: ../telemetry-measurements.rst:641 -msgid "hardware.network.i\\ p.outgoing.datagra\\ ms" -msgstr "" - -#: ../telemetry-measurements.rst:630 -msgid "hardware.network.o\\ utgoing.bytes" -msgstr "" - -#: ../telemetry-measurements.rst:633 -msgid "hardware.network.o\\ utgoing.errors" -msgstr "" - -#: ../telemetry-measurements.rst:655 -msgid "hardware.system_st\\ ats.cpu.idle" -msgstr "" - -#: ../telemetry-measurements.rst:645 -msgid "hardware.system_st\\ ats.io.incoming.bl\\ ocks" -msgstr "" - -#: ../telemetry-measurements.rst:650 -msgid "hardware.system_st\\ ats.io.outgoing.bl\\ ocks" -msgstr "" - -#: ../telemetry-measurements.rst:1075 ../telemetry-measurements.rst:1121 -#: ../telemetry-measurements.rst:1126 -msgid "health\\ _monit\\ or" -msgstr "" - -#: ../blockstorage-driver-filter-weighing.rst:134 -msgid "host" +#: ../telemetry-measurements.rst:434 +msgid "compute.node.cpu.\\ frequency" msgstr "" #: ../telemetry-measurements.rst:434 ../telemetry-measurements.rst:437 @@ -23761,97 +22597,518 @@ msgstr "" msgid "host ID" msgstr "" -# #-#-#-#-# blockstorage-driver-filter-weighing.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -# #-#-#-#-# compute-live-migration-usage.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -#: ../blockstorage-driver-filter-weighing.rst:195 -#: ../compute-live-migration-usage.rst:68 -msgid "id" +#: ../telemetry-measurements.rst:437 +msgid "CPU kernel time" msgstr "" -#: ../telemetry-measurements.rst:849 -msgid "identity.authent\\ icate.failure" +#: ../telemetry-measurements.rst:437 +msgid "compute.node.cpu.\\ kernel.time" msgstr "" -#: ../telemetry-measurements.rst:846 -msgid "identity.authent\\ icate.pending" +#: ../telemetry-measurements.rst:440 +msgid "CPU idle time" msgstr "" -#: ../telemetry-measurements.rst:843 -msgid "identity.authent\\ icate.success" +#: ../telemetry-measurements.rst:440 +msgid "compute.node.cpu.\\ idle.time" msgstr "" -#: ../telemetry-measurements.rst:861 -msgid "identity.group.c\\ reated" +#: ../telemetry-measurements.rst:443 +msgid "CPU user mode time" msgstr "" -#: ../telemetry-measurements.rst:864 -msgid "identity.group.d\\ eleted" +#: ../telemetry-measurements.rst:443 +msgid "compute.node.cpu.\\ user.time" msgstr "" -#: ../telemetry-measurements.rst:867 -msgid "identity.group.u\\ pdated" +#: ../telemetry-measurements.rst:446 +msgid "CPU I/O wait time" msgstr "" -#: ../telemetry-measurements.rst:879 -msgid "identity.project\\ .created" +#: ../telemetry-measurements.rst:446 +msgid "compute.node.cpu.\\ iowait.time" msgstr "" -#: ../telemetry-measurements.rst:882 -msgid "identity.project\\ .deleted" +#: ../telemetry-measurements.rst:449 +msgid "CPU kernel percentage" msgstr "" -#: ../telemetry-measurements.rst:885 -msgid "identity.project\\ .updated" +#: ../telemetry-measurements.rst:449 +msgid "compute.node.cpu.\\ kernel.percent" msgstr "" -#: ../telemetry-measurements.rst:870 -msgid "identity.role.cr\\ eated" +#: ../telemetry-measurements.rst:452 +msgid "CPU idle percentage" msgstr "" -#: ../telemetry-measurements.rst:873 -msgid "identity.role.de\\ leted" +#: ../telemetry-measurements.rst:452 +msgid "compute.node.cpu.\\ idle.percent" msgstr "" -#: ../telemetry-measurements.rst:876 -msgid "identity.role.up\\ dated" +#: ../telemetry-measurements.rst:455 +msgid "CPU user mode percentage" msgstr "" -#: ../telemetry-measurements.rst:896 -msgid "identity.role_as\\ signment.created" +#: ../telemetry-measurements.rst:455 +msgid "compute.node.cpu.\\ user.percent" msgstr "" -#: ../telemetry-measurements.rst:900 -msgid "identity.role_as\\ signment.deleted" +#: ../telemetry-measurements.rst:458 +msgid "CPU I/O wait percentage" msgstr "" -#: ../telemetry-measurements.rst:888 -msgid "identity.trust.c\\ reated" +#: ../telemetry-measurements.rst:458 +msgid "compute.node.cpu.\\ iowait.percent" msgstr "" -#: ../telemetry-measurements.rst:891 -msgid "identity.trust.d\\ eleted" +#: ../telemetry-measurements.rst:461 +msgid "CPU utilisation" msgstr "" -#: ../telemetry-measurements.rst:852 -msgid "identity.user.cr\\ eated" +#: ../telemetry-measurements.rst:461 +msgid "compute.node.cpu.\\ percent" msgstr "" -#: ../telemetry-measurements.rst:855 -msgid "identity.user.de\\ leted" +#: ../telemetry-measurements.rst:469 +msgid "" +"Telemetry captures notifications that are emitted by the Bare metal service. " +"The source of the notifications are IPMI sensors that collect data from the " +"host machine." msgstr "" -#: ../telemetry-measurements.rst:858 -msgid "identity.user.up\\ dated" +#: ../telemetry-measurements.rst:475 +msgid "" +"The sensor data is not available in the Bare metal service by default. To " +"enable the meters and configure this module to emit notifications about the " +"measured values see the `Installation Guide `__ for the Bare metal service." msgstr "" -#: ../telemetry-measurements.rst:1184 ../telemetry-measurements.rst:1188 -#: ../telemetry-measurements.rst:1192 -msgid "ikepol\\ icy" +#: ../telemetry-measurements.rst:481 +msgid "The following meters are recorded for the Bare metal service:" msgstr "" -#: ../telemetry-measurements.rst:1184 ../telemetry-measurements.rst:1188 -#: ../telemetry-measurements.rst:1192 -msgid "ikepolicy ID" +#: ../telemetry-measurements.rst:486 ../telemetry-measurements.rst:530 +#: ../telemetry-measurements.rst:707 ../telemetry-measurements.rst:841 +#: ../telemetry-measurements.rst:1061 ../telemetry-measurements.rst:1139 +#: ../telemetry-measurements.rst:1204 ../telemetry-measurements.rst:1281 +msgid "**Meters added in the Juno release**" +msgstr "" + +#: ../telemetry-measurements.rst:488 ../telemetry-measurements.rst:491 +msgid "Fan rounds per minute (RPM)" +msgstr "" + +#: ../telemetry-measurements.rst:488 ../telemetry-measurements.rst:491 +msgid "RPM" +msgstr "" + +#: ../telemetry-measurements.rst:488 ../telemetry-measurements.rst:491 +msgid "fan sensor" +msgstr "" + +#: ../telemetry-measurements.rst:488 ../telemetry-measurements.rst:491 +msgid "hardware.ipmi.fan" +msgstr "" + +#: ../telemetry-measurements.rst:494 ../telemetry-measurements.rst:535 +#: ../telemetry-measurements.rst:541 ../telemetry-measurements.rst:544 +msgid "C" +msgstr "" + +#: ../telemetry-measurements.rst:494 +msgid "Temperate reading from sensor" +msgstr "" + +#: ../telemetry-measurements.rst:494 +msgid "hardware.ipmi\\ .temperature" +msgstr "" + +#: ../telemetry-measurements.rst:494 +msgid "temper\\ ature sensor" +msgstr "" + +#: ../telemetry-measurements.rst:498 +msgid "Current reading from sensor" +msgstr "" + +#: ../telemetry-measurements.rst:498 ../telemetry-measurements.rst:532 +#: ../telemetry-measurements.rst:1328 +msgid "W" +msgstr "" + +#: ../telemetry-measurements.rst:498 +msgid "current sensor" +msgstr "" + +#: ../telemetry-measurements.rst:498 +msgid "hardware.ipmi\\ .current" +msgstr "" + +#: ../telemetry-measurements.rst:501 +msgid "V" +msgstr "" + +#: ../telemetry-measurements.rst:501 +msgid "Voltage reading from sensor" +msgstr "" + +#: ../telemetry-measurements.rst:501 +msgid "hardware.ipmi\\ .voltage" +msgstr "" + +#: ../telemetry-measurements.rst:501 +msgid "voltage sensor" +msgstr "" + +#: ../telemetry-measurements.rst:506 +msgid "IPMI based meters" +msgstr "" + +#: ../telemetry-measurements.rst:507 +msgid "" +"Another way of gathering IPMI based data is to use IPMI sensors " +"independently from the Bare metal service's components. Same meters as :ref:" +"`telemetry-bare-metal-service` could be fetched except that origin is " +"``Pollster`` instead of ``Notification``." +msgstr "" + +#: ../telemetry-measurements.rst:512 +msgid "" +"You need to deploy the ceilometer-agent-ipmi on each IPMI-capable node in " +"order to poll local sensor data. For further information about the IPMI " +"agent see :ref:`telemetry-ipmi-agent`." +msgstr "" + +#: ../telemetry-measurements.rst:518 +msgid "" +"To avoid duplication of metering data and unnecessary load on the IPMI " +"interface, do not deploy the IPMI agent on nodes that are managed by the " +"Bare metal service and keep the ``conductor.send_sensor_data`` option set to " +"``False`` in the :file:`ironic.conf` configuration file." +msgstr "" + +#: ../telemetry-measurements.rst:524 +msgid "" +"Besides generic IPMI sensor data, the following Intel Node Manager meters " +"are recorded from capable platform:" +msgstr "" + +#: ../telemetry-measurements.rst:532 +msgid "Current power of the system" +msgstr "" + +#: ../telemetry-measurements.rst:532 +msgid "hardware.ipmi.node\\ .power" +msgstr "" + +#: ../telemetry-measurements.rst:535 +msgid "Current tempera\\ ture of the system" +msgstr "" + +#: ../telemetry-measurements.rst:535 +msgid "hardware.ipmi.node\\ .temperature" +msgstr "" + +#: ../telemetry-measurements.rst:539 ../telemetry-measurements.rst:591 +#: ../telemetry-measurements.rst:715 ../telemetry-measurements.rst:804 +#: ../telemetry-measurements.rst:894 ../telemetry-measurements.rst:1095 +#: ../telemetry-measurements.rst:1150 ../telemetry-measurements.rst:1214 +#: ../telemetry-measurements.rst:1304 +msgid "**Meters added in the Kilo release**" +msgstr "" + +#: ../telemetry-measurements.rst:541 +msgid "Inlet temperatu\\ re of the system" +msgstr "" + +#: ../telemetry-measurements.rst:541 +msgid "hardware.ipmi.node\\ .inlet_temperature" +msgstr "" + +#: ../telemetry-measurements.rst:544 +msgid "Outlet temperat\\ ure of the system" +msgstr "" + +#: ../telemetry-measurements.rst:544 +msgid "hardware.ipmi.node\\ .outlet_temperature" +msgstr "" + +#: ../telemetry-measurements.rst:547 +msgid "CFM" +msgstr "" + +#: ../telemetry-measurements.rst:547 +msgid "Volumetric airf\\ low of the syst\\ em, expressed as 1/10th of CFM" +msgstr "" + +#: ../telemetry-measurements.rst:547 +msgid "hardware.ipmi.node\\ .airflow" +msgstr "" + +#: ../telemetry-measurements.rst:552 +msgid "CUPS" +msgstr "" + +#: ../telemetry-measurements.rst:552 +msgid "CUPS(Compute Us\\ age Per Second) index data of the system" +msgstr "" + +#: ../telemetry-measurements.rst:552 +msgid "hardware.ipmi.node\\ .cups" +msgstr "" + +#: ../telemetry-measurements.rst:557 +msgid "CPU CUPS utiliz\\ ation of the system" +msgstr "" + +#: ../telemetry-measurements.rst:557 +msgid "hardware.ipmi.node\\ .cpu_util" +msgstr "" + +#: ../telemetry-measurements.rst:561 +msgid "Memory CUPS utilization of the system" +msgstr "" + +#: ../telemetry-measurements.rst:561 +msgid "hardware.ipmi.node\\ .mem_util" +msgstr "" + +#: ../telemetry-measurements.rst:565 +msgid "IO CUPS utilization of the system" +msgstr "" + +#: ../telemetry-measurements.rst:565 +msgid "hardware.ipmi.node\\ .io_util" +msgstr "" + +#: ../telemetry-measurements.rst:573 +msgid "Meters renamed in the Kilo release" +msgstr "" + +#: ../telemetry-measurements.rst:575 +msgid "**New Name**" +msgstr "" + +#: ../telemetry-measurements.rst:575 +msgid "**Original Name**" +msgstr "" + +#: ../telemetry-measurements.rst:577 +msgid "hardware.ipmi.node.inlet_temperature" +msgstr "" + +#: ../telemetry-measurements.rst:577 +msgid "hardware.ipmi.node.temperature" +msgstr "" + +#: ../telemetry-measurements.rst:581 +msgid "SNMP based meters" +msgstr "" + +#: ../telemetry-measurements.rst:582 +msgid "" +"Telemetry supports gathering SNMP based generic host meters. In order to be " +"able to collect this data you need to run smpd on each target host." +msgstr "" + +#: ../telemetry-measurements.rst:585 +msgid "" +"The following meters are available about the host machines by using SNMP:" +msgstr "" + +#: ../telemetry-measurements.rst:593 +msgid "CPU load in the past 1 minute" +msgstr "" + +#: ../telemetry-measurements.rst:593 +msgid "hardware.cpu.load.\\ 1min" +msgstr "" + +#: ../telemetry-measurements.rst:593 ../telemetry-measurements.rst:596 +#: ../telemetry-measurements.rst:599 +msgid "proc\\ ess" +msgstr "" + +#: ../telemetry-measurements.rst:596 +msgid "CPU load in the past 5 minutes" +msgstr "" + +#: ../telemetry-measurements.rst:596 +msgid "hardware.cpu.load.\\ 5min" +msgstr "" + +#: ../telemetry-measurements.rst:599 +msgid "CPU load in the past 10 minutes" +msgstr "" + +#: ../telemetry-measurements.rst:599 +msgid "hardware.cpu.load.\\ 10min" +msgstr "" + +#: ../telemetry-measurements.rst:602 ../telemetry-measurements.rst:605 +#: ../telemetry-measurements.rst:608 ../telemetry-measurements.rst:611 +#: ../telemetry-measurements.rst:614 ../telemetry-measurements.rst:617 +#: ../telemetry-measurements.rst:620 ../telemetry-measurements.rst:623 +msgid "KB" +msgstr "" + +#: ../telemetry-measurements.rst:602 +msgid "Total disk size" +msgstr "" + +#: ../telemetry-measurements.rst:602 +msgid "hardware.disk.size\\ .total" +msgstr "" + +#: ../telemetry-measurements.rst:605 +msgid "Used disk size" +msgstr "" + +#: ../telemetry-measurements.rst:605 +msgid "hardware.disk.size\\ .used" +msgstr "" + +#: ../telemetry-measurements.rst:608 +msgid "Total physical memory size" +msgstr "" + +#: ../telemetry-measurements.rst:608 +msgid "hardware.memory.to\\ tal" +msgstr "" + +#: ../telemetry-measurements.rst:611 +msgid "Used physical m\\ emory size" +msgstr "" + +#: ../telemetry-measurements.rst:611 +msgid "hardware.memory.us\\ ed" +msgstr "" + +#: ../telemetry-measurements.rst:614 +msgid "Physical memory buffer size" +msgstr "" + +#: ../telemetry-measurements.rst:614 +msgid "hardware.memory.bu\\ ffer" +msgstr "" + +#: ../telemetry-measurements.rst:617 +msgid "Cached physical memory size" +msgstr "" + +#: ../telemetry-measurements.rst:617 +msgid "hardware.memory.ca\\ ched" +msgstr "" + +#: ../telemetry-measurements.rst:620 +msgid "Total swap space size" +msgstr "" + +#: ../telemetry-measurements.rst:620 +msgid "hardware.memory.sw\\ ap.total" +msgstr "" + +#: ../telemetry-measurements.rst:623 +msgid "Available swap space size" +msgstr "" + +#: ../telemetry-measurements.rst:623 +msgid "hardware.memory.sw\\ ap.avail" +msgstr "" + +#: ../telemetry-measurements.rst:626 +msgid "Bytes received by network inte\\ rface" +msgstr "" + +#: ../telemetry-measurements.rst:626 +msgid "hardware.network.i\\ ncoming.bytes" +msgstr "" + +#: ../telemetry-measurements.rst:630 +msgid "Bytes sent by n\\ etwork interface" +msgstr "" + +#: ../telemetry-measurements.rst:630 +msgid "hardware.network.o\\ utgoing.bytes" +msgstr "" + +#: ../telemetry-measurements.rst:633 +msgid "Sending error o\\ f network inter\\ face" +msgstr "" + +#: ../telemetry-measurements.rst:633 +msgid "hardware.network.o\\ utgoing.errors" +msgstr "" + +#: ../telemetry-measurements.rst:633 +msgid "pack\\ et" +msgstr "" + +#: ../telemetry-measurements.rst:637 +msgid "Number of recei\\ ved datagrams" +msgstr "" + +#: ../telemetry-measurements.rst:637 ../telemetry-measurements.rst:641 +msgid "data\\ grams" +msgstr "" + +#: ../telemetry-measurements.rst:637 +msgid "hardware.network.i\\ p.incoming.datagra\\ ms" +msgstr "" + +#: ../telemetry-measurements.rst:641 +msgid "Number of sent datagrams" +msgstr "" + +#: ../telemetry-measurements.rst:641 +msgid "hardware.network.i\\ p.outgoing.datagra\\ ms" +msgstr "" + +#: ../telemetry-measurements.rst:645 +msgid "Aggregated numb\\ er of blocks re\\ ceived to block device" +msgstr "" + +#: ../telemetry-measurements.rst:645 ../telemetry-measurements.rst:650 +msgid "bloc\\ ks" +msgstr "" + +#: ../telemetry-measurements.rst:645 +msgid "hardware.system_st\\ ats.io.incoming.bl\\ ocks" +msgstr "" + +#: ../telemetry-measurements.rst:650 +msgid "Aggregated numb\\ er of blocks se\\ nt to block dev\\ ice" +msgstr "" + +#: ../telemetry-measurements.rst:650 +msgid "hardware.system_st\\ ats.io.outgoing.bl\\ ocks" +msgstr "" + +#: ../telemetry-measurements.rst:655 +msgid "CPU idle percen\\ tage" +msgstr "" + +#: ../telemetry-measurements.rst:655 +msgid "hardware.system_st\\ ats.cpu.idle" +msgstr "" + +#: ../telemetry-measurements.rst:661 +msgid "The following meters are collected for OpenStack Image service:" +msgstr "" + +#: ../telemetry-measurements.rst:668 +msgid "Existence of the image" +msgstr "" + +#: ../telemetry-measurements.rst:668 ../telemetry-measurements.rst:672 +#: ../telemetry-measurements.rst:953 ../telemetry-measurements.rst:1063 +#: ../telemetry-measurements.rst:1067 ../telemetry-measurements.rst:1071 +#: ../telemetry-measurements.rst:1075 ../telemetry-measurements.rst:1141 +#: ../telemetry-measurements.rst:1145 ../telemetry-measurements.rst:1170 +#: ../telemetry-measurements.rst:1184 ../telemetry-measurements.rst:1206 +#: ../telemetry-measurements.rst:1210 +msgid "Notifica\\ tion, Po\\ llster" msgstr "" #: ../telemetry-measurements.rst:668 ../telemetry-measurements.rst:672 @@ -23867,116 +23124,714 @@ msgstr "" msgid "image ID" msgstr "" -# #-#-#-#-# telemetry-data-collection.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -# #-#-#-#-# telemetry-measurements.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -#: ../telemetry-data-collection.rst:75 ../telemetry-measurements.rst:682 -msgid "image.delete" -msgstr "" - -#: ../telemetry-measurements.rst:685 -msgid "image.download" -msgstr "" - -#: ../telemetry-data-collection.rst:77 -msgid "image.send" -msgstr "" - -#: ../telemetry-measurements.rst:688 -msgid "image.serve" +#: ../telemetry-measurements.rst:672 +msgid "Size of the upl\\ oaded image" msgstr "" #: ../telemetry-measurements.rst:672 msgid "image.size" msgstr "" -# #-#-#-#-# telemetry-data-collection.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -# #-#-#-#-# telemetry-measurements.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -#: ../telemetry-data-collection.rst:71 ../telemetry-measurements.rst:676 -msgid "image.update" +#: ../telemetry-measurements.rst:676 ../telemetry-measurements.rst:679 +#: ../telemetry-measurements.rst:682 ../telemetry-measurements.rst:685 +#: ../telemetry-measurements.rst:688 ../telemetry-measurements.rst:701 +#: ../telemetry-measurements.rst:704 ../telemetry-measurements.rst:709 +#: ../telemetry-measurements.rst:712 ../telemetry-measurements.rst:717 +#: ../telemetry-measurements.rst:720 ../telemetry-measurements.rst:723 +#: ../telemetry-measurements.rst:727 ../telemetry-measurements.rst:730 +#: ../telemetry-measurements.rst:734 ../telemetry-measurements.rst:738 +#: ../telemetry-measurements.rst:741 ../telemetry-measurements.rst:843 +#: ../telemetry-measurements.rst:846 ../telemetry-measurements.rst:849 +#: ../telemetry-measurements.rst:852 ../telemetry-measurements.rst:855 +#: ../telemetry-measurements.rst:858 ../telemetry-measurements.rst:861 +#: ../telemetry-measurements.rst:864 ../telemetry-measurements.rst:867 +#: ../telemetry-measurements.rst:870 ../telemetry-measurements.rst:873 +#: ../telemetry-measurements.rst:876 ../telemetry-measurements.rst:879 +#: ../telemetry-measurements.rst:882 ../telemetry-measurements.rst:885 +#: ../telemetry-measurements.rst:888 ../telemetry-measurements.rst:891 +#: ../telemetry-measurements.rst:896 ../telemetry-measurements.rst:900 +#: ../telemetry-measurements.rst:914 ../telemetry-measurements.rst:917 +#: ../telemetry-measurements.rst:921 ../telemetry-measurements.rst:924 +#: ../telemetry-measurements.rst:927 ../telemetry-measurements.rst:931 +#: ../telemetry-measurements.rst:934 ../telemetry-measurements.rst:937 +#: ../telemetry-measurements.rst:940 ../telemetry-measurements.rst:943 +#: ../telemetry-measurements.rst:946 ../telemetry-measurements.rst:950 +#: ../telemetry-measurements.rst:957 ../telemetry-measurements.rst:960 +#: ../telemetry-measurements.rst:963 ../telemetry-measurements.rst:1097 +#: ../telemetry-measurements.rst:1101 ../telemetry-measurements.rst:1105 +#: ../telemetry-measurements.rst:1109 ../telemetry-measurements.rst:1113 +#: ../telemetry-measurements.rst:1117 ../telemetry-measurements.rst:1121 +#: ../telemetry-measurements.rst:1126 ../telemetry-measurements.rst:1152 +#: ../telemetry-measurements.rst:1156 ../telemetry-measurements.rst:1160 +#: ../telemetry-measurements.rst:1165 ../telemetry-measurements.rst:1174 +#: ../telemetry-measurements.rst:1179 ../telemetry-measurements.rst:1188 +#: ../telemetry-measurements.rst:1192 ../telemetry-measurements.rst:1216 +#: ../telemetry-measurements.rst:1220 ../telemetry-measurements.rst:1224 +#: ../telemetry-measurements.rst:1229 ../telemetry-measurements.rst:1234 +#: ../telemetry-measurements.rst:1238 ../telemetry-measurements.rst:1243 +msgid "Notifica\\ tion" msgstr "" -# #-#-#-#-# telemetry-data-collection.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -# #-#-#-#-# telemetry-measurements.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -#: ../telemetry-data-collection.rst:73 ../telemetry-measurements.rst:679 -msgid "image.upload" +#: ../telemetry-measurements.rst:676 +msgid "Number of updat\\ es on the image" msgstr "" -#: ../ts-eql-volume-size.rst:113 -msgid "image\\_from\\_volume1" +#: ../telemetry-measurements.rst:679 +msgid "Number of uploa\\ ds on the image" msgstr "" -#: ../telemetry-measurements.rst:1312 -msgid "index" +#: ../telemetry-measurements.rst:682 +msgid "Number of delet\\ es on the image" msgstr "" -#: ../telemetry-measurements.rst:200 ../telemetry-measurements.rst:205 -#: ../telemetry-measurements.rst:348 -msgid "ins\\ tance" +#: ../telemetry-measurements.rst:685 +msgid "Image is downlo\\ aded" msgstr "" -#: ../telemetry-measurements.rst:101 ../telemetry-measurements.rst:105 -msgid "inst\\ ance" +#: ../telemetry-measurements.rst:685 +msgid "image.download" msgstr "" -#: ../telemetry-measurements.rst:101 ../telemetry-measurements.rst:200 -msgid "instance" +#: ../telemetry-measurements.rst:688 +msgid "Image is served out" msgstr "" -#: ../telemetry-measurements.rst:101 ../telemetry-measurements.rst:105 -#: ../telemetry-measurements.rst:109 ../telemetry-measurements.rst:113 -#: ../telemetry-measurements.rst:119 ../telemetry-measurements.rst:122 -#: ../telemetry-measurements.rst:126 ../telemetry-measurements.rst:130 -#: ../telemetry-measurements.rst:133 ../telemetry-measurements.rst:137 -#: ../telemetry-measurements.rst:140 ../telemetry-measurements.rst:144 -#: ../telemetry-measurements.rst:147 ../telemetry-measurements.rst:151 -#: ../telemetry-measurements.rst:154 ../telemetry-measurements.rst:158 -#: ../telemetry-measurements.rst:161 ../telemetry-measurements.rst:200 -#: ../telemetry-measurements.rst:205 ../telemetry-measurements.rst:210 -#: ../telemetry-measurements.rst:216 ../telemetry-measurements.rst:221 -#: ../telemetry-measurements.rst:226 ../telemetry-measurements.rst:290 -#: ../telemetry-measurements.rst:296 ../telemetry-measurements.rst:301 -#: ../telemetry-measurements.rst:304 ../telemetry-measurements.rst:314 -#: ../telemetry-measurements.rst:318 ../telemetry-measurements.rst:324 -#: ../telemetry-measurements.rst:348 ../telemetry-measurements.rst:355 -msgid "instance ID" +#: ../telemetry-measurements.rst:688 +msgid "image.serve" msgstr "" -#: ../telemetry-measurements.rst:105 -msgid "instance:\\ " +#: ../telemetry-measurements.rst:694 +msgid "The following meters are collected for OpenStack Block Storage:" msgstr "" -#: ../telemetry-measurements.rst:205 ../telemetry-measurements.rst:348 -msgid "instance\\ :" +#: ../telemetry-measurements.rst:701 +msgid "Existence of the volume" msgstr "" -#: ../telemetry-alarms.rst:23 -msgid "insufficient data" +#: ../telemetry-measurements.rst:701 ../telemetry-measurements.rst:717 +#: ../telemetry-measurements.rst:720 ../telemetry-measurements.rst:723 +#: ../telemetry-measurements.rst:727 ../telemetry-measurements.rst:730 +#: ../telemetry-measurements.rst:734 +msgid "volume" msgstr "" -#: ../telemetry-alarms.rst:200 -msgid "insufficient-data-action" +#: ../telemetry-measurements.rst:701 ../telemetry-measurements.rst:704 +#: ../telemetry-measurements.rst:717 ../telemetry-measurements.rst:720 +#: ../telemetry-measurements.rst:723 ../telemetry-measurements.rst:727 +#: ../telemetry-measurements.rst:730 ../telemetry-measurements.rst:734 +msgid "volume ID" msgstr "" -#: ../telemetry-measurements.rst:164 ../telemetry-measurements.rst:168 -#: ../telemetry-measurements.rst:172 ../telemetry-measurements.rst:176 -#: ../telemetry-measurements.rst:180 ../telemetry-measurements.rst:184 -#: ../telemetry-measurements.rst:189 ../telemetry-measurements.rst:193 -#: ../telemetry-measurements.rst:268 ../telemetry-measurements.rst:273 -#: ../telemetry-measurements.rst:278 ../telemetry-measurements.rst:283 -#: ../telemetry-measurements.rst:626 ../telemetry-measurements.rst:630 -#: ../telemetry-measurements.rst:633 -msgid "interface ID" +#: ../telemetry-measurements.rst:704 +msgid "Size of the vol\\ ume" msgstr "" -#: ../networking_adv-config.rst:30 ../networking_adv-config.rst:36 -msgid "interface\\_driver ($NEUTRON\\_CONF\\_DIR/metering\\_agent.ini)" +#: ../telemetry-measurements.rst:704 +msgid "volume.size" msgstr "" -#: ../compute-live-migration-usage.rst:115 -#: ../compute-live-migration-usage.rst:122 -#: ../compute-live-migration-usage.rst:129 -#: ../compute-live-migration-usage.rst:150 -msgid "internal" +#: ../telemetry-measurements.rst:709 +msgid "Existence of the snapshot" +msgstr "" + +#: ../telemetry-measurements.rst:709 ../telemetry-measurements.rst:738 +#: ../telemetry-measurements.rst:741 +msgid "snapsh\\ ot" +msgstr "" + +#: ../telemetry-measurements.rst:709 +msgid "snapshot" +msgstr "" + +#: ../telemetry-measurements.rst:709 ../telemetry-measurements.rst:712 +#: ../telemetry-measurements.rst:738 ../telemetry-measurements.rst:741 +msgid "snapshot ID" +msgstr "" + +#: ../telemetry-measurements.rst:712 +msgid "Size of the sna\\ pshot" +msgstr "" + +#: ../telemetry-measurements.rst:712 +msgid "snapshot.size" +msgstr "" + +#: ../telemetry-measurements.rst:717 +msgid "Creation of the volume" +msgstr "" + +#: ../telemetry-measurements.rst:717 +msgid "volume.create.(sta\\ rt|end)" +msgstr "" + +#: ../telemetry-measurements.rst:720 +msgid "Deletion of the volume" +msgstr "" + +#: ../telemetry-measurements.rst:720 +msgid "volume.delete.(sta\\ rt|end)" +msgstr "" + +#: ../telemetry-measurements.rst:723 +msgid "Update the name or description of the volume" +msgstr "" + +#: ../telemetry-measurements.rst:723 +msgid "volume.update.(sta\\ rt|end)" +msgstr "" + +#: ../telemetry-measurements.rst:727 +msgid "Update the size of the volume" +msgstr "" + +#: ../telemetry-measurements.rst:727 +msgid "volume.resize.(sta\\ rt|end)" +msgstr "" + +#: ../telemetry-measurements.rst:730 +msgid "Attaching the v\\ olume to an ins\\ tance" +msgstr "" + +#: ../telemetry-measurements.rst:730 +msgid "volume.attach.(sta\\ rt|end)" +msgstr "" + +#: ../telemetry-measurements.rst:734 +msgid "Detaching the v\\ olume from an i\\ nstance" +msgstr "" + +#: ../telemetry-measurements.rst:734 +msgid "volume.detach.(sta\\ rt|end)" +msgstr "" + +#: ../telemetry-measurements.rst:738 +msgid "Creation of the snapshot" +msgstr "" + +#: ../telemetry-measurements.rst:738 +msgid "snapshot.create.(s\\ tart|end)" +msgstr "" + +#: ../telemetry-measurements.rst:741 +msgid "Deletion of the snapshot" +msgstr "" + +#: ../telemetry-measurements.rst:741 +msgid "snapshot.delete.(s\\ tart|end)" +msgstr "" + +#: ../telemetry-measurements.rst:749 +msgid "The following meters are collected for OpenStack Object Storage:" +msgstr "" + +#: ../telemetry-measurements.rst:756 +msgid "Number of objec\\ ts" +msgstr "" + +#: ../telemetry-measurements.rst:756 ../telemetry-measurements.rst:776 +#: ../telemetry-measurements.rst:806 ../telemetry-measurements.rst:819 +msgid "object" +msgstr "" + +#: ../telemetry-measurements.rst:756 ../telemetry-measurements.rst:759 +#: ../telemetry-measurements.rst:762 ../telemetry-measurements.rst:765 +#: ../telemetry-measurements.rst:768 ../telemetry-measurements.rst:771 +#: ../telemetry-measurements.rst:806 ../telemetry-measurements.rst:808 +#: ../telemetry-measurements.rst:811 ../telemetry-measurements.rst:814 +msgid "storage ID" +msgstr "" + +#: ../telemetry-measurements.rst:756 +msgid "storage.objects" +msgstr "" + +#: ../telemetry-measurements.rst:759 ../telemetry-measurements.rst:808 +msgid "Total size of s\\ tored objects" +msgstr "" + +#: ../telemetry-measurements.rst:759 +msgid "storage.objects.si\\ ze" +msgstr "" + +#: ../telemetry-measurements.rst:762 ../telemetry-measurements.rst:811 +msgid "Number of conta\\ iners" +msgstr "" + +#: ../telemetry-measurements.rst:762 +msgid "conta\\ iner" +msgstr "" + +#: ../telemetry-measurements.rst:762 +msgid "storage.objects.co\\ ntainers" +msgstr "" + +#: ../telemetry-measurements.rst:765 +msgid "Number of incom\\ ing bytes" +msgstr "" + +#: ../telemetry-measurements.rst:765 +msgid "storage.objects.in\\ coming.bytes" +msgstr "" + +#: ../telemetry-measurements.rst:768 +msgid "Number of outgo\\ ing bytes" +msgstr "" + +#: ../telemetry-measurements.rst:768 +msgid "storage.objects.ou\\ tgoing.bytes" +msgstr "" + +#: ../telemetry-measurements.rst:771 +msgid "Number of API r\\ equests against OpenStack Obje\\ ct Storage" +msgstr "" + +#: ../telemetry-measurements.rst:771 +msgid "requ\\ est" +msgstr "" + +#: ../telemetry-measurements.rst:771 +msgid "storage.api.request" +msgstr "" + +#: ../telemetry-measurements.rst:776 ../telemetry-measurements.rst:819 +msgid "Number of objec\\ ts in container" +msgstr "" + +#: ../telemetry-measurements.rst:776 ../telemetry-measurements.rst:779 +#: ../telemetry-measurements.rst:819 ../telemetry-measurements.rst:822 +msgid "storage ID\\ /container" +msgstr "" + +#: ../telemetry-measurements.rst:776 +msgid "storage.containers\\ .objects" +msgstr "" + +#: ../telemetry-measurements.rst:779 +msgid "Total size of s\\ tored objects i\\ n container" +msgstr "" + +#: ../telemetry-measurements.rst:779 +msgid "storage.containers\\ .objects.size" +msgstr "" + +#: ../telemetry-measurements.rst:785 +msgid "Ceph Object Storage" +msgstr "" + +#: ../telemetry-measurements.rst:786 +msgid "" +"In order to gather meters from Ceph, you have to install and configure the " +"Ceph Object Gateway (radosgw) as it is described in the `Installation Manual " +"`__. You have to enable `usage " +"logging `__ in " +"order to get the related meters from Ceph. You will also need an ``admin`` " +"user with ``users``, ``buckets``, ``metadata`` and ``usage`` ``caps`` " +"configured." +msgstr "" + +#: ../telemetry-measurements.rst:794 +msgid "" +"In order to access Ceph from Telemetry, you need to specify a ``service " +"group`` for ``radosgw`` in the ``ceilometer.conf`` configuration file along " +"with ``access_key`` and ``secret_key`` of the ``admin`` user mentioned above." +msgstr "" + +#: ../telemetry-measurements.rst:799 +msgid "The following meters are collected for Ceph Object Storage:" +msgstr "" + +#: ../telemetry-measurements.rst:806 +msgid "Number of objects" +msgstr "" + +#: ../telemetry-measurements.rst:806 +msgid "radosgw.objects" +msgstr "" + +#: ../telemetry-measurements.rst:808 +msgid "radosgw.objects.\\ size" +msgstr "" + +#: ../telemetry-measurements.rst:811 +msgid "contai\\ ner" +msgstr "" + +#: ../telemetry-measurements.rst:811 +msgid "radosgw.objects.\\ containers" +msgstr "" + +#: ../telemetry-measurements.rst:814 +msgid "Number of API r\\ equests against Ceph Object Ga\\ teway (radosgw)" +msgstr "" + +#: ../telemetry-measurements.rst:814 +msgid "radosgw.api.requ\\ est" +msgstr "" + +#: ../telemetry-measurements.rst:814 +msgid "request" +msgstr "" + +#: ../telemetry-measurements.rst:819 +msgid "radosgw.containe\\ rs.objects" +msgstr "" + +#: ../telemetry-measurements.rst:822 +msgid "Total size of s\\ tored objects in container" +msgstr "" + +#: ../telemetry-measurements.rst:822 +msgid "radosgw.containe\\ rs.objects.size" +msgstr "" + +#: ../telemetry-measurements.rst:829 +msgid "" +"The ``usage`` related information may not be updated right after an upload " +"or download, because the Ceph Object Gateway needs time to update the usage " +"properties. For instance, the default configuration needs approximately 30 " +"minutes to generate the usage logs." +msgstr "" + +#: ../telemetry-measurements.rst:835 +msgid "OpenStack Identity" +msgstr "" + +#: ../telemetry-measurements.rst:836 +msgid "The following meters are collected for OpenStack Identity:" +msgstr "" + +#: ../telemetry-measurements.rst:843 +msgid "User successful\\ ly authenticated" +msgstr "" + +#: ../telemetry-measurements.rst:843 +msgid "identity.authent\\ icate.success" +msgstr "" + +#: ../telemetry-measurements.rst:843 ../telemetry-measurements.rst:846 +#: ../telemetry-measurements.rst:849 ../telemetry-measurements.rst:852 +#: ../telemetry-measurements.rst:855 ../telemetry-measurements.rst:858 +msgid "user" +msgstr "" + +#: ../telemetry-measurements.rst:843 ../telemetry-measurements.rst:846 +#: ../telemetry-measurements.rst:849 ../telemetry-measurements.rst:852 +#: ../telemetry-measurements.rst:855 ../telemetry-measurements.rst:858 +msgid "user ID" +msgstr "" + +#: ../telemetry-measurements.rst:846 +msgid "User pending au\\ thentication" +msgstr "" + +#: ../telemetry-measurements.rst:846 +msgid "identity.authent\\ icate.pending" +msgstr "" + +#: ../telemetry-measurements.rst:849 +msgid "User failed to authenticate" +msgstr "" + +#: ../telemetry-measurements.rst:849 +msgid "identity.authent\\ icate.failure" +msgstr "" + +#: ../telemetry-measurements.rst:852 +msgid "User is created" +msgstr "" + +#: ../telemetry-measurements.rst:852 +msgid "identity.user.cr\\ eated" +msgstr "" + +#: ../telemetry-measurements.rst:855 +msgid "User is deleted" +msgstr "" + +#: ../telemetry-measurements.rst:855 +msgid "identity.user.de\\ leted" +msgstr "" + +#: ../telemetry-measurements.rst:858 +msgid "User is updated" +msgstr "" + +#: ../telemetry-measurements.rst:858 +msgid "identity.user.up\\ dated" +msgstr "" + +#: ../telemetry-measurements.rst:861 +msgid "Group is created" +msgstr "" + +#: ../telemetry-measurements.rst:861 ../telemetry-measurements.rst:864 +#: ../telemetry-measurements.rst:867 +msgid "group" +msgstr "" + +#: ../telemetry-measurements.rst:861 ../telemetry-measurements.rst:864 +#: ../telemetry-measurements.rst:867 +msgid "group ID" +msgstr "" + +#: ../telemetry-measurements.rst:861 +msgid "identity.group.c\\ reated" +msgstr "" + +#: ../telemetry-measurements.rst:864 +msgid "Group is deleted" +msgstr "" + +#: ../telemetry-measurements.rst:864 +msgid "identity.group.d\\ eleted" +msgstr "" + +#: ../telemetry-measurements.rst:867 +msgid "Group is updated" +msgstr "" + +#: ../telemetry-measurements.rst:867 +msgid "identity.group.u\\ pdated" +msgstr "" + +#: ../telemetry-measurements.rst:870 +msgid "Role is created" +msgstr "" + +#: ../telemetry-measurements.rst:870 +msgid "identity.role.cr\\ eated" +msgstr "" + +#: ../telemetry-measurements.rst:870 ../telemetry-measurements.rst:873 +#: ../telemetry-measurements.rst:876 +msgid "role" +msgstr "" + +#: ../telemetry-measurements.rst:870 ../telemetry-measurements.rst:873 +#: ../telemetry-measurements.rst:876 ../telemetry-measurements.rst:896 +#: ../telemetry-measurements.rst:900 +msgid "role ID" +msgstr "" + +#: ../telemetry-measurements.rst:873 +msgid "Role is deleted" +msgstr "" + +#: ../telemetry-measurements.rst:873 +msgid "identity.role.de\\ leted" +msgstr "" + +#: ../telemetry-measurements.rst:876 +msgid "Role is updated" +msgstr "" + +#: ../telemetry-measurements.rst:876 +msgid "identity.role.up\\ dated" +msgstr "" + +#: ../telemetry-measurements.rst:879 +msgid "Project is crea\\ ted" +msgstr "" + +#: ../telemetry-measurements.rst:879 +msgid "identity.project\\ .created" +msgstr "" + +#: ../telemetry-measurements.rst:879 ../telemetry-measurements.rst:882 +#: ../telemetry-measurements.rst:885 +msgid "project" +msgstr "" + +#: ../telemetry-measurements.rst:879 ../telemetry-measurements.rst:882 +#: ../telemetry-measurements.rst:885 +msgid "project ID" +msgstr "" + +#: ../telemetry-measurements.rst:882 +msgid "Project is dele\\ ted" +msgstr "" + +#: ../telemetry-measurements.rst:882 +msgid "identity.project\\ .deleted" +msgstr "" + +#: ../telemetry-measurements.rst:885 +msgid "Project is upda\\ ted" +msgstr "" + +#: ../telemetry-measurements.rst:885 +msgid "identity.project\\ .updated" +msgstr "" + +#: ../telemetry-measurements.rst:888 +msgid "Trust is created" +msgstr "" + +#: ../telemetry-measurements.rst:888 +msgid "identity.trust.c\\ reated" +msgstr "" + +#: ../telemetry-measurements.rst:888 ../telemetry-measurements.rst:891 +msgid "trust" +msgstr "" + +#: ../telemetry-measurements.rst:888 ../telemetry-measurements.rst:891 +msgid "trust ID" +msgstr "" + +#: ../telemetry-measurements.rst:891 +msgid "Trust is deleted" +msgstr "" + +#: ../telemetry-measurements.rst:891 +msgid "identity.trust.d\\ eleted" +msgstr "" + +#: ../telemetry-measurements.rst:896 +msgid "Role is added to an actor on a target" +msgstr "" + +#: ../telemetry-measurements.rst:896 +msgid "identity.role_as\\ signment.created" +msgstr "" + +#: ../telemetry-measurements.rst:896 ../telemetry-measurements.rst:900 +msgid "role_a\\ ssignm\\ ent" +msgstr "" + +#: ../telemetry-measurements.rst:900 +msgid "Role is removed from an actor on a target" +msgstr "" + +#: ../telemetry-measurements.rst:900 +msgid "identity.role_as\\ signment.deleted" +msgstr "" + +#: ../telemetry-measurements.rst:907 +msgid "The following meters are collected for OpenStack Networking:" +msgstr "" + +#: ../telemetry-measurements.rst:914 +msgid "Existence of ne\\ twork" +msgstr "" + +#: ../telemetry-measurements.rst:914 ../telemetry-measurements.rst:917 +#: ../telemetry-measurements.rst:921 +msgid "networ\\ k" +msgstr "" + +#: ../telemetry-measurements.rst:914 +msgid "network" +msgstr "" + +#: ../telemetry-measurements.rst:914 ../telemetry-measurements.rst:917 +#: ../telemetry-measurements.rst:921 +msgid "network ID" +msgstr "" + +#: ../telemetry-measurements.rst:917 +msgid "Creation reques\\ ts for this net\\ work" +msgstr "" + +#: ../telemetry-measurements.rst:917 +msgid "network.create" +msgstr "" + +#: ../telemetry-measurements.rst:921 +msgid "Update requests for this network" +msgstr "" + +#: ../telemetry-measurements.rst:921 +msgid "network.update" +msgstr "" + +#: ../telemetry-measurements.rst:924 +msgid "Existence of su\\ bnet" +msgstr "" + +#: ../telemetry-measurements.rst:924 ../telemetry-measurements.rst:927 +#: ../telemetry-measurements.rst:931 +msgid "subnet" +msgstr "" + +#: ../telemetry-measurements.rst:924 ../telemetry-measurements.rst:927 +#: ../telemetry-measurements.rst:931 +msgid "subnet ID" +msgstr "" + +#: ../telemetry-measurements.rst:927 +msgid "Creation reques\\ ts for this sub\\ net" +msgstr "" + +#: ../telemetry-measurements.rst:927 +msgid "subnet.create" +msgstr "" + +#: ../telemetry-measurements.rst:931 +msgid "Update requests for this subnet" +msgstr "" + +#: ../telemetry-measurements.rst:931 +msgid "subnet.update" +msgstr "" + +#: ../telemetry-measurements.rst:934 ../telemetry-measurements.rst:980 +msgid "Existence of po\\ rt" +msgstr "" + +#: ../telemetry-measurements.rst:934 ../telemetry-measurements.rst:937 +#: ../telemetry-measurements.rst:940 +msgid "port ID" +msgstr "" + +#: ../telemetry-measurements.rst:937 +msgid "Creation reques\\ ts for this port" +msgstr "" + +#: ../telemetry-measurements.rst:937 +msgid "port.create" +msgstr "" + +#: ../telemetry-measurements.rst:940 +msgid "Update requests for this port" +msgstr "" + +#: ../telemetry-measurements.rst:940 +msgid "port.update" +msgstr "" + +#: ../telemetry-measurements.rst:943 +msgid "Existence of ro\\ uter" +msgstr "" + +#: ../telemetry-measurements.rst:943 ../telemetry-measurements.rst:946 +#: ../telemetry-measurements.rst:950 +msgid "router" +msgstr "" + +#: ../telemetry-measurements.rst:943 ../telemetry-measurements.rst:946 +#: ../telemetry-measurements.rst:950 +msgid "router ID" +msgstr "" + +#: ../telemetry-measurements.rst:946 +msgid "Creation reques\\ ts for this rou\\ ter" +msgstr "" + +#: ../telemetry-measurements.rst:946 +msgid "router.create" +msgstr "" + +#: ../telemetry-measurements.rst:950 +msgid "Update requests for this router" +msgstr "" + +#: ../telemetry-measurements.rst:950 +msgid "router.update" +msgstr "" + +#: ../telemetry-measurements.rst:953 +msgid "Existence of IP" msgstr "" #: ../telemetry-measurements.rst:953 ../telemetry-measurements.rst:957 @@ -23993,1150 +23848,44 @@ msgstr "" msgid "ip.floating" msgstr "" +#: ../telemetry-measurements.rst:957 +msgid "Creation reques\\ ts for this IP" +msgstr "" + #: ../telemetry-measurements.rst:957 msgid "ip.floating.cr\\ eate" msgstr "" +#: ../telemetry-measurements.rst:960 +msgid "Update requests for this IP" +msgstr "" + #: ../telemetry-measurements.rst:960 msgid "ip.floating.up\\ date" msgstr "" -#: ../telemetry-measurements.rst:1145 ../telemetry-measurements.rst:1160 -#: ../telemetry-measurements.rst:1165 -msgid "ipsec\\_\\ site\\_c\\ onnect\\ ion" +#: ../telemetry-measurements.rst:963 +msgid "Bytes through t\\ his l3 metering label" msgstr "" -#: ../telemetry-measurements.rst:1170 ../telemetry-measurements.rst:1174 -#: ../telemetry-measurements.rst:1179 -msgid "ipsecp\\ olicy" -msgstr "" - -#: ../telemetry-measurements.rst:1170 ../telemetry-measurements.rst:1174 -#: ../telemetry-measurements.rst:1179 -msgid "ipsecpolicy ID" -msgstr "" - -#: ../compute-networking-nova.rst:317 -msgid "ipv6_backend = rfc2462" -msgstr "" - -#: ../telemetry-measurements.rst:1326 -msgid "kWh" -msgstr "" - -#: ../telemetry-data-retrieval.rst:527 -msgid "kafka" -msgstr "" - -#: ../identity_concepts.rst:313 -msgid "keystone Web Server Gateway Interface (WSGI) service" -msgstr "" - -#: ../identity_concepts.rst:322 -msgid "keystone-all" -msgstr "" - -#: ../telemetry-data-collection.rst:112 -msgid "l3.meter" +#: ../telemetry-measurements.rst:963 +msgid "bandwidth" msgstr "" #: ../telemetry-measurements.rst:963 msgid "label ID" msgstr "" -#: ../compute-configuring-migrations.rst:227 -msgid "libvirtd TCP socket, with GSSAPI/Kerberos for auth+data encryption" +#: ../telemetry-measurements.rst:969 +msgid "SDN controllers" msgstr "" -#: ../compute-configuring-migrations.rst:232 -msgid "" -"libvirtd TCP socket, with TLS for encryption and Kerberos for authentication" +#: ../telemetry-measurements.rst:970 +msgid "The following meters are collected for SDN:" msgstr "" -#: ../compute-configuring-migrations.rst:229 -msgid "" -"libvirtd TCP socket, with TLS for encryption and x509 client certs for " -"authentication" -msgstr "" - -#: ../blockstorage-driver-filter-weighing.rst:105 -msgid "logic" -msgstr "" - -#: ../compute-live-migration-usage.rst:86 -msgid "m1.tiny" -msgstr "" - -#: ../telemetry-measurements.rst:1306 -msgid "magnetodb.table.\\ create" -msgstr "" - -#: ../telemetry-measurements.rst:1309 -msgid "magnetodb.table\\ .delete" -msgstr "" - -#: ../telemetry-measurements.rst:1312 -msgid "magnetodb.table\\ .index.count" -msgstr "" - -#: ../compute-system-admin.rst:45 -msgid "manages certificates." -msgstr "" - -#: ../compute-system-admin.rst:57 -msgid "manages console authentication." -msgstr "" - -#: ../compute-system-admin.rst:67 -msgid "" -"manages floating and fixed IPs, DHCP, bridging and VLANs. Loads a Service " -"object which exposes the public methods on one of the subclasses of " -"NetworkManager. Different networking strategies are available by changing " -"the ``network_manager`` configuration option to ``FlatManager``, " -"``FlatDHCPManager``, or ``VLANManager`` (defaults to ``VLANManager`` if " -"nothing is specified)." -msgstr "" - -#: ../compute-system-admin.rst:48 -msgid "" -"manages virtual machines. Loads a Service object, and exposes the public " -"methods on ComputeManager through a Remote Procedure Call (RPC)." -msgstr "" - -#: ../blockstorage-driver-filter-weighing.rst:113 -msgid "math helper functions" -msgstr "" - -#: ../telemetry-measurements.rst:1071 ../telemetry-measurements.rst:1113 -#: ../telemetry-measurements.rst:1117 -msgid "member" -msgstr "" - -#: ../telemetry-measurements.rst:1071 ../telemetry-measurements.rst:1113 -#: ../telemetry-measurements.rst:1117 -msgid "member ID" -msgstr "" - -#: ../telemetry-measurements.rst:109 -msgid "memory" -msgstr "" - -#: ../telemetry-measurements.rst:113 ../telemetry-measurements.rst:210 -#: ../telemetry-measurements.rst:290 -msgid "memory.\\ usage" -msgstr "" - -#: ../telemetry-measurements.rst:296 -msgid "memory.r\\ esident" -msgstr "" - -#: ../compute-live-migration-usage.rst:169 -msgid "memory_mb" -msgstr "" - -#: ../telemetry-events.rst:40 -msgid "message\\_id" -msgstr "" - -#: ../blockstorage-driver-filter-weighing.rst:222 -msgid "metadata" -msgstr "" - -#: ../compute-networking-nova.rst:511 -msgid "metadata_cache_expiration = 15" -msgstr "" - -#: ../compute-networking-nova.rst:517 -msgid "metadata_host = $my_ip" -msgstr "" - -#: ../compute-networking-nova.rst:519 -msgid "metadata_listen = 0.0.0.0" -msgstr "" - -#: ../compute-networking-nova.rst:521 -msgid "metadata_listen_port = 8775" -msgstr "" - -#: ../compute-networking-nova.rst:523 -msgid "metadata_manager = nova.api.manager.MetadataManager" -msgstr "" - -#: ../compute-networking-nova.rst:525 -msgid "metadata_port = 8775" -msgstr "" - -#: ../compute-networking-nova.rst:527 -msgid "metadata_workers = None" -msgstr "" - -#: ../telemetry-alarms.rst:241 -msgid "" -"meters have not yet been gathered about this instance over the evaluation " -"window into the recent past (for example a brand-new instance)" -msgstr "" - -#: ../keystone_configure_with_SSL.rst:20 -msgid "middleware.pem" -msgstr "" - -#: ../database.rst:168 -msgid "mongodb" -msgstr "" - -#: ../telemetry-measurements.rst:1075 ../telemetry-measurements.rst:1121 -#: ../telemetry-measurements.rst:1126 -msgid "monitor ID" -msgstr "" - -#: ../telemetry-measurements.rst:301 ../telemetry-measurements.rst:307 -msgid "ms" -msgstr "" - -#: ../database.rst:166 -msgid "mysql" -msgstr "" - -# #-#-#-#-# compute-live-migration-usage.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -# #-#-#-#-# database.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -# #-#-#-#-# telemetry-data-collection.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -#: ../compute-live-migration-usage.rst:71 ../database.rst:112 -#: ../telemetry-data-collection.rst:651 -msgid "name" -msgstr "" - -#: ../telemetry-measurements.rst:914 ../telemetry-measurements.rst:917 -#: ../telemetry-measurements.rst:921 -msgid "networ\\ k" -msgstr "" - -#: ../telemetry-measurements.rst:914 -msgid "network" -msgstr "" - -#: ../telemetry-measurements.rst:914 ../telemetry-measurements.rst:917 -#: ../telemetry-measurements.rst:921 -msgid "network ID" -msgstr "" - -#: ../telemetry-measurements.rst:164 -msgid "network.\\ incoming.\\ bytes" -msgstr "" - -#: ../telemetry-measurements.rst:168 ../telemetry-measurements.rst:268 -msgid "network.\\ incoming.\\ bytes.rate" -msgstr "" - -#: ../telemetry-measurements.rst:278 -msgid "network.\\ incoming.\\ packets.\\ rate" -msgstr "" - -#: ../telemetry-measurements.rst:184 -msgid "network.\\ incoming\\ .packets\\ .rate" -msgstr "" - -#: ../telemetry-measurements.rst:180 -msgid "network.\\ incoming| .packets" -msgstr "" - -#: ../telemetry-measurements.rst:176 ../telemetry-measurements.rst:273 -msgid "network.\\ outgoing.\\ bytes.rate" -msgstr "" - -#: ../telemetry-measurements.rst:283 -msgid "network.\\ outgoing.\\ packets.\\ rate" -msgstr "" - -#: ../telemetry-measurements.rst:172 -msgid "network.\\ outgoing\\ .bytes" -msgstr "" - -#: ../telemetry-measurements.rst:193 -msgid "network.\\ outgoing\\ .packets\\ .rate" -msgstr "" - -#: ../telemetry-measurements.rst:189 -msgid "network.\\ outpoing\\ .packets" -msgstr "" - -#: ../telemetry-measurements.rst:917 -msgid "network.create" -msgstr "" - -#: ../telemetry-data-collection.rst:88 -msgid "network.create.end" -msgstr "" - -#: ../telemetry-data-collection.rst:92 -msgid "network.exists" -msgstr "" - -#: ../telemetry-measurements.rst:401 -msgid "network.incoming.bytes.rate" -msgstr "" - -#: ../telemetry-measurements.rst:405 -msgid "network.incoming.packets.rate" -msgstr "" - -#: ../telemetry-measurements.rst:403 -msgid "network.outgoing.bytes.rate" -msgstr "" - -#: ../telemetry-measurements.rst:407 -msgid "network.outgoing.packets.rate" -msgstr "" - -#: ../telemetry-measurements.rst:1216 -msgid "network.serv\\ ices.firewal\\ l.create" -msgstr "" - -#: ../telemetry-measurements.rst:1210 -msgid "network.serv\\ ices.firewal\\ l.policy" -msgstr "" - -#: ../telemetry-measurements.rst:1224 -msgid "network.serv\\ ices.firewal\\ l.policy.cre\\ ate" -msgstr "" - -#: ../telemetry-measurements.rst:1229 -msgid "network.serv\\ ices.firewal\\ l.policy.upd\\ ate" -msgstr "" - -#: ../telemetry-measurements.rst:1234 -msgid "network.serv\\ ices.firewal\\ l.rule" -msgstr "" - -#: ../telemetry-measurements.rst:1238 -msgid "network.serv\\ ices.firewal\\ l.rule.create" -msgstr "" - -#: ../telemetry-measurements.rst:1243 -msgid "network.serv\\ ices.firewal\\ l.rule.update" -msgstr "" - -#: ../telemetry-measurements.rst:1220 -msgid "network.serv\\ ices.firewal\\ l.update" -msgstr "" - -#: ../telemetry-measurements.rst:1206 -msgid "network.serv\\ ices.firewall" -msgstr "" - -#: ../telemetry-measurements.rst:1083 -msgid "network.serv\\ ices.lb.acti\\ ve.connections" -msgstr "" - -#: ../telemetry-measurements.rst:1075 -msgid "network.serv\\ ices.lb.heal\\ th_monitor" -msgstr "" - -#: ../telemetry-measurements.rst:1121 -msgid "network.serv\\ ices.lb.heal\\ th_monitor.c\\ reate" -msgstr "" - -#: ../telemetry-measurements.rst:1126 -msgid "network.serv\\ ices.lb.heal\\ th_monitor.u\\ pdate" -msgstr "" - -#: ../telemetry-measurements.rst:1087 -msgid "network.serv\\ ices.lb.inco\\ ming.bytes" -msgstr "" - -#: ../telemetry-measurements.rst:1071 -msgid "network.serv\\ ices.lb.memb\\ er" -msgstr "" - -#: ../telemetry-measurements.rst:1113 -msgid "network.serv\\ ices.lb.memb\\ er.create" -msgstr "" - -#: ../telemetry-measurements.rst:1117 -msgid "network.serv\\ ices.lb.memb\\ er.update" -msgstr "" - -#: ../telemetry-measurements.rst:1091 -msgid "network.serv\\ ices.lb.outg\\ oing.bytes" -msgstr "" - -#: ../telemetry-measurements.rst:1063 -msgid "network.serv\\ ices.lb.pool" -msgstr "" - -#: ../telemetry-measurements.rst:1097 -msgid "network.serv\\ ices.lb.pool\\ .create" -msgstr "" - -#: ../telemetry-measurements.rst:1101 -msgid "network.serv\\ ices.lb.pool\\ .update" -msgstr "" - -#: ../telemetry-measurements.rst:1079 -msgid "network.serv\\ ices.lb.tota\\ l.connections" -msgstr "" - -#: ../telemetry-measurements.rst:1067 -msgid "network.serv\\ ices.lb.vip" -msgstr "" - -#: ../telemetry-measurements.rst:1105 -msgid "network.serv\\ ices.lb.vip.\\ create" -msgstr "" - -#: ../telemetry-measurements.rst:1109 -msgid "network.serv\\ ices.lb.vip.\\ update" -msgstr "" - -#: ../telemetry-measurements.rst:1141 -msgid "network.serv\\ ices.vpn" -msgstr "" - -#: ../telemetry-measurements.rst:1145 -msgid "network.serv\\ ices.vpn.con\\ nections" -msgstr "" - -#: ../telemetry-measurements.rst:1160 -msgid "network.serv\\ ices.vpn.con\\ nections.cre\\ ate" -msgstr "" - -#: ../telemetry-measurements.rst:1165 -msgid "network.serv\\ ices.vpn.con\\ nections.upd\\ ate" -msgstr "" - -#: ../telemetry-measurements.rst:1152 -msgid "network.serv\\ ices.vpn.cre\\ ate" -msgstr "" - -#: ../telemetry-measurements.rst:1184 -msgid "network.serv\\ ices.vpn.ike\\ policy" -msgstr "" - -#: ../telemetry-measurements.rst:1188 -msgid "network.serv\\ ices.vpn.ike\\ policy.create" -msgstr "" - -#: ../telemetry-measurements.rst:1192 -msgid "network.serv\\ ices.vpn.ike\\ policy.update" -msgstr "" - -#: ../telemetry-measurements.rst:1170 -msgid "network.serv\\ ices.vpn.ips\\ ecpolicy" -msgstr "" - -#: ../telemetry-measurements.rst:1174 -msgid "network.serv\\ ices.vpn.ips\\ ecpolicy.cre\\ ate" -msgstr "" - -#: ../telemetry-measurements.rst:1179 -msgid "network.serv\\ ices.vpn.ips\\ ecpolicy.upd\\ ate" -msgstr "" - -#: ../telemetry-measurements.rst:1156 -msgid "network.serv\\ ices.vpn.upd\\ ate" -msgstr "" - -#: ../telemetry-measurements.rst:921 -msgid "network.update" -msgstr "" - -#: ../telemetry-data-collection.rst:90 -msgid "network.update.\\*" -msgstr "" - -#: ../networking_adv-config.rst:37 -msgid "neutron.agent.linux.interface. BridgeInterfaceDriver" -msgstr "" - -#: ../networking_adv-config.rst:31 -msgid "neutron.agent.linux.interface. OVSInterfaceDriver" -msgstr "" - -#: ../networking_adv-features.rst:709 -msgid "nexthop" -msgstr "" - -#: ../blockstorage-driver-filter-weighing.rst:105 -msgid "not, and, or, &, \\|, !" -msgstr "" - -#: ../telemetry-data-retrieval.rst:498 -msgid "notifier" -msgstr "" - -#: ../compute-live-migration-usage.rst:136 -#: ../compute-live-migration-usage.rst:143 -msgid "nova" -msgstr "" - -#: ../compute-live-migration-usage.rst:148 -msgid "nova-cert" -msgstr "" - -#: ../compute-live-migration-usage.rst:134 -#: ../compute-live-migration-usage.rst:141 -msgid "nova-compute" -msgstr "" - -#: ../compute-live-migration-usage.rst:127 -msgid "nova-conductor" -msgstr "" - -#: ../compute-live-migration-usage.rst:113 -msgid "nova-consoleauth" -msgstr "" - -#: ../compute-remote-console-access.rst:210 -msgid "nova-novncproxy (noVNC)" -msgstr "" - -#: ../compute-live-migration-usage.rst:120 -msgid "nova-scheduler" -msgstr "" - -#: ../compute-remote-console-access.rst:182 -msgid "novncproxy_base_url = http://127.0.0.1:6080/vnc_auto.html" -msgstr "" - -#: ../telemetry-measurements.rst:119 ../telemetry-measurements.rst:355 -#: ../telemetry-measurements.rst:437 ../telemetry-measurements.rst:440 -#: ../telemetry-measurements.rst:443 ../telemetry-measurements.rst:446 -#: ../telemetry-measurements.rst:1038 -msgid "ns" -msgstr "" - -#: ../database.rst:314 -msgid "num_config_servers_per_cluster" -msgstr "" - -#: ../database.rst:317 -msgid "num_query_routers_per_cluster" -msgstr "" - -#: ../telemetry-measurements.rst:756 ../telemetry-measurements.rst:776 -#: ../telemetry-measurements.rst:806 ../telemetry-measurements.rst:819 -msgid "object" -msgstr "" - -#: ../telemetry-alarms.rst:16 -msgid "ok" -msgstr "" - -#: ../telemetry-alarms.rst:196 -msgid "ok-action" -msgstr "" - -#: ../compute-networking-nova.rst:682 -msgid "on RHEL, Fedora, CentOS, openSUSE and SLES:" -msgstr "" - -#: ../compute-networking-nova.rst:676 -msgid "on Ubuntu, Debian:" -msgstr "" - -#: ../telemetry-alarms.rst:258 -msgid "" -"on-admin users see only the alarms associated with their project (as per the " -"normal tenant segregation in OpenStack)" -msgstr "" - -# #-#-#-#-# blockstorage_glusterfs_backend.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -# #-#-#-#-# blockstorage_nfs_backend.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -#: ../blockstorage_glusterfs_backend.rst:18 -#: ../blockstorage_glusterfs_backend.rst:139 -#: ../blockstorage_nfs_backend.rst:18 ../blockstorage_nfs_backend.rst:77 -msgid "openSUSE" -msgstr "" - -#: ../keystone_token-binding.rst:21 -msgid "or" -msgstr "" - -#: ../telemetry-alarms.rst:312 -msgid "or even deleted permanently (an irreversible step):" -msgstr "" - -#: ../orchestration-stack-domain-users.rst:137 -msgid "or::" -msgstr "" - -#: ../telemetry-data-collection.rst:114 -msgid "orchestration.stack\\ .create.end" -msgstr "" - -#: ../telemetry-data-collection.rst:120 -msgid "orchestration.stack\\ .delete.end" -msgstr "" - -#: ../telemetry-data-collection.rst:123 -msgid "orchestration.stack\\ .resume.end" -msgstr "" - -#: ../telemetry-data-collection.rst:126 -msgid "orchestration.stack\\ .suspend.end" -msgstr "" - -#: ../telemetry-data-collection.rst:117 -msgid "orchestration.stack\\ .update.end" -msgstr "" - -#: ../compute-live-migration-usage.rst:179 -msgid "p1" -msgstr "" - -#: ../compute-live-migration-usage.rst:180 -msgid "p2" -msgstr "" - -#: ../telemetry-measurements.rst:180 ../telemetry-measurements.rst:189 -msgid "pac\\ ket" -msgstr "" - -#: ../telemetry-measurements.rst:193 -msgid "pac\\ ket/s" -msgstr "" - -#: ../telemetry-measurements.rst:633 -msgid "pack\\ et" -msgstr "" - -#: ../telemetry-measurements.rst:184 ../telemetry-measurements.rst:278 -#: ../telemetry-measurements.rst:283 -msgid "pack\\ et/s" -msgstr "" - -#: ../database.rst:180 -msgid "packages" -msgstr "" - -#: ../telemetry-measurements.rst:983 ../telemetry-measurements.rst:986 -#: ../telemetry-measurements.rst:995 ../telemetry-measurements.rst:998 -#: ../telemetry-measurements.rst:1001 ../telemetry-measurements.rst:1004 -#: ../telemetry-measurements.rst:1007 ../telemetry-measurements.rst:1011 -#: ../telemetry-measurements.rst:1015 ../telemetry-measurements.rst:1027 -#: ../telemetry-measurements.rst:1030 ../telemetry-measurements.rst:1042 -msgid "packet" -msgstr "" - -#: ../telemetry-data-collection.rst:654 -msgid "parameters" -msgstr "" - -#: ../compute-flavors.rst:196 ../compute-flavors.rst:204 -msgid "peak: 512 Mbps (65536 kilobytes/second)" -msgstr "" - -#: ../database.rst:171 -msgid "percona" -msgstr "" - -#: ../compute_arch.rst:234 -msgid "php-opencloud" -msgstr "" - -#: ../telemetry-events.rst:152 -msgid "plugin" -msgstr "" - -#: ../telemetry-measurements.rst:1224 ../telemetry-measurements.rst:1229 -msgid "policy ID" -msgstr "" - -#: ../telemetry-measurements.rst:1063 ../telemetry-measurements.rst:1097 -#: ../telemetry-measurements.rst:1101 -msgid "pool" -msgstr "" - -#: ../telemetry-measurements.rst:1063 ../telemetry-measurements.rst:1079 -#: ../telemetry-measurements.rst:1083 ../telemetry-measurements.rst:1087 -#: ../telemetry-measurements.rst:1091 ../telemetry-measurements.rst:1097 -#: ../telemetry-measurements.rst:1101 -msgid "pool ID" -msgstr "" - -# #-#-#-#-# compute-security.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -# #-#-#-#-# telemetry-measurements.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -#: ../compute-security.rst:83 ../telemetry-measurements.rst:934 -#: ../telemetry-measurements.rst:937 ../telemetry-measurements.rst:940 -#: ../telemetry-measurements.rst:980 -msgid "port" -msgstr "" - -#: ../telemetry-measurements.rst:934 ../telemetry-measurements.rst:937 -#: ../telemetry-measurements.rst:940 -msgid "port ID" -msgstr "" - -#: ../telemetry-measurements.rst:937 -msgid "port.create" -msgstr "" - -#: ../telemetry-data-collection.rst:94 -msgid "port.create.end" -msgstr "" - -#: ../telemetry-data-collection.rst:98 -msgid "port.exists" -msgstr "" - -#: ../telemetry-measurements.rst:940 -msgid "port.update" -msgstr "" - -#: ../telemetry-data-collection.rst:96 -msgid "port.update.\\*" -msgstr "" - -#: ../telemetry-measurements.rst:1328 -msgid "power" -msgstr "" - -#: ../compute-live-migration-usage.rst:73 -msgid "private network" -msgstr "" - -#: ../compute-live-migration-usage.rst:41 -msgid "private=a.b.c.d" -msgstr "" - -#: ../compute-live-migration-usage.rst:45 -msgid "private=e.f.g.h" -msgstr "" - -#: ../telemetry-measurements.rst:1326 ../telemetry-measurements.rst:1328 -msgid "probe ID" -msgstr "" - -#: ../telemetry-measurements.rst:593 ../telemetry-measurements.rst:596 -#: ../telemetry-measurements.rst:599 -msgid "proc\\ ess" -msgstr "" - -#: ../telemetry-measurements.rst:879 ../telemetry-measurements.rst:882 -#: ../telemetry-measurements.rst:885 -msgid "project" -msgstr "" - -#: ../telemetry-measurements.rst:879 ../telemetry-measurements.rst:882 -#: ../telemetry-measurements.rst:885 -msgid "project ID" -msgstr "" - -#: ../networking_adv-features.rst:131 -msgid "provider: network\\_type" -msgstr "" - -#: ../networking_adv-features.rst:142 -msgid "provider: physical_network" -msgstr "" - -#: ../networking_adv-features.rst:150 -msgid "provider:segmentation_id" -msgstr "" - -#: ../compute-system-admin.rst:79 -msgid "" -"provides a VNC proxy for browsers, allowing VNC consoles to access virtual " -"machines." -msgstr "" - -#: ../compute-system-admin.rst:53 -msgid "" -"provides database-access support for Compute nodes (thereby reducing " -"security risks)." -msgstr "" - -#: ../telemetry-data-retrieval.rst:559 -msgid "queue" -msgstr "" - -#: ../telemetry-measurements.rst:814 -msgid "radosgw.api.requ\\ est" -msgstr "" - -#: ../telemetry-measurements.rst:819 -msgid "radosgw.containe\\ rs.objects" -msgstr "" - -#: ../telemetry-measurements.rst:822 -msgid "radosgw.containe\\ rs.objects.size" -msgstr "" - -#: ../telemetry-measurements.rst:806 -msgid "radosgw.objects" -msgstr "" - -#: ../telemetry-measurements.rst:811 -msgid "radosgw.objects.\\ containers" -msgstr "" - -#: ../telemetry-measurements.rst:808 -msgid "radosgw.objects.\\ size" -msgstr "" - -#: ../telemetry-data-collection.rst:617 -msgid "rate\\_of\\_change" -msgstr "" - -# #-#-#-#-# telemetry-events.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -# #-#-#-#-# ts-eql-volume-size.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -#: ../telemetry-events.rst:52 ../ts-eql-volume-size.rst:113 -msgid "raw" -msgstr "" - -#: ../compute-system-admin.rst:39 -msgid "" -"receives XML requests and sends them to the rest of the system. A WSGI app " -"routes and authenticates requests. Supports the EC2 and OpenStack APIs. A :" -"file:`nova.conf` configuration file is created when Compute is installed." -msgstr "" - -#: ../database.rst:167 -msgid "redis" -msgstr "" - -#: ../telemetry-alarms.rst:193 -msgid "repeat-actions" -msgstr "" - -#: ../blockstorage-driver-filter-weighing.rst:198 -msgid "replication\\_status" -msgstr "" - -#: ../telemetry-measurements.rst:130 ../telemetry-measurements.rst:137 -#: ../telemetry-measurements.rst:232 ../telemetry-measurements.rst:241 -msgid "req\\ uest" -msgstr "" - -#: ../telemetry-measurements.rst:771 -msgid "requ\\ est" -msgstr "" - -#: ../telemetry-measurements.rst:133 ../telemetry-measurements.rst:140 -#: ../telemetry-measurements.rst:236 ../telemetry-measurements.rst:245 -msgid "requ\\ est/s" -msgstr "" - -#: ../telemetry-measurements.rst:814 -msgid "request" -msgstr "" - -#: ../blockstorage-driver-filter-weighing.rst:183 -msgid "reservations" -msgstr "" - -#: ../blockstorage-driver-filter-weighing.rst:158 -msgid "reserved\\_percentage" -msgstr "" - -#: ../telemetry-measurements.rst:870 ../telemetry-measurements.rst:873 -#: ../telemetry-measurements.rst:876 -msgid "role" -msgstr "" - -#: ../telemetry-measurements.rst:870 ../telemetry-measurements.rst:873 -#: ../telemetry-measurements.rst:876 ../telemetry-measurements.rst:896 -#: ../telemetry-measurements.rst:900 -msgid "role ID" -msgstr "" - -#: ../telemetry-measurements.rst:896 ../telemetry-measurements.rst:900 -msgid "role_a\\ ssignm\\ ent" -msgstr "" - -#: ../telemetry-measurements.rst:943 ../telemetry-measurements.rst:946 -#: ../telemetry-measurements.rst:950 -msgid "router" -msgstr "" - -#: ../telemetry-measurements.rst:943 ../telemetry-measurements.rst:946 -#: ../telemetry-measurements.rst:950 -msgid "router ID" -msgstr "" - -#: ../telemetry-measurements.rst:946 -msgid "router.create" -msgstr "" - -#: ../telemetry-data-collection.rst:100 -msgid "router.create.end" -msgstr "" - -#: ../telemetry-data-collection.rst:104 -msgid "router.exists" -msgstr "" - -#: ../telemetry-measurements.rst:950 -msgid "router.update" -msgstr "" - -#: ../telemetry-data-collection.rst:102 -msgid "router.update.\\*" -msgstr "" - -#: ../telemetry-data-retrieval.rst:505 -msgid "rpc" -msgstr "" - -#: ../compute-manage-logs.rst:90 -msgid "" -"rsyslog is useful for setting up a centralized log server across multiple " -"machines. This section briefly describe the configuration to set up an " -"rsyslog server. A full treatment of rsyslog is beyond the scope of this " -"book. This section assumes rsyslog has already been installed on your hosts " -"(it is installed by default on most Linux distributions)." -msgstr "" - -#: ../telemetry-measurements.rst:1234 ../telemetry-measurements.rst:1238 -#: ../telemetry-measurements.rst:1243 -msgid "rule ID" -msgstr "" - -#: ../telemetry-measurements.rst:1035 -msgid "s" -msgstr "" - -#: ../telemetry-data-collection.rst:61 -msgid "scheduler.run\\_insta\\ nce.scheduled" -msgstr "" - -#: ../telemetry-data-collection.rst:64 -msgid "scheduler.select\\_\\ destinations" -msgstr "" - -#: ../compute-manage-logs.rst:205 -msgid "serial" -msgstr "" - -#: ../compute-security.rst:80 -msgid "server" -msgstr "" - -#: ../compute-security.rst:86 -msgid "server_ca_file" -msgstr "" - -#: ../blockstorage-driver-filter-weighing.rst:109 -msgid "sign" -msgstr "" - -#: ../blockstorage-driver-filter-weighing.rst:219 -msgid "size" -msgstr "" - -#: ../telemetry-measurements.rst:709 ../telemetry-measurements.rst:738 -#: ../telemetry-measurements.rst:741 -msgid "snapsh\\ ot" -msgstr "" - -#: ../telemetry-measurements.rst:709 -msgid "snapshot" -msgstr "" - -#: ../telemetry-measurements.rst:709 ../telemetry-measurements.rst:712 -#: ../telemetry-measurements.rst:738 ../telemetry-measurements.rst:741 -msgid "snapshot ID" -msgstr "" - -#: ../telemetry-measurements.rst:738 -msgid "snapshot.create.(s\\ tart|end)" -msgstr "" - -#: ../telemetry-data-collection.rst:145 -msgid "snapshot.create.\\*" -msgstr "" - -#: ../telemetry-measurements.rst:741 -msgid "snapshot.delete.(s\\ tart|end)" -msgstr "" - -#: ../telemetry-data-collection.rst:147 -msgid "snapshot.delete.\\*" -msgstr "" - -#: ../telemetry-data-collection.rst:143 -msgid "snapshot.exists" -msgstr "" - -#: ../telemetry-measurements.rst:712 -msgid "snapshot.size" -msgstr "" - -#: ../telemetry-data-collection.rst:149 -msgid "snapshot.update.\\*" -msgstr "" - -#: ../blockstorage-driver-filter-weighing.rst:201 -msgid "snapshot\\_id" -msgstr "" - -#: ../networking_adv-features.rst:694 -msgid "source" -msgstr "" - -#: ../blockstorage-driver-filter-weighing.rst:213 -msgid "source\\_replicaid" -msgstr "" - -#: ../blockstorage-driver-filter-weighing.rst:207 -msgid "source\\_volid" -msgstr "" - -#: ../compute-networking-nova.rst:170 -msgid "" -"specifies a range of fixed IP addresses to allocate, and can be a subset of " -"the ``--fixed-range-v4`` argument." -msgstr "" - -#: ../compute-networking-nova.rst:173 -msgid "" -"specifies the bridge device to which this network is connected on every " -"compute node." -msgstr "" - -#: ../compute-networking-nova.rst:169 -msgid "specifies the network subnet." -msgstr "" - -#: ../keystone_configure_with_SSL.rst:16 -msgid "ssl\\_cert.pem" -msgstr "" - -#: ../keystone_configure_with_SSL.rst:26 -msgid "ssl\\_key.pem" -msgstr "" - -#: ../telemetry-measurements.rst:1257 ../telemetry-measurements.rst:1260 -#: ../telemetry-measurements.rst:1263 ../telemetry-measurements.rst:1266 -#: ../telemetry-measurements.rst:1269 -msgid "stack" -msgstr "" - -#: ../telemetry-measurements.rst:1257 ../telemetry-measurements.rst:1260 -#: ../telemetry-measurements.rst:1263 ../telemetry-measurements.rst:1266 -#: ../telemetry-measurements.rst:1269 -msgid "stack ID" -msgstr "" - -#: ../telemetry-measurements.rst:1257 -msgid "stack.create" -msgstr "" - -#: ../telemetry-measurements.rst:1263 -msgid "stack.delete" -msgstr "" - -#: ../telemetry-measurements.rst:1266 -msgid "stack.resume" -msgstr "" - -#: ../telemetry-measurements.rst:1269 -msgid "stack.suspend" -msgstr "" - -#: ../telemetry-measurements.rst:1260 -msgid "stack.update" -msgstr "" - -#: ../blockstorage-driver-filter-weighing.rst:103 -msgid "standard math" -msgstr "" - -#: ../telemetry-alarms.rst:181 -msgid "state" -msgstr "" - -# #-#-#-#-# blockstorage-driver-filter-weighing.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -# #-#-#-#-# compute-live-migration-usage.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -#: ../blockstorage-driver-filter-weighing.rst:171 -#: ../compute-live-migration-usage.rst:75 -msgid "status" -msgstr "" - -#: ../telemetry-measurements.rst:756 ../telemetry-measurements.rst:759 -#: ../telemetry-measurements.rst:762 ../telemetry-measurements.rst:765 -#: ../telemetry-measurements.rst:768 ../telemetry-measurements.rst:771 -#: ../telemetry-measurements.rst:806 ../telemetry-measurements.rst:808 -#: ../telemetry-measurements.rst:811 ../telemetry-measurements.rst:814 -msgid "storage ID" -msgstr "" - -#: ../telemetry-measurements.rst:776 ../telemetry-measurements.rst:779 -#: ../telemetry-measurements.rst:819 ../telemetry-measurements.rst:822 -msgid "storage ID\\ /container" -msgstr "" - -#: ../telemetry-measurements.rst:771 -msgid "storage.api.request" -msgstr "" - -#: ../telemetry-measurements.rst:776 -msgid "storage.containers\\ .objects" -msgstr "" - -#: ../telemetry-measurements.rst:779 -msgid "storage.containers\\ .objects.size" -msgstr "" - -#: ../telemetry-measurements.rst:756 -msgid "storage.objects" -msgstr "" - -#: ../telemetry-measurements.rst:762 -msgid "storage.objects.co\\ ntainers" -msgstr "" - -#: ../telemetry-measurements.rst:765 -msgid "storage.objects.in\\ coming.bytes" -msgstr "" - -#: ../telemetry-measurements.rst:768 -msgid "storage.objects.ou\\ tgoing.bytes" -msgstr "" - -#: ../telemetry-measurements.rst:759 -msgid "storage.objects.si\\ ze" -msgstr "" - -#: ../blockstorage-driver-filter-weighing.rst:146 -msgid "storage\\_protocol" -msgstr "" - -#: ../telemetry-measurements.rst:924 ../telemetry-measurements.rst:927 -#: ../telemetry-measurements.rst:931 -msgid "subnet" -msgstr "" - -#: ../telemetry-measurements.rst:924 ../telemetry-measurements.rst:927 -#: ../telemetry-measurements.rst:931 -msgid "subnet ID" -msgstr "" - -#: ../telemetry-measurements.rst:927 -msgid "subnet.create" -msgstr "" - -#: ../telemetry-data-collection.rst:106 -msgid "subnet.create.end" -msgstr "" - -#: ../telemetry-data-collection.rst:110 -msgid "subnet.exists" -msgstr "" - -#: ../telemetry-measurements.rst:931 -msgid "subnet.update" -msgstr "" - -#: ../telemetry-data-collection.rst:108 -msgid "subnet.update.\\*" -msgstr "" - -#: ../objectstorage_tenant_specific_image_storage.rst:28 -msgid "swift_store_admin_tenants" -msgstr "" - -#: ../objectstorage_tenant_specific_image_storage.rst:24 -msgid "swift_store_multi_tenant" +#: ../telemetry-measurements.rst:977 +msgid "Existence of sw\\ itch" msgstr "" #: ../telemetry-measurements.rst:977 @@ -25158,232 +23907,260 @@ msgstr "" msgid "switch ID" msgstr "" -#: ../telemetry-measurements.rst:1033 -msgid "switch.flow" -msgstr "" - -#: ../telemetry-measurements.rst:1045 -msgid "switch.flow.by\\ tes" -msgstr "" - -#: ../telemetry-measurements.rst:1038 -msgid "switch.flow.du\\ ration.nanosec\\ onds" -msgstr "" - -#: ../telemetry-measurements.rst:1035 -msgid "switch.flow.du\\ ration.seconds" -msgstr "" - -#: ../telemetry-measurements.rst:1042 -msgid "switch.flow.pa\\ ckets" -msgstr "" - #: ../telemetry-measurements.rst:980 msgid "switch.port" msgstr "" -#: ../telemetry-measurements.rst:1018 -msgid "switch.port.co\\ llision.count" +#: ../telemetry-measurements.rst:983 ../telemetry-measurements.rst:986 +#: ../telemetry-measurements.rst:989 ../telemetry-measurements.rst:992 +#: ../telemetry-measurements.rst:995 ../telemetry-measurements.rst:998 +#: ../telemetry-measurements.rst:1001 ../telemetry-measurements.rst:1004 +#: ../telemetry-measurements.rst:1007 ../telemetry-measurements.rst:1011 +#: ../telemetry-measurements.rst:1015 ../telemetry-measurements.rst:1018 +#: ../telemetry-measurements.rst:1042 ../telemetry-measurements.rst:1045 +#: ../telemetry-measurements.rst:1079 ../telemetry-measurements.rst:1087 +#: ../telemetry-measurements.rst:1091 +msgid "Cumula\\ tive" +msgstr "" + +#: ../telemetry-measurements.rst:983 +msgid "Packets receive\\ d on port" +msgstr "" + +#: ../telemetry-measurements.rst:983 ../telemetry-measurements.rst:986 +#: ../telemetry-measurements.rst:995 ../telemetry-measurements.rst:998 +#: ../telemetry-measurements.rst:1001 ../telemetry-measurements.rst:1004 +#: ../telemetry-measurements.rst:1007 ../telemetry-measurements.rst:1011 +#: ../telemetry-measurements.rst:1015 ../telemetry-measurements.rst:1027 +#: ../telemetry-measurements.rst:1030 ../telemetry-measurements.rst:1042 +msgid "packet" +msgstr "" + +#: ../telemetry-measurements.rst:983 +msgid "switch.port.re\\ ceive.packets" +msgstr "" + +#: ../telemetry-measurements.rst:986 +msgid "Packets transmi\\ tted on port" +msgstr "" + +#: ../telemetry-measurements.rst:986 +msgid "switch.port.tr\\ ansmit.packets" +msgstr "" + +#: ../telemetry-measurements.rst:989 +msgid "Bytes received on port" msgstr "" #: ../telemetry-measurements.rst:989 msgid "switch.port.re\\ ceive.bytes" msgstr "" -#: ../telemetry-measurements.rst:1015 -msgid "switch.port.re\\ ceive.crc\\_error" +#: ../telemetry-measurements.rst:992 +msgid "Bytes transmitt\\ ed on port" +msgstr "" + +#: ../telemetry-measurements.rst:992 +msgid "switch.port.tr\\ ansmit.bytes" +msgstr "" + +#: ../telemetry-measurements.rst:995 +msgid "Drops received on port" msgstr "" #: ../telemetry-measurements.rst:995 msgid "switch.port.re\\ ceive.drops" msgstr "" +#: ../telemetry-measurements.rst:998 +msgid "Drops transmitt\\ ed on port" +msgstr "" + +#: ../telemetry-measurements.rst:998 +msgid "switch.port.tr\\ ansmit.drops" +msgstr "" + +#: ../telemetry-measurements.rst:1001 +msgid "Errors received on port" +msgstr "" + #: ../telemetry-measurements.rst:1001 msgid "switch.port.re\\ ceive.errors" msgstr "" +#: ../telemetry-measurements.rst:1004 +msgid "Errors transmit\\ ted on port" +msgstr "" + +#: ../telemetry-measurements.rst:1004 +msgid "switch.port.tr\\ ansmit.errors" +msgstr "" + +#: ../telemetry-measurements.rst:1007 +msgid "Frame alignment errors receive\\ d on port" +msgstr "" + #: ../telemetry-measurements.rst:1007 msgid "switch.port.re\\ ceive.frame\\_er\\ ror" msgstr "" +#: ../telemetry-measurements.rst:1011 +msgid "Overrun errors received on port" +msgstr "" + #: ../telemetry-measurements.rst:1011 msgid "switch.port.re\\ ceive.overrun\\_\\ error" msgstr "" -#: ../telemetry-measurements.rst:983 -msgid "switch.port.re\\ ceive.packets" +#: ../telemetry-measurements.rst:1015 +msgid "CRC errors rece\\ ived on port" msgstr "" -#: ../telemetry-measurements.rst:992 -msgid "switch.port.tr\\ ansmit.bytes" +#: ../telemetry-measurements.rst:1015 +msgid "switch.port.re\\ ceive.crc\\_error" msgstr "" -#: ../telemetry-measurements.rst:998 -msgid "switch.port.tr\\ ansmit.drops" +#: ../telemetry-measurements.rst:1018 +msgid "Collisions on p\\ ort" msgstr "" -#: ../telemetry-measurements.rst:1004 -msgid "switch.port.tr\\ ansmit.errors" +#: ../telemetry-measurements.rst:1018 +msgid "count" msgstr "" -#: ../telemetry-measurements.rst:986 -msgid "switch.port.tr\\ ansmit.packets" +#: ../telemetry-measurements.rst:1018 +msgid "switch.port.co\\ llision.count" +msgstr "" + +#: ../telemetry-measurements.rst:1021 +msgid "Duration of tab\\ le" msgstr "" #: ../telemetry-measurements.rst:1021 msgid "switch.table" msgstr "" -#: ../telemetry-measurements.rst:1024 -msgid "switch.table.a\\ ctive.entries" -msgstr "" - -#: ../telemetry-measurements.rst:1027 -msgid "switch.table.l\\ ookup.packets" -msgstr "" - -#: ../telemetry-measurements.rst:1030 -msgid "switch.table.m\\ atched.packets" -msgstr "" - #: ../telemetry-measurements.rst:1021 ../telemetry-measurements.rst:1306 #: ../telemetry-measurements.rst:1309 msgid "table" msgstr "" -#: ../telemetry-measurements.rst:1306 ../telemetry-measurements.rst:1309 -#: ../telemetry-measurements.rst:1312 -msgid "table ID" +#: ../telemetry-measurements.rst:1024 +msgid "Active entries in table" msgstr "" -#: ../telemetry-measurements.rst:494 -msgid "temper\\ ature sensor" +#: ../telemetry-measurements.rst:1024 +msgid "entry" msgstr "" -#: ../blockstorage-driver-filter-weighing.rst:111 -msgid "ternary" +#: ../telemetry-measurements.rst:1024 +msgid "switch.table.a\\ ctive.entries" msgstr "" -#: ../telemetry-alarms.rst:205 -msgid "time-constraint" +#: ../telemetry-measurements.rst:1027 +msgid "Lookup packets for table" msgstr "" -#: ../blockstorage_multi_backend.rst:47 -msgid "to convert current block devices to the new hostname." +#: ../telemetry-measurements.rst:1027 +msgid "switch.table.l\\ ookup.packets" msgstr "" -#: ../blockstorage-driver-filter-weighing.rst:152 -msgid "total\\_capacity\\_gb" +#: ../telemetry-measurements.rst:1030 +msgid "Packets matches for table" msgstr "" -#: ../telemetry-events.rst:48 ../telemetry-events.rst:129 -msgid "traits" +#: ../telemetry-measurements.rst:1030 +msgid "switch.table.m\\ atched.packets" msgstr "" -#: ../telemetry-measurements.rst:888 ../telemetry-measurements.rst:891 -msgid "trust" +#: ../telemetry-measurements.rst:1033 +msgid "Duration of flow" msgstr "" -#: ../telemetry-measurements.rst:888 ../telemetry-measurements.rst:891 -msgid "trust ID" +#: ../telemetry-measurements.rst:1033 +msgid "flow" msgstr "" -#: ../telemetry-events.rst:149 -msgid "type" +#: ../telemetry-measurements.rst:1033 +msgid "switch.flow" msgstr "" -#: ../telemetry-data-retrieval.rst:509 -msgid "udp" +#: ../telemetry-measurements.rst:1035 +msgid "Duration of flow in seconds" msgstr "" -#: ../telemetry-data-collection.rst:619 -msgid "unit\\_conversion" +#: ../telemetry-measurements.rst:1035 +msgid "s" msgstr "" -#: ../compute-live-migration-usage.rst:117 -#: ../compute-live-migration-usage.rst:124 -#: ../compute-live-migration-usage.rst:131 -#: ../compute-live-migration-usage.rst:138 -#: ../compute-live-migration-usage.rst:145 -#: ../compute-live-migration-usage.rst:152 -msgid "up" +#: ../telemetry-measurements.rst:1035 +msgid "switch.flow.du\\ ration.seconds" msgstr "" -#: ../compute-networking-nova.rst:319 -msgid "use_ipv6 = False" +#: ../telemetry-measurements.rst:1038 +msgid "Duration of flow in nanoseconds" msgstr "" -#: ../telemetry-measurements.rst:843 ../telemetry-measurements.rst:846 -#: ../telemetry-measurements.rst:849 ../telemetry-measurements.rst:852 -#: ../telemetry-measurements.rst:855 ../telemetry-measurements.rst:858 -msgid "user" +#: ../telemetry-measurements.rst:1038 +msgid "switch.flow.du\\ ration.nanosec\\ onds" msgstr "" -#: ../telemetry-measurements.rst:843 ../telemetry-measurements.rst:846 -#: ../telemetry-measurements.rst:849 ../telemetry-measurements.rst:852 -#: ../telemetry-measurements.rst:855 ../telemetry-measurements.rst:858 -msgid "user ID" +#: ../telemetry-measurements.rst:1042 +msgid "Packets received" msgstr "" -#: ../blockstorage-driver-filter-weighing.rst:186 -msgid "user\\_id" +#: ../telemetry-measurements.rst:1042 +msgid "switch.flow.pa\\ ckets" msgstr "" -#: ../telemetry-measurements.rst:113 -msgid "vSphere" +#: ../telemetry-measurements.rst:1045 +msgid "Bytes received" msgstr "" -#: ../telemetry-measurements.rst:210 -msgid "vSphere, XenAPI" +#: ../telemetry-measurements.rst:1045 +msgid "switch.flow.by\\ tes" msgstr "" -#: ../telemetry-measurements.rst:126 -msgid "vcpu" -msgstr "" - -#: ../telemetry-measurements.rst:126 -msgid "vcpus" -msgstr "" - -#: ../blockstorage-driver-filter-weighing.rst:140 -msgid "vendor\\_name" -msgstr "" - -#: ../compute-networking-nova.rst:529 +#: ../telemetry-measurements.rst:1051 msgid "" -"vendordata_driver = nova.api.metadata.vendordata_json.JsonFileVendorData" +"These meters are available for OpenFlow based switches. In order to enable " +"these meters, each driver needs to be properly configured." msgstr "" -#: ../compute-networking-nova.rst:531 -msgid "vendordata_jsonfile_path = None" +#: ../telemetry-measurements.rst:1055 +msgid "Load-Balancer-as-a-Service (LBaaS)" msgstr "" -#: ../database.rst:157 -msgid "version name" +#: ../telemetry-measurements.rst:1056 +msgid "The following meters are collected for LBaaS:" msgstr "" -#: ../compute-flavors.rst:162 -msgid "vif\\_inbound\\_ average" +#: ../telemetry-measurements.rst:1063 +msgid "Existence of a LB pool" msgstr "" -#: ../compute-flavors.rst:164 -msgid "vif\\_inbound\\_burst" +#: ../telemetry-measurements.rst:1063 +msgid "network.serv\\ ices.lb.pool" msgstr "" -#: ../compute-flavors.rst:166 -msgid "vif\\_inbound\\_peak" +#: ../telemetry-measurements.rst:1063 ../telemetry-measurements.rst:1097 +#: ../telemetry-measurements.rst:1101 +msgid "pool" msgstr "" -#: ../compute-flavors.rst:168 -msgid "vif\\_outbound\\_ average" +#: ../telemetry-measurements.rst:1063 ../telemetry-measurements.rst:1079 +#: ../telemetry-measurements.rst:1083 ../telemetry-measurements.rst:1087 +#: ../telemetry-measurements.rst:1091 ../telemetry-measurements.rst:1097 +#: ../telemetry-measurements.rst:1101 +msgid "pool ID" msgstr "" -#: ../compute-flavors.rst:170 -msgid "vif\\_outbound\\_burst" +#: ../telemetry-measurements.rst:1067 +msgid "Existence of a LB VIP" msgstr "" -#: ../compute-flavors.rst:172 -msgid "vif\\_outbound\\_peak" +#: ../telemetry-measurements.rst:1067 +msgid "network.serv\\ ices.lb.vip" msgstr "" #: ../telemetry-measurements.rst:1067 ../telemetry-measurements.rst:1105 @@ -25396,171 +24173,156 @@ msgstr "" msgid "vip ID" msgstr "" -#: ../compute-live-migration-usage.rst:39 -#: ../compute-live-migration-usage.rst:90 -msgid "vm1" +#: ../telemetry-measurements.rst:1071 +msgid "Existence of a LB member" msgstr "" -#: ../compute-live-migration-usage.rst:43 -msgid "vm2" +#: ../telemetry-measurements.rst:1071 ../telemetry-measurements.rst:1113 +#: ../telemetry-measurements.rst:1117 +msgid "member" msgstr "" -#: ../compute-remote-console-access.rst:177 -msgid "vnc_port_total = 10000" +#: ../telemetry-measurements.rst:1071 ../telemetry-measurements.rst:1113 +#: ../telemetry-measurements.rst:1117 +msgid "member ID" msgstr "" -#: ../compute-remote-console-access.rst:185 -msgid "vncserver_listen = 127.0.0.1" +#: ../telemetry-measurements.rst:1071 +msgid "network.serv\\ ices.lb.memb\\ er" msgstr "" -#: ../compute-remote-console-access.rst:187 -msgid "vncserver_proxyclient_address = 127.0.0.1" +#: ../telemetry-measurements.rst:1075 +msgid "Existence of a LB health probe" msgstr "" -#: ../telemetry-measurements.rst:501 -msgid "voltage sensor" +#: ../telemetry-measurements.rst:1075 ../telemetry-measurements.rst:1121 +#: ../telemetry-measurements.rst:1126 +msgid "health\\ _monit\\ or" msgstr "" -#: ../telemetry-measurements.rst:701 ../telemetry-measurements.rst:717 -#: ../telemetry-measurements.rst:720 ../telemetry-measurements.rst:723 -#: ../telemetry-measurements.rst:727 ../telemetry-measurements.rst:730 -#: ../telemetry-measurements.rst:734 -msgid "volume" +#: ../telemetry-measurements.rst:1075 ../telemetry-measurements.rst:1121 +#: ../telemetry-measurements.rst:1126 +msgid "monitor ID" msgstr "" -#: ../telemetry-measurements.rst:701 ../telemetry-measurements.rst:704 -#: ../telemetry-measurements.rst:717 ../telemetry-measurements.rst:720 -#: ../telemetry-measurements.rst:723 ../telemetry-measurements.rst:727 -#: ../telemetry-measurements.rst:730 ../telemetry-measurements.rst:734 -msgid "volume ID" +#: ../telemetry-measurements.rst:1075 +msgid "network.serv\\ ices.lb.heal\\ th_monitor" msgstr "" -#: ../compute-manage-volumes.rst:15 -msgid "volume-attach" +#: ../telemetry-measurements.rst:1079 +msgid "Total connectio\\ ns on a LB" msgstr "" -#: ../compute-manage-volumes.rst:17 -msgid "volume-create" +#: ../telemetry-measurements.rst:1079 ../telemetry-measurements.rst:1083 +msgid "connec\\ tion" msgstr "" -#: ../compute-manage-volumes.rst:19 -msgid "volume-delete" +#: ../telemetry-measurements.rst:1079 +msgid "network.serv\\ ices.lb.tota\\ l.connections" msgstr "" -#: ../compute-manage-volumes.rst:21 -msgid "volume-detach" +#: ../telemetry-measurements.rst:1083 +msgid "Active connecti\\ ons on a LB" msgstr "" -#: ../compute-manage-volumes.rst:23 -msgid "volume-list" +#: ../telemetry-measurements.rst:1083 +msgid "network.serv\\ ices.lb.acti\\ ve.connections" msgstr "" -#: ../compute-manage-volumes.rst:25 -msgid "volume-show" +#: ../telemetry-measurements.rst:1087 +msgid "Number of incom\\ ing Bytes" msgstr "" -#: ../compute-manage-volumes.rst:27 -msgid "volume-snapshot-create" +#: ../telemetry-measurements.rst:1087 +msgid "network.serv\\ ices.lb.inco\\ ming.bytes" msgstr "" -#: ../compute-manage-volumes.rst:29 -msgid "volume-snapshot-delete" +#: ../telemetry-measurements.rst:1091 +msgid "Number of outgo\\ ing Bytes" msgstr "" -#: ../compute-manage-volumes.rst:31 -msgid "volume-snapshot-list" +#: ../telemetry-measurements.rst:1091 +msgid "network.serv\\ ices.lb.outg\\ oing.bytes" msgstr "" -#: ../compute-manage-volumes.rst:33 -msgid "volume-snapshot-show" +#: ../telemetry-measurements.rst:1097 +msgid "LB pool was cre\\ ated" msgstr "" -#: ../compute-manage-volumes.rst:35 -msgid "volume-type-create" +#: ../telemetry-measurements.rst:1097 +msgid "network.serv\\ ices.lb.pool\\ .create" msgstr "" -#: ../compute-manage-volumes.rst:37 -msgid "volume-type-delete" +#: ../telemetry-measurements.rst:1101 +msgid "LB pool was upd\\ ated" msgstr "" -#: ../compute-manage-volumes.rst:39 -msgid "volume-type-list" +#: ../telemetry-measurements.rst:1101 +msgid "network.serv\\ ices.lb.pool\\ .update" msgstr "" -#: ../compute-manage-volumes.rst:41 -msgid "volume-update" +#: ../telemetry-measurements.rst:1105 +msgid "LB VIP was crea\\ ted" msgstr "" -#: ../telemetry-measurements.rst:730 -msgid "volume.attach.(sta\\ rt|end)" +#: ../telemetry-measurements.rst:1105 +msgid "network.serv\\ ices.lb.vip.\\ create" msgstr "" -#: ../telemetry-data-collection.rst:139 -msgid "volume.attach.\\*" +#: ../telemetry-measurements.rst:1109 +msgid "LB VIP was upda\\ ted" msgstr "" -#: ../telemetry-measurements.rst:717 -msgid "volume.create.(sta\\ rt|end)" +#: ../telemetry-measurements.rst:1109 +msgid "network.serv\\ ices.lb.vip.\\ update" msgstr "" -#: ../telemetry-data-collection.rst:131 -msgid "volume.create.\\*" +#: ../telemetry-measurements.rst:1113 +msgid "LB member was c\\ reated" msgstr "" -#: ../telemetry-measurements.rst:720 -msgid "volume.delete.(sta\\ rt|end)" +#: ../telemetry-measurements.rst:1113 +msgid "network.serv\\ ices.lb.memb\\ er.create" msgstr "" -#: ../telemetry-data-collection.rst:133 -msgid "volume.delete.\\*" +#: ../telemetry-measurements.rst:1117 +msgid "LB member was u\\ pdated" msgstr "" -#: ../telemetry-measurements.rst:734 -msgid "volume.detach.(sta\\ rt|end)" +#: ../telemetry-measurements.rst:1117 +msgid "network.serv\\ ices.lb.memb\\ er.update" msgstr "" -#: ../telemetry-data-collection.rst:141 -msgid "volume.detach.\\*" +#: ../telemetry-measurements.rst:1121 +msgid "LB health probe was created" msgstr "" -#: ../telemetry-data-collection.rst:129 -msgid "volume.exists" +#: ../telemetry-measurements.rst:1121 +msgid "network.serv\\ ices.lb.heal\\ th_monitor.c\\ reate" msgstr "" -#: ../telemetry-measurements.rst:727 -msgid "volume.resize.(sta\\ rt|end)" +#: ../telemetry-measurements.rst:1126 +msgid "LB health probe was updated" msgstr "" -#: ../telemetry-data-collection.rst:137 -msgid "volume.resize.\\*" +#: ../telemetry-measurements.rst:1126 +msgid "network.serv\\ ices.lb.heal\\ th_monitor.u\\ pdate" msgstr "" -#: ../telemetry-measurements.rst:704 -msgid "volume.size" +#: ../telemetry-measurements.rst:1133 +msgid "VPN as a Service (VPNaaS)" msgstr "" -#: ../telemetry-measurements.rst:723 -msgid "volume.update.(sta\\ rt|end)" +#: ../telemetry-measurements.rst:1134 +msgid "The following meters are collected for VPNaaS:" msgstr "" -#: ../telemetry-data-collection.rst:135 -msgid "volume.update.\\*" +#: ../telemetry-measurements.rst:1141 +msgid "Existence of a VPN" msgstr "" -#: ../blockstorage-driver-filter-weighing.rst:210 -msgid "volume\\_admin\\_metadata" -msgstr "" - -#: ../blockstorage-driver-filter-weighing.rst:137 -msgid "volume\\_backend\\_name" -msgstr "" - -#: ../blockstorage-driver-filter-weighing.rst:180 -msgid "volume\\_metadata" -msgstr "" - -#: ../blockstorage-driver-filter-weighing.rst:174 -msgid "volume\\_type\\_id" +#: ../telemetry-measurements.rst:1141 +msgid "network.serv\\ ices.vpn" msgstr "" #: ../telemetry-measurements.rst:1141 ../telemetry-measurements.rst:1152 @@ -25573,66 +24335,1355 @@ msgstr "" msgid "vpnser\\ vice" msgstr "" -#: ../identity_service_api_protection.rst:71 +#: ../telemetry-measurements.rst:1145 +msgid "Existence of an IPSec connection" +msgstr "" + +#: ../telemetry-measurements.rst:1145 ../telemetry-measurements.rst:1160 +#: ../telemetry-measurements.rst:1165 +msgid "connection ID" +msgstr "" + +#: ../telemetry-measurements.rst:1145 ../telemetry-measurements.rst:1160 +#: ../telemetry-measurements.rst:1165 +msgid "ipsec\\_\\ site\\_c\\ onnect\\ ion" +msgstr "" + +#: ../telemetry-measurements.rst:1145 +msgid "network.serv\\ ices.vpn.con\\ nections" +msgstr "" + +#: ../telemetry-measurements.rst:1152 +msgid "VPN was created" +msgstr "" + +#: ../telemetry-measurements.rst:1152 +msgid "network.serv\\ ices.vpn.cre\\ ate" +msgstr "" + +#: ../telemetry-measurements.rst:1156 +msgid "VPN was updated" +msgstr "" + +#: ../telemetry-measurements.rst:1156 +msgid "network.serv\\ ices.vpn.upd\\ ate" +msgstr "" + +#: ../telemetry-measurements.rst:1160 +msgid "IPSec connection was created" +msgstr "" + +#: ../telemetry-measurements.rst:1160 +msgid "network.serv\\ ices.vpn.con\\ nections.cre\\ ate" +msgstr "" + +#: ../telemetry-measurements.rst:1165 +msgid "IPSec connection was updated" +msgstr "" + +#: ../telemetry-measurements.rst:1165 +msgid "network.serv\\ ices.vpn.con\\ nections.upd\\ ate" +msgstr "" + +#: ../telemetry-measurements.rst:1170 +msgid "Existence of an IPSec policy" +msgstr "" + +#: ../telemetry-measurements.rst:1170 ../telemetry-measurements.rst:1174 +#: ../telemetry-measurements.rst:1179 +msgid "ipsecp\\ olicy" +msgstr "" + +#: ../telemetry-measurements.rst:1170 ../telemetry-measurements.rst:1174 +#: ../telemetry-measurements.rst:1179 +msgid "ipsecpolicy ID" +msgstr "" + +#: ../telemetry-measurements.rst:1170 +msgid "network.serv\\ ices.vpn.ips\\ ecpolicy" +msgstr "" + +#: ../telemetry-measurements.rst:1174 +msgid "IPSec policy was reated" +msgstr "" + +#: ../telemetry-measurements.rst:1174 +msgid "network.serv\\ ices.vpn.ips\\ ecpolicy.cre\\ ate" +msgstr "" + +#: ../telemetry-measurements.rst:1179 +msgid "IPSec policy was updated" +msgstr "" + +#: ../telemetry-measurements.rst:1179 +msgid "network.serv\\ ices.vpn.ips\\ ecpolicy.upd\\ ate" +msgstr "" + +#: ../telemetry-measurements.rst:1184 +msgid "Existence of an Ike policy" +msgstr "" + +#: ../telemetry-measurements.rst:1184 ../telemetry-measurements.rst:1188 +#: ../telemetry-measurements.rst:1192 +msgid "ikepol\\ icy" +msgstr "" + +#: ../telemetry-measurements.rst:1184 ../telemetry-measurements.rst:1188 +#: ../telemetry-measurements.rst:1192 +msgid "ikepolicy ID" +msgstr "" + +#: ../telemetry-measurements.rst:1184 +msgid "network.serv\\ ices.vpn.ike\\ policy" +msgstr "" + +#: ../telemetry-measurements.rst:1188 +msgid "Ike policy was created" +msgstr "" + +#: ../telemetry-measurements.rst:1188 +msgid "network.serv\\ ices.vpn.ike\\ policy.create" +msgstr "" + +#: ../telemetry-measurements.rst:1192 +msgid "Ike policy was updated" +msgstr "" + +#: ../telemetry-measurements.rst:1192 +msgid "network.serv\\ ices.vpn.ike\\ policy.update" +msgstr "" + +#: ../telemetry-measurements.rst:1198 +msgid "Firewall as a Service (FWaaS)" +msgstr "" + +#: ../telemetry-measurements.rst:1199 +msgid "The following meters are collected for FWaaS:" +msgstr "" + +#: ../telemetry-measurements.rst:1206 +msgid "Existence of a firewall" +msgstr "" + +#: ../telemetry-measurements.rst:1206 ../telemetry-measurements.rst:1216 +#: ../telemetry-measurements.rst:1220 +msgid "firewall" +msgstr "" + +#: ../telemetry-measurements.rst:1206 ../telemetry-measurements.rst:1210 +#: ../telemetry-measurements.rst:1216 ../telemetry-measurements.rst:1220 +msgid "firewall ID" +msgstr "" + +#: ../telemetry-measurements.rst:1206 +msgid "network.serv\\ ices.firewall" +msgstr "" + +#: ../telemetry-measurements.rst:1210 +msgid "Existence of a firewall policy" +msgstr "" + +#: ../telemetry-measurements.rst:1210 ../telemetry-measurements.rst:1224 +#: ../telemetry-measurements.rst:1229 +msgid "firewa\\ ll_pol\\ icy" +msgstr "" + +#: ../telemetry-measurements.rst:1210 +msgid "network.serv\\ ices.firewal\\ l.policy" +msgstr "" + +#: ../telemetry-measurements.rst:1216 +msgid "Firewall was cr\\ eated" +msgstr "" + +#: ../telemetry-measurements.rst:1216 +msgid "network.serv\\ ices.firewal\\ l.create" +msgstr "" + +#: ../telemetry-measurements.rst:1220 +msgid "Firewall was up\\ dated" +msgstr "" + +#: ../telemetry-measurements.rst:1220 +msgid "network.serv\\ ices.firewal\\ l.update" +msgstr "" + +#: ../telemetry-measurements.rst:1224 +msgid "Firewall policy was created" +msgstr "" + +#: ../telemetry-measurements.rst:1224 +msgid "network.serv\\ ices.firewal\\ l.policy.cre\\ ate" +msgstr "" + +#: ../telemetry-measurements.rst:1224 ../telemetry-measurements.rst:1229 +msgid "policy ID" +msgstr "" + +#: ../telemetry-measurements.rst:1229 +msgid "Firewall policy was updated" +msgstr "" + +#: ../telemetry-measurements.rst:1229 +msgid "network.serv\\ ices.firewal\\ l.policy.upd\\ ate" +msgstr "" + +#: ../telemetry-measurements.rst:1234 +msgid "Existence of a firewall rule" +msgstr "" + +#: ../telemetry-measurements.rst:1234 ../telemetry-measurements.rst:1238 +#: ../telemetry-measurements.rst:1243 +msgid "firewa\\ ll_rule" +msgstr "" + +#: ../telemetry-measurements.rst:1234 +msgid "network.serv\\ ices.firewal\\ l.rule" +msgstr "" + +#: ../telemetry-measurements.rst:1234 ../telemetry-measurements.rst:1238 +#: ../telemetry-measurements.rst:1243 +msgid "rule ID" +msgstr "" + +#: ../telemetry-measurements.rst:1238 +msgid "Firewall rule w\\ as created" +msgstr "" + +#: ../telemetry-measurements.rst:1238 +msgid "network.serv\\ ices.firewal\\ l.rule.create" +msgstr "" + +#: ../telemetry-measurements.rst:1243 +msgid "Firewall rule w\\ as updated" +msgstr "" + +#: ../telemetry-measurements.rst:1243 +msgid "network.serv\\ ices.firewal\\ l.rule.update" +msgstr "" + +#: ../telemetry-measurements.rst:1250 +msgid "The following meters are collected for the Orchestration module:" +msgstr "" + +#: ../telemetry-measurements.rst:1257 +msgid "Stack was success\\ fully created" +msgstr "" + +#: ../telemetry-measurements.rst:1257 ../telemetry-measurements.rst:1260 +#: ../telemetry-measurements.rst:1263 ../telemetry-measurements.rst:1266 +#: ../telemetry-measurements.rst:1269 +msgid "stack" +msgstr "" + +#: ../telemetry-measurements.rst:1257 ../telemetry-measurements.rst:1260 +#: ../telemetry-measurements.rst:1263 ../telemetry-measurements.rst:1266 +#: ../telemetry-measurements.rst:1269 +msgid "stack ID" +msgstr "" + +#: ../telemetry-measurements.rst:1257 +msgid "stack.create" +msgstr "" + +#: ../telemetry-measurements.rst:1260 +msgid "Stack was success\\ fully updated" +msgstr "" + +#: ../telemetry-measurements.rst:1260 +msgid "stack.update" +msgstr "" + +#: ../telemetry-measurements.rst:1263 +msgid "Stack was success\\ fully deleted" +msgstr "" + +#: ../telemetry-measurements.rst:1263 +msgid "stack.delete" +msgstr "" + +#: ../telemetry-measurements.rst:1266 +msgid "Stack was success\\ fully resumed" +msgstr "" + +#: ../telemetry-measurements.rst:1266 +msgid "stack.resume" +msgstr "" + +#: ../telemetry-measurements.rst:1269 +msgid "Stack was success\\ fully suspended" +msgstr "" + +#: ../telemetry-measurements.rst:1269 +msgid "stack.suspend" +msgstr "" + +#: ../telemetry-measurements.rst:1274 +msgid "Data processing service for OpenStack" +msgstr "" + +#: ../telemetry-measurements.rst:1275 msgid "" -"would ensure that Identity only deletes the user object in the same domain " -"as the provided token." +"The following meters are collected for the Data processing service for " +"OpenStack:" msgstr "" -#: ../compute-manage-logs.rst:206 -msgid "ws://127.0.0.1:6083/?token=18510769-71ad-4e5a-8348-4218b5613b3d" +#: ../telemetry-measurements.rst:1283 +msgid "Cluster was successfully created" msgstr "" -#: ../blockstorage-driver-filter-weighing.rst:111 -msgid "x ? a : b" +#: ../telemetry-measurements.rst:1283 ../telemetry-measurements.rst:1288 +#: ../telemetry-measurements.rst:1292 +msgid "cluster" msgstr "" -#: ../compute-remote-console-access.rst:190 -msgid "xvpvncproxy_base_url = http://127.0.0.1:6081/console" +#: ../telemetry-measurements.rst:1283 ../telemetry-measurements.rst:1288 +#: ../telemetry-measurements.rst:1292 +msgid "cluster ID" msgstr "" -#: ../compute-images-instances.rst:52 -msgid "|Base image state with no running instances|" +#: ../telemetry-measurements.rst:1283 +msgid "cluster.create" msgstr "" -#: ../compute-images-instances.rst:92 -msgid "|End state of image and volume after instance exits|" +#: ../telemetry-measurements.rst:1288 +msgid "Cluster was successfully updated" msgstr "" -#: ../networking_introduction.rst:168 -msgid "|FWaaS architecture|" +#: ../telemetry-measurements.rst:1288 +msgid "cluster.update" msgstr "" -#: ../compute-images-instances.rst:60 -msgid "|Instance creation from image and runtime state|" +#: ../telemetry-measurements.rst:1292 +msgid "Cluster was successfully deleted" msgstr "" -#: ../compute-security.rst:139 -msgid "|Trusted compute pool|" +#: ../telemetry-measurements.rst:1292 +msgid "cluster.delete" msgstr "" -#: ../networking_arch.rst:87 -msgid "|VMware NSX deployment example - single Compute node|" +#: ../telemetry-measurements.rst:1298 +msgid "Key Value Store module" msgstr "" -#: ../networking_arch.rst:85 -msgid "|VMware NSX deployment example - two Compute nodes|" +#: ../telemetry-measurements.rst:1299 +msgid "The following meters are collected for the Key Value Store module:" msgstr "" -# #-#-#-#-# compute-security.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -# #-#-#-#-# networking_multi-dhcp-agents.pot (Cloud Administrator Guide 0.9) #-#-#-#-# -#: ../compute-security.rst:43 ../networking_multi-dhcp-agents.rst:31 -msgid "|image0|" +#: ../telemetry-measurements.rst:1306 +msgid "Table was succe\\ ssfully created" msgstr "" -#: ../compute-networking-nova.rst:783 -msgid "|multinic VLAN manager|" +#: ../telemetry-measurements.rst:1306 +msgid "magnetodb.table.\\ create" msgstr "" -#: ../compute-networking-nova.rst:779 -msgid "|multinic flat manager|" +#: ../telemetry-measurements.rst:1306 ../telemetry-measurements.rst:1309 +#: ../telemetry-measurements.rst:1312 +msgid "table ID" msgstr "" -#: ../compute-networking-nova.rst:781 -msgid "|multinic flatdhcp manager|" +#: ../telemetry-measurements.rst:1309 +msgid "Table was succe\\ ssfully deleted" +msgstr "" + +#: ../telemetry-measurements.rst:1309 +msgid "magnetodb.table\\ .delete" +msgstr "" + +#: ../telemetry-measurements.rst:1312 +msgid "Number of indices created in a table" +msgstr "" + +#: ../telemetry-measurements.rst:1312 +msgid "index" +msgstr "" + +#: ../telemetry-measurements.rst:1312 +msgid "magnetodb.table\\ .index.count" +msgstr "" + +#: ../telemetry-measurements.rst:1318 +msgid "Energy" +msgstr "" + +#: ../telemetry-measurements.rst:1319 +msgid "The following energy related meters are available:" +msgstr "" + +#: ../telemetry-measurements.rst:1326 +msgid "Amount of energy" +msgstr "" + +#: ../telemetry-measurements.rst:1326 +msgid "energy" +msgstr "" + +#: ../telemetry-measurements.rst:1326 +msgid "kWh" +msgstr "" + +#: ../telemetry-measurements.rst:1326 ../telemetry-measurements.rst:1328 +msgid "probe ID" +msgstr "" + +#: ../telemetry-measurements.rst:1328 +msgid "Power consumption" +msgstr "" + +#: ../telemetry-measurements.rst:1328 +msgid "power" +msgstr "" + +#: ../telemetry-system-architecture.rst:7 +msgid "" +"The Telemetry module uses an agent-based architecture. Several modules " +"combine their responsibilities to collect data, store samples in a database, " +"or provide an API service for handling incoming requests." +msgstr "" + +#: ../telemetry-system-architecture.rst:11 +msgid "The Telemetry module is built from the following agents and services:" +msgstr "" + +#: ../telemetry-system-architecture.rst:14 +msgid "" +"Presents aggregated metering data to consumers (such as billing engines, " +"analytics tools and so forth)." +msgstr "" + +#: ../telemetry-system-architecture.rst:15 +msgid "ceilometer-api" +msgstr "" + +#: ../telemetry-system-architecture.rst:18 +msgid "" +"Polls for different kinds of meter data by using the polling plug-ins " +"(pollsters) registered in different namespaces. It provides a single polling " +"interface across different namespaces." +msgstr "" + +#: ../telemetry-system-architecture.rst:20 +msgid "ceilometer-polling" +msgstr "" + +#: ../telemetry-system-architecture.rst:23 +msgid "" +"Polls the public RESTful APIs of other OpenStack services such as Compute " +"service and Image service, in order to keep tabs on resource existence, by " +"using the polling plug-ins (pollsters) registered in the central polling " +"namespace." +msgstr "" + +#: ../telemetry-system-architecture.rst:26 +msgid "ceilometer-agent-central" +msgstr "" + +#: ../telemetry-system-architecture.rst:29 +msgid "" +"Polls the local hypervisor or libvirt daemon to acquire performance data for " +"the local instances, messages and emits the data as AMQP messages, by using " +"the polling plug-ins (pollsters) registered in the compute polling namespace." +msgstr "" + +#: ../telemetry-system-architecture.rst:32 +msgid "ceilometer-agent-compute" +msgstr "" + +#: ../telemetry-system-architecture.rst:35 +msgid "" +"Polls the local node with IPMI support, in order to acquire IPMI sensor data " +"and Intel Node Manager data, by using the polling plug-ins (pollsters) " +"registered in the IPMI polling namespace." +msgstr "" + +#: ../telemetry-system-architecture.rst:37 +msgid "ceilometer-agent-ipmi" +msgstr "" + +#: ../telemetry-system-architecture.rst:40 +msgid "Consumes AMQP messages from other OpenStack services." +msgstr "" + +#: ../telemetry-system-architecture.rst:40 +msgid "ceilometer-agent-notification" +msgstr "" + +#: ../telemetry-system-architecture.rst:43 +msgid "" +"Consumes AMQP notifications from the agents, then dispatches these data to " +"the appropriate data store." +msgstr "" + +#: ../telemetry-system-architecture.rst:44 +msgid "ceilometer-collector" +msgstr "" + +#: ../telemetry-system-architecture.rst:47 +msgid "" +"Determines when alarms fire due to the associated statistic trend crossing a " +"threshold over a sliding time window." +msgstr "" + +#: ../telemetry-system-architecture.rst:48 +msgid "ceilometer-alarm-evaluator" +msgstr "" + +#: ../telemetry-system-architecture.rst:51 +msgid "" +"Initiates alarm actions, for example calling out to a webhook with a " +"description of the alarm state transition." +msgstr "" + +#: ../telemetry-system-architecture.rst:56 +msgid "" +"The ``ceilometer-polling`` service is available since the Kilo release. It " +"is intended to replace ceilometer-agent-central, ceilometer-agent-compute, " +"and ceilometer-agent-ipmi." +msgstr "" + +#: ../telemetry-system-architecture.rst:58 +msgid "ceilometer-alarm-notifier" +msgstr "" + +#: ../telemetry-system-architecture.rst:60 +msgid "" +"Besides the ``ceilometer-agent-compute`` and the ``ceilometer-agent-ipmi`` " +"services, all the other services are placed on one or more controller nodes." +msgstr "" + +#: ../telemetry-system-architecture.rst:64 +msgid "" +"The Telemetry architecture highly depends on the AMQP service both for " +"consuming notifications coming from OpenStack services and internal " +"communication." +msgstr "" + +#: ../telemetry-system-architecture.rst:73 +msgid "Supported databases" +msgstr "" + +#: ../telemetry-system-architecture.rst:75 +msgid "" +"The other key external component of Telemetry is the database, where events, " +"samples, alarm definitions and alarms are stored." +msgstr "" + +#: ../telemetry-system-architecture.rst:80 +msgid "" +"Multiple database back ends can be configured in order to store events, " +"samples and alarms separately." +msgstr "" + +#: ../telemetry-system-architecture.rst:83 +msgid "The list of supported database back ends:" +msgstr "" + +#: ../telemetry-system-architecture.rst:85 +msgid "`ElasticSearch (events only) `__" +msgstr "" + +#: ../telemetry-system-architecture.rst:87 +msgid "`MongoDB `__" +msgstr "" + +#: ../telemetry-system-architecture.rst:89 +msgid "`MySQL `__" +msgstr "" + +#: ../telemetry-system-architecture.rst:91 +msgid "`PostgreSQL `__" +msgstr "" + +#: ../telemetry-system-architecture.rst:93 +msgid "`HBase `__" +msgstr "" + +#: ../telemetry-system-architecture.rst:95 +msgid "`DB2(deprecated) `__" +msgstr "" + +#: ../telemetry-system-architecture.rst:99 +msgid "" +"DB2 nosql support is deprecated as of Liberty and will be removed in Mitaka " +"as the product is no longer in development." +msgstr "" + +#: ../telemetry-system-architecture.rst:107 +msgid "Supported hypervisors" +msgstr "" + +#: ../telemetry-system-architecture.rst:109 +msgid "" +"The Telemetry module collects information about the virtual machines, which " +"requires close connection to the hypervisor that runs on the compute hosts." +msgstr "" + +#: ../telemetry-system-architecture.rst:113 +msgid "The list of supported hypervisors is:" +msgstr "" + +#: ../telemetry-system-architecture.rst:115 +msgid "" +"The following hypervisors are supported via `Libvirt `__:" +msgstr "" + +#: ../telemetry-system-architecture.rst:121 +msgid "`Quick Emulator (QEMU) `__" +msgstr "" + +#: ../telemetry-system-architecture.rst:125 +msgid "`User-mode Linux (UML) `__" +msgstr "" + +#: ../telemetry-system-architecture.rst:130 +msgid "" +"For details about hypervisor support in libvirt please check the `Libvirt " +"API support matrix `__." +msgstr "" + +#: ../telemetry-system-architecture.rst:135 +msgid "`XEN `__" +msgstr "" + +#: ../telemetry-system-architecture.rst:137 +msgid "" +"`VMWare vSphere `__" +msgstr "" + +#: ../telemetry-system-architecture.rst:143 +msgid "Supported networking services" +msgstr "" + +#: ../telemetry-system-architecture.rst:145 +msgid "" +"Telemetry is able to retrieve information from OpenStack Networking and " +"external networking services:" +msgstr "" + +#: ../telemetry-system-architecture.rst:148 +msgid "OpenStack Networking:" +msgstr "" + +#: ../telemetry-system-architecture.rst:150 +msgid "Basic network meters" +msgstr "" + +#: ../telemetry-system-architecture.rst:152 +msgid "Firewall-as-a-Service (FWaaS) meters" +msgstr "" + +#: ../telemetry-system-architecture.rst:154 +msgid "Load-Balancer-as-a-Service (LBaaS) meters" +msgstr "" + +#: ../telemetry-system-architecture.rst:156 +msgid "VPN-as-a-Service (VPNaaS) meters" +msgstr "" + +#: ../telemetry-system-architecture.rst:158 +msgid "SDN controller meters:" +msgstr "" + +#: ../telemetry-system-architecture.rst:160 +msgid "`OpenDaylight `__" +msgstr "" + +#: ../telemetry-system-architecture.rst:162 +msgid "`OpenContrail `__" +msgstr "" + +#: ../telemetry-system-architecture.rst:169 +msgid "Users, roles and tenants" +msgstr "" + +#: ../telemetry-system-architecture.rst:171 +msgid "" +"This module of OpenStack uses OpenStack Identity for authenticating and " +"authorizing users. The required configuration options are listed in the " +"`Telemetry section `__ in the *OpenStack Configuration " +"Reference*." +msgstr "" + +#: ../telemetry-system-architecture.rst:177 +msgid "" +"The system uses two roles:`admin` and `non-admin`. The authorization happens " +"before processing each API request. The amount of returned data depends on " +"the role the requestor owns." +msgstr "" + +#: ../telemetry-system-architecture.rst:181 +msgid "" +"The creation of alarm definitions also highly depends on the role of the " +"user, who initiated the action. Further details about :ref:`telemetry-" +"alarms` handling can be found in this guide." +msgstr "" + +#: ../telemetry-troubleshooting-guide.rst:2 +msgid "Troubleshoot Telemetry" +msgstr "" + +#: ../telemetry-troubleshooting-guide.rst:5 +msgid "Logging in Telemetry" +msgstr "" + +#: ../telemetry-troubleshooting-guide.rst:7 +msgid "" +"The Telemetry module has similar log settings as the other OpenStack " +"services. Multiple options are available to change the target of logging, " +"the format of the log entries and the log levels." +msgstr "" + +#: ../telemetry-troubleshooting-guide.rst:11 +msgid "" +"The log settings can be changed in :file:`ceilometer.conf`. The list of " +"configuration options are listed in the logging configuration options table " +"in the `Telemetry section `__ in the *OpenStack " +"Configuration Reference*." +msgstr "" + +#: ../telemetry-troubleshooting-guide.rst:17 +msgid "" +"By default ``stderr`` is used as standard output for the log messages. It " +"can be changed to either a log file or syslog. The ``debug`` and ``verbose`` " +"options are also set to false in the default settings, the default log " +"levels of the corresponding modules can be found in the table referred above." +msgstr "" + +#: ../telemetry-troubleshooting-guide.rst:26 +msgid "Recommended order of starting services" +msgstr "" + +#: ../telemetry-troubleshooting-guide.rst:28 +msgid "" +"As it can be seen in `Bug 1355809 `__, the wrong ordering of service startup can result in data " +"loss." +msgstr "" + +#: ../telemetry-troubleshooting-guide.rst:32 +msgid "" +"When the services are started for the first time or in line with the message " +"queue service restart, it takes time while the **ceilometer-collector** " +"service establishes the connection and joins or rejoins to the configured " +"exchanges. Therefore, if the **ceilometer-agent-compute**, **ceilometer-" +"agent-central**, and the **ceilometer-agent-notification** services are " +"started before the **ceilometer-collector** service, the **ceilometer-" +"collector** service may lose some messages while connecting to the message " +"queue service." +msgstr "" + +#: ../telemetry-troubleshooting-guide.rst:41 +msgid "" +"The possibility of this issue to happen is higher, when the polling interval " +"is set to a relatively short period. In order to avoid this situation, the " +"recommended order of service startup is to start or restart the **ceilometer-" +"collector** service after the message queue. All the other Telemetry " +"services should be started or restarted after and the **ceilometer-agent-" +"compute** should be the last in the sequence, as this component emits " +"metering messages in order to send the samples to the collector." +msgstr "" + +#: ../telemetry-troubleshooting-guide.rst:53 +msgid "Notification agent" +msgstr "" + +#: ../telemetry-troubleshooting-guide.rst:55 +msgid "" +"In the Icehouse release of OpenStack a new service was introduced to be " +"responsible for consuming notifications that are coming from other OpenStack " +"services." +msgstr "" + +#: ../telemetry-troubleshooting-guide.rst:59 +msgid "" +"If the **ceilometer-agent-notification** service is not installed and " +"started, samples originating from notifications will not be generated. In " +"case of the lack of notification based samples, the state of this service " +"and the log file of Telemetry should be checked first." +msgstr "" + +#: ../telemetry-troubleshooting-guide.rst:64 +msgid "" +"For the list of meters that are originated from notifications, see the " +"`Telemetry Measurements Reference `__." +msgstr "" + +#: ../telemetry-troubleshooting-guide.rst:71 +msgid "Recommended ``auth_url`` to be used" +msgstr "" + +#: ../telemetry-troubleshooting-guide.rst:73 +msgid "" +"When using the Telemetry command line client, the credentials and the " +"``os_auth_url`` have to be set in order for the client to authenticate " +"against OpenStack Identity. For further details about the credentials that " +"have to be provided see the `Telemetry Python API `__." +msgstr "" + +#: ../telemetry-troubleshooting-guide.rst:79 +msgid "" +"The service catalog provided by OpenStack Identity contains the URLs that " +"are available for authentication. The URLs have different ``port``\\s, based " +"on whether the type of the given URL is ``public``, ``internal`` or " +"``admin``." +msgstr "" + +#: ../telemetry-troubleshooting-guide.rst:84 +msgid "" +"OpenStack Identity is about to change API version from v2 to v3. The " +"``adminURL`` endpoint (which is available via the port: ``35357``) supports " +"only the v3 version, while the other two supports both." +msgstr "" + +#: ../telemetry-troubleshooting-guide.rst:88 +msgid "" +"The Telemetry command line client is not adapted to the v3 version of the " +"OpenStack Identity API. If the ``adminURL`` is used as ``os_auth_url``, the :" +"command:`ceilometer` command results in the following error message:" +msgstr "" + +#: ../telemetry-troubleshooting-guide.rst:99 +msgid "" +"Therefore when specifying the ``os_auth_url`` parameter on the command line " +"or by using environment variable, use the ``internalURL`` or ``publicURL``." +msgstr "" + +#: ../telemetry-troubleshooting-guide.rst:103 +msgid "" +"For more details check the bug report `Bug 1351841 `__." +msgstr "" + +#: ../telemetry.rst:5 +msgid "Telemetry" +msgstr "" + +#: ../telemetry.rst:7 +msgid "" +"Even in the cloud industry, providers must use a multi-step process for " +"billing. The required steps to bill for usage in a cloud environment are " +"metering, rating, and billing. Because the provider's requirements may be " +"far too specific for a shared solution, rating and billing solutions cannot " +"be designed in a common module that satisfies all. Providing users with " +"measurements on cloud services is required to meet the \"measured service\" " +"definition of cloud computing." +msgstr "" + +#: ../telemetry.rst:15 +msgid "" +"The Telemetry module was originally designed to support billing systems for " +"OpenStack cloud resources. This project only covers the metering portion of " +"the required processing for billing. This module collects information about " +"the system and stores it in the form of samples in order to provide data " +"about anything that can be billed." +msgstr "" + +#: ../telemetry.rst:21 +msgid "" +"In addition to system measurements, the Telemetry module also captures event " +"notifications triggered when various actions are executed in the OpenStack " +"system. This data is captured as Events and stored alongside metering data." +msgstr "" + +#: ../telemetry.rst:26 +msgid "" +"The list of meters is continuously growing, which makes it possible to use " +"the data collected by Telemetry for different purposes, other than billing. " +"For example, the autoscaling feature in the Orchestration module can be " +"triggered by alarms this module sets and then gets notified within Telemetry." +msgstr "" + +#: ../telemetry.rst:32 +msgid "" +"The sections in this document contain information about the architecture and " +"usage of Telemetry. The first section contains a brief summary about the " +"system architecture used in a typical OpenStack deployment. The second " +"section describes the data collection mechanisms. You can also read about " +"alarming to understand how alarm definitions can be posted to Telemetry and " +"what actions can happen if an alarm is raised. The last section contains a " +"troubleshooting guide, which mentions error situations and possible " +"solutions to the problems." +msgstr "" + +#: ../telemetry.rst:42 +msgid "" +"You can retrieve the collected samples in three different ways: with the " +"REST API, with the command line interface, or with the Metering tab on an " +"OpenStack dashboard." +msgstr "" + +#: ../ts-HTTP-bad-req-in-cinder-vol-log.rst:6 +msgid "HTTP bad request in cinder volume log" +msgstr "" + +# #-#-#-#-# ts-duplicate-3par-host.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +# #-#-#-#-# ts-eql-volume-size.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +# #-#-#-#-# ts-failed-attach-vol-after-detach.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +# #-#-#-#-# ts-failed-attach-vol-no-sysfsutils.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +# #-#-#-#-# ts-failed-connect-vol-FC-SAN.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +# #-#-#-#-# ts-HTTP-bad-req-in-cinder-vol-log.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +# #-#-#-#-# ts_multipath_warn.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +# #-#-#-#-# ts_no_emulator_x86_64.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +# #-#-#-#-# ts_non_existent_host.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +# #-#-#-#-# ts_non_existent_vlun.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +# #-#-#-#-# ts_vol_attach_miss_sg_scan.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +#: ../ts-HTTP-bad-req-in-cinder-vol-log.rst:9 ../ts-duplicate-3par-host.rst:9 +#: ../ts-eql-volume-size.rst:9 ../ts-failed-attach-vol-after-detach.rst:9 +#: ../ts-failed-attach-vol-no-sysfsutils.rst:9 +#: ../ts-failed-connect-vol-FC-SAN.rst:9 ../ts_multipath_warn.rst:6 +#: ../ts_no_emulator_x86_64.rst:6 ../ts_non_existent_host.rst:6 +#: ../ts_non_existent_vlun.rst:6 ../ts_vol_attach_miss_sg_scan.rst:6 +msgid "Problem" +msgstr "" + +#: ../ts-HTTP-bad-req-in-cinder-vol-log.rst:11 +msgid "These errors appear in the :file:`cinder-volume.log` file::" +msgstr "" + +# #-#-#-#-# ts-duplicate-3par-host.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +# #-#-#-#-# ts-eql-volume-size.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +# #-#-#-#-# ts-failed-attach-vol-after-detach.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +# #-#-#-#-# ts-failed-attach-vol-no-sysfsutils.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +# #-#-#-#-# ts-failed-connect-vol-FC-SAN.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +# #-#-#-#-# ts-HTTP-bad-req-in-cinder-vol-log.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +# #-#-#-#-# ts_multipath_warn.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +# #-#-#-#-# ts_no_emulator_x86_64.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +# #-#-#-#-# ts_non_existent_host.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +# #-#-#-#-# ts_non_existent_vlun.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +# #-#-#-#-# ts_vol_attach_miss_sg_scan.pot (Cloud Administrator Guide 0.9) #-#-#-#-# +#: ../ts-HTTP-bad-req-in-cinder-vol-log.rst:44 +#: ../ts-duplicate-3par-host.rst:21 ../ts-eql-volume-size.rst:135 +#: ../ts-failed-attach-vol-after-detach.rst:14 +#: ../ts-failed-attach-vol-no-sysfsutils.rst:24 +#: ../ts-failed-connect-vol-FC-SAN.rst:27 ../ts_multipath_warn.rst:23 +#: ../ts_no_emulator_x86_64.rst:12 ../ts_non_existent_host.rst:19 +#: ../ts_non_existent_vlun.rst:18 ../ts_vol_attach_miss_sg_scan.rst:22 +msgid "Solution" +msgstr "" + +#: ../ts-HTTP-bad-req-in-cinder-vol-log.rst:46 +msgid "" +"You need to update your copy of the :file:`hp_3par_fc.py` driver which " +"contains the synchronization code." +msgstr "" + +#: ../ts-duplicate-3par-host.rst:6 +msgid "Duplicate 3PAR host" +msgstr "" + +#: ../ts-duplicate-3par-host.rst:11 +msgid "" +"This error may be caused by a volume being exported outside of OpenStack " +"using a host name different from the system name that OpenStack expects. " +"This error could be displayed with the IQN if the host was exported using " +"iSCSI::" +msgstr "" + +#: ../ts-duplicate-3par-host.rst:23 +msgid "" +"Change the 3PAR host name to match the one that OpenStack expects. The 3PAR " +"host constructed by the driver uses just the local hostname, not the fully " +"qualified domain name (FQDN) of the compute host. For example, if the FQDN " +"was *myhost.example.com*, just *myhost* would be used as the 3PAR hostname. " +"IP addresses are not allowed as host names on the 3PAR storage server." +msgstr "" + +#: ../ts-eql-volume-size.rst:6 +msgid "" +"Addressing discrepancies in reported volume sizes for EqualLogic storage" +msgstr "" + +#: ../ts-eql-volume-size.rst:11 +msgid "" +"There is a discrepancy between both the actual volume size in EqualLogic " +"(EQL) storage and the image size in the Image service, with what is reported " +"OpenStack database. This could lead to confusion if a user is creating " +"volumes from an image that was uploaded from an EQL volume (through the " +"Image service). The image size is slightly larger than the target volume " +"size; this is because EQL size reporting accounts for additional storage " +"used by EQL for internal volume metadata." +msgstr "" + +#: ../ts-eql-volume-size.rst:19 +msgid "To reproduce the issue follow the steps in the following procedure." +msgstr "" + +#: ../ts-eql-volume-size.rst:21 +msgid "" +"This procedure assumes that the EQL array is provisioned, and that " +"appropriate configuration settings have been included in :file:`/etc/cinder/" +"cinder.conf` to connect to the EQL array." +msgstr "" + +#: ../ts-eql-volume-size.rst:25 +msgid "" +"Create a new volume. Note the ID and size of the volume. In the following " +"example, the ID and size are ``74cf9c04-4543-47ae-a937-a9b7c6c921e7`` and " +"``1``, respectively:" +msgstr "" + +#: ../ts-eql-volume-size.rst:51 +msgid "" +"Verify the volume size on the EQL array by using its command-line interface." +msgstr "" + +#: ../ts-eql-volume-size.rst:54 +msgid "" +"The actual size (``VolReserve``) is 1.01 GB. The EQL Group Manager should " +"also report a volume size of 1.01 GB::" +msgstr "" + +#: ../ts-eql-volume-size.rst:82 +msgid "Create a new image from this volume:" +msgstr "" + +#: ../ts-eql-volume-size.rst:104 +msgid "" +"When you uploaded the volume in the previous step, the Image service " +"reported the volume's size as ``1`` (GB). However, when using ``glance image-" +"list`` to list the image, the displayed size is 1085276160 bytes, or roughly " +"1.01 GB:" +msgstr "" + +#: ../ts-eql-volume-size.rst:110 +msgid "Container Format" +msgstr "" + +#: ../ts-eql-volume-size.rst:110 +msgid "Disk Format" +msgstr "" + +#: ../ts-eql-volume-size.rst:110 +msgid "Size" +msgstr "" + +#: ../ts-eql-volume-size.rst:113 +msgid "*1085276160*" +msgstr "" + +#: ../ts-eql-volume-size.rst:113 +msgid "bare" +msgstr "" + +#: ../ts-eql-volume-size.rst:113 +msgid "image\\_from\\_volume1" +msgstr "" + +#: ../ts-eql-volume-size.rst:118 +msgid "" +"Create a new volume using the previous image (``image_id 3020a21d-ba37-4495 " +"-8899-07fc201161b9`` in this example) as the source. Set the target volume " +"size to 1 GB; this is the size reported by the ``cinder`` tool when you " +"uploaded the volume to the Image service:" +msgstr "" + +#: ../ts-eql-volume-size.rst:131 +msgid "" +"The attempt to create a new volume based on the size reported by the " +"``cinder`` tool will then fail." +msgstr "" + +#: ../ts-eql-volume-size.rst:137 +msgid "" +"To work around this problem, increase the target size of the new image to " +"the next whole number. In the problem example, you created a 1 GB volume to " +"be used as volume-backed image, so a new volume using this volume-backed " +"image should use a size of 2 GB:" +msgstr "" + +#: ../ts-eql-volume-size.rst:168 +msgid "" +"The dashboard suggests a suitable size when you create a new volume based on " +"a volume-backed image." +msgstr "" + +#: ../ts-eql-volume-size.rst:171 +msgid "You can then check this new volume into the EQL array::" +msgstr "" + +#: ../ts-failed-attach-vol-after-detach.rst:6 +msgid "Failed to attach volume after detaching" +msgstr "" + +#: ../ts-failed-attach-vol-after-detach.rst:11 +msgid "Failed to attach a volume after detaching the same volume." +msgstr "" + +#: ../ts-failed-attach-vol-after-detach.rst:16 +msgid "" +"You must change the device name on the ``nova-attach`` command. The VM might " +"not clean up after a ``nova-detach`` command runs. This example shows how " +"the ``nova-attach`` command fails when you use the ``vdb``, ``vdc``, or " +"``vdd`` device names::" +msgstr "" + +#: ../ts-failed-attach-vol-after-detach.rst:34 +msgid "" +"You might also have this problem after attaching and detaching the same " +"volume from the same VM with the same mount point multiple times. In this " +"case, restart the KVM host." +msgstr "" + +#: ../ts-failed-attach-vol-no-sysfsutils.rst:6 +msgid "Failed to attach volume, systool is not installed" +msgstr "" + +#: ../ts-failed-attach-vol-no-sysfsutils.rst:11 +msgid "" +"This warning and error occurs if you do not have the required ``sysfsutils`` " +"package installed on the compute node::" +msgstr "" + +#: ../ts-failed-attach-vol-no-sysfsutils.rst:26 +msgid "" +"Run the following command on the compute node to install the ``sysfsutils`` " +"packages::" +msgstr "" + +#: ../ts-failed-connect-vol-FC-SAN.rst:6 +msgid "Failed to connect volume in FC SAN" +msgstr "" + +#: ../ts-failed-connect-vol-FC-SAN.rst:11 +msgid "" +"Compute node failed to connect to a volume in a Fibre Channel (FC) SAN " +"configuration. The WWN may not be zoned correctly in your FC SAN that links " +"the compute host to the storage array::" +msgstr "" + +#: ../ts-failed-connect-vol-FC-SAN.rst:29 +msgid "" +"The network administrator must configure the FC SAN fabric by correctly " +"zoning the WWN (port names) from your compute node HBAs." +msgstr "" + +#: ../ts_cinder_config.rst:6 +msgid "Troubleshoot the Block Storage configuration" +msgstr "" + +#: ../ts_cinder_config.rst:8 +msgid "" +"Most Block Storage errors are caused by incorrect volume configurations that " +"result in volume creation failures. To resolve these failures, review these " +"logs:" +msgstr "" + +#: ../ts_cinder_config.rst:12 +msgid "cinder-api log (:file:`/var/log/cinder/api.log`)" +msgstr "" + +#: ../ts_cinder_config.rst:14 +msgid "cinder-volume log (:file:`/var/log/cinder/volume.log`)" +msgstr "" + +#: ../ts_cinder_config.rst:16 +msgid "" +"The cinder-api log is useful for determining if you have endpoint or " +"connectivity issues. If you send a request to create a volume and it fails, " +"review the cinder-api log to determine whether the request made it to the " +"Block Storage service. If the request is logged and you see no errors or " +"tracebacks, check the cinder-volume log for errors or tracebacks." +msgstr "" + +#: ../ts_cinder_config.rst:25 +msgid "Create commands are listed in the ``cinder-api`` log." +msgstr "" + +#: ../ts_cinder_config.rst:27 +msgid "" +"These entries in the :file:`cinder.openstack.common.log` file can be used to " +"assist in troubleshooting your block storage configuration." +msgstr "" + +#: ../ts_cinder_config.rst:105 +msgid "" +"These common issues might occur during configuration. To correct, use these " +"suggested solutions." +msgstr "" + +#: ../ts_cinder_config.rst:108 +msgid "Issues with ``state_path`` and ``volumes_dir`` settings." +msgstr "" + +#: ../ts_cinder_config.rst:110 +msgid "" +"The OpenStack Block Storage uses ``tgtd`` as the default iSCSI helper and " +"implements persistent targets. This means that in the case of a ``tgt`` " +"restart or even a node reboot your existing volumes on that node will be " +"restored automatically with their original IQN." +msgstr "" + +#: ../ts_cinder_config.rst:115 +msgid "" +"In order to make this possible the iSCSI target information needs to be " +"stored in a file on creation that can be queried in case of restart of the " +"``tgt daemon``. By default, Block Storage uses a ``state_path`` variable, " +"which if installing with Yum or APT should be set to :file:`/var/lib/cinder/" +"`. The next part is the ``volumes_dir`` variable, by default this just " +"simply appends a :file:`volumes` directory to the ``state_path``. The result " +"is a file-tree :file:`/var/lib/cinder/volumes/`." +msgstr "" + +#: ../ts_cinder_config.rst:124 +msgid "" +"While the installer should handle all this, it can go wrong. If you have " +"trouble creating volumes and this directory does not exist you should see an " +"error message in the ``cinder-volume`` log indicating that the " +"``volumes_dir`` does not exist, and it should provide information about " +"which path it was looking for." +msgstr "" + +#: ../ts_cinder_config.rst:130 +msgid "The persistent tgt include file." +msgstr "" + +#: ../ts_cinder_config.rst:132 +msgid "" +"Along with the ``volumes_dir`` option, the iSCSI target driver also needs to " +"be configured to look in the correct place for the persistent files. This is " +"a simple entry in the :file:`/etc/tgt/conf.d` file that you should have set " +"when you installed OpenStack. If issues occur, verify that you have a :file:" +"`/etc/tgt/conf.d/cinder.conf` file." +msgstr "" + +#: ../ts_cinder_config.rst:138 +msgid "If the file is not present, create it with this command" +msgstr "" + +#: ../ts_cinder_config.rst:144 +msgid "No sign of attach call in the ``cinder-api log``." +msgstr "" + +#: ../ts_cinder_config.rst:146 +msgid "" +"This is most likely going to be a minor adjustment to your :file:`nova.conf` " +"file. Make sure that your :file:`nova.conf` has this entry" +msgstr "" + +#: ../ts_cinder_config.rst:153 +msgid "" +"Failed to create iscsi target error in the :file:`cinder-volume.log` file." +msgstr "" + +#: ../ts_cinder_config.rst:162 +msgid "" +"You might see this error in :file:`cinder-volume.log` after trying to create " +"a volume that is 1 GB. To fix this issue:" +msgstr "" + +#: ../ts_cinder_config.rst:165 +msgid "" +"Change contents of the :file:`/etc/tgt/targets.conf` from ``include /etc/tgt/" +"conf.d/*.conf`` to ``include /etc/tgt/conf.d/cinder_tgt.conf``, as follows:" +msgstr "" + +#: ../ts_cinder_config.rst:175 +msgid "" +"Restart ``tgt`` and ``cinder-*`` services so they pick up the new " +"configuration." +msgstr "" + +#: ../ts_multipath_warn.rst:3 +msgid "Multipath call failed exit" +msgstr "" + +#: ../ts_multipath_warn.rst:8 +msgid "" +"Multipath call failed exit. This warning occurs in the Compute log if you do " +"not have the optional ``multipath-tools`` package installed on the compute " +"node. This is an optional package and the volume attachment does work " +"without the multipath tools installed. If the ``multipath-tools`` package is " +"installed on the compute node, it is used to perform the volume attachment. " +"The IDs in your message are unique to your system." +msgstr "" + +#: ../ts_multipath_warn.rst:25 +msgid "" +"Run the following command on the compute node to install the ``multipath-" +"tools`` packages." +msgstr "" + +#: ../ts_no_emulator_x86_64.rst:3 +msgid "Cannot find suitable emulator for x86_64" +msgstr "" + +#: ../ts_no_emulator_x86_64.rst:8 +msgid "" +"When you attempt to create a VM, the error shows the VM is in the ``BUILD`` " +"then ``ERROR`` state." +msgstr "" + +#: ../ts_no_emulator_x86_64.rst:14 +msgid "" +"On the KVM host, run ``cat /proc/cpuinfo``. Make sure the ``vmx`` or ``svm`` " +"flags are set." +msgstr "" + +#: ../ts_no_emulator_x86_64.rst:17 +msgid "" +"Follow the instructions in the `enabling KVM section `__ of the " +"Configuration Reference to enable hardware virtualization support in your " +"BIOS." +msgstr "" + +#: ../ts_non_existent_host.rst:3 +msgid "Non-existent host" +msgstr "" + +#: ../ts_non_existent_host.rst:8 +msgid "" +"This error could be caused by a volume being exported outside of OpenStack " +"using a host name different from the system name that OpenStack expects. " +"This error could be displayed with the IQN if the host was exported using " +"iSCSI." +msgstr "" + +#: ../ts_non_existent_host.rst:21 +msgid "" +"Host names constructed by the driver use just the local hostname, not the " +"fully qualified domain name (FQDN) of the Compute host. For example, if the " +"FQDN was **myhost.example.com**, just **myhost** would be used as the 3PAR " +"hostname. IP addresses are not allowed as host names on the 3PAR storage " +"server." +msgstr "" + +#: ../ts_non_existent_vlun.rst:3 +msgid "Non-existent VLUN" +msgstr "" + +#: ../ts_non_existent_vlun.rst:8 +msgid "" +"This error occurs if the 3PAR host exists with the correct host name that " +"the OpenStack Block Storage drivers expect but the volume was created in a " +"different Domain." +msgstr "" + +#: ../ts_non_existent_vlun.rst:20 +msgid "" +"The ``hp3par_domain`` configuration items either need to be updated to use " +"the domain the 3PAR host currently resides in, or the 3PAR host needs to be " +"moved to the domain that the volume was created in." +msgstr "" + +#: ../ts_vol_attach_miss_sg_scan.rst:3 +msgid "Failed to Attach Volume, Missing sg_scan" +msgstr "" + +#: ../ts_vol_attach_miss_sg_scan.rst:8 +msgid "" +"Failed to attach volume to an instance, ``sg_scan`` file not found. This " +"warning and error occur when the sg3-utils package is not installed on the " +"compute node. The IDs in your message are unique to your system:" +msgstr "" + +#: ../ts_vol_attach_miss_sg_scan.rst:25 +msgid "Run this command on the compute node to install the sg3-utils package:" msgstr "" diff --git a/doc/common-rst/source/locale/common-rst.pot b/doc/common-rst/source/locale/common-rst.pot index af51c04f38..501733b2b8 100644 --- a/doc/common-rst/source/locale/common-rst.pot +++ b/doc/common-rst/source/locale/common-rst.pot @@ -11,1059 +11,219 @@ msgstr "" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" -#: ../common/glossary.rst:2970 ../common/glossary.rst:2977 -#: ../common/glossary.rst:2984 ../common/glossary.rst:2986 -#: ../common/glossary.rst:2975 -msgid "(RADOS)" +#: ../common/app_support.rst:3 +msgid "Community support" msgstr "" -#: ../common/app_support.rst:233 ../common/app_support.rst:230 -#: ../common/app_support.rst:228 ../common/app_support.rst:234 -#: ../common/app_support.rst:236 ../common/app_support.rst:239 -#: ../common/app_support.rst:241 -msgid "" -"**CentOS, Fedora, and Red Hat Enterprise Linux:** https://www.rdoproject.org/" -msgstr "" - -#: ../common/support-compute.rst:91 -msgid "**Credential errors, 401, and 403 forbidden errors**" -msgstr "" - -#: ../common/app_support.rst:231 -msgid "**Debian:** http://wiki.debian.org/OpenStack" -msgstr "" - -#: ../common/app_support.rst:231 ../common/app_support.rst:228 -#: ../common/app_support.rst:226 ../common/app_support.rst:232 -#: ../common/app_support.rst:234 ../common/app_support.rst:237 -#: ../common/app_support.rst:239 -msgid "**Debian:** https://wiki.debian.org/OpenStack" -msgstr "" - -#: ../common/cli_manage_images.rst:232 -msgid "**Disk and CD-ROM bus model values**" -msgstr "" - -#: ../common/support-compute.rst:149 -msgid "**Empty log output for Linux instances**" -msgstr "" - -#: ../common/log_in_dashboard.rst:143 ../common/log_in_dashboard.rst:146 -#: ../common/log_in_dashboard.rst:142 ../common/log_in_dashboard.rst:141 -msgid "**Figure: Admin tab**" -msgstr "" - -#: ../common/log_in_dashboard.rst:68 ../common/log_in_dashboard.rst:70 -msgid "**Figure: Project tab**" -msgstr "" - -#: ../common/support-compute.rst:113 -msgid "**Instance errors**" -msgstr "" - -#: ../common/cli_install_openstack_command_line_clients.rst:56 -msgid "**MacOS**" -msgstr "" - -#: ../common/cli_install_openstack_command_line_clients.rst:62 -msgid "**Microsoft Windows**" -msgstr "" - -#: ../common/get_started_database_service.rst:17 -#: ../common/get_started_database_service.rst:16 -msgid "**Process flow example**" -msgstr "" - -#: ../common/cli_install_openstack_command_line_clients.rst:87 -msgid "**Red Hat Enterprise Linux, CentOS, or Fedora.**" -msgstr "" - -#: ../common/cli_install_openstack_command_line_clients.rst:101 -msgid "**SUSE Linux Enterprise Linux 11**" -msgstr "" - -#: ../common/cli_install_openstack_command_line_clients.rst:77 -msgid "**Ubuntu and Debian**" -msgstr "" - -#: ../common/app_support.rst:239 ../common/app_support.rst:236 -#: ../common/app_support.rst:234 ../common/app_support.rst:240 -#: ../common/app_support.rst:242 ../common/app_support.rst:245 -#: ../common/app_support.rst:247 -msgid "**Ubuntu:** https://wiki.ubuntu.com/ServerTeam/CloudArchive" -msgstr "" - -#: ../common/cli_manage_images.rst:251 -msgid "**VIF model values**" -msgstr "" - -#: ../common/app_support.rst:236 -msgid "" -"**openSUSE and SUSE Linux Enterprise Server:** http://en.opensuse.org/Portal:" -"OpenStack" -msgstr "" - -#: ../common/app_support.rst:236 ../common/app_support.rst:233 -#: ../common/app_support.rst:231 ../common/app_support.rst:237 -#: ../common/app_support.rst:239 ../common/app_support.rst:242 -#: ../common/app_support.rst:244 -msgid "" -"**openSUSE and SUSE Linux Enterprise Server:** https://en.opensuse.org/" -"Portal:OpenStack" -msgstr "" - -#: ../common/cli_install_openstack_command_line_clients.rst:127 -msgid "**openSUSE**" -msgstr "" - -#: ../common/get_started_storage_concepts.rst:44 -#: ../common/get_started_storage_concepts.rst:47 -#: ../common/get_started_storage_concepts.rst:46 -msgid "" -"*The OpenStack Image service is used to manage the virtual machine images in " -"an OpenStack cluster, not store them.* It provides an abstraction to " -"different methods for storage - a bridge to the storage, not the storage " -"itself." -msgstr "" - -#: ../common/get_started_storage_concepts.rst:49 -#: ../common/get_started_storage_concepts.rst:52 -#: ../common/get_started_storage_concepts.rst:51 -msgid "" -"*The OpenStack Object Storage can function on its own.* The Object Storage " -"(swift) product can be used independently of the Compute (nova) product." -msgstr "" - -#: ../common/get_started_storage_concepts.rst:36 -#: ../common/get_started_storage_concepts.rst:39 -#: ../common/get_started_storage_concepts.rst:38 -msgid "" -"*You cannot use OpenStack Object Storage like a traditional hard drive.* The " -"Object Storage relaxes some of the constraints of a POSIX-style file system " -"to get other gains. You can access the objects through an API which uses " -"HTTP. Subsequently you don't have to provide atomic operations (that is, " -"relying on eventual consistency), you can scale a storage system easily and " -"avoid a central point of failure." -msgstr "" - -#: ../common/glossary.rst:16 -msgid "6to4" -msgstr "" - -#: ../common/support-compute.rst:133 -msgid ":file:`console.log`, after the instance starts." -msgstr "" - -#: ../common/support-compute.rst:130 -msgid ":file:`disk-raw`" -msgstr "" - -#: ../common/support-compute.rst:129 -msgid ":file:`disk`" -msgstr "" - -#: ../common/support-compute.rst:131 -msgid ":file:`kernel`" -msgstr "" - -#: ../common/support-compute.rst:128 -msgid ":file:`libvirt.xml`" -msgstr "" - -#: ../common/support-compute.rst:132 -msgid ":file:`ramdisk`" -msgstr "" - -#: ../common/log_in_dashboard.rst:106 ../common/log_in_dashboard.rst:102 -#: ../common/log_in_dashboard.rst:104 -msgid ":guilabel:`API Access`: View API endpoints." -msgstr "" - -#: ../common/log_in_dashboard.rst:96 ../common/log_in_dashboard.rst:92 -#: ../common/log_in_dashboard.rst:94 -msgid "" -":guilabel:`Access & Security`: Use the following tabs to complete these " -"tasks:" -msgstr "" - -#: ../common/log_in_dashboard.rst:148 ../common/log_in_dashboard.rst:151 -msgid ":guilabel:`Admin` tab" -msgstr "" - -#: ../common/log_in_dashboard.rst:203 ../common/log_in_dashboard.rst:195 -#: ../common/log_in_dashboard.rst:201 ../common/log_in_dashboard.rst:200 -#: ../common/log_in_dashboard.rst:202 -msgid "" -":guilabel:`Block Storage Services`: View a list of all Block Storage " -"services." -msgstr "" - -#: ../common/log_in_dashboard.rst:219 ../common/log_in_dashboard.rst:225 -#: ../common/log_in_dashboard.rst:224 ../common/log_in_dashboard.rst:228 -msgid ":guilabel:`Change Password`: Change the password of the user." -msgstr "" - -#: ../common/log_in_dashboard.rst:191 ../common/log_in_dashboard.rst:194 -#: ../common/log_in_dashboard.rst:201 ../common/log_in_dashboard.rst:193 -#: ../common/log_in_dashboard.rst:199 ../common/log_in_dashboard.rst:198 -#: ../common/log_in_dashboard.rst:200 -msgid ":guilabel:`Compute Services`: View a list of all Compute services." -msgstr "" - -#: ../common/log_in_dashboard.rst:78 ../common/log_in_dashboard.rst:74 -#: ../common/log_in_dashboard.rst:76 -msgid ":guilabel:`Compute` tab" -msgstr "" - -#: ../common/log_in_dashboard.rst:122 ../common/log_in_dashboard.rst:118 -#: ../common/log_in_dashboard.rst:120 -msgid ":guilabel:`Containers`: Create and manage containers and objects." -msgstr "" - -#: ../common/log_in_dashboard.rst:161 ../common/log_in_dashboard.rst:164 -msgid ":guilabel:`Daily Report`: View the daily report." +#: ../common/app_support.rst:5 +msgid "Community Support" msgstr "" -#: ../common/log_in_dashboard.rst:195 ../common/log_in_dashboard.rst:198 +#: ../common/app_support.rst:5 ../common/app_support.rst:7 msgid "" -":guilabel:`Default Quotas`: View default quota values. Quotas are hard-coded " -"in OpenStack Compute and define the maximum allowable size and number of " -"resources." +"The following resources are available to help you run and use OpenStack. The " +"OpenStack community constantly improves and adds to the main features of " +"OpenStack, but if you have any questions, do not hesitate to ask. Use the " +"following resources to get OpenStack support, and troubleshoot your " +"installations." msgstr "" -#: ../common/log_in_dashboard.rst:189 ../common/log_in_dashboard.rst:181 -#: ../common/log_in_dashboard.rst:187 ../common/log_in_dashboard.rst:186 -#: ../common/log_in_dashboard.rst:188 -msgid "" -":guilabel:`Defaults`: View default quota values. Quotas are hard-coded in " -"OpenStack Compute and define the maximum allowable size and number of " -"resources." +#: ../common/app_support.rst:12 ../common/app_support.rst:14 +msgid "Documentation" msgstr "" -#: ../common/log_in_dashboard.rst:176 ../common/log_in_dashboard.rst:179 -#: ../common/log_in_dashboard.rst:171 ../common/log_in_dashboard.rst:177 -#: ../common/log_in_dashboard.rst:178 +#: ../common/app_support.rst:14 ../common/app_support.rst:16 msgid "" -":guilabel:`Flavors`: View, create, edit, view extra specifications for, and " -"delete flavors. A flavor is size of an instance." +"For the available OpenStack documentation, see `docs.openstack.org `__." msgstr "" -#: ../common/log_in_dashboard.rst:103 ../common/log_in_dashboard.rst:99 -#: ../common/log_in_dashboard.rst:101 +#: ../common/app_support.rst:17 ../common/app_support.rst:19 +#: ../common/app_support.rst:213 ../common/app_support.rst:215 +#: ../common/app_support.rst:218 ../common/app_support.rst:219 +#: ../common/app_support.rst:221 ../common/app_support.rst:224 +#: ../common/app_support.rst:226 ../common/get_started_feedback.rst:5 +#: ../common/get_started_with_openstack.rst:143 msgid "" -":guilabel:`Floating IPs`: Allocate an IP address to or release it from a " -"project." +"To provide feedback on documentation, join and use the openstack-docs@lists." +"openstack.org mailing list at `OpenStack Documentation Mailing List `__, or `report " +"a bug `__." msgstr "" -#: ../common/log_in_dashboard.rst:167 ../common/log_in_dashboard.rst:170 -#: ../common/log_in_dashboard.rst:162 ../common/log_in_dashboard.rst:161 -#: ../common/log_in_dashboard.rst:163 +#: ../common/app_support.rst:24 ../common/app_support.rst:26 msgid "" -":guilabel:`Host Aggregates`: View, create, and edit host aggregates. View " -"the list of availability zones." -msgstr "" - -#: ../common/log_in_dashboard.rst:165 ../common/log_in_dashboard.rst:168 -#: ../common/log_in_dashboard.rst:160 ../common/log_in_dashboard.rst:159 -#: ../common/log_in_dashboard.rst:161 -msgid ":guilabel:`Hypervisors`: View the hypervisor summary." -msgstr "" - -#: ../common/log_in_dashboard.rst:201 ../common/log_in_dashboard.rst:204 -#: ../common/log_in_dashboard.rst:213 -msgid ":guilabel:`Identity Panel` tab" +"The following books explain how to install an OpenStack cloud and its " +"associated components:" msgstr "" -#: ../common/log_in_dashboard.rst:92 ../common/log_in_dashboard.rst:88 -#: ../common/log_in_dashboard.rst:90 +#: ../common/app_support.rst:27 ../common/app_support.rst:29 msgid "" -":guilabel:`Images`: View images and instance snapshots created by project " -"users, plus any images that are publicly available. Create, edit, and delete " -"images, and launch instances from images and snapshots." +"`Installation Guide for openSUSE 13.2 and SUSE Linux Enterprise Server 12 " +"`__" msgstr "" -#: ../common/log_in_dashboard.rst:179 ../common/log_in_dashboard.rst:182 -#: ../common/log_in_dashboard.rst:174 ../common/log_in_dashboard.rst:180 -#: ../common/log_in_dashboard.rst:181 +#: ../common/app_support.rst:31 ../common/app_support.rst:33 msgid "" -":guilabel:`Images`: View, create, edit properties for, and delete custom " -"images." +"`Installation Guide for Red Hat Enterprise Linux 7, CentOS 7, and Fedora 21 " +"`__" msgstr "" -#: ../common/log_in_dashboard.rst:82 ../common/log_in_dashboard.rst:78 -#: ../common/log_in_dashboard.rst:80 +#: ../common/app_support.rst:35 ../common/app_support.rst:37 msgid "" -":guilabel:`Instances`: View, launch, create a snapshot from, stop, pause, or " -"reboot instances, or connect to them through VNC." +"`Installation Guide for Ubuntu 14.04 `__" msgstr "" -#: ../common/log_in_dashboard.rst:170 ../common/log_in_dashboard.rst:173 -#: ../common/log_in_dashboard.rst:165 ../common/log_in_dashboard.rst:164 -#: ../common/log_in_dashboard.rst:166 +#: ../common/app_support.rst:38 ../common/app_support.rst:40 msgid "" -":guilabel:`Instances`: View, pause, resume, suspend, migrate, soft or hard " -"reboot, and delete running instances that belong to users of some, but not " -"all, projects. Also, view the log for an instance or access an instance " -"through VNC." +"The following books explain how to configure and run an OpenStack cloud:" msgstr "" -#: ../common/log_in_dashboard.rst:101 ../common/log_in_dashboard.rst:97 -#: ../common/log_in_dashboard.rst:99 +#: ../common/app_support.rst:40 ../common/app_support.rst:42 msgid "" -":guilabel:`Key Pairs`: View, create, edit, import, and delete key pairs." +"`Architecture Design Guide `__" msgstr "" -#: ../common/log_in_dashboard.rst:193 ../common/log_in_dashboard.rst:185 -#: ../common/log_in_dashboard.rst:191 ../common/log_in_dashboard.rst:190 -#: ../common/log_in_dashboard.rst:192 +#: ../common/app_support.rst:43 msgid "" -":guilabel:`Metadata Definitions`: Import namespace and view the metadata " -"information." +"`Cloud Administrator Guide `__" msgstr "" -#: ../common/log_in_dashboard.rst:193 ../common/log_in_dashboard.rst:196 -#: ../common/log_in_dashboard.rst:206 ../common/log_in_dashboard.rst:198 -#: ../common/log_in_dashboard.rst:204 ../common/log_in_dashboard.rst:203 -#: ../common/log_in_dashboard.rst:205 -msgid ":guilabel:`Network Agents`: View the network agents." -msgstr "" - -#: ../common/log_in_dashboard.rst:112 ../common/log_in_dashboard.rst:108 -#: ../common/log_in_dashboard.rst:110 -msgid ":guilabel:`Network Topology`: View the network topology." -msgstr "" - -#: ../common/log_in_dashboard.rst:110 ../common/log_in_dashboard.rst:106 -#: ../common/log_in_dashboard.rst:108 -msgid ":guilabel:`Network` tab" -msgstr "" - -#: ../common/log_in_dashboard.rst:114 ../common/log_in_dashboard.rst:110 -#: ../common/log_in_dashboard.rst:112 -msgid ":guilabel:`Networks`: Create and manage public and private networks." -msgstr "" - -#: ../common/log_in_dashboard.rst:182 ../common/log_in_dashboard.rst:185 -#: ../common/log_in_dashboard.rst:177 ../common/log_in_dashboard.rst:183 -#: ../common/log_in_dashboard.rst:184 +#: ../common/app_support.rst:43 ../common/app_support.rst:45 msgid "" -":guilabel:`Networks`: View, create, edit properties for, and delete networks." -msgstr "" - -#: ../common/log_in_dashboard.rst:120 ../common/log_in_dashboard.rst:116 -#: ../common/log_in_dashboard.rst:118 -msgid ":guilabel:`Object Store` tab" +"`Cloud Administrator Guide `__" msgstr "" -#: ../common/log_in_dashboard.rst:208 ../common/log_in_dashboard.rst:200 -#: ../common/log_in_dashboard.rst:206 ../common/log_in_dashboard.rst:205 -#: ../common/log_in_dashboard.rst:207 +#: ../common/app_support.rst:46 ../common/app_support.rst:48 msgid "" -":guilabel:`Orchestration Services`: View a list of all Orchestration " -"services." +"`Configuration Reference `__" msgstr "" -#: ../common/log_in_dashboard.rst:126 ../common/log_in_dashboard.rst:122 -#: ../common/log_in_dashboard.rst:124 -msgid ":guilabel:`Orchestration` tab" +#: ../common/app_support.rst:49 ../common/app_support.rst:51 +msgid "`Operations Guide `__" msgstr "" -#: ../common/log_in_dashboard.rst:156 ../common/log_in_dashboard.rst:159 -#: ../common/log_in_dashboard.rst:151 ../common/log_in_dashboard.rst:150 -#: ../common/log_in_dashboard.rst:152 -msgid ":guilabel:`Overview`: View basic reports." +#: ../common/app_support.rst:51 ../common/app_support.rst:53 +msgid "`Networking Guide `__" msgstr "" -#: ../common/log_in_dashboard.rst:80 ../common/log_in_dashboard.rst:76 -#: ../common/log_in_dashboard.rst:78 -msgid ":guilabel:`Overview`: View reports for the project." -msgstr "" - -#: ../common/log_in_dashboard.rst:72 -msgid ":guilabel:`Project` tab" -msgstr "" - -#: ../common/log_in_dashboard.rst:203 ../common/log_in_dashboard.rst:206 -#: ../common/log_in_dashboard.rst:215 ../common/log_in_dashboard.rst:212 -#: ../common/log_in_dashboard.rst:211 +#: ../common/app_support.rst:53 ../common/app_support.rst:55 msgid "" -":guilabel:`Projects`: View, create, assign users to, remove users from, and " -"delete projects." +"`High Availability Guide `__" msgstr "" -#: ../common/log_in_dashboard.rst:131 ../common/log_in_dashboard.rst:127 -#: ../common/log_in_dashboard.rst:129 -msgid "" -":guilabel:`Resource Types`: Show a list of all the supported resource types " -"for HOT templates." +#: ../common/app_support.rst:56 ../common/app_support.rst:58 +msgid "`Security Guide `__" msgstr "" -#: ../common/log_in_dashboard.rst:158 ../common/log_in_dashboard.rst:161 -#: ../common/log_in_dashboard.rst:153 ../common/log_in_dashboard.rst:152 -#: ../common/log_in_dashboard.rst:154 +#: ../common/app_support.rst:58 ../common/app_support.rst:60 msgid "" -":guilabel:`Resource Usage`: Use the following tabs to view the following " -"usages:" +"`Virtual Machine Image Guide `__" msgstr "" -#: ../common/log_in_dashboard.rst:116 ../common/log_in_dashboard.rst:112 -#: ../common/log_in_dashboard.rst:114 -msgid ":guilabel:`Routers`: Create and manage routers." -msgstr "" - -#: ../common/log_in_dashboard.rst:116 -msgid ":guilabel:`Routers`: Create and manage subnets." -msgstr "" - -#: ../common/log_in_dashboard.rst:184 ../common/log_in_dashboard.rst:187 -#: ../common/log_in_dashboard.rst:179 ../common/log_in_dashboard.rst:185 -#: ../common/log_in_dashboard.rst:186 +#: ../common/app_support.rst:61 ../common/app_support.rst:63 msgid "" -":guilabel:`Routers`: View, create, edit properties for, and delete routers." +"The following books explain how to use the OpenStack dashboard and command-" +"line clients:" msgstr "" -#: ../common/log_in_dashboard.rst:98 ../common/log_in_dashboard.rst:94 -#: ../common/log_in_dashboard.rst:96 +#: ../common/app_support.rst:64 ../common/app_support.rst:66 msgid "" -":guilabel:`Security Groups`: View, create, edit, and delete security groups " -"and security group rules." +"`API Quick Start `__" msgstr "" -#: ../common/log_in_dashboard.rst:189 ../common/log_in_dashboard.rst:192 -#: ../common/log_in_dashboard.rst:199 ../common/log_in_dashboard.rst:191 -#: ../common/log_in_dashboard.rst:197 ../common/log_in_dashboard.rst:196 -#: ../common/log_in_dashboard.rst:198 -msgid ":guilabel:`Services`: View a list of the services." +#: ../common/app_support.rst:67 ../common/app_support.rst:69 +msgid "`End User Guide `__" msgstr "" -#: ../common/log_in_dashboard.rst:128 ../common/log_in_dashboard.rst:124 -#: ../common/log_in_dashboard.rst:126 -msgid "" -":guilabel:`Stacks`: Use the REST API to orchestrate multiple composite cloud " -"applications." +#: ../common/app_support.rst:69 ../common/app_support.rst:71 +msgid "`Admin User Guide `__" msgstr "" -#: ../common/log_in_dashboard.rst:163 ../common/log_in_dashboard.rst:166 -#: ../common/log_in_dashboard.rst:158 ../common/log_in_dashboard.rst:157 -#: ../common/log_in_dashboard.rst:159 -msgid ":guilabel:`Stats`: View the statistics of all resources." -msgstr "" - -#: ../common/log_in_dashboard.rst:186 ../common/log_in_dashboard.rst:189 +#: ../common/app_support.rst:72 ../common/app_support.rst:74 msgid "" -":guilabel:`System Info`: Use the following tabs to view the service " -"information:" +"`Command-Line Interface Reference `__" msgstr "" -#: ../common/log_in_dashboard.rst:189 ../common/log_in_dashboard.rst:196 -#: ../common/log_in_dashboard.rst:188 ../common/log_in_dashboard.rst:194 -#: ../common/log_in_dashboard.rst:193 ../common/log_in_dashboard.rst:195 +#: ../common/app_support.rst:75 ../common/app_support.rst:77 msgid "" -":guilabel:`System Information`: Use the following tabs to view the service " -"information:" -msgstr "" - -#: ../common/log_in_dashboard.rst:154 ../common/log_in_dashboard.rst:157 -#: ../common/log_in_dashboard.rst:149 -msgid ":guilabel:`System Panel` tab" -msgstr "" - -#: ../common/log_in_dashboard.rst:149 ../common/log_in_dashboard.rst:148 -#: ../common/log_in_dashboard.rst:150 -msgid ":guilabel:`System` tab" +"The following documentation provides reference and guidance information for " +"the OpenStack APIs:" msgstr "" -#: ../common/log_in_dashboard.rst:164 ../common/log_in_dashboard.rst:156 -#: ../common/log_in_dashboard.rst:155 ../common/log_in_dashboard.rst:157 -msgid ":guilabel:`Usage Report`: View the usage report." -msgstr "" - -#: ../common/log_in_dashboard.rst:217 ../common/log_in_dashboard.rst:223 -#: ../common/log_in_dashboard.rst:222 ../common/log_in_dashboard.rst:226 -msgid ":guilabel:`User Settings`: View and manage dashboard settings." -msgstr "" - -#: ../common/log_in_dashboard.rst:206 ../common/log_in_dashboard.rst:209 -#: ../common/log_in_dashboard.rst:218 ../common/log_in_dashboard.rst:215 -#: ../common/log_in_dashboard.rst:214 -msgid ":guilabel:`Users`: View, create, enable, disable, and delete users." -msgstr "" - -#: ../common/log_in_dashboard.rst:89 ../common/log_in_dashboard.rst:85 -#: ../common/log_in_dashboard.rst:87 +#: ../common/app_support.rst:78 ../common/app_support.rst:80 msgid "" -":guilabel:`Volume Snapshots`: View, create, edit, and delete volume " -"snapshots." +"`OpenStack API Complete Reference (HTML) `__" msgstr "" -#: ../common/log_in_dashboard.rst:175 ../common/log_in_dashboard.rst:174 -#: ../common/log_in_dashboard.rst:176 +#: ../common/app_support.rst:81 ../common/app_support.rst:83 msgid "" -":guilabel:`Volume Snapshots`: View, manage, and delete volume snapshots." +"`API Complete Reference (PDF) `__" msgstr "" -#: ../common/log_in_dashboard.rst:173 ../common/log_in_dashboard.rst:172 -#: ../common/log_in_dashboard.rst:174 +#: ../common/app_support.rst:86 msgid "" -":guilabel:`Volume Types`: View, create, manage, and delete volume types." +"The `Training Guides `__ " +"offer software training for cloud administration and management." msgstr "" -#: ../common/log_in_dashboard.rst:85 ../common/log_in_dashboard.rst:81 -#: ../common/log_in_dashboard.rst:169 ../common/log_in_dashboard.rst:168 -#: ../common/log_in_dashboard.rst:83 ../common/log_in_dashboard.rst:170 -msgid ":guilabel:`Volumes`: Use the following tabs to complete these tasks:" +#: ../common/app_support.rst:86 ../common/app_support.rst:88 +#: ../common/app_support.rst:91 +msgid "ask.openstack.org" msgstr "" -#: ../common/log_in_dashboard.rst:174 ../common/log_in_dashboard.rst:177 -#: ../common/log_in_dashboard.rst:169 +#: ../common/app_support.rst:88 ../common/app_support.rst:90 +#: ../common/app_support.rst:93 msgid "" -":guilabel:`Volumes`: View, create, edit, and delete volumes and volume types." -msgstr "" - -#: ../common/log_in_dashboard.rst:87 ../common/log_in_dashboard.rst:83 -#: ../common/log_in_dashboard.rst:85 -msgid ":guilabel:`Volumes`: View, create, edit, and delete volumes." -msgstr "" - -#: ../common/log_in_dashboard.rst:171 ../common/log_in_dashboard.rst:170 -#: ../common/log_in_dashboard.rst:172 -msgid ":guilabel:`Volumes`: View, create, manage, and delete volumes." +"During the set up or testing of OpenStack, you might have questions about " +"how a specific task is completed or be in a situation where a feature does " +"not work correctly. Use the `ask.openstack.org `__ site to ask questions and get answers. When you visit the https://" +"ask.openstack.org site, scan the recently asked questions to see whether " +"your question has already been answered. If not, ask a new question. Be sure " +"to give a clear, concise summary in the title and provide as much detail as " +"possible in the description. Paste in your command output or stack traces, " +"links to screen shots, and any other information which might be useful." msgstr "" -#: ../common/glossary.rst:2503 ../common/glossary.rst:2510 -#: ../common/glossary.rst:2509 ../common/glossary.rst:2515 -#: ../common/glossary.rst:2517 ../common/glossary.rst:2506 -msgid "A BLOB of data held by Object Storage; can be in any format." -msgstr "" - -#: ../common/glossary.rst:3722 ../common/glossary.rst:3729 -#: ../common/glossary.rst:3736 ../common/glossary.rst:3744 -#: ../common/glossary.rst:3733 -msgid "" -"A Block Storage component that creates, attaches, and detaches persistent " -"storage volumes." -msgstr "" - -#: ../common/glossary.rst:3708 ../common/glossary.rst:3715 -#: ../common/glossary.rst:3722 ../common/glossary.rst:3730 -#: ../common/glossary.rst:3719 -msgid "" -"A Block Storage component that oversees and coordinates storage volume " -"actions." -msgstr "" - -#: ../common/glossary.rst:3727 ../common/glossary.rst:3734 -#: ../common/glossary.rst:3741 ../common/glossary.rst:3749 -#: ../common/glossary.rst:3738 -msgid "A Block Storage node that runs the cinder-volume daemon." -msgstr "" - -#: ../common/glossary.rst:3792 ../common/glossary.rst:3799 -#: ../common/glossary.rst:3806 ../common/glossary.rst:3814 -#: ../common/glossary.rst:3803 -msgid "" -"A Block Storage volume plug-in that enables communication with the Xen " -"Storage Manager API." -msgstr "" - -#: ../common/get_started_database_service.rst:46 -#: ../common/get_started_database_service.rst:45 -msgid "A CLI that communicates with the ``trove-api`` component." -msgstr "" - -#: ../common/get_started_orchestration.rst:22 -#: ../common/get_started_orchestration.rst:21 -msgid "" -"A CLI that communicates with the heat-api to run AWS CloudFormation APIs. " -"End developers can directly use the Orchestration REST API." -msgstr "" - -#: ../common/glossary.rst:2328 ../common/glossary.rst:2335 -#: ../common/glossary.rst:2334 ../common/glossary.rst:2340 -#: ../common/glossary.rst:2329 -msgid "" -"A Ceph component that communicates with external clients, checks data state " -"and consistency, and performs quorum functions." -msgstr "" - -#: ../common/glossary.rst:659 +#: ../common/app_support.rst:93 msgid "" -"A Compute API parameter that downloads changes to the requested item since " -"your last request, instead of downloading a new, fresh set of data and " -"comparing it against the old data." +"During the set up or testing of OpenStack, you might have questions about " +"how a specific task is completed or be in a situation where a feature does " +"not work correctly. Use the `ask.openstack.org `__ " +"site to ask questions and get answers. When you visit the http://ask." +"openstack.org site, scan the recently asked questions to see whether your " +"question has already been answered. If not, ask a new question. Be sure to " +"give a clear, concise summary in the title and provide as much detail as " +"possible in the description. Paste in your command output or stack traces, " +"links to screen shots, and any other information which might be useful." msgstr "" -#: ../common/glossary.rst:1224 ../common/glossary.rst:1225 -msgid "" -"A Compute RabbitMQ message queue that remains active when the server " -"restarts." -msgstr "" - -#: ../common/glossary.rst:347 -msgid "" -"A Compute RabbitMQ setting that determines whether a message exchange is " -"automatically created when the program starts." -msgstr "" - -#: ../common/glossary.rst:580 -msgid "" -"A Compute back-end database table that contains the current workload, amount " -"of free RAM, and number of VMs running on each host. Used to determine on " -"which VM a host starts." -msgstr "" - -#: ../common/glossary.rst:3111 ../common/glossary.rst:3118 -#: ../common/glossary.rst:3125 ../common/glossary.rst:3127 -#: ../common/glossary.rst:3116 -msgid "" -"A Compute component that determines where VM instances should start. Uses " -"modular design to support a variety of scheduler types." -msgstr "" - -#: ../common/glossary.rst:1271 ../common/glossary.rst:1272 -msgid "" -"A Compute component that enables OpenStack to communicate with Amazon EC2." -msgstr "" - -#: ../common/glossary.rst:2497 ../common/glossary.rst:2504 -#: ../common/glossary.rst:2503 ../common/glossary.rst:2509 -#: ../common/glossary.rst:2511 ../common/glossary.rst:2500 -msgid "" -"A Compute component that manages IP address allocation, firewalls, and other " -"network-related tasks. This is the legacy networking option and an " -"alternative to Networking." -msgstr "" - -#: ../common/glossary.rst:3657 ../common/glossary.rst:3664 -#: ../common/glossary.rst:3671 ../common/glossary.rst:3679 -#: ../common/glossary.rst:3668 -msgid "" -"A Compute component that provides dnsmasq and radvd and sets up forwarding " -"to and from cloudpipe instances." -msgstr "" - -#: ../common/glossary.rst:3693 ../common/glossary.rst:3700 -#: ../common/glossary.rst:3707 ../common/glossary.rst:3715 -#: ../common/glossary.rst:3704 -msgid "" -"A Compute component that provides users access to the consoles of their VM " -"instances through VNC or VMRC." -msgstr "" - -#: ../common/glossary.rst:3425 ../common/glossary.rst:3432 -#: ../common/glossary.rst:3439 ../common/glossary.rst:3447 -#: ../common/glossary.rst:3436 -msgid "" -"A Compute component that, along with the notification system, collects " -"meters and usage information. This information can be used for billing." -msgstr "" - -#: ../common/glossary.rst:2380 ../common/glossary.rst:2387 -#: ../common/glossary.rst:2386 ../common/glossary.rst:2392 -#: ../common/glossary.rst:2393 ../common/glossary.rst:2382 -msgid "" -"A Compute daemon that orchestrates the network configuration of nodes, " -"including IP addresses, VLANs, and bridging. Also manages routing for both " -"public and private networks." -msgstr "" - -#: ../common/glossary.rst:1481 ../common/glossary.rst:1482 -msgid "" -"A Compute networking method where the OS network configuration information " -"is injected into the VM image before the instance starts." -msgstr "" - -#: ../common/glossary.rst:619 -msgid "" -"A Compute option that enables parent cells to pass resource requests to " -"child cells if the parent cannot provide the requested resource." -msgstr "" - -#: ../common/glossary.rst:3746 ../common/glossary.rst:3753 -#: ../common/glossary.rst:3760 ../common/glossary.rst:3768 -#: ../common/glossary.rst:3757 -msgid "" -"A Compute process that determines the suitability of the VM instances for a " -"job for a particular host. For example, not enough RAM on the host, too many " -"CPUs on the host, and so on." -msgstr "" - -#: ../common/glossary.rst:3530 ../common/glossary.rst:3537 -#: ../common/glossary.rst:3544 ../common/glossary.rst:3552 -#: ../common/glossary.rst:3541 -msgid "A Debian-based Linux distribution." -msgstr "" - -#: ../common/support-compute.rst:49 -msgid "" -"A Guru Meditation report is sent by the Compute Service upon receipt of the " -"``SIGUSR1`` signal. This report is a general-purpose error report, including " -"a complete report of the service's current state, and is sent to ``stderr``." -msgstr "" - -#: ../common/support-compute.rst:49 -msgid "" -"A Guru Meditation report is sent by the Compute service upon receipt of the " -"``SIGUSR1`` signal. This report is a general-purpose error report, including " -"a complete report of the service's current state, and is sent to ``stderr``." -msgstr "" - -#: ../common/glossary.rst:220 -msgid "A Java program that can be embedded into a web page." -msgstr "" - -#: ../common/glossary.rst:1434 ../common/glossary.rst:1435 -msgid "A Linux distribution compatible with OpenStack." -msgstr "" - -#: ../common/glossary.rst:631 ../common/glossary.rst:1004 -#: ../common/glossary.rst:2614 ../common/glossary.rst:2948 -#: ../common/glossary.rst:3370 ../common/glossary.rst:2621 -#: ../common/glossary.rst:2955 ../common/glossary.rst:3377 -#: ../common/glossary.rst:2627 ../common/glossary.rst:2962 -#: ../common/glossary.rst:3384 ../common/glossary.rst:2629 -#: ../common/glossary.rst:2964 ../common/glossary.rst:3392 -#: ../common/glossary.rst:2618 ../common/glossary.rst:2953 -#: ../common/glossary.rst:3381 -msgid "A Linux distribution that is compatible with OpenStack." -msgstr "" - -#: ../common/glossary.rst:1463 ../common/glossary.rst:1464 -msgid "A Networking extension that provides perimeter firewall functionality." -msgstr "" - -#: ../common/glossary.rst:688 -msgid "" -"A Networking plug-in for Cisco devices and technologies, including UCS and " -"Nexus." -msgstr "" - -#: ../common/glossary.rst:56 -msgid "" -"A SQLite database that contains Object Storage accounts and related metadata " -"and that the accounts server accesses." -msgstr "" - -#: ../common/glossary.rst:852 -msgid "" -"A SQLite database that stores Object Storage containers and container " -"metadata. The container server accesses this database." -msgstr "" - -#: ../common/glossary.rst:1317 ../common/glossary.rst:1318 -msgid "" -"A VM image that does not save changes made to its volumes and reverts them " -"to their original state after the instance is terminated." -msgstr "" - -#: ../common/glossary.rst:2465 ../common/glossary.rst:2472 -#: ../common/glossary.rst:2471 ../common/glossary.rst:2477 -#: ../common/glossary.rst:2479 ../common/glossary.rst:2468 -msgid "A VM instance that runs on a host." -msgstr "" - -#: ../common/glossary.rst:2666 ../common/glossary.rst:2673 -#: ../common/glossary.rst:2679 ../common/glossary.rst:2681 -#: ../common/glossary.rst:2670 -msgid "" -"A VM state where no changes occur (no changes in memory, network " -"communications stop, etc); the VM is frozen but not shut down." -msgstr "" - -#: ../common/glossary.rst:740 -msgid "" -"A Windows project providing guest initialization features, similar to cloud-" -"init." -msgstr "" - -#: ../common/glossary.rst:3339 ../common/glossary.rst:3346 -#: ../common/glossary.rst:3353 ../common/glossary.rst:3361 -#: ../common/glossary.rst:3350 -msgid "" -"A XenAPI component that provides a pluggable interface to support a wide " -"variety of persistent storage back ends." -msgstr "" - -#: ../common/glossary.rst:443 -msgid "" -"A bit is a single digit number that is in base of 2 (either a zero or one). " -"Bandwidth usage is measured in bits per second." -msgstr "" - -#: ../common/glossary.rst:3549 ../common/glossary.rst:3556 -#: ../common/glossary.rst:3563 ../common/glossary.rst:3571 -#: ../common/glossary.rst:3560 -msgid "" -"A blob of data that the user can specify when they launch an instance. The " -"instance can access this data through the metadata service or config drive. " -"Commonly used to pass a shell script that the instance runs on boot." -msgstr "" - -#: ../common/get_started_telemetry.rst:28 -#: ../common/get_started_telemetry.rst:27 -msgid "A central agent (``ceilometer-agent-central``)" -msgstr "" - -#: ../common/get_started_compute.rst:125 ../common/get_started_compute.rst:124 -msgid "" -"A central hub for passing messages between daemons. Usually implemented with " -"`RabbitMQ `__, but can be implemented with an AMQP " -"message queue, such as `Apache Qpid `__ or `Zero MQ " -"`__." -msgstr "" - -#: ../common/get_started_identity.rst:20 -msgid "" -"A centralized server provides authentication and authorization services " -"using a RESTful interface." -msgstr "" - -#: ../common/glossary.rst:3736 ../common/glossary.rst:3743 -#: ../common/glossary.rst:3750 ../common/glossary.rst:3758 -#: ../common/glossary.rst:3747 -msgid "" -"A cinder component that interacts with back-end storage to manage the " -"creation and deletion of volumes and the creation of compute volumes, " -"provided by the cinder-volume daemon." -msgstr "" - -#: ../common/get_started_storage_concepts.rst:64 -#: ../common/get_started_storage_concepts.rst:67 -#: ../common/get_started_storage_concepts.rst:66 -#: ../common/get_started_object_storage.rst:46 -msgid "" -"A cli tool used to retrieve various metrics and telemetry information about " -"a cluster, that has been collected by the swift-recon middleware." -msgstr "" - -#: ../common/glossary.rst:1358 ../common/glossary.rst:1359 -msgid "" -"A collection of command-line tools for administering VMs; most are " -"compatible with OpenStack." -msgstr "" - -#: ../common/glossary.rst:2972 ../common/glossary.rst:2979 -#: ../common/glossary.rst:2986 ../common/glossary.rst:2988 -#: ../common/glossary.rst:2977 -msgid "" -"A collection of components that provides object storage within Ceph. Similar " -"to OpenStack Object Storage." -msgstr "" - -#: ../common/glossary.rst:1808 ../common/glossary.rst:1814 -msgid "" -"A collection of files for a specific operating system (OS) that you use to " -"create or rebuild a server. OpenStack provides pre-built images. You can " -"also create custom images, or snapshots, from servers that you have " -"launched. Custom images can be used for data backups or as \"gold\" images " -"for additional servers." -msgstr "" - -#: ../common/glossary.rst:1744 ../common/glossary.rst:1750 -msgid "A collection of hypervisors grouped together through host aggregates." -msgstr "" - -#: ../common/glossary.rst:3234 ../common/glossary.rst:3241 -#: ../common/glossary.rst:3248 ../common/glossary.rst:3256 -#: ../common/glossary.rst:3245 -msgid "" -"A collection of servers that can share IPs with other members of the group. " -"Any server in a group can share one or more public IPs with any other server " -"in the group. With the exception of the first server in a shared IP group, " -"servers must be launched into shared IP groups. A server may be a member of " -"only one shared IP group." -msgstr "" - -#: ../common/glossary.rst:224 -msgid "" -"A collection of specifications used to access a service, application, or " -"program. Includes service calls, required parameters for each call, and the " -"expected return values." -msgstr "" - -#: ../common/get_started_telemetry.rst:37 -#: ../common/get_started_telemetry.rst:36 -msgid "A collector (``ceilometer-collector``)" -msgstr "" - -#: ../common/get_started_identity.rst:80 ../common/get_started_identity.rst:79 -msgid "" -"A command line interface for the OpenStack Identity API. For example, users " -"can run the ``keystone service-create`` and ``keystone endpoint-create`` " -"commands to register services in their OpenStack installations." -msgstr "" - -#: ../common/glossary.rst:1872 ../common/glossary.rst:1878 -msgid "" -"A community project may be elevated to this status and is then promoted to a " -"core project." -msgstr "" - -#: ../common/get_started_telemetry.rst:23 -#: ../common/get_started_telemetry.rst:22 -msgid "A compute agent (``ceilometer-agent-compute``)" -msgstr "" - -#: ../common/glossary.rst:745 -msgid "A compute service that creates VPNs on a per-project basis." -msgstr "" - -#: ../common/glossary.rst:2513 ../common/glossary.rst:2520 -#: ../common/glossary.rst:2519 ../common/glossary.rst:2525 -#: ../common/glossary.rst:2527 ../common/glossary.rst:2516 -msgid "" -"A configurable option within Object Storage to automatically delete objects " -"after a specified amount of time has passed or a certain date is reached." -msgstr "" - -#: ../common/get_started_identity.rst:54 ../common/get_started_identity.rst:53 -msgid "" -"A container used to group or isolate resources. Tenants also group or " -"isolate identity objects. Depending on the service operator, a tenant may " -"map to a customer, account, organization, or project." -msgstr "" - -#: ../common/glossary.rst:879 -msgid "" -"A content delivery network is a specialized network that is used to " -"distribute content to clients, typically located close to the client for " -"increased performance." -msgstr "" - -#: ../common/glossary.rst:3277 ../common/glossary.rst:3284 -#: ../common/glossary.rst:3291 ../common/glossary.rst:3299 -#: ../common/glossary.rst:3288 -msgid "" -"A controlled reboot where a VM instance is properly restarted through " -"operating system commands." -msgstr "" - -#: ../common/glossary.rst:2436 ../common/glossary.rst:2443 -#: ../common/glossary.rst:2442 ../common/glossary.rst:2448 -#: ../common/glossary.rst:2450 ../common/glossary.rst:2439 -msgid "" -"A core OpenStack project that provides a network connectivity abstraction " -"layer to OpenStack Compute." -msgstr "" - -#: ../common/glossary.rst:2425 ../common/glossary.rst:2432 -#: ../common/glossary.rst:2431 ../common/glossary.rst:2437 -#: ../common/glossary.rst:2439 ../common/glossary.rst:2428 -msgid "" -"A core OpenStack project that provides a network connectivity abstraction " -"layer to OpenStack Compute. The project name of Networking is neutron." -msgstr "" - -#: ../common/glossary.rst:678 -msgid "A core OpenStack project that provides block storage services for VMs." -msgstr "" - -#: ../common/glossary.rst:1554 ../common/glossary.rst:1555 -msgid "A core project that provides the OpenStack Image service." -msgstr "" - -#: ../common/glossary.rst:3762 ../common/glossary.rst:3769 -#: ../common/glossary.rst:3776 ../common/glossary.rst:3784 -#: ../common/glossary.rst:3773 -msgid "" -"A daemon that listens to a queue and carries out tasks in response to " -"messages. For example, the cinder-volume worker manages volume creation and " -"deletion on storage arrays." -msgstr "" - -#: ../common/glossary.rst:2022 ../common/glossary.rst:2028 -msgid "" -"A default role in the Compute RBAC system that can quarantine an instance in " -"any project." -msgstr "" - -#: ../common/glossary.rst:453 -msgid "" -"A device that moves data in the form of blocks. These device nodes interface " -"the devices, such as hard disks, CD-ROM drives, flash drives, and other " -"addressable regions of memory." -msgstr "" - -#: ../common/glossary.rst:1785 ../common/glossary.rst:1791 -msgid "" -"A directory service, which allows users to login with a user name and " -"password. It is a typical source of authentication tokens." -msgstr "" - -#: ../common/glossary.rst:2956 ../common/glossary.rst:2963 -#: ../common/glossary.rst:2970 ../common/glossary.rst:2972 -#: ../common/glossary.rst:2961 -msgid "" -"A discrete OpenStack environment with dedicated API endpoints that typically " -"shares only the Identity (keystone) with other regions." -msgstr "" - -#: ../common/glossary.rst:272 -msgid "A disk storage protocol tunneled within Ethernet." -msgstr "" - -#: ../common/glossary.rst:2248 ../common/glossary.rst:2255 -#: ../common/glossary.rst:2254 ../common/glossary.rst:2243 -msgid "" -"A distributed memory object caching system that is used by Object Storage " -"for caching." -msgstr "" - -#: ../common/glossary.rst:3359 ../common/glossary.rst:3366 -#: ../common/glossary.rst:3373 ../common/glossary.rst:3381 -#: ../common/glossary.rst:3370 -msgid "" -"A domain within a parent domain. Subdomains cannot be registered. Subdomains " -"enable you to delegate domains. Subdomains can themselves have subdomains, " -"so third-level, fourth-level, fifth-level, and deeper levels of nesting are " -"possible." -msgstr "" - -#: ../common/glossary.rst:2226 ../common/glossary.rst:2232 -#: ../common/glossary.rst:2221 -msgid "" -"A driver for the Modular Layer 2 (ML2) neutron plug-in that provides layer-2 " -"connectivity for virtual instances. A single OpenStack installation can use " -"multiple mechanism drivers." -msgstr "" - -#: ../common/glossary.rst:3055 ../common/glossary.rst:3062 -#: ../common/glossary.rst:3069 ../common/glossary.rst:3071 -#: ../common/glossary.rst:3060 -msgid "" -"A feature of Compute that allows the unprivileged \"nova\" user to run a " -"specified list of commands as the Linux root user." -msgstr "" - -#: ../common/glossary.rst:3211 ../common/glossary.rst:3218 -#: ../common/glossary.rst:3225 ../common/glossary.rst:3233 -#: ../common/glossary.rst:3222 -msgid "" -"A feature of the load-balancing service. It attempts to force subsequent " -"connections to a service to be redirected to the same node as long as it is " -"online." -msgstr "" - -#: ../common/glossary.rst:1573 ../common/glossary.rst:1574 -msgid "" -"A file system designed to aggregate NAS hosts, compatible with OpenStack." -msgstr "" - -#: ../common/glossary.rst:2685 ../common/glossary.rst:2692 -#: ../common/glossary.rst:2698 ../common/glossary.rst:2700 -#: ../common/glossary.rst:2689 -msgid "" -"A file used to customize a Compute instance. It can be used to inject SSH " -"keys or a specific network configuration." +#: ../common/app_support.rst:100 ../common/app_support.rst:102 +#: ../common/app_support.rst:105 +msgid "OpenStack mailing lists" msgstr "" -#: ../common/glossary.rst:3612 ../common/glossary.rst:3619 -#: ../common/glossary.rst:3626 ../common/glossary.rst:3634 -#: ../common/glossary.rst:3623 +#: ../common/app_support.rst:102 ../common/app_support.rst:104 +#: ../common/app_support.rst:107 msgid "" -"A generic term for virtualization of network functions such as switching, " -"routing, load balancing, and security using a combination of VMs and " -"overlays on physical network infrastructure." +"A great way to get answers and insights is to post your question or " +"problematic scenario to the OpenStack mailing list. You can learn from and " +"help others who might have similar issues. To subscribe or view the " +"archives, go to http://lists.openstack.org/cgi-bin/mailman/listinfo/" +"openstack. You might be interested in the other mailing lists for specific " +"projects or development, which you can find `on the wiki `__. A description of all mailing lists is " +"available at https://wiki.openstack.org/wiki/MailingLists." msgstr "" #: ../common/app_support.rst:107 @@ -1078,383 +238,497 @@ msgid "" "available at http://wiki.openstack.org/MailingLists." msgstr "" -#: ../common/app_support.rst:107 ../common/app_support.rst:104 -#: ../common/app_support.rst:102 +#: ../common/app_support.rst:113 ../common/app_support.rst:115 +#: ../common/app_support.rst:118 +msgid "The OpenStack wiki" +msgstr "" + +#: ../common/app_support.rst:115 ../common/app_support.rst:117 +#: ../common/app_support.rst:120 msgid "" -"A great way to get answers and insights is to post your question or " -"problematic scenario to the OpenStack mailing list. You can learn from and " -"help others who might have similar issues. To subscribe or view the " -"archives, go to http://lists.openstack.org/cgi-bin/mailman/listinfo/" -"openstack. You might be interested in the other mailing lists for specific " -"projects or development, which you can find `on the wiki `__. A description of all mailing lists is " -"available at https://wiki.openstack.org/wiki/MailingLists." +"The `OpenStack wiki `__ contains a broad range " +"of topics but some of the information can be difficult to find or is a few " +"pages deep. Fortunately, the wiki search feature enables you to search by " +"title or content. If you search for specific information, such as about " +"networking or OpenStack Compute, you can find a large amount of relevant " +"material. More is being added all the time, so be sure to check back often. " +"You can find the search box in the upper-right corner of any OpenStack wiki " +"page." msgstr "" -#: ../common/glossary.rst:103 +#: ../common/app_support.rst:120 msgid "" -"A group of fixed and/or floating IP addresses that are assigned to a project " -"and can be used by or assigned to the VM instances in a project." +"The `OpenStack wiki `__ contains a broad range " +"of topics but some of the information can be difficult to find or is a few " +"pages deep. Fortunately, the wiki search feature enables you to search by " +"title or content. If you search for specific information, such as about " +"networking or OpenStack Compute, you can find a large amount of relevant " +"material. More is being added all the time, so be sure to check back often. " +"You can find the search box in the upper-right corner of any OpenStack wiki " +"page." msgstr "" -#: ../common/glossary.rst:266 +#: ../common/app_support.rst:125 ../common/app_support.rst:127 +#: ../common/app_support.rst:130 +msgid "The Launchpad Bugs area" +msgstr "" + +#: ../common/app_support.rst:127 ../common/app_support.rst:129 +#: ../common/app_support.rst:132 msgid "" -"A group of interrelated web development techniques used on the client-side " -"to create asynchronous web applications. Used extensively in horizon." +"The OpenStack community values your set up and testing efforts and wants " +"your feedback. To log a bug, you must sign up for a Launchpad account at " +"https://launchpad.net/+login. You can view existing bugs and report bugs in " +"the Launchpad Bugs area. Use the search feature to determine whether the bug " +"has already been reported or already been fixed. If it still seems like your " +"bug is unreported, fill out a bug report." msgstr "" -#: ../common/glossary.rst:522 +#: ../common/app_support.rst:134 ../common/app_support.rst:136 +#: ../common/app_support.rst:139 +msgid "Some tips:" +msgstr "" + +#: ../common/app_support.rst:136 ../common/app_support.rst:138 +#: ../common/app_support.rst:141 +msgid "Give a clear, concise summary." +msgstr "" + +#: ../common/app_support.rst:138 ../common/app_support.rst:140 +#: ../common/app_support.rst:143 msgid "" -"A group of related button types within horizon. Buttons to start, stop, and " -"suspend VMs are in one class. Buttons to associate and disassociate floating " -"IP addresses are in another class, and so on." +"Provide as much detail as possible in the description. Paste in your command " +"output or stack traces, links to screen shots, and any other information " +"which might be useful." msgstr "" -#: ../common/glossary.rst:3453 ../common/glossary.rst:3460 -#: ../common/glossary.rst:3467 ../common/glossary.rst:3475 -#: ../common/glossary.rst:3464 +#: ../common/app_support.rst:142 ../common/app_support.rst:144 +#: ../common/app_support.rst:147 msgid "" -"A group of users; used to isolate access to Compute resources. An " -"alternative term for a project." +"Be sure to include the software and package versions that you are using, " +"especially if you are using a development branch, such as, ``\"Juno release" +"\" vs git commit bc79c3ecc55929bac585d04a03475b72e06a3208``." msgstr "" -#: ../common/glossary.rst:1328 ../common/glossary.rst:1329 +#: ../common/app_support.rst:146 ../common/app_support.rst:148 +#: ../common/app_support.rst:151 msgid "" -"A grouped release of projects related to OpenStack that came out in April " -"2012, the fifth release of OpenStack. It included Compute (nova 2012.1), " -"Object Storage (swift 1.4.8), Image (glance), Identity (keystone), and " -"Dashboard (horizon). Essex is the code name for the fifth release of " -"OpenStack. The design summit took place in Boston, Massachusetts, US and " -"Essex is a nearby city." +"Any deployment-specific information is helpful, such as whether you are " +"using Ubuntu 14.04 or are performing a multi-node installation." msgstr "" -#: ../common/glossary.rst:429 +#: ../common/app_support.rst:149 ../common/app_support.rst:151 +#: ../common/app_support.rst:154 +msgid "The following Launchpad Bugs areas are available:" +msgstr "" + +#: ../common/app_support.rst:151 ../common/app_support.rst:153 +#: ../common/app_support.rst:156 msgid "" -"A grouped release of projects related to OpenStack that came out in February " -"of 2011. It included only Compute (nova) and Object Storage (swift). Bexar " -"is the code name for the second release of OpenStack. The design summit took " -"place in San Antonio, Texas, US, which is the county seat for Bexar county." +"`Bugs: OpenStack Block Storage (cinder) `__" msgstr "" -#: ../common/glossary.rst:1096 +#: ../common/app_support.rst:154 ../common/app_support.rst:156 +#: ../common/app_support.rst:159 +msgid "`Bugs: OpenStack Compute (nova) `__" +msgstr "" + +#: ../common/app_support.rst:156 ../common/app_support.rst:158 +#: ../common/app_support.rst:161 msgid "" -"A grouped release of projects related to OpenStack that came out in the fall " -"of 2011, the fourth release of OpenStack. It included Compute (nova 2011.3), " -"Object Storage (swift 1.4.3), and the Image service (glance). Diablo is the " -"code name for the fourth release of OpenStack. The design summit took place " -"in in the Bay Area near Santa Clara, California, US and Diablo is a nearby " -"city." +"`Bugs: OpenStack Dashboard (horizon) `__" msgstr "" -#: ../common/glossary.rst:1517 ../common/glossary.rst:1518 +#: ../common/app_support.rst:159 ../common/app_support.rst:161 +#: ../common/app_support.rst:164 msgid "" -"A grouped release of projects related to OpenStack that came out in the fall " -"of 2012, the sixth release of OpenStack. It includes Compute (nova), Object " -"Storage (swift), Identity (keystone), Networking (neutron), Image service " -"(glance), and Volumes or Block Storage (cinder). Folsom is the code name for " -"the sixth release of OpenStack. The design summit took place in San " -"Francisco, California, US and Folsom is a nearby city." +"`Bugs: OpenStack Identity (keystone) `__" msgstr "" -#: ../common/conventions.rst:12 -msgid "A handy tip or reminder." -msgstr "" - -#: ../common/glossary.rst:1659 ../common/glossary.rst:1665 +#: ../common/app_support.rst:162 ../common/app_support.rst:164 +#: ../common/app_support.rst:167 msgid "" -"A high availability system design approach and associated service " -"implementation ensures that a prearranged level of operational performance " -"will be met during a contractual measurement period. High availability " -"systems seeks to minimize system downtime and data loss." +"`Bugs: OpenStack Image service (glance) `__" msgstr "" -#: ../common/glossary.rst:3217 ../common/glossary.rst:3224 -#: ../common/glossary.rst:3231 ../common/glossary.rst:3239 -#: ../common/glossary.rst:3228 +#: ../common/app_support.rst:165 ../common/app_support.rst:167 +#: ../common/app_support.rst:170 msgid "" -"A horizon component that stores and tracks client session information. " -"Implemented through the Django sessions framework." +"`Bugs: OpenStack Networking (neutron) `__" msgstr "" -#: ../common/glossary.rst:1709 ../common/glossary.rst:1715 +#: ../common/app_support.rst:168 ../common/app_support.rst:170 +#: ../common/app_support.rst:173 msgid "" -"A hybrid cloud is a composition of two or more clouds (private, community or " -"public) that remain distinct entities but are bound together, offering the " -"benefits of multiple deployment models. Hybrid cloud can also mean the " -"ability to connect colocation, managed and/or dedicated services with cloud " -"resources." +"`Bugs: OpenStack Object Storage (swift) `__" msgstr "" -#: ../common/glossary.rst:3020 ../common/glossary.rst:3027 -#: ../common/glossary.rst:3034 ../common/glossary.rst:3036 -#: ../common/glossary.rst:3025 +#: ../common/app_support.rst:171 msgid "" -"A kind of web service API that uses REST, or Representational State " -"Transfer. REST is the style of architecture for hypermedia systems that is " -"used for the World Wide Web." +"`Bugs: Application catalog (murano) `__" msgstr "" -#: ../common/glossary.rst:3302 ../common/glossary.rst:3309 -#: ../common/glossary.rst:3316 ../common/glossary.rst:3324 -#: ../common/glossary.rst:3313 +#: ../common/app_support.rst:171 ../common/app_support.rst:173 +#: ../common/app_support.rst:176 msgid "" -"A lightweight SQL database, used as the default persistent storage method in " -"many OpenStack services." +"`Bugs: Bare metal service (ironic) `__" msgstr "" -#: ../common/glossary.rst:596 +#: ../common/app_support.rst:173 ../common/app_support.rst:175 +#: ../common/app_support.rst:177 ../common/app_support.rst:178 msgid "" -"A list of API endpoints that are available to a user after authentication " -"with the Identity service." +"`Bugs: Data processing service (sahara) `__" msgstr "" -#: ../common/glossary.rst:1304 ../common/glossary.rst:1305 +#: ../common/app_support.rst:175 msgid "" -"A list of URL and port number endpoints that indicate where a service, such " -"as Object Storage, Compute, Identity, and so on, can be accessed." +"`Bugs: Containers service (magnum) `__" msgstr "" -#: ../common/glossary.rst:1842 ../common/glossary.rst:1848 -msgid "A list of VM images that are available through Image service." +#: ../common/app_support.rst:176 ../common/app_support.rst:178 +#: ../common/app_support.rst:180 ../common/app_support.rst:181 +msgid "`Bugs: Database service (trove) `__" msgstr "" -#: ../common/glossary.rst:30 +#: ../common/app_support.rst:178 ../common/app_support.rst:180 +#: ../common/app_support.rst:182 ../common/app_support.rst:183 +#: ../common/app_support.rst:184 ../common/app_support.rst:186 +msgid "`Bugs: Orchestration (heat) `__" +msgstr "" + +#: ../common/app_support.rst:180 ../common/app_support.rst:182 +#: ../common/app_support.rst:185 ../common/app_support.rst:186 +#: ../common/app_support.rst:188 ../common/app_support.rst:190 msgid "" -"A list of permissions attached to an object. An ACL specifies which users or " -"system processes have access to objects. It also defines which operations " -"can be performed on specified objects. Each entry in a typical ACL specifies " -"a subject and an operation. For instance, the ACL entry `(Alice, delete)` " -"for a file gives Alice permission to delete the file." +"`Bugs: Telemetry (ceilometer) `__" msgstr "" -#: ../common/glossary.rst:1832 ../common/glossary.rst:2243 -#: ../common/glossary.rst:2250 ../common/glossary.rst:1838 -#: ../common/glossary.rst:2249 ../common/glossary.rst:2238 +#: ../common/app_support.rst:182 msgid "" -"A list of tenants that can access a given VM image within Image service." +"`Bugs: Deployment service (tuskar) `__" msgstr "" -#: ../common/glossary.rst:2159 ../common/glossary.rst:2165 +#: ../common/app_support.rst:182 ../common/app_support.rst:184 msgid "" -"A load balancer is a logical device that belongs to a cloud account. It is " -"used to distribute workloads between multiple back-end systems or services, " -"based on the criteria defined as part of its configuration." +"`Bugs: Key Manager Service (barbican) `__" msgstr "" -#: ../common/glossary.rst:2756 ../common/glossary.rst:2763 +#: ../common/app_support.rst:183 ../common/app_support.rst:185 +#: ../common/app_support.rst:188 ../common/app_support.rst:189 +#: ../common/app_support.rst:191 ../common/app_support.rst:194 +#: ../common/app_support.rst:196 +msgid "`Bugs: Messaging service (zaqar) `__" +msgstr "" + +#: ../common/app_support.rst:184 ../common/app_support.rst:186 +#: ../common/app_support.rst:188 msgid "" -"A logical grouping of users within Compute; defines quotas and access to VM " -"images." +"`Bugs: Shared file systems (manila) `__" msgstr "" -#: ../common/glossary.rst:2708 ../common/glossary.rst:2715 -#: ../common/glossary.rst:2721 ../common/glossary.rst:2723 -#: ../common/glossary.rst:2712 +#: ../common/app_support.rst:186 ../common/app_support.rst:188 +#: ../common/app_support.rst:191 ../common/app_support.rst:192 +#: ../common/app_support.rst:194 ../common/app_support.rst:197 +#: ../common/app_support.rst:199 msgid "" -"A logical set of devices, such as web servers, that you group together to " -"receive and process traffic. The load balancing function chooses which " -"member of the pool handles the new requests or connections received on the " -"VIP address. Each VIP has one pool." +"`Bugs: OpenStack API Documentation (developer.openstack.org) `__" msgstr "" -#: ../common/glossary.rst:19 +#: ../common/app_support.rst:189 ../common/app_support.rst:191 +#: ../common/app_support.rst:194 ../common/app_support.rst:195 +#: ../common/app_support.rst:197 ../common/app_support.rst:200 +#: ../common/app_support.rst:202 msgid "" -"A mechanism that allows IPv6 packets to be transmitted over an IPv4 network, " -"providing a strategy for migrating to IPv6." +"`Bugs: OpenStack Documentation (docs.openstack.org) `__" msgstr "" -#: ../common/glossary.rst:920 +#: ../common/app_support.rst:191 ../common/app_support.rst:193 msgid "" -"A mechanism that allows many resources (for example, fonts, JavaScript) on a " -"web page to be requested from another domain outside the domain from which " -"the resource originated. In particular, JavaScript's AJAX calls can use the " -"XMLHttpRequest mechanism." +"`Bugs: Workflow service (mistral) `__" msgstr "" -#: ../common/glossary.rst:2676 ../common/glossary.rst:2683 -#: ../common/glossary.rst:2689 ../common/glossary.rst:2691 -#: ../common/glossary.rst:2680 +#: ../common/app_support.rst:193 ../common/app_support.rst:195 +#: ../common/app_support.rst:198 ../common/app_support.rst:199 +#: ../common/app_support.rst:201 ../common/app_support.rst:204 +#: ../common/app_support.rst:206 +msgid "The OpenStack IRC channel" +msgstr "" + +#: ../common/app_support.rst:195 ../common/app_support.rst:197 +#: ../common/app_support.rst:200 ../common/app_support.rst:201 +#: ../common/app_support.rst:203 ../common/app_support.rst:206 +#: ../common/app_support.rst:208 msgid "" -"A message that is stored both in memory and on disk. The message is not lost " -"after a failure or restart." +"The OpenStack community lives in the #openstack IRC channel on the Freenode " +"network. You can hang out, ask questions, or get immediate feedback for " +"urgent and pressing issues. To install an IRC client or use a browser-based " +"client, go to `https://webchat.freenode.net/ `__. You can also use Colloquy (Mac OS X, http://colloquy.info/), mIRC " +"(Windows, http://www.mirc.com/), or XChat (Linux). When you are in the IRC " +"channel and want to share code or command output, the generally accepted " +"method is to use a Paste Bin. The OpenStack project has one at http://paste." +"openstack.org. Just paste your longer amounts of text or logs in the web " +"form and you get a URL that you can paste into the channel. The OpenStack " +"IRC channel is ``#openstack`` on ``irc.freenode.net``. You can find a list " +"of all OpenStack IRC channels at https://wiki.openstack.org/wiki/IRC." msgstr "" -#: ../common/glossary.rst:3511 ../common/glossary.rst:3518 -#: ../common/glossary.rst:3525 ../common/glossary.rst:3533 -#: ../common/glossary.rst:3522 +#: ../common/app_support.rst:211 ../common/app_support.rst:213 +#: ../common/app_support.rst:216 ../common/app_support.rst:217 +#: ../common/app_support.rst:219 ../common/app_support.rst:222 +#: ../common/app_support.rst:224 +msgid "Documentation feedback" +msgstr "" + +#: ../common/app_support.rst:221 ../common/app_support.rst:223 +#: ../common/app_support.rst:226 ../common/app_support.rst:227 +#: ../common/app_support.rst:229 ../common/app_support.rst:232 +#: ../common/app_support.rst:234 +msgid "OpenStack distribution packages" +msgstr "" + +#: ../common/app_support.rst:223 ../common/app_support.rst:225 +#: ../common/app_support.rst:228 ../common/app_support.rst:229 +#: ../common/app_support.rst:231 ../common/app_support.rst:234 +#: ../common/app_support.rst:236 msgid "" -"A message that is stored in memory and is lost after the server is restarted." +"The following Linux distributions provide community-supported packages for " +"OpenStack:" msgstr "" -#: ../common/glossary.rst:2386 ../common/glossary.rst:2393 -#: ../common/glossary.rst:2392 ../common/glossary.rst:2398 -#: ../common/glossary.rst:2399 ../common/glossary.rst:2388 +#: ../common/app_support.rst:226 ../common/app_support.rst:228 +#: ../common/app_support.rst:231 ../common/app_support.rst:232 +#: ../common/app_support.rst:234 ../common/app_support.rst:237 +#: ../common/app_support.rst:239 +msgid "**Debian:** https://wiki.debian.org/OpenStack" +msgstr "" + +#: ../common/app_support.rst:228 ../common/app_support.rst:230 +#: ../common/app_support.rst:233 ../common/app_support.rst:234 +#: ../common/app_support.rst:236 ../common/app_support.rst:239 +#: ../common/app_support.rst:241 msgid "" -"A method for making file systems available over the network. Supported by " -"OpenStack." +"**CentOS, Fedora, and Red Hat Enterprise Linux:** https://www.rdoproject.org/" msgstr "" -#: ../common/glossary.rst:459 +#: ../common/app_support.rst:231 +msgid "**Debian:** http://wiki.debian.org/OpenStack" +msgstr "" + +#: ../common/app_support.rst:231 ../common/app_support.rst:233 +#: ../common/app_support.rst:236 ../common/app_support.rst:237 +#: ../common/app_support.rst:239 ../common/app_support.rst:242 +#: ../common/app_support.rst:244 msgid "" -"A method of VM live migration used by KVM to evacuate instances from one " -"host to another with very little downtime during a user-initiated " -"switchover. Does not require shared storage. Supported by Compute." +"**openSUSE and SUSE Linux Enterprise Server:** https://en.opensuse.org/" +"Portal:OpenStack" msgstr "" -#: ../common/glossary.rst:2410 ../common/glossary.rst:2417 -#: ../common/glossary.rst:2416 ../common/glossary.rst:2422 +#: ../common/app_support.rst:234 ../common/app_support.rst:236 +#: ../common/app_support.rst:239 ../common/app_support.rst:240 +#: ../common/app_support.rst:242 ../common/app_support.rst:245 +#: ../common/app_support.rst:247 +msgid "**Ubuntu:** https://wiki.ubuntu.com/ServerTeam/CloudArchive" +msgstr "" + +#: ../common/app_support.rst:236 msgid "" -"A method of keeping a clock for a host or node correct through " -"communications with a trusted, accurate time source." +"**openSUSE and SUSE Linux Enterprise Server:** http://en.opensuse.org/Portal:" +"OpenStack" msgstr "" -#: ../common/glossary.rst:1578 ../common/glossary.rst:1579 +#: ../common/cli_discover_version_number_for_a_client.rst:3 +msgid "Discover the version number for a client" +msgstr "" + +#: ../common/cli_discover_version_number_for_a_client.rst:5 +msgid "Run the following command to discover the version number for a client::" +msgstr "" + +#: ../common/cli_discover_version_number_for_a_client.rst:9 msgid "" -"A method of operating system installation where a finalized disk image is " -"created and then used by all nodes without modification." +"For example, to see the version number for the ``nova`` client, run the " +"following command::" msgstr "" -#: ../common/glossary.rst:1229 ../common/glossary.rst:1230 +#: ../common/cli_discover_version_number_for_a_client.rst:14 +msgid "The version number (2.15.0 in the example) is returned." +msgstr "" + +#: ../common/cli_install_openstack_command_line_clients.rst:3 +msgid "Install the OpenStack command-line clients" +msgstr "" + +#: ../common/cli_install_openstack_command_line_clients.rst:5 msgid "" -"A method to automatically configure networking for a host at boot time. " -"Provided by both Networking and Compute." +"Install the prerequisite software and the Python package for each OpenStack " +"client." msgstr "" -#: ../common/glossary.rst:1429 ../common/glossary.rst:1430 +#: ../common/cli_install_openstack_command_line_clients.rst:9 +msgid "Install the prerequisite software" +msgstr "" + +#: ../common/cli_install_openstack_command_line_clients.rst:11 msgid "" -"A method to establish trusts between identity providers and the OpenStack " -"cloud." +"Most Linux distributions include packaged versions of the command-line " +"clients that you can install directly, see Installing_from_packages_." msgstr "" -#: ../common/glossary.rst:1680 ../common/glossary.rst:1686 +#: ../common/cli_install_openstack_command_line_clients.rst:14 msgid "" -"A method to further subdivide availability zones into hypervisor pools, a " -"collection of common hosts." +"If you need to install the command-line packages source packages, the " +"following table lists the software that you need to have to run the command-" +"line clients, and provides installation instructions as needed." msgstr "" -#: ../common/glossary.rst:683 +#: ../common/cli_install_openstack_command_line_clients.rst:19 +#: ../common/cli_overview.rst:32 ../common/get_started_with_openstack.rst:27 +#: ../common/get_started_with_openstack.rst:35 +msgid "Description" +msgstr "" + +#: ../common/cli_install_openstack_command_line_clients.rst:19 +msgid "Prerequisite" +msgstr "" + +#: ../common/cli_install_openstack_command_line_clients.rst:21 +msgid "Currently, the clients do not support Python 3." +msgstr "" + +#: ../common/cli_install_openstack_command_line_clients.rst:21 +msgid "Python 2.7 or later" +msgstr "" + +#: ../common/cli_install_openstack_command_line_clients.rst:23 +msgid "Installed by default on Mac OS X." +msgstr "" + +#: ../common/cli_install_openstack_command_line_clients.rst:23 +msgid "setuptools package" +msgstr "" + +#: ../common/cli_install_openstack_command_line_clients.rst:25 msgid "" -"A minimal Linux distribution designed for use as a test image on clouds such " -"as OpenStack." +"Many Linux distributions provide packages to make setuptools easy to " +"install. Search your package manager for setuptools to find an installation " +"package. If you cannot find one, download the setuptools package directly " +"from http://pypi.python.org/pypi/setuptools." msgstr "" -#: ../common/glossary.rst:698 +#: ../common/cli_install_openstack_command_line_clients.rst:25 msgid "" -"A model that enables access to a shared pool of configurable computing " -"resources, such as networks, servers, storage, applications, and services, " -"that can be rapidly provisioned and released with minimal management effort " -"or service provider interaction." +"Many Linux distributions provide packages to make setuptools easy to " +"install. Search your package manager for setuptools to find an installation " +"package. If you cannot find one, download the setuptools package directly " +"from https://pypi.python.org/pypi/setuptools." msgstr "" -#: ../common/glossary.rst:491 +#: ../common/cli_install_openstack_command_line_clients.rst:32 msgid "" -"A network protocol used by a network client to obtain an IP address from a " -"configuration server. Provided in Compute through the dnsmasq daemon when " -"using either the FlatDHCP manager or VLAN manager network manager." +"The recommended way to install setuptools on Microsoft Windows is to follow " +"the documentation provided on the setuptools website (https://pypi.python." +"org/pypi/setuptools#windows). Another option is to use the unofficial binary " +"installer maintained by Christoph Gohlke (`http://www.lfd.uci.edu/~gohlke/" +"pythonlibs/ #setuptools `__)." msgstr "" -#: ../common/glossary.rst:1407 ../common/glossary.rst:1408 -msgid "A network segment typically used for instance Internet access." -msgstr "" - -#: ../common/glossary.rst:2196 ../common/glossary.rst:2202 -#: ../common/glossary.rst:2191 +#: ../common/cli_install_openstack_command_line_clients.rst:32 msgid "" -"A network segment used for administration, not accessible to the public " -"Internet." +"The recommended way to install setuptools on Microsoft Windows is to follow " +"the documentation provided on the setuptools website (https://pypi.python." +"org/pypi/setuptools). Another option is to use the unofficial binary " +"installer maintained by Christoph Gohlke (`http://www.lfd.uci.edu/~gohlke/" +"pythonlibs/ #setuptools `__)." msgstr "" -#: ../common/glossary.rst:1906 ../common/glossary.rst:1912 +#: ../common/cli_install_openstack_command_line_clients.rst:42 msgid "" -"A network segment used for instance traffic tunnels between compute nodes " -"and the network node." +"To install the clients on a Linux, Mac OS X, or Microsoft Windows system, " +"use pip. It is easy to use, ensures that you get the latest version of the " +"clients from the `Python Package Index `__, and " +"lets you update or remove the packages later on." msgstr "" -#: ../common/glossary.rst:3583 ../common/glossary.rst:3590 -#: ../common/glossary.rst:3597 ../common/glossary.rst:3605 -#: ../common/glossary.rst:3594 +#: ../common/cli_install_openstack_command_line_clients.rst:42 msgid "" -"A network virtualization technology that attempts to reduce the scalability " -"problems associated with large cloud computing deployments. It uses a VLAN-" -"like encapsulation technique to encapsulate Ethernet frames within UDP " -"packets." +"To install the clients on a Linux, Mac OS X, or Microsoft Windows system, " +"use pip. It is easy to use, ensures that you get the latest version of the " +"clients from the `Python Package Index `__, and " +"lets you update or remove the packages later on." msgstr "" -#: ../common/get_started_identity.rst:65 ../common/get_started_identity.rst:64 +#: ../common/cli_install_openstack_command_line_clients.rst:42 +msgid "pip package" +msgstr "" + +#: ../common/cli_install_openstack_command_line_clients.rst:49 msgid "" -"A network-accessible address where you access a service, usually a URL " -"address. If you are using an extension for templates, an endpoint template " -"can be created, which represents the templates of all the consumable " -"services that are available across the regions." +"Since the installation process compiles source files, this requires the " +"related Python development package for your operating system and " +"distribution." msgstr "" -#: ../common/glossary.rst:2789 ../common/glossary.rst:2796 -#: ../common/glossary.rst:2803 ../common/glossary.rst:2805 -#: ../common/glossary.rst:2794 -msgid "A node that provides the Object Storage proxy service." +#: ../common/cli_install_openstack_command_line_clients.rst:53 +msgid "Install pip through the package manager for your system:" msgstr "" -#: ../common/glossary.rst:3409 ../common/glossary.rst:3416 -#: ../common/glossary.rst:3423 ../common/glossary.rst:3431 -#: ../common/glossary.rst:3420 +#: ../common/cli_install_openstack_command_line_clients.rst:56 +msgid "**MacOS**" +msgstr "" + +#: ../common/cli_install_openstack_command_line_clients.rst:62 +msgid "**Microsoft Windows**" +msgstr "" + +#: ../common/cli_install_openstack_command_line_clients.rst:64 msgid "" -"A node that runs Object Storage account, container, and object services." +"Ensure that the ``C:\\Python27\\Scripts`` directory is defined in the " +"``PATH`` environment variable, and use the ``easy_install`` command from the " +"setuptools package:" msgstr "" -#: ../common/glossary.rst:712 +#: ../common/cli_install_openstack_command_line_clients.rst:73 msgid "" -"A node that runs network, volume, API, scheduler, and image services. Each " -"service may be broken out into separate nodes for scalability or " -"availability." +"Another option is to use the unofficial binary installer provided by " +"Christoph Gohlke (http://www.lfd.uci.edu/~gohlke/pythonlibs/#pip)." msgstr "" -#: ../common/glossary.rst:803 +#: ../common/cli_install_openstack_command_line_clients.rst:77 +msgid "**Ubuntu and Debian**" +msgstr "" + +#: ../common/cli_install_openstack_command_line_clients.rst:83 msgid "" -"A node that runs the nova-compute daemon that manages VM instances that " -"provide a wide range of services, such as web applications and analytics." +"Note that extra dependencies may be required, per operating system, " +"depending on the package being installed, such as is the case with Tempest." msgstr "" -#: ../common/get_started_telemetry.rst:32 -#: ../common/get_started_telemetry.rst:31 -msgid "A notification agent (``ceilometer-agent-notification``)" +#: ../common/cli_install_openstack_command_line_clients.rst:87 +msgid "**Red Hat Enterprise Linux, CentOS, or Fedora.**" msgstr "" -#: ../common/glossary.rst:586 +#: ../common/cli_install_openstack_command_line_clients.rst:89 +msgid "A packaged version enables you to use yum to install the package:" +msgstr "" + +#: ../common/cli_install_openstack_command_line_clients.rst:96 msgid "" -"A notification driver that monitors VM instances and updates the capacity " -"cache as needed." +"There are also packaged versions of the clients available in `RDO `__ that enable yum to install the clients as described " +"in Installing_from_packages_." msgstr "" -#: ../common/get_started_image_service.rst:14 -msgid "" -"A number of periodic processes run on the OpenStack Image Service to support " -"caching. Replication services ensure consistency and availability through " -"the cluster. Other periodic processes include auditors, updaters, and " -"reapers." -msgstr "" - -#: ../common/get_started_image_service.rst:14 -#: ../common/get_started_image_service.rst:11 -msgid "" -"A number of periodic processes run on the OpenStack Image service to support " -"caching. Replication services ensure consistency and availability through " -"the cluster. Other periodic processes include auditors, updaters, and " -"reapers." -msgstr "" - -#: ../common/glossary.rst:2943 ../common/glossary.rst:2950 -#: ../common/glossary.rst:2957 ../common/glossary.rst:2959 -#: ../common/glossary.rst:2948 -msgid "" -"A number within a database that is incremented each time a change is made. " -"Used by Object Storage when replicating." -msgstr "" - -#: ../common/glossary.rst:728 -msgid "" -"A package commonly installed in VM images that performs initialization of an " -"instance after boot using information that it retrieves from the metadata " -"service, such as the SSH public key and user data." +#: ../common/cli_install_openstack_command_line_clients.rst:101 +msgid "**SUSE Linux Enterprise Linux 11**" msgstr "" #: ../common/cli_install_openstack_command_line_clients.rst:103 @@ -1466,325 +740,1716 @@ msgid "" "First, add the Open Build Service repository:" msgstr "" -#: ../common/cli_install_openstack_command_line_clients.rst:89 -msgid "A packaged version enables you to use yum to install the package:" +#: ../common/cli_install_openstack_command_line_clients.rst:116 +msgid "Then install pip and use it to manage client installation:" msgstr "" -#: ../common/glossary.rst:3344 ../common/glossary.rst:3351 -#: ../common/glossary.rst:3358 ../common/glossary.rst:3366 -#: ../common/glossary.rst:3355 -msgid "A persistent storage method supported by XenAPI, such as iSCSI or NFS." -msgstr "" - -#: ../common/glossary.rst:693 -msgid "A person who plans, designs, and oversees the creation of clouds." -msgstr "" - -#: ../common/glossary.rst:3045 ../common/glossary.rst:3052 -#: ../common/glossary.rst:3059 ../common/glossary.rst:3061 -#: ../common/glossary.rst:3050 +#: ../common/cli_install_openstack_command_line_clients.rst:123 +#: ../common/cli_install_openstack_command_line_clients.rst:136 msgid "" -"A personality that a user assumes to perform a specific set of operations. A " -"role includes a set of rights and privileges. A user assuming that role " -"inherits those rights and privileges." +"There are also packaged versions of the clients available that enable zypper " +"to install the clients as described in Installing_from_packages_." msgstr "" -#: ../common/get_started_identity.rst:71 ../common/get_started_identity.rst:70 +#: ../common/cli_install_openstack_command_line_clients.rst:127 +msgid "**openSUSE**" +msgstr "" + +#: ../common/cli_install_openstack_command_line_clients.rst:129 +msgid "You can install pip and use it to manage client installation:" +msgstr "" + +#: ../common/cli_install_openstack_command_line_clients.rst:142 +msgid "Install the clients" +msgstr "" + +#: ../common/cli_install_openstack_command_line_clients.rst:144 msgid "" -"A personality with a defined set of user rights and privileges to perform a " -"specific set of operations." +"When following the instructions in this section, replace PROJECT with the " +"lowercase name of the client to install, such as ``nova``. Repeat for each " +"client. The following values are valid:" msgstr "" -#: ../common/glossary.rst:1676 ../common/glossary.rst:1682 -msgid "A physical computer, not a VM instance (node)." +#: ../common/cli_install_openstack_command_line_clients.rst:148 +msgid "``barbican`` - Key Manager Service API" msgstr "" -#: ../common/glossary.rst:1925 ../common/glossary.rst:1931 +#: ../common/cli_install_openstack_command_line_clients.rst:148 +#: ../common/cli_install_openstack_command_line_clients.rst:150 +msgid "``ceilometer`` - Telemetry API" +msgstr "" + +#: ../common/cli_install_openstack_command_line_clients.rst:150 +#: ../common/cli_install_openstack_command_line_clients.rst:152 +msgid "``cinder`` - Block Storage API and extensions" +msgstr "" + +#: ../common/cli_install_openstack_command_line_clients.rst:152 +#: ../common/cli_install_openstack_command_line_clients.rst:154 +msgid "``glance`` - Image service API" +msgstr "" + +#: ../common/cli_install_openstack_command_line_clients.rst:154 +#: ../common/cli_install_openstack_command_line_clients.rst:156 +msgid "``heat`` - Orchestration API" +msgstr "" + +#: ../common/cli_install_openstack_command_line_clients.rst:156 +#: ../common/cli_install_openstack_command_line_clients.rst:158 +msgid "``magnum`` - Containers service API" +msgstr "" + +#: ../common/cli_install_openstack_command_line_clients.rst:156 +#: ../common/cli_install_openstack_command_line_clients.rst:162 +#: ../common/cli_install_openstack_command_line_clients.rst:164 +#: ../common/cli_install_openstack_command_line_clients.rst:166 +msgid "``neutron`` - Networking API" +msgstr "" + +#: ../common/cli_install_openstack_command_line_clients.rst:158 +#: ../common/cli_install_openstack_command_line_clients.rst:160 +msgid "``manila`` - Shared file systems API" +msgstr "" + +#: ../common/cli_install_openstack_command_line_clients.rst:158 +#: ../common/cli_install_openstack_command_line_clients.rst:164 +#: ../common/cli_install_openstack_command_line_clients.rst:166 +#: ../common/cli_install_openstack_command_line_clients.rst:168 +msgid "``nova`` - Compute API and extensions" +msgstr "" + +#: ../common/cli_install_openstack_command_line_clients.rst:160 +#: ../common/cli_install_openstack_command_line_clients.rst:162 +#: ../common/cli_install_openstack_command_line_clients.rst:164 +msgid "``murano`` - Application catalog API" +msgstr "" + +#: ../common/cli_install_openstack_command_line_clients.rst:160 +#: ../common/cli_install_openstack_command_line_clients.rst:166 +#: ../common/cli_install_openstack_command_line_clients.rst:168 +#: ../common/cli_install_openstack_command_line_clients.rst:170 +msgid "``sahara`` - Data Processing API" +msgstr "" + +#: ../common/cli_install_openstack_command_line_clients.rst:160 +msgid "``sahara`` - Database Processing API" +msgstr "" + +#: ../common/cli_install_openstack_command_line_clients.rst:162 +msgid "``mistral`` - Workflow service API" +msgstr "" + +#: ../common/cli_install_openstack_command_line_clients.rst:162 +#: ../common/cli_install_openstack_command_line_clients.rst:168 +#: ../common/cli_install_openstack_command_line_clients.rst:170 +#: ../common/cli_install_openstack_command_line_clients.rst:172 +msgid "``swift`` - Object Storage API" +msgstr "" + +#: ../common/cli_install_openstack_command_line_clients.rst:164 +#: ../common/cli_install_openstack_command_line_clients.rst:170 +#: ../common/cli_install_openstack_command_line_clients.rst:172 +#: ../common/cli_install_openstack_command_line_clients.rst:174 +msgid "``trove`` - Database service API" +msgstr "" + +#: ../common/cli_install_openstack_command_line_clients.rst:166 +#: ../common/cli_install_openstack_command_line_clients.rst:172 +#: ../common/cli_install_openstack_command_line_clients.rst:174 +#: ../common/cli_install_openstack_command_line_clients.rst:176 +#: ../common/cli_install_openstack_command_line_clients.rst:178 +msgid "``openstack`` - Common OpenStack client supporting multiple services" +msgstr "" + +#: ../common/cli_install_openstack_command_line_clients.rst:168 +#: ../common/cli_install_openstack_command_line_clients.rst:174 +#: ../common/cli_install_openstack_command_line_clients.rst:176 +#: ../common/cli_install_openstack_command_line_clients.rst:178 +#: ../common/cli_install_openstack_command_line_clients.rst:180 msgid "" -"A physical or virtual device that provides connectivity to another device or " -"medium." +"The following CLIs are deprecated in favor of ``openstack``, the Common " +"OpenStack client supporting multiple services:" msgstr "" -#: ../common/glossary.rst:3065 ../common/glossary.rst:3072 -#: ../common/glossary.rst:3079 ../common/glossary.rst:3081 -#: ../common/glossary.rst:3070 +#: ../common/cli_install_openstack_command_line_clients.rst:171 +#: ../common/cli_install_openstack_command_line_clients.rst:177 +#: ../common/cli_install_openstack_command_line_clients.rst:179 +#: ../common/cli_install_openstack_command_line_clients.rst:181 +#: ../common/cli_install_openstack_command_line_clients.rst:183 +msgid "``keystone`` - Identity service API and extensions" +msgstr "" + +#: ../common/cli_install_openstack_command_line_clients.rst:173 +#: ../common/cli_install_openstack_command_line_clients.rst:179 +#: ../common/cli_install_openstack_command_line_clients.rst:181 +#: ../common/cli_install_openstack_command_line_clients.rst:183 +#: ../common/cli_install_openstack_command_line_clients.rst:185 msgid "" -"A physical or virtual network device that passes network traffic between " -"different networks." +"The following example shows the command for installing the nova client with " +"``pip``." msgstr "" -#: ../common/glossary.rst:238 +#: ../common/cli_install_openstack_command_line_clients.rst:176 +msgid "``tuskar`` - Deployment service API" +msgstr "" + +#: ../common/cli_install_openstack_command_line_clients.rst:181 +#: ../common/cli_install_openstack_command_line_clients.rst:187 +#: ../common/cli_install_openstack_command_line_clients.rst:189 +#: ../common/cli_install_openstack_command_line_clients.rst:191 +#: ../common/cli_install_openstack_command_line_clients.rst:193 +msgid "Installing with pip" +msgstr "" + +#: ../common/cli_install_openstack_command_line_clients.rst:183 msgid "" -"A piece of software that makes available another piece of software over a " -"network." +"Use pip to install the OpenStack clients on a Linux, Mac OS X, or Microsoft " +"Windows system. It is easy to use and ensures that you get the latest " +"version of the client from the `Python Package Index `__. Also, pip enables you to update or remove a package." msgstr "" -#: ../common/glossary.rst:1055 +#: ../common/cli_install_openstack_command_line_clients.rst:183 +#: ../common/cli_install_openstack_command_line_clients.rst:189 +#: ../common/cli_install_openstack_command_line_clients.rst:191 +#: ../common/cli_install_openstack_command_line_clients.rst:193 +#: ../common/cli_install_openstack_command_line_clients.rst:195 msgid "" -"A platform that provides a suite of desktop environments that users access " -"to receive a desktop experience from any location. This may provide general " -"use, development, or even homogeneous testing environments." +"Use pip to install the OpenStack clients on a Linux, Mac OS X, or Microsoft " +"Windows system. It is easy to use and ensures that you get the latest " +"version of the client from the `Python Package Index `__. Also, pip enables you to update or remove a package." msgstr "" -#: ../common/glossary.rst:1672 ../common/glossary.rst:1678 -msgid "A plug-in for the OpenStack dashboard (horizon)." +#: ../common/cli_install_openstack_command_line_clients.rst:189 +#: ../common/cli_install_openstack_command_line_clients.rst:195 +#: ../common/cli_install_openstack_command_line_clients.rst:197 +#: ../common/cli_install_openstack_command_line_clients.rst:199 +#: ../common/cli_install_openstack_command_line_clients.rst:201 +msgid "Install each client separately by using the following command:" msgstr "" -#: ../common/glossary.rst:3271 ../common/glossary.rst:3278 -#: ../common/glossary.rst:3285 ../common/glossary.rst:3293 -#: ../common/glossary.rst:3282 +#: ../common/cli_install_openstack_command_line_clients.rst:191 +#: ../common/cli_install_openstack_command_line_clients.rst:197 +#: ../common/cli_install_openstack_command_line_clients.rst:199 +#: ../common/cli_install_openstack_command_line_clients.rst:201 +#: ../common/cli_install_openstack_command_line_clients.rst:203 +msgid "For Mac OS X or Linux::" +msgstr "" + +#: ../common/cli_install_openstack_command_line_clients.rst:195 +#: ../common/cli_install_openstack_command_line_clients.rst:201 +#: ../common/cli_install_openstack_command_line_clients.rst:203 +#: ../common/cli_install_openstack_command_line_clients.rst:205 +#: ../common/cli_install_openstack_command_line_clients.rst:207 +msgid "For Microsoft Windows::" +msgstr "" + +#: ../common/cli_install_openstack_command_line_clients.rst:202 +#: ../common/cli_install_openstack_command_line_clients.rst:208 +#: ../common/cli_install_openstack_command_line_clients.rst:210 +#: ../common/cli_install_openstack_command_line_clients.rst:212 +#: ../common/cli_install_openstack_command_line_clients.rst:214 +msgid "Installing from packages" +msgstr "" + +#: ../common/cli_install_openstack_command_line_clients.rst:204 +#: ../common/cli_install_openstack_command_line_clients.rst:210 msgid "" -"A point-in-time copy of an OpenStack storage volume or image. Use storage " -"volume snapshots to back up volumes. Use image snapshots to back up data, or " -"as \"gold\" images for additional servers." +"RDO, openSUSE and SUSE Linux Enterprise have client packages that can be " +"installed without ``pip``." msgstr "" -#: ../common/glossary.rst:750 +#: ../common/cli_install_openstack_command_line_clients.rst:207 +#: ../common/cli_install_openstack_command_line_clients.rst:213 +#: ../common/cli_install_openstack_command_line_clients.rst:215 +#: ../common/cli_install_openstack_command_line_clients.rst:217 +#: ../common/cli_install_openstack_command_line_clients.rst:219 msgid "" -"A pre-made VM image that serves as a cloudpipe server. Essentially, OpenVPN " -"running on Linux." +"On Red Hat Enterprise Linux, CentOS, or Fedora, use ``yum`` to install the " +"clients from the packaged versions available in `RDO `__::" msgstr "" -#: ../common/glossary.rst:3488 ../common/glossary.rst:3495 -#: ../common/glossary.rst:3502 ../common/glossary.rst:3510 -#: ../common/glossary.rst:3499 +#: ../common/cli_install_openstack_command_line_clients.rst:212 +#: ../common/cli_install_openstack_command_line_clients.rst:214 +#: ../common/cli_install_openstack_command_line_clients.rst:216 msgid "" -"A process that is created when a RPC call is executed; used to push the " -"message to the topic exchange." +"RDO, openSUSE, SUSE Linux Enterprise, Debian, and Ubuntu have client " +"packages that can be installed without ``pip``." msgstr "" -#: ../common/glossary.rst:948 +#: ../common/cli_install_openstack_command_line_clients.rst:213 msgid "" -"A process that runs in the background and waits for requests. May or may not " -"listen on a TCP or UDP port. Do not confuse with a worker." +"For openSUSE, use zypper to install the clients from the distribution " +"packages Service::" msgstr "" -#: ../common/glossary.rst:547 +#: ../common/cli_install_openstack_command_line_clients.rst:213 +#: ../common/cli_install_openstack_command_line_clients.rst:219 msgid "" -"A program that keeps the Image service VM image cache at or below its " -"configured maximum size." +"For openSUSE, use zypper to install the clients from the distribution " +"packages service::" msgstr "" -#: ../common/glossary.rst:2027 ../common/glossary.rst:2033 +#: ../common/cli_install_openstack_command_line_clients.rst:218 +#: ../common/cli_install_openstack_command_line_clients.rst:224 msgid "" -"A programming language that is used to create systems that involve more than " -"one computer by way of a network." +"For SUSE Linux Enterprise Server, use zypper to install the clients from the " +"distribution packages in the Open Build Service. First, add the Open Build " +"Service repository::" msgstr "" -#: ../common/glossary.rst:768 +#: ../common/cli_install_openstack_command_line_clients.rst:221 +#: ../common/cli_install_openstack_command_line_clients.rst:223 +#: ../common/cli_install_openstack_command_line_clients.rst:225 msgid "" -"A project that is not officially endorsed by the OpenStack Foundation. If " -"the project is successful enough, it might be elevated to an incubated " -"project and then to a core project, or it might be merged with the main code " -"trunk." +"For Ubuntu or Debian, use ``apt-get`` to install the clients from the " +"packaged versions::" msgstr "" -#: ../common/glossary.rst:160 +#: ../common/cli_install_openstack_command_line_clients.rst:224 +#: ../common/cli_install_openstack_command_line_clients.rst:230 +#: ../common/cli_install_openstack_command_line_clients.rst:237 +#: ../common/cli_install_openstack_command_line_clients.rst:239 +#: ../common/cli_install_openstack_command_line_clients.rst:241 +msgid "Then you can install the packages::" +msgstr "" + +#: ../common/cli_install_openstack_command_line_clients.rst:226 +#: ../common/cli_install_openstack_command_line_clients.rst:228 +#: ../common/cli_install_openstack_command_line_clients.rst:230 msgid "" -"A project that ports the shell script-based project named DevStack to Python." +"For openSUSE, use ``zypper`` to install the clients from the distribution " +"packages service::" msgstr "" -#: ../common/glossary.rst:2952 ../common/glossary.rst:2959 -#: ../common/glossary.rst:2966 ../common/glossary.rst:2968 -#: ../common/glossary.rst:2957 -msgid "A recommended architecture for an OpenStack cloud." +#: ../common/cli_install_openstack_command_line_clients.rst:229 +#: ../common/cli_install_openstack_command_line_clients.rst:235 +#: ../common/cli_install_openstack_command_line_clients.rst:242 +#: ../common/cli_install_openstack_command_line_clients.rst:244 +#: ../common/cli_install_openstack_command_line_clients.rst:246 +msgid "Upgrade or remove clients" msgstr "" -#: ../common/glossary.rst:1162 +#: ../common/cli_install_openstack_command_line_clients.rst:231 +#: ../common/cli_install_openstack_command_line_clients.rst:233 +#: ../common/cli_install_openstack_command_line_clients.rst:235 msgid "" -"A record that specifies information about a particular domain and belongs to " -"the domain." +"For SUSE Linux Enterprise Server, use ``zypper`` to install the clients from " +"the distribution packages in the Open Build Service. First, add the Open " +"Build Service repository::" msgstr "" -#: ../common/glossary.rst:1385 ../common/glossary.rst:1386 -msgid "A routing algorithm in the Compute RabbitMQ." -msgstr "" - -#: ../common/glossary.rst:1113 +#: ../common/cli_install_openstack_command_line_clients.rst:231 +#: ../common/cli_install_openstack_command_line_clients.rst:237 +#: ../common/cli_install_openstack_command_line_clients.rst:244 +#: ../common/cli_install_openstack_command_line_clients.rst:246 +#: ../common/cli_install_openstack_command_line_clients.rst:248 msgid "" -"A routing table that is created within the Compute RabbitMQ during RPC " -"calls; one is created for each RPC call that is invoked." +"To upgrade a client, add the ``--upgrade`` option to the ``pip install`` " +"command::" msgstr "" -#: ../common/glossary.rst:1893 ../common/glossary.rst:1899 +#: ../common/cli_install_openstack_command_line_clients.rst:236 +#: ../common/cli_install_openstack_command_line_clients.rst:242 +#: ../common/cli_install_openstack_command_line_clients.rst:249 +#: ../common/cli_install_openstack_command_line_clients.rst:251 +#: ../common/cli_install_openstack_command_line_clients.rst:253 +msgid "To remove the client, run the ``pip uninstall`` command::" +msgstr "" + +#: ../common/cli_install_openstack_command_line_clients.rst:241 +#: ../common/cli_install_openstack_command_line_clients.rst:247 +#: ../common/cli_install_openstack_command_line_clients.rst:254 +#: ../common/cli_install_openstack_command_line_clients.rst:256 +#: ../common/cli_install_openstack_command_line_clients.rst:258 +msgid "What's next" +msgstr "" + +#: ../common/cli_install_openstack_command_line_clients.rst:243 +#: ../common/cli_install_openstack_command_line_clients.rst:249 +#: ../common/cli_install_openstack_command_line_clients.rst:256 +#: ../common/cli_install_openstack_command_line_clients.rst:258 +#: ../common/cli_install_openstack_command_line_clients.rst:260 msgid "" -"A running VM, or a VM in a known state such as suspended, that can be used " -"like a hardware server." +"Before you can run client commands, you must create and source the :file:" +"`PROJECT-openrc.sh` file to set environment variables. See :doc:`../common/" +"cli_set_environment_variables_using_openstack_rc`." msgstr "" -#: ../common/glossary.rst:654 +#: ../common/cli_manage_images.rst:3 +msgid "Manage images" +msgstr "" + +#: ../common/cli_manage_images.rst:5 msgid "" -"A scheduling method used by Compute that randomly chooses an available host " -"from the pool." +"The cloud operator assigns roles to users. Roles determine who can upload " +"and manage images. The operator might restrict image upload and management " +"to only cloud administrators or operators." msgstr "" -#: ../common/glossary.rst:2032 ../common/glossary.rst:2038 -msgid "A scripting language that is used to build web pages." -msgstr "" - -#: ../common/glossary.rst:413 +#: ../common/cli_manage_images.rst:9 msgid "" -"A security model that focuses on data confidentiality and controlled access " -"to classified information. This model divide the entities into subjects and " -"objects. The clearance of a subject is compared to the classification of the " -"object to determine if the subject is authorized for the specific access " -"mode. The clearance or classification scheme is expressed in terms of a " -"lattice." +"You can upload images through the ``glance`` client or the Image service " +"API. Besides, you can use the ``nova`` client for the image management. The " +"latter provides mechanisms to list and delete images, set and delete image " +"metadata, and create images of a running instance of snapshot and backup " +"types." msgstr "" -#: ../common/get_started_compute.rst:67 ../common/get_started_compute.rst:66 +#: ../common/cli_manage_images.rst:15 +msgid "After you upload an image, you cannot change it." +msgstr "" + +#: ../common/cli_manage_images.rst:17 msgid "" -"A server daemon that serves the Nova Cert service for X509 certificates. " -"Used to generate certificates for ``euca-bundle-image``. Only needed for the " -"EC2 API." +"For details about image creation, see the `Virtual Machine Image Guide " +"`__." msgstr "" -#: ../common/glossary.rst:3307 ../common/glossary.rst:3314 -#: ../common/glossary.rst:3321 ../common/glossary.rst:3329 -#: ../common/glossary.rst:3318 +#: ../common/cli_manage_images.rst:21 +msgid "List or get details for images (glance)" +msgstr "" + +#: ../common/cli_manage_images.rst:23 msgid "" -"A set of OpenStack resources created and managed by the Orchestration " -"service according to a given template (either an AWS CloudFormation template " -"or a Heat Orchestration Template (HOT))." +"To get a list of images and to then get further details about a single " +"image, use ``glance image-list`` and ``glance image-show``." msgstr "" -#: ../common/get_started_compute.rst:114 ../common/get_started_compute.rst:113 +#: ../common/cli_manage_images.rst:81 msgid "" -"A set of command-line interpreter commands for managing cloud resources. " -"Although it is not an OpenStack module, you can configure nova-api to " -"support this EC2 interface. For more information, see the `Eucalyptus 3.4 " -"Documentation `__." +"When viewing a list of images, you can also use ``grep`` to filter the list, " +"as follows::" msgstr "" -#: ../common/glossary.rst:3138 ../common/glossary.rst:3145 -#: ../common/glossary.rst:3152 ../common/glossary.rst:3154 -#: ../common/glossary.rst:3143 +#: ../common/cli_manage_images.rst:91 msgid "" -"A set of network traffic filtering rules that are applied to a Compute " -"instance." +"To store location metadata for images, which enables direct file access for " +"a client, update the ``/etc/glance/glance-api.conf`` file with the following " +"statements:" msgstr "" -#: ../common/glossary.rst:819 +#: ../common/cli_manage_images.rst:91 msgid "" -"A set of segment objects that Object Storage combines and sends to the " -"client." +"To store location metadata for images, which enables direct file access for " +"a client, update the ``/etc/glance/glance.conf`` file with the following " +"statements:" msgstr "" -#: ../common/glossary.rst:645 +#: ../common/cli_manage_images.rst:93 +msgid "``show_multiple_locations = True``" +msgstr "" + +#: ../common/cli_manage_images.rst:95 msgid "" -"A simple certificate authority provided by Compute for cloudpipe VPNs and VM " -"image decryption." +"``filesystem_store_metadata_file = filePath``, where filePath points to a " +"JSON file that defines the mount point for OpenStack images on your system " +"and a unique ID. For example:" msgstr "" -#: ../common/glossary.rst:2211 ../common/glossary.rst:2217 -#: ../common/glossary.rst:2206 +#: ../common/cli_manage_images.rst:105 msgid "" -"A special Object Storage object that contains the manifest for a large " -"object." +"After you restart the Image service, you can use the following syntax to " +"view the image's location information::" msgstr "" -#: ../common/glossary.rst:3007 ../common/glossary.rst:3014 -#: ../common/glossary.rst:3021 ../common/glossary.rst:3023 -#: ../common/glossary.rst:3012 +#: ../common/cli_manage_images.rst:109 msgid "" -"A special type of VM image that is booted when an instance is placed into " -"rescue mode. Allows an administrator to mount the file systems for an " -"instance to correct the problem." +"For example, using the image ID shown above, you would issue the command as " +"follows::" msgstr "" -#: ../common/glossary.rst:3257 ../common/glossary.rst:3264 -#: ../common/glossary.rst:3271 ../common/glossary.rst:3279 -#: ../common/glossary.rst:3268 +#: ../common/cli_manage_images.rst:114 +msgid "Create or update an image (glance)" +msgstr "" + +#: ../common/cli_manage_images.rst:116 +msgid "To create an image, use ``glance image-create``:" +msgstr "" + +#: ../common/cli_manage_images.rst:122 +msgid "To update an image by name or ID, use ``glance image-update``:" +msgstr "" + +#: ../common/cli_manage_images.rst:128 msgid "" -"A specification that, when implemented by a physical PCIe device, enables it " -"to appear as multiple separate PCIe devices. This enables multiple " -"virtualized guests to share direct access to the physical device, offering " -"improved performance over an equivalent virtual device. Currently supported " -"in OpenStack Havana and later releases." +"The following list explains the optional arguments that you can use with the " +"``create`` and ``update`` commands to modify image properties. For more " +"information, refer to Image service chapter in the `OpenStack Command-Line " +"Interface Reference `__." msgstr "" -#: ../common/glossary.rst:2562 ../common/glossary.rst:2569 -#: ../common/glossary.rst:2568 ../common/glossary.rst:2574 -#: ../common/glossary.rst:2576 ../common/glossary.rst:2565 +#: ../common/cli_manage_images.rst:135 +msgid "The name of the image." +msgstr "" + +#: ../common/cli_manage_images.rst:135 +msgid "``--name NAME``" +msgstr "" + +#: ../common/cli_manage_images.rst:138 msgid "" -"A standardized interface for managing compute, data, and network resources, " -"currently unsupported in OpenStack." +"The disk format of the image. Acceptable formats are ami, ari, aki, vhd, " +"vmdk, raw, qcow2, vdi, and iso." msgstr "" -#: ../common/glossary.rst:316 +#: ../common/cli_manage_images.rst:139 +msgid "``--disk-format DISK_FORMAT``" +msgstr "" + +#: ../common/cli_manage_images.rst:142 msgid "" -"A string of text provided to the client after authentication. Must be " -"provided by the user or process in subsequent requests to the API endpoint." +"The container format of the image. Acceptable formats are ami, ari, aki, " +"bare, and ovf." msgstr "" -#: ../common/glossary.rst:109 +#: ../common/cli_manage_images.rst:143 +msgid "``--container-format CONTAINER_FORMAT``" +msgstr "" + +#: ../common/cli_manage_images.rst:146 +msgid "The tenant who should own the image. The size of image data, in bytes." +msgstr "" + +#: ../common/cli_manage_images.rst:147 +msgid "``--owner TENANT_ID --size SIZE``" +msgstr "" + +#: ../common/cli_manage_images.rst:150 +msgid "The minimum size of the disk needed to boot the image, in gigabytes." +msgstr "" + +#: ../common/cli_manage_images.rst:151 +msgid "``--min-disk DISK_GB``" +msgstr "" + +#: ../common/cli_manage_images.rst:154 +msgid "The minimum amount of RAM needed to boot the image, in megabytes." +msgstr "" + +#: ../common/cli_manage_images.rst:154 +msgid "``--min-ram DISK_RAM``" +msgstr "" + +#: ../common/cli_manage_images.rst:157 msgid "" -"A subset of API calls that are accessible to authorized administrators and " -"are generally not accessible to end users or the public Internet. They can " -"exist as a separate service (keystone) or can be a subset of another API " -"(nova)." +"The URL where the data for this image resides. For example, if the image " +"data is stored in swift, you could specify ``swift://account:key@example.com/" +"container/obj``." msgstr "" -#: ../common/glossary.rst:1196 ../common/glossary.rst:1197 +#: ../common/cli_manage_images.rst:159 +msgid "``--location IMAGE_URL``" +msgstr "" + +#: ../common/cli_manage_images.rst:162 msgid "" -"A system by which Internet domain name-to-address and address-to-name " -"resolutions are determined. DNS helps navigate the Internet by translating " -"the IP address into an address that is easier to remember. For example, " -"translating 111.111.111.1 into www.yahoo.com. All domains and their " -"components, such as mail servers, utilize DNS to resolve to the appropriate " -"locations. DNS servers are usually set up in a master-slave relationship " -"such that failure of the master invokes the slave. DNS servers might also be " -"clustered or replicated such that changes made to one DNS server are " -"automatically propagated to other active servers." +"Local file that contains the disk image to be uploaded during the update. " +"Alternatively, you can pass images to the client through stdin." msgstr "" -#: ../common/glossary.rst:3185 ../common/glossary.rst:3192 -#: ../common/glossary.rst:3199 ../common/glossary.rst:3207 -#: ../common/glossary.rst:3196 +#: ../common/cli_manage_images.rst:164 +msgid "``--file FILE``" +msgstr "" + +#: ../common/cli_manage_images.rst:167 +msgid "Hash of image data to use for verification." +msgstr "" + +#: ../common/cli_manage_images.rst:167 +msgid "``--checksum CHECKSUM``" +msgstr "" + +#: ../common/cli_manage_images.rst:170 msgid "" -"A system that provides services to other system entities. In case of " -"federated identity, OpenStack Identity is the service provider." +"Similar to ``--location`` in usage, but indicates that the image server " +"should immediately copy the data and store it in its configured image store." msgstr "" -#: ../common/glossary.rst:2730 ../common/glossary.rst:2737 -#: ../common/glossary.rst:2743 ../common/glossary.rst:2745 -#: ../common/glossary.rst:2734 +#: ../common/cli_manage_images.rst:172 +msgid "``--copy-from IMAGE_URL``" +msgstr "" + +#: ../common/cli_manage_images.rst:175 +msgid "Makes an image accessible for all the tenants (admin-only by default)." +msgstr "" + +#: ../common/cli_manage_images.rst:176 +msgid "``--is-public [True|False]``" +msgstr "" + +#: ../common/cli_manage_images.rst:179 +msgid "Prevents an image from being deleted." +msgstr "" + +#: ../common/cli_manage_images.rst:179 +msgid "``--is-protected [True|False]``" +msgstr "" + +#: ../common/cli_manage_images.rst:182 msgid "" -"A tool to automate system configuration and installation on Debian-based " -"Linux distributions." +"Arbitrary property to associate with image. This option can be used multiple " +"times." msgstr "" -#: ../common/glossary.rst:2082 ../common/glossary.rst:2088 +#: ../common/cli_manage_images.rst:183 +msgid "``--property KEY=VALUE``" +msgstr "" + +#: ../common/cli_manage_images.rst:186 msgid "" -"A tool to automate system configuration and installation on Red Hat, Fedora, " -"and CentOS-based Linux distributions." +"Deletes all image properties that are not explicitly set in the update " +"request. Otherwise, those properties not referenced are preserved." msgstr "" -#: ../common/glossary.rst:486 -msgid "A type of VM image that exists as a single, bootable file." +#: ../common/cli_manage_images.rst:188 +msgid "``--purge-props``" msgstr "" -#: ../common/glossary.rst:1591 ../common/glossary.rst:1592 +#: ../common/cli_manage_images.rst:191 +msgid "Prints the image size in a human-friendly format." +msgstr "" + +#: ../common/cli_manage_images.rst:192 +msgid "``--human-readable``" +msgstr "" + +#: ../common/cli_manage_images.rst:194 msgid "" -"A type of image file that is commonly used for animated images on web pages." +"The following example shows the command that you would use to upload a " +"CentOS 6.3 image in qcow2 format and configure it for public access:" msgstr "" -#: ../common/glossary.rst:1629 ../common/glossary.rst:1635 +#: ../common/cli_manage_images.rst:202 msgid "" -"A type of reboot where a physical or virtual power button is pressed as " -"opposed to a graceful, proper shutdown of the operating system." +"The following example shows how to update an existing image with a " +"properties that describe the disk bus, the CD-ROM bus, and the VIF model:" msgstr "" -#: ../common/glossary.rst:975 -msgid "A unique ID given to each replica of an Object Storage database." -msgstr "" - -#: ../common/glossary.rst:2645 ../common/glossary.rst:2652 -#: ../common/glossary.rst:2658 ../common/glossary.rst:2660 -#: ../common/glossary.rst:2649 +#: ../common/cli_manage_images.rst:214 msgid "" -"A unit of storage within Object Storage used to store objects. It exists on " -"top of devices and is replicated for fault tolerance." +"Currently the libvirt virtualization tool determines the disk, CD-ROM, and " +"VIF device models based on the configured hypervisor type (``libvirt_type`` " +"in ``/etc/nova/nova.conf``). For the sake of optimal performance, libvirt " +"defaults to using virtio for both disk and VIF (NIC) models. The " +"disadvantage of this approach is that it is not possible to run operating " +"systems that lack virtio drivers, for example, BSD, Solaris, and older " +"versions of Linux and Windows." +msgstr "" + +#: ../common/cli_manage_images.rst:222 +msgid "" +"If you specify a disk or CD-ROM bus model that is not supported, see the " +"Disk_and_CD-ROM_bus_model_values_table_. If you specify a VIF model that is " +"not supported, the instance fails to launch. See the VIF_model_values_table_." +msgstr "" + +#: ../common/cli_manage_images.rst:227 +msgid "" +"The valid model values depend on the ``libvirt_type`` setting, as shown in " +"the following tables." +msgstr "" + +#: ../common/cli_manage_images.rst:232 +msgid "**Disk and CD-ROM bus model values**" +msgstr "" + +#: ../common/cli_manage_images.rst:235 ../common/cli_manage_images.rst:254 +msgid "Supported model values" +msgstr "" + +#: ../common/cli_manage_images.rst:235 ../common/cli_manage_images.rst:254 +msgid "libvirt\\_type setting" +msgstr "" + +#: ../common/cli_manage_images.rst:237 ../common/cli_manage_images.rst:243 +msgid "ide" +msgstr "" + +#: ../common/cli_manage_images.rst:237 ../common/cli_manage_images.rst:256 +msgid "qemu or kvm" +msgstr "" + +#: ../common/cli_manage_images.rst:239 +msgid "scsi" +msgstr "" + +#: ../common/cli_manage_images.rst:241 ../common/cli_manage_images.rst:264 +msgid "virtio" +msgstr "" + +#: ../common/cli_manage_images.rst:243 ../common/cli_manage_images.rst:245 +#: ../common/cli_manage_images.rst:266 +msgid "xen" +msgstr "" + +#: ../common/cli_manage_images.rst:251 +msgid "**VIF model values**" +msgstr "" + +#: ../common/cli_manage_images.rst:256 ../common/cli_manage_images.rst:266 +msgid "e1000" +msgstr "" + +#: ../common/cli_manage_images.rst:258 ../common/cli_manage_images.rst:270 +msgid "ne2k\\_pci" +msgstr "" + +#: ../common/cli_manage_images.rst:260 ../common/cli_manage_images.rst:272 +msgid "pcnet" +msgstr "" + +#: ../common/cli_manage_images.rst:262 ../common/cli_manage_images.rst:274 +msgid "rtl8139" +msgstr "" + +#: ../common/cli_manage_images.rst:268 +msgid "netfront" +msgstr "" + +#: ../common/cli_manage_images.rst:276 +msgid "VirtualE1000" +msgstr "" + +#: ../common/cli_manage_images.rst:276 +msgid "vmware" +msgstr "" + +#: ../common/cli_manage_images.rst:278 +msgid "VirtualPCNet32" +msgstr "" + +#: ../common/cli_manage_images.rst:280 +msgid "VirtualVmxnet" +msgstr "" + +#: ../common/cli_manage_images.rst:284 +msgid "Troubleshoot image creation" +msgstr "" + +#: ../common/cli_manage_images.rst:286 +msgid "" +"If you encounter problems in creating an image in Image service or Compute, " +"the following information may help you troubleshoot the creation process." +msgstr "" + +#: ../common/cli_manage_images.rst:290 +msgid "" +"Ensure that the version of qemu you are using is version 0.14 or later. " +"Earlier versions of qemu result in an ``unknown option -s`` error message in " +"the ``nova-compute.log`` file." +msgstr "" + +#: ../common/cli_manage_images.rst:294 +msgid "" +"Examine the :file:`/var/log/nova-api.log` and :file:`/var/log/nova-compute." +"log` log files for error messages." +msgstr "" + +#: ../common/cli_manage_volumes.rst:5 +msgid "Manage volumes" +msgstr "" + +#: ../common/cli_manage_volumes.rst:7 +msgid "" +"A volume is a detachable block storage device, similar to a USB hard drive. " +"You can attach a volume to only one instance. To create and manage volumes, " +"you use a combination of ``nova`` and ``cinder`` client commands." +msgstr "" + +#: ../common/cli_manage_volumes.rst:13 +msgid "Migrate a volume" +msgstr "" + +#: ../common/cli_manage_volumes.rst:15 +msgid "" +"As an administrator, you can migrate a volume with its data from one " +"location to another in a manner that is transparent to users and workloads. " +"You can migrate only detached volumes with no snapshots." +msgstr "" + +#: ../common/cli_manage_volumes.rst:19 +msgid "Possible use cases for data migration include:" +msgstr "" + +#: ../common/cli_manage_volumes.rst:21 +msgid "" +"Bring down a physical storage device for maintenance without disrupting " +"workloads." +msgstr "" + +#: ../common/cli_manage_volumes.rst:24 +msgid "Modify the properties of a volume." +msgstr "" + +#: ../common/cli_manage_volumes.rst:26 +msgid "Free up space in a thinly-provisioned back end." +msgstr "" + +#: ../common/cli_manage_volumes.rst:28 +msgid "" +"Migrate a volume with the :command:`cinder migrate` command, as shown in the " +"following example::" +msgstr "" + +#: ../common/cli_manage_volumes.rst:33 +msgid "" +"In this example, ``--force-host-copy True`` forces the generic host-based " +"migration mechanism and bypasses any driver optimizations." +msgstr "" + +#: ../common/cli_manage_volumes.rst:38 +msgid "" +"If the volume is in use or has snapshots, the specified host destination " +"cannot accept the volume. If the user is not an administrator, the migration " +"fails." +msgstr "" + +#: ../common/cli_manage_volumes.rst:43 +msgid "Create a volume" +msgstr "" + +#: ../common/cli_manage_volumes.rst:45 +msgid "This example creates a my-new-volume volume based on an image." +msgstr "" + +#: ../common/cli_manage_volumes.rst:47 +msgid "" +"List images, and note the ID of the image that you want to use for your " +"volume::" +msgstr "" + +#: ../common/cli_manage_volumes.rst:62 +msgid "" +"List the availability zones, and note the ID of the availability zone in " +"which you want to create your volume::" +msgstr "" + +#: ../common/cli_manage_volumes.rst:73 +msgid "" +"Create a volume with 8 gibibytes (GiB) of space, and specify the " +"availability zone and image::" +msgstr "" + +#: ../common/cli_manage_volumes.rst:98 +msgid "" +"To verify that your volume was created successfully, list the available " +"volumes::" +msgstr "" + +#: ../common/cli_manage_volumes.rst:110 +msgid "" +"If your volume was created successfully, its status is ``available``. If its " +"status is ``error``, you might have exceeded your quota." +msgstr "" + +#: ../common/cli_manage_volumes.rst:116 +msgid "Attach a volume to an instance" +msgstr "" + +#: ../common/cli_manage_volumes.rst:118 +msgid "" +"Attach your volume to a server, specifying the server ID and the volume ID::" +msgstr "" + +#: ../common/cli_manage_volumes.rst:132 +msgid "Note the ID of your volume." +msgstr "" + +#: ../common/cli_manage_volumes.rst:134 +msgid "Show information for your volume:" +msgstr "" + +#: ../common/cli_manage_volumes.rst:140 +msgid "" +"The output shows that the volume is attached to the server with ID " +"``84c6e57d-a6b1-44b6-81eb-fcb36afd31b5``, is in the nova availability zone, " +"and is bootable." +msgstr "" + +#: ../common/cli_manage_volumes.rst:176 +msgid "Resize a volume" +msgstr "" + +#: ../common/cli_manage_volumes.rst:178 +msgid "" +"To resize your volume, you must first detach it from the server. To detach " +"the volume from your server, pass the server ID and volume ID to the " +"following command:" +msgstr "" + +#: ../common/cli_manage_volumes.rst:186 +msgid "The ``volume-detach`` command does not return any output." +msgstr "" + +#: ../common/cli_manage_volumes.rst:188 +msgid "List volumes::" +msgstr "" + +#: ../common/cli_manage_volumes.rst:201 +msgid "Note that the volume is now available." +msgstr "" + +#: ../common/cli_manage_volumes.rst:203 +msgid "" +"Resize the volume by passing the volume ID and the new size (a value greater " +"than the old one) as parameters::" +msgstr "" + +#: ../common/cli_manage_volumes.rst:208 +msgid "The ``extend`` command does not return any output." +msgstr "" + +#: ../common/cli_manage_volumes.rst:211 +msgid "Delete a volume" +msgstr "" + +#: ../common/cli_manage_volumes.rst:213 +msgid "" +"To delete your volume, you must first detach it from the server. To detach " +"the volume from your server and check for the list of existing volumes, see " +"steps 1 and 2 in Resize_a_volume_." +msgstr "" + +#: ../common/cli_manage_volumes.rst:217 +msgid "Delete the volume using either the volume name or ID::" +msgstr "" + +#: ../common/cli_manage_volumes.rst:221 +msgid "The delete command does not return any output." +msgstr "" + +#: ../common/cli_manage_volumes.rst:223 +msgid "" +"List the volumes again, and note that the status of your volume is " +"``deleting``::" +msgstr "" + +#: ../common/cli_manage_volumes.rst:237 +msgid "" +"When the volume is fully deleted, it disappears from the list of volumes::" +msgstr "" + +#: ../common/cli_manage_volumes.rst:251 +msgid "Transfer a volume" +msgstr "" + +#: ../common/cli_manage_volumes.rst:253 +msgid "" +"You can transfer a volume from one owner to another by using the ``cinder " +"transfer*`` commands. The volume donor, or original owner, creates a " +"transfer request and sends the created transfer ID and authorization key to " +"the volume recipient. The volume recipient, or new owner, accepts the " +"transfer by using the ID and key." +msgstr "" + +#: ../common/cli_manage_volumes.rst:261 +msgid "" +"The procedure for volume transfer is intended for tenants (both the volume " +"donor and recipient) within the same cloud." +msgstr "" + +#: ../common/cli_manage_volumes.rst:264 +msgid "Use cases include:" +msgstr "" + +#: ../common/cli_manage_volumes.rst:266 +msgid "" +"Create a custom bootable volume or a volume with a large data set and " +"transfer it to a customer." +msgstr "" + +#: ../common/cli_manage_volumes.rst:269 +msgid "" +"For bulk import of data to the cloud, the data ingress system creates a new " +"Block Storage volume, copies data from the physical device, and transfers " +"device ownership to the end user." +msgstr "" + +#: ../common/cli_manage_volumes.rst:274 +msgid "Create a volume transfer request" +msgstr "" + +#: ../common/cli_manage_volumes.rst:276 +msgid "While logged in as the volume donor, list the available volumes::" +msgstr "" + +#: ../common/cli_manage_volumes.rst:289 +msgid "" +"As the volume donor, request a volume transfer authorization code for a " +"specific volume::" +msgstr "" + +#: ../common/cli_manage_volumes.rst:294 +msgid "" +"The volume must be in an ``available`` state or the request will be denied. " +"If the transfer request is valid in the database (that is, it has not " +"expired or been deleted), the volume is placed in an ``awaiting transfer`` " +"state. For example::" +msgstr "" + +#: ../common/cli_manage_volumes.rst:301 +msgid "" +"The output shows the volume transfer ID in the ``id`` row and the " +"authorization key." +msgstr "" + +#: ../common/cli_manage_volumes.rst:318 +msgid "" +"Optionally, you can specify a name for the transfer by using the ``--display-" +"name displayName`` parameter." +msgstr "" + +#: ../common/cli_manage_volumes.rst:323 +msgid "" +"While the ``auth_key`` property is visible in the output of ``cinder " +"transfer-create VOLUME_ID``, it will not be available in subsequent ``cinder " +"transfer-show TRANSFER_ID`` commands." +msgstr "" + +#: ../common/cli_manage_volumes.rst:327 +msgid "" +"Send the volume transfer ID and authorization key to the new owner (for " +"example, by email)." +msgstr "" + +#: ../common/cli_manage_volumes.rst:330 +msgid "View pending transfers::" +msgstr "" + +#: ../common/cli_manage_volumes.rst:342 +msgid "" +"After the volume recipient, or new owner, accepts the transfer, you can see " +"that the transfer is no longer available::" +msgstr "" + +#: ../common/cli_manage_volumes.rst:355 +msgid "Accept a volume transfer request" +msgstr "" + +#: ../common/cli_manage_volumes.rst:357 +msgid "" +"As the volume recipient, you must first obtain the transfer ID and " +"authorization key from the original owner." +msgstr "" + +#: ../common/cli_manage_volumes.rst:360 +msgid "Accept the request::" +msgstr "" + +#: ../common/cli_manage_volumes.rst:364 +msgid "For example::" +msgstr "" + +#: ../common/cli_manage_volumes.rst:380 +msgid "" +"If you do not have a sufficient quota for the transfer, the transfer is " +"refused." +msgstr "" + +#: ../common/cli_manage_volumes.rst:384 +msgid "Delete a volume transfer" +msgstr "" + +#: ../common/cli_manage_volumes.rst:386 +msgid "List available volumes and their statuses::" +msgstr "" + +#: ../common/cli_manage_volumes.rst:399 +msgid "Find the matching transfer ID::" +msgstr "" + +#: ../common/cli_manage_volumes.rst:411 +msgid "Delete the volume::" +msgstr "" + +#: ../common/cli_manage_volumes.rst:415 +msgid "For example:" +msgstr "" + +#: ../common/cli_manage_volumes.rst:421 +msgid "" +"Verify that transfer list is now empty and that the volume is again " +"available for transfer::" +msgstr "" + +#: ../common/cli_nova_evacuate.rst:5 +msgid "Evacuate instances" +msgstr "" + +#: ../common/cli_nova_evacuate.rst:7 +msgid "" +"If a cloud compute node fails due to a hardware malfunction or another " +"reason, you can evacuate instances to make them available again. You can " +"optionally include the target host on the :command:`evacuate` command. If " +"you omit the host, the scheduler determines the target host." +msgstr "" + +#: ../common/cli_nova_evacuate.rst:13 +msgid "" +"To preserve user data on server disk, you must configure shared storage on " +"the target host. Also, you must validate that the current VM host is down; " +"otherwise, the evacuation fails with an error." +msgstr "" + +#: ../common/cli_nova_evacuate.rst:17 +msgid "" +"To list hosts and find a different host for the evacuated instance, run::" +msgstr "" + +#: ../common/cli_nova_evacuate.rst:21 +msgid "" +"Evacuate the instance. You can pass the instance password to the command by " +"using the :option:`--password PWD` option. If you do not specify a password, " +"one is generated and printed after the command finishes successfully. The " +"following command evacuates a server without shared storage from a host that " +"is down to the specified HOST_B::" +msgstr "" + +#: ../common/cli_nova_evacuate.rst:30 +msgid "" +"The instance is booted from a new disk, but preserves its configuration " +"including its ID, name, uid, IP address, and so on. The command returns a " +"password::" +msgstr "" + +#: ../common/cli_nova_evacuate.rst:40 +msgid "" +"To preserve the user disk data on the evacuated server, deploy OpenStack " +"Compute with a shared file system. To configure your system, see `Configure " +"migrations `_ in OpenStack Cloud Administrator Guide. In the following " +"example, the password remains unchanged::" +msgstr "" + +#: ../common/cli_nova_evacuate.rst:40 +msgid "" +"To preserve the user disk data on the evacuated server, deploy OpenStack " +"Compute with a shared file system. To configure your system, see `Configure " +"migrations `_ in OpenStack Cloud " +"Administrator Guide. In the following example, the password remains " +"unchanged::" +msgstr "" + +#: ../common/cli_overview.rst:3 +msgid "Overview" +msgstr "" + +#: ../common/cli_overview.rst:5 +msgid "" +"Each OpenStack project provides a command-line client, which enables you to " +"access the project API through easy-to-use commands. For example, the " +"Compute service provides a nova command-line client." +msgstr "" + +#: ../common/cli_overview.rst:9 +msgid "" +"You can run the commands from the command line, or include the commands " +"within scripts to automate tasks. If you provide OpenStack credentials, such " +"as your user name and password, you can run these commands on any computer." +msgstr "" + +#: ../common/cli_overview.rst:14 +msgid "" +"Internally, each command uses cURL command-line tools, which embed API " +"requests. OpenStack APIs are RESTful APIs, and use the HTTP protocol. They " +"include methods, URIs, media types, and response codes." +msgstr "" + +#: ../common/cli_overview.rst:18 +msgid "" +"OpenStack APIs are open-source Python clients, and can run on Linux or Mac " +"OS X systems. On some client commands, you can specify a debug parameter to " +"show the underlying API request for the command. This is a good way to " +"become familiar with the OpenStack API calls." +msgstr "" + +#: ../common/cli_overview.rst:23 +msgid "" +"As a cloud end user, you can use the OpenStack dashboard to provision your " +"own resources within the limits set by administrators. You can modify the " +"examples provided in this section to create other types and sizes of server " +"instances." +msgstr "" + +#: ../common/cli_overview.rst:28 +msgid "" +"The following table lists the command-line client for each OpenStack service " +"with its package name and description." +msgstr "" + +#: ../common/cli_overview.rst:32 +msgid "Client" +msgstr "" + +#: ../common/cli_overview.rst:32 +msgid "Package" +msgstr "" + +#: ../common/cli_overview.rst:32 ../common/get_started_identity.rst:61 +#: ../common/get_started_identity.rst:62 +#: ../common/get_started_with_openstack.rst:25 +#: ../common/get_started_with_openstack.rst:33 +msgid "Service" +msgstr "" + +#: ../common/cli_overview.rst:34 ../common/glossary.rst:227 +msgid "Application catalog" +msgstr "" + +#: ../common/cli_overview.rst:34 ../common/cli_overview.rst:37 +#: ../common/glossary.rst:463 +msgid "Block Storage" +msgstr "" + +#: ../common/cli_overview.rst:34 +msgid "Create and manage applications." +msgstr "" + +#: ../common/cli_overview.rst:34 ../common/cli_overview.rst:37 +msgid "Create and manage volumes." +msgstr "" + +#: ../common/cli_overview.rst:34 ../common/cli_overview.rst:37 +#: ../common/glossary.rst:675 +msgid "cinder" +msgstr "" + +#: ../common/cli_overview.rst:34 ../common/glossary.rst:2311 +#: ../common/glossary.rst:2312 ../common/glossary.rst:2317 +#: ../common/glossary.rst:2318 ../common/glossary.rst:2323 +msgid "murano" +msgstr "" + +#: ../common/cli_overview.rst:34 ../common/cli_overview.rst:37 +msgid "python-cinderclient" +msgstr "" + +#: ../common/cli_overview.rst:34 +msgid "python-muranoclient" +msgstr "" + +#: ../common/cli_overview.rst:37 ../common/cli_overview.rst:40 +#: ../common/glossary.rst:780 +msgid "Compute" +msgstr "" + +#: ../common/cli_overview.rst:37 ../common/cli_overview.rst:40 +msgid "Create and manage images, instances, and flavors." +msgstr "" + +#: ../common/cli_overview.rst:37 ../common/cli_overview.rst:40 +#: ../common/glossary.rst:2486 ../common/glossary.rst:2489 +#: ../common/glossary.rst:2492 ../common/glossary.rst:2493 +#: ../common/glossary.rst:2498 ../common/glossary.rst:2500 +msgid "nova" +msgstr "" + +#: ../common/cli_overview.rst:37 ../common/cli_overview.rst:40 +msgid "python-novaclient" +msgstr "" + +#: ../common/cli_overview.rst:41 ../common/cli_overview.rst:47 +msgid "Create and manage databases." +msgstr "" + +#: ../common/cli_overview.rst:41 ../common/cli_overview.rst:47 +#: ../common/glossary.rst:982 +msgid "Database service" +msgstr "" + +#: ../common/cli_overview.rst:41 ../common/cli_overview.rst:47 +msgid "python-troveclient" +msgstr "" + +#: ../common/cli_overview.rst:41 ../common/cli_overview.rst:47 +#: ../common/glossary.rst:3522 ../common/glossary.rst:3529 +#: ../common/glossary.rst:3533 ../common/glossary.rst:3536 +#: ../common/glossary.rst:3544 +msgid "trove" +msgstr "" + +#: ../common/cli_overview.rst:44 ../common/glossary.rst:865 +msgid "Containers service" +msgstr "" + +#: ../common/cli_overview.rst:44 +msgid "Create and manage containers." +msgstr "" + +#: ../common/cli_overview.rst:44 ../common/cli_overview.rst:50 +#: ../common/cli_overview.rst:54 ../common/cli_overview.rst:57 +msgid "Create and manage users, tenants, roles, endpoints, and credentials." +msgstr "" + +#: ../common/cli_overview.rst:44 ../common/cli_overview.rst:50 +#: ../common/cli_overview.rst:54 ../common/cli_overview.rst:57 +#: ../common/glossary.rst:1788 ../common/glossary.rst:1794 +msgid "Identity" +msgstr "" + +#: ../common/cli_overview.rst:44 ../common/cli_overview.rst:50 +#: ../common/cli_overview.rst:54 ../common/cli_overview.rst:57 +#: ../common/glossary.rst:2075 ../common/glossary.rst:2081 +msgid "keystone" +msgstr "" + +#: ../common/cli_overview.rst:44 ../common/glossary.rst:2179 +#: ../common/glossary.rst:2184 ../common/glossary.rst:2190 +msgid "magnum" +msgstr "" + +#: ../common/cli_overview.rst:44 ../common/cli_overview.rst:50 +#: ../common/cli_overview.rst:54 ../common/cli_overview.rst:57 +msgid "python-keystoneclient" +msgstr "" + +#: ../common/cli_overview.rst:44 +msgid "python-magnumclient" +msgstr "" + +#: ../common/cli_overview.rst:49 ../common/cli_overview.rst:55 +#: ../common/cli_overview.rst:59 ../common/cli_overview.rst:62 +msgid "Create and manage images." +msgstr "" + +#: ../common/cli_overview.rst:49 ../common/cli_overview.rst:55 +#: ../common/cli_overview.rst:59 ../common/cli_overview.rst:62 +#: ../common/glossary.rst:1844 ../common/glossary.rst:1850 +msgid "Image service" +msgstr "" + +#: ../common/cli_overview.rst:49 ../common/cli_overview.rst:55 +#: ../common/cli_overview.rst:59 ../common/cli_overview.rst:62 +#: ../common/glossary.rst:1551 ../common/glossary.rst:1552 +msgid "glance" +msgstr "" + +#: ../common/cli_overview.rst:49 ../common/cli_overview.rst:55 +#: ../common/cli_overview.rst:59 ../common/cli_overview.rst:62 +msgid "python-glanceclient" +msgstr "" + +#: ../common/cli_overview.rst:50 ../common/cli_overview.rst:76 +#: ../common/cli_overview.rst:85 ../common/cli_overview.rst:88 +msgid "Create and manage Hadoop clusters on OpenStack." +msgstr "" + +#: ../common/cli_overview.rst:50 ../common/cli_overview.rst:76 +#: ../common/cli_overview.rst:85 ../common/cli_overview.rst:88 +msgid "Data processing" +msgstr "" + +#: ../common/cli_overview.rst:50 ../common/cli_overview.rst:76 +#: ../common/cli_overview.rst:85 ../common/cli_overview.rst:88 +msgid "python-saharaclient" +msgstr "" + +#: ../common/cli_overview.rst:50 ../common/cli_overview.rst:76 +#: ../common/cli_overview.rst:85 ../common/cli_overview.rst:88 +#: ../common/glossary.rst:3098 ../common/glossary.rst:3103 +#: ../common/glossary.rst:3105 ../common/glossary.rst:3112 +#: ../common/glossary.rst:3114 +msgid "sahara" +msgstr "" + +#: ../common/cli_overview.rst:52 ../common/cli_overview.rst:58 +#: ../common/cli_overview.rst:61 ../common/cli_overview.rst:65 +#: ../common/cli_overview.rst:68 +msgid "Configure networks for guest servers." +msgstr "" + +#: ../common/cli_overview.rst:52 ../common/cli_overview.rst:58 +#: ../common/cli_overview.rst:61 ../common/cli_overview.rst:65 +#: ../common/cli_overview.rst:68 ../common/glossary.rst:2422 +#: ../common/glossary.rst:2425 ../common/glossary.rst:2428 +#: ../common/glossary.rst:2429 ../common/glossary.rst:2434 +#: ../common/glossary.rst:2436 +msgid "Networking" +msgstr "" + +#: ../common/cli_overview.rst:52 ../common/cli_overview.rst:58 +#: ../common/cli_overview.rst:61 ../common/cli_overview.rst:65 +#: ../common/cli_overview.rst:68 ../common/glossary.rst:2433 +#: ../common/glossary.rst:2436 ../common/glossary.rst:2439 +#: ../common/glossary.rst:2440 ../common/glossary.rst:2445 +#: ../common/glossary.rst:2447 +msgid "neutron" +msgstr "" + +#: ../common/cli_overview.rst:52 ../common/cli_overview.rst:58 +#: ../common/cli_overview.rst:61 ../common/cli_overview.rst:65 +#: ../common/cli_overview.rst:68 +msgid "python-neutronclient" +msgstr "" + +#: ../common/cli_overview.rst:54 +msgid "Deployment service" +msgstr "" + +#: ../common/cli_overview.rst:54 +msgid "Plan Deployments." +msgstr "" + +#: ../common/cli_overview.rst:54 +msgid "python-tuskarclient" +msgstr "" + +#: ../common/cli_overview.rst:54 +msgid "tuskar" +msgstr "" + +#: ../common/cli_overview.rst:55 ../common/cli_overview.rst:61 +#: ../common/cli_overview.rst:64 ../common/cli_overview.rst:68 +#: ../common/cli_overview.rst:71 +msgid "" +"Gather statistics, list items, update metadata, and upload, download, and " +"delete files stored by the Object Storage service. Gain access to an Object " +"Storage installation for ad hoc processing." +msgstr "" + +#: ../common/cli_overview.rst:55 ../common/cli_overview.rst:61 +#: ../common/cli_overview.rst:64 ../common/cli_overview.rst:68 +#: ../common/cli_overview.rst:71 ../common/glossary.rst:2535 +#: ../common/glossary.rst:2538 ../common/glossary.rst:2541 +#: ../common/glossary.rst:2542 ../common/glossary.rst:2547 +#: ../common/glossary.rst:2549 +msgid "Object Storage" +msgstr "" + +#: ../common/cli_overview.rst:55 ../common/cli_overview.rst:61 +#: ../common/cli_overview.rst:64 ../common/cli_overview.rst:68 +#: ../common/cli_overview.rst:71 +msgid "python-swiftclient" +msgstr "" + +#: ../common/cli_overview.rst:55 ../common/cli_overview.rst:61 +#: ../common/cli_overview.rst:64 ../common/cli_overview.rst:68 +#: ../common/cli_overview.rst:71 ../common/glossary.rst:3386 +#: ../common/glossary.rst:3393 ../common/glossary.rst:3397 +#: ../common/glossary.rst:3400 ../common/glossary.rst:3408 +msgid "swift" +msgstr "" + +#: ../common/cli_overview.rst:58 ../common/cli_overview.rst:62 +#: ../common/cli_overview.rst:65 +msgid "Create and manage keys." +msgstr "" + +#: ../common/cli_overview.rst:58 ../common/cli_overview.rst:62 +#: ../common/cli_overview.rst:65 +msgid "Key Manager service" +msgstr "" + +#: ../common/cli_overview.rst:58 ../common/cli_overview.rst:62 +#: ../common/cli_overview.rst:65 ../common/glossary.rst:392 +msgid "barbican" +msgstr "" + +#: ../common/cli_overview.rst:58 ../common/cli_overview.rst:62 +#: ../common/cli_overview.rst:65 +msgid "python-barbicanclient" +msgstr "" + +#: ../common/cli_overview.rst:65 ../common/cli_overview.rst:71 +#: ../common/cli_overview.rst:74 ../common/cli_overview.rst:78 +#: ../common/cli_overview.rst:81 +msgid "" +"Launch stacks from templates, view details of running stacks including " +"events and resources, and update and delete stacks." +msgstr "" + +#: ../common/cli_overview.rst:65 ../common/cli_overview.rst:71 +#: ../common/cli_overview.rst:74 ../common/cli_overview.rst:78 +#: ../common/cli_overview.rst:81 ../common/glossary.rst:2620 +#: ../common/glossary.rst:2624 ../common/glossary.rst:2627 +#: ../common/glossary.rst:2633 ../common/glossary.rst:2635 +msgid "Orchestration" +msgstr "" + +#: ../common/cli_overview.rst:65 ../common/cli_overview.rst:71 +#: ../common/cli_overview.rst:74 ../common/cli_overview.rst:78 +#: ../common/cli_overview.rst:81 ../common/glossary.rst:1638 +#: ../common/glossary.rst:1644 +msgid "heat" +msgstr "" + +#: ../common/cli_overview.rst:65 ../common/cli_overview.rst:71 +#: ../common/cli_overview.rst:74 ../common/cli_overview.rst:78 +#: ../common/cli_overview.rst:81 +msgid "python-heatclient" +msgstr "" + +#: ../common/cli_overview.rst:72 ../common/cli_overview.rst:81 +#: ../common/cli_overview.rst:84 ../common/cli_overview.rst:88 +#: ../common/cli_overview.rst:91 +msgid "Create and collect measurements across OpenStack." +msgstr "" + +#: ../common/cli_overview.rst:72 ../common/cli_overview.rst:81 +#: ../common/cli_overview.rst:84 ../common/cli_overview.rst:88 +#: ../common/cli_overview.rst:91 ../common/glossary.rst:3428 +#: ../common/glossary.rst:3435 ../common/glossary.rst:3439 +#: ../common/glossary.rst:3442 ../common/glossary.rst:3450 +msgid "Telemetry" +msgstr "" + +#: ../common/cli_overview.rst:72 ../common/cli_overview.rst:81 +#: ../common/cli_overview.rst:84 ../common/cli_overview.rst:88 +#: ../common/cli_overview.rst:91 ../common/glossary.rst:603 +msgid "ceilometer" +msgstr "" + +#: ../common/cli_overview.rst:72 ../common/cli_overview.rst:81 +#: ../common/cli_overview.rst:84 ../common/cli_overview.rst:88 +#: ../common/cli_overview.rst:91 +msgid "python-ceilometerclient" +msgstr "" + +#: ../common/cli_overview.rst:78 +msgid "Create and manage shared file systems" +msgstr "" + +#: ../common/cli_overview.rst:78 ../common/cli_overview.rst:81 +#: ../common/cli_overview.rst:85 ../common/cli_overview.rst:88 +msgid "Shared file systems" +msgstr "" + +#: ../common/cli_overview.rst:78 ../common/cli_overview.rst:81 +#: ../common/cli_overview.rst:85 ../common/cli_overview.rst:88 +#: ../common/glossary.rst:2208 ../common/glossary.rst:2213 +#: ../common/glossary.rst:2219 +msgid "manila" +msgstr "" + +#: ../common/cli_overview.rst:78 ../common/cli_overview.rst:81 +#: ../common/cli_overview.rst:85 ../common/cli_overview.rst:88 +msgid "python-manilaclient" +msgstr "" + +#: ../common/cli_overview.rst:80 ../common/cli_overview.rst:89 +#: ../common/cli_overview.rst:92 ../common/cli_overview.rst:95 +#: ../common/cli_overview.rst:98 +msgid "Common client" +msgstr "" + +#: ../common/cli_overview.rst:80 ../common/cli_overview.rst:89 +#: ../common/cli_overview.rst:92 ../common/cli_overview.rst:95 +#: ../common/cli_overview.rst:98 +msgid "Common client for the OpenStack project." +msgstr "" + +#: ../common/cli_overview.rst:80 ../common/cli_overview.rst:89 +#: ../common/cli_overview.rst:92 ../common/cli_overview.rst:95 +#: ../common/cli_overview.rst:98 +msgid "openstack" +msgstr "" + +#: ../common/cli_overview.rst:80 ../common/cli_overview.rst:89 +#: ../common/cli_overview.rst:92 ../common/cli_overview.rst:95 +#: ../common/cli_overview.rst:98 +msgid "python-openstackclient" +msgstr "" + +#: ../common/cli_overview.rst:81 ../common/cli_overview.rst:85 +#: ../common/cli_overview.rst:88 +msgid "Create and manage shared file systems." +msgstr "" + +#: ../common/cli_overview.rst:92 ../common/cli_overview.rst:95 +#: ../common/glossary.rst:3765 ../common/glossary.rst:3772 +#: ../common/glossary.rst:3776 ../common/glossary.rst:3779 +#: ../common/glossary.rst:3787 +msgid "Workflow service" +msgstr "" + +#: ../common/cli_overview.rst:92 ../common/cli_overview.rst:95 +msgid "Workflow service for OpenStack cloud." +msgstr "" + +#: ../common/cli_overview.rst:92 ../common/cli_overview.rst:95 +#: ../common/glossary.rst:2290 ../common/glossary.rst:2295 +#: ../common/glossary.rst:2301 ../common/glossary.rst:2302 +msgid "mistral" +msgstr "" + +#: ../common/cli_overview.rst:92 ../common/cli_overview.rst:95 +msgid "python-mistralclient" +msgstr "" + +#: ../common/cli_set_environment_variables_using_openstack_rc.rst:3 +msgid "Set environment variables using the OpenStack RC file" +msgstr "" + +#: ../common/cli_set_environment_variables_using_openstack_rc.rst:5 +msgid "" +"To set the required environment variables for the OpenStack command-line " +"clients, you must create an environment file called an OpenStack rc file, " +"or :file:`openrc.sh` file. If your OpenStack installation provides it, you " +"can download the file from the OpenStack dashboard as an administrative user " +"or any other user. This project-specific environment file contains the " +"credentials that all OpenStack services use." +msgstr "" + +#: ../common/cli_set_environment_variables_using_openstack_rc.rst:12 +msgid "" +"When you source the file, environment variables are set for your current " +"shell. The variables enable the OpenStack client commands to communicate " +"with the OpenStack services that run in the cloud." +msgstr "" + +#: ../common/cli_set_environment_variables_using_openstack_rc.rst:18 +msgid "" +"Defining environment variables using an environment file is not a common " +"practice on Microsoft Windows. Environment variables are usually defined in " +"the :guilabel:`Advanced` tab of the :guilabel:`System Properties` dialog box." +msgstr "" + +#: ../common/cli_set_environment_variables_using_openstack_rc.rst:24 +msgid "Download and source the OpenStack RC file" +msgstr "" + +#: ../common/cli_set_environment_variables_using_openstack_rc.rst:26 +msgid "" +"Log in to the OpenStack dashboard, choose the project for which you want to " +"download the OpenStack RC file, and click :guilabel:`Access & Security`." +msgstr "" + +#: ../common/cli_set_environment_variables_using_openstack_rc.rst:26 +msgid "" +"Log in to the OpenStack dashboard, choose the project for which you want to " +"download the OpenStack RC file, on the :guilabel:`Project` tab, open the :" +"guilabel:`Compute` tab and click :guilabel:`Access & Security`." +msgstr "" + +#: ../common/cli_set_environment_variables_using_openstack_rc.rst:29 +msgid "" +"On the API Access tab, click :guilabel:`Download OpenStack RC File` and save " +"the file. The filename will be of the form :file:`PROJECT-openrc.sh` where " +"``PROJECT`` is the name of the project for which you downloaded the file." +msgstr "" + +#: ../common/cli_set_environment_variables_using_openstack_rc.rst:30 +msgid "" +"On the :guilabel:`API Access` tab, click :guilabel:`Download OpenStack RC " +"File` and save the file. The filename will be of the form :file:`PROJECT-" +"openrc.sh` where ``PROJECT`` is the name of the project for which you " +"downloaded the file." +msgstr "" + +#: ../common/cli_set_environment_variables_using_openstack_rc.rst:34 +#: ../common/cli_set_environment_variables_using_openstack_rc.rst:35 +msgid "" +"Copy the :file:`PROJECT-openrc.sh` file to the computer from which you want " +"to run OpenStack commands." +msgstr "" + +#: ../common/cli_set_environment_variables_using_openstack_rc.rst:37 +#: ../common/cli_set_environment_variables_using_openstack_rc.rst:38 +msgid "" +"For example, copy the file to the computer from which you want to upload an " +"image with a ``glance`` client command." +msgstr "" + +#: ../common/cli_set_environment_variables_using_openstack_rc.rst:40 +#: ../common/cli_set_environment_variables_using_openstack_rc.rst:41 +msgid "" +"On any shell from which you want to run OpenStack commands, source the :file:" +"`PROJECT-openrc.sh` file for the respective project." +msgstr "" + +#: ../common/cli_set_environment_variables_using_openstack_rc.rst:43 +#: ../common/cli_set_environment_variables_using_openstack_rc.rst:44 +msgid "" +"In the following example, the :file:`demo-openrc.sh` file is sourced for the " +"demo project::" +msgstr "" + +#: ../common/cli_set_environment_variables_using_openstack_rc.rst:48 +#: ../common/cli_set_environment_variables_using_openstack_rc.rst:49 +msgid "" +"When you are prompted for an OpenStack password, enter the password for the " +"user who downloaded the :file:`PROJECT-openrc.sh` file." +msgstr "" + +#: ../common/cli_set_environment_variables_using_openstack_rc.rst:52 +#: ../common/cli_set_environment_variables_using_openstack_rc.rst:53 +msgid "Create and source the OpenStack RC file" +msgstr "" + +#: ../common/cli_set_environment_variables_using_openstack_rc.rst:54 +#: ../common/cli_set_environment_variables_using_openstack_rc.rst:55 +msgid "" +"Alternatively, you can create the :file:`PROJECT-openrc.sh` file from " +"scratch, if you cannot download the file from the dashboard." +msgstr "" + +#: ../common/cli_set_environment_variables_using_openstack_rc.rst:57 +#: ../common/cli_set_environment_variables_using_openstack_rc.rst:58 +msgid "" +"In a text editor, create a file named :file:`PROJECT-openrc.sh` and add the " +"following authentication information::" +msgstr "" + +#: ../common/cli_set_environment_variables_using_openstack_rc.rst:69 +#: ../common/cli_set_environment_variables_using_openstack_rc.rst:70 +msgid "" +"On any shell from which you want to run OpenStack commands, source the :file:" +"`PROJECT-openrc.sh` file for the respective project. In this example, you " +"source the :file:`admin-openrc.sh` file for the admin project::" +msgstr "" + +#: ../common/cli_set_environment_variables_using_openstack_rc.rst:78 +#: ../common/cli_set_environment_variables_using_openstack_rc.rst:79 +msgid "" +"You are not prompted for the password with this method. The password lives " +"in clear text format in the :file:`PROJECT-openrc.sh` file. Restrict the " +"permissions on this file to avoid security problems. You can also remove the " +"``OS_PASSWORD`` variable from the file, and use the ``--password`` parameter " +"with OpenStack client commands instead." +msgstr "" + +#: ../common/cli_set_environment_variables_using_openstack_rc.rst:87 +#: ../common/cli_set_environment_variables_using_openstack_rc.rst:88 +msgid "" +"You must set the ``OS_CACERT`` environment variable when using the https " +"protocol in the ``OS_AUTH_URL`` environment setting because the verification " +"process for the TLS (HTTPS) server certificate uses the one indicated in the " +"environment. This certificate will be used when verifying the TLS (HTTPS) " +"server certificate." +msgstr "" + +#: ../common/cli_set_environment_variables_using_openstack_rc.rst:94 +#: ../common/cli_set_environment_variables_using_openstack_rc.rst:95 +msgid "Override environment variable values" +msgstr "" + +#: ../common/cli_set_environment_variables_using_openstack_rc.rst:96 +msgid "" +"When you run OpenStack client commands, you can override some environment " +"variable settings by using the options that are listed at the end of the " +"``help`` output of the various client commands. For example, you can " +"override the ``OS_PASSWORD`` setting in the :file:`PROJECT-openrc.sh` file " +"by specifying a password on a :command:`keystone` command, as follows::" +msgstr "" + +#: ../common/cli_set_environment_variables_using_openstack_rc.rst:96 +#: ../common/cli_set_environment_variables_using_openstack_rc.rst:97 +msgid "" +"When you run OpenStack client commands, you can override some environment " +"variable settings by using the options that are listed at the end of the " +"``help`` output of the various client commands. For example, you can " +"override the ``OS_PASSWORD`` setting in the :file:`PROJECT-openrc.sh` file " +"by specifying a password on a :command:`openstack` command, as follows::" +msgstr "" + +#: ../common/cli_set_environment_variables_using_openstack_rc.rst:105 +#: ../common/cli_set_environment_variables_using_openstack_rc.rst:106 +msgid "Where ``PASSWORD`` is your password." msgstr "" #: ../common/cli_set_environment_variables_using_openstack_rc.rst:107 @@ -1797,164 +2462,333 @@ msgid "" "methods." msgstr "" -#: ../common/glossary.rst:943 +#: ../common/cli_set_environment_variables_using_openstack_rc.rst:113 +#: ../common/cli_set_environment_variables_using_openstack_rc.rst:114 msgid "" -"A user-created Python module that is loaded by horizon to change the look " -"and feel of the dashboard." +"For example, when you specify your password using the command-line client " +"with the ``--os-password`` argument, anyone with access to your computer can " +"view it in plain text with the ``ps`` field." msgstr "" -#: ../common/glossary.rst:2721 ../common/glossary.rst:2728 -#: ../common/glossary.rst:2734 ../common/glossary.rst:2736 -#: ../common/glossary.rst:2725 +#: ../common/cli_set_environment_variables_using_openstack_rc.rst:117 +#: ../common/cli_set_environment_variables_using_openstack_rc.rst:118 msgid "" -"A virtual network port within Networking; VIFs / vNICs are connected to a " -"port." +"To avoid storing the password in plain text, you can prompt for the " +"OpenStack password interactively." msgstr "" -#: ../common/glossary.rst:2368 ../common/glossary.rst:2375 -#: ../common/glossary.rst:2374 ../common/glossary.rst:2380 -#: ../common/glossary.rst:2369 +#: ../common/conventions.rst:3 +msgid "Conventions" +msgstr "" + +#: ../common/conventions.rst:5 +msgid "The OpenStack documentation uses several typesetting conventions." +msgstr "" + +#: ../common/conventions.rst:8 +msgid "Notices" +msgstr "" + +#: ../common/conventions.rst:10 +msgid "Notices take these forms:" +msgstr "" + +#: ../common/conventions.rst:12 +msgid "A handy tip or reminder." +msgstr "" + +#: ../common/conventions.rst:14 +msgid "Something you must be aware of before proceeding." +msgstr "" + +#: ../common/conventions.rst:16 +msgid "Critical information about the risk of data loss or security issues." +msgstr "" + +#: ../common/conventions.rst:20 +msgid "Command prompts" +msgstr "" + +#: ../common/conventions.rst:26 msgid "" -"A virtual network that provides connectivity between entities. For example, " -"a collection of virtual ports that share network connectivity. In Networking " -"terminology, a network is always a layer-2 network." +"Any user, including the ``root`` user, can run commands that are prefixed " +"with the ``$`` prompt." msgstr "" -#: ../common/cli_manage_volumes.rst:7 +#: ../common/conventions.rst:33 msgid "" -"A volume is a detachable block storage device, similar to a USB hard drive. " -"You can attach a volume to only one instance. To create and manage volumes, " -"you use a combination of ``nova`` and ``cinder`` client commands." +"The ``root`` user must run commands that are prefixed with the ``#`` prompt. " +"You can also prefix these commands with the :command:`sudo` command, if " +"available, to run them." msgstr "" -#: ../common/glossary.rst:1151 -msgid "A web framework used extensively in horizon." +#: ../common/dashboard_customizing.rst:8 +msgid "Customize the dashboard" msgstr "" -#: ../common/get_started_compute.rst:40 ../common/get_started_compute.rst:39 +#: ../common/dashboard_customizing.rst:10 msgid "" -"A worker daemon that creates and terminates virtual machine instances " -"through hypervisor APIs. For example:" +"Once you have the dashboard installed you can customize the way it looks and " +"feels to suit your own needs." msgstr "" -#: ../common/glossary.rst:292 +#: ../common/dashboard_customizing.rst:14 msgid "" -"A worker process that verifies the integrity of Object Storage objects, " -"containers, and accounts. Auditors is the collective term for the Object " -"Storage account auditor, container auditor, and object auditor." +"The OpenStack dashboard by default on Ubuntu installs the ``openstack-" +"dashboard-ubuntu-theme`` package." msgstr "" -#: ../common/glossary.rst:858 +#: ../common/dashboard_customizing.rst:17 msgid "" -"A wrapper used by the Image service that contains a VM image and its " -"associated metadata, such as machine state, OS disk size, and so on." +"If you do not want to use this theme you can remove it and its dependencies " +"using the following command::" msgstr "" -#: ../common/glossary.rst:79 -msgid "ACL" -msgstr "" - -#: ../common/glossary.rst:178 -msgid "API" -msgstr "" - -#: ../common/glossary.rst:182 -msgid "API endpoint" -msgstr "" - -#: ../common/glossary.rst:189 -msgid "API extension" -msgstr "" - -#: ../common/glossary.rst:193 -msgid "API extension plug-in" -msgstr "" - -#: ../common/glossary.rst:198 -msgid "API key" -msgstr "" - -#: ../common/glossary.rst:202 -msgid "API server" -msgstr "" - -#: ../common/glossary.rst:207 -msgid "API token" -msgstr "" - -#: ../common/glossary.rst:2431 ../common/glossary.rst:2438 -#: ../common/glossary.rst:2437 ../common/glossary.rst:2443 -#: ../common/glossary.rst:2445 ../common/glossary.rst:2434 +#: ../common/dashboard_customizing.rst:23 msgid "" -"API used to access OpenStack Networking. Provides an extensible architecture " -"to enable custom plug-in creation." +"This guide focuses on the :file:`local_settings.py` file, stored in :file:`/" +"openstack-dashboard/openstack_dashboard/local/`." msgstr "" -#: ../common/glossary.rst:2544 ../common/glossary.rst:2551 -#: ../common/glossary.rst:2550 ../common/glossary.rst:2556 -#: ../common/glossary.rst:2558 ../common/glossary.rst:2547 -msgid "API used to access OpenStack Object Storage." -msgstr "" - -#: ../common/glossary.rst:212 -msgid "API version" -msgstr "" - -#: ../common/glossary.rst:269 -msgid "ATA over Ethernet (AoE)" -msgstr "" - -#: ../common/glossary.rst:355 -msgid "AWS" -msgstr "" - -#: ../common/glossary.rst:362 +#: ../common/dashboard_customizing.rst:26 msgid "" -"AWS CloudFormation allows AWS users to create and manage a collection of " -"related resources. The Orchestration module supports a CloudFormation-" -"compatible format (CFN)." +"This guide is adapted from `How To Custom Brand The OpenStack \"Horizon\" " +"Dashboard `__." msgstr "" -#: ../common/glossary.rst:359 -msgid "AWS CloudFormation template" +#: ../common/dashboard_customizing.rst:30 +msgid "Logo and site colors" msgstr "" -#: ../common/glossary.rst:3086 ../common/glossary.rst:3093 -#: ../common/glossary.rst:3100 ../common/glossary.rst:3102 -#: ../common/glossary.rst:3091 +#: ../common/dashboard_customizing.rst:31 msgid "" -"Absolute limit on the amount of network traffic a Compute VM instance can " -"send and receive." +"Create two PNG logo files with transparent backgrounds using the following " +"sizes:" msgstr "" -#: ../common/cli_manage_volumes.rst:355 -msgid "Accept a volume transfer request" +#: ../common/dashboard_customizing.rst:34 +msgid "Login screen: 365 x 50" msgstr "" -#: ../common/cli_manage_volumes.rst:360 -msgid "Accept the request::" +#: ../common/dashboard_customizing.rst:35 +msgid "Logged in banner: 216 x 35" +msgstr "" + +#: ../common/dashboard_customizing.rst:37 +msgid "" +"Upload your new images to :file:`/usr/share/openstack-dashboard/" +"openstack_dashboard/static/dashboard/img/`." +msgstr "" + +#: ../common/dashboard_customizing.rst:40 +msgid "" +"Create a CSS style sheet in :file:`/usr/share/openstack-dashboard/" +"openstack_dashboard/static/dashboard/css/`." +msgstr "" + +#: ../common/dashboard_customizing.rst:40 +msgid "" +"Create a CSS style sheet in :file:`/usr/share/openstack-dashboard/" +"openstack_dashboard/static/dashboard/scss/`." +msgstr "" + +#: ../common/dashboard_customizing.rst:43 +msgid "" +"Change the colors and image file names as appropriate, though the relative " +"directory paths should be the same. The following example file shows you how " +"to customize your CSS file::" +msgstr "" + +#: ../common/dashboard_customizing.rst:81 +msgid "Open the following HTML template in an editor of your choice::" +msgstr "" + +#: ../common/dashboard_customizing.rst:85 +msgid "" +"Add a line to include your newly created style sheet. For example :file:" +"`custom.css`::" +msgstr "" + +#: ../common/dashboard_customizing.rst:92 +msgid "Restart Apache:" +msgstr "" + +#: ../common/dashboard_customizing.rst:94 +msgid "On Ubuntu::" +msgstr "" + +#: ../common/dashboard_customizing.rst:98 +msgid "On Fedora, RHEL, CentOS::" +msgstr "" + +#: ../common/dashboard_customizing.rst:102 +msgid "On openSUSE::" +msgstr "" + +#: ../common/dashboard_customizing.rst:106 +msgid "" +"To view your changes reload your dashboard. If necessary go back and modify " +"your CSS file as appropriate." +msgstr "" + +#: ../common/dashboard_customizing.rst:110 +msgid "HTML title" +msgstr "" + +#: ../common/dashboard_customizing.rst:111 +msgid "" +"Set the HTML title, which appears at the top of the browser window, by " +"adding the following line to :file:`local_settings.py`::" +msgstr "" + +#: ../common/dashboard_customizing.rst:116 +#: ../common/dashboard_customizing.rst:126 +#: ../common/dashboard_customizing.rst:136 +msgid "Restart Apache for this change to take effect." +msgstr "" + +#: ../common/dashboard_customizing.rst:119 +msgid "Logo link" +msgstr "" + +#: ../common/dashboard_customizing.rst:120 +msgid "" +"The logo also acts as a hyperlink. The default behavior is to redirect to " +"``horizon:user_home``. To change this, add the following attribute to :file:" +"`local_settings.py`::" +msgstr "" + +#: ../common/dashboard_customizing.rst:129 +msgid "Help URL" +msgstr "" + +#: ../common/dashboard_customizing.rst:130 +msgid "" +"By default the help URL points to http://docs.openstack.org. Change this by " +"editing the following attribute to the URL of your choice in :file:" +"`local_settings.py`::" +msgstr "" + +#: ../common/get_started_block_storage.rst:3 +#: ../common/get_started_block_storage.rst:4 +msgid "OpenStack Block Storage" +msgstr "" + +#: ../common/get_started_block_storage.rst:5 +#: ../common/get_started_block_storage.rst:6 +msgid "" +"The OpenStack Block Storage service (cinder) adds persistent storage to a " +"virtual machine. Block Storage provides an infrastructure for managing " +"volumes, and interacts with OpenStack Compute to provide volumes for " +"instances. The service also enables management of volume snapshots, and " +"volume types." +msgstr "" + +#: ../common/get_started_block_storage.rst:11 +#: ../common/get_started_block_storage.rst:12 +msgid "The Block Storage service consists of the following components:" msgstr "" -#: ../common/get_started_block_storage.rst:15 #: ../common/get_started_block_storage.rst:14 +#: ../common/get_started_block_storage.rst:15 msgid "Accepts API requests, and routes them to the cinder-volume for action." msgstr "" -#: ../common/get_started_image_service.rst:22 -#: ../common/get_started_image_service.rst:19 -msgid "Accepts Image API calls for image discovery, retrieval, and storage." +#: ../common/get_started_block_storage.rst:15 +#: ../common/get_started_block_storage.rst:16 +msgid "cinder-api" msgstr "" -#: ../common/get_started_object_storage.rst:13 -#: ../common/get_started_object_storage.rst:12 +#: ../common/get_started_block_storage.rst:18 +#: ../common/get_started_block_storage.rst:19 msgid "" -"Accepts OpenStack Object Storage API and raw HTTP requests to upload files, " -"modify metadata, and create containers. It also serves file or container " -"listings to web browsers. To improve performance, the proxy server can use " -"an optional cache that is usually deployed with memcache." +"Interacts directly with the Block Storage service, and processes such as the " +"cinder-scheduler. It also interacts with these processes through a message " +"queue. The cinder-volume service responds to read and write requests sent to " +"the Block Storage service to maintain state. It can interact with a variety " +"of storage providers through a driver architecture." msgstr "" -#: ../common/get_started_compute.rst:21 ../common/get_started_compute.rst:20 +#: ../common/get_started_block_storage.rst:23 +#: ../common/get_started_block_storage.rst:24 +msgid "cinder-volume" +msgstr "" + +#: ../common/get_started_block_storage.rst:26 +#: ../common/get_started_block_storage.rst:27 +msgid "" +"Selects the optimal storage provider node on which to create the volume. A " +"similar component to the nova-scheduler." +msgstr "" + +#: ../common/get_started_block_storage.rst:27 +#: ../common/get_started_block_storage.rst:28 +msgid "cinder-scheduler daemon" +msgstr "" + +#: ../common/get_started_block_storage.rst:30 +#: ../common/get_started_block_storage.rst:31 +msgid "" +"The cinder-backup service provides backing up volumes of any type to a " +"backup storage provider. Like the cinder-volume service, it can interact " +"with a variety of storage providers through a driver architecture." +msgstr "" + +#: ../common/get_started_block_storage.rst:33 +#: ../common/get_started_block_storage.rst:34 +msgid "cinder-backup daemon" +msgstr "" + +#: ../common/get_started_block_storage.rst:35 +#: ../common/get_started_block_storage.rst:36 +#: ../common/get_started_block_storage.rst:37 +#: ../common/get_started_openstack_networking.rst:30 +#: ../common/get_started_openstack_networking.rst:31 +msgid "Messaging queue" +msgstr "" + +#: ../common/get_started_block_storage.rst:36 +#: ../common/get_started_block_storage.rst:37 +msgid "Routes information between the Block Storage processes." +msgstr "" + +#: ../common/get_started_compute.rst:3 ../common/get_started_compute.rst:4 +msgid "OpenStack Compute" +msgstr "" + +#: ../common/get_started_compute.rst:5 ../common/get_started_compute.rst:6 +msgid "" +"Use OpenStack Compute to host and manage cloud computing systems. OpenStack " +"Compute is a major part of an Infrastructure-as-a-Service (IaaS) system. The " +"main modules are implemented in Python." +msgstr "" + +#: ../common/get_started_compute.rst:9 ../common/get_started_compute.rst:10 +msgid "" +"OpenStack Compute interacts with OpenStack Identity for authentication, " +"OpenStack Image service for disk and server images, and OpenStack dashboard " +"for the user and administrative interface. Image access is limited by " +"projects, and by users; quotas are limited per project (the number of " +"instances, for example). OpenStack Compute can scale horizontally on " +"standard hardware, and download images to launch instances." +msgstr "" + +#: ../common/get_started_compute.rst:10 +msgid "" +"OpenStack Compute interacts with OpenStack Identity for authentication, " +"OpenStack Image Service for disk and server images, and OpenStack dashboard " +"for the user and administrative interface. Image access is limited by " +"projects, and by users; quotas are limited per project (the number of " +"instances, for example). OpenStack Compute can scale horizontally on " +"standard hardware, and download images to launch instances." +msgstr "" + +#: ../common/get_started_compute.rst:17 ../common/get_started_compute.rst:18 +msgid "OpenStack Compute consists of the following areas and their components:" +msgstr "" + +#: ../common/get_started_compute.rst:20 ../common/get_started_compute.rst:21 msgid "" "Accepts and responds to end user compute API calls. The service supports the " "OpenStack Compute API, the Amazon EC2 API, and a special Admin API for " @@ -1963,11 +2797,8 @@ msgid "" "instance." msgstr "" -#: ../common/get_started_openstack_networking.rst:14 -#: ../common/get_started_openstack_networking.rst:13 -msgid "" -"Accepts and routes API requests to the appropriate OpenStack Networking plug-" -"in for action." +#: ../common/get_started_compute.rst:24 ../common/get_started_compute.rst:25 +msgid "``nova-api`` service" msgstr "" #: ../common/get_started_compute.rst:27 @@ -1979,7 +2810,7 @@ msgid "" "OpenStack Cloud Administrator Guide." msgstr "" -#: ../common/get_started_compute.rst:28 ../common/get_started_compute.rst:27 +#: ../common/get_started_compute.rst:27 ../common/get_started_compute.rst:28 msgid "" "Accepts metadata requests from instances. The nova-api-metadata service is " "generally used when you run in multi-host mode with nova-network " @@ -1988,664 +2819,158 @@ msgid "" "Cloud Administrator Guide." msgstr "" -#: ../common/get_started_storage_concepts.rst:21 -#: ../common/get_started_storage_concepts.rst:22 -#: ../common/get_started_storage_concepts.rst:20 -msgid "Access associated with a VM" +#: ../common/get_started_compute.rst:31 ../common/get_started_compute.rst:32 +msgid "``nova-api-metadata`` service" msgstr "" -#: ../common/get_started_database_service.rst:38 -#: ../common/get_started_database_service.rst:37 +#: ../common/get_started_compute.rst:39 ../common/get_started_compute.rst:40 msgid "" -"Access the Database service instance using typical database access commands. " -"For example, with MySQL::" +"A worker daemon that creates and terminates virtual machine instances " +"through hypervisor APIs. For example:" msgstr "" -#: ../common/log_in_dashboard.rst:150 ../common/log_in_dashboard.rst:153 -msgid "Access the following categories to complete these tasks:" +#: ../common/get_started_compute.rst:42 ../common/get_started_compute.rst:43 +msgid "XenAPI for XenServer/XCP" msgstr "" -#: ../common/get_started_object_storage.rst:20 -#: ../common/get_started_object_storage.rst:19 -msgid "Account servers (swift-account-server)" +#: ../common/get_started_compute.rst:44 ../common/get_started_compute.rst:45 +msgid "libvirt for KVM or QEMU" msgstr "" -#: ../common/glossary.rst:89 -msgid "Active Directory" +#: ../common/get_started_compute.rst:46 ../common/get_started_compute.rst:47 +msgid "VMwareAPI for VMware" msgstr "" -#: ../common/glossary.rst:3404 ../common/glossary.rst:3411 -#: ../common/glossary.rst:3418 ../common/glossary.rst:3426 -#: ../common/glossary.rst:3415 +#: ../common/get_started_compute.rst:48 ../common/get_started_compute.rst:49 msgid "" -"Acts as the gatekeeper to Object Storage and is responsible for " -"authenticating the user." +"Processing is fairly complex. Basically, the daemon accepts actions from the " +"queue and performs a series of system commands such as launching a KVM " +"instance and updating its state in the database." msgstr "" -#: ../common/dashboard_customizing.rst:85 +#: ../common/get_started_compute.rst:50 ../common/get_started_compute.rst:51 +msgid "``nova-compute`` service" +msgstr "" + +#: ../common/get_started_compute.rst:53 ../common/get_started_compute.rst:54 msgid "" -"Add a line to include your newly created style sheet. For example :file:" -"`custom.css`::" +"Takes a virtual machine instance request from the queue and determines on " +"which compute server host it runs." msgstr "" -#: ../common/glossary.rst:246 -msgid "Address Resolution Protocol (ARP)" +#: ../common/get_started_compute.rst:54 ../common/get_started_compute.rst:55 +msgid "``nova-scheduler`` service" msgstr "" -#: ../common/log_in_dashboard.rst:136 ../common/log_in_dashboard.rst:139 -#: ../common/log_in_dashboard.rst:135 +#: ../common/get_started_compute.rst:57 ../common/get_started_compute.rst:58 msgid "" -"Administrative users can use the :guilabel:`Admin` tab to view usage and to " -"manage instances, volumes, flavors, images, projects, users, services, and " -"quotas." +"Mediates interactions between the nova-compute service and the database. It " +"eliminates direct accesses to the cloud database made by the nova-compute " +"service. The nova-conductor module scales horizontally. However, do not " +"deploy it on nodes where the nova-compute service runs. For more " +"information, see `A new Nova service: nova-conductor `__." msgstr "" -#: ../common/log_in_dashboard.rst:135 ../common/log_in_dashboard.rst:137 +#: ../common/get_started_compute.rst:63 ../common/get_started_compute.rst:64 +msgid "``nova-conductor`` module" +msgstr "" + +#: ../common/get_started_compute.rst:66 ../common/get_started_compute.rst:67 msgid "" -"Administrative users can use the :guilabel:`Admin` tab to view usage and to " -"manage instances, volumes, flavors, images, services, and quotas." +"A server daemon that serves the Nova Cert service for X509 certificates. " +"Used to generate certificates for ``euca-bundle-image``. Only needed for the " +"EC2 API." msgstr "" -#: ../common/get_started_storage_concepts.rst:27 -#: ../common/get_started_storage_concepts.rst:30 -#: ../common/get_started_storage_concepts.rst:29 -msgid "Administrator configures size setting, based on flavors" +#: ../common/get_started_compute.rst:68 ../common/get_started_compute.rst:69 +msgid "``nova-cert`` module" msgstr "" -#: ../common/glossary.rst:118 -msgid "Advanced Message Queuing Protocol (AMQP)" -msgstr "" - -#: ../common/glossary.rst:124 -msgid "Advanced RISC Machine (ARM)" -msgstr "" - -#: ../common/cli_manage_volumes.rst:342 +#: ../common/get_started_compute.rst:71 ../common/get_started_compute.rst:72 msgid "" -"After the volume recipient, or new owner, accepts the transfer, you can see " -"that the transfer is no longer available::" +"Similar to the nova-compute service, accepts networking tasks from the queue " +"and manipulates the network. Performs tasks such as setting up bridging " +"interfaces or changing IPtables rules." msgstr "" -#: ../common/cli_manage_images.rst:105 +#: ../common/get_started_compute.rst:73 ../common/get_started_compute.rst:74 +msgid "``nova-network worker`` daemon" +msgstr "" + +#: ../common/get_started_compute.rst:76 msgid "" -"After you restart the Image service, you can use the following syntax to " -"view the image's location information::" +"Authorizes tokens for users that console proxies provide. See nova-" +"novncproxy and nova-xvpvncproxy. This service must be running for console " +"proxies to work. You can run proxies of either type against a single nova-" +"consoleauth service in a cluster configuration. For information, see `About " +"nova-consoleauth `__." msgstr "" -#: ../common/cli_manage_images.rst:15 -msgid "After you upload an image, you cannot change it." -msgstr "" - -#: ../common/glossary.rst:171 +#: ../common/get_started_compute.rst:76 ../common/get_started_compute.rst:77 msgid "" -"All OpenStack core projects are provided under the terms of the Apache " -"License 2.0 license." +"Authorizes tokens for users that console proxies provide. See nova-" +"novncproxy and nova-xvpvncproxy. This service must be running for console " +"proxies to work. You can run proxies of either type against a single nova-" +"consoleauth service in a cluster configuration. For information, see `About " +"nova-consoleauth `__." msgstr "" -#: ../common/glossary.rst:2552 ../common/glossary.rst:2559 -#: ../common/glossary.rst:2558 ../common/glossary.rst:2564 -#: ../common/glossary.rst:2566 ../common/glossary.rst:2555 +#: ../common/get_started_compute.rst:81 ../common/get_started_compute.rst:82 +msgid "``nova-consoleauth`` daemon" +msgstr "" + +#: ../common/get_started_compute.rst:84 ../common/get_started_compute.rst:85 msgid "" -"Allows a user to set a flag on an Object Storage container so that all " -"objects within the container are versioned." +"Provides a proxy for accessing running instances through a VNC connection. " +"Supports browser-based novnc clients." msgstr "" -#: ../common/glossary.rst:3051 ../common/glossary.rst:3058 -#: ../common/glossary.rst:3065 ../common/glossary.rst:3067 -#: ../common/glossary.rst:3056 -msgid "Alphanumeric ID assigned to each Identity service role." +#: ../common/get_started_compute.rst:85 ../common/get_started_compute.rst:86 +msgid "``nova-novncproxy`` daemon" msgstr "" -#: ../common/support-compute.rst:138 +#: ../common/get_started_compute.rst:88 ../common/get_started_compute.rst:89 msgid "" -"Also check :file:`nova-compute.log` for exceptions. Sometimes they do not " -"appear in the console output." +"Provides a proxy for accessing running instances through a SPICE connection. " +"Supports browser-based HTML5 client." msgstr "" -#: ../common/support-compute.rst:110 +#: ../common/get_started_compute.rst:89 ../common/get_started_compute.rst:90 +msgid "``nova-spicehtml5proxy`` daemon" +msgstr "" + +#: ../common/get_started_compute.rst:92 ../common/get_started_compute.rst:93 msgid "" -"Also, check your HTTP proxy settings to see whether they cause problems " -"with :file:`novarc` creation." +"Provides a proxy for accessing running instances through a VNC connection. " +"Supports an OpenStack-specific Java client." msgstr "" -#: ../common/glossary.rst:3704 ../common/glossary.rst:3711 -#: ../common/glossary.rst:3718 ../common/glossary.rst:3726 -#: ../common/glossary.rst:3715 -msgid "Alternative name for the Block Storage API." +#: ../common/get_started_compute.rst:93 ../common/get_started_compute.rst:94 +msgid "``nova-xvpvncproxy`` daemon" msgstr "" -#: ../common/glossary.rst:1853 ../common/glossary.rst:1859 -msgid "Alternative name for the glance image API." +#: ../common/get_started_compute.rst:96 ../common/get_started_compute.rst:97 +msgid "``nova-cert`` daemon" msgstr "" -#: ../common/glossary.rst:196 -msgid "Alternative term for a Networking plug-in or Networking API extension." +#: ../common/get_started_compute.rst:96 ../common/get_started_compute.rst:97 +msgid "x509 certificates." msgstr "" -#: ../common/glossary.rst:1381 ../common/glossary.rst:1382 -msgid "Alternative term for a RabbitMQ message exchange." -msgstr "" - -#: ../common/glossary.rst:3162 ../common/glossary.rst:3169 -#: ../common/glossary.rst:3176 ../common/glossary.rst:3184 -#: ../common/glossary.rst:3173 -msgid "Alternative term for a VM image." -msgstr "" - -#: ../common/glossary.rst:1500 ../common/glossary.rst:1501 -msgid "Alternative term for a VM instance type." -msgstr "" - -#: ../common/glossary.rst:3640 ../common/glossary.rst:3647 -#: ../common/glossary.rst:3654 ../common/glossary.rst:3662 -#: ../common/glossary.rst:3651 -msgid "Alternative term for a VM or guest." -msgstr "" - -#: ../common/glossary.rst:885 -msgid "Alternative term for a cloud controller node." -msgstr "" - -#: ../common/glossary.rst:2766 ../common/glossary.rst:2773 -#: ../common/glossary.rst:2780 ../common/glossary.rst:2782 -#: ../common/glossary.rst:2771 -msgid "Alternative term for a cloudpipe." -msgstr "" - -#: ../common/glossary.rst:3319 ../common/glossary.rst:3326 -#: ../common/glossary.rst:3333 ../common/glossary.rst:3341 -#: ../common/glossary.rst:3330 -msgid "Alternative term for a fixed IP address." -msgstr "" - -#: ../common/glossary.rst:1917 ../common/glossary.rst:1923 -msgid "Alternative term for a flavor ID." -msgstr "" - -#: ../common/glossary.rst:3507 ../common/glossary.rst:3514 -#: ../common/glossary.rst:3521 ../common/glossary.rst:3529 -#: ../common/glossary.rst:3518 -msgid "Alternative term for a non-durable exchange." -msgstr "" - -#: ../common/glossary.rst:3516 ../common/glossary.rst:3523 -#: ../common/glossary.rst:3530 ../common/glossary.rst:3538 -#: ../common/glossary.rst:3527 -msgid "Alternative term for a non-durable queue." -msgstr "" - -#: ../common/glossary.rst:3374 ../common/glossary.rst:3381 -#: ../common/glossary.rst:3388 ../common/glossary.rst:3396 -#: ../common/glossary.rst:3385 -msgid "Alternative term for a paused VM instance." -msgstr "" - -#: ../common/glossary.rst:3649 ../common/glossary.rst:3656 -#: ../common/glossary.rst:3663 ../common/glossary.rst:3671 -#: ../common/glossary.rst:3660 -msgid "Alternative term for a virtual network." -msgstr "" - -#: ../common/glossary.rst:3713 ../common/glossary.rst:3720 -#: ../common/glossary.rst:3727 ../common/glossary.rst:3735 -#: ../common/glossary.rst:3724 -msgid "Alternative term for a volume plug-in." -msgstr "" - -#: ../common/glossary.rst:1401 ../common/glossary.rst:1402 +#: ../common/get_started_compute.rst:98 ../common/get_started_compute.rst:99 msgid "" -"Alternative term for an API extension or plug-in. In the context of Identity " -"service, this is a call that is specific to the implementation, such as " -"adding support for OpenID." +"In Debian, a unique nova-consoleproxy package provides the nova-novncproxy, " +"nova-spicehtml5proxy, and nova-xvpvncproxy packages. To select packages, " +"edit the :file:`/etc/default/nova-consoleproxy` file or use the debconf " +"interface. You can also manually edit the :file:`/etc/default/nova-" +"consoleproxy` file, and stop and start the console daemons." msgstr "" -#: ../common/glossary.rst:201 -msgid "Alternative term for an API token." -msgstr "" - -#: ../common/glossary.rst:39 -msgid "Alternative term for an Amazon EC2 access key. See EC2 access key." -msgstr "" - -#: ../common/glossary.rst:1294 ../common/glossary.rst:1295 -msgid "Alternative term for an Identity service catalog." -msgstr "" - -#: ../common/glossary.rst:3534 ../common/glossary.rst:3541 -#: ../common/glossary.rst:3548 ../common/glossary.rst:3556 -#: ../common/glossary.rst:3545 -msgid "Alternative term for an Identity service default token." -msgstr "" - -#: ../common/glossary.rst:305 -msgid "Alternative term for an Object Storage authorization node." -msgstr "" - -#: ../common/glossary.rst:2192 ../common/glossary.rst:2198 -#: ../common/glossary.rst:2187 -msgid "Alternative term for an admin API." -msgstr "" - -#: ../common/glossary.rst:2479 ../common/glossary.rst:2486 -#: ../common/glossary.rst:2485 ../common/glossary.rst:2491 -#: ../common/glossary.rst:2493 ../common/glossary.rst:2482 -msgid "Alternative term for an ephemeral volume." -msgstr "" - -#: ../common/glossary.rst:3676 ../common/glossary.rst:3683 -#: ../common/glossary.rst:3690 ../common/glossary.rst:3698 -#: ../common/glossary.rst:3687 -msgid "Alternative term for an image." -msgstr "" - -#: ../common/glossary.rst:1898 ../common/glossary.rst:1904 -msgid "Alternative term for instance UUID." -msgstr "" - -#: ../common/glossary.rst:3503 ../common/glossary.rst:3510 -#: ../common/glossary.rst:3517 ../common/glossary.rst:3525 -#: ../common/glossary.rst:3514 -msgid "Alternative term for non-durable." -msgstr "" - -#: ../common/glossary.rst:939 -msgid "Alternative term for tenant." -msgstr "" - -#: ../common/glossary.rst:2493 ../common/glossary.rst:2500 -#: ../common/glossary.rst:2499 ../common/glossary.rst:2505 -#: ../common/glossary.rst:2507 ../common/glossary.rst:2496 -msgid "Alternative term for the Compute API." -msgstr "" - -#: ../common/glossary.rst:1776 ../common/glossary.rst:1782 -msgid "Alternative term for the Identity service API." -msgstr "" - -#: ../common/glossary.rst:3176 ../common/glossary.rst:3183 -#: ../common/glossary.rst:3190 ../common/glossary.rst:3198 -#: ../common/glossary.rst:3187 -msgid "Alternative term for the Identity service catalog." -msgstr "" - -#: ../common/glossary.rst:1564 ../common/glossary.rst:1565 -msgid "Alternative term for the Image service image registry." -msgstr "" - -#: ../common/glossary.rst:2962 ../common/glossary.rst:2969 -#: ../common/glossary.rst:2976 ../common/glossary.rst:2978 -#: ../common/glossary.rst:2967 -msgid "Alternative term for the Image service registry." -msgstr "" - -#: ../common/cli_set_environment_variables_using_openstack_rc.rst:54 -#: ../common/cli_set_environment_variables_using_openstack_rc.rst:55 -msgid "" -"Alternatively, you can create the :file:`PROJECT-openrc.sh` file from " -"scratch, if you cannot download the file from the dashboard." -msgstr "" - -#: ../common/glossary.rst:142 -msgid "Amazon Kernel Image (AKI)" -msgstr "" - -#: ../common/glossary.rst:147 -msgid "Amazon Machine Image (AMI)" -msgstr "" - -#: ../common/glossary.rst:152 -msgid "Amazon Ramdisk Image (ARI)" -msgstr "" - -#: ../common/glossary.rst:358 -msgid "Amazon Web Services." -msgstr "" - -#: ../common/glossary.rst:2799 ../common/glossary.rst:2806 -#: ../common/glossary.rst:2813 ../common/glossary.rst:2815 -#: ../common/glossary.rst:2804 -msgid "" -"An API endpoint used for both service-to-service communication and end-user " -"interactions." -msgstr "" - -#: ../common/glossary.rst:472 -msgid "" -"An API on a separate endpoint for attaching, detaching, and creating block " -"storage for compute VMs." -msgstr "" - -#: ../common/get_started_telemetry.rst:50 -#: ../common/get_started_telemetry.rst:49 -msgid "An API server (``ceilometer-api``)" -msgstr "" - -#: ../common/glossary.rst:3458 ../common/glossary.rst:3465 -#: ../common/glossary.rst:3472 ../common/glossary.rst:3480 -#: ../common/glossary.rst:3469 -msgid "An API that is accessible to tenants." -msgstr "" - -#: ../common/get_started_orchestration.rst:30 -#: ../common/get_started_orchestration.rst:29 -msgid "" -"An AWS Query API that is compatible with AWS CloudFormation. It processes " -"API requests by sending them to the heat-engine over RPC." -msgstr "" - -#: ../common/glossary.rst:1245 ../common/glossary.rst:1246 -msgid "" -"An Amazon EBS storage volume that contains a bootable VM image, currently " -"unsupported in OpenStack." -msgstr "" - -#: ../common/glossary.rst:352 -msgid "" -"An Amazon EC2 concept of an isolated area that is used for fault tolerance. " -"Do not confuse with an OpenStack Compute zone or cell." -msgstr "" - -#: ../common/glossary.rst:1509 ../common/glossary.rst:1510 -msgid "" -"An IP address that a project can associate with a VM so that the instance " -"has the same public IP address each time that it boots. You create a pool of " -"floating IP addresses and assign them to instances as they are launched to " -"maintain a consistent IP address for maintaining DNS assignment." -msgstr "" - -#: ../common/glossary.rst:3222 ../common/glossary.rst:3229 -#: ../common/glossary.rst:3236 ../common/glossary.rst:3244 -#: ../common/glossary.rst:3233 -msgid "" -"An IP address that can be assigned to a VM instance within the shared IP " -"group. Public IP addresses can be shared across multiple servers for use in " -"various high-availability scenarios. When an IP address is shared to another " -"server, the cloud network restrictions are modified to enable each server to " -"listen to and respond on that IP address. You can optionally specify that " -"the target server network configuration be modified. Shared IP addresses can " -"be used with many standard heartbeat facilities, such as keepalive, that " -"monitor for failure and manage IP failover." -msgstr "" - -#: ../common/glossary.rst:2809 ../common/glossary.rst:2816 -#: ../common/glossary.rst:2823 ../common/glossary.rst:2825 -#: ../common/glossary.rst:2814 -msgid "An IP address that is accessible to end-users." -msgstr "" - -#: ../common/glossary.rst:1468 ../common/glossary.rst:1469 -msgid "" -"An IP address that is associated with the same instance each time that " -"instance boots, is generally not accessible to end users or the public " -"Internet, and is used for management of the instance." -msgstr "" - -#: ../common/glossary.rst:2740 ../common/glossary.rst:2747 -#: ../common/glossary.rst:2753 ../common/glossary.rst:2755 -#: ../common/glossary.rst:2744 -msgid "" -"An IP address used for management and administration, not available to the " -"public Internet." -msgstr "" - -#: ../common/glossary.rst:1538 ../common/glossary.rst:1539 -msgid "" -"An IP address, typically assigned to a router, that passes network traffic " -"between different networks." -msgstr "" - -#: ../common/glossary.rst:1179 -msgid "" -"An Identity API v3 entity. Represents a collection of projects, groups and " -"users that defines administrative boundaries for managing OpenStack Identity " -"entities. On the Internet, separates a website from other sites. Often, the " -"domain name has two or more parts that are separated by dots. For example, " -"yahoo.com, usa.gov, harvard.edu, or mail.yahoo.com. Also, a domain is an " -"entity or container of all DNS-related information containing one or more " -"records." -msgstr "" - -#: ../common/glossary.rst:3117 ../common/glossary.rst:3124 -#: ../common/glossary.rst:3131 ../common/glossary.rst:3133 -#: ../common/glossary.rst:3122 -msgid "" -"An Identity service API access token that is associated with a specific " -"tenant." -msgstr "" - -#: ../common/glossary.rst:3462 ../common/glossary.rst:3469 -#: ../common/glossary.rst:3476 ../common/glossary.rst:3484 -#: ../common/glossary.rst:3473 -msgid "" -"An Identity service API endpoint that is associated with one or more tenants." -msgstr "" - -#: ../common/glossary.rst:3477 ../common/glossary.rst:3484 -#: ../common/glossary.rst:3491 ../common/glossary.rst:3499 -#: ../common/glossary.rst:3488 -msgid "" -"An Identity service component that manages and validates tokens after a user " -"or tenant has been authenticated." -msgstr "" - -#: ../common/glossary.rst:3191 ../common/glossary.rst:3198 -#: ../common/glossary.rst:3205 ../common/glossary.rst:3213 -#: ../common/glossary.rst:3202 -msgid "" -"An Identity service feature that enables services, such as Compute, to " -"automatically register with the catalog." -msgstr "" - -#: ../common/glossary.rst:601 -msgid "" -"An Identity service that lists API endpoints that are available to a user " -"after authentication with the Identity service." -msgstr "" - -#: ../common/glossary.rst:1024 -msgid "" -"An Identity service token that is not associated with a specific tenant and " -"is exchanged for a scoped token." -msgstr "" - -#: ../common/glossary.rst:1615 -msgid "" -"An Identity v3 API entity. Represents a collection of users that is owned by " -"a specific domain." -msgstr "" - -#: ../common/glossary.rst:2804 ../common/glossary.rst:2811 -#: ../common/glossary.rst:2818 ../common/glossary.rst:2820 -#: ../common/glossary.rst:2809 -msgid "An Image service VM image that is available to all tenants." -msgstr "" - -#: ../common/glossary.rst:2735 ../common/glossary.rst:2742 -#: ../common/glossary.rst:2748 ../common/glossary.rst:2750 -#: ../common/glossary.rst:2739 -msgid "An Image service VM image that is only available to specified tenants." -msgstr "" - -#: ../common/glossary.rst:399 -msgid "" -"An Image service container format that indicates that no container exists " -"for the VM image." -msgstr "" - -#: ../common/glossary.rst:2966 ../common/glossary.rst:2973 -#: ../common/glossary.rst:2980 ../common/glossary.rst:2982 -#: ../common/glossary.rst:2971 -msgid "" -"An Image service that provides VM image metadata information to clients." -msgstr "" - -#: ../common/glossary.rst:3595 ../common/glossary.rst:3602 -#: ../common/glossary.rst:3609 ../common/glossary.rst:3617 -#: ../common/glossary.rst:3606 -msgid "" -"An Internet Protocol (IP) address configured on the load balancer for use by " -"clients connecting to a service that is load balanced. Incoming connections " -"are distributed to back-end nodes based on the configuration of the load " -"balancer." -msgstr "" - -#: ../common/glossary.rst:3608 ../common/glossary.rst:3615 -#: ../common/glossary.rst:3622 ../common/glossary.rst:3630 -#: ../common/glossary.rst:3619 -msgid "An L2 network segment within Networking." -msgstr "" - -#: ../common/glossary.rst:2929 ../common/glossary.rst:2936 -#: ../common/glossary.rst:2943 ../common/glossary.rst:2945 -#: ../common/glossary.rst:2934 -msgid "An Object Storage component that collects meters." -msgstr "" - -#: ../common/glossary.rst:2528 ../common/glossary.rst:2535 -#: ../common/glossary.rst:2534 ../common/glossary.rst:2540 -#: ../common/glossary.rst:2542 ../common/glossary.rst:2531 -msgid "" -"An Object Storage component that copies an object to remote partitions for " -"fault tolerance." -msgstr "" - -#: ../common/glossary.rst:980 -msgid "" -"An Object Storage component that copies changes in the account, container, " -"and object databases to other nodes." -msgstr "" - -#: ../common/glossary.rst:2533 ../common/glossary.rst:2540 -#: ../common/glossary.rst:2539 ../common/glossary.rst:2545 -#: ../common/glossary.rst:2547 ../common/glossary.rst:2536 -msgid "An Object Storage component that is responsible for managing objects." -msgstr "" - -#: ../common/glossary.rst:71 -msgid "" -"An Object Storage component that provides account services such as list, " -"create, modify, and audit. Do not confuse with OpenStack Identity service, " -"OpenLDAP, or similar user-account services." -msgstr "" - -#: ../common/glossary.rst:3143 ../common/glossary.rst:3150 -#: ../common/glossary.rst:3157 ../common/glossary.rst:3159 -#: ../common/glossary.rst:3148 -msgid "" -"An Object Storage large object that has been broken up into pieces. The re-" -"assembled object is called a concatenated object." -msgstr "" - -#: ../common/glossary.rst:3448 ../common/glossary.rst:3455 -#: ../common/glossary.rst:3462 ../common/glossary.rst:3470 -#: ../common/glossary.rst:3459 -msgid "" -"An Object Storage middleware component that enables creation of URLs for " -"temporary object access." -msgstr "" - -#: ../common/glossary.rst:332 -msgid "An Object Storage node that provides authorization services." -msgstr "" - -#: ../common/glossary.rst:3333 ../common/glossary.rst:3340 -#: ../common/glossary.rst:3347 ../common/glossary.rst:3355 -#: ../common/glossary.rst:3344 -msgid "" -"An Object Storage node that provides container services, account services, " -"and object services; controls the account databases, container databases, " -"and object storage." -msgstr "" - -#: ../common/glossary.rst:864 -msgid "An Object Storage server that manages containers." -msgstr "" - -#: ../common/glossary.rst:61 -msgid "" -"An Object Storage worker that scans for and deletes account databases and " -"that the account server has marked for deletion." -msgstr "" - -#: ../common/glossary.rst:1847 ../common/glossary.rst:1853 -msgid "" -"An OpenStack core project that provides discovery, registration, and " -"delivery services for disk and server images. The project name of the Image " -"service is glance." -msgstr "" - -#: ../common/glossary.rst:3389 ../common/glossary.rst:3396 -#: ../common/glossary.rst:3403 ../common/glossary.rst:3411 -#: ../common/glossary.rst:3400 -msgid "An OpenStack core project that provides object storage services." -msgstr "" - -#: ../common/glossary.rst:552 -msgid "" -"An OpenStack grouped release of projects that came out in the spring of " -"2011. It included Compute (nova), Object Storage (swift), and the Image " -"service (glance). Cactus is a city in Texas, US and is the code name for the " -"third release of OpenStack. When OpenStack releases went from three to six " -"months long, the code name of the release changed to match a geography " -"nearest the previous summit." -msgstr "" - -#: ../common/get_started_identity.rst:59 ../common/get_started_identity.rst:58 -msgid "" -"An OpenStack service, such as Compute (nova), Object Storage (swift), or " -"Image service (glance). It provides one or more endpoints in which users can " -"access resources and perform operations." -msgstr "" - -#: ../common/glossary.rst:3170 ../common/glossary.rst:3177 -#: ../common/glossary.rst:3184 ../common/glossary.rst:3192 -#: ../common/glossary.rst:3181 -msgid "" -"An OpenStack service, such as Compute, Object Storage, or Image service. " -"Provides one or more endpoints through which users can access resources and " -"perform operations." -msgstr "" - -#: ../common/get_started_orchestration.rst:26 -#: ../common/get_started_orchestration.rst:25 -msgid "" -"An OpenStack-native REST API that processes API requests by sending them to " -"the heat-engine over Remote Procedure Call (RPC)." -msgstr "" - -#: ../common/glossary.rst:409 -msgid "An OpenStack-provided image." -msgstr "" - -#: ../common/glossary.rst:1338 ../common/glossary.rst:1342 -#: ../common/glossary.rst:2149 ../common/glossary.rst:3556 -#: ../common/glossary.rst:3653 ../common/glossary.rst:3742 -#: ../common/glossary.rst:3788 ../common/glossary.rst:3797 -#: ../common/glossary.rst:3563 ../common/glossary.rst:3660 -#: ../common/glossary.rst:3749 ../common/glossary.rst:3795 -#: ../common/glossary.rst:3804 ../common/glossary.rst:1339 -#: ../common/glossary.rst:1343 ../common/glossary.rst:2155 -#: ../common/glossary.rst:3570 ../common/glossary.rst:3667 -#: ../common/glossary.rst:3756 ../common/glossary.rst:3802 -#: ../common/glossary.rst:3811 ../common/glossary.rst:3578 -#: ../common/glossary.rst:3675 ../common/glossary.rst:3764 -#: ../common/glossary.rst:3810 ../common/glossary.rst:3819 -#: ../common/glossary.rst:3567 ../common/glossary.rst:3664 -#: ../common/glossary.rst:3753 ../common/glossary.rst:3799 -#: ../common/glossary.rst:3808 -msgid "An OpenStack-supported hypervisor." -msgstr "" - -#: ../common/glossary.rst:2056 ../common/glossary.rst:2062 -msgid "" -"An OpenStack-supported hypervisor. KVM is a full virtualization solution for " -"Linux on x86 hardware containing virtualization extensions (Intel VT or AMD-" -"V), ARM, IBM Power, and IBM zSeries. It consists of a loadable kernel " -"module, that provides the core virtualization infrastructure and a processor " -"specific module." -msgstr "" - -#: ../common/get_started_compute.rst:107 ../common/get_started_compute.rst:106 +#: ../common/get_started_compute.rst:106 ../common/get_started_compute.rst:107 msgid "" "An S3 interface for registering images with the OpenStack Image service. " "Used primarily for installations that must support euca2ools. The euca2ools " @@ -2653,338 +2978,635 @@ msgid "" "translates S3 requests into Image service requests." msgstr "" -#: ../common/glossary.rst:2784 ../common/glossary.rst:2791 -#: ../common/glossary.rst:2798 ../common/glossary.rst:2800 -#: ../common/glossary.rst:2789 -msgid "An administrator who has access to all hosts and instances." +#: ../common/get_started_compute.rst:110 ../common/get_started_compute.rst:111 +msgid "nova-objectstore daemon" msgstr "" -#: ../common/glossary.rst:3201 ../common/glossary.rst:3208 -#: ../common/glossary.rst:3215 ../common/glossary.rst:3223 -#: ../common/glossary.rst:3212 +#: ../common/get_started_compute.rst:113 ../common/get_started_compute.rst:114 msgid "" -"An administrator-defined token used by Compute to communicate securely with " -"the Identity service." +"A set of command-line interpreter commands for managing cloud resources. " +"Although it is not an OpenStack module, you can configure nova-api to " +"support this EC2 interface. For more information, see the `Eucalyptus 3.4 " +"Documentation `__." msgstr "" -#: ../common/get_started_telemetry.rst:42 -#: ../common/get_started_telemetry.rst:41 -msgid "An alarm evaluator (``ceilometer-alarm-evaluator``)" +#: ../common/get_started_compute.rst:117 ../common/get_started_compute.rst:118 +msgid "euca2ools client" msgstr "" -#: ../common/get_started_telemetry.rst:46 -#: ../common/get_started_telemetry.rst:45 -msgid "An alarm notifier (``ceilometer-alarm-notifier``)" +#: ../common/get_started_compute.rst:120 ../common/get_started_compute.rst:121 +msgid "Enables users to submit commands as a tenant administrator or end user." msgstr "" -#: ../common/glossary.rst:3472 ../common/glossary.rst:3479 -#: ../common/glossary.rst:3486 ../common/glossary.rst:3494 -#: ../common/glossary.rst:3483 +#: ../common/get_started_compute.rst:121 ../common/get_started_compute.rst:122 +msgid "nova client" +msgstr "" + +#: ../common/get_started_compute.rst:124 ../common/get_started_compute.rst:125 msgid "" -"An alpha-numeric string of text used to access OpenStack APIs and resources." +"A central hub for passing messages between daemons. Usually implemented with " +"`RabbitMQ `__, but can be implemented with an AMQP " +"message queue, such as `Apache Qpid `__ or `Zero MQ " +"`__." msgstr "" -#: ../common/get_started_identity.rst:44 ../common/get_started_identity.rst:43 +#: ../common/get_started_compute.rst:128 ../common/get_started_compute.rst:129 +msgid "The queue" +msgstr "" + +#: ../common/get_started_compute.rst:131 ../common/get_started_compute.rst:132 +msgid "" +"Stores most build-time and run-time states for a cloud infrastructure, " +"including:" +msgstr "" + +#: ../common/get_started_compute.rst:134 ../common/get_started_compute.rst:135 +msgid "Available instance types" +msgstr "" + +#: ../common/get_started_compute.rst:136 ../common/get_started_compute.rst:137 +msgid "Instances in use" +msgstr "" + +#: ../common/get_started_compute.rst:138 ../common/get_started_compute.rst:139 +msgid "Available networks" +msgstr "" + +#: ../common/get_started_compute.rst:140 ../common/get_started_compute.rst:141 +msgid "Projects" +msgstr "" + +#: ../common/get_started_compute.rst:142 ../common/get_started_compute.rst:143 +msgid "" +"Theoretically, OpenStack Compute can support any database that SQL-Alchemy " +"supports. Common databases are SQLite3 for test and development work, MySQL, " +"and PostgreSQL." +msgstr "" + +#: ../common/get_started_compute.rst:143 ../common/get_started_compute.rst:144 +#: ../common/get_started_compute.rst:145 +msgid "SQL database" +msgstr "" + +#: ../common/get_started_conceptual_architecture.rst:4 +#: ../common/get_started_conceptual_architecture.rst:5 +msgid "Conceptual architecture" +msgstr "" + +#: ../common/get_started_conceptual_architecture.rst:6 +#: ../common/get_started_conceptual_architecture.rst:7 +msgid "" +"The following diagram shows the relationships among the OpenStack services:" +msgstr "" + +#: ../common/get_started_dashboard.rst:4 ../common/get_started_dashboard.rst:5 +msgid "OpenStack dashboard" +msgstr "" + +#: ../common/get_started_dashboard.rst:6 ../common/get_started_dashboard.rst:7 +msgid "" +"The OpenStack dashboard is a modular `Django web application `__ that provides a graphical interface to OpenStack " +"services." +msgstr "" + +#: ../common/get_started_dashboard.rst:12 +#: ../common/get_started_dashboard.rst:13 +msgid "" +"The dashboard is usually deployed through `mod_wsgi `__ in Apache. You can modify the dashboard code to make it " +"suitable for different sites." +msgstr "" + +#: ../common/get_started_dashboard.rst:16 +#: ../common/get_started_dashboard.rst:17 +msgid "" +"From a network architecture point of view, this service must be accessible " +"to customers and the public API for each OpenStack service. To use the " +"administrator functionality for other services, it must also connect to " +"Admin API endpoints, which should not be accessible by customers." +msgstr "" + +#: ../common/get_started_database_service.rst:3 +#: ../common/get_started_database_service.rst:4 +msgid "OpenStack Database service" +msgstr "" + +#: ../common/get_started_database_service.rst:4 +msgid "Database service overview" +msgstr "" + +#: ../common/get_started_database_service.rst:5 +#: ../common/get_started_database_service.rst:6 +msgid "" +"The Database service provides scalable and reliable cloud provisioning " +"functionality for both relational and non-relational database engines. Users " +"can quickly and easily use database features without the burden of handling " +"complex administrative tasks. Cloud users and database administrators can " +"provision and manage multiple database instances as needed." +msgstr "" + +#: ../common/get_started_database_service.rst:12 +#: ../common/get_started_database_service.rst:13 +msgid "" +"The Database service provides resource isolation at high performance levels, " +"and automates complex administrative tasks such as deployment, " +"configuration, patching, backups, restores, and monitoring." +msgstr "" + +#: ../common/get_started_database_service.rst:16 +#: ../common/get_started_database_service.rst:17 +msgid "**Process flow example**" +msgstr "" + +#: ../common/get_started_database_service.rst:18 +#: ../common/get_started_database_service.rst:19 +msgid "This example is a high-level process flow for using Database services:" +msgstr "" + +#: ../common/get_started_database_service.rst:20 +#: ../common/get_started_database_service.rst:21 +msgid "" +"The OpenStack Administrator configures the basic infrastructure using the " +"following steps:" +msgstr "" + +#: ../common/get_started_database_service.rst:23 +#: ../common/get_started_database_service.rst:24 +msgid "Install the Database service." +msgstr "" + +#: ../common/get_started_database_service.rst:24 +#: ../common/get_started_database_service.rst:25 +msgid "" +"Create an image for each type of database. For example, one for MySQL and " +"one for MongoDB." +msgstr "" + +#: ../common/get_started_database_service.rst:26 +#: ../common/get_started_database_service.rst:27 +msgid "" +"Use the ``trove-manage`` command to import images and offer them to tenants." +msgstr "" + +#: ../common/get_started_database_service.rst:29 +#: ../common/get_started_database_service.rst:30 +msgid "" +"The OpenStack end user deploys the Database service using the following " +"steps:" +msgstr "" + +#: ../common/get_started_database_service.rst:32 +#: ../common/get_started_database_service.rst:33 +msgid "" +"Create a Database service instance using the :command:`trove create` command." +msgstr "" + +#: ../common/get_started_database_service.rst:34 +#: ../common/get_started_database_service.rst:35 +msgid "" +"Use the :command:`trove list` command to get the ID of the instance, " +"followed by the :command:`trove show` command to get the IP address of it." +msgstr "" + +#: ../common/get_started_database_service.rst:37 +#: ../common/get_started_database_service.rst:38 +msgid "" +"Access the Database service instance using typical database access commands. " +"For example, with MySQL::" +msgstr "" + +#: ../common/get_started_database_service.rst:42 +#: ../common/get_started_database_service.rst:43 +msgid "The Database service includes the following components:" +msgstr "" + +#: ../common/get_started_database_service.rst:45 +#: ../common/get_started_database_service.rst:46 +msgid "A CLI that communicates with the ``trove-api`` component." +msgstr "" + +#: ../common/get_started_database_service.rst:45 +#: ../common/get_started_database_service.rst:46 +msgid "``python-troveclient`` command-line client" +msgstr "" + +#: ../common/get_started_database_service.rst:48 +#: ../common/get_started_database_service.rst:49 +msgid "" +"Provides an OpenStack-native RESTful API that supports JSON to provision and " +"manage Trove instances." +msgstr "" + +#: ../common/get_started_database_service.rst:49 +#: ../common/get_started_database_service.rst:50 +msgid "``trove-api`` component" +msgstr "" + +#: ../common/get_started_database_service.rst:52 +#: ../common/get_started_database_service.rst:53 +msgid "" +"Runs on the host, and receives messages from guest instances that want to " +"update information on the host." +msgstr "" + +#: ../common/get_started_database_service.rst:53 +#: ../common/get_started_database_service.rst:54 +msgid "``trove-conductor`` service" +msgstr "" + +#: ../common/get_started_database_service.rst:56 +#: ../common/get_started_database_service.rst:57 +msgid "" +"Instruments the complex system flows that support provisioning instances, " +"managing the lifecycle of instances, and performing operations on instances." +msgstr "" + +#: ../common/get_started_database_service.rst:58 +#: ../common/get_started_database_service.rst:59 +msgid "``trove-taskmanager`` service" +msgstr "" + +#: ../common/get_started_database_service.rst:61 +#: ../common/get_started_database_service.rst:62 +msgid "" +"Runs within the guest instance. Manages and performs operations on the " +"database itself." +msgstr "" + +#: ../common/get_started_database_service.rst:61 +#: ../common/get_started_database_service.rst:62 +#: ../common/get_started_database_service.rst:63 +msgid "``trove-guestagent`` service" +msgstr "" + +#: ../common/get_started_feedback.rst:3 +#: ../common/get_started_with_openstack.rst:141 +msgid "Feedback" +msgstr "" + +#: ../common/get_started_identity.rst:3 ../common/get_started_identity.rst:4 +msgid "OpenStack Identity" +msgstr "" + +#: ../common/get_started_identity.rst:4 +msgid "OpenStack Identity concepts" +msgstr "" + +#: ../common/get_started_identity.rst:5 +msgid "" +"The OpenStack :term:`Identity service ` provides a single point of " +"integration for managing authentication, authorization, and service catalog " +"services. Other OpenStack services use the Identity service as a common " +"unified API. Additionally, services that provide information about users but " +"that are not included in OpenStack (such as LDAP services) can be integrated " +"into a pre-existing infrastructure." +msgstr "" + +#: ../common/get_started_identity.rst:5 ../common/get_started_identity.rst:6 +msgid "The OpenStack Identity service performs the following functions:" +msgstr "" + +#: ../common/get_started_identity.rst:7 ../common/get_started_identity.rst:8 +msgid "Tracking users and their permissions." +msgstr "" + +#: ../common/get_started_identity.rst:9 ../common/get_started_identity.rst:10 +msgid "Providing a catalog of available services with their API endpoints." +msgstr "" + +#: ../common/get_started_identity.rst:11 ../common/get_started_identity.rst:12 +#: ../common/get_started_identity.rst:38 +msgid "" +"When installing OpenStack Identity service, you must register each service " +"in your OpenStack installation. Identity service can then track which " +"OpenStack services are installed, and where they are located on the network." +msgstr "" + +#: ../common/get_started_identity.rst:12 +msgid "" +"In order to benefit from the Identity service, other OpenStack services need " +"to collaborate with it. When an OpenStack service receives a request from a " +"user, it checks with the Identity service whether the user is authorized to " +"make the request." +msgstr "" + +#: ../common/get_started_identity.rst:16 ../common/get_started_identity.rst:17 +msgid "" +"To understand OpenStack Identity, you must understand the following concepts:" +msgstr "" + +#: ../common/get_started_identity.rst:17 +msgid "The Identity service contains these components:" +msgstr "" + +#: ../common/get_started_identity.rst:20 +msgid "" +"A centralized server provides authentication and authorization services " +"using a RESTful interface." +msgstr "" + +#: ../common/get_started_identity.rst:20 ../common/get_started_identity.rst:21 +msgid "" +"Digital representation of a person, system, or service who uses OpenStack " +"cloud services. The Identity service validates that incoming requests are " +"made by the user who claims to be making the call. Users have a login and " +"may be assigned tokens to access resources. Users can be directly assigned " +"to a particular tenant and behave as if they are contained in that tenant." +msgstr "" + +#: ../common/get_started_identity.rst:21 +msgid "Server" +msgstr "" + +#: ../common/get_started_identity.rst:24 +msgid "" +"Drivers or a service back end are integrated to the centralized server, and " +"are used for accessing identity information in repositories, external to " +"OpenStack, and maybe already existing in the infrastructure where OpenStack " +"is deployed (for example, SQL databases or LDAP servers)." +msgstr "" + +#: ../common/get_started_identity.rst:24 +msgid "" +"Drivers or a service back end are integrated to the centralized server. They " +"are used for accessing identity information in repositories external to " +"OpenStack, and may already exist in the infrastructure where OpenStack is " +"deployed (for example, SQL databases or LDAP servers)." +msgstr "" + +#: ../common/get_started_identity.rst:25 ../common/get_started_identity.rst:26 +msgid "User" +msgstr "" + +#: ../common/get_started_identity.rst:28 ../common/get_started_identity.rst:29 +msgid "" +"Data that confirms the user's identity. For example: user name and password, " +"user name and API key, or an authentication token provided by the Identity " +"service." +msgstr "" + +#: ../common/get_started_identity.rst:28 +msgid "Drivers" +msgstr "" + +#: ../common/get_started_identity.rst:29 +msgid "" +"Data that confirms the user's identity. For example: user name and password, " +"user name and API key, or an authentication token provided by the Identity " +"Service." +msgstr "" + +#: ../common/get_started_identity.rst:30 ../common/get_started_identity.rst:31 +msgid "Credentials" +msgstr "" + +#: ../common/get_started_identity.rst:31 +msgid "" +"Middleware modules run in the address space of the OpenStack component that " +"is using the Identity service. These modules intercept service requests, " +"extract user credentials, and send them to the centralized server for " +"authorization. The integration between the middleware modules and OpenStack " +"components uses the Python Web Server Gateway Interface." +msgstr "" + +#: ../common/get_started_identity.rst:33 ../common/get_started_identity.rst:34 +msgid "" +"The process of confirming the identity of a user. OpenStack Identity " +"confirms an incoming request by validating a set of credentials supplied by " +"the user." +msgstr "" + +#: ../common/get_started_identity.rst:36 +msgid "Modules" +msgstr "" + +#: ../common/get_started_identity.rst:37 ../common/get_started_identity.rst:38 +msgid "" +"These credentials are initially a user name and password, or a user name and " +"API key. When user credentials are validated, OpenStack Identity issues an " +"authentication token which the user provides in subsequent requests." +msgstr "" + +#: ../common/get_started_identity.rst:40 ../common/get_started_identity.rst:41 +msgid "Authentication" +msgstr "" + +#: ../common/get_started_identity.rst:43 ../common/get_started_identity.rst:44 msgid "" "An alpha-numeric string of text used to access OpenStack APIs and resources. " "A token may be revoked at any time and is valid for a finite duration." msgstr "" -#: ../common/glossary.rst:2441 ../common/glossary.rst:2448 -#: ../common/glossary.rst:2447 ../common/glossary.rst:2453 -#: ../common/glossary.rst:2455 ../common/glossary.rst:2444 -msgid "An alternative name for Networking API." +#: ../common/get_started_identity.rst:43 ../common/get_started_identity.rst:84 +#: ../common/get_started_identity.rst:85 +msgid "The following diagram shows the OpenStack Identity process flow:" msgstr "" -#: ../common/glossary.rst:2716 ../common/glossary.rst:2723 -#: ../common/glossary.rst:2729 ../common/glossary.rst:2731 -#: ../common/glossary.rst:2720 +#: ../common/get_started_identity.rst:47 ../common/get_started_identity.rst:48 msgid "" -"An application that runs on the back-end server in a load-balancing system." +"While OpenStack Identity supports token-based authentication in this " +"release, the intention is to support additional protocols in the future. Its " +"main purpose is to be an integration service, and not aspire to be a full-" +"fledged identity store and management solution." msgstr "" -#: ../common/glossary.rst:3383 ../common/glossary.rst:3390 -#: ../common/glossary.rst:3397 ../common/glossary.rst:3405 -#: ../common/glossary.rst:3394 +#: ../common/get_started_identity.rst:50 ../common/get_started_identity.rst:51 +msgid "Token" +msgstr "" + +#: ../common/get_started_identity.rst:53 ../common/get_started_identity.rst:54 msgid "" -"An authentication and authorization service for Object Storage, implemented " -"through WSGI middleware; uses Object Storage itself as the persistent " -"backing store." +"A container used to group or isolate resources. Tenants also group or " +"isolate identity objects. Depending on the service operator, a tenant may " +"map to a customer, account, organization, or project." msgstr "" -#: ../common/glossary.rst:3437 ../common/glossary.rst:3444 -#: ../common/glossary.rst:3451 ../common/glossary.rst:3459 -#: ../common/glossary.rst:3448 +#: ../common/get_started_identity.rst:55 ../common/get_started_identity.rst:56 +msgid "Tenant" +msgstr "" + +#: ../common/get_started_identity.rst:58 ../common/get_started_identity.rst:59 msgid "" -"An authentication facility within Object Storage that enables Object Storage " -"itself to perform authentication and authorization. Frequently used in " -"testing and development." +"An OpenStack service, such as Compute (nova), Object Storage (swift), or " +"Image service (glance). It provides one or more endpoints in which users can " +"access resources and perform operations." msgstr "" -#: ../common/glossary.rst:1418 ../common/glossary.rst:1419 +#: ../common/get_started_identity.rst:64 ../common/get_started_identity.rst:65 msgid "" -"An easy method to create a local LDAP directory for testing Identity and " -"Compute. Requires Redis." +"A network-accessible address where you access a service, usually a URL " +"address. If you are using an extension for templates, an endpoint template " +"can be created, which represents the templates of all the consumable " +"services that are available across the regions." msgstr "" -#: ../common/glossary.rst:1107 +#: ../common/get_started_identity.rst:67 ../common/get_started_identity.rst:68 +msgid "Endpoint" +msgstr "" + +#: ../common/get_started_identity.rst:70 ../common/get_started_identity.rst:71 msgid "" -"An element of the Compute RabbitMQ that comes to life when a RPC call is " -"executed. It connects to a direct exchange through a unique exclusive queue, " -"sends the message, and terminates." +"A personality with a defined set of user rights and privileges to perform a " +"specific set of operations." msgstr "" -#: ../common/glossary.rst:933 +#: ../common/get_started_identity.rst:73 ../common/get_started_identity.rst:74 msgid "" -"An element of the Compute capacity cache that is calculated based on the " -"number of build, snapshot, migrate, and resize operations currently in " -"progress on a given host." +"In the Identity service, a token that is issued to a user includes the list " +"of roles. Services that are being called by that user determine how they " +"interpret the set of roles a user has and to which operations or resources " +"each role grants access." msgstr "" -#: ../common/glossary.rst:3026 ../common/glossary.rst:3033 -#: ../common/glossary.rst:3040 ../common/glossary.rst:3042 -#: ../common/glossary.rst:3031 +#: ../common/get_started_identity.rst:76 ../common/get_started_identity.rst:77 +msgid "Role" +msgstr "" + +#: ../common/get_started_identity.rst:79 ../common/get_started_identity.rst:80 msgid "" -"An entity that maps Object Storage data to partitions. A separate ring " -"exists for each service, such as account, object, and container." +"A command line interface for the OpenStack Identity API. For example, users " +"can run the ``keystone service-create`` and ``keystone endpoint-create`` " +"commands to register services in their OpenStack installations." msgstr "" -#: ../common/glossary.rst:650 -msgid "An iSCSI authentication method supported by Compute." +#: ../common/get_started_identity.rst:82 ../common/get_started_identity.rst:83 +msgid "Keystone Client" msgstr "" -#: ../common/glossary.rst:723 +#: ../common/get_started_image_service.rst:3 +#: ../common/get_started_image_service.rst:4 +msgid "OpenStack Image service" +msgstr "" + +#: ../common/get_started_image_service.rst:4 +msgid "OpenStack Image Service" +msgstr "" + +#: ../common/get_started_image_service.rst:5 msgid "" -"An in-progress specification for cloud management. Currently unsupported in " -"OpenStack." +"The OpenStack Image service is central to Infrastructure-as-a-Service (IaaS) " +"as shown in :ref:`get_started_conceptual_architecture`. It accepts API " +"requests for disk or server images, and image metadata from end users or " +"OpenStack Compute components. It also supports the storage of disk or server " +"images on various repository types, including OpenStack Object Storage." msgstr "" -#: ../common/glossary.rst:1641 ../common/glossary.rst:1647 +#: ../common/get_started_image_service.rst:6 msgid "" -"An integrated project that aims to orchestrate multiple cloud applications " -"for OpenStack." +"The OpenStack Image Service is central to Infrastructure-as-a-Service (IaaS) " +"as shown in Conceptual architecture. It accepts API requests for disk or " +"server images, and image metadata from end users or OpenStack Compute " +"components. It also supports the storage of disk or server images on various " +"repository types, including OpenStack Object Storage." msgstr "" -#: ../common/glossary.rst:2623 ../common/glossary.rst:2630 -#: ../common/glossary.rst:2636 ../common/glossary.rst:2638 -#: ../common/glossary.rst:2627 +#: ../common/get_started_image_service.rst:6 msgid "" -"An integrated project that orchestrates multiple cloud applications for " -"OpenStack. The project name of Orchestration is heat." +"The OpenStack Image service is central to Infrastructure-as-a-Service (IaaS) " +"as shown in Conceptual architecture. It accepts API requests for disk or " +"server images, and image metadata from end users or OpenStack Compute " +"components. It also supports the storage of disk or server images on various " +"repository types, including OpenStack Object Storage." msgstr "" -#: ../common/glossary.rst:985 +#: ../common/get_started_image_service.rst:11 +#: ../common/get_started_image_service.rst:14 msgid "" -"An integrated project that provide scalable and reliable Cloud Database-as-a-" -"Service functionality for both relational and non-relational database " -"engines. The project name of Database service is trove." +"A number of periodic processes run on the OpenStack Image service to support " +"caching. Replication services ensure consistency and availability through " +"the cluster. Other periodic processes include auditors, updaters, and " +"reapers." msgstr "" -#: ../common/glossary.rst:3431 ../common/glossary.rst:3438 -#: ../common/glossary.rst:3445 ../common/glossary.rst:3453 -#: ../common/glossary.rst:3442 +#: ../common/get_started_image_service.rst:14 msgid "" -"An integrated project that provides metering and measuring facilities for " -"OpenStack. The project name of Telemetry is ceilometer." +"A number of periodic processes run on the OpenStack Image Service to support " +"caching. Replication services ensure consistency and availability through " +"the cluster. Other periodic processes include auditors, updaters, and " +"reapers." msgstr "" -#: ../common/glossary.rst:3624 ../common/glossary.rst:3631 -#: ../common/glossary.rst:3638 ../common/glossary.rst:3646 -#: ../common/glossary.rst:3635 +#: ../common/get_started_image_service.rst:16 +#: ../common/get_started_image_service.rst:19 +msgid "The OpenStack Image service includes the following components:" +msgstr "" + +#: ../common/get_started_image_service.rst:19 +#: ../common/get_started_image_service.rst:22 +msgid "Accepts Image API calls for image discovery, retrieval, and storage." +msgstr "" + +#: ../common/get_started_image_service.rst:19 +msgid "The OpenStack Image Service includes the following components:" +msgstr "" + +#: ../common/get_started_image_service.rst:19 +#: ../common/get_started_image_service.rst:22 +msgid "glance-api" +msgstr "" + +#: ../common/get_started_image_service.rst:22 +#: ../common/get_started_image_service.rst:25 msgid "" -"An interface that is plugged into a port in a Networking network. Typically " -"a virtual network interface belonging to a VM." +"Stores, processes, and retrieves metadata about images. Metadata includes " +"items such as size and type." msgstr "" -#: ../common/glossary.rst:1624 ../common/glossary.rst:1630 +#: ../common/get_started_image_service.rst:27 +#: ../common/get_started_image_service.rst:30 msgid "" -"An object state in Object Storage where a new replica of the object is " -"automatically created due to a drive failure." +"The registry is a private internal service meant for use by OpenStack Image " +"service. Do not disclose it to users." msgstr "" -#: ../common/glossary.rst:2096 ../common/glossary.rst:2102 -msgid "An object within Object Storage that is larger than 5 GB." +#: ../common/get_started_image_service.rst:28 +#: ../common/get_started_image_service.rst:31 +msgid "glance-registry" msgstr "" -#: ../common/glossary.rst:895 +#: ../common/get_started_image_service.rst:30 msgid "" -"An official OpenStack project. Currently consists of Compute (nova), Object " -"Storage (swift), Image service (glance), Identity (keystone), Dashboard " -"(horizon), Networking (neutron), and Block Storage (cinder), the Telemetry " -"module (ceilometer), Orchestration module (heat), Database service (trove), " -"Bare Metal service (ironic), Data processing service (sahara). However, this " -"definition is changing based on community discussions about the \"Big Tent\"." +"The registry is a private internal service meant for use by OpenStack Image " +"Service. Do not disclose it to users." msgstr "" -#: ../common/glossary.rst:2589 ../common/glossary.rst:2596 -#: ../common/glossary.rst:2595 ../common/glossary.rst:2601 -#: ../common/glossary.rst:2603 ../common/glossary.rst:2592 -msgid "An open source LDAP server. Supported by both Compute and Identity." -msgstr "" - -#: ../common/glossary.rst:3298 ../common/glossary.rst:3305 -#: ../common/glossary.rst:3312 ../common/glossary.rst:3320 -#: ../common/glossary.rst:3309 -msgid "An open source SQL toolkit for Python, used in OpenStack." -msgstr "" - -#: ../common/glossary.rst:928 +#: ../common/get_started_image_service.rst:31 +#: ../common/get_started_image_service.rst:34 msgid "" -"An open source community project by Dell that aims to provide all necessary " -"services to quickly deploy clouds." +"Stores image metadata and you can choose your database depending on your " +"preference. Most deployments use MySQL or SQLite." msgstr "" -#: ../common/glossary.rst:665 +#: ../common/get_started_image_service.rst:32 +#: ../common/get_started_image_service.rst:35 +msgid "Database" +msgstr "" + +#: ../common/get_started_image_service.rst:35 +#: ../common/get_started_image_service.rst:38 msgid "" -"An operating system configuration management tool supporting OpenStack " -"deployments." +"Various repository types are supported including normal file systems, Object " +"Storage, RADOS block devices, HTTP, and Amazon S3. Note that some " +"repositories will only support read-only usage." msgstr "" -#: ../common/glossary.rst:2826 ../common/glossary.rst:2833 -#: ../common/glossary.rst:2840 ../common/glossary.rst:2842 -#: ../common/glossary.rst:2831 +#: ../common/get_started_image_service.rst:36 +#: ../common/get_started_image_service.rst:39 +#: ../common/get_started_image_service.rst:40 +msgid "Storage repository for image files" +msgstr "" + +#: ../common/get_started_logical_architecture.rst:3 +#: ../common/get_started_logical_architecture.rst:4 +msgid "Logical architecture" +msgstr "" + +#: ../common/get_started_logical_architecture.rst:5 +#: ../common/get_started_logical_architecture.rst:6 msgid "" -"An operating system configuration-management tool supported by OpenStack." -msgstr "" - -#: ../common/glossary.rst:1614 ../common/glossary.rst:1620 -msgid "An operating system instance running under the control of a hypervisor." -msgstr "" - -#: ../common/glossary.rst:3602 ../common/glossary.rst:3609 -#: ../common/glossary.rst:3616 ../common/glossary.rst:3624 -#: ../common/glossary.rst:3613 -msgid "" -"An operating system instance that runs on top of a hypervisor. Multiple VMs " -"can run at the same time on the same physical host." -msgstr "" - -#: ../common/glossary.rst:1045 -msgid "" -"An option within Compute that enables administrators to create and manage " -"users through the `nova-manage` command as opposed to using the Identity " -"service." -msgstr "" - -#: ../common/glossary.rst:1029 -msgid "" -"An option within Image service so that an image is deleted after a " -"predefined number of seconds instead of immediately." -msgstr "" - -#: ../common/get_started_sahara.rst:22 ../common/get_started_sahara.rst:23 -msgid "Analytics-as-a-Service for ad-hoc or bursty analytic workloads." -msgstr "" - -#: ../common/cli_install_openstack_command_line_clients.rst:73 -msgid "" -"Another option is to use the unofficial binary installer provided by " -"Christoph Gohlke (http://www.lfd.uci.edu/~gohlke/pythonlibs/#pip)." -msgstr "" - -#: ../common/glossary.rst:157 -msgid "Anvil" -msgstr "" - -#: ../common/glossary.rst:1940 ../common/glossary.rst:1946 -msgid "" -"Any business that provides Internet access to individuals or businesses." -msgstr "" - -#: ../common/glossary.rst:505 -msgid "" -"Any client software that enables a computer or device to access the Internet." -msgstr "" - -#: ../common/glossary.rst:2401 ../common/glossary.rst:2408 -#: ../common/glossary.rst:2407 ../common/glossary.rst:2413 -#: ../common/glossary.rst:2414 ../common/glossary.rst:2403 -msgid "Any compute node that runs the network worker daemon." -msgstr "" - -#: ../common/app_support.rst:151 ../common/app_support.rst:148 -#: ../common/app_support.rst:146 -msgid "" -"Any deployment-specific information is helpful, such as whether you are " -"using Ubuntu 14.04 or are performing a multi-node installation." -msgstr "" - -#: ../common/glossary.rst:1722 ../common/glossary.rst:1728 -msgid "" -"Any kind of text that contains a link to some other site, commonly found in " -"documents where clicking on a word or words opens up a different website." -msgstr "" - -#: ../common/glossary.rst:205 -msgid "Any node running a daemon or worker that provides an API endpoint." -msgstr "" - -#: ../common/glossary.rst:1310 ../common/glossary.rst:1311 -msgid "" -"Any piece of hardware or software that wants to connect to the network " -"services provided by Networking, the network connectivity service. An entity " -"can make use of Networking by implementing a VIF." -msgstr "" - -#: ../common/conventions.rst:26 -msgid "" -"Any user, including the ``root`` user, can run commands that are prefixed " -"with the ``$`` prompt." -msgstr "" - -#: ../common/glossary.rst:162 -msgid "Apache" -msgstr "" - -#: ../common/glossary.rst:1619 ../common/glossary.rst:1625 -msgid "" -"Apache Hadoop is an open source software framework that supports data-" -"intensive distributed applications." -msgstr "" - -#: ../common/glossary.rst:168 -msgid "Apache License 2.0" -msgstr "" - -#: ../common/glossary.rst:173 -msgid "Apache Web Server" -msgstr "" - -#: ../common/glossary.rst:221 -msgid "Application Programming Interface (API)" -msgstr "" - -#: ../common/glossary.rst:240 -msgid "Application Service Provider (ASP)" -msgstr "" - -#: ../common/glossary.rst:227 ../common/cli_overview.rst:34 -msgid "Application catalog" -msgstr "" - -#: ../common/glossary.rst:181 -msgid "Application programming interface." -msgstr "" - -#: ../common/cli_manage_images.rst:182 -msgid "" -"Arbitrary property to associate with image. This option can be used multiple " -"times." -msgstr "" - -#: ../common/cli_overview.rst:23 -msgid "" -"As a cloud end user, you can use the OpenStack dashboard to provision your " -"own resources within the limits set by administrators. You can modify the " -"examples provided in this section to create other types and sizes of server " -"instances." -msgstr "" - -#: ../common/cli_manage_volumes.rst:15 -msgid "" -"As an administrator, you can migrate a volume with its data from one " -"location to another in a manner that is transparent to users and workloads. " -"You can migrate only detached volumes with no snapshots." +"To design, deploy, and configure OpenStack, administrators must understand " +"the logical architecture." msgstr "" #: ../common/get_started_logical_architecture.rst:8 @@ -3005,2467 +3627,8 @@ msgid "" "are necessary." msgstr "" -#: ../common/cli_manage_volumes.rst:289 -msgid "" -"As the volume donor, request a volume transfer authorization code for a " -"specific volume::" -msgstr "" - -#: ../common/cli_manage_volumes.rst:357 -msgid "" -"As the volume recipient, you must first obtain the transfer ID and " -"authorization key from the original owner." -msgstr "" - -#: ../common/log_in_dashboard.rst:7 -msgid "" -"Ask the cloud operator for the host name or public IP address from which you " -"can access the dashboard, and for your user name and password." -msgstr "" - -#: ../common/glossary.rst:282 -msgid "" -"Association of an interface ID to a logical port. Plugs an interface into a " -"port." -msgstr "" - -#: ../common/glossary.rst:263 -msgid "Asynchronous JavaScript and XML (AJAX)" -msgstr "" - -#: ../common/cli_manage_volumes.rst:116 -msgid "Attach a volume to an instance" -msgstr "" - -#: ../common/cli_manage_volumes.rst:118 -msgid "" -"Attach your volume to a server, specifying the server ID and the volume ID::" -msgstr "" - -#: ../common/glossary.rst:3630 ../common/glossary.rst:3637 -#: ../common/glossary.rst:3644 ../common/glossary.rst:3652 -#: ../common/glossary.rst:3641 -msgid "" -"Attachment point where a virtual interface connects to a virtual network." -msgstr "" - -#: ../common/glossary.rst:296 -msgid "Austin" -msgstr "" - -#: ../common/glossary.rst:319 -msgid "AuthN" -msgstr "" - -#: ../common/glossary.rst:334 -msgid "AuthZ" -msgstr "" - -#: ../common/get_started_identity.rst:41 ../common/get_started_identity.rst:40 -msgid "Authentication" -msgstr "" - -#: ../common/glossary.rst:92 -msgid "" -"Authentication and identity service by Microsoft, based on LDAP. Supported " -"in OpenStack." -msgstr "" - -#: ../common/glossary.rst:2813 ../common/glossary.rst:2820 -#: ../common/glossary.rst:2827 ../common/glossary.rst:2829 -#: ../common/glossary.rst:2818 -msgid "Authentication method that uses keys rather than passwords." -msgstr "" - -#: ../common/glossary.rst:2333 ../common/glossary.rst:2340 -#: ../common/glossary.rst:2339 ../common/glossary.rst:2345 -#: ../common/glossary.rst:2334 -msgid "" -"Authentication method that uses two or more credentials, such as a password " -"and a private key. Currently not supported in Identity." -msgstr "" - -#: ../common/get_started_compute.rst:76 -msgid "" -"Authorizes tokens for users that console proxies provide. See nova-" -"novncproxy and nova-xvpvncproxy. This service must be running for console " -"proxies to work. You can run proxies of either type against a single nova-" -"consoleauth service in a cluster configuration. For information, see `About " -"nova-consoleauth `__." -msgstr "" - -#: ../common/get_started_compute.rst:77 ../common/get_started_compute.rst:76 -msgid "" -"Authorizes tokens for users that console proxies provide. See nova-" -"novncproxy and nova-xvpvncproxy. This service must be running for console " -"proxies to work. You can run proxies of either type against a single nova-" -"consoleauth service in a cluster configuration. For information, see `About " -"nova-consoleauth `__." -msgstr "" - -#: ../common/glossary.rst:339 -msgid "Auto ACK" -msgstr "" - -#: ../common/glossary.rst:3443 ../common/glossary.rst:3450 -#: ../common/glossary.rst:3457 ../common/glossary.rst:3465 -#: ../common/glossary.rst:3454 -msgid "" -"Automated software test suite designed to run against the trunk of the " -"OpenStack core project." -msgstr "" - -#: ../common/get_started_storage_concepts.rst:23 -#: ../common/get_started_storage_concepts.rst:22 -msgid "Available from anywhere" -msgstr "" - -#: ../common/get_started_compute.rst:135 ../common/get_started_compute.rst:134 -msgid "Available instance types" -msgstr "" - -#: ../common/get_started_compute.rst:139 ../common/get_started_compute.rst:138 -msgid "Available networks" -msgstr "" - -#: ../common/glossary.rst:475 -msgid "BMC" -msgstr "" - -#: ../common/glossary.rst:401 -msgid "Bare metal service" -msgstr "" - -#: ../common/glossary.rst:478 -msgid "" -"Baseboard Management Controller. The intelligence in the IPMI architecture, " -"which is a specialized micro-controller that is embedded on the motherboard " -"of a computer and acts as a server. Manages the interface between system " -"management software and platform hardware." -msgstr "" - -#: ../common/app_support.rst:147 ../common/app_support.rst:144 -#: ../common/app_support.rst:142 -msgid "" -"Be sure to include the software and package versions that you are using, " -"especially if you are using a development branch, such as, ``\"Juno release" -"\" vs git commit bc79c3ecc55929bac585d04a03475b72e06a3208``." -msgstr "" - -#: ../common/cli_install_openstack_command_line_clients.rst:243 -#: ../common/cli_install_openstack_command_line_clients.rst:249 -#: ../common/cli_install_openstack_command_line_clients.rst:256 -#: ../common/cli_install_openstack_command_line_clients.rst:258 -#: ../common/cli_install_openstack_command_line_clients.rst:260 -msgid "" -"Before you can run client commands, you must create and source the :file:" -"`PROJECT-openrc.sh` file to set environment variables. See :doc:`../common/" -"cli_set_environment_variables_using_openstack_rc`." -msgstr "" - -#: ../common/glossary.rst:410 -msgid "Bell-LaPadula model" -msgstr "" - -#: ../common/glossary.rst:2933 ../common/glossary.rst:2940 -#: ../common/glossary.rst:2947 ../common/glossary.rst:2949 -#: ../common/glossary.rst:2938 -msgid "" -"Belongs to a particular domain and is used to specify information about the " -"domain. There are several types of DNS records. Each record type contains " -"particular information used to describe the purpose of that record. Examples " -"include mail exchange (MX) records, which specify the mail server for a " -"particular domain; and name server (NS) records, which specify the " -"authoritative name servers for a domain." -msgstr "" - -#: ../common/glossary.rst:419 -msgid "Benchmark service" -msgstr "" - -#: ../common/glossary.rst:426 -msgid "Bexar" -msgstr "" - -#: ../common/glossary.rst:463 ../common/cli_overview.rst:34 -#: ../common/cli_overview.rst:37 -msgid "Block Storage" -msgstr "" - -#: ../common/glossary.rst:469 -msgid "Block Storage API" -msgstr "" - -#: ../common/get_started_storage_concepts.rst:13 -#: ../common/get_started_storage_concepts.rst:12 -msgid "Block storage (cinder)" -msgstr "" - -#: ../common/glossary.rst:3242 ../common/glossary.rst:3249 -#: ../common/glossary.rst:3256 ../common/glossary.rst:3264 -#: ../common/glossary.rst:3253 -msgid "" -"Block storage that is simultaneously accessible by multiple clients, for " -"example, NFS." -msgstr "" - -#: ../common/glossary.rst:488 -msgid "Bootstrap Protocol (BOOTP)" -msgstr "" - -#: ../common/glossary.rst:495 -msgid "Border Gateway Protocol (BGP)" -msgstr "" - -#: ../common/glossary.rst:967 -msgid "" -"Both Image service and Compute support encrypted virtual machine (VM) images " -"(but not instances). In-transit data encryption is supported in OpenStack " -"using technologies such as HTTPS, SSL, TLS, and SSH. Object Storage does not " -"support object encryption at the application level but may support storage " -"that uses disk encryption." -msgstr "" - -#: ../common/glossary.rst:145 ../common/glossary.rst:150 -#: ../common/glossary.rst:155 -msgid "Both a VM container format and disk format. Supported by Image service." -msgstr "" - -#: ../common/cli_manage_volumes.rst:21 -msgid "" -"Bring down a physical storage device for maintenance without disrupting " -"workloads." -msgstr "" - -#: ../common/glossary.rst:3032 ../common/glossary.rst:3039 -#: ../common/glossary.rst:3046 ../common/glossary.rst:3048 -#: ../common/glossary.rst:3037 -msgid "" -"Builds and manages rings within Object Storage, assigns partitions to " -"devices, and pushes the configuration to other storage nodes." -msgstr "" - -#: ../common/dashboard_customizing.rst:130 -msgid "" -"By default the help URL points to http://docs.openstack.org. Change this by " -"editing the following attribute to the URL of your choice in :file:" -"`local_settings.py`::" -msgstr "" - -#: ../common/glossary.rst:531 -msgid "CA" -msgstr "" - -#: ../common/glossary.rst:560 -msgid "CADF" -msgstr "" - -#: ../common/glossary.rst:566 -msgid "CALL" -msgstr "" - -#: ../common/glossary.rst:588 -msgid "CAST" -msgstr "" - -#: ../common/glossary.rst:752 -msgid "CMDB" -msgstr "" - -#: ../common/glossary.rst:549 -msgid "Cactus" -msgstr "" - -#: ../common/glossary.rst:2318 ../common/glossary.rst:2325 -#: ../common/glossary.rst:2324 ../common/glossary.rst:2330 -#: ../common/glossary.rst:2319 -msgid "" -"Can concurrently use multiple layer-2 networking technologies, such as " -"802.1Q and VXLAN, in Networking." -msgstr "" - -#: ../common/glossary.rst:2770 ../common/glossary.rst:2777 -#: ../common/glossary.rst:2784 ../common/glossary.rst:2786 -#: ../common/glossary.rst:2775 -msgid "" -"Causes the network interface to pass all traffic it receives to the host " -"rather than passing only the frames addressed to it." -msgstr "" - -#: ../common/glossary.rst:628 -msgid "CentOS" -msgstr "" - -#: ../common/glossary.rst:632 -msgid "Ceph" -msgstr "" - -#: ../common/glossary.rst:2872 ../common/glossary.rst:2879 -#: ../common/glossary.rst:2886 ../common/glossary.rst:2888 -#: ../common/glossary.rst:2877 -msgid "" -"Ceph component that enables a Linux block device to be striped over multiple " -"distributed data stores." -msgstr "" - -#: ../common/glossary.rst:638 -msgid "CephFS" -msgstr "" - -#: ../common/glossary.rst:534 -msgid "" -"Certificate Authority or Certification Authority. In cryptography, an entity " -"that issues digital certificates. The digital certificate certifies the " -"ownership of a public key by the named subject of the certificate. This " -"enables others (relying parties) to rely upon signatures or assertions made " -"by the private key that corresponds to the certified public key. In this " -"model of trust relationships, a CA is a trusted third party for both the " -"subject (owner) of the certificate and the party relying upon the " -"certificate. CAs are characteristic of many public key infrastructure (PKI) " -"schemes." -msgstr "" - -#: ../common/glossary.rst:647 -msgid "Challenge-Handshake Authentication Protocol (CHAP)" -msgstr "" - -#: ../common/dashboard_customizing.rst:43 -msgid "" -"Change the colors and image file names as appropriate, though the relative " -"directory paths should be the same. The following example file shows you how " -"to customize your CSS file::" -msgstr "" - -#: ../common/glossary.rst:2681 ../common/glossary.rst:2688 -#: ../common/glossary.rst:2694 ../common/glossary.rst:2696 -#: ../common/glossary.rst:2685 -msgid "Changes to these types of disk volumes are saved." -msgstr "" - -#: ../common/glossary.rst:3122 ../common/glossary.rst:3129 -#: ../common/glossary.rst:3136 ../common/glossary.rst:3138 -#: ../common/glossary.rst:3127 -msgid "" -"Checks for and deletes unused VMs; the component of Image service that " -"implements delayed delete." -msgstr "" - -#: ../common/glossary.rst:50 -msgid "" -"Checks for missing replicas and incorrect or corrupted objects in a " -"specified Object Storage account by running queries against the back-end " -"SQLite database." -msgstr "" - -#: ../common/glossary.rst:846 -msgid "" -"Checks for missing replicas or incorrect objects in specified Object Storage " -"containers through queries to the SQLite back-end database." -msgstr "" - -#: ../common/glossary.rst:662 -msgid "Chef" -msgstr "" - -#: ../common/glossary.rst:1596 ../common/glossary.rst:1597 -msgid "" -"Choosing a host based on the existence of a GPU is currently unsupported in " -"OpenStack." -msgstr "" - -#: ../common/glossary.rst:680 -msgid "CirrOS" -msgstr "" - -#: ../common/glossary.rst:685 -msgid "Cisco neutron plug-in" -msgstr "" - -#: ../common/log_in_dashboard.rst:214 ../common/log_in_dashboard.rst:220 -#: ../common/log_in_dashboard.rst:219 ../common/log_in_dashboard.rst:223 -msgid "" -"Click the 'Settings' button from the user drop down menu in the top right of " -"any page, you will see the :guilabel:`Settings` tab." -msgstr "" - -#: ../common/cli_overview.rst:32 -msgid "Client" -msgstr "" - -#: ../common/glossary.rst:563 -msgid "" -"Cloud Auditing Data Federation (CADF) is a specification for audit event " -"data. CADF is supported by OpenStack Identity." -msgstr "" - -#: ../common/glossary.rst:715 -msgid "Cloud Data Management Interface (CDMI)" -msgstr "" - -#: ../common/glossary.rst:720 -msgid "Cloud Infrastructure Management Interface (CIMI)" -msgstr "" - -#: ../common/glossary.rst:737 -msgid "Cloudbase-Init" -msgstr "" - -#: ../common/glossary.rst:1051 -msgid "Code name for the DNS service project for OpenStack." -msgstr "" - -#: ../common/glossary.rst:2187 ../common/glossary.rst:2193 -#: ../common/glossary.rst:2182 -msgid "" -"Code name for the OpenStack project that provides the Containers Service." -msgstr "" - -#: ../common/glossary.rst:395 -msgid "Code name of the key management service for OpenStack." -msgstr "" - -#: ../common/glossary.rst:705 -msgid "" -"Collection of Compute components that represent the global state of the " -"cloud; talks to services, such as Identity authentication, Object Storage, " -"and node/storage workers through a queue." -msgstr "" - -#: ../common/glossary.rst:3349 ../common/glossary.rst:3356 -#: ../common/glossary.rst:3363 ../common/glossary.rst:3371 -#: ../common/glossary.rst:3360 -msgid "" -"Collective name for the Object Storage object services, container services, " -"and account services." -msgstr "" - -#: ../common/glossary.rst:3399 ../common/glossary.rst:3406 -#: ../common/glossary.rst:3413 ../common/glossary.rst:3421 -#: ../common/glossary.rst:3410 -msgid "" -"Collective term for Object Storage components that provide additional " -"functionality." -msgstr "" - -#: ../common/glossary.rst:3538 ../common/glossary.rst:3545 -#: ../common/glossary.rst:3552 ../common/glossary.rst:3560 -#: ../common/glossary.rst:3549 -msgid "" -"Collective term for a group of Object Storage components that processes " -"queued and failed updates for containers and objects." -msgstr "" - -#: ../common/get_started_telemetry.rst:10 -#: ../common/get_started_telemetry.rst:9 -msgid "" -"Collects event and metering data by monitoring notifications sent from " -"services." -msgstr "" - -#: ../common/glossary.rst:1827 ../common/glossary.rst:1833 -msgid "" -"Combination of a URI and UUID used to access Image service VM images through " -"the image API." -msgstr "" - -#: ../common/conventions.rst:20 -msgid "Command prompts" -msgstr "" - -#: ../common/cli_overview.rst:80 ../common/cli_overview.rst:89 -#: ../common/cli_overview.rst:92 ../common/cli_overview.rst:95 -#: ../common/cli_overview.rst:98 -msgid "Common client" -msgstr "" - -#: ../common/cli_overview.rst:80 ../common/cli_overview.rst:89 -#: ../common/cli_overview.rst:92 ../common/cli_overview.rst:95 -#: ../common/cli_overview.rst:98 -msgid "Common client for the OpenStack project." -msgstr "" - -#: ../common/support-compute.rst:83 -msgid "Common errors and fixes for Compute" -msgstr "" - -#: ../common/support-compute.rst:9 -msgid "" -"Common problems for Compute typically involve misconfigured networking or " -"credentials that are not sourced properly in the environment. Also, most " -"flat networking configurations do not enable :command:`ping` or :command:" -"`ssh` from a compute node to the instances that run on that node. Another " -"common problem is trying to run 32-bit images on a 64-bit compute node. This " -"section shows you how to troubleshoot Compute." -msgstr "" - -#: ../common/app_support.rst:5 -msgid "Community Support" -msgstr "" - -#: ../common/glossary.rst:3314 ../common/glossary.rst:3321 -#: ../common/glossary.rst:3328 ../common/glossary.rst:3336 -#: ../common/glossary.rst:3325 -msgid "" -"Community project that captures Compute AMQP communications; useful for " -"debugging." -msgstr "" - -#: ../common/glossary.rst:1077 -msgid "" -"Community project that uses shell scripts to quickly build complete " -"OpenStack development environments." -msgstr "" - -#: ../common/glossary.rst:3493 ../common/glossary.rst:3500 -#: ../common/glossary.rst:3507 ../common/glossary.rst:3515 -#: ../common/glossary.rst:3504 -msgid "" -"Community project used to run automated tests against the OpenStack API." -msgstr "" - -#: ../common/app_support.rst:3 -msgid "Community support" -msgstr "" - -#: ../common/glossary.rst:243 -msgid "" -"Companies that rent specialized applications that help businesses and " -"organizations provide additional services with lower cost." -msgstr "" - -#: ../common/glossary.rst:2703 ../common/glossary.rst:2710 -#: ../common/glossary.rst:2716 ../common/glossary.rst:2718 -#: ../common/glossary.rst:2707 -msgid "" -"Component of Identity that provides a rule-management interface and a rule-" -"based authorization engine." -msgstr "" - -#: ../common/glossary.rst:780 ../common/cli_overview.rst:37 -#: ../common/cli_overview.rst:40 -msgid "Compute" -msgstr "" - -#: ../common/glossary.rst:785 -msgid "Compute API" -msgstr "" - -#: ../common/glossary.rst:806 -msgid "Compute service" -msgstr "" - -#: ../common/support-compute.rst:21 -msgid "Compute service logging" -msgstr "" - -#: ../common/support-compute.rst:23 -msgid "" -"Compute stores a log file for each service in :file:`/var/log/nova`. For " -"example, :file:`nova-compute.log` is the log for the ``nova-compute`` " -"service. You can set the following options to format log strings for the " -"``nova.log`` module in the :file:`nova.conf` file:" -msgstr "" - -#: ../common/glossary.rst:3154 ../common/glossary.rst:3161 -#: ../common/glossary.rst:3168 ../common/glossary.rst:3176 -#: ../common/glossary.rst:3165 -msgid "" -"Computer that provides explicit services to the client software running on " -"that system, often managing a variety of computer operations. A server is a " -"VM instance in the Compute system. Flavor and image are requisite elements " -"when creating a server." -msgstr "" - -#: ../common/get_started_conceptual_architecture.rst:4 -#: ../common/get_started_conceptual_architecture.rst:5 -msgid "Conceptual architecture" -msgstr "" - -#: ../common/glossary.rst:2899 ../common/glossary.rst:2906 -#: ../common/glossary.rst:2913 ../common/glossary.rst:2915 -#: ../common/glossary.rst:2904 -msgid "" -"Configurable option within Object Storage to limit database writes on a per-" -"account and/or per-container basis." -msgstr "" - -#: ../common/glossary.rst:755 -msgid "Configuration Management Database." -msgstr "" - -#: ../common/glossary.rst:342 -msgid "" -"Configuration setting within RabbitMQ that enables or disables message " -"acknowledgment. Enabled by default." -msgstr "" - -#: ../common/support-compute.rst:74 -msgid "" -"Configuration: Lists all configuration options currently accessible through " -"the CONF object for the current process." -msgstr "" - -#: ../common/cli_overview.rst:52 ../common/cli_overview.rst:58 -#: ../common/cli_overview.rst:61 ../common/cli_overview.rst:65 -#: ../common/cli_overview.rst:68 -msgid "Configure networks for guest servers." -msgstr "" - -#: ../common/glossary.rst:1389 ../common/glossary.rst:1390 -msgid "" -"Connected to by a direct consumer in RabbitMQ—Compute, the message can be " -"consumed only by the current connection." -msgstr "" - -#: ../common/get_started_object_storage.rst:23 -#: ../common/get_started_object_storage.rst:22 -msgid "Container servers (swift-container-server)" -msgstr "" - -#: ../common/glossary.rst:865 ../common/cli_overview.rst:44 -msgid "Containers service" -msgstr "" - -#: ../common/glossary.rst:510 -msgid "" -"Contains configuration information that Object Storage uses to reconfigure a " -"ring or to re-create it from scratch after a serious failure." -msgstr "" - -#: ../common/glossary.rst:3106 ../common/glossary.rst:3113 -#: ../common/glossary.rst:3120 ../common/glossary.rst:3122 -#: ../common/glossary.rst:3111 -msgid "" -"Contains information about a user as provided by the identity provider. It " -"is an indication that a user has been authenticated." -msgstr "" - -#: ../common/glossary.rst:2651 ../common/glossary.rst:2658 -#: ../common/glossary.rst:2664 ../common/glossary.rst:2666 -#: ../common/glossary.rst:2655 -msgid "" -"Contains the locations of all Object Storage partitions within the ring." -msgstr "" - -#: ../common/glossary.rst:836 -msgid "Contains the output from a Linux VM console in Compute." -msgstr "" - -#: ../common/conventions.rst:3 -msgid "Conventions" -msgstr "" - -#: ../common/glossary.rst:3013 ../common/glossary.rst:3020 -#: ../common/glossary.rst:3027 ../common/glossary.rst:3029 -#: ../common/glossary.rst:3018 -msgid "" -"Converts an existing server to a different flavor, which scales the server " -"up or down. The original server is saved to enable rollback if a problem " -"occurs. All resizes must be tested and explicitly confirmed, at which time " -"the original server is removed." -msgstr "" - -#: ../common/cli_set_environment_variables_using_openstack_rc.rst:34 -#: ../common/cli_set_environment_variables_using_openstack_rc.rst:35 -msgid "" -"Copy the :file:`PROJECT-openrc.sh` file to the computer from which you want " -"to run OpenStack commands." -msgstr "" - -#: ../common/dashboard_customizing.rst:40 -msgid "" -"Create a CSS style sheet in :file:`/usr/share/openstack-dashboard/" -"openstack_dashboard/static/dashboard/css/`." -msgstr "" - -#: ../common/dashboard_customizing.rst:40 -msgid "" -"Create a CSS style sheet in :file:`/usr/share/openstack-dashboard/" -"openstack_dashboard/static/dashboard/scss/`." -msgstr "" - -#: ../common/get_started_database_service.rst:33 -#: ../common/get_started_database_service.rst:32 -msgid "" -"Create a Database service instance using the :command:`trove create` command." -msgstr "" - -#: ../common/cli_manage_volumes.rst:266 -msgid "" -"Create a custom bootable volume or a volume with a large data set and " -"transfer it to a customer." -msgstr "" - -#: ../common/cli_manage_volumes.rst:43 -msgid "Create a volume" -msgstr "" - -#: ../common/cli_manage_volumes.rst:274 -msgid "Create a volume transfer request" -msgstr "" - -#: ../common/cli_manage_volumes.rst:73 -msgid "" -"Create a volume with 8 gibibytes (GiB) of space, and specify the " -"availability zone and image::" -msgstr "" - -#: ../common/get_started_database_service.rst:25 -#: ../common/get_started_database_service.rst:24 -msgid "" -"Create an image for each type of database. For example, one for MySQL and " -"one for MongoDB." -msgstr "" - -#: ../common/cli_overview.rst:72 ../common/cli_overview.rst:81 -#: ../common/cli_overview.rst:84 ../common/cli_overview.rst:88 -#: ../common/cli_overview.rst:91 -msgid "Create and collect measurements across OpenStack." -msgstr "" - -#: ../common/cli_overview.rst:76 ../common/cli_overview.rst:85 -#: ../common/cli_overview.rst:88 ../common/cli_overview.rst:50 -msgid "Create and manage Hadoop clusters on OpenStack." -msgstr "" - -#: ../common/cli_overview.rst:34 -msgid "Create and manage applications." -msgstr "" - -#: ../common/cli_overview.rst:44 -msgid "Create and manage containers." -msgstr "" - -#: ../common/cli_overview.rst:41 ../common/cli_overview.rst:47 -msgid "Create and manage databases." -msgstr "" - -#: ../common/cli_overview.rst:37 ../common/cli_overview.rst:40 -msgid "Create and manage images, instances, and flavors." -msgstr "" - -#: ../common/cli_overview.rst:49 ../common/cli_overview.rst:55 -#: ../common/cli_overview.rst:59 ../common/cli_overview.rst:62 -msgid "Create and manage images." -msgstr "" - -#: ../common/cli_overview.rst:58 ../common/cli_overview.rst:62 -#: ../common/cli_overview.rst:65 -msgid "Create and manage keys." -msgstr "" - -#: ../common/cli_overview.rst:78 -msgid "Create and manage shared file systems" -msgstr "" - -#: ../common/cli_overview.rst:81 ../common/cli_overview.rst:85 -#: ../common/cli_overview.rst:88 -msgid "Create and manage shared file systems." -msgstr "" - -#: ../common/cli_overview.rst:44 ../common/cli_overview.rst:50 -#: ../common/cli_overview.rst:54 ../common/cli_overview.rst:57 -msgid "Create and manage users, tenants, roles, endpoints, and credentials." -msgstr "" - -#: ../common/cli_overview.rst:34 ../common/cli_overview.rst:37 -msgid "Create and manage volumes." -msgstr "" - -#: ../common/cli_set_environment_variables_using_openstack_rc.rst:52 -#: ../common/cli_set_environment_variables_using_openstack_rc.rst:53 -msgid "Create and source the OpenStack RC file" -msgstr "" - -#: ../common/cli_manage_images.rst:114 -msgid "Create or update an image (glance)" -msgstr "" - -#: ../common/dashboard_customizing.rst:31 -msgid "" -"Create two PNG logo files with transparent backgrounds using the following " -"sizes:" -msgstr "" - -#: ../common/glossary.rst:3394 ../common/glossary.rst:3401 -#: ../common/glossary.rst:3408 ../common/glossary.rst:3416 -#: ../common/glossary.rst:3405 -msgid "" -"Creates a full Object Storage development environment within a single VM." -msgstr "" - -#: ../common/get_started_telemetry.rst:16 -#: ../common/get_started_telemetry.rst:15 -msgid "Creates alarms when collected data breaks defined rules." -msgstr "" - -#: ../common/get_started_identity.rst:31 ../common/get_started_identity.rst:30 -msgid "Credentials" -msgstr "" - -#: ../common/conventions.rst:16 -msgid "Critical information about the risk of data loss or security issues." -msgstr "" - -#: ../common/glossary.rst:917 -msgid "Cross-Origin Resource Sharing (CORS)" -msgstr "" - -#: ../common/glossary.rst:925 -msgid "Crowbar" -msgstr "" - -#: ../common/cli_manage_images.rst:214 -msgid "" -"Currently the libvirt virtualization tool determines the disk, CD-ROM, and " -"VIF device models based on the configured hypervisor type (``libvirt_type`` " -"in ``/etc/nova/nova.conf``). For the sake of optimal performance, libvirt " -"defaults to using virtio for both disk and VIF (NIC) models. The " -"disadvantage of this approach is that it is not possible to run operating " -"systems that lack virtio drivers, for example, BSD, Solaris, and older " -"versions of Linux and Windows." -msgstr "" - -#: ../common/cli_install_openstack_command_line_clients.rst:21 -msgid "Currently, the clients do not support Python 3." -msgstr "" - -#: ../common/glossary.rst:192 -msgid "Custom modules that extend some OpenStack core APIs." -msgstr "" - -#: ../common/dashboard_customizing.rst:8 -msgid "Customize the dashboard" -msgstr "" - -#: ../common/glossary.rst:951 -msgid "DAC" -msgstr "" - -#: ../common/glossary.rst:1079 -msgid "DHCP" -msgstr "" - -#: ../common/glossary.rst:1088 -msgid "DHCP agent" -msgstr "" - -#: ../common/glossary.rst:1152 -msgid "DNS" -msgstr "" - -#: ../common/glossary.rst:1159 -msgid "DNS record" -msgstr "" - -#: ../common/glossary.rst:1164 -msgid "DNS service" -msgstr "" - -#: ../common/glossary.rst:1212 ../common/glossary.rst:1213 -msgid "DRTM" -msgstr "" - -#: ../common/glossary.rst:1174 -msgid "" -"Daemon that provides DNS, DHCP, BOOTP, and TFTP services for virtual " -"networks." -msgstr "" - -#: ../common/cli_overview.rst:76 ../common/cli_overview.rst:85 -#: ../common/cli_overview.rst:88 ../common/cli_overview.rst:50 -msgid "Data processing" -msgstr "" - -#: ../common/glossary.rst:989 ../common/get_started_sahara.rst:4 -msgid "Data processing service" -msgstr "" - -#: ../common/get_started_identity.rst:29 -msgid "" -"Data that confirms the user's identity. For example: user name and password, " -"user name and API key, or an authentication token provided by the Identity " -"Service." -msgstr "" - -#: ../common/get_started_identity.rst:29 ../common/get_started_identity.rst:28 -msgid "" -"Data that confirms the user's identity. For example: user name and password, " -"user name and API key, or an authentication token provided by the Identity " -"service." -msgstr "" - -#: ../common/glossary.rst:912 -msgid "" -"Data that is only known to or accessible by a user and used to verify that " -"the user is who he says he is. Credentials are presented to the server " -"during authentication. Examples include a password, secret key, digital " -"certificate, and fingerprint." -msgstr "" - -#: ../common/get_started_image_service.rst:35 -#: ../common/get_started_image_service.rst:32 -msgid "Database" -msgstr "" - -#: ../common/glossary.rst:982 ../common/cli_overview.rst:41 -#: ../common/cli_overview.rst:47 -msgid "Database service" -msgstr "" - -#: ../common/get_started_database_service.rst:4 -msgid "Database service overview" -msgstr "" - -#: ../common/glossary.rst:1001 -msgid "Debian" -msgstr "" - -#: ../common/glossary.rst:574 -msgid "" -"Defines resources for a cell, including CPU, storage, and networking. Can " -"apply to the specific services within a cell or a whole cell." -msgstr "" - -#: ../common/cli_set_environment_variables_using_openstack_rc.rst:18 -msgid "" -"Defining environment variables using an environment file is not a common " -"practice on Microsoft Windows. Environment variables are usually defined in " -"the :guilabel:`Advanced` tab of the :guilabel:`System Properties` dialog box." -msgstr "" - -#: ../common/cli_manage_volumes.rst:211 -msgid "Delete a volume" -msgstr "" - -#: ../common/cli_manage_volumes.rst:384 -msgid "Delete a volume transfer" -msgstr "" - -#: ../common/cli_manage_volumes.rst:217 -msgid "Delete the volume using either the volume name or ID::" -msgstr "" - -#: ../common/cli_manage_volumes.rst:411 -msgid "Delete the volume::" -msgstr "" - -#: ../common/cli_manage_images.rst:186 -msgid "" -"Deletes all image properties that are not explicitly set in the update " -"request. Otherwise, those properties not referenced are preserved." -msgstr "" - -#: ../common/glossary.rst:1039 -msgid "" -"Denial of service (DoS) is a short form for denial-of-service attack. This " -"is a malicious attempt to prevent legitimate users from using a service." -msgstr "" - -#: ../common/glossary.rst:889 -msgid "" -"Depending on context, the core API is either the OpenStack API or the main " -"API of a specific core project, such as Compute, Networking, Image service, " -"and so on." -msgstr "" - -#: ../common/cli_overview.rst:54 -msgid "Deployment service" -msgstr "" - -#: ../common/glossary.rst:1911 ../common/glossary.rst:1917 -msgid "" -"Describes the parameters of the various virtual machine images that are " -"available to users; includes parameters such as CPU, storage, and memory. " -"Alternative term for flavor." -msgstr "" - -#: ../common/cli_install_openstack_command_line_clients.rst:19 -#: ../common/cli_overview.rst:32 ../common/get_started_with_openstack.rst:27 -#: ../common/get_started_with_openstack.rst:35 -msgid "Description" -msgstr "" - -#: ../common/glossary.rst:1048 -msgid "Designate" -msgstr "" - -#: ../common/get_started_sahara.rst:26 ../common/get_started_sahara.rst:27 -msgid "Designed as an OpenStack component." -msgstr "" - -#: ../common/glossary.rst:1052 -msgid "Desktop-as-a-Service" -msgstr "" - -#: ../common/glossary.rst:1650 ../common/glossary.rst:1656 -msgid "" -"Determines whether back-end members of a VIP pool can process a request. A " -"pool can have several health monitors associated with it. When a pool has " -"several monitors associated with it, all monitors check each member of the " -"pool. All monitors must declare a member to be healthy for it to stay active." -msgstr "" - -#: ../common/glossary.rst:1074 -msgid "DevStack" -msgstr "" - -#: ../common/glossary.rst:1685 ../common/glossary.rst:1691 -msgid "" -"Device plugged into a PCI slot, such as a fibre channel or network card." -msgstr "" - -#: ../common/glossary.rst:1093 -msgid "Diablo" -msgstr "" - -#: ../common/get_started_identity.rst:21 ../common/get_started_identity.rst:20 -msgid "" -"Digital representation of a person, system, or service who uses OpenStack " -"cloud services. The Identity service validates that incoming requests are " -"made by the user who claims to be making the call. Users have a login and " -"may be assigned tokens to access resources. Users can be directly assigned " -"to a particular tenant and behave as if they are contained in that tenant." -msgstr "" - -#: ../common/support-compute.rst:212 -msgid "Disable live snapshotting" -msgstr "" - -#: ../common/glossary.rst:2460 ../common/glossary.rst:2467 -#: ../common/glossary.rst:2466 ../common/glossary.rst:2472 -#: ../common/glossary.rst:2474 ../common/glossary.rst:2463 -msgid "" -"Disables server-side message acknowledgment in the Compute RabbitMQ. " -"Increases performance but decreases reliability." -msgstr "" - -#: ../common/cli_discover_version_number_for_a_client.rst:3 -msgid "Discover the version number for a client" -msgstr "" - -#: ../common/glossary.rst:954 -msgid "" -"Discretionary access control. Governs the ability of subjects to access " -"objects, while enabling users to make policy decisions and assign security " -"attributes. The traditional UNIX system of users, groups, and read-write-" -"execute permissions is an example of DAC." -msgstr "" - -#: ../common/glossary.rst:3698 ../common/glossary.rst:3705 -#: ../common/glossary.rst:3712 ../common/glossary.rst:3720 -#: ../common/glossary.rst:3709 -msgid "" -"Disk-based data storage generally represented as an iSCSI target with a file " -"system that supports extended attributes; can be persistent or ephemeral." -msgstr "" - -#: ../common/glossary.rst:3378 ../common/glossary.rst:3385 -#: ../common/glossary.rst:3392 ../common/glossary.rst:3400 -#: ../common/glossary.rst:3389 -msgid "" -"Disk-based virtual memory used by operating systems to provide more memory " -"than is actually available on the system." -msgstr "" - -#: ../common/glossary.rst:3247 ../common/glossary.rst:3254 -#: ../common/glossary.rst:3261 ../common/glossary.rst:3269 -#: ../common/glossary.rst:3258 -msgid "Distributed block storage system for QEMU, supported by OpenStack." -msgstr "" - -#: ../common/glossary.rst:1072 -msgid "" -"Distributes partitions proportionately across Object Storage devices based " -"on the storage capacity of each device." -msgstr "" - -#: ../common/glossary.rst:1148 -msgid "Django" -msgstr "" - -#: ../common/app_support.rst:14 ../common/app_support.rst:12 -msgid "Documentation" -msgstr "" - -#: ../common/app_support.rst:216 ../common/app_support.rst:213 -#: ../common/app_support.rst:211 ../common/app_support.rst:217 -#: ../common/app_support.rst:219 ../common/app_support.rst:222 -#: ../common/app_support.rst:224 -msgid "Documentation feedback" -msgstr "" - -#: ../common/glossary.rst:1155 -msgid "" -"Domain Name Server. A hierarchical and distributed naming system for " -"computers, services, and resources connected to the Internet or a private " -"network. Associates a human-friendly names to IP addresses." -msgstr "" - -#: ../common/glossary.rst:1187 ../common/glossary.rst:1188 -msgid "Domain Name Service (DNS)" -msgstr "" - -#: ../common/glossary.rst:1193 ../common/glossary.rst:1194 -msgid "Domain Name System (DNS)" -msgstr "" - -#: ../common/cli_set_environment_variables_using_openstack_rc.rst:24 -msgid "Download and source the OpenStack RC file" -msgstr "" - -#: ../common/get_started_identity.rst:28 -msgid "Drivers" -msgstr "" - -#: ../common/get_started_identity.rst:24 -msgid "" -"Drivers or a service back end are integrated to the centralized server, and " -"are used for accessing identity information in repositories, external to " -"OpenStack, and maybe already existing in the infrastructure where OpenStack " -"is deployed (for example, SQL databases or LDAP servers)." -msgstr "" - -#: ../common/app_support.rst:93 -msgid "" -"During the set up or testing of OpenStack, you might have questions about " -"how a specific task is completed or be in a situation where a feature does " -"not work correctly. Use the `ask.openstack.org `__ " -"site to ask questions and get answers. When you visit the http://ask." -"openstack.org site, scan the recently asked questions to see whether your " -"question has already been answered. If not, ask a new question. Be sure to " -"give a clear, concise summary in the title and provide as much detail as " -"possible in the description. Paste in your command output or stack traces, " -"links to screen shots, and any other information which might be useful." -msgstr "" - -#: ../common/app_support.rst:93 ../common/app_support.rst:90 -#: ../common/app_support.rst:88 -msgid "" -"During the set up or testing of OpenStack, you might have questions about " -"how a specific task is completed or be in a situation where a feature does " -"not work correctly. Use the `ask.openstack.org `__ site to ask questions and get answers. When you visit the https://" -"ask.openstack.org site, scan the recently asked questions to see whether " -"your question has already been answered. If not, ask a new question. Be sure " -"to give a clear, concise summary in the title and provide as much detail as " -"possible in the description. Paste in your command output or stack traces, " -"links to screen shots, and any other information which might be useful." -msgstr "" - -#: ../common/glossary.rst:1226 ../common/glossary.rst:1227 -msgid "Dynamic Host Configuration Protocol (DHCP)" -msgstr "" - -#: ../common/glossary.rst:1082 -msgid "" -"Dynamic Host Configuration Protocol. A network protocol that configures " -"devices that are connected to a network so that they can communicate on that " -"network by using the Internet Protocol (IP). The protocol is implemented in " -"a client-server model where DHCP clients request configuration data, such as " -"an IP address, a default route, and one or more DNS server addresses from a " -"DHCP server." -msgstr "" - -#: ../common/glossary.rst:1231 ../common/glossary.rst:1232 -msgid "Dynamic HyperText Markup Language (DHTML)" -msgstr "" - -#: ../common/glossary.rst:1215 ../common/glossary.rst:1216 -msgid "Dynamic root of trust measurement." -msgstr "" - -#: ../common/glossary.rst:1242 ../common/glossary.rst:1243 -msgid "EBS boot volume" -msgstr "" - -#: ../common/glossary.rst:1253 ../common/glossary.rst:1254 -msgid "EC2" -msgstr "" - -#: ../common/glossary.rst:1263 ../common/glossary.rst:1264 -msgid "EC2 API" -msgstr "" - -#: ../common/glossary.rst:1268 ../common/glossary.rst:1269 -msgid "EC2 Compatibility API" -msgstr "" - -#: ../common/glossary.rst:1258 ../common/glossary.rst:1259 -msgid "EC2 access key" -msgstr "" - -#: ../common/glossary.rst:1273 ../common/glossary.rst:1274 -msgid "EC2 secret key" -msgstr "" - -#: ../common/glossary.rst:1335 ../common/glossary.rst:1336 -msgid "ESX" -msgstr "" - -#: ../common/glossary.rst:1339 ../common/glossary.rst:1340 -msgid "ESXi" -msgstr "" - -#: ../common/glossary.rst:1350 ../common/glossary.rst:1351 -msgid "ETag" -msgstr "" - -#: ../common/cli_overview.rst:5 -msgid "" -"Each OpenStack project provides a command-line client, which enables you to " -"access the project API through easy-to-use commands. For example, the " -"Compute service provides a nova command-line client." -msgstr "" - -#: ../common/glossary.rst:2610 -msgid "" -"Each OpenStack release has a code name. Code names ascend in alphabetical " -"order: Austin, Bexar, Cactus, Diablo, Essex, Folsom, Grizzly, Havana, " -"Icehouse, Juno, Kilo, Liberty, and Meiji. Code names are cities or counties " -"near where the corresponding OpenStack design summit took place. An " -"exception, called the Waldon exception, is granted to elements of the state " -"flag that sound especially cool. Code names are chosen by popular vote." -msgstr "" - -#: ../common/glossary.rst:2609 ../common/glossary.rst:2615 -#: ../common/glossary.rst:2617 ../common/glossary.rst:2606 -msgid "" -"Each OpenStack release has a code name. Code names ascend in alphabetical " -"order: Austin, Bexar, Cactus, Diablo, Essex, Folsom, Grizzly, Havana, " -"Icehouse, Juno, Kilo, Liberty, and Mitaka. Code names are cities or counties " -"near where the corresponding OpenStack design summit took place. An " -"exception, called the Waldon exception, is granted to elements of the state " -"flag that sound especially cool. Code names are chosen by popular vote." -msgstr "" - -#: ../common/glossary.rst:2603 -msgid "" -"Each OpenStack release has a code name. Code names ascend in alphabetical " -"order: Austin, Bexar, Cactus, Diablo, Essex, Folsom, Grizzly, Havana, " -"Icehouse, Juno, Kilo, and Liberty. Code names are cities or counties near " -"where the corresponding OpenStack design summit took place. An exception, " -"called the Waldon exception, is granted to elements of the state flag that " -"sound especially cool. Code names are chosen by popular vote." -msgstr "" - -#: ../common/glossary.rst:2603 -msgid "" -"Each OpenStack release has a code name. Code names ascend in alphabetical " -"order: Austin, Bexar, Cactus, Diablo, Essex, Folsom, Grizzly, Havana, " -"Icehouse, Juno, and Kilo. Code names are cities or counties near where the " -"corresponding OpenStack design summit took place. An exception, called the " -"Waldon exception, is granted to elements of the state flag that sound " -"especially cool. Code names are chosen by popular vote." -msgstr "" - -#: ../common/get_started_storage_concepts.rst:29 -#: ../common/get_started_storage_concepts.rst:32 -#: ../common/get_started_storage_concepts.rst:31 -msgid "Easily scalable for future growth" -msgstr "" - -#: ../common/get_started_telemetry.rst:8 ../common/get_started_telemetry.rst:7 -msgid "Efficiently polls metering data related to OpenStack services." -msgstr "" - -#: ../common/glossary.rst:2915 ../common/glossary.rst:2922 -#: ../common/glossary.rst:2929 ../common/glossary.rst:2931 -#: ../common/glossary.rst:2920 -msgid "" -"Either a soft or hard reboot of a server. With a soft reboot, the operating " -"system is signaled to restart, which enables a graceful shutdown of all " -"processes. A hard reboot is the equivalent of power cycling the server. The " -"virtualization platform should ensure that the reboot action has completed " -"successfully, even in cases in which the underlying domain/VM is paused or " -"halted/stopped." -msgstr "" - -#: ../common/glossary.rst:1278 ../common/glossary.rst:1279 -msgid "Elastic Block Storage (EBS)" -msgstr "" - -#: ../common/glossary.rst:1119 -msgid "Element of RabbitMQ that provides a response to an incoming MQ message." -msgstr "" - -#: ../common/glossary.rst:2445 ../common/glossary.rst:2452 -#: ../common/glossary.rst:2451 ../common/glossary.rst:2457 -#: ../common/glossary.rst:2459 ../common/glossary.rst:2448 -msgid "" -"Enables Compute and Networking integration, which enables Networking to " -"perform network management for guest VMs." -msgstr "" - -#: ../common/glossary.rst:2362 ../common/glossary.rst:2369 -#: ../common/glossary.rst:2368 ../common/glossary.rst:2374 -#: ../common/glossary.rst:2363 -msgid "" -"Enables Compute to communicate with NetApp storage devices through the " -"NetApp OnCommand Provisioning Manager." -msgstr "" - -#: ../common/get_started_with_openstack.rst:40 -#: ../common/get_started_with_openstack.rst:48 -msgid "" -"Enables Network-Connectivity-as-a-Service for other OpenStack services, such " -"as OpenStack Compute. Provides an API for users to define networks and the " -"attachments into them. Has a pluggable architecture that supports many " -"popular networking vendors and technologies." -msgstr "" - -#: ../common/glossary.rst:2171 ../common/glossary.rst:2177 -msgid "" -"Enables Networking to distribute incoming requests evenly between designated " -"instances." -msgstr "" - -#: ../common/glossary.rst:2144 ../common/glossary.rst:2150 -msgid "" -"Enables a Linux bridge to understand a Networking port, interface " -"attachment, and other abstractions." -msgstr "" - -#: ../common/get_started_compute.rst:121 ../common/get_started_compute.rst:120 -msgid "Enables users to submit commands as a tenant administrator or end user." -msgstr "" - -#: ../common/get_started_storage_concepts.rst:54 -#: ../common/get_started_storage_concepts.rst:57 -#: ../common/get_started_storage_concepts.rst:56 -#: ../common/get_started_object_storage.rst:36 -msgid "" -"Enables users to submit commands to the REST API through a command-line " -"client authorized as either a admin user, reseller user, or swift user." -msgstr "" - -#: ../common/glossary.rst:1733 ../common/glossary.rst:1739 -msgid "" -"Encrypted HTTP communications using SSL or TLS; most OpenStack API endpoints " -"and many inter-component communications support HTTPS communication." -msgstr "" - -#: ../common/get_started_storage_concepts.rst:27 -#: ../common/get_started_storage_concepts.rst:28 -#: ../common/get_started_storage_concepts.rst:26 -msgid "Encryption is available" -msgstr "" - -#: ../common/get_started_identity.rst:68 ../common/get_started_identity.rst:67 -msgid "Endpoint" -msgstr "" - -#: ../common/cli_install_openstack_command_line_clients.rst:64 -msgid "" -"Ensure that the ``C:\\Python27\\Scripts`` directory is defined in the " -"``PATH`` environment variable, and use the ``easy_install`` command from the " -"setuptools package:" -msgstr "" - -#: ../common/cli_manage_images.rst:290 -msgid "" -"Ensure that the version of qemu you are using is version 0.14 or later. " -"Earlier versions of qemu result in an ``unknown option -s`` error message in " -"the ``nova-compute.log`` file." -msgstr "" - -#: ../common/glossary.rst:1325 ../common/glossary.rst:1326 -msgid "Essex" -msgstr "" - -#: ../common/glossary.rst:1360 ../common/glossary.rst:1361 -msgid "Eucalyptus Kernel Image (EKI)" -msgstr "" - -#: ../common/glossary.rst:1364 ../common/glossary.rst:1365 -msgid "Eucalyptus Machine Image (EMI)" -msgstr "" - -#: ../common/glossary.rst:1368 ../common/glossary.rst:1369 -msgid "Eucalyptus Ramdisk Image (ERI)" -msgstr "" - -#: ../common/cli_nova_evacuate.rst:5 -msgid "Evacuate instances" -msgstr "" - -#: ../common/cli_nova_evacuate.rst:21 -msgid "" -"Evacuate the instance. You can pass the instance password to the command by " -"using the :option:`--password PWD` option. If you do not specify a password, " -"one is generated and printed after the command finishes successfully. The " -"following command evacuates a server without shared storage from a host that " -"is down to the specified HOST_B::" -msgstr "" - -#: ../common/cli_manage_images.rst:294 -msgid "" -"Examine the :file:`/var/log/nova-api.log` and :file:`/var/log/nova-compute." -"log` log files for error messages." -msgstr "" - -#: ../common/get_started_storage_concepts.rst:31 -#: ../common/get_started_storage_concepts.rst:34 -#: ../common/get_started_storage_concepts.rst:33 -msgid "Example: 1 TB \"extra hard drive\"" -msgstr "" - -#: ../common/get_started_storage_concepts.rst:30 -#: ../common/get_started_storage_concepts.rst:33 -#: ../common/get_started_storage_concepts.rst:32 -msgid "Example: 10 GB first disk, 30 GB/core second disk" -msgstr "" - -#: ../common/get_started_storage_concepts.rst:32 -#: ../common/get_started_storage_concepts.rst:35 -#: ../common/get_started_storage_concepts.rst:34 -msgid "Example: 10s of TBs of data set storage" -msgstr "" - -#: ../common/glossary.rst:1995 ../common/glossary.rst:2001 -msgid "" -"Extension to iptables that allows creation of firewall rules that match " -"entire \"sets\" of IP addresses simultaneously. These sets reside in indexed " -"data structures to increase efficiency, particularly on systems with a large " -"quantity of rules." -msgstr "" - -#: ../common/glossary.rst:1461 -msgid "FWaaS" -msgstr "" - -#: ../common/glossary.rst:2309 ../common/glossary.rst:2316 -#: ../common/glossary.rst:2315 ../common/glossary.rst:2321 -#: ../common/glossary.rst:2310 -msgid "" -"Facility in Compute that allows each virtual machine instance to have more " -"than one VIF connected to it." -msgstr "" - -#: ../common/glossary.rst:2339 ../common/glossary.rst:2346 -#: ../common/glossary.rst:2345 ../common/glossary.rst:2351 -#: ../common/glossary.rst:2340 -msgid "" -"Facility in Compute that enables a virtual machine instance to have more " -"than one VIF connected to it." -msgstr "" - -#: ../common/glossary.rst:1415 ../common/glossary.rst:1416 -msgid "FakeLDAP" -msgstr "" - -#: ../common/get_started_sahara.rst:16 ../common/get_started_sahara.rst:17 -msgid "" -"Fast provisioning of Hadoop clusters on OpenStack for development and QA." -msgstr "" - -#: ../common/glossary.rst:2045 ../common/glossary.rst:2051 -msgid "" -"Feature in modern Ethernet networks that supports frames up to approximately " -"9000 bytes." -msgstr "" - -#: ../common/glossary.rst:1543 ../common/glossary.rst:1544 -msgid "" -"Feature of certain network interface drivers that combines many smaller " -"received packets into a large packet before delivery to the kernel IP stack." -msgstr "" - -#: ../common/glossary.rst:1431 ../common/glossary.rst:1432 -msgid "Fedora" -msgstr "" - -#: ../common/get_started_with_openstack.rst:141 -#: ../common/get_started_feedback.rst:3 -msgid "Feedback" -msgstr "" - -#: ../common/glossary.rst:1435 ../common/glossary.rst:1436 -msgid "Fibre Channel" -msgstr "" - -#: ../common/glossary.rst:1440 ../common/glossary.rst:1441 -msgid "Fibre Channel over Ethernet (FCoE)" -msgstr "" - -#: ../common/glossary.rst:1394 ../common/glossary.rst:1395 -msgid "" -"File system option that enables storage of additional information beyond " -"owner, group, permissions, modification time, and so on. The underlying " -"Object Storage file system must support extended attributes." -msgstr "" - -#: ../common/glossary.rst:1346 ../common/glossary.rst:1347 -msgid "" -"Filtering tool for a Linux bridging firewall, enabling filtering of network " -"traffic passing through a Linux bridge. Used to restrict communications " -"between hosts and/or nodes in OpenStack Compute along with iptables, " -"arptables, and ip6tables." -msgstr "" - -#: ../common/support-compute.rst:144 -msgid "" -"Finally, from the :file:`/var/lib/nova/instances` directory for the " -"instance, see if this command returns an error::" -msgstr "" - -#: ../common/cli_manage_volumes.rst:399 -msgid "Find the matching transfer ID::" -msgstr "" - -#: ../common/glossary.rst:1460 ../common/glossary.rst:1461 -msgid "Firewall-as-a-Service (FWaaS)" -msgstr "" - -#: ../common/glossary.rst:1472 ../common/glossary.rst:1473 -msgid "Flat Manager" -msgstr "" - -#: ../common/glossary.rst:1492 ../common/glossary.rst:1493 -msgid "FlatDHCP Manager" -msgstr "" - -#: ../common/glossary.rst:1514 ../common/glossary.rst:1515 -msgid "Folsom" -msgstr "" - -#: ../common/glossary.rst:3165 ../common/glossary.rst:3154 -msgid "" -"For IaaS, ability for a regular (non-privileged) account to manage a virtual " -"infrastructure component such as networks without involving an administrator." -msgstr "" - -#: ../common/cli_install_openstack_command_line_clients.rst:191 -#: ../common/cli_install_openstack_command_line_clients.rst:197 -#: ../common/cli_install_openstack_command_line_clients.rst:199 -#: ../common/cli_install_openstack_command_line_clients.rst:201 -#: ../common/cli_install_openstack_command_line_clients.rst:203 -msgid "For Mac OS X or Linux::" -msgstr "" - -#: ../common/cli_install_openstack_command_line_clients.rst:195 -#: ../common/cli_install_openstack_command_line_clients.rst:201 -#: ../common/cli_install_openstack_command_line_clients.rst:203 -#: ../common/cli_install_openstack_command_line_clients.rst:205 -#: ../common/cli_install_openstack_command_line_clients.rst:207 -msgid "For Microsoft Windows::" -msgstr "" - -#: ../common/cli_install_openstack_command_line_clients.rst:231 -#: ../common/cli_install_openstack_command_line_clients.rst:233 -#: ../common/cli_install_openstack_command_line_clients.rst:235 -msgid "" -"For SUSE Linux Enterprise Server, use ``zypper`` to install the clients from " -"the distribution packages in the Open Build Service. First, add the Open " -"Build Service repository::" -msgstr "" - -#: ../common/cli_install_openstack_command_line_clients.rst:218 -#: ../common/cli_install_openstack_command_line_clients.rst:224 -msgid "" -"For SUSE Linux Enterprise Server, use zypper to install the clients from the " -"distribution packages in the Open Build Service. First, add the Open Build " -"Service repository::" -msgstr "" - -#: ../common/cli_install_openstack_command_line_clients.rst:221 -#: ../common/cli_install_openstack_command_line_clients.rst:223 -#: ../common/cli_install_openstack_command_line_clients.rst:225 -msgid "" -"For Ubuntu or Debian, use ``apt-get`` to install the clients from the " -"packaged versions::" -msgstr "" - -#: ../common/cli_manage_volumes.rst:269 -msgid "" -"For bulk import of data to the cloud, the data ingress system creates a new " -"Block Storage volume, copies data from the physical device, and transfers " -"device ownership to the end user." -msgstr "" - -#: ../common/get_started_logical_architecture.rst:23 -#: ../common/get_started_logical_architecture.rst:20 -msgid "" -"For communication between the processes of one service, an AMQP message " -"broker is used. The service's state is stored in a database. When deploying " -"and configuring your OpenStack cloud, you can choose among several message " -"broker and database solutions, such as RabbitMQ, Qpid, MySQL, MariaDB, and " -"SQLite." -msgstr "" - -#: ../common/cli_manage_images.rst:17 -msgid "" -"For details about image creation, see the `Virtual Machine Image Guide " -"`__." -msgstr "" - -#: ../common/cli_set_environment_variables_using_openstack_rc.rst:37 -#: ../common/cli_set_environment_variables_using_openstack_rc.rst:38 -msgid "" -"For example, copy the file to the computer from which you want to upload an " -"image with a ``glance`` client command." -msgstr "" - -#: ../common/support-compute.rst:54 -msgid "" -"For example, if you redirect error output to ``nova-api-err.log`` using :" -"command:`nova-api 2>/var/log/nova/nova-api-err.log`, resulting in the " -"process ID 8675, you can then run::" -msgstr "" - -#: ../common/cli_discover_version_number_for_a_client.rst:9 -msgid "" -"For example, to see the version number for the ``nova`` client, run the " -"following command::" -msgstr "" - -#: ../common/cli_manage_images.rst:109 -msgid "" -"For example, using the image ID shown above, you would issue the command as " -"follows::" -msgstr "" - -#: ../common/cli_set_environment_variables_using_openstack_rc.rst:113 -#: ../common/cli_set_environment_variables_using_openstack_rc.rst:114 -msgid "" -"For example, when you specify your password using the command-line client " -"with the ``--os-password`` argument, anyone with access to your computer can " -"view it in plain text with the ``ps`` field." -msgstr "" - -#: ../common/cli_manage_volumes.rst:415 -msgid "For example:" -msgstr "" - -#: ../common/cli_manage_volumes.rst:364 -msgid "For example::" -msgstr "" - -#: ../common/support-compute.rst:77 -msgid "" -"For more information, see `Guru Meditation Reports `_." -msgstr "" - -#: ../common/nova_show_usage_statistics_for_hosts_instances.rst:9 -msgid "" -"For more sophisticated monitoring, see the `ceilometer `__ project. You can also use tools, such as `Ganglia `__ or `Graphite `__, to gather " -"more detailed data." -msgstr "" - -#: ../common/cli_install_openstack_command_line_clients.rst:226 -#: ../common/cli_install_openstack_command_line_clients.rst:228 -#: ../common/cli_install_openstack_command_line_clients.rst:230 -msgid "" -"For openSUSE, use ``zypper`` to install the clients from the distribution " -"packages service::" -msgstr "" - -#: ../common/cli_install_openstack_command_line_clients.rst:213 -msgid "" -"For openSUSE, use zypper to install the clients from the distribution " -"packages Service::" -msgstr "" - -#: ../common/cli_install_openstack_command_line_clients.rst:213 -#: ../common/cli_install_openstack_command_line_clients.rst:219 -msgid "" -"For openSUSE, use zypper to install the clients from the distribution " -"packages service::" -msgstr "" - -#: ../common/app_support.rst:16 ../common/app_support.rst:14 -msgid "" -"For the available OpenStack documentation, see `docs.openstack.org `__." -msgstr "" - -#: ../common/glossary.rst:1525 ../common/glossary.rst:1526 -msgid "FormPost" -msgstr "" - -#: ../common/cli_manage_volumes.rst:26 -msgid "Free up space in a thinly-provisioned back end." -msgstr "" - -#: ../common/get_started_dashboard.rst:16 -#: ../common/get_started_dashboard.rst:17 -msgid "" -"From a network architecture point of view, this service must be accessible " -"to customers and the public API for each OpenStack service. To use the " -"administrator functionality for other services, it must also connect to " -"Admin API endpoints, which should not be accessible by customers." -msgstr "" - -#: ../common/log_in_dashboard.rst:144 ../common/log_in_dashboard.rst:143 -#: ../common/log_in_dashboard.rst:145 -msgid "" -"From the :guilabel:`Admin` tab, you can access the following category to " -"complete these tasks:" -msgstr "" - -#: ../common/log_in_dashboard.rst:74 ../common/log_in_dashboard.rst:70 -#: ../common/log_in_dashboard.rst:72 -msgid "From the :guilabel:`Project` tab, you can access the following tabs:" -msgstr "" - -#: ../common/log_in_dashboard.rst:62 ../common/log_in_dashboard.rst:64 -msgid "" -"From the :guilabel:`Project` tab, you can view and manage the resources in a " -"selected project, including instances and images. You select the project " -"from the CURRENT PROJECT list at the top of the tab." -msgstr "" - -#: ../common/cli_overview.rst:55 ../common/cli_overview.rst:61 -#: ../common/cli_overview.rst:64 ../common/cli_overview.rst:68 -#: ../common/cli_overview.rst:71 -msgid "" -"Gather statistics, list items, update metadata, and upload, download, and " -"delete files stored by the Object Storage service. Gain access to an Object " -"Storage installation for ad hoc processing." -msgstr "" - -#: ../common/glossary.rst:2776 ../common/glossary.rst:2783 -#: ../common/glossary.rst:2790 ../common/glossary.rst:2792 -#: ../common/glossary.rst:2781 -msgid "" -"Generally, extra properties on an Image service image to which only cloud " -"administrators have access. Limits which user roles can perform CRUD " -"operations on that property. The cloud administrator can configure any image " -"property as protected." -msgstr "" - -#: ../common/support-compute.rst:102 -msgid "" -"Generates :file:`novarc` from the project ZIP file and sources it for you." -msgstr "" - -#: ../common/nova_show_usage_statistics_for_hosts_instances.rst:76 -msgid "Get CPU, memory, I/O, and network statistics for an instance." -msgstr "" - -#: ../common/nova_show_usage_statistics_for_hosts_instances.rst:35 -msgid "" -"Get a summary of resource usage of all of the instances running on the host::" -msgstr "" - -#: ../common/nova_show_usage_statistics_for_hosts_instances.rst:90 -msgid "Get diagnostic statistics:" -msgstr "" - -#: ../common/get_started_with_openstack.rst:5 -msgid "Get started with OpenStack" -msgstr "" - -#: ../common/nova_show_usage_statistics_for_hosts_instances.rst:115 -msgid "Get summary statistics for each tenant:" -msgstr "" - -#: ../common/support-compute.rst:97 -msgid "" -"Gets the :file:`novarc` file from the project ZIP file, save existing " -"credentials in case of override. and manually source the :file:`novarc` file." -msgstr "" - -#: ../common/support-compute.rst:97 -msgid "" -"Gets the :file:`novarc` file from the project ZIP file, saves existing " -"credentials in case of override, and manually sources the :file:`novarc` " -"file." -msgstr "" - -#: ../common/app_support.rst:141 ../common/app_support.rst:138 -#: ../common/app_support.rst:136 -msgid "Give a clear, concise summary." -msgstr "" - -#: ../common/glossary.rst:2671 ../common/glossary.rst:2678 -#: ../common/glossary.rst:2684 ../common/glossary.rst:2686 -#: ../common/glossary.rst:2675 -msgid "" -"Gives guest VMs exclusive access to a PCI device. Currently supported in " -"OpenStack Havana and later releases." -msgstr "" - -#: ../common/glossary.rst:3 -msgid "Glossary" -msgstr "" - -#: ../common/glossary.rst:1570 ../common/glossary.rst:1571 -msgid "GlusterFS" -msgstr "" - -#: ../common/glossary.rst:1581 ../common/glossary.rst:1582 -msgid "Governance service" -msgstr "" - -#: ../common/glossary.rst:1588 ../common/glossary.rst:1589 -msgid "Graphic Interchange Format (GIF)" -msgstr "" - -#: ../common/glossary.rst:1593 ../common/glossary.rst:1594 -msgid "Graphics Processing Unit (GPU)" -msgstr "" - -#: ../common/glossary.rst:1598 ../common/glossary.rst:1599 -msgid "Green Threads" -msgstr "" - -#: ../common/support-compute.rst:71 -msgid "" -"Green Threads: Displays stack traces for each of the green threads within " -"the process (green threads do not have thread IDs)." -msgstr "" - -#: ../common/glossary.rst:1604 ../common/glossary.rst:1605 -msgid "Grizzly" -msgstr "" - -#: ../common/glossary.rst:1612 -msgid "Group" -msgstr "" - -#: ../common/support-compute.rst:47 -msgid "Guru Meditation reports" -msgstr "" - -#: ../common/dashboard_customizing.rst:110 -msgid "HTML title" -msgstr "" - -#: ../common/glossary.rst:1687 ../common/glossary.rst:1693 -msgid "HTTP" -msgstr "" - -#: ../common/glossary.rst:1696 ../common/glossary.rst:1702 -msgid "HTTPS" -msgstr "" - -#: ../common/glossary.rst:1616 ../common/glossary.rst:1622 -msgid "Hadoop" -msgstr "" - -#: ../common/get_started_object_storage.rst:34 -#: ../common/get_started_object_storage.rst:33 -msgid "Handles authentication and is usually OpenStack Identity." -msgstr "" - -#: ../common/cli_manage_images.rst:167 -msgid "Hash of image data to use for verification." -msgstr "" - -#: ../common/glossary.rst:1632 ../common/glossary.rst:1638 -msgid "Havana" -msgstr "" - -#: ../common/glossary.rst:1643 ../common/glossary.rst:1649 -msgid "Heat Orchestration Template (HOT)" -msgstr "" - -#: ../common/glossary.rst:1646 ../common/glossary.rst:1652 -msgid "Heat input in the format native to OpenStack." -msgstr "" - -#: ../common/dashboard_customizing.rst:129 -msgid "Help URL" -msgstr "" - -#: ../common/glossary.rst:2302 ../common/glossary.rst:2309 -#: ../common/glossary.rst:2308 ../common/glossary.rst:2314 -#: ../common/glossary.rst:2303 -msgid "" -"High-availability mode for legacy (nova) networking. Each compute node " -"handles NAT and DHCP and acts as a gateway for all of the VMs on it. A " -"networking failure on one compute node doesn't affect VMs on other compute " -"nodes." -msgstr "" - -#: ../common/glossary.rst:3801 ../common/glossary.rst:3808 -#: ../common/glossary.rst:3815 ../common/glossary.rst:3823 -#: ../common/glossary.rst:3812 -msgid "" -"High-performance 64-bit file system created by Silicon Graphics. Excels in " -"parallel I/O operations and data consistency." -msgstr "" - -#: ../common/glossary.rst:1682 ../common/glossary.rst:1688 -msgid "Host Bus Adapter (HBA)" -msgstr "" - -#: ../common/glossary.rst:1715 ../common/glossary.rst:1721 -msgid "Hyper-V" -msgstr "" - -#: ../common/glossary.rst:1725 ../common/glossary.rst:1731 -msgid "Hypertext Transfer Protocol (HTTP)" -msgstr "" - -#: ../common/glossary.rst:1730 ../common/glossary.rst:1736 -msgid "Hypertext Transfer Protocol Secure (HTTPS)" -msgstr "" - -#: ../common/glossary.rst:1699 ../common/glossary.rst:1705 -msgid "" -"Hypertext Transfer Protocol Secure (HTTPS) is a communications protocol for " -"secure communication over a computer network, with especially wide " -"deployment on the Internet. Technically, it is not a protocol in and of " -"itself; rather, it is the result of simply layering the Hypertext Transfer " -"Protocol (HTTP) on top of the SSL/TLS protocol, thus adding the security " -"capabilities of SSL/TLS to standard HTTP communications." -msgstr "" - -#: ../common/glossary.rst:1690 ../common/glossary.rst:1696 -msgid "" -"Hypertext Transfer Protocol. HTTP is an application protocol for " -"distributed, collaborative, hypermedia information systems. It is the " -"foundation of data communication for the World Wide Web. Hypertext is " -"structured text that uses logical links (hyperlinks) between nodes " -"containing text. HTTP is the protocol to exchange or transfer hypertext." -msgstr "" - -#: ../common/glossary.rst:1761 ../common/glossary.rst:1767 -msgid "ICMP" -msgstr "" - -#: ../common/glossary.rst:1768 ../common/glossary.rst:1774 -msgid "ID number" -msgstr "" - -#: ../common/glossary.rst:1801 ../common/glossary.rst:1807 -msgid "IDS" -msgstr "" - -#: ../common/glossary.rst:1879 ../common/glossary.rst:1885 -msgid "INI" -msgstr "" - -#: ../common/glossary.rst:1952 ../common/glossary.rst:1958 -msgid "IOPS" -msgstr "" - -#: ../common/glossary.rst:1955 ../common/glossary.rst:1961 -msgid "" -"IOPS (Input/Output Operations Per Second) are a common performance " -"measurement used to benchmark computer storage devices like hard disk " -"drives, solid state drives, and storage area networks." -msgstr "" - -#: ../common/glossary.rst:1965 ../common/glossary.rst:1971 -msgid "IP Address Management (IPAM)" -msgstr "" - -#: ../common/glossary.rst:1959 ../common/glossary.rst:1965 -msgid "IP address" -msgstr "" - -#: ../common/glossary.rst:1971 ../common/glossary.rst:1977 -msgid "IPL" -msgstr "" - -#: ../common/glossary.rst:1975 ../common/glossary.rst:1981 -msgid "IPMI" -msgstr "" - -#: ../common/glossary.rst:2014 ../common/glossary.rst:2020 -msgid "ISO9960" -msgstr "" - -#: ../common/glossary.rst:1746 ../common/glossary.rst:1752 -msgid "IaaS" -msgstr "" - -#: ../common/glossary.rst:1755 ../common/glossary.rst:1761 -msgid "Icehouse" -msgstr "" - -#: ../common/glossary.rst:1788 ../common/cli_overview.rst:44 -#: ../common/cli_overview.rst:50 ../common/glossary.rst:1794 -#: ../common/cli_overview.rst:54 ../common/cli_overview.rst:57 -msgid "Identity" -msgstr "" - -#: ../common/glossary.rst:1773 ../common/glossary.rst:1779 -msgid "Identity API" -msgstr "" - -#: ../common/glossary.rst:1777 ../common/glossary.rst:1783 -msgid "Identity back end" -msgstr "" - -#: ../common/glossary.rst:1796 ../common/glossary.rst:1802 -msgid "Identity service API" -msgstr "" - -#: ../common/glossary.rst:2845 ../common/glossary.rst:2852 -#: ../common/glossary.rst:2859 ../common/glossary.rst:2861 -#: ../common/glossary.rst:2850 -msgid "" -"If Object Storage finds objects, containers, or accounts that are corrupt, " -"they are placed in this state, are not replicated, cannot be read by " -"clients, and a correct copy is re-replicated." -msgstr "" - -#: ../common/log_in_dashboard.rst:31 -msgid "" -"If a certificate warning appears when you try to access the URL for the " -"first time, a self-signed certificate is in use, which is not considered " -"trustworthy by default. Verify the certificate or add an exception in the " -"browser to bypass the warning." -msgstr "" - -#: ../common/cli_nova_evacuate.rst:7 -msgid "" -"If a cloud compute node fails due to a hardware malfunction or another " -"reason, you can evacuate instances to make them available again. You can " -"optionally include the target host on the :command:`evacuate` command. If " -"you omit the host, the scheduler determines the target host." -msgstr "" - -#: ../common/glossary.rst:670 -msgid "" -"If a requested resource such as CPU time, disk storage, or memory is not " -"available in the parent cell, the request is forwarded to its associated " -"child cells. If the child cell can fulfill the request, it does. Otherwise, " -"it attempts to pass the request to any of its children." -msgstr "" - -#: ../common/glossary.rst:2639 ../common/glossary.rst:2646 -#: ../common/glossary.rst:2652 ../common/glossary.rst:2654 -#: ../common/glossary.rst:2643 -msgid "" -"If a requested resource, such as CPU time, disk storage, or memory, is not " -"available in the parent cell, the request is forwarded to associated child " -"cells." -msgstr "" - -#: ../common/support-compute.rst:174 -msgid "" -"If an instance remains in an intermediate state, such as ``deleting``, you " -"can use the :command:`nova reset-state` command to manually reset the state " -"of an instance to an error state. You can then delete the instance. For " -"example::" -msgstr "" - -#: ../common/support-compute.rst:135 -msgid "" -"If any files are missing, empty, or very small, the ``nova-compute`` service " -"did not successfully download the images from the Image Service." -msgstr "" - -#: ../common/support-compute.rst:135 -msgid "" -"If any files are missing, empty, or very small, the ``nova-compute`` service " -"did not successfully download the images from the Image service." -msgstr "" - -#: ../common/support-compute.rst:192 -msgid "" -"If instances do not boot or boot slowly, investigate file injection as a " -"cause." -msgstr "" - -#: ../common/support-compute.rst:33 -msgid "" -"If the log level is set to ``debug``, you can also specify " -"``logging_debug_format_suffix`` to append extra formatting. For information " -"about what variables are available for the formatter see http://docs.python." -"org/library/logging.html#formatter-objects." -msgstr "" - -#: ../common/support-compute.rst:33 -msgid "" -"If the log level is set to ``debug``, you can also specify " -"``logging_debug_format_suffix`` to append extra formatting. For information " -"about what variables are available for the formatter see http://docs.python." -"org/library/logging.html#formatter." -msgstr "" - -#: ../common/cli_manage_volumes.rst:38 -msgid "" -"If the volume is in use or has snapshots, the specified host destination " -"cannot accept the volume. If the user is not an administrator, the migration " -"fails." -msgstr "" - -#: ../common/log_in_dashboard.rst:49 -msgid "" -"If you are logged in as an administrator, the :guilabel:`Project` tab (:ref:" -"`dashboard-project-tab`) and :guilabel:`Admin` tab (:ref:`dashboard-admin-" -"tab`) and :guilabel:`Identity` tab (:ref:`dashboard-identity-tab`) are " -"displayed." -msgstr "" - -#: ../common/log_in_dashboard.rst:48 -msgid "" -"If you are logged in as an administrator, the :guilabel:`Project` tab (:ref:" -"`dashboard-project-tab`) and :guilabel:`Admin` tab (:ref:`dashboard-admin-" -"tab`) are displayed." -msgstr "" - -#: ../common/log_in_dashboard.rst:45 -msgid "" -"If you are logged in as an end user, the :guilabel:`Project` tab (:ref:" -"`dashboard-project-tab`) and :guilabel:`Identity` tab (:ref:`dashboard-" -"identity-tab`) are displayed." -msgstr "" - -#: ../common/log_in_dashboard.rst:45 -msgid "" -"If you are logged in as an end user, the :guilabel:`Project` tab is " -"displayed." -msgstr "" - -#: ../common/cli_manage_volumes.rst:380 -msgid "" -"If you do not have a sufficient quota for the transfer, the transfer is " -"refused." -msgstr "" - -#: ../common/dashboard_customizing.rst:17 -msgid "" -"If you do not want to use this theme you can remove it and its dependencies " -"using the following command::" -msgstr "" - -#: ../common/cli_manage_images.rst:286 -msgid "" -"If you encounter problems in creating an image in Image service or Compute, " -"the following information may help you troubleshoot the creation process." -msgstr "" - -#: ../common/support-compute.rst:202 -msgid "" -"If you have not enabled the configuration drive and you want to make user-" -"specified files available from the metadata server for to improve " -"performance and avoid boot failure if injection fails, you must disable " -"injection." -msgstr "" - -#: ../common/cli_install_openstack_command_line_clients.rst:14 -msgid "" -"If you need to install the command-line packages source packages, the " -"following table lists the software that you need to have to run the command-" -"line clients, and provides installation instructions as needed." -msgstr "" - -#: ../common/cli_manage_images.rst:222 -msgid "" -"If you specify a disk or CD-ROM bus model that is not supported, see the " -"Disk_and_CD-ROM_bus_model_values_table_. If you specify a VIF model that is " -"not supported, the instance fails to launch. See the VIF_model_values_table_." -msgstr "" - -#: ../common/support-compute.rst:214 -msgid "" -"If you use libvirt version ``1.2.2``, you may experience problems with live " -"snapshots creation. Occasionally, libvirt of the specified version fails to " -"perform the live snapshotting under load that presupposes a concurrent " -"creation of multiple snapshots." -msgstr "" - -#: ../common/cli_manage_volumes.rst:110 -msgid "" -"If your volume was created successfully, its status is ``available``. If its " -"status is ``error``, you might have exceeded your quota." -msgstr "" - -#: ../common/glossary.rst:1813 ../common/glossary.rst:1819 -msgid "Image API" -msgstr "" - -#: ../common/glossary.rst:1844 ../common/cli_overview.rst:49 -#: ../common/cli_overview.rst:55 ../common/glossary.rst:1850 -#: ../common/cli_overview.rst:59 ../common/cli_overview.rst:62 -msgid "Image service" -msgstr "" - -#: ../common/glossary.rst:1850 ../common/glossary.rst:1856 -msgid "Image service API" -msgstr "" - -#: ../common/glossary.rst:25 -msgid "" -"Impassable limits for guest VMs. Settings include total RAM size, maximum " -"number of vCPUs, and maximum disk size." -msgstr "" - -#: ../common/get_started_storage_concepts.rst:24 -#: ../common/get_started_storage_concepts.rst:23 -msgid "Implemented as a filesystem underlying OpenStack Compute" -msgstr "" - -#: ../common/glossary.rst:2858 ../common/glossary.rst:2865 -#: ../common/glossary.rst:2872 ../common/glossary.rst:2874 -#: ../common/glossary.rst:2863 -msgid "" -"In Compute and Block Storage, the ability to set resource limits on a per-" -"project basis." -msgstr "" - -#: ../common/glossary.rst:824 -msgid "" -"In Compute, conductor is the process that proxies database requests from the " -"compute process. Using conductor improves security because compute nodes do " -"not need direct access to the database." -msgstr "" - -#: ../common/glossary.rst:1190 ../common/glossary.rst:1191 -msgid "" -"In Compute, the support that enables associating DNS entries with floating " -"IP addresses, nodes, or cells so that hostnames are consistent across " -"reboots." -msgstr "" - -#: ../common/get_started_compute.rst:99 ../common/get_started_compute.rst:98 -msgid "" -"In Debian, a unique nova-consoleproxy package provides the nova-novncproxy, " -"nova-spicehtml5proxy, and nova-xvpvncproxy packages. To select packages, " -"edit the :file:`/etc/default/nova-consoleproxy` file or use the debconf " -"interface. You can also manually edit the :file:`/etc/default/nova-" -"consoleproxy` file, and stop and start the console daemons." -msgstr "" - -#: ../common/glossary.rst:3543 ../common/glossary.rst:3550 -msgid "" -"In Identity, each user is associated with one or more tenants, and in " -"Compute can be associated with roles, projects, or both." -msgstr "" - -#: ../common/glossary.rst:1141 -msgid "" -"In Object Storage, tools to test and ensure dispersion of objects and " -"containers to ensure fault tolerance." -msgstr "" - -#: ../common/glossary.rst:3557 ../common/glossary.rst:3565 -#: ../common/glossary.rst:3554 -msgid "" -"In OpenStack Identity, entities represent individual API consumers and are " -"owned by a specific domain. In OpenStack Compute, a user can be associated " -"with roles, projects, or both." -msgstr "" - -#: ../common/glossary.rst:215 -msgid "" -"In OpenStack, the API version for a project is part of the URL. For " -"example, :file:`example.com/nova/v1/foobar`." -msgstr "" - -#: ../common/glossary.rst:86 -msgid "" -"In a high-availability setup with an active/active configuration, several " -"systems share the load together and if one fails, the load is distributed to " -"the remaining systems." -msgstr "" - -#: ../common/glossary.rst:97 -msgid "" -"In a high-availability setup with an active/passive configuration, systems " -"are set up to bring additional resources online to replace those that have " -"failed." -msgstr "" - -#: ../common/cli_set_environment_variables_using_openstack_rc.rst:57 -#: ../common/cli_set_environment_variables_using_openstack_rc.rst:58 -msgid "" -"In a text editor, create a file named :file:`PROJECT-openrc.sh` and add the " -"following authentication information::" -msgstr "" - -#: ../common/get_started_identity.rst:12 -msgid "" -"In order to benefit from the Identity service, other OpenStack services need " -"to collaborate with it. When an OpenStack service receives a request from a " -"user, it checks with the Identity service whether the user is authorized to " -"make the request." -msgstr "" - -#: ../common/get_started_identity.rst:74 ../common/get_started_identity.rst:73 -msgid "" -"In the Identity service, a token that is issued to a user includes the list " -"of roles. Services that are being called by that user determine how they " -"interpret the set of roles a user has and to which operations or resources " -"each role grants access." -msgstr "" - -#: ../common/glossary.rst:1179 -msgid "" -"In the Identity service, provides isolation between projects and users. On " -"the Internet, separates a website from other sites. Often, the domain name " -"has two or more parts that are separated by dots. For example, yahoo.com, " -"usa.gov, harvard.edu, or mail.yahoo.com. Also, a domain is an entity or " -"container of all DNS-related information containing one or more records." -msgstr "" - -#: ../common/log_in_dashboard.rst:22 -msgid "" -"In the address bar, enter the host name or IP address for the dashboard." -msgstr "" - -#: ../common/glossary.rst:2629 ../common/glossary.rst:2636 -#: ../common/glossary.rst:2642 ../common/glossary.rst:2644 -#: ../common/glossary.rst:2633 -msgid "" -"In the context of Object Storage, this is a process that is not terminated " -"after an upgrade, restart, or reload of the service." -msgstr "" - -#: ../common/glossary.rst:116 -msgid "" -"In the context of the Identity service, the worker process that provides " -"access to the admin API." -msgstr "" - -#: ../common/cli_set_environment_variables_using_openstack_rc.rst:43 -#: ../common/cli_set_environment_variables_using_openstack_rc.rst:44 -msgid "" -"In the following example, the :file:`demo-openrc.sh` file is sourced for the " -"demo project::" -msgstr "" - -#: ../common/cli_manage_volumes.rst:33 -msgid "" -"In this example, ``--force-host-copy True`` forces the generic host-based " -"migration mechanism and bypasses any driver optimizations." -msgstr "" - -#: ../common/glossary.rst:438 -msgid "" -"Information that consists solely of ones and zeroes, which is the language " -"of computers." -msgstr "" - -#: ../common/glossary.rst:1749 ../common/glossary.rst:1755 -msgid "" -"Infrastructure-as-a-Service. IaaS is a provisioning model in which an " -"organization outsources physical components of a data center, such as " -"storage, hardware, servers, and networking components. A service provider " -"owns the equipment and is responsible for housing, operating and maintaining " -"it. The client typically pays on a per-use basis. IaaS is a model for " -"providing cloud services." -msgstr "" - -#: ../common/glossary.rst:1974 ../common/glossary.rst:1980 -msgid "Initial Program Loader." -msgstr "" - -#: ../common/support-compute.rst:190 -msgid "Injection problems" -msgstr "" - -#: ../common/cli_install_openstack_command_line_clients.rst:189 -#: ../common/cli_install_openstack_command_line_clients.rst:195 -#: ../common/cli_install_openstack_command_line_clients.rst:197 -#: ../common/cli_install_openstack_command_line_clients.rst:199 -#: ../common/cli_install_openstack_command_line_clients.rst:201 -msgid "Install each client separately by using the following command:" -msgstr "" - -#: ../common/cli_install_openstack_command_line_clients.rst:53 -msgid "Install pip through the package manager for your system:" -msgstr "" - -#: ../common/get_started_database_service.rst:24 -#: ../common/get_started_database_service.rst:23 -msgid "Install the Database service." -msgstr "" - -#: ../common/cli_install_openstack_command_line_clients.rst:3 -msgid "Install the OpenStack command-line clients" -msgstr "" - -#: ../common/cli_install_openstack_command_line_clients.rst:142 -msgid "Install the clients" -msgstr "" - -#: ../common/cli_install_openstack_command_line_clients.rst:9 -msgid "Install the prerequisite software" -msgstr "" - -#: ../common/cli_install_openstack_command_line_clients.rst:5 -msgid "" -"Install the prerequisite software and the Python package for each OpenStack " -"client." -msgstr "" - -#: ../common/cli_install_openstack_command_line_clients.rst:23 -msgid "Installed by default on Mac OS X." -msgstr "" - -#: ../common/cli_install_openstack_command_line_clients.rst:202 -#: ../common/cli_install_openstack_command_line_clients.rst:208 -#: ../common/cli_install_openstack_command_line_clients.rst:210 -#: ../common/cli_install_openstack_command_line_clients.rst:212 -#: ../common/cli_install_openstack_command_line_clients.rst:214 -msgid "Installing from packages" -msgstr "" - -#: ../common/cli_install_openstack_command_line_clients.rst:181 -#: ../common/cli_install_openstack_command_line_clients.rst:187 -#: ../common/cli_install_openstack_command_line_clients.rst:189 -#: ../common/cli_install_openstack_command_line_clients.rst:191 -#: ../common/cli_install_openstack_command_line_clients.rst:193 -msgid "Installing with pip" -msgstr "" - -#: ../common/get_started_compute.rst:137 ../common/get_started_compute.rst:136 -msgid "Instances in use" -msgstr "" - -#: ../common/get_started_database_service.rst:57 -#: ../common/get_started_database_service.rst:56 -msgid "" -"Instruments the complex system flows that support provisioning instances, " -"managing the lifecycle of instances, and performing operations on instances." -msgstr "" - -#: ../common/get_started_sahara.rst:35 ../common/get_started_sahara.rst:36 -msgid "" -"Integration with vendor specific management tools, such as Apache Ambari or " -"Cloudera Management Console." -msgstr "" - -#: ../common/glossary.rst:1978 ../common/glossary.rst:1984 -msgid "" -"Intelligent Platform Management Interface. IPMI is a standardized computer " -"system interface used by system administrators for out-of-band management of " -"computer systems and monitoring of their operation. In layman's terms, it is " -"a way to manage a computer using a direct network connection, whether it is " -"turned on or not; connecting to the hardware rather than an operating system " -"or login shell." -msgstr "" - -#: ../common/glossary.rst:368 -msgid "" -"Interactions and processes that are obfuscated from the user, such as " -"Compute volume mount, data transmission to an iSCSI target by a daemon, or " -"Object Storage object integrity checks." -msgstr "" - -#: ../common/get_started_block_storage.rst:19 -#: ../common/get_started_block_storage.rst:18 -msgid "" -"Interacts directly with the Block Storage service, and processes such as the " -"cinder-scheduler. It also interacts with these processes through a message " -"queue. The cinder-volume service responds to read and write requests sent to " -"the Block Storage service to maintain state. It can interact with a variety " -"of storage providers through a driver architecture." -msgstr "" - -#: ../common/glossary.rst:2450 ../common/glossary.rst:2457 -#: ../common/glossary.rst:2456 ../common/glossary.rst:2462 -#: ../common/glossary.rst:2464 ../common/glossary.rst:2453 -msgid "" -"Interface within Networking that enables organizations to create custom plug-" -"ins for advanced features, such as QoS, ACLs, or IDS." -msgstr "" - -#: ../common/get_started_logical_architecture.rst:17 #: ../common/get_started_logical_architecture.rst:14 +#: ../common/get_started_logical_architecture.rst:17 msgid "" "Internally, OpenStack services are composed of several processes. All " "services have at least one API process, which listens for API requests, " @@ -5474,1034 +3637,209 @@ msgid "" "processes." msgstr "" -#: ../common/cli_overview.rst:14 +#: ../common/get_started_logical_architecture.rst:20 +#: ../common/get_started_logical_architecture.rst:23 msgid "" -"Internally, each command uses cURL command-line tools, which embed API " -"requests. OpenStack APIs are RESTful APIs, and use the HTTP protocol. They " -"include methods, URIs, media types, and response codes." +"For communication between the processes of one service, an AMQP message " +"broker is used. The service's state is stored in a database. When deploying " +"and configuring your OpenStack cloud, you can choose among several message " +"broker and database solutions, such as RabbitMQ, Qpid, MySQL, MariaDB, and " +"SQLite." msgstr "" -#: ../common/glossary.rst:1764 ../common/glossary.rst:1770 +#: ../common/get_started_logical_architecture.rst:26 msgid "" -"Internet Control Message Protocol, used by network devices for control " -"messages. For example, :command:`ping` uses ICMP to test connectivity." +"Users can access OpenStack via the web-based user interface implemented by " +"the :ref:`get_started_dashboard`, via `command-line clients `__ and by issuing API requests through " +"tools like browser plug-ins or :command:`curl`. For applications, `several " +"SDKs `__ are available. Ultimately, all " +"these access methods issue REST API calls to the various OpenStack services." msgstr "" -#: ../common/glossary.rst:1937 ../common/glossary.rst:1943 -msgid "Internet Service Provider (ISP)" +#: ../common/get_started_logical_architecture.rst:29 +msgid "" +"Users can access OpenStack via the web-based user interface implemented by " +"the OpenStack dashboard, via `command-line clients `__ and by issuing API requests through tools like " +"browser plug-ins or :command:`curl`. For applications, `several SDKs `__ are available. Ultimately, all these access " +"methods issue REST API calls to the various OpenStack services." msgstr "" -#: ../common/glossary.rst:1942 ../common/glossary.rst:1948 -msgid "Internet Small Computer System Interface (iSCSI)" +#: ../common/get_started_logical_architecture.rst:36 +#: ../common/get_started_logical_architecture.rst:39 +msgid "" +"The following diagram shows the most common, but not the only possible, " +"architecture for an OpenStack cloud:" msgstr "" -#: ../common/glossary.rst:1932 ../common/glossary.rst:1938 -msgid "Internet protocol (IP)" +#: ../common/get_started_object_storage.rst:3 +#: ../common/get_started_object_storage.rst:4 +msgid "OpenStack Object Storage" msgstr "" -#: ../common/glossary.rst:1804 ../common/glossary.rst:1810 -msgid "Intrusion Detection System." +#: ../common/get_started_object_storage.rst:5 +#: ../common/get_started_object_storage.rst:6 +msgid "" +"The OpenStack Object Storage is a multi-tenant object storage system. It is " +"highly scalable and can manage large amounts of unstructured data at low " +"cost through a RESTful HTTP API." msgstr "" -#: ../common/get_started_object_storage.rst:10 -#: ../common/get_started_openstack_networking.rst:11 #: ../common/get_started_object_storage.rst:9 +#: ../common/get_started_object_storage.rst:10 #: ../common/get_started_openstack_networking.rst:10 +#: ../common/get_started_openstack_networking.rst:11 msgid "It includes the following components:" msgstr "" -#: ../common/glossary.rst:2024 ../common/glossary.rst:2030 -msgid "Java" -msgstr "" - -#: ../common/glossary.rst:2029 ../common/glossary.rst:2035 -msgid "JavaScript" -msgstr "" - -#: ../common/glossary.rst:2033 ../common/glossary.rst:2039 -msgid "JavaScript Object Notation (JSON)" -msgstr "" - -#: ../common/glossary.rst:2037 ../common/glossary.rst:2043 -msgid "Jenkins" -msgstr "" - -#: ../common/glossary.rst:2047 ../common/glossary.rst:2053 -msgid "Juno" -msgstr "" - -#: ../common/cli_overview.rst:58 ../common/cli_overview.rst:62 -#: ../common/cli_overview.rst:65 -msgid "Key Manager service" -msgstr "" - -#: ../common/get_started_sahara.rst:24 ../common/get_started_sahara.rst:25 -msgid "Key features are:" -msgstr "" - -#: ../common/glossary.rst:2062 ../common/glossary.rst:2068 -msgid "Key management service" -msgstr "" - -#: ../common/glossary.rst:2069 ../common/glossary.rst:2075 -msgid "Key-Value Store as a Service" -msgstr "" - -#: ../common/get_started_identity.rst:83 ../common/get_started_identity.rst:82 -msgid "Keystone Client" -msgstr "" - -#: ../common/glossary.rst:2079 ../common/glossary.rst:2085 -msgid "Kickstart" -msgstr "" - -#: ../common/glossary.rst:2084 ../common/glossary.rst:2090 -msgid "Kilo" -msgstr "" - -#: ../common/glossary.rst:2174 ../common/glossary.rst:2168 -msgid "LBaaS" -msgstr "" - -#: ../common/glossary.rst:2323 ../common/glossary.rst:2330 -#: ../common/glossary.rst:2329 ../common/glossary.rst:2335 -#: ../common/glossary.rst:2324 +#: ../common/get_started_object_storage.rst:12 +#: ../common/get_started_object_storage.rst:13 msgid "" -"LBaaS feature that provides availability monitoring using the `ping` " -"command, TCP, and HTTP/HTTPS GET." +"Accepts OpenStack Object Storage API and raw HTTP requests to upload files, " +"modify metadata, and create containers. It also serves file or container " +"listings to web browsers. To improve performance, the proxy server can use " +"an optional cache that is usually deployed with memcache." msgstr "" -#: ../common/cli_overview.rst:65 ../common/cli_overview.rst:71 -#: ../common/cli_overview.rst:74 ../common/cli_overview.rst:78 -#: ../common/cli_overview.rst:81 -msgid "" -"Launch stacks from templates, view details of running stacks including " -"events and resources, and update and delete stacks." +#: ../common/get_started_object_storage.rst:16 +#: ../common/get_started_object_storage.rst:17 +msgid "Proxy servers (swift-proxy-server)" msgstr "" -#: ../common/glossary.rst:2097 ../common/glossary.rst:2103 -msgid "Launchpad" -msgstr "" - -#: ../common/glossary.rst:2114 ../common/glossary.rst:2120 -msgid "Layer-2 (L2) agent" -msgstr "" - -#: ../common/glossary.rst:2101 ../common/glossary.rst:2107 -msgid "Layer-2 network" -msgstr "" - -#: ../common/glossary.rst:2119 ../common/glossary.rst:2125 -msgid "Layer-3 (L3) agent" -msgstr "" - -#: ../common/glossary.rst:2108 ../common/glossary.rst:2114 -msgid "Layer-3 network" -msgstr "" - -#: ../common/glossary.rst:2124 ../common/glossary.rst:2130 -msgid "Liberty" -msgstr "" - -#: ../common/glossary.rst:2141 ../common/glossary.rst:2147 -msgid "Linux Bridge neutron plug-in" -msgstr "" - -#: ../common/glossary.rst:2136 ../common/glossary.rst:2142 -msgid "Linux bridge" -msgstr "" - -#: ../common/glossary.rst:2146 ../common/glossary.rst:2152 -msgid "Linux containers (LXC)" -msgstr "" - -#: ../common/glossary.rst:2344 ../common/glossary.rst:2351 -#: ../common/glossary.rst:2350 ../common/glossary.rst:2356 -#: ../common/glossary.rst:2345 -msgid "" -"Linux kernel feature that provides independent virtual networking instances " -"on a single host with separate routing tables and interfaces. Similar to " -"virtual routing and forwarding (VRF) services on physical network equipment." -msgstr "" - -#: ../common/glossary.rst:3149 ../common/glossary.rst:3156 -#: ../common/glossary.rst:3163 ../common/glossary.rst:3171 -#: ../common/glossary.rst:3160 -msgid "" -"Linux kernel security module that provides the mechanism for supporting " -"access control policies." -msgstr "" - -#: ../common/cli_manage_volumes.rst:386 -msgid "List available volumes and their statuses::" -msgstr "" - -#: ../common/cli_manage_volumes.rst:47 -msgid "" -"List images, and note the ID of the image that you want to use for your " -"volume::" -msgstr "" - -#: ../common/nova_show_usage_statistics_for_hosts_instances.rst:78 -msgid "List instances:" -msgstr "" - -#: ../common/cli_manage_images.rst:21 -msgid "List or get details for images (glance)" -msgstr "" - -#: ../common/cli_manage_volumes.rst:62 -msgid "" -"List the availability zones, and note the ID of the availability zone in " -"which you want to create your volume::" -msgstr "" - -#: ../common/nova_show_usage_statistics_for_hosts_instances.rst:21 -msgid "List the hosts and the nova-related services that run on them::" -msgstr "" - -#: ../common/cli_manage_volumes.rst:223 -msgid "" -"List the volumes again, and note that the status of your volume is " -"``deleting``::" -msgstr "" - -#: ../common/cli_manage_volumes.rst:188 -msgid "List volumes::" -msgstr "" - -#: ../common/glossary.rst:763 -msgid "Lists allowed commands within the Compute rootwrap facility." -msgstr "" - -#: ../common/glossary.rst:66 -msgid "" -"Lists containers in Object Storage and stores container information in the " -"account database." -msgstr "" - -#: ../common/glossary.rst:2168 ../common/glossary.rst:2174 -msgid "Load-Balancer-as-a-Service (LBaaS)" -msgstr "" - -#: ../common/cli_manage_images.rst:162 -msgid "" -"Local file that contains the disk image to be uploaded during the update. " -"Alternatively, you can pass images to the client through stdin." -msgstr "" - -#: ../common/cli_set_environment_variables_using_openstack_rc.rst:26 -msgid "" -"Log in to the OpenStack dashboard, choose the project for which you want to " -"download the OpenStack RC file, and click :guilabel:`Access & Security`." -msgstr "" - -#: ../common/cli_set_environment_variables_using_openstack_rc.rst:26 -msgid "" -"Log in to the OpenStack dashboard, choose the project for which you want to " -"download the OpenStack RC file, on the :guilabel:`Project` tab, open the :" -"guilabel:`Compute` tab and click :guilabel:`Access & Security`." -msgstr "" - -#: ../common/log_in_dashboard.rst:2 -msgid "Log in to the dashboard" -msgstr "" - -#: ../common/dashboard_customizing.rst:35 -msgid "Logged in banner: 216 x 35" -msgstr "" - -#: ../common/glossary.rst:2173 ../common/glossary.rst:2179 -msgid "Logical Volume Manager (LVM)" -msgstr "" - -#: ../common/get_started_logical_architecture.rst:4 -#: ../common/get_started_logical_architecture.rst:3 -msgid "Logical architecture" -msgstr "" - -#: ../common/glossary.rst:2201 ../common/glossary.rst:2207 -#: ../common/glossary.rst:2196 -msgid "" -"Logical groupings of related code, such as the Block Storage volume manager " -"or network manager." -msgstr "" - -#: ../common/glossary.rst:3366 ../common/glossary.rst:3373 -#: ../common/glossary.rst:3380 ../common/glossary.rst:3388 -#: ../common/glossary.rst:3377 -msgid "Logical subdivision of an IP network." -msgstr "" - -#: ../common/dashboard_customizing.rst:34 -msgid "Login screen: 365 x 50" -msgstr "" - -#: ../common/dashboard_customizing.rst:30 -msgid "Logo and site colors" -msgstr "" - -#: ../common/dashboard_customizing.rst:119 -msgid "Logo link" -msgstr "" - -#: ../common/glossary.rst:127 -msgid "" -"Lower power consumption CPU often found in mobile and embedded devices. " -"Supported by OpenStack." -msgstr "" - -#: ../common/glossary.rst:1353 ../common/glossary.rst:1354 -msgid "" -"MD5 hash of an object within Object Storage, used to ensure data integrity." -msgstr "" - -#: ../common/cli_manage_images.rst:175 -msgid "Makes an image accessible for all the tenants (admin-only by default)." -msgstr "" - -#: ../common/cli_manage_images.rst:3 -msgid "Manage images" -msgstr "" - -#: ../common/cli_manage_volumes.rst:5 -msgid "Manage volumes" -msgstr "" - -#: ../common/get_started_sahara.rst:28 ../common/get_started_sahara.rst:29 -msgid "" -"Managed through REST API with UI available as part of OpenStack dashboard." -msgstr "" - -#: ../common/get_started_object_storage.rst:20 #: ../common/get_started_object_storage.rst:19 +#: ../common/get_started_object_storage.rst:20 +msgid "Account servers (swift-account-server)" +msgstr "" + +#: ../common/get_started_object_storage.rst:19 +#: ../common/get_started_object_storage.rst:20 msgid "Manages accounts defined with Object Storage." msgstr "" +#: ../common/get_started_object_storage.rst:22 +#: ../common/get_started_object_storage.rst:23 +msgid "Container servers (swift-container-server)" +msgstr "" + +#: ../common/get_started_object_storage.rst:22 +#: ../common/get_started_object_storage.rst:23 +msgid "Manages the mapping of containers or folders, within Object Storage." +msgstr "" + #: ../common/get_started_object_storage.rst:25 msgid "Manages actual objects, such as files, on the storage nodes." msgstr "" -#: ../common/get_started_object_storage.rst:26 #: ../common/get_started_object_storage.rst:25 +#: ../common/get_started_object_storage.rst:26 msgid "Manages actual objects,such as files, on the storage nodes." msgstr "" -#: ../common/get_started_with_openstack.rst:35 -#: ../common/get_started_with_openstack.rst:43 -msgid "" -"Manages the lifecycle of compute instances in an OpenStack environment. " -"Responsibilities include spawning, scheduling and decommissioning of virtual " -"machines on demand." -msgstr "" - -#: ../common/get_started_object_storage.rst:23 -#: ../common/get_started_object_storage.rst:22 -msgid "Manages the mapping of containers or folders, within Object Storage." -msgstr "" - -#: ../common/support-compute.rst:99 -msgid "Manual method" -msgstr "" - -#: ../common/cli_install_openstack_command_line_clients.rst:25 -msgid "" -"Many Linux distributions provide packages to make setuptools easy to " -"install. Search your package manager for setuptools to find an installation " -"package. If you cannot find one, download the setuptools package directly " -"from http://pypi.python.org/pypi/setuptools." -msgstr "" - -#: ../common/cli_install_openstack_command_line_clients.rst:25 -msgid "" -"Many Linux distributions provide packages to make setuptools easy to " -"install. Search your package manager for setuptools to find an installation " -"package. If you cannot find one, download the setuptools package directly " -"from https://pypi.python.org/pypi/setuptools." -msgstr "" - -#: ../common/glossary.rst:1067 -msgid "Maps Object Storage partitions to physical storage devices." -msgstr "" - -#: ../common/glossary.rst:635 -msgid "" -"Massively scalable distributed storage system that consists of an object " -"store, block store, and POSIX-compatible distributed file system. Compatible " -"with OpenStack." -msgstr "" - -#: ../common/glossary.rst:2221 ../common/glossary.rst:2227 -#: ../common/glossary.rst:2216 -msgid "" -"Maximum frame or packet size for a particular network medium. Typically 1500 " -"bytes for Ethernet networks." -msgstr "" - -#: ../common/glossary.rst:1146 -msgid "" -"Mechanism for highly-available multi-host routing when using OpenStack " -"Networking (neutron)." -msgstr "" - -#: ../common/glossary.rst:2661 ../common/glossary.rst:2668 -#: ../common/glossary.rst:2674 ../common/glossary.rst:2676 -#: ../common/glossary.rst:2665 -msgid "" -"Mechanism in IP networks to detect end-to-end MTU and adjust packet size " -"accordingly." -msgstr "" - -#: ../common/get_started_compute.rst:58 ../common/get_started_compute.rst:57 -msgid "" -"Mediates interactions between the nova-compute service and the database. It " -"eliminates direct accesses to the cloud database made by the nova-compute " -"service. The nova-conductor module scales horizontally. However, do not " -"deploy it on nodes where the nova-compute service runs. For more " -"information, see `A new Nova service: nova-conductor `__." -msgstr "" - -#: ../common/glossary.rst:2230 -msgid "Meiji" -msgstr "" - -#: ../common/glossary.rst:2469 ../common/glossary.rst:2476 -#: ../common/glossary.rst:2475 ../common/glossary.rst:2481 -#: ../common/glossary.rst:2483 ../common/glossary.rst:2472 -msgid "" -"Message exchange that is cleared when the service restarts. Its data is not " -"written to persistent storage." -msgstr "" - -#: ../common/glossary.rst:3812 ../common/glossary.rst:3819 -#: ../common/glossary.rst:3826 ../common/glossary.rst:3834 -#: ../common/glossary.rst:3823 -msgid "" -"Message queue software supported by OpenStack. An alternative to RabbitMQ. " -"Also spelled 0MQ." -msgstr "" - -#: ../common/glossary.rst:2840 ../common/glossary.rst:2847 -#: ../common/glossary.rst:2854 ../common/glossary.rst:2856 -#: ../common/glossary.rst:2845 -msgid "" -"Message queue software supported by OpenStack; an alternative to RabbitMQ." -msgstr "" - -#: ../common/glossary.rst:2474 ../common/glossary.rst:2481 -#: ../common/glossary.rst:2480 ../common/glossary.rst:2486 -#: ../common/glossary.rst:2488 ../common/glossary.rst:2477 -msgid "" -"Message queue that is cleared when the service restarts. Its data is not " -"written to persistent storage." -msgstr "" - -#: ../common/glossary.rst:2272 ../common/glossary.rst:2279 -#: ../common/glossary.rst:2278 ../common/glossary.rst:2267 -msgid "Message service" -msgstr "" - -#: ../common/get_started_block_storage.rst:36 -#: ../common/get_started_openstack_networking.rst:31 -#: ../common/get_started_block_storage.rst:37 -#: ../common/get_started_block_storage.rst:35 -#: ../common/get_started_openstack_networking.rst:30 -msgid "Messaging queue" -msgstr "" - -#: ../common/glossary.rst:2286 ../common/glossary.rst:2293 -#: ../common/glossary.rst:2292 ../common/glossary.rst:2281 -msgid "Meta-Data Server (MDS)" -msgstr "" - -#: ../common/glossary.rst:2281 ../common/glossary.rst:2288 -#: ../common/glossary.rst:2287 ../common/glossary.rst:2276 -msgid "Metadata agent" -msgstr "" - -#: ../common/glossary.rst:3680 ../common/glossary.rst:3687 -#: ../common/glossary.rst:3694 ../common/glossary.rst:3702 -#: ../common/glossary.rst:3691 -msgid "" -"Method to access VM instance consoles using a web browser. Supported by " -"Compute." -msgstr "" - -#: ../common/get_started_identity.rst:31 -msgid "" -"Middleware modules run in the address space of the OpenStack component that " -"is using the Identity service. These modules intercept service requests, " -"extract user credentials, and send them to the centralized server for " -"authorization. The integration between the middleware modules and OpenStack " -"components uses the Python Web Server Gateway Interface." -msgstr "" - -#: ../common/cli_manage_volumes.rst:13 -msgid "Migrate a volume" -msgstr "" - -#: ../common/cli_manage_volumes.rst:28 -msgid "" -"Migrate a volume with the :command:`cinder migrate` command, as shown in the " -"following example::" -msgstr "" - -#: ../common/support-compute.rst:93 -msgid "" -"Missing credentials cause a ``403 forbidden`` error. To resolve this issue, " -"use one of these methods:" -msgstr "" - -#: ../common/glossary.rst:2299 ../common/glossary.rst:2305 -#: ../common/glossary.rst:2294 -msgid "Mitaka" -msgstr "" - -#: ../common/cli_manage_volumes.rst:24 -msgid "Modify the properties of a volume." -msgstr "" - -#: ../common/glossary.rst:2315 ../common/glossary.rst:2322 -#: ../common/glossary.rst:2321 ../common/glossary.rst:2327 -#: ../common/glossary.rst:2316 -msgid "Modular Layer 2 (ML2) neutron plug-in" -msgstr "" - -#: ../common/glossary.rst:3076 ../common/glossary.rst:3083 -#: ../common/glossary.rst:3090 ../common/glossary.rst:3092 -#: ../common/glossary.rst:3081 -msgid "" -"Modular system that allows the underlying message queue software of Compute " -"to be changed. For example, from RabbitMQ to ZeroMQ or Qpid." -msgstr "" - -#: ../common/get_started_identity.rst:36 -msgid "Modules" -msgstr "" - -#: ../common/glossary.rst:2320 ../common/glossary.rst:2327 -#: ../common/glossary.rst:2326 ../common/glossary.rst:2332 -#: ../common/glossary.rst:2321 -msgid "Monitor (LBaaS)" -msgstr "" - -#: ../common/glossary.rst:2325 ../common/glossary.rst:2332 -#: ../common/glossary.rst:2331 ../common/glossary.rst:2337 -#: ../common/glossary.rst:2326 -msgid "Monitor (Mon)" -msgstr "" - -#: ../common/get_started_with_openstack.rst:68 -#: ../common/get_started_with_openstack.rst:76 -msgid "" -"Monitors and meters the OpenStack cloud for billing, benchmarking, " -"scalability, and statistical purposes." -msgstr "" - -#: ../common/cli_install_openstack_command_line_clients.rst:11 -msgid "" -"Most Linux distributions include packaged versions of the command-line " -"clients that you can install directly, see Installing_from_packages_." -msgstr "" - -#: ../common/get_started_storage_concepts.rst:25 -#: ../common/get_started_storage_concepts.rst:24 -msgid "" -"Mounted via OpenStack Block Storage controlled protocol (for example, iSCSI)" -msgstr "" - -#: ../common/glossary.rst:2336 ../common/glossary.rst:2343 -#: ../common/glossary.rst:2342 ../common/glossary.rst:2348 -#: ../common/glossary.rst:2337 -msgid "MultiNic" -msgstr "" - -#: ../common/glossary.rst:2384 ../common/glossary.rst:2373 -msgid "NAT" -msgstr "" - -#: ../common/glossary.rst:2420 ../common/glossary.rst:2409 -msgid "NTP" -msgstr "" - -#: ../common/glossary.rst:809 -msgid "Name for the Compute component that manages VMs." -msgstr "" - -#: ../common/glossary.rst:2348 ../common/glossary.rst:2355 -#: ../common/glossary.rst:2354 ../common/glossary.rst:2360 -#: ../common/glossary.rst:2349 -msgid "Nebula" -msgstr "" - -#: ../common/glossary.rst:2359 ../common/glossary.rst:2366 -#: ../common/glossary.rst:2365 ../common/glossary.rst:2371 -#: ../common/glossary.rst:2360 -msgid "NetApp volume driver" -msgstr "" - -#: ../common/glossary.rst:2372 ../common/glossary.rst:2379 -#: ../common/glossary.rst:2378 ../common/glossary.rst:2384 -msgid "Network Address Translation (NAT)" -msgstr "" - -#: ../common/glossary.rst:2387 ../common/glossary.rst:2376 -msgid "" -"Network Address Translation; Process of modifying IP address information " -"while in transit. Supported by Compute and Networking." -msgstr "" - -#: ../common/glossary.rst:2383 ../common/glossary.rst:2390 -#: ../common/glossary.rst:2389 ../common/glossary.rst:2395 -#: ../common/glossary.rst:2396 ../common/glossary.rst:2385 -msgid "Network File System (NFS)" -msgstr "" - -#: ../common/glossary.rst:2407 ../common/glossary.rst:2414 -#: ../common/glossary.rst:2413 ../common/glossary.rst:2419 -msgid "Network Time Protocol (NTP)" -msgstr "" - -#: ../common/glossary.rst:2423 ../common/glossary.rst:2412 -msgid "" -"Network Time Protocol; Method of keeping a clock for a host or node correct " -"via communication with a trusted, accurate time source." -msgstr "" - -#: ../common/glossary.rst:2483 ../common/glossary.rst:2490 -#: ../common/glossary.rst:2489 ../common/glossary.rst:2495 -#: ../common/glossary.rst:2497 ../common/glossary.rst:2486 -msgid "" -"Network traffic between a user or client (north) and a server (south), or " -"traffic into the cloud (south) and out of the cloud (north). See also east-" -"west traffic." -msgstr "" - -#: ../common/glossary.rst:1240 ../common/glossary.rst:1241 -msgid "" -"Network traffic between servers in the same cloud or data center. See also " -"north-south traffic." -msgstr "" - -#: ../common/glossary.rst:2422 ../common/cli_overview.rst:52 -#: ../common/glossary.rst:2429 ../common/glossary.rst:2428 -#: ../common/cli_overview.rst:58 ../common/glossary.rst:2434 -#: ../common/cli_overview.rst:61 ../common/glossary.rst:2436 -#: ../common/cli_overview.rst:65 ../common/glossary.rst:2425 -#: ../common/cli_overview.rst:68 -msgid "Networking" -msgstr "" - -#: ../common/glossary.rst:2428 ../common/glossary.rst:2435 -#: ../common/glossary.rst:2434 ../common/glossary.rst:2440 -#: ../common/glossary.rst:2442 ../common/glossary.rst:2431 -msgid "Networking API" -msgstr "" - -#: ../common/glossary.rst:1019 -msgid "" -"New users are assigned to this tenant if no tenant is specified when a user " -"is created." -msgstr "" - -#: ../common/glossary.rst:2453 ../common/glossary.rst:2460 -#: ../common/glossary.rst:2459 ../common/glossary.rst:2465 -#: ../common/glossary.rst:2467 ../common/glossary.rst:2456 -msgid "Nexenta volume driver" -msgstr "" - -#: ../common/support-compute.rst:141 -msgid "" -"Next, check the log file for the instance in the :file:`/var/log/libvirt/" -"qemu` directory to see if it exists and has any useful error messages in it." -msgstr "" - -#: ../common/glossary.rst:2457 ../common/glossary.rst:2464 -#: ../common/glossary.rst:2463 ../common/glossary.rst:2469 -#: ../common/glossary.rst:2471 ../common/glossary.rst:2460 -msgid "No ACK" -msgstr "" - -#: ../common/cli_install_openstack_command_line_clients.rst:83 -msgid "" -"Note that extra dependencies may be required, per operating system, " -"depending on the package being installed, such as is the case with Tempest." -msgstr "" - -#: ../common/cli_manage_volumes.rst:201 -msgid "Note that the volume is now available." -msgstr "" - -#: ../common/cli_manage_volumes.rst:132 -msgid "Note the ID of your volume." -msgstr "" - -#: ../common/conventions.rst:8 -msgid "Notices" -msgstr "" - -#: ../common/conventions.rst:10 -msgid "Notices take these forms:" -msgstr "" - -#: ../common/glossary.rst:2490 ../common/glossary.rst:2497 -#: ../common/glossary.rst:2496 ../common/glossary.rst:2502 -#: ../common/glossary.rst:2504 ../common/glossary.rst:2493 -msgid "Nova API" -msgstr "" - -#: ../common/glossary.rst:1962 ../common/glossary.rst:1968 -msgid "" -"Number that is unique to every computer system on the Internet. Two versions " -"of the Internet Protocol (IP) are in use for addresses: IPv4 and IPv6." -msgstr "" - -#: ../common/glossary.rst:2535 ../common/cli_overview.rst:55 -#: ../common/glossary.rst:2542 ../common/glossary.rst:2541 -#: ../common/cli_overview.rst:61 ../common/glossary.rst:2547 -#: ../common/cli_overview.rst:64 ../common/glossary.rst:2549 -#: ../common/cli_overview.rst:68 ../common/glossary.rst:2538 -#: ../common/cli_overview.rst:71 -msgid "Object Storage" -msgstr "" - -#: ../common/get_started_storage_concepts.rst:14 -#: ../common/get_started_storage_concepts.rst:13 -msgid "Object Storage (swift)" -msgstr "" - -#: ../common/glossary.rst:2541 ../common/glossary.rst:2548 -#: ../common/glossary.rst:2547 ../common/glossary.rst:2553 -#: ../common/glossary.rst:2555 ../common/glossary.rst:2544 -msgid "Object Storage API" -msgstr "" - -#: ../common/glossary.rst:2545 ../common/glossary.rst:2552 -#: ../common/glossary.rst:2551 ../common/glossary.rst:2557 -#: ../common/glossary.rst:2559 ../common/glossary.rst:2548 -msgid "Object Storage Device (OSD)" -msgstr "" - -#: ../common/glossary.rst:1528 ../common/glossary.rst:1529 -msgid "" -"Object Storage middleware that uploads (posts) an image through a form on a " -"web page." -msgstr "" - -#: ../common/get_started_object_storage.rst:26 #: ../common/get_started_object_storage.rst:25 +#: ../common/get_started_object_storage.rst:26 msgid "Object servers (swift-object-server)" msgstr "" -#: ../common/glossary.rst:3096 ../common/glossary.rst:3103 -#: ../common/glossary.rst:3110 ../common/glossary.rst:3112 -#: ../common/glossary.rst:3101 +#: ../common/get_started_object_storage.rst:28 +#: ../common/get_started_object_storage.rst:29 msgid "" -"Object storage service by Amazon; similar in function to Object Storage, it " -"can act as a back-end store for Image service VM images." +"Performs housekeeping tasks on the large data store. The replication " +"services ensure consistency and availability through the cluster. Other " +"periodic processes include auditors, updaters, and reapers." msgstr "" -#: ../common/glossary.rst:2554 ../common/glossary.rst:2561 -#: ../common/glossary.rst:2560 ../common/glossary.rst:2566 -#: ../common/glossary.rst:2568 ../common/glossary.rst:2557 -msgid "Oldie" +#: ../common/get_started_object_storage.rst:30 +#: ../common/get_started_object_storage.rst:31 +msgid "Various periodic processes" msgstr "" -#: ../common/dashboard_customizing.rst:98 -msgid "On Fedora, RHEL, CentOS::" +#: ../common/get_started_object_storage.rst:32 +#: ../common/get_started_object_storage.rst:33 +#: ../common/get_started_object_storage.rst:34 +msgid "WSGI middleware" msgstr "" -#: ../common/cli_install_openstack_command_line_clients.rst:207 -#: ../common/cli_install_openstack_command_line_clients.rst:213 -#: ../common/cli_install_openstack_command_line_clients.rst:215 -#: ../common/cli_install_openstack_command_line_clients.rst:217 -#: ../common/cli_install_openstack_command_line_clients.rst:219 +#: ../common/get_started_object_storage.rst:33 +#: ../common/get_started_object_storage.rst:34 +msgid "Handles authentication and is usually OpenStack Identity." +msgstr "" + +#: ../common/get_started_object_storage.rst:36 +#: ../common/get_started_storage_concepts.rst:54 +#: ../common/get_started_storage_concepts.rst:56 +#: ../common/get_started_storage_concepts.rst:57 msgid "" -"On Red Hat Enterprise Linux, CentOS, or Fedora, use ``yum`` to install the " -"clients from the packaged versions available in `RDO `__::" +"Enables users to submit commands to the REST API through a command-line " +"client authorized as either a admin user, reseller user, or swift user." msgstr "" -#: ../common/dashboard_customizing.rst:94 -msgid "On Ubuntu::" +#: ../common/get_started_object_storage.rst:38 +#: ../common/get_started_storage_concepts.rst:56 +#: ../common/get_started_storage_concepts.rst:58 +#: ../common/get_started_storage_concepts.rst:59 +msgid "swift client" msgstr "" -#: ../common/cli_set_environment_variables_using_openstack_rc.rst:40 -#: ../common/cli_set_environment_variables_using_openstack_rc.rst:41 +#: ../common/get_started_object_storage.rst:41 +#: ../common/get_started_storage_concepts.rst:59 +#: ../common/get_started_storage_concepts.rst:61 +#: ../common/get_started_storage_concepts.rst:62 msgid "" -"On any shell from which you want to run OpenStack commands, source the :file:" -"`PROJECT-openrc.sh` file for the respective project." +"Script that initializes the building of the ring file, takes daemon names as " +"parameter and offers commands. Documented in http://docs.openstack.org/" +"developer/swift/admin_guide.html#managing-services." msgstr "" -#: ../common/cli_set_environment_variables_using_openstack_rc.rst:69 -#: ../common/cli_set_environment_variables_using_openstack_rc.rst:70 +#: ../common/get_started_object_storage.rst:43 +#: ../common/get_started_storage_concepts.rst:61 +#: ../common/get_started_storage_concepts.rst:63 +#: ../common/get_started_storage_concepts.rst:64 +msgid "swift-init" +msgstr "" + +#: ../common/get_started_object_storage.rst:46 +#: ../common/get_started_storage_concepts.rst:64 +#: ../common/get_started_storage_concepts.rst:66 +#: ../common/get_started_storage_concepts.rst:67 msgid "" -"On any shell from which you want to run OpenStack commands, source the :file:" -"`PROJECT-openrc.sh` file for the respective project. In this example, you " -"source the :file:`admin-openrc.sh` file for the admin project::" +"A cli tool used to retrieve various metrics and telemetry information about " +"a cluster, that has been collected by the swift-recon middleware." msgstr "" -#: ../common/dashboard_customizing.rst:102 -msgid "On openSUSE::" +#: ../common/get_started_object_storage.rst:47 +#: ../common/get_started_storage_concepts.rst:65 +#: ../common/get_started_storage_concepts.rst:67 +#: ../common/get_started_storage_concepts.rst:68 +msgid "swift-recon" msgstr "" -#: ../common/cli_set_environment_variables_using_openstack_rc.rst:30 +#: ../common/get_started_object_storage.rst:50 +#: ../common/get_started_storage_concepts.rst:68 +#: ../common/get_started_storage_concepts.rst:70 +#: ../common/get_started_storage_concepts.rst:71 msgid "" -"On the :guilabel:`API Access` tab, click :guilabel:`Download OpenStack RC " -"File` and save the file. The filename will be of the form :file:`PROJECT-" -"openrc.sh` where ``PROJECT`` is the name of the project for which you " -"downloaded the file." +"Storage ring build and rebalance utility. Documented in http://docs." +"openstack.org/developer/swift/admin_guide.html#managing-the-rings." msgstr "" -#: ../common/cli_set_environment_variables_using_openstack_rc.rst:29 -msgid "" -"On the API Access tab, click :guilabel:`Download OpenStack RC File` and save " -"the file. The filename will be of the form :file:`PROJECT-openrc.sh` where " -"``PROJECT`` is the name of the project for which you downloaded the file." +#: ../common/get_started_object_storage.rst:50 +#: ../common/get_started_storage_concepts.rst:68 +#: ../common/get_started_storage_concepts.rst:69 +#: ../common/get_started_storage_concepts.rst:70 +#: ../common/get_started_storage_concepts.rst:71 +#: ../common/get_started_storage_concepts.rst:72 +msgid "swift-ring-builder" msgstr "" -#: ../common/log_in_dashboard.rst:36 -msgid "" -"On the Log In page, enter your user name and password, and click :guilabel:" -"`Sign In`." -msgstr "" - -#: ../common/get_started_storage_concepts.rst:12 -#: ../common/get_started_storage_concepts.rst:11 -msgid "On-instance / ephemeral" -msgstr "" - -#: ../common/dashboard_customizing.rst:10 -msgid "" -"Once you have the dashboard installed you can customize the way it looks and " -"feels to suit your own needs." -msgstr "" - -#: ../common/glossary.rst:591 -msgid "" -"One of the RPC primitives used by the OpenStack message queue software. " -"Sends a message and does not wait for a response." -msgstr "" - -#: ../common/glossary.rst:569 -msgid "" -"One of the RPC primitives used by the OpenStack message queue software. " -"Sends a message and waits for a response." -msgstr "" - -#: ../common/glossary.rst:2017 ../common/glossary.rst:2835 -#: ../common/glossary.rst:3578 ../common/glossary.rst:3590 -#: ../common/glossary.rst:3671 ../common/glossary.rst:2842 -#: ../common/glossary.rst:3585 ../common/glossary.rst:3597 -#: ../common/glossary.rst:3678 ../common/glossary.rst:2023 -#: ../common/glossary.rst:2849 ../common/glossary.rst:3592 -#: ../common/glossary.rst:3604 ../common/glossary.rst:3685 -#: ../common/glossary.rst:2851 ../common/glossary.rst:3600 -#: ../common/glossary.rst:3612 ../common/glossary.rst:3693 -#: ../common/glossary.rst:2840 ../common/glossary.rst:3589 -#: ../common/glossary.rst:3601 ../common/glossary.rst:3682 -msgid "One of the VM image disk formats supported by Image service." -msgstr "" - -#: ../common/glossary.rst:2904 ../common/glossary.rst:2911 -#: ../common/glossary.rst:2918 ../common/glossary.rst:2920 -#: ../common/glossary.rst:2909 -msgid "" -"One of the VM image disk formats supported by Image service; an unstructured " -"disk image." -msgstr "" - -#: ../common/glossary.rst:1062 -msgid "" -"One of the default roles in the Compute RBAC system and the default role " -"assigned to a new user." -msgstr "" - -#: ../common/glossary.rst:3419 ../common/glossary.rst:3426 -#: ../common/glossary.rst:3433 ../common/glossary.rst:3441 -#: ../common/glossary.rst:3430 -msgid "" -"One of the default roles in the Compute RBAC system. Enables a user to add " -"other users to a project, interact with VM images that are associated with " -"the project, and start and stop VM instances." -msgstr "" - -#: ../common/glossary.rst:2356 ../common/glossary.rst:2363 -#: ../common/glossary.rst:2362 ../common/glossary.rst:2368 -#: ../common/glossary.rst:2357 -msgid "" -"One of the default roles in the Compute RBAC system. Enables the user to " -"allocate publicly accessible IP addresses to instances and change firewall " -"rules." -msgstr "" - -#: ../common/glossary.rst:735 -msgid "" -"One of the default roles in the Compute RBAC system. Grants complete system " -"access." -msgstr "" - -#: ../common/glossary.rst:1718 ../common/glossary.rst:1724 -msgid "One of the hypervisors supported by OpenStack." -msgstr "" - -#: ../common/glossary.rst:2036 ../common/glossary.rst:2042 -msgid "One of the supported response formats in OpenStack." -msgstr "" - -#: ../common/glossary.rst:2559 ../common/glossary.rst:2566 -#: ../common/glossary.rst:2565 ../common/glossary.rst:2571 -#: ../common/glossary.rst:2573 ../common/glossary.rst:2562 -msgid "Open Cloud Computing Interface (OCCI)" -msgstr "" - -#: ../common/glossary.rst:2564 ../common/glossary.rst:2571 -#: ../common/glossary.rst:2570 ../common/glossary.rst:2576 -#: ../common/glossary.rst:2578 ../common/glossary.rst:2567 -msgid "Open Virtualization Format (OVF)" -msgstr "" - -#: ../common/log_in_dashboard.rst:11 -msgid "Open a web browser that has JavaScript and cookies enabled." -msgstr "" - -#: ../common/glossary.rst:3619 ../common/glossary.rst:3626 -#: ../common/glossary.rst:3633 ../common/glossary.rst:3641 -#: ../common/glossary.rst:3630 -msgid "" -"Open source GUI and CLI tools used for remote console access to VMs. " -"Supported by Compute." -msgstr "" - -#: ../common/glossary.rst:3132 ../common/glossary.rst:3139 -#: ../common/glossary.rst:3146 ../common/glossary.rst:3148 -#: ../common/glossary.rst:3137 -msgid "" -"Open source tool used to access remote hosts through an encrypted " -"communications channel, SSH key injection is supported by Compute." -msgstr "" - -#: ../common/dashboard_customizing.rst:81 -msgid "Open the following HTML template in an editor of your choice::" -msgstr "" - -#: ../common/glossary.rst:2568 ../common/glossary.rst:2575 -#: ../common/glossary.rst:2574 ../common/glossary.rst:2580 -#: ../common/glossary.rst:2582 ../common/glossary.rst:2571 -msgid "Open vSwitch" -msgstr "" - -#: ../common/glossary.rst:2577 ../common/glossary.rst:2584 -#: ../common/glossary.rst:2583 ../common/glossary.rst:2589 -#: ../common/glossary.rst:2591 ../common/glossary.rst:2580 -msgid "Open vSwitch (OVS) agent" -msgstr "" - -#: ../common/glossary.rst:2571 ../common/glossary.rst:2578 -#: ../common/glossary.rst:2577 ../common/glossary.rst:2583 -#: ../common/glossary.rst:2585 ../common/glossary.rst:2574 -msgid "" -"Open vSwitch is a production quality, multilayer virtual switch licensed " -"under the open source Apache 2.0 license. It is designed to enable massive " -"network automation through programmatic extension, while still supporting " -"standard management interfaces and protocols (for example NetFlow, sFlow, " -"SPAN, RSPAN, CLI, LACP, 802.1ag)." -msgstr "" - -#: ../common/glossary.rst:2582 ../common/glossary.rst:2589 -#: ../common/glossary.rst:2588 ../common/glossary.rst:2594 -#: ../common/glossary.rst:2596 ../common/glossary.rst:2585 -msgid "Open vSwitch neutron plug-in" -msgstr "" - -#: ../common/glossary.rst:2586 ../common/glossary.rst:2593 -#: ../common/glossary.rst:2592 ../common/glossary.rst:2598 -#: ../common/glossary.rst:2600 ../common/glossary.rst:2589 -msgid "OpenLDAP" -msgstr "" - -#: ../common/glossary.rst:2591 ../common/glossary.rst:2598 -#: ../common/glossary.rst:2597 ../common/glossary.rst:2603 -#: ../common/glossary.rst:2605 ../common/glossary.rst:2594 -msgid "OpenStack" -msgstr "" - -#: ../common/cli_overview.rst:18 -msgid "" -"OpenStack APIs are open-source Python clients, and can run on Linux or Mac " -"OS X systems. On some client commands, you can specify a debug parameter to " -"show the underlying API request for the command. This is a good way to " -"become familiar with the OpenStack API calls." -msgstr "" - -#: ../common/get_started_block_storage.rst:4 -#: ../common/get_started_block_storage.rst:3 -msgid "OpenStack Block Storage" -msgstr "" - -#: ../common/get_started_compute.rst:4 ../common/get_started_compute.rst:3 -msgid "OpenStack Compute" -msgstr "" - -#: ../common/get_started_compute.rst:18 ../common/get_started_compute.rst:17 -msgid "OpenStack Compute consists of the following areas and their components:" -msgstr "" - -#: ../common/get_started_compute.rst:10 -msgid "" -"OpenStack Compute interacts with OpenStack Identity for authentication, " -"OpenStack Image Service for disk and server images, and OpenStack dashboard " -"for the user and administrative interface. Image access is limited by " -"projects, and by users; quotas are limited per project (the number of " -"instances, for example). OpenStack Compute can scale horizontally on " -"standard hardware, and download images to launch instances." -msgstr "" - -#: ../common/get_started_compute.rst:10 ../common/get_started_compute.rst:9 -msgid "" -"OpenStack Compute interacts with OpenStack Identity for authentication, " -"OpenStack Image service for disk and server images, and OpenStack dashboard " -"for the user and administrative interface. Image access is limited by " -"projects, and by users; quotas are limited per project (the number of " -"instances, for example). OpenStack Compute can scale horizontally on " -"standard hardware, and download images to launch instances." -msgstr "" - -#: ../common/get_started_sahara.rst:4 ../common/get_started_sahara.rst:5 -msgid "OpenStack Data processing service" -msgstr "" - -#: ../common/get_started_database_service.rst:4 -#: ../common/get_started_database_service.rst:3 -msgid "OpenStack Database service" -msgstr "" - -#: ../common/get_started_identity.rst:4 ../common/get_started_identity.rst:3 -msgid "OpenStack Identity" -msgstr "" - -#: ../common/get_started_identity.rst:4 -msgid "OpenStack Identity concepts" -msgstr "" - -#: ../common/get_started_image_service.rst:4 -msgid "OpenStack Image Service" -msgstr "" - -#: ../common/get_started_image_service.rst:4 -#: ../common/get_started_image_service.rst:3 -msgid "OpenStack Image service" -msgstr "" - -#: ../common/get_started_openstack_networking.rst:4 #: ../common/get_started_openstack_networking.rst:3 +#: ../common/get_started_openstack_networking.rst:4 msgid "OpenStack Networking" msgstr "" -#: ../common/get_started_openstack_networking.rst:6 #: ../common/get_started_openstack_networking.rst:5 +#: ../common/get_started_openstack_networking.rst:6 msgid "" "OpenStack Networking (neutron) allows you to create and attach interface " "devices managed by other OpenStack services to networks. Plug-ins can be " @@ -6509,440 +3847,20 @@ msgid "" "providing flexibility to OpenStack architecture and deployment." msgstr "" -#: ../common/glossary.rst:1091 +#: ../common/get_started_openstack_networking.rst:13 +#: ../common/get_started_openstack_networking.rst:14 msgid "" -"OpenStack Networking agent that provides DHCP services for virtual networks." +"Accepts and routes API requests to the appropriate OpenStack Networking plug-" +"in for action." msgstr "" -#: ../common/glossary.rst:2117 ../common/glossary.rst:2123 -msgid "" -"OpenStack Networking agent that provides layer-2 connectivity for virtual " -"networks." +#: ../common/get_started_openstack_networking.rst:14 +#: ../common/get_started_openstack_networking.rst:15 +msgid "neutron-server" msgstr "" -#: ../common/glossary.rst:2122 ../common/glossary.rst:2128 -msgid "" -"OpenStack Networking agent that provides layer-3 (routing) services for " -"virtual networks." -msgstr "" - -#: ../common/glossary.rst:2284 ../common/glossary.rst:2291 -#: ../common/glossary.rst:2290 ../common/glossary.rst:2279 -msgid "" -"OpenStack Networking agent that provides metadata services for instances." -msgstr "" - -#: ../common/get_started_openstack_networking.rst:33 -#: ../common/get_started_openstack_networking.rst:32 -msgid "" -"OpenStack Networking mainly interacts with OpenStack Compute to provide " -"networks and connectivity for its instances." -msgstr "" - -#: ../common/get_started_openstack_networking.rst:26 -#: ../common/get_started_openstack_networking.rst:25 -msgid "OpenStack Networking plug-ins and agents" -msgstr "" - -#: ../common/get_started_object_storage.rst:4 -#: ../common/get_started_object_storage.rst:3 -msgid "OpenStack Object Storage" -msgstr "" - -#: ../common/get_started_orchestration.rst:4 -#: ../common/get_started_orchestration.rst:3 -msgid "OpenStack Orchestration module" -msgstr "" - -#: ../common/get_started_with_openstack.rst:0 -msgid "OpenStack Services" -msgstr "" - -#: ../common/get_started_telemetry.rst:4 ../common/get_started_telemetry.rst:3 -msgid "OpenStack Telemetry module" -msgstr "" - -#: ../common/glossary.rst:2600 ../common/glossary.rst:2607 -#: ../common/glossary.rst:2606 ../common/glossary.rst:2612 -#: ../common/glossary.rst:2614 ../common/glossary.rst:2603 -msgid "OpenStack code name" -msgstr "" - -#: ../common/get_started_dashboard.rst:4 ../common/get_started_dashboard.rst:5 -msgid "OpenStack dashboard" -msgstr "" - -#: ../common/log_in_dashboard.rst:134 ../common/log_in_dashboard.rst:137 -#: ../common/log_in_dashboard.rst:133 ../common/log_in_dashboard.rst:135 -msgid "OpenStack dashboard—:guilabel:`Admin` tab" -msgstr "" - -#: ../common/log_in_dashboard.rst:204 ../common/log_in_dashboard.rst:210 -#: ../common/log_in_dashboard.rst:209 ../common/log_in_dashboard.rst:213 -msgid "OpenStack dashboard—:guilabel:`Identity` tab" -msgstr "" - -#: ../common/log_in_dashboard.rst:56 ../common/log_in_dashboard.rst:58 -msgid "OpenStack dashboard—:guilabel:`Project` tab" -msgstr "" - -#: ../common/log_in_dashboard.rst:212 ../common/log_in_dashboard.rst:218 -#: ../common/log_in_dashboard.rst:217 ../common/log_in_dashboard.rst:221 -msgid "OpenStack dashboard—:guilabel:`Settings` tab" -msgstr "" - -#: ../common/app_support.rst:226 ../common/app_support.rst:223 -#: ../common/app_support.rst:221 ../common/app_support.rst:227 -#: ../common/app_support.rst:229 ../common/app_support.rst:232 -#: ../common/app_support.rst:234 -msgid "OpenStack distribution packages" -msgstr "" - -#: ../common/glossary.rst:2594 ../common/glossary.rst:2601 -#: ../common/glossary.rst:2600 ../common/glossary.rst:2606 -#: ../common/glossary.rst:2608 ../common/glossary.rst:2597 -msgid "" -"OpenStack is a cloud operating system that controls large pools of compute, " -"storage, and networking resources throughout a data center, all managed " -"through a dashboard that gives administrators control while empowering their " -"users to provision resources through a web interface. OpenStack is an open " -"source project licensed under the Apache License 2.0." -msgstr "" - -#: ../common/app_support.rst:105 ../common/app_support.rst:102 -#: ../common/app_support.rst:100 -msgid "OpenStack mailing lists" -msgstr "" - -#: ../common/glossary.rst:2275 ../common/glossary.rst:2282 -#: ../common/glossary.rst:2281 ../common/glossary.rst:2270 -msgid "" -"OpenStack project that aims to produce an OpenStack messaging service that " -"affords a variety of distributed application patterns in an efficient, " -"scalable and highly-available manner, and to create and maintain associated " -"Python libraries and documentation. The code name for the project is zaqar." -msgstr "" - -#: ../common/glossary.rst:2065 ../common/glossary.rst:2071 -msgid "" -"OpenStack project that produces a secret storage and generation system " -"capable of providing key management for services wishing to enable " -"encryption features. The code name of the project is barbican." -msgstr "" - -#: ../common/glossary.rst:2634 ../common/glossary.rst:2641 -#: ../common/glossary.rst:2647 ../common/glossary.rst:2649 -#: ../common/glossary.rst:2638 -msgid "" -"OpenStack project that produces a set of Python libraries containing code " -"shared by OpenStack projects." -msgstr "" - -#: ../common/glossary.rst:2182 ../common/glossary.rst:2188 -msgid "" -"OpenStack project that provides a Key-Value Store as a Service for OpenStack " -"users." -msgstr "" - -#: ../common/glossary.rst:1667 ../common/glossary.rst:1673 -msgid "OpenStack project that provides a dashboard, which is a web interface." -msgstr "" - -#: ../common/glossary.rst:422 -msgid "" -"OpenStack project that provides a framework for performance analysis and " -"benchmarking of individual OpenStack components as well as full production " -"OpenStack cloud deployments. The code name of the project is rally." -msgstr "" - -#: ../common/glossary.rst:2072 ../common/glossary.rst:2078 -msgid "" -"OpenStack project that provides a key-value store for applications running " -"in an OpenStack cloud. The code name for the project is magnetoDB." -msgstr "" - -#: ../common/glossary.rst:3807 ../common/glossary.rst:3814 -#: ../common/glossary.rst:3821 ../common/glossary.rst:3829 -#: ../common/glossary.rst:3818 -msgid "OpenStack project that provides a message service to applications." -msgstr "" - -#: ../common/glossary.rst:3101 ../common/glossary.rst:3108 -#: ../common/glossary.rst:3115 ../common/glossary.rst:3117 -#: ../common/glossary.rst:3106 -msgid "" -"OpenStack project that provides a scalable data-processing stack and " -"associated management interfaces." -msgstr "" - -#: ../common/glossary.rst:992 -msgid "" -"OpenStack project that provides a scalable data-processing stack and " -"associated management interfaces. The code name for the project is sahara." -msgstr "" - -#: ../common/glossary.rst:868 -msgid "" -"OpenStack project that provides a set of services for management of " -"application containers in a multi-tenant cloud environment. The code name of " -"the project name is magnum." -msgstr "" - -#: ../common/glossary.rst:3768 ../common/glossary.rst:3775 -#: ../common/glossary.rst:3782 ../common/glossary.rst:3790 -#: ../common/glossary.rst:3779 -msgid "" -"OpenStack project that provides a simple YAML-based language to write " -"workflows, tasks and transition rules, and a service that allows to upload " -"them, modify, run them at scale and in a highly available manner, manage and " -"monitor workflow execution state and state of individual tasks. The code " -"name of the project is mistral." -msgstr "" - -#: ../common/glossary.rst:2314 ../common/glossary.rst:2321 -#: ../common/glossary.rst:2320 ../common/glossary.rst:2326 -#: ../common/glossary.rst:2315 -msgid "OpenStack project that provides an Application catalog." -msgstr "" - -#: ../common/glossary.rst:230 -msgid "" -"OpenStack project that provides an application catalog service so that users " -"can compose and deploy composite environments on an application abstraction " -"level while managing the application lifecycle. The code name of the project " -"is murano." -msgstr "" - -#: ../common/glossary.rst:2489 ../common/glossary.rst:2496 -#: ../common/glossary.rst:2495 ../common/glossary.rst:2501 -#: ../common/glossary.rst:2503 ../common/glossary.rst:2492 -msgid "OpenStack project that provides compute services." -msgstr "" - -#: ../common/glossary.rst:3525 ../common/glossary.rst:3532 -#: ../common/glossary.rst:3539 ../common/glossary.rst:3547 -#: ../common/glossary.rst:3536 -msgid "OpenStack project that provides database services to applications." -msgstr "" - -#: ../common/glossary.rst:1167 -msgid "" -"OpenStack project that provides scalable, on demand, self service access to " -"authoritative DNS services, in a technology-agnostic manner. The code name " -"for the project is designate." -msgstr "" - -#: ../common/glossary.rst:2216 ../common/glossary.rst:2222 -#: ../common/glossary.rst:2211 -msgid "" -"OpenStack project that provides shared file systems as service to " -"applications." -msgstr "" - -#: ../common/glossary.rst:2883 ../common/glossary.rst:2890 -#: ../common/glossary.rst:2897 ../common/glossary.rst:2899 -#: ../common/glossary.rst:2888 -msgid "OpenStack project that provides the Benchmark service." -msgstr "" - -#: ../common/glossary.rst:759 -msgid "OpenStack project that provides the Governance service." -msgstr "" - -#: ../common/glossary.rst:2298 ../common/glossary.rst:2305 -#: ../common/glossary.rst:2304 ../common/glossary.rst:2293 -msgid "OpenStack project that provides the Workflow service." -msgstr "" - -#: ../common/glossary.rst:1950 ../common/glossary.rst:1956 -msgid "" -"OpenStack project that provisions bare metal, as opposed to virtual, " -"machines." -msgstr "" - -#: ../common/glossary.rst:404 -msgid "" -"OpenStack project that provisions bare metal, as opposed to virtual, " -"machines. The code name for the project is ironic." -msgstr "" - -#: ../common/glossary.rst:1584 ../common/glossary.rst:1585 -msgid "" -"OpenStack project to provide governance as a service across any collection " -"of cloud services in order to monitor, enforce, and audit policy over " -"dynamic infrastructure. The code name for the project is congress." -msgstr "" - -#: ../common/get_started_with_openstack.rst:12 -#: ../common/get_started_with_openstack.rst:20 -msgid "" -"OpenStack provides an Infrastructure-as-a-Service (IaaS) solution through a " -"set of interrelated services. Each service offers an application programming " -"interface (API) that facilitates this integration. Depending on your needs, " -"you can install some or all services." -msgstr "" - -#: ../common/get_started_with_openstack.rst:96 -#: ../common/get_started_openstack_services.rst:3 -msgid "OpenStack services" -msgstr "" - -#: ../common/glossary.rst:1266 ../common/glossary.rst:1267 -msgid "OpenStack supports accessing the Amazon EC2 API through Compute." -msgstr "" - -#: ../common/glossary.rst:1285 ../common/glossary.rst:1286 -msgid "" -"OpenStack supports encryption technologies such as HTTPS, SSH, SSL, TLS, " -"digital certificates, and data encryption." -msgstr "" - -#: ../common/glossary.rst:3520 ../common/glossary.rst:3527 -#: ../common/glossary.rst:3534 ../common/glossary.rst:3542 -#: ../common/glossary.rst:3531 -msgid "" -"OpenStack-on-OpenStack program. The code name for the OpenStack Deployment " -"program." -msgstr "" - -#: ../common/glossary.rst:2508 ../common/glossary.rst:2515 -#: ../common/glossary.rst:2514 ../common/glossary.rst:2520 -#: ../common/glossary.rst:2522 ../common/glossary.rst:2511 -msgid "" -"Opens all objects for an object server and verifies the MD5 hash, size, and " -"metadata for each object." -msgstr "" - -#: ../common/cli_manage_volumes.rst:318 -msgid "" -"Optionally, you can specify a name for the transfer by using the ``--display-" -"name displayName`` parameter." -msgstr "" - -#: ../common/get_started_with_openstack.rst:72 -#: ../common/get_started_with_openstack.rst:80 -msgid "" -"Orchestrates multiple composite cloud applications by using either the " -"native HOT template format or the AWS CloudFormation template format, " -"through both an OpenStack-native REST API and a CloudFormation-compatible " -"Query API." -msgstr "" - -#: ../common/get_started_orchestration.rst:34 -#: ../common/get_started_orchestration.rst:33 -msgid "" -"Orchestrates the launching of templates and provides events back to the API " -"consumer." -msgstr "" - -#: ../common/glossary.rst:2620 ../common/cli_overview.rst:65 -#: ../common/glossary.rst:2627 ../common/cli_overview.rst:71 -#: ../common/glossary.rst:2633 ../common/cli_overview.rst:74 -#: ../common/glossary.rst:2635 ../common/cli_overview.rst:78 -#: ../common/glossary.rst:2624 ../common/cli_overview.rst:81 -msgid "Orchestration" -msgstr "" - -#: ../common/get_started_orchestration.rst:4 -msgid "Orchestration module concepts" -msgstr "" - -#: ../common/glossary.rst:840 -msgid "" -"Organizes and stores objects in Object Storage. Similar to the concept of a " -"Linux directory but cannot be nested. Alternative term for an Image service " -"container format." -msgstr "" - -#: ../common/glossary.rst:2631 ../common/glossary.rst:2638 -#: ../common/glossary.rst:2644 ../common/glossary.rst:2646 -#: ../common/glossary.rst:2635 -msgid "Oslo" -msgstr "" - -#: ../common/cli_set_environment_variables_using_openstack_rc.rst:94 -#: ../common/cli_set_environment_variables_using_openstack_rc.rst:95 -msgid "Override environment variable values" -msgstr "" - -#: ../common/cli_overview.rst:3 -msgid "Overview" -msgstr "" - -#: ../common/glossary.rst:2668 ../common/glossary.rst:2675 -#: ../common/glossary.rst:2681 ../common/glossary.rst:2683 -#: ../common/glossary.rst:2672 -msgid "PCI passthrough" -msgstr "" - -#: ../common/cli_overview.rst:32 -msgid "Package" -msgstr "" - -#: ../common/support-compute.rst:65 -msgid "" -"Package: Displays information about the package to which the process " -"belongs, including version information." -msgstr "" - -#: ../common/glossary.rst:1234 ../common/glossary.rst:1235 -msgid "" -"Pages that use HTML, JavaScript, and Cascading Style Sheets to enable users " -"to interact with a web page or show simple animation." -msgstr "" - -#: ../common/glossary.rst:210 -msgid "" -"Passed to API requests and used by OpenStack to verify that the client is " -"authorized to run the requested operation." -msgstr "" - -#: ../common/glossary.rst:2270 ../common/glossary.rst:2277 -#: ../common/glossary.rst:2276 ../common/glossary.rst:2265 -msgid "" -"Passes requests from clients to the appropriate workers and returns the " -"output to the client after the job completes." -msgstr "" - -#: ../common/get_started_object_storage.rst:29 -#: ../common/get_started_object_storage.rst:28 -msgid "" -"Performs housekeeping tasks on the large data store. The replication " -"services ensure consistency and availability through the cluster. Other " -"periodic processes include auditors, updaters, and reapers." -msgstr "" - -#: ../common/get_started_storage_concepts.rst:18 -#: ../common/get_started_storage_concepts.rst:17 -msgid "Persists until VM is terminated" -msgstr "" - -#: ../common/get_started_storage_concepts.rst:19 -#: ../common/get_started_storage_concepts.rst:20 -#: ../common/get_started_storage_concepts.rst:18 -msgid "Persists until deleted" -msgstr "" - -#: ../common/glossary.rst:799 -msgid "Physical host dedicated to running compute nodes." -msgstr "" - -#: ../common/cli_overview.rst:54 -msgid "Plan Deployments." -msgstr "" - -#: ../common/glossary.rst:2687 ../common/glossary.rst:2694 -#: ../common/glossary.rst:2700 ../common/glossary.rst:2702 -#: ../common/glossary.rst:2691 -msgid "Platform-as-a-Service (PaaS)" -msgstr "" - -#: ../common/get_started_sahara.rst:33 ../common/get_started_sahara.rst:34 -msgid "Pluggable system of Hadoop installation engines." -msgstr "" - -#: ../common/get_started_openstack_networking.rst:18 #: ../common/get_started_openstack_networking.rst:17 +#: ../common/get_started_openstack_networking.rst:18 msgid "" "Plugs and unplugs ports, creates networks or subnets, and provides IP " "addressing. These plug-ins and agents differ depending on the vendor and " @@ -6951,1501 +3869,50 @@ msgid "" "products, Open vSwitch, Linux bridging, and the VMware NSX product." msgstr "" -#: ../common/glossary.rst:3414 ../common/glossary.rst:3421 -#: ../common/glossary.rst:3428 ../common/glossary.rst:3436 -#: ../common/glossary.rst:3425 +#: ../common/get_started_openstack_networking.rst:24 +#: ../common/get_started_openstack_networking.rst:25 msgid "" -"Point in time since the last container and accounts database sync among " -"nodes within Object Storage." +"The common agents are L3 (layer 3), DHCP (dynamic host IP addressing), and a " +"plug-in agent." msgstr "" -#: ../common/cli_manage_volumes.rst:19 -msgid "Possible use cases for data migration include:" +#: ../common/get_started_openstack_networking.rst:25 +#: ../common/get_started_openstack_networking.rst:26 +msgid "OpenStack Networking plug-ins and agents" msgstr "" -#: ../common/get_started_sahara.rst:38 ../common/get_started_sahara.rst:39 +#: ../common/get_started_openstack_networking.rst:28 +#: ../common/get_started_openstack_networking.rst:29 msgid "" -"Predefined templates of Hadoop configurations with the ability to modify " -"parameters." +"Used by most OpenStack Networking installations to route information between " +"the neutron-server and various agents, as well as a database to store " +"networking state for particular plug-ins." msgstr "" -#: ../common/cli_install_openstack_command_line_clients.rst:19 -msgid "Prerequisite" -msgstr "" - -#: ../common/cli_manage_images.rst:179 -msgid "Prevents an image from being deleted." -msgstr "" - -#: ../common/glossary.rst:1935 ../common/glossary.rst:1941 -msgid "" -"Principal communications protocol in the internet protocol suite for " -"relaying datagrams across network boundaries." -msgstr "" - -#: ../common/cli_manage_images.rst:191 -msgid "Prints the image size in a human-friendly format." -msgstr "" - -#: ../common/glossary.rst:1558 ../common/glossary.rst:1559 -msgid "" -"Processes client requests for VMs, updates Image service metadata on the " -"registry server, and communicates with the store adapter to upload VM images " -"from the back-end store." -msgstr "" - -#: ../common/get_started_compute.rst:49 ../common/get_started_compute.rst:48 -msgid "" -"Processing is fairly complex. Basically, the daemon accepts actions from the " -"queue and performs a series of system commands such as launching a KVM " -"instance and updating its state in the database." -msgstr "" - -#: ../common/glossary.rst:2831 ../common/glossary.rst:2838 -#: ../common/glossary.rst:2845 ../common/glossary.rst:2847 -#: ../common/glossary.rst:2836 -msgid "Programming language used extensively in OpenStack." -msgstr "" - -#: ../common/get_started_with_openstack.rst:26 -#: ../common/get_started_with_openstack.rst:34 -msgid "Project name" -msgstr "" - -#: ../common/glossary.rst:2233 ../common/glossary.rst:2240 -#: ../common/glossary.rst:2239 ../common/glossary.rst:2228 -msgid "" -"Project name for OpenStack Network Information Service. To be merged with " -"Networking." -msgstr "" - -#: ../common/get_started_compute.rst:141 ../common/get_started_compute.rst:140 -msgid "Projects" -msgstr "" - -#: ../common/log_in_dashboard.rst:58 ../common/log_in_dashboard.rst:60 -msgid "" -"Projects are organizational units in the cloud, and are also known as " -"tenants or accounts. Each user is a member of one or more projects. Within a " -"project, a user creates and manages instances." -msgstr "" - -#: ../common/glossary.rst:2769 ../common/glossary.rst:2771 -#: ../common/glossary.rst:2760 -msgid "" -"Projects represent the base unit of “ownership” in OpenStack, in that all " -"resources in OpenStack should be owned by a specific project. In OpenStack " -"Identity, a project must be owned by a specific domain." -msgstr "" - -#: ../common/glossary.rst:1549 ../common/glossary.rst:1550 -msgid "" -"Protocol that encapsulates a wide variety of network layer protocols inside " -"virtual point-to-point links." -msgstr "" - -#: ../common/app_support.rst:143 ../common/app_support.rst:140 -#: ../common/app_support.rst:138 -msgid "" -"Provide as much detail as possible in the description. Paste in your command " -"output or stack traces, links to screen shots, and any other information " -"which might be useful." -msgstr "" - -#: ../common/glossary.rst:3635 ../common/glossary.rst:3642 -#: ../common/glossary.rst:3649 ../common/glossary.rst:3657 -#: ../common/glossary.rst:3646 -msgid "" -"Provided by Compute in the form of cloudpipes, specialized instances that " -"are used to create VPNs on a per-project basis." -msgstr "" - -#: ../common/glossary.rst:287 -msgid "Provided in Compute through the system usage data facility." -msgstr "" - -#: ../common/glossary.rst:2176 ../common/glossary.rst:2182 -msgid "" -"Provides a method of allocating space on mass-storage devices that is more " -"flexible than conventional partitioning schemes." -msgstr "" - -#: ../common/glossary.rst:3038 ../common/glossary.rst:3045 -#: ../common/glossary.rst:3052 ../common/glossary.rst:3054 -#: ../common/glossary.rst:3043 -msgid "" -"Provides a predefined list of actions that the user can perform, such as " -"start or stop VMs, reset passwords, and so on. Supported in both Identity " -"and Compute and can be configured using the horizon dashboard." -msgstr "" - -#: ../common/get_started_compute.rst:89 ../common/get_started_compute.rst:88 -msgid "" -"Provides a proxy for accessing running instances through a SPICE connection. " -"Supports browser-based HTML5 client." -msgstr "" - -#: ../common/get_started_compute.rst:93 ../common/get_started_compute.rst:92 -msgid "" -"Provides a proxy for accessing running instances through a VNC connection. " -"Supports an OpenStack-specific Java client." -msgstr "" - -#: ../common/get_started_compute.rst:85 ../common/get_started_compute.rst:84 -msgid "" -"Provides a proxy for accessing running instances through a VNC connection. " -"Supports browser-based novnc clients." -msgstr "" - -#: ../common/get_started_with_openstack.rst:30 -#: ../common/get_started_with_openstack.rst:38 -msgid "" -"Provides a web-based self-service portal to interact with underlying " -"OpenStack services, such as launching an instance, assigning IP addresses " -"and configuring access controls." -msgstr "" - -#: ../common/get_started_database_service.rst:49 -#: ../common/get_started_database_service.rst:48 -msgid "" -"Provides an OpenStack-native RESTful API that supports JSON to provision and " -"manage Trove instances." -msgstr "" - -#: ../common/get_started_with_openstack.rst:59 -#: ../common/get_started_with_openstack.rst:67 -msgid "" -"Provides an authentication and authorization service for other OpenStack " -"services. Provides a catalog of endpoints for all OpenStack services." -msgstr "" - -#: ../common/glossary.rst:2580 ../common/glossary.rst:2587 -#: ../common/glossary.rst:2586 ../common/glossary.rst:2592 -#: ../common/glossary.rst:2594 ../common/glossary.rst:2583 -msgid "" -"Provides an interface to the underlying Open vSwitch service for the " -"Networking plug-in." -msgstr "" - -#: ../common/get_started_with_openstack.rst:90 -msgid "" -"Provides capabilities to provision and scale Hadoop clusters in OpenStack by " -"specifying parameters like Hadoop version, cluster topology and nodes " -"hardware details." -msgstr "" - -#: ../common/get_started_with_openstack.rst:82 -#: ../common/get_started_with_openstack.rst:90 -msgid "" -"Provides capabilties to provision and scale Hadoop clusters in OpenStack by " -"specifying parameters like Hadoop version, cluster topology and nodes " -"hardware details." -msgstr "" - -#: ../common/glossary.rst:2982 ../common/glossary.rst:2989 -#: ../common/glossary.rst:2996 ../common/glossary.rst:2998 -#: ../common/glossary.rst:2987 -msgid "" -"Provides data redundancy and fault tolerance by creating copies of Object " -"Storage objects, accounts, and containers so that they are not lost when the " -"underlying storage fails." -msgstr "" - -#: ../common/glossary.rst:612 -msgid "" -"Provides logical partitioning of Compute resources in a child and parent " -"relationship. Requests are passed from parent cells to child cells if the " -"parent cannot provide the requested resource." -msgstr "" - -#: ../common/get_started_with_openstack.rst:54 -#: ../common/get_started_with_openstack.rst:62 -msgid "" -"Provides persistent block storage to running instances. Its pluggable driver " -"architecture facilitates the creation and management of block storage " -"devices." -msgstr "" - -#: ../common/get_started_with_openstack.rst:78 -#: ../common/get_started_with_openstack.rst:86 -msgid "" -"Provides scalable and reliable Cloud Database-as-a-Service functionality for " -"both relational and non-relational database engines." -msgstr "" - -#: ../common/glossary.rst:2456 ../common/glossary.rst:2463 -#: ../common/glossary.rst:2462 ../common/glossary.rst:2468 -#: ../common/glossary.rst:2470 ../common/glossary.rst:2459 -msgid "Provides support for NexentaStor devices in Compute." -msgstr "" - -#: ../common/glossary.rst:2585 ../common/glossary.rst:2592 -#: ../common/glossary.rst:2591 ../common/glossary.rst:2597 -#: ../common/glossary.rst:2599 ../common/glossary.rst:2588 -msgid "Provides support for Open vSwitch in Networking." -msgstr "" - -#: ../common/glossary.rst:3689 ../common/glossary.rst:3696 -#: ../common/glossary.rst:3703 ../common/glossary.rst:3711 -#: ../common/glossary.rst:3700 -msgid "Provides support for VMware NSX in Neutron." -msgstr "" - -#: ../common/glossary.rst:3731 ../common/glossary.rst:3738 -#: ../common/glossary.rst:3745 ../common/glossary.rst:3753 -#: ../common/glossary.rst:3742 -msgid "" -"Provides support for new and specialized types of back-end storage for the " -"Block Storage volume manager." -msgstr "" - -#: ../common/glossary.rst:2690 ../common/glossary.rst:2697 -#: ../common/glossary.rst:2703 ../common/glossary.rst:2705 -#: ../common/glossary.rst:2694 -msgid "" -"Provides to the consumer the ability to deploy applications through a " -"programming language or tools supported by the cloud platform provider. An " -"example of Platform-as-a-Service is an Eclipse/Java programming platform " -"provided with no downloads required." -msgstr "" - -#: ../common/get_started_identity.rst:10 ../common/get_started_identity.rst:9 -msgid "Providing a catalog of available services with their API endpoints." -msgstr "" - -#: ../common/get_started_object_storage.rst:17 -#: ../common/get_started_object_storage.rst:16 -msgid "Proxy servers (swift-proxy-server)" -msgstr "" - -#: ../common/get_started_telemetry.rst:13 -#: ../common/get_started_telemetry.rst:12 -msgid "" -"Publishes collected data to various targets including data stores and " -"message queues." -msgstr "" - -#: ../common/glossary.rst:2823 ../common/glossary.rst:2830 -#: ../common/glossary.rst:2837 ../common/glossary.rst:2839 -#: ../common/glossary.rst:2828 -msgid "Puppet" -msgstr "" - -#: ../common/glossary.rst:2828 ../common/glossary.rst:2835 -#: ../common/glossary.rst:2842 ../common/glossary.rst:2844 -#: ../common/glossary.rst:2833 -msgid "Python" -msgstr "" - -#: ../common/cli_install_openstack_command_line_clients.rst:21 -msgid "Python 2.7 or later" -msgstr "" - -#: ../common/glossary.rst:2832 ../common/glossary.rst:2839 -#: ../common/glossary.rst:2846 ../common/glossary.rst:2848 -#: ../common/glossary.rst:2837 -msgid "QEMU Copy On Write 2 (QCOW2)" -msgstr "" - -#: ../common/glossary.rst:2851 ../common/glossary.rst:2858 -#: ../common/glossary.rst:2865 ../common/glossary.rst:2867 -#: ../common/glossary.rst:2856 -msgid "" -"QEMU is a generic and open source machine emulator and virtualizer. One of " -"the hypervisors supported by OpenStack, generally used for development " -"purposes." -msgstr "" - -#: ../common/glossary.rst:2837 ../common/glossary.rst:2844 -#: ../common/glossary.rst:2851 ../common/glossary.rst:2853 -#: ../common/glossary.rst:2842 -msgid "Qpid" -msgstr "" - -#: ../common/glossary.rst:2848 ../common/glossary.rst:2855 -#: ../common/glossary.rst:2862 ../common/glossary.rst:2864 -#: ../common/glossary.rst:2853 -msgid "Quick EMUlator (QEMU)" -msgstr "" - -#: ../common/glossary.rst:2869 ../common/glossary.rst:2876 -#: ../common/glossary.rst:2883 ../common/glossary.rst:2885 -#: ../common/glossary.rst:2874 -msgid "RADOS Block Device (RBD)" -msgstr "" - -#: ../common/glossary.rst:2884 ../common/glossary.rst:2891 -#: ../common/glossary.rst:2898 ../common/glossary.rst:2900 -#: ../common/glossary.rst:2889 -msgid "RAM filter" -msgstr "" - -#: ../common/glossary.rst:2889 ../common/glossary.rst:2896 -#: ../common/glossary.rst:2903 ../common/glossary.rst:2905 -#: ../common/glossary.rst:2894 -msgid "RAM overcommit" -msgstr "" - -#: ../common/cli_install_openstack_command_line_clients.rst:204 -#: ../common/cli_install_openstack_command_line_clients.rst:210 -msgid "" -"RDO, openSUSE and SUSE Linux Enterprise have client packages that can be " -"installed without ``pip``." -msgstr "" - -#: ../common/cli_install_openstack_command_line_clients.rst:212 -#: ../common/cli_install_openstack_command_line_clients.rst:214 -#: ../common/cli_install_openstack_command_line_clients.rst:216 -msgid "" -"RDO, openSUSE, SUSE Linux Enterprise, Debian, and Ubuntu have client " -"packages that can be installed without ``pip``." -msgstr "" - -#: ../common/get_started_storage_concepts.rst:26 -#: ../common/get_started_storage_concepts.rst:25 -msgid "REST API" -msgstr "" - -#: ../common/glossary.rst:3017 ../common/glossary.rst:3024 -#: ../common/glossary.rst:3031 ../common/glossary.rst:3033 -#: ../common/glossary.rst:3022 -msgid "RESTful" -msgstr "" - -#: ../common/glossary.rst:3073 ../common/glossary.rst:3080 -#: ../common/glossary.rst:3087 ../common/glossary.rst:3089 -#: ../common/glossary.rst:3078 -msgid "RPC driver" -msgstr "" - -#: ../common/glossary.rst:3083 ../common/glossary.rst:3090 -#: ../common/glossary.rst:3097 ../common/glossary.rst:3099 -#: ../common/glossary.rst:3088 -msgid "RXTX cap" -msgstr "" - -#: ../common/glossary.rst:3088 ../common/glossary.rst:3095 -#: ../common/glossary.rst:3102 ../common/glossary.rst:3104 -#: ../common/glossary.rst:3093 -msgid "RXTX quota" -msgstr "" - -#: ../common/glossary.rst:2860 ../common/glossary.rst:2867 -#: ../common/glossary.rst:2874 ../common/glossary.rst:2876 -#: ../common/glossary.rst:2865 -msgid "RabbitMQ" -msgstr "" - -#: ../common/glossary.rst:2864 ../common/glossary.rst:2871 -#: ../common/glossary.rst:2878 ../common/glossary.rst:2880 -#: ../common/glossary.rst:2869 -msgid "Rackspace Cloud Files" -msgstr "" - -#: ../common/glossary.rst:2926 ../common/glossary.rst:2933 -#: ../common/glossary.rst:2940 ../common/glossary.rst:2942 -#: ../common/glossary.rst:2931 -msgid "Recon" -msgstr "" - -#: ../common/glossary.rst:2945 ../common/glossary.rst:2952 -#: ../common/glossary.rst:2959 ../common/glossary.rst:2961 -#: ../common/glossary.rst:2950 -msgid "Red Hat Enterprise Linux (RHEL)" -msgstr "" - -#: ../common/glossary.rst:775 -msgid "" -"Reducing the size of files by special encoding, the file can be decompressed " -"again to its original content. OpenStack supports compression at the Linux " -"file system level but does not support compression for things such as Object " -"Storage objects or Image service VM images." -msgstr "" - -#: ../common/glossary.rst:2351 ../common/glossary.rst:2358 -#: ../common/glossary.rst:2357 ../common/glossary.rst:2363 -#: ../common/glossary.rst:2352 -msgid "Released as open source by NASA in 2010 and is the basis for Compute." -msgstr "" - -#: ../common/glossary.rst:2867 ../common/glossary.rst:2874 -#: ../common/glossary.rst:2881 ../common/glossary.rst:2883 -#: ../common/glossary.rst:2872 -msgid "" -"Released as open source by Rackspace in 2010; the basis for Object Storage." -msgstr "" - -#: ../common/glossary.rst:2968 ../common/glossary.rst:2975 -#: ../common/glossary.rst:2982 ../common/glossary.rst:2984 -#: ../common/glossary.rst:2973 -msgid "Reliable, Autonomic Distributed Object Store" -msgstr "" - -#: ../common/glossary.rst:2974 ../common/glossary.rst:2981 -#: ../common/glossary.rst:2988 ../common/glossary.rst:2990 -#: ../common/glossary.rst:2979 -msgid "Remote Procedure Call (RPC)" -msgstr "" - -#: ../common/glossary.rst:2924 ../common/glossary.rst:2931 -#: ../common/glossary.rst:2938 ../common/glossary.rst:2940 -#: ../common/glossary.rst:2929 -msgid "" -"Removes all data on the server and replaces it with the specified image. " -"Server ID and IP addresses remain the same." -msgstr "" - -#: ../common/glossary.rst:2405 ../common/glossary.rst:2412 -#: ../common/glossary.rst:2411 ../common/glossary.rst:2417 -#: ../common/glossary.rst:2418 ../common/glossary.rst:2407 -msgid "Represents a virtual, isolated OSI layer-2 subnet in Networking." -msgstr "" - -#: ../common/support-compute.rst:172 -msgid "Reset the state of an instance" -msgstr "" - -#: ../common/cli_manage_volumes.rst:176 -msgid "Resize a volume" -msgstr "" - -#: ../common/cli_manage_volumes.rst:203 -msgid "" -"Resize the volume by passing the volume ID and the new size (a value greater " -"than the old one) as parameters::" -msgstr "" - -#: ../common/dashboard_customizing.rst:116 -#: ../common/dashboard_customizing.rst:126 -#: ../common/dashboard_customizing.rst:136 -msgid "Restart Apache for this change to take effect." -msgstr "" - -#: ../common/dashboard_customizing.rst:92 -msgid "Restart Apache:" -msgstr "" - -#: ../common/get_started_identity.rst:77 ../common/get_started_identity.rst:76 -msgid "Role" -msgstr "" - -#: ../common/glossary.rst:3035 ../common/glossary.rst:3042 -#: ../common/glossary.rst:3049 ../common/glossary.rst:3051 -#: ../common/glossary.rst:3040 -msgid "Role Based Access Control (RBAC)" -msgstr "" - -#: ../common/get_started_block_storage.rst:37 -#: ../common/get_started_block_storage.rst:36 -msgid "Routes information between the Block Storage processes." -msgstr "" - -#: ../common/cli_discover_version_number_for_a_client.rst:5 -msgid "Run the following command to discover the version number for a client::" -msgstr "" - -#: ../common/glossary.rst:3266 ../common/glossary.rst:3273 -#: ../common/glossary.rst:3280 ../common/glossary.rst:3288 -#: ../common/glossary.rst:3277 -msgid "Runs automated tests against the core OpenStack API; written in Rails." -msgstr "" - -#: ../common/get_started_telemetry.rst:26 -#: ../common/get_started_telemetry.rst:25 -msgid "" -"Runs on a central management server to poll for resource utilization " -"statistics for resources not tied to instances or compute nodes. Multiple " -"agents can be started to scale service horizontally." -msgstr "" - -#: ../common/get_started_telemetry.rst:31 -#: ../common/get_started_telemetry.rst:30 -msgid "" -"Runs on a central management server(s) and consumes messages from the " -"message queue(s) to build event and metering data." -msgstr "" - -#: ../common/get_started_telemetry.rst:35 -#: ../common/get_started_telemetry.rst:34 -msgid "" -"Runs on central management server(s) and dispatches collected telemetry data " -"to a data store or external consumer without modification." -msgstr "" - -#: ../common/get_started_telemetry.rst:21 -#: ../common/get_started_telemetry.rst:20 -msgid "" -"Runs on each compute node and polls for resource utilization statistics. " -"There may be other types of agents in the future, but for now our focus is " -"creating the compute agent." -msgstr "" - -#: ../common/get_started_telemetry.rst:45 -#: ../common/get_started_telemetry.rst:44 -msgid "" -"Runs on one or more central management servers to allow alarms to be set " -"based on the threshold evaluation for a collection of samples." -msgstr "" - -#: ../common/get_started_telemetry.rst:40 -#: ../common/get_started_telemetry.rst:39 -msgid "" -"Runs on one or more central management servers to determine when alarms fire " -"due to the associated statistic trend crossing a threshold over a sliding " -"time window." -msgstr "" - -#: ../common/get_started_telemetry.rst:49 -#: ../common/get_started_telemetry.rst:48 -msgid "" -"Runs on one or more central management servers to provide data access from " -"the data store." -msgstr "" - -#: ../common/get_started_database_service.rst:53 -#: ../common/get_started_database_service.rst:52 -msgid "" -"Runs on the host, and receives messages from guest instances that want to " -"update information on the host." -msgstr "" - -#: ../common/get_started_storage_concepts.rst:15 -#: ../common/get_started_storage_concepts.rst:14 -msgid "Runs operating systems and provides scratch space" -msgstr "" - -#: ../common/get_started_database_service.rst:62 -#: ../common/get_started_database_service.rst:61 -msgid "" -"Runs within the guest instance. Manages and performs operations on the " -"database itself." -msgstr "" - -#: ../common/glossary.rst:3093 ../common/glossary.rst:3100 -#: ../common/glossary.rst:3107 ../common/glossary.rst:3109 -#: ../common/glossary.rst:3098 -msgid "S3" -msgstr "" - -#: ../common/glossary.rst:3103 ../common/glossary.rst:3110 -#: ../common/glossary.rst:3117 ../common/glossary.rst:3119 -#: ../common/glossary.rst:3108 -msgid "SAML assertion" -msgstr "" - -#: ../common/glossary.rst:3146 ../common/glossary.rst:3153 -#: ../common/glossary.rst:3160 ../common/glossary.rst:3168 -#: ../common/glossary.rst:3157 -msgid "SELinux" -msgstr "" - -#: ../common/glossary.rst:718 -msgid "" -"SINA standard that defines a RESTful API for managing objects in the cloud, " -"currently unsupported in OpenStack." -msgstr "" - -#: ../common/glossary.rst:3284 ../common/glossary.rst:3291 -#: ../common/glossary.rst:3298 ../common/glossary.rst:3306 -#: ../common/glossary.rst:3295 -msgid "SPICE" -msgstr "" - -#: ../common/get_started_compute.rst:144 ../common/get_started_compute.rst:145 -#: ../common/get_started_compute.rst:143 -msgid "SQL database" -msgstr "" - -#: ../common/glossary.rst:3295 ../common/glossary.rst:3302 -#: ../common/glossary.rst:3309 ../common/glossary.rst:3317 -#: ../common/glossary.rst:3306 -msgid "SQL-Alchemy" -msgstr "" - -#: ../common/glossary.rst:3299 ../common/glossary.rst:3306 -#: ../common/glossary.rst:3313 ../common/glossary.rst:3321 -#: ../common/glossary.rst:3310 -msgid "SQLite" -msgstr "" - -#: ../common/glossary.rst:3367 ../common/glossary.rst:3374 -#: ../common/glossary.rst:3381 ../common/glossary.rst:3389 -#: ../common/glossary.rst:3378 -msgid "SUSE Linux Enterprise Server (SLES)" -msgstr "" - -#: ../common/support-compute.rst:102 -msgid "Script method" -msgstr "" - -#: ../common/get_started_storage_concepts.rst:59 -#: ../common/get_started_storage_concepts.rst:62 -#: ../common/get_started_storage_concepts.rst:61 -#: ../common/get_started_object_storage.rst:41 -msgid "" -"Script that initializes the building of the ring file, takes daemon names as " -"parameter and offers commands. Documented in http://docs.openstack.org/" -"developer/swift/admin_guide.html#managing-services." -msgstr "" - -#: ../common/glossary.rst:1290 ../common/glossary.rst:1291 -msgid "See API endpoint." -msgstr "" - -#: ../common/glossary.rst:82 -msgid "See access control list." -msgstr "" - -#: ../common/get_started_block_storage.rst:27 -#: ../common/get_started_block_storage.rst:26 -msgid "" -"Selects the optimal storage provider node on which to create the volume. A " -"similar component to the nova-scheduler." -msgstr "" - -#: ../common/cli_manage_volumes.rst:327 -msgid "" -"Send the volume transfer ID and authorization key to the new owner (for " -"example, by email)." -msgstr "" - -#: ../common/get_started_identity.rst:21 -msgid "Server" -msgstr "" - -#: ../common/cli_overview.rst:32 ../common/get_started_identity.rst:62 -#: ../common/get_started_with_openstack.rst:25 -#: ../common/get_started_identity.rst:61 -#: ../common/get_started_with_openstack.rst:33 -msgid "Service" -msgstr "" - -#: ../common/cli_set_environment_variables_using_openstack_rc.rst:3 -msgid "Set environment variables using the OpenStack RC file" -msgstr "" - -#: ../common/glossary.rst:529 -msgid "" -"Set of bits that make up a single character; there are usually 8 bits to a " -"byte." -msgstr "" - -#: ../common/dashboard_customizing.rst:111 -msgid "" -"Set the HTML title, which appears at the top of the browser window, by " -"adding the following line to :file:`local_settings.py`::" -msgstr "" - -#: ../common/glossary.rst:1034 -msgid "" -"Setting for the Compute RabbitMQ message delivery mode; can be set to either " -"transient or persistent." -msgstr "" - -#: ../common/cli_overview.rst:78 ../common/cli_overview.rst:81 -#: ../common/cli_overview.rst:85 ../common/cli_overview.rst:88 -msgid "Shared file systems" -msgstr "" - -#: ../common/glossary.rst:3244 ../common/glossary.rst:3251 -#: ../common/glossary.rst:3258 ../common/glossary.rst:3266 -#: ../common/glossary.rst:3255 -msgid "Sheepdog" -msgstr "" - -#: ../common/nova_show_usage_statistics_for_hosts_instances.rst:16 -msgid "Show host usage statistics" -msgstr "" - -#: ../common/cli_manage_volumes.rst:134 -msgid "Show information for your volume:" -msgstr "" - -#: ../common/nova_show_usage_statistics_for_hosts_instances.rst:74 -msgid "Show instance usage statistics" -msgstr "" - -#: ../common/nova_show_usage_statistics_for_hosts_instances.rst:3 -msgid "Show usage statistics for hosts and instances" -msgstr "" - -#: ../common/cli_manage_images.rst:170 -msgid "" -"Similar to ``--location`` in usage, but indicates that the image server " -"should immediately copy the data and store it in its configured image store." -msgstr "" - -#: ../common/get_started_compute.rst:72 ../common/get_started_compute.rst:71 -msgid "" -"Similar to the nova-compute service, accepts networking tasks from the queue " -"and manipulates the network. Performs tasks such as setting up bridging " -"interfaces or changing IPtables rules." -msgstr "" - -#: ../common/glossary.rst:3249 ../common/glossary.rst:3256 -#: ../common/glossary.rst:3263 ../common/glossary.rst:3271 -#: ../common/glossary.rst:3260 -msgid "Simple Cloud Identity Management (SCIM)" -msgstr "" - -#: ../common/cli_install_openstack_command_line_clients.rst:49 -msgid "" -"Since the installation process compiles source files, this requires the " -"related Python development package for your operating system and " -"distribution." -msgstr "" - -#: ../common/glossary.rst:3254 ../common/glossary.rst:3261 -#: ../common/glossary.rst:3268 ../common/glossary.rst:3276 -#: ../common/glossary.rst:3265 -msgid "Single-root I/O Virtualization (SR-IOV)" -msgstr "" - -#: ../common/get_started_storage_concepts.rst:28 -#: ../common/get_started_storage_concepts.rst:31 -#: ../common/get_started_storage_concepts.rst:30 -msgid "Sizings based on need" -msgstr "" - -#: ../common/glossary.rst:3263 ../common/glossary.rst:3270 -#: ../common/glossary.rst:3277 ../common/glossary.rst:3285 -#: ../common/glossary.rst:3274 -msgid "SmokeStack" -msgstr "" - -#: ../common/glossary.rst:3091 ../common/glossary.rst:3098 -#: ../common/glossary.rst:3105 ../common/glossary.rst:3107 -#: ../common/glossary.rst:3096 -msgid "" -"Soft limit on the amount of network traffic a Compute VM instance can send " -"and receive." -msgstr "" - -#: ../common/glossary.rst:2698 ../common/glossary.rst:2705 -#: ../common/glossary.rst:2711 ../common/glossary.rst:2713 -#: ../common/glossary.rst:2702 -msgid "" -"Software component providing the actual implementation for Networking APIs, " -"or for Compute APIs, depending on the context." -msgstr "" - -#: ../common/glossary.rst:1739 ../common/glossary.rst:1745 -msgid "" -"Software that arbitrates and controls VM access to the actual underlying " -"hardware." -msgstr "" - -#: ../common/glossary.rst:2139 ../common/glossary.rst:2145 -msgid "" -"Software that enables multiple VMs to share a single physical NIC within " -"Compute." -msgstr "" - -#: ../common/glossary.rst:3644 ../common/glossary.rst:3651 -#: ../common/glossary.rst:3658 ../common/glossary.rst:3666 -#: ../common/glossary.rst:3655 -msgid "" -"Software that runs on a host or node and provides the features and functions " -"of a hardware-based network switch." -msgstr "" - -#: ../common/glossary.rst:3279 ../common/glossary.rst:3286 -#: ../common/glossary.rst:3293 ../common/glossary.rst:3301 -#: ../common/glossary.rst:3290 -msgid "SolidFire Volume Driver" -msgstr "" - -#: ../common/app_support.rst:139 ../common/app_support.rst:136 -#: ../common/app_support.rst:134 -msgid "Some tips:" -msgstr "" - -#: ../common/conventions.rst:14 -msgid "Something you must be aware of before proceeding." -msgstr "" - -#: ../common/support-compute.rst:115 -msgid "" -"Sometimes a particular instance shows ``pending`` or you cannot SSH to it. " -"Sometimes the image itself is the problem. For example, when you use flat " -"manager networking, you do not have a DHCP server and certain images do not " -"support interface injection; you cannot connect to them. The fix for this " -"problem is to use an image that does support this method, such as Ubuntu, " -"which obtains an IP address correctly with FlatManager network settings." -msgstr "" - -#: ../common/glossary.rst:3196 ../common/glossary.rst:3203 -#: ../common/glossary.rst:3210 ../common/glossary.rst:3218 -#: ../common/glossary.rst:3207 -msgid "" -"Special tenant that contains all services that are listed in the catalog." -msgstr "" - -#: ../common/glossary.rst:3252 ../common/glossary.rst:3259 -#: ../common/glossary.rst:3266 ../common/glossary.rst:3274 -#: ../common/glossary.rst:3263 -msgid "" -"Specification for managing identity in the cloud, currently unsupported by " -"OpenStack." -msgstr "" - -#: ../common/glossary.rst:1412 ../common/glossary.rst:1413 -msgid "" -"Specifies additional requirements when Compute determines where to start a " -"new instance. Examples include a minimum amount of network bandwidth or a " -"GPU." -msgstr "" - -#: ../common/glossary.rst:3354 ../common/glossary.rst:3361 -#: ../common/glossary.rst:3368 ../common/glossary.rst:3376 -#: ../common/glossary.rst:3365 -msgid "Specifies the authentication source used by Image service or Identity." -msgstr "" - -#: ../common/glossary.rst:3311 ../common/glossary.rst:3318 -#: ../common/glossary.rst:3325 ../common/glossary.rst:3333 -#: ../common/glossary.rst:3322 -msgid "StackTach" -msgstr "" - -#: ../common/glossary.rst:2567 ../common/glossary.rst:2574 -#: ../common/glossary.rst:2573 ../common/glossary.rst:2579 -#: ../common/glossary.rst:2581 ../common/glossary.rst:2570 -msgid "Standard for packaging VM images. Supported in OpenStack." -msgstr "" - -#: ../common/glossary.rst:3320 ../common/glossary.rst:3327 -#: ../common/glossary.rst:3334 ../common/glossary.rst:3342 -#: ../common/glossary.rst:3331 -msgid "StaticWeb" -msgstr "" - -#: ../common/get_started_storage_concepts.rst:4 -#: ../common/get_started_storage_concepts.rst:3 -msgid "Storage concepts" -msgstr "" - -#: ../common/glossary.rst:1438 ../common/glossary.rst:1439 -msgid "" -"Storage protocol similar in concept to TCP/IP; encapsulates SCSI commands " -"and data." -msgstr "" - -#: ../common/glossary.rst:1945 ../common/glossary.rst:1951 -msgid "" -"Storage protocol that encapsulates SCSI frames for transport over IP " -"networks." -msgstr "" - -#: ../common/get_started_image_service.rst:39 -#: ../common/get_started_image_service.rst:40 -#: ../common/get_started_image_service.rst:36 -msgid "Storage repository for image files" -msgstr "" - -#: ../common/get_started_storage_concepts.rst:68 -#: ../common/get_started_storage_concepts.rst:71 -#: ../common/get_started_storage_concepts.rst:70 -#: ../common/get_started_object_storage.rst:50 -msgid "" -"Storage ring build and rebalance utility. Documented in http://docs." -"openstack.org/developer/swift/admin_guide.html#managing-the-rings." -msgstr "" - -#: ../common/get_started_storage_concepts.rst:0 -msgid "Storage types" -msgstr "" - -#: ../common/glossary.rst:2289 ../common/glossary.rst:2296 -#: ../common/glossary.rst:2295 ../common/glossary.rst:2284 -msgid "Stores CephFS metadata." -msgstr "" - -#: ../common/get_started_with_openstack.rst:46 -#: ../common/get_started_with_openstack.rst:54 -msgid "" -"Stores and retrieves arbitrary unstructured data objects via a RESTful, HTTP " -"based API. It is highly fault tolerant with its data replication and scale-" -"out architecture. Its implementation is not like a file server with " -"mountable directories. In this case, it writes objects and files to multiple " -"drives, ensuring the data is replicated across a server cluster." -msgstr "" - -#: ../common/get_started_with_openstack.rst:64 -#: ../common/get_started_with_openstack.rst:72 -msgid "" -"Stores and retrieves virtual machine disk images. OpenStack Compute makes " -"use of this during instance provisioning." -msgstr "" - -#: ../common/get_started_image_service.rst:34 -#: ../common/get_started_image_service.rst:31 -msgid "" -"Stores image metadata and you can choose your database depending on your " -"preference. Most deployments use MySQL or SQLite." -msgstr "" - -#: ../common/get_started_compute.rst:132 ../common/get_started_compute.rst:131 -msgid "" -"Stores most build-time and run-time states for a cloud infrastructure, " -"including:" -msgstr "" - -#: ../common/get_started_image_service.rst:25 -#: ../common/get_started_image_service.rst:22 -msgid "" -"Stores, processes, and retrieves metadata about images. Metadata includes " -"items such as size and type." -msgstr "" - -#: ../common/glossary.rst:3127 ../common/glossary.rst:3134 -#: ../common/glossary.rst:3141 ../common/glossary.rst:3143 -#: ../common/glossary.rst:3132 -msgid "" -"String of text known only by the user; used along with an access key to make " -"requests to the Compute API." -msgstr "" - -#: ../common/glossary.rst:3573 ../common/glossary.rst:3580 -#: ../common/glossary.rst:3587 ../common/glossary.rst:3595 -#: ../common/glossary.rst:3584 -msgid "Subdivides physical CPUs. Instances can then use those divisions." -msgstr "" - -#: ../common/get_started_sahara.rst:31 ../common/get_started_sahara.rst:32 -msgid "Support for different Hadoop distributions:" -msgstr "" - -#: ../common/cli_manage_images.rst:235 ../common/cli_manage_images.rst:254 -msgid "Supported model values" -msgstr "" - -#: ../common/glossary.rst:3685 ../common/glossary.rst:3692 -#: ../common/glossary.rst:3699 ../common/glossary.rst:3707 -#: ../common/glossary.rst:3696 -msgid "Supports interaction with VMware products in Compute." -msgstr "" - -#: ../common/get_started_compute.rst:54 ../common/get_started_compute.rst:53 -msgid "" -"Takes a virtual machine instance request from the queue and determines on " -"which compute server host it runs." -msgstr "" - -#: ../common/glossary.rst:3428 ../common/cli_overview.rst:72 -#: ../common/glossary.rst:3435 ../common/cli_overview.rst:81 -#: ../common/glossary.rst:3442 ../common/cli_overview.rst:84 -#: ../common/glossary.rst:3450 ../common/cli_overview.rst:88 -#: ../common/glossary.rst:3439 ../common/cli_overview.rst:91 -msgid "Telemetry" -msgstr "" - -#: ../common/get_started_telemetry.rst:4 -msgid "Telemetry module" -msgstr "" - -#: ../common/glossary.rst:3434 ../common/glossary.rst:3441 -#: ../common/glossary.rst:3448 ../common/glossary.rst:3456 -#: ../common/glossary.rst:3445 -msgid "TempAuth" -msgstr "" - -#: ../common/glossary.rst:3445 ../common/glossary.rst:3452 -#: ../common/glossary.rst:3459 ../common/glossary.rst:3467 -#: ../common/glossary.rst:3456 -msgid "TempURL" -msgstr "" - -#: ../common/glossary.rst:3440 ../common/glossary.rst:3447 -#: ../common/glossary.rst:3454 ../common/glossary.rst:3462 -#: ../common/glossary.rst:3451 -msgid "Tempest" -msgstr "" - -#: ../common/get_started_identity.rst:56 ../common/get_started_identity.rst:55 -msgid "Tenant" -msgstr "" - -#: ../common/glossary.rst:3455 ../common/glossary.rst:3462 -#: ../common/glossary.rst:3469 ../common/glossary.rst:3477 -#: ../common/glossary.rst:3466 -msgid "Tenant API" -msgstr "" - -#: ../common/glossary.rst:2557 ../common/glossary.rst:2564 -#: ../common/glossary.rst:2563 ../common/glossary.rst:2569 -#: ../common/glossary.rst:2571 ../common/glossary.rst:2560 -msgid "" -"Term for an Object Storage process that runs for a long time. Can indicate a " -"hung process." -msgstr "" - -#: ../common/glossary.rst:2104 ../common/glossary.rst:2110 -msgid "" -"Term used in the OSI network architecture for the data link layer. The data " -"link layer is responsible for media access control, flow control and " -"detecting and possibly correcting errors that may occur in the physical " -"layer." -msgstr "" - -#: ../common/glossary.rst:2111 ../common/glossary.rst:2117 -msgid "" -"Term used in the OSI network architecture for the network layer. The network " -"layer is responsible for packet forwarding including routing from one node " -"to another." -msgstr "" - -#: ../common/glossary.rst:1799 ../common/glossary.rst:1805 -msgid "" -"The API used to access the OpenStack Identity service provided through " -"keystone." -msgstr "" - -#: ../common/glossary.rst:1281 ../common/glossary.rst:1282 -msgid "The Amazon commercial block storage product." -msgstr "" - -#: ../common/glossary.rst:1256 ../common/glossary.rst:1257 -msgid "The Amazon commercial compute product, similar to Compute." -msgstr "" - -#: ../common/glossary.rst:165 -msgid "" -"The Apache Software Foundation supports the Apache community of open-source " -"software projects. These projects provide software products for the public " -"good." -msgstr "" - -#: ../common/glossary.rst:3282 ../common/glossary.rst:3289 -#: ../common/glossary.rst:3296 ../common/glossary.rst:3304 -#: ../common/glossary.rst:3293 -msgid "The Block Storage driver for the SolidFire iSCSI storage appliance." -msgstr "" - -#: ../common/get_started_block_storage.rst:12 -#: ../common/get_started_block_storage.rst:11 -msgid "The Block Storage service consists of the following components:" -msgstr "" - -#: ../common/glossary.rst:498 -msgid "" -"The Border Gateway Protocol is a dynamic routing protocol that connects " -"autonomous systems. Considered the backbone of the Internet, this protocol " -"connects disparate networks to form a larger network." -msgstr "" - -#: ../common/glossary.rst:2548 ../common/glossary.rst:2555 -#: ../common/glossary.rst:2554 ../common/glossary.rst:2560 -#: ../common/glossary.rst:2562 ../common/glossary.rst:2551 -msgid "The Ceph storage daemon." -msgstr "" - -#: ../common/glossary.rst:1219 ../common/glossary.rst:1220 -msgid "" -"The Compute RabbitMQ message exchange that remains active when the server " -"restarts." -msgstr "" - -#: ../common/glossary.rst:3293 ../common/glossary.rst:3300 -#: ../common/glossary.rst:3307 ../common/glossary.rst:3315 -#: ../common/glossary.rst:3304 -msgid "" -"The Compute VM scheduling algorithm that attempts to start a new VM on the " -"host with the least amount of load." -msgstr "" - -#: ../common/glossary.rst:794 -msgid "" -"The Compute component that chooses suitable hosts on which to start VM " -"instances." -msgstr "" - -#: ../common/glossary.rst:625 -msgid "" -"The Compute component that contains a list of the current capabilities of " -"each host within the cell and routes requests as appropriate." -msgstr "" - -#: ../common/glossary.rst:1475 ../common/glossary.rst:1476 -msgid "" -"The Compute component that gives IP addresses to authorized nodes and " -"assumes DHCP, DNS, and routing configuration and services are provided by " -"something else." -msgstr "" - -#: ../common/glossary.rst:2396 ../common/glossary.rst:2403 -#: ../common/glossary.rst:2402 ../common/glossary.rst:2408 -#: ../common/glossary.rst:2409 ../common/glossary.rst:2398 -msgid "" -"The Compute component that manages various network components, such as " -"firewall rules, IP address allocation, and so on." -msgstr "" - -#: ../common/glossary.rst:1495 ../common/glossary.rst:1496 -msgid "" -"The Compute component that provides dnsmasq (DHCP, DNS, BOOTP, TFTP) and " -"radvd (routing) services." -msgstr "" - -#: ../common/glossary.rst:813 -msgid "" -"The Compute component that runs on each compute node and manages the VM " -"instance life cycle, including run, reboot, terminate, attach/detach " -"volumes, and so on. Provided by the nova-compute daemon." -msgstr "" - -#: ../common/glossary.rst:3070 ../common/glossary.rst:3077 -#: ../common/glossary.rst:3084 ../common/glossary.rst:3086 -#: ../common/glossary.rst:3075 -msgid "" -"The Compute direct exchanges, fanout exchanges, and topic exchanges use this " -"key to determine how to process a message; processing varies depending on " -"exchange type." -msgstr "" - -#: ../common/glossary.rst:1447 ../common/glossary.rst:1448 -msgid "" -"The Compute scheduling method that attempts to fill a host with VMs rather " -"than starting new VMs on a variety of hosts." -msgstr "" - -#: ../common/glossary.rst:132 -msgid "" -"The Compute service can send alerts through its notification system, which " -"includes a facility to create custom notification drivers. Alerts can be " -"sent to and displayed on the horizon dashboard." -msgstr "" - -#: ../common/glossary.rst:77 -msgid "" -"The Compute service provides accounting information through the event " -"notification and system usage data facilities." -msgstr "" - -#: ../common/glossary.rst:2887 ../common/glossary.rst:2894 -#: ../common/glossary.rst:2901 ../common/glossary.rst:2903 -#: ../common/glossary.rst:2892 -msgid "The Compute setting that enables or disables RAM overcommitment." -msgstr "" - -#: ../common/get_started_sahara.rst:7 -msgid "" -"The Data processing service for OpenStack (sahara) aims to provide users " -"with a simple means to provision data processing (Hadoop, Spark) clusters by " -"specifying several parameters like Hadoop version, cluster topology, node " -"hardware details and a few more. After a user fills in all the parameters, " -"the Data processing service deploys the cluster in a few minutes. Sahara " -"also provides a means to scale already provisioned clusters by adding or " -"removing worker nodes on demand." -msgstr "" - -#: ../common/get_started_sahara.rst:6 -msgid "" -"The Data processing service for OpenStack (sahara) aims to provide users " -"with a simple means to provision data processing (Hadoop, Spark) clusters by " -"specifying several parameters like Hadoop version, cluster topology, node " -"hardware details and a few more. After a user fills in all the parameters, " -"the Data processing service deploys the cluster in a few minutes. Sahara " -"also provides a means to scale already provisioned clusters by adding/" -"removing worker nodes on demand." -msgstr "" - -#: ../common/get_started_database_service.rst:43 -#: ../common/get_started_database_service.rst:42 -msgid "The Database service includes the following components:" -msgstr "" - -#: ../common/get_started_database_service.rst:13 -#: ../common/get_started_database_service.rst:12 -msgid "" -"The Database service provides resource isolation at high performance levels, " -"and automates complex administrative tasks such as deployment, " -"configuration, patching, backups, restores, and monitoring." -msgstr "" - -#: ../common/get_started_database_service.rst:6 -#: ../common/get_started_database_service.rst:5 -msgid "" -"The Database service provides scalable and reliable cloud provisioning " -"functionality for both relational and non-relational database engines. Users " -"can quickly and easily use database features without the burden of handling " -"complex administrative tasks. Cloud users and database administrators can " -"provision and manage multiple database instances as needed." -msgstr "" - -#: ../common/glossary.rst:337 -msgid "The Identity component that provides high-level authorization services." -msgstr "" - -#: ../common/glossary.rst:322 -msgid "The Identity service component that provides authentication services." -msgstr "" - -#: ../common/get_started_identity.rst:17 -msgid "The Identity service contains these components:" -msgstr "" - -#: ../common/glossary.rst:1568 ../common/glossary.rst:1569 -msgid "" -"The Identity service endpoint template that contains services available to " -"all tenants." -msgstr "" - -#: ../common/glossary.rst:1816 ../common/glossary.rst:1822 -msgid "The Image service API endpoint for management of VM images." -msgstr "" - -#: ../common/app_support.rst:130 ../common/app_support.rst:127 -#: ../common/app_support.rst:125 -msgid "The Launchpad Bugs area" -msgstr "" - -#: ../common/glossary.rst:3662 ../common/glossary.rst:3669 -#: ../common/glossary.rst:3676 ../common/glossary.rst:3684 -#: ../common/glossary.rst:3673 -msgid "" -"The Network Controller provides virtual networks to enable compute servers " -"to interact with each other and with the public network. All machines must " -"have a public and private network interface. A VLAN network is a private " -"network interface, which is controlled by the `vlan_interface` option with " -"VLAN managers." -msgstr "" - -#: ../common/glossary.rst:2745 ../common/glossary.rst:2752 -#: ../common/glossary.rst:2758 ../common/glossary.rst:2760 -#: ../common/glossary.rst:2749 -msgid "" -"The Network Controller provides virtual networks to enable compute servers " -"to interact with each other and with the public network. All machines must " -"have a public and private network interface. A private network interface can " -"be a flat or VLAN network interface. A flat network interface is controlled " -"by the flat_interface with flat managers. A VLAN network interface is " -"controlled by the `vlan_interface` option with VLAN managers." -msgstr "" - -#: ../common/glossary.rst:2818 ../common/glossary.rst:2825 -#: ../common/glossary.rst:2832 ../common/glossary.rst:2834 -#: ../common/glossary.rst:2823 -msgid "" -"The Network Controller provides virtual networks to enable compute servers " -"to interact with each other and with the public network. All machines must " -"have a public and private network interface. The public network interface is " -"controlled by the `public_interface` option." -msgstr "" - -#: ../common/glossary.rst:2998 ../common/glossary.rst:3005 -#: ../common/glossary.rst:3012 ../common/glossary.rst:3014 -#: ../common/glossary.rst:3003 -msgid "" -"The Object Storage back-end process that creates and manages object replicas." -msgstr "" - -#: ../common/glossary.rst:874 -msgid "" -"The Object Storage component that provides container services, such as " -"create, delete, list, and so on." -msgstr "" - -#: ../common/glossary.rst:44 -msgid "" -"The Object Storage context of an account. Do not confuse with a user account " -"from an authentication service, such as Active Directory, /etc/passwd, " -"OpenLDAP, OpenStack Identity, and so on." -msgstr "" - -#: ../common/get_started_identity.rst:5 -msgid "" -"The OpenStack :term:`Identity service ` provides a single point of " -"integration for managing authentication, authorization, and service catalog " -"services. Other OpenStack services use the Identity service as a common " -"unified API. Additionally, services that provide information about users but " -"that are not included in OpenStack (such as LDAP services) can be integrated " -"into a pre-existing infrastructure." -msgstr "" - -#: ../common/get_started_database_service.rst:21 -#: ../common/get_started_database_service.rst:20 -msgid "" -"The OpenStack Administrator configures the basic infrastructure using the " -"following steps:" -msgstr "" - -#: ../common/get_started_block_storage.rst:6 -#: ../common/get_started_block_storage.rst:5 -msgid "" -"The OpenStack Block Storage service (cinder) adds persistent storage to a " -"virtual machine. Block Storage provides an infrastructure for managing " -"volumes, and interacts with OpenStack Compute to provide volumes for " -"instances. The service also enables management of volume snapshots, and " -"volume types." -msgstr "" - -#: ../common/app_support.rst:198 ../common/app_support.rst:195 -#: ../common/app_support.rst:193 ../common/app_support.rst:199 -#: ../common/app_support.rst:201 ../common/app_support.rst:204 -#: ../common/app_support.rst:206 -msgid "The OpenStack IRC channel" -msgstr "" - -#: ../common/get_started_identity.rst:6 ../common/get_started_identity.rst:5 -msgid "The OpenStack Identity service performs the following functions:" -msgstr "" - -#: ../common/get_started_image_service.rst:19 -msgid "The OpenStack Image Service includes the following components:" -msgstr "" - -#: ../common/get_started_image_service.rst:6 -msgid "" -"The OpenStack Image Service is central to Infrastructure-as-a-Service (IaaS) " -"as shown in Conceptual architecture. It accepts API requests for disk or " -"server images, and image metadata from end users or OpenStack Compute " -"components. It also supports the storage of disk or server images on various " -"repository types, including OpenStack Object Storage." -msgstr "" - -#: ../common/get_started_image_service.rst:19 -#: ../common/get_started_image_service.rst:16 -msgid "The OpenStack Image service includes the following components:" -msgstr "" - -#: ../common/get_started_image_service.rst:5 -msgid "" -"The OpenStack Image service is central to Infrastructure-as-a-Service (IaaS) " -"as shown in :ref:`get_started_conceptual_architecture`. It accepts API " -"requests for disk or server images, and image metadata from end users or " -"OpenStack Compute components. It also supports the storage of disk or server " -"images on various repository types, including OpenStack Object Storage." -msgstr "" - -#: ../common/get_started_image_service.rst:6 -msgid "" -"The OpenStack Image service is central to Infrastructure-as-a-Service (IaaS) " -"as shown in Conceptual architecture. It accepts API requests for disk or " -"server images, and image metadata from end users or OpenStack Compute " -"components. It also supports the storage of disk or server images on various " -"repository types, including OpenStack Object Storage." -msgstr "" - -#: ../common/get_started_object_storage.rst:6 -#: ../common/get_started_object_storage.rst:5 -msgid "" -"The OpenStack Object Storage is a multi-tenant object storage system. It is " -"highly scalable and can manage large amounts of unstructured data at low " -"cost through a RESTful HTTP API." -msgstr "" - -#: ../common/app_support.rst:200 ../common/app_support.rst:197 -#: ../common/app_support.rst:195 ../common/app_support.rst:201 -#: ../common/app_support.rst:203 ../common/app_support.rst:206 -#: ../common/app_support.rst:208 -msgid "" -"The OpenStack community lives in the #openstack IRC channel on the Freenode " -"network. You can hang out, ask questions, or get immediate feedback for " -"urgent and pressing issues. To install an IRC client or use a browser-based " -"client, go to `https://webchat.freenode.net/ `__. You can also use Colloquy (Mac OS X, http://colloquy.info/), mIRC " -"(Windows, http://www.mirc.com/), or XChat (Linux). When you are in the IRC " -"channel and want to share code or command output, the generally accepted " -"method is to use a Paste Bin. The OpenStack project has one at http://paste." -"openstack.org. Just paste your longer amounts of text or logs in the web " -"form and you get a URL that you can paste into the channel. The OpenStack " -"IRC channel is ``#openstack`` on ``irc.freenode.net``. You can find a list " -"of all OpenStack IRC channels at https://wiki.openstack.org/wiki/IRC." -msgstr "" - -#: ../common/app_support.rst:132 ../common/app_support.rst:129 -#: ../common/app_support.rst:127 -msgid "" -"The OpenStack community values your set up and testing efforts and wants " -"your feedback. To log a bug, you must sign up for a Launchpad account at " -"https://launchpad.net/+login. You can view existing bugs and report bugs in " -"the Launchpad Bugs area. Use the search feature to determine whether the bug " -"has already been reported or already been fixed. If it still seems like your " -"bug is unreported, fill out a bug report." -msgstr "" - -#: ../common/glossary.rst:1882 ../common/glossary.rst:1888 -msgid "" -"The OpenStack configuration files use an INI format to describe options and " -"their values. It consists of sections and key value pairs." -msgstr "" - -#: ../common/glossary.rst:466 -msgid "" -"The OpenStack core project that enables management of volumes, volume " -"snapshots, and volume types. The project name of Block Storage is cinder." -msgstr "" - -#: ../common/glossary.rst:1791 ../common/glossary.rst:1797 -msgid "" -"The OpenStack core project that provides a central directory of users mapped " -"to the OpenStack services they can access. It also registers endpoints for " -"OpenStack services. It acts as a common authentication system. The project " -"name of Identity is keystone." -msgstr "" - -#: ../common/glossary.rst:783 -msgid "" -"The OpenStack core project that provides compute services. The project name " -"of Compute service is nova." -msgstr "" - -#: ../common/glossary.rst:2538 ../common/glossary.rst:2545 -#: ../common/glossary.rst:2544 ../common/glossary.rst:2550 -#: ../common/glossary.rst:2552 ../common/glossary.rst:2541 -msgid "" -"The OpenStack core project that provides eventually consistent and redundant " -"storage and retrieval of fixed digital content. The project name of " -"OpenStack Object Storage is swift." -msgstr "" - -#: ../common/dashboard_customizing.rst:14 -msgid "" -"The OpenStack dashboard by default on Ubuntu installs the ``openstack-" -"dashboard-ubuntu-theme`` package." -msgstr "" - -#: ../common/get_started_dashboard.rst:6 ../common/get_started_dashboard.rst:7 -msgid "" -"The OpenStack dashboard is a modular `Django web application `__ that provides a graphical interface to OpenStack " -"services." -msgstr "" - -#: ../common/conventions.rst:5 -msgid "The OpenStack documentation uses several typesetting conventions." -msgstr "" - -#: ../common/get_started_database_service.rst:30 -#: ../common/get_started_database_service.rst:29 +#: ../common/get_started_openstack_networking.rst:32 +#: ../common/get_started_openstack_networking.rst:33 msgid "" -"The OpenStack end user deploys the Database service using the following " -"steps:" +"OpenStack Networking mainly interacts with OpenStack Compute to provide " +"networks and connectivity for its instances." msgstr "" -#: ../common/get_started_with_openstack.rst:7 -#: ../common/get_started_with_openstack.rst:15 -msgid "" -"The OpenStack project is an open source cloud computing platform for all " -"types of clouds, which aims to be simple to implement, massively scalable, " -"and feature rich. Developers and cloud computing technologists from around " -"the world create the OpenStack project." +#: ../common/get_started_openstack_services.rst:3 +#: ../common/get_started_with_openstack.rst:96 +msgid "OpenStack services" msgstr "" -#: ../common/get_started_storage_concepts.rst:6 -#: ../common/get_started_storage_concepts.rst:5 -msgid "The OpenStack stack uses the following storage types:" +#: ../common/get_started_openstack_services.rst:22 +#: ../common/get_started_with_openstack.rst:98 +msgid "This section describes OpenStack services in detail." msgstr "" -#: ../common/app_support.rst:118 ../common/app_support.rst:115 -#: ../common/app_support.rst:113 -msgid "The OpenStack wiki" +#: ../common/get_started_orchestration.rst:3 +#: ../common/get_started_orchestration.rst:4 +msgid "OpenStack Orchestration module" msgstr "" -#: ../common/get_started_orchestration.rst:19 -#: ../common/get_started_orchestration.rst:18 -msgid "The Orchestration module consists of the following components:" +#: ../common/get_started_orchestration.rst:4 +msgid "Orchestration module concepts" msgstr "" #: ../common/get_started_orchestration.rst:5 @@ -8472,155 +3939,1260 @@ msgid "" "enables OpenStack core projects to receive a larger user base." msgstr "" -#: ../common/glossary.rst:641 -msgid "The POSIX-compliant file system provided by Ceph." -msgstr "" - -#: ../common/glossary.rst:2012 ../common/glossary.rst:2018 +#: ../common/get_started_orchestration.rst:15 +#: ../common/get_started_orchestration.rst:16 msgid "" -"The SCSI disk protocol tunneled within Ethernet, supported by Compute, " -"Object Storage, and Image service." +"The service enables deployers to integrate with the Orchestration module " +"directly or through custom plug-ins." msgstr "" -#: ../common/glossary.rst:3287 ../common/glossary.rst:3294 -#: ../common/glossary.rst:3301 ../common/glossary.rst:3309 -#: ../common/glossary.rst:3298 +#: ../common/get_started_orchestration.rst:18 +#: ../common/get_started_orchestration.rst:19 +msgid "The Orchestration module consists of the following components:" +msgstr "" + +#: ../common/get_started_orchestration.rst:21 +#: ../common/get_started_orchestration.rst:22 msgid "" -"The Simple Protocol for Independent Computing Environments (SPICE) provides " -"remote desktop access to guest virtual machines. It is an alternative to " -"VNC. SPICE is supported by OpenStack." +"A CLI that communicates with the heat-api to run AWS CloudFormation APIs. " +"End developers can directly use the Orchestration REST API." msgstr "" -#: ../common/get_started_telemetry.rst:18 -#: ../common/get_started_telemetry.rst:17 -msgid "The Telemetry module consists of the following components:" +#: ../common/get_started_orchestration.rst:22 +#: ../common/get_started_orchestration.rst:23 +msgid "``heat`` command-line client" msgstr "" -#: ../common/get_started_telemetry.rst:6 ../common/get_started_telemetry.rst:5 +#: ../common/get_started_orchestration.rst:25 +#: ../common/get_started_orchestration.rst:26 +msgid "" +"An OpenStack-native REST API that processes API requests by sending them to " +"the heat-engine over Remote Procedure Call (RPC)." +msgstr "" + +#: ../common/get_started_orchestration.rst:26 +#: ../common/get_started_orchestration.rst:27 +msgid "``heat-api`` component" +msgstr "" + +#: ../common/get_started_orchestration.rst:29 +#: ../common/get_started_orchestration.rst:30 +msgid "" +"An AWS Query API that is compatible with AWS CloudFormation. It processes " +"API requests by sending them to the heat-engine over RPC." +msgstr "" + +#: ../common/get_started_orchestration.rst:30 +#: ../common/get_started_orchestration.rst:31 +msgid "``heat-api-cfn`` component" +msgstr "" + +#: ../common/get_started_orchestration.rst:33 +#: ../common/get_started_orchestration.rst:34 +msgid "" +"Orchestrates the launching of templates and provides events back to the API " +"consumer." +msgstr "" + +#: ../common/get_started_orchestration.rst:33 +#: ../common/get_started_orchestration.rst:34 +#: ../common/get_started_orchestration.rst:35 +msgid "``heat-engine``" +msgstr "" + +#: ../common/get_started_sahara.rst:4 ../common/glossary.rst:989 +msgid "Data processing service" +msgstr "" + +#: ../common/get_started_sahara.rst:4 ../common/get_started_sahara.rst:5 +msgid "OpenStack Data processing service" +msgstr "" + +#: ../common/get_started_sahara.rst:6 +msgid "" +"The Data processing service for OpenStack (sahara) aims to provide users " +"with a simple means to provision data processing (Hadoop, Spark) clusters by " +"specifying several parameters like Hadoop version, cluster topology, node " +"hardware details and a few more. After a user fills in all the parameters, " +"the Data processing service deploys the cluster in a few minutes. Sahara " +"also provides a means to scale already provisioned clusters by adding/" +"removing worker nodes on demand." +msgstr "" + +#: ../common/get_started_sahara.rst:7 +msgid "" +"The Data processing service for OpenStack (sahara) aims to provide users " +"with a simple means to provision data processing (Hadoop, Spark) clusters by " +"specifying several parameters like Hadoop version, cluster topology, node " +"hardware details and a few more. After a user fills in all the parameters, " +"the Data processing service deploys the cluster in a few minutes. Sahara " +"also provides a means to scale already provisioned clusters by adding or " +"removing worker nodes on demand." +msgstr "" + +#: ../common/get_started_sahara.rst:14 ../common/get_started_sahara.rst:15 +msgid "The solution addresses the following use cases:" +msgstr "" + +#: ../common/get_started_sahara.rst:16 ../common/get_started_sahara.rst:17 +msgid "" +"Fast provisioning of Hadoop clusters on OpenStack for development and QA." +msgstr "" + +#: ../common/get_started_sahara.rst:19 ../common/get_started_sahara.rst:20 +msgid "" +"Utilization of unused compute power from general purpose OpenStack IaaS " +"cloud." +msgstr "" + +#: ../common/get_started_sahara.rst:22 ../common/get_started_sahara.rst:23 +msgid "Analytics-as-a-Service for ad-hoc or bursty analytic workloads." +msgstr "" + +#: ../common/get_started_sahara.rst:24 ../common/get_started_sahara.rst:25 +msgid "Key features are:" +msgstr "" + +#: ../common/get_started_sahara.rst:26 ../common/get_started_sahara.rst:27 +msgid "Designed as an OpenStack component." +msgstr "" + +#: ../common/get_started_sahara.rst:28 ../common/get_started_sahara.rst:29 +msgid "" +"Managed through REST API with UI available as part of OpenStack dashboard." +msgstr "" + +#: ../common/get_started_sahara.rst:31 ../common/get_started_sahara.rst:32 +msgid "Support for different Hadoop distributions:" +msgstr "" + +#: ../common/get_started_sahara.rst:33 ../common/get_started_sahara.rst:34 +msgid "Pluggable system of Hadoop installation engines." +msgstr "" + +#: ../common/get_started_sahara.rst:35 ../common/get_started_sahara.rst:36 +msgid "" +"Integration with vendor specific management tools, such as Apache Ambari or " +"Cloudera Management Console." +msgstr "" + +#: ../common/get_started_sahara.rst:38 ../common/get_started_sahara.rst:39 +msgid "" +"Predefined templates of Hadoop configurations with the ability to modify " +"parameters." +msgstr "" + +#: ../common/get_started_sahara.rst:41 ../common/get_started_sahara.rst:42 +msgid "User-friendly UI for ad-hoc analytics queries based on Hive or Pig." +msgstr "" + +#: ../common/get_started_storage_concepts.rst:0 +msgid "Storage types" +msgstr "" + +#: ../common/get_started_storage_concepts.rst:3 +#: ../common/get_started_storage_concepts.rst:4 +msgid "Storage concepts" +msgstr "" + +#: ../common/get_started_storage_concepts.rst:5 +#: ../common/get_started_storage_concepts.rst:6 +msgid "The OpenStack stack uses the following storage types:" +msgstr "" + +#: ../common/get_started_storage_concepts.rst:11 +#: ../common/get_started_storage_concepts.rst:12 +msgid "On-instance / ephemeral" +msgstr "" + +#: ../common/get_started_storage_concepts.rst:12 +#: ../common/get_started_storage_concepts.rst:13 +msgid "Block storage (cinder)" +msgstr "" + +#: ../common/get_started_storage_concepts.rst:13 +#: ../common/get_started_storage_concepts.rst:14 +msgid "Object Storage (swift)" +msgstr "" + +#: ../common/get_started_storage_concepts.rst:14 +#: ../common/get_started_storage_concepts.rst:15 +msgid "Runs operating systems and provides scratch space" +msgstr "" + +#: ../common/get_started_storage_concepts.rst:15 +#: ../common/get_started_storage_concepts.rst:16 +msgid "Used for adding additional persistent storage to a virtual machine (VM)" +msgstr "" + +#: ../common/get_started_storage_concepts.rst:16 +#: ../common/get_started_storage_concepts.rst:17 +msgid "Used for storing virtual machine images and data" +msgstr "" + +#: ../common/get_started_storage_concepts.rst:17 +#: ../common/get_started_storage_concepts.rst:18 +msgid "Persists until VM is terminated" +msgstr "" + +#: ../common/get_started_storage_concepts.rst:18 +#: ../common/get_started_storage_concepts.rst:19 +#: ../common/get_started_storage_concepts.rst:20 +msgid "Persists until deleted" +msgstr "" + +#: ../common/get_started_storage_concepts.rst:20 +#: ../common/get_started_storage_concepts.rst:21 +#: ../common/get_started_storage_concepts.rst:22 +msgid "Access associated with a VM" +msgstr "" + +#: ../common/get_started_storage_concepts.rst:22 +#: ../common/get_started_storage_concepts.rst:23 +msgid "Available from anywhere" +msgstr "" + +#: ../common/get_started_storage_concepts.rst:23 +#: ../common/get_started_storage_concepts.rst:24 +msgid "Implemented as a filesystem underlying OpenStack Compute" +msgstr "" + +#: ../common/get_started_storage_concepts.rst:24 +#: ../common/get_started_storage_concepts.rst:25 +msgid "" +"Mounted via OpenStack Block Storage controlled protocol (for example, iSCSI)" +msgstr "" + +#: ../common/get_started_storage_concepts.rst:25 +#: ../common/get_started_storage_concepts.rst:26 +msgid "REST API" +msgstr "" + +#: ../common/get_started_storage_concepts.rst:26 +#: ../common/get_started_storage_concepts.rst:27 +#: ../common/get_started_storage_concepts.rst:28 +msgid "Encryption is available" +msgstr "" + +#: ../common/get_started_storage_concepts.rst:27 +#: ../common/get_started_storage_concepts.rst:29 +#: ../common/get_started_storage_concepts.rst:30 +msgid "Administrator configures size setting, based on flavors" +msgstr "" + +#: ../common/get_started_storage_concepts.rst:28 +#: ../common/get_started_storage_concepts.rst:30 +#: ../common/get_started_storage_concepts.rst:31 +msgid "Sizings based on need" +msgstr "" + +#: ../common/get_started_storage_concepts.rst:28 +#: ../common/get_started_storage_concepts.rst:29 +msgid "Work in progress - expected for the Mitaka release" +msgstr "" + +#: ../common/get_started_storage_concepts.rst:29 +#: ../common/get_started_storage_concepts.rst:31 +#: ../common/get_started_storage_concepts.rst:32 +msgid "Easily scalable for future growth" +msgstr "" + +#: ../common/get_started_storage_concepts.rst:30 +#: ../common/get_started_storage_concepts.rst:32 +#: ../common/get_started_storage_concepts.rst:33 +msgid "Example: 10 GB first disk, 30 GB/core second disk" +msgstr "" + +#: ../common/get_started_storage_concepts.rst:31 +#: ../common/get_started_storage_concepts.rst:33 +#: ../common/get_started_storage_concepts.rst:34 +msgid "Example: 1 TB \"extra hard drive\"" +msgstr "" + +#: ../common/get_started_storage_concepts.rst:32 +#: ../common/get_started_storage_concepts.rst:34 +#: ../common/get_started_storage_concepts.rst:35 +msgid "Example: 10s of TBs of data set storage" +msgstr "" + +#: ../common/get_started_storage_concepts.rst:36 +#: ../common/get_started_storage_concepts.rst:38 +#: ../common/get_started_storage_concepts.rst:39 +msgid "" +"*You cannot use OpenStack Object Storage like a traditional hard drive.* The " +"Object Storage relaxes some of the constraints of a POSIX-style file system " +"to get other gains. You can access the objects through an API which uses " +"HTTP. Subsequently you don't have to provide atomic operations (that is, " +"relying on eventual consistency), you can scale a storage system easily and " +"avoid a central point of failure." +msgstr "" + +#: ../common/get_started_storage_concepts.rst:44 +#: ../common/get_started_storage_concepts.rst:46 +#: ../common/get_started_storage_concepts.rst:47 +msgid "" +"*The OpenStack Image service is used to manage the virtual machine images in " +"an OpenStack cluster, not store them.* It provides an abstraction to " +"different methods for storage - a bridge to the storage, not the storage " +"itself." +msgstr "" + +#: ../common/get_started_storage_concepts.rst:49 +#: ../common/get_started_storage_concepts.rst:51 +#: ../common/get_started_storage_concepts.rst:52 +msgid "" +"*The OpenStack Object Storage can function on its own.* The Object Storage " +"(swift) product can be used independently of the Compute (nova) product." +msgstr "" + +#: ../common/get_started_telemetry.rst:3 ../common/get_started_telemetry.rst:4 +msgid "OpenStack Telemetry module" +msgstr "" + +#: ../common/get_started_telemetry.rst:4 +msgid "Telemetry module" +msgstr "" + +#: ../common/get_started_telemetry.rst:5 ../common/get_started_telemetry.rst:6 msgid "The Telemetry module performs the following functions:" msgstr "" -#: ../common/cli_manage_images.rst:157 +#: ../common/get_started_telemetry.rst:7 ../common/get_started_telemetry.rst:8 +msgid "Efficiently polls metering data related to OpenStack services." +msgstr "" + +#: ../common/get_started_telemetry.rst:9 +#: ../common/get_started_telemetry.rst:10 msgid "" -"The URL where the data for this image resides. For example, if the image " -"data is stored in swift, you could specify ``swift://account:key@example.com/" -"container/obj``." +"Collects event and metering data by monitoring notifications sent from " +"services." msgstr "" -#: ../common/glossary.rst:3783 ../common/glossary.rst:3790 -#: ../common/glossary.rst:3797 ../common/glossary.rst:3805 -#: ../common/glossary.rst:3794 -msgid "The Xen administrative API, which is supported by Compute." -msgstr "" - -#: ../common/app_support.rst:120 +#: ../common/get_started_telemetry.rst:12 +#: ../common/get_started_telemetry.rst:13 msgid "" -"The `OpenStack wiki `__ contains a broad range " -"of topics but some of the information can be difficult to find or is a few " -"pages deep. Fortunately, the wiki search feature enables you to search by " -"title or content. If you search for specific information, such as about " -"networking or OpenStack Compute, you can find a large amount of relevant " -"material. More is being added all the time, so be sure to check back often. " -"You can find the search box in the upper-right corner of any OpenStack wiki " -"page." +"Publishes collected data to various targets including data stores and " +"message queues." msgstr "" -#: ../common/app_support.rst:120 ../common/app_support.rst:117 -#: ../common/app_support.rst:115 +#: ../common/get_started_telemetry.rst:15 +#: ../common/get_started_telemetry.rst:16 +msgid "Creates alarms when collected data breaks defined rules." +msgstr "" + +#: ../common/get_started_telemetry.rst:17 +#: ../common/get_started_telemetry.rst:18 +msgid "The Telemetry module consists of the following components:" +msgstr "" + +#: ../common/get_started_telemetry.rst:20 +#: ../common/get_started_telemetry.rst:21 msgid "" -"The `OpenStack wiki `__ contains a broad range " -"of topics but some of the information can be difficult to find or is a few " -"pages deep. Fortunately, the wiki search feature enables you to search by " -"title or content. If you search for specific information, such as about " -"networking or OpenStack Compute, you can find a large amount of relevant " -"material. More is being added all the time, so be sure to check back often. " -"You can find the search box in the upper-right corner of any OpenStack wiki " -"page." +"Runs on each compute node and polls for resource utilization statistics. " +"There may be other types of agents in the future, but for now our focus is " +"creating the compute agent." msgstr "" -#: ../common/app_support.rst:86 +#: ../common/get_started_telemetry.rst:22 +#: ../common/get_started_telemetry.rst:23 +msgid "A compute agent (``ceilometer-agent-compute``)" +msgstr "" + +#: ../common/get_started_telemetry.rst:25 +#: ../common/get_started_telemetry.rst:26 msgid "" -"The `Training Guides `__ " -"offer software training for cloud administration and management." +"Runs on a central management server to poll for resource utilization " +"statistics for resources not tied to instances or compute nodes. Multiple " +"agents can be started to scale service horizontally." msgstr "" -#: ../common/nova_show_usage_statistics_for_hosts_instances.rst:49 +#: ../common/get_started_telemetry.rst:27 +#: ../common/get_started_telemetry.rst:28 +msgid "A central agent (``ceilometer-agent-central``)" +msgstr "" + +#: ../common/get_started_telemetry.rst:30 +#: ../common/get_started_telemetry.rst:31 msgid "" -"The ``cpu`` column shows the sum of the virtual CPUs for instances running " -"on the host." +"Runs on a central management server(s) and consumes messages from the " +"message queue(s) to build event and metering data." msgstr "" -#: ../common/nova_show_usage_statistics_for_hosts_instances.rst:55 +#: ../common/get_started_telemetry.rst:31 +#: ../common/get_started_telemetry.rst:32 +msgid "A notification agent (``ceilometer-agent-notification``)" +msgstr "" + +#: ../common/get_started_telemetry.rst:34 +#: ../common/get_started_telemetry.rst:35 msgid "" -"The ``disk_gb`` column shows the sum of the root and ephemeral disk sizes " -"(in GB) of the instances that run on the host." +"Runs on central management server(s) and dispatches collected telemetry data " +"to a data store or external consumer without modification." msgstr "" -#: ../common/cli_manage_volumes.rst:208 -msgid "The ``extend`` command does not return any output." +#: ../common/get_started_telemetry.rst:36 +#: ../common/get_started_telemetry.rst:37 +msgid "A collector (``ceilometer-collector``)" msgstr "" -#: ../common/nova_show_usage_statistics_for_hosts_instances.rst:52 +#: ../common/get_started_telemetry.rst:39 +#: ../common/get_started_telemetry.rst:40 msgid "" -"The ``memory_mb`` column shows the sum of the memory (in MB) allocated to " -"the instances that run on the host." +"Runs on one or more central management servers to determine when alarms fire " +"due to the associated statistic trend crossing a threshold over a sliding " +"time window." msgstr "" -#: ../common/conventions.rst:33 +#: ../common/get_started_telemetry.rst:41 +#: ../common/get_started_telemetry.rst:42 +msgid "An alarm evaluator (``ceilometer-alarm-evaluator``)" +msgstr "" + +#: ../common/get_started_telemetry.rst:44 +#: ../common/get_started_telemetry.rst:45 msgid "" -"The ``root`` user must run commands that are prefixed with the ``#`` prompt. " -"You can also prefix these commands with the :command:`sudo` command, if " -"available, to run them." +"Runs on one or more central management servers to allow alarms to be set " +"based on the threshold evaluation for a collection of samples." msgstr "" -#: ../common/cli_manage_volumes.rst:186 -msgid "The ``volume-detach`` command does not return any output." +#: ../common/get_started_telemetry.rst:45 +#: ../common/get_started_telemetry.rst:46 +msgid "An alarm notifier (``ceilometer-alarm-notifier``)" msgstr "" -#: ../common/support-compute.rst:85 +#: ../common/get_started_telemetry.rst:48 +#: ../common/get_started_telemetry.rst:49 msgid "" -"The `ask.openstack.org `_ site offers a place to " -"ask and answer questions, and you can also mark questions as frequently " -"asked questions. This section describes some errors people have posted " -"previously. Bugs are constantly being fixed, so online resources are a great " -"way to get the most up-to-date errors and fixes." +"Runs on one or more central management servers to provide data access from " +"the data store." msgstr "" -#: ../common/glossary.rst:2419 ../common/glossary.rst:2426 -#: ../common/glossary.rst:2425 ../common/glossary.rst:2431 -#: ../common/glossary.rst:2433 ../common/glossary.rst:2422 -msgid "" -"The `nova-network` worker daemon; provides services such as giving an IP " -"address to a booting nova instance." +#: ../common/get_started_telemetry.rst:49 +#: ../common/get_started_telemetry.rst:50 +msgid "An API server (``ceilometer-api``)" msgstr "" -#: ../common/glossary.rst:1130 +#: ../common/get_started_telemetry.rst:51 +#: ../common/get_started_telemetry.rst:52 msgid "" -"The ability to encrypt data at the file system, disk partition, or whole-" -"disk level. Supported within Compute VMs." +"These services communicate by using the OpenStack messaging bus. Only the " +"collector and API server have access to the data store." msgstr "" -#: ../common/glossary.rst:2253 ../common/glossary.rst:2260 -#: ../common/glossary.rst:2259 ../common/glossary.rst:2248 -msgid "" -"The ability to start new VM instances based on the actual memory usage of a " -"host, as opposed to basing the decision on the amount of RAM each running " -"instance thinks it has available. Also known as RAM overcommit." +#: ../common/get_started_with_openstack.rst:0 +msgid "OpenStack Services" msgstr "" -#: ../common/glossary.rst:2892 ../common/glossary.rst:2899 -#: ../common/glossary.rst:2906 ../common/glossary.rst:2908 -#: ../common/glossary.rst:2897 -msgid "" -"The ability to start new VM instances based on the actual memory usage of a " -"host, as opposed to basing the decision on the amount of RAM each running " -"instance thinks it has available. Also known as memory overcommit." +#: ../common/get_started_with_openstack.rst:5 +msgid "Get started with OpenStack" msgstr "" -#: ../common/glossary.rst:2153 ../common/glossary.rst:2159 +#: ../common/get_started_with_openstack.rst:7 +#: ../common/get_started_with_openstack.rst:15 msgid "" -"The ability within Compute to move running virtual machine instances from " -"one host to another with only a small service interruption during switchover." +"The OpenStack project is an open source cloud computing platform for all " +"types of clouds, which aims to be simple to implement, massively scalable, " +"and feature rich. Developers and cloud computing technologists from around " +"the world create the OpenStack project." +msgstr "" + +#: ../common/get_started_with_openstack.rst:12 +#: ../common/get_started_with_openstack.rst:20 +msgid "" +"OpenStack provides an Infrastructure-as-a-Service (IaaS) solution through a " +"set of interrelated services. Each service offers an application programming " +"interface (API) that facilitates this integration. Depending on your needs, " +"you can install some or all services." +msgstr "" + +#: ../common/get_started_with_openstack.rst:18 +#: ../common/get_started_with_openstack.rst:26 +msgid "" +"The following table describes the OpenStack services that make up the " +"OpenStack architecture:" +msgstr "" + +#: ../common/get_started_with_openstack.rst:26 +#: ../common/get_started_with_openstack.rst:34 +msgid "Project name" +msgstr "" + +#: ../common/get_started_with_openstack.rst:28 +#: ../common/get_started_with_openstack.rst:36 +msgid "`Dashboard `__" +msgstr "" + +#: ../common/get_started_with_openstack.rst:29 +#: ../common/get_started_with_openstack.rst:37 +msgid "`Horizon `__" +msgstr "" + +#: ../common/get_started_with_openstack.rst:30 +#: ../common/get_started_with_openstack.rst:38 +msgid "" +"Provides a web-based self-service portal to interact with underlying " +"OpenStack services, such as launching an instance, assigning IP addresses " +"and configuring access controls." +msgstr "" + +#: ../common/get_started_with_openstack.rst:33 +#: ../common/get_started_with_openstack.rst:41 +msgid "`Compute `__" +msgstr "" + +#: ../common/get_started_with_openstack.rst:34 +#: ../common/get_started_with_openstack.rst:42 +msgid "`Nova `__" +msgstr "" + +#: ../common/get_started_with_openstack.rst:35 +#: ../common/get_started_with_openstack.rst:43 +msgid "" +"Manages the lifecycle of compute instances in an OpenStack environment. " +"Responsibilities include spawning, scheduling and decommissioning of virtual " +"machines on demand." +msgstr "" + +#: ../common/get_started_with_openstack.rst:38 +#: ../common/get_started_with_openstack.rst:46 +msgid "" +"`Networking `__" +msgstr "" + +#: ../common/get_started_with_openstack.rst:39 +#: ../common/get_started_with_openstack.rst:47 +msgid "`Neutron `__" +msgstr "" + +#: ../common/get_started_with_openstack.rst:40 +#: ../common/get_started_with_openstack.rst:48 +msgid "" +"Enables Network-Connectivity-as-a-Service for other OpenStack services, such " +"as OpenStack Compute. Provides an API for users to define networks and the " +"attachments into them. Has a pluggable architecture that supports many " +"popular networking vendors and technologies." +msgstr "" + +#: ../common/get_started_with_openstack.rst:44 +#: ../common/get_started_with_openstack.rst:52 +msgid "" +"`Object Storage `__" +msgstr "" + +#: ../common/get_started_with_openstack.rst:45 +#: ../common/get_started_with_openstack.rst:53 +msgid "`Swift `__" +msgstr "" + +#: ../common/get_started_with_openstack.rst:46 +#: ../common/get_started_with_openstack.rst:54 +msgid "" +"Stores and retrieves arbitrary unstructured data objects via a RESTful, HTTP " +"based API. It is highly fault tolerant with its data replication and scale-" +"out architecture. Its implementation is not like a file server with " +"mountable directories. In this case, it writes objects and files to multiple " +"drives, ensuring the data is replicated across a server cluster." +msgstr "" + +#: ../common/get_started_with_openstack.rst:52 +#: ../common/get_started_with_openstack.rst:60 +msgid "" +"`Block Storage `__" +msgstr "" + +#: ../common/get_started_with_openstack.rst:53 +#: ../common/get_started_with_openstack.rst:61 +msgid "`Cinder `__" +msgstr "" + +#: ../common/get_started_with_openstack.rst:54 +#: ../common/get_started_with_openstack.rst:62 +msgid "" +"Provides persistent block storage to running instances. Its pluggable driver " +"architecture facilitates the creation and management of block storage " +"devices." +msgstr "" + +#: ../common/get_started_with_openstack.rst:57 +#: ../common/get_started_with_openstack.rst:65 +msgid "" +"`Identity service `__" +msgstr "" + +#: ../common/get_started_with_openstack.rst:58 +#: ../common/get_started_with_openstack.rst:66 +msgid "`Keystone `__" +msgstr "" + +#: ../common/get_started_with_openstack.rst:59 +#: ../common/get_started_with_openstack.rst:67 +msgid "" +"Provides an authentication and authorization service for other OpenStack " +"services. Provides a catalog of endpoints for all OpenStack services." +msgstr "" + +#: ../common/get_started_with_openstack.rst:62 +#: ../common/get_started_with_openstack.rst:70 +msgid "" +"`Image service `__" +msgstr "" + +#: ../common/get_started_with_openstack.rst:63 +#: ../common/get_started_with_openstack.rst:71 +msgid "`Glance `__" +msgstr "" + +#: ../common/get_started_with_openstack.rst:64 +#: ../common/get_started_with_openstack.rst:72 +msgid "" +"Stores and retrieves virtual machine disk images. OpenStack Compute makes " +"use of this during instance provisioning." +msgstr "" + +#: ../common/get_started_with_openstack.rst:66 +#: ../common/get_started_with_openstack.rst:74 +msgid "" +"`Telemetry `__" +msgstr "" + +#: ../common/get_started_with_openstack.rst:67 +#: ../common/get_started_with_openstack.rst:75 +msgid "`Ceilometer `__" +msgstr "" + +#: ../common/get_started_with_openstack.rst:68 +#: ../common/get_started_with_openstack.rst:76 +msgid "" +"Monitors and meters the OpenStack cloud for billing, benchmarking, " +"scalability, and statistical purposes." +msgstr "" + +#: ../common/get_started_with_openstack.rst:70 +#: ../common/get_started_with_openstack.rst:78 +msgid "" +"`Orchestration `__" +msgstr "" + +#: ../common/get_started_with_openstack.rst:71 +#: ../common/get_started_with_openstack.rst:79 +msgid "`Heat `__" +msgstr "" + +#: ../common/get_started_with_openstack.rst:72 +#: ../common/get_started_with_openstack.rst:80 +msgid "" +"Orchestrates multiple composite cloud applications by using either the " +"native HOT template format or the AWS CloudFormation template format, " +"through both an OpenStack-native REST API and a CloudFormation-compatible " +"Query API." +msgstr "" + +#: ../common/get_started_with_openstack.rst:76 +#: ../common/get_started_with_openstack.rst:84 +msgid "" +"`Database service `__" +msgstr "" + +#: ../common/get_started_with_openstack.rst:77 +#: ../common/get_started_with_openstack.rst:85 +msgid "`Trove `__" +msgstr "" + +#: ../common/get_started_with_openstack.rst:78 +#: ../common/get_started_with_openstack.rst:86 +msgid "" +"Provides scalable and reliable Cloud Database-as-a-Service functionality for " +"both relational and non-relational database engines." +msgstr "" + +#: ../common/get_started_with_openstack.rst:80 +#: ../common/get_started_with_openstack.rst:88 +msgid "" +"`Data processing service `__" +msgstr "" + +#: ../common/get_started_with_openstack.rst:81 +#: ../common/get_started_with_openstack.rst:89 +msgid "`Sahara `__" +msgstr "" + +#: ../common/get_started_with_openstack.rst:82 +#: ../common/get_started_with_openstack.rst:90 +msgid "" +"Provides capabilties to provision and scale Hadoop clusters in OpenStack by " +"specifying parameters like Hadoop version, cluster topology and nodes " +"hardware details." +msgstr "" + +#: ../common/get_started_with_openstack.rst:90 +msgid "" +"Provides capabilities to provision and scale Hadoop clusters in OpenStack by " +"specifying parameters like Hadoop version, cluster topology and nodes " +"hardware details." +msgstr "" + +#: ../common/glossary.rst:3 +msgid "Glossary" +msgstr "" + +#: ../common/glossary.rst:8 +msgid "" +"This glossary offers a list of terms and definitions to define a vocabulary " +"for OpenStack-related concepts." +msgstr "" + +#: ../common/glossary.rst:11 +msgid "" +"To add to OpenStack glossary, clone the `openstack/openstack-manuals " +"repository `__ " +"and update the source file :file:`doc/glossary/glossary-terms.xml` through " +"the OpenStack contribution process." +msgstr "" + +#: ../common/glossary.rst:16 +msgid "6to4" +msgstr "" + +#: ../common/glossary.rst:19 +msgid "" +"A mechanism that allows IPv6 packets to be transmitted over an IPv4 network, " +"providing a strategy for migrating to IPv6." +msgstr "" + +#: ../common/glossary.rst:22 +msgid "absolute limit" +msgstr "" + +#: ../common/glossary.rst:25 +msgid "" +"Impassable limits for guest VMs. Settings include total RAM size, maximum " +"number of vCPUs, and maximum disk size." +msgstr "" + +#: ../common/glossary.rst:27 +msgid "access control list" +msgstr "" + +#: ../common/glossary.rst:30 +msgid "" +"A list of permissions attached to an object. An ACL specifies which users or " +"system processes have access to objects. It also defines which operations " +"can be performed on specified objects. Each entry in a typical ACL specifies " +"a subject and an operation. For instance, the ACL entry `(Alice, delete)` " +"for a file gives Alice permission to delete the file." +msgstr "" + +#: ../common/glossary.rst:36 +msgid "access key" +msgstr "" + +#: ../common/glossary.rst:39 +msgid "Alternative term for an Amazon EC2 access key. See EC2 access key." +msgstr "" + +#: ../common/glossary.rst:41 +msgid "account" +msgstr "" + +#: ../common/glossary.rst:44 +msgid "" +"The Object Storage context of an account. Do not confuse with a user account " +"from an authentication service, such as Active Directory, /etc/passwd, " +"OpenLDAP, OpenStack Identity, and so on." +msgstr "" + +#: ../common/glossary.rst:47 +msgid "account auditor" +msgstr "" + +#: ../common/glossary.rst:50 +msgid "" +"Checks for missing replicas and incorrect or corrupted objects in a " +"specified Object Storage account by running queries against the back-end " +"SQLite database." +msgstr "" + +#: ../common/glossary.rst:53 +msgid "account database" +msgstr "" + +#: ../common/glossary.rst:56 +msgid "" +"A SQLite database that contains Object Storage accounts and related metadata " +"and that the accounts server accesses." +msgstr "" + +#: ../common/glossary.rst:58 +msgid "account reaper" +msgstr "" + +#: ../common/glossary.rst:61 +msgid "" +"An Object Storage worker that scans for and deletes account databases and " +"that the account server has marked for deletion." +msgstr "" + +#: ../common/glossary.rst:63 +msgid "account server" +msgstr "" + +#: ../common/glossary.rst:66 +msgid "" +"Lists containers in Object Storage and stores container information in the " +"account database." +msgstr "" + +#: ../common/glossary.rst:68 +msgid "account service" +msgstr "" + +#: ../common/glossary.rst:71 +msgid "" +"An Object Storage component that provides account services such as list, " +"create, modify, and audit. Do not confuse with OpenStack Identity service, " +"OpenLDAP, or similar user-account services." +msgstr "" + +#: ../common/glossary.rst:74 +msgid "accounting" +msgstr "" + +#: ../common/glossary.rst:77 +msgid "" +"The Compute service provides accounting information through the event " +"notification and system usage data facilities." +msgstr "" + +#: ../common/glossary.rst:79 +msgid "ACL" +msgstr "" + +#: ../common/glossary.rst:82 +msgid "See access control list." +msgstr "" + +#: ../common/glossary.rst:83 +msgid "active/active configuration" +msgstr "" + +#: ../common/glossary.rst:86 +msgid "" +"In a high-availability setup with an active/active configuration, several " +"systems share the load together and if one fails, the load is distributed to " +"the remaining systems." +msgstr "" + +#: ../common/glossary.rst:89 +msgid "Active Directory" +msgstr "" + +#: ../common/glossary.rst:92 +msgid "" +"Authentication and identity service by Microsoft, based on LDAP. Supported " +"in OpenStack." +msgstr "" + +#: ../common/glossary.rst:94 +msgid "active/passive configuration" +msgstr "" + +#: ../common/glossary.rst:97 +msgid "" +"In a high-availability setup with an active/passive configuration, systems " +"are set up to bring additional resources online to replace those that have " +"failed." +msgstr "" + +#: ../common/glossary.rst:100 +msgid "address pool" +msgstr "" + +#: ../common/glossary.rst:103 +msgid "" +"A group of fixed and/or floating IP addresses that are assigned to a project " +"and can be used by or assigned to the VM instances in a project." +msgstr "" + +#: ../common/glossary.rst:106 +msgid "admin API" +msgstr "" + +#: ../common/glossary.rst:109 +msgid "" +"A subset of API calls that are accessible to authorized administrators and " +"are generally not accessible to end users or the public Internet. They can " +"exist as a separate service (keystone) or can be a subset of another API " +"(nova)." +msgstr "" + +#: ../common/glossary.rst:113 +msgid "admin server" +msgstr "" + +#: ../common/glossary.rst:116 +msgid "" +"In the context of the Identity service, the worker process that provides " +"access to the admin API." +msgstr "" + +#: ../common/glossary.rst:118 +msgid "Advanced Message Queuing Protocol (AMQP)" +msgstr "" + +#: ../common/glossary.rst:121 +msgid "" +"The open standard messaging protocol used by OpenStack components for intra-" +"service communications, provided by RabbitMQ, Qpid, or ZeroMQ." +msgstr "" + +#: ../common/glossary.rst:124 +msgid "Advanced RISC Machine (ARM)" +msgstr "" + +#: ../common/glossary.rst:127 +msgid "" +"Lower power consumption CPU often found in mobile and embedded devices. " +"Supported by OpenStack." +msgstr "" + +#: ../common/glossary.rst:129 +msgid "alert" +msgstr "" + +#: ../common/glossary.rst:132 +msgid "" +"The Compute service can send alerts through its notification system, which " +"includes a facility to create custom notification drivers. Alerts can be " +"sent to and displayed on the horizon dashboard." +msgstr "" + +#: ../common/glossary.rst:136 +msgid "allocate" +msgstr "" + +#: ../common/glossary.rst:139 +msgid "" +"The process of taking a floating IP address from the address pool so it can " +"be associated with a fixed IP on a guest VM instance." +msgstr "" + +#: ../common/glossary.rst:142 +msgid "Amazon Kernel Image (AKI)" +msgstr "" + +#: ../common/glossary.rst:145 ../common/glossary.rst:150 +#: ../common/glossary.rst:155 +msgid "Both a VM container format and disk format. Supported by Image service." +msgstr "" + +#: ../common/glossary.rst:147 +msgid "Amazon Machine Image (AMI)" +msgstr "" + +#: ../common/glossary.rst:152 +msgid "Amazon Ramdisk Image (ARI)" +msgstr "" + +#: ../common/glossary.rst:157 +msgid "Anvil" +msgstr "" + +#: ../common/glossary.rst:160 +msgid "" +"A project that ports the shell script-based project named DevStack to Python." +msgstr "" + +#: ../common/glossary.rst:162 +msgid "Apache" +msgstr "" + +#: ../common/glossary.rst:165 +msgid "" +"The Apache Software Foundation supports the Apache community of open-source " +"software projects. These projects provide software products for the public " +"good." +msgstr "" + +#: ../common/glossary.rst:168 +msgid "Apache License 2.0" +msgstr "" + +#: ../common/glossary.rst:171 +msgid "" +"All OpenStack core projects are provided under the terms of the Apache " +"License 2.0 license." +msgstr "" + +#: ../common/glossary.rst:173 +msgid "Apache Web Server" +msgstr "" + +#: ../common/glossary.rst:176 +msgid "The most common web server software currently used on the Internet." +msgstr "" + +#: ../common/glossary.rst:178 +msgid "API" +msgstr "" + +#: ../common/glossary.rst:181 +msgid "Application programming interface." +msgstr "" + +#: ../common/glossary.rst:182 +msgid "API endpoint" +msgstr "" + +#: ../common/glossary.rst:185 +msgid "" +"The daemon, worker, or service that a client communicates with to access an " +"API. API endpoints can provide any number of services, such as " +"authentication, sales data, performance meters, Compute VM commands, census " +"data, and so on." +msgstr "" + +#: ../common/glossary.rst:189 +msgid "API extension" +msgstr "" + +#: ../common/glossary.rst:192 +msgid "Custom modules that extend some OpenStack core APIs." +msgstr "" + +#: ../common/glossary.rst:193 +msgid "API extension plug-in" +msgstr "" + +#: ../common/glossary.rst:196 +msgid "Alternative term for a Networking plug-in or Networking API extension." +msgstr "" + +#: ../common/glossary.rst:198 +msgid "API key" +msgstr "" + +#: ../common/glossary.rst:201 +msgid "Alternative term for an API token." +msgstr "" + +#: ../common/glossary.rst:202 +msgid "API server" +msgstr "" + +#: ../common/glossary.rst:205 +msgid "Any node running a daemon or worker that provides an API endpoint." +msgstr "" + +#: ../common/glossary.rst:207 +msgid "API token" +msgstr "" + +#: ../common/glossary.rst:210 +msgid "" +"Passed to API requests and used by OpenStack to verify that the client is " +"authorized to run the requested operation." +msgstr "" + +#: ../common/glossary.rst:212 +msgid "API version" +msgstr "" + +#: ../common/glossary.rst:215 +msgid "" +"In OpenStack, the API version for a project is part of the URL. For " +"example, :file:`example.com/nova/v1/foobar`." +msgstr "" + +#: ../common/glossary.rst:217 +msgid "applet" +msgstr "" + +#: ../common/glossary.rst:220 +msgid "A Java program that can be embedded into a web page." +msgstr "" + +#: ../common/glossary.rst:221 +msgid "Application Programming Interface (API)" +msgstr "" + +#: ../common/glossary.rst:224 +msgid "" +"A collection of specifications used to access a service, application, or " +"program. Includes service calls, required parameters for each call, and the " +"expected return values." +msgstr "" + +#: ../common/glossary.rst:230 +msgid "" +"OpenStack project that provides an application catalog service so that users " +"can compose and deploy composite environments on an application abstraction " +"level while managing the application lifecycle. The code name of the project " +"is murano." +msgstr "" + +#: ../common/glossary.rst:235 +msgid "application server" +msgstr "" + +#: ../common/glossary.rst:238 +msgid "" +"A piece of software that makes available another piece of software over a " +"network." +msgstr "" + +#: ../common/glossary.rst:240 +msgid "Application Service Provider (ASP)" +msgstr "" + +#: ../common/glossary.rst:243 +msgid "" +"Companies that rent specialized applications that help businesses and " +"organizations provide additional services with lower cost." +msgstr "" + +#: ../common/glossary.rst:246 +msgid "Address Resolution Protocol (ARP)" +msgstr "" + +#: ../common/glossary.rst:249 +msgid "" +"The protocol by which layer-3 IP addresses are resolved into layer-2 link " +"local addresses." +msgstr "" + +#: ../common/glossary.rst:251 +msgid "arptables" +msgstr "" + +#: ../common/glossary.rst:254 +msgid "" +"Tool used for maintaining Address Resolution Protocol packet filter rules in " +"the Linux kernel firewall modules. Used along with iptables, ebtables, and " +"ip6tables in Compute to provide firewall services for VMs." +msgstr "" + +#: ../common/glossary.rst:258 +msgid "associate" +msgstr "" + +#: ../common/glossary.rst:261 +msgid "" +"The process associating a Compute floating IP address with a fixed IP " +"address." +msgstr "" + +#: ../common/glossary.rst:263 +msgid "Asynchronous JavaScript and XML (AJAX)" +msgstr "" + +#: ../common/glossary.rst:266 +msgid "" +"A group of interrelated web development techniques used on the client-side " +"to create asynchronous web applications. Used extensively in horizon." +msgstr "" + +#: ../common/glossary.rst:269 +msgid "ATA over Ethernet (AoE)" +msgstr "" + +#: ../common/glossary.rst:272 +msgid "A disk storage protocol tunneled within Ethernet." +msgstr "" + +#: ../common/glossary.rst:273 +msgid "attach" +msgstr "" + +#: ../common/glossary.rst:276 +msgid "" +"The process of connecting a VIF or vNIC to a L2 network in Networking. In " +"the context of Compute, this process connects a storage volume to an " +"instance." +msgstr "" + +#: ../common/glossary.rst:279 +msgid "attachment (network)" +msgstr "" + +#: ../common/glossary.rst:282 +msgid "" +"Association of an interface ID to a logical port. Plugs an interface into a " +"port." +msgstr "" + +#: ../common/glossary.rst:284 +msgid "auditing" +msgstr "" + +#: ../common/glossary.rst:287 +msgid "Provided in Compute through the system usage data facility." +msgstr "" + +#: ../common/glossary.rst:289 +msgid "auditor" +msgstr "" + +#: ../common/glossary.rst:292 +msgid "" +"A worker process that verifies the integrity of Object Storage objects, " +"containers, and accounts. Auditors is the collective term for the Object " +"Storage account auditor, container auditor, and object auditor." +msgstr "" + +#: ../common/glossary.rst:296 +msgid "Austin" +msgstr "" + +#: ../common/glossary.rst:299 +msgid "" +"The code name for the initial release of OpenStack. The first design summit " +"took place in Austin, Texas, US." +msgstr "" + +#: ../common/glossary.rst:302 +msgid "auth node" +msgstr "" + +#: ../common/glossary.rst:305 +msgid "Alternative term for an Object Storage authorization node." +msgstr "" + +#: ../common/glossary.rst:307 +msgid "authentication" +msgstr "" + +#: ../common/glossary.rst:310 +msgid "" +"The process that confirms that the user, process, or client is really who " +"they say they are through private key, secret token, password, fingerprint, " +"or similar method." +msgstr "" + +#: ../common/glossary.rst:313 +msgid "authentication token" +msgstr "" + +#: ../common/glossary.rst:316 +msgid "" +"A string of text provided to the client after authentication. Must be " +"provided by the user or process in subsequent requests to the API endpoint." +msgstr "" + +#: ../common/glossary.rst:319 +msgid "AuthN" +msgstr "" + +#: ../common/glossary.rst:322 +msgid "The Identity service component that provides authentication services." +msgstr "" + +#: ../common/glossary.rst:324 +msgid "authorization" msgstr "" #: ../common/glossary.rst:327 @@ -8629,6 +5201,110 @@ msgid "" "perform an action." msgstr "" +#: ../common/glossary.rst:329 +msgid "authorization node" +msgstr "" + +#: ../common/glossary.rst:332 +msgid "An Object Storage node that provides authorization services." +msgstr "" + +#: ../common/glossary.rst:334 +msgid "AuthZ" +msgstr "" + +#: ../common/glossary.rst:337 +msgid "The Identity component that provides high-level authorization services." +msgstr "" + +#: ../common/glossary.rst:339 +msgid "Auto ACK" +msgstr "" + +#: ../common/glossary.rst:342 +msgid "" +"Configuration setting within RabbitMQ that enables or disables message " +"acknowledgment. Enabled by default." +msgstr "" + +#: ../common/glossary.rst:344 +msgid "auto declare" +msgstr "" + +#: ../common/glossary.rst:347 +msgid "" +"A Compute RabbitMQ setting that determines whether a message exchange is " +"automatically created when the program starts." +msgstr "" + +#: ../common/glossary.rst:349 +msgid "availability zone" +msgstr "" + +#: ../common/glossary.rst:352 +msgid "" +"An Amazon EC2 concept of an isolated area that is used for fault tolerance. " +"Do not confuse with an OpenStack Compute zone or cell." +msgstr "" + +#: ../common/glossary.rst:355 +msgid "AWS" +msgstr "" + +#: ../common/glossary.rst:358 +msgid "Amazon Web Services." +msgstr "" + +#: ../common/glossary.rst:359 +msgid "AWS CloudFormation template" +msgstr "" + +#: ../common/glossary.rst:362 +msgid "" +"AWS CloudFormation allows AWS users to create and manage a collection of " +"related resources. The Orchestration module supports a CloudFormation-" +"compatible format (CFN)." +msgstr "" + +#: ../common/glossary.rst:365 +msgid "back end" +msgstr "" + +#: ../common/glossary.rst:368 +msgid "" +"Interactions and processes that are obfuscated from the user, such as " +"Compute volume mount, data transmission to an iSCSI target by a daemon, or " +"Object Storage object integrity checks." +msgstr "" + +#: ../common/glossary.rst:371 +msgid "back-end catalog" +msgstr "" + +#: ../common/glossary.rst:374 +msgid "" +"The storage method used by the Identity service catalog service to store and " +"retrieve information about API endpoints that are available to the client. " +"Examples include a SQL database, LDAP database, or KVS back end." +msgstr "" + +#: ../common/glossary.rst:378 +msgid "back-end store" +msgstr "" + +#: ../common/glossary.rst:381 +msgid "" +"The persistent data store used to save and retrieve information for a " +"service, such as lists of Object Storage objects, current state of guest " +"VMs, lists of user names, and so on. Also, the method that the Image service " +"uses to get and store VM images. Options include Object Storage, local file " +"system, S3, and HTTP." +msgstr "" + +#: ../common/glossary.rst:386 +msgid "bandwidth" +msgstr "" + #: ../common/glossary.rst:389 msgid "" "The amount of available data used by communication resources, such as the " @@ -8636,17 +5312,2575 @@ msgid "" "the amount of data available to download." msgstr "" +#: ../common/glossary.rst:395 +msgid "Code name of the key management service for OpenStack." +msgstr "" + +#: ../common/glossary.rst:396 +msgid "bare" +msgstr "" + +#: ../common/glossary.rst:399 +msgid "" +"An Image service container format that indicates that no container exists " +"for the VM image." +msgstr "" + +#: ../common/glossary.rst:401 +msgid "Bare metal service" +msgstr "" + +#: ../common/glossary.rst:404 +msgid "" +"OpenStack project that provisions bare metal, as opposed to virtual, " +"machines. The code name for the project is ironic." +msgstr "" + +#: ../common/glossary.rst:406 +msgid "base image" +msgstr "" + +#: ../common/glossary.rst:409 +msgid "An OpenStack-provided image." +msgstr "" + +#: ../common/glossary.rst:410 +msgid "Bell-LaPadula model" +msgstr "" + +#: ../common/glossary.rst:413 +msgid "" +"A security model that focuses on data confidentiality and controlled access " +"to classified information. This model divide the entities into subjects and " +"objects. The clearance of a subject is compared to the classification of the " +"object to determine if the subject is authorized for the specific access " +"mode. The clearance or classification scheme is expressed in terms of a " +"lattice." +msgstr "" + +#: ../common/glossary.rst:419 +msgid "Benchmark service" +msgstr "" + +#: ../common/glossary.rst:422 +msgid "" +"OpenStack project that provides a framework for performance analysis and " +"benchmarking of individual OpenStack components as well as full production " +"OpenStack cloud deployments. The code name of the project is rally." +msgstr "" + +#: ../common/glossary.rst:426 +msgid "Bexar" +msgstr "" + +#: ../common/glossary.rst:429 +msgid "" +"A grouped release of projects related to OpenStack that came out in February " +"of 2011. It included only Compute (nova) and Object Storage (swift). Bexar " +"is the code name for the second release of OpenStack. The design summit took " +"place in San Antonio, Texas, US, which is the county seat for Bexar county." +msgstr "" + +#: ../common/glossary.rst:435 +msgid "binary" +msgstr "" + +#: ../common/glossary.rst:438 +msgid "" +"Information that consists solely of ones and zeroes, which is the language " +"of computers." +msgstr "" + +#: ../common/glossary.rst:440 +msgid "bit" +msgstr "" + +#: ../common/glossary.rst:443 +msgid "" +"A bit is a single digit number that is in base of 2 (either a zero or one). " +"Bandwidth usage is measured in bits per second." +msgstr "" + +#: ../common/glossary.rst:445 +msgid "bits per second (BPS)" +msgstr "" + +#: ../common/glossary.rst:448 +msgid "" +"The universal measurement of how quickly data is transferred from place to " +"place." +msgstr "" + +#: ../common/glossary.rst:450 +msgid "block device" +msgstr "" + +#: ../common/glossary.rst:453 +msgid "" +"A device that moves data in the form of blocks. These device nodes interface " +"the devices, such as hard disks, CD-ROM drives, flash drives, and other " +"addressable regions of memory." +msgstr "" + +#: ../common/glossary.rst:456 +msgid "block migration" +msgstr "" + +#: ../common/glossary.rst:459 +msgid "" +"A method of VM live migration used by KVM to evacuate instances from one " +"host to another with very little downtime during a user-initiated " +"switchover. Does not require shared storage. Supported by Compute." +msgstr "" + +#: ../common/glossary.rst:466 +msgid "" +"The OpenStack core project that enables management of volumes, volume " +"snapshots, and volume types. The project name of Block Storage is cinder." +msgstr "" + +#: ../common/glossary.rst:469 +msgid "Block Storage API" +msgstr "" + +#: ../common/glossary.rst:472 +msgid "" +"An API on a separate endpoint for attaching, detaching, and creating block " +"storage for compute VMs." +msgstr "" + +#: ../common/glossary.rst:475 +msgid "BMC" +msgstr "" + +#: ../common/glossary.rst:478 +msgid "" +"Baseboard Management Controller. The intelligence in the IPMI architecture, " +"which is a specialized micro-controller that is embedded on the motherboard " +"of a computer and acts as a server. Manages the interface between system " +"management software and platform hardware." +msgstr "" + +#: ../common/glossary.rst:483 +msgid "bootable disk image" +msgstr "" + +#: ../common/glossary.rst:486 +msgid "A type of VM image that exists as a single, bootable file." +msgstr "" + +#: ../common/glossary.rst:488 +msgid "Bootstrap Protocol (BOOTP)" +msgstr "" + +#: ../common/glossary.rst:491 +msgid "" +"A network protocol used by a network client to obtain an IP address from a " +"configuration server. Provided in Compute through the dnsmasq daemon when " +"using either the FlatDHCP manager or VLAN manager network manager." +msgstr "" + +#: ../common/glossary.rst:495 +msgid "Border Gateway Protocol (BGP)" +msgstr "" + +#: ../common/glossary.rst:498 +msgid "" +"The Border Gateway Protocol is a dynamic routing protocol that connects " +"autonomous systems. Considered the backbone of the Internet, this protocol " +"connects disparate networks to form a larger network." +msgstr "" + +#: ../common/glossary.rst:502 +msgid "browser" +msgstr "" + +#: ../common/glossary.rst:505 +msgid "" +"Any client software that enables a computer or device to access the Internet." +msgstr "" + +#: ../common/glossary.rst:507 +msgid "builder file" +msgstr "" + +#: ../common/glossary.rst:510 +msgid "" +"Contains configuration information that Object Storage uses to reconfigure a " +"ring or to re-create it from scratch after a serious failure." +msgstr "" + +#: ../common/glossary.rst:513 +msgid "bursting" +msgstr "" + +#: ../common/glossary.rst:516 +msgid "" +"The practice of utilizing a secondary environment to elastically build " +"instances on-demand when the primary environment is resource constrained." +msgstr "" + +#: ../common/glossary.rst:519 +msgid "button class" +msgstr "" + +#: ../common/glossary.rst:522 +msgid "" +"A group of related button types within horizon. Buttons to start, stop, and " +"suspend VMs are in one class. Buttons to associate and disassociate floating " +"IP addresses are in another class, and so on." +msgstr "" + +#: ../common/glossary.rst:526 +msgid "byte" +msgstr "" + +#: ../common/glossary.rst:529 +msgid "" +"Set of bits that make up a single character; there are usually 8 bits to a " +"byte." +msgstr "" + +#: ../common/glossary.rst:531 +msgid "CA" +msgstr "" + +#: ../common/glossary.rst:534 +msgid "" +"Certificate Authority or Certification Authority. In cryptography, an entity " +"that issues digital certificates. The digital certificate certifies the " +"ownership of a public key by the named subject of the certificate. This " +"enables others (relying parties) to rely upon signatures or assertions made " +"by the private key that corresponds to the certified public key. In this " +"model of trust relationships, a CA is a trusted third party for both the " +"subject (owner) of the certificate and the party relying upon the " +"certificate. CAs are characteristic of many public key infrastructure (PKI) " +"schemes." +msgstr "" + +#: ../common/glossary.rst:544 +msgid "cache pruner" +msgstr "" + +#: ../common/glossary.rst:547 +msgid "" +"A program that keeps the Image service VM image cache at or below its " +"configured maximum size." +msgstr "" + +#: ../common/glossary.rst:549 +msgid "Cactus" +msgstr "" + +#: ../common/glossary.rst:552 +msgid "" +"An OpenStack grouped release of projects that came out in the spring of " +"2011. It included Compute (nova), Object Storage (swift), and the Image " +"service (glance). Cactus is a city in Texas, US and is the code name for the " +"third release of OpenStack. When OpenStack releases went from three to six " +"months long, the code name of the release changed to match a geography " +"nearest the previous summit." +msgstr "" + +#: ../common/glossary.rst:560 +msgid "CADF" +msgstr "" + +#: ../common/glossary.rst:563 +msgid "" +"Cloud Auditing Data Federation (CADF) is a specification for audit event " +"data. CADF is supported by OpenStack Identity." +msgstr "" + +#: ../common/glossary.rst:566 +msgid "CALL" +msgstr "" + +#: ../common/glossary.rst:569 +msgid "" +"One of the RPC primitives used by the OpenStack message queue software. " +"Sends a message and waits for a response." +msgstr "" + +#: ../common/glossary.rst:571 +msgid "capability" +msgstr "" + +#: ../common/glossary.rst:574 +msgid "" +"Defines resources for a cell, including CPU, storage, and networking. Can " +"apply to the specific services within a cell or a whole cell." +msgstr "" + +#: ../common/glossary.rst:577 +msgid "capacity cache" +msgstr "" + +#: ../common/glossary.rst:580 +msgid "" +"A Compute back-end database table that contains the current workload, amount " +"of free RAM, and number of VMs running on each host. Used to determine on " +"which VM a host starts." +msgstr "" + +#: ../common/glossary.rst:583 +msgid "capacity updater" +msgstr "" + +#: ../common/glossary.rst:586 +msgid "" +"A notification driver that monitors VM instances and updates the capacity " +"cache as needed." +msgstr "" + +#: ../common/glossary.rst:588 +msgid "CAST" +msgstr "" + +#: ../common/glossary.rst:591 +msgid "" +"One of the RPC primitives used by the OpenStack message queue software. " +"Sends a message and does not wait for a response." +msgstr "" + +#: ../common/glossary.rst:593 +msgid "catalog" +msgstr "" + +#: ../common/glossary.rst:596 +msgid "" +"A list of API endpoints that are available to a user after authentication " +"with the Identity service." +msgstr "" + +#: ../common/glossary.rst:598 +msgid "catalog service" +msgstr "" + +#: ../common/glossary.rst:601 +msgid "" +"An Identity service that lists API endpoints that are available to a user " +"after authentication with the Identity service." +msgstr "" + +#: ../common/glossary.rst:606 +msgid "" +"The project name for the Telemetry service, which is an integrated project " +"that provides metering and measuring facilities for OpenStack." +msgstr "" + +#: ../common/glossary.rst:609 +msgid "cell" +msgstr "" + +#: ../common/glossary.rst:612 +msgid "" +"Provides logical partitioning of Compute resources in a child and parent " +"relationship. Requests are passed from parent cells to child cells if the " +"parent cannot provide the requested resource." +msgstr "" + +#: ../common/glossary.rst:616 +msgid "cell forwarding" +msgstr "" + +#: ../common/glossary.rst:619 +msgid "" +"A Compute option that enables parent cells to pass resource requests to " +"child cells if the parent cannot provide the requested resource." +msgstr "" + +#: ../common/glossary.rst:622 +msgid "cell manager" +msgstr "" + +#: ../common/glossary.rst:625 +msgid "" +"The Compute component that contains a list of the current capabilities of " +"each host within the cell and routes requests as appropriate." +msgstr "" + +#: ../common/glossary.rst:628 +msgid "CentOS" +msgstr "" + +#: ../common/glossary.rst:631 ../common/glossary.rst:1004 +#: ../common/glossary.rst:2614 ../common/glossary.rst:2618 +#: ../common/glossary.rst:2621 ../common/glossary.rst:2627 +#: ../common/glossary.rst:2629 ../common/glossary.rst:2948 +#: ../common/glossary.rst:2953 ../common/glossary.rst:2955 +#: ../common/glossary.rst:2962 ../common/glossary.rst:2964 +#: ../common/glossary.rst:3370 ../common/glossary.rst:3377 +#: ../common/glossary.rst:3381 ../common/glossary.rst:3384 +#: ../common/glossary.rst:3392 +msgid "A Linux distribution that is compatible with OpenStack." +msgstr "" + +#: ../common/glossary.rst:632 +msgid "Ceph" +msgstr "" + +#: ../common/glossary.rst:635 +msgid "" +"Massively scalable distributed storage system that consists of an object " +"store, block store, and POSIX-compatible distributed file system. Compatible " +"with OpenStack." +msgstr "" + +#: ../common/glossary.rst:638 +msgid "CephFS" +msgstr "" + +#: ../common/glossary.rst:641 +msgid "The POSIX-compliant file system provided by Ceph." +msgstr "" + +#: ../common/glossary.rst:642 +msgid "certificate authority" +msgstr "" + +#: ../common/glossary.rst:645 +msgid "" +"A simple certificate authority provided by Compute for cloudpipe VPNs and VM " +"image decryption." +msgstr "" + +#: ../common/glossary.rst:647 +msgid "Challenge-Handshake Authentication Protocol (CHAP)" +msgstr "" + +#: ../common/glossary.rst:650 +msgid "An iSCSI authentication method supported by Compute." +msgstr "" + +#: ../common/glossary.rst:651 +msgid "chance scheduler" +msgstr "" + +#: ../common/glossary.rst:654 +msgid "" +"A scheduling method used by Compute that randomly chooses an available host " +"from the pool." +msgstr "" + +#: ../common/glossary.rst:656 +msgid "changes since" +msgstr "" + +#: ../common/glossary.rst:659 +msgid "" +"A Compute API parameter that downloads changes to the requested item since " +"your last request, instead of downloading a new, fresh set of data and " +"comparing it against the old data." +msgstr "" + +#: ../common/glossary.rst:662 +msgid "Chef" +msgstr "" + +#: ../common/glossary.rst:665 +msgid "" +"An operating system configuration management tool supporting OpenStack " +"deployments." +msgstr "" + +#: ../common/glossary.rst:667 +msgid "child cell" +msgstr "" + +#: ../common/glossary.rst:670 +msgid "" +"If a requested resource such as CPU time, disk storage, or memory is not " +"available in the parent cell, the request is forwarded to its associated " +"child cells. If the child cell can fulfill the request, it does. Otherwise, " +"it attempts to pass the request to any of its children." +msgstr "" + +#: ../common/glossary.rst:678 +msgid "A core OpenStack project that provides block storage services for VMs." +msgstr "" + +#: ../common/glossary.rst:680 +msgid "CirrOS" +msgstr "" + +#: ../common/glossary.rst:683 +msgid "" +"A minimal Linux distribution designed for use as a test image on clouds such " +"as OpenStack." +msgstr "" + +#: ../common/glossary.rst:685 +msgid "Cisco neutron plug-in" +msgstr "" + +#: ../common/glossary.rst:688 +msgid "" +"A Networking plug-in for Cisco devices and technologies, including UCS and " +"Nexus." +msgstr "" + +#: ../common/glossary.rst:690 +msgid "cloud architect" +msgstr "" + +#: ../common/glossary.rst:693 +msgid "A person who plans, designs, and oversees the creation of clouds." +msgstr "" + +#: ../common/glossary.rst:695 +msgid "cloud computing" +msgstr "" + +#: ../common/glossary.rst:698 +msgid "" +"A model that enables access to a shared pool of configurable computing " +"resources, such as networks, servers, storage, applications, and services, " +"that can be rapidly provisioned and released with minimal management effort " +"or service provider interaction." +msgstr "" + +#: ../common/glossary.rst:702 +msgid "cloud controller" +msgstr "" + +#: ../common/glossary.rst:705 +msgid "" +"Collection of Compute components that represent the global state of the " +"cloud; talks to services, such as Identity authentication, Object Storage, " +"and node/storage workers through a queue." +msgstr "" + +#: ../common/glossary.rst:709 +msgid "cloud controller node" +msgstr "" + +#: ../common/glossary.rst:712 +msgid "" +"A node that runs network, volume, API, scheduler, and image services. Each " +"service may be broken out into separate nodes for scalability or " +"availability." +msgstr "" + +#: ../common/glossary.rst:715 +msgid "Cloud Data Management Interface (CDMI)" +msgstr "" + +#: ../common/glossary.rst:718 +msgid "" +"SINA standard that defines a RESTful API for managing objects in the cloud, " +"currently unsupported in OpenStack." +msgstr "" + +#: ../common/glossary.rst:720 +msgid "Cloud Infrastructure Management Interface (CIMI)" +msgstr "" + +#: ../common/glossary.rst:723 +msgid "" +"An in-progress specification for cloud management. Currently unsupported in " +"OpenStack." +msgstr "" + +#: ../common/glossary.rst:725 +msgid "cloud-init" +msgstr "" + +#: ../common/glossary.rst:728 +msgid "" +"A package commonly installed in VM images that performs initialization of an " +"instance after boot using information that it retrieves from the metadata " +"service, such as the SSH public key and user data." +msgstr "" + +#: ../common/glossary.rst:732 +msgid "cloudadmin" +msgstr "" + +#: ../common/glossary.rst:735 +msgid "" +"One of the default roles in the Compute RBAC system. Grants complete system " +"access." +msgstr "" + +#: ../common/glossary.rst:737 +msgid "Cloudbase-Init" +msgstr "" + +#: ../common/glossary.rst:740 +msgid "" +"A Windows project providing guest initialization features, similar to cloud-" +"init." +msgstr "" + +#: ../common/glossary.rst:742 +msgid "cloudpipe" +msgstr "" + +#: ../common/glossary.rst:745 +msgid "A compute service that creates VPNs on a per-project basis." +msgstr "" + +#: ../common/glossary.rst:747 +msgid "cloudpipe image" +msgstr "" + +#: ../common/glossary.rst:750 +msgid "" +"A pre-made VM image that serves as a cloudpipe server. Essentially, OpenVPN " +"running on Linux." +msgstr "" + +#: ../common/glossary.rst:752 +msgid "CMDB" +msgstr "" + +#: ../common/glossary.rst:755 +msgid "Configuration Management Database." +msgstr "" + +#: ../common/glossary.rst:756 +msgid "congress" +msgstr "" + +#: ../common/glossary.rst:759 +msgid "OpenStack project that provides the Governance service." +msgstr "" + +#: ../common/glossary.rst:760 +msgid "command filter" +msgstr "" + +#: ../common/glossary.rst:763 +msgid "Lists allowed commands within the Compute rootwrap facility." +msgstr "" + +#: ../common/glossary.rst:765 +msgid "community project" +msgstr "" + +#: ../common/glossary.rst:768 +msgid "" +"A project that is not officially endorsed by the OpenStack Foundation. If " +"the project is successful enough, it might be elevated to an incubated " +"project and then to a core project, or it might be merged with the main code " +"trunk." +msgstr "" + +#: ../common/glossary.rst:772 +msgid "compression" +msgstr "" + +#: ../common/glossary.rst:775 +msgid "" +"Reducing the size of files by special encoding, the file can be decompressed " +"again to its original content. OpenStack supports compression at the Linux " +"file system level but does not support compression for things such as Object " +"Storage objects or Image service VM images." +msgstr "" + +#: ../common/glossary.rst:783 +msgid "" +"The OpenStack core project that provides compute services. The project name " +"of Compute service is nova." +msgstr "" + +#: ../common/glossary.rst:785 +msgid "Compute API" +msgstr "" + +#: ../common/glossary.rst:788 +msgid "" +"The nova-api daemon provides access to nova services. Can communicate with " +"other APIs, such as the Amazon EC2 API." +msgstr "" + +#: ../common/glossary.rst:791 +msgid "compute controller" +msgstr "" + +#: ../common/glossary.rst:794 +msgid "" +"The Compute component that chooses suitable hosts on which to start VM " +"instances." +msgstr "" + +#: ../common/glossary.rst:796 +msgid "compute host" +msgstr "" + +#: ../common/glossary.rst:799 +msgid "Physical host dedicated to running compute nodes." +msgstr "" + +#: ../common/glossary.rst:800 +msgid "compute node" +msgstr "" + +#: ../common/glossary.rst:803 +msgid "" +"A node that runs the nova-compute daemon that manages VM instances that " +"provide a wide range of services, such as web applications and analytics." +msgstr "" + +#: ../common/glossary.rst:806 +msgid "Compute service" +msgstr "" + +#: ../common/glossary.rst:809 +msgid "Name for the Compute component that manages VMs." +msgstr "" + +#: ../common/glossary.rst:810 +msgid "compute worker" +msgstr "" + +#: ../common/glossary.rst:813 +msgid "" +"The Compute component that runs on each compute node and manages the VM " +"instance life cycle, including run, reboot, terminate, attach/detach " +"volumes, and so on. Provided by the nova-compute daemon." +msgstr "" + +#: ../common/glossary.rst:816 +msgid "concatenated object" +msgstr "" + +#: ../common/glossary.rst:819 +msgid "" +"A set of segment objects that Object Storage combines and sends to the " +"client." +msgstr "" + +#: ../common/glossary.rst:821 +msgid "conductor" +msgstr "" + +#: ../common/glossary.rst:824 +msgid "" +"In Compute, conductor is the process that proxies database requests from the " +"compute process. Using conductor improves security because compute nodes do " +"not need direct access to the database." +msgstr "" + +#: ../common/glossary.rst:828 +msgid "consistency window" +msgstr "" + #: ../common/glossary.rst:831 msgid "" "The amount of time it takes for a new Object Storage object to become " "accessible to all clients." msgstr "" -#: ../common/glossary.rst:2238 ../common/glossary.rst:2245 -#: ../common/glossary.rst:2244 ../common/glossary.rst:2233 +#: ../common/glossary.rst:833 +msgid "console log" +msgstr "" + +#: ../common/glossary.rst:836 +msgid "Contains the output from a Linux VM console in Compute." +msgstr "" + +#: ../common/glossary.rst:837 +msgid "container" +msgstr "" + +#: ../common/glossary.rst:840 msgid "" -"The association between an Image service VM image and a tenant. Enables " -"images to be shared with specified tenants." +"Organizes and stores objects in Object Storage. Similar to the concept of a " +"Linux directory but cannot be nested. Alternative term for an Image service " +"container format." +msgstr "" + +#: ../common/glossary.rst:843 +msgid "container auditor" +msgstr "" + +#: ../common/glossary.rst:846 +msgid "" +"Checks for missing replicas or incorrect objects in specified Object Storage " +"containers through queries to the SQLite back-end database." +msgstr "" + +#: ../common/glossary.rst:849 +msgid "container database" +msgstr "" + +#: ../common/glossary.rst:852 +msgid "" +"A SQLite database that stores Object Storage containers and container " +"metadata. The container server accesses this database." +msgstr "" + +#: ../common/glossary.rst:855 +msgid "container format" +msgstr "" + +#: ../common/glossary.rst:858 +msgid "" +"A wrapper used by the Image service that contains a VM image and its " +"associated metadata, such as machine state, OS disk size, and so on." +msgstr "" + +#: ../common/glossary.rst:861 +msgid "container server" +msgstr "" + +#: ../common/glossary.rst:864 +msgid "An Object Storage server that manages containers." +msgstr "" + +#: ../common/glossary.rst:868 +msgid "" +"OpenStack project that provides a set of services for management of " +"application containers in a multi-tenant cloud environment. The code name of " +"the project name is magnum." +msgstr "" + +#: ../common/glossary.rst:871 +msgid "container service" +msgstr "" + +#: ../common/glossary.rst:874 +msgid "" +"The Object Storage component that provides container services, such as " +"create, delete, list, and so on." +msgstr "" + +#: ../common/glossary.rst:876 +msgid "content delivery network (CDN)" +msgstr "" + +#: ../common/glossary.rst:879 +msgid "" +"A content delivery network is a specialized network that is used to " +"distribute content to clients, typically located close to the client for " +"increased performance." +msgstr "" + +#: ../common/glossary.rst:882 +msgid "controller node" +msgstr "" + +#: ../common/glossary.rst:885 +msgid "Alternative term for a cloud controller node." +msgstr "" + +#: ../common/glossary.rst:886 +msgid "core API" +msgstr "" + +#: ../common/glossary.rst:889 +msgid "" +"Depending on context, the core API is either the OpenStack API or the main " +"API of a specific core project, such as Compute, Networking, Image service, " +"and so on." +msgstr "" + +#: ../common/glossary.rst:892 +msgid "core project" +msgstr "" + +#: ../common/glossary.rst:895 +msgid "" +"An official OpenStack project. Currently consists of Compute (nova), Object " +"Storage (swift), Image service (glance), Identity (keystone), Dashboard " +"(horizon), Networking (neutron), and Block Storage (cinder), the Telemetry " +"module (ceilometer), Orchestration module (heat), Database service (trove), " +"Bare Metal service (ironic), Data processing service (sahara). However, this " +"definition is changing based on community discussions about the \"Big Tent\"." +msgstr "" + +#: ../common/glossary.rst:903 +msgid "cost" +msgstr "" + +#: ../common/glossary.rst:906 +msgid "" +"Under the Compute distributed scheduler, this is calculated by looking at " +"the capabilities of each host relative to the flavor of the VM instance " +"being requested." +msgstr "" + +#: ../common/glossary.rst:909 +msgid "credentials" +msgstr "" + +#: ../common/glossary.rst:912 +msgid "" +"Data that is only known to or accessible by a user and used to verify that " +"the user is who he says he is. Credentials are presented to the server " +"during authentication. Examples include a password, secret key, digital " +"certificate, and fingerprint." +msgstr "" + +#: ../common/glossary.rst:917 +msgid "Cross-Origin Resource Sharing (CORS)" +msgstr "" + +#: ../common/glossary.rst:920 +msgid "" +"A mechanism that allows many resources (for example, fonts, JavaScript) on a " +"web page to be requested from another domain outside the domain from which " +"the resource originated. In particular, JavaScript's AJAX calls can use the " +"XMLHttpRequest mechanism." +msgstr "" + +#: ../common/glossary.rst:925 +msgid "Crowbar" +msgstr "" + +#: ../common/glossary.rst:928 +msgid "" +"An open source community project by Dell that aims to provide all necessary " +"services to quickly deploy clouds." +msgstr "" + +#: ../common/glossary.rst:930 +msgid "current workload" +msgstr "" + +#: ../common/glossary.rst:933 +msgid "" +"An element of the Compute capacity cache that is calculated based on the " +"number of build, snapshot, migrate, and resize operations currently in " +"progress on a given host." +msgstr "" + +#: ../common/glossary.rst:936 +msgid "customer" +msgstr "" + +#: ../common/glossary.rst:939 +msgid "Alternative term for tenant." +msgstr "" + +#: ../common/glossary.rst:940 +msgid "customization module" +msgstr "" + +#: ../common/glossary.rst:943 +msgid "" +"A user-created Python module that is loaded by horizon to change the look " +"and feel of the dashboard." +msgstr "" + +#: ../common/glossary.rst:945 +msgid "daemon" +msgstr "" + +#: ../common/glossary.rst:948 +msgid "" +"A process that runs in the background and waits for requests. May or may not " +"listen on a TCP or UDP port. Do not confuse with a worker." +msgstr "" + +#: ../common/glossary.rst:951 +msgid "DAC" +msgstr "" + +#: ../common/glossary.rst:954 +msgid "" +"Discretionary access control. Governs the ability of subjects to access " +"objects, while enabling users to make policy decisions and assign security " +"attributes. The traditional UNIX system of users, groups, and read-write-" +"execute permissions is an example of DAC." +msgstr "" + +#: ../common/glossary.rst:959 +msgid "dashboard" +msgstr "" + +#: ../common/glossary.rst:962 +msgid "" +"The web-based management interface for OpenStack. An alternative name for " +"horizon." +msgstr "" + +#: ../common/glossary.rst:964 +msgid "data encryption" +msgstr "" + +#: ../common/glossary.rst:967 +msgid "" +"Both Image service and Compute support encrypted virtual machine (VM) images " +"(but not instances). In-transit data encryption is supported in OpenStack " +"using technologies such as HTTPS, SSL, TLS, and SSH. Object Storage does not " +"support object encryption at the application level but may support storage " +"that uses disk encryption." +msgstr "" + +#: ../common/glossary.rst:972 +msgid "database ID" +msgstr "" + +#: ../common/glossary.rst:975 +msgid "A unique ID given to each replica of an Object Storage database." +msgstr "" + +#: ../common/glossary.rst:977 +msgid "database replicator" +msgstr "" + +#: ../common/glossary.rst:980 +msgid "" +"An Object Storage component that copies changes in the account, container, " +"and object databases to other nodes." +msgstr "" + +#: ../common/glossary.rst:985 +msgid "" +"An integrated project that provide scalable and reliable Cloud Database-as-a-" +"Service functionality for both relational and non-relational database " +"engines. The project name of Database service is trove." +msgstr "" + +#: ../common/glossary.rst:992 +msgid "" +"OpenStack project that provides a scalable data-processing stack and " +"associated management interfaces. The code name for the project is sahara." +msgstr "" + +#: ../common/glossary.rst:995 +msgid "deallocate" +msgstr "" + +#: ../common/glossary.rst:998 +msgid "" +"The process of removing the association between a floating IP address and a " +"fixed IP address. Once this association is removed, the floating IP returns " +"to the address pool." +msgstr "" + +#: ../common/glossary.rst:1001 +msgid "Debian" +msgstr "" + +#: ../common/glossary.rst:1005 +msgid "deduplication" +msgstr "" + +#: ../common/glossary.rst:1008 +msgid "" +"The process of finding duplicate data at the disk block, file, and/or object " +"level to minimize storage use—currently unsupported within OpenStack." +msgstr "" + +#: ../common/glossary.rst:1011 +msgid "default panel" +msgstr "" + +#: ../common/glossary.rst:1014 +msgid "" +"The default panel that is displayed when a user accesses the horizon " +"dashboard." +msgstr "" + +#: ../common/glossary.rst:1016 +msgid "default tenant" +msgstr "" + +#: ../common/glossary.rst:1019 +msgid "" +"New users are assigned to this tenant if no tenant is specified when a user " +"is created." +msgstr "" + +#: ../common/glossary.rst:1021 +msgid "default token" +msgstr "" + +#: ../common/glossary.rst:1024 +msgid "" +"An Identity service token that is not associated with a specific tenant and " +"is exchanged for a scoped token." +msgstr "" + +#: ../common/glossary.rst:1026 +msgid "delayed delete" +msgstr "" + +#: ../common/glossary.rst:1029 +msgid "" +"An option within Image service so that an image is deleted after a " +"predefined number of seconds instead of immediately." +msgstr "" + +#: ../common/glossary.rst:1031 +msgid "delivery mode" +msgstr "" + +#: ../common/glossary.rst:1034 +msgid "" +"Setting for the Compute RabbitMQ message delivery mode; can be set to either " +"transient or persistent." +msgstr "" + +#: ../common/glossary.rst:1036 +msgid "denial of service (DoS)" +msgstr "" + +#: ../common/glossary.rst:1039 +msgid "" +"Denial of service (DoS) is a short form for denial-of-service attack. This " +"is a malicious attempt to prevent legitimate users from using a service." +msgstr "" + +#: ../common/glossary.rst:1042 +msgid "deprecated auth" +msgstr "" + +#: ../common/glossary.rst:1045 +msgid "" +"An option within Compute that enables administrators to create and manage " +"users through the `nova-manage` command as opposed to using the Identity " +"service." +msgstr "" + +#: ../common/glossary.rst:1048 +msgid "Designate" +msgstr "" + +#: ../common/glossary.rst:1051 +msgid "Code name for the DNS service project for OpenStack." +msgstr "" + +#: ../common/glossary.rst:1052 +msgid "Desktop-as-a-Service" +msgstr "" + +#: ../common/glossary.rst:1055 +msgid "" +"A platform that provides a suite of desktop environments that users access " +"to receive a desktop experience from any location. This may provide general " +"use, development, or even homogeneous testing environments." +msgstr "" + +#: ../common/glossary.rst:1059 +msgid "developer" +msgstr "" + +#: ../common/glossary.rst:1062 +msgid "" +"One of the default roles in the Compute RBAC system and the default role " +"assigned to a new user." +msgstr "" + +#: ../common/glossary.rst:1064 +msgid "device ID" +msgstr "" + +#: ../common/glossary.rst:1067 +msgid "Maps Object Storage partitions to physical storage devices." +msgstr "" + +#: ../common/glossary.rst:1069 +msgid "device weight" +msgstr "" + +#: ../common/glossary.rst:1072 +msgid "" +"Distributes partitions proportionately across Object Storage devices based " +"on the storage capacity of each device." +msgstr "" + +#: ../common/glossary.rst:1074 +msgid "DevStack" +msgstr "" + +#: ../common/glossary.rst:1077 +msgid "" +"Community project that uses shell scripts to quickly build complete " +"OpenStack development environments." +msgstr "" + +#: ../common/glossary.rst:1079 +msgid "DHCP" +msgstr "" + +#: ../common/glossary.rst:1082 +msgid "" +"Dynamic Host Configuration Protocol. A network protocol that configures " +"devices that are connected to a network so that they can communicate on that " +"network by using the Internet Protocol (IP). The protocol is implemented in " +"a client-server model where DHCP clients request configuration data, such as " +"an IP address, a default route, and one or more DNS server addresses from a " +"DHCP server." +msgstr "" + +#: ../common/glossary.rst:1088 +msgid "DHCP agent" +msgstr "" + +#: ../common/glossary.rst:1091 +msgid "" +"OpenStack Networking agent that provides DHCP services for virtual networks." +msgstr "" + +#: ../common/glossary.rst:1093 +msgid "Diablo" +msgstr "" + +#: ../common/glossary.rst:1096 +msgid "" +"A grouped release of projects related to OpenStack that came out in the fall " +"of 2011, the fourth release of OpenStack. It included Compute (nova 2011.3), " +"Object Storage (swift 1.4.3), and the Image service (glance). Diablo is the " +"code name for the fourth release of OpenStack. The design summit took place " +"in in the Bay Area near Santa Clara, California, US and Diablo is a nearby " +"city." +msgstr "" + +#: ../common/glossary.rst:1104 +msgid "direct consumer" +msgstr "" + +#: ../common/glossary.rst:1107 +msgid "" +"An element of the Compute RabbitMQ that comes to life when a RPC call is " +"executed. It connects to a direct exchange through a unique exclusive queue, " +"sends the message, and terminates." +msgstr "" + +#: ../common/glossary.rst:1110 +msgid "direct exchange" +msgstr "" + +#: ../common/glossary.rst:1113 +msgid "" +"A routing table that is created within the Compute RabbitMQ during RPC " +"calls; one is created for each RPC call that is invoked." +msgstr "" + +#: ../common/glossary.rst:1116 +msgid "direct publisher" +msgstr "" + +#: ../common/glossary.rst:1119 +msgid "Element of RabbitMQ that provides a response to an incoming MQ message." +msgstr "" + +#: ../common/glossary.rst:1121 +msgid "disassociate" +msgstr "" + +#: ../common/glossary.rst:1124 +msgid "" +"The process of removing the association between a floating IP address and " +"fixed IP and thus returning the floating IP address to the address pool." +msgstr "" + +#: ../common/glossary.rst:1127 +msgid "disk encryption" +msgstr "" + +#: ../common/glossary.rst:1130 +msgid "" +"The ability to encrypt data at the file system, disk partition, or whole-" +"disk level. Supported within Compute VMs." +msgstr "" + +#: ../common/glossary.rst:1132 +msgid "disk format" +msgstr "" + +#: ../common/glossary.rst:1135 +msgid "" +"The underlying format that a disk image for a VM is stored as within the " +"Image service back-end store. For example, AMI, ISO, QCOW2, VMDK, and so on." +msgstr "" + +#: ../common/glossary.rst:1138 +msgid "dispersion" +msgstr "" + +#: ../common/glossary.rst:1141 +msgid "" +"In Object Storage, tools to test and ensure dispersion of objects and " +"containers to ensure fault tolerance." +msgstr "" + +#: ../common/glossary.rst:1143 +msgid "distributed virtual router (DVR)" +msgstr "" + +#: ../common/glossary.rst:1146 +msgid "" +"Mechanism for highly-available multi-host routing when using OpenStack " +"Networking (neutron)." +msgstr "" + +#: ../common/glossary.rst:1148 +msgid "Django" +msgstr "" + +#: ../common/glossary.rst:1151 +msgid "A web framework used extensively in horizon." +msgstr "" + +#: ../common/glossary.rst:1152 +msgid "DNS" +msgstr "" + +#: ../common/glossary.rst:1155 +msgid "" +"Domain Name Server. A hierarchical and distributed naming system for " +"computers, services, and resources connected to the Internet or a private " +"network. Associates a human-friendly names to IP addresses." +msgstr "" + +#: ../common/glossary.rst:1159 +msgid "DNS record" +msgstr "" + +#: ../common/glossary.rst:1162 +msgid "" +"A record that specifies information about a particular domain and belongs to " +"the domain." +msgstr "" + +#: ../common/glossary.rst:1164 +msgid "DNS service" +msgstr "" + +#: ../common/glossary.rst:1167 +msgid "" +"OpenStack project that provides scalable, on demand, self service access to " +"authoritative DNS services, in a technology-agnostic manner. The code name " +"for the project is designate." +msgstr "" + +#: ../common/glossary.rst:1171 +msgid "dnsmasq" +msgstr "" + +#: ../common/glossary.rst:1174 +msgid "" +"Daemon that provides DNS, DHCP, BOOTP, and TFTP services for virtual " +"networks." +msgstr "" + +#: ../common/glossary.rst:1176 +msgid "domain" +msgstr "" + +#: ../common/glossary.rst:1179 +msgid "" +"An Identity API v3 entity. Represents a collection of projects, groups and " +"users that defines administrative boundaries for managing OpenStack Identity " +"entities. On the Internet, separates a website from other sites. Often, the " +"domain name has two or more parts that are separated by dots. For example, " +"yahoo.com, usa.gov, harvard.edu, or mail.yahoo.com. Also, a domain is an " +"entity or container of all DNS-related information containing one or more " +"records." +msgstr "" + +#: ../common/glossary.rst:1179 +msgid "" +"In the Identity service, provides isolation between projects and users. On " +"the Internet, separates a website from other sites. Often, the domain name " +"has two or more parts that are separated by dots. For example, yahoo.com, " +"usa.gov, harvard.edu, or mail.yahoo.com. Also, a domain is an entity or " +"container of all DNS-related information containing one or more records." +msgstr "" + +#: ../common/glossary.rst:1187 ../common/glossary.rst:1188 +msgid "Domain Name Service (DNS)" +msgstr "" + +#: ../common/glossary.rst:1190 ../common/glossary.rst:1191 +msgid "" +"In Compute, the support that enables associating DNS entries with floating " +"IP addresses, nodes, or cells so that hostnames are consistent across " +"reboots." +msgstr "" + +#: ../common/glossary.rst:1193 ../common/glossary.rst:1194 +msgid "Domain Name System (DNS)" +msgstr "" + +#: ../common/glossary.rst:1196 ../common/glossary.rst:1197 +msgid "" +"A system by which Internet domain name-to-address and address-to-name " +"resolutions are determined. DNS helps navigate the Internet by translating " +"the IP address into an address that is easier to remember. For example, " +"translating 111.111.111.1 into www.yahoo.com. All domains and their " +"components, such as mail servers, utilize DNS to resolve to the appropriate " +"locations. DNS servers are usually set up in a master-slave relationship " +"such that failure of the master invokes the slave. DNS servers might also be " +"clustered or replicated such that changes made to one DNS server are " +"automatically propagated to other active servers." +msgstr "" + +#: ../common/glossary.rst:1207 ../common/glossary.rst:1208 +msgid "download" +msgstr "" + +#: ../common/glossary.rst:1210 ../common/glossary.rst:1211 +msgid "" +"The transfer of data, usually in the form of files, from one computer to " +"another." +msgstr "" + +#: ../common/glossary.rst:1212 ../common/glossary.rst:1213 +msgid "DRTM" +msgstr "" + +#: ../common/glossary.rst:1215 ../common/glossary.rst:1216 +msgid "Dynamic root of trust measurement." +msgstr "" + +#: ../common/glossary.rst:1216 ../common/glossary.rst:1217 +msgid "durable exchange" +msgstr "" + +#: ../common/glossary.rst:1219 ../common/glossary.rst:1220 +msgid "" +"The Compute RabbitMQ message exchange that remains active when the server " +"restarts." +msgstr "" + +#: ../common/glossary.rst:1221 ../common/glossary.rst:1222 +msgid "durable queue" +msgstr "" + +#: ../common/glossary.rst:1224 ../common/glossary.rst:1225 +msgid "" +"A Compute RabbitMQ message queue that remains active when the server " +"restarts." +msgstr "" + +#: ../common/glossary.rst:1226 ../common/glossary.rst:1227 +msgid "Dynamic Host Configuration Protocol (DHCP)" +msgstr "" + +#: ../common/glossary.rst:1229 ../common/glossary.rst:1230 +msgid "" +"A method to automatically configure networking for a host at boot time. " +"Provided by both Networking and Compute." +msgstr "" + +#: ../common/glossary.rst:1231 ../common/glossary.rst:1232 +msgid "Dynamic HyperText Markup Language (DHTML)" +msgstr "" + +#: ../common/glossary.rst:1234 ../common/glossary.rst:1235 +msgid "" +"Pages that use HTML, JavaScript, and Cascading Style Sheets to enable users " +"to interact with a web page or show simple animation." +msgstr "" + +#: ../common/glossary.rst:1237 ../common/glossary.rst:1238 +msgid "east-west traffic" +msgstr "" + +#: ../common/glossary.rst:1240 ../common/glossary.rst:1241 +msgid "" +"Network traffic between servers in the same cloud or data center. See also " +"north-south traffic." +msgstr "" + +#: ../common/glossary.rst:1242 ../common/glossary.rst:1243 +msgid "EBS boot volume" +msgstr "" + +#: ../common/glossary.rst:1245 ../common/glossary.rst:1246 +msgid "" +"An Amazon EBS storage volume that contains a bootable VM image, currently " +"unsupported in OpenStack." +msgstr "" + +#: ../common/glossary.rst:1247 ../common/glossary.rst:1248 +#: ../common/glossary.rst:1343 ../common/glossary.rst:1344 +msgid "ebtables" +msgstr "" + +#: ../common/glossary.rst:1250 ../common/glossary.rst:1251 +msgid "" +"Used in Compute along with arptables, iptables, and ip6tables to create " +"firewalls and to ensure isolation of network communications." +msgstr "" + +#: ../common/glossary.rst:1253 ../common/glossary.rst:1254 +msgid "EC2" +msgstr "" + +#: ../common/glossary.rst:1256 ../common/glossary.rst:1257 +msgid "The Amazon commercial compute product, similar to Compute." +msgstr "" + +#: ../common/glossary.rst:1258 ../common/glossary.rst:1259 +msgid "EC2 access key" +msgstr "" + +#: ../common/glossary.rst:1261 ../common/glossary.rst:1262 +msgid "Used along with an EC2 secret key to access the Compute EC2 API." +msgstr "" + +#: ../common/glossary.rst:1263 ../common/glossary.rst:1264 +msgid "EC2 API" +msgstr "" + +#: ../common/glossary.rst:1266 ../common/glossary.rst:1267 +msgid "OpenStack supports accessing the Amazon EC2 API through Compute." +msgstr "" + +#: ../common/glossary.rst:1268 ../common/glossary.rst:1269 +msgid "EC2 Compatibility API" +msgstr "" + +#: ../common/glossary.rst:1271 ../common/glossary.rst:1272 +msgid "" +"A Compute component that enables OpenStack to communicate with Amazon EC2." +msgstr "" + +#: ../common/glossary.rst:1273 ../common/glossary.rst:1274 +msgid "EC2 secret key" +msgstr "" + +#: ../common/glossary.rst:1276 ../common/glossary.rst:1277 +msgid "" +"Used along with an EC2 access key when communicating with the Compute EC2 " +"API; used to digitally sign each request." +msgstr "" + +#: ../common/glossary.rst:1278 ../common/glossary.rst:1279 +msgid "Elastic Block Storage (EBS)" +msgstr "" + +#: ../common/glossary.rst:1281 ../common/glossary.rst:1282 +msgid "The Amazon commercial block storage product." +msgstr "" + +#: ../common/glossary.rst:1282 ../common/glossary.rst:1283 +msgid "encryption" +msgstr "" + +#: ../common/glossary.rst:1285 ../common/glossary.rst:1286 +msgid "" +"OpenStack supports encryption technologies such as HTTPS, SSH, SSL, TLS, " +"digital certificates, and data encryption." +msgstr "" + +#: ../common/glossary.rst:1287 ../common/glossary.rst:1288 +msgid "endpoint" +msgstr "" + +#: ../common/glossary.rst:1290 ../common/glossary.rst:1291 +msgid "See API endpoint." +msgstr "" + +#: ../common/glossary.rst:1291 ../common/glossary.rst:1292 +msgid "endpoint registry" +msgstr "" + +#: ../common/glossary.rst:1294 ../common/glossary.rst:1295 +msgid "Alternative term for an Identity service catalog." +msgstr "" + +#: ../common/glossary.rst:1295 ../common/glossary.rst:1296 +msgid "encapsulation" +msgstr "" + +#: ../common/glossary.rst:1298 ../common/glossary.rst:1299 +msgid "" +"The practice of placing one packet type within another for the purposes of " +"abstracting or securing data. Examples include GRE, MPLS, or IPsec." +msgstr "" + +#: ../common/glossary.rst:1301 ../common/glossary.rst:1302 +msgid "endpoint template" +msgstr "" + +#: ../common/glossary.rst:1304 ../common/glossary.rst:1305 +msgid "" +"A list of URL and port number endpoints that indicate where a service, such " +"as Object Storage, Compute, Identity, and so on, can be accessed." +msgstr "" + +#: ../common/glossary.rst:1307 ../common/glossary.rst:1308 +msgid "entity" +msgstr "" + +#: ../common/glossary.rst:1310 ../common/glossary.rst:1311 +msgid "" +"Any piece of hardware or software that wants to connect to the network " +"services provided by Networking, the network connectivity service. An entity " +"can make use of Networking by implementing a VIF." +msgstr "" + +#: ../common/glossary.rst:1314 ../common/glossary.rst:1315 +msgid "ephemeral image" +msgstr "" + +#: ../common/glossary.rst:1317 ../common/glossary.rst:1318 +msgid "" +"A VM image that does not save changes made to its volumes and reverts them " +"to their original state after the instance is terminated." +msgstr "" + +#: ../common/glossary.rst:1320 ../common/glossary.rst:1321 +msgid "ephemeral volume" +msgstr "" + +#: ../common/glossary.rst:1323 ../common/glossary.rst:1324 +msgid "" +"Volume that does not save the changes made to it and reverts to its original " +"state when the current user relinquishes control." +msgstr "" + +#: ../common/glossary.rst:1325 ../common/glossary.rst:1326 +msgid "Essex" +msgstr "" + +#: ../common/glossary.rst:1328 ../common/glossary.rst:1329 +msgid "" +"A grouped release of projects related to OpenStack that came out in April " +"2012, the fifth release of OpenStack. It included Compute (nova 2012.1), " +"Object Storage (swift 1.4.8), Image (glance), Identity (keystone), and " +"Dashboard (horizon). Essex is the code name for the fifth release of " +"OpenStack. The design summit took place in Boston, Massachusetts, US and " +"Essex is a nearby city." +msgstr "" + +#: ../common/glossary.rst:1335 ../common/glossary.rst:1336 +msgid "ESX" +msgstr "" + +#: ../common/glossary.rst:1338 ../common/glossary.rst:1339 +#: ../common/glossary.rst:1342 ../common/glossary.rst:1343 +#: ../common/glossary.rst:2149 ../common/glossary.rst:2155 +#: ../common/glossary.rst:3556 ../common/glossary.rst:3563 +#: ../common/glossary.rst:3567 ../common/glossary.rst:3570 +#: ../common/glossary.rst:3578 ../common/glossary.rst:3653 +#: ../common/glossary.rst:3660 ../common/glossary.rst:3664 +#: ../common/glossary.rst:3667 ../common/glossary.rst:3675 +#: ../common/glossary.rst:3742 ../common/glossary.rst:3749 +#: ../common/glossary.rst:3753 ../common/glossary.rst:3756 +#: ../common/glossary.rst:3764 ../common/glossary.rst:3788 +#: ../common/glossary.rst:3795 ../common/glossary.rst:3797 +#: ../common/glossary.rst:3799 ../common/glossary.rst:3802 +#: ../common/glossary.rst:3804 ../common/glossary.rst:3808 +#: ../common/glossary.rst:3810 ../common/glossary.rst:3811 +#: ../common/glossary.rst:3819 +msgid "An OpenStack-supported hypervisor." +msgstr "" + +#: ../common/glossary.rst:1339 ../common/glossary.rst:1340 +msgid "ESXi" +msgstr "" + +#: ../common/glossary.rst:1346 ../common/glossary.rst:1347 +msgid "" +"Filtering tool for a Linux bridging firewall, enabling filtering of network " +"traffic passing through a Linux bridge. Used to restrict communications " +"between hosts and/or nodes in OpenStack Compute along with iptables, " +"arptables, and ip6tables." +msgstr "" + +#: ../common/glossary.rst:1350 ../common/glossary.rst:1351 +msgid "ETag" +msgstr "" + +#: ../common/glossary.rst:1353 ../common/glossary.rst:1354 +msgid "" +"MD5 hash of an object within Object Storage, used to ensure data integrity." +msgstr "" + +#: ../common/glossary.rst:1355 ../common/glossary.rst:1356 +msgid "euca2ools" +msgstr "" + +#: ../common/glossary.rst:1358 ../common/glossary.rst:1359 +msgid "" +"A collection of command-line tools for administering VMs; most are " +"compatible with OpenStack." +msgstr "" + +#: ../common/glossary.rst:1360 ../common/glossary.rst:1361 +msgid "Eucalyptus Kernel Image (EKI)" +msgstr "" + +#: ../common/glossary.rst:1363 ../common/glossary.rst:1364 +msgid "Used along with an ERI to create an EMI." +msgstr "" + +#: ../common/glossary.rst:1364 ../common/glossary.rst:1365 +msgid "Eucalyptus Machine Image (EMI)" +msgstr "" + +#: ../common/glossary.rst:1367 ../common/glossary.rst:1368 +msgid "VM image container format supported by Image service." +msgstr "" + +#: ../common/glossary.rst:1368 ../common/glossary.rst:1369 +msgid "Eucalyptus Ramdisk Image (ERI)" +msgstr "" + +#: ../common/glossary.rst:1371 ../common/glossary.rst:1372 +msgid "Used along with an EKI to create an EMI." +msgstr "" + +#: ../common/glossary.rst:1372 ../common/glossary.rst:1373 +msgid "evacuate" +msgstr "" + +#: ../common/glossary.rst:1375 ../common/glossary.rst:1376 +msgid "" +"The process of migrating one or all virtual machine (VM) instances from one " +"host to another, compatible with both shared storage live migration and " +"block migration." +msgstr "" + +#: ../common/glossary.rst:1378 ../common/glossary.rst:1379 +msgid "exchange" +msgstr "" + +#: ../common/glossary.rst:1381 ../common/glossary.rst:1382 +msgid "Alternative term for a RabbitMQ message exchange." +msgstr "" + +#: ../common/glossary.rst:1382 ../common/glossary.rst:1383 +msgid "exchange type" +msgstr "" + +#: ../common/glossary.rst:1385 ../common/glossary.rst:1386 +msgid "A routing algorithm in the Compute RabbitMQ." +msgstr "" + +#: ../common/glossary.rst:1386 ../common/glossary.rst:1387 +msgid "exclusive queue" +msgstr "" + +#: ../common/glossary.rst:1389 ../common/glossary.rst:1390 +msgid "" +"Connected to by a direct consumer in RabbitMQ—Compute, the message can be " +"consumed only by the current connection." +msgstr "" + +#: ../common/glossary.rst:1391 ../common/glossary.rst:1392 +msgid "extended attributes (xattr)" +msgstr "" + +#: ../common/glossary.rst:1394 ../common/glossary.rst:1395 +msgid "" +"File system option that enables storage of additional information beyond " +"owner, group, permissions, modification time, and so on. The underlying " +"Object Storage file system must support extended attributes." +msgstr "" + +#: ../common/glossary.rst:1398 ../common/glossary.rst:1399 +msgid "extension" +msgstr "" + +#: ../common/glossary.rst:1401 ../common/glossary.rst:1402 +msgid "" +"Alternative term for an API extension or plug-in. In the context of Identity " +"service, this is a call that is specific to the implementation, such as " +"adding support for OpenID." +msgstr "" + +#: ../common/glossary.rst:1404 ../common/glossary.rst:1405 +msgid "external network" +msgstr "" + +#: ../common/glossary.rst:1407 ../common/glossary.rst:1408 +msgid "A network segment typically used for instance Internet access." +msgstr "" + +#: ../common/glossary.rst:1409 ../common/glossary.rst:1410 +msgid "extra specs" +msgstr "" + +#: ../common/glossary.rst:1412 ../common/glossary.rst:1413 +msgid "" +"Specifies additional requirements when Compute determines where to start a " +"new instance. Examples include a minimum amount of network bandwidth or a " +"GPU." +msgstr "" + +#: ../common/glossary.rst:1415 ../common/glossary.rst:1416 +msgid "FakeLDAP" +msgstr "" + +#: ../common/glossary.rst:1418 ../common/glossary.rst:1419 +msgid "" +"An easy method to create a local LDAP directory for testing Identity and " +"Compute. Requires Redis." +msgstr "" + +#: ../common/glossary.rst:1420 ../common/glossary.rst:1421 +msgid "fan-out exchange" +msgstr "" + +#: ../common/glossary.rst:1423 ../common/glossary.rst:1424 +msgid "" +"Within RabbitMQ and Compute, it is the messaging interface that is used by " +"the scheduler service to receive capability messages from the compute, " +"volume, and network nodes." +msgstr "" + +#: ../common/glossary.rst:1426 ../common/glossary.rst:1427 +msgid "federated identity" +msgstr "" + +#: ../common/glossary.rst:1429 ../common/glossary.rst:1430 +msgid "" +"A method to establish trusts between identity providers and the OpenStack " +"cloud." +msgstr "" + +#: ../common/glossary.rst:1431 ../common/glossary.rst:1432 +msgid "Fedora" +msgstr "" + +#: ../common/glossary.rst:1434 ../common/glossary.rst:1435 +msgid "A Linux distribution compatible with OpenStack." +msgstr "" + +#: ../common/glossary.rst:1435 ../common/glossary.rst:1436 +msgid "Fibre Channel" +msgstr "" + +#: ../common/glossary.rst:1438 ../common/glossary.rst:1439 +msgid "" +"Storage protocol similar in concept to TCP/IP; encapsulates SCSI commands " +"and data." +msgstr "" + +#: ../common/glossary.rst:1440 ../common/glossary.rst:1441 +msgid "Fibre Channel over Ethernet (FCoE)" +msgstr "" + +#: ../common/glossary.rst:1443 ../common/glossary.rst:1444 +msgid "The fibre channel protocol tunneled within Ethernet." +msgstr "" + +#: ../common/glossary.rst:1444 ../common/glossary.rst:1445 +msgid "fill-first scheduler" +msgstr "" + +#: ../common/glossary.rst:1447 ../common/glossary.rst:1448 +msgid "" +"The Compute scheduling method that attempts to fill a host with VMs rather " +"than starting new VMs on a variety of hosts." +msgstr "" + +#: ../common/glossary.rst:1449 ../common/glossary.rst:1450 +msgid "filter" +msgstr "" + +#: ../common/glossary.rst:1452 ../common/glossary.rst:1453 +msgid "" +"The step in the Compute scheduling process when hosts that cannot run VMs " +"are eliminated and not chosen." +msgstr "" + +#: ../common/glossary.rst:1454 ../common/glossary.rst:1455 +msgid "firewall" +msgstr "" + +#: ../common/glossary.rst:1457 ../common/glossary.rst:1458 +msgid "" +"Used to restrict communications between hosts and/or nodes, implemented in " +"Compute using iptables, arptables, ip6tables, and etables." +msgstr "" + +#: ../common/glossary.rst:1458 +msgid "" +"Used to restrict communications between hosts and/or nodes, implemented in " +"Compute using iptables, arptables, ip6tables, and ebtables." +msgstr "" + +#: ../common/glossary.rst:1460 ../common/glossary.rst:1461 +msgid "Firewall-as-a-Service (FWaaS)" +msgstr "" + +#: ../common/glossary.rst:1461 +msgid "FWaaS" +msgstr "" + +#: ../common/glossary.rst:1463 ../common/glossary.rst:1464 +msgid "A Networking extension that provides perimeter firewall functionality." +msgstr "" + +#: ../common/glossary.rst:1465 ../common/glossary.rst:1466 +msgid "fixed IP address" +msgstr "" + +#: ../common/glossary.rst:1468 ../common/glossary.rst:1469 +msgid "" +"An IP address that is associated with the same instance each time that " +"instance boots, is generally not accessible to end users or the public " +"Internet, and is used for management of the instance." +msgstr "" + +#: ../common/glossary.rst:1472 ../common/glossary.rst:1473 +msgid "Flat Manager" +msgstr "" + +#: ../common/glossary.rst:1475 ../common/glossary.rst:1476 +msgid "" +"The Compute component that gives IP addresses to authorized nodes and " +"assumes DHCP, DNS, and routing configuration and services are provided by " +"something else." +msgstr "" + +#: ../common/glossary.rst:1478 ../common/glossary.rst:1479 +msgid "flat mode injection" +msgstr "" + +#: ../common/glossary.rst:1481 ../common/glossary.rst:1482 +msgid "" +"A Compute networking method where the OS network configuration information " +"is injected into the VM image before the instance starts." +msgstr "" + +#: ../common/glossary.rst:1484 ../common/glossary.rst:1485 +msgid "flat network" +msgstr "" + +#: ../common/glossary.rst:1487 ../common/glossary.rst:1488 +msgid "" +"Virtual network type that uses neither VLANs nor tunnels to segregate tenant " +"traffic. Each flat network typically requires a separate underlying physical " +"interface defined by bridge mappings. However, a flat network can contain " +"multiple subnets." +msgstr "" + +#: ../common/glossary.rst:1492 ../common/glossary.rst:1493 +msgid "FlatDHCP Manager" +msgstr "" + +#: ../common/glossary.rst:1495 ../common/glossary.rst:1496 +msgid "" +"The Compute component that provides dnsmasq (DHCP, DNS, BOOTP, TFTP) and " +"radvd (routing) services." +msgstr "" + +#: ../common/glossary.rst:1497 ../common/glossary.rst:1498 +msgid "flavor" +msgstr "" + +#: ../common/glossary.rst:1500 ../common/glossary.rst:1501 +msgid "Alternative term for a VM instance type." +msgstr "" + +#: ../common/glossary.rst:1501 ../common/glossary.rst:1502 +msgid "flavor ID" +msgstr "" + +#: ../common/glossary.rst:1504 ../common/glossary.rst:1505 +msgid "UUID for each Compute or Image service VM flavor or instance type." +msgstr "" + +#: ../common/glossary.rst:1506 ../common/glossary.rst:1507 +msgid "floating IP address" +msgstr "" + +#: ../common/glossary.rst:1509 ../common/glossary.rst:1510 +msgid "" +"An IP address that a project can associate with a VM so that the instance " +"has the same public IP address each time that it boots. You create a pool of " +"floating IP addresses and assign them to instances as they are launched to " +"maintain a consistent IP address for maintaining DNS assignment." +msgstr "" + +#: ../common/glossary.rst:1514 ../common/glossary.rst:1515 +msgid "Folsom" +msgstr "" + +#: ../common/glossary.rst:1517 ../common/glossary.rst:1518 +msgid "" +"A grouped release of projects related to OpenStack that came out in the fall " +"of 2012, the sixth release of OpenStack. It includes Compute (nova), Object " +"Storage (swift), Identity (keystone), Networking (neutron), Image service " +"(glance), and Volumes or Block Storage (cinder). Folsom is the code name for " +"the sixth release of OpenStack. The design summit took place in San " +"Francisco, California, US and Folsom is a nearby city." +msgstr "" + +#: ../common/glossary.rst:1525 ../common/glossary.rst:1526 +msgid "FormPost" +msgstr "" + +#: ../common/glossary.rst:1528 ../common/glossary.rst:1529 +msgid "" +"Object Storage middleware that uploads (posts) an image through a form on a " +"web page." +msgstr "" + +#: ../common/glossary.rst:1530 ../common/glossary.rst:1531 +msgid "front end" +msgstr "" + +#: ../common/glossary.rst:1533 ../common/glossary.rst:1534 +msgid "" +"The point where a user interacts with a service; can be an API endpoint, the " +"horizon dashboard, or a command-line tool." +msgstr "" + +#: ../common/glossary.rst:1535 ../common/glossary.rst:1536 +msgid "gateway" +msgstr "" + +#: ../common/glossary.rst:1538 ../common/glossary.rst:1539 +msgid "" +"An IP address, typically assigned to a router, that passes network traffic " +"between different networks." +msgstr "" + +#: ../common/glossary.rst:1540 ../common/glossary.rst:1541 +msgid "generic receive offload (GRO)" +msgstr "" + +#: ../common/glossary.rst:1543 ../common/glossary.rst:1544 +msgid "" +"Feature of certain network interface drivers that combines many smaller " +"received packets into a large packet before delivery to the kernel IP stack." +msgstr "" + +#: ../common/glossary.rst:1546 ../common/glossary.rst:1547 +msgid "generic routing encapsulation (GRE)" +msgstr "" + +#: ../common/glossary.rst:1549 ../common/glossary.rst:1550 +msgid "" +"Protocol that encapsulates a wide variety of network layer protocols inside " +"virtual point-to-point links." +msgstr "" + +#: ../common/glossary.rst:1554 ../common/glossary.rst:1555 +msgid "A core project that provides the OpenStack Image service." +msgstr "" + +#: ../common/glossary.rst:1555 ../common/glossary.rst:1556 +msgid "glance API server" +msgstr "" + +#: ../common/glossary.rst:1558 ../common/glossary.rst:1559 +msgid "" +"Processes client requests for VMs, updates Image service metadata on the " +"registry server, and communicates with the store adapter to upload VM images " +"from the back-end store." +msgstr "" + +#: ../common/glossary.rst:1561 ../common/glossary.rst:1562 +msgid "glance registry" +msgstr "" + +#: ../common/glossary.rst:1564 ../common/glossary.rst:1565 +msgid "Alternative term for the Image service image registry." +msgstr "" + +#: ../common/glossary.rst:1565 ../common/glossary.rst:1566 +msgid "global endpoint template" +msgstr "" + +#: ../common/glossary.rst:1568 ../common/glossary.rst:1569 +msgid "" +"The Identity service endpoint template that contains services available to " +"all tenants." +msgstr "" + +#: ../common/glossary.rst:1570 ../common/glossary.rst:1571 +msgid "GlusterFS" +msgstr "" + +#: ../common/glossary.rst:1573 ../common/glossary.rst:1574 +msgid "" +"A file system designed to aggregate NAS hosts, compatible with OpenStack." +msgstr "" + +#: ../common/glossary.rst:1575 ../common/glossary.rst:1576 +msgid "golden image" +msgstr "" + +#: ../common/glossary.rst:1578 ../common/glossary.rst:1579 +msgid "" +"A method of operating system installation where a finalized disk image is " +"created and then used by all nodes without modification." +msgstr "" + +#: ../common/glossary.rst:1581 ../common/glossary.rst:1582 +msgid "Governance service" +msgstr "" + +#: ../common/glossary.rst:1584 ../common/glossary.rst:1585 +msgid "" +"OpenStack project to provide governance as a service across any collection " +"of cloud services in order to monitor, enforce, and audit policy over " +"dynamic infrastructure. The code name for the project is congress." +msgstr "" + +#: ../common/glossary.rst:1588 ../common/glossary.rst:1589 +msgid "Graphic Interchange Format (GIF)" +msgstr "" + +#: ../common/glossary.rst:1591 ../common/glossary.rst:1592 +msgid "" +"A type of image file that is commonly used for animated images on web pages." +msgstr "" + +#: ../common/glossary.rst:1593 ../common/glossary.rst:1594 +msgid "Graphics Processing Unit (GPU)" +msgstr "" + +#: ../common/glossary.rst:1596 ../common/glossary.rst:1597 +msgid "" +"Choosing a host based on the existence of a GPU is currently unsupported in " +"OpenStack." +msgstr "" + +#: ../common/glossary.rst:1598 ../common/glossary.rst:1599 +msgid "Green Threads" +msgstr "" + +#: ../common/glossary.rst:1601 ../common/glossary.rst:1602 +msgid "" +"The cooperative threading model used by Python; reduces race conditions and " +"only context switches when specific library calls are made. Each OpenStack " +"service is its own thread." +msgstr "" + +#: ../common/glossary.rst:1604 ../common/glossary.rst:1605 +msgid "Grizzly" +msgstr "" + +#: ../common/glossary.rst:1607 ../common/glossary.rst:1608 +msgid "" +"The code name for the seventh release of OpenStack. The design summit took " +"place in San Diego, California, US and Grizzly is an element of the state " +"flag of California." +msgstr "" + +#: ../common/glossary.rst:1611 ../common/glossary.rst:1617 +msgid "guest OS" +msgstr "" + +#: ../common/glossary.rst:1612 +msgid "Group" +msgstr "" + +#: ../common/glossary.rst:1614 ../common/glossary.rst:1620 +msgid "An operating system instance running under the control of a hypervisor." +msgstr "" + +#: ../common/glossary.rst:1615 +msgid "" +"An Identity v3 API entity. Represents a collection of users that is owned by " +"a specific domain." +msgstr "" + +#: ../common/glossary.rst:1616 ../common/glossary.rst:1622 +msgid "Hadoop" +msgstr "" + +#: ../common/glossary.rst:1619 ../common/glossary.rst:1625 +msgid "" +"Apache Hadoop is an open source software framework that supports data-" +"intensive distributed applications." +msgstr "" + +#: ../common/glossary.rst:1621 ../common/glossary.rst:1627 +msgid "handover" +msgstr "" + +#: ../common/glossary.rst:1624 ../common/glossary.rst:1630 +msgid "" +"An object state in Object Storage where a new replica of the object is " +"automatically created due to a drive failure." +msgstr "" + +#: ../common/glossary.rst:1626 ../common/glossary.rst:1632 +msgid "hard reboot" +msgstr "" + +#: ../common/glossary.rst:1629 ../common/glossary.rst:1635 +msgid "" +"A type of reboot where a physical or virtual power button is pressed as " +"opposed to a graceful, proper shutdown of the operating system." +msgstr "" + +#: ../common/glossary.rst:1632 ../common/glossary.rst:1638 +msgid "Havana" +msgstr "" + +#: ../common/glossary.rst:1635 ../common/glossary.rst:1641 +msgid "" +"The code name for the eighth release of OpenStack. The design summit took " +"place in Portland, Oregon, US and Havana is an unincorporated community in " +"Oregon." +msgstr "" + +#: ../common/glossary.rst:1641 ../common/glossary.rst:1647 +msgid "" +"An integrated project that aims to orchestrate multiple cloud applications " +"for OpenStack." +msgstr "" + +#: ../common/glossary.rst:1643 ../common/glossary.rst:1649 +msgid "Heat Orchestration Template (HOT)" +msgstr "" + +#: ../common/glossary.rst:1646 ../common/glossary.rst:1652 +msgid "Heat input in the format native to OpenStack." +msgstr "" + +#: ../common/glossary.rst:1647 ../common/glossary.rst:1653 +msgid "health monitor" +msgstr "" + +#: ../common/glossary.rst:1650 ../common/glossary.rst:1656 +msgid "" +"Determines whether back-end members of a VIP pool can process a request. A " +"pool can have several health monitors associated with it. When a pool has " +"several monitors associated with it, all monitors check each member of the " +"pool. All monitors must declare a member to be healthy for it to stay active." +msgstr "" + +#: ../common/glossary.rst:1656 ../common/glossary.rst:1662 +msgid "high availability (HA)" +msgstr "" + +#: ../common/glossary.rst:1659 ../common/glossary.rst:1665 +msgid "" +"A high availability system design approach and associated service " +"implementation ensures that a prearranged level of operational performance " +"will be met during a contractual measurement period. High availability " +"systems seeks to minimize system downtime and data loss." +msgstr "" + +#: ../common/glossary.rst:1664 ../common/glossary.rst:1670 +msgid "horizon" +msgstr "" + +#: ../common/glossary.rst:1667 ../common/glossary.rst:1673 +msgid "OpenStack project that provides a dashboard, which is a web interface." +msgstr "" + +#: ../common/glossary.rst:1669 ../common/glossary.rst:1675 +msgid "horizon plug-in" +msgstr "" + +#: ../common/glossary.rst:1672 ../common/glossary.rst:1678 +msgid "A plug-in for the OpenStack dashboard (horizon)." +msgstr "" + +#: ../common/glossary.rst:1673 ../common/glossary.rst:1679 +msgid "host" +msgstr "" + +#: ../common/glossary.rst:1676 ../common/glossary.rst:1682 +msgid "A physical computer, not a VM instance (node)." +msgstr "" + +#: ../common/glossary.rst:1677 ../common/glossary.rst:1683 +msgid "host aggregate" +msgstr "" + +#: ../common/glossary.rst:1680 ../common/glossary.rst:1686 +msgid "" +"A method to further subdivide availability zones into hypervisor pools, a " +"collection of common hosts." +msgstr "" + +#: ../common/glossary.rst:1682 ../common/glossary.rst:1688 +msgid "Host Bus Adapter (HBA)" +msgstr "" + +#: ../common/glossary.rst:1685 ../common/glossary.rst:1691 +msgid "" +"Device plugged into a PCI slot, such as a fibre channel or network card." +msgstr "" + +#: ../common/glossary.rst:1687 ../common/glossary.rst:1693 +msgid "HTTP" +msgstr "" + +#: ../common/glossary.rst:1690 ../common/glossary.rst:1696 +msgid "" +"Hypertext Transfer Protocol. HTTP is an application protocol for " +"distributed, collaborative, hypermedia information systems. It is the " +"foundation of data communication for the World Wide Web. Hypertext is " +"structured text that uses logical links (hyperlinks) between nodes " +"containing text. HTTP is the protocol to exchange or transfer hypertext." +msgstr "" + +#: ../common/glossary.rst:1696 ../common/glossary.rst:1702 +msgid "HTTPS" +msgstr "" + +#: ../common/glossary.rst:1699 ../common/glossary.rst:1705 +msgid "" +"Hypertext Transfer Protocol Secure (HTTPS) is a communications protocol for " +"secure communication over a computer network, with especially wide " +"deployment on the Internet. Technically, it is not a protocol in and of " +"itself; rather, it is the result of simply layering the Hypertext Transfer " +"Protocol (HTTP) on top of the SSL/TLS protocol, thus adding the security " +"capabilities of SSL/TLS to standard HTTP communications." +msgstr "" + +#: ../common/glossary.rst:1706 ../common/glossary.rst:1712 +msgid "hybrid cloud" +msgstr "" + +#: ../common/glossary.rst:1709 ../common/glossary.rst:1715 +msgid "" +"A hybrid cloud is a composition of two or more clouds (private, community or " +"public) that remain distinct entities but are bound together, offering the " +"benefits of multiple deployment models. Hybrid cloud can also mean the " +"ability to connect colocation, managed and/or dedicated services with cloud " +"resources." +msgstr "" + +#: ../common/glossary.rst:1715 ../common/glossary.rst:1721 +msgid "Hyper-V" +msgstr "" + +#: ../common/glossary.rst:1718 ../common/glossary.rst:1724 +msgid "One of the hypervisors supported by OpenStack." +msgstr "" + +#: ../common/glossary.rst:1719 ../common/glossary.rst:1725 +msgid "hyperlink" +msgstr "" + +#: ../common/glossary.rst:1722 ../common/glossary.rst:1728 +msgid "" +"Any kind of text that contains a link to some other site, commonly found in " +"documents where clicking on a word or words opens up a different website." +msgstr "" + +#: ../common/glossary.rst:1725 ../common/glossary.rst:1731 +msgid "Hypertext Transfer Protocol (HTTP)" +msgstr "" + +#: ../common/glossary.rst:1728 ../common/glossary.rst:1734 +msgid "The protocol that tells browsers where to go to find information." +msgstr "" + +#: ../common/glossary.rst:1730 ../common/glossary.rst:1736 +msgid "Hypertext Transfer Protocol Secure (HTTPS)" +msgstr "" + +#: ../common/glossary.rst:1733 ../common/glossary.rst:1739 +msgid "" +"Encrypted HTTP communications using SSL or TLS; most OpenStack API endpoints " +"and many inter-component communications support HTTPS communication." +msgstr "" + +#: ../common/glossary.rst:1736 ../common/glossary.rst:1742 +msgid "hypervisor" +msgstr "" + +#: ../common/glossary.rst:1739 ../common/glossary.rst:1745 +msgid "" +"Software that arbitrates and controls VM access to the actual underlying " +"hardware." +msgstr "" + +#: ../common/glossary.rst:1741 ../common/glossary.rst:1747 +msgid "hypervisor pool" +msgstr "" + +#: ../common/glossary.rst:1744 ../common/glossary.rst:1750 +msgid "A collection of hypervisors grouped together through host aggregates." +msgstr "" + +#: ../common/glossary.rst:1746 ../common/glossary.rst:1752 +msgid "IaaS" +msgstr "" + +#: ../common/glossary.rst:1749 ../common/glossary.rst:1755 +msgid "" +"Infrastructure-as-a-Service. IaaS is a provisioning model in which an " +"organization outsources physical components of a data center, such as " +"storage, hardware, servers, and networking components. A service provider " +"owns the equipment and is responsible for housing, operating and maintaining " +"it. The client typically pays on a per-use basis. IaaS is a model for " +"providing cloud services." +msgstr "" + +#: ../common/glossary.rst:1755 ../common/glossary.rst:1761 +msgid "Icehouse" +msgstr "" + +#: ../common/glossary.rst:1758 ../common/glossary.rst:1764 +msgid "" +"The code name for the ninth release of OpenStack. The design summit took " +"place in Hong Kong and Ice House is a street in that city." +msgstr "" + +#: ../common/glossary.rst:1761 ../common/glossary.rst:1767 +msgid "ICMP" +msgstr "" + +#: ../common/glossary.rst:1764 ../common/glossary.rst:1770 +msgid "" +"Internet Control Message Protocol, used by network devices for control " +"messages. For example, :command:`ping` uses ICMP to test connectivity." +msgstr "" + +#: ../common/glossary.rst:1768 ../common/glossary.rst:1774 +msgid "ID number" +msgstr "" + +#: ../common/glossary.rst:1771 ../common/glossary.rst:1777 +msgid "" +"Unique numeric ID associated with each user in Identity, conceptually " +"similar to a Linux or LDAP UID." +msgstr "" + +#: ../common/glossary.rst:1773 ../common/glossary.rst:1779 +msgid "Identity API" +msgstr "" + +#: ../common/glossary.rst:1776 ../common/glossary.rst:1782 +msgid "Alternative term for the Identity service API." +msgstr "" + +#: ../common/glossary.rst:1777 ../common/glossary.rst:1783 +msgid "Identity back end" +msgstr "" + +#: ../common/glossary.rst:1780 ../common/glossary.rst:1786 +msgid "" +"The source used by Identity service to retrieve user information; an " +"OpenLDAP server, for example." +msgstr "" + +#: ../common/glossary.rst:1782 ../common/glossary.rst:1788 +msgid "identity provider" +msgstr "" + +#: ../common/glossary.rst:1785 ../common/glossary.rst:1791 +msgid "" +"A directory service, which allows users to login with a user name and " +"password. It is a typical source of authentication tokens." +msgstr "" + +#: ../common/glossary.rst:1791 ../common/glossary.rst:1797 +msgid "" +"The OpenStack core project that provides a central directory of users mapped " +"to the OpenStack services they can access. It also registers endpoints for " +"OpenStack services. It acts as a common authentication system. The project " +"name of Identity is keystone." +msgstr "" + +#: ../common/glossary.rst:1796 ../common/glossary.rst:1802 +msgid "Identity service API" +msgstr "" + +#: ../common/glossary.rst:1799 ../common/glossary.rst:1805 +msgid "" +"The API used to access the OpenStack Identity service provided through " +"keystone." +msgstr "" + +#: ../common/glossary.rst:1801 ../common/glossary.rst:1807 +msgid "IDS" +msgstr "" + +#: ../common/glossary.rst:1804 ../common/glossary.rst:1810 +msgid "Intrusion Detection System." +msgstr "" + +#: ../common/glossary.rst:1805 ../common/glossary.rst:1811 +msgid "image" +msgstr "" + +#: ../common/glossary.rst:1808 ../common/glossary.rst:1814 +msgid "" +"A collection of files for a specific operating system (OS) that you use to " +"create or rebuild a server. OpenStack provides pre-built images. You can " +"also create custom images, or snapshots, from servers that you have " +"launched. Custom images can be used for data backups or as \"gold\" images " +"for additional servers." +msgstr "" + +#: ../common/glossary.rst:1813 ../common/glossary.rst:1819 +msgid "Image API" +msgstr "" + +#: ../common/glossary.rst:1816 ../common/glossary.rst:1822 +msgid "The Image service API endpoint for management of VM images." +msgstr "" + +#: ../common/glossary.rst:1818 ../common/glossary.rst:1824 +msgid "image cache" +msgstr "" + +#: ../common/glossary.rst:1821 ../common/glossary.rst:1827 +msgid "" +"Used by Image service to obtain images on the local host rather than re-" +"downloading them from the image server each time one is requested." +msgstr "" + +#: ../common/glossary.rst:1824 ../common/glossary.rst:1830 +msgid "image ID" +msgstr "" + +#: ../common/glossary.rst:1827 ../common/glossary.rst:1833 +msgid "" +"Combination of a URI and UUID used to access Image service VM images through " +"the image API." +msgstr "" + +#: ../common/glossary.rst:1829 ../common/glossary.rst:1835 +msgid "image membership" +msgstr "" + +#: ../common/glossary.rst:1832 ../common/glossary.rst:1838 +#: ../common/glossary.rst:2238 ../common/glossary.rst:2243 +#: ../common/glossary.rst:2249 ../common/glossary.rst:2250 +msgid "" +"A list of tenants that can access a given VM image within Image service." +msgstr "" + +#: ../common/glossary.rst:1834 ../common/glossary.rst:1840 +msgid "image owner" +msgstr "" + +#: ../common/glossary.rst:1837 ../common/glossary.rst:1843 +msgid "The tenant who owns an Image service virtual machine image." +msgstr "" + +#: ../common/glossary.rst:1839 ../common/glossary.rst:1845 +msgid "image registry" +msgstr "" + +#: ../common/glossary.rst:1842 ../common/glossary.rst:1848 +msgid "A list of VM images that are available through Image service." +msgstr "" + +#: ../common/glossary.rst:1847 ../common/glossary.rst:1853 +msgid "" +"An OpenStack core project that provides discovery, registration, and " +"delivery services for disk and server images. The project name of the Image " +"service is glance." +msgstr "" + +#: ../common/glossary.rst:1850 ../common/glossary.rst:1856 +msgid "Image service API" +msgstr "" + +#: ../common/glossary.rst:1853 ../common/glossary.rst:1859 +msgid "Alternative name for the glance image API." +msgstr "" + +#: ../common/glossary.rst:1854 ../common/glossary.rst:1860 +msgid "image status" +msgstr "" + +#: ../common/glossary.rst:1857 ../common/glossary.rst:1863 +msgid "" +"The current status of a VM image in Image service, not to be confused with " +"the status of a running instance." +msgstr "" + +#: ../common/glossary.rst:1859 ../common/glossary.rst:1865 +msgid "image store" msgstr "" #: ../common/glossary.rst:1862 ../common/glossary.rst:1868 @@ -8655,26 +7889,411 @@ msgid "" "Object Storage, local file system, S3, or HTTP." msgstr "" -#: ../common/get_started_block_storage.rst:31 -#: ../common/get_started_block_storage.rst:30 -msgid "" -"The cinder-backup service provides backing up volumes of any type to a " -"backup storage provider. Like the cinder-volume service, it can interact " -"with a variety of storage providers through a driver architecture." +#: ../common/glossary.rst:1864 ../common/glossary.rst:1870 +msgid "image UUID" msgstr "" -#: ../common/cli_manage_images.rst:5 -msgid "" -"The cloud operator assigns roles to users. Roles determine who can upload " -"and manage images. The operator might restrict image upload and management " -"to only cloud administrators or operators." +#: ../common/glossary.rst:1867 ../common/glossary.rst:1873 +msgid "UUID used by Image service to uniquely identify each VM image." msgstr "" -#: ../common/glossary.rst:1635 ../common/glossary.rst:1641 +#: ../common/glossary.rst:1869 ../common/glossary.rst:1875 +msgid "incubated project" +msgstr "" + +#: ../common/glossary.rst:1872 ../common/glossary.rst:1878 msgid "" -"The code name for the eighth release of OpenStack. The design summit took " -"place in Portland, Oregon, US and Havana is an unincorporated community in " -"Oregon." +"A community project may be elevated to this status and is then promoted to a " +"core project." +msgstr "" + +#: ../common/glossary.rst:1874 ../common/glossary.rst:1880 +msgid "ingress filtering" +msgstr "" + +#: ../common/glossary.rst:1877 ../common/glossary.rst:1883 +msgid "" +"The process of filtering incoming network traffic. Supported by Compute." +msgstr "" + +#: ../common/glossary.rst:1879 ../common/glossary.rst:1885 +msgid "INI" +msgstr "" + +#: ../common/glossary.rst:1882 ../common/glossary.rst:1888 +msgid "" +"The OpenStack configuration files use an INI format to describe options and " +"their values. It consists of sections and key value pairs." +msgstr "" + +#: ../common/glossary.rst:1885 ../common/glossary.rst:1891 +msgid "injection" +msgstr "" + +#: ../common/glossary.rst:1888 ../common/glossary.rst:1894 +msgid "" +"The process of putting a file into a virtual machine image before the " +"instance is started." +msgstr "" + +#: ../common/glossary.rst:1890 ../common/glossary.rst:1896 +msgid "instance" +msgstr "" + +#: ../common/glossary.rst:1893 ../common/glossary.rst:1899 +msgid "" +"A running VM, or a VM in a known state such as suspended, that can be used " +"like a hardware server." +msgstr "" + +#: ../common/glossary.rst:1895 ../common/glossary.rst:1901 +msgid "instance ID" +msgstr "" + +#: ../common/glossary.rst:1898 ../common/glossary.rst:1904 +msgid "Alternative term for instance UUID." +msgstr "" + +#: ../common/glossary.rst:1899 ../common/glossary.rst:1905 +msgid "instance state" +msgstr "" + +#: ../common/glossary.rst:1902 ../common/glossary.rst:1908 +msgid "The current state of a guest VM image." +msgstr "" + +#: ../common/glossary.rst:1903 ../common/glossary.rst:1909 +msgid "instance tunnels network" +msgstr "" + +#: ../common/glossary.rst:1906 ../common/glossary.rst:1912 +msgid "" +"A network segment used for instance traffic tunnels between compute nodes " +"and the network node." +msgstr "" + +#: ../common/glossary.rst:1908 ../common/glossary.rst:1914 +msgid "instance type" +msgstr "" + +#: ../common/glossary.rst:1911 ../common/glossary.rst:1917 +msgid "" +"Describes the parameters of the various virtual machine images that are " +"available to users; includes parameters such as CPU, storage, and memory. " +"Alternative term for flavor." +msgstr "" + +#: ../common/glossary.rst:1914 ../common/glossary.rst:1920 +msgid "instance type ID" +msgstr "" + +#: ../common/glossary.rst:1917 ../common/glossary.rst:1923 +msgid "Alternative term for a flavor ID." +msgstr "" + +#: ../common/glossary.rst:1918 ../common/glossary.rst:1924 +msgid "instance UUID" +msgstr "" + +#: ../common/glossary.rst:1921 ../common/glossary.rst:1927 +#: ../common/glossary.rst:3166 ../common/glossary.rst:3173 +#: ../common/glossary.rst:3177 ../common/glossary.rst:3180 +#: ../common/glossary.rst:3188 +msgid "Unique ID assigned to each guest VM instance." +msgstr "" + +#: ../common/glossary.rst:1922 ../common/glossary.rst:1928 +msgid "interface" +msgstr "" + +#: ../common/glossary.rst:1925 ../common/glossary.rst:1931 +msgid "" +"A physical or virtual device that provides connectivity to another device or " +"medium." +msgstr "" + +#: ../common/glossary.rst:1927 ../common/glossary.rst:1933 +msgid "interface ID" +msgstr "" + +#: ../common/glossary.rst:1930 ../common/glossary.rst:1936 +msgid "Unique ID for a Networking VIF or vNIC in the form of a UUID." +msgstr "" + +#: ../common/glossary.rst:1932 ../common/glossary.rst:1938 +msgid "Internet protocol (IP)" +msgstr "" + +#: ../common/glossary.rst:1935 ../common/glossary.rst:1941 +msgid "" +"Principal communications protocol in the internet protocol suite for " +"relaying datagrams across network boundaries." +msgstr "" + +#: ../common/glossary.rst:1937 ../common/glossary.rst:1943 +msgid "Internet Service Provider (ISP)" +msgstr "" + +#: ../common/glossary.rst:1940 ../common/glossary.rst:1946 +msgid "" +"Any business that provides Internet access to individuals or businesses." +msgstr "" + +#: ../common/glossary.rst:1942 ../common/glossary.rst:1948 +msgid "Internet Small Computer System Interface (iSCSI)" +msgstr "" + +#: ../common/glossary.rst:1945 ../common/glossary.rst:1951 +msgid "" +"Storage protocol that encapsulates SCSI frames for transport over IP " +"networks." +msgstr "" + +#: ../common/glossary.rst:1947 ../common/glossary.rst:1953 +msgid "ironic" +msgstr "" + +#: ../common/glossary.rst:1950 ../common/glossary.rst:1956 +msgid "" +"OpenStack project that provisions bare metal, as opposed to virtual, " +"machines." +msgstr "" + +#: ../common/glossary.rst:1952 ../common/glossary.rst:1958 +msgid "IOPS" +msgstr "" + +#: ../common/glossary.rst:1955 ../common/glossary.rst:1961 +msgid "" +"IOPS (Input/Output Operations Per Second) are a common performance " +"measurement used to benchmark computer storage devices like hard disk " +"drives, solid state drives, and storage area networks." +msgstr "" + +#: ../common/glossary.rst:1959 ../common/glossary.rst:1965 +msgid "IP address" +msgstr "" + +#: ../common/glossary.rst:1962 ../common/glossary.rst:1968 +msgid "" +"Number that is unique to every computer system on the Internet. Two versions " +"of the Internet Protocol (IP) are in use for addresses: IPv4 and IPv6." +msgstr "" + +#: ../common/glossary.rst:1965 ../common/glossary.rst:1971 +msgid "IP Address Management (IPAM)" +msgstr "" + +#: ../common/glossary.rst:1968 ../common/glossary.rst:1974 +msgid "" +"The process of automating IP address allocation, deallocation, and " +"management. Currently provided by Compute, melange, and Networking." +msgstr "" + +#: ../common/glossary.rst:1971 ../common/glossary.rst:1977 +msgid "IPL" +msgstr "" + +#: ../common/glossary.rst:1974 ../common/glossary.rst:1980 +msgid "Initial Program Loader." +msgstr "" + +#: ../common/glossary.rst:1975 ../common/glossary.rst:1981 +msgid "IPMI" +msgstr "" + +#: ../common/glossary.rst:1978 ../common/glossary.rst:1984 +msgid "" +"Intelligent Platform Management Interface. IPMI is a standardized computer " +"system interface used by system administrators for out-of-band management of " +"computer systems and monitoring of their operation. In layman's terms, it is " +"a way to manage a computer using a direct network connection, whether it is " +"turned on or not; connecting to the hardware rather than an operating system " +"or login shell." +msgstr "" + +#: ../common/glossary.rst:1985 ../common/glossary.rst:1991 +msgid "ip6tables" +msgstr "" + +#: ../common/glossary.rst:1988 ../common/glossary.rst:1994 +msgid "" +"Tool used to set up, maintain, and inspect the tables of IPv6 packet filter " +"rules in the Linux kernel. In OpenStack Compute, ip6tables is used along " +"with arptables, ebtables, and iptables to create firewalls for both nodes " +"and VMs." +msgstr "" + +#: ../common/glossary.rst:1992 ../common/glossary.rst:1998 +msgid "ipset" +msgstr "" + +#: ../common/glossary.rst:1995 ../common/glossary.rst:2001 +msgid "" +"Extension to iptables that allows creation of firewall rules that match " +"entire \"sets\" of IP addresses simultaneously. These sets reside in indexed " +"data structures to increase efficiency, particularly on systems with a large " +"quantity of rules." +msgstr "" + +#: ../common/glossary.rst:1999 ../common/glossary.rst:2005 +msgid "iptables" +msgstr "" + +#: ../common/glossary.rst:2002 ../common/glossary.rst:2008 +msgid "" +"Used along with arptables and ebtables, iptables create firewalls in " +"Compute. iptables are the tables provided by the Linux kernel firewall " +"(implemented as different Netfilter modules) and the chains and rules it " +"stores. Different kernel modules and programs are currently used for " +"different protocols: iptables applies to IPv4, ip6tables to IPv6, arptables " +"to ARP, and ebtables to Ethernet frames. Requires root privilege to " +"manipulate." +msgstr "" + +#: ../common/glossary.rst:2009 ../common/glossary.rst:2015 +msgid "iSCSI" +msgstr "" + +#: ../common/glossary.rst:2012 ../common/glossary.rst:2018 +msgid "" +"The SCSI disk protocol tunneled within Ethernet, supported by Compute, " +"Object Storage, and Image service." +msgstr "" + +#: ../common/glossary.rst:2014 ../common/glossary.rst:2020 +msgid "ISO9960" +msgstr "" + +#: ../common/glossary.rst:2017 ../common/glossary.rst:2023 +#: ../common/glossary.rst:2835 ../common/glossary.rst:2840 +#: ../common/glossary.rst:2842 ../common/glossary.rst:2849 +#: ../common/glossary.rst:2851 ../common/glossary.rst:3578 +#: ../common/glossary.rst:3585 ../common/glossary.rst:3589 +#: ../common/glossary.rst:3590 ../common/glossary.rst:3592 +#: ../common/glossary.rst:3597 ../common/glossary.rst:3600 +#: ../common/glossary.rst:3601 ../common/glossary.rst:3604 +#: ../common/glossary.rst:3612 ../common/glossary.rst:3671 +#: ../common/glossary.rst:3678 ../common/glossary.rst:3682 +#: ../common/glossary.rst:3685 ../common/glossary.rst:3693 +msgid "One of the VM image disk formats supported by Image service." +msgstr "" + +#: ../common/glossary.rst:2019 ../common/glossary.rst:2025 +msgid "itsec" +msgstr "" + +#: ../common/glossary.rst:2022 ../common/glossary.rst:2028 +msgid "" +"A default role in the Compute RBAC system that can quarantine an instance in " +"any project." +msgstr "" + +#: ../common/glossary.rst:2024 ../common/glossary.rst:2030 +msgid "Java" +msgstr "" + +#: ../common/glossary.rst:2027 ../common/glossary.rst:2033 +msgid "" +"A programming language that is used to create systems that involve more than " +"one computer by way of a network." +msgstr "" + +#: ../common/glossary.rst:2029 ../common/glossary.rst:2035 +msgid "JavaScript" +msgstr "" + +#: ../common/glossary.rst:2032 ../common/glossary.rst:2038 +msgid "A scripting language that is used to build web pages." +msgstr "" + +#: ../common/glossary.rst:2033 ../common/glossary.rst:2039 +msgid "JavaScript Object Notation (JSON)" +msgstr "" + +#: ../common/glossary.rst:2036 ../common/glossary.rst:2042 +msgid "One of the supported response formats in OpenStack." +msgstr "" + +#: ../common/glossary.rst:2037 ../common/glossary.rst:2043 +msgid "Jenkins" +msgstr "" + +#: ../common/glossary.rst:2040 ../common/glossary.rst:2046 +msgid "Tool used to run jobs automatically for OpenStack development." +msgstr "" + +#: ../common/glossary.rst:2042 ../common/glossary.rst:2048 +msgid "jumbo frame" +msgstr "" + +#: ../common/glossary.rst:2045 ../common/glossary.rst:2051 +msgid "" +"Feature in modern Ethernet networks that supports frames up to approximately " +"9000 bytes." +msgstr "" + +#: ../common/glossary.rst:2047 ../common/glossary.rst:2053 +msgid "Juno" +msgstr "" + +#: ../common/glossary.rst:2050 ../common/glossary.rst:2056 +msgid "" +"The code name for the tenth release of OpenStack. The design summit took " +"place in Atlanta, Georgia, US and Juno is an unincorporated community in " +"Georgia." +msgstr "" + +#: ../common/glossary.rst:2053 ../common/glossary.rst:2059 +msgid "kernel-based VM (KVM)" +msgstr "" + +#: ../common/glossary.rst:2056 ../common/glossary.rst:2062 +msgid "" +"An OpenStack-supported hypervisor. KVM is a full virtualization solution for " +"Linux on x86 hardware containing virtualization extensions (Intel VT or AMD-" +"V), ARM, IBM Power, and IBM zSeries. It consists of a loadable kernel " +"module, that provides the core virtualization infrastructure and a processor " +"specific module." +msgstr "" + +#: ../common/glossary.rst:2062 ../common/glossary.rst:2068 +msgid "Key management service" +msgstr "" + +#: ../common/glossary.rst:2065 ../common/glossary.rst:2071 +msgid "" +"OpenStack project that produces a secret storage and generation system " +"capable of providing key management for services wishing to enable " +"encryption features. The code name of the project is barbican." +msgstr "" + +#: ../common/glossary.rst:2069 ../common/glossary.rst:2075 +msgid "Key-Value Store as a Service" +msgstr "" + +#: ../common/glossary.rst:2072 ../common/glossary.rst:2078 +msgid "" +"OpenStack project that provides a key-value store for applications running " +"in an OpenStack cloud. The code name for the project is magnetoDB." +msgstr "" + +#: ../common/glossary.rst:2078 ../common/glossary.rst:2084 +msgid "The project that provides OpenStack Identity services." +msgstr "" + +#: ../common/glossary.rst:2079 ../common/glossary.rst:2085 +msgid "Kickstart" +msgstr "" + +#: ../common/glossary.rst:2082 ../common/glossary.rst:2088 +msgid "" +"A tool to automate system configuration and installation on Red Hat, Fedora, " +"and CentOS-based Linux distributions." +msgstr "" + +#: ../common/glossary.rst:2084 ../common/glossary.rst:2090 +msgid "Kilo" msgstr "" #: ../common/glossary.rst:2087 ../common/glossary.rst:2093 @@ -8686,44 +8305,67 @@ msgid "" "community chose Kilo as the release name." msgstr "" -#: ../common/glossary.rst:299 -msgid "" -"The code name for the initial release of OpenStack. The first design summit " -"took place in Austin, Texas, US." +#: ../common/glossary.rst:2093 ../common/glossary.rst:2099 +msgid "large object" msgstr "" -#: ../common/glossary.rst:1758 ../common/glossary.rst:1764 -msgid "" -"The code name for the ninth release of OpenStack. The design summit took " -"place in Hong Kong and Ice House is a street in that city." +#: ../common/glossary.rst:2096 ../common/glossary.rst:2102 +msgid "An object within Object Storage that is larger than 5 GB." msgstr "" -#: ../common/glossary.rst:1607 ../common/glossary.rst:1608 -msgid "" -"The code name for the seventh release of OpenStack. The design summit took " -"place in San Diego, California, US and Grizzly is an element of the state " -"flag of California." +#: ../common/glossary.rst:2097 ../common/glossary.rst:2103 +msgid "Launchpad" msgstr "" -#: ../common/glossary.rst:2050 ../common/glossary.rst:2056 -msgid "" -"The code name for the tenth release of OpenStack. The design summit took " -"place in Atlanta, Georgia, US and Juno is an unincorporated community in " -"Georgia." +#: ../common/glossary.rst:2100 ../common/glossary.rst:2106 +msgid "The collaboration site for OpenStack." msgstr "" -#: ../common/glossary.rst:2302 ../common/glossary.rst:2308 -#: ../common/glossary.rst:2297 -msgid "" -"The code name for the thirteenth release of OpenStack. The design summit " -"will take place in Tokyo, Japan. Mitaka is a city in Tokyo." +#: ../common/glossary.rst:2101 ../common/glossary.rst:2107 +msgid "Layer-2 network" msgstr "" -#: ../common/glossary.rst:2233 +#: ../common/glossary.rst:2104 ../common/glossary.rst:2110 msgid "" -"The code name for the thirteenth release of OpenStack. The design summit " -"will take place in Tokyo, Japan. The code name comes from the locations " -"Meiji shrine and Meiji park in Tokyo. They are named after the emperor Meiji." +"Term used in the OSI network architecture for the data link layer. The data " +"link layer is responsible for media access control, flow control and " +"detecting and possibly correcting errors that may occur in the physical " +"layer." +msgstr "" + +#: ../common/glossary.rst:2108 ../common/glossary.rst:2114 +msgid "Layer-3 network" +msgstr "" + +#: ../common/glossary.rst:2111 ../common/glossary.rst:2117 +msgid "" +"Term used in the OSI network architecture for the network layer. The network " +"layer is responsible for packet forwarding including routing from one node " +"to another." +msgstr "" + +#: ../common/glossary.rst:2114 ../common/glossary.rst:2120 +msgid "Layer-2 (L2) agent" +msgstr "" + +#: ../common/glossary.rst:2117 ../common/glossary.rst:2123 +msgid "" +"OpenStack Networking agent that provides layer-2 connectivity for virtual " +"networks." +msgstr "" + +#: ../common/glossary.rst:2119 ../common/glossary.rst:2125 +msgid "Layer-3 (L3) agent" +msgstr "" + +#: ../common/glossary.rst:2122 ../common/glossary.rst:2128 +msgid "" +"OpenStack Networking agent that provides layer-3 (routing) services for " +"virtual networks." +msgstr "" + +#: ../common/glossary.rst:2124 ../common/glossary.rst:2130 +msgid "Liberty" msgstr "" #: ../common/glossary.rst:2127 ../common/glossary.rst:2133 @@ -8740,444 +8382,63 @@ msgid "" "Canadian province of Saskatchewan." msgstr "" -#: ../common/glossary.rst:2100 ../common/glossary.rst:2106 -msgid "The collaboration site for OpenStack." +#: ../common/glossary.rst:2131 ../common/glossary.rst:2137 +msgid "libvirt" msgstr "" -#: ../common/get_started_openstack_networking.rst:25 -#: ../common/get_started_openstack_networking.rst:24 +#: ../common/glossary.rst:2134 ../common/glossary.rst:2140 msgid "" -"The common agents are L3 (layer 3), DHCP (dynamic host IP addressing), and a " -"plug-in agent." +"Virtualization API library used by OpenStack to interact with many of its " +"supported hypervisors." msgstr "" -#: ../common/cli_manage_images.rst:142 +#: ../common/glossary.rst:2136 ../common/glossary.rst:2142 +msgid "Linux bridge" +msgstr "" + +#: ../common/glossary.rst:2139 ../common/glossary.rst:2145 msgid "" -"The container format of the image. Acceptable formats are ami, ari, aki, " -"bare, and ovf." +"Software that enables multiple VMs to share a single physical NIC within " +"Compute." msgstr "" -#: ../common/glossary.rst:1601 ../common/glossary.rst:1602 +#: ../common/glossary.rst:2141 ../common/glossary.rst:2147 +msgid "Linux Bridge neutron plug-in" +msgstr "" + +#: ../common/glossary.rst:2144 ../common/glossary.rst:2150 msgid "" -"The cooperative threading model used by Python; reduces race conditions and " -"only context switches when specific library calls are made. Each OpenStack " -"service is its own thread." +"Enables a Linux bridge to understand a Networking port, interface " +"attachment, and other abstractions." msgstr "" -#: ../common/glossary.rst:1902 ../common/glossary.rst:1908 -msgid "The current state of a guest VM image." +#: ../common/glossary.rst:2146 ../common/glossary.rst:2152 +msgid "Linux containers (LXC)" msgstr "" -#: ../common/glossary.rst:1857 ../common/glossary.rst:1863 +#: ../common/glossary.rst:2150 ../common/glossary.rst:2156 +msgid "live migration" +msgstr "" + +#: ../common/glossary.rst:2153 ../common/glossary.rst:2159 msgid "" -"The current status of a VM image in Image service, not to be confused with " -"the status of a running instance." +"The ability within Compute to move running virtual machine instances from " +"one host to another with only a small service interruption during switchover." msgstr "" -#: ../common/glossary.rst:185 +#: ../common/glossary.rst:2156 ../common/glossary.rst:2162 +msgid "load balancer" +msgstr "" + +#: ../common/glossary.rst:2159 ../common/glossary.rst:2165 msgid "" -"The daemon, worker, or service that a client communicates with to access an " -"API. API endpoints can provide any number of services, such as " -"authentication, sales data, performance meters, Compute VM commands, census " -"data, and so on." +"A load balancer is a logical device that belongs to a cloud account. It is " +"used to distribute workloads between multiple back-end systems or services, " +"based on the criteria defined as part of its configuration." msgstr "" -#: ../common/log_in_dashboard.rst:4 -msgid "" -"The dashboard is available on the node with the ``nova-dashboard`` server " -"role." -msgstr "" - -#: ../common/get_started_dashboard.rst:12 -#: ../common/get_started_dashboard.rst:13 -msgid "" -"The dashboard is usually deployed through `mod_wsgi `__ in Apache. You can modify the dashboard code to make it " -"suitable for different sites." -msgstr "" - -#: ../common/glossary.rst:2863 ../common/glossary.rst:2870 -#: ../common/glossary.rst:2877 ../common/glossary.rst:2879 -#: ../common/glossary.rst:2868 -msgid "The default message queue software used by OpenStack." -msgstr "" - -#: ../common/glossary.rst:1014 -msgid "" -"The default panel that is displayed when a user accesses the horizon " -"dashboard." -msgstr "" - -#: ../common/cli_manage_volumes.rst:221 -msgid "The delete command does not return any output." -msgstr "" - -#: ../common/cli_manage_images.rst:138 -msgid "" -"The disk format of the image. Acceptable formats are ami, ari, aki, vhd, " -"vmdk, raw, qcow2, vdi, and iso." -msgstr "" - -#: ../common/glossary.rst:1443 ../common/glossary.rst:1444 -msgid "The fibre channel protocol tunneled within Ethernet." -msgstr "" - -#: ../common/cli_install_openstack_command_line_clients.rst:168 -#: ../common/cli_install_openstack_command_line_clients.rst:174 -#: ../common/cli_install_openstack_command_line_clients.rst:176 -#: ../common/cli_install_openstack_command_line_clients.rst:178 -#: ../common/cli_install_openstack_command_line_clients.rst:180 -msgid "" -"The following CLIs are deprecated in favor of ``openstack``, the Common " -"OpenStack client supporting multiple services:" -msgstr "" - -#: ../common/app_support.rst:154 ../common/app_support.rst:151 -#: ../common/app_support.rst:149 -msgid "The following Launchpad Bugs areas are available:" -msgstr "" - -#: ../common/app_support.rst:228 ../common/app_support.rst:225 -#: ../common/app_support.rst:223 ../common/app_support.rst:229 -#: ../common/app_support.rst:231 ../common/app_support.rst:234 -#: ../common/app_support.rst:236 -msgid "" -"The following Linux distributions provide community-supported packages for " -"OpenStack:" -msgstr "" - -#: ../common/app_support.rst:40 ../common/app_support.rst:38 -msgid "" -"The following books explain how to configure and run an OpenStack cloud:" -msgstr "" - -#: ../common/app_support.rst:26 ../common/app_support.rst:24 -msgid "" -"The following books explain how to install an OpenStack cloud and its " -"associated components:" -msgstr "" - -#: ../common/app_support.rst:63 ../common/app_support.rst:61 -msgid "" -"The following books explain how to use the OpenStack dashboard and command-" -"line clients:" -msgstr "" - -#: ../common/get_started_identity.rst:85 ../common/get_started_identity.rst:84 -#: ../common/get_started_identity.rst:43 -msgid "The following diagram shows the OpenStack Identity process flow:" -msgstr "" - -#: ../common/get_started_logical_architecture.rst:39 -#: ../common/get_started_logical_architecture.rst:36 -msgid "" -"The following diagram shows the most common, but not the only possible, " -"architecture for an OpenStack cloud:" -msgstr "" - -#: ../common/get_started_conceptual_architecture.rst:6 -#: ../common/get_started_conceptual_architecture.rst:7 -msgid "" -"The following diagram shows the relationships among the OpenStack services:" -msgstr "" - -#: ../common/app_support.rst:77 ../common/app_support.rst:75 -msgid "" -"The following documentation provides reference and guidance information for " -"the OpenStack APIs:" -msgstr "" - -#: ../common/cli_manage_images.rst:202 -msgid "" -"The following example shows how to update an existing image with a " -"properties that describe the disk bus, the CD-ROM bus, and the VIF model:" -msgstr "" - -#: ../common/cli_install_openstack_command_line_clients.rst:173 -#: ../common/cli_install_openstack_command_line_clients.rst:179 -#: ../common/cli_install_openstack_command_line_clients.rst:181 -#: ../common/cli_install_openstack_command_line_clients.rst:183 -#: ../common/cli_install_openstack_command_line_clients.rst:185 -msgid "" -"The following example shows the command for installing the nova client with " -"``pip``." -msgstr "" - -#: ../common/cli_manage_images.rst:194 -msgid "" -"The following example shows the command that you would use to upload a " -"CentOS 6.3 image in qcow2 format and configure it for public access:" -msgstr "" - -#: ../common/nova_show_usage_statistics_for_hosts_instances.rst:18 -msgid "" -"The following examples show the host usage statistics for a host called " -"``devstack``." -msgstr "" - -#: ../common/cli_manage_images.rst:128 -msgid "" -"The following list explains the optional arguments that you can use with the " -"``create`` and ``update`` commands to modify image properties. For more " -"information, refer to Image service chapter in the `OpenStack Command-Line " -"Interface Reference `__." -msgstr "" - -#: ../common/app_support.rst:7 ../common/app_support.rst:5 -msgid "" -"The following resources are available to help you run and use OpenStack. The " -"OpenStack community constantly improves and adds to the main features of " -"OpenStack, but if you have any questions, do not hesitate to ask. Use the " -"following resources to get OpenStack support, and troubleshoot your " -"installations." -msgstr "" - -#: ../common/get_started_with_openstack.rst:18 -#: ../common/get_started_with_openstack.rst:26 -msgid "" -"The following table describes the OpenStack services that make up the " -"OpenStack architecture:" -msgstr "" - -#: ../common/cli_overview.rst:28 -msgid "" -"The following table lists the command-line client for each OpenStack service " -"with its package name and description." -msgstr "" - -#: ../common/cli_nova_evacuate.rst:30 -msgid "" -"The instance is booted from a new disk, but preserves its configuration " -"including its ID, name, uid, IP address, and so on. The command returns a " -"password::" -msgstr "" - -#: ../common/dashboard_customizing.rst:120 -msgid "" -"The logo also acts as a hyperlink. The default behavior is to redirect to " -"``horizon:user_home``. To change this, add the following attribute to :file:" -"`local_settings.py`::" -msgstr "" - -#: ../common/glossary.rst:2265 ../common/glossary.rst:2272 -#: ../common/glossary.rst:2271 ../common/glossary.rst:2260 -msgid "" -"The main virtual communication line used by all AMQP messages for inter-" -"cloud communications within Compute." -msgstr "" - -#: ../common/glossary.rst:3206 ../common/glossary.rst:3213 -#: ../common/glossary.rst:3220 ../common/glossary.rst:3228 -#: ../common/glossary.rst:3217 -msgid "" -"The method of storage used by horizon to track client sessions, such as " -"local memory, cookies, a database, or memcached." -msgstr "" - -#: ../common/glossary.rst:3328 ../common/glossary.rst:3335 -#: ../common/glossary.rst:3342 ../common/glossary.rst:3350 -#: ../common/glossary.rst:3339 -msgid "" -"The method that a service uses for persistent storage, such as iSCSI, NFS, " -"or local disk." -msgstr "" - -#: ../common/glossary.rst:2977 ../common/glossary.rst:2984 -#: ../common/glossary.rst:2991 ../common/glossary.rst:2993 -#: ../common/glossary.rst:2982 -msgid "" -"The method used by the Compute RabbitMQ for intra-service communications." -msgstr "" - -#: ../common/cli_manage_images.rst:154 -msgid "The minimum amount of RAM needed to boot the image, in megabytes." -msgstr "" - -#: ../common/cli_manage_images.rst:150 -msgid "The minimum size of the disk needed to boot the image, in gigabytes." -msgstr "" - -#: ../common/glossary.rst:176 -msgid "The most common web server software currently used on the Internet." -msgstr "" - -#: ../common/cli_manage_images.rst:135 -msgid "The name of the image." -msgstr "" - -#: ../common/glossary.rst:788 -msgid "" -"The nova-api daemon provides access to nova services. Can communicate with " -"other APIs, such as the Amazon EC2 API." -msgstr "" - -#: ../common/glossary.rst:2988 ../common/glossary.rst:2995 -#: ../common/glossary.rst:3002 ../common/glossary.rst:3004 -#: ../common/glossary.rst:2993 -msgid "The number of replicas of the data in an Object Storage ring." -msgstr "" - -#: ../common/glossary.rst:121 -msgid "" -"The open standard messaging protocol used by OpenStack components for intra-" -"service communications, provided by RabbitMQ, Qpid, or ZeroMQ." -msgstr "" - -#: ../common/cli_manage_volumes.rst:140 -msgid "" -"The output shows that the volume is attached to the server with ID " -"``84c6e57d-a6b1-44b6-81eb-fcb36afd31b5``, is in the nova availability zone, " -"and is bootable." -msgstr "" - -#: ../common/cli_manage_volumes.rst:301 -msgid "" -"The output shows the volume transfer ID in the ``id`` row and the " -"authorization key." -msgstr "" - -#: ../common/glossary.rst:381 -msgid "" -"The persistent data store used to save and retrieve information for a " -"service, such as lists of Object Storage objects, current state of guest " -"VMs, lists of user names, and so on. Also, the method that the Image service " -"uses to get and store VM images. Options include Object Storage, local file " -"system, S3, and HTTP." -msgstr "" - -#: ../common/glossary.rst:2618 ../common/glossary.rst:2625 -#: ../common/glossary.rst:2631 ../common/glossary.rst:2633 -#: ../common/glossary.rst:2622 -msgid "" -"The person responsible for planning and maintaining an OpenStack " -"installation." -msgstr "" - -#: ../common/glossary.rst:1533 ../common/glossary.rst:1534 -msgid "" -"The point where a user interacts with a service; can be an API endpoint, the " -"horizon dashboard, or a command-line tool." -msgstr "" - -#: ../common/glossary.rst:1298 ../common/glossary.rst:1299 -msgid "" -"The practice of placing one packet type within another for the purposes of " -"abstracting or securing data. Examples include GRE, MPLS, or IPsec." -msgstr "" - -#: ../common/glossary.rst:516 -msgid "" -"The practice of utilizing a secondary environment to elastically build " -"instances on-demand when the primary environment is resource constrained." -msgstr "" - -#: ../common/glossary.rst:3564 ../common/glossary.rst:3571 -#: ../common/glossary.rst:3578 ../common/glossary.rst:3586 -#: ../common/glossary.rst:3575 -msgid "" -"The primary load balancing configuration object. Specifies the virtual IP " -"address and port where client traffic is received. Also defines other " -"details such as the load balancing method to be used, protocol, and so on. " -"This entity is sometimes known in load-balancing products as a virtual " -"server, vserver, or listener." -msgstr "" - -#: ../common/cli_manage_volumes.rst:261 -msgid "" -"The procedure for volume transfer is intended for tenants (both the volume " -"donor and recipient) within the same cloud." -msgstr "" - -#: ../common/glossary.rst:261 -msgid "" -"The process associating a Compute floating IP address with a fixed IP " -"address." -msgstr "" - -#: ../common/glossary.rst:1968 ../common/glossary.rst:1974 -msgid "" -"The process of automating IP address allocation, deallocation, and " -"management. Currently provided by Compute, melange, and Networking." -msgstr "" - -#: ../common/get_started_identity.rst:34 ../common/get_started_identity.rst:33 -msgid "" -"The process of confirming the identity of a user. OpenStack Identity " -"confirms an incoming request by validating a set of credentials supplied by " -"the user." -msgstr "" - -#: ../common/glossary.rst:276 -msgid "" -"The process of connecting a VIF or vNIC to a L2 network in Networking. In " -"the context of Compute, this process connects a storage volume to an " -"instance." -msgstr "" - -#: ../common/glossary.rst:2993 ../common/glossary.rst:3000 -#: ../common/glossary.rst:3007 ../common/glossary.rst:3009 -#: ../common/glossary.rst:2998 -msgid "" -"The process of copying data to a separate physical device for fault " -"tolerance and performance." -msgstr "" - -#: ../common/glossary.rst:2909 ../common/glossary.rst:2916 -#: ../common/glossary.rst:2923 ../common/glossary.rst:2925 -#: ../common/glossary.rst:2914 -msgid "" -"The process of distributing Object Storage partitions across all drives in " -"the ring; used during initial ring creation and after ring reconfiguration." -msgstr "" - -#: ../common/glossary.rst:1877 ../common/glossary.rst:1883 -msgid "" -"The process of filtering incoming network traffic. Supported by Compute." -msgstr "" - -#: ../common/glossary.rst:1008 -msgid "" -"The process of finding duplicate data at the disk block, file, and/or object " -"level to minimize storage use—currently unsupported within OpenStack." -msgstr "" - -#: ../common/glossary.rst:1375 ../common/glossary.rst:1376 -msgid "" -"The process of migrating one or all virtual machine (VM) instances from one " -"host to another, compatible with both shared storage live migration and " -"block migration." -msgstr "" - -#: ../common/glossary.rst:2375 ../common/glossary.rst:2382 -#: ../common/glossary.rst:2381 ../common/glossary.rst:2387 -msgid "" -"The process of modifying IP address information while in transit. Supported " -"by Compute and Networking." -msgstr "" - -#: ../common/glossary.rst:2293 ../common/glossary.rst:2300 -#: ../common/glossary.rst:2299 ../common/glossary.rst:2288 -msgid "The process of moving a VM instance from one host to another." -msgstr "" - -#: ../common/glossary.rst:1888 ../common/glossary.rst:1894 -msgid "" -"The process of putting a file into a virtual machine image before the " -"instance is started." -msgstr "" - -#: ../common/glossary.rst:998 -msgid "" -"The process of removing the association between a floating IP address and a " -"fixed IP address. Once this association is removed, the floating IP returns " -"to the address pool." -msgstr "" - -#: ../common/glossary.rst:1124 -msgid "" -"The process of removing the association between a floating IP address and " -"fixed IP and thus returning the floating IP address to the address pool." +#: ../common/glossary.rst:2163 ../common/glossary.rst:2169 +msgid "load balancing" msgstr "" #: ../common/glossary.rst:2166 ../common/glossary.rst:2172 @@ -9186,492 +8447,4159 @@ msgid "" "improve performance and availability." msgstr "" -#: ../common/glossary.rst:139 +#: ../common/glossary.rst:2168 ../common/glossary.rst:2174 +msgid "LBaaS" +msgstr "" + +#: ../common/glossary.rst:2168 ../common/glossary.rst:2174 +msgid "Load-Balancer-as-a-Service (LBaaS)" +msgstr "" + +#: ../common/glossary.rst:2171 ../common/glossary.rst:2177 msgid "" -"The process of taking a floating IP address from the address pool so it can " -"be associated with a fixed IP on a guest VM instance." +"Enables Networking to distribute incoming requests evenly between designated " +"instances." msgstr "" -#: ../common/glossary.rst:310 +#: ../common/glossary.rst:2173 ../common/glossary.rst:2179 +msgid "Logical Volume Manager (LVM)" +msgstr "" + +#: ../common/glossary.rst:2176 ../common/glossary.rst:2182 msgid "" -"The process that confirms that the user, process, or client is really who " -"they say they are through private key, secret token, password, fingerprint, " -"or similar method." +"Provides a method of allocating space on mass-storage devices that is more " +"flexible than conventional partitioning schemes." msgstr "" -#: ../common/glossary.rst:606 +#: ../common/glossary.rst:2179 ../common/glossary.rst:2185 +msgid "magnetoDB" +msgstr "" + +#: ../common/glossary.rst:2182 ../common/glossary.rst:2187 +#: ../common/glossary.rst:2193 msgid "" -"The project name for the Telemetry service, which is an integrated project " -"that provides metering and measuring facilities for OpenStack." +"Code name for the OpenStack project that provides the Containers Service." msgstr "" -#: ../common/glossary.rst:2078 ../common/glossary.rst:2084 -msgid "The project that provides OpenStack Identity services." -msgstr "" - -#: ../common/glossary.rst:249 +#: ../common/glossary.rst:2182 ../common/glossary.rst:2188 msgid "" -"The protocol by which layer-3 IP addresses are resolved into layer-2 link " -"local addresses." +"OpenStack project that provides a Key-Value Store as a Service for OpenStack " +"users." msgstr "" -#: ../common/glossary.rst:1728 ../common/glossary.rst:1734 -msgid "The protocol that tells browsers where to go to find information." +#: ../common/glossary.rst:2184 ../common/glossary.rst:2189 +#: ../common/glossary.rst:2195 +msgid "management API" msgstr "" -#: ../common/get_started_compute.rst:129 ../common/get_started_compute.rst:128 -msgid "The queue" +#: ../common/glossary.rst:2187 ../common/glossary.rst:2192 +#: ../common/glossary.rst:2198 +msgid "Alternative term for an admin API." msgstr "" -#: ../common/cli_install_openstack_command_line_clients.rst:32 +#: ../common/glossary.rst:2188 ../common/glossary.rst:2193 +#: ../common/glossary.rst:2199 +msgid "management network" +msgstr "" + +#: ../common/glossary.rst:2191 ../common/glossary.rst:2196 +#: ../common/glossary.rst:2202 msgid "" -"The recommended way to install setuptools on Microsoft Windows is to follow " -"the documentation provided on the setuptools website (https://pypi.python." -"org/pypi/setuptools#windows). Another option is to use the unofficial binary " -"installer maintained by Christoph Gohlke (`http://www.lfd.uci.edu/~gohlke/" -"pythonlibs/ #setuptools `__)." +"A network segment used for administration, not accessible to the public " +"Internet." msgstr "" -#: ../common/cli_install_openstack_command_line_clients.rst:32 +#: ../common/glossary.rst:2193 ../common/glossary.rst:2198 +#: ../common/glossary.rst:2204 +msgid "manager" +msgstr "" + +#: ../common/glossary.rst:2196 ../common/glossary.rst:2201 +#: ../common/glossary.rst:2207 msgid "" -"The recommended way to install setuptools on Microsoft Windows is to follow " -"the documentation provided on the setuptools website (https://pypi.python." -"org/pypi/setuptools). Another option is to use the unofficial binary " -"installer maintained by Christoph Gohlke (`http://www.lfd.uci.edu/~gohlke/" -"pythonlibs/ #setuptools `__)." +"Logical groupings of related code, such as the Block Storage volume manager " +"or network manager." msgstr "" -#: ../common/get_started_image_service.rst:30 +#: ../common/glossary.rst:2198 ../common/glossary.rst:2203 +#: ../common/glossary.rst:2209 +msgid "manifest" +msgstr "" + +#: ../common/glossary.rst:2201 ../common/glossary.rst:2206 +#: ../common/glossary.rst:2212 +msgid "Used to track segments of a large object within Object Storage." +msgstr "" + +#: ../common/glossary.rst:2203 ../common/glossary.rst:2208 +#: ../common/glossary.rst:2214 +msgid "manifest object" +msgstr "" + +#: ../common/glossary.rst:2206 ../common/glossary.rst:2211 +#: ../common/glossary.rst:2217 msgid "" -"The registry is a private internal service meant for use by OpenStack Image " -"Service. Do not disclose it to users." +"A special Object Storage object that contains the manifest for a large " +"object." msgstr "" -#: ../common/get_started_image_service.rst:30 -#: ../common/get_started_image_service.rst:27 +#: ../common/glossary.rst:2211 ../common/glossary.rst:2216 +#: ../common/glossary.rst:2222 msgid "" -"The registry is a private internal service meant for use by OpenStack Image " -"service. Do not disclose it to users." +"OpenStack project that provides shared file systems as service to " +"applications." msgstr "" -#: ../common/support-compute.rst:63 -msgid "The report has the following sections:" +#: ../common/glossary.rst:2213 ../common/glossary.rst:2218 +#: ../common/glossary.rst:2224 +msgid "maximum transmission unit (MTU)" msgstr "" -#: ../common/glossary.rst:2877 ../common/glossary.rst:2884 -#: ../common/glossary.rst:2891 ../common/glossary.rst:2893 -#: ../common/glossary.rst:2882 +#: ../common/glossary.rst:2216 ../common/glossary.rst:2221 +#: ../common/glossary.rst:2227 msgid "" -"The router advertisement daemon, used by the Compute VLAN manager and " -"FlatDHCP manager to provide routing services for VM instances." +"Maximum frame or packet size for a particular network medium. Typically 1500 " +"bytes for Ethernet networks." msgstr "" -#: ../common/nova_show_usage_statistics_for_hosts_instances.rst:63 +#: ../common/glossary.rst:2218 ../common/glossary.rst:2223 +#: ../common/glossary.rst:2229 +msgid "mechanism driver" +msgstr "" + +#: ../common/glossary.rst:2221 ../common/glossary.rst:2226 +#: ../common/glossary.rst:2232 msgid "" -"The row that has the value ``used_max`` in the ``PROJECT`` column shows the " -"sum of the resources allocated to the instances that run on the host." +"A driver for the Modular Layer 2 (ML2) neutron plug-in that provides layer-2 " +"connectivity for virtual instances. A single OpenStack installation can use " +"multiple mechanism drivers." msgstr "" -#: ../common/nova_show_usage_statistics_for_hosts_instances.rst:58 +#: ../common/glossary.rst:2225 ../common/glossary.rst:2230 +#: ../common/glossary.rst:2236 ../common/glossary.rst:2237 +msgid "melange" +msgstr "" + +#: ../common/glossary.rst:2228 ../common/glossary.rst:2233 +#: ../common/glossary.rst:2239 ../common/glossary.rst:2240 msgid "" -"The row that has the value ``used_now`` in the ``PROJECT`` column shows the " -"sum of the resources allocated to the instances that run on the host, plus " -"the resources allocated to the virtual machine of the host itself." +"Project name for OpenStack Network Information Service. To be merged with " +"Networking." msgstr "" -#: ../common/get_started_orchestration.rst:16 -#: ../common/get_started_orchestration.rst:15 +#: ../common/glossary.rst:2230 +msgid "Meiji" +msgstr "" + +#: ../common/glossary.rst:2230 ../common/glossary.rst:2235 +#: ../common/glossary.rst:2241 ../common/glossary.rst:2242 +msgid "membership" +msgstr "" + +#: ../common/glossary.rst:2233 ../common/glossary.rst:2238 +#: ../common/glossary.rst:2244 ../common/glossary.rst:2245 msgid "" -"The service enables deployers to integrate with the Orchestration module " -"directly or through custom plug-ins." +"The association between an Image service VM image and a tenant. Enables " +"images to be shared with specified tenants." msgstr "" -#: ../common/glossary.rst:2260 ../common/glossary.rst:2267 -#: ../common/glossary.rst:2266 ../common/glossary.rst:2255 +#: ../common/glossary.rst:2233 +msgid "" +"The code name for the thirteenth release of OpenStack. The design summit " +"will take place in Tokyo, Japan. The code name comes from the locations " +"Meiji shrine and Meiji park in Tokyo. They are named after the emperor Meiji." +msgstr "" + +#: ../common/glossary.rst:2235 ../common/glossary.rst:2240 +#: ../common/glossary.rst:2246 ../common/glossary.rst:2247 +msgid "membership list" +msgstr "" + +#: ../common/glossary.rst:2240 ../common/glossary.rst:2245 +#: ../common/glossary.rst:2251 ../common/glossary.rst:2252 +msgid "memcached" +msgstr "" + +#: ../common/glossary.rst:2243 ../common/glossary.rst:2248 +#: ../common/glossary.rst:2254 ../common/glossary.rst:2255 +msgid "" +"A distributed memory object caching system that is used by Object Storage " +"for caching." +msgstr "" + +#: ../common/glossary.rst:2245 ../common/glossary.rst:2250 +#: ../common/glossary.rst:2256 ../common/glossary.rst:2257 +msgid "memory overcommit" +msgstr "" + +#: ../common/glossary.rst:2248 ../common/glossary.rst:2253 +#: ../common/glossary.rst:2259 ../common/glossary.rst:2260 +msgid "" +"The ability to start new VM instances based on the actual memory usage of a " +"host, as opposed to basing the decision on the amount of RAM each running " +"instance thinks it has available. Also known as RAM overcommit." +msgstr "" + +#: ../common/glossary.rst:2252 ../common/glossary.rst:2257 +#: ../common/glossary.rst:2263 ../common/glossary.rst:2264 +msgid "message broker" +msgstr "" + +#: ../common/glossary.rst:2255 ../common/glossary.rst:2260 +#: ../common/glossary.rst:2266 ../common/glossary.rst:2267 msgid "" "The software package used to provide AMQP messaging capabilities within " "Compute. Default package is RabbitMQ." msgstr "" -#: ../common/get_started_sahara.rst:14 ../common/get_started_sahara.rst:15 -msgid "The solution addresses the following use cases:" +#: ../common/glossary.rst:2257 ../common/glossary.rst:2262 +#: ../common/glossary.rst:2268 ../common/glossary.rst:2269 +msgid "message bus" msgstr "" -#: ../common/glossary.rst:1780 ../common/glossary.rst:1786 +#: ../common/glossary.rst:2260 ../common/glossary.rst:2265 +#: ../common/glossary.rst:2271 ../common/glossary.rst:2272 msgid "" -"The source used by Identity service to retrieve user information; an " -"OpenLDAP server, for example." +"The main virtual communication line used by all AMQP messages for inter-" +"cloud communications within Compute." msgstr "" -#: ../common/glossary.rst:1452 ../common/glossary.rst:1453 -msgid "" -"The step in the Compute scheduling process when hosts that cannot run VMs " -"are eliminated and not chosen." +#: ../common/glossary.rst:2262 ../common/glossary.rst:2267 +#: ../common/glossary.rst:2273 ../common/glossary.rst:2274 +msgid "message queue" msgstr "" -#: ../common/glossary.rst:374 +#: ../common/glossary.rst:2265 ../common/glossary.rst:2270 +#: ../common/glossary.rst:2276 ../common/glossary.rst:2277 msgid "" -"The storage method used by the Identity service catalog service to store and " -"retrieve information about API endpoints that are available to the client. " -"Examples include a SQL database, LDAP database, or KVS back end." +"Passes requests from clients to the appropriate workers and returns the " +"output to the client after the job completes." +msgstr "" + +#: ../common/glossary.rst:2267 ../common/glossary.rst:2272 +#: ../common/glossary.rst:2278 ../common/glossary.rst:2279 +msgid "Message service" +msgstr "" + +#: ../common/glossary.rst:2270 ../common/glossary.rst:2275 +#: ../common/glossary.rst:2281 ../common/glossary.rst:2282 +msgid "" +"OpenStack project that aims to produce an OpenStack messaging service that " +"affords a variety of distributed application patterns in an efficient, " +"scalable and highly-available manner, and to create and maintain associated " +"Python libraries and documentation. The code name for the project is zaqar." +msgstr "" + +#: ../common/glossary.rst:2276 ../common/glossary.rst:2281 +#: ../common/glossary.rst:2287 ../common/glossary.rst:2288 +msgid "Metadata agent" +msgstr "" + +#: ../common/glossary.rst:2279 ../common/glossary.rst:2284 +#: ../common/glossary.rst:2290 ../common/glossary.rst:2291 +msgid "" +"OpenStack Networking agent that provides metadata services for instances." +msgstr "" + +#: ../common/glossary.rst:2281 ../common/glossary.rst:2286 +#: ../common/glossary.rst:2292 ../common/glossary.rst:2293 +msgid "Meta-Data Server (MDS)" +msgstr "" + +#: ../common/glossary.rst:2284 ../common/glossary.rst:2289 +#: ../common/glossary.rst:2295 ../common/glossary.rst:2296 +msgid "Stores CephFS metadata." +msgstr "" + +#: ../common/glossary.rst:2285 ../common/glossary.rst:2290 +#: ../common/glossary.rst:2296 ../common/glossary.rst:2297 +msgid "migration" +msgstr "" + +#: ../common/glossary.rst:2288 ../common/glossary.rst:2293 +#: ../common/glossary.rst:2299 ../common/glossary.rst:2300 +msgid "The process of moving a VM instance from one host to another." +msgstr "" + +#: ../common/glossary.rst:2293 ../common/glossary.rst:2298 +#: ../common/glossary.rst:2304 ../common/glossary.rst:2305 +msgid "OpenStack project that provides the Workflow service." +msgstr "" + +#: ../common/glossary.rst:2294 ../common/glossary.rst:2299 +#: ../common/glossary.rst:2305 +msgid "Mitaka" +msgstr "" + +#: ../common/glossary.rst:2297 ../common/glossary.rst:2302 +#: ../common/glossary.rst:2308 +msgid "" +"The code name for the thirteenth release of OpenStack. The design summit " +"will take place in Tokyo, Japan. Mitaka is a city in Tokyo." +msgstr "" + +#: ../common/glossary.rst:2299 ../common/glossary.rst:2300 +#: ../common/glossary.rst:2305 ../common/glossary.rst:2306 +#: ../common/glossary.rst:2311 +msgid "multi-host" +msgstr "" + +#: ../common/glossary.rst:2302 ../common/glossary.rst:2303 +#: ../common/glossary.rst:2308 ../common/glossary.rst:2309 +#: ../common/glossary.rst:2314 +msgid "" +"High-availability mode for legacy (nova) networking. Each compute node " +"handles NAT and DHCP and acts as a gateway for all of the VMs on it. A " +"networking failure on one compute node doesn't affect VMs on other compute " +"nodes." +msgstr "" + +#: ../common/glossary.rst:2306 ../common/glossary.rst:2307 +#: ../common/glossary.rst:2312 ../common/glossary.rst:2313 +#: ../common/glossary.rst:2318 +msgid "multinic" +msgstr "" + +#: ../common/glossary.rst:2309 ../common/glossary.rst:2310 +#: ../common/glossary.rst:2315 ../common/glossary.rst:2316 +#: ../common/glossary.rst:2321 +msgid "" +"Facility in Compute that allows each virtual machine instance to have more " +"than one VIF connected to it." +msgstr "" + +#: ../common/glossary.rst:2314 ../common/glossary.rst:2315 +#: ../common/glossary.rst:2320 ../common/glossary.rst:2321 +#: ../common/glossary.rst:2326 +msgid "OpenStack project that provides an Application catalog." +msgstr "" + +#: ../common/glossary.rst:2315 ../common/glossary.rst:2316 +#: ../common/glossary.rst:2321 ../common/glossary.rst:2322 +#: ../common/glossary.rst:2327 +msgid "Modular Layer 2 (ML2) neutron plug-in" +msgstr "" + +#: ../common/glossary.rst:2318 ../common/glossary.rst:2319 +#: ../common/glossary.rst:2324 ../common/glossary.rst:2325 +#: ../common/glossary.rst:2330 +msgid "" +"Can concurrently use multiple layer-2 networking technologies, such as " +"802.1Q and VXLAN, in Networking." +msgstr "" + +#: ../common/glossary.rst:2320 ../common/glossary.rst:2321 +#: ../common/glossary.rst:2326 ../common/glossary.rst:2327 +#: ../common/glossary.rst:2332 +msgid "Monitor (LBaaS)" +msgstr "" + +#: ../common/glossary.rst:2323 ../common/glossary.rst:2324 +#: ../common/glossary.rst:2329 ../common/glossary.rst:2330 +#: ../common/glossary.rst:2335 +msgid "" +"LBaaS feature that provides availability monitoring using the `ping` " +"command, TCP, and HTTP/HTTPS GET." +msgstr "" + +#: ../common/glossary.rst:2325 ../common/glossary.rst:2326 +#: ../common/glossary.rst:2331 ../common/glossary.rst:2332 +#: ../common/glossary.rst:2337 +msgid "Monitor (Mon)" +msgstr "" + +#: ../common/glossary.rst:2328 ../common/glossary.rst:2329 +#: ../common/glossary.rst:2334 ../common/glossary.rst:2335 +#: ../common/glossary.rst:2340 +msgid "" +"A Ceph component that communicates with external clients, checks data state " +"and consistency, and performs quorum functions." +msgstr "" + +#: ../common/glossary.rst:2330 ../common/glossary.rst:2331 +#: ../common/glossary.rst:2336 ../common/glossary.rst:2337 +#: ../common/glossary.rst:2342 +msgid "multi-factor authentication" +msgstr "" + +#: ../common/glossary.rst:2333 ../common/glossary.rst:2334 +#: ../common/glossary.rst:2339 ../common/glossary.rst:2340 +#: ../common/glossary.rst:2345 +msgid "" +"Authentication method that uses two or more credentials, such as a password " +"and a private key. Currently not supported in Identity." +msgstr "" + +#: ../common/glossary.rst:2336 ../common/glossary.rst:2337 +#: ../common/glossary.rst:2342 ../common/glossary.rst:2343 +#: ../common/glossary.rst:2348 +msgid "MultiNic" +msgstr "" + +#: ../common/glossary.rst:2339 ../common/glossary.rst:2340 +#: ../common/glossary.rst:2345 ../common/glossary.rst:2346 +#: ../common/glossary.rst:2351 +msgid "" +"Facility in Compute that enables a virtual machine instance to have more " +"than one VIF connected to it." +msgstr "" + +#: ../common/glossary.rst:2341 ../common/glossary.rst:2342 +#: ../common/glossary.rst:2347 ../common/glossary.rst:2348 +#: ../common/glossary.rst:2353 +msgid "network namespace" +msgstr "" + +#: ../common/glossary.rst:2344 ../common/glossary.rst:2345 +#: ../common/glossary.rst:2350 ../common/glossary.rst:2351 +#: ../common/glossary.rst:2356 +msgid "" +"Linux kernel feature that provides independent virtual networking instances " +"on a single host with separate routing tables and interfaces. Similar to " +"virtual routing and forwarding (VRF) services on physical network equipment." +msgstr "" + +#: ../common/glossary.rst:2348 ../common/glossary.rst:2349 +#: ../common/glossary.rst:2354 ../common/glossary.rst:2355 +#: ../common/glossary.rst:2360 +msgid "Nebula" +msgstr "" + +#: ../common/glossary.rst:2351 ../common/glossary.rst:2352 +#: ../common/glossary.rst:2357 ../common/glossary.rst:2358 +#: ../common/glossary.rst:2363 +msgid "Released as open source by NASA in 2010 and is the basis for Compute." +msgstr "" + +#: ../common/glossary.rst:2353 ../common/glossary.rst:2354 +#: ../common/glossary.rst:2359 ../common/glossary.rst:2360 +#: ../common/glossary.rst:2365 +msgid "netadmin" +msgstr "" + +#: ../common/glossary.rst:2356 ../common/glossary.rst:2357 +#: ../common/glossary.rst:2362 ../common/glossary.rst:2363 +#: ../common/glossary.rst:2368 +msgid "" +"One of the default roles in the Compute RBAC system. Enables the user to " +"allocate publicly accessible IP addresses to instances and change firewall " +"rules." +msgstr "" + +#: ../common/glossary.rst:2359 ../common/glossary.rst:2360 +#: ../common/glossary.rst:2365 ../common/glossary.rst:2366 +#: ../common/glossary.rst:2371 +msgid "NetApp volume driver" +msgstr "" + +#: ../common/glossary.rst:2362 ../common/glossary.rst:2363 +#: ../common/glossary.rst:2368 ../common/glossary.rst:2369 +#: ../common/glossary.rst:2374 +msgid "" +"Enables Compute to communicate with NetApp storage devices through the " +"NetApp OnCommand Provisioning Manager." +msgstr "" + +#: ../common/glossary.rst:2365 ../common/glossary.rst:2366 +#: ../common/glossary.rst:2371 ../common/glossary.rst:2372 +#: ../common/glossary.rst:2377 +msgid "network" +msgstr "" + +#: ../common/glossary.rst:2368 ../common/glossary.rst:2369 +#: ../common/glossary.rst:2374 ../common/glossary.rst:2375 +#: ../common/glossary.rst:2380 +msgid "" +"A virtual network that provides connectivity between entities. For example, " +"a collection of virtual ports that share network connectivity. In Networking " +"terminology, a network is always a layer-2 network." +msgstr "" + +#: ../common/glossary.rst:2372 ../common/glossary.rst:2378 +#: ../common/glossary.rst:2379 ../common/glossary.rst:2384 +msgid "Network Address Translation (NAT)" +msgstr "" + +#: ../common/glossary.rst:2373 ../common/glossary.rst:2384 +msgid "NAT" +msgstr "" + +#: ../common/glossary.rst:2375 ../common/glossary.rst:2381 +#: ../common/glossary.rst:2382 ../common/glossary.rst:2387 +msgid "" +"The process of modifying IP address information while in transit. Supported " +"by Compute and Networking." +msgstr "" + +#: ../common/glossary.rst:2376 ../common/glossary.rst:2387 +msgid "" +"Network Address Translation; Process of modifying IP address information " +"while in transit. Supported by Compute and Networking." +msgstr "" + +#: ../common/glossary.rst:2377 ../common/glossary.rst:2379 +#: ../common/glossary.rst:2383 ../common/glossary.rst:2384 +#: ../common/glossary.rst:2389 ../common/glossary.rst:2390 +msgid "network controller" +msgstr "" + +#: ../common/glossary.rst:2380 ../common/glossary.rst:2382 +#: ../common/glossary.rst:2386 ../common/glossary.rst:2387 +#: ../common/glossary.rst:2392 ../common/glossary.rst:2393 +msgid "" +"A Compute daemon that orchestrates the network configuration of nodes, " +"including IP addresses, VLANs, and bridging. Also manages routing for both " +"public and private networks." +msgstr "" + +#: ../common/glossary.rst:2383 ../common/glossary.rst:2385 +#: ../common/glossary.rst:2389 ../common/glossary.rst:2390 +#: ../common/glossary.rst:2395 ../common/glossary.rst:2396 +msgid "Network File System (NFS)" +msgstr "" + +#: ../common/glossary.rst:2386 ../common/glossary.rst:2388 +#: ../common/glossary.rst:2392 ../common/glossary.rst:2393 +#: ../common/glossary.rst:2398 ../common/glossary.rst:2399 +msgid "" +"A method for making file systems available over the network. Supported by " +"OpenStack." +msgstr "" + +#: ../common/glossary.rst:2388 ../common/glossary.rst:2390 +#: ../common/glossary.rst:2394 ../common/glossary.rst:2395 +#: ../common/glossary.rst:2400 ../common/glossary.rst:2401 +msgid "network ID" +msgstr "" + +#: ../common/glossary.rst:2391 ../common/glossary.rst:2393 +#: ../common/glossary.rst:2397 ../common/glossary.rst:2398 +#: ../common/glossary.rst:2403 ../common/glossary.rst:2404 +msgid "" +"Unique ID assigned to each network segment within Networking. Same as " +"network UUID." +msgstr "" + +#: ../common/glossary.rst:2393 ../common/glossary.rst:2395 +#: ../common/glossary.rst:2399 ../common/glossary.rst:2400 +#: ../common/glossary.rst:2405 ../common/glossary.rst:2406 +msgid "network manager" +msgstr "" + +#: ../common/glossary.rst:2396 ../common/glossary.rst:2398 +#: ../common/glossary.rst:2402 ../common/glossary.rst:2403 +#: ../common/glossary.rst:2408 ../common/glossary.rst:2409 +msgid "" +"The Compute component that manages various network components, such as " +"firewall rules, IP address allocation, and so on." +msgstr "" + +#: ../common/glossary.rst:2398 ../common/glossary.rst:2400 +#: ../common/glossary.rst:2404 ../common/glossary.rst:2405 +#: ../common/glossary.rst:2410 ../common/glossary.rst:2411 +msgid "network node" +msgstr "" + +#: ../common/glossary.rst:2401 ../common/glossary.rst:2403 +#: ../common/glossary.rst:2407 ../common/glossary.rst:2408 +#: ../common/glossary.rst:2413 ../common/glossary.rst:2414 +msgid "Any compute node that runs the network worker daemon." +msgstr "" + +#: ../common/glossary.rst:2402 ../common/glossary.rst:2404 +#: ../common/glossary.rst:2408 ../common/glossary.rst:2409 +#: ../common/glossary.rst:2414 ../common/glossary.rst:2415 +msgid "network segment" +msgstr "" + +#: ../common/glossary.rst:2405 ../common/glossary.rst:2407 +#: ../common/glossary.rst:2411 ../common/glossary.rst:2412 +#: ../common/glossary.rst:2417 ../common/glossary.rst:2418 +msgid "Represents a virtual, isolated OSI layer-2 subnet in Networking." +msgstr "" + +#: ../common/glossary.rst:2407 ../common/glossary.rst:2413 +#: ../common/glossary.rst:2414 ../common/glossary.rst:2419 +msgid "Network Time Protocol (NTP)" +msgstr "" + +#: ../common/glossary.rst:2409 ../common/glossary.rst:2420 +msgid "NTP" +msgstr "" + +#: ../common/glossary.rst:2410 ../common/glossary.rst:2416 +#: ../common/glossary.rst:2417 ../common/glossary.rst:2422 +msgid "" +"A method of keeping a clock for a host or node correct through " +"communications with a trusted, accurate time source." +msgstr "" + +#: ../common/glossary.rst:2412 ../common/glossary.rst:2423 +msgid "" +"Network Time Protocol; Method of keeping a clock for a host or node correct " +"via communication with a trusted, accurate time source." +msgstr "" + +#: ../common/glossary.rst:2412 ../common/glossary.rst:2415 +#: ../common/glossary.rst:2418 ../common/glossary.rst:2419 +#: ../common/glossary.rst:2424 ../common/glossary.rst:2426 +msgid "network UUID" +msgstr "" + +#: ../common/glossary.rst:2415 ../common/glossary.rst:2418 +#: ../common/glossary.rst:2421 ../common/glossary.rst:2422 +#: ../common/glossary.rst:2427 ../common/glossary.rst:2429 +msgid "Unique ID for a Networking network segment." +msgstr "" + +#: ../common/glossary.rst:2416 ../common/glossary.rst:2419 +#: ../common/glossary.rst:2422 ../common/glossary.rst:2423 +#: ../common/glossary.rst:2428 ../common/glossary.rst:2430 +msgid "network worker" +msgstr "" + +#: ../common/glossary.rst:2419 ../common/glossary.rst:2422 +#: ../common/glossary.rst:2425 ../common/glossary.rst:2426 +#: ../common/glossary.rst:2431 ../common/glossary.rst:2433 +msgid "" +"The `nova-network` worker daemon; provides services such as giving an IP " +"address to a booting nova instance." +msgstr "" + +#: ../common/glossary.rst:2425 ../common/glossary.rst:2428 +#: ../common/glossary.rst:2431 ../common/glossary.rst:2432 +#: ../common/glossary.rst:2437 ../common/glossary.rst:2439 +msgid "" +"A core OpenStack project that provides a network connectivity abstraction " +"layer to OpenStack Compute. The project name of Networking is neutron." +msgstr "" + +#: ../common/glossary.rst:2428 ../common/glossary.rst:2431 +#: ../common/glossary.rst:2434 ../common/glossary.rst:2435 +#: ../common/glossary.rst:2440 ../common/glossary.rst:2442 +msgid "Networking API" +msgstr "" + +#: ../common/glossary.rst:2431 ../common/glossary.rst:2434 +#: ../common/glossary.rst:2437 ../common/glossary.rst:2438 +#: ../common/glossary.rst:2443 ../common/glossary.rst:2445 +msgid "" +"API used to access OpenStack Networking. Provides an extensible architecture " +"to enable custom plug-in creation." +msgstr "" + +#: ../common/glossary.rst:2436 ../common/glossary.rst:2439 +#: ../common/glossary.rst:2442 ../common/glossary.rst:2443 +#: ../common/glossary.rst:2448 ../common/glossary.rst:2450 +msgid "" +"A core OpenStack project that provides a network connectivity abstraction " +"layer to OpenStack Compute." +msgstr "" + +#: ../common/glossary.rst:2438 ../common/glossary.rst:2441 +#: ../common/glossary.rst:2444 ../common/glossary.rst:2445 +#: ../common/glossary.rst:2450 ../common/glossary.rst:2452 +msgid "neutron API" +msgstr "" + +#: ../common/glossary.rst:2441 ../common/glossary.rst:2444 +#: ../common/glossary.rst:2447 ../common/glossary.rst:2448 +#: ../common/glossary.rst:2453 ../common/glossary.rst:2455 +msgid "An alternative name for Networking API." +msgstr "" + +#: ../common/glossary.rst:2442 ../common/glossary.rst:2445 +#: ../common/glossary.rst:2448 ../common/glossary.rst:2449 +#: ../common/glossary.rst:2454 ../common/glossary.rst:2456 +msgid "neutron manager" +msgstr "" + +#: ../common/glossary.rst:2445 ../common/glossary.rst:2448 +#: ../common/glossary.rst:2451 ../common/glossary.rst:2452 +#: ../common/glossary.rst:2457 ../common/glossary.rst:2459 +msgid "" +"Enables Compute and Networking integration, which enables Networking to " +"perform network management for guest VMs." +msgstr "" + +#: ../common/glossary.rst:2447 ../common/glossary.rst:2450 +#: ../common/glossary.rst:2453 ../common/glossary.rst:2454 +#: ../common/glossary.rst:2459 ../common/glossary.rst:2461 +msgid "neutron plug-in" +msgstr "" + +#: ../common/glossary.rst:2450 ../common/glossary.rst:2453 +#: ../common/glossary.rst:2456 ../common/glossary.rst:2457 +#: ../common/glossary.rst:2462 ../common/glossary.rst:2464 +msgid "" +"Interface within Networking that enables organizations to create custom plug-" +"ins for advanced features, such as QoS, ACLs, or IDS." +msgstr "" + +#: ../common/glossary.rst:2453 ../common/glossary.rst:2456 +#: ../common/glossary.rst:2459 ../common/glossary.rst:2460 +#: ../common/glossary.rst:2465 ../common/glossary.rst:2467 +msgid "Nexenta volume driver" +msgstr "" + +#: ../common/glossary.rst:2456 ../common/glossary.rst:2459 +#: ../common/glossary.rst:2462 ../common/glossary.rst:2463 +#: ../common/glossary.rst:2468 ../common/glossary.rst:2470 +msgid "Provides support for NexentaStor devices in Compute." +msgstr "" + +#: ../common/glossary.rst:2457 ../common/glossary.rst:2460 +#: ../common/glossary.rst:2463 ../common/glossary.rst:2464 +#: ../common/glossary.rst:2469 ../common/glossary.rst:2471 +msgid "No ACK" +msgstr "" + +#: ../common/glossary.rst:2460 ../common/glossary.rst:2463 +#: ../common/glossary.rst:2466 ../common/glossary.rst:2467 +#: ../common/glossary.rst:2472 ../common/glossary.rst:2474 +msgid "" +"Disables server-side message acknowledgment in the Compute RabbitMQ. " +"Increases performance but decreases reliability." +msgstr "" + +#: ../common/glossary.rst:2462 ../common/glossary.rst:2465 +#: ../common/glossary.rst:2468 ../common/glossary.rst:2469 +#: ../common/glossary.rst:2474 ../common/glossary.rst:2476 +msgid "node" +msgstr "" + +#: ../common/glossary.rst:2465 ../common/glossary.rst:2468 +#: ../common/glossary.rst:2471 ../common/glossary.rst:2472 +#: ../common/glossary.rst:2477 ../common/glossary.rst:2479 +msgid "A VM instance that runs on a host." +msgstr "" + +#: ../common/glossary.rst:2466 ../common/glossary.rst:2469 +#: ../common/glossary.rst:2472 ../common/glossary.rst:2473 +#: ../common/glossary.rst:2478 ../common/glossary.rst:2480 +msgid "non-durable exchange" +msgstr "" + +#: ../common/glossary.rst:2469 ../common/glossary.rst:2472 +#: ../common/glossary.rst:2475 ../common/glossary.rst:2476 +#: ../common/glossary.rst:2481 ../common/glossary.rst:2483 +msgid "" +"Message exchange that is cleared when the service restarts. Its data is not " +"written to persistent storage." +msgstr "" + +#: ../common/glossary.rst:2471 ../common/glossary.rst:2474 +#: ../common/glossary.rst:2477 ../common/glossary.rst:2478 +#: ../common/glossary.rst:2483 ../common/glossary.rst:2485 +msgid "non-durable queue" +msgstr "" + +#: ../common/glossary.rst:2474 ../common/glossary.rst:2477 +#: ../common/glossary.rst:2480 ../common/glossary.rst:2481 +#: ../common/glossary.rst:2486 ../common/glossary.rst:2488 +msgid "" +"Message queue that is cleared when the service restarts. Its data is not " +"written to persistent storage." +msgstr "" + +#: ../common/glossary.rst:2476 ../common/glossary.rst:2479 +#: ../common/glossary.rst:2482 ../common/glossary.rst:2483 +#: ../common/glossary.rst:2488 ../common/glossary.rst:2490 +msgid "non-persistent volume" +msgstr "" + +#: ../common/glossary.rst:2479 ../common/glossary.rst:2482 +#: ../common/glossary.rst:2485 ../common/glossary.rst:2486 +#: ../common/glossary.rst:2491 ../common/glossary.rst:2493 +msgid "Alternative term for an ephemeral volume." +msgstr "" + +#: ../common/glossary.rst:2480 ../common/glossary.rst:2483 +#: ../common/glossary.rst:2486 ../common/glossary.rst:2487 +#: ../common/glossary.rst:2492 ../common/glossary.rst:2494 +msgid "north-south traffic" +msgstr "" + +#: ../common/glossary.rst:2483 ../common/glossary.rst:2486 +#: ../common/glossary.rst:2489 ../common/glossary.rst:2490 +#: ../common/glossary.rst:2495 ../common/glossary.rst:2497 +msgid "" +"Network traffic between a user or client (north) and a server (south), or " +"traffic into the cloud (south) and out of the cloud (north). See also east-" +"west traffic." +msgstr "" + +#: ../common/glossary.rst:2489 ../common/glossary.rst:2492 +#: ../common/glossary.rst:2495 ../common/glossary.rst:2496 +#: ../common/glossary.rst:2501 ../common/glossary.rst:2503 +msgid "OpenStack project that provides compute services." +msgstr "" + +#: ../common/glossary.rst:2490 ../common/glossary.rst:2493 +#: ../common/glossary.rst:2496 ../common/glossary.rst:2497 +#: ../common/glossary.rst:2502 ../common/glossary.rst:2504 +msgid "Nova API" +msgstr "" + +#: ../common/glossary.rst:2493 ../common/glossary.rst:2496 +#: ../common/glossary.rst:2499 ../common/glossary.rst:2500 +#: ../common/glossary.rst:2505 ../common/glossary.rst:2507 +msgid "Alternative term for the Compute API." +msgstr "" + +#: ../common/glossary.rst:2494 ../common/glossary.rst:2497 +#: ../common/glossary.rst:2500 ../common/glossary.rst:2501 +#: ../common/glossary.rst:2506 ../common/glossary.rst:2508 +msgid "nova-network" +msgstr "" + +#: ../common/glossary.rst:2497 ../common/glossary.rst:2500 +#: ../common/glossary.rst:2503 ../common/glossary.rst:2504 +#: ../common/glossary.rst:2509 ../common/glossary.rst:2511 +msgid "" +"A Compute component that manages IP address allocation, firewalls, and other " +"network-related tasks. This is the legacy networking option and an " +"alternative to Networking." +msgstr "" + +#: ../common/glossary.rst:2500 ../common/glossary.rst:2503 +#: ../common/glossary.rst:2506 ../common/glossary.rst:2507 +#: ../common/glossary.rst:2512 ../common/glossary.rst:2514 +msgid "object" +msgstr "" + +#: ../common/glossary.rst:2503 ../common/glossary.rst:2506 +#: ../common/glossary.rst:2509 ../common/glossary.rst:2510 +#: ../common/glossary.rst:2515 ../common/glossary.rst:2517 +msgid "A BLOB of data held by Object Storage; can be in any format." +msgstr "" + +#: ../common/glossary.rst:2505 ../common/glossary.rst:2508 +#: ../common/glossary.rst:2511 ../common/glossary.rst:2512 +#: ../common/glossary.rst:2517 ../common/glossary.rst:2519 +msgid "object auditor" +msgstr "" + +#: ../common/glossary.rst:2508 ../common/glossary.rst:2511 +#: ../common/glossary.rst:2514 ../common/glossary.rst:2515 +#: ../common/glossary.rst:2520 ../common/glossary.rst:2522 +msgid "" +"Opens all objects for an object server and verifies the MD5 hash, size, and " +"metadata for each object." +msgstr "" + +#: ../common/glossary.rst:2510 ../common/glossary.rst:2513 +#: ../common/glossary.rst:2516 ../common/glossary.rst:2517 +#: ../common/glossary.rst:2522 ../common/glossary.rst:2524 +msgid "object expiration" +msgstr "" + +#: ../common/glossary.rst:2513 ../common/glossary.rst:2516 +#: ../common/glossary.rst:2519 ../common/glossary.rst:2520 +#: ../common/glossary.rst:2525 ../common/glossary.rst:2527 +msgid "" +"A configurable option within Object Storage to automatically delete objects " +"after a specified amount of time has passed or a certain date is reached." +msgstr "" + +#: ../common/glossary.rst:2516 ../common/glossary.rst:2519 +#: ../common/glossary.rst:2522 ../common/glossary.rst:2523 +#: ../common/glossary.rst:2528 ../common/glossary.rst:2530 +msgid "object hash" +msgstr "" + +#: ../common/glossary.rst:2519 ../common/glossary.rst:2522 +#: ../common/glossary.rst:2525 ../common/glossary.rst:2526 +#: ../common/glossary.rst:2531 ../common/glossary.rst:2533 +msgid "Uniquely ID for an Object Storage object." +msgstr "" + +#: ../common/glossary.rst:2520 ../common/glossary.rst:2523 +#: ../common/glossary.rst:2526 ../common/glossary.rst:2527 +#: ../common/glossary.rst:2532 ../common/glossary.rst:2534 +msgid "object path hash" +msgstr "" + +#: ../common/glossary.rst:2523 ../common/glossary.rst:2526 +#: ../common/glossary.rst:2529 ../common/glossary.rst:2530 +#: ../common/glossary.rst:2535 ../common/glossary.rst:2537 +msgid "" +"Used by Object Storage to determine the location of an object in the ring. " +"Maps objects to partitions." +msgstr "" + +#: ../common/glossary.rst:2525 ../common/glossary.rst:2528 +#: ../common/glossary.rst:2531 ../common/glossary.rst:2532 +#: ../common/glossary.rst:2537 ../common/glossary.rst:2539 +msgid "object replicator" +msgstr "" + +#: ../common/glossary.rst:2528 ../common/glossary.rst:2531 +#: ../common/glossary.rst:2534 ../common/glossary.rst:2535 +#: ../common/glossary.rst:2540 ../common/glossary.rst:2542 +msgid "" +"An Object Storage component that copies an object to remote partitions for " +"fault tolerance." +msgstr "" + +#: ../common/glossary.rst:2530 ../common/glossary.rst:2533 +#: ../common/glossary.rst:2536 ../common/glossary.rst:2537 +#: ../common/glossary.rst:2542 ../common/glossary.rst:2544 +msgid "object server" +msgstr "" + +#: ../common/glossary.rst:2533 ../common/glossary.rst:2536 +#: ../common/glossary.rst:2539 ../common/glossary.rst:2540 +#: ../common/glossary.rst:2545 ../common/glossary.rst:2547 +msgid "An Object Storage component that is responsible for managing objects." +msgstr "" + +#: ../common/glossary.rst:2538 ../common/glossary.rst:2541 +#: ../common/glossary.rst:2544 ../common/glossary.rst:2545 +#: ../common/glossary.rst:2550 ../common/glossary.rst:2552 +msgid "" +"The OpenStack core project that provides eventually consistent and redundant " +"storage and retrieval of fixed digital content. The project name of " +"OpenStack Object Storage is swift." +msgstr "" + +#: ../common/glossary.rst:2541 ../common/glossary.rst:2544 +#: ../common/glossary.rst:2547 ../common/glossary.rst:2548 +#: ../common/glossary.rst:2553 ../common/glossary.rst:2555 +msgid "Object Storage API" +msgstr "" + +#: ../common/glossary.rst:2544 ../common/glossary.rst:2547 +#: ../common/glossary.rst:2550 ../common/glossary.rst:2551 +#: ../common/glossary.rst:2556 ../common/glossary.rst:2558 +msgid "API used to access OpenStack Object Storage." +msgstr "" + +#: ../common/glossary.rst:2545 ../common/glossary.rst:2548 +#: ../common/glossary.rst:2551 ../common/glossary.rst:2552 +#: ../common/glossary.rst:2557 ../common/glossary.rst:2559 +msgid "Object Storage Device (OSD)" +msgstr "" + +#: ../common/glossary.rst:2548 ../common/glossary.rst:2551 +#: ../common/glossary.rst:2554 ../common/glossary.rst:2555 +#: ../common/glossary.rst:2560 ../common/glossary.rst:2562 +msgid "The Ceph storage daemon." +msgstr "" + +#: ../common/glossary.rst:2549 ../common/glossary.rst:2552 +#: ../common/glossary.rst:2555 ../common/glossary.rst:2556 +#: ../common/glossary.rst:2561 ../common/glossary.rst:2563 +msgid "object versioning" +msgstr "" + +#: ../common/glossary.rst:2552 ../common/glossary.rst:2555 +#: ../common/glossary.rst:2558 ../common/glossary.rst:2559 +#: ../common/glossary.rst:2564 ../common/glossary.rst:2566 +msgid "" +"Allows a user to set a flag on an Object Storage container so that all " +"objects within the container are versioned." +msgstr "" + +#: ../common/glossary.rst:2554 ../common/glossary.rst:2557 +#: ../common/glossary.rst:2560 ../common/glossary.rst:2561 +#: ../common/glossary.rst:2566 ../common/glossary.rst:2568 +msgid "Oldie" +msgstr "" + +#: ../common/glossary.rst:2557 ../common/glossary.rst:2560 +#: ../common/glossary.rst:2563 ../common/glossary.rst:2564 +#: ../common/glossary.rst:2569 ../common/glossary.rst:2571 +msgid "" +"Term for an Object Storage process that runs for a long time. Can indicate a " +"hung process." +msgstr "" + +#: ../common/glossary.rst:2559 ../common/glossary.rst:2562 +#: ../common/glossary.rst:2565 ../common/glossary.rst:2566 +#: ../common/glossary.rst:2571 ../common/glossary.rst:2573 +msgid "Open Cloud Computing Interface (OCCI)" +msgstr "" + +#: ../common/glossary.rst:2562 ../common/glossary.rst:2565 +#: ../common/glossary.rst:2568 ../common/glossary.rst:2569 +#: ../common/glossary.rst:2574 ../common/glossary.rst:2576 +msgid "" +"A standardized interface for managing compute, data, and network resources, " +"currently unsupported in OpenStack." +msgstr "" + +#: ../common/glossary.rst:2564 ../common/glossary.rst:2567 +#: ../common/glossary.rst:2570 ../common/glossary.rst:2571 +#: ../common/glossary.rst:2576 ../common/glossary.rst:2578 +msgid "Open Virtualization Format (OVF)" +msgstr "" + +#: ../common/glossary.rst:2567 ../common/glossary.rst:2570 +#: ../common/glossary.rst:2573 ../common/glossary.rst:2574 +#: ../common/glossary.rst:2579 ../common/glossary.rst:2581 +msgid "Standard for packaging VM images. Supported in OpenStack." +msgstr "" + +#: ../common/glossary.rst:2568 ../common/glossary.rst:2571 +#: ../common/glossary.rst:2574 ../common/glossary.rst:2575 +#: ../common/glossary.rst:2580 ../common/glossary.rst:2582 +msgid "Open vSwitch" +msgstr "" + +#: ../common/glossary.rst:2571 ../common/glossary.rst:2574 +#: ../common/glossary.rst:2577 ../common/glossary.rst:2578 +#: ../common/glossary.rst:2583 ../common/glossary.rst:2585 +msgid "" +"Open vSwitch is a production quality, multilayer virtual switch licensed " +"under the open source Apache 2.0 license. It is designed to enable massive " +"network automation through programmatic extension, while still supporting " +"standard management interfaces and protocols (for example NetFlow, sFlow, " +"SPAN, RSPAN, CLI, LACP, 802.1ag)." +msgstr "" + +#: ../common/glossary.rst:2577 ../common/glossary.rst:2580 +#: ../common/glossary.rst:2583 ../common/glossary.rst:2584 +#: ../common/glossary.rst:2589 ../common/glossary.rst:2591 +msgid "Open vSwitch (OVS) agent" +msgstr "" + +#: ../common/glossary.rst:2580 ../common/glossary.rst:2583 +#: ../common/glossary.rst:2586 ../common/glossary.rst:2587 +#: ../common/glossary.rst:2592 ../common/glossary.rst:2594 +msgid "" +"Provides an interface to the underlying Open vSwitch service for the " +"Networking plug-in." +msgstr "" + +#: ../common/glossary.rst:2582 ../common/glossary.rst:2585 +#: ../common/glossary.rst:2588 ../common/glossary.rst:2589 +#: ../common/glossary.rst:2594 ../common/glossary.rst:2596 +msgid "Open vSwitch neutron plug-in" +msgstr "" + +#: ../common/glossary.rst:2585 ../common/glossary.rst:2588 +#: ../common/glossary.rst:2591 ../common/glossary.rst:2592 +#: ../common/glossary.rst:2597 ../common/glossary.rst:2599 +msgid "Provides support for Open vSwitch in Networking." +msgstr "" + +#: ../common/glossary.rst:2586 ../common/glossary.rst:2589 +#: ../common/glossary.rst:2592 ../common/glossary.rst:2593 +#: ../common/glossary.rst:2598 ../common/glossary.rst:2600 +msgid "OpenLDAP" +msgstr "" + +#: ../common/glossary.rst:2589 ../common/glossary.rst:2592 +#: ../common/glossary.rst:2595 ../common/glossary.rst:2596 +#: ../common/glossary.rst:2601 ../common/glossary.rst:2603 +msgid "An open source LDAP server. Supported by both Compute and Identity." +msgstr "" + +#: ../common/glossary.rst:2591 ../common/glossary.rst:2594 +#: ../common/glossary.rst:2597 ../common/glossary.rst:2598 +#: ../common/glossary.rst:2603 ../common/glossary.rst:2605 +msgid "OpenStack" +msgstr "" + +#: ../common/glossary.rst:2594 ../common/glossary.rst:2597 +#: ../common/glossary.rst:2600 ../common/glossary.rst:2601 +#: ../common/glossary.rst:2606 ../common/glossary.rst:2608 +msgid "" +"OpenStack is a cloud operating system that controls large pools of compute, " +"storage, and networking resources throughout a data center, all managed " +"through a dashboard that gives administrators control while empowering their " +"users to provision resources through a web interface. OpenStack is an open " +"source project licensed under the Apache License 2.0." +msgstr "" + +#: ../common/glossary.rst:2600 ../common/glossary.rst:2603 +#: ../common/glossary.rst:2606 ../common/glossary.rst:2607 +#: ../common/glossary.rst:2612 ../common/glossary.rst:2614 +msgid "OpenStack code name" +msgstr "" + +#: ../common/glossary.rst:2603 +msgid "" +"Each OpenStack release has a code name. Code names ascend in alphabetical " +"order: Austin, Bexar, Cactus, Diablo, Essex, Folsom, Grizzly, Havana, " +"Icehouse, Juno, Kilo, and Liberty. Code names are cities or counties near " +"where the corresponding OpenStack design summit took place. An exception, " +"called the Waldon exception, is granted to elements of the state flag that " +"sound especially cool. Code names are chosen by popular vote." +msgstr "" + +#: ../common/glossary.rst:2603 +msgid "" +"Each OpenStack release has a code name. Code names ascend in alphabetical " +"order: Austin, Bexar, Cactus, Diablo, Essex, Folsom, Grizzly, Havana, " +"Icehouse, Juno, and Kilo. Code names are cities or counties near where the " +"corresponding OpenStack design summit took place. An exception, called the " +"Waldon exception, is granted to elements of the state flag that sound " +"especially cool. Code names are chosen by popular vote." +msgstr "" + +#: ../common/glossary.rst:2606 ../common/glossary.rst:2609 +#: ../common/glossary.rst:2615 ../common/glossary.rst:2617 +msgid "" +"Each OpenStack release has a code name. Code names ascend in alphabetical " +"order: Austin, Bexar, Cactus, Diablo, Essex, Folsom, Grizzly, Havana, " +"Icehouse, Juno, Kilo, Liberty, and Mitaka. Code names are cities or counties " +"near where the corresponding OpenStack design summit took place. An " +"exception, called the Waldon exception, is granted to elements of the state " +"flag that sound especially cool. Code names are chosen by popular vote." +msgstr "" + +#: ../common/glossary.rst:2610 +msgid "" +"Each OpenStack release has a code name. Code names ascend in alphabetical " +"order: Austin, Bexar, Cactus, Diablo, Essex, Folsom, Grizzly, Havana, " +"Icehouse, Juno, Kilo, Liberty, and Meiji. Code names are cities or counties " +"near where the corresponding OpenStack design summit took place. An " +"exception, called the Waldon exception, is granted to elements of the state " +"flag that sound especially cool. Code names are chosen by popular vote." +msgstr "" + +#: ../common/glossary.rst:2611 ../common/glossary.rst:2615 +#: ../common/glossary.rst:2618 ../common/glossary.rst:2624 +#: ../common/glossary.rst:2626 +msgid "openSUSE" +msgstr "" + +#: ../common/glossary.rst:2615 ../common/glossary.rst:2619 +#: ../common/glossary.rst:2622 ../common/glossary.rst:2628 +#: ../common/glossary.rst:2630 +msgid "operator" +msgstr "" + +#: ../common/glossary.rst:2618 ../common/glossary.rst:2622 +#: ../common/glossary.rst:2625 ../common/glossary.rst:2631 +#: ../common/glossary.rst:2633 +msgid "" +"The person responsible for planning and maintaining an OpenStack " +"installation." +msgstr "" + +#: ../common/glossary.rst:2623 ../common/glossary.rst:2627 +#: ../common/glossary.rst:2630 ../common/glossary.rst:2636 +#: ../common/glossary.rst:2638 +msgid "" +"An integrated project that orchestrates multiple cloud applications for " +"OpenStack. The project name of Orchestration is heat." +msgstr "" + +#: ../common/glossary.rst:2626 ../common/glossary.rst:2630 +#: ../common/glossary.rst:2633 ../common/glossary.rst:2639 +#: ../common/glossary.rst:2641 +msgid "orphan" +msgstr "" + +#: ../common/glossary.rst:2629 ../common/glossary.rst:2633 +#: ../common/glossary.rst:2636 ../common/glossary.rst:2642 +#: ../common/glossary.rst:2644 +msgid "" +"In the context of Object Storage, this is a process that is not terminated " +"after an upgrade, restart, or reload of the service." +msgstr "" + +#: ../common/glossary.rst:2631 ../common/glossary.rst:2635 +#: ../common/glossary.rst:2638 ../common/glossary.rst:2644 +#: ../common/glossary.rst:2646 +msgid "Oslo" +msgstr "" + +#: ../common/glossary.rst:2634 ../common/glossary.rst:2638 +#: ../common/glossary.rst:2641 ../common/glossary.rst:2647 +#: ../common/glossary.rst:2649 +msgid "" +"OpenStack project that produces a set of Python libraries containing code " +"shared by OpenStack projects." +msgstr "" + +#: ../common/glossary.rst:2636 ../common/glossary.rst:2640 +#: ../common/glossary.rst:2643 ../common/glossary.rst:2649 +#: ../common/glossary.rst:2651 +msgid "parent cell" +msgstr "" + +#: ../common/glossary.rst:2639 ../common/glossary.rst:2643 +#: ../common/glossary.rst:2646 ../common/glossary.rst:2652 +#: ../common/glossary.rst:2654 +msgid "" +"If a requested resource, such as CPU time, disk storage, or memory, is not " +"available in the parent cell, the request is forwarded to associated child " +"cells." +msgstr "" + +#: ../common/glossary.rst:2642 ../common/glossary.rst:2646 +#: ../common/glossary.rst:2649 ../common/glossary.rst:2655 +#: ../common/glossary.rst:2657 +msgid "partition" +msgstr "" + +#: ../common/glossary.rst:2645 ../common/glossary.rst:2649 +#: ../common/glossary.rst:2652 ../common/glossary.rst:2658 +#: ../common/glossary.rst:2660 +msgid "" +"A unit of storage within Object Storage used to store objects. It exists on " +"top of devices and is replicated for fault tolerance." +msgstr "" + +#: ../common/glossary.rst:2648 ../common/glossary.rst:2652 +#: ../common/glossary.rst:2655 ../common/glossary.rst:2661 +#: ../common/glossary.rst:2663 +msgid "partition index" +msgstr "" + +#: ../common/glossary.rst:2651 ../common/glossary.rst:2655 +#: ../common/glossary.rst:2658 ../common/glossary.rst:2664 +#: ../common/glossary.rst:2666 +msgid "" +"Contains the locations of all Object Storage partitions within the ring." +msgstr "" + +#: ../common/glossary.rst:2653 ../common/glossary.rst:2657 +#: ../common/glossary.rst:2660 ../common/glossary.rst:2666 +#: ../common/glossary.rst:2668 +msgid "partition shift value" +msgstr "" + +#: ../common/glossary.rst:2656 ../common/glossary.rst:2660 +#: ../common/glossary.rst:2663 ../common/glossary.rst:2669 +#: ../common/glossary.rst:2671 +msgid "" +"Used by Object Storage to determine which partition data should reside on." +msgstr "" + +#: ../common/glossary.rst:2658 ../common/glossary.rst:2662 +#: ../common/glossary.rst:2665 ../common/glossary.rst:2671 +#: ../common/glossary.rst:2673 +msgid "path MTU discovery (PMTUD)" +msgstr "" + +#: ../common/glossary.rst:2661 ../common/glossary.rst:2665 +#: ../common/glossary.rst:2668 ../common/glossary.rst:2674 +#: ../common/glossary.rst:2676 +msgid "" +"Mechanism in IP networks to detect end-to-end MTU and adjust packet size " +"accordingly." +msgstr "" + +#: ../common/glossary.rst:2663 ../common/glossary.rst:2667 +#: ../common/glossary.rst:2670 ../common/glossary.rst:2676 +#: ../common/glossary.rst:2678 +msgid "pause" +msgstr "" + +#: ../common/glossary.rst:2666 ../common/glossary.rst:2670 +#: ../common/glossary.rst:2673 ../common/glossary.rst:2679 +#: ../common/glossary.rst:2681 +msgid "" +"A VM state where no changes occur (no changes in memory, network " +"communications stop, etc); the VM is frozen but not shut down." +msgstr "" + +#: ../common/glossary.rst:2668 ../common/glossary.rst:2672 +#: ../common/glossary.rst:2675 ../common/glossary.rst:2681 +#: ../common/glossary.rst:2683 +msgid "PCI passthrough" +msgstr "" + +#: ../common/glossary.rst:2671 ../common/glossary.rst:2675 +#: ../common/glossary.rst:2678 ../common/glossary.rst:2684 +#: ../common/glossary.rst:2686 +msgid "" +"Gives guest VMs exclusive access to a PCI device. Currently supported in " +"OpenStack Havana and later releases." +msgstr "" + +#: ../common/glossary.rst:2673 ../common/glossary.rst:2677 +#: ../common/glossary.rst:2680 ../common/glossary.rst:2686 +#: ../common/glossary.rst:2688 +msgid "persistent message" +msgstr "" + +#: ../common/glossary.rst:2676 ../common/glossary.rst:2680 +#: ../common/glossary.rst:2683 ../common/glossary.rst:2689 +#: ../common/glossary.rst:2691 +msgid "" +"A message that is stored both in memory and on disk. The message is not lost " +"after a failure or restart." +msgstr "" + +#: ../common/glossary.rst:2678 ../common/glossary.rst:2682 +#: ../common/glossary.rst:2685 ../common/glossary.rst:2691 +#: ../common/glossary.rst:2693 +msgid "persistent volume" +msgstr "" + +#: ../common/glossary.rst:2681 ../common/glossary.rst:2685 +#: ../common/glossary.rst:2688 ../common/glossary.rst:2694 +#: ../common/glossary.rst:2696 +msgid "Changes to these types of disk volumes are saved." +msgstr "" + +#: ../common/glossary.rst:2682 ../common/glossary.rst:2686 +#: ../common/glossary.rst:2689 ../common/glossary.rst:2695 +#: ../common/glossary.rst:2697 +msgid "personality file" +msgstr "" + +#: ../common/glossary.rst:2685 ../common/glossary.rst:2689 +#: ../common/glossary.rst:2692 ../common/glossary.rst:2698 +#: ../common/glossary.rst:2700 +msgid "" +"A file used to customize a Compute instance. It can be used to inject SSH " +"keys or a specific network configuration." +msgstr "" + +#: ../common/glossary.rst:2687 ../common/glossary.rst:2691 +#: ../common/glossary.rst:2694 ../common/glossary.rst:2700 +#: ../common/glossary.rst:2702 +msgid "Platform-as-a-Service (PaaS)" +msgstr "" + +#: ../common/glossary.rst:2690 ../common/glossary.rst:2694 +#: ../common/glossary.rst:2697 ../common/glossary.rst:2703 +#: ../common/glossary.rst:2705 +msgid "" +"Provides to the consumer the ability to deploy applications through a " +"programming language or tools supported by the cloud platform provider. An " +"example of Platform-as-a-Service is an Eclipse/Java programming platform " +"provided with no downloads required." +msgstr "" + +#: ../common/glossary.rst:2695 ../common/glossary.rst:2699 +#: ../common/glossary.rst:2702 ../common/glossary.rst:2708 +#: ../common/glossary.rst:2710 +msgid "plug-in" +msgstr "" + +#: ../common/glossary.rst:2698 ../common/glossary.rst:2702 +#: ../common/glossary.rst:2705 ../common/glossary.rst:2711 +#: ../common/glossary.rst:2713 +msgid "" +"Software component providing the actual implementation for Networking APIs, " +"or for Compute APIs, depending on the context." +msgstr "" + +#: ../common/glossary.rst:2700 ../common/glossary.rst:2704 +#: ../common/glossary.rst:2707 ../common/glossary.rst:2713 +#: ../common/glossary.rst:2715 +msgid "policy service" +msgstr "" + +#: ../common/glossary.rst:2703 ../common/glossary.rst:2707 +#: ../common/glossary.rst:2710 ../common/glossary.rst:2716 +#: ../common/glossary.rst:2718 +msgid "" +"Component of Identity that provides a rule-management interface and a rule-" +"based authorization engine." +msgstr "" + +#: ../common/glossary.rst:2705 ../common/glossary.rst:2709 +#: ../common/glossary.rst:2712 ../common/glossary.rst:2718 +#: ../common/glossary.rst:2720 +msgid "pool" +msgstr "" + +#: ../common/glossary.rst:2708 ../common/glossary.rst:2712 +#: ../common/glossary.rst:2715 ../common/glossary.rst:2721 +#: ../common/glossary.rst:2723 +msgid "" +"A logical set of devices, such as web servers, that you group together to " +"receive and process traffic. The load balancing function chooses which " +"member of the pool handles the new requests or connections received on the " +"VIP address. Each VIP has one pool." +msgstr "" + +#: ../common/glossary.rst:2713 ../common/glossary.rst:2717 +#: ../common/glossary.rst:2720 ../common/glossary.rst:2726 +#: ../common/glossary.rst:2728 +msgid "pool member" +msgstr "" + +#: ../common/glossary.rst:2716 ../common/glossary.rst:2720 +#: ../common/glossary.rst:2723 ../common/glossary.rst:2729 +#: ../common/glossary.rst:2731 +msgid "" +"An application that runs on the back-end server in a load-balancing system." +msgstr "" + +#: ../common/glossary.rst:2718 ../common/glossary.rst:2722 +#: ../common/glossary.rst:2725 ../common/glossary.rst:2731 +#: ../common/glossary.rst:2733 +msgid "port" +msgstr "" + +#: ../common/glossary.rst:2721 ../common/glossary.rst:2725 +#: ../common/glossary.rst:2728 ../common/glossary.rst:2734 +#: ../common/glossary.rst:2736 +msgid "" +"A virtual network port within Networking; VIFs / vNICs are connected to a " +"port." +msgstr "" + +#: ../common/glossary.rst:2723 ../common/glossary.rst:2727 +#: ../common/glossary.rst:2730 ../common/glossary.rst:2736 +#: ../common/glossary.rst:2738 +msgid "port UUID" +msgstr "" + +#: ../common/glossary.rst:2726 ../common/glossary.rst:2730 +#: ../common/glossary.rst:2733 ../common/glossary.rst:2739 +#: ../common/glossary.rst:2741 +msgid "Unique ID for a Networking port." +msgstr "" + +#: ../common/glossary.rst:2727 ../common/glossary.rst:2731 +#: ../common/glossary.rst:2734 ../common/glossary.rst:2740 +#: ../common/glossary.rst:2742 +msgid "preseed" +msgstr "" + +#: ../common/glossary.rst:2730 ../common/glossary.rst:2734 +#: ../common/glossary.rst:2737 ../common/glossary.rst:2743 +#: ../common/glossary.rst:2745 +msgid "" +"A tool to automate system configuration and installation on Debian-based " +"Linux distributions." +msgstr "" + +#: ../common/glossary.rst:2732 ../common/glossary.rst:2736 +#: ../common/glossary.rst:2739 ../common/glossary.rst:2745 +#: ../common/glossary.rst:2747 +msgid "private image" +msgstr "" + +#: ../common/glossary.rst:2735 ../common/glossary.rst:2739 +#: ../common/glossary.rst:2742 ../common/glossary.rst:2748 +#: ../common/glossary.rst:2750 +msgid "An Image service VM image that is only available to specified tenants." +msgstr "" + +#: ../common/glossary.rst:2737 ../common/glossary.rst:2741 +#: ../common/glossary.rst:2744 ../common/glossary.rst:2750 +#: ../common/glossary.rst:2752 +msgid "private IP address" +msgstr "" + +#: ../common/glossary.rst:2740 ../common/glossary.rst:2744 +#: ../common/glossary.rst:2747 ../common/glossary.rst:2753 +#: ../common/glossary.rst:2755 +msgid "" +"An IP address used for management and administration, not available to the " +"public Internet." +msgstr "" + +#: ../common/glossary.rst:2742 ../common/glossary.rst:2746 +#: ../common/glossary.rst:2749 ../common/glossary.rst:2755 +#: ../common/glossary.rst:2757 +msgid "private network" +msgstr "" + +#: ../common/glossary.rst:2745 ../common/glossary.rst:2749 +#: ../common/glossary.rst:2752 ../common/glossary.rst:2758 +#: ../common/glossary.rst:2760 +msgid "" +"The Network Controller provides virtual networks to enable compute servers " +"to interact with each other and with the public network. All machines must " +"have a public and private network interface. A private network interface can " +"be a flat or VLAN network interface. A flat network interface is controlled " +"by the flat_interface with flat managers. A VLAN network interface is " +"controlled by the `vlan_interface` option with VLAN managers." +msgstr "" + +#: ../common/glossary.rst:2753 ../common/glossary.rst:2757 +#: ../common/glossary.rst:2760 ../common/glossary.rst:2766 +#: ../common/glossary.rst:2768 +msgid "project" +msgstr "" + +#: ../common/glossary.rst:2756 ../common/glossary.rst:2763 +msgid "" +"A logical grouping of users within Compute; defines quotas and access to VM " +"images." +msgstr "" + +#: ../common/glossary.rst:2758 ../common/glossary.rst:2763 +#: ../common/glossary.rst:2765 ../common/glossary.rst:2772 +#: ../common/glossary.rst:2774 +msgid "project ID" +msgstr "" + +#: ../common/glossary.rst:2760 ../common/glossary.rst:2769 +#: ../common/glossary.rst:2771 +msgid "" +"Projects represent the base unit of “ownership” in OpenStack, in that all " +"resources in OpenStack should be owned by a specific project. In OpenStack " +"Identity, a project must be owned by a specific domain." +msgstr "" + +#: ../common/glossary.rst:2761 ../common/glossary.rst:2766 +#: ../common/glossary.rst:2768 ../common/glossary.rst:2775 +#: ../common/glossary.rst:2777 +msgid "User-defined alphanumeric string in Compute; the name of a project." +msgstr "" + +#: ../common/glossary.rst:2763 ../common/glossary.rst:2768 +#: ../common/glossary.rst:2770 ../common/glossary.rst:2777 +#: ../common/glossary.rst:2779 +msgid "project VPN" +msgstr "" + +#: ../common/glossary.rst:2766 ../common/glossary.rst:2771 +#: ../common/glossary.rst:2773 ../common/glossary.rst:2780 +#: ../common/glossary.rst:2782 +msgid "Alternative term for a cloudpipe." +msgstr "" + +#: ../common/glossary.rst:2767 ../common/glossary.rst:2772 +#: ../common/glossary.rst:2774 ../common/glossary.rst:2781 +#: ../common/glossary.rst:2783 +msgid "promiscuous mode" +msgstr "" + +#: ../common/glossary.rst:2770 ../common/glossary.rst:2775 +#: ../common/glossary.rst:2777 ../common/glossary.rst:2784 +#: ../common/glossary.rst:2786 +msgid "" +"Causes the network interface to pass all traffic it receives to the host " +"rather than passing only the frames addressed to it." +msgstr "" + +#: ../common/glossary.rst:2773 ../common/glossary.rst:2778 +#: ../common/glossary.rst:2780 ../common/glossary.rst:2787 +#: ../common/glossary.rst:2789 +msgid "protected property" +msgstr "" + +#: ../common/glossary.rst:2776 ../common/glossary.rst:2781 +#: ../common/glossary.rst:2783 ../common/glossary.rst:2790 +#: ../common/glossary.rst:2792 +msgid "" +"Generally, extra properties on an Image service image to which only cloud " +"administrators have access. Limits which user roles can perform CRUD " +"operations on that property. The cloud administrator can configure any image " +"property as protected." +msgstr "" + +#: ../common/glossary.rst:2781 ../common/glossary.rst:2786 +#: ../common/glossary.rst:2788 ../common/glossary.rst:2795 +#: ../common/glossary.rst:2797 +msgid "provider" +msgstr "" + +#: ../common/glossary.rst:2784 ../common/glossary.rst:2789 +#: ../common/glossary.rst:2791 ../common/glossary.rst:2798 +#: ../common/glossary.rst:2800 +msgid "An administrator who has access to all hosts and instances." +msgstr "" + +#: ../common/glossary.rst:2786 ../common/glossary.rst:2791 +#: ../common/glossary.rst:2793 ../common/glossary.rst:2800 +#: ../common/glossary.rst:2802 +msgid "proxy node" +msgstr "" + +#: ../common/glossary.rst:2789 ../common/glossary.rst:2794 +#: ../common/glossary.rst:2796 ../common/glossary.rst:2803 +#: ../common/glossary.rst:2805 +msgid "A node that provides the Object Storage proxy service." +msgstr "" + +#: ../common/glossary.rst:2790 ../common/glossary.rst:2795 +#: ../common/glossary.rst:2797 ../common/glossary.rst:2804 +#: ../common/glossary.rst:2806 +msgid "proxy server" +msgstr "" + +#: ../common/glossary.rst:2793 ../common/glossary.rst:2798 +#: ../common/glossary.rst:2800 ../common/glossary.rst:2807 +#: ../common/glossary.rst:2809 +msgid "" +"Users of Object Storage interact with the service through the proxy server, " +"which in turn looks up the location of the requested data within the ring " +"and returns the results to the user." +msgstr "" + +#: ../common/glossary.rst:2796 ../common/glossary.rst:2801 +#: ../common/glossary.rst:2803 ../common/glossary.rst:2810 +#: ../common/glossary.rst:2812 +msgid "public API" +msgstr "" + +#: ../common/glossary.rst:2799 ../common/glossary.rst:2804 +#: ../common/glossary.rst:2806 ../common/glossary.rst:2813 +#: ../common/glossary.rst:2815 +msgid "" +"An API endpoint used for both service-to-service communication and end-user " +"interactions." +msgstr "" + +#: ../common/glossary.rst:2801 ../common/glossary.rst:2806 +#: ../common/glossary.rst:2808 ../common/glossary.rst:2815 +#: ../common/glossary.rst:2817 +msgid "public image" +msgstr "" + +#: ../common/glossary.rst:2804 ../common/glossary.rst:2809 +#: ../common/glossary.rst:2811 ../common/glossary.rst:2818 +#: ../common/glossary.rst:2820 +msgid "An Image service VM image that is available to all tenants." +msgstr "" + +#: ../common/glossary.rst:2806 ../common/glossary.rst:2811 +#: ../common/glossary.rst:2813 ../common/glossary.rst:2820 +#: ../common/glossary.rst:2822 +msgid "public IP address" +msgstr "" + +#: ../common/glossary.rst:2809 ../common/glossary.rst:2814 +#: ../common/glossary.rst:2816 ../common/glossary.rst:2823 +#: ../common/glossary.rst:2825 +msgid "An IP address that is accessible to end-users." +msgstr "" + +#: ../common/glossary.rst:2810 ../common/glossary.rst:2815 +#: ../common/glossary.rst:2817 ../common/glossary.rst:2824 +#: ../common/glossary.rst:2826 +msgid "public key authentication" +msgstr "" + +#: ../common/glossary.rst:2813 ../common/glossary.rst:2818 +#: ../common/glossary.rst:2820 ../common/glossary.rst:2827 +#: ../common/glossary.rst:2829 +msgid "Authentication method that uses keys rather than passwords." +msgstr "" + +#: ../common/glossary.rst:2815 ../common/glossary.rst:2820 +#: ../common/glossary.rst:2822 ../common/glossary.rst:2829 +#: ../common/glossary.rst:2831 +msgid "public network" +msgstr "" + +#: ../common/glossary.rst:2818 ../common/glossary.rst:2823 +#: ../common/glossary.rst:2825 ../common/glossary.rst:2832 +#: ../common/glossary.rst:2834 +msgid "" +"The Network Controller provides virtual networks to enable compute servers " +"to interact with each other and with the public network. All machines must " +"have a public and private network interface. The public network interface is " +"controlled by the `public_interface` option." +msgstr "" + +#: ../common/glossary.rst:2823 ../common/glossary.rst:2828 +#: ../common/glossary.rst:2830 ../common/glossary.rst:2837 +#: ../common/glossary.rst:2839 +msgid "Puppet" +msgstr "" + +#: ../common/glossary.rst:2826 ../common/glossary.rst:2831 +#: ../common/glossary.rst:2833 ../common/glossary.rst:2840 +#: ../common/glossary.rst:2842 +msgid "" +"An operating system configuration-management tool supported by OpenStack." +msgstr "" + +#: ../common/glossary.rst:2828 ../common/glossary.rst:2833 +#: ../common/glossary.rst:2835 ../common/glossary.rst:2842 +#: ../common/glossary.rst:2844 +msgid "Python" +msgstr "" + +#: ../common/glossary.rst:2831 ../common/glossary.rst:2836 +#: ../common/glossary.rst:2838 ../common/glossary.rst:2845 +#: ../common/glossary.rst:2847 +msgid "Programming language used extensively in OpenStack." +msgstr "" + +#: ../common/glossary.rst:2832 ../common/glossary.rst:2837 +#: ../common/glossary.rst:2839 ../common/glossary.rst:2846 +#: ../common/glossary.rst:2848 +msgid "QEMU Copy On Write 2 (QCOW2)" +msgstr "" + +#: ../common/glossary.rst:2837 ../common/glossary.rst:2842 +#: ../common/glossary.rst:2844 ../common/glossary.rst:2851 +#: ../common/glossary.rst:2853 +msgid "Qpid" +msgstr "" + +#: ../common/glossary.rst:2840 ../common/glossary.rst:2845 +#: ../common/glossary.rst:2847 ../common/glossary.rst:2854 +#: ../common/glossary.rst:2856 +msgid "" +"Message queue software supported by OpenStack; an alternative to RabbitMQ." +msgstr "" + +#: ../common/glossary.rst:2842 ../common/glossary.rst:2847 +#: ../common/glossary.rst:2849 ../common/glossary.rst:2856 +#: ../common/glossary.rst:2858 +msgid "quarantine" +msgstr "" + +#: ../common/glossary.rst:2845 ../common/glossary.rst:2850 +#: ../common/glossary.rst:2852 ../common/glossary.rst:2859 +#: ../common/glossary.rst:2861 +msgid "" +"If Object Storage finds objects, containers, or accounts that are corrupt, " +"they are placed in this state, are not replicated, cannot be read by " +"clients, and a correct copy is re-replicated." +msgstr "" + +#: ../common/glossary.rst:2848 ../common/glossary.rst:2853 +#: ../common/glossary.rst:2855 ../common/glossary.rst:2862 +#: ../common/glossary.rst:2864 +msgid "Quick EMUlator (QEMU)" +msgstr "" + +#: ../common/glossary.rst:2851 ../common/glossary.rst:2856 +#: ../common/glossary.rst:2858 ../common/glossary.rst:2865 +#: ../common/glossary.rst:2867 +msgid "" +"QEMU is a generic and open source machine emulator and virtualizer. One of " +"the hypervisors supported by OpenStack, generally used for development " +"purposes." +msgstr "" + +#: ../common/glossary.rst:2855 ../common/glossary.rst:2860 +#: ../common/glossary.rst:2862 ../common/glossary.rst:2869 +#: ../common/glossary.rst:2871 +msgid "quota" +msgstr "" + +#: ../common/glossary.rst:2858 ../common/glossary.rst:2863 +#: ../common/glossary.rst:2865 ../common/glossary.rst:2872 +#: ../common/glossary.rst:2874 +msgid "" +"In Compute and Block Storage, the ability to set resource limits on a per-" +"project basis." +msgstr "" + +#: ../common/glossary.rst:2860 ../common/glossary.rst:2865 +#: ../common/glossary.rst:2867 ../common/glossary.rst:2874 +#: ../common/glossary.rst:2876 +msgid "RabbitMQ" +msgstr "" + +#: ../common/glossary.rst:2863 ../common/glossary.rst:2868 +#: ../common/glossary.rst:2870 ../common/glossary.rst:2877 +#: ../common/glossary.rst:2879 +msgid "The default message queue software used by OpenStack." +msgstr "" + +#: ../common/glossary.rst:2864 ../common/glossary.rst:2869 +#: ../common/glossary.rst:2871 ../common/glossary.rst:2878 +#: ../common/glossary.rst:2880 +msgid "Rackspace Cloud Files" +msgstr "" + +#: ../common/glossary.rst:2867 ../common/glossary.rst:2872 +#: ../common/glossary.rst:2874 ../common/glossary.rst:2881 +#: ../common/glossary.rst:2883 +msgid "" +"Released as open source by Rackspace in 2010; the basis for Object Storage." +msgstr "" + +#: ../common/glossary.rst:2869 ../common/glossary.rst:2874 +#: ../common/glossary.rst:2876 ../common/glossary.rst:2883 +#: ../common/glossary.rst:2885 +msgid "RADOS Block Device (RBD)" +msgstr "" + +#: ../common/glossary.rst:2872 ../common/glossary.rst:2877 +#: ../common/glossary.rst:2879 ../common/glossary.rst:2886 +#: ../common/glossary.rst:2888 +msgid "" +"Ceph component that enables a Linux block device to be striped over multiple " +"distributed data stores." +msgstr "" + +#: ../common/glossary.rst:2874 ../common/glossary.rst:2879 +#: ../common/glossary.rst:2881 ../common/glossary.rst:2888 +#: ../common/glossary.rst:2890 +msgid "radvd" +msgstr "" + +#: ../common/glossary.rst:2877 ../common/glossary.rst:2882 +#: ../common/glossary.rst:2884 ../common/glossary.rst:2891 +#: ../common/glossary.rst:2893 +msgid "" +"The router advertisement daemon, used by the Compute VLAN manager and " +"FlatDHCP manager to provide routing services for VM instances." +msgstr "" + +#: ../common/glossary.rst:2880 ../common/glossary.rst:2885 +#: ../common/glossary.rst:2887 ../common/glossary.rst:2894 +#: ../common/glossary.rst:2896 +msgid "rally" +msgstr "" + +#: ../common/glossary.rst:2883 ../common/glossary.rst:2888 +#: ../common/glossary.rst:2890 ../common/glossary.rst:2897 +#: ../common/glossary.rst:2899 +msgid "OpenStack project that provides the Benchmark service." +msgstr "" + +#: ../common/glossary.rst:2884 ../common/glossary.rst:2889 +#: ../common/glossary.rst:2891 ../common/glossary.rst:2898 +#: ../common/glossary.rst:2900 +msgid "RAM filter" +msgstr "" + +#: ../common/glossary.rst:2887 ../common/glossary.rst:2892 +#: ../common/glossary.rst:2894 ../common/glossary.rst:2901 +#: ../common/glossary.rst:2903 +msgid "The Compute setting that enables or disables RAM overcommitment." +msgstr "" + +#: ../common/glossary.rst:2889 ../common/glossary.rst:2894 +#: ../common/glossary.rst:2896 ../common/glossary.rst:2903 +#: ../common/glossary.rst:2905 +msgid "RAM overcommit" +msgstr "" + +#: ../common/glossary.rst:2892 ../common/glossary.rst:2897 +#: ../common/glossary.rst:2899 ../common/glossary.rst:2906 +#: ../common/glossary.rst:2908 +msgid "" +"The ability to start new VM instances based on the actual memory usage of a " +"host, as opposed to basing the decision on the amount of RAM each running " +"instance thinks it has available. Also known as memory overcommit." +msgstr "" + +#: ../common/glossary.rst:2896 ../common/glossary.rst:2901 +#: ../common/glossary.rst:2903 ../common/glossary.rst:2910 +#: ../common/glossary.rst:2912 +msgid "rate limit" +msgstr "" + +#: ../common/glossary.rst:2899 ../common/glossary.rst:2904 +#: ../common/glossary.rst:2906 ../common/glossary.rst:2913 +#: ../common/glossary.rst:2915 +msgid "" +"Configurable option within Object Storage to limit database writes on a per-" +"account and/or per-container basis." +msgstr "" + +#: ../common/glossary.rst:2901 ../common/glossary.rst:2906 +#: ../common/glossary.rst:2908 ../common/glossary.rst:2915 +#: ../common/glossary.rst:2917 +msgid "raw" +msgstr "" + +#: ../common/glossary.rst:2904 ../common/glossary.rst:2909 +#: ../common/glossary.rst:2911 ../common/glossary.rst:2918 +#: ../common/glossary.rst:2920 +msgid "" +"One of the VM image disk formats supported by Image service; an unstructured " +"disk image." +msgstr "" + +#: ../common/glossary.rst:2906 ../common/glossary.rst:2911 +#: ../common/glossary.rst:2913 ../common/glossary.rst:2920 +#: ../common/glossary.rst:2922 +msgid "rebalance" +msgstr "" + +#: ../common/glossary.rst:2909 ../common/glossary.rst:2914 +#: ../common/glossary.rst:2916 ../common/glossary.rst:2923 +#: ../common/glossary.rst:2925 +msgid "" +"The process of distributing Object Storage partitions across all drives in " +"the ring; used during initial ring creation and after ring reconfiguration." +msgstr "" + +#: ../common/glossary.rst:2912 ../common/glossary.rst:2917 +#: ../common/glossary.rst:2919 ../common/glossary.rst:2926 +#: ../common/glossary.rst:2928 +msgid "reboot" +msgstr "" + +#: ../common/glossary.rst:2915 ../common/glossary.rst:2920 +#: ../common/glossary.rst:2922 ../common/glossary.rst:2929 +#: ../common/glossary.rst:2931 +msgid "" +"Either a soft or hard reboot of a server. With a soft reboot, the operating " +"system is signaled to restart, which enables a graceful shutdown of all " +"processes. A hard reboot is the equivalent of power cycling the server. The " +"virtualization platform should ensure that the reboot action has completed " +"successfully, even in cases in which the underlying domain/VM is paused or " +"halted/stopped." +msgstr "" + +#: ../common/glossary.rst:2921 ../common/glossary.rst:2926 +#: ../common/glossary.rst:2928 ../common/glossary.rst:2935 +#: ../common/glossary.rst:2937 +msgid "rebuild" +msgstr "" + +#: ../common/glossary.rst:2924 ../common/glossary.rst:2929 +#: ../common/glossary.rst:2931 ../common/glossary.rst:2938 +#: ../common/glossary.rst:2940 +msgid "" +"Removes all data on the server and replaces it with the specified image. " +"Server ID and IP addresses remain the same." +msgstr "" + +#: ../common/glossary.rst:2926 ../common/glossary.rst:2931 +#: ../common/glossary.rst:2933 ../common/glossary.rst:2940 +#: ../common/glossary.rst:2942 +msgid "Recon" +msgstr "" + +#: ../common/glossary.rst:2929 ../common/glossary.rst:2934 +#: ../common/glossary.rst:2936 ../common/glossary.rst:2943 +#: ../common/glossary.rst:2945 +msgid "An Object Storage component that collects meters." +msgstr "" + +#: ../common/glossary.rst:2930 ../common/glossary.rst:2935 +#: ../common/glossary.rst:2937 ../common/glossary.rst:2944 +#: ../common/glossary.rst:2946 +msgid "record" +msgstr "" + +#: ../common/glossary.rst:2933 ../common/glossary.rst:2938 +#: ../common/glossary.rst:2940 ../common/glossary.rst:2947 +#: ../common/glossary.rst:2949 +msgid "" +"Belongs to a particular domain and is used to specify information about the " +"domain. There are several types of DNS records. Each record type contains " +"particular information used to describe the purpose of that record. Examples " +"include mail exchange (MX) records, which specify the mail server for a " +"particular domain; and name server (NS) records, which specify the " +"authoritative name servers for a domain." +msgstr "" + +#: ../common/glossary.rst:2940 ../common/glossary.rst:2945 +#: ../common/glossary.rst:2947 ../common/glossary.rst:2954 +#: ../common/glossary.rst:2956 +msgid "record ID" +msgstr "" + +#: ../common/glossary.rst:2943 ../common/glossary.rst:2948 +#: ../common/glossary.rst:2950 ../common/glossary.rst:2957 +#: ../common/glossary.rst:2959 +msgid "" +"A number within a database that is incremented each time a change is made. " +"Used by Object Storage when replicating." +msgstr "" + +#: ../common/glossary.rst:2945 ../common/glossary.rst:2950 +#: ../common/glossary.rst:2952 ../common/glossary.rst:2959 +#: ../common/glossary.rst:2961 +msgid "Red Hat Enterprise Linux (RHEL)" +msgstr "" + +#: ../common/glossary.rst:2949 ../common/glossary.rst:2954 +#: ../common/glossary.rst:2956 ../common/glossary.rst:2963 +#: ../common/glossary.rst:2965 +msgid "reference architecture" +msgstr "" + +#: ../common/glossary.rst:2952 ../common/glossary.rst:2957 +#: ../common/glossary.rst:2959 ../common/glossary.rst:2966 +#: ../common/glossary.rst:2968 +msgid "A recommended architecture for an OpenStack cloud." +msgstr "" + +#: ../common/glossary.rst:2953 ../common/glossary.rst:2958 +#: ../common/glossary.rst:2960 ../common/glossary.rst:2967 +#: ../common/glossary.rst:2969 +msgid "region" +msgstr "" + +#: ../common/glossary.rst:2956 ../common/glossary.rst:2961 +#: ../common/glossary.rst:2963 ../common/glossary.rst:2970 +#: ../common/glossary.rst:2972 +msgid "" +"A discrete OpenStack environment with dedicated API endpoints that typically " +"shares only the Identity (keystone) with other regions." +msgstr "" + +#: ../common/glossary.rst:2959 ../common/glossary.rst:2964 +#: ../common/glossary.rst:2966 ../common/glossary.rst:2973 +#: ../common/glossary.rst:2975 +msgid "registry" +msgstr "" + +#: ../common/glossary.rst:2962 ../common/glossary.rst:2967 +#: ../common/glossary.rst:2969 ../common/glossary.rst:2976 +#: ../common/glossary.rst:2978 +msgid "Alternative term for the Image service registry." +msgstr "" + +#: ../common/glossary.rst:2963 ../common/glossary.rst:2968 +#: ../common/glossary.rst:2970 ../common/glossary.rst:2977 +#: ../common/glossary.rst:2979 +msgid "registry server" +msgstr "" + +#: ../common/glossary.rst:2966 ../common/glossary.rst:2971 +#: ../common/glossary.rst:2973 ../common/glossary.rst:2980 +#: ../common/glossary.rst:2982 +msgid "" +"An Image service that provides VM image metadata information to clients." +msgstr "" + +#: ../common/glossary.rst:2968 ../common/glossary.rst:2973 +#: ../common/glossary.rst:2975 ../common/glossary.rst:2982 +#: ../common/glossary.rst:2984 +msgid "Reliable, Autonomic Distributed Object Store" +msgstr "" + +#: ../common/glossary.rst:2970 ../common/glossary.rst:2975 +#: ../common/glossary.rst:2977 ../common/glossary.rst:2984 +#: ../common/glossary.rst:2986 +msgid "(RADOS)" +msgstr "" + +#: ../common/glossary.rst:2972 ../common/glossary.rst:2977 +#: ../common/glossary.rst:2979 ../common/glossary.rst:2986 +#: ../common/glossary.rst:2988 +msgid "" +"A collection of components that provides object storage within Ceph. Similar " +"to OpenStack Object Storage." +msgstr "" + +#: ../common/glossary.rst:2974 ../common/glossary.rst:2979 +#: ../common/glossary.rst:2981 ../common/glossary.rst:2988 +#: ../common/glossary.rst:2990 +msgid "Remote Procedure Call (RPC)" +msgstr "" + +#: ../common/glossary.rst:2977 ../common/glossary.rst:2982 +#: ../common/glossary.rst:2984 ../common/glossary.rst:2991 +#: ../common/glossary.rst:2993 +msgid "" +"The method used by the Compute RabbitMQ for intra-service communications." +msgstr "" + +#: ../common/glossary.rst:2979 ../common/glossary.rst:2984 +#: ../common/glossary.rst:2986 ../common/glossary.rst:2993 +#: ../common/glossary.rst:2995 +msgid "replica" +msgstr "" + +#: ../common/glossary.rst:2982 ../common/glossary.rst:2987 +#: ../common/glossary.rst:2989 ../common/glossary.rst:2996 +#: ../common/glossary.rst:2998 +msgid "" +"Provides data redundancy and fault tolerance by creating copies of Object " +"Storage objects, accounts, and containers so that they are not lost when the " +"underlying storage fails." +msgstr "" + +#: ../common/glossary.rst:2985 ../common/glossary.rst:2990 +#: ../common/glossary.rst:2992 ../common/glossary.rst:2999 +#: ../common/glossary.rst:3001 +msgid "replica count" +msgstr "" + +#: ../common/glossary.rst:2988 ../common/glossary.rst:2993 +#: ../common/glossary.rst:2995 ../common/glossary.rst:3002 +#: ../common/glossary.rst:3004 +msgid "The number of replicas of the data in an Object Storage ring." +msgstr "" + +#: ../common/glossary.rst:2990 ../common/glossary.rst:2995 +#: ../common/glossary.rst:2997 ../common/glossary.rst:3004 +#: ../common/glossary.rst:3006 +msgid "replication" +msgstr "" + +#: ../common/glossary.rst:2993 ../common/glossary.rst:2998 +#: ../common/glossary.rst:3000 ../common/glossary.rst:3007 +#: ../common/glossary.rst:3009 +msgid "" +"The process of copying data to a separate physical device for fault " +"tolerance and performance." +msgstr "" + +#: ../common/glossary.rst:2995 ../common/glossary.rst:3000 +#: ../common/glossary.rst:3002 ../common/glossary.rst:3009 +#: ../common/glossary.rst:3011 +msgid "replicator" +msgstr "" + +#: ../common/glossary.rst:2998 ../common/glossary.rst:3003 +#: ../common/glossary.rst:3005 ../common/glossary.rst:3012 +#: ../common/glossary.rst:3014 +msgid "" +"The Object Storage back-end process that creates and manages object replicas." +msgstr "" + +#: ../common/glossary.rst:3000 ../common/glossary.rst:3005 +#: ../common/glossary.rst:3007 ../common/glossary.rst:3014 +#: ../common/glossary.rst:3016 +msgid "request ID" +msgstr "" + +#: ../common/glossary.rst:3003 ../common/glossary.rst:3008 +#: ../common/glossary.rst:3010 ../common/glossary.rst:3017 +#: ../common/glossary.rst:3019 +msgid "Unique ID assigned to each request sent to Compute." +msgstr "" + +#: ../common/glossary.rst:3004 ../common/glossary.rst:3009 +#: ../common/glossary.rst:3011 ../common/glossary.rst:3018 +#: ../common/glossary.rst:3020 +msgid "rescue image" +msgstr "" + +#: ../common/glossary.rst:3007 ../common/glossary.rst:3012 +#: ../common/glossary.rst:3014 ../common/glossary.rst:3021 +#: ../common/glossary.rst:3023 +msgid "" +"A special type of VM image that is booted when an instance is placed into " +"rescue mode. Allows an administrator to mount the file systems for an " +"instance to correct the problem." +msgstr "" + +#: ../common/glossary.rst:3010 ../common/glossary.rst:3015 +#: ../common/glossary.rst:3017 ../common/glossary.rst:3024 +#: ../common/glossary.rst:3026 +msgid "resize" +msgstr "" + +#: ../common/glossary.rst:3013 ../common/glossary.rst:3018 +#: ../common/glossary.rst:3020 ../common/glossary.rst:3027 +#: ../common/glossary.rst:3029 +msgid "" +"Converts an existing server to a different flavor, which scales the server " +"up or down. The original server is saved to enable rollback if a problem " +"occurs. All resizes must be tested and explicitly confirmed, at which time " +"the original server is removed." +msgstr "" + +#: ../common/glossary.rst:3017 ../common/glossary.rst:3022 +#: ../common/glossary.rst:3024 ../common/glossary.rst:3031 +#: ../common/glossary.rst:3033 +msgid "RESTful" +msgstr "" + +#: ../common/glossary.rst:3020 ../common/glossary.rst:3025 +#: ../common/glossary.rst:3027 ../common/glossary.rst:3034 +#: ../common/glossary.rst:3036 +msgid "" +"A kind of web service API that uses REST, or Representational State " +"Transfer. REST is the style of architecture for hypermedia systems that is " +"used for the World Wide Web." +msgstr "" + +#: ../common/glossary.rst:3023 ../common/glossary.rst:3028 +#: ../common/glossary.rst:3030 ../common/glossary.rst:3037 +#: ../common/glossary.rst:3039 +msgid "ring" +msgstr "" + +#: ../common/glossary.rst:3026 ../common/glossary.rst:3031 +#: ../common/glossary.rst:3033 ../common/glossary.rst:3040 +#: ../common/glossary.rst:3042 +msgid "" +"An entity that maps Object Storage data to partitions. A separate ring " +"exists for each service, such as account, object, and container." +msgstr "" + +#: ../common/glossary.rst:3029 ../common/glossary.rst:3034 +#: ../common/glossary.rst:3036 ../common/glossary.rst:3043 +#: ../common/glossary.rst:3045 +msgid "ring builder" +msgstr "" + +#: ../common/glossary.rst:3032 ../common/glossary.rst:3037 +#: ../common/glossary.rst:3039 ../common/glossary.rst:3046 +#: ../common/glossary.rst:3048 +msgid "" +"Builds and manages rings within Object Storage, assigns partitions to " +"devices, and pushes the configuration to other storage nodes." +msgstr "" + +#: ../common/glossary.rst:3035 ../common/glossary.rst:3040 +#: ../common/glossary.rst:3042 ../common/glossary.rst:3049 +#: ../common/glossary.rst:3051 +msgid "Role Based Access Control (RBAC)" +msgstr "" + +#: ../common/glossary.rst:3038 ../common/glossary.rst:3043 +#: ../common/glossary.rst:3045 ../common/glossary.rst:3052 +#: ../common/glossary.rst:3054 +msgid "" +"Provides a predefined list of actions that the user can perform, such as " +"start or stop VMs, reset passwords, and so on. Supported in both Identity " +"and Compute and can be configured using the horizon dashboard." +msgstr "" + +#: ../common/glossary.rst:3042 ../common/glossary.rst:3047 +#: ../common/glossary.rst:3049 ../common/glossary.rst:3056 +#: ../common/glossary.rst:3058 +msgid "role" +msgstr "" + +#: ../common/glossary.rst:3045 ../common/glossary.rst:3050 +#: ../common/glossary.rst:3052 ../common/glossary.rst:3059 +#: ../common/glossary.rst:3061 +msgid "" +"A personality that a user assumes to perform a specific set of operations. A " +"role includes a set of rights and privileges. A user assuming that role " +"inherits those rights and privileges." +msgstr "" + +#: ../common/glossary.rst:3048 ../common/glossary.rst:3053 +#: ../common/glossary.rst:3055 ../common/glossary.rst:3062 +#: ../common/glossary.rst:3064 +msgid "role ID" +msgstr "" + +#: ../common/glossary.rst:3051 ../common/glossary.rst:3056 +#: ../common/glossary.rst:3058 ../common/glossary.rst:3065 +#: ../common/glossary.rst:3067 +msgid "Alphanumeric ID assigned to each Identity service role." +msgstr "" + +#: ../common/glossary.rst:3052 ../common/glossary.rst:3057 +#: ../common/glossary.rst:3059 ../common/glossary.rst:3066 +#: ../common/glossary.rst:3068 +msgid "rootwrap" +msgstr "" + +#: ../common/glossary.rst:3055 ../common/glossary.rst:3060 +#: ../common/glossary.rst:3062 ../common/glossary.rst:3069 +#: ../common/glossary.rst:3071 +msgid "" +"A feature of Compute that allows the unprivileged \"nova\" user to run a " +"specified list of commands as the Linux root user." +msgstr "" + +#: ../common/glossary.rst:3057 ../common/glossary.rst:3062 +#: ../common/glossary.rst:3064 ../common/glossary.rst:3071 +#: ../common/glossary.rst:3073 +msgid "round-robin scheduler" +msgstr "" + +#: ../common/glossary.rst:3060 ../common/glossary.rst:3065 +#: ../common/glossary.rst:3067 ../common/glossary.rst:3074 +#: ../common/glossary.rst:3076 +msgid "" +"Type of Compute scheduler that evenly distributes instances among available " +"hosts." +msgstr "" + +#: ../common/glossary.rst:3062 ../common/glossary.rst:3067 +#: ../common/glossary.rst:3069 ../common/glossary.rst:3076 +#: ../common/glossary.rst:3078 +msgid "router" +msgstr "" + +#: ../common/glossary.rst:3065 ../common/glossary.rst:3070 +#: ../common/glossary.rst:3072 ../common/glossary.rst:3079 +#: ../common/glossary.rst:3081 +msgid "" +"A physical or virtual network device that passes network traffic between " +"different networks." +msgstr "" + +#: ../common/glossary.rst:3067 ../common/glossary.rst:3072 +#: ../common/glossary.rst:3074 ../common/glossary.rst:3081 +#: ../common/glossary.rst:3083 +msgid "routing key" +msgstr "" + +#: ../common/glossary.rst:3070 ../common/glossary.rst:3075 +#: ../common/glossary.rst:3077 ../common/glossary.rst:3084 +#: ../common/glossary.rst:3086 +msgid "" +"The Compute direct exchanges, fanout exchanges, and topic exchanges use this " +"key to determine how to process a message; processing varies depending on " +"exchange type." +msgstr "" + +#: ../common/glossary.rst:3073 ../common/glossary.rst:3078 +#: ../common/glossary.rst:3080 ../common/glossary.rst:3087 +#: ../common/glossary.rst:3089 +msgid "RPC driver" +msgstr "" + +#: ../common/glossary.rst:3076 ../common/glossary.rst:3081 +#: ../common/glossary.rst:3083 ../common/glossary.rst:3090 +#: ../common/glossary.rst:3092 +msgid "" +"Modular system that allows the underlying message queue software of Compute " +"to be changed. For example, from RabbitMQ to ZeroMQ or Qpid." +msgstr "" + +#: ../common/glossary.rst:3079 ../common/glossary.rst:3084 +#: ../common/glossary.rst:3086 ../common/glossary.rst:3093 +#: ../common/glossary.rst:3095 +msgid "rsync" +msgstr "" + +#: ../common/glossary.rst:3082 ../common/glossary.rst:3087 +#: ../common/glossary.rst:3089 ../common/glossary.rst:3096 +#: ../common/glossary.rst:3098 +msgid "Used by Object Storage to push object replicas." +msgstr "" + +#: ../common/glossary.rst:3083 ../common/glossary.rst:3088 +#: ../common/glossary.rst:3090 ../common/glossary.rst:3097 +#: ../common/glossary.rst:3099 +msgid "RXTX cap" +msgstr "" + +#: ../common/glossary.rst:3086 ../common/glossary.rst:3091 +#: ../common/glossary.rst:3093 ../common/glossary.rst:3100 +#: ../common/glossary.rst:3102 +msgid "" +"Absolute limit on the amount of network traffic a Compute VM instance can " +"send and receive." +msgstr "" + +#: ../common/glossary.rst:3088 ../common/glossary.rst:3093 +#: ../common/glossary.rst:3095 ../common/glossary.rst:3102 +#: ../common/glossary.rst:3104 +msgid "RXTX quota" +msgstr "" + +#: ../common/glossary.rst:3091 ../common/glossary.rst:3096 +#: ../common/glossary.rst:3098 ../common/glossary.rst:3105 +#: ../common/glossary.rst:3107 +msgid "" +"Soft limit on the amount of network traffic a Compute VM instance can send " +"and receive." +msgstr "" + +#: ../common/glossary.rst:3093 ../common/glossary.rst:3098 +#: ../common/glossary.rst:3100 ../common/glossary.rst:3107 +#: ../common/glossary.rst:3109 +msgid "S3" +msgstr "" + +#: ../common/glossary.rst:3096 ../common/glossary.rst:3101 +#: ../common/glossary.rst:3103 ../common/glossary.rst:3110 +#: ../common/glossary.rst:3112 +msgid "" +"Object storage service by Amazon; similar in function to Object Storage, it " +"can act as a back-end store for Image service VM images." +msgstr "" + +#: ../common/glossary.rst:3101 ../common/glossary.rst:3106 +#: ../common/glossary.rst:3108 ../common/glossary.rst:3115 +#: ../common/glossary.rst:3117 +msgid "" +"OpenStack project that provides a scalable data-processing stack and " +"associated management interfaces." +msgstr "" + +#: ../common/glossary.rst:3103 ../common/glossary.rst:3108 +#: ../common/glossary.rst:3110 ../common/glossary.rst:3117 +#: ../common/glossary.rst:3119 +msgid "SAML assertion" +msgstr "" + +#: ../common/glossary.rst:3106 ../common/glossary.rst:3111 +#: ../common/glossary.rst:3113 ../common/glossary.rst:3120 +#: ../common/glossary.rst:3122 +msgid "" +"Contains information about a user as provided by the identity provider. It " +"is an indication that a user has been authenticated." +msgstr "" + +#: ../common/glossary.rst:3108 ../common/glossary.rst:3113 +#: ../common/glossary.rst:3115 ../common/glossary.rst:3122 +#: ../common/glossary.rst:3124 +msgid "scheduler manager" +msgstr "" + +#: ../common/glossary.rst:3111 ../common/glossary.rst:3116 +#: ../common/glossary.rst:3118 ../common/glossary.rst:3125 +#: ../common/glossary.rst:3127 +msgid "" +"A Compute component that determines where VM instances should start. Uses " +"modular design to support a variety of scheduler types." +msgstr "" + +#: ../common/glossary.rst:3114 ../common/glossary.rst:3119 +#: ../common/glossary.rst:3121 ../common/glossary.rst:3128 +#: ../common/glossary.rst:3130 +msgid "scoped token" +msgstr "" + +#: ../common/glossary.rst:3117 ../common/glossary.rst:3122 +#: ../common/glossary.rst:3124 ../common/glossary.rst:3131 +#: ../common/glossary.rst:3133 +msgid "" +"An Identity service API access token that is associated with a specific " +"tenant." +msgstr "" + +#: ../common/glossary.rst:3119 ../common/glossary.rst:3124 +#: ../common/glossary.rst:3126 ../common/glossary.rst:3133 +#: ../common/glossary.rst:3135 +msgid "scrubber" +msgstr "" + +#: ../common/glossary.rst:3122 ../common/glossary.rst:3127 +#: ../common/glossary.rst:3129 ../common/glossary.rst:3136 +#: ../common/glossary.rst:3138 +msgid "" +"Checks for and deletes unused VMs; the component of Image service that " +"implements delayed delete." +msgstr "" + +#: ../common/glossary.rst:3124 ../common/glossary.rst:3129 +#: ../common/glossary.rst:3131 ../common/glossary.rst:3138 +#: ../common/glossary.rst:3140 +msgid "secret key" +msgstr "" + +#: ../common/glossary.rst:3127 ../common/glossary.rst:3132 +#: ../common/glossary.rst:3134 ../common/glossary.rst:3141 +#: ../common/glossary.rst:3143 +msgid "" +"String of text known only by the user; used along with an access key to make " +"requests to the Compute API." +msgstr "" + +#: ../common/glossary.rst:3129 ../common/glossary.rst:3134 +#: ../common/glossary.rst:3136 ../common/glossary.rst:3143 +#: ../common/glossary.rst:3145 +msgid "secure shell (SSH)" +msgstr "" + +#: ../common/glossary.rst:3132 ../common/glossary.rst:3137 +#: ../common/glossary.rst:3139 ../common/glossary.rst:3146 +#: ../common/glossary.rst:3148 +msgid "" +"Open source tool used to access remote hosts through an encrypted " +"communications channel, SSH key injection is supported by Compute." +msgstr "" + +#: ../common/glossary.rst:3135 ../common/glossary.rst:3140 +#: ../common/glossary.rst:3142 ../common/glossary.rst:3149 +#: ../common/glossary.rst:3151 +msgid "security group" +msgstr "" + +#: ../common/glossary.rst:3138 ../common/glossary.rst:3143 +#: ../common/glossary.rst:3145 ../common/glossary.rst:3152 +#: ../common/glossary.rst:3154 +msgid "" +"A set of network traffic filtering rules that are applied to a Compute " +"instance." +msgstr "" + +#: ../common/glossary.rst:3140 ../common/glossary.rst:3145 +#: ../common/glossary.rst:3147 ../common/glossary.rst:3154 +#: ../common/glossary.rst:3156 +msgid "segmented object" +msgstr "" + +#: ../common/glossary.rst:3143 ../common/glossary.rst:3148 +#: ../common/glossary.rst:3150 ../common/glossary.rst:3157 +#: ../common/glossary.rst:3159 +msgid "" +"An Object Storage large object that has been broken up into pieces. The re-" +"assembled object is called a concatenated object." +msgstr "" + +#: ../common/glossary.rst:3146 ../common/glossary.rst:3153 +#: ../common/glossary.rst:3157 ../common/glossary.rst:3160 +#: ../common/glossary.rst:3168 +msgid "SELinux" +msgstr "" + +#: ../common/glossary.rst:3149 ../common/glossary.rst:3156 +#: ../common/glossary.rst:3160 ../common/glossary.rst:3163 +#: ../common/glossary.rst:3171 +msgid "" +"Linux kernel security module that provides the mechanism for supporting " +"access control policies." +msgstr "" + +#: ../common/glossary.rst:3151 ../common/glossary.rst:3162 +msgid "self-service" +msgstr "" + +#: ../common/glossary.rst:3151 ../common/glossary.rst:3158 +#: ../common/glossary.rst:3162 ../common/glossary.rst:3165 +#: ../common/glossary.rst:3173 +msgid "server" +msgstr "" + +#: ../common/glossary.rst:3154 ../common/glossary.rst:3161 +#: ../common/glossary.rst:3165 ../common/glossary.rst:3168 +#: ../common/glossary.rst:3176 +msgid "" +"Computer that provides explicit services to the client software running on " +"that system, often managing a variety of computer operations. A server is a " +"VM instance in the Compute system. Flavor and image are requisite elements " +"when creating a server." +msgstr "" + +#: ../common/glossary.rst:3154 ../common/glossary.rst:3165 +msgid "" +"For IaaS, ability for a regular (non-privileged) account to manage a virtual " +"infrastructure component such as networks without involving an administrator." +msgstr "" + +#: ../common/glossary.rst:3159 ../common/glossary.rst:3166 +#: ../common/glossary.rst:3170 ../common/glossary.rst:3173 +#: ../common/glossary.rst:3181 +msgid "server image" +msgstr "" + +#: ../common/glossary.rst:3162 ../common/glossary.rst:3169 +#: ../common/glossary.rst:3173 ../common/glossary.rst:3176 +#: ../common/glossary.rst:3184 +msgid "Alternative term for a VM image." +msgstr "" + +#: ../common/glossary.rst:3163 ../common/glossary.rst:3170 +#: ../common/glossary.rst:3174 ../common/glossary.rst:3177 +#: ../common/glossary.rst:3185 +msgid "server UUID" +msgstr "" + +#: ../common/glossary.rst:3167 ../common/glossary.rst:3174 +#: ../common/glossary.rst:3178 ../common/glossary.rst:3181 +#: ../common/glossary.rst:3189 +msgid "service" +msgstr "" + +#: ../common/glossary.rst:3170 ../common/glossary.rst:3177 +#: ../common/glossary.rst:3181 ../common/glossary.rst:3184 +#: ../common/glossary.rst:3192 +msgid "" +"An OpenStack service, such as Compute, Object Storage, or Image service. " +"Provides one or more endpoints through which users can access resources and " +"perform operations." +msgstr "" + +#: ../common/glossary.rst:3173 ../common/glossary.rst:3180 +#: ../common/glossary.rst:3184 ../common/glossary.rst:3187 +#: ../common/glossary.rst:3195 +msgid "service catalog" +msgstr "" + +#: ../common/glossary.rst:3176 ../common/glossary.rst:3183 +#: ../common/glossary.rst:3187 ../common/glossary.rst:3190 +#: ../common/glossary.rst:3198 +msgid "Alternative term for the Identity service catalog." +msgstr "" + +#: ../common/glossary.rst:3177 ../common/glossary.rst:3184 +#: ../common/glossary.rst:3188 ../common/glossary.rst:3191 +#: ../common/glossary.rst:3199 +msgid "service ID" +msgstr "" + +#: ../common/glossary.rst:3180 ../common/glossary.rst:3187 +#: ../common/glossary.rst:3191 ../common/glossary.rst:3194 +#: ../common/glossary.rst:3202 +msgid "" +"Unique ID assigned to each service that is available in the Identity service " +"catalog." +msgstr "" + +#: ../common/glossary.rst:3182 ../common/glossary.rst:3189 +#: ../common/glossary.rst:3193 ../common/glossary.rst:3196 +#: ../common/glossary.rst:3204 +msgid "service provider" +msgstr "" + +#: ../common/glossary.rst:3185 ../common/glossary.rst:3192 +#: ../common/glossary.rst:3196 ../common/glossary.rst:3199 +#: ../common/glossary.rst:3207 +msgid "" +"A system that provides services to other system entities. In case of " +"federated identity, OpenStack Identity is the service provider." +msgstr "" + +#: ../common/glossary.rst:3188 ../common/glossary.rst:3195 +#: ../common/glossary.rst:3199 ../common/glossary.rst:3202 +#: ../common/glossary.rst:3210 +msgid "service registration" +msgstr "" + +#: ../common/glossary.rst:3191 ../common/glossary.rst:3198 +#: ../common/glossary.rst:3202 ../common/glossary.rst:3205 +#: ../common/glossary.rst:3213 +msgid "" +"An Identity service feature that enables services, such as Compute, to " +"automatically register with the catalog." +msgstr "" + +#: ../common/glossary.rst:3193 ../common/glossary.rst:3200 +#: ../common/glossary.rst:3204 ../common/glossary.rst:3207 +#: ../common/glossary.rst:3215 +msgid "service tenant" +msgstr "" + +#: ../common/glossary.rst:3196 ../common/glossary.rst:3203 +#: ../common/glossary.rst:3207 ../common/glossary.rst:3210 +#: ../common/glossary.rst:3218 +msgid "" +"Special tenant that contains all services that are listed in the catalog." +msgstr "" + +#: ../common/glossary.rst:3198 ../common/glossary.rst:3205 +#: ../common/glossary.rst:3209 ../common/glossary.rst:3212 +#: ../common/glossary.rst:3220 +msgid "service token" +msgstr "" + +#: ../common/glossary.rst:3201 ../common/glossary.rst:3208 +#: ../common/glossary.rst:3212 ../common/glossary.rst:3215 +#: ../common/glossary.rst:3223 +msgid "" +"An administrator-defined token used by Compute to communicate securely with " +"the Identity service." +msgstr "" + +#: ../common/glossary.rst:3203 ../common/glossary.rst:3210 +#: ../common/glossary.rst:3214 ../common/glossary.rst:3217 +#: ../common/glossary.rst:3225 +msgid "session back end" +msgstr "" + +#: ../common/glossary.rst:3206 ../common/glossary.rst:3213 +#: ../common/glossary.rst:3217 ../common/glossary.rst:3220 +#: ../common/glossary.rst:3228 +msgid "" +"The method of storage used by horizon to track client sessions, such as " +"local memory, cookies, a database, or memcached." +msgstr "" + +#: ../common/glossary.rst:3208 ../common/glossary.rst:3215 +#: ../common/glossary.rst:3219 ../common/glossary.rst:3222 +#: ../common/glossary.rst:3230 +msgid "session persistence" +msgstr "" + +#: ../common/glossary.rst:3211 ../common/glossary.rst:3218 +#: ../common/glossary.rst:3222 ../common/glossary.rst:3225 +#: ../common/glossary.rst:3233 +msgid "" +"A feature of the load-balancing service. It attempts to force subsequent " +"connections to a service to be redirected to the same node as long as it is " +"online." +msgstr "" + +#: ../common/glossary.rst:3214 ../common/glossary.rst:3221 +#: ../common/glossary.rst:3225 ../common/glossary.rst:3228 +#: ../common/glossary.rst:3236 +msgid "session storage" +msgstr "" + +#: ../common/glossary.rst:3217 ../common/glossary.rst:3224 +#: ../common/glossary.rst:3228 ../common/glossary.rst:3231 +#: ../common/glossary.rst:3239 +msgid "" +"A horizon component that stores and tracks client session information. " +"Implemented through the Django sessions framework." +msgstr "" + +#: ../common/glossary.rst:3219 ../common/glossary.rst:3226 +#: ../common/glossary.rst:3230 ../common/glossary.rst:3233 +#: ../common/glossary.rst:3241 +msgid "shared IP address" +msgstr "" + +#: ../common/glossary.rst:3222 ../common/glossary.rst:3229 +#: ../common/glossary.rst:3233 ../common/glossary.rst:3236 +#: ../common/glossary.rst:3244 +msgid "" +"An IP address that can be assigned to a VM instance within the shared IP " +"group. Public IP addresses can be shared across multiple servers for use in " +"various high-availability scenarios. When an IP address is shared to another " +"server, the cloud network restrictions are modified to enable each server to " +"listen to and respond on that IP address. You can optionally specify that " +"the target server network configuration be modified. Shared IP addresses can " +"be used with many standard heartbeat facilities, such as keepalive, that " +"monitor for failure and manage IP failover." +msgstr "" + +#: ../common/glossary.rst:3231 ../common/glossary.rst:3238 +#: ../common/glossary.rst:3242 ../common/glossary.rst:3245 +#: ../common/glossary.rst:3253 +msgid "shared IP group" +msgstr "" + +#: ../common/glossary.rst:3234 ../common/glossary.rst:3241 +#: ../common/glossary.rst:3245 ../common/glossary.rst:3248 +#: ../common/glossary.rst:3256 +msgid "" +"A collection of servers that can share IPs with other members of the group. " +"Any server in a group can share one or more public IPs with any other server " +"in the group. With the exception of the first server in a shared IP group, " +"servers must be launched into shared IP groups. A server may be a member of " +"only one shared IP group." +msgstr "" + +#: ../common/glossary.rst:3239 ../common/glossary.rst:3246 +#: ../common/glossary.rst:3250 ../common/glossary.rst:3253 +#: ../common/glossary.rst:3261 +msgid "shared storage" +msgstr "" + +#: ../common/glossary.rst:3242 ../common/glossary.rst:3249 +#: ../common/glossary.rst:3253 ../common/glossary.rst:3256 +#: ../common/glossary.rst:3264 +msgid "" +"Block storage that is simultaneously accessible by multiple clients, for " +"example, NFS." +msgstr "" + +#: ../common/glossary.rst:3244 ../common/glossary.rst:3251 +#: ../common/glossary.rst:3255 ../common/glossary.rst:3258 +#: ../common/glossary.rst:3266 +msgid "Sheepdog" +msgstr "" + +#: ../common/glossary.rst:3247 ../common/glossary.rst:3254 +#: ../common/glossary.rst:3258 ../common/glossary.rst:3261 +#: ../common/glossary.rst:3269 +msgid "Distributed block storage system for QEMU, supported by OpenStack." +msgstr "" + +#: ../common/glossary.rst:3249 ../common/glossary.rst:3256 +#: ../common/glossary.rst:3260 ../common/glossary.rst:3263 +#: ../common/glossary.rst:3271 +msgid "Simple Cloud Identity Management (SCIM)" +msgstr "" + +#: ../common/glossary.rst:3252 ../common/glossary.rst:3259 +#: ../common/glossary.rst:3263 ../common/glossary.rst:3266 +#: ../common/glossary.rst:3274 +msgid "" +"Specification for managing identity in the cloud, currently unsupported by " +"OpenStack." +msgstr "" + +#: ../common/glossary.rst:3254 ../common/glossary.rst:3261 +#: ../common/glossary.rst:3265 ../common/glossary.rst:3268 +#: ../common/glossary.rst:3276 +msgid "Single-root I/O Virtualization (SR-IOV)" +msgstr "" + +#: ../common/glossary.rst:3257 ../common/glossary.rst:3264 +#: ../common/glossary.rst:3268 ../common/glossary.rst:3271 +#: ../common/glossary.rst:3279 +msgid "" +"A specification that, when implemented by a physical PCIe device, enables it " +"to appear as multiple separate PCIe devices. This enables multiple " +"virtualized guests to share direct access to the physical device, offering " +"improved performance over an equivalent virtual device. Currently supported " +"in OpenStack Havana and later releases." +msgstr "" + +#: ../common/glossary.rst:3263 ../common/glossary.rst:3270 +#: ../common/glossary.rst:3274 ../common/glossary.rst:3277 +#: ../common/glossary.rst:3285 +msgid "SmokeStack" +msgstr "" + +#: ../common/glossary.rst:3266 ../common/glossary.rst:3273 +#: ../common/glossary.rst:3277 ../common/glossary.rst:3280 +#: ../common/glossary.rst:3288 +msgid "Runs automated tests against the core OpenStack API; written in Rails." +msgstr "" + +#: ../common/glossary.rst:3268 ../common/glossary.rst:3275 +#: ../common/glossary.rst:3279 ../common/glossary.rst:3282 +#: ../common/glossary.rst:3290 +msgid "snapshot" +msgstr "" + +#: ../common/glossary.rst:3271 ../common/glossary.rst:3278 +#: ../common/glossary.rst:3282 ../common/glossary.rst:3285 +#: ../common/glossary.rst:3293 +msgid "" +"A point-in-time copy of an OpenStack storage volume or image. Use storage " +"volume snapshots to back up volumes. Use image snapshots to back up data, or " +"as \"gold\" images for additional servers." +msgstr "" + +#: ../common/glossary.rst:3274 ../common/glossary.rst:3281 +#: ../common/glossary.rst:3285 ../common/glossary.rst:3288 +#: ../common/glossary.rst:3296 +msgid "soft reboot" +msgstr "" + +#: ../common/glossary.rst:3277 ../common/glossary.rst:3284 +#: ../common/glossary.rst:3288 ../common/glossary.rst:3291 +#: ../common/glossary.rst:3299 +msgid "" +"A controlled reboot where a VM instance is properly restarted through " +"operating system commands." +msgstr "" + +#: ../common/glossary.rst:3279 ../common/glossary.rst:3286 +#: ../common/glossary.rst:3290 ../common/glossary.rst:3293 +#: ../common/glossary.rst:3301 +msgid "SolidFire Volume Driver" +msgstr "" + +#: ../common/glossary.rst:3282 ../common/glossary.rst:3289 +#: ../common/glossary.rst:3293 ../common/glossary.rst:3296 +#: ../common/glossary.rst:3304 +msgid "The Block Storage driver for the SolidFire iSCSI storage appliance." +msgstr "" + +#: ../common/glossary.rst:3284 ../common/glossary.rst:3291 +#: ../common/glossary.rst:3295 ../common/glossary.rst:3298 +#: ../common/glossary.rst:3306 +msgid "SPICE" +msgstr "" + +#: ../common/glossary.rst:3287 ../common/glossary.rst:3294 +#: ../common/glossary.rst:3298 ../common/glossary.rst:3301 +#: ../common/glossary.rst:3309 +msgid "" +"The Simple Protocol for Independent Computing Environments (SPICE) provides " +"remote desktop access to guest virtual machines. It is an alternative to " +"VNC. SPICE is supported by OpenStack." +msgstr "" + +#: ../common/glossary.rst:3290 ../common/glossary.rst:3297 +#: ../common/glossary.rst:3301 ../common/glossary.rst:3304 +#: ../common/glossary.rst:3312 +msgid "spread-first scheduler" +msgstr "" + +#: ../common/glossary.rst:3293 ../common/glossary.rst:3300 +#: ../common/glossary.rst:3304 ../common/glossary.rst:3307 +#: ../common/glossary.rst:3315 +msgid "" +"The Compute VM scheduling algorithm that attempts to start a new VM on the " +"host with the least amount of load." +msgstr "" + +#: ../common/glossary.rst:3295 ../common/glossary.rst:3302 +#: ../common/glossary.rst:3306 ../common/glossary.rst:3309 +#: ../common/glossary.rst:3317 +msgid "SQL-Alchemy" +msgstr "" + +#: ../common/glossary.rst:3298 ../common/glossary.rst:3305 +#: ../common/glossary.rst:3309 ../common/glossary.rst:3312 +#: ../common/glossary.rst:3320 +msgid "An open source SQL toolkit for Python, used in OpenStack." +msgstr "" + +#: ../common/glossary.rst:3299 ../common/glossary.rst:3306 +#: ../common/glossary.rst:3310 ../common/glossary.rst:3313 +#: ../common/glossary.rst:3321 +msgid "SQLite" +msgstr "" + +#: ../common/glossary.rst:3302 ../common/glossary.rst:3309 +#: ../common/glossary.rst:3313 ../common/glossary.rst:3316 +#: ../common/glossary.rst:3324 +msgid "" +"A lightweight SQL database, used as the default persistent storage method in " +"many OpenStack services." +msgstr "" + +#: ../common/glossary.rst:3304 ../common/glossary.rst:3311 +#: ../common/glossary.rst:3315 ../common/glossary.rst:3318 +#: ../common/glossary.rst:3326 +msgid "stack" +msgstr "" + +#: ../common/glossary.rst:3307 ../common/glossary.rst:3314 +#: ../common/glossary.rst:3318 ../common/glossary.rst:3321 +#: ../common/glossary.rst:3329 +msgid "" +"A set of OpenStack resources created and managed by the Orchestration " +"service according to a given template (either an AWS CloudFormation template " +"or a Heat Orchestration Template (HOT))." +msgstr "" + +#: ../common/glossary.rst:3311 ../common/glossary.rst:3318 +#: ../common/glossary.rst:3322 ../common/glossary.rst:3325 +#: ../common/glossary.rst:3333 +msgid "StackTach" +msgstr "" + +#: ../common/glossary.rst:3314 ../common/glossary.rst:3321 +#: ../common/glossary.rst:3325 ../common/glossary.rst:3328 +#: ../common/glossary.rst:3336 +msgid "" +"Community project that captures Compute AMQP communications; useful for " +"debugging." +msgstr "" + +#: ../common/glossary.rst:3316 ../common/glossary.rst:3323 +#: ../common/glossary.rst:3327 ../common/glossary.rst:3330 +#: ../common/glossary.rst:3338 +msgid "static IP address" +msgstr "" + +#: ../common/glossary.rst:3319 ../common/glossary.rst:3326 +#: ../common/glossary.rst:3330 ../common/glossary.rst:3333 +#: ../common/glossary.rst:3341 +msgid "Alternative term for a fixed IP address." +msgstr "" + +#: ../common/glossary.rst:3320 ../common/glossary.rst:3327 +#: ../common/glossary.rst:3331 ../common/glossary.rst:3334 +#: ../common/glossary.rst:3342 +msgid "StaticWeb" +msgstr "" + +#: ../common/glossary.rst:3323 ../common/glossary.rst:3330 +#: ../common/glossary.rst:3334 ../common/glossary.rst:3337 +#: ../common/glossary.rst:3345 +msgid "" +"WSGI middleware component of Object Storage that serves container data as a " +"static web page." +msgstr "" + +#: ../common/glossary.rst:3325 ../common/glossary.rst:3332 +#: ../common/glossary.rst:3336 ../common/glossary.rst:3339 +#: ../common/glossary.rst:3347 +msgid "storage back end" +msgstr "" + +#: ../common/glossary.rst:3328 ../common/glossary.rst:3335 +#: ../common/glossary.rst:3339 ../common/glossary.rst:3342 +#: ../common/glossary.rst:3350 +msgid "" +"The method that a service uses for persistent storage, such as iSCSI, NFS, " +"or local disk." +msgstr "" + +#: ../common/glossary.rst:3330 ../common/glossary.rst:3337 +#: ../common/glossary.rst:3341 ../common/glossary.rst:3344 +#: ../common/glossary.rst:3352 +msgid "storage node" +msgstr "" + +#: ../common/glossary.rst:3333 ../common/glossary.rst:3340 +#: ../common/glossary.rst:3344 ../common/glossary.rst:3347 +#: ../common/glossary.rst:3355 +msgid "" +"An Object Storage node that provides container services, account services, " +"and object services; controls the account databases, container databases, " +"and object storage." +msgstr "" + +#: ../common/glossary.rst:3336 ../common/glossary.rst:3343 +#: ../common/glossary.rst:3347 ../common/glossary.rst:3350 +#: ../common/glossary.rst:3358 +msgid "storage manager" +msgstr "" + +#: ../common/glossary.rst:3339 ../common/glossary.rst:3346 +#: ../common/glossary.rst:3350 ../common/glossary.rst:3353 +#: ../common/glossary.rst:3361 +msgid "" +"A XenAPI component that provides a pluggable interface to support a wide " +"variety of persistent storage back ends." +msgstr "" + +#: ../common/glossary.rst:3341 ../common/glossary.rst:3348 +#: ../common/glossary.rst:3352 ../common/glossary.rst:3355 +#: ../common/glossary.rst:3363 +msgid "storage manager back end" +msgstr "" + +#: ../common/glossary.rst:3344 ../common/glossary.rst:3351 +#: ../common/glossary.rst:3355 ../common/glossary.rst:3358 +#: ../common/glossary.rst:3366 +msgid "A persistent storage method supported by XenAPI, such as iSCSI or NFS." +msgstr "" + +#: ../common/glossary.rst:3346 ../common/glossary.rst:3353 +#: ../common/glossary.rst:3357 ../common/glossary.rst:3360 +#: ../common/glossary.rst:3368 +msgid "storage services" +msgstr "" + +#: ../common/glossary.rst:3349 ../common/glossary.rst:3356 +#: ../common/glossary.rst:3360 ../common/glossary.rst:3363 +#: ../common/glossary.rst:3371 +msgid "" +"Collective name for the Object Storage object services, container services, " +"and account services." +msgstr "" + +#: ../common/glossary.rst:3351 ../common/glossary.rst:3358 +#: ../common/glossary.rst:3362 ../common/glossary.rst:3365 +#: ../common/glossary.rst:3373 +msgid "strategy" +msgstr "" + +#: ../common/glossary.rst:3354 ../common/glossary.rst:3361 +#: ../common/glossary.rst:3365 ../common/glossary.rst:3368 +#: ../common/glossary.rst:3376 +msgid "Specifies the authentication source used by Image service or Identity." +msgstr "" + +#: ../common/glossary.rst:3356 ../common/glossary.rst:3363 +#: ../common/glossary.rst:3367 ../common/glossary.rst:3370 +#: ../common/glossary.rst:3378 +msgid "subdomain" +msgstr "" + +#: ../common/glossary.rst:3359 ../common/glossary.rst:3366 +#: ../common/glossary.rst:3370 ../common/glossary.rst:3373 +#: ../common/glossary.rst:3381 +msgid "" +"A domain within a parent domain. Subdomains cannot be registered. Subdomains " +"enable you to delegate domains. Subdomains can themselves have subdomains, " +"so third-level, fourth-level, fifth-level, and deeper levels of nesting are " +"possible." +msgstr "" + +#: ../common/glossary.rst:3363 ../common/glossary.rst:3370 +#: ../common/glossary.rst:3374 ../common/glossary.rst:3377 +#: ../common/glossary.rst:3385 +msgid "subnet" +msgstr "" + +#: ../common/glossary.rst:3366 ../common/glossary.rst:3373 +#: ../common/glossary.rst:3377 ../common/glossary.rst:3380 +#: ../common/glossary.rst:3388 +msgid "Logical subdivision of an IP network." +msgstr "" + +#: ../common/glossary.rst:3367 ../common/glossary.rst:3374 +#: ../common/glossary.rst:3378 ../common/glossary.rst:3381 +#: ../common/glossary.rst:3389 +msgid "SUSE Linux Enterprise Server (SLES)" +msgstr "" + +#: ../common/glossary.rst:3371 ../common/glossary.rst:3378 +#: ../common/glossary.rst:3382 ../common/glossary.rst:3385 +#: ../common/glossary.rst:3393 +msgid "suspend" +msgstr "" + +#: ../common/glossary.rst:3374 ../common/glossary.rst:3381 +#: ../common/glossary.rst:3385 ../common/glossary.rst:3388 +#: ../common/glossary.rst:3396 +msgid "Alternative term for a paused VM instance." +msgstr "" + +#: ../common/glossary.rst:3375 ../common/glossary.rst:3382 +#: ../common/glossary.rst:3386 ../common/glossary.rst:3389 +#: ../common/glossary.rst:3397 +msgid "swap" +msgstr "" + +#: ../common/glossary.rst:3378 ../common/glossary.rst:3385 +#: ../common/glossary.rst:3389 ../common/glossary.rst:3392 +#: ../common/glossary.rst:3400 +msgid "" +"Disk-based virtual memory used by operating systems to provide more memory " +"than is actually available on the system." +msgstr "" + +#: ../common/glossary.rst:3380 ../common/glossary.rst:3387 +#: ../common/glossary.rst:3391 ../common/glossary.rst:3394 +#: ../common/glossary.rst:3402 +msgid "swawth" +msgstr "" + +#: ../common/glossary.rst:3383 ../common/glossary.rst:3390 +#: ../common/glossary.rst:3394 ../common/glossary.rst:3397 +#: ../common/glossary.rst:3405 +msgid "" +"An authentication and authorization service for Object Storage, implemented " +"through WSGI middleware; uses Object Storage itself as the persistent " +"backing store." +msgstr "" + +#: ../common/glossary.rst:3389 ../common/glossary.rst:3396 +#: ../common/glossary.rst:3400 ../common/glossary.rst:3403 +#: ../common/glossary.rst:3411 +msgid "An OpenStack core project that provides object storage services." +msgstr "" + +#: ../common/glossary.rst:3391 ../common/glossary.rst:3398 +#: ../common/glossary.rst:3402 ../common/glossary.rst:3405 +#: ../common/glossary.rst:3413 +msgid "swift All in One (SAIO)" +msgstr "" + +#: ../common/glossary.rst:3394 ../common/glossary.rst:3401 +#: ../common/glossary.rst:3405 ../common/glossary.rst:3408 +#: ../common/glossary.rst:3416 +msgid "" +"Creates a full Object Storage development environment within a single VM." +msgstr "" + +#: ../common/glossary.rst:3396 ../common/glossary.rst:3403 +#: ../common/glossary.rst:3407 ../common/glossary.rst:3410 +#: ../common/glossary.rst:3418 +msgid "swift middleware" +msgstr "" + +#: ../common/glossary.rst:3399 ../common/glossary.rst:3406 +#: ../common/glossary.rst:3410 ../common/glossary.rst:3413 +#: ../common/glossary.rst:3421 +msgid "" +"Collective term for Object Storage components that provide additional " +"functionality." +msgstr "" + +#: ../common/glossary.rst:3401 ../common/glossary.rst:3408 +#: ../common/glossary.rst:3412 ../common/glossary.rst:3415 +#: ../common/glossary.rst:3423 +msgid "swift proxy server" +msgstr "" + +#: ../common/glossary.rst:3404 ../common/glossary.rst:3411 +#: ../common/glossary.rst:3415 ../common/glossary.rst:3418 +#: ../common/glossary.rst:3426 +msgid "" +"Acts as the gatekeeper to Object Storage and is responsible for " +"authenticating the user." +msgstr "" + +#: ../common/glossary.rst:3406 ../common/glossary.rst:3413 +#: ../common/glossary.rst:3417 ../common/glossary.rst:3420 +#: ../common/glossary.rst:3428 +msgid "swift storage node" +msgstr "" + +#: ../common/glossary.rst:3409 ../common/glossary.rst:3416 +#: ../common/glossary.rst:3420 ../common/glossary.rst:3423 +#: ../common/glossary.rst:3431 +msgid "" +"A node that runs Object Storage account, container, and object services." +msgstr "" + +#: ../common/glossary.rst:3411 ../common/glossary.rst:3418 +#: ../common/glossary.rst:3422 ../common/glossary.rst:3425 +#: ../common/glossary.rst:3433 +msgid "sync point" +msgstr "" + +#: ../common/glossary.rst:3414 ../common/glossary.rst:3421 +#: ../common/glossary.rst:3425 ../common/glossary.rst:3428 +#: ../common/glossary.rst:3436 +msgid "" +"Point in time since the last container and accounts database sync among " +"nodes within Object Storage." +msgstr "" + +#: ../common/glossary.rst:3416 ../common/glossary.rst:3423 +#: ../common/glossary.rst:3427 ../common/glossary.rst:3430 +#: ../common/glossary.rst:3438 +msgid "sysadmin" +msgstr "" + +#: ../common/glossary.rst:3419 ../common/glossary.rst:3426 +#: ../common/glossary.rst:3430 ../common/glossary.rst:3433 +#: ../common/glossary.rst:3441 +msgid "" +"One of the default roles in the Compute RBAC system. Enables a user to add " +"other users to a project, interact with VM images that are associated with " +"the project, and start and stop VM instances." +msgstr "" + +#: ../common/glossary.rst:3422 ../common/glossary.rst:3429 +#: ../common/glossary.rst:3433 ../common/glossary.rst:3436 +#: ../common/glossary.rst:3444 +msgid "system usage" +msgstr "" + +#: ../common/glossary.rst:3425 ../common/glossary.rst:3432 +#: ../common/glossary.rst:3436 ../common/glossary.rst:3439 +#: ../common/glossary.rst:3447 +msgid "" +"A Compute component that, along with the notification system, collects " +"meters and usage information. This information can be used for billing." +msgstr "" + +#: ../common/glossary.rst:3431 ../common/glossary.rst:3438 +#: ../common/glossary.rst:3442 ../common/glossary.rst:3445 +#: ../common/glossary.rst:3453 +msgid "" +"An integrated project that provides metering and measuring facilities for " +"OpenStack. The project name of Telemetry is ceilometer." +msgstr "" + +#: ../common/glossary.rst:3434 ../common/glossary.rst:3441 +#: ../common/glossary.rst:3445 ../common/glossary.rst:3448 +#: ../common/glossary.rst:3456 +msgid "TempAuth" +msgstr "" + +#: ../common/glossary.rst:3437 ../common/glossary.rst:3444 +#: ../common/glossary.rst:3448 ../common/glossary.rst:3451 +#: ../common/glossary.rst:3459 +msgid "" +"An authentication facility within Object Storage that enables Object Storage " +"itself to perform authentication and authorization. Frequently used in " +"testing and development." +msgstr "" + +#: ../common/glossary.rst:3440 ../common/glossary.rst:3447 +#: ../common/glossary.rst:3451 ../common/glossary.rst:3454 +#: ../common/glossary.rst:3462 +msgid "Tempest" +msgstr "" + +#: ../common/glossary.rst:3443 ../common/glossary.rst:3450 +#: ../common/glossary.rst:3454 ../common/glossary.rst:3457 +#: ../common/glossary.rst:3465 +msgid "" +"Automated software test suite designed to run against the trunk of the " +"OpenStack core project." +msgstr "" + +#: ../common/glossary.rst:3445 ../common/glossary.rst:3452 +#: ../common/glossary.rst:3456 ../common/glossary.rst:3459 +#: ../common/glossary.rst:3467 +msgid "TempURL" +msgstr "" + +#: ../common/glossary.rst:3448 ../common/glossary.rst:3455 +#: ../common/glossary.rst:3459 ../common/glossary.rst:3462 +#: ../common/glossary.rst:3470 +msgid "" +"An Object Storage middleware component that enables creation of URLs for " +"temporary object access." +msgstr "" + +#: ../common/glossary.rst:3450 ../common/glossary.rst:3457 +#: ../common/glossary.rst:3461 ../common/glossary.rst:3464 +#: ../common/glossary.rst:3472 +msgid "tenant" +msgstr "" + +#: ../common/glossary.rst:3453 ../common/glossary.rst:3460 +#: ../common/glossary.rst:3464 ../common/glossary.rst:3467 +#: ../common/glossary.rst:3475 +msgid "" +"A group of users; used to isolate access to Compute resources. An " +"alternative term for a project." +msgstr "" + +#: ../common/glossary.rst:3455 ../common/glossary.rst:3462 +#: ../common/glossary.rst:3466 ../common/glossary.rst:3469 +#: ../common/glossary.rst:3477 +msgid "Tenant API" +msgstr "" + +#: ../common/glossary.rst:3458 ../common/glossary.rst:3465 +#: ../common/glossary.rst:3469 ../common/glossary.rst:3472 +#: ../common/glossary.rst:3480 +msgid "An API that is accessible to tenants." +msgstr "" + +#: ../common/glossary.rst:3459 ../common/glossary.rst:3466 +#: ../common/glossary.rst:3470 ../common/glossary.rst:3473 +#: ../common/glossary.rst:3481 +msgid "tenant endpoint" +msgstr "" + +#: ../common/glossary.rst:3462 ../common/glossary.rst:3469 +#: ../common/glossary.rst:3473 ../common/glossary.rst:3476 +#: ../common/glossary.rst:3484 +msgid "" +"An Identity service API endpoint that is associated with one or more tenants." +msgstr "" + +#: ../common/glossary.rst:3464 ../common/glossary.rst:3471 +#: ../common/glossary.rst:3475 ../common/glossary.rst:3478 +#: ../common/glossary.rst:3486 +msgid "tenant ID" +msgstr "" + +#: ../common/glossary.rst:3467 ../common/glossary.rst:3474 +#: ../common/glossary.rst:3478 ../common/glossary.rst:3481 +#: ../common/glossary.rst:3489 +msgid "" +"Unique ID assigned to each tenant within the Identity service. The project " +"IDs map to the tenant IDs." +msgstr "" + +#: ../common/glossary.rst:3469 ../common/glossary.rst:3476 +#: ../common/glossary.rst:3480 ../common/glossary.rst:3483 +#: ../common/glossary.rst:3491 +msgid "token" +msgstr "" + +#: ../common/glossary.rst:3472 ../common/glossary.rst:3479 +#: ../common/glossary.rst:3483 ../common/glossary.rst:3486 +#: ../common/glossary.rst:3494 +msgid "" +"An alpha-numeric string of text used to access OpenStack APIs and resources." +msgstr "" + +#: ../common/glossary.rst:3474 ../common/glossary.rst:3481 +#: ../common/glossary.rst:3485 ../common/glossary.rst:3488 +#: ../common/glossary.rst:3496 +msgid "token services" +msgstr "" + +#: ../common/glossary.rst:3477 ../common/glossary.rst:3484 +#: ../common/glossary.rst:3488 ../common/glossary.rst:3491 +#: ../common/glossary.rst:3499 +msgid "" +"An Identity service component that manages and validates tokens after a user " +"or tenant has been authenticated." +msgstr "" + +#: ../common/glossary.rst:3479 ../common/glossary.rst:3486 +#: ../common/glossary.rst:3490 ../common/glossary.rst:3493 +#: ../common/glossary.rst:3501 +msgid "tombstone" +msgstr "" + +#: ../common/glossary.rst:3482 ../common/glossary.rst:3489 +#: ../common/glossary.rst:3493 ../common/glossary.rst:3496 +#: ../common/glossary.rst:3504 +msgid "" +"Used to mark Object Storage objects that have been deleted; ensures that the " +"object is not updated on another node after it has been deleted." +msgstr "" + +#: ../common/glossary.rst:3485 ../common/glossary.rst:3492 +#: ../common/glossary.rst:3496 ../common/glossary.rst:3499 +#: ../common/glossary.rst:3507 +msgid "topic publisher" +msgstr "" + +#: ../common/glossary.rst:3488 ../common/glossary.rst:3495 +#: ../common/glossary.rst:3499 ../common/glossary.rst:3502 +#: ../common/glossary.rst:3510 +msgid "" +"A process that is created when a RPC call is executed; used to push the " +"message to the topic exchange." +msgstr "" + +#: ../common/glossary.rst:3490 ../common/glossary.rst:3497 +#: ../common/glossary.rst:3501 ../common/glossary.rst:3504 +#: ../common/glossary.rst:3512 +msgid "Torpedo" +msgstr "" + +#: ../common/glossary.rst:3493 ../common/glossary.rst:3500 +#: ../common/glossary.rst:3504 ../common/glossary.rst:3507 +#: ../common/glossary.rst:3515 +msgid "" +"Community project used to run automated tests against the OpenStack API." +msgstr "" + +#: ../common/glossary.rst:3495 ../common/glossary.rst:3502 +#: ../common/glossary.rst:3506 ../common/glossary.rst:3509 +#: ../common/glossary.rst:3517 +msgid "transaction ID" +msgstr "" + +#: ../common/glossary.rst:3498 ../common/glossary.rst:3505 +#: ../common/glossary.rst:3509 ../common/glossary.rst:3512 +#: ../common/glossary.rst:3520 +msgid "" +"Unique ID assigned to each Object Storage request; used for debugging and " +"tracing." +msgstr "" + +#: ../common/glossary.rst:3500 ../common/glossary.rst:3507 +#: ../common/glossary.rst:3511 ../common/glossary.rst:3514 +#: ../common/glossary.rst:3522 +msgid "transient" +msgstr "" + +#: ../common/glossary.rst:3503 ../common/glossary.rst:3510 +#: ../common/glossary.rst:3514 ../common/glossary.rst:3517 +#: ../common/glossary.rst:3525 +msgid "Alternative term for non-durable." +msgstr "" + +#: ../common/glossary.rst:3504 ../common/glossary.rst:3511 +#: ../common/glossary.rst:3515 ../common/glossary.rst:3518 +#: ../common/glossary.rst:3526 +msgid "transient exchange" +msgstr "" + +#: ../common/glossary.rst:3507 ../common/glossary.rst:3514 +#: ../common/glossary.rst:3518 ../common/glossary.rst:3521 +#: ../common/glossary.rst:3529 +msgid "Alternative term for a non-durable exchange." +msgstr "" + +#: ../common/glossary.rst:3508 ../common/glossary.rst:3515 +#: ../common/glossary.rst:3519 ../common/glossary.rst:3522 +#: ../common/glossary.rst:3530 +msgid "transient message" +msgstr "" + +#: ../common/glossary.rst:3511 ../common/glossary.rst:3518 +#: ../common/glossary.rst:3522 ../common/glossary.rst:3525 +#: ../common/glossary.rst:3533 +msgid "" +"A message that is stored in memory and is lost after the server is restarted." +msgstr "" + +#: ../common/glossary.rst:3513 ../common/glossary.rst:3520 +#: ../common/glossary.rst:3524 ../common/glossary.rst:3527 +#: ../common/glossary.rst:3535 +msgid "transient queue" +msgstr "" + +#: ../common/glossary.rst:3516 ../common/glossary.rst:3523 +#: ../common/glossary.rst:3527 ../common/glossary.rst:3530 +#: ../common/glossary.rst:3538 +msgid "Alternative term for a non-durable queue." +msgstr "" + +#: ../common/glossary.rst:3517 ../common/glossary.rst:3524 +#: ../common/glossary.rst:3528 ../common/glossary.rst:3531 +#: ../common/glossary.rst:3539 +msgid "TripleO" +msgstr "" + +#: ../common/glossary.rst:3520 ../common/glossary.rst:3527 +#: ../common/glossary.rst:3531 ../common/glossary.rst:3534 +#: ../common/glossary.rst:3542 +msgid "" +"OpenStack-on-OpenStack program. The code name for the OpenStack Deployment " +"program." +msgstr "" + +#: ../common/glossary.rst:3525 ../common/glossary.rst:3532 +#: ../common/glossary.rst:3536 ../common/glossary.rst:3539 +#: ../common/glossary.rst:3547 +msgid "OpenStack project that provides database services to applications." +msgstr "" + +#: ../common/glossary.rst:3527 ../common/glossary.rst:3534 +#: ../common/glossary.rst:3538 ../common/glossary.rst:3541 +#: ../common/glossary.rst:3549 +msgid "Ubuntu" +msgstr "" + +#: ../common/glossary.rst:3530 ../common/glossary.rst:3537 +#: ../common/glossary.rst:3541 ../common/glossary.rst:3544 +#: ../common/glossary.rst:3552 +msgid "A Debian-based Linux distribution." +msgstr "" + +#: ../common/glossary.rst:3531 ../common/glossary.rst:3538 +#: ../common/glossary.rst:3542 ../common/glossary.rst:3545 +#: ../common/glossary.rst:3553 +msgid "unscoped token" +msgstr "" + +#: ../common/glossary.rst:3534 ../common/glossary.rst:3541 +#: ../common/glossary.rst:3545 ../common/glossary.rst:3548 +#: ../common/glossary.rst:3556 +msgid "Alternative term for an Identity service default token." +msgstr "" + +#: ../common/glossary.rst:3535 ../common/glossary.rst:3542 +#: ../common/glossary.rst:3546 ../common/glossary.rst:3549 +#: ../common/glossary.rst:3557 +msgid "updater" +msgstr "" + +#: ../common/glossary.rst:3538 ../common/glossary.rst:3545 +#: ../common/glossary.rst:3549 ../common/glossary.rst:3552 +#: ../common/glossary.rst:3560 +msgid "" +"Collective term for a group of Object Storage components that processes " +"queued and failed updates for containers and objects." +msgstr "" + +#: ../common/glossary.rst:3540 ../common/glossary.rst:3547 +#: ../common/glossary.rst:3551 ../common/glossary.rst:3554 +#: ../common/glossary.rst:3562 +msgid "user" +msgstr "" + +#: ../common/glossary.rst:3543 ../common/glossary.rst:3550 +msgid "" +"In Identity, each user is associated with one or more tenants, and in " +"Compute can be associated with roles, projects, or both." +msgstr "" + +#: ../common/glossary.rst:3546 ../common/glossary.rst:3553 +#: ../common/glossary.rst:3557 ../common/glossary.rst:3560 +#: ../common/glossary.rst:3568 +msgid "user data" +msgstr "" + +#: ../common/glossary.rst:3549 ../common/glossary.rst:3556 +#: ../common/glossary.rst:3560 ../common/glossary.rst:3563 +#: ../common/glossary.rst:3571 +msgid "" +"A blob of data that the user can specify when they launch an instance. The " +"instance can access this data through the metadata service or config drive. " +"Commonly used to pass a shell script that the instance runs on boot." +msgstr "" + +#: ../common/glossary.rst:3553 ../common/glossary.rst:3560 +#: ../common/glossary.rst:3564 ../common/glossary.rst:3567 +#: ../common/glossary.rst:3575 +msgid "User Mode Linux (UML)" +msgstr "" + +#: ../common/glossary.rst:3554 ../common/glossary.rst:3557 +#: ../common/glossary.rst:3565 +msgid "" +"In OpenStack Identity, entities represent individual API consumers and are " +"owned by a specific domain. In OpenStack Compute, a user can be associated " +"with roles, projects, or both." +msgstr "" + +#: ../common/glossary.rst:3557 ../common/glossary.rst:3564 +#: ../common/glossary.rst:3568 ../common/glossary.rst:3571 +#: ../common/glossary.rst:3579 +msgid "VIF UUID" +msgstr "" + +#: ../common/glossary.rst:3560 ../common/glossary.rst:3567 +#: ../common/glossary.rst:3571 ../common/glossary.rst:3574 +#: ../common/glossary.rst:3582 +msgid "Unique ID assigned to each Networking VIF." +msgstr "" + +#: ../common/glossary.rst:3561 ../common/glossary.rst:3568 +#: ../common/glossary.rst:3572 ../common/glossary.rst:3575 +#: ../common/glossary.rst:3583 +msgid "VIP" +msgstr "" + +#: ../common/glossary.rst:3564 ../common/glossary.rst:3571 +#: ../common/glossary.rst:3575 ../common/glossary.rst:3578 +#: ../common/glossary.rst:3586 +msgid "" +"The primary load balancing configuration object. Specifies the virtual IP " +"address and port where client traffic is received. Also defines other " +"details such as the load balancing method to be used, protocol, and so on. " +"This entity is sometimes known in load-balancing products as a virtual " +"server, vserver, or listener." +msgstr "" + +#: ../common/glossary.rst:3570 ../common/glossary.rst:3577 +#: ../common/glossary.rst:3581 ../common/glossary.rst:3584 +#: ../common/glossary.rst:3592 +msgid "Virtual Central Processing Unit (vCPU)" +msgstr "" + +#: ../common/glossary.rst:3573 ../common/glossary.rst:3580 +#: ../common/glossary.rst:3584 ../common/glossary.rst:3587 +#: ../common/glossary.rst:3595 +msgid "Subdivides physical CPUs. Instances can then use those divisions." +msgstr "" + +#: ../common/glossary.rst:3575 ../common/glossary.rst:3582 +#: ../common/glossary.rst:3586 ../common/glossary.rst:3589 +#: ../common/glossary.rst:3597 +msgid "Virtual Disk Image (VDI)" +msgstr "" + +#: ../common/glossary.rst:3580 ../common/glossary.rst:3587 +#: ../common/glossary.rst:3594 +msgid "virtual extensible LAN (VXLAN)" +msgstr "" + +#: ../common/glossary.rst:3583 ../common/glossary.rst:3590 +#: ../common/glossary.rst:3594 ../common/glossary.rst:3597 +#: ../common/glossary.rst:3605 +msgid "" +"A network virtualization technology that attempts to reduce the scalability " +"problems associated with large cloud computing deployments. It uses a VLAN-" +"like encapsulation technique to encapsulate Ethernet frames within UDP " +"packets." +msgstr "" + +#: ../common/glossary.rst:3587 ../common/glossary.rst:3594 +#: ../common/glossary.rst:3598 ../common/glossary.rst:3601 +#: ../common/glossary.rst:3609 +msgid "Virtual Hard Disk (VHD)" +msgstr "" + +#: ../common/glossary.rst:3591 ../common/glossary.rst:3602 +msgid "VXLAN" +msgstr "" + +#: ../common/glossary.rst:3592 ../common/glossary.rst:3599 +#: ../common/glossary.rst:3603 ../common/glossary.rst:3606 +#: ../common/glossary.rst:3614 +msgid "virtual IP" +msgstr "" + +#: ../common/glossary.rst:3595 ../common/glossary.rst:3602 +#: ../common/glossary.rst:3606 ../common/glossary.rst:3609 +#: ../common/glossary.rst:3617 +msgid "" +"An Internet Protocol (IP) address configured on the load balancer for use by " +"clients connecting to a service that is load balanced. Incoming connections " +"are distributed to back-end nodes based on the configuration of the load " +"balancer." +msgstr "" + +#: ../common/glossary.rst:3599 ../common/glossary.rst:3606 +#: ../common/glossary.rst:3610 ../common/glossary.rst:3613 +#: ../common/glossary.rst:3621 +msgid "virtual machine (VM)" +msgstr "" + +#: ../common/glossary.rst:3602 ../common/glossary.rst:3609 +#: ../common/glossary.rst:3613 ../common/glossary.rst:3616 +#: ../common/glossary.rst:3624 +msgid "" +"An operating system instance that runs on top of a hypervisor. Multiple VMs " +"can run at the same time on the same physical host." +msgstr "" + +#: ../common/glossary.rst:3605 ../common/glossary.rst:3612 +#: ../common/glossary.rst:3616 ../common/glossary.rst:3619 +#: ../common/glossary.rst:3627 +msgid "virtual network" +msgstr "" + +#: ../common/glossary.rst:3608 ../common/glossary.rst:3615 +#: ../common/glossary.rst:3619 ../common/glossary.rst:3622 +#: ../common/glossary.rst:3630 +msgid "An L2 network segment within Networking." +msgstr "" + +#: ../common/glossary.rst:3609 ../common/glossary.rst:3616 +#: ../common/glossary.rst:3620 ../common/glossary.rst:3623 +#: ../common/glossary.rst:3631 +msgid "virtual networking" +msgstr "" + +#: ../common/glossary.rst:3612 ../common/glossary.rst:3619 +#: ../common/glossary.rst:3623 ../common/glossary.rst:3626 +#: ../common/glossary.rst:3634 +msgid "" +"A generic term for virtualization of network functions such as switching, " +"routing, load balancing, and security using a combination of VMs and " +"overlays on physical network infrastructure." +msgstr "" + +#: ../common/glossary.rst:3616 ../common/glossary.rst:3623 +#: ../common/glossary.rst:3627 ../common/glossary.rst:3630 +#: ../common/glossary.rst:3638 +msgid "Virtual Network Computing (VNC)" +msgstr "" + +#: ../common/glossary.rst:3619 ../common/glossary.rst:3626 +#: ../common/glossary.rst:3630 ../common/glossary.rst:3633 +#: ../common/glossary.rst:3641 +msgid "" +"Open source GUI and CLI tools used for remote console access to VMs. " +"Supported by Compute." +msgstr "" + +#: ../common/glossary.rst:3621 ../common/glossary.rst:3628 +#: ../common/glossary.rst:3632 ../common/glossary.rst:3635 +#: ../common/glossary.rst:3643 +msgid "Virtual Network InterFace (VIF)" +msgstr "" + +#: ../common/glossary.rst:3624 ../common/glossary.rst:3631 +#: ../common/glossary.rst:3635 ../common/glossary.rst:3638 +#: ../common/glossary.rst:3646 +msgid "" +"An interface that is plugged into a port in a Networking network. Typically " +"a virtual network interface belonging to a VM." +msgstr "" + +#: ../common/glossary.rst:3627 ../common/glossary.rst:3634 +#: ../common/glossary.rst:3638 ../common/glossary.rst:3641 +#: ../common/glossary.rst:3649 +msgid "virtual port" +msgstr "" + +#: ../common/glossary.rst:3630 ../common/glossary.rst:3637 +#: ../common/glossary.rst:3641 ../common/glossary.rst:3644 +#: ../common/glossary.rst:3652 +msgid "" +"Attachment point where a virtual interface connects to a virtual network." +msgstr "" + +#: ../common/glossary.rst:3632 ../common/glossary.rst:3639 +#: ../common/glossary.rst:3643 ../common/glossary.rst:3646 +#: ../common/glossary.rst:3654 +msgid "virtual private network (VPN)" +msgstr "" + +#: ../common/glossary.rst:3635 ../common/glossary.rst:3642 +#: ../common/glossary.rst:3646 ../common/glossary.rst:3649 +#: ../common/glossary.rst:3657 +msgid "" +"Provided by Compute in the form of cloudpipes, specialized instances that " +"are used to create VPNs on a per-project basis." +msgstr "" + +#: ../common/glossary.rst:3637 ../common/glossary.rst:3644 +#: ../common/glossary.rst:3648 ../common/glossary.rst:3651 +#: ../common/glossary.rst:3659 +msgid "virtual server" +msgstr "" + +#: ../common/glossary.rst:3640 ../common/glossary.rst:3647 +#: ../common/glossary.rst:3651 ../common/glossary.rst:3654 +#: ../common/glossary.rst:3662 +msgid "Alternative term for a VM or guest." +msgstr "" + +#: ../common/glossary.rst:3641 ../common/glossary.rst:3648 +#: ../common/glossary.rst:3652 ../common/glossary.rst:3655 +#: ../common/glossary.rst:3663 +msgid "virtual switch (vSwitch)" +msgstr "" + +#: ../common/glossary.rst:3644 ../common/glossary.rst:3651 +#: ../common/glossary.rst:3655 ../common/glossary.rst:3658 +#: ../common/glossary.rst:3666 +msgid "" +"Software that runs on a host or node and provides the features and functions " +"of a hardware-based network switch." +msgstr "" + +#: ../common/glossary.rst:3646 ../common/glossary.rst:3653 +#: ../common/glossary.rst:3657 ../common/glossary.rst:3660 +#: ../common/glossary.rst:3668 +msgid "virtual VLAN" +msgstr "" + +#: ../common/glossary.rst:3649 ../common/glossary.rst:3656 +#: ../common/glossary.rst:3660 ../common/glossary.rst:3663 +#: ../common/glossary.rst:3671 +msgid "Alternative term for a virtual network." +msgstr "" + +#: ../common/glossary.rst:3650 ../common/glossary.rst:3657 +#: ../common/glossary.rst:3661 ../common/glossary.rst:3664 +#: ../common/glossary.rst:3672 +msgid "VirtualBox" +msgstr "" + +#: ../common/glossary.rst:3654 ../common/glossary.rst:3661 +#: ../common/glossary.rst:3665 ../common/glossary.rst:3668 +#: ../common/glossary.rst:3676 +msgid "VLAN manager" +msgstr "" + +#: ../common/glossary.rst:3657 ../common/glossary.rst:3664 +#: ../common/glossary.rst:3668 ../common/glossary.rst:3671 +#: ../common/glossary.rst:3679 +msgid "" +"A Compute component that provides dnsmasq and radvd and sets up forwarding " +"to and from cloudpipe instances." +msgstr "" + +#: ../common/glossary.rst:3659 ../common/glossary.rst:3666 +#: ../common/glossary.rst:3670 ../common/glossary.rst:3673 +#: ../common/glossary.rst:3681 +msgid "VLAN network" +msgstr "" + +#: ../common/glossary.rst:3662 ../common/glossary.rst:3669 +#: ../common/glossary.rst:3673 ../common/glossary.rst:3676 +#: ../common/glossary.rst:3684 +msgid "" +"The Network Controller provides virtual networks to enable compute servers " +"to interact with each other and with the public network. All machines must " +"have a public and private network interface. A VLAN network is a private " +"network interface, which is controlled by the `vlan_interface` option with " +"VLAN managers." +msgstr "" + +#: ../common/glossary.rst:3668 ../common/glossary.rst:3675 +#: ../common/glossary.rst:3679 ../common/glossary.rst:3682 +#: ../common/glossary.rst:3690 +msgid "VM disk (VMDK)" +msgstr "" + +#: ../common/glossary.rst:3673 ../common/glossary.rst:3680 +#: ../common/glossary.rst:3684 ../common/glossary.rst:3687 +#: ../common/glossary.rst:3695 +msgid "VM image" +msgstr "" + +#: ../common/glossary.rst:3676 ../common/glossary.rst:3683 +#: ../common/glossary.rst:3687 ../common/glossary.rst:3690 +#: ../common/glossary.rst:3698 +msgid "Alternative term for an image." +msgstr "" + +#: ../common/glossary.rst:3677 ../common/glossary.rst:3684 +#: ../common/glossary.rst:3688 ../common/glossary.rst:3691 +#: ../common/glossary.rst:3699 +msgid "VM Remote Control (VMRC)" +msgstr "" + +#: ../common/glossary.rst:3680 ../common/glossary.rst:3687 +#: ../common/glossary.rst:3691 ../common/glossary.rst:3694 +#: ../common/glossary.rst:3702 +msgid "" +"Method to access VM instance consoles using a web browser. Supported by " +"Compute." +msgstr "" + +#: ../common/glossary.rst:3682 ../common/glossary.rst:3689 +#: ../common/glossary.rst:3693 ../common/glossary.rst:3696 +#: ../common/glossary.rst:3704 +msgid "VMware API" +msgstr "" + +#: ../common/glossary.rst:3685 ../common/glossary.rst:3692 +#: ../common/glossary.rst:3696 ../common/glossary.rst:3699 +#: ../common/glossary.rst:3707 +msgid "Supports interaction with VMware products in Compute." +msgstr "" + +#: ../common/glossary.rst:3686 ../common/glossary.rst:3693 +#: ../common/glossary.rst:3697 ../common/glossary.rst:3700 +#: ../common/glossary.rst:3708 +msgid "VMware NSX Neutron plug-in" +msgstr "" + +#: ../common/glossary.rst:3689 ../common/glossary.rst:3696 +#: ../common/glossary.rst:3700 ../common/glossary.rst:3703 +#: ../common/glossary.rst:3711 +msgid "Provides support for VMware NSX in Neutron." +msgstr "" + +#: ../common/glossary.rst:3690 ../common/glossary.rst:3697 +#: ../common/glossary.rst:3701 ../common/glossary.rst:3704 +#: ../common/glossary.rst:3712 +msgid "VNC proxy" +msgstr "" + +#: ../common/glossary.rst:3693 ../common/glossary.rst:3700 +#: ../common/glossary.rst:3704 ../common/glossary.rst:3707 +#: ../common/glossary.rst:3715 +msgid "" +"A Compute component that provides users access to the consoles of their VM " +"instances through VNC or VMRC." +msgstr "" + +#: ../common/glossary.rst:3695 ../common/glossary.rst:3702 +#: ../common/glossary.rst:3706 ../common/glossary.rst:3709 +#: ../common/glossary.rst:3717 +msgid "volume" +msgstr "" + +#: ../common/glossary.rst:3698 ../common/glossary.rst:3705 +#: ../common/glossary.rst:3709 ../common/glossary.rst:3712 +#: ../common/glossary.rst:3720 +msgid "" +"Disk-based data storage generally represented as an iSCSI target with a file " +"system that supports extended attributes; can be persistent or ephemeral." +msgstr "" + +#: ../common/glossary.rst:3701 ../common/glossary.rst:3708 +#: ../common/glossary.rst:3712 ../common/glossary.rst:3715 +#: ../common/glossary.rst:3723 +msgid "Volume API" +msgstr "" + +#: ../common/glossary.rst:3704 ../common/glossary.rst:3711 +#: ../common/glossary.rst:3715 ../common/glossary.rst:3718 +#: ../common/glossary.rst:3726 +msgid "Alternative name for the Block Storage API." +msgstr "" + +#: ../common/glossary.rst:3705 ../common/glossary.rst:3712 +#: ../common/glossary.rst:3716 ../common/glossary.rst:3719 +#: ../common/glossary.rst:3727 +msgid "volume controller" +msgstr "" + +#: ../common/glossary.rst:3708 ../common/glossary.rst:3715 +#: ../common/glossary.rst:3719 ../common/glossary.rst:3722 +#: ../common/glossary.rst:3730 +msgid "" +"A Block Storage component that oversees and coordinates storage volume " +"actions." +msgstr "" + +#: ../common/glossary.rst:3710 ../common/glossary.rst:3717 +#: ../common/glossary.rst:3721 ../common/glossary.rst:3724 +#: ../common/glossary.rst:3732 +msgid "volume driver" +msgstr "" + +#: ../common/glossary.rst:3713 ../common/glossary.rst:3720 +#: ../common/glossary.rst:3724 ../common/glossary.rst:3727 +#: ../common/glossary.rst:3735 +msgid "Alternative term for a volume plug-in." +msgstr "" + +#: ../common/glossary.rst:3714 ../common/glossary.rst:3721 +#: ../common/glossary.rst:3725 ../common/glossary.rst:3728 +#: ../common/glossary.rst:3736 +msgid "volume ID" +msgstr "" + +#: ../common/glossary.rst:3717 ../common/glossary.rst:3724 +#: ../common/glossary.rst:3728 ../common/glossary.rst:3731 +#: ../common/glossary.rst:3739 +msgid "" +"Unique ID applied to each storage volume under the Block Storage control." +msgstr "" + +#: ../common/glossary.rst:3719 ../common/glossary.rst:3726 +#: ../common/glossary.rst:3730 ../common/glossary.rst:3733 +#: ../common/glossary.rst:3741 +msgid "volume manager" +msgstr "" + +#: ../common/glossary.rst:3722 ../common/glossary.rst:3729 +#: ../common/glossary.rst:3733 ../common/glossary.rst:3736 +#: ../common/glossary.rst:3744 +msgid "" +"A Block Storage component that creates, attaches, and detaches persistent " +"storage volumes." +msgstr "" + +#: ../common/glossary.rst:3724 ../common/glossary.rst:3731 +#: ../common/glossary.rst:3735 ../common/glossary.rst:3738 +#: ../common/glossary.rst:3746 +msgid "volume node" +msgstr "" + +#: ../common/glossary.rst:3727 ../common/glossary.rst:3734 +#: ../common/glossary.rst:3738 ../common/glossary.rst:3741 +#: ../common/glossary.rst:3749 +msgid "A Block Storage node that runs the cinder-volume daemon." +msgstr "" + +#: ../common/glossary.rst:3728 ../common/glossary.rst:3735 +#: ../common/glossary.rst:3739 ../common/glossary.rst:3742 +#: ../common/glossary.rst:3750 +msgid "volume plug-in" +msgstr "" + +#: ../common/glossary.rst:3731 ../common/glossary.rst:3738 +#: ../common/glossary.rst:3742 ../common/glossary.rst:3745 +#: ../common/glossary.rst:3753 +msgid "" +"Provides support for new and specialized types of back-end storage for the " +"Block Storage volume manager." +msgstr "" + +#: ../common/glossary.rst:3733 ../common/glossary.rst:3740 +#: ../common/glossary.rst:3744 ../common/glossary.rst:3747 +#: ../common/glossary.rst:3755 +msgid "volume worker" +msgstr "" + +#: ../common/glossary.rst:3736 ../common/glossary.rst:3743 +#: ../common/glossary.rst:3747 ../common/glossary.rst:3750 +#: ../common/glossary.rst:3758 +msgid "" +"A cinder component that interacts with back-end storage to manage the " +"creation and deletion of volumes and the creation of compute volumes, " +"provided by the cinder-volume daemon." +msgstr "" + +#: ../common/glossary.rst:3739 ../common/glossary.rst:3746 +#: ../common/glossary.rst:3750 ../common/glossary.rst:3753 +#: ../common/glossary.rst:3761 +msgid "vSphere" +msgstr "" + +#: ../common/glossary.rst:3743 ../common/glossary.rst:3750 +#: ../common/glossary.rst:3754 ../common/glossary.rst:3757 +#: ../common/glossary.rst:3765 +msgid "weighting" +msgstr "" + +#: ../common/glossary.rst:3746 ../common/glossary.rst:3753 +#: ../common/glossary.rst:3757 ../common/glossary.rst:3760 +#: ../common/glossary.rst:3768 +msgid "" +"A Compute process that determines the suitability of the VM instances for a " +"job for a particular host. For example, not enough RAM on the host, too many " +"CPUs on the host, and so on." +msgstr "" + +#: ../common/glossary.rst:3749 ../common/glossary.rst:3756 +#: ../common/glossary.rst:3760 ../common/glossary.rst:3763 +#: ../common/glossary.rst:3771 +msgid "weight" +msgstr "" + +#: ../common/glossary.rst:3752 ../common/glossary.rst:3759 +#: ../common/glossary.rst:3763 ../common/glossary.rst:3766 +#: ../common/glossary.rst:3774 +msgid "" +"Used by Object Storage devices to determine which storage devices are " +"suitable for the job. Devices are weighted by size." +msgstr "" + +#: ../common/glossary.rst:3754 ../common/glossary.rst:3761 +#: ../common/glossary.rst:3765 ../common/glossary.rst:3768 +#: ../common/glossary.rst:3776 +msgid "weighted cost" msgstr "" #: ../common/glossary.rst:3757 ../common/glossary.rst:3764 -#: ../common/glossary.rst:3771 ../common/glossary.rst:3779 -#: ../common/glossary.rst:3768 +#: ../common/glossary.rst:3768 ../common/glossary.rst:3771 +#: ../common/glossary.rst:3779 msgid "" "The sum of each cost used when deciding where to start a new VM instance in " "Compute." msgstr "" -#: ../common/glossary.rst:1837 ../common/glossary.rst:1843 -msgid "The tenant who owns an Image service virtual machine image." +#: ../common/glossary.rst:3759 ../common/glossary.rst:3766 +#: ../common/glossary.rst:3770 ../common/glossary.rst:3773 +#: ../common/glossary.rst:3781 +msgid "worker" msgstr "" -#: ../common/cli_manage_images.rst:146 -msgid "The tenant who should own the image. The size of image data, in bytes." -msgstr "" - -#: ../common/log_in_dashboard.rst:39 +#: ../common/glossary.rst:3762 ../common/glossary.rst:3769 +#: ../common/glossary.rst:3773 ../common/glossary.rst:3776 +#: ../common/glossary.rst:3784 msgid "" -"The top of the window displays your user name. You can also access settings " -"or sign out of the dashboard." +"A daemon that listens to a queue and carries out tasks in response to " +"messages. For example, the cinder-volume worker manages volume creation and " +"deletion on storage arrays." msgstr "" -#: ../common/glossary.rst:1210 ../common/glossary.rst:1211 +#: ../common/glossary.rst:3768 ../common/glossary.rst:3775 +#: ../common/glossary.rst:3779 ../common/glossary.rst:3782 +#: ../common/glossary.rst:3790 msgid "" -"The transfer of data, usually in the form of files, from one computer to " -"another." +"OpenStack project that provides a simple YAML-based language to write " +"workflows, tasks and transition rules, and a service that allows to upload " +"them, modify, run them at scale and in a highly available manner, manage and " +"monitor workflow execution state and state of individual tasks. The code " +"name of the project is mistral." msgstr "" -#: ../common/glossary.rst:1135 +#: ../common/glossary.rst:3774 ../common/glossary.rst:3781 +#: ../common/glossary.rst:3785 ../common/glossary.rst:3788 +#: ../common/glossary.rst:3796 +msgid "Xen" +msgstr "" + +#: ../common/glossary.rst:3777 ../common/glossary.rst:3784 +#: ../common/glossary.rst:3788 ../common/glossary.rst:3791 +#: ../common/glossary.rst:3799 msgid "" -"The underlying format that a disk image for a VM is stored as within the " -"Image service back-end store. For example, AMI, ISO, QCOW2, VMDK, and so on." +"Xen is a hypervisor using a microkernel design, providing services that " +"allow multiple computer operating systems to execute on the same computer " +"hardware concurrently." msgstr "" -#: ../common/glossary.rst:448 +#: ../common/glossary.rst:3780 ../common/glossary.rst:3787 +#: ../common/glossary.rst:3791 ../common/glossary.rst:3794 +#: ../common/glossary.rst:3802 +msgid "Xen API" +msgstr "" + +#: ../common/glossary.rst:3783 ../common/glossary.rst:3790 +#: ../common/glossary.rst:3794 ../common/glossary.rst:3797 +#: ../common/glossary.rst:3805 +msgid "The Xen administrative API, which is supported by Compute." +msgstr "" + +#: ../common/glossary.rst:3785 ../common/glossary.rst:3792 +#: ../common/glossary.rst:3796 ../common/glossary.rst:3799 +#: ../common/glossary.rst:3807 +msgid "Xen Cloud Platform (XCP)" +msgstr "" + +#: ../common/glossary.rst:3789 ../common/glossary.rst:3796 +#: ../common/glossary.rst:3800 ../common/glossary.rst:3803 +#: ../common/glossary.rst:3811 +msgid "Xen Storage Manager Volume Driver" +msgstr "" + +#: ../common/glossary.rst:3792 ../common/glossary.rst:3799 +#: ../common/glossary.rst:3803 ../common/glossary.rst:3806 +#: ../common/glossary.rst:3814 msgid "" -"The universal measurement of how quickly data is transferred from place to " -"place." +"A Block Storage volume plug-in that enables communication with the Xen " +"Storage Manager API." msgstr "" -#: ../common/cli_manage_images.rst:227 +#: ../common/glossary.rst:3794 ../common/glossary.rst:3801 +#: ../common/glossary.rst:3805 ../common/glossary.rst:3808 +#: ../common/glossary.rst:3816 +msgid "XenServer" +msgstr "" + +#: ../common/glossary.rst:3798 ../common/glossary.rst:3805 +#: ../common/glossary.rst:3809 ../common/glossary.rst:3812 +#: ../common/glossary.rst:3820 +msgid "XFS" +msgstr "" + +#: ../common/glossary.rst:3801 ../common/glossary.rst:3808 +#: ../common/glossary.rst:3812 ../common/glossary.rst:3815 +#: ../common/glossary.rst:3823 msgid "" -"The valid model values depend on the ``libvirt_type`` setting, as shown in " -"the following tables." +"High-performance 64-bit file system created by Silicon Graphics. Excels in " +"parallel I/O operations and data consistency." msgstr "" -#: ../common/cli_discover_version_number_for_a_client.rst:14 -msgid "The version number (2.15.0 in the example) is returned." +#: ../common/glossary.rst:3804 ../common/glossary.rst:3811 +#: ../common/glossary.rst:3815 ../common/glossary.rst:3818 +#: ../common/glossary.rst:3826 +msgid "zaqar" msgstr "" -#: ../common/log_in_dashboard.rst:42 +#: ../common/glossary.rst:3807 ../common/glossary.rst:3814 +#: ../common/glossary.rst:3818 ../common/glossary.rst:3821 +#: ../common/glossary.rst:3829 +msgid "OpenStack project that provides a message service to applications." +msgstr "" + +#: ../common/glossary.rst:3809 ../common/glossary.rst:3816 +#: ../common/glossary.rst:3820 ../common/glossary.rst:3823 +#: ../common/glossary.rst:3831 +msgid "ZeroMQ" +msgstr "" + +#: ../common/glossary.rst:3812 ../common/glossary.rst:3819 +#: ../common/glossary.rst:3823 ../common/glossary.rst:3826 +#: ../common/glossary.rst:3834 msgid "" -"The visible tabs and functions in the dashboard depend on the access " -"permissions, or roles, of the user you are logged in as." +"Message queue software supported by OpenStack. An alternative to RabbitMQ. " +"Also spelled 0MQ." msgstr "" -#: ../common/cli_manage_volumes.rst:294 +#: ../common/glossary.rst:3814 ../common/glossary.rst:3821 +#: ../common/glossary.rst:3825 ../common/glossary.rst:3828 +#: ../common/glossary.rst:3836 +msgid "Zuul" +msgstr "" + +#: ../common/glossary.rst:3817 ../common/glossary.rst:3824 +#: ../common/glossary.rst:3828 ../common/glossary.rst:3831 +#: ../common/glossary.rst:3839 msgid "" -"The volume must be in an ``available`` state or the request will be denied. " -"If the transfer request is valid in the database (that is, it has not " -"expired or been deleted), the volume is placed in an ``awaiting transfer`` " -"state. For example::" +"Tool used in OpenStack development to ensure correctly ordered testing of " +"changes in parallel." msgstr "" -#: ../common/glossary.rst:962 +#: ../common/log_in_dashboard.rst:2 +msgid "Log in to the dashboard" +msgstr "" + +#: ../common/log_in_dashboard.rst:4 msgid "" -"The web-based management interface for OpenStack. An alternative name for " -"horizon." +"The dashboard is available on the node with the ``nova-dashboard`` server " +"role." msgstr "" -#: ../common/cli_install_openstack_command_line_clients.rst:116 -msgid "Then install pip and use it to manage client installation:" -msgstr "" - -#: ../common/cli_install_openstack_command_line_clients.rst:224 -#: ../common/cli_install_openstack_command_line_clients.rst:230 -#: ../common/cli_install_openstack_command_line_clients.rst:237 -#: ../common/cli_install_openstack_command_line_clients.rst:239 -#: ../common/cli_install_openstack_command_line_clients.rst:241 -msgid "Then you can install the packages::" -msgstr "" - -#: ../common/get_started_compute.rst:143 ../common/get_started_compute.rst:142 +#: ../common/log_in_dashboard.rst:7 msgid "" -"Theoretically, OpenStack Compute can support any database that SQL-Alchemy " -"supports. Common databases are SQLite3 for test and development work, MySQL, " -"and PostgreSQL." +"Ask the cloud operator for the host name or public IP address from which you " +"can access the dashboard, and for your user name and password." msgstr "" -#: ../common/cli_install_openstack_command_line_clients.rst:96 -msgid "" -"There are also packaged versions of the clients available in `RDO `__ that enable yum to install the clients as described " -"in Installing_from_packages_." -msgstr "" - -#: ../common/cli_install_openstack_command_line_clients.rst:123 -#: ../common/cli_install_openstack_command_line_clients.rst:136 -msgid "" -"There are also packaged versions of the clients available that enable zypper " -"to install the clients as described in Installing_from_packages_." -msgstr "" - -#: ../common/get_started_identity.rst:38 ../common/get_started_identity.rst:37 -msgid "" -"These credentials are initially a user name and password, or a user name and " -"API key. When user credentials are validated, OpenStack Identity issues an " -"authentication token which the user provides in subsequent requests." -msgstr "" - -#: ../common/get_started_telemetry.rst:52 -#: ../common/get_started_telemetry.rst:51 -msgid "" -"These services communicate by using the OpenStack messaging bus. Only the " -"collector and API server have access to the data store." -msgstr "" - -#: ../common/nova_show_usage_statistics_for_hosts_instances.rst:69 -msgid "" -"These values are computed by using information about the flavors of the " -"instances that run on the hosts. This command does not query the CPU usage, " -"memory usage, or hard disk usage of the physical host." -msgstr "" - -#: ../common/support-compute.rst:60 -msgid "" -"This command triggers the Guru Meditation report to be printed to :file:`/" -"var/log/nova/nova-api-err.log`." -msgstr "" - -#: ../common/cli_manage_volumes.rst:45 -msgid "This example creates a my-new-volume volume based on an image." -msgstr "" - -#: ../common/get_started_database_service.rst:19 -#: ../common/get_started_database_service.rst:18 -msgid "This example is a high-level process flow for using Database services:" -msgstr "" - -#: ../common/glossary.rst:8 -msgid "" -"This glossary offers a list of terms and definitions to define a vocabulary " -"for OpenStack-related concepts." -msgstr "" - -#: ../common/dashboard_customizing.rst:23 -msgid "" -"This guide focuses on the :file:`local_settings.py` file, stored in :file:`/" -"openstack-dashboard/openstack_dashboard/local/`." -msgstr "" - -#: ../common/dashboard_customizing.rst:26 -msgid "" -"This guide is adapted from `How To Custom Brand The OpenStack \"Horizon\" " -"Dashboard `__." -msgstr "" - -#: ../common/support-compute.rst:157 -msgid "" -"This occurs when the Compute service attempts to retrieve the log output of " -"the instance via a serial console while the instance itself is not " -"configured to send output to the console. To rectify this, append the " -"following parameters to kernel arguments specified in the instance's boot " -"loader::" -msgstr "" - -#: ../common/get_started_with_openstack.rst:98 -#: ../common/get_started_openstack_services.rst:22 -msgid "This section describes OpenStack services in detail." -msgstr "" - -#: ../common/support-compute.rst:68 -msgid "" -"Threads: Displays stack traces and thread IDs for each of the threads within " -"the process." -msgstr "" - -#: ../common/glossary.rst:11 -msgid "" -"To add to OpenStack glossary, clone the `openstack/openstack-manuals " -"repository `__ " -"and update the source file :file:`doc/glossary/glossary-terms.xml` through " -"the OpenStack contribution process." -msgstr "" - -#: ../common/cli_set_environment_variables_using_openstack_rc.rst:117 -#: ../common/cli_set_environment_variables_using_openstack_rc.rst:118 -msgid "" -"To avoid storing the password in plain text, you can prompt for the " -"OpenStack password interactively." -msgstr "" - -#: ../common/cli_manage_images.rst:116 -msgid "To create an image, use ``glance image-create``:" -msgstr "" - -#: ../common/cli_manage_volumes.rst:213 -msgid "" -"To delete your volume, you must first detach it from the server. To detach " -"the volume from your server and check for the list of existing volumes, see " -"steps 1 and 2 in Resize_a_volume_." -msgstr "" - -#: ../common/get_started_logical_architecture.rst:6 -#: ../common/get_started_logical_architecture.rst:5 -msgid "" -"To design, deploy, and configure OpenStack, administrators must understand " -"the logical architecture." -msgstr "" - -#: ../common/support-compute.rst:194 -msgid "" -"To disable injection in libvirt, set the following in :file:`nova.conf`:" -msgstr "" - -#: ../common/support-compute.rst:219 -msgid "" -"To effectively disable the libvirt live snapshotting, until the problem is " -"resolved, configure the ``disable_libvirt_livesnapshot`` option. You can " -"turn off the live snapshotting mechanism by setting up its value to ``True`` " -"in the ``[workarounds]`` section of the :file:`nova.conf` file:" -msgstr "" - -#: ../common/cli_manage_images.rst:23 -msgid "" -"To get a list of images and to then get further details about a single " -"image, use ``glance image-list`` and ``glance image-show``." -msgstr "" - -#: ../common/cli_install_openstack_command_line_clients.rst:42 -msgid "" -"To install the clients on a Linux, Mac OS X, or Microsoft Windows system, " -"use pip. It is easy to use, ensures that you get the latest version of the " -"clients from the `Python Package Index `__, and " -"lets you update or remove the packages later on." -msgstr "" - -#: ../common/cli_install_openstack_command_line_clients.rst:42 -msgid "" -"To install the clients on a Linux, Mac OS X, or Microsoft Windows system, " -"use pip. It is easy to use, ensures that you get the latest version of the " -"clients from the `Python Package Index `__, and " -"lets you update or remove the packages later on." -msgstr "" - -#: ../common/cli_nova_evacuate.rst:17 -msgid "" -"To list hosts and find a different host for the evacuated instance, run::" -msgstr "" - -#: ../common/cli_nova_evacuate.rst:40 -msgid "" -"To preserve the user disk data on the evacuated server, deploy OpenStack " -"Compute with a shared file system. To configure your system, see `Configure " -"migrations `_ in OpenStack Cloud Administrator Guide. In the following " -"example, the password remains unchanged::" -msgstr "" - -#: ../common/cli_nova_evacuate.rst:40 -msgid "" -"To preserve the user disk data on the evacuated server, deploy OpenStack " -"Compute with a shared file system. To configure your system, see `Configure " -"migrations `_ in OpenStack Cloud " -"Administrator Guide. In the following example, the password remains " -"unchanged::" -msgstr "" - -#: ../common/cli_nova_evacuate.rst:13 -msgid "" -"To preserve user data on server disk, you must configure shared storage on " -"the target host. Also, you must validate that the current VM host is down; " -"otherwise, the evacuation fails with an error." -msgstr "" - -#: ../common/app_support.rst:19 ../common/app_support.rst:218 -#: ../common/get_started_with_openstack.rst:143 -#: ../common/get_started_feedback.rst:5 ../common/app_support.rst:215 -#: ../common/app_support.rst:17 ../common/app_support.rst:213 -#: ../common/app_support.rst:219 ../common/app_support.rst:221 -#: ../common/app_support.rst:224 ../common/app_support.rst:226 -msgid "" -"To provide feedback on documentation, join and use the openstack-docs@lists." -"openstack.org mailing list at `OpenStack Documentation Mailing List `__, or `report " -"a bug `__." -msgstr "" - -#: ../common/cli_install_openstack_command_line_clients.rst:236 -#: ../common/cli_install_openstack_command_line_clients.rst:242 -#: ../common/cli_install_openstack_command_line_clients.rst:249 -#: ../common/cli_install_openstack_command_line_clients.rst:251 -#: ../common/cli_install_openstack_command_line_clients.rst:253 -msgid "To remove the client, run the ``pip uninstall`` command::" -msgstr "" - -#: ../common/cli_manage_volumes.rst:178 -msgid "" -"To resize your volume, you must first detach it from the server. To detach " -"the volume from your server, pass the server ID and volume ID to the " -"following command:" -msgstr "" - -#: ../common/cli_set_environment_variables_using_openstack_rc.rst:5 -msgid "" -"To set the required environment variables for the OpenStack command-line " -"clients, you must create an environment file called an OpenStack rc file, " -"or :file:`openrc.sh` file. If your OpenStack installation provides it, you " -"can download the file from the OpenStack dashboard as an administrative user " -"or any other user. This project-specific environment file contains the " -"credentials that all OpenStack services use." -msgstr "" - -#: ../common/cli_manage_images.rst:91 -msgid "" -"To store location metadata for images, which enables direct file access for " -"a client, update the ``/etc/glance/glance-api.conf`` file with the following " -"statements:" -msgstr "" - -#: ../common/cli_manage_images.rst:91 -msgid "" -"To store location metadata for images, which enables direct file access for " -"a client, update the ``/etc/glance/glance.conf`` file with the following " -"statements:" -msgstr "" - -#: ../common/support-compute.rst:123 -msgid "" -"To troubleshoot other possible problems with an instance, such as an " -"instance that stays in a spawning state, check the directory for the " -"particular instance under :file:`/var/lib/nova/instances` on the ``nova-" -"compute`` host and make sure that these files are present:" -msgstr "" - -#: ../common/get_started_identity.rst:17 ../common/get_started_identity.rst:16 -msgid "" -"To understand OpenStack Identity, you must understand the following concepts:" -msgstr "" - -#: ../common/cli_manage_images.rst:122 -msgid "To update an image by name or ID, use ``glance image-update``:" -msgstr "" - -#: ../common/cli_install_openstack_command_line_clients.rst:231 -#: ../common/cli_install_openstack_command_line_clients.rst:237 -#: ../common/cli_install_openstack_command_line_clients.rst:244 -#: ../common/cli_install_openstack_command_line_clients.rst:246 -#: ../common/cli_install_openstack_command_line_clients.rst:248 -msgid "" -"To upgrade a client, add the ``--upgrade`` option to the ``pip install`` " -"command::" +#: ../common/log_in_dashboard.rst:11 +msgid "Open a web browser that has JavaScript and cookies enabled." msgstr "" #: ../common/log_in_dashboard.rst:15 @@ -9684,797 +12612,502 @@ msgid "" "support>`__." msgstr "" -#: ../common/cli_manage_volumes.rst:98 +#: ../common/log_in_dashboard.rst:22 msgid "" -"To verify that your volume was created successfully, list the available " -"volumes::" +"In the address bar, enter the host name or IP address for the dashboard." msgstr "" -#: ../common/dashboard_customizing.rst:106 +#: ../common/log_in_dashboard.rst:31 msgid "" -"To view your changes reload your dashboard. If necessary go back and modify " -"your CSS file as appropriate." +"If a certificate warning appears when you try to access the URL for the " +"first time, a self-signed certificate is in use, which is not considered " +"trustworthy by default. Verify the certificate or add an exception in the " +"browser to bypass the warning." msgstr "" -#: ../common/get_started_identity.rst:51 ../common/get_started_identity.rst:50 -msgid "Token" -msgstr "" - -#: ../common/glossary.rst:254 +#: ../common/log_in_dashboard.rst:36 msgid "" -"Tool used for maintaining Address Resolution Protocol packet filter rules in " -"the Linux kernel firewall modules. Used along with iptables, ebtables, and " -"ip6tables in Compute to provide firewall services for VMs." +"On the Log In page, enter your user name and password, and click :guilabel:" +"`Sign In`." msgstr "" -#: ../common/glossary.rst:3817 ../common/glossary.rst:3824 -#: ../common/glossary.rst:3831 ../common/glossary.rst:3839 -#: ../common/glossary.rst:3828 +#: ../common/log_in_dashboard.rst:39 msgid "" -"Tool used in OpenStack development to ensure correctly ordered testing of " -"changes in parallel." +"The top of the window displays your user name. You can also access settings " +"or sign out of the dashboard." msgstr "" -#: ../common/glossary.rst:2040 ../common/glossary.rst:2046 -msgid "Tool used to run jobs automatically for OpenStack development." -msgstr "" - -#: ../common/glossary.rst:1988 ../common/glossary.rst:1994 +#: ../common/log_in_dashboard.rst:42 msgid "" -"Tool used to set up, maintain, and inspect the tables of IPv6 packet filter " -"rules in the Linux kernel. In OpenStack Compute, ip6tables is used along " -"with arptables, ebtables, and iptables to create firewalls for both nodes " -"and VMs." +"The visible tabs and functions in the dashboard depend on the access " +"permissions, or roles, of the user you are logged in as." msgstr "" -#: ../common/glossary.rst:3490 ../common/glossary.rst:3497 -#: ../common/glossary.rst:3504 ../common/glossary.rst:3512 -#: ../common/glossary.rst:3501 -msgid "Torpedo" -msgstr "" - -#: ../common/get_started_identity.rst:8 ../common/get_started_identity.rst:7 -msgid "Tracking users and their permissions." -msgstr "" - -#: ../common/cli_manage_volumes.rst:251 -msgid "Transfer a volume" -msgstr "" - -#: ../common/glossary.rst:3517 ../common/glossary.rst:3524 -#: ../common/glossary.rst:3531 ../common/glossary.rst:3539 -#: ../common/glossary.rst:3528 -msgid "TripleO" -msgstr "" - -#: ../common/support-compute.rst:7 -msgid "Troubleshoot Compute" -msgstr "" - -#: ../common/cli_manage_images.rst:284 -msgid "Troubleshoot image creation" -msgstr "" - -#: ../common/glossary.rst:3060 ../common/glossary.rst:3067 -#: ../common/glossary.rst:3074 ../common/glossary.rst:3076 -#: ../common/glossary.rst:3065 +#: ../common/log_in_dashboard.rst:45 msgid "" -"Type of Compute scheduler that evenly distributes instances among available " -"hosts." +"If you are logged in as an end user, the :guilabel:`Project` tab (:ref:" +"`dashboard-project-tab`) and :guilabel:`Identity` tab (:ref:`dashboard-" +"identity-tab`) are displayed." msgstr "" -#: ../common/glossary.rst:1504 ../common/glossary.rst:1505 -msgid "UUID for each Compute or Image service VM flavor or instance type." -msgstr "" - -#: ../common/glossary.rst:1867 ../common/glossary.rst:1873 -msgid "UUID used by Image service to uniquely identify each VM image." -msgstr "" - -#: ../common/glossary.rst:3527 ../common/glossary.rst:3534 -#: ../common/glossary.rst:3541 ../common/glossary.rst:3549 -#: ../common/glossary.rst:3538 -msgid "Ubuntu" -msgstr "" - -#: ../common/glossary.rst:906 +#: ../common/log_in_dashboard.rst:45 msgid "" -"Under the Compute distributed scheduler, this is calculated by looking at " -"the capabilities of each host relative to the flavor of the VM instance " -"being requested." +"If you are logged in as an end user, the :guilabel:`Project` tab is " +"displayed." msgstr "" -#: ../common/glossary.rst:3717 ../common/glossary.rst:3724 -#: ../common/glossary.rst:3731 ../common/glossary.rst:3739 -#: ../common/glossary.rst:3728 +#: ../common/log_in_dashboard.rst:48 msgid "" -"Unique ID applied to each storage volume under the Block Storage control." +"If you are logged in as an administrator, the :guilabel:`Project` tab (:ref:" +"`dashboard-project-tab`) and :guilabel:`Admin` tab (:ref:`dashboard-admin-" +"tab`) are displayed." msgstr "" -#: ../common/glossary.rst:3560 ../common/glossary.rst:3567 -#: ../common/glossary.rst:3574 ../common/glossary.rst:3582 -#: ../common/glossary.rst:3571 -msgid "Unique ID assigned to each Networking VIF." -msgstr "" - -#: ../common/glossary.rst:3498 ../common/glossary.rst:3505 -#: ../common/glossary.rst:3512 ../common/glossary.rst:3520 -#: ../common/glossary.rst:3509 +#: ../common/log_in_dashboard.rst:49 msgid "" -"Unique ID assigned to each Object Storage request; used for debugging and " -"tracing." +"If you are logged in as an administrator, the :guilabel:`Project` tab (:ref:" +"`dashboard-project-tab`) and :guilabel:`Admin` tab (:ref:`dashboard-admin-" +"tab`) and :guilabel:`Identity` tab (:ref:`dashboard-identity-tab`) are " +"displayed." msgstr "" -#: ../common/glossary.rst:1921 ../common/glossary.rst:3166 -#: ../common/glossary.rst:3173 ../common/glossary.rst:1927 -#: ../common/glossary.rst:3180 ../common/glossary.rst:3188 -#: ../common/glossary.rst:3177 -msgid "Unique ID assigned to each guest VM instance." +#: ../common/log_in_dashboard.rst:56 ../common/log_in_dashboard.rst:58 +msgid "OpenStack dashboard—:guilabel:`Project` tab" msgstr "" -#: ../common/glossary.rst:2391 ../common/glossary.rst:2398 -#: ../common/glossary.rst:2397 ../common/glossary.rst:2403 -#: ../common/glossary.rst:2404 ../common/glossary.rst:2393 +#: ../common/log_in_dashboard.rst:58 ../common/log_in_dashboard.rst:60 msgid "" -"Unique ID assigned to each network segment within Networking. Same as " -"network UUID." +"Projects are organizational units in the cloud, and are also known as " +"tenants or accounts. Each user is a member of one or more projects. Within a " +"project, a user creates and manages instances." msgstr "" -#: ../common/glossary.rst:3003 ../common/glossary.rst:3010 -#: ../common/glossary.rst:3017 ../common/glossary.rst:3019 -#: ../common/glossary.rst:3008 -msgid "Unique ID assigned to each request sent to Compute." -msgstr "" - -#: ../common/glossary.rst:3180 ../common/glossary.rst:3187 -#: ../common/glossary.rst:3194 ../common/glossary.rst:3202 -#: ../common/glossary.rst:3191 +#: ../common/log_in_dashboard.rst:62 ../common/log_in_dashboard.rst:64 msgid "" -"Unique ID assigned to each service that is available in the Identity service " -"catalog." +"From the :guilabel:`Project` tab, you can view and manage the resources in a " +"selected project, including instances and images. You select the project " +"from the CURRENT PROJECT list at the top of the tab." msgstr "" -#: ../common/glossary.rst:3467 ../common/glossary.rst:3474 -#: ../common/glossary.rst:3481 ../common/glossary.rst:3489 -#: ../common/glossary.rst:3478 +#: ../common/log_in_dashboard.rst:68 ../common/log_in_dashboard.rst:70 +msgid "**Figure: Project tab**" +msgstr "" + +#: ../common/log_in_dashboard.rst:70 ../common/log_in_dashboard.rst:72 +#: ../common/log_in_dashboard.rst:74 +msgid "From the :guilabel:`Project` tab, you can access the following tabs:" +msgstr "" + +#: ../common/log_in_dashboard.rst:72 +msgid ":guilabel:`Project` tab" +msgstr "" + +#: ../common/log_in_dashboard.rst:74 ../common/log_in_dashboard.rst:76 +#: ../common/log_in_dashboard.rst:78 +msgid ":guilabel:`Compute` tab" +msgstr "" + +#: ../common/log_in_dashboard.rst:76 ../common/log_in_dashboard.rst:78 +#: ../common/log_in_dashboard.rst:80 +msgid ":guilabel:`Overview`: View reports for the project." +msgstr "" + +#: ../common/log_in_dashboard.rst:78 ../common/log_in_dashboard.rst:80 +#: ../common/log_in_dashboard.rst:82 msgid "" -"Unique ID assigned to each tenant within the Identity service. The project " -"IDs map to the tenant IDs." +":guilabel:`Instances`: View, launch, create a snapshot from, stop, pause, or " +"reboot instances, or connect to them through VNC." msgstr "" -#: ../common/glossary.rst:1930 ../common/glossary.rst:1936 -msgid "Unique ID for a Networking VIF or vNIC in the form of a UUID." +#: ../common/log_in_dashboard.rst:81 ../common/log_in_dashboard.rst:83 +#: ../common/log_in_dashboard.rst:85 ../common/log_in_dashboard.rst:168 +#: ../common/log_in_dashboard.rst:169 ../common/log_in_dashboard.rst:170 +msgid ":guilabel:`Volumes`: Use the following tabs to complete these tasks:" msgstr "" -#: ../common/glossary.rst:2415 ../common/glossary.rst:2422 -#: ../common/glossary.rst:2421 ../common/glossary.rst:2427 -#: ../common/glossary.rst:2429 ../common/glossary.rst:2418 -msgid "Unique ID for a Networking network segment." +#: ../common/log_in_dashboard.rst:83 ../common/log_in_dashboard.rst:85 +#: ../common/log_in_dashboard.rst:87 +msgid ":guilabel:`Volumes`: View, create, edit, and delete volumes." msgstr "" -#: ../common/glossary.rst:2726 ../common/glossary.rst:2733 -#: ../common/glossary.rst:2739 ../common/glossary.rst:2741 -#: ../common/glossary.rst:2730 -msgid "Unique ID for a Networking port." -msgstr "" - -#: ../common/glossary.rst:1771 ../common/glossary.rst:1777 +#: ../common/log_in_dashboard.rst:85 ../common/log_in_dashboard.rst:87 +#: ../common/log_in_dashboard.rst:89 msgid "" -"Unique numeric ID associated with each user in Identity, conceptually " -"similar to a Linux or LDAP UID." +":guilabel:`Volume Snapshots`: View, create, edit, and delete volume " +"snapshots." msgstr "" -#: ../common/glossary.rst:2519 ../common/glossary.rst:2526 -#: ../common/glossary.rst:2525 ../common/glossary.rst:2531 -#: ../common/glossary.rst:2533 ../common/glossary.rst:2522 -msgid "Uniquely ID for an Object Storage object." -msgstr "" - -#: ../common/cli_install_openstack_command_line_clients.rst:229 -#: ../common/cli_install_openstack_command_line_clients.rst:235 -#: ../common/cli_install_openstack_command_line_clients.rst:242 -#: ../common/cli_install_openstack_command_line_clients.rst:244 -#: ../common/cli_install_openstack_command_line_clients.rst:246 -msgid "Upgrade or remove clients" -msgstr "" - -#: ../common/dashboard_customizing.rst:37 +#: ../common/log_in_dashboard.rst:88 ../common/log_in_dashboard.rst:90 +#: ../common/log_in_dashboard.rst:92 msgid "" -"Upload your new images to :file:`/usr/share/openstack-dashboard/" -"openstack_dashboard/static/dashboard/img/`." +":guilabel:`Images`: View images and instance snapshots created by project " +"users, plus any images that are publicly available. Create, edit, and delete " +"images, and launch instances from images and snapshots." msgstr "" -#: ../common/support-compute.rst:165 +#: ../common/log_in_dashboard.rst:92 ../common/log_in_dashboard.rst:94 +#: ../common/log_in_dashboard.rst:96 msgid "" -"Upon rebooting, the instance will be configured to send output to the " -"Compute service." +":guilabel:`Access & Security`: Use the following tabs to complete these " +"tasks:" msgstr "" -#: ../common/get_started_compute.rst:6 ../common/get_started_compute.rst:5 +#: ../common/log_in_dashboard.rst:94 ../common/log_in_dashboard.rst:96 +#: ../common/log_in_dashboard.rst:98 msgid "" -"Use OpenStack Compute to host and manage cloud computing systems. OpenStack " -"Compute is a major part of an Infrastructure-as-a-Service (IaaS) system. The " -"main modules are implemented in Python." +":guilabel:`Security Groups`: View, create, edit, and delete security groups " +"and security group rules." msgstr "" -#: ../common/cli_manage_volumes.rst:264 -msgid "Use cases include:" -msgstr "" - -#: ../common/cli_install_openstack_command_line_clients.rst:183 +#: ../common/log_in_dashboard.rst:97 ../common/log_in_dashboard.rst:99 +#: ../common/log_in_dashboard.rst:101 msgid "" -"Use pip to install the OpenStack clients on a Linux, Mac OS X, or Microsoft " -"Windows system. It is easy to use and ensures that you get the latest " -"version of the client from the `Python Package Index `__. Also, pip enables you to update or remove a package." +":guilabel:`Key Pairs`: View, create, edit, import, and delete key pairs." msgstr "" -#: ../common/cli_install_openstack_command_line_clients.rst:183 -#: ../common/cli_install_openstack_command_line_clients.rst:189 -#: ../common/cli_install_openstack_command_line_clients.rst:191 -#: ../common/cli_install_openstack_command_line_clients.rst:193 -#: ../common/cli_install_openstack_command_line_clients.rst:195 +#: ../common/log_in_dashboard.rst:99 ../common/log_in_dashboard.rst:101 +#: ../common/log_in_dashboard.rst:103 msgid "" -"Use pip to install the OpenStack clients on a Linux, Mac OS X, or Microsoft " -"Windows system. It is easy to use and ensures that you get the latest " -"version of the client from the `Python Package Index `__. Also, pip enables you to update or remove a package." +":guilabel:`Floating IPs`: Allocate an IP address to or release it from a " +"project." msgstr "" -#: ../common/get_started_database_service.rst:35 -#: ../common/get_started_database_service.rst:34 +#: ../common/log_in_dashboard.rst:102 ../common/log_in_dashboard.rst:104 +#: ../common/log_in_dashboard.rst:106 +msgid ":guilabel:`API Access`: View API endpoints." +msgstr "" + +#: ../common/log_in_dashboard.rst:106 ../common/log_in_dashboard.rst:108 +#: ../common/log_in_dashboard.rst:110 +msgid ":guilabel:`Network` tab" +msgstr "" + +#: ../common/log_in_dashboard.rst:108 ../common/log_in_dashboard.rst:110 +#: ../common/log_in_dashboard.rst:112 +msgid ":guilabel:`Network Topology`: View the network topology." +msgstr "" + +#: ../common/log_in_dashboard.rst:110 ../common/log_in_dashboard.rst:112 +#: ../common/log_in_dashboard.rst:114 +msgid ":guilabel:`Networks`: Create and manage public and private networks." +msgstr "" + +#: ../common/log_in_dashboard.rst:112 ../common/log_in_dashboard.rst:114 +#: ../common/log_in_dashboard.rst:116 +msgid ":guilabel:`Routers`: Create and manage routers." +msgstr "" + +#: ../common/log_in_dashboard.rst:116 ../common/log_in_dashboard.rst:118 +#: ../common/log_in_dashboard.rst:120 +msgid ":guilabel:`Object Store` tab" +msgstr "" + +#: ../common/log_in_dashboard.rst:116 +msgid ":guilabel:`Routers`: Create and manage subnets." +msgstr "" + +#: ../common/log_in_dashboard.rst:118 ../common/log_in_dashboard.rst:120 +#: ../common/log_in_dashboard.rst:122 +msgid ":guilabel:`Containers`: Create and manage containers and objects." +msgstr "" + +#: ../common/log_in_dashboard.rst:122 ../common/log_in_dashboard.rst:124 +#: ../common/log_in_dashboard.rst:126 +msgid ":guilabel:`Orchestration` tab" +msgstr "" + +#: ../common/log_in_dashboard.rst:124 ../common/log_in_dashboard.rst:126 +#: ../common/log_in_dashboard.rst:128 msgid "" -"Use the :command:`trove list` command to get the ID of the instance, " -"followed by the :command:`trove show` command to get the IP address of it." +":guilabel:`Stacks`: Use the REST API to orchestrate multiple composite cloud " +"applications." msgstr "" -#: ../common/get_started_database_service.rst:27 -#: ../common/get_started_database_service.rst:26 +#: ../common/log_in_dashboard.rst:127 ../common/log_in_dashboard.rst:129 +#: ../common/log_in_dashboard.rst:131 msgid "" -"Use the ``trove-manage`` command to import images and offer them to tenants." +":guilabel:`Resource Types`: Show a list of all the supported resource types " +"for HOT templates." msgstr "" -#: ../common/glossary.rst:1276 ../common/glossary.rst:1277 +#: ../common/log_in_dashboard.rst:133 ../common/log_in_dashboard.rst:134 +#: ../common/log_in_dashboard.rst:135 ../common/log_in_dashboard.rst:137 +msgid "OpenStack dashboard—:guilabel:`Admin` tab" +msgstr "" + +#: ../common/log_in_dashboard.rst:135 ../common/log_in_dashboard.rst:136 +#: ../common/log_in_dashboard.rst:139 msgid "" -"Used along with an EC2 access key when communicating with the Compute EC2 " -"API; used to digitally sign each request." +"Administrative users can use the :guilabel:`Admin` tab to view usage and to " +"manage instances, volumes, flavors, images, projects, users, services, and " +"quotas." msgstr "" -#: ../common/glossary.rst:1261 ../common/glossary.rst:1262 -msgid "Used along with an EC2 secret key to access the Compute EC2 API." -msgstr "" - -#: ../common/glossary.rst:1371 ../common/glossary.rst:1372 -msgid "Used along with an EKI to create an EMI." -msgstr "" - -#: ../common/glossary.rst:1363 ../common/glossary.rst:1364 -msgid "Used along with an ERI to create an EMI." -msgstr "" - -#: ../common/glossary.rst:2002 ../common/glossary.rst:2008 +#: ../common/log_in_dashboard.rst:135 ../common/log_in_dashboard.rst:137 msgid "" -"Used along with arptables and ebtables, iptables create firewalls in " -"Compute. iptables are the tables provided by the Linux kernel firewall " -"(implemented as different Netfilter modules) and the chains and rules it " -"stores. Different kernel modules and programs are currently used for " -"different protocols: iptables applies to IPv4, ip6tables to IPv6, arptables " -"to ARP, and ebtables to Ethernet frames. Requires root privilege to " -"manipulate." +"Administrative users can use the :guilabel:`Admin` tab to view usage and to " +"manage instances, volumes, flavors, images, services, and quotas." msgstr "" -#: ../common/glossary.rst:1821 ../common/glossary.rst:1827 +#: ../common/log_in_dashboard.rst:141 ../common/log_in_dashboard.rst:142 +#: ../common/log_in_dashboard.rst:143 ../common/log_in_dashboard.rst:146 +msgid "**Figure: Admin tab**" +msgstr "" + +#: ../common/log_in_dashboard.rst:143 ../common/log_in_dashboard.rst:144 +#: ../common/log_in_dashboard.rst:145 msgid "" -"Used by Image service to obtain images on the local host rather than re-" -"downloading them from the image server each time one is requested." +"From the :guilabel:`Admin` tab, you can access the following category to " +"complete these tasks:" msgstr "" -#: ../common/glossary.rst:3752 ../common/glossary.rst:3759 -#: ../common/glossary.rst:3766 ../common/glossary.rst:3774 -#: ../common/glossary.rst:3763 +#: ../common/log_in_dashboard.rst:148 ../common/log_in_dashboard.rst:151 +msgid ":guilabel:`Admin` tab" +msgstr "" + +#: ../common/log_in_dashboard.rst:148 ../common/log_in_dashboard.rst:149 +#: ../common/log_in_dashboard.rst:150 +msgid ":guilabel:`System` tab" +msgstr "" + +#: ../common/log_in_dashboard.rst:149 ../common/log_in_dashboard.rst:154 +#: ../common/log_in_dashboard.rst:157 +msgid ":guilabel:`System Panel` tab" +msgstr "" + +#: ../common/log_in_dashboard.rst:150 ../common/log_in_dashboard.rst:151 +#: ../common/log_in_dashboard.rst:152 ../common/log_in_dashboard.rst:156 +#: ../common/log_in_dashboard.rst:159 +msgid ":guilabel:`Overview`: View basic reports." +msgstr "" + +#: ../common/log_in_dashboard.rst:150 ../common/log_in_dashboard.rst:153 +msgid "Access the following categories to complete these tasks:" +msgstr "" + +#: ../common/log_in_dashboard.rst:152 ../common/log_in_dashboard.rst:153 +#: ../common/log_in_dashboard.rst:154 ../common/log_in_dashboard.rst:158 +#: ../common/log_in_dashboard.rst:161 msgid "" -"Used by Object Storage devices to determine which storage devices are " -"suitable for the job. Devices are weighted by size." +":guilabel:`Resource Usage`: Use the following tabs to view the following " +"usages:" msgstr "" -#: ../common/glossary.rst:2523 ../common/glossary.rst:2530 -#: ../common/glossary.rst:2529 ../common/glossary.rst:2535 -#: ../common/glossary.rst:2537 ../common/glossary.rst:2526 +#: ../common/log_in_dashboard.rst:155 ../common/log_in_dashboard.rst:156 +#: ../common/log_in_dashboard.rst:157 ../common/log_in_dashboard.rst:164 +msgid ":guilabel:`Usage Report`: View the usage report." +msgstr "" + +#: ../common/log_in_dashboard.rst:157 ../common/log_in_dashboard.rst:158 +#: ../common/log_in_dashboard.rst:159 ../common/log_in_dashboard.rst:163 +#: ../common/log_in_dashboard.rst:166 +msgid ":guilabel:`Stats`: View the statistics of all resources." +msgstr "" + +#: ../common/log_in_dashboard.rst:159 ../common/log_in_dashboard.rst:160 +#: ../common/log_in_dashboard.rst:161 ../common/log_in_dashboard.rst:165 +#: ../common/log_in_dashboard.rst:168 +msgid ":guilabel:`Hypervisors`: View the hypervisor summary." +msgstr "" + +#: ../common/log_in_dashboard.rst:161 ../common/log_in_dashboard.rst:164 +msgid ":guilabel:`Daily Report`: View the daily report." +msgstr "" + +#: ../common/log_in_dashboard.rst:161 ../common/log_in_dashboard.rst:162 +#: ../common/log_in_dashboard.rst:163 ../common/log_in_dashboard.rst:167 +#: ../common/log_in_dashboard.rst:170 msgid "" -"Used by Object Storage to determine the location of an object in the ring. " -"Maps objects to partitions." +":guilabel:`Host Aggregates`: View, create, and edit host aggregates. View " +"the list of availability zones." msgstr "" -#: ../common/glossary.rst:2656 ../common/glossary.rst:2663 -#: ../common/glossary.rst:2669 ../common/glossary.rst:2671 -#: ../common/glossary.rst:2660 +#: ../common/log_in_dashboard.rst:164 ../common/log_in_dashboard.rst:165 +#: ../common/log_in_dashboard.rst:166 ../common/log_in_dashboard.rst:170 +#: ../common/log_in_dashboard.rst:173 msgid "" -"Used by Object Storage to determine which partition data should reside on." +":guilabel:`Instances`: View, pause, resume, suspend, migrate, soft or hard " +"reboot, and delete running instances that belong to users of some, but not " +"all, projects. Also, view the log for an instance or access an instance " +"through VNC." msgstr "" -#: ../common/glossary.rst:3082 ../common/glossary.rst:3089 -#: ../common/glossary.rst:3096 ../common/glossary.rst:3098 -#: ../common/glossary.rst:3087 -msgid "Used by Object Storage to push object replicas." -msgstr "" - -#: ../common/get_started_openstack_networking.rst:29 -#: ../common/get_started_openstack_networking.rst:28 +#: ../common/log_in_dashboard.rst:169 ../common/log_in_dashboard.rst:174 +#: ../common/log_in_dashboard.rst:177 msgid "" -"Used by most OpenStack Networking installations to route information between " -"the neutron-server and various agents, as well as a database to store " -"networking state for particular plug-ins." +":guilabel:`Volumes`: View, create, edit, and delete volumes and volume types." msgstr "" -#: ../common/get_started_storage_concepts.rst:16 -#: ../common/get_started_storage_concepts.rst:15 -msgid "Used for adding additional persistent storage to a virtual machine (VM)" +#: ../common/log_in_dashboard.rst:170 ../common/log_in_dashboard.rst:171 +#: ../common/log_in_dashboard.rst:172 +msgid ":guilabel:`Volumes`: View, create, manage, and delete volumes." msgstr "" -#: ../common/get_started_storage_concepts.rst:17 -#: ../common/get_started_storage_concepts.rst:16 -msgid "Used for storing virtual machine images and data" -msgstr "" - -#: ../common/glossary.rst:1250 ../common/glossary.rst:1251 +#: ../common/log_in_dashboard.rst:171 ../common/log_in_dashboard.rst:176 +#: ../common/log_in_dashboard.rst:177 ../common/log_in_dashboard.rst:178 +#: ../common/log_in_dashboard.rst:179 msgid "" -"Used in Compute along with arptables, iptables, and ip6tables to create " -"firewalls and to ensure isolation of network communications." +":guilabel:`Flavors`: View, create, edit, view extra specifications for, and " +"delete flavors. A flavor is size of an instance." msgstr "" -#: ../common/glossary.rst:3482 ../common/glossary.rst:3489 -#: ../common/glossary.rst:3496 ../common/glossary.rst:3504 -#: ../common/glossary.rst:3493 +#: ../common/log_in_dashboard.rst:172 ../common/log_in_dashboard.rst:173 +#: ../common/log_in_dashboard.rst:174 msgid "" -"Used to mark Object Storage objects that have been deleted; ensures that the " -"object is not updated on another node after it has been deleted." +":guilabel:`Volume Types`: View, create, manage, and delete volume types." msgstr "" -#: ../common/glossary.rst:1457 ../common/glossary.rst:1458 +#: ../common/log_in_dashboard.rst:174 ../common/log_in_dashboard.rst:179 +#: ../common/log_in_dashboard.rst:180 ../common/log_in_dashboard.rst:181 +#: ../common/log_in_dashboard.rst:182 msgid "" -"Used to restrict communications between hosts and/or nodes, implemented in " -"Compute using iptables, arptables, ip6tables, and etables." +":guilabel:`Images`: View, create, edit properties for, and delete custom " +"images." msgstr "" -#: ../common/glossary.rst:2206 ../common/glossary.rst:2212 -#: ../common/glossary.rst:2201 -msgid "Used to track segments of a large object within Object Storage." -msgstr "" - -#: ../common/get_started_identity.rst:26 ../common/get_started_identity.rst:25 -msgid "User" -msgstr "" - -#: ../common/glossary.rst:3553 ../common/glossary.rst:3560 -#: ../common/glossary.rst:3567 ../common/glossary.rst:3575 -#: ../common/glossary.rst:3564 -msgid "User Mode Linux (UML)" -msgstr "" - -#: ../common/glossary.rst:2761 ../common/glossary.rst:2768 -#: ../common/glossary.rst:2775 ../common/glossary.rst:2777 -#: ../common/glossary.rst:2766 -msgid "User-defined alphanumeric string in Compute; the name of a project." -msgstr "" - -#: ../common/get_started_sahara.rst:41 ../common/get_started_sahara.rst:42 -msgid "User-friendly UI for ad-hoc analytics queries based on Hive or Pig." -msgstr "" - -#: ../common/get_started_logical_architecture.rst:26 +#: ../common/log_in_dashboard.rst:174 ../common/log_in_dashboard.rst:175 +#: ../common/log_in_dashboard.rst:176 msgid "" -"Users can access OpenStack via the web-based user interface implemented by " -"the :ref:`get_started_dashboard`, via `command-line clients `__ and by issuing API requests through " -"tools like browser plug-ins or :command:`curl`. For applications, `several " -"SDKs `__ are available. Ultimately, all " -"these access methods issue REST API calls to the various OpenStack services." +":guilabel:`Volume Snapshots`: View, manage, and delete volume snapshots." msgstr "" -#: ../common/get_started_logical_architecture.rst:29 +#: ../common/log_in_dashboard.rst:177 ../common/log_in_dashboard.rst:182 +#: ../common/log_in_dashboard.rst:183 ../common/log_in_dashboard.rst:184 +#: ../common/log_in_dashboard.rst:185 msgid "" -"Users can access OpenStack via the web-based user interface implemented by " -"the OpenStack dashboard, via `command-line clients `__ and by issuing API requests through tools like " -"browser plug-ins or :command:`curl`. For applications, `several SDKs `__ are available. Ultimately, all these access " -"methods issue REST API calls to the various OpenStack services." +":guilabel:`Networks`: View, create, edit properties for, and delete networks." msgstr "" -#: ../common/glossary.rst:2793 ../common/glossary.rst:2800 -#: ../common/glossary.rst:2807 ../common/glossary.rst:2809 -#: ../common/glossary.rst:2798 +#: ../common/log_in_dashboard.rst:179 ../common/log_in_dashboard.rst:184 +#: ../common/log_in_dashboard.rst:185 ../common/log_in_dashboard.rst:186 +#: ../common/log_in_dashboard.rst:187 msgid "" -"Users of Object Storage interact with the service through the proxy server, " -"which in turn looks up the location of the requested data within the ring " -"and returns the results to the user." +":guilabel:`Routers`: View, create, edit properties for, and delete routers." msgstr "" -#: ../common/get_started_sahara.rst:19 ../common/get_started_sahara.rst:20 +#: ../common/log_in_dashboard.rst:181 ../common/log_in_dashboard.rst:186 +#: ../common/log_in_dashboard.rst:187 ../common/log_in_dashboard.rst:188 +#: ../common/log_in_dashboard.rst:189 msgid "" -"Utilization of unused compute power from general purpose OpenStack IaaS " -"cloud." +":guilabel:`Defaults`: View default quota values. Quotas are hard-coded in " +"OpenStack Compute and define the maximum allowable size and number of " +"resources." msgstr "" -#: ../common/glossary.rst:3557 ../common/glossary.rst:3564 -#: ../common/glossary.rst:3571 ../common/glossary.rst:3579 -#: ../common/glossary.rst:3568 -msgid "VIF UUID" -msgstr "" - -#: ../common/glossary.rst:3561 ../common/glossary.rst:3568 -#: ../common/glossary.rst:3575 ../common/glossary.rst:3583 -#: ../common/glossary.rst:3572 -msgid "VIP" -msgstr "" - -#: ../common/glossary.rst:3654 ../common/glossary.rst:3661 -#: ../common/glossary.rst:3668 ../common/glossary.rst:3676 -#: ../common/glossary.rst:3665 -msgid "VLAN manager" -msgstr "" - -#: ../common/glossary.rst:3659 ../common/glossary.rst:3666 -#: ../common/glossary.rst:3673 ../common/glossary.rst:3681 -#: ../common/glossary.rst:3670 -msgid "VLAN network" -msgstr "" - -#: ../common/glossary.rst:3677 ../common/glossary.rst:3684 -#: ../common/glossary.rst:3691 ../common/glossary.rst:3699 -#: ../common/glossary.rst:3688 -msgid "VM Remote Control (VMRC)" -msgstr "" - -#: ../common/glossary.rst:3668 ../common/glossary.rst:3675 -#: ../common/glossary.rst:3682 ../common/glossary.rst:3690 -#: ../common/glossary.rst:3679 -msgid "VM disk (VMDK)" -msgstr "" - -#: ../common/glossary.rst:3673 ../common/glossary.rst:3680 -#: ../common/glossary.rst:3687 ../common/glossary.rst:3695 -#: ../common/glossary.rst:3684 -msgid "VM image" -msgstr "" - -#: ../common/glossary.rst:1367 ../common/glossary.rst:1368 -msgid "VM image container format supported by Image service." -msgstr "" - -#: ../common/glossary.rst:3682 ../common/glossary.rst:3689 -#: ../common/glossary.rst:3696 ../common/glossary.rst:3704 -#: ../common/glossary.rst:3693 -msgid "VMware API" -msgstr "" - -#: ../common/glossary.rst:3686 ../common/glossary.rst:3693 -#: ../common/glossary.rst:3700 ../common/glossary.rst:3708 -#: ../common/glossary.rst:3697 -msgid "VMware NSX Neutron plug-in" -msgstr "" - -#: ../common/get_started_compute.rst:47 ../common/get_started_compute.rst:46 -msgid "VMwareAPI for VMware" -msgstr "" - -#: ../common/glossary.rst:3690 ../common/glossary.rst:3697 -#: ../common/glossary.rst:3704 ../common/glossary.rst:3712 -#: ../common/glossary.rst:3701 -msgid "VNC proxy" -msgstr "" - -#: ../common/glossary.rst:3602 ../common/glossary.rst:3591 -msgid "VXLAN" -msgstr "" - -#: ../common/get_started_object_storage.rst:31 -#: ../common/get_started_object_storage.rst:30 -msgid "Various periodic processes" -msgstr "" - -#: ../common/get_started_image_service.rst:38 -#: ../common/get_started_image_service.rst:35 +#: ../common/log_in_dashboard.rst:185 ../common/log_in_dashboard.rst:190 +#: ../common/log_in_dashboard.rst:191 ../common/log_in_dashboard.rst:192 +#: ../common/log_in_dashboard.rst:193 msgid "" -"Various repository types are supported including normal file systems, Object " -"Storage, RADOS block devices, HTTP, and Amazon S3. Note that some " -"repositories will only support read-only usage." +":guilabel:`Metadata Definitions`: Import namespace and view the metadata " +"information." msgstr "" -#: ../common/cli_manage_volumes.rst:421 +#: ../common/log_in_dashboard.rst:186 ../common/log_in_dashboard.rst:189 msgid "" -"Verify that transfer list is now empty and that the volume is again " -"available for transfer::" +":guilabel:`System Info`: Use the following tabs to view the service " +"information:" msgstr "" -#: ../common/cli_manage_volumes.rst:330 -msgid "View pending transfers::" -msgstr "" - -#: ../common/glossary.rst:3570 ../common/glossary.rst:3577 -#: ../common/glossary.rst:3584 ../common/glossary.rst:3592 -#: ../common/glossary.rst:3581 -msgid "Virtual Central Processing Unit (vCPU)" -msgstr "" - -#: ../common/glossary.rst:3575 ../common/glossary.rst:3582 -#: ../common/glossary.rst:3589 ../common/glossary.rst:3597 -#: ../common/glossary.rst:3586 -msgid "Virtual Disk Image (VDI)" -msgstr "" - -#: ../common/glossary.rst:3587 ../common/glossary.rst:3594 -#: ../common/glossary.rst:3601 ../common/glossary.rst:3609 -#: ../common/glossary.rst:3598 -msgid "Virtual Hard Disk (VHD)" -msgstr "" - -#: ../common/glossary.rst:3616 ../common/glossary.rst:3623 -#: ../common/glossary.rst:3630 ../common/glossary.rst:3638 -#: ../common/glossary.rst:3627 -msgid "Virtual Network Computing (VNC)" -msgstr "" - -#: ../common/glossary.rst:3621 ../common/glossary.rst:3628 -#: ../common/glossary.rst:3635 ../common/glossary.rst:3643 -#: ../common/glossary.rst:3632 -msgid "Virtual Network InterFace (VIF)" -msgstr "" - -#: ../common/glossary.rst:1487 ../common/glossary.rst:1488 +#: ../common/log_in_dashboard.rst:188 ../common/log_in_dashboard.rst:189 +#: ../common/log_in_dashboard.rst:193 ../common/log_in_dashboard.rst:194 +#: ../common/log_in_dashboard.rst:195 ../common/log_in_dashboard.rst:196 msgid "" -"Virtual network type that uses neither VLANs nor tunnels to segregate tenant " -"traffic. Each flat network typically requires a separate underlying physical " -"interface defined by bridge mappings. However, a flat network can contain " -"multiple subnets." +":guilabel:`System Information`: Use the following tabs to view the service " +"information:" msgstr "" -#: ../common/glossary.rst:3650 ../common/glossary.rst:3657 -#: ../common/glossary.rst:3664 ../common/glossary.rst:3672 -#: ../common/glossary.rst:3661 -msgid "VirtualBox" +#: ../common/log_in_dashboard.rst:189 ../common/log_in_dashboard.rst:191 +#: ../common/log_in_dashboard.rst:192 ../common/log_in_dashboard.rst:196 +#: ../common/log_in_dashboard.rst:197 ../common/log_in_dashboard.rst:198 +#: ../common/log_in_dashboard.rst:199 +msgid ":guilabel:`Services`: View a list of the services." msgstr "" -#: ../common/cli_manage_images.rst:276 -msgid "VirtualE1000" +#: ../common/log_in_dashboard.rst:191 ../common/log_in_dashboard.rst:193 +#: ../common/log_in_dashboard.rst:194 ../common/log_in_dashboard.rst:198 +#: ../common/log_in_dashboard.rst:199 ../common/log_in_dashboard.rst:200 +#: ../common/log_in_dashboard.rst:201 +msgid ":guilabel:`Compute Services`: View a list of all Compute services." msgstr "" -#: ../common/cli_manage_images.rst:278 -msgid "VirtualPCNet32" +#: ../common/log_in_dashboard.rst:193 ../common/log_in_dashboard.rst:196 +#: ../common/log_in_dashboard.rst:198 ../common/log_in_dashboard.rst:203 +#: ../common/log_in_dashboard.rst:204 ../common/log_in_dashboard.rst:205 +#: ../common/log_in_dashboard.rst:206 +msgid ":guilabel:`Network Agents`: View the network agents." msgstr "" -#: ../common/cli_manage_images.rst:280 -msgid "VirtualVmxnet" -msgstr "" - -#: ../common/glossary.rst:2134 ../common/glossary.rst:2140 +#: ../common/log_in_dashboard.rst:195 ../common/log_in_dashboard.rst:200 +#: ../common/log_in_dashboard.rst:201 ../common/log_in_dashboard.rst:202 +#: ../common/log_in_dashboard.rst:203 msgid "" -"Virtualization API library used by OpenStack to interact with many of its " -"supported hypervisors." +":guilabel:`Block Storage Services`: View a list of all Block Storage " +"services." msgstr "" -#: ../common/glossary.rst:3701 ../common/glossary.rst:3708 -#: ../common/glossary.rst:3715 ../common/glossary.rst:3723 -#: ../common/glossary.rst:3712 -msgid "Volume API" -msgstr "" - -#: ../common/glossary.rst:1323 ../common/glossary.rst:1324 +#: ../common/log_in_dashboard.rst:195 ../common/log_in_dashboard.rst:198 msgid "" -"Volume that does not save the changes made to it and reverts to its original " -"state when the current user relinquishes control." +":guilabel:`Default Quotas`: View default quota values. Quotas are hard-coded " +"in OpenStack Compute and define the maximum allowable size and number of " +"resources." msgstr "" -#: ../common/get_started_object_storage.rst:33 -#: ../common/get_started_object_storage.rst:34 -#: ../common/get_started_object_storage.rst:32 -msgid "WSGI middleware" -msgstr "" - -#: ../common/glossary.rst:3323 ../common/glossary.rst:3330 -#: ../common/glossary.rst:3337 ../common/glossary.rst:3345 -#: ../common/glossary.rst:3334 +#: ../common/log_in_dashboard.rst:200 ../common/log_in_dashboard.rst:205 +#: ../common/log_in_dashboard.rst:206 ../common/log_in_dashboard.rst:207 +#: ../common/log_in_dashboard.rst:208 msgid "" -"WSGI middleware component of Object Storage that serves container data as a " -"static web page." +":guilabel:`Orchestration Services`: View a list of all Orchestration " +"services." msgstr "" -#: ../common/cli_install_openstack_command_line_clients.rst:241 -#: ../common/cli_install_openstack_command_line_clients.rst:247 -#: ../common/cli_install_openstack_command_line_clients.rst:254 -#: ../common/cli_install_openstack_command_line_clients.rst:256 -#: ../common/cli_install_openstack_command_line_clients.rst:258 -msgid "What's next" +#: ../common/log_in_dashboard.rst:201 ../common/log_in_dashboard.rst:204 +#: ../common/log_in_dashboard.rst:213 +msgid ":guilabel:`Identity Panel` tab" msgstr "" -#: ../common/cli_install_openstack_command_line_clients.rst:144 +#: ../common/log_in_dashboard.rst:203 ../common/log_in_dashboard.rst:206 +#: ../common/log_in_dashboard.rst:211 ../common/log_in_dashboard.rst:212 +#: ../common/log_in_dashboard.rst:215 msgid "" -"When following the instructions in this section, replace PROJECT with the " -"lowercase name of the client to install, such as ``nova``. Repeat for each " -"client. The following values are valid:" +":guilabel:`Projects`: View, create, assign users to, remove users from, and " +"delete projects." msgstr "" -#: ../common/get_started_identity.rst:12 ../common/get_started_identity.rst:11 -#: ../common/get_started_identity.rst:38 +#: ../common/log_in_dashboard.rst:204 ../common/log_in_dashboard.rst:209 +#: ../common/log_in_dashboard.rst:210 ../common/log_in_dashboard.rst:213 +msgid "OpenStack dashboard—:guilabel:`Identity` tab" +msgstr "" + +#: ../common/log_in_dashboard.rst:206 ../common/log_in_dashboard.rst:209 +#: ../common/log_in_dashboard.rst:214 ../common/log_in_dashboard.rst:215 +#: ../common/log_in_dashboard.rst:218 +msgid ":guilabel:`Users`: View, create, enable, disable, and delete users." +msgstr "" + +#: ../common/log_in_dashboard.rst:212 ../common/log_in_dashboard.rst:217 +#: ../common/log_in_dashboard.rst:218 ../common/log_in_dashboard.rst:221 +msgid "OpenStack dashboard—:guilabel:`Settings` tab" +msgstr "" + +#: ../common/log_in_dashboard.rst:214 ../common/log_in_dashboard.rst:219 +#: ../common/log_in_dashboard.rst:220 ../common/log_in_dashboard.rst:223 msgid "" -"When installing OpenStack Identity service, you must register each service " -"in your OpenStack installation. Identity service can then track which " -"OpenStack services are installed, and where they are located on the network." +"Click the 'Settings' button from the user drop down menu in the top right of " +"any page, you will see the :guilabel:`Settings` tab." msgstr "" -#: ../common/cli_manage_volumes.rst:237 -msgid "" -"When the volume is fully deleted, it disappears from the list of volumes::" +#: ../common/log_in_dashboard.rst:217 ../common/log_in_dashboard.rst:222 +#: ../common/log_in_dashboard.rst:223 ../common/log_in_dashboard.rst:226 +msgid ":guilabel:`User Settings`: View and manage dashboard settings." msgstr "" -#: ../common/cli_manage_images.rst:81 -msgid "" -"When viewing a list of images, you can also use ``grep`` to filter the list, " -"as follows::" +#: ../common/log_in_dashboard.rst:219 ../common/log_in_dashboard.rst:224 +#: ../common/log_in_dashboard.rst:225 ../common/log_in_dashboard.rst:228 +msgid ":guilabel:`Change Password`: Change the password of the user." msgstr "" -#: ../common/cli_set_environment_variables_using_openstack_rc.rst:48 -#: ../common/cli_set_environment_variables_using_openstack_rc.rst:49 -msgid "" -"When you are prompted for an OpenStack password, enter the password for the " -"user who downloaded the :file:`PROJECT-openrc.sh` file." -msgstr "" - -#: ../common/cli_set_environment_variables_using_openstack_rc.rst:96 -msgid "" -"When you run OpenStack client commands, you can override some environment " -"variable settings by using the options that are listed at the end of the " -"``help`` output of the various client commands. For example, you can " -"override the ``OS_PASSWORD`` setting in the :file:`PROJECT-openrc.sh` file " -"by specifying a password on a :command:`keystone` command, as follows::" -msgstr "" - -#: ../common/cli_set_environment_variables_using_openstack_rc.rst:96 -#: ../common/cli_set_environment_variables_using_openstack_rc.rst:97 -msgid "" -"When you run OpenStack client commands, you can override some environment " -"variable settings by using the options that are listed at the end of the " -"``help`` output of the various client commands. For example, you can " -"override the ``OS_PASSWORD`` setting in the :file:`PROJECT-openrc.sh` file " -"by specifying a password on a :command:`openstack` command, as follows::" -msgstr "" - -#: ../common/support-compute.rst:104 -msgid "" -"When you run ``nova-api`` the first time, it generates the certificate " -"authority information, including :file:`openssl.cnf`. If you start the CA " -"services before this, you might not be able to create your ZIP file. Restart " -"the services. When your CA information is available, create your ZIP file." -msgstr "" - -#: ../common/cli_set_environment_variables_using_openstack_rc.rst:12 -msgid "" -"When you source the file, environment variables are set for your current " -"shell. The variables enable the OpenStack client commands to communicate " -"with the OpenStack services that run in the cloud." -msgstr "" - -#: ../common/cli_set_environment_variables_using_openstack_rc.rst:105 -#: ../common/cli_set_environment_variables_using_openstack_rc.rst:106 -msgid "Where ``PASSWORD`` is your password." -msgstr "" - -#: ../common/get_started_identity.rst:48 ../common/get_started_identity.rst:47 -msgid "" -"While OpenStack Identity supports token-based authentication in this " -"release, the intention is to support additional protocols in the future. Its " -"main purpose is to be an integration service, and not aspire to be a full-" -"fledged identity store and management solution." -msgstr "" - -#: ../common/cli_manage_volumes.rst:276 -msgid "While logged in as the volume donor, list the available volumes::" -msgstr "" - -#: ../common/cli_manage_volumes.rst:323 -msgid "" -"While the ``auth_key`` property is visible in the output of ``cinder " -"transfer-create VOLUME_ID``, it will not be available in subsequent ``cinder " -"transfer-show TRANSFER_ID`` commands." -msgstr "" - -#: ../common/glossary.rst:1423 ../common/glossary.rst:1424 -msgid "" -"Within RabbitMQ and Compute, it is the messaging interface that is used by " -"the scheduler service to receive capability messages from the compute, " -"volume, and network nodes." -msgstr "" - -#: ../common/get_started_storage_concepts.rst:29 -#: ../common/get_started_storage_concepts.rst:28 -msgid "Work in progress - expected for the Mitaka release" -msgstr "" - -#: ../common/glossary.rst:3765 ../common/glossary.rst:3772 -#: ../common/glossary.rst:3779 ../common/glossary.rst:3787 -#: ../common/cli_overview.rst:92 ../common/glossary.rst:3776 -#: ../common/cli_overview.rst:95 -msgid "Workflow service" -msgstr "" - -#: ../common/cli_overview.rst:92 ../common/cli_overview.rst:95 -msgid "Workflow service for OpenStack cloud." -msgstr "" - -#: ../common/glossary.rst:3798 ../common/glossary.rst:3805 -#: ../common/glossary.rst:3812 ../common/glossary.rst:3820 -#: ../common/glossary.rst:3809 -msgid "XFS" -msgstr "" - -#: ../common/glossary.rst:3774 ../common/glossary.rst:3781 -#: ../common/glossary.rst:3788 ../common/glossary.rst:3796 -#: ../common/glossary.rst:3785 -msgid "Xen" -msgstr "" - -#: ../common/glossary.rst:3780 ../common/glossary.rst:3787 -#: ../common/glossary.rst:3794 ../common/glossary.rst:3802 -#: ../common/glossary.rst:3791 -msgid "Xen API" -msgstr "" - -#: ../common/glossary.rst:3785 ../common/glossary.rst:3792 -#: ../common/glossary.rst:3799 ../common/glossary.rst:3807 -#: ../common/glossary.rst:3796 -msgid "Xen Cloud Platform (XCP)" -msgstr "" - -#: ../common/glossary.rst:3789 ../common/glossary.rst:3796 -#: ../common/glossary.rst:3803 ../common/glossary.rst:3811 -#: ../common/glossary.rst:3800 -msgid "Xen Storage Manager Volume Driver" -msgstr "" - -#: ../common/glossary.rst:3777 ../common/glossary.rst:3784 -#: ../common/glossary.rst:3791 ../common/glossary.rst:3799 -#: ../common/glossary.rst:3788 -msgid "" -"Xen is a hypervisor using a microkernel design, providing services that " -"allow multiple computer operating systems to execute on the same computer " -"hardware concurrently." -msgstr "" - -#: ../common/get_started_compute.rst:43 ../common/get_started_compute.rst:42 -msgid "XenAPI for XenServer/XCP" -msgstr "" - -#: ../common/glossary.rst:3794 ../common/glossary.rst:3801 -#: ../common/glossary.rst:3808 ../common/glossary.rst:3816 -#: ../common/glossary.rst:3805 -msgid "XenServer" -msgstr "" - -#: ../common/cli_set_environment_variables_using_openstack_rc.rst:78 -#: ../common/cli_set_environment_variables_using_openstack_rc.rst:79 -msgid "" -"You are not prompted for the password with this method. The password lives " -"in clear text format in the :file:`PROJECT-openrc.sh` file. Restrict the " -"permissions on this file to avoid security problems. You can also remove the " -"``OS_PASSWORD`` variable from the file, and use the ``--password`` parameter " -"with OpenStack client commands instead." -msgstr "" - -#: ../common/support-compute.rst:181 -msgid "" -"You can also use the :option:`--active` parameter to force the instance back " -"to an active state instead of an error state. For example::" -msgstr "" - -#: ../common/cli_install_openstack_command_line_clients.rst:129 -msgid "You can install pip and use it to manage client installation:" -msgstr "" - -#: ../common/cli_overview.rst:9 -msgid "" -"You can run the commands from the command line, or include the commands " -"within scripts to automate tasks. If you provide OpenStack credentials, such " -"as your user name and password, you can run these commands on any computer." +#: ../common/nova_show_usage_statistics_for_hosts_instances.rst:3 +msgid "Show usage statistics for hosts and instances" msgstr "" #: ../common/nova_show_usage_statistics_for_hosts_instances.rst:5 @@ -10482,531 +13115,115 @@ msgid "" "You can show basic statistics on resource usage for hosts and instances." msgstr "" -#: ../common/cli_manage_volumes.rst:253 +#: ../common/nova_show_usage_statistics_for_hosts_instances.rst:9 msgid "" -"You can transfer a volume from one owner to another by using the ``cinder " -"transfer*`` commands. The volume donor, or original owner, creates a " -"transfer request and sends the created transfer ID and authorization key to " -"the volume recipient. The volume recipient, or new owner, accepts the " -"transfer by using the ID and key." +"For more sophisticated monitoring, see the `ceilometer `__ project. You can also use tools, such as `Ganglia `__ or `Graphite `__, to gather " +"more detailed data." msgstr "" -#: ../common/cli_manage_images.rst:9 +#: ../common/nova_show_usage_statistics_for_hosts_instances.rst:16 +msgid "Show host usage statistics" +msgstr "" + +#: ../common/nova_show_usage_statistics_for_hosts_instances.rst:18 msgid "" -"You can upload images through the ``glance`` client or the Image service " -"API. Besides, you can use the ``nova`` client for the image management. The " -"latter provides mechanisms to list and delete images, set and delete image " -"metadata, and create images of a running instance of snapshot and backup " -"types." +"The following examples show the host usage statistics for a host called " +"``devstack``." msgstr "" -#: ../common/support-compute.rst:151 +#: ../common/nova_show_usage_statistics_for_hosts_instances.rst:21 +msgid "List the hosts and the nova-related services that run on them::" +msgstr "" + +#: ../common/nova_show_usage_statistics_for_hosts_instances.rst:35 msgid "" -"You can view the log output of running instances from either the :guilabel:" -"`Log` tab of the dashboard or the output of :command:`nova console-log`. In " -"some cases, the log output of a running Linux instance will be empty or only " -"display a single character (for example, the `?` character)." +"Get a summary of resource usage of all of the instances running on the host::" msgstr "" -#: ../common/support-compute.rst:38 +#: ../common/nova_show_usage_statistics_for_hosts_instances.rst:49 msgid "" -"You have two options for logging for OpenStack Compute based on " -"configuration settings. In :file:`nova.conf`, include the ``logfile`` option " -"to enable logging. Alternatively you can set ``use_syslog = 1`` so that the " -"nova daemon logs to syslog." +"The ``cpu`` column shows the sum of the virtual CPUs for instances running " +"on the host." msgstr "" -#: ../common/cli_set_environment_variables_using_openstack_rc.rst:87 -#: ../common/cli_set_environment_variables_using_openstack_rc.rst:88 +#: ../common/nova_show_usage_statistics_for_hosts_instances.rst:52 msgid "" -"You must set the ``OS_CACERT`` environment variable when using the https " -"protocol in the ``OS_AUTH_URL`` environment setting because the verification " -"process for the TLS (HTTPS) server certificate uses the one indicated in the " -"environment. This certificate will be used when verifying the TLS (HTTPS) " -"server certificate." +"The ``memory_mb`` column shows the sum of the memory (in MB) allocated to " +"the instances that run on the host." msgstr "" -#: ../common/glossary.rst:3809 ../common/glossary.rst:3816 -#: ../common/glossary.rst:3823 ../common/glossary.rst:3831 -#: ../common/glossary.rst:3820 -msgid "ZeroMQ" -msgstr "" - -#: ../common/glossary.rst:3814 ../common/glossary.rst:3821 -#: ../common/glossary.rst:3828 ../common/glossary.rst:3836 -#: ../common/glossary.rst:3825 -msgid "Zuul" -msgstr "" - -#: ../common/app_support.rst:83 ../common/app_support.rst:81 +#: ../common/nova_show_usage_statistics_for_hosts_instances.rst:55 msgid "" -"`API Complete Reference (PDF) `__" +"The ``disk_gb`` column shows the sum of the root and ephemeral disk sizes " +"(in GB) of the instances that run on the host." msgstr "" -#: ../common/app_support.rst:66 ../common/app_support.rst:64 +#: ../common/nova_show_usage_statistics_for_hosts_instances.rst:58 msgid "" -"`API Quick Start `__" +"The row that has the value ``used_now`` in the ``PROJECT`` column shows the " +"sum of the resources allocated to the instances that run on the host, plus " +"the resources allocated to the virtual machine of the host itself." msgstr "" -#: ../common/app_support.rst:71 ../common/app_support.rst:69 -msgid "`Admin User Guide `__" -msgstr "" - -#: ../common/app_support.rst:42 ../common/app_support.rst:40 +#: ../common/nova_show_usage_statistics_for_hosts_instances.rst:63 msgid "" -"`Architecture Design Guide `__" +"The row that has the value ``used_max`` in the ``PROJECT`` column shows the " +"sum of the resources allocated to the instances that run on the host." msgstr "" -#: ../common/get_started_with_openstack.rst:52 -#: ../common/get_started_with_openstack.rst:60 +#: ../common/nova_show_usage_statistics_for_hosts_instances.rst:69 msgid "" -"`Block Storage `__" +"These values are computed by using information about the flavors of the " +"instances that run on the hosts. This command does not query the CPU usage, " +"memory usage, or hard disk usage of the physical host." msgstr "" -#: ../common/app_support.rst:171 +#: ../common/nova_show_usage_statistics_for_hosts_instances.rst:74 +msgid "Show instance usage statistics" +msgstr "" + +#: ../common/nova_show_usage_statistics_for_hosts_instances.rst:76 +msgid "Get CPU, memory, I/O, and network statistics for an instance." +msgstr "" + +#: ../common/nova_show_usage_statistics_for_hosts_instances.rst:78 +msgid "List instances:" +msgstr "" + +#: ../common/nova_show_usage_statistics_for_hosts_instances.rst:90 +msgid "Get diagnostic statistics:" +msgstr "" + +#: ../common/nova_show_usage_statistics_for_hosts_instances.rst:115 +msgid "Get summary statistics for each tenant:" +msgstr "" + +#: ../common/support-compute.rst:7 +msgid "Troubleshoot Compute" +msgstr "" + +#: ../common/support-compute.rst:9 msgid "" -"`Bugs: Application catalog (murano) `__" +"Common problems for Compute typically involve misconfigured networking or " +"credentials that are not sourced properly in the environment. Also, most " +"flat networking configurations do not enable :command:`ping` or :command:" +"`ssh` from a compute node to the instances that run on that node. Another " +"common problem is trying to run 32-bit images on a 64-bit compute node. This " +"section shows you how to troubleshoot Compute." msgstr "" -#: ../common/app_support.rst:176 ../common/app_support.rst:173 -#: ../common/app_support.rst:171 +#: ../common/support-compute.rst:21 +msgid "Compute service logging" +msgstr "" + +#: ../common/support-compute.rst:23 msgid "" -"`Bugs: Bare metal service (ironic) `__" -msgstr "" - -#: ../common/app_support.rst:175 -msgid "" -"`Bugs: Containers service (magnum) `__" -msgstr "" - -#: ../common/app_support.rst:178 ../common/app_support.rst:175 -#: ../common/app_support.rst:173 ../common/app_support.rst:177 -msgid "" -"`Bugs: Data processing service (sahara) `__" -msgstr "" - -#: ../common/app_support.rst:181 ../common/app_support.rst:178 -#: ../common/app_support.rst:176 ../common/app_support.rst:180 -msgid "`Bugs: Database service (trove) `__" -msgstr "" - -#: ../common/app_support.rst:182 -msgid "" -"`Bugs: Deployment service (tuskar) `__" -msgstr "" - -#: ../common/app_support.rst:182 ../common/app_support.rst:184 -msgid "" -"`Bugs: Key Manager Service (barbican) `__" -msgstr "" - -#: ../common/app_support.rst:188 ../common/app_support.rst:185 -#: ../common/app_support.rst:183 ../common/app_support.rst:189 -#: ../common/app_support.rst:191 ../common/app_support.rst:194 -#: ../common/app_support.rst:196 -msgid "`Bugs: Messaging service (zaqar) `__" -msgstr "" - -#: ../common/app_support.rst:191 ../common/app_support.rst:188 -#: ../common/app_support.rst:186 ../common/app_support.rst:192 -#: ../common/app_support.rst:194 ../common/app_support.rst:197 -#: ../common/app_support.rst:199 -msgid "" -"`Bugs: OpenStack API Documentation (developer.openstack.org) `__" -msgstr "" - -#: ../common/app_support.rst:156 ../common/app_support.rst:153 -#: ../common/app_support.rst:151 -msgid "" -"`Bugs: OpenStack Block Storage (cinder) `__" -msgstr "" - -#: ../common/app_support.rst:159 ../common/app_support.rst:156 -#: ../common/app_support.rst:154 -msgid "`Bugs: OpenStack Compute (nova) `__" -msgstr "" - -#: ../common/app_support.rst:161 ../common/app_support.rst:158 -#: ../common/app_support.rst:156 -msgid "" -"`Bugs: OpenStack Dashboard (horizon) `__" -msgstr "" - -#: ../common/app_support.rst:194 ../common/app_support.rst:191 -#: ../common/app_support.rst:189 ../common/app_support.rst:195 -#: ../common/app_support.rst:197 ../common/app_support.rst:200 -#: ../common/app_support.rst:202 -msgid "" -"`Bugs: OpenStack Documentation (docs.openstack.org) `__" -msgstr "" - -#: ../common/app_support.rst:164 ../common/app_support.rst:161 -#: ../common/app_support.rst:159 -msgid "" -"`Bugs: OpenStack Identity (keystone) `__" -msgstr "" - -#: ../common/app_support.rst:167 ../common/app_support.rst:164 -#: ../common/app_support.rst:162 -msgid "" -"`Bugs: OpenStack Image service (glance) `__" -msgstr "" - -#: ../common/app_support.rst:170 ../common/app_support.rst:167 -#: ../common/app_support.rst:165 -msgid "" -"`Bugs: OpenStack Networking (neutron) `__" -msgstr "" - -#: ../common/app_support.rst:173 ../common/app_support.rst:170 -#: ../common/app_support.rst:168 -msgid "" -"`Bugs: OpenStack Object Storage (swift) `__" -msgstr "" - -#: ../common/app_support.rst:183 ../common/app_support.rst:180 -#: ../common/app_support.rst:178 ../common/app_support.rst:182 -#: ../common/app_support.rst:184 ../common/app_support.rst:186 -msgid "`Bugs: Orchestration (heat) `__" -msgstr "" - -#: ../common/app_support.rst:184 ../common/app_support.rst:186 -#: ../common/app_support.rst:188 -msgid "" -"`Bugs: Shared file systems (manila) `__" -msgstr "" - -#: ../common/app_support.rst:185 ../common/app_support.rst:182 -#: ../common/app_support.rst:180 ../common/app_support.rst:186 -#: ../common/app_support.rst:188 ../common/app_support.rst:190 -msgid "" -"`Bugs: Telemetry (ceilometer) `__" -msgstr "" - -#: ../common/app_support.rst:191 ../common/app_support.rst:193 -msgid "" -"`Bugs: Workflow service (mistral) `__" -msgstr "" - -#: ../common/get_started_with_openstack.rst:67 -#: ../common/get_started_with_openstack.rst:75 -msgid "`Ceilometer `__" -msgstr "" - -#: ../common/get_started_with_openstack.rst:53 -#: ../common/get_started_with_openstack.rst:61 -msgid "`Cinder `__" -msgstr "" - -#: ../common/app_support.rst:43 -msgid "" -"`Cloud Administrator Guide `__" -msgstr "" - -#: ../common/app_support.rst:45 ../common/app_support.rst:43 -msgid "" -"`Cloud Administrator Guide `__" -msgstr "" - -#: ../common/app_support.rst:74 ../common/app_support.rst:72 -msgid "" -"`Command-Line Interface Reference `__" -msgstr "" - -#: ../common/get_started_with_openstack.rst:33 -#: ../common/get_started_with_openstack.rst:41 -msgid "`Compute `__" -msgstr "" - -#: ../common/app_support.rst:48 ../common/app_support.rst:46 -msgid "" -"`Configuration Reference `__" -msgstr "" - -#: ../common/get_started_with_openstack.rst:28 -#: ../common/get_started_with_openstack.rst:36 -msgid "`Dashboard `__" -msgstr "" - -#: ../common/get_started_with_openstack.rst:80 -#: ../common/get_started_with_openstack.rst:88 -msgid "" -"`Data processing service `__" -msgstr "" - -#: ../common/get_started_with_openstack.rst:76 -#: ../common/get_started_with_openstack.rst:84 -msgid "" -"`Database service `__" -msgstr "" - -#: ../common/app_support.rst:69 ../common/app_support.rst:67 -msgid "`End User Guide `__" -msgstr "" - -#: ../common/get_started_with_openstack.rst:63 -#: ../common/get_started_with_openstack.rst:71 -msgid "`Glance `__" -msgstr "" - -#: ../common/get_started_with_openstack.rst:71 -#: ../common/get_started_with_openstack.rst:79 -msgid "`Heat `__" -msgstr "" - -#: ../common/app_support.rst:55 ../common/app_support.rst:53 -msgid "" -"`High Availability Guide `__" -msgstr "" - -#: ../common/get_started_with_openstack.rst:29 -#: ../common/get_started_with_openstack.rst:37 -msgid "`Horizon `__" -msgstr "" - -#: ../common/get_started_with_openstack.rst:57 -#: ../common/get_started_with_openstack.rst:65 -msgid "" -"`Identity service `__" -msgstr "" - -#: ../common/get_started_with_openstack.rst:62 -#: ../common/get_started_with_openstack.rst:70 -msgid "" -"`Image service `__" -msgstr "" - -#: ../common/app_support.rst:33 ../common/app_support.rst:31 -msgid "" -"`Installation Guide for Red Hat Enterprise Linux 7, CentOS 7, and Fedora 21 " -"`__" -msgstr "" - -#: ../common/app_support.rst:37 ../common/app_support.rst:35 -msgid "" -"`Installation Guide for Ubuntu 14.04 `__" -msgstr "" - -#: ../common/app_support.rst:29 ../common/app_support.rst:27 -msgid "" -"`Installation Guide for openSUSE 13.2 and SUSE Linux Enterprise Server 12 " -"`__" -msgstr "" - -#: ../common/get_started_with_openstack.rst:58 -#: ../common/get_started_with_openstack.rst:66 -msgid "`Keystone `__" -msgstr "" - -#: ../common/get_started_with_openstack.rst:38 -#: ../common/get_started_with_openstack.rst:46 -msgid "" -"`Networking `__" -msgstr "" - -#: ../common/app_support.rst:53 ../common/app_support.rst:51 -msgid "`Networking Guide `__" -msgstr "" - -#: ../common/get_started_with_openstack.rst:39 -#: ../common/get_started_with_openstack.rst:47 -msgid "`Neutron `__" -msgstr "" - -#: ../common/get_started_with_openstack.rst:34 -#: ../common/get_started_with_openstack.rst:42 -msgid "`Nova `__" -msgstr "" - -#: ../common/get_started_with_openstack.rst:44 -#: ../common/get_started_with_openstack.rst:52 -msgid "" -"`Object Storage `__" -msgstr "" - -#: ../common/app_support.rst:80 ../common/app_support.rst:78 -msgid "" -"`OpenStack API Complete Reference (HTML) `__" -msgstr "" - -#: ../common/app_support.rst:51 ../common/app_support.rst:49 -msgid "`Operations Guide `__" -msgstr "" - -#: ../common/get_started_with_openstack.rst:70 -#: ../common/get_started_with_openstack.rst:78 -msgid "" -"`Orchestration `__" -msgstr "" - -#: ../common/get_started_with_openstack.rst:81 -#: ../common/get_started_with_openstack.rst:89 -msgid "`Sahara `__" -msgstr "" - -#: ../common/app_support.rst:58 ../common/app_support.rst:56 -msgid "`Security Guide `__" -msgstr "" - -#: ../common/get_started_with_openstack.rst:45 -#: ../common/get_started_with_openstack.rst:53 -msgid "`Swift `__" -msgstr "" - -#: ../common/get_started_with_openstack.rst:66 -#: ../common/get_started_with_openstack.rst:74 -msgid "" -"`Telemetry `__" -msgstr "" - -#: ../common/get_started_with_openstack.rst:77 -#: ../common/get_started_with_openstack.rst:85 -msgid "`Trove `__" -msgstr "" - -#: ../common/app_support.rst:60 ../common/app_support.rst:58 -msgid "" -"`Virtual Machine Image Guide `__" -msgstr "" - -#: ../common/cli_manage_images.rst:167 -msgid "``--checksum CHECKSUM``" -msgstr "" - -#: ../common/cli_manage_images.rst:143 -msgid "``--container-format CONTAINER_FORMAT``" -msgstr "" - -#: ../common/cli_manage_images.rst:172 -msgid "``--copy-from IMAGE_URL``" -msgstr "" - -#: ../common/cli_manage_images.rst:139 -msgid "``--disk-format DISK_FORMAT``" -msgstr "" - -#: ../common/cli_manage_images.rst:164 -msgid "``--file FILE``" -msgstr "" - -#: ../common/cli_manage_images.rst:192 -msgid "``--human-readable``" -msgstr "" - -#: ../common/cli_manage_images.rst:179 -msgid "``--is-protected [True|False]``" -msgstr "" - -#: ../common/cli_manage_images.rst:176 -msgid "``--is-public [True|False]``" -msgstr "" - -#: ../common/cli_manage_images.rst:159 -msgid "``--location IMAGE_URL``" -msgstr "" - -#: ../common/cli_manage_images.rst:151 -msgid "``--min-disk DISK_GB``" -msgstr "" - -#: ../common/cli_manage_images.rst:154 -msgid "``--min-ram DISK_RAM``" -msgstr "" - -#: ../common/cli_manage_images.rst:135 -msgid "``--name NAME``" -msgstr "" - -#: ../common/cli_manage_images.rst:147 -msgid "``--owner TENANT_ID --size SIZE``" -msgstr "" - -#: ../common/cli_manage_images.rst:183 -msgid "``--property KEY=VALUE``" -msgstr "" - -#: ../common/cli_manage_images.rst:188 -msgid "``--purge-props``" -msgstr "" - -#: ../common/cli_install_openstack_command_line_clients.rst:148 -msgid "``barbican`` - Key Manager Service API" -msgstr "" - -#: ../common/cli_install_openstack_command_line_clients.rst:148 -#: ../common/cli_install_openstack_command_line_clients.rst:150 -msgid "``ceilometer`` - Telemetry API" -msgstr "" - -#: ../common/cli_install_openstack_command_line_clients.rst:150 -#: ../common/cli_install_openstack_command_line_clients.rst:152 -msgid "``cinder`` - Block Storage API and extensions" -msgstr "" - -#: ../common/cli_manage_images.rst:95 -msgid "" -"``filesystem_store_metadata_file = filePath``, where filePath points to a " -"JSON file that defines the mount point for OpenStack images on your system " -"and a unique ID. For example:" -msgstr "" - -#: ../common/cli_install_openstack_command_line_clients.rst:152 -#: ../common/cli_install_openstack_command_line_clients.rst:154 -msgid "``glance`` - Image service API" -msgstr "" - -#: ../common/get_started_orchestration.rst:31 -#: ../common/get_started_orchestration.rst:30 -msgid "``heat-api-cfn`` component" -msgstr "" - -#: ../common/get_started_orchestration.rst:27 -#: ../common/get_started_orchestration.rst:26 -msgid "``heat-api`` component" -msgstr "" - -#: ../common/get_started_orchestration.rst:34 -#: ../common/get_started_orchestration.rst:35 -#: ../common/get_started_orchestration.rst:33 -msgid "``heat-engine``" -msgstr "" - -#: ../common/cli_install_openstack_command_line_clients.rst:154 -#: ../common/cli_install_openstack_command_line_clients.rst:156 -msgid "``heat`` - Orchestration API" -msgstr "" - -#: ../common/get_started_orchestration.rst:23 -#: ../common/get_started_orchestration.rst:22 -msgid "``heat`` command-line client" -msgstr "" - -#: ../common/cli_install_openstack_command_line_clients.rst:171 -#: ../common/cli_install_openstack_command_line_clients.rst:177 -#: ../common/cli_install_openstack_command_line_clients.rst:179 -#: ../common/cli_install_openstack_command_line_clients.rst:181 -#: ../common/cli_install_openstack_command_line_clients.rst:183 -msgid "``keystone`` - Identity service API and extensions" +"Compute stores a log file for each service in :file:`/var/log/nova`. For " +"example, :file:`nova-compute.log` is the log for the ``nova-compute`` " +"service. You can set the following options to format log strings for the " +"``nova.log`` module in the :file:`nova.conf` file:" msgstr "" #: ../common/support-compute.rst:29 @@ -11017,2521 +13234,318 @@ msgstr "" msgid "``logging_default_format_string``" msgstr "" -#: ../common/cli_install_openstack_command_line_clients.rst:156 -#: ../common/cli_install_openstack_command_line_clients.rst:158 -msgid "``magnum`` - Containers service API" +#: ../common/support-compute.rst:33 +msgid "" +"If the log level is set to ``debug``, you can also specify " +"``logging_debug_format_suffix`` to append extra formatting. For information " +"about what variables are available for the formatter see http://docs.python." +"org/library/logging.html#formatter-objects." msgstr "" -#: ../common/cli_install_openstack_command_line_clients.rst:158 -#: ../common/cli_install_openstack_command_line_clients.rst:160 -msgid "``manila`` - Shared file systems API" +#: ../common/support-compute.rst:33 +msgid "" +"If the log level is set to ``debug``, you can also specify " +"``logging_debug_format_suffix`` to append extra formatting. For information " +"about what variables are available for the formatter see http://docs.python." +"org/library/logging.html#formatter." msgstr "" -#: ../common/cli_install_openstack_command_line_clients.rst:162 -msgid "``mistral`` - Workflow service API" +#: ../common/support-compute.rst:38 +msgid "" +"You have two options for logging for OpenStack Compute based on " +"configuration settings. In :file:`nova.conf`, include the ``logfile`` option " +"to enable logging. Alternatively you can set ``use_syslog = 1`` so that the " +"nova daemon logs to syslog." msgstr "" -#: ../common/cli_install_openstack_command_line_clients.rst:160 -#: ../common/cli_install_openstack_command_line_clients.rst:162 -#: ../common/cli_install_openstack_command_line_clients.rst:164 -msgid "``murano`` - Application catalog API" +#: ../common/support-compute.rst:47 +msgid "Guru Meditation reports" msgstr "" -#: ../common/cli_install_openstack_command_line_clients.rst:156 -#: ../common/cli_install_openstack_command_line_clients.rst:162 -#: ../common/cli_install_openstack_command_line_clients.rst:164 -#: ../common/cli_install_openstack_command_line_clients.rst:166 -msgid "``neutron`` - Networking API" +#: ../common/support-compute.rst:49 +msgid "" +"A Guru Meditation report is sent by the Compute Service upon receipt of the " +"``SIGUSR1`` signal. This report is a general-purpose error report, including " +"a complete report of the service's current state, and is sent to ``stderr``." msgstr "" -#: ../common/get_started_compute.rst:32 ../common/get_started_compute.rst:31 -msgid "``nova-api-metadata`` service" +#: ../common/support-compute.rst:49 +msgid "" +"A Guru Meditation report is sent by the Compute service upon receipt of the " +"``SIGUSR1`` signal. This report is a general-purpose error report, including " +"a complete report of the service's current state, and is sent to ``stderr``." msgstr "" -#: ../common/get_started_compute.rst:25 ../common/get_started_compute.rst:24 -msgid "``nova-api`` service" +#: ../common/support-compute.rst:54 +msgid "" +"For example, if you redirect error output to ``nova-api-err.log`` using :" +"command:`nova-api 2>/var/log/nova/nova-api-err.log`, resulting in the " +"process ID 8675, you can then run::" msgstr "" -#: ../common/get_started_compute.rst:97 ../common/get_started_compute.rst:96 -msgid "``nova-cert`` daemon" +#: ../common/support-compute.rst:60 +msgid "" +"This command triggers the Guru Meditation report to be printed to :file:`/" +"var/log/nova/nova-api-err.log`." msgstr "" -#: ../common/get_started_compute.rst:69 ../common/get_started_compute.rst:68 -msgid "``nova-cert`` module" +#: ../common/support-compute.rst:63 +msgid "The report has the following sections:" msgstr "" -#: ../common/get_started_compute.rst:51 ../common/get_started_compute.rst:50 -msgid "``nova-compute`` service" +#: ../common/support-compute.rst:65 +msgid "" +"Package: Displays information about the package to which the process " +"belongs, including version information." msgstr "" -#: ../common/get_started_compute.rst:64 ../common/get_started_compute.rst:63 -msgid "``nova-conductor`` module" +#: ../common/support-compute.rst:68 +msgid "" +"Threads: Displays stack traces and thread IDs for each of the threads within " +"the process." msgstr "" -#: ../common/get_started_compute.rst:82 ../common/get_started_compute.rst:81 -msgid "``nova-consoleauth`` daemon" +#: ../common/support-compute.rst:71 +msgid "" +"Green Threads: Displays stack traces for each of the green threads within " +"the process (green threads do not have thread IDs)." msgstr "" -#: ../common/get_started_compute.rst:74 ../common/get_started_compute.rst:73 -msgid "``nova-network worker`` daemon" +#: ../common/support-compute.rst:74 +msgid "" +"Configuration: Lists all configuration options currently accessible through " +"the CONF object for the current process." msgstr "" -#: ../common/get_started_compute.rst:86 ../common/get_started_compute.rst:85 -msgid "``nova-novncproxy`` daemon" +#: ../common/support-compute.rst:77 +msgid "" +"For more information, see `Guru Meditation Reports `_." msgstr "" -#: ../common/get_started_compute.rst:55 ../common/get_started_compute.rst:54 -msgid "``nova-scheduler`` service" +#: ../common/support-compute.rst:83 +msgid "Common errors and fixes for Compute" msgstr "" -#: ../common/get_started_compute.rst:90 ../common/get_started_compute.rst:89 -msgid "``nova-spicehtml5proxy`` daemon" +#: ../common/support-compute.rst:85 +msgid "" +"The `ask.openstack.org `_ site offers a place to " +"ask and answer questions, and you can also mark questions as frequently " +"asked questions. This section describes some errors people have posted " +"previously. Bugs are constantly being fixed, so online resources are a great " +"way to get the most up-to-date errors and fixes." msgstr "" -#: ../common/get_started_compute.rst:94 ../common/get_started_compute.rst:93 -msgid "``nova-xvpvncproxy`` daemon" +#: ../common/support-compute.rst:91 +msgid "**Credential errors, 401, and 403 forbidden errors**" msgstr "" -#: ../common/cli_install_openstack_command_line_clients.rst:158 -#: ../common/cli_install_openstack_command_line_clients.rst:164 -#: ../common/cli_install_openstack_command_line_clients.rst:166 -#: ../common/cli_install_openstack_command_line_clients.rst:168 -msgid "``nova`` - Compute API and extensions" +#: ../common/support-compute.rst:93 +msgid "" +"Missing credentials cause a ``403 forbidden`` error. To resolve this issue, " +"use one of these methods:" msgstr "" -#: ../common/cli_install_openstack_command_line_clients.rst:166 -#: ../common/cli_install_openstack_command_line_clients.rst:172 -#: ../common/cli_install_openstack_command_line_clients.rst:174 -#: ../common/cli_install_openstack_command_line_clients.rst:176 -#: ../common/cli_install_openstack_command_line_clients.rst:178 -msgid "``openstack`` - Common OpenStack client supporting multiple services" +#: ../common/support-compute.rst:97 +msgid "" +"Gets the :file:`novarc` file from the project ZIP file, save existing " +"credentials in case of override. and manually source the :file:`novarc` file." msgstr "" -#: ../common/get_started_database_service.rst:46 -#: ../common/get_started_database_service.rst:45 -msgid "``python-troveclient`` command-line client" +#: ../common/support-compute.rst:97 +msgid "" +"Gets the :file:`novarc` file from the project ZIP file, saves existing " +"credentials in case of override, and manually sources the :file:`novarc` " +"file." msgstr "" -#: ../common/cli_install_openstack_command_line_clients.rst:160 -#: ../common/cli_install_openstack_command_line_clients.rst:166 -#: ../common/cli_install_openstack_command_line_clients.rst:168 -#: ../common/cli_install_openstack_command_line_clients.rst:170 -msgid "``sahara`` - Data Processing API" +#: ../common/support-compute.rst:99 +msgid "Manual method" msgstr "" -#: ../common/cli_install_openstack_command_line_clients.rst:160 -msgid "``sahara`` - Database Processing API" +#: ../common/support-compute.rst:102 +msgid "" +"Generates :file:`novarc` from the project ZIP file and sources it for you." msgstr "" -#: ../common/cli_manage_images.rst:93 -msgid "``show_multiple_locations = True``" +#: ../common/support-compute.rst:102 +msgid "Script method" msgstr "" -#: ../common/cli_install_openstack_command_line_clients.rst:162 -#: ../common/cli_install_openstack_command_line_clients.rst:168 -#: ../common/cli_install_openstack_command_line_clients.rst:170 -#: ../common/cli_install_openstack_command_line_clients.rst:172 -msgid "``swift`` - Object Storage API" +#: ../common/support-compute.rst:104 +msgid "" +"When you run ``nova-api`` the first time, it generates the certificate " +"authority information, including :file:`openssl.cnf`. If you start the CA " +"services before this, you might not be able to create your ZIP file. Restart " +"the services. When your CA information is available, create your ZIP file." msgstr "" -#: ../common/get_started_database_service.rst:50 -#: ../common/get_started_database_service.rst:49 -msgid "``trove-api`` component" +#: ../common/support-compute.rst:110 +msgid "" +"Also, check your HTTP proxy settings to see whether they cause problems " +"with :file:`novarc` creation." msgstr "" -#: ../common/get_started_database_service.rst:54 -#: ../common/get_started_database_service.rst:53 -msgid "``trove-conductor`` service" +#: ../common/support-compute.rst:113 +msgid "**Instance errors**" msgstr "" -#: ../common/get_started_database_service.rst:62 -#: ../common/get_started_database_service.rst:63 -#: ../common/get_started_database_service.rst:61 -msgid "``trove-guestagent`` service" +#: ../common/support-compute.rst:115 +msgid "" +"Sometimes a particular instance shows ``pending`` or you cannot SSH to it. " +"Sometimes the image itself is the problem. For example, when you use flat " +"manager networking, you do not have a DHCP server and certain images do not " +"support interface injection; you cannot connect to them. The fix for this " +"problem is to use an image that does support this method, such as Ubuntu, " +"which obtains an IP address correctly with FlatManager network settings." msgstr "" -#: ../common/get_started_database_service.rst:59 -#: ../common/get_started_database_service.rst:58 -msgid "``trove-taskmanager`` service" +#: ../common/support-compute.rst:123 +msgid "" +"To troubleshoot other possible problems with an instance, such as an " +"instance that stays in a spawning state, check the directory for the " +"particular instance under :file:`/var/lib/nova/instances` on the ``nova-" +"compute`` host and make sure that these files are present:" msgstr "" -#: ../common/cli_install_openstack_command_line_clients.rst:164 -#: ../common/cli_install_openstack_command_line_clients.rst:170 -#: ../common/cli_install_openstack_command_line_clients.rst:172 -#: ../common/cli_install_openstack_command_line_clients.rst:174 -msgid "``trove`` - Database service API" +#: ../common/support-compute.rst:128 +msgid ":file:`libvirt.xml`" msgstr "" -#: ../common/cli_install_openstack_command_line_clients.rst:176 -msgid "``tuskar`` - Deployment service API" +#: ../common/support-compute.rst:129 +msgid ":file:`disk`" msgstr "" -#: ../common/glossary.rst:22 -msgid "absolute limit" +#: ../common/support-compute.rst:130 +msgid ":file:`disk-raw`" msgstr "" -#: ../common/glossary.rst:27 -msgid "access control list" +#: ../common/support-compute.rst:131 +msgid ":file:`kernel`" msgstr "" -#: ../common/glossary.rst:36 -msgid "access key" +#: ../common/support-compute.rst:132 +msgid ":file:`ramdisk`" msgstr "" -#: ../common/glossary.rst:41 -msgid "account" +#: ../common/support-compute.rst:133 +msgid ":file:`console.log`, after the instance starts." msgstr "" -#: ../common/glossary.rst:47 -msgid "account auditor" +#: ../common/support-compute.rst:135 +msgid "" +"If any files are missing, empty, or very small, the ``nova-compute`` service " +"did not successfully download the images from the Image Service." msgstr "" -#: ../common/glossary.rst:53 -msgid "account database" +#: ../common/support-compute.rst:135 +msgid "" +"If any files are missing, empty, or very small, the ``nova-compute`` service " +"did not successfully download the images from the Image service." msgstr "" -#: ../common/glossary.rst:58 -msgid "account reaper" +#: ../common/support-compute.rst:138 +msgid "" +"Also check :file:`nova-compute.log` for exceptions. Sometimes they do not " +"appear in the console output." msgstr "" -#: ../common/glossary.rst:63 -msgid "account server" +#: ../common/support-compute.rst:141 +msgid "" +"Next, check the log file for the instance in the :file:`/var/log/libvirt/" +"qemu` directory to see if it exists and has any useful error messages in it." msgstr "" -#: ../common/glossary.rst:68 -msgid "account service" +#: ../common/support-compute.rst:144 +msgid "" +"Finally, from the :file:`/var/lib/nova/instances` directory for the " +"instance, see if this command returns an error::" msgstr "" -#: ../common/glossary.rst:74 -msgid "accounting" +#: ../common/support-compute.rst:149 +msgid "**Empty log output for Linux instances**" msgstr "" -#: ../common/glossary.rst:83 -msgid "active/active configuration" +#: ../common/support-compute.rst:151 +msgid "" +"You can view the log output of running instances from either the :guilabel:" +"`Log` tab of the dashboard or the output of :command:`nova console-log`. In " +"some cases, the log output of a running Linux instance will be empty or only " +"display a single character (for example, the `?` character)." msgstr "" -#: ../common/glossary.rst:94 -msgid "active/passive configuration" +#: ../common/support-compute.rst:157 +msgid "" +"This occurs when the Compute service attempts to retrieve the log output of " +"the instance via a serial console while the instance itself is not " +"configured to send output to the console. To rectify this, append the " +"following parameters to kernel arguments specified in the instance's boot " +"loader::" msgstr "" -#: ../common/glossary.rst:100 -msgid "address pool" +#: ../common/support-compute.rst:165 +msgid "" +"Upon rebooting, the instance will be configured to send output to the " +"Compute service." msgstr "" -#: ../common/glossary.rst:106 -msgid "admin API" +#: ../common/support-compute.rst:172 +msgid "Reset the state of an instance" msgstr "" -#: ../common/glossary.rst:113 -msgid "admin server" +#: ../common/support-compute.rst:174 +msgid "" +"If an instance remains in an intermediate state, such as ``deleting``, you " +"can use the :command:`nova reset-state` command to manually reset the state " +"of an instance to an error state. You can then delete the instance. For " +"example::" msgstr "" -#: ../common/glossary.rst:129 -msgid "alert" +#: ../common/support-compute.rst:181 +msgid "" +"You can also use the :option:`--active` parameter to force the instance back " +"to an active state instead of an error state. For example::" msgstr "" -#: ../common/glossary.rst:136 -msgid "allocate" +#: ../common/support-compute.rst:190 +msgid "Injection problems" msgstr "" -#: ../common/glossary.rst:217 -msgid "applet" +#: ../common/support-compute.rst:192 +msgid "" +"If instances do not boot or boot slowly, investigate file injection as a " +"cause." msgstr "" -#: ../common/glossary.rst:235 -msgid "application server" +#: ../common/support-compute.rst:194 +msgid "" +"To disable injection in libvirt, set the following in :file:`nova.conf`:" msgstr "" -#: ../common/glossary.rst:251 -msgid "arptables" +#: ../common/support-compute.rst:202 +msgid "" +"If you have not enabled the configuration drive and you want to make user-" +"specified files available from the metadata server for to improve " +"performance and avoid boot failure if injection fails, you must disable " +"injection." msgstr "" -#: ../common/app_support.rst:91 ../common/app_support.rst:88 -#: ../common/app_support.rst:86 -msgid "ask.openstack.org" +#: ../common/support-compute.rst:212 +msgid "Disable live snapshotting" msgstr "" -#: ../common/glossary.rst:258 -msgid "associate" +#: ../common/support-compute.rst:214 +msgid "" +"If you use libvirt version ``1.2.2``, you may experience problems with live " +"snapshots creation. Occasionally, libvirt of the specified version fails to " +"perform the live snapshotting under load that presupposes a concurrent " +"creation of multiple snapshots." msgstr "" -#: ../common/glossary.rst:273 -msgid "attach" -msgstr "" - -#: ../common/glossary.rst:279 -msgid "attachment (network)" -msgstr "" - -#: ../common/glossary.rst:284 -msgid "auditing" -msgstr "" - -#: ../common/glossary.rst:289 -msgid "auditor" -msgstr "" - -#: ../common/glossary.rst:302 -msgid "auth node" -msgstr "" - -#: ../common/glossary.rst:307 -msgid "authentication" -msgstr "" - -#: ../common/glossary.rst:313 -msgid "authentication token" -msgstr "" - -#: ../common/glossary.rst:324 -msgid "authorization" -msgstr "" - -#: ../common/glossary.rst:329 -msgid "authorization node" -msgstr "" - -#: ../common/glossary.rst:344 -msgid "auto declare" -msgstr "" - -#: ../common/glossary.rst:349 -msgid "availability zone" -msgstr "" - -#: ../common/glossary.rst:365 -msgid "back end" -msgstr "" - -#: ../common/glossary.rst:371 -msgid "back-end catalog" -msgstr "" - -#: ../common/glossary.rst:378 -msgid "back-end store" -msgstr "" - -#: ../common/glossary.rst:386 -msgid "bandwidth" -msgstr "" - -#: ../common/glossary.rst:392 ../common/cli_overview.rst:58 -#: ../common/cli_overview.rst:62 ../common/cli_overview.rst:65 -msgid "barbican" -msgstr "" - -#: ../common/glossary.rst:396 -msgid "bare" -msgstr "" - -#: ../common/glossary.rst:406 -msgid "base image" -msgstr "" - -#: ../common/glossary.rst:435 -msgid "binary" -msgstr "" - -#: ../common/glossary.rst:440 -msgid "bit" -msgstr "" - -#: ../common/glossary.rst:445 -msgid "bits per second (BPS)" -msgstr "" - -#: ../common/glossary.rst:450 -msgid "block device" -msgstr "" - -#: ../common/glossary.rst:456 -msgid "block migration" -msgstr "" - -#: ../common/glossary.rst:483 -msgid "bootable disk image" -msgstr "" - -#: ../common/glossary.rst:502 -msgid "browser" -msgstr "" - -#: ../common/glossary.rst:507 -msgid "builder file" -msgstr "" - -#: ../common/glossary.rst:513 -msgid "bursting" -msgstr "" - -#: ../common/glossary.rst:519 -msgid "button class" -msgstr "" - -#: ../common/glossary.rst:526 -msgid "byte" -msgstr "" - -#: ../common/glossary.rst:544 -msgid "cache pruner" -msgstr "" - -#: ../common/glossary.rst:571 -msgid "capability" -msgstr "" - -#: ../common/glossary.rst:577 -msgid "capacity cache" -msgstr "" - -#: ../common/glossary.rst:583 -msgid "capacity updater" -msgstr "" - -#: ../common/glossary.rst:593 -msgid "catalog" -msgstr "" - -#: ../common/glossary.rst:598 -msgid "catalog service" -msgstr "" - -#: ../common/glossary.rst:603 ../common/cli_overview.rst:72 -#: ../common/cli_overview.rst:81 ../common/cli_overview.rst:84 -#: ../common/cli_overview.rst:88 ../common/cli_overview.rst:91 -msgid "ceilometer" -msgstr "" - -#: ../common/glossary.rst:609 -msgid "cell" -msgstr "" - -#: ../common/glossary.rst:616 -msgid "cell forwarding" -msgstr "" - -#: ../common/glossary.rst:622 -msgid "cell manager" -msgstr "" - -#: ../common/glossary.rst:642 -msgid "certificate authority" -msgstr "" - -#: ../common/glossary.rst:651 -msgid "chance scheduler" -msgstr "" - -#: ../common/glossary.rst:656 -msgid "changes since" -msgstr "" - -#: ../common/glossary.rst:667 -msgid "child cell" -msgstr "" - -#: ../common/glossary.rst:675 ../common/cli_overview.rst:34 -#: ../common/cli_overview.rst:37 -msgid "cinder" -msgstr "" - -#: ../common/get_started_block_storage.rst:16 -#: ../common/get_started_block_storage.rst:15 -msgid "cinder-api" -msgstr "" - -#: ../common/get_started_block_storage.rst:34 -#: ../common/get_started_block_storage.rst:33 -msgid "cinder-backup daemon" -msgstr "" - -#: ../common/get_started_block_storage.rst:28 -#: ../common/get_started_block_storage.rst:27 -msgid "cinder-scheduler daemon" -msgstr "" - -#: ../common/get_started_block_storage.rst:24 -#: ../common/get_started_block_storage.rst:23 -msgid "cinder-volume" -msgstr "" - -#: ../common/glossary.rst:690 -msgid "cloud architect" -msgstr "" - -#: ../common/glossary.rst:695 -msgid "cloud computing" -msgstr "" - -#: ../common/glossary.rst:702 -msgid "cloud controller" -msgstr "" - -#: ../common/glossary.rst:709 -msgid "cloud controller node" -msgstr "" - -#: ../common/glossary.rst:725 -msgid "cloud-init" -msgstr "" - -#: ../common/glossary.rst:732 -msgid "cloudadmin" -msgstr "" - -#: ../common/glossary.rst:742 -msgid "cloudpipe" -msgstr "" - -#: ../common/glossary.rst:747 -msgid "cloudpipe image" -msgstr "" - -#: ../common/glossary.rst:760 -msgid "command filter" -msgstr "" - -#: ../common/glossary.rst:765 -msgid "community project" -msgstr "" - -#: ../common/glossary.rst:772 -msgid "compression" -msgstr "" - -#: ../common/glossary.rst:791 -msgid "compute controller" -msgstr "" - -#: ../common/glossary.rst:796 -msgid "compute host" -msgstr "" - -#: ../common/glossary.rst:800 -msgid "compute node" -msgstr "" - -#: ../common/glossary.rst:810 -msgid "compute worker" -msgstr "" - -#: ../common/glossary.rst:816 -msgid "concatenated object" -msgstr "" - -#: ../common/glossary.rst:821 -msgid "conductor" -msgstr "" - -#: ../common/glossary.rst:756 -msgid "congress" -msgstr "" - -#: ../common/glossary.rst:828 -msgid "consistency window" -msgstr "" - -#: ../common/glossary.rst:833 -msgid "console log" -msgstr "" - -#: ../common/glossary.rst:837 -msgid "container" -msgstr "" - -#: ../common/glossary.rst:843 -msgid "container auditor" -msgstr "" - -#: ../common/glossary.rst:849 -msgid "container database" -msgstr "" - -#: ../common/glossary.rst:855 -msgid "container format" -msgstr "" - -#: ../common/glossary.rst:861 -msgid "container server" -msgstr "" - -#: ../common/glossary.rst:871 -msgid "container service" -msgstr "" - -#: ../common/glossary.rst:876 -msgid "content delivery network (CDN)" -msgstr "" - -#: ../common/glossary.rst:882 -msgid "controller node" -msgstr "" - -#: ../common/glossary.rst:886 -msgid "core API" -msgstr "" - -#: ../common/glossary.rst:892 -msgid "core project" -msgstr "" - -#: ../common/glossary.rst:903 -msgid "cost" -msgstr "" - -#: ../common/glossary.rst:909 -msgid "credentials" -msgstr "" - -#: ../common/glossary.rst:930 -msgid "current workload" -msgstr "" - -#: ../common/glossary.rst:936 -msgid "customer" -msgstr "" - -#: ../common/glossary.rst:940 -msgid "customization module" -msgstr "" - -#: ../common/glossary.rst:945 -msgid "daemon" -msgstr "" - -#: ../common/glossary.rst:959 -msgid "dashboard" -msgstr "" - -#: ../common/glossary.rst:964 -msgid "data encryption" -msgstr "" - -#: ../common/glossary.rst:972 -msgid "database ID" -msgstr "" - -#: ../common/glossary.rst:977 -msgid "database replicator" -msgstr "" - -#: ../common/glossary.rst:995 -msgid "deallocate" -msgstr "" - -#: ../common/glossary.rst:1005 -msgid "deduplication" -msgstr "" - -#: ../common/glossary.rst:1011 -msgid "default panel" -msgstr "" - -#: ../common/glossary.rst:1016 -msgid "default tenant" -msgstr "" - -#: ../common/glossary.rst:1021 -msgid "default token" -msgstr "" - -#: ../common/glossary.rst:1026 -msgid "delayed delete" -msgstr "" - -#: ../common/glossary.rst:1031 -msgid "delivery mode" -msgstr "" - -#: ../common/glossary.rst:1036 -msgid "denial of service (DoS)" -msgstr "" - -#: ../common/glossary.rst:1042 -msgid "deprecated auth" -msgstr "" - -#: ../common/glossary.rst:1059 -msgid "developer" -msgstr "" - -#: ../common/glossary.rst:1064 -msgid "device ID" -msgstr "" - -#: ../common/glossary.rst:1069 -msgid "device weight" -msgstr "" - -#: ../common/glossary.rst:1104 -msgid "direct consumer" -msgstr "" - -#: ../common/glossary.rst:1110 -msgid "direct exchange" -msgstr "" - -#: ../common/glossary.rst:1116 -msgid "direct publisher" -msgstr "" - -#: ../common/glossary.rst:1121 -msgid "disassociate" -msgstr "" - -#: ../common/glossary.rst:1127 -msgid "disk encryption" -msgstr "" - -#: ../common/glossary.rst:1132 -msgid "disk format" -msgstr "" - -#: ../common/glossary.rst:1138 -msgid "dispersion" -msgstr "" - -#: ../common/glossary.rst:1143 -msgid "distributed virtual router (DVR)" -msgstr "" - -#: ../common/glossary.rst:1171 -msgid "dnsmasq" -msgstr "" - -#: ../common/glossary.rst:1176 -msgid "domain" -msgstr "" - -#: ../common/glossary.rst:1207 ../common/glossary.rst:1208 -msgid "download" -msgstr "" - -#: ../common/glossary.rst:1216 ../common/glossary.rst:1217 -msgid "durable exchange" -msgstr "" - -#: ../common/glossary.rst:1221 ../common/glossary.rst:1222 -msgid "durable queue" -msgstr "" - -#: ../common/cli_manage_images.rst:256 ../common/cli_manage_images.rst:266 -msgid "e1000" -msgstr "" - -#: ../common/glossary.rst:1237 ../common/glossary.rst:1238 -msgid "east-west traffic" -msgstr "" - -#: ../common/glossary.rst:1247 ../common/glossary.rst:1343 -#: ../common/glossary.rst:1248 ../common/glossary.rst:1344 -msgid "ebtables" -msgstr "" - -#: ../common/glossary.rst:1295 ../common/glossary.rst:1296 -msgid "encapsulation" -msgstr "" - -#: ../common/glossary.rst:1282 ../common/glossary.rst:1283 -msgid "encryption" -msgstr "" - -#: ../common/glossary.rst:1287 ../common/glossary.rst:1288 -msgid "endpoint" -msgstr "" - -#: ../common/glossary.rst:1291 ../common/glossary.rst:1292 -msgid "endpoint registry" -msgstr "" - -#: ../common/glossary.rst:1301 ../common/glossary.rst:1302 -msgid "endpoint template" -msgstr "" - -#: ../common/glossary.rst:1307 ../common/glossary.rst:1308 -msgid "entity" -msgstr "" - -#: ../common/glossary.rst:1314 ../common/glossary.rst:1315 -msgid "ephemeral image" -msgstr "" - -#: ../common/glossary.rst:1320 ../common/glossary.rst:1321 -msgid "ephemeral volume" -msgstr "" - -#: ../common/glossary.rst:1355 ../common/glossary.rst:1356 -msgid "euca2ools" -msgstr "" - -#: ../common/get_started_compute.rst:118 ../common/get_started_compute.rst:117 -msgid "euca2ools client" -msgstr "" - -#: ../common/glossary.rst:1372 ../common/glossary.rst:1373 -msgid "evacuate" -msgstr "" - -#: ../common/glossary.rst:1378 ../common/glossary.rst:1379 -msgid "exchange" -msgstr "" - -#: ../common/glossary.rst:1382 ../common/glossary.rst:1383 -msgid "exchange type" -msgstr "" - -#: ../common/glossary.rst:1386 ../common/glossary.rst:1387 -msgid "exclusive queue" -msgstr "" - -#: ../common/glossary.rst:1391 ../common/glossary.rst:1392 -msgid "extended attributes (xattr)" -msgstr "" - -#: ../common/glossary.rst:1398 ../common/glossary.rst:1399 -msgid "extension" -msgstr "" - -#: ../common/glossary.rst:1404 ../common/glossary.rst:1405 -msgid "external network" -msgstr "" - -#: ../common/glossary.rst:1409 ../common/glossary.rst:1410 -msgid "extra specs" -msgstr "" - -#: ../common/glossary.rst:1420 ../common/glossary.rst:1421 -msgid "fan-out exchange" -msgstr "" - -#: ../common/glossary.rst:1426 ../common/glossary.rst:1427 -msgid "federated identity" -msgstr "" - -#: ../common/glossary.rst:1444 ../common/glossary.rst:1445 -msgid "fill-first scheduler" -msgstr "" - -#: ../common/glossary.rst:1449 ../common/glossary.rst:1450 -msgid "filter" -msgstr "" - -#: ../common/glossary.rst:1454 ../common/glossary.rst:1455 -msgid "firewall" -msgstr "" - -#: ../common/glossary.rst:1465 ../common/glossary.rst:1466 -msgid "fixed IP address" -msgstr "" - -#: ../common/glossary.rst:1478 ../common/glossary.rst:1479 -msgid "flat mode injection" -msgstr "" - -#: ../common/glossary.rst:1484 ../common/glossary.rst:1485 -msgid "flat network" -msgstr "" - -#: ../common/glossary.rst:1497 ../common/glossary.rst:1498 -msgid "flavor" -msgstr "" - -#: ../common/glossary.rst:1501 ../common/glossary.rst:1502 -msgid "flavor ID" -msgstr "" - -#: ../common/glossary.rst:1506 ../common/glossary.rst:1507 -msgid "floating IP address" -msgstr "" - -#: ../common/glossary.rst:1530 ../common/glossary.rst:1531 -msgid "front end" -msgstr "" - -#: ../common/glossary.rst:1535 ../common/glossary.rst:1536 -msgid "gateway" -msgstr "" - -#: ../common/glossary.rst:1540 ../common/glossary.rst:1541 -msgid "generic receive offload (GRO)" -msgstr "" - -#: ../common/glossary.rst:1546 ../common/glossary.rst:1547 -msgid "generic routing encapsulation (GRE)" -msgstr "" - -#: ../common/glossary.rst:1551 ../common/cli_overview.rst:49 -#: ../common/cli_overview.rst:55 ../common/glossary.rst:1552 -#: ../common/cli_overview.rst:59 ../common/cli_overview.rst:62 -msgid "glance" -msgstr "" - -#: ../common/glossary.rst:1555 ../common/glossary.rst:1556 -msgid "glance API server" -msgstr "" - -#: ../common/glossary.rst:1561 ../common/glossary.rst:1562 -msgid "glance registry" -msgstr "" - -#: ../common/get_started_image_service.rst:22 -#: ../common/get_started_image_service.rst:19 -msgid "glance-api" -msgstr "" - -#: ../common/get_started_image_service.rst:31 -#: ../common/get_started_image_service.rst:28 -msgid "glance-registry" -msgstr "" - -#: ../common/glossary.rst:1565 ../common/glossary.rst:1566 -msgid "global endpoint template" -msgstr "" - -#: ../common/glossary.rst:1575 ../common/glossary.rst:1576 -msgid "golden image" -msgstr "" - -#: ../common/glossary.rst:1611 ../common/glossary.rst:1617 -msgid "guest OS" -msgstr "" - -#: ../common/glossary.rst:1621 ../common/glossary.rst:1627 -msgid "handover" -msgstr "" - -#: ../common/glossary.rst:1626 ../common/glossary.rst:1632 -msgid "hard reboot" -msgstr "" - -#: ../common/glossary.rst:1647 ../common/glossary.rst:1653 -msgid "health monitor" -msgstr "" - -#: ../common/glossary.rst:1638 ../common/cli_overview.rst:65 -#: ../common/cli_overview.rst:71 ../common/glossary.rst:1644 -#: ../common/cli_overview.rst:74 ../common/cli_overview.rst:78 -#: ../common/cli_overview.rst:81 -msgid "heat" -msgstr "" - -#: ../common/glossary.rst:1656 ../common/glossary.rst:1662 -msgid "high availability (HA)" -msgstr "" - -#: ../common/glossary.rst:1664 ../common/glossary.rst:1670 -msgid "horizon" -msgstr "" - -#: ../common/glossary.rst:1669 ../common/glossary.rst:1675 -msgid "horizon plug-in" -msgstr "" - -#: ../common/glossary.rst:1673 ../common/glossary.rst:1679 -msgid "host" -msgstr "" - -#: ../common/glossary.rst:1677 ../common/glossary.rst:1683 -msgid "host aggregate" -msgstr "" - -#: ../common/glossary.rst:1706 ../common/glossary.rst:1712 -msgid "hybrid cloud" -msgstr "" - -#: ../common/glossary.rst:1719 ../common/glossary.rst:1725 -msgid "hyperlink" -msgstr "" - -#: ../common/glossary.rst:1736 ../common/glossary.rst:1742 -msgid "hypervisor" -msgstr "" - -#: ../common/glossary.rst:1741 ../common/glossary.rst:1747 -msgid "hypervisor pool" -msgstr "" - -#: ../common/glossary.rst:2009 ../common/glossary.rst:2015 -msgid "iSCSI" -msgstr "" - -#: ../common/cli_manage_images.rst:237 ../common/cli_manage_images.rst:243 -msgid "ide" -msgstr "" - -#: ../common/glossary.rst:1782 ../common/glossary.rst:1788 -msgid "identity provider" -msgstr "" - -#: ../common/glossary.rst:1805 ../common/glossary.rst:1811 -msgid "image" -msgstr "" - -#: ../common/glossary.rst:1824 ../common/glossary.rst:1830 -msgid "image ID" -msgstr "" - -#: ../common/glossary.rst:1864 ../common/glossary.rst:1870 -msgid "image UUID" -msgstr "" - -#: ../common/glossary.rst:1818 ../common/glossary.rst:1824 -msgid "image cache" -msgstr "" - -#: ../common/glossary.rst:1829 ../common/glossary.rst:1835 -msgid "image membership" -msgstr "" - -#: ../common/glossary.rst:1834 ../common/glossary.rst:1840 -msgid "image owner" -msgstr "" - -#: ../common/glossary.rst:1839 ../common/glossary.rst:1845 -msgid "image registry" -msgstr "" - -#: ../common/glossary.rst:1854 ../common/glossary.rst:1860 -msgid "image status" -msgstr "" - -#: ../common/glossary.rst:1859 ../common/glossary.rst:1865 -msgid "image store" -msgstr "" - -#: ../common/glossary.rst:1869 ../common/glossary.rst:1875 -msgid "incubated project" -msgstr "" - -#: ../common/glossary.rst:1874 ../common/glossary.rst:1880 -msgid "ingress filtering" -msgstr "" - -#: ../common/glossary.rst:1885 ../common/glossary.rst:1891 -msgid "injection" -msgstr "" - -#: ../common/glossary.rst:1890 ../common/glossary.rst:1896 -msgid "instance" -msgstr "" - -#: ../common/glossary.rst:1895 ../common/glossary.rst:1901 -msgid "instance ID" -msgstr "" - -#: ../common/glossary.rst:1918 ../common/glossary.rst:1924 -msgid "instance UUID" -msgstr "" - -#: ../common/glossary.rst:1899 ../common/glossary.rst:1905 -msgid "instance state" -msgstr "" - -#: ../common/glossary.rst:1903 ../common/glossary.rst:1909 -msgid "instance tunnels network" -msgstr "" - -#: ../common/glossary.rst:1908 ../common/glossary.rst:1914 -msgid "instance type" -msgstr "" - -#: ../common/glossary.rst:1914 ../common/glossary.rst:1920 -msgid "instance type ID" -msgstr "" - -#: ../common/glossary.rst:1922 ../common/glossary.rst:1928 -msgid "interface" -msgstr "" - -#: ../common/glossary.rst:1927 ../common/glossary.rst:1933 -msgid "interface ID" -msgstr "" - -#: ../common/glossary.rst:1985 ../common/glossary.rst:1991 -msgid "ip6tables" -msgstr "" - -#: ../common/glossary.rst:1992 ../common/glossary.rst:1998 -msgid "ipset" -msgstr "" - -#: ../common/glossary.rst:1999 ../common/glossary.rst:2005 -msgid "iptables" -msgstr "" - -#: ../common/glossary.rst:1947 ../common/glossary.rst:1953 -msgid "ironic" -msgstr "" - -#: ../common/glossary.rst:2019 ../common/glossary.rst:2025 -msgid "itsec" -msgstr "" - -#: ../common/glossary.rst:2042 ../common/glossary.rst:2048 -msgid "jumbo frame" -msgstr "" - -#: ../common/glossary.rst:2053 ../common/glossary.rst:2059 -msgid "kernel-based VM (KVM)" -msgstr "" - -#: ../common/glossary.rst:2075 ../common/cli_overview.rst:44 -#: ../common/cli_overview.rst:50 ../common/glossary.rst:2081 -#: ../common/cli_overview.rst:54 ../common/cli_overview.rst:57 -msgid "keystone" -msgstr "" - -#: ../common/glossary.rst:2093 ../common/glossary.rst:2099 -msgid "large object" -msgstr "" - -#: ../common/glossary.rst:2131 ../common/glossary.rst:2137 -msgid "libvirt" -msgstr "" - -#: ../common/get_started_compute.rst:45 ../common/get_started_compute.rst:44 -msgid "libvirt for KVM or QEMU" -msgstr "" - -#: ../common/cli_manage_images.rst:235 ../common/cli_manage_images.rst:254 -msgid "libvirt\\_type setting" -msgstr "" - -#: ../common/glossary.rst:2150 ../common/glossary.rst:2156 -msgid "live migration" -msgstr "" - -#: ../common/glossary.rst:2156 ../common/glossary.rst:2162 -msgid "load balancer" -msgstr "" - -#: ../common/glossary.rst:2163 ../common/glossary.rst:2169 -msgid "load balancing" -msgstr "" - -#: ../common/glossary.rst:2179 ../common/glossary.rst:2185 -msgid "magnetoDB" -msgstr "" - -#: ../common/glossary.rst:2184 ../common/cli_overview.rst:44 -#: ../common/glossary.rst:2190 ../common/glossary.rst:2179 -msgid "magnum" -msgstr "" - -#: ../common/glossary.rst:2189 ../common/glossary.rst:2195 -#: ../common/glossary.rst:2184 -msgid "management API" -msgstr "" - -#: ../common/glossary.rst:2193 ../common/glossary.rst:2199 -#: ../common/glossary.rst:2188 -msgid "management network" -msgstr "" - -#: ../common/glossary.rst:2198 ../common/glossary.rst:2204 -#: ../common/glossary.rst:2193 -msgid "manager" -msgstr "" - -#: ../common/glossary.rst:2203 ../common/glossary.rst:2209 -#: ../common/glossary.rst:2198 -msgid "manifest" -msgstr "" - -#: ../common/glossary.rst:2208 ../common/glossary.rst:2214 -#: ../common/glossary.rst:2203 -msgid "manifest object" -msgstr "" - -#: ../common/glossary.rst:2213 ../common/cli_overview.rst:78 -#: ../common/glossary.rst:2219 ../common/cli_overview.rst:81 -#: ../common/cli_overview.rst:85 ../common/glossary.rst:2208 -#: ../common/cli_overview.rst:88 -msgid "manila" -msgstr "" - -#: ../common/glossary.rst:2218 ../common/glossary.rst:2224 -#: ../common/glossary.rst:2213 -msgid "maximum transmission unit (MTU)" -msgstr "" - -#: ../common/glossary.rst:2223 ../common/glossary.rst:2229 -#: ../common/glossary.rst:2218 -msgid "mechanism driver" -msgstr "" - -#: ../common/glossary.rst:2230 ../common/glossary.rst:2237 -#: ../common/glossary.rst:2236 ../common/glossary.rst:2225 -msgid "melange" -msgstr "" - -#: ../common/glossary.rst:2235 ../common/glossary.rst:2242 -#: ../common/glossary.rst:2241 ../common/glossary.rst:2230 -msgid "membership" -msgstr "" - -#: ../common/glossary.rst:2240 ../common/glossary.rst:2247 -#: ../common/glossary.rst:2246 ../common/glossary.rst:2235 -msgid "membership list" -msgstr "" - -#: ../common/glossary.rst:2245 ../common/glossary.rst:2252 -#: ../common/glossary.rst:2251 ../common/glossary.rst:2240 -msgid "memcached" -msgstr "" - -#: ../common/glossary.rst:2250 ../common/glossary.rst:2257 -#: ../common/glossary.rst:2256 ../common/glossary.rst:2245 -msgid "memory overcommit" -msgstr "" - -#: ../common/glossary.rst:2257 ../common/glossary.rst:2264 -#: ../common/glossary.rst:2263 ../common/glossary.rst:2252 -msgid "message broker" -msgstr "" - -#: ../common/glossary.rst:2262 ../common/glossary.rst:2269 -#: ../common/glossary.rst:2268 ../common/glossary.rst:2257 -msgid "message bus" -msgstr "" - -#: ../common/glossary.rst:2267 ../common/glossary.rst:2274 -#: ../common/glossary.rst:2273 ../common/glossary.rst:2262 -msgid "message queue" -msgstr "" - -#: ../common/glossary.rst:2290 ../common/glossary.rst:2297 -#: ../common/glossary.rst:2296 ../common/glossary.rst:2285 -msgid "migration" -msgstr "" - -#: ../common/glossary.rst:2295 ../common/glossary.rst:2302 -#: ../common/glossary.rst:2301 ../common/cli_overview.rst:92 -#: ../common/glossary.rst:2290 ../common/cli_overview.rst:95 -msgid "mistral" -msgstr "" - -#: ../common/glossary.rst:2330 ../common/glossary.rst:2337 -#: ../common/glossary.rst:2336 ../common/glossary.rst:2342 -#: ../common/glossary.rst:2331 -msgid "multi-factor authentication" -msgstr "" - -#: ../common/glossary.rst:2299 ../common/glossary.rst:2306 -#: ../common/glossary.rst:2305 ../common/glossary.rst:2311 -#: ../common/glossary.rst:2300 -msgid "multi-host" -msgstr "" - -#: ../common/glossary.rst:2306 ../common/glossary.rst:2313 -#: ../common/glossary.rst:2312 ../common/glossary.rst:2318 -#: ../common/glossary.rst:2307 -msgid "multinic" -msgstr "" - -#: ../common/glossary.rst:2311 ../common/glossary.rst:2318 -#: ../common/glossary.rst:2317 ../common/cli_overview.rst:34 -#: ../common/glossary.rst:2323 ../common/glossary.rst:2312 -msgid "murano" -msgstr "" - -#: ../common/cli_manage_images.rst:258 ../common/cli_manage_images.rst:270 -msgid "ne2k\\_pci" -msgstr "" - -#: ../common/glossary.rst:2353 ../common/glossary.rst:2360 -#: ../common/glossary.rst:2359 ../common/glossary.rst:2365 -#: ../common/glossary.rst:2354 -msgid "netadmin" -msgstr "" - -#: ../common/cli_manage_images.rst:268 -msgid "netfront" -msgstr "" - -#: ../common/glossary.rst:2365 ../common/glossary.rst:2372 -#: ../common/glossary.rst:2371 ../common/glossary.rst:2377 -#: ../common/glossary.rst:2366 -msgid "network" -msgstr "" - -#: ../common/glossary.rst:2388 ../common/glossary.rst:2395 -#: ../common/glossary.rst:2394 ../common/glossary.rst:2400 -#: ../common/glossary.rst:2401 ../common/glossary.rst:2390 -msgid "network ID" -msgstr "" - -#: ../common/glossary.rst:2412 ../common/glossary.rst:2419 -#: ../common/glossary.rst:2418 ../common/glossary.rst:2424 -#: ../common/glossary.rst:2426 ../common/glossary.rst:2415 -msgid "network UUID" -msgstr "" - -#: ../common/glossary.rst:2377 ../common/glossary.rst:2384 -#: ../common/glossary.rst:2383 ../common/glossary.rst:2389 -#: ../common/glossary.rst:2390 ../common/glossary.rst:2379 -msgid "network controller" -msgstr "" - -#: ../common/glossary.rst:2393 ../common/glossary.rst:2400 -#: ../common/glossary.rst:2399 ../common/glossary.rst:2405 -#: ../common/glossary.rst:2406 ../common/glossary.rst:2395 -msgid "network manager" -msgstr "" - -#: ../common/glossary.rst:2341 ../common/glossary.rst:2348 -#: ../common/glossary.rst:2347 ../common/glossary.rst:2353 -#: ../common/glossary.rst:2342 -msgid "network namespace" -msgstr "" - -#: ../common/glossary.rst:2398 ../common/glossary.rst:2405 -#: ../common/glossary.rst:2404 ../common/glossary.rst:2410 -#: ../common/glossary.rst:2411 ../common/glossary.rst:2400 -msgid "network node" -msgstr "" - -#: ../common/glossary.rst:2402 ../common/glossary.rst:2409 -#: ../common/glossary.rst:2408 ../common/glossary.rst:2414 -#: ../common/glossary.rst:2415 ../common/glossary.rst:2404 -msgid "network segment" -msgstr "" - -#: ../common/glossary.rst:2416 ../common/glossary.rst:2423 -#: ../common/glossary.rst:2422 ../common/glossary.rst:2428 -#: ../common/glossary.rst:2430 ../common/glossary.rst:2419 -msgid "network worker" -msgstr "" - -#: ../common/glossary.rst:2433 ../common/cli_overview.rst:52 -#: ../common/glossary.rst:2440 ../common/glossary.rst:2439 -#: ../common/cli_overview.rst:58 ../common/glossary.rst:2445 -#: ../common/cli_overview.rst:61 ../common/glossary.rst:2447 -#: ../common/cli_overview.rst:65 ../common/glossary.rst:2436 -#: ../common/cli_overview.rst:68 -msgid "neutron" -msgstr "" - -#: ../common/glossary.rst:2438 ../common/glossary.rst:2445 -#: ../common/glossary.rst:2444 ../common/glossary.rst:2450 -#: ../common/glossary.rst:2452 ../common/glossary.rst:2441 -msgid "neutron API" -msgstr "" - -#: ../common/glossary.rst:2442 ../common/glossary.rst:2449 -#: ../common/glossary.rst:2448 ../common/glossary.rst:2454 -#: ../common/glossary.rst:2456 ../common/glossary.rst:2445 -msgid "neutron manager" -msgstr "" - -#: ../common/glossary.rst:2447 ../common/glossary.rst:2454 -#: ../common/glossary.rst:2453 ../common/glossary.rst:2459 -#: ../common/glossary.rst:2461 ../common/glossary.rst:2450 -msgid "neutron plug-in" -msgstr "" - -#: ../common/get_started_openstack_networking.rst:15 -#: ../common/get_started_openstack_networking.rst:14 -msgid "neutron-server" -msgstr "" - -#: ../common/glossary.rst:2462 ../common/glossary.rst:2469 -#: ../common/glossary.rst:2468 ../common/glossary.rst:2474 -#: ../common/glossary.rst:2476 ../common/glossary.rst:2465 -msgid "node" -msgstr "" - -#: ../common/glossary.rst:2466 ../common/glossary.rst:2473 -#: ../common/glossary.rst:2472 ../common/glossary.rst:2478 -#: ../common/glossary.rst:2480 ../common/glossary.rst:2469 -msgid "non-durable exchange" -msgstr "" - -#: ../common/glossary.rst:2471 ../common/glossary.rst:2478 -#: ../common/glossary.rst:2477 ../common/glossary.rst:2483 -#: ../common/glossary.rst:2485 ../common/glossary.rst:2474 -msgid "non-durable queue" -msgstr "" - -#: ../common/glossary.rst:2476 ../common/glossary.rst:2483 -#: ../common/glossary.rst:2482 ../common/glossary.rst:2488 -#: ../common/glossary.rst:2490 ../common/glossary.rst:2479 -msgid "non-persistent volume" -msgstr "" - -#: ../common/glossary.rst:2480 ../common/glossary.rst:2487 -#: ../common/glossary.rst:2486 ../common/glossary.rst:2492 -#: ../common/glossary.rst:2494 ../common/glossary.rst:2483 -msgid "north-south traffic" -msgstr "" - -#: ../common/glossary.rst:2486 ../common/cli_overview.rst:37 -#: ../common/glossary.rst:2493 ../common/glossary.rst:2492 -#: ../common/cli_overview.rst:40 ../common/glossary.rst:2498 -#: ../common/glossary.rst:2500 ../common/glossary.rst:2489 -msgid "nova" -msgstr "" - -#: ../common/get_started_compute.rst:122 ../common/get_started_compute.rst:121 -msgid "nova client" -msgstr "" - -#: ../common/glossary.rst:2494 ../common/glossary.rst:2501 -#: ../common/glossary.rst:2500 ../common/glossary.rst:2506 -#: ../common/glossary.rst:2508 ../common/glossary.rst:2497 -msgid "nova-network" -msgstr "" - -#: ../common/get_started_compute.rst:111 ../common/get_started_compute.rst:110 -msgid "nova-objectstore daemon" -msgstr "" - -#: ../common/glossary.rst:2500 ../common/glossary.rst:2507 -#: ../common/glossary.rst:2506 ../common/glossary.rst:2512 -#: ../common/glossary.rst:2514 ../common/glossary.rst:2503 -msgid "object" -msgstr "" - -#: ../common/glossary.rst:2505 ../common/glossary.rst:2512 -#: ../common/glossary.rst:2511 ../common/glossary.rst:2517 -#: ../common/glossary.rst:2519 ../common/glossary.rst:2508 -msgid "object auditor" -msgstr "" - -#: ../common/glossary.rst:2510 ../common/glossary.rst:2517 -#: ../common/glossary.rst:2516 ../common/glossary.rst:2522 -#: ../common/glossary.rst:2524 ../common/glossary.rst:2513 -msgid "object expiration" -msgstr "" - -#: ../common/glossary.rst:2516 ../common/glossary.rst:2523 -#: ../common/glossary.rst:2522 ../common/glossary.rst:2528 -#: ../common/glossary.rst:2530 ../common/glossary.rst:2519 -msgid "object hash" -msgstr "" - -#: ../common/glossary.rst:2520 ../common/glossary.rst:2527 -#: ../common/glossary.rst:2526 ../common/glossary.rst:2532 -#: ../common/glossary.rst:2534 ../common/glossary.rst:2523 -msgid "object path hash" -msgstr "" - -#: ../common/glossary.rst:2525 ../common/glossary.rst:2532 -#: ../common/glossary.rst:2531 ../common/glossary.rst:2537 -#: ../common/glossary.rst:2539 ../common/glossary.rst:2528 -msgid "object replicator" -msgstr "" - -#: ../common/glossary.rst:2530 ../common/glossary.rst:2537 -#: ../common/glossary.rst:2536 ../common/glossary.rst:2542 -#: ../common/glossary.rst:2544 ../common/glossary.rst:2533 -msgid "object server" -msgstr "" - -#: ../common/glossary.rst:2549 ../common/glossary.rst:2556 -#: ../common/glossary.rst:2555 ../common/glossary.rst:2561 -#: ../common/glossary.rst:2563 ../common/glossary.rst:2552 -msgid "object versioning" -msgstr "" - -#: ../common/glossary.rst:2611 ../common/glossary.rst:2618 -#: ../common/glossary.rst:2624 ../common/glossary.rst:2626 -#: ../common/glossary.rst:2615 -msgid "openSUSE" -msgstr "" - -#: ../common/cli_overview.rst:80 ../common/cli_overview.rst:89 -#: ../common/cli_overview.rst:92 ../common/cli_overview.rst:95 -#: ../common/cli_overview.rst:98 -msgid "openstack" -msgstr "" - -#: ../common/glossary.rst:2615 ../common/glossary.rst:2622 -#: ../common/glossary.rst:2628 ../common/glossary.rst:2630 -#: ../common/glossary.rst:2619 -msgid "operator" -msgstr "" - -#: ../common/glossary.rst:2626 ../common/glossary.rst:2633 -#: ../common/glossary.rst:2639 ../common/glossary.rst:2641 -#: ../common/glossary.rst:2630 -msgid "orphan" -msgstr "" - -#: ../common/glossary.rst:2636 ../common/glossary.rst:2643 -#: ../common/glossary.rst:2649 ../common/glossary.rst:2651 -#: ../common/glossary.rst:2640 -msgid "parent cell" -msgstr "" - -#: ../common/glossary.rst:2642 ../common/glossary.rst:2649 -#: ../common/glossary.rst:2655 ../common/glossary.rst:2657 -#: ../common/glossary.rst:2646 -msgid "partition" -msgstr "" - -#: ../common/glossary.rst:2648 ../common/glossary.rst:2655 -#: ../common/glossary.rst:2661 ../common/glossary.rst:2663 -#: ../common/glossary.rst:2652 -msgid "partition index" -msgstr "" - -#: ../common/glossary.rst:2653 ../common/glossary.rst:2660 -#: ../common/glossary.rst:2666 ../common/glossary.rst:2668 -#: ../common/glossary.rst:2657 -msgid "partition shift value" -msgstr "" - -#: ../common/glossary.rst:2658 ../common/glossary.rst:2665 -#: ../common/glossary.rst:2671 ../common/glossary.rst:2673 -#: ../common/glossary.rst:2662 -msgid "path MTU discovery (PMTUD)" -msgstr "" - -#: ../common/glossary.rst:2663 ../common/glossary.rst:2670 -#: ../common/glossary.rst:2676 ../common/glossary.rst:2678 -#: ../common/glossary.rst:2667 -msgid "pause" -msgstr "" - -#: ../common/cli_manage_images.rst:260 ../common/cli_manage_images.rst:272 -msgid "pcnet" -msgstr "" - -#: ../common/glossary.rst:2673 ../common/glossary.rst:2680 -#: ../common/glossary.rst:2686 ../common/glossary.rst:2688 -#: ../common/glossary.rst:2677 -msgid "persistent message" -msgstr "" - -#: ../common/glossary.rst:2678 ../common/glossary.rst:2685 -#: ../common/glossary.rst:2691 ../common/glossary.rst:2693 -#: ../common/glossary.rst:2682 -msgid "persistent volume" -msgstr "" - -#: ../common/glossary.rst:2682 ../common/glossary.rst:2689 -#: ../common/glossary.rst:2695 ../common/glossary.rst:2697 -#: ../common/glossary.rst:2686 -msgid "personality file" -msgstr "" - -#: ../common/cli_install_openstack_command_line_clients.rst:42 -msgid "pip package" -msgstr "" - -#: ../common/glossary.rst:2695 ../common/glossary.rst:2702 -#: ../common/glossary.rst:2708 ../common/glossary.rst:2710 -#: ../common/glossary.rst:2699 -msgid "plug-in" -msgstr "" - -#: ../common/glossary.rst:2700 ../common/glossary.rst:2707 -#: ../common/glossary.rst:2713 ../common/glossary.rst:2715 -#: ../common/glossary.rst:2704 -msgid "policy service" -msgstr "" - -#: ../common/glossary.rst:2705 ../common/glossary.rst:2712 -#: ../common/glossary.rst:2718 ../common/glossary.rst:2720 -#: ../common/glossary.rst:2709 -msgid "pool" -msgstr "" - -#: ../common/glossary.rst:2713 ../common/glossary.rst:2720 -#: ../common/glossary.rst:2726 ../common/glossary.rst:2728 -#: ../common/glossary.rst:2717 -msgid "pool member" -msgstr "" - -#: ../common/glossary.rst:2718 ../common/glossary.rst:2725 -#: ../common/glossary.rst:2731 ../common/glossary.rst:2733 -#: ../common/glossary.rst:2722 -msgid "port" -msgstr "" - -#: ../common/glossary.rst:2723 ../common/glossary.rst:2730 -#: ../common/glossary.rst:2736 ../common/glossary.rst:2738 -#: ../common/glossary.rst:2727 -msgid "port UUID" -msgstr "" - -#: ../common/glossary.rst:2727 ../common/glossary.rst:2734 -#: ../common/glossary.rst:2740 ../common/glossary.rst:2742 -#: ../common/glossary.rst:2731 -msgid "preseed" -msgstr "" - -#: ../common/glossary.rst:2737 ../common/glossary.rst:2744 -#: ../common/glossary.rst:2750 ../common/glossary.rst:2752 -#: ../common/glossary.rst:2741 -msgid "private IP address" -msgstr "" - -#: ../common/glossary.rst:2732 ../common/glossary.rst:2739 -#: ../common/glossary.rst:2745 ../common/glossary.rst:2747 -#: ../common/glossary.rst:2736 -msgid "private image" -msgstr "" - -#: ../common/glossary.rst:2742 ../common/glossary.rst:2749 -#: ../common/glossary.rst:2755 ../common/glossary.rst:2757 -#: ../common/glossary.rst:2746 -msgid "private network" -msgstr "" - -#: ../common/glossary.rst:2753 ../common/glossary.rst:2760 -#: ../common/glossary.rst:2766 ../common/glossary.rst:2768 -#: ../common/glossary.rst:2757 -msgid "project" -msgstr "" - -#: ../common/glossary.rst:2758 ../common/glossary.rst:2765 -#: ../common/glossary.rst:2772 ../common/glossary.rst:2774 -#: ../common/glossary.rst:2763 -msgid "project ID" -msgstr "" - -#: ../common/glossary.rst:2763 ../common/glossary.rst:2770 -#: ../common/glossary.rst:2777 ../common/glossary.rst:2779 -#: ../common/glossary.rst:2768 -msgid "project VPN" -msgstr "" - -#: ../common/glossary.rst:2767 ../common/glossary.rst:2774 -#: ../common/glossary.rst:2781 ../common/glossary.rst:2783 -#: ../common/glossary.rst:2772 -msgid "promiscuous mode" -msgstr "" - -#: ../common/glossary.rst:2773 ../common/glossary.rst:2780 -#: ../common/glossary.rst:2787 ../common/glossary.rst:2789 -#: ../common/glossary.rst:2778 -msgid "protected property" -msgstr "" - -#: ../common/glossary.rst:2781 ../common/glossary.rst:2788 -#: ../common/glossary.rst:2795 ../common/glossary.rst:2797 -#: ../common/glossary.rst:2786 -msgid "provider" -msgstr "" - -#: ../common/glossary.rst:2786 ../common/glossary.rst:2793 -#: ../common/glossary.rst:2800 ../common/glossary.rst:2802 -#: ../common/glossary.rst:2791 -msgid "proxy node" -msgstr "" - -#: ../common/glossary.rst:2790 ../common/glossary.rst:2797 -#: ../common/glossary.rst:2804 ../common/glossary.rst:2806 -#: ../common/glossary.rst:2795 -msgid "proxy server" -msgstr "" - -#: ../common/glossary.rst:2796 ../common/glossary.rst:2803 -#: ../common/glossary.rst:2810 ../common/glossary.rst:2812 -#: ../common/glossary.rst:2801 -msgid "public API" -msgstr "" - -#: ../common/glossary.rst:2806 ../common/glossary.rst:2813 -#: ../common/glossary.rst:2820 ../common/glossary.rst:2822 -#: ../common/glossary.rst:2811 -msgid "public IP address" -msgstr "" - -#: ../common/glossary.rst:2801 ../common/glossary.rst:2808 -#: ../common/glossary.rst:2815 ../common/glossary.rst:2817 -#: ../common/glossary.rst:2806 -msgid "public image" -msgstr "" - -#: ../common/glossary.rst:2810 ../common/glossary.rst:2817 -#: ../common/glossary.rst:2824 ../common/glossary.rst:2826 -#: ../common/glossary.rst:2815 -msgid "public key authentication" -msgstr "" - -#: ../common/glossary.rst:2815 ../common/glossary.rst:2822 -#: ../common/glossary.rst:2829 ../common/glossary.rst:2831 -#: ../common/glossary.rst:2820 -msgid "public network" -msgstr "" - -#: ../common/cli_overview.rst:58 ../common/cli_overview.rst:62 -#: ../common/cli_overview.rst:65 -msgid "python-barbicanclient" -msgstr "" - -#: ../common/cli_overview.rst:72 ../common/cli_overview.rst:81 -#: ../common/cli_overview.rst:84 ../common/cli_overview.rst:88 -#: ../common/cli_overview.rst:91 -msgid "python-ceilometerclient" -msgstr "" - -#: ../common/cli_overview.rst:34 ../common/cli_overview.rst:37 -msgid "python-cinderclient" -msgstr "" - -#: ../common/cli_overview.rst:49 ../common/cli_overview.rst:55 -#: ../common/cli_overview.rst:59 ../common/cli_overview.rst:62 -msgid "python-glanceclient" -msgstr "" - -#: ../common/cli_overview.rst:65 ../common/cli_overview.rst:71 -#: ../common/cli_overview.rst:74 ../common/cli_overview.rst:78 -#: ../common/cli_overview.rst:81 -msgid "python-heatclient" -msgstr "" - -#: ../common/cli_overview.rst:44 ../common/cli_overview.rst:50 -#: ../common/cli_overview.rst:54 ../common/cli_overview.rst:57 -msgid "python-keystoneclient" -msgstr "" - -#: ../common/cli_overview.rst:44 -msgid "python-magnumclient" -msgstr "" - -#: ../common/cli_overview.rst:78 ../common/cli_overview.rst:81 -#: ../common/cli_overview.rst:85 ../common/cli_overview.rst:88 -msgid "python-manilaclient" -msgstr "" - -#: ../common/cli_overview.rst:92 ../common/cli_overview.rst:95 -msgid "python-mistralclient" -msgstr "" - -#: ../common/cli_overview.rst:34 -msgid "python-muranoclient" -msgstr "" - -#: ../common/cli_overview.rst:52 ../common/cli_overview.rst:58 -#: ../common/cli_overview.rst:61 ../common/cli_overview.rst:65 -#: ../common/cli_overview.rst:68 -msgid "python-neutronclient" -msgstr "" - -#: ../common/cli_overview.rst:37 ../common/cli_overview.rst:40 -msgid "python-novaclient" -msgstr "" - -#: ../common/cli_overview.rst:80 ../common/cli_overview.rst:89 -#: ../common/cli_overview.rst:92 ../common/cli_overview.rst:95 -#: ../common/cli_overview.rst:98 -msgid "python-openstackclient" -msgstr "" - -#: ../common/cli_overview.rst:76 ../common/cli_overview.rst:85 -#: ../common/cli_overview.rst:88 ../common/cli_overview.rst:50 -msgid "python-saharaclient" -msgstr "" - -#: ../common/cli_overview.rst:55 ../common/cli_overview.rst:61 -#: ../common/cli_overview.rst:64 ../common/cli_overview.rst:68 -#: ../common/cli_overview.rst:71 -msgid "python-swiftclient" -msgstr "" - -#: ../common/cli_overview.rst:41 ../common/cli_overview.rst:47 -msgid "python-troveclient" -msgstr "" - -#: ../common/cli_overview.rst:54 -msgid "python-tuskarclient" -msgstr "" - -#: ../common/cli_manage_images.rst:237 ../common/cli_manage_images.rst:256 -msgid "qemu or kvm" -msgstr "" - -#: ../common/glossary.rst:2842 ../common/glossary.rst:2849 -#: ../common/glossary.rst:2856 ../common/glossary.rst:2858 -#: ../common/glossary.rst:2847 -msgid "quarantine" -msgstr "" - -#: ../common/glossary.rst:2855 ../common/glossary.rst:2862 -#: ../common/glossary.rst:2869 ../common/glossary.rst:2871 -#: ../common/glossary.rst:2860 -msgid "quota" -msgstr "" - -#: ../common/glossary.rst:2874 ../common/glossary.rst:2881 -#: ../common/glossary.rst:2888 ../common/glossary.rst:2890 -#: ../common/glossary.rst:2879 -msgid "radvd" -msgstr "" - -#: ../common/glossary.rst:2880 ../common/glossary.rst:2887 -#: ../common/glossary.rst:2894 ../common/glossary.rst:2896 -#: ../common/glossary.rst:2885 -msgid "rally" -msgstr "" - -#: ../common/glossary.rst:2896 ../common/glossary.rst:2903 -#: ../common/glossary.rst:2910 ../common/glossary.rst:2912 -#: ../common/glossary.rst:2901 -msgid "rate limit" -msgstr "" - -#: ../common/glossary.rst:2901 ../common/glossary.rst:2908 -#: ../common/glossary.rst:2915 ../common/glossary.rst:2917 -#: ../common/glossary.rst:2906 -msgid "raw" -msgstr "" - -#: ../common/glossary.rst:2906 ../common/glossary.rst:2913 -#: ../common/glossary.rst:2920 ../common/glossary.rst:2922 -#: ../common/glossary.rst:2911 -msgid "rebalance" -msgstr "" - -#: ../common/glossary.rst:2912 ../common/glossary.rst:2919 -#: ../common/glossary.rst:2926 ../common/glossary.rst:2928 -#: ../common/glossary.rst:2917 -msgid "reboot" -msgstr "" - -#: ../common/glossary.rst:2921 ../common/glossary.rst:2928 -#: ../common/glossary.rst:2935 ../common/glossary.rst:2937 -#: ../common/glossary.rst:2926 -msgid "rebuild" -msgstr "" - -#: ../common/glossary.rst:2930 ../common/glossary.rst:2937 -#: ../common/glossary.rst:2944 ../common/glossary.rst:2946 -#: ../common/glossary.rst:2935 -msgid "record" -msgstr "" - -#: ../common/glossary.rst:2940 ../common/glossary.rst:2947 -#: ../common/glossary.rst:2954 ../common/glossary.rst:2956 -#: ../common/glossary.rst:2945 -msgid "record ID" -msgstr "" - -#: ../common/glossary.rst:2949 ../common/glossary.rst:2956 -#: ../common/glossary.rst:2963 ../common/glossary.rst:2965 -#: ../common/glossary.rst:2954 -msgid "reference architecture" -msgstr "" - -#: ../common/glossary.rst:2953 ../common/glossary.rst:2960 -#: ../common/glossary.rst:2967 ../common/glossary.rst:2969 -#: ../common/glossary.rst:2958 -msgid "region" -msgstr "" - -#: ../common/glossary.rst:2959 ../common/glossary.rst:2966 -#: ../common/glossary.rst:2973 ../common/glossary.rst:2975 -#: ../common/glossary.rst:2964 -msgid "registry" -msgstr "" - -#: ../common/glossary.rst:2963 ../common/glossary.rst:2970 -#: ../common/glossary.rst:2977 ../common/glossary.rst:2979 -#: ../common/glossary.rst:2968 -msgid "registry server" -msgstr "" - -#: ../common/glossary.rst:2979 ../common/glossary.rst:2986 -#: ../common/glossary.rst:2993 ../common/glossary.rst:2995 -#: ../common/glossary.rst:2984 -msgid "replica" -msgstr "" - -#: ../common/glossary.rst:2985 ../common/glossary.rst:2992 -#: ../common/glossary.rst:2999 ../common/glossary.rst:3001 -#: ../common/glossary.rst:2990 -msgid "replica count" -msgstr "" - -#: ../common/glossary.rst:2990 ../common/glossary.rst:2997 -#: ../common/glossary.rst:3004 ../common/glossary.rst:3006 -#: ../common/glossary.rst:2995 -msgid "replication" -msgstr "" - -#: ../common/glossary.rst:2995 ../common/glossary.rst:3002 -#: ../common/glossary.rst:3009 ../common/glossary.rst:3011 -#: ../common/glossary.rst:3000 -msgid "replicator" -msgstr "" - -#: ../common/glossary.rst:3000 ../common/glossary.rst:3007 -#: ../common/glossary.rst:3014 ../common/glossary.rst:3016 -#: ../common/glossary.rst:3005 -msgid "request ID" -msgstr "" - -#: ../common/glossary.rst:3004 ../common/glossary.rst:3011 -#: ../common/glossary.rst:3018 ../common/glossary.rst:3020 -#: ../common/glossary.rst:3009 -msgid "rescue image" -msgstr "" - -#: ../common/glossary.rst:3010 ../common/glossary.rst:3017 -#: ../common/glossary.rst:3024 ../common/glossary.rst:3026 -#: ../common/glossary.rst:3015 -msgid "resize" -msgstr "" - -#: ../common/glossary.rst:3023 ../common/glossary.rst:3030 -#: ../common/glossary.rst:3037 ../common/glossary.rst:3039 -#: ../common/glossary.rst:3028 -msgid "ring" -msgstr "" - -#: ../common/glossary.rst:3029 ../common/glossary.rst:3036 -#: ../common/glossary.rst:3043 ../common/glossary.rst:3045 -#: ../common/glossary.rst:3034 -msgid "ring builder" -msgstr "" - -#: ../common/glossary.rst:3042 ../common/glossary.rst:3049 -#: ../common/glossary.rst:3056 ../common/glossary.rst:3058 -#: ../common/glossary.rst:3047 -msgid "role" -msgstr "" - -#: ../common/glossary.rst:3048 ../common/glossary.rst:3055 -#: ../common/glossary.rst:3062 ../common/glossary.rst:3064 -#: ../common/glossary.rst:3053 -msgid "role ID" -msgstr "" - -#: ../common/glossary.rst:3052 ../common/glossary.rst:3059 -#: ../common/glossary.rst:3066 ../common/glossary.rst:3068 -#: ../common/glossary.rst:3057 -msgid "rootwrap" -msgstr "" - -#: ../common/glossary.rst:3057 ../common/glossary.rst:3064 -#: ../common/glossary.rst:3071 ../common/glossary.rst:3073 -#: ../common/glossary.rst:3062 -msgid "round-robin scheduler" -msgstr "" - -#: ../common/glossary.rst:3062 ../common/glossary.rst:3069 -#: ../common/glossary.rst:3076 ../common/glossary.rst:3078 -#: ../common/glossary.rst:3067 -msgid "router" -msgstr "" - -#: ../common/glossary.rst:3067 ../common/glossary.rst:3074 -#: ../common/glossary.rst:3081 ../common/glossary.rst:3083 -#: ../common/glossary.rst:3072 -msgid "routing key" -msgstr "" - -#: ../common/glossary.rst:3079 ../common/glossary.rst:3086 -#: ../common/glossary.rst:3093 ../common/glossary.rst:3095 -#: ../common/glossary.rst:3084 -msgid "rsync" -msgstr "" - -#: ../common/cli_manage_images.rst:262 ../common/cli_manage_images.rst:274 -msgid "rtl8139" -msgstr "" - -#: ../common/glossary.rst:3098 ../common/cli_overview.rst:76 -#: ../common/glossary.rst:3105 ../common/cli_overview.rst:85 -#: ../common/glossary.rst:3112 ../common/cli_overview.rst:88 -#: ../common/glossary.rst:3114 ../common/cli_overview.rst:50 -#: ../common/glossary.rst:3103 -msgid "sahara" -msgstr "" - -#: ../common/glossary.rst:3108 ../common/glossary.rst:3115 -#: ../common/glossary.rst:3122 ../common/glossary.rst:3124 -#: ../common/glossary.rst:3113 -msgid "scheduler manager" -msgstr "" - -#: ../common/glossary.rst:3114 ../common/glossary.rst:3121 -#: ../common/glossary.rst:3128 ../common/glossary.rst:3130 -#: ../common/glossary.rst:3119 -msgid "scoped token" -msgstr "" - -#: ../common/glossary.rst:3119 ../common/glossary.rst:3126 -#: ../common/glossary.rst:3133 ../common/glossary.rst:3135 -#: ../common/glossary.rst:3124 -msgid "scrubber" -msgstr "" - -#: ../common/cli_manage_images.rst:239 -msgid "scsi" -msgstr "" - -#: ../common/glossary.rst:3124 ../common/glossary.rst:3131 -#: ../common/glossary.rst:3138 ../common/glossary.rst:3140 -#: ../common/glossary.rst:3129 -msgid "secret key" -msgstr "" - -#: ../common/glossary.rst:3129 ../common/glossary.rst:3136 -#: ../common/glossary.rst:3143 ../common/glossary.rst:3145 -#: ../common/glossary.rst:3134 -msgid "secure shell (SSH)" -msgstr "" - -#: ../common/glossary.rst:3135 ../common/glossary.rst:3142 -#: ../common/glossary.rst:3149 ../common/glossary.rst:3151 -#: ../common/glossary.rst:3140 -msgid "security group" -msgstr "" - -#: ../common/glossary.rst:3140 ../common/glossary.rst:3147 -#: ../common/glossary.rst:3154 ../common/glossary.rst:3156 -#: ../common/glossary.rst:3145 -msgid "segmented object" -msgstr "" - -#: ../common/glossary.rst:3162 ../common/glossary.rst:3151 -msgid "self-service" -msgstr "" - -#: ../common/glossary.rst:3151 ../common/glossary.rst:3158 -#: ../common/glossary.rst:3165 ../common/glossary.rst:3173 -#: ../common/glossary.rst:3162 -msgid "server" -msgstr "" - -#: ../common/glossary.rst:3163 ../common/glossary.rst:3170 -#: ../common/glossary.rst:3177 ../common/glossary.rst:3185 -#: ../common/glossary.rst:3174 -msgid "server UUID" -msgstr "" - -#: ../common/glossary.rst:3159 ../common/glossary.rst:3166 -#: ../common/glossary.rst:3173 ../common/glossary.rst:3181 -#: ../common/glossary.rst:3170 -msgid "server image" -msgstr "" - -#: ../common/glossary.rst:3167 ../common/glossary.rst:3174 -#: ../common/glossary.rst:3181 ../common/glossary.rst:3189 -#: ../common/glossary.rst:3178 -msgid "service" -msgstr "" - -#: ../common/glossary.rst:3177 ../common/glossary.rst:3184 -#: ../common/glossary.rst:3191 ../common/glossary.rst:3199 -#: ../common/glossary.rst:3188 -msgid "service ID" -msgstr "" - -#: ../common/glossary.rst:3173 ../common/glossary.rst:3180 -#: ../common/glossary.rst:3187 ../common/glossary.rst:3195 -#: ../common/glossary.rst:3184 -msgid "service catalog" -msgstr "" - -#: ../common/glossary.rst:3182 ../common/glossary.rst:3189 -#: ../common/glossary.rst:3196 ../common/glossary.rst:3204 -#: ../common/glossary.rst:3193 -msgid "service provider" -msgstr "" - -#: ../common/glossary.rst:3188 ../common/glossary.rst:3195 -#: ../common/glossary.rst:3202 ../common/glossary.rst:3210 -#: ../common/glossary.rst:3199 -msgid "service registration" -msgstr "" - -#: ../common/glossary.rst:3193 ../common/glossary.rst:3200 -#: ../common/glossary.rst:3207 ../common/glossary.rst:3215 -#: ../common/glossary.rst:3204 -msgid "service tenant" -msgstr "" - -#: ../common/glossary.rst:3198 ../common/glossary.rst:3205 -#: ../common/glossary.rst:3212 ../common/glossary.rst:3220 -#: ../common/glossary.rst:3209 -msgid "service token" -msgstr "" - -#: ../common/glossary.rst:3203 ../common/glossary.rst:3210 -#: ../common/glossary.rst:3217 ../common/glossary.rst:3225 -#: ../common/glossary.rst:3214 -msgid "session back end" -msgstr "" - -#: ../common/glossary.rst:3208 ../common/glossary.rst:3215 -#: ../common/glossary.rst:3222 ../common/glossary.rst:3230 -#: ../common/glossary.rst:3219 -msgid "session persistence" -msgstr "" - -#: ../common/glossary.rst:3214 ../common/glossary.rst:3221 -#: ../common/glossary.rst:3228 ../common/glossary.rst:3236 -#: ../common/glossary.rst:3225 -msgid "session storage" -msgstr "" - -#: ../common/cli_install_openstack_command_line_clients.rst:23 -msgid "setuptools package" -msgstr "" - -#: ../common/glossary.rst:3219 ../common/glossary.rst:3226 -#: ../common/glossary.rst:3233 ../common/glossary.rst:3241 -#: ../common/glossary.rst:3230 -msgid "shared IP address" -msgstr "" - -#: ../common/glossary.rst:3231 ../common/glossary.rst:3238 -#: ../common/glossary.rst:3245 ../common/glossary.rst:3253 -#: ../common/glossary.rst:3242 -msgid "shared IP group" -msgstr "" - -#: ../common/glossary.rst:3239 ../common/glossary.rst:3246 -#: ../common/glossary.rst:3253 ../common/glossary.rst:3261 -#: ../common/glossary.rst:3250 -msgid "shared storage" -msgstr "" - -#: ../common/glossary.rst:3268 ../common/glossary.rst:3275 -#: ../common/glossary.rst:3282 ../common/glossary.rst:3290 -#: ../common/glossary.rst:3279 -msgid "snapshot" -msgstr "" - -#: ../common/glossary.rst:3274 ../common/glossary.rst:3281 -#: ../common/glossary.rst:3288 ../common/glossary.rst:3296 -#: ../common/glossary.rst:3285 -msgid "soft reboot" -msgstr "" - -#: ../common/glossary.rst:3290 ../common/glossary.rst:3297 -#: ../common/glossary.rst:3304 ../common/glossary.rst:3312 -#: ../common/glossary.rst:3301 -msgid "spread-first scheduler" -msgstr "" - -#: ../common/glossary.rst:3304 ../common/glossary.rst:3311 -#: ../common/glossary.rst:3318 ../common/glossary.rst:3326 -#: ../common/glossary.rst:3315 -msgid "stack" -msgstr "" - -#: ../common/glossary.rst:3316 ../common/glossary.rst:3323 -#: ../common/glossary.rst:3330 ../common/glossary.rst:3338 -#: ../common/glossary.rst:3327 -msgid "static IP address" -msgstr "" - -#: ../common/glossary.rst:3325 ../common/glossary.rst:3332 -#: ../common/glossary.rst:3339 ../common/glossary.rst:3347 -#: ../common/glossary.rst:3336 -msgid "storage back end" -msgstr "" - -#: ../common/glossary.rst:3336 ../common/glossary.rst:3343 -#: ../common/glossary.rst:3350 ../common/glossary.rst:3358 -#: ../common/glossary.rst:3347 -msgid "storage manager" -msgstr "" - -#: ../common/glossary.rst:3341 ../common/glossary.rst:3348 -#: ../common/glossary.rst:3355 ../common/glossary.rst:3363 -#: ../common/glossary.rst:3352 -msgid "storage manager back end" -msgstr "" - -#: ../common/glossary.rst:3330 ../common/glossary.rst:3337 -#: ../common/glossary.rst:3344 ../common/glossary.rst:3352 -#: ../common/glossary.rst:3341 -msgid "storage node" -msgstr "" - -#: ../common/glossary.rst:3346 ../common/glossary.rst:3353 -#: ../common/glossary.rst:3360 ../common/glossary.rst:3368 -#: ../common/glossary.rst:3357 -msgid "storage services" -msgstr "" - -#: ../common/glossary.rst:3351 ../common/glossary.rst:3358 -#: ../common/glossary.rst:3365 ../common/glossary.rst:3373 -#: ../common/glossary.rst:3362 -msgid "strategy" -msgstr "" - -#: ../common/glossary.rst:3356 ../common/glossary.rst:3363 -#: ../common/glossary.rst:3370 ../common/glossary.rst:3378 -#: ../common/glossary.rst:3367 -msgid "subdomain" -msgstr "" - -#: ../common/glossary.rst:3363 ../common/glossary.rst:3370 -#: ../common/glossary.rst:3377 ../common/glossary.rst:3385 -#: ../common/glossary.rst:3374 -msgid "subnet" -msgstr "" - -#: ../common/glossary.rst:3371 ../common/glossary.rst:3378 -#: ../common/glossary.rst:3385 ../common/glossary.rst:3393 -#: ../common/glossary.rst:3382 -msgid "suspend" -msgstr "" - -#: ../common/glossary.rst:3375 ../common/glossary.rst:3382 -#: ../common/glossary.rst:3389 ../common/glossary.rst:3397 -#: ../common/glossary.rst:3386 -msgid "swap" -msgstr "" - -#: ../common/glossary.rst:3380 ../common/glossary.rst:3387 -#: ../common/glossary.rst:3394 ../common/glossary.rst:3402 -#: ../common/glossary.rst:3391 -msgid "swawth" -msgstr "" - -#: ../common/glossary.rst:3386 ../common/cli_overview.rst:55 -#: ../common/glossary.rst:3393 ../common/cli_overview.rst:61 -#: ../common/glossary.rst:3400 ../common/cli_overview.rst:64 -#: ../common/glossary.rst:3408 ../common/cli_overview.rst:68 -#: ../common/glossary.rst:3397 ../common/cli_overview.rst:71 -msgid "swift" -msgstr "" - -#: ../common/glossary.rst:3391 ../common/glossary.rst:3398 -#: ../common/glossary.rst:3405 ../common/glossary.rst:3413 -#: ../common/glossary.rst:3402 -msgid "swift All in One (SAIO)" -msgstr "" - -#: ../common/get_started_storage_concepts.rst:56 -#: ../common/get_started_storage_concepts.rst:59 -#: ../common/get_started_storage_concepts.rst:58 -#: ../common/get_started_object_storage.rst:38 -msgid "swift client" -msgstr "" - -#: ../common/glossary.rst:3396 ../common/glossary.rst:3403 -#: ../common/glossary.rst:3410 ../common/glossary.rst:3418 -#: ../common/glossary.rst:3407 -msgid "swift middleware" -msgstr "" - -#: ../common/glossary.rst:3401 ../common/glossary.rst:3408 -#: ../common/glossary.rst:3415 ../common/glossary.rst:3423 -#: ../common/glossary.rst:3412 -msgid "swift proxy server" -msgstr "" - -#: ../common/glossary.rst:3406 ../common/glossary.rst:3413 -#: ../common/glossary.rst:3420 ../common/glossary.rst:3428 -#: ../common/glossary.rst:3417 -msgid "swift storage node" -msgstr "" - -#: ../common/get_started_storage_concepts.rst:61 -#: ../common/get_started_storage_concepts.rst:64 -#: ../common/get_started_storage_concepts.rst:63 -#: ../common/get_started_object_storage.rst:43 -msgid "swift-init" -msgstr "" - -#: ../common/get_started_storage_concepts.rst:65 -#: ../common/get_started_storage_concepts.rst:68 -#: ../common/get_started_storage_concepts.rst:67 -#: ../common/get_started_object_storage.rst:47 -msgid "swift-recon" -msgstr "" - -#: ../common/get_started_storage_concepts.rst:68 -#: ../common/get_started_storage_concepts.rst:69 -#: ../common/get_started_storage_concepts.rst:71 -#: ../common/get_started_storage_concepts.rst:72 -#: ../common/get_started_storage_concepts.rst:70 -#: ../common/get_started_object_storage.rst:50 -msgid "swift-ring-builder" -msgstr "" - -#: ../common/glossary.rst:3411 ../common/glossary.rst:3418 -#: ../common/glossary.rst:3425 ../common/glossary.rst:3433 -#: ../common/glossary.rst:3422 -msgid "sync point" -msgstr "" - -#: ../common/glossary.rst:3416 ../common/glossary.rst:3423 -#: ../common/glossary.rst:3430 ../common/glossary.rst:3438 -#: ../common/glossary.rst:3427 -msgid "sysadmin" -msgstr "" - -#: ../common/glossary.rst:3422 ../common/glossary.rst:3429 -#: ../common/glossary.rst:3436 ../common/glossary.rst:3444 -#: ../common/glossary.rst:3433 -msgid "system usage" -msgstr "" - -#: ../common/glossary.rst:3450 ../common/glossary.rst:3457 -#: ../common/glossary.rst:3464 ../common/glossary.rst:3472 -#: ../common/glossary.rst:3461 -msgid "tenant" -msgstr "" - -#: ../common/glossary.rst:3464 ../common/glossary.rst:3471 -#: ../common/glossary.rst:3478 ../common/glossary.rst:3486 -#: ../common/glossary.rst:3475 -msgid "tenant ID" -msgstr "" - -#: ../common/glossary.rst:3459 ../common/glossary.rst:3466 -#: ../common/glossary.rst:3473 ../common/glossary.rst:3481 -#: ../common/glossary.rst:3470 -msgid "tenant endpoint" -msgstr "" - -#: ../common/glossary.rst:3469 ../common/glossary.rst:3476 -#: ../common/glossary.rst:3483 ../common/glossary.rst:3491 -#: ../common/glossary.rst:3480 -msgid "token" -msgstr "" - -#: ../common/glossary.rst:3474 ../common/glossary.rst:3481 -#: ../common/glossary.rst:3488 ../common/glossary.rst:3496 -#: ../common/glossary.rst:3485 -msgid "token services" -msgstr "" - -#: ../common/glossary.rst:3479 ../common/glossary.rst:3486 -#: ../common/glossary.rst:3493 ../common/glossary.rst:3501 -#: ../common/glossary.rst:3490 -msgid "tombstone" -msgstr "" - -#: ../common/glossary.rst:3485 ../common/glossary.rst:3492 -#: ../common/glossary.rst:3499 ../common/glossary.rst:3507 -#: ../common/glossary.rst:3496 -msgid "topic publisher" -msgstr "" - -#: ../common/glossary.rst:3495 ../common/glossary.rst:3502 -#: ../common/glossary.rst:3509 ../common/glossary.rst:3517 -#: ../common/glossary.rst:3506 -msgid "transaction ID" -msgstr "" - -#: ../common/glossary.rst:3500 ../common/glossary.rst:3507 -#: ../common/glossary.rst:3514 ../common/glossary.rst:3522 -#: ../common/glossary.rst:3511 -msgid "transient" -msgstr "" - -#: ../common/glossary.rst:3504 ../common/glossary.rst:3511 -#: ../common/glossary.rst:3518 ../common/glossary.rst:3526 -#: ../common/glossary.rst:3515 -msgid "transient exchange" -msgstr "" - -#: ../common/glossary.rst:3508 ../common/glossary.rst:3515 -#: ../common/glossary.rst:3522 ../common/glossary.rst:3530 -#: ../common/glossary.rst:3519 -msgid "transient message" -msgstr "" - -#: ../common/glossary.rst:3513 ../common/glossary.rst:3520 -#: ../common/glossary.rst:3527 ../common/glossary.rst:3535 -#: ../common/glossary.rst:3524 -msgid "transient queue" -msgstr "" - -#: ../common/glossary.rst:3522 ../common/cli_overview.rst:41 -#: ../common/glossary.rst:3529 ../common/cli_overview.rst:47 -#: ../common/glossary.rst:3536 ../common/glossary.rst:3544 -#: ../common/glossary.rst:3533 -msgid "trove" -msgstr "" - -#: ../common/cli_overview.rst:54 -msgid "tuskar" -msgstr "" - -#: ../common/glossary.rst:3531 ../common/glossary.rst:3538 -#: ../common/glossary.rst:3545 ../common/glossary.rst:3553 -#: ../common/glossary.rst:3542 -msgid "unscoped token" -msgstr "" - -#: ../common/glossary.rst:3535 ../common/glossary.rst:3542 -#: ../common/glossary.rst:3549 ../common/glossary.rst:3557 -#: ../common/glossary.rst:3546 -msgid "updater" -msgstr "" - -#: ../common/glossary.rst:3540 ../common/glossary.rst:3547 -#: ../common/glossary.rst:3554 ../common/glossary.rst:3562 -#: ../common/glossary.rst:3551 -msgid "user" -msgstr "" - -#: ../common/glossary.rst:3546 ../common/glossary.rst:3553 -#: ../common/glossary.rst:3560 ../common/glossary.rst:3568 -#: ../common/glossary.rst:3557 -msgid "user data" -msgstr "" - -#: ../common/glossary.rst:3739 ../common/glossary.rst:3746 -#: ../common/glossary.rst:3753 ../common/glossary.rst:3761 -#: ../common/glossary.rst:3750 -msgid "vSphere" -msgstr "" - -#: ../common/cli_manage_images.rst:241 ../common/cli_manage_images.rst:264 -msgid "virtio" -msgstr "" - -#: ../common/glossary.rst:3592 ../common/glossary.rst:3599 -#: ../common/glossary.rst:3606 ../common/glossary.rst:3614 -#: ../common/glossary.rst:3603 -msgid "virtual IP" -msgstr "" - -#: ../common/glossary.rst:3646 ../common/glossary.rst:3653 -#: ../common/glossary.rst:3660 ../common/glossary.rst:3668 -#: ../common/glossary.rst:3657 -msgid "virtual VLAN" -msgstr "" - -#: ../common/glossary.rst:3580 ../common/glossary.rst:3587 -#: ../common/glossary.rst:3594 -msgid "virtual extensible LAN (VXLAN)" -msgstr "" - -#: ../common/glossary.rst:3599 ../common/glossary.rst:3606 -#: ../common/glossary.rst:3613 ../common/glossary.rst:3621 -#: ../common/glossary.rst:3610 -msgid "virtual machine (VM)" -msgstr "" - -#: ../common/glossary.rst:3605 ../common/glossary.rst:3612 -#: ../common/glossary.rst:3619 ../common/glossary.rst:3627 -#: ../common/glossary.rst:3616 -msgid "virtual network" -msgstr "" - -#: ../common/glossary.rst:3609 ../common/glossary.rst:3616 -#: ../common/glossary.rst:3623 ../common/glossary.rst:3631 -#: ../common/glossary.rst:3620 -msgid "virtual networking" -msgstr "" - -#: ../common/glossary.rst:3627 ../common/glossary.rst:3634 -#: ../common/glossary.rst:3641 ../common/glossary.rst:3649 -#: ../common/glossary.rst:3638 -msgid "virtual port" -msgstr "" - -#: ../common/glossary.rst:3632 ../common/glossary.rst:3639 -#: ../common/glossary.rst:3646 ../common/glossary.rst:3654 -#: ../common/glossary.rst:3643 -msgid "virtual private network (VPN)" -msgstr "" - -#: ../common/glossary.rst:3637 ../common/glossary.rst:3644 -#: ../common/glossary.rst:3651 ../common/glossary.rst:3659 -#: ../common/glossary.rst:3648 -msgid "virtual server" -msgstr "" - -#: ../common/glossary.rst:3641 ../common/glossary.rst:3648 -#: ../common/glossary.rst:3655 ../common/glossary.rst:3663 -#: ../common/glossary.rst:3652 -msgid "virtual switch (vSwitch)" -msgstr "" - -#: ../common/cli_manage_images.rst:276 -msgid "vmware" -msgstr "" - -#: ../common/glossary.rst:3695 ../common/glossary.rst:3702 -#: ../common/glossary.rst:3709 ../common/glossary.rst:3717 -#: ../common/glossary.rst:3706 -msgid "volume" -msgstr "" - -#: ../common/glossary.rst:3714 ../common/glossary.rst:3721 -#: ../common/glossary.rst:3728 ../common/glossary.rst:3736 -#: ../common/glossary.rst:3725 -msgid "volume ID" -msgstr "" - -#: ../common/glossary.rst:3705 ../common/glossary.rst:3712 -#: ../common/glossary.rst:3719 ../common/glossary.rst:3727 -#: ../common/glossary.rst:3716 -msgid "volume controller" -msgstr "" - -#: ../common/glossary.rst:3710 ../common/glossary.rst:3717 -#: ../common/glossary.rst:3724 ../common/glossary.rst:3732 -#: ../common/glossary.rst:3721 -msgid "volume driver" -msgstr "" - -#: ../common/glossary.rst:3719 ../common/glossary.rst:3726 -#: ../common/glossary.rst:3733 ../common/glossary.rst:3741 -#: ../common/glossary.rst:3730 -msgid "volume manager" -msgstr "" - -#: ../common/glossary.rst:3724 ../common/glossary.rst:3731 -#: ../common/glossary.rst:3738 ../common/glossary.rst:3746 -#: ../common/glossary.rst:3735 -msgid "volume node" -msgstr "" - -#: ../common/glossary.rst:3728 ../common/glossary.rst:3735 -#: ../common/glossary.rst:3742 ../common/glossary.rst:3750 -#: ../common/glossary.rst:3739 -msgid "volume plug-in" -msgstr "" - -#: ../common/glossary.rst:3733 ../common/glossary.rst:3740 -#: ../common/glossary.rst:3747 ../common/glossary.rst:3755 -#: ../common/glossary.rst:3744 -msgid "volume worker" -msgstr "" - -#: ../common/glossary.rst:3749 ../common/glossary.rst:3756 -#: ../common/glossary.rst:3763 ../common/glossary.rst:3771 -#: ../common/glossary.rst:3760 -msgid "weight" -msgstr "" - -#: ../common/glossary.rst:3754 ../common/glossary.rst:3761 -#: ../common/glossary.rst:3768 ../common/glossary.rst:3776 -#: ../common/glossary.rst:3765 -msgid "weighted cost" -msgstr "" - -#: ../common/glossary.rst:3743 ../common/glossary.rst:3750 -#: ../common/glossary.rst:3757 ../common/glossary.rst:3765 -#: ../common/glossary.rst:3754 -msgid "weighting" -msgstr "" - -#: ../common/glossary.rst:3759 ../common/glossary.rst:3766 -#: ../common/glossary.rst:3773 ../common/glossary.rst:3781 -#: ../common/glossary.rst:3770 -msgid "worker" -msgstr "" - -#: ../common/get_started_compute.rst:97 ../common/get_started_compute.rst:96 -msgid "x509 certificates." -msgstr "" - -#: ../common/cli_manage_images.rst:243 ../common/cli_manage_images.rst:245 -#: ../common/cli_manage_images.rst:266 -msgid "xen" -msgstr "" - -#: ../common/glossary.rst:3804 ../common/glossary.rst:3811 -#: ../common/glossary.rst:3818 ../common/glossary.rst:3826 -#: ../common/glossary.rst:3815 -msgid "zaqar" +#: ../common/support-compute.rst:219 +msgid "" +"To effectively disable the libvirt live snapshotting, until the problem is " +"resolved, configure the ``disable_libvirt_livesnapshot`` option. You can " +"turn off the live snapshotting mechanism by setting up its value to ``True`` " +"in the ``[workarounds]`` section of the :file:`nova.conf` file:" msgstr "" diff --git a/doc/common/locale/common.pot b/doc/common/locale/common.pot index 32d67508c4..2e6095cdc9 100644 --- a/doc/common/locale/common.pot +++ b/doc/common/locale/common.pot @@ -1,7 +1,7 @@ msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" -"POT-Creation-Date: 2015-10-05 06:15+0000\n" +"POT-Creation-Date: 2015-10-08 06:30+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -6268,46 +6268,46 @@ msgid "The other options require that HTTPS is enabled; these options defend aga msgstr "" #: ./doc/common/section_dashboard-configure-https.xml:33(para) -msgid "Edit the /etc/apache2/conf.d/openstack-dashboard.conf file as shown in :" +msgid "Edit the openstack-dashboard.conf file as shown in :" msgstr "" -#: ./doc/common/section_dashboard-configure-https.xml:38(title) +#: ./doc/common/section_dashboard-configure-https.xml:37(title) msgid "Before" msgstr "" -#: ./doc/common/section_dashboard-configure-https.xml:52(title) +#: ./doc/common/section_dashboard-configure-https.xml:51(title) msgid "After" msgstr "" -#: ./doc/common/section_dashboard-configure-https.xml:94(para) +#: ./doc/common/section_dashboard-configure-https.xml:93(para) msgid "In this configuration, the Apache HTTP server listens on port 443 and redirects all non-secure requests to the HTTPS protocol. The secured section defines the private key, public key, and certificate to use." msgstr "" -#: ./doc/common/section_dashboard-configure-https.xml:101(para) +#: ./doc/common/section_dashboard-configure-https.xml:100(para) msgid "Restart the Apache HTTP server." msgstr "" -#: ./doc/common/section_dashboard-configure-https.xml:102(para) +#: ./doc/common/section_dashboard-configure-https.xml:101(para) msgid "For Debian, Ubuntu, or SUSE distributions:" msgstr "" -#: ./doc/common/section_dashboard-configure-https.xml:104(para) +#: ./doc/common/section_dashboard-configure-https.xml:103(para) msgid "For Fedora, RHEL, or CentOS distributions:" msgstr "" -#: ./doc/common/section_dashboard-configure-https.xml:108(para) +#: ./doc/common/section_dashboard-configure-https.xml:107(para) msgid "Restart memcached:" msgstr "" -#: ./doc/common/section_dashboard-configure-https.xml:111(para) +#: ./doc/common/section_dashboard-configure-https.xml:110(para) msgid "If you try to access the dashboard through HTTP, the browser redirects you to the HTTPS page." msgstr "" -#: ./doc/common/section_dashboard-configure-https.xml:116(para) +#: ./doc/common/section_dashboard-configure-https.xml:115(para) msgid "Configuring the dashboard for HTTPS also requires enabling SSL for the noVNC proxy service. On the controller node, add the following additional options to the [DEFAULT] section of the /etc/nova/nova.conf file: " msgstr "" -#: ./doc/common/section_dashboard-configure-https.xml:128(para) +#: ./doc/common/section_dashboard-configure-https.xml:127(para) msgid "On the compute nodes, ensure the nonvncproxy_base_url option points to a URL with an HTTPS scheme:" msgstr "" diff --git a/doc/config-reference/locale/config-reference.pot b/doc/config-reference/locale/config-reference.pot index a2d5549b7e..ad8c9af5f6 100644 --- a/doc/config-reference/locale/config-reference.pot +++ b/doc/config-reference/locale/config-reference.pot @@ -1,7 +1,7 @@ msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" -"POT-Creation-Date: 2015-10-05 06:15+0000\n" +"POT-Creation-Date: 2015-10-08 06:30+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -565,7 +565,7 @@ msgstr "" msgid "HTTPS" msgstr "" -#: ./doc/config-reference/table_default-ports-peripheral-services.xml:34(td) ./doc/config-reference/block-storage/drivers/zfssa-nfs-driver.xml:193(replaceable) +#: ./doc/config-reference/table_default-ports-peripheral-services.xml:34(td) ./doc/config-reference/block-storage/drivers/zfssa-nfs-driver.xml:196(replaceable) msgid "443" msgstr "" @@ -2203,7 +2203,7 @@ msgstr "" msgid "Host" msgstr "" -#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:252(td) ./doc/config-reference/compute/section_hypervisor_vmware.xml:318(td) ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:39(title) ./doc/config-reference/block-storage/drivers/sheepdog-driver.xml:46(title) ./doc/config-reference/block-storage/drivers/scality-sofs-driver.xml:50(title) ./doc/config-reference/block-storage/drivers/hitachi-storage-volume-driver.xml:85(title) +#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:252(td) ./doc/config-reference/compute/section_hypervisor_vmware.xml:318(td) ./doc/config-reference/block-storage/drivers/zfssa-iscsi-driver.xml:14(title) ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:39(title) ./doc/config-reference/block-storage/drivers/sheepdog-driver.xml:46(title) ./doc/config-reference/block-storage/drivers/scality-sofs-driver.xml:50(title) ./doc/config-reference/block-storage/drivers/hitachi-storage-volume-driver.xml:85(title) msgid "Configuration" msgstr "" @@ -4997,7 +4997,7 @@ msgstr "" msgid "ADMINISTRATOR" msgstr "" -#: ./doc/config-reference/image-service/section_image-service-backend-vmware.xml:59(replaceable) ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:82(replaceable) ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:146(replaceable) ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:354(replaceable) ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:411(replaceable) ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:490(replaceable) ./doc/config-reference/block-storage/drivers/zfssa-nfs-driver.xml:176(replaceable) +#: ./doc/config-reference/image-service/section_image-service-backend-vmware.xml:59(replaceable) ./doc/config-reference/block-storage/drivers/zfssa-iscsi-driver.xml:71(replaceable) ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:82(replaceable) ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:146(replaceable) ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:354(replaceable) ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:411(replaceable) ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:490(replaceable) ./doc/config-reference/block-storage/drivers/zfssa-nfs-driver.xml:179(replaceable) msgid "password" msgstr "" @@ -5409,7 +5409,7 @@ msgstr "" msgid "NFS (access by IP)" msgstr "" -#: ./doc/config-reference/shared-file-systems/drivers/glusterfs-driver.xml:21(title) ./doc/config-reference/shared-file-systems/drivers/hdfs-native-driver.xml:38(title) ./doc/config-reference/shared-file-systems/drivers/ibm-gpfs-driver.xml:22(title) ./doc/config-reference/shared-file-systems/drivers/emc-vnx-driver.xml:66(title) ./doc/config-reference/shared-file-systems/drivers/huawei-nas-driver.xml:45(title) ./doc/config-reference/shared-file-systems/drivers/hp-3par-share-driver.xml:10(title) ./doc/config-reference/shared-file-systems/drivers/glusterfs-native-driver.xml:47(title) ./doc/config-reference/shared-file-systems/drivers/emc-isilon-driver.xml:35(title) ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:99(title) ./doc/config-reference/block-storage/drivers/pure-storage-driver.xml:23(title) ./doc/config-reference/block-storage/drivers/dell-storagecenter-driver.xml:17(title) ./doc/config-reference/block-storage/drivers/dell-equallogic-driver.xml:10(title) ./doc/config-reference/block-storage/drivers/hds-hnas-driver.xml:17(title) ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:252(title) ./doc/config-reference/block-storage/drivers/emc-vnx-direct-driver.xml:40(title) ./doc/config-reference/block-storage/drivers/sheepdog-driver.xml:18(title) ./doc/config-reference/block-storage/drivers/emc-xtremio-driver.xml:21(title) ./doc/config-reference/block-storage/drivers/ibm-flashsystem-volume-driver.xml:289(title) ./doc/config-reference/block-storage/drivers/emc-vmax-driver.xml:35(title) ./doc/config-reference/block-storage/drivers/xio-volume-driver.xml:17(title) ./doc/config-reference/block-storage/drivers/prophetstor-dpl-driver.xml:18(title) ./doc/config-reference/block-storage/drivers/hp-msa-driver.xml:48(title) ./doc/config-reference/block-storage/drivers/dothill-driver.xml:53(title) ./doc/config-reference/block-storage/drivers/scality-sofs-driver.xml:16(title) ./doc/config-reference/block-storage/drivers/hitachi-storage-volume-driver.xml:56(title) ./doc/config-reference/block-storage/drivers/lenovo-driver.xml:48(title) ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:66(title) ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:327(title) ./doc/config-reference/block-storage/drivers/zfssa-nfs-driver.xml:15(title) +#: ./doc/config-reference/shared-file-systems/drivers/glusterfs-driver.xml:21(title) ./doc/config-reference/shared-file-systems/drivers/hdfs-native-driver.xml:38(title) ./doc/config-reference/shared-file-systems/drivers/ibm-gpfs-driver.xml:22(title) ./doc/config-reference/shared-file-systems/drivers/emc-vnx-driver.xml:66(title) ./doc/config-reference/shared-file-systems/drivers/huawei-nas-driver.xml:45(title) ./doc/config-reference/shared-file-systems/drivers/hp-3par-share-driver.xml:10(title) ./doc/config-reference/shared-file-systems/drivers/glusterfs-native-driver.xml:47(title) ./doc/config-reference/shared-file-systems/drivers/emc-isilon-driver.xml:35(title) ./doc/config-reference/block-storage/drivers/zfssa-iscsi-driver.xml:93(title) ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:99(title) ./doc/config-reference/block-storage/drivers/pure-storage-driver.xml:23(title) ./doc/config-reference/block-storage/drivers/dell-storagecenter-driver.xml:17(title) ./doc/config-reference/block-storage/drivers/dell-equallogic-driver.xml:10(title) ./doc/config-reference/block-storage/drivers/hds-hnas-driver.xml:17(title) ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:252(title) ./doc/config-reference/block-storage/drivers/emc-vnx-direct-driver.xml:40(title) ./doc/config-reference/block-storage/drivers/sheepdog-driver.xml:18(title) ./doc/config-reference/block-storage/drivers/emc-xtremio-driver.xml:21(title) ./doc/config-reference/block-storage/drivers/ibm-flashsystem-volume-driver.xml:289(title) ./doc/config-reference/block-storage/drivers/emc-vmax-driver.xml:35(title) ./doc/config-reference/block-storage/drivers/xio-volume-driver.xml:17(title) ./doc/config-reference/block-storage/drivers/prophetstor-dpl-driver.xml:18(title) ./doc/config-reference/block-storage/drivers/hp-msa-driver.xml:48(title) ./doc/config-reference/block-storage/drivers/dothill-driver.xml:53(title) ./doc/config-reference/block-storage/drivers/scality-sofs-driver.xml:16(title) ./doc/config-reference/block-storage/drivers/hitachi-storage-volume-driver.xml:56(title) ./doc/config-reference/block-storage/drivers/lenovo-driver.xml:48(title) ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:66(title) ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:327(title) ./doc/config-reference/block-storage/drivers/zfssa-nfs-driver.xml:15(title) msgid "Supported operations" msgstr "" @@ -7717,228 +7717,231 @@ msgstr "" msgid "Alternatively, the dispersion report can also be output in JSON format. This allows it to be more easily consumed by third-party utilities:" msgstr "" -#. Usage documented in http://docs.openstack.org/developer/swift/overview_large_objects.html -#: ./doc/config-reference/object-storage/section_object-storage-features.xml:474(title) +#: ./doc/config-reference/object-storage/section_object-storage-features.xml:473(title) msgid "Static Large Object (SLO) support" msgstr "" -#: ./doc/config-reference/object-storage/section_object-storage-features.xml:475(para) +#: ./doc/config-reference/object-storage/section_object-storage-features.xml:474(para) msgid "This feature is very similar to Dynamic Large Object (DLO) support in that it enables the user to upload many objects concurrently and afterwards download them as a single object. It is different in that it does not rely on eventually consistent container listings to do so. Instead, a user-defined manifest of the object segments is used." msgstr "" -#: ./doc/config-reference/object-storage/section_object-storage-features.xml:487(title) +#: ./doc/config-reference/object-storage/section_object-storage-features.xml:481(para) +msgid "For more information regarding SLO usage and support, please see: Static Large Objects." +msgstr "" + +#: ./doc/config-reference/object-storage/section_object-storage-features.xml:489(title) msgid "Container quotas" msgstr "" -#: ./doc/config-reference/object-storage/section_object-storage-features.xml:488(para) +#: ./doc/config-reference/object-storage/section_object-storage-features.xml:490(para) msgid "The container_quotas middleware implements simple quotas that can be imposed on Object Storage containers by a user with the ability to set container metadata, most likely the account administrator. This can be useful for limiting the scope of containers that are delegated to non-admin users, exposed to form uploads, or just as a self-imposed sanity check." msgstr "" -#: ./doc/config-reference/object-storage/section_object-storage-features.xml:496(para) +#: ./doc/config-reference/object-storage/section_object-storage-features.xml:498(para) msgid "Any object operations that exceed these quotas return a Forbidden (403) status code." msgstr "" -#: ./doc/config-reference/object-storage/section_object-storage-features.xml:498(para) +#: ./doc/config-reference/object-storage/section_object-storage-features.xml:500(para) msgid "Quotas are subject to several limitations: eventual consistency, the timeliness of the cached container_info (60 second TTL by default), and it is unable to reject chunked transfer uploads that exceed the quota (though once the quota is exceeded, new chunked transfers are refused)." msgstr "" -#: ./doc/config-reference/object-storage/section_object-storage-features.xml:504(para) +#: ./doc/config-reference/object-storage/section_object-storage-features.xml:506(para) msgid "Set quotas by adding meta values to the container. These values are validated when you set them:" msgstr "" -#: ./doc/config-reference/object-storage/section_object-storage-features.xml:508(para) +#: ./doc/config-reference/object-storage/section_object-storage-features.xml:510(para) msgid "X-Container-Meta-Quota-Bytes: Maximum size of the container, in bytes." msgstr "" -#: ./doc/config-reference/object-storage/section_object-storage-features.xml:512(para) +#: ./doc/config-reference/object-storage/section_object-storage-features.xml:514(para) msgid "X-Container-Meta-Quota-Count: Maximum object count of the container." msgstr "" -#: ./doc/config-reference/object-storage/section_object-storage-features.xml:521(title) +#: ./doc/config-reference/object-storage/section_object-storage-features.xml:523(title) msgid "Account quotas" msgstr "" -#: ./doc/config-reference/object-storage/section_object-storage-features.xml:522(para) +#: ./doc/config-reference/object-storage/section_object-storage-features.xml:524(para) msgid "The x-account-meta-quota-bytes metadata entry must be requests (PUT, POST) if a given account quota (in bytes) is exceeded while DELETE requests are still allowed." msgstr "" -#: ./doc/config-reference/object-storage/section_object-storage-features.xml:526(para) +#: ./doc/config-reference/object-storage/section_object-storage-features.xml:528(para) msgid "The x-account-meta-quota-bytes metadata entry must be set to store and enable the quota. Write requests to this metadata entry are only permitted for resellers. There is no account quota limitation on a reseller account even if x-account-meta-quota-bytes is set." msgstr "" -#: ./doc/config-reference/object-storage/section_object-storage-features.xml:533(para) +#: ./doc/config-reference/object-storage/section_object-storage-features.xml:535(para) msgid "Any object PUT operations that exceed the quota return a 413 response (request entity too large) with a descriptive body." msgstr "" -#: ./doc/config-reference/object-storage/section_object-storage-features.xml:536(para) +#: ./doc/config-reference/object-storage/section_object-storage-features.xml:538(para) msgid "The following command uses an admin account that own the Reseller role to set a quota on the test account:" msgstr "" -#: ./doc/config-reference/object-storage/section_object-storage-features.xml:540(para) +#: ./doc/config-reference/object-storage/section_object-storage-features.xml:542(para) msgid "Here is the stat listing of an account where quota has been set:" msgstr "" -#: ./doc/config-reference/object-storage/section_object-storage-features.xml:550(para) +#: ./doc/config-reference/object-storage/section_object-storage-features.xml:552(para) msgid "This command removes the account quota:" msgstr "" -#: ./doc/config-reference/object-storage/section_object-storage-features.xml:554(title) +#: ./doc/config-reference/object-storage/section_object-storage-features.xml:556(title) msgid "Bulk delete" msgstr "" -#: ./doc/config-reference/object-storage/section_object-storage-features.xml:555(para) +#: ./doc/config-reference/object-storage/section_object-storage-features.xml:557(para) msgid "Use bulk-delete to delete multiple files from an account with a single request. Responds to DELETE requests with a header 'X-Bulk-Delete: true_value'. The body of the DELETE request is a new line-separated list of files to delete. The files listed must be URL encoded and in the form:" msgstr "" -#: ./doc/config-reference/object-storage/section_object-storage-features.xml:565(para) +#: ./doc/config-reference/object-storage/section_object-storage-features.xml:567(para) msgid "If all files are successfully deleted (or did not exist), the operation returns HTTPOk. If any files failed to delete, the operation returns HTTPBadGateway. In both cases, the response body is a JSON dictionary that shows the number of files that were successfully deleted or not found. The files that failed are listed." msgstr "" -#: ./doc/config-reference/object-storage/section_object-storage-features.xml:578(title) +#: ./doc/config-reference/object-storage/section_object-storage-features.xml:580(title) msgid "Drive audit" msgstr "" -#: ./doc/config-reference/object-storage/section_object-storage-features.xml:579(para) +#: ./doc/config-reference/object-storage/section_object-storage-features.xml:581(para) msgid "The configuration items reference a script that can be run by using to watch for bad drives. If errors are detected, it unmounts the bad drive so that OpenStack Object Storage can work around it. It takes the following options:" msgstr "" -#: ./doc/config-reference/object-storage/section_object-storage-features.xml:591(title) +#: ./doc/config-reference/object-storage/section_object-storage-features.xml:593(title) msgid "Form post" msgstr "" -#: ./doc/config-reference/object-storage/section_object-storage-features.xml:592(para) +#: ./doc/config-reference/object-storage/section_object-storage-features.xml:594(para) msgid "Middleware that enables you to upload objects to a cluster by using an HTML form ." msgstr "" -#: ./doc/config-reference/object-storage/section_object-storage-features.xml:596(para) +#: ./doc/config-reference/object-storage/section_object-storage-features.xml:598(para) msgid "The format of the form is:" msgstr "" -#: ./doc/config-reference/object-storage/section_object-storage-features.xml:613(para) +#: ./doc/config-reference/object-storage/section_object-storage-features.xml:615(para) msgid "In the form:" msgstr "" -#: ./doc/config-reference/object-storage/section_object-storage-features.xml:619(literal) +#: ./doc/config-reference/object-storage/section_object-storage-features.xml:621(literal) msgid "action=\"<swift-url>\"" msgstr "" -#: ./doc/config-reference/object-storage/section_object-storage-features.xml:621(para) +#: ./doc/config-reference/object-storage/section_object-storage-features.xml:623(para) msgid "The URL to the Object Storage destination, such as https://swift-cluster.example.com/v1/AUTH_account/container/object_prefix." msgstr "" -#: ./doc/config-reference/object-storage/section_object-storage-features.xml:625(para) +#: ./doc/config-reference/object-storage/section_object-storage-features.xml:627(para) msgid "The name of each uploaded file is appended to the specified swift-url. So, you can upload directly to the root of container with a URL like https://swift-cluster.example.com/v1/AUTH_account/container/." msgstr "" -#: ./doc/config-reference/object-storage/section_object-storage-features.xml:631(para) +#: ./doc/config-reference/object-storage/section_object-storage-features.xml:633(para) msgid "Optionally, you can include an object prefix to separate different users' uploads, such as https://swift-cluster.example.com/v1/AUTH_account/container/object_prefix." msgstr "" -#: ./doc/config-reference/object-storage/section_object-storage-features.xml:640(literal) +#: ./doc/config-reference/object-storage/section_object-storage-features.xml:642(literal) msgid "method=\"POST\"" msgstr "" -#: ./doc/config-reference/object-storage/section_object-storage-features.xml:641(para) +#: ./doc/config-reference/object-storage/section_object-storage-features.xml:643(para) msgid "The form method must be ." msgstr "" -#: ./doc/config-reference/object-storage/section_object-storage-features.xml:648(literal) +#: ./doc/config-reference/object-storage/section_object-storage-features.xml:650(literal) msgid "enctype=\"multipart/form-data" msgstr "" -#: ./doc/config-reference/object-storage/section_object-storage-features.xml:649(para) +#: ./doc/config-reference/object-storage/section_object-storage-features.xml:651(para) msgid "The enctype must be set to multipart/form-data." msgstr "" -#: ./doc/config-reference/object-storage/section_object-storage-features.xml:656(literal) +#: ./doc/config-reference/object-storage/section_object-storage-features.xml:658(literal) msgid "name=\"redirect\"" msgstr "" -#: ./doc/config-reference/object-storage/section_object-storage-features.xml:657(para) +#: ./doc/config-reference/object-storage/section_object-storage-features.xml:659(para) msgid "The URL to which to redirect the browser after the upload completes. The URL has status and message query parameters added to it that indicate the HTTP status code for the upload and, optionally, additional error information. The 2nn status code indicates success. If an error occurs, the URL might include error information, such as \"max_file_size exceeded\"." msgstr "" -#: ./doc/config-reference/object-storage/section_object-storage-features.xml:670(literal) +#: ./doc/config-reference/object-storage/section_object-storage-features.xml:672(literal) msgid "name=\"max_file_size\"" msgstr "" -#: ./doc/config-reference/object-storage/section_object-storage-features.xml:671(para) +#: ./doc/config-reference/object-storage/section_object-storage-features.xml:673(para) msgid "Required. The maximum number of bytes that can be uploaded in a single file upload." msgstr "" -#: ./doc/config-reference/object-storage/section_object-storage-features.xml:679(literal) +#: ./doc/config-reference/object-storage/section_object-storage-features.xml:681(literal) msgid "name=\"max_file_count\"" msgstr "" -#: ./doc/config-reference/object-storage/section_object-storage-features.xml:680(para) +#: ./doc/config-reference/object-storage/section_object-storage-features.xml:682(para) msgid "Required. The maximum number of files that can be uploaded with the form." msgstr "" -#: ./doc/config-reference/object-storage/section_object-storage-features.xml:688(literal) +#: ./doc/config-reference/object-storage/section_object-storage-features.xml:690(literal) msgid "name=\"expires\"" msgstr "" -#: ./doc/config-reference/object-storage/section_object-storage-features.xml:690(para) +#: ./doc/config-reference/object-storage/section_object-storage-features.xml:692(para) msgid "The expiration date and time for the form in UNIX Epoch time stamp format. After this date and time, the form is no longer valid." msgstr "" -#: ./doc/config-reference/object-storage/section_object-storage-features.xml:696(para) ./doc/config-reference/object-storage/section_object-storage-features.xml:746(para) +#: ./doc/config-reference/object-storage/section_object-storage-features.xml:698(para) ./doc/config-reference/object-storage/section_object-storage-features.xml:748(para) msgid "For example, 1440619048 is equivalent to Mon, Wed, 26 Aug 2015 19:57:28 GMT." msgstr "" -#: ./doc/config-reference/object-storage/section_object-storage-features.xml:704(literal) +#: ./doc/config-reference/object-storage/section_object-storage-features.xml:706(literal) msgid "name=\"signature\"" msgstr "" -#: ./doc/config-reference/object-storage/section_object-storage-features.xml:706(para) +#: ./doc/config-reference/object-storage/section_object-storage-features.xml:708(para) msgid "The HMAC-SHA1 signature of the form. This sample Python code shows how to compute the signature:" msgstr "" -#: ./doc/config-reference/object-storage/section_object-storage-features.xml:722(para) +#: ./doc/config-reference/object-storage/section_object-storage-features.xml:724(para) msgid "The key is the value of the X-Account-Meta-Temp-URL-Key header on the account." msgstr "" -#: ./doc/config-reference/object-storage/section_object-storage-features.xml:725(para) +#: ./doc/config-reference/object-storage/section_object-storage-features.xml:727(para) msgid "Use the full path from the /v1/ value and onward." msgstr "" -#: ./doc/config-reference/object-storage/section_object-storage-features.xml:729(para) +#: ./doc/config-reference/object-storage/section_object-storage-features.xml:731(para) msgid "During testing, you can use the command-line tool to compute the expires and signature values." msgstr "" -#: ./doc/config-reference/object-storage/section_object-storage-features.xml:739(literal) +#: ./doc/config-reference/object-storage/section_object-storage-features.xml:741(literal) msgid "name=\"x_delete_at\"" msgstr "" -#: ./doc/config-reference/object-storage/section_object-storage-features.xml:741(para) +#: ./doc/config-reference/object-storage/section_object-storage-features.xml:743(para) msgid "The date and time in UNIX Epoch time stamp format when the object will be removed." msgstr "" -#: ./doc/config-reference/object-storage/section_object-storage-features.xml:750(para) +#: ./doc/config-reference/object-storage/section_object-storage-features.xml:752(para) msgid "This attribute enables you to specify the X-Delete- At header value in the form ." msgstr "" -#: ./doc/config-reference/object-storage/section_object-storage-features.xml:758(literal) +#: ./doc/config-reference/object-storage/section_object-storage-features.xml:760(literal) msgid "name=\"x_delete_after\"" msgstr "" -#: ./doc/config-reference/object-storage/section_object-storage-features.xml:760(para) +#: ./doc/config-reference/object-storage/section_object-storage-features.xml:762(para) msgid "The number of seconds after which the object is removed. Internally, the Object Storage system stores this value in the X-Delete-At metadata item. This attribute enables you to specify the X-Delete-After header value in the form ." msgstr "" -#: ./doc/config-reference/object-storage/section_object-storage-features.xml:770(literal) +#: ./doc/config-reference/object-storage/section_object-storage-features.xml:772(literal) msgid "type=\"file\" name=\"filexx\"" msgstr "" -#: ./doc/config-reference/object-storage/section_object-storage-features.xml:772(para) +#: ./doc/config-reference/object-storage/section_object-storage-features.xml:774(para) msgid "Optional. One or more files to upload. Must appear after the other attributes to be processed correctly. If attributes come after the file attribute, they are not sent with the sub- request because on the server side, all attributes in the file cannot be parsed unless the whole file is read into memory and the server does not have enough memory to service these requests. So, attributes that follow the file attribute are ignored." msgstr "" -#: ./doc/config-reference/object-storage/section_object-storage-features.xml:787(title) +#: ./doc/config-reference/object-storage/section_object-storage-features.xml:789(title) msgid "Static web sites" msgstr "" -#: ./doc/config-reference/object-storage/section_object-storage-features.xml:788(para) +#: ./doc/config-reference/object-storage/section_object-storage-features.xml:790(para) msgid "When configured, this middleware serves container data as a static web site with index file and error file resolution and optional file listings. This mode is normally only active for anonymous requests." msgstr "" @@ -8782,6 +8785,206 @@ msgstr "" msgid "The following configuration options are available for the NFS back-end backup driver." msgstr "" +#: ./doc/config-reference/block-storage/drivers/zfssa-iscsi-driver.xml:5(title) +msgid "Oracle ZFS Storage Appliance iSCSI driver" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/zfssa-iscsi-driver.xml:6(para) +msgid "Oracle ZFS Storage Appliances (ZFSSAs) provide advanced software to protect data, speed tuning and troubleshooting, and deliver high performance and high availability. Through the Oracle ZFSSA iSCSI Driver, OpenStack Block Storage can use an Oracle ZFSSA as a block storage resource. The driver enables you to create iSCSI volumes that an OpenStack Block Storage server can allocate to any virtual machine running on a compute host. The Oracle ZFSSA iSCSI Driver, version 1.0.0 and later, supports ZFSSA software release 2013.1.2.0 and later." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/zfssa-iscsi-driver.xml:17(para) +msgid "Enable RESTful service on the ZFSSA Storage Appliance." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/zfssa-iscsi-driver.xml:20(para) +msgid "Create a new user on the appliance with the following authorizations:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/zfssa-iscsi-driver.xml:23(code) +msgid "scope=stmf - allow_configure=true" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/zfssa-iscsi-driver.xml:26(code) +msgid "scope=nas - allow_clone=true, allow_createProject=true, allow_createShare=true, allow_changeSpaceProps=true, allow_changeGeneralProps=true, allow_destroy=true, allow_rollback=true, allow_takeSnap=true" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/zfssa-iscsi-driver.xml:29(para) +msgid "You can create a role with authorizations as follows:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/zfssa-iscsi-driver.xml:41(para) +msgid "You can create a user with a specific role as follows:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/zfssa-iscsi-driver.xml:49(para) +msgid "You can also run this workflow to automate the above tasks." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/zfssa-iscsi-driver.xml:55(para) +msgid "Ensure that the ZFSSA iSCSI service is online. If the ZFSSA iSCSI service is not online, enable the service by using the BUI, CLI or REST API in the appliance." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/zfssa-iscsi-driver.xml:67(para) +msgid "Define the following required properties in the cinder.conf file:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/zfssa-iscsi-driver.xml:69(replaceable) ./doc/config-reference/block-storage/drivers/zfssa-nfs-driver.xml:177(replaceable) +msgid "myhost" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/zfssa-iscsi-driver.xml:70(replaceable) ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:81(replaceable) ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:145(replaceable) ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:353(replaceable) ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:410(replaceable) ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:489(replaceable) ./doc/config-reference/block-storage/drivers/zfssa-nfs-driver.xml:178(replaceable) +msgid "username" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/zfssa-iscsi-driver.xml:72(replaceable) ./doc/config-reference/block-storage/drivers/zfssa-nfs-driver.xml:181(replaceable) +msgid "mypool" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/zfssa-iscsi-driver.xml:73(replaceable) +msgid "myproject" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/zfssa-iscsi-driver.xml:74(replaceable) ./doc/config-reference/block-storage/drivers/hds-hnas-driver.xml:228(literal) +msgid "default" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/zfssa-iscsi-driver.xml:75(replaceable) +msgid "w.x.y.z:3260" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/zfssa-iscsi-driver.xml:76(replaceable) +msgid "e1000g0" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/zfssa-iscsi-driver.xml:77(para) +msgid "Optionally, you can define additional properties." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/zfssa-iscsi-driver.xml:78(para) +msgid "Target interfaces can be seen as follows in the CLI:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/zfssa-iscsi-driver.xml:86(para) +msgid "Do not use management interfaces for zfssa_target_interfaces." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/zfssa-iscsi-driver.xml:96(para) +msgid "Create and delete volumes" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/zfssa-iscsi-driver.xml:99(para) +msgid "Extend volume" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/zfssa-iscsi-driver.xml:102(para) +msgid "Create and delete snapshots" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/zfssa-iscsi-driver.xml:105(para) +msgid "Create volume from snapshot" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/zfssa-iscsi-driver.xml:108(para) +msgid "Delete volume snapshots" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/zfssa-iscsi-driver.xml:111(para) ./doc/config-reference/block-storage/drivers/zfssa-nfs-driver.xml:21(para) +msgid "Attach and detach volumes" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/zfssa-iscsi-driver.xml:114(para) +msgid "Get volume stats" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/zfssa-iscsi-driver.xml:117(para) +msgid "Clone volumes" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/zfssa-iscsi-driver.xml:120(para) ./doc/config-reference/block-storage/drivers/zfssa-nfs-driver.xml:39(para) +msgid "Volume migration" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/zfssa-iscsi-driver.xml:125(title) +msgid "ZFSSA assisted volume migration" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/zfssa-iscsi-driver.xml:126(para) +msgid "The ZFSSA iSCSI driver supports storage assisted volume migration starting in the Liberty release. This feature uses remote replication feature on the ZFSSA. Volumes can be migrated between two backends configured not only to the same ZFSSA but also between two separate ZFSSAs altogether." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/zfssa-iscsi-driver.xml:131(para) +msgid "The following conditions must be met in order to use ZFSSA assisted volume migration:" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/zfssa-iscsi-driver.xml:136(para) +msgid "Both the source and target backends are configured to ZFSSAs." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/zfssa-iscsi-driver.xml:139(para) +msgid "Remote replication service on the source and target appliance is enabled." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/zfssa-iscsi-driver.xml:142(para) +msgid "The ZFSSA to which the target backend is configured should be configured as a target in the remote replication service of the ZFSSA configured to the source backend. The remote replication target needs to be configured even when the source and the destination for volume migration are the same ZFSSA. Define zfssa_replication_ip in the cinder.conf of the source backend as the IP address used to register the target ZFSSA in the remote replication service of the source ZFSSA." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/zfssa-iscsi-driver.xml:152(para) +msgid "The name of the iSCSI target group(zfssa_target_group) on the source and the destination ZFSSA is the same." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/zfssa-iscsi-driver.xml:157(para) +msgid "The volume is not attached and is in available state." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/zfssa-iscsi-driver.xml:161(para) +msgid "If any of the above conditions are not met, the driver will proceed with generic volume migration." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/zfssa-iscsi-driver.xml:163(para) +msgid "The ZFSSA user on the source and target appliances will need to have additional role authorizations for assisted volume migration to work. In scope nas, set allow_rrtarget and allow_rrsource to true." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/zfssa-iscsi-driver.xml:175(title) +msgid "Supported extra specs" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/zfssa-iscsi-driver.xml:176(para) +msgid "Extra specs provide the OpenStack storage admin the flexibility to create volumes with different characteristics from the ones specified in cinder.conf. The admin will specify the volume properties as keys at volume type creation. When a user requests a volume of this volume type, the volume will be created with the properties specified as extra specs." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/zfssa-iscsi-driver.xml:183(para) +msgid "The following extra specs scoped keys are supported by the driver" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/zfssa-iscsi-driver.xml:187(para) +msgid "zfssa:volblocksize" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/zfssa-iscsi-driver.xml:190(para) +msgid "zfssa:sparse" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/zfssa-iscsi-driver.xml:193(para) +msgid "zfssa:compression" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/zfssa-iscsi-driver.xml:196(para) +msgid "zfssa:logbias" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/zfssa-iscsi-driver.xml:199(para) +msgid "Volume types can be created using the cinder type-create. Extra spec keys can be added using cinder type-key command." +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/zfssa-iscsi-driver.xml:205(title) ./doc/config-reference/block-storage/drivers/dell-storagecenter-driver.xml:139(title) ./doc/config-reference/block-storage/drivers/ceph-rbd-volume-driver.xml:111(title) ./doc/config-reference/block-storage/drivers/zfssa-nfs-driver.xml:205(title) +msgid "Driver options" +msgstr "" + +#: ./doc/config-reference/block-storage/drivers/zfssa-iscsi-driver.xml:206(para) +msgid "The Oracle ZFSSA iSCSI Driver supports these options:" +msgstr "" + #: ./doc/config-reference/block-storage/drivers/glusterfs-driver.xml:7(para) msgid "GlusterFS is an open-source scalable distributed file system that is able to grow to petabytes and beyond in size. More information can be found on Gluster's homepage." msgstr "" @@ -9030,7 +9233,7 @@ msgstr "" msgid "maxIOPS" msgstr "" -#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:240(literal) ./doc/config-reference/block-storage/drivers/zfssa-nfs-driver.xml:192(replaceable) +#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:240(literal) ./doc/config-reference/block-storage/drivers/zfssa-nfs-driver.xml:195(replaceable) msgid "latency" msgstr "" @@ -10370,10 +10573,6 @@ msgstr "" msgid "Use the following instructions to update the configuration file for fibre channel: " msgstr "" -#: ./doc/config-reference/block-storage/drivers/dell-storagecenter-driver.xml:139(title) ./doc/config-reference/block-storage/drivers/ceph-rbd-volume-driver.xml:111(title) ./doc/config-reference/block-storage/drivers/zfssa-nfs-driver.xml:202(title) -msgid "Driver options" -msgstr "" - #: ./doc/config-reference/block-storage/drivers/dell-storagecenter-driver.xml:140(para) msgid "The following table contains the configation options specific to the Dell Storage Center volume driver." msgstr "" @@ -10710,10 +10909,6 @@ msgstr "" msgid "Configuration options for service labels" msgstr "" -#: ./doc/config-reference/block-storage/drivers/hds-hnas-driver.xml:228(literal) -msgid "default" -msgstr "" - #: ./doc/config-reference/block-storage/drivers/hds-hnas-driver.xml:230(para) msgid "When a create_volume call with a certain volume type happens, the volume type will try to be matched up with this tag. In each configuration file you must define the default volume type in the service labels and, if no volume type is specified, the default is used. Other labels are case sensitive and should match exactly. If no configured volume types match the incoming requested type, an error occurs in the volume creation." msgstr "" @@ -12841,10 +13036,6 @@ msgstr "" msgid "port" msgstr "" -#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:81(replaceable) ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:145(replaceable) ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:353(replaceable) ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:410(replaceable) ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:489(replaceable) ./doc/config-reference/block-storage/drivers/zfssa-nfs-driver.xml:175(replaceable) -msgid "username" -msgstr "" - #: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:84(para) ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:356(para) ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:504(para) msgid "To use the iSCSI protocol, you must override the default value of with iscsi." msgstr "" @@ -14274,143 +14465,131 @@ msgstr "" msgid "Create, extend, delete volumes" msgstr "" -#: ./doc/config-reference/block-storage/drivers/zfssa-nfs-driver.xml:21(para) -msgid "Attach and detach volumes" -msgstr "" - #: ./doc/config-reference/block-storage/drivers/zfssa-nfs-driver.xml:24(para) msgid "Create, delete snapshots" msgstr "" -#: ./doc/config-reference/block-storage/drivers/zfssa-nfs-driver.xml:41(title) +#: ./doc/config-reference/block-storage/drivers/zfssa-nfs-driver.xml:44(title) msgid "Appliance configuration" msgstr "" -#: ./doc/config-reference/block-storage/drivers/zfssa-nfs-driver.xml:42(para) +#: ./doc/config-reference/block-storage/drivers/zfssa-nfs-driver.xml:45(para) msgid "Appliance configuration using the command line interface (CLI) is described below. To access the CLI, ensure SSH remote access is enabled, which is the default. You can also perform configuration using the browser user interface (BUI) or the RESTful API. Please refer to the Oracle ZFS Storage Appliance documentation for details on how to configure the Oracle ZFS Storage Appliance using the BUI, CLI and RESTful API." msgstr "" -#: ./doc/config-reference/block-storage/drivers/zfssa-nfs-driver.xml:52(para) +#: ./doc/config-reference/block-storage/drivers/zfssa-nfs-driver.xml:55(para) msgid "Log in to the Oracle ZFS Storage Appliance CLI and enable the REST service. REST service needs to stay online for this driver to function." msgstr "" -#: ./doc/config-reference/block-storage/drivers/zfssa-nfs-driver.xml:57(para) +#: ./doc/config-reference/block-storage/drivers/zfssa-nfs-driver.xml:60(para) msgid "Create a new storage pool on the appliance if you do not want to use an existing one. This storage pool is named 'mypool' for the sake of this documentation." msgstr "" -#: ./doc/config-reference/block-storage/drivers/zfssa-nfs-driver.xml:61(para) +#: ./doc/config-reference/block-storage/drivers/zfssa-nfs-driver.xml:64(para) msgid "Create a new project and share in the storage pool (mypool) if you do not want to use existing ones. This driver will create a project and share by the names specified in cinder.conf, if the a project or share by that name doesnt already exist in the storage pool (mypool). The project and share are named 'NFSProject' and 'nfs_share' in the sample cinder.conf entries below." msgstr "" -#: ./doc/config-reference/block-storage/drivers/zfssa-nfs-driver.xml:67(para) +#: ./doc/config-reference/block-storage/drivers/zfssa-nfs-driver.xml:70(para) msgid "To perform driver operations, create a role with the following authorizations:" msgstr "" -#: ./doc/config-reference/block-storage/drivers/zfssa-nfs-driver.xml:71(code) +#: ./doc/config-reference/block-storage/drivers/zfssa-nfs-driver.xml:74(code) msgid "scope=svc - allow_administer=true, allow_restart=true, allow_configure=true" msgstr "" -#: ./doc/config-reference/block-storage/drivers/zfssa-nfs-driver.xml:74(code) +#: ./doc/config-reference/block-storage/drivers/zfssa-nfs-driver.xml:77(code) msgid "scope=nas - pool=pool_name, project=project_name, share=share_name, allow_clone=true, allow_createProject=true, allow_createShare=true, allow_changeSpaceProps=true, allow_changeGeneralProps=true, allow_destroy=true, allow_rollback=true, allow_takeSnap=true" msgstr "" -#: ./doc/config-reference/block-storage/drivers/zfssa-nfs-driver.xml:77(para) +#: ./doc/config-reference/block-storage/drivers/zfssa-nfs-driver.xml:80(para) msgid "The following examples show how to create a role with authorizations." msgstr "" -#: ./doc/config-reference/block-storage/drivers/zfssa-nfs-driver.xml:90(para) +#: ./doc/config-reference/block-storage/drivers/zfssa-nfs-driver.xml:93(para) msgid "The following properties need to be set when the scope of this role needs to be limited to a pool (mypool), a project (NFSProject) and a share (nfs_share) created in the steps above. This will prevent the user assigned to this role from being used to modify other pools, projects and shares." msgstr "" -#: ./doc/config-reference/block-storage/drivers/zfssa-nfs-driver.xml:96(para) +#: ./doc/config-reference/block-storage/drivers/zfssa-nfs-driver.xml:99(para) msgid "The following properties only need to be set when a share or a project has not been created following the steps above and wish to allow the driver to create them for you." msgstr "" -#: ./doc/config-reference/block-storage/drivers/zfssa-nfs-driver.xml:108(para) +#: ./doc/config-reference/block-storage/drivers/zfssa-nfs-driver.xml:111(para) msgid "Create a new user or modify an existing one and assign the new role to the user." msgstr "" -#: ./doc/config-reference/block-storage/drivers/zfssa-nfs-driver.xml:110(para) +#: ./doc/config-reference/block-storage/drivers/zfssa-nfs-driver.xml:113(para) msgid "The following example shows how to create a new user and assign the new role to the user." msgstr "" -#: ./doc/config-reference/block-storage/drivers/zfssa-nfs-driver.xml:120(para) +#: ./doc/config-reference/block-storage/drivers/zfssa-nfs-driver.xml:123(para) msgid "Ensure that NFS and HTTP services on the appliance are online. Note the HTTPS port number for later entry in the cinder service configuration file (cinder.conf). This driver uses WebDAV over HTTPS to create snapshots and clones of volumes, and therefore needs to have the HTTP service online." msgstr "" -#: ./doc/config-reference/block-storage/drivers/zfssa-nfs-driver.xml:123(para) +#: ./doc/config-reference/block-storage/drivers/zfssa-nfs-driver.xml:126(para) msgid "The following example illustrates enabling the services and showing their properties." msgstr "" -#: ./doc/config-reference/block-storage/drivers/zfssa-nfs-driver.xml:141(para) +#: ./doc/config-reference/block-storage/drivers/zfssa-nfs-driver.xml:144(para) msgid "Create a network interface to be used exclusively for data. An existing network interface may also be used. The following example illustrates how to make a network interface for data traffic flow only." msgstr "" -#: ./doc/config-reference/block-storage/drivers/zfssa-nfs-driver.xml:144(para) +#: ./doc/config-reference/block-storage/drivers/zfssa-nfs-driver.xml:147(para) msgid "For better performance and reliability, it is recommended to configure a separate subnet exclusively for data traffic in your cloud environment." msgstr "" -#: ./doc/config-reference/block-storage/drivers/zfssa-nfs-driver.xml:152(para) +#: ./doc/config-reference/block-storage/drivers/zfssa-nfs-driver.xml:155(para) msgid "For clustered controller systems, the following verification is required in addition to the above steps. Skip this step if a standalone system is used." msgstr "" -#: ./doc/config-reference/block-storage/drivers/zfssa-nfs-driver.xml:155(para) +#: ./doc/config-reference/block-storage/drivers/zfssa-nfs-driver.xml:158(para) msgid "Verify that both the newly created pool and the network interface are of type \"singleton\" and are not locked to the current controller. This approach ensures that the pool and the interface used for data always belong to the active controller, regardless of the current state of the cluster. Verify that both the network interface used for management and data, and the storage pool belong to the same head." msgstr "" -#: ./doc/config-reference/block-storage/drivers/zfssa-nfs-driver.xml:161(para) +#: ./doc/config-reference/block-storage/drivers/zfssa-nfs-driver.xml:164(para) msgid "There will be a short service interruption during failback/takeover, but once the process is complete, the driver should be able to access the ZFSSA for data as well as for management." msgstr "" -#: ./doc/config-reference/block-storage/drivers/zfssa-nfs-driver.xml:168(title) +#: ./doc/config-reference/block-storage/drivers/zfssa-nfs-driver.xml:171(title) msgid "Cinder service configuration" msgstr "" -#: ./doc/config-reference/block-storage/drivers/zfssa-nfs-driver.xml:171(para) +#: ./doc/config-reference/block-storage/drivers/zfssa-nfs-driver.xml:174(para) msgid "Define the following required properties in the cinder.conf configuration file:" msgstr "" -#: ./doc/config-reference/block-storage/drivers/zfssa-nfs-driver.xml:174(replaceable) -msgid "myhost" -msgstr "" - -#: ./doc/config-reference/block-storage/drivers/zfssa-nfs-driver.xml:177(replaceable) +#: ./doc/config-reference/block-storage/drivers/zfssa-nfs-driver.xml:180(replaceable) msgid "mydata" msgstr "" -#: ./doc/config-reference/block-storage/drivers/zfssa-nfs-driver.xml:178(replaceable) -msgid "mypool" -msgstr "" - -#: ./doc/config-reference/block-storage/drivers/zfssa-nfs-driver.xml:180(para) +#: ./doc/config-reference/block-storage/drivers/zfssa-nfs-driver.xml:183(para) msgid "Management interface san_ip can be used instead of zfssa_data_ip, but it is not recommended." msgstr "" -#: ./doc/config-reference/block-storage/drivers/zfssa-nfs-driver.xml:186(para) +#: ./doc/config-reference/block-storage/drivers/zfssa-nfs-driver.xml:189(para) msgid "You can also define the following additional properties in the cinder.conf configuration file:" msgstr "" -#: ./doc/config-reference/block-storage/drivers/zfssa-nfs-driver.xml:188(replaceable) +#: ./doc/config-reference/block-storage/drivers/zfssa-nfs-driver.xml:191(replaceable) msgid "NFSProject" msgstr "" -#: ./doc/config-reference/block-storage/drivers/zfssa-nfs-driver.xml:189(replaceable) +#: ./doc/config-reference/block-storage/drivers/zfssa-nfs-driver.xml:192(replaceable) msgid "nfs_share" msgstr "" -#: ./doc/config-reference/block-storage/drivers/zfssa-nfs-driver.xml:191(replaceable) +#: ./doc/config-reference/block-storage/drivers/zfssa-nfs-driver.xml:194(replaceable) msgid "off" msgstr "" -#: ./doc/config-reference/block-storage/drivers/zfssa-nfs-driver.xml:197(para) +#: ./doc/config-reference/block-storage/drivers/zfssa-nfs-driver.xml:200(para) msgid "The driver does not use the file specified in the nfs_shares_config option." msgstr "" -#: ./doc/config-reference/block-storage/drivers/zfssa-nfs-driver.xml:203(para) +#: ./doc/config-reference/block-storage/drivers/zfssa-nfs-driver.xml:206(para) msgid "The Oracle ZFS Storage Appliance NFS driver supports these options:" msgstr "" -#: ./doc/config-reference/block-storage/drivers/zfssa-nfs-driver.xml:205(para) +#: ./doc/config-reference/block-storage/drivers/zfssa-nfs-driver.xml:208(para) msgid "This driver shares additional NFS configuration options with the generic NFS driver. For a description of these, see ." msgstr "" diff --git a/doc/glossary/locale/glossary.pot b/doc/glossary/locale/glossary.pot index c674740f9d..d0b2222068 100644 --- a/doc/glossary/locale/glossary.pot +++ b/doc/glossary/locale/glossary.pot @@ -1,7 +1,7 @@ msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" -"POT-Creation-Date: 2015-10-04 06:17+0000\n" +"POT-Creation-Date: 2015-10-08 06:30+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -2482,7 +2482,7 @@ msgid "firewalls" msgstr "" #: ./doc/glossary/glossary-terms.xml:3464(para) -msgid "Used to restrict communications between hosts and/or nodes, implemented in Compute using iptables, arptables, ip6tables, and etables." +msgid "Used to restrict communications between hosts and/or nodes, implemented in Compute using iptables, arptables, ip6tables, and ebtables." msgstr "" #: ./doc/glossary/glossary-terms.xml:3471(glossterm) diff --git a/doc/glossary/locale/ja.po b/doc/glossary/locale/ja.po index b24401ef6a..bf395b6b3b 100644 --- a/doc/glossary/locale/ja.po +++ b/doc/glossary/locale/ja.po @@ -11,7 +11,7 @@ msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" -"POT-Creation-Date: 2015-10-04 00:25+0000\n" +"POT-Creation-Date: 2015-10-08 06:01+0000\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" @@ -5473,13 +5473,6 @@ msgstr "" "Object Storage のオブジェクトが削除済みであることを示す印をつけるために使用さ" "れる。オブジェクトの削除後、他のノードにおいて更新されないことを保証する。" -msgid "" -"Used to restrict communications between hosts and/or nodes, implemented in " -"Compute using iptables, arptables, ip6tables, and etables." -msgstr "" -"ホストノード間の通信を制限する為に使用される。iptables, arptables, " -"ip6tables, ebtables を使用して Compute により実装される。" - msgid "Used to track segments of a large object within Object Storage." msgstr "Object Storage 内で大きなオブジェクトを管理するために使用される。" diff --git a/doc/glossary/locale/vi_VN.po b/doc/glossary/locale/vi_VN.po index c614094449..fb272c99a5 100644 --- a/doc/glossary/locale/vi_VN.po +++ b/doc/glossary/locale/vi_VN.po @@ -16,7 +16,7 @@ msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" -"POT-Creation-Date: 2015-10-04 00:25+0000\n" +"POT-Creation-Date: 2015-10-08 06:01+0000\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" @@ -5536,14 +5536,6 @@ msgstr "" "Được dùng để dánh dấu các object của Object Storage đã bị xóa; đảm bảo rằng " "các object này không được cập nhật trên một node khác sau khi nó đã bị xóa." -msgid "" -"Used to restrict communications between hosts and/or nodes, implemented in " -"Compute using iptables, arptables, ip6tables, and etables." -msgstr "" -"Được sử dụng để giới hạn các giao tiếp giữa các máy vật lý và/hoặc các node, " -"được cài đặt trong Compute bằng việc sử dụng iptables, arptables, ip6tables " -"và etables." - msgid "Used to track segments of a large object within Object Storage." msgstr "" "Được sử dụng để theo dõi các phân đoạn của các object lớn nằm trong Object " diff --git a/doc/install-guide/source/locale/install-guide.pot b/doc/install-guide/source/locale/install-guide.pot index 27c66db624..67f0501481 100644 --- a/doc/install-guide/source/locale/install-guide.pot +++ b/doc/install-guide/source/locale/install-guide.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Installation Guide 0.1\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2015-10-05 06:15+0000\n" +"POT-Creation-Date: 2015-10-08 06:30+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -16,535 +16,50 @@ msgstr "" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" -# #-#-#-#-# ceilometer-controller-install.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# ceilometer-nova.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# cinder-controller-node.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# cinder-storage-node.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# glance-install.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# heat-install.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# keystone-install.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# neutron-compute-install.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# neutron-controller-install-option1.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# neutron-controller-install-option2.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# neutron-controller-install.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# nova-compute-install.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# nova-controller-install.pot (Installation Guide 0.1) #-#-#-#-# -#: ../ceilometer-controller-install.rst:445 -#: ../ceilometer-controller-install.rst:457 ../ceilometer-nova.rst:110 -#: ../cinder-controller-node.rst:282 ../cinder-storage-node.rst:339 -#: ../glance-install.rst:249 ../glance-install.rst:313 ../heat-install.rst:328 -#: ../keystone-install.rst:165 ../neutron-compute-install.rst:133 -#: ../neutron-controller-install-option1.rst:185 -#: ../neutron-controller-install-option1.rst:314 -#: ../neutron-controller-install-option2.rst:182 -#: ../neutron-controller-install-option2.rst:337 -#: ../neutron-controller-install-option2.rst:409 -#: ../neutron-controller-install.rst:180 ../nova-compute-install.rst:186 -#: ../nova-controller-install.rst:325 -msgid "" -"(Optional) To assist with troubleshooting, enable verbose logging in the " -"``[DEFAULT]`` section:" -msgstr "" - -#: ../swift-finalize-installation.rst:5 -msgid "**Configure hashes and default storage policy**" -msgstr "" - -# #-#-#-#-# launch-instance-cinder.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# launch-instance-networks-private.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# launch-instance-networks-public.pot (Installation Guide 0.1) #-#-#-#-# -#: ../launch-instance-cinder.rst:65 ../launch-instance-networks-private.rst:96 -#: ../launch-instance-networks-public.rst:105 -msgid "**Example**" -msgstr "" - -#: ../overview.rst:134 -msgid "**Hardware requirements**" -msgstr "" - -#: ../overview.rst:82 -msgid "**Higher-level services**" -msgstr "" - -#: ../launch-instance-networks-public.rst:23 -msgid "**Networking Option 1: Provider networks - Overview**" -msgstr "" - -#: ../launch-instance-networks-public.rst:28 -msgid "**Networking Option 2: Provider networks - Connectivity**" -msgstr "" - -#: ../launch-instance-networks-private.rst:35 -msgid "**Networking Option 2: Self-service networks - Connectivity**" -msgstr "" - -#: ../launch-instance-networks-private.rst:30 -msgid "**Networking Option 2: Self-service networks - Overview**" -msgstr "" - -#: ../environment-dependencies.rst:97 -msgid "**On SLES 12:**" -msgstr "" - -#: ../environment-dependencies.rst:81 -msgid "**On openSUSE 13.2:**" -msgstr "" - -#: ../overview.rst:0 -msgid "**OpenStack services**" -msgstr "" - -#: ../environment.rst:0 -msgid "**Passwords**" -msgstr "" - #: ../app_reserved_uids.rst:0 msgid "**Reserved user IDs**" msgstr "" -#: ../overview.rst:65 -msgid "**Shared services**" -msgstr "" - -#: ../overview.rst:48 -msgid "**Storage**" -msgstr "" - -#: ../app_reserved_uids.rst:93 -msgid "160" -msgstr "" - -#: ../app_reserved_uids.rst:48 -msgid "161" -msgstr "" - -#: ../app_reserved_uids.rst:84 -msgid "162" -msgstr "" - -#: ../app_reserved_uids.rst:66 -msgid "163" -msgstr "" - -#: ../app_reserved_uids.rst:75 -msgid "164" -msgstr "" - -#: ../app_reserved_uids.rst:39 -msgid "165" -msgstr "" - -#: ../app_reserved_uids.rst:30 -msgid "166" -msgstr "" - -#: ../app_reserved_uids.rst:57 -msgid "187" -msgstr "" - -#: ../index-debian.rst:103 -msgid ":ref:`search`" -msgstr "" - -# #-#-#-#-# launch-instance-private.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# launch-instance-public.pot (Installation Guide 0.1) #-#-#-#-# -#: ../launch-instance-private.rst:12 ../launch-instance-public.rst:12 -msgid "" -"A flavor specifies a virtual resource allocation profile which includes " -"processor, memory, and storage." -msgstr "" - -#: ../environment.rst:50 -msgid "" -"A single disk partition on each node works for most basic installations. " -"However, you should consider :term:`Logical Volume Manager (LVM)` for " -"installations with optional services such as Block Storage." -msgstr "" - -#: ../environment.rst:61 -msgid "" -"Ability to take periodic \"snap shots\" throughout the installation process " -"and \"roll back\" to a working configuration in the event of a problem." -msgstr "" - -#: ../index-debian.rst:35 -msgid "Abstract" -msgstr "" - -#: ../dashboard-verify.rst:9 -msgid "Access the dashboard using a web browser at ``http://controller/``." -msgstr "" - -#: ../dashboard-verify.rst:14 -msgid "" -"Access the dashboard using a web browser at ``http://controller/dashboard``." -msgstr "" - -#: ../dashboard-verify.rst:19 -msgid "" -"Access the dashboard using a web browser at ``http://controller/horizon``." -msgstr "" - -# #-#-#-#-# launch-instance-private.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# launch-instance-public.pot (Installation Guide 0.1) #-#-#-#-# -#: ../launch-instance-private.rst:188 ../launch-instance-public.rst:199 -msgid "Access the instance remotely" -msgstr "" - -#: ../launch-instance-private.rst:132 -msgid "Access the instance using a virtual console" -msgstr "" - -#: ../launch-instance-public.rst:143 -msgid "Access the instance using the virtual console" -msgstr "" - -#: ../launch-instance-cinder.rst:93 -msgid "" -"Access your instance using SSH and use the ``fdisk`` command to verify " -"presence of the volume as the ``/dev/vdb`` block storage device:" -msgstr "" - -# #-#-#-#-# launch-instance-private.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# launch-instance-public.pot (Installation Guide 0.1) #-#-#-#-# -#: ../launch-instance-private.rst:247 ../launch-instance-public.rst:217 -msgid "" -"Access your instance using SSH from the controller node or any host on the " -"public physical network:" -msgstr "" - -#: ../swift-initial-rings.rst:16 -msgid "Account ring" -msgstr "" - -#: ../swift.rst:5 -msgid "Add Object Storage" -msgstr "" - -#: ../nova-controller-install.rst:184 -msgid "Add a ``[database]`` section, and configure database access:" -msgstr "" - -#: ../swift-initial-rings.rst:34 ../swift-initial-rings.rst:115 -#: ../swift-initial-rings.rst:194 -msgid "Add each storage node to the ring:" -msgstr "" - -#: ../launch-instance.rst:82 -msgid "Add rules to the ``default`` security group:" -msgstr "" - -#: ../launch-instance.rst:75 -msgid "Add security group rules" -msgstr "" - -#: ../cinder.rst:3 -msgid "Add the Block Storage service" -msgstr "" - -#: ../nova.rst:3 -msgid "Add the Compute service" -msgstr "" - -#: ../keystone.rst:3 -msgid "Add the Identity service" -msgstr "" - -#: ../glance.rst:3 -msgid "Add the Image service" -msgstr "" - -#: ../neutron.rst:5 -msgid "Add the Networking service" -msgstr "" - -#: ../heat.rst:3 -msgid "Add the Orchestration module" -msgstr "" - -#: ../ceilometer.rst:3 -msgid "Add the Telemetry module" -msgstr "" - -#: ../ceilometer-swift.rst:34 -msgid "" -"Add the ``ResellerAdmin`` role to the ``service`` tenant and ``ceilometer`` " -"user:" -msgstr "" - -#: ../keystone-users.rst:68 -msgid "Add the ``admin`` role to the ``admin`` project and user:" -msgstr "" - -#: ../ceilometer-controller-install.rst:248 -msgid "Add the ``admin`` role to the ``ceilometer`` user." -msgstr "" - -#: ../cinder-controller-node.rst:70 -msgid "Add the ``admin`` role to the ``cinder`` user:" -msgstr "" - -#: ../glance-install.rst:69 -msgid "Add the ``admin`` role to the ``glance`` user and ``service`` project:" -msgstr "" - -#: ../heat-install.rst:66 -msgid "Add the ``admin`` role to the ``heat`` user:" -msgstr "" - -#: ../neutron-controller-install.rst:63 -msgid "Add the ``admin`` role to the ``neutron`` user:" -msgstr "" - -#: ../nova-controller-install.rst:66 -msgid "Add the ``admin`` role to the ``nova`` user:" -msgstr "" - -#: ../swift-controller-node.rst:54 -msgid "Add the ``admin`` role to the ``swift`` user:" -msgstr "" - -#: ../heat-install.rst:90 -msgid "Add the ``heat_stack_owner`` role to the ``demo`` tenant and user:" -msgstr "" - -#: ../environment-dependencies.rst:450 -msgid "Add the ``openstack`` user:" -msgstr "" - -#: ../launch-instance-networks-private.rst:143 -msgid "Add the ``router: external`` option to the ``public`` provider network:" -msgstr "" - -#: ../ceilometer-swift.rst:92 -msgid "" -"Add the ``swift`` system user to the ``ceilometer`` system group to permit " -"access to the Telemetry configuration files by the Object Storage service:" -msgstr "" - -#: ../keystone-users.rst:162 -msgid "Add the ``user`` role to the ``demo`` project and user:" -msgstr "" - -#: ../horizon.rst:3 -msgid "Add the dashboard" -msgstr "" - -#: ../launch-instance-networks-private.rst:174 -msgid "Add the private network subnet as an interface on the router:" -msgstr "" - -#: ../environment-networking.rst:162 -msgid "Additional compute nodes should use 10.0.0.32, 10.0.0.33, and so on." -msgstr "" - -#: ../neutron-concepts.rst:43 -msgid "" -"Additionally, you can allocate IP addresses on external networks to ports on " -"the internal network. Whenever something is connected to a subnet, that " -"connection is called a port. You can associate external network IP addresses " -"with ports to VMs. This way, entities on the outside network can access VMs." -msgstr "" - -#: ../ceilometer-nova.rst:146 -msgid "" -"Administrators can also restrict notification delivery to certain tenant " -"groups. Users can view notifications through a web browser, without using a " -"specific interface." -msgstr "" - -#: ../launch-instance-cinder.rst:41 -msgid "" -"After a short time, the volume status should change from ``creating`` to " -"``available``:" -msgstr "" - -#: ../overview.rst:93 -msgid "" -"After becoming familiar with basic installation, configuration, operation, " -"and troubleshooting of these OpenStack services, you should consider the " -"following steps toward deployment using a production architecture:" -msgstr "" - -#: ../launch-instance.rst:35 -msgid "" -"After creating the appropriate networks for your environment, you can " -"continue preparing the environment to launch an instance." -msgstr "" - -#: ../environment-networking.rst:33 -msgid "" -"After installing the operating system on each node for the architecture that " -"you choose to deploy, you must configure the network interfaces. We " -"recommend that you disable any automated network management tools and " -"manually edit the appropriate configuration files for your distribution. For " -"more information on how to configure networking on your distribution, see " -"the `SLES 12 `__ or `openSUSE `__ documentation." -msgstr "" - -#: ../environment-networking.rst:24 -msgid "" -"After installing the operating system on each node for the architecture that " -"you choose to deploy, you must configure the network interfaces. We " -"recommend that you disable any automated network management tools and " -"manually edit the appropriate configuration files for your distribution. For " -"more information on how to configure networking on your distribution, see " -"the `documentation `__ ." -msgstr "" - -#: ../environment-networking.rst:6 -msgid "" -"After installing the operating system on each node for the architecture that " -"you choose to deploy, you must configure the network interfaces. We " -"recommend that you disable any automated network management tools and " -"manually edit the appropriate configuration files for your distribution. For " -"more information on how to configure networking on your distribution, see " -"the `documentation `__ ." -msgstr "" - -#: ../environment-networking.rst:15 -msgid "" -"After installing the operating system on each node for the architecture that " -"you choose to deploy, you must configure the network interfaces. We " -"recommend that you disable any automated network management tools and " -"manually edit the appropriate configuration files for your distribution. For " -"more information on how to configure networking on your distribution, see " -"the `documentation `__ ." -msgstr "" - -# #-#-#-#-# neutron-controller-install-option1.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# neutron-controller-install-option2.pot (Installation Guide 0.1) #-#-#-#-# -#: ../neutron-controller-install-option1.rst:228 -#: ../neutron-controller-install-option2.rst:226 -msgid "" -"After you configure the ML2 plug-in, removing values in the ``type_drivers`` " -"option can lead to database inconsistency." -msgstr "" - -#: ../debconf/debconf-dbconfig-common.rst:70 -msgid "After you create this file, run this command:" -msgstr "" - -#: ../dashboard-next-step.rst:8 -msgid "" -"After you install and configure the dashboard, you can complete the " -"following tasks:" -msgstr "" - -#: ../debconf/debconf-api-endpoints.rst:7 -msgid "" -"All Debian packages for API services, except the ``heat-api`` package, " -"register the service in the Identity service catalog. This feature is " -"helpful because API endpoints are difficult to remember." -msgstr "" - -#: ../environment-networking.rst:40 -msgid "" -"All nodes require Internet access for administrative purposes such as " -"package installation, security updates, :term:`DNS`, and :term:`NTP`. In " -"most cases, nodes should obtain internet access through the management " -"network interface. To highlight the importance of network separation, the " -"example architectures use `private address space `__ for the management network and assume that the physical " -"network infrastructure provides Internet access via :term:`NAT` or other " -"method. The example architectures use routable IP address space for the " -"public network and assume that the physical network infrastructure provides " -"direct Internet access. In the provider networks architecture, all instances " -"attach directly to the public network. In the self-service networks " -"architecture, instances can attach to a private or public network. Private " -"networks can reside entirely within OpenStack or provide some level of " -"public network access using :term:`NAT`." -msgstr "" - -#: ../dashboard-install.rst:99 -msgid "Allow all hosts to access the dashboard::" -msgstr "" - -# #-#-#-#-# cinder-storage-node.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# swift-storage-node.pot (Installation Guide 0.1) #-#-#-#-# -#: ../cinder-storage-node.rst:42 ../swift-storage-node.rst:61 -msgid "" -"Also add this content to the :file:`/etc/hosts` file on all other nodes in " -"your environment." -msgstr "" - -#: ../environment.rst:161 -msgid "" -"Also, the Networking service assumes default values for kernel network " -"parameters and modifies firewall rules. To avoid most issues during your " -"initial installation, we recommend using a stock deployment of a supported " -"distribution on your hosts. However, if you choose to automate deployment of " -"your hosts, review the configuration and policies applied to them before " -"proceeding further." -msgstr "" - -#: ../debconf/debconf-dbconfig-common.rst:140 -msgid "" -"Alternatively, if you do not want to install this package, run this script " -"to enable remote root access:" -msgstr "" - -#: ../launch-instance.rst:60 -msgid "" -"Alternatively, you can skip the ``ssh-keygen`` command and use an existing " -"public key." -msgstr "" - -#: ../environment.rst:17 -msgid "" -"Although most environments include Identity, Image service, Compute, at " -"least one networking service, and the dashboard, the Object Storage service " -"can operate independently. If your use case only involves Object Storage, " -"you can skip to :ref:`swift` after configuring the appropriate nodes for it. " -"However, the dashboard requires at least the Image service and Compute." -msgstr "" - -#: ../debconf/debconf-concepts.rst:44 -msgid "" -"Another way to disable the ``debconf`` package is to prefix the :command:" -"`apt` command with ``DEBIAN_FRONTEND=noninteractive``, as follows:" -msgstr "" - -#: ../neutron-concepts.rst:21 -msgid "" -"Any given Networking set up has at least one external network. Unlike the " -"other networks, the external network is not merely a virtually defined " -"network. Instead, it represents a view into a slice of the physical, " -"external network accessible outside the OpenStack installation. IP addresses " -"on the external network are accessible by anybody physically on the outside " -"network. Because the external network merely represents a view into the " -"outside network, DHCP is disabled on this network." -msgstr "" - -#: ../keystone-users.rst:80 -msgid "" -"Any roles that you create must map to roles specified in the ``policy.json`` " -"file in the configuration file directory of each OpenStack service. The " -"default policy for most services grants administrative access to the " -"``admin`` role. For more information, see the `Operations Guide - Managing " -"Projects and Users `__." -msgstr "" - #: ../app_reserved_uids.rst:3 msgid "Appendix A. Reserved user IDs" msgstr "" -#: ../debconf/debconf-dbconfig-common.rst:98 -msgid "As an example, here are screenshots from the ``cinder-common`` package:" +#: ../app_reserved_uids.rst:5 +msgid "" +"OpenStack reserves certain user IDs to run specific services and own " +"specific files. These user IDs are set up according to the distribution " +"packages. The following table gives an overview." msgstr "" -#: ../keystone-verify.rst:33 -msgid "As the ``admin`` user, request an authentication token:" +#: ../app_reserved_uids.rst:11 +msgid "" +"Some OpenStack packages generate and assign user IDs automatically during " +"package installation. In these cases, the user ID value is not important. " +"The existence of the user ID is what matters." msgstr "" -#: ../keystone-verify.rst:55 -msgid "As the ``demo`` user, request an authentication token:" +#: ../app_reserved_uids.rst:19 +msgid "Name" +msgstr "" + +# #-#-#-#-# app_reserved_uids.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# environment-security.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# overview.pot (Installation Guide 0.1) #-#-#-#-# +#: ../app_reserved_uids.rst:20 ../environment-security.rst:30 +#: ../overview.rst:25 +msgid "Description" +msgstr "" + +#: ../app_reserved_uids.rst:21 +msgid "ID" +msgstr "" + +#: ../app_reserved_uids.rst:22 +msgid "ceilometer" +msgstr "" + +#: ../app_reserved_uids.rst:23 +msgid "OpenStack ceilometer daemons" msgstr "" #: ../app_reserved_uids.rst:26 ../app_reserved_uids.rst:35 @@ -555,1176 +70,130 @@ msgstr "" msgid "Assigned during package installation" msgstr "" -#: ../launch-instance-private.rst:209 -msgid "Associate the floating IP address with the instance:" +#: ../app_reserved_uids.rst:30 +msgid "166" msgstr "" -#: ../launch-instance-cinder.rst:56 -msgid "Attach a volume to an instance:" +#: ../app_reserved_uids.rst:31 +msgid "cinder" msgstr "" -#: ../launch-instance-cinder.rst:67 -msgid "" -"Attach the ``0a816b7c-e578-4290-bb74-c13b8b90d4e7`` volume to the ``public-" -"instance`` instance:" +#: ../app_reserved_uids.rst:32 +msgid "OpenStack cinder daemons" msgstr "" -#: ../launch-instance-cinder.rst:54 -msgid "Attach the volume to an instance" +#: ../app_reserved_uids.rst:39 +msgid "165" msgstr "" -#: ../dashboard-verify.rst:22 -msgid "Authenticate using ``admin`` or ``demo`` user credentials." +#: ../app_reserved_uids.rst:40 +msgid "glance" msgstr "" -#: ../cinder-storage-node.rst:319 -msgid "" -"Back-end names are arbitrary. As an example, this guide uses the name of the " -"driver as the name of the back end." +#: ../app_reserved_uids.rst:41 +msgid "OpenStack glance daemons" msgstr "" -#: ../environment-dependencies.rst:201 -msgid "" -"Because Fedora does not provide the ``openstack-selinux`` package ensure " -"that SELinux is disabled." +#: ../app_reserved_uids.rst:48 +msgid "161" msgstr "" -#: ../debconf/debconf-keystone-authtoken.rst:7 -msgid "" -"Because most OpenStack services must access the Identity service, you must " -"configure the IP address of the ``keystone`` server to be able to access it. " -"You must also configure the ``admin_tenant_name``, ``admin_user``, and " -"``admin_password`` options for each service to work." +#: ../app_reserved_uids.rst:49 +msgid "heat" msgstr "" -# #-#-#-#-# cinder-controller-node.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# glance-install.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# heat-install.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# keystone-install.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# nova-compute-install.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# nova-controller-install.pot (Installation Guide 0.1) #-#-#-#-# -#: ../cinder-controller-node.rst:322 ../glance-install.rst:378 -#: ../heat-install.rst:419 ../keystone-install.rst:505 -#: ../nova-compute-install.rst:266 ../nova-controller-install.rst:400 -msgid "" -"Because this configuration uses an SQL database server, you can remove the " -"SQLite database file:" +#: ../app_reserved_uids.rst:50 +msgid "OpenStack heat daemons" msgstr "" -#: ../launch-instance-networks-public.rst:6 -msgid "" -"Before launching an instance, you must create the necessary virtual network " -"infrastructure. For networking option 1, an instance uses a public provider " -"virtual network that connects to the physical network infrastructure via " -"layer-2 (bridging/switching). This network includes a DHCP server that " -"provides IP addresses to instances." +#: ../app_reserved_uids.rst:57 +msgid "187" msgstr "" -#: ../swift-initial-rings.rst:5 -msgid "" -"Before starting the Object Storage services, you must create the initial " -"account, container, and object rings. The ring builder creates configuration " -"files that each node uses to determine and deploy the storage architecture. " -"For simplicity, this guide uses one region and zone with 2^10 (1024) maximum " -"partitions, 3 replicas of each object, and 1 hour minimum time between " -"moving a partition more than once. For Object Storage, a partition indicates " -"a directory on a storage device rather than a conventional partition table. " -"For more information, see the `Deployment Guide `__." +#: ../app_reserved_uids.rst:58 +msgid "keystone" msgstr "" -#: ../environment.rst:34 -msgid "Before you begin" +#: ../app_reserved_uids.rst:59 +msgid "OpenStack keystone daemons" msgstr "" -#: ../neutron-controller-install-option1.rst:9 -msgid "" -"Before you configure networking option 1, you must configure kernel " -"parameters to disable reverse-path filtering." +#: ../app_reserved_uids.rst:66 +msgid "163" msgstr "" -#: ../neutron-controller-install-option2.rst:9 -msgid "" -"Before you configure networking option 2, you must configure kernel " -"parameters to enable IP forwarding (routing) and disable reverse-path " -"filtering." +#: ../app_reserved_uids.rst:67 +msgid "neutron" msgstr "" -#: ../keystone-install.rst:12 -msgid "" -"Before you configure the OpenStack Identity service, you must create a " -"database and an administration token." +#: ../app_reserved_uids.rst:68 +msgid "OpenStack neutron daemons" msgstr "" -#: ../neutron-controller-install.rst:7 -msgid "" -"Before you configure the OpenStack Networking (neutron) service, you must " -"create a database, service credentials, and API endpoints." +#: ../app_reserved_uids.rst:75 +msgid "164" msgstr "" -#: ../neutron-compute-install.rst:10 -msgid "" -"Before you install and configure OpenStack Networking, you must kernel " -"networking parameters to disable reverse-path filtering:" +#: ../app_reserved_uids.rst:76 +msgid "nova" msgstr "" -#: ../heat-install.rst:13 -msgid "" -"Before you install and configure Orchestration, you must create a database, " -"service credentials, and API endpoints." +#: ../app_reserved_uids.rst:77 +msgid "OpenStack nova daemons" msgstr "" -#: ../ceilometer-controller-install.rst:13 -msgid "" -"Before you install and configure Telemetry, you must install ``MongoDB``, " -"create a MongoDB database, service credentials, and API endpoint." +#: ../app_reserved_uids.rst:84 +msgid "162" msgstr "" -#: ../cinder-controller-node.rst:13 -msgid "" -"Before you install and configure the Block Storage service, you must create " -"a database, service credentials, and API endpoint." +#: ../app_reserved_uids.rst:85 +msgid "swift" msgstr "" -#: ../nova-controller-install.rst:10 -msgid "" -"Before you install and configure the Compute service, you must create a " -"database, service credentials, and API endpoints." +#: ../app_reserved_uids.rst:86 +msgid "OpenStack swift daemons" msgstr "" -#: ../glance-install.rst:13 -msgid "" -"Before you install and configure the Image service, you must create a " -"database, service credentials, and API endpoints." +#: ../app_reserved_uids.rst:93 +msgid "160" msgstr "" -#: ../glance.rst:26 -msgid "" -"Before you proceed, ensure that the controller node has at least several " -"gigabytes of space available in this directory." +#: ../app_reserved_uids.rst:94 +msgid "trove" msgstr "" -# #-#-#-#-# launch-instance-cinder.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# launch-instance.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# overview.pot (Installation Guide 0.1) #-#-#-#-# -#: ../launch-instance-cinder.rst:4 ../launch-instance.rst:122 -#: ../overview.rst:163 -msgid "Block Storage" -msgstr "" - -#: ../debconf/debconf-dbconfig-common.rst:124 -msgid "" -"By default in Debian, you can access the MySQL server from either localhost " -"through the socket file or 127.0.0.1. To access it over the network, you " -"must edit the :file:`/etc/mysql/my.cnf` file, and the ``mysql.user`` table. " -"To do so, Debian provides a helper script in the ``openstack-deploy`` " -"package. To use it, install the package:" -msgstr "" - -# #-#-#-#-# nova-compute-install.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# nova-controller-install.pot (Installation Guide 0.1) #-#-#-#-# -#: ../nova-compute-install.rst:128 ../nova-controller-install.rst:263 -msgid "" -"By default, Compute uses an internal firewall service. Since Networking " -"includes a firewall service, you must disable the Compute firewall service " -"by using the ``nova.virt.firewall.NoopFirewallDriver`` firewall driver." -msgstr "" - -#: ../ceilometer-controller-install.rst:81 -#: ../ceilometer-controller-install.rst:118 -#: ../ceilometer-controller-install.rst:153 -msgid "" -"By default, MongoDB creates several 1 GB journal files in the :file:`/var/" -"lib/mongodb/journal` directory. If you want to reduce the size of each " -"journal file to 128 MB and limit total journal space consumption to 512 MB, " -"assert the ``smallfiles`` key:" -msgstr "" - -#: ../dashboard-install.rst:120 -msgid "" -"By default, SLES and openSUSE use an SQL database for session storage. For " -"simplicity, we recommend changing the configuration to use ``memcached`` for " -"session storage." -msgstr "" - -#: ../debconf/debconf-dbconfig-common.rst:27 -msgid "" -"By default, ``dbconfig-common`` does not provide access to database servers " -"over a network. If you want the ``dbconfig-common`` package to prompt for " -"remote database servers that are accessed over a network and not through a " -"UNIX socket file, reconfigure it, as follows:" -msgstr "" - -#: ../keystone-services.rst:14 -msgid "" -"By default, the Identity service database contains no information to support " -"conventional authentication and catalog services. You must use a temporary " -"authentication token that you created in the section called :doc:`keystone-" -"install` to initialize the service entity and API endpoint for the Identity " -"service." -msgstr "" - -# #-#-#-#-# cinder-controller-node.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# glance-install.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# heat-install.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# keystone-install.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# nova-compute-install.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# nova-controller-install.pot (Installation Guide 0.1) #-#-#-#-# -#: ../cinder-controller-node.rst:320 ../glance-install.rst:376 -#: ../heat-install.rst:417 ../keystone-install.rst:503 -#: ../nova-compute-install.rst:264 ../nova-controller-install.rst:398 -msgid "By default, the Ubuntu packages create an SQLite database." -msgstr "" - -#: ../cinder-storage-node.rst:380 -msgid "" -"By default, the Ubuntu packages create an SQLite database. Because this " -"configuration uses an SQL database server, remove the SQLite database file:" -msgstr "" - -#: ../debconf/debconf-dbconfig-common.rst:22 -msgid "" -"By default, the ``dbconfig-common`` package configures the OpenStack " -"services to use SQLite. So if you use debconf in non-interactive mode and " -"without pre-seeding, the OpenStack services that you install will use SQLite." -msgstr "" - -#: ../launch-instance.rst:77 -msgid "" -"By default, the ``default`` security group applies to all instances and " -"includes firewall rules that deny remote access to instances. For Linux " -"images such as CirrOS, we recommend allowing at least ICMP (ping) and secure " -"shell (SSH)." -msgstr "" - -#: ../environment-ntp-controller.rst:44 -msgid "" -"By default, the controller node synchronizes the time via a pool of public " -"servers. However, you can optionally configure alternative servers such as " -"those provided by your organization." -msgstr "" - -#: ../environment-dependencies.rst:60 -msgid "CentOS and Fedora do not require these repositories." -msgstr "" - -#: ../environment-dependencies.rst:218 -msgid "CentOS and RHEL do not require this step." -msgstr "" - -#: ../swift-initial-rings.rst:22 ../swift-initial-rings.rst:103 -#: ../swift-initial-rings.rst:182 -msgid "Change to the :file:`/etc/swift` directory." -msgstr "" - -#: ../launch-instance-private.rst:219 -msgid "Check the status of your floating IP address:" -msgstr "" - -# #-#-#-#-# launch-instance-private.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# launch-instance-public.pot (Installation Guide 0.1) #-#-#-#-# -#: ../launch-instance-private.rst:116 ../launch-instance-public.rst:128 -msgid "Check the status of your instance:" -msgstr "" - -#: ../environment-dependencies.rst:295 -msgid "Choose a suitable password for the database root account." -msgstr "" - -#: ../neutron-controller-install.rst:117 -msgid "" -"Choose one of the following networking options to configure services " -"specific to it." -msgstr "" - -#: ../overview.rst:192 -msgid "Choose one of the following virtual networking options." -msgstr "" - -#: ../neutron-compute-install.rst:145 -msgid "" -"Choose the same networking option that you chose for the controller node to " -"configure services specific to it." -msgstr "" - -# #-#-#-#-# ceilometer-controller-install.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# ceilometer-nova.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# heat-install.pot (Installation Guide 0.1) #-#-#-#-# -#: ../ceilometer-controller-install.rst:402 ../ceilometer-nova.rst:88 -#: ../heat-install.rst:298 -msgid "" -"Comment out any ``auth_host``, ``auth_port``, and ``auth_protocol`` options " -"because the ``identity_uri`` option replaces them." -msgstr "" - -#: ../dashboard-install.rst:114 -msgid "Comment out any other session storage configuration." -msgstr "" - -#: ../swift-controller-node-include.txt:71 -msgid "" -"Comment out or remove any other options in the ``[filter:authtoken]`` " -"section." -msgstr "" - -# #-#-#-#-# cinder-controller-node.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# cinder-storage-node.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# glance-install.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# neutron-compute-install.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# neutron-controller-install-option1.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# neutron-controller-install-option2.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# nova-compute-install.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# nova-controller-install.pot (Installation Guide 0.1) #-#-#-#-# -#: ../cinder-controller-node.rst:262 ../cinder-storage-node.rst:263 -#: ../glance-install.rst:223 ../glance-install.rst:297 -#: ../neutron-compute-install.rst:130 -#: ../neutron-controller-install-option1.rst:157 -#: ../neutron-controller-install-option2.rst:154 -#: ../nova-compute-install.rst:99 ../nova-controller-install.rst:238 -msgid "" -"Comment out or remove any other options in the ``[keystone_authtoken]`` " -"section." -msgstr "" - -#: ../swift-controller-node.rst:114 -msgid "Complete OpenStack environments already include some of these packages." -msgstr "" - -#: ../overview.rst:150 -msgid "Compute" -msgstr "" - -#: ../environment.rst:44 -msgid "Compute Node: 1 processor, 2 GB memory, and 10 GB storage" -msgstr "" - -#: ../environment-networking.rst:147 -msgid "Compute node" -msgstr "" - -# #-#-#-#-# neutron-compute-install.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# neutron-controller-install.pot (Installation Guide 0.1) #-#-#-#-# -#: ../neutron-compute-install.rst:163 ../neutron-controller-install.rst:190 -msgid "Configure Compute to use Networking" -msgstr "" - -#: ../environment-ntp.rst:7 -msgid "Configure Network Time Protocol (NTP)" -msgstr "" - -#: ../debconf/debconf.rst:5 -msgid "Configure OpenStack with debconf" -msgstr "" - -#: ../dashboard-install.rst:124 -msgid "" -"Configure ``user`` as the default role for users that you create via the " -"dashboard::" -msgstr "" - -#: ../environment-networking.rst:122 ../environment-networking.rst:212 -msgid "Configure name resolution" -msgstr "" - -#: ../environment-networking.rst:107 ../environment-networking.rst:150 -msgid "Configure networking" -msgstr "" - -# #-#-#-#-# neutron-compute-install.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# neutron-controller-install.pot (Installation Guide 0.1) #-#-#-#-# -#: ../neutron-compute-install.rst:143 ../neutron-controller-install.rst:115 -msgid "Configure networking options" -msgstr "" - -#: ../swift-storage-node.rst:47 -msgid "Configure shared items on both storage nodes:" -msgstr "" - -#: ../keystone-install.rst:289 -msgid "Configure the Apache HTTP server" -msgstr "" - -#: ../ceilometer-cinder.rst:3 -msgid "Configure the Block Storage service" -msgstr "" - -#: ../ceilometer-nova.rst:3 -msgid "Configure the Compute service" -msgstr "" - -#: ../ceilometer-nova.rst:123 -msgid "Configure the Compute service to send notifications to the message bus." -msgstr "" - -# #-#-#-#-# neutron-controller-install-option1.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# neutron-controller-install-option2.pot (Installation Guide 0.1) #-#-#-#-# -#: ../neutron-controller-install-option1.rst:296 -#: ../neutron-controller-install-option2.rst:347 -msgid "Configure the DHCP agent" -msgstr "" - -#: ../keystone-services.rst:68 -msgid "Configure the Identity API version:" -msgstr "" - -#: ../ceilometer-glance.rst:3 -msgid "Configure the Image service" -msgstr "" - -# #-#-#-#-# neutron-compute-install-option1.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# neutron-compute-install-option2.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# neutron-controller-install-option1.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# neutron-controller-install-option2.pot (Installation Guide 0.1) #-#-#-#-# -#: ../neutron-compute-install-option1.rst:7 -#: ../neutron-compute-install-option2.rst:7 -#: ../neutron-controller-install-option1.rst:249 -#: ../neutron-controller-install-option2.rst:260 -msgid "Configure the Linux bridge agent" -msgstr "" - -# #-#-#-#-# neutron-controller-install-option1.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# neutron-controller-install-option2.pot (Installation Guide 0.1) #-#-#-#-# -#: ../neutron-controller-install-option1.rst:195 -#: ../neutron-controller-install-option2.rst:192 -msgid "Configure the Modular Layer 2 (ML2) plug-in" -msgstr "" - -# #-#-#-#-# environment-ntp-controller.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# environment-ntp-other.pot (Installation Guide 0.1) #-#-#-#-# -#: ../environment-ntp-controller.rst:42 ../environment-ntp-other.rst:42 -msgid "Configure the NTP service" -msgstr "" - -# #-#-#-#-# neutron-controller-install-option1.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# neutron-controller-install-option2.pot (Installation Guide 0.1) #-#-#-#-# -#: ../neutron-controller-install-option1.rst:83 -#: ../neutron-controller-install-option2.rst:85 -msgid "Configure the Networking server component" -msgstr "" - -#: ../ceilometer-swift.rst:3 -msgid "Configure the Object Storage service" -msgstr "" - -#: ../ceilometer-controller-install.rst:73 -#: ../ceilometer-controller-install.rst:110 -#: ../ceilometer-controller-install.rst:145 -msgid "" -"Configure the ``bind_ip`` key to use the management interface IP address of " -"the controller node." -msgstr "" - -#: ../dashboard-install.rst:103 -msgid "Configure the ``memcached`` session storage service::" -msgstr "" - -#: ../keystone-services.rst:39 -msgid "Configure the authentication token:" -msgstr "" - -#: ../dashboard-install.rst:94 -msgid "" -"Configure the dashboard to use OpenStack services on the ``controller`` " -"node::" -msgstr "" - -#: ../debconf/debconf-dbconfig-common.rst:5 -msgid "Configure the database with dbconfig-common" -msgstr "" - -#: ../keystone-services.rst:55 -msgid "Configure the endpoint URL:" -msgstr "" - -#: ../environment-networking.rst:109 ../environment-networking.rst:152 -msgid "Configure the first interface as the management interface:" -msgstr "" - -#: ../keystone-install.rst:222 -msgid "Configure the initial administration token:" -msgstr "" - -#: ../neutron-controller-install-option2.rst:315 -msgid "Configure the layer-3 agent" -msgstr "" - -# #-#-#-#-# cinder-storage-node.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# swift-storage-node.pot (Installation Guide 0.1) #-#-#-#-# -#: ../cinder-storage-node.rst:26 ../swift-storage-node.rst:29 -#: ../swift-storage-node.rst:39 -msgid "Configure the management interface:" -msgstr "" - -#: ../environment-dependencies.rst:438 -msgid "Configure the message queue service" -msgstr "" - -#: ../neutron-controller-install.rst:135 -msgid "Configure the metadata agent" -msgstr "" - -#: ../environment-ntp-other.rst:44 -msgid "" -"Configure the network and compute nodes to reference the controller node." -msgstr "" - -#: ../dashboard-install.rst:71 -msgid "Configure the web server::" -msgstr "" - -#: ../swift-storage-node.rst:27 -msgid "Configure unique items on the first storage node:" -msgstr "" - -#: ../swift-storage-node.rst:37 -msgid "Configure unique items on the second storage node:" -msgstr "" - -#: ../glance-verify.rst:84 -msgid "Confirm upload of the image and validate attributes:" -msgstr "" - -#: ../swift-initial-rings.rst:96 -msgid "Container ring" -msgstr "" - -#: ../index-debian.rst:76 -msgid "Contents" -msgstr "" - -#: ../environment-ntp-verify.rst:21 -msgid "" -"Contents in the *Name/IP address* column should indicate the hostname or IP " -"address of one or more NTP servers. Contents in the *S* column should " -"indicate *\\** for the server to which the NTP service is currently " -"synchronized." -msgstr "" - -#: ../environment-ntp-verify.rst:35 -msgid "" -"Contents in the *remote* column should indicate the hostname of the " -"controller node." -msgstr "" - -#: ../overview.rst:137 -msgid "Controller" -msgstr "" - -#: ../environment.rst:42 -msgid "Controller Node: 1 processor, 2 GB memory, and 5 GB storage" -msgstr "" - -# #-#-#-#-# environment-networking.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# environment-ntp-controller.pot (Installation Guide 0.1) #-#-#-#-# -#: ../environment-networking.rst:104 ../environment-ntp-controller.rst:4 -msgid "Controller node" -msgstr "" - -#: ../cinder-controller-node.rst:195 -msgid "" -"Copy the :file:`/usr/share/cinder/cinder-dist.conf` file to :file:`/etc/" -"cinder/cinder.conf`." -msgstr "" - -#: ../heat-install.rst:233 -msgid "" -"Copy the :file:`/usr/share/heat/heat-dist.conf` file to :file:`/etc/heat/" -"heat.conf`." -msgstr "" - -#: ../swift-initial-rings.rst:255 -msgid "" -"Copy the :file:`account.ring.gz`, :file:`container.ring.gz`, and :file:" -"`object.ring.gz` files to the :file:`/etc/swift` directory on each storage " -"node and any additional nodes running the proxy service." -msgstr "" - -#: ../swift-finalize-installation.rst:50 ../swift-finalize-installation.rst:86 -msgid "" -"Copy the :file:`swift.conf` file to the :file:`/etc/swift` directory on each " -"storage node and any additional nodes running the proxy service." -msgstr "" - -#: ../swift-storage-node.rst:49 -msgid "" -"Copy the contents of the :file:`/etc/hosts` file from the controller node " -"and add the following to it:" -msgstr "" - -#: ../cinder-storage-node.rst:36 -msgid "" -"Copy the contents of the :file:`/etc/hosts` file from the controller node to " -"the storage node and add the following to it::" -msgstr "" - -#: ../keystone-openrc.rst:2 -msgid "Create OpenStack client environment scripts" -msgstr "" - -#: ../launch-instance-cinder.rst:16 -msgid "Create a 1 GB volume:" -msgstr "" - -#: ../launch-instance-private.rst:190 -msgid "" -"Create a :term:`floating IP address` on the ``public`` provider network:" -msgstr "" - -#: ../cinder-controller-node.rst:53 -msgid "Create a ``cinder`` user:" -msgstr "" - -#: ../launch-instance-networks-private.rst:124 -msgid "Create a router" -msgstr "" - -# #-#-#-#-# launch-instance-networks-private.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# launch-instance-networks-public.pot (Installation Guide 0.1) #-#-#-#-# -#: ../launch-instance-networks-private.rst:82 -#: ../launch-instance-networks-public.rst:86 -msgid "Create a subnet on the network:" -msgstr "" - -#: ../heat-verify.rst:20 -msgid "" -"Create a test template in the :file:`test-stack.yml` file with the following " -"content:" -msgstr "" - -#: ../launch-instance-cinder.rst:7 -msgid "Create a volume" -msgstr "" - -#: ../keystone-users.rst:13 -msgid "" -"Create an administrative project, user, and role for administrative " -"operations in your environment:" -msgstr "" - -#: ../environment-dependencies.rst:327 -msgid "" -"Create and edit the :file:`/etc/my.cnf.d/mariadb_openstack.cnf` file and " -"complete the following actions:" -msgstr "" - -#: ../environment-dependencies.rst:297 -msgid "" -"Create and edit the :file:`/etc/mysql/conf.d/mysqld_openstack.cnf` file and " -"complete the following actions:" -msgstr "" - -#: ../neutron-controller-install-option2.rst:402 -msgid "" -"Create and edit the :file:`/etc/neutron/dnsmasq-neutron.conf` file to enable " -"the DHCP MTU option (26) and configure it to 1450 bytes:" -msgstr "" - -#: ../keystone-openrc.rst:16 -msgid "" -"Create client environment scripts for the ``admin`` and ``demo`` projects " -"and users. Future portions of this guide reference these scripts to load " -"appropriate credentials for client operations." -msgstr "" - -#: ../swift-initial-rings.rst:3 -msgid "Create initial rings" -msgstr "" - -#: ../keystone-users.rst:2 -msgid "Create projects, users, and roles" -msgstr "" - -#: ../swift-controller-node.rst:140 -msgid "Create the :file:`/etc/swift` directory." -msgstr "" - -#: ../swift-storage-node.rst:238 ../swift-storage-node.rst:256 -msgid "Create the :file:`recon` directory and ensure proper ownership of it:" -msgstr "" - -#: ../cinder-controller-node.rst:118 -msgid "Create the Block Storage service API endpoints:" -msgstr "" - -#: ../nova-controller-install.rst:92 -msgid "Create the Compute service API endpoints:" -msgstr "" - -#: ../keystone-services.rst:120 -msgid "Create the Identity service API endpoints:" -msgstr "" - -#: ../glance-install.rst:96 -msgid "Create the Image service API endpoints:" -msgstr "" - -#: ../cinder-storage-node.rst:110 -msgid "Create the LVM physical volume :file:`/dev/sdb1`:" -msgstr "" - -#: ../cinder-storage-node.rst:122 -msgid "Create the LVM volume group ``cinder-volumes``:" -msgstr "" - -#: ../neutron-controller-install.rst:91 -msgid "Create the Networking service API endpoints:" -msgstr "" - -#: ../swift-controller-node.rst:82 -msgid "Create the Object Storage service API endpoint:" -msgstr "" - -#: ../heat-install.rst:154 -msgid "Create the Orchestration service API endpoints:" -msgstr "" - -#: ../ceilometer-controller-install.rst:276 -msgid "Create the Telemetry module API endpoint:" -msgstr "" - -#: ../keystone-install.rst:432 -msgid "" -"Create the ``/etc/apache2/conf.d/wsgi-keystone.conf`` file with the " -"following content:" -msgstr "" - -#: ../keystone-install.rst:363 -msgid "" -"Create the ``/etc/apache2/sites-available/wsgi-keystone.conf`` file with the " -"following content:" -msgstr "" - -#: ../keystone-install.rst:300 -msgid "" -"Create the ``/etc/httpd/conf.d/wsgi-keystone.conf`` file with the following " -"content:" -msgstr "" - -#: ../ceilometer-swift.rst:22 -msgid "Create the ``ResellerAdmin`` role:" -msgstr "" - -#: ../keystone-users.rst:16 -msgid "Create the ``admin`` project:" -msgstr "" - -#: ../keystone-users.rst:56 -msgid "Create the ``admin`` role:" -msgstr "" - -#: ../keystone-install.rst:240 -msgid "Create the ``admin`` tenant and user:" -msgstr "" - -#: ../keystone-users.rst:39 -msgid "Create the ``admin`` user:" -msgstr "" - -#: ../ceilometer-controller-install.rst:178 -#: ../ceilometer-controller-install.rst:205 -msgid "Create the ``ceilometer`` database:" -msgstr "" - -#: ../ceilometer-controller-install.rst:260 -msgid "Create the ``ceilometer`` service entity:" -msgstr "" - -#: ../ceilometer-controller-install.rst:231 -msgid "Create the ``ceilometer`` user:" -msgstr "" - -#: ../cinder-controller-node.rst:25 -msgid "Create the ``cinder`` database:" -msgstr "" - -#: ../cinder-controller-node.rst:82 -msgid "Create the ``cinder`` service entities:" -msgstr "" - -#: ../keystone-users.rst:110 -msgid "Create the ``demo`` project:" -msgstr "" - -#: ../keystone-users.rst:133 -msgid "Create the ``demo`` user:" -msgstr "" - -#: ../glance-install.rst:25 -msgid "Create the ``glance`` database:" -msgstr "" - -#: ../glance-install.rst:80 -msgid "Create the ``glance`` service entity:" -msgstr "" - -#: ../glance-install.rst:53 -msgid "Create the ``glance`` user:" -msgstr "" - -#: ../heat-install.rst:78 -msgid "Create the ``heat_stack_owner`` role:" -msgstr "" - -#: ../heat-install.rst:107 -msgid "Create the ``heat_stack_user`` role:" -msgstr "" - -#: ../heat-install.rst:127 -msgid "Create the ``heat`` and ``heat-cfn`` service entities:" -msgstr "" - -#: ../heat-install.rst:25 -msgid "Create the ``heat`` database::" -msgstr "" - -#: ../heat-install.rst:49 -msgid "Create the ``heat`` user:" -msgstr "" - -#: ../keystone-install.rst:24 -msgid "Create the ``keystone`` database:" -msgstr "" - -#: ../neutron-controller-install.rst:19 -msgid "Create the ``neutron`` database:" -msgstr "" - -#: ../neutron-controller-install.rst:75 -msgid "Create the ``neutron`` service entity:" -msgstr "" - -#: ../neutron-controller-install.rst:46 -msgid "Create the ``neutron`` user:" -msgstr "" - -#: ../nova-controller-install.rst:22 -msgid "Create the ``nova`` database:" -msgstr "" - -#: ../nova-controller-install.rst:76 -msgid "Create the ``nova`` service entity:" -msgstr "" - -#: ../nova-controller-install.rst:50 -msgid "Create the ``nova`` user:" -msgstr "" - -#: ../swift-controller-node.rst:66 -msgid "Create the ``swift`` service entity:" -msgstr "" - -#: ../swift-controller-node.rst:37 -msgid "Create the ``swift`` user:" -msgstr "" - -#: ../keystone-users.rst:150 -msgid "Create the ``user`` role:" -msgstr "" - -#: ../swift-initial-rings.rst:24 -msgid "Create the base :file:`account.builder` file:" -msgstr "" - -#: ../swift-initial-rings.rst:105 -msgid "Create the base :file:`container.builder` file:" -msgstr "" - -#: ../swift-initial-rings.rst:184 -msgid "Create the base :file:`object.builder` file:" -msgstr "" - -#: ../heat-install.rst:347 -msgid "Create the heat domain in Identity service:" -msgstr "" - -#: ../swift-storage-node.rst:94 -msgid "Create the mount point directory structure:" -msgstr "" - -# #-#-#-#-# launch-instance-networks-private.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# launch-instance-networks-public.pot (Installation Guide 0.1) #-#-#-#-# -#: ../launch-instance-networks-private.rst:47 -#: ../launch-instance-networks-public.rst:40 -msgid "Create the network:" -msgstr "" - -#: ../launch-instance-networks-private.rst:38 -msgid "Create the private project network" -msgstr "" - -#: ../launch-instance-networks-public.rst:31 -msgid "Create the public network" -msgstr "" - -#: ../launch-instance-networks-private.rst:156 -msgid "Create the router:" -msgstr "" - -#: ../keystone-services.rst:2 ../keystone-services.rst:75 -msgid "Create the service entity and API endpoints" -msgstr "" - -#: ../keystone-services.rst:81 -msgid "Create the service entity for the Identity service:" -msgstr "" - -#: ../launch-instance.rst:22 -msgid "Create virtual networks" -msgstr "" - -#: ../launch-instance.rst:24 -msgid "" -"Create virtual networks for the networking option that you chose in :ref:" -"`networking`. If you chose option 1, create only the public virtual network. " -"If you chose option 2, create the public and private virtual networks." -msgstr "" - -#: ../keystone-openrc.rst:14 -msgid "Creating the scripts" -msgstr "" - -#: ../dashboard-next-step.rst:16 -msgid "" -"Customize your dashboard. See section `Customize the dashboard `__." -msgstr "" - -#: ../environment.rst:109 -msgid "Database password (no variable used)" -msgstr "" - -#: ../environment.rst:142 -msgid "Database password for Compute service" -msgstr "" - -#: ../environment.rst:126 -msgid "Database password for Image service" -msgstr "" - -#: ../environment.rst:118 -msgid "Database password for the Block Storage service" -msgstr "" - -#: ../environment.rst:138 -msgid "Database password for the Networking service" -msgstr "" - -#: ../environment.rst:130 -msgid "Database password for the Orchestration service" -msgstr "" - -#: ../environment.rst:114 -msgid "Database password for the Telemetry service" -msgstr "" - -#: ../environment.rst:122 -msgid "Database password for the dashboard" -msgstr "" - -#: ../environment.rst:136 -msgid "Database password of Identity service" -msgstr "" - -#: ../neutron-controller-install.rst:274 ../neutron-controller-install.rst:369 -msgid "" -"Database population occurs later for Networking because the script requires " -"complete server and plug-in configuration files." -msgstr "" - -# #-#-#-#-# glance-install.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# keystone-install.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# neutron-compute-install.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# neutron-controller-install-option1.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# nova-compute-install.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# nova-controller-install.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# swift-controller-node.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# swift-finalize-installation.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# swift-storage-node.pot (Installation Guide 0.1) #-#-#-#-# -#: ../shared/note_configuration_vary_by_distribution.rst:3 -msgid "" -"Default configuration files vary by distribution. You might need to add " -"these sections and options rather than modifying existing sections and " -"options. Also, an ellipsis (``...``) in the configuration snippets indicates " -"potential default configuration options that you should retain." -msgstr "" - -# #-#-#-#-# cinder-storage-node.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# environment-networking.pot (Installation Guide 0.1) #-#-#-#-# -#: ../cinder-storage-node.rst:32 ../environment-networking.rst:115 -#: ../environment-networking.rst:158 -msgid "Default gateway: 10.0.0.1" -msgstr "" - -#: ../swift-storage-node.rst:33 ../swift-storage-node.rst:43 -msgid "Default gateway: ``10.0.0.1``" -msgstr "" - -# #-#-#-#-# app_reserved_uids.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# environment.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# overview.pot (Installation Guide 0.1) #-#-#-#-# -#: ../app_reserved_uids.rst:20 ../environment.rst:108 ../overview.rst:25 -msgid "Description" -msgstr "" - -#: ../overview.rst:97 -msgid "" -"Determine and implement the necessary core and optional services to meet " -"performance and redundancy requirements." -msgstr "" - -# #-#-#-#-# launch-instance-private.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# launch-instance-public.pot (Installation Guide 0.1) #-#-#-#-# -#: ../launch-instance-private.rst:7 ../launch-instance-public.rst:7 -msgid "Determine instance options" -msgstr "" - -#: ../nova-compute-install.rst:209 -msgid "" -"Determine whether your compute node supports hardware acceleration for " -"virtual machines:" -msgstr "" - -#: ../environment-dependencies.rst:17 -msgid "" -"Disable or remove any automatic update services because they can impact your " -"OpenStack environment." -msgstr "" - -#: ../keystone-install.rst:68 -msgid "" -"Disable the keystone service from starting automatically after installation:" -msgstr "" - -#: ../swift-initial-rings.rst:253 -msgid "Distribute ring configuration files" -msgstr "" - -#: ../environment-dependencies.rst:11 -msgid "" -"Distributions release OpenStack packages as part of the distribution or " -"using other methods because of differing release schedules. Perform these " -"procedures on all nodes." -msgstr "" - -#: ../environment-networking.rst:188 -msgid "Do not change the ``HWADDR`` and ``UUID`` keys." -msgstr "" - -#: ../keystone-users.rst:130 -msgid "" -"Do not repeat this step when creating additional users for this project." -msgstr "" - -#: ../swift-verify.rst:51 -msgid "Download a test file:" -msgstr "" - -#: ../ceilometer-verify.rst:32 -msgid "Download an image from the Image service:" -msgstr "" - -#: ../glance-verify.rst:30 -msgid "Download the source image:" -msgstr "" - -#: ../dashboard-install.rst:149 -msgid "" -"Due to a packaging bug, the dashboard CSS fails to load properly. Run the " -"following command to resolve this issue::" -msgstr "" - -# #-#-#-#-# neutron-compute-install.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# neutron-controller-install.pot (Installation Guide 0.1) #-#-#-#-# -#: ../neutron-compute-install.rst:215 ../neutron-controller-install.rst:248 -msgid "" -"Due to a packaging issue, the Linux bridge agent initialization script " -"explicitly looks for the Linux bridge plug-in configuration file rather than " -"the agent configuration file. Run the following commands to resolve this " -"issue:" -msgstr "" - -# #-#-#-#-# neutron-compute-install.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# neutron-controller-install.pot (Installation Guide 0.1) #-#-#-#-# -#: ../neutron-compute-install.rst:279 ../neutron-controller-install.rst:348 -msgid "" -"Due to a packaging issue, the Linux bridge agent initialization script " -"explicitly looks for the ML2 plug-in configuration file rather than the " -"agent configuration file. Run the following commands to resolve this issue:" -msgstr "" - -#: ../keystone-install.rst:242 -msgid "" -"During the final stage of the package installation, it is possible to " -"automatically create an admin tenant and an admin user. This can later be " -"used for other OpenStack services to contact the Identity service. This is " -"the equivalent of running the below commands:" -msgstr "" - -#: ../cinder-storage-node.rst:149 -msgid "" -"Each item in the filter array begins with ``a`` for **accept** or ``r`` for " -"**reject** and includes a regular expression for the device name. The array " -"must end with ``r/.*/`` to reject any remaining devices. You can use the :" -"command:`vgs -vvvv` command to test filters." -msgstr "" - -#: ../neutron-concepts.rst:55 -msgid "" -"Each plug-in that Networking uses has its own concepts. While not vital to " -"operating the VNI and OpenStack environment, understanding these concepts " -"can help you set up Networking. All Networking installations use a core plug-" -"in and a security group plug-in (or just the No-Op security group plug-in). " -"Additionally, Firewall-as-a-Service (FWaaS) and Load-Balancer-as-a-Service " -"(LBaaS) plug-ins are available." -msgstr "" - -#: ../neutron-concepts.rst:17 -msgid "" -"Each router has one gateway that connects to a network, and many interfaces " -"connected to subnets. Subnets can access machines on other subnets connected " -"to the same router." -msgstr "" - -#: ../keystone-services.rst:174 -msgid "" -"Each service that you add to your OpenStack environment requires one or more " -"service entities and three API endpoint variants in the Identity service." +#: ../app_reserved_uids.rst:95 +msgid "OpenStack trove daemons" msgstr "" #: ../app_reserved_uids.rst:98 msgid "Each user belongs to a user group with the same name as the user." msgstr "" +#: ../ceilometer-cinder.rst:3 +msgid "Configure the Block Storage service" +msgstr "" + +#: ../ceilometer-cinder.rst:5 +msgid "" +"To retrieve volume-oriented events and samples, you must configure the Block " +"Storage service to send notifications to the message bus. Perform these " +"steps on the controller and storage nodes." +msgstr "" + +# #-#-#-#-# ceilometer-cinder.pot (Installation Guide 0.1) #-#-#-#-# # #-#-#-#-# ceilometer-controller-install.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# ceilometer-nova.pot (Installation Guide 0.1) #-#-#-#-# -#: ../ceilometer-controller-install.rst:343 ../ceilometer-nova.rst:35 -msgid "" -"Edit the :file:`/etc/ceilometer/ceilometer.conf` file and complete the " -"following actions:" -msgstr "" - -#: ../environment-ntp-other.rst:64 -msgid "" -"Edit the :file:`/etc/chrony.conf` and comment out or remove all but one " -"``server`` key. Change it to reference the controller node:" -msgstr "" - -#: ../environment-ntp-controller.rst:69 -msgid "" -"Edit the :file:`/etc/chrony.conf` file and add, change, or remove the " -"following keys as necessary for your environment:" -msgstr "" - -#: ../environment-ntp-other.rst:49 -msgid "" -"Edit the :file:`/etc/chrony/chrony.conf` and comment out or remove all but " -"one ``server`` key. Change it to reference the controller node:" -msgstr "" - -#: ../environment-ntp-controller.rst:50 -msgid "" -"Edit the :file:`/etc/chrony/chrony.conf` file and add, change, or remove the " -"following keys as necessary for your environment:" +# #-#-#-#-# ceilometer-swift.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# cinder-controller-node.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# cinder-storage-node.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# heat-install.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# swift-controller-node.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# swift-storage-node.pot (Installation Guide 0.1) #-#-#-#-# +#: ../ceilometer-cinder.rst:10 ../ceilometer-controller-install.rst:11 +#: ../ceilometer-swift.rst:9 ../cinder-controller-node.rst:11 +#: ../cinder-storage-node.rst:17 ../heat-install.rst:11 +#: ../swift-controller-node.rst:15 ../swift-storage-node.rst:18 +msgid "To configure prerequisites" msgstr "" # #-#-#-#-# ceilometer-cinder.pot (Installation Guide 0.1) #-#-#-#-# @@ -1737,1433 +206,24 @@ msgid "" "actions:" msgstr "" -#: ../swift-storage-node.rst:155 -msgid "" -"Edit the :file:`/etc/default/rsync` file and enable the ``rsync`` service:" -msgstr "" - -#: ../swift-storage-node.rst:101 -msgid "Edit the :file:`/etc/fstab` file and add the following to it:" -msgstr "" - -#: ../ceilometer-glance.rst:9 -msgid "" -"Edit the :file:`/etc/glance/glance-api.conf` and :file:`/etc/glance/glance-" -"registry.conf` files and complete the following actions:" -msgstr "" - -#: ../heat-install.rst:241 ../heat-install.rst:378 -msgid "" -"Edit the :file:`/etc/heat/heat.conf` file and complete the following actions:" -msgstr "" - -#: ../environment-networking.rst:126 ../environment-networking.rst:216 -msgid "Edit the :file:`/etc/hosts` file to contain the following:" -msgstr "" - -#: ../ceilometer-controller-install.rst:107 -msgid "" -"Edit the :file:`/etc/mongod.conf` file and complete the following actions:" -msgstr "" - -#: ../ceilometer-controller-install.rst:70 -#: ../ceilometer-controller-install.rst:142 -msgid "" -"Edit the :file:`/etc/mongodb.conf` file and complete the following actions:" -msgstr "" - -#: ../environment-networking.rst:173 -msgid "Edit the :file:`/etc/network/interfaces` file to contain the following:" -msgstr "" - -#: ../ceilometer-nova.rst:125 -msgid "" -"Edit the :file:`/etc/nova/nova.conf` file and configure notifications in the " -"``[DEFAULT]`` section:" -msgstr "" - -#: ../dashboard-install.rst:85 -msgid "" -"Edit the :file:`/etc/openstack-dashboard/local_settings.py` file and " -"complete the following actions:" -msgstr "" - -#: ../dashboard-install.rst:91 -msgid "" -"Edit the :file:`/etc/openstack-dashboard/local_settings` file and complete " -"the following actions:" -msgstr "" - -#: ../swift-storage-node.rst:116 -msgid "Edit the :file:`/etc/rsyncd.conf` file and add the following to it:" -msgstr "" - -#: ../swift-storage-node-include1.txt:1 -msgid "" -"Edit the :file:`/etc/swift/account-server.conf` file and complete the " -"following actions:" -msgstr "" - -#: ../swift-storage-node-include2.txt:1 -msgid "" -"Edit the :file:`/etc/swift/container-server.conf` file and complete the " -"following actions:" -msgstr "" - -#: ../swift-storage-node-include3.txt:1 -msgid "" -"Edit the :file:`/etc/swift/object-server.conf` file and complete the " -"following actions:" -msgstr "" - -# #-#-#-#-# ceilometer-swift.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# swift-controller-node.pot (Installation Guide 0.1) #-#-#-#-# -#: ../ceilometer-swift.rst:53 ../swift-controller-node-include.txt:1 -msgid "" -"Edit the :file:`/etc/swift/proxy-server.conf` file and complete the " -"following actions:" -msgstr "" - -#: ../swift-finalize-installation.rst:19 ../swift-finalize-installation.rst:55 -msgid "" -"Edit the :file:`/etc/swift/swift.conf` file and complete the following " -"actions:" -msgstr "" - -#: ../environment-networking.rst:185 -msgid "" -"Edit the :file:`/etc/sysconfig/network-scripts/ifcfg-INTERFACE_NAME` file to " -"contain the following:" -msgstr "" - -#: ../environment-networking.rst:199 -msgid "" -"Edit the :file:`/etc/sysconfig/network/ifcfg-INTERFACE_NAME` file to contain " -"the following:" -msgstr "" - -# #-#-#-#-# neutron-compute-install.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# neutron-controller-install-option1.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# neutron-controller-install-option2.pot (Installation Guide 0.1) #-#-#-#-# -#: ../neutron-compute-install.rst:13 -#: ../neutron-controller-install-option1.rst:12 -#: ../neutron-controller-install-option2.rst:13 -msgid "" -"Edit the :file:`/etc/sysctl.conf` file to contain the following parameters:" -msgstr "" - -#: ../dashboard-install.rst:79 -msgid "" -"Edit the :file:`/srv/www/openstack-dashboard/openstack_dashboard/local/" -"local_settings.py` file and complete the following actions:" -msgstr "" - -#: ../keystone-install.rst:356 -msgid "" -"Edit the ``/etc/apache2/apache2.conf`` file and configure the ``ServerName`` " -"option to reference the controller node:" -msgstr "" - -#: ../glance-install.rst:184 -msgid "" -"Edit the ``/etc/glance/glance-api.conf`` file and complete the following " -"actions:" -msgstr "" - -#: ../glance-install.rst:258 -msgid "" -"Edit the ``/etc/glance/glance-registry.conf`` file and complete the " -"following actions:" -msgstr "" - -#: ../keystone-install.rst:293 -msgid "" -"Edit the ``/etc/httpd/conf/httpd.conf`` file and configure the " -"``ServerName`` option to reference the controller node:" -msgstr "" - -#: ../keystone-verify.rst:12 -msgid "" -"Edit the ``/etc/keystone/keystone-paste.ini`` file and remove " -"``admin_token_auth`` from the ``[pipeline:public_api]``, ``[pipeline:" -"admin_api]``, and ``[pipeline:api_v3]`` sections." -msgstr "" - -#: ../keystone-install.rst:114 -msgid "" -"Edit the ``/etc/keystone/keystone.conf`` file and complete the following " -"actions:" -msgstr "" - -# #-#-#-#-# neutron-controller-install-option1.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# neutron-controller-install-option2.pot (Installation Guide 0.1) #-#-#-#-# -#: ../neutron-controller-install-option1.rst:300 -#: ../neutron-controller-install-option2.rst:351 -msgid "Edit the ``/etc/neutron/dhcp_agent.ini`` file." -msgstr "" - -#: ../neutron-controller-install-option2.rst:320 -msgid "Edit the ``/etc/neutron/l3_agent.ini`` file:" -msgstr "" - -#: ../neutron-controller-install.rst:140 -msgid "Edit the ``/etc/neutron/metadata_agent.ini`` file." -msgstr "" - -# #-#-#-#-# neutron-compute-install.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# neutron-controller-install-option1.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# neutron-controller-install-option2.pot (Installation Guide 0.1) #-#-#-#-# -#: ../neutron-compute-install.rst:82 -#: ../neutron-controller-install-option1.rst:91 -#: ../neutron-controller-install-option2.rst:87 -msgid "Edit the ``/etc/neutron/neutron.conf`` file." -msgstr "" - -# #-#-#-#-# neutron-compute-install-option1.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# neutron-compute-install-option2.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# neutron-controller-install-option1.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# neutron-controller-install-option2.pot (Installation Guide 0.1) #-#-#-#-# -#: ../neutron-compute-install-option1.rst:13 -#: ../neutron-compute-install-option2.rst:13 -#: ../neutron-controller-install-option1.rst:255 -#: ../neutron-controller-install-option2.rst:266 -msgid "Edit the ``/etc/neutron/plugins/ml2/linuxbridge_agent.conf`` file." -msgstr "" - -# #-#-#-#-# neutron-controller-install-option1.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# neutron-controller-install-option2.pot (Installation Guide 0.1) #-#-#-#-# -#: ../neutron-controller-install-option1.rst:200 -#: ../neutron-controller-install-option2.rst:197 -msgid "Edit the ``/etc/neutron/plugins/ml2/ml2_conf.ini`` file." -msgstr "" - -# #-#-#-#-# nova-compute-install.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# nova-controller-install.pot (Installation Guide 0.1) #-#-#-#-# -#: ../nova-compute-install.rst:53 ../nova-controller-install.rst:181 -msgid "" -"Edit the ``/etc/nova/nova.conf`` file and complete the following actions:" -msgstr "" - -#: ../neutron-compute-install.rst:165 -msgid "Edit the ``/etc/nova/nova.conf`` file." -msgstr "" - -#: ../neutron-controller-install.rst:192 -msgid "Edit the ``/etc/nova/nova.conf`` file:" -msgstr "" - -#: ../keystone-install.rst:425 -msgid "" -"Edit the ``/etc/sysconfig/apache2`` file and configure the " -"``APACHE_SERVERNAME`` option to reference the controller node:" -msgstr "" - -#: ../keystone-verify.rst:22 -msgid "" -"Edit the ``/usr/share/keystone/keystone-dist-paste.ini`` file and remove " -"``admin_token_auth`` from the ``[pipeline:public_api]``, ``[pipeline:" -"admin_api]``, and ``[pipeline:api_v3]`` sections." -msgstr "" - -#: ../nova-compute-install.rst:237 -msgid "" -"Edit the ``[libvirt]`` section in the ``/etc/nova/nova-compute.conf`` file " -"as follows:" -msgstr "" - -#: ../nova-compute-install.rst:226 -msgid "" -"Edit the ``[libvirt]`` section in the ``/etc/nova/nova.conf`` file as " -"follows:" -msgstr "" - -#: ../keystone-openrc.rst:20 -msgid "Edit the ``admin-openrc.sh`` file and add the following content:" -msgstr "" - -#: ../keystone-openrc.rst:36 -msgid "Edit the ``demo-openrc.sh`` file and add the following content:" -msgstr "" - -#: ../keystone-install.rst:417 -msgid "Enable the Identity service virtual hosts:" -msgstr "" - -#: ../environment-dependencies.rst:78 -msgid "" -"Enable the Open Build Service repositories based on your openSUSE or SLES " -"version:" -msgstr "" - -#: ../ceilometer-controller-install.rst:18 -msgid "" -"Enable the Open Build Service repositories for MongoDB based on your " -"openSUSE or SLES version:" -msgstr "" - -#: ../environment-dependencies.rst:23 ../environment-dependencies.rst:65 -#: ../environment-dependencies.rst:76 -msgid "Enable the OpenStack repository" -msgstr "" - -#: ../environment-dependencies.rst:119 -msgid "Enable the backports repository" -msgstr "" - -#: ../overview.rst:40 -msgid "" -"Enables Network-Connectivity-as-a-Service for other OpenStack services, such " -"as OpenStack Compute. Provides an API for users to define networks and the " -"attachments into them. Has a pluggable architecture that supports many " -"popular networking vendors and technologies." -msgstr "" - -#: ../swift-storage-node.rst:232 ../swift-storage-node.rst:250 -msgid "Ensure proper ownership of the mount point directory structure:" -msgstr "" - -#: ../nova-compute-install.rst:197 -msgid "Ensure the kernel module ``nbd`` is loaded." -msgstr "" - -#: ../nova-compute-install.rst:203 -msgid "" -"Ensure the module will be loaded on every boot by adding ``nbd`` in the ``/" -"etc/modules-load.d/nbd.conf`` file." -msgstr "" - -#: ../environment.rst:5 -msgid "Environment" -msgstr "" - -#: ../overview.rst:109 -msgid "Example architecture" -msgstr "" - -# #-#-#-#-# cinder-controller-node.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# glance-install.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# heat-install.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# keystone-install.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# neutron-controller-install.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# nova-controller-install.pot (Installation Guide 0.1) #-#-#-#-# -#: ../cinder-controller-node.rst:42 ../glance-install.rst:42 -#: ../heat-install.rst:38 ../keystone-install.rst:41 -#: ../neutron-controller-install.rst:35 ../nova-controller-install.rst:39 -msgid "Exit the database access client." -msgstr "" - -#: ../index-debian.rst:66 -msgid "" -"Explanations of configuration options and sample configuration files are " -"included." -msgstr "" - -#: ../environment-dependencies.rst:199 -msgid "Fedora does not require this package." -msgstr "" - -#: ../environment-dependencies.rst:48 -msgid "Fedora does not require this repository." -msgstr "" - -# #-#-#-#-# glance-install.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# neutron-compute-install.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# neutron-controller-install.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# nova-compute-install.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# nova-controller-install.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# swift-finalize-installation.pot (Installation Guide 0.1) #-#-#-#-# -#: ../glance-install.rst:351 ../neutron-compute-install.rst:202 -#: ../neutron-controller-install.rst:235 ../nova-compute-install.rst:207 -#: ../nova-controller-install.rst:351 ../swift-finalize-installation.rst:3 -msgid "Finalize installation" -msgstr "" - -# #-#-#-#-# environment-dependencies.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# keystone-install.pot (Installation Guide 0.1) #-#-#-#-# -#: ../environment-dependencies.rst:146 ../keystone-install.rst:493 -msgid "Finalize the installation" -msgstr "" - -#: ../environment.rst:96 -msgid "" -"For OpenStack services, this guide uses ``SERVICE_PASS`` to reference " -"service account passwords and ``SERVICE_DBPASS`` to reference database " -"passwords." -msgstr "" - -#: ../environment.rst:36 -msgid "" -"For best performance, we recommend that your environment meets or exceeds " -"the hardware requirements in :ref:`figure-hwreqs`. However, OpenStack does " -"not require a significant amount of resources and the following minimum " -"requirements should support a proof-of-concept environment with core " -"services and several :term:`CirrOS` instances:" -msgstr "" - -#: ../neutron-controller-install.rst:287 ../neutron-controller-install.rst:326 -#: ../neutron-controller-install.rst:380 -msgid "For both networking options:" -msgstr "" - -#: ../dashboard-next-step.rst:27 -msgid "" -"For details about browsers that support noVNC, see `README `__ and `browser support `__." -msgstr "" - -#: ../debconf/debconf-rabbitmq.rst:7 -msgid "" -"For every package that must connect to a Messaging Server, the Debian " -"package enables you to configure the IP address for that server and the user " -"name and password that is used to connect. The following example shows " -"configuration with the ``ceilometer-common`` package:" -msgstr "" - -#: ../glance-verify.rst:74 -msgid "" -"For information about disk and container formats for images, see `Disk and " -"container formats for images `__ in the ``OpenStack Virtual Machine Image Guide``." -msgstr "" - -#: ../glance-verify.rst:68 -msgid "" -"For information about the :command:`glance image-create` parameters, see " -"`Image service command-line client `__ in the ``OpenStack Command-Line Interface Reference``." -msgstr "" - -#: ../glance.rst:29 -msgid "" -"For information on requirements for other back ends, see `Configuration " -"Reference `__." -msgstr "" - -#: ../glance-verify.rst:8 -msgid "" -"For more information about how to download and build images, see `OpenStack " -"Virtual Machine Image Guide `__. For information about how to manage images, see the " -"`OpenStack User Guide `__." -msgstr "" - -#: ../launch-instance-cinder.rst:123 -msgid "" -"For more information about how to manage volumes, see the `OpenStack User " -"Guide `__." -msgstr "" - -#: ../environment.rst:75 -msgid "" -"For more information about system requirements, see the `OpenStack " -"Operations Guide `_." -msgstr "" - -# #-#-#-#-# swift-controller-node.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# swift-storage-node.pot (Installation Guide 0.1) #-#-#-#-# -#: ../swift-controller-node-include.txt:28 -#: ../swift-storage-node-include1.txt:31 ../swift-storage-node-include2.txt:31 -#: ../swift-storage-node-include3.txt:31 -msgid "" -"For more information on other modules that enable additional features, see " -"the `Deployment Guide `__." -msgstr "" - -#: ../overview.rst:124 -msgid "" -"For more information on production architectures, see the `Architecture " -"Design Guide `__, " -"`Operations Guide `__, and `Networking Guide " -"`__." -msgstr "" - -#: ../dashboard-install.rst:154 -msgid "" -"For more information, see the `bug report `__." -msgstr "" - -#: ../neutron-controller-install.rst:298 ../neutron-controller-install.rst:339 -msgid "For networking option 2, also enable and start the layer-3 service:" -msgstr "" - -# #-#-#-#-# neutron-controller-install-option1.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# neutron-controller-install-option2.pot (Installation Guide 0.1) #-#-#-#-# -#: ../neutron-controller-install-option1.rst:62 -#: ../neutron-controller-install-option2.rst:64 -msgid "For networking option 2, also install the ``neutron-l3-agent`` package." -msgstr "" - -#: ../neutron-controller-install.rst:389 -msgid "For networking option 2, also restart the layer-3 service:" -msgstr "" - -#: ../keystone-verify.rst:9 ../keystone-verify.rst:19 -msgid "" -"For security reasons, disable the temporary authentication token mechanism:" -msgstr "" - -#: ../keystone-services.rst:36 -msgid "" -"For security reasons, do not use the temporary authentication token for " -"longer than necessary to initialize the Identity service." -msgstr "" - -#: ../overview.rst:168 ../overview.rst:182 -msgid "" -"For simplicity, service traffic between compute nodes and this node uses the " -"management network. Production environments should implement a separate " -"storage network to increase performance and security." -msgstr "" - -#: ../glance.rst:21 -msgid "" -"For simplicity, this guide describes configuring the Image service to use " -"the ``file`` back end, which uploads and stores in a directory on the " -"controller node hosting the Image service. By default, this directory is :" -"file:`/var/lib/glance/images/`." -msgstr "" - -#: ../keystone-users.rst:11 -msgid "For simplicity, this guide uses the ``default`` domain." -msgstr "" - -#: ../neutron-concepts.rst:36 -msgid "" -"For the outside network to access VMs, and vice versa, routers between the " -"networks are needed. Each router has one gateway that is connected to a " -"network and many interfaces that are connected to subnets. Like a physical " -"router, subnets can access machines on other subnets that are connected to " -"the same router, and machines can access the outside network through the " -"gateway for the router." -msgstr "" - -#: ../swift-storage-node.rst:87 -msgid "Format the :file:`/dev/sdb1` and :file:`/dev/sdc1` partitions as XFS:" -msgstr "" - -#: ../environment-networking.rst:273 -msgid "From the *compute* node, test access to the Internet:" -msgstr "" - -#: ../environment-networking.rst:288 -msgid "" -"From the *compute* node, test access to the management interface on the " -"*controller* node:" -msgstr "" - -#: ../environment-networking.rst:242 -msgid "From the *controller* node, test access to the Internet:" -msgstr "" - -#: ../environment-networking.rst:257 -msgid "" -"From the *controller* node, test access to the management interface on the " -"*compute* node:" -msgstr "" - -# #-#-#-#-# neutron-compute-install.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# neutron-controller-install.pot (Installation Guide 0.1) #-#-#-#-# -#: ../neutron-compute-install.rst:229 ../neutron-controller-install.rst:262 -msgid "" -"Future upgrades of the ``neutron-linuxbridge-agent`` package may overwrite " -"this modification." -msgstr "" - -#: ../debconf/debconf-concepts.rst:65 -msgid "" -"Generally, the ``-common`` packages install the configuration files. For " -"example, the ``glance-common`` package installs the :file:`glance-api.conf` " -"and :file:`glance-registry.conf` files. So, for the Image service, you must " -"re-configure the ``glance-common`` package. The same applies for ``cinder-" -"common``, ``nova-common``, and ``heat-common`` packages." -msgstr "" - -#: ../debconf/debconf-keystone-authtoken.rst:12 -msgid "Generally, this section looks like this:" -msgstr "" - -#: ../launch-instance.rst:39 -msgid "Generate a key pair" -msgstr "" - -#: ../keystone-install.rst:43 ../keystone-install.rst:215 -msgid "" -"Generate a random value to use as the administration token during initial " -"configuration:" -msgstr "" - -#: ../ceilometer-controller-install.rst:337 -msgid "Generate a random value to use as the telemetry secret:" -msgstr "" - -#: ../launch-instance.rst:51 -msgid "Generate and add a key pair:" -msgstr "" - -#: ../cinder-controller-node.rst:31 -msgid "Grant proper access to the ``cinder`` database:" -msgstr "" - -#: ../glance-install.rst:31 -msgid "Grant proper access to the ``glance`` database:" -msgstr "" - -#: ../heat-install.rst:29 -msgid "Grant proper access to the ``heat`` database::" -msgstr "" - -#: ../keystone-install.rst:30 -msgid "Grant proper access to the ``keystone`` database:" -msgstr "" - -#: ../neutron-controller-install.rst:25 -msgid "" -"Grant proper access to the ``neutron`` database, replacing " -"``NEUTRON_DBPASS`` with a suitable password:" -msgstr "" - -#: ../nova-controller-install.rst:28 -msgid "Grant proper access to the ``nova`` database:" -msgstr "" - -#: ../horizon.rst:13 -msgid "Horizon enables you to customize the brand of the dashboard." -msgstr "" - -#: ../horizon.rst:15 -msgid "" -"Horizon provides a set of core classes and reusable templates and tools." -msgstr "" - -#: ../environment-networking.rst:2 -msgid "Host Networking" -msgstr "" - -#: ../environment.rst:170 -msgid "Host networking, NTP, OpenStack service dependencies" -msgstr "" - -#: ../environment.rst:65 -msgid "" -"However, VMs will reduce performance of your instances, particularly if your " -"hypervisor and/or processor lacks support for hardware acceleration of " -"nested VMs." -msgstr "" - -#: ../app_reserved_uids.rst:21 -msgid "ID" -msgstr "" - -#: ../environment-networking.rst:111 -msgid "IP address: 10.0.0.11" -msgstr "" - -#: ../environment-networking.rst:154 -msgid "IP address: 10.0.0.31" -msgstr "" - -#: ../cinder-storage-node.rst:28 -msgid "IP address: 10.0.0.41" -msgstr "" - -#: ../swift-storage-node.rst:31 -msgid "IP address: ``10.0.0.51``" -msgstr "" - -#: ../swift-storage-node.rst:41 -msgid "IP address: ``10.0.0.52``" -msgstr "" - -#: ../neutron-controller-install-option2.rst:375 -msgid "" -"Ideally, you can prevent these problems by enabling :term:`jumbo frames " -"` on the physical network that contains your tenant virtual " -"networks. Jumbo frames support MTUs up to approximately 9000 bytes which " -"negates the impact of VXLAN overhead on virtual networks. However, many " -"network devices lack support for jumbo frames and OpenStack administrators " -"often lack control over network infrastructure. Given the latter " -"complications, you can also prevent MTU problems by reducing the instance " -"MTU to account for VXLAN overhead. Determining the proper MTU value often " -"takes experimentation, but 1450 bytes works in most environments. You can " -"configure the DHCP server that assigns IP addresses to your instances to " -"also adjust the MTU." -msgstr "" - -#: ../environment-dependencies.rst:209 -msgid "" -"If ``SELinux status`` is ``enabled`` disable SELinux by editing the file ``/" -"etc/selinux/config`` and restarting the system afterwards:" -msgstr "" - -#: ../environment-ntp-controller.rst:87 -msgid "" -"If necessary, replace ``10.0.0.0/24`` with a description of your subnet." -msgstr "" - -#: ../environment-dependencies.rst:158 ../environment-dependencies.rst:171 -#: ../environment-dependencies.rst:184 -msgid "" -"If the upgrade process includes a new kernel, reboot your system to activate " -"it." -msgstr "" - -#: ../nova-compute-install.rst:152 -msgid "" -"If the web browser to access remote consoles resides on a host that cannot " -"resolve the ``controller`` hostname, you must replace ``controller`` with " -"the management interface IP address of the controller node." -msgstr "" - -#: ../nova-compute-install.rst:216 -msgid "" -"If this command returns a value of ``one or greater``, your compute node " -"supports hardware acceleration which typically requires no additional " -"configuration." -msgstr "" - -#: ../nova-compute-install.rst:220 -msgid "" -"If this command returns a value of ``zero``, your compute node does not " -"support hardware acceleration and you must configure ``libvirt`` to use QEMU " -"instead of KVM." -msgstr "" - -#: ../debconf/debconf-concepts.rst:15 -msgid "" -"If you are familiar with these packages and pre-seeding, you can proceed to :" -"doc:`../keystone`." -msgstr "" - -#: ../ceilometer-controller-install.rst:164 -msgid "" -"If you change the journaling configuration, stop the MongoDB service, remove " -"the initial journal files, and start the service:" -msgstr "" - -#: ../environment.rst:71 -msgid "" -"If you choose to install on VMs, make sure your hypervisor permits :term:" -"`promiscuous mode` and disables MAC address filtering on the :term:`external " -"network`." -msgstr "" - -#: ../launch-instance.rst:109 -msgid "" -"If you chose networking option 1, you can only launch an instance on the " -"public network. If you chose networking option 2, you can launch an instance " -"on the public network and the private network." -msgstr "" - -#: ../launch-instance-networks-private.rst:6 -msgid "" -"If you chose networking option 2, you can also create a private project " -"virtual network that connects to the physical network infrastructure via " -"layer-3 (routing) and NAT. This network includes a DHCP server that provides " -"IP addresses to instances. An instance on this network can automatically " -"access external networks such as the Internet. However, access to an " -"instance on this network from external networks such as the Internet " -"requires a :term:`floating IP address`." -msgstr "" - -#: ../launch-instance-public.rst:89 -msgid "" -"If you chose option 1 and your environment contains only one network, you " -"can omit the ``--nic`` option because OpenStack automatically chooses the " -"only network available." -msgstr "" - -#: ../launch-instance-public.rst:65 -msgid "" -"If you chose option 2, the output should also contain the private network." -msgstr "" - -#: ../debconf/debconf-concepts.rst:52 -msgid "" -"If you configure a package with ``debconf`` incorrectly, you can re-" -"configure it, as follows:" -msgstr "" - -#: ../keystone-install.rst:207 -msgid "" -"If you decide to not use ``dbconfig-common``, then you will have to create " -"the database and manage its access rights yourself, and run the following by " -"hand." -msgstr "" - -#: ../cinder-storage-node.rst:50 ../cinder-storage-node.rst:61 -#: ../cinder-storage-node.rst:88 -msgid "" -"If you intend to use non-raw image types such as QCOW2 and VMDK, install the " -"QEMU support package:" -msgstr "" - -#: ../launch-instance.rst:124 -msgid "" -"If your environment includes the Block Storage service, you can create a " -"volume and attach it to an instance." -msgstr "" - -# #-#-#-#-# launch-instance-private.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# launch-instance-public.pot (Installation Guide 0.1) #-#-#-#-# -#: ../launch-instance-private.rst:261 ../launch-instance-public.rst:231 -msgid "" -"If your host does not contain the public/private key pair created in an " -"earlier step, SSH prompts for the default password associated with the " -"``cirros`` user, ``cubswin:)``." -msgstr "" - -# #-#-#-#-# launch-instance-private.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# launch-instance-public.pot (Installation Guide 0.1) #-#-#-#-# -#: ../launch-instance-private.rst:265 ../launch-instance-public.rst:235 -msgid "" -"If your instance does not launch or seem to work as you expect, see the " -"`OpenStack Operations Guide `__ for more " -"information or use one of the :doc:`many other options ` " -"to seek assistance. We want your first installation to work!" -msgstr "" - -#: ../cinder-storage-node.rst:157 -msgid "" -"If your storage nodes use LVM on the operating system disk, you must also " -"add the associated device to the filter. For example, if the :file:`/dev/" -"sda` device contains the operating system:" -msgstr "" - -#: ../cinder-storage-node.rst:119 -msgid "" -"If your system uses a different device name, adjust these steps accordingly." -msgstr "" - -# #-#-#-#-# launch-instance-private.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# launch-instance-public.pot (Installation Guide 0.1) #-#-#-#-# -#: ../launch-instance-private.rst:148 ../launch-instance-public.rst:159 -msgid "" -"If your web browser runs on a host that cannot resolve the ``controller`` " -"host name, you can replace ``controller`` with the IP address of the " -"management interface on your controller node." -msgstr "" - -#: ../nova-verify.rst:131 -msgid "Ignore any warnings in this output." -msgstr "" - -#: ../overview.rst:103 -msgid "" -"Implement a deployment tool such as Ansible, Chef, Puppet, or Salt to " -"automate deployment and management of the production environment." -msgstr "" - -# #-#-#-#-# neutron-compute-install.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# neutron-controller-install-option1.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# neutron-controller-install-option2.pot (Installation Guide 0.1) #-#-#-#-# -#: ../neutron-compute-install.rst:20 -#: ../neutron-controller-install-option1.rst:19 -#: ../neutron-controller-install-option2.rst:21 -msgid "Implement the changes:" -msgstr "" - -#: ../keystone-install.rst:269 -msgid "" -"In Debian, the Keystone package offers automatic registration of Keystone in " -"the service catalogue. This is equivalent of running the below commands:" -msgstr "" - -#: ../keystone-install.rst:58 -msgid "" -"In Kilo and Liberty releases, the keystone project deprecates eventlet in " -"favor of a separate web server with WSGI extensions. This guide uses the " -"Apache HTTP server with ``mod_wsgi`` to serve Identity service requests on " -"port 5000 and 35357. By default, the keystone service still listens on ports " -"5000 and 35357. Therefore, this guide disables the keystone service. The " -"keystone project plans to remove eventlet support in Mitaka." -msgstr "" - -#: ../debconf/debconf-concepts.rst:71 -msgid "" -"In ``debconf``, the higher the priority for a screen, the greater the chance " -"that the user sees that screen. If a ``debconf`` screen has ``medium`` " -"priority and you configure the Debian system to show only ``critical`` " -"prompts, which is the default in Debian, the user does not see that " -"``debconf`` screen. Instead, the default for the related package is used. In " -"the Debian OpenStack packages, a number of ``debconf`` screens are set with " -"``medium`` priority. Consequently, if you want to respond to all ``debconf`` " -"screens from the Debian OpenStack packages, you must run the following " -"command and select the ``medium`` priority before you install any packages:" -msgstr "" - -#: ../neutron-concepts.rst:30 -msgid "" -"In addition to external networks, any Networking set up has one or more " -"internal networks. These software-defined networks connect directly to the " -"VMs. Only the VMs on any given internal network, or those on subnets " -"connected through interfaces to a similar router, can access VMs connected " -"to that network directly." -msgstr "" - -#: ../cinder-verify.rst:13 -msgid "" -"In each client environment script, configure the Block Storage client to use " -"API version 2.0:" -msgstr "" - -#: ../glance-verify.rst:15 -msgid "" -"In each client environment script, configure the Image service client to use " -"API version 2.0:" -msgstr "" - -#: ../nova-compute-install.rst:56 -msgid "" -"In the ``[DEFAULT]`` and [oslo_messaging_rabbit] sections, configure " -"``RabbitMQ`` message queue access:" -msgstr "" - -# #-#-#-#-# ceilometer-controller-install.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# cinder-controller-node.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# cinder-storage-node.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# neutron-compute-install.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# neutron-controller-install-option1.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# neutron-controller-install-option2.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# nova-compute-install.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# nova-controller-install.pot (Installation Guide 0.1) #-#-#-#-# -#: ../ceilometer-controller-install.rst:379 ../cinder-controller-node.rst:237 -#: ../cinder-storage-node.rst:238 ../neutron-compute-install.rst:105 -#: ../neutron-controller-install-option1.rst:132 -#: ../neutron-controller-install-option2.rst:129 -#: ../nova-compute-install.rst:74 ../nova-controller-install.rst:213 -msgid "" -"In the ``[DEFAULT]`` and ``[keystone_authtoken]`` sections, configure " -"Identity service access:" -msgstr "" - -# #-#-#-#-# neutron-controller-install-option1.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# neutron-controller-install-option2.pot (Installation Guide 0.1) #-#-#-#-# -#: ../neutron-controller-install-option1.rst:160 -#: ../neutron-controller-install-option2.rst:157 -msgid "" -"In the ``[DEFAULT]`` and ``[nova]`` sections, configure Networking to notify " -"Compute of network topology changes:" -msgstr "" - -# #-#-#-#-# neutron-compute-install.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# neutron-controller-install-option1.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# neutron-controller-install-option2.pot (Installation Guide 0.1) #-#-#-#-# -#: ../neutron-compute-install.rst:87 -#: ../neutron-controller-install-option1.rst:114 -#: ../neutron-controller-install-option2.rst:111 -msgid "" -"In the ``[DEFAULT]`` and ``[oslo_messaging_rabbit]`` sections, configure " -"RabbitMQ message queue access:" -msgstr "" - -# #-#-#-#-# ceilometer-controller-install.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# ceilometer-nova.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# cinder-controller-node.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# cinder-storage-node.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# heat-install.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# nova-controller-install.pot (Installation Guide 0.1) #-#-#-#-# -#: ../ceilometer-controller-install.rst:360 ../ceilometer-nova.rst:50 -#: ../cinder-controller-node.rst:219 ../cinder-storage-node.rst:220 -#: ../heat-install.rst:256 ../nova-controller-install.rst:195 -msgid "" -"In the ``[DEFAULT]`` and ``[oslo_messaging_rabbit]`` sections, configure " -"``RabbitMQ`` message queue access:" -msgstr "" - -# #-#-#-#-# neutron-compute-install.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# neutron-controller-install.pot (Installation Guide 0.1) #-#-#-#-# -#: ../neutron-compute-install.rst:167 ../neutron-controller-install.rst:194 -msgid "" -"In the ``[DEFAULT]`` section, configure Compute to use the Networking " -"service:" -msgstr "" - -#: ../neutron-controller-install.rst:142 -msgid "In the ``[DEFAULT]`` section, configure access parameters:" -msgstr "" - -#: ../heat-install.rst:313 -msgid "" -"In the ``[DEFAULT]`` section, configure information about the heat Identity " -"service domain:" -msgstr "" - -#: ../ceilometer-glance.rst:13 -msgid "" -"In the ``[DEFAULT]`` section, configure notifications and RabbitMQ message " -"broker access:" -msgstr "" - #: ../ceilometer-cinder.rst:15 msgid "In the ``[DEFAULT]`` section, configure notifications:" msgstr "" -#: ../neutron-controller-install-option2.rst:322 +#: ../ceilometer-cinder.rst:26 ../ceilometer-cinder.rst:40 +msgid "Restart the Block Storage services on the controller node:" +msgstr "" + +#: ../ceilometer-cinder.rst:32 ../ceilometer-cinder.rst:47 +msgid "Restart the Block Storage services on the storage nodes:" +msgstr "" + +#: ../ceilometer-cinder.rst:53 msgid "" -"In the ``[DEFAULT]`` section, configure the Linux bridge interface driver " -"and external network bridge:" -msgstr "" - -# #-#-#-#-# neutron-controller-install-option1.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# neutron-controller-install-option2.pot (Installation Guide 0.1) #-#-#-#-# -#: ../neutron-controller-install-option1.rst:302 -#: ../neutron-controller-install-option2.rst:353 -msgid "" -"In the ``[DEFAULT]`` section, configure the Linux bridge interface driver, " -"Dnsmasq DHCP driver, and enable isolated metadata so instances on public " -"networks can access metadata over the network:" -msgstr "" - -# #-#-#-#-# cinder-controller-node.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# nova-controller-install.pot (Installation Guide 0.1) #-#-#-#-# -#: ../cinder-controller-node.rst:265 ../nova-controller-install.rst:241 -msgid "" -"In the ``[DEFAULT]`` section, configure the ``my_ip`` option to use the " -"management interface IP address of the controller node:" -msgstr "" - -# #-#-#-#-# cinder-storage-node.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# nova-compute-install.pot (Installation Guide 0.1) #-#-#-#-# -#: ../cinder-storage-node.rst:266 ../nova-compute-install.rst:102 -msgid "In the ``[DEFAULT]`` section, configure the ``my_ip`` option:" -msgstr "" - -#: ../glance-install.rst:236 ../glance-install.rst:300 -msgid "" -"In the ``[DEFAULT]`` section, configure the ``noop`` notification driver to " -"disable notifications because they only pertain to the optional Telemetry " -"service:" -msgstr "" - -#: ../swift-storage-node-include1.txt:4 ../swift-storage-node-include2.txt:4 -#: ../swift-storage-node-include3.txt:4 -msgid "" -"In the ``[DEFAULT]`` section, configure the bind IP address, bind port, " -"user, configuration directory, and mount point directory:" -msgstr "" - -#: ../swift-controller-node-include.txt:4 -msgid "" -"In the ``[DEFAULT]`` section, configure the bind port, user, and " -"configuration directory:" -msgstr "" - -#: ../cinder-storage-node.rst:322 -msgid "" -"In the ``[DEFAULT]`` section, configure the location of the Image service:" -msgstr "" - -#: ../heat-install.rst:302 -msgid "" -"In the ``[DEFAULT]`` section, configure the metadata and wait condition URLs:" -msgstr "" - -#: ../neutron-controller-install.rst:161 -msgid "In the ``[DEFAULT]`` section, configure the metadata host:" -msgstr "" - -#: ../neutron-controller-install.rst:169 -msgid "" -"In the ``[DEFAULT]`` section, configure the metadata proxy shared secret:" -msgstr "" - -#: ../keystone-install.rst:117 -msgid "" -"In the ``[DEFAULT]`` section, define the value of the initial administration " -"token:" -msgstr "" - -#: ../nova-controller-install.rst:317 -msgid "In the ``[DEFAULT]`` section, disable the EC2 API:" -msgstr "" - -# #-#-#-#-# nova-compute-install.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# nova-controller-install.pot (Installation Guide 0.1) #-#-#-#-# -#: ../nova-compute-install.rst:115 ../nova-controller-install.rst:250 -msgid "" -"In the ``[DEFAULT]`` section, enable support for the Networking service:" -msgstr "" - -#: ../neutron-controller-install-option2.rst:393 -msgid "" -"In the ``[DEFAULT]`` section, enable the :term:`dnsmasq` configuration file:" -msgstr "" - -#: ../cinder-storage-node.rst:309 -msgid "In the ``[DEFAULT]`` section, enable the LVM back end:" -msgstr "" - -#: ../neutron-controller-install-option1.rst:104 -msgid "" -"In the ``[DEFAULT]`` section, enable the Modular Layer 2 (ML2) plug-in and " -"disable additional plug-ins:" -msgstr "" - -#: ../neutron-controller-install-option2.rst:100 -msgid "" -"In the ``[DEFAULT]`` section, enable the Modular Layer 2 (ML2) plug-in, " -"router service, and overlapping IP addresses:" -msgstr "" - -# #-#-#-#-# neutron-controller-install-option1.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# neutron-controller-install-option2.pot (Installation Guide 0.1) #-#-#-#-# -#: ../neutron-controller-install-option1.rst:275 -#: ../neutron-controller-install-option2.rst:294 -msgid "In the ``[agent]`` section, enable ARP spoofing protection:" -msgstr "" - -#: ../swift-controller-node-include.txt:31 -msgid "" -"In the ``[app:proxy-server]`` section, enable automatic account creation:" -msgstr "" - -#: ../ceilometer-controller-install.rst:436 -msgid "In the ``[collector]`` section, configure the dispatcher:" -msgstr "" - -#: ../neutron-compute-install.rst:84 -msgid "" -"In the ``[database]`` section, comment out any ``connection`` options " -"because compute nodes do not directly access the database." -msgstr "" - -# #-#-#-#-# ceilometer-controller-install.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# cinder-controller-node.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# cinder-storage-node.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# glance-install.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# heat-install.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# keystone-install.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# neutron-controller-install-option1.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# neutron-controller-install-option2.pot (Installation Guide 0.1) #-#-#-#-# -#: ../ceilometer-controller-install.rst:346 ../cinder-controller-node.rst:208 -#: ../cinder-storage-node.rst:209 ../glance-install.rst:187 -#: ../glance-install.rst:261 ../heat-install.rst:244 -#: ../keystone-install.rst:129 ../neutron-controller-install-option1.rst:93 -#: ../neutron-controller-install-option2.rst:89 -msgid "In the ``[database]`` section, configure database access:" -msgstr "" - -#: ../heat-install.rst:381 -msgid "In the ``[ec2authtoken]`` section, configure Identity service access:" -msgstr "" - -#: ../swift-controller-node-include.txt:48 -msgid "" -"In the ``[filter:authtoken]`` section, configure Identity service access:" -msgstr "" - -#: ../swift-controller-node-include.txt:74 -msgid "" -"In the ``[filter:cache]`` section, configure the ``memcached`` location:" -msgstr "" - -#: ../ceilometer-swift.rst:75 -msgid "In the ``[filter:ceilometer]`` section, configure notifications:" -msgstr "" - -#: ../ceilometer-swift.rst:56 -msgid "" -"In the ``[filter:keystoneauth]`` section, add the ``ResellerAdmin`` role:" -msgstr "" - -#: ../swift-controller-node-include.txt:39 -msgid "In the ``[filter:keystoneauth]`` section, configure the operator roles:" -msgstr "" - -#: ../swift-storage-node-include3.txt:34 -msgid "" -"In the ``[filter:recon]`` section, configure the recon (meters) cache and " -"lock directories:" -msgstr "" - -#: ../swift-storage-node-include1.txt:34 ../swift-storage-node-include2.txt:34 -msgid "" -"In the ``[filter:recon]`` section, configure the recon (meters) cache " -"directory:" -msgstr "" - -# #-#-#-#-# nova-compute-install.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# nova-controller-install.pot (Installation Guide 0.1) #-#-#-#-# -#: ../nova-compute-install.rst:157 ../nova-controller-install.rst:278 -msgid "" -"In the ``[glance]`` section, configure the location of the Image service:" -msgstr "" - -#: ../glance-install.rst:226 -msgid "" -"In the ``[glance_store]`` section, configure the local file system store and " -"location of image files:" -msgstr "" - -#: ../heat-install.rst:275 -msgid "" -"In the ``[keystone_authtoken]`` and ``[ec2authtoken]`` sections, configure " -"Identity service access:" -msgstr "" - -#: ../glance-install.rst:198 ../glance-install.rst:272 -msgid "" -"In the ``[keystone_authtoken]`` and ``[paste_deploy]`` sections, configure " -"Identity service access:" -msgstr "" - -#: ../ceilometer-nova.rst:69 -msgid "" -"In the ``[keystone_authtoken]`` section, configure Identity service access:" -msgstr "" - -# #-#-#-#-# neutron-compute-install-option1.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# neutron-compute-install-option2.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# neutron-controller-install-option1.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# neutron-controller-install-option2.pot (Installation Guide 0.1) #-#-#-#-# -#: ../neutron-compute-install-option1.rst:15 -#: ../neutron-compute-install-option2.rst:15 -#: ../neutron-controller-install-option1.rst:257 -#: ../neutron-controller-install-option2.rst:268 -msgid "" -"In the ``[linux_bridge]`` section, map the public virtual network to the " -"public physical network interface:" -msgstr "" - -#: ../cinder-storage-node.rst:281 ../cinder-storage-node.rst:296 -msgid "" -"In the ``[lvm]`` section, configure the LVM back end with the LVM driver, " -"``cinder-volumes`` volume group, iSCSI protocol, and appropriate iSCSI " -"service:" -msgstr "" - -#: ../keystone-install.rst:139 -msgid "In the ``[memcache]`` section, configure the Memcache service:" -msgstr "" - -#: ../neutron-controller-install-option1.rst:210 -msgid "In the ``[ml2]`` section, disable project (private) networks:" -msgstr "" - -#: ../neutron-controller-install-option2.rst:207 -msgid "In the ``[ml2]`` section, enable VXLAN project (private) networks:" -msgstr "" - -#: ../neutron-controller-install-option1.rst:202 -msgid "In the ``[ml2]`` section, enable flat and VLAN networks:" -msgstr "" - -#: ../neutron-controller-install-option2.rst:199 -msgid "In the ``[ml2]`` section, enable flat, VLAN, and VXLAN networks:" -msgstr "" - -#: ../neutron-controller-install-option2.rst:215 -msgid "" -"In the ``[ml2]`` section, enable the Linux bridge and layer-2 population " -"mechanisms:" -msgstr "" - -#: ../neutron-controller-install-option1.rst:218 -msgid "In the ``[ml2]`` section, enable the Linux bridge mechanism:" -msgstr "" - -# #-#-#-#-# neutron-controller-install-option1.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# neutron-controller-install-option2.pot (Installation Guide 0.1) #-#-#-#-# -#: ../neutron-controller-install-option1.rst:231 -#: ../neutron-controller-install-option2.rst:233 -msgid "In the ``[ml2]`` section, enable the port security extension driver:" -msgstr "" - -# #-#-#-#-# neutron-controller-install-option1.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# neutron-controller-install-option2.pot (Installation Guide 0.1) #-#-#-#-# -#: ../neutron-controller-install-option1.rst:239 -#: ../neutron-controller-install-option2.rst:241 -msgid "" -"In the ``[ml2_type_flat]`` section, configure the public flat provider " -"network:" -msgstr "" - -#: ../neutron-controller-install-option2.rst:250 -msgid "" -"In the ``[ml2_type_vxlan]`` section, configure the VXLAN network identifier " -"range for private networks:" -msgstr "" - -#: ../environment-dependencies.rst:300 ../environment-dependencies.rst:330 -msgid "" -"In the ``[mysqld]`` section, set the ``bind-address`` key to the management " -"IP address of the controller node to enable access by other nodes via the " -"management network:" -msgstr "" - -#: ../environment-dependencies.rst:311 ../environment-dependencies.rst:341 -msgid "" -"In the ``[mysqld]`` section, set the following keys to enable useful options " -"and the UTF-8 character set:" -msgstr "" - -#: ../neutron-controller-install.rst:211 -msgid "" -"In the ``[neutron]`` section, configure access parameters, enable the " -"metadata proxy, and configure the secret:" -msgstr "" - -#: ../neutron-compute-install.rst:185 -msgid "In the ``[neutron]`` section, configure access parameters:" -msgstr "" - -# #-#-#-#-# cinder-controller-node.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# cinder-storage-node.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# nova-compute-install.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# nova-controller-install.pot (Installation Guide 0.1) #-#-#-#-# -#: ../cinder-controller-node.rst:274 ../cinder-storage-node.rst:331 -#: ../nova-compute-install.rst:168 ../nova-compute-install.rst:178 -#: ../nova-controller-install.rst:289 ../nova-controller-install.rst:299 -#: ../nova-controller-install.rst:309 -msgid "In the ``[oslo_concurrency]`` section, configure the lock path:" -msgstr "" - -#: ../ceilometer-swift.rst:66 -msgid "In the ``[pipeline:main]`` section, add ``ceilometer``:" -msgstr "" - -# #-#-#-#-# swift-controller-node.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# swift-storage-node.pot (Installation Guide 0.1) #-#-#-#-# -#: ../swift-controller-node-include.txt:16 -#: ../swift-storage-node-include1.txt:21 ../swift-storage-node-include2.txt:21 -#: ../swift-storage-node-include3.txt:21 -msgid "In the ``[pipeline:main]`` section, enable the appropriate modules:" -msgstr "" - -# #-#-#-#-# ceilometer-controller-install.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# ceilometer-nova.pot (Installation Guide 0.1) #-#-#-#-# -#: ../ceilometer-controller-install.rst:422 ../ceilometer-nova.rst:38 -msgid "In the ``[publisher]`` section, configure the telemetry secret:" -msgstr "" - -#: ../keystone-install.rst:157 -msgid "In the ``[revoke]`` section, configure the SQL revocation driver:" -msgstr "" - -# #-#-#-#-# neutron-compute-install-option1.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# neutron-compute-install-option2.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# neutron-controller-install-option1.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# neutron-controller-install-option2.pot (Installation Guide 0.1) #-#-#-#-# -#: ../neutron-compute-install-option1.rst:33 -#: ../neutron-compute-install-option2.rst:41 -#: ../neutron-controller-install-option1.rst:283 -#: ../neutron-controller-install-option2.rst:302 -msgid "" -"In the ``[securitygroup]`` section, enable security groups, enable :term:" -"`ipset`, and configure the Linux bridge :term:`iptables` firewall driver:" -msgstr "" - -# #-#-#-#-# ceilometer-controller-install.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# ceilometer-nova.pot (Installation Guide 0.1) #-#-#-#-# -#: ../ceilometer-controller-install.rst:405 ../ceilometer-nova.rst:92 -msgid "" -"In the ``[service_credentials]`` section, configure service credentials:" -msgstr "" - -#: ../swift-finalize-installation.rst:39 ../swift-finalize-installation.rst:75 -msgid "" -"In the ``[storage-policy:0]`` section, configure the default storage policy:" -msgstr "" - -#: ../swift-finalize-installation.rst:22 ../swift-finalize-installation.rst:58 -msgid "" -"In the ``[swift-hash]`` section, configure the hash path prefix and suffix " -"for your environment." -msgstr "" - -#: ../keystone-install.rst:147 -msgid "" -"In the ``[token]`` section, configure the UUID token provider and Memcached " -"driver:" -msgstr "" - -#: ../nova-controller-install.rst:268 -msgid "" -"In the ``[vnc]`` section, configure the VNC proxy to use the management " -"interface IP address of the controller node:" -msgstr "" - -#: ../nova-compute-install.rst:133 -msgid "In the ``[vnc]`` section, enable and configure remote console access:" -msgstr "" - -# #-#-#-#-# neutron-compute-install-option1.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# neutron-controller-install-option1.pot (Installation Guide 0.1) #-#-#-#-# -#: ../neutron-compute-install-option1.rst:26 -#: ../neutron-controller-install-option1.rst:268 -msgid "In the ``[vxlan]`` section, disable VXLAN overlay networks:" -msgstr "" - -# #-#-#-#-# neutron-compute-install-option2.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# neutron-controller-install-option2.pot (Installation Guide 0.1) #-#-#-#-# -#: ../neutron-compute-install-option2.rst:26 -#: ../neutron-controller-install-option2.rst:279 -msgid "" -"In the ``[vxlan]`` section, enable VXLAN overlay networks, configure the IP " -"address of the physical network interface that handles overlay networks, and " -"enable layer-2 population:" -msgstr "" - -#: ../cinder-storage-node.rst:142 -msgid "" -"In the ``devices`` section, add a filter that accepts the :file:`/dev/sdb` " -"device and rejects all other devices::" -msgstr "" - -#: ../overview.rst:100 -msgid "" -"Increase security using methods such as firewalls, encryption, and service " -"policies." -msgstr "" - -# #-#-#-#-# dashboard-install.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# glance-install.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# keystone-install.pot (Installation Guide 0.1) #-#-#-#-# -#: ../dashboard-install.rst:3 ../glance-install.rst:2 -#: ../keystone-install.rst:2 -msgid "Install and configure" -msgstr "" - -# #-#-#-#-# cinder-storage-node.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# swift-storage-node.pot (Installation Guide 0.1) #-#-#-#-# -#: ../cinder-storage-node.rst:45 ../swift-storage-node.rst:64 -msgid "" -"Install and configure :term:`NTP` using the instructions in :ref:" -"`environment-ntp`." -msgstr "" - -#: ../cinder-storage-node.rst:176 -msgid "Install and configure Block Storage volume components" -msgstr "" - -#: ../heat-install.rst:3 -msgid "Install and configure Orchestration" -msgstr "" - -#: ../nova-compute-install.rst:2 -msgid "Install and configure a compute node" -msgstr "" - -#: ../cinder-storage-node.rst:3 -msgid "Install and configure a storage node" -msgstr "" - -# #-#-#-#-# glance-install.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# keystone-install.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# nova-compute-install.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# nova-controller-install.pot (Installation Guide 0.1) #-#-#-#-# -#: ../glance-install.rst:149 ../keystone-install.rst:53 -#: ../nova-compute-install.rst:25 ../nova-controller-install.rst:145 -msgid "Install and configure components" -msgstr "" - -#: ../neutron-compute-install.rst:2 -msgid "Install and configure compute node" +"Use the ``cinder-volume-usage-audit`` command to retrieve meters on demand. " +"For more information, see `Block Storage audit script setup to get " +"notifications `__." msgstr "" # #-#-#-#-# ceilometer-controller-install.pot (Installation Guide 0.1) #-#-#-#-# @@ -3175,55 +235,46 @@ msgstr "" msgid "Install and configure controller node" msgstr "" -#: ../swift-storage-node.rst:180 -msgid "Install and configure storage node components" -msgstr "" - -# #-#-#-#-# neutron-compute-install.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# neutron-controller-install-option2.pot (Installation Guide 0.1) #-#-#-#-# -#: ../neutron-compute-install.rst:52 -#: ../neutron-controller-install-option2.rst:57 -msgid "Install and configure the Networking components" -msgstr "" - -# #-#-#-#-# neutron-compute-install-option1.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# neutron-compute-install-option2.pot (Installation Guide 0.1) #-#-#-#-# -#: ../neutron-compute-install-option1.rst:4 -#: ../neutron-compute-install-option2.rst:4 -msgid "Install and configure the Networking components on a *compute* node." -msgstr "" - -# #-#-#-#-# neutron-controller-install-option1.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# neutron-controller-install-option2.pot (Installation Guide 0.1) #-#-#-#-# -#: ../neutron-controller-install-option1.rst:4 -#: ../neutron-controller-install-option2.rst:4 +#: ../ceilometer-controller-install.rst:5 msgid "" -"Install and configure the Networking components on the *controller* node." +"This section describes how to install and configure the Telemetry module, " +"code-named ceilometer, on the controller node. The Telemetry module uses " +"separate agents to collect measurements from each OpenStack service in your " +"environment." msgstr "" -#: ../keystone-install.rst:185 -msgid "Install and configure the components" +#: ../ceilometer-controller-install.rst:13 +msgid "" +"Before you install and configure Telemetry, you must install ``MongoDB``, " +"create a MongoDB database, service credentials, and API endpoint." msgstr "" -#: ../swift-controller-node.rst:3 -msgid "Install and configure the controller node" +#: ../ceilometer-controller-install.rst:18 +msgid "" +"Enable the Open Build Service repositories for MongoDB based on your " +"openSUSE or SLES version:" msgstr "" -#: ../environment-dependencies.rst:259 -msgid "Install and configure the database server" +# #-#-#-#-# ceilometer-controller-install.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# environment-ntp-controller.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# environment-ntp-other.pot (Installation Guide 0.1) #-#-#-#-# +#: ../ceilometer-controller-install.rst:21 +#: ../environment-ntp-controller.rst:25 ../environment-ntp-other.rst:25 +msgid "On openSUSE:" msgstr "" -#: ../neutron-controller-install-option1.rst:55 -msgid "Install and configure the networking components" +# #-#-#-#-# ceilometer-controller-install.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# environment-ntp-controller.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# environment-ntp-other.pot (Installation Guide 0.1) #-#-#-#-# +#: ../ceilometer-controller-install.rst:27 +#: ../environment-ntp-controller.rst:33 ../environment-ntp-other.rst:33 +msgid "On SLES:" msgstr "" -#: ../swift-storage-node.rst:3 -msgid "Install and configure the storage nodes" -msgstr "" - -#: ../cinder-storage-node.rst:57 ../cinder-storage-node.rst:68 -#: ../cinder-storage-node.rst:99 -msgid "Install the LVM packages:" +#: ../ceilometer-controller-install.rst:35 +msgid "" +"The packages are signed by GPG key ``562111AC05905EA8``. You should verify " +"the fingerprint of the imported GPG key before using it." msgstr "" #: ../ceilometer-controller-install.rst:46 @@ -3232,46 +283,117 @@ msgstr "" msgid "Install the MongoDB package:" msgstr "" -# #-#-#-#-# environment-ntp-controller.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# environment-ntp-other.pot (Installation Guide 0.1) #-#-#-#-# -#: ../environment-ntp-controller.rst:7 ../environment-ntp-other.rst:7 -msgid "Install the NTP service" -msgstr "" - -# #-#-#-#-# neutron-compute-install.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# neutron-controller-install-option2.pot (Installation Guide 0.1) #-#-#-#-# -#: ../neutron-compute-install.rst:29 -#: ../neutron-controller-install-option2.rst:28 -msgid "Install the Networking components" -msgstr "" - -#: ../environment-dependencies.rst:223 -msgid "Install the OpenStack client" -msgstr "" - -#: ../environment-dependencies.rst:25 -msgid "Install the Ubuntu Cloud archive keyring and repository:" -msgstr "" - -#: ../ceilometer-swift.rst:111 -msgid "Install the ``ceilometermiddleware`` package:" -msgstr "" - -#: ../environment-dependencies.rst:67 +#: ../ceilometer-controller-install.rst:70 +#: ../ceilometer-controller-install.rst:142 msgid "" -"Install the ``rdo-release-liberty`` package to enable the RDO repository:" +"Edit the :file:`/etc/mongodb.conf` file and complete the following actions:" msgstr "" -#: ../environment-dependencies.rst:414 -msgid "Install the message queue service" +#: ../ceilometer-controller-install.rst:73 +#: ../ceilometer-controller-install.rst:110 +#: ../ceilometer-controller-install.rst:145 +msgid "" +"Configure the ``bind_ip`` key to use the management interface IP address of " +"the controller node." msgstr "" -#: ../neutron-controller-install-option1.rst:26 -msgid "Install the networking components" +#: ../ceilometer-controller-install.rst:81 +#: ../ceilometer-controller-install.rst:118 +#: ../ceilometer-controller-install.rst:153 +msgid "" +"By default, MongoDB creates several 1 GB journal files in the :file:`/var/" +"lib/mongodb/journal` directory. If you want to reduce the size of each " +"journal file to 128 MB and limit total journal space consumption to 512 MB, " +"assert the ``smallfiles`` key:" msgstr "" -#: ../environment-dependencies.rst:228 ../environment-dependencies.rst:416 -msgid "Install the package:" +#: ../ceilometer-controller-install.rst:92 +#: ../ceilometer-controller-install.rst:129 +#: ../ceilometer-controller-install.rst:173 +msgid "" +"You can also disable journaling. For more information, see the `MongoDB " +"manual `__." +msgstr "" + +#: ../ceilometer-controller-install.rst:95 +#: ../ceilometer-controller-install.rst:132 +msgid "" +"Start the MongoDB services and configure them to start when the system boots:" +msgstr "" + +#: ../ceilometer-controller-install.rst:107 +msgid "" +"Edit the :file:`/etc/mongod.conf` file and complete the following actions:" +msgstr "" + +#: ../ceilometer-controller-install.rst:164 +msgid "" +"If you change the journaling configuration, stop the MongoDB service, remove " +"the initial journal files, and start the service:" +msgstr "" + +#: ../ceilometer-controller-install.rst:178 +#: ../ceilometer-controller-install.rst:205 +msgid "Create the ``ceilometer`` database:" +msgstr "" + +#: ../ceilometer-controller-install.rst:201 +#: ../ceilometer-controller-install.rst:219 +msgid "Replace ``CEILOMETER_DBPASS`` with a suitable password." +msgstr "" + +# #-#-#-#-# ceilometer-controller-install.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# ceilometer-verify.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# cinder-controller-node.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# cinder-verify.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# glance-install.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# glance-verify.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# heat-install.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# neutron-controller-install.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# neutron-verify.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# nova-controller-install.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# nova-verify.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# swift-controller-node.pot (Installation Guide 0.1) #-#-#-#-# +#: ../ceilometer-controller-install.rst:222 ../ceilometer-verify.rst:11 +#: ../cinder-controller-node.rst:44 ../cinder-verify.rst:20 +#: ../glance-install.rst:44 ../glance-verify.rst:23 ../heat-install.rst:40 +#: ../heat-install.rst:397 ../neutron-controller-install.rst:37 +#: ../neutron-verify.rst:4 ../nova-controller-install.rst:41 +#: ../nova-verify.rst:10 ../swift-controller-node.rst:29 +msgid "" +"Source the ``admin`` credentials to gain access to admin-only CLI commands:" +msgstr "" + +# #-#-#-#-# ceilometer-controller-install.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# cinder-controller-node.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# glance-install.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# heat-install.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# neutron-controller-install.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# nova-controller-install.pot (Installation Guide 0.1) #-#-#-#-# +#: ../ceilometer-controller-install.rst:229 ../cinder-controller-node.rst:51 +#: ../glance-install.rst:51 ../heat-install.rst:47 +#: ../neutron-controller-install.rst:44 ../nova-controller-install.rst:48 +msgid "To create the service credentials, complete these steps:" +msgstr "" + +#: ../ceilometer-controller-install.rst:231 +msgid "Create the ``ceilometer`` user:" +msgstr "" + +#: ../ceilometer-controller-install.rst:248 +msgid "Add the ``admin`` role to the ``ceilometer`` user." +msgstr "" + +#: ../ceilometer-controller-install.rst:260 +msgid "Create the ``ceilometer`` service entity:" +msgstr "" + +#: ../ceilometer-controller-install.rst:276 +msgid "Create the Telemetry module API endpoint:" +msgstr "" + +#: ../ceilometer-controller-install.rst:329 +msgid "To install and configure the Telemetry module components" msgstr "" # #-#-#-#-# ceilometer-controller-install.pot (Installation Guide 0.1) #-#-#-#-# @@ -3279,19 +401,22 @@ msgstr "" # #-#-#-#-# cinder-controller-node.pot (Installation Guide 0.1) #-#-#-#-# # #-#-#-#-# cinder-storage-node.pot (Installation Guide 0.1) #-#-#-#-# # #-#-#-#-# environment-dependencies.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# environment-ntp-controller.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# environment-ntp-other.pot (Installation Guide 0.1) #-#-#-#-# # #-#-#-#-# glance-install.pot (Installation Guide 0.1) #-#-#-#-# # #-#-#-#-# nova-compute-install.pot (Installation Guide 0.1) #-#-#-#-# # #-#-#-#-# nova-controller-install.pot (Installation Guide 0.1) #-#-#-#-# # #-#-#-#-# swift-controller-node.pot (Installation Guide 0.1) #-#-#-#-# # #-#-#-#-# swift-storage-node.pot (Installation Guide 0.1) #-#-#-#-# -#: ../ceilometer-controller-install.rst:304 -#: ../ceilometer-controller-install.rst:317 -#: ../ceilometer-controller-install.rst:328 ../ceilometer-nova.rst:13 +#: ../ceilometer-controller-install.rst:333 +#: ../ceilometer-controller-install.rst:346 +#: ../ceilometer-controller-install.rst:357 ../ceilometer-nova.rst:13 #: ../ceilometer-nova.rst:21 ../ceilometer-nova.rst:29 #: ../cinder-controller-node.rst:167 ../cinder-controller-node.rst:175 #: ../cinder-controller-node.rst:183 ../cinder-storage-node.rst:180 #: ../cinder-storage-node.rst:188 ../cinder-storage-node.rst:200 -#: ../environment-dependencies.rst:261 ../glance-install.rst:157 +#: ../environment-dependencies.rst:261 ../environment-ntp-controller.rst:9 +#: ../environment-ntp-other.rst:9 ../glance-install.rst:157 #: ../glance-install.rst:165 ../glance-install.rst:176 #: ../glance-install.rst:332 ../nova-compute-install.rst:31 #: ../nova-compute-install.rst:39 ../nova-compute-install.rst:47 @@ -3301,279 +426,214 @@ msgstr "" msgid "Install the packages:" msgstr "" -#: ../dashboard-install.rst:25 ../dashboard-install.rst:32 -#: ../dashboard-install.rst:39 ../dashboard-install.rst:45 -msgid "Install the packages::" +#: ../ceilometer-controller-install.rst:366 +msgid "Generate a random value to use as the telemetry secret:" msgstr "" -#: ../swift-storage-node.rst:67 -msgid "Install the supporting utility packages:" -msgstr "" - -#: ../swift-finalize-installation.rst:37 ../swift-finalize-installation.rst:73 -msgid "Keep these values secret and do not change or lose them." -msgstr "" - -#: ../keystone-install.rst:231 +# #-#-#-#-# ceilometer-controller-install.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# ceilometer-nova.pot (Installation Guide 0.1) #-#-#-#-# +#: ../ceilometer-controller-install.rst:372 ../ceilometer-nova.rst:35 msgid "" -"Later on, the package will configure the below directive with the value you " -"entered:" -msgstr "" - -#: ../environment-dependencies.rst:138 -msgid "Later you can use the following command to install a package:" -msgstr "" - -#: ../launch-instance.rst:5 ../launch-instance.rst:107 -msgid "Launch an instance" -msgstr "" - -#: ../launch-instance-private.rst:4 -msgid "Launch an instance on the private network" -msgstr "" - -#: ../launch-instance-public.rst:4 -msgid "Launch an instance on the public network" -msgstr "" - -#: ../launch-instance-public.rst:81 -msgid "Launch the instance" -msgstr "" - -# #-#-#-#-# launch-instance-private.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# launch-instance-public.pot (Installation Guide 0.1) #-#-#-#-# -#: ../launch-instance-private.rst:77 ../launch-instance-public.rst:83 -msgid "Launch the instance:" -msgstr "" - -#: ../nova-verify.rst:39 -msgid "" -"List API endpoints in the Identity service to verify connectivity with the " -"Identity service:" -msgstr "" - -# #-#-#-#-# neutron-verify-option1.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# neutron-verify-option2.pot (Installation Guide 0.1) #-#-#-#-# -#: ../neutron-verify-option1.rst:4 ../neutron-verify-option2.rst:4 -msgid "List agents to verify successful launch of the neutron agents:" -msgstr "" - -# #-#-#-#-# launch-instance-private.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# launch-instance-public.pot (Installation Guide 0.1) #-#-#-#-# -#: ../launch-instance-private.rst:15 ../launch-instance-public.rst:15 -msgid "List available flavors:" -msgstr "" - -# #-#-#-#-# launch-instance-private.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# launch-instance-public.pot (Installation Guide 0.1) #-#-#-#-# -#: ../launch-instance-private.rst:36 ../launch-instance-public.rst:36 -msgid "List available images:" -msgstr "" - -#: ../ceilometer-verify.rst:39 -msgid "" -"List available meters again to validate detection of the image download:" -msgstr "" - -#: ../ceilometer-verify.rst:18 -msgid "List available meters:" -msgstr "" - -# #-#-#-#-# launch-instance-private.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# launch-instance-public.pot (Installation Guide 0.1) #-#-#-#-# -#: ../launch-instance-private.rst:49 ../launch-instance-public.rst:49 -msgid "List available networks:" -msgstr "" - -# #-#-#-#-# launch-instance-private.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# launch-instance-public.pot (Installation Guide 0.1) #-#-#-#-# -#: ../launch-instance-private.rst:64 ../launch-instance-public.rst:67 -msgid "List available security groups:" -msgstr "" - -#: ../swift-verify.rst:44 -msgid "List containers:" -msgstr "" - -#: ../nova-verify.rst:133 -msgid "" -"List images in the Image service catalog to verify connectivity with the " -"Image service:" -msgstr "" - -#: ../neutron-verify.rst:11 -msgid "" -"List loaded extensions to verify successful launch of the ``neutron-server`` " -"process:" -msgstr "" - -#: ../launch-instance-networks-private.rst:202 -msgid "" -"List network namespaces. You should see one ``qrouter`` namespace and two " -"``qdhcp`` namespaces." -msgstr "" - -#: ../launch-instance-networks-private.rst:212 -msgid "" -"List ports on the router to determine the gateway IP address on the public " -"provider network:" -msgstr "" - -#: ../nova-verify.rst:17 -msgid "" -"List service components to verify successful launch and registration of each " -"process:" -msgstr "" - -#: ../cinder-verify.rst:27 -msgid "List service components to verify successful launch of each process:" -msgstr "" - -#: ../launch-instance-cinder.rst:82 -msgid "List volumes:" -msgstr "" - -#: ../keystone-openrc.rst:59 -msgid "" -"Load the ``admin-openrc.sh`` file to populate environment variables with the " -"location of the Identity service and the ``admin`` project and user " -"credentials:" -msgstr "" - -#: ../environment-networking.rst:62 -msgid "Management on 10.0.0.0/24 with gateway 10.0.0.1" -msgstr "" - -#: ../overview.rst:34 -msgid "" -"Manages the lifecycle of compute instances in an OpenStack environment. " -"Responsibilities include spawning, scheduling and decommissioning of virtual " -"machines on demand." -msgstr "" - -#: ../debconf/debconf-dbconfig-common.rst:7 -msgid "" -"Many of the OpenStack services need to be configured to access a database. " -"These are configured through a DSN (Database Source Name) directive as " -"follows:" -msgstr "" - -#: ../environment.rst:54 -msgid "" -"Many users build their test environment on a :term:`virtual machine (VM)`. " -"The primary benefits of VMs include the following:" -msgstr "" - -#: ../environment-dependencies.rst:400 -msgid "Message queue" -msgstr "" - -#: ../ceilometer-nova.rst:150 -msgid "" -"Messages arrive in a specific format which includes: Message ID, Publisher " -"ID, Event type, Timestamp, Priority, and Payload. See the `Notification " -"System information `__ for an example " -"message format." -msgstr "" - -#: ../overview.rst:78 -msgid "" -"Monitors and meters the OpenStack cloud for billing, benchmarking, " -"scalability, and statistical purposes." -msgstr "" - -#: ../environment-dependencies.rst:251 -msgid "" -"Most OpenStack services use an SQL database to store information. The " -"database typically runs on the controller node. The procedures in this guide " -"use MariaDB or MySQL depending on the distribution. OpenStack services also " -"support other SQL databases including `PostgreSQL `__." -msgstr "" - -#: ../launch-instance.rst:41 -msgid "" -"Most cloud images support :term:`public key authentication` rather than " -"conventional password authentication. Before launching an instance, you must " -"add a public key to the Compute service." -msgstr "" - -#: ../swift-storage-node.rst:109 -msgid "Mount the devices:" -msgstr "" - -#: ../app_reserved_uids.rst:19 -msgid "Name" -msgstr "" - -#: ../environment-networking.rst:82 -msgid "" -"Network interface names vary by distribution. Traditionally, interfaces use " -"\"eth\" followed by a sequential number. To cover all variations, this guide " -"simply refers to the first interface as the interface with the lowest number " -"and the second interface as the interface with the highest number." +"Edit the :file:`/etc/ceilometer/ceilometer.conf` file and complete the " +"following actions:" msgstr "" +# #-#-#-#-# ceilometer-controller-install.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# cinder-controller-node.pot (Installation Guide 0.1) #-#-#-#-# # #-#-#-#-# cinder-storage-node.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# environment-networking.pot (Installation Guide 0.1) #-#-#-#-# -#: ../cinder-storage-node.rst:30 ../environment-networking.rst:113 -#: ../environment-networking.rst:156 -msgid "Network mask: 255.255.255.0 (or /24)" -msgstr "" - -#: ../swift-storage-node.rst:32 ../swift-storage-node.rst:42 -msgid "Network mask: ``255.255.255.0`` (or ``/24``)" -msgstr "" - -#: ../overview.rst:190 -msgid "Networking" -msgstr "" - -#: ../neutron-concepts.rst:2 -msgid "Networking (neutron) concepts" -msgstr "" - -# #-#-#-#-# neutron-compute-install-option1.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# glance-install.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# heat-install.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# keystone-install.pot (Installation Guide 0.1) #-#-#-#-# # #-#-#-#-# neutron-controller-install-option1.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# neutron-verify-option1.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# overview.pot (Installation Guide 0.1) #-#-#-#-# -#: ../neutron-compute-install-option1.rst:2 -#: ../neutron-controller-install-option1.rst:2 ../neutron-verify-option1.rst:2 -#: ../overview.rst:197 -msgid "Networking Option 1: Provider networks" -msgstr "" - -# #-#-#-#-# neutron-compute-install-option2.pot (Installation Guide 0.1) #-#-#-#-# # #-#-#-#-# neutron-controller-install-option2.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# neutron-verify-option2.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# overview.pot (Installation Guide 0.1) #-#-#-#-# -#: ../neutron-compute-install-option2.rst:2 -#: ../neutron-controller-install-option2.rst:2 ../neutron-verify-option2.rst:2 -#: ../overview.rst:221 -msgid "Networking Option 2: Self-service networks" +#: ../ceilometer-controller-install.rst:375 ../cinder-controller-node.rst:208 +#: ../cinder-storage-node.rst:209 ../glance-install.rst:187 +#: ../glance-install.rst:261 ../heat-install.rst:301 +#: ../keystone-install.rst:129 ../neutron-controller-install-option1.rst:94 +#: ../neutron-controller-install-option2.rst:90 +msgid "In the ``[database]`` section, configure database access:" msgstr "" -#: ../overview.rst:118 +#: ../ceilometer-controller-install.rst:384 msgid "" -"Networking agents reside on the controller node instead of one or more " -"dedicated network nodes." +"Replace ``CEILOMETER_DBPASS`` with the password you chose for the Telemetry " +"module database. You must escape special characters such as ':', '/', '+', " +"and '@' in the connection string in accordance with RFC2396." msgstr "" -#: ../neutron-concepts.rst:49 +# #-#-#-#-# ceilometer-controller-install.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# ceilometer-nova.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# cinder-controller-node.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# cinder-storage-node.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# heat-install.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# nova-controller-install.pot (Installation Guide 0.1) #-#-#-#-# +#: ../ceilometer-controller-install.rst:389 ../ceilometer-nova.rst:50 +#: ../cinder-controller-node.rst:219 ../cinder-storage-node.rst:220 +#: ../heat-install.rst:313 ../nova-controller-install.rst:195 msgid "" -"Networking also supports *security groups*. Security groups enable " -"administrators to define firewall rules in groups. A VM can belong to one or " -"more security groups, and Networking applies the rules in those security " -"groups to block or unblock ports, port ranges, or traffic types for that VM." +"In the ``[DEFAULT]`` and ``[oslo_messaging_rabbit]`` sections, configure " +"``RabbitMQ`` message queue access:" msgstr "" -#: ../neutron-concepts.rst:12 +# #-#-#-#-# ceilometer-controller-install.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# ceilometer-glance.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# ceilometer-nova.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# ceilometer-swift.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# cinder-controller-node.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# cinder-storage-node.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# heat-install.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# nova-compute-install.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# nova-controller-install.pot (Installation Guide 0.1) #-#-#-#-# +#: ../ceilometer-controller-install.rst:405 ../ceilometer-glance.rst:26 +#: ../ceilometer-nova.rst:66 ../ceilometer-swift.rst:89 +#: ../cinder-controller-node.rst:234 ../cinder-storage-node.rst:235 +#: ../heat-install.rst:329 ../nova-compute-install.rst:71 +#: ../nova-controller-install.rst:210 msgid "" -"Networking provides the networks, subnets, and routers object abstractions. " -"Each abstraction has functionality that mimics its physical counterpart: " -"networks contain subnets, and routers route traffic between different subnet " -"and networks." +"Replace ``RABBIT_PASS`` with the password you chose for the ``openstack`` " +"account in ``RabbitMQ``." +msgstr "" + +# #-#-#-#-# ceilometer-controller-install.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# cinder-controller-node.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# cinder-storage-node.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# neutron-compute-install.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# neutron-controller-install-option1.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# neutron-controller-install-option2.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# nova-compute-install.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# nova-controller-install.pot (Installation Guide 0.1) #-#-#-#-# +#: ../ceilometer-controller-install.rst:408 ../cinder-controller-node.rst:237 +#: ../cinder-storage-node.rst:238 ../neutron-compute-install.rst:106 +#: ../neutron-controller-install-option1.rst:133 +#: ../neutron-controller-install-option2.rst:130 +#: ../nova-compute-install.rst:74 ../nova-controller-install.rst:213 +msgid "" +"In the ``[DEFAULT]`` and ``[keystone_authtoken]`` sections, configure " +"Identity service access:" +msgstr "" + +# #-#-#-#-# ceilometer-controller-install.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# ceilometer-nova.pot (Installation Guide 0.1) #-#-#-#-# +#: ../ceilometer-controller-install.rst:426 +#: ../ceilometer-controller-install.rst:448 ../ceilometer-nova.rst:107 +msgid "" +"Replace ``CEILOMETER_PASS`` with the password you chose for the " +"``ceilometer`` user in the Identity service." +msgstr "" + +# #-#-#-#-# ceilometer-controller-install.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# ceilometer-nova.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# heat-install.pot (Installation Guide 0.1) #-#-#-#-# +#: ../ceilometer-controller-install.rst:431 ../ceilometer-nova.rst:88 +#: ../heat-install.rst:355 +msgid "" +"Comment out any ``auth_host``, ``auth_port``, and ``auth_protocol`` options " +"because the ``identity_uri`` option replaces them." +msgstr "" + +# #-#-#-#-# ceilometer-controller-install.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# ceilometer-nova.pot (Installation Guide 0.1) #-#-#-#-# +#: ../ceilometer-controller-install.rst:434 ../ceilometer-nova.rst:92 +msgid "" +"In the ``[service_credentials]`` section, configure service credentials:" +msgstr "" + +# #-#-#-#-# ceilometer-controller-install.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# ceilometer-nova.pot (Installation Guide 0.1) #-#-#-#-# +#: ../ceilometer-controller-install.rst:451 ../ceilometer-nova.rst:38 +msgid "In the ``[publisher]`` section, configure the telemetry secret:" +msgstr "" + +#: ../ceilometer-controller-install.rst:460 +msgid "" +"Replace TELEMETRY_SECRET with the telemetry secret that you generated in a " +"previous step." +msgstr "" + +#: ../ceilometer-controller-install.rst:465 +msgid "In the ``[collector]`` section, configure the dispatcher:" +msgstr "" + +# #-#-#-#-# ceilometer-controller-install.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# ceilometer-nova.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# cinder-controller-node.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# cinder-storage-node.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# glance-install.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# heat-install.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# keystone-install.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# neutron-compute-install.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# neutron-controller-install-option1.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# neutron-controller-install-option2.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# neutron-controller-install.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# nova-compute-install.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# nova-controller-install.pot (Installation Guide 0.1) #-#-#-#-# +#: ../ceilometer-controller-install.rst:474 +#: ../ceilometer-controller-install.rst:486 ../ceilometer-nova.rst:110 +#: ../cinder-controller-node.rst:282 ../cinder-storage-node.rst:339 +#: ../glance-install.rst:249 ../glance-install.rst:313 ../heat-install.rst:385 +#: ../keystone-install.rst:165 ../neutron-compute-install.rst:134 +#: ../neutron-controller-install-option1.rst:186 +#: ../neutron-controller-install-option1.rst:318 +#: ../neutron-controller-install-option2.rst:183 +#: ../neutron-controller-install-option2.rst:341 +#: ../neutron-controller-install-option2.rst:370 +#: ../neutron-controller-install.rst:208 ../nova-compute-install.rst:186 +#: ../nova-controller-install.rst:325 +msgid "" +"(Optional) To assist with troubleshooting, enable verbose logging in the " +"``[DEFAULT]`` section:" +msgstr "" + +# #-#-#-#-# ceilometer-controller-install.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# ceilometer-nova.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# cinder-controller-node.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# cinder-storage-node.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# dashboard-install.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# environment-dependencies.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# heat-install.pot (Installation Guide 0.1) #-#-#-#-# +#: ../ceilometer-controller-install.rst:497 ../ceilometer-nova.rst:170 +#: ../cinder-controller-node.rst:298 ../cinder-storage-node.rst:349 +#: ../dashboard-install.rst:133 ../environment-dependencies.rst:355 +#: ../heat-install.rst:448 +msgid "To finalize installation" +msgstr "" + +#: ../ceilometer-controller-install.rst:500 +#: ../ceilometer-controller-install.rst:520 +msgid "" +"Start the Telemetry services and configure them to start when the system " +"boots:" +msgstr "" + +#: ../ceilometer-controller-install.rst:540 +msgid "Restart the Telemetry services:" +msgstr "" + +#: ../ceilometer-glance.rst:3 +msgid "Configure the Image service" +msgstr "" + +#: ../ceilometer-glance.rst:5 +msgid "" +"To retrieve image-oriented events and samples, configure the Image service " +"to send notifications to the message bus. Perform these steps on the " +"controller node." +msgstr "" + +#: ../ceilometer-glance.rst:9 +msgid "" +"Edit the :file:`/etc/glance/glance-api.conf` and :file:`/etc/glance/glance-" +"registry.conf` files and complete the following actions:" +msgstr "" + +#: ../ceilometer-glance.rst:13 +msgid "" +"In the ``[DEFAULT]`` section, configure notifications and RabbitMQ message " +"broker access:" +msgstr "" + +#: ../ceilometer-glance.rst:31 ../ceilometer-glance.rst:39 +msgid "Restart the Image service:" msgstr "" # #-#-#-#-# ceilometer-next-steps.pot (Installation Guide 0.1) #-#-#-#-# @@ -3588,646 +648,35 @@ msgstr "" msgid "Next steps" msgstr "" -#: ../launch-instance-networks-private.rst:68 +#: ../ceilometer-next-steps.rst:5 msgid "" -"Non-privileged users typically cannot supply additional parameters to this " -"command. The service automatically chooses paramters using information from " -"the following files:" +"Your OpenStack environment now includes Telemetry. You can :ref:`launch-" +"instance` or add more services to your environment." msgstr "" -#: ../ceilometer-nova.rst:156 +#: ../ceilometer-nova.rst:3 +msgid "Configure the Compute service" +msgstr "" + +#: ../ceilometer-nova.rst:5 msgid "" -"Notification messages are placed on the OpenStack messaging system, which " -"recruits AMQP to send information when an event triggers alerts." +"Telemetry uses a combination of notifications and an agent to collect " +"Compute meters. Perform these steps on each compute node." msgstr "" -#: ../ceilometer-nova.rst:143 +#: ../ceilometer-nova.rst:9 +msgid "To install and configure the agent" +msgstr "" + +#: ../ceilometer-nova.rst:47 msgid "" -"Notifications in real-time allow administrars to observe and resolve " -"emergencies when the cloud environment experiences errors or faults." +"Replace ``TELEMETRY_SECRET`` with the telemetry secret you chose for the " +"Telemetry module." msgstr "" -#: ../overview.rst:176 -msgid "Object Storage" -msgstr "" - -#: ../swift-initial-rings.rst:175 -msgid "Object ring" -msgstr "" - -# #-#-#-#-# launch-instance-private.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# launch-instance-public.pot (Installation Guide 0.1) #-#-#-#-# -#: ../launch-instance-private.rst:134 ../launch-instance-public.rst:145 +#: ../ceilometer-nova.rst:69 msgid "" -"Obtain a :term:`Virtual Network Computing (VNC)` session URL for your " -"instance and access it from a web browser:" -msgstr "" - -#: ../swift-finalize-installation.rst:11 -msgid "" -"Obtain the :file:`/etc/swift/swift.conf` file from the Object Storage source " -"repository:" -msgstr "" - -#: ../swift-storage-node.rst:212 -msgid "" -"Obtain the accounting, container, object, container-reconciler, and object-" -"expirer service configuration files from the Object Storage source " -"repository:" -msgstr "" - -#: ../swift-controller-node.rst:142 ../swift-controller-node.rst:153 -msgid "" -"Obtain the proxy service configuration file from the Object Storage source " -"repository:" -msgstr "" - -#: ../dashboard-install.rst:142 -msgid "" -"On RHEL and CentOS, configure SELinux to permit the web server to connect to " -"OpenStack services::" -msgstr "" - -#: ../environment-dependencies.rst:39 -msgid "" -"On RHEL and CentOS, enable the `EPEL `_ " -"repository:" -msgstr "" - -#: ../environment-dependencies.rst:50 -msgid "On RHEL, enable additional repositories using the subscription manager:" -msgstr "" - -# #-#-#-#-# ceilometer-controller-install.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# environment-ntp-controller.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# environment-ntp-other.pot (Installation Guide 0.1) #-#-#-#-# -#: ../ceilometer-controller-install.rst:27 -#: ../environment-ntp-controller.rst:31 ../environment-ntp-other.rst:31 -msgid "On SLES:" -msgstr "" - -#: ../environment-dependencies.rst:128 -msgid "" -"On all nodes, adding the Debian 8 (Jessie) backport repository to the source " -"list:" -msgstr "" - -#: ../swift-finalize-installation.rst:91 -#: ../swift-finalize-installation.rst:119 -#: ../swift-finalize-installation.rst:154 -msgid "On all nodes, ensure proper ownership of the configuration directory:" -msgstr "" - -# #-#-#-#-# ceilometer-controller-install.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# environment-ntp-controller.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# environment-ntp-other.pot (Installation Guide 0.1) #-#-#-#-# -#: ../ceilometer-controller-install.rst:21 -#: ../environment-ntp-controller.rst:23 ../environment-ntp-other.rst:23 -msgid "On openSUSE:" -msgstr "" - -#: ../swift-finalize-installation.rst:97 -msgid "" -"On the controller node and any other nodes running the proxy service, " -"restart the Object Storage proxy service including its dependencies:" -msgstr "" - -#: ../swift-finalize-installation.rst:125 -#: ../swift-finalize-installation.rst:160 -msgid "" -"On the controller node and any other nodes running the proxy service, start " -"the Object Storage proxy service including its dependencies and configure " -"them to start when the system boots:" -msgstr "" - -# #-#-#-#-# launch-instance-networks-private.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# launch-instance-networks-public.pot (Installation Guide 0.1) #-#-#-#-# -#: ../launch-instance-networks-private.rst:136 -#: ../launch-instance-networks-private.rst:195 -#: ../launch-instance-networks-public.rst:33 -msgid "" -"On the controller node, source the ``admin`` credentials to gain access to " -"admin-only CLI commands:" -msgstr "" - -#: ../launch-instance-networks-private.rst:40 -msgid "" -"On the controller node, source the ``demo`` credentials to gain access to " -"user-only CLI commands:" -msgstr "" - -#: ../swift-finalize-installation.rst:134 -#: ../swift-finalize-installation.rst:169 -msgid "" -"On the storage nodes, start the Object Storage services and configure them " -"to start when the system boots:" -msgstr "" - -#: ../swift-finalize-installation.rst:105 -msgid "On the storage nodes, start the Object Storage services:" -msgstr "" - -#: ../environment.rst:58 -msgid "" -"One physical server can support multiple nodes, each with almost any number " -"of network interfaces." -msgstr "" - -#: ../cinder-storage-node.rst:131 -msgid "" -"Only instances can access Block Storage volumes. However, the underlying " -"operating system manages the devices associated with the volumes. By " -"default, the LVM volume scanning tool scans the :file:`/dev` directory for " -"block storage devices that contain volumes. If projects use LVM on their " -"volumes, the scanning tool detects these volumes and attempts to cache them " -"which can cause a variety of problems with both the underlying operating " -"system and project volumes. You must reconfigure LVM to scan only the " -"devices that contain the ``cinder-volume`` volume group. Edit the :file:`/" -"etc/lvm/lvm.conf` file and complete the following actions:" -msgstr "" - -#: ../index-debian.rst:3 ../index-debian.rst:31 -msgid "OpenStack Installation Guide for Debian" -msgstr "" - -#: ../index-debian.rst:13 -msgid "" -"OpenStack Installation Guide for Red Hat Enterprise Linux, CentOS, and Fedora" -msgstr "" - -#: ../index-debian.rst:25 -msgid "OpenStack Installation Guide for Ubuntu" -msgstr "" - -#: ../index-debian.rst:19 -msgid "OpenStack Installation Guide for openSUSE and SUSE Linux Enterprise" -msgstr "" - -#: ../neutron-concepts.rst:4 -msgid "" -"OpenStack Networking (neutron) manages all networking facets for the Virtual " -"Networking Infrastructure (VNI) and the access layer aspects of the Physical " -"Networking Infrastructure (PNI) in your OpenStack environment. OpenStack " -"Networking enables tenants to create advanced virtual network topologies " -"which may include services such as a :term:`firewall`, a :term:`load " -"balancer`, and a :term:`virtual private network (VPN)`." -msgstr "" - -#: ../environment.rst:152 -msgid "" -"OpenStack and supporting services require administrative privileges during " -"installation and operation. In some cases, services perform modifications to " -"the host that can interfere with deployment automation tools such as " -"Ansible, Chef, and Puppet. For example, some OpenStack services add a root " -"wrapper to ``sudo`` that can interfere with security policies. See the " -"`Cloud Administrator Guide `__ for more information." -msgstr "" - -#: ../app_reserved_uids.rst:23 -msgid "OpenStack ceilometer daemons" -msgstr "" - -#: ../app_reserved_uids.rst:32 -msgid "OpenStack cinder daemons" -msgstr "" - -# #-#-#-#-# glance-verify.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# keystone-services.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# keystone-users.pot (Installation Guide 0.1) #-#-#-#-# -#: ../glance-verify.rst:81 ../keystone-services.rst:99 -#: ../keystone-users.rst:36 -msgid "" -"OpenStack generates IDs dynamically, so you will see different values in the " -"example command output." -msgstr "" - -#: ../app_reserved_uids.rst:41 -msgid "OpenStack glance daemons" -msgstr "" - -#: ../app_reserved_uids.rst:50 -msgid "OpenStack heat daemons" -msgstr "" - -#: ../app_reserved_uids.rst:59 -msgid "OpenStack keystone daemons" -msgstr "" - -#: ../app_reserved_uids.rst:68 -msgid "OpenStack neutron daemons" -msgstr "" - -#: ../app_reserved_uids.rst:77 -msgid "OpenStack nova daemons" -msgstr "" - -#: ../environment-dependencies.rst:9 -msgid "OpenStack packages" -msgstr "" - -#: ../overview.rst:10 -msgid "" -"OpenStack provides an :term:`Infrastructure-as-a-Service (IaaS)` " -"solution through a variety of complemental services. Each service offers an :" -"term:`application programming interface (API)` that facilitates this " -"integration." -msgstr "" - -#: ../app_reserved_uids.rst:5 -msgid "" -"OpenStack reserves certain user IDs to run specific services and own " -"specific files. These user IDs are set up according to the distribution " -"packages. The following table gives an overview." -msgstr "" - -#: ../environment-dependencies.rst:6 -msgid "OpenStack service dependencies" -msgstr "" - -#: ../environment.rst:82 -msgid "" -"OpenStack services support various security methods including password, " -"policy, and encryption. Additionally, supporting services including the " -"database server and message broker support at least password security." -msgstr "" - -#: ../app_reserved_uids.rst:86 -msgid "OpenStack swift daemons" -msgstr "" - -#: ../app_reserved_uids.rst:95 -msgid "OpenStack trove daemons" -msgstr "" - -#: ../environment-dependencies.rst:402 -msgid "" -"OpenStack uses a :term:`message queue` to coordinate operations and status " -"information among services. The message queue service typically runs on the " -"controller node. OpenStack supports several message queue services including " -"`RabbitMQ `__, `Qpid `__, " -"and `ZeroMQ `__. However, most distributions that package " -"OpenStack support a particular message queue service. This guide implements " -"the RabbitMQ message queue service because most distributions support it. If " -"you prefer to implement a different message queue service, consult the " -"documentation associated with it." -msgstr "" - -#: ../keystone-services.rst:106 -msgid "" -"OpenStack uses three API endpoint variants for each service: admin, " -"internal, and public. The admin API endpoint allows modifying users and " -"tenants by default, while the public and internal APIs do not allow these " -"operations. In a production environment, the variants might reside on " -"separate networks that service different types of users for security " -"reasons. For instance, the public API network might be visible from the " -"Internet so customers can manage their clouds. The admin API network might " -"be restricted to operators within the organization that manages cloud " -"infrastructure. The internal API network might be restricted to the hosts " -"that contain OpenStack services. Also, OpenStack supports multiple regions " -"for scalability. For simplicity, this guide uses the management network for " -"all endpoint variations and the default ``RegionOne`` region." -msgstr "" - -# #-#-#-#-# neutron-compute-install.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# neutron-controller-install.pot (Installation Guide 0.1) #-#-#-#-# -#: ../neutron-compute-install.rst:150 ../neutron-controller-install.rst:122 -msgid "" -"Option 2 augments option 1 with the layer-3 (routing) service and enables " -"self-service (private) networks. If you want to use public (provider) and " -"private (self-service) networks, choose option 2." -msgstr "" - -#: ../dashboard-install.rst:129 -msgid "Optionally, configure the time zone::" -msgstr "" - -#: ../overview.rst:144 -msgid "" -"Optionally, the controller node runs portions of Block Storage, Object " -"Storage, Orchestration, and Telemetry services." -msgstr "" - -#: ../overview.rst:85 -msgid "" -"Orchestrates multiple composite cloud applications by using either the " -"native :term:`HOT ` template format or " -"the AWS CloudFormation template format, through both an OpenStack-native " -"REST API and a CloudFormation-compatible Query API." -msgstr "" - -#: ../environment-ntp-other.rst:4 -msgid "Other nodes" -msgstr "" - -#: ../overview.rst:121 -msgid "" -"Overlay (tunnel) traffic for private networks traverses the management " -"network instead of a dedicated network." -msgstr "" - -#: ../neutron-controller-install-option2.rst:365 -msgid "" -"Overlay networks such as VXLAN include additional packet headers that " -"increase overhead and decrease space available for the payload or user data. " -"Without knowledge of the virtual network infrastructure, instances attempt " -"to send packets using the default Ethernet :term:`maximum transmission unit " -"(MTU)` of 1500 bytes. :term:`Internet protocol (IP)` networks contain the :" -"term:`path MTU discovery (PMTUD)` mechanism to detect end-to-end MTU and " -"adjust packet size accordingly. However, some operating systems and networks " -"block or otherwise lack support for PMTUD causing performance degradation or " -"connectivity failure." -msgstr "" - -#: ../overview.rst:3 -msgid "Overview" -msgstr "" - -#: ../environment.rst:107 -msgid "Password name" -msgstr "" - -#: ../environment.rst:120 -msgid "Password of Block Storage service user ``cinder``" -msgstr "" - -#: ../environment.rst:144 -msgid "Password of Compute service user ``nova``" -msgstr "" - -#: ../environment.rst:128 -msgid "Password of Image service user ``glance``" -msgstr "" - -#: ../environment.rst:140 -msgid "Password of Networking service user ``neutron``" -msgstr "" - -#: ../environment.rst:148 -msgid "Password of Object Storage service user ``swift``" -msgstr "" - -#: ../environment.rst:132 -msgid "Password of Orchestration domain" -msgstr "" - -#: ../environment.rst:134 -msgid "Password of Orchestration service user ``heat``" -msgstr "" - -#: ../environment.rst:116 -msgid "Password of Telemetry service user ``ceilometer``" -msgstr "" - -#: ../environment.rst:112 -msgid "Password of user ``admin``" -msgstr "" - -#: ../environment.rst:124 -msgid "Password of user ``demo``" -msgstr "" - -#: ../environment.rst:146 -msgid "Password of user guest of RabbitMQ" -msgstr "" - -# #-#-#-#-# cinder-verify.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# nova-verify.pot (Installation Guide 0.1) #-#-#-#-# -#: ../cinder-verify.rst:11 ../nova-verify.rst:8 -msgid "Perform these commands on the controller node." -msgstr "" - -#: ../swift-storage-node.rst:186 -msgid "Perform these steps on each storage node." -msgstr "" - -#: ../ceilometer-swift.rst:50 -msgid "" -"Perform these steps on the controller and any other nodes that run the " -"Object Storage proxy service." -msgstr "" - -# #-#-#-#-# ceilometer-verify.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# swift-verify.pot (Installation Guide 0.1) #-#-#-#-# -#: ../ceilometer-verify.rst:9 ../swift-verify.rst:12 -msgid "Perform these steps on the controller node." -msgstr "" - -#: ../launch-instance.rst:84 -msgid "Permit :term:`ICMP` (ping):" -msgstr "" - -#: ../environment-dependencies.rst:459 -msgid "" -"Permit configuration, write, and read access for the ``openstack`` user:" -msgstr "" - -#: ../launch-instance.rst:95 -msgid "Permit secure shell (SSH) access:" -msgstr "" - -#: ../launch-instance-networks-private.rst:229 -msgid "" -"Ping this IP address from the controller node or any host on the public " -"physical network:" -msgstr "" - -#: ../cinder-controller-node.rst:291 -msgid "Populate the Block Storage database:" -msgstr "" - -#: ../nova-controller-install.rst:336 ../nova-controller-install.rst:344 -msgid "Populate the Compute database:" -msgstr "" - -#: ../keystone-install.rst:176 -msgid "Populate the Identity service database:" -msgstr "" - -#: ../glance-install.rst:324 -msgid "Populate the Image service database:" -msgstr "" - -#: ../heat-install.rst:358 -msgid "Populate the Orchestration database:" -msgstr "" - -#: ../neutron-controller-install.rst:265 ../neutron-controller-install.rst:360 -msgid "Populate the database:" -msgstr "" - -#: ../debconf/debconf-concepts.rst:97 -msgid "Pre-seed debconf prompts" -msgstr "" - -# #-#-#-#-# environment-dependencies.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# glance-install.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# keystone-install.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# keystone-services.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# neutron-compute-install.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# neutron-controller-install-option1.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# neutron-controller-install-option2.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# neutron-controller-install.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# nova-controller-install.pot (Installation Guide 0.1) #-#-#-#-# -#: ../environment-dependencies.rst:37 ../glance-install.rst:11 -#: ../keystone-install.rst:10 ../keystone-services.rst:10 -#: ../neutron-compute-install.rst:8 -#: ../neutron-controller-install-option1.rst:7 -#: ../neutron-controller-install-option2.rst:7 -#: ../neutron-controller-install.rst:5 ../nova-controller-install.rst:8 -msgid "Prerequisites" -msgstr "" - -#: ../launch-instance-networks-private.rst:4 -msgid "Private project network" -msgstr "" - -#: ../launch-instance-networks-private.rst:126 -msgid "" -"Private project networks connect to public provider networks using a virtual " -"router. Each router contains an interface to at least one private project " -"network and a gateway on a public provider network." -msgstr "" - -#: ../overview.rst:24 -msgid "Project name" -msgstr "" - -#: ../dashboard-next-step.rst:11 -msgid "" -"Provide users with a public IP address, a username, and a password so they " -"can access the dashboard through a web browser. In case of any SSL " -"certificate connection problems, point the server IP address to a domain " -"name, and give users access." -msgstr "" - -#: ../overview.rst:28 -msgid "" -"Provides a web-based self-service portal to interact with underlying " -"OpenStack services, such as launching an instance, assigning IP addresses " -"and configuring access controls." -msgstr "" - -#: ../overview.rst:68 -msgid "" -"Provides an authentication and authorization service for other OpenStack " -"services. Provides a catalog of endpoints for all OpenStack services." -msgstr "" - -#: ../overview.rst:60 -msgid "" -"Provides persistent block storage to running instances. Its pluggable driver " -"architecture facilitates the creation and management of block storage " -"devices." -msgstr "" - -#: ../environment-networking.rst:70 -msgid "Public on 203.0.113.0/24 with gateway 203.0.113.1" -msgstr "" - -#: ../launch-instance-networks-public.rst:4 -msgid "Public provider network" -msgstr "" - -#: ../environment-dependencies.rst:189 -msgid "" -"RHEL and CentOS enable :term:`SELinux` by default. Install the ``openstack-" -"selinux`` package to automatically manage security policies for OpenStack " -"services:" -msgstr "" - -#: ../debconf/debconf-rabbitmq.rst:5 -msgid "RabbitMQ credentials parameters" -msgstr "" - -#: ../swift-initial-rings.rst:86 ../swift-initial-rings.rst:167 -#: ../swift-initial-rings.rst:245 -msgid "Rebalance the ring:" -msgstr "" - -#: ../environment-networking.rst:117 ../environment-networking.rst:207 -msgid "Reboot the system to activate the changes." -msgstr "" - -#: ../environment-networking.rst:99 -msgid "" -"Reconfiguring network interfaces will interrupt network connectivity. We " -"recommend using a local terminal session for these procedures." -msgstr "" - -#: ../keystone-install.rst:486 -msgid "Recursively change the ownership of the ``/etc/keystone`` directory:" -msgstr "" - -#: ../debconf/debconf-api-endpoints.rst:5 -msgid "Register API endpoints" -msgstr "" - -#: ../keystone-users.rst:107 -msgid "" -"Regular (non-admin) tasks should use an unprivileged project and user. As an " -"example, this guide creates the ``demo`` project and user." -msgstr "" - -#: ../dashboard-install.rst:159 -msgid "Reload the web server configuration::" -msgstr "" - -#: ../ceilometer-verify.rst:67 -msgid "Remove the previously downloaded image file :file:`/tmp/cirros.img`:" -msgstr "" - -#: ../swift-initial-rings.rst:53 ../swift-initial-rings.rst:134 -#: ../swift-initial-rings.rst:212 -msgid "" -"Repeat this command for each storage device on each storage node. In the " -"example architecture, use the command in four variations:" -msgstr "" - -#: ../swift-finalize-installation.rst:33 ../swift-finalize-installation.rst:69 -msgid "Replace HASH_PATH_PREFIX and HASH_PATH_SUFFIX with unique values." -msgstr "" - -#: ../swift-storage-node-include3.txt:18 -msgid "" -"Replace MANAGEMENT_INTERFACE_IP_ADDRESS with the IP address of the " -"management network on the storage node." -msgstr "" - -#: ../ceilometer-controller-install.rst:431 -msgid "" -"Replace TELEMETRY_SECRET with the telemetry secret that you generated in a " -"previous step." -msgstr "" - -#: ../keystone-openrc.rst:33 -msgid "" -"Replace ``ADMIN_PASS`` with the password you chose for the ``admin`` user in " -"the Identity service." -msgstr "" - -#: ../keystone-services.rst:47 -msgid "" -"Replace ``ADMIN_TOKEN`` with the authentication token that you generated in " -"the section called :doc:`keystone-install`. For example:" -msgstr "" - -#: ../keystone-install.rst:126 -msgid "" -"Replace ``ADMIN_TOKEN`` with the random value that you generated in a " -"previous step." -msgstr "" - -#: ../ceilometer-controller-install.rst:201 -#: ../ceilometer-controller-install.rst:219 -msgid "Replace ``CEILOMETER_DBPASS`` with a suitable password." -msgstr "" - -#: ../ceilometer-controller-install.rst:355 -msgid "" -"Replace ``CEILOMETER_DBPASS`` with the password you chose for the Telemetry " -"module database. You must escape special characters such as ':', '/', '+', " -"and '@' in the connection string in accordance with RFC2396." +"In the ``[keystone_authtoken]`` section, configure Identity service access:" msgstr "" #: ../ceilometer-nova.rst:83 @@ -4236,19 +685,300 @@ msgid "" "module database." msgstr "" -# #-#-#-#-# ceilometer-controller-install.pot (Installation Guide 0.1) #-#-#-#-# # #-#-#-#-# ceilometer-nova.pot (Installation Guide 0.1) #-#-#-#-# -#: ../ceilometer-controller-install.rst:397 -#: ../ceilometer-controller-install.rst:419 ../ceilometer-nova.rst:107 +# #-#-#-#-# ceilometer-swift.pot (Installation Guide 0.1) #-#-#-#-# +#: ../ceilometer-nova.rst:121 ../ceilometer-swift.rst:48 +msgid "To configure notifications" +msgstr "" + +#: ../ceilometer-nova.rst:123 +msgid "Configure the Compute service to send notifications to the message bus." +msgstr "" + +#: ../ceilometer-nova.rst:125 msgid "" -"Replace ``CEILOMETER_PASS`` with the password you chose for the " -"``ceilometer`` user in the Identity service." +"Edit the :file:`/etc/nova/nova.conf` file and configure notifications in the " +"``[DEFAULT]`` section:" +msgstr "" + +#: ../ceilometer-nova.rst:138 +msgid "" +"The Nova notification_driver creates alerts and sends system state updates " +"to administrators and users. The notification_driver sends this information " +"to users in a manner as close to real-time as possible." +msgstr "" + +#: ../ceilometer-nova.rst:143 +msgid "" +"Notifications in real-time allow administrars to observe and resolve " +"emergencies when the cloud environment experiences errors or faults." +msgstr "" + +#: ../ceilometer-nova.rst:146 +msgid "" +"Administrators can also restrict notification delivery to certain tenant " +"groups. Users can view notifications through a web browser, without using a " +"specific interface." +msgstr "" + +#: ../ceilometer-nova.rst:150 +msgid "" +"Messages arrive in a specific format which includes: Message ID, Publisher " +"ID, Event type, Timestamp, Priority, and Payload. See the `Notification " +"System information `__ for an example " +"message format." +msgstr "" + +#: ../ceilometer-nova.rst:156 +msgid "" +"Notification messages are placed on the OpenStack messaging system, which " +"recruits AMQP to send information when an event triggers alerts." +msgstr "" + +#: ../ceilometer-nova.rst:159 +msgid "" +"The :file:`nova.conf` file uses the nova_notification driver by defualt." +msgstr "" + +#: ../ceilometer-nova.rst:163 +msgid "" +"While you can use a customised notification_driver, we recommend using the " +"default settings. Using stable web hooks for events, such as creating new " +"instances, and using custom notification drivers are not guaranteed to " +"deliver notifications in real-time." +msgstr "" + +#: ../ceilometer-nova.rst:174 ../ceilometer-nova.rst:184 +msgid "" +"Start the Telemetry agent and configure it to start when the system boots:" +msgstr "" + +# #-#-#-#-# ceilometer-nova.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# neutron-compute-install.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# nova-compute-install.pot (Installation Guide 0.1) #-#-#-#-# +#: ../ceilometer-nova.rst:194 ../ceilometer-nova.rst:208 +#: ../neutron-compute-install.rst:218 ../neutron-compute-install.rst:243 +#: ../neutron-compute-install.rst:259 ../nova-compute-install.rst:258 +msgid "Restart the Compute service:" +msgstr "" + +#: ../ceilometer-nova.rst:202 +msgid "Restart the agent:" +msgstr "" + +#: ../ceilometer-swift.rst:3 +msgid "Configure the Object Storage service" +msgstr "" + +#: ../ceilometer-swift.rst:5 +msgid "" +"To retrieve storage-oriented events and samples, configure the Object " +"Storage service to send notifications to the message bus." +msgstr "" + +#: ../ceilometer-swift.rst:11 +msgid "" +"The Telemetry service requires access to the Object Storage service using " +"the ``ResellerAdmin`` role. Perform these steps on the controller node." +msgstr "" + +#: ../ceilometer-swift.rst:15 +msgid "" +"Source the ``admin`` credentials to gain access to admin-only CLI commands." +msgstr "" + +#: ../ceilometer-swift.rst:22 +msgid "Create the ``ResellerAdmin`` role:" +msgstr "" + +#: ../ceilometer-swift.rst:34 +msgid "" +"Add the ``ResellerAdmin`` role to the ``service`` tenant and ``ceilometer`` " +"user:" +msgstr "" + +#: ../ceilometer-swift.rst:50 +msgid "" +"Perform these steps on the controller and any other nodes that run the " +"Object Storage proxy service." +msgstr "" + +# #-#-#-#-# ceilometer-swift.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# swift-controller-node.pot (Installation Guide 0.1) #-#-#-#-# +#: ../ceilometer-swift.rst:53 ../swift-controller-node-include.txt:1 +msgid "" +"Edit the :file:`/etc/swift/proxy-server.conf` file and complete the " +"following actions:" +msgstr "" + +#: ../ceilometer-swift.rst:56 +msgid "" +"In the ``[filter:keystoneauth]`` section, add the ``ResellerAdmin`` role:" +msgstr "" + +#: ../ceilometer-swift.rst:66 +msgid "In the ``[pipeline:main]`` section, add ``ceilometer``:" +msgstr "" + +#: ../ceilometer-swift.rst:75 +msgid "In the ``[filter:ceilometer]`` section, configure notifications:" +msgstr "" + +#: ../ceilometer-swift.rst:92 +msgid "" +"Add the ``swift`` system user to the ``ceilometer`` system group to permit " +"access to the Telemetry configuration files by the Object Storage service:" +msgstr "" + +#: ../ceilometer-swift.rst:103 ../ceilometer-swift.rst:119 +#: ../ceilometer-swift.rst:127 +msgid "Restart the Object Storage proxy service:" +msgstr "" + +#: ../ceilometer-swift.rst:111 +msgid "Install the ``ceilometermiddleware`` package:" +msgstr "" + +#: ../ceilometer-verify.rst:3 +msgid "Verify the Telemetry installation" +msgstr "" + +#: ../ceilometer-verify.rst:5 +msgid "This section describes how to verify operation of the Telemetry module." +msgstr "" + +# #-#-#-#-# ceilometer-verify.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# swift-verify.pot (Installation Guide 0.1) #-#-#-#-# +#: ../ceilometer-verify.rst:9 ../swift-verify.rst:12 +msgid "Perform these steps on the controller node." +msgstr "" + +#: ../ceilometer-verify.rst:18 +msgid "List available meters:" +msgstr "" + +#: ../ceilometer-verify.rst:32 +msgid "Download an image from the Image service:" +msgstr "" + +#: ../ceilometer-verify.rst:39 +msgid "" +"List available meters again to validate detection of the image download:" +msgstr "" + +#: ../ceilometer-verify.rst:56 +msgid "Retrieve usage statistics from the ``image.download`` meter:" +msgstr "" + +#: ../ceilometer-verify.rst:67 +msgid "Remove the previously downloaded image file :file:`/tmp/cirros.img`:" +msgstr "" + +#: ../ceilometer.rst:3 +msgid "Add the Telemetry module" +msgstr "" + +#: ../ceilometer.rst:16 +msgid "" +"Telemetry provides a framework for monitoring and metering the OpenStack " +"cloud. It is also known as the ceilometer project." +msgstr "" + +#: ../cinder-controller-node.rst:5 +msgid "" +"This section describes how to install and configure the Block Storage " +"service, code-named cinder, on the controller node. This service requires at " +"least one additional storage node that provides volumes to instances." +msgstr "" + +#: ../cinder-controller-node.rst:13 +msgid "" +"Before you install and configure the Block Storage service, you must create " +"a database, service credentials, and API endpoint." +msgstr "" + +# #-#-#-#-# cinder-controller-node.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# glance-install.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# heat-install.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# neutron-controller-install.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# nova-controller-install.pot (Installation Guide 0.1) #-#-#-#-# +#: ../cinder-controller-node.rst:16 ../glance-install.rst:16 +#: ../heat-install.rst:16 ../neutron-controller-install.rst:10 +#: ../nova-controller-install.rst:13 +msgid "To create the database, complete these steps:" +msgstr "" + +# #-#-#-#-# cinder-controller-node.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# glance-install.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# heat-install.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# keystone-install.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# nova-controller-install.pot (Installation Guide 0.1) #-#-#-#-# +#: ../cinder-controller-node.rst:18 ../glance-install.rst:18 +#: ../heat-install.rst:18 ../keystone-install.rst:17 +#: ../nova-controller-install.rst:15 +msgid "" +"Use the database access client to connect to the database server as the " +"``root`` user:" +msgstr "" + +#: ../cinder-controller-node.rst:25 +msgid "Create the ``cinder`` database:" +msgstr "" + +#: ../cinder-controller-node.rst:31 +msgid "Grant proper access to the ``cinder`` database:" msgstr "" #: ../cinder-controller-node.rst:40 msgid "Replace ``CINDER_DBPASS`` with a suitable password." msgstr "" +# #-#-#-#-# cinder-controller-node.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# glance-install.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# heat-install.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# keystone-install.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# neutron-controller-install.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# nova-controller-install.pot (Installation Guide 0.1) #-#-#-#-# +#: ../cinder-controller-node.rst:42 ../glance-install.rst:42 +#: ../heat-install.rst:38 ../keystone-install.rst:41 +#: ../neutron-controller-install.rst:35 ../nova-controller-install.rst:39 +msgid "Exit the database access client." +msgstr "" + +#: ../cinder-controller-node.rst:53 +msgid "Create a ``cinder`` user:" +msgstr "" + +#: ../cinder-controller-node.rst:70 +msgid "Add the ``admin`` role to the ``cinder`` user:" +msgstr "" + +#: ../cinder-controller-node.rst:82 +msgid "Create the ``cinder`` service entities:" +msgstr "" + +#: ../cinder-controller-node.rst:114 +msgid "" +"The Block Storage service requires both the ``volume`` and ``volumev2`` " +"services. However, both services use the same API endpoint that references " +"the Block Storage version 2 API." +msgstr "" + +#: ../cinder-controller-node.rst:118 +msgid "Create the Block Storage service API endpoints:" +msgstr "" + +#: ../cinder-controller-node.rst:163 +msgid "To install and configure Block Storage controller components" +msgstr "" + +#: ../cinder-controller-node.rst:195 +msgid "" +"Copy the :file:`/usr/share/cinder/cinder-dist.conf` file to :file:`/etc/" +"cinder/cinder.conf`." +msgstr "" + # #-#-#-#-# cinder-controller-node.pot (Installation Guide 0.1) #-#-#-#-# # #-#-#-#-# cinder-storage-node.pot (Installation Guide 0.1) #-#-#-#-# #: ../cinder-controller-node.rst:216 ../cinder-storage-node.rst:217 @@ -4265,674 +995,46 @@ msgid "" "in the Identity service." msgstr "" -#: ../keystone-openrc.rst:49 -msgid "" -"Replace ``DEMO_PASS`` with the password you chose for the ``demo`` user in " -"the Identity service." -msgstr "" - -#: ../swift-verify.rst:41 -msgid "" -"Replace ``FILE`` with the name of a local file to upload to the ``demo-" -"container1`` container." -msgstr "" - -#: ../swift-verify.rst:58 -msgid "" -"Replace ``FILE`` with the name of the file uploaded to the ``demo-" -"container1`` container." -msgstr "" - -#: ../glance-install.rst:40 -msgid "Replace ``GLANCE_DBPASS`` with a suitable password." -msgstr "" - -#: ../glance-install.rst:195 ../glance-install.rst:269 -msgid "" -"Replace ``GLANCE_DBPASS`` with the password you chose for the Image service " -"database." -msgstr "" - -#: ../glance-install.rst:218 ../glance-install.rst:292 -msgid "" -"Replace ``GLANCE_PASS`` with the password you chose for the ``glance`` user " -"in the Identity service." -msgstr "" - -#: ../heat-install.rst:36 -msgid "Replace ``HEAT_DBPASS`` with a suitable password." -msgstr "" - -#: ../heat-install.rst:253 -msgid "" -"Replace ``HEAT_DBPASS`` with the password you chose for the Orchestration " -"database." -msgstr "" - -#: ../heat-install.rst:356 -msgid "Replace ``HEAT_DOMAIN_PASS`` with a suitable password." -msgstr "" - -#: ../heat-install.rst:325 -msgid "" -"Replace ``HEAT_DOMAIN_PASS`` with the password you chose for the admin user " -"of the ``heat`` user domain in the Identity service." -msgstr "" - -#: ../heat-install.rst:293 -msgid "" -"Replace ``HEAT_PASS`` with the password you chose for the ``heat`` user in " -"the Identity service." -msgstr "" - -#: ../launch-instance-cinder.rst:62 -msgid "" -"Replace ``INSTANCE_NAME`` with the name of the instance and ``VOLUME_ID`` " -"with the ID of the volume you want to attach to it." -msgstr "" - -#: ../environment-networking.rst:168 -msgid "" -"Replace ``INTERFACE_NAME`` with the actual interface name. For example, " -"*eth1* or *ens224*." -msgstr "" - -#: ../keystone-install.rst:39 -msgid "Replace ``KEYSTONE_DBPASS`` with a suitable password." -msgstr "" - -#: ../keystone-install.rst:137 -msgid "" -"Replace ``KEYSTONE_DBPASS`` with the password you chose for the database." -msgstr "" - -#: ../nova-compute-install.rst:110 -msgid "" -"Replace ``MANAGEMENT_INTERFACE_IP_ADDRESS`` with the IP address of the " -"management network interface on your compute node, typically 10.0.0.31 for " -"the first node in the :ref:`example architecture `." -msgstr "" - -#: ../cinder-storage-node.rst:274 -msgid "" -"Replace ``MANAGEMENT_INTERFACE_IP_ADDRESS`` with the IP address of the " -"management network interface on your storage node, typically 10.0.0.41 for " -"the first node in the :ref:`example architecture `." -msgstr "" - -#: ../swift-storage-node.rst:145 ../swift-storage-node-include1.txt:18 -#: ../swift-storage-node-include2.txt:18 -msgid "" -"Replace ``MANAGEMENT_INTERFACE_IP_ADDRESS`` with the IP address of the " -"management network on the storage node." -msgstr "" - -#: ../neutron-controller-install.rst:178 -msgid "" -"Replace ``METADATA_SECRET`` with a suitable secret for the metadata proxy." -msgstr "" - -#: ../neutron-controller-install.rst:231 -msgid "" -"Replace ``METADATA_SECRET`` with the secret you chose for the metadata proxy." -msgstr "" - -# #-#-#-#-# neutron-controller-install-option1.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# neutron-controller-install-option2.pot (Installation Guide 0.1) #-#-#-#-# -#: ../neutron-controller-install-option1.rst:101 -#: ../neutron-controller-install-option2.rst:97 -msgid "" -"Replace ``NEUTRON_DBPASS`` with the password you chose for the database." -msgstr "" - -# #-#-#-#-# neutron-compute-install.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# neutron-controller-install-option1.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# neutron-controller-install-option2.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# neutron-controller-install.pot (Installation Guide 0.1) #-#-#-#-# -#: ../neutron-compute-install.rst:125 ../neutron-compute-install.rst:198 -#: ../neutron-controller-install-option1.rst:152 -#: ../neutron-controller-install-option2.rst:149 -#: ../neutron-controller-install.rst:158 ../neutron-controller-install.rst:228 -msgid "" -"Replace ``NEUTRON_PASS`` with the password you chose for the ``neutron`` " -"user in the Identity service." -msgstr "" - -#: ../nova-controller-install.rst:37 -msgid "Replace ``NOVA_DBPASS`` with a suitable password." -msgstr "" - -#: ../nova-controller-install.rst:192 -msgid "" -"Replace ``NOVA_DBPASS`` with the password you chose for the Compute database." -msgstr "" - -# #-#-#-#-# neutron-controller-install-option1.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# neutron-controller-install-option2.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# nova-compute-install.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# nova-controller-install.pot (Installation Guide 0.1) #-#-#-#-# -#: ../neutron-controller-install-option1.rst:182 -#: ../neutron-controller-install-option2.rst:179 -#: ../nova-compute-install.rst:94 ../nova-controller-install.rst:233 -msgid "" -"Replace ``NOVA_PASS`` with the password you chose for the ``nova`` user in " -"the Identity service." -msgstr "" - -#: ../environment-ntp-controller.rst:57 ../environment-ntp-controller.rst:76 -msgid "" -"Replace ``NTP_SERVER`` with the hostname or IP address of a suitable more " -"accurate (lower stratum) NTP server. The configuration supports multiple " -"``server`` keys." -msgstr "" - -# #-#-#-#-# neutron-compute-install-option2.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# neutron-controller-install-option2.pot (Installation Guide 0.1) #-#-#-#-# -#: ../neutron-compute-install-option2.rst:37 -#: ../neutron-controller-install-option2.rst:290 -msgid "" -"Replace ``OVERLAY_INTERFACE_IP_ADDRESS`` with the IP address of the " -"underlying physical network interface that handles overlay networks. The " -"example architecture uses the management interface." -msgstr "" - -#: ../launch-instance-networks-private.rst:89 -msgid "" -"Replace ``PRIVATE_NETWORK_CIDR`` with the subnet you want to use on the " -"private network. You can use any arbitrary value, although we recommend a " -"network from `RFC 1918 `_." -msgstr "" - -#: ../launch-instance-networks-private.rst:93 -msgid "" -"Replace ``PRIVATE_NETWORK_GATEWAY`` with the gateway you want to use on the " -"private network, typically the \".1\" IP address." -msgstr "" - -#: ../launch-instance-private.rst:79 -msgid "" -"Replace ``PRIVATE_NET_ID`` with the ID of the ``private`` project network." -msgstr "" - -# #-#-#-#-# neutron-compute-install-option1.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# neutron-compute-install-option2.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# neutron-controller-install-option1.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# neutron-controller-install-option2.pot (Installation Guide 0.1) #-#-#-#-# -#: ../neutron-compute-install-option1.rst:23 -#: ../neutron-compute-install-option2.rst:23 -#: ../neutron-controller-install-option1.rst:265 -#: ../neutron-controller-install-option2.rst:276 -msgid "" -"Replace ``PUBLIC_INTERFACE_NAME`` with the name of the underlying physical " -"public network interface." -msgstr "" - -#: ../launch-instance-networks-public.rst:94 -msgid "" -"Replace ``PUBLIC_NETWORK_CIDR`` with the subnet on the public physical " -"network in CIDR notation." -msgstr "" - -#: ../launch-instance-networks-public.rst:102 -msgid "" -"Replace ``PUBLIC_NETWORK_GATEWAY`` with the gateway IP address on the public " -"physical network, typically the \".1\" IP address." -msgstr "" - -#: ../launch-instance-public.rst:85 -msgid "" -"Replace ``PUBLIC_NET_ID`` with the ID of the ``public`` provider network." -msgstr "" - -#: ../environment-dependencies.rst:457 -msgid "Replace ``RABBIT_PASS`` with a suitable password." -msgstr "" - -# #-#-#-#-# neutron-compute-install.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# neutron-controller-install-option1.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# neutron-controller-install-option2.pot (Installation Guide 0.1) #-#-#-#-# -#: ../neutron-compute-install.rst:102 -#: ../neutron-controller-install-option1.rst:129 -#: ../neutron-controller-install-option2.rst:126 -msgid "" -"Replace ``RABBIT_PASS`` with the password you chose for the ``openstack`` " -"account in RabbitMQ." -msgstr "" - -# #-#-#-#-# ceilometer-controller-install.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# ceilometer-glance.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# ceilometer-nova.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# ceilometer-swift.pot (Installation Guide 0.1) #-#-#-#-# # #-#-#-#-# cinder-controller-node.pot (Installation Guide 0.1) #-#-#-#-# # #-#-#-#-# cinder-storage-node.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# heat-install.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# nova-compute-install.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# nova-controller-install.pot (Installation Guide 0.1) #-#-#-#-# -#: ../ceilometer-controller-install.rst:376 ../ceilometer-glance.rst:26 -#: ../ceilometer-nova.rst:66 ../ceilometer-swift.rst:89 -#: ../cinder-controller-node.rst:234 ../cinder-storage-node.rst:235 -#: ../heat-install.rst:272 ../nova-compute-install.rst:71 -#: ../nova-controller-install.rst:210 -msgid "" -"Replace ``RABBIT_PASS`` with the password you chose for the ``openstack`` " -"account in ``RabbitMQ``." -msgstr "" - -#: ../launch-instance-networks-public.rst:97 -msgid "" -"Replace ``START_IP_ADDRESS`` and ``END_IP_ADDRESS`` with the first and last " -"IP address of the range within the subnet that you want to allocate for " -"instances. This range must not include any existing active IP addresses." -msgstr "" - -#: ../swift-initial-rings.rst:42 ../swift-initial-rings.rst:123 -#: ../swift-initial-rings.rst:202 -msgid "" -"Replace ``STORAGE_NODE_MANAGEMENT_INTERFACE_IP_ADDRESS`` with the IP address " -"of the management network on the storage node. Replace ``DEVICE_NAME`` with " -"a storage device name on the same storage node. For example, using the first " -"storage node in :doc:`swift-storage-node` with the :file:`/dev/sdb1` storage " -"device and weight of 100:" -msgstr "" - -#: ../swift-controller-node-include.txt:66 -msgid "" -"Replace ``SWIFT_PASS`` with the password you chose for the ``swift`` user in " -"the Identity service." -msgstr "" - -#: ../ceilometer-nova.rst:47 -msgid "" -"Replace ``TELEMETRY_SECRET`` with the telemetry secret you chose for the " -"Telemetry module." -msgstr "" - -#: ../dashboard-install.rst:133 -msgid "" -"Replace ``TIME_ZONE`` with an appropriate time zone identifier. For more " -"information, see the `list of time zones `__." -msgstr "" - -#: ../keystone-openrc.rst:67 -msgid "Request an authentication token:" -msgstr "" - # #-#-#-#-# glance-install.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# heat-install.pot (Installation Guide 0.1) #-#-#-#-# -#: ../glance-install.rst:338 ../heat-install.rst:372 -msgid "" -"Respond to prompts for :doc:`database management `, :doc:`Identity service credentials `, :doc:`service endpoint registration `, and :doc:`message broker credentials `." -msgstr "" - -#: ../keystone-install.rst:198 -msgid "" -"Respond to prompts for :doc:`debconf/debconf-dbconfig-common`, which will " -"fill the below database access directive." -msgstr "" - -#: ../neutron-compute-install.rst:58 -msgid "" -"Respond to prompts for ``database management``, ``Identity service " -"credentials``, ``service endpoint``, and ``message queue credentials``." -msgstr "" - +# #-#-#-#-# neutron-compute-install.pot (Installation Guide 0.1) #-#-#-#-# # #-#-#-#-# neutron-controller-install-option1.pot (Installation Guide 0.1) #-#-#-#-# # #-#-#-#-# neutron-controller-install-option2.pot (Installation Guide 0.1) #-#-#-#-# -#: ../neutron-controller-install-option1.rst:64 -#: ../neutron-controller-install-option2.rst:66 -msgid "" -"Respond to prompts for `database management <#debconf-dbconfig-common>`__, " -"`Identity service credentials <#debconf-keystone_authtoken>`__, `service " -"endpoint registration <#debconf-api-endpoints>`__, and `message queue " -"credentials <#debconf-rabbitmq>`__." -msgstr "" - -#: ../dashboard-install.rst:49 -msgid "Respond to prompts for web server configuration." -msgstr "" - -#: ../keystone-install.rst:497 -msgid "Restart the Apache HTTP server:" -msgstr "" - -#: ../dashboard-install.rst:173 ../dashboard-install.rst:185 -msgid "Restart the Apache HTTP service if it is already running." -msgstr "" - -#: ../ceilometer-cinder.rst:26 ../ceilometer-cinder.rst:40 -msgid "Restart the Block Storage services on the controller node:" -msgstr "" - -#: ../ceilometer-cinder.rst:32 ../ceilometer-cinder.rst:47 -msgid "Restart the Block Storage services on the storage nodes:" -msgstr "" - -#: ../cinder-controller-node.rst:313 -msgid "Restart the Block Storage services:" -msgstr "" - -#: ../cinder-storage-node.rst:373 -msgid "Restart the Block Storage volume service including its dependencies:" -msgstr "" - -# #-#-#-#-# ceilometer-nova.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# neutron-compute-install.pot (Installation Guide 0.1) #-#-#-#-# # #-#-#-#-# nova-compute-install.pot (Installation Guide 0.1) #-#-#-#-# -#: ../ceilometer-nova.rst:194 ../ceilometer-nova.rst:208 -#: ../neutron-compute-install.rst:232 ../neutron-compute-install.rst:257 -#: ../neutron-compute-install.rst:273 ../nova-compute-install.rst:258 -msgid "Restart the Compute service:" -msgstr "" - -# #-#-#-#-# neutron-controller-install.pot (Installation Guide 0.1) #-#-#-#-# # #-#-#-#-# nova-controller-install.pot (Installation Guide 0.1) #-#-#-#-# -#: ../neutron-controller-install.rst:277 ../neutron-controller-install.rst:316 -#: ../nova-controller-install.rst:387 -msgid "Restart the Compute services:" -msgstr "" - -#: ../glance-install.rst:367 -msgid "Restart the Image service services:" -msgstr "" - -#: ../ceilometer-glance.rst:31 ../ceilometer-glance.rst:39 -msgid "Restart the Image service:" -msgstr "" - -#: ../neutron-compute-install.rst:291 -msgid "Restart the Linux bridge agent:" -msgstr "" - -# #-#-#-#-# environment-ntp-controller.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# environment-ntp-other.pot (Installation Guide 0.1) #-#-#-#-# -#: ../environment-ntp-controller.rst:61 ../environment-ntp-other.rst:56 -msgid "Restart the NTP service:" -msgstr "" - -#: ../neutron-controller-install.rst:378 -msgid "Restart the Networking services." -msgstr "" - -#: ../ceilometer-swift.rst:103 ../ceilometer-swift.rst:119 -#: ../ceilometer-swift.rst:127 -msgid "Restart the Object Storage proxy service:" -msgstr "" - -#: ../heat-install.rst:407 -msgid "Restart the Orchestration services:" -msgstr "" - -#: ../ceilometer-controller-install.rst:511 -msgid "Restart the Telemetry services:" -msgstr "" - -#: ../ceilometer-nova.rst:202 -msgid "Restart the agent:" -msgstr "" - -#: ../environment-dependencies.rst:359 -msgid "Restart the database service:" -msgstr "" - -#: ../neutron-controller-install.rst:372 -msgid "Restart the nova-api service:" -msgstr "" - -#: ../ceilometer-verify.rst:56 -msgid "Retrieve usage statistics from the ``image.download`` meter:" -msgstr "" - -# #-#-#-#-# launch-instance-networks-private.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# launch-instance-networks-public.pot (Installation Guide 0.1) #-#-#-#-# -#: ../launch-instance-networks-private.rst:244 -#: ../launch-instance-networks-public.rst:135 +#: ../cinder-controller-node.rst:262 ../cinder-storage-node.rst:263 +#: ../glance-install.rst:223 ../glance-install.rst:297 +#: ../neutron-compute-install.rst:131 +#: ../neutron-controller-install-option1.rst:158 +#: ../neutron-controller-install-option2.rst:155 +#: ../nova-compute-install.rst:99 ../nova-controller-install.rst:238 msgid "" -"Return to :ref:`Launch an instance - Create virtual networks `." +"Comment out or remove any other options in the ``[keystone_authtoken]`` " +"section." msgstr "" -# #-#-#-#-# launch-instance-private.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# launch-instance-public.pot (Installation Guide 0.1) #-#-#-#-# -#: ../launch-instance-private.rst:270 ../launch-instance-public.rst:240 -msgid "Return to :ref:`Launch an instance `." -msgstr "" - -# #-#-#-#-# neutron-compute-install-option1.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# neutron-compute-install-option2.pot (Installation Guide 0.1) #-#-#-#-# -#: ../neutron-compute-install-option1.rst:45 -#: ../neutron-compute-install-option2.rst:53 -msgid "" -"Return to :ref:`Networking compute node configuration `." -msgstr "" - -# #-#-#-#-# neutron-controller-install-option1.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# neutron-controller-install-option2.pot (Installation Guide 0.1) #-#-#-#-# -#: ../neutron-controller-install-option1.rst:323 -#: ../neutron-controller-install-option2.rst:418 -msgid "" -"Return to :ref:`Networking controller node configuration `." -msgstr "" - -#: ../launch-instance-cinder.rst:127 -msgid "Return to :ref:`launch-instance`." -msgstr "" - -#: ../environment.rst:110 -msgid "Root password for the database" -msgstr "" - -#: ../keystone-install.rst:75 ../keystone-install.rst:86 -#: ../keystone-install.rst:187 -msgid "Run the following command to install the packages:" -msgstr "" - -#: ../heat-install.rst:200 ../heat-install.rst:209 ../heat-install.rst:218 -#: ../heat-install.rst:366 -msgid "Run the following commands to install the packages:" -msgstr "" - -#: ../environment-ntp-verify.rst:25 -msgid "Run the same command on *all other* nodes:" -msgstr "" - -#: ../environment-ntp-verify.rst:10 -msgid "Run this command on the *controller* node:" -msgstr "" - -#: ../environment-dependencies.rst:249 -msgid "SQL database" -msgstr "" - -#: ../index-debian.rst:101 -msgid "Search in this guide" -msgstr "" - -#: ../environment-dependencies.rst:392 -msgid "" -"Secure the database service including choosing a suitable password for the " -"root account:" -msgstr "" - -#: ../environment-dependencies.rst:386 -msgid "Secure the database service:" -msgstr "" - -#: ../environment.rst:80 -msgid "Security" -msgstr "" - -# #-#-#-#-# neutron-compute-install.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# neutron-controller-install-option1.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# neutron-controller-install-option2.pot (Installation Guide 0.1) #-#-#-#-# -#: ../neutron-compute-install.rst:61 -#: ../neutron-controller-install-option1.rst:70 -#: ../neutron-controller-install-option2.rst:72 -msgid "Select the ML2 plug-in:" -msgstr "" - -#: ../glance-install.rst:344 -msgid "" -"Select the ``keystone`` pipeline to configure the Image service to use the " -"Identity service:" -msgstr "" - -# #-#-#-#-# neutron-compute-install.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# neutron-controller-install-option1.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# neutron-controller-install-option2.pot (Installation Guide 0.1) #-#-#-#-# -#: ../neutron-compute-install.rst:68 -#: ../neutron-controller-install-option1.rst:76 -#: ../neutron-controller-install-option2.rst:78 -msgid "" -"Selecting the ML2 plug-in also populates the ``service_plugins`` and " -"``allow_overlapping_ips`` options in the :file:`/etc/neutron/neutron.conf` " -"file with the appropriate values." -msgstr "" - -#: ../overview.rst:23 -msgid "Service" -msgstr "" - -#: ../debconf/debconf-keystone-authtoken.rst:5 -msgid "Services and the [keystone_authtoken]" -msgstr "" - -#: ../launch-instance-networks-private.rst:181 -msgid "Set a gateway on the public network on the router:" -msgstr "" - -#: ../cinder-storage-node.rst:34 -msgid "Set the hostname of the node to ``block1``." -msgstr "" - -#: ../environment-networking.rst:214 -msgid "Set the hostname of the node to ``compute1``." -msgstr "" - -#: ../environment-networking.rst:124 -msgid "Set the hostname of the node to ``controller``." -msgstr "" - -#: ../swift-storage-node.rst:35 -msgid "Set the hostname of the node to ``object1``." -msgstr "" - -#: ../swift-storage-node.rst:45 -msgid "Set the hostname of the node to ``object2``." -msgstr "" - -#: ../dashboard-next-step.rst:20 -msgid "" -"Set up session storage. See `Set up session storage for the dashboard " -"`__." -msgstr "" - -#: ../swift-verify.rst:20 -msgid "Show the service status:" -msgstr "" - -#: ../cinder-storage-node.rst:165 -msgid "" -"Similarly, if your compute nodes use LVM on the operating system disk, you " -"must also modify the filter in the :file:`/etc/lvm/lvm.conf` file on those " -"nodes to include only the operating system disk. For example, if the :file:`/" -"dev/sda` device contains the operating system:" -msgstr "" - -#: ../debconf/debconf-dbconfig-common.rst:94 -msgid "" -"So, if using Debian, you wont need to care about database creation, access " -"rights and character sets. All that is handled for you by the packages." -msgstr "" - -#: ../app_reserved_uids.rst:11 -msgid "" -"Some OpenStack packages generate and assign user IDs automatically during " -"package installation. In these cases, the user ID value is not important. " -"The existence of the user ID is what matters." -msgstr "" - -#: ../neutron-controller-install-option2.rst:389 -msgid "" -"Some cloud images ignore the DHCP MTU option in which case you should " -"configure it using metadata, a script, or other suitable method." -msgstr "" - -#: ../environment-networking.rst:138 ../environment-networking.rst:228 -msgid "" -"Some distributions add an extraneous entry in the :file:`/etc/hosts` file " -"that resolves the actual hostname to another loopback IP address such as " -"``127.0.1.1``. You must comment out or remove this entry to prevent name " -"resolution problems. **Do not remove the 127.0.0.1 entry.**" -msgstr "" - -#: ../cinder-storage-node.rst:76 ../cinder-storage-node.rst:97 -#: ../cinder-storage-node.rst:107 -msgid "Some distributions include LVM by default." -msgstr "" - -#: ../ceilometer-swift.rst:15 -msgid "" -"Source the ``admin`` credentials to gain access to admin-only CLI commands." -msgstr "" - -# #-#-#-#-# ceilometer-controller-install.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# ceilometer-verify.pot (Installation Guide 0.1) #-#-#-#-# # #-#-#-#-# cinder-controller-node.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# cinder-verify.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# glance-install.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# glance-verify.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# heat-install.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# neutron-controller-install.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# neutron-verify.pot (Installation Guide 0.1) #-#-#-#-# # #-#-#-#-# nova-controller-install.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# nova-verify.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# swift-controller-node.pot (Installation Guide 0.1) #-#-#-#-# -#: ../ceilometer-controller-install.rst:222 ../ceilometer-verify.rst:11 -#: ../cinder-controller-node.rst:44 ../cinder-verify.rst:20 -#: ../glance-install.rst:44 ../glance-verify.rst:23 ../heat-install.rst:40 -#: ../heat-install.rst:340 ../neutron-controller-install.rst:37 -#: ../neutron-verify.rst:4 ../nova-controller-install.rst:41 -#: ../nova-verify.rst:10 ../swift-controller-node.rst:29 +#: ../cinder-controller-node.rst:265 ../nova-controller-install.rst:241 msgid "" -"Source the ``admin`` credentials to gain access to admin-only CLI commands:" +"In the ``[DEFAULT]`` section, configure the ``my_ip`` option to use the " +"management interface IP address of the controller node:" msgstr "" -#: ../heat-verify.rst:8 -msgid "Source the ``admin`` tenant credentials:" +# #-#-#-#-# cinder-controller-node.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# cinder-storage-node.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# nova-compute-install.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# nova-controller-install.pot (Installation Guide 0.1) #-#-#-#-# +#: ../cinder-controller-node.rst:274 ../cinder-storage-node.rst:331 +#: ../nova-compute-install.rst:168 ../nova-compute-install.rst:178 +#: ../nova-controller-install.rst:289 ../nova-controller-install.rst:299 +#: ../nova-controller-install.rst:309 +msgid "In the ``[oslo_concurrency]`` section, configure the lock path:" msgstr "" -#: ../launch-instance-networks-private.rst:150 -msgid "" -"Source the ``demo`` credentials to gain access to user-only CLI commands:" -msgstr "" - -#: ../launch-instance-cinder.rst:9 -msgid "" -"Source the ``demo`` credentials to perform the following steps as a non-" -"administrative project:" -msgstr "" - -#: ../swift-verify.rst:14 -msgid "Source the ``demo`` credentials:" -msgstr "" - -#: ../launch-instance.rst:45 -msgid "Source the ``demo`` tenant credentials:" -msgstr "" - -#: ../keystone-install.rst:514 ../keystone-install.rst:523 -msgid "" -"Start the Apache HTTP service and configure it to start when the system " -"boots:" +#: ../cinder-controller-node.rst:291 +msgid "Populate the Block Storage database:" msgstr "" #: ../cinder-controller-node.rst:302 @@ -4941,1029 +1043,45 @@ msgid "" "boots:" msgstr "" -#: ../cinder-storage-node.rst:353 ../cinder-storage-node.rst:363 -msgid "" -"Start the Block Storage volume service including its dependencies and " -"configure them to start when the system boots:" -msgstr "" - -#: ../nova-compute-install.rst:248 -msgid "" -"Start the Compute service including its dependencies and configure them to " -"start automatically when the system boots:" -msgstr "" - -#: ../nova-controller-install.rst:355 ../nova-controller-install.rst:371 -msgid "" -"Start the Compute services and configure them to start when the system boots:" -msgstr "" - -#: ../glance-install.rst:355 -msgid "" -"Start the Image service services and configure them to start when the system " -"boots:" -msgstr "" - -#: ../cinder-storage-node.rst:78 -msgid "" -"Start the LVM metadata service and configure it to start when the system " -"boots:" -msgstr "" - -#: ../neutron-compute-install.rst:263 -msgid "" -"Start the Linux Bridge agent and configure it to start when the system boots:" -msgstr "" - -#: ../neutron-compute-install.rst:238 -msgid "" -"Start the Linux bridge agent and configure it to start when the system boots:" -msgstr "" - -#: ../keystone-install.rst:104 -msgid "" -"Start the Memcached service and configure it to start when the system boots:" -msgstr "" - -#: ../ceilometer-controller-install.rst:95 -#: ../ceilometer-controller-install.rst:132 -msgid "" -"Start the MongoDB services and configure them to start when the system boots:" -msgstr "" - -# #-#-#-#-# environment-ntp-controller.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# environment-ntp-other.pot (Installation Guide 0.1) #-#-#-#-# -#: ../environment-ntp-controller.rst:89 ../environment-ntp-other.rst:71 -msgid "Start the NTP service and configure it to start when the system boots:" -msgstr "" - -#: ../neutron-controller-install.rst:284 ../neutron-controller-install.rst:323 -msgid "" -"Start the Networking services and configure them to start when the system " -"boots." -msgstr "" - -#: ../heat-install.rst:395 -msgid "" -"Start the Orchestration services and configure them to start when the system " -"boots:" -msgstr "" - -#: ../ceilometer-nova.rst:174 ../ceilometer-nova.rst:184 -msgid "" -"Start the Telemetry agent and configure it to start when the system boots:" -msgstr "" - -#: ../ceilometer-controller-install.rst:471 -#: ../ceilometer-controller-install.rst:491 -msgid "" -"Start the Telemetry services and configure them to start when the system " -"boots:" -msgstr "" - -#: ../swift-storage-node.rst:163 -msgid "Start the ``rsync`` service:" -msgstr "" - -#: ../swift-storage-node.rst:171 -msgid "" -"Start the ``rsyncd`` service and configure it to start when the system boots:" -msgstr "" - -#: ../environment-dependencies.rst:367 -msgid "" -"Start the database service and configure it to start when the system boots:" -msgstr "" - -#: ../environment-dependencies.rst:440 -msgid "" -"Start the message queue service and configure it to start when the system " -"boots:" -msgstr "" - -#: ../dashboard-install.rst:165 ../dashboard-install.rst:177 -msgid "" -"Start the web server and session storage service and configure them to start " -"when the system boots::" -msgstr "" - -#: ../overview.rst:51 -msgid "" -"Stores and retrieves arbitrary unstructured data objects via a :term:" -"`RESTful`, HTTP based API. It is highly fault tolerant with its data " -"replication and scale-out architecture. Its implementation is not like a " -"file server with mountable directories. In this case, it writes objects and " -"files to multiple drives, ensuring the data is replicated across a server " -"cluster." -msgstr "" - -#: ../overview.rst:73 -msgid "" -"Stores and retrieves virtual machine disk images. OpenStack Compute makes " -"use of this during instance provisioning." -msgstr "" - -#: ../ceilometer.rst:16 -msgid "" -"Telemetry provides a framework for monitoring and metering the OpenStack " -"cloud. It is also known as the ceilometer project." -msgstr "" - -#: ../ceilometer-nova.rst:5 -msgid "" -"Telemetry uses a combination of notifications and an agent to collect " -"Compute meters. Perform these steps on each compute node." -msgstr "" - -#: ../environment.rst:29 -msgid "" -"The :command:`systemctl enable` call on openSUSE outputs a warning message " -"when the service uses SysV Init scripts instead of native systemd files. " -"This warning can be ignored." -msgstr "" - -#: ../ceilometer-nova.rst:159 -msgid "" -"The :file:`nova.conf` file uses the nova_notification driver by defualt." -msgstr "" - -# #-#-#-#-# neutron-controller-install-option1.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# neutron-controller-install-option2.pot (Installation Guide 0.1) #-#-#-#-# -#: ../neutron-controller-install-option1.rst:298 -#: ../neutron-controller-install-option2.rst:349 -msgid "The :term:`DHCP agent` provides DHCP services for virtual networks." -msgstr "" - -#: ../neutron-controller-install-option2.rst:317 -msgid "" -"The :term:`Layer-3 (L3) agent` provides routing and NAT services for virtual " -"networks." -msgstr "" - -#: ../overview.rst:5 -msgid "" -"The :term:`OpenStack` project is an open source cloud computing platform " -"that supports all types of cloud environments. The project aims for simple " -"implementation, massive scalability, and a rich set of features. Cloud " -"computing experts from around the world contribute to the project." -msgstr "" - -#: ../neutron-controller-install.rst:137 -msgid "" -"The :term:`metadata agent ` provides configuration " -"information such as credentials to instances." -msgstr "" - -#: ../cinder-storage-node.rst:129 -msgid "The Block Storage service creates logical volumes in this volume group." -msgstr "" - -#: ../cinder-controller-node.rst:114 -msgid "" -"The Block Storage service requires both the ``volume`` and ``volumev2`` " -"services. However, both services use the same API endpoint that references " -"the Block Storage version 2 API." -msgstr "" - -# #-#-#-#-# launch-instance-private.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# launch-instance-public.pot (Installation Guide 0.1) #-#-#-#-# -#: ../launch-instance-private.rst:152 ../launch-instance-public.rst:163 -msgid "" -"The CirrOS image includes conventional user name/password authentication and " -"provides these credentials at the login prompt. After logging into CirrOS, " -"we recommend that you verify network connectivity using ``ping``." -msgstr "" - -#: ../horizon.rst:10 -msgid "" -"The Dashboard enables web-based interactions with the OpenStack Compute " -"cloud controller through the OpenStack APIs." -msgstr "" - -#: ../debconf/debconf-keystone-authtoken.rst:57 -msgid "" -"The Debian OpenStack packages offer automation for this, so OpenStack users " -"do not have to manually edit the configuration files." -msgstr "" - -#: ../debconf/debconf-api-endpoints.rst:59 -msgid "" -"The Debian package post installation scripts will then perform the below " -"commands for you:" -msgstr "" - -#: ../debconf/debconf-concepts.rst:20 -msgid "The Debian packages" -msgstr "" - -#: ../debconf/debconf-dbconfig-common.rst:76 -msgid "" -"The Identity service is installed with MySQL as the database back end, " -"``keystonedb`` as database name, and the localhost socket file. The " -"corresponding DNS will then be:" -msgstr "" - -#: ../keystone-services.rst:102 -msgid "" -"The Identity service manages a catalog of API endpoints associated with the " -"services in your OpenStack environment. Services use this catalog to " -"determine how to communicate with other services in your environment." -msgstr "" - -#: ../keystone-services.rst:77 -msgid "" -"The Identity service manages a catalog of services in your OpenStack " -"environment. Services use this catalog to determine the other services " -"available in your environment." -msgstr "" - -#: ../keystone-services.rst:4 -msgid "" -"The Identity service provides a catalog of services and their locations. " -"Each service that you add to your OpenStack environment requires a :term:" -"`service` entity and several :term:`API endpoints` in the " -"catalog." -msgstr "" - -#: ../keystone-users.rst:4 -msgid "" -"The Identity service provides authentication services for each OpenStack " -"service. The authentication service uses a combination of :term:`domains " -"`, :term:`projects` (tenants), :term:`users`, and :" -"term:`roles`." -msgstr "" - -#: ../environment-dependencies.rst:121 -msgid "" -"The Liberty release is available directly through the official Debian " -"backports repository. To use this repository, follow the instruction from " -"the official `Debian website `_, " -"which basically suggest doing the following steps:" -msgstr "" - -# #-#-#-#-# neutron-compute-install-option1.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# neutron-compute-install-option2.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# neutron-controller-install-option1.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# neutron-controller-install-option2.pot (Installation Guide 0.1) #-#-#-#-# -#: ../neutron-compute-install-option1.rst:9 -#: ../neutron-compute-install-option2.rst:9 -#: ../neutron-controller-install-option1.rst:251 -#: ../neutron-controller-install-option2.rst:262 -msgid "" -"The Linux bridge agent builds layer-2 (bridging and switching) virtual " -"networking infrastructure for instances including VXLAN tunnels for private " -"networks and handles security groups." -msgstr "" - -#: ../neutron-controller-install-option2.rst:231 -msgid "The Linux bridge agent only supports VXLAN overlay networks." -msgstr "" - -# #-#-#-#-# neutron-controller-install-option1.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# neutron-controller-install-option2.pot (Installation Guide 0.1) #-#-#-#-# -#: ../neutron-controller-install-option1.rst:197 -#: ../neutron-controller-install-option2.rst:194 -msgid "" -"The ML2 plug-in uses the Linux bridge mechanism to build layer-2 (bridging " -"and switching) virtual networking infrastructure for instances." -msgstr "" - -#: ../neutron-compute-install.rst:77 -msgid "" -"The Networking common component configuration includes the authentication " -"mechanism, message queue, and plug-in." -msgstr "" - -#: ../neutron-controller-install-option1.rst:85 -msgid "" -"The Networking server component configuration includes the database, " -"authentication mechanism, message queue, topology change notifications, and " -"plug-in." -msgstr "" - -# #-#-#-#-# neutron-compute-install.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# neutron-controller-install.pot (Installation Guide 0.1) #-#-#-#-# -#: ../neutron-compute-install.rst:206 ../neutron-controller-install.rst:239 -msgid "" -"The Networking service initialization scripts expect a symbolic link :file:`/" -"etc/neutron/plugin.ini` pointing to the ML2 plug-in configuration file, :" -"file:`/etc/neutron/plugins/ml2/ml2_conf.ini`. If this symbolic link does not " -"exist, create it using the following command:" -msgstr "" - -# #-#-#-#-# neutron-compute-install.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# neutron-controller-install.pot (Installation Guide 0.1) #-#-#-#-# -#: ../neutron-compute-install.rst:248 ../neutron-controller-install.rst:307 -msgid "" -"The Networking service initialization scripts expect the variable " -"``NEUTRON_PLUGIN_CONF`` in the :file:`/etc/sysconfig/neutron` file to " -"reference the ML2 plug-in configuration file. Edit the :file:`/etc/sysconfig/" -"neutron` file and add the following:" -msgstr "" - -#: ../ceilometer-nova.rst:138 -msgid "" -"The Nova notification_driver creates alerts and sends system state updates " -"to administrators and users. The notification_driver sends this information " -"to users in a manner as close to real-time as possible." -msgstr "" - -#: ../swift-controller-node.rst:26 -msgid "" -"The Object Storage service does not use an SQL database on the controller " -"node. Instead, it uses distributed SQLite databases on each storage node." -msgstr "" - -#: ../cinder.rst:13 -msgid "" -"The OpenStack Block Storage service provides block storage devices to guest " -"instances. The method in which the storage is provisioned and consumed is " -"determined by the Block Storage driver, or drivers in the case of a multi-" -"backend configuration. There are a variety of drivers that are available: " -"NAS/SAN, NFS, iSCSI, Ceph, and more. The Block Storage API and scheduler " -"services typically run on the controller nodes. Depending upon the drivers " -"used, the volume service can run on controllers, compute nodes, or " -"standalone storage nodes. For more information, see the `Configuration " -"Reference `__." -msgstr "" - -#: ../horizon.rst:5 -msgid "" -"The OpenStack Dashboard, also known as `horizon `__ is a web interface that enables cloud " -"administrators and users to manage various OpenStack resources and services." -msgstr "" - -#: ../glance.rst:11 -msgid "" -"The OpenStack Image service (glance) enables users to discover, register, " -"and retrieve virtual machine images. It offers a :term:`REST ` API " -"that enables you to query virtual machine image metadata and retrieve an " -"actual image. You can store virtual machine images made available through " -"the Image service in a variety of locations, from simple file systems to " -"object-storage systems like OpenStack Object Storage." -msgstr "" - -#: ../swift.rst:7 -msgid "" -"The OpenStack Object Storage services (swift) work together to provide " -"object storage and retrieval through a :term:`REST API `. Your " -"environment must at least include the Identity service (keystone) prior to " -"deploying Object Storage." -msgstr "" - -#: ../index-debian.rst:37 -msgid "" -"The OpenStack system consists of several key projects that you install " -"separately. These projects work together depending on your cloud needs. " -"These projects include Compute, Identity Service, Networking, Image Service, " -"Block Storage, Object Storage, Telemetry, Orchestration, and Database. You " -"can install any of these projects separately and configure them stand-alone " -"or as connected entities." -msgstr "" - -#: ../heat.rst:12 -msgid "" -"The Orchestration module (heat) uses a heat orchestration template (HOT) to " -"create and manage cloud resources." -msgstr "" - -#: ../heat-verify.rst:14 -msgid "" -"The Orchestration module uses templates to describe stacks. To learn about " -"the template language, see `the Template Guide `__ in the `Heat developer " -"documentation `__." -msgstr "" - -#: ../heat-install.rst:121 -msgid "" -"The Orchestration service automatically assigns the ``heat_stack_user`` role " -"to users that it creates during stack deployment. By default, this role " -"restricts :term:`API` operations. To avoid conflicts, do not add this role " -"to users with the ``heat_stack_owner`` role." -msgstr "" - -#: ../environment-dependencies.rst:267 -msgid "The Python MySQL library is compatible with MariaDB." -msgstr "" - -#: ../glance-install.rst:246 ../glance-install.rst:310 -msgid "" -"The Telemetry chapter provides an Image service configuration that enables " -"notifications." -msgstr "" - -#: ../ceilometer-swift.rst:11 -msgid "" -"The Telemetry service requires access to the Object Storage service using " -"the ``ResellerAdmin`` role. Perform these steps on the controller node." -msgstr "" - -#: ../launch-instance-networks-public.rst:67 -msgid "" -"The ``--provider:physical_network public`` and ``--provider:network_type " -"flat`` options connect the flat virtual network to the flat (native/" -"untagged) public physical network on the ``eth1`` interface on the host " -"using information from the following files:" -msgstr "" - -#: ../launch-instance-networks-public.rst:65 -msgid "The ``--shared`` option allows all projects to use the virtual network." -msgstr "" - -#: ../launch-instance-networks-public.rst:12 -msgid "" -"The ``admin`` or other privileged user must create this network because it " -"connects directly to the physical network infrastructure." -msgstr "" - -#: ../debconf/debconf-dbconfig-common.rst:85 -msgid "" -"The ``dbconfig-common`` package will configure MySQL for these access " -"rights, and create the database for you. Since OpenStack 2014.1.1, all " -"OpenStack packages in Debian are performing the following MySQL query after " -"database creation (if you decide to use MySQL as a back-end):" -msgstr "" - -#: ../launch-instance-networks-private.rst:14 -msgid "" -"The ``demo`` or other unprivileged user can create this network because it " -"only provides connectivity to instances within the ``demo`` project." -msgstr "" - -#: ../neutron-controller-install-option2.rst:334 -msgid "" -"The ``external_network_bridge`` option intentionally lacks a value to enable " -"multiple external networks on a single agent." -msgstr "" - -# #-#-#-#-# neutron-compute-install.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# neutron-controller-install.pot (Installation Guide 0.1) #-#-#-#-# -#: ../neutron-compute-install.rst:181 ../neutron-controller-install.rst:207 -msgid "" -"The ``firewall_driver`` option uses the ``NoopFirewallDriver`` value because " -"Compute delegates security group (firewall) operation to the Networking " -"service." -msgstr "" - -#: ../debconf/debconf-api-endpoints.rst:13 -msgid "" -"The ``heat-common`` package and not the ``heat-api`` package configures the " -"Orchestration service." -msgstr "" - -#: ../swift-storage-node.rst:150 -msgid "" -"The ``rsync`` service requires no authentication, so consider running it on " -"a private network." -msgstr "" - -#: ../debconf/debconf-concepts.rst:119 -msgid "" -"The ``seen true`` option tells ``debconf`` that a specified screen was " -"already seen by the user so do not show it again. This option is useful for " -"upgrades." -msgstr "" - -#: ../swift-verify.rst:8 -msgid "" -"The ``swift`` client requires the ``-V 3`` parameter to use the Identity " -"version 3 API." -msgstr "" - -#: ../swift-initial-rings.rst:18 -msgid "" -"The account server uses the account ring to maintain lists of containers." -msgstr "" - -#: ../dashboard-install.rst:53 -msgid "" -"The automatic configuration process generates a self-signed SSL certificate. " -"Consider obtaining an official certificate for production environments." -msgstr "" - -#: ../neutron-compute-install.rst:4 -msgid "" -"The compute node handles connectivity and :term:`security groups ` for instances." -msgstr "" - -#: ../overview.rst:152 -msgid "" -"The compute node runs the :term:`hypervisor` portion of Compute that " -"operates instances. By default, Compute uses the :term:`KVM ` hypervisor. The compute node also runs a Networking service agent " -"that connects instances to virtual networks and provides firewalling " -"services to instances via :term:`security groups `." -msgstr "" - -#: ../swift-initial-rings.rst:98 -msgid "" -"The container server uses the container ring to maintain lists of objects. " -"However, it does not track object locations." -msgstr "" - -#: ../overview.rst:147 -msgid "The controller node requires a minimum of two network interfaces." -msgstr "" - -#: ../overview.rst:139 -msgid "" -"The controller node runs the Identity service, Image service, management " -"portions of Compute, management portion of Networking, various Networking " -"agents, and the dashboard. It also includes supporting services such as an " -"SQL database, :term:`message queue`, and :term:`NTP`." -msgstr "" - -#: ../dashboard-install.rst:8 -msgid "" -"The dashboard relies on functional core services including Identity, Image " -"service, Compute, and either Networking (neutron) or legacy networking (nova-" -"network). Environments with stand-alone services such as Object Storage " -"cannot use the dashboard. For more information, see the `developer " -"documentation `__." -msgstr "" - -#: ../debconf/debconf-keystone-authtoken.rst:24 -msgid "" -"The debconf system helps users configure the ``auth_uri``, ``identity_uri``, " -"``admin_tenant_name``, ``admin_user``, and ``admin_password`` options." -msgstr "" - -#: ../environment.rst:9 -msgid "" -"The draft version of this guide focuses on the future Liberty release and " -"will not work for the current Kilo release. If you want to install Kilo, you " -"must use the `Kilo version `__ of this guide " -"instead." -msgstr "" - -#: ../overview.rst:111 -msgid "" -"The example architecture requires at least two nodes (hosts) to launch a " -"basic :term:`virtual machine ` or instance. Optional " -"services such as Block Storage and Object Storage require additional nodes." -msgstr "" - -#: ../environment-networking.rst:60 -msgid "The example architectures assume use of the following networks:" -msgstr "" - -#: ../debconf/debconf-concepts.rst:105 -msgid "" -"The following example shows how to pre-seed an automated MySQL Server " -"installation:" -msgstr "" - -# #-#-#-#-# launch-instance-networks-private.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# launch-instance-networks-public.pot (Installation Guide 0.1) #-#-#-#-# -#: ../launch-instance-networks-private.rst:24 -#: ../launch-instance-networks-public.rst:17 -msgid "" -"The following instructions and diagrams use example IP address ranges. You " -"must adjust them for your particular environment." -msgstr "" - -#: ../debconf/debconf-keystone-authtoken.rst:28 -msgid "The following screens show an example Image service configuration:" -msgstr "" - -#: ../environment.rst:100 -msgid "" -"The following table provides a list of services that require passwords and " -"their associated references in the guide:" -msgstr "" - -#: ../swift-initial-rings.rst:177 -msgid "" -"The object server uses the object ring to maintain lists of object locations " -"on local devices." -msgstr "" - -#: ../environment-dependencies.rst:87 -msgid "" -"The openSUSE distribution uses the concept of patterns to represent " -"collections of packages. If you selected 'Minimal Server Selection (Text " -"Mode)' during the initial installation, you may be presented with a " -"dependency conflict when you attempt to install the OpenStack packages. To " -"avoid this, remove the minimal\\_base-conflicts package:" -msgstr "" - -#: ../overview.rst:165 -msgid "" -"The optional Block Storage node contains the disks that the Block Storage " -"service provisions for instances." -msgstr "" - -#: ../overview.rst:178 -msgid "" -"The optional Object Storage node contain the disks that the Object Storage " -"service uses for storing accounts, containers, and objects." -msgstr "" - -#: ../debconf/debconf-rabbitmq.rst:36 -msgid "The other directives concerning RabbitMQ will stay untouched." -msgstr "" - -#: ../neutron-verify-option2.rst:19 -msgid "" -"The output should indicate four agents on the controller node and one agent " -"on each compute node." -msgstr "" - -#: ../neutron-verify-option1.rst:18 -msgid "" -"The output should indicate three agents on the controller node and one agent " -"on each compute node." -msgstr "" - -#: ../environment-dependencies.rst:105 -msgid "" -"The packages are signed by GPG key 893A90DAD85F9316. You should verify the " -"fingerprint of the imported GPG key before using it." -msgstr "" - -#: ../ceilometer-controller-install.rst:35 -msgid "" -"The packages are signed by GPG key ``562111AC05905EA8``. You should verify " -"the fingerprint of the imported GPG key before using it." -msgstr "" - -#: ../keystone-services.rst:65 -msgid "" -"The packages can automatically create the service entity and API endpoint." -msgstr "" - -#: ../keystone-services.rst:24 -msgid "" -"The packages can automatically create the service entity and API endpoints." -msgstr "" - -#: ../debconf/debconf-concepts.rst:88 -msgid "" -"The packages do not require pre-depends. If ``dbconfig-common`` is already " -"installed on the system, the user sees all prompts. However, you cannot " -"define the order in which the ``debconf`` screens appear. The user must make " -"sense of it even if the prompts appear in an illogical order." -msgstr "" - -#: ../keystone-openrc.rst:4 -msgid "" -"The previous section used a combination of environment variables and command " -"options to interact with the Identity service via the ``openstack`` client. " -"To increase efficiency of client operations, OpenStack supports simple " -"client environment scripts also known as OpenRC files. These scripts " -"typically contain common options for all clients, but also support unique " -"options. For more information, see the `OpenStack User Guide `__." -msgstr "" - -#: ../launch-instance-networks-private.rst:98 -msgid "The private network uses 172.16.1.0/24 with a gateway on 172.16.1.1:" -msgstr "" - -#: ../overview.rst:199 -msgid "" -"The provider networks option deploys the OpenStack Networking service in the " -"simplest way possible with primarily layer-2 (bridging/switching) services " -"and VLAN segmentation of networks. Essentially, it bridges virtual networks " -"to physical networks and relies on physical network infrastructure for " -"layer-3 (routing) services. Additionally, a :term:`DHCP` service provides IP " -"address information to instances." -msgstr "" - -#: ../swift-controller-node.rst:17 -msgid "" -"The proxy service relies on an authentication and authorization mechanism " -"such as the Identity service. However, unlike other services, it also offers " -"an internal mechanism that allows it to operate without any other OpenStack " -"services. However, for simplicity, this guide references the Identity " -"service in :doc:`keystone`. Before you configure the Object Storage service, " -"you must create service credentials and an API endpoint." -msgstr "" - -#: ../environment-networking.rst:164 -msgid "" -"The public interface uses a special configuration without an IP address " -"assigned to it. Configure the second interface as the public interface:" -msgstr "" - -#: ../launch-instance-networks-public.rst:107 -msgid "" -"The public physical network uses 203.0.113.0/24 with a gateway on " -"203.0.113.1 and instances can use 203.0.113.101 to 203.0.113.200." -msgstr "" - -#: ../launch-instance-networks-private.rst:130 -msgid "" -"The public provider network must include the ``router: external`` option to " -"enable project routers to use it for connectivity to external networks such " -"as the Internet. The ``admin`` or other privileged user must include this " -"option during network creation or add it later. In this case, we can add it " -"to the existing ``public`` provider network." -msgstr "" - -#: ../debconf/debconf-concepts.rst:22 -msgid "" -"The rules described here are from the `Debian Policy Manual `__. If any rule described in this chapter is " -"not respected, you have found a serious bug that must be fixed." -msgstr "" - -#: ../overview.rst:223 -msgid "" -"The self-service networks option augments the provider networks option with " -"layer-3 (routing) services that enable :term:`self-service` networks using " -"overlay segmentation methods such as :term:`VXLAN`. Essentially, it routes " -"virtual networks to physical networks using :term:`NAT`. Additionally, this " -"option provides the foundation for advanced services such as LBaaS and FWaaS." -msgstr "" - -#: ../nova-compute-install.rst:144 -msgid "" -"The server component listens on all IP addresses and the proxy component " -"only listens on the management interface IP address of the compute node. The " -"base URL indicates the location where you can use a web browser to access " -"remote consoles of instances on this compute node." -msgstr "" - -# #-#-#-#-# launch-instance-private.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# launch-instance-public.pot (Installation Guide 0.1) #-#-#-#-# -#: ../launch-instance-private.rst:128 ../launch-instance-public.rst:139 -msgid "" -"The status changes from ``BUILD`` to ``ACTIVE`` when the build process " -"successfully completes." -msgstr "" - -#: ../swift-finalize-installation.rst:113 -msgid "" -"The storage node runs many Object Storage services and the :command:`swift-" -"init` command makes them easier to manage. You can ignore errors from " -"services not running on the storage node." -msgstr "" - -#: ../debconf/debconf-api-endpoints.rst:76 -msgid "" -"The values of ``AUTH_TOKEN``, ``KEYSTONE_ENDPOINT_IP``, ``PKG_ENDPOINT_IP``, " -"and ``REGION_NAME`` depend on the answer you will provide to the debconf " -"prompts. But the values of ``SERVICE_NAME``, ``SERVICE_TYPE``, " -"``SERVICE_DESC``, and ``SERVICE_URL`` are already pre-wired in each package, " -"so you don't have to remember them." -msgstr "" - -#: ../debconf/debconf-concepts.rst:42 -msgid "Then, ``debconf`` does not prompt you." -msgstr "" - -#: ../debconf/debconf-rabbitmq.rst:24 -msgid "" -"These debconf screens appear in: ``ceilometer-common``, ``cinder-common``, " -"``glance-common``, ``heat-common``, ``neutron-common``, and ``nova-common``." -msgstr "" - -#: ../debconf/debconf-dbconfig-common.rst:36 -msgid "" -"These screens appear when you re-configure the ``dbconfig-common`` package:" -msgstr "" - -#: ../debconf/debconf-dbconfig-common.rst:16 -msgid "" -"This ``connection`` directive will be handled by the ``dbconfig-common`` " -"package, which provides a standard Debian interface. It enables you to " -"configure Debian database parameters. It includes localized prompts for many " -"languages and it supports the following database backends: SQLite, MySQL, " -"and PostgreSQL." -msgstr "" - -#: ../debconf/debconf-concepts.rst:60 -msgid "" -"This calls the post-installation script for the ``PACKAGE-NAME`` package " -"after the user responds to all prompts. If you cannot install a Debian " -"package in a non-interactive way, you have found a release-critical bug in " -"Debian. Report it to the Debian bug tracking system." -msgstr "" - -#: ../neutron.rst:7 -msgid "" -"This chapter explains how to install and configure the OpenStack Networking " -"service (neutron) using the :ref:`provider networks ` or :ref:" -"`self-service networks ` option. For more information about the " -"Networking service including virtual networking components, layout, and " -"traffic flows, see the `Networking Guide `__." -msgstr "" - -#: ../debconf/debconf-concepts.rst:7 -msgid "" -"This chapter explains how to use the Debian ``debconf`` and ``dbconfig-" -"common`` packages to configure OpenStack services. These packages enable " -"users to perform configuration tasks. When users install OpenStack packages, " -"``debconf`` prompts the user for responses, which seed the contents of " -"configuration files associated with that package. After package " -"installation, users can update the configuration of a package by using the :" -"command:`dpkg-reconfigure` program." -msgstr "" - -#: ../cinder.rst:27 -msgid "" -"This chapter omits the backup manager because it depends on the Object " -"Storage service." +#: ../cinder-controller-node.rst:313 +msgid "Restart the Block Storage services:" msgstr "" +# #-#-#-#-# cinder-controller-node.pot (Installation Guide 0.1) #-#-#-#-# # #-#-#-#-# glance-install.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# keystone-users.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# launch-instance-private.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# heat-install.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# keystone-install.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# nova-compute-install.pot (Installation Guide 0.1) #-#-#-#-# # #-#-#-#-# nova-controller-install.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# swift-initial-rings.pot (Installation Guide 0.1) #-#-#-#-# -#: ../glance-install.rst:78 ../keystone-users.rst:76 ../keystone-users.rst:170 -#: ../launch-instance-private.rst:217 ../nova-controller-install.rst:74 -#: ../swift-initial-rings.rst:32 ../swift-initial-rings.rst:113 -#: ../swift-initial-rings.rst:192 -msgid "This command provides no output." +#: ../cinder-controller-node.rst:320 ../glance-install.rst:376 +#: ../heat-install.rst:474 ../keystone-install.rst:503 +#: ../nova-compute-install.rst:264 ../nova-controller-install.rst:398 +msgid "By default, the Ubuntu packages create an SQLite database." msgstr "" -#: ../keystone-verify.rst:53 -msgid "This command uses the password for the ``admin`` user." -msgstr "" - -#: ../keystone-verify.rst:75 +# #-#-#-#-# cinder-controller-node.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# glance-install.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# heat-install.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# keystone-install.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# nova-compute-install.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# nova-controller-install.pot (Installation Guide 0.1) #-#-#-#-# +#: ../cinder-controller-node.rst:322 ../glance-install.rst:378 +#: ../heat-install.rst:476 ../keystone-install.rst:505 +#: ../nova-compute-install.rst:266 ../nova-controller-install.rst:400 msgid "" -"This command uses the password for the ``demo`` user and API port 5000 which " -"only allows regular (non-admin) access to the Identity service API." +"Because this configuration uses an SQL database server, you can remove the " +"SQLite database file:" msgstr "" -#: ../overview.rst:115 +#: ../cinder-next-steps.rst:5 msgid "" -"This example architecture differs from a minimal production architecture as " -"follows:" +"Your OpenStack environment now includes Block Storage. You can :doc:`launch " +"an instance ` or add more services to your environment in " +"the following chapters." msgstr "" -#: ../horizon.rst:17 -msgid "This example deployment uses an Apache web server." -msgstr "" - -#: ../overview.rst:15 -msgid "" -"This guide covers step-by-step deployment of the following major OpenStack " -"services using a functional example architecture suitable for new users of " -"OpenStack with sufficient Linux experience:" -msgstr "" - -#: ../index-debian.rst:69 -msgid "This guide documents OpenStack Liberty release." -msgstr "" - -#: ../index-debian.rst:71 -msgid "" -"This guide is a work-in-progress and changing rapidly while we continue to " -"test and enhance the guidance. Please note where there are open \"to do\" " -"items and help where you are able." -msgstr "" - -#: ../index-debian.rst:46 -msgid "" -"This guide shows you how to install OpenStack by using packages available " -"through Fedora 22 as well as on Red Hat Enterprise Linux 7 and its " -"derivatives through the EPEL repository." -msgstr "" - -#: ../index-debian.rst:57 -msgid "" -"This guide shows you how to install OpenStack by using packages on openSUSE " -"13.2 and SUSE Linux Enterprise Server 12 through the Open Build Service " -"Cloud repository." -msgstr "" - -#: ../keystone-users.rst:87 -msgid "" -"This guide uses a service project that contains a unique user for each " -"service that you add to your environment. Create the ``service`` project:" -msgstr "" - -#: ../index-debian.rst:63 -msgid "" -"This guide walks through an installation by using packages available through " -"Debian 8 (code name: Jessie)." -msgstr "" - -#: ../index-debian.rst:52 -msgid "" -"This guide walks through an installation by using packages available through " -"Ubuntu 14.04." -msgstr "" - -#: ../debconf/debconf-keystone-authtoken.rst:44 -msgid "" -"This information is stored in the configuration file for each service. For " -"example:" -msgstr "" - -# #-#-#-#-# launch-instance-private.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# launch-instance-public.pot (Installation Guide 0.1) #-#-#-#-# -#: ../launch-instance-private.rst:47 ../launch-instance-public.rst:47 -msgid "This instance uses the ``cirros`` image." -msgstr "" - -# #-#-#-#-# launch-instance-private.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# launch-instance-public.pot (Installation Guide 0.1) #-#-#-#-# -#: ../launch-instance-private.rst:75 ../launch-instance-public.rst:78 -msgid "This instance uses the ``default`` security group." -msgstr "" - -# #-#-#-#-# launch-instance-private.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# launch-instance-public.pot (Installation Guide 0.1) #-#-#-#-# -#: ../launch-instance-private.rst:30 ../launch-instance-public.rst:30 -msgid "This instance uses the ``m1.tiny`` flavor." -msgstr "" - -#: ../launch-instance-private.rst:61 -msgid "" -"This instance uses the ``private`` project network. However, you must " -"reference this network using the ID instead of the name." -msgstr "" - -#: ../launch-instance-public.rst:60 -msgid "" -"This instance uses the ``public`` provider network. However, you must " -"reference this network using the ID instead of the name." -msgstr "" - -#: ../environment-networking.rst:66 -msgid "" -"This network requires a gateway to provide Internet access to all nodes for " -"administrative purposes such as package installation, security updates, :" -"term:`DNS`, and :term:`NTP`." -msgstr "" - -#: ../environment-networking.rst:74 -msgid "" -"This network requires a gateway to provide Internet access to instances in " -"your OpenStack environment." -msgstr "" - -#: ../overview.rst:208 -msgid "" -"This option lacks support for self-service private networks, layer-3 " -"(routing) services, and advanced services such as :term:`LBaaS` and :term:" -"`FWaaS`. Consider the self-service networks option if you desire these " -"features." -msgstr "" - -#: ../nova-verify.rst:35 -msgid "" -"This output should indicate four service components enabled on the " -"controller node and one service component enabled on the compute node." -msgstr "" - -#: ../debconf/debconf-api-endpoints.rst:41 -msgid "" -"This screen configures the IP addresses for the service. The configuration " -"script automatically detects the IP address used by the interface that is " -"connected to the default route (``/sbin/route`` and ``/sbin/ip``)." -msgstr "" - -#: ../debconf/debconf-api-endpoints.rst:52 -msgid "" -"This screen configures the region name for the service. For example, ``us-" -"east-coast`` or ``europe-paris``." -msgstr "" - -#: ../debconf/debconf-api-endpoints.rst:27 -msgid "This screen registers packages in the Identity service catalog:" -msgstr "" - -#: ../dashboard-install.rst:16 -msgid "" -"This section assumes proper installation, configuration, and operation of " -"the Identity service using the Apache HTTP server and Memcached as described " -"in the \":doc:`keystone-install`\" section." -msgstr "" - -#: ../nova-compute-install.rst:17 -msgid "" -"This section assumes that you are following the instructions in this guide " -"step-by-step to configure the first compute node. If you want to configure " -"additional compute nodes, prepare them in a similar fashion to the first " -"compute node in the :ref:`example architectures ` section. Each additional compute node requires a unique IP " -"address." -msgstr "" - -#: ../launch-instance.rst:7 -msgid "" -"This section creates the necessary virtual networks to support launching one " -"more instances. Networking option 1 includes one public virtual network and " -"one instance that uses it. Networking option 1 includes one public virtual " -"network, one private virtual network, and one instance that uses each " -"network. The instructions in this section use command-line interface (CLI) " -"tools on the controller node. For more information on the CLI tools, see the " -"`OpenStack User Guide `__. To use the dashboard, see the `OpenStack User " -"Guide `__." +#: ../cinder-storage-node.rst:3 +msgid "Install and configure a storage node" msgstr "" #: ../cinder-storage-node.rst:5 @@ -5979,440 +1097,204 @@ msgid "" "with additional storage nodes." msgstr "" -#: ../swift-storage-node.rst:5 +#: ../cinder-storage-node.rst:19 msgid "" -"This section describes how to install and configure storage nodes that " -"operate the account, container, and object services. For simplicity, this " -"configuration references two storage nodes, each containing two empty local " -"block storage devices. Each of the devices, :file:`/dev/sdb` and :file:`/dev/" -"sdc`, must contain a suitable partition table with one partition occupying " -"the entire device. Although the Object Storage service supports any file " -"system with :term:`extended attributes (xattr)`, testing and benchmarking " -"indicate the best performance and reliability on :term:`XFS`. For more " -"information on horizontally scaling your environment, see the `Deployment " -"Guide `_." +"You must configure the storage node before you install and configure the " +"volume service on it. Similar to the controller node, the storage node " +"contains one network interface on the :term:`management network`. The " +"storage node also needs an empty block storage device of suitable size for " +"your environment. For more information, see :ref:`environment`." msgstr "" -#: ../cinder-controller-node.rst:5 -msgid "" -"This section describes how to install and configure the Block Storage " -"service, code-named cinder, on the controller node. This service requires at " -"least one additional storage node that provides volumes to instances." -msgstr "" - -#: ../nova-compute-install.rst:4 -msgid "" -"This section describes how to install and configure the Compute service on a " -"compute node. The service supports several :term:`hypervisors ` " -"to deploy :term:`instances ` or :term:`VMs `. For simplicity, this configuration uses the :term:`QEMU ` hypervisor with the :term:`KVM ` " -"extension on compute nodes that support hardware acceleration for virtual " -"machines. On legacy hardware, this configuration uses the generic QEMU " -"hypervisor. You can follow these instructions with minor modifications to " -"horizontally scale your environment with additional compute nodes." -msgstr "" - -#: ../nova-controller-install.rst:4 -msgid "" -"This section describes how to install and configure the Compute service, " -"code-named nova, on the controller node." -msgstr "" - -#: ../glance-install.rst:4 -msgid "" -"This section describes how to install and configure the Image service, code-" -"named glance, on the controller node. For simplicity, this configuration " -"stores images on the local file system." -msgstr "" - -#: ../keystone-install.rst:4 -msgid "" -"This section describes how to install and configure the OpenStack Identity " -"service, code-named keystone, on the controller node. For performance, this " -"configuration deploys the Apache HTTP server to handle requests and " -"Memcached to store tokens instead of an SQL database." -msgstr "" - -#: ../heat-install.rst:5 -msgid "" -"This section describes how to install and configure the Orchestration " -"module, code-named heat, on the controller node." -msgstr "" - -#: ../ceilometer-controller-install.rst:5 -msgid "" -"This section describes how to install and configure the Telemetry module, " -"code-named ceilometer, on the controller node. The Telemetry module uses " -"separate agents to collect measurements from each OpenStack service in your " -"environment." -msgstr "" - -#: ../dashboard-install.rst:5 -msgid "" -"This section describes how to install and configure the dashboard on the " -"controller node." -msgstr "" - -#: ../swift-controller-node.rst:5 -msgid "" -"This section describes how to install and configure the proxy service that " -"handles requests for the account, container, and object services operating " -"on the storage nodes. For simplicity, this guide installs and configures the " -"proxy service on the controller node. However, you can run the proxy service " -"on any node with network connectivity to the storage nodes. Additionally, " -"you can install and configure the proxy service on multiple nodes to " -"increase performance and redundancy. For more information, see the " -"`Deployment Guide `__." -msgstr "" - -#: ../swift-verify.rst:4 -msgid "" -"This section describes how to verify operation of the Object Storage service." -msgstr "" - -#: ../heat-verify.rst:5 -msgid "" -"This section describes how to verify operation of the Orchestration module " -"(heat)." -msgstr "" - -#: ../ceilometer-verify.rst:5 -msgid "This section describes how to verify operation of the Telemetry module." -msgstr "" - -#: ../dashboard-verify.rst:5 -msgid "This section describes how to verify operation of the dashboard." -msgstr "" - -#: ../environment.rst:14 -msgid "" -"This section explains how to configure the controller and one compute node " -"using the example architecture." -msgstr "" - -#: ../overview.rst:186 -msgid "" -"This service requires two nodes. Each node requires a minimum of one network " -"interface. You can deploy more than two object storage nodes." -msgstr "" - -#: ../debconf/debconf-rabbitmq.rst:27 -msgid "" -"This will configure the below directives (example from :file:`nova.conf`):" -msgstr "" - -#: ../environment-dependencies.rst:225 -msgid "" -"Throughout the guide the OpenStack client will be used to perform actions on " -"the installed services." -msgstr "" - -# #-#-#-#-# ceilometer-nova.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# ceilometer-swift.pot (Installation Guide 0.1) #-#-#-#-# -#: ../ceilometer-nova.rst:121 ../ceilometer-swift.rst:48 -msgid "To configure notifications" -msgstr "" - -# #-#-#-#-# ceilometer-cinder.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# ceilometer-controller-install.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# ceilometer-swift.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# cinder-controller-node.pot (Installation Guide 0.1) #-#-#-#-# # #-#-#-#-# cinder-storage-node.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# heat-install.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# swift-controller-node.pot (Installation Guide 0.1) #-#-#-#-# # #-#-#-#-# swift-storage-node.pot (Installation Guide 0.1) #-#-#-#-# -#: ../ceilometer-cinder.rst:10 ../ceilometer-controller-install.rst:11 -#: ../ceilometer-swift.rst:9 ../cinder-controller-node.rst:11 -#: ../cinder-storage-node.rst:17 ../heat-install.rst:11 -#: ../swift-controller-node.rst:15 ../swift-storage-node.rst:18 -msgid "To configure prerequisites" +#: ../cinder-storage-node.rst:26 ../swift-storage-node.rst:29 +#: ../swift-storage-node.rst:39 +msgid "Configure the management interface:" msgstr "" -#: ../neutron-compute-install.rst:75 -msgid "To configure the Networking common components" +#: ../cinder-storage-node.rst:28 +msgid "IP address: 10.0.0.41" msgstr "" -#: ../dashboard-install.rst:67 -msgid "To configure the dashboard" -msgstr "" - -#: ../swift-controller-node.rst:35 -msgid "To create the Identity service credentials, complete these steps:" -msgstr "" - -#: ../keystone-install.rst:15 -msgid "To create the database, complete the following actions:" -msgstr "" - -# #-#-#-#-# cinder-controller-node.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# glance-install.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# heat-install.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# neutron-controller-install.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# nova-controller-install.pot (Installation Guide 0.1) #-#-#-#-# -#: ../cinder-controller-node.rst:16 ../glance-install.rst:16 -#: ../heat-install.rst:16 ../neutron-controller-install.rst:10 -#: ../nova-controller-install.rst:13 -msgid "To create the database, complete these steps:" -msgstr "" - -#: ../swift-initial-rings.rst:20 ../swift-initial-rings.rst:101 -#: ../swift-initial-rings.rst:180 -msgid "To create the ring perform the following steps on the controller node." -msgstr "" - -# #-#-#-#-# ceilometer-controller-install.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# cinder-controller-node.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# glance-install.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# heat-install.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# neutron-controller-install.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# nova-controller-install.pot (Installation Guide 0.1) #-#-#-#-# -#: ../ceilometer-controller-install.rst:229 ../cinder-controller-node.rst:51 -#: ../glance-install.rst:51 ../heat-install.rst:47 -#: ../neutron-controller-install.rst:44 ../nova-controller-install.rst:48 -msgid "To create the service credentials, complete these steps:" -msgstr "" - -#: ../environment.rst:86 -msgid "" -"To ease the installation process, this guide only covers password security " -"where applicable. You can create secure passwords manually, generate them " -"using a tool such as `pwgen `__, or " -"by running the following command:" -msgstr "" - -#: ../environment-ntp-controller.rst:80 -msgid "" -"To enable other nodes to connect to the chrony daemon on the controller, add " -"the following key to :file:`/etc/chrony.conf`:" -msgstr "" - -# #-#-#-#-# ceilometer-controller-install.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# ceilometer-nova.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# cinder-controller-node.pot (Installation Guide 0.1) #-#-#-#-# # #-#-#-#-# cinder-storage-node.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# dashboard-install.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# environment-dependencies.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# heat-install.pot (Installation Guide 0.1) #-#-#-#-# -#: ../ceilometer-controller-install.rst:468 ../ceilometer-nova.rst:170 -#: ../cinder-controller-node.rst:298 ../cinder-storage-node.rst:349 -#: ../dashboard-install.rst:138 ../environment-dependencies.rst:355 -#: ../heat-install.rst:391 -msgid "To finalize installation" +# #-#-#-#-# environment-networking-compute.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# environment-networking-controller.pot (Installation Guide 0.1) #-#-#-#-# +#: ../cinder-storage-node.rst:30 ../environment-networking-compute.rst:11 +#: ../environment-networking-controller.rst:11 +msgid "Network mask: 255.255.255.0 (or /24)" msgstr "" -#: ../cinder-controller-node.rst:163 -msgid "To install and configure Block Storage controller components" +# #-#-#-#-# cinder-storage-node.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# environment-networking-compute.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# environment-networking-controller.pot (Installation Guide 0.1) #-#-#-#-# +#: ../cinder-storage-node.rst:32 ../environment-networking-compute.rst:13 +#: ../environment-networking-controller.rst:13 +msgid "Default gateway: 10.0.0.1" msgstr "" -#: ../heat-install.rst:196 -msgid "To install and configure the Orchestration components" +#: ../cinder-storage-node.rst:34 +msgid "Set the hostname of the node to ``block1``." msgstr "" -#: ../ceilometer-controller-install.rst:300 -msgid "To install and configure the Telemetry module components" -msgstr "" - -#: ../ceilometer-nova.rst:9 -msgid "To install and configure the agent" -msgstr "" - -#: ../swift-controller-node.rst:106 -msgid "To install and configure the controller node components" -msgstr "" - -#: ../dashboard-install.rst:21 -msgid "To install the dashboard components" -msgstr "" - -# #-#-#-#-# launch-instance-private.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# launch-instance-public.pot (Installation Guide 0.1) #-#-#-#-# -#: ../launch-instance-private.rst:9 ../launch-instance-public.rst:9 +#: ../cinder-storage-node.rst:36 msgid "" -"To launch an instance, you must at least specify the flavor, image name, " -"network, security group, key, and instance name." +"Copy the contents of the :file:`/etc/hosts` file from the controller node to " +"the storage node and add the following to it::" msgstr "" -#: ../environment.rst:46 +# #-#-#-#-# cinder-storage-node.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# swift-storage-node.pot (Installation Guide 0.1) #-#-#-#-# +#: ../cinder-storage-node.rst:42 ../swift-storage-node.rst:61 msgid "" -"To minimize clutter and provide more resources for OpenStack, we recommend a " -"minimal installation of your Linux distribution. Also, you must install a 64-" -"bit version of your distribution on each node." +"Also add this content to the :file:`/etc/hosts` file on all other nodes in " +"your environment." msgstr "" -#: ../debconf/debconf-concepts.rst:35 +# #-#-#-#-# cinder-storage-node.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# swift-storage-node.pot (Installation Guide 0.1) #-#-#-#-# +#: ../cinder-storage-node.rst:45 ../swift-storage-node.rst:64 msgid "" -"To opt out of using the ``debconf`` package, run the :command:`dpkg-" -"reconfigure` command and select non-interactive mode:" +"Install and configure :term:`NTP` using the instructions in :ref:" +"`environment-ntp`." msgstr "" -#: ../ceilometer-glance.rst:5 +#: ../cinder-storage-node.rst:50 ../cinder-storage-node.rst:61 +#: ../cinder-storage-node.rst:88 msgid "" -"To retrieve image-oriented events and samples, configure the Image service " -"to send notifications to the message bus. Perform these steps on the " -"controller node." +"If you intend to use non-raw image types such as QCOW2 and VMDK, install the " +"QEMU support package:" msgstr "" -#: ../ceilometer-swift.rst:5 +#: ../cinder-storage-node.rst:57 ../cinder-storage-node.rst:68 +#: ../cinder-storage-node.rst:99 +msgid "Install the LVM packages:" +msgstr "" + +#: ../cinder-storage-node.rst:76 ../cinder-storage-node.rst:97 +#: ../cinder-storage-node.rst:107 +msgid "Some distributions include LVM by default." +msgstr "" + +#: ../cinder-storage-node.rst:78 msgid "" -"To retrieve storage-oriented events and samples, configure the Object " -"Storage service to send notifications to the message bus." +"Start the LVM metadata service and configure it to start when the system " +"boots:" msgstr "" -#: ../ceilometer-cinder.rst:5 +#: ../cinder-storage-node.rst:110 +msgid "Create the LVM physical volume :file:`/dev/sdb1`:" +msgstr "" + +#: ../cinder-storage-node.rst:119 msgid "" -"To retrieve volume-oriented events and samples, you must configure the Block " -"Storage service to send notifications to the message bus. Perform these " -"steps on the controller and storage nodes." +"If your system uses a different device name, adjust these steps accordingly." msgstr "" -#: ../keystone-openrc.rst:55 +#: ../cinder-storage-node.rst:122 +msgid "Create the LVM volume group ``cinder-volumes``:" +msgstr "" + +#: ../cinder-storage-node.rst:129 +msgid "The Block Storage service creates logical volumes in this volume group." +msgstr "" + +#: ../cinder-storage-node.rst:131 msgid "" -"To run clients as a specific project and user, you can simply load the " -"associated client environment script prior to running them. For example:" +"Only instances can access Block Storage volumes. However, the underlying " +"operating system manages the devices associated with the volumes. By " +"default, the LVM volume scanning tool scans the :file:`/dev` directory for " +"block storage devices that contain volumes. If projects use LVM on their " +"volumes, the scanning tool detects these volumes and attempts to cache them " +"which can cause a variety of problems with both the underlying operating " +"system and project volumes. You must reconfigure LVM to scan only the " +"devices that contain the ``cinder-volume`` volume group. Edit the :file:`/" +"etc/lvm/lvm.conf` file and complete the following actions:" msgstr "" -#: ../dashboard-next-step.rst:24 +#: ../cinder-storage-node.rst:142 msgid "" -"To use the VNC client with the dashboard, the browser must support HTML5 " -"Canvas and HTML5 WebSockets." +"In the ``devices`` section, add a filter that accepts the :file:`/dev/sdb` " +"device and rejects all other devices::" msgstr "" -#: ../dashboard-install.rst:61 +#: ../cinder-storage-node.rst:149 msgid "" -"Ubuntu installs the ``openstack-dashboard-ubuntu-theme`` package as a " -"dependency. Some users reported issues with this theme in previous releases. " -"If you encounter issues, remove this package to restore the original " -"OpenStack theme." +"Each item in the filter array begins with ``a`` for **accept** or ``r`` for " +"**reject** and includes a regular expression for the device name. The array " +"must end with ``r/.*/`` to reject any remaining devices. You can use the :" +"command:`vgs -vvvv` command to test filters." msgstr "" -#: ../debconf/debconf-api-endpoints.rst:46 -msgid "Unless you have a unique set up for your network, press **ENTER**." -msgstr "" - -#: ../environment-networking.rst:90 +#: ../cinder-storage-node.rst:157 msgid "" -"Unless you intend to use the exact configuration provided in this example " -"architecture, you must modify the networks in this procedure to match your " -"environment. Also, each node must resolve the other nodes by name in " -"addition to IP address. For example, the ``controller`` name must resolve to " -"``10.0.0.11``, the IP address of the management interface on the controller " -"node." +"If your storage nodes use LVM on the operating system disk, you must also " +"add the associated device to the filter. For example, if the :file:`/dev/" +"sda` device contains the operating system:" msgstr "" -#: ../debconf/debconf-dbconfig-common.rst:46 +#: ../cinder-storage-node.rst:165 msgid "" -"Unlike other debconf prompts, you cannot pre-seed the responses for the " -"``dbconfig-common`` prompts by using ``debconf-set-selections``. Instead, " -"you must create a file in :file:`/etc/dbconfig-common`. For example, you " -"might create a keystone configuration file for ``dbconfig-common`` that is " -"located in :file:`/etc/dbconfig-common/keystone.conf`, as follows:" +"Similarly, if your compute nodes use LVM on the operating system disk, you " +"must also modify the filter in the :file:`/etc/lvm/lvm.conf` file on those " +"nodes to include only the operating system disk. For example, if the :file:`/" +"dev/sda` device contains the operating system:" msgstr "" -#: ../keystone-verify.rst:27 -msgid "Unset the temporary ``OS_TOKEN`` and ``OS_URL`` environment variables:" +#: ../cinder-storage-node.rst:176 +msgid "Install and configure Block Storage volume components" msgstr "" -#: ../environment-dependencies.rst:150 ../environment-dependencies.rst:163 -#: ../environment-dependencies.rst:176 -msgid "Upgrade the packages on your system:" +# #-#-#-#-# cinder-storage-node.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# nova-compute-install.pot (Installation Guide 0.1) #-#-#-#-# +#: ../cinder-storage-node.rst:266 ../nova-compute-install.rst:102 +msgid "In the ``[DEFAULT]`` section, configure the ``my_ip`` option:" msgstr "" -#: ../swift-verify.rst:34 -msgid "Upload a test file:" -msgstr "" - -#: ../glance-verify.rst:36 +#: ../cinder-storage-node.rst:274 msgid "" -"Upload the image to the Image service using the :term:`QCOW2 ` disk format, :term:`bare` container format, and public " -"visibility so all projects can access it:" +"Replace ``MANAGEMENT_INTERFACE_IP_ADDRESS`` with the IP address of the " +"management network interface on your storage node, typically 10.0.0.41 for " +"the first node in the :ref:`example architecture `." msgstr "" -#: ../heat-verify.rst:51 +#: ../cinder-storage-node.rst:281 ../cinder-storage-node.rst:296 msgid "" -"Use the :command:`heat stack-create` command to create a stack from the " -"template:" +"In the ``[lvm]`` section, configure the LVM back end with the LVM driver, " +"``cinder-volumes`` volume group, iSCSI protocol, and appropriate iSCSI " +"service:" msgstr "" -#: ../heat-verify.rst:65 +#: ../cinder-storage-node.rst:309 +msgid "In the ``[DEFAULT]`` section, enable the LVM back end:" +msgstr "" + +#: ../cinder-storage-node.rst:319 msgid "" -"Use the :command:`heat stack-list` command to verify successful creation of " -"the stack:" +"Back-end names are arbitrary. As an example, this guide uses the name of the " +"driver as the name of the back end." msgstr "" -#: ../ceilometer-cinder.rst:53 +#: ../cinder-storage-node.rst:322 msgid "" -"Use the ``cinder-volume-usage-audit`` command to retrieve meters on demand. " -"For more information, see `Block Storage audit script setup to get " -"notifications `__." +"In the ``[DEFAULT]`` section, configure the location of the Image service:" msgstr "" -# #-#-#-#-# cinder-controller-node.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# glance-install.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# heat-install.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# keystone-install.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# neutron-controller-install.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# nova-controller-install.pot (Installation Guide 0.1) #-#-#-#-# -#: ../cinder-controller-node.rst:18 ../glance-install.rst:18 -#: ../heat-install.rst:18 ../keystone-install.rst:17 -#: ../neutron-controller-install.rst:12 ../nova-controller-install.rst:15 +#: ../cinder-storage-node.rst:353 ../cinder-storage-node.rst:363 msgid "" -"Use the database access client to connect to the database server as the " -"``root`` user:" +"Start the Block Storage volume service including its dependencies and " +"configure them to start when the system boots:" msgstr "" -#: ../keystone-install.rst:227 +#: ../cinder-storage-node.rst:373 +msgid "Restart the Block Storage volume service including its dependencies:" +msgstr "" + +#: ../cinder-storage-node.rst:380 msgid "" -"Use the random value that you generated in a previous step. If you install " -"using non-interactive mode or you do not specify this token, the " -"configuration tool generates a random value." -msgstr "" - -#: ../neutron-verify.rst:45 -msgid "" -"Use the verification section for the networking option that you chose to " -"deploy." -msgstr "" - -#: ../keystone-openrc.rst:53 -msgid "Using the scripts" -msgstr "" - -#: ../launch-instance-private.rst:157 -msgid "Verify access to the ``private`` project network gateway:" -msgstr "" - -# #-#-#-#-# launch-instance-private.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# launch-instance-public.pot (Installation Guide 0.1) #-#-#-#-# -#: ../launch-instance-private.rst:172 ../launch-instance-public.rst:183 -msgid "Verify access to the internet:" -msgstr "" - -#: ../launch-instance-public.rst:168 -msgid "Verify access to the public provider network gateway:" -msgstr "" - -#: ../launch-instance.rst:63 -msgid "Verify addition of the key pair:" -msgstr "" - -#: ../environment-networking.rst:237 -msgid "Verify connectivity" -msgstr "" - -#: ../launch-instance-public.rst:201 -msgid "" -"Verify connectivity to the instance from the controller node or any host on " -"the public physical network:" -msgstr "" - -#: ../launch-instance-private.rst:231 -msgid "" -"Verify connectivity to the instance via floating IP address from the " -"controller node or any host on the public physical network:" +"By default, the Ubuntu packages create an SQLite database. Because this " +"configuration uses an SQL database server, remove the SQLite database file:" msgstr "" # #-#-#-#-# cinder-verify.pot (Installation Guide 0.1) #-#-#-#-# @@ -6436,49 +1318,280 @@ msgstr "" msgid "Verify operation of the Block Storage service." msgstr "" -#: ../nova-verify.rst:4 -msgid "Verify operation of the Compute service." +# #-#-#-#-# cinder-verify.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# nova-verify.pot (Installation Guide 0.1) #-#-#-#-# +#: ../cinder-verify.rst:11 ../nova-verify.rst:8 +msgid "Perform these commands on the controller node." msgstr "" -#: ../keystone-verify.rst:4 +#: ../cinder-verify.rst:13 msgid "" -"Verify operation of the Identity service before installing other services." +"In each client environment script, configure the Block Storage client to use " +"API version 2.0:" msgstr "" -#: ../glance-verify.rst:4 +#: ../cinder-verify.rst:27 +msgid "List service components to verify successful launch of each process:" +msgstr "" + +#: ../cinder.rst:3 +msgid "Add the Block Storage service" +msgstr "" + +#: ../cinder.rst:13 msgid "" -"Verify operation of the Image service using `CirrOS `__, a small Linux image that helps you test your OpenStack " -"deployment." +"The OpenStack Block Storage service provides block storage devices to guest " +"instances. The method in which the storage is provisioned and consumed is " +"determined by the Block Storage driver, or drivers in the case of a multi-" +"backend configuration. There are a variety of drivers that are available: " +"NAS/SAN, NFS, iSCSI, Ceph, and more. The Block Storage API and scheduler " +"services typically run on the controller nodes. Depending upon the drivers " +"used, the volume service can run on controllers, compute nodes, or " +"standalone storage nodes. For more information, see the `Configuration " +"Reference `__." msgstr "" -#: ../ceilometer-verify.rst:3 -msgid "Verify the Telemetry installation" -msgstr "" - -#: ../swift-initial-rings.rst:71 ../swift-initial-rings.rst:152 -#: ../swift-initial-rings.rst:230 -msgid "Verify the ring contents:" -msgstr "" - -#: ../environment-ntp-verify.rst:6 +#: ../cinder.rst:27 msgid "" -"We recommend that you verify NTP synchronization before proceeding further. " -"Some nodes, particularly those that reference the controller node, can take " -"several minutes to synchronize." +"This chapter omits the backup manager because it depends on the Object " +"Storage service." msgstr "" -#: ../environment-networking.rst:239 -msgid "" -"We recommend that you verify network connectivity to the Internet and among " -"the nodes before proceeding further." +# #-#-#-#-# dashboard-install.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# glance-install.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# keystone-install.pot (Installation Guide 0.1) #-#-#-#-# +#: ../dashboard-install.rst:3 ../glance-install.rst:2 +#: ../keystone-install.rst:2 +msgid "Install and configure" msgstr "" -#: ../launch-instance-networks-private.rst:191 +#: ../dashboard-install.rst:5 msgid "" -"We recommend that you verify operation and fix any issues before proceeding " -"The following steps use the IP address ranges from the network and subnet " -"creation examples." +"This section describes how to install and configure the dashboard on the " +"controller node." +msgstr "" + +#: ../dashboard-install.rst:8 +msgid "" +"The dashboard relies on functional core services including Identity, Image " +"service, Compute, and either Networking (neutron) or legacy networking (nova-" +"network). Environments with stand-alone services such as Object Storage " +"cannot use the dashboard. For more information, see the `developer " +"documentation `__." +msgstr "" + +#: ../dashboard-install.rst:16 +msgid "" +"This section assumes proper installation, configuration, and operation of " +"the Identity service using the Apache HTTP server and Memcached as described " +"in the \":doc:`keystone-install`\" section." +msgstr "" + +#: ../dashboard-install.rst:21 +msgid "To install the dashboard components" +msgstr "" + +#: ../dashboard-install.rst:25 ../dashboard-install.rst:32 +#: ../dashboard-install.rst:39 ../dashboard-install.rst:45 +msgid "Install the packages::" +msgstr "" + +#: ../dashboard-install.rst:49 +msgid "Respond to prompts for web server configuration." +msgstr "" + +#: ../dashboard-install.rst:53 +msgid "" +"The automatic configuration process generates a self-signed SSL certificate. " +"Consider obtaining an official certificate for production environments." +msgstr "" + +#: ../dashboard-install.rst:61 +msgid "" +"Ubuntu installs the ``openstack-dashboard-ubuntu-theme`` package as a " +"dependency. Some users reported issues with this theme in previous releases. " +"If you encounter issues, remove this package to restore the original " +"OpenStack theme." +msgstr "" + +#: ../dashboard-install.rst:67 +msgid "To configure the dashboard" +msgstr "" + +#: ../dashboard-install.rst:71 +msgid "Configure the web server::" +msgstr "" + +#: ../dashboard-install.rst:79 +msgid "" +"Edit the :file:`/srv/www/openstack-dashboard/openstack_dashboard/local/" +"local_settings.py` file and complete the following actions:" +msgstr "" + +#: ../dashboard-install.rst:85 +msgid "" +"Edit the :file:`/etc/openstack-dashboard/local_settings.py` file and " +"complete the following actions:" +msgstr "" + +#: ../dashboard-install.rst:89 +msgid "" +"Configure the dashboard to use OpenStack services on the ``controller`` " +"node::" +msgstr "" + +#: ../dashboard-install.rst:94 +msgid "Allow all hosts to access the dashboard::" +msgstr "" + +#: ../dashboard-install.rst:98 +msgid "Configure the ``memcached`` session storage service::" +msgstr "" + +#: ../dashboard-install.rst:109 +msgid "Comment out any other session storage configuration." +msgstr "" + +#: ../dashboard-install.rst:115 +msgid "" +"By default, SLES and openSUSE use an SQL database for session storage. For " +"simplicity, we recommend changing the configuration to use ``memcached`` for " +"session storage." +msgstr "" + +#: ../dashboard-install.rst:119 +msgid "" +"Configure ``user`` as the default role for users that you create via the " +"dashboard::" +msgstr "" + +#: ../dashboard-install.rst:124 +msgid "Optionally, configure the time zone::" +msgstr "" + +#: ../dashboard-install.rst:128 +msgid "" +"Replace ``TIME_ZONE`` with an appropriate time zone identifier. For more " +"information, see the `list of time zones `__." +msgstr "" + +#: ../dashboard-install.rst:137 +msgid "" +"On RHEL and CentOS, configure SELinux to permit the web server to connect to " +"OpenStack services::" +msgstr "" + +#: ../dashboard-install.rst:144 +msgid "" +"Due to a packaging bug, the dashboard CSS fails to load properly. Run the " +"following command to resolve this issue::" +msgstr "" + +#: ../dashboard-install.rst:149 +msgid "" +"For more information, see the `bug report `__." +msgstr "" + +#: ../dashboard-install.rst:154 +msgid "Reload the web server configuration::" +msgstr "" + +#: ../dashboard-install.rst:160 ../dashboard-install.rst:172 +msgid "" +"Start the web server and session storage service and configure them to start " +"when the system boots::" +msgstr "" + +#: ../dashboard-install.rst:168 ../dashboard-install.rst:180 +msgid "Restart the Apache HTTP service if it is already running." +msgstr "" + +#: ../dashboard-next-step.rst:5 +msgid "" +"Your OpenStack environment now includes the dashboard. You can :ref:`launch-" +"instance` or add more services to your environment." +msgstr "" + +#: ../dashboard-next-step.rst:8 +msgid "" +"After you install and configure the dashboard, you can complete the " +"following tasks:" +msgstr "" + +#: ../dashboard-next-step.rst:11 +msgid "" +"Provide users with a public IP address, a username, and a password so they " +"can access the dashboard through a web browser. In case of any SSL " +"certificate connection problems, point the server IP address to a domain " +"name, and give users access." +msgstr "" + +#: ../dashboard-next-step.rst:16 +msgid "" +"Customize your dashboard. See section `Customize the dashboard `__." +msgstr "" + +#: ../dashboard-next-step.rst:20 +msgid "" +"Set up session storage. See `Set up session storage for the dashboard " +"`__." +msgstr "" + +#: ../dashboard-next-step.rst:24 +msgid "" +"To use the VNC client with the dashboard, the browser must support HTML5 " +"Canvas and HTML5 WebSockets." +msgstr "" + +#: ../dashboard-next-step.rst:27 +msgid "" +"For details about browsers that support noVNC, see `README `__ and `browser support `__." +msgstr "" + +#: ../dashboard-verify.rst:5 +msgid "This section describes how to verify operation of the dashboard." +msgstr "" + +#: ../dashboard-verify.rst:9 +msgid "Access the dashboard using a web browser at ``http://controller/``." +msgstr "" + +#: ../dashboard-verify.rst:14 +msgid "" +"Access the dashboard using a web browser at ``http://controller/dashboard``." +msgstr "" + +#: ../dashboard-verify.rst:19 +msgid "" +"Access the dashboard using a web browser at ``http://controller/horizon``." +msgstr "" + +#: ../dashboard-verify.rst:22 +msgid "Authenticate using ``admin`` or ``demo`` user credentials." +msgstr "" + +#: ../debconf/debconf-api-endpoints.rst:5 +msgid "Register API endpoints" +msgstr "" + +#: ../debconf/debconf-api-endpoints.rst:7 +msgid "" +"All Debian packages for API services, except the ``heat-api`` package, " +"register the service in the Identity service catalog. This feature is " +"helpful because API endpoints are difficult to remember." +msgstr "" + +#: ../debconf/debconf-api-endpoints.rst:13 +msgid "" +"The ``heat-common`` package and not the ``heat-api`` package configures the " +"Orchestration service." msgstr "" #: ../debconf/debconf-api-endpoints.rst:16 @@ -6491,6 +1604,81 @@ msgid "" "respond ``no`` when you upgrade." msgstr "" +#: ../debconf/debconf-api-endpoints.rst:27 +msgid "This screen registers packages in the Identity service catalog:" +msgstr "" + +#: ../debconf/debconf-api-endpoints.rst:33 +msgid "" +"You are prompted for the Identity service ``admin_token`` value. The " +"Identity Service uses this value to register the API service. When you set " +"up the ``keystone`` package, this value is configured automatically." +msgstr "" + +#: ../debconf/debconf-api-endpoints.rst:41 +msgid "" +"This screen configures the IP addresses for the service. The configuration " +"script automatically detects the IP address used by the interface that is " +"connected to the default route (``/sbin/route`` and ``/sbin/ip``)." +msgstr "" + +#: ../debconf/debconf-api-endpoints.rst:46 +msgid "Unless you have a unique set up for your network, press **ENTER**." +msgstr "" + +#: ../debconf/debconf-api-endpoints.rst:52 +msgid "" +"This screen configures the region name for the service. For example, ``us-" +"east-coast`` or ``europe-paris``." +msgstr "" + +#: ../debconf/debconf-api-endpoints.rst:59 +msgid "" +"The Debian package post installation scripts will then perform the below " +"commands for you:" +msgstr "" + +#: ../debconf/debconf-api-endpoints.rst:76 +msgid "" +"The values of ``AUTH_TOKEN``, ``KEYSTONE_ENDPOINT_IP``, ``PKG_ENDPOINT_IP``, " +"and ``REGION_NAME`` depend on the answer you will provide to the debconf " +"prompts. But the values of ``SERVICE_NAME``, ``SERVICE_TYPE``, " +"``SERVICE_DESC``, and ``SERVICE_URL`` are already pre-wired in each package, " +"so you don't have to remember them." +msgstr "" + +#: ../debconf/debconf-concepts.rst:5 +msgid "debconf concepts" +msgstr "" + +#: ../debconf/debconf-concepts.rst:7 +msgid "" +"This chapter explains how to use the Debian ``debconf`` and ``dbconfig-" +"common`` packages to configure OpenStack services. These packages enable " +"users to perform configuration tasks. When users install OpenStack packages, " +"``debconf`` prompts the user for responses, which seed the contents of " +"configuration files associated with that package. After package " +"installation, users can update the configuration of a package by using the :" +"command:`dpkg-reconfigure` program." +msgstr "" + +#: ../debconf/debconf-concepts.rst:15 +msgid "" +"If you are familiar with these packages and pre-seeding, you can proceed to :" +"doc:`../keystone`." +msgstr "" + +#: ../debconf/debconf-concepts.rst:20 +msgid "The Debian packages" +msgstr "" + +#: ../debconf/debconf-concepts.rst:22 +msgid "" +"The rules described here are from the `Debian Policy Manual `__. If any rule described in this chapter is " +"not respected, you have found a serious bug that must be fixed." +msgstr "" + #: ../debconf/debconf-concepts.rst:27 msgid "" "When you install or upgrade a Debian package, all configuration file values " @@ -6502,51 +1690,68 @@ msgid "" "configuration file." msgstr "" -#: ../ceilometer-nova.rst:163 +#: ../debconf/debconf-concepts.rst:35 msgid "" -"While you can use a customised notification_driver, we recommend using the " -"default settings. Using stable web hooks for events, such as creating new " -"instances, and using custom notification drivers are not guaranteed to " -"deliver notifications in real-time." +"To opt out of using the ``debconf`` package, run the :command:`dpkg-" +"reconfigure` command and select non-interactive mode:" msgstr "" -#: ../debconf/debconf-api-endpoints.rst:33 -msgid "" -"You are prompted for the Identity service ``admin_token`` value. The " -"Identity Service uses this value to register the API service. When you set " -"up the ``keystone`` package, this value is configured automatically." +#: ../debconf/debconf-concepts.rst:42 +msgid "Then, ``debconf`` does not prompt you." msgstr "" -#: ../ceilometer-controller-install.rst:92 -#: ../ceilometer-controller-install.rst:129 -#: ../ceilometer-controller-install.rst:173 +#: ../debconf/debconf-concepts.rst:44 msgid "" -"You can also disable journaling. For more information, see the `MongoDB " -"manual `__." +"Another way to disable the ``debconf`` package is to prefix the :command:" +"`apt` command with ``DEBIAN_FRONTEND=noninteractive``, as follows:" msgstr "" -# #-#-#-#-# launch-instance-private.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# launch-instance-public.pot (Installation Guide 0.1) #-#-#-#-# -#: ../launch-instance-private.rst:34 ../launch-instance-public.rst:34 -msgid "You can also reference a flavor by ID." +#: ../debconf/debconf-concepts.rst:52 +msgid "" +"If you configure a package with ``debconf`` incorrectly, you can re-" +"configure it, as follows:" msgstr "" -#: ../overview.rst:172 +#: ../debconf/debconf-concepts.rst:60 msgid "" -"You can deploy more than one block storage node. Each node requires a " -"minimum of one network interface." +"This calls the post-installation script for the ``PACKAGE-NAME`` package " +"after the user responds to all prompts. If you cannot install a Debian " +"package in a non-interactive way, you have found a release-critical bug in " +"Debian. Report it to the Debian bug tracking system." msgstr "" -#: ../overview.rst:159 +#: ../debconf/debconf-concepts.rst:65 msgid "" -"You can deploy more than one compute node. Each node requires a minimum of " -"two network interfaces." +"Generally, the ``-common`` packages install the configuration files. For " +"example, the ``glance-common`` package installs the :file:`glance-api.conf` " +"and :file:`glance-registry.conf` files. So, for the Image service, you must " +"re-configure the ``glance-common`` package. The same applies for ``cinder-" +"common``, ``nova-common``, and ``heat-common`` packages." msgstr "" -#: ../environment-networking.rst:77 +#: ../debconf/debconf-concepts.rst:71 msgid "" -"You can modify these ranges and gateways to work with your particular " -"network infrastructure." +"In ``debconf``, the higher the priority for a screen, the greater the chance " +"that the user sees that screen. If a ``debconf`` screen has ``medium`` " +"priority and you configure the Debian system to show only ``critical`` " +"prompts, which is the default in Debian, the user does not see that " +"``debconf`` screen. Instead, the default for the related package is used. In " +"the Debian OpenStack packages, a number of ``debconf`` screens are set with " +"``medium`` priority. Consequently, if you want to respond to all ``debconf`` " +"screens from the Debian OpenStack packages, you must run the following " +"command and select the ``medium`` priority before you install any packages:" +msgstr "" + +#: ../debconf/debconf-concepts.rst:88 +msgid "" +"The packages do not require pre-depends. If ``dbconfig-common`` is already " +"installed on the system, the user sees all prompts. However, you cannot " +"define the order in which the ``debconf`` screens appear. The user must make " +"sense of it even if the prompts appear in an illogical order." +msgstr "" + +#: ../debconf/debconf-concepts.rst:97 +msgid "Pre-seed debconf prompts" msgstr "" #: ../debconf/debconf-concepts.rst:99 @@ -6558,41 +1763,114 @@ msgid "" "the services." msgstr "" -#: ../keystone-users.rst:174 -msgid "You can repeat this procedure to create additional projects and users." -msgstr "" - -#: ../launch-instance-networks-private.rst:19 +#: ../debconf/debconf-concepts.rst:105 msgid "" -"You must :ref:`create the public provider network ` before the private project network." +"The following example shows how to pre-seed an automated MySQL Server " +"installation:" msgstr "" -#: ../heat-install.rst:104 -msgid "You must add the ``heat_stack_owner`` role to users that manage stacks." -msgstr "" - -#: ../swift-storage-node.rst:20 +#: ../debconf/debconf-concepts.rst:119 msgid "" -"You must configure each storage node before you install and configure the " -"Object Storage service on it. Similar to the controller node, each storage " -"node contains one network interface on the :term:`management network`. " -"Optionally, each storage node can contain a second network interface on a " -"separate network for replication. For more information, see :ref:" -"`environment`." +"The ``seen true`` option tells ``debconf`` that a specified screen was " +"already seen by the user so do not show it again. This option is useful for " +"upgrades." msgstr "" -#: ../cinder-storage-node.rst:19 +#: ../debconf/debconf-dbconfig-common.rst:5 +msgid "Configure the database with dbconfig-common" +msgstr "" + +#: ../debconf/debconf-dbconfig-common.rst:7 msgid "" -"You must configure the storage node before you install and configure the " -"volume service on it. Similar to the controller node, the storage node " -"contains one network interface on the :term:`management network`. The " -"storage node also needs an empty block storage device of suitable size for " -"your environment. For more information, see :ref:`environment`." +"Many of the OpenStack services need to be configured to access a database. " +"These are configured through a DSN (Database Source Name) directive as " +"follows:" msgstr "" -#: ../launch-instance-cinder.rst:121 -msgid "You must create a partition table and file system to use the volume." +#: ../debconf/debconf-dbconfig-common.rst:16 +msgid "" +"This ``connection`` directive will be handled by the ``dbconfig-common`` " +"package, which provides a standard Debian interface. It enables you to " +"configure Debian database parameters. It includes localized prompts for many " +"languages and it supports the following database backends: SQLite, MySQL, " +"and PostgreSQL." +msgstr "" + +#: ../debconf/debconf-dbconfig-common.rst:22 +msgid "" +"By default, the ``dbconfig-common`` package configures the OpenStack " +"services to use SQLite. So if you use debconf in non-interactive mode and " +"without pre-seeding, the OpenStack services that you install will use SQLite." +msgstr "" + +#: ../debconf/debconf-dbconfig-common.rst:27 +msgid "" +"By default, ``dbconfig-common`` does not provide access to database servers " +"over a network. If you want the ``dbconfig-common`` package to prompt for " +"remote database servers that are accessed over a network and not through a " +"UNIX socket file, reconfigure it, as follows:" +msgstr "" + +#: ../debconf/debconf-dbconfig-common.rst:36 +msgid "" +"These screens appear when you re-configure the ``dbconfig-common`` package:" +msgstr "" + +#: ../debconf/debconf-dbconfig-common.rst:46 +msgid "" +"Unlike other debconf prompts, you cannot pre-seed the responses for the " +"``dbconfig-common`` prompts by using ``debconf-set-selections``. Instead, " +"you must create a file in :file:`/etc/dbconfig-common`. For example, you " +"might create a keystone configuration file for ``dbconfig-common`` that is " +"located in :file:`/etc/dbconfig-common/keystone.conf`, as follows:" +msgstr "" + +#: ../debconf/debconf-dbconfig-common.rst:70 +msgid "After you create this file, run this command:" +msgstr "" + +#: ../debconf/debconf-dbconfig-common.rst:76 +msgid "" +"The Identity service is installed with MySQL as the database back end, " +"``keystonedb`` as database name, and the localhost socket file. The " +"corresponding DNS will then be:" +msgstr "" + +#: ../debconf/debconf-dbconfig-common.rst:85 +msgid "" +"The ``dbconfig-common`` package will configure MySQL for these access " +"rights, and create the database for you. Since OpenStack 2014.1.1, all " +"OpenStack packages in Debian are performing the following MySQL query after " +"database creation (if you decide to use MySQL as a back-end):" +msgstr "" + +#: ../debconf/debconf-dbconfig-common.rst:94 +msgid "" +"So, if using Debian, you wont need to care about database creation, access " +"rights and character sets. All that is handled for you by the packages." +msgstr "" + +#: ../debconf/debconf-dbconfig-common.rst:98 +msgid "As an example, here are screenshots from the ``cinder-common`` package:" +msgstr "" + +#: ../debconf/debconf-dbconfig-common.rst:124 +msgid "" +"By default in Debian, you can access the MySQL server from either localhost " +"through the socket file or 127.0.0.1. To access it over the network, you " +"must edit the :file:`/etc/mysql/my.cnf` file, and the ``mysql.user`` table. " +"To do so, Debian provides a helper script in the ``openstack-deploy`` " +"package. To use it, install the package:" +msgstr "" + +#: ../debconf/debconf-dbconfig-common.rst:134 +msgid "and run the helper script:" +msgstr "" + +#: ../debconf/debconf-dbconfig-common.rst:140 +msgid "" +"Alternatively, if you do not want to install this package, run this script " +"to enable remote root access:" msgstr "" #: ../debconf/debconf-dbconfig-common.rst:168 @@ -6601,6 +1879,1989 @@ msgid "" "multiple nodes." msgstr "" +#: ../debconf/debconf-keystone-authtoken.rst:5 +msgid "Services and the [keystone_authtoken]" +msgstr "" + +#: ../debconf/debconf-keystone-authtoken.rst:7 +msgid "" +"Because most OpenStack services must access the Identity service, you must " +"configure the IP address of the ``keystone`` server to be able to access it. " +"You must also configure the ``admin_tenant_name``, ``admin_user``, and " +"``admin_password`` options for each service to work." +msgstr "" + +#: ../debconf/debconf-keystone-authtoken.rst:12 +msgid "Generally, this section looks like this:" +msgstr "" + +#: ../debconf/debconf-keystone-authtoken.rst:24 +msgid "" +"The debconf system helps users configure the ``auth_uri``, ``identity_uri``, " +"``admin_tenant_name``, ``admin_user``, and ``admin_password`` options." +msgstr "" + +#: ../debconf/debconf-keystone-authtoken.rst:28 +msgid "The following screens show an example Image service configuration:" +msgstr "" + +#: ../debconf/debconf-keystone-authtoken.rst:44 +msgid "" +"This information is stored in the configuration file for each service. For " +"example:" +msgstr "" + +#: ../debconf/debconf-keystone-authtoken.rst:57 +msgid "" +"The Debian OpenStack packages offer automation for this, so OpenStack users " +"do not have to manually edit the configuration files." +msgstr "" + +#: ../debconf/debconf-rabbitmq.rst:5 +msgid "RabbitMQ credentials parameters" +msgstr "" + +#: ../debconf/debconf-rabbitmq.rst:7 +msgid "" +"For every package that must connect to a Messaging Server, the Debian " +"package enables you to configure the IP address for that server and the user " +"name and password that is used to connect. The following example shows " +"configuration with the ``ceilometer-common`` package:" +msgstr "" + +#: ../debconf/debconf-rabbitmq.rst:24 +msgid "" +"These debconf screens appear in: ``ceilometer-common``, ``cinder-common``, " +"``glance-common``, ``heat-common``, ``neutron-common``, and ``nova-common``." +msgstr "" + +#: ../debconf/debconf-rabbitmq.rst:27 +msgid "" +"This will configure the below directives (example from :file:`nova.conf`):" +msgstr "" + +#: ../debconf/debconf-rabbitmq.rst:36 +msgid "The other directives concerning RabbitMQ will stay untouched." +msgstr "" + +#: ../debconf/debconf.rst:5 +msgid "Configure OpenStack with debconf" +msgstr "" + +#: ../environment-dependencies.rst:6 +msgid "OpenStack service dependencies" +msgstr "" + +#: ../environment-dependencies.rst:9 +msgid "OpenStack packages" +msgstr "" + +#: ../environment-dependencies.rst:11 +msgid "" +"Distributions release OpenStack packages as part of the distribution or " +"using other methods because of differing release schedules. Perform these " +"procedures on all nodes." +msgstr "" + +#: ../environment-dependencies.rst:17 +msgid "" +"Disable or remove any automatic update services because they can impact your " +"OpenStack environment." +msgstr "" + +#: ../environment-dependencies.rst:23 ../environment-dependencies.rst:65 +#: ../environment-dependencies.rst:76 +msgid "Enable the OpenStack repository" +msgstr "" + +#: ../environment-dependencies.rst:25 +msgid "Install the Ubuntu Cloud archive keyring and repository:" +msgstr "" + +# #-#-#-#-# environment-dependencies.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# glance-install.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# keystone-install.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# keystone-services.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# neutron-compute-install.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# neutron-controller-install-option1.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# neutron-controller-install-option2.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# neutron-controller-install.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# nova-controller-install.pot (Installation Guide 0.1) #-#-#-#-# +#: ../environment-dependencies.rst:37 ../glance-install.rst:11 +#: ../keystone-install.rst:10 ../keystone-services.rst:10 +#: ../neutron-compute-install.rst:8 +#: ../neutron-controller-install-option1.rst:7 +#: ../neutron-controller-install-option2.rst:7 +#: ../neutron-controller-install.rst:5 ../nova-controller-install.rst:8 +msgid "Prerequisites" +msgstr "" + +#: ../environment-dependencies.rst:39 +msgid "" +"On RHEL and CentOS, enable the `EPEL `_ " +"repository:" +msgstr "" + +#: ../environment-dependencies.rst:48 +msgid "Fedora does not require this repository." +msgstr "" + +#: ../environment-dependencies.rst:50 +msgid "On RHEL, enable additional repositories using the subscription manager:" +msgstr "" + +#: ../environment-dependencies.rst:60 +msgid "CentOS and Fedora do not require these repositories." +msgstr "" + +#: ../environment-dependencies.rst:67 +msgid "" +"Install the ``rdo-release-liberty`` package to enable the RDO repository:" +msgstr "" + +#: ../environment-dependencies.rst:78 +msgid "" +"Enable the Open Build Service repositories based on your openSUSE or SLES " +"version:" +msgstr "" + +#: ../environment-dependencies.rst:81 +msgid "**On openSUSE 13.2:**" +msgstr "" + +#: ../environment-dependencies.rst:87 +msgid "" +"The openSUSE distribution uses the concept of patterns to represent " +"collections of packages. If you selected 'Minimal Server Selection (Text " +"Mode)' during the initial installation, you may be presented with a " +"dependency conflict when you attempt to install the OpenStack packages. To " +"avoid this, remove the minimal\\_base-conflicts package:" +msgstr "" + +#: ../environment-dependencies.rst:97 +msgid "**On SLES 12:**" +msgstr "" + +#: ../environment-dependencies.rst:105 +msgid "" +"The packages are signed by GPG key 893A90DAD85F9316. You should verify the " +"fingerprint of the imported GPG key before using it." +msgstr "" + +#: ../environment-dependencies.rst:119 +msgid "Enable the backports repository" +msgstr "" + +#: ../environment-dependencies.rst:121 +msgid "" +"The Liberty release is available directly through the official Debian " +"backports repository. To use this repository, follow the instruction from " +"the official `Debian website `_, " +"which basically suggest doing the following steps:" +msgstr "" + +#: ../environment-dependencies.rst:128 +msgid "" +"On all nodes, adding the Debian 8 (Jessie) backport repository to the source " +"list:" +msgstr "" + +#: ../environment-dependencies.rst:138 +msgid "Later you can use the following command to install a package:" +msgstr "" + +# #-#-#-#-# environment-dependencies.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# keystone-install.pot (Installation Guide 0.1) #-#-#-#-# +#: ../environment-dependencies.rst:146 ../keystone-install.rst:493 +msgid "Finalize the installation" +msgstr "" + +#: ../environment-dependencies.rst:150 ../environment-dependencies.rst:163 +#: ../environment-dependencies.rst:176 +msgid "Upgrade the packages on your system:" +msgstr "" + +#: ../environment-dependencies.rst:158 ../environment-dependencies.rst:171 +#: ../environment-dependencies.rst:184 +msgid "" +"If the upgrade process includes a new kernel, reboot your system to activate " +"it." +msgstr "" + +#: ../environment-dependencies.rst:189 +msgid "" +"RHEL and CentOS enable :term:`SELinux` by default. Install the ``openstack-" +"selinux`` package to automatically manage security policies for OpenStack " +"services:" +msgstr "" + +#: ../environment-dependencies.rst:199 +msgid "Fedora does not require this package." +msgstr "" + +#: ../environment-dependencies.rst:201 +msgid "" +"Because Fedora does not provide the ``openstack-selinux`` package ensure " +"that SELinux is disabled." +msgstr "" + +#: ../environment-dependencies.rst:209 +msgid "" +"If ``SELinux status`` is ``enabled`` disable SELinux by editing the file ``/" +"etc/selinux/config`` and restarting the system afterwards:" +msgstr "" + +#: ../environment-dependencies.rst:218 +msgid "CentOS and RHEL do not require this step." +msgstr "" + +#: ../environment-dependencies.rst:223 +msgid "Install the OpenStack client" +msgstr "" + +#: ../environment-dependencies.rst:225 +msgid "" +"Throughout the guide the OpenStack client will be used to perform actions on " +"the installed services." +msgstr "" + +#: ../environment-dependencies.rst:228 ../environment-dependencies.rst:408 +msgid "Install the package:" +msgstr "" + +#: ../environment-dependencies.rst:249 +msgid "SQL database" +msgstr "" + +#: ../environment-dependencies.rst:251 +msgid "" +"Most OpenStack services use an SQL database to store information. The " +"database typically runs on the controller node. The procedures in this guide " +"use MariaDB or MySQL depending on the distribution. OpenStack services also " +"support other SQL databases including `PostgreSQL `__." +msgstr "" + +#: ../environment-dependencies.rst:259 +msgid "Install and configure the database server" +msgstr "" + +#: ../environment-dependencies.rst:267 +msgid "The Python MySQL library is compatible with MariaDB." +msgstr "" + +#: ../environment-dependencies.rst:295 +msgid "Choose a suitable password for the database root account." +msgstr "" + +#: ../environment-dependencies.rst:297 +msgid "" +"Create and edit the :file:`/etc/mysql/conf.d/mysqld_openstack.cnf` file and " +"complete the following actions:" +msgstr "" + +#: ../environment-dependencies.rst:300 ../environment-dependencies.rst:330 +msgid "" +"In the ``[mysqld]`` section, set the ``bind-address`` key to the management " +"IP address of the controller node to enable access by other nodes via the " +"management network:" +msgstr "" + +#: ../environment-dependencies.rst:311 ../environment-dependencies.rst:341 +msgid "" +"In the ``[mysqld]`` section, set the following keys to enable useful options " +"and the UTF-8 character set:" +msgstr "" + +#: ../environment-dependencies.rst:327 +msgid "" +"Create and edit the :file:`/etc/my.cnf.d/mariadb_openstack.cnf` file and " +"complete the following actions:" +msgstr "" + +#: ../environment-dependencies.rst:359 +msgid "Restart the database service:" +msgstr "" + +#: ../environment-dependencies.rst:367 +msgid "" +"Start the database service and configure it to start when the system boots:" +msgstr "" + +#: ../environment-dependencies.rst:386 +msgid "" +"Secure the database service by running the ``mysql_secure_installation`` " +"script." +msgstr "" + +#: ../environment-dependencies.rst:392 +msgid "Message queue" +msgstr "" + +#: ../environment-dependencies.rst:394 +msgid "" +"OpenStack uses a :term:`message queue` to coordinate operations and status " +"information among services. The message queue service typically runs on the " +"controller node. OpenStack supports several message queue services including " +"`RabbitMQ `__, `Qpid `__, " +"and `ZeroMQ `__. However, most distributions that package " +"OpenStack support a particular message queue service. This guide implements " +"the RabbitMQ message queue service because most distributions support it. If " +"you prefer to implement a different message queue service, consult the " +"documentation associated with it." +msgstr "" + +#: ../environment-dependencies.rst:406 +msgid "Install the message queue service" +msgstr "" + +#: ../environment-dependencies.rst:430 +msgid "Configure the message queue service" +msgstr "" + +#: ../environment-dependencies.rst:432 +msgid "" +"Start the message queue service and configure it to start when the system " +"boots:" +msgstr "" + +#: ../environment-dependencies.rst:442 +msgid "Add the ``openstack`` user:" +msgstr "" + +#: ../environment-dependencies.rst:449 +msgid "Replace ``RABBIT_PASS`` with a suitable password." +msgstr "" + +#: ../environment-dependencies.rst:451 +msgid "" +"Permit configuration, write, and read access for the ``openstack`` user:" +msgstr "" + +#: ../environment-networking-compute.rst:2 +msgid "Compute node" +msgstr "" + +# #-#-#-#-# environment-networking-compute.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# environment-networking-controller.pot (Installation Guide 0.1) #-#-#-#-# +#: ../environment-networking-compute.rst:5 +#: ../environment-networking-controller.rst:5 +msgid "Configure network interfaces" +msgstr "" + +# #-#-#-#-# environment-networking-compute.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# environment-networking-controller.pot (Installation Guide 0.1) #-#-#-#-# +#: ../environment-networking-compute.rst:7 +#: ../environment-networking-controller.rst:7 +msgid "Configure the first interface as the management interface:" +msgstr "" + +#: ../environment-networking-compute.rst:9 +msgid "IP address: 10.0.0.31" +msgstr "" + +#: ../environment-networking-compute.rst:17 +msgid "Additional compute nodes should use 10.0.0.32, 10.0.0.33, and so on." +msgstr "" + +# #-#-#-#-# environment-networking-compute.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# environment-networking-controller.pot (Installation Guide 0.1) #-#-#-#-# +#: ../environment-networking-compute.rst:19 +#: ../environment-networking-controller.rst:15 +msgid "" +"The public interface uses a special configuration without an IP address " +"assigned to it. Configure the second interface as the public interface:" +msgstr "" + +# #-#-#-#-# environment-networking-compute.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# environment-networking-controller.pot (Installation Guide 0.1) #-#-#-#-# +#: ../environment-networking-compute.rst:23 +#: ../environment-networking-controller.rst:19 +msgid "" +"Replace ``INTERFACE_NAME`` with the actual interface name. For example, " +"*eth1* or *ens224*." +msgstr "" + +# #-#-#-#-# environment-networking-compute.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# environment-networking-controller.pot (Installation Guide 0.1) #-#-#-#-# +#: ../environment-networking-compute.rst:28 +#: ../environment-networking-controller.rst:24 +msgid "Edit the :file:`/etc/network/interfaces` file to contain the following:" +msgstr "" + +# #-#-#-#-# environment-networking-compute.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# environment-networking-controller.pot (Installation Guide 0.1) #-#-#-#-# +#: ../environment-networking-compute.rst:40 +#: ../environment-networking-controller.rst:36 +msgid "" +"Edit the :file:`/etc/sysconfig/network-scripts/ifcfg-INTERFACE_NAME` file to " +"contain the following:" +msgstr "" + +# #-#-#-#-# environment-networking-compute.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# environment-networking-controller.pot (Installation Guide 0.1) #-#-#-#-# +#: ../environment-networking-compute.rst:43 +#: ../environment-networking-controller.rst:39 +msgid "Do not change the ``HWADDR`` and ``UUID`` keys." +msgstr "" + +# #-#-#-#-# environment-networking-compute.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# environment-networking-controller.pot (Installation Guide 0.1) #-#-#-#-# +#: ../environment-networking-compute.rst:54 +#: ../environment-networking-controller.rst:50 +msgid "" +"Edit the :file:`/etc/sysconfig/network/ifcfg-INTERFACE_NAME` file to contain " +"the following:" +msgstr "" + +# #-#-#-#-# environment-networking-compute.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# environment-networking-controller.pot (Installation Guide 0.1) #-#-#-#-# +#: ../environment-networking-compute.rst:62 +#: ../environment-networking-controller.rst:58 +msgid "Reboot the system to activate the changes." +msgstr "" + +# #-#-#-#-# environment-networking-compute.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# environment-networking-controller.pot (Installation Guide 0.1) #-#-#-#-# +#: ../environment-networking-compute.rst:65 +#: ../environment-networking-controller.rst:61 +msgid "Configure name resolution" +msgstr "" + +#: ../environment-networking-compute.rst:67 +msgid "Set the hostname of the node to ``compute1``." +msgstr "" + +# #-#-#-#-# environment-networking-compute.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# environment-networking-controller.pot (Installation Guide 0.1) #-#-#-#-# +#: ../environment-networking-compute.rst:69 +#: ../environment-networking-controller.rst:65 +msgid "Edit the :file:`/etc/hosts` file to contain the following:" +msgstr "" + +# #-#-#-#-# environment-networking-compute.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# environment-networking-controller.pot (Installation Guide 0.1) #-#-#-#-# +#: ../environment-networking-compute.rst:81 +#: ../environment-networking-controller.rst:77 +msgid "" +"Some distributions add an extraneous entry in the :file:`/etc/hosts` file " +"that resolves the actual hostname to another loopback IP address such as " +"``127.0.1.1``. You must comment out or remove this entry to prevent name " +"resolution problems. **Do not remove the 127.0.0.1 entry.**" +msgstr "" + +# #-#-#-#-# environment-networking-controller.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# environment-ntp-controller.pot (Installation Guide 0.1) #-#-#-#-# +#: ../environment-networking-controller.rst:2 +#: ../environment-ntp-controller.rst:4 +msgid "Controller node" +msgstr "" + +#: ../environment-networking-controller.rst:9 +msgid "IP address: 10.0.0.11" +msgstr "" + +#: ../environment-networking-controller.rst:63 +msgid "Set the hostname of the node to ``controller``." +msgstr "" + +#: ../environment-networking-verify.rst:2 +msgid "Verify connectivity" +msgstr "" + +#: ../environment-networking-verify.rst:4 +msgid "" +"We recommend that you verify network connectivity to the Internet and among " +"the nodes before proceeding further." +msgstr "" + +#: ../environment-networking-verify.rst:7 +msgid "From the *controller* node, test access to the Internet:" +msgstr "" + +#: ../environment-networking-verify.rst:22 +msgid "" +"From the *controller* node, test access to the management interface on the " +"*compute* node:" +msgstr "" + +#: ../environment-networking-verify.rst:38 +msgid "From the *compute* node, test access to the Internet:" +msgstr "" + +#: ../environment-networking-verify.rst:53 +msgid "" +"From the *compute* node, test access to the management interface on the " +"*controller* node:" +msgstr "" + +# #-#-#-#-# environment-networking.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# environment-networking-verify.pot (Installation Guide 0.1) #-#-#-#-# +#: ../environment-networking-verify.rst:73 ../environment-networking.rst:107 +msgid "" +"Your distribution enables a restrictive :term:`firewall` by default. During " +"the installation process, certain steps will fail unless you alter or " +"disable the firewall. For more information about securing your environment, " +"refer to the `OpenStack Security Guide `__." +msgstr "" + +# #-#-#-#-# environment-networking.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# environment-networking-verify.pot (Installation Guide 0.1) #-#-#-#-# +#: ../environment-networking-verify.rst:81 ../environment-networking.rst:115 +msgid "" +"Your distribution does not enable a restrictive :term:`firewall` by default. " +"For more information about securing your environment, refer to the " +"`OpenStack Security Guide `__." +msgstr "" + +#: ../environment-networking.rst:2 +msgid "Host networking" +msgstr "" + +#: ../environment-networking.rst:6 +msgid "" +"After installing the operating system on each node for the architecture that " +"you choose to deploy, you must configure the network interfaces. We " +"recommend that you disable any automated network management tools and " +"manually edit the appropriate configuration files for your distribution. For " +"more information on how to configure networking on your distribution, see " +"the `documentation `__ ." +msgstr "" + +#: ../environment-networking.rst:15 +msgid "" +"After installing the operating system on each node for the architecture that " +"you choose to deploy, you must configure the network interfaces. We " +"recommend that you disable any automated network management tools and " +"manually edit the appropriate configuration files for your distribution. For " +"more information on how to configure networking on your distribution, see " +"the `documentation `__ ." +msgstr "" + +#: ../environment-networking.rst:24 +msgid "" +"After installing the operating system on each node for the architecture that " +"you choose to deploy, you must configure the network interfaces. We " +"recommend that you disable any automated network management tools and " +"manually edit the appropriate configuration files for your distribution. For " +"more information on how to configure networking on your distribution, see " +"the `documentation `__ ." +msgstr "" + +#: ../environment-networking.rst:33 +msgid "" +"After installing the operating system on each node for the architecture that " +"you choose to deploy, you must configure the network interfaces. We " +"recommend that you disable any automated network management tools and " +"manually edit the appropriate configuration files for your distribution. For " +"more information on how to configure networking on your distribution, see " +"the `SLES 12 `__ or `openSUSE `__ documentation." +msgstr "" + +#: ../environment-networking.rst:40 +msgid "" +"All nodes require Internet access for administrative purposes such as " +"package installation, security updates, :term:`DNS`, and :term:`NTP`. In " +"most cases, nodes should obtain internet access through the management " +"network interface. To highlight the importance of network separation, the " +"example architectures use `private address space `__ for the management network and assume that the physical " +"network infrastructure provides Internet access via :term:`NAT` or other " +"method. The example architectures use routable IP address space for the " +"public network and assume that the physical network infrastructure provides " +"direct Internet access. In the provider networks architecture, all instances " +"attach directly to the public network. In the self-service networks " +"architecture, instances can attach to a private or public network. Private " +"networks can reside entirely within OpenStack or provide some level of " +"public network access using :term:`NAT`." +msgstr "" + +#: ../environment-networking.rst:60 +msgid "The example architectures assume use of the following networks:" +msgstr "" + +#: ../environment-networking.rst:62 +msgid "Management on 10.0.0.0/24 with gateway 10.0.0.1" +msgstr "" + +#: ../environment-networking.rst:66 +msgid "" +"This network requires a gateway to provide Internet access to all nodes for " +"administrative purposes such as package installation, security updates, :" +"term:`DNS`, and :term:`NTP`." +msgstr "" + +#: ../environment-networking.rst:70 +msgid "Public on 203.0.113.0/24 with gateway 203.0.113.1" +msgstr "" + +#: ../environment-networking.rst:74 +msgid "" +"This network requires a gateway to provide Internet access to instances in " +"your OpenStack environment." +msgstr "" + +#: ../environment-networking.rst:77 +msgid "" +"You can modify these ranges and gateways to work with your particular " +"network infrastructure." +msgstr "" + +#: ../environment-networking.rst:82 +msgid "" +"Network interface names vary by distribution. Traditionally, interfaces use " +"\"eth\" followed by a sequential number. To cover all variations, this guide " +"simply refers to the first interface as the interface with the lowest number " +"and the second interface as the interface with the highest number." +msgstr "" + +#: ../environment-networking.rst:90 +msgid "" +"Unless you intend to use the exact configuration provided in this example " +"architecture, you must modify the networks in this procedure to match your " +"environment. Also, each node must resolve the other nodes by name in " +"addition to IP address. For example, the ``controller`` name must resolve to " +"``10.0.0.11``, the IP address of the management interface on the controller " +"node." +msgstr "" + +#: ../environment-networking.rst:99 +msgid "" +"Reconfiguring network interfaces will interrupt network connectivity. We " +"recommend using a local terminal session for these procedures." +msgstr "" + +# #-#-#-#-# environment-ntp-controller.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# environment-ntp-other.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# glance-install.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# keystone-install.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# nova-compute-install.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# nova-controller-install.pot (Installation Guide 0.1) #-#-#-#-# +#: ../environment-ntp-controller.rst:7 ../environment-ntp-other.rst:7 +#: ../glance-install.rst:149 ../keystone-install.rst:53 +#: ../nova-compute-install.rst:25 ../nova-controller-install.rst:145 +msgid "Install and configure components" +msgstr "" + +#: ../environment-ntp-controller.rst:41 +msgid "" +"By default, the controller node synchronizes the time via a pool of public " +"servers. However, you can optionally configure alternative servers such as " +"those provided by your organization." +msgstr "" + +#: ../environment-ntp-controller.rst:47 +msgid "" +"Edit the ``/etc/chrony/chrony.conf`` file and add, change, or remove the " +"following keys as necessary for your environment:" +msgstr "" + +#: ../environment-ntp-controller.rst:54 ../environment-ntp-controller.rst:73 +msgid "" +"Replace ``NTP_SERVER`` with the hostname or IP address of a suitable more " +"accurate (lower stratum) NTP server. The configuration supports multiple " +"``server`` keys." +msgstr "" + +# #-#-#-#-# environment-ntp-controller.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# environment-ntp-other.pot (Installation Guide 0.1) #-#-#-#-# +#: ../environment-ntp-controller.rst:58 ../environment-ntp-other.rst:53 +msgid "Restart the NTP service:" +msgstr "" + +#: ../environment-ntp-controller.rst:66 +msgid "" +"Edit the ``/etc/chrony.conf`` file and add, change, or remove the following " +"keys as necessary for your environment:" +msgstr "" + +#: ../environment-ntp-controller.rst:77 +msgid "" +"To enable other nodes to connect to the chrony daemon on the controller, add " +"the following key to the ``/etc/chrony.conf`` file:" +msgstr "" + +#: ../environment-ntp-controller.rst:84 +msgid "" +"If necessary, replace ``10.0.0.0/24`` with a description of your subnet." +msgstr "" + +# #-#-#-#-# environment-ntp-controller.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# environment-ntp-other.pot (Installation Guide 0.1) #-#-#-#-# +#: ../environment-ntp-controller.rst:86 ../environment-ntp-other.rst:68 +msgid "Start the NTP service and configure it to start when the system boots:" +msgstr "" + +#: ../environment-ntp-other.rst:4 +msgid "Other nodes" +msgstr "" + +#: ../environment-ntp-other.rst:41 +msgid "" +"Configure the network and compute nodes to reference the controller node." +msgstr "" + +#: ../environment-ntp-other.rst:46 +msgid "" +"Edit the ``/etc/chrony/chrony.conf`` file and comment out or remove all but " +"one ``server`` key. Change it to reference the controller node:" +msgstr "" + +#: ../environment-ntp-other.rst:61 +msgid "" +"Edit the ``/etc/chrony.conf`` file and comment out or remove all but one " +"``server`` key. Change it to reference the controller node:" +msgstr "" + +#: ../environment-ntp-verify.rst:6 +msgid "" +"We recommend that you verify NTP synchronization before proceeding further. " +"Some nodes, particularly those that reference the controller node, can take " +"several minutes to synchronize." +msgstr "" + +#: ../environment-ntp-verify.rst:10 +msgid "Run this command on the *controller* node:" +msgstr "" + +#: ../environment-ntp-verify.rst:21 +msgid "" +"Contents in the *Name/IP address* column should indicate the hostname or IP " +"address of one or more NTP servers. Contents in the *S* column should " +"indicate *\\** for the server to which the NTP service is currently " +"synchronized." +msgstr "" + +#: ../environment-ntp-verify.rst:25 +msgid "Run the same command on *all other* nodes:" +msgstr "" + +#: ../environment-ntp-verify.rst:35 +msgid "" +"Contents in the *Name/IP address* column should indicate the hostname of the " +"controller node." +msgstr "" + +#: ../environment-ntp.rst:7 +msgid "Network Time Protocol (NTP)" +msgstr "" + +#: ../environment-ntp.rst:9 +msgid "" +"You should install Chrony, an implementation of :term:`NTP`, to properly " +"synchronize services among nodes. We recommend that you configure the " +"controller node to reference more accurate (lower stratum) servers and other " +"nodes to reference the controller node." +msgstr "" + +#: ../environment-security.rst:0 +msgid "**Passwords**" +msgstr "" + +#: ../environment-security.rst:2 +msgid "Security" +msgstr "" + +#: ../environment-security.rst:4 +msgid "" +"OpenStack services support various security methods including password, " +"policy, and encryption. Additionally, supporting services including the " +"database server and message broker support at least password security." +msgstr "" + +#: ../environment-security.rst:8 +msgid "" +"To ease the installation process, this guide only covers password security " +"where applicable. You can create secure passwords manually, generate them " +"using a tool such as `pwgen `__, or " +"by running the following command:" +msgstr "" + +#: ../environment-security.rst:18 +msgid "" +"For OpenStack services, this guide uses ``SERVICE_PASS`` to reference " +"service account passwords and ``SERVICE_DBPASS`` to reference database " +"passwords." +msgstr "" + +#: ../environment-security.rst:22 +msgid "" +"The following table provides a list of services that require passwords and " +"their associated references in the guide:" +msgstr "" + +#: ../environment-security.rst:29 +msgid "Password name" +msgstr "" + +#: ../environment-security.rst:31 +msgid "Database password (no variable used)" +msgstr "" + +#: ../environment-security.rst:32 +msgid "Root password for the database" +msgstr "" + +#: ../environment-security.rst:33 +msgid "``ADMIN_PASS``" +msgstr "" + +#: ../environment-security.rst:34 +msgid "Password of user ``admin``" +msgstr "" + +#: ../environment-security.rst:35 +msgid "``CEILOMETER_DBPASS``" +msgstr "" + +#: ../environment-security.rst:36 +msgid "Database password for the Telemetry service" +msgstr "" + +#: ../environment-security.rst:37 +msgid "``CEILOMETER_PASS``" +msgstr "" + +#: ../environment-security.rst:38 +msgid "Password of Telemetry service user ``ceilometer``" +msgstr "" + +#: ../environment-security.rst:39 +msgid "``CINDER_DBPASS``" +msgstr "" + +#: ../environment-security.rst:40 +msgid "Database password for the Block Storage service" +msgstr "" + +#: ../environment-security.rst:41 +msgid "``CINDER_PASS``" +msgstr "" + +#: ../environment-security.rst:42 +msgid "Password of Block Storage service user ``cinder``" +msgstr "" + +#: ../environment-security.rst:43 +msgid "``DASH_DBPASS``" +msgstr "" + +#: ../environment-security.rst:44 +msgid "Database password for the dashboard" +msgstr "" + +#: ../environment-security.rst:45 +msgid "``DEMO_PASS``" +msgstr "" + +#: ../environment-security.rst:46 +msgid "Password of user ``demo``" +msgstr "" + +#: ../environment-security.rst:47 +msgid "``GLANCE_DBPASS``" +msgstr "" + +#: ../environment-security.rst:48 +msgid "Database password for Image service" +msgstr "" + +#: ../environment-security.rst:49 +msgid "``GLANCE_PASS``" +msgstr "" + +#: ../environment-security.rst:50 +msgid "Password of Image service user ``glance``" +msgstr "" + +#: ../environment-security.rst:51 +msgid "``HEAT_DBPASS``" +msgstr "" + +#: ../environment-security.rst:52 +msgid "Database password for the Orchestration service" +msgstr "" + +#: ../environment-security.rst:53 +msgid "``HEAT_DOMAIN_PASS``" +msgstr "" + +#: ../environment-security.rst:54 +msgid "Password of Orchestration domain" +msgstr "" + +#: ../environment-security.rst:55 +msgid "``HEAT_PASS``" +msgstr "" + +#: ../environment-security.rst:56 +msgid "Password of Orchestration service user ``heat``" +msgstr "" + +#: ../environment-security.rst:57 +msgid "``KEYSTONE_DBPASS``" +msgstr "" + +#: ../environment-security.rst:58 +msgid "Database password of Identity service" +msgstr "" + +#: ../environment-security.rst:59 +msgid "``NEUTRON_DBPASS``" +msgstr "" + +#: ../environment-security.rst:60 +msgid "Database password for the Networking service" +msgstr "" + +#: ../environment-security.rst:61 +msgid "``NEUTRON_PASS``" +msgstr "" + +#: ../environment-security.rst:62 +msgid "Password of Networking service user ``neutron``" +msgstr "" + +#: ../environment-security.rst:63 +msgid "``NOVA_DBPASS``" +msgstr "" + +#: ../environment-security.rst:64 +msgid "Database password for Compute service" +msgstr "" + +#: ../environment-security.rst:65 +msgid "``NOVA_PASS``" +msgstr "" + +#: ../environment-security.rst:66 +msgid "Password of Compute service user ``nova``" +msgstr "" + +#: ../environment-security.rst:67 +msgid "``RABBIT_PASS``" +msgstr "" + +#: ../environment-security.rst:68 +msgid "Password of user guest of RabbitMQ" +msgstr "" + +#: ../environment-security.rst:69 +msgid "``SWIFT_PASS``" +msgstr "" + +#: ../environment-security.rst:70 +msgid "Password of Object Storage service user ``swift``" +msgstr "" + +#: ../environment-security.rst:72 +msgid "" +"OpenStack and supporting services require administrative privileges during " +"installation and operation. In some cases, services perform modifications to " +"the host that can interfere with deployment automation tools such as " +"Ansible, Chef, and Puppet. For example, some OpenStack services add a root " +"wrapper to ``sudo`` that can interfere with security policies. See the " +"`Cloud Administrator Guide `__ for more information." +msgstr "" + +#: ../environment-security.rst:81 +msgid "" +"Also, the Networking service assumes default values for kernel network " +"parameters and modifies firewall rules. To avoid most issues during your " +"initial installation, we recommend using a stock deployment of a supported " +"distribution on your hosts. However, if you choose to automate deployment of " +"your hosts, review the configuration and policies applied to them before " +"proceeding further." +msgstr "" + +#: ../environment.rst:5 +msgid "Environment" +msgstr "" + +#: ../environment.rst:9 +msgid "" +"The draft version of this guide focuses on the future Liberty release and " +"will not work for the current Kilo release. If you want to install Kilo, you " +"must use the `Kilo version `__ of this guide " +"instead." +msgstr "" + +#: ../environment.rst:14 +msgid "" +"This section explains how to configure the controller and one compute node " +"using the example architecture." +msgstr "" + +#: ../environment.rst:17 +msgid "" +"Although most environments include Identity, Image service, Compute, at " +"least one networking service, and the dashboard, the Object Storage service " +"can operate independently. If your use case only involves Object Storage, " +"you can skip to :ref:`swift` after configuring the appropriate nodes for it. " +"However, the dashboard requires at least the Image service, Compute, and " +"Networking." +msgstr "" + +#: ../environment.rst:23 +msgid "" +"You must use an account with administrative privileges to configure each " +"node. Either run the commands as the ``root`` user or configure the ``sudo`` " +"utility." +msgstr "" + +#: ../environment.rst:29 +msgid "" +"The :command:`systemctl enable` call on openSUSE outputs a warning message " +"when the service uses SysV Init scripts instead of native systemd files. " +"This warning can be ignored." +msgstr "" + +#: ../environment.rst:33 +msgid "" +"For best performance, we recommend that your environment meets or exceeds " +"the hardware requirements in :ref:`figure-hwreqs`. However, OpenStack does " +"not require a significant amount of resources and the following minimum " +"requirements should support a proof-of-concept environment with core " +"services and several :term:`CirrOS` instances:" +msgstr "" + +#: ../environment.rst:39 +msgid "Controller Node: 1 processor, 2 GB memory, and 5 GB storage" +msgstr "" + +#: ../environment.rst:41 +msgid "Compute Node: 1 processor, 2 GB memory, and 10 GB storage" +msgstr "" + +#: ../environment.rst:43 +msgid "" +"To minimize clutter and provide more resources for OpenStack, we recommend a " +"minimal installation of your Linux distribution. Also, you must install a 64-" +"bit version of your distribution on each node." +msgstr "" + +#: ../environment.rst:47 +msgid "" +"A single disk partition on each node works for most basic installations. " +"However, you should consider :term:`Logical Volume Manager (LVM)` for " +"installations with optional services such as Block Storage." +msgstr "" + +#: ../environment.rst:51 +msgid "" +"For first-time installation and testing purposes, many users elect to build " +"each host as a :term:`virtual machine (VM)`. The primary benefits of VMs " +"include the following:" +msgstr "" + +#: ../environment.rst:55 +msgid "" +"One physical server can support multiple nodes, each with almost any number " +"of network interfaces." +msgstr "" + +#: ../environment.rst:58 +msgid "" +"Ability to take periodic \"snap shots\" throughout the installation process " +"and \"roll back\" to a working configuration in the event of a problem." +msgstr "" + +#: ../environment.rst:62 +msgid "" +"However, VMs will reduce performance of your instances, particularly if your " +"hypervisor and/or processor lacks support for hardware acceleration of " +"nested VMs." +msgstr "" + +#: ../environment.rst:68 +msgid "" +"If you choose to install on VMs, make sure your hypervisor provides a way to " +"disable MAC address filtering on the ``public`` network interface." +msgstr "" + +#: ../environment.rst:72 +msgid "" +"For more information about system requirements, see the `OpenStack " +"Operations Guide `_." +msgstr "" + +#: ../glance-install.rst:4 +msgid "" +"This section describes how to install and configure the Image service, code-" +"named glance, on the controller node. For simplicity, this configuration " +"stores images on the local file system." +msgstr "" + +#: ../glance-install.rst:13 +msgid "" +"Before you install and configure the Image service, you must create a " +"database, service credentials, and API endpoints." +msgstr "" + +#: ../glance-install.rst:25 +msgid "Create the ``glance`` database:" +msgstr "" + +#: ../glance-install.rst:31 +msgid "Grant proper access to the ``glance`` database:" +msgstr "" + +#: ../glance-install.rst:40 +msgid "Replace ``GLANCE_DBPASS`` with a suitable password." +msgstr "" + +#: ../glance-install.rst:53 +msgid "Create the ``glance`` user:" +msgstr "" + +#: ../glance-install.rst:69 +msgid "Add the ``admin`` role to the ``glance`` user and ``service`` project:" +msgstr "" + +# #-#-#-#-# glance-install.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# keystone-users.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# launch-instance-private.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# neutron-controller-install.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# nova-controller-install.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# swift-initial-rings.pot (Installation Guide 0.1) #-#-#-#-# +#: ../glance-install.rst:78 ../keystone-users.rst:76 ../keystone-users.rst:170 +#: ../launch-instance-private.rst:224 ../neutron-controller-install.rst:71 +#: ../nova-controller-install.rst:74 ../swift-initial-rings.rst:32 +#: ../swift-initial-rings.rst:113 ../swift-initial-rings.rst:192 +msgid "This command provides no output." +msgstr "" + +#: ../glance-install.rst:80 +msgid "Create the ``glance`` service entity:" +msgstr "" + +#: ../glance-install.rst:96 +msgid "Create the Image service API endpoints:" +msgstr "" + +#: ../glance-install.rst:184 +msgid "" +"Edit the ``/etc/glance/glance-api.conf`` file and complete the following " +"actions:" +msgstr "" + +#: ../glance-install.rst:195 ../glance-install.rst:269 +msgid "" +"Replace ``GLANCE_DBPASS`` with the password you chose for the Image service " +"database." +msgstr "" + +#: ../glance-install.rst:198 ../glance-install.rst:272 +msgid "" +"In the ``[keystone_authtoken]`` and ``[paste_deploy]`` sections, configure " +"Identity service access:" +msgstr "" + +#: ../glance-install.rst:218 ../glance-install.rst:292 +msgid "" +"Replace ``GLANCE_PASS`` with the password you chose for the ``glance`` user " +"in the Identity service." +msgstr "" + +#: ../glance-install.rst:226 +msgid "" +"In the ``[glance_store]`` section, configure the local file system store and " +"location of image files:" +msgstr "" + +#: ../glance-install.rst:236 ../glance-install.rst:300 +msgid "" +"In the ``[DEFAULT]`` section, configure the ``noop`` notification driver to " +"disable notifications because they only pertain to the optional Telemetry " +"service:" +msgstr "" + +#: ../glance-install.rst:246 ../glance-install.rst:310 +msgid "" +"The Telemetry chapter provides an Image service configuration that enables " +"notifications." +msgstr "" + +#: ../glance-install.rst:258 +msgid "" +"Edit the ``/etc/glance/glance-registry.conf`` file and complete the " +"following actions:" +msgstr "" + +#: ../glance-install.rst:324 +msgid "Populate the Image service database:" +msgstr "" + +# #-#-#-#-# glance-install.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# heat-install.pot (Installation Guide 0.1) #-#-#-#-# +#: ../glance-install.rst:338 ../heat-install.rst:429 +msgid "" +"Respond to prompts for :doc:`database management `, :doc:`Identity service credentials `, :doc:`service endpoint registration `, and :doc:`message broker credentials `." +msgstr "" + +#: ../glance-install.rst:344 +msgid "" +"Select the ``keystone`` pipeline to configure the Image service to use the " +"Identity service:" +msgstr "" + +# #-#-#-#-# glance-install.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# neutron-compute-install.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# neutron-controller-install.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# nova-compute-install.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# nova-controller-install.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# swift-finalize-installation.pot (Installation Guide 0.1) #-#-#-#-# +#: ../glance-install.rst:351 ../neutron-compute-install.rst:188 +#: ../neutron-controller-install.rst:249 ../nova-compute-install.rst:207 +#: ../nova-controller-install.rst:351 ../swift-finalize-installation.rst:3 +msgid "Finalize installation" +msgstr "" + +#: ../glance-install.rst:355 +msgid "" +"Start the Image service services and configure them to start when the system " +"boots:" +msgstr "" + +#: ../glance-install.rst:367 +msgid "Restart the Image service services:" +msgstr "" + +#: ../glance-verify.rst:4 +msgid "" +"Verify operation of the Image service using `CirrOS `__, a small Linux image that helps you test your OpenStack " +"deployment." +msgstr "" + +#: ../glance-verify.rst:8 +msgid "" +"For more information about how to download and build images, see `OpenStack " +"Virtual Machine Image Guide `__. For information about how to manage images, see the " +"`OpenStack User Guide `__." +msgstr "" + +#: ../glance-verify.rst:15 +msgid "" +"In each client environment script, configure the Image service client to use " +"API version 2.0:" +msgstr "" + +#: ../glance-verify.rst:30 +msgid "Download the source image:" +msgstr "" + +#: ../glance-verify.rst:36 +msgid "" +"Upload the image to the Image service using the :term:`QCOW2 ` disk format, :term:`bare` container format, and public " +"visibility so all projects can access it:" +msgstr "" + +#: ../glance-verify.rst:68 +msgid "" +"For information about the :command:`glance image-create` parameters, see " +"`Image service command-line client `__ in the ``OpenStack Command-Line Interface Reference``." +msgstr "" + +#: ../glance-verify.rst:74 +msgid "" +"For information about disk and container formats for images, see `Disk and " +"container formats for images `__ in the ``OpenStack Virtual Machine Image Guide``." +msgstr "" + +# #-#-#-#-# glance-verify.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# keystone-services.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# keystone-users.pot (Installation Guide 0.1) #-#-#-#-# +#: ../glance-verify.rst:81 ../keystone-services.rst:99 +#: ../keystone-users.rst:36 +msgid "" +"OpenStack generates IDs dynamically, so you will see different values in the " +"example command output." +msgstr "" + +#: ../glance-verify.rst:84 +msgid "Confirm upload of the image and validate attributes:" +msgstr "" + +#: ../glance.rst:3 +msgid "Add the Image service" +msgstr "" + +#: ../glance.rst:11 +msgid "" +"The OpenStack Image service (glance) enables users to discover, register, " +"and retrieve virtual machine images. It offers a :term:`REST ` API " +"that enables you to query virtual machine image metadata and retrieve an " +"actual image. You can store virtual machine images made available through " +"the Image service in a variety of locations, from simple file systems to " +"object-storage systems like OpenStack Object Storage." +msgstr "" + +#: ../glance.rst:21 +msgid "" +"For simplicity, this guide describes configuring the Image service to use " +"the ``file`` back end, which uploads and stores in a directory on the " +"controller node hosting the Image service. By default, this directory is :" +"file:`/var/lib/glance/images/`." +msgstr "" + +#: ../glance.rst:26 +msgid "" +"Before you proceed, ensure that the controller node has at least several " +"gigabytes of space available in this directory." +msgstr "" + +#: ../glance.rst:29 +msgid "" +"For information on requirements for other back ends, see `Configuration " +"Reference `__." +msgstr "" + +#: ../heat-install.rst:3 +msgid "Install and configure Orchestration" +msgstr "" + +#: ../heat-install.rst:5 +msgid "" +"This section describes how to install and configure the Orchestration " +"module, code-named heat, on the controller node." +msgstr "" + +#: ../heat-install.rst:13 +msgid "" +"Before you install and configure Orchestration, you must create a database, " +"service credentials, and API endpoints." +msgstr "" + +#: ../heat-install.rst:25 +msgid "Create the ``heat`` database::" +msgstr "" + +#: ../heat-install.rst:29 +msgid "Grant proper access to the ``heat`` database::" +msgstr "" + +#: ../heat-install.rst:36 +msgid "Replace ``HEAT_DBPASS`` with a suitable password." +msgstr "" + +#: ../heat-install.rst:49 +msgid "Create the ``heat`` user:" +msgstr "" + +#: ../heat-install.rst:66 +msgid "Add the ``admin`` role to the ``heat`` user:" +msgstr "" + +#: ../heat-install.rst:78 +msgid "Create the ``heat_stack_owner`` role:" +msgstr "" + +#: ../heat-install.rst:90 +msgid "Add the ``heat_stack_owner`` role to the ``demo`` tenant and user:" +msgstr "" + +#: ../heat-install.rst:104 +msgid "You must add the ``heat_stack_owner`` role to users that manage stacks." +msgstr "" + +#: ../heat-install.rst:107 +msgid "Create the ``heat_stack_user`` role:" +msgstr "" + +#: ../heat-install.rst:121 +msgid "" +"The Orchestration service automatically assigns the ``heat_stack_user`` role " +"to users that it creates during stack deployment. By default, this role " +"restricts :term:`API` operations. To avoid conflicts, do not add this role " +"to users with the ``heat_stack_owner`` role." +msgstr "" + +#: ../heat-install.rst:127 +msgid "Create the ``heat`` and ``heat-cfn`` service entities:" +msgstr "" + +#: ../heat-install.rst:154 +msgid "Create the Orchestration service API endpoints:" +msgstr "" + +#: ../heat-install.rst:253 +msgid "To install and configure the Orchestration components" +msgstr "" + +#: ../heat-install.rst:257 ../heat-install.rst:266 ../heat-install.rst:275 +#: ../heat-install.rst:423 +msgid "Run the following commands to install the packages:" +msgstr "" + +#: ../heat-install.rst:290 +msgid "" +"Copy the :file:`/usr/share/heat/heat-dist.conf` file to :file:`/etc/heat/" +"heat.conf`." +msgstr "" + +#: ../heat-install.rst:298 ../heat-install.rst:435 +msgid "" +"Edit the :file:`/etc/heat/heat.conf` file and complete the following actions:" +msgstr "" + +#: ../heat-install.rst:310 +msgid "" +"Replace ``HEAT_DBPASS`` with the password you chose for the Orchestration " +"database." +msgstr "" + +#: ../heat-install.rst:332 +msgid "" +"In the ``[keystone_authtoken]`` and ``[ec2authtoken]`` sections, configure " +"Identity service access:" +msgstr "" + +#: ../heat-install.rst:350 +msgid "" +"Replace ``HEAT_PASS`` with the password you chose for the ``heat`` user in " +"the Identity service." +msgstr "" + +#: ../heat-install.rst:359 +msgid "" +"In the ``[DEFAULT]`` section, configure the metadata and wait condition URLs:" +msgstr "" + +#: ../heat-install.rst:370 +msgid "" +"In the ``[DEFAULT]`` section, configure information about the heat Identity " +"service domain:" +msgstr "" + +#: ../heat-install.rst:382 +msgid "" +"Replace ``HEAT_DOMAIN_PASS`` with the password you chose for the admin user " +"of the ``heat`` user domain in the Identity service." +msgstr "" + +#: ../heat-install.rst:404 +msgid "Create the heat domain in Identity service:" +msgstr "" + +#: ../heat-install.rst:413 +msgid "Replace ``HEAT_DOMAIN_PASS`` with a suitable password." +msgstr "" + +#: ../heat-install.rst:415 +msgid "Populate the Orchestration database:" +msgstr "" + +#: ../heat-install.rst:438 +msgid "In the ``[ec2authtoken]`` section, configure Identity service access:" +msgstr "" + +#: ../heat-install.rst:452 +msgid "" +"Start the Orchestration services and configure them to start when the system " +"boots:" +msgstr "" + +#: ../heat-install.rst:464 +msgid "Restart the Orchestration services:" +msgstr "" + +#: ../heat-next-step.rst:5 +msgid "" +"Your OpenStack environment now includes Orchestration. You can :ref:`launch-" +"instance` or add more services to your environment in the following chapters." +msgstr "" + +#: ../heat-verify.rst:5 +msgid "" +"This section describes how to verify operation of the Orchestration module " +"(heat)." +msgstr "" + +#: ../heat-verify.rst:8 +msgid "Source the ``admin`` tenant credentials:" +msgstr "" + +#: ../heat-verify.rst:14 +msgid "" +"The Orchestration module uses templates to describe stacks. To learn about " +"the template language, see `the Template Guide `__ in the `Heat developer " +"documentation `__." +msgstr "" + +#: ../heat-verify.rst:20 +msgid "" +"Create a test template in the :file:`test-stack.yml` file with the following " +"content:" +msgstr "" + +#: ../heat-verify.rst:51 +msgid "" +"Use the :command:`heat stack-create` command to create a stack from the " +"template:" +msgstr "" + +#: ../heat-verify.rst:65 +msgid "" +"Use the :command:`heat stack-list` command to verify successful creation of " +"the stack:" +msgstr "" + +#: ../heat.rst:3 +msgid "Add the Orchestration module" +msgstr "" + +#: ../heat.rst:12 +msgid "" +"The Orchestration module (heat) uses a heat orchestration template (HOT) to " +"create and manage cloud resources." +msgstr "" + +#: ../horizon.rst:3 +msgid "Add the dashboard" +msgstr "" + +#: ../horizon.rst:5 +msgid "" +"The OpenStack Dashboard, also known as `horizon `__ is a web interface that enables cloud " +"administrators and users to manage various OpenStack resources and services." +msgstr "" + +#: ../horizon.rst:10 +msgid "" +"The Dashboard enables web-based interactions with the OpenStack Compute " +"cloud controller through the OpenStack APIs." +msgstr "" + +#: ../horizon.rst:13 +msgid "Horizon enables you to customize the brand of the dashboard." +msgstr "" + +#: ../horizon.rst:15 +msgid "" +"Horizon provides a set of core classes and reusable templates and tools." +msgstr "" + +#: ../horizon.rst:17 +msgid "This example deployment uses an Apache web server." +msgstr "" + +#: ../index-debian.rst:3 ../index-debian.rst:31 +msgid "OpenStack Installation Guide for Debian" +msgstr "" + +#: ../index-debian.rst:13 +msgid "" +"OpenStack Installation Guide for Red Hat Enterprise Linux, CentOS, and Fedora" +msgstr "" + +#: ../index-debian.rst:19 +msgid "OpenStack Installation Guide for openSUSE and SUSE Linux Enterprise" +msgstr "" + +#: ../index-debian.rst:25 +msgid "OpenStack Installation Guide for Ubuntu" +msgstr "" + +#: ../index-debian.rst:35 +msgid "Abstract" +msgstr "" + +#: ../index-debian.rst:37 +msgid "" +"The OpenStack system consists of several key projects that you install " +"separately. These projects work together depending on your cloud needs. " +"These projects include Compute, Identity Service, Networking, Image Service, " +"Block Storage, Object Storage, Telemetry, Orchestration, and Database. You " +"can install any of these projects separately and configure them stand-alone " +"or as connected entities." +msgstr "" + +#: ../index-debian.rst:46 +msgid "" +"This guide shows you how to install OpenStack by using packages available " +"through Fedora 22 as well as on Red Hat Enterprise Linux 7 and its " +"derivatives through the EPEL repository." +msgstr "" + +#: ../index-debian.rst:52 +msgid "" +"This guide walks through an installation by using packages available through " +"Canonical's Ubuntu Cloud archive repository." +msgstr "" + +#: ../index-debian.rst:57 +msgid "" +"This guide shows you how to install OpenStack by using packages on openSUSE " +"13.2 and SUSE Linux Enterprise Server 12 through the Open Build Service " +"Cloud repository." +msgstr "" + +#: ../index-debian.rst:63 +msgid "" +"This guide walks through an installation by using packages available through " +"Debian 8 (code name: Jessie)." +msgstr "" + +#: ../index-debian.rst:66 +msgid "" +"Explanations of configuration options and sample configuration files are " +"included." +msgstr "" + +#: ../index-debian.rst:69 +msgid "This guide documents OpenStack Liberty release." +msgstr "" + +#: ../index-debian.rst:71 +msgid "" +"This guide is a work-in-progress and changing rapidly while we continue to " +"test and enhance the guidance. Please note where there are open \"to do\" " +"items and help where you are able." +msgstr "" + +#: ../index-debian.rst:76 +msgid "Contents" +msgstr "" + +#: ../index-debian.rst:101 +msgid "Search in this guide" +msgstr "" + +#: ../index-debian.rst:103 +msgid ":ref:`search`" +msgstr "" + +#: ../keystone-install.rst:4 +msgid "" +"This section describes how to install and configure the OpenStack Identity " +"service, code-named keystone, on the controller node. For performance, this " +"configuration deploys the Apache HTTP server to handle requests and " +"Memcached to store tokens instead of an SQL database." +msgstr "" + +#: ../keystone-install.rst:12 +msgid "" +"Before you configure the OpenStack Identity service, you must create a " +"database and an administration token." +msgstr "" + +#: ../keystone-install.rst:15 +msgid "To create the database, complete the following actions:" +msgstr "" + +#: ../keystone-install.rst:24 +msgid "Create the ``keystone`` database:" +msgstr "" + +#: ../keystone-install.rst:30 +msgid "Grant proper access to the ``keystone`` database:" +msgstr "" + +#: ../keystone-install.rst:39 +msgid "Replace ``KEYSTONE_DBPASS`` with a suitable password." +msgstr "" + +#: ../keystone-install.rst:43 ../keystone-install.rst:215 +msgid "" +"Generate a random value to use as the administration token during initial " +"configuration:" +msgstr "" + +#: ../keystone-install.rst:58 +msgid "" +"In Kilo and Liberty releases, the keystone project deprecates eventlet in " +"favor of a separate web server with WSGI extensions. This guide uses the " +"Apache HTTP server with ``mod_wsgi`` to serve Identity service requests on " +"port 5000 and 35357. By default, the keystone service still listens on ports " +"5000 and 35357. Therefore, this guide disables the keystone service. The " +"keystone project plans to remove eventlet support in Mitaka." +msgstr "" + +#: ../keystone-install.rst:68 +msgid "" +"Disable the keystone service from starting automatically after installation:" +msgstr "" + +#: ../keystone-install.rst:75 ../keystone-install.rst:86 +#: ../keystone-install.rst:187 +msgid "Run the following command to install the packages:" +msgstr "" + +#: ../keystone-install.rst:104 +msgid "" +"Start the Memcached service and configure it to start when the system boots:" +msgstr "" + +#: ../keystone-install.rst:114 +msgid "" +"Edit the ``/etc/keystone/keystone.conf`` file and complete the following " +"actions:" +msgstr "" + +#: ../keystone-install.rst:117 +msgid "" +"In the ``[DEFAULT]`` section, define the value of the initial administration " +"token:" +msgstr "" + +#: ../keystone-install.rst:126 +msgid "" +"Replace ``ADMIN_TOKEN`` with the random value that you generated in a " +"previous step." +msgstr "" + +#: ../keystone-install.rst:137 +msgid "" +"Replace ``KEYSTONE_DBPASS`` with the password you chose for the database." +msgstr "" + +#: ../keystone-install.rst:139 +msgid "In the ``[memcache]`` section, configure the Memcache service:" +msgstr "" + +#: ../keystone-install.rst:147 +msgid "" +"In the ``[token]`` section, configure the UUID token provider and Memcached " +"driver:" +msgstr "" + +#: ../keystone-install.rst:157 +msgid "In the ``[revoke]`` section, configure the SQL revocation driver:" +msgstr "" + +#: ../keystone-install.rst:176 +msgid "Populate the Identity service database:" +msgstr "" + +#: ../keystone-install.rst:185 +msgid "Install and configure the components" +msgstr "" + +#: ../keystone-install.rst:195 +msgid "" +"python-keystoneclient will automatically be installed as it is a dependency " +"of the keystone package." +msgstr "" + +#: ../keystone-install.rst:198 +msgid "" +"Respond to prompts for :doc:`debconf/debconf-dbconfig-common`, which will " +"fill the below database access directive." +msgstr "" + +#: ../keystone-install.rst:207 +msgid "" +"If you decide to not use ``dbconfig-common``, then you will have to create " +"the database and manage its access rights yourself, and run the following by " +"hand." +msgstr "" + +#: ../keystone-install.rst:222 +msgid "Configure the initial administration token:" +msgstr "" + +#: ../keystone-install.rst:227 +msgid "" +"Use the random value that you generated in a previous step. If you install " +"using non-interactive mode or you do not specify this token, the " +"configuration tool generates a random value." +msgstr "" + +#: ../keystone-install.rst:231 +msgid "" +"Later on, the package will configure the below directive with the value you " +"entered:" +msgstr "" + +#: ../keystone-install.rst:240 +msgid "Create the ``admin`` tenant and user:" +msgstr "" + +#: ../keystone-install.rst:242 +msgid "" +"During the final stage of the package installation, it is possible to " +"automatically create an admin tenant and an admin user. This can later be " +"used for other OpenStack services to contact the Identity service. This is " +"the equivalent of running the below commands:" +msgstr "" + +#: ../keystone-install.rst:269 +msgid "" +"In Debian, the Keystone package offers automatic registration of Keystone in " +"the service catalogue. This is equivalent of running the below commands:" +msgstr "" + +#: ../keystone-install.rst:289 +msgid "Configure the Apache HTTP server" +msgstr "" + +#: ../keystone-install.rst:293 +msgid "" +"Edit the ``/etc/httpd/conf/httpd.conf`` file and configure the " +"``ServerName`` option to reference the controller node:" +msgstr "" + +#: ../keystone-install.rst:300 +msgid "" +"Create the ``/etc/httpd/conf.d/wsgi-keystone.conf`` file with the following " +"content:" +msgstr "" + +#: ../keystone-install.rst:356 +msgid "" +"Edit the ``/etc/apache2/apache2.conf`` file and configure the ``ServerName`` " +"option to reference the controller node:" +msgstr "" + +#: ../keystone-install.rst:363 +msgid "" +"Create the ``/etc/apache2/sites-available/wsgi-keystone.conf`` file with the " +"following content:" +msgstr "" + +#: ../keystone-install.rst:417 +msgid "Enable the Identity service virtual hosts:" +msgstr "" + +#: ../keystone-install.rst:425 +msgid "" +"Edit the ``/etc/sysconfig/apache2`` file and configure the " +"``APACHE_SERVERNAME`` option to reference the controller node:" +msgstr "" + +#: ../keystone-install.rst:432 +msgid "" +"Create the ``/etc/apache2/conf.d/wsgi-keystone.conf`` file with the " +"following content:" +msgstr "" + +#: ../keystone-install.rst:486 +msgid "Recursively change the ownership of the ``/etc/keystone`` directory:" +msgstr "" + +#: ../keystone-install.rst:497 +msgid "Restart the Apache HTTP server:" +msgstr "" + +#: ../keystone-install.rst:514 ../keystone-install.rst:523 +msgid "" +"Start the Apache HTTP service and configure it to start when the system " +"boots:" +msgstr "" + +#: ../keystone-openrc.rst:2 +msgid "Create OpenStack client environment scripts" +msgstr "" + +#: ../keystone-openrc.rst:4 +msgid "" +"The previous section used a combination of environment variables and command " +"options to interact with the Identity service via the ``openstack`` client. " +"To increase efficiency of client operations, OpenStack supports simple " +"client environment scripts also known as OpenRC files. These scripts " +"typically contain common options for all clients, but also support unique " +"options. For more information, see the `OpenStack User Guide `__." +msgstr "" + +#: ../keystone-openrc.rst:14 +msgid "Creating the scripts" +msgstr "" + +#: ../keystone-openrc.rst:16 +msgid "" +"Create client environment scripts for the ``admin`` and ``demo`` projects " +"and users. Future portions of this guide reference these scripts to load " +"appropriate credentials for client operations." +msgstr "" + +#: ../keystone-openrc.rst:20 +msgid "Edit the ``admin-openrc.sh`` file and add the following content:" +msgstr "" + +#: ../keystone-openrc.rst:33 +msgid "" +"Replace ``ADMIN_PASS`` with the password you chose for the ``admin`` user in " +"the Identity service." +msgstr "" + +#: ../keystone-openrc.rst:36 +msgid "Edit the ``demo-openrc.sh`` file and add the following content:" +msgstr "" + +#: ../keystone-openrc.rst:49 +msgid "" +"Replace ``DEMO_PASS`` with the password you chose for the ``demo`` user in " +"the Identity service." +msgstr "" + +#: ../keystone-openrc.rst:53 +msgid "Using the scripts" +msgstr "" + +#: ../keystone-openrc.rst:55 +msgid "" +"To run clients as a specific project and user, you can simply load the " +"associated client environment script prior to running them. For example:" +msgstr "" + +#: ../keystone-openrc.rst:59 +msgid "" +"Load the ``admin-openrc.sh`` file to populate environment variables with the " +"location of the Identity service and the ``admin`` project and user " +"credentials:" +msgstr "" + +#: ../keystone-openrc.rst:67 +msgid "Request an authentication token:" +msgstr "" + +#: ../keystone-services.rst:2 ../keystone-services.rst:75 +msgid "Create the service entity and API endpoints" +msgstr "" + +#: ../keystone-services.rst:4 +msgid "" +"The Identity service provides a catalog of services and their locations. " +"Each service that you add to your OpenStack environment requires a :term:" +"`service` entity and several :term:`API endpoints` in the " +"catalog." +msgstr "" + +#: ../keystone-services.rst:14 +msgid "" +"By default, the Identity service database contains no information to support " +"conventional authentication and catalog services. You must use a temporary " +"authentication token that you created in the section called :doc:`keystone-" +"install` to initialize the service entity and API endpoint for the Identity " +"service." +msgstr "" + +#: ../keystone-services.rst:24 +msgid "" +"The packages can automatically create the service entity and API endpoints." +msgstr "" + #: ../keystone-services.rst:27 msgid "" "You must pass the value of the authentication token to the :command:" @@ -6611,44 +3872,1806 @@ msgid "" "environment variables to reduce command length." msgstr "" -#: ../environment.rst:23 +#: ../keystone-services.rst:36 msgid "" -"You must use an account with administrative privileges to configure each " -"node. Either run the commands as the ``root`` user or configure the ``sudo`` " -"utility." +"For security reasons, do not use the temporary authentication token for " +"longer than necessary to initialize the Identity service." msgstr "" -#: ../environment-ntp.rst:9 -msgid "" -"You should install Chrony, an implementation of :term:`NTP`, to properly " -"synchronize services among nodes. We recommend that you configure the " -"controller node to reference more accurate (lower stratum) servers and other " -"nodes to reference the controller node." +#: ../keystone-services.rst:39 +msgid "Configure the authentication token:" msgstr "" -#: ../cinder-next-steps.rst:5 +#: ../keystone-services.rst:47 msgid "" -"Your OpenStack environment now includes Block Storage. You can :doc:`launch " -"an instance ` or add more services to your environment in " -"the following chapters." +"Replace ``ADMIN_TOKEN`` with the authentication token that you generated in " +"the section called :doc:`keystone-install`. For example:" msgstr "" -#: ../swift-next-steps.rst:5 -msgid "" -"Your OpenStack environment now includes Object Storage. You can :ref:`launch-" -"instance` or add more services to your environment." +#: ../keystone-services.rst:55 +msgid "Configure the endpoint URL:" msgstr "" -#: ../heat-next-step.rst:5 +#: ../keystone-services.rst:65 msgid "" -"Your OpenStack environment now includes Orchestration. You can :ref:`launch-" -"instance` or add more services to your environment in the following chapters." +"The packages can automatically create the service entity and API endpoint." msgstr "" -#: ../ceilometer-next-steps.rst:5 +#: ../keystone-services.rst:68 +msgid "Configure the Identity API version:" +msgstr "" + +#: ../keystone-services.rst:77 msgid "" -"Your OpenStack environment now includes Telemetry. You can :ref:`launch-" -"instance` or add more services to your environment." +"The Identity service manages a catalog of services in your OpenStack " +"environment. Services use this catalog to determine the other services " +"available in your environment." +msgstr "" + +#: ../keystone-services.rst:81 +msgid "Create the service entity for the Identity service:" +msgstr "" + +#: ../keystone-services.rst:102 +msgid "" +"The Identity service manages a catalog of API endpoints associated with the " +"services in your OpenStack environment. Services use this catalog to " +"determine how to communicate with other services in your environment." +msgstr "" + +#: ../keystone-services.rst:106 +msgid "" +"OpenStack uses three API endpoint variants for each service: admin, " +"internal, and public. The admin API endpoint allows modifying users and " +"tenants by default, while the public and internal APIs do not allow these " +"operations. In a production environment, the variants might reside on " +"separate networks that service different types of users for security " +"reasons. For instance, the public API network might be visible from the " +"Internet so customers can manage their clouds. The admin API network might " +"be restricted to operators within the organization that manages cloud " +"infrastructure. The internal API network might be restricted to the hosts " +"that contain OpenStack services. Also, OpenStack supports multiple regions " +"for scalability. For simplicity, this guide uses the management network for " +"all endpoint variations and the default ``RegionOne`` region." +msgstr "" + +#: ../keystone-services.rst:120 +msgid "Create the Identity service API endpoints:" +msgstr "" + +#: ../keystone-services.rst:174 +msgid "" +"Each service that you add to your OpenStack environment requires one or more " +"service entities and three API endpoint variants in the Identity service." +msgstr "" + +#: ../keystone-users.rst:2 +msgid "Create projects, users, and roles" +msgstr "" + +#: ../keystone-users.rst:4 +msgid "" +"The Identity service provides authentication services for each OpenStack " +"service. The authentication service uses a combination of :term:`domains " +"`, :term:`projects` (tenants), :term:`users`, and :" +"term:`roles`." +msgstr "" + +#: ../keystone-users.rst:11 +msgid "For simplicity, this guide uses the ``default`` domain." +msgstr "" + +#: ../keystone-users.rst:13 +msgid "" +"Create an administrative project, user, and role for administrative " +"operations in your environment:" +msgstr "" + +#: ../keystone-users.rst:16 +msgid "Create the ``admin`` project:" +msgstr "" + +#: ../keystone-users.rst:39 +msgid "Create the ``admin`` user:" +msgstr "" + +#: ../keystone-users.rst:56 +msgid "Create the ``admin`` role:" +msgstr "" + +#: ../keystone-users.rst:68 +msgid "Add the ``admin`` role to the ``admin`` project and user:" +msgstr "" + +#: ../keystone-users.rst:80 +msgid "" +"Any roles that you create must map to roles specified in the ``policy.json`` " +"file in the configuration file directory of each OpenStack service. The " +"default policy for most services grants administrative access to the " +"``admin`` role. For more information, see the `Operations Guide - Managing " +"Projects and Users `__." +msgstr "" + +#: ../keystone-users.rst:87 +msgid "" +"This guide uses a service project that contains a unique user for each " +"service that you add to your environment. Create the ``service`` project:" +msgstr "" + +#: ../keystone-users.rst:107 +msgid "" +"Regular (non-admin) tasks should use an unprivileged project and user. As an " +"example, this guide creates the ``demo`` project and user." +msgstr "" + +#: ../keystone-users.rst:110 +msgid "Create the ``demo`` project:" +msgstr "" + +#: ../keystone-users.rst:130 +msgid "" +"Do not repeat this step when creating additional users for this project." +msgstr "" + +#: ../keystone-users.rst:133 +msgid "Create the ``demo`` user:" +msgstr "" + +#: ../keystone-users.rst:150 +msgid "Create the ``user`` role:" +msgstr "" + +#: ../keystone-users.rst:162 +msgid "Add the ``user`` role to the ``demo`` project and user:" +msgstr "" + +#: ../keystone-users.rst:174 +msgid "You can repeat this procedure to create additional projects and users." +msgstr "" + +#: ../keystone-verify.rst:4 +msgid "" +"Verify operation of the Identity service before installing other services." +msgstr "" + +#: ../keystone-verify.rst:9 ../keystone-verify.rst:19 +msgid "" +"For security reasons, disable the temporary authentication token mechanism:" +msgstr "" + +#: ../keystone-verify.rst:12 +msgid "" +"Edit the ``/etc/keystone/keystone-paste.ini`` file and remove " +"``admin_token_auth`` from the ``[pipeline:public_api]``, ``[pipeline:" +"admin_api]``, and ``[pipeline:api_v3]`` sections." +msgstr "" + +#: ../keystone-verify.rst:22 +msgid "" +"Edit the ``/usr/share/keystone/keystone-dist-paste.ini`` file and remove " +"``admin_token_auth`` from the ``[pipeline:public_api]``, ``[pipeline:" +"admin_api]``, and ``[pipeline:api_v3]`` sections." +msgstr "" + +#: ../keystone-verify.rst:27 +msgid "Unset the temporary ``OS_TOKEN`` and ``OS_URL`` environment variables:" +msgstr "" + +#: ../keystone-verify.rst:33 +msgid "As the ``admin`` user, request an authentication token:" +msgstr "" + +#: ../keystone-verify.rst:53 +msgid "This command uses the password for the ``admin`` user." +msgstr "" + +#: ../keystone-verify.rst:55 +msgid "As the ``demo`` user, request an authentication token:" +msgstr "" + +#: ../keystone-verify.rst:75 +msgid "" +"This command uses the password for the ``demo`` user and API port 5000 which " +"only allows regular (non-admin) access to the Identity service API." +msgstr "" + +#: ../keystone.rst:3 +msgid "Add the Identity service" +msgstr "" + +# #-#-#-#-# launch-instance-cinder.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# launch-instance.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# overview.pot (Installation Guide 0.1) #-#-#-#-# +#: ../launch-instance-cinder.rst:4 ../launch-instance.rst:122 +#: ../overview.rst:163 +msgid "Block Storage" +msgstr "" + +#: ../launch-instance-cinder.rst:7 +msgid "Create a volume" +msgstr "" + +#: ../launch-instance-cinder.rst:9 +msgid "" +"Source the ``demo`` credentials to perform the following steps as a non-" +"administrative project:" +msgstr "" + +#: ../launch-instance-cinder.rst:16 +msgid "Create a 1 GB volume:" +msgstr "" + +#: ../launch-instance-cinder.rst:41 +msgid "" +"After a short time, the volume status should change from ``creating`` to " +"``available``:" +msgstr "" + +#: ../launch-instance-cinder.rst:54 +msgid "Attach the volume to an instance" +msgstr "" + +#: ../launch-instance-cinder.rst:56 +msgid "Attach a volume to an instance:" +msgstr "" + +#: ../launch-instance-cinder.rst:62 +msgid "" +"Replace ``INSTANCE_NAME`` with the name of the instance and ``VOLUME_ID`` " +"with the ID of the volume you want to attach to it." +msgstr "" + +# #-#-#-#-# launch-instance-cinder.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# launch-instance-networks-private.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# launch-instance-networks-public.pot (Installation Guide 0.1) #-#-#-#-# +#: ../launch-instance-cinder.rst:65 ../launch-instance-networks-private.rst:96 +#: ../launch-instance-networks-public.rst:105 +msgid "**Example**" +msgstr "" + +#: ../launch-instance-cinder.rst:67 +msgid "" +"Attach the ``0a816b7c-e578-4290-bb74-c13b8b90d4e7`` volume to the ``public-" +"instance`` instance:" +msgstr "" + +#: ../launch-instance-cinder.rst:82 +msgid "List volumes:" +msgstr "" + +#: ../launch-instance-cinder.rst:93 +msgid "" +"Access your instance using SSH and use the ``fdisk`` command to verify " +"presence of the volume as the ``/dev/vdb`` block storage device:" +msgstr "" + +#: ../launch-instance-cinder.rst:121 +msgid "You must create a partition table and file system to use the volume." +msgstr "" + +#: ../launch-instance-cinder.rst:123 +msgid "" +"For more information about how to manage volumes, see the `OpenStack User " +"Guide `__." +msgstr "" + +#: ../launch-instance-cinder.rst:127 +msgid "Return to :ref:`launch-instance`." +msgstr "" + +#: ../launch-instance-networks-private.rst:4 +msgid "Private project network" +msgstr "" + +#: ../launch-instance-networks-private.rst:6 +msgid "" +"If you chose networking option 2, you can also create a private project " +"virtual network that connects to the physical network infrastructure via " +"layer-3 (routing) and NAT. This network includes a DHCP server that provides " +"IP addresses to instances. An instance on this network can automatically " +"access external networks such as the Internet. However, access to an " +"instance on this network from external networks such as the Internet " +"requires a :term:`floating IP address`." +msgstr "" + +#: ../launch-instance-networks-private.rst:14 +msgid "" +"The ``demo`` or other unprivileged user can create this network because it " +"only provides connectivity to instances within the ``demo`` project." +msgstr "" + +#: ../launch-instance-networks-private.rst:19 +msgid "" +"You must :ref:`create the public provider network ` before the private project network." +msgstr "" + +# #-#-#-#-# launch-instance-networks-private.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# launch-instance-networks-public.pot (Installation Guide 0.1) #-#-#-#-# +#: ../launch-instance-networks-private.rst:24 +#: ../launch-instance-networks-public.rst:17 +msgid "" +"The following instructions and diagrams use example IP address ranges. You " +"must adjust them for your particular environment." +msgstr "" + +#: ../launch-instance-networks-private.rst:30 +msgid "**Networking Option 2: Self-service networks - Overview**" +msgstr "" + +#: ../launch-instance-networks-private.rst:35 +msgid "**Networking Option 2: Self-service networks - Connectivity**" +msgstr "" + +#: ../launch-instance-networks-private.rst:38 +msgid "Create the private project network" +msgstr "" + +# #-#-#-#-# launch-instance-networks-private.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# launch-instance-private.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# launch-instance-public.pot (Installation Guide 0.1) #-#-#-#-# +#: ../launch-instance-networks-private.rst:40 +#: ../launch-instance-private.rst:12 ../launch-instance-public.rst:12 +msgid "" +"On the controller node, source the ``demo`` credentials to gain access to " +"user-only CLI commands:" +msgstr "" + +# #-#-#-#-# launch-instance-networks-private.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# launch-instance-networks-public.pot (Installation Guide 0.1) #-#-#-#-# +#: ../launch-instance-networks-private.rst:47 +#: ../launch-instance-networks-public.rst:40 +msgid "Create the network:" +msgstr "" + +#: ../launch-instance-networks-private.rst:68 +msgid "" +"Non-privileged users typically cannot supply additional parameters to this " +"command. The service automatically chooses paramters using information from " +"the following files:" +msgstr "" + +# #-#-#-#-# launch-instance-networks-private.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# launch-instance-networks-public.pot (Installation Guide 0.1) #-#-#-#-# +#: ../launch-instance-networks-private.rst:72 +#: ../launch-instance-networks-public.rst:72 +msgid "``ml2_conf.ini``:" +msgstr "" + +# #-#-#-#-# launch-instance-networks-private.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# launch-instance-networks-public.pot (Installation Guide 0.1) #-#-#-#-# +#: ../launch-instance-networks-private.rst:82 +#: ../launch-instance-networks-public.rst:86 +msgid "Create a subnet on the network:" +msgstr "" + +#: ../launch-instance-networks-private.rst:89 +msgid "" +"Replace ``PRIVATE_NETWORK_CIDR`` with the subnet you want to use on the " +"private network. You can use any arbitrary value, although we recommend a " +"network from `RFC 1918 `_." +msgstr "" + +#: ../launch-instance-networks-private.rst:93 +msgid "" +"Replace ``PRIVATE_NETWORK_GATEWAY`` with the gateway you want to use on the " +"private network, typically the \".1\" IP address." +msgstr "" + +#: ../launch-instance-networks-private.rst:98 +msgid "The private network uses 172.16.1.0/24 with a gateway on 172.16.1.1:" +msgstr "" + +#: ../launch-instance-networks-private.rst:124 +msgid "Create a router" +msgstr "" + +#: ../launch-instance-networks-private.rst:126 +msgid "" +"Private project networks connect to public provider networks using a virtual " +"router. Each router contains an interface to at least one private project " +"network and a gateway on a public provider network." +msgstr "" + +#: ../launch-instance-networks-private.rst:130 +msgid "" +"The public provider network must include the ``router: external`` option to " +"enable project routers to use it for connectivity to external networks such " +"as the Internet. The ``admin`` or other privileged user must include this " +"option during network creation or add it later. In this case, we can add it " +"to the existing ``public`` provider network." +msgstr "" + +# #-#-#-#-# launch-instance-networks-private.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# launch-instance-networks-public.pot (Installation Guide 0.1) #-#-#-#-# +#: ../launch-instance-networks-private.rst:136 +#: ../launch-instance-networks-private.rst:195 +#: ../launch-instance-networks-public.rst:33 +msgid "" +"On the controller node, source the ``admin`` credentials to gain access to " +"admin-only CLI commands:" +msgstr "" + +#: ../launch-instance-networks-private.rst:143 +msgid "Add the ``router: external`` option to the ``public`` provider network:" +msgstr "" + +#: ../launch-instance-networks-private.rst:150 +msgid "" +"Source the ``demo`` credentials to gain access to user-only CLI commands:" +msgstr "" + +#: ../launch-instance-networks-private.rst:156 +msgid "Create the router:" +msgstr "" + +#: ../launch-instance-networks-private.rst:174 +msgid "Add the private network subnet as an interface on the router:" +msgstr "" + +#: ../launch-instance-networks-private.rst:181 +msgid "Set a gateway on the public network on the router:" +msgstr "" + +#: ../launch-instance-networks-private.rst:191 +msgid "" +"We recommend that you verify operation and fix any issues before proceeding " +"The following steps use the IP address ranges from the network and subnet " +"creation examples." +msgstr "" + +#: ../launch-instance-networks-private.rst:202 +msgid "" +"List network namespaces. You should see one ``qrouter`` namespace and two " +"``qdhcp`` namespaces." +msgstr "" + +#: ../launch-instance-networks-private.rst:212 +msgid "" +"List ports on the router to determine the gateway IP address on the public " +"provider network:" +msgstr "" + +#: ../launch-instance-networks-private.rst:229 +msgid "" +"Ping this IP address from the controller node or any host on the public " +"physical network:" +msgstr "" + +# #-#-#-#-# launch-instance-networks-private.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# launch-instance-networks-public.pot (Installation Guide 0.1) #-#-#-#-# +#: ../launch-instance-networks-private.rst:244 +#: ../launch-instance-networks-public.rst:135 +msgid "" +"Return to :ref:`Launch an instance - Create virtual networks `." +msgstr "" + +#: ../launch-instance-networks-public.rst:4 +msgid "Public provider network" +msgstr "" + +#: ../launch-instance-networks-public.rst:6 +msgid "" +"Before launching an instance, you must create the necessary virtual network " +"infrastructure. For networking option 1, an instance uses a public provider " +"virtual network that connects to the physical network infrastructure via " +"layer-2 (bridging/switching). This network includes a DHCP server that " +"provides IP addresses to instances." +msgstr "" + +#: ../launch-instance-networks-public.rst:12 +msgid "" +"The ``admin`` or other privileged user must create this network because it " +"connects directly to the physical network infrastructure." +msgstr "" + +#: ../launch-instance-networks-public.rst:23 +msgid "**Networking Option 1: Provider networks - Overview**" +msgstr "" + +#: ../launch-instance-networks-public.rst:28 +msgid "**Networking Option 2: Provider networks - Connectivity**" +msgstr "" + +#: ../launch-instance-networks-public.rst:31 +msgid "Create the public network" +msgstr "" + +#: ../launch-instance-networks-public.rst:65 +msgid "The ``--shared`` option allows all projects to use the virtual network." +msgstr "" + +#: ../launch-instance-networks-public.rst:67 +msgid "" +"The ``--provider:physical_network public`` and ``--provider:network_type " +"flat`` options connect the flat virtual network to the flat (native/" +"untagged) public physical network on the ``eth1`` interface on the host " +"using information from the following files:" +msgstr "" + +#: ../launch-instance-networks-public.rst:79 +msgid "``linuxbridge_agent.ini``:" +msgstr "" + +#: ../launch-instance-networks-public.rst:94 +msgid "" +"Replace ``PUBLIC_NETWORK_CIDR`` with the subnet on the public physical " +"network in CIDR notation." +msgstr "" + +#: ../launch-instance-networks-public.rst:97 +msgid "" +"Replace ``START_IP_ADDRESS`` and ``END_IP_ADDRESS`` with the first and last " +"IP address of the range within the subnet that you want to allocate for " +"instances. This range must not include any existing active IP addresses." +msgstr "" + +#: ../launch-instance-networks-public.rst:102 +msgid "" +"Replace ``PUBLIC_NETWORK_GATEWAY`` with the gateway IP address on the public " +"physical network, typically the \".1\" IP address." +msgstr "" + +#: ../launch-instance-networks-public.rst:107 +msgid "" +"The public physical network uses 203.0.113.0/24 with a gateway on " +"203.0.113.1 and instances can use 203.0.113.101 to 203.0.113.200." +msgstr "" + +#: ../launch-instance-private.rst:4 +msgid "Launch an instance on the private network" +msgstr "" + +# #-#-#-#-# launch-instance-private.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# launch-instance-public.pot (Installation Guide 0.1) #-#-#-#-# +#: ../launch-instance-private.rst:7 ../launch-instance-public.rst:7 +msgid "Determine instance options" +msgstr "" + +# #-#-#-#-# launch-instance-private.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# launch-instance-public.pot (Installation Guide 0.1) #-#-#-#-# +#: ../launch-instance-private.rst:9 ../launch-instance-public.rst:9 +msgid "" +"To launch an instance, you must at least specify the flavor, image name, " +"network, security group, key, and instance name." +msgstr "" + +# #-#-#-#-# launch-instance-private.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# launch-instance-public.pot (Installation Guide 0.1) #-#-#-#-# +#: ../launch-instance-private.rst:19 ../launch-instance-public.rst:19 +msgid "" +"A flavor specifies a virtual resource allocation profile which includes " +"processor, memory, and storage." +msgstr "" + +# #-#-#-#-# launch-instance-private.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# launch-instance-public.pot (Installation Guide 0.1) #-#-#-#-# +#: ../launch-instance-private.rst:22 ../launch-instance-public.rst:22 +msgid "List available flavors:" +msgstr "" + +# #-#-#-#-# launch-instance-private.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# launch-instance-public.pot (Installation Guide 0.1) #-#-#-#-# +#: ../launch-instance-private.rst:37 ../launch-instance-public.rst:37 +msgid "This instance uses the ``m1.tiny`` flavor." +msgstr "" + +# #-#-#-#-# launch-instance-private.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# launch-instance-public.pot (Installation Guide 0.1) #-#-#-#-# +#: ../launch-instance-private.rst:41 ../launch-instance-public.rst:41 +msgid "You can also reference a flavor by ID." +msgstr "" + +# #-#-#-#-# launch-instance-private.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# launch-instance-public.pot (Installation Guide 0.1) #-#-#-#-# +#: ../launch-instance-private.rst:43 ../launch-instance-public.rst:43 +msgid "List available images:" +msgstr "" + +# #-#-#-#-# launch-instance-private.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# launch-instance-public.pot (Installation Guide 0.1) #-#-#-#-# +#: ../launch-instance-private.rst:54 ../launch-instance-public.rst:54 +msgid "This instance uses the ``cirros`` image." +msgstr "" + +# #-#-#-#-# launch-instance-private.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# launch-instance-public.pot (Installation Guide 0.1) #-#-#-#-# +#: ../launch-instance-private.rst:56 ../launch-instance-public.rst:56 +msgid "List available networks:" +msgstr "" + +#: ../launch-instance-private.rst:68 +msgid "" +"This instance uses the ``private`` project network. However, you must " +"reference this network using the ID instead of the name." +msgstr "" + +# #-#-#-#-# launch-instance-private.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# launch-instance-public.pot (Installation Guide 0.1) #-#-#-#-# +#: ../launch-instance-private.rst:71 ../launch-instance-public.rst:74 +msgid "List available security groups:" +msgstr "" + +# #-#-#-#-# launch-instance-private.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# launch-instance-public.pot (Installation Guide 0.1) #-#-#-#-# +#: ../launch-instance-private.rst:82 ../launch-instance-public.rst:85 +msgid "This instance uses the ``default`` security group." +msgstr "" + +# #-#-#-#-# launch-instance-private.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# launch-instance-public.pot (Installation Guide 0.1) #-#-#-#-# +#: ../launch-instance-private.rst:84 ../launch-instance-public.rst:90 +msgid "Launch the instance:" +msgstr "" + +#: ../launch-instance-private.rst:86 +msgid "" +"Replace ``PRIVATE_NET_ID`` with the ID of the ``private`` project network." +msgstr "" + +# #-#-#-#-# launch-instance-private.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# launch-instance-public.pot (Installation Guide 0.1) #-#-#-#-# +#: ../launch-instance-private.rst:123 ../launch-instance-public.rst:135 +msgid "Check the status of your instance:" +msgstr "" + +# #-#-#-#-# launch-instance-private.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# launch-instance-public.pot (Installation Guide 0.1) #-#-#-#-# +#: ../launch-instance-private.rst:135 ../launch-instance-public.rst:146 +msgid "" +"The status changes from ``BUILD`` to ``ACTIVE`` when the build process " +"successfully completes." +msgstr "" + +#: ../launch-instance-private.rst:139 +msgid "Access the instance using a virtual console" +msgstr "" + +# #-#-#-#-# launch-instance-private.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# launch-instance-public.pot (Installation Guide 0.1) #-#-#-#-# +#: ../launch-instance-private.rst:141 ../launch-instance-public.rst:152 +msgid "" +"Obtain a :term:`Virtual Network Computing (VNC)` session URL for your " +"instance and access it from a web browser:" +msgstr "" + +# #-#-#-#-# launch-instance-private.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# launch-instance-public.pot (Installation Guide 0.1) #-#-#-#-# +#: ../launch-instance-private.rst:155 ../launch-instance-public.rst:166 +msgid "" +"If your web browser runs on a host that cannot resolve the ``controller`` " +"host name, you can replace ``controller`` with the IP address of the " +"management interface on your controller node." +msgstr "" + +# #-#-#-#-# launch-instance-private.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# launch-instance-public.pot (Installation Guide 0.1) #-#-#-#-# +#: ../launch-instance-private.rst:159 ../launch-instance-public.rst:170 +msgid "" +"The CirrOS image includes conventional user name/password authentication and " +"provides these credentials at the login prompt. After logging into CirrOS, " +"we recommend that you verify network connectivity using ``ping``." +msgstr "" + +#: ../launch-instance-private.rst:164 +msgid "Verify access to the ``private`` project network gateway:" +msgstr "" + +# #-#-#-#-# launch-instance-private.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# launch-instance-public.pot (Installation Guide 0.1) #-#-#-#-# +#: ../launch-instance-private.rst:179 ../launch-instance-public.rst:190 +msgid "Verify access to the internet:" +msgstr "" + +# #-#-#-#-# launch-instance-private.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# launch-instance-public.pot (Installation Guide 0.1) #-#-#-#-# +#: ../launch-instance-private.rst:195 ../launch-instance-public.rst:206 +msgid "Access the instance remotely" +msgstr "" + +#: ../launch-instance-private.rst:197 +msgid "" +"Create a :term:`floating IP address` on the ``public`` provider network:" +msgstr "" + +#: ../launch-instance-private.rst:216 +msgid "Associate the floating IP address with the instance:" +msgstr "" + +#: ../launch-instance-private.rst:226 +msgid "Check the status of your floating IP address:" +msgstr "" + +#: ../launch-instance-private.rst:238 +msgid "" +"Verify connectivity to the instance via floating IP address from the " +"controller node or any host on the public physical network:" +msgstr "" + +# #-#-#-#-# launch-instance-private.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# launch-instance-public.pot (Installation Guide 0.1) #-#-#-#-# +#: ../launch-instance-private.rst:254 ../launch-instance-public.rst:224 +msgid "" +"Access your instance using SSH from the controller node or any host on the " +"public physical network:" +msgstr "" + +# #-#-#-#-# launch-instance-private.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# launch-instance-public.pot (Installation Guide 0.1) #-#-#-#-# +#: ../launch-instance-private.rst:268 ../launch-instance-public.rst:238 +msgid "" +"If your host does not contain the public/private key pair created in an " +"earlier step, SSH prompts for the default password associated with the " +"``cirros`` user, ``cubswin:)``." +msgstr "" + +# #-#-#-#-# launch-instance-private.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# launch-instance-public.pot (Installation Guide 0.1) #-#-#-#-# +#: ../launch-instance-private.rst:272 ../launch-instance-public.rst:242 +msgid "" +"If your instance does not launch or seem to work as you expect, see the " +"`OpenStack Operations Guide `__ for more " +"information or use one of the :doc:`many other options ` " +"to seek assistance. We want your first installation to work!" +msgstr "" + +# #-#-#-#-# launch-instance-private.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# launch-instance-public.pot (Installation Guide 0.1) #-#-#-#-# +#: ../launch-instance-private.rst:277 ../launch-instance-public.rst:247 +msgid "Return to :ref:`Launch an instance `." +msgstr "" + +#: ../launch-instance-public.rst:4 +msgid "Launch an instance on the public network" +msgstr "" + +#: ../launch-instance-public.rst:67 +msgid "" +"This instance uses the ``public`` provider network. However, you must " +"reference this network using the ID instead of the name." +msgstr "" + +#: ../launch-instance-public.rst:72 +msgid "" +"If you chose option 2, the output should also contain the private network." +msgstr "" + +#: ../launch-instance-public.rst:88 +msgid "Launch the instance" +msgstr "" + +#: ../launch-instance-public.rst:92 +msgid "" +"Replace ``PUBLIC_NET_ID`` with the ID of the ``public`` provider network." +msgstr "" + +#: ../launch-instance-public.rst:96 +msgid "" +"If you chose option 1 and your environment contains only one network, you " +"can omit the ``--nic`` option because OpenStack automatically chooses the " +"only network available." +msgstr "" + +#: ../launch-instance-public.rst:150 +msgid "Access the instance using the virtual console" +msgstr "" + +#: ../launch-instance-public.rst:175 +msgid "Verify access to the public provider network gateway:" +msgstr "" + +#: ../launch-instance-public.rst:208 +msgid "" +"Verify connectivity to the instance from the controller node or any host on " +"the public physical network:" +msgstr "" + +#: ../launch-instance.rst:5 ../launch-instance.rst:107 +msgid "Launch an instance" +msgstr "" + +#: ../launch-instance.rst:7 +msgid "" +"This section creates the necessary virtual networks to support launching one " +"more instances. Networking option 1 includes one public virtual network and " +"one instance that uses it. Networking option 1 includes one public virtual " +"network, one private virtual network, and one instance that uses each " +"network. The instructions in this section use command-line interface (CLI) " +"tools on the controller node. For more information on the CLI tools, see the " +"`OpenStack User Guide `__. To use the dashboard, see the `OpenStack User " +"Guide `__." +msgstr "" + +#: ../launch-instance.rst:22 +msgid "Create virtual networks" +msgstr "" + +#: ../launch-instance.rst:24 +msgid "" +"Create virtual networks for the networking option that you chose in :ref:" +"`networking`. If you chose option 1, create only the public virtual network. " +"If you chose option 2, create the public and private virtual networks." +msgstr "" + +#: ../launch-instance.rst:35 +msgid "" +"After creating the appropriate networks for your environment, you can " +"continue preparing the environment to launch an instance." +msgstr "" + +#: ../launch-instance.rst:39 +msgid "Generate a key pair" +msgstr "" + +#: ../launch-instance.rst:41 +msgid "" +"Most cloud images support :term:`public key authentication` rather than " +"conventional password authentication. Before launching an instance, you must " +"add a public key to the Compute service." +msgstr "" + +#: ../launch-instance.rst:45 +msgid "Source the ``demo`` tenant credentials:" +msgstr "" + +#: ../launch-instance.rst:51 +msgid "Generate and add a key pair:" +msgstr "" + +#: ../launch-instance.rst:60 +msgid "" +"Alternatively, you can skip the ``ssh-keygen`` command and use an existing " +"public key." +msgstr "" + +#: ../launch-instance.rst:63 +msgid "Verify addition of the key pair:" +msgstr "" + +#: ../launch-instance.rst:75 +msgid "Add security group rules" +msgstr "" + +#: ../launch-instance.rst:77 +msgid "" +"By default, the ``default`` security group applies to all instances and " +"includes firewall rules that deny remote access to instances. For Linux " +"images such as CirrOS, we recommend allowing at least ICMP (ping) and secure " +"shell (SSH)." +msgstr "" + +#: ../launch-instance.rst:82 +msgid "Add rules to the ``default`` security group:" +msgstr "" + +#: ../launch-instance.rst:84 +msgid "Permit :term:`ICMP` (ping):" +msgstr "" + +#: ../launch-instance.rst:95 +msgid "Permit secure shell (SSH) access:" +msgstr "" + +#: ../launch-instance.rst:109 +msgid "" +"If you chose networking option 1, you can only launch an instance on the " +"public network. If you chose networking option 2, you can launch an instance " +"on the public network and the private network." +msgstr "" + +#: ../launch-instance.rst:124 +msgid "" +"If your environment includes the Block Storage service, you can create a " +"volume and attach it to an instance." +msgstr "" + +# #-#-#-#-# neutron-compute-install-option1.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# neutron-controller-install-option1.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# neutron-verify-option1.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# overview.pot (Installation Guide 0.1) #-#-#-#-# +#: ../neutron-compute-install-option1.rst:2 +#: ../neutron-controller-install-option1.rst:2 ../neutron-verify-option1.rst:2 +#: ../overview.rst:197 +msgid "Networking Option 1: Provider networks" +msgstr "" + +# #-#-#-#-# neutron-compute-install-option1.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# neutron-compute-install-option2.pot (Installation Guide 0.1) #-#-#-#-# +#: ../neutron-compute-install-option1.rst:4 +#: ../neutron-compute-install-option2.rst:4 +msgid "Configure the Networking components on a *compute* node." +msgstr "" + +# #-#-#-#-# neutron-compute-install-option1.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# neutron-compute-install-option2.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# neutron-controller-install-option1.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# neutron-controller-install-option2.pot (Installation Guide 0.1) #-#-#-#-# +#: ../neutron-compute-install-option1.rst:7 +#: ../neutron-compute-install-option2.rst:7 +#: ../neutron-controller-install-option1.rst:251 +#: ../neutron-controller-install-option2.rst:262 +msgid "Configure the Linux bridge agent" +msgstr "" + +# #-#-#-#-# neutron-compute-install-option1.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# neutron-compute-install-option2.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# neutron-controller-install-option1.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# neutron-controller-install-option2.pot (Installation Guide 0.1) #-#-#-#-# +#: ../neutron-compute-install-option1.rst:9 +#: ../neutron-compute-install-option2.rst:9 +#: ../neutron-controller-install-option1.rst:253 +#: ../neutron-controller-install-option2.rst:264 +msgid "" +"The Linux bridge agent builds layer-2 (bridging and switching) virtual " +"networking infrastructure for instances including VXLAN tunnels for private " +"networks and handles security groups." +msgstr "" + +# #-#-#-#-# neutron-compute-install-option1.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# neutron-compute-install-option2.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# neutron-controller-install-option1.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# neutron-controller-install-option2.pot (Installation Guide 0.1) #-#-#-#-# +#: ../neutron-compute-install-option1.rst:13 +#: ../neutron-compute-install-option2.rst:13 +#: ../neutron-controller-install-option1.rst:257 +#: ../neutron-controller-install-option2.rst:268 +msgid "" +"Edit the ``/etc/neutron/plugins/ml2/linuxbridge_agent.conf`` file and " +"complete the following actions:" +msgstr "" + +# #-#-#-#-# neutron-compute-install-option1.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# neutron-compute-install-option2.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# neutron-controller-install-option1.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# neutron-controller-install-option2.pot (Installation Guide 0.1) #-#-#-#-# +#: ../neutron-compute-install-option1.rst:16 +#: ../neutron-compute-install-option2.rst:16 +#: ../neutron-controller-install-option1.rst:260 +#: ../neutron-controller-install-option2.rst:271 +msgid "" +"In the ``[linux_bridge]`` section, map the public virtual network to the " +"public physical network interface:" +msgstr "" + +# #-#-#-#-# neutron-compute-install-option1.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# neutron-compute-install-option2.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# neutron-controller-install-option1.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# neutron-controller-install-option2.pot (Installation Guide 0.1) #-#-#-#-# +#: ../neutron-compute-install-option1.rst:24 +#: ../neutron-compute-install-option2.rst:24 +#: ../neutron-controller-install-option1.rst:268 +#: ../neutron-controller-install-option2.rst:279 +msgid "" +"Replace ``PUBLIC_INTERFACE_NAME`` with the name of the underlying physical " +"public network interface." +msgstr "" + +# #-#-#-#-# neutron-compute-install-option1.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# neutron-controller-install-option1.pot (Installation Guide 0.1) #-#-#-#-# +#: ../neutron-compute-install-option1.rst:27 +#: ../neutron-controller-install-option1.rst:271 +msgid "In the ``[vxlan]`` section, disable VXLAN overlay networks:" +msgstr "" + +# #-#-#-#-# neutron-compute-install-option1.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# neutron-compute-install-option2.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# neutron-controller-install-option1.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# neutron-controller-install-option2.pot (Installation Guide 0.1) #-#-#-#-# +#: ../neutron-compute-install-option1.rst:34 +#: ../neutron-compute-install-option2.rst:42 +#: ../neutron-controller-install-option1.rst:278 +#: ../neutron-controller-install-option2.rst:297 +msgid "In the ``[agent]`` section, enable ARP spoofing protection:" +msgstr "" + +# #-#-#-#-# neutron-compute-install-option1.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# neutron-compute-install-option2.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# neutron-controller-install-option1.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# neutron-controller-install-option2.pot (Installation Guide 0.1) #-#-#-#-# +#: ../neutron-compute-install-option1.rst:42 +#: ../neutron-compute-install-option2.rst:50 +#: ../neutron-controller-install-option1.rst:286 +#: ../neutron-controller-install-option2.rst:305 +msgid "" +"In the ``[securitygroup]`` section, enable security groups, enable :term:" +"`ipset`, and configure the Linux bridge :term:`iptables` firewall driver:" +msgstr "" + +# #-#-#-#-# neutron-compute-install-option1.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# neutron-compute-install-option2.pot (Installation Guide 0.1) #-#-#-#-# +#: ../neutron-compute-install-option1.rst:54 +#: ../neutron-compute-install-option2.rst:62 +msgid "" +"Return to :ref:`Networking compute node configuration `." +msgstr "" + +# #-#-#-#-# neutron-compute-install-option2.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# neutron-controller-install-option2.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# neutron-verify-option2.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# overview.pot (Installation Guide 0.1) #-#-#-#-# +#: ../neutron-compute-install-option2.rst:2 +#: ../neutron-controller-install-option2.rst:2 ../neutron-verify-option2.rst:2 +#: ../overview.rst:221 +msgid "Networking Option 2: Self-service networks" +msgstr "" + +# #-#-#-#-# neutron-compute-install-option2.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# neutron-controller-install-option2.pot (Installation Guide 0.1) #-#-#-#-# +#: ../neutron-compute-install-option2.rst:27 +#: ../neutron-controller-install-option2.rst:282 +msgid "" +"In the ``[vxlan]`` section, enable VXLAN overlay networks, configure the IP " +"address of the physical network interface that handles overlay networks, and " +"enable layer-2 population:" +msgstr "" + +# #-#-#-#-# neutron-compute-install-option2.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# neutron-controller-install-option2.pot (Installation Guide 0.1) #-#-#-#-# +#: ../neutron-compute-install-option2.rst:38 +#: ../neutron-controller-install-option2.rst:293 +msgid "" +"Replace ``OVERLAY_INTERFACE_IP_ADDRESS`` with the IP address of the " +"underlying physical network interface that handles overlay networks. The " +"example architecture uses the management interface." +msgstr "" + +#: ../neutron-compute-install.rst:2 +msgid "Install and configure compute node" +msgstr "" + +#: ../neutron-compute-install.rst:4 +msgid "" +"The compute node handles connectivity and :term:`security groups ` for instances." +msgstr "" + +#: ../neutron-compute-install.rst:10 +msgid "" +"Before you install and configure OpenStack Networking, you must kernel " +"networking parameters to disable reverse-path filtering:" +msgstr "" + +# #-#-#-#-# neutron-compute-install.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# neutron-controller-install-option1.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# neutron-controller-install-option2.pot (Installation Guide 0.1) #-#-#-#-# +#: ../neutron-compute-install.rst:13 +#: ../neutron-controller-install-option1.rst:12 +#: ../neutron-controller-install-option2.rst:13 +msgid "Edit the ``/etc/sysctl.conf`` file to contain the following parameters:" +msgstr "" + +# #-#-#-#-# neutron-compute-install.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# neutron-controller-install-option1.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# neutron-controller-install-option2.pot (Installation Guide 0.1) #-#-#-#-# +#: ../neutron-compute-install.rst:20 +#: ../neutron-controller-install-option1.rst:19 +#: ../neutron-controller-install-option2.rst:21 +msgid "Implement the changes:" +msgstr "" + +# #-#-#-#-# neutron-compute-install.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# neutron-controller-install-option1.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# neutron-controller-install-option2.pot (Installation Guide 0.1) #-#-#-#-# +#: ../neutron-compute-install.rst:29 +#: ../neutron-controller-install-option1.rst:26 +#: ../neutron-controller-install-option2.rst:28 +msgid "Install the components" +msgstr "" + +# #-#-#-#-# neutron-compute-install.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# neutron-controller-install-option2.pot (Installation Guide 0.1) #-#-#-#-# +#: ../neutron-compute-install.rst:52 +#: ../neutron-controller-install-option2.rst:57 +msgid "Install and configure the Networking components" +msgstr "" + +#: ../neutron-compute-install.rst:58 +msgid "" +"Respond to prompts for ``database management``, ``Identity service " +"credentials``, ``service endpoint``, and ``message queue credentials``." +msgstr "" + +# #-#-#-#-# neutron-compute-install.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# neutron-controller-install-option1.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# neutron-controller-install-option2.pot (Installation Guide 0.1) #-#-#-#-# +#: ../neutron-compute-install.rst:61 +#: ../neutron-controller-install-option1.rst:70 +#: ../neutron-controller-install-option2.rst:72 +msgid "Select the ML2 plug-in:" +msgstr "" + +# #-#-#-#-# neutron-compute-install.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# neutron-controller-install-option1.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# neutron-controller-install-option2.pot (Installation Guide 0.1) #-#-#-#-# +#: ../neutron-compute-install.rst:68 +#: ../neutron-controller-install-option1.rst:76 +#: ../neutron-controller-install-option2.rst:78 +msgid "" +"Selecting the ML2 plug-in also populates the ``service_plugins`` and " +"``allow_overlapping_ips`` options in the ``/etc/neutron/neutron.conf`` file " +"with the appropriate values." +msgstr "" + +#: ../neutron-compute-install.rst:75 +msgid "Configure the common component" +msgstr "" + +#: ../neutron-compute-install.rst:77 +msgid "" +"The Networking common component configuration includes the authentication " +"mechanism, message queue, and plug-in." +msgstr "" + +# #-#-#-#-# neutron-compute-install.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# neutron-controller-install-option1.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# neutron-controller-install-option2.pot (Installation Guide 0.1) #-#-#-#-# +#: ../neutron-compute-install.rst:82 +#: ../neutron-controller-install-option1.rst:91 +#: ../neutron-controller-install-option2.rst:87 +msgid "" +"Edit the ``/etc/neutron/neutron.conf`` file and complete the following " +"actions:" +msgstr "" + +#: ../neutron-compute-install.rst:85 +msgid "" +"In the ``[database]`` section, comment out any ``connection`` options " +"because compute nodes do not directly access the database." +msgstr "" + +# #-#-#-#-# neutron-compute-install.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# neutron-controller-install-option1.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# neutron-controller-install-option2.pot (Installation Guide 0.1) #-#-#-#-# +#: ../neutron-compute-install.rst:88 +#: ../neutron-controller-install-option1.rst:115 +#: ../neutron-controller-install-option2.rst:112 +msgid "" +"In the ``[DEFAULT]`` and ``[oslo_messaging_rabbit]`` sections, configure " +"RabbitMQ message queue access:" +msgstr "" + +# #-#-#-#-# neutron-compute-install.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# neutron-controller-install-option1.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# neutron-controller-install-option2.pot (Installation Guide 0.1) #-#-#-#-# +#: ../neutron-compute-install.rst:103 +#: ../neutron-controller-install-option1.rst:130 +#: ../neutron-controller-install-option2.rst:127 +msgid "" +"Replace ``RABBIT_PASS`` with the password you chose for the ``openstack`` " +"account in RabbitMQ." +msgstr "" + +# #-#-#-#-# neutron-compute-install.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# neutron-controller-install-option1.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# neutron-controller-install-option2.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# neutron-controller-install.pot (Installation Guide 0.1) #-#-#-#-# +#: ../neutron-compute-install.rst:126 ../neutron-compute-install.rst:184 +#: ../neutron-controller-install-option1.rst:153 +#: ../neutron-controller-install-option2.rst:150 +#: ../neutron-controller-install.rst:186 ../neutron-controller-install.rst:242 +msgid "" +"Replace ``NEUTRON_PASS`` with the password you chose for the ``neutron`` " +"user in the Identity service." +msgstr "" + +# #-#-#-#-# neutron-compute-install.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# neutron-controller-install.pot (Installation Guide 0.1) #-#-#-#-# +#: ../neutron-compute-install.rst:144 ../neutron-controller-install.rst:142 +msgid "Configure networking options" +msgstr "" + +#: ../neutron-compute-install.rst:146 +msgid "" +"Choose the same networking option that you chose for the controller node to " +"configure services specific to it." +msgstr "" + +# #-#-#-#-# neutron-compute-install.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# neutron-controller-install.pot (Installation Guide 0.1) #-#-#-#-# +#: ../neutron-compute-install.rst:151 ../neutron-controller-install.rst:149 +msgid "" +"Option 2 augments option 1 with the layer-3 (routing) service and enables " +"self-service (private) networks. If you want to use public (provider) and " +"private (self-service) networks, choose option 2." +msgstr "" + +# #-#-#-#-# neutron-compute-install.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# neutron-controller-install.pot (Installation Guide 0.1) #-#-#-#-# +#: ../neutron-compute-install.rst:164 ../neutron-controller-install.rst:218 +msgid "Configure Compute to use Networking" +msgstr "" + +# #-#-#-#-# neutron-compute-install.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# nova-compute-install.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# nova-controller-install.pot (Installation Guide 0.1) #-#-#-#-# +#: ../neutron-compute-install.rst:166 ../nova-compute-install.rst:53 +#: ../nova-controller-install.rst:181 +msgid "" +"Edit the ``/etc/nova/nova.conf`` file and complete the following actions:" +msgstr "" + +#: ../neutron-compute-install.rst:168 +msgid "In the ``[neutron]`` section, configure access parameters:" +msgstr "" + +# #-#-#-#-# neutron-compute-install.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# neutron-controller-install.pot (Installation Guide 0.1) #-#-#-#-# +#: ../neutron-compute-install.rst:192 ../neutron-controller-install.rst:253 +msgid "" +"The Networking service initialization scripts expect a symbolic link ``/etc/" +"neutron/plugin.ini`` pointing to the ML2 plug-in configuration file, ``/etc/" +"neutron/plugins/ml2/ml2_conf.ini``. If this symbolic link does not exist, " +"create it using the following command:" +msgstr "" + +# #-#-#-#-# neutron-compute-install.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# neutron-controller-install.pot (Installation Guide 0.1) #-#-#-#-# +#: ../neutron-compute-install.rst:201 ../neutron-controller-install.rst:262 +msgid "" +"Due to a packaging issue, the Linux bridge agent initialization script " +"explicitly looks for the Linux bridge plug-in configuration file rather than " +"the agent configuration file. Run the following commands to resolve this " +"issue:" +msgstr "" + +# #-#-#-#-# neutron-compute-install.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# neutron-controller-install.pot (Installation Guide 0.1) #-#-#-#-# +#: ../neutron-compute-install.rst:215 ../neutron-controller-install.rst:276 +msgid "" +"Future upgrades of the ``neutron-linuxbridge-agent`` package may overwrite " +"this modification." +msgstr "" + +#: ../neutron-compute-install.rst:224 +msgid "" +"Start the Linux bridge agent and configure it to start when the system boots:" +msgstr "" + +# #-#-#-#-# neutron-compute-install.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# neutron-controller-install.pot (Installation Guide 0.1) #-#-#-#-# +#: ../neutron-compute-install.rst:234 ../neutron-controller-install.rst:321 +msgid "" +"The Networking service initialization scripts expect the variable " +"``NEUTRON_PLUGIN_CONF`` in the ``/etc/sysconfig/neutron`` file to reference " +"the ML2 plug-in configuration file. Edit the ``/etc/sysconfig/neutron`` file " +"and add the following:" +msgstr "" + +#: ../neutron-compute-install.rst:249 +msgid "" +"Start the Linux Bridge agent and configure it to start when the system boots:" +msgstr "" + +#: ../neutron-compute-install.rst:265 +msgid "Restart the Linux bridge agent:" +msgstr "" + +#: ../neutron-concepts.rst:2 +msgid "Networking (neutron) concepts" +msgstr "" + +#: ../neutron-concepts.rst:4 +msgid "" +"OpenStack Networking (neutron) manages all networking facets for the Virtual " +"Networking Infrastructure (VNI) and the access layer aspects of the Physical " +"Networking Infrastructure (PNI) in your OpenStack environment. OpenStack " +"Networking enables tenants to create advanced virtual network topologies " +"which may include services such as a :term:`firewall`, a :term:`load " +"balancer`, and a :term:`virtual private network (VPN)`." +msgstr "" + +#: ../neutron-concepts.rst:12 +msgid "" +"Networking provides the networks, subnets, and routers object abstractions. " +"Each abstraction has functionality that mimics its physical counterpart: " +"networks contain subnets, and routers route traffic between different subnet " +"and networks." +msgstr "" + +#: ../neutron-concepts.rst:17 +msgid "" +"Each router has one gateway that connects to a network, and many interfaces " +"connected to subnets. Subnets can access machines on other subnets connected " +"to the same router." +msgstr "" + +#: ../neutron-concepts.rst:21 +msgid "" +"Any given Networking set up has at least one external network. Unlike the " +"other networks, the external network is not merely a virtually defined " +"network. Instead, it represents a view into a slice of the physical, " +"external network accessible outside the OpenStack installation. IP addresses " +"on the external network are accessible by anybody physically on the outside " +"network. Because the external network merely represents a view into the " +"outside network, DHCP is disabled on this network." +msgstr "" + +#: ../neutron-concepts.rst:30 +msgid "" +"In addition to external networks, any Networking set up has one or more " +"internal networks. These software-defined networks connect directly to the " +"VMs. Only the VMs on any given internal network, or those on subnets " +"connected through interfaces to a similar router, can access VMs connected " +"to that network directly." +msgstr "" + +#: ../neutron-concepts.rst:36 +msgid "" +"For the outside network to access VMs, and vice versa, routers between the " +"networks are needed. Each router has one gateway that is connected to a " +"network and many interfaces that are connected to subnets. Like a physical " +"router, subnets can access machines on other subnets that are connected to " +"the same router, and machines can access the outside network through the " +"gateway for the router." +msgstr "" + +#: ../neutron-concepts.rst:43 +msgid "" +"Additionally, you can allocate IP addresses on external networks to ports on " +"the internal network. Whenever something is connected to a subnet, that " +"connection is called a port. You can associate external network IP addresses " +"with ports to VMs. This way, entities on the outside network can access VMs." +msgstr "" + +#: ../neutron-concepts.rst:49 +msgid "" +"Networking also supports *security groups*. Security groups enable " +"administrators to define firewall rules in groups. A VM can belong to one or " +"more security groups, and Networking applies the rules in those security " +"groups to block or unblock ports, port ranges, or traffic types for that VM." +msgstr "" + +#: ../neutron-concepts.rst:55 +msgid "" +"Each plug-in that Networking uses has its own concepts. While not vital to " +"operating the VNI and OpenStack environment, understanding these concepts " +"can help you set up Networking. All Networking installations use a core plug-" +"in and a security group plug-in (or just the No-Op security group plug-in). " +"Additionally, Firewall-as-a-Service (FWaaS) and Load-Balancer-as-a-Service " +"(LBaaS) plug-ins are available." +msgstr "" + +# #-#-#-#-# neutron-controller-install-option1.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# neutron-controller-install-option2.pot (Installation Guide 0.1) #-#-#-#-# +#: ../neutron-controller-install-option1.rst:4 +#: ../neutron-controller-install-option2.rst:4 +msgid "" +"Install and configure the Networking components on the *controller* node." +msgstr "" + +#: ../neutron-controller-install-option1.rst:9 +msgid "" +"Before you configure networking option 1, you must configure kernel " +"parameters to disable reverse-path filtering." +msgstr "" + +#: ../neutron-controller-install-option1.rst:55 +msgid "Install and configure the networking components" +msgstr "" + +# #-#-#-#-# neutron-controller-install-option1.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# neutron-controller-install-option2.pot (Installation Guide 0.1) #-#-#-#-# +#: ../neutron-controller-install-option1.rst:62 +#: ../neutron-controller-install-option2.rst:64 +msgid "For networking option 2, also install the ``neutron-l3-agent`` package." +msgstr "" + +# #-#-#-#-# neutron-controller-install-option1.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# neutron-controller-install-option2.pot (Installation Guide 0.1) #-#-#-#-# +#: ../neutron-controller-install-option1.rst:64 +#: ../neutron-controller-install-option2.rst:66 +msgid "" +"Respond to prompts for `database management <#debconf-dbconfig-common>`__, " +"`Identity service credentials <#debconf-keystone_authtoken>`__, `service " +"endpoint registration <#debconf-api-endpoints>`__, and `message queue " +"credentials <#debconf-rabbitmq>`__." +msgstr "" + +# #-#-#-#-# neutron-controller-install-option1.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# neutron-controller-install-option2.pot (Installation Guide 0.1) #-#-#-#-# +#: ../neutron-controller-install-option1.rst:83 +#: ../neutron-controller-install-option2.rst:85 +msgid "Configure the server component" +msgstr "" + +#: ../neutron-controller-install-option1.rst:85 +msgid "" +"The Networking server component configuration includes the database, " +"authentication mechanism, message queue, topology change notifications, and " +"plug-in." +msgstr "" + +# #-#-#-#-# neutron-controller-install-option1.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# neutron-controller-install-option2.pot (Installation Guide 0.1) #-#-#-#-# +#: ../neutron-controller-install-option1.rst:102 +#: ../neutron-controller-install-option2.rst:98 +msgid "" +"Replace ``NEUTRON_DBPASS`` with the password you chose for the database." +msgstr "" + +#: ../neutron-controller-install-option1.rst:105 +msgid "" +"In the ``[DEFAULT]`` section, enable the Modular Layer 2 (ML2) plug-in and " +"disable additional plug-ins:" +msgstr "" + +# #-#-#-#-# neutron-controller-install-option1.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# neutron-controller-install-option2.pot (Installation Guide 0.1) #-#-#-#-# +#: ../neutron-controller-install-option1.rst:161 +#: ../neutron-controller-install-option2.rst:158 +msgid "" +"In the ``[DEFAULT]`` and ``[nova]`` sections, configure Networking to notify " +"Compute of network topology changes:" +msgstr "" + +# #-#-#-#-# neutron-controller-install-option1.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# neutron-controller-install-option2.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# nova-compute-install.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# nova-controller-install.pot (Installation Guide 0.1) #-#-#-#-# +#: ../neutron-controller-install-option1.rst:183 +#: ../neutron-controller-install-option2.rst:180 +#: ../nova-compute-install.rst:94 ../nova-controller-install.rst:233 +msgid "" +"Replace ``NOVA_PASS`` with the password you chose for the ``nova`` user in " +"the Identity service." +msgstr "" + +# #-#-#-#-# neutron-controller-install-option1.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# neutron-controller-install-option2.pot (Installation Guide 0.1) #-#-#-#-# +#: ../neutron-controller-install-option1.rst:196 +#: ../neutron-controller-install-option2.rst:193 +msgid "Configure the Modular Layer 2 (ML2) plug-in" +msgstr "" + +# #-#-#-#-# neutron-controller-install-option1.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# neutron-controller-install-option2.pot (Installation Guide 0.1) #-#-#-#-# +#: ../neutron-controller-install-option1.rst:198 +#: ../neutron-controller-install-option2.rst:195 +msgid "" +"The ML2 plug-in uses the Linux bridge mechanism to build layer-2 (bridging " +"and switching) virtual networking infrastructure for instances." +msgstr "" + +# #-#-#-#-# neutron-controller-install-option1.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# neutron-controller-install-option2.pot (Installation Guide 0.1) #-#-#-#-# +#: ../neutron-controller-install-option1.rst:201 +#: ../neutron-controller-install-option2.rst:198 +msgid "" +"Edit the ``/etc/neutron/plugins/ml2/ml2_conf.ini`` file and complete the " +"following actions:" +msgstr "" + +#: ../neutron-controller-install-option1.rst:204 +msgid "In the ``[ml2]`` section, enable flat and VLAN networks:" +msgstr "" + +#: ../neutron-controller-install-option1.rst:212 +msgid "In the ``[ml2]`` section, disable project (private) networks:" +msgstr "" + +#: ../neutron-controller-install-option1.rst:220 +msgid "In the ``[ml2]`` section, enable the Linux bridge mechanism:" +msgstr "" + +# #-#-#-#-# neutron-controller-install-option1.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# neutron-controller-install-option2.pot (Installation Guide 0.1) #-#-#-#-# +#: ../neutron-controller-install-option1.rst:230 +#: ../neutron-controller-install-option2.rst:228 +msgid "" +"After you configure the ML2 plug-in, removing values in the ``type_drivers`` " +"option can lead to database inconsistency." +msgstr "" + +# #-#-#-#-# neutron-controller-install-option1.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# neutron-controller-install-option2.pot (Installation Guide 0.1) #-#-#-#-# +#: ../neutron-controller-install-option1.rst:233 +#: ../neutron-controller-install-option2.rst:235 +msgid "In the ``[ml2]`` section, enable the port security extension driver:" +msgstr "" + +# #-#-#-#-# neutron-controller-install-option1.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# neutron-controller-install-option2.pot (Installation Guide 0.1) #-#-#-#-# +#: ../neutron-controller-install-option1.rst:241 +#: ../neutron-controller-install-option2.rst:243 +msgid "" +"In the ``[ml2_type_flat]`` section, configure the public flat provider " +"network:" +msgstr "" + +# #-#-#-#-# neutron-controller-install-option1.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# neutron-controller-install-option2.pot (Installation Guide 0.1) #-#-#-#-# +#: ../neutron-controller-install-option1.rst:299 +#: ../neutron-controller-install-option2.rst:351 +msgid "Configure the DHCP agent" +msgstr "" + +# #-#-#-#-# neutron-controller-install-option1.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# neutron-controller-install-option2.pot (Installation Guide 0.1) #-#-#-#-# +#: ../neutron-controller-install-option1.rst:301 +#: ../neutron-controller-install-option2.rst:353 +msgid "The :term:`DHCP agent` provides DHCP services for virtual networks." +msgstr "" + +# #-#-#-#-# neutron-controller-install-option1.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# neutron-controller-install-option2.pot (Installation Guide 0.1) #-#-#-#-# +#: ../neutron-controller-install-option1.rst:303 +#: ../neutron-controller-install-option2.rst:355 +msgid "" +"Edit the ``/etc/neutron/dhcp_agent.ini`` file and complete the following " +"actions:" +msgstr "" + +# #-#-#-#-# neutron-controller-install-option1.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# neutron-controller-install-option2.pot (Installation Guide 0.1) #-#-#-#-# +#: ../neutron-controller-install-option1.rst:306 +#: ../neutron-controller-install-option2.rst:358 +msgid "" +"In the ``[DEFAULT]`` section, configure the Linux bridge interface driver, " +"Dnsmasq DHCP driver, and enable isolated metadata so instances on public " +"networks can access metadata over the network:" +msgstr "" + +# #-#-#-#-# neutron-controller-install-option1.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# neutron-controller-install-option2.pot (Installation Guide 0.1) #-#-#-#-# +#: ../neutron-controller-install-option1.rst:327 +#: ../neutron-controller-install-option2.rst:423 +msgid "" +"Return to :ref:`Networking controller node configuration `." +msgstr "" + +#: ../neutron-controller-install-option2.rst:9 +msgid "" +"Before you configure networking option 2, you must configure kernel " +"parameters to enable IP forwarding (routing) and disable reverse-path " +"filtering." +msgstr "" + +#: ../neutron-controller-install-option2.rst:101 +msgid "" +"In the ``[DEFAULT]`` section, enable the Modular Layer 2 (ML2) plug-in, " +"router service, and overlapping IP addresses:" +msgstr "" + +#: ../neutron-controller-install-option2.rst:201 +msgid "In the ``[ml2]`` section, enable flat, VLAN, and VXLAN networks:" +msgstr "" + +#: ../neutron-controller-install-option2.rst:209 +msgid "In the ``[ml2]`` section, enable VXLAN project (private) networks:" +msgstr "" + +#: ../neutron-controller-install-option2.rst:217 +msgid "" +"In the ``[ml2]`` section, enable the Linux bridge and layer-2 population " +"mechanisms:" +msgstr "" + +#: ../neutron-controller-install-option2.rst:233 +msgid "The Linux bridge agent only supports VXLAN overlay networks." +msgstr "" + +#: ../neutron-controller-install-option2.rst:252 +msgid "" +"In the ``[ml2_type_vxlan]`` section, configure the VXLAN network identifier " +"range for private networks:" +msgstr "" + +#: ../neutron-controller-install-option2.rst:318 +msgid "Configure the layer-3 agent" +msgstr "" + +#: ../neutron-controller-install-option2.rst:320 +msgid "" +"The :term:`Layer-3 (L3) agent` provides routing and NAT services for virtual " +"networks." +msgstr "" + +#: ../neutron-controller-install-option2.rst:323 +msgid "" +"Edit the ``/etc/neutron/l3_agent.ini`` file and complete the following " +"actions:" +msgstr "" + +#: ../neutron-controller-install-option2.rst:326 +msgid "" +"In the ``[DEFAULT]`` section, configure the Linux bridge interface driver " +"and external network bridge:" +msgstr "" + +#: ../neutron-controller-install-option2.rst:338 +msgid "" +"The ``external_network_bridge`` option intentionally lacks a value to enable " +"multiple external networks on a single agent." +msgstr "" + +#: ../neutron-controller-install-option2.rst:379 +msgid "" +"Overlay networks such as VXLAN include additional packet headers that " +"increase overhead and decrease space available for the payload or user data. " +"Without knowledge of the virtual network infrastructure, instances attempt " +"to send packets using the default Ethernet :term:`maximum transmission unit " +"(MTU)` of 1500 bytes. :term:`Internet protocol (IP)` networks contain the :" +"term:`path MTU discovery (PMTUD)` mechanism to detect end-to-end MTU and " +"adjust packet size accordingly. However, some operating systems and networks " +"block or otherwise lack support for PMTUD causing performance degradation or " +"connectivity failure." +msgstr "" + +#: ../neutron-controller-install-option2.rst:389 +msgid "" +"Ideally, you can prevent these problems by enabling :term:`jumbo frames " +"` on the physical network that contains your tenant virtual " +"networks. Jumbo frames support MTUs up to approximately 9000 bytes which " +"negates the impact of VXLAN overhead on virtual networks. However, many " +"network devices lack support for jumbo frames and OpenStack administrators " +"often lack control over network infrastructure. Given the latter " +"complications, you can also prevent MTU problems by reducing the instance " +"MTU to account for VXLAN overhead. Determining the proper MTU value often " +"takes experimentation, but 1450 bytes works in most environments. You can " +"configure the DHCP server that assigns IP addresses to your instances to " +"also adjust the MTU." +msgstr "" + +#: ../neutron-controller-install-option2.rst:403 +msgid "" +"Some cloud images ignore the DHCP MTU option in which case you should " +"configure it using metadata, a script, or other suitable method." +msgstr "" + +#: ../neutron-controller-install-option2.rst:407 +msgid "" +"In the ``[DEFAULT]`` section, enable the :term:`dnsmasq` configuration file:" +msgstr "" + +#: ../neutron-controller-install-option2.rst:416 +msgid "" +"Create and edit the ``/etc/neutron/dnsmasq-neutron.conf`` file to enable the " +"DHCP MTU option (26) and configure it to 1450 bytes:" +msgstr "" + +#: ../neutron-controller-install.rst:7 +msgid "" +"Before you configure the OpenStack Networking (neutron) service, you must " +"create a database, service credentials, and API endpoints." +msgstr "" + +#: ../neutron-controller-install.rst:13 +msgid "Use the database access client to connect to the database server as the" +msgstr "" + +#: ../neutron-controller-install.rst:13 +msgid "``root`` user:" +msgstr "" + +#: ../neutron-controller-install.rst:19 +msgid "Create the ``neutron`` database:" +msgstr "" + +#: ../neutron-controller-install.rst:25 +msgid "" +"Grant proper access to the ``neutron`` database, replacing " +"``NEUTRON_DBPASS`` with a suitable password:" +msgstr "" + +#: ../neutron-controller-install.rst:46 +msgid "Create the ``neutron`` user:" +msgstr "" + +#: ../neutron-controller-install.rst:63 +msgid "Add the ``admin`` role to the ``neutron`` user:" +msgstr "" + +#: ../neutron-controller-install.rst:73 +msgid "Create the ``neutron`` service entity:" +msgstr "" + +#: ../neutron-controller-install.rst:89 +msgid "Create the Networking service API endpoints:" +msgstr "" + +#: ../neutron-controller-install.rst:144 +msgid "" +"Choose one of the following networking options to configure services " +"specific to it." +msgstr "" + +#: ../neutron-controller-install.rst:162 +msgid "Configure the metadata agent" +msgstr "" + +#: ../neutron-controller-install.rst:164 +msgid "" +"The :term:`metadata agent ` provides configuration " +"information such as credentials to instances." +msgstr "" + +#: ../neutron-controller-install.rst:167 +msgid "" +"Edit the ``/etc/neutron/metadata_agent.ini`` file and complete the following " +"actions:" +msgstr "" + +#: ../neutron-controller-install.rst:170 +msgid "In the ``[DEFAULT]`` section, configure access parameters:" +msgstr "" + +#: ../neutron-controller-install.rst:189 +msgid "In the ``[DEFAULT]`` section, configure the metadata host:" +msgstr "" + +#: ../neutron-controller-install.rst:197 +msgid "" +"In the ``[DEFAULT]`` section, configure the metadata proxy shared secret:" +msgstr "" + +#: ../neutron-controller-install.rst:206 +msgid "" +"Replace ``METADATA_SECRET`` with a suitable secret for the metadata proxy." +msgstr "" + +#: ../neutron-controller-install.rst:220 +msgid "" +"Edit the ``/etc/nova/nova.conf`` file and perform the following actions:" +msgstr "" + +#: ../neutron-controller-install.rst:222 +msgid "" +"In the ``[neutron]`` section, configure access parameters, enable the " +"metadata proxy, and configure the secret:" +msgstr "" + +#: ../neutron-controller-install.rst:245 +msgid "" +"Replace ``METADATA_SECRET`` with the secret you chose for the metadata proxy." +msgstr "" + +#: ../neutron-controller-install.rst:279 ../neutron-controller-install.rst:362 +msgid "Populate the database:" +msgstr "" + +#: ../neutron-controller-install.rst:288 ../neutron-controller-install.rst:371 +msgid "" +"Database population occurs later for Networking because the script requires " +"complete server and plug-in configuration files." +msgstr "" + +# #-#-#-#-# neutron-controller-install.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# nova-controller-install.pot (Installation Guide 0.1) #-#-#-#-# +#: ../neutron-controller-install.rst:291 ../neutron-controller-install.rst:330 +#: ../nova-controller-install.rst:387 +msgid "Restart the Compute services:" +msgstr "" + +#: ../neutron-controller-install.rst:298 ../neutron-controller-install.rst:337 +msgid "" +"Start the Networking services and configure them to start when the system " +"boots." +msgstr "" + +#: ../neutron-controller-install.rst:301 ../neutron-controller-install.rst:340 +#: ../neutron-controller-install.rst:382 +msgid "For both networking options:" +msgstr "" + +#: ../neutron-controller-install.rst:312 ../neutron-controller-install.rst:353 +msgid "For networking option 2, also enable and start the layer-3 service:" +msgstr "" + +#: ../neutron-controller-install.rst:374 +msgid "Restart the nova-api service:" +msgstr "" + +#: ../neutron-controller-install.rst:380 +msgid "Restart the Networking services." +msgstr "" + +#: ../neutron-controller-install.rst:391 +msgid "For networking option 2, also restart the layer-3 service:" msgstr "" #: ../neutron-next-steps.rst:5 @@ -6658,73 +5681,352 @@ msgid "" "OpenStack services to your environment." msgstr "" -#: ../dashboard-next-step.rst:5 +# #-#-#-#-# neutron-verify-option1.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# neutron-verify-option2.pot (Installation Guide 0.1) #-#-#-#-# +#: ../neutron-verify-option1.rst:4 ../neutron-verify-option2.rst:4 +msgid "List agents to verify successful launch of the neutron agents:" +msgstr "" + +#: ../neutron-verify-option1.rst:18 msgid "" -"Your OpenStack environment now includes the dashboard. You can :ref:`launch-" -"instance` or add more services to your environment." +"The output should indicate three agents on the controller node and one agent " +"on each compute node." msgstr "" -#: ../environment-networking.rst:316 +#: ../neutron-verify-option2.rst:19 msgid "" -"Your distribution does not enable a restrictive :term:`firewall` by default. " -"For more information about securing your environment, refer to the " -"`OpenStack Security Guide `__." +"The output should indicate four agents on the controller node and one agent " +"on each compute node." msgstr "" -#: ../environment-networking.rst:308 +#: ../neutron-verify.rst:11 msgid "" -"Your distribution enables a restrictive :term:`firewall` by default. During " -"the installation process, certain steps will fail unless you alter or " -"disable the firewall. For more information about securing your environment, " -"refer to the `OpenStack Security Guide `__." +"List loaded extensions to verify successful launch of the ``neutron-server`` " +"process:" msgstr "" -#: ../overview.rst:58 -msgid "`Block Storage `_" +#: ../neutron-verify.rst:45 +msgid "" +"Use the verification section for the networking option that you chose to " +"deploy." msgstr "" -#: ../overview.rst:77 -msgid "`Ceilometer `_" +#: ../neutron.rst:5 +msgid "Add the Networking service" msgstr "" -#: ../overview.rst:59 -msgid "`Cinder `_" +#: ../neutron.rst:7 +msgid "" +"This chapter explains how to install and configure the OpenStack Networking " +"service (neutron) using the :ref:`provider networks ` or :ref:" +"`self-service networks ` option. For more information about the " +"Networking service including virtual networking components, layout, and " +"traffic flows, see the `Networking Guide `__." msgstr "" -#: ../overview.rst:32 -msgid "`Compute `_" +#: ../nova-compute-install.rst:2 +msgid "Install and configure a compute node" +msgstr "" + +#: ../nova-compute-install.rst:4 +msgid "" +"This section describes how to install and configure the Compute service on a " +"compute node. The service supports several :term:`hypervisors ` " +"to deploy :term:`instances ` or :term:`VMs `. For simplicity, this configuration uses the :term:`QEMU ` hypervisor with the :term:`KVM ` " +"extension on compute nodes that support hardware acceleration for virtual " +"machines. On legacy hardware, this configuration uses the generic QEMU " +"hypervisor. You can follow these instructions with minor modifications to " +"horizontally scale your environment with additional compute nodes." +msgstr "" + +#: ../nova-compute-install.rst:17 +msgid "" +"This section assumes that you are following the instructions in this guide " +"step-by-step to configure the first compute node. If you want to configure " +"additional compute nodes, prepare them in a similar fashion to the first " +"compute node in the :ref:`example architectures ` section. Each additional compute node requires a unique IP " +"address." +msgstr "" + +#: ../nova-compute-install.rst:56 +msgid "" +"In the ``[DEFAULT]`` and [oslo_messaging_rabbit] sections, configure " +"``RabbitMQ`` message queue access:" +msgstr "" + +#: ../nova-compute-install.rst:110 +msgid "" +"Replace ``MANAGEMENT_INTERFACE_IP_ADDRESS`` with the IP address of the " +"management network interface on your compute node, typically 10.0.0.31 for " +"the first node in the :ref:`example architecture `." +msgstr "" + +# #-#-#-#-# nova-compute-install.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# nova-controller-install.pot (Installation Guide 0.1) #-#-#-#-# +#: ../nova-compute-install.rst:115 ../nova-controller-install.rst:250 +msgid "" +"In the ``[DEFAULT]`` section, enable support for the Networking service:" +msgstr "" + +# #-#-#-#-# nova-compute-install.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# nova-controller-install.pot (Installation Guide 0.1) #-#-#-#-# +#: ../nova-compute-install.rst:128 ../nova-controller-install.rst:263 +msgid "" +"By default, Compute uses an internal firewall service. Since Networking " +"includes a firewall service, you must disable the Compute firewall service " +"by using the ``nova.virt.firewall.NoopFirewallDriver`` firewall driver." +msgstr "" + +#: ../nova-compute-install.rst:133 +msgid "In the ``[vnc]`` section, enable and configure remote console access:" +msgstr "" + +#: ../nova-compute-install.rst:144 +msgid "" +"The server component listens on all IP addresses and the proxy component " +"only listens on the management interface IP address of the compute node. The " +"base URL indicates the location where you can use a web browser to access " +"remote consoles of instances on this compute node." +msgstr "" + +#: ../nova-compute-install.rst:152 +msgid "" +"If the web browser to access remote consoles resides on a host that cannot " +"resolve the ``controller`` hostname, you must replace ``controller`` with " +"the management interface IP address of the controller node." +msgstr "" + +# #-#-#-#-# nova-compute-install.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# nova-controller-install.pot (Installation Guide 0.1) #-#-#-#-# +#: ../nova-compute-install.rst:157 ../nova-controller-install.rst:278 +msgid "" +"In the ``[glance]`` section, configure the location of the Image service:" +msgstr "" + +#: ../nova-compute-install.rst:197 +msgid "Ensure the kernel module ``nbd`` is loaded." +msgstr "" + +#: ../nova-compute-install.rst:203 +msgid "" +"Ensure the module will be loaded on every boot by adding ``nbd`` in the ``/" +"etc/modules-load.d/nbd.conf`` file." +msgstr "" + +#: ../nova-compute-install.rst:209 +msgid "" +"Determine whether your compute node supports hardware acceleration for " +"virtual machines:" +msgstr "" + +#: ../nova-compute-install.rst:216 +msgid "" +"If this command returns a value of ``one or greater``, your compute node " +"supports hardware acceleration which typically requires no additional " +"configuration." +msgstr "" + +#: ../nova-compute-install.rst:220 +msgid "" +"If this command returns a value of ``zero``, your compute node does not " +"support hardware acceleration and you must configure ``libvirt`` to use QEMU " +"instead of KVM." +msgstr "" + +#: ../nova-compute-install.rst:226 +msgid "" +"Edit the ``[libvirt]`` section in the ``/etc/nova/nova.conf`` file as " +"follows:" +msgstr "" + +#: ../nova-compute-install.rst:237 +msgid "" +"Edit the ``[libvirt]`` section in the ``/etc/nova/nova-compute.conf`` file " +"as follows:" +msgstr "" + +#: ../nova-compute-install.rst:248 +msgid "" +"Start the Compute service including its dependencies and configure them to " +"start automatically when the system boots:" +msgstr "" + +#: ../nova-controller-install.rst:4 +msgid "" +"This section describes how to install and configure the Compute service, " +"code-named nova, on the controller node." +msgstr "" + +#: ../nova-controller-install.rst:10 +msgid "" +"Before you install and configure the Compute service, you must create a " +"database, service credentials, and API endpoints." +msgstr "" + +#: ../nova-controller-install.rst:22 +msgid "Create the ``nova`` database:" +msgstr "" + +#: ../nova-controller-install.rst:28 +msgid "Grant proper access to the ``nova`` database:" +msgstr "" + +#: ../nova-controller-install.rst:37 +msgid "Replace ``NOVA_DBPASS`` with a suitable password." +msgstr "" + +#: ../nova-controller-install.rst:50 +msgid "Create the ``nova`` user:" +msgstr "" + +#: ../nova-controller-install.rst:66 +msgid "Add the ``admin`` role to the ``nova`` user:" +msgstr "" + +#: ../nova-controller-install.rst:76 +msgid "Create the ``nova`` service entity:" +msgstr "" + +#: ../nova-controller-install.rst:92 +msgid "Create the Compute service API endpoints:" +msgstr "" + +#: ../nova-controller-install.rst:184 +msgid "Add a ``[database]`` section, and configure database access:" +msgstr "" + +#: ../nova-controller-install.rst:192 +msgid "" +"Replace ``NOVA_DBPASS`` with the password you chose for the Compute database." +msgstr "" + +#: ../nova-controller-install.rst:268 +msgid "" +"In the ``[vnc]`` section, configure the VNC proxy to use the management " +"interface IP address of the controller node:" +msgstr "" + +#: ../nova-controller-install.rst:317 +msgid "In the ``[DEFAULT]`` section, disable the EC2 API:" +msgstr "" + +#: ../nova-controller-install.rst:336 ../nova-controller-install.rst:344 +msgid "Populate the Compute database:" +msgstr "" + +#: ../nova-controller-install.rst:355 ../nova-controller-install.rst:371 +msgid "" +"Start the Compute services and configure them to start when the system boots:" +msgstr "" + +#: ../nova-verify.rst:4 +msgid "Verify operation of the Compute service." +msgstr "" + +#: ../nova-verify.rst:17 +msgid "" +"List service components to verify successful launch and registration of each " +"process:" +msgstr "" + +#: ../nova-verify.rst:35 +msgid "" +"This output should indicate four service components enabled on the " +"controller node and one service component enabled on the compute node." +msgstr "" + +#: ../nova-verify.rst:39 +msgid "" +"List API endpoints in the Identity service to verify connectivity with the " +"Identity service:" +msgstr "" + +#: ../nova-verify.rst:131 +msgid "Ignore any warnings in this output." +msgstr "" + +#: ../nova-verify.rst:133 +msgid "" +"List images in the Image service catalog to verify connectivity with the " +"Image service:" +msgstr "" + +#: ../nova.rst:3 +msgid "Add the Compute service" +msgstr "" + +#: ../overview.rst:0 +msgid "**OpenStack services**" +msgstr "" + +#: ../overview.rst:3 +msgid "Overview" +msgstr "" + +#: ../overview.rst:5 +msgid "" +"The :term:`OpenStack` project is an open source cloud computing platform " +"that supports all types of cloud environments. The project aims for simple " +"implementation, massive scalability, and a rich set of features. Cloud " +"computing experts from around the world contribute to the project." +msgstr "" + +#: ../overview.rst:10 +msgid "" +"OpenStack provides an :term:`Infrastructure-as-a-Service (IaaS)` " +"solution through a variety of complemental services. Each service offers an :" +"term:`application programming interface (API)` that facilitates this " +"integration." +msgstr "" + +#: ../overview.rst:15 +msgid "" +"This guide covers step-by-step deployment of the following major OpenStack " +"services using a functional example architecture suitable for new users of " +"OpenStack with sufficient Linux experience:" +msgstr "" + +#: ../overview.rst:23 +msgid "Service" +msgstr "" + +#: ../overview.rst:24 +msgid "Project name" msgstr "" #: ../overview.rst:26 msgid "`Dashboard `_" msgstr "" -#: ../overview.rst:72 -msgid "`Glance `_" -msgstr "" - -#: ../overview.rst:84 -msgid "`Heat `_" -msgstr "" - #: ../overview.rst:27 msgid "`Horizon `_" msgstr "" -#: ../overview.rst:66 +#: ../overview.rst:28 msgid "" -"`Identity service `_" +"Provides a web-based self-service portal to interact with underlying " +"OpenStack services, such as launching an instance, assigning IP addresses " +"and configuring access controls." msgstr "" -#: ../overview.rst:71 -msgid "" -"`Image service `_" +#: ../overview.rst:32 +msgid "`Compute `_" msgstr "" -#: ../overview.rst:67 -msgid "`Keystone `_" +#: ../overview.rst:33 +msgid "`Nova `_" +msgstr "" + +#: ../overview.rst:34 +msgid "" +"Manages the lifecycle of compute instances in an OpenStack environment. " +"Responsibilities include spawning, scheduling and decommissioning of virtual " +"machines on demand." msgstr "" #: ../overview.rst:38 @@ -6735,8 +6037,16 @@ msgstr "" msgid "`Neutron `_" msgstr "" -#: ../overview.rst:33 -msgid "`Nova `_" +#: ../overview.rst:40 +msgid "" +"Enables Network-Connectivity-as-a-Service for other OpenStack services, such " +"as OpenStack Compute. Provides an API for users to define networks and the " +"attachments into them. Has a pluggable architecture that supports many " +"popular networking vendors and technologies." +msgstr "" + +#: ../overview.rst:48 +msgid "**Storage**" msgstr "" #: ../overview.rst:49 @@ -6744,154 +6054,863 @@ msgid "" "`Object Storage `_" msgstr "" +#: ../overview.rst:50 +msgid "`Swift `_" +msgstr "" + +#: ../overview.rst:51 +msgid "" +"Stores and retrieves arbitrary unstructured data objects via a :term:" +"`RESTful`, HTTP based API. It is highly fault tolerant with its data " +"replication and scale-out architecture. Its implementation is not like a " +"file server with mountable directories. In this case, it writes objects and " +"files to multiple drives, ensuring the data is replicated across a server " +"cluster." +msgstr "" + +#: ../overview.rst:58 +msgid "`Block Storage `_" +msgstr "" + +#: ../overview.rst:59 +msgid "`Cinder `_" +msgstr "" + +#: ../overview.rst:60 +msgid "" +"Provides persistent block storage to running instances. Its pluggable driver " +"architecture facilitates the creation and management of block storage " +"devices." +msgstr "" + +#: ../overview.rst:65 +msgid "**Shared services**" +msgstr "" + +#: ../overview.rst:66 +msgid "" +"`Identity service `_" +msgstr "" + +#: ../overview.rst:67 +msgid "`Keystone `_" +msgstr "" + +#: ../overview.rst:68 +msgid "" +"Provides an authentication and authorization service for other OpenStack " +"services. Provides a catalog of endpoints for all OpenStack services." +msgstr "" + +#: ../overview.rst:71 +msgid "" +"`Image service `_" +msgstr "" + +#: ../overview.rst:72 +msgid "`Glance `_" +msgstr "" + +#: ../overview.rst:73 +msgid "" +"Stores and retrieves virtual machine disk images. OpenStack Compute makes " +"use of this during instance provisioning." +msgstr "" + +#: ../overview.rst:76 +msgid "" +"`Telemetry `_" +msgstr "" + +#: ../overview.rst:77 +msgid "`Ceilometer `_" +msgstr "" + +#: ../overview.rst:78 +msgid "" +"Monitors and meters the OpenStack cloud for billing, benchmarking, " +"scalability, and statistical purposes." +msgstr "" + +#: ../overview.rst:82 +msgid "**Higher-level services**" +msgstr "" + #: ../overview.rst:83 msgid "" "`Orchestration `_" msgstr "" -#: ../overview.rst:50 -msgid "`Swift `_" +#: ../overview.rst:84 +msgid "`Heat `_" msgstr "" -#: ../overview.rst:76 +#: ../overview.rst:85 msgid "" -"`Telemetry `_" +"Orchestrates multiple composite cloud applications by using either the " +"native :term:`HOT ` template format or " +"the AWS CloudFormation template format, through both an OpenStack-native " +"REST API and a CloudFormation-compatible Query API." msgstr "" -#: ../environment.rst:111 -msgid "``ADMIN_PASS``" -msgstr "" - -#: ../environment.rst:113 -msgid "``CEILOMETER_DBPASS``" -msgstr "" - -#: ../environment.rst:115 -msgid "``CEILOMETER_PASS``" -msgstr "" - -#: ../environment.rst:117 -msgid "``CINDER_DBPASS``" -msgstr "" - -#: ../environment.rst:119 -msgid "``CINDER_PASS``" -msgstr "" - -#: ../environment.rst:121 -msgid "``DASH_DBPASS``" -msgstr "" - -#: ../environment.rst:123 -msgid "``DEMO_PASS``" -msgstr "" - -#: ../environment.rst:125 -msgid "``GLANCE_DBPASS``" -msgstr "" - -#: ../environment.rst:127 -msgid "``GLANCE_PASS``" -msgstr "" - -#: ../environment.rst:129 -msgid "``HEAT_DBPASS``" -msgstr "" - -#: ../environment.rst:131 -msgid "``HEAT_DOMAIN_PASS``" -msgstr "" - -#: ../environment.rst:133 -msgid "``HEAT_PASS``" -msgstr "" - -#: ../environment.rst:135 -msgid "``KEYSTONE_DBPASS``" -msgstr "" - -#: ../environment.rst:137 -msgid "``NEUTRON_DBPASS``" -msgstr "" - -#: ../environment.rst:139 -msgid "``NEUTRON_PASS``" -msgstr "" - -#: ../environment.rst:141 -msgid "``NOVA_DBPASS``" -msgstr "" - -#: ../environment.rst:143 -msgid "``NOVA_PASS``" -msgstr "" - -#: ../environment.rst:145 -msgid "``RABBIT_PASS``" -msgstr "" - -#: ../environment.rst:147 -msgid "``SWIFT_PASS``" -msgstr "" - -#: ../launch-instance-networks-public.rst:79 -msgid "``linuxbridge_agent.ini``:" -msgstr "" - -# #-#-#-#-# launch-instance-networks-private.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# launch-instance-networks-public.pot (Installation Guide 0.1) #-#-#-#-# -#: ../launch-instance-networks-private.rst:72 -#: ../launch-instance-networks-public.rst:72 -msgid "``ml2_conf.ini``:" -msgstr "" - -#: ../debconf/debconf-dbconfig-common.rst:134 -msgid "and run the helper script:" -msgstr "" - -#: ../app_reserved_uids.rst:22 -msgid "ceilometer" -msgstr "" - -#: ../app_reserved_uids.rst:31 -msgid "cinder" -msgstr "" - -#: ../debconf/debconf-concepts.rst:5 -msgid "debconf concepts" -msgstr "" - -#: ../app_reserved_uids.rst:40 -msgid "glance" -msgstr "" - -#: ../app_reserved_uids.rst:49 -msgid "heat" -msgstr "" - -#: ../app_reserved_uids.rst:58 -msgid "keystone" -msgstr "" - -#: ../app_reserved_uids.rst:67 -msgid "neutron" -msgstr "" - -#: ../app_reserved_uids.rst:76 -msgid "nova" -msgstr "" - -#: ../keystone-install.rst:195 +#: ../overview.rst:93 msgid "" -"python-keystoneclient will automatically be installed as it is a dependency " -"of the keystone package." +"After becoming familiar with basic installation, configuration, operation, " +"and troubleshooting of these OpenStack services, you should consider the " +"following steps toward deployment using a production architecture:" msgstr "" -#: ../app_reserved_uids.rst:85 -msgid "swift" +#: ../overview.rst:97 +msgid "" +"Determine and implement the necessary core and optional services to meet " +"performance and redundancy requirements." msgstr "" -#: ../app_reserved_uids.rst:94 -msgid "trove" +#: ../overview.rst:100 +msgid "" +"Increase security using methods such as firewalls, encryption, and service " +"policies." +msgstr "" + +#: ../overview.rst:103 +msgid "" +"Implement a deployment tool such as Ansible, Chef, Puppet, or Salt to " +"automate deployment and management of the production environment." +msgstr "" + +#: ../overview.rst:109 +msgid "Example architecture" +msgstr "" + +#: ../overview.rst:111 +msgid "" +"The example architecture requires at least two nodes (hosts) to launch a " +"basic :term:`virtual machine ` or instance. Optional " +"services such as Block Storage and Object Storage require additional nodes." +msgstr "" + +#: ../overview.rst:115 +msgid "" +"This example architecture differs from a minimal production architecture as " +"follows:" +msgstr "" + +#: ../overview.rst:118 +msgid "" +"Networking agents reside on the controller node instead of one or more " +"dedicated network nodes." +msgstr "" + +#: ../overview.rst:121 +msgid "" +"Overlay (tunnel) traffic for private networks traverses the management " +"network instead of a dedicated network." +msgstr "" + +#: ../overview.rst:124 +msgid "" +"For more information on production architectures, see the `Architecture " +"Design Guide `__, " +"`Operations Guide `__, and `Networking Guide " +"`__." +msgstr "" + +#: ../overview.rst:134 +msgid "**Hardware requirements**" +msgstr "" + +#: ../overview.rst:137 +msgid "Controller" +msgstr "" + +#: ../overview.rst:139 +msgid "" +"The controller node runs the Identity service, Image service, management " +"portions of Compute, management portion of Networking, various Networking " +"agents, and the dashboard. It also includes supporting services such as an " +"SQL database, :term:`message queue`, and :term:`NTP`." +msgstr "" + +#: ../overview.rst:144 +msgid "" +"Optionally, the controller node runs portions of Block Storage, Object " +"Storage, Orchestration, and Telemetry services." +msgstr "" + +#: ../overview.rst:147 +msgid "The controller node requires a minimum of two network interfaces." +msgstr "" + +#: ../overview.rst:150 +msgid "Compute" +msgstr "" + +#: ../overview.rst:152 +msgid "" +"The compute node runs the :term:`hypervisor` portion of Compute that " +"operates instances. By default, Compute uses the :term:`KVM ` hypervisor. The compute node also runs a Networking service agent " +"that connects instances to virtual networks and provides firewalling " +"services to instances via :term:`security groups `." +msgstr "" + +#: ../overview.rst:159 +msgid "" +"You can deploy more than one compute node. Each node requires a minimum of " +"two network interfaces." +msgstr "" + +#: ../overview.rst:165 +msgid "" +"The optional Block Storage node contains the disks that the Block Storage " +"service provisions for instances." +msgstr "" + +#: ../overview.rst:168 ../overview.rst:182 +msgid "" +"For simplicity, service traffic between compute nodes and this node uses the " +"management network. Production environments should implement a separate " +"storage network to increase performance and security." +msgstr "" + +#: ../overview.rst:172 +msgid "" +"You can deploy more than one block storage node. Each node requires a " +"minimum of one network interface." +msgstr "" + +#: ../overview.rst:176 +msgid "Object Storage" +msgstr "" + +#: ../overview.rst:178 +msgid "" +"The optional Object Storage node contain the disks that the Object Storage " +"service uses for storing accounts, containers, and objects." +msgstr "" + +#: ../overview.rst:186 +msgid "" +"This service requires two nodes. Each node requires a minimum of one network " +"interface. You can deploy more than two object storage nodes." +msgstr "" + +#: ../overview.rst:190 +msgid "Networking" +msgstr "" + +#: ../overview.rst:192 +msgid "Choose one of the following virtual networking options." +msgstr "" + +#: ../overview.rst:199 +msgid "" +"The provider networks option deploys the OpenStack Networking service in the " +"simplest way possible with primarily layer-2 (bridging/switching) services " +"and VLAN segmentation of networks. Essentially, it bridges virtual networks " +"to physical networks and relies on physical network infrastructure for " +"layer-3 (routing) services. Additionally, a :term:`DHCP` service provides IP " +"address information to instances." +msgstr "" + +#: ../overview.rst:208 +msgid "" +"This option lacks support for self-service private networks, layer-3 " +"(routing) services, and advanced services such as :term:`LBaaS` and :term:" +"`FWaaS`. Consider the self-service networks option if you desire these " +"features." +msgstr "" + +#: ../overview.rst:223 +msgid "" +"The self-service networks option augments the provider networks option with " +"layer-3 (routing) services that enable :term:`self-service` networks using " +"overlay segmentation methods such as :term:`VXLAN`. Essentially, it routes " +"virtual networks to physical networks using :term:`NAT`. Additionally, this " +"option provides the foundation for advanced services such as LBaaS and FWaaS." +msgstr "" + +# #-#-#-#-# glance-install.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# keystone-install.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# neutron-compute-install.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# neutron-controller-install-option1.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# nova-compute-install.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# nova-controller-install.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# swift-controller-node.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# swift-finalize-installation.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# swift-storage-node.pot (Installation Guide 0.1) #-#-#-#-# +#: ../shared/note_configuration_vary_by_distribution.rst:3 +msgid "" +"Default configuration files vary by distribution. You might need to add " +"these sections and options rather than modifying existing sections and " +"options. Also, an ellipsis (``...``) in the configuration snippets indicates " +"potential default configuration options that you should retain." +msgstr "" + +#: ../swift-controller-node-include.txt:4 +msgid "" +"In the ``[DEFAULT]`` section, configure the bind port, user, and " +"configuration directory:" +msgstr "" + +# #-#-#-#-# swift-controller-node.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# swift-storage-node.pot (Installation Guide 0.1) #-#-#-#-# +#: ../swift-controller-node-include.txt:16 +#: ../swift-storage-node-include1.txt:21 ../swift-storage-node-include2.txt:21 +#: ../swift-storage-node-include3.txt:21 +msgid "In the ``[pipeline:main]`` section, enable the appropriate modules:" +msgstr "" + +# #-#-#-#-# swift-controller-node.pot (Installation Guide 0.1) #-#-#-#-# +# #-#-#-#-# swift-storage-node.pot (Installation Guide 0.1) #-#-#-#-# +#: ../swift-controller-node-include.txt:28 +#: ../swift-storage-node-include1.txt:31 ../swift-storage-node-include2.txt:31 +#: ../swift-storage-node-include3.txt:31 +msgid "" +"For more information on other modules that enable additional features, see " +"the `Deployment Guide `__." +msgstr "" + +#: ../swift-controller-node-include.txt:31 +msgid "" +"In the ``[app:proxy-server]`` section, enable automatic account creation:" +msgstr "" + +#: ../swift-controller-node-include.txt:39 +msgid "In the ``[filter:keystoneauth]`` section, configure the operator roles:" +msgstr "" + +#: ../swift-controller-node-include.txt:48 +msgid "" +"In the ``[filter:authtoken]`` section, configure Identity service access:" +msgstr "" + +#: ../swift-controller-node-include.txt:66 +msgid "" +"Replace ``SWIFT_PASS`` with the password you chose for the ``swift`` user in " +"the Identity service." +msgstr "" + +#: ../swift-controller-node-include.txt:71 +msgid "" +"Comment out or remove any other options in the ``[filter:authtoken]`` " +"section." +msgstr "" + +#: ../swift-controller-node-include.txt:74 +msgid "" +"In the ``[filter:cache]`` section, configure the ``memcached`` location:" +msgstr "" + +#: ../swift-controller-node.rst:3 +msgid "Install and configure the controller node" +msgstr "" + +#: ../swift-controller-node.rst:5 +msgid "" +"This section describes how to install and configure the proxy service that " +"handles requests for the account, container, and object services operating " +"on the storage nodes. For simplicity, this guide installs and configures the " +"proxy service on the controller node. However, you can run the proxy service " +"on any node with network connectivity to the storage nodes. Additionally, " +"you can install and configure the proxy service on multiple nodes to " +"increase performance and redundancy. For more information, see the " +"`Deployment Guide `__." +msgstr "" + +#: ../swift-controller-node.rst:17 +msgid "" +"The proxy service relies on an authentication and authorization mechanism " +"such as the Identity service. However, unlike other services, it also offers " +"an internal mechanism that allows it to operate without any other OpenStack " +"services. However, for simplicity, this guide references the Identity " +"service in :doc:`keystone`. Before you configure the Object Storage service, " +"you must create service credentials and an API endpoint." +msgstr "" + +#: ../swift-controller-node.rst:26 +msgid "" +"The Object Storage service does not use an SQL database on the controller " +"node. Instead, it uses distributed SQLite databases on each storage node." +msgstr "" + +#: ../swift-controller-node.rst:35 +msgid "To create the Identity service credentials, complete these steps:" +msgstr "" + +#: ../swift-controller-node.rst:37 +msgid "Create the ``swift`` user:" +msgstr "" + +#: ../swift-controller-node.rst:54 +msgid "Add the ``admin`` role to the ``swift`` user:" +msgstr "" + +#: ../swift-controller-node.rst:66 +msgid "Create the ``swift`` service entity:" +msgstr "" + +#: ../swift-controller-node.rst:82 +msgid "Create the Object Storage service API endpoint:" +msgstr "" + +#: ../swift-controller-node.rst:106 +msgid "To install and configure the controller node components" +msgstr "" + +#: ../swift-controller-node.rst:114 +msgid "Complete OpenStack environments already include some of these packages." +msgstr "" + +#: ../swift-controller-node.rst:140 +msgid "Create the :file:`/etc/swift` directory." +msgstr "" + +#: ../swift-controller-node.rst:142 ../swift-controller-node.rst:153 +msgid "" +"Obtain the proxy service configuration file from the Object Storage source " +"repository:" +msgstr "" + +#: ../swift-finalize-installation.rst:5 +msgid "**Configure hashes and default storage policy**" +msgstr "" + +#: ../swift-finalize-installation.rst:11 +msgid "" +"Obtain the :file:`/etc/swift/swift.conf` file from the Object Storage source " +"repository:" +msgstr "" + +#: ../swift-finalize-installation.rst:19 ../swift-finalize-installation.rst:55 +msgid "" +"Edit the :file:`/etc/swift/swift.conf` file and complete the following " +"actions:" +msgstr "" + +#: ../swift-finalize-installation.rst:22 ../swift-finalize-installation.rst:58 +msgid "" +"In the ``[swift-hash]`` section, configure the hash path prefix and suffix " +"for your environment." +msgstr "" + +#: ../swift-finalize-installation.rst:33 ../swift-finalize-installation.rst:69 +msgid "Replace HASH_PATH_PREFIX and HASH_PATH_SUFFIX with unique values." +msgstr "" + +#: ../swift-finalize-installation.rst:37 ../swift-finalize-installation.rst:73 +msgid "Keep these values secret and do not change or lose them." +msgstr "" + +#: ../swift-finalize-installation.rst:39 ../swift-finalize-installation.rst:75 +msgid "" +"In the ``[storage-policy:0]`` section, configure the default storage policy:" +msgstr "" + +#: ../swift-finalize-installation.rst:50 ../swift-finalize-installation.rst:86 +msgid "" +"Copy the :file:`swift.conf` file to the :file:`/etc/swift` directory on each " +"storage node and any additional nodes running the proxy service." +msgstr "" + +#: ../swift-finalize-installation.rst:91 +#: ../swift-finalize-installation.rst:119 +#: ../swift-finalize-installation.rst:154 +msgid "On all nodes, ensure proper ownership of the configuration directory:" +msgstr "" + +#: ../swift-finalize-installation.rst:97 +msgid "" +"On the controller node and any other nodes running the proxy service, " +"restart the Object Storage proxy service including its dependencies:" +msgstr "" + +#: ../swift-finalize-installation.rst:105 +msgid "On the storage nodes, start the Object Storage services:" +msgstr "" + +#: ../swift-finalize-installation.rst:113 +msgid "" +"The storage node runs many Object Storage services and the :command:`swift-" +"init` command makes them easier to manage. You can ignore errors from " +"services not running on the storage node." +msgstr "" + +#: ../swift-finalize-installation.rst:125 +#: ../swift-finalize-installation.rst:160 +msgid "" +"On the controller node and any other nodes running the proxy service, start " +"the Object Storage proxy service including its dependencies and configure " +"them to start when the system boots:" +msgstr "" + +#: ../swift-finalize-installation.rst:134 +#: ../swift-finalize-installation.rst:169 +msgid "" +"On the storage nodes, start the Object Storage services and configure them " +"to start when the system boots:" +msgstr "" + +#: ../swift-initial-rings.rst:3 +msgid "Create initial rings" +msgstr "" + +#: ../swift-initial-rings.rst:5 +msgid "" +"Before starting the Object Storage services, you must create the initial " +"account, container, and object rings. The ring builder creates configuration " +"files that each node uses to determine and deploy the storage architecture. " +"For simplicity, this guide uses one region and zone with 2^10 (1024) maximum " +"partitions, 3 replicas of each object, and 1 hour minimum time between " +"moving a partition more than once. For Object Storage, a partition indicates " +"a directory on a storage device rather than a conventional partition table. " +"For more information, see the `Deployment Guide `__." +msgstr "" + +#: ../swift-initial-rings.rst:16 +msgid "Account ring" +msgstr "" + +#: ../swift-initial-rings.rst:18 +msgid "" +"The account server uses the account ring to maintain lists of containers." +msgstr "" + +#: ../swift-initial-rings.rst:20 ../swift-initial-rings.rst:101 +#: ../swift-initial-rings.rst:180 +msgid "To create the ring perform the following steps on the controller node." +msgstr "" + +#: ../swift-initial-rings.rst:22 ../swift-initial-rings.rst:103 +#: ../swift-initial-rings.rst:182 +msgid "Change to the :file:`/etc/swift` directory." +msgstr "" + +#: ../swift-initial-rings.rst:24 +msgid "Create the base :file:`account.builder` file:" +msgstr "" + +#: ../swift-initial-rings.rst:34 ../swift-initial-rings.rst:115 +#: ../swift-initial-rings.rst:194 +msgid "Add each storage node to the ring:" +msgstr "" + +#: ../swift-initial-rings.rst:42 ../swift-initial-rings.rst:123 +#: ../swift-initial-rings.rst:202 +msgid "" +"Replace ``STORAGE_NODE_MANAGEMENT_INTERFACE_IP_ADDRESS`` with the IP address " +"of the management network on the storage node. Replace ``DEVICE_NAME`` with " +"a storage device name on the same storage node. For example, using the first " +"storage node in :doc:`swift-storage-node` with the :file:`/dev/sdb1` storage " +"device and weight of 100:" +msgstr "" + +#: ../swift-initial-rings.rst:53 ../swift-initial-rings.rst:134 +#: ../swift-initial-rings.rst:212 +msgid "" +"Repeat this command for each storage device on each storage node. In the " +"example architecture, use the command in four variations:" +msgstr "" + +#: ../swift-initial-rings.rst:71 ../swift-initial-rings.rst:152 +#: ../swift-initial-rings.rst:230 +msgid "Verify the ring contents:" +msgstr "" + +#: ../swift-initial-rings.rst:86 ../swift-initial-rings.rst:167 +#: ../swift-initial-rings.rst:245 +msgid "Rebalance the ring:" +msgstr "" + +#: ../swift-initial-rings.rst:96 +msgid "Container ring" +msgstr "" + +#: ../swift-initial-rings.rst:98 +msgid "" +"The container server uses the container ring to maintain lists of objects. " +"However, it does not track object locations." +msgstr "" + +#: ../swift-initial-rings.rst:105 +msgid "Create the base :file:`container.builder` file:" +msgstr "" + +#: ../swift-initial-rings.rst:175 +msgid "Object ring" +msgstr "" + +#: ../swift-initial-rings.rst:177 +msgid "" +"The object server uses the object ring to maintain lists of object locations " +"on local devices." +msgstr "" + +#: ../swift-initial-rings.rst:184 +msgid "Create the base :file:`object.builder` file:" +msgstr "" + +#: ../swift-initial-rings.rst:253 +msgid "Distribute ring configuration files" +msgstr "" + +#: ../swift-initial-rings.rst:255 +msgid "" +"Copy the :file:`account.ring.gz`, :file:`container.ring.gz`, and :file:" +"`object.ring.gz` files to the :file:`/etc/swift` directory on each storage " +"node and any additional nodes running the proxy service." +msgstr "" + +#: ../swift-next-steps.rst:5 +msgid "" +"Your OpenStack environment now includes Object Storage. You can :ref:`launch-" +"instance` or add more services to your environment." +msgstr "" + +#: ../swift-storage-node-include1.txt:1 +msgid "" +"Edit the :file:`/etc/swift/account-server.conf` file and complete the " +"following actions:" +msgstr "" + +#: ../swift-storage-node-include1.txt:4 ../swift-storage-node-include2.txt:4 +#: ../swift-storage-node-include3.txt:4 +msgid "" +"In the ``[DEFAULT]`` section, configure the bind IP address, bind port, " +"user, configuration directory, and mount point directory:" +msgstr "" + +#: ../swift-storage-node-include1.txt:18 ../swift-storage-node-include2.txt:18 +#: ../swift-storage-node.rst:145 +msgid "" +"Replace ``MANAGEMENT_INTERFACE_IP_ADDRESS`` with the IP address of the " +"management network on the storage node." +msgstr "" + +#: ../swift-storage-node-include1.txt:34 ../swift-storage-node-include2.txt:34 +msgid "" +"In the ``[filter:recon]`` section, configure the recon (meters) cache " +"directory:" +msgstr "" + +#: ../swift-storage-node-include2.txt:1 +msgid "" +"Edit the :file:`/etc/swift/container-server.conf` file and complete the " +"following actions:" +msgstr "" + +#: ../swift-storage-node-include3.txt:1 +msgid "" +"Edit the :file:`/etc/swift/object-server.conf` file and complete the " +"following actions:" +msgstr "" + +#: ../swift-storage-node-include3.txt:18 +msgid "" +"Replace MANAGEMENT_INTERFACE_IP_ADDRESS with the IP address of the " +"management network on the storage node." +msgstr "" + +#: ../swift-storage-node-include3.txt:34 +msgid "" +"In the ``[filter:recon]`` section, configure the recon (meters) cache and " +"lock directories:" +msgstr "" + +#: ../swift-storage-node.rst:3 +msgid "Install and configure the storage nodes" +msgstr "" + +#: ../swift-storage-node.rst:5 +msgid "" +"This section describes how to install and configure storage nodes that " +"operate the account, container, and object services. For simplicity, this " +"configuration references two storage nodes, each containing two empty local " +"block storage devices. Each of the devices, :file:`/dev/sdb` and :file:`/dev/" +"sdc`, must contain a suitable partition table with one partition occupying " +"the entire device. Although the Object Storage service supports any file " +"system with :term:`extended attributes (xattr)`, testing and benchmarking " +"indicate the best performance and reliability on :term:`XFS`. For more " +"information on horizontally scaling your environment, see the `Deployment " +"Guide `_." +msgstr "" + +#: ../swift-storage-node.rst:20 +msgid "" +"You must configure each storage node before you install and configure the " +"Object Storage service on it. Similar to the controller node, each storage " +"node contains one network interface on the :term:`management network`. " +"Optionally, each storage node can contain a second network interface on a " +"separate network for replication. For more information, see :ref:" +"`environment`." +msgstr "" + +#: ../swift-storage-node.rst:27 +msgid "Configure unique items on the first storage node:" +msgstr "" + +#: ../swift-storage-node.rst:31 +msgid "IP address: ``10.0.0.51``" +msgstr "" + +#: ../swift-storage-node.rst:32 ../swift-storage-node.rst:42 +msgid "Network mask: ``255.255.255.0`` (or ``/24``)" +msgstr "" + +#: ../swift-storage-node.rst:33 ../swift-storage-node.rst:43 +msgid "Default gateway: ``10.0.0.1``" +msgstr "" + +#: ../swift-storage-node.rst:35 +msgid "Set the hostname of the node to ``object1``." +msgstr "" + +#: ../swift-storage-node.rst:37 +msgid "Configure unique items on the second storage node:" +msgstr "" + +#: ../swift-storage-node.rst:41 +msgid "IP address: ``10.0.0.52``" +msgstr "" + +#: ../swift-storage-node.rst:45 +msgid "Set the hostname of the node to ``object2``." +msgstr "" + +#: ../swift-storage-node.rst:47 +msgid "Configure shared items on both storage nodes:" +msgstr "" + +#: ../swift-storage-node.rst:49 +msgid "" +"Copy the contents of the :file:`/etc/hosts` file from the controller node " +"and add the following to it:" +msgstr "" + +#: ../swift-storage-node.rst:67 +msgid "Install the supporting utility packages:" +msgstr "" + +#: ../swift-storage-node.rst:87 +msgid "Format the :file:`/dev/sdb1` and :file:`/dev/sdc1` partitions as XFS:" +msgstr "" + +#: ../swift-storage-node.rst:94 +msgid "Create the mount point directory structure:" +msgstr "" + +#: ../swift-storage-node.rst:101 +msgid "Edit the :file:`/etc/fstab` file and add the following to it:" +msgstr "" + +#: ../swift-storage-node.rst:109 +msgid "Mount the devices:" +msgstr "" + +#: ../swift-storage-node.rst:116 +msgid "Edit the :file:`/etc/rsyncd.conf` file and add the following to it:" +msgstr "" + +#: ../swift-storage-node.rst:150 +msgid "" +"The ``rsync`` service requires no authentication, so consider running it on " +"a private network." +msgstr "" + +#: ../swift-storage-node.rst:155 +msgid "" +"Edit the :file:`/etc/default/rsync` file and enable the ``rsync`` service:" +msgstr "" + +#: ../swift-storage-node.rst:163 +msgid "Start the ``rsync`` service:" +msgstr "" + +#: ../swift-storage-node.rst:171 +msgid "" +"Start the ``rsyncd`` service and configure it to start when the system boots:" +msgstr "" + +#: ../swift-storage-node.rst:180 +msgid "Install and configure storage node components" +msgstr "" + +#: ../swift-storage-node.rst:186 +msgid "Perform these steps on each storage node." +msgstr "" + +#: ../swift-storage-node.rst:212 +msgid "" +"Obtain the accounting, container, object, container-reconciler, and object-" +"expirer service configuration files from the Object Storage source " +"repository:" +msgstr "" + +#: ../swift-storage-node.rst:232 ../swift-storage-node.rst:250 +msgid "Ensure proper ownership of the mount point directory structure:" +msgstr "" + +#: ../swift-storage-node.rst:238 ../swift-storage-node.rst:256 +msgid "Create the :file:`recon` directory and ensure proper ownership of it:" +msgstr "" + +#: ../swift-verify.rst:4 +msgid "" +"This section describes how to verify operation of the Object Storage service." +msgstr "" + +#: ../swift-verify.rst:8 +msgid "" +"The ``swift`` client requires the ``-V 3`` parameter to use the Identity " +"version 3 API." +msgstr "" + +#: ../swift-verify.rst:14 +msgid "Source the ``demo`` credentials:" +msgstr "" + +#: ../swift-verify.rst:20 +msgid "Show the service status:" +msgstr "" + +#: ../swift-verify.rst:34 +msgid "Upload a test file:" +msgstr "" + +#: ../swift-verify.rst:41 +msgid "" +"Replace ``FILE`` with the name of a local file to upload to the ``demo-" +"container1`` container." +msgstr "" + +#: ../swift-verify.rst:44 +msgid "List containers:" +msgstr "" + +#: ../swift-verify.rst:51 +msgid "Download a test file:" +msgstr "" + +#: ../swift-verify.rst:58 +msgid "" +"Replace ``FILE`` with the name of the file uploaded to the ``demo-" +"container1`` container." +msgstr "" + +#: ../swift.rst:5 +msgid "Add Object Storage" +msgstr "" + +#: ../swift.rst:7 +msgid "" +"The OpenStack Object Storage services (swift) work together to provide " +"object storage and retrieval through a :term:`REST API `. Your " +"environment must at least include the Identity service (keystone) prior to " +"deploying Object Storage." msgstr "" diff --git a/doc/install-guide/source/locale/ja/LC_MESSAGES/install-guide.po b/doc/install-guide/source/locale/ja/LC_MESSAGES/install-guide.po index 5972a9843a..c33e7e63fc 100644 --- a/doc/install-guide/source/locale/ja/LC_MESSAGES/install-guide.po +++ b/doc/install-guide/source/locale/ja/LC_MESSAGES/install-guide.po @@ -14,11 +14,11 @@ msgid "" msgstr "" "Project-Id-Version: Installation Guide 0.1\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2015-10-05 04:54+0000\n" +"POT-Creation-Date: 2015-10-08 06:01+0000\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" -"PO-Revision-Date: 2015-10-05 03:26+0000\n" +"PO-Revision-Date: 2015-10-07 07:00+0000\n" "Last-Translator: KATO Tomoyuki \n" "Language-Team: Japanese (http://www.transifex.com/openstack/openstack-" "manuals-i18n/language/ja/)\n" @@ -457,19 +457,6 @@ msgstr "" "代わりに、``ssh-keygen`` コマンドをスキップして、既存の公開鍵を使用することも" "できます。" -msgid "" -"Although most environments include Identity, Image service, Compute, at " -"least one networking service, and the dashboard, the Object Storage service " -"can operate independently. If your use case only involves Object Storage, " -"you can skip to :ref:`swift` after configuring the appropriate nodes for it. " -"However, the dashboard requires at least the Image service and Compute." -msgstr "" -"ほとんどの環境には、Identity、Image service、Compute、少なくとも 1 つのネット" -"ワークサービス、ダッシュボードがありますが、Object Storage は他のほとんどの" -"サービスと独立して動作できます。Object Storage のみを使用するユースケースの場" -"合、適切なノードを設定した後に :ref:`swift` まで進めます。しかしながらダッ" -"シュボードは、少なくとも Image service と Compute を必要とします。" - msgid "" "Another way to disable the ``debconf`` package is to prefix the :command:" "`apt` command with ``DEBIAN_FRONTEND=noninteractive``, as follows:" @@ -587,9 +574,6 @@ msgstr "" "す。詳細は `Deployment Guide `__ を参照してください。" -msgid "Before you begin" -msgstr "始める前に" - msgid "" "Before you configure the OpenStack Identity service, you must create a " "database and an administration token." @@ -851,9 +835,6 @@ msgstr "コンピュートノード" msgid "Configure Compute to use Networking" msgstr "Networking を使用するための Compute の設定" -msgid "Configure Network Time Protocol (NTP)" -msgstr "Network Time Protocol (NTP) の設定" - msgid "Configure OpenStack with debconf" msgstr "debconf を用いた OpenStack の設定" @@ -867,8 +848,8 @@ msgstr "" msgid "Configure name resolution" msgstr "名前解決の設定" -msgid "Configure networking" -msgstr "ネットワークの設定" +msgid "Configure network interfaces" +msgstr "ネットワークインターフェースの設定" msgid "Configure networking options" msgstr "ネットワークのオプションの設定" @@ -903,11 +884,9 @@ msgstr "Linux ブリッジエージェントの設定" msgid "Configure the Modular Layer 2 (ML2) plug-in" msgstr "ML2 プラグインの設定" -msgid "Configure the NTP service" -msgstr "NTP サービスの設定" - -msgid "Configure the Networking server component" -msgstr "Networking のサーバーコンポーネントの設定" +msgid "Configure the Networking components on a *compute* node." +msgstr "" +"*コンピュート* ノードにおいて、Networking のコンポーネントを設定します。" msgid "Configure the Object Storage service" msgstr "Object Storage の設定" @@ -925,6 +904,9 @@ msgstr "``memcached`` セッションストレージサービスを設定しま msgid "Configure the authentication token:" msgstr "認証トークンを設定します。" +msgid "Configure the common component" +msgstr "共通コンポーネントの設定" + msgid "" "Configure the dashboard to use OpenStack services on the ``controller`` " "node::" @@ -966,6 +948,9 @@ msgstr "" "ネットワークノードとコンピュートノードがコントローラーノードを参照するよう設" "定します。" +msgid "Configure the server component" +msgstr "サーバーコンポーネントの設定" + msgid "Configure the web server::" msgstr "Web サーバーを設定します::" @@ -994,12 +979,6 @@ msgstr "" "レスを表すでしょう。*S* 列の内容は、*\\** のサーバーが現在 NTP サービスと同期" "されていることを表します。" -msgid "" -"Contents in the *remote* column should indicate the hostname of the " -"controller node." -msgstr "" -"*remote* 列の内容は、コントローラーノードのホスト名を意味するでしょう。" - msgid "Controller" msgstr "コントローラー" @@ -1110,11 +1089,11 @@ msgstr "" "の作業を実行します。" msgid "" -"Create and edit the :file:`/etc/neutron/dnsmasq-neutron.conf` file to enable " -"the DHCP MTU option (26) and configure it to 1450 bytes:" +"Create and edit the ``/etc/neutron/dnsmasq-neutron.conf`` file to enable the " +"DHCP MTU option (26) and configure it to 1450 bytes:" msgstr "" -":file:`/etc/neutron/dnsmasq-neutron.conf` ファイルを作成して編集して、DHCP " -"MTU オプション (26) を有効化し、それを 1450 バイトに設定します。" +"``/etc/neutron/dnsmasq-neutron.conf`` ファイルを作成して編集して、DHCP MTU オ" +"プション (26) を有効化し、それを 1450 バイトに設定します。" msgid "" "Create client environment scripts for the ``admin`` and ``demo`` projects " @@ -1504,36 +1483,6 @@ msgstr "" ":file:`/etc/ceilometer/ceilometer.conf` ファイルを編集し、以下の作業を完了し" "ます。" -msgid "" -"Edit the :file:`/etc/chrony.conf` and comment out or remove all but one " -"``server`` key. Change it to reference the controller node:" -msgstr "" -":file:`/etc/chrony.conf` ファイルを編集して、1 つの ``server`` キー以外のすべ" -"てをコメントアウトまたは削除します。このキーはコントローラーノードを参照する" -"よう変更します。" - -msgid "" -"Edit the :file:`/etc/chrony.conf` file and add, change, or remove the " -"following keys as necessary for your environment:" -msgstr "" -":file:`/etc/chrony.conf` ファイルを編集して、お使いの環境の必要に応じて、以下" -"のキーを追加、変更、削除します。" - -msgid "" -"Edit the :file:`/etc/chrony/chrony.conf` and comment out or remove all but " -"one ``server`` key. Change it to reference the controller node:" -msgstr "" -":file:`/etc/chrony/chrony.conf` ファイルを編集して、1 つの ``server`` キー以" -"外のすべてをコメントアウトまたは削除します。このキーはコントローラーノードを" -"参照するよう変更します。" - -msgid "" -"Edit the :file:`/etc/chrony/chrony.conf` file and add, change, or remove the " -"following keys as necessary for your environment:" -msgstr "" -":file:`/etc/chrony/chrony.conf` ファイルを編集して、お使いの環境の必要に応じ" -"て、以下のキーを追加、変更、削除します。" - # #-#-#-#-# ceilometer-cinder.pot (Installation Guide 0.1) #-#-#-#-# # #-#-#-#-# cinder-controller-node.pot (Installation Guide 0.1) #-#-#-#-# # #-#-#-#-# cinder-storage-node.pot (Installation Guide 0.1) #-#-#-#-# @@ -1596,13 +1545,6 @@ msgstr "" ":file:`/etc/openstack-dashboard/local_settings.py` ファイルを編集し、以下の作" "業を完了します。" -msgid "" -"Edit the :file:`/etc/openstack-dashboard/local_settings` file and complete " -"the following actions:" -msgstr "" -":file:`/etc/openstack-dashboard/local_settings` ファイルを編集し、以下の作業" -"を完了します。" - msgid "Edit the :file:`/etc/rsyncd.conf` file and add the following to it:" msgstr ":file:`/etc/rsyncd.conf` ファイルを編集し、以下の内容を追加します。" @@ -1660,13 +1602,6 @@ msgstr "" ":file:`/etc/sysconfig/network/ifcfg-INTERFACE_NAME` ファイルを編集し、以下の" "内容を含めます。" -# #-#-#-#-# neutron-compute-node.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# neutron-network-node.pot (Installation Guide 0.1) #-#-#-#-# -msgid "" -"Edit the :file:`/etc/sysctl.conf` file to contain the following parameters:" -msgstr "" -":file:`/etc/sysctl.conf` ファイルを編集して、以下のパラメーターを追加します。" - msgid "" "Edit the :file:`/srv/www/openstack-dashboard/openstack_dashboard/local/" "local_settings.py` file and complete the following actions:" @@ -1681,6 +1616,36 @@ msgstr "" "``/etc/apache2/apache2.conf`` ファイルを編集し、``ServerName`` オプションを設" "定し、コントローラーノードを参照します。" +msgid "" +"Edit the ``/etc/chrony.conf`` file and add, change, or remove the following " +"keys as necessary for your environment:" +msgstr "" +"``/etc/ntp.conf`` ファイルを編集して、お使いの環境の必要に応じて、以下のキー" +"を追加、変更、削除します。" + +msgid "" +"Edit the ``/etc/chrony.conf`` file and comment out or remove all but one " +"``server`` key. Change it to reference the controller node:" +msgstr "" +"``/etc/chrony/chrony.conf`` ファイルを編集して、1 つの ``server`` キー以外の" +"すべてをコメントアウトまたは削除します。このキーはコントローラーノードを参照" +"するよう変更します。" + +msgid "" +"Edit the ``/etc/chrony/chrony.conf`` file and add, change, or remove the " +"following keys as necessary for your environment:" +msgstr "" +"``/etc/ntp.conf`` ファイルを編集して、お使いの環境の必要に応じて、以下のキー" +"を追加、変更、削除します。" + +msgid "" +"Edit the ``/etc/chrony/chrony.conf`` file and comment out or remove all but " +"one ``server`` key. Change it to reference the controller node:" +msgstr "" +"``/etc/chrony/chrony.conf`` ファイルを編集して、1 つの ``server`` キー以外の" +"すべてをコメントアウトまたは削除します。このキーはコントローラーノードを参照" +"するよう変更します。" + msgid "" "Edit the ``/etc/glance/glance-api.conf`` file and complete the following " "actions:" @@ -1701,34 +1666,45 @@ msgstr "" "``/etc/httpd/conf/httpd.conf`` ファイルを編集し、``ServerName`` オプションを" "設定し、コントローラーノードを参照します。" -msgid "Edit the ``/etc/neutron/dhcp_agent.ini`` file." -msgstr "``/etc/neutron/dhcp_agent.ini`` ファイルを編集します。" - -msgid "Edit the ``/etc/neutron/l3_agent.ini`` file:" -msgstr "``/etc/neutron/l3_agent.ini`` ファイルを編集します。" - -msgid "Edit the ``/etc/neutron/metadata_agent.ini`` file." -msgstr "``/etc/neutron/metadata_agent.ini`` ファイルを編集します。" - -msgid "Edit the ``/etc/neutron/neutron.conf`` file." -msgstr "``/etc/neutron/neutron.conf`` ファイルを編集します。" - -msgid "Edit the ``/etc/neutron/plugins/ml2/linuxbridge_agent.conf`` file." +msgid "" +"Edit the ``/etc/neutron/dhcp_agent.ini`` file and complete the following " +"actions:" msgstr "" -"``/etc/neutron/plugins/ml2/linuxbridge_agent.conf`` ファイルを編集します。" +"``/etc/neutron/dhcp_agent.ini`` ファイルを編集して、以下の作業を実行します。" -msgid "Edit the ``/etc/neutron/plugins/ml2/ml2_conf.ini`` file." -msgstr "``/etc/neutron/plugins/ml2/ml2_conf.ini`` ファイルを編集します。" +msgid "" +"Edit the ``/etc/neutron/l3_agent.ini`` file and complete the following " +"actions:" +msgstr "" +"``/etc/neutron/l3_agent.ini`` ファイルを編集して、以下の作業を実行します。" + +msgid "" +"Edit the ``/etc/neutron/neutron.conf`` file and complete the following " +"actions:" +msgstr "" +"``/etc/neutron/neutron.conf`` ファイルを編集し、以下の作業を実行します。" + +msgid "" +"Edit the ``/etc/neutron/plugins/ml2/linuxbridge_agent.conf`` file and " +"complete the following actions:" +msgstr "" +"``/etc/neutron/plugins/ml2/linuxbridge_agent.conf`` ファイルを編集して、以下" +"の作業を実行します。" + +msgid "" +"Edit the ``/etc/neutron/plugins/ml2/ml2_conf.ini`` file and complete the " +"following actions:" +msgstr "" +"``/etc/neutron/plugins/ml2/ml2_conf.ini`` ファイルを編集して、以下の作業を実" +"行します。" msgid "" "Edit the ``/etc/nova/nova.conf`` file and complete the following actions:" msgstr "``/etc/nova/nova.conf`` ファイルを編集し、以下の作業を完了します。" -msgid "Edit the ``/etc/nova/nova.conf`` file." -msgstr "``/etc/nova/nova.conf`` ファイルを編集します。" - -msgid "Edit the ``/etc/nova/nova.conf`` file:" -msgstr "``/etc/nova/nova.conf`` ファイルを編集します。" +msgid "Edit the ``/etc/sysctl.conf`` file to contain the following parameters:" +msgstr "" +"``/etc/sysctl.conf`` ファイルを編集して、以下のパラメーターを追加します。" msgid "" "Edit the ``[libvirt]`` section in the ``/etc/nova/nova-compute.conf`` file " @@ -1955,6 +1931,14 @@ msgstr "" "詳細は `バグ報告 `__ を" "参照してください。" +msgid "For networking option 2, also install the ``neutron-l3-agent`` package." +msgstr "" +"Networking オプション 2 の場合、``neutron-l3-agent`` パッケージもインストール" +"します。" + +msgid "For networking option 2, also restart the layer-3 service:" +msgstr "Networking オプション 2 の場合、L3 サービスも再起動します。" + msgid "" "For security reasons, disable the temporary authentication token mechanism:" msgstr "セキュリティのため、一時認証トークンメカニズムを無効化します。" @@ -2088,12 +2072,9 @@ msgid "" msgstr "" "Horizon は、コアなクラス、再利用可能なテンプレートやツールを提供します。" -msgid "Host Networking" +msgid "Host networking" msgstr "ホストネットワーク" -msgid "Host networking, NTP, OpenStack service dependencies" -msgstr "ホストのネットワーク、NTP、OpenStack サービスの依存関係" - msgid "" "However, VMs will reduce performance of your instances, particularly if your " "hypervisor and/or processor lacks support for hardware acceleration of " @@ -2207,15 +2188,6 @@ msgstr "" "ジャーナリングの設定を変更する場合、MongoDB サービスを停止し、初期ジャーナル" "ファイルを削除し、サービスを起動します。" -msgid "" -"If you choose to install on VMs, make sure your hypervisor permits :term:" -"`promiscuous mode` and disables MAC address filtering on the :term:`external " -"network`." -msgstr "" -"仮想マシンにインストールする場合、お使いのハイパーバイザーが :term:`外部ネッ" -"トワーク ` で :term:`プロミスキャスモード ` を許可し、MAC アドレスフィルタリングを無効化していることを確認します。" - msgid "" "If you configure a package with ``debconf`` incorrectly, you can re-" "configure it, as follows:" @@ -2236,6 +2208,13 @@ msgstr "" "QCOW2 や VMDK などの raw 以外のイメージ形式を使用したい場合、QEMU サポート" "パッケージをインストールします。" +msgid "" +"If your environment includes the Block Storage service, you can create a " +"volume and attach it to an instance." +msgstr "" +"お使いの環境に Block Storage がある場合、ボリュームを作成して、それをインスタ" +"ンスに接続できます。" + msgid "" "If your storage nodes use LVM on the operating system disk, you must also " "add the associated device to the filter. For example, if the :file:`/dev/" @@ -2262,6 +2241,9 @@ msgstr "" "場合、コントローラーノードで管理インターフェースの IP アドレスで " "``controller`` を置き換えられます。" +msgid "Ignore any warnings in this output." +msgstr "この出力のエラーはすべて無視してください。" + # #-#-#-#-# neutron-compute-node.pot (Installation Guide 0.1) #-#-#-#-# # #-#-#-#-# neutron-network-node.pot (Installation Guide 0.1) #-#-#-#-# msgid "Implement the changes:" @@ -2726,6 +2708,13 @@ msgstr "" "``[token]`` セクションに UUID トークンプロバイダーと Memcached ドライバーを設" "定します。" +msgid "" +"In the ``[vnc]`` section, configure the VNC proxy to use the management " +"interface IP address of the controller node:" +msgstr "" +"``[vnc]`` セクションで、コントローラーノードの管理インターフェース IP アドレ" +"スを使用するために、VNC プロキシを設定します。" + msgid "In the ``[vnc]`` section, enable and configure remote console access:" msgstr "" "``[vnc]`` セクションにおいて、リモートコンソールアクセスを有効化および設定し" @@ -2743,12 +2732,26 @@ msgstr "" "``devices`` セクションに、:file:`/dev/sdb` デバイスを受け付け、他のデバイスを" "すべて拒否するフィルターを追加します。" +msgid "" +"Increase security using methods such as firewalls, encryption, and service " +"policies." +msgstr "" +"ファイアウォール、暗号化、サービスポリシーなどの方法を使用して、セキュリ" +"ティーを向上させます。" + # #-#-#-#-# dashboard-install.pot (Installation Guide 0.1) #-#-#-#-# # #-#-#-#-# glance-install.pot (Installation Guide 0.1) #-#-#-#-# # #-#-#-#-# keystone-install.pot (Installation Guide 0.1) #-#-#-#-# msgid "Install and configure" msgstr "インストールと設定" +msgid "" +"Install and configure :term:`NTP` using the instructions in :ref:" +"`environment-ntp`." +msgstr "" +":ref:`environment-ntp` の説明に従って、:term:`NTP` をインストールして設定しま" +"す。" + msgid "Install and configure Block Storage volume components" msgstr "Block Storage ボリュームコンポーネントのインストールと設定" @@ -2781,11 +2784,6 @@ msgstr "ストレージノードのコンポーネントのインストールと msgid "Install and configure the Networking components" msgstr "Networking コンポーネントのインストールおよび設定" -msgid "Install and configure the Networking components on a *compute* node." -msgstr "" -"*コンピュート* ノードにおいて、Networking のコンポーネントをインストールおよ" -"び設定します。" - msgid "" "Install and configure the Networking components on the *controller* node." msgstr "" @@ -2813,12 +2811,6 @@ msgstr "LVM パッケージをインストールします。" msgid "Install the MongoDB package:" msgstr "MongoDB パッケージをインストールします。" -msgid "Install the NTP service" -msgstr "NTP サービスのインストール" - -msgid "Install the Networking components" -msgstr "Networking コンポーネントのインストール" - msgid "Install the OpenStack client" msgstr "OpenStack client のインストール" @@ -2835,12 +2827,12 @@ msgstr "" "``rdo-release-liberty`` パッケージをインストールし、RDO リポジトリを有効化し" "ます。" +msgid "Install the components" +msgstr "コンポーネントのインストール" + msgid "Install the message queue service" msgstr "メッセージキューサービスのインストール" -msgid "Install the networking components" -msgstr "ネットワークコンポーネントのインストール" - msgid "Install the package:" msgstr "パッケージをインストールします。" @@ -2993,13 +2985,6 @@ msgstr "" "ます。これらは、以下のとおり DSN (Database Source Name) ディレクティブ経由で" "設定されます。" -msgid "" -"Many users build their test environment on a :term:`virtual machine (VM)`. " -"The primary benefits of VMs include the following:" -msgstr "" -"多くのユーザーは、:term:`仮想マシン ` にテスト環境を構" -"築します。仮想マシンの主な利点は以下のとおりです。" - msgid "Message queue" msgstr "メッセージキュー" @@ -3042,6 +3027,9 @@ msgstr "デバイスをマウントします。" msgid "Name" msgstr "名前" +msgid "Network Time Protocol (NTP)" +msgstr "Network Time Protocol (NTP)" + msgid "" "Network interface names vary by distribution. Traditionally, interfaces use " "\"eth\" followed by a sequential number. To cover all variations, this guide " @@ -3419,6 +3407,27 @@ msgstr "" msgid "Other nodes" msgstr "その他ノード" +msgid "" +"Overlay networks such as VXLAN include additional packet headers that " +"increase overhead and decrease space available for the payload or user data. " +"Without knowledge of the virtual network infrastructure, instances attempt " +"to send packets using the default Ethernet :term:`maximum transmission unit " +"(MTU)` of 1500 bytes. :term:`Internet protocol (IP)` networks contain the :" +"term:`path MTU discovery (PMTUD)` mechanism to detect end-to-end MTU and " +"adjust packet size accordingly. However, some operating systems and networks " +"block or otherwise lack support for PMTUD causing performance degradation or " +"connectivity failure." +msgstr "" +"VXLAN などのオーバーレイネットワークは、オーバーヘッドを増やし、ペイロードや" +"ユーザーデータに利用可能な容量を減らす、追加のパケットヘッダーを含みます。仮" +"想ネットワーク基盤の知識がないと、インスタンスが、デフォルトの Ethernet :" +"term:`maximum transmission unit (MTU)` 1500 バイトを使用して、パケットを送信" +"しようとします。:term:`Internet protocol (IP)` は、:term:`path MTU discovery " +"(PMTUD)` 機構を有していて、エンド間の MTU を検知して、パケット容量を適切に調" +"整します。しかしながら、いくつかのオペレーティングシステムやネットワークは、" +"パフォーマンス劣化や接続エラーを引き起こす PMTUD をブロックします。または、サ" +"ポートしていません。" + msgid "Overview" msgstr "概要" @@ -3559,6 +3568,9 @@ msgstr "" "可能なドライバーアーキテクチャーにより、ブロックストレージデバイスの作成と管" "理が容易になります。" +msgid "Public on 203.0.113.0/24 with gateway 203.0.113.1" +msgstr "パブリックネットワーク 203.0.113.0/24、ゲートウェイ 203.0.113.1" + msgid "Public provider network" msgstr "パブリックプロバイダーネットワーク" @@ -3821,6 +3833,11 @@ msgstr "" "メタデータプロキシ用に選択した適切なシークレットで ``METADATA_SECRET`` を置き" "換えます。" +msgid "" +"Replace ``NEUTRON_DBPASS`` with the password you chose for the database." +msgstr "" +"``NEUTRON_DBPASS`` をデータベース用に選択したパスワードで置き換えます。" + # #-#-#-#-# neutron-compute-node.pot (Installation Guide 0.1) #-#-#-#-# # #-#-#-#-# neutron-controller-node.pot (Installation Guide 0.1) #-#-#-#-# # #-#-#-#-# neutron-network-node.pot (Installation Guide 0.1) #-#-#-#-# @@ -4058,6 +4075,20 @@ msgstr "``image.download`` メーターの利用状況を取得します。" msgid "Return to :ref:`Launch an instance `." msgstr ":ref:`インスタンスの起動 ` に戻ります。" +msgid "" +"Return to :ref:`Networking compute node configuration `." +msgstr "" +":ref:`Networking コンピュートノードの設定 ` に戻りま" +"す。" + +msgid "" +"Return to :ref:`Networking controller node configuration `." +msgstr "" +":ref:`Networking コントローラーノードの設定 ` に戻ります。" + msgid "Return to :ref:`launch-instance`." msgstr ":ref:`launch-instance` に戻ります。" @@ -4083,14 +4114,11 @@ msgid "Search in this guide" msgstr "ガイド内検索" msgid "" -"Secure the database service including choosing a suitable password for the " -"root account:" +"Secure the database service by running the ``mysql_secure_installation`` " +"script." msgstr "" -"データベースの root アカウントに適切なパスワードを選択するなど、データベース" -"サービスをセキュア化します。" - -msgid "Secure the database service:" -msgstr "データベースサービスをセキュア化します。" +"``mysql_secure_installation`` スクリプトを実行して、データベースサービスをセ" +"キュア化します。" msgid "Security" msgstr "セキュリティ" @@ -4108,17 +4136,14 @@ msgstr "" "``keystone`` パイプラインを選択し、Image service が Identity を使用するよう設" "定します。" -# #-#-#-#-# neutron-compute-node.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# neutron-controller-node.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# neutron-network-node.pot (Installation Guide 0.1) #-#-#-#-# msgid "" "Selecting the ML2 plug-in also populates the ``service_plugins`` and " -"``allow_overlapping_ips`` options in the :file:`/etc/neutron/neutron.conf` " -"file with the appropriate values." +"``allow_overlapping_ips`` options in the ``/etc/neutron/neutron.conf`` file " +"with the appropriate values." msgstr "" -"ML2 プラグインを選択することにより、:file:`/etc/neutron/neutron.conf` ファイ" -"ルのオプション ``service_plugins`` と ``allow_overlapping_ips`` にも適切な値" -"が入ります。" +"ML2 プラグインを選択することにより、``/etc/neutron/neutron.conf`` ファイルの" +"オプション ``service_plugins`` と ``allow_overlapping_ips`` にも適切な値が入" +"ります。" msgid "Service" msgstr "サービス" @@ -4185,6 +4210,25 @@ msgstr "" "し、割り当てます。これらのケースで、ユーザー ID 値が重要ではありません。ユー" "ザー ID の存在が重要です。" +msgid "" +"Some cloud images ignore the DHCP MTU option in which case you should " +"configure it using metadata, a script, or other suitable method." +msgstr "" +"いくつかのクラウドイメージは、メタデータ、スクリプト、他の適切な方法を使用す" +"るよう設定している場合、DHCP MTU オプションを無視します。" + +msgid "" +"Some distributions add an extraneous entry in the :file:`/etc/hosts` file " +"that resolves the actual hostname to another loopback IP address such as " +"``127.0.1.1``. You must comment out or remove this entry to prevent name " +"resolution problems. **Do not remove the 127.0.0.1 entry.**" +msgstr "" +"いくつかのディストリビューションは、:file:`/etc/hosts` ファイルに無関係な項目" +"を追加します。これは、実際のホスト名を別のループバック IP アドレス " +"``127.0.1.1`` などに名前解決します。名前解決の問題を防ぐために、この項目をコ" +"メントアウトまたは削除する必要があります。*127.0.0.1 の項目を削除しないでくだ" +"さい。*" + msgid "Some distributions include LVM by default." msgstr "いくつかのディストリビューションは、デフォルトで LVM を含みます。" @@ -4565,33 +4609,27 @@ msgstr "" "Networking のサーバーコンポーネントの設定は、データベース、認証メカニズム、" "メッセージキュー、トポロジー変更通知、プラグインを含みます。" -# #-#-#-#-# neutron-compute-node.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# neutron-controller-node.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# neutron-network-node.pot (Installation Guide 0.1) #-#-#-#-# msgid "" -"The Networking service initialization scripts expect a symbolic link :file:`/" -"etc/neutron/plugin.ini` pointing to the ML2 plug-in configuration file, :" -"file:`/etc/neutron/plugins/ml2/ml2_conf.ini`. If this symbolic link does not " -"exist, create it using the following command:" +"The Networking service initialization scripts expect a symbolic link ``/etc/" +"neutron/plugin.ini`` pointing to the ML2 plug-in configuration file, ``/etc/" +"neutron/plugins/ml2/ml2_conf.ini``. If this symbolic link does not exist, " +"create it using the following command:" msgstr "" -"Networking のサービス初期化スクリプトは、シンボリックリンク :file:`/etc/" -"neutron/plugin.ini` が ML2 プラグイン設定ファイル :file:`/etc/neutron/" -"plugins/ml2/ml2_conf.ini` を指し示すことを期待します。このシンボリックリンク" -"が存在しなければ、以下のコマンドを使用して作成します。" +"Networking のサービス初期化スクリプトは、シンボリックリンク ``/etc/neutron/" +"plugin.ini`` が ML2 プラグイン設定ファイル ``/etc/neutron/plugins/ml2/" +"ml2_conf.ini`` を指し示すことを期待します。このシンボリックリンクが存在しなけ" +"れば、以下のコマンドを使用して作成します。" -# #-#-#-#-# neutron-compute-node.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# neutron-controller-node.pot (Installation Guide 0.1) #-#-#-#-# -# #-#-#-#-# neutron-network-node.pot (Installation Guide 0.1) #-#-#-#-# msgid "" "The Networking service initialization scripts expect the variable " -"``NEUTRON_PLUGIN_CONF`` in the :file:`/etc/sysconfig/neutron` file to " -"reference the ML2 plug-in configuration file. Edit the :file:`/etc/sysconfig/" -"neutron` file and add the following:" +"``NEUTRON_PLUGIN_CONF`` in the ``/etc/sysconfig/neutron`` file to reference " +"the ML2 plug-in configuration file. Edit the ``/etc/sysconfig/neutron`` file " +"and add the following:" msgstr "" "Networking のサービス初期化スクリプトは、ML2 プラグイン設定ファイルを参照する" -"ために、:file:`/etc/sysconfig/neutron` ファイルに ``NEUTRON_PLUGIN_CONF`` 変" -"数があることを期待します。:file:`/etc/sysconfig/neutron` ファイルを編集し、以" -"下を追加します。" +"ために、``/etc/sysconfig/neutron`` ファイルに ``NEUTRON_PLUGIN_CONF`` 変数が" +"あることを期待します。``/etc/sysconfig/neutron`` ファイルを編集し、以下を追加" +"します。" msgid "" "The Nova notification_driver creates alerts and sends system state updates " @@ -4897,6 +4935,20 @@ msgstr "" msgid "The other directives concerning RabbitMQ will stay untouched." msgstr "他の RabbitMQ に関するディレクティブは、そのままにしておきます。" +msgid "" +"The output should indicate four agents on the controller node and one agent " +"on each compute node." +msgstr "" +"この出力は、コントローラーノードに 4 つのエージェント、各コンピュートノード" +"に 1 つのエージェントがあることを意味します。" + +msgid "" +"The output should indicate three agents on the controller node and one agent " +"on each compute node." +msgstr "" +"この出力は、コントローラーノードに 3 つのエージェント、各コンピュートノード" +"に 1 つのエージェントがあることを意味します。" + msgid "" "The packages are signed by GPG key 893A90DAD85F9316. You should verify the " "fingerprint of the imported GPG key before using it." @@ -5122,13 +5174,6 @@ msgstr "" "このガイドは、Debian 8 (コード名: Jessie) において利用可能なパッケージを使用" "するインストールについて詳細に説明しています。" -msgid "" -"This guide walks through an installation by using packages available through " -"Ubuntu 14.04." -msgstr "" -"このガイドは、Ubuntu 14.04 において利用可能なパッケージを使用するインストール" -"について詳細に説明しています。" - msgid "" "This information is stored in the configuration file for each service. For " "example:" @@ -5382,6 +5427,13 @@ msgid "" msgstr "" "これにより、以下のディレクティブ (:file:`nova.conf` の例) が設定されます。" +msgid "" +"Throughout the guide the OpenStack client will be used to perform actions on " +"the installed services." +msgstr "" +"ガイド全体を通して、インストール済みサービスに処理を実行するために、" +"OpenStack Client が使用されます。" + # #-#-#-#-# ceilometer-nova.pot (Installation Guide 0.1) #-#-#-#-# # #-#-#-#-# ceilometer-swift.pot (Installation Guide 0.1) #-#-#-#-# msgid "To configure notifications" @@ -5401,9 +5453,6 @@ msgstr "通知の設定方法" msgid "To configure prerequisites" msgstr "前提条件の設定方法" -msgid "To configure the Networking common components" -msgstr "Networking 共通コンポーネントの設定方法" - msgid "To configure the dashboard" msgstr "ダッシュボードの設定方法" @@ -5448,10 +5497,10 @@ msgstr "" msgid "" "To enable other nodes to connect to the chrony daemon on the controller, add " -"the following key to :file:`/etc/chrony.conf`:" +"the following key to the ``/etc/chrony.conf`` file:" msgstr "" "他のノードがコントローラーノードの chrony デーモンに接続できるよう、以下の" -"キーを :file:`/etc/chrony.conf` に追加します。" +"キーを ``/etc/chrony.conf`` に追加します。" # #-#-#-#-# ceilometer-controller-install.pot (Installation Guide 0.1) # #-#-#-#-# diff --git a/doc/networking-guide/source/locale/networking-guide.pot b/doc/networking-guide/source/locale/networking-guide.pot index 9db6df8e94..929bcabaa9 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-10-04 06:17+0000\n" +"POT-Creation-Date: 2015-10-08 06:30+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -16,6 +16,1230 @@ msgstr "" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" +#: ../adv_config.rst:3 +msgid "Advanced configuration" +msgstr "" + +# #-#-#-#-# adv_config_FwaaS.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# adv_config_ipv6.pot (Networking Guide 0.9) #-#-#-#-# +#: ../adv_config_FwaaS.rst:3 ../adv_config_ipv6.rst:399 +msgid "FWaaS" +msgstr "" + +#: ../adv_config_FwaaS.rst:5 +msgid "See the following URL:" +msgstr "" + +#: ../adv_config_FwaaS.rst:7 +msgid "" +"http://docs.openstack.org/admin-guide-cloud/networking_introduction." +"html#firewall-as-a-service-fwaas-overview" +msgstr "" + +# #-#-#-#-# adv_config_ipv6.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# adv_config_LBaaS.pot (Networking Guide 0.9) #-#-#-#-# +#: ../adv_config_LBaaS.rst:3 ../adv_config_ipv6.rst:394 +msgid "LBaaS" +msgstr "" + +#: ../adv_config_LBaaS.rst:5 +msgid "See the following URLs:" +msgstr "" + +#: ../adv_config_LBaaS.rst:7 +msgid "" +"http://docs.openstack.org/admin-guide-cloud/networking_introduction." +"html#load-balancer-as-a-service-lbaas-overview" +msgstr "" + +#: ../adv_config_LBaaS.rst:9 +msgid "" +"http://docs.openstack.org/admin-guide-cloud/networking_config-agents." +"html#configure-load-balancer-as-a-service-lbaas" +msgstr "" + +#: ../adv_config_LBaaS.rst:11 +msgid "" +"http://docs.openstack.org/admin-guide-cloud/networking_adv-features." +"html#basic-load-balancer-as-a-service-operations" +msgstr "" + +# #-#-#-#-# adv_config_ipv6.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# adv_config_VPNaaS.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# intro_os_networking_service.pot (Networking Guide 0.9) #-#-#-#-# +#: ../adv_config_VPNaaS.rst:3 ../adv_config_ipv6.rst:381 +#: ../intro_os_networking_service.rst:69 +msgid "VPNaaS" +msgstr "" + +# #-#-#-#-# adv_config_group_policy.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# adv_config_operational.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# adv_config_service_chaining.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# adv_config_VPNaaS.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# migration_legacy_to_dvr.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# migration_legacy_to_L3_HA.pot (Networking Guide 0.9) #-#-#-#-# +#: ../adv_config_VPNaaS.rst:5 ../adv_config_group_policy.rst:5 +#: ../adv_config_group_policy.rst:12 ../adv_config_operational.rst:5 +#: ../adv_config_service_chaining.rst:7 ../migration_legacy_to_L3_HA.rst:5 +#: ../migration_legacy_to_dvr.rst:5 +msgid "TBD" +msgstr "" + +#: ../adv_config_debugging.rst:3 +msgid "Debugging" +msgstr "" + +#: ../adv_config_debugging.rst:5 +msgid "" +"The OpenStack Networking service offers many degrees of freedom because of " +"the pluggable back end that supports a variety of open source and vendor " +"(proprietary) plug-ins. The open source plug-ins generally implement native " +"Linux facilities such as Open vSwitch (OVS) and Linux bridge. This section " +"provides methods to troubleshoot and mitigate network issues for " +"environments using the open source ML2 plug-in with the OVS or Linux bridge " +"agent." +msgstr "" + +#: ../adv_config_debugging.rst:14 ../adv_config_debugging.rst:29 +msgid "Neutron-debug command line tools" +msgstr "" + +#: ../adv_config_debugging.rst:16 +msgid "" +"Network troubleshooting can unfortunately be a very difficult and confusing " +"procedure. A network issue can cause a problem at several points in the " +"cloud. Using a logical troubleshooting procedure can help mitigate the " +"confusion and quickly isolate the network issue." +msgstr "" + +#: ../adv_config_debugging.rst:21 +msgid "" +"Some of the following sections reference these popular tools to understand " +"both network configuration and traffic patterns:" +msgstr "" + +#: ../adv_config_debugging.rst:24 +msgid "iproute2" +msgstr "" + +#: ../adv_config_debugging.rst:25 +msgid "tcpdump" +msgstr "" + +#: ../adv_config_debugging.rst:26 +msgid "iptables" +msgstr "" + +#: ../adv_config_debugging.rst:31 ../adv_config_debugging.rst:36 +#: ../adv_config_debugging.rst:41 ../adv_config_debugging.rst:46 +#: ../adv_config_debugging.rst:51 ../adv_config_debugging.rst:56 +msgid "Subsection ..." +msgstr "" + +#: ../adv_config_debugging.rst:34 +msgid "Network configuration in the database" +msgstr "" + +#: ../adv_config_debugging.rst:39 +msgid "Debugging DHCP Issues" +msgstr "" + +#: ../adv_config_debugging.rst:44 +msgid "Debugging DNS Issues" +msgstr "" + +#: ../adv_config_debugging.rst:49 +msgid "Network namespaces configuration" +msgstr "" + +#: ../adv_config_debugging.rst:54 +msgid "Summary" +msgstr "" + +#: ../adv_config_group_policy.rst:3 +msgid "Group policy" +msgstr "" + +#: ../adv_config_group_policy.rst:9 +msgid "How it differs from legacy neutron data model" +msgstr "" + +#: ../adv_config_ipv6.rst:3 +msgid "Using OpenStack Networking with IPv6" +msgstr "" + +#: ../adv_config_ipv6.rst:5 +msgid "" +"The purpose of this page is to describe how the features and functionality " +"available in OpenStack (using neutron networking) as of the Kilo release. It " +"is intended to serve as a guide for how to deploy IPv6-enabled instances " +"using OpenStack Networking. Where appropriate, features planned for Liberty " +"or beyond may be described." +msgstr "" + +# #-#-#-#-# adv_config_ipv6.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# adv_config_qos.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# adv_config_sriov.pot (Networking Guide 0.9) #-#-#-#-# +#: ../adv_config_ipv6.rst:12 ../adv_config_qos.rst:23 +#: ../adv_config_sriov.rst:11 +msgid "The basics" +msgstr "" + +#: ../adv_config_ipv6.rst:14 +msgid "" +"OpenStack Networking has supported IPv6 tenant subnets in certain " +"configurations since Juno, but the Kilo release adds a number of new " +"features, functionality and bug fixes to make it more robust. The focus of " +"this page will be:" +msgstr "" + +#: ../adv_config_ipv6.rst:19 +msgid "How to enable dual-stack (IPv4 and IPv6 enabled) instances." +msgstr "" + +#: ../adv_config_ipv6.rst:20 +msgid "How those instances receive an IPv6 address." +msgstr "" + +#: ../adv_config_ipv6.rst:21 +msgid "" +"How those instances communicate across a router to other subnets or the " +"internet." +msgstr "" + +#: ../adv_config_ipv6.rst:23 +msgid "How those instances interact with other OpenStack services." +msgstr "" + +#: ../adv_config_ipv6.rst:25 +msgid "" +"To enable a dual-stack network in OpenStack Networking simply requires " +"creating a subnet with the ``ip_version`` field set to ``6``, then the IPv6 " +"attributes (``ipv6_ra_mode`` and ``ipv6_address_mode``) set. The " +"``ipv6_ra_mode`` and ``ipv6_address_mode`` will be described in detail in " +"the next section. Finally, the subnets ``cidr`` needs to be provided." +msgstr "" + +#: ../adv_config_ipv6.rst:32 +msgid "Not in scope" +msgstr "" + +#: ../adv_config_ipv6.rst:34 +msgid "Things not in the scope of this document include:" +msgstr "" + +#: ../adv_config_ipv6.rst:36 +msgid "Single stack IPv6 tenant networking" +msgstr "" + +#: ../adv_config_ipv6.rst:37 +msgid "" +"OpenStack control communication between servers and services over an IPv6 " +"network." +msgstr "" + +#: ../adv_config_ipv6.rst:39 +msgid "Connection to the OpenStack APIs via an IPv6 transport network" +msgstr "" + +#: ../adv_config_ipv6.rst:40 +msgid "IPv6 multicast" +msgstr "" + +#: ../adv_config_ipv6.rst:41 +msgid "" +"IPv6 support in conjunction with any out of tree routers, switches, services " +"or agents whether in physical or virtual form factors." +msgstr "" + +#: ../adv_config_ipv6.rst:46 +msgid "Neutron subnets and the IPv6 API attributes" +msgstr "" + +#: ../adv_config_ipv6.rst:48 +msgid "" +"As of Juno, the OpenStack Networking service (neutron) provides two new " +"attributes to the subnet object, which allows users of the API to configure " +"IPv6 subnets." +msgstr "" + +#: ../adv_config_ipv6.rst:52 +msgid "There are two IPv6 attributes:" +msgstr "" + +#: ../adv_config_ipv6.rst:54 +msgid "``ipv6_ra_mode``" +msgstr "" + +#: ../adv_config_ipv6.rst:55 +msgid "``ipv6_address_mode``" +msgstr "" + +#: ../adv_config_ipv6.rst:57 +msgid "These attributes can be set to the following values:" +msgstr "" + +#: ../adv_config_ipv6.rst:59 +msgid "``slaac``" +msgstr "" + +#: ../adv_config_ipv6.rst:60 +msgid "``dhcpv6-stateful``" +msgstr "" + +#: ../adv_config_ipv6.rst:61 +msgid "``dhcpv6-stateless``" +msgstr "" + +#: ../adv_config_ipv6.rst:63 +msgid "The attributes can also be left unset." +msgstr "" + +#: ../adv_config_ipv6.rst:67 +msgid "IPv6 addressing" +msgstr "" + +#: ../adv_config_ipv6.rst:69 +msgid "" +"The ``ipv6_address_mode`` attribute is used to control how addressing is " +"handled by OpenStack. There are a number of different ways that guest " +"instances can obtain an IPv6 address, and this attribute exposes these " +"choices to users of the Networking API." +msgstr "" + +#: ../adv_config_ipv6.rst:76 +msgid "Router advertisements" +msgstr "" + +#: ../adv_config_ipv6.rst:78 +msgid "" +"The ``ipv6_ra_mode`` attribute is used to control router advertisements for " +"a subnet." +msgstr "" + +#: ../adv_config_ipv6.rst:81 +msgid "" +"The IPv6 Protocol uses Internet Control Message Protocol packets (ICMPv6) as " +"a way to distribute information about networking. ICMPv6 packets with the " +"type flag set to 134 are called \"Router Advertisement\" packets, which " +"broadcasts information about the router and the route that can be used by " +"guest instances to send network traffic." +msgstr "" + +#: ../adv_config_ipv6.rst:88 +msgid "" +"The ``ipv6_ra_mode`` is used to specify if the Networking service should " +"transmit ICMPv6 packets, for a subnet." +msgstr "" + +#: ../adv_config_ipv6.rst:93 +msgid "ipv6_ra_mode and ipv6_address_mode combinations" +msgstr "" + +#: ../adv_config_ipv6.rst:99 +msgid "ipv6 ra mode" +msgstr "" + +#: ../adv_config_ipv6.rst:100 +msgid "ipv6 address mode" +msgstr "" + +#: ../adv_config_ipv6.rst:101 +msgid "radvd A,M,O" +msgstr "" + +#: ../adv_config_ipv6.rst:102 +msgid "External Router A,M,O" +msgstr "" + +#: ../adv_config_ipv6.rst:103 +msgid "Description" +msgstr "" + +#: ../adv_config_ipv6.rst:104 ../adv_config_ipv6.rst:105 +#: ../adv_config_ipv6.rst:109 ../adv_config_ipv6.rst:114 +#: ../adv_config_ipv6.rst:119 ../adv_config_ipv6.rst:125 +#: ../adv_config_ipv6.rst:130 ../adv_config_ipv6.rst:135 +msgid "*N/S*" +msgstr "" + +#: ../adv_config_ipv6.rst:106 ../adv_config_ipv6.rst:111 +#: ../adv_config_ipv6.rst:116 ../adv_config_ipv6.rst:121 +#: ../adv_config_ipv6.rst:127 ../adv_config_ipv6.rst:132 +#: ../adv_config_ipv6.rst:137 ../adv_config_ipv6.rst:142 +#: ../adv_config_ipv6.rst:147 ../adv_config_ipv6.rst:153 +msgid "Off" +msgstr "" + +#: ../adv_config_ipv6.rst:107 +msgid "Not Defined" +msgstr "" + +#: ../adv_config_ipv6.rst:108 +msgid "Backwards compatibility with pre-Juno IPv6 behavior." +msgstr "" + +#: ../adv_config_ipv6.rst:110 ../adv_config_ipv6.rst:124 +#: ../adv_config_ipv6.rst:139 ../adv_config_ipv6.rst:140 +#: ../adv_config_ipv6.rst:157 ../adv_config_ipv6.rst:162 +#: ../adv_config_ipv6.rst:168 ../adv_config_ipv6.rst:178 +msgid "slaac" +msgstr "" + +#: ../adv_config_ipv6.rst:112 ../adv_config_ipv6.rst:126 +#: ../adv_config_ipv6.rst:141 +msgid "1,0,0" +msgstr "" + +#: ../adv_config_ipv6.rst:113 +msgid "" +"Guest instance obtains IPv6 address from non-OpenStack router using SLAAC." +msgstr "" + +#: ../adv_config_ipv6.rst:115 ../adv_config_ipv6.rst:129 +#: ../adv_config_ipv6.rst:144 ../adv_config_ipv6.rst:145 +#: ../adv_config_ipv6.rst:158 ../adv_config_ipv6.rst:167 +#: ../adv_config_ipv6.rst:172 ../adv_config_ipv6.rst:183 +msgid "dhcpv6-stateful" +msgstr "" + +#: ../adv_config_ipv6.rst:117 ../adv_config_ipv6.rst:131 +#: ../adv_config_ipv6.rst:146 +msgid "0,1,1" +msgstr "" + +#: ../adv_config_ipv6.rst:118 ../adv_config_ipv6.rst:123 +#: ../adv_config_ipv6.rst:128 ../adv_config_ipv6.rst:133 +#: ../adv_config_ipv6.rst:138 +msgid "Not currently implemented in the reference implementation." +msgstr "" + +#: ../adv_config_ipv6.rst:120 ../adv_config_ipv6.rst:134 +#: ../adv_config_ipv6.rst:150 ../adv_config_ipv6.rst:151 +#: ../adv_config_ipv6.rst:163 ../adv_config_ipv6.rst:173 +#: ../adv_config_ipv6.rst:177 ../adv_config_ipv6.rst:182 +msgid "dhcpv6-stateless" +msgstr "" + +#: ../adv_config_ipv6.rst:122 ../adv_config_ipv6.rst:136 +#: ../adv_config_ipv6.rst:152 +msgid "1,0,1" +msgstr "" + +#: ../adv_config_ipv6.rst:143 +msgid "" +"Guest instance obtains IPv6 address from OpenStack managed radvd using SLAAC." +msgstr "" + +#: ../adv_config_ipv6.rst:148 +msgid "" +"Guest instance obtains IPv6 address from dnsmasq using DHCPv6 stateful and " +"optional info from dnsmasq using DHCPv6." +msgstr "" + +#: ../adv_config_ipv6.rst:154 +msgid "" +"Guest instance obtains IPv6 address from OpenStack managed radvd using SLAAC " +"and optional info from dnsmasq using DHCPv6." +msgstr "" + +#: ../adv_config_ipv6.rst:161 ../adv_config_ipv6.rst:166 +#: ../adv_config_ipv6.rst:171 ../adv_config_ipv6.rst:176 +#: ../adv_config_ipv6.rst:181 ../adv_config_ipv6.rst:186 +msgid "*Invalid combination.*" +msgstr "" + +#: ../adv_config_ipv6.rst:189 +msgid "Tenant network considerations" +msgstr "" + +#: ../adv_config_ipv6.rst:193 +msgid "Dataplane" +msgstr "" + +#: ../adv_config_ipv6.rst:195 +msgid "" +"Both the Linux bridge and the Open vSwitch dataplane modules support " +"forwarding IPv6 packets amongst the guests and router ports. Similar to " +"IPv4, there is no special configuration or setup required to enable the " +"dataplane to properly forward packets from the source to the destination " +"using IPv6. Note that these dataplanes will forward Link-local Address (LLA) " +"packets between hosts on the same network just fine without any " +"participation or setup by OpenStack components after the ports are all " +"connected and MAC addresses learned." +msgstr "" + +#: ../adv_config_ipv6.rst:205 +msgid "Addresses for subnets" +msgstr "" + +#: ../adv_config_ipv6.rst:207 +msgid "There are four methods for a subnet to get its ``cidr`` in OpenStack:" +msgstr "" + +#: ../adv_config_ipv6.rst:209 +msgid "Direct assignment during subnet creation via command line or Horizon" +msgstr "" + +#: ../adv_config_ipv6.rst:210 +msgid "Referencing a subnet pool during subnet creation" +msgstr "" + +#: ../adv_config_ipv6.rst:212 +msgid "" +"In the future, different techniques could be used to allocate subnets to " +"tenants:" +msgstr "" + +#: ../adv_config_ipv6.rst:215 +msgid "Using a PD client to request a prefix for a subnet from a PD server" +msgstr "" + +#: ../adv_config_ipv6.rst:216 +msgid "Use of an external IPAM module to allocate the subnet" +msgstr "" + +#: ../adv_config_ipv6.rst:219 +msgid "Address modes for ports" +msgstr "" + +#: ../adv_config_ipv6.rst:221 +msgid "" +"That an external DHCPv6 server in theory could override the full address " +"OpenStack assigns based on the EUI-64 address, but that would not be wise as " +"it would not be consistent through the system." +msgstr "" + +#: ../adv_config_ipv6.rst:225 +msgid "" +"IPv6 supports three different addressing schemes for address configuration " +"and for providing optional network information." +msgstr "" + +#: ../adv_config_ipv6.rst:229 +msgid "Address configuration using Router Advertisement (RA)." +msgstr "" + +#: ../adv_config_ipv6.rst:229 +msgid "Stateless Address Auto Configuration (SLAAC)" +msgstr "" + +#: ../adv_config_ipv6.rst:232 +msgid "Address configuration using RA and optional information using DHCPv6." +msgstr "" + +#: ../adv_config_ipv6.rst:233 ../adv_config_ipv6.rst:306 +#: ../adv_config_ipv6.rst:307 +msgid "DHCPv6-stateless" +msgstr "" + +#: ../adv_config_ipv6.rst:236 +msgid "Address configuration and optional information using DHCPv6." +msgstr "" + +#: ../adv_config_ipv6.rst:236 ../adv_config_ipv6.rst:310 +#: ../adv_config_ipv6.rst:311 +msgid "DHCPv6-stateful" +msgstr "" + +#: ../adv_config_ipv6.rst:238 +msgid "" +"OpenStack can be setup such that OpenStack Networking directly provides RA, " +"DHCP relay and DHCPv6 address and optional information for their networks or " +"this can be delegated to external routers and services based on the drivers " +"that are in use. There are two neutron subnet attributes - ``ipv6_ra_mode`` " +"and ``ipv6_address_mode`` – that determine how IPv6 addressing and network " +"information is provided to tenant instances:" +msgstr "" + +#: ../adv_config_ipv6.rst:246 +msgid "``ipv6_ra_mode``: Determines who sends RA." +msgstr "" + +#: ../adv_config_ipv6.rst:247 +msgid "" +"``ipv6_address_mode``: Determines how instances obtain IPv6 address, default " +"gateway, or optional information." +msgstr "" + +#: ../adv_config_ipv6.rst:250 +msgid "" +"For the above two attributes to be effective, ``enable_dhcp`` must be set to " +"True in file :file:`neutron.conf`." +msgstr "" + +#: ../adv_config_ipv6.rst:254 +msgid "Using SLAAC for addressing" +msgstr "" + +#: ../adv_config_ipv6.rst:256 +msgid "" +"When using SLAAC, the currently supported combinations for ``ipv6_ra_mode`` " +"and ``ipv6_address_mode`` are as follows." +msgstr "" + +#: ../adv_config_ipv6.rst:263 ../adv_config_ipv6.rst:303 +msgid "ipv6_ra_mode" +msgstr "" + +#: ../adv_config_ipv6.rst:264 ../adv_config_ipv6.rst:304 +msgid "ipv6_address_mode" +msgstr "" + +#: ../adv_config_ipv6.rst:265 ../adv_config_ipv6.rst:305 +msgid "Result" +msgstr "" + +#: ../adv_config_ipv6.rst:266 +msgid "Not specified." +msgstr "" + +#: ../adv_config_ipv6.rst:267 ../adv_config_ipv6.rst:270 +#: ../adv_config_ipv6.rst:271 +msgid "SLAAC" +msgstr "" + +#: ../adv_config_ipv6.rst:268 +msgid "" +"Addresses are assigned using EUI-64, and an external router will be used for " +"routing." +msgstr "" + +#: ../adv_config_ipv6.rst:272 +msgid "" +"Address are assigned using EUI-64, and OpenStack Networking provides routing." +msgstr "" + +#: ../adv_config_ipv6.rst:275 +msgid "" +"Setting ``ipv6_ra_mode`` to ``slaac`` will result in OpenStack Networking " +"routers being configured to send RA packets, when they are created. This " +"results in the following values set for the address configuration flags in " +"the RA messages:" +msgstr "" + +#: ../adv_config_ipv6.rst:280 +msgid "Auto Configuration Flag = 1 Managed" +msgstr "" + +#: ../adv_config_ipv6.rst:281 +msgid "Configuration Flag = 0" +msgstr "" + +#: ../adv_config_ipv6.rst:282 +msgid "Other Configuration Flag = 0 New or existing" +msgstr "" + +#: ../adv_config_ipv6.rst:284 +msgid "" +"Neutron networks that contain a SLAAC enabled IPv6 subnet will result in all " +"neutron ports attached to the network receiving IPv6 addresses. This is " +"because when RA broadcast messages are sent out on a neutron network, they " +"are received by all IPv6 capable ports on the network, and each port will " +"then configure an IPv6 address based on the information contained in the RA " +"packet. In some cases, an IPv6 SLAAC address will be added to a port, in " +"addition to other IPv4 and IPv6 addresses that the port already has been " +"assigned." +msgstr "" + +#: ../adv_config_ipv6.rst:294 +msgid "DHCPv6" +msgstr "" + +#: ../adv_config_ipv6.rst:296 +msgid "" +"For DHCPv6-stateless, the currently supported combinations are as follows:" +msgstr "" + +#: ../adv_config_ipv6.rst:308 +msgid "" +"Address and optional information using neutron router and DHCP " +"implementation respectively." +msgstr "" + +#: ../adv_config_ipv6.rst:312 +msgid "Addresses and optional information are assigned using DHCPv6." +msgstr "" + +#: ../adv_config_ipv6.rst:314 +msgid "" +"Setting DHCPv6-stateless for ``ipv6_ra_mode`` configures the neutron router " +"with radvd agent to send RAs. The table below captures the values set for " +"the address configuration flags in the RA packet in this scenario. " +"Similarly, setting DHCPv6-stateless for ``ipv6_address_mode`` configures " +"neutron DHCP implementation to provide the additional network information." +msgstr "" + +#: ../adv_config_ipv6.rst:321 +msgid "Auto Configuration Flag = 1" +msgstr "" + +#: ../adv_config_ipv6.rst:322 +msgid "Managed Configuration Flag = 0" +msgstr "" + +#: ../adv_config_ipv6.rst:323 +msgid "Other Configuration Flag = 1" +msgstr "" + +#: ../adv_config_ipv6.rst:326 +msgid "Router support" +msgstr "" + +#: ../adv_config_ipv6.rst:328 +msgid "" +"The behavior of the neutron router for IPv6 is different than IPv4 in a few " +"ways." +msgstr "" + +#: ../adv_config_ipv6.rst:331 +msgid "" +"Internal router ports, that act as default gateway ports for a network, will " +"share a common port for all IPv6 subnets associated with the network. This " +"implies that there will be an IPv6 internal router interface with multiple " +"IPv6 addresses from each of the IPv6 subnets associated with the network and " +"a separate IPv4 internal router interface for the IPv4 subnet. On the other " +"hand, external router ports are allowed to have a dual-stack configuration " +"with both an IPv4 and an IPv6 address assigned to them." +msgstr "" + +#: ../adv_config_ipv6.rst:339 +msgid "" +"Neutron tenant networks that are assigned Global Unicast Address (GUA) " +"prefixes and addresses don’t require NAT on the neutron router external " +"gateway port to access the outside world. As a consequence of the lack of " +"NAT the external router port doesn’t require a GUA to send and receive to " +"the external networks. This implies a GUA IPv6 subnet prefix is not " +"necessarily needed for the neutron external network. By default, a IPv6 LLA " +"associated with the external gateway port can be used for routing purposes. " +"To handle this scenario, the implementation of router-gateway-set API in " +"neutron has been modified so that an IPv6 subnet is not required for the " +"external network that is associated with the neutron router. The LLA address " +"of the upstream router can be learned in two ways." +msgstr "" + +#: ../adv_config_ipv6.rst:351 +msgid "" +"In the absence of an upstream RA support, ``ipv6_gateway`` flag can be set " +"with the external router gateway LLA in the neutron L3 agent configuration " +"file. This also requires that no subnet is associated with that port." +msgstr "" + +#: ../adv_config_ipv6.rst:354 +msgid "" +"The upstream router can send an RA and the neutron router will automatically " +"learn the next-hop LLA, provided again that no subnet is assigned and the " +"``ipv6_gateway`` flag is not set." +msgstr "" + +#: ../adv_config_ipv6.rst:358 +msgid "" +"Effectively the ``ipv6_gateway`` flag takes precedence over an RA that is " +"received from the upstream router. If it is desired to use a GUA next hop " +"that is accomplished by allocating a subnet to the external router port and " +"assigning the upstream routers GUA address as the gateway for the subnet." +msgstr "" + +#: ../adv_config_ipv6.rst:364 +msgid "" +"That it should be possible for tenants to communicate with each other on an " +"isolated network (a network without a router port) using LLA with little to " +"no participation on the part of OpenStack. The authors of this section have " +"not proven that to be true for all scenarios." +msgstr "" + +#: ../adv_config_ipv6.rst:370 +msgid "Neutron's Distributed Router feature and IPv6" +msgstr "" + +#: ../adv_config_ipv6.rst:372 +msgid "" +"IPv6 does work when the Distributed Virtual Router functionality is enabled, " +"but all ingress/egress traffic is via the centralized router (hence, not " +"distributed). More work is required to fully enable this functionality." +msgstr "" + +#: ../adv_config_ipv6.rst:378 +msgid "Advanced services" +msgstr "" + +#: ../adv_config_ipv6.rst:383 +msgid "" +"VPNaaS supports IPv6, but support in Kilo and prior releases will have some " +"bugs that may limit how it can be used. More thorough and complete testing " +"and bug fixing is being done as part of the Liberty release. IPv6-based VPN " +"as a service is configured similar to the IPv4 configuration. Either or both " +"the ``peer_address`` and the ``peer_cidr`` can specified as an IPv6 address. " +"The choice of addressing modes and router modes described above should not " +"impact support." +msgstr "" + +#: ../adv_config_ipv6.rst:396 +msgid "TODO" +msgstr "" + +#: ../adv_config_ipv6.rst:401 +msgid "FWaaS allows creation of IPv6 based rules." +msgstr "" + +#: ../adv_config_ipv6.rst:404 +msgid "NAT & Floating IPs" +msgstr "" + +#: ../adv_config_ipv6.rst:406 +msgid "" +"At the current time OpenStack Networking does not provide any facility to " +"support any flavor of NAT with IPv6. Unlike IPv4 there is no current " +"embedded support for floating IPs with IPv6. It is assumed that the IPv6 " +"addressing amongst the tenants are using GUAs with no overlap across the " +"tenants." +msgstr "" + +#: ../adv_config_ipv6.rst:413 +msgid "Security considerations" +msgstr "" + +#: ../adv_config_ipv6.rst:419 +msgid "Configuring interfaces of the guest" +msgstr "" + +#: ../adv_config_ipv6.rst:421 +msgid "" +"OpenStack currently doesn't support the privacy extensions defined by RFC " +"4941. The interface identifier and DUID used must be directly derived from " +"the MAC as described in RFC 2373. The compute hosts must not be setup to " +"utilize the privacy extensions when generating their interface identifier." +msgstr "" + +#: ../adv_config_ipv6.rst:426 +msgid "" +"There is no provisions for an IPv6-based metadata service similar to what is " +"provided for IPv4. In the case of dual stack Guests though it is always " +"possible to use the IPv4 metadata service instead." +msgstr "" + +#: ../adv_config_ipv6.rst:430 +msgid "" +"Unlike IPv4 the MTU of a given network can be conveyed in the RA messages " +"sent by the router and not in the DHCP messages. In Kilo the MTU sent by " +"RADVD is always 1500, but in Liberty changes are planned to allow the RA to " +"send the proper MTU of the network." +msgstr "" + +#: ../adv_config_ipv6.rst:436 +msgid "OpenStack control & management network considerations" +msgstr "" + +#: ../adv_config_ipv6.rst:438 +msgid "" +"As of the Kilo release, considerable effort has gone in to ensuring the " +"tenant network can handle dual stack IPv6 and IPv4 transport across the " +"variety of configurations describe above. This same level of scrutiny has " +"not been apply to running the OpenStack control network in a dual stack " +"configuration. Similarly, little scrutiny has gone into ensuring that the " +"OpenStack API endpoints can be accessed via an IPv6 network. At this time, " +"Open vSwitch (OVS) tunnel types - STT, VXLAN, GRE, only support IPv4 " +"endpoints, not IPv6, so a full IPv6-only deployment is not possible with " +"that technology." +msgstr "" + +#: ../adv_config_ipv6.rst:450 +msgid "Prefix delegation" +msgstr "" + +#: ../adv_config_ipv6.rst:452 +msgid "" +"From the Liberty release onwards, OpenStack Networking supports IPv6 prefix " +"delegation. This section describes the configuration and workflow steps " +"necessary to use IPv6 prefix delegation to provide automatic allocation of " +"subnet CIDRs. This allows you as the OpenStack administrator to rely on an " +"external (to the OpenStack Networking service) DHCPv6 server to manage your " +"tenant network prefixes." +msgstr "" + +#: ../adv_config_ipv6.rst:460 +msgid "" +"Prefix delegation will be in the upcoming Liberty release, it is not " +"available in the current OpenStack Kilo release. HA and DVR routers are not " +"currently supported by this feature." +msgstr "" + +#: ../adv_config_ipv6.rst:465 +msgid "Configuring OpenStack Networking for prefix delegation" +msgstr "" + +#: ../adv_config_ipv6.rst:467 +msgid "To enable prefix delegation, edit the :file:`etc/neutron.conf` file::" +msgstr "" + +#: ../adv_config_ipv6.rst:473 +msgid "" +"If you are not using the default dibbler-based driver for prefix delegation, " +"then you also need to set the driver in :file:`etc/neutron.conf`::" +msgstr "" + +#: ../adv_config_ipv6.rst:479 +msgid "" +"Drivers other than the default one may require extra configuration, please " +"refer to :ref:`extra-driver-conf`" +msgstr "" + +#: ../adv_config_ipv6.rst:482 +msgid "" +"This tells OpenStack Networking to use the prefix delegation mechanism for " +"subnet allocation when the user does not provide a CIDR or subnet pool id " +"when creating a subnet." +msgstr "" + +#: ../adv_config_ipv6.rst:487 +msgid "Requirements" +msgstr "" + +#: ../adv_config_ipv6.rst:489 +msgid "" +"To use this feature, you need a prefix delegation capable DHCPv6 server that " +"is reachable from your OpenStack Networking node(s). This could be software " +"running on the OpenStack Networking node(s) or elsewhere, or a physical " +"router. For the purposes of this guide we are using the open-source DHCPv6 " +"server, Dibbler. Dibbler is available in many Linux package managers, or " +"from source at https://github.com/tomaszmrugalski/dibbler." +msgstr "" + +#: ../adv_config_ipv6.rst:496 +msgid "" +"When using the reference implementation of the OpenStack Networking prefix " +"delegation driver, Dibbler must also be installed on your OpenStack " +"Networking node(s) to serve as a DHCPv6 client. Version 1.0.1 or higher is " +"required." +msgstr "" + +#: ../adv_config_ipv6.rst:500 +msgid "" +"This guide assumes that you are running a Dibbler server on the network node " +"where the external network bridge exists. If you already have a prefix " +"delegation capable DHCPv6 server in place, then you can skip the following " +"section." +msgstr "" + +#: ../adv_config_ipv6.rst:506 +msgid "Configuring the Dibbler server" +msgstr "" + +#: ../adv_config_ipv6.rst:508 +msgid "" +"After installing Dibbler, edit the :file:`/etc/dibbler/server.conf` file:" +msgstr "" + +#: ../adv_config_ipv6.rst:521 +msgid "The options used in the configuration file above are:" +msgstr "" + +#: ../adv_config_ipv6.rst:523 +msgid "" +":code:`script`: Points to a script to be run when a prefix is delegated or " +"released. This is only needed if you want instances on your subnets to have " +"external network access. More on this below." +msgstr "" + +#: ../adv_config_ipv6.rst:526 +msgid "" +":code:`iface`: The name of the network interface on which to listen for " +"prefix delegation messages." +msgstr "" + +#: ../adv_config_ipv6.rst:528 +msgid "" +":code:`pd-pool`: The larger prefix from which you want your delegated " +"prefixes to come. The example given is sufficient if you do not need " +"external network access, otherwise a unique globally routable prefix is " +"necessary." +msgstr "" + +#: ../adv_config_ipv6.rst:532 +msgid "" +":code:`pd-length`: The length that delegated prefixes will be. This must be " +"64 to work with the current OpenStack Networking reference implementation." +msgstr "" + +#: ../adv_config_ipv6.rst:535 +msgid "" +"To provide external network access to your instances, your Dibbler server " +"also needs to create new routes for each delegated prefix. This is done " +"using the script file named in the config file above. Edit the :file:`/var/" +"lib/dibbler/pd-server.sh` file:" +msgstr "" + +#: ../adv_config_ipv6.rst:551 +msgid "The variables used in the script file above are:" +msgstr "" + +#: ../adv_config_ipv6.rst:553 +msgid ":code:`$PREFIX1`: The prefix being added/deleted by the Dibbler server." +msgstr "" + +#: ../adv_config_ipv6.rst:554 +msgid ":code:`$1`: The operation being performed." +msgstr "" + +#: ../adv_config_ipv6.rst:555 +msgid ":code:`$REMOTE_ADDR`: The IP address of the requesting Dibbler client." +msgstr "" + +#: ../adv_config_ipv6.rst:556 +msgid "" +":code:`$IFACE`: The network interface upon which the request was received." +msgstr "" + +#: ../adv_config_ipv6.rst:559 +msgid "" +"The above is all you need in this scenario, but more information on " +"installing, configuring, and running Dibbler is available in the Dibbler " +"user guide, at http://klub.com.pl/dhcpv6/doc/dibbler-user.pdf." +msgstr "" + +#: ../adv_config_ipv6.rst:563 +msgid "To start your Dibbler server, run::" +msgstr "" + +#: ../adv_config_ipv6.rst:567 +msgid "Or to run in headless mode::" +msgstr "" + +#: ../adv_config_ipv6.rst:571 +msgid "" +"When using DevStack, it is important to start your server after the :file:" +"`stack.sh` script has finished to ensure that the required network " +"interfaces have been created." +msgstr "" + +# #-#-#-#-# adv_config_ipv6.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# adv_config_qos.pot (Networking Guide 0.9) #-#-#-#-# +#: ../adv_config_ipv6.rst:576 ../adv_config_qos.rst:98 +msgid "User workflow" +msgstr "" + +#: ../adv_config_ipv6.rst:578 +msgid "First, create a network and IPv6 subnet:" +msgstr "" + +#: ../adv_config_ipv6.rst:620 +msgid "" +"The subnet is initially created with a temporary CIDR before one can be " +"assigned by prefix delegation. Any number of subnets with this temporary " +"CIDR can exist without raising an overlap error. The subnetpool_id is " +"automatically set to :code:`prefix_delegation`." +msgstr "" + +#: ../adv_config_ipv6.rst:625 +msgid "" +"To trigger the prefix delegation process, create a router interface between " +"this subnet and a router with an active interface on the external network:" +msgstr "" + +#: ../adv_config_ipv6.rst:635 +msgid "" +"The prefix delegation mechanism then sends a request via the external " +"network to your prefix delegation server, which replies with the delegated " +"prefix. The subnet is then updated with the new prefix, including issuing " +"new IP addresses to all ports:" +msgstr "" + +#: ../adv_config_ipv6.rst:663 +msgid "" +"If the prefix delegation server is configured to delegate globally routable " +"prefixes and setup routes, then any instance with a port on this subnet " +"should now have external network access." +msgstr "" + +#: ../adv_config_ipv6.rst:667 +msgid "" +"Deleting the router interface causes the subnet to be reverted to the " +"temporary CIDR, and all ports have their IPs updated. Prefix leases are " +"released and renewed automatically as necessary." +msgstr "" + +#: ../adv_config_ipv6.rst:672 +msgid "References" +msgstr "" + +#: ../adv_config_ipv6.rst:674 +msgid "" +"The following link provides a great step by step tutorial on setting up IPv6 " +"with OpenStack: http://www.debug-all.com/?p=52" +msgstr "" + +#: ../adv_config_ipv6.rst:680 +msgid "Extra configuration" +msgstr "" + +#: ../adv_config_ipv6.rst:683 +msgid "Neutron dhcpv6_pd_agent" +msgstr "" + +#: ../adv_config_ipv6.rst:684 +msgid "" +"To enable the driver for the dhcpv6_pd_agent, set pd_dhcp_driver to this in :" +"file:`etc/neutron.conf`::" +msgstr "" + +#: ../adv_config_ipv6.rst:689 +msgid "" +"To allow the neutron-pd-agent to communicate with prefix delegation servers, " +"you must set which network interface to use for external communication. In " +"DevStack the default for this is br-ex::" +msgstr "" + +#: ../adv_config_ipv6.rst:695 +msgid "" +"Once you have stacked run the command below to start the neutron-pd-agent::" +msgstr "" + +#: ../adv_config_operational.rst:3 +msgid "Operational" +msgstr "" + +#: ../adv_config_operational.rst:8 +msgid "Logging" +msgstr "" + +#: ../adv_config_operational.rst:10 +msgid "" +"http://docs.openstack.org/admin-guide-cloud/networking_adv-operational-" +"features.html#logging-settings" +msgstr "" + +#: ../adv_config_qos.rst:3 +msgid "Using OpenStack Networking with QoS" +msgstr "" + +#: ../adv_config_qos.rst:5 +msgid "" +"This page serves as a guide for how to use the \"Quality of Service\" (QoS) " +"functionality of OpenStack Networking." +msgstr "" + +#: ../adv_config_qos.rst:8 +msgid "" +"QoS is defined as the ability to guarantee certain network requirements like " +"bandwidth, latency, jitter, and reliability in order to satisfy a Service " +"Level Agreement (SLA) between an application provider and end users." +msgstr "" + +#: ../adv_config_qos.rst:13 +msgid "" +"Network devices such as switches and routers can mark traffic so that it is " +"handled with a higher priority to fulfill the QoS conditions agreed under " +"the SLA. In other cases, certain network traffic such as Voice over IP " +"(VoIP) and video streaming needs to be transmitted with minimal bandwidth " +"constraints. On a system without network QoS management, all traffic will be " +"transmitted in a \"best-effort\" manner making it impossible to guarantee " +"service delivery to customers." +msgstr "" + +#: ../adv_config_qos.rst:25 +msgid "" +"QoS is an advanced service plug-in. QoS is decoupled from the rest of the " +"Neutron code on multiple levels and it is available through the ml2 " +"extension driver." +msgstr "" + +#: ../adv_config_qos.rst:29 +msgid "" +"Details about the DB models, API extension, and use cases are out of the " +"scope of this guide but can be found here: `qos spec `" +msgstr "" + +#: ../adv_config_qos.rst:35 +msgid "Supported QoS rule types" +msgstr "" + +#: ../adv_config_qos.rst:37 +msgid "" +"Any plug-in or ml2 mechanism driver can claim support for some QoS rule " +"types by providing a plug-in/driver class property called " +"'supported_qos_rule_types' that returns a list of strings that correspond to " +"QoS rule types: ``" +msgstr "" + +#: ../adv_config_qos.rst:43 +msgid "" +"For the Liberty release only egress bandwidth limit rules are supported." +msgstr "" + +#: ../adv_config_qos.rst:45 +msgid "" +"In the most simple case, the property can be represented by a simple Python " +"list defined on the class." +msgstr "" + +#: ../adv_config_qos.rst:48 +msgid "" +"For an ml2 plug-in, the list of supported QoS rule types is defined as a " +"common subset of rules supported by all active mechanism drivers." +msgstr "" + +#: ../adv_config_qos.rst:52 +msgid "" +"The list of supported rule types reported by core plug-in is not enforced " +"when accessing QoS rule resources. This is mostly because then we would not " +"be able to create any rules while at least one ml2 driver lacks support for " +"QoS (at the moment of writing, linuxbridge is such a driver)." +msgstr "" + +# #-#-#-#-# adv_config_qos.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# config.pot (Networking Guide 0.9) #-#-#-#-# +#: ../adv_config_qos.rst:60 ../config.rst:3 +msgid "Configuration" +msgstr "" + +#: ../adv_config_qos.rst:62 +msgid "To enable the service, follow the steps below:" +msgstr "" + +#: ../adv_config_qos.rst:64 +msgid "On server side:" +msgstr "" + +#: ../adv_config_qos.rst:66 +msgid "Enable ``qos`` service in ``service_plugins``." +msgstr "" + +#: ../adv_config_qos.rst:67 +msgid "" +"Set the needed notification_drivers in [qos] section (message_queue is the " +"default)." +msgstr "" + +#: ../adv_config_qos.rst:69 +msgid "For ml2, add 'qos' to extension_drivers in [ml2] section." +msgstr "" + +#: ../adv_config_qos.rst:71 +msgid "On agent side (OVS):" +msgstr "" + +#: ../adv_config_qos.rst:73 +msgid "Add 'qos' to extensions in [agent] section." +msgstr "" + +#: ../adv_config_qos.rst:76 +msgid "" +"QoS currently works with ml2 only (SR-IOV and Open vSwitch are the only " +"drivers that are enabled for QoS in Liberty release)." +msgstr "" + +#: ../adv_config_qos.rst:80 +msgid "Trusted tenants policy.json configuration" +msgstr "" + +#: ../adv_config_qos.rst:82 +msgid "" +"If tenants are trusted to administrate their own QoS policies in your cloud, " +"neutron's file :file:`policy.json` can be modified to allow this." +msgstr "" + #: ../adv_config_qos.rst:86 msgid "" "\"get_policy\": \"rule:regular_user\", \"create_policy\": \"rule:regular_user" @@ -27,402 +1251,57 @@ msgid "" "\"get_rule_type\": \"rule:regular_user\"," msgstr "" -#: ../scenario_dvr_ovs.rst:606 -msgid "(Optional) Reduce MTU for GRE/VXLAN project networks." +#: ../adv_config_qos.rst:95 +msgid "Modify ``/etc/neutron/policy.json`` policy entries as follows::" msgstr "" -# #-#-#-#-# scenario_l3ha_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# -#: ../scenario_l3ha_lb.rst:332 ../scenario_legacy_lb.rst:651 -msgid "(Optional) Reduce MTU for VXLAN project networks." -msgstr "" - -# #-#-#-#-# scenario_l3ha_ovs.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../scenario_l3ha_ovs.rst:342 ../scenario_legacy_ovs.rst:752 -msgid "(Optional) Reduce MTU for VXLAN/GRE project networks." -msgstr "" - -#: ../adv_config_ipv6.rst:161 ../adv_config_ipv6.rst:166 -#: ../adv_config_ipv6.rst:171 ../adv_config_ipv6.rst:176 -#: ../adv_config_ipv6.rst:181 ../adv_config_ipv6.rst:186 -msgid "*Invalid combination.*" -msgstr "" - -#: ../adv_config_ipv6.rst:104 ../adv_config_ipv6.rst:105 -#: ../adv_config_ipv6.rst:109 ../adv_config_ipv6.rst:114 -#: ../adv_config_ipv6.rst:119 ../adv_config_ipv6.rst:125 -#: ../adv_config_ipv6.rst:130 ../adv_config_ipv6.rst:135 -msgid "*N/S*" -msgstr "" - -#: ../intro_network_address_translation.rst:5 +#: ../adv_config_qos.rst:100 msgid "" -"*Network Address Translation* (NAT) is a process for modifying the source or " -"destination addresses in the headers of an IP packet while the packet is in " -"transit. In general, the sender and receiver applications are not aware that " -"the IP packets are being manipulated." +"QoS policies are only created by admins with the default ``policy.json``. " +"Therefore, you should have the Cloud Operator to set up them on behalf of " +"the Cloud tenants." msgstr "" -# #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../deploy_scenario4b.rst:153 ../scenario_legacy_lb.rst:191 -#: ../scenario_legacy_ovs.rst:200 ../scenario_provider_ovs.rst:154 +#: ../adv_config_qos.rst:104 msgid "" -"*North-south* network traffic travels between an instance and external " -"network, typically the Internet. *East-west* network traffic travels between " -"instances." +"If tenants are trusted to create their own policies, check the trusted " +"tenants ``policy.json`` configuration section." msgstr "" -#: ../intro_basic_networking.rst:190 +#: ../adv_config_qos.rst:107 +msgid "First, create a QoS policy and its bandwidth limit rules:" +msgstr "" + +#: ../adv_config_qos.rst:136 msgid "" -"*To: everybody (ff:ff:ff:ff:ff:ff). I am looking for the computer who has IP " -"address 192.168.1.7. Signed: MAC address fc:99:47:49:d4:a0*." +"Second, associate the created policy with an existing neutron port. In order " +"to do this, user extracts the port id to be associated to the already " +"created policy. In the next example, we will assign the ``bw-limiter`` " +"policy to the VM with IP address 10.0.0.3" msgstr "" -#: ../intro_basic_networking.rst:195 +#: ../adv_config_qos.rst:155 msgid "" -"*To: fc:99:47:49:d4:a0. I have IP address 192.168.1.7. Signed: MAC address " -"54:78:1a:86:00:a5.*" +"In order to detach a port from the QoS policy, simply update again the port " +"configuration." msgstr "" -#: ../adv_config_ipv6.rst:117 ../adv_config_ipv6.rst:131 -#: ../adv_config_ipv6.rst:146 -msgid "0,1,1" +#: ../adv_config_qos.rst:164 +msgid "Ports can be created with a policy attached to them too." msgstr "" -#: ../adv_config_ipv6.rst:112 ../adv_config_ipv6.rst:126 -#: ../adv_config_ipv6.rst:141 -msgid "1,0,0" -msgstr "" - -#: ../adv_config_ipv6.rst:122 ../adv_config_ipv6.rst:136 -#: ../adv_config_ipv6.rst:152 -msgid "1,0,1" -msgstr "" - -#: ../adv_config_ipv6.rst:554 -msgid ":code:`$1`: The operation being performed." -msgstr "" - -#: ../adv_config_ipv6.rst:556 +#: ../adv_config_qos.rst:194 msgid "" -":code:`$IFACE`: The network interface upon which the request was received." +"You can attach networks to a QoS policy. The meaning of this is that any " +"compute port connected to the network will use the network policy by default " +"unless the port has a specific policy attached to it. Network owned ports " +"like dhcp and router ports are excluded from network policy application." msgstr "" -#: ../adv_config_ipv6.rst:553 -msgid ":code:`$PREFIX1`: The prefix being added/deleted by the Dibbler server." -msgstr "" - -#: ../adv_config_ipv6.rst:555 -msgid ":code:`$REMOTE_ADDR`: The IP address of the requesting Dibbler client." -msgstr "" - -#: ../adv_config_ipv6.rst:526 +#: ../adv_config_qos.rst:199 msgid "" -":code:`iface`: The name of the network interface on which to listen for " -"prefix delegation messages." -msgstr "" - -#: ../adv_config_ipv6.rst:532 -msgid "" -":code:`pd-length`: The length that delegated prefixes will be. This must be " -"64 to work with the current OpenStack Networking reference implementation." -msgstr "" - -#: ../adv_config_ipv6.rst:528 -msgid "" -":code:`pd-pool`: The larger prefix from which you want your delegated " -"prefixes to come. The example given is sufficient if you do not need " -"external network access, otherwise a unique globally routable prefix is " -"necessary." -msgstr "" - -#: ../adv_config_ipv6.rst:523 -msgid "" -":code:`script`: Points to a script to be run when a prefix is delegated or " -"released. This is only needed if you want instances on your subnets to have " -"external network access. More on this below." -msgstr "" - -#: ../index.rst:45 -msgid ":ref:`search`" -msgstr "" - -#: ../intro_basic_networking.rst:380 -msgid "" -"A TCP server is said to *listen* on a port. For example, an SSH server " -"typically listens on port 22. For a client to connect to a server using TCP, " -"the client must know both the IP address of a server's host and the server's " -"TCP port." -msgstr "" - -#: ../intro_tunnel_technologies.rst:21 -msgid "" -"A VXLAN, virtual extensible local area network, allows the creation of a " -"logical network for virtual machines across various networks. VXLAN " -"encapsulates layer-2 Ethernet frames over layer-4 UDP packets." -msgstr "" - -#: ../intro_os_networking_overview.rst:107 -msgid "" -"A block of IP addresses and associated configuration state. This is also " -"known as the native IPAM (IP Address Management) provided by the networking " -"service for both tenant and provider networks. Subnets are used to allocate " -"IP addresses when new ports are created on a network." -msgstr "" - -#: ../intro_networking_components.rst:24 -msgid "" -"A firewall is a network device that controls the incoming and outgoing " -"network traffic based on an applied rule set." -msgstr "" - -# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../scenario_legacy_lb.rst:34 ../scenario_legacy_ovs.rst:34 -msgid "" -"A flat network essentially uses the untagged or native VLAN. Similar to " -"layer-2 properties of physical networks, only one flat network can exist per " -"external bridge. In most cases, production deployments should use VLAN " -"transport for external networks." -msgstr "" - -#: ../intro_basic_networking.rst:282 -msgid "" -"A host sending a packet to an IP address consults its *routing table* to " -"determine which machine on the local network(s) the packet should be sent " -"to. The routing table maintains a list of the subnets associated with each " -"local network that the host is directly connected to, as well as a list of " -"routers that are on these local networks." -msgstr "" - -#: ../intro_networking_components.rst:30 -msgid "" -"A load balancer is a network device that distributes network or application " -"traffic across a number of servers." -msgstr "" - -#: ../intro_network_namespaces.rst:5 -msgid "" -"A namespace is a way of scoping a particular set of identifiers. Using a " -"namespace, you can use the same identifier multiple times in different " -"namespaces. You can also restrict an identifier set visible to particular " -"processes." -msgstr "" - -#: ../intro_os_networking_overview.rst:116 -msgid "" -"A port is a connection point for attaching a single device, such as the NIC " -"of a virtual server, to a virtual network. Also describes the associated " -"network configuration, such as the MAC and IP addresses to be used on that " -"port." -msgstr "" - -# #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../deploy_scenario4b.rst:260 ../scenario_provider_ovs.rst:274 -msgid "" -"A router (4) routes the packet from provider network 1 to provider network 2." -msgstr "" - -#: ../scenario_provider_ovs.rst:212 -msgid "" -"A router (4) routes the packet from provider network 1 to the external " -"network." -msgstr "" - -#: ../deploy_scenario4b.rst:202 -msgid "" -"A router (4) routes the packet from the provider network to the external " -"network." -msgstr "" - -#: ../intro_networking_components.rst:16 -msgid "" -"A router is a networking device that connects multiple networks together. " -"Routers are connected to two or more networks. When they receive data " -"packets, they use a routing table to determine which networks to pass the " -"information to." -msgstr "" - -#: ../intro_os_networking_overview.rst:132 -msgid "" -"A security group acts as a virtual firewall for your compute instances to " -"control inbound and outbound traffic. Security groups act at the port level, " -"not the subnet level. Therefore, each port in a subnet could be assigned to " -"a different set of security groups. If you don't specify a particular group " -"at launch time, the instance is automatically assigned to the default " -"security group for that network." -msgstr "" - -# #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../deploy_scenario4b.rst:323 ../scenario_provider_ovs.rst:344 -msgid "A switch (3) forwards the packet from compute node 1 to compute node 2." -msgstr "" - -# #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../deploy_scenario4b.rst:264 ../scenario_provider_ovs.rst:278 -msgid "A switch (3) forwards the packet to compute node 2." -msgstr "" - -# #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../deploy_scenario4b.rst:206 ../scenario_provider_ovs.rst:216 -msgid "A switch (3) forwards the packet to the external network." -msgstr "" - -# #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../deploy_scenario4b.rst:258 ../scenario_provider_ovs.rst:210 -#: ../scenario_provider_ovs.rst:272 -msgid "" -"A switch (3) handles any VLAN tag operations between provider network 1 and " -"the router (4)." -msgstr "" - -#: ../deploy_scenario4b.rst:200 -msgid "" -"A switch (3) handles any VLAN tag operations between the provider network " -"and the router (4)." -msgstr "" - -# #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../deploy_scenario4b.rst:262 ../scenario_provider_ovs.rst:276 -msgid "" -"A switch (3) handles any VLAN tag operations between the router (4) and " -"provider network 2." -msgstr "" - -# #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../deploy_scenario4b.rst:204 ../scenario_provider_ovs.rst:214 -msgid "" -"A switch (3) handles any VLAN tag operations between the router (4) and the " -"external network." -msgstr "" - -#: ../intro_networking_components.rst:8 -msgid "" -"A switch is a device that is used to connect devices on a network. Switches " -"forward packets on to other devices, using packet switching to pass data " -"along only to devices that need to receive it. Switches operate at layer 2 " -"of the OSI model." -msgstr "" - -#: ../intro_os_networking_overview.rst:29 -msgid "API server" -msgstr "" - -#: ../adv_config_sriov.rst:74 -msgid "" -"ARP spoofing filtering is supported since Liberty when using sriov-agent." -msgstr "" - -#: ../index.rst:11 -msgid "Abstract" -msgstr "" - -#: ../intro_os_networking_overview.rst:38 -msgid "" -"Accepts and routes RPC requests between agents to complete API operations. " -"Message queue is used in the ML2 plug-in for RPC between the neutron server " -"and neutron agents that run on each hypervisor, in the ML2 mechanism drivers " -"for :term:`Open vSwitch` and :term:`Linux bridge`." -msgstr "" - -#: ../adv_config_qos.rst:73 -msgid "Add 'qos' to extensions in [agent] section." -msgstr "" - -#: ../adv_config_sriov.rst:209 -msgid "" -"Add ``sriovnicswitch`` as mechanism driver. Edit the file :file:`/etc/" -"neutron/plugins/ml2/ml2_conf.ini`:" -msgstr "" - -#: ../scenario_dvr_ovs.rst:906 -msgid "" -"Add a gateway to the external network for the project network on the router:" -msgstr "" - -# #-#-#-#-# scenario_l3ha_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_l3ha_ovs.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../scenario_l3ha_lb.rst:601 ../scenario_l3ha_ovs.rst:611 -#: ../scenario_legacy_lb.rst:907 ../scenario_legacy_ovs.rst:1010 -msgid "Add a gateway to the external network on the router:" -msgstr "" - -#: ../adv_config_sriov.rst:235 -msgid "" -"Add the newly configured :file:`ml2_conf_sriov.ini` as parameter to the " -"neutron-server daemon. Edit the file :file:`/etc/init/neutron-server.conf`:" -msgstr "" - -# #-#-#-#-# scenario_l3ha_ovs.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../scenario_l3ha_ovs.rst:604 ../scenario_legacy_lb.rst:900 -#: ../scenario_legacy_ovs.rst:1003 -msgid "Add the project subnet as an interface on the router:" -msgstr "" - -#: ../scenario_provider_ovs.rst:462 ../scenario_provider_ovs.rst:525 -msgid "" -"Add the provider network interface as a port on the Open vSwitch provider " -"bridge ``br-provider``:" -msgstr "" - -#: ../misc_add_ha_for_DHCP.rst:3 -msgid "Adding high availability for DHCP" -msgstr "" - -#: ../adv_config_ipv6.rst:308 -msgid "" -"Address and optional information using neutron router and DHCP " -"implementation respectively." -msgstr "" - -#: ../adv_config_ipv6.rst:272 -msgid "" -"Address are assigned using EUI-64, and OpenStack Networking provides routing." -msgstr "" - -#: ../adv_config_ipv6.rst:236 -msgid "Address configuration and optional information using DHCPv6." -msgstr "" - -#: ../adv_config_ipv6.rst:232 -msgid "Address configuration using RA and optional information using DHCPv6." -msgstr "" - -#: ../adv_config_ipv6.rst:229 -msgid "Address configuration using Router Advertisement (RA)." -msgstr "" - -#: ../adv_config_ipv6.rst:219 -msgid "Address modes for ports" -msgstr "" - -#: ../adv_config_ipv6.rst:312 -msgid "Addresses and optional information are assigned using DHCPv6." -msgstr "" - -#: ../adv_config_ipv6.rst:268 -msgid "" -"Addresses are assigned using EUI-64, and an external router will be used for " -"routing." -msgstr "" - -#: ../adv_config_ipv6.rst:205 -msgid "Addresses for subnets" +"In order to attach a QoS policy to a network, update an existing network, or " +"initially create the network attached to the policy." msgstr "" #: ../adv_config_qos.rst:209 @@ -436,35 +1315,233 @@ msgid "" "policy attached to a network or port." msgstr "" -#: ../adv_config.rst:3 -msgid "Advanced configuration" -msgstr "" - -#: ../adv_config_ipv6.rst:378 -msgid "Advanced services" -msgstr "" - -#: ../adv_config_ipv6.rst:508 +#: ../adv_config_qos.rst:215 msgid "" -"After installing Dibbler, edit the :file:`/etc/dibbler/server.conf` file:" +"If the policy is shared, the tenant is able to attach or detach such policy " +"from its own ports and networks." msgstr "" -#: ../adv_config_sriov.rst:315 +#: ../adv_config_qos.rst:220 +msgid "Rule modification" +msgstr "" + +#: ../adv_config_qos.rst:221 msgid "" -"After the configuration is done, you can now launch Instances with neutron " -"SR-IOV ports." +"You can modify rules at runtime. Rule modifications will be propagated to " +"any attached port." msgstr "" -# #-#-#-#-# config_ml2_plug_in.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# intro_os_networking_service.pot (Networking Guide 0.9) #-#-#-#-# -#: ../config_ml2_plug_in.rst:80 ../intro_os_networking_service.rst:22 -msgid "Agents" +#: ../adv_config_service_chaining.rst:3 +msgid "Service chaining" msgstr "" -#: ../intro_os_networking_overview.rst:67 +#: ../adv_config_sriov.rst:3 +msgid "Using SR-IOV functionality" +msgstr "" + +#: ../adv_config_sriov.rst:5 msgid "" -"All instances reside on the same network, which can also be shared with the " -"hosts. No VLAN tagging or other network segregation takes place." +"The purpose of this page is to describe how to enable SR-IOV functionality " +"available in OpenStack (using OpenStack Networking) as of the Juno release. " +"This page serves as a how-to guide on configuring OpenStack Networking and " +"OpenStack Compute to create neutron SR-IOV ports." +msgstr "" + +#: ../adv_config_sriov.rst:13 +msgid "" +"PCI-SIG Single Root I/O Virtualization and Sharing (SR-IOV) specification " +"defines a standardized mechanism to virtualize PCIe devices. The mechanism " +"can virtualize a single PCIe Ethernet controller to appear as multiple PCIe " +"devices. You can directly assign each virtual PCIe device to a VM, bypassing " +"the hypervisor and virtual switch layer. As a result, users are able to " +"achieve low latency and near-line wire speed." +msgstr "" + +#: ../adv_config_sriov.rst:20 +msgid "The following terms are used over the document:" +msgstr "" + +#: ../adv_config_sriov.rst:26 +msgid "Term" +msgstr "" + +#: ../adv_config_sriov.rst:27 +msgid "Definition" +msgstr "" + +#: ../adv_config_sriov.rst:28 +msgid "PF" +msgstr "" + +#: ../adv_config_sriov.rst:29 +msgid "" +"Physical Function. This is the physical ethernet controller that supports SR-" +"IOV." +msgstr "" + +#: ../adv_config_sriov.rst:31 +msgid "VF" +msgstr "" + +#: ../adv_config_sriov.rst:32 +msgid "" +"Virtual Function. This is a virtual PCIe device created from a physical " +"ethernet controller." +msgstr "" + +#: ../adv_config_sriov.rst:36 +msgid "In order to enable SR-IOV, the following steps are required:" +msgstr "" + +#: ../adv_config_sriov.rst:38 ../adv_config_sriov.rst:92 +msgid "Create Virtual Functions (Compute)" +msgstr "" + +#: ../adv_config_sriov.rst:39 +msgid "Whitelist PCI devices in nova-compute (Compute)" +msgstr "" + +#: ../adv_config_sriov.rst:40 ../adv_config_sriov.rst:207 +msgid "Configure neutron-server (Controller)" +msgstr "" + +#: ../adv_config_sriov.rst:41 ../adv_config_sriov.rst:248 +msgid "Configure nova-scheduler (Controller)" +msgstr "" + +#: ../adv_config_sriov.rst:42 ../adv_config_sriov.rst:269 +msgid "Enable neutron sriov-agent (Compute)" +msgstr "" + +#: ../adv_config_sriov.rst:45 +msgid "Neutron sriov-agent" +msgstr "" + +#: ../adv_config_sriov.rst:46 +msgid "There are 2 ways of configuring SR-IOV:" +msgstr "" + +#: ../adv_config_sriov.rst:48 +msgid "With the sriov-agent running on each compute node" +msgstr "" + +#: ../adv_config_sriov.rst:49 +msgid "Without the sriov-agent running on each compute node" +msgstr "" + +#: ../adv_config_sriov.rst:51 +msgid "" +"The sriov-agent allows you to set the admin state of ports and starting from " +"Liberty allows you to control port security (enable and disable " +"spoofchecking) and QoS rate limit settings." +msgstr "" + +#: ../adv_config_sriov.rst:57 +msgid "" +"With the sriov-agent mode is default in Liberty. Without the sriov-agent " +"mode is deprecated in Liberty and removed in Mitaka." +msgstr "" + +#: ../adv_config_sriov.rst:62 +msgid "Known limitations" +msgstr "" + +#: ../adv_config_sriov.rst:64 +msgid "" +"QoS is supported since Liberty, while it has limitations. max_burst_kbps " +"(burst over max_kbps) is not supported. max_kbps is rounded to Mbps." +msgstr "" + +#: ../adv_config_sriov.rst:67 +msgid "" +"Security Group is not supported. the agent is only working with " +"``firewall_driver = neutron.agent.firewall.NoopFirewallDriver``." +msgstr "" + +#: ../adv_config_sriov.rst:69 +msgid "" +"No OpenStack Dashboard integration. Users need to use CLI or API to create " +"neutron SR-IOV ports." +msgstr "" + +#: ../adv_config_sriov.rst:71 +msgid "Live migration is not supported for instances with SR-IOV ports." +msgstr "" + +#: ../adv_config_sriov.rst:74 +msgid "" +"ARP spoofing filtering is supported since Liberty when using sriov-agent." +msgstr "" + +#: ../adv_config_sriov.rst:78 +msgid "Environment example" +msgstr "" + +#: ../adv_config_sriov.rst:79 +msgid "" +"We recommend using Open vSwitch with VLAN as segration. This way you can " +"combine normal VMs without SR-IOV ports and instances with SR-IOV ports on a " +"single neutron network." +msgstr "" + +#: ../adv_config_sriov.rst:85 +msgid "" +"Throughout this guide, eth3 is used as the PF and physnet2 is used as the " +"provider network configured as a VLAN range. You are expected to change this " +"according to your actual environment." +msgstr "" + +#: ../adv_config_sriov.rst:93 +msgid "" +"In this step, create the VFs for the network interface that will be used for " +"SR-IOV. Use eth3 as PF, which is also used as the interface for Open vSwitch " +"VLAN and has access to the private networks of all machines." +msgstr "" + +#: ../adv_config_sriov.rst:99 +msgid "" +"The step to create VFs differ between SR-IOV card ethernet controller " +"manufacturers. Currently the following manufacturers are known to work:" +msgstr "" + +#: ../adv_config_sriov.rst:102 +msgid "Intel" +msgstr "" + +#: ../adv_config_sriov.rst:103 +msgid "Mellanox" +msgstr "" + +#: ../adv_config_sriov.rst:104 +msgid "QLogic" +msgstr "" + +#: ../adv_config_sriov.rst:106 +msgid "" +"For **Mellanox SR-IOV ethernet cards** see: `Mellanox: HowTo Configure SR-" +"IOV VFs `_" +msgstr "" + +#: ../adv_config_sriov.rst:110 +msgid "" +"To create the VFs on Ubuntu for **Intel SR-IOV ethernet cards**, do the " +"following:" +msgstr "" + +#: ../adv_config_sriov.rst:113 +msgid "" +"Make sure SR-IOV is enabled in BIOS, check for VT-d and make sure it is " +"enabled. After enabling VT-d, enable IOMMU on Linux by adding " +"``intel_iommu=on`` to kernel parameters. Edit the file :file:`/etc/default/" +"grub`:" +msgstr "" + +#: ../adv_config_sriov.rst:122 +msgid "Run the following if you have added new parameters:" +msgstr "" + +#: ../adv_config_sriov.rst:129 +msgid "On each compute node, create the VFs via the PCI SYS interface:" msgstr "" #: ../adv_config_sriov.rst:135 @@ -474,49 +1551,191 @@ msgid "" "deprecated so the PCI SYS interface is the preferred method." msgstr "" +#: ../adv_config_sriov.rst:139 +msgid "" +"Now verify that the VFs have been created (Should see Virtual Function " +"device):" +msgstr "" + +#: ../adv_config_sriov.rst:146 +msgid "Persist created VFs on reboot:" +msgstr "" + +#: ../adv_config_sriov.rst:154 +msgid "" +"The suggested way of making PCI SYS settings persistent is through :file:" +"`sysfs.conf` but for unknown reason changing :file:`sysfs.conf` does not " +"have any effect on Ubuntu 14.04." +msgstr "" + +#: ../adv_config_sriov.rst:158 +msgid "" +"For **QLogic SR-IOV ethernet cards** see: `User's Guide OpenStack Deployment " +"with SR-IOV Configuration `_" +msgstr "" + +#: ../adv_config_sriov.rst:164 +msgid "Whitelist PCI devices nova-compute (Compute)" +msgstr "" + +#: ../adv_config_sriov.rst:166 +msgid "" +"Tell nova-compute which pci devices are allowed to be passed through. Edit " +"the file :file:`/etc/nova/nova.conf`:" +msgstr "" + +#: ../adv_config_sriov.rst:174 +msgid "" +"This tells nova that all VFs belonging to eth3 are allowed to be passed " +"through to VMs and belong to the neutron provider network physnet2. Restart " +"nova compute with :command:`service nova-compute restart` to let the changes " +"have effect." +msgstr "" + #: ../adv_config_sriov.rst:179 msgid "" "Alternatively the ``pci_passthrough_whitelist`` parameter also supports " "whitelisting by:" msgstr "" -#: ../misc_libvirt.rst:77 +#: ../adv_config_sriov.rst:182 msgid "" -"Although OpenStack does not make use of libvirt's networking, this " -"networking will not interfere with OpenStack's behavior, and can be safely " -"left enabled. However, libvirt's networking can be a nuisance when debugging " -"OpenStack networking issues. Because libvirt creates an additional bridge, " -"dnsmasq process, and iptables ruleset, these may distract an operator " -"engaged in network troubleshooting. Unless you need to start up virtual " -"machines using libvirt directly, you can safely disable libvirt's network." +"PCI address: The address uses the same syntax as in ``lspci`` and an " +"asterisk (*) can be used to match anything." msgstr "" -#: ../scenario_legacy_lb.rst:220 ../scenario_legacy_lb.rst:317 +#: ../adv_config_sriov.rst:192 msgid "" -"Although the diagram shows both VXLAN and VLAN project networks, the packet " -"flow only considers one instance using a VXLAN project network." +"PCI ``vendor_id`` and ``product_id`` as displayed by the Linux utility " +"``lspci``." msgstr "" -#: ../intro_network_namespaces.rst:38 +#: ../adv_config_sriov.rst:201 msgid "" -"Any given Linux process runs in a particular network namespace. By default " -"this is inherited from its parent process, but a process with the right " -"capabilities can switch itself into a different namespace; in practice this " -"is mostly done using the :command:`ip netns exec NETNS COMMAND...` " -"invocation, which starts ``COMMAND`` running in the namespace named " -"``NETNS``. Suppose such a process sends out a message to IP address A.B.C.D, " -"the effect of the namespace is that A.B.C.D will be looked up in that " -"namespace's routing table, and that will determine the network device that " -"the message is transmitted through." +"If the device defined by the PCI address or devname corresponds to a SR-IOV " +"PF, all VFs under the PF will match the entry. Multiple " +"pci_passthrough_whitelist entries per host are supported." msgstr "" -#: ../adv_config_qos.rst:37 +#: ../adv_config_sriov.rst:209 msgid "" -"Any plug-in or ml2 mechanism driver can claim support for some QoS rule " -"types by providing a plug-in/driver class property called " -"'supported_qos_rule_types' that returns a list of strings that correspond to " -"QoS rule types: ``" +"Add ``sriovnicswitch`` as mechanism driver. Edit the file :file:`/etc/" +"neutron/plugins/ml2/ml2_conf.ini`:" +msgstr "" + +#: ../adv_config_sriov.rst:216 +msgid "" +"Find out the ``vendor_id`` and ``product_id`` of your **VFs** by logging in " +"to your compute node with VFs previously created:" +msgstr "" + +#: ../adv_config_sriov.rst:226 +msgid "" +"Update the :file:`/etc/neutron/plugins/ml2/ml2_conf_sriov.ini` on each " +"controller. In our case the vendor_id is 8086 and the product_id is 10ed. " +"Tell neutron the vendor_id and product_id of the VFs that are supported." +msgstr "" + +#: ../adv_config_sriov.rst:235 +msgid "" +"Add the newly configured :file:`ml2_conf_sriov.ini` as parameter to the " +"neutron-server daemon. Edit the file :file:`/etc/init/neutron-server.conf`:" +msgstr "" + +#: ../adv_config_sriov.rst:244 +msgid "" +"To make the changes have effect, restart the neutron-server service with " +"the :command:`service neutron-server restart`." +msgstr "" + +#: ../adv_config_sriov.rst:250 +msgid "" +"On every controller node running nova-scheduler add PCIDeviceScheduler to " +"the scheduler_default_filters parameter and add a new line for " +"scheduler_available_filters parameter under the [default] section in :file:`/" +"etc/nova/nova.conf`:" +msgstr "" + +#: ../adv_config_sriov.rst:264 +msgid "" +"Now restart the nova-scheduler service with :command:`service nova-scheduler " +"restart`." +msgstr "" + +#: ../adv_config_sriov.rst:272 +msgid "" +"You only need to enable the sriov-agent if you decided to keep " +"``agent_required=True`` in the step `Configure neutron-server " +"(Controller)`_. If you set ``agent_required=False``, you can safely skip " +"this step." +msgstr "" + +#: ../adv_config_sriov.rst:276 +msgid "" +"On each compute node edit the file :file:`/etc/neutron/plugins/ml2/" +"ml2_conf_sriov.ini`:" +msgstr "" + +#: ../adv_config_sriov.rst:289 +msgid "" +"exclude_devices is empty so all the VFs associated with eth3 may be " +"configured by the agent. If you want to exclude specific VFs, add them to " +"the exclude_devices parameter as follows:" +msgstr "" + +#: ../adv_config_sriov.rst:297 +msgid "Test whether the sriov-agent runs successfully:" +msgstr "" + +#: ../adv_config_sriov.rst:303 +msgid "" +"Enable the neutron-sriov-agent to start automatically at system start. If " +"your distribution does not come with a daemon file for your init system, " +"create a daemon configuration file. For example on Ubuntu install the " +"package:" +msgstr "" + +#: ../adv_config_sriov.rst:314 +msgid "Creating instances with SR-IOV ports" +msgstr "" + +#: ../adv_config_sriov.rst:315 +msgid "" +"After the configuration is done, you can now launch Instances with neutron " +"SR-IOV ports." +msgstr "" + +#: ../adv_config_sriov.rst:318 +msgid "" +"Get the id of the neutron network where you want the SR-IOV port to be " +"created:" +msgstr "" + +#: ../adv_config_sriov.rst:325 +msgid "" +"Create the SR-IOV port. We specify vnic_type direct, but other options " +"include macvtap:" +msgstr "" + +#: ../adv_config_sriov.rst:332 +msgid "" +"Create the VM. For the nic we specify the SR-IOV port created in step 2:" +msgstr "" + +#: ../config.rst:5 +msgid "" +"This content currently under development. For general configuration, see the " +"`Configuration Reference `_." +msgstr "" + +#: ../config_ml2_plug_in.rst:3 +msgid "ML2 plug-in" +msgstr "" + +#: ../config_ml2_plug_in.rst:6 +msgid "Overview" msgstr "" # #-#-#-#-# config_ml2_plug_in.pot (Networking Guide 0.9) #-#-#-#-# @@ -536,752 +1755,139 @@ msgstr "" msgid "Architecture" msgstr "" -#: ../intro_basic_networking.rst:61 -msgid "" -"As mentioned earlier, modern Ethernet networks use switches to interconnect " -"the network hosts. A switch is a box of networking hardware with a large " -"number of ports, that forwards Ethernet frames from one connected host to " -"another. When hosts first send frames over the switch, the switch doesn’t " -"know which MAC address is associated with which port. If an Ethernet frame " -"is destined for an unknown MAC address, the switch broadcasts the frame to " -"all ports. The port learns which MAC addresses are at which ports by " -"observing the traffic. Once it knows which MAC address is associated with a " -"port, it can send Ethernet frames to the correct port instead of " -"broadcasting. The switch maintains the mappings of MAC addresses to switch " -"ports in a table called a *forwarding table* or *forwarding information " -"base* (FIB). Switches can be daisy-chained together, and the resulting " -"connection of switches and hosts behaves like a single network." -msgstr "" - -#: ../adv_config_ipv6.rst:48 -msgid "" -"As of Juno, the OpenStack Networking service (neutron) provides two new " -"attributes to the subnet object, which allows users of the API to configure " -"IPv6 subnets." -msgstr "" - -#: ../adv_config_ipv6.rst:438 -msgid "" -"As of the Kilo release, considerable effort has gone in to ensuring the " -"tenant network can handle dual stack IPv6 and IPv4 transport across the " -"variety of configurations describe above. This same level of scrutiny has " -"not been apply to running the OpenStack control network in a dual stack " -"configuration. Similarly, little scrutiny has gone into ensuring that the " -"OpenStack API endpoints can be accessed via an IPv6 network. At this time, " -"Open vSwitch (OVS) tunnel types - STT, VXLAN, GRE, only support IPv4 " -"endpoints, not IPv6, so a full IPv6-only deployment is not possible with " -"that technology." -msgstr "" - -# #-#-#-#-# scenario_dvr_ovs.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_l3ha_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_l3ha_ovs.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../scenario_dvr_ovs.rst:1041 ../scenario_l3ha_lb.rst:900 -#: ../scenario_l3ha_ovs.rst:908 ../scenario_legacy_lb.rst:1031 -#: ../scenario_legacy_ovs.rst:1134 -msgid "Associate the floating IP address with the instance:" -msgstr "" - -#: ../scenario_legacy_ovs.rst:83 -msgid "" -"At least one compute node with three network interfaces: management, project " -"tunnel networks, and VLAN project networks. The Open vSwitch bridge ``br-" -"vlan`` must contain a port on the VLAN interface." -msgstr "" - -#: ../scenario_l3ha_ovs.rst:64 -msgid "" -"At least one compute node with three network interfaces: management, project " -"tunnel networks, and project VLAN networks. The Open vSwitch bridge ``br-" -"vlan`` must contain a port on the VLAN interface." -msgstr "" - -#: ../scenario_legacy_lb.rst:81 -msgid "" -"At least one compute nodes with three network interfaces: management, " -"project tunnel networks, and VLAN project networks." -msgstr "" - -#: ../scenario_dvr_ovs.rst:49 -msgid "" -"At least two compute nodes with four network interfaces: management, project " -"tunnel networks, project VLAN networks, and external (typically the " -"Internet). The Open vSwitch bridge ``br-vlan`` must contain a port on the " -"VLAN interface and the Open vSwitch bridge ``br-ex`` must contain a port on " -"the external interface." -msgstr "" - -#: ../scenario_l3ha_lb.rst:63 -msgid "" -"At least two compute nodes with three network interfaces: management, " -"project tunnel networks, and project VLAN networks." -msgstr "" - -#: ../deploy_scenario4b.rst:69 -msgid "" -"At least two compute nodes with two network interfaces: management and " -"provider. The provider interface connects to a generic network that physical " -"network infrastructure switches/routes to external networks (typically the " -"Internet)." -msgstr "" - -#: ../scenario_provider_ovs.rst:63 -msgid "" -"At least two compute nodes with two network interfaces: management and " -"provider. The provider interface connects to a generic network that the " -"physical network infrastructure switches/routes to external networks " -"(typically the Internet). The Open vSwitch bridge ``br-provider`` must " -"contain a port on the provider network interface." -msgstr "" - -#: ../scenario_l3ha_lb.rst:60 -msgid "" -"At least two network nodes with four network interfaces: management, project " -"tunnel networks, project VLAN networks, and external (typically the " -"Internet)." -msgstr "" - -#: ../adv_config_ipv6.rst:406 -msgid "" -"At the current time OpenStack Networking does not provide any facility to " -"support any flavor of NAT with IPv6. Unlike IPv4 there is no current " -"embedded support for floating IPs with IPv6. It is assumed that the IPv6 " -"addressing amongst the tenants are using GUAs with no overlap across the " -"tenants." -msgstr "" - -#: ../migration_nova_network_to_neutron.rst:105 -msgid "" -"At this moment the Networking DB is the source of truth, but nova-api is the " -"only public read-write API." -msgstr "" - -#: ../migration_nova_network_to_neutron.rst:118 -msgid "" -"At this point, all compute nodes have been migrated, but they are still " -"using the nova-api API and Compute gateways. Finally, enable OpenStack " -"Networking by following these steps:" -msgstr "" - -#: ../scenario_dvr_ovs.rst:899 -msgid "Attach the project network to the router:" -msgstr "" - -#: ../scenario_l3ha_lb.rst:594 -msgid "Attach the project subnet as an interface on the router:" -msgstr "" - -#: ../adv_config_ipv6.rst:321 -msgid "Auto Configuration Flag = 1" -msgstr "" - -#: ../adv_config_ipv6.rst:280 -msgid "Auto Configuration Flag = 1 Managed" -msgstr "" - -#: ../adv_config_ipv6.rst:108 -msgid "Backwards compatibility with pre-Juno IPv6 behavior." -msgstr "" - -#: ../intro_basic_networking.rst:3 -msgid "Basic networking" -msgstr "" - -#: ../intro_basic_networking.rst:374 -msgid "" -"Because a network host may have multiple TCP-based applications running, TCP " -"uses an addressing scheme called *ports* to uniquely identify TCP-based " -"applications. A TCP port is associated with a number in the range 1-65535, " -"and only one application on a host can be associated with a TCP port at a " -"time, a restriction that is enforced by the operating system." -msgstr "" - -#: ../intro_network_address_translation.rst:60 -msgid "" -"Because the NAT router modifies ports as well as IP addresses, this form of " -"SNAT is sometimes referred to as *Port Address Translation* (PAT). It is " -"also sometimes referred to as *NAT overload*." -msgstr "" - -#: ../deploy_scenario4b.rst:23 -msgid "" -"Before OpenStack Networking introduced Distributed Virtual Routers (DVR), " -"all network traffic traversed one or more dedicated network nodes which " -"limited performance and reliability. Physical network infrastructures " -"typically offer better performance and reliability than general-purpose " -"hosts that handle various network operations in software." -msgstr "" - -#: ../scenario_provider_ovs.rst:20 -msgid "" -"Before OpenStack Networking introduced Distributed Virtual Routers (DVR), " -"all network traffic traversed one or more dedicated network nodes, which " -"limited performance and reliability. Physical network infrastructures " -"typically offer better performance and reliability than general-purpose " -"hosts that handle various network operations in software." -msgstr "" - -# #-#-#-#-# scenario_l3ha_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_l3ha_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../scenario_l3ha_lb.rst:673 ../scenario_l3ha_ovs.rst:683 -msgid "Both ``qrouter`` namespaces should use the same UUID." -msgstr "" - -#: ../scenario_legacy_lb.rst:485 -msgid "Both instances use the same VXLAN project network." -msgstr "" - -#: ../scenario_legacy_ovs.rst:549 -msgid "Both instances use the same project network." -msgstr "" - -# #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../deploy_scenario4b.rst:304 ../scenario_provider_ovs.rst:321 -msgid "Both instances use the same provider network." -msgstr "" - -#: ../scenario_dvr_ovs.rst:392 -msgid "Both project networks reside on the same distributed virtual router." -msgstr "" - -# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../scenario_legacy_lb.rst:409 ../scenario_legacy_ovs.rst:415 -msgid "Both project networks reside on the same router." -msgstr "" - -#: ../adv_config_ipv6.rst:195 -msgid "" -"Both the Linux bridge and the Open vSwitch dataplane modules support " -"forwarding IPv6 packets amongst the guests and router ports. Similar to " -"IPv4, there is no special configuration or setup required to enable the " -"dataplane to properly forward packets from the source to the destination " -"using IPv6. Note that these dataplanes will forward Link-local Address (LLA) " -"packets between hosts on the same network just fine without any " -"participation or setup by OpenStack components after the ports are all " -"connected and MAC addresses learned." -msgstr "" - -#: ../migration_nova_network_to_neutron.rst:122 -msgid "" -"Bring up the Networking (l3) nodes. The new routers will have identical MAC" -"+IPs as old Compute gateways so some sort of immediate cutover is possible, " -"except for stateful connections issues such as NAT." -msgstr "" - -#: ../misc_libvirt.rst:35 -msgid "" -"By default, libvirt creates a network named *default*. The details of this " -"network may vary by distribution; on Ubuntu this network involves:" -msgstr "" - -#: ../misc_libvirt.rst:24 -msgid "" -"By default, libvirt's networking functionality is enabled, and libvirt " -"creates a network when the system boots. To implement this network, libvirt " -"leverages some of the same technologies that OpenStack Network does. In " -"particular, libvirt uses:" -msgstr "" - -# #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../deploy_scenario4b.rst:158 ../scenario_provider_ovs.rst:164 -msgid "Case 1: North-south" -msgstr "" - -# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../scenario_legacy_lb.rst:196 ../scenario_legacy_ovs.rst:205 -msgid "Case 1: North-south for instances with a fixed IP address" -msgstr "" - -#: ../scenario_dvr_ovs.rst:182 -msgid "Case 1: North/south for instances with a fixed IP address" -msgstr "" - -# #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../deploy_scenario4b.rst:215 ../scenario_provider_ovs.rst:225 -msgid "Case 2: East-west for instances on different networks" -msgstr "" - -# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../scenario_legacy_lb.rst:292 ../scenario_legacy_ovs.rst:297 -msgid "Case 2: North-south for instances with a floating IP address" -msgstr "" - -#: ../scenario_dvr_ovs.rst:266 -msgid "Case 2: North/south for instances with a floating IP address" -msgstr "" - -# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../scenario_legacy_lb.rst:383 ../scenario_legacy_ovs.rst:389 -msgid "Case 3: East-west for instances on different networks" -msgstr "" - -# #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../deploy_scenario4b.rst:285 ../scenario_provider_ovs.rst:302 -msgid "Case 3: East-west for instances on the same network" -msgstr "" - -#: ../scenario_dvr_ovs.rst:363 -msgid "" -"Case 3: East/west for instances using different networks on the same router" -msgstr "" - -# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../scenario_legacy_lb.rst:465 ../scenario_legacy_ovs.rst:529 -msgid "Case 4: East-west for instances on the same network" -msgstr "" - -#: ../intro_basic_networking.rst:371 -msgid "Client and server exchange data." -msgstr "" - -#: ../intro_basic_networking.rst:370 -msgid "Client connects to server." -msgstr "" - -#: ../intro_basic_networking.rst:372 -msgid "Client or server disconnects." -msgstr "" - -#: ../migration_nova_network_to_neutron.rst:56 -msgid "" -"Compute needs a per-hypervisor \"has_transitioned\" boolean change in the " -"data model to be used during the migration process. This flag is no longer " -"required once the process is complete." -msgstr "" - -#: ../scenario_dvr_ovs.rst:287 -msgid "Compute node" -msgstr "" - -# #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_dvr_ovs.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../deploy_scenario4b.rst:177 ../deploy_scenario4b.rst:230 -#: ../deploy_scenario4b.rst:294 ../scenario_dvr_ovs.rst:201 -#: ../scenario_dvr_ovs.rst:380 ../scenario_legacy_lb.rst:212 -#: ../scenario_legacy_lb.rst:308 ../scenario_legacy_lb.rst:399 -#: ../scenario_legacy_lb.rst:475 ../scenario_legacy_ovs.rst:221 -#: ../scenario_legacy_ovs.rst:313 ../scenario_legacy_ovs.rst:405 -#: ../scenario_legacy_ovs.rst:539 ../scenario_provider_ovs.rst:183 -#: ../scenario_provider_ovs.rst:240 ../scenario_provider_ovs.rst:311 -msgid "Compute node 1" -msgstr "" - -# #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_dvr_ovs.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../deploy_scenario4b.rst:234 ../deploy_scenario4b.rst:298 -#: ../scenario_dvr_ovs.rst:385 ../scenario_legacy_lb.rst:403 -#: ../scenario_legacy_lb.rst:479 ../scenario_legacy_ovs.rst:409 -#: ../scenario_legacy_ovs.rst:543 ../scenario_provider_ovs.rst:244 -#: ../scenario_provider_ovs.rst:315 -msgid "Compute node 2" -msgstr "" - -# #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_dvr_ovs.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_l3ha_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_l3ha_ovs.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../deploy_scenario4b.rst:442 ../scenario_dvr_ovs.rst:642 -#: ../scenario_l3ha_lb.rst:367 ../scenario_l3ha_ovs.rst:378 -#: ../scenario_legacy_lb.rst:686 ../scenario_legacy_ovs.rst:788 -#: ../scenario_provider_ovs.rst:479 -msgid "Compute nodes" -msgstr "" - -#: ../intro_basic_networking.rst:32 -msgid "" -"Conceptually, you can think of an Ethernet network as a single bus that each " -"of the network hosts connects to. In early implementations, an Ethernet " -"network consisted of a single coaxial cable that hosts would tap into to " -"connect to the network. Modern Ethernet networks do not use this approach, " -"and instead each network host connects directly to a network device called a " -"*switch*. Still, this conceptual model is useful, and in network diagrams " -"(including those generated by the OpenStack dashboard) an Ethernet network " -"is often depicted as if it was a single bus. You'll sometimes hear an " -"Ethernet network referred to as a *layer 2 segment*." -msgstr "" - -# #-#-#-#-# adv_config_qos.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# config.pot (Networking Guide 0.9) #-#-#-#-# -#: ../adv_config_qos.rst:60 ../config.rst:3 -msgid "Configuration" -msgstr "" - -#: ../adv_config_ipv6.rst:281 -msgid "Configuration Flag = 0" -msgstr "" - -#: ../config_ml2_plug_in.rst:85 ../config_ml2_plug_in.rst:90 -#: ../config_ml2_plug_in.rst:95 -msgid "Configuration file" -msgstr "" - # #-#-#-#-# config_ml2_plug_in.pot (Networking Guide 0.9) #-#-#-#-# # #-#-#-#-# config_server.pot (Networking Guide 0.9) #-#-#-#-# #: ../config_ml2_plug_in.rst:12 ../config_server.rst:9 msgid "Configuration file organization, relationships, etc." msgstr "" -# #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_dvr_ovs.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_l3ha_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_l3ha_ovs.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../deploy_scenario4b.rst:372 ../deploy_scenario4b.rst:458 -#: ../scenario_dvr_ovs.rst:468 ../scenario_dvr_ovs.rst:548 -#: ../scenario_dvr_ovs.rst:662 ../scenario_l3ha_lb.rst:199 -#: ../scenario_l3ha_lb.rst:274 ../scenario_l3ha_lb.rst:385 -#: ../scenario_l3ha_ovs.rst:208 ../scenario_l3ha_ovs.rst:286 -#: ../scenario_l3ha_ovs.rst:396 ../scenario_legacy_lb.rst:529 -#: ../scenario_legacy_lb.rst:598 ../scenario_legacy_lb.rst:704 -#: ../scenario_legacy_ovs.rst:624 ../scenario_legacy_ovs.rst:696 -#: ../scenario_legacy_ovs.rst:806 ../scenario_provider_ovs.rst:395 -#: ../scenario_provider_ovs.rst:495 +#: ../config_ml2_plug_in.rst:15 +msgid "Network type drivers" +msgstr "" + +# #-#-#-#-# config_ml2_plug_in.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# intro_os_networking_overview.pot (Networking Guide 0.9) #-#-#-#-# +#: ../config_ml2_plug_in.rst:17 ../intro_os_networking_overview.rst:68 +msgid "Flat" +msgstr "" + +# #-#-#-#-# config_ml2_plug_in.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# intro_os_networking_overview.pot (Networking Guide 0.9) #-#-#-#-# +#: ../config_ml2_plug_in.rst:19 ../config_ml2_plug_in.rst:33 +#: ../intro_os_networking_overview.rst:76 +msgid "VLAN" +msgstr "" + +#: ../config_ml2_plug_in.rst:21 ../config_ml2_plug_in.rst:37 +msgid "GRE" +msgstr "" + +#: ../config_ml2_plug_in.rst:23 ../config_ml2_plug_in.rst:41 +msgid "VXLAN" +msgstr "" + +#: ../config_ml2_plug_in.rst:26 +msgid "Tenant network types" +msgstr "" + +#: ../config_ml2_plug_in.rst:28 msgid "" -"Configure common options. Edit the :file:`/etc/neutron/neutron.conf` file:" +"Similar info in: http://docs.openstack.org/admin-guide-cloud/networking_adv-" +"features.html#provider-networks" msgstr "" -#: ../adv_config_sriov.rst:40 ../adv_config_sriov.rst:207 -msgid "Configure neutron-server (Controller)" +#: ../config_ml2_plug_in.rst:31 +msgid "Local" msgstr "" -#: ../adv_config_sriov.rst:41 ../adv_config_sriov.rst:248 -msgid "Configure nova-scheduler (Controller)" +#: ../config_ml2_plug_in.rst:35 ../config_ml2_plug_in.rst:43 +msgid "ID ranges" msgstr "" -# #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_dvr_ovs.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_l3ha_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_l3ha_ovs.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../deploy_scenario4b.rst:424 ../scenario_dvr_ovs.rst:594 -#: ../scenario_l3ha_lb.rst:320 ../scenario_l3ha_ovs.rst:330 -#: ../scenario_legacy_lb.rst:639 ../scenario_legacy_ovs.rst:740 -#: ../scenario_provider_ovs.rst:441 -msgid "" -"Configure the DHCP agent. Edit the :file:`/etc/neutron/dhcp_agent.ini` file:" +#: ../config_ml2_plug_in.rst:39 +msgid "Tunnel ID ranges" msgstr "" -# #-#-#-#-# scenario_dvr_ovs.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_l3ha_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_l3ha_ovs.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../scenario_dvr_ovs.rst:578 ../scenario_dvr_ovs.rst:692 -#: ../scenario_l3ha_lb.rst:304 ../scenario_l3ha_ovs.rst:314 -#: ../scenario_legacy_lb.rst:628 ../scenario_legacy_ovs.rst:725 -msgid "" -"Configure the L3 agent. Edit the :file:`/etc/neutron/l3_agent.ini` file:" +#: ../config_ml2_plug_in.rst:45 +msgid "Multicast discovery (L2 population)" msgstr "" -# #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_l3ha_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# -#: ../deploy_scenario4b.rst:465 ../scenario_l3ha_lb.rst:281 -#: ../scenario_l3ha_lb.rst:392 ../scenario_legacy_lb.rst:605 -#: ../scenario_legacy_lb.rst:711 -msgid "" -"Configure the Linux bridge agent. Edit the :file:`/etc/neutron/plugins/ml2/" -"ml2_conf.ini` file:" +#: ../config_ml2_plug_in.rst:48 +msgid "Mechanism" msgstr "" -#: ../deploy_scenario4b.rst:386 -msgid "" -"Configure the ML2 plug-in and Linux bridge agent. Edit the :file:`/etc/" -"neutron/plugins/ml2/ml2_conf.ini` file:" +#: ../config_ml2_plug_in.rst:50 +msgid "Linux bridge" msgstr "" -#: ../scenario_provider_ovs.rst:409 -msgid "" -"Configure the ML2 plug-in and Open vSwitch agent. Edit the :file:`/etc/" -"neutron/plugins/ml2/ml2_conf.ini` file:" -msgstr "" - -# #-#-#-#-# scenario_dvr_ovs.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_l3ha_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_l3ha_ovs.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../scenario_dvr_ovs.rst:485 ../scenario_l3ha_lb.rst:215 -#: ../scenario_l3ha_ovs.rst:224 ../scenario_legacy_lb.rst:539 -#: ../scenario_legacy_ovs.rst:634 -msgid "" -"Configure the ML2 plug-in. Edit the :file:`/etc/neutron/plugins/ml2/ml2_conf." -"ini` file:" +#: ../config_ml2_plug_in.rst:52 ../config_ml2_plug_in.rst:56 +msgid "Option stanza/section" msgstr "" +# #-#-#-#-# config_ml2_plug_in.pot (Networking Guide 0.9) #-#-#-#-# # #-#-#-#-# scenario_dvr_ovs.pot (Networking Guide 0.9) #-#-#-#-# # #-#-#-#-# scenario_l3ha_ovs.pot (Networking Guide 0.9) #-#-#-#-# # #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# # #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../scenario_dvr_ovs.rst:555 ../scenario_dvr_ovs.rst:669 -#: ../scenario_l3ha_ovs.rst:293 ../scenario_l3ha_ovs.rst:403 -#: ../scenario_legacy_ovs.rst:703 ../scenario_legacy_ovs.rst:813 -#: ../scenario_provider_ovs.rst:502 -msgid "" -"Configure the Open vSwitch agent. Edit the :file:`/etc/neutron/plugins/ml2/" -"ml2_conf.ini` file:" +#: ../config_ml2_plug_in.rst:54 ../scenario_dvr_ovs.rst:635 +#: ../scenario_dvr_ovs.rst:722 ../scenario_l3ha_ovs.rst:371 +#: ../scenario_l3ha_ovs.rst:426 ../scenario_legacy_ovs.rst:781 +#: ../scenario_legacy_ovs.rst:837 ../scenario_provider_ovs.rst:454 +#: ../scenario_provider_ovs.rst:517 +msgid "Open vSwitch" msgstr "" -# #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../deploy_scenario4b.rst:358 ../deploy_scenario4b.rst:444 -#: ../scenario_provider_ovs.rst:381 ../scenario_provider_ovs.rst:481 -msgid "" -"Configure the kernel to disable reverse path filtering. Edit the :file:`/etc/" -"sysctl.conf` file:" +#: ../config_ml2_plug_in.rst:58 +msgid "L2 population" msgstr "" -# #-#-#-#-# scenario_l3ha_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_l3ha_ovs.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../scenario_l3ha_lb.rst:369 ../scenario_l3ha_ovs.rst:380 -#: ../scenario_legacy_lb.rst:688 ../scenario_legacy_ovs.rst:790 -msgid "" -"Configure the kernel to enable *iptables* on bridges and disable reverse " -"path filtering. Edit the :file:`/etc/sysctl.conf` file:" +#: ../config_ml2_plug_in.rst:60 +msgid "Specialized" msgstr "" -# #-#-#-#-# scenario_dvr_ovs.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_l3ha_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_l3ha_ovs.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../scenario_dvr_ovs.rst:533 ../scenario_l3ha_lb.rst:259 -#: ../scenario_l3ha_ovs.rst:271 ../scenario_legacy_lb.rst:583 -#: ../scenario_legacy_ovs.rst:681 -msgid "" -"Configure the kernel to enable packet forwarding and disable reverse path " -"filtering. Edit the :file:`/etc/sysctl.conf` file:" +#: ../config_ml2_plug_in.rst:62 +msgid "Open source" msgstr "" -#: ../scenario_dvr_ovs.rst:644 -msgid "" -"Configure the kernel to enable packet forwarding, enable *iptables* on " -"bridges, and disable reverse path filtering. Edit the :file:`/etc/sysctl." -"conf` file:" +#: ../config_ml2_plug_in.rst:64 +msgid "Explains that mechanisms such as OpenDaylight and OpenContrail exist" msgstr "" -# #-#-#-#-# scenario_dvr_ovs.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_l3ha_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_l3ha_ovs.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../scenario_dvr_ovs.rst:621 ../scenario_dvr_ovs.rst:708 -#: ../scenario_l3ha_lb.rst:347 ../scenario_l3ha_ovs.rst:357 -#: ../scenario_legacy_lb.rst:666 ../scenario_legacy_ovs.rst:767 -msgid "" -"Configure the metadata agent. Edit the :file:`/etc/neutron/metadata_agent." -"ini` file:" +#: ../config_ml2_plug_in.rst:66 ../config_ml2_plug_in.rst:72 +msgid "Does not cover how to do this" msgstr "" -#: ../adv_config_ipv6.rst:465 -msgid "Configuring OpenStack Networking for prefix delegation" +#: ../config_ml2_plug_in.rst:68 +msgid "Proprietary (vendor)" msgstr "" -#: ../adv_config_ipv6.rst:419 -msgid "Configuring interfaces of the guest" +#: ../config_ml2_plug_in.rst:70 +msgid "Just specifies that these exist" msgstr "" -#: ../adv_config_ipv6.rst:506 -msgid "Configuring the Dibbler server" +#: ../config_ml2_plug_in.rst:75 +msgid "Security" msgstr "" -#: ../scenario_dvr_ovs.rst:480 -msgid "" -"Configuring the ``router_distributed = True`` option creates distributed " -"routers by default for all users. Without it, only privileged users can " -"create distributed routers using the ``--distributed True`` option during " -"router creation." +#: ../config_ml2_plug_in.rst:77 +msgid "Options" msgstr "" -#: ../adv_config_ipv6.rst:39 -msgid "Connection to the OpenStack APIs via an IPv6 transport network" +# #-#-#-#-# config_ml2_plug_in.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# intro_os_networking_service.pot (Networking Guide 0.9) #-#-#-#-# +#: ../config_ml2_plug_in.rst:80 ../intro_os_networking_service.rst:22 +msgid "Agents" msgstr "" -#: ../intro_basic_networking.rst:166 -msgid "" -"Consider an IP address of 192.168.1.5, where the first 24 bits of the " -"address are the network number. In dotted quad notation, the netmask would " -"be written as ``255.255.255.0``. CIDR notation includes both the IP address " -"and netmask, and this example would be written as ``192.168.1.5/24``." +# #-#-#-#-# config_ml2_plug_in.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# intro_os_networking_service.pot (Networking Guide 0.9) #-#-#-#-# +#: ../config_ml2_plug_in.rst:83 ../intro_os_networking_service.rst:47 +msgid "L3" msgstr "" -#: ../index.rst:24 -msgid "Contents" -msgstr "" - -# #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_dvr_ovs.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_l3ha_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_l3ha_ovs.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../deploy_scenario4b.rst:356 ../scenario_dvr_ovs.rst:466 -#: ../scenario_l3ha_lb.rst:197 ../scenario_l3ha_ovs.rst:206 -#: ../scenario_legacy_lb.rst:527 ../scenario_legacy_ovs.rst:622 -#: ../scenario_provider_ovs.rst:379 -msgid "Controller node" -msgstr "" - -#: ../adv_config_sriov.rst:38 ../adv_config_sriov.rst:92 -msgid "Create Virtual Functions (Compute)" -msgstr "" - -#: ../scenario_dvr_ovs.rst:875 -msgid "Create a distributed project router:" -msgstr "" - -# #-#-#-#-# scenario_dvr_ovs.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_l3ha_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_l3ha_ovs.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../scenario_dvr_ovs.rst:1022 ../scenario_l3ha_lb.rst:881 -#: ../scenario_l3ha_ovs.rst:889 ../scenario_legacy_lb.rst:1013 -#: ../scenario_legacy_ovs.rst:1116 -msgid "Create a floating IP address on the external network:" -msgstr "" - -#: ../scenario_l3ha_lb.rst:518 -msgid "Create a project network:" -msgstr "" - -# #-#-#-#-# scenario_l3ha_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_l3ha_ovs.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../scenario_l3ha_lb.rst:569 ../scenario_l3ha_ovs.rst:579 -#: ../scenario_legacy_lb.rst:883 ../scenario_legacy_ovs.rst:985 -msgid "Create a project router:" -msgstr "" - -# #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../deploy_scenario4b.rst:513 ../scenario_provider_ovs.rst:564 -msgid "Create a provider network:" -msgstr "" - -# #-#-#-#-# scenario_dvr_ovs.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_l3ha_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_l3ha_ovs.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../scenario_dvr_ovs.rst:780 ../scenario_l3ha_lb.rst:472 -#: ../scenario_l3ha_ovs.rst:482 ../scenario_legacy_lb.rst:787 -#: ../scenario_legacy_ovs.rst:889 -msgid "Create a subnet on the external network:" -msgstr "" - -# #-#-#-#-# scenario_dvr_ovs.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_l3ha_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_l3ha_ovs.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../scenario_dvr_ovs.rst:850 ../scenario_l3ha_lb.rst:544 -#: ../scenario_l3ha_ovs.rst:554 ../scenario_legacy_lb.rst:858 -#: ../scenario_legacy_ovs.rst:960 -msgid "Create a subnet on the project network:" -msgstr "" - -# #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../deploy_scenario4b.rst:540 ../scenario_provider_ovs.rst:591 -msgid "Create a subnet on the provider network:" -msgstr "" - -# #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_dvr_ovs.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_l3ha_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_l3ha_ovs.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../deploy_scenario4b.rst:507 ../scenario_dvr_ovs.rst:752 -#: ../scenario_l3ha_lb.rst:444 ../scenario_l3ha_ovs.rst:454 -#: ../scenario_legacy_lb.rst:759 ../scenario_legacy_ovs.rst:861 -#: ../scenario_provider_ovs.rst:558 -msgid "Create initial networks" -msgstr "" - -#: ../scenario_provider_ovs.rst:456 ../scenario_provider_ovs.rst:519 -msgid "Create the Open vSwitch provider bridge ``br-provider``:" -msgstr "" - -#: ../adv_config_sriov.rst:325 -msgid "" -"Create the SR-IOV port. We specify vnic_type direct, but other options " -"include macvtap:" -msgstr "" - -#: ../adv_config_sriov.rst:332 -msgid "" -"Create the VM. For the nic we specify the SR-IOV port created in step 2:" -msgstr "" - -# #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_dvr_ovs.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_l3ha_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_l3ha_ovs.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../deploy_scenario4b.rst:580 ../scenario_dvr_ovs.rst:1003 -#: ../scenario_l3ha_lb.rst:792 ../scenario_l3ha_ovs.rst:800 -#: ../scenario_legacy_lb.rst:994 ../scenario_legacy_ovs.rst:1097 -#: ../scenario_provider_ovs.rst:631 -msgid "" -"Create the appropriate security group rules to allow ping and SSH access to " -"the instance. For example:" -msgstr "" - -# #-#-#-#-# scenario_dvr_ovs.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_l3ha_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_l3ha_ovs.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../scenario_dvr_ovs.rst:757 ../scenario_l3ha_lb.rst:449 -#: ../scenario_l3ha_ovs.rst:459 ../scenario_legacy_lb.rst:764 -#: ../scenario_legacy_ovs.rst:866 -msgid "Create the external network:" -msgstr "" - -# #-#-#-#-# scenario_dvr_ovs.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_l3ha_ovs.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../scenario_dvr_ovs.rst:826 ../scenario_l3ha_ovs.rst:528 -#: ../scenario_legacy_lb.rst:833 ../scenario_legacy_ovs.rst:935 -msgid "Create the project network:" -msgstr "" - -#: ../adv_config_sriov.rst:314 -msgid "Creating instances with SR-IOV ports" +#: ../config_ml2_plug_in.rst:85 ../config_ml2_plug_in.rst:90 +#: ../config_ml2_plug_in.rst:95 +msgid "Configuration file" msgstr "" # #-#-#-#-# config_ml2_plug_in.pot (Networking Guide 0.9) #-#-#-#-# @@ -1292,1041 +1898,57 @@ msgstr "" msgid "DHCP" msgstr "" +# #-#-#-#-# config_ml2_plug_in.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# intro_os_networking_service.pot (Networking Guide 0.9) #-#-#-#-# +#: ../config_ml2_plug_in.rst:93 ../intro_os_networking_service.rst:58 +msgid "Metadata" +msgstr "" + +# #-#-#-#-# config_server.pot (Networking Guide 0.9) #-#-#-#-# # #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# intro_os_networking_service.pot (Networking Guide 0.9) #-#-#-#-# # #-#-#-#-# scenario_dvr_ovs.pot (Networking Guide 0.9) #-#-#-#-# # #-#-#-#-# scenario_l3ha_lb.pot (Networking Guide 0.9) #-#-#-#-# # #-#-#-#-# scenario_l3ha_ovs.pot (Networking Guide 0.9) #-#-#-#-# # #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# # #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# # #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../deploy_scenario4b.rst:439 ../scenario_dvr_ovs.rst:638 -#: ../scenario_l3ha_lb.rst:363 ../scenario_l3ha_ovs.rst:374 -#: ../scenario_legacy_lb.rst:682 ../scenario_legacy_ovs.rst:784 -#: ../scenario_provider_ovs.rst:476 -msgid "DHCP agent" +#: ../config_server.rst:3 ../deploy_scenario4b.rst:437 +#: ../intro_os_networking_service.rst:6 ../scenario_dvr_ovs.rst:528 +#: ../scenario_l3ha_lb.rst:254 ../scenario_l3ha_ovs.rst:266 +#: ../scenario_legacy_lb.rst:578 ../scenario_legacy_ovs.rst:676 +#: ../scenario_provider_ovs.rst:474 +msgid "Server" msgstr "" -#: ../scenario_dvr_ovs.rst:127 -msgid "" -"DHCP agent managing the ``qdhcp`` namespaces. The ``dhcp`` namespaces " -"provide DHCP services for instances using project networks." -msgstr "" - -# #-#-#-#-# scenario_l3ha_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_l3ha_ovs.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../scenario_l3ha_lb.rst:134 ../scenario_l3ha_ovs.rst:141 -#: ../scenario_legacy_lb.rst:161 ../scenario_legacy_ovs.rst:167 -msgid "" -"DHCP agent managing the ``qdhcp`` namespaces. The ``qdhcp`` namespaces " -"provide DHCP services for instances using project networks." -msgstr "" - -# #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../deploy_scenario4b.rst:120 ../scenario_provider_ovs.rst:116 -msgid "" -"DHCP agent managing the ``qdhcp`` namespaces. The ``qdhcp`` namespaces " -"provide DHCP services for instances using provider networks." -msgstr "" - -#: ../misc_add_ha_for_DHCP.rst:8 -msgid "DHCP agents" -msgstr "" - -#: ../intro_basic_networking.rst:230 -msgid "" -"DHCP clients locate the DHCP server by sending a UDP_ packet from port 68 to " -"address ``255.255.255.255`` on port 67. Address ``255.255.255.255`` is the " -"local network broadcast address: all hosts on the local network see the UDP " -"packets sent to this address. However, such packets are not forwarded to " -"other networks. Consequently, the DHCP server must be on the same local " -"network as the client, or the server will not receive the broadcast. The " -"DHCP server responds by sending a UDP packet from port 67 to port 68 on the " -"client. The exchange looks like this:" -msgstr "" - -#: ../intro_basic_networking.rst:441 -msgid "" -"DHCP_, the Domain Name System (DNS), the Network Time Protocol (NTP), and :" -"ref:`VXLAN` are examples of UDP-based protocols used in OpenStack " -"deployments." -msgstr "" - -#: ../adv_config_ipv6.rst:294 -msgid "DHCPv6" -msgstr "" - -#: ../adv_config_ipv6.rst:236 ../adv_config_ipv6.rst:310 -#: ../adv_config_ipv6.rst:311 -msgid "DHCPv6-stateful" -msgstr "" - -#: ../adv_config_ipv6.rst:233 ../adv_config_ipv6.rst:306 -#: ../adv_config_ipv6.rst:307 -msgid "DHCPv6-stateless" -msgstr "" - -#: ../intro_network_address_translation.rst:68 -msgid "DNAT" -msgstr "" - -#: ../scenario_dvr_ovs.rst:204 ../scenario_dvr_ovs.rst:291 -#: ../scenario_dvr_ovs.rst:383 -msgid "DVR MAC address *D1*" -msgstr "" - -#: ../scenario_dvr_ovs.rst:388 -msgid "DVR MAC address *D2*" -msgstr "" - -#: ../scenario_dvr_ovs.rst:292 -msgid "DVR internal IP addresses *DA1* and *DA2*" -msgstr "" - -#: ../adv_config_ipv6.rst:193 -msgid "Dataplane" -msgstr "" - -#: ../misc_libvirt.rst:97 -msgid "" -"Deactivating the network will remove the ``virbr0`` bridge, terminate the " -"dnsmasq process, and remove the iptables rules." -msgstr "" - -#: ../adv_config_debugging.rst:3 -msgid "Debugging" -msgstr "" - -#: ../adv_config_debugging.rst:39 -msgid "Debugging DHCP Issues" -msgstr "" - -#: ../adv_config_debugging.rst:44 -msgid "Debugging DNS Issues" -msgstr "" - -#: ../scenario_dvr_ovs.rst:896 -msgid "" -"Default policy might prevent the '`distributed`` flag from appearing in the " -"command output for non-privileged users." -msgstr "" - -#: ../adv_config_sriov.rst:27 -msgid "Definition" -msgstr "" - -#: ../adv_config_ipv6.rst:667 -msgid "" -"Deleting the router interface causes the subnet to be reverted to the " -"temporary CIDR, and all ports have their IPs updated. Prefix leases are " -"released and renewed automatically as necessary." +#: ../config_server.rst:12 +msgid "Reference common configuration items" msgstr "" #: ../deploy.rst:3 msgid "Deployment scenarios" msgstr "" -#: ../adv_config_ipv6.rst:103 -msgid "Description" +#: ../deploy_scenario4b.rst:3 +msgid "Scenario: Provider networks with Linux bridge" msgstr "" -#: ../adv_config_qos.rst:29 +#: ../deploy_scenario4b.rst:5 msgid "" -"Details about the DB models, API extension, and use cases are out of the " -"scope of this guide but can be found here: `qos spec `" +"This scenario describes a provider networks implementation of the OpenStack " +"Networking service using the ML2 plug-in with Linux bridge." msgstr "" # #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# # #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../deploy_scenario4b.rst:641 ../scenario_provider_ovs.rst:692 -msgid "" -"Determine the IP address of the instance. The following step uses " -"203.0.113.3." -msgstr "" - -# #-#-#-#-# scenario_dvr_ovs.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_l3ha_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_l3ha_ovs.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../scenario_dvr_ovs.rst:931 ../scenario_l3ha_lb.rst:758 -#: ../scenario_l3ha_ovs.rst:766 ../scenario_legacy_lb.rst:929 -#: ../scenario_legacy_ovs.rst:1032 -msgid "" -"Determine the external network gateway IP address for the project network on " -"the router, typically the lowest IP address in the external subnet IP " -"allocation range:" -msgstr "" - -#: ../adv_config_ipv6.rst:209 -msgid "Direct assignment during subnet creation via command line or Horizon" -msgstr "" - -#: ../migration_nova_network_to_neutron.rst:112 -msgid "Disable nova-compute." -msgstr "" - -#: ../migration_nova_network_to_neutron.rst:110 -msgid "" -"Disable the hypervisor. This would be a good time to live migrate or " -"evacuate the compute node, if supported." -msgstr "" - -#: ../misc_libvirt.rst:3 -msgid "Disabling libvirt networking" -msgstr "" - -#: ../config_ml2_plug_in.rst:66 ../config_ml2_plug_in.rst:72 -msgid "Does not cover how to do this" -msgstr "" - -#: ../adv_config_ipv6.rst:479 -msgid "" -"Drivers other than the default one may require extra configuration, please " -"refer to :ref:`extra-driver-conf`" -msgstr "" - -#: ../scenario_l3ha_ovs.rst:33 -msgid "" -"Due to a bug in the Juno (initial) and Kilo releases, VXLAN and GRE project " -"networks must use multicast instead of the layer-2 population mechanism." -msgstr "" - -# #-#-#-#-# scenario_dvr_ovs.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_l3ha_ovs.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../scenario_dvr_ovs.rst:168 ../scenario_l3ha_ovs.rst:163 -#: ../scenario_provider_ovs.rst:137 -msgid "" -"Due to limitations with Open vSwitch and *iptables*, the Networking service " -"uses a Linux bridge to manage security groups for instances." -msgstr "" - -# #-#-#-#-# scenario_l3ha_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_l3ha_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../scenario_l3ha_lb.rst:173 ../scenario_l3ha_ovs.rst:182 -msgid "" -"During normal operation, the master router periodically transmits " -"*heartbeat* packets over a hidden project network that connects all HA " -"routers for a particular project. By default, this network uses the type " -"indicated by the first value in the ``tenant_network_types`` option in the :" -"file:`/etc/neutron/plugins/ml2_conf.ini` file." -msgstr "" - -#: ../migration_nova_network_to_neutron.rst:83 -msgid "" -"During the migration, nova-network API calls will go through an additional " -"internal conversion to Networking calls. This will have different and likely " -"poorer performance characteristics compared with either the pre-migration or " -"post-migration APIs." -msgstr "" - -#: ../intro_network_namespaces.rst:27 -msgid "" -"Each network namespace also has its own routing table, and in fact this is " -"the main reason for namespaces to exist. A routing table is keyed by " -"destination IP address, so network namespaces are what you need if you want " -"the same destination IP address to mean different things at different times " -"- which is something that OpenStack Networking requires for its feature of " -"providing overlapping IP addresses in different virtual networks." -msgstr "" - -#: ../intro_network_namespaces.rst:34 -msgid "" -"Each network namespace also has its own set of iptables (for both IPv4 and " -"IPv6). So, you can apply different security to flows with the same IP " -"addressing in different namespaces, as well as different routing." -msgstr "" - -# #-#-#-#-# scenario_dvr_ovs.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_l3ha_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_l3ha_ovs.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../scenario_dvr_ovs.rst:608 ../scenario_l3ha_lb.rst:334 -#: ../scenario_l3ha_ovs.rst:344 ../scenario_legacy_lb.rst:653 -#: ../scenario_legacy_ovs.rst:754 -msgid "Edit the :file:`/etc/neutron/dhcp_agent.ini` file:" -msgstr "" - -# #-#-#-#-# scenario_dvr_ovs.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_l3ha_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_l3ha_ovs.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../scenario_dvr_ovs.rst:615 ../scenario_l3ha_lb.rst:341 -#: ../scenario_l3ha_ovs.rst:351 ../scenario_legacy_lb.rst:660 -#: ../scenario_legacy_ovs.rst:761 -msgid "Edit the :file:`/etc/neutron/dnsmasq-neutron.conf` file:" -msgstr "" - -#: ../adv_config_ipv6.rst:358 -msgid "" -"Effectively the ``ipv6_gateway`` flag takes precedence over an RA that is " -"received from the upstream router. If it is desired to use a GUA next hop " -"that is accomplished by allocating a subnet to the external router port and " -"assigning the upstream routers GUA address as the gateway for the subnet." -msgstr "" - -#: ../adv_config_qos.rst:66 -msgid "Enable ``qos`` service in ``service_plugins``." -msgstr "" - -#: ../migration_nova_network_to_neutron.rst:96 -msgid "" -"Enable a nova-api proxy that recreates internal Compute objects from " -"Networking information (via the Networking REST API)." -msgstr "" - -#: ../adv_config_sriov.rst:42 ../adv_config_sriov.rst:269 -msgid "Enable neutron sriov-agent (Compute)" -msgstr "" - -#: ../migration_nova_network_to_neutron.rst:113 -msgid "Enable the Networking agent." -msgstr "" - -#: ../adv_config_sriov.rst:303 -msgid "" -"Enable the neutron-sriov-agent to start automatically at system start. If " -"your distribution does not come with a daemon file for your init system, " -"create a daemon configuration file. For example on Ubuntu install the " -"package:" -msgstr "" - -#: ../adv_config_sriov.rst:78 -msgid "Environment example" -msgstr "" - -#: ../intro_basic_networking.rst:6 -msgid "Ethernet" -msgstr "" - -#: ../intro_basic_networking.rst:8 -msgid "" -"Ethernet is a networking protocol, specified by the IEEE 802.3 standard. " -"Most wired network interface cards (NICs) communicate using Ethernet." -msgstr "" - -# #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_dvr_ovs.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_l3ha_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_l3ha_ovs.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../deploy_scenario4b.rst:345 ../scenario_dvr_ovs.rst:457 -#: ../scenario_l3ha_lb.rst:191 ../scenario_l3ha_ovs.rst:200 -#: ../scenario_legacy_lb.rst:521 ../scenario_legacy_ovs.rst:616 -#: ../scenario_provider_ovs.rst:368 -msgid "Example configuration" -msgstr "" - -#: ../config_ml2_plug_in.rst:64 -msgid "Explains that mechanisms such as OpenDaylight and OpenContrail exist" -msgstr "" - -#: ../intro_os_networking_overview.rst:148 -msgid "Extensions" -msgstr "" - -#: ../adv_config_ipv6.rst:102 -msgid "External Router A,M,O" -msgstr "" - -# #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_dvr_ovs.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../deploy_scenario4b.rst:168 ../scenario_dvr_ovs.rst:188 -#: ../scenario_dvr_ovs.rst:275 ../scenario_legacy_lb.rst:201 -#: ../scenario_legacy_lb.rst:297 ../scenario_legacy_ovs.rst:210 -#: ../scenario_legacy_ovs.rst:302 ../scenario_provider_ovs.rst:174 -msgid "External network" -msgstr "" - -# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../scenario_legacy_lb.rst:24 ../scenario_legacy_ovs.rst:24 -msgid "External networks" -msgstr "" - -# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../scenario_legacy_lb.rst:26 ../scenario_legacy_ovs.rst:26 -msgid "" -"External networks provide connectivity to external networks such as the " -"Internet. Only administrative (privileged) users can manage external " -"networks because they interface with the physical network infrastructure. " -"External networks can use flat or VLAN transport methods depending on the " -"physical network infrastructure and generally use public IP address ranges." -msgstr "" - -#: ../adv_config_ipv6.rst:680 -msgid "Extra configuration" -msgstr "" - -#: ../misc_add_ha_for_DHCP.rst:5 -msgid "FIXME (Simple note, needs to be added.)" -msgstr "" - -#: ../misc_add_ha_for_DHCP.rst:10 -msgid "" -"FIXME: Content needs to be written; see DHCP agents (http://docs.openstack." -"org/admin-guide-cloud/networking_multi-dhcp-agents.html)" -msgstr "" - -# #-#-#-#-# adv_config_FwaaS.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# adv_config_ipv6.pot (Networking Guide 0.9) #-#-#-#-# -#: ../adv_config_FwaaS.rst:3 ../adv_config_ipv6.rst:399 -msgid "FWaaS" -msgstr "" - -#: ../adv_config_ipv6.rst:401 -msgid "FWaaS allows creation of IPv6 based rules." -msgstr "" - -#: ../adv_config_sriov.rst:216 -msgid "" -"Find out the ``vendor_id`` and ``product_id`` of your **VFs** by logging in " -"to your compute node with VFs previously created:" -msgstr "" - -#: ../intro_networking_components.rst:22 -msgid "Firewalls" -msgstr "" - -#: ../adv_config_qos.rst:107 -msgid "First, create a QoS policy and its bandwidth limit rules:" -msgstr "" - -#: ../adv_config_ipv6.rst:578 -msgid "First, create a network and IPv6 subnet:" -msgstr "" - -# #-#-#-#-# config_ml2_plug_in.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# intro_os_networking_overview.pot (Networking Guide 0.9) #-#-#-#-# -#: ../config_ml2_plug_in.rst:17 ../intro_os_networking_overview.rst:68 -msgid "Flat" -msgstr "" - -#: ../scenario_dvr_ovs.rst:192 ../scenario_dvr_ovs.rst:279 -msgid "Floating IP range 203.0.113.101 to 203.0.113.200" -msgstr "" - -#: ../adv_config_sriov.rst:106 -msgid "" -"For **Mellanox SR-IOV ethernet cards** see: `Mellanox: HowTo Configure SR-" -"IOV VFs `_" -msgstr "" - -#: ../adv_config_sriov.rst:158 -msgid "" -"For **QLogic SR-IOV ethernet cards** see: `User's Guide OpenStack Deployment " -"with SR-IOV Configuration `_" -msgstr "" - -#: ../adv_config_ipv6.rst:296 -msgid "" -"For DHCPv6-stateless, the currently supported combinations are as follows:" -msgstr "" - -# #-#-#-#-# scenario_dvr_ovs.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_l3ha_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../scenario_dvr_ovs.rst:70 ../scenario_l3ha_ovs.rst:89 -msgid "" -"For VLAN external and project networks, the network infrastructure must " -"support VLAN tagging. For best performance with VXLAN and GRE project " -"networks, the network infrastructure should support jumbo frames." -msgstr "" - -#: ../scenario_l3ha_lb.rst:86 -msgid "" -"For VLAN external and project networks, the network infrastructure must " -"support VLAN tagging. For best performance with VXLAN project networks, the " -"network infrastructure should support jumbo frames." -msgstr "" - -#: ../scenario_legacy_ovs.rst:108 -msgid "" -"For VLAN external and project networks, the physical network infrastructure " -"must support VLAN tagging. For best performance with VXLAN and GRE project " -"networks, the network infrastructure should support jumbo frames." -msgstr "" - -#: ../scenario_legacy_lb.rst:104 -msgid "" -"For VLAN external and project networks, the physical network infrastructure " -"must support VLAN tagging. For best performance with VXLAN project networks, " -"the network infrastructure should support jumbo frames." -msgstr "" - -# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../scenario_legacy_lb.rst:238 ../scenario_legacy_lb.rst:265 -#: ../scenario_legacy_lb.rst:339 ../scenario_legacy_lb.rst:363 -#: ../scenario_legacy_ovs.rst:239 ../scenario_legacy_ovs.rst:259 -#: ../scenario_legacy_ovs.rst:337 ../scenario_legacy_ovs.rst:357 -#: ../scenario_legacy_ovs.rst:429 ../scenario_legacy_ovs.rst:449 -#: ../scenario_legacy_ovs.rst:477 ../scenario_legacy_ovs.rst:497 -#: ../scenario_legacy_ovs.rst:564 ../scenario_legacy_ovs.rst:584 -msgid "For VLAN project networks:" -msgstr "" - -#: ../scenario_legacy_ovs.rst:248 ../scenario_legacy_ovs.rst:268 -#: ../scenario_legacy_ovs.rst:346 ../scenario_legacy_ovs.rst:366 -#: ../scenario_legacy_ovs.rst:438 ../scenario_legacy_ovs.rst:458 -#: ../scenario_legacy_ovs.rst:486 ../scenario_legacy_ovs.rst:506 -#: ../scenario_legacy_ovs.rst:573 ../scenario_legacy_ovs.rst:593 -msgid "For VXLAN and GRE project networks:" -msgstr "" - -#: ../scenario_legacy_lb.rst:225 ../scenario_legacy_lb.rst:254 -#: ../scenario_legacy_lb.rst:330 ../scenario_legacy_lb.rst:351 -msgid "For VXLAN project networks:" -msgstr "" - -#: ../adv_config_qos.rst:48 -msgid "" -"For an ml2 plug-in, the list of supported QoS rule types is defined as a " -"common subset of rules supported by all active mechanism drivers." -msgstr "" - -#: ../intro_network_namespaces.rst:10 -msgid "" -"For example, Linux provides namespaces for networking and processes, among " -"other things. If a process is running within a process namespace, it can " -"only see and communicate with other processes in the same namespace. So, if " -"a shell in a particular process namespace ran :command:`ps waux`, it would " -"only show the other processes in the same namespace." -msgstr "" - -# #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../deploy_scenario4b.rst:130 ../deploy_scenario4b.rst:146 -#: ../scenario_provider_ovs.rst:126 ../scenario_provider_ovs.rst:147 -msgid "" -"For illustration purposes, the diagram contains two different provider " -"networks." -msgstr "" - -# #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../deploy_scenario4b.rst:59 ../scenario_provider_ovs.rst:52 -msgid "" -"For illustration purposes, the management network uses 10.0.0.0/24 and " -"provider networks use 192.0.2.0/24, 198.51.100.0/24, and 203.0.113.0/24." -msgstr "" - -#: ../scenario_dvr_ovs.rst:131 -msgid "" -"For instances using project networks on legacy routers, the ``qrouter`` " -"namespaces route *north-south* and *east-west* network traffic and perform " -"DNAT/SNAT similar to the legacy scenarios. They also route metadata traffic " -"between instances and the metadata agent." -msgstr "" - -#: ../scenario_dvr_ovs.rst:135 -msgid "" -"For instances with a fixed IP address using project networks on distributed " -"routers, the ``snat`` namespaces perform SNAT for *north-south* network " -"traffic." -msgstr "" - -#: ../scenario_dvr_ovs.rst:184 -msgid "" -"For instances with a fixed IP address using project networks on distributed " -"routers, the network node routes *north-south* network traffic between " -"project and external networks." -msgstr "" - -# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../scenario_legacy_lb.rst:198 ../scenario_legacy_ovs.rst:207 -msgid "" -"For instances with a fixed IP address, the network node routes *north-south* " -"network traffic between project and external networks." -msgstr "" - -#: ../scenario_dvr_ovs.rst:159 -msgid "" -"For instances with a fixed or floating IP address using project networks on " -"distributed routers, the ``qrouter`` namespaces route *east-west* traffic." -msgstr "" - -# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../scenario_legacy_lb.rst:385 ../scenario_legacy_ovs.rst:391 -msgid "" -"For instances with a fixed or floating IP address, the network node routes " -"*east-west* network traffic among project networks using the same project " -"router." -msgstr "" - -# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../scenario_legacy_lb.rst:467 ../scenario_legacy_ovs.rst:531 -msgid "" -"For instances with a fixed or floating IP address, the project network " -"switches *east-west* network traffic among instances without using a project " -"router on the network node." -msgstr "" - -#: ../scenario_dvr_ovs.rst:156 -msgid "" -"For instances with a floating IP address using project networks on " -"distributed routers, the ``fip`` namespaces route *north-south* network " -"traffic and perform DNAT/SNAT." -msgstr "" - -#: ../scenario_dvr_ovs.rst:268 -msgid "" -"For instances with a floating IP address using project networks on " -"distributed routers, the compute node containing the instance routes *north-" -"south* network traffic between project and external networks, avoiding the " -"network node. Given the complexity of this case, the following case covers " -"both the flow of network traffic from the external network to an instance " -"and from an instance to the external network." -msgstr "" - -# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../scenario_legacy_lb.rst:294 ../scenario_legacy_ovs.rst:299 -msgid "" -"For instances with a floating IP address, the network node routes *north-" -"south* network traffic between project and external networks." -msgstr "" - -#: ../scenario_dvr_ovs.rst:365 -msgid "" -"For instances with fixed or floating IP addresses using project networks on " -"distributed routers, the compute nodes route *east-west* network traffic " -"among the project networks that reside on the same distributed virtual " -"router, avoiding the network node." -msgstr "" - -#: ../adv_config_qos.rst:69 -msgid "For ml2, add 'qos' to extension_drivers in [ml2] section." -msgstr "" - -#: ../intro_basic_networking.rst:353 -msgid "" -"For networked software applications to communicate over an IP network, they " -"must use a protocol layered atop IP. These protocols occupy the fourth layer " -"of the OSI model known as the *transport layer* or *layer 4*. See the " -"`Protocol Numbers`_ web page maintained by the Internet Assigned Numbers " -"Authority (IANA) for a list of protocols that layer atop IP and their " -"associated numbers." -msgstr "" - -#: ../scenario_l3ha_lb.rst:149 -msgid "" -"For simplicity, the hidden project network that connects all HA routers for " -"a particular project uses the VXLAN network type." -msgstr "" - -#: ../adv_config_qos.rst:43 -msgid "" -"For the Liberty release only egress bandwidth limit rules are supported." -msgstr "" - -#: ../adv_config_ipv6.rst:250 -msgid "" -"For the above two attributes to be effective, ``enable_dhcp`` must be set to " -"True in file :file:`neutron.conf`." -msgstr "" - -#: ../adv_config_ipv6.rst:452 -msgid "" -"From the Liberty release onwards, OpenStack Networking supports IPv6 prefix " -"delegation. This section describes the configuration and workflow steps " -"necessary to use IPv6 prefix delegation to provide automatic allocation of " -"subnet CIDRs. This allows you as the OpenStack administrator to rely on an " -"external (to the OpenStack Networking service) DHCPv6 server to manage your " -"tenant network prefixes." -msgstr "" - -#: ../intro_os_networking_service.rst:82 -msgid "FwaaS" -msgstr "" - -#: ../config_ml2_plug_in.rst:21 ../config_ml2_plug_in.rst:37 -msgid "GRE" -msgstr "" - -#: ../intro_os_networking_overview.rst:85 -msgid "GRE and VXLAN" -msgstr "" - -#: ../intro_tunnel_technologies.rst:13 -msgid "" -"GRE carries IP packets with private IP addresses over the Internet using " -"delivery packets with public IP addresses." -msgstr "" - -# #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../deploy_scenario4b.rst:175 ../scenario_provider_ovs.rst:181 -msgid "Gateway 192.0.2.1 with MAC address *TG*" -msgstr "" - -# #-#-#-#-# scenario_dvr_ovs.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../scenario_dvr_ovs.rst:199 ../scenario_dvr_ovs.rst:285 -#: ../scenario_legacy_lb.rst:210 ../scenario_legacy_lb.rst:306 -#: ../scenario_legacy_ovs.rst:219 ../scenario_legacy_ovs.rst:311 -msgid "Gateway 192.168.1.1 with MAC address *TG*" -msgstr "" - -#: ../scenario_dvr_ovs.rst:373 -msgid "Gateway 192.168.1.1 with MAC address *TG1*" -msgstr "" - -#: ../scenario_dvr_ovs.rst:378 -msgid "Gateway 192.168.2.1 with MAC address *TG2*" -msgstr "" - -#: ../scenario_dvr_ovs.rst:191 ../scenario_dvr_ovs.rst:278 -msgid "Gateway 203.0.113.1 with MAC address *EG*" -msgstr "" - -# #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../deploy_scenario4b.rst:223 ../scenario_provider_ovs.rst:233 -msgid "Gateway: 192.0.2.1 with MAC address *TG1*" -msgstr "" - -# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../scenario_legacy_lb.rst:392 ../scenario_legacy_ovs.rst:398 -msgid "Gateway: 192.168.1.1 with MAC address *TG1*" -msgstr "" - -# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../scenario_legacy_lb.rst:397 ../scenario_legacy_ovs.rst:403 -msgid "Gateway: 192.168.2.1 with MAC address *TG2*" -msgstr "" - -# #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../deploy_scenario4b.rst:228 ../scenario_provider_ovs.rst:238 -msgid "Gateway: 198.51.100.1 with MAC address *TG2*" -msgstr "" - -#: ../intro_tunnel_technologies.rst:11 -msgid "Generic routing encapsulation (GRE)" -msgstr "" - -#: ../adv_config_sriov.rst:318 -msgid "" -"Get the id of the neutron network where you want the SR-IOV port to be " -"created:" -msgstr "" - -#: ../adv_config_group_policy.rst:3 -msgid "Group policy" -msgstr "" - -#: ../adv_config_ipv6.rst:154 -msgid "" -"Guest instance obtains IPv6 address from OpenStack managed radvd using SLAAC " -"and optional info from dnsmasq using DHCPv6." -msgstr "" - -#: ../adv_config_ipv6.rst:143 -msgid "" -"Guest instance obtains IPv6 address from OpenStack managed radvd using SLAAC." -msgstr "" - -#: ../adv_config_ipv6.rst:148 -msgid "" -"Guest instance obtains IPv6 address from dnsmasq using DHCPv6 stateful and " -"optional info from dnsmasq using DHCPv6." -msgstr "" - -#: ../adv_config_ipv6.rst:113 -msgid "" -"Guest instance obtains IPv6 address from non-OpenStack router using SLAAC." -msgstr "" - -#: ../intro_os_networking_service.rst:31 -msgid "Handles metadata, etc." -msgstr "" - -#: ../intro_os_networking_service.rst:29 -msgid "Handles physical-virtual network transition" -msgstr "" - -#: ../intro_basic_networking.rst:294 -msgid "Here is an example of output from ``ip route show``::" -msgstr "" - -#: ../intro_basic_networking.rst:198 -msgid "Host *A* then sends Ethernet frames to host *B*." -msgstr "" - -#: ../intro_basic_networking.rst:193 -msgid "Host *B* responds with a response like this:" -msgstr "" - -#: ../intro_basic_networking.rst:225 -msgid "" -"Hosts connected to a network use the Dynamic Host Configuration Protocol (:" -"term:`DHCP`) to dynamically obtain IP addresses. A DHCP server hands out the " -"IP addresses to network hosts, which are the DHCP clients." -msgstr "" - -#: ../adv_config_group_policy.rst:9 -msgid "How it differs from legacy neutron data model" -msgstr "" - -#: ../adv_config_ipv6.rst:21 -msgid "" -"How those instances communicate across a router to other subnets or the " -"internet." -msgstr "" - -#: ../adv_config_ipv6.rst:23 -msgid "How those instances interact with other OpenStack services." -msgstr "" - -#: ../adv_config_ipv6.rst:20 -msgid "How those instances receive an IPv6 address." -msgstr "" - -#: ../misc_libvirt.rst:75 -msgid "How to disable libvirt networks" -msgstr "" - -#: ../adv_config_ipv6.rst:19 -msgid "How to enable dual-stack (IPv4 and IPv6 enabled) instances." -msgstr "" - -#: ../misc_libvirt.rst:15 -msgid "" -"However, libvirt is capable of providing networking services to the virtual " -"machines that it manages. In particular, libvirt can be configured to " -"provide networking functionality akin to a simplified, single-node version " -"of OpenStack. Users can use libvirt to create layer 2 networks that are " -"similar to OpenStack Networking's networks, confined to a single node." -msgstr "" - -#: ../intro_basic_networking.rst:391 -msgid "" -"IANA maintains a `registry of port numbers`_ for many TCP-based services, as " -"well as services that use other layer 4 protocols that employ ports. " -"Registering a TCP port number is not required, but registering a port number " -"is helpful to avoid collisions with other services. See `Appendix B. " -"Firewalls and default ports`_ of the `OpenStack Configuration Reference`_ " -"for the default TCP ports used by various services involved in an OpenStack " -"deployment." -msgstr "" - -#: ../config_ml2_plug_in.rst:35 ../config_ml2_plug_in.rst:43 -msgid "ID ranges" -msgstr "" - -#: ../intro_basic_networking.rst:269 -msgid "IP" -msgstr "" - -# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../scenario_legacy_lb.rst:204 ../scenario_legacy_lb.rst:300 -#: ../scenario_legacy_ovs.rst:213 ../scenario_legacy_ovs.rst:305 -msgid "IP address allocation from 203.0.113.101 to 203.0.113.200" -msgstr "" - -#: ../intro_basic_networking.rst:148 -msgid "" -"IP addresses are broken up into two parts: a *network number* and a *host " -"identifier*. Two hosts are on the same *subnet* if they have the same " -"network number. Recall that two hosts can only communicate directly over " -"Ethernet if they are on the same local network. ARP assumes that all " -"machines that are in the same subnet are on the same local network. Network " -"administrators must take care when assigning IP addresses and netmasks to " -"hosts so that any two hosts that are in the same subnet are on the same " -"local network, otherwise ARP does not work properly." -msgstr "" - -#: ../adv_config_ipv6.rst:67 -msgid "IPv6 addressing" -msgstr "" - -#: ../adv_config_ipv6.rst:372 -msgid "" -"IPv6 does work when the Distributed Virtual Router functionality is enabled, " -"but all ingress/egress traffic is via the centralized router (hence, not " -"distributed). More work is required to fully enable this functionality." -msgstr "" - -#: ../adv_config_ipv6.rst:40 -msgid "IPv6 multicast" -msgstr "" - -#: ../adv_config_ipv6.rst:41 -msgid "" -"IPv6 support in conjunction with any out of tree routers, switches, services " -"or agents whether in physical or virtual form factors." -msgstr "" - -#: ../adv_config_ipv6.rst:225 -msgid "" -"IPv6 supports three different addressing schemes for address configuration " -"and for providing optional network information." -msgstr "" - -#: ../adv_config_qos.rst:82 -msgid "" -"If tenants are trusted to administrate their own QoS policies in your cloud, " -"neutron's file :file:`policy.json` can be modified to allow this." -msgstr "" - -#: ../adv_config_qos.rst:104 -msgid "" -"If tenants are trusted to create their own policies, check the trusted " -"tenants ``policy.json`` configuration section." -msgstr "" - -# #-#-#-#-# scenario_l3ha_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_l3ha_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../scenario_l3ha_lb.rst:179 ../scenario_l3ha_ovs.rst:188 -msgid "" -"If the backup router stops receiving these packets, it assumes failure of " -"the master router and promotes itself to the master router by configuring IP " -"addresses on the interfaces in the ``qrouter`` namespace. In environments " -"with more than one backup router, the router with the next highest priority " -"becomes the master router." -msgstr "" - -#: ../adv_config_sriov.rst:201 -msgid "" -"If the device defined by the PCI address or devname corresponds to a SR-IOV " -"PF, all VFs under the PF will match the entry. Multiple " -"pci_passthrough_whitelist entries per host are supported." -msgstr "" - -#: ../adv_config_qos.rst:215 -msgid "" -"If the policy is shared, the tenant is able to attach or detach such policy " -"from its own ports and networks." -msgstr "" - -#: ../adv_config_ipv6.rst:663 -msgid "" -"If the prefix delegation server is configured to delegate globally routable " -"prefixes and setup routes, then any instance with a port on this subnet " -"should now have external network access." -msgstr "" - -#: ../intro_basic_networking.rst:112 -msgid "" -"If two switches are to be connected together, and the switches are " -"configured for VLANs, then the switchports used for cross-connecting the " -"switches must be configured to allow Ethernet frames from any VLAN to be " -"forwarded to the other switch. In addition, the sending switch must tag each " -"Ethernet frame with the VLAN ID so that the receiving switch can ensure that " -"only hosts on the matching VLAN are eligible to receive the frame." -msgstr "" - -#: ../adv_config_ipv6.rst:473 -msgid "" -"If you are not using the default dibbler-based driver for prefix delegation, " -"then you also need to set the driver in :file:`etc/neutron.conf`::" -msgstr "" - -#: ../migration_nova_network_to_neutron.rst:34 -msgid "Impact and limitations" -msgstr "" - -#: ../intro_network_address_translation.rst:70 -msgid "" -"In *Destination Network Address Translation* (DNAT), the NAT router modifies " -"the IP address of the destination in IP packet headers." -msgstr "" - -#: ../intro_network_address_translation.rst:24 -msgid "" -"In *Source Network Address Translation* (SNAT), the NAT router modifies the " -"IP address of the sender in IP packets. SNAT is commonly used to enable " -"hosts with *private addresses* to communicate with servers on the public " -"Internet." -msgstr "" - -#: ../intro_network_address_translation.rst:84 -msgid "" -"In *one-to-one NAT*, the NAT router maintains a one-to-one mapping between " -"private IP addresses and public IP addresses. OpenStack uses one-to-one NAT " -"to implement floating IP addresses." -msgstr "" - -#: ../intro_network_namespaces.rst:19 -msgid "" -"In a network namespace, the scoped 'identifiers' are network devices; so a " -"given network device, such as ``eth0``, exists in a particular namespace. " -"Linux starts up with a default network namespace, so if your operating " -"system does not do anything special, that is where all the network devices " -"will be located. But it is also possible to create further non-default " -"namespaces, and create new devices in those namespaces, or to move an " -"existing device from one namespace to another." -msgstr "" - -#: ../intro_basic_networking.rst:43 -msgid "" -"In an Ethernet network, every host on the network can send a frame directly " -"to every other host. An Ethernet network also supports broadcasts, so that " -"one host can send a frame to every host on the network by sending to the " -"special MAC address ``ff:ff:ff:ff:ff:ff``. ARP_ and DHCP_ are two notable " -"protocols that use Ethernet broadcasts. Because Ethernet networks support " -"broadcasts, you will sometimes hear an Ethernet network referred to as a " -"*broadcast domain*." -msgstr "" - -#: ../intro_basic_networking.rst:16 -msgid "" -"In an Ethernet network, the hosts connected to the network communicate by " -"exchanging *frames*, which is the Ethernet terminology for packets. Every " -"host on an Ethernet network is uniquely identified by an address called the " -"media access control (MAC) address. In particular, in an OpenStack " -"environment, every virtual machine instance has a unique MAC address, which " -"is different from the MAC address of the compute host. A MAC address has 48 " -"bits and is typically represented as a hexadecimal string, such as " -"``08:00:27:b9:88:74``. The MAC address is hard-coded into the NIC by the " -"manufacturer, although modern NICs allow you to change the MAC address " -"programatically. In Linux, you can retrieve the MAC address of a NIC using " -"the ``ip`` command::" -msgstr "" - -#: ../deploy_scenario4b.rst:40 -msgid "" -"In comparison to provider networks with Open vSwitch (OVS), this scenario " -"relies completely on native Linux networking services which makes it the " -"simplest of all scenarios in this guide." -msgstr "" - -# #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../deploy_scenario4b.rst:29 ../scenario_provider_ovs.rst:26 -msgid "" -"In general, the OpenStack Networking software components that handle layer-3 " -"operations impact performance and reliability the most. To improve " -"performance and reliability, provider networks move layer-3 operations to " -"the physical network infrastructure." -msgstr "" - -#: ../scenario_provider_ovs.rst:15 -msgid "" -"In many cases, operators who are already familiar with network architectures " -"that rely on the physical network infrastructure can easily deploy OpenStack " -"Networking on it. Over time, operators can test and implement cloud " -"networking features in their environment." +#: ../deploy_scenario4b.rst:8 ../scenario_provider_ovs.rst:8 +msgid "" +"Provider networks generally offer simplicity, performance, and reliability " +"at the cost of flexibility. Unlike other scenarios, only administrators can " +"manage provider networks because they require configuration of physical " +"network infrastructure. Also, provider networks lack the concept of fixed " +"and floating IP addresses because they only handle layer-2 connectivity for " +"instances." msgstr "" #: ../deploy_scenario4b.rst:15 @@ -2340,6 +1962,25 @@ msgid "" "deployment to enable more cloud networking features." msgstr "" +#: ../deploy_scenario4b.rst:23 +msgid "" +"Before OpenStack Networking introduced Distributed Virtual Routers (DVR), " +"all network traffic traversed one or more dedicated network nodes which " +"limited performance and reliability. Physical network infrastructures " +"typically offer better performance and reliability than general-purpose " +"hosts that handle various network operations in software." +msgstr "" + +# #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../deploy_scenario4b.rst:29 ../scenario_provider_ovs.rst:26 +msgid "" +"In general, the OpenStack Networking software components that handle layer-3 " +"operations impact performance and reliability the most. To improve " +"performance and reliability, provider networks move layer-3 operations to " +"the physical network infrastructure." +msgstr "" + # #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# # #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# #: ../deploy_scenario4b.rst:34 ../scenario_provider_ovs.rst:31 @@ -2351,119 +1992,54 @@ msgid "" "VLANs, to applications outside of the deployment." msgstr "" -#: ../adv_config_qos.rst:199 +#: ../deploy_scenario4b.rst:40 msgid "" -"In order to attach a QoS policy to a network, update an existing network, or " -"initially create the network attached to the policy." +"In comparison to provider networks with Open vSwitch (OVS), this scenario " +"relies completely on native Linux networking services which makes it the " +"simplest of all scenarios in this guide." msgstr "" -#: ../adv_config_qos.rst:155 +# #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../deploy_scenario4b.rst:44 ../scenario_provider_ovs.rst:37 msgid "" -"In order to detach a port from the QoS policy, simply update again the port " -"configuration." -msgstr "" - -#: ../adv_config_sriov.rst:36 -msgid "In order to enable SR-IOV, the following steps are required:" -msgstr "" - -#: ../migration_nova_network_to_neutron.rst:63 -msgid "" -"In order to support a wide range of deployment options, the migration " -"process described here requires a rolling restart of hypervisors. The rate " -"and timing of specific hypervisor restarts is under the control of the " -"operator." -msgstr "" - -#: ../migration_nova_network_to_neutron.rst:75 -msgid "" -"In order to support the widest range of deployer needs, the process " -"described here is easy to automate but is not already automated. Deployers " -"should expect to perform multiple manual steps or write some simple scripts " -"in order to perform this migration." -msgstr "" - -#: ../scenario_l3ha_lb.rst:33 -msgid "" -"In the Juno (initial) and Kilo releases, L3HA with Linux bridge supports " -"VLAN and VXLAN project networks. However, due to a bug, VXLAN project " -"networks must use multicast instead of the layer-2 population mechanism." -msgstr "" - -#: ../scenario_dvr_ovs.rst:23 -msgid "" -"In the Juno (initial) release, DVR supports VXLAN and GRE project networks. " -"In the Kilo release, DVR adds support for VLAN project networks. All " -"releases support flat and VLAN external networks." -msgstr "" - -#: ../intro_basic_networking.rst:278 -msgid "" -"In the OSI model of networking protocols, IP occupies the third layer, which " -"is known as the network layer. When discussing IP, you will often hear terms " -"such as *layer 3*, *L3*, and *network layer*." -msgstr "" - -#: ../intro_basic_networking.rst:11 -msgid "" -"In the `OSI model`_ of networking protocols, Ethernet occupies the second " -"layer, which is known as the data link layer. When discussing Ethernet, you " -"will often hear terms such as *local network*, *layer 2*, *L2*, *link layer* " -"and *data link layer*." -msgstr "" - -#: ../adv_config_ipv6.rst:351 -msgid "" -"In the absence of an upstream RA support, ``ipv6_gateway`` flag can be set " -"with the external router gateway LLA in the neutron L3 agent configuration " -"file. This also requires that no subnet is associated with that port." -msgstr "" - -#: ../scenario_dvr_ovs.rst:55 -msgid "" -"In the example configuration, the management network uses 10.0.0.0/24, the " -"tunnel network uses 10.0.1.0/24, and the external network uses " -"203.0.113.0/24. The VLAN network does not require an IP address range " -"because it only handles layer 2 connectivity." -msgstr "" - -# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../scenario_legacy_lb.rst:89 ../scenario_legacy_ovs.rst:93 -msgid "" -"In the example configuration, the management network uses 10.0.0.0/24, the " -"tunnel network uses 10.0.1.0/24, and the external network uses " -"203.0.113.0/24. The VLAN network does not require an IP address range " -"because it only handles layer-2 connectivity." +"The example configuration creates a VLAN provider network. However, it also " +"supports flat (untagged or native) provider networks." msgstr "" +# #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_dvr_ovs.pot (Networking Guide 0.9) #-#-#-#-# # #-#-#-#-# scenario_l3ha_lb.pot (Networking Guide 0.9) #-#-#-#-# # #-#-#-#-# scenario_l3ha_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../scenario_l3ha_lb.rst:71 ../scenario_l3ha_ovs.rst:74 -msgid "" -"In the example configuration, the management network uses 10.0.0.0/24, the " -"tunnel network uses 10.0.1.0/24, the VRRP network uses 169.254.192.0/18, and " -"the external network uses 203.0.113.0/24. The VLAN network does not require " -"an IP address range because it only handles layer-2 connectivity." +# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../deploy_scenario4b.rst:48 ../scenario_dvr_ovs.rst:28 +#: ../scenario_l3ha_lb.rst:43 ../scenario_l3ha_ovs.rst:42 +#: ../scenario_legacy_lb.rst:63 ../scenario_legacy_ovs.rst:62 +#: ../scenario_provider_ovs.rst:41 +msgid "Prerequisites" msgstr "" -#: ../adv_config_ipv6.rst:212 +#: ../deploy_scenario4b.rst:50 msgid "" -"In the future, different techniques could be used to allocate subnets to " -"tenants:" +"These prerequisites define the minimum physical infrastructure and OpenStack " +"service dependencies that you need to deploy this scenario. For example, the " +"Networking service immediately depends on the Identity service, and the " +"Compute service immediately depends on the Networking service. These " +"dependencies lack services such as the Image service because the Networking " +"service does not immediately depend on it. However, the Compute service " +"depends on the Image service to launch an instance. The example " +"configuration in this scenario assumes basic configuration knowledge of " +"Networking service components." msgstr "" -#: ../adv_config_qos.rst:45 +# #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../deploy_scenario4b.rst:59 ../scenario_provider_ovs.rst:52 msgid "" -"In the most simple case, the property can be represented by a simple Python " -"list defined on the class." -msgstr "" - -#: ../adv_config_sriov.rst:93 -msgid "" -"In this step, create the VFs for the network interface that will be used for " -"SR-IOV. Use eth3 as PF, which is also used as the interface for Open vSwitch " -"VLAN and has access to the private networks of all machines." +"For illustration purposes, the management network uses 10.0.0.0/24 and " +"provider networks use 192.0.2.0/24, 198.51.100.0/24, and 203.0.113.0/24." msgstr "" # #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# @@ -2480,1119 +2056,6 @@ msgstr "" msgid "Infrastructure" msgstr "" -# #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../deploy_scenario4b.rst:179 ../scenario_provider_ovs.rst:185 -msgid "Instance 1 192.0.2.11 with MAC address *I1*" -msgstr "" - -# #-#-#-#-# scenario_dvr_ovs.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../scenario_dvr_ovs.rst:203 ../scenario_dvr_ovs.rst:382 -#: ../scenario_legacy_lb.rst:214 ../scenario_legacy_ovs.rst:223 -msgid "Instance 1 192.168.1.11 with MAC address *I1*" -msgstr "" - -# #-#-#-#-# scenario_dvr_ovs.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../scenario_dvr_ovs.rst:289 ../scenario_legacy_lb.rst:310 -#: ../scenario_legacy_ovs.rst:315 -msgid "" -"Instance 1 192.168.1.11 with MAC address *I1* and floating IP address " -"203.0.113.102 *F1*" -msgstr "" - -#: ../scenario_legacy_lb.rst:407 -msgid "Instance 1 resides on compute node 1 and uses VXLAN project network 1." -msgstr "" - -# #-#-#-#-# scenario_dvr_ovs.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../scenario_dvr_ovs.rst:206 ../scenario_dvr_ovs.rst:294 -#: ../scenario_legacy_lb.rst:216 ../scenario_legacy_lb.rst:313 -#: ../scenario_legacy_ovs.rst:225 ../scenario_legacy_ovs.rst:318 -msgid "Instance 1 resides on compute node 1 and uses a project network." -msgstr "" - -# #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../deploy_scenario4b.rst:181 ../scenario_provider_ovs.rst:187 -msgid "Instance 1 resides on compute node 1 and uses a provider network." -msgstr "" - -# #-#-#-#-# scenario_dvr_ovs.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../scenario_dvr_ovs.rst:390 ../scenario_legacy_ovs.rst:413 -msgid "Instance 1 resides on compute node 1 and uses project network 1." -msgstr "" - -# #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../deploy_scenario4b.rst:238 ../scenario_provider_ovs.rst:248 -msgid "Instance 1 resides on compute node 1 and uses provider network 1." -msgstr "" - -# #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../deploy_scenario4b.rst:302 ../scenario_legacy_lb.rst:483 -#: ../scenario_legacy_ovs.rst:547 ../scenario_provider_ovs.rst:319 -msgid "Instance 1 resides on compute node 1." -msgstr "" - -#: ../scenario_dvr_ovs.rst:295 -msgid "Instance 1 sends a packet to a host on the external network." -msgstr "" - -# #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_dvr_ovs.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../deploy_scenario4b.rst:240 ../deploy_scenario4b.rst:305 -#: ../scenario_dvr_ovs.rst:393 ../scenario_legacy_lb.rst:410 -#: ../scenario_legacy_lb.rst:486 ../scenario_legacy_ovs.rst:416 -#: ../scenario_legacy_ovs.rst:550 ../scenario_provider_ovs.rst:250 -#: ../scenario_provider_ovs.rst:322 -msgid "Instance 1 sends a packet to instance 2." -msgstr "" - -# #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../deploy_scenario4b.rst:232 ../deploy_scenario4b.rst:296 -#: ../scenario_provider_ovs.rst:242 ../scenario_provider_ovs.rst:313 -msgid "Instance 1: 192.0.2.11 with MAC address *I1*" -msgstr "" - -# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../scenario_legacy_lb.rst:401 ../scenario_legacy_lb.rst:477 -#: ../scenario_legacy_ovs.rst:407 ../scenario_legacy_ovs.rst:541 -msgid "Instance 1: 192.168.1.11 with MAC address *I1*" -msgstr "" - -#: ../scenario_dvr_ovs.rst:387 -msgid "Instance 2 192.168.2.11 with MAC address *I2*" -msgstr "" - -#: ../scenario_legacy_lb.rst:408 -msgid "Instance 2 resides on compute node 2 and uses VLAN project network 2." -msgstr "" - -# #-#-#-#-# scenario_dvr_ovs.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../scenario_dvr_ovs.rst:391 ../scenario_legacy_ovs.rst:414 -msgid "Instance 2 resides on compute node 2 and uses project network 2." -msgstr "" - -# #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../deploy_scenario4b.rst:239 ../scenario_provider_ovs.rst:249 -msgid "Instance 2 resides on compute node 2 and uses provider network 2." -msgstr "" - -# #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../deploy_scenario4b.rst:303 ../scenario_legacy_lb.rst:484 -#: ../scenario_legacy_ovs.rst:548 ../scenario_provider_ovs.rst:320 -msgid "Instance 2 resides on compute node 2." -msgstr "" - -# #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../deploy_scenario4b.rst:300 ../scenario_provider_ovs.rst:317 -msgid "Instance 2: 192.0.2.12 with MAC address *I2*" -msgstr "" - -# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../scenario_legacy_lb.rst:481 ../scenario_legacy_ovs.rst:545 -msgid "Instance 2: 192.168.1.12 with MAC address *I2*" -msgstr "" - -# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../scenario_legacy_lb.rst:405 ../scenario_legacy_ovs.rst:411 -msgid "Instance 2: 192.168.2.11 with MAC address *I2*" -msgstr "" - -# #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../deploy_scenario4b.rst:236 ../scenario_provider_ovs.rst:246 -msgid "Instance 2: 198.51.100.11 with MAC address *I2*" -msgstr "" - -#: ../adv_config_sriov.rst:102 -msgid "Intel" -msgstr "" - -#: ../adv_config_ipv6.rst:331 -msgid "" -"Internal router ports, that act as default gateway ports for a network, will " -"share a common port for all IPv6 subnets associated with the network. This " -"implies that there will be an IPv6 internal router interface with multiple " -"IPv6 addresses from each of the IPv6 subnets associated with the network and " -"a separate IPv4 internal router interface for the IPv4 subnet. On the other " -"hand, external router ports are allowed to have a dual-stack configuration " -"with both an IPv4 and an IPv6 address assigned to them." -msgstr "" - -#: ../intro_os_networking.rst:3 -msgid "Introduction to OpenStack Networking (neutron)" -msgstr "" - -#: ../intro_networking.rst:3 -msgid "Introduction to networking" -msgstr "" - -#: ../intro_os_networking_overview.rst:19 -msgid "It includes the following components:" -msgstr "" - -#: ../intro_basic_networking.rst:343 -msgid "" -"It is common for a packet to hop across multiple routers to reach its final " -"destination. On a Linux machine, the ``traceroute`` and more recent ``mtr`` " -"programs prints out the IP address of each router that an IP packet " -"traverses along its path to its destination." -msgstr "" - -#: ../intro_basic_networking.rst:128 -msgid "" -"It is important that you select a VLAN range that your current network " -"infrastructure is not using. For example, if you estimate that your cloud " -"must support a maximum of 100 projects, pick a VLAN range outside of that " -"value, such as VLAN 200–299. OpenStack and all physical network " -"infrastructure that handles tenant networks must then support this VLAN " -"range." -msgstr "" - -#: ../config_ml2_plug_in.rst:70 -msgid "Just specifies that these exist" -msgstr "" - -#: ../adv_config_sriov.rst:62 -msgid "Known limitations" -msgstr "" - -#: ../config_ml2_plug_in.rst:58 -msgid "L2 population" -msgstr "" - -# #-#-#-#-# config_ml2_plug_in.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# intro_os_networking_service.pot (Networking Guide 0.9) #-#-#-#-# -#: ../config_ml2_plug_in.rst:83 ../intro_os_networking_service.rst:47 -msgid "L3" -msgstr "" - -# #-#-#-#-# scenario_dvr_ovs.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_l3ha_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_l3ha_ovs.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../scenario_dvr_ovs.rst:637 ../scenario_dvr_ovs.rst:724 -#: ../scenario_l3ha_lb.rst:362 ../scenario_l3ha_ovs.rst:373 -#: ../scenario_legacy_lb.rst:681 ../scenario_legacy_ovs.rst:783 -msgid "L3 agent" -msgstr "" - -#: ../scenario_dvr_ovs.rst:154 -msgid "L3 agent managing the ``qrouter`` and ``fip`` namespaces." -msgstr "" - -#: ../scenario_dvr_ovs.rst:129 -msgid "L3 agent managing the ``qrouter`` and ``snat`` namespaces." -msgstr "" - -# #-#-#-#-# scenario_l3ha_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_l3ha_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../scenario_l3ha_lb.rst:136 ../scenario_l3ha_ovs.rst:143 -msgid "" -"L3 agent managing the ``qrouter`` namespaces and VRRP using ``keepalived``. " -"The ``qrouter`` namespaces provide routing between project and external " -"networks and among project networks. They also route metadata traffic " -"between instances and the metadata agent." -msgstr "" - -# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../scenario_legacy_lb.rst:163 ../scenario_legacy_ovs.rst:169 -msgid "" -"L3 agent managing the ``qrouter`` namespaces. The ``qrouter`` namespaces " -"provide routing between project and external networks and among project " -"networks. They also route metadata traffic between instances and the " -"metadata agent." -msgstr "" - -# #-#-#-#-# adv_config_ipv6.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# adv_config_LBaaS.pot (Networking Guide 0.9) #-#-#-#-# -#: ../adv_config_ipv6.rst:394 ../adv_config_LBaaS.rst:3 -msgid "LBaaS" -msgstr "" - -# #-#-#-#-# scenario_dvr_ovs.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../scenario_dvr_ovs.rst:962 ../scenario_legacy_lb.rst:961 -#: ../scenario_legacy_ovs.rst:1064 -msgid "Launch an instance with an interface on the project network." -msgstr "" - -# #-#-#-#-# scenario_l3ha_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_l3ha_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../scenario_l3ha_lb.rst:811 ../scenario_l3ha_ovs.rst:819 -msgid "" -"Launch an instance with an interface on the project network. For example, " -"using an existing *CirrOS* image:" -msgstr "" - -# #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../deploy_scenario4b.rst:599 ../scenario_provider_ovs.rst:650 -msgid "Launch an instance with an interface on the provider network." -msgstr "" - -#: ../intro_os_networking_service.rst:34 -msgid "Layer 2 (Ethernet and Switching)" -msgstr "" - -#: ../intro_os_networking_service.rst:45 -msgid "Layer 3 (IP and Routing)" -msgstr "" - -#: ../intro_os_networking_service.rst:75 -msgid "LbaaS" -msgstr "" - -#: ../migration_legacy_to_dvr.rst:3 -msgid "Legacy to DVR" -msgstr "" - -#: ../migration_legacy_to_L3_HA.rst:3 -msgid "Legacy to L3 HA" -msgstr "" - -#: ../intro_basic_networking.rst:434 -msgid "" -"Like TCP, the sockets API is the most common API for writing UDP-based " -"applications. The sockets API provides a *message-oriented* interface for " -"writing UDP applications: a programmer sends data over UDP by transmitting a " -"fixed-sized message. If an application requires retransmissions of lost " -"packets or a well-defined ordering of received packets, the programmer is " -"responsible for implementing this functionality in the application code." -msgstr "" - -#: ../intro_basic_networking.rst:302 -msgid "" -"Line 1 of the output specifies the location of the default route, which is " -"the effective routing rule if none of the other rules match. The router " -"associated with the default route (``10.0.2.2`` in the example above) is " -"sometimes referred to as the *default gateway*. A DHCP_ server typically " -"transmits the IP address of the default gateway to the DHCP client along " -"with the client's IP address and a netmask." -msgstr "" - -#: ../intro_basic_networking.rst:309 -msgid "" -"Line 2 of the output specifies that IPs in the 10.0.2.0/24 subnet are on the " -"local network associated with the network interface eth0." -msgstr "" - -#: ../intro_basic_networking.rst:312 -msgid "" -"Line 3 of the output specifies that IPs in the 192.168.27.0/24 subnet are on " -"the local network associated with the network interface eth1." -msgstr "" - -#: ../intro_basic_networking.rst:315 -msgid "" -"Line 4 of the output specifies that IPs in the 192.168.122/24 subnet are on " -"the local network associated with the network interface virbr0." -msgstr "" - -#: ../intro_os_networking_service.rst:36 -msgid "Linux Bridge" -msgstr "" - -#: ../config_ml2_plug_in.rst:50 -msgid "Linux bridge" -msgstr "" - -# #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_l3ha_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# -#: ../deploy_scenario4b.rst:438 ../deploy_scenario4b.rst:486 -#: ../scenario_l3ha_lb.rst:361 ../scenario_l3ha_lb.rst:417 -#: ../scenario_legacy_lb.rst:680 ../scenario_legacy_lb.rst:736 -msgid "Linux bridge agent" -msgstr "" - -# #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_l3ha_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# -#: ../deploy_scenario4b.rst:117 ../scenario_l3ha_lb.rst:131 -#: ../scenario_legacy_lb.rst:158 -msgid "" -"Linux bridge agent managing virtual switches, connectivity among them, and " -"interaction via virtual ports with other network components such as " -"namespaces and underlying interfaces." -msgstr "" - -# #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_l3ha_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# -#: ../deploy_scenario4b.rst:135 ../scenario_l3ha_lb.rst:154 -#: ../scenario_legacy_lb.rst:177 -msgid "" -"Linux bridge agent managing virtual switches, connectivity among them, and " -"interaction via virtual ports with other network components such as " -"namespaces, security groups, and underlying interfaces." -msgstr "" - -# #-#-#-#-# scenario_dvr_ovs.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_l3ha_ovs.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../scenario_dvr_ovs.rst:165 ../scenario_l3ha_ovs.rst:160 -#: ../scenario_provider_ovs.rst:134 -msgid "Linux bridges handling security groups." -msgstr "" - -#: ../scenario_legacy_ovs.rst:186 -msgid "" -"Linux bridges handling security groups. Due to limitations with Open vSwitch " -"and *iptables*, the Networking service uses a Linux bridge to manage " -"security groups for instances." -msgstr "" - -#: ../misc_libvirt.rst:29 -msgid "Linux bridging for implementing a layer 2 network" -msgstr "" - -#: ../intro_network_namespaces.rst:17 -msgid "Linux network namespaces" -msgstr "" - -#: ../adv_config_sriov.rst:71 -msgid "Live migration is not supported for instances with SR-IOV ports." -msgstr "" - -#: ../intro_networking_components.rst:28 -msgid "Load balancers" -msgstr "" - -# #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_dvr_ovs.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_l3ha_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_l3ha_ovs.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../deploy_scenario4b.rst:366 ../deploy_scenario4b.rst:452 -#: ../scenario_dvr_ovs.rst:542 ../scenario_dvr_ovs.rst:656 -#: ../scenario_l3ha_lb.rst:268 ../scenario_l3ha_lb.rst:379 -#: ../scenario_l3ha_ovs.rst:280 ../scenario_l3ha_ovs.rst:390 -#: ../scenario_legacy_lb.rst:592 ../scenario_legacy_lb.rst:698 -#: ../scenario_legacy_ovs.rst:690 ../scenario_legacy_ovs.rst:800 -#: ../scenario_provider_ovs.rst:389 ../scenario_provider_ovs.rst:489 -msgid "Load the new kernel configuration:" -msgstr "" - -#: ../config_ml2_plug_in.rst:31 -msgid "Local" -msgstr "" - -#: ../adv_config_operational.rst:8 -msgid "Logging" -msgstr "" - -#: ../config_ml2_plug_in.rst:3 -msgid "ML2 plug-in" -msgstr "" - -# #-#-#-#-# scenario_l3ha_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# -#: ../scenario_l3ha_lb.rst:111 ../scenario_legacy_lb.rst:129 -msgid "" -"ML2 plug-in, Linux bridge agent, L3 agent, DHCP agent, metadata agent, and " -"any dependencies." -msgstr "" - -# #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_l3ha_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# -#: ../deploy_scenario4b.rst:104 ../scenario_l3ha_lb.rst:121 -#: ../scenario_legacy_lb.rst:139 -msgid "ML2 plug-in, Linux bridge agent, and any dependencies." -msgstr "" - -#: ../migration_nova_network_to_neutron.rst:99 -msgid "" -"Make Compute REST API read-write again. This means legacy networking DB is " -"now unused, new changes are now stored in the Networking DB, and no rollback " -"is possible from here without losing those new changes." -msgstr "" - -#: ../adv_config_sriov.rst:113 -msgid "" -"Make sure SR-IOV is enabled in BIOS, check for VT-d and make sure it is " -"enabled. After enabling VT-d, enable IOMMU on Linux by adding " -"``intel_iommu=on`` to kernel parameters. Edit the file :file:`/etc/default/" -"grub`:" -msgstr "" - -#: ../migration_nova_network_to_neutron.rst:93 -msgid "Make the Compute REST API read-only." -msgstr "" - -#: ../migration_nova_network_to_neutron.rst:126 -msgid "Make the Networking API read-write and disable legacy networking." -msgstr "" - -#: ../adv_config_ipv6.rst:322 -msgid "Managed Configuration Flag = 0" -msgstr "" - -#: ../migration_nova_network_to_neutron.rst:43 -msgid "Management impact" -msgstr "" - -#: ../intro_os_networking_service.rst:19 -msgid "Manages agents" -msgstr "" - -#: ../config_ml2_plug_in.rst:48 -msgid "Mechanism" -msgstr "" - -#: ../adv_config_sriov.rst:103 -msgid "Mellanox" -msgstr "" - -#: ../intro_os_networking_overview.rst:42 -msgid "Messaging queue" -msgstr "" - -# #-#-#-#-# config_ml2_plug_in.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# intro_os_networking_service.pot (Networking Guide 0.9) #-#-#-#-# -#: ../config_ml2_plug_in.rst:93 ../intro_os_networking_service.rst:58 -msgid "Metadata" -msgstr "" - -# #-#-#-#-# scenario_dvr_ovs.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_l3ha_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_l3ha_ovs.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../scenario_dvr_ovs.rst:639 ../scenario_dvr_ovs.rst:725 -#: ../scenario_l3ha_lb.rst:364 ../scenario_l3ha_ovs.rst:375 -#: ../scenario_legacy_lb.rst:683 ../scenario_legacy_ovs.rst:785 -msgid "Metadata agent" -msgstr "" - -#: ../scenario_dvr_ovs.rst:163 -msgid "" -"Metadata agent handling metadata operations for instances using project " -"networks on distributed routers." -msgstr "" - -#: ../scenario_dvr_ovs.rst:139 -msgid "" -"Metadata agent handling metadata operations for instances using project " -"networks on legacy routers." -msgstr "" - -# #-#-#-#-# scenario_l3ha_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_l3ha_ovs.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../scenario_l3ha_lb.rst:140 ../scenario_l3ha_ovs.rst:147 -#: ../scenario_legacy_lb.rst:167 ../scenario_legacy_ovs.rst:173 -msgid "Metadata agent handling metadata operations for instances." -msgstr "" - -#: ../migration_nova_network_to_neutron.rst:3 -msgid "Migrate legacy nova-network to OpenStack Networking (neutron)" -msgstr "" - -#: ../migration.rst:3 -msgid "Migration" -msgstr "" - -#: ../migration_nova_network_to_neutron.rst:128 -msgid "Migration Completed!" -msgstr "" - -#: ../migration_nova_network_to_neutron.rst:89 -msgid "Migration process overview" -msgstr "" - -# #-#-#-#-# intro_os_networking_service.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# miscellaneous.pot (Networking Guide 0.9) #-#-#-#-# -#: ../intro_os_networking_service.rst:56 ../miscellaneous.rst:3 -msgid "Miscellaneous" -msgstr "" - -#: ../adv_config_qos.rst:95 -msgid "Modify ``/etc/neutron/policy.json`` policy entries as follows::" -msgstr "" - -#: ../misc_libvirt.rst:5 -msgid "" -"Most OpenStack deployments use the libvirt_ toolkit for interacting with the " -"hypervisor. Specifically, OpenStack Compute uses libvirt for tasks such as " -"booting and terminating virtual machine instances. When OpenStack Compute " -"boots a new instance, libvirt provides OpenStack with the VIF associated " -"with the instance, and OpenStack Compute plugs the VIF into a virtual device " -"provided by OpenStack Network. The libvirt toolkit itself does not provide " -"any networking functionality in OpenStack deployments." -msgstr "" - -#: ../config_ml2_plug_in.rst:45 -msgid "Multicast discovery (L2 population)" -msgstr "" - -#: ../adv_config_ipv6.rst:404 -msgid "NAT & Floating IPs" -msgstr "" - -#: ../intro_network_address_translation.rst:10 -msgid "" -"NAT is often implemented by routers, and so we will refer to the host " -"performing NAT as a *NAT router*. However, in OpenStack deployments it is " -"typically Linux servers that implement the NAT functionality, not hardware " -"routers. These servers use the iptables_ software package to implement the " -"NAT functionality." -msgstr "" - -# #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../deploy_scenario4b.rst:174 ../scenario_provider_ovs.rst:180 -msgid "Network 192.0.2.0/24" -msgstr "" - -# #-#-#-#-# scenario_dvr_ovs.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../scenario_dvr_ovs.rst:198 ../scenario_dvr_ovs.rst:284 -#: ../scenario_dvr_ovs.rst:372 ../scenario_legacy_lb.rst:209 -#: ../scenario_legacy_lb.rst:305 ../scenario_legacy_ovs.rst:218 -#: ../scenario_legacy_ovs.rst:310 -msgid "Network 192.168.1.0/24" -msgstr "" - -#: ../scenario_dvr_ovs.rst:377 -msgid "Network 192.168.2.0/24" -msgstr "" - -# #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_dvr_ovs.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../deploy_scenario4b.rst:170 ../scenario_dvr_ovs.rst:190 -#: ../scenario_dvr_ovs.rst:277 ../scenario_legacy_lb.rst:203 -#: ../scenario_legacy_lb.rst:299 ../scenario_legacy_ovs.rst:212 -#: ../scenario_legacy_ovs.rst:304 ../scenario_provider_ovs.rst:176 -msgid "Network 203.0.113.0/24" -msgstr "" - -#: ../intro_network_address_translation.rst:3 -msgid "Network address translation" -msgstr "" - -#: ../intro_networking_components.rst:3 -msgid "Network components" -msgstr "" - -#: ../adv_config_debugging.rst:34 -msgid "Network configuration in the database" -msgstr "" - -#: ../adv_config_qos.rst:13 -msgid "" -"Network devices such as switches and routers can mark traffic so that it is " -"handled with a higher priority to fulfill the QoS conditions agreed under " -"the SLA. In other cases, certain network traffic such as Voice over IP " -"(VoIP) and video streaming needs to be transmitted with minimal bandwidth " -"constraints. On a system without network QoS management, all traffic will be " -"transmitted in a \"best-effort\" manner making it impossible to guarantee " -"service delivery to customers." -msgstr "" - -#: ../intro_network_namespaces.rst:3 -msgid "Network namespaces" -msgstr "" - -#: ../adv_config_debugging.rst:49 -msgid "Network namespaces configuration" -msgstr "" - -# #-#-#-#-# scenario_dvr_ovs.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../scenario_dvr_ovs.rst:531 ../scenario_legacy_lb.rst:581 -#: ../scenario_legacy_ovs.rst:679 -msgid "Network node" -msgstr "" - -# #-#-#-#-# scenario_l3ha_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_l3ha_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../scenario_l3ha_lb.rst:659 ../scenario_l3ha_lb.rst:681 -#: ../scenario_l3ha_lb.rst:736 ../scenario_l3ha_ovs.rst:669 -#: ../scenario_l3ha_ovs.rst:690 ../scenario_l3ha_ovs.rst:745 -msgid "Network node 1:" -msgstr "" - -# #-#-#-#-# scenario_l3ha_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_l3ha_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../scenario_l3ha_lb.rst:666 ../scenario_l3ha_lb.rst:705 -#: ../scenario_l3ha_lb.rst:745 ../scenario_l3ha_ovs.rst:676 -#: ../scenario_l3ha_ovs.rst:714 ../scenario_l3ha_ovs.rst:754 -msgid "Network node 2:" -msgstr "" - -# #-#-#-#-# scenario_l3ha_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_l3ha_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../scenario_l3ha_lb.rst:257 ../scenario_l3ha_ovs.rst:269 -msgid "Network nodes" -msgstr "" - -#: ../adv_config_debugging.rst:16 -msgid "" -"Network troubleshooting can unfortunately be a very difficult and confusing " -"procedure. A network issue can cause a problem at several points in the " -"cloud. Using a logical troubleshooting procedure can help mitigate the " -"confusion and quickly isolate the network issue." -msgstr "" - -#: ../config_ml2_plug_in.rst:15 -msgid "Network type drivers" -msgstr "" - -# #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../deploy_scenario4b.rst:222 ../deploy_scenario4b.rst:292 -#: ../scenario_provider_ovs.rst:232 ../scenario_provider_ovs.rst:309 -msgid "Network: 192.0.2.0/24" -msgstr "" - -# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../scenario_legacy_lb.rst:391 ../scenario_legacy_lb.rst:473 -#: ../scenario_legacy_ovs.rst:397 ../scenario_legacy_ovs.rst:537 -msgid "Network: 192.168.1.0/24" -msgstr "" - -# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../scenario_legacy_lb.rst:396 ../scenario_legacy_ovs.rst:402 -msgid "Network: 192.168.2.0/24" -msgstr "" - -# #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../deploy_scenario4b.rst:227 ../scenario_provider_ovs.rst:237 -msgid "Network: 198.51.100.0/24" -msgstr "" - -#: ../intro_os_networking_overview.rst:71 -msgid "" -"Networking allows users to create multiple provider or tenant networks using " -"VLAN IDs (802.1Q tagged) that correspond to VLANs present in the physical " -"network. This allows instances to communicate with each other across the " -"environment. They can also communicate with dedicated servers, firewalls, " -"load balancers, and other networking infrastructure on the same layer 2 VLAN." -msgstr "" - -#: ../adv_config_ipv6.rst:683 -msgid "Neutron dhcpv6_pd_agent" -msgstr "" - -#: ../adv_config_ipv6.rst:284 -msgid "" -"Neutron networks that contain a SLAAC enabled IPv6 subnet will result in all " -"neutron ports attached to the network receiving IPv6 addresses. This is " -"because when RA broadcast messages are sent out on a neutron network, they " -"are received by all IPv6 capable ports on the network, and each port will " -"then configure an IPv6 address based on the information contained in the RA " -"packet. In some cases, an IPv6 SLAAC address will be added to a port, in " -"addition to other IPv4 and IPv6 addresses that the port already has been " -"assigned." -msgstr "" - -#: ../deploy_scenario4b.rst:94 -msgid "" -"Neutron server service, ML2 plug-in, Linux bridge agent, DHCP agent, and any " -"dependencies." -msgstr "" - -# #-#-#-#-# scenario_dvr_ovs.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_l3ha_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_l3ha_ovs.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../scenario_dvr_ovs.rst:90 ../scenario_l3ha_lb.rst:104 -#: ../scenario_l3ha_ovs.rst:109 ../scenario_legacy_lb.rst:122 -#: ../scenario_legacy_ovs.rst:128 -msgid "Neutron server service, ML2 plug-in, and any dependencies." -msgstr "" - -#: ../scenario_provider_ovs.rst:89 -msgid "" -"Neutron server service, Open vSwitch service, ML2 plug-in, Open vSwitch " -"agent, DHCP agent, and any dependencies." -msgstr "" - -#: ../adv_config_sriov.rst:45 -msgid "Neutron sriov-agent" -msgstr "" - -#: ../adv_config_ipv6.rst:46 -msgid "Neutron subnets and the IPv6 API attributes" -msgstr "" - -#: ../adv_config_ipv6.rst:339 -msgid "" -"Neutron tenant networks that are assigned Global Unicast Address (GUA) " -"prefixes and addresses don’t require NAT on the neutron router external " -"gateway port to access the outside world. As a consequence of the lack of " -"NAT the external router port doesn’t require a GUA to send and receive to " -"the external networks. This implies a GUA IPv6 subnet prefix is not " -"necessarily needed for the neutron external network. By default, a IPv6 LLA " -"associated with the external gateway port can be used for routing purposes. " -"To handle this scenario, the implementation of router-gateway-set API in " -"neutron has been modified so that an IPv6 subnet is not required for the " -"external network that is associated with the neutron router. The LLA address " -"of the upstream router can be learned in two ways." -msgstr "" - -#: ../adv_config_ipv6.rst:370 -msgid "Neutron's Distributed Router feature and IPv6" -msgstr "" - -#: ../adv_config_debugging.rst:14 ../adv_config_debugging.rst:29 -msgid "Neutron-debug command line tools" -msgstr "" - -#: ../migration_nova_network_to_neutron.rst:108 -msgid "" -"Next, you'll need to migrate each hypervisor. To do that, follow these " -"steps:" -msgstr "" - -#: ../adv_config_sriov.rst:69 -msgid "" -"No OpenStack Dashboard integration. Users need to use CLI or API to create " -"neutron SR-IOV ports." -msgstr "" - -#: ../adv_config_ipv6.rst:107 -msgid "Not Defined" -msgstr "" - -#: ../adv_config_ipv6.rst:118 ../adv_config_ipv6.rst:123 -#: ../adv_config_ipv6.rst:128 ../adv_config_ipv6.rst:133 -#: ../adv_config_ipv6.rst:138 -msgid "Not currently implemented in the reference implementation." -msgstr "" - -#: ../adv_config_ipv6.rst:32 -msgid "Not in scope" -msgstr "" - -#: ../adv_config_ipv6.rst:266 -msgid "Not specified." -msgstr "" - -#: ../intro_basic_networking.rst:124 -msgid "" -"Note that if you are using VLANs on your physical switches to implement " -"tenant isolation in your OpenStack cloud, you must ensure that all of your " -"switchports are configured as trunk ports." -msgstr "" - -#: ../intro_basic_networking.rst:102 -msgid "" -"Now consider the scenario that all of the switchports in the first switch " -"become occupied, and so the organization buys a second switch and connects " -"it to the first switch to expand the available number of switchports. The " -"second switch is also configured to support VLAN IDs 10, 11, and 12. Now " -"imagine host A connected to switch 1 on a port configured for VLAN ID 10 " -"sends an Ethernet frame intended for host B connected to switch 2 on a port " -"configured for VLAN ID 10. When switch 1 forwards the Ethernet frame to " -"switch 2, it must communicate that the frame is associated with VLAN ID 10." -msgstr "" - -#: ../adv_config_sriov.rst:264 -msgid "" -"Now restart the nova-scheduler service with :command:`service nova-scheduler " -"restart`." -msgstr "" - -#: ../adv_config_sriov.rst:139 -msgid "" -"Now verify that the VFs have been created (Should see Virtual Function " -"device):" -msgstr "" - -#: ../intro_os_networking_service.rst:40 -msgid "OVS" -msgstr "" - -# #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../deploy_scenario4b.rst:670 ../scenario_provider_ovs.rst:721 -msgid "Obtain access to the instance." -msgstr "" - -# #-#-#-#-# scenario_dvr_ovs.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_l3ha_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_l3ha_ovs.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../scenario_dvr_ovs.rst:971 ../scenario_l3ha_lb.rst:849 -#: ../scenario_l3ha_ovs.rst:857 ../scenario_legacy_lb.rst:962 -#: ../scenario_legacy_ovs.rst:1065 -msgid "Obtain console access to the instance." -msgstr "" - -# #-#-#-#-# scenario_dvr_ovs.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_l3ha_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_l3ha_ovs.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../scenario_dvr_ovs.rst:812 ../scenario_l3ha_lb.rst:504 -#: ../scenario_l3ha_ovs.rst:514 ../scenario_legacy_lb.rst:819 -#: ../scenario_legacy_ovs.rst:921 -msgid "" -"Obtain the ID of a regular project. For example, using the ``demo`` project:" -msgstr "" - -#: ../adv_config_ipv6.rst:106 ../adv_config_ipv6.rst:111 -#: ../adv_config_ipv6.rst:116 ../adv_config_ipv6.rst:121 -#: ../adv_config_ipv6.rst:127 ../adv_config_ipv6.rst:132 -#: ../adv_config_ipv6.rst:137 ../adv_config_ipv6.rst:142 -#: ../adv_config_ipv6.rst:147 ../adv_config_ipv6.rst:153 -msgid "Off" -msgstr "" - -#: ../intro_network_address_translation.rst:41 -msgid "" -"Often, an application running on a host with a private IP address will need " -"to connect to a server on the public Internet. One such example is a user " -"who wants to access a public website such as www.openstack.org. If the IP " -"packets reach the web server at www.openstack.org with a private IP address " -"as the source, then the web server cannot send packets back to the sender." -msgstr "" - -# #-#-#-#-# scenario_l3ha_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_l3ha_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../scenario_l3ha_lb.rst:639 ../scenario_l3ha_ovs.rst:649 -msgid "" -"Older versions of *python-neutronclient* do not support the ``ha_state`` " -"field." -msgstr "" - -#: ../misc_libvirt.rst:46 -msgid "" -"On Ubuntu, the iptables ruleset that libvirt creates includes the following " -"rules::" -msgstr "" - -#: ../intro_basic_networking.rst:288 -msgid "" -"On a Linux machine, any of the following commands displays the routing " -"table::" -msgstr "" - -#: ../adv_config_qos.rst:71 -msgid "On agent side (OVS):" -msgstr "" - -#: ../adv_config_sriov.rst:276 -msgid "" -"On each compute node edit the file :file:`/etc/neutron/plugins/ml2/" -"ml2_conf_sriov.ini`:" -msgstr "" - -#: ../adv_config_sriov.rst:129 -msgid "On each compute node, create the VFs via the PCI SYS interface:" -msgstr "" - -#: ../scenario_l3ha_lb.rst:725 -msgid "" -"On each network node, the ``qrouter`` namespace should include the ``ha``, " -"``qr``, and ``qg`` interfaces. On the master node, the ``qr`` interface " -"contains the project network gateway IP address and the ``qg`` interface " -"contains the project network router IP address on the external network. On " -"the backup node, the ``qr`` and ``qg`` interfaces should not contain an IP " -"address. On both nodes, the ``ha`` interface should contain a unique IP " -"address in the 169.254.192.0/18 range." -msgstr "" - -#: ../scenario_l3ha_ovs.rst:734 -msgid "" -"On each network node, the ``qrouter`` namespace should include the ``ha``, " -"``qr``, and ``qg`` interfaces. On the master node, the ``qr`` interface " -"contains the project network gateway IP address and the ``qg`` interface " -"contains the project router IP address on the external network. On the " -"backup node, the ``qr`` and ``qg`` interfaces should not contain an IP " -"address. On both nodes, the ``ha`` interface should contain a unique IP " -"address in the 169.254.192.0/18 range." -msgstr "" - -#: ../adv_config_sriov.rst:250 -msgid "" -"On every controller node running nova-scheduler add PCIDeviceScheduler to " -"the scheduler_default_filters parameter and add a new line for " -"scheduler_available_filters parameter under the [default] section in :file:`/" -"etc/nova/nova.conf`:" -msgstr "" - -#: ../adv_config_qos.rst:64 -msgid "On server side:" -msgstr "" - -#: ../scenario_dvr_ovs.rst:1058 -msgid "" -"On the compute node with the instance, verify creation of the ``fip`` " -"namespace:" -msgstr "" - -#: ../scenario_dvr_ovs.rst:963 -msgid "" -"On the compute node with the instance, verify creation of the ``qrouter`` " -"namespace:" -msgstr "" - -# #-#-#-#-# scenario_dvr_ovs.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_l3ha_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_l3ha_ovs.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../scenario_dvr_ovs.rst:945 ../scenario_l3ha_lb.rst:774 -#: ../scenario_l3ha_ovs.rst:782 ../scenario_legacy_lb.rst:943 -#: ../scenario_legacy_ovs.rst:1046 -msgid "" -"On the controller node or any host with access to the external network, ping " -"the external network gateway IP address on the project router:" -msgstr "" - -# #-#-#-#-# scenario_dvr_ovs.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_l3ha_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_l3ha_ovs.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../scenario_dvr_ovs.rst:1066 ../scenario_l3ha_lb.rst:917 -#: ../scenario_l3ha_ovs.rst:925 ../scenario_legacy_lb.rst:1048 -#: ../scenario_legacy_ovs.rst:1151 -msgid "" -"On the controller node or any host with access to the external network, ping " -"the floating IP address associated with the instance:" -msgstr "" - -# #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../deploy_scenario4b.rst:654 ../scenario_provider_ovs.rst:705 -msgid "" -"On the controller node or any host with access to the provider network, ping " -"the IP address of the instance:" -msgstr "" - -# #-#-#-#-# scenario_l3ha_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_l3ha_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../scenario_l3ha_lb.rst:612 ../scenario_l3ha_ovs.rst:622 -msgid "On the controller node, verify creation of the HA network:" -msgstr "" - -# #-#-#-#-# scenario_l3ha_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_l3ha_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../scenario_l3ha_lb.rst:641 ../scenario_l3ha_ovs.rst:651 -msgid "" -"On the controller node, verify creation of the HA ports on the ``demo-" -"router`` router:" -msgstr "" - -# #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../deploy_scenario4b.rst:568 ../scenario_provider_ovs.rst:619 -msgid "On the controller node, verify creation of the ``qdhcp`` namespace:" -msgstr "" - -# #-#-#-#-# scenario_l3ha_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_l3ha_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../scenario_l3ha_lb.rst:625 ../scenario_l3ha_ovs.rst:635 -msgid "" -"On the controller node, verify creation of the router on more than one " -"network node:" -msgstr "" - -# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../scenario_legacy_lb.rst:917 ../scenario_legacy_ovs.rst:1020 -msgid "" -"On the network node, verify creation of the ``qrouter`` and ``qdhcp`` " -"namespaces:" -msgstr "" - -#: ../scenario_dvr_ovs.rst:917 -msgid "" -"On the network node, verify creation of the `snat`, `qrouter`, and `qdhcp` " -"namespaces:" -msgstr "" - -# #-#-#-#-# scenario_l3ha_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_l3ha_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../scenario_l3ha_lb.rst:679 ../scenario_l3ha_ovs.rst:688 -msgid "On the network nodes, verify HA operation:" -msgstr "" - -#: ../scenario_l3ha_lb.rst:733 -msgid "" -"On the network nodes, verify VRRP advertisements from the master node HA " -"interface IP address on the appropriate network interface." -msgstr "" - -#: ../scenario_l3ha_ovs.rst:742 -msgid "" -"On the network nodes, verify VRRP advertisements from the master node HA " -"interface IP address on the appropriate network interface:" -msgstr "" - -#: ../scenario_l3ha_lb.rst:656 -msgid "" -"On the network nodes, verify creation of the ``qrouter`` and ``qdhcp`` " -"namespaces." -msgstr "" - -#: ../scenario_l3ha_ovs.rst:666 -msgid "" -"On the network nodes, verify creation of the ``qrouter`` and ``qdhcp`` " -"namespaces:" -msgstr "" - -#: ../adv_config_ipv6.rst:695 -msgid "" -"Once you have stacked run the command below to start the neutron-pd-agent::" -msgstr "" - -# #-#-#-#-# scenario_dvr_ovs.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_l3ha_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_l3ha_ovs.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../scenario_dvr_ovs.rst:43 ../scenario_l3ha_lb.rst:59 -#: ../scenario_l3ha_ovs.rst:58 ../scenario_legacy_lb.rst:78 -#: ../scenario_legacy_ovs.rst:77 -msgid "One controller node with one network interface: management." -msgstr "" - #: ../deploy_scenario4b.rst:65 msgid "" "One controller node with two network interfaces: management and provider. " @@ -3600,240 +2063,12 @@ msgid "" "infrastructure switches/routes to external networks (typically the Internet)." msgstr "" -#: ../scenario_provider_ovs.rst:58 +#: ../deploy_scenario4b.rst:69 msgid "" -"One controller node with two network interfaces: management and provider. " -"The provider interface connects to a generic network that physical network " -"infrastructure switches/routes to external networks (typically the " -"Internet). The Open vSwitch bridge ``br-provider`` must contain a port on " -"the provider network interface." -msgstr "" - -#: ../scenario_legacy_lb.rst:79 -msgid "" -"One network node with four network interfaces: management, project tunnel " -"networks, VLAN project networks, and external (typically the Internet)." -msgstr "" - -#: ../scenario_legacy_ovs.rst:78 -msgid "" -"One network node with four network interfaces: management, project tunnel " -"networks, VLAN project networks, and external (typically the Internet). The " -"Open vSwitch bridge ``br-vlan`` must contain a port on the VLAN interface " -"and Open vSwitch bridge ``br-ex`` must contain a port on the external " -"interface." -msgstr "" - -#: ../scenario_dvr_ovs.rst:44 -msgid "" -"One network node with four network interfaces: management, project tunnel " -"networks, VLAN project networks, and external (typically the Internet). The " -"Open vSwitch bridge ``br-vlan`` must contain a port on the VLAN interface " -"and the Open vSwitch bridge ``br-ex`` must contain a port on the external " -"interface." -msgstr "" - -#: ../scenario_dvr_ovs.rst:928 -msgid "One or more namespaces might not exist until launching an instance." -msgstr "" - -#: ../intro_network_address_translation.rst:82 -msgid "One-to-one NAT" -msgstr "" - -#: ../config_ml2_plug_in.rst:62 -msgid "Open source" -msgstr "" - -# #-#-#-#-# config_ml2_plug_in.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_dvr_ovs.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_l3ha_ovs.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../config_ml2_plug_in.rst:54 ../scenario_dvr_ovs.rst:635 -#: ../scenario_dvr_ovs.rst:722 ../scenario_l3ha_ovs.rst:371 -#: ../scenario_l3ha_ovs.rst:426 ../scenario_legacy_ovs.rst:781 -#: ../scenario_legacy_ovs.rst:837 ../scenario_provider_ovs.rst:454 -#: ../scenario_provider_ovs.rst:517 -msgid "Open vSwitch" -msgstr "" - -# #-#-#-#-# scenario_dvr_ovs.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_l3ha_ovs.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../scenario_dvr_ovs.rst:636 ../scenario_dvr_ovs.rst:723 -#: ../scenario_l3ha_ovs.rst:372 ../scenario_l3ha_ovs.rst:427 -#: ../scenario_legacy_ovs.rst:782 ../scenario_legacy_ovs.rst:838 -#: ../scenario_provider_ovs.rst:475 ../scenario_provider_ovs.rst:537 -msgid "Open vSwitch agent" -msgstr "" - -#: ../scenario_provider_ovs.rst:131 -msgid "" -"Open vSwitch agent managing virtual switches, connectivity among them, and " -"interaction via virtual ports with other network components such as Linux " -"bridges and underlying interfaces." -msgstr "" - -#: ../scenario_provider_ovs.rst:113 -msgid "" -"Open vSwitch agent managing virtual switches, connectivity among them, and " -"interaction via virtual ports with other network components such as " -"namespaces and underlying interfaces." -msgstr "" - -# #-#-#-#-# scenario_dvr_ovs.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_l3ha_ovs.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../scenario_dvr_ovs.rst:124 ../scenario_dvr_ovs.rst:150 -#: ../scenario_l3ha_ovs.rst:138 ../scenario_l3ha_ovs.rst:157 -#: ../scenario_legacy_ovs.rst:164 ../scenario_legacy_ovs.rst:183 -msgid "" -"Open vSwitch agent managing virtual switches, connectivity among them, and " -"interaction via virtual ports with other network components such as " -"namespaces, Linux bridges, and underlying interfaces." -msgstr "" - -# #-#-#-#-# scenario_dvr_ovs.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_l3ha_ovs.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../scenario_dvr_ovs.rst:97 ../scenario_l3ha_ovs.rst:116 -#: ../scenario_legacy_ovs.rst:135 -msgid "" -"Open vSwitch service, ML2 plug-in, Open vSwitch agent, L3 agent, DHCP agent, " -"metadata agent, and any dependencies." -msgstr "" - -#: ../scenario_dvr_ovs.rst:107 -msgid "" -"Open vSwitch service, ML2 plug-in, Open vSwitch agent, L3 agent, metadata " -"agent, and any dependencies." -msgstr "" - -# #-#-#-#-# scenario_l3ha_ovs.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../scenario_l3ha_ovs.rst:127 ../scenario_legacy_ovs.rst:145 -#: ../scenario_provider_ovs.rst:99 -msgid "" -"Open vSwitch service, ML2 plug-in, Open vSwitch agent, and any dependencies." -msgstr "" - -#: ../scenario_provider_ovs.rst:159 -msgid "" -"Open vSwitch uses VLANs internally to segregate networks that traverse " -"bridges. The VLAN ID usually differs from the segmentation ID of the virtual " -"network." -msgstr "" - -#: ../intro_networking.rst:30 -msgid "" -"OpenStack Compute (nova) is used to plug each virtual NIC on the VM into a " -"particular network." -msgstr "" - -#: ../intro_networking.rst:27 -msgid "" -"OpenStack Identity (keystone) is used for authentication and authorization " -"of API requests." -msgstr "" - -#: ../index.rst:8 -msgid "OpenStack Networking Guide" -msgstr "" - -#: ../intro_os_networking_overview.rst:5 -msgid "" -"OpenStack Networking allows you to create and manage network objects, such " -"as networks, subnets, and ports, which other OpenStack services can use. " -"Plug-ins can be implemented to accommodate different networking equipment " -"and software, providing flexibility to OpenStack architecture and deployment." -msgstr "" - -#: ../intro_os_networking_overview.rst:45 -msgid "OpenStack Networking concepts" -msgstr "" - -#: ../intro_networking.rst:14 -msgid "" -"OpenStack Networking consists of the neutron-server, a database for " -"persistent storage, and any number of plug-in agents, which provide other " -"services such as interfacing with native Linux networking mechanisms, " -"external devices, or SDN controllers." -msgstr "" - -#: ../adv_config_ipv6.rst:14 -msgid "" -"OpenStack Networking has supported IPv6 tenant subnets in certain " -"configurations since Juno, but the Kilo release adds a number of new " -"features, functionality and bug fixes to make it more robust. The focus of " -"this page will be:" -msgstr "" - -#: ../intro_networking.rst:24 -msgid "" -"OpenStack Networking integrates with various other OpenStack components:" -msgstr "" - -#: ../intro_networking.rst:19 -msgid "" -"OpenStack Networking is entirely standalone and can be deployed to a " -"dedicated host. If your deployment uses a controller host to run centralized " -"Compute components, you can deploy the Networking server to that specific " -"host instead." -msgstr "" - -#: ../intro_os_networking_overview.rst:35 -msgid "OpenStack Networking plug-in and agents" -msgstr "" - -#: ../adv_config_ipv6.rst:238 -msgid "" -"OpenStack can be setup such that OpenStack Networking directly provides RA, " -"DHCP relay and DHCPv6 address and optional information for their networks or " -"this can be delegated to external routers and services based on the drivers " -"that are in use. There are two neutron subnet attributes - ``ipv6_ra_mode`` " -"and ``ipv6_address_mode`` – that determine how IPv6 addressing and network " -"information is provided to tenant instances:" -msgstr "" - -#: ../adv_config_ipv6.rst:436 -msgid "OpenStack control & management network considerations" -msgstr "" - -#: ../adv_config_ipv6.rst:37 -msgid "" -"OpenStack control communication between servers and services over an IPv6 " -"network." -msgstr "" - -#: ../adv_config_ipv6.rst:421 -msgid "" -"OpenStack currently doesn't support the privacy extensions defined by RFC " -"4941. The interface identifier and DUID used must be directly derived from " -"the MAC as described in RFC 2373. The compute hosts must not be setup to " -"utilize the privacy extensions when generating their interface identifier." -msgstr "" - -#: ../intro_networking.rst:33 -msgid "" -"OpenStack dashboard (horizon) is used by administrators and tenant users to " -"create and manage network services through a web-based graphical interface." -msgstr "" - -# #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_dvr_ovs.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_l3ha_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_l3ha_ovs.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../deploy_scenario4b.rst:98 ../scenario_dvr_ovs.rst:101 -#: ../scenario_l3ha_lb.rst:115 ../scenario_l3ha_ovs.rst:120 -#: ../scenario_legacy_lb.rst:133 ../scenario_legacy_ovs.rst:139 -#: ../scenario_provider_ovs.rst:93 -msgid "OpenStack services - compute nodes" +"At least two compute nodes with two network interfaces: management and " +"provider. The provider interface connects to a generic network that physical " +"network infrastructure switches/routes to external networks (typically the " +"Internet)." msgstr "" # #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# @@ -3850,105 +2085,6 @@ msgstr "" msgid "OpenStack services - controller node" msgstr "" -# #-#-#-#-# scenario_dvr_ovs.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_l3ha_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../scenario_dvr_ovs.rst:93 ../scenario_l3ha_lb.rst:107 -#: ../scenario_legacy_lb.rst:125 ../scenario_legacy_ovs.rst:131 -msgid "OpenStack services - network node" -msgstr "" - -#: ../scenario_l3ha_ovs.rst:112 -msgid "OpenStack services - network nodes" -msgstr "" - -#: ../intro_network_address_translation.rst:73 -msgid "" -"OpenStack uses DNAT to route packets from instances to the OpenStack " -"metadata service. Applications running inside of instances access the " -"OpenStack metadata service by making HTTP GET requests to a web server with " -"IP address 169.254.169.254. In an OpenStack deployment, there is no host " -"with this IP address. Instead, OpenStack uses DNAT to change the destination " -"IP of these packets so they reach the network interface that a metadata " -"service is listening on." -msgstr "" - -#: ../intro_network_address_translation.rst:64 -msgid "" -"OpenStack uses SNAT to enable applications running inside of instances to " -"connect out to the public Internet." -msgstr "" - -#: ../intro_basic_networking.rst:250 -msgid "" -"OpenStack uses a third-party program called dnsmasq_ to implement the DHCP " -"server. Dnsmasq writes to the syslog (normally found at /var/log/syslog), " -"where you can observe the DHCP request and replies::" -msgstr "" - -#: ../adv_config_operational.rst:3 -msgid "Operational" -msgstr "" - -#: ../scenario_l3ha_ovs.rst:124 -msgid "" -"Operational OpenStack Compute controller/management service with appropriate " -"configuration to use OpenStack Networking in the :file:`neutron.conf` file." -msgstr "" - -#: ../scenario_l3ha_ovs.rst:106 -msgid "" -"Operational OpenStack Compute controller/management service with appropriate " -"configuration to use OpenStack Networking in the :file:`nova.conf` file." -msgstr "" - -# #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_dvr_ovs.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_l3ha_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../deploy_scenario4b.rst:92 ../deploy_scenario4b.rst:102 -#: ../scenario_dvr_ovs.rst:88 ../scenario_l3ha_lb.rst:102 -#: ../scenario_legacy_lb.rst:120 ../scenario_legacy_lb.rst:137 -#: ../scenario_legacy_ovs.rst:125 ../scenario_legacy_ovs.rst:143 -#: ../scenario_provider_ovs.rst:87 ../scenario_provider_ovs.rst:97 -msgid "" -"Operational OpenStack Compute controller/management service with appropriate " -"configuration to use neutron in the :file:`nova.conf` file." -msgstr "" - -# #-#-#-#-# scenario_dvr_ovs.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_l3ha_lb.pot (Networking Guide 0.9) #-#-#-#-# -#: ../scenario_dvr_ovs.rst:105 ../scenario_l3ha_lb.rst:119 -msgid "" -"Operational OpenStack Compute hypervisor service with appropriate " -"configuration to use neutron in the :file:`nova.conf` file." -msgstr "" - -# #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_dvr_ovs.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_l3ha_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_l3ha_ovs.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../deploy_scenario4b.rst:90 ../deploy_scenario4b.rst:100 -#: ../scenario_dvr_ovs.rst:86 ../scenario_dvr_ovs.rst:95 -#: ../scenario_dvr_ovs.rst:103 ../scenario_l3ha_lb.rst:100 -#: ../scenario_l3ha_lb.rst:109 ../scenario_l3ha_lb.rst:117 -#: ../scenario_l3ha_ovs.rst:104 ../scenario_l3ha_ovs.rst:114 -#: ../scenario_l3ha_ovs.rst:122 ../scenario_legacy_lb.rst:118 -#: ../scenario_legacy_lb.rst:127 ../scenario_legacy_lb.rst:135 -#: ../scenario_legacy_ovs.rst:123 ../scenario_legacy_ovs.rst:133 -#: ../scenario_legacy_ovs.rst:141 ../scenario_provider_ovs.rst:85 -#: ../scenario_provider_ovs.rst:95 -msgid "" -"Operational OpenStack Identity service with appropriate configuration in " -"the :file:`neutron.conf` file." -msgstr "" - # #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# # #-#-#-#-# scenario_dvr_ovs.pot (Networking Guide 0.9) #-#-#-#-# # #-#-#-#-# scenario_l3ha_lb.pot (Networking Guide 0.9) #-#-#-#-# @@ -3981,79 +2117,135 @@ msgid "" "file:`neutron.conf` file." msgstr "" -#: ../migration_nova_network_to_neutron.rst:61 -msgid "Operations impact" -msgstr "" - -#: ../config_ml2_plug_in.rst:52 ../config_ml2_plug_in.rst:56 -msgid "Option stanza/section" -msgstr "" - -#: ../config_ml2_plug_in.rst:77 -msgid "Options" -msgstr "" - -#: ../adv_config_ipv6.rst:567 -msgid "Or to run in headless mode::" -msgstr "" - -#: ../adv_config_ipv6.rst:282 -msgid "Other Configuration Flag = 0 New or existing" -msgstr "" - -#: ../adv_config_ipv6.rst:323 -msgid "Other Configuration Flag = 1" -msgstr "" - +# #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_dvr_ovs.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_l3ha_lb.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_l3ha_ovs.pot (Networking Guide 0.9) #-#-#-#-# # #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# # #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../scenario_legacy_lb.rst:52 ../scenario_legacy_ovs.rst:52 +# #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../deploy_scenario4b.rst:90 ../deploy_scenario4b.rst:100 +#: ../scenario_dvr_ovs.rst:86 ../scenario_dvr_ovs.rst:95 +#: ../scenario_dvr_ovs.rst:103 ../scenario_l3ha_lb.rst:100 +#: ../scenario_l3ha_lb.rst:109 ../scenario_l3ha_lb.rst:117 +#: ../scenario_l3ha_ovs.rst:104 ../scenario_l3ha_ovs.rst:114 +#: ../scenario_l3ha_ovs.rst:122 ../scenario_legacy_lb.rst:118 +#: ../scenario_legacy_lb.rst:127 ../scenario_legacy_lb.rst:135 +#: ../scenario_legacy_ovs.rst:123 ../scenario_legacy_ovs.rst:133 +#: ../scenario_legacy_ovs.rst:141 ../scenario_provider_ovs.rst:85 +#: ../scenario_provider_ovs.rst:95 msgid "" -"Other supporting services include DHCP and metadata. The DHCP service " -"manages IP addresses for instances on project networks. The metadata service " -"provides an API for instances on project networks to obtain metadata such as " -"SSH keys." +"Operational OpenStack Identity service with appropriate configuration in " +"the :file:`neutron.conf` file." msgstr "" -#: ../config_ml2_plug_in.rst:6 -msgid "Overview" -msgstr "" - -#: ../intro_os_networking_overview.rst:3 -msgid "Overview and components" -msgstr "" - -#: ../intro_os_networking_service.rst:9 ../intro_os_networking_service.rst:17 -#: ../intro_os_networking_service.rst:25 ../intro_os_networking_service.rst:38 -#: ../intro_os_networking_service.rst:42 ../intro_os_networking_service.rst:49 -#: ../intro_os_networking_service.rst:53 ../intro_os_networking_service.rst:60 -msgid "Overview and concepts" -msgstr "" - -#: ../adv_config_sriov.rst:192 +# #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_dvr_ovs.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_l3ha_lb.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../deploy_scenario4b.rst:92 ../deploy_scenario4b.rst:102 +#: ../scenario_dvr_ovs.rst:88 ../scenario_l3ha_lb.rst:102 +#: ../scenario_legacy_lb.rst:120 ../scenario_legacy_lb.rst:137 +#: ../scenario_legacy_ovs.rst:125 ../scenario_legacy_ovs.rst:143 +#: ../scenario_provider_ovs.rst:87 ../scenario_provider_ovs.rst:97 msgid "" -"PCI ``vendor_id`` and ``product_id`` as displayed by the Linux utility " -"``lspci``." +"Operational OpenStack Compute controller/management service with appropriate " +"configuration to use neutron in the :file:`nova.conf` file." msgstr "" -#: ../adv_config_sriov.rst:182 +#: ../deploy_scenario4b.rst:94 msgid "" -"PCI address: The address uses the same syntax as in ``lspci`` and an " -"asterisk (*) can be used to match anything." +"Neutron server service, ML2 plug-in, Linux bridge agent, DHCP agent, and any " +"dependencies." msgstr "" -#: ../adv_config_sriov.rst:13 +# #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_dvr_ovs.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_l3ha_lb.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_l3ha_ovs.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../deploy_scenario4b.rst:98 ../scenario_dvr_ovs.rst:101 +#: ../scenario_l3ha_lb.rst:115 ../scenario_l3ha_ovs.rst:120 +#: ../scenario_legacy_lb.rst:133 ../scenario_legacy_ovs.rst:139 +#: ../scenario_provider_ovs.rst:93 +msgid "OpenStack services - compute nodes" +msgstr "" + +# #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_l3ha_lb.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# +#: ../deploy_scenario4b.rst:104 ../scenario_l3ha_lb.rst:121 +#: ../scenario_legacy_lb.rst:139 +msgid "ML2 plug-in, Linux bridge agent, and any dependencies." +msgstr "" + +# #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../deploy_scenario4b.rst:109 ../scenario_provider_ovs.rst:105 msgid "" -"PCI-SIG Single Root I/O Virtualization and Sharing (SR-IOV) specification " -"defines a standardized mechanism to virtualize PCIe devices. The mechanism " -"can virtualize a single PCIe Ethernet controller to appear as multiple PCIe " -"devices. You can directly assign each virtual PCIe device to a VM, bypassing " -"the hypervisor and virtual switch layer. As a result, users are able to " -"achieve low latency and near-line wire speed." +"The general provider network architecture uses physical network " +"infrastructure to handle switching and routing of network traffic." msgstr "" -#: ../adv_config_sriov.rst:28 -msgid "PF" +# #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../deploy_scenario4b.rst:115 ../scenario_provider_ovs.rst:111 +msgid "The controller node contains the following network components:" +msgstr "" + +# #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_l3ha_lb.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# +#: ../deploy_scenario4b.rst:117 ../scenario_l3ha_lb.rst:131 +#: ../scenario_legacy_lb.rst:158 +msgid "" +"Linux bridge agent managing virtual switches, connectivity among them, and " +"interaction via virtual ports with other network components such as " +"namespaces and underlying interfaces." +msgstr "" + +# #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../deploy_scenario4b.rst:120 ../scenario_provider_ovs.rst:116 +msgid "" +"DHCP agent managing the ``qdhcp`` namespaces. The ``qdhcp`` namespaces " +"provide DHCP services for instances using provider networks." +msgstr "" + +# #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../deploy_scenario4b.rst:130 ../deploy_scenario4b.rst:146 +#: ../scenario_provider_ovs.rst:126 ../scenario_provider_ovs.rst:147 +msgid "" +"For illustration purposes, the diagram contains two different provider " +"networks." +msgstr "" + +# #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_dvr_ovs.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_l3ha_lb.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../deploy_scenario4b.rst:133 ../scenario_dvr_ovs.rst:148 +#: ../scenario_l3ha_lb.rst:152 ../scenario_legacy_lb.rst:175 +#: ../scenario_legacy_ovs.rst:181 ../scenario_provider_ovs.rst:129 +msgid "The compute nodes contain the following network components:" +msgstr "" + +# #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_l3ha_lb.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# +#: ../deploy_scenario4b.rst:135 ../scenario_l3ha_lb.rst:154 +#: ../scenario_legacy_lb.rst:177 +msgid "" +"Linux bridge agent managing virtual switches, connectivity among them, and " +"interaction via virtual ports with other network components such as " +"namespaces, security groups, and underlying interfaces." msgstr "" # #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# @@ -4070,162 +2262,59 @@ msgstr "" msgid "Packet flow" msgstr "" -#: ../scenario_dvr_ovs.rst:444 -msgid "" -"Packets arriving from compute node 1 do not traverse the project network " -"interfaces (5,6) in the ``qrouter`` namespace on compute node 2. However, " -"return traffic traverses them." -msgstr "" - -#: ../migration_nova_network_to_neutron.rst:81 -msgid "Performance impact" -msgstr "" - -#: ../adv_config_sriov.rst:146 -msgid "Persist created VFs on reboot:" -msgstr "" - -#: ../adv_config_sriov.rst:29 -msgid "" -"Physical Function. This is the physical ethernet controller that supports SR-" -"IOV." -msgstr "" - -#: ../intro_os_networking_service.rst:14 -msgid "Plug-ins" -msgstr "" - -#: ../intro_os_networking_overview.rst:32 -msgid "" -"Plugs and unplugs ports, creates networks or subnets, and provides IP " -"addressing. The chosen plug-in and agents differ depending on the vendor and " -"technologies used in the particular cloud. It is important to mention that " -"only one plug-in can be used at a time." -msgstr "" - -#: ../intro_os_networking_overview.rst:114 -msgid "Ports" -msgstr "" - -#: ../adv_config_qos.rst:164 -msgid "Ports can be created with a policy attached to them too." -msgstr "" - -#: ../adv_config_ipv6.rst:450 -msgid "Prefix delegation" -msgstr "" - -#: ../adv_config_ipv6.rst:460 -msgid "" -"Prefix delegation will be in the upcoming Liberty release, it is not " -"available in the current OpenStack Kilo release. HA and DVR routers are not " -"currently supported by this feature." -msgstr "" - # #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_dvr_ovs.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_l3ha_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_l3ha_ovs.pot (Networking Guide 0.9) #-#-#-#-# # #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# # #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# # #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../deploy_scenario4b.rst:48 ../scenario_dvr_ovs.rst:28 -#: ../scenario_l3ha_lb.rst:43 ../scenario_l3ha_ovs.rst:42 -#: ../scenario_legacy_lb.rst:63 ../scenario_legacy_ovs.rst:62 -#: ../scenario_provider_ovs.rst:41 -msgid "Prerequisites" -msgstr "" - -# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../scenario_legacy_lb.rst:13 ../scenario_legacy_ovs.rst:13 -msgid "Project (tenant) networks" -msgstr "" - -# #-#-#-#-# scenario_dvr_ovs.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../scenario_dvr_ovs.rst:196 ../scenario_dvr_ovs.rst:282 -#: ../scenario_legacy_lb.rst:207 ../scenario_legacy_lb.rst:303 -#: ../scenario_legacy_lb.rst:471 ../scenario_legacy_ovs.rst:216 -#: ../scenario_legacy_ovs.rst:308 ../scenario_legacy_ovs.rst:535 -msgid "Project network" -msgstr "" - -# #-#-#-#-# scenario_dvr_ovs.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../scenario_dvr_ovs.rst:370 ../scenario_legacy_lb.rst:389 -#: ../scenario_legacy_ovs.rst:395 -msgid "Project network 1" -msgstr "" - -# #-#-#-#-# scenario_dvr_ovs.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../scenario_dvr_ovs.rst:375 ../scenario_legacy_lb.rst:394 -#: ../scenario_legacy_ovs.rst:400 -msgid "Project network 2" -msgstr "" - -#: ../scenario_dvr_ovs.rst:194 -msgid "Project network SNAT interface 192.168.1.2 with MAC address *TN*" -msgstr "" - -# #-#-#-#-# scenario_dvr_ovs.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../scenario_dvr_ovs.rst:193 ../scenario_dvr_ovs.rst:280 -#: ../scenario_legacy_lb.rst:205 ../scenario_legacy_lb.rst:301 -#: ../scenario_legacy_ovs.rst:214 ../scenario_legacy_ovs.rst:306 -msgid "Project network router interface 203.0.113.101 *TR*" -msgstr "" - -# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../scenario_legacy_lb.rst:15 ../scenario_legacy_ovs.rst:15 +#: ../deploy_scenario4b.rst:153 ../scenario_legacy_lb.rst:191 +#: ../scenario_legacy_ovs.rst:200 ../scenario_provider_ovs.rst:154 msgid "" -"Project networks provide connectivity to instances for a particular project. " -"Regular (non-privileged) users can manage project networks within the " -"allocation that an administrator or operator defines for for them. Project " -"networks can use VLAN, GRE, or VXLAN transport methods depending on the " -"allocation. Project networks generally use private IP address ranges " -"(RFC1918) and lack connectivity to external networks such as the Internet. " -"Networking refers to IP addresses on project networks as *fixed* IP " -"addresses." -msgstr "" - -#: ../scenario_l3ha_lb.rst:91 -msgid "Proper operation of VXLAN requires kernel 3.13 or newer." -msgstr "" - -# #-#-#-#-# scenario_l3ha_ovs.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../scenario_l3ha_ovs.rst:94 ../scenario_legacy_ovs.rst:113 -msgid "" -"Proper operation of this scenario requires Open vSwitch 2.1 or newer. VXLAN " -"also requires kernel 3.13 or newer." -msgstr "" - -#: ../scenario_dvr_ovs.rst:75 -msgid "" -"Proper operation of this scenario requires Open vSwitch 2.1 or newer. VXLAN " -"requires kernel 3.13 or newer. Also, the Kilo release increases stability " -"and reliability of DVR considerably over the Juno release." -msgstr "" - -#: ../scenario_legacy_lb.rst:109 -msgid "Proper operation of this scenario requires kernel 3.13 or newer." -msgstr "" - -#: ../config_ml2_plug_in.rst:68 -msgid "Proprietary (vendor)" +"*North-south* network traffic travels between an instance and external " +"network, typically the Internet. *East-west* network traffic travels between " +"instances." msgstr "" # #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# # #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../deploy_scenario4b.rst:290 ../scenario_provider_ovs.rst:307 -msgid "Provider network" +#: ../deploy_scenario4b.rst:158 ../scenario_provider_ovs.rst:164 +msgid "Case 1: North-south" +msgstr "" + +# #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../deploy_scenario4b.rst:160 ../scenario_provider_ovs.rst:166 +msgid "" +"The physical network infrastructure handles routing and potentially other " +"services between the provider and external network. In this case, *provider* " +"and *external* simply differentiate between a network available to instances " +"and a network only accessible via router, respectively, to illustrate that " +"the physical network infrastructure handles routing. However, provider " +"networks support direct connection to *external* networks such as the " +"Internet." +msgstr "" + +# #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_dvr_ovs.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../deploy_scenario4b.rst:168 ../scenario_dvr_ovs.rst:188 +#: ../scenario_dvr_ovs.rst:275 ../scenario_legacy_lb.rst:201 +#: ../scenario_legacy_lb.rst:297 ../scenario_legacy_ovs.rst:210 +#: ../scenario_legacy_ovs.rst:302 ../scenario_provider_ovs.rst:174 +msgid "External network" +msgstr "" + +# #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_dvr_ovs.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../deploy_scenario4b.rst:170 ../scenario_dvr_ovs.rst:190 +#: ../scenario_dvr_ovs.rst:277 ../scenario_legacy_lb.rst:203 +#: ../scenario_legacy_lb.rst:299 ../scenario_legacy_ovs.rst:212 +#: ../scenario_legacy_ovs.rst:304 ../scenario_provider_ovs.rst:176 +msgid "Network 203.0.113.0/24" msgstr "" # #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# @@ -4236,174 +2325,120 @@ msgstr "" # #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# # #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../deploy_scenario4b.rst:220 ../scenario_provider_ovs.rst:230 -msgid "Provider network 1" +#: ../deploy_scenario4b.rst:174 ../scenario_provider_ovs.rst:180 +msgid "Network 192.0.2.0/24" msgstr "" # #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# # #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../deploy_scenario4b.rst:225 ../scenario_provider_ovs.rst:235 -msgid "Provider network 2" +#: ../deploy_scenario4b.rst:175 ../scenario_provider_ovs.rst:181 +msgid "Gateway 192.0.2.1 with MAC address *TG*" msgstr "" -#: ../intro_os_networking_overview.rst:88 -msgid "Provider networks" +# #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_dvr_ovs.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../deploy_scenario4b.rst:177 ../deploy_scenario4b.rst:230 +#: ../deploy_scenario4b.rst:294 ../scenario_dvr_ovs.rst:201 +#: ../scenario_dvr_ovs.rst:380 ../scenario_legacy_lb.rst:212 +#: ../scenario_legacy_lb.rst:308 ../scenario_legacy_lb.rst:399 +#: ../scenario_legacy_lb.rst:475 ../scenario_legacy_ovs.rst:221 +#: ../scenario_legacy_ovs.rst:313 ../scenario_legacy_ovs.rst:405 +#: ../scenario_legacy_ovs.rst:539 ../scenario_provider_ovs.rst:183 +#: ../scenario_provider_ovs.rst:240 ../scenario_provider_ovs.rst:311 +msgid "Compute node 1" msgstr "" # #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# # #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../deploy_scenario4b.rst:8 ../scenario_provider_ovs.rst:8 -msgid "" -"Provider networks generally offer simplicity, performance, and reliability " -"at the cost of flexibility. Unlike other scenarios, only administrators can " -"manage provider networks because they require configuration of physical " -"network infrastructure. Also, provider networks lack the concept of fixed " -"and floating IP addresses because they only handle layer-2 connectivity for " -"instances." -msgstr "" - -#: ../intro_os_networking_service.rst:11 -msgid "Provides API, manages database, etc." -msgstr "" - -#: ../intro_os_networking_service.rst:27 -msgid "Provides layer 2/3 connectivity to instances" -msgstr "" - -#: ../adv_config_sriov.rst:104 -msgid "QLogic" -msgstr "" - -#: ../adv_config_qos.rst:76 -msgid "" -"QoS currently works with ml2 only (SR-IOV and Open vSwitch are the only " -"drivers that are enabled for QoS in Liberty release)." -msgstr "" - -#: ../adv_config_qos.rst:25 -msgid "" -"QoS is an advanced service plug-in. QoS is decoupled from the rest of the " -"Neutron code on multiple levels and it is available through the ml2 " -"extension driver." -msgstr "" - -#: ../adv_config_qos.rst:8 -msgid "" -"QoS is defined as the ability to guarantee certain network requirements like " -"bandwidth, latency, jitter, and reliability in order to satisfy a Service " -"Level Agreement (SLA) between an application provider and end users." -msgstr "" - -#: ../adv_config_sriov.rst:64 -msgid "" -"QoS is supported since Liberty, while it has limitations. max_burst_kbps " -"(burst over max_kbps) is not supported. max_kbps is rounded to Mbps." -msgstr "" - -#: ../adv_config_qos.rst:100 -msgid "" -"QoS policies are only created by admins with the default ``policy.json``. " -"Therefore, you should have the Cloud Operator to set up them on behalf of " -"the Cloud tenants." -msgstr "" - -#: ../migration_nova_network_to_neutron.rst:116 -msgid "Re-enable the hypervisor." -msgstr "" - -#: ../migration_nova_network_to_neutron.rst:115 -msgid "" -"Reboot the hypervisor (or run \"smart\" live transition tool if available)." -msgstr "" - -#: ../config_server.rst:12 -msgid "Reference common configuration items" -msgstr "" - -#: ../adv_config_ipv6.rst:672 -msgid "References" -msgstr "" - -#: ../adv_config_ipv6.rst:210 -msgid "Referencing a subnet pool during subnet creation" -msgstr "" - -# #-#-#-#-# scenario_dvr_ovs.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_l3ha_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_l3ha_ovs.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../scenario_dvr_ovs.rst:631 ../scenario_dvr_ovs.rst:718 -#: ../scenario_l3ha_lb.rst:357 ../scenario_l3ha_ovs.rst:367 -#: ../scenario_legacy_lb.rst:676 ../scenario_legacy_ovs.rst:777 -msgid "Replace ``METADATA_SECRET`` with a suitable value for your environment." -msgstr "" - -# #-#-#-#-# scenario_dvr_ovs.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_l3ha_ovs.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../scenario_dvr_ovs.rst:513 ../scenario_l3ha_ovs.rst:252 -#: ../scenario_legacy_ovs.rst:662 -msgid "" -"Replace ``MIN_VLAN_ID``, ``MAX_VLAN_ID``, ``MIN_GRE_ID``, ``MAX_GRE_ID``, " -"``MIN_VXLAN_ID``, and ``MAX_VXLAN_ID`` with VLAN, GRE, and VXLAN ID minimum " -"and maximum values suitable for your environment." -msgstr "" - -# #-#-#-#-# scenario_l3ha_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# -#: ../scenario_l3ha_lb.rst:240 ../scenario_legacy_lb.rst:564 -msgid "" -"Replace ``MIN_VLAN_ID``, ``MAX_VLAN_ID``, ``MIN_VXLAN_ID``, and " -"``MAX_VXLAN_ID`` with VLAN and VXLAN ID minimum and maximum values suitable " -"for your environment." -msgstr "" - -# #-#-#-#-# scenario_l3ha_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# -#: ../scenario_l3ha_lb.rst:299 ../scenario_l3ha_lb.rst:410 -#: ../scenario_legacy_lb.rst:623 -msgid "" -"Replace ``PROJECT_VLAN_INTERFACE`` and ``EXTERNAL_INTERFACE`` with the name " -"of the underlying interface that handles VLAN project networks and external " -"networks, respectively. Replace ``TUNNEL_INTERFACE_IP_ADDRESS`` with the IP " -"address of the interface that handles project tunnel networks." -msgstr "" - -#: ../scenario_legacy_lb.rst:729 -msgid "" -"Replace ``PROJECT_VLAN_INTERFACE`` with the name of the underlying interface " -"that handles VLAN project networks and external networks, respectively. " -"Replace ``TUNNEL_INTERFACE_IP_ADDRESS`` with the IP address of the interface " -"that handles VXLAN project networks." +#: ../deploy_scenario4b.rst:179 ../scenario_provider_ovs.rst:185 +msgid "Instance 1 192.0.2.11 with MAC address *I1*" msgstr "" # #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# # #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../deploy_scenario4b.rst:413 ../deploy_scenario4b.rst:481 -#: ../scenario_provider_ovs.rst:469 ../scenario_provider_ovs.rst:532 -msgid "" -"Replace ``PROVIDER_INTERFACE`` with the name of the underlying interface " -"that handles provider networks. For example, ``eth1``." +#: ../deploy_scenario4b.rst:181 ../scenario_provider_ovs.rst:187 +msgid "Instance 1 resides on compute node 1 and uses a provider network." msgstr "" +# #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# # #-#-#-#-# scenario_dvr_ovs.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_l3ha_ovs.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# # #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../scenario_dvr_ovs.rst:575 ../scenario_dvr_ovs.rst:689 -#: ../scenario_l3ha_ovs.rst:311 ../scenario_l3ha_ovs.rst:421 -#: ../scenario_legacy_ovs.rst:722 ../scenario_legacy_ovs.rst:832 +# #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../deploy_scenario4b.rst:182 ../scenario_dvr_ovs.rst:207 +#: ../scenario_legacy_lb.rst:217 ../scenario_legacy_ovs.rst:226 +#: ../scenario_provider_ovs.rst:188 +msgid "The instance sends a packet to a host on the external network." +msgstr "" + +# #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../deploy_scenario4b.rst:184 ../scenario_provider_ovs.rst:190 +msgid "The following steps involve compute node 1." +msgstr "" + +#: ../deploy_scenario4b.rst:186 msgid "" -"Replace ``TUNNEL_INTERFACE_IP_ADDRESS`` with the IP address of the interface " -"that handles GRE/VXLAN project networks." +"The instance 1 ``tap`` interface (1) forwards the packet to the provider " +"bridge ``qbr``. The packet contains destination MAC address *TG* because the " +"destination resides on another network." msgstr "" -#: ../adv_config_ipv6.rst:487 -msgid "Requirements" +#: ../deploy_scenario4b.rst:189 +msgid "" +"Security group rules (2) on the provider bridge ``qbr`` handle firewalling " +"and tracking for the packet." msgstr "" -#: ../adv_config_ipv6.rst:265 ../adv_config_ipv6.rst:305 -msgid "Result" +#: ../deploy_scenario4b.rst:191 ../deploy_scenario4b.rst:249 +#: ../deploy_scenario4b.rst:314 +msgid "" +"The provider bridge ``qbr`` forwards the packet to the logical VLAN " +"interface ``device.sid`` where *device* references the underlying physical " +"provider interface and *sid* contains the provider network segmentation ID." +msgstr "" + +#: ../deploy_scenario4b.rst:195 +msgid "" +"The logical VLAN interface ``device.sid`` forwards the packet to the " +"physical network via the physical provider interface." +msgstr "" + +# #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../deploy_scenario4b.rst:198 ../deploy_scenario4b.rst:256 +#: ../deploy_scenario4b.rst:321 ../scenario_provider_ovs.rst:208 +#: ../scenario_provider_ovs.rst:270 ../scenario_provider_ovs.rst:342 +msgid "The following steps involve the physical network infrastructure:" +msgstr "" + +#: ../deploy_scenario4b.rst:200 +msgid "" +"A switch (3) handles any VLAN tag operations between the provider network " +"and the router (4)." +msgstr "" + +#: ../deploy_scenario4b.rst:202 +msgid "" +"A router (4) routes the packet from the provider network to the external " +"network." +msgstr "" + +# #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../deploy_scenario4b.rst:204 ../scenario_provider_ovs.rst:214 +msgid "" +"A switch (3) handles any VLAN tag operations between the router (4) and the " +"external network." +msgstr "" + +# #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../deploy_scenario4b.rst:206 ../scenario_provider_ovs.rst:216 +msgid "A switch (3) forwards the packet to the external network." msgstr "" # #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# @@ -4422,251 +2457,128 @@ msgstr "" msgid "Return traffic follows similar steps in reverse." msgstr "" -#: ../adv_config_ipv6.rst:76 -msgid "Router advertisements" +# #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../deploy_scenario4b.rst:215 ../scenario_provider_ovs.rst:225 +msgid "Case 2: East-west for instances on different networks" msgstr "" -#: ../adv_config_ipv6.rst:326 -msgid "Router support" -msgstr "" - -# #-#-#-#-# intro_networking_components.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# intro_os_networking_overview.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../intro_networking_components.rst:14 -#: ../intro_os_networking_overview.rst:122 ../scenario_legacy_lb.rst:39 -#: ../scenario_legacy_ovs.rst:39 -msgid "Routers" -msgstr "" - -# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../scenario_legacy_lb.rst:41 ../scenario_legacy_ovs.rst:41 +# #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../deploy_scenario4b.rst:217 ../scenario_provider_ovs.rst:227 msgid "" -"Routers typically connect project and external networks. By default, they " -"implement SNAT to provide outbound external connectivity for instances on " -"project networks. Each router uses an IP address in the external network " -"allocation for SNAT. Routers also use DNAT to provide inbound external " -"connectivity for instances on project networks. Networking refers to IP " -"addresses on routers that provide inbound external connectivity for " -"instances on project networks as *floating* IP addresses. Routers can also " -"connect project networks that belong to the same project." +"The physical network infrastructure handles routing between the provider " +"networks." msgstr "" -#: ../intro_os_networking_service.rst:66 -msgid "Routing services" +# #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../deploy_scenario4b.rst:220 ../scenario_provider_ovs.rst:230 +msgid "Provider network 1" msgstr "" -#: ../adv_config_qos.rst:220 -msgid "Rule modification" +# #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../deploy_scenario4b.rst:222 ../deploy_scenario4b.rst:292 +#: ../scenario_provider_ovs.rst:232 ../scenario_provider_ovs.rst:309 +msgid "Network: 192.0.2.0/24" msgstr "" -#: ../migration_nova_network_to_neutron.rst:94 -msgid "" -"Run a DB dump/restore tool that creates Networking data structures " -"representing current legacy networking config." +# #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../deploy_scenario4b.rst:223 ../scenario_provider_ovs.rst:233 +msgid "Gateway: 192.0.2.1 with MAC address *TG1*" msgstr "" -#: ../adv_config_sriov.rst:122 -msgid "Run the following if you have added new parameters:" +# #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../deploy_scenario4b.rst:225 ../scenario_provider_ovs.rst:235 +msgid "Provider network 2" msgstr "" -#: ../adv_config_ipv6.rst:267 ../adv_config_ipv6.rst:270 -#: ../adv_config_ipv6.rst:271 -msgid "SLAAC" +# #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../deploy_scenario4b.rst:227 ../scenario_provider_ovs.rst:237 +msgid "Network: 198.51.100.0/24" msgstr "" -#: ../intro_network_address_translation.rst:22 -msgid "SNAT" +# #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../deploy_scenario4b.rst:228 ../scenario_provider_ovs.rst:238 +msgid "Gateway: 198.51.100.1 with MAC address *TG2*" msgstr "" -#: ../intro_network_address_translation.rst:47 -msgid "" -"SNAT solves this problem by modifying the source IP address to an IP address " -"that is routable on the public Internet. There are different variations of " -"SNAT; in the form that OpenStack deployments use, a NAT router on the path " -"between the sender and receiver replaces the packet's source IP address with " -"the router's public IP address. The router also modifies the source TCP or " -"UDP port to another value, and the router maintains a record of the sender's " -"true IP address and port, as well as the modified IP address and port." -msgstr "" - -#: ../scenario_dvr_ovs.rst:3 -msgid "Scenario: High Availability using Distributed Virtual Routing (DVR)" -msgstr "" - -#: ../scenario_l3ha_lb.rst:3 -msgid "Scenario: High Availability using VRRP (L3HA) with Linux Bridge" -msgstr "" - -#: ../scenario_l3ha_ovs.rst:3 -msgid "Scenario: High Availability using VRRP (L3HA) with Open vSwitch" -msgstr "" - -#: ../scenario_legacy_lb.rst:3 -msgid "Scenario: Legacy with Linux Bridge" -msgstr "" - -#: ../scenario_legacy_ovs.rst:3 -msgid "Scenario: Legacy with Open vSwitch" -msgstr "" - -#: ../deploy_scenario4b.rst:3 -msgid "Scenario: Provider networks with Linux bridge" -msgstr "" - -#: ../scenario_provider_ovs.rst:3 -msgid "Scenario: Provider networks with Open vSwitch" -msgstr "" - -#: ../index.rst:43 -msgid "Search in this guide" -msgstr "" - -#: ../adv_config_qos.rst:136 -msgid "" -"Second, associate the created policy with an existing neutron port. In order " -"to do this, user extracts the port id to be associated to the already " -"created policy. In the next example, we will assign the ``bw-limiter`` " -"policy to the VM with IP address 10.0.0.3" -msgstr "" - -#: ../config_ml2_plug_in.rst:75 -msgid "Security" -msgstr "" - -#: ../adv_config_sriov.rst:67 -msgid "" -"Security Group is not supported. the agent is only working with " -"``firewall_driver = neutron.agent.firewall.NoopFirewallDriver``." -msgstr "" - -#: ../adv_config_ipv6.rst:413 -msgid "Security considerations" -msgstr "" - -#: ../scenario_legacy_lb.rst:453 -msgid "" -"Security group rules (10) on the VLAN bridge ``qbr`` handle firewalling and " -"state tracking for the packet." -msgstr "" - -#: ../scenario_provider_ovs.rst:195 ../scenario_provider_ovs.rst:257 -#: ../scenario_provider_ovs.rst:329 -msgid "" -"Security group rules (2) on the Linux bridge ``qbr`` handle firewalling and " -"state tracking for the packet." +# #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../deploy_scenario4b.rst:232 ../deploy_scenario4b.rst:296 +#: ../scenario_provider_ovs.rst:242 ../scenario_provider_ovs.rst:313 +msgid "Instance 1: 192.0.2.11 with MAC address *I1*" msgstr "" +# #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# # #-#-#-#-# scenario_dvr_ovs.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../scenario_dvr_ovs.rst:218 ../scenario_dvr_ovs.rst:404 -#: ../scenario_legacy_ovs.rst:233 ../scenario_legacy_ovs.rst:423 -msgid "" -"Security group rules (2) on the Linux bridge ``qbr`` handle state tracking " -"for the packet." -msgstr "" - -#: ../deploy_scenario4b.rst:312 -msgid "" -"Security group rules (2) on the provider bridge ``qbr`` handle firewalling " -"and state tracking for the packet." -msgstr "" - -#: ../deploy_scenario4b.rst:189 -msgid "" -"Security group rules (2) on the provider bridge ``qbr`` handle firewalling " -"and tracking for the packet." -msgstr "" - -#: ../scenario_legacy_ovs.rst:558 -msgid "" -"Security group rules (2) on the provider bridge ``qbr`` handle state " -"tracking for the packet." -msgstr "" - -#: ../scenario_legacy_lb.rst:230 ../scenario_legacy_lb.rst:417 -#: ../scenario_legacy_lb.rst:494 -msgid "" -"Security group rules (2) on the tunnel bridge ``qbr`` handle state tracking " -"for the packet." -msgstr "" - -#: ../scenario_legacy_ovs.rst:604 -msgid "" -"Security group rules (3) on the Linux bridge ``qbr`` handle firewalling and " -"state tracking for the packet." -msgstr "" - +# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# # #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# # #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../scenario_legacy_ovs.rst:377 ../scenario_provider_ovs.rst:356 -msgid "" -"Security group rules (4) on the Linux bridge ``qbr`` handle firewalling and " -"state tracking for the packet." +#: ../deploy_scenario4b.rst:234 ../deploy_scenario4b.rst:298 +#: ../scenario_dvr_ovs.rst:385 ../scenario_legacy_lb.rst:403 +#: ../scenario_legacy_lb.rst:479 ../scenario_legacy_ovs.rst:409 +#: ../scenario_legacy_ovs.rst:543 ../scenario_provider_ovs.rst:244 +#: ../scenario_provider_ovs.rst:315 +msgid "Compute node 2" msgstr "" -#: ../deploy_scenario4b.rst:333 -msgid "" -"Security group rules (4) on the provider bridge ``qbr`` handle firewalling " -"and state tracking for the packet." +# #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../deploy_scenario4b.rst:236 ../scenario_provider_ovs.rst:246 +msgid "Instance 2: 198.51.100.11 with MAC address *I2*" msgstr "" +# #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../deploy_scenario4b.rst:238 ../scenario_provider_ovs.rst:248 +msgid "Instance 1 resides on compute node 1 and uses provider network 1." +msgstr "" + +# #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../deploy_scenario4b.rst:239 ../scenario_provider_ovs.rst:249 +msgid "Instance 2 resides on compute node 2 and uses provider network 2." +msgstr "" + +# #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_dvr_ovs.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# # #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# # #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../scenario_legacy_ovs.rst:517 ../scenario_provider_ovs.rst:290 -msgid "" -"Security group rules (5) on the Linux bridge ``qbr`` handle firewalling and " -"state tracking for the packet." +#: ../deploy_scenario4b.rst:240 ../deploy_scenario4b.rst:305 +#: ../scenario_dvr_ovs.rst:393 ../scenario_legacy_lb.rst:410 +#: ../scenario_legacy_lb.rst:486 ../scenario_legacy_ovs.rst:416 +#: ../scenario_legacy_ovs.rst:550 ../scenario_provider_ovs.rst:250 +#: ../scenario_provider_ovs.rst:322 +msgid "Instance 1 sends a packet to instance 2." msgstr "" -#: ../deploy_scenario4b.rst:274 -msgid "" -"Security group rules (5) on the provider bridge ``qbr`` handle firewalling " -"and state tracking for the packet." +# #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_dvr_ovs.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../deploy_scenario4b.rst:242 ../deploy_scenario4b.rst:307 +#: ../scenario_dvr_ovs.rst:213 ../scenario_dvr_ovs.rst:399 +#: ../scenario_legacy_lb.rst:223 ../scenario_legacy_lb.rst:349 +#: ../scenario_legacy_lb.rst:412 ../scenario_legacy_lb.rst:489 +#: ../scenario_legacy_ovs.rst:228 ../scenario_legacy_ovs.rst:355 +#: ../scenario_legacy_ovs.rst:418 ../scenario_legacy_ovs.rst:553 +#: ../scenario_provider_ovs.rst:252 ../scenario_provider_ovs.rst:324 +msgid "The following steps involve compute node 1:" msgstr "" -#: ../scenario_legacy_lb.rst:509 +#: ../deploy_scenario4b.rst:244 msgid "" -"Security group rules (5) on the tunnel bridge ``qbr`` handle firewalling and " -"state tracking for the packet." -msgstr "" - -#: ../scenario_legacy_lb.rst:358 -msgid "" -"Security group rules (6) on the tunnel bridge ``qbr`` handle firewalling and " -"state tracking for the packet." -msgstr "" - -#: ../scenario_dvr_ovs.rst:438 -msgid "" -"Security group rules (7) on the Linux bridge ``qbr`` handle firewalling and " -"state tracking for the packet." -msgstr "" - -#: ../scenario_dvr_ovs.rst:326 -msgid "" -"Security group rules (8) on the Linux bridge ``qbr`` handle firewalling and " -"state tracking for the packet." -msgstr "" - -#: ../scenario_dvr_ovs.rst:337 -msgid "" -"Security group rules (8) on the Linux bridge ``qbr`` handle state tracking " -"for the packet." -msgstr "" - -#: ../scenario_legacy_lb.rst:371 -msgid "" -"Security group rules on the VLAN bridge ``qbr`` handle firewalling and state " -"tracking for the packet." -msgstr "" - -#: ../scenario_legacy_lb.rst:243 -msgid "" -"Security group rules on the VLAN bridge ``qbr`` handle state tracking for " -"the packet." +"The instance 1 ``tap`` interface forwards the packet to the provider bridge " +"``qbr``. The packet contains destination MAC address *TG1* because the " +"destination resides on another network." msgstr "" #: ../deploy_scenario4b.rst:247 @@ -4675,115 +2587,159 @@ msgid "" "state tracking for the packet." msgstr "" -#: ../intro_os_networking_overview.rst:130 -msgid "Security groups" -msgstr "" - -#: ../intro_os_networking_overview.rst:139 +#: ../deploy_scenario4b.rst:253 ../deploy_scenario4b.rst:318 msgid "" -"Security groups and security group rules give administrators and tenants the " -"ability to specify the type of traffic and direction (ingress/egress) that " -"is allowed to pass through a port. A security group is a container for " -"security group rules. When a port is created, it is associated with a " -"security group. If a security group is not specified, the port is associated " -"with a 'default' security group. By default, this group drops all ingress " -"traffic and allows all egress. Rules can be added to this group in order to " -"change the behavior." +"The logical VLAN interface ``device.sid`` forwards the packet to the " +"physical network infrastructure via the physical provider interface." +msgstr "" + +# #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../deploy_scenario4b.rst:258 ../scenario_provider_ovs.rst:210 +#: ../scenario_provider_ovs.rst:272 +msgid "" +"A switch (3) handles any VLAN tag operations between provider network 1 and " +"the router (4)." +msgstr "" + +# #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../deploy_scenario4b.rst:260 ../scenario_provider_ovs.rst:274 +msgid "" +"A router (4) routes the packet from provider network 1 to provider network 2." +msgstr "" + +# #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../deploy_scenario4b.rst:262 ../scenario_provider_ovs.rst:276 +msgid "" +"A switch (3) handles any VLAN tag operations between the router (4) and " +"provider network 2." +msgstr "" + +# #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../deploy_scenario4b.rst:264 ../scenario_provider_ovs.rst:278 +msgid "A switch (3) forwards the packet to compute node 2." msgstr "" -#: ../adv_config_FwaaS.rst:5 -msgid "See the following URL:" -msgstr "" - -#: ../adv_config_LBaaS.rst:5 -msgid "See the following URLs:" -msgstr "" - -# #-#-#-#-# config_server.pot (Networking Guide 0.9) #-#-#-#-# # #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# intro_os_networking_service.pot (Networking Guide 0.9) #-#-#-#-# # #-#-#-#-# scenario_dvr_ovs.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_l3ha_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_l3ha_ovs.pot (Networking Guide 0.9) #-#-#-#-# # #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# # #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# # #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../config_server.rst:3 ../deploy_scenario4b.rst:437 -#: ../intro_os_networking_service.rst:6 ../scenario_dvr_ovs.rst:528 -#: ../scenario_l3ha_lb.rst:254 ../scenario_l3ha_ovs.rst:266 -#: ../scenario_legacy_lb.rst:578 ../scenario_legacy_ovs.rst:676 -#: ../scenario_provider_ovs.rst:474 -msgid "Server" +#: ../deploy_scenario4b.rst:266 ../deploy_scenario4b.rst:325 +#: ../scenario_dvr_ovs.rst:427 ../scenario_legacy_lb.rst:446 +#: ../scenario_legacy_lb.rst:502 ../scenario_legacy_ovs.rst:495 +#: ../scenario_legacy_ovs.rst:582 ../scenario_provider_ovs.rst:280 +#: ../scenario_provider_ovs.rst:346 +msgid "The following steps involve compute node 2:" msgstr "" -#: ../intro_os_networking_service.rst:3 -msgid "Service and component hierarchy" -msgstr "" - -#: ../adv_config_service_chaining.rst:3 -msgid "Service chaining" -msgstr "" - -#: ../intro_os_networking_service.rst:63 -msgid "Services" -msgstr "" - -#: ../migration_nova_network_to_neutron.rst:114 +#: ../deploy_scenario4b.rst:268 ../deploy_scenario4b.rst:327 msgid "" -"Set the \"has_transitioned\" flag in the Compute hypervisor database/config." +"The physical provider interface forwards the packet to the logical VLAN " +"interface ``device.sid`` where *device* references the underlying physical " +"provider interface and *sid* contains the provider network segmentation ID." msgstr "" -#: ../adv_config_qos.rst:67 +#: ../deploy_scenario4b.rst:272 ../deploy_scenario4b.rst:331 msgid "" -"Set the needed notification_drivers in [qos] section (message_queue is the " -"default)." +"The logical VLAN interface ``device.sid`` forwards the packet to the " +"provider bridge ``qbr``." msgstr "" -#: ../adv_config_ipv6.rst:314 +#: ../deploy_scenario4b.rst:274 msgid "" -"Setting DHCPv6-stateless for ``ipv6_ra_mode`` configures the neutron router " -"with radvd agent to send RAs. The table below captures the values set for " -"the address configuration flags in the RA packet in this scenario. " -"Similarly, setting DHCPv6-stateless for ``ipv6_address_mode`` configures " -"neutron DHCP implementation to provide the additional network information." +"Security group rules (5) on the provider bridge ``qbr`` handle firewalling " +"and state tracking for the packet." msgstr "" -#: ../adv_config_ipv6.rst:275 +#: ../deploy_scenario4b.rst:276 msgid "" -"Setting ``ipv6_ra_mode`` to ``slaac`` will result in OpenStack Networking " -"routers being configured to send RA packets, when they are created. This " -"results in the following values set for the address configuration flags in " -"the RA messages:" +"The provider bridge ``qbr`` forwards the packet to the ``tap`` interface (6) " +"on instance 2." msgstr "" -#: ../config_ml2_plug_in.rst:28 +# #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../deploy_scenario4b.rst:285 ../scenario_provider_ovs.rst:302 +msgid "Case 3: East-west for instances on the same network" +msgstr "" + +# #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../deploy_scenario4b.rst:287 ../scenario_provider_ovs.rst:304 msgid "" -"Similar info in: http://docs.openstack.org/admin-guide-cloud/networking_adv-" -"features.html#provider-networks" +"The physical network infrastructure handles switching within the provider " +"network." msgstr "" -#: ../adv_config_ipv6.rst:36 -msgid "Single stack IPv6 tenant networking" +# #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../deploy_scenario4b.rst:290 ../scenario_provider_ovs.rst:307 +msgid "Provider network" msgstr "" -#: ../adv_config_debugging.rst:21 +# #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../deploy_scenario4b.rst:300 ../scenario_provider_ovs.rst:317 +msgid "Instance 2: 192.0.2.12 with MAC address *I2*" +msgstr "" + +# #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../deploy_scenario4b.rst:302 ../scenario_legacy_lb.rst:483 +#: ../scenario_legacy_ovs.rst:547 ../scenario_provider_ovs.rst:319 +msgid "Instance 1 resides on compute node 1." +msgstr "" + +# #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../deploy_scenario4b.rst:303 ../scenario_legacy_lb.rst:484 +#: ../scenario_legacy_ovs.rst:548 ../scenario_provider_ovs.rst:320 +msgid "Instance 2 resides on compute node 2." +msgstr "" + +# #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../deploy_scenario4b.rst:304 ../scenario_provider_ovs.rst:321 +msgid "Both instances use the same provider network." +msgstr "" + +#: ../deploy_scenario4b.rst:309 msgid "" -"Some of the following sections reference these popular tools to understand " -"both network configuration and traffic patterns:" +"The instance 1 ``tap`` interface (1) forwards the packet to the provider " +"bridge ``qbr``. The packet contains destination MAC address *I2* because the " +"destination resides on the same network." msgstr "" -#: ../intro_basic_networking.rst:172 +#: ../deploy_scenario4b.rst:312 msgid "" -"Sometimes we want to refer to a subnet, but not any particular IP address on " -"the subnet. A common convention is to set the host identifier to all zeros " -"to make reference to a subnet. For example, if a host's IP address is " -"``10.10.53.24/16``, then we would say the subnet is ``10.10.0.0/16``." +"Security group rules (2) on the provider bridge ``qbr`` handle firewalling " +"and state tracking for the packet." msgstr "" -#: ../scenario_l3ha_ovs.rst:552 +# #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../deploy_scenario4b.rst:323 ../scenario_provider_ovs.rst:344 +msgid "A switch (3) forwards the packet from compute node 1 to compute node 2." +msgstr "" + +#: ../deploy_scenario4b.rst:333 msgid "" -"Source the ``demo`` project credentials. The following steps use the " -"``demo`` project." +"Security group rules (4) on the provider bridge ``qbr`` handle firewalling " +"and state tracking for the packet." +msgstr "" + +#: ../deploy_scenario4b.rst:335 +msgid "" +"The provider bridge ``qbr`` forwards the packet to the instance 2 ``tap`` " +"interface (5)." msgstr "" # #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# @@ -4793,55 +2749,151 @@ msgstr "" # #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# # #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# # #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../deploy_scenario4b.rst:491 ../deploy_scenario4b.rst:512 -#: ../scenario_dvr_ovs.rst:730 ../scenario_dvr_ovs.rst:756 -#: ../scenario_dvr_ovs.rst:930 ../scenario_l3ha_lb.rst:422 -#: ../scenario_l3ha_lb.rst:448 ../scenario_l3ha_lb.rst:611 -#: ../scenario_l3ha_ovs.rst:432 ../scenario_l3ha_ovs.rst:458 -#: ../scenario_l3ha_ovs.rst:621 ../scenario_legacy_lb.rst:741 -#: ../scenario_legacy_lb.rst:763 ../scenario_legacy_ovs.rst:843 -#: ../scenario_legacy_ovs.rst:865 ../scenario_provider_ovs.rst:542 -#: ../scenario_provider_ovs.rst:563 -msgid "Source the administrative project credentials." -msgstr "" - -#: ../scenario_l3ha_lb.rst:790 -msgid "" -"Source the credentials for a non-privileged project. The following steps use " -"the ``demo`` project." -msgstr "" - -#: ../scenario_dvr_ovs.rst:849 ../scenario_dvr_ovs.rst:961 -msgid "Source the regular project credentials." +#: ../deploy_scenario4b.rst:345 ../scenario_dvr_ovs.rst:457 +#: ../scenario_l3ha_lb.rst:191 ../scenario_l3ha_ovs.rst:200 +#: ../scenario_legacy_lb.rst:521 ../scenario_legacy_ovs.rst:616 +#: ../scenario_provider_ovs.rst:368 +msgid "Example configuration" msgstr "" # #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_dvr_ovs.pot (Networking Guide 0.9) #-#-#-#-# # #-#-#-#-# scenario_l3ha_lb.pot (Networking Guide 0.9) #-#-#-#-# # #-#-#-#-# scenario_l3ha_ovs.pot (Networking Guide 0.9) #-#-#-#-# # #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# # #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# # #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../deploy_scenario4b.rst:578 ../scenario_l3ha_lb.rst:542 -#: ../scenario_l3ha_ovs.rst:798 ../scenario_legacy_lb.rst:856 -#: ../scenario_legacy_lb.rst:959 ../scenario_legacy_ovs.rst:958 -#: ../scenario_legacy_ovs.rst:1062 ../scenario_provider_ovs.rst:629 +#: ../deploy_scenario4b.rst:347 ../scenario_dvr_ovs.rst:459 +#: ../scenario_l3ha_lb.rst:193 ../scenario_l3ha_ovs.rst:202 +#: ../scenario_legacy_lb.rst:523 ../scenario_legacy_ovs.rst:618 +#: ../scenario_provider_ovs.rst:370 msgid "" -"Source the regular project credentials. The following steps use the ``demo`` " -"project." +"Use the following example configuration as a template to deploy this " +"scenario in your environment." msgstr "" -#: ../config_ml2_plug_in.rst:60 -msgid "Specialized" -msgstr "" - -#: ../migration_nova_network_to_neutron.rst:91 +# #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../deploy_scenario4b.rst:351 ../scenario_provider_ovs.rst:374 msgid "" -"Start neutron-server in intended final config, except with REST API " -"restricted to read-write only by nova-api." +"The lack of L3 agents in this scenario prevents operation of the " +"conventional metadata agent. You must use a configuration drive to provide " +"instance metadata." msgstr "" -#: ../scenario_provider_ovs.rst:452 ../scenario_provider_ovs.rst:515 -msgid "Start the following service:" +# #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_dvr_ovs.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_l3ha_lb.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_l3ha_ovs.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../deploy_scenario4b.rst:356 ../scenario_dvr_ovs.rst:466 +#: ../scenario_l3ha_lb.rst:197 ../scenario_l3ha_ovs.rst:206 +#: ../scenario_legacy_lb.rst:527 ../scenario_legacy_ovs.rst:622 +#: ../scenario_provider_ovs.rst:379 +msgid "Controller node" +msgstr "" + +# #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../deploy_scenario4b.rst:358 ../deploy_scenario4b.rst:444 +#: ../scenario_provider_ovs.rst:381 ../scenario_provider_ovs.rst:481 +msgid "" +"Configure the kernel to disable reverse path filtering. Edit the :file:`/etc/" +"sysctl.conf` file:" +msgstr "" + +# #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_dvr_ovs.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_l3ha_lb.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_l3ha_ovs.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../deploy_scenario4b.rst:366 ../deploy_scenario4b.rst:452 +#: ../scenario_dvr_ovs.rst:542 ../scenario_dvr_ovs.rst:656 +#: ../scenario_l3ha_lb.rst:268 ../scenario_l3ha_lb.rst:379 +#: ../scenario_l3ha_ovs.rst:280 ../scenario_l3ha_ovs.rst:390 +#: ../scenario_legacy_lb.rst:592 ../scenario_legacy_lb.rst:698 +#: ../scenario_legacy_ovs.rst:690 ../scenario_legacy_ovs.rst:800 +#: ../scenario_provider_ovs.rst:389 ../scenario_provider_ovs.rst:489 +msgid "Load the new kernel configuration:" +msgstr "" + +# #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_dvr_ovs.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_l3ha_lb.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_l3ha_ovs.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../deploy_scenario4b.rst:372 ../deploy_scenario4b.rst:458 +#: ../scenario_dvr_ovs.rst:468 ../scenario_dvr_ovs.rst:548 +#: ../scenario_dvr_ovs.rst:662 ../scenario_l3ha_lb.rst:199 +#: ../scenario_l3ha_lb.rst:274 ../scenario_l3ha_lb.rst:385 +#: ../scenario_l3ha_ovs.rst:208 ../scenario_l3ha_ovs.rst:286 +#: ../scenario_l3ha_ovs.rst:396 ../scenario_legacy_lb.rst:529 +#: ../scenario_legacy_lb.rst:598 ../scenario_legacy_lb.rst:704 +#: ../scenario_legacy_ovs.rst:624 ../scenario_legacy_ovs.rst:696 +#: ../scenario_legacy_ovs.rst:806 ../scenario_provider_ovs.rst:395 +#: ../scenario_provider_ovs.rst:495 +msgid "" +"Configure common options. Edit the :file:`/etc/neutron/neutron.conf` file:" +msgstr "" + +# #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../deploy_scenario4b.rst:382 ../scenario_provider_ovs.rst:405 +msgid "" +"The ``service_plugins`` option contains no value because the Networking " +"service does not provide layer-3 services such as routing." +msgstr "" + +#: ../deploy_scenario4b.rst:386 +msgid "" +"Configure the ML2 plug-in and Linux bridge agent. Edit the :file:`/etc/" +"neutron/plugins/ml2/ml2_conf.ini` file:" +msgstr "" + +# #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../deploy_scenario4b.rst:413 ../deploy_scenario4b.rst:481 +#: ../scenario_provider_ovs.rst:469 ../scenario_provider_ovs.rst:532 +msgid "" +"Replace ``PROVIDER_INTERFACE`` with the name of the underlying interface " +"that handles provider networks. For example, ``eth1``." +msgstr "" + +# #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../deploy_scenario4b.rst:417 ../scenario_provider_ovs.rst:434 +msgid "" +"The ``tenant_network_types`` option contains no value because the " +"architecture does not support project (private) networks." +msgstr "" + +# #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../deploy_scenario4b.rst:421 ../scenario_provider_ovs.rst:438 +msgid "" +"The ``provider`` value in the ``network_vlan_ranges`` option lacks VLAN ID " +"ranges to support use of arbitrary VLAN IDs." +msgstr "" + +# #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_dvr_ovs.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_l3ha_lb.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_l3ha_ovs.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../deploy_scenario4b.rst:424 ../scenario_dvr_ovs.rst:594 +#: ../scenario_l3ha_lb.rst:320 ../scenario_l3ha_ovs.rst:330 +#: ../scenario_legacy_lb.rst:639 ../scenario_legacy_ovs.rst:740 +#: ../scenario_provider_ovs.rst:441 +msgid "" +"Configure the DHCP agent. Edit the :file:`/etc/neutron/dhcp_agent.ini` file:" msgstr "" # #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# @@ -4864,83 +2916,13 @@ msgstr "" msgid "Start the following services:" msgstr "" -#: ../adv_config_ipv6.rst:229 -msgid "Stateless Address Auto Configuration (SLAAC)" -msgstr "" - -#: ../intro_os_networking_overview.rst:105 -msgid "Subnets" -msgstr "" - -#: ../intro_basic_networking.rst:142 -msgid "Subnets and ARP" -msgstr "" - -#: ../adv_config_debugging.rst:31 ../adv_config_debugging.rst:36 -#: ../adv_config_debugging.rst:41 ../adv_config_debugging.rst:46 -#: ../adv_config_debugging.rst:51 ../adv_config_debugging.rst:56 -msgid "Subsection ..." -msgstr "" - -#: ../adv_config_debugging.rst:54 -msgid "Summary" -msgstr "" - -#: ../adv_config_qos.rst:35 -msgid "Supported QoS rule types" -msgstr "" - +# #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_l3ha_lb.pot (Networking Guide 0.9) #-#-#-#-# # #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../scenario_legacy_lb.rst:50 ../scenario_legacy_ovs.rst:50 -msgid "Supporting services" -msgstr "" - -#: ../intro_networking_components.rst:6 -msgid "Switches" -msgstr "" - -# #-#-#-#-# adv_config_group_policy.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# adv_config_operational.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# adv_config_service_chaining.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# adv_config_VPNaaS.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# migration_legacy_to_dvr.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# migration_legacy_to_L3_HA.pot (Networking Guide 0.9) #-#-#-#-# -#: ../adv_config_group_policy.rst:5 ../adv_config_group_policy.rst:12 -#: ../adv_config_operational.rst:5 ../adv_config_service_chaining.rst:7 -#: ../adv_config_VPNaaS.rst:5 ../migration_legacy_to_dvr.rst:5 -#: ../migration_legacy_to_L3_HA.rst:5 -msgid "TBD" -msgstr "" - -#: ../intro_basic_networking.rst:351 -msgid "TCP/UDP/ICMP" -msgstr "" - -#: ../adv_config_ipv6.rst:396 -msgid "TODO" -msgstr "" - -#: ../adv_config_sriov.rst:166 -msgid "" -"Tell nova-compute which pci devices are allowed to be passed through. Edit " -"the file :file:`/etc/nova/nova.conf`:" -msgstr "" - -#: ../adv_config_ipv6.rst:189 -msgid "Tenant network considerations" -msgstr "" - -#: ../config_ml2_plug_in.rst:26 -msgid "Tenant network types" -msgstr "" - -#: ../intro_os_networking_overview.rst:60 -msgid "Tenant networks" -msgstr "" - -#: ../adv_config_sriov.rst:26 -msgid "Term" +#: ../deploy_scenario4b.rst:438 ../deploy_scenario4b.rst:486 +#: ../scenario_l3ha_lb.rst:361 ../scenario_l3ha_lb.rst:417 +#: ../scenario_legacy_lb.rst:680 ../scenario_legacy_lb.rst:736 +msgid "Linux bridge agent" msgstr "" # #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# @@ -4950,2358 +2932,11 @@ msgstr "" # #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# # #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# # #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../deploy_scenario4b.rst:671 ../scenario_dvr_ovs.rst:988 -#: ../scenario_l3ha_lb.rst:866 ../scenario_l3ha_ovs.rst:874 -#: ../scenario_legacy_lb.rst:979 ../scenario_legacy_ovs.rst:1082 -#: ../scenario_provider_ovs.rst:722 -msgid "Test connectivity to the Internet:" -msgstr "" - -# #-#-#-#-# scenario_dvr_ovs.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_l3ha_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_l3ha_ovs.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../scenario_dvr_ovs.rst:973 ../scenario_l3ha_lb.rst:851 -#: ../scenario_l3ha_ovs.rst:859 ../scenario_legacy_lb.rst:964 -#: ../scenario_legacy_ovs.rst:1067 -msgid "Test connectivity to the project router:" -msgstr "" - -#: ../adv_config_sriov.rst:297 -msgid "Test whether the sriov-agent runs successfully:" -msgstr "" - -#: ../adv_config_ipv6.rst:221 -msgid "" -"That an external DHCPv6 server in theory could override the full address " -"OpenStack assigns based on the EUI-64 address, but that would not be wise as " -"it would not be consistent through the system." -msgstr "" - -#: ../adv_config_ipv6.rst:364 -msgid "" -"That it should be possible for tenants to communicate with each other on an " -"isolated network (a network without a router port) using LLA with little to " -"no participation on the part of OpenStack. The authors of this section have " -"not proven that to be true for all scenarios." -msgstr "" - -#: ../intro_basic_networking.rst:456 -msgid "" -"The *Internet Control Message Protocol* (ICMP) is a protocol used for " -"sending control messages over an IP network. For example, a router that " -"receives an IP packet may send an ICMP packet back to the source if there is " -"no route in the router's routing table that corresponds to the destination " -"address (ICMP code 1, destination host unreachable) or if the IP packet is " -"too large for the router to handle (ICMP code 4, fragmentation required and " -"\"don't fragment\" flag is set)." -msgstr "" - -#: ../intro_basic_networking.rst:362 -msgid "" -"The *Transmission Control Protocol* (TCP) is the most commonly used layer 4 " -"protocol in networked applications. TCP is a *connection-oriented* protocol: " -"it uses a client-server model where a client connects to a server, where " -"*server* refers to the application that receives connections. The typical " -"interaction in a TCP-based application proceeds as follows:" -msgstr "" - -#: ../intro_basic_networking.rst:419 -msgid "" -"The *User Datagram Protocol* (UDP) is another layer 4 protocol that is the " -"basis of several well-known networking protocols. UDP is a *connectionless* " -"protocol: two applications that communicate over UDP do not need to " -"establish a connection before exchanging data. UDP is also an *unreliable* " -"protocol. The operating system does not attempt to retransmit or even detect " -"lost UDP packets. The operating system also does not provide any guarantee " -"that the receiving application sees the UDP packets in the same order that " -"they were sent in." -msgstr "" - -#: ../scenario_legacy_lb.rst:327 -msgid "" -"The *iptables* service (2) performs DNAT on the packet using the ``qr`` " -"interface (3) as the source IP address. The ``qr`` interface contains the " -"project network gateway IP address *TR*." -msgstr "" - -#: ../scenario_legacy_ovs.rst:330 -msgid "" -"The *iptables* service (2) performs DNAT on the packet using the ``qr`` " -"interface (3) as the source IP address. The ``qr`` interface contains the " -"project network router interface IP address *TR1*." -msgstr "" - -#: ../scenario_legacy_ovs.rst:280 -msgid "" -"The *iptables* service (4) performs SNAT on the packet using the ``qg`` " -"interface (5) as the source IP address. The ``qg`` interface contains the " -"project network router interface IP address *TR*." -msgstr "" - -#: ../scenario_dvr_ovs.rst:252 -msgid "" -"The *iptables* service (5) performs SNAT on the packet using the project " -"network 1 router interface IP address *TR* on the ``qg`` interface (6)." -msgstr "" - -#: ../scenario_dvr_ovs.rst:319 -msgid "" -"The *iptables* service (6) in the distributed router namespace ``qrouter`` " -"performs DNAT on the packet using the destination IP address. The ``qr`` " -"interface (7) contains the project network gateway IP address *TG*." -msgstr "" - -#: ../scenario_legacy_lb.rst:277 -msgid "" -"The *iptables* service (6) performs SNAT on the packet using the ``qg`` " -"interface (7) as the source IP address. The ``qg`` interface contains the " -"project network router interface IP address *TR*." -msgstr "" - -#: ../scenario_dvr_ovs.rst:345 -msgid "" -"The *iptables* service (6) performs SNAT on the packet using the ``rfp`` " -"interface (5) as the source IP address. The ``rfp`` interface contains the " -"instance floating IP address *F1*." -msgstr "" - -#: ../intro_basic_networking.rst:464 -msgid "" -"The *ping* and *mtr* Linux command-line tools are two examples of network " -"utilities that use ICMP." -msgstr "" - -#: ../migration_nova_network_to_neutron.rst:50 -msgid "" -"The Compute REST API is available throughout the entire process, although " -"there is a brief period where it is made read-only during a database " -"migration. The Networking REST API will need to expose (to nova-api) all " -"details necessary for reconstructing the information previously held in the " -"legacy networking database." -msgstr "" - -#: ../scenario_dvr_ovs.rst:12 -msgid "" -"The DVR architecture augments the legacy architecture by providing direct " -"connectivity to external networks on compute nodes. For instances with a " -"floating IP address, routing between project and external networks resides " -"completely on the compute nodes to eliminate single point of failure and " -"performance issues with legacy network nodes. Routing also resides " -"completely on the compute nodes for instances with a fixed or floating IP " -"address using project networks on the same distributed virtual router. " -"However, instances with a fixed IP address still rely on the network node " -"for routing and SNAT services between project and external networks." -msgstr "" - -#: ../intro_os_networking_service.rst:84 -msgid "" -"The Firewall-as-a-Service (FWaaS) API is an experimental API that enables " -"early adopters and vendors to test their networking implementations." -msgstr "" - -#: ../adv_config_ipv6.rst:81 -msgid "" -"The IPv6 Protocol uses Internet Control Message Protocol packets (ICMPv6) as " -"a way to distribute information about networking. ICMPv6 packets with the " -"type flag set to 134 are called \"Router Advertisement\" packets, which " -"broadcasts information about the router and the route that can be used by " -"guest instances to send network traffic." -msgstr "" - -#: ../intro_basic_networking.rst:271 -msgid "" -"The Internet Protocol (IP) specifies how to route packets between hosts that " -"are connected to different local networks. IP relies on special network " -"hosts called *routers* or *gateways*. A router is a host that is connected " -"to at least two local networks and can forward IP packets from one local " -"network to another. A router has multiple IP addresses: one for each of the " -"networks it is connected to." -msgstr "" - -#: ../scenario_l3ha_lb.rst:169 -msgid "" -"The L3HA mechanism simply augments :doc:`scenario_legacy_lb` with quick " -"failover of layer-3 services to another router if the master router fails." -msgstr "" - -#: ../scenario_l3ha_ovs.rst:178 -msgid "" -"The L3HA mechanism simply augments :doc:`scenario_legacy_ovs` with quick " -"failover of layer-3 services to another router if the master router fails." -msgstr "" - -# #-#-#-#-# scenario_l3ha_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_l3ha_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../scenario_l3ha_lb.rst:186 ../scenario_l3ha_ovs.rst:195 -msgid "" -"The L3HA mechanism uses the same priority for all routers. Therefore, VRRP " -"promotes the backup router with the highest IP address to the master router." -msgstr "" - -# #-#-#-#-# scenario_dvr_ovs.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../scenario_dvr_ovs.rst:220 ../scenario_dvr_ovs.rst:339 -#: ../scenario_dvr_ovs.rst:406 ../scenario_legacy_ovs.rst:235 -#: ../scenario_legacy_ovs.rst:425 ../scenario_legacy_ovs.rst:560 -#: ../scenario_provider_ovs.rst:197 ../scenario_provider_ovs.rst:259 -#: ../scenario_provider_ovs.rst:331 -msgid "" -"The Linux bridge ``qbr`` forwards the packet to the Open vSwitch integration " -"bridge ``br-int``." -msgstr "" - -#: ../scenario_legacy_ovs.rst:606 -msgid "" -"The Linux bridge ``qbr`` forwards the packet to the ``tap`` interface (4) on " -"instance 2." -msgstr "" - -#: ../scenario_legacy_ovs.rst:379 -msgid "" -"The Linux bridge ``qbr`` forwards the packet to the ``tap`` interface (5) on " -"instance 1." -msgstr "" - -#: ../scenario_provider_ovs.rst:358 -msgid "" -"The Linux bridge ``qbr`` forwards the packet to the ``tap`` interface (5) on " -"instance 2." -msgstr "" - -# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../scenario_legacy_ovs.rst:519 ../scenario_provider_ovs.rst:292 -msgid "" -"The Linux bridge ``qbr`` forwards the packet to the ``tap`` interface (6) on " -"instance 2." -msgstr "" - -#: ../scenario_dvr_ovs.rst:440 -msgid "" -"The Linux bridge ``qbr`` forwards the packet to the instance 2 ``tap`` " -"interface (8)." -msgstr "" - -#: ../scenario_dvr_ovs.rst:328 -msgid "" -"The Linux bridge ``qbr`` forwards the packet to the instance ``tap`` " -"interface (9)." -msgstr "" - -#: ../scenario_legacy_lb.rst:487 -msgid "The Linux bridge agent handles switching within the project network." -msgstr "" - -#: ../intro_os_networking_service.rst:77 -msgid "" -"The Load-Balancer-as-a-Service (LBaaS) API provisions and configures load " -"balancers. The reference implementation is based on the HAProxy software " -"load balancer." -msgstr "" - -#: ../migration_nova_network_to_neutron.rst:45 -msgid "" -"The Networking REST API is publicly read-only until after the migration is " -"complete. During the migration, Networking REST API is read-write only to " -"nova-api, and changes to Networking are only allowed via nova-api." -msgstr "" - -#: ../intro_os_networking_overview.rst:11 -msgid "" -"The Networking service, code-named neutron, provides an API that lets you " -"define network connectivity and addressing in the cloud. The Networking " -"service enables operators to leverage different networking technologies to " -"power their cloud networking. The Networking service also provides an API to " -"configure and manage a variety of network services ranging from L3 " -"forwarding and NAT to load balancing, perimeter firewalls, and virtual " -"private networks." -msgstr "" - -#: ../scenario_provider_ovs.rst:267 ../scenario_provider_ovs.rst:339 -msgid "" -"The Open vSwitch VLAN bridge ``br-provider`` forwards the packet to the " -"physical network infrastructure via the provider network interface." -msgstr "" - -#: ../scenario_legacy_ovs.rst:483 -msgid "" -"The Open vSwitch VLAN bridge ``br-vlan`` forwards the packet to compute node " -"2 via the VLAN interface." -msgstr "" - -#: ../scenario_legacy_ovs.rst:263 ../scenario_legacy_ovs.rst:361 -#: ../scenario_legacy_ovs.rst:453 ../scenario_legacy_ovs.rst:501 -#: ../scenario_legacy_ovs.rst:588 -msgid "" -"The Open vSwitch VLAN bridge ``br-vlan`` forwards the packet to the Open " -"vSwitch integration bridge ``br-int``." -msgstr "" - -#: ../scenario_legacy_ovs.rst:570 -msgid "" -"The Open vSwitch VLAN bridge ``br-vlan`` forwards the packet to the compute " -"node 2 via the VLAN interface." -msgstr "" - -#: ../scenario_legacy_ovs.rst:343 -msgid "" -"The Open vSwitch VLAN bridge ``br-vlan`` forwards the packet to the compute " -"node via the VLAN interface." -msgstr "" - -#: ../scenario_legacy_ovs.rst:245 ../scenario_legacy_ovs.rst:435 -msgid "" -"The Open vSwitch VLAN bridge ``br-vlan`` forwards the packet to the network " -"node via the VLAN interface." -msgstr "" - -#: ../scenario_legacy_ovs.rst:433 ../scenario_legacy_ovs.rst:568 -msgid "" -"The Open vSwitch VLAN bridge ``br-vlan`` replaces the internal tag with the " -"actual VLAN tag of project network 1." -msgstr "" - -#: ../scenario_legacy_ovs.rst:481 -msgid "" -"The Open vSwitch VLAN bridge ``br-vlan`` replaces the internal tag with the " -"actual VLAN tag of project network 2." -msgstr "" - -#: ../scenario_legacy_ovs.rst:243 ../scenario_legacy_ovs.rst:341 -msgid "" -"The Open vSwitch VLAN bridge ``br-vlan`` replaces the internal tag with the " -"actual VLAN tag of the project network." -msgstr "" - -#: ../scenario_legacy_ovs.rst:551 -msgid "The Open vSwitch agent handles switching within the project network." -msgstr "" - -#: ../scenario_legacy_ovs.rst:325 -msgid "" -"The Open vSwitch external bridge ``br-ex`` forwards the packet to the Open " -"vSwitch integration bridge ``br-int``." -msgstr "" - -#: ../scenario_dvr_ovs.rst:307 -msgid "" -"The Open vSwitch external bridge ``br-ex`` forwards the packet to the ``fg`` " -"interface (1) in the floating IP namespace ``fip``. The ``fg`` interface " -"responds to any ARP requests for the instance floating IP address *F1*." -msgstr "" - -# #-#-#-#-# scenario_dvr_ovs.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../scenario_dvr_ovs.rst:256 ../scenario_dvr_ovs.rst:356 -#: ../scenario_legacy_ovs.rst:287 -msgid "" -"The Open vSwitch external bridge ``br-ex`` forwards the packet to the " -"external network via the external interface." -msgstr "" - -#: ../scenario_legacy_ovs.rst:427 -msgid "" -"The Open vSwitch integration bridge ``br-int`` adds the internal tag for " -"project network 1." -msgstr "" - -#: ../scenario_legacy_ovs.rst:475 -msgid "" -"The Open vSwitch integration bridge ``br-int`` adds the internal tag for " -"project network 2." -msgstr "" - -# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../scenario_legacy_ovs.rst:562 ../scenario_provider_ovs.rst:261 -msgid "" -"The Open vSwitch integration bridge ``br-int`` adds the internal tag for " -"provider network 1." -msgstr "" - -#: ../scenario_legacy_ovs.rst:237 ../scenario_legacy_ovs.rst:335 -msgid "" -"The Open vSwitch integration bridge ``br-int`` adds the internal tag for the " -"project network." -msgstr "" - -#: ../scenario_provider_ovs.rst:199 ../scenario_provider_ovs.rst:333 -msgid "" -"The Open vSwitch integration bridge ``br-int`` adds the internal tag for the " -"provider network." -msgstr "" - -#: ../scenario_dvr_ovs.rst:224 -msgid "" -"The Open vSwitch integration bridge ``br-int`` forwards the packet (3) to " -"the project network 1 gateway *TG* interface ``qr`` in the distributed " -"router namespace ``qrouter``." -msgstr "" - -# #-#-#-#-# scenario_dvr_ovs.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../scenario_dvr_ovs.rst:324 ../scenario_dvr_ovs.rst:436 -#: ../scenario_legacy_ovs.rst:375 ../scenario_legacy_ovs.rst:515 -#: ../scenario_legacy_ovs.rst:602 ../scenario_provider_ovs.rst:288 -#: ../scenario_provider_ovs.rst:354 -msgid "" -"The Open vSwitch integration bridge ``br-int`` forwards the packet to the " -"Linux bridge ``qbr``." -msgstr "" - -#: ../scenario_legacy_ovs.rst:241 ../scenario_legacy_ovs.rst:339 -#: ../scenario_legacy_ovs.rst:431 ../scenario_legacy_ovs.rst:479 -#: ../scenario_legacy_ovs.rst:566 -msgid "" -"The Open vSwitch integration bridge ``br-int`` forwards the packet to the " -"Open vSwitch VLAN bridge ``br-vlan``." -msgstr "" - -#: ../scenario_legacy_ovs.rst:285 -msgid "" -"The Open vSwitch integration bridge ``br-int`` forwards the packet to the " -"Open vSwitch external bridge ``br-ex``." -msgstr "" - -#: ../scenario_provider_ovs.rst:201 ../scenario_provider_ovs.rst:263 -#: ../scenario_provider_ovs.rst:335 -msgid "" -"The Open vSwitch integration bridge ``br-int`` forwards the packet to the " -"Open vSwitch provider bridge ``br-provider``." -msgstr "" - -# #-#-#-#-# scenario_dvr_ovs.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../scenario_dvr_ovs.rst:231 ../scenario_dvr_ovs.rst:418 -#: ../scenario_legacy_ovs.rst:250 ../scenario_legacy_ovs.rst:348 -#: ../scenario_legacy_ovs.rst:440 ../scenario_legacy_ovs.rst:488 -#: ../scenario_legacy_ovs.rst:575 -msgid "" -"The Open vSwitch integration bridge ``br-int`` forwards the packet to the " -"Open vSwitch tunnel bridge ``br-tun``." -msgstr "" - -#: ../scenario_legacy_ovs.rst:467 -msgid "" -"The Open vSwitch integration bridge ``br-int`` forwards the packet to the " -"``qr-1`` interface (3) in the router namespace ``qrouter``. The ``qr-1`` " -"interface contains the project network 1 gateway IP address *TG1*." -msgstr "" - -#: ../scenario_legacy_ovs.rst:277 -msgid "" -"The Open vSwitch integration bridge ``br-int`` forwards the packet to the " -"``qr`` interface (3) in the router namespace ``qrouter``. The ``qr`` " -"interface contains the project network gateway IP address *TG*." -msgstr "" - -#: ../scenario_dvr_ovs.rst:341 -msgid "" -"The Open vSwitch integration bridge ``br-int`` forwards the packet to the " -"``qr`` interface (7) in the distributed router namespace ``qrouter``. The " -"``qr`` interface contains the project network gateway IP address *TG*." -msgstr "" - -#: ../scenario_dvr_ovs.rst:250 -msgid "" -"The Open vSwitch integration bridge ``br-int`` forwards the packet to the " -"``sg`` interface (4) in the SNAT namespace ``snat``." -msgstr "" - -#: ../scenario_dvr_ovs.rst:408 -msgid "" -"The Open vSwitch integration bridge ``br-int`` forwards the packet to the " -"project network 1 interface (3) in the distributed router namespace " -"``qrouter``." -msgstr "" - -#: ../scenario_dvr_ovs.rst:222 -msgid "" -"The Open vSwitch integration bridge ``br-int`` modifies the packet to " -"contain the internal tag for project network 1." -msgstr "" - -#: ../scenario_dvr_ovs.rst:416 -msgid "" -"The Open vSwitch integration bridge ``br-int`` modifies the packet to " -"contain the internal tag for project network 2." -msgstr "" - -#: ../scenario_provider_ovs.rst:352 -msgid "" -"The Open vSwitch integration bridge ``br-int`` replaces the actual VLAN tag " -"(segmentation ID) of provider network 1 with the internal tag." -msgstr "" - -#: ../scenario_provider_ovs.rst:286 -msgid "" -"The Open vSwitch integration bridge ``br-int`` replaces the actual VLAN tag " -"(segmentation ID) of provider network 2 with the internal tag." -msgstr "" - -#: ../scenario_legacy_ovs.rst:455 -msgid "" -"The Open vSwitch integration bridge ``br-int`` replaces the actual VLAN tag " -"of project network 1 with the internal tag." -msgstr "" - -#: ../scenario_legacy_ovs.rst:503 ../scenario_legacy_ovs.rst:590 -msgid "" -"The Open vSwitch integration bridge ``br-int`` replaces the actual VLAN tag " -"of project network 2 with the internal tag." -msgstr "" - -#: ../scenario_legacy_ovs.rst:265 -msgid "" -"The Open vSwitch integration bridge ``br-int`` replaces the actual VLAN tag " -"of the project network with the internal tag." -msgstr "" - -#: ../scenario_legacy_ovs.rst:363 -msgid "" -"The Open vSwitch integration bridge ``br-int`` replaces the actual VLAN tag " -"the project network with the internal tag." -msgstr "" - -#: ../scenario_dvr_ovs.rst:248 -msgid "" -"The Open vSwitch integration bridge ``br-int`` replaces the packet source " -"MAC address *D1* with *TG*." -msgstr "" - -#: ../scenario_dvr_ovs.rst:434 -msgid "" -"The Open vSwitch integration bridge ``br-int`` replaces the packet source " -"MAC address *D1* with *TG2*." -msgstr "" - -#: ../scenario_legacy_ovs.rst:327 -msgid "" -"The Open vSwitch integration bridge forwards the packet to the ``qg`` " -"interface (1) in the router namespace ``qrouter``. The ``qg`` interface " -"contains the instance 1 floating IP address *F1*." -msgstr "" - -#: ../scenario_provider_ovs.rst:284 ../scenario_provider_ovs.rst:350 -msgid "" -"The Open vSwitch provider bridge ``br-provider`` forwards the packet to the " -"Open vSwitch integration bridge ``br-int``." -msgstr "" - -#: ../scenario_provider_ovs.rst:205 -msgid "" -"The Open vSwitch provider bridge ``br-provider`` forwards the packet to the " -"physical network via the provider network interface." -msgstr "" - -#: ../scenario_provider_ovs.rst:265 -msgid "" -"The Open vSwitch provider bridge ``br-provider`` replaces the internal tag " -"with the actual VLAN tag (segmentation ID) of provider network 1." -msgstr "" - -#: ../scenario_provider_ovs.rst:203 ../scenario_provider_ovs.rst:337 -msgid "" -"The Open vSwitch provider bridge ``br-provider`` replaces the internal tag " -"with the actual VLAN tag (segmentation ID) of the provider network." -msgstr "" - -# #-#-#-#-# scenario_dvr_ovs.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../scenario_dvr_ovs.rst:424 ../scenario_legacy_ovs.rst:492 -msgid "" -"The Open vSwitch tunnel bridge ``br-tun`` forwards the packet to compute " -"node 2 via the tunnel interface." -msgstr "" - -# #-#-#-#-# scenario_dvr_ovs.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../scenario_dvr_ovs.rst:246 ../scenario_dvr_ovs.rst:432 -#: ../scenario_legacy_ovs.rst:274 ../scenario_legacy_ovs.rst:372 -#: ../scenario_legacy_ovs.rst:464 ../scenario_legacy_ovs.rst:512 -#: ../scenario_legacy_ovs.rst:599 -msgid "" -"The Open vSwitch tunnel bridge ``br-tun`` forwards the packet to the Open " -"vSwitch integration bridge ``br-int``." -msgstr "" - -#: ../scenario_legacy_ovs.rst:579 -msgid "" -"The Open vSwitch tunnel bridge ``br-tun`` forwards the packet to the compute " -"node 2 via the tunnel interface." -msgstr "" - -#: ../scenario_legacy_ovs.rst:352 -msgid "" -"The Open vSwitch tunnel bridge ``br-tun`` forwards the packet to the compute " -"node via the tunnel interface." -msgstr "" - -# #-#-#-#-# scenario_dvr_ovs.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../scenario_dvr_ovs.rst:237 ../scenario_legacy_ovs.rst:254 -#: ../scenario_legacy_ovs.rst:444 -msgid "" -"The Open vSwitch tunnel bridge ``br-tun`` forwards the packet to the network " -"node via the tunnel interface." -msgstr "" - -#: ../scenario_dvr_ovs.rst:233 ../scenario_dvr_ovs.rst:420 -msgid "" -"The Open vSwitch tunnel bridge ``br-tun`` replaces the packet source MAC " -"address *I1* with *D1*." -msgstr "" - -# #-#-#-#-# scenario_dvr_ovs.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../scenario_dvr_ovs.rst:244 ../scenario_legacy_ovs.rst:462 -msgid "" -"The Open vSwitch tunnel bridge ``br-tun`` unwraps the packet and adds the " -"internal tag for project network 1." -msgstr "" - -#: ../scenario_legacy_ovs.rst:510 ../scenario_legacy_ovs.rst:597 -msgid "" -"The Open vSwitch tunnel bridge ``br-tun`` unwraps the packet and adds the " -"internal tag for project network 2." -msgstr "" - -#: ../scenario_legacy_ovs.rst:272 ../scenario_legacy_ovs.rst:370 -msgid "" -"The Open vSwitch tunnel bridge ``br-tun`` unwraps the packet and adds the " -"internal tag for the project network." -msgstr "" - -#: ../scenario_dvr_ovs.rst:431 -msgid "The Open vSwitch tunnel bridge ``br-tun`` unwraps the packet." -msgstr "" - -#: ../scenario_legacy_ovs.rst:442 ../scenario_legacy_ovs.rst:577 -msgid "" -"The Open vSwitch tunnel bridge ``br-tun`` wraps the packet in a VXLAN or GRE " -"tunnel and adds a tag to identify project network 1." -msgstr "" - -#: ../scenario_legacy_ovs.rst:490 -msgid "" -"The Open vSwitch tunnel bridge ``br-tun`` wraps the packet in a VXLAN or GRE " -"tunnel and adds a tag to identify project network 2." -msgstr "" - -#: ../scenario_legacy_ovs.rst:252 ../scenario_legacy_ovs.rst:350 -msgid "" -"The Open vSwitch tunnel bridge ``br-tun`` wraps the packet in a VXLAN or GRE " -"tunnel and adds a tag to identify the project network." -msgstr "" - -#: ../scenario_dvr_ovs.rst:235 -msgid "" -"The Open vSwitch tunnel bridge ``br-tun`` wraps the packet in a VXLAN tunnel " -"that contains a tag for project network 1." -msgstr "" - -#: ../scenario_dvr_ovs.rst:422 -msgid "" -"The Open vSwitch tunnel bridge ``br-tun`` wraps the packet in a VXLAN tunnel " -"that contains a tag for project network 2." -msgstr "" - -#: ../intro_os_networking_overview.rst:22 -msgid "" -"The OpenStack Networking API includes support for Layer 2 networking and IP " -"address management (IPAM), as well as an extension for a Layer 3 router " -"construct that enables routing between Layer 2 networks and gateways to " -"external networks. OpenStack Networking includes a growing list of plug-ins " -"that enable interoperability with various commercial and open source network " -"technologies, including routers, switches, virtual switches and software-" -"defined networking (SDN) controllers." -msgstr "" - -#: ../adv_config_debugging.rst:5 -msgid "" -"The OpenStack Networking service offers many degrees of freedom because of " -"the pluggable back end that supports a variety of open source and vendor " -"(proprietary) plug-ins. The open source plug-ins generally implement native " -"Linux facilities such as Open vSwitch (OVS) and Linux bridge. This section " -"provides methods to troubleshoot and mitigate network issues for " -"environments using the open source ML2 plug-in with the OVS or Linux bridge " -"agent." -msgstr "" - -#: ../intro_networking.rst:5 -msgid "" -"The OpenStack Networking service provides an API that allows users to set up " -"and define network connectivity and addressing in the cloud. The project " -"code-name for Networking services is neutron. OpenStack Networking handles " -"the creation and management of a virtual networking infrastructure, " -"including networks, switches, subnets, and routers for devices managed by " -"the OpenStack Compute service (nova). Advanced services such as firewalls or " -"virtual private networks (VPNs) can also be used." -msgstr "" - -#: ../intro_os_networking_overview.rst:90 -msgid "" -"The OpenStack administrator creates provider networks. These networks map to " -"existing physical networks in the data center. Useful network types in this " -"category are flat (untagged) and VLAN (802.1Q tagged)." -msgstr "" - -#: ../intro_os_networking_overview.rst:150 -msgid "" -"The OpenStack networking service is extensible. Extensions serve two " -"purposes: they allow the introduction of new features in the API without " -"requiring a version change and they allow the introduction of vendor " -"specific niche functionality. Applications can programmatically list " -"available extensions by performing a GET on the :code:`/extensions` URI. " -"Note that this is a versioned request; that is, an extension available in " -"one API version might not be available in another." -msgstr "" - -#: ../scenario_legacy_lb.rst:273 -msgid "" -"The VLAN bridge ``qbr`` forwards the packet to the ``qr`` interface in the " -"router namespace ``qrouter``. The ``qr`` interface contains the project " -"network 1 gateway IP address *TG*." -msgstr "" - -#: ../scenario_legacy_lb.rst:455 -msgid "" -"The VLAN bridge ``qbr`` forwards the packet to the ``tap`` interface (11) on " -"instance 2." -msgstr "" - -#: ../scenario_legacy_lb.rst:373 -msgid "" -"The VLAN bridge ``qbr`` forwards the packet to the ``tap`` interface on " -"instance 1." -msgstr "" - -#: ../scenario_legacy_lb.rst:245 ../scenario_legacy_lb.rst:343 -msgid "" -"The VLAN bridge ``qbr`` forwards the packet to the logical VLAN interface " -"``device.sid`` where *device* references the underlying physical VLAN " -"interface and *sid* contains the project network segmentation ID." -msgstr "" - -#: ../scenario_legacy_lb.rst:441 -msgid "" -"The VLAN bridge ``qbr`` forwards the packet to the logical VLAN interface " -"``vlan.sid`` (8) where *sid* contains the project network segmentation ID." -msgstr "" - -#: ../scenario_legacy_ovs.rst:261 ../scenario_legacy_ovs.rst:359 -#: ../scenario_legacy_ovs.rst:451 ../scenario_legacy_ovs.rst:499 -#: ../scenario_legacy_ovs.rst:586 -msgid "" -"The VLAN interface forwards the packet to the Open vSwitch VLAN bridge ``br-" -"vlan``." -msgstr "" - -#: ../intro_os_networking_service.rst:71 -msgid "" -"The Virtual Private Network as a Service (VPNaaS) is a neutron extension " -"that introduces the VPN feature set." -msgstr "" - -# #-#-#-#-# scenario_dvr_ovs.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_l3ha_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_l3ha_ovs.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../scenario_dvr_ovs.rst:591 ../scenario_dvr_ovs.rst:705 -#: ../scenario_l3ha_lb.rst:317 ../scenario_l3ha_ovs.rst:327 -#: ../scenario_legacy_ovs.rst:737 -msgid "The ``external_network_bridge`` option intentionally contains no value." -msgstr "" - -# #-#-#-#-# scenario_l3ha_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_l3ha_ovs.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../scenario_l3ha_lb.rst:249 ../scenario_l3ha_ovs.rst:261 -#: ../scenario_legacy_lb.rst:573 ../scenario_legacy_ovs.rst:671 -msgid "" -"The ``external`` value in the ``network_vlan_ranges`` option lacks VLAN ID " -"ranges to support use of arbitrary VLAN IDs by administrative users." -msgstr "" - -#: ../scenario_dvr_ovs.rst:523 -msgid "" -"The ``external`` value in the ``network_vlan_ranges`` option lacks VLAN ID " -"ranges to support use of arbitrary VLAN IDs by privileged users." -msgstr "" - -#: ../scenario_dvr_ovs.rst:353 -msgid "" -"The ``fg`` interface (1) in the floating IP namespace ``fip`` forwards the " -"packet to the Open vSwitch external bridge ``br-ex``. The ``fg`` interface " -"contains the project router external IP address *TE*." -msgstr "" - -#: ../intro_basic_networking.rst:330 -msgid "" -"The ``ip route get`` command outputs the route for a destination IP address. " -"From the above example, destination IP address 10.0.2.14 is on the local " -"network of eth0 and would be sent directly::" -msgstr "" - -#: ../adv_config_ipv6.rst:69 -msgid "" -"The ``ipv6_address_mode`` attribute is used to control how addressing is " -"handled by OpenStack. There are a number of different ways that guest " -"instances can obtain an IPv6 address, and this attribute exposes these " -"choices to users of the Networking API." -msgstr "" - -#: ../adv_config_ipv6.rst:78 -msgid "" -"The ``ipv6_ra_mode`` attribute is used to control router advertisements for " -"a subnet." -msgstr "" - -#: ../adv_config_ipv6.rst:88 -msgid "" -"The ``ipv6_ra_mode`` is used to specify if the Networking service should " -"transmit ICMPv6 packets, for a subnet." -msgstr "" - -# #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../deploy_scenario4b.rst:421 ../scenario_provider_ovs.rst:438 -msgid "" -"The ``provider`` value in the ``network_vlan_ranges`` option lacks VLAN ID " -"ranges to support use of arbitrary VLAN IDs." -msgstr "" - -# #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../deploy_scenario4b.rst:576 ../scenario_legacy_lb.rst:927 -#: ../scenario_legacy_ovs.rst:1030 ../scenario_provider_ovs.rst:627 -msgid "The ``qdhcp`` namespace might not exist until launching an instance." -msgstr "" - -#: ../scenario_l3ha_lb.rst:677 -msgid "The ``qdhcp`` namespaces might not appear until launching an instance." -msgstr "" - -#: ../scenario_l3ha_ovs.rst:686 -msgid "The ``qdhcp`` namespaces might not exist until launching an instance." -msgstr "" - -#: ../scenario_dvr_ovs.rst:254 -msgid "" -"The ``qg`` interface forwards the packet to the Open vSwitch external bridge " -"``br-ex``." -msgstr "" - -# #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../deploy_scenario4b.rst:382 ../scenario_provider_ovs.rst:405 -msgid "" -"The ``service_plugins`` option contains no value because the Networking " -"service does not provide layer-3 services such as routing." -msgstr "" - -# #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../deploy_scenario4b.rst:538 ../scenario_provider_ovs.rst:589 -msgid "The ``shared`` option allows any project to use this network." -msgstr "" - -# #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../deploy_scenario4b.rst:417 ../scenario_provider_ovs.rst:434 -msgid "" -"The ``tenant_network_types`` option contains no value because the " -"architecture does not support project (private) networks." -msgstr "" - -#: ../adv_config_ipv6.rst:559 -msgid "" -"The above is all you need in this scenario, but more information on " -"installing, configuring, and running Dibbler is available in the Dibbler " -"user guide, at http://klub.com.pl/dhcpv6/doc/dibbler-user.pdf." -msgstr "" - -#: ../adv_config_ipv6.rst:63 -msgid "The attributes can also be left unset." -msgstr "" - -# #-#-#-#-# adv_config_ipv6.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# adv_config_qos.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# adv_config_sriov.pot (Networking Guide 0.9) #-#-#-#-# -#: ../adv_config_ipv6.rst:12 ../adv_config_qos.rst:23 -#: ../adv_config_sriov.rst:11 -msgid "The basics" -msgstr "" - -#: ../adv_config_ipv6.rst:328 -msgid "" -"The behavior of the neutron router for IPv6 is different than IPv4 in a few " -"ways." -msgstr "" - -#: ../intro_basic_networking.rst:240 -msgid "" -"The client sends a discover (\"I’m a client at MAC address ``08:00:27:" -"b9:88:74``, I need an IP address\")" -msgstr "" - -#: ../intro_basic_networking.rst:244 -msgid "" -"The client sends a request (\"Server ``10.10.0.131``, I would like to have " -"IP ``10.10.0.112``\")" -msgstr "" - -#: ../scenario_l3ha_ovs.rst:155 -msgid "The compute nodes contain the following components:" -msgstr "" - -# #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_dvr_ovs.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_l3ha_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../deploy_scenario4b.rst:133 ../scenario_dvr_ovs.rst:148 -#: ../scenario_l3ha_lb.rst:152 ../scenario_legacy_lb.rst:175 -#: ../scenario_legacy_ovs.rst:181 ../scenario_provider_ovs.rst:129 -msgid "The compute nodes contain the following network components:" -msgstr "" - -# #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../deploy_scenario4b.rst:115 ../scenario_provider_ovs.rst:111 -msgid "The controller node contains the following network components:" -msgstr "" - -#: ../migration_nova_network_to_neutron.rst:19 -msgid "" -"The current process as designed is a minimally viable migration with the " -"goal of deprecating and then removing legacy networking. Both the Compute " -"and Networking teams agree that a \"one-button\" migration process from " -"legacy networking to OpenStack Networking (neutron) is not an essential " -"requirement for the deprecation and removal of the legacy networking at a " -"future date. This section includes a process and tools which are designed to " -"solve a simple use case migration." -msgstr "" - -# #-#-#-#-# scenario_l3ha_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_l3ha_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../scenario_l3ha_lb.rst:590 ../scenario_l3ha_ovs.rst:600 -msgid "" -"The default :file:`policy.json` file allows only administrative projects to " -"enable/disable HA during router creation and view the ``ha`` flag for a " -"router." -msgstr "" - -#: ../intro_basic_networking.rst:337 -msgid "" -"The destination IP address 93.184.216.34 is not on any of the connected " -"local networks and would be forwarded to the default gateway at 10.0.2.2::" -msgstr "" - -#: ../scenario_dvr_ovs.rst:227 -msgid "" -"The distributed router ``qrouter`` namespace resolves the project network 1 " -"SNAT interface MAC address *TN* on the ``sg`` interface (4) in the SNAT " -"namespace ``snat`` and forwards the packet to the Open vSwitch integration " -"bridge ``br-int``." -msgstr "" - -#: ../scenario_dvr_ovs.rst:348 -msgid "" -"The distributed router namespace ``qrouter`` (2) routes the packet to the " -"floating IP namespace ``fip`` using DVR internal IP addresses *DA1* and " -"*DA2*. The ``rfp`` interface (4) contains DVR internal IP address *DA2* and " -"the ``fpr`` interface (3) contains DVR internal IP address *DA1*." -msgstr "" - -#: ../scenario_dvr_ovs.rst:322 -msgid "" -"The distributed router namespace ``qrouter`` forwards the packet to the Open " -"vSwitch integration bridge ``br-int``." -msgstr "" - -#: ../scenario_dvr_ovs.rst:411 -msgid "" -"The distributed router namespace ``qrouter`` routes the packet to project " -"network 2." -msgstr "" - -#: ../scenario_dvr_ovs.rst:807 -msgid "" -"The example configuration contains ``vlan`` as the first project network " -"type. Only a privileged user can create other types of networks such as GRE " -"or VXLAN. The following commands use the ``admin`` project credentials to " -"create a VXLAN project network." -msgstr "" - -# #-#-#-#-# scenario_l3ha_ovs.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../scenario_l3ha_ovs.rst:509 ../scenario_legacy_ovs.rst:916 -msgid "" -"The example configuration contains ``vlan`` as the first project network " -"type. Only an administrative user can create other types of networks such as " -"GRE or VXLAN. The following commands use the ``admin`` project credentials " -"to create a VXLAN project network." -msgstr "" - -# #-#-#-#-# scenario_l3ha_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# -#: ../scenario_l3ha_lb.rst:499 ../scenario_legacy_lb.rst:814 -msgid "" -"The example configuration contains ``vlan`` as the first project network " -"type. Only an administrative user can create other types of networks such as " -"VXLAN. The following commands use the ``admin`` project credentials to " -"create a VXLAN project network." -msgstr "" - -# #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../deploy_scenario4b.rst:44 ../scenario_provider_ovs.rst:37 -msgid "" -"The example configuration creates a VLAN provider network. However, it also " -"supports flat (untagged or native) provider networks." -msgstr "" - -#: ../scenario_l3ha_lb.rst:28 -msgid "" -"The example configuration creates one flat external network and one VXLAN " -"project (tenant) network. However, this configuration also supports VLAN " -"external and project networks." -msgstr "" - -# #-#-#-#-# scenario_l3ha_ovs.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../scenario_l3ha_ovs.rst:28 ../scenario_legacy_ovs.rst:57 -msgid "" -"The example configuration creates one flat external network and one VXLAN " -"project (tenant) network. However, this configuration also supports VLAN " -"external networks, VLAN project networks, and GRE project networks." -msgstr "" - -#: ../scenario_legacy_lb.rst:57 -msgid "" -"The example configuration creates one flat external network and one VXLAN " -"project network. However, this configuration also supports VLAN external and " -"project networks. The Linux bridge agent does not support GRE project " -"networks." -msgstr "" - -# #-#-#-#-# scenario_l3ha_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_l3ha_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../scenario_l3ha_lb.rst:756 ../scenario_l3ha_ovs.rst:764 -msgid "The example output uses network interface ``eth1``." -msgstr "" - -#: ../scenario_legacy_lb.rst:324 -msgid "" -"The external bridge ``qbr`` forwards the packet to the ``qg`` interface (1) " -"in the router namespace ``qrouter``. The ``qg`` interface contains the " -"instance floating IP address *F1*." -msgstr "" - -#: ../scenario_legacy_lb.rst:282 -msgid "" -"The external bridge ``qbr`` forwards the packet to the external network via " -"the physical external interface." -msgstr "" - -#: ../scenario_legacy_ovs.rst:323 -msgid "" -"The external interface forwards the packet to the Open vSwitch external " -"bridge ``br-ex``." -msgstr "" - -#: ../scenario_dvr_ovs.rst:304 -msgid "" -"The external interface forwards the packet to the Open vSwitch external " -"bridge ``br-ex``. The packet contains destination IP address *F1*." -msgstr "" - -# #-#-#-#-# scenario_l3ha_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_l3ha_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../scenario_l3ha_lb.rst:25 ../scenario_l3ha_ovs.rst:25 -msgid "" -"The failover process only retains the state of network connections for " -"instances with a floating IP address." -msgstr "" - -#: ../intro_basic_networking.rst:185 -msgid "" -"The first time host *A* attempts to communicate with host *B*, the " -"destination MAC address is not known. Host *A* makes an ARP request to the " -"local network. The request is a broadcast with a message like this:" -msgstr "" - -#: ../scenario_dvr_ovs.rst:518 -msgid "" -"The first value in the ``tenant_network_types`` option becomes the default " -"project network type when a non-privileged user creates a network." -msgstr "" - -# #-#-#-#-# scenario_l3ha_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_l3ha_ovs.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../scenario_l3ha_lb.rst:245 ../scenario_l3ha_ovs.rst:257 -#: ../scenario_legacy_lb.rst:569 ../scenario_legacy_ovs.rst:667 -msgid "" -"The first value in the ``tenant_network_types`` option becomes the default " -"project network type when a regular user creates a network." -msgstr "" - -#: ../scenario_dvr_ovs.rst:316 -msgid "" -"The floating IP namespace ``fip`` forwards the packet to the ``rfp`` " -"interface (5) in the distributed router namespace ``qrouter``. The ``rfp`` " -"interface also contains the instance floating IP address *F1*." -msgstr "" - -#: ../scenario_dvr_ovs.rst:311 -msgid "" -"The floating IP namespace ``fip`` routes the packet (2) to the distributed " -"router namespace ``qrouter`` using DVR internal IP addresses *DA1* and " -"*DA2*. The ``fpr`` interface (3) contains DVR internal IP address *DA1* and " -"the ``rfp`` interface (4) contains DVR internal IP address *DA2*." -msgstr "" - -#: ../adv_config_ipv6.rst:674 -msgid "" -"The following link provides a great step by step tutorial on setting up IPv6 " -"with OpenStack: http://www.debug-all.com/?p=52" -msgstr "" - -#: ../misc_libvirt.rst:69 -msgid "" -"The following shows the dnsmasq process that libvirt manages as it appears " -"in the output of :command:`ps`::" -msgstr "" - -#: ../scenario_dvr_ovs.rst:301 -msgid "" -"The following steps involve a packet inbound from the external network to an " -"instance on compute node 1:" -msgstr "" - -#: ../scenario_dvr_ovs.rst:331 -msgid "" -"The following steps involve a packet outbound from an instance on compute " -"node 1 to the external network:" -msgstr "" - -# #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../deploy_scenario4b.rst:184 ../scenario_provider_ovs.rst:190 -msgid "The following steps involve compute node 1." -msgstr "" - -# #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_dvr_ovs.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../deploy_scenario4b.rst:242 ../deploy_scenario4b.rst:307 -#: ../scenario_dvr_ovs.rst:213 ../scenario_dvr_ovs.rst:399 -#: ../scenario_legacy_lb.rst:223 ../scenario_legacy_lb.rst:349 -#: ../scenario_legacy_lb.rst:412 ../scenario_legacy_lb.rst:489 -#: ../scenario_legacy_ovs.rst:228 ../scenario_legacy_ovs.rst:355 -#: ../scenario_legacy_ovs.rst:418 ../scenario_legacy_ovs.rst:553 -#: ../scenario_provider_ovs.rst:252 ../scenario_provider_ovs.rst:324 -msgid "The following steps involve compute node 1:" -msgstr "" - -# #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_dvr_ovs.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../deploy_scenario4b.rst:266 ../deploy_scenario4b.rst:325 -#: ../scenario_dvr_ovs.rst:427 ../scenario_legacy_lb.rst:446 -#: ../scenario_legacy_lb.rst:502 ../scenario_legacy_ovs.rst:495 -#: ../scenario_legacy_ovs.rst:582 ../scenario_provider_ovs.rst:280 -#: ../scenario_provider_ovs.rst:346 -msgid "The following steps involve compute node 2:" -msgstr "" - -# #-#-#-#-# scenario_dvr_ovs.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../scenario_dvr_ovs.rst:240 ../scenario_legacy_lb.rst:252 -#: ../scenario_legacy_lb.rst:320 ../scenario_legacy_lb.rst:425 -#: ../scenario_legacy_ovs.rst:257 ../scenario_legacy_ovs.rst:321 -#: ../scenario_legacy_ovs.rst:447 -msgid "The following steps involve the network node:" -msgstr "" - -# #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../deploy_scenario4b.rst:198 ../deploy_scenario4b.rst:256 -#: ../deploy_scenario4b.rst:321 ../scenario_provider_ovs.rst:208 -#: ../scenario_provider_ovs.rst:270 ../scenario_provider_ovs.rst:342 -msgid "The following steps involve the physical network infrastructure:" -msgstr "" - -#: ../adv_config_sriov.rst:20 -msgid "The following terms are used over the document:" -msgstr "" - -# #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../deploy_scenario4b.rst:109 ../scenario_provider_ovs.rst:105 -msgid "" -"The general provider network architecture uses physical network " -"infrastructure to handle switching and routing of network traffic." -msgstr "" - -#: ../scenario_provider_ovs.rst:326 -msgid "" -"The instance 1 ``tap`` interface (1) forwards the packet to the Linux bridge " -"``qbr``. The packet contains destination MAC address *I2* because the " -"destination resides on the same network." -msgstr "" - -# #-#-#-#-# scenario_dvr_ovs.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../scenario_dvr_ovs.rst:215 ../scenario_legacy_ovs.rst:230 -#: ../scenario_provider_ovs.rst:192 -msgid "" -"The instance 1 ``tap`` interface (1) forwards the packet to the Linux bridge " -"``qbr``. The packet contains destination MAC address *TG* because the " -"destination resides on another network." -msgstr "" - -# #-#-#-#-# scenario_dvr_ovs.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../scenario_dvr_ovs.rst:401 ../scenario_legacy_ovs.rst:420 -#: ../scenario_provider_ovs.rst:254 -msgid "" -"The instance 1 ``tap`` interface (1) forwards the packet to the Linux bridge " -"``qbr``. The packet contains destination MAC address *TG1* because the " -"destination resides on another network." -msgstr "" - -#: ../scenario_legacy_ovs.rst:555 -msgid "" -"The instance 1 ``tap`` interface (1) forwards the packet to the VLAN bridge " -"``qbr``. The packet contains destination MAC address *I2* because the " -"destination resides on the same network." -msgstr "" - -#: ../deploy_scenario4b.rst:309 -msgid "" -"The instance 1 ``tap`` interface (1) forwards the packet to the provider " -"bridge ``qbr``. The packet contains destination MAC address *I2* because the " -"destination resides on the same network." -msgstr "" - -#: ../deploy_scenario4b.rst:186 -msgid "" -"The instance 1 ``tap`` interface (1) forwards the packet to the provider " -"bridge ``qbr``. The packet contains destination MAC address *TG* because the " -"destination resides on another network." -msgstr "" - -#: ../scenario_legacy_lb.rst:227 -msgid "" -"The instance 1 ``tap`` interface (1) forwards the packet to the tunnel " -"bridge ``qbr``. The packet contains destination MAC address *TG* because the " -"destination resides on another network." -msgstr "" - -#: ../scenario_legacy_lb.rst:414 ../scenario_legacy_lb.rst:491 -msgid "" -"The instance 1 ``tap`` interface (1) forwards the packet to the tunnel " -"bridge ``qbr``. The packet contains destination MAC address *TG1* because " -"the destination resides on another network." -msgstr "" - -#: ../scenario_dvr_ovs.rst:334 -msgid "" -"The instance 1 ``tap`` interface (9) forwards the packet to the Linux bridge " -"``qbr``. The packet contains destination MAC address *TG1* because the " -"destination resides on another network." -msgstr "" - -#: ../scenario_legacy_lb.rst:240 -msgid "" -"The instance 1 ``tap`` interface forwards the packet to the VLAN bridge " -"``qbr``. The packet contains destination MAC address *TG* because the " -"destination resides on another network." -msgstr "" - -#: ../deploy_scenario4b.rst:244 -msgid "" -"The instance 1 ``tap`` interface forwards the packet to the provider bridge " -"``qbr``. The packet contains destination MAC address *TG1* because the " -"destination resides on another network." -msgstr "" - -# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../scenario_legacy_lb.rst:314 ../scenario_legacy_ovs.rst:319 -msgid "The instance receives a packet from a host on the external network." -msgstr "" - -# #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_dvr_ovs.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../deploy_scenario4b.rst:182 ../scenario_dvr_ovs.rst:207 -#: ../scenario_legacy_lb.rst:217 ../scenario_legacy_ovs.rst:226 -#: ../scenario_provider_ovs.rst:188 -msgid "The instance sends a packet to a host on the external network." -msgstr "" - -# #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../deploy_scenario4b.rst:351 ../scenario_provider_ovs.rst:374 -msgid "" -"The lack of L3 agents in this scenario prevents operation of the " -"conventional metadata agent. You must use a configuration drive to provide " -"instance metadata." -msgstr "" - -#: ../scenario_legacy_ovs.rst:151 -msgid "" -"The legacy architecture provides basic virtual networking components in your " -"environment. Routing among project and external networks resides completely " -"on the network node. Although more simple to deploy than other " -"architectures, performing all functions on the network node creates a single " -"point of failure and potential performance issues. Consider deploying DVR or " -"L3 HA architectures in production environments to provide redundancy and " -"increase performance." -msgstr "" - -#: ../scenario_legacy_lb.rst:144 -msgid "" -"The legacy architecture provides basic virtual networking components in your " -"environment. Routing among project and external networks resides completely " -"on the network node. Although more simple to deploy than other " -"architectures, performing all functions on the network node creates a single " -"point of failure and potential performance issues. Consider deploying DVR or " -"L3 HA architectures in production environments to provide redundancy and " -"increase performance. However, the DVR architecture requires Open vSwitch." -msgstr "" - -# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../scenario_legacy_lb.rst:8 ../scenario_legacy_ovs.rst:8 -msgid "" -"The legacy implementation contributes the networking portion of self-service " -"virtual data center infrastructure by providing a method for regular (non-" -"privileged) users to manage virtual networks within a project and includes " -"the following components:" -msgstr "" - -#: ../adv_config_qos.rst:52 -msgid "" -"The list of supported rule types reported by core plug-in is not enforced " -"when accessing QoS rule resources. This is mostly because then we would not " -"be able to create any rules while at least one ml2 driver lacks support for " -"QoS (at the moment of writing, linuxbridge is such a driver)." -msgstr "" - -#: ../scenario_legacy_lb.rst:271 ../scenario_legacy_lb.rst:369 -msgid "" -"The logical VLAN interface ``device.sid`` forwards the packet to the VLAN " -"bridge ``qbr``." -msgstr "" - -#: ../scenario_legacy_lb.rst:249 -msgid "" -"The logical VLAN interface ``device.sid`` forwards the packet to the network " -"node via the physical VLAN interface." -msgstr "" - -#: ../deploy_scenario4b.rst:253 ../deploy_scenario4b.rst:318 -msgid "" -"The logical VLAN interface ``device.sid`` forwards the packet to the " -"physical network infrastructure via the physical provider interface." -msgstr "" - -#: ../deploy_scenario4b.rst:195 -msgid "" -"The logical VLAN interface ``device.sid`` forwards the packet to the " -"physical network via the physical provider interface." -msgstr "" - -#: ../deploy_scenario4b.rst:272 ../deploy_scenario4b.rst:331 -msgid "" -"The logical VLAN interface ``device.sid`` forwards the packet to the " -"provider bridge ``qbr``." -msgstr "" - -#: ../scenario_legacy_lb.rst:451 -msgid "" -"The logical VLAN interface ``vlan.sid`` forwards the packet to the VLAN " -"bridge ``qbr``." -msgstr "" - -#: ../scenario_legacy_lb.rst:259 ../scenario_legacy_lb.rst:356 -#: ../scenario_legacy_lb.rst:430 ../scenario_legacy_lb.rst:507 -msgid "" -"The logical tunnel interface ``vxlan-sid`` forwards the packet to the tunnel " -"bridge ``qbr``." -msgstr "" - -#: ../migration_nova_network_to_neutron.rst:68 -msgid "" -"The migration may be paused, even for an extended period of time (for " -"example, while testing or investigating issues) with some hypervisors on " -"legacy networking and some on Networking, and Compute API remains fully " -"functional. Individual hypervisors may be rolled back to legacy networking " -"during this stage of the migration, although this requires an additional " -"restart." -msgstr "" - -#: ../migration_nova_network_to_neutron.rst:36 -msgid "" -"The migration process from the legacy nova-network networking service to " -"OpenStack Networking (neutron) has some limitations and impacts on the " -"operational state of the cloud. It is critical to understand them in order " -"to decide whether or not this process is acceptable for your cloud and all " -"users." -msgstr "" - -#: ../intro_basic_networking.rst:404 -msgid "" -"The most common application programming interface (API) for writing TCP-" -"based applications is called *Berkeley sockets*, also known as *BSD sockets* " -"or, simply, *sockets*. The sockets API exposes a *stream oriented* interface " -"for writing TCP applications: from the perspective of a programmer, sending " -"data over a TCP connection is similar to writing a stream of bytes to a " -"file. It is the responsibility of the operating system's TCP/IP " -"implementation to break up the stream of data into IP packets. The operating " -"system is also responsible for automatically retransmitting dropped packets, " -"and for handling flow control to ensure that transmitted data does not " -"overrun the sender's data buffers, receiver's data buffers, and network " -"capacity. Finally, the operating system is responsible for re-assembling the " -"packets in the correct order into a stream of data on the receiver's side. " -"Because TCP detects and retransmits lost packets, it is said to be a " -"*reliable* protocol." -msgstr "" - -# #-#-#-#-# scenario_dvr_ovs.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../scenario_dvr_ovs.rst:122 ../scenario_legacy_lb.rst:156 -#: ../scenario_legacy_ovs.rst:162 -msgid "The network node contains the following network components:" -msgstr "" - -# #-#-#-#-# scenario_l3ha_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_l3ha_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../scenario_l3ha_lb.rst:129 ../scenario_l3ha_ovs.rst:136 -msgid "The network nodes contain the following components:" -msgstr "" - -#: ../intro_basic_networking.rst:385 -msgid "" -"The operating system of the TCP client application automatically assigns a " -"port number to the client. The client owns this port number until the TCP " -"connection is terminated, after which time the operating system reclaims the " -"port number. These types of ports are referred to as *ephemeral ports*." -msgstr "" - -#: ../adv_config_ipv6.rst:521 -msgid "The options used in the configuration file above are:" -msgstr "" - -#: ../intro_basic_networking.rst:318 -msgid "" -"The output of the ``route -n`` and ``netsat -rn`` commands are formatted in " -"a slightly different way. This example shows how the same routes would be " -"formatted using these commands::" -msgstr "" - -#: ../scenario_legacy_lb.rst:347 -msgid "The physical VLAN interface forwards the packet to compute node 1." -msgstr "" - -#: ../scenario_legacy_lb.rst:444 -msgid "The physical VLAN interface forwards the packet to compute node 2." -msgstr "" - -#: ../scenario_legacy_lb.rst:267 ../scenario_legacy_lb.rst:365 -msgid "" -"The physical VLAN interface forwards the packet to the logical VLAN " -"interface ``device.sid`` where *device* references the underlying physical " -"VLAN interface and *sid* contains the project network segmentation ID." -msgstr "" - -#: ../scenario_legacy_lb.rst:448 -msgid "" -"The physical VLAN interface forwards the packet to the logical VLAN " -"interface ``vlan.sid`` (9) where *sid* contains the project network " -"segmentation ID." -msgstr "" - -#: ../scenario_legacy_lb.rst:322 -msgid "" -"The physical external interface forwards the packet to the external bridge " -"``qbr``." -msgstr "" - -# #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../deploy_scenario4b.rst:160 ../scenario_provider_ovs.rst:166 -msgid "" -"The physical network infrastructure handles routing and potentially other " -"services between the provider and external network. In this case, *provider* " -"and *external* simply differentiate between a network available to instances " -"and a network only accessible via router, respectively, to illustrate that " -"the physical network infrastructure handles routing. However, provider " -"networks support direct connection to *external* networks such as the " -"Internet." -msgstr "" - -# #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../deploy_scenario4b.rst:217 ../scenario_provider_ovs.rst:227 -msgid "" -"The physical network infrastructure handles routing between the provider " -"networks." -msgstr "" - -# #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../deploy_scenario4b.rst:287 ../scenario_provider_ovs.rst:304 -msgid "" -"The physical network infrastructure handles switching within the provider " -"network." -msgstr "" - -#: ../deploy_scenario4b.rst:268 ../deploy_scenario4b.rst:327 -msgid "" -"The physical provider interface forwards the packet to the logical VLAN " -"interface ``device.sid`` where *device* references the underlying physical " -"provider interface and *sid* contains the provider network segmentation ID." -msgstr "" - -#: ../scenario_legacy_lb.rst:337 -msgid "The physical tunnel interface forwards the packet to compute node 1." -msgstr "" - -#: ../scenario_legacy_lb.rst:256 ../scenario_legacy_lb.rst:427 -#: ../scenario_legacy_lb.rst:504 -msgid "" -"The physical tunnel interface forwards the packet to the logical tunnel " -"interface ``vxlan-sid`` (4) where *sid* contains the project network " -"segmentation ID." -msgstr "" - -#: ../scenario_legacy_lb.rst:353 -msgid "" -"The physical tunnel interface forwards the packet to the logical tunnel " -"interface ``vxlan-sid`` (5) where *sid* contains the project network " -"segmentation ID." -msgstr "" - -#: ../scenario_legacy_lb.rst:235 ../scenario_legacy_lb.rst:422 -#: ../scenario_legacy_lb.rst:499 -msgid "The physical tunnel interface forwards the packet to the network node." -msgstr "" - -#: ../adv_config_ipv6.rst:635 -msgid "" -"The prefix delegation mechanism then sends a request via the external " -"network to your prefix delegation server, which replies with the delegated " -"prefix. The subnet is then updated with the new prefix, including issuing " -"new IP addresses to all ports:" -msgstr "" - -#: ../scenario_dvr_ovs.rst:413 -msgid "" -"The project network 2 interface (4) in the distributed router namespace " -"``qrouter`` namespace forwards the packet to the Open vSwitch integration " -"bridge ``br-int``." -msgstr "" - -#: ../deploy_scenario4b.rst:276 -msgid "" -"The provider bridge ``qbr`` forwards the packet to the ``tap`` interface (6) " -"on instance 2." -msgstr "" - -#: ../deploy_scenario4b.rst:335 -msgid "" -"The provider bridge ``qbr`` forwards the packet to the instance 2 ``tap`` " -"interface (5)." -msgstr "" - -#: ../deploy_scenario4b.rst:191 ../deploy_scenario4b.rst:249 -#: ../deploy_scenario4b.rst:314 -msgid "" -"The provider bridge ``qbr`` forwards the packet to the logical VLAN " -"interface ``device.sid`` where *device* references the underlying physical " -"provider interface and *sid* contains the provider network segmentation ID." -msgstr "" - -#: ../scenario_provider_ovs.rst:282 ../scenario_provider_ovs.rst:348 -msgid "" -"The provider network interface forwards the packet to the Open vSwitch " -"provider bridge ``br-provider``." -msgstr "" - -#: ../adv_config_ipv6.rst:5 -msgid "" -"The purpose of this page is to describe how the features and functionality " -"available in OpenStack (using neutron networking) as of the Kilo release. It " -"is intended to serve as a guide for how to deploy IPv6-enabled instances " -"using OpenStack Networking. Where appropriate, features planned for Liberty " -"or beyond may be described." -msgstr "" - -#: ../adv_config_sriov.rst:5 -msgid "" -"The purpose of this page is to describe how to enable SR-IOV functionality " -"available in OpenStack (using OpenStack Networking) as of the Juno release. " -"This page serves as a how-to guide on configuring OpenStack Networking and " -"OpenStack Compute to create neutron SR-IOV ports." -msgstr "" - -#: ../scenario_legacy_ovs.rst:283 -msgid "" -"The router namespace ``qrouter`` forwards the packet to the Open vSwitch " -"integration bridge ``br-int`` via the ``qg`` interface." -msgstr "" - -#: ../scenario_legacy_ovs.rst:333 ../scenario_legacy_ovs.rst:473 -msgid "" -"The router namespace ``qrouter`` forwards the packet to the Open vSwitch " -"integration bridge ``br-int``." -msgstr "" - -#: ../scenario_legacy_lb.rst:341 ../scenario_legacy_lb.rst:439 -msgid "" -"The router namespace ``qrouter`` forwards the packet to the VLAN bridge " -"``qbr``." -msgstr "" - -#: ../scenario_legacy_lb.rst:280 -msgid "" -"The router namespace ``qrouter`` forwards the packet to the external bridge " -"``qbr``." -msgstr "" - -#: ../scenario_legacy_lb.rst:332 -msgid "" -"The router namespace ``qrouter`` forwards the packet to the tunnel bridge " -"``qbr``." -msgstr "" - -#: ../scenario_legacy_lb.rst:436 -msgid "" -"The router namespace ``qrouter`` routes the packet (6) to the ``qr-2`` " -"interface (7). The ``qr-2`` interface contains the project network 2 gateway " -"IP address *TG2*." -msgstr "" - -#: ../scenario_legacy_ovs.rst:470 -msgid "" -"The router namespace ``qrouter`` routes the packet to the ``qr-2`` interface " -"(4). The ``qr-2`` interface contains the project network 2 gateway IP " -"address *TG2*." -msgstr "" - -#: ../intro_basic_networking.rst:246 -msgid "" -"The server sends an acknowledgement (\"OK ``08:00:27:b9:88:74``, IP " -"``10.10.0.112`` is yours\")" -msgstr "" - -#: ../intro_basic_networking.rst:242 -msgid "" -"The server sends an offer (\"OK ``08:00:27:b9:88:74``, I’m offering IP " -"address ``10.10.0.112``\")" -msgstr "" - -#: ../adv_config_sriov.rst:51 -msgid "" -"The sriov-agent allows you to set the admin state of ports and starting from " -"Liberty allows you to control port security (enable and disable " -"spoofchecking) and QoS rate limit settings." -msgstr "" - -#: ../adv_config_sriov.rst:99 -msgid "" -"The step to create VFs differ between SR-IOV card ethernet controller " -"manufacturers. Currently the following manufacturers are known to work:" -msgstr "" - -#: ../adv_config_ipv6.rst:620 -msgid "" -"The subnet is initially created with a temporary CIDR before one can be " -"assigned by prefix delegation. Any number of subnets with this temporary " -"CIDR can exist without raising an overlap error. The subnetpool_id is " -"automatically set to :code:`prefix_delegation`." -msgstr "" - -#: ../adv_config_sriov.rst:154 -msgid "" -"The suggested way of making PCI SYS settings persistent is through :file:" -"`sysfs.conf` but for unknown reason changing :file:`sysfs.conf` does not " -"have any effect on Ubuntu 14.04." -msgstr "" - -#: ../scenario_dvr_ovs.rst:117 -msgid "" -"The term *north-south* generally defines network traffic that travels " -"between an instance and external network (typically the Internet) and the " -"term *east-west* generally defines network traffic that travels between " -"instances." -msgstr "" - -#: ../scenario_legacy_lb.rst:432 -msgid "" -"The tunnel bridge ``qbr`` forwards the packet to the ``qr-1`` interface (5) " -"in the router namespace ``qrouter``. The ``qr-1`` interface contains the " -"project network 1 gateway IP address *TG1*." -msgstr "" - -#: ../scenario_legacy_lb.rst:261 -msgid "" -"The tunnel bridge ``qbr`` forwards the packet to the ``qr`` interface (5) in " -"the router namespace ``qrouter``. The ``qr`` interface contains the project " -"network router interface IP address *TG*." -msgstr "" - -#: ../scenario_legacy_lb.rst:511 -msgid "" -"The tunnel bridge ``qbr`` forwards the packet to the ``tap`` interface (6) " -"on instance 2." -msgstr "" - -#: ../scenario_legacy_lb.rst:360 -msgid "" -"The tunnel bridge ``qbr`` forwards the packet to the ``tap`` interface (7) " -"on instance 1." -msgstr "" - -#: ../scenario_legacy_lb.rst:232 ../scenario_legacy_lb.rst:419 -#: ../scenario_legacy_lb.rst:496 -msgid "" -"The tunnel bridge ``qbr`` forwards the packet to the logical tunnel " -"interface ``vxlan-sid`` (3) where *sid* contains the project network " -"segmentation ID." -msgstr "" - -#: ../scenario_legacy_lb.rst:334 -msgid "" -"The tunnel bridge ``qbr`` forwards the packet to the logical tunnel " -"interface ``vxlan-sid`` (4) where *sid* contains the project network " -"segmentation ID." -msgstr "" - -# #-#-#-#-# scenario_dvr_ovs.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../scenario_dvr_ovs.rst:242 ../scenario_dvr_ovs.rst:429 -#: ../scenario_legacy_ovs.rst:270 ../scenario_legacy_ovs.rst:368 -#: ../scenario_legacy_ovs.rst:460 ../scenario_legacy_ovs.rst:508 -#: ../scenario_legacy_ovs.rst:595 -msgid "" -"The tunnel interface forwards the packet to the Open vSwitch tunnel bridge " -"``br-tun``." -msgstr "" - -#: ../adv_config_ipv6.rst:354 -msgid "" -"The upstream router can send an RA and the neutron router will automatically " -"learn the next-hop LLA, provided again that no subnet is assigned and the " -"``ipv6_gateway`` flag is not set." -msgstr "" - -#: ../adv_config_ipv6.rst:551 -msgid "The variables used in the script file above are:" -msgstr "" - -#: ../adv_config_sriov.rst:46 -msgid "There are 2 ways of configuring SR-IOV:" -msgstr "" - -#: ../adv_config_ipv6.rst:207 -msgid "There are four methods for a subnet to get its ``cidr`` in OpenStack:" -msgstr "" - -#: ../intro_network_address_translation.rst:16 -msgid "" -"There are multiple variations of NAT, and here we describe three kinds " -"commonly found in OpenStack deployments." -msgstr "" - -#: ../adv_config_ipv6.rst:52 -msgid "There are two IPv6 attributes:" -msgstr "" - -#: ../intro_basic_networking.rst:161 -msgid "There are two syntaxes for expressing a netmask:" -msgstr "" - -#: ../adv_config_ipv6.rst:426 -msgid "" -"There is no provisions for an IPv6-based metadata service similar to what is " -"provided for IPv4. In the case of dual stack Guests though it is always " -"possible to use the IPv4 metadata service instead." -msgstr "" - -#: ../intro_network_address_translation.rst:37 -msgid "" -"These IP addresses are not publicly routable, meaning that a host on the " -"public Internet can not send an IP packet to any of these addresses. Private " -"IP addresses are widely used in both residential and corporate environments." -msgstr "" - -#: ../adv_config_ipv6.rst:57 -msgid "These attributes can be set to the following values:" -msgstr "" - -# #-#-#-#-# scenario_dvr_ovs.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../scenario_dvr_ovs.rst:30 ../scenario_legacy_lb.rst:65 -#: ../scenario_legacy_ovs.rst:64 -msgid "" -"These prerequisites define the minimal physical infrastructure and immediate " -"OpenStack service dependencies necessary to deploy this scenario. For " -"example, the Networking service immediately depends on the Identity service " -"and the Compute service immediately depends on the Networking service. These " -"dependencies lack services such as the Image service because the Networking " -"service does not immediately depend on it. However, the Compute service " -"depends on the Image service to launch an instance. The example " -"configuration in this scenario assumes basic configuration knowledge of " -"Networking service components." -msgstr "" - -# #-#-#-#-# scenario_l3ha_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_l3ha_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../scenario_l3ha_lb.rst:45 ../scenario_l3ha_ovs.rst:44 -msgid "" -"These prerequisites define the minimal physical infrastructure and immediate " -"OpenStack service dependencies necessary to deploy this scenario. For " -"example, the Networking service immediately depends on the Identity service " -"and the Compute service immediately depends on the Networking service. These " -"dependencies lack services such as the Image service because the Networking " -"service does not immediately depend on it. However, the Compute service " -"depends on the Image service to launch an instance. The example " -"configuration in this scenario assumes basic configuration knowledge of " -"Networking service components. For assistance with basic configuration of " -"the Networking service, see the Installation Guide." -msgstr "" - -#: ../scenario_provider_ovs.rst:43 -msgid "" -"These prerequisites define the minimum physical infrastructure and OpenStack " -"service dependencies that you need to deploy this scenario. For example, the " -"Networking service immediately depends on the Identity service and the " -"Compute service immediately depends on the Networking service. These " -"dependencies lack services such as the Image service because the Networking " -"service does not immediately depend on it. However, the Compute service " -"depends on the Image service to launch an instance. The example " -"configuration in this scenario assumes basic configuration knowledge of " -"Networking service components." -msgstr "" - -#: ../deploy_scenario4b.rst:50 -msgid "" -"These prerequisites define the minimum physical infrastructure and OpenStack " -"service dependencies that you need to deploy this scenario. For example, the " -"Networking service immediately depends on the Identity service, and the " -"Compute service immediately depends on the Networking service. These " -"dependencies lack services such as the Image service because the Networking " -"service does not immediately depend on it. However, the Compute service " -"depends on the Image service to launch an instance. The example " -"configuration in this scenario assumes basic configuration knowledge of " -"Networking service components." -msgstr "" - -#: ../adv_config_ipv6.rst:34 -msgid "Things not in the scope of this document include:" -msgstr "" - -#: ../scenario_dvr_ovs.rst:463 -msgid "This configuration primarily supports the Kilo release." -msgstr "" - -#: ../config.rst:5 -msgid "" -"This content currently under development. For general configuration, see the " -"`Configuration Reference `_." -msgstr "" - -# #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../deploy_scenario4b.rst:509 ../scenario_provider_ovs.rst:560 -msgid "" -"This example creates a VLAN provider network. Change the VLAN ID and IP " -"address range to values suitable for your environment." -msgstr "" - -# #-#-#-#-# scenario_dvr_ovs.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_l3ha_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_l3ha_ovs.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../scenario_dvr_ovs.rst:754 ../scenario_l3ha_lb.rst:446 -#: ../scenario_l3ha_ovs.rst:456 ../scenario_legacy_lb.rst:761 -#: ../scenario_legacy_ovs.rst:863 -msgid "" -"This example creates a flat external network and a VXLAN project network." -msgstr "" - -# #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../deploy_scenario4b.rst:602 ../scenario_provider_ovs.rst:653 -msgid "" -"This example uses a CirrOS image that was manually uploaded into the Image " -"Service" -msgstr "" - -#: ../adv_config_ipv6.rst:500 -msgid "" -"This guide assumes that you are running a Dibbler server on the network node " -"where the external network bridge exists. If you already have a prefix " -"delegation capable DHCPv6 server in place, then you can skip the following " -"section." -msgstr "" - -#: ../index.rst:16 -msgid "" -"This guide documents OpenStack Kilo, OpenStack Juno, and OpenStack Icehouse " -"releases." -msgstr "" - -#: ../index.rst:19 -msgid "" -"This guide is a work-in-progress and changing rapidly while we continue to " -"test and enhance the guidance. Please note where there are open \"to do\" " -"items and help where you are able." -msgstr "" - -#: ../index.rst:13 -msgid "" -"This guide targets OpenStack administrators seeking to deploy and manage " -"OpenStack Networking (neutron)." -msgstr "" - -#: ../scenario_l3ha_lb.rst:8 -msgid "" -"This high-availability implementation augments the :doc:`scenario_legacy_lb` " -"architecture with Virtual Router Redundancy Protocol (VRRP) using " -"``keepalived`` to provide quick failover of layer-3 services. See :ref:" -"`scenario_l3ha_lb-packet_flow` for VRRP operation. Similar to the legacy " -"scenario, all network traffic on a project network that requires routing " -"actively traverses only one network node regardless of the quantity of " -"network nodes providing HA for the router. Therefore, this high-availability " -"implementation primarily addresses failure situations instead of bandwidth " -"constraints that limit performance. However, it supports random distribution " -"of routers on different network nodes to reduce the chances of bandwidth " -"constraints and to improve scaling. Also, this implementation does not " -"address situations where one or more layer-3 agents fail and the underlying " -"virtual networks continue to operate normally. Consider deploying :doc:" -"`scenario_dvr_ovs` to increase performance in addition to redundancy. As of " -"the Kilo release, you cannot combine the DVR and L3HA mechanisms." -msgstr "" - -#: ../scenario_l3ha_ovs.rst:8 -msgid "" -"This high-availability implementation augments the :doc:" -"`scenario_legacy_ovs` architecture with Virtual Router Redundancy Protocol " -"(VRRP) using ``keepalived`` to provide quick failover of layer-3 services. " -"See :ref:`scenario_l3ha_ovs-packet_flow` for VRRP operation. Similar to the " -"legacy scenario, all network traffic on a project network that requires " -"routing actively traverses only one network node regardless of the quantity " -"of network nodes providing HA for the router. Therefore, this high-" -"availability implementation primarily addresses failure situations instead " -"of bandwidth constraints that limit performance. However, it supports random " -"distribution of routers on different network nodes to reduce the chances of " -"bandwidth constraints and to improve scaling. Also, this implementation does " -"not address situations where one or more layer-3 agents fail and the " -"underlying virtual networks continue to operate normally. Consider " -"deploying :doc:`scenario_dvr_ovs` to increase performance in addition to " -"redundancy. As of the Kilo release, you cannot combine the DVR and L3HA " -"mechanisms." -msgstr "" - -#: ../intro_os_networking_overview.rst:124 -msgid "" -"This is a logical component that forwards data packets between networks. It " -"also provides L3 and NAT forwarding to provide external network access for " -"VMs on tenant networks. Required by certain plug-ins only." -msgstr "" - -#: ../adv_config_qos.rst:5 -msgid "" -"This page serves as a guide for how to use the \"Quality of Service\" (QoS) " -"functionality of OpenStack Networking." -msgstr "" - -#: ../scenario_l3ha_lb.rst:5 -msgid "" -"This scenario describes a high-availability implementation of the OpenStack " -"Networking service using the ML2 plug-in and Linux bridge." -msgstr "" - -#: ../scenario_l3ha_ovs.rst:5 -msgid "" -"This scenario describes a high-availability implementation of the OpenStack " -"Networking service using the ML2 plug-in and Open vSwitch (OVS)." -msgstr "" - -#: ../scenario_legacy_lb.rst:5 -msgid "" -"This scenario describes a legacy (basic) implementation of the OpenStack " -"Networking service using the ML2 plug-in with Linux bridge." -msgstr "" - -#: ../scenario_legacy_ovs.rst:5 -msgid "" -"This scenario describes a legacy (basic) implementation of the OpenStack " -"Networking service using the ML2 plug-in with Open vSwitch (OVS)." -msgstr "" - -#: ../deploy_scenario4b.rst:5 -msgid "" -"This scenario describes a provider networks implementation of the OpenStack " -"Networking service using the ML2 plug-in with Linux bridge." -msgstr "" - -#: ../scenario_provider_ovs.rst:5 -msgid "" -"This scenario describes a provider networks implementation of the OpenStack " -"Networking service using the ML2 plug-in with Open vSwitch (OVS)." -msgstr "" - -#: ../scenario_dvr_ovs.rst:5 -msgid "" -"This scenario describes the high-availability Distributed Virtual Routing " -"(DVR) implementation of the OpenStack Networking service using the ML2 plug-" -"in and Open vSwitch. The example configuration creates one flat external " -"network and one VXLAN project (tenant) network. However, This configuration " -"also supports VLAN external networks, VLAN project networks, and GRE project " -"networks." -msgstr "" - -#: ../scenario_dvr_ovs.rst:209 ../scenario_dvr_ovs.rst:297 -#: ../scenario_dvr_ovs.rst:395 -msgid "" -"This scenario supports both VLAN and GRE/VXLAN project networks. However, " -"the packet flow only considers one instance using a VXLAN project network " -"for simplicity." -msgstr "" - -#: ../migration_nova_network_to_neutron.rst:13 -msgid "" -"This section describes the process of migrating clouds based on the legacy " -"networking model to the OpenStack Networking model. This process requires " -"additional changes to both compute and networking to support the migration. " -"This document describes the overall process and the features required in " -"both Networking and Compute." -msgstr "" - -#: ../adv_config_ipv6.rst:482 -msgid "" -"This tells OpenStack Networking to use the prefix delegation mechanism for " -"subnet allocation when the user does not provide a CIDR or subnet pool id " -"when creating a subnet." -msgstr "" - -#: ../adv_config_sriov.rst:174 -msgid "" -"This tells nova that all VFs belonging to eth3 are allowed to be passed " -"through to VMs and belong to the neutron provider network physnet2. Restart " -"nova compute with :command:`service nova-compute restart` to let the changes " -"have effect." -msgstr "" - -#: ../adv_config_sriov.rst:85 -msgid "" -"Throughout this guide, eth3 is used as the PF and physnet2 is used as the " -"provider network configured as a VLAN range. You are expected to change this " -"according to your actual environment." -msgstr "" - -#: ../misc_libvirt.rst:104 -msgid "To activate the network after it has been deactivated::" -msgstr "" - -#: ../adv_config_ipv6.rst:689 -msgid "" -"To allow the neutron-pd-agent to communicate with prefix delegation servers, " -"you must set which network interface to use for external communication. In " -"DevStack the default for this is br-ex::" -msgstr "" - -#: ../intro_basic_networking.rst:157 -msgid "" -"To calculate the network number of an IP address, you must know the " -"*netmask* associated with the address. A netmask indicates how many of the " -"bits in the 32-bit IP address make up the network number." -msgstr "" - -#: ../intro_os_networking_overview.rst:47 -msgid "" -"To configure rich network topologies, you can create and configure networks " -"and subnets and instruct other OpenStack services like Compute to attach " -"virtual devices to ports on these networks. OpenStack Compute is a prominent " -"consumer of OpenStack Networking to provide connectivity for its instances. " -"In particular, OpenStack Networking supports each tenant having multiple " -"private networks and enables tenants to choose their own IP addressing " -"scheme, even if those IP addresses overlap with those that other tenants " -"use. There are two types of network, tenant and provider networks. It is " -"possible to share any of these types of networks among tenants as part of " -"the network creation process." -msgstr "" - -#: ../intro_os_networking_overview.rst:97 -msgid "" -"To configure rich network topologies, you can create and configure networks " -"and subnets and other OpenStack services like Compute will request to be " -"connected to these networks by requesting virtual ports. In particular, " -"Networking supports each tenant having multiple private networks and enables " -"tenants to choose their own IP addressing scheme, even if those IP addresses " -"overlap with those that other tenants use." -msgstr "" - -#: ../adv_config_sriov.rst:110 -msgid "" -"To create the VFs on Ubuntu for **Intel SR-IOV ethernet cards**, do the " -"following:" -msgstr "" - -#: ../misc_libvirt.rst:93 -msgid "To deactivate the libvirt network named *default*::" -msgstr "" - -#: ../adv_config_ipv6.rst:25 -msgid "" -"To enable a dual-stack network in OpenStack Networking simply requires " -"creating a subnet with the ``ip_version`` field set to ``6``, then the IPv6 " -"attributes (``ipv6_ra_mode`` and ``ipv6_address_mode``) set. The " -"``ipv6_ra_mode`` and ``ipv6_address_mode`` will be described in detail in " -"the next section. Finally, the subnets ``cidr`` needs to be provided." -msgstr "" - -#: ../adv_config_ipv6.rst:467 -msgid "To enable prefix delegation, edit the :file:`etc/neutron.conf` file::" -msgstr "" - -#: ../adv_config_ipv6.rst:684 -msgid "" -"To enable the driver for the dhcpv6_pd_agent, set pd_dhcp_driver to this in :" -"file:`etc/neutron.conf`::" -msgstr "" - -#: ../adv_config_qos.rst:62 -msgid "To enable the service, follow the steps below:" -msgstr "" - -#: ../scenario_legacy_ovs.rst:87 -msgid "" -"To improve understanding of network traffic flow, the network and compute " -"nodes contain a separate network interface for VLAN project networks. In " -"production environments, VLAN project networks can use any Open vSwitch " -"bridge with access to a network interface. For example, the ``br-tun`` " -"bridge." -msgstr "" - -#: ../scenario_legacy_lb.rst:84 -msgid "" -"To improve understanding of network traffic flow, the network and compute " -"nodes contain a separate network interface for VLAN project networks. In " -"production environments, you can use any network interface for VLAN project " -"networks." -msgstr "" - -#: ../scenario_l3ha_ovs.rst:68 -msgid "" -"To improve understanding of network traffic flow, the network and compute " -"nodes contain a separate network interface for project VLAN networks. In " -"production environments, project VLAN networks can use any Open vSwitch " -"bridge with access to a network interface. For example, the ``br-tun`` " -"bridge." -msgstr "" - -#: ../scenario_l3ha_lb.rst:66 -msgid "" -"To improve understanding of network traffic flow, the network and compute " -"nodes contain a separate network interface for project VLAN networks. In " -"production environments, you can use any network interface for VLAN project " -"networks." -msgstr "" - -#: ../adv_config_sriov.rst:244 -msgid "" -"To make the changes have effect, restart the neutron-server service with " -"the :command:`service neutron-server restart`." -msgstr "" - -#: ../misc_libvirt.rst:100 -msgid "To prevent the network from automatically starting on boot::" -msgstr "" - -#: ../adv_config_ipv6.rst:535 -msgid "" -"To provide external network access to your instances, your Dibbler server " -"also needs to create new routes for each delegated prefix. This is done " -"using the script file named in the config file above. Edit the :file:`/var/" -"lib/dibbler/pd-server.sh` file:" -msgstr "" - -#: ../intro_basic_networking.rst:211 -msgid "" -"To reduce the number of ARP requests, operating systems maintain an ARP " -"cache that contains the mappings of IP addresses to MAC address. On a Linux " -"machine, you can view the contents of the ARP cache by using the *arp* " -"command::" -msgstr "" - -#: ../adv_config_ipv6.rst:563 -msgid "To start your Dibbler server, run::" -msgstr "" - -#: ../adv_config_ipv6.rst:625 -msgid "" -"To trigger the prefix delegation process, create a router interface between " -"this subnet and a router with an active interface on the external network:" -msgstr "" - -#: ../intro_basic_networking.rst:178 -msgid "" -"To understand how ARP translates IP addresses to MAC addresses, consider the " -"following example. Assume host *A* has an IP address of ``192.168.1.5/24`` " -"and a MAC address of ``fc:99:47:49:d4:a0``, and wants to send a packet to " -"host *B* with an IP address of ``192.168.1.7``. Note that the network number " -"is the same for both hosts, so host *A* is able to send frames directly to " -"host *B*." -msgstr "" - -#: ../intro_basic_networking.rst:90 -msgid "" -"To understand how VLANs work, let's consider VLAN applications in a " -"traditional IT environment, where physical hosts are attached to a physical " -"switch, and no virtualization is involved. Imagine a scenario where you want " -"three isolated networks, but you only have a single physical switch. The " -"network administrator would choose three VLAN IDs, say, 10, 11, and 12, and " -"would configure the switch to associate switchports with VLAN IDs. For " -"example, switchport 2 might be associated with VLAN 10, switchport 3 might " -"be associated with VLAN 11, and so forth. When a switchport is configured " -"for a specific VLAN, it is called an *access port*. The switch is " -"responsible for ensuring that the network traffic is isolated across the " -"VLANs." -msgstr "" - -#: ../adv_config_ipv6.rst:489 -msgid "" -"To use this feature, you need a prefix delegation capable DHCPv6 server that " -"is reachable from your OpenStack Networking node(s). This could be software " -"running on the OpenStack Networking node(s) or elsewhere, or a physical " -"router. For the purposes of this guide we are using the open-source DHCPv6 " -"server, Dibbler. Dibbler is available in many Linux package managers, or " -"from source at https://github.com/tomaszmrugalski/dibbler." -msgstr "" - -#: ../misc_libvirt.rst:86 -msgid "To view the defined libvirt networks and their state::" -msgstr "" - -#: ../intro_basic_networking.rst:134 -msgid "" -"Trunking is used to connect between different switches. Each trunk uses a " -"tag to identify which VLAN is in use. This ensures that switches on the same " -"VLAN can communicate." -msgstr "" - -#: ../adv_config_qos.rst:80 -msgid "Trusted tenants policy.json configuration" -msgstr "" - -#: ../config_ml2_plug_in.rst:39 -msgid "Tunnel ID ranges" -msgstr "" - -#: ../intro_tunnel_technologies.rst:3 -msgid "Tunnel technologies" -msgstr "" - -#: ../intro_tunnel_technologies.rst:5 -msgid "" -"Tunneling allows one network protocol to encapsulate another payload " -"protocol such that packets from the payload protocol are passed as data on " -"the delivery protocol. For example, this can be used to pass data securely " -"over an untrusted network." -msgstr "" - -#: ../scenario_l3ha_ovs.rst:59 -msgid "" -"Two network nodes with four network interfaces: management, project tunnel " -"networks, project VLAN networks, and external (typically the Internet). The " -"Open vSwitch bridge ``br-vlan`` must contain a port on the VLAN interface " -"and Open vSwitch bridge ``br-ex`` must contain a port on the external " -"interface." -msgstr "" - -#: ../migration_nova_network_to_neutron.rst:5 -msgid "" -"Two networking models exist in OpenStack. The first is called legacy " -"networking (nova-network) and it is a sub-process embedded in the Compute " -"project (nova). This model has some limitations, such as creating complex " -"network topologies, extending its back-end implementation to vendor-specific " -"technologies, and providing tenant-specific networking elements. These " -"limitations are the main reasons the OpenStack Networking (neutron) model " -"was created." -msgstr "" - -#: ../intro_basic_networking.rst:444 -msgid "" -"UDP has support for one-to-many communication: sending a single packet to " -"multiple hosts. An application can broadcast a UDP packet to all of the " -"network hosts on a local network by setting the receiver IP address as the " -"special IP broadcast address ``255.255.255.255``. An application can also " -"send a UDP packet to a set of receivers using *IP multicast*. The intended " -"receiver applications join a multicast group by binding a UDP socket to a " -"special IP address that is one of the valid multicast group addresses. The " -"receiving hosts do not have to be on the same local network as the sender, " -"but the intervening routers must be configured to support IP multicast " -"routing. VXLAN is an example of a UDP-based protocol that uses IP multicast." -msgstr "" - -#: ../intro_basic_networking.rst:428 -msgid "" -"UDP, like TCP, uses the notion of ports to distinguish between different " -"applications running on the same system. Note, however, that operating " -"systems treat UDP ports separately from TCP ports. For example, it is " -"possible for one application to be associated with TCP port 16543 and a " -"separate application to be associated with UDP port 16543." -msgstr "" - -#: ../adv_config_ipv6.rst:430 -msgid "" -"Unlike IPv4 the MTU of a given network can be conveyed in the RA messages " -"sent by the router and not in the DHCP messages. In Kilo the MTU sent by " -"RADVD is always 1500, but in Liberty changes are planned to allow the RA to " -"send the proper MTU of the network." -msgstr "" - -#: ../adv_config_sriov.rst:226 -msgid "" -"Update the :file:`/etc/neutron/plugins/ml2/ml2_conf_sriov.ini` on each " -"controller. In our case the vendor_id is 8086 and the product_id is 10ed. " -"Tell neutron the vendor_id and product_id of the VFs that are supported." -msgstr "" - -#: ../adv_config_ipv6.rst:216 -msgid "Use of an external IPAM module to allocate the subnet" +#: ../deploy_scenario4b.rst:439 ../scenario_dvr_ovs.rst:638 +#: ../scenario_l3ha_lb.rst:363 ../scenario_l3ha_ovs.rst:374 +#: ../scenario_legacy_lb.rst:682 ../scenario_legacy_ovs.rst:784 +#: ../scenario_provider_ovs.rst:476 +msgid "DHCP agent" msgstr "" # #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# @@ -7311,126 +2946,22 @@ msgstr "" # #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# # #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# # #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../deploy_scenario4b.rst:347 ../scenario_dvr_ovs.rst:459 -#: ../scenario_l3ha_lb.rst:193 ../scenario_l3ha_ovs.rst:202 -#: ../scenario_legacy_lb.rst:523 ../scenario_legacy_ovs.rst:618 -#: ../scenario_provider_ovs.rst:370 -msgid "" -"Use the following example configuration as a template to deploy this " -"scenario in your environment." +#: ../deploy_scenario4b.rst:442 ../scenario_dvr_ovs.rst:642 +#: ../scenario_l3ha_lb.rst:367 ../scenario_l3ha_ovs.rst:378 +#: ../scenario_legacy_lb.rst:686 ../scenario_legacy_ovs.rst:788 +#: ../scenario_provider_ovs.rst:479 +msgid "Compute nodes" msgstr "" -# #-#-#-#-# adv_config_ipv6.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# adv_config_qos.pot (Networking Guide 0.9) #-#-#-#-# -#: ../adv_config_ipv6.rst:576 ../adv_config_qos.rst:98 -msgid "User workflow" -msgstr "" - -#: ../migration_nova_network_to_neutron.rst:27 -msgid "" -"Users are encouraged to take these tools, test them, provide feedback, and " -"then expand on the feature set to suit their own deployments; deployers that " -"refrain from participating in this process intending to wait for a path that " -"better suits their use case are likely to be disappointed." -msgstr "" - -#: ../intro_os_networking_overview.rst:62 -msgid "" -"Users create tenant networks for connectivity within projects. By default, " -"they are fully isolated and are not shared with other projects. OpenStack " -"Networking supports the following types of network isolation and overlay " -"technologies." -msgstr "" - -#: ../adv_config_ipv6.rst:3 -msgid "Using OpenStack Networking with IPv6" -msgstr "" - -#: ../adv_config_qos.rst:3 -msgid "Using OpenStack Networking with QoS" -msgstr "" - -#: ../adv_config_ipv6.rst:254 -msgid "Using SLAAC for addressing" -msgstr "" - -#: ../adv_config_sriov.rst:3 -msgid "Using SR-IOV functionality" -msgstr "" - -#: ../adv_config_ipv6.rst:215 -msgid "Using a PD client to request a prefix for a subnet from a PD server" -msgstr "" - -#: ../adv_config_sriov.rst:31 -msgid "VF" -msgstr "" - -# #-#-#-#-# config_ml2_plug_in.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# intro_os_networking_overview.pot (Networking Guide 0.9) #-#-#-#-# -#: ../config_ml2_plug_in.rst:19 ../config_ml2_plug_in.rst:33 -#: ../intro_os_networking_overview.rst:76 -msgid "VLAN" -msgstr "" - -#: ../intro_basic_networking.rst:81 -msgid "" -"VLAN is a networking technology that enables a single switch to act as if it " -"was multiple independent switches. Specifically, two hosts that are " -"connected to the same switch but on different VLANs do not see each other's " -"traffic. OpenStack is able to take advantage of VLANs to isolate the traffic " -"of different tenants, even if the tenants happen to have instances running " -"on the same compute host. Each VLAN has an associated numerical ID, between " -"1 and 4095. We say \"VLAN 15\" to refer to the VLAN with numerical ID of 15." -msgstr "" - -#: ../intro_basic_networking.rst:79 -msgid "VLANs" -msgstr "" - -# #-#-#-#-# adv_config_ipv6.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# adv_config_VPNaaS.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# intro_os_networking_service.pot (Networking Guide 0.9) #-#-#-#-# -#: ../adv_config_ipv6.rst:381 ../adv_config_VPNaaS.rst:3 -#: ../intro_os_networking_service.rst:69 -msgid "VPNaaS" -msgstr "" - -#: ../adv_config_ipv6.rst:383 -msgid "" -"VPNaaS supports IPv6, but support in Kilo and prior releases will have some " -"bugs that may limit how it can be used. More thorough and complete testing " -"and bug fixing is being done as part of the Liberty release. IPv6-based VPN " -"as a service is configured similar to the IPv4 configuration. Either or both " -"the ``peer_address`` and the ``peer_cidr`` can specified as an IPv6 address. " -"The choice of addressing modes and router modes described above should not " -"impact support." -msgstr "" - -#: ../config_ml2_plug_in.rst:23 ../config_ml2_plug_in.rst:41 -msgid "VXLAN" -msgstr "" - -#: ../intro_os_networking_overview.rst:79 -msgid "" -"VXLAN and GRE are encapsulation protocols that create overlay networks to " -"activate and control communication between compute instances. A Networking " -"router is required to allow traffic to flow outside of the GRE or VXLAN " -"tenant network. A router is also required to connect directly-connected " -"tenant networks with external networks, including the Internet. The router " -"provides the ability to connect to instances directly from an external " -"network using floating IP addresses." -msgstr "" - -# #-#-#-#-# scenario_dvr_ovs.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# # #-#-#-#-# scenario_l3ha_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_l3ha_ovs.pot (Networking Guide 0.9) #-#-#-#-# # #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# -# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../scenario_dvr_ovs.rst:1047 ../scenario_l3ha_lb.rst:906 -#: ../scenario_l3ha_ovs.rst:914 ../scenario_legacy_lb.rst:1037 -#: ../scenario_legacy_ovs.rst:1140 -msgid "Verify addition of the floating IP address to the instance:" +#: ../deploy_scenario4b.rst:465 ../scenario_l3ha_lb.rst:281 +#: ../scenario_l3ha_lb.rst:392 ../scenario_legacy_lb.rst:605 +#: ../scenario_legacy_lb.rst:711 +msgid "" +"Configure the Linux bridge agent. Edit the :file:`/etc/neutron/plugins/ml2/" +"ml2_conf.ini` file:" msgstr "" # #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# @@ -7440,11 +2971,30 @@ msgstr "" # #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# # #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# # #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../deploy_scenario4b.rst:566 ../scenario_dvr_ovs.rst:915 -#: ../scenario_l3ha_lb.rst:609 ../scenario_l3ha_ovs.rst:619 -#: ../scenario_legacy_lb.rst:915 ../scenario_legacy_ovs.rst:1018 -#: ../scenario_provider_ovs.rst:617 -msgid "Verify network operation" +#: ../deploy_scenario4b.rst:489 ../scenario_dvr_ovs.rst:728 +#: ../scenario_l3ha_lb.rst:420 ../scenario_l3ha_ovs.rst:430 +#: ../scenario_legacy_lb.rst:739 ../scenario_legacy_ovs.rst:841 +#: ../scenario_provider_ovs.rst:540 +msgid "Verify service operation" +msgstr "" + +# #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_dvr_ovs.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_l3ha_lb.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_l3ha_ovs.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../deploy_scenario4b.rst:491 ../deploy_scenario4b.rst:512 +#: ../scenario_dvr_ovs.rst:730 ../scenario_dvr_ovs.rst:756 +#: ../scenario_dvr_ovs.rst:930 ../scenario_l3ha_lb.rst:422 +#: ../scenario_l3ha_lb.rst:448 ../scenario_l3ha_lb.rst:611 +#: ../scenario_l3ha_ovs.rst:432 ../scenario_l3ha_ovs.rst:458 +#: ../scenario_l3ha_ovs.rst:621 ../scenario_legacy_lb.rst:741 +#: ../scenario_legacy_lb.rst:763 ../scenario_legacy_ovs.rst:843 +#: ../scenario_legacy_ovs.rst:865 ../scenario_provider_ovs.rst:542 +#: ../scenario_provider_ovs.rst:563 +msgid "Source the administrative project credentials." msgstr "" # #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# @@ -7468,39 +3018,247 @@ msgstr "" # #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# # #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# # #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# -#: ../deploy_scenario4b.rst:489 ../scenario_dvr_ovs.rst:728 -#: ../scenario_l3ha_lb.rst:420 ../scenario_l3ha_ovs.rst:430 -#: ../scenario_legacy_lb.rst:739 ../scenario_legacy_ovs.rst:841 -#: ../scenario_provider_ovs.rst:540 -msgid "Verify service operation" +#: ../deploy_scenario4b.rst:507 ../scenario_dvr_ovs.rst:752 +#: ../scenario_l3ha_lb.rst:444 ../scenario_l3ha_ovs.rst:454 +#: ../scenario_legacy_lb.rst:759 ../scenario_legacy_ovs.rst:861 +#: ../scenario_provider_ovs.rst:558 +msgid "Create initial networks" msgstr "" -#: ../adv_config_sriov.rst:32 +# #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../deploy_scenario4b.rst:509 ../scenario_provider_ovs.rst:560 msgid "" -"Virtual Function. This is a virtual PCIe device created from a physical " -"ethernet controller." +"This example creates a VLAN provider network. Change the VLAN ID and IP " +"address range to values suitable for your environment." msgstr "" -#: ../intro_tunnel_technologies.rst:19 -msgid "Virtual extensible local area network (VXLAN)" +# #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../deploy_scenario4b.rst:513 ../scenario_provider_ovs.rst:564 +msgid "Create a provider network:" msgstr "" -#: ../intro_network_namespaces.rst:48 -msgid "Virtual routing and forwarding (VRF)" +# #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../deploy_scenario4b.rst:538 ../scenario_provider_ovs.rst:589 +msgid "The ``shared`` option allows any project to use this network." msgstr "" -#: ../intro_network_namespaces.rst:50 +# #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../deploy_scenario4b.rst:540 ../scenario_provider_ovs.rst:591 +msgid "Create a subnet on the provider network:" +msgstr "" + +# #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_dvr_ovs.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_l3ha_lb.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_l3ha_ovs.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../deploy_scenario4b.rst:566 ../scenario_dvr_ovs.rst:915 +#: ../scenario_l3ha_lb.rst:609 ../scenario_l3ha_ovs.rst:619 +#: ../scenario_legacy_lb.rst:915 ../scenario_legacy_ovs.rst:1018 +#: ../scenario_provider_ovs.rst:617 +msgid "Verify network operation" +msgstr "" + +# #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../deploy_scenario4b.rst:568 ../scenario_provider_ovs.rst:619 +msgid "On the controller node, verify creation of the ``qdhcp`` namespace:" +msgstr "" + +# #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../deploy_scenario4b.rst:576 ../scenario_legacy_lb.rst:927 +#: ../scenario_legacy_ovs.rst:1030 ../scenario_provider_ovs.rst:627 +msgid "The ``qdhcp`` namespace might not exist until launching an instance." +msgstr "" + +# #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_l3ha_lb.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_l3ha_ovs.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../deploy_scenario4b.rst:578 ../scenario_l3ha_lb.rst:542 +#: ../scenario_l3ha_ovs.rst:798 ../scenario_legacy_lb.rst:856 +#: ../scenario_legacy_lb.rst:959 ../scenario_legacy_ovs.rst:958 +#: ../scenario_legacy_ovs.rst:1062 ../scenario_provider_ovs.rst:629 msgid "" -"Virtual routing and forwarding is an IP technology that allows multiple " -"instances of a routing table to coexist on the same router at the same time. " -"It is another name for the network namespace functionality described above." +"Source the regular project credentials. The following steps use the ``demo`` " +"project." msgstr "" -#: ../adv_config_sriov.rst:79 +# #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_dvr_ovs.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_l3ha_lb.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_l3ha_ovs.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../deploy_scenario4b.rst:580 ../scenario_dvr_ovs.rst:1003 +#: ../scenario_l3ha_lb.rst:792 ../scenario_l3ha_ovs.rst:800 +#: ../scenario_legacy_lb.rst:994 ../scenario_legacy_ovs.rst:1097 +#: ../scenario_provider_ovs.rst:631 msgid "" -"We recommend using Open vSwitch with VLAN as segration. This way you can " -"combine normal VMs without SR-IOV ports and instances with SR-IOV ports on a " -"single neutron network." +"Create the appropriate security group rules to allow ping and SSH access to " +"the instance. For example:" +msgstr "" + +# #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../deploy_scenario4b.rst:599 ../scenario_provider_ovs.rst:650 +msgid "Launch an instance with an interface on the provider network." +msgstr "" + +# #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../deploy_scenario4b.rst:602 ../scenario_provider_ovs.rst:653 +msgid "" +"This example uses a CirrOS image that was manually uploaded into the Image " +"Service" +msgstr "" + +# #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../deploy_scenario4b.rst:641 ../scenario_provider_ovs.rst:692 +msgid "" +"Determine the IP address of the instance. The following step uses " +"203.0.113.3." +msgstr "" + +# #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../deploy_scenario4b.rst:654 ../scenario_provider_ovs.rst:705 +msgid "" +"On the controller node or any host with access to the provider network, ping " +"the IP address of the instance:" +msgstr "" + +# #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../deploy_scenario4b.rst:670 ../scenario_provider_ovs.rst:721 +msgid "Obtain access to the instance." +msgstr "" + +# #-#-#-#-# deploy_scenario4b.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_dvr_ovs.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_l3ha_lb.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_l3ha_ovs.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../deploy_scenario4b.rst:671 ../scenario_dvr_ovs.rst:988 +#: ../scenario_l3ha_lb.rst:866 ../scenario_l3ha_ovs.rst:874 +#: ../scenario_legacy_lb.rst:979 ../scenario_legacy_ovs.rst:1082 +#: ../scenario_provider_ovs.rst:722 +msgid "Test connectivity to the Internet:" +msgstr "" + +#: ../index.rst:8 +msgid "OpenStack Networking Guide" +msgstr "" + +#: ../index.rst:11 +msgid "Abstract" +msgstr "" + +#: ../index.rst:13 +msgid "" +"This guide targets OpenStack administrators seeking to deploy and manage " +"OpenStack Networking (neutron)." +msgstr "" + +#: ../index.rst:16 +msgid "" +"This guide documents OpenStack Kilo, OpenStack Juno, and OpenStack Icehouse " +"releases." +msgstr "" + +#: ../index.rst:19 +msgid "" +"This guide is a work-in-progress and changing rapidly while we continue to " +"test and enhance the guidance. Please note where there are open \"to do\" " +"items and help where you are able." +msgstr "" + +#: ../index.rst:24 +msgid "Contents" +msgstr "" + +#: ../index.rst:43 +msgid "Search in this guide" +msgstr "" + +#: ../index.rst:45 +msgid ":ref:`search`" +msgstr "" + +#: ../intro_basic_networking.rst:3 +msgid "Basic networking" +msgstr "" + +#: ../intro_basic_networking.rst:6 +msgid "Ethernet" +msgstr "" + +#: ../intro_basic_networking.rst:8 +msgid "" +"Ethernet is a networking protocol, specified by the IEEE 802.3 standard. " +"Most wired network interface cards (NICs) communicate using Ethernet." +msgstr "" + +#: ../intro_basic_networking.rst:11 +msgid "" +"In the `OSI model`_ of networking protocols, Ethernet occupies the second " +"layer, which is known as the data link layer. When discussing Ethernet, you " +"will often hear terms such as *local network*, *layer 2*, *L2*, *link layer* " +"and *data link layer*." +msgstr "" + +#: ../intro_basic_networking.rst:16 +msgid "" +"In an Ethernet network, the hosts connected to the network communicate by " +"exchanging *frames*, which is the Ethernet terminology for packets. Every " +"host on an Ethernet network is uniquely identified by an address called the " +"media access control (MAC) address. In particular, in an OpenStack " +"environment, every virtual machine instance has a unique MAC address, which " +"is different from the MAC address of the compute host. A MAC address has 48 " +"bits and is typically represented as a hexadecimal string, such as " +"``08:00:27:b9:88:74``. The MAC address is hard-coded into the NIC by the " +"manufacturer, although modern NICs allow you to change the MAC address " +"programatically. In Linux, you can retrieve the MAC address of a NIC using " +"the ``ip`` command::" +msgstr "" + +#: ../intro_basic_networking.rst:32 +msgid "" +"Conceptually, you can think of an Ethernet network as a single bus that each " +"of the network hosts connects to. In early implementations, an Ethernet " +"network consisted of a single coaxial cable that hosts would tap into to " +"connect to the network. Modern Ethernet networks do not use this approach, " +"and instead each network host connects directly to a network device called a " +"*switch*. Still, this conceptual model is useful, and in network diagrams " +"(including those generated by the OpenStack dashboard) an Ethernet network " +"is often depicted as if it was a single bus. You'll sometimes hear an " +"Ethernet network referred to as a *layer 2 segment*." +msgstr "" + +#: ../intro_basic_networking.rst:43 +msgid "" +"In an Ethernet network, every host on the network can send a frame directly " +"to every other host. An Ethernet network also supports broadcasts, so that " +"one host can send a frame to every host on the network by sending to the " +"special MAC address ``ff:ff:ff:ff:ff:ff``. ARP_ and DHCP_ are two notable " +"protocols that use Ethernet broadcasts. Because Ethernet networks support " +"broadcasts, you will sometimes hear an Ethernet network referred to as a " +"*broadcast domain*." msgstr "" #: ../intro_basic_networking.rst:51 @@ -7515,6 +3273,75 @@ msgid "" "have the appropriate NICs configured for promiscuous mode." msgstr "" +#: ../intro_basic_networking.rst:61 +msgid "" +"As mentioned earlier, modern Ethernet networks use switches to interconnect " +"the network hosts. A switch is a box of networking hardware with a large " +"number of ports, that forwards Ethernet frames from one connected host to " +"another. When hosts first send frames over the switch, the switch doesn’t " +"know which MAC address is associated with which port. If an Ethernet frame " +"is destined for an unknown MAC address, the switch broadcasts the frame to " +"all ports. The port learns which MAC addresses are at which ports by " +"observing the traffic. Once it knows which MAC address is associated with a " +"port, it can send Ethernet frames to the correct port instead of " +"broadcasting. The switch maintains the mappings of MAC addresses to switch " +"ports in a table called a *forwarding table* or *forwarding information " +"base* (FIB). Switches can be daisy-chained together, and the resulting " +"connection of switches and hosts behaves like a single network." +msgstr "" + +#: ../intro_basic_networking.rst:79 +msgid "VLANs" +msgstr "" + +#: ../intro_basic_networking.rst:81 +msgid "" +"VLAN is a networking technology that enables a single switch to act as if it " +"was multiple independent switches. Specifically, two hosts that are " +"connected to the same switch but on different VLANs do not see each other's " +"traffic. OpenStack is able to take advantage of VLANs to isolate the traffic " +"of different tenants, even if the tenants happen to have instances running " +"on the same compute host. Each VLAN has an associated numerical ID, between " +"1 and 4095. We say \"VLAN 15\" to refer to the VLAN with numerical ID of 15." +msgstr "" + +#: ../intro_basic_networking.rst:90 +msgid "" +"To understand how VLANs work, let's consider VLAN applications in a " +"traditional IT environment, where physical hosts are attached to a physical " +"switch, and no virtualization is involved. Imagine a scenario where you want " +"three isolated networks, but you only have a single physical switch. The " +"network administrator would choose three VLAN IDs, say, 10, 11, and 12, and " +"would configure the switch to associate switchports with VLAN IDs. For " +"example, switchport 2 might be associated with VLAN 10, switchport 3 might " +"be associated with VLAN 11, and so forth. When a switchport is configured " +"for a specific VLAN, it is called an *access port*. The switch is " +"responsible for ensuring that the network traffic is isolated across the " +"VLANs." +msgstr "" + +#: ../intro_basic_networking.rst:102 +msgid "" +"Now consider the scenario that all of the switchports in the first switch " +"become occupied, and so the organization buys a second switch and connects " +"it to the first switch to expand the available number of switchports. The " +"second switch is also configured to support VLAN IDs 10, 11, and 12. Now " +"imagine host A connected to switch 1 on a port configured for VLAN ID 10 " +"sends an Ethernet frame intended for host B connected to switch 2 on a port " +"configured for VLAN ID 10. When switch 1 forwards the Ethernet frame to " +"switch 2, it must communicate that the frame is associated with VLAN ID 10." +msgstr "" + +#: ../intro_basic_networking.rst:112 +msgid "" +"If two switches are to be connected together, and the switches are " +"configured for VLANs, then the switchports used for cross-connecting the " +"switches must be configured to allow Ethernet frames from any VLAN to be " +"forwarded to the other switch. In addition, the sending switch must tag each " +"Ethernet frame with the VLAN ID so that the receiving switch can ensure that " +"only hosts on the matching VLAN are eligible to receive the frame." +msgstr "" + #: ../intro_basic_networking.rst:119 msgid "" "When a switchport is configured to pass frames from all VLANs and tag them " @@ -7523,45 +3350,32 @@ msgid "" "trunking is being used." msgstr "" -#: ../misc_libvirt.rst:43 +#: ../intro_basic_networking.rst:124 msgid "" -"When libvirt boots a virtual machine, it places the machine's VIF in the " -"bridge ``virbr0`` unless explicitly told not to." +"Note that if you are using VLANs on your physical switches to implement " +"tenant isolation in your OpenStack cloud, you must ensure that all of your " +"switchports are configured as trunk ports." msgstr "" -#: ../intro_network_address_translation.rst:56 +#: ../intro_basic_networking.rst:128 msgid "" -"When the router receives a packet with the matching IP address and port, it " -"translates these back to the private IP address and port, and forwards the " -"packet along." +"It is important that you select a VLAN range that your current network " +"infrastructure is not using. For example, if you estimate that your cloud " +"must support a maximum of 100 projects, pick a VLAN range outside of that " +"value, such as VLAN 200–299. OpenStack and all physical network " +"infrastructure that handles tenant networks must then support this VLAN " +"range." msgstr "" -#: ../intro_basic_networking.rst:260 +#: ../intro_basic_networking.rst:134 msgid "" -"When troubleshooting an instance that is not reachable over the network, it " -"can be helpful to examine this log to verify that all four steps of the DHCP " -"protocol were carried out for the instance in question." +"Trunking is used to connect between different switches. Each trunk uses a " +"tag to identify which VLAN is in use. This ensures that switches on the same " +"VLAN can communicate." msgstr "" -#: ../adv_config_ipv6.rst:571 -msgid "" -"When using DevStack, it is important to start your server after the :file:" -"`stack.sh` script has finished to ensure that the required network " -"interfaces have been created." -msgstr "" - -#: ../adv_config_ipv6.rst:256 -msgid "" -"When using SLAAC, the currently supported combinations for ``ipv6_ra_mode`` " -"and ``ipv6_address_mode`` are as follows." -msgstr "" - -#: ../adv_config_ipv6.rst:496 -msgid "" -"When using the reference implementation of the OpenStack Networking prefix " -"delegation driver, Dibbler must also be installed on your OpenStack " -"Networking node(s) to serve as a DHCPv6 client. Version 1.0.1 or higher is " -"required." +#: ../intro_basic_networking.rst:142 +msgid "Subnets and ARP" msgstr "" #: ../intro_basic_networking.rst:144 @@ -7571,34 +3385,88 @@ msgid "" "between Ethernet and IP by translating IP addresses into MAC addresses." msgstr "" -#: ../adv_config_sriov.rst:39 -msgid "Whitelist PCI devices in nova-compute (Compute)" -msgstr "" - -#: ../adv_config_sriov.rst:164 -msgid "Whitelist PCI devices nova-compute (Compute)" -msgstr "" - -#: ../adv_config_sriov.rst:57 +#: ../intro_basic_networking.rst:148 msgid "" -"With the sriov-agent mode is default in Liberty. Without the sriov-agent " -"mode is deprecated in Liberty and removed in Mitaka." +"IP addresses are broken up into two parts: a *network number* and a *host " +"identifier*. Two hosts are on the same *subnet* if they have the same " +"network number. Recall that two hosts can only communicate directly over " +"Ethernet if they are on the same local network. ARP assumes that all " +"machines that are in the same subnet are on the same local network. Network " +"administrators must take care when assigning IP addresses and netmasks to " +"hosts so that any two hosts that are in the same subnet are on the same " +"local network, otherwise ARP does not work properly." msgstr "" -#: ../adv_config_sriov.rst:48 -msgid "With the sriov-agent running on each compute node" -msgstr "" - -#: ../adv_config_sriov.rst:49 -msgid "Without the sriov-agent running on each compute node" -msgstr "" - -#: ../adv_config_qos.rst:194 +#: ../intro_basic_networking.rst:157 msgid "" -"You can attach networks to a QoS policy. The meaning of this is that any " -"compute port connected to the network will use the network policy by default " -"unless the port has a specific policy attached to it. Network owned ports " -"like dhcp and router ports are excluded from network policy application." +"To calculate the network number of an IP address, you must know the " +"*netmask* associated with the address. A netmask indicates how many of the " +"bits in the 32-bit IP address make up the network number." +msgstr "" + +#: ../intro_basic_networking.rst:161 +msgid "There are two syntaxes for expressing a netmask:" +msgstr "" + +#: ../intro_basic_networking.rst:163 +msgid "dotted quad" +msgstr "" + +#: ../intro_basic_networking.rst:164 +msgid "classless inter-domain routing (CIDR)" +msgstr "" + +#: ../intro_basic_networking.rst:166 +msgid "" +"Consider an IP address of 192.168.1.5, where the first 24 bits of the " +"address are the network number. In dotted quad notation, the netmask would " +"be written as ``255.255.255.0``. CIDR notation includes both the IP address " +"and netmask, and this example would be written as ``192.168.1.5/24``." +msgstr "" + +#: ../intro_basic_networking.rst:172 +msgid "" +"Sometimes we want to refer to a subnet, but not any particular IP address on " +"the subnet. A common convention is to set the host identifier to all zeros " +"to make reference to a subnet. For example, if a host's IP address is " +"``10.10.53.24/16``, then we would say the subnet is ``10.10.0.0/16``." +msgstr "" + +#: ../intro_basic_networking.rst:178 +msgid "" +"To understand how ARP translates IP addresses to MAC addresses, consider the " +"following example. Assume host *A* has an IP address of ``192.168.1.5/24`` " +"and a MAC address of ``fc:99:47:49:d4:a0``, and wants to send a packet to " +"host *B* with an IP address of ``192.168.1.7``. Note that the network number " +"is the same for both hosts, so host *A* is able to send frames directly to " +"host *B*." +msgstr "" + +#: ../intro_basic_networking.rst:185 +msgid "" +"The first time host *A* attempts to communicate with host *B*, the " +"destination MAC address is not known. Host *A* makes an ARP request to the " +"local network. The request is a broadcast with a message like this:" +msgstr "" + +#: ../intro_basic_networking.rst:190 +msgid "" +"*To: everybody (ff:ff:ff:ff:ff:ff). I am looking for the computer who has IP " +"address 192.168.1.7. Signed: MAC address fc:99:47:49:d4:a0*." +msgstr "" + +#: ../intro_basic_networking.rst:193 +msgid "Host *B* responds with a response like this:" +msgstr "" + +#: ../intro_basic_networking.rst:195 +msgid "" +"*To: fc:99:47:49:d4:a0. I have IP address 192.168.1.7. Signed: MAC address " +"54:78:1a:86:00:a5.*" +msgstr "" + +#: ../intro_basic_networking.rst:198 +msgid "Host *A* then sends Ethernet frames to host *B*." msgstr "" #: ../intro_basic_networking.rst:200 @@ -7607,18 +3475,362 @@ msgid "" "example, to send an ARP request to IP address ``10.30.0.132``::" msgstr "" -#: ../adv_config_qos.rst:221 +#: ../intro_basic_networking.rst:211 msgid "" -"You can modify rules at runtime. Rule modifications will be propagated to " -"any attached port." +"To reduce the number of ARP requests, operating systems maintain an ARP " +"cache that contains the mappings of IP addresses to MAC address. On a Linux " +"machine, you can view the contents of the ARP cache by using the *arp* " +"command::" msgstr "" -#: ../adv_config_sriov.rst:272 +#: ../intro_basic_networking.rst:225 msgid "" -"You only need to enable the sriov-agent if you decided to keep " -"``agent_required=True`` in the step `Configure neutron-server " -"(Controller)`_. If you set ``agent_required=False``, you can safely skip " -"this step." +"Hosts connected to a network use the Dynamic Host Configuration Protocol (:" +"term:`DHCP`) to dynamically obtain IP addresses. A DHCP server hands out the " +"IP addresses to network hosts, which are the DHCP clients." +msgstr "" + +#: ../intro_basic_networking.rst:230 +msgid "" +"DHCP clients locate the DHCP server by sending a UDP_ packet from port 68 to " +"address ``255.255.255.255`` on port 67. Address ``255.255.255.255`` is the " +"local network broadcast address: all hosts on the local network see the UDP " +"packets sent to this address. However, such packets are not forwarded to " +"other networks. Consequently, the DHCP server must be on the same local " +"network as the client, or the server will not receive the broadcast. The " +"DHCP server responds by sending a UDP packet from port 67 to port 68 on the " +"client. The exchange looks like this:" +msgstr "" + +#: ../intro_basic_networking.rst:240 +msgid "" +"The client sends a discover (\"I’m a client at MAC address ``08:00:27:" +"b9:88:74``, I need an IP address\")" +msgstr "" + +#: ../intro_basic_networking.rst:242 +msgid "" +"The server sends an offer (\"OK ``08:00:27:b9:88:74``, I’m offering IP " +"address ``10.10.0.112``\")" +msgstr "" + +#: ../intro_basic_networking.rst:244 +msgid "" +"The client sends a request (\"Server ``10.10.0.131``, I would like to have " +"IP ``10.10.0.112``\")" +msgstr "" + +#: ../intro_basic_networking.rst:246 +msgid "" +"The server sends an acknowledgement (\"OK ``08:00:27:b9:88:74``, IP " +"``10.10.0.112`` is yours\")" +msgstr "" + +#: ../intro_basic_networking.rst:250 +msgid "" +"OpenStack uses a third-party program called dnsmasq_ to implement the DHCP " +"server. Dnsmasq writes to the syslog (normally found at /var/log/syslog), " +"where you can observe the DHCP request and replies::" +msgstr "" + +#: ../intro_basic_networking.rst:260 +msgid "" +"When troubleshooting an instance that is not reachable over the network, it " +"can be helpful to examine this log to verify that all four steps of the DHCP " +"protocol were carried out for the instance in question." +msgstr "" + +#: ../intro_basic_networking.rst:269 +msgid "IP" +msgstr "" + +#: ../intro_basic_networking.rst:271 +msgid "" +"The Internet Protocol (IP) specifies how to route packets between hosts that " +"are connected to different local networks. IP relies on special network " +"hosts called *routers* or *gateways*. A router is a host that is connected " +"to at least two local networks and can forward IP packets from one local " +"network to another. A router has multiple IP addresses: one for each of the " +"networks it is connected to." +msgstr "" + +#: ../intro_basic_networking.rst:278 +msgid "" +"In the OSI model of networking protocols, IP occupies the third layer, which " +"is known as the network layer. When discussing IP, you will often hear terms " +"such as *layer 3*, *L3*, and *network layer*." +msgstr "" + +#: ../intro_basic_networking.rst:282 +msgid "" +"A host sending a packet to an IP address consults its *routing table* to " +"determine which machine on the local network(s) the packet should be sent " +"to. The routing table maintains a list of the subnets associated with each " +"local network that the host is directly connected to, as well as a list of " +"routers that are on these local networks." +msgstr "" + +#: ../intro_basic_networking.rst:288 +msgid "" +"On a Linux machine, any of the following commands displays the routing " +"table::" +msgstr "" + +#: ../intro_basic_networking.rst:294 +msgid "Here is an example of output from ``ip route show``::" +msgstr "" + +#: ../intro_basic_networking.rst:302 +msgid "" +"Line 1 of the output specifies the location of the default route, which is " +"the effective routing rule if none of the other rules match. The router " +"associated with the default route (``10.0.2.2`` in the example above) is " +"sometimes referred to as the *default gateway*. A DHCP_ server typically " +"transmits the IP address of the default gateway to the DHCP client along " +"with the client's IP address and a netmask." +msgstr "" + +#: ../intro_basic_networking.rst:309 +msgid "" +"Line 2 of the output specifies that IPs in the 10.0.2.0/24 subnet are on the " +"local network associated with the network interface eth0." +msgstr "" + +#: ../intro_basic_networking.rst:312 +msgid "" +"Line 3 of the output specifies that IPs in the 192.168.27.0/24 subnet are on " +"the local network associated with the network interface eth1." +msgstr "" + +#: ../intro_basic_networking.rst:315 +msgid "" +"Line 4 of the output specifies that IPs in the 192.168.122/24 subnet are on " +"the local network associated with the network interface virbr0." +msgstr "" + +#: ../intro_basic_networking.rst:318 +msgid "" +"The output of the ``route -n`` and ``netstat -rn`` commands are formatted in " +"a slightly different way. This example shows how the same routes would be " +"formatted using these commands::" +msgstr "" + +#: ../intro_basic_networking.rst:330 +msgid "" +"The ``ip route get`` command outputs the route for a destination IP address. " +"From the above example, destination IP address 10.0.2.14 is on the local " +"network of eth0 and would be sent directly::" +msgstr "" + +#: ../intro_basic_networking.rst:337 +msgid "" +"The destination IP address 93.184.216.34 is not on any of the connected " +"local networks and would be forwarded to the default gateway at 10.0.2.2::" +msgstr "" + +#: ../intro_basic_networking.rst:343 +msgid "" +"It is common for a packet to hop across multiple routers to reach its final " +"destination. On a Linux machine, the ``traceroute`` and more recent ``mtr`` " +"programs prints out the IP address of each router that an IP packet " +"traverses along its path to its destination." +msgstr "" + +#: ../intro_basic_networking.rst:351 +msgid "TCP/UDP/ICMP" +msgstr "" + +#: ../intro_basic_networking.rst:353 +msgid "" +"For networked software applications to communicate over an IP network, they " +"must use a protocol layered atop IP. These protocols occupy the fourth layer " +"of the OSI model known as the *transport layer* or *layer 4*. See the " +"`Protocol Numbers`_ web page maintained by the Internet Assigned Numbers " +"Authority (IANA) for a list of protocols that layer atop IP and their " +"associated numbers." +msgstr "" + +#: ../intro_basic_networking.rst:362 +msgid "" +"The *Transmission Control Protocol* (TCP) is the most commonly used layer 4 " +"protocol in networked applications. TCP is a *connection-oriented* protocol: " +"it uses a client-server model where a client connects to a server, where " +"*server* refers to the application that receives connections. The typical " +"interaction in a TCP-based application proceeds as follows:" +msgstr "" + +#: ../intro_basic_networking.rst:370 +msgid "Client connects to server." +msgstr "" + +#: ../intro_basic_networking.rst:371 +msgid "Client and server exchange data." +msgstr "" + +#: ../intro_basic_networking.rst:372 +msgid "Client or server disconnects." +msgstr "" + +#: ../intro_basic_networking.rst:374 +msgid "" +"Because a network host may have multiple TCP-based applications running, TCP " +"uses an addressing scheme called *ports* to uniquely identify TCP-based " +"applications. A TCP port is associated with a number in the range 1-65535, " +"and only one application on a host can be associated with a TCP port at a " +"time, a restriction that is enforced by the operating system." +msgstr "" + +#: ../intro_basic_networking.rst:380 +msgid "" +"A TCP server is said to *listen* on a port. For example, an SSH server " +"typically listens on port 22. For a client to connect to a server using TCP, " +"the client must know both the IP address of a server's host and the server's " +"TCP port." +msgstr "" + +#: ../intro_basic_networking.rst:385 +msgid "" +"The operating system of the TCP client application automatically assigns a " +"port number to the client. The client owns this port number until the TCP " +"connection is terminated, after which time the operating system reclaims the " +"port number. These types of ports are referred to as *ephemeral ports*." +msgstr "" + +#: ../intro_basic_networking.rst:391 +msgid "" +"IANA maintains a `registry of port numbers`_ for many TCP-based services, as " +"well as services that use other layer 4 protocols that employ ports. " +"Registering a TCP port number is not required, but registering a port number " +"is helpful to avoid collisions with other services. See `Appendix B. " +"Firewalls and default ports`_ of the `OpenStack Configuration Reference`_ " +"for the default TCP ports used by various services involved in an OpenStack " +"deployment." +msgstr "" + +#: ../intro_basic_networking.rst:404 +msgid "" +"The most common application programming interface (API) for writing TCP-" +"based applications is called *Berkeley sockets*, also known as *BSD sockets* " +"or, simply, *sockets*. The sockets API exposes a *stream oriented* interface " +"for writing TCP applications: from the perspective of a programmer, sending " +"data over a TCP connection is similar to writing a stream of bytes to a " +"file. It is the responsibility of the operating system's TCP/IP " +"implementation to break up the stream of data into IP packets. The operating " +"system is also responsible for automatically retransmitting dropped packets, " +"and for handling flow control to ensure that transmitted data does not " +"overrun the sender's data buffers, receiver's data buffers, and network " +"capacity. Finally, the operating system is responsible for re-assembling the " +"packets in the correct order into a stream of data on the receiver's side. " +"Because TCP detects and retransmits lost packets, it is said to be a " +"*reliable* protocol." +msgstr "" + +#: ../intro_basic_networking.rst:419 +msgid "" +"The *User Datagram Protocol* (UDP) is another layer 4 protocol that is the " +"basis of several well-known networking protocols. UDP is a *connectionless* " +"protocol: two applications that communicate over UDP do not need to " +"establish a connection before exchanging data. UDP is also an *unreliable* " +"protocol. The operating system does not attempt to retransmit or even detect " +"lost UDP packets. The operating system also does not provide any guarantee " +"that the receiving application sees the UDP packets in the same order that " +"they were sent in." +msgstr "" + +#: ../intro_basic_networking.rst:428 +msgid "" +"UDP, like TCP, uses the notion of ports to distinguish between different " +"applications running on the same system. Note, however, that operating " +"systems treat UDP ports separately from TCP ports. For example, it is " +"possible for one application to be associated with TCP port 16543 and a " +"separate application to be associated with UDP port 16543." +msgstr "" + +#: ../intro_basic_networking.rst:434 +msgid "" +"Like TCP, the sockets API is the most common API for writing UDP-based " +"applications. The sockets API provides a *message-oriented* interface for " +"writing UDP applications: a programmer sends data over UDP by transmitting a " +"fixed-sized message. If an application requires retransmissions of lost " +"packets or a well-defined ordering of received packets, the programmer is " +"responsible for implementing this functionality in the application code." +msgstr "" + +#: ../intro_basic_networking.rst:441 +msgid "" +"DHCP_, the Domain Name System (DNS), the Network Time Protocol (NTP), and :" +"ref:`VXLAN` are examples of UDP-based protocols used in OpenStack " +"deployments." +msgstr "" + +#: ../intro_basic_networking.rst:444 +msgid "" +"UDP has support for one-to-many communication: sending a single packet to " +"multiple hosts. An application can broadcast a UDP packet to all of the " +"network hosts on a local network by setting the receiver IP address as the " +"special IP broadcast address ``255.255.255.255``. An application can also " +"send a UDP packet to a set of receivers using *IP multicast*. The intended " +"receiver applications join a multicast group by binding a UDP socket to a " +"special IP address that is one of the valid multicast group addresses. The " +"receiving hosts do not have to be on the same local network as the sender, " +"but the intervening routers must be configured to support IP multicast " +"routing. VXLAN is an example of a UDP-based protocol that uses IP multicast." +msgstr "" + +#: ../intro_basic_networking.rst:456 +msgid "" +"The *Internet Control Message Protocol* (ICMP) is a protocol used for " +"sending control messages over an IP network. For example, a router that " +"receives an IP packet may send an ICMP packet back to the source if there is " +"no route in the router's routing table that corresponds to the destination " +"address (ICMP code 1, destination host unreachable) or if the IP packet is " +"too large for the router to handle (ICMP code 4, fragmentation required and " +"\"don't fragment\" flag is set)." +msgstr "" + +#: ../intro_basic_networking.rst:464 +msgid "" +"The *ping* and *mtr* Linux command-line tools are two examples of network " +"utilities that use ICMP." +msgstr "" + +#: ../intro_network_address_translation.rst:3 +msgid "Network address translation" +msgstr "" + +#: ../intro_network_address_translation.rst:5 +msgid "" +"*Network Address Translation* (NAT) is a process for modifying the source or " +"destination addresses in the headers of an IP packet while the packet is in " +"transit. In general, the sender and receiver applications are not aware that " +"the IP packets are being manipulated." +msgstr "" + +#: ../intro_network_address_translation.rst:10 +msgid "" +"NAT is often implemented by routers, and so we will refer to the host " +"performing NAT as a *NAT router*. However, in OpenStack deployments it is " +"typically Linux servers that implement the NAT functionality, not hardware " +"routers. These servers use the iptables_ software package to implement the " +"NAT functionality." +msgstr "" + +#: ../intro_network_address_translation.rst:16 +msgid "" +"There are multiple variations of NAT, and here we describe three kinds " +"commonly found in OpenStack deployments." +msgstr "" + +#: ../intro_network_address_translation.rst:22 +msgid "SNAT" +msgstr "" + +#: ../intro_network_address_translation.rst:24 +msgid "" +"In *Source Network Address Translation* (SNAT), the NAT router modifies the " +"IP address of the sender in IP packets. SNAT is commonly used to enable " +"hosts with *private addresses* to communicate with servers on the public " +"Internet." msgstr "" #: ../intro_network_address_translation.rst:29 @@ -7637,34 +3849,923 @@ msgstr "" msgid "``192.168.0.0/16``" msgstr "" -#: ../adv_config_ipv6.rst:60 -msgid "``dhcpv6-stateful``" -msgstr "" - -#: ../adv_config_ipv6.rst:61 -msgid "``dhcpv6-stateless``" -msgstr "" - -#: ../adv_config_ipv6.rst:55 -msgid "``ipv6_address_mode``" -msgstr "" - -#: ../adv_config_ipv6.rst:247 +#: ../intro_network_address_translation.rst:37 msgid "" -"``ipv6_address_mode``: Determines how instances obtain IPv6 address, default " -"gateway, or optional information." +"These IP addresses are not publicly routable, meaning that a host on the " +"public Internet can not send an IP packet to any of these addresses. Private " +"IP addresses are widely used in both residential and corporate environments." msgstr "" -#: ../adv_config_ipv6.rst:54 -msgid "``ipv6_ra_mode``" +#: ../intro_network_address_translation.rst:41 +msgid "" +"Often, an application running on a host with a private IP address will need " +"to connect to a server on the public Internet. One such example is a user " +"who wants to access a public website such as www.openstack.org. If the IP " +"packets reach the web server at www.openstack.org with a private IP address " +"as the source, then the web server cannot send packets back to the sender." msgstr "" -#: ../adv_config_ipv6.rst:246 -msgid "``ipv6_ra_mode``: Determines who sends RA." +#: ../intro_network_address_translation.rst:47 +msgid "" +"SNAT solves this problem by modifying the source IP address to an IP address " +"that is routable on the public Internet. There are different variations of " +"SNAT; in the form that OpenStack deployments use, a NAT router on the path " +"between the sender and receiver replaces the packet's source IP address with " +"the router's public IP address. The router also modifies the source TCP or " +"UDP port to another value, and the router maintains a record of the sender's " +"true IP address and port, as well as the modified IP address and port." msgstr "" -#: ../adv_config_ipv6.rst:59 -msgid "``slaac``" +#: ../intro_network_address_translation.rst:56 +msgid "" +"When the router receives a packet with the matching IP address and port, it " +"translates these back to the private IP address and port, and forwards the " +"packet along." +msgstr "" + +#: ../intro_network_address_translation.rst:60 +msgid "" +"Because the NAT router modifies ports as well as IP addresses, this form of " +"SNAT is sometimes referred to as *Port Address Translation* (PAT). It is " +"also sometimes referred to as *NAT overload*." +msgstr "" + +#: ../intro_network_address_translation.rst:64 +msgid "" +"OpenStack uses SNAT to enable applications running inside of instances to " +"connect out to the public Internet." +msgstr "" + +#: ../intro_network_address_translation.rst:68 +msgid "DNAT" +msgstr "" + +#: ../intro_network_address_translation.rst:70 +msgid "" +"In *Destination Network Address Translation* (DNAT), the NAT router modifies " +"the IP address of the destination in IP packet headers." +msgstr "" + +#: ../intro_network_address_translation.rst:73 +msgid "" +"OpenStack uses DNAT to route packets from instances to the OpenStack " +"metadata service. Applications running inside of instances access the " +"OpenStack metadata service by making HTTP GET requests to a web server with " +"IP address 169.254.169.254. In an OpenStack deployment, there is no host " +"with this IP address. Instead, OpenStack uses DNAT to change the destination " +"IP of these packets so they reach the network interface that a metadata " +"service is listening on." +msgstr "" + +#: ../intro_network_address_translation.rst:82 +msgid "One-to-one NAT" +msgstr "" + +#: ../intro_network_address_translation.rst:84 +msgid "" +"In *one-to-one NAT*, the NAT router maintains a one-to-one mapping between " +"private IP addresses and public IP addresses. OpenStack uses one-to-one NAT " +"to implement floating IP addresses." +msgstr "" + +#: ../intro_network_namespaces.rst:3 +msgid "Network namespaces" +msgstr "" + +#: ../intro_network_namespaces.rst:5 +msgid "" +"A namespace is a way of scoping a particular set of identifiers. Using a " +"namespace, you can use the same identifier multiple times in different " +"namespaces. You can also restrict an identifier set visible to particular " +"processes." +msgstr "" + +#: ../intro_network_namespaces.rst:10 +msgid "" +"For example, Linux provides namespaces for networking and processes, among " +"other things. If a process is running within a process namespace, it can " +"only see and communicate with other processes in the same namespace. So, if " +"a shell in a particular process namespace ran :command:`ps waux`, it would " +"only show the other processes in the same namespace." +msgstr "" + +#: ../intro_network_namespaces.rst:17 +msgid "Linux network namespaces" +msgstr "" + +#: ../intro_network_namespaces.rst:19 +msgid "" +"In a network namespace, the scoped 'identifiers' are network devices; so a " +"given network device, such as ``eth0``, exists in a particular namespace. " +"Linux starts up with a default network namespace, so if your operating " +"system does not do anything special, that is where all the network devices " +"will be located. But it is also possible to create further non-default " +"namespaces, and create new devices in those namespaces, or to move an " +"existing device from one namespace to another." +msgstr "" + +#: ../intro_network_namespaces.rst:27 +msgid "" +"Each network namespace also has its own routing table, and in fact this is " +"the main reason for namespaces to exist. A routing table is keyed by " +"destination IP address, so network namespaces are what you need if you want " +"the same destination IP address to mean different things at different times " +"- which is something that OpenStack Networking requires for its feature of " +"providing overlapping IP addresses in different virtual networks." +msgstr "" + +#: ../intro_network_namespaces.rst:34 +msgid "" +"Each network namespace also has its own set of iptables (for both IPv4 and " +"IPv6). So, you can apply different security to flows with the same IP " +"addressing in different namespaces, as well as different routing." +msgstr "" + +#: ../intro_network_namespaces.rst:38 +msgid "" +"Any given Linux process runs in a particular network namespace. By default " +"this is inherited from its parent process, but a process with the right " +"capabilities can switch itself into a different namespace; in practice this " +"is mostly done using the :command:`ip netns exec NETNS COMMAND...` " +"invocation, which starts ``COMMAND`` running in the namespace named " +"``NETNS``. Suppose such a process sends out a message to IP address A.B.C.D, " +"the effect of the namespace is that A.B.C.D will be looked up in that " +"namespace's routing table, and that will determine the network device that " +"the message is transmitted through." +msgstr "" + +#: ../intro_network_namespaces.rst:48 +msgid "Virtual routing and forwarding (VRF)" +msgstr "" + +#: ../intro_network_namespaces.rst:50 +msgid "" +"Virtual routing and forwarding is an IP technology that allows multiple " +"instances of a routing table to coexist on the same router at the same time. " +"It is another name for the network namespace functionality described above." +msgstr "" + +#: ../intro_networking.rst:3 +msgid "Introduction to networking" +msgstr "" + +#: ../intro_networking.rst:5 +msgid "" +"The OpenStack Networking service provides an API that allows users to set up " +"and define network connectivity and addressing in the cloud. The project " +"code-name for Networking services is neutron. OpenStack Networking handles " +"the creation and management of a virtual networking infrastructure, " +"including networks, switches, subnets, and routers for devices managed by " +"the OpenStack Compute service (nova). Advanced services such as firewalls or " +"virtual private networks (VPNs) can also be used." +msgstr "" + +#: ../intro_networking.rst:14 +msgid "" +"OpenStack Networking consists of the neutron-server, a database for " +"persistent storage, and any number of plug-in agents, which provide other " +"services such as interfacing with native Linux networking mechanisms, " +"external devices, or SDN controllers." +msgstr "" + +#: ../intro_networking.rst:19 +msgid "" +"OpenStack Networking is entirely standalone and can be deployed to a " +"dedicated host. If your deployment uses a controller host to run centralized " +"Compute components, you can deploy the Networking server to that specific " +"host instead." +msgstr "" + +#: ../intro_networking.rst:24 +msgid "" +"OpenStack Networking integrates with various other OpenStack components:" +msgstr "" + +#: ../intro_networking.rst:27 +msgid "" +"OpenStack Identity (keystone) is used for authentication and authorization " +"of API requests." +msgstr "" + +#: ../intro_networking.rst:30 +msgid "" +"OpenStack Compute (nova) is used to plug each virtual NIC on the VM into a " +"particular network." +msgstr "" + +#: ../intro_networking.rst:33 +msgid "" +"OpenStack dashboard (horizon) is used by administrators and tenant users to " +"create and manage network services through a web-based graphical interface." +msgstr "" + +#: ../intro_networking_components.rst:3 +msgid "Network components" +msgstr "" + +#: ../intro_networking_components.rst:6 +msgid "Switches" +msgstr "" + +#: ../intro_networking_components.rst:8 +msgid "" +"A switch is a device that is used to connect devices on a network. Switches " +"forward packets on to other devices, using packet switching to pass data " +"along only to devices that need to receive it. Switches operate at layer 2 " +"of the OSI model." +msgstr "" + +# #-#-#-#-# intro_networking_components.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# intro_os_networking_overview.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../intro_networking_components.rst:14 +#: ../intro_os_networking_overview.rst:122 ../scenario_legacy_lb.rst:39 +#: ../scenario_legacy_ovs.rst:39 +msgid "Routers" +msgstr "" + +#: ../intro_networking_components.rst:16 +msgid "" +"A router is a networking device that connects multiple networks together. " +"Routers are connected to two or more networks. When they receive data " +"packets, they use a routing table to determine which networks to pass the " +"information to." +msgstr "" + +#: ../intro_networking_components.rst:22 +msgid "Firewalls" +msgstr "" + +#: ../intro_networking_components.rst:24 +msgid "" +"A firewall is a network device that controls the incoming and outgoing " +"network traffic based on an applied rule set." +msgstr "" + +#: ../intro_networking_components.rst:28 +msgid "Load balancers" +msgstr "" + +#: ../intro_networking_components.rst:30 +msgid "" +"A load balancer is a network device that distributes network or application " +"traffic across a number of servers." +msgstr "" + +#: ../intro_os_networking.rst:3 +msgid "Introduction to OpenStack Networking (neutron)" +msgstr "" + +#: ../intro_os_networking_overview.rst:3 +msgid "Overview and components" +msgstr "" + +#: ../intro_os_networking_overview.rst:5 +msgid "" +"OpenStack Networking allows you to create and manage network objects, such " +"as networks, subnets, and ports, which other OpenStack services can use. " +"Plug-ins can be implemented to accommodate different networking equipment " +"and software, providing flexibility to OpenStack architecture and deployment." +msgstr "" + +#: ../intro_os_networking_overview.rst:11 +msgid "" +"The Networking service, code-named neutron, provides an API that lets you " +"define network connectivity and addressing in the cloud. The Networking " +"service enables operators to leverage different networking technologies to " +"power their cloud networking. The Networking service also provides an API to " +"configure and manage a variety of network services ranging from L3 " +"forwarding and NAT to load balancing, perimeter firewalls, and virtual " +"private networks." +msgstr "" + +#: ../intro_os_networking_overview.rst:19 +msgid "It includes the following components:" +msgstr "" + +#: ../intro_os_networking_overview.rst:22 +msgid "" +"The OpenStack Networking API includes support for Layer 2 networking and IP " +"address management (IPAM), as well as an extension for a Layer 3 router " +"construct that enables routing between Layer 2 networks and gateways to " +"external networks. OpenStack Networking includes a growing list of plug-ins " +"that enable interoperability with various commercial and open source network " +"technologies, including routers, switches, virtual switches and software-" +"defined networking (SDN) controllers." +msgstr "" + +#: ../intro_os_networking_overview.rst:29 +msgid "API server" +msgstr "" + +#: ../intro_os_networking_overview.rst:32 +msgid "" +"Plugs and unplugs ports, creates networks or subnets, and provides IP " +"addressing. The chosen plug-in and agents differ depending on the vendor and " +"technologies used in the particular cloud. It is important to mention that " +"only one plug-in can be used at a time." +msgstr "" + +#: ../intro_os_networking_overview.rst:35 +msgid "OpenStack Networking plug-in and agents" +msgstr "" + +#: ../intro_os_networking_overview.rst:38 +msgid "" +"Accepts and routes RPC requests between agents to complete API operations. " +"Message queue is used in the ML2 plug-in for RPC between the neutron server " +"and neutron agents that run on each hypervisor, in the ML2 mechanism drivers " +"for :term:`Open vSwitch` and :term:`Linux bridge`." +msgstr "" + +#: ../intro_os_networking_overview.rst:42 +msgid "Messaging queue" +msgstr "" + +#: ../intro_os_networking_overview.rst:45 +msgid "OpenStack Networking concepts" +msgstr "" + +#: ../intro_os_networking_overview.rst:47 +msgid "" +"To configure rich network topologies, you can create and configure networks " +"and subnets and instruct other OpenStack services like Compute to attach " +"virtual devices to ports on these networks. OpenStack Compute is a prominent " +"consumer of OpenStack Networking to provide connectivity for its instances. " +"In particular, OpenStack Networking supports each tenant having multiple " +"private networks and enables tenants to choose their own IP addressing " +"scheme, even if those IP addresses overlap with those that other tenants " +"use. There are two types of network, tenant and provider networks. It is " +"possible to share any of these types of networks among tenants as part of " +"the network creation process." +msgstr "" + +#: ../intro_os_networking_overview.rst:60 +msgid "Tenant networks" +msgstr "" + +#: ../intro_os_networking_overview.rst:62 +msgid "" +"Users create tenant networks for connectivity within projects. By default, " +"they are fully isolated and are not shared with other projects. OpenStack " +"Networking supports the following types of network isolation and overlay " +"technologies." +msgstr "" + +#: ../intro_os_networking_overview.rst:67 +msgid "" +"All instances reside on the same network, which can also be shared with the " +"hosts. No VLAN tagging or other network segregation takes place." +msgstr "" + +#: ../intro_os_networking_overview.rst:71 +msgid "" +"Networking allows users to create multiple provider or tenant networks using " +"VLAN IDs (802.1Q tagged) that correspond to VLANs present in the physical " +"network. This allows instances to communicate with each other across the " +"environment. They can also communicate with dedicated servers, firewalls, " +"load balancers, and other networking infrastructure on the same layer 2 VLAN." +msgstr "" + +#: ../intro_os_networking_overview.rst:79 +msgid "" +"VXLAN and GRE are encapsulation protocols that create overlay networks to " +"activate and control communication between compute instances. A Networking " +"router is required to allow traffic to flow outside of the GRE or VXLAN " +"tenant network. A router is also required to connect directly-connected " +"tenant networks with external networks, including the Internet. The router " +"provides the ability to connect to instances directly from an external " +"network using floating IP addresses." +msgstr "" + +#: ../intro_os_networking_overview.rst:85 +msgid "GRE and VXLAN" +msgstr "" + +#: ../intro_os_networking_overview.rst:88 +msgid "Provider networks" +msgstr "" + +#: ../intro_os_networking_overview.rst:90 +msgid "" +"The OpenStack administrator creates provider networks. These networks map to " +"existing physical networks in the data center. Useful network types in this " +"category are flat (untagged) and VLAN (802.1Q tagged)." +msgstr "" + +#: ../intro_os_networking_overview.rst:97 +msgid "" +"To configure rich network topologies, you can create and configure networks " +"and subnets and other OpenStack services like Compute will request to be " +"connected to these networks by requesting virtual ports. In particular, " +"Networking supports each tenant having multiple private networks and enables " +"tenants to choose their own IP addressing scheme, even if those IP addresses " +"overlap with those that other tenants use." +msgstr "" + +#: ../intro_os_networking_overview.rst:105 +msgid "Subnets" +msgstr "" + +#: ../intro_os_networking_overview.rst:107 +msgid "" +"A block of IP addresses and associated configuration state. This is also " +"known as the native IPAM (IP Address Management) provided by the networking " +"service for both tenant and provider networks. Subnets are used to allocate " +"IP addresses when new ports are created on a network." +msgstr "" + +#: ../intro_os_networking_overview.rst:114 +msgid "Ports" +msgstr "" + +#: ../intro_os_networking_overview.rst:116 +msgid "" +"A port is a connection point for attaching a single device, such as the NIC " +"of a virtual server, to a virtual network. Also describes the associated " +"network configuration, such as the MAC and IP addresses to be used on that " +"port." +msgstr "" + +#: ../intro_os_networking_overview.rst:124 +msgid "" +"This is a logical component that forwards data packets between networks. It " +"also provides L3 and NAT forwarding to provide external network access for " +"VMs on tenant networks. Required by certain plug-ins only." +msgstr "" + +#: ../intro_os_networking_overview.rst:130 +msgid "Security groups" +msgstr "" + +#: ../intro_os_networking_overview.rst:132 +msgid "" +"A security group acts as a virtual firewall for your compute instances to " +"control inbound and outbound traffic. Security groups act at the port level, " +"not the subnet level. Therefore, each port in a subnet could be assigned to " +"a different set of security groups. If you don't specify a particular group " +"at launch time, the instance is automatically assigned to the default " +"security group for that network." +msgstr "" + +#: ../intro_os_networking_overview.rst:139 +msgid "" +"Security groups and security group rules give administrators and tenants the " +"ability to specify the type of traffic and direction (ingress/egress) that " +"is allowed to pass through a port. A security group is a container for " +"security group rules. When a port is created, it is associated with a " +"security group. If a security group is not specified, the port is associated " +"with a 'default' security group. By default, this group drops all ingress " +"traffic and allows all egress. Rules can be added to this group in order to " +"change the behavior." +msgstr "" + +#: ../intro_os_networking_overview.rst:148 +msgid "Extensions" +msgstr "" + +#: ../intro_os_networking_overview.rst:150 +msgid "" +"The OpenStack networking service is extensible. Extensions serve two " +"purposes: they allow the introduction of new features in the API without " +"requiring a version change and they allow the introduction of vendor " +"specific niche functionality. Applications can programmatically list " +"available extensions by performing a GET on the :code:`/extensions` URI. " +"Note that this is a versioned request; that is, an extension available in " +"one API version might not be available in another." +msgstr "" + +#: ../intro_os_networking_service.rst:3 +msgid "Service and component hierarchy" +msgstr "" + +#: ../intro_os_networking_service.rst:9 ../intro_os_networking_service.rst:17 +#: ../intro_os_networking_service.rst:25 ../intro_os_networking_service.rst:38 +#: ../intro_os_networking_service.rst:42 ../intro_os_networking_service.rst:49 +#: ../intro_os_networking_service.rst:53 ../intro_os_networking_service.rst:60 +msgid "Overview and concepts" +msgstr "" + +#: ../intro_os_networking_service.rst:11 +msgid "Provides API, manages database, etc." +msgstr "" + +#: ../intro_os_networking_service.rst:14 +msgid "Plug-ins" +msgstr "" + +#: ../intro_os_networking_service.rst:19 +msgid "Manages agents" +msgstr "" + +#: ../intro_os_networking_service.rst:27 +msgid "Provides layer 2/3 connectivity to instances" +msgstr "" + +#: ../intro_os_networking_service.rst:29 +msgid "Handles physical-virtual network transition" +msgstr "" + +#: ../intro_os_networking_service.rst:31 +msgid "Handles metadata, etc." +msgstr "" + +#: ../intro_os_networking_service.rst:34 +msgid "Layer 2 (Ethernet and Switching)" +msgstr "" + +#: ../intro_os_networking_service.rst:36 +msgid "Linux Bridge" +msgstr "" + +#: ../intro_os_networking_service.rst:40 +msgid "OVS" +msgstr "" + +#: ../intro_os_networking_service.rst:45 +msgid "Layer 3 (IP and Routing)" +msgstr "" + +# #-#-#-#-# intro_os_networking_service.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# miscellaneous.pot (Networking Guide 0.9) #-#-#-#-# +#: ../intro_os_networking_service.rst:56 ../miscellaneous.rst:3 +msgid "Miscellaneous" +msgstr "" + +#: ../intro_os_networking_service.rst:63 +msgid "Services" +msgstr "" + +#: ../intro_os_networking_service.rst:66 +msgid "Routing services" +msgstr "" + +#: ../intro_os_networking_service.rst:71 +msgid "" +"The Virtual Private Network as a Service (VPNaaS) is a neutron extension " +"that introduces the VPN feature set." +msgstr "" + +#: ../intro_os_networking_service.rst:75 +msgid "LbaaS" +msgstr "" + +#: ../intro_os_networking_service.rst:77 +msgid "" +"The Load-Balancer-as-a-Service (LBaaS) API provisions and configures load " +"balancers. The reference implementation is based on the HAProxy software " +"load balancer." +msgstr "" + +#: ../intro_os_networking_service.rst:82 +msgid "FwaaS" +msgstr "" + +#: ../intro_os_networking_service.rst:84 +msgid "" +"The Firewall-as-a-Service (FWaaS) API is an experimental API that enables " +"early adopters and vendors to test their networking implementations." +msgstr "" + +#: ../intro_tunnel_technologies.rst:3 +msgid "Tunnel technologies" +msgstr "" + +#: ../intro_tunnel_technologies.rst:5 +msgid "" +"Tunneling allows one network protocol to encapsulate another payload " +"protocol such that packets from the payload protocol are passed as data on " +"the delivery protocol. For example, this can be used to pass data securely " +"over an untrusted network." +msgstr "" + +#: ../intro_tunnel_technologies.rst:11 +msgid "Generic routing encapsulation (GRE)" +msgstr "" + +#: ../intro_tunnel_technologies.rst:13 +msgid "" +"GRE carries IP packets with private IP addresses over the Internet using " +"delivery packets with public IP addresses." +msgstr "" + +#: ../intro_tunnel_technologies.rst:19 +msgid "Virtual extensible local area network (VXLAN)" +msgstr "" + +#: ../intro_tunnel_technologies.rst:21 +msgid "" +"A VXLAN, virtual extensible local area network, allows the creation of a " +"logical network for virtual machines across various networks. VXLAN " +"encapsulates layer-2 Ethernet frames over layer-4 UDP packets." +msgstr "" + +#: ../migration.rst:3 +msgid "Migration" +msgstr "" + +#: ../migration_legacy_to_L3_HA.rst:3 +msgid "Legacy to L3 HA" +msgstr "" + +#: ../migration_legacy_to_dvr.rst:3 +msgid "Legacy to DVR" +msgstr "" + +#: ../migration_nova_network_to_neutron.rst:3 +msgid "Migrate legacy nova-network to OpenStack Networking (neutron)" +msgstr "" + +#: ../migration_nova_network_to_neutron.rst:5 +msgid "" +"Two networking models exist in OpenStack. The first is called legacy " +"networking (nova-network) and it is a sub-process embedded in the Compute " +"project (nova). This model has some limitations, such as creating complex " +"network topologies, extending its back-end implementation to vendor-specific " +"technologies, and providing tenant-specific networking elements. These " +"limitations are the main reasons the OpenStack Networking (neutron) model " +"was created." +msgstr "" + +#: ../migration_nova_network_to_neutron.rst:13 +msgid "" +"This section describes the process of migrating clouds based on the legacy " +"networking model to the OpenStack Networking model. This process requires " +"additional changes to both compute and networking to support the migration. " +"This document describes the overall process and the features required in " +"both Networking and Compute." +msgstr "" + +#: ../migration_nova_network_to_neutron.rst:19 +msgid "" +"The current process as designed is a minimally viable migration with the " +"goal of deprecating and then removing legacy networking. Both the Compute " +"and Networking teams agree that a \"one-button\" migration process from " +"legacy networking to OpenStack Networking (neutron) is not an essential " +"requirement for the deprecation and removal of the legacy networking at a " +"future date. This section includes a process and tools which are designed to " +"solve a simple use case migration." +msgstr "" + +#: ../migration_nova_network_to_neutron.rst:27 +msgid "" +"Users are encouraged to take these tools, test them, provide feedback, and " +"then expand on the feature set to suit their own deployments; deployers that " +"refrain from participating in this process intending to wait for a path that " +"better suits their use case are likely to be disappointed." +msgstr "" + +#: ../migration_nova_network_to_neutron.rst:34 +msgid "Impact and limitations" +msgstr "" + +#: ../migration_nova_network_to_neutron.rst:36 +msgid "" +"The migration process from the legacy nova-network networking service to " +"OpenStack Networking (neutron) has some limitations and impacts on the " +"operational state of the cloud. It is critical to understand them in order " +"to decide whether or not this process is acceptable for your cloud and all " +"users." +msgstr "" + +#: ../migration_nova_network_to_neutron.rst:43 +msgid "Management impact" +msgstr "" + +#: ../migration_nova_network_to_neutron.rst:45 +msgid "" +"The Networking REST API is publicly read-only until after the migration is " +"complete. During the migration, Networking REST API is read-write only to " +"nova-api, and changes to Networking are only allowed via nova-api." +msgstr "" + +#: ../migration_nova_network_to_neutron.rst:50 +msgid "" +"The Compute REST API is available throughout the entire process, although " +"there is a brief period where it is made read-only during a database " +"migration. The Networking REST API will need to expose (to nova-api) all " +"details necessary for reconstructing the information previously held in the " +"legacy networking database." +msgstr "" + +#: ../migration_nova_network_to_neutron.rst:56 +msgid "" +"Compute needs a per-hypervisor \"has_transitioned\" boolean change in the " +"data model to be used during the migration process. This flag is no longer " +"required once the process is complete." +msgstr "" + +#: ../migration_nova_network_to_neutron.rst:61 +msgid "Operations impact" +msgstr "" + +#: ../migration_nova_network_to_neutron.rst:63 +msgid "" +"In order to support a wide range of deployment options, the migration " +"process described here requires a rolling restart of hypervisors. The rate " +"and timing of specific hypervisor restarts is under the control of the " +"operator." +msgstr "" + +#: ../migration_nova_network_to_neutron.rst:68 +msgid "" +"The migration may be paused, even for an extended period of time (for " +"example, while testing or investigating issues) with some hypervisors on " +"legacy networking and some on Networking, and Compute API remains fully " +"functional. Individual hypervisors may be rolled back to legacy networking " +"during this stage of the migration, although this requires an additional " +"restart." +msgstr "" + +#: ../migration_nova_network_to_neutron.rst:75 +msgid "" +"In order to support the widest range of deployer needs, the process " +"described here is easy to automate but is not already automated. Deployers " +"should expect to perform multiple manual steps or write some simple scripts " +"in order to perform this migration." +msgstr "" + +#: ../migration_nova_network_to_neutron.rst:81 +msgid "Performance impact" +msgstr "" + +#: ../migration_nova_network_to_neutron.rst:83 +msgid "" +"During the migration, nova-network API calls will go through an additional " +"internal conversion to Networking calls. This will have different and likely " +"poorer performance characteristics compared with either the pre-migration or " +"post-migration APIs." +msgstr "" + +#: ../migration_nova_network_to_neutron.rst:89 +msgid "Migration process overview" +msgstr "" + +#: ../migration_nova_network_to_neutron.rst:91 +msgid "" +"Start neutron-server in intended final config, except with REST API " +"restricted to read-write only by nova-api." +msgstr "" + +#: ../migration_nova_network_to_neutron.rst:93 +msgid "Make the Compute REST API read-only." +msgstr "" + +#: ../migration_nova_network_to_neutron.rst:94 +msgid "" +"Run a DB dump/restore tool that creates Networking data structures " +"representing current legacy networking config." +msgstr "" + +#: ../migration_nova_network_to_neutron.rst:96 +msgid "" +"Enable a nova-api proxy that recreates internal Compute objects from " +"Networking information (via the Networking REST API)." +msgstr "" + +#: ../migration_nova_network_to_neutron.rst:99 +msgid "" +"Make Compute REST API read-write again. This means legacy networking DB is " +"now unused, new changes are now stored in the Networking DB, and no rollback " +"is possible from here without losing those new changes." +msgstr "" + +#: ../migration_nova_network_to_neutron.rst:105 +msgid "" +"At this moment the Networking DB is the source of truth, but nova-api is the " +"only public read-write API." +msgstr "" + +#: ../migration_nova_network_to_neutron.rst:108 +msgid "" +"Next, you'll need to migrate each hypervisor. To do that, follow these " +"steps:" +msgstr "" + +#: ../migration_nova_network_to_neutron.rst:110 +msgid "" +"Disable the hypervisor. This would be a good time to live migrate or " +"evacuate the compute node, if supported." +msgstr "" + +#: ../migration_nova_network_to_neutron.rst:112 +msgid "Disable nova-compute." +msgstr "" + +#: ../migration_nova_network_to_neutron.rst:113 +msgid "Enable the Networking agent." +msgstr "" + +#: ../migration_nova_network_to_neutron.rst:114 +msgid "" +"Set the \"has_transitioned\" flag in the Compute hypervisor database/config." +msgstr "" + +#: ../migration_nova_network_to_neutron.rst:115 +msgid "" +"Reboot the hypervisor (or run \"smart\" live transition tool if available)." +msgstr "" + +#: ../migration_nova_network_to_neutron.rst:116 +msgid "Re-enable the hypervisor." +msgstr "" + +#: ../migration_nova_network_to_neutron.rst:118 +msgid "" +"At this point, all compute nodes have been migrated, but they are still " +"using the nova-api API and Compute gateways. Finally, enable OpenStack " +"Networking by following these steps:" +msgstr "" + +#: ../migration_nova_network_to_neutron.rst:122 +msgid "" +"Bring up the Networking (l3) nodes. The new routers will have identical MAC" +"+IPs as old Compute gateways so some sort of immediate cutover is possible, " +"except for stateful connections issues such as NAT." +msgstr "" + +#: ../migration_nova_network_to_neutron.rst:126 +msgid "Make the Networking API read-write and disable legacy networking." +msgstr "" + +#: ../migration_nova_network_to_neutron.rst:128 +msgid "Migration Completed!" +msgstr "" + +#: ../misc_add_ha_for_DHCP.rst:3 +msgid "Adding high availability for DHCP" +msgstr "" + +#: ../misc_add_ha_for_DHCP.rst:5 +msgid "FIXME (Simple note, needs to be added.)" +msgstr "" + +#: ../misc_add_ha_for_DHCP.rst:8 +msgid "DHCP agents" +msgstr "" + +#: ../misc_add_ha_for_DHCP.rst:10 +msgid "" +"FIXME: Content needs to be written; see DHCP agents (http://docs.openstack." +"org/admin-guide-cloud/networking_multi-dhcp-agents.html)" +msgstr "" + +#: ../misc_libvirt.rst:3 +msgid "Disabling libvirt networking" +msgstr "" + +#: ../misc_libvirt.rst:5 +msgid "" +"Most OpenStack deployments use the libvirt_ toolkit for interacting with the " +"hypervisor. Specifically, OpenStack Compute uses libvirt for tasks such as " +"booting and terminating virtual machine instances. When OpenStack Compute " +"boots a new instance, libvirt provides OpenStack with the VIF associated " +"with the instance, and OpenStack Compute plugs the VIF into a virtual device " +"provided by OpenStack Network. The libvirt toolkit itself does not provide " +"any networking functionality in OpenStack deployments." +msgstr "" + +#: ../misc_libvirt.rst:15 +msgid "" +"However, libvirt is capable of providing networking services to the virtual " +"machines that it manages. In particular, libvirt can be configured to " +"provide networking functionality akin to a simplified, single-node version " +"of OpenStack. Users can use libvirt to create layer 2 networks that are " +"similar to OpenStack Networking's networks, confined to a single node." +msgstr "" + +#: ../misc_libvirt.rst:22 +msgid "libvirt network implementation" +msgstr "" + +#: ../misc_libvirt.rst:24 +msgid "" +"By default, libvirt's networking functionality is enabled, and libvirt " +"creates a network when the system boots. To implement this network, libvirt " +"leverages some of the same technologies that OpenStack Network does. In " +"particular, libvirt uses:" +msgstr "" + +#: ../misc_libvirt.rst:29 +msgid "Linux bridging for implementing a layer 2 network" +msgstr "" + +#: ../misc_libvirt.rst:30 +msgid "dnsmasq for providing IP addresses to virtual machines using DHCP" +msgstr "" + +#: ../misc_libvirt.rst:31 +msgid "" +"iptables to implement SNAT so instances can connect out to the public " +"internet, and to ensure that virtual machines are permitted to communicate " +"with dnsmasq using DHCP" +msgstr "" + +#: ../misc_libvirt.rst:35 +msgid "" +"By default, libvirt creates a network named *default*. The details of this " +"network may vary by distribution; on Ubuntu this network involves:" msgstr "" #: ../misc_libvirt.rst:38 @@ -7682,119 +4783,3018 @@ msgstr "" msgid "a set of iptables rules" msgstr "" -#: ../intro_basic_networking.rst:164 -msgid "classless inter-domain routing (CIDR)" -msgstr "" - -#: ../adv_config_ipv6.rst:115 ../adv_config_ipv6.rst:129 -#: ../adv_config_ipv6.rst:144 ../adv_config_ipv6.rst:145 -#: ../adv_config_ipv6.rst:158 ../adv_config_ipv6.rst:167 -#: ../adv_config_ipv6.rst:172 ../adv_config_ipv6.rst:183 -msgid "dhcpv6-stateful" -msgstr "" - -#: ../adv_config_ipv6.rst:120 ../adv_config_ipv6.rst:134 -#: ../adv_config_ipv6.rst:150 ../adv_config_ipv6.rst:151 -#: ../adv_config_ipv6.rst:163 ../adv_config_ipv6.rst:173 -#: ../adv_config_ipv6.rst:177 ../adv_config_ipv6.rst:182 -msgid "dhcpv6-stateless" -msgstr "" - -#: ../misc_libvirt.rst:30 -msgid "dnsmasq for providing IP addresses to virtual machines using DHCP" -msgstr "" - -#: ../intro_basic_networking.rst:163 -msgid "dotted quad" -msgstr "" - -#: ../adv_config_sriov.rst:289 +#: ../misc_libvirt.rst:43 msgid "" -"exclude_devices is empty so all the VFs associated with eth3 may be " -"configured by the agent. If you want to exclude specific VFs, add them to " -"the exclude_devices parameter as follows:" +"When libvirt boots a virtual machine, it places the machine's VIF in the " +"bridge ``virbr0`` unless explicitly told not to." msgstr "" -#: ../adv_config_LBaaS.rst:11 +#: ../misc_libvirt.rst:46 msgid "" -"http://docs.openstack.org/admin-guide-cloud/networking_adv-features." -"html#basic-load-balancer-as-a-service-operations" +"On Ubuntu, the iptables ruleset that libvirt creates includes the following " +"rules::" msgstr "" -#: ../adv_config_operational.rst:10 +#: ../misc_libvirt.rst:69 msgid "" -"http://docs.openstack.org/admin-guide-cloud/networking_adv-operational-" -"features.html#logging-settings" +"The following shows the dnsmasq process that libvirt manages as it appears " +"in the output of :command:`ps`::" msgstr "" -#: ../adv_config_LBaaS.rst:9 +#: ../misc_libvirt.rst:75 +msgid "How to disable libvirt networks" +msgstr "" + +#: ../misc_libvirt.rst:77 msgid "" -"http://docs.openstack.org/admin-guide-cloud/networking_config-agents." -"html#configure-load-balancer-as-a-service-lbaas" +"Although OpenStack does not make use of libvirt's networking, this " +"networking will not interfere with OpenStack's behavior, and can be safely " +"left enabled. However, libvirt's networking can be a nuisance when debugging " +"OpenStack networking issues. Because libvirt creates an additional bridge, " +"dnsmasq process, and iptables ruleset, these may distract an operator " +"engaged in network troubleshooting. Unless you need to start up virtual " +"machines using libvirt directly, you can safely disable libvirt's network." msgstr "" -#: ../adv_config_FwaaS.rst:7 +#: ../misc_libvirt.rst:86 +msgid "To view the defined libvirt networks and their state::" +msgstr "" + +#: ../misc_libvirt.rst:93 +msgid "To deactivate the libvirt network named *default*::" +msgstr "" + +#: ../misc_libvirt.rst:97 msgid "" -"http://docs.openstack.org/admin-guide-cloud/networking_introduction." -"html#firewall-as-a-service-fwaas-overview" +"Deactivating the network will remove the ``virbr0`` bridge, terminate the " +"dnsmasq process, and remove the iptables rules." msgstr "" -#: ../adv_config_LBaaS.rst:7 +#: ../misc_libvirt.rst:100 +msgid "To prevent the network from automatically starting on boot::" +msgstr "" + +#: ../misc_libvirt.rst:104 +msgid "To activate the network after it has been deactivated::" +msgstr "" + +#: ../scenario_dvr_ovs.rst:3 +msgid "Scenario: High Availability using Distributed Virtual Routing (DVR)" +msgstr "" + +#: ../scenario_dvr_ovs.rst:5 msgid "" -"http://docs.openstack.org/admin-guide-cloud/networking_introduction." -"html#load-balancer-as-a-service-lbaas-overview" +"This scenario describes the high-availability Distributed Virtual Routing " +"(DVR) implementation of the OpenStack Networking service using the ML2 plug-" +"in and Open vSwitch. The example configuration creates one flat external " +"network and one VXLAN project (tenant) network. However, This configuration " +"also supports VLAN external networks, VLAN project networks, and GRE project " +"networks." msgstr "" -#: ../adv_config_debugging.rst:24 -msgid "iproute2" -msgstr "" - -#: ../adv_config_debugging.rst:26 -msgid "iptables" -msgstr "" - -#: ../misc_libvirt.rst:31 +#: ../scenario_dvr_ovs.rst:12 msgid "" -"iptables to implement SNAT so instances can connect out to the public " -"internet, and to ensure that virtual machines are permitted to communicate " -"with dnsmasq using DHCP" +"The DVR architecture augments the legacy architecture by providing direct " +"connectivity to external networks on compute nodes. For instances with a " +"floating IP address, routing between project and external networks resides " +"completely on the compute nodes to eliminate single point of failure and " +"performance issues with legacy network nodes. Routing also resides " +"completely on the compute nodes for instances with a fixed or floating IP " +"address using project networks on the same distributed virtual router. " +"However, instances with a fixed IP address still rely on the network node " +"for routing and SNAT services between project and external networks." msgstr "" -#: ../adv_config_ipv6.rst:100 -msgid "ipv6 address mode" +#: ../scenario_dvr_ovs.rst:23 +msgid "" +"In the Juno (initial) release, DVR supports VXLAN and GRE project networks. " +"In the Kilo release, DVR adds support for VLAN project networks. All " +"releases support flat and VLAN external networks." msgstr "" -#: ../adv_config_ipv6.rst:99 -msgid "ipv6 ra mode" +# #-#-#-#-# scenario_dvr_ovs.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../scenario_dvr_ovs.rst:30 ../scenario_legacy_lb.rst:65 +#: ../scenario_legacy_ovs.rst:64 +msgid "" +"These prerequisites define the minimal physical infrastructure and immediate " +"OpenStack service dependencies necessary to deploy this scenario. For " +"example, the Networking service immediately depends on the Identity service " +"and the Compute service immediately depends on the Networking service. These " +"dependencies lack services such as the Image service because the Networking " +"service does not immediately depend on it. However, the Compute service " +"depends on the Image service to launch an instance. The example " +"configuration in this scenario assumes basic configuration knowledge of " +"Networking service components." msgstr "" -#: ../adv_config_ipv6.rst:264 ../adv_config_ipv6.rst:304 -msgid "ipv6_address_mode" +# #-#-#-#-# scenario_dvr_ovs.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_l3ha_lb.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_l3ha_ovs.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../scenario_dvr_ovs.rst:43 ../scenario_l3ha_lb.rst:59 +#: ../scenario_l3ha_ovs.rst:58 ../scenario_legacy_lb.rst:78 +#: ../scenario_legacy_ovs.rst:77 +msgid "One controller node with one network interface: management." msgstr "" -#: ../adv_config_ipv6.rst:263 ../adv_config_ipv6.rst:303 -msgid "ipv6_ra_mode" +#: ../scenario_dvr_ovs.rst:44 +msgid "" +"One network node with four network interfaces: management, project tunnel " +"networks, VLAN project networks, and external (typically the Internet). The " +"Open vSwitch bridge ``br-vlan`` must contain a port on the VLAN interface " +"and the Open vSwitch bridge ``br-ex`` must contain a port on the external " +"interface." msgstr "" -#: ../adv_config_ipv6.rst:93 -msgid "ipv6_ra_mode and ipv6_address_mode combinations" +#: ../scenario_dvr_ovs.rst:49 +msgid "" +"At least two compute nodes with four network interfaces: management, project " +"tunnel networks, project VLAN networks, and external (typically the " +"Internet). The Open vSwitch bridge ``br-vlan`` must contain a port on the " +"VLAN interface and the Open vSwitch bridge ``br-ex`` must contain a port on " +"the external interface." msgstr "" -#: ../misc_libvirt.rst:22 -msgid "libvirt network implementation" +#: ../scenario_dvr_ovs.rst:55 +msgid "" +"In the example configuration, the management network uses 10.0.0.0/24, the " +"tunnel network uses 10.0.1.0/24, and the external network uses " +"203.0.113.0/24. The VLAN network does not require an IP address range " +"because it only handles layer 2 connectivity." msgstr "" -#: ../adv_config_ipv6.rst:101 -msgid "radvd A,M,O" +# #-#-#-#-# scenario_dvr_ovs.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_l3ha_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../scenario_dvr_ovs.rst:70 ../scenario_l3ha_ovs.rst:89 +msgid "" +"For VLAN external and project networks, the network infrastructure must " +"support VLAN tagging. For best performance with VXLAN and GRE project " +"networks, the network infrastructure should support jumbo frames." msgstr "" -#: ../adv_config_ipv6.rst:110 ../adv_config_ipv6.rst:124 -#: ../adv_config_ipv6.rst:139 ../adv_config_ipv6.rst:140 -#: ../adv_config_ipv6.rst:157 ../adv_config_ipv6.rst:162 -#: ../adv_config_ipv6.rst:168 ../adv_config_ipv6.rst:178 -msgid "slaac" +#: ../scenario_dvr_ovs.rst:75 +msgid "" +"Proper operation of this scenario requires Open vSwitch 2.1 or newer. VXLAN " +"requires kernel 3.13 or newer. Also, the Kilo release increases stability " +"and reliability of DVR considerably over the Juno release." msgstr "" -#: ../adv_config_debugging.rst:25 -msgid "tcpdump" +# #-#-#-#-# scenario_dvr_ovs.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_l3ha_lb.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_l3ha_ovs.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../scenario_dvr_ovs.rst:90 ../scenario_l3ha_lb.rst:104 +#: ../scenario_l3ha_ovs.rst:109 ../scenario_legacy_lb.rst:122 +#: ../scenario_legacy_ovs.rst:128 +msgid "Neutron server service, ML2 plug-in, and any dependencies." +msgstr "" + +# #-#-#-#-# scenario_dvr_ovs.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_l3ha_lb.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../scenario_dvr_ovs.rst:93 ../scenario_l3ha_lb.rst:107 +#: ../scenario_legacy_lb.rst:125 ../scenario_legacy_ovs.rst:131 +msgid "OpenStack services - network node" +msgstr "" + +# #-#-#-#-# scenario_dvr_ovs.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_l3ha_ovs.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../scenario_dvr_ovs.rst:97 ../scenario_l3ha_ovs.rst:116 +#: ../scenario_legacy_ovs.rst:135 +msgid "" +"Open vSwitch service, ML2 plug-in, Open vSwitch agent, L3 agent, DHCP agent, " +"metadata agent, and any dependencies." +msgstr "" + +# #-#-#-#-# scenario_dvr_ovs.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_l3ha_lb.pot (Networking Guide 0.9) #-#-#-#-# +#: ../scenario_dvr_ovs.rst:105 ../scenario_l3ha_lb.rst:119 +msgid "" +"Operational OpenStack Compute hypervisor service with appropriate " +"configuration to use neutron in the :file:`nova.conf` file." +msgstr "" + +#: ../scenario_dvr_ovs.rst:107 +msgid "" +"Open vSwitch service, ML2 plug-in, Open vSwitch agent, L3 agent, metadata " +"agent, and any dependencies." +msgstr "" + +#: ../scenario_dvr_ovs.rst:117 +msgid "" +"The term *north-south* generally defines network traffic that travels " +"between an instance and external network (typically the Internet) and the " +"term *east-west* generally defines network traffic that travels between " +"instances." +msgstr "" + +# #-#-#-#-# scenario_dvr_ovs.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../scenario_dvr_ovs.rst:122 ../scenario_legacy_lb.rst:156 +#: ../scenario_legacy_ovs.rst:162 +msgid "The network node contains the following network components:" +msgstr "" + +# #-#-#-#-# scenario_dvr_ovs.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_l3ha_ovs.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../scenario_dvr_ovs.rst:124 ../scenario_dvr_ovs.rst:150 +#: ../scenario_l3ha_ovs.rst:138 ../scenario_l3ha_ovs.rst:157 +#: ../scenario_legacy_ovs.rst:164 ../scenario_legacy_ovs.rst:183 +msgid "" +"Open vSwitch agent managing virtual switches, connectivity among them, and " +"interaction via virtual ports with other network components such as " +"namespaces, Linux bridges, and underlying interfaces." +msgstr "" + +#: ../scenario_dvr_ovs.rst:127 +msgid "" +"DHCP agent managing the ``qdhcp`` namespaces. The ``dhcp`` namespaces " +"provide DHCP services for instances using project networks." +msgstr "" + +#: ../scenario_dvr_ovs.rst:129 +msgid "L3 agent managing the ``qrouter`` and ``snat`` namespaces." +msgstr "" + +#: ../scenario_dvr_ovs.rst:131 +msgid "" +"For instances using project networks on legacy routers, the ``qrouter`` " +"namespaces route *north-south* and *east-west* network traffic and perform " +"DNAT/SNAT similar to the legacy scenarios. They also route metadata traffic " +"between instances and the metadata agent." +msgstr "" + +#: ../scenario_dvr_ovs.rst:135 +msgid "" +"For instances with a fixed IP address using project networks on distributed " +"routers, the ``snat`` namespaces perform SNAT for *north-south* network " +"traffic." +msgstr "" + +#: ../scenario_dvr_ovs.rst:139 +msgid "" +"Metadata agent handling metadata operations for instances using project " +"networks on legacy routers." +msgstr "" + +#: ../scenario_dvr_ovs.rst:154 +msgid "L3 agent managing the ``qrouter`` and ``fip`` namespaces." +msgstr "" + +#: ../scenario_dvr_ovs.rst:156 +msgid "" +"For instances with a floating IP address using project networks on " +"distributed routers, the ``fip`` namespaces route *north-south* network " +"traffic and perform DNAT/SNAT." +msgstr "" + +#: ../scenario_dvr_ovs.rst:159 +msgid "" +"For instances with a fixed or floating IP address using project networks on " +"distributed routers, the ``qrouter`` namespaces route *east-west* traffic." +msgstr "" + +#: ../scenario_dvr_ovs.rst:163 +msgid "" +"Metadata agent handling metadata operations for instances using project " +"networks on distributed routers." +msgstr "" + +# #-#-#-#-# scenario_dvr_ovs.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_l3ha_ovs.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../scenario_dvr_ovs.rst:165 ../scenario_l3ha_ovs.rst:160 +#: ../scenario_provider_ovs.rst:134 +msgid "Linux bridges handling security groups." +msgstr "" + +# #-#-#-#-# scenario_dvr_ovs.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_l3ha_ovs.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../scenario_dvr_ovs.rst:168 ../scenario_l3ha_ovs.rst:163 +#: ../scenario_provider_ovs.rst:137 +msgid "" +"Due to limitations with Open vSwitch and *iptables*, the Networking service " +"uses a Linux bridge to manage security groups for instances." +msgstr "" + +#: ../scenario_dvr_ovs.rst:182 +msgid "Case 1: North/south for instances with a fixed IP address" +msgstr "" + +#: ../scenario_dvr_ovs.rst:184 +msgid "" +"For instances with a fixed IP address using project networks on distributed " +"routers, the network node routes *north-south* network traffic between " +"project and external networks." +msgstr "" + +#: ../scenario_dvr_ovs.rst:191 ../scenario_dvr_ovs.rst:278 +msgid "Gateway 203.0.113.1 with MAC address *EG*" +msgstr "" + +#: ../scenario_dvr_ovs.rst:192 ../scenario_dvr_ovs.rst:279 +msgid "Floating IP range 203.0.113.101 to 203.0.113.200" +msgstr "" + +# #-#-#-#-# scenario_dvr_ovs.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../scenario_dvr_ovs.rst:193 ../scenario_dvr_ovs.rst:280 +#: ../scenario_legacy_lb.rst:205 ../scenario_legacy_lb.rst:301 +#: ../scenario_legacy_ovs.rst:214 ../scenario_legacy_ovs.rst:306 +msgid "Project network router interface 203.0.113.101 *TR*" +msgstr "" + +#: ../scenario_dvr_ovs.rst:194 +msgid "Project network SNAT interface 192.168.1.2 with MAC address *TN*" +msgstr "" + +# #-#-#-#-# scenario_dvr_ovs.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../scenario_dvr_ovs.rst:196 ../scenario_dvr_ovs.rst:282 +#: ../scenario_legacy_lb.rst:207 ../scenario_legacy_lb.rst:303 +#: ../scenario_legacy_lb.rst:471 ../scenario_legacy_ovs.rst:216 +#: ../scenario_legacy_ovs.rst:308 ../scenario_legacy_ovs.rst:535 +msgid "Project network" +msgstr "" + +# #-#-#-#-# scenario_dvr_ovs.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../scenario_dvr_ovs.rst:198 ../scenario_dvr_ovs.rst:284 +#: ../scenario_dvr_ovs.rst:372 ../scenario_legacy_lb.rst:209 +#: ../scenario_legacy_lb.rst:305 ../scenario_legacy_ovs.rst:218 +#: ../scenario_legacy_ovs.rst:310 +msgid "Network 192.168.1.0/24" +msgstr "" + +# #-#-#-#-# scenario_dvr_ovs.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../scenario_dvr_ovs.rst:199 ../scenario_dvr_ovs.rst:285 +#: ../scenario_legacy_lb.rst:210 ../scenario_legacy_lb.rst:306 +#: ../scenario_legacy_ovs.rst:219 ../scenario_legacy_ovs.rst:311 +msgid "Gateway 192.168.1.1 with MAC address *TG*" +msgstr "" + +# #-#-#-#-# scenario_dvr_ovs.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../scenario_dvr_ovs.rst:203 ../scenario_dvr_ovs.rst:382 +#: ../scenario_legacy_lb.rst:214 ../scenario_legacy_ovs.rst:223 +msgid "Instance 1 192.168.1.11 with MAC address *I1*" +msgstr "" + +#: ../scenario_dvr_ovs.rst:204 ../scenario_dvr_ovs.rst:291 +#: ../scenario_dvr_ovs.rst:383 +msgid "DVR MAC address *D1*" +msgstr "" + +# #-#-#-#-# scenario_dvr_ovs.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../scenario_dvr_ovs.rst:206 ../scenario_dvr_ovs.rst:294 +#: ../scenario_legacy_lb.rst:216 ../scenario_legacy_lb.rst:313 +#: ../scenario_legacy_ovs.rst:225 ../scenario_legacy_ovs.rst:318 +msgid "Instance 1 resides on compute node 1 and uses a project network." +msgstr "" + +#: ../scenario_dvr_ovs.rst:209 ../scenario_dvr_ovs.rst:297 +#: ../scenario_dvr_ovs.rst:395 +msgid "" +"This scenario supports both VLAN and GRE/VXLAN project networks. However, " +"the packet flow only considers one instance using a VXLAN project network " +"for simplicity." +msgstr "" + +# #-#-#-#-# scenario_dvr_ovs.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../scenario_dvr_ovs.rst:215 ../scenario_legacy_ovs.rst:230 +#: ../scenario_provider_ovs.rst:192 +msgid "" +"The instance 1 ``tap`` interface (1) forwards the packet to the Linux bridge " +"``qbr``. The packet contains destination MAC address *TG* because the " +"destination resides on another network." +msgstr "" + +# #-#-#-#-# scenario_dvr_ovs.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../scenario_dvr_ovs.rst:218 ../scenario_dvr_ovs.rst:404 +#: ../scenario_legacy_ovs.rst:233 ../scenario_legacy_ovs.rst:423 +msgid "" +"Security group rules (2) on the Linux bridge ``qbr`` handle state tracking " +"for the packet." +msgstr "" + +# #-#-#-#-# scenario_dvr_ovs.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../scenario_dvr_ovs.rst:220 ../scenario_dvr_ovs.rst:339 +#: ../scenario_dvr_ovs.rst:406 ../scenario_legacy_ovs.rst:235 +#: ../scenario_legacy_ovs.rst:425 ../scenario_legacy_ovs.rst:560 +#: ../scenario_provider_ovs.rst:197 ../scenario_provider_ovs.rst:259 +#: ../scenario_provider_ovs.rst:331 +msgid "" +"The Linux bridge ``qbr`` forwards the packet to the Open vSwitch integration " +"bridge ``br-int``." +msgstr "" + +#: ../scenario_dvr_ovs.rst:222 +msgid "" +"The Open vSwitch integration bridge ``br-int`` modifies the packet to " +"contain the internal tag for project network 1." +msgstr "" + +#: ../scenario_dvr_ovs.rst:224 +msgid "" +"The Open vSwitch integration bridge ``br-int`` forwards the packet (3) to " +"the project network 1 gateway *TG* interface ``qr`` in the distributed " +"router namespace ``qrouter``." +msgstr "" + +#: ../scenario_dvr_ovs.rst:227 +msgid "" +"The distributed router ``qrouter`` namespace resolves the project network 1 " +"SNAT interface MAC address *TN* on the ``sg`` interface (4) in the SNAT " +"namespace ``snat`` and forwards the packet to the Open vSwitch integration " +"bridge ``br-int``." +msgstr "" + +# #-#-#-#-# scenario_dvr_ovs.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../scenario_dvr_ovs.rst:231 ../scenario_dvr_ovs.rst:418 +#: ../scenario_legacy_ovs.rst:250 ../scenario_legacy_ovs.rst:348 +#: ../scenario_legacy_ovs.rst:440 ../scenario_legacy_ovs.rst:488 +#: ../scenario_legacy_ovs.rst:575 +msgid "" +"The Open vSwitch integration bridge ``br-int`` forwards the packet to the " +"Open vSwitch tunnel bridge ``br-tun``." +msgstr "" + +#: ../scenario_dvr_ovs.rst:233 ../scenario_dvr_ovs.rst:420 +msgid "" +"The Open vSwitch tunnel bridge ``br-tun`` replaces the packet source MAC " +"address *I1* with *D1*." +msgstr "" + +#: ../scenario_dvr_ovs.rst:235 +msgid "" +"The Open vSwitch tunnel bridge ``br-tun`` wraps the packet in a VXLAN tunnel " +"that contains a tag for project network 1." +msgstr "" + +# #-#-#-#-# scenario_dvr_ovs.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../scenario_dvr_ovs.rst:237 ../scenario_legacy_ovs.rst:254 +#: ../scenario_legacy_ovs.rst:444 +msgid "" +"The Open vSwitch tunnel bridge ``br-tun`` forwards the packet to the network " +"node via the tunnel interface." +msgstr "" + +# #-#-#-#-# scenario_dvr_ovs.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../scenario_dvr_ovs.rst:240 ../scenario_legacy_lb.rst:252 +#: ../scenario_legacy_lb.rst:320 ../scenario_legacy_lb.rst:425 +#: ../scenario_legacy_ovs.rst:257 ../scenario_legacy_ovs.rst:321 +#: ../scenario_legacy_ovs.rst:447 +msgid "The following steps involve the network node:" +msgstr "" + +# #-#-#-#-# scenario_dvr_ovs.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../scenario_dvr_ovs.rst:242 ../scenario_dvr_ovs.rst:429 +#: ../scenario_legacy_ovs.rst:270 ../scenario_legacy_ovs.rst:368 +#: ../scenario_legacy_ovs.rst:460 ../scenario_legacy_ovs.rst:508 +#: ../scenario_legacy_ovs.rst:595 +msgid "" +"The tunnel interface forwards the packet to the Open vSwitch tunnel bridge " +"``br-tun``." +msgstr "" + +# #-#-#-#-# scenario_dvr_ovs.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../scenario_dvr_ovs.rst:244 ../scenario_legacy_ovs.rst:462 +msgid "" +"The Open vSwitch tunnel bridge ``br-tun`` unwraps the packet and adds the " +"internal tag for project network 1." +msgstr "" + +# #-#-#-#-# scenario_dvr_ovs.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../scenario_dvr_ovs.rst:246 ../scenario_dvr_ovs.rst:432 +#: ../scenario_legacy_ovs.rst:274 ../scenario_legacy_ovs.rst:372 +#: ../scenario_legacy_ovs.rst:464 ../scenario_legacy_ovs.rst:512 +#: ../scenario_legacy_ovs.rst:599 +msgid "" +"The Open vSwitch tunnel bridge ``br-tun`` forwards the packet to the Open " +"vSwitch integration bridge ``br-int``." +msgstr "" + +#: ../scenario_dvr_ovs.rst:248 +msgid "" +"The Open vSwitch integration bridge ``br-int`` replaces the packet source " +"MAC address *D1* with *TG*." +msgstr "" + +#: ../scenario_dvr_ovs.rst:250 +msgid "" +"The Open vSwitch integration bridge ``br-int`` forwards the packet to the " +"``sg`` interface (4) in the SNAT namespace ``snat``." +msgstr "" + +#: ../scenario_dvr_ovs.rst:252 +msgid "" +"The *iptables* service (5) performs SNAT on the packet using the project " +"network 1 router interface IP address *TR* on the ``qg`` interface (6)." +msgstr "" + +#: ../scenario_dvr_ovs.rst:254 +msgid "" +"The ``qg`` interface forwards the packet to the Open vSwitch external bridge " +"``br-ex``." +msgstr "" + +# #-#-#-#-# scenario_dvr_ovs.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../scenario_dvr_ovs.rst:256 ../scenario_dvr_ovs.rst:356 +#: ../scenario_legacy_ovs.rst:287 +msgid "" +"The Open vSwitch external bridge ``br-ex`` forwards the packet to the " +"external network via the external interface." +msgstr "" + +#: ../scenario_dvr_ovs.rst:266 +msgid "Case 2: North/south for instances with a floating IP address" +msgstr "" + +#: ../scenario_dvr_ovs.rst:268 +msgid "" +"For instances with a floating IP address using project networks on " +"distributed routers, the compute node containing the instance routes *north-" +"south* network traffic between project and external networks, avoiding the " +"network node. Given the complexity of this case, the following case covers " +"both the flow of network traffic from the external network to an instance " +"and from an instance to the external network." +msgstr "" + +#: ../scenario_dvr_ovs.rst:287 +msgid "Compute node" +msgstr "" + +# #-#-#-#-# scenario_dvr_ovs.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../scenario_dvr_ovs.rst:289 ../scenario_legacy_lb.rst:310 +#: ../scenario_legacy_ovs.rst:315 +msgid "" +"Instance 1 192.168.1.11 with MAC address *I1* and floating IP address " +"203.0.113.102 *F1*" +msgstr "" + +#: ../scenario_dvr_ovs.rst:292 +msgid "DVR internal IP addresses *DA1* and *DA2*" +msgstr "" + +#: ../scenario_dvr_ovs.rst:295 +msgid "Instance 1 sends a packet to a host on the external network." +msgstr "" + +#: ../scenario_dvr_ovs.rst:301 +msgid "" +"The following steps involve a packet inbound from the external network to an " +"instance on compute node 1:" +msgstr "" + +#: ../scenario_dvr_ovs.rst:304 +msgid "" +"The external interface forwards the packet to the Open vSwitch external " +"bridge ``br-ex``. The packet contains destination IP address *F1*." +msgstr "" + +#: ../scenario_dvr_ovs.rst:307 +msgid "" +"The Open vSwitch external bridge ``br-ex`` forwards the packet to the ``fg`` " +"interface (1) in the floating IP namespace ``fip``. The ``fg`` interface " +"responds to any ARP requests for the instance floating IP address *F1*." +msgstr "" + +#: ../scenario_dvr_ovs.rst:311 +msgid "" +"The floating IP namespace ``fip`` routes the packet (2) to the distributed " +"router namespace ``qrouter`` using DVR internal IP addresses *DA1* and " +"*DA2*. The ``fpr`` interface (3) contains DVR internal IP address *DA1* and " +"the ``rfp`` interface (4) contains DVR internal IP address *DA2*." +msgstr "" + +#: ../scenario_dvr_ovs.rst:316 +msgid "" +"The floating IP namespace ``fip`` forwards the packet to the ``rfp`` " +"interface (5) in the distributed router namespace ``qrouter``. The ``rfp`` " +"interface also contains the instance floating IP address *F1*." +msgstr "" + +#: ../scenario_dvr_ovs.rst:319 +msgid "" +"The *iptables* service (6) in the distributed router namespace ``qrouter`` " +"performs DNAT on the packet using the destination IP address. The ``qr`` " +"interface (7) contains the project network gateway IP address *TG*." +msgstr "" + +#: ../scenario_dvr_ovs.rst:322 +msgid "" +"The distributed router namespace ``qrouter`` forwards the packet to the Open " +"vSwitch integration bridge ``br-int``." +msgstr "" + +# #-#-#-#-# scenario_dvr_ovs.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../scenario_dvr_ovs.rst:324 ../scenario_dvr_ovs.rst:436 +#: ../scenario_legacy_ovs.rst:375 ../scenario_legacy_ovs.rst:515 +#: ../scenario_legacy_ovs.rst:602 ../scenario_provider_ovs.rst:288 +#: ../scenario_provider_ovs.rst:354 +msgid "" +"The Open vSwitch integration bridge ``br-int`` forwards the packet to the " +"Linux bridge ``qbr``." +msgstr "" + +#: ../scenario_dvr_ovs.rst:326 +msgid "" +"Security group rules (8) on the Linux bridge ``qbr`` handle firewalling and " +"state tracking for the packet." +msgstr "" + +#: ../scenario_dvr_ovs.rst:328 +msgid "" +"The Linux bridge ``qbr`` forwards the packet to the instance ``tap`` " +"interface (9)." +msgstr "" + +#: ../scenario_dvr_ovs.rst:331 +msgid "" +"The following steps involve a packet outbound from an instance on compute " +"node 1 to the external network:" +msgstr "" + +#: ../scenario_dvr_ovs.rst:334 +msgid "" +"The instance 1 ``tap`` interface (9) forwards the packet to the Linux bridge " +"``qbr``. The packet contains destination MAC address *TG1* because the " +"destination resides on another network." +msgstr "" + +#: ../scenario_dvr_ovs.rst:337 +msgid "" +"Security group rules (8) on the Linux bridge ``qbr`` handle state tracking " +"for the packet." +msgstr "" + +#: ../scenario_dvr_ovs.rst:341 +msgid "" +"The Open vSwitch integration bridge ``br-int`` forwards the packet to the " +"``qr`` interface (7) in the distributed router namespace ``qrouter``. The " +"``qr`` interface contains the project network gateway IP address *TG*." +msgstr "" + +#: ../scenario_dvr_ovs.rst:345 +msgid "" +"The *iptables* service (6) performs SNAT on the packet using the ``rfp`` " +"interface (5) as the source IP address. The ``rfp`` interface contains the " +"instance floating IP address *F1*." +msgstr "" + +#: ../scenario_dvr_ovs.rst:348 +msgid "" +"The distributed router namespace ``qrouter`` (2) routes the packet to the " +"floating IP namespace ``fip`` using DVR internal IP addresses *DA1* and " +"*DA2*. The ``rfp`` interface (4) contains DVR internal IP address *DA2* and " +"the ``fpr`` interface (3) contains DVR internal IP address *DA1*." +msgstr "" + +#: ../scenario_dvr_ovs.rst:353 +msgid "" +"The ``fg`` interface (1) in the floating IP namespace ``fip`` forwards the " +"packet to the Open vSwitch external bridge ``br-ex``. The ``fg`` interface " +"contains the project router external IP address *TE*." +msgstr "" + +#: ../scenario_dvr_ovs.rst:363 +msgid "" +"Case 3: East/west for instances using different networks on the same router" +msgstr "" + +#: ../scenario_dvr_ovs.rst:365 +msgid "" +"For instances with fixed or floating IP addresses using project networks on " +"distributed routers, the compute nodes route *east-west* network traffic " +"among the project networks that reside on the same distributed virtual " +"router, avoiding the network node." +msgstr "" + +# #-#-#-#-# scenario_dvr_ovs.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../scenario_dvr_ovs.rst:370 ../scenario_legacy_lb.rst:389 +#: ../scenario_legacy_ovs.rst:395 +msgid "Project network 1" +msgstr "" + +#: ../scenario_dvr_ovs.rst:373 +msgid "Gateway 192.168.1.1 with MAC address *TG1*" +msgstr "" + +# #-#-#-#-# scenario_dvr_ovs.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../scenario_dvr_ovs.rst:375 ../scenario_legacy_lb.rst:394 +#: ../scenario_legacy_ovs.rst:400 +msgid "Project network 2" +msgstr "" + +#: ../scenario_dvr_ovs.rst:377 +msgid "Network 192.168.2.0/24" +msgstr "" + +#: ../scenario_dvr_ovs.rst:378 +msgid "Gateway 192.168.2.1 with MAC address *TG2*" +msgstr "" + +#: ../scenario_dvr_ovs.rst:387 +msgid "Instance 2 192.168.2.11 with MAC address *I2*" +msgstr "" + +#: ../scenario_dvr_ovs.rst:388 +msgid "DVR MAC address *D2*" +msgstr "" + +# #-#-#-#-# scenario_dvr_ovs.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../scenario_dvr_ovs.rst:390 ../scenario_legacy_ovs.rst:413 +msgid "Instance 1 resides on compute node 1 and uses project network 1." +msgstr "" + +# #-#-#-#-# scenario_dvr_ovs.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../scenario_dvr_ovs.rst:391 ../scenario_legacy_ovs.rst:414 +msgid "Instance 2 resides on compute node 2 and uses project network 2." +msgstr "" + +#: ../scenario_dvr_ovs.rst:392 +msgid "Both project networks reside on the same distributed virtual router." +msgstr "" + +# #-#-#-#-# scenario_dvr_ovs.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../scenario_dvr_ovs.rst:401 ../scenario_legacy_ovs.rst:420 +#: ../scenario_provider_ovs.rst:254 +msgid "" +"The instance 1 ``tap`` interface (1) forwards the packet to the Linux bridge " +"``qbr``. The packet contains destination MAC address *TG1* because the " +"destination resides on another network." +msgstr "" + +#: ../scenario_dvr_ovs.rst:408 +msgid "" +"The Open vSwitch integration bridge ``br-int`` forwards the packet to the " +"project network 1 interface (3) in the distributed router namespace " +"``qrouter``." +msgstr "" + +#: ../scenario_dvr_ovs.rst:411 +msgid "" +"The distributed router namespace ``qrouter`` routes the packet to project " +"network 2." +msgstr "" + +#: ../scenario_dvr_ovs.rst:413 +msgid "" +"The project network 2 interface (4) in the distributed router namespace " +"``qrouter`` namespace forwards the packet to the Open vSwitch integration " +"bridge ``br-int``." +msgstr "" + +#: ../scenario_dvr_ovs.rst:416 +msgid "" +"The Open vSwitch integration bridge ``br-int`` modifies the packet to " +"contain the internal tag for project network 2." +msgstr "" + +#: ../scenario_dvr_ovs.rst:422 +msgid "" +"The Open vSwitch tunnel bridge ``br-tun`` wraps the packet in a VXLAN tunnel " +"that contains a tag for project network 2." +msgstr "" + +# #-#-#-#-# scenario_dvr_ovs.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../scenario_dvr_ovs.rst:424 ../scenario_legacy_ovs.rst:492 +msgid "" +"The Open vSwitch tunnel bridge ``br-tun`` forwards the packet to compute " +"node 2 via the tunnel interface." +msgstr "" + +#: ../scenario_dvr_ovs.rst:431 +msgid "The Open vSwitch tunnel bridge ``br-tun`` unwraps the packet." +msgstr "" + +#: ../scenario_dvr_ovs.rst:434 +msgid "" +"The Open vSwitch integration bridge ``br-int`` replaces the packet source " +"MAC address *D1* with *TG2*." +msgstr "" + +#: ../scenario_dvr_ovs.rst:438 +msgid "" +"Security group rules (7) on the Linux bridge ``qbr`` handle firewalling and " +"state tracking for the packet." +msgstr "" + +#: ../scenario_dvr_ovs.rst:440 +msgid "" +"The Linux bridge ``qbr`` forwards the packet to the instance 2 ``tap`` " +"interface (8)." +msgstr "" + +#: ../scenario_dvr_ovs.rst:444 +msgid "" +"Packets arriving from compute node 1 do not traverse the project network " +"interfaces (5,6) in the ``qrouter`` namespace on compute node 2. However, " +"return traffic traverses them." +msgstr "" + +#: ../scenario_dvr_ovs.rst:463 +msgid "This configuration primarily supports the Kilo release." +msgstr "" + +#: ../scenario_dvr_ovs.rst:480 +msgid "" +"Configuring the ``router_distributed = True`` option creates distributed " +"routers by default for all users. Without it, only privileged users can " +"create distributed routers using the ``--distributed True`` option during " +"router creation." +msgstr "" + +# #-#-#-#-# scenario_dvr_ovs.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_l3ha_lb.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_l3ha_ovs.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../scenario_dvr_ovs.rst:485 ../scenario_l3ha_lb.rst:215 +#: ../scenario_l3ha_ovs.rst:224 ../scenario_legacy_lb.rst:539 +#: ../scenario_legacy_ovs.rst:634 +msgid "" +"Configure the ML2 plug-in. Edit the :file:`/etc/neutron/plugins/ml2/ml2_conf." +"ini` file:" +msgstr "" + +# #-#-#-#-# scenario_dvr_ovs.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_l3ha_ovs.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../scenario_dvr_ovs.rst:513 ../scenario_l3ha_ovs.rst:252 +#: ../scenario_legacy_ovs.rst:662 +msgid "" +"Replace ``MIN_VLAN_ID``, ``MAX_VLAN_ID``, ``MIN_GRE_ID``, ``MAX_GRE_ID``, " +"``MIN_VXLAN_ID``, and ``MAX_VXLAN_ID`` with VLAN, GRE, and VXLAN ID minimum " +"and maximum values suitable for your environment." +msgstr "" + +#: ../scenario_dvr_ovs.rst:518 +msgid "" +"The first value in the ``tenant_network_types`` option becomes the default " +"project network type when a non-privileged user creates a network." +msgstr "" + +#: ../scenario_dvr_ovs.rst:523 +msgid "" +"The ``external`` value in the ``network_vlan_ranges`` option lacks VLAN ID " +"ranges to support use of arbitrary VLAN IDs by privileged users." +msgstr "" + +# #-#-#-#-# scenario_dvr_ovs.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../scenario_dvr_ovs.rst:531 ../scenario_legacy_lb.rst:581 +#: ../scenario_legacy_ovs.rst:679 +msgid "Network node" +msgstr "" + +# #-#-#-#-# scenario_dvr_ovs.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_l3ha_lb.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_l3ha_ovs.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../scenario_dvr_ovs.rst:533 ../scenario_l3ha_lb.rst:259 +#: ../scenario_l3ha_ovs.rst:271 ../scenario_legacy_lb.rst:583 +#: ../scenario_legacy_ovs.rst:681 +msgid "" +"Configure the kernel to enable packet forwarding and disable reverse path " +"filtering. Edit the :file:`/etc/sysctl.conf` file:" +msgstr "" + +# #-#-#-#-# scenario_dvr_ovs.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_l3ha_ovs.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../scenario_dvr_ovs.rst:555 ../scenario_dvr_ovs.rst:669 +#: ../scenario_l3ha_ovs.rst:293 ../scenario_l3ha_ovs.rst:403 +#: ../scenario_legacy_ovs.rst:703 ../scenario_legacy_ovs.rst:813 +#: ../scenario_provider_ovs.rst:502 +msgid "" +"Configure the Open vSwitch agent. Edit the :file:`/etc/neutron/plugins/ml2/" +"ml2_conf.ini` file:" +msgstr "" + +# #-#-#-#-# scenario_dvr_ovs.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_l3ha_ovs.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../scenario_dvr_ovs.rst:575 ../scenario_dvr_ovs.rst:689 +#: ../scenario_l3ha_ovs.rst:311 ../scenario_l3ha_ovs.rst:421 +#: ../scenario_legacy_ovs.rst:722 ../scenario_legacy_ovs.rst:832 +msgid "" +"Replace ``TUNNEL_INTERFACE_IP_ADDRESS`` with the IP address of the interface " +"that handles GRE/VXLAN project networks." +msgstr "" + +# #-#-#-#-# scenario_dvr_ovs.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_l3ha_lb.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_l3ha_ovs.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../scenario_dvr_ovs.rst:578 ../scenario_dvr_ovs.rst:692 +#: ../scenario_l3ha_lb.rst:304 ../scenario_l3ha_ovs.rst:314 +#: ../scenario_legacy_lb.rst:628 ../scenario_legacy_ovs.rst:725 +msgid "" +"Configure the L3 agent. Edit the :file:`/etc/neutron/l3_agent.ini` file:" +msgstr "" + +# #-#-#-#-# scenario_dvr_ovs.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_l3ha_lb.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_l3ha_ovs.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../scenario_dvr_ovs.rst:591 ../scenario_dvr_ovs.rst:705 +#: ../scenario_l3ha_lb.rst:317 ../scenario_l3ha_ovs.rst:327 +#: ../scenario_legacy_ovs.rst:737 +msgid "The ``external_network_bridge`` option intentionally contains no value." +msgstr "" + +#: ../scenario_dvr_ovs.rst:606 +msgid "(Optional) Reduce MTU for GRE/VXLAN project networks." +msgstr "" + +# #-#-#-#-# scenario_dvr_ovs.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_l3ha_lb.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_l3ha_ovs.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../scenario_dvr_ovs.rst:608 ../scenario_l3ha_lb.rst:334 +#: ../scenario_l3ha_ovs.rst:344 ../scenario_legacy_lb.rst:653 +#: ../scenario_legacy_ovs.rst:754 +msgid "Edit the :file:`/etc/neutron/dhcp_agent.ini` file:" +msgstr "" + +# #-#-#-#-# scenario_dvr_ovs.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_l3ha_lb.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_l3ha_ovs.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../scenario_dvr_ovs.rst:615 ../scenario_l3ha_lb.rst:341 +#: ../scenario_l3ha_ovs.rst:351 ../scenario_legacy_lb.rst:660 +#: ../scenario_legacy_ovs.rst:761 +msgid "Edit the :file:`/etc/neutron/dnsmasq-neutron.conf` file:" +msgstr "" + +# #-#-#-#-# scenario_dvr_ovs.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_l3ha_lb.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_l3ha_ovs.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../scenario_dvr_ovs.rst:621 ../scenario_dvr_ovs.rst:708 +#: ../scenario_l3ha_lb.rst:347 ../scenario_l3ha_ovs.rst:357 +#: ../scenario_legacy_lb.rst:666 ../scenario_legacy_ovs.rst:767 +msgid "" +"Configure the metadata agent. Edit the :file:`/etc/neutron/metadata_agent." +"ini` file:" +msgstr "" + +# #-#-#-#-# scenario_dvr_ovs.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_l3ha_lb.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_l3ha_ovs.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../scenario_dvr_ovs.rst:631 ../scenario_dvr_ovs.rst:718 +#: ../scenario_l3ha_lb.rst:357 ../scenario_l3ha_ovs.rst:367 +#: ../scenario_legacy_lb.rst:676 ../scenario_legacy_ovs.rst:777 +msgid "Replace ``METADATA_SECRET`` with a suitable value for your environment." +msgstr "" + +# #-#-#-#-# scenario_dvr_ovs.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_l3ha_ovs.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../scenario_dvr_ovs.rst:636 ../scenario_dvr_ovs.rst:723 +#: ../scenario_l3ha_ovs.rst:372 ../scenario_l3ha_ovs.rst:427 +#: ../scenario_legacy_ovs.rst:782 ../scenario_legacy_ovs.rst:838 +#: ../scenario_provider_ovs.rst:475 ../scenario_provider_ovs.rst:537 +msgid "Open vSwitch agent" +msgstr "" + +# #-#-#-#-# scenario_dvr_ovs.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_l3ha_lb.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_l3ha_ovs.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../scenario_dvr_ovs.rst:637 ../scenario_dvr_ovs.rst:724 +#: ../scenario_l3ha_lb.rst:362 ../scenario_l3ha_ovs.rst:373 +#: ../scenario_legacy_lb.rst:681 ../scenario_legacy_ovs.rst:783 +msgid "L3 agent" +msgstr "" + +# #-#-#-#-# scenario_dvr_ovs.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_l3ha_lb.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_l3ha_ovs.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../scenario_dvr_ovs.rst:639 ../scenario_dvr_ovs.rst:725 +#: ../scenario_l3ha_lb.rst:364 ../scenario_l3ha_ovs.rst:375 +#: ../scenario_legacy_lb.rst:683 ../scenario_legacy_ovs.rst:785 +msgid "Metadata agent" +msgstr "" + +#: ../scenario_dvr_ovs.rst:644 +msgid "" +"Configure the kernel to enable packet forwarding, enable *iptables* on " +"bridges, and disable reverse path filtering. Edit the :file:`/etc/sysctl." +"conf` file:" +msgstr "" + +# #-#-#-#-# scenario_dvr_ovs.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_l3ha_lb.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_l3ha_ovs.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../scenario_dvr_ovs.rst:754 ../scenario_l3ha_lb.rst:446 +#: ../scenario_l3ha_ovs.rst:456 ../scenario_legacy_lb.rst:761 +#: ../scenario_legacy_ovs.rst:863 +msgid "" +"This example creates a flat external network and a VXLAN project network." +msgstr "" + +# #-#-#-#-# scenario_dvr_ovs.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_l3ha_lb.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_l3ha_ovs.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../scenario_dvr_ovs.rst:757 ../scenario_l3ha_lb.rst:449 +#: ../scenario_l3ha_ovs.rst:459 ../scenario_legacy_lb.rst:764 +#: ../scenario_legacy_ovs.rst:866 +msgid "Create the external network:" +msgstr "" + +# #-#-#-#-# scenario_dvr_ovs.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_l3ha_lb.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_l3ha_ovs.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../scenario_dvr_ovs.rst:780 ../scenario_l3ha_lb.rst:472 +#: ../scenario_l3ha_ovs.rst:482 ../scenario_legacy_lb.rst:787 +#: ../scenario_legacy_ovs.rst:889 +msgid "Create a subnet on the external network:" +msgstr "" + +#: ../scenario_dvr_ovs.rst:807 +msgid "" +"The example configuration contains ``vlan`` as the first project network " +"type. Only a privileged user can create other types of networks such as GRE " +"or VXLAN. The following commands use the ``admin`` project credentials to " +"create a VXLAN project network." +msgstr "" + +# #-#-#-#-# scenario_dvr_ovs.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_l3ha_lb.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_l3ha_ovs.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../scenario_dvr_ovs.rst:812 ../scenario_l3ha_lb.rst:504 +#: ../scenario_l3ha_ovs.rst:514 ../scenario_legacy_lb.rst:819 +#: ../scenario_legacy_ovs.rst:921 +msgid "" +"Obtain the ID of a regular project. For example, using the ``demo`` project:" +msgstr "" + +# #-#-#-#-# scenario_dvr_ovs.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_l3ha_ovs.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../scenario_dvr_ovs.rst:826 ../scenario_l3ha_ovs.rst:528 +#: ../scenario_legacy_lb.rst:833 ../scenario_legacy_ovs.rst:935 +msgid "Create the project network:" +msgstr "" + +#: ../scenario_dvr_ovs.rst:849 ../scenario_dvr_ovs.rst:961 +msgid "Source the regular project credentials." +msgstr "" + +# #-#-#-#-# scenario_dvr_ovs.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_l3ha_lb.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_l3ha_ovs.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../scenario_dvr_ovs.rst:850 ../scenario_l3ha_lb.rst:544 +#: ../scenario_l3ha_ovs.rst:554 ../scenario_legacy_lb.rst:858 +#: ../scenario_legacy_ovs.rst:960 +msgid "Create a subnet on the project network:" +msgstr "" + +#: ../scenario_dvr_ovs.rst:875 +msgid "Create a distributed project router:" +msgstr "" + +#: ../scenario_dvr_ovs.rst:896 +msgid "" +"Default policy might prevent the '`distributed`` flag from appearing in the " +"command output for non-privileged users." +msgstr "" + +#: ../scenario_dvr_ovs.rst:899 +msgid "Attach the project network to the router:" +msgstr "" + +#: ../scenario_dvr_ovs.rst:906 +msgid "" +"Add a gateway to the external network for the project network on the router:" +msgstr "" + +#: ../scenario_dvr_ovs.rst:917 +msgid "" +"On the network node, verify creation of the `snat`, `qrouter`, and `qdhcp` " +"namespaces:" +msgstr "" + +#: ../scenario_dvr_ovs.rst:928 +msgid "One or more namespaces might not exist until launching an instance." +msgstr "" + +# #-#-#-#-# scenario_dvr_ovs.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_l3ha_lb.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_l3ha_ovs.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../scenario_dvr_ovs.rst:931 ../scenario_l3ha_lb.rst:758 +#: ../scenario_l3ha_ovs.rst:766 ../scenario_legacy_lb.rst:929 +#: ../scenario_legacy_ovs.rst:1032 +msgid "" +"Determine the external network gateway IP address for the project network on " +"the router, typically the lowest IP address in the external subnet IP " +"allocation range:" +msgstr "" + +# #-#-#-#-# scenario_dvr_ovs.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_l3ha_lb.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_l3ha_ovs.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../scenario_dvr_ovs.rst:945 ../scenario_l3ha_lb.rst:774 +#: ../scenario_l3ha_ovs.rst:782 ../scenario_legacy_lb.rst:943 +#: ../scenario_legacy_ovs.rst:1046 +msgid "" +"On the controller node or any host with access to the external network, ping " +"the external network gateway IP address on the project router:" +msgstr "" + +# #-#-#-#-# scenario_dvr_ovs.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../scenario_dvr_ovs.rst:962 ../scenario_legacy_lb.rst:961 +#: ../scenario_legacy_ovs.rst:1064 +msgid "Launch an instance with an interface on the project network." +msgstr "" + +#: ../scenario_dvr_ovs.rst:963 +msgid "" +"On the compute node with the instance, verify creation of the ``qrouter`` " +"namespace:" +msgstr "" + +# #-#-#-#-# scenario_dvr_ovs.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_l3ha_lb.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_l3ha_ovs.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../scenario_dvr_ovs.rst:971 ../scenario_l3ha_lb.rst:849 +#: ../scenario_l3ha_ovs.rst:857 ../scenario_legacy_lb.rst:962 +#: ../scenario_legacy_ovs.rst:1065 +msgid "Obtain console access to the instance." +msgstr "" + +# #-#-#-#-# scenario_dvr_ovs.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_l3ha_lb.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_l3ha_ovs.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../scenario_dvr_ovs.rst:973 ../scenario_l3ha_lb.rst:851 +#: ../scenario_l3ha_ovs.rst:859 ../scenario_legacy_lb.rst:964 +#: ../scenario_legacy_ovs.rst:1067 +msgid "Test connectivity to the project router:" +msgstr "" + +# #-#-#-#-# scenario_dvr_ovs.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_l3ha_lb.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_l3ha_ovs.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../scenario_dvr_ovs.rst:1022 ../scenario_l3ha_lb.rst:881 +#: ../scenario_l3ha_ovs.rst:889 ../scenario_legacy_lb.rst:1013 +#: ../scenario_legacy_ovs.rst:1116 +msgid "Create a floating IP address on the external network:" +msgstr "" + +# #-#-#-#-# scenario_dvr_ovs.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_l3ha_lb.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_l3ha_ovs.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../scenario_dvr_ovs.rst:1041 ../scenario_l3ha_lb.rst:900 +#: ../scenario_l3ha_ovs.rst:908 ../scenario_legacy_lb.rst:1031 +#: ../scenario_legacy_ovs.rst:1134 +msgid "Associate the floating IP address with the instance:" +msgstr "" + +# #-#-#-#-# scenario_dvr_ovs.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_l3ha_lb.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_l3ha_ovs.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../scenario_dvr_ovs.rst:1047 ../scenario_l3ha_lb.rst:906 +#: ../scenario_l3ha_ovs.rst:914 ../scenario_legacy_lb.rst:1037 +#: ../scenario_legacy_ovs.rst:1140 +msgid "Verify addition of the floating IP address to the instance:" +msgstr "" + +#: ../scenario_dvr_ovs.rst:1058 +msgid "" +"On the compute node with the instance, verify creation of the ``fip`` " +"namespace:" +msgstr "" + +# #-#-#-#-# scenario_dvr_ovs.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_l3ha_lb.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_l3ha_ovs.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../scenario_dvr_ovs.rst:1066 ../scenario_l3ha_lb.rst:917 +#: ../scenario_l3ha_ovs.rst:925 ../scenario_legacy_lb.rst:1048 +#: ../scenario_legacy_ovs.rst:1151 +msgid "" +"On the controller node or any host with access to the external network, ping " +"the floating IP address associated with the instance:" +msgstr "" + +#: ../scenario_l3ha_lb.rst:3 +msgid "Scenario: High Availability using VRRP (L3HA) with Linux Bridge" +msgstr "" + +#: ../scenario_l3ha_lb.rst:5 +msgid "" +"This scenario describes a high-availability implementation of the OpenStack " +"Networking service using the ML2 plug-in and Linux bridge." +msgstr "" + +#: ../scenario_l3ha_lb.rst:8 +msgid "" +"This high-availability implementation augments the :doc:`scenario_legacy_lb` " +"architecture with Virtual Router Redundancy Protocol (VRRP) using " +"``keepalived`` to provide quick failover of layer-3 services. See :ref:" +"`scenario_l3ha_lb-packet_flow` for VRRP operation. Similar to the legacy " +"scenario, all network traffic on a project network that requires routing " +"actively traverses only one network node regardless of the quantity of " +"network nodes providing HA for the router. Therefore, this high-availability " +"implementation primarily addresses failure situations instead of bandwidth " +"constraints that limit performance. However, it supports random distribution " +"of routers on different network nodes to reduce the chances of bandwidth " +"constraints and to improve scaling. Also, this implementation does not " +"address situations where one or more layer-3 agents fail and the underlying " +"virtual networks continue to operate normally. Consider deploying :doc:" +"`scenario_dvr_ovs` to increase performance in addition to redundancy. As of " +"the Kilo release, you cannot combine the DVR and L3HA mechanisms." +msgstr "" + +# #-#-#-#-# scenario_l3ha_lb.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_l3ha_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../scenario_l3ha_lb.rst:25 ../scenario_l3ha_ovs.rst:25 +msgid "" +"The failover process only retains the state of network connections for " +"instances with a floating IP address." +msgstr "" + +#: ../scenario_l3ha_lb.rst:28 +msgid "" +"The example configuration creates one flat external network and one VXLAN " +"project (tenant) network. However, this configuration also supports VLAN " +"external and project networks." +msgstr "" + +#: ../scenario_l3ha_lb.rst:33 +msgid "" +"In the Juno (initial) and Kilo releases, L3HA with Linux bridge supports " +"VLAN and VXLAN project networks. However, due to a bug, VXLAN project " +"networks must use multicast instead of the layer-2 population mechanism." +msgstr "" + +# #-#-#-#-# scenario_l3ha_lb.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_l3ha_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../scenario_l3ha_lb.rst:45 ../scenario_l3ha_ovs.rst:44 +msgid "" +"These prerequisites define the minimal physical infrastructure and immediate " +"OpenStack service dependencies necessary to deploy this scenario. For " +"example, the Networking service immediately depends on the Identity service " +"and the Compute service immediately depends on the Networking service. These " +"dependencies lack services such as the Image service because the Networking " +"service does not immediately depend on it. However, the Compute service " +"depends on the Image service to launch an instance. The example " +"configuration in this scenario assumes basic configuration knowledge of " +"Networking service components. For assistance with basic configuration of " +"the Networking service, see the Installation Guide." +msgstr "" + +#: ../scenario_l3ha_lb.rst:60 +msgid "" +"At least two network nodes with four network interfaces: management, project " +"tunnel networks, project VLAN networks, and external (typically the " +"Internet)." +msgstr "" + +#: ../scenario_l3ha_lb.rst:63 +msgid "" +"At least two compute nodes with three network interfaces: management, " +"project tunnel networks, and project VLAN networks." +msgstr "" + +#: ../scenario_l3ha_lb.rst:66 +msgid "" +"To improve understanding of network traffic flow, the network and compute " +"nodes contain a separate network interface for project VLAN networks. In " +"production environments, you can use any network interface for VLAN project " +"networks." +msgstr "" + +# #-#-#-#-# scenario_l3ha_lb.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_l3ha_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../scenario_l3ha_lb.rst:71 ../scenario_l3ha_ovs.rst:74 +msgid "" +"In the example configuration, the management network uses 10.0.0.0/24, the " +"tunnel network uses 10.0.1.0/24, the VRRP network uses 169.254.192.0/18, and " +"the external network uses 203.0.113.0/24. The VLAN network does not require " +"an IP address range because it only handles layer-2 connectivity." +msgstr "" + +#: ../scenario_l3ha_lb.rst:86 +msgid "" +"For VLAN external and project networks, the network infrastructure must " +"support VLAN tagging. For best performance with VXLAN project networks, the " +"network infrastructure should support jumbo frames." +msgstr "" + +#: ../scenario_l3ha_lb.rst:91 +msgid "Proper operation of VXLAN requires kernel 3.13 or newer." +msgstr "" + +# #-#-#-#-# scenario_l3ha_lb.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# +#: ../scenario_l3ha_lb.rst:111 ../scenario_legacy_lb.rst:129 +msgid "" +"ML2 plug-in, Linux bridge agent, L3 agent, DHCP agent, metadata agent, and " +"any dependencies." +msgstr "" + +# #-#-#-#-# scenario_l3ha_lb.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_l3ha_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../scenario_l3ha_lb.rst:129 ../scenario_l3ha_ovs.rst:136 +msgid "The network nodes contain the following components:" +msgstr "" + +# #-#-#-#-# scenario_l3ha_lb.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_l3ha_ovs.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../scenario_l3ha_lb.rst:134 ../scenario_l3ha_ovs.rst:141 +#: ../scenario_legacy_lb.rst:161 ../scenario_legacy_ovs.rst:167 +msgid "" +"DHCP agent managing the ``qdhcp`` namespaces. The ``qdhcp`` namespaces " +"provide DHCP services for instances using project networks." +msgstr "" + +# #-#-#-#-# scenario_l3ha_lb.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_l3ha_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../scenario_l3ha_lb.rst:136 ../scenario_l3ha_ovs.rst:143 +msgid "" +"L3 agent managing the ``qrouter`` namespaces and VRRP using ``keepalived``. " +"The ``qrouter`` namespaces provide routing between project and external " +"networks and among project networks. They also route metadata traffic " +"between instances and the metadata agent." +msgstr "" + +# #-#-#-#-# scenario_l3ha_lb.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_l3ha_ovs.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../scenario_l3ha_lb.rst:140 ../scenario_l3ha_ovs.rst:147 +#: ../scenario_legacy_lb.rst:167 ../scenario_legacy_ovs.rst:173 +msgid "Metadata agent handling metadata operations for instances." +msgstr "" + +#: ../scenario_l3ha_lb.rst:149 +msgid "" +"For simplicity, the hidden project network that connects all HA routers for " +"a particular project uses the VXLAN network type." +msgstr "" + +#: ../scenario_l3ha_lb.rst:169 +msgid "" +"The L3HA mechanism simply augments :doc:`scenario_legacy_lb` with quick " +"failover of layer-3 services to another router if the master router fails." +msgstr "" + +# #-#-#-#-# scenario_l3ha_lb.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_l3ha_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../scenario_l3ha_lb.rst:173 ../scenario_l3ha_ovs.rst:182 +msgid "" +"During normal operation, the master router periodically transmits " +"*heartbeat* packets over a hidden project network that connects all HA " +"routers for a particular project. By default, this network uses the type " +"indicated by the first value in the ``tenant_network_types`` option in the :" +"file:`/etc/neutron/plugins/ml2_conf.ini` file." +msgstr "" + +# #-#-#-#-# scenario_l3ha_lb.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_l3ha_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../scenario_l3ha_lb.rst:179 ../scenario_l3ha_ovs.rst:188 +msgid "" +"If the backup router stops receiving these packets, it assumes failure of " +"the master router and promotes itself to the master router by configuring IP " +"addresses on the interfaces in the ``qrouter`` namespace. In environments " +"with more than one backup router, the router with the next highest priority " +"becomes the master router." +msgstr "" + +# #-#-#-#-# scenario_l3ha_lb.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_l3ha_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../scenario_l3ha_lb.rst:186 ../scenario_l3ha_ovs.rst:195 +msgid "" +"The L3HA mechanism uses the same priority for all routers. Therefore, VRRP " +"promotes the backup router with the highest IP address to the master router." +msgstr "" + +# #-#-#-#-# scenario_l3ha_lb.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# +#: ../scenario_l3ha_lb.rst:240 ../scenario_legacy_lb.rst:564 +msgid "" +"Replace ``MIN_VLAN_ID``, ``MAX_VLAN_ID``, ``MIN_VXLAN_ID``, and " +"``MAX_VXLAN_ID`` with VLAN and VXLAN ID minimum and maximum values suitable " +"for your environment." +msgstr "" + +# #-#-#-#-# scenario_l3ha_lb.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_l3ha_ovs.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../scenario_l3ha_lb.rst:245 ../scenario_l3ha_ovs.rst:257 +#: ../scenario_legacy_lb.rst:569 ../scenario_legacy_ovs.rst:667 +msgid "" +"The first value in the ``tenant_network_types`` option becomes the default " +"project network type when a regular user creates a network." +msgstr "" + +# #-#-#-#-# scenario_l3ha_lb.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_l3ha_ovs.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../scenario_l3ha_lb.rst:249 ../scenario_l3ha_ovs.rst:261 +#: ../scenario_legacy_lb.rst:573 ../scenario_legacy_ovs.rst:671 +msgid "" +"The ``external`` value in the ``network_vlan_ranges`` option lacks VLAN ID " +"ranges to support use of arbitrary VLAN IDs by administrative users." +msgstr "" + +# #-#-#-#-# scenario_l3ha_lb.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_l3ha_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../scenario_l3ha_lb.rst:257 ../scenario_l3ha_ovs.rst:269 +msgid "Network nodes" +msgstr "" + +# #-#-#-#-# scenario_l3ha_lb.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# +#: ../scenario_l3ha_lb.rst:299 ../scenario_l3ha_lb.rst:410 +#: ../scenario_legacy_lb.rst:623 +msgid "" +"Replace ``PROJECT_VLAN_INTERFACE`` and ``EXTERNAL_INTERFACE`` with the name " +"of the underlying interface that handles VLAN project networks and external " +"networks, respectively. Replace ``TUNNEL_INTERFACE_IP_ADDRESS`` with the IP " +"address of the interface that handles project tunnel networks." +msgstr "" + +# #-#-#-#-# scenario_l3ha_lb.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# +#: ../scenario_l3ha_lb.rst:332 ../scenario_legacy_lb.rst:651 +msgid "(Optional) Reduce MTU for VXLAN project networks." +msgstr "" + +# #-#-#-#-# scenario_l3ha_lb.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_l3ha_ovs.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../scenario_l3ha_lb.rst:369 ../scenario_l3ha_ovs.rst:380 +#: ../scenario_legacy_lb.rst:688 ../scenario_legacy_ovs.rst:790 +msgid "" +"Configure the kernel to enable *iptables* on bridges and disable reverse " +"path filtering. Edit the :file:`/etc/sysctl.conf` file:" +msgstr "" + +# #-#-#-#-# scenario_l3ha_lb.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# +#: ../scenario_l3ha_lb.rst:499 ../scenario_legacy_lb.rst:814 +msgid "" +"The example configuration contains ``vlan`` as the first project network " +"type. Only an administrative user can create other types of networks such as " +"VXLAN. The following commands use the ``admin`` project credentials to " +"create a VXLAN project network." +msgstr "" + +#: ../scenario_l3ha_lb.rst:518 +msgid "Create a project network:" +msgstr "" + +# #-#-#-#-# scenario_l3ha_lb.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_l3ha_ovs.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../scenario_l3ha_lb.rst:569 ../scenario_l3ha_ovs.rst:579 +#: ../scenario_legacy_lb.rst:883 ../scenario_legacy_ovs.rst:985 +msgid "Create a project router:" +msgstr "" + +# #-#-#-#-# scenario_l3ha_lb.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_l3ha_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../scenario_l3ha_lb.rst:590 ../scenario_l3ha_ovs.rst:600 +msgid "" +"The default :file:`policy.json` file allows only administrative projects to " +"enable/disable HA during router creation and view the ``ha`` flag for a " +"router." +msgstr "" + +#: ../scenario_l3ha_lb.rst:594 +msgid "Attach the project subnet as an interface on the router:" +msgstr "" + +# #-#-#-#-# scenario_l3ha_lb.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_l3ha_ovs.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../scenario_l3ha_lb.rst:601 ../scenario_l3ha_ovs.rst:611 +#: ../scenario_legacy_lb.rst:907 ../scenario_legacy_ovs.rst:1010 +msgid "Add a gateway to the external network on the router:" +msgstr "" + +# #-#-#-#-# scenario_l3ha_lb.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_l3ha_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../scenario_l3ha_lb.rst:612 ../scenario_l3ha_ovs.rst:622 +msgid "On the controller node, verify creation of the HA network:" +msgstr "" + +# #-#-#-#-# scenario_l3ha_lb.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_l3ha_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../scenario_l3ha_lb.rst:625 ../scenario_l3ha_ovs.rst:635 +msgid "" +"On the controller node, verify creation of the router on more than one " +"network node:" +msgstr "" + +# #-#-#-#-# scenario_l3ha_lb.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_l3ha_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../scenario_l3ha_lb.rst:639 ../scenario_l3ha_ovs.rst:649 +msgid "" +"Older versions of *python-neutronclient* do not support the ``ha_state`` " +"field." +msgstr "" + +# #-#-#-#-# scenario_l3ha_lb.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_l3ha_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../scenario_l3ha_lb.rst:641 ../scenario_l3ha_ovs.rst:651 +msgid "" +"On the controller node, verify creation of the HA ports on the ``demo-" +"router`` router:" +msgstr "" + +#: ../scenario_l3ha_lb.rst:656 +msgid "" +"On the network nodes, verify creation of the ``qrouter`` and ``qdhcp`` " +"namespaces." +msgstr "" + +# #-#-#-#-# scenario_l3ha_lb.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_l3ha_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../scenario_l3ha_lb.rst:659 ../scenario_l3ha_lb.rst:681 +#: ../scenario_l3ha_lb.rst:736 ../scenario_l3ha_ovs.rst:669 +#: ../scenario_l3ha_ovs.rst:690 ../scenario_l3ha_ovs.rst:745 +msgid "Network node 1:" +msgstr "" + +# #-#-#-#-# scenario_l3ha_lb.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_l3ha_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../scenario_l3ha_lb.rst:666 ../scenario_l3ha_lb.rst:705 +#: ../scenario_l3ha_lb.rst:745 ../scenario_l3ha_ovs.rst:676 +#: ../scenario_l3ha_ovs.rst:714 ../scenario_l3ha_ovs.rst:754 +msgid "Network node 2:" +msgstr "" + +# #-#-#-#-# scenario_l3ha_lb.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_l3ha_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../scenario_l3ha_lb.rst:673 ../scenario_l3ha_ovs.rst:683 +msgid "Both ``qrouter`` namespaces should use the same UUID." +msgstr "" + +#: ../scenario_l3ha_lb.rst:677 +msgid "The ``qdhcp`` namespaces might not appear until launching an instance." +msgstr "" + +# #-#-#-#-# scenario_l3ha_lb.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_l3ha_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../scenario_l3ha_lb.rst:679 ../scenario_l3ha_ovs.rst:688 +msgid "On the network nodes, verify HA operation:" +msgstr "" + +#: ../scenario_l3ha_lb.rst:725 +msgid "" +"On each network node, the ``qrouter`` namespace should include the ``ha``, " +"``qr``, and ``qg`` interfaces. On the master node, the ``qr`` interface " +"contains the project network gateway IP address and the ``qg`` interface " +"contains the project network router IP address on the external network. On " +"the backup node, the ``qr`` and ``qg`` interfaces should not contain an IP " +"address. On both nodes, the ``ha`` interface should contain a unique IP " +"address in the 169.254.192.0/18 range." +msgstr "" + +#: ../scenario_l3ha_lb.rst:733 +msgid "" +"On the network nodes, verify VRRP advertisements from the master node HA " +"interface IP address on the appropriate network interface." +msgstr "" + +# #-#-#-#-# scenario_l3ha_lb.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_l3ha_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../scenario_l3ha_lb.rst:756 ../scenario_l3ha_ovs.rst:764 +msgid "The example output uses network interface ``eth1``." +msgstr "" + +#: ../scenario_l3ha_lb.rst:790 +msgid "" +"Source the credentials for a non-privileged project. The following steps use " +"the ``demo`` project." +msgstr "" + +# #-#-#-#-# scenario_l3ha_lb.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_l3ha_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../scenario_l3ha_lb.rst:811 ../scenario_l3ha_ovs.rst:819 +msgid "" +"Launch an instance with an interface on the project network. For example, " +"using an existing *CirrOS* image:" +msgstr "" + +#: ../scenario_l3ha_ovs.rst:3 +msgid "Scenario: High Availability using VRRP (L3HA) with Open vSwitch" +msgstr "" + +#: ../scenario_l3ha_ovs.rst:5 +msgid "" +"This scenario describes a high-availability implementation of the OpenStack " +"Networking service using the ML2 plug-in and Open vSwitch (OVS)." +msgstr "" + +#: ../scenario_l3ha_ovs.rst:8 +msgid "" +"This high-availability implementation augments the :doc:" +"`scenario_legacy_ovs` architecture with Virtual Router Redundancy Protocol " +"(VRRP) using ``keepalived`` to provide quick failover of layer-3 services. " +"See :ref:`scenario_l3ha_ovs-packet_flow` for VRRP operation. Similar to the " +"legacy scenario, all network traffic on a project network that requires " +"routing actively traverses only one network node regardless of the quantity " +"of network nodes providing HA for the router. Therefore, this high-" +"availability implementation primarily addresses failure situations instead " +"of bandwidth constraints that limit performance. However, it supports random " +"distribution of routers on different network nodes to reduce the chances of " +"bandwidth constraints and to improve scaling. Also, this implementation does " +"not address situations where one or more layer-3 agents fail and the " +"underlying virtual networks continue to operate normally. Consider " +"deploying :doc:`scenario_dvr_ovs` to increase performance in addition to " +"redundancy. As of the Kilo release, you cannot combine the DVR and L3HA " +"mechanisms." +msgstr "" + +# #-#-#-#-# scenario_l3ha_ovs.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../scenario_l3ha_ovs.rst:28 ../scenario_legacy_ovs.rst:57 +msgid "" +"The example configuration creates one flat external network and one VXLAN " +"project (tenant) network. However, this configuration also supports VLAN " +"external networks, VLAN project networks, and GRE project networks." +msgstr "" + +#: ../scenario_l3ha_ovs.rst:33 +msgid "" +"Due to a bug in the Juno (initial) and Kilo releases, VXLAN and GRE project " +"networks must use multicast instead of the layer-2 population mechanism." +msgstr "" + +#: ../scenario_l3ha_ovs.rst:59 +msgid "" +"Two network nodes with four network interfaces: management, project tunnel " +"networks, project VLAN networks, and external (typically the Internet). The " +"Open vSwitch bridge ``br-vlan`` must contain a port on the VLAN interface " +"and Open vSwitch bridge ``br-ex`` must contain a port on the external " +"interface." +msgstr "" + +#: ../scenario_l3ha_ovs.rst:64 +msgid "" +"At least one compute node with three network interfaces: management, project " +"tunnel networks, and project VLAN networks. The Open vSwitch bridge ``br-" +"vlan`` must contain a port on the VLAN interface." +msgstr "" + +#: ../scenario_l3ha_ovs.rst:68 +msgid "" +"To improve understanding of network traffic flow, the network and compute " +"nodes contain a separate network interface for project VLAN networks. In " +"production environments, project VLAN networks can use any Open vSwitch " +"bridge with access to a network interface. For example, the ``br-tun`` " +"bridge." +msgstr "" + +# #-#-#-#-# scenario_l3ha_ovs.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../scenario_l3ha_ovs.rst:94 ../scenario_legacy_ovs.rst:113 +msgid "" +"Proper operation of this scenario requires Open vSwitch 2.1 or newer. VXLAN " +"also requires kernel 3.13 or newer." +msgstr "" + +#: ../scenario_l3ha_ovs.rst:106 +msgid "" +"Operational OpenStack Compute controller/management service with appropriate " +"configuration to use OpenStack Networking in the :file:`nova.conf` file." +msgstr "" + +#: ../scenario_l3ha_ovs.rst:112 +msgid "OpenStack services - network nodes" +msgstr "" + +#: ../scenario_l3ha_ovs.rst:124 +msgid "" +"Operational OpenStack Compute controller/management service with appropriate " +"configuration to use OpenStack Networking in the :file:`neutron.conf` file." +msgstr "" + +# #-#-#-#-# scenario_l3ha_ovs.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../scenario_l3ha_ovs.rst:127 ../scenario_legacy_ovs.rst:145 +#: ../scenario_provider_ovs.rst:99 +msgid "" +"Open vSwitch service, ML2 plug-in, Open vSwitch agent, and any dependencies." +msgstr "" + +#: ../scenario_l3ha_ovs.rst:155 +msgid "The compute nodes contain the following components:" +msgstr "" + +#: ../scenario_l3ha_ovs.rst:178 +msgid "" +"The L3HA mechanism simply augments :doc:`scenario_legacy_ovs` with quick " +"failover of layer-3 services to another router if the master router fails." +msgstr "" + +# #-#-#-#-# scenario_l3ha_ovs.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../scenario_l3ha_ovs.rst:342 ../scenario_legacy_ovs.rst:752 +msgid "(Optional) Reduce MTU for VXLAN/GRE project networks." +msgstr "" + +# #-#-#-#-# scenario_l3ha_ovs.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../scenario_l3ha_ovs.rst:509 ../scenario_legacy_ovs.rst:916 +msgid "" +"The example configuration contains ``vlan`` as the first project network " +"type. Only an administrative user can create other types of networks such as " +"GRE or VXLAN. The following commands use the ``admin`` project credentials " +"to create a VXLAN project network." +msgstr "" + +#: ../scenario_l3ha_ovs.rst:552 +msgid "" +"Source the ``demo`` project credentials. The following steps use the " +"``demo`` project." +msgstr "" + +# #-#-#-#-# scenario_l3ha_ovs.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../scenario_l3ha_ovs.rst:604 ../scenario_legacy_lb.rst:900 +#: ../scenario_legacy_ovs.rst:1003 +msgid "Add the project subnet as an interface on the router:" +msgstr "" + +#: ../scenario_l3ha_ovs.rst:666 +msgid "" +"On the network nodes, verify creation of the ``qrouter`` and ``qdhcp`` " +"namespaces:" +msgstr "" + +#: ../scenario_l3ha_ovs.rst:686 +msgid "The ``qdhcp`` namespaces might not exist until launching an instance." +msgstr "" + +#: ../scenario_l3ha_ovs.rst:734 +msgid "" +"On each network node, the ``qrouter`` namespace should include the ``ha``, " +"``qr``, and ``qg`` interfaces. On the master node, the ``qr`` interface " +"contains the project network gateway IP address and the ``qg`` interface " +"contains the project router IP address on the external network. On the " +"backup node, the ``qr`` and ``qg`` interfaces should not contain an IP " +"address. On both nodes, the ``ha`` interface should contain a unique IP " +"address in the 169.254.192.0/18 range." +msgstr "" + +#: ../scenario_l3ha_ovs.rst:742 +msgid "" +"On the network nodes, verify VRRP advertisements from the master node HA " +"interface IP address on the appropriate network interface:" +msgstr "" + +#: ../scenario_legacy_lb.rst:3 +msgid "Scenario: Legacy with Linux Bridge" +msgstr "" + +#: ../scenario_legacy_lb.rst:5 +msgid "" +"This scenario describes a legacy (basic) implementation of the OpenStack " +"Networking service using the ML2 plug-in with Linux bridge." +msgstr "" + +# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../scenario_legacy_lb.rst:8 ../scenario_legacy_ovs.rst:8 +msgid "" +"The legacy implementation contributes the networking portion of self-service " +"virtual data center infrastructure by providing a method for regular (non-" +"privileged) users to manage virtual networks within a project and includes " +"the following components:" +msgstr "" + +# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../scenario_legacy_lb.rst:13 ../scenario_legacy_ovs.rst:13 +msgid "Project (tenant) networks" +msgstr "" + +# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../scenario_legacy_lb.rst:15 ../scenario_legacy_ovs.rst:15 +msgid "" +"Project networks provide connectivity to instances for a particular project. " +"Regular (non-privileged) users can manage project networks within the " +"allocation that an administrator or operator defines for for them. Project " +"networks can use VLAN, GRE, or VXLAN transport methods depending on the " +"allocation. Project networks generally use private IP address ranges " +"(RFC1918) and lack connectivity to external networks such as the Internet. " +"Networking refers to IP addresses on project networks as *fixed* IP " +"addresses." +msgstr "" + +# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../scenario_legacy_lb.rst:24 ../scenario_legacy_ovs.rst:24 +msgid "External networks" +msgstr "" + +# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../scenario_legacy_lb.rst:26 ../scenario_legacy_ovs.rst:26 +msgid "" +"External networks provide connectivity to external networks such as the " +"Internet. Only administrative (privileged) users can manage external " +"networks because they interface with the physical network infrastructure. " +"External networks can use flat or VLAN transport methods depending on the " +"physical network infrastructure and generally use public IP address ranges." +msgstr "" + +# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../scenario_legacy_lb.rst:34 ../scenario_legacy_ovs.rst:34 +msgid "" +"A flat network essentially uses the untagged or native VLAN. Similar to " +"layer-2 properties of physical networks, only one flat network can exist per " +"external bridge. In most cases, production deployments should use VLAN " +"transport for external networks." +msgstr "" + +# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../scenario_legacy_lb.rst:41 ../scenario_legacy_ovs.rst:41 +msgid "" +"Routers typically connect project and external networks. By default, they " +"implement SNAT to provide outbound external connectivity for instances on " +"project networks. Each router uses an IP address in the external network " +"allocation for SNAT. Routers also use DNAT to provide inbound external " +"connectivity for instances on project networks. Networking refers to IP " +"addresses on routers that provide inbound external connectivity for " +"instances on project networks as *floating* IP addresses. Routers can also " +"connect project networks that belong to the same project." +msgstr "" + +# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../scenario_legacy_lb.rst:50 ../scenario_legacy_ovs.rst:50 +msgid "Supporting services" +msgstr "" + +# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../scenario_legacy_lb.rst:52 ../scenario_legacy_ovs.rst:52 +msgid "" +"Other supporting services include DHCP and metadata. The DHCP service " +"manages IP addresses for instances on project networks. The metadata service " +"provides an API for instances on project networks to obtain metadata such as " +"SSH keys." +msgstr "" + +#: ../scenario_legacy_lb.rst:57 +msgid "" +"The example configuration creates one flat external network and one VXLAN " +"project network. However, this configuration also supports VLAN external and " +"project networks. The Linux bridge agent does not support GRE project " +"networks." +msgstr "" + +#: ../scenario_legacy_lb.rst:79 +msgid "" +"One network node with four network interfaces: management, project tunnel " +"networks, VLAN project networks, and external (typically the Internet)." +msgstr "" + +#: ../scenario_legacy_lb.rst:81 +msgid "" +"At least one compute nodes with three network interfaces: management, " +"project tunnel networks, and VLAN project networks." +msgstr "" + +#: ../scenario_legacy_lb.rst:84 +msgid "" +"To improve understanding of network traffic flow, the network and compute " +"nodes contain a separate network interface for VLAN project networks. In " +"production environments, you can use any network interface for VLAN project " +"networks." +msgstr "" + +# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../scenario_legacy_lb.rst:89 ../scenario_legacy_ovs.rst:93 +msgid "" +"In the example configuration, the management network uses 10.0.0.0/24, the " +"tunnel network uses 10.0.1.0/24, and the external network uses " +"203.0.113.0/24. The VLAN network does not require an IP address range " +"because it only handles layer-2 connectivity." +msgstr "" + +#: ../scenario_legacy_lb.rst:104 +msgid "" +"For VLAN external and project networks, the physical network infrastructure " +"must support VLAN tagging. For best performance with VXLAN project networks, " +"the network infrastructure should support jumbo frames." +msgstr "" + +#: ../scenario_legacy_lb.rst:109 +msgid "Proper operation of this scenario requires kernel 3.13 or newer." +msgstr "" + +#: ../scenario_legacy_lb.rst:144 +msgid "" +"The legacy architecture provides basic virtual networking components in your " +"environment. Routing among project and external networks resides completely " +"on the network node. Although more simple to deploy than other " +"architectures, performing all functions on the network node creates a single " +"point of failure and potential performance issues. Consider deploying DVR or " +"L3 HA architectures in production environments to provide redundancy and " +"increase performance. However, the DVR architecture requires Open vSwitch." +msgstr "" + +# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../scenario_legacy_lb.rst:163 ../scenario_legacy_ovs.rst:169 +msgid "" +"L3 agent managing the ``qrouter`` namespaces. The ``qrouter`` namespaces " +"provide routing between project and external networks and among project " +"networks. They also route metadata traffic between instances and the " +"metadata agent." +msgstr "" + +# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../scenario_legacy_lb.rst:196 ../scenario_legacy_ovs.rst:205 +msgid "Case 1: North-south for instances with a fixed IP address" +msgstr "" + +# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../scenario_legacy_lb.rst:198 ../scenario_legacy_ovs.rst:207 +msgid "" +"For instances with a fixed IP address, the network node routes *north-south* " +"network traffic between project and external networks." +msgstr "" + +# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../scenario_legacy_lb.rst:204 ../scenario_legacy_lb.rst:300 +#: ../scenario_legacy_ovs.rst:213 ../scenario_legacy_ovs.rst:305 +msgid "IP address allocation from 203.0.113.101 to 203.0.113.200" +msgstr "" + +#: ../scenario_legacy_lb.rst:220 ../scenario_legacy_lb.rst:317 +msgid "" +"Although the diagram shows both VXLAN and VLAN project networks, the packet " +"flow only considers one instance using a VXLAN project network." +msgstr "" + +#: ../scenario_legacy_lb.rst:225 ../scenario_legacy_lb.rst:254 +#: ../scenario_legacy_lb.rst:330 ../scenario_legacy_lb.rst:351 +msgid "For VXLAN project networks:" +msgstr "" + +#: ../scenario_legacy_lb.rst:227 +msgid "" +"The instance 1 ``tap`` interface (1) forwards the packet to the tunnel " +"bridge ``qbr``. The packet contains destination MAC address *TG* because the " +"destination resides on another network." +msgstr "" + +#: ../scenario_legacy_lb.rst:230 ../scenario_legacy_lb.rst:417 +#: ../scenario_legacy_lb.rst:494 +msgid "" +"Security group rules (2) on the tunnel bridge ``qbr`` handle state tracking " +"for the packet." +msgstr "" + +#: ../scenario_legacy_lb.rst:232 ../scenario_legacy_lb.rst:419 +#: ../scenario_legacy_lb.rst:496 +msgid "" +"The tunnel bridge ``qbr`` forwards the packet to the logical tunnel " +"interface ``vxlan-sid`` (3) where *sid* contains the project network " +"segmentation ID." +msgstr "" + +#: ../scenario_legacy_lb.rst:235 ../scenario_legacy_lb.rst:422 +#: ../scenario_legacy_lb.rst:499 +msgid "The physical tunnel interface forwards the packet to the network node." +msgstr "" + +# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../scenario_legacy_lb.rst:238 ../scenario_legacy_lb.rst:265 +#: ../scenario_legacy_lb.rst:339 ../scenario_legacy_lb.rst:363 +#: ../scenario_legacy_ovs.rst:239 ../scenario_legacy_ovs.rst:259 +#: ../scenario_legacy_ovs.rst:337 ../scenario_legacy_ovs.rst:357 +#: ../scenario_legacy_ovs.rst:429 ../scenario_legacy_ovs.rst:449 +#: ../scenario_legacy_ovs.rst:477 ../scenario_legacy_ovs.rst:497 +#: ../scenario_legacy_ovs.rst:564 ../scenario_legacy_ovs.rst:584 +msgid "For VLAN project networks:" +msgstr "" + +#: ../scenario_legacy_lb.rst:240 +msgid "" +"The instance 1 ``tap`` interface forwards the packet to the VLAN bridge " +"``qbr``. The packet contains destination MAC address *TG* because the " +"destination resides on another network." +msgstr "" + +#: ../scenario_legacy_lb.rst:243 +msgid "" +"Security group rules on the VLAN bridge ``qbr`` handle state tracking for " +"the packet." +msgstr "" + +#: ../scenario_legacy_lb.rst:245 ../scenario_legacy_lb.rst:343 +msgid "" +"The VLAN bridge ``qbr`` forwards the packet to the logical VLAN interface " +"``device.sid`` where *device* references the underlying physical VLAN " +"interface and *sid* contains the project network segmentation ID." +msgstr "" + +#: ../scenario_legacy_lb.rst:249 +msgid "" +"The logical VLAN interface ``device.sid`` forwards the packet to the network " +"node via the physical VLAN interface." +msgstr "" + +#: ../scenario_legacy_lb.rst:256 ../scenario_legacy_lb.rst:427 +#: ../scenario_legacy_lb.rst:504 +msgid "" +"The physical tunnel interface forwards the packet to the logical tunnel " +"interface ``vxlan-sid`` (4) where *sid* contains the project network " +"segmentation ID." +msgstr "" + +#: ../scenario_legacy_lb.rst:259 ../scenario_legacy_lb.rst:356 +#: ../scenario_legacy_lb.rst:430 ../scenario_legacy_lb.rst:507 +msgid "" +"The logical tunnel interface ``vxlan-sid`` forwards the packet to the tunnel " +"bridge ``qbr``." +msgstr "" + +#: ../scenario_legacy_lb.rst:261 +msgid "" +"The tunnel bridge ``qbr`` forwards the packet to the ``qr`` interface (5) in " +"the router namespace ``qrouter``. The ``qr`` interface contains the project " +"network router interface IP address *TG*." +msgstr "" + +#: ../scenario_legacy_lb.rst:267 ../scenario_legacy_lb.rst:365 +msgid "" +"The physical VLAN interface forwards the packet to the logical VLAN " +"interface ``device.sid`` where *device* references the underlying physical " +"VLAN interface and *sid* contains the project network segmentation ID." +msgstr "" + +#: ../scenario_legacy_lb.rst:271 ../scenario_legacy_lb.rst:369 +msgid "" +"The logical VLAN interface ``device.sid`` forwards the packet to the VLAN " +"bridge ``qbr``." +msgstr "" + +#: ../scenario_legacy_lb.rst:273 +msgid "" +"The VLAN bridge ``qbr`` forwards the packet to the ``qr`` interface in the " +"router namespace ``qrouter``. The ``qr`` interface contains the project " +"network 1 gateway IP address *TG*." +msgstr "" + +#: ../scenario_legacy_lb.rst:277 +msgid "" +"The *iptables* service (6) performs SNAT on the packet using the ``qg`` " +"interface (7) as the source IP address. The ``qg`` interface contains the " +"project network router interface IP address *TR*." +msgstr "" + +#: ../scenario_legacy_lb.rst:280 +msgid "" +"The router namespace ``qrouter`` forwards the packet to the external bridge " +"``qbr``." +msgstr "" + +#: ../scenario_legacy_lb.rst:282 +msgid "" +"The external bridge ``qbr`` forwards the packet to the external network via " +"the physical external interface." +msgstr "" + +# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../scenario_legacy_lb.rst:292 ../scenario_legacy_ovs.rst:297 +msgid "Case 2: North-south for instances with a floating IP address" +msgstr "" + +# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../scenario_legacy_lb.rst:294 ../scenario_legacy_ovs.rst:299 +msgid "" +"For instances with a floating IP address, the network node routes *north-" +"south* network traffic between project and external networks." +msgstr "" + +# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../scenario_legacy_lb.rst:314 ../scenario_legacy_ovs.rst:319 +msgid "The instance receives a packet from a host on the external network." +msgstr "" + +#: ../scenario_legacy_lb.rst:322 +msgid "" +"The physical external interface forwards the packet to the external bridge " +"``qbr``." +msgstr "" + +#: ../scenario_legacy_lb.rst:324 +msgid "" +"The external bridge ``qbr`` forwards the packet to the ``qg`` interface (1) " +"in the router namespace ``qrouter``. The ``qg`` interface contains the " +"instance floating IP address *F1*." +msgstr "" + +#: ../scenario_legacy_lb.rst:327 +msgid "" +"The *iptables* service (2) performs DNAT on the packet using the ``qr`` " +"interface (3) as the source IP address. The ``qr`` interface contains the " +"project network gateway IP address *TR*." +msgstr "" + +#: ../scenario_legacy_lb.rst:332 +msgid "" +"The router namespace ``qrouter`` forwards the packet to the tunnel bridge " +"``qbr``." +msgstr "" + +#: ../scenario_legacy_lb.rst:334 +msgid "" +"The tunnel bridge ``qbr`` forwards the packet to the logical tunnel " +"interface ``vxlan-sid`` (4) where *sid* contains the project network " +"segmentation ID." +msgstr "" + +#: ../scenario_legacy_lb.rst:337 +msgid "The physical tunnel interface forwards the packet to compute node 1." +msgstr "" + +#: ../scenario_legacy_lb.rst:341 ../scenario_legacy_lb.rst:439 +msgid "" +"The router namespace ``qrouter`` forwards the packet to the VLAN bridge " +"``qbr``." +msgstr "" + +#: ../scenario_legacy_lb.rst:347 +msgid "The physical VLAN interface forwards the packet to compute node 1." +msgstr "" + +#: ../scenario_legacy_lb.rst:353 +msgid "" +"The physical tunnel interface forwards the packet to the logical tunnel " +"interface ``vxlan-sid`` (5) where *sid* contains the project network " +"segmentation ID." +msgstr "" + +#: ../scenario_legacy_lb.rst:358 +msgid "" +"Security group rules (6) on the tunnel bridge ``qbr`` handle firewalling and " +"state tracking for the packet." +msgstr "" + +#: ../scenario_legacy_lb.rst:360 +msgid "" +"The tunnel bridge ``qbr`` forwards the packet to the ``tap`` interface (7) " +"on instance 1." +msgstr "" + +#: ../scenario_legacy_lb.rst:371 +msgid "" +"Security group rules on the VLAN bridge ``qbr`` handle firewalling and state " +"tracking for the packet." +msgstr "" + +#: ../scenario_legacy_lb.rst:373 +msgid "" +"The VLAN bridge ``qbr`` forwards the packet to the ``tap`` interface on " +"instance 1." +msgstr "" + +# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../scenario_legacy_lb.rst:383 ../scenario_legacy_ovs.rst:389 +msgid "Case 3: East-west for instances on different networks" +msgstr "" + +# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../scenario_legacy_lb.rst:385 ../scenario_legacy_ovs.rst:391 +msgid "" +"For instances with a fixed or floating IP address, the network node routes " +"*east-west* network traffic among project networks using the same project " +"router." +msgstr "" + +# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../scenario_legacy_lb.rst:391 ../scenario_legacy_lb.rst:473 +#: ../scenario_legacy_ovs.rst:397 ../scenario_legacy_ovs.rst:537 +msgid "Network: 192.168.1.0/24" +msgstr "" + +# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../scenario_legacy_lb.rst:392 ../scenario_legacy_ovs.rst:398 +msgid "Gateway: 192.168.1.1 with MAC address *TG1*" +msgstr "" + +# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../scenario_legacy_lb.rst:396 ../scenario_legacy_ovs.rst:402 +msgid "Network: 192.168.2.0/24" +msgstr "" + +# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../scenario_legacy_lb.rst:397 ../scenario_legacy_ovs.rst:403 +msgid "Gateway: 192.168.2.1 with MAC address *TG2*" +msgstr "" + +# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../scenario_legacy_lb.rst:401 ../scenario_legacy_lb.rst:477 +#: ../scenario_legacy_ovs.rst:407 ../scenario_legacy_ovs.rst:541 +msgid "Instance 1: 192.168.1.11 with MAC address *I1*" +msgstr "" + +# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../scenario_legacy_lb.rst:405 ../scenario_legacy_ovs.rst:411 +msgid "Instance 2: 192.168.2.11 with MAC address *I2*" +msgstr "" + +#: ../scenario_legacy_lb.rst:407 +msgid "Instance 1 resides on compute node 1 and uses VXLAN project network 1." +msgstr "" + +#: ../scenario_legacy_lb.rst:408 +msgid "Instance 2 resides on compute node 2 and uses VLAN project network 2." +msgstr "" + +# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../scenario_legacy_lb.rst:409 ../scenario_legacy_ovs.rst:415 +msgid "Both project networks reside on the same router." +msgstr "" + +#: ../scenario_legacy_lb.rst:414 ../scenario_legacy_lb.rst:491 +msgid "" +"The instance 1 ``tap`` interface (1) forwards the packet to the tunnel " +"bridge ``qbr``. The packet contains destination MAC address *TG1* because " +"the destination resides on another network." +msgstr "" + +#: ../scenario_legacy_lb.rst:432 +msgid "" +"The tunnel bridge ``qbr`` forwards the packet to the ``qr-1`` interface (5) " +"in the router namespace ``qrouter``. The ``qr-1`` interface contains the " +"project network 1 gateway IP address *TG1*." +msgstr "" + +#: ../scenario_legacy_lb.rst:436 +msgid "" +"The router namespace ``qrouter`` routes the packet (6) to the ``qr-2`` " +"interface (7). The ``qr-2`` interface contains the project network 2 gateway " +"IP address *TG2*." +msgstr "" + +#: ../scenario_legacy_lb.rst:441 +msgid "" +"The VLAN bridge ``qbr`` forwards the packet to the logical VLAN interface " +"``vlan.sid`` (8) where *sid* contains the project network segmentation ID." +msgstr "" + +#: ../scenario_legacy_lb.rst:444 +msgid "The physical VLAN interface forwards the packet to compute node 2." +msgstr "" + +#: ../scenario_legacy_lb.rst:448 +msgid "" +"The physical VLAN interface forwards the packet to the logical VLAN " +"interface ``vlan.sid`` (9) where *sid* contains the project network " +"segmentation ID." +msgstr "" + +#: ../scenario_legacy_lb.rst:451 +msgid "" +"The logical VLAN interface ``vlan.sid`` forwards the packet to the VLAN " +"bridge ``qbr``." +msgstr "" + +#: ../scenario_legacy_lb.rst:453 +msgid "" +"Security group rules (10) on the VLAN bridge ``qbr`` handle firewalling and " +"state tracking for the packet." +msgstr "" + +#: ../scenario_legacy_lb.rst:455 +msgid "" +"The VLAN bridge ``qbr`` forwards the packet to the ``tap`` interface (11) on " +"instance 2." +msgstr "" + +# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../scenario_legacy_lb.rst:465 ../scenario_legacy_ovs.rst:529 +msgid "Case 4: East-west for instances on the same network" +msgstr "" + +# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../scenario_legacy_lb.rst:467 ../scenario_legacy_ovs.rst:531 +msgid "" +"For instances with a fixed or floating IP address, the project network " +"switches *east-west* network traffic among instances without using a project " +"router on the network node." +msgstr "" + +# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../scenario_legacy_lb.rst:481 ../scenario_legacy_ovs.rst:545 +msgid "Instance 2: 192.168.1.12 with MAC address *I2*" +msgstr "" + +#: ../scenario_legacy_lb.rst:485 +msgid "Both instances use the same VXLAN project network." +msgstr "" + +#: ../scenario_legacy_lb.rst:487 +msgid "The Linux bridge agent handles switching within the project network." +msgstr "" + +#: ../scenario_legacy_lb.rst:509 +msgid "" +"Security group rules (5) on the tunnel bridge ``qbr`` handle firewalling and " +"state tracking for the packet." +msgstr "" + +#: ../scenario_legacy_lb.rst:511 +msgid "" +"The tunnel bridge ``qbr`` forwards the packet to the ``tap`` interface (6) " +"on instance 2." +msgstr "" + +#: ../scenario_legacy_lb.rst:729 +msgid "" +"Replace ``PROJECT_VLAN_INTERFACE`` with the name of the underlying interface " +"that handles VLAN project networks and external networks, respectively. " +"Replace ``TUNNEL_INTERFACE_IP_ADDRESS`` with the IP address of the interface " +"that handles VXLAN project networks." +msgstr "" + +# #-#-#-#-# scenario_legacy_lb.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../scenario_legacy_lb.rst:917 ../scenario_legacy_ovs.rst:1020 +msgid "" +"On the network node, verify creation of the ``qrouter`` and ``qdhcp`` " +"namespaces:" +msgstr "" + +#: ../scenario_legacy_ovs.rst:3 +msgid "Scenario: Legacy with Open vSwitch" +msgstr "" + +#: ../scenario_legacy_ovs.rst:5 +msgid "" +"This scenario describes a legacy (basic) implementation of the OpenStack " +"Networking service using the ML2 plug-in with Open vSwitch (OVS)." +msgstr "" + +#: ../scenario_legacy_ovs.rst:78 +msgid "" +"One network node with four network interfaces: management, project tunnel " +"networks, VLAN project networks, and external (typically the Internet). The " +"Open vSwitch bridge ``br-vlan`` must contain a port on the VLAN interface " +"and Open vSwitch bridge ``br-ex`` must contain a port on the external " +"interface." +msgstr "" + +#: ../scenario_legacy_ovs.rst:83 +msgid "" +"At least one compute node with three network interfaces: management, project " +"tunnel networks, and VLAN project networks. The Open vSwitch bridge ``br-" +"vlan`` must contain a port on the VLAN interface." +msgstr "" + +#: ../scenario_legacy_ovs.rst:87 +msgid "" +"To improve understanding of network traffic flow, the network and compute " +"nodes contain a separate network interface for VLAN project networks. In " +"production environments, VLAN project networks can use any Open vSwitch " +"bridge with access to a network interface. For example, the ``br-tun`` " +"bridge." +msgstr "" + +#: ../scenario_legacy_ovs.rst:108 +msgid "" +"For VLAN external and project networks, the physical network infrastructure " +"must support VLAN tagging. For best performance with VXLAN and GRE project " +"networks, the network infrastructure should support jumbo frames." +msgstr "" + +#: ../scenario_legacy_ovs.rst:151 +msgid "" +"The legacy architecture provides basic virtual networking components in your " +"environment. Routing among project and external networks resides completely " +"on the network node. Although more simple to deploy than other " +"architectures, performing all functions on the network node creates a single " +"point of failure and potential performance issues. Consider deploying DVR or " +"L3 HA architectures in production environments to provide redundancy and " +"increase performance." +msgstr "" + +#: ../scenario_legacy_ovs.rst:186 +msgid "" +"Linux bridges handling security groups. Due to limitations with Open vSwitch " +"and *iptables*, the Networking service uses a Linux bridge to manage " +"security groups for instances." +msgstr "" + +#: ../scenario_legacy_ovs.rst:237 ../scenario_legacy_ovs.rst:335 +msgid "" +"The Open vSwitch integration bridge ``br-int`` adds the internal tag for the " +"project network." +msgstr "" + +#: ../scenario_legacy_ovs.rst:241 ../scenario_legacy_ovs.rst:339 +#: ../scenario_legacy_ovs.rst:431 ../scenario_legacy_ovs.rst:479 +#: ../scenario_legacy_ovs.rst:566 +msgid "" +"The Open vSwitch integration bridge ``br-int`` forwards the packet to the " +"Open vSwitch VLAN bridge ``br-vlan``." +msgstr "" + +#: ../scenario_legacy_ovs.rst:243 ../scenario_legacy_ovs.rst:341 +msgid "" +"The Open vSwitch VLAN bridge ``br-vlan`` replaces the internal tag with the " +"actual VLAN tag of the project network." +msgstr "" + +#: ../scenario_legacy_ovs.rst:245 ../scenario_legacy_ovs.rst:435 +msgid "" +"The Open vSwitch VLAN bridge ``br-vlan`` forwards the packet to the network " +"node via the VLAN interface." +msgstr "" + +#: ../scenario_legacy_ovs.rst:248 ../scenario_legacy_ovs.rst:268 +#: ../scenario_legacy_ovs.rst:346 ../scenario_legacy_ovs.rst:366 +#: ../scenario_legacy_ovs.rst:438 ../scenario_legacy_ovs.rst:458 +#: ../scenario_legacy_ovs.rst:486 ../scenario_legacy_ovs.rst:506 +#: ../scenario_legacy_ovs.rst:573 ../scenario_legacy_ovs.rst:593 +msgid "For VXLAN and GRE project networks:" +msgstr "" + +#: ../scenario_legacy_ovs.rst:252 ../scenario_legacy_ovs.rst:350 +msgid "" +"The Open vSwitch tunnel bridge ``br-tun`` wraps the packet in a VXLAN or GRE " +"tunnel and adds a tag to identify the project network." +msgstr "" + +#: ../scenario_legacy_ovs.rst:261 ../scenario_legacy_ovs.rst:359 +#: ../scenario_legacy_ovs.rst:451 ../scenario_legacy_ovs.rst:499 +#: ../scenario_legacy_ovs.rst:586 +msgid "" +"The VLAN interface forwards the packet to the Open vSwitch VLAN bridge ``br-" +"vlan``." +msgstr "" + +#: ../scenario_legacy_ovs.rst:263 ../scenario_legacy_ovs.rst:361 +#: ../scenario_legacy_ovs.rst:453 ../scenario_legacy_ovs.rst:501 +#: ../scenario_legacy_ovs.rst:588 +msgid "" +"The Open vSwitch VLAN bridge ``br-vlan`` forwards the packet to the Open " +"vSwitch integration bridge ``br-int``." +msgstr "" + +#: ../scenario_legacy_ovs.rst:265 +msgid "" +"The Open vSwitch integration bridge ``br-int`` replaces the actual VLAN tag " +"of the project network with the internal tag." +msgstr "" + +#: ../scenario_legacy_ovs.rst:272 ../scenario_legacy_ovs.rst:370 +msgid "" +"The Open vSwitch tunnel bridge ``br-tun`` unwraps the packet and adds the " +"internal tag for the project network." +msgstr "" + +#: ../scenario_legacy_ovs.rst:277 +msgid "" +"The Open vSwitch integration bridge ``br-int`` forwards the packet to the " +"``qr`` interface (3) in the router namespace ``qrouter``. The ``qr`` " +"interface contains the project network gateway IP address *TG*." +msgstr "" + +#: ../scenario_legacy_ovs.rst:280 +msgid "" +"The *iptables* service (4) performs SNAT on the packet using the ``qg`` " +"interface (5) as the source IP address. The ``qg`` interface contains the " +"project network router interface IP address *TR*." +msgstr "" + +#: ../scenario_legacy_ovs.rst:283 +msgid "" +"The router namespace ``qrouter`` forwards the packet to the Open vSwitch " +"integration bridge ``br-int`` via the ``qg`` interface." +msgstr "" + +#: ../scenario_legacy_ovs.rst:285 +msgid "" +"The Open vSwitch integration bridge ``br-int`` forwards the packet to the " +"Open vSwitch external bridge ``br-ex``." +msgstr "" + +#: ../scenario_legacy_ovs.rst:323 +msgid "" +"The external interface forwards the packet to the Open vSwitch external " +"bridge ``br-ex``." +msgstr "" + +#: ../scenario_legacy_ovs.rst:325 +msgid "" +"The Open vSwitch external bridge ``br-ex`` forwards the packet to the Open " +"vSwitch integration bridge ``br-int``." +msgstr "" + +#: ../scenario_legacy_ovs.rst:327 +msgid "" +"The Open vSwitch integration bridge forwards the packet to the ``qg`` " +"interface (1) in the router namespace ``qrouter``. The ``qg`` interface " +"contains the instance 1 floating IP address *F1*." +msgstr "" + +#: ../scenario_legacy_ovs.rst:330 +msgid "" +"The *iptables* service (2) performs DNAT on the packet using the ``qr`` " +"interface (3) as the source IP address. The ``qr`` interface contains the " +"project network router interface IP address *TR1*." +msgstr "" + +#: ../scenario_legacy_ovs.rst:333 ../scenario_legacy_ovs.rst:473 +msgid "" +"The router namespace ``qrouter`` forwards the packet to the Open vSwitch " +"integration bridge ``br-int``." +msgstr "" + +#: ../scenario_legacy_ovs.rst:343 +msgid "" +"The Open vSwitch VLAN bridge ``br-vlan`` forwards the packet to the compute " +"node via the VLAN interface." +msgstr "" + +#: ../scenario_legacy_ovs.rst:352 +msgid "" +"The Open vSwitch tunnel bridge ``br-tun`` forwards the packet to the compute " +"node via the tunnel interface." +msgstr "" + +#: ../scenario_legacy_ovs.rst:363 +msgid "" +"The Open vSwitch integration bridge ``br-int`` replaces the actual VLAN tag " +"the project network with the internal tag." +msgstr "" + +# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../scenario_legacy_ovs.rst:377 ../scenario_provider_ovs.rst:356 +msgid "" +"Security group rules (4) on the Linux bridge ``qbr`` handle firewalling and " +"state tracking for the packet." +msgstr "" + +#: ../scenario_legacy_ovs.rst:379 +msgid "" +"The Linux bridge ``qbr`` forwards the packet to the ``tap`` interface (5) on " +"instance 1." +msgstr "" + +#: ../scenario_legacy_ovs.rst:427 +msgid "" +"The Open vSwitch integration bridge ``br-int`` adds the internal tag for " +"project network 1." +msgstr "" + +#: ../scenario_legacy_ovs.rst:433 ../scenario_legacy_ovs.rst:568 +msgid "" +"The Open vSwitch VLAN bridge ``br-vlan`` replaces the internal tag with the " +"actual VLAN tag of project network 1." +msgstr "" + +#: ../scenario_legacy_ovs.rst:442 ../scenario_legacy_ovs.rst:577 +msgid "" +"The Open vSwitch tunnel bridge ``br-tun`` wraps the packet in a VXLAN or GRE " +"tunnel and adds a tag to identify project network 1." +msgstr "" + +#: ../scenario_legacy_ovs.rst:455 +msgid "" +"The Open vSwitch integration bridge ``br-int`` replaces the actual VLAN tag " +"of project network 1 with the internal tag." +msgstr "" + +#: ../scenario_legacy_ovs.rst:467 +msgid "" +"The Open vSwitch integration bridge ``br-int`` forwards the packet to the " +"``qr-1`` interface (3) in the router namespace ``qrouter``. The ``qr-1`` " +"interface contains the project network 1 gateway IP address *TG1*." +msgstr "" + +#: ../scenario_legacy_ovs.rst:470 +msgid "" +"The router namespace ``qrouter`` routes the packet to the ``qr-2`` interface " +"(4). The ``qr-2`` interface contains the project network 2 gateway IP " +"address *TG2*." +msgstr "" + +#: ../scenario_legacy_ovs.rst:475 +msgid "" +"The Open vSwitch integration bridge ``br-int`` adds the internal tag for " +"project network 2." +msgstr "" + +#: ../scenario_legacy_ovs.rst:481 +msgid "" +"The Open vSwitch VLAN bridge ``br-vlan`` replaces the internal tag with the " +"actual VLAN tag of project network 2." +msgstr "" + +#: ../scenario_legacy_ovs.rst:483 +msgid "" +"The Open vSwitch VLAN bridge ``br-vlan`` forwards the packet to compute node " +"2 via the VLAN interface." +msgstr "" + +#: ../scenario_legacy_ovs.rst:490 +msgid "" +"The Open vSwitch tunnel bridge ``br-tun`` wraps the packet in a VXLAN or GRE " +"tunnel and adds a tag to identify project network 2." +msgstr "" + +#: ../scenario_legacy_ovs.rst:503 ../scenario_legacy_ovs.rst:590 +msgid "" +"The Open vSwitch integration bridge ``br-int`` replaces the actual VLAN tag " +"of project network 2 with the internal tag." +msgstr "" + +#: ../scenario_legacy_ovs.rst:510 ../scenario_legacy_ovs.rst:597 +msgid "" +"The Open vSwitch tunnel bridge ``br-tun`` unwraps the packet and adds the " +"internal tag for project network 2." +msgstr "" + +# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../scenario_legacy_ovs.rst:517 ../scenario_provider_ovs.rst:290 +msgid "" +"Security group rules (5) on the Linux bridge ``qbr`` handle firewalling and " +"state tracking for the packet." +msgstr "" + +# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../scenario_legacy_ovs.rst:519 ../scenario_provider_ovs.rst:292 +msgid "" +"The Linux bridge ``qbr`` forwards the packet to the ``tap`` interface (6) on " +"instance 2." +msgstr "" + +#: ../scenario_legacy_ovs.rst:549 +msgid "Both instances use the same project network." +msgstr "" + +#: ../scenario_legacy_ovs.rst:551 +msgid "The Open vSwitch agent handles switching within the project network." +msgstr "" + +#: ../scenario_legacy_ovs.rst:555 +msgid "" +"The instance 1 ``tap`` interface (1) forwards the packet to the VLAN bridge " +"``qbr``. The packet contains destination MAC address *I2* because the " +"destination resides on the same network." +msgstr "" + +#: ../scenario_legacy_ovs.rst:558 +msgid "" +"Security group rules (2) on the provider bridge ``qbr`` handle state " +"tracking for the packet." +msgstr "" + +# #-#-#-#-# scenario_legacy_ovs.pot (Networking Guide 0.9) #-#-#-#-# +# #-#-#-#-# scenario_provider_ovs.pot (Networking Guide 0.9) #-#-#-#-# +#: ../scenario_legacy_ovs.rst:562 ../scenario_provider_ovs.rst:261 +msgid "" +"The Open vSwitch integration bridge ``br-int`` adds the internal tag for " +"provider network 1." +msgstr "" + +#: ../scenario_legacy_ovs.rst:570 +msgid "" +"The Open vSwitch VLAN bridge ``br-vlan`` forwards the packet to the compute " +"node 2 via the VLAN interface." +msgstr "" + +#: ../scenario_legacy_ovs.rst:579 +msgid "" +"The Open vSwitch tunnel bridge ``br-tun`` forwards the packet to the compute " +"node 2 via the tunnel interface." +msgstr "" + +#: ../scenario_legacy_ovs.rst:604 +msgid "" +"Security group rules (3) on the Linux bridge ``qbr`` handle firewalling and " +"state tracking for the packet." +msgstr "" + +#: ../scenario_legacy_ovs.rst:606 +msgid "" +"The Linux bridge ``qbr`` forwards the packet to the ``tap`` interface (4) on " +"instance 2." +msgstr "" + +#: ../scenario_provider_ovs.rst:3 +msgid "Scenario: Provider networks with Open vSwitch" +msgstr "" + +#: ../scenario_provider_ovs.rst:5 +msgid "" +"This scenario describes a provider networks implementation of the OpenStack " +"Networking service using the ML2 plug-in with Open vSwitch (OVS)." +msgstr "" + +#: ../scenario_provider_ovs.rst:15 +msgid "" +"In many cases, operators who are already familiar with network architectures " +"that rely on the physical network infrastructure can easily deploy OpenStack " +"Networking on it. Over time, operators can test and implement cloud " +"networking features in their environment." +msgstr "" + +#: ../scenario_provider_ovs.rst:20 +msgid "" +"Before OpenStack Networking introduced Distributed Virtual Routers (DVR), " +"all network traffic traversed one or more dedicated network nodes, which " +"limited performance and reliability. Physical network infrastructures " +"typically offer better performance and reliability than general-purpose " +"hosts that handle various network operations in software." +msgstr "" + +#: ../scenario_provider_ovs.rst:43 +msgid "" +"These prerequisites define the minimum physical infrastructure and OpenStack " +"service dependencies that you need to deploy this scenario. For example, the " +"Networking service immediately depends on the Identity service and the " +"Compute service immediately depends on the Networking service. These " +"dependencies lack services such as the Image service because the Networking " +"service does not immediately depend on it. However, the Compute service " +"depends on the Image service to launch an instance. The example " +"configuration in this scenario assumes basic configuration knowledge of " +"Networking service components." +msgstr "" + +#: ../scenario_provider_ovs.rst:58 +msgid "" +"One controller node with two network interfaces: management and provider. " +"The provider interface connects to a generic network that physical network " +"infrastructure switches/routes to external networks (typically the " +"Internet). The Open vSwitch bridge ``br-provider`` must contain a port on " +"the provider network interface." +msgstr "" + +#: ../scenario_provider_ovs.rst:63 +msgid "" +"At least two compute nodes with two network interfaces: management and " +"provider. The provider interface connects to a generic network that the " +"physical network infrastructure switches/routes to external networks " +"(typically the Internet). The Open vSwitch bridge ``br-provider`` must " +"contain a port on the provider network interface." +msgstr "" + +#: ../scenario_provider_ovs.rst:89 +msgid "" +"Neutron server service, Open vSwitch service, ML2 plug-in, Open vSwitch " +"agent, DHCP agent, and any dependencies." +msgstr "" + +#: ../scenario_provider_ovs.rst:113 +msgid "" +"Open vSwitch agent managing virtual switches, connectivity among them, and " +"interaction via virtual ports with other network components such as " +"namespaces and underlying interfaces." +msgstr "" + +#: ../scenario_provider_ovs.rst:131 +msgid "" +"Open vSwitch agent managing virtual switches, connectivity among them, and " +"interaction via virtual ports with other network components such as Linux " +"bridges and underlying interfaces." +msgstr "" + +#: ../scenario_provider_ovs.rst:159 +msgid "" +"Open vSwitch uses VLANs internally to segregate networks that traverse " +"bridges. The VLAN ID usually differs from the segmentation ID of the virtual " +"network." +msgstr "" + +#: ../scenario_provider_ovs.rst:195 ../scenario_provider_ovs.rst:257 +#: ../scenario_provider_ovs.rst:329 +msgid "" +"Security group rules (2) on the Linux bridge ``qbr`` handle firewalling and " +"state tracking for the packet." +msgstr "" + +#: ../scenario_provider_ovs.rst:199 ../scenario_provider_ovs.rst:333 +msgid "" +"The Open vSwitch integration bridge ``br-int`` adds the internal tag for the " +"provider network." +msgstr "" + +#: ../scenario_provider_ovs.rst:201 ../scenario_provider_ovs.rst:263 +#: ../scenario_provider_ovs.rst:335 +msgid "" +"The Open vSwitch integration bridge ``br-int`` forwards the packet to the " +"Open vSwitch provider bridge ``br-provider``." +msgstr "" + +#: ../scenario_provider_ovs.rst:203 ../scenario_provider_ovs.rst:337 +msgid "" +"The Open vSwitch provider bridge ``br-provider`` replaces the internal tag " +"with the actual VLAN tag (segmentation ID) of the provider network." +msgstr "" + +#: ../scenario_provider_ovs.rst:205 +msgid "" +"The Open vSwitch provider bridge ``br-provider`` forwards the packet to the " +"physical network via the provider network interface." +msgstr "" + +#: ../scenario_provider_ovs.rst:212 +msgid "" +"A router (4) routes the packet from provider network 1 to the external " +"network." +msgstr "" + +#: ../scenario_provider_ovs.rst:265 +msgid "" +"The Open vSwitch provider bridge ``br-provider`` replaces the internal tag " +"with the actual VLAN tag (segmentation ID) of provider network 1." +msgstr "" + +#: ../scenario_provider_ovs.rst:267 ../scenario_provider_ovs.rst:339 +msgid "" +"The Open vSwitch VLAN bridge ``br-provider`` forwards the packet to the " +"physical network infrastructure via the provider network interface." +msgstr "" + +#: ../scenario_provider_ovs.rst:282 ../scenario_provider_ovs.rst:348 +msgid "" +"The provider network interface forwards the packet to the Open vSwitch " +"provider bridge ``br-provider``." +msgstr "" + +#: ../scenario_provider_ovs.rst:284 ../scenario_provider_ovs.rst:350 +msgid "" +"The Open vSwitch provider bridge ``br-provider`` forwards the packet to the " +"Open vSwitch integration bridge ``br-int``." +msgstr "" + +#: ../scenario_provider_ovs.rst:286 +msgid "" +"The Open vSwitch integration bridge ``br-int`` replaces the actual VLAN tag " +"(segmentation ID) of provider network 2 with the internal tag." +msgstr "" + +#: ../scenario_provider_ovs.rst:326 +msgid "" +"The instance 1 ``tap`` interface (1) forwards the packet to the Linux bridge " +"``qbr``. The packet contains destination MAC address *I2* because the " +"destination resides on the same network." +msgstr "" + +#: ../scenario_provider_ovs.rst:352 +msgid "" +"The Open vSwitch integration bridge ``br-int`` replaces the actual VLAN tag " +"(segmentation ID) of provider network 1 with the internal tag." +msgstr "" + +#: ../scenario_provider_ovs.rst:358 +msgid "" +"The Linux bridge ``qbr`` forwards the packet to the ``tap`` interface (5) on " +"instance 2." +msgstr "" + +#: ../scenario_provider_ovs.rst:409 +msgid "" +"Configure the ML2 plug-in and Open vSwitch agent. Edit the :file:`/etc/" +"neutron/plugins/ml2/ml2_conf.ini` file:" +msgstr "" + +#: ../scenario_provider_ovs.rst:452 ../scenario_provider_ovs.rst:515 +msgid "Start the following service:" +msgstr "" + +#: ../scenario_provider_ovs.rst:456 ../scenario_provider_ovs.rst:519 +msgid "Create the Open vSwitch provider bridge ``br-provider``:" +msgstr "" + +#: ../scenario_provider_ovs.rst:462 ../scenario_provider_ovs.rst:525 +msgid "" +"Add the provider network interface as a port on the Open vSwitch provider " +"bridge ``br-provider``:" msgstr "" diff --git a/doc/user-guide-admin/source/locale/ja/LC_MESSAGES/user-guide-admin.po b/doc/user-guide-admin/source/locale/ja/LC_MESSAGES/user-guide-admin.po index 81e2ce264d..d6d55397f5 100644 --- a/doc/user-guide-admin/source/locale/ja/LC_MESSAGES/user-guide-admin.po +++ b/doc/user-guide-admin/source/locale/ja/LC_MESSAGES/user-guide-admin.po @@ -17,11 +17,11 @@ msgid "" msgstr "" "Project-Id-Version: Admin User Guide 1.0.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2015-10-04 00:26+0000\n" +"POT-Creation-Date: 2015-10-08 06:01+0000\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" -"PO-Revision-Date: 2015-10-04 12:35+0000\n" +"PO-Revision-Date: 2015-10-07 12:32+0000\n" "Last-Translator: KATO Tomoyuki \n" "Language-Team: Japanese (http://www.transifex.com/openstack/openstack-" "manuals-i18n/language/ja/)\n" @@ -50,6 +50,9 @@ msgstr "**暗号化オプション**" msgid "**Ephemeral Disk GB**" msgstr "**一時ディスク GB**" +msgid "**Figure Dashboard—Create Image**" +msgstr "**図 Dashboard—イメージの作成**" + msgid "**Figure Dashboard—Instance Actions**" msgstr "**図 ダッシュボード—インスタンスの操作**" @@ -315,6 +318,21 @@ msgstr "管理ユーザーは、Block Storage のクォータを編集、更新 msgid "Administrative users can view Block Storage service quotas." msgstr "管理ユーザーは、Block Storage のクォータを表示できます。" +msgid "" +"Administrators use templates to create stacks, which are collections of " +"resources. For example, a stack might include instances, floating IPs, " +"volumes, security groups, or users. The Orchestration service offers access " +"to all OpenStack core services via a single modular template, with " +"additional orchestration capabilities such as auto-scaling and basic high " +"availability." +msgstr "" +"管理者は、スタックを作成するためにテンプレートを使用します。これは、リソース" +"のコレクションです。例えば、スタックはインスタンス、Floating IP、ボリューム、" +"セキュリティグループ、ユーザーを含むでしょう。Orchestration は、オートスケー" +"ルや基本的な高可用性などのオーケストレーションの追加機能とともに、単一のモ" +"ジュール型テンプレート経由で OpenStack のコアサービスへのアクセスを提供しま" +"す。" + msgid "" "After ``awk`` processes the output, it pipes it to ``sort`` and ``uniq -c`` " "to sum up the number of occurrences for each request type and return code " @@ -547,14 +565,6 @@ msgstr "" "場所` の項目が表示されます。場所の URL を指定したり、お使いのファイルシステム" "にあるイメージファイルを参照して追加したりできます。" -msgid "" -"Basic creation and deletion of Orchestration stacks, refer to the `OpenStack " -"End User Guide `_" -msgstr "" -"基本的な Orchestration スタックの作成や削除は `OpenStack End User Guide " -"`_ を参照してくだ" -"さい。" - msgid "Basic quota configuration" msgstr "基本的なクォータ設定" @@ -653,17 +663,16 @@ msgstr ":guilabel:`フレーバーの作成` をクリックします。" msgid "Click :guilabel:`Create Host Aggregate`." msgstr ":guilabel:`ホストアグリゲートの作成` をクリックします。" +msgid "" +"Click :guilabel:`Create Image`, which opens the :guilabel:`Create An Image` " +"window." +msgstr "" +":guilabel:`イメージの作成` をクリックします。これにより、:guilabel:`イメージ" +"の作成` ウィンドウが開きます。" + msgid "Click :guilabel:`Create Image`." msgstr ":guilabel:`イメージの作成` をクリックします。" -msgid "" -"Click :guilabel:`Create Snapshot`. The dashboard shows the instance snapshot " -"in the :guilabel:`Images & Snapshots` category." -msgstr "" -":guilabel:`スナップショットの作成` をクリックします。ダッシュボードの:" -"guilabel:`イメージとスナップショット` カテゴリーにインスタンスのスナップ" -"ショットが表示されます。" - msgid "Click :guilabel:`Create Volume Type Encryption`." msgstr ":guilabel:`ボリューム種別の暗号化設定の作成` をクリックします。" @@ -671,13 +680,6 @@ msgid "Click :guilabel:`Create Volume Type` button to confirm your changes." msgstr "" ":guilabel:`ボリューム種別の作成` ボタンをクリックして、変更内容を確認します。" -msgid "" -"Click :guilabel:`Create Volume Type` button. In the :guilabel:`Create Volume " -"Type` window, enter a name for the volume type." -msgstr "" -":guilabel:`ボリューム種別の作成` ボタンをクリックします。:guilabel:`ボリュー" -"ム種別の作成` ウィンドウで、ボリューム種別の名前を入力します。" - msgid "Click :guilabel:`Delete Flavors`." msgstr ":guilabel:`フレーバーの削除` をクリックします。" @@ -716,6 +718,22 @@ msgstr ":guilabel:`デフォルトの更新` ボタンをクリックします msgid "Click the :guilabel:`Update Role` button to confirm your changes." msgstr ":guilabel:`ロールの更新` ボタンをクリックして、変更内容を確認します。" +msgid "" +"Click the :guilabel:`Volume Types` tab, and click :guilabel:`Create Volume " +"Type` button. In the :guilabel:`Create Volume Type` window, enter a name for " +"the volume type." +msgstr "" +":guilabel:`ボリューム種別` タブをクリックし、:guilabel:`ボリューム種別の作成" +"` ボタンをクリックします。:guilabel:`ボリューム種別の作成` ウィンドウで、ボ" +"リューム種別の名前を入力します。" + +msgid "" +"Click the :guilabel:`Volume Types` tab, select the volume type or types that " +"you want to delete." +msgstr "" +":guilabel:`ボリューム種別` タブをクリックし、削除したいボリューム種別を選択し" +"ます。" + msgid "Click the:" msgstr "以下をクリックします。" @@ -1127,11 +1145,8 @@ msgstr "" "`__ を参照" "してください。" -msgid "For information about the:" -msgstr "詳細は以下のとおりです。" - msgid "" -"For information about using the dashboard to launch instances as an end " +"For information about using the Dashboard to launch instances as an end " "user, see the `OpenStack End User Guide `__." msgstr "" @@ -1337,13 +1352,6 @@ msgstr "" "guilabel:`フレーバーの削除` をクリックします。この操作を取り消すことはできま" "せん。" -msgid "" -"In the :guilabel:`Confirm Delete Image` window, click :guilabel:`Delete " -"Images` to confirm the deletion." -msgstr "" -":guilabel:`イメージの削除の確認` ウィンドウで、:guilabel:`イメージの削除` を" -"クリックして削除を確定します。" - msgid "" "In the :guilabel:`Confirm Delete Roles` window, click :guilabel:`Delete " "Roles` to confirm the deletion." @@ -1588,6 +1596,27 @@ msgstr "ユーザーを一覧表示して、ロールを割り当てたいユー msgid "Lists defined quotas for all tenants" msgstr "全テナントに対して定義済みのクォータを表示します。 " +msgid "" +"Log in to the Dashboard and choose the admin project from the CURRENT " +"PROJECT drop-down list." +msgstr "" +"ダッシュボードにログインし、現在のプロジェクト ドロップダウンリストから " +"admin プロジェクトを選択します。" + +msgid "" +"Log in to the Dashboard and choose the admin project from the drop-down list " +"at the top of the page." +msgstr "" +"ダッシュボードにログインし、ページの上部にあるドロップダウンリストから admin " +"プロジェクトを選択します。" + +msgid "" +"Log in to the Dashboard. Choose the :guilabel:`admin` project from the drop-" +"down list at the top of the page." +msgstr "" +"ダッシュボードにログインします。ページの上部にあるドロップダウンリストから :" +"guilabel:`admin` プロジェクトを選択します。" + msgid "" "Log in to the OpenStack dashboard and choose the :guilabel:`admin` project " "from the drop-down list at the top of the page." @@ -1615,20 +1644,6 @@ msgstr "" "ダッシュボードにログインし、ページの上部にあるドロップダウンリストから :" "guilabel:`admin` プロジェクトを選択します。" -msgid "" -"Log in to the dashboard and choose the admin project from the CURRENT " -"PROJECT drop-down list." -msgstr "" -"ダッシュボードにログインし、現在のプロジェクト ドロップダウンリストから " -"admin プロジェクトを選択します。" - -msgid "" -"Log in to the dashboard and choose the admin project from the drop-down list " -"at the top of the page." -msgstr "" -"ダッシュボードにログインし、ページの上部にあるドロップダウンリストから admin " -"プロジェクトを選択します。" - # #-#-#-#-# dashboard_manage_flavors.pot (Admin User Guide 1.0.0) #-#-#-#-# # #-#-#-#-# dashboard_manage_host_aggregates.pot (Admin User Guide 1.0.0) # #-#-#-#-# @@ -2141,9 +2156,6 @@ msgstr "イメージの形式を選択します。" msgid "Select the images that you want to delete." msgstr "削除したいイメージを選択します。" -msgid "Select the images that you want to edit. Click :guilabel:`Edit`." -msgstr "編集したいイメージを選択します。:guilabel:`編集` をクリックします。" - msgid "Select the instance for which you want to change the state." msgstr "状態を変更したいインスタンスを選択します。" @@ -2156,9 +2168,6 @@ msgstr "" msgid "Select the volume or volumes that you want to delete." msgstr "削除したいボリュームを選択します。" -msgid "Select the volume type or types that you want to delete." -msgstr "削除したいボリューム種別を選択します。" - msgid "" "Select this option to ensure that only users with permissions can delete it." msgstr "" @@ -2305,6 +2314,17 @@ msgstr "" "トレージ、ネットワーク、インスタンス、アプリケーションなどのクラウドインフラ" "ストラクチャーリソースを作成および管理するために使用できます。" +msgid "" +"The Orchestration service provides a template-based orchestration engine for " +"the OpenStack cloud. Orchestration services create and manage cloud " +"infrastructure resources such as storage, networking, instances, and " +"applications as a repeatable running environment." +msgstr "" +"Orchestration により、OpenStack クラウドに対して、テンプレートによるオーケス" +"トレーションエンジンが提供されます。これは、繰り返し実行可能な環境として、ス" +"トレージ、ネットワーク、インスタンス、アプリケーションなどのクラウドインフラ" +"ストラクチャーリソースを作成および管理します。" + msgid "" "The Telemetry module provides user-level usage data for OpenStack-based " "clouds, which can be used for customer billing, system monitoring, or " @@ -2458,7 +2478,7 @@ msgstr "" msgid "" "There are no administration-specific tasks that can be done through the " -"dashboard." +"Dashboard." msgstr "ダッシュボードから実行できる、管理者固有の作業はありません。" msgid "" @@ -2654,17 +2674,6 @@ msgstr "無効化したユーザーアカウントを有効化する方法:" msgid "To get details for a service, run this command::" msgstr "サービスの詳細を取得するために、このコマンドを実行します。" -msgid "" -"To launch an instance from the snapshot, select the snapshot and click " -"Launch. For information about launching instances, see the `OpenStack End " -"User Guide `__." -msgstr "" -"スナップショットからインスタンスを起動するために、スナップショットを選択し、" -"起動をクリックします。インスタンスの起動方法は、`OpenStack エンドユーザーガイ" -"ド `__ " -"を参照してください。" - msgid "To list all floating IP addresses for all projects, run::" msgstr "" "全プロジェクトのすべての Floating IP アドレスを一覧表示するために、以下を実行" @@ -3333,6 +3342,14 @@ msgstr "aes-xts-plain64 (推奨)" msgid "back-end" msgstr "バックエンド" +msgid "" +"basic creation and deletion of Orchestration stacks, refer to the `OpenStack " +"End User Guide `_" +msgstr "" +"基本的な Orchestration スタックの作成や削除は `OpenStack End User Guide " +"`_ を参照してくだ" +"さい。" + msgid "cores" msgstr "cores" diff --git a/doc/user-guide-admin/source/locale/user-guide-admin.pot b/doc/user-guide-admin/source/locale/user-guide-admin.pot index 39ed50cad1..d15dec795d 100644 --- a/doc/user-guide-admin/source/locale/user-guide-admin.pot +++ b/doc/user-guide-admin/source/locale/user-guide-admin.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Admin User Guide 1.0.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2015-10-04 06:17+0000\n" +"POT-Creation-Date: 2015-10-08 06:31+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -16,80 +16,279 @@ msgstr "" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" -#: ../dashboard_manage_flavors.rst:129 -msgid "**Bandwidth I/O**" +#: ../analyzing-log-files-with-swift-cli.rst:3 +msgid "Analyze log files" msgstr "" -#: ../cli_cinder_quotas.rst:9 -msgid "**Block Storage quotas**" +#: ../analyzing-log-files-with-swift-cli.rst:5 +msgid "Use the swift command-line client to analyze log files." msgstr "" -#: ../dashboard_manage_flavors.rst:107 -msgid "**CPU limits**" +#: ../analyzing-log-files-with-swift-cli.rst:7 +msgid "The swift client is simple to use, scalable, and flexible." msgstr "" -#: ../cli_set_compute_quotas.rst:10 -msgid "**Compute quota descriptions**" +#: ../analyzing-log-files-with-swift-cli.rst:9 +msgid "" +"Use the swift client ``-o`` or ``-output`` option to get short answers to " +"questions about logs." msgstr "" -#: ../dashboard_manage_flavors.rst:117 -msgid "**Disk tuning**" +#: ../analyzing-log-files-with-swift-cli.rst:12 +msgid "" +"You can use the ``-o`` or ``--output`` option with a single object download " +"to redirect the command output to a specific file or to STDOUT (``-``). The " +"ability to redirect the output to STDOUT enables you to pipe (``|``) data " +"without saving it to disk first." msgstr "" -#: ../dashboard_manage_volumes.rst:61 -msgid "**Encryption Options**" +#: ../analyzing-log-files-with-swift-cli.rst:18 +msgid "Upload and analyze log files" msgstr "" -#: ../dashboard_manage_flavors.rst:46 -msgid "**Ephemeral Disk GB**" +#: ../analyzing-log-files-with-swift-cli.rst:20 +msgid "" +"This example assumes that ``logtest`` directory contains the following log " +"files::" msgstr "" -#: ../dashboard_manage_instances.rst:54 -msgid "**Figure Dashboard—Instance Actions**" +#: ../analyzing-log-files-with-swift-cli.rst:29 +msgid "Each file uses the following line format::" msgstr "" -#: ../dashboard_manage_flavors.rst:34 -msgid "**Flavor info tab**" +#: ../analyzing-log-files-with-swift-cli.rst:35 +msgid "Change into the ``logtest`` directory::" msgstr "" -#: ../dashboard_manage_flavors.rst:38 -msgid "**ID**" +#: ../analyzing-log-files-with-swift-cli.rst:39 +msgid "Upload the log files into the ``logtest`` container::" msgstr "" -#: ../dashboard_manage_flavors.rst:37 -msgid "**Name**" +#: ../analyzing-log-files-with-swift-cli.rst:50 +msgid "Get statistics for the account::" msgstr "" -#: ../dashboard_manage_flavors.rst:102 -msgid "**Optional metadata keys**" +#: ../analyzing-log-files-with-swift-cli.rst:62 +msgid "Get statistics for the logtest container::" msgstr "" -#: ../dashboard_set_quotas.rst:33 -msgid "**Quota Descriptions**" +#: ../analyzing-log-files-with-swift-cli.rst:76 +msgid "List all objects in the logtest container::" msgstr "" -#: ../dashboard_manage_flavors.rst:41 -msgid "**RAM MB**" +#: ../analyzing-log-files-with-swift-cli.rst:89 +msgid "Download and analyze an object" msgstr "" -#: ../dashboard_manage_flavors.rst:143 -msgid "**Random-number generator**" +#: ../analyzing-log-files-with-swift-cli.rst:91 +msgid "" +"This example uses the ``-o`` option and a hyphen (``-``) to get information " +"about an object." msgstr "" -#: ../dashboard_manage_flavors.rst:43 -msgid "**Root Disk GB**" +#: ../analyzing-log-files-with-swift-cli.rst:94 +msgid "" +"Use the swift ``download`` command to download the object. On this command, " +"stream the output to ``awk`` to break down requests by return code and the " +"date ``2200 on November 16th, 2010``." msgstr "" -#: ../dashboard_manage_flavors.rst:57 -msgid "**Swap Disk MB**" +#: ../analyzing-log-files-with-swift-cli.rst:98 +msgid "" +"Using the log line format, find the request type in column 9 and the return " +"code in column 12." msgstr "" -#: ../dashboard_manage_flavors.rst:39 -msgid "**VCPUs**" +#: ../analyzing-log-files-with-swift-cli.rst:101 +msgid "" +"After ``awk`` processes the output, it pipes it to ``sort`` and ``uniq -c`` " +"to sum up the number of occurrences for each request type and return code " +"combination." msgstr "" -#: ../dashboard_manage_flavors.rst:139 -msgid "**Watchdog behavior**" +#: ../analyzing-log-files-with-swift-cli.rst:105 +msgid "Download an object::" +msgstr "" + +#: ../analyzing-log-files-with-swift-cli.rst:144 +msgid "Discover how many PUT requests are in each log file." +msgstr "" + +#: ../analyzing-log-files-with-swift-cli.rst:146 +msgid "" +"Use a bash for loop with awk and swift with the ``-o`` or ``--output`` " +"option and a hyphen (``-``) to discover how many PUT requests are in each " +"log file." +msgstr "" + +#: ../analyzing-log-files-with-swift-cli.rst:150 +msgid "" +"Run the swift ``list`` command to list objects in the logtest container. " +"Then, for each item in the list, run the swift ``download -o -`` command. " +"Pipe the output into grep to filter the PUT requests. Finally, pipe into " +"``wc -l`` to count the lines." +msgstr "" + +#: ../analyzing-log-files-with-swift-cli.rst:171 +msgid "List the object names that begin with a specified string." +msgstr "" + +#: ../analyzing-log-files-with-swift-cli.rst:173 +msgid "" +"Run the swift ``list -p 2010-11-15`` command to list objects in the logtest " +"container that begin with the ``2010-11-15`` string." +msgstr "" + +#: ../analyzing-log-files-with-swift-cli.rst:176 +msgid "For each item in the list, run the swift **download -o -** command." +msgstr "" + +#: ../analyzing-log-files-with-swift-cli.rst:178 +msgid "" +"Pipe the output to **grep** and **wc**. Use the **echo** command to display " +"the object name::" +msgstr "" + +#: ../cli.rst:3 +msgid "OpenStack command-line clients" +msgstr "" + +#: ../cli_admin_manage_environment.rst:3 +msgid "Manage the OpenStack environment" +msgstr "" + +#: ../cli_admin_manage_environment.rst:5 +msgid "This section includes tasks specific to the OpenStack environment." +msgstr "" + +#: ../cli_admin_manage_ip_addresses.rst:3 +msgid "Manage IP addresses" +msgstr "" + +#: ../cli_admin_manage_ip_addresses.rst:5 +msgid "" +"Each instance has a private, fixed IP address (assigned when launched) and " +"can also have a public, or floating, address. Private IP addresses are used " +"for communication between instances, and public addresses are used for " +"communication with networks outside the cloud, including the Internet." +msgstr "" + +#: ../cli_admin_manage_ip_addresses.rst:11 +msgid "" +"By default, both administrative and end users can associate floating IP " +"addresses with projects and instances. You can change user permissions for " +"managing IP addresses by updating the ``/etc/nova/policy.json`` file. For " +"basic floating-IP procedures, refer to the *Manage IP Addresses* section in " +"the `OpenStack End User Guide `_." +msgstr "" + +#: ../cli_admin_manage_ip_addresses.rst:17 +msgid "" +"For details on creating public networks using OpenStack Networking " +"(``neutron``), refer to the `OpenStack Cloud Administrator Guide `_ . No " +"floating IP addresses are created by default in OpenStack Networking." +msgstr "" + +#: ../cli_admin_manage_ip_addresses.rst:22 +msgid "" +"As an administrator using legacy networking (``nova-network``), you can use " +"the following bulk commands to list, create, and delete ranges of floating " +"IP addresses. These addresses can then be associated with instances by end " +"users." +msgstr "" + +#: ../cli_admin_manage_ip_addresses.rst:28 +msgid "List addresses for all projects" +msgstr "" + +#: ../cli_admin_manage_ip_addresses.rst:29 +msgid "To list all floating IP addresses for all projects, run::" +msgstr "" + +#: ../cli_admin_manage_ip_addresses.rst:58 +msgid "Bulk create floating IP addresses" +msgstr "" + +#: ../cli_admin_manage_ip_addresses.rst:59 +msgid "To create a range of floating IP addresses, run::" +msgstr "" + +# #-#-#-#-# cli_admin_manage_ip_addresses.pot (Admin User Guide 1.0.0) #-#-#-#-# +# #-#-#-#-# cli_nova_specify_host.pot (Admin User Guide 1.0.0) #-#-#-#-# +# #-#-#-#-# cli_set_compute_quotas.pot (Admin User Guide 1.0.0) #-#-#-#-# +#: ../cli_admin_manage_ip_addresses.rst:63 +#: ../cli_admin_manage_ip_addresses.rst:89 ../cli_nova_specify_host.rst:13 +#: ../cli_set_compute_quotas.rst:53 ../cli_set_compute_quotas.rst:77 +#: ../cli_set_compute_quotas.rst:92 ../cli_set_compute_quotas.rst:122 +#: ../cli_set_compute_quotas.rst:163 ../cli_set_compute_quotas.rst:197 +msgid "For example::" +msgstr "" + +#: ../cli_admin_manage_ip_addresses.rst:67 +msgid "" +"By default, **floating-ip-bulk-create** uses the ``public`` pool and " +"``eth0`` interface values." +msgstr "" + +#: ../cli_admin_manage_ip_addresses.rst:70 +msgid "" +"You should use a range of free IP addresses that is correct for your " +"network. If you are not sure, at least try to avoid the DHCP address range:" +msgstr "" + +#: ../cli_admin_manage_ip_addresses.rst:74 +msgid "" +"Pick a small range (/29 gives an 8 address range, 6 of which will be usable)." +msgstr "" + +#: ../cli_admin_manage_ip_addresses.rst:77 +msgid "" +"Use **nmap** to check a range's availability. For example, 192.168.1.56/29 " +"represents a small range of addresses (192.168.1.56-63, with 57-62 usable), " +"and you could run the command **nmap -sn 192.168.1.56/29** to check whether " +"the entire range is currently unused." +msgstr "" + +#: ../cli_admin_manage_ip_addresses.rst:84 +msgid "Bulk delete floating IP addresses" +msgstr "" + +#: ../cli_admin_manage_ip_addresses.rst:85 +msgid "To delete a range of floating IP addresses, run::" +msgstr "" + +#: ../cli_admin_manage_stacks.rst:3 +msgid "Launch and manage stacks using the CLI" +msgstr "" + +#: ../cli_admin_manage_stacks.rst:5 +msgid "" +"The Orchestration service provides a template-based orchestration engine for " +"the OpenStack cloud, which can be used to create and manage cloud " +"infrastructure resources such as storage, networking, instances, and " +"applications as a repeatable running environment." +msgstr "" + +#: ../cli_admin_manage_stacks.rst:11 +msgid "" +"Templates are used to create stacks, which are collections of resources. For " +"example, a stack might include instances, floating IPs, volumes, security " +"groups, or users. The Orchestration service offers access to all OpenStack " +"core services via a single modular template, with additional orchestration " +"capabilities such as auto-scaling and basic high availability." +msgstr "" + +# #-#-#-#-# cli_admin_manage_stacks.pot (Admin User Guide 1.0.0) #-#-#-#-# +# #-#-#-#-# dashboard_admin_manage_stacks.pot (Admin User Guide 1.0.0) #-#-#-#-# +#: ../cli_admin_manage_stacks.rst:19 ../dashboard_admin_manage_stacks.rst:20 +msgid "For information about:" +msgstr "" + +#: ../cli_admin_manage_stacks.rst:21 +msgid "" +"basic creation and deletion of Orchestration stacks, refer to the `OpenStack " +"End User Guide `_" msgstr "" #: ../cli_admin_manage_stacks.rst:24 @@ -98,6 +297,354 @@ msgid "" "`_" msgstr "" +#: ../cli_admin_manage_stacks.rst:26 +msgid "" +"As an administrator, you can also carry out stack functions on behalf of " +"your users. For example, to resume, suspend, or delete a stack, run:" +msgstr "" + +#: ../cli_cinder_quotas.rst:3 +msgid "Manage Block Storage service quotas" +msgstr "" + +#: ../cli_cinder_quotas.rst:5 +msgid "" +"As an administrative user, you can update the OpenStack Block Storage " +"service quotas for a project. You can also update the quota defaults for a " +"new project." +msgstr "" + +#: ../cli_cinder_quotas.rst:9 +msgid "**Block Storage quotas**" +msgstr "" + +# #-#-#-#-# cli_cinder_quotas.pot (Admin User Guide 1.0.0) #-#-#-#-# +# #-#-#-#-# dashboard_set_quotas.pot (Admin User Guide 1.0.0) #-#-#-#-# +#: ../cli_cinder_quotas.rst:12 ../dashboard_set_quotas.rst:36 +msgid "Defines the number of" +msgstr "" + +#: ../cli_cinder_quotas.rst:12 +msgid "Property name" +msgstr "" + +#: ../cli_cinder_quotas.rst:14 +msgid "Volume gigabytes allowed for each tenant." +msgstr "" + +#: ../cli_cinder_quotas.rst:14 +msgid "gigabytes" +msgstr "" + +#: ../cli_cinder_quotas.rst:15 +msgid "Volume snapshots allowed for each tenant." +msgstr "" + +#: ../cli_cinder_quotas.rst:15 +msgid "snapshots" +msgstr "" + +#: ../cli_cinder_quotas.rst:16 +msgid "Volumes allowed for each tenant." +msgstr "" + +#: ../cli_cinder_quotas.rst:16 +msgid "volumes" +msgstr "" + +#: ../cli_cinder_quotas.rst:20 +msgid "View Block Storage quotas" +msgstr "" + +#: ../cli_cinder_quotas.rst:22 +msgid "Administrative users can view Block Storage service quotas." +msgstr "" + +#: ../cli_cinder_quotas.rst:24 +msgid "List the default quotas for all projects:" +msgstr "" + +#: ../cli_cinder_quotas.rst:37 +msgid "View Block Storage service quotas for a project::" +msgstr "" + +# #-#-#-#-# cli_cinder_quotas.pot (Admin User Guide 1.0.0) #-#-#-#-# +# #-#-#-#-# cli_keystone_manage_services.pot (Admin User Guide 1.0.0) #-#-#-#-# +# #-#-#-#-# nova_cli_manage_projects_security.pot (Admin User Guide 1.0.0) #-#-#-#-# +#: ../cli_cinder_quotas.rst:41 ../cli_cinder_quotas.rst:92 +#: ../cli_keystone_manage_services.rst:88 +#: ../cli_keystone_manage_services.rst:145 +#: ../nova_cli_manage_projects_security.rst:67 +#: ../nova_cli_manage_projects_security.rst:103 +#: ../nova_cli_manage_projects_security.rst:172 +#: ../nova_cli_manage_projects_security.rst:195 +msgid "For example:" +msgstr "" + +#: ../cli_cinder_quotas.rst:54 +msgid "Show the current usage of a per-tenant quota:" +msgstr "" + +#: ../cli_cinder_quotas.rst:68 +msgid "Edit and update Block Storage service quotas" +msgstr "" + +#: ../cli_cinder_quotas.rst:70 +msgid "Administrative users can edit and update Block Storage service quotas." +msgstr "" + +#: ../cli_cinder_quotas.rst:73 ../cli_cinder_quotas.rst:106 +msgid "Clear per-tenant quota limits::" +msgstr "" + +#: ../cli_cinder_quotas.rst:77 +msgid "" +"To update a default value for a new project, update the property in the :" +"guilabel:`cinder.quota` section of the :file:`/etc/cinder/cinder.conf` file. " +"For more information, see the `Block Storage Configuration Reference `_." +msgstr "" + +#: ../cli_cinder_quotas.rst:83 +msgid "" +"To update Block Storage service quotas, place the tenant ID in a variable::" +msgstr "" + +#: ../cli_cinder_quotas.rst:88 +msgid "Update a particular quota value::" +msgstr "" + +#: ../cli_keystone_manage_services.rst:3 +msgid "Create and manage services and service users" +msgstr "" + +#: ../cli_keystone_manage_services.rst:4 +msgid "The Identity Service enables you to define services, as follows:" +msgstr "" + +#: ../cli_keystone_manage_services.rst:7 +msgid "" +"Service catalog template. The Identity Service acts as a service catalog of " +"endpoints for other OpenStack services. The :file:`etc/default_catalog." +"templates` template file defines the endpoints for services. When the " +"Identity Service uses a template file back end, any changes that are made to " +"the endpoints are cached. These changes do not persist when you restart the " +"service or reboot the machine." +msgstr "" + +#: ../cli_keystone_manage_services.rst:15 +msgid "" +"An SQL back end for the catalog service. When the Identity Service is " +"online, you must add the services to the catalog. When you deploy a system " +"for production, use the SQL back end." +msgstr "" + +#: ../cli_keystone_manage_services.rst:20 +msgid "" +"The ``auth_token`` middleware supports the use of either a shared secret or " +"users for each service." +msgstr "" + +#: ../cli_keystone_manage_services.rst:24 +msgid "" +"To authenticate users against the Identity Service, you must create a " +"service user for each OpenStack service. For example, create a service user " +"for the Compute, Block Storage, and Networking services." +msgstr "" + +#: ../cli_keystone_manage_services.rst:29 +msgid "" +"To configure the OpenStack services with service users, create a project for " +"all services and create users for each service. Assign the admin role to " +"each service user and project pair. This role enables users to validate " +"tokens and authenticate and authorize other user requests." +msgstr "" + +#: ../cli_keystone_manage_services.rst:36 +msgid "Create a service" +msgstr "" + +#: ../cli_keystone_manage_services.rst:38 +msgid "List the available services:" +msgstr "" + +#: ../cli_keystone_manage_services.rst:57 +msgid "To create a service, run this command::" +msgstr "" + +#: ../cli_keystone_manage_services.rst:62 +msgid "``service_name``: the unique name of the new service." +msgstr "" + +#: ../cli_keystone_manage_services.rst:63 +msgid "" +"``service_type``: the service type, such as ``identity``, ``compute``, " +"``network``, ``image``, ``object-store`` or any other service identifier " +"string." +msgstr "" + +#: ../cli_keystone_manage_services.rst:66 +msgid "The arguments are:" +msgstr "" + +#: ../cli_keystone_manage_services.rst:66 +msgid "``service_description``: the description of the service." +msgstr "" + +#: ../cli_keystone_manage_services.rst:68 +msgid "" +"For example, to create a ``swift`` service of type ``object-store``, run " +"this command:" +msgstr "" + +#: ../cli_keystone_manage_services.rst:84 +msgid "To get details for a service, run this command::" +msgstr "" + +#: ../cli_keystone_manage_services.rst:104 +msgid "Create service users" +msgstr "" + +#: ../cli_keystone_manage_services.rst:106 +msgid "" +"Create a project for the service users. Typically, this project is named " +"``service``, but choose any name you like::" +msgstr "" + +#: ../cli_keystone_manage_services.rst:123 +msgid "Create service users for the relevant services for your deployment." +msgstr "" + +#: ../cli_keystone_manage_services.rst:126 +msgid "Assign the admin role to the user-project pair::" +msgstr "" + +#: ../cli_keystone_manage_services.rst:140 +msgid "Delete a service" +msgstr "" + +#: ../cli_keystone_manage_services.rst:141 +msgid "To delete a specified service, specify its ID::" +msgstr "" + +# #-#-#-#-# cli_manage_flavors.pot (Admin User Guide 1.0.0) #-#-#-#-# +# #-#-#-#-# dashboard_manage_flavors.pot (Admin User Guide 1.0.0) #-#-#-#-# +#: ../cli_manage_flavors.rst:3 ../dashboard_manage_flavors.rst:3 +msgid "Manage flavors" +msgstr "" + +#: ../cli_manage_flavors.rst:5 +msgid "" +"In OpenStack, flavors define the compute, memory, and storage capacity of " +"nova computing instances. To put it simply, a flavor is an available " +"hardware configuration for a server. It defines the \"size\" of a virtual " +"server that can be launched." +msgstr "" + +#: ../cli_manage_flavors.rst:12 +msgid "" +"Flavors can also determine on which compute host a flavor can be used to " +"launch an instance. For information about customizing flavors, refer to the " +"`OpenStack Cloud Administrator Guide `_." +msgstr "" + +#: ../cli_manage_flavors.rst:17 +msgid "A flavor consists of the following parameters:" +msgstr "" + +#: ../cli_manage_flavors.rst:20 +msgid "" +"Automatically generated by OpenStack. For private flavors, a value from 1 to " +"255." +msgstr "" + +#: ../cli_manage_flavors.rst:21 +msgid "Flavor ID" +msgstr "" + +#: ../cli_manage_flavors.rst:24 +msgid "Name" +msgstr "" + +#: ../cli_manage_flavors.rst:24 +msgid "Name for the new flavor." +msgstr "" + +#: ../cli_manage_flavors.rst:27 +msgid "Number of virtual CPUs to use." +msgstr "" + +# #-#-#-#-# cli_manage_flavors.pot (Admin User Guide 1.0.0) #-#-#-#-# +# #-#-#-#-# dashboard_manage_flavors.pot (Admin User Guide 1.0.0) #-#-#-#-# +# #-#-#-#-# dashboard_set_quotas.pot (Admin User Guide 1.0.0) #-#-#-#-# +#: ../cli_manage_flavors.rst:27 ../cli_manage_flavors.rst:53 +#: ../dashboard_manage_flavors.rst:12 ../dashboard_set_quotas.rst:67 +msgid "VCPUs" +msgstr "" + +#: ../cli_manage_flavors.rst:30 +msgid "Amount of RAM to use (in megabytes)." +msgstr "" + +#: ../cli_manage_flavors.rst:30 +msgid "Memory MB" +msgstr "" + +#: ../cli_manage_flavors.rst:33 +msgid "Amount of disk space (in gigabytes) to use for the root (/) partition." +msgstr "" + +#: ../cli_manage_flavors.rst:34 +msgid "Root Disk GB" +msgstr "" + +#: ../cli_manage_flavors.rst:37 +msgid "" +"Amount of disk space (in gigabytes) to use for the ephemeral partition. If " +"unspecified, the value is 0 by default. Ephemeral disks offer machine local " +"disk storage linked to the life cycle of a VM instance. When a VM is " +"terminated, all data on the ephemeral disk is lost. Ephemeral disks are not " +"included in any snapshots." +msgstr "" + +#: ../cli_manage_flavors.rst:44 +msgid "Ephemeral Disk GB" +msgstr "" + +#: ../cli_manage_flavors.rst:47 +msgid "" +"Amount of swap space (in megabytes) to use. If unspecified, the value is 0 " +"by default." +msgstr "" + +#: ../cli_manage_flavors.rst:48 +msgid "Swap" +msgstr "" + +#: ../cli_manage_flavors.rst:50 +msgid "The default flavors are:" +msgstr "" + +# #-#-#-#-# cli_manage_flavors.pot (Admin User Guide 1.0.0) #-#-#-#-# +# #-#-#-#-# dashboard_manage_flavors.pot (Admin User Guide 1.0.0) #-#-#-#-# +#: ../cli_manage_flavors.rst:53 ../dashboard_manage_flavors.rst:12 +msgid "Disk (in GB)" +msgstr "" + +# #-#-#-#-# cli_manage_flavors.pot (Admin User Guide 1.0.0) #-#-#-#-# +# #-#-#-#-# dashboard_manage_flavors.pot (Admin User Guide 1.0.0) #-#-#-#-# +#: ../cli_manage_flavors.rst:53 ../dashboard_manage_flavors.rst:12 +msgid "Flavor" +msgstr "" + +# #-#-#-#-# cli_manage_flavors.pot (Admin User Guide 1.0.0) #-#-#-#-# +# #-#-#-#-# dashboard_manage_flavors.pot (Admin User Guide 1.0.0) #-#-#-#-# +#: ../cli_manage_flavors.rst:53 ../dashboard_manage_flavors.rst:12 +msgid "RAM (in MB)" +msgstr "" + # #-#-#-#-# cli_manage_flavors.pot (Admin User Guide 1.0.0) #-#-#-#-# # #-#-#-#-# dashboard_manage_flavors.pot (Admin User Guide 1.0.0) #-#-#-#-# #: ../cli_manage_flavors.rst:55 ../cli_manage_flavors.rst:56 @@ -107,20 +654,14 @@ msgstr "" # #-#-#-#-# cli_manage_flavors.pot (Admin User Guide 1.0.0) #-#-#-#-# # #-#-#-#-# dashboard_manage_flavors.pot (Admin User Guide 1.0.0) #-#-#-#-# -#: ../cli_manage_flavors.rst:59 ../dashboard_manage_flavors.rst:18 -msgid "160" +#: ../cli_manage_flavors.rst:55 ../dashboard_manage_flavors.rst:14 +msgid "512" msgstr "" # #-#-#-#-# cli_manage_flavors.pot (Admin User Guide 1.0.0) #-#-#-#-# # #-#-#-#-# dashboard_manage_flavors.pot (Admin User Guide 1.0.0) #-#-#-#-# -#: ../cli_manage_flavors.rst:59 ../dashboard_manage_flavors.rst:18 -msgid "16384" -msgstr "" - -# #-#-#-#-# cli_manage_flavors.pot (Admin User Guide 1.0.0) #-#-#-#-# -# #-#-#-#-# dashboard_manage_flavors.pot (Admin User Guide 1.0.0) #-#-#-#-# -#: ../cli_manage_flavors.rst:57 ../dashboard_manage_flavors.rst:16 -msgid "2" +#: ../cli_manage_flavors.rst:55 ../dashboard_manage_flavors.rst:14 +msgid "m1.tiny" msgstr "" # #-#-#-#-# cli_manage_flavors.pot (Admin User Guide 1.0.0) #-#-#-#-# @@ -135,14 +676,16 @@ msgstr "" msgid "2048" msgstr "" -#: ../dashboard_manage_volumes.rst:109 -msgid "256" +# #-#-#-#-# cli_manage_flavors.pot (Admin User Guide 1.0.0) #-#-#-#-# +# #-#-#-#-# dashboard_manage_flavors.pot (Admin User Guide 1.0.0) #-#-#-#-# +#: ../cli_manage_flavors.rst:56 ../dashboard_manage_flavors.rst:15 +msgid "m1.small" msgstr "" # #-#-#-#-# cli_manage_flavors.pot (Admin User Guide 1.0.0) #-#-#-#-# # #-#-#-#-# dashboard_manage_flavors.pot (Admin User Guide 1.0.0) #-#-#-#-# -#: ../cli_manage_flavors.rst:58 ../dashboard_manage_flavors.rst:17 -msgid "4" +#: ../cli_manage_flavors.rst:57 ../dashboard_manage_flavors.rst:16 +msgid "2" msgstr "" # #-#-#-#-# cli_manage_flavors.pot (Admin User Guide 1.0.0) #-#-#-#-# @@ -159,19 +702,14 @@ msgstr "" # #-#-#-#-# cli_manage_flavors.pot (Admin User Guide 1.0.0) #-#-#-#-# # #-#-#-#-# dashboard_manage_flavors.pot (Admin User Guide 1.0.0) #-#-#-#-# -#: ../cli_manage_flavors.rst:55 ../dashboard_manage_flavors.rst:14 -msgid "512" -msgstr "" - -#: ../dashboard_manage_volumes.rst:104 -msgid "" -"512 (Recommended for aes-xts-plain64. 256 should be used for aes-cbc-essiv)" +#: ../cli_manage_flavors.rst:57 ../dashboard_manage_flavors.rst:16 +msgid "m1.medium" msgstr "" # #-#-#-#-# cli_manage_flavors.pot (Admin User Guide 1.0.0) #-#-#-#-# # #-#-#-#-# dashboard_manage_flavors.pot (Admin User Guide 1.0.0) #-#-#-#-# -#: ../cli_manage_flavors.rst:59 ../dashboard_manage_flavors.rst:18 -msgid "8" +#: ../cli_manage_flavors.rst:58 ../dashboard_manage_flavors.rst:17 +msgid "4" msgstr "" # #-#-#-#-# cli_manage_flavors.pot (Admin User Guide 1.0.0) #-#-#-#-# @@ -186,1012 +724,63 @@ msgstr "" msgid "8192" msgstr "" -#: ../dashboard_manage_services.rst:26 -msgid "" -":guilabel:`Block Storage Services`: Displays information specific to the " -"Block Storage Service. Both host and zone are listed for each service, as " -"well as its activation status." -msgstr "" - -#: ../dashboard_manage_services.rst:21 -msgid "" -":guilabel:`Compute Services`: Displays information specific to the Compute " -"Service. Both host and zone are listed for each service, as well as its " -"activation status." -msgstr "" - -#: ../dashboard_manage_images.rst:37 -msgid ":guilabel:`Description`" -msgstr "" - -#: ../dashboard_manage_images.rst:53 -msgid ":guilabel:`Format`" -msgstr "" - -#: ../dashboard_manage_images.rst:45 -msgid ":guilabel:`Image File` or :guilabel:`Image Location`" -msgstr "" - -#: ../dashboard_manage_images.rst:40 -msgid ":guilabel:`Image Source`" -msgstr "" - -#: ../dashboard_manage_images.rst:55 -msgid ":guilabel:`Minimum Disk (GB)` and :guilabel:`Minimum RAM (MB)`" -msgstr "" - -#: ../dashboard_manage_images.rst:35 -msgid ":guilabel:`Name`" -msgstr "" - -#: ../dashboard_manage_services.rst:31 -msgid "" -":guilabel:`Network Agents`: Displays the network agents active within the " -"cluster, such as L3 and DHCP agents, and the status of each agent." -msgstr "" - -#: ../dashboard_manage_services.rst:35 -msgid "" -":guilabel:`Orchestration Services`: Displays information specific to the " -"Orchestration Service. Name, engine id, host and topic are listed for each " -"service, as well as its activation status." -msgstr "" - -#: ../dashboard_manage_images.rst:62 -msgid ":guilabel:`Protected`" -msgstr "" - -#: ../dashboard_manage_images.rst:59 -msgid ":guilabel:`Public`" -msgstr "" - -#: ../dashboard_manage_services.rst:16 -msgid "" -":guilabel:`Services`: Displays the internal name and the public OpenStack " -"name for each service, the host on which the service runs, and whether or " -"not the service is enabled." -msgstr "" - -#: ../dashboard_view_cloud_resources.rst:37 -msgid "" -":guilabel:`Stats` tab to view a multi-series line chart with user-defined " -"meters. You group by project, define the value type (min, max, avg, or sum), " -"and specify the time period (or even use a calendar to define a date range)." -msgstr "" - -#: ../dashboard_view_cloud_resources.rst:33 -msgid "" -":guilabel:`Usage Report` tab to view a usage report per tenant (project) by " -"specifying the time period (or even use a calendar to define a date range)." -msgstr "" - -#: ../index.rst:35 -msgid ":ref:`search`" -msgstr "" - -#: ../cli_manage_flavors.rst:17 -msgid "A flavor consists of the following parameters:" -msgstr "" - -#: ../dashboard_manage_volumes.rst:32 ../dashboard_manage_volumes.rst:134 -#: ../dashboard_manage_volumes.rst:155 -msgid "A message indicates whether the action succeeded." -msgstr "" - -#: ../manage_projects_users_and_roles.rst:36 -msgid "" -"A project is a group of zero or more users. In Compute, a project owns " -"virtual machines. In Object Storage, a project owns containers. Users can be " -"associated with more than one project. Each project and user pairing can " -"have a role associated with it." -msgstr "" - -#: ../networking_advanced_quotas.rst:4 -msgid "" -"A quota limits the number of available resources. A default quota might be " -"enforced for all tenants. When you try to create more resources than the " -"quota allows, an error occurs:" -msgstr "" - -#: ../dashboard_admin_manage_roles.rst:5 -msgid "" -"A role is a personality that a user assumes to perform a specific set of " -"operations. A role includes a set of rights and privileges. A user assumes " -"that role inherits those rights and privileges." -msgstr "" - -#: ../index.rst:6 -msgid "Abstract" -msgstr "" - -#: ../nova_cli_manage_projects_security.rst:114 -msgid "Add a new group rule, as follows:" -msgstr "" - -#: ../nova_cli_manage_projects_security.rst:189 -msgid "Add a source group, as follows:" -msgstr "" - -#: ../nova_cli_manage_projects_security.rst:97 -msgid "Add the new security group, as follows:" -msgstr "" - -#: ../nova_cli_manage_projects_security.rst:30 -msgid "" -"Additionally, the number of maximum rules per security group is controlled " -"by the ``security_group_rules`` and the number of allowed security groups " -"per project is controlled by the ``security_groups`` quota (see the `Manage " -"quotas `_ " -"section)." -msgstr "" - -#: ../cli_cinder_quotas.rst:70 -msgid "Administrative users can edit and update Block Storage service quotas." -msgstr "" - -#: ../cli_cinder_quotas.rst:22 -msgid "Administrative users can view Block Storage service quotas." -msgstr "" - -#: ../analyzing-log-files-with-swift-cli.rst:101 -msgid "" -"After ``awk`` processes the output, it pipes it to ``sort`` and ``uniq -c`` " -"to sum up the number of occurrences for each request type and return code " -"combination." -msgstr "" - -#: ../cli_nova_migrate.rst:18 -msgid "" -"After selecting a VM from the list, run this command where :guilabel:`VM_ID` " -"is set to the ID in the list returned in the previous step::" -msgstr "" - -#: ../cli_manage_flavors.rst:107 -msgid "" -"After you create a flavor, assign it to a project by specifying the flavor " -"name or ID and the tenant ID::" -msgstr "" - -#: ../networking_advanced_quotas.rst:278 -msgid "" -"After you run this command, you can see that quota values for the tenant are " -"reset to the default values::" -msgstr "" - -#: ../nova_cli_manage_projects_security.rst:10 -msgid "" -"All projects have a \"default\" security group which is applied to any " -"instance that has no other defined security group. Unless you change the " -"default, this security group denies all incoming traffic and allows only " -"outgoing traffic to your instance." -msgstr "" - -#: ../dashboard_manage_volumes.rst:70 -msgid "" -"Allows easier import and migration of imported encrypted volumes, and allows " -"access key to be changed without re-encrypting the volume" -msgstr "" - -#: ../cli_manage_flavors.rst:30 -msgid "Amount of RAM to use (in megabytes)." -msgstr "" - -#: ../cli_manage_flavors.rst:37 -msgid "" -"Amount of disk space (in gigabytes) to use for the ephemeral partition. If " -"unspecified, the value is 0 by default. Ephemeral disks offer machine local " -"disk storage linked to the life cycle of a VM instance. When a VM is " -"terminated, all data on the ephemeral disk is lost. Ephemeral disks are not " -"included in any snapshots." -msgstr "" - -#: ../cli_manage_flavors.rst:33 -msgid "Amount of disk space (in gigabytes) to use for the root (/) partition." -msgstr "" - -#: ../cli_manage_flavors.rst:47 -msgid "" -"Amount of swap space (in megabytes) to use. If unspecified, the value is 0 " -"by default." -msgstr "" - -#: ../cli_keystone_manage_services.rst:15 -msgid "" -"An SQL back end for the catalog service. When the Identity Service is " -"online, you must add the services to the catalog. When you deploy a system " -"for production, use the SQL back end." -msgstr "" - -#: ../analyzing-log-files-with-swift-cli.rst:3 -msgid "Analyze log files" -msgstr "" - -#: ../dashboard.rst:5 -msgid "" -"As a cloud administrative user, the OpenStack dashboard lets you create and " -"manage projects, users, images, and flavors. You can also set quotas and " -"create and manage services. For information about using the dashboard to " -"perform end user tasks, see the `OpenStack End User Guide `__." -msgstr "" - -#: ../manage_projects_users_and_roles.rst:4 -msgid "" -"As a cloud administrator, you manage projects, users, and roles. Projects " -"are organizational units in the cloud to which you can assign users. " -"Projects are also known as ``tenants`` or ``accounts``. Users can be members " -"of one or more projects. Roles define which actions users can perform. You " -"assign roles to user-project pairs." -msgstr "" - -#: ../intro-admin.rst:5 -msgid "" -"As an OpenStack cloud administrative user, you can manage tenants, known as " -"projects, users, services, images, flavors, and quotas." -msgstr "" - -#: ../dashboard_manage_images.rst:5 -msgid "" -"As an administrative user, you can create and manage images for the projects " -"to which you belong. You can also create and manage images for users in all " -"projects to which you have access." -msgstr "" - -#: ../dashboard_manage_instances.rst:5 -msgid "" -"As an administrative user, you can manage instances for users in various " -"projects. You can view, terminate, edit, perform a soft or hard reboot, " -"create a snapshot from, and migrate instances. You can also view the logs " -"for instances or launch a VNC console for an instance." -msgstr "" - -#: ../dashboard_manage_volumes.rst:11 -msgid "" -"As an administrative user, you can manage volumes and volume types for users " -"in various projects. You can create and delete volume types, and you can " -"view and delete volumes. Note that a volume can be encrypted by using the " -"steps outlined below." -msgstr "" - -#: ../cli_cinder_quotas.rst:5 -msgid "" -"As an administrative user, you can update the OpenStack Block Storage " -"service quotas for a project. You can also update the quota defaults for a " -"new project." -msgstr "" - -#: ../cli_set_compute_quotas.rst:5 -msgid "" -"As an administrative user, you can use the :command:`nova quota-*` commands, " -"which are provided by the ``python-novaclient`` package, to update the " -"Compute service quotas for a specific tenant or tenant user, as well as " -"update the quota defaults for a new tenant." -msgstr "" - -#: ../dashboard_manage_services.rst:5 -msgid "" -"As an administrative user, you can view information for OpenStack services." -msgstr "" - -#: ../cli_admin_manage_ip_addresses.rst:22 -msgid "" -"As an administrator using legacy networking (``nova-network``), you can use " -"the following bulk commands to list, create, and delete ranges of floating " -"IP addresses. These addresses can then be associated with instances by end " -"users." -msgstr "" - -#: ../cli_admin_manage_stacks.rst:26 -msgid "" -"As an administrator, you can also carry out stack functions on behalf of " -"your users. For example, to resume, suspend, or delete a stack, run:" -msgstr "" - -#: ../manage_projects_users_and_roles.rst:245 -msgid "Assign a role" -msgstr "" - -#: ../manage_projects_users_and_roles.rst:301 -msgid "" -"Assign a role to a user-project pair. In this example, assign the ``new-" -"role`` role to the ``demo`` and ``test-project`` pair:" -msgstr "" - -#: ../dashboard_manage_host_aggregates.rst:45 -msgid "" -"Assign hosts to the aggregate on the Host within :guilabel:`Aggregate` tab." -msgstr "" - -#: ../cli_keystone_manage_services.rst:126 -msgid "Assign the admin role to the user-project pair::" -msgstr "" - -#: ../cli_manage_flavors.rst:20 -msgid "" -"Automatically generated by OpenStack. For private flavors, a value from 1 to " -"255." -msgstr "" - -#: ../dashboard_manage_host_aggregates.rst:34 -msgid "" -"Availability Zone: The cloud provider defines the default availability zone, " -"such as ``us-west``, ``apac-south``, or ``nova``. You can target the host " -"aggregate, as follows:" -msgstr "" - -#: ../dashboard_manage_images.rst:45 -msgid "" -"Based on your selection, there is an :guilabel:`Image File` or :guilabel:" -"`Image Location` field. You can include the location URL or browse for the " -"image file on your file system and add it." -msgstr "" - -#: ../cli_admin_manage_stacks.rst:21 -msgid "" -"Basic creation and deletion of Orchestration stacks, refer to the `OpenStack " -"End User Guide `_" -msgstr "" - -#: ../networking_advanced_quotas.rst:17 -msgid "Basic quota configuration" -msgstr "" - -#: ../manage_projects_users_and_roles.rst:25 -msgid "" -"Before you can delete a user account, you must remove the user account from " -"its primary project." -msgstr "" - -#: ../manage_projects_users_and_roles.rst:28 -msgid "" -"Before you can run keystone client commands, you must download and source an " -"OpenStack RC file. See `Download and source the OpenStack RC file `__." -msgstr "" - -#: ../dashboard_set_quotas.rst:38 ../dashboard_set_quotas.rst:64 -#: ../dashboard_set_quotas.rst:70 -msgid "Block Storage" -msgstr "" - -#: ../cli_admin_manage_ip_addresses.rst:58 -msgid "Bulk create floating IP addresses" -msgstr "" - -#: ../cli_admin_manage_ip_addresses.rst:84 -msgid "Bulk delete floating IP addresses" -msgstr "" - -#: ../cli_admin_manage_ip_addresses.rst:67 -msgid "" -"By default, **floating-ip-bulk-create** uses the ``public`` pool and " -"``eth0`` interface values." -msgstr "" - -#: ../cli_admin_manage_ip_addresses.rst:11 -msgid "" -"By default, both administrative and end users can associate floating IP " -"addresses with projects and instances. You can change user permissions for " -"managing IP addresses by updating the ``/etc/nova/policy.json`` file. For " -"basic floating-IP procedures, refer to the *Manage IP Addresses* section in " -"the `OpenStack End User Guide `_." -msgstr "" - -#: ../analyzing-log-files-with-swift-cli.rst:35 -msgid "Change into the ``logtest`` directory::" -msgstr "" - -#: ../cli_nova_manage_services.rst:35 ../cli_nova_manage_services.rst:62 -msgid "Check the service list:" -msgstr "" - +# #-#-#-#-# cli_manage_flavors.pot (Admin User Guide 1.0.0) #-#-#-#-# # #-#-#-#-# dashboard_manage_flavors.pot (Admin User Guide 1.0.0) #-#-#-#-# -# #-#-#-#-# dashboard_manage_images.pot (Admin User Guide 1.0.0) #-#-#-#-# -#: ../dashboard_manage_flavors.rst:26 ../dashboard_manage_flavors.rst:76 -#: ../dashboard_manage_flavors.rst:91 ../dashboard_manage_flavors.rst:157 -#: ../dashboard_manage_images.rst:25 ../dashboard_manage_images.rst:77 -#: ../dashboard_manage_images.rst:94 +#: ../cli_manage_flavors.rst:58 ../dashboard_manage_flavors.rst:17 +msgid "m1.large" +msgstr "" + +# #-#-#-#-# cli_manage_flavors.pot (Admin User Guide 1.0.0) #-#-#-#-# +# #-#-#-#-# dashboard_manage_flavors.pot (Admin User Guide 1.0.0) #-#-#-#-# +#: ../cli_manage_flavors.rst:59 ../dashboard_manage_flavors.rst:18 +msgid "160" +msgstr "" + +# #-#-#-#-# cli_manage_flavors.pot (Admin User Guide 1.0.0) #-#-#-#-# +# #-#-#-#-# dashboard_manage_flavors.pot (Admin User Guide 1.0.0) #-#-#-#-# +#: ../cli_manage_flavors.rst:59 ../dashboard_manage_flavors.rst:18 +msgid "16384" +msgstr "" + +# #-#-#-#-# cli_manage_flavors.pot (Admin User Guide 1.0.0) #-#-#-#-# +# #-#-#-#-# dashboard_manage_flavors.pot (Admin User Guide 1.0.0) #-#-#-#-# +#: ../cli_manage_flavors.rst:59 ../dashboard_manage_flavors.rst:18 +msgid "8" +msgstr "" + +# #-#-#-#-# cli_manage_flavors.pot (Admin User Guide 1.0.0) #-#-#-#-# +# #-#-#-#-# dashboard_manage_flavors.pot (Admin User Guide 1.0.0) #-#-#-#-# +#: ../cli_manage_flavors.rst:59 ../dashboard_manage_flavors.rst:18 +msgid "m1.xlarge" +msgstr "" + +#: ../cli_manage_flavors.rst:62 msgid "" -"Choose the :guilabel:`admin` project from the drop-down list at the top of " -"the page." -msgstr "" - -#: ../dashboard_manage_host_aggregates.rst:21 -#: ../dashboard_manage_host_aggregates.rst:57 -msgid "" -"Choose the admin project from the drop-down list at the top of the page." -msgstr "" - -#: ../dashboard_manage_images.rst:40 -msgid "" -"Choose the image source from the dropdown list. Your choices are :guilabel:" -"`Image Location` and :guilabel:`Image File`." -msgstr "" - -#: ../dashboard_manage_volumes.rst:50 ../dashboard_manage_volumes.rst:97 -msgid "Cipher" -msgstr "" - -#: ../cli_cinder_quotas.rst:73 ../cli_cinder_quotas.rst:106 -msgid "Clear per-tenant quota limits::" -msgstr "" - -#: ../dashboard_manage_volumes.rst:39 -msgid "" -"Click :guilabel:`Create Encryption` in the Actions column of the newly " -"created volume type." -msgstr "" - -#: ../dashboard_manage_flavors.rst:30 ../dashboard_manage_flavors.rst:69 -msgid "Click :guilabel:`Create Flavor`." -msgstr "" - -#: ../dashboard_manage_host_aggregates.rst:27 -msgid "Click :guilabel:`Create Host Aggregate`." -msgstr "" - -#: ../dashboard_manage_images.rst:30 ../dashboard_manage_images.rst:67 -msgid "Click :guilabel:`Create Image`." -msgstr "" - -#: ../dashboard_manage_instances.rst:27 -msgid "" -"Click :guilabel:`Create Snapshot`. The dashboard shows the instance snapshot " -"in the :guilabel:`Images & Snapshots` category." -msgstr "" - -#: ../dashboard_manage_volumes.rst:55 -msgid "Click :guilabel:`Create Volume Type Encryption`." -msgstr "" - -#: ../dashboard_manage_volumes.rst:30 -msgid "Click :guilabel:`Create Volume Type` button to confirm your changes." -msgstr "" - -#: ../dashboard_manage_volumes.rst:27 -msgid "" -"Click :guilabel:`Create Volume Type` button. In the :guilabel:`Create Volume " -"Type` window, enter a name for the volume type." -msgstr "" - -#: ../dashboard_manage_flavors.rst:162 -msgid "Click :guilabel:`Delete Flavors`." -msgstr "" - -#: ../dashboard_manage_images.rst:99 -msgid "Click :guilabel:`Delete Images`." -msgstr "" - -#: ../dashboard_manage_volumes.rst:129 -msgid "Click :guilabel:`Delete Volume Types` button." -msgstr "" - -#: ../dashboard_manage_volumes.rst:150 -msgid "Click :guilabel:`Delete Volumes` button." -msgstr "" - -#: ../dashboard_manage_instances.rst:73 -msgid "Click :guilabel:`Download CSV Summary` to download a CSV summary." -msgstr "" - -#: ../dashboard_manage_flavors.rst:84 ../dashboard_manage_flavors.rst:100 -msgid "Click :guilabel:`Save`." -msgstr "" - -#: ../dashboard_manage_images.rst:87 -msgid "Click :guilabel:`Update Image`." -msgstr "" - -#: ../dashboard_admin_manage_roles.rst:28 -msgid "Click the :guilabel:`Create Role` button to confirm your changes." -msgstr "" - -#: ../dashboard_admin_manage_roles.rst:25 -msgid "Click the :guilabel:`Create Role` button." -msgstr "" - -#: ../dashboard_admin_manage_roles.rst:36 -msgid "Click the :guilabel:`Edit` button." -msgstr "" - -#: ../dashboard_set_quotas.rst:100 ../dashboard_set_quotas.rst:105 -msgid "Click the :guilabel:`Update Defaults` button." -msgstr "" - -#: ../dashboard_admin_manage_roles.rst:39 -msgid "Click the :guilabel:`Update Role` button to confirm your changes." -msgstr "" - -#: ../dashboard_view_cloud_resources.rst:31 -msgid "Click the:" -msgstr "" - -#: ../dashboard_manage_volumes.rst:67 -msgid "Comments" -msgstr "" - -#: ../dashboard_set_quotas.rst:41 ../dashboard_set_quotas.rst:44 -#: ../dashboard_set_quotas.rst:47 ../dashboard_set_quotas.rst:50 -#: ../dashboard_set_quotas.rst:52 ../dashboard_set_quotas.rst:55 -#: ../dashboard_set_quotas.rst:58 ../dashboard_set_quotas.rst:61 -#: ../dashboard_set_quotas.rst:67 -msgid "Compute" -msgstr "" - -#: ../networking_advanced_quotas.rst:104 -msgid "Configure Networking to show per-tenant quotas" -msgstr "" - -#: ../networking_advanced_quotas.rst:82 -msgid "Configure per-tenant quotas" -msgstr "" - -#: ../dashboard_manage_volumes.rst:42 -msgid "" -"Configure the encrypted volume by setting the parameters below from " -"available options (see table):" -msgstr "" - -#: ../cli_nova_numa_libvirt.rst:3 -msgid "Consider NUMA topology when booting instances" -msgstr "" - -#: ../dashboard_set_quotas.rst:47 -msgid "Content bytes allowed for each injected file." -msgstr "" - -#: ../index.rst:18 -msgid "Contents" -msgstr "" - -#: ../dashboard_manage_volumes.rst:48 ../dashboard_manage_volumes.rst:81 -msgid "Control Location" -msgstr "" - -#: ../dashboard_manage_instances.rst:35 -msgid "Control the state of an instance" +"You can create and manage flavors with the nova **flavor-*** commands " +"provided by the ``python-novaclient`` package." msgstr "" #: ../cli_manage_flavors.rst:67 msgid "Create a flavor" msgstr "" -#: ../manage_projects_users_and_roles.rst:62 -msgid "Create a project" -msgstr "" - -#: ../cli_keystone_manage_services.rst:106 +#: ../cli_manage_flavors.rst:69 msgid "" -"Create a project for the service users. Typically, this project is named " -"``service``, but choose any name you like::" +"List flavors to show the ID and name, the amount of memory, the amount of " +"disk space for the root partition and for the ephemeral partition, the swap, " +"and the number of virtual CPUs for each flavor::" msgstr "" -#: ../manage_projects_users_and_roles.rst:64 -msgid "Create a project named ``new-project``:" -msgstr "" - -# #-#-#-#-# dashboard_admin_manage_roles.pot (Admin User Guide 1.0.0) #-#-#-#-# -# #-#-#-#-# manage_projects_users_and_roles.pot (Admin User Guide 1.0.0) #-#-#-#-# -#: ../dashboard_admin_manage_roles.rst:20 -#: ../manage_projects_users_and_roles.rst:227 -msgid "Create a role" -msgstr "" - -#: ../nova_cli_manage_projects_security.rst:87 -msgid "Create a security group" -msgstr "" - -#: ../cli_keystone_manage_services.rst:36 -msgid "Create a service" -msgstr "" - -#: ../manage_projects_users_and_roles.rst:146 -msgid "Create a user" -msgstr "" - -#: ../dashboard_manage_volumes.rst:19 -msgid "Create a volume type" -msgstr "" - -#: ../dashboard_manage_volumes.rst:37 +#: ../cli_manage_flavors.rst:77 msgid "" -"Create a volume type using the steps above for :ref:`create-a-volume-type`." +"To create a flavor, specify a name, ID, RAM size, disk size, and the number " +"of VCPUs for the flavor, as follows::" msgstr "" -#: ../dashboard_manage_volumes.rst:35 -msgid "Create an encrypted volume type" -msgstr "" - -#: ../dashboard_manage_host_aggregates.rst:3 -msgid "Create and manage host aggregates" -msgstr "" - -#: ../dashboard_manage_images.rst:3 -msgid "Create and manage images" -msgstr "" - -#: ../dashboard_admin_manage_roles.rst:3 -msgid "Create and manage roles" -msgstr "" - -#: ../cli_keystone_manage_services.rst:3 -msgid "Create and manage services and service users" -msgstr "" - -#: ../dashboard_manage_flavors.rst:22 -msgid "Create flavors" -msgstr "" - -#: ../dashboard_manage_images.rst:18 -msgid "Create images" -msgstr "" - -#: ../dashboard_manage_instances.rst:14 -msgid "Create instance snapshots" -msgstr "" - -#: ../nova_cli_manage_projects_security.rst:179 -msgid "Create security group rules for a cluster of instances" -msgstr "" - -#: ../cli_keystone_manage_services.rst:104 -msgid "Create service users" -msgstr "" - -#: ../cli_keystone_manage_services.rst:123 -msgid "Create service users for the relevant services for your deployment." -msgstr "" - -#: ../manage_projects_users_and_roles.rst:232 -msgid "Create the ``new-role`` role:" -msgstr "" - -#: ../manage_projects_users_and_roles.rst:153 -msgid "Create the ``new-user`` user:" -msgstr "" - -# #-#-#-#-# cli_cinder_quotas.pot (Admin User Guide 1.0.0) #-#-#-#-# -# #-#-#-#-# dashboard_set_quotas.pot (Admin User Guide 1.0.0) #-#-#-#-# -#: ../cli_cinder_quotas.rst:12 ../dashboard_set_quotas.rst:36 -msgid "Defines the number of" -msgstr "" - -#: ../cli_manage_flavors.rst:130 -msgid "Delete a flavor" -msgstr "" - -#: ../manage_projects_users_and_roles.rst:117 -msgid "Delete a project" -msgstr "" - -#: ../dashboard_admin_manage_roles.rst:45 -msgid "Delete a role" -msgstr "" - -#: ../nova_cli_manage_projects_security.rst:162 -msgid "Delete a security group" -msgstr "" - -#: ../cli_keystone_manage_services.rst:140 -msgid "Delete a service" -msgstr "" - -#: ../cli_manage_flavors.rst:131 -msgid "Delete a specified flavor, as follows::" -msgstr "" - -#: ../manage_projects_users_and_roles.rst:199 -msgid "Delete a specified user account:" -msgstr "" - -#: ../manage_projects_users_and_roles.rst:197 -msgid "Delete a user" -msgstr "" - -#: ../networking_advanced_quotas.rst:89 -msgid "Delete defined quotas for a specified tenant" -msgstr "" - -#: ../dashboard_manage_flavors.rst:153 -msgid "Delete flavors" -msgstr "" - -#: ../dashboard_manage_images.rst:90 -msgid "Delete images" -msgstr "" - -#: ../networking_advanced_quotas.rst:270 -msgid "Delete per-tenant quota values." -msgstr "" - -#: ../nova_cli_manage_projects_security.rst:166 -msgid "Delete the new security group, as follows:" -msgstr "" - -#: ../dashboard_manage_volumes.rst:117 -msgid "Delete volume types" -msgstr "" - -#: ../dashboard_manage_volumes.rst:137 -msgid "Delete volumes" -msgstr "" - -#: ../dashboard_manage_instances.rst:48 +#: ../cli_manage_flavors.rst:84 msgid "" -"Depending on the current state of the instance, you can choose to pause, un-" -"pause, suspend, resume, soft or hard reboot, or terminate an instance (items " -"in red are dangerous)." -msgstr "" - -#: ../cli_set_compute_quotas.rst:17 -msgid "Description" -msgstr "" - -#: ../nova_cli_manage_projects_security.rst:146 -msgid "" -"Despite only outputting the newly added rule, this operation is additive " -"(both rules are created and enforced)." -msgstr "" - -#: ../cli_nova_manage_services.rst:24 -msgid "Disable a nova service:" -msgstr "" - -#: ../analyzing-log-files-with-swift-cli.rst:144 -msgid "Discover how many PUT requests are in each log file." -msgstr "" - -# #-#-#-#-# cli_manage_flavors.pot (Admin User Guide 1.0.0) #-#-#-#-# -# #-#-#-#-# dashboard_manage_flavors.pot (Admin User Guide 1.0.0) #-#-#-#-# -#: ../cli_manage_flavors.rst:53 ../dashboard_manage_flavors.rst:12 -msgid "Disk (in GB)" -msgstr "" - -#: ../analyzing-log-files-with-swift-cli.rst:105 -msgid "Download an object::" -msgstr "" - -#: ../analyzing-log-files-with-swift-cli.rst:89 -msgid "Download and analyze an object" -msgstr "" - -#: ../manage_projects_users_and_roles.rst:17 -msgid "" -"During cloud set up, the operator defines at least one project, user, and " -"role." -msgstr "" - -#: ../analyzing-log-files-with-swift-cli.rst:29 -msgid "Each file uses the following line format::" -msgstr "" - -#: ../cli_admin_manage_ip_addresses.rst:5 -msgid "" -"Each instance has a private, fixed IP address (assigned when launched) and " -"can also have a public, or floating, address. Private IP addresses are used " -"for communication between instances, and public addresses are used for " -"communication with networks outside the cloud, including the Internet." -msgstr "" - -#: ../dashboard_manage_host_aggregates.rst:8 -msgid "" -"Each node can have multiple aggregates and each aggregate can have multiple " -"key-value pairs. You can assign the same key-value pair to multiple " -"aggregates." -msgstr "" - -#: ../dashboard_admin_manage_roles.rst:31 -msgid "Edit a role" -msgstr "" - -#: ../cli_cinder_quotas.rst:68 -msgid "Edit and update Block Storage service quotas" -msgstr "" - -#: ../cli_nova_manage_services.rst:51 -msgid "Enable the service:" -msgstr "" - -#: ../dashboard_manage_volumes.rst:67 -msgid "Encryption parameters" -msgstr "" - -#: ../nova_cli_manage_projects_security.rst:94 -msgid "" -"Ensure your system variables are set for the user and tenant for which you " -"are checking security group rules for." -msgstr "" - -#: ../nova_cli_manage_projects_security.rst:41 -msgid "" -"Ensure your system variables are set for the user and tenant for which you " -"are checking security group rules for. For example:" -msgstr "" - -#: ../nova_cli_manage_projects_security.rst:163 -msgid "" -"Ensure your system variables are set for the user and tenant for which you " -"are deleting a security group for." -msgstr "" - -#: ../dashboard_manage_images.rst:37 -msgid "Enter a brief description of the image." -msgstr "" - -#: ../dashboard_manage_images.rst:35 -msgid "Enter a name for the image." -msgstr "" - -#: ../dashboard_manage_flavors.rst:41 -msgid "Enter the amount of RAM to use, in megabytes." -msgstr "" - -#: ../dashboard_manage_flavors.rst:46 -msgid "" -"Enter the amount of disk space in gigabytes to use for the ephemeral " -"partition. If unspecified, the value is 0 by default." -msgstr "" - -#: ../dashboard_manage_flavors.rst:43 -msgid "" -"Enter the amount of disk space in gigabytes to use for the root (/) " -"partition." -msgstr "" - -#: ../dashboard_manage_flavors.rst:57 -msgid "" -"Enter the amount of swap space (in megabytes) to use. If unspecified, the " -"default is 0." -msgstr "" - -#: ../dashboard_manage_flavors.rst:37 -msgid "Enter the flavor name." -msgstr "" - -#: ../dashboard_manage_flavors.rst:39 -msgid "Enter the number of virtual CPUs to use." -msgstr "" - -#: ../cli_manage_flavors.rst:44 -msgid "Ephemeral Disk GB" -msgstr "" - -#: ../dashboard_manage_flavors.rst:51 -msgid "" -"Ephemeral disks offer machine local disk storage linked to the life cycle of " -"a VM instance. When a VM is terminated, all data on the ephemeral disk is " -"lost. Ephemeral disks are not included in any snapshots." -msgstr "" - -#: ../cli_nova_evacuate.rst:3 -msgid "Evacuate instances" -msgstr "" - -#: ../cli_nova_evacuate.rst:19 -msgid "" -"Evacuate the instance. You can pass the instance password to the command by " -"using the :option:`--password PWD` option. If you do not specify a password, " -"one is generated and printed after the command finishes successfully. The " -"following command evacuates a server without shared storage from a host that " -"is down to the specified HOST_B::" -msgstr "" - -# #-#-#-#-# cli_manage_flavors.pot (Admin User Guide 1.0.0) #-#-#-#-# -# #-#-#-#-# dashboard_manage_flavors.pot (Admin User Guide 1.0.0) #-#-#-#-# -#: ../cli_manage_flavors.rst:53 ../dashboard_manage_flavors.rst:12 -msgid "Flavor" -msgstr "" - -#: ../cli_manage_flavors.rst:21 -msgid "Flavor ID" -msgstr "" - -#: ../cli_manage_flavors.rst:12 -msgid "" -"Flavors can also determine on which compute host a flavor can be used to " -"launch an instance. For information about customizing flavors, refer to the " -"`OpenStack Cloud Administrator Guide `_." -msgstr "" - -#: ../cli_manage_flavors.rst:103 ../cli_manage_flavors.rst:125 -msgid "For a list of optional parameters, run this command::" -msgstr "" - -#: ../dashboard_view_cloud_resources.rst:18 -msgid "" -"For basic administration information, refer to the \"Measure Cloud Resources" -"\" chapter in the `OpenStack End User Guide `_." -msgstr "" - -#: ../dashboard_manage_images.rst:20 -msgid "" -"For details about image creation, see the `Virtual Machine Image Guide " -"`_." -msgstr "" - -#: ../cli_admin_manage_ip_addresses.rst:17 -msgid "" -"For details on creating public networks using OpenStack Networking " -"(``neutron``), refer to the `OpenStack Cloud Administrator Guide `_ . No " -"floating IP addresses are created by default in OpenStack Networking." -msgstr "" - -#: ../analyzing-log-files-with-swift-cli.rst:176 -msgid "For each item in the list, run the swift **download -o -** command." -msgstr "" - -#: ../cli_keystone_manage_services.rst:68 -msgid "" -"For example, to create a ``swift`` service of type ``object-store``, run " -"this command:" -msgstr "" - -# #-#-#-#-# cli_cinder_quotas.pot (Admin User Guide 1.0.0) #-#-#-#-# -# #-#-#-#-# cli_keystone_manage_services.pot (Admin User Guide 1.0.0) #-#-#-#-# -# #-#-#-#-# nova_cli_manage_projects_security.pot (Admin User Guide 1.0.0) #-#-#-#-# -#: ../cli_cinder_quotas.rst:41 ../cli_cinder_quotas.rst:92 -#: ../cli_keystone_manage_services.rst:88 -#: ../cli_keystone_manage_services.rst:145 -#: ../nova_cli_manage_projects_security.rst:67 -#: ../nova_cli_manage_projects_security.rst:103 -#: ../nova_cli_manage_projects_security.rst:172 -#: ../nova_cli_manage_projects_security.rst:195 -msgid "For example:" -msgstr "" - -# #-#-#-#-# cli_admin_manage_ip_addresses.pot (Admin User Guide 1.0.0) #-#-#-#-# -# #-#-#-#-# cli_nova_specify_host.pot (Admin User Guide 1.0.0) #-#-#-#-# -# #-#-#-#-# cli_set_compute_quotas.pot (Admin User Guide 1.0.0) #-#-#-#-# -#: ../cli_admin_manage_ip_addresses.rst:63 -#: ../cli_admin_manage_ip_addresses.rst:89 ../cli_nova_specify_host.rst:13 -#: ../cli_set_compute_quotas.rst:53 ../cli_set_compute_quotas.rst:77 -#: ../cli_set_compute_quotas.rst:92 ../cli_set_compute_quotas.rst:122 -#: ../cli_set_compute_quotas.rst:163 ../cli_set_compute_quotas.rst:197 -msgid "For example::" -msgstr "" - -#: ../dashboard_manage_flavors.rst:148 -msgid "" -"For information about supporting metadata keys, see the `OpenStack Cloud " -"Administrator Guide `__." -msgstr "" - -#: ../cli_admin_manage_stacks.rst:19 -msgid "For information about the:" -msgstr "" - -#: ../dashboard_manage_instances.rst:10 -msgid "" -"For information about using the dashboard to launch instances as an end " -"user, see the `OpenStack End User Guide `__." -msgstr "" - -#: ../dashboard_admin_manage_stacks.rst:17 -msgid "For information about:" -msgstr "" - -#: ../nova_cli_manage_projects_security.rst:38 -msgid "" -"From the command line you can get a list of security groups for the project, " -"using the nova command:" -msgstr "" - -#: ../analyzing-log-files-with-swift-cli.rst:50 -msgid "Get statistics for the account::" -msgstr "" - -#: ../analyzing-log-files-with-swift-cli.rst:62 -msgid "Get statistics for the logtest container::" -msgstr "" - -#: ../dashboard_set_quotas.rst:38 -msgid "Gigabytes" +"The flavor ID is a number from 1 to 255 and cannot contain special " +"characters or spaces." msgstr "" #: ../cli_manage_flavors.rst:87 @@ -1203,24 +792,6 @@ msgid "" "(through the Virtual Interface (vif) creation in the hypervisor)::" msgstr "" -#: ../dashboard_manage_host_aggregates.rst:5 -msgid "" -"Host aggregates enable administrative users to assign key-value pairs to " -"groups of machines." -msgstr "" - -#: ../intro-admin.rst:3 -msgid "How can I administer an OpenStack cloud?" -msgstr "" - -#: ../cli_nova_evacuate.rst:5 -msgid "" -"If a cloud compute node fails due to a hardware malfunction or another " -"reason, you can evacuate instances to make them available again. You can " -"optionally include the target host on the :command:`evacuate` command. If " -"you omit the host, the scheduler determines the target host." -msgstr "" - #: ../cli_manage_flavors.rst:98 msgid "" "If an individual user or group of users needs a custom flavor that you do " @@ -1230,73 +801,14 @@ msgid "" "flavors.html>`_." msgstr "" -#: ../nova_cli_manage_projects_security.rst:19 -msgid "If set to:" +#: ../cli_manage_flavors.rst:103 ../cli_manage_flavors.rst:125 +msgid "For a list of optional parameters, run this command::" msgstr "" -#: ../cli_nova_numa_libvirt.rst:16 +#: ../cli_manage_flavors.rst:107 msgid "" -"If the host is NUMA capable, and the instance has requested a specific NUMA " -"topology, Compute will try to pin the vCPUs of different NUMA cells on the " -"instance to the corresponding NUMA cells on the host. It will also expose " -"the NUMA topology of the instance to the guest OS." -msgstr "" - -#: ../cli_nova_numa_libvirt.rst:12 -msgid "" -"If the host is NUMA capable, but the instance has not requested a NUMA " -"topology, Compute attempts to pack the instance into a single cell. If this " -"fails, though, Compute will not continue to try." -msgstr "" - -#: ../manage_projects_users_and_roles.rst:351 -msgid "If the role was removed, the command output omits the removed role." -msgstr "" - -#: ../manage_projects_users_and_roles.rst:179 -msgid "" -"If you disable a user account, the user cannot log in to the dashboard. " -"However, data for the user account is maintained, so you can enable the user " -"at any time." -msgstr "" - -#: ../cli_nova_migrate.rst:66 -msgid "" -"If you see this error, it means you are either trying the command with the " -"wrong credentials, such as a non-admin user, or the ``policy.json`` file " -"prevents migration for your user:" -msgstr "" - -#: ../cli_nova_numa_libvirt.rst:21 -msgid "" -"If you want Compute to pin a particular vCPU as part of this process, set " -"the ``vcpu_pin_set`` parameter in the :file:`nova.conf` configuration file. " -"For more information about the ``vcpu_pin_set`` parameter, see the " -"Configuration Reference Guide." -msgstr "" - -#: ../dashboard_manage_flavors.rst:5 -msgid "" -"In OpenStack, a flavor defines the compute, memory, and storage capacity of " -"a virtual server, also known as an instance. As an administrative user, you " -"can create, edit, and delete flavors." -msgstr "" - -#: ../cli_manage_flavors.rst:5 -msgid "" -"In OpenStack, flavors define the compute, memory, and storage capacity of " -"nova computing instances. To put it simply, a flavor is an available " -"hardware configuration for a server. It defines the \"size\" of a virtual " -"server that can be launched." -msgstr "" - -#: ../intro-admin.rst:21 -msgid "" -"In addition to these ways of interacting with a cloud, you can access the " -"OpenStack APIs directly or indirectly through `cURL `__ " -"commands or open SDKs. You can automate access or build tools to manage " -"resources and services by using the native OpenStack APIs or the EC2 " -"compatibility API." +"After you create a flavor, assign it to a project by specifying the flavor " +"name or ID and the tenant ID::" msgstr "" #: ../cli_manage_flavors.rst:113 @@ -1312,421 +824,147 @@ msgid "" "`__." msgstr "" -#: ../dashboard_manage_host_aggregates.rst:72 -msgid "" -"In the :guilabel:`Add/Remove Hosts to Aggregate` dialog box, click **+** to " -"assign a host to an aggregate. Click **-** to remove a host that is assigned " -"to an aggregate." +#: ../cli_manage_flavors.rst:130 +msgid "Delete a flavor" msgstr "" -#: ../dashboard_manage_flavors.rst:28 ../dashboard_manage_flavors.rst:78 -#: ../dashboard_manage_flavors.rst:93 ../dashboard_manage_flavors.rst:159 -msgid "" -"In the :guilabel:`Admin` tab, open the :guilabel:`System` tab and click the :" -"guilabel:`Flavors` category." -msgstr "" - -#: ../dashboard_manage_flavors.rst:163 -msgid "" -"In the :guilabel:`Confirm Delete Flavors` window, click :guilabel:`Delete " -"Flavors` to confirm the deletion. You cannot undo this action." -msgstr "" - -#: ../dashboard_manage_images.rst:100 -msgid "" -"In the :guilabel:`Confirm Delete Image` window, click :guilabel:`Delete " -"Images` to confirm the deletion." -msgstr "" - -#: ../dashboard_admin_manage_roles.rst:52 -msgid "" -"In the :guilabel:`Confirm Delete Roles` window, click :guilabel:`Delete " -"Roles` to confirm the deletion." -msgstr "" - -#: ../dashboard_manage_volumes.rst:131 -msgid "" -"In the :guilabel:`Confirm Delete Volume Types` window, click the :guilabel:" -"`Delete Volume Types` button to confirm the action." -msgstr "" - -#: ../dashboard_manage_volumes.rst:152 -msgid "" -"In the :guilabel:`Confirm Delete Volumes` window, click the :guilabel:" -"`Delete Volumes` button to confirm the action." -msgstr "" - -#: ../dashboard_manage_images.rst:31 -msgid "" -"In the :guilabel:`Create An Image` window, enter or select the following " -"values:" -msgstr "" - -#: ../dashboard_manage_flavors.rst:31 -msgid "" -"In the :guilabel:`Create Flavor` window, enter or select the parameters for " -"the flavor." -msgstr "" - -#: ../dashboard_manage_host_aggregates.rst:29 -msgid "" -"In the :guilabel:`Create Host Aggregate` dialog box, enter or select the " -"following values on the :guilabel:`Host Aggregate Info` tab:" -msgstr "" - -#: ../dashboard_admin_manage_roles.rst:27 -msgid "In the :guilabel:`Create Role` window, enter a name for the role." -msgstr "" - -#: ../dashboard_manage_instances.rst:25 -msgid "" -"In the :guilabel:`Create Snapshot` window, enter a name for the snapshot." -msgstr "" - -#: ../dashboard_manage_flavors.rst:82 -msgid "" -"In the :guilabel:`Edit Flavor` window, you can change the flavor name, " -"VCPUs, RAM, root disk, ephemeral disk, and swap disk values." -msgstr "" - -#: ../dashboard_manage_host_aggregates.rst:66 -msgid "" -"In the :guilabel:`Edit Host Aggregate` dialog box, you can change the name " -"and availability zone for the aggregate." -msgstr "" - -#: ../dashboard_manage_flavors.rst:62 -msgid "" -"In the :guilabel:`Flavor Access` tab, you can control access to the flavor " -"by moving projects from the :guilabel:`All Projects` column to the :guilabel:" -"`Selected Projects` column." -msgstr "" - -#: ../dashboard_manage_instances.rst:45 -msgid "" -"In the :guilabel:`More` drop-down list in the :guilabel:`Actions` column, " -"select the state." -msgstr "" - -#: ../dashboard_set_quotas.rst:102 -msgid "" -"In the :guilabel:`Update Default Quotas` window, you can edit the default " -"quota values." -msgstr "" - -#: ../dashboard_manage_flavors.rst:98 -msgid "" -"In the :guilabel:`Update Flavor Metadata` window, you can customize some " -"metadata keys, then add it to this flavor and set them values." -msgstr "" - -#: ../dashboard_manage_images.rst:82 -msgid "In the :guilabel:`Update Image` window, you can change the image name." -msgstr "" - -#: ../dashboard_admin_manage_roles.rst:38 -msgid "In the :guilabel:`Update Role` window, enter a new name for the role." -msgstr "" - -#: ../networking_advanced_quotas.rst:18 -msgid "" -"In the Networking default quota mechanism, all tenants have the same quota " -"values, such as the number of resources that a tenant can create." -msgstr "" - -#: ../dashboard_set_quotas.rst:47 -msgid "Injected File Content Bytes" -msgstr "" - -#: ../dashboard_set_quotas.rst:44 -msgid "Injected Files" -msgstr "" - -#: ../dashboard_set_quotas.rst:44 -msgid "Injected files allowed for each project." -msgstr "" - -#: ../dashboard_set_quotas.rst:67 -msgid "Instance cores allowed for each project." -msgstr "" - -#: ../dashboard_set_quotas.rst:41 -msgid "Instances" -msgstr "" - -#: ../dashboard_set_quotas.rst:41 -msgid "Instances allowed for each project." -msgstr "" - -#: ../dashboard_manage_volumes.rst:53 -msgid "Key Size" -msgstr "" - -#: ../dashboard_manage_volumes.rst:104 -msgid "Key Size (bits)" -msgstr "" - -#: ../dashboard_set_quotas.rst:50 -msgid "Keypairs" -msgstr "" - -#: ../cli_admin_manage_stacks.rst:3 -msgid "Launch and manage stacks using the CLI" -msgstr "" - -#: ../dashboard_admin_manage_stacks.rst:3 -msgid "Launch and manage stacks using the Dashboard" -msgstr "" - -#: ../manage_projects_users_and_roles.rst:20 -msgid "" -"Learn how to add, update, and delete projects and users, assign users to one " -"or more projects, and change or remove the assignment. To enable or " -"temporarily disable a project or user, you update that project or user. You " -"can also change quotas at the project level." -msgstr "" - -#: ../dashboard_manage_images.rst:55 -msgid "Leave these fields empty." -msgstr "" - -#: ../cli_set_compute_quotas.rst:29 -msgid "Length of injected file path." -msgstr "" - -#: ../dashboard_manage_volumes.rst:77 -msgid "Less disk overhead than LUKS" -msgstr "" - -#: ../networking_advanced_quotas.rst:112 -msgid "List Networking extensions." -msgstr "" - -#: ../cli_admin_manage_ip_addresses.rst:28 -msgid "List addresses for all projects" -msgstr "" - -#: ../cli_set_compute_quotas.rst:49 -msgid "List all default quotas for all tenants, as follows::" -msgstr "" - -#: ../analyzing-log-files-with-swift-cli.rst:76 -msgid "List all objects in the logtest container::" -msgstr "" - -#: ../manage_projects_users_and_roles.rst:44 -msgid "" -"List all projects with their ID, name, and whether they are enabled or " -"disabled:" -msgstr "" - -#: ../manage_projects_users_and_roles.rst:131 -msgid "List all users:" -msgstr "" - -#: ../nova_cli_manage_projects_security.rst:37 -msgid "List and view current security groups" -msgstr "" - -#: ../manage_projects_users_and_roles.rst:209 -msgid "List available roles" -msgstr "" - -#: ../cli_manage_flavors.rst:69 -msgid "" -"List flavors to show the ID and name, the amount of memory, the amount of " -"disk space for the root partition and for the ephemeral partition, the swap, " -"and the number of virtual CPUs for each flavor::" -msgstr "" - -#: ../manage_projects_users_and_roles.rst:42 -msgid "List projects" -msgstr "" - -#: ../manage_projects_users_and_roles.rst:283 -msgid "List projects and note the project ID you want to assign to the role:" -msgstr "" - -#: ../manage_projects_users_and_roles.rst:267 -msgid "List role IDs and note the role ID you want to assign:" -msgstr "" - -#: ../networking_advanced_quotas.rst:159 -msgid "List tenants who have per-tenant quota support." -msgstr "" - -#: ../cli_nova_manage_services.rst:8 -msgid "List the Compute services:" -msgstr "" - -#: ../manage_projects_users_and_roles.rst:211 -msgid "List the available roles:" -msgstr "" - -#: ../cli_keystone_manage_services.rst:38 -msgid "List the available services:" -msgstr "" - -#: ../cli_set_compute_quotas.rst:159 -msgid "List the currently set quota values for a tenant user, as follows::" -msgstr "" - -#: ../cli_set_compute_quotas.rst:88 -msgid "List the currently set quota values for a tenant, as follows::" -msgstr "" - -#: ../cli_cinder_quotas.rst:24 -msgid "List the default quotas for all projects:" -msgstr "" - -#: ../analyzing-log-files-with-swift-cli.rst:171 -msgid "List the object names that begin with a specified string." -msgstr "" - -#: ../manage_projects_users_and_roles.rst:129 -msgid "List users" -msgstr "" - -#: ../manage_projects_users_and_roles.rst:251 -msgid "List users and note the user ID you want to assign to the role:" -msgstr "" - -#: ../networking_advanced_quotas.rst:92 -msgid "Lists defined quotas for all tenants" -msgstr "" - -#: ../dashboard_manage_services.rst:7 -msgid "" -"Log in to the OpenStack dashboard and choose the :guilabel:`admin` project " -"from the drop-down list at the top of the page." -msgstr "" - -#: ../dashboard_view_cloud_resources.rst:27 -msgid "Log in to the OpenStack dashboard as a user with Admin privileges." -msgstr "" - -#: ../dashboard_set_quotas.rst:79 ../dashboard_set_quotas.rst:95 -msgid "Log in to the OpenStack dashboard." -msgstr "" - -#: ../dashboard_admin_manage_roles.rst:22 -#: ../dashboard_admin_manage_roles.rst:33 -#: ../dashboard_admin_manage_roles.rst:47 -msgid "" -"Log in to the dashboard and choose the :guilabel:`admin` project from the :" -"guilabel:`CURRENT PROJECT` drop-down list." -msgstr "" - -#: ../dashboard_manage_volumes.rst:21 ../dashboard_manage_volumes.rst:121 -#: ../dashboard_manage_volumes.rst:142 -msgid "" -"Log in to the dashboard and choose the :guilabel:`admin` project from the " -"drop-down list at the top of the page." -msgstr "" - -#: ../dashboard_manage_instances.rst:65 -msgid "" -"Log in to the dashboard and choose the admin project from the CURRENT " -"PROJECT drop-down list." -msgstr "" - -#: ../dashboard_manage_instances.rst:16 ../dashboard_manage_instances.rst:37 -msgid "" -"Log in to the dashboard and choose the admin project from the drop-down list " -"at the top of the page." -msgstr "" - -# #-#-#-#-# dashboard_manage_flavors.pot (Admin User Guide 1.0.0) #-#-#-#-# -# #-#-#-#-# dashboard_manage_host_aggregates.pot (Admin User Guide 1.0.0) #-#-#-#-# -# #-#-#-#-# dashboard_manage_images.pot (Admin User Guide 1.0.0) #-#-#-#-# -#: ../dashboard_manage_flavors.rst:24 ../dashboard_manage_flavors.rst:74 -#: ../dashboard_manage_flavors.rst:89 ../dashboard_manage_flavors.rst:155 -#: ../dashboard_manage_host_aggregates.rst:19 -#: ../dashboard_manage_images.rst:23 ../dashboard_manage_images.rst:75 -#: ../dashboard_manage_images.rst:92 -msgid "Log in to the dashboard." -msgstr "" - -#: ../nova_cli_manage_projects_security.rst:186 -msgid "" -"Make sure to set the system variables for the user and tenant for which you " -"are deleting a security group for." -msgstr "" - -#: ../cli_cinder_quotas.rst:3 -msgid "Manage Block Storage service quotas" -msgstr "" - -#: ../cli_set_compute_quotas.rst:3 -msgid "Manage Compute service quotas" -msgstr "" - -#: ../cli_nova_manage_services.rst:3 -msgid "Manage Compute services" -msgstr "" - -#: ../cli_admin_manage_ip_addresses.rst:3 -msgid "Manage IP addresses" -msgstr "" - -#: ../networking_advanced_quotas.rst:3 -msgid "Manage Networking service quotas" -msgstr "" - -# #-#-#-#-# cli_manage_flavors.pot (Admin User Guide 1.0.0) #-#-#-#-# -# #-#-#-#-# dashboard_manage_flavors.pot (Admin User Guide 1.0.0) #-#-#-#-# -#: ../cli_manage_flavors.rst:3 ../dashboard_manage_flavors.rst:3 -msgid "Manage flavors" -msgstr "" - -#: ../dashboard_manage_instances.rst:3 -msgid "Manage instances" -msgstr "" - -#: ../nova_cli_manage_projects_security.rst:3 -msgid "Manage project security" -msgstr "" - -#: ../manage_projects_users_and_roles.rst:3 -msgid "Manage projects, users, and roles" -msgstr "" - -#: ../cli_set_quotas.rst:3 -msgid "Manage quotas" +#: ../cli_manage_flavors.rst:131 +msgid "Delete a specified flavor, as follows::" msgstr "" #: ../cli_manage_services.rst:3 msgid "Manage services" msgstr "" -#: ../cli_admin_manage_environment.rst:3 -msgid "Manage the OpenStack environment" +#: ../cli_nova_evacuate.rst:3 +msgid "Evacuate instances" msgstr "" -#: ../dashboard_manage_volumes.rst:3 -msgid "Manage volumes and volume types" +#: ../cli_nova_evacuate.rst:5 +msgid "" +"If a cloud compute node fails due to a hardware malfunction or another " +"reason, you can evacuate instances to make them available again. You can " +"optionally include the target host on the :command:`evacuate` command. If " +"you omit the host, the scheduler determines the target host." msgstr "" -#: ../cli_set_compute_quotas.rst:39 -msgid "Megabytes of instance ram allowed per tenant." +#: ../cli_nova_evacuate.rst:11 +msgid "" +"To preserve user data on server disk, you must configure shared storage on " +"the target host. Also, you must validate that the current VM host is down; " +"otherwise, the evacuation fails with an error." msgstr "" -#: ../cli_manage_flavors.rst:30 -msgid "Memory MB" +#: ../cli_nova_evacuate.rst:15 +msgid "" +"To list hosts and find a different host for the evacuated instance, run::" msgstr "" -#: ../dashboard_set_quotas.rst:52 -msgid "Metadata Items" +#: ../cli_nova_evacuate.rst:19 +msgid "" +"Evacuate the instance. You can pass the instance password to the command by " +"using the :option:`--password PWD` option. If you do not specify a password, " +"one is generated and printed after the command finishes successfully. The " +"following command evacuates a server without shared storage from a host that " +"is down to the specified HOST_B::" msgstr "" -#: ../dashboard_set_quotas.rst:52 -msgid "Metadata items allowed for each instance." +#: ../cli_nova_evacuate.rst:28 +msgid "" +"The instance is booted from a new disk, but preserves its configuration " +"including its ID, name, uid, IP address, and so on. The command returns a " +"password::" +msgstr "" + +#: ../cli_nova_evacuate.rst:38 +msgid "" +"To preserve the user disk data on the evacuated server, deploy OpenStack " +"Compute with a shared file system. To configure your system, see `Configure " +"migrations `_ in OpenStack Cloud Administrator Guide. In the following " +"example, the password remains unchanged::" +msgstr "" + +#: ../cli_nova_manage_services.rst:3 +msgid "Manage Compute services" +msgstr "" + +#: ../cli_nova_manage_services.rst:4 +msgid "" +"You can enable and disable Compute services. The following examples disable " +"and enable the ``nova-compute`` service." +msgstr "" + +#: ../cli_nova_manage_services.rst:8 +msgid "List the Compute services:" +msgstr "" + +#: ../cli_nova_manage_services.rst:24 +msgid "Disable a nova service:" +msgstr "" + +#: ../cli_nova_manage_services.rst:35 ../cli_nova_manage_services.rst:62 +msgid "Check the service list:" +msgstr "" + +#: ../cli_nova_manage_services.rst:51 +msgid "Enable the service:" msgstr "" #: ../cli_nova_migrate.rst:6 msgid "Migrate single instance to another compute host" msgstr "" +#: ../cli_nova_migrate.rst:8 +msgid "" +"When you want to move an instance from one compute host to another, you can " +"use the ``nova migrate`` command. The scheduler chooses the destination " +"compute host based on its settings. This process does not assume that the " +"instance has shared storage available on the target host." +msgstr "" + +#: ../cli_nova_migrate.rst:14 +msgid "To list the VMs you want to migrate, run::" +msgstr "" + +#: ../cli_nova_migrate.rst:18 +msgid "" +"After selecting a VM from the list, run this command where :guilabel:`VM_ID` " +"is set to the ID in the list returned in the previous step::" +msgstr "" + +#: ../cli_nova_migrate.rst:23 +msgid "Now, use the ``nova migrate`` command::" +msgstr "" + +#: ../cli_nova_migrate.rst:27 +msgid "" +"To migrate of an instance and watch the status, use this example script:" +msgstr "" + +#: ../cli_nova_migrate.rst:66 +msgid "" +"If you see this error, it means you are either trying the command with the " +"wrong credentials, such as a non-admin user, or the ``policy.json`` file " +"prevents migration for your user:" +msgstr "" + +#: ../cli_nova_migrate.rst:71 +msgid "" +"``ERROR (Forbidden): Policy doesn't allow compute_extension:admin_actions:" +"migrate to be performed. (HTTP 403)``" +msgstr "" + +#: ../cli_nova_migrate.rst:74 +msgid "" +"The instance is booted from a new host, but preserves its configuration " +"including its ID, name, any metadata, IP address, and other properties." +msgstr "" + +#: ../cli_nova_numa_libvirt.rst:3 +msgid "Consider NUMA topology when booting instances" +msgstr "" + #: ../cli_nova_numa_libvirt.rst:5 msgid "" "NUMA topology can exist on both the physical hardware of the host, and the " @@ -1737,29 +975,92 @@ msgid "" "configuration." msgstr "" -#: ../cli_manage_flavors.rst:24 -msgid "Name" -msgstr "" - -#: ../cli_manage_flavors.rst:24 -msgid "Name for the new flavor." -msgstr "" - -#: ../dashboard_manage_host_aggregates.rst:32 -msgid "Name: The host aggregate name." -msgstr "" - -#: ../dashboard_manage_volumes.rst:100 +#: ../cli_nova_numa_libvirt.rst:12 msgid "" -"Note: On the command line, type 'cryptsetup benchmark' for additional options" +"If the host is NUMA capable, but the instance has not requested a NUMA " +"topology, Compute attempts to pack the instance into a single cell. If this " +"fails, though, Compute will not continue to try." msgstr "" -#: ../cli_nova_migrate.rst:23 -msgid "Now, use the ``nova migrate`` command::" +#: ../cli_nova_numa_libvirt.rst:16 +msgid "" +"If the host is NUMA capable, and the instance has requested a specific NUMA " +"topology, Compute will try to pin the vCPUs of different NUMA cells on the " +"instance to the corresponding NUMA cells on the host. It will also expose " +"the NUMA topology of the instance to the guest OS." msgstr "" -#: ../cli_set_compute_quotas.rst:27 -msgid "Number of content bytes allowed per injected file." +#: ../cli_nova_numa_libvirt.rst:21 +msgid "" +"If you want Compute to pin a particular vCPU as part of this process, set " +"the ``vcpu_pin_set`` parameter in the :file:`nova.conf` configuration file. " +"For more information about the ``vcpu_pin_set`` parameter, see the " +"Configuration Reference Guide." +msgstr "" + +#: ../cli_nova_specify_host.rst:3 +msgid "Select hosts where instances are launched" +msgstr "" + +#: ../cli_nova_specify_host.rst:5 +msgid "" +"With the appropriate permissions, you can select which host instances are " +"launched on and which roles can boot instances on this host." +msgstr "" + +#: ../cli_nova_specify_host.rst:9 +msgid "" +"To select the host where instances are launched, use the ``--" +"availability_zone ZONE:HOST`` parameter on the :command:`nova boot` command." +msgstr "" + +#: ../cli_nova_specify_host.rst:17 +msgid "" +"To specify which roles can launch an instance on a specified host, enable " +"the :code:`create:forced_host` option in the :file:`policy.json` file. By " +"default, this option is enabled for only the admin role." +msgstr "" + +#: ../cli_nova_specify_host.rst:22 +msgid "" +"To view the list of valid compute hosts, use the :command:`nova hypervisor-" +"list` command, as follows::" +msgstr "" + +#: ../cli_set_compute_quotas.rst:3 +msgid "Manage Compute service quotas" +msgstr "" + +#: ../cli_set_compute_quotas.rst:5 +msgid "" +"As an administrative user, you can use the :command:`nova quota-*` commands, " +"which are provided by the ``python-novaclient`` package, to update the " +"Compute service quotas for a specific tenant or tenant user, as well as " +"update the quota defaults for a new tenant." +msgstr "" + +#: ../cli_set_compute_quotas.rst:10 +msgid "**Compute quota descriptions**" +msgstr "" + +#: ../cli_set_compute_quotas.rst:16 +msgid "Quota name" +msgstr "" + +#: ../cli_set_compute_quotas.rst:17 +msgid "Description" +msgstr "" + +#: ../cli_set_compute_quotas.rst:18 +msgid "cores" +msgstr "" + +#: ../cli_set_compute_quotas.rst:19 +msgid "Number of instance cores (VCPUs) allowed per tenant." +msgstr "" + +#: ../cli_set_compute_quotas.rst:20 +msgid "fixed-ips" msgstr "" #: ../cli_set_compute_quotas.rst:21 @@ -1768,241 +1069,137 @@ msgid "" "to or greater than the number of allowed instances." msgstr "" +#: ../cli_set_compute_quotas.rst:24 +msgid "floating-ips" +msgstr "" + #: ../cli_set_compute_quotas.rst:25 msgid "Number of floating IP addresses allowed per tenant." msgstr "" +#: ../cli_set_compute_quotas.rst:26 +msgid "injected-file-content-bytes" +msgstr "" + +#: ../cli_set_compute_quotas.rst:27 +msgid "Number of content bytes allowed per injected file." +msgstr "" + +#: ../cli_set_compute_quotas.rst:28 +msgid "injected-file-path-bytes" +msgstr "" + +#: ../cli_set_compute_quotas.rst:29 +msgid "Length of injected file path." +msgstr "" + +#: ../cli_set_compute_quotas.rst:30 +msgid "injected-files" +msgstr "" + #: ../cli_set_compute_quotas.rst:31 msgid "Number of injected files allowed per tenant." msgstr "" -#: ../cli_set_compute_quotas.rst:19 -msgid "Number of instance cores (VCPUs) allowed per tenant." +#: ../cli_set_compute_quotas.rst:32 +msgid "instances" msgstr "" #: ../cli_set_compute_quotas.rst:33 msgid "Number of instances allowed per tenant." msgstr "" +#: ../cli_set_compute_quotas.rst:34 +msgid "key-pairs" +msgstr "" + #: ../cli_set_compute_quotas.rst:35 msgid "Number of key pairs allowed per user." msgstr "" -#: ../dashboard_set_quotas.rst:50 -msgid "Number of keypairs." +#: ../cli_set_compute_quotas.rst:36 +msgid "metadata-items" msgstr "" #: ../cli_set_compute_quotas.rst:37 msgid "Number of metadata items allowed per instance." msgstr "" -#: ../cli_set_compute_quotas.rst:43 -msgid "Number of rules per security group." +#: ../cli_set_compute_quotas.rst:38 +msgid "ram" +msgstr "" + +#: ../cli_set_compute_quotas.rst:39 +msgid "Megabytes of instance ram allowed per tenant." +msgstr "" + +#: ../cli_set_compute_quotas.rst:40 +msgid "security-groups" msgstr "" #: ../cli_set_compute_quotas.rst:41 msgid "Number of security groups per tenant." msgstr "" -#: ../cli_manage_flavors.rst:27 -msgid "Number of virtual CPUs to use." +#: ../cli_set_compute_quotas.rst:42 +msgid "security-group-rules" +msgstr "" + +#: ../cli_set_compute_quotas.rst:43 +msgid "Number of rules per security group." +msgstr "" + +#: ../cli_set_compute_quotas.rst:46 +msgid "View and update Compute quotas for a tenant (project)" +msgstr "" + +#: ../cli_set_compute_quotas.rst:48 +msgid "To view and update default quota values" +msgstr "" + +#: ../cli_set_compute_quotas.rst:49 +msgid "List all default quotas for all tenants, as follows::" +msgstr "" + +#: ../cli_set_compute_quotas.rst:73 +msgid "Update a default value for a new tenant, as follows::" +msgstr "" + +#: ../cli_set_compute_quotas.rst:82 +msgid "To view quota values for an existing tenant (project)" +msgstr "" + +#: ../cli_set_compute_quotas.rst:84 +msgid "Place the tenant ID in a usable variable, as follows::" +msgstr "" + +#: ../cli_set_compute_quotas.rst:88 +msgid "List the currently set quota values for a tenant, as follows::" +msgstr "" + +#: ../cli_set_compute_quotas.rst:113 +msgid "To update quota values for an existing tenant (project)" msgstr "" #: ../cli_set_compute_quotas.rst:114 msgid "Obtain the tenant ID, as follows::" msgstr "" -#: ../dashboard_manage_images.rst:96 +#: ../cli_set_compute_quotas.rst:118 ../cli_set_compute_quotas.rst:193 +msgid "Update a particular quota value, as follows::" +msgstr "" + +#: ../cli_set_compute_quotas.rst:143 ../cli_set_compute_quotas.rst:218 msgid "" -"On the :guilabel:`Admin tab`, open the :guilabel:`System` tab and click the :" -"guilabel:`Images` category." +"To view a list of options for the :command:`quota-update` command, run::" msgstr "" -#: ../dashboard_manage_instances.rst:68 -msgid "On the :guilabel:`Admin` tab, click the :guilabel:`Instances` category." +#: ../cli_set_compute_quotas.rst:148 +msgid "View and update Compute quotas for a tenant user" msgstr "" -#: ../dashboard_view_cloud_resources.rst:29 -msgid "" -"On the :guilabel:`Admin` tab, click the :guilabel:`Resource Usage` category." -msgstr "" - -#: ../dashboard_admin_manage_roles.rst:24 -#: ../dashboard_admin_manage_roles.rst:35 -#: ../dashboard_admin_manage_roles.rst:49 -msgid "On the :guilabel:`Admin` tab, click the :guilabel:`Roles` category." -msgstr "" - -#: ../dashboard_manage_services.rst:11 -msgid "" -"On the :guilabel:`Admin` tab, click the :guilabel:`System Information` " -"category." -msgstr "" - -#: ../dashboard_set_quotas.rst:81 ../dashboard_set_quotas.rst:97 -msgid "" -"On the :guilabel:`Admin` tab, open the :guilabel:`System` tab and click the :" -"guilabel:`Defaults` category." -msgstr "" - -#: ../dashboard_manage_host_aggregates.rst:24 -#: ../dashboard_manage_host_aggregates.rst:60 -msgid "" -"On the :guilabel:`Admin` tab, open the :guilabel:`System` tab and click the :" -"guilabel:`Host Aggregates` category." -msgstr "" - -#: ../dashboard_manage_images.rst:79 -msgid "" -"On the :guilabel:`Admin` tab, open the :guilabel:`System` tab and click the :" -"guilabel:`Images` category." -msgstr "" - -#: ../dashboard_manage_images.rst:27 -msgid "" -"On the :guilabel:`Admin` tab, open the :guilabel:`System` tab and click the :" -"guilabel:`Images` category. The images that you can administer for cloud " -"users appear on this page." -msgstr "" - -#: ../dashboard_manage_instances.rst:19 ../dashboard_manage_instances.rst:40 -msgid "" -"On the :guilabel:`Admin` tab, open the :guilabel:`System` tab and click the :" -"guilabel:`Instances` category." -msgstr "" - -#: ../dashboard_manage_volumes.rst:24 ../dashboard_manage_volumes.rst:124 -#: ../dashboard_manage_volumes.rst:145 -msgid "" -"On the :guilabel:`Admin` tab, open the :guilabel:`System` tab and click the :" -"guilabel:`Volumes` category." -msgstr "" - -#: ../dashboard_manage_volumes.rst:58 -msgid "" -"Once a volume type is updated by the :guilabel:`Create Encryption` option, " -"the volume type cannot be deleted." -msgstr "" - -#: ../dashboard_manage_flavors.rst:66 -msgid "" -"Only projects in the :guilabel:`Selected Projects` column can use the " -"flavor. If there are no projects in the right column, all projects can use " -"the flavor." -msgstr "" - -#: ../networking_advanced_quotas.rst:153 -msgid "" -"Only some plug-ins support per-tenant quotas. Specifically, Open vSwitch, " -"Linux Bridge, and VMware NSX support them, but new versions of other plug-" -"ins might bring additional functionality. See the documentation for each " -"plug-in." -msgstr "" - -#: ../networking_advanced_quotas.rst:100 -msgid "" -"Only users with the ``admin`` role can change a quota value. By default, the " -"default set of quotas are enforced for all tenants, so no :command:`quota-" -"create` command exists." -msgstr "" - -#: ../index.rst:3 -msgid "OpenStack Admin User Guide" -msgstr "" - -#: ../dashboard_admin_manage_roles.rst:9 -msgid "" -"OpenStack Identity service defines a user's role on a project, but it is " -"completely up to the individual service to define what that role means. This " -"is referred to as the service's policy. To get details about what the " -"privileges for each role are, refer to the :file:`policy.json` file " -"available for each service in the :file:`/etc/SERVICE/policy.json` file. For " -"example, the policy defined for OpenStack Identity service is defined in " -"the :file:`/etc/keystone/policy.json` file." -msgstr "" - -#: ../networking_advanced_quotas.rst:83 -msgid "" -"OpenStack Networking also supports per-tenant quota limit by quota extension " -"API." -msgstr "" - -#: ../networking_advanced_quotas.rst:46 -msgid "" -"OpenStack Networking also supports quotas for L3 resources: router and " -"floating IP. Add these lines to the ``quotas`` section in the :file:`neutron." -"conf` file:" -msgstr "" - -#: ../networking_advanced_quotas.rst:62 -msgid "" -"OpenStack Networking also supports quotas for security group resources: " -"number of security groups and the number of rules for each security group. " -"Add these lines to the ``quotas`` section in the :file:`neutron.conf` file:" -msgstr "" - -#: ../cli.rst:3 -msgid "OpenStack command-line clients" -msgstr "" - -#: ../intro-admin.rst:14 -msgid "" -"OpenStack command-line clients. Each core OpenStack project has a command-" -"line client that you can use to run simple commands to view, create, and " -"manage resources and services in a cloud and automate tasks by using scripts." -msgstr "" - -#: ../dashboard.rst:3 -msgid "OpenStack dashboard" -msgstr "" - -#: ../intro-admin.rst:11 -msgid "" -"OpenStack dashboard. Use this web-based graphical interface, code named " -"`horizon `__, to view, " -"create, and manage resources and services." -msgstr "" - -#: ../dashboard_manage_flavors.rst:38 -msgid "OpenStack generates the flavor ID." -msgstr "" - -#: ../index.rst:8 -msgid "" -"OpenStack is an open source cloud computing platform for public and private " -"clouds. A series of interrelated projects deliver a cloud infrastructure " -"solution. This guide shows OpenStack admin users how to create and manage " -"resources in an OpenStack cloud with the OpenStack dashboard or OpenStack " -"client commands." -msgstr "" - -#: ../nova_cli_manage_projects_security.rst:49 -msgid "Output security groups, as follows:" -msgstr "" - -#: ../dashboard_manage_volumes.rst:67 -msgid "Parameter options" -msgstr "" - -#: ../networking_advanced_quotas.rst:13 -msgid "" -"Per-tenant quota configuration is also supported by the quota extension API. " -"See :ref:`cfg_quotas_per_tenant` for details." -msgstr "" - -#: ../cli_admin_manage_ip_addresses.rst:74 -msgid "" -"Pick a small range (/29 gives an 8 address range, 6 of which will be usable)." -msgstr "" - -#: ../analyzing-log-files-with-swift-cli.rst:178 -msgid "" -"Pipe the output to **grep** and **wc**. Use the **echo** command to display " -"the object name::" -msgstr "" - -#: ../cli_set_compute_quotas.rst:84 -msgid "Place the tenant ID in a usable variable, as follows::" +#: ../cli_set_compute_quotas.rst:150 +msgid "To view quota values for a tenant user" msgstr "" #: ../cli_set_compute_quotas.rst:151 ../cli_set_compute_quotas.rst:185 @@ -2013,673 +1210,26 @@ msgstr "" msgid "Place the user's tenant ID in a usable variable, as follows::" msgstr "" -#: ../manage_projects_users_and_roles.rst:34 -msgid "Projects" +#: ../cli_set_compute_quotas.rst:159 +msgid "List the currently set quota values for a tenant user, as follows::" msgstr "" -#: ../cli_cinder_quotas.rst:12 -msgid "Property name" -msgstr "" - -#: ../dashboard_manage_volumes.rst:45 ../dashboard_manage_volumes.rst:70 -msgid "Provider" -msgstr "" - -#: ../dashboard_set_quotas.rst:36 -msgid "Quota Name" -msgstr "" - -#: ../cli_set_compute_quotas.rst:16 -msgid "Quota name" -msgstr "" - -#: ../dashboard_set_quotas.rst:55 -msgid "RAM (MB)" -msgstr "" - -# #-#-#-#-# cli_manage_flavors.pot (Admin User Guide 1.0.0) #-#-#-#-# -# #-#-#-#-# dashboard_manage_flavors.pot (Admin User Guide 1.0.0) #-#-#-#-# -#: ../cli_manage_flavors.rst:53 ../dashboard_manage_flavors.rst:12 -msgid "RAM (in MB)" -msgstr "" - -#: ../dashboard_set_quotas.rst:55 -msgid "RAM megabytes allowed for each instance." -msgstr "" - -#: ../manage_projects_users_and_roles.rst:335 -msgid "Remove a role" -msgstr "" - -#: ../manage_projects_users_and_roles.rst:337 -msgid "Remove a role from a user-project pair:" -msgstr "" - -#: ../manage_projects_users_and_roles.rst:206 -msgid "Roles and role assignments" -msgstr "" - -#: ../cli_manage_flavors.rst:34 -msgid "Root Disk GB" -msgstr "" - -#: ../dashboard_set_quotas.rst:61 -msgid "Rules allowed for each security group." -msgstr "" - -#: ../manage_projects_users_and_roles.rst:339 -msgid "Run :command:`openstack role remove`:" -msgstr "" - -#: ../analyzing-log-files-with-swift-cli.rst:173 -msgid "" -"Run the swift ``list -p 2010-11-15`` command to list objects in the logtest " -"container that begin with the ``2010-11-15`` string." -msgstr "" - -#: ../analyzing-log-files-with-swift-cli.rst:150 -msgid "" -"Run the swift ``list`` command to list objects in the logtest container. " -"Then, for each item in the list, run the swift ``download -o -`` command. " -"Pipe the output into grep to filter the PUT requests. Finally, pipe into " -"``wc -l`` to count the lines." -msgstr "" - -#: ../index.rst:33 -msgid "Search in this guide" -msgstr "" - -#: ../dashboard_set_quotas.rst:61 -msgid "Security Group Rules" -msgstr "" - -#: ../dashboard_set_quotas.rst:58 -msgid "Security Groups" -msgstr "" - -#: ../dashboard_set_quotas.rst:58 -msgid "Security groups allowed for each project." -msgstr "" - -#: ../nova_cli_manage_projects_security.rst:5 -msgid "" -"Security groups are sets of IP filter rules that are applied to all project " -"instances, which define networking access to the instance. Group rules are " -"project specific; project members can edit the default rules for their group " -"and add new rule sets." -msgstr "" - -#: ../dashboard_manage_volumes.rst:97 -msgid "See NIST reference below to see advantages*" -msgstr "" - -#: ../dashboard_manage_instances.rst:70 -msgid "" -"Select a month and click :guilabel:`Submit` to query the instance usage for " -"that month." -msgstr "" - -#: ../dashboard_manage_instances.rst:22 -msgid "" -"Select an instance to create a snapshot from it. From the :guilabel:" -"`Actions` drop-down list, select :guilabel:`Create Snapshot`." -msgstr "" - -#: ../cli_nova_specify_host.rst:3 -msgid "Select hosts where instances are launched" -msgstr "" - -#: ../dashboard_manage_images.rst:84 -msgid "" -"Select the :guilabel:`Public` check box to make the image public. Clear this " -"check box to make the image private. You cannot change the kernel ID, RAM " -"disk ID, or architecture attributes for an image." -msgstr "" - -#: ../dashboard_manage_flavors.rst:80 -msgid "Select the flavor that you want to edit. Click :guilabel:`Edit Flavor`." -msgstr "" - -#: ../dashboard_manage_flavors.rst:95 -msgid "" -"Select the flavor that you want to update. In the drop-down list, click :" -"guilabel:`Update Metadata` or click :guilabel:`No` or :guilabel:`Yes` in " -"the :guilabel:`Metadata` column." -msgstr "" - -#: ../dashboard_manage_flavors.rst:161 -msgid "Select the flavors that you want to delete." -msgstr "" - -#: ../dashboard_manage_images.rst:53 -msgid "Select the image format." -msgstr "" - -#: ../dashboard_manage_images.rst:98 -msgid "Select the images that you want to delete." -msgstr "" - -#: ../dashboard_manage_images.rst:81 -msgid "Select the images that you want to edit. Click :guilabel:`Edit`." -msgstr "" - -#: ../dashboard_manage_instances.rst:43 -msgid "Select the instance for which you want to change the state." -msgstr "" - -#: ../dashboard_admin_manage_roles.rst:50 -msgid "" -"Select the role you want to delete and click the :guilabel:`Delete Roles` " -"button." -msgstr "" - -#: ../dashboard_manage_volumes.rst:148 -msgid "Select the volume or volumes that you want to delete." -msgstr "" - -#: ../dashboard_manage_volumes.rst:127 -msgid "Select the volume type or types that you want to delete." -msgstr "" - -#: ../dashboard_manage_images.rst:62 -msgid "" -"Select this option to ensure that only users with permissions can delete it." -msgstr "" - -#: ../dashboard_manage_images.rst:59 -msgid "Select this option to make the image public to all users." -msgstr "" - -#: ../dashboard_set_quotas.rst:36 -msgid "Service" -msgstr "" - -#: ../cli_keystone_manage_services.rst:7 -msgid "" -"Service catalog template. The Identity Service acts as a service catalog of " -"endpoints for other OpenStack services. The :file:`etc/default_catalog." -"templates` template file defines the endpoints for services. When the " -"Identity Service uses a template file back end, any changes that are made to " -"the endpoints are cached. These changes do not persist when you restart the " -"service or reboot the machine." -msgstr "" - -#: ../networking_advanced_quotas.rst:106 -msgid "Set the :code:`quota_driver` option in the :file:`neutron.conf` file::" -msgstr "" - -#: ../networking_advanced_quotas.rst:135 -msgid "Show information for the quotas extension." -msgstr "" - -#: ../networking_advanced_quotas.rst:173 -msgid "Show per-tenant quota values." -msgstr "" - -#: ../cli_cinder_quotas.rst:54 -msgid "Show the current usage of a per-tenant quota:" -msgstr "" - -#: ../networking_advanced_quotas.rst:95 -msgid "Shows quotas for a specified tenant" -msgstr "" - -#: ../dashboard_set_quotas.rst:64 -msgid "Snapshots" -msgstr "" - -#: ../nova_cli_manage_projects_security.rst:180 -msgid "" -"Source Groups are a special, dynamic way of defining the CIDR of allowed " -"sources. The user specifies a Source Group (Security Group name), and all " -"the users' other Instances using the specified Source Group are selected " -"dynamically. This alleviates the need for individual rules to allow each new " -"member of the cluster." -msgstr "" - -#: ../dashboard_manage_volumes.rst:46 -msgid "Specifies the class responsible for configuring the encryption." -msgstr "" - -#: ../dashboard_manage_volumes.rst:51 -msgid "Specifies the encryption algorithm." -msgstr "" - -#: ../dashboard_manage_volumes.rst:53 -msgid "Specifies the encryption key size." -msgstr "" - -#: ../dashboard_manage_volumes.rst:48 -msgid "" -"Specifies whether the encryption is from the front end (nova) or the back " -"end (cinder)." -msgstr "" - -#: ../manage_projects_users_and_roles.rst:119 -msgid "Specify the project ID to delete a project:" -msgstr "" - -#: ../manage_projects_users_and_roles.rst:81 -msgid "" -"Specify the project ID to update a project. You can update the name, " -"description, and enabled status of a project." -msgstr "" - -#: ../cli_manage_flavors.rst:48 -msgid "Swap" -msgstr "" - -# #-#-#-#-# cli_admin_manage_stacks.pot (Admin User Guide 1.0.0) #-#-#-#-# -# #-#-#-#-# dashboard_admin_manage_stacks.pot (Admin User Guide 1.0.0) #-#-#-#-# -#: ../cli_admin_manage_stacks.rst:11 ../dashboard_admin_manage_stacks.rst:10 -msgid "" -"Templates are used to create stacks, which are collections of resources. For " -"example, a stack might include instances, floating IPs, volumes, security " -"groups, or users. The Orchestration service offers access to all OpenStack " -"core services via a single modular template, with additional orchestration " -"capabilities such as auto-scaling and basic high availability." -msgstr "" - -#: ../networking_advanced_quotas.rst:60 ../networking_advanced_quotas.rst:77 -msgid "The :code:`quota_items` option does not affect these quotas." -msgstr "" - -#: ../networking_advanced_quotas.rst:161 -msgid "" -"The :command:`quota-list` command lists tenants for which the per-tenant " -"quota is enabled. The command does not list tenants with default quota " -"support. You must be an administrative user to run this command::" -msgstr "" - -#: ../networking_advanced_quotas.rst:175 -msgid "" -"The :command:`quota-show` command reports the current set of quota limits " -"for the specified tenant. Non-administrative users can run this command " -"without the ``--tenant_id`` parameter. If per-tenant quota limits are not " -"enabled for the tenant, the command shows the default set of quotas::" -msgstr "" - -#: ../cli_keystone_manage_services.rst:4 -msgid "The Identity Service enables you to define services, as follows:" -msgstr "" - -# #-#-#-#-# cli_admin_manage_stacks.pot (Admin User Guide 1.0.0) #-#-#-#-# -# #-#-#-#-# dashboard_admin_manage_stacks.pot (Admin User Guide 1.0.0) #-#-#-#-# -#: ../cli_admin_manage_stacks.rst:5 ../dashboard_admin_manage_stacks.rst:5 -msgid "" -"The Orchestration service provides a template-based orchestration engine for " -"the OpenStack cloud, which can be used to create and manage cloud " -"infrastructure resources such as storage, networking, instances, and " -"applications as a repeatable running environment." -msgstr "" - -#: ../dashboard_view_cloud_resources.rst:5 -msgid "" -"The Telemetry module provides user-level usage data for OpenStack-based " -"clouds, which can be used for customer billing, system monitoring, or " -"alerts. Data can be collected by notifications sent by existing OpenStack " -"components (for example, usage events emitted from Compute) or by polling " -"the infrastructure (for example, libvirt)." -msgstr "" - -#: ../cli_keystone_manage_services.rst:20 -msgid "" -"The ``auth_token`` middleware supports the use of either a shared secret or " -"users for each service." -msgstr "" - -#: ../nova_cli_manage_projects_security.rst:201 -msgid "" -"The ``cluster`` rule allows ssh access from any other instance that uses the " -"``global_http`` group." -msgstr "" - -#: ../nova_cli_manage_projects_security.rst:120 -msgid "" -"The arguments are positional, and the \"from-port\" and \"to-port\" " -"arguments specify the local port range connections are allowed to access, " -"not the source and destination ports of the connection. For example:" -msgstr "" - -#: ../cli_keystone_manage_services.rst:66 -msgid "The arguments are:" -msgstr "" - -#: ../cli_set_quotas.rst:16 -msgid "" -"The cloud operator typically changes default values because a tenant " -"requires more than ten volumes or 1 TB on a compute node." -msgstr "" - -#: ../networking_advanced_quotas.rst:118 -msgid "" -"The command shows the ``quotas`` extension, which provides per-tenant quota " -"management support::" -msgstr "" - -#: ../dashboard_set_quotas.rst:108 -msgid "" -"The dashboard does not show all possible project quotas. To view and update " -"the quotas for a service, use its command-line client. See :doc:" -"`cli_set_quotas`." -msgstr "" - -#: ../cli_manage_flavors.rst:50 -msgid "The default flavors are:" -msgstr "" - -#: ../dashboard_set_quotas.rst:84 -msgid "The default quota values are displayed." -msgstr "" - -#: ../dashboard_manage_volumes.rst:81 -msgid "" -"The encryption occurs within nova so that the data transmitted over the " -"network is encrypted" -msgstr "" - -#: ../intro-admin.rst:8 -msgid "" -"The examples in this guide show you how to perform tasks by using the " -"following methods:" -msgstr "" - -#: ../cli_manage_flavors.rst:84 -msgid "" -"The flavor ID is a number from 1 to 255 and cannot contain special " -"characters or spaces." -msgstr "" - -#: ../networking_advanced_quotas.rst:193 -msgid "" -"The following command shows the command output for a non-administrative " -"user::" -msgstr "" - -#: ../dashboard_set_quotas.rst:29 -msgid "" -"The following table describes the Compute and Block Storage service quotas:" -msgstr "" - -#: ../dashboard_manage_flavors.rst:9 -msgid "The following table lists the default flavors." -msgstr "" - -#: ../dashboard_manage_images.rst:69 -msgid "" -"The image is queued to be uploaded. It might take several minutes before the " -"status changes from ``Queued`` to ``Active``." -msgstr "" - -#: ../cli_nova_evacuate.rst:28 -msgid "" -"The instance is booted from a new disk, but preserves its configuration " -"including its ID, name, uid, IP address, and so on. The command returns a " -"password::" -msgstr "" - -#: ../cli_nova_migrate.rst:74 -msgid "" -"The instance is booted from a new host, but preserves its configuration " -"including its ID, name, any metadata, IP address, and other properties." -msgstr "" - -#: ../networking_advanced_quotas.rst:22 -msgid "" -"The quota value is defined in the OpenStack Networking :file:`neutron.conf` " -"configuration file. To disable quotas for a specific resource, such as " -"network, subnet, or port, remove a corresponding item from :code:" -"`quota_items`. This example shows the default quota values:" -msgstr "" - -#: ../dashboard_manage_host_aggregates.rst:12 -msgid "" -"The scheduler uses this information to make scheduling decisions. For " -"information, see `Scheduling `__." -msgstr "" - -#: ../analyzing-log-files-with-swift-cli.rst:7 -msgid "The swift client is simple to use, scalable, and flexible." -msgstr "" - -#: ../dashboard_manage_volumes.rst:63 -msgid "" -"The table below provides a few alternatives available for creating encrypted " -"volumes." -msgstr "" - -#: ../dashboard_admin_manage_stacks.rst:23 -msgid "" -"There are no administration-specific tasks that can be done through the " -"dashboard." -msgstr "" - -#: ../nova_cli_manage_projects_security.rst:80 -msgid "" -"These rules are allow type rules as the default is deny. The first column is " -"the IP protocol (one of icmp, tcp, or udp). The second and third columns " -"specify the affected port range. The third column specifies the IP range in " -"CIDR format. This example shows the full port range for all protocols " -"allowed from all IPs." -msgstr "" - -#: ../intro-admin.rst:34 -msgid "" -"This book is written for administrators who maintain and secure an OpenStack " -"cloud installation to serve end users' needs. You should have years of " -"experience with Linux-based tools for system administration. You should also " -"be familiar with OpenStack basics, such as managing projects and users, " -"troubleshooting, performing backup and recovery, and monitoring. For more " -"information, see the `OpenStack Operations Guide `__." -msgstr "" - -#: ../dashboard_manage_volumes.rst:87 -msgid "" -"This could be selected if a cinder plug-in supporting an encrypted back-end " -"block storage device becomes available in the future. TLS or other network " -"encryption would also be needed to protect data as it traverses the network" -msgstr "" - -#: ../analyzing-log-files-with-swift-cli.rst:20 -msgid "" -"This example assumes that ``logtest`` directory contains the following log " -"files::" -msgstr "" - -#: ../networking_advanced_quotas.rst:241 -msgid "" -"This example updates the limit of the number of floating IPs for the " -"specified tenant::" -msgstr "" - -#: ../analyzing-log-files-with-swift-cli.rst:91 -msgid "" -"This example uses the ``-o`` option and a hyphen (``-``) to get information " -"about an object." -msgstr "" - -#: ../index.rst:14 -msgid "" -"This guide documents OpenStack Kilo, OpenStack Juno, and OpenStack Icehouse " -"releases." -msgstr "" - -#: ../cli_admin_manage_environment.rst:5 -msgid "This section includes tasks specific to the OpenStack environment." -msgstr "" - -#: ../dashboard_manage_host_aggregates.rst:47 -msgid "" -"To assign a host to the aggregate, click **+** for the host. The host moves " -"from the :guilabel:`All available hosts` list to the :guilabel:`Selected " -"hosts` list." -msgstr "" - -#: ../manage_projects_users_and_roles.rst:247 -msgid "" -"To assign a user to a project, you must assign the role to a user-project " -"pair. To do this, you need the user, role, and project IDs." -msgstr "" - -#: ../cli_keystone_manage_services.rst:24 -msgid "" -"To authenticate users against the Identity Service, you must create a " -"service user for each OpenStack service. For example, create a service user " -"for the Compute, Block Storage, and Networking services." -msgstr "" - -#: ../manage_projects_users_and_roles.rst:189 -msgid "To change the name and description for a user account:" -msgstr "" - -#: ../networking_advanced_quotas.rst:272 -msgid "" -"To clear per-tenant quota limits, use the :command:`quota-delete` command::" -msgstr "" - -#: ../cli_keystone_manage_services.rst:29 -msgid "" -"To configure the OpenStack services with service users, create a project for " -"all services and create users for each service. Assign the admin role to " -"each service user and project pair. This role enables users to validate " -"tokens and authenticate and authorize other user requests." -msgstr "" - -#: ../cli_manage_flavors.rst:77 -msgid "" -"To create a flavor, specify a name, ID, RAM size, disk size, and the number " -"of VCPUs for the flavor, as follows::" -msgstr "" - -#: ../dashboard_manage_host_aggregates.rst:17 -msgid "To create a host aggregate" -msgstr "" - -#: ../cli_admin_manage_ip_addresses.rst:59 -msgid "To create a range of floating IP addresses, run::" -msgstr "" - -#: ../cli_keystone_manage_services.rst:57 -msgid "To create a service, run this command::" -msgstr "" - -#: ../manage_projects_users_and_roles.rst:148 -msgid "" -"To create a user, you must specify a name. Optionally, you can specify a " -"tenant ID, password, and email address. It is recommended that you include " -"the tenant ID and password because the user cannot log in to the dashboard " -"without this information." -msgstr "" - -#: ../dashboard_manage_images.rst:14 -msgid "" -"To create and manage images as an administrator for other users, use the " -"following procedures." -msgstr "" - -#: ../dashboard_manage_images.rst:10 -msgid "" -"To create and manage images in specified projects as an end user, see the " -"`OpenStack End User Guide `_." -msgstr "" - -#: ../cli_admin_manage_ip_addresses.rst:85 -msgid "To delete a range of floating IP addresses, run::" -msgstr "" - -#: ../cli_keystone_manage_services.rst:141 -msgid "To delete a specified service, specify its ID::" -msgstr "" - -#: ../dashboard_manage_host_aggregates.rst:76 -msgid "" -"To delete host aggregates, locate the host aggregate that you want to edit " -"in the table. Click :guilabel:`More` and select :guilabel:`Delete Host " -"Aggregate`." -msgstr "" - -#: ../cli_set_quotas.rst:33 -msgid "To display all current users for a tenant, run::" +#: ../cli_set_compute_quotas.rst:184 +msgid "To update quota values for a tenant user" msgstr "" #: ../cli_set_compute_quotas.rst:223 msgid "To display the current quota usage for a tenant user" msgstr "" -#: ../dashboard_manage_host_aggregates.rst:63 +#: ../cli_set_compute_quotas.rst:224 msgid "" -"To edit host aggregates, select the host aggregate that you want to edit. " -"Click :guilabel:`Edit Host Aggregate`." +"Use :command:`nova absolute-limits` to get a list of the current quota " +"values and the current quota usage::" msgstr "" -#: ../manage_projects_users_and_roles.rst:90 -msgid "To enable a disabled project:" -msgstr "" - -#: ../manage_projects_users_and_roles.rst:183 -msgid "To enable a disabled user account:" -msgstr "" - -#: ../cli_keystone_manage_services.rst:84 -msgid "To get details for a service, run this command::" -msgstr "" - -#: ../dashboard_manage_instances.rst:30 -msgid "" -"To launch an instance from the snapshot, select the snapshot and click " -"Launch. For information about launching instances, see the `OpenStack End " -"User Guide `__." -msgstr "" - -#: ../cli_admin_manage_ip_addresses.rst:29 -msgid "To list all floating IP addresses for all projects, run::" -msgstr "" - -#: ../cli_nova_evacuate.rst:15 -msgid "" -"To list hosts and find a different host for the evacuated instance, run::" -msgstr "" - -#: ../networking_advanced_quotas.rst:114 -msgid "To list the Networking extensions, run this command::" -msgstr "" - -#: ../cli_nova_migrate.rst:14 -msgid "To list the VMs you want to migrate, run::" -msgstr "" - -#: ../dashboard_manage_host_aggregates.rst:55 -msgid "To manage host aggregates" -msgstr "" - -#: ../dashboard_manage_host_aggregates.rst:69 -msgid "" -"To manage hosts, locate the host aggregate that you want to edit in the " -"table. Click :guilabel:`More` and select :guilabel:`Manage Hosts`." -msgstr "" - -#: ../cli_nova_migrate.rst:27 -msgid "" -"To migrate of an instance and watch the status, use this example script:" -msgstr "" - -#: ../cli_nova_evacuate.rst:38 -msgid "" -"To preserve the user disk data on the evacuated server, deploy OpenStack " -"Compute with a shared file system. To configure your system, see `Configure " -"migrations `_ in OpenStack Cloud Administrator Guide. In the following " -"example, the password remains unchanged::" -msgstr "" - -#: ../cli_nova_evacuate.rst:11 -msgid "" -"To preserve user data on server disk, you must configure shared storage on " -"the target host. Also, you must validate that the current VM host is down; " -"otherwise, the evacuation fails with an error." +#: ../cli_set_quotas.rst:3 +msgid "Manage quotas" msgstr "" # #-#-#-#-# cli_set_quotas.pot (Admin User Guide 1.0.0) #-#-#-#-# @@ -2693,239 +1243,6 @@ msgid "" "the tenant-user level." msgstr "" -#: ../cli_nova_specify_host.rst:9 -msgid "" -"To select the host where instances are launched, use the ``--" -"availability_zone ZONE:HOST`` parameter on the :command:`nova boot` command." -msgstr "" - -#: ../networking_advanced_quotas.rst:137 -msgid "To show information for the ``quotas`` extension, run this command::" -msgstr "" - -#: ../cli_nova_specify_host.rst:17 -msgid "" -"To specify which roles can launch an instance on a specified host, enable " -"the :code:`create:forced_host` option in the :file:`policy.json` file. By " -"default, this option is enabled for only the admin role." -msgstr "" - -#: ../manage_projects_users_and_roles.rst:84 -msgid "To temporarily disable a project:" -msgstr "" - -#: ../manage_projects_users_and_roles.rst:173 -msgid "To temporarily disable a user account:" -msgstr "" - -#: ../cli_cinder_quotas.rst:83 -msgid "" -"To update Block Storage service quotas, place the tenant ID in a variable::" -msgstr "" - -#: ../cli_cinder_quotas.rst:77 -msgid "" -"To update a default value for a new project, update the property in the :" -"guilabel:`cinder.quota` section of the :file:`/etc/cinder/cinder.conf` file. " -"For more information, see the `Block Storage Configuration Reference `_." -msgstr "" - -#: ../cli_set_compute_quotas.rst:184 -msgid "To update quota values for a tenant user" -msgstr "" - -#: ../cli_set_compute_quotas.rst:113 -msgid "To update quota values for an existing tenant (project)" -msgstr "" - -#: ../networking_advanced_quotas.rst:237 -msgid "" -"To update the limits for an L3 resource such as, router or floating IP, you " -"must define new values for the quotas after the ``--`` directive." -msgstr "" - -#: ../manage_projects_users_and_roles.rst:96 -msgid "To update the name of a project:" -msgstr "" - -#: ../intro-admin.rst:27 -msgid "" -"To use the OpenStack APIs, it helps to be familiar with HTTP/1.1, RESTful " -"web services, the OpenStack services, and JSON or XML data serialization " -"formats." -msgstr "" - -#: ../manage_projects_users_and_roles.rst:102 -msgid "To verify your changes, show information for the updated project:" -msgstr "" - -#: ../cli_set_compute_quotas.rst:143 ../cli_set_compute_quotas.rst:218 -msgid "" -"To view a list of options for the :command:`quota-update` command, run::" -msgstr "" - -#: ../cli_set_quotas.rst:21 -msgid "To view all tenants (projects), run::" -msgstr "" - -#: ../cli_set_compute_quotas.rst:48 -msgid "To view and update default quota values" -msgstr "" - -#: ../cli_set_compute_quotas.rst:150 -msgid "To view quota values for a tenant user" -msgstr "" - -#: ../cli_set_compute_quotas.rst:82 -msgid "To view quota values for an existing tenant (project)" -msgstr "" - -#: ../cli_nova_specify_host.rst:22 -msgid "" -"To view the list of valid compute hosts, use the :command:`nova hypervisor-" -"list` command, as follows::" -msgstr "" - -#: ../dashboard_manage_instances.rst:58 -msgid "Track usage" -msgstr "" - -#: ../dashboard_set_quotas.rst:16 -msgid "" -"Typically, you change quotas when a project needs more than ten volumes or 1 " -"|nbsp| TB on a compute node." -msgstr "" - -#: ../dashboard_manage_flavors.rst:87 -msgid "Update Metadata" -msgstr "" - -#: ../cli_set_compute_quotas.rst:73 -msgid "Update a default value for a new tenant, as follows::" -msgstr "" - -#: ../cli_set_compute_quotas.rst:118 ../cli_set_compute_quotas.rst:193 -msgid "Update a particular quota value, as follows::" -msgstr "" - -#: ../cli_cinder_quotas.rst:88 -msgid "Update a particular quota value::" -msgstr "" - -#: ../manage_projects_users_and_roles.rst:79 -msgid "Update a project" -msgstr "" - -#: ../manage_projects_users_and_roles.rst:169 -msgid "Update a user" -msgstr "" - -#: ../dashboard_manage_flavors.rst:72 -msgid "Update flavors" -msgstr "" - -#: ../dashboard_manage_images.rst:73 -msgid "Update images" -msgstr "" - -#: ../dashboard_set_quotas.rst:93 -msgid "Update project quotas" -msgstr "" - -#: ../networking_advanced_quotas.rst:207 -msgid "Update quota values for a specified tenant." -msgstr "" - -#: ../networking_advanced_quotas.rst:98 -msgid "Updates quotas for a specified tenant" -msgstr "" - -#: ../analyzing-log-files-with-swift-cli.rst:18 -msgid "Upload and analyze log files" -msgstr "" - -#: ../analyzing-log-files-with-swift-cli.rst:39 -msgid "Upload the log files into the ``logtest`` container::" -msgstr "" - -#: ../cli_admin_manage_ip_addresses.rst:77 -msgid "" -"Use **nmap** to check a range's availability. For example, 192.168.1.56/29 " -"represents a small range of addresses (192.168.1.56-63, with 57-62 usable), " -"and you could run the command **nmap -sn 192.168.1.56/29** to check whether " -"the entire range is currently unused." -msgstr "" - -#: ../cli_set_compute_quotas.rst:224 -msgid "" -"Use :command:`nova absolute-limits` to get a list of the current quota " -"values and the current quota usage::" -msgstr "" - -#: ../analyzing-log-files-with-swift-cli.rst:146 -msgid "" -"Use a bash for loop with awk and swift with the ``-o`` or ``--output`` " -"option and a hyphen (``-``) to discover how many PUT requests are in each " -"log file." -msgstr "" - -#: ../networking_advanced_quotas.rst:209 -msgid "" -"Use the :command:`quota-update` command to update a quota for a specified " -"tenant::" -msgstr "" - -#: ../dashboard_manage_instances.rst:60 -msgid "Use the Overview category to track usage of instances for each project." -msgstr "" - -#: ../analyzing-log-files-with-swift-cli.rst:94 -msgid "" -"Use the swift ``download`` command to download the object. On this command, " -"stream the output to ``awk`` to break down requests by return code and the " -"date ``2200 on November 16th, 2010``." -msgstr "" - -#: ../analyzing-log-files-with-swift-cli.rst:9 -msgid "" -"Use the swift client ``-o`` or ``-output`` option to get short answers to " -"questions about logs." -msgstr "" - -#: ../analyzing-log-files-with-swift-cli.rst:5 -msgid "Use the swift command-line client to analyze log files." -msgstr "" - -#: ../networking_advanced_quotas.rst:86 -msgid "Use these commands to manage per-tenant quotas:" -msgstr "" - -#: ../manage_projects_users_and_roles.rst:126 -msgid "User" -msgstr "" - -#: ../manage_projects_users_and_roles.rst:229 -msgid "" -"Users can be members of multiple projects. To assign users to multiple " -"projects, define a role and assign that role to a user-project pair." -msgstr "" - -#: ../dashboard_set_quotas.rst:19 -msgid "" -"Using the Dashboard, you can view default Compute and Block Storage quotas " -"for new tenants, as well as update quotas for existing tenants." -msgstr "" - -#: ../dashboard_set_quotas.rst:23 -msgid "" -"Using the command-line interface, you can manage quotas for the OpenStack " -"Compute service, the OpenStack Block Storage service, and the OpenStack " -"Networking service (see :doc:`cli_set_quotas`). Additionally, you can update " -"Compute service quotas for tenant users." -msgstr "" - #: ../cli_set_quotas.rst:12 msgid "" "Using the command-line interface, you can manage quotas for the OpenStack " @@ -2933,505 +1250,384 @@ msgid "" "Networking service." msgstr "" +#: ../cli_set_quotas.rst:16 +msgid "" +"The cloud operator typically changes default values because a tenant " +"requires more than ten volumes or 1 TB on a compute node." +msgstr "" + +#: ../cli_set_quotas.rst:21 +msgid "To view all tenants (projects), run::" +msgstr "" + +#: ../cli_set_quotas.rst:33 +msgid "To display all current users for a tenant, run::" +msgstr "" + +#: ../dashboard.rst:3 +msgid "OpenStack dashboard" +msgstr "" + +#: ../dashboard.rst:5 +msgid "" +"As a cloud administrative user, the OpenStack dashboard lets you create and " +"manage projects, users, images, and flavors. You can also set quotas and " +"create and manage services. For information about using the dashboard to " +"perform end user tasks, see the `OpenStack End User Guide `__." +msgstr "" + +#: ../dashboard_admin_manage_roles.rst:3 +msgid "Create and manage roles" +msgstr "" + +#: ../dashboard_admin_manage_roles.rst:5 +msgid "" +"A role is a personality that a user assumes to perform a specific set of " +"operations. A role includes a set of rights and privileges. A user assumes " +"that role inherits those rights and privileges." +msgstr "" + +#: ../dashboard_admin_manage_roles.rst:9 +msgid "" +"OpenStack Identity service defines a user's role on a project, but it is " +"completely up to the individual service to define what that role means. This " +"is referred to as the service's policy. To get details about what the " +"privileges for each role are, refer to the :file:`policy.json` file " +"available for each service in the :file:`/etc/SERVICE/policy.json` file. For " +"example, the policy defined for OpenStack Identity service is defined in " +"the :file:`/etc/keystone/policy.json` file." +msgstr "" + +# #-#-#-#-# dashboard_admin_manage_roles.pot (Admin User Guide 1.0.0) #-#-#-#-# +# #-#-#-#-# manage_projects_users_and_roles.pot (Admin User Guide 1.0.0) #-#-#-#-# +#: ../dashboard_admin_manage_roles.rst:20 +#: ../manage_projects_users_and_roles.rst:227 +msgid "Create a role" +msgstr "" + +#: ../dashboard_admin_manage_roles.rst:22 +#: ../dashboard_admin_manage_roles.rst:33 +#: ../dashboard_admin_manage_roles.rst:47 +msgid "" +"Log in to the dashboard and choose the :guilabel:`admin` project from the :" +"guilabel:`CURRENT PROJECT` drop-down list." +msgstr "" + +#: ../dashboard_admin_manage_roles.rst:24 +#: ../dashboard_admin_manage_roles.rst:35 +#: ../dashboard_admin_manage_roles.rst:49 +msgid "On the :guilabel:`Admin` tab, click the :guilabel:`Roles` category." +msgstr "" + +#: ../dashboard_admin_manage_roles.rst:25 +msgid "Click the :guilabel:`Create Role` button." +msgstr "" + +#: ../dashboard_admin_manage_roles.rst:27 +msgid "In the :guilabel:`Create Role` window, enter a name for the role." +msgstr "" + +#: ../dashboard_admin_manage_roles.rst:28 +msgid "Click the :guilabel:`Create Role` button to confirm your changes." +msgstr "" + +#: ../dashboard_admin_manage_roles.rst:31 +msgid "Edit a role" +msgstr "" + +#: ../dashboard_admin_manage_roles.rst:36 +msgid "Click the :guilabel:`Edit` button." +msgstr "" + +#: ../dashboard_admin_manage_roles.rst:38 +msgid "In the :guilabel:`Update Role` window, enter a new name for the role." +msgstr "" + +#: ../dashboard_admin_manage_roles.rst:39 +msgid "Click the :guilabel:`Update Role` button to confirm your changes." +msgstr "" + #: ../dashboard_admin_manage_roles.rst:41 msgid "Using the dashboard, you can edit only the name assigned to a role." msgstr "" -#: ../analyzing-log-files-with-swift-cli.rst:98 +#: ../dashboard_admin_manage_roles.rst:45 +msgid "Delete a role" +msgstr "" + +#: ../dashboard_admin_manage_roles.rst:50 msgid "" -"Using the log line format, find the request type in column 9 and the return " -"code in column 12." +"Select the role you want to delete and click the :guilabel:`Delete Roles` " +"button." msgstr "" -#: ../dashboard_manage_volumes.rst:109 +#: ../dashboard_admin_manage_roles.rst:52 msgid "" -"Using this selection for aes-xts, the underlying key size would only be 128-" -"bits*" -msgstr "" - -#: ../dashboard_manage_volumes.rst:104 -msgid "" -"Using this selection for aes-xts, the underlying key size would only be 256-" -"bits*" -msgstr "" - -# #-#-#-#-# cli_manage_flavors.pot (Admin User Guide 1.0.0) #-#-#-#-# -# #-#-#-#-# dashboard_manage_flavors.pot (Admin User Guide 1.0.0) #-#-#-#-# -# #-#-#-#-# dashboard_set_quotas.pot (Admin User Guide 1.0.0) #-#-#-#-# -#: ../cli_manage_flavors.rst:27 ../cli_manage_flavors.rst:53 -#: ../dashboard_manage_flavors.rst:12 ../dashboard_set_quotas.rst:67 -msgid "VCPUs" -msgstr "" - -#: ../manage_projects_users_and_roles.rst:308 -msgid "Verify the role assignment:" -msgstr "" - -#: ../manage_projects_users_and_roles.rst:345 -msgid "Verify the role removal:" -msgstr "" - -#: ../cli_cinder_quotas.rst:20 -msgid "View Block Storage quotas" -msgstr "" - -#: ../cli_cinder_quotas.rst:37 -msgid "View Block Storage service quotas for a project::" -msgstr "" - -#: ../nova_cli_manage_projects_security.rst:149 -msgid "View all rules for the new security group, as follows:" -msgstr "" - -#: ../dashboard_set_quotas.rst:5 -msgid "View and manage quotas" -msgstr "" - -#: ../cli_set_compute_quotas.rst:46 -msgid "View and update Compute quotas for a tenant (project)" -msgstr "" - -#: ../cli_set_compute_quotas.rst:148 -msgid "View and update Compute quotas for a tenant user" -msgstr "" - -#: ../dashboard_manage_resources.rst:3 -msgid "View cloud resources" -msgstr "" - -#: ../dashboard_view_cloud_resources.rst:3 -msgid "View cloud usage statistics" -msgstr "" - -#: ../dashboard_set_quotas.rst:77 -msgid "View default project quotas" -msgstr "" - -#: ../manage_projects_users_and_roles.rst:322 -msgid "View details for a specified role:" -msgstr "" - -#: ../dashboard_view_cloud_resources.rst:25 -msgid "View resource statistics" -msgstr "" - -#: ../manage_projects_users_and_roles.rst:320 -msgid "View role details" -msgstr "" - -#: ../dashboard_manage_services.rst:3 -msgid "View services information" -msgstr "" - -#: ../nova_cli_manage_projects_security.rst:61 -msgid "View the details of a group, as follows:" -msgstr "" - -#: ../dashboard_manage_services.rst:14 -msgid "View the following information on these tabs:" -msgstr "" - -#: ../dashboard_set_quotas.rst:38 -msgid "Volume gigabytes allowed for each project." -msgstr "" - -#: ../cli_cinder_quotas.rst:14 -msgid "Volume gigabytes allowed for each tenant." -msgstr "" - -#: ../dashboard_set_quotas.rst:64 -msgid "Volume snapshots allowed for each project." -msgstr "" - -#: ../cli_cinder_quotas.rst:15 -msgid "Volume snapshots allowed for each tenant." -msgstr "" - -#: ../dashboard_set_quotas.rst:70 -msgid "Volumes" -msgstr "" - -#: ../dashboard_set_quotas.rst:70 -msgid "Volumes allowed for each project." -msgstr "" - -#: ../cli_cinder_quotas.rst:16 -msgid "Volumes allowed for each tenant." -msgstr "" - -#: ../dashboard_manage_volumes.rst:5 -msgid "" -"Volumes are the Block Storage devices that you attach to instances to enable " -"persistent storage. Users can attach a volume to a running instance or " -"detach a volume and attach it to another instance at any time. For " -"information about using the dashboard to create and manage volumes as an end " -"user, see the `OpenStack End User Guide `_." -msgstr "" - -#: ../nova_cli_manage_projects_security.rst:88 -msgid "" -"When adding a new security group, you should pick a descriptive but brief " -"name. This name shows up in brief descriptions of the instances that use it " -"where the longer description field often does not. For example, seeing that " -"an instance is using security group \"http\" is much easier to understand " -"than \"bobs\\_group\" or \"secgrp1\"." -msgstr "" - -#: ../dashboard_manage_host_aggregates.rst:38 -msgid "" -"When the host aggregate is exposed as an availability zone, select the " -"availability zone when you launch an instance." -msgstr "" - -#: ../dashboard_manage_host_aggregates.rst:41 -msgid "" -"When the host aggregate is not exposed as an availability zone, select a " -"flavor and its extra specs to target the host aggregate." -msgstr "" - -#: ../dashboard_manage_volumes.rst:119 -msgid "When you delete a volume type, volumes of that type are not deleted." -msgstr "" - -#: ../dashboard_manage_volumes.rst:139 -msgid "" -"When you delete an instance, the data of its attached volumes is not " -"destroyed." -msgstr "" - -#: ../networking_advanced_quotas.rst:110 -msgid "" -"When you set this option, the output for Networking commands shows " -"``quotas``." -msgstr "" - -#: ../cli_nova_migrate.rst:8 -msgid "" -"When you want to move an instance from one compute host to another, you can " -"use the ``nova migrate`` command. The scheduler chooses the destination " -"compute host based on its settings. This process does not assume that the " -"instance has shared storage available on the target host." -msgstr "" - -#: ../intro-admin.rst:32 -msgid "Who should read this book?" -msgstr "" - -#: ../cli_nova_specify_host.rst:5 -msgid "" -"With the appropriate permissions, you can select which host instances are " -"launched on and which roles can boot instances on this host." -msgstr "" - -#: ../dashboard_manage_host_aggregates.rst:51 -msgid "" -"You can add one host to one or more aggregates. To add a host to an existing " -"aggregate, edit the aggregate." -msgstr "" - -#: ../cli_manage_flavors.rst:62 -msgid "" -"You can create and manage flavors with the nova **flavor-*** commands " -"provided by the ``python-novaclient`` package." -msgstr "" - -#: ../nova_cli_manage_projects_security.rst:134 -msgid "" -"You can create complex rule sets by creating additional rules. For example, " -"if you want to pass both HTTP and HTTPS traffic, run:" -msgstr "" - -#: ../manage_projects_users_and_roles.rst:11 -msgid "" -"You can define actions for OpenStack service roles in the ``/etc/PROJECT``/" -"policy.json files. For example, define actions for Compute service roles in " -"the ``/etc/nova/policy.json`` file." -msgstr "" - -#: ../cli_nova_manage_services.rst:4 -msgid "" -"You can enable and disable Compute services. The following examples disable " -"and enable the ``nova-compute`` service." -msgstr "" - -#: ../manage_projects_users_and_roles.rst:15 -msgid "" -"You can manage projects, users, and roles independently from each other." -msgstr "" - -#: ../intro-admin.rst:19 -msgid "You can modify these examples for your specific use cases." -msgstr "" - -#: ../dashboard_view_cloud_resources.rst:13 -msgid "" -"You can only view metering statistics on the dashboard (available only to " -"administrators). The Telemetry service must be set up and administered " -"through the :command:`ceilometer` command-line interface (CLI)." -msgstr "" - -#: ../dashboard_set_quotas.rst:87 -msgid "" -"You can sort the table by clicking on either the :guilabel:`Quota Name` or :" -"guilabel:`Limit` column headers." -msgstr "" - -#: ../dashboard_manage_instances.rst:62 -msgid "" -"You can track costs per month by showing meters like number of VCPUs, disks, " -"RAM, and uptime of all your instances." -msgstr "" - -#: ../networking_advanced_quotas.rst:223 -msgid "You can update quotas for multiple resources through one command::" -msgstr "" - -#: ../networking_advanced_quotas.rst:255 -msgid "" -"You can update the limits of multiple resources by including L2 resources " -"and L3 resource through one command::" -msgstr "" - -#: ../manage_projects_users_and_roles.rst:171 -msgid "You can update the name, email address, and enabled status for a user." -msgstr "" - -#: ../analyzing-log-files-with-swift-cli.rst:12 -msgid "" -"You can use the ``-o`` or ``--output`` option with a single object download " -"to redirect the command output to a specific file or to STDOUT (``-``). The " -"ability to redirect the output to STDOUT enables you to pipe (``|``) data " -"without saving it to disk first." -msgstr "" - -#: ../nova_cli_manage_projects_security.rst:15 -msgid "" -"You can use the ``allow_same_net_traffic`` option in the :file:`/etc/nova/" -"nova.conf` file to globally control whether the rules apply to hosts which " -"share a network." +"In the :guilabel:`Confirm Delete Roles` window, click :guilabel:`Delete " +"Roles` to confirm the deletion." msgstr "" # #-#-#-#-# dashboard_admin_manage_roles.pot (Admin User Guide 1.0.0) #-#-#-#-# # #-#-#-#-# dashboard_manage_images.pot (Admin User Guide 1.0.0) #-#-#-#-# -#: ../dashboard_admin_manage_roles.rst:55 ../dashboard_manage_images.rst:103 +#: ../dashboard_admin_manage_roles.rst:55 ../dashboard_manage_images.rst:107 msgid "You cannot undo this action." msgstr "" -#: ../cli_admin_manage_ip_addresses.rst:70 +#: ../dashboard_admin_manage_stacks.rst:3 +msgid "Launch and manage stacks using the Dashboard" +msgstr "" + +#: ../dashboard_admin_manage_stacks.rst:5 msgid "" -"You should use a range of free IP addresses that is correct for your " -"network. If you are not sure, at least try to avoid the DHCP address range:" +"The Orchestration service provides a template-based orchestration engine for " +"the OpenStack cloud. Orchestration services create and manage cloud " +"infrastructure resources such as storage, networking, instances, and " +"applications as a repeatable running environment." msgstr "" -#: ../dashboard_manage_volumes.rst:114 +#: ../dashboard_admin_manage_stacks.rst:11 msgid "" -"`*` Source `NIST SP 800-38E `_" +"Administrators use templates to create stacks, which are collections of " +"resources. For example, a stack might include instances, floating IPs, " +"volumes, security groups, or users. The Orchestration service offers access " +"to all OpenStack core services via a single modular template, with " +"additional orchestration capabilities such as auto-scaling and basic high " +"availability." msgstr "" -#: ../cli_nova_migrate.rst:71 -msgid "" -"``ERROR (Forbidden): Policy doesn't allow compute_extension:admin_actions:" -"migrate to be performed. (HTTP 403)``" -msgstr "" - -#: ../nova_cli_manage_projects_security.rst:28 -msgid "``False``, security groups are enforced for all connections." -msgstr "" - -#: ../nova_cli_manage_projects_security.rst:21 -msgid "" -"``True`` (default), hosts on the same subnet are not filtered and are " -"allowed to pass all types of traffic between them. On a flat network, this " -"allows all instances from all projects unfiltered communication. With VLAN " -"networking, this allows access between instances within the same project. " -"You can also simulate this setting by configuring the default security group " -"to allow all traffic from the subnet." -msgstr "" - -#: ../cli_keystone_manage_services.rst:66 -msgid "``service_description``: the description of the service." -msgstr "" - -#: ../cli_keystone_manage_services.rst:62 -msgid "``service_name``: the unique name of the new service." -msgstr "" - -#: ../cli_keystone_manage_services.rst:63 -msgid "" -"``service_type``: the service type, such as ``identity``, ``compute``, " -"``network``, ``image``, ``object-store`` or any other service identifier " -"string." -msgstr "" - -#: ../dashboard_admin_manage_stacks.rst:19 +#: ../dashboard_admin_manage_stacks.rst:22 msgid "" "administrative tasks on the command line, see :doc:`cli_admin_manage_stacks`." msgstr "" -#: ../dashboard_manage_volumes.rst:100 -msgid "aes-cbc-essiv" +#: ../dashboard_admin_manage_stacks.rst:26 +msgid "" +"There are no administration-specific tasks that can be done through the " +"Dashboard." msgstr "" -#: ../dashboard_manage_volumes.rst:97 -msgid "aes-xts-plain64 (Recommended)" +#: ../dashboard_admin_manage_stacks.rst:29 +msgid "" +"the basic creation and deletion of Orchestration stacks, refer to the " +"`OpenStack End User Guide `__." msgstr "" -#: ../dashboard_manage_volumes.rst:87 -msgid "back-end" +#: ../dashboard_manage_flavors.rst:5 +msgid "" +"In OpenStack, a flavor defines the compute, memory, and storage capacity of " +"a virtual server, also known as an instance. As an administrative user, you " +"can create, edit, and delete flavors." msgstr "" -#: ../cli_set_compute_quotas.rst:18 -msgid "cores" +#: ../dashboard_manage_flavors.rst:9 +msgid "The following table lists the default flavors." msgstr "" -#: ../cli_set_compute_quotas.rst:20 -msgid "fixed-ips" +#: ../dashboard_manage_flavors.rst:22 +msgid "Create flavors" msgstr "" -#: ../cli_set_compute_quotas.rst:24 -msgid "floating-ips" -msgstr "" - -#: ../dashboard_manage_volumes.rst:81 -msgid "front-end (Recommended)" -msgstr "" - -#: ../cli_cinder_quotas.rst:14 -msgid "gigabytes" -msgstr "" - -#: ../dashboard_manage_flavors.rst:139 -msgid "hw:watchdog_action" -msgstr "" - -#: ../dashboard_manage_flavors.rst:141 -msgid "hw_rng:allowed" -msgstr "" - -#: ../dashboard_manage_flavors.rst:143 -msgid "hw_rng:rate_bytes" -msgstr "" - -#: ../dashboard_manage_flavors.rst:145 -msgid "hw_rng:rate_period" -msgstr "" - -#: ../cli_set_compute_quotas.rst:26 -msgid "injected-file-content-bytes" -msgstr "" - -#: ../cli_set_compute_quotas.rst:28 -msgid "injected-file-path-bytes" -msgstr "" - -#: ../cli_set_compute_quotas.rst:30 -msgid "injected-files" -msgstr "" - -#: ../cli_set_compute_quotas.rst:32 -msgid "instances" -msgstr "" - -#: ../cli_set_compute_quotas.rst:34 -msgid "key-pairs" -msgstr "" - -# #-#-#-#-# cli_manage_flavors.pot (Admin User Guide 1.0.0) #-#-#-#-# # #-#-#-#-# dashboard_manage_flavors.pot (Admin User Guide 1.0.0) #-#-#-#-# -#: ../cli_manage_flavors.rst:58 ../dashboard_manage_flavors.rst:17 -msgid "m1.large" +# #-#-#-#-# dashboard_manage_host_aggregates.pot (Admin User Guide 1.0.0) #-#-#-#-# +# #-#-#-#-# dashboard_manage_images.pot (Admin User Guide 1.0.0) #-#-#-#-# +#: ../dashboard_manage_flavors.rst:24 ../dashboard_manage_flavors.rst:74 +#: ../dashboard_manage_flavors.rst:89 ../dashboard_manage_flavors.rst:155 +#: ../dashboard_manage_host_aggregates.rst:19 +#: ../dashboard_manage_images.rst:23 +msgid "Log in to the dashboard." msgstr "" -# #-#-#-#-# cli_manage_flavors.pot (Admin User Guide 1.0.0) #-#-#-#-# # #-#-#-#-# dashboard_manage_flavors.pot (Admin User Guide 1.0.0) #-#-#-#-# -#: ../cli_manage_flavors.rst:57 ../dashboard_manage_flavors.rst:16 -msgid "m1.medium" +# #-#-#-#-# dashboard_manage_images.pot (Admin User Guide 1.0.0) #-#-#-#-# +#: ../dashboard_manage_flavors.rst:26 ../dashboard_manage_flavors.rst:76 +#: ../dashboard_manage_flavors.rst:91 ../dashboard_manage_flavors.rst:157 +#: ../dashboard_manage_images.rst:25 +msgid "" +"Choose the :guilabel:`admin` project from the drop-down list at the top of " +"the page." msgstr "" -# #-#-#-#-# cli_manage_flavors.pot (Admin User Guide 1.0.0) #-#-#-#-# -# #-#-#-#-# dashboard_manage_flavors.pot (Admin User Guide 1.0.0) #-#-#-#-# -#: ../cli_manage_flavors.rst:56 ../dashboard_manage_flavors.rst:15 -msgid "m1.small" +#: ../dashboard_manage_flavors.rst:28 ../dashboard_manage_flavors.rst:78 +#: ../dashboard_manage_flavors.rst:93 ../dashboard_manage_flavors.rst:159 +msgid "" +"In the :guilabel:`Admin` tab, open the :guilabel:`System` tab and click the :" +"guilabel:`Flavors` category." msgstr "" -# #-#-#-#-# cli_manage_flavors.pot (Admin User Guide 1.0.0) #-#-#-#-# -# #-#-#-#-# dashboard_manage_flavors.pot (Admin User Guide 1.0.0) #-#-#-#-# -#: ../cli_manage_flavors.rst:55 ../dashboard_manage_flavors.rst:14 -msgid "m1.tiny" +#: ../dashboard_manage_flavors.rst:30 ../dashboard_manage_flavors.rst:69 +msgid "Click :guilabel:`Create Flavor`." msgstr "" -# #-#-#-#-# cli_manage_flavors.pot (Admin User Guide 1.0.0) #-#-#-#-# -# #-#-#-#-# dashboard_manage_flavors.pot (Admin User Guide 1.0.0) #-#-#-#-# -#: ../cli_manage_flavors.rst:59 ../dashboard_manage_flavors.rst:18 -msgid "m1.xlarge" +#: ../dashboard_manage_flavors.rst:31 +msgid "" +"In the :guilabel:`Create Flavor` window, enter or select the parameters for " +"the flavor." msgstr "" -#: ../cli_set_compute_quotas.rst:36 -msgid "metadata-items" +#: ../dashboard_manage_flavors.rst:34 +msgid "**Flavor info tab**" msgstr "" -#: ../networking_advanced_quotas.rst:89 -msgid "neutron quota-delete" +#: ../dashboard_manage_flavors.rst:37 +msgid "**Name**" msgstr "" -#: ../networking_advanced_quotas.rst:92 -msgid "neutron quota-list" +#: ../dashboard_manage_flavors.rst:37 +msgid "Enter the flavor name." msgstr "" -#: ../networking_advanced_quotas.rst:95 -msgid "neutron quota-show" +#: ../dashboard_manage_flavors.rst:38 +msgid "**ID**" msgstr "" -#: ../networking_advanced_quotas.rst:98 -msgid "neutron quota-update" +#: ../dashboard_manage_flavors.rst:38 +msgid "OpenStack generates the flavor ID." msgstr "" -#: ../dashboard_manage_volumes.rst:77 -msgid "nova.volume.encryptors. cryptsetup. CryptsetupEncryptor" +#: ../dashboard_manage_flavors.rst:39 +msgid "**VCPUs**" msgstr "" -#: ../dashboard_manage_volumes.rst:70 -msgid "nova.volume.encryptors. luks.LuksEncryptor (Recommended)" +#: ../dashboard_manage_flavors.rst:39 +msgid "Enter the number of virtual CPUs to use." msgstr "" -#: ../dashboard_manage_flavors.rst:109 -msgid "quota:cpu_limit" +#: ../dashboard_manage_flavors.rst:41 +msgid "**RAM MB**" +msgstr "" + +#: ../dashboard_manage_flavors.rst:41 +msgid "Enter the amount of RAM to use, in megabytes." +msgstr "" + +#: ../dashboard_manage_flavors.rst:43 +msgid "**Root Disk GB**" +msgstr "" + +#: ../dashboard_manage_flavors.rst:43 +msgid "" +"Enter the amount of disk space in gigabytes to use for the root (/) " +"partition." +msgstr "" + +#: ../dashboard_manage_flavors.rst:46 +msgid "**Ephemeral Disk GB**" +msgstr "" + +#: ../dashboard_manage_flavors.rst:46 +msgid "" +"Enter the amount of disk space in gigabytes to use for the ephemeral " +"partition. If unspecified, the value is 0 by default." +msgstr "" + +#: ../dashboard_manage_flavors.rst:51 +msgid "" +"Ephemeral disks offer machine local disk storage linked to the life cycle of " +"a VM instance. When a VM is terminated, all data on the ephemeral disk is " +"lost. Ephemeral disks are not included in any snapshots." +msgstr "" + +#: ../dashboard_manage_flavors.rst:57 +msgid "**Swap Disk MB**" +msgstr "" + +#: ../dashboard_manage_flavors.rst:57 +msgid "" +"Enter the amount of swap space (in megabytes) to use. If unspecified, the " +"default is 0." +msgstr "" + +#: ../dashboard_manage_flavors.rst:62 +msgid "" +"In the :guilabel:`Flavor Access` tab, you can control access to the flavor " +"by moving projects from the :guilabel:`All Projects` column to the :guilabel:" +"`Selected Projects` column." +msgstr "" + +#: ../dashboard_manage_flavors.rst:66 +msgid "" +"Only projects in the :guilabel:`Selected Projects` column can use the " +"flavor. If there are no projects in the right column, all projects can use " +"the flavor." +msgstr "" + +#: ../dashboard_manage_flavors.rst:72 +msgid "Update flavors" +msgstr "" + +#: ../dashboard_manage_flavors.rst:80 +msgid "Select the flavor that you want to edit. Click :guilabel:`Edit Flavor`." +msgstr "" + +#: ../dashboard_manage_flavors.rst:82 +msgid "" +"In the :guilabel:`Edit Flavor` window, you can change the flavor name, " +"VCPUs, RAM, root disk, ephemeral disk, and swap disk values." +msgstr "" + +#: ../dashboard_manage_flavors.rst:84 ../dashboard_manage_flavors.rst:100 +msgid "Click :guilabel:`Save`." +msgstr "" + +#: ../dashboard_manage_flavors.rst:87 +msgid "Update Metadata" +msgstr "" + +#: ../dashboard_manage_flavors.rst:95 +msgid "" +"Select the flavor that you want to update. In the drop-down list, click :" +"guilabel:`Update Metadata` or click :guilabel:`No` or :guilabel:`Yes` in " +"the :guilabel:`Metadata` column." +msgstr "" + +#: ../dashboard_manage_flavors.rst:98 +msgid "" +"In the :guilabel:`Update Flavor Metadata` window, you can customize some " +"metadata keys, then add it to this flavor and set them values." +msgstr "" + +#: ../dashboard_manage_flavors.rst:102 +msgid "**Optional metadata keys**" +msgstr "" + +#: ../dashboard_manage_flavors.rst:105 +msgid "quota:cpu_shares" +msgstr "" + +#: ../dashboard_manage_flavors.rst:107 +msgid "**CPU limits**" msgstr "" #: ../dashboard_manage_flavors.rst:107 msgid "quota:cpu_period" msgstr "" -#: ../dashboard_manage_flavors.rst:113 -msgid "quota:cpu_quota" +#: ../dashboard_manage_flavors.rst:109 +msgid "quota:cpu_limit" msgstr "" #: ../dashboard_manage_flavors.rst:111 msgid "quota:cpu_reservation" msgstr "" -#: ../dashboard_manage_flavors.rst:105 -msgid "quota:cpu_shares" +#: ../dashboard_manage_flavors.rst:113 +msgid "quota:cpu_quota" msgstr "" #: ../dashboard_manage_flavors.rst:115 msgid "quota:disk_read_bytes_sec" msgstr "" +#: ../dashboard_manage_flavors.rst:117 +msgid "**Disk tuning**" +msgstr "" + #: ../dashboard_manage_flavors.rst:117 msgid "quota:disk_read_iops_sec" msgstr "" -#: ../dashboard_manage_flavors.rst:123 -msgid "quota:disk_total_bytes_sec" -msgstr "" - -#: ../dashboard_manage_flavors.rst:125 -msgid "quota:disk_total_iops_sec" -msgstr "" - #: ../dashboard_manage_flavors.rst:119 msgid "quota:disk_write_bytes_sec" msgstr "" @@ -3440,10 +1636,22 @@ msgstr "" msgid "quota:disk_write_iops_sec" msgstr "" +#: ../dashboard_manage_flavors.rst:123 +msgid "quota:disk_total_bytes_sec" +msgstr "" + +#: ../dashboard_manage_flavors.rst:125 +msgid "quota:disk_total_iops_sec" +msgstr "" + #: ../dashboard_manage_flavors.rst:127 msgid "quota:vif_inbound_average" msgstr "" +#: ../dashboard_manage_flavors.rst:129 +msgid "**Bandwidth I/O**" +msgstr "" + #: ../dashboard_manage_flavors.rst:129 msgid "quota:vif_inbound_burst" msgstr "" @@ -3464,29 +1672,1850 @@ msgstr "" msgid "quota:vif_outbound_peak" msgstr "" -#: ../cli_set_compute_quotas.rst:38 -msgid "ram" +#: ../dashboard_manage_flavors.rst:139 +msgid "**Watchdog behavior**" msgstr "" -#: ../cli_set_compute_quotas.rst:42 -msgid "security-group-rules" +#: ../dashboard_manage_flavors.rst:139 +msgid "hw:watchdog_action" msgstr "" -#: ../cli_set_compute_quotas.rst:40 -msgid "security-groups" +#: ../dashboard_manage_flavors.rst:141 +msgid "hw_rng:allowed" msgstr "" -#: ../cli_cinder_quotas.rst:15 -msgid "snapshots" +#: ../dashboard_manage_flavors.rst:143 +msgid "**Random-number generator**" msgstr "" -#: ../dashboard_admin_manage_stacks.rst:26 +#: ../dashboard_manage_flavors.rst:143 +msgid "hw_rng:rate_bytes" +msgstr "" + +#: ../dashboard_manage_flavors.rst:145 +msgid "hw_rng:rate_period" +msgstr "" + +#: ../dashboard_manage_flavors.rst:148 msgid "" -"the basic creation and deletion of Orchestration stacks, refer to the " -"`OpenStack End User Guide `__." +"For information about supporting metadata keys, see the `OpenStack Cloud " +"Administrator Guide `__." msgstr "" -#: ../cli_cinder_quotas.rst:16 -msgid "volumes" +#: ../dashboard_manage_flavors.rst:153 +msgid "Delete flavors" +msgstr "" + +#: ../dashboard_manage_flavors.rst:161 +msgid "Select the flavors that you want to delete." +msgstr "" + +#: ../dashboard_manage_flavors.rst:162 +msgid "Click :guilabel:`Delete Flavors`." +msgstr "" + +#: ../dashboard_manage_flavors.rst:163 +msgid "" +"In the :guilabel:`Confirm Delete Flavors` window, click :guilabel:`Delete " +"Flavors` to confirm the deletion. You cannot undo this action." +msgstr "" + +#: ../dashboard_manage_host_aggregates.rst:3 +msgid "Create and manage host aggregates" +msgstr "" + +#: ../dashboard_manage_host_aggregates.rst:5 +msgid "" +"Host aggregates enable administrative users to assign key-value pairs to " +"groups of machines." +msgstr "" + +#: ../dashboard_manage_host_aggregates.rst:8 +msgid "" +"Each node can have multiple aggregates and each aggregate can have multiple " +"key-value pairs. You can assign the same key-value pair to multiple " +"aggregates." +msgstr "" + +#: ../dashboard_manage_host_aggregates.rst:12 +msgid "" +"The scheduler uses this information to make scheduling decisions. For " +"information, see `Scheduling `__." +msgstr "" + +#: ../dashboard_manage_host_aggregates.rst:17 +msgid "To create a host aggregate" +msgstr "" + +#: ../dashboard_manage_host_aggregates.rst:21 +#: ../dashboard_manage_host_aggregates.rst:57 +msgid "" +"Choose the admin project from the drop-down list at the top of the page." +msgstr "" + +#: ../dashboard_manage_host_aggregates.rst:24 +#: ../dashboard_manage_host_aggregates.rst:60 +msgid "" +"On the :guilabel:`Admin` tab, open the :guilabel:`System` tab and click the :" +"guilabel:`Host Aggregates` category." +msgstr "" + +#: ../dashboard_manage_host_aggregates.rst:27 +msgid "Click :guilabel:`Create Host Aggregate`." +msgstr "" + +#: ../dashboard_manage_host_aggregates.rst:29 +msgid "" +"In the :guilabel:`Create Host Aggregate` dialog box, enter or select the " +"following values on the :guilabel:`Host Aggregate Info` tab:" +msgstr "" + +#: ../dashboard_manage_host_aggregates.rst:32 +msgid "Name: The host aggregate name." +msgstr "" + +#: ../dashboard_manage_host_aggregates.rst:34 +msgid "" +"Availability Zone: The cloud provider defines the default availability zone, " +"such as ``us-west``, ``apac-south``, or ``nova``. You can target the host " +"aggregate, as follows:" +msgstr "" + +#: ../dashboard_manage_host_aggregates.rst:38 +msgid "" +"When the host aggregate is exposed as an availability zone, select the " +"availability zone when you launch an instance." +msgstr "" + +#: ../dashboard_manage_host_aggregates.rst:41 +msgid "" +"When the host aggregate is not exposed as an availability zone, select a " +"flavor and its extra specs to target the host aggregate." +msgstr "" + +#: ../dashboard_manage_host_aggregates.rst:45 +msgid "" +"Assign hosts to the aggregate on the Host within :guilabel:`Aggregate` tab." +msgstr "" + +#: ../dashboard_manage_host_aggregates.rst:47 +msgid "" +"To assign a host to the aggregate, click **+** for the host. The host moves " +"from the :guilabel:`All available hosts` list to the :guilabel:`Selected " +"hosts` list." +msgstr "" + +#: ../dashboard_manage_host_aggregates.rst:51 +msgid "" +"You can add one host to one or more aggregates. To add a host to an existing " +"aggregate, edit the aggregate." +msgstr "" + +#: ../dashboard_manage_host_aggregates.rst:55 +msgid "To manage host aggregates" +msgstr "" + +#: ../dashboard_manage_host_aggregates.rst:63 +msgid "" +"To edit host aggregates, select the host aggregate that you want to edit. " +"Click :guilabel:`Edit Host Aggregate`." +msgstr "" + +#: ../dashboard_manage_host_aggregates.rst:66 +msgid "" +"In the :guilabel:`Edit Host Aggregate` dialog box, you can change the name " +"and availability zone for the aggregate." +msgstr "" + +#: ../dashboard_manage_host_aggregates.rst:69 +msgid "" +"To manage hosts, locate the host aggregate that you want to edit in the " +"table. Click :guilabel:`More` and select :guilabel:`Manage Hosts`." +msgstr "" + +#: ../dashboard_manage_host_aggregates.rst:72 +msgid "" +"In the :guilabel:`Add/Remove Hosts to Aggregate` dialog box, click **+** to " +"assign a host to an aggregate. Click **-** to remove a host that is assigned " +"to an aggregate." +msgstr "" + +#: ../dashboard_manage_host_aggregates.rst:76 +msgid "" +"To delete host aggregates, locate the host aggregate that you want to edit " +"in the table. Click :guilabel:`More` and select :guilabel:`Delete Host " +"Aggregate`." +msgstr "" + +#: ../dashboard_manage_images.rst:3 +msgid "Create and manage images" +msgstr "" + +#: ../dashboard_manage_images.rst:5 +msgid "" +"As an administrative user, you can create and manage images for the projects " +"to which you belong. You can also create and manage images for users in all " +"projects to which you have access." +msgstr "" + +#: ../dashboard_manage_images.rst:10 +msgid "" +"To create and manage images in specified projects as an end user, see the " +"`OpenStack End User Guide `_." +msgstr "" + +#: ../dashboard_manage_images.rst:14 +msgid "" +"To create and manage images as an administrator for other users, use the " +"following procedures." +msgstr "" + +#: ../dashboard_manage_images.rst:18 +msgid "Create images" +msgstr "" + +#: ../dashboard_manage_images.rst:20 +msgid "" +"For details about image creation, see the `Virtual Machine Image Guide " +"`_." +msgstr "" + +#: ../dashboard_manage_images.rst:27 +msgid "" +"On the :guilabel:`Admin` tab, open the :guilabel:`System` tab and click the :" +"guilabel:`Images` category. The images that you can administer for cloud " +"users appear on this page." +msgstr "" + +#: ../dashboard_manage_images.rst:30 +msgid "" +"Click :guilabel:`Create Image`, which opens the :guilabel:`Create An Image` " +"window." +msgstr "" + +#: ../dashboard_manage_images.rst:35 +msgid "**Figure Dashboard—Create Image**" +msgstr "" + +#: ../dashboard_manage_images.rst:37 +msgid "" +"In the :guilabel:`Create An Image` window, enter or select the following " +"values:" +msgstr "" + +#: ../dashboard_manage_images.rst:41 +msgid ":guilabel:`Name`" +msgstr "" + +#: ../dashboard_manage_images.rst:41 +msgid "Enter a name for the image." +msgstr "" + +#: ../dashboard_manage_images.rst:43 +msgid ":guilabel:`Description`" +msgstr "" + +#: ../dashboard_manage_images.rst:43 +msgid "Enter a brief description of the image." +msgstr "" + +#: ../dashboard_manage_images.rst:46 +msgid ":guilabel:`Image Source`" +msgstr "" + +#: ../dashboard_manage_images.rst:46 +msgid "" +"Choose the image source from the dropdown list. Your choices are :guilabel:" +"`Image Location` and :guilabel:`Image File`." +msgstr "" + +#: ../dashboard_manage_images.rst:51 +msgid ":guilabel:`Image File` or :guilabel:`Image Location`" +msgstr "" + +#: ../dashboard_manage_images.rst:51 +msgid "" +"Based on your selection, there is an :guilabel:`Image File` or :guilabel:" +"`Image Location` field. You can include the location URL or browse for the " +"image file on your file system and add it." +msgstr "" + +#: ../dashboard_manage_images.rst:59 +msgid ":guilabel:`Format`" +msgstr "" + +#: ../dashboard_manage_images.rst:59 +msgid "Select the image format." +msgstr "" + +#: ../dashboard_manage_images.rst:61 +msgid ":guilabel:`Minimum Disk (GB)` and :guilabel:`Minimum RAM (MB)`" +msgstr "" + +#: ../dashboard_manage_images.rst:61 +msgid "Leave these fields empty." +msgstr "" + +#: ../dashboard_manage_images.rst:65 +msgid ":guilabel:`Public`" +msgstr "" + +#: ../dashboard_manage_images.rst:65 +msgid "Select this option to make the image public to all users." +msgstr "" + +#: ../dashboard_manage_images.rst:68 +msgid ":guilabel:`Protected`" +msgstr "" + +#: ../dashboard_manage_images.rst:68 +msgid "" +"Select this option to ensure that only users with permissions can delete it." +msgstr "" + +#: ../dashboard_manage_images.rst:73 +msgid "Click :guilabel:`Create Image`." +msgstr "" + +#: ../dashboard_manage_images.rst:75 +msgid "" +"The image is queued to be uploaded. It might take several minutes before the " +"status changes from ``Queued`` to ``Active``." +msgstr "" + +#: ../dashboard_manage_images.rst:79 +msgid "Update images" +msgstr "" + +#: ../dashboard_manage_images.rst:81 ../dashboard_manage_images.rst:97 +msgid "" +"Log in to the Dashboard. Choose the :guilabel:`admin` project from the drop-" +"down list at the top of the page." +msgstr "" + +#: ../dashboard_manage_images.rst:84 +msgid "" +"On the :guilabel:`Admin` tab, open the :guilabel:`System` tab and click the :" +"guilabel:`Images` category." +msgstr "" + +#: ../dashboard_manage_images.rst:86 +msgid "Select the images that you want to edit. Click :guilabel:`Edit Image`." +msgstr "" + +#: ../dashboard_manage_images.rst:87 +msgid "In the :guilabel:`Update Image` window, you can change the image name." +msgstr "" + +#: ../dashboard_manage_images.rst:89 +msgid "" +"Select the :guilabel:`Public` check box to make the image public. Clear this " +"check box to make the image private. You cannot change the kernel ID, RAM " +"disk ID, or architecture attributes for an image." +msgstr "" + +#: ../dashboard_manage_images.rst:92 +msgid "Click :guilabel:`Update Image`." +msgstr "" + +#: ../dashboard_manage_images.rst:95 +msgid "Delete images" +msgstr "" + +#: ../dashboard_manage_images.rst:100 +msgid "" +"On the :guilabel:`Admin tab`, open the :guilabel:`System` tab and click the :" +"guilabel:`Images` category." +msgstr "" + +#: ../dashboard_manage_images.rst:102 +msgid "Select the images that you want to delete." +msgstr "" + +#: ../dashboard_manage_images.rst:103 +msgid "Click :guilabel:`Delete Images`." +msgstr "" + +#: ../dashboard_manage_images.rst:104 +msgid "" +"In the :guilabel:`Confirm Delete Images` window, click :guilabel:`Delete " +"Images` to confirm the deletion." +msgstr "" + +#: ../dashboard_manage_instances.rst:3 +msgid "Manage instances" +msgstr "" + +#: ../dashboard_manage_instances.rst:5 +msgid "" +"As an administrative user, you can manage instances for users in various " +"projects. You can view, terminate, edit, perform a soft or hard reboot, " +"create a snapshot from, and migrate instances. You can also view the logs " +"for instances or launch a VNC console for an instance." +msgstr "" + +#: ../dashboard_manage_instances.rst:10 +msgid "" +"For information about using the Dashboard to launch instances as an end " +"user, see the `OpenStack End User Guide `__." +msgstr "" + +#: ../dashboard_manage_instances.rst:14 +msgid "Create instance snapshots" +msgstr "" + +#: ../dashboard_manage_instances.rst:16 ../dashboard_manage_instances.rst:38 +msgid "" +"Log in to the Dashboard and choose the admin project from the drop-down list " +"at the top of the page." +msgstr "" + +#: ../dashboard_manage_instances.rst:19 ../dashboard_manage_instances.rst:41 +msgid "" +"On the :guilabel:`Admin` tab, open the :guilabel:`System` tab and click the :" +"guilabel:`Instances` category." +msgstr "" + +#: ../dashboard_manage_instances.rst:22 +msgid "" +"Select an instance to create a snapshot from it. From the :guilabel:" +"`Actions` drop-down list, select :guilabel:`Create Snapshot`." +msgstr "" + +#: ../dashboard_manage_instances.rst:25 +msgid "" +"In the :guilabel:`Create Snapshot` window, enter a name for the snapshot." +msgstr "" + +#: ../dashboard_manage_instances.rst:27 +msgid "" +"Click :guilabel:`Create Snapshot`. The Dashboard shows the instance snapshot " +"in the :guilabel:`Images` category." +msgstr "" + +#: ../dashboard_manage_instances.rst:30 +msgid "" +"To launch an instance from the snapshot, select the snapshot and click :" +"guilabel:`Launch Instance`. For information about launching instances, see " +"the `OpenStack End User Guide `__." +msgstr "" + +#: ../dashboard_manage_instances.rst:36 +msgid "Control the state of an instance" +msgstr "" + +#: ../dashboard_manage_instances.rst:44 +msgid "Select the instance for which you want to change the state." +msgstr "" + +#: ../dashboard_manage_instances.rst:46 +msgid "" +"In the :guilabel:`More` drop-down list in the :guilabel:`Actions` column, " +"select the state." +msgstr "" + +#: ../dashboard_manage_instances.rst:49 +msgid "" +"Depending on the current state of the instance, you can choose to pause, un-" +"pause, suspend, resume, soft or hard reboot, or terminate an instance (items " +"in red are dangerous)." +msgstr "" + +#: ../dashboard_manage_instances.rst:55 +msgid "**Figure Dashboard—Instance Actions**" +msgstr "" + +#: ../dashboard_manage_instances.rst:59 +msgid "Track usage" +msgstr "" + +#: ../dashboard_manage_instances.rst:61 +msgid "Use the Overview category to track usage of instances for each project." +msgstr "" + +#: ../dashboard_manage_instances.rst:63 +msgid "" +"You can track costs per month by showing meters like number of VCPUs, disks, " +"RAM, and uptime of all your instances." +msgstr "" + +#: ../dashboard_manage_instances.rst:66 +msgid "" +"Log in to the Dashboard and choose the admin project from the CURRENT " +"PROJECT drop-down list." +msgstr "" + +#: ../dashboard_manage_instances.rst:69 +msgid "On the :guilabel:`Admin` tab, click the :guilabel:`Instances` category." +msgstr "" + +#: ../dashboard_manage_instances.rst:71 +msgid "" +"Select a month and click :guilabel:`Submit` to query the instance usage for " +"that month." +msgstr "" + +#: ../dashboard_manage_instances.rst:74 +msgid "Click :guilabel:`Download CSV Summary` to download a CSV summary." +msgstr "" + +#: ../dashboard_manage_resources.rst:3 +msgid "View cloud resources" +msgstr "" + +#: ../dashboard_manage_services.rst:3 +msgid "View services information" +msgstr "" + +#: ../dashboard_manage_services.rst:5 +msgid "" +"As an administrative user, you can view information for OpenStack services." +msgstr "" + +#: ../dashboard_manage_services.rst:7 +msgid "" +"Log in to the OpenStack dashboard and choose the :guilabel:`admin` project " +"from the drop-down list at the top of the page." +msgstr "" + +#: ../dashboard_manage_services.rst:11 +msgid "" +"On the :guilabel:`Admin` tab, click the :guilabel:`System Information` " +"category." +msgstr "" + +#: ../dashboard_manage_services.rst:14 +msgid "View the following information on these tabs:" +msgstr "" + +#: ../dashboard_manage_services.rst:16 +msgid "" +":guilabel:`Services`: Displays the internal name and the public OpenStack " +"name for each service, the host on which the service runs, and whether or " +"not the service is enabled." +msgstr "" + +#: ../dashboard_manage_services.rst:21 +msgid "" +":guilabel:`Compute Services`: Displays information specific to the Compute " +"Service. Both host and zone are listed for each service, as well as its " +"activation status." +msgstr "" + +#: ../dashboard_manage_services.rst:26 +msgid "" +":guilabel:`Block Storage Services`: Displays information specific to the " +"Block Storage Service. Both host and zone are listed for each service, as " +"well as its activation status." +msgstr "" + +#: ../dashboard_manage_services.rst:31 +msgid "" +":guilabel:`Network Agents`: Displays the network agents active within the " +"cluster, such as L3 and DHCP agents, and the status of each agent." +msgstr "" + +#: ../dashboard_manage_services.rst:35 +msgid "" +":guilabel:`Orchestration Services`: Displays information specific to the " +"Orchestration Service. Name, engine id, host and topic are listed for each " +"service, as well as its activation status." +msgstr "" + +#: ../dashboard_manage_volumes.rst:3 +msgid "Manage volumes and volume types" +msgstr "" + +#: ../dashboard_manage_volumes.rst:5 +msgid "" +"Volumes are the Block Storage devices that you attach to instances to enable " +"persistent storage. Users can attach a volume to a running instance or " +"detach a volume and attach it to another instance at any time. For " +"information about using the dashboard to create and manage volumes as an end " +"user, see the `OpenStack End User Guide `_." +msgstr "" + +#: ../dashboard_manage_volumes.rst:11 +msgid "" +"As an administrative user, you can manage volumes and volume types for users " +"in various projects. You can create and delete volume types, and you can " +"view and delete volumes. Note that a volume can be encrypted by using the " +"steps outlined below." +msgstr "" + +#: ../dashboard_manage_volumes.rst:19 +msgid "Create a volume type" +msgstr "" + +#: ../dashboard_manage_volumes.rst:21 ../dashboard_manage_volumes.rst:122 +#: ../dashboard_manage_volumes.rst:144 +msgid "" +"Log in to the dashboard and choose the :guilabel:`admin` project from the " +"drop-down list at the top of the page." +msgstr "" + +#: ../dashboard_manage_volumes.rst:24 ../dashboard_manage_volumes.rst:125 +#: ../dashboard_manage_volumes.rst:147 +msgid "" +"On the :guilabel:`Admin` tab, open the :guilabel:`System` tab and click the :" +"guilabel:`Volumes` category." +msgstr "" + +#: ../dashboard_manage_volumes.rst:27 +msgid "" +"Click the :guilabel:`Volume Types` tab, and click :guilabel:`Create Volume " +"Type` button. In the :guilabel:`Create Volume Type` window, enter a name for " +"the volume type." +msgstr "" + +#: ../dashboard_manage_volumes.rst:31 +msgid "Click :guilabel:`Create Volume Type` button to confirm your changes." +msgstr "" + +#: ../dashboard_manage_volumes.rst:33 ../dashboard_manage_volumes.rst:136 +#: ../dashboard_manage_volumes.rst:157 +msgid "A message indicates whether the action succeeded." +msgstr "" + +#: ../dashboard_manage_volumes.rst:36 +msgid "Create an encrypted volume type" +msgstr "" + +#: ../dashboard_manage_volumes.rst:38 +msgid "" +"Create a volume type using the steps above for :ref:`create-a-volume-type`." +msgstr "" + +#: ../dashboard_manage_volumes.rst:40 +msgid "" +"Click :guilabel:`Create Encryption` in the Actions column of the newly " +"created volume type." +msgstr "" + +#: ../dashboard_manage_volumes.rst:43 +msgid "" +"Configure the encrypted volume by setting the parameters below from " +"available options (see table):" +msgstr "" + +#: ../dashboard_manage_volumes.rst:46 ../dashboard_manage_volumes.rst:71 +msgid "Provider" +msgstr "" + +#: ../dashboard_manage_volumes.rst:47 +msgid "Specifies the class responsible for configuring the encryption." +msgstr "" + +#: ../dashboard_manage_volumes.rst:49 ../dashboard_manage_volumes.rst:82 +msgid "Control Location" +msgstr "" + +#: ../dashboard_manage_volumes.rst:49 +msgid "" +"Specifies whether the encryption is from the front end (nova) or the back " +"end (cinder)." +msgstr "" + +#: ../dashboard_manage_volumes.rst:51 ../dashboard_manage_volumes.rst:98 +msgid "Cipher" +msgstr "" + +#: ../dashboard_manage_volumes.rst:52 +msgid "Specifies the encryption algorithm." +msgstr "" + +#: ../dashboard_manage_volumes.rst:54 +msgid "Key Size" +msgstr "" + +#: ../dashboard_manage_volumes.rst:54 +msgid "Specifies the encryption key size." +msgstr "" + +#: ../dashboard_manage_volumes.rst:56 +msgid "Click :guilabel:`Create Volume Type Encryption`." +msgstr "" + +#: ../dashboard_manage_volumes.rst:59 +msgid "" +"Once a volume type is updated by the :guilabel:`Create Encryption` option, " +"the volume type cannot be deleted." +msgstr "" + +#: ../dashboard_manage_volumes.rst:62 +msgid "**Encryption Options**" +msgstr "" + +#: ../dashboard_manage_volumes.rst:64 +msgid "" +"The table below provides a few alternatives available for creating encrypted " +"volumes." +msgstr "" + +#: ../dashboard_manage_volumes.rst:68 +msgid "Comments" +msgstr "" + +#: ../dashboard_manage_volumes.rst:68 +msgid "Encryption parameters" +msgstr "" + +#: ../dashboard_manage_volumes.rst:68 +msgid "Parameter options" +msgstr "" + +#: ../dashboard_manage_volumes.rst:71 +msgid "" +"Allows easier import and migration of imported encrypted volumes, and allows " +"access key to be changed without re-encrypting the volume" +msgstr "" + +#: ../dashboard_manage_volumes.rst:71 +msgid "nova.volume.encryptors. luks.LuksEncryptor (Recommended)" +msgstr "" + +#: ../dashboard_manage_volumes.rst:78 +msgid "Less disk overhead than LUKS" +msgstr "" + +#: ../dashboard_manage_volumes.rst:78 +msgid "nova.volume.encryptors. cryptsetup. CryptsetupEncryptor" +msgstr "" + +#: ../dashboard_manage_volumes.rst:82 +msgid "" +"The encryption occurs within nova so that the data transmitted over the " +"network is encrypted" +msgstr "" + +#: ../dashboard_manage_volumes.rst:82 +msgid "front-end (Recommended)" +msgstr "" + +#: ../dashboard_manage_volumes.rst:88 +msgid "" +"This could be selected if a cinder plug-in supporting an encrypted back-end " +"block storage device becomes available in the future. TLS or other network " +"encryption would also be needed to protect data as it traverses the network" +msgstr "" + +#: ../dashboard_manage_volumes.rst:88 +msgid "back-end" +msgstr "" + +#: ../dashboard_manage_volumes.rst:98 +msgid "See NIST reference below to see advantages*" +msgstr "" + +#: ../dashboard_manage_volumes.rst:98 +msgid "aes-xts-plain64 (Recommended)" +msgstr "" + +#: ../dashboard_manage_volumes.rst:101 +msgid "" +"Note: On the command line, type 'cryptsetup benchmark' for additional options" +msgstr "" + +#: ../dashboard_manage_volumes.rst:101 +msgid "aes-cbc-essiv" +msgstr "" + +#: ../dashboard_manage_volumes.rst:105 +msgid "" +"512 (Recommended for aes-xts-plain64. 256 should be used for aes-cbc-essiv)" +msgstr "" + +#: ../dashboard_manage_volumes.rst:105 +msgid "Key Size (bits)" +msgstr "" + +#: ../dashboard_manage_volumes.rst:105 +msgid "" +"Using this selection for aes-xts, the underlying key size would only be 256-" +"bits*" +msgstr "" + +#: ../dashboard_manage_volumes.rst:110 +msgid "256" +msgstr "" + +#: ../dashboard_manage_volumes.rst:110 +msgid "" +"Using this selection for aes-xts, the underlying key size would only be 128-" +"bits*" +msgstr "" + +#: ../dashboard_manage_volumes.rst:115 +msgid "" +"`*` Source `NIST SP 800-38E `_" +msgstr "" + +#: ../dashboard_manage_volumes.rst:118 +msgid "Delete volume types" +msgstr "" + +#: ../dashboard_manage_volumes.rst:120 +msgid "When you delete a volume type, volumes of that type are not deleted." +msgstr "" + +#: ../dashboard_manage_volumes.rst:128 +msgid "" +"Click the :guilabel:`Volume Types` tab, select the volume type or types that " +"you want to delete." +msgstr "" + +#: ../dashboard_manage_volumes.rst:131 +msgid "Click :guilabel:`Delete Volume Types` button." +msgstr "" + +#: ../dashboard_manage_volumes.rst:133 +msgid "" +"In the :guilabel:`Confirm Delete Volume Types` window, click the :guilabel:" +"`Delete Volume Types` button to confirm the action." +msgstr "" + +#: ../dashboard_manage_volumes.rst:139 +msgid "Delete volumes" +msgstr "" + +#: ../dashboard_manage_volumes.rst:141 +msgid "" +"When you delete an instance, the data of its attached volumes is not " +"destroyed." +msgstr "" + +#: ../dashboard_manage_volumes.rst:150 +msgid "Select the volume or volumes that you want to delete." +msgstr "" + +#: ../dashboard_manage_volumes.rst:152 +msgid "Click :guilabel:`Delete Volumes` button." +msgstr "" + +#: ../dashboard_manage_volumes.rst:154 +msgid "" +"In the :guilabel:`Confirm Delete Volumes` window, click the :guilabel:" +"`Delete Volumes` button to confirm the action." +msgstr "" + +#: ../dashboard_set_quotas.rst:5 +msgid "View and manage quotas" +msgstr "" + +#: ../dashboard_set_quotas.rst:16 +msgid "" +"Typically, you change quotas when a project needs more than ten volumes or 1 " +"|nbsp| TB on a compute node." +msgstr "" + +#: ../dashboard_set_quotas.rst:19 +msgid "" +"Using the Dashboard, you can view default Compute and Block Storage quotas " +"for new tenants, as well as update quotas for existing tenants." +msgstr "" + +#: ../dashboard_set_quotas.rst:23 +msgid "" +"Using the command-line interface, you can manage quotas for the OpenStack " +"Compute service, the OpenStack Block Storage service, and the OpenStack " +"Networking service (see :doc:`cli_set_quotas`). Additionally, you can update " +"Compute service quotas for tenant users." +msgstr "" + +#: ../dashboard_set_quotas.rst:29 +msgid "" +"The following table describes the Compute and Block Storage service quotas:" +msgstr "" + +#: ../dashboard_set_quotas.rst:33 +msgid "**Quota Descriptions**" +msgstr "" + +#: ../dashboard_set_quotas.rst:36 +msgid "Quota Name" +msgstr "" + +#: ../dashboard_set_quotas.rst:36 +msgid "Service" +msgstr "" + +#: ../dashboard_set_quotas.rst:38 ../dashboard_set_quotas.rst:64 +#: ../dashboard_set_quotas.rst:70 +msgid "Block Storage" +msgstr "" + +#: ../dashboard_set_quotas.rst:38 +msgid "Gigabytes" +msgstr "" + +#: ../dashboard_set_quotas.rst:38 +msgid "Volume gigabytes allowed for each project." +msgstr "" + +#: ../dashboard_set_quotas.rst:41 ../dashboard_set_quotas.rst:44 +#: ../dashboard_set_quotas.rst:47 ../dashboard_set_quotas.rst:50 +#: ../dashboard_set_quotas.rst:52 ../dashboard_set_quotas.rst:55 +#: ../dashboard_set_quotas.rst:58 ../dashboard_set_quotas.rst:61 +#: ../dashboard_set_quotas.rst:67 +msgid "Compute" +msgstr "" + +#: ../dashboard_set_quotas.rst:41 +msgid "Instances" +msgstr "" + +#: ../dashboard_set_quotas.rst:41 +msgid "Instances allowed for each project." +msgstr "" + +#: ../dashboard_set_quotas.rst:44 +msgid "Injected Files" +msgstr "" + +#: ../dashboard_set_quotas.rst:44 +msgid "Injected files allowed for each project." +msgstr "" + +#: ../dashboard_set_quotas.rst:47 +msgid "Content bytes allowed for each injected file." +msgstr "" + +#: ../dashboard_set_quotas.rst:47 +msgid "Injected File Content Bytes" +msgstr "" + +#: ../dashboard_set_quotas.rst:50 +msgid "Keypairs" +msgstr "" + +#: ../dashboard_set_quotas.rst:50 +msgid "Number of keypairs." +msgstr "" + +#: ../dashboard_set_quotas.rst:52 +msgid "Metadata Items" +msgstr "" + +#: ../dashboard_set_quotas.rst:52 +msgid "Metadata items allowed for each instance." +msgstr "" + +#: ../dashboard_set_quotas.rst:55 +msgid "RAM (MB)" +msgstr "" + +#: ../dashboard_set_quotas.rst:55 +msgid "RAM megabytes allowed for each instance." +msgstr "" + +#: ../dashboard_set_quotas.rst:58 +msgid "Security Groups" +msgstr "" + +#: ../dashboard_set_quotas.rst:58 +msgid "Security groups allowed for each project." +msgstr "" + +#: ../dashboard_set_quotas.rst:61 +msgid "Rules allowed for each security group." +msgstr "" + +#: ../dashboard_set_quotas.rst:61 +msgid "Security Group Rules" +msgstr "" + +#: ../dashboard_set_quotas.rst:64 +msgid "Snapshots" +msgstr "" + +#: ../dashboard_set_quotas.rst:64 +msgid "Volume snapshots allowed for each project." +msgstr "" + +#: ../dashboard_set_quotas.rst:67 +msgid "Instance cores allowed for each project." +msgstr "" + +#: ../dashboard_set_quotas.rst:70 +msgid "Volumes" +msgstr "" + +#: ../dashboard_set_quotas.rst:70 +msgid "Volumes allowed for each project." +msgstr "" + +#: ../dashboard_set_quotas.rst:77 +msgid "View default project quotas" +msgstr "" + +#: ../dashboard_set_quotas.rst:79 ../dashboard_set_quotas.rst:95 +msgid "Log in to the OpenStack dashboard." +msgstr "" + +#: ../dashboard_set_quotas.rst:81 ../dashboard_set_quotas.rst:97 +msgid "" +"On the :guilabel:`Admin` tab, open the :guilabel:`System` tab and click the :" +"guilabel:`Defaults` category." +msgstr "" + +#: ../dashboard_set_quotas.rst:84 +msgid "The default quota values are displayed." +msgstr "" + +#: ../dashboard_set_quotas.rst:87 +msgid "" +"You can sort the table by clicking on either the :guilabel:`Quota Name` or :" +"guilabel:`Limit` column headers." +msgstr "" + +#: ../dashboard_set_quotas.rst:93 +msgid "Update project quotas" +msgstr "" + +#: ../dashboard_set_quotas.rst:100 ../dashboard_set_quotas.rst:105 +msgid "Click the :guilabel:`Update Defaults` button." +msgstr "" + +#: ../dashboard_set_quotas.rst:102 +msgid "" +"In the :guilabel:`Update Default Quotas` window, you can edit the default " +"quota values." +msgstr "" + +#: ../dashboard_set_quotas.rst:108 +msgid "" +"The dashboard does not show all possible project quotas. To view and update " +"the quotas for a service, use its command-line client. See :doc:" +"`cli_set_quotas`." +msgstr "" + +#: ../dashboard_view_cloud_resources.rst:3 +msgid "View cloud usage statistics" +msgstr "" + +#: ../dashboard_view_cloud_resources.rst:5 +msgid "" +"The Telemetry module provides user-level usage data for OpenStack-based " +"clouds, which can be used for customer billing, system monitoring, or " +"alerts. Data can be collected by notifications sent by existing OpenStack " +"components (for example, usage events emitted from Compute) or by polling " +"the infrastructure (for example, libvirt)." +msgstr "" + +#: ../dashboard_view_cloud_resources.rst:13 +msgid "" +"You can only view metering statistics on the dashboard (available only to " +"administrators). The Telemetry service must be set up and administered " +"through the :command:`ceilometer` command-line interface (CLI)." +msgstr "" + +#: ../dashboard_view_cloud_resources.rst:18 +msgid "" +"For basic administration information, refer to the \"Measure Cloud Resources" +"\" chapter in the `OpenStack End User Guide `_." +msgstr "" + +#: ../dashboard_view_cloud_resources.rst:25 +msgid "View resource statistics" +msgstr "" + +#: ../dashboard_view_cloud_resources.rst:27 +msgid "Log in to the OpenStack dashboard as a user with Admin privileges." +msgstr "" + +#: ../dashboard_view_cloud_resources.rst:29 +msgid "" +"On the :guilabel:`Admin` tab, click the :guilabel:`Resource Usage` category." +msgstr "" + +#: ../dashboard_view_cloud_resources.rst:31 +msgid "Click the:" +msgstr "" + +#: ../dashboard_view_cloud_resources.rst:33 +msgid "" +":guilabel:`Usage Report` tab to view a usage report per tenant (project) by " +"specifying the time period (or even use a calendar to define a date range)." +msgstr "" + +#: ../dashboard_view_cloud_resources.rst:37 +msgid "" +":guilabel:`Stats` tab to view a multi-series line chart with user-defined " +"meters. You group by project, define the value type (min, max, avg, or sum), " +"and specify the time period (or even use a calendar to define a date range)." +msgstr "" + +#: ../index.rst:3 +msgid "OpenStack Admin User Guide" +msgstr "" + +#: ../index.rst:6 +msgid "Abstract" +msgstr "" + +#: ../index.rst:8 +msgid "" +"OpenStack is an open source cloud computing platform for public and private " +"clouds. A series of interrelated projects deliver a cloud infrastructure " +"solution. This guide shows OpenStack admin users how to create and manage " +"resources in an OpenStack cloud with the OpenStack dashboard or OpenStack " +"client commands." +msgstr "" + +#: ../index.rst:14 +msgid "" +"This guide documents OpenStack Kilo, OpenStack Juno, and OpenStack Icehouse " +"releases." +msgstr "" + +#: ../index.rst:18 +msgid "Contents" +msgstr "" + +#: ../index.rst:33 +msgid "Search in this guide" +msgstr "" + +#: ../index.rst:35 +msgid ":ref:`search`" +msgstr "" + +#: ../intro-admin.rst:3 +msgid "How can I administer an OpenStack cloud?" +msgstr "" + +#: ../intro-admin.rst:5 +msgid "" +"As an OpenStack cloud administrative user, you can manage tenants, known as " +"projects, users, services, images, flavors, and quotas." +msgstr "" + +#: ../intro-admin.rst:8 +msgid "" +"The examples in this guide show you how to perform tasks by using the " +"following methods:" +msgstr "" + +#: ../intro-admin.rst:11 +msgid "" +"OpenStack dashboard. Use this web-based graphical interface, code named " +"`horizon `__, to view, " +"create, and manage resources and services." +msgstr "" + +#: ../intro-admin.rst:14 +msgid "" +"OpenStack command-line clients. Each core OpenStack project has a command-" +"line client that you can use to run simple commands to view, create, and " +"manage resources and services in a cloud and automate tasks by using scripts." +msgstr "" + +#: ../intro-admin.rst:19 +msgid "You can modify these examples for your specific use cases." +msgstr "" + +#: ../intro-admin.rst:21 +msgid "" +"In addition to these ways of interacting with a cloud, you can access the " +"OpenStack APIs directly or indirectly through `cURL `__ " +"commands or open SDKs. You can automate access or build tools to manage " +"resources and services by using the native OpenStack APIs or the EC2 " +"compatibility API." +msgstr "" + +#: ../intro-admin.rst:27 +msgid "" +"To use the OpenStack APIs, it helps to be familiar with HTTP/1.1, RESTful " +"web services, the OpenStack services, and JSON or XML data serialization " +"formats." +msgstr "" + +#: ../intro-admin.rst:32 +msgid "Who should read this book?" +msgstr "" + +#: ../intro-admin.rst:34 +msgid "" +"This book is written for administrators who maintain and secure an OpenStack " +"cloud installation to serve end users' needs. You should have years of " +"experience with Linux-based tools for system administration. You should also " +"be familiar with OpenStack basics, such as managing projects and users, " +"troubleshooting, performing backup and recovery, and monitoring. For more " +"information, see the `OpenStack Operations Guide `__." +msgstr "" + +#: ../manage_projects_users_and_roles.rst:3 +msgid "Manage projects, users, and roles" +msgstr "" + +#: ../manage_projects_users_and_roles.rst:4 +msgid "" +"As a cloud administrator, you manage projects, users, and roles. Projects " +"are organizational units in the cloud to which you can assign users. " +"Projects are also known as ``tenants`` or ``accounts``. Users can be members " +"of one or more projects. Roles define which actions users can perform. You " +"assign roles to user-project pairs." +msgstr "" + +#: ../manage_projects_users_and_roles.rst:11 +msgid "" +"You can define actions for OpenStack service roles in the ``/etc/PROJECT``/" +"policy.json files. For example, define actions for Compute service roles in " +"the ``/etc/nova/policy.json`` file." +msgstr "" + +#: ../manage_projects_users_and_roles.rst:15 +msgid "" +"You can manage projects, users, and roles independently from each other." +msgstr "" + +#: ../manage_projects_users_and_roles.rst:17 +msgid "" +"During cloud set up, the operator defines at least one project, user, and " +"role." +msgstr "" + +#: ../manage_projects_users_and_roles.rst:20 +msgid "" +"Learn how to add, update, and delete projects and users, assign users to one " +"or more projects, and change or remove the assignment. To enable or " +"temporarily disable a project or user, you update that project or user. You " +"can also change quotas at the project level." +msgstr "" + +#: ../manage_projects_users_and_roles.rst:25 +msgid "" +"Before you can delete a user account, you must remove the user account from " +"its primary project." +msgstr "" + +#: ../manage_projects_users_and_roles.rst:28 +msgid "" +"Before you can run keystone client commands, you must download and source an " +"OpenStack RC file. See `Download and source the OpenStack RC file `__." +msgstr "" + +#: ../manage_projects_users_and_roles.rst:34 +msgid "Projects" +msgstr "" + +#: ../manage_projects_users_and_roles.rst:36 +msgid "" +"A project is a group of zero or more users. In Compute, a project owns " +"virtual machines. In Object Storage, a project owns containers. Users can be " +"associated with more than one project. Each project and user pairing can " +"have a role associated with it." +msgstr "" + +#: ../manage_projects_users_and_roles.rst:42 +msgid "List projects" +msgstr "" + +#: ../manage_projects_users_and_roles.rst:44 +msgid "" +"List all projects with their ID, name, and whether they are enabled or " +"disabled:" +msgstr "" + +#: ../manage_projects_users_and_roles.rst:62 +msgid "Create a project" +msgstr "" + +#: ../manage_projects_users_and_roles.rst:64 +msgid "Create a project named ``new-project``:" +msgstr "" + +#: ../manage_projects_users_and_roles.rst:79 +msgid "Update a project" +msgstr "" + +#: ../manage_projects_users_and_roles.rst:81 +msgid "" +"Specify the project ID to update a project. You can update the name, " +"description, and enabled status of a project." +msgstr "" + +#: ../manage_projects_users_and_roles.rst:84 +msgid "To temporarily disable a project:" +msgstr "" + +#: ../manage_projects_users_and_roles.rst:90 +msgid "To enable a disabled project:" +msgstr "" + +#: ../manage_projects_users_and_roles.rst:96 +msgid "To update the name of a project:" +msgstr "" + +#: ../manage_projects_users_and_roles.rst:102 +msgid "To verify your changes, show information for the updated project:" +msgstr "" + +#: ../manage_projects_users_and_roles.rst:117 +msgid "Delete a project" +msgstr "" + +#: ../manage_projects_users_and_roles.rst:119 +msgid "Specify the project ID to delete a project:" +msgstr "" + +#: ../manage_projects_users_and_roles.rst:126 +msgid "User" +msgstr "" + +#: ../manage_projects_users_and_roles.rst:129 +msgid "List users" +msgstr "" + +#: ../manage_projects_users_and_roles.rst:131 +msgid "List all users:" +msgstr "" + +#: ../manage_projects_users_and_roles.rst:146 +msgid "Create a user" +msgstr "" + +#: ../manage_projects_users_and_roles.rst:148 +msgid "" +"To create a user, you must specify a name. Optionally, you can specify a " +"tenant ID, password, and email address. It is recommended that you include " +"the tenant ID and password because the user cannot log in to the dashboard " +"without this information." +msgstr "" + +#: ../manage_projects_users_and_roles.rst:153 +msgid "Create the ``new-user`` user:" +msgstr "" + +#: ../manage_projects_users_and_roles.rst:169 +msgid "Update a user" +msgstr "" + +#: ../manage_projects_users_and_roles.rst:171 +msgid "You can update the name, email address, and enabled status for a user." +msgstr "" + +#: ../manage_projects_users_and_roles.rst:173 +msgid "To temporarily disable a user account:" +msgstr "" + +#: ../manage_projects_users_and_roles.rst:179 +msgid "" +"If you disable a user account, the user cannot log in to the dashboard. " +"However, data for the user account is maintained, so you can enable the user " +"at any time." +msgstr "" + +#: ../manage_projects_users_and_roles.rst:183 +msgid "To enable a disabled user account:" +msgstr "" + +#: ../manage_projects_users_and_roles.rst:189 +msgid "To change the name and description for a user account:" +msgstr "" + +#: ../manage_projects_users_and_roles.rst:197 +msgid "Delete a user" +msgstr "" + +#: ../manage_projects_users_and_roles.rst:199 +msgid "Delete a specified user account:" +msgstr "" + +#: ../manage_projects_users_and_roles.rst:206 +msgid "Roles and role assignments" +msgstr "" + +#: ../manage_projects_users_and_roles.rst:209 +msgid "List available roles" +msgstr "" + +#: ../manage_projects_users_and_roles.rst:211 +msgid "List the available roles:" +msgstr "" + +#: ../manage_projects_users_and_roles.rst:229 +msgid "" +"Users can be members of multiple projects. To assign users to multiple " +"projects, define a role and assign that role to a user-project pair." +msgstr "" + +#: ../manage_projects_users_and_roles.rst:232 +msgid "Create the ``new-role`` role:" +msgstr "" + +#: ../manage_projects_users_and_roles.rst:245 +msgid "Assign a role" +msgstr "" + +#: ../manage_projects_users_and_roles.rst:247 +msgid "" +"To assign a user to a project, you must assign the role to a user-project " +"pair. To do this, you need the user, role, and project IDs." +msgstr "" + +#: ../manage_projects_users_and_roles.rst:251 +msgid "List users and note the user ID you want to assign to the role:" +msgstr "" + +#: ../manage_projects_users_and_roles.rst:267 +msgid "List role IDs and note the role ID you want to assign:" +msgstr "" + +#: ../manage_projects_users_and_roles.rst:283 +msgid "List projects and note the project ID you want to assign to the role:" +msgstr "" + +#: ../manage_projects_users_and_roles.rst:301 +msgid "" +"Assign a role to a user-project pair. In this example, assign the ``new-" +"role`` role to the ``demo`` and ``test-project`` pair:" +msgstr "" + +#: ../manage_projects_users_and_roles.rst:308 +msgid "Verify the role assignment:" +msgstr "" + +#: ../manage_projects_users_and_roles.rst:320 +msgid "View role details" +msgstr "" + +#: ../manage_projects_users_and_roles.rst:322 +msgid "View details for a specified role:" +msgstr "" + +#: ../manage_projects_users_and_roles.rst:335 +msgid "Remove a role" +msgstr "" + +#: ../manage_projects_users_and_roles.rst:337 +msgid "Remove a role from a user-project pair:" +msgstr "" + +#: ../manage_projects_users_and_roles.rst:339 +msgid "Run :command:`openstack role remove`:" +msgstr "" + +#: ../manage_projects_users_and_roles.rst:345 +msgid "Verify the role removal:" +msgstr "" + +#: ../manage_projects_users_and_roles.rst:351 +msgid "If the role was removed, the command output omits the removed role." +msgstr "" + +#: ../networking_advanced_quotas.rst:3 +msgid "Manage Networking service quotas" +msgstr "" + +#: ../networking_advanced_quotas.rst:4 +msgid "" +"A quota limits the number of available resources. A default quota might be " +"enforced for all tenants. When you try to create more resources than the " +"quota allows, an error occurs:" +msgstr "" + +#: ../networking_advanced_quotas.rst:13 +msgid "" +"Per-tenant quota configuration is also supported by the quota extension API. " +"See :ref:`cfg_quotas_per_tenant` for details." +msgstr "" + +#: ../networking_advanced_quotas.rst:17 +msgid "Basic quota configuration" +msgstr "" + +#: ../networking_advanced_quotas.rst:18 +msgid "" +"In the Networking default quota mechanism, all tenants have the same quota " +"values, such as the number of resources that a tenant can create." +msgstr "" + +#: ../networking_advanced_quotas.rst:22 +msgid "" +"The quota value is defined in the OpenStack Networking :file:`neutron.conf` " +"configuration file. To disable quotas for a specific resource, such as " +"network, subnet, or port, remove a corresponding item from :code:" +"`quota_items`. This example shows the default quota values:" +msgstr "" + +#: ../networking_advanced_quotas.rst:46 +msgid "" +"OpenStack Networking also supports quotas for L3 resources: router and " +"floating IP. Add these lines to the ``quotas`` section in the :file:`neutron." +"conf` file:" +msgstr "" + +#: ../networking_advanced_quotas.rst:60 ../networking_advanced_quotas.rst:77 +msgid "The :code:`quota_items` option does not affect these quotas." +msgstr "" + +#: ../networking_advanced_quotas.rst:62 +msgid "" +"OpenStack Networking also supports quotas for security group resources: " +"number of security groups and the number of rules for each security group. " +"Add these lines to the ``quotas`` section in the :file:`neutron.conf` file:" +msgstr "" + +#: ../networking_advanced_quotas.rst:82 +msgid "Configure per-tenant quotas" +msgstr "" + +#: ../networking_advanced_quotas.rst:83 +msgid "" +"OpenStack Networking also supports per-tenant quota limit by quota extension " +"API." +msgstr "" + +#: ../networking_advanced_quotas.rst:86 +msgid "Use these commands to manage per-tenant quotas:" +msgstr "" + +#: ../networking_advanced_quotas.rst:89 +msgid "Delete defined quotas for a specified tenant" +msgstr "" + +#: ../networking_advanced_quotas.rst:89 +msgid "neutron quota-delete" +msgstr "" + +#: ../networking_advanced_quotas.rst:92 +msgid "Lists defined quotas for all tenants" +msgstr "" + +#: ../networking_advanced_quotas.rst:92 +msgid "neutron quota-list" +msgstr "" + +#: ../networking_advanced_quotas.rst:95 +msgid "Shows quotas for a specified tenant" +msgstr "" + +#: ../networking_advanced_quotas.rst:95 +msgid "neutron quota-show" +msgstr "" + +#: ../networking_advanced_quotas.rst:98 +msgid "Updates quotas for a specified tenant" +msgstr "" + +#: ../networking_advanced_quotas.rst:98 +msgid "neutron quota-update" +msgstr "" + +#: ../networking_advanced_quotas.rst:100 +msgid "" +"Only users with the ``admin`` role can change a quota value. By default, the " +"default set of quotas are enforced for all tenants, so no :command:`quota-" +"create` command exists." +msgstr "" + +#: ../networking_advanced_quotas.rst:104 +msgid "Configure Networking to show per-tenant quotas" +msgstr "" + +#: ../networking_advanced_quotas.rst:106 +msgid "Set the :code:`quota_driver` option in the :file:`neutron.conf` file::" +msgstr "" + +#: ../networking_advanced_quotas.rst:110 +msgid "" +"When you set this option, the output for Networking commands shows " +"``quotas``." +msgstr "" + +#: ../networking_advanced_quotas.rst:112 +msgid "List Networking extensions." +msgstr "" + +#: ../networking_advanced_quotas.rst:114 +msgid "To list the Networking extensions, run this command::" +msgstr "" + +#: ../networking_advanced_quotas.rst:118 +msgid "" +"The command shows the ``quotas`` extension, which provides per-tenant quota " +"management support::" +msgstr "" + +#: ../networking_advanced_quotas.rst:135 +msgid "Show information for the quotas extension." +msgstr "" + +#: ../networking_advanced_quotas.rst:137 +msgid "To show information for the ``quotas`` extension, run this command::" +msgstr "" + +#: ../networking_advanced_quotas.rst:153 +msgid "" +"Only some plug-ins support per-tenant quotas. Specifically, Open vSwitch, " +"Linux Bridge, and VMware NSX support them, but new versions of other plug-" +"ins might bring additional functionality. See the documentation for each " +"plug-in." +msgstr "" + +#: ../networking_advanced_quotas.rst:159 +msgid "List tenants who have per-tenant quota support." +msgstr "" + +#: ../networking_advanced_quotas.rst:161 +msgid "" +"The :command:`quota-list` command lists tenants for which the per-tenant " +"quota is enabled. The command does not list tenants with default quota " +"support. You must be an administrative user to run this command::" +msgstr "" + +#: ../networking_advanced_quotas.rst:173 +msgid "Show per-tenant quota values." +msgstr "" + +#: ../networking_advanced_quotas.rst:175 +msgid "" +"The :command:`quota-show` command reports the current set of quota limits " +"for the specified tenant. Non-administrative users can run this command " +"without the ``--tenant_id`` parameter. If per-tenant quota limits are not " +"enabled for the tenant, the command shows the default set of quotas::" +msgstr "" + +#: ../networking_advanced_quotas.rst:193 +msgid "" +"The following command shows the command output for a non-administrative " +"user::" +msgstr "" + +#: ../networking_advanced_quotas.rst:207 +msgid "Update quota values for a specified tenant." +msgstr "" + +#: ../networking_advanced_quotas.rst:209 +msgid "" +"Use the :command:`quota-update` command to update a quota for a specified " +"tenant::" +msgstr "" + +#: ../networking_advanced_quotas.rst:223 +msgid "You can update quotas for multiple resources through one command::" +msgstr "" + +#: ../networking_advanced_quotas.rst:237 +msgid "" +"To update the limits for an L3 resource such as, router or floating IP, you " +"must define new values for the quotas after the ``--`` directive." +msgstr "" + +#: ../networking_advanced_quotas.rst:241 +msgid "" +"This example updates the limit of the number of floating IPs for the " +"specified tenant::" +msgstr "" + +#: ../networking_advanced_quotas.rst:255 +msgid "" +"You can update the limits of multiple resources by including L2 resources " +"and L3 resource through one command::" +msgstr "" + +#: ../networking_advanced_quotas.rst:270 +msgid "Delete per-tenant quota values." +msgstr "" + +#: ../networking_advanced_quotas.rst:272 +msgid "" +"To clear per-tenant quota limits, use the :command:`quota-delete` command::" +msgstr "" + +#: ../networking_advanced_quotas.rst:278 +msgid "" +"After you run this command, you can see that quota values for the tenant are " +"reset to the default values::" +msgstr "" + +#: ../nova_cli_manage_projects_security.rst:3 +msgid "Manage project security" +msgstr "" + +#: ../nova_cli_manage_projects_security.rst:5 +msgid "" +"Security groups are sets of IP filter rules that are applied to all project " +"instances, which define networking access to the instance. Group rules are " +"project specific; project members can edit the default rules for their group " +"and add new rule sets." +msgstr "" + +#: ../nova_cli_manage_projects_security.rst:10 +msgid "" +"All projects have a \"default\" security group which is applied to any " +"instance that has no other defined security group. Unless you change the " +"default, this security group denies all incoming traffic and allows only " +"outgoing traffic to your instance." +msgstr "" + +#: ../nova_cli_manage_projects_security.rst:15 +msgid "" +"You can use the ``allow_same_net_traffic`` option in the :file:`/etc/nova/" +"nova.conf` file to globally control whether the rules apply to hosts which " +"share a network." +msgstr "" + +#: ../nova_cli_manage_projects_security.rst:19 +msgid "If set to:" +msgstr "" + +#: ../nova_cli_manage_projects_security.rst:21 +msgid "" +"``True`` (default), hosts on the same subnet are not filtered and are " +"allowed to pass all types of traffic between them. On a flat network, this " +"allows all instances from all projects unfiltered communication. With VLAN " +"networking, this allows access between instances within the same project. " +"You can also simulate this setting by configuring the default security group " +"to allow all traffic from the subnet." +msgstr "" + +#: ../nova_cli_manage_projects_security.rst:28 +msgid "``False``, security groups are enforced for all connections." +msgstr "" + +#: ../nova_cli_manage_projects_security.rst:30 +msgid "" +"Additionally, the number of maximum rules per security group is controlled " +"by the ``security_group_rules`` and the number of allowed security groups " +"per project is controlled by the ``security_groups`` quota (see the `Manage " +"quotas `_ " +"section)." +msgstr "" + +#: ../nova_cli_manage_projects_security.rst:37 +msgid "List and view current security groups" +msgstr "" + +#: ../nova_cli_manage_projects_security.rst:38 +msgid "" +"From the command line you can get a list of security groups for the project, " +"using the nova command:" +msgstr "" + +#: ../nova_cli_manage_projects_security.rst:41 +msgid "" +"Ensure your system variables are set for the user and tenant for which you " +"are checking security group rules for. For example:" +msgstr "" + +#: ../nova_cli_manage_projects_security.rst:49 +msgid "Output security groups, as follows:" +msgstr "" + +#: ../nova_cli_manage_projects_security.rst:61 +msgid "View the details of a group, as follows:" +msgstr "" + +#: ../nova_cli_manage_projects_security.rst:80 +msgid "" +"These rules are allow type rules as the default is deny. The first column is " +"the IP protocol (one of icmp, tcp, or udp). The second and third columns " +"specify the affected port range. The third column specifies the IP range in " +"CIDR format. This example shows the full port range for all protocols " +"allowed from all IPs." +msgstr "" + +#: ../nova_cli_manage_projects_security.rst:87 +msgid "Create a security group" +msgstr "" + +#: ../nova_cli_manage_projects_security.rst:88 +msgid "" +"When adding a new security group, you should pick a descriptive but brief " +"name. This name shows up in brief descriptions of the instances that use it " +"where the longer description field often does not. For example, seeing that " +"an instance is using security group \"http\" is much easier to understand " +"than \"bobs\\_group\" or \"secgrp1\"." +msgstr "" + +#: ../nova_cli_manage_projects_security.rst:94 +msgid "" +"Ensure your system variables are set for the user and tenant for which you " +"are checking security group rules for." +msgstr "" + +#: ../nova_cli_manage_projects_security.rst:97 +msgid "Add the new security group, as follows:" +msgstr "" + +#: ../nova_cli_manage_projects_security.rst:114 +msgid "Add a new group rule, as follows:" +msgstr "" + +#: ../nova_cli_manage_projects_security.rst:120 +msgid "" +"The arguments are positional, and the \"from-port\" and \"to-port\" " +"arguments specify the local port range connections are allowed to access, " +"not the source and destination ports of the connection. For example:" +msgstr "" + +#: ../nova_cli_manage_projects_security.rst:134 +msgid "" +"You can create complex rule sets by creating additional rules. For example, " +"if you want to pass both HTTP and HTTPS traffic, run:" +msgstr "" + +#: ../nova_cli_manage_projects_security.rst:146 +msgid "" +"Despite only outputting the newly added rule, this operation is additive " +"(both rules are created and enforced)." +msgstr "" + +#: ../nova_cli_manage_projects_security.rst:149 +msgid "View all rules for the new security group, as follows:" +msgstr "" + +#: ../nova_cli_manage_projects_security.rst:162 +msgid "Delete a security group" +msgstr "" + +#: ../nova_cli_manage_projects_security.rst:163 +msgid "" +"Ensure your system variables are set for the user and tenant for which you " +"are deleting a security group for." +msgstr "" + +#: ../nova_cli_manage_projects_security.rst:166 +msgid "Delete the new security group, as follows:" +msgstr "" + +#: ../nova_cli_manage_projects_security.rst:179 +msgid "Create security group rules for a cluster of instances" +msgstr "" + +#: ../nova_cli_manage_projects_security.rst:180 +msgid "" +"Source Groups are a special, dynamic way of defining the CIDR of allowed " +"sources. The user specifies a Source Group (Security Group name), and all " +"the users' other Instances using the specified Source Group are selected " +"dynamically. This alleviates the need for individual rules to allow each new " +"member of the cluster." +msgstr "" + +#: ../nova_cli_manage_projects_security.rst:186 +msgid "" +"Make sure to set the system variables for the user and tenant for which you " +"are deleting a security group for." +msgstr "" + +#: ../nova_cli_manage_projects_security.rst:189 +msgid "Add a source group, as follows:" +msgstr "" + +#: ../nova_cli_manage_projects_security.rst:201 +msgid "" +"The ``cluster`` rule allows ssh access from any other instance that uses the " +"``global_http`` group." msgstr "" 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 a6d662a31e..b470c01fee 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 @@ -16,11 +16,11 @@ msgid "" msgstr "" "Project-Id-Version: End User Guide 1.0.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2015-10-04 00:26+0000\n" +"POT-Creation-Date: 2015-10-08 06:01+0000\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" -"PO-Revision-Date: 2015-10-04 12:33+0000\n" +"PO-Revision-Date: 2015-10-07 12:27+0000\n" "Last-Translator: KATO Tomoyuki \n" "Language-Team: Japanese (http://www.transifex.com/openstack/openstack-" "manuals-i18n/language/ja/)\n" @@ -203,6 +203,12 @@ msgstr "" msgid "**Re-examine the database configuration**" msgstr "**データベース設定の再検査**" +msgid "**Remote**: ``CIDR``" +msgstr "**接続相手**: ``CIDR``" + +msgid "**Remote**: ``Ingress``" +msgstr "**接続相手**: ``受信``" + msgid "" "**Replication set name. **\\ This name consists of the cluster name, " "followed by the string -rs\\ *n*, where *n* is 1 for the first replication " @@ -221,6 +227,12 @@ msgstr "**データベースインスタンスのリストア**" msgid "**Restore using incremental backups**" msgstr "**増分バックアップを用いたリストア**" +msgid "**Rule**: ``All ICMP``" +msgstr "**ルール**: ``All ICMP``" + +msgid "**Rule**: ``SSH``" +msgstr "**ルール**: ``SSH``" + msgid "" "**Source of traffic**. Enable traffic to instances from either IP addresses " "inside the cloud from other group members or from all IP addresses." @@ -2328,9 +2340,6 @@ msgstr "詳細" msgid "Determine whether the ``vm1`` server exists:" msgstr "``vm1`` サーバーが存在するかどうかを確認します。" -msgid "Direction" -msgstr "方向" - msgid "" "Disassociate a configuration group from a database instance, using the trove " "``configuration-detach`` command." @@ -3069,7 +3078,7 @@ msgstr "" "グループを表示します。" msgid "" -"If you are using the dashboard from a Windows computer, use PuTTYgen to load " +"If you are using the Dashboard from a Windows computer, use PuTTYgen to load " "the ``*.pem`` file and convert and save it as ``*.ppk``. For more " "information see the `WinSCP web page for PuTTYgen `__." @@ -3403,13 +3412,6 @@ msgid "In the :guilabel:`Actions` column, click :guilabel:`Edit Volume`." msgstr "" ":guilabel:`操作` の列で、:guilabel:`ボリュームの編集` をクリックします。" -msgid "" -"In the :guilabel:`Actions` column, click :guilabel:`More` and then select :" -"guilabel:`Edit` from the list." -msgstr "" -":guilabel:`アクション` 欄の :guilabel:`▼` をクリックし、ドロップダウンリスト" -"から :guilabel:`編集` を選択します。" - msgid "" "In the :guilabel:`Add Interface` dialog box, select a :guilabel:`Subnet`." msgstr "" @@ -3425,13 +3427,6 @@ msgstr "" ":guilabel:`データベースのバックアップ` ダイアログボックスに以下の値を指定しま" "す。" -msgid "" -"In the :guilabel:`Confirm Delete Image` dialog box, click :guilabel:`Delete " -"Images` to confirm the deletion." -msgstr "" -":guilabel:`イメージの削除の確認` ダイアログボックスで、:guilabel:`イメージの" -"削除` をクリックして削除を確定します。" - msgid "" "In the :guilabel:`Copy Object` launch dialog box, enter the following values:" msgstr "" @@ -5016,9 +5011,6 @@ msgstr "Redis" msgid "Register raw image" msgstr "raw イメージの登録" -msgid "Remote" -msgstr "接続相手" - msgid "Removal or addition of segment objects" msgstr "分割オブジェクトの削除または追加" @@ -5107,9 +5099,6 @@ msgstr "ルートの GB 単位のボリューム容量: ``5``" msgid "Root volume size: ``2``" msgstr "ルートボリューム容量: ``2``" -msgid "Rule" -msgstr "ルール" - msgid "Rules are automatically enforced as soon as you create or modify them." msgstr "ルールは、作成または変更後すぐに自動的に有効になります。" @@ -5709,6 +5698,12 @@ msgstr "サブネットの CIDR。" msgid "The Compute database registers the public key of the key pair." msgstr "コンピュートのデータベースはキーペアの公開鍵を登録します。" +msgid "" +"The Dashboard lists the key pair on the :guilabel:`Access & Security` tab." +msgstr "" +"ダッシュボードの :guilabel:`アクセスとセキュリティ` タブにキーペアが一覧表示" +"されます。" + # #-#-#-#-# dashboard_databases.pot (End User Guide 1.0.0) #-#-#-#-# # #-#-#-#-# trove-manage-db.pot (End User Guide 1.0.0) #-#-#-#-# msgid "" @@ -6051,12 +6046,6 @@ msgid "" "The container and object name in the format: ``CONTAINER_NAME/OBJECT_NAME``." msgstr "``CONTAINER_NAME/OBJECT_NAME`` 形式のコンテナー名とオブジェクト名。" -msgid "" -"The dashboard lists the key pair on the :guilabel:`Access & Security` tab." -msgstr "" -"ダッシュボードの :guilabel:`アクセスとセキュリティ` タブにキーペアが一覧表示" -"されます。" - msgid "" "The dashboard shows the images that have been uploaded to OpenStack Image " "service and are available for this project." @@ -9012,21 +9001,9 @@ msgstr "``--swap``" msgid "``Accept`` request header" msgstr "``Accept`` リクエストヘッダー" -msgid "``All ICMP``" -msgstr "``すべての ICMP``" - -msgid "``CIDR``" -msgstr "``CIDR``" - -msgid "``Ingress``" -msgstr "``受信``" - msgid "``NAME``. The name for the server." msgstr "``NAME``。サーバーの名前。" -msgid "``SSH``" -msgstr "``SSH``" - msgid "" "``Segment objects`` store the object content. You can divide your content " "into segments, and upload each segment into its own segment object. Segment " diff --git a/doc/user-guide/source/locale/user-guide.pot b/doc/user-guide/source/locale/user-guide.pot index d7c09a8520..a0560f6001 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-10-04 06:17+0000\n" +"POT-Creation-Date: 2015-10-08 06:31+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -16,8 +16,202 @@ msgstr "" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" -#: ../create_db.rst:169 -msgid "**Access the new database**" +# #-#-#-#-# backup_db.pot (End User Guide 1.0.0) #-#-#-#-# +# #-#-#-#-# dashboard_databases.pot (End User Guide 1.0.0) #-#-#-#-# +#: ../backup_db.rst:3 ../dashboard_databases.rst:103 +msgid "Backup and restore a database" +msgstr "" + +# #-#-#-#-# backup_db.pot (End User Guide 1.0.0) #-#-#-#-# +# #-#-#-#-# dashboard_databases.pot (End User Guide 1.0.0) #-#-#-#-# +#: ../backup_db.rst:5 ../dashboard_databases.rst:105 +msgid "" +"You can use Database services to backup a database and store the backup " +"artifact in the Object Storage module. Later on, if the original database is " +"damaged, you can use the backup artifact to restore the database. The " +"restore process creates a database instance." +msgstr "" + +# #-#-#-#-# backup_db.pot (End User Guide 1.0.0) #-#-#-#-# +# #-#-#-#-# dashboard_databases.pot (End User Guide 1.0.0) #-#-#-#-# +#: ../backup_db.rst:10 ../dashboard_databases.rst:110 +msgid "This example shows you how to back up and restore a MySQL database." +msgstr "" + +#: ../backup_db.rst:12 +msgid "**Backup the database instance**" +msgstr "" + +#: ../backup_db.rst:14 +msgid "" +"As background, assume that you have created a database instance with the " +"following characteristics:" +msgstr "" + +#: ../backup_db.rst:18 +msgid "Name of the database instance: ``guest1``" +msgstr "" + +#: ../backup_db.rst:20 +msgid "Flavor ID: ``10``" +msgstr "" + +#: ../backup_db.rst:22 +msgid "Root volume size: ``2``" +msgstr "" + +#: ../backup_db.rst:24 +msgid "Databases: ``db1`` and ``db2``" +msgstr "" + +#: ../backup_db.rst:26 +msgid "Users: The ``user1`` user with the ``password`` password" +msgstr "" + +#: ../backup_db.rst:28 +msgid "" +"First, get the ID of the ``guest1`` database instance by using the trove " +"``list`` command:" +msgstr "" + +#: ../backup_db.rst:40 +msgid "" +"Back up the database instance by using the trove ``backup-create`` command. " +"In this example, the backup is called ``backup1``. In this example, replace " +"``INSTANCE_ID`` with ``97b4b853-80f6-414f-ba6f-c6f455a79ae6``:" +msgstr "" + +#: ../backup_db.rst:45 +msgid "" +"This command syntax pertains only to python-troveclient version 1.0.6 and " +"later. Earlier versions require you to pass in the backup name as the first " +"argument." +msgstr "" + +#: ../backup_db.rst:67 +msgid "" +"Note that the command returns both the ID of the original instance " +"(``instance_id``) and the ID of the backup artifact (``id``)." +msgstr "" + +#: ../backup_db.rst:70 +msgid "" +"Later on, use the trove ``backup-list`` command to get this information:" +msgstr "" + +#: ../backup_db.rst:82 +msgid "" +"You can get additional information about the backup by using the trove " +"``backup-show`` command and passing in the ``BACKUP_ID``, which is " +"``8af30763-61fd-4aab-8fe8-57d528911138``." +msgstr "" + +#: ../backup_db.rst:104 +msgid "**Restore a database instance**" +msgstr "" + +#: ../backup_db.rst:106 +msgid "" +"Now assume that your ``guest1`` database instance is damaged and you need to " +"restore it. In this example, you use the trove ``create`` command to create " +"a new database instance called ``guest2``." +msgstr "" + +#: ../backup_db.rst:110 +msgid "" +"You specify that the new ``guest2`` instance has the same flavor (``10``) " +"and the same root volume size (``2``) as the original ``guest1`` instance." +msgstr "" + +#: ../backup_db.rst:114 +msgid "" +"You use the ``--backup`` argument to indicate that this new instance is " +"based on the backup artifact identified by ``BACKUP_ID``. In this example, " +"replace ``BACKUP_ID`` with ``8af30763-61fd-4aab-8fe8-57d528911138``." +msgstr "" + +#: ../backup_db.rst:136 +msgid "**Verify backup**" +msgstr "" + +#: ../backup_db.rst:138 +msgid "" +"Now check that the new ``guest2`` instance has the same characteristics as " +"the original ``guest1`` instance." +msgstr "" + +#: ../backup_db.rst:141 +msgid "Start by getting the ID of the new ``guest2`` instance." +msgstr "" + +#: ../backup_db.rst:153 +msgid "" +"Use the trove ``show`` command to display information about the new guest2 " +"instance. Pass in guest2's ``INSTANCE_ID``, which is ``ac7a2b35-a9b4-4ff6-" +"beac-a1bcee86d04b``." +msgstr "" + +#: ../backup_db.rst:176 +msgid "" +"Note that the data store, flavor ID, and volume size have the same values as " +"in the original ``guest1`` instance." +msgstr "" + +#: ../backup_db.rst:179 +msgid "" +"Use the trove ``database-list`` command to check that the original databases " +"(``db1`` and ``db2``) are present on the restored instance." +msgstr "" + +#: ../backup_db.rst:194 +msgid "" +"Use the trove ``user-list`` command to check that the original user " +"(``user1``) is present on the restored instance." +msgstr "" + +#: ../backup_db.rst:206 +msgid "**Notify users**" +msgstr "" + +#: ../backup_db.rst:208 +msgid "" +"Tell the users who were accessing the now-disabled ``guest1`` database " +"instance that they can now access ``guest2``. Provide them with ``guest2``'s " +"name, IP address, and any other information they might need. (You can get " +"this information by using the trove ``show`` command.)" +msgstr "" + +#: ../backup_db.rst:214 +msgid "**Clean up**" +msgstr "" + +#: ../backup_db.rst:216 +msgid "" +"At this point, you might want to delete the disabled ``guest1`` instance, by " +"using the trove ``delete`` command." +msgstr "" + +#: ../backup_db_incremental.rst:3 +msgid "Use incremental backups" +msgstr "" + +#: ../backup_db_incremental.rst:5 +msgid "" +"Incremental backups let you chain together a series of backups. You start " +"with a regular backup. Then, when you want to create a subsequent " +"incremental backup, you specify the parent backup." +msgstr "" + +#: ../backup_db_incremental.rst:9 +msgid "" +"Restoring a database instance from an incremental backup is the same as " +"creating a database instance from a regular backup—the Database service " +"handles the complexities of applying the chain of incremental backups." +msgstr "" + +#: ../backup_db_incremental.rst:13 +msgid "" +"This example shows you how to use incremental backups with a MySQL database." msgstr "" #: ../backup_db_incremental.rst:16 @@ -26,258 +220,238 @@ msgid "" "following database instance:" msgstr "" -#: ../backup_db.rst:12 -msgid "**Backup the database instance**" +#: ../backup_db_incremental.rst:19 +msgid "Instance name: ``guest1``" msgstr "" -#: ../set_up_clustering.rst:24 -msgid "**Before you begin. **\\ Make sure that:" -msgstr "" - -#: ../manage_db_config.rst:150 -msgid "**Change the database configuration using a configuration group**" -msgstr "" - -#: ../backup_db.rst:214 -msgid "**Clean up**" -msgstr "" - -#: ../cli_config_drive.rst:26 -msgid "**Compute host requirements**" -msgstr "" - -#: ../manage_db_config.rst:205 +#: ../backup_db_incremental.rst:21 msgid "" -"**Conclusion. **\\ Using a configuration group to set a single option on a " -"single database is obviously a trivial example. However, configuration " -"groups can provide major efficiencies when you consider that:" +"ID of the instance (``INSTANCE_ID``): ``792a6a56-278f-4a01-9997-" +"d997fa126370``" msgstr "" -#: ../dashboard_databases.rst:19 -msgid "**Configure a default datastore.**" -msgstr "" - -#: ../set_up_clustering.rst:35 -msgid "**Create a cluster**" -msgstr "" - -#: ../manage_db_config.rst:86 -msgid "**Create a configuration group**" -msgstr "" - -#: ../create_db.rst:90 -msgid "**Create a database instance**" -msgstr "" - -#: ../dashboard_databases.rst:56 +#: ../backup_db_incremental.rst:24 msgid "" -"**Create database instance. **\\ Once you have configured a default " -"datastore and verified that you have an appropriate flavor, you can create a " -"database instance." +"ID of the regular backup artifact (``BACKUP_ID``): " +"``6dc3a9b7-1f3e-4954-8582-3f2e4942cddd``" msgstr "" -#: ../set_up_replication.rst:36 -msgid "**Create the replica**" +#: ../backup_db_incremental.rst:28 +msgid "Create and use incremental backups" msgstr "" #: ../backup_db_incremental.rst:30 msgid "**Create your first incremental backup**" msgstr "" +#: ../backup_db_incremental.rst:32 +msgid "Use the trove ``backup-create`` command and specify:" +msgstr "" + +#: ../backup_db_incremental.rst:34 +msgid "" +"The ``INSTANCE_ID`` of the database instance you are doing the incremental " +"backup for (in this example, ``792a6a56-278f-4a01-9997-d997fa126370``)" +msgstr "" + +#: ../backup_db_incremental.rst:38 +msgid "The name of the incremental backup you are creating: ``backup1.1``" +msgstr "" + +#: ../backup_db_incremental.rst:40 +msgid "" +"The ``BACKUP_ID`` of the parent backup. In this case, the parent is the " +"regular backup, with an ID of ``6dc3a9b7-1f3e-4954-8582-3f2e4942cddd``" +msgstr "" + +#: ../backup_db_incremental.rst:62 +msgid "" +"Note that this command returns both the ID of the database instance you are " +"incrementally backing up (``instance_id``) and a new ID for the new " +"incremental backup artifact you just created (``id``)." +msgstr "" + #: ../backup_db_incremental.rst:66 msgid "**Create your second incremental backup**" msgstr "" -#: ../set_up_clustering.rst:150 -msgid "**Delete a cluster**" -msgstr "" - -#: ../cli_nova_configure_access_security_for_instances.rst:42 +#: ../backup_db_incremental.rst:68 msgid "" -"**Destination port on virtual machine**. Define a port range. To open a " -"single port only, enter the same value twice. ICMP does not support ports; " -"instead, you enter values to define the codes and types of ICMP traffic to " -"be allowed." -msgstr "" - -#: ../set_up_replication.rst:99 -msgid "**Detach the replica**" -msgstr "" - -#: ../create_db.rst:15 -msgid "**Determine which flavor to use for your database**" -msgstr "" - -#: ../set_up_clustering.rst:69 -msgid "**Display cluster information**" -msgstr "" - -#: ../manage_db_config.rst:128 -msgid "**Examine your existing configuration**" -msgstr "" - -#: ../create_db.rst:129 -msgid "**Get the IP address of the database instance**" -msgstr "" - -#: ../set_up_replication.rst:23 -msgid "**Get the instance ID**" -msgstr "" - -#: ../cli_config_drive.rst:62 -msgid "**Guidelines**" -msgstr "" - -#: ../cli_create_and_manage_networks.rst:242 -msgid "" -"**How to find unknown options** The unknown options can be easily found by " -"watching the output of ``create_xxx`` or ``show_xxx`` command. For example, " -"in the port creation command, we see the fixed\\_ips fields, which can be " -"used as an unknown option." -msgstr "" - -#: ../cli_config_drive.rst:45 -msgid "**Image requirements**" -msgstr "" - -#: ../set_up_clustering.rst:129 -msgid "" -"**Instance name. **\\ This name consists of the replication set name " -"followed by the string -*n*, where *n* is 1 for the first instance in a " -"replication set, 2 for the second instance, and so on. In this example, the " -"instance names are ``cluster1-rs1-1``, ``cluster1-rs1-2``, and ``cluster1-" -"rs1-3``." -msgstr "" - -#: ../manage_db_config.rst:20 -msgid "**List available options**" -msgstr "" - -#: ../set_up_clustering.rst:101 -msgid "**List cluster instances**" -msgstr "" - -#: ../set_up_clustering.rst:135 -msgid "**List clusters**" -msgstr "" - -#: ../manage_db_config.rst:217 -msgid "" -"**Maintenance. **\\ There are also a number of useful maintenance features " -"for working with configuration groups. You can:" -msgstr "" - -#: ../create_db.rst:65 -msgid "" -"**MySQL example. **\\ This example creates a flavor that you can use with a " -"MySQL database. This example has the following attributes:" -msgstr "" - -#: ../set_up_clustering.rst:117 -msgid "" -"**Naming conventions for replication sets and instances. **\\ Note that the " -"``Name`` column displays an instance name that includes the replication set " -"name. The replication set names and instance names are automatically " -"generated, following these rules:" -msgstr "" - -#: ../backup_db.rst:206 -msgid "**Notify users**" -msgstr "" - -#: ../dashboard_databases.rst:15 -msgid "" -"**Prerequisites. **\\ Before you create a database instance, you need to " -"configure a default datastore and make sure you have an appropriate flavor " -"for the type of database instance you want." -msgstr "" - -#: ../cli_nova_configure_access_security_for_instances.rst:40 -msgid "**Protocol**. Choose TCP for SSH, ICMP for pings, or UDP." -msgstr "" - -#: ../manage_db_config.rst:189 -msgid "**Re-examine the database configuration**" -msgstr "" - -#: ../set_up_clustering.rst:122 -msgid "" -"**Replication set name. **\\ This name consists of the cluster name, " -"followed by the string -rs\\ *n*, where *n* is 1 for the first replication " -"set you create, 2 for the second replication set, and so on. In this " -"example, the cluster name is ``cluster1``, and there is only one replication " -"set, so the replication set name is ``cluster1-rs1``." -msgstr "" - -#: ../backup_db.rst:104 -msgid "**Restore a database instance**" +"The name of your second incremental backup is ``backup1.2``. This time, when " +"you specify the parent, pass in the ID of the incremental backup you just " +"created in the previous step (``backup1.1``). In this example, it is " +"``1d474981-a006-4f62-b25f-43d7b8a7097e``." msgstr "" #: ../backup_db_incremental.rst:91 msgid "**Restore using incremental backups**" msgstr "" -#: ../cli_nova_configure_access_security_for_instances.rst:36 +#: ../backup_db_incremental.rst:93 msgid "" -"**Source of traffic**. Enable traffic to instances from either IP addresses " -"inside the cloud from other group members or from all IP addresses." +"Now assume that your ``guest1`` database instance is damaged and you need to " +"restore it from your incremental backups. In this example, you use the trove " +"``create`` command to create a new database instance called ``guest2``." msgstr "" -#: ../dashboard_manage_containers.rst:94 -msgid "**To copy an object from one container to another**" -msgstr "" - -#: ../dashboard_manage_containers.rst:120 -msgid "**To create a metadata-only object without a file**" -msgstr "" - -#: ../dashboard_manage_containers.rst:149 -msgid "**To create a pseudo-folder**" -msgstr "" - -#: ../dashboard_manage_containers.rst:71 -msgid "**To edit an object**" -msgstr "" - -#: ../backup_db.rst:136 -msgid "**Verify backup**" -msgstr "" - -#: ../dashboard_databases.rst:51 -msgid "**Verify flavor.**" -msgstr "" - -#: ../set_up_replication.rst:49 -msgid "**Verify replication status**" -msgstr "" - -#: ../set_up_clustering.rst:96 +#: ../backup_db_incremental.rst:98 msgid "" -"**Your application connects to this IP address. **\\ The trove ``cluster-" -"show`` command displays the IP address of the query router. This is the IP " -"address your application uses to retrieve data from the database." +"To incorporate your incremental backups, you simply use the ``--backup`` " +"parameter to pass in the ``BACKUP_ID`` of your most recent incremental " +"backup. The Database service handles the complexities of applying the chain " +"of all previous incremental backups." msgstr "" -#: ../cli_ceilometer.rst:47 -msgid "**avg**. The average of sample volumes over each period." +#: ../cli.rst:3 +msgid "OpenStack command-line clients" msgstr "" -#: ../cli_nova_launch_instance_from_volume.rst:205 -msgid "**bootindex=INDEX**" +#: ../cli_access_instance_through_a_console.rst:3 +msgid "Access an instance through a console" +msgstr "" + +#: ../cli_access_instance_through_a_console.rst:5 +msgid "" +"VNC or SPICE is used to view the console output of an instance, regardless " +"of whether or not the console log has output. This allows relaying keyboard " +"and mouse activity to and from an instance." +msgstr "" + +#: ../cli_access_instance_through_a_console.rst:9 +msgid "" +"There are three remote console access methods commonly used with OpenStack:" +msgstr "" + +#: ../cli_access_instance_through_a_console.rst:13 +msgid "An in-browser VNC client implemented using HTML5 Canvas and WebSockets" +msgstr "" + +#: ../cli_access_instance_through_a_console.rst:14 +msgid "novnc" +msgstr "" + +#: ../cli_access_instance_through_a_console.rst:17 +msgid "" +"A complete in-browser client solution for interaction with virtualized " +"instances" +msgstr "" + +#: ../cli_access_instance_through_a_console.rst:18 +msgid "spice" +msgstr "" + +#: ../cli_access_instance_through_a_console.rst:21 +msgid "A Java client offering console access to an instance" +msgstr "" + +#: ../cli_access_instance_through_a_console.rst:21 +msgid "xvpvnc" +msgstr "" + +#: ../cli_access_instance_through_a_console.rst:23 +msgid "Example:" +msgstr "" + +#: ../cli_access_instance_through_a_console.rst:25 +msgid "" +"To access an instance through a remote console, run the following command:" +msgstr "" + +#: ../cli_access_instance_through_a_console.rst:32 +msgid "The command returns a URL from which you can access your instance:" +msgstr "" + +#: ../cli_access_instance_through_a_console.rst:42 +msgid "" +"VNC\\_TYPE can be replaced by any of the above values as connection types." +msgstr "" + +#: ../cli_access_instance_through_a_console.rst:45 +msgid "" +"When using SPICE to view the console of an instance, a browser plugin can be " +"used directly on the instance page, or the ``get-vnc-console`` command can " +"be used with it, as well, by returning a token-authenticated address, as in " +"the example above." +msgstr "" + +#: ../cli_access_instance_through_a_console.rst:50 +msgid "" +"For further information and comparisons (including security considerations), " +"see the `Security Guide `__." +msgstr "" + +#: ../cli_ceilometer.rst:3 +msgid "Measure cloud resources" +msgstr "" + +#: ../cli_ceilometer.rst:5 +msgid "" +"Telemetry measures cloud resources in OpenStack. It collects data related to " +"billing. Currently, this metering service is available through only the :" +"command:`ceilometer` command-line client." +msgstr "" + +#: ../cli_ceilometer.rst:9 +msgid "To model data, Telemetry uses the following abstractions:" +msgstr "" + +#: ../cli_ceilometer.rst:12 +msgid "" +"Measures a specific aspect of resource usage, such as the existence of a " +"running instance, or ongoing performance, such as the CPU utilization for an " +"instance. Meters exist for each type of resource. For example, a separate " +"``cpu_util`` meter exists for each instance. The life cycle of a meter is " +"decoupled from the existence of its related resource. The meter persists " +"after the resource goes away." +msgstr "" + +#: ../cli_ceilometer.rst:22 +msgid "A meter has the following attributes:" +msgstr "" + +#: ../cli_ceilometer.rst:24 +msgid "String name" +msgstr "" + +#: ../cli_ceilometer.rst:26 +msgid "A unit of measurement" +msgstr "" + +#: ../cli_ceilometer.rst:28 +msgid "" +"A type, which indicates whether values increase monotonically (cumulative), " +"are interpreted as a change from the previous value (delta), or are stand-" +"alone and relate only to the current duration (gauge)" +msgstr "" + +#: ../cli_ceilometer.rst:31 +msgid "Meter" +msgstr "" + +#: ../cli_ceilometer.rst:34 +msgid "" +"An individual data point that is associated with a specific meter. A sample " +"has the same attributes as the associated meter, with the addition of time " +"stamp and value attributes. The value attribute is also known as the sample " +"``volume``." +msgstr "" + +#: ../cli_ceilometer.rst:37 +msgid "Sample" +msgstr "" + +#: ../cli_ceilometer.rst:40 +msgid "" +"A set of data point aggregates over a time duration. (In contrast, a sample " +"represents a single data point.) The Telemetry service employs the following " +"aggregation functions:" msgstr "" #: ../cli_ceilometer.rst:44 msgid "**count**. The number of samples in each period." msgstr "" -#: ../cli_nova_launch_instance_from_volume.rst:194 -msgid "**dest=DEST**" -msgstr "" - -#: ../cli_nova_launch_instance_from_volume.rst:190 -msgid "**id=ID**" -msgstr "" - #: ../cli_ceilometer.rst:45 msgid "**max**. The maximum number of sample volumes in each period." msgstr "" @@ -286,621 +460,16 @@ msgstr "" msgid "**min**. The minimum number of sample volumes in each period." msgstr "" -#: ../cli_nova_launch_instance_from_volume.rst:202 -msgid "**shutdown={preserve\\|remove}**" -msgstr "" - -#: ../cli_nova_launch_instance_from_volume.rst:197 -msgid "**size=SIZE**" -msgstr "" - -#: ../cli_nova_launch_instance_from_volume.rst:187 -msgid "**source=SOURCE**" +#: ../cli_ceilometer.rst:47 +msgid "**avg**. The average of sample volumes over each period." msgstr "" #: ../cli_ceilometer.rst:48 msgid "**sum**. The sum of sample volumes over each period." msgstr "" -#: ../manage_db_config.rst:103 -msgid "*DATASTORE_NAME*. The name of the associated data store." -msgstr "" - -#: ../manage_db_config.rst:99 -msgid "*NAME*. The name you want to use for this group." -msgstr "" - -#: ../manage_db_config.rst:101 -msgid "*VALUES*. The list of key-value pairs." -msgstr "" - -#: ../dashboard_manage_containers.rst:142 -msgid "" -"*````* is the name of the container to which you are uploading the " -"object." -msgstr "" - -#: ../create_db.rst:48 ../create_db.rst:50 ../create_db.rst:52 -#: ../create_db.rst:54 -msgid "1" -msgstr "" - -#: ../create_db.rst:52 -msgid "1024" -msgstr "" - -#: ../create_db.rst:50 -msgid "2048" -msgstr "" - -#: ../create_db.rst:48 ../create_db.rst:50 ../create_db.rst:52 -#: ../create_db.rst:54 -msgid "5" -msgstr "" - -#: ../create_db.rst:48 ../create_db.rst:54 -msgid "512" -msgstr "" - -#: ../dashboard_launch_instances.rst:121 -msgid ":guilabel:`Access & Security` tab" -msgstr "" - -#: ../dashboard_manage_shares.rst:62 -msgid ":guilabel:`Access Level`: Choose read-write or read-only." -msgstr "" - -#: ../dashboard_manage_shares.rst:64 -msgid ":guilabel:`Access To`: Fill in Access To field." -msgstr "" - -#: ../dashboard_manage_shares.rst:60 -msgid ":guilabel:`Access Type`: Choose ip, user, or cert." -msgstr "" - -#: ../dashboard_launch_instances.rst:151 -msgid ":guilabel:`Advanced Options` tab" -msgstr "" - -#: ../dashboard_create_networks.rst:58 -msgid ":guilabel:`Allocation Pools`: Specify IP address pools." -msgstr "" - -#: ../dashboard_manage_images.rst:64 -msgid ":guilabel:`Architecture`" -msgstr "" - -#: ../dashboard_manage_shares.rst:203 -msgid ":guilabel:`Confirm Password`: Enter the password again to confirm." -msgstr "" - -#: ../dashboard_create_networks.rst:37 -msgid ":guilabel:`Create Subnet`: Select this check box to create a subnet" -msgstr "" - -#: ../dashboard_stacks.rst:67 -msgid ":guilabel:`Creation Timeout` :guilabel:`(minutes)`" -msgstr "" - -#: ../dashboard_stacks.rst:92 -msgid ":guilabel:`DBName`" -msgstr "" - -#: ../dashboard_stacks.rst:95 -msgid ":guilabel:`DBPassword`" -msgstr "" - -#: ../dashboard_stacks.rst:86 -msgid ":guilabel:`DBRootPassword`" -msgstr "" - -#: ../dashboard_stacks.rst:80 -msgid ":guilabel:`DBUsername`" -msgstr "" - -#: ../dashboard_manage_shares.rst:193 -msgid ":guilabel:`DNS IP`: Enter the DNS IP address." -msgstr "" - -#: ../dashboard_create_networks.rst:60 -msgid ":guilabel:`DNS Name Servers`: Specify a name for the DNS server." -msgstr "" - -#: ../dashboard_databases.rst:75 -msgid ":guilabel:`Database Name`: Specify a name for the database instance." -msgstr "" - -#: ../dashboard_manage_images.rst:44 -msgid ":guilabel:`Description`" -msgstr "" - -#: ../dashboard_manage_shares.rst:109 ../dashboard_manage_shares.rst:175 -#: ../dashboard_manage_shares.rst:238 -msgid ":guilabel:`Description`: Enter a new description." -msgstr "" - -#: ../dashboard_manage_shares.rst:207 -msgid "" -":guilabel:`Description`: Optionally, provide a brief description for the " -"security service." -msgstr "" - -#: ../dashboard_manage_shares.rst:141 -msgid "" -":guilabel:`Description`: Optionally, provide a brief description for the " -"share network." -msgstr "" - -#: ../dashboard_manage_shares.rst:22 -msgid "" -":guilabel:`Description`: Optionally, provide a brief description for the " -"share." -msgstr "" - -#: ../dashboard_manage_volumes.rst:28 -msgid "" -":guilabel:`Description`: Optionally, provide a brief description for the " -"volume." -msgstr "" - -#: ../dashboard_manage_containers.rst:111 -msgid "" -":guilabel:`Destination Container`: Choose the destination container from the " -"list." -msgstr "" - -#: ../dashboard_manage_containers.rst:115 -msgid "" -":guilabel:`Destination object name`: Enter a name for the object in the new " -"container." -msgstr "" - -#: ../dashboard_launch_instances.rst:52 -msgid ":guilabel:`Details` tab" -msgstr "" - -#: ../dashboard_create_networks.rst:51 -msgid "" -":guilabel:`Disable Gateway`: Select this check box to disable a gateway IP " -"address." -msgstr "" - -#: ../dashboard_manage_shares.rst:197 -msgid ":guilabel:`Domain`: Enter the domain name." -msgstr "" - -#: ../dashboard_create_networks.rst:56 -msgid ":guilabel:`Enable DHCP`: Select this check box to enable DHCP." -msgstr "" - -#: ../dashboard_stacks.rst:53 -msgid ":guilabel:`Environment File/Data`" -msgstr "" - -#: ../dashboard_stacks.rst:47 -msgid ":guilabel:`Environment Source`" -msgstr "" - -#: ../dashboard_databases.rst:77 -msgid ":guilabel:`Flavor`: Select an appropriate flavor for the instance." -msgstr "" - -#: ../dashboard_manage_images.rst:61 -msgid ":guilabel:`Format`" -msgstr "" - -#: ../dashboard_create_networks.rst:48 -msgid "" -":guilabel:`Gateway IP`: Specify an IP address for a specific gateway. This " -"parameter is optional." -msgstr "" - -#: ../dashboard_create_networks.rst:62 -msgid ":guilabel:`Host Routes`: Specify the IP address of host routes." -msgstr "" - -#: ../dashboard_databases.rst:95 -msgid "" -":guilabel:`Host`: Optionally, allow the user to connect only from this host. " -"If you do not specify a host, this user will be allowed to connect from " -"anywhere." -msgstr "" - -#: ../dashboard_create_networks.rst:46 -msgid ":guilabel:`IP Version`: Select IPv4 or IPv6." -msgstr "" - -#: ../dashboard_manage_images.rst:52 -msgid ":guilabel:`Image File` or :guilabel:`Image Location`" -msgstr "" - -#: ../dashboard_manage_images.rst:47 -msgid ":guilabel:`Image Source`" -msgstr "" - -#: ../dashboard_databases.rst:89 -msgid "" -":guilabel:`Initial Admin User`: Create an initial admin user. This user will " -"have access to all the databases you create." -msgstr "" - -#: ../dashboard_databases.rst:82 -msgid ":guilabel:`Initialize Databases`: Initial Database" -msgstr "" - -#: ../dashboard_stacks.rst:98 -msgid ":guilabel:`InstanceType`" -msgstr "" - -#: ../dashboard_stacks.rst:89 -msgid ":guilabel:`KeyName`" -msgstr "" - -#: ../dashboard_stacks.rst:83 -msgid ":guilabel:`LinuxDistribution`" -msgstr "" - -#: ../dashboard_manage_shares.rst:33 -msgid ":guilabel:`Metadata`: Enter metadata for the share creation if needed." -msgstr "" - -#: ../dashboard_manage_shares.rst:92 -msgid "" -":guilabel:`Metadata`: To add share metadata, use key=value. To unset " -"metadata, use key." -msgstr "" - -#: ../dashboard_manage_images.rst:69 -msgid ":guilabel:`Minimum Disk (GB)` and :guilabel:`Minimum RAM (MB)`" -msgstr "" - -#: ../dashboard_manage_images.rst:42 -msgid ":guilabel:`Name`" -msgstr "" - -#: ../dashboard_manage_shares.rst:236 -msgid ":guilabel:`Name`: Enter a new security service name." -msgstr "" - -#: ../dashboard_manage_shares.rst:173 -msgid ":guilabel:`Name`: Enter a new share network name." -msgstr "" - -#: ../dashboard_manage_shares.rst:191 -msgid ":guilabel:`Name`: Specify a name for the security service." -msgstr "" - -#: ../dashboard_manage_shares.rst:139 -msgid ":guilabel:`Name`: Specify a name for the share network." -msgstr "" - -#: ../dashboard_create_networks.rst:44 -msgid ":guilabel:`Network Address`: Specify the IP address for the subnet." -msgstr "" - -#: ../dashboard_create_networks.rst:33 -msgid ":guilabel:`Network Name`: Specify a name to identify the network." -msgstr "" - -#: ../dashboard_create_networks.rst:31 -msgid ":guilabel:`Network` tab" -msgstr "" - -#: ../dashboard_launch_instances.rst:139 -msgid ":guilabel:`Networking` tab" -msgstr "" - -#: ../dashboard_manage_shares.rst:144 -msgid ":guilabel:`Neutron Net`: Choose a neutron network." -msgstr "" - -#: ../dashboard_manage_shares.rst:146 -msgid ":guilabel:`Neutron Subnet`: Choose a neutron subnet." -msgstr "" - -#: ../dashboard_manage_shares.rst:123 -msgid ":guilabel:`New Size (GB)`: Enter new size." -msgstr "" - -#: ../dashboard_stacks.rst:76 -msgid ":guilabel:`Password for user` :guilabel:`\"demo\"`" -msgstr "" - -#: ../dashboard_manage_shares.rst:201 -msgid ":guilabel:`Password`: Enter the password." -msgstr "" - -#: ../dashboard_databases.rst:92 -msgid "" -":guilabel:`Password`: Specify a password associated with the initial admin " -"user you just named." -msgstr "" - -#: ../dashboard_manage_containers.rst:113 -msgid "" -":guilabel:`Path`: Specify a path in which the new copy should be stored " -"inside of the selected container." -msgstr "" - -#: ../dashboard_launch_instances.rst:145 -msgid ":guilabel:`Post-Creation` tab" -msgstr "" - -#: ../dashboard_manage_images.rst:78 -msgid ":guilabel:`Protected`" -msgstr "" - -#: ../dashboard_manage_images.rst:73 -msgid ":guilabel:`Public`" -msgstr "" - -#: ../dashboard_stacks.rst:71 -msgid ":guilabel:`Rollback On Failure`" -msgstr "" - -#: ../dashboard_manage_shares.rst:195 -msgid ":guilabel:`Server`: Enter the server name." -msgstr "" - -#: ../dashboard_manage_shares.rst:107 -msgid ":guilabel:`Share Name`: Enter a new share name." -msgstr "" - -#: ../dashboard_manage_shares.rst:20 -msgid ":guilabel:`Share Name`: Specify a name for the share." -msgstr "" - -#: ../dashboard_manage_shares.rst:31 -msgid ":guilabel:`Share Network`: Choose a share network." -msgstr "" - -#: ../dashboard_manage_shares.rst:29 -msgid ":guilabel:`Share Protocol`: Select NFS, CIFS, GlusterFS, or HDFS." -msgstr "" - -#: ../dashboard_manage_shares.rst:25 -msgid ":guilabel:`Share Type`: Choose a share type." -msgstr "" - -#: ../dashboard_manage_shares.rst:27 -msgid ":guilabel:`Size (GB)`: The size of the share in gibibytes (GiB)." -msgstr "" - -#: ../dashboard_manage_volumes.rst:33 -msgid ":guilabel:`Size (GB)`: The size of the volume in gibibytes (GiB)." -msgstr "" - -#: ../dashboard_stacks.rst:64 -msgid ":guilabel:`Stack Name`" -msgstr "" - -#: ../dashboard_create_networks.rst:54 -msgid ":guilabel:`Subnet Detail` tab" -msgstr "" - -#: ../dashboard_create_networks.rst:42 -msgid ":guilabel:`Subnet Name`: Specify a name for the subnet." -msgstr "" - -#: ../dashboard_create_networks.rst:35 -msgid ":guilabel:`Subnet` tab" -msgstr "" - -#: ../dashboard_stacks.rst:38 -msgid ":guilabel:`Template Source`" -msgstr "" - -#: ../dashboard_stacks.rst:41 -msgid ":guilabel:`Template URL/File/Data`" -msgstr "" - -#: ../dashboard_manage_shares.rst:205 -msgid "" -":guilabel:`Type`: Choose the type from Active Directory, LDAP, or Kerberos." -msgstr "" - -#: ../dashboard_manage_volumes.rst:31 -msgid ":guilabel:`Type`: Leave this field blank." -msgstr "" - -#: ../dashboard_manage_shares.rst:199 -msgid ":guilabel:`User`: Enter the user name." -msgstr "" - -#: ../dashboard_manage_volumes.rst:26 -msgid ":guilabel:`Volume Name`: Specify a name for the volume." -msgstr "" - -#: ../dashboard_databases.rst:79 -msgid "" -":guilabel:`Volume Size`: Select a volume size. Volume size is expressed in " -"GB." -msgstr "" - -#: ../dashboard_manage_volumes.rst:35 -msgid ":guilabel:`Volume Source`: Select one of the following options:" -msgstr "" - -#: ../cli_nova_launch_instance_from_volume.rst:23 -#: ../cli_nova_launch_instance_from_volume.rst:33 -#: ../cli_nova_launch_instance_from_volume.rst:36 -msgid ":ref:`Attach_swap_or_ephemeral_disk_to_an_instance`" -msgstr "" - -#: ../cli_use_snapshots_to_migrate_instances.rst:18 -msgid ":ref:`Boot_a_new_instance_from_the_snapshot`" -msgstr "" - -#: ../cli_nova_launch_instance_from_volume.rst:20 -msgid ":ref:`Boot_instance_from_image_and_attach_non-bootable_volume`" -msgstr "" - -#: ../cli_use_snapshots_to_migrate_instances.rst:10 -msgid ":ref:`Create_a_snapshot_of_the_instance`" -msgstr "" - -#: ../cli_nova_launch_instance_from_volume.rst:27 -#: ../cli_nova_launch_instance_from_volume.rst:30 -msgid ":ref:`Create_volume_from_image_and_boot_instance`" -msgstr "" - -#: ../cli_use_snapshots_to_migrate_instances.rst:12 -msgid ":ref:`Download_the_snapshot_as_an_image`" -msgstr "" - -#: ../cli_use_snapshots_to_migrate_instances.rst:16 -msgid ":ref:`Import_the_snapshot_to_the_new_environment`" -msgstr "" - -#: ../cli_swift_discoverability.rst:11 -msgid ":ref:`archive-auto-extract`" -msgstr "" - -#: ../cli_swift_discoverability.rst:12 -msgid ":ref:`bulk-delete`" -msgstr "" - -#: ../cli_swift_discoverability.rst:10 -msgid ":ref:`large-object-creation`" -msgstr "" - -#: ../index.rst:38 -msgid ":ref:`search`" -msgstr "" - -#: ../cli_swift_discoverability.rst:13 -msgid ":ref:`static-website`" -msgstr "" - -#: ../sdk_assign_cors_headers.rst:5 -msgid "" -":term:`Cross-Origin Resource Sharing (CORS)` is a specification that defines " -"how browsers and servers communicate across origins by using HTTP headers, " -"such as those assigned by Object Storage API requests. The Object Storage " -"API supports the following headers:" -msgstr "" - -#: ../cli_launch_instances.rst:37 -msgid "" -"A **key pair** for your instance, which are SSH credentials that are " -"injected into images when they are launched. For the key pair to be " -"successfully injected, the image must contain the ``cloud-init`` package. " -"Create at least one key pair for each project. If you already have generated " -"a key pair with an external tool, you can import it into OpenStack. You can " -"use the key pair for multiple instances that belong to that project." -msgstr "" - -#: ../cli_launch_instances.rst:18 -msgid "A **name** for your instance." -msgstr "" - -#: ../cli_launch_instances.rst:45 -msgid "" -"A **security group** that defines which incoming network traffic is " -"forwarded to instances. Security groups hold a set of firewall policies, " -"known as *security group rules*." -msgstr "" - -#: ../cli_nova_configure_access_security_for_instances.rst:17 -msgid "" -"A *security group* is a named collection of network access rules that are " -"use to limit the types of traffic that have access to instances. When you " -"launch an instance, you can assign one or more security groups to it. If you " -"do not create security groups, new instances are automatically assigned to " -"the default security group, unless you explicitly specify a different " -"security group." -msgstr "" - -#: ../cli_access_instance_through_a_console.rst:21 -msgid "A Java client offering console access to an instance" -msgstr "" - -#: ../sdk_schedule_objects_for_deletion.rst:18 -msgid "" -"A UNIX epoch timestamp, in integer form. For example, ``1348691905`` " -"represents ``Wed, 26 Sept 2012 20:38:25 GMT``. It specifies the time you " -"want the object to expire, no longer be served, and be deleted completely " -"from the object store." -msgstr "" - -#: ../cli_swift_set_object_versions.rst:138 -msgid "" -"A ``POST`` request to a versioned object updates only the metadata for the " -"object and does not create a new version of the object. New versions are " -"created only when the content of the object changes." -msgstr "" - -#: ../cli_swift_large_object_creation.rst:21 -msgid "" -"A ``manifest object`` links the segment objects into one logical large " -"object. When you download a manifest object, Object Storage concatenates and " -"returns the contents of the segment objects in the response body of the " -"request. This behavior extends to the response headers returned by ``GET`` " -"and ``HEAD`` requests. The ``Content-Length`` response header value is the " -"total size of all segment objects. Object Storage calculates the ``ETag`` " -"response header value by taking the ``ETag`` value of each segment, " -"concatenating them together, and returning the MD5 checksum of the result. " -"The manifest object types are:" -msgstr "" - -#: ../cli_manage_bare_metal_nodes.rst:103 -msgid "" -"A bare-metal instance is an instance created directly on a physical machine, " -"without any virtualization layer running underneath it. Nova retains power " -"control via IPMI. In some situations, Nova may retain network control via " -"Neutron and OpenFlow." -msgstr "" - -#: ../cli_access_instance_through_a_console.rst:17 -msgid "" -"A complete in-browser client solution for interaction with virtualized " -"instances" -msgstr "" - -#: ../manage_db_config.rst:209 -msgid "A configuration group can specify a large number of option values." -msgstr "" - -#: ../manage_db_config.rst:88 -msgid "" -"A configuration group contains a comma-separated list of key-value pairs. " -"Each pair consists of a configuration option and its value." -msgstr "" - -# #-#-#-#-# dashboard_manage_shares.pot (End User Guide 1.0.0) #-#-#-#-# -# #-#-#-#-# dashboard_manage_volumes.pot (End User Guide 1.0.0) #-#-#-#-# -#: ../dashboard_manage_shares.rst:48 ../dashboard_manage_shares.rst:68 -#: ../dashboard_manage_shares.rst:82 ../dashboard_manage_shares.rst:97 -#: ../dashboard_manage_shares.rst:113 ../dashboard_manage_shares.rst:127 -#: ../dashboard_manage_shares.rst:162 ../dashboard_manage_shares.rst:179 -#: ../dashboard_manage_shares.rst:225 ../dashboard_manage_shares.rst:242 -#: ../dashboard_manage_volumes.rst:104 ../dashboard_manage_volumes.rst:175 -msgid "A message indicates whether the action was successful." -msgstr "" - -#: ../cli_ceilometer.rst:22 -msgid "A meter has the following attributes:" -msgstr "" - -#: ../cli_manage_ip_addresses.rst:14 -msgid "" -"A pool of floating IP addresses, configured by the cloud administrator, is " -"available in OpenStack Compute. The project quota defines the maximum number " -"of floating IP addresses that you can allocate to the project. After you " -"allocate a floating IP address to a project, you can:" -msgstr "" - -#: ../cli_create_and_manage_stacks.rst:103 -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_ceilometer.rst:40 -msgid "" -"A set of data point aggregates over a time duration. (In contrast, a sample " -"represents a single data point.) The Telemetry service employs the following " -"aggregation functions:" +#: ../cli_ceilometer.rst:48 +msgid "Statistic" msgstr "" #: ../cli_ceilometer.rst:51 @@ -916,10 +485,924 @@ msgid "" "configurable length into the recent past." msgstr "" -#: ../dashboard_manage_containers.rst:173 +#: ../cli_ceilometer.rst:60 +msgid "Alarm" +msgstr "" + +#: ../cli_ceilometer.rst:62 msgid "" -"A slash (/) character is used as the delimiter for pseudo-folders in Object " -"Storage." +"This example uses the :command:`heat` client to create an auto-scaling stack " +"and the :command:`ceilometer` client to measure resources." +msgstr "" + +#: ../cli_ceilometer.rst:65 +msgid "" +"Create an auto-scaling stack by running the following command. The :option:`-" +"f` option specifies the name of the stack template file, and the :option:`-" +"P` option specifies the :code:`KeyName` parameter as :code:`heat_key`::" +msgstr "" + +#: ../cli_ceilometer.rst:72 +msgid "List the heat resources that were created::" +msgstr "" + +#: ../cli_ceilometer.rst:89 +msgid "List the alarms that are set::" +msgstr "" + +#: ../cli_ceilometer.rst:99 +msgid "List the meters that are set::" +msgstr "" + +#: ../cli_ceilometer.rst:110 +msgid "List samples::" +msgstr "" + +#: ../cli_ceilometer.rst:119 +msgid "View statistics::" +msgstr "" + +#: ../cli_change_the_size_of_your_server.rst:3 +msgid "Change the size of your server" +msgstr "" + +#: ../cli_change_the_size_of_your_server.rst:5 +msgid "Change the size of a server by changing its flavor." +msgstr "" + +#: ../cli_change_the_size_of_your_server.rst:7 +msgid "" +"Show information about your server, including its size, which is shown as " +"the value of the flavor property::" +msgstr "" + +#: ../cli_change_the_size_of_your_server.rst:42 +msgid "The size (flavor) of the server is ``m1.small (2)``." +msgstr "" + +#: ../cli_change_the_size_of_your_server.rst:44 +msgid "List the available flavors with the following command::" +msgstr "" + +#: ../cli_change_the_size_of_your_server.rst:57 +msgid "" +"To resize the server, use the ``nova resize`` command and add the server ID " +"or name and the new flavor. Include the ``--poll`` parameter to display the " +"resize progress. For example::" +msgstr "" + +#: ../cli_change_the_size_of_your_server.rst:68 +msgid "" +"By default, the :command:`nova resize` command gives the guest operating " +"system a chance to perform a controlled shutdown before the instance is " +"powered off and the instance is resized. The shutdown behavior is configured " +"by the ``shutdown_timeout`` parameter that can be set in the :file:`nova." +"conf` file. Its value stands for the overall period (in seconds) a guest " +"operation system is allowed to complete the shutdown. The default timeout is " +"60 seconds. See `Description of Compute configuration options `_ for details." +msgstr "" + +# #-#-#-#-# cli_change_the_size_of_your_server.pot (End User Guide 1.0.0) #-#-#-#-# +# #-#-#-#-# cli_reboot_an_instance.pot (End User Guide 1.0.0) #-#-#-#-# +# #-#-#-#-# cli_stop_and_start_an_instance.pot (End User Guide 1.0.0) #-#-#-#-# +#: ../cli_change_the_size_of_your_server.rst:80 +#: ../cli_reboot_an_instance.rst:54 ../cli_stop_and_start_an_instance.rst:66 +msgid "" +"The timeout value can be overridden on a per image basis by means of " +"``os_shutdown_timeout`` that is an image metadata setting allowing different " +"types of operating systems to specify how much time they need to shut down " +"cleanly." +msgstr "" + +#: ../cli_change_the_size_of_your_server.rst:85 +msgid "Show the status for your server::" +msgstr "" + +#: ../cli_change_the_size_of_your_server.rst:94 +msgid "When the resize completes, the status becomes VERIFY\\_RESIZE." +msgstr "" + +#: ../cli_change_the_size_of_your_server.rst:96 +msgid "Confirm the resize,for example::" +msgstr "" + +#: ../cli_change_the_size_of_your_server.rst:100 +#: ../cli_change_the_size_of_your_server.rst:108 +msgid "The server status becomes ACTIVE." +msgstr "" + +#: ../cli_change_the_size_of_your_server.rst:102 +msgid "" +"If the resize fails or does not work as expected, you can revert the resize. " +"For example::" +msgstr "" + +#: ../cli_cheat_sheet.rst:3 +msgid "OpenStack command-line interface cheat sheet" +msgstr "" + +#: ../cli_cheat_sheet.rst:5 +msgid "Here is a list of common commands for reference." +msgstr "" + +#: ../cli_cheat_sheet.rst:8 +msgid "Identity (keystone)" +msgstr "" + +#: ../cli_cheat_sheet.rst:10 +msgid "List all users" +msgstr "" + +#: ../cli_cheat_sheet.rst:16 +msgid "List Identity service catalog" +msgstr "" + +#: ../cli_cheat_sheet.rst:23 +msgid "Images (glance)" +msgstr "" + +#: ../cli_cheat_sheet.rst:25 +msgid "List images you can access" +msgstr "" + +#: ../cli_cheat_sheet.rst:31 +msgid "Delete specified image" +msgstr "" + +#: ../cli_cheat_sheet.rst:37 +msgid "Describe a specific image" +msgstr "" + +#: ../cli_cheat_sheet.rst:43 +msgid "Update image" +msgstr "" + +#: ../cli_cheat_sheet.rst:49 +msgid "Upload kernel image" +msgstr "" + +#: ../cli_cheat_sheet.rst:57 +msgid "Upload RAM image" +msgstr "" + +#: ../cli_cheat_sheet.rst:65 +msgid "Upload three-part image" +msgstr "" + +#: ../cli_cheat_sheet.rst:74 +msgid "Register raw image" +msgstr "" + +#: ../cli_cheat_sheet.rst:83 +msgid "Compute (nova)" +msgstr "" + +#: ../cli_cheat_sheet.rst:85 +msgid "List instances, check status of instance" +msgstr "" + +# #-#-#-#-# cli_cheat_sheet.pot (End User Guide 1.0.0) #-#-#-#-# +# #-#-#-#-# sdk_manage_images.pot (End User Guide 1.0.0) #-#-#-#-# +#: ../cli_cheat_sheet.rst:91 ../sdk_manage_images.rst:14 +msgid "List images" +msgstr "" + +#: ../cli_cheat_sheet.rst:97 +msgid "List flavors" +msgstr "" + +#: ../cli_cheat_sheet.rst:103 +msgid "Boot an instance using flavor and image names (if names are unique)" +msgstr "" + +#: ../cli_cheat_sheet.rst:111 +msgid "Login to instance" +msgstr "" + +#: ../cli_cheat_sheet.rst:120 +msgid "" +"In CirrOS the password for user ``cirros`` is \"cubswin:)\" without the " +"quotes." +msgstr "" + +#: ../cli_cheat_sheet.rst:123 +msgid "Show details of instance" +msgstr "" + +#: ../cli_cheat_sheet.rst:130 +msgid "View console log of instance" +msgstr "" + +#: ../cli_cheat_sheet.rst:136 +msgid "Set metadata on an instance" +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:142 ../dashboard_launch_instances.rst:211 +msgid "Create an instance snapshot" +msgstr "" + +#: ../cli_cheat_sheet.rst:150 +msgid "Pause, suspend, stop, rescue, resize, rebuild, reboot an instance" +msgstr "" + +#: ../cli_cheat_sheet.rst:152 +msgid "Pause" +msgstr "" + +#: ../cli_cheat_sheet.rst:159 +msgid "Unpause" +msgstr "" + +#: ../cli_cheat_sheet.rst:165 +msgid "Suspend" +msgstr "" + +#: ../cli_cheat_sheet.rst:171 +msgid "Unsuspend" +msgstr "" + +#: ../cli_cheat_sheet.rst:177 +msgid "Stop" +msgstr "" + +#: ../cli_cheat_sheet.rst:183 +msgid "Start" +msgstr "" + +#: ../cli_cheat_sheet.rst:189 +msgid "Rescue" +msgstr "" + +#: ../cli_cheat_sheet.rst:196 +msgid "Resize" +msgstr "" + +#: ../cli_cheat_sheet.rst:204 +msgid "Rebuild" +msgstr "" + +#: ../cli_cheat_sheet.rst:211 +msgid "Reboot" +msgstr "" + +#: ../cli_cheat_sheet.rst:218 +msgid "Inject user data and files into an instance" +msgstr "" + +#: ../cli_cheat_sheet.rst:226 +msgid "" +"To validate that the file was injected, use ssh to connect to the instance, " +"and look in ``/var/lib/cloud`` for the file." +msgstr "" + +#: ../cli_cheat_sheet.rst:229 +msgid "" +"Inject a keypair into an instance and access the instance with that keypair" +msgstr "" + +#: ../cli_cheat_sheet.rst:232 +msgid "Create keypair" +msgstr "" + +#: ../cli_cheat_sheet.rst:239 +msgid "Start an instance (boot)" +msgstr "" + +#: ../cli_cheat_sheet.rst:246 +msgid "Use ssh to connect to the instance" +msgstr "" + +#: ../cli_cheat_sheet.rst:253 +msgid "Manage security groups" +msgstr "" + +#: ../cli_cheat_sheet.rst:255 +msgid "" +"Add rules to default security group allowing ping and SSH between instances " +"in the default security group" +msgstr "" + +#: ../cli_cheat_sheet.rst:264 +msgid "Networking (neutron)" +msgstr "" + +# #-#-#-#-# cli_cheat_sheet.pot (End User Guide 1.0.0) #-#-#-#-# +# #-#-#-#-# sdk_neutron_apis.pot (End User Guide 1.0.0) #-#-#-#-# +#: ../cli_cheat_sheet.rst:266 ../sdk_neutron_apis.rst:131 +msgid "Create network" +msgstr "" + +#: ../cli_cheat_sheet.rst:272 +msgid "Create a subnet" +msgstr "" + +#: ../cli_cheat_sheet.rst:280 +msgid "Block Storage (cinder)" +msgstr "" + +#: ../cli_cheat_sheet.rst:282 +msgid "Used to manage volumes and volume snapshots that attach to instances." +msgstr "" + +#: ../cli_cheat_sheet.rst:284 +msgid "Create a new volume" +msgstr "" + +#: ../cli_cheat_sheet.rst:291 +msgid "Boot an instance and attach to volume" +msgstr "" + +#: ../cli_cheat_sheet.rst:297 +msgid "List volumes, notice status of volume" +msgstr "" + +#: ../cli_cheat_sheet.rst:303 +msgid "" +"Attach volume to instance after instance is active, and volume is available" +msgstr "" + +#: ../cli_cheat_sheet.rst:311 +msgid "Manage volumes after login into the instance" +msgstr "" + +#: ../cli_cheat_sheet.rst:313 +msgid "List storage devices" +msgstr "" + +#: ../cli_cheat_sheet.rst:319 +msgid "Make filesystem on volume" +msgstr "" + +#: ../cli_cheat_sheet.rst:325 +msgid "Create a mountpoint" +msgstr "" + +#: ../cli_cheat_sheet.rst:331 +msgid "Mount the volume at the mountpoint" +msgstr "" + +#: ../cli_cheat_sheet.rst:337 +msgid "Create a file on the volume" +msgstr "" + +#: ../cli_cheat_sheet.rst:344 +msgid "Unmount the volume" +msgstr "" + +#: ../cli_cheat_sheet.rst:351 +msgid "Object Storage (swift)" +msgstr "" + +#: ../cli_cheat_sheet.rst:353 +msgid "Display information for the account, container, or object" +msgstr "" + +#: ../cli_cheat_sheet.rst:362 +msgid "List containers" +msgstr "" + +#: ../cli_config_drive.rst:3 +msgid "Store metadata on a configuration drive" +msgstr "" + +#: ../cli_config_drive.rst:4 +msgid "" +"You can configure OpenStack to write metadata to a special configuration " +"drive that attaches to the instance when it boots. The instance can mount " +"this drive and read files from it to get information that is normally " +"available through the `metadata service `__. This metadata " +"is different from the user data." +msgstr "" + +#: ../cli_config_drive.rst:10 +msgid "" +"One use case for using the configuration drive is to pass a networking " +"configuration when you do not use DHCP to assign IP addresses to instances. " +"For example, you might pass the IP address configuration for the instance " +"through the configuration drive, which the instance can mount and access " +"before you configure the network settings for the instance." +msgstr "" + +#: ../cli_config_drive.rst:17 +msgid "" +"Any modern guest operating system that is capable of mounting an ISO 9660 or " +"VFAT file system can use the configuration drive." +msgstr "" + +#: ../cli_config_drive.rst:21 +msgid "Requirements and guidelines" +msgstr "" + +#: ../cli_config_drive.rst:23 +msgid "" +"To use the configuration drive, you must follow the following requirements " +"for the compute host and image." +msgstr "" + +#: ../cli_config_drive.rst:26 +msgid "**Compute host requirements**" +msgstr "" + +#: ../cli_config_drive.rst:28 +msgid "" +"The following hypervisors support the configuration drive: libvirt, " +"XenServer, Hyper-V, and VMware." +msgstr "" + +#: ../cli_config_drive.rst:31 +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 +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 +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 " +"must set the ``qemu_img_cmd`` value in the ``hyperv`` configuration section " +"to the full path to an :command:`qemu-img` command installation." +msgstr "" + +#: ../cli_config_drive.rst:45 +msgid "**Image requirements**" +msgstr "" + +#: ../cli_config_drive.rst:47 +msgid "" +"An image built with a recent version of the cloud-init package can " +"automatically access metadata passed through the configuration drive. The " +"cloud-init package version 0.7.1 works with Ubuntu and Fedora based images, " +"such as Red Hat Enterprise Linux." +msgstr "" + +#: ../cli_config_drive.rst:52 +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 " +"boot, reads the data from the drive, and takes appropriate action such as " +"adding the public key to an account. You can read more details about how " +"data is organized on the configuration drive." +msgstr "" + +#: ../cli_config_drive.rst:58 +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 +msgid "**Guidelines**" +msgstr "" + +#: ../cli_config_drive.rst:64 +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 +msgid "" +"When you create images that access configuration drive data and multiple " +"directories are under the ``openstack`` directory, always select the highest " +"API version by date that your consumer supports. For example, if your guest " +"image supports the 2012-03-05, 2012-08-05, and 2013-04-13 versions, try " +"2013-04-13 first and fall back to a previous version if 2013-04-13 is not " +"present." +msgstr "" + +#: ../cli_config_drive.rst:76 +msgid "Enable and access the configuration drive" +msgstr "" + +#: ../cli_config_drive.rst:78 +msgid "" +"To enable the configuration drive, pass the ``--config-drive true`` " +"parameter to the :command:`nova boot` command." +msgstr "" + +#: ../cli_config_drive.rst:81 +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:91 +msgid "" +"You can also configure the Compute service to always create a configuration " +"drive by setting the following option in the :file:`/etc/nova/nova.conf` " +"file::" +msgstr "" + +#: ../cli_config_drive.rst:99 +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:103 +msgid "" +"If your guest operating system supports accessing disk by label, you can " +"mount the configuration drive as the ``/dev/disk/by-label/" +"configurationDriveVolumeLabel`` device. In the following example, the " +"configuration drive has the ``config-2`` volume label::" +msgstr "" + +#: ../cli_config_drive.rst:114 +msgid "" +"Ensure that you use at least version 0.3.1 of CirrOS for configuration drive " +"support." +msgstr "" + +#: ../cli_config_drive.rst:117 +msgid "" +"If your guest operating system does not use ``udev``, the ``/dev/disk/by-" +"label`` directory is not present." +msgstr "" + +#: ../cli_config_drive.rst:120 +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:133 +msgid "Once identified, you can mount the device::" +msgstr "" + +#: ../cli_config_drive.rst:139 +msgid "Configuration drive contents" +msgstr "" + +#: ../cli_config_drive.rst:141 +msgid "" +"In this example, the contents of the configuration drive are as follows::" +msgstr "" + +#: ../cli_config_drive.rst:155 +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:159 +msgid "OpenStack metadata format" +msgstr "" + +#: ../cli_config_drive.rst:161 +msgid "" +"The following example shows the contents of the :file:`openstack/2012-08-10/" +"meta_data.json` and :file:`openstack/latest/meta_data.json` files. These " +"files are identical. The file contents are formatted for readability." +msgstr "" + +#: ../cli_config_drive.rst:193 +msgid "" +"Note the effect of the ``--file /etc/network/interfaces=/home/myuser/" +"instance-interfaces`` argument that was passed to the :command:`nova boot` " +"command. The contents of this file are contained in the :file:`openstack/" +"content/0000` file on the configuration drive, and the path is specified as :" +"file:`/etc/network/interfaces` in the :file:`meta_data.json` file." +msgstr "" + +#: ../cli_config_drive.rst:201 +msgid "EC2 metadata format" +msgstr "" + +#: ../cli_config_drive.rst:203 +msgid "" +"The following example shows the contents of the :file:`ec2/2009-04-04/meta-" +"data.json` and the :file:`ec2/latest/meta-data.json` files. These files are " +"identical. The file contents are formatted to improve readability." +msgstr "" + +#: ../cli_config_drive.rst:245 +msgid "User data" +msgstr "" + +#: ../cli_config_drive.rst:247 +msgid "" +"The :file:`openstack/2012-08-10/user_data`, :file:`openstack/latest/" +"user_data`, :file:`ec2/2009-04-04/user-data`, and :file:`ec2/latest/user-" +"data` file are present only if the ``--user-data`` flag and the contents of " +"the user data file are passed to the :command:`nova boot` command." +msgstr "" + +#: ../cli_config_drive.rst:253 +msgid "Configuration drive format" +msgstr "" + +#: ../cli_config_drive.rst:255 +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 :file:" +"`/etc/nova/nova.conf` file::" +msgstr "" + +#: ../cli_config_drive.rst:261 +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 :file:`/etc/nova/nova.conf` file::" +msgstr "" + +#: ../cli_config_drive.rst:267 +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 " +"format because ISO 9660 is widely supported across operating systems. " +"However, to use the VFAT format, add the following line to the :file:`/etc/" +"nova/nova.conf` file::" +msgstr "" + +#: ../cli_config_drive.rst:275 +msgid "If you choose VFAT, the configuration drive is 64 MB." +msgstr "" + +#: ../cli_config_drive.rst:279 +msgid "" +"In current version (Kilo) of OpenStack Compute, live migration with " +"``config_drive`` on local disk is forbidden due to the bug in libvirt of " +"copying a read-only disk. However, if we use VFAT as the format of " +"``config_drive``, the function of live migration works well." +msgstr "" + +# #-#-#-#-# cli_create_and_manage_networks.pot (End User Guide 1.0.0) #-#-#-#-# +# #-#-#-#-# dashboard_create_networks.pot (End User Guide 1.0.0) #-#-#-#-# +#: ../cli_create_and_manage_networks.rst:3 ../dashboard_create_networks.rst:3 +msgid "Create and manage networks" +msgstr "" + +#: ../cli_create_and_manage_networks.rst:5 +msgid "Before you run commands, set the following environment variables:" +msgstr "" + +#: ../cli_create_and_manage_networks.rst:15 +msgid "Create networks" +msgstr "" + +#: ../cli_create_and_manage_networks.rst:17 +msgid "List the extensions of the system::" +msgstr "" + +#: ../cli_create_and_manage_networks.rst:34 +msgid "Create a network::" +msgstr "" + +#: ../cli_create_and_manage_networks.rst:57 +msgid "Some fields of the created network are invisible to non-admin users." +msgstr "" + +#: ../cli_create_and_manage_networks.rst:59 +msgid "Create a network with specified provider network type::" +msgstr "" + +#: ../cli_create_and_manage_networks.rst:80 +msgid "" +"Just as shown previously, the unknown option ``--provider:network-type`` is " +"used to create a ``local`` provider network." +msgstr "" + +#: ../cli_create_and_manage_networks.rst:84 +msgid "Create subnets" +msgstr "" + +#: ../cli_create_and_manage_networks.rst:86 +msgid "Create a subnet::" +msgstr "" + +#: ../cli_create_and_manage_networks.rst:107 +msgid "" +"The ``subnet-create`` command has the following positional and optional " +"parameters:" +msgstr "" + +#: ../cli_create_and_manage_networks.rst:110 +msgid "The name or ID of the network to which the subnet belongs." +msgstr "" + +#: ../cli_create_and_manage_networks.rst:112 +msgid "" +"In this example, ``net1`` is a positional argument that specifies the " +"network name." +msgstr "" + +#: ../cli_create_and_manage_networks.rst:115 +msgid "The CIDR of the subnet." +msgstr "" + +#: ../cli_create_and_manage_networks.rst:117 +msgid "" +"In this example, ``192.168.2.0/24`` is a positional argument that specifies " +"the CIDR." +msgstr "" + +#: ../cli_create_and_manage_networks.rst:120 +msgid "The subnet name, which is optional." +msgstr "" + +#: ../cli_create_and_manage_networks.rst:122 +msgid "In this example, ``--name subnet1`` specifies the name of the subnet." +msgstr "" + +#: ../cli_create_and_manage_networks.rst:125 +msgid "" +"For information and examples on more advanced use of neutron's ``subnet`` " +"subcommand, see the `Cloud Administrator Guide `__." +msgstr "" + +#: ../cli_create_and_manage_networks.rst:130 +msgid "Create routers" +msgstr "" + +#: ../cli_create_and_manage_networks.rst:132 +msgid "Create a router::" +msgstr "" + +#: ../cli_create_and_manage_networks.rst:148 +msgid "" +"Take note of the unique router identifier returned, this will be required in " +"subsequent steps." +msgstr "" + +#: ../cli_create_and_manage_networks.rst:151 +msgid "Link the router to the external provider network::" +msgstr "" + +#: ../cli_create_and_manage_networks.rst:155 +msgid "" +"Replace ROUTER with the unique identifier of the router, replace NETWORK " +"with the unique identifier of the external provider network." +msgstr "" + +#: ../cli_create_and_manage_networks.rst:158 +msgid "Link the router to the subnet::" +msgstr "" + +#: ../cli_create_and_manage_networks.rst:162 +msgid "" +"Replace ROUTER with the unique identifier of the router, replace SUBNET with " +"the unique identifier of the subnet." +msgstr "" + +# #-#-#-#-# cli_create_and_manage_networks.pot (End User Guide 1.0.0) #-#-#-#-# +# #-#-#-#-# sdk_neutron_apis.pot (End User Guide 1.0.0) #-#-#-#-# +#: ../cli_create_and_manage_networks.rst:166 ../sdk_neutron_apis.rst:188 +msgid "Create ports" +msgstr "" + +#: ../cli_create_and_manage_networks.rst:168 +msgid "Create a port with specified IP address::" +msgstr "" + +#: ../cli_create_and_manage_networks.rst:190 +msgid "" +"In the previous command, ``net1`` is the network name, which is a positional " +"argument. ``--fixed-ip ip_address=192.168.2.40`` is an option, which " +"specifies the port's fixed IP address we wanted." +msgstr "" + +#: ../cli_create_and_manage_networks.rst:196 +msgid "" +"When creating a port, you can specify any unallocated IP in the subnet even " +"if the address is not in a pre-defined pool of allocated IP addresses (set " +"by your cloud provider)." +msgstr "" + +#: ../cli_create_and_manage_networks.rst:200 +msgid "Create a port without specified IP address::" +msgstr "" + +#: ../cli_create_and_manage_networks.rst:224 +msgid "" +"Note that the system allocates one IP address if you do not specify an IP " +"address in the ``neutron port-create`` command." +msgstr "" + +#: ../cli_create_and_manage_networks.rst:227 +msgid "Query ports with specified fixed IP addresses::" +msgstr "" + +#: ../cli_create_and_manage_networks.rst:239 +msgid "" +"``--fixed-ips ip_address=192.168.2.2 ip_address=192.168.2.40`` is one " +"unknown option." +msgstr "" + +#: ../cli_create_and_manage_networks.rst:242 +msgid "" +"**How to find unknown options** The unknown options can be easily found by " +"watching the output of ``create_xxx`` or ``show_xxx`` command. For example, " +"in the port creation command, we see the fixed\\_ips fields, which can be " +"used as an unknown option." +msgstr "" + +#: ../cli_create_and_manage_stacks.rst:3 +msgid "Create and manage stacks" +msgstr "" + +#: ../cli_create_and_manage_stacks.rst:5 +msgid "" +"The Orchestration module enables you to orchestrate multiple composite cloud " +"applications. This module supports use of both the Amazon Web Services (AWS) " +"CloudFormation template format through both a Query API that is compatible " +"with CloudFormation and the native OpenStack :term:`Heat Orchestration " +"Template (HOT)` format through a REST API." +msgstr "" + +#: ../cli_create_and_manage_stacks.rst:11 +msgid "" +"These flexible template languages enable application developers to describe " +"and automate the deployment of infrastructure, services, and applications. " +"The templates enable creation of most OpenStack resource types, such as " +"instances, floating IP addresses, volumes, security groups, and users. The " +"resources, once created, are referred to as stacks." +msgstr "" + +#: ../cli_create_and_manage_stacks.rst:18 +msgid "" +"The template languages are described in `the Template Guide `__ in the `Heat " +"developer documentation `__." +msgstr "" + +#: ../cli_create_and_manage_stacks.rst:24 +msgid "Create a stack from an example template file" +msgstr "" + +#: ../cli_create_and_manage_stacks.rst:26 +msgid "" +"To create a stack, or template, from an `example template file `__, run the following command::" +msgstr "" + +#: ../cli_create_and_manage_stacks.rst:33 +msgid "" +"The :option:`--parameters` values that you specify depend on the parameters " +"that are defined in the template. If a website hosts the template file, you " +"can specify the URL with the :option:`--template-url` parameter instead of " +"the :option:`--template-file` parameter." +msgstr "" + +#: ../cli_create_and_manage_stacks.rst:38 +msgid "The command returns the following output::" +msgstr "" + +#: ../cli_create_and_manage_stacks.rst:46 +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:51 +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:55 +msgid "To do so, run the following command::" +msgstr "" + +#: ../cli_create_and_manage_stacks.rst:59 +msgid "If validation fails, the response returns an error message." +msgstr "" + +#: ../cli_create_and_manage_stacks.rst:62 +msgid "Get information about stacks" +msgstr "" + +#: ../cli_create_and_manage_stacks.rst:64 +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:67 +msgid "" +"To see which stacks are visible to the current user, run the following " +"command::" +msgstr "" + +#: ../cli_create_and_manage_stacks.rst:78 +msgid "To show the details of a stack, run the following command::" msgstr "" #: ../cli_create_and_manage_stacks.rst:82 @@ -928,8 +1411,291 @@ msgid "" "their status, run the following command::" msgstr "" -#: ../cli_launch_instances.rst:221 -msgid "A status of ``ACTIVE`` indicates that the instance is active." +#: ../cli_create_and_manage_stacks.rst:92 +msgid "" +"To show the details for a specific resource in a stack, run the following " +"command::" +msgstr "" + +#: ../cli_create_and_manage_stacks.rst:97 +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:103 +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:114 +msgid "To show the details for a particular event, run the following command::" +msgstr "" + +#: ../cli_create_and_manage_stacks.rst:120 +msgid "Update a stack" +msgstr "" + +#: ../cli_create_and_manage_stacks.rst:122 +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:135 +msgid "" +"Some resources are updated in-place, while others are replaced with new " +"resources." +msgstr "" + +#: ../cli_delete_an_instance.rst:3 +msgid "Delete an instance" +msgstr "" + +#: ../cli_delete_an_instance.rst:5 +msgid "When you no longer need an instance, you can delete it." +msgstr "" + +#: ../cli_delete_an_instance.rst:7 +msgid "List all instances::" +msgstr "" + +#: ../cli_delete_an_instance.rst:19 +msgid "" +"Run the :command:`nova delete` command to delete the instance. The following " +"example shows deletion of the ``newServer`` instance, which is in ``ERROR`` " +"state::" +msgstr "" + +#: ../cli_delete_an_instance.rst:25 +msgid "The command does not notify that your server was deleted." +msgstr "" + +#: ../cli_delete_an_instance.rst:27 +msgid "" +"To verify that the server was deleted, run the :command:`nova list` command::" +msgstr "" + +#: ../cli_delete_an_instance.rst:38 +msgid "The deleted instance does not appear in the list." +msgstr "" + +#: ../cli_launch_instances.rst:3 +msgid "Launch instances" +msgstr "" + +#: ../cli_launch_instances.rst:11 +msgid "Instances are virtual machines that run inside the cloud." +msgstr "" + +#: ../cli_launch_instances.rst:13 +msgid "Before you can launch an instance, gather the following parameters:" +msgstr "" + +#: ../cli_launch_instances.rst:15 +msgid "" +"The **instance source** can be an image, snapshot, or block storage volume " +"that contains an image or snapshot." +msgstr "" + +#: ../cli_launch_instances.rst:18 +msgid "A **name** for your instance." +msgstr "" + +#: ../cli_launch_instances.rst:20 +msgid "" +"The **flavor** for your instance, which defines the compute, memory, and " +"storage capacity of nova computing instances. A flavor is an available " +"hardware configuration for a server. It defines the size of a virtual server " +"that can be launched." +msgstr "" + +#: ../cli_launch_instances.rst:25 +msgid "" +"Any **user data** files. A user data file is a special key in the metadata " +"service that holds a file that cloud-aware applications in the guest " +"instance can access. For example, one application that uses user data is the " +"`cloud-init `__ system, which " +"is an open-source package from Ubuntu that is available on various Linux " +"distributions and that handles early initialization of a cloud instance." +msgstr "" + +#: ../cli_launch_instances.rst:34 +msgid "" +"Access and security credentials, which include one or both of the following " +"credentials:" +msgstr "" + +#: ../cli_launch_instances.rst:37 +msgid "" +"A **key pair** for your instance, which are SSH credentials that are " +"injected into images when they are launched. For the key pair to be " +"successfully injected, the image must contain the ``cloud-init`` package. " +"Create at least one key pair for each project. If you already have generated " +"a key pair with an external tool, you can import it into OpenStack. You can " +"use the key pair for multiple instances that belong to that project." +msgstr "" + +#: ../cli_launch_instances.rst:45 +msgid "" +"A **security group** that defines which incoming network traffic is " +"forwarded to instances. Security groups hold a set of firewall policies, " +"known as *security group rules*." +msgstr "" + +#: ../cli_launch_instances.rst:49 +msgid "" +"If needed, you can assign a **floating (public) IP address** to a running " +"instance." +msgstr "" + +#: ../cli_launch_instances.rst:52 +msgid "" +"You can also attach a block storage device, or **volume**, for persistent " +"storage." +msgstr "" + +# #-#-#-#-# cli_launch_instances.pot (End User Guide 1.0.0) #-#-#-#-# +# #-#-#-#-# cli_nova_configure_access_security_for_instances.pot (End User Guide 1.0.0) #-#-#-#-# +#: ../cli_launch_instances.rst:57 +#: ../cli_nova_configure_access_security_for_instances.rst:51 +msgid "" +"Instances that use the default security group cannot, by default, be " +"accessed from any IP address outside of the cloud. If you want those IP " +"addresses to access the instances, you must modify the rules for the default " +"security group." +msgstr "" + +# #-#-#-#-# cli_launch_instances.pot (End User Guide 1.0.0) #-#-#-#-# +# #-#-#-#-# cli_nova_configure_access_security_for_instances.pot (End User Guide 1.0.0) #-#-#-#-# +#: ../cli_launch_instances.rst:62 +#: ../cli_nova_configure_access_security_for_instances.rst:56 +msgid "" +"You can also assign a floating IP address to a running instance to make it " +"accessible from outside the cloud. See :doc:`cli_manage_ip_addresses`." +msgstr "" + +#: ../cli_launch_instances.rst:66 +msgid "" +"After you gather the parameters that you need to launch an instance, you can " +"launch it from an image_ or a :ref:`volume`. You can launch an instance " +"directly from one of the available OpenStack images or from an image that " +"you have copied to a persistent volume. The OpenStack Image service provides " +"a pool of images that are accessible to members of different projects." +msgstr "" + +#: ../cli_launch_instances.rst:74 +msgid "Gather parameters to launch an instance" +msgstr "" + +#: ../cli_launch_instances.rst:76 +msgid "Before you begin, source the OpenStack RC file." +msgstr "" + +# #-#-#-#-# cli_launch_instances.pot (End User Guide 1.0.0) #-#-#-#-# +# #-#-#-#-# cli_nova_launch_instance_from_volume.pot (End User Guide 1.0.0) #-#-#-#-# +#: ../cli_launch_instances.rst:78 +#: ../cli_nova_launch_instance_from_volume.rst:154 +msgid "List the available flavors::" +msgstr "" + +#: ../cli_launch_instances.rst:82 +msgid "Note the ID of the flavor that you want to use for your instance::" +msgstr "" + +# #-#-#-#-# cli_launch_instances.pot (End User Guide 1.0.0) #-#-#-#-# +# #-#-#-#-# cli_nova_launch_instance_from_volume.pot (End User Guide 1.0.0) #-#-#-#-# +#: ../cli_launch_instances.rst:94 +#: ../cli_nova_launch_instance_from_volume.rst:140 +msgid "List the available images::" +msgstr "" + +#: ../cli_launch_instances.rst:98 +msgid "Note the ID of the image from which you want to boot your instance::" +msgstr "" + +#: ../cli_launch_instances.rst:108 +msgid "" +"You can also filter the image list by using ``grep`` to find a specific " +"image, as follows::" +msgstr "" + +#: ../cli_launch_instances.rst:115 +msgid "List the available security groups::" +msgstr "" + +#: ../cli_launch_instances.rst:121 +msgid "" +"If you are an admin user, specify the ``--all-tenants`` parameter to list " +"groups for all tenants." +msgstr "" + +#: ../cli_launch_instances.rst:126 +msgid "" +"Note the ID of the security group that you want to use for your instance::" +msgstr "" + +#: ../cli_launch_instances.rst:136 +msgid "" +"If you have not created any security groups, you can assign the instance to " +"only the default security group." +msgstr "" + +#: ../cli_launch_instances.rst:139 +msgid "You can view rules for a specified security group::" +msgstr "" + +#: ../cli_launch_instances.rst:143 +msgid "" +"List the available key pairs, and note the key pair name that you use for " +"SSH access::" +msgstr "" + +#: ../cli_launch_instances.rst:151 +msgid "Launch an instance from an image" +msgstr "" + +#: ../cli_launch_instances.rst:153 +msgid "" +"After you gather required parameters, run the following command to launch an " +"instance. Specify the server name, flavor ID, and image ID::" +msgstr "" + +#: ../cli_launch_instances.rst:160 +msgid "" +"Optionally, you can provide a key name for access control and a security " +"group for security. You can also include metadata key and value pairs. For " +"example, you can add a description for your server by providing the ``--meta " +"description=\"My Server\"`` parameter." +msgstr "" + +#: ../cli_launch_instances.rst:165 +msgid "" +"You can pass user data in a local file at instance launch by using the ``--" +"user-data USER-DATA-FILE`` parameter." +msgstr "" + +#: ../cli_launch_instances.rst:169 +msgid "" +"If you boot an instance with an INSTANCE_NAME greater than 63 characters, " +"Compute truncates it automatically when turning it into a hostname to ensure " +"the correct work of dnsmasq. The corresponding warning is written into the " +"nova-network.log file." +msgstr "" + +#: ../cli_launch_instances.rst:174 +msgid "" +"The following command launches the ``MyCirrosServer`` instance with the ``m1." +"small`` flavor (ID of ``1``), ``cirros-0.3.2-x86_64-uec`` image (ID of " +"``397e713c-b95b-4186-ad46-6126863ea0a9``), ``default`` security group, " +"``KeyPair01`` key, and a user data file called ``cloudinit.file``::" +msgstr "" + +#: ../cli_launch_instances.rst:184 +msgid "" +"Depending on the parameters that you provide, the command returns a list of " +"server properties::" msgstr "" #: ../cli_launch_instances.rst:218 @@ -938,15 +1704,979 @@ msgid "" "yet online." msgstr "" -#: ../cli_ceilometer.rst:28 -msgid "" -"A type, which indicates whether values increase monotonically (cumulative), " -"are interpreted as a change from the previous value (delta), or are stand-" -"alone and relate only to the current duration (gauge)" +#: ../cli_launch_instances.rst:221 +msgid "A status of ``ACTIVE`` indicates that the instance is active." msgstr "" -#: ../cli_ceilometer.rst:26 -msgid "A unit of measurement" +#: ../cli_launch_instances.rst:223 +msgid "" +"Copy the server ID value from the ``id`` field in the output. Use the ID to " +"get server details or to delete your server." +msgstr "" + +#: ../cli_launch_instances.rst:226 +msgid "" +"Copy the administrative password value from the ``adminPass`` field. Use the " +"password to log in to your server." +msgstr "" + +#: ../cli_launch_instances.rst:231 +msgid "" +"You can also place arbitrary local files into the instance file system at " +"creation time by using the ``--file `` option. You can " +"store up to five files. For example, if you have a special authorized keys " +"file named ``special_authorized_keysfile`` that you want to put on the " +"instance rather than using the regular SSH key injection, you can use the " +"``--file`` option as shown in the following example." +msgstr "" + +#: ../cli_launch_instances.rst:244 +msgid "Check if the instance is online::" +msgstr "" + +#: ../cli_launch_instances.rst:248 +msgid "" +"The list shows the ID, name, status, and private (and if assigned, public) " +"IP addresses for all instances in the project to which you belong::" +msgstr "" + +#: ../cli_launch_instances.rst:259 +msgid "If the status for the instance is ACTIVE, the instance is online." +msgstr "" + +#: ../cli_launch_instances.rst:261 +msgid "" +"To view the available options for the :command:`nova list` command, run the " +"following command::" +msgstr "" + +#: ../cli_launch_instances.rst:268 +msgid "" +"If you did not provide a key pair, security groups, or rules, you can access " +"the instance only from inside the cloud through VNC. Even pinging the " +"instance is not possible." +msgstr "" + +#: ../cli_manage_bare_metal_nodes.rst:3 +msgid "Manage bare-metal nodes" +msgstr "" + +#: ../cli_manage_bare_metal_nodes.rst:5 +msgid "" +"The bare-metal driver for OpenStack Compute manages provisioning of physical " +"hardware by using common cloud APIs and tools such as Orchestration (Heat). " +"The use case for this driver is for single tenant clouds such as a high-" +"performance computing cluster, or for deploying OpenStack itself." +msgstr "" + +#: ../cli_manage_bare_metal_nodes.rst:11 +msgid "" +"If you use the bare-metal driver, you must create a network interface and " +"add it to a bare-metal node. Then, you can launch an instance from a bare-" +"metal image." +msgstr "" + +#: ../cli_manage_bare_metal_nodes.rst:15 +msgid "" +"You can list and delete bare-metal nodes. When you delete a node, any " +"associated network interfaces are removed. You can list and remove network " +"interfaces that are associated with a bare-metal node." +msgstr "" + +#: ../cli_manage_bare_metal_nodes.rst:20 +msgid "Commands" +msgstr "" + +#: ../cli_manage_bare_metal_nodes.rst:22 +msgid "The following commands can be used to manage bare-metal nodes." +msgstr "" + +#: ../cli_manage_bare_metal_nodes.rst:25 +msgid "Adds a network interface to a bare-metal node." +msgstr "" + +#: ../cli_manage_bare_metal_nodes.rst:25 +msgid "``baremetal-interface-add``" +msgstr "" + +#: ../cli_manage_bare_metal_nodes.rst:28 +msgid "Lists network interfaces associated with a bare-metal node." +msgstr "" + +#: ../cli_manage_bare_metal_nodes.rst:28 +msgid "``baremetal-interface-list``" +msgstr "" + +#: ../cli_manage_bare_metal_nodes.rst:31 +msgid "Removes a network interface from a bare-metal node." +msgstr "" + +#: ../cli_manage_bare_metal_nodes.rst:31 +msgid "``baremetal-interface-remove``" +msgstr "" + +#: ../cli_manage_bare_metal_nodes.rst:34 +msgid "Creates a bare-metal node." +msgstr "" + +#: ../cli_manage_bare_metal_nodes.rst:34 +msgid "``baremetal-node-create``" +msgstr "" + +#: ../cli_manage_bare_metal_nodes.rst:37 +msgid "Removes a bare-metal node and any associated interfaces." +msgstr "" + +#: ../cli_manage_bare_metal_nodes.rst:37 +msgid "``baremetal-node-delete``" +msgstr "" + +#: ../cli_manage_bare_metal_nodes.rst:40 +msgid "Lists available bare-metal nodes." +msgstr "" + +#: ../cli_manage_bare_metal_nodes.rst:40 +msgid "``baremetal-node-list``" +msgstr "" + +#: ../cli_manage_bare_metal_nodes.rst:43 +msgid "Shows information about a bare-metal node." +msgstr "" + +#: ../cli_manage_bare_metal_nodes.rst:43 +msgid "``baremetal-node-show``" +msgstr "" + +#: ../cli_manage_bare_metal_nodes.rst:46 +msgid "Create a bare-metal node" +msgstr "" + +#: ../cli_manage_bare_metal_nodes.rst:48 +msgid "" +"When you create a bare-metal node, your PM address, user name, and password " +"should match the information in your hardware's BIOS/IPMI configuration." +msgstr "" + +#: ../cli_manage_bare_metal_nodes.rst:57 +msgid "" +"The following example shows the command and results from creating a node " +"with the PM address ``1.2.3.4``, the PM user name ipmi, and password " +"``ipmi``." +msgstr "" + +#: ../cli_manage_bare_metal_nodes.rst:83 +msgid "Add a network interface to the node" +msgstr "" + +#: ../cli_manage_bare_metal_nodes.rst:85 +msgid "" +"For each NIC on the node, you must create an interface, specifying the " +"interface's MAC address." +msgstr "" + +#: ../cli_manage_bare_metal_nodes.rst:101 +msgid "Launch an instance from a bare-metal image" +msgstr "" + +#: ../cli_manage_bare_metal_nodes.rst:103 +msgid "" +"A bare-metal instance is an instance created directly on a physical machine, " +"without any virtualization layer running underneath it. Nova retains power " +"control via IPMI. In some situations, Nova may retain network control via " +"Neutron and OpenFlow." +msgstr "" + +#: ../cli_manage_bare_metal_nodes.rst:122 +msgid "" +"Set the ``--availability_zone`` parameter to specify which zone or node to " +"use to start the server. Separate the zone from the host name with a comma. " +"For example:" +msgstr "" + +#: ../cli_manage_bare_metal_nodes.rst:130 +msgid "" +"``host`` is optional for the ``--availability_zone`` parameter. You can " +"simply specify ``zone:,node``, still including the comma." +msgstr "" + +#: ../cli_manage_bare_metal_nodes.rst:134 +msgid "List bare-metal nodes and interfaces" +msgstr "" + +#: ../cli_manage_bare_metal_nodes.rst:136 +msgid "" +"Use the :command:`nova baremetal-node-list` command to view all bare-metal " +"nodes and interfaces. When a node is in use, its status includes the UUID of " +"the instance that runs on it:" +msgstr "" + +#: ../cli_manage_bare_metal_nodes.rst:150 +msgid "Show details for a bare-metal node" +msgstr "" + +#: ../cli_manage_bare_metal_nodes.rst:152 +msgid "" +"Use the :command:`nova baremetal-node-list` command to view the details for " +"a bare-metal node:" +msgstr "" + +#: ../cli_manage_instances_hosts.rst:3 +msgid "Manage instances and hosts" +msgstr "" + +#: ../cli_manage_instances_hosts.rst:5 +msgid "" +"Instances are virtual machines that run inside the cloud on physical compute " +"nodes. The Compute service manages instances. A host is the node on which a " +"group of instances resides." +msgstr "" + +#: ../cli_manage_instances_hosts.rst:9 +msgid "" +"This section describes how to perform the different tasks involved in " +"instance management, such as adding floating IP addresses, stopping and " +"starting instances, and terminating instances. This section also discusses " +"node management tasks." +msgstr "" + +#: ../cli_manage_ip_addresses.rst:3 +msgid "Manage IP addresses" +msgstr "" + +#: ../cli_manage_ip_addresses.rst:5 +msgid "" +"Each instance has a private, fixed IP address and can also have a public, or " +"floating IP address. Private IP addresses are used for communication between " +"instances, and public addresses are used for communication with networks " +"outside the cloud, including the Internet." +msgstr "" + +#: ../cli_manage_ip_addresses.rst:10 +msgid "" +"When you launch an instance, it is automatically assigned a private IP " +"address that stays the same until you explicitly terminate the instance. " +"Rebooting an instance has no effect on the private IP address." +msgstr "" + +#: ../cli_manage_ip_addresses.rst:14 +msgid "" +"A pool of floating IP addresses, configured by the cloud administrator, is " +"available in OpenStack Compute. The project quota defines the maximum number " +"of floating IP addresses that you can allocate to the project. After you " +"allocate a floating IP address to a project, you can:" +msgstr "" + +#: ../cli_manage_ip_addresses.rst:19 +msgid "" +"Associate the floating IP address with an instance of the project. Only one " +"floating IP address can be allocated to an instance at any given time." +msgstr "" + +#: ../cli_manage_ip_addresses.rst:22 +msgid "Disassociate a floating IP address from an instance in the project." +msgstr "" + +#: ../cli_manage_ip_addresses.rst:24 +msgid "" +"Delete a floating IP from the project which automatically deletes that IP's " +"associations." +msgstr "" + +#: ../cli_manage_ip_addresses.rst:27 +msgid "" +"Use the :command:`nova floating-ip-*` commands to manage floating IP " +"addresses." +msgstr "" + +#: ../cli_manage_ip_addresses.rst:30 +msgid "List floating IP address information" +msgstr "" + +#: ../cli_manage_ip_addresses.rst:32 +msgid "To list all pools that provide floating IP addresses, run::" +msgstr "" + +#: ../cli_manage_ip_addresses.rst:43 +msgid "" +"If this list is empty, the cloud administrator must configure a pool of " +"floating IP addresses." +msgstr "" + +#: ../cli_manage_ip_addresses.rst:46 +msgid "" +"To list all floating IP addresses that are allocated to the current project, " +"run::" +msgstr "" + +#: ../cli_manage_ip_addresses.rst:57 +msgid "" +"For each floating IP address that is allocated to the current project, the " +"command outputs the floating IP address, the ID for the instance to which " +"the floating IP address is assigned, the associated fixed IP address, and " +"the pool from which the floating IP address was allocated." +msgstr "" + +#: ../cli_manage_ip_addresses.rst:64 +msgid "Associate floating IP addresses" +msgstr "" + +#: ../cli_manage_ip_addresses.rst:66 +msgid "You can assign a floating IP address to a project and to an instance." +msgstr "" + +#: ../cli_manage_ip_addresses.rst:68 +msgid "" +"Run the following command to allocate a floating IP address to the current " +"project. By default, the floating IP address is allocated from the public " +"pool. The command outputs the allocated IP address::" +msgstr "" + +#: ../cli_manage_ip_addresses.rst:81 +msgid "" +"If more than one IP address pool is available, you can specify from which " +"pool to allocate the IP address, using the pool's name. For example, to " +"allocate a floating IP address from the ``test`` pool, run::" +msgstr "" + +#: ../cli_manage_ip_addresses.rst:87 +msgid "" +"List all project instances with which a floating IP address could be " +"associated::" +msgstr "" + +#: ../cli_manage_ip_addresses.rst:98 +msgid "Associate an IP address with an instance in the project, as follows::" +msgstr "" + +# #-#-#-#-# cli_manage_ip_addresses.pot (End User Guide 1.0.0) #-#-#-#-# +# #-#-#-#-# cli_nova_launch_instance_from_volume.pot (End User Guide 1.0.0) #-#-#-#-# +#: ../cli_manage_ip_addresses.rst:102 +#: ../cli_nova_launch_instance_from_volume.rst:172 +msgid "For example::" +msgstr "" + +#: ../cli_manage_ip_addresses.rst:106 +msgid "The instance is now associated with two IP addresses::" +msgstr "" + +#: ../cli_manage_ip_addresses.rst:116 +msgid "" +"After you associate the IP address and configure security group rules for " +"the instance, the instance is publicly available at the floating IP address." +msgstr "" + +#: ../cli_manage_ip_addresses.rst:122 +msgid "" +"If an instance is connected to multiple networks, you can associate a " +"floating IP address with a specific fixed IP address using the optional ``--" +"fixed-address`` parameter:" +msgstr "" + +#: ../cli_manage_ip_addresses.rst:132 +msgid "Disassociate floating IP addresses" +msgstr "" + +#: ../cli_manage_ip_addresses.rst:134 +msgid "To disassociate a floating IP address from an instance::" +msgstr "" + +#: ../cli_manage_ip_addresses.rst:138 +msgid "To remove the floating IP address from a project::" +msgstr "" + +#: ../cli_manage_ip_addresses.rst:142 +msgid "" +"The IP address is returned to the pool of IP addresses that is available for " +"all projects. If the IP address is still associated with a running instance, " +"it is automatically disassociated from that instance." +msgstr "" + +# #-#-#-#-# cli_nova_configure_access_security_for_instances.pot (End User Guide 1.0.0) #-#-#-#-# +# #-#-#-#-# configure_access_and_security_for_instances.pot (End User Guide 1.0.0) #-#-#-#-# +# #-#-#-#-# sdk_configure_access_security_instances.pot (End User Guide 1.0.0) #-#-#-#-# +#: ../cli_nova_configure_access_security_for_instances.rst:3 +#: ../configure_access_and_security_for_instances.rst:3 +#: ../sdk_configure_access_security_instances.rst:6 +msgid "Configure access and security for instances" +msgstr "" + +#: ../cli_nova_configure_access_security_for_instances.rst:5 +msgid "" +"When you launch a virtual machine, you can inject a *key pair*, which " +"provides SSH access to your instance. For this to work, the image must " +"contain the ``cloud-init`` package." +msgstr "" + +#: ../cli_nova_configure_access_security_for_instances.rst:9 +msgid "" +"You can create at least one key pair for each project. You can use the key " +"pair for multiple instances that belong to that project. If you generate a " +"key pair with an external tool, you can import it into OpenStack." +msgstr "" + +#: ../cli_nova_configure_access_security_for_instances.rst:13 +msgid "" +"If an image uses a static root password or a static key set (neither is " +"recommended), you must not provide a key pair when you launch the instance." +msgstr "" + +#: ../cli_nova_configure_access_security_for_instances.rst:17 +msgid "" +"A *security group* is a named collection of network access rules that are " +"use to limit the types of traffic that have access to instances. When you " +"launch an instance, you can assign one or more security groups to it. If you " +"do not create security groups, new instances are automatically assigned to " +"the default security group, unless you explicitly specify a different " +"security group." +msgstr "" + +#: ../cli_nova_configure_access_security_for_instances.rst:24 +msgid "" +"The associated *rules* in each security group control the traffic to " +"instances in the group. Any incoming traffic that is not matched by a rule " +"is denied access by default. You can add rules to or remove rules from a " +"security group, and you can modify rules for the default and any other " +"security group." +msgstr "" + +#: ../cli_nova_configure_access_security_for_instances.rst:30 +msgid "" +"You can modify the rules in a security group to allow access to instances " +"through different ports and protocols. For example, you can modify rules to " +"allow access to instances through SSH, to ping instances, or to allow UDP " +"traffic; for example, for a DNS server running on an instance. You specify " +"the following parameters for rules:" +msgstr "" + +#: ../cli_nova_configure_access_security_for_instances.rst:36 +msgid "" +"**Source of traffic**. Enable traffic to instances from either IP addresses " +"inside the cloud from other group members or from all IP addresses." +msgstr "" + +#: ../cli_nova_configure_access_security_for_instances.rst:40 +msgid "**Protocol**. Choose TCP for SSH, ICMP for pings, or UDP." +msgstr "" + +#: ../cli_nova_configure_access_security_for_instances.rst:42 +msgid "" +"**Destination port on virtual machine**. Define a port range. To open a " +"single port only, enter the same value twice. ICMP does not support ports; " +"instead, you enter values to define the codes and types of ICMP traffic to " +"be allowed." +msgstr "" + +#: ../cli_nova_configure_access_security_for_instances.rst:47 +msgid "Rules are automatically enforced as soon as you create or modify them." +msgstr "" + +# #-#-#-#-# cli_nova_configure_access_security_for_instances.pot (End User Guide 1.0.0) #-#-#-#-# +# #-#-#-#-# configure_access_and_security_for_instances.pot (End User Guide 1.0.0) #-#-#-#-# +#: ../cli_nova_configure_access_security_for_instances.rst:61 +#: ../configure_access_and_security_for_instances.rst:90 +msgid "Add a key pair" +msgstr "" + +#: ../cli_nova_configure_access_security_for_instances.rst:63 +msgid "You can generate a key pair or upload an existing public key." +msgstr "" + +#: ../cli_nova_configure_access_security_for_instances.rst:65 +msgid "To generate a key pair, run the following command::" +msgstr "" + +#: ../cli_nova_configure_access_security_for_instances.rst:69 +msgid "" +"This command generates a key pair with the name that you specify for KEY" +"\\_NAME, writes the private key to the :file:`.pem` file that you specify, " +"and registers the public key to the Nova database." +msgstr "" + +#: ../cli_nova_configure_access_security_for_instances.rst:73 +msgid "" +"To set the permissions of the :file:`.pem` file so that only you can read " +"and write to it, run the following command::" +msgstr "" + +# #-#-#-#-# cli_nova_configure_access_security_for_instances.pot (End User Guide 1.0.0) #-#-#-#-# +# #-#-#-#-# configure_access_and_security_for_instances.pot (End User Guide 1.0.0) #-#-#-#-# +#: ../cli_nova_configure_access_security_for_instances.rst:79 +#: ../configure_access_and_security_for_instances.rst:116 +msgid "Import a key pair" +msgstr "" + +#: ../cli_nova_configure_access_security_for_instances.rst:81 +msgid "" +"If you have already generated a key pair and the public key is located at " +"``~/.ssh/id_rsa.pub``, run the following command to upload the public key::" +msgstr "" + +#: ../cli_nova_configure_access_security_for_instances.rst:87 +msgid "" +"This command registers the public key at the Nova database and names the key " +"pair the name that you specify for ``KEY_NAME``." +msgstr "" + +#: ../cli_nova_configure_access_security_for_instances.rst:90 +msgid "" +"To ensure that the key pair has been successfully imported, list key pairs " +"as follows::" +msgstr "" + +# #-#-#-#-# cli_nova_configure_access_security_for_instances.pot (End User Guide 1.0.0) #-#-#-#-# +# #-#-#-#-# sdk_configure_access_security_instances.pot (End User Guide 1.0.0) #-#-#-#-# +#: ../cli_nova_configure_access_security_for_instances.rst:96 +#: ../sdk_configure_access_security_instances.rst:105 +msgid "Create and manage security groups" +msgstr "" + +#: ../cli_nova_configure_access_security_for_instances.rst:98 +msgid "" +"To list the security groups for the current project, including descriptions, " +"enter the following command::" +msgstr "" + +#: ../cli_nova_configure_access_security_for_instances.rst:103 +msgid "" +"To create a security group with a specified name and description, enter the " +"following command::" +msgstr "" + +#: ../cli_nova_configure_access_security_for_instances.rst:108 +msgid "To delete a specified group, enter the following command::" +msgstr "" + +#: ../cli_nova_configure_access_security_for_instances.rst:114 +msgid "" +"You cannot delete the default security group for a project. Also, you cannot " +"delete a security group that is assigned to a running instance." +msgstr "" + +# #-#-#-#-# cli_nova_configure_access_security_for_instances.pot (End User Guide 1.0.0) #-#-#-#-# +# #-#-#-#-# sdk_configure_access_security_instances.pot (End User Guide 1.0.0) #-#-#-#-# +#: ../cli_nova_configure_access_security_for_instances.rst:119 +#: ../sdk_configure_access_security_instances.rst:155 +msgid "Create and manage security group rules" +msgstr "" + +#: ../cli_nova_configure_access_security_for_instances.rst:121 +msgid "" +"Modify security group rules with the :command:`nova secgroup-*-rule` " +"commands. Before you begin, source the OpenStack RC file. For details, see :" +"doc:`../common/cli_set_environment_variables_using_openstack_rc`." +msgstr "" + +#: ../cli_nova_configure_access_security_for_instances.rst:125 +msgid "To list the rules for a security group, run the following command::" +msgstr "" + +#: ../cli_nova_configure_access_security_for_instances.rst:129 +msgid "" +"To allow SSH access to the instances, choose one of the following options:" +msgstr "" + +#: ../cli_nova_configure_access_security_for_instances.rst:132 +msgid "" +"Allow access from all IP addresses, specified as IP subnet ``0.0.0.0/0`` in " +"CIDR notation::" +msgstr "" + +#: ../cli_nova_configure_access_security_for_instances.rst:137 +msgid "" +"Allow access only from IP addresses from other security groups (source " +"groups) to access the specified port::" +msgstr "" + +#: ../cli_nova_configure_access_security_for_instances.rst:143 +msgid "To allow pinging of the instances, choose one of the following options:" +msgstr "" + +#: ../cli_nova_configure_access_security_for_instances.rst:145 +msgid "" +"Allow pinging from all IP addresses, specified as IP subnet ``0.0.0.0/0`` in " +"CIDR notation::" +msgstr "" + +#: ../cli_nova_configure_access_security_for_instances.rst:150 +msgid "This allows access to all codes and all types of ICMP traffic." +msgstr "" + +#: ../cli_nova_configure_access_security_for_instances.rst:152 +msgid "" +"Allow only members of other security groups (source groups) to ping " +"instances::" +msgstr "" + +#: ../cli_nova_configure_access_security_for_instances.rst:158 +msgid "" +"To allow access through a UDP port, such as allowing access to a DNS server " +"that runs on a VM, choose one of the following options:" +msgstr "" + +#: ../cli_nova_configure_access_security_for_instances.rst:161 +msgid "" +"Allow UDP access from IP addresses, specified as IP subnet ``0.0.0.0/0`` in " +"CIDR notation::" +msgstr "" + +#: ../cli_nova_configure_access_security_for_instances.rst:166 +msgid "" +"Allow only IP addresses from other security groups (source groups) to access " +"the specified port::" +msgstr "" + +#: ../cli_nova_configure_access_security_for_instances.rst:173 +msgid "Delete a security group rule" +msgstr "" + +#: ../cli_nova_configure_access_security_for_instances.rst:175 +msgid "" +"To delete a security group rule, specify the same arguments that you used to " +"create the rule." +msgstr "" + +#: ../cli_nova_configure_access_security_for_instances.rst:178 +msgid "" +"For example, to delete the security group rule that permits SSH access from " +"all IP addresses, run the following command::" +msgstr "" + +#: ../cli_nova_launch_instance_from_volume.rst:3 +msgid "Launch an instance from a volume" +msgstr "" + +#: ../cli_nova_launch_instance_from_volume.rst:5 +msgid "You can boot instances from a volume instead of an image." +msgstr "" + +#: ../cli_nova_launch_instance_from_volume.rst:7 +msgid "" +"To complete these tasks, use these parameters on the :command:`nova boot` " +"command:" +msgstr "" + +#: ../cli_nova_launch_instance_from_volume.rst:14 +msgid "Task" +msgstr "" + +#: ../cli_nova_launch_instance_from_volume.rst:15 +msgid "nova boot parameter" +msgstr "" + +#: ../cli_nova_launch_instance_from_volume.rst:16 +msgid "Information" +msgstr "" + +#: ../cli_nova_launch_instance_from_volume.rst:17 +msgid "Boot an instance from an image and attach a non-bootable volume." +msgstr "" + +#: ../cli_nova_launch_instance_from_volume.rst:19 +#: ../cli_nova_launch_instance_from_volume.rst:26 +#: ../cli_nova_launch_instance_from_volume.rst:29 +msgid "``--block-device``" +msgstr "" + +#: ../cli_nova_launch_instance_from_volume.rst:20 +msgid ":ref:`Boot_instance_from_image_and_attach_non-bootable_volume`" +msgstr "" + +#: ../cli_nova_launch_instance_from_volume.rst:21 +#: ../cli_nova_launch_instance_from_volume.rst:31 +msgid "Attach a swap disk to an instance." +msgstr "" + +#: ../cli_nova_launch_instance_from_volume.rst:22 +#: ../cli_nova_launch_instance_from_volume.rst:32 +msgid "``--swap``" +msgstr "" + +#: ../cli_nova_launch_instance_from_volume.rst:23 +#: ../cli_nova_launch_instance_from_volume.rst:33 +#: ../cli_nova_launch_instance_from_volume.rst:36 +msgid ":ref:`Attach_swap_or_ephemeral_disk_to_an_instance`" +msgstr "" + +#: ../cli_nova_launch_instance_from_volume.rst:24 +msgid "Create a volume from an image and boot an instance from that volume." +msgstr "" + +#: ../cli_nova_launch_instance_from_volume.rst:27 +#: ../cli_nova_launch_instance_from_volume.rst:30 +msgid ":ref:`Create_volume_from_image_and_boot_instance`" +msgstr "" + +#: ../cli_nova_launch_instance_from_volume.rst:28 +msgid "Boot from an existing source image, volume, or snapshot." +msgstr "" + +#: ../cli_nova_launch_instance_from_volume.rst:34 +msgid "Attach an ephemeral disk to an instance." +msgstr "" + +#: ../cli_nova_launch_instance_from_volume.rst:35 +msgid "``--ephemeral``" +msgstr "" + +#: ../cli_nova_launch_instance_from_volume.rst:40 +msgid "" +"To attach a volume to a running instance, see :ref:" +"`Attach_a_volume_to_an_instance`." +msgstr "" + +#: ../cli_nova_launch_instance_from_volume.rst:46 +msgid "Boot instance from image and attach non-bootable volume" +msgstr "" + +#: ../cli_nova_launch_instance_from_volume.rst:48 +msgid "" +"Create a non-bootable volume and attach that volume to an instance that you " +"boot from an image." +msgstr "" + +#: ../cli_nova_launch_instance_from_volume.rst:51 +msgid "" +"To create a non-bootable volume, do not create it from an image. The volume " +"must be entirely empty with no partition table and no file system." +msgstr "" + +#: ../cli_nova_launch_instance_from_volume.rst:55 +msgid "Create a non-bootable volume::" +msgstr "" + +#: ../cli_nova_launch_instance_from_volume.rst:82 +msgid "List volumes::" +msgstr "" + +#: ../cli_nova_launch_instance_from_volume.rst:91 +msgid "" +"Boot an instance from an image and attach the empty volume to the instance::" +msgstr "" + +#: ../cli_nova_launch_instance_from_volume.rst:134 +msgid "Create volume from image and boot instance" +msgstr "" + +#: ../cli_nova_launch_instance_from_volume.rst:136 +msgid "" +"You can create a volume from an existing image, volume, or snapshot. This " +"procedure shows you how to create a volume from an image, and use the volume " +"to boot an instance." +msgstr "" + +#: ../cli_nova_launch_instance_from_volume.rst:152 +msgid "Note the ID of the image that you want to use to create a volume." +msgstr "" + +#: ../cli_nova_launch_instance_from_volume.rst:167 +msgid "Note the ID of the flavor that you want to use to create a volume." +msgstr "" + +#: ../cli_nova_launch_instance_from_volume.rst:169 +msgid "" +"To create a bootable volume from an image and launch an instance from this " +"volume, use the ``--block-device`` parameter." +msgstr "" + +#: ../cli_nova_launch_instance_from_volume.rst:178 +msgid "The parameters are:" +msgstr "" + +#: ../cli_nova_launch_instance_from_volume.rst:180 +msgid "``--flavor`` FLAVOR. The flavor ID or name." +msgstr "" + +#: ../cli_nova_launch_instance_from_volume.rst:182 +msgid "" +"``--block-device`` source=SOURCE,id=ID,dest=DEST,size=SIZE,shutdown=PRESERVE," +"bootindex=INDEX" +msgstr "" + +#: ../cli_nova_launch_instance_from_volume.rst:186 +msgid "" +"The type of object used to create the block device. Valid values are " +"``volume``, ``snapshot``, ``image``, and ``blank``." +msgstr "" + +#: ../cli_nova_launch_instance_from_volume.rst:187 +msgid "**source=SOURCE**" +msgstr "" + +#: ../cli_nova_launch_instance_from_volume.rst:190 +msgid "**id=ID**" +msgstr "" + +#: ../cli_nova_launch_instance_from_volume.rst:190 +msgid "The ID of the source object." +msgstr "" + +#: ../cli_nova_launch_instance_from_volume.rst:193 +msgid "" +"The type of the target virtual device. Valid values are ``volume`` and " +"``local``." +msgstr "" + +#: ../cli_nova_launch_instance_from_volume.rst:194 +msgid "**dest=DEST**" +msgstr "" + +#: ../cli_nova_launch_instance_from_volume.rst:197 +msgid "**size=SIZE**" +msgstr "" + +#: ../cli_nova_launch_instance_from_volume.rst:197 +msgid "The size of the volume that is created." +msgstr "" + +#: ../cli_nova_launch_instance_from_volume.rst:200 +msgid "" +"What to do with the volume when the instance is deleted. ``preserve`` does " +"not delete the volume. ``remove`` deletes the volume." +msgstr "" + +#: ../cli_nova_launch_instance_from_volume.rst:202 +msgid "**shutdown={preserve\\|remove}**" +msgstr "" + +#: ../cli_nova_launch_instance_from_volume.rst:205 +msgid "**bootindex=INDEX**" +msgstr "" + +#: ../cli_nova_launch_instance_from_volume.rst:205 +msgid "Orders the boot disks. Use ``0`` to boot from this volume." +msgstr "" + +#: ../cli_nova_launch_instance_from_volume.rst:207 +msgid "``NAME``. The name for the server." +msgstr "" + +#: ../cli_nova_launch_instance_from_volume.rst:209 +msgid "" +"Create a bootable volume from an image, before the instance boots. The " +"volume is not deleted when the instance is terminated::" +msgstr "" + +#: ../cli_nova_launch_instance_from_volume.rst:250 +msgid "" +"List volumes to see the bootable volume and its attached " +"``myInstanceFromVolume`` instance::" +msgstr "" + +#: ../cli_nova_launch_instance_from_volume.rst:263 +msgid "Attach swap or ephemeral disk to an instance" +msgstr "" + +#: ../cli_nova_launch_instance_from_volume.rst:265 +msgid "" +"Use the nova ``boot`` ``--swap`` parameter to attach a swap disk on boot or " +"the nova ``boot`` ``--ephemeral`` parameter to attach an ephemeral disk on " +"boot. When you terminate the instance, both disks are deleted." +msgstr "" + +#: ../cli_nova_launch_instance_from_volume.rst:269 +msgid "Boot an instance with a 512 MB swap disk and 2 GB ephemeral disk::" +msgstr "" + +#: ../cli_nova_launch_instance_from_volume.rst:275 +msgid "" +"The flavor defines the maximum swap and ephemeral disk size. You cannot " +"exceed these maximum values." +msgstr "" + +#: ../cli_nova_launch_instance_using_ISO_image.rst:3 +msgid "Launch an instance using ISO image" +msgstr "" + +#: ../cli_nova_launch_instance_using_ISO_image.rst:8 +msgid "Boot an instance from an ISO image" +msgstr "" + +#: ../cli_nova_launch_instance_using_ISO_image.rst:10 +msgid "" +"OpenStack supports booting instances using ISO images. But before you make " +"such instances functional, use the :command:`nova boot` command with the " +"following parameters to boot an instance::" +msgstr "" + +#: ../cli_nova_launch_instance_using_ISO_image.rst:53 +msgid "" +"In this command, ``ubuntu-14.04.2-server-amd64.iso`` is the ISO image, and " +"``INSTANCE_NAME`` is the name of the new instance. ``NETWORK_UUID`` is a " +"valid network id in your system." +msgstr "" + +#: ../cli_nova_launch_instance_using_ISO_image.rst:59 +msgid "" +"You need the Block Storage service, and the parameter ``shutdown=preserve`` " +"is also mandatory, thus the volume will be preserved after the shutdown of " +"the instance." +msgstr "" + +#: ../cli_nova_launch_instance_using_ISO_image.rst:63 +msgid "" +"After the instance is successfully launched, connect to the instance using a " +"remote console and follow the instructions to install the system as using " +"ISO images on regular computers. When the installation is finished and " +"system is rebooted, the instance asks you again to install the operating " +"system, which means your instance is not usable. If you have problems with " +"image creation, please check the `Virtual Machine Image Guide `_ for " +"reference." +msgstr "" + +#: ../cli_nova_launch_instance_using_ISO_image.rst:75 +msgid "Make the instances booted from ISO image functional" +msgstr "" + +#: ../cli_nova_launch_instance_using_ISO_image.rst:77 +msgid "" +"Now complete the following steps to make your instances created using ISO " +"image actually functional." +msgstr "" + +#: ../cli_nova_launch_instance_using_ISO_image.rst:80 +msgid "Delete the instance using the following command::" +msgstr "" + +#: ../cli_nova_launch_instance_using_ISO_image.rst:84 +msgid "" +"After you delete the instance, the system you have just installed using your " +"ISO image remains, because the parameter ``shutdown=preserve`` was set, so " +"run the following command::" +msgstr "" + +#: ../cli_nova_launch_instance_using_ISO_image.rst:95 +msgid "" +"You get a list with all the volumes in your system. In this list, you can " +"find the volume that is attached to your ISO created instance, with the " +"false bootable property." +msgstr "" + +#: ../cli_nova_launch_instance_using_ISO_image.rst:99 +msgid "Upload the volume to glance::" +msgstr "" + +#: ../cli_nova_launch_instance_using_ISO_image.rst:109 +msgid "" +"The ``VOLUME_UUID`` is the uuid of the volume that is attached to your ISO " +"created instance, and the ``IMAGE_NAME`` is the name that you give to your " +"new image." +msgstr "" + +#: ../cli_nova_launch_instance_using_ISO_image.rst:113 +msgid "" +"After the image is successfully uploaded, you can use the new image to boot " +"instances." +msgstr "" + +#: ../cli_nova_launch_instance_using_ISO_image.rst:116 +msgid "" +"The instances launched using this image contain the system that you have " +"just installed using the ISO image." +msgstr "" + +#: ../cli_provide_user_data_to_instances.rst:3 +msgid "Provide user data to instances" msgstr "" #: ../cli_provide_user_data_to_instances.rst:5 @@ -959,6 +2689,3480 @@ msgid "" "handles early initialization of a cloud instance." msgstr "" +#: ../cli_provide_user_data_to_instances.rst:13 +msgid "" +"You can place user data in a local file and pass it through the ``--user-" +"data `` parameter at instance creation::" +msgstr "" + +#: ../cli_reboot_an_instance.rst:3 +msgid "Reboot an instance" +msgstr "" + +#: ../cli_reboot_an_instance.rst:5 +msgid "" +"You can soft or hard reboot a running instance. A soft reboot attempts a " +"graceful shut down and restart of the instance. A hard reboot power cycles " +"the instance." +msgstr "" + +#: ../cli_reboot_an_instance.rst:9 +msgid "By default, when you reboot an instance, it is a soft reboot." +msgstr "" + +#: ../cli_reboot_an_instance.rst:15 +msgid "To perform a hard reboot, pass the ``--hard`` parameter, as follows::" +msgstr "" + +#: ../cli_reboot_an_instance.rst:19 +msgid "" +"It is also possible to reboot a running instance into rescue mode. For " +"example, this operation may be required, if a filesystem of an instance " +"becomes corrupted with prolonged use." +msgstr "" + +#: ../cli_reboot_an_instance.rst:25 +msgid "" +"Pause, suspend, and stop operations are not allowed when an instance is " +"running in rescue mode, as triggering these actions causes the loss of the " +"original instance state, and makes it impossible to unrescue the instance." +msgstr "" + +#: ../cli_reboot_an_instance.rst:30 +msgid "" +"Rescue mode provides a mechanism for access, even if an image renders the " +"instance inaccessible. By default, it starts an instance from the initial " +"image attaching the current boot disk as a secondary one." +msgstr "" + +#: ../cli_reboot_an_instance.rst:34 +msgid "" +"To perform an instance reboot into rescue mode, run the following command::" +msgstr "" + +#: ../cli_reboot_an_instance.rst:41 +msgid "" +"On running the :command:`nova rescue` command, an instance performs a soft " +"shutdown first. This means that the guest operating system has a chance to " +"perform a controlled shutdown before the instance is powered off. The " +"shutdown behavior is configured by the ``shutdown_timeout`` parameter that " +"can be set in the :file:`nova.conf` file. Its value stands for the overall " +"period (in seconds) a guest operation system is allowed to complete the " +"shutdown. The default timeout is 60 seconds. See `Description of Compute " +"configuration options `_ for details." +msgstr "" + +#: ../cli_reboot_an_instance.rst:59 +msgid "" +"To restart the instance from the normal boot disk, run the following " +"command::" +msgstr "" + +#: ../cli_reboot_an_instance.rst:64 +msgid "" +"If you want to rescue an instance with a specific image, rather than the " +"default one, use the ``--rescue_image_ref`` parameter::" +msgstr "" + +#: ../cli_search_instance_with_ip_address.rst:3 +msgid "Search for an instance using IP address" +msgstr "" + +#: ../cli_search_instance_with_ip_address.rst:5 +msgid "" +"You can search for an instance using the IP address parameter, ``--ip``, " +"with the :command:`nova list` command." +msgstr "" + +#: ../cli_search_instance_with_ip_address.rst:12 +msgid "The following example shows the results of a search on ``10.0.0.4``." +msgstr "" + +#: ../cli_stop_and_start_an_instance.rst:3 +msgid "Stop and start an instance" +msgstr "" + +#: ../cli_stop_and_start_an_instance.rst:5 +msgid "Use one of the following methods to stop and start an instance." +msgstr "" + +#: ../cli_stop_and_start_an_instance.rst:8 +msgid "Pause and unpause an instance" +msgstr "" + +#: ../cli_stop_and_start_an_instance.rst:10 +msgid "To pause an instance, run the following command::" +msgstr "" + +#: ../cli_stop_and_start_an_instance.rst:14 +msgid "" +"This command stores the state of the VM in RAM. A paused instance continues " +"to run in a frozen state." +msgstr "" + +#: ../cli_stop_and_start_an_instance.rst:17 +msgid "To unpause an instance, run the following command::" +msgstr "" + +#: ../cli_stop_and_start_an_instance.rst:22 +msgid "Suspend and resume an instance" +msgstr "" + +#: ../cli_stop_and_start_an_instance.rst:24 +msgid "" +"To initiate a hypervisor-level suspend operation, run the following command::" +msgstr "" + +#: ../cli_stop_and_start_an_instance.rst:29 +msgid "To resume a suspended instance, run the following command::" +msgstr "" + +#: ../cli_stop_and_start_an_instance.rst:34 +msgid "Shelve and unshelve an instance" +msgstr "" + +#: ../cli_stop_and_start_an_instance.rst:36 +msgid "" +"Shelving is useful if you have an instance that you are not using, but would " +"like retain in your list of servers. For example, you can stop an instance " +"at the end of a work week, and resume work again at the start of the next " +"week. All associated data and resources are kept; however, anything still in " +"memory is not retained. If a shelved instance is no longer needed, it can " +"also be entirely removed." +msgstr "" + +#: ../cli_stop_and_start_an_instance.rst:43 +msgid "You can run the following shelving tasks:" +msgstr "" + +#: ../cli_stop_and_start_an_instance.rst:45 +msgid "" +"Shelve an instance - Shuts down the instance, and stores it together with " +"associated data and resources (a snapshot is taken if not volume backed). " +"Anything in memory is lost." +msgstr "" + +#: ../cli_stop_and_start_an_instance.rst:55 +msgid "" +"By default, the :command:`nova shelve` command gives the guest operating " +"system a chance to perform a controlled shutdown before the instance is " +"powered off. The shutdown behavior is configured by the ``shutdown_timeout`` " +"parameter that can be set in the :file:`nova.conf` file. Its value stands " +"for the overall period (in seconds) a guest operation system is allowed to " +"complete the shutdown. The default timeout is 60 seconds. See `Description " +"of Compute configuration options `_ for details." +msgstr "" + +#: ../cli_stop_and_start_an_instance.rst:71 +msgid "Unshelve an instance - Restores the instance." +msgstr "" + +#: ../cli_stop_and_start_an_instance.rst:77 +msgid "" +"Remove a shelved instance - Removes the instance from the server; data and " +"resource associations are deleted. If an instance is no longer needed, you " +"can move the instance off the hypervisor in order to minimize resource usage." +msgstr "" + +#: ../cli_swift_archive_auto_extract.rst:5 +msgid "Auto-extract archive files" +msgstr "" + +# #-#-#-#-# cli_swift_archive_auto_extract.pot (End User Guide 1.0.0) #-#-#-#-# +# #-#-#-#-# cli_swift_bulk_delete.pot (End User Guide 1.0.0) #-#-#-#-# +# #-#-#-#-# cli_swift_large_object_creation.pot (End User Guide 1.0.0) #-#-#-#-# +# #-#-#-#-# cli_swift_static_website.pot (End User Guide 1.0.0) #-#-#-#-# +#: ../cli_swift_archive_auto_extract.rst:7 ../cli_swift_bulk_delete.rst:7 +#: ../cli_swift_large_object_creation.rst:7 ../cli_swift_static_website.rst:7 +msgid "" +"To discover whether your Object Storage system supports this feature, see :" +"ref:`discoverability`. Alternatively, check with your service provider." +msgstr "" + +#: ../cli_swift_archive_auto_extract.rst:11 +msgid "Use the auto-extract archive feature to upload a tar archive file." +msgstr "" + +#: ../cli_swift_archive_auto_extract.rst:13 +msgid "" +"The Object Storage system extracts files from the archive file and creates " +"an object." +msgstr "" + +#: ../cli_swift_archive_auto_extract.rst:17 +msgid "Auto-extract archive request" +msgstr "" + +#: ../cli_swift_archive_auto_extract.rst:19 +msgid "" +"To upload an archive file, make a ``PUT`` request. Add the ``extract-" +"archive=format`` query parameter to indicate that you are uploading a tar " +"archive file instead of normal content." +msgstr "" + +#: ../cli_swift_archive_auto_extract.rst:23 +msgid "" +"Valid values for the ``format`` variable are ``tar``, ``tar.gz``, or ``tar." +"bz2``." +msgstr "" + +#: ../cli_swift_archive_auto_extract.rst:26 +msgid "" +"The path you specify in the ``PUT`` request is used for the location of the " +"object and the prefix for the resulting object names." +msgstr "" + +#: ../cli_swift_archive_auto_extract.rst:29 +msgid "In the ``PUT`` request, you can specify the path for:" +msgstr "" + +#: ../cli_swift_archive_auto_extract.rst:31 +msgid "An account" +msgstr "" + +#: ../cli_swift_archive_auto_extract.rst:33 +msgid "Optionally, a specific container" +msgstr "" + +#: ../cli_swift_archive_auto_extract.rst:35 +msgid "Optionally, a specific object prefix" +msgstr "" + +#: ../cli_swift_archive_auto_extract.rst:37 +msgid "" +"For example, if the first object in the tar archive is ``/home/file1.txt`` " +"and you specify the ``/v1/12345678912345/mybackup/castor/`` path, the " +"operation creates the ``castor/home/file1.txt`` object in the ``mybackup`` " +"container in the ``12345678912345`` account." +msgstr "" + +#: ../cli_swift_archive_auto_extract.rst:44 +msgid "Create an archive for auto-extract" +msgstr "" + +#: ../cli_swift_archive_auto_extract.rst:46 +msgid "You must use the tar utility to create the tar archive file." +msgstr "" + +#: ../cli_swift_archive_auto_extract.rst:48 +msgid "" +"You can upload regular files but you cannot upload other items (for example, " +"empty directories or symbolic links)." +msgstr "" + +#: ../cli_swift_archive_auto_extract.rst:51 +msgid "You must UTF-8-encode the member names." +msgstr "" + +#: ../cli_swift_archive_auto_extract.rst:53 +msgid "The archive auto-extract feature supports these formats:" +msgstr "" + +#: ../cli_swift_archive_auto_extract.rst:55 +msgid "The POSIX.1-1988 Ustar format." +msgstr "" + +#: ../cli_swift_archive_auto_extract.rst:57 +msgid "" +"The GNU tar format. Includes the long name, long link, and sparse extensions." +msgstr "" + +#: ../cli_swift_archive_auto_extract.rst:60 +msgid "The POSIX.1-2001 pax format." +msgstr "" + +#: ../cli_swift_archive_auto_extract.rst:62 +msgid "Use gzip or bzip2 to compress the archive." +msgstr "" + +#: ../cli_swift_archive_auto_extract.rst:64 +msgid "" +"Use the ``extract-archive`` query parameter to specify the format. Valid " +"values for this parameter are ``tar``, ``tar.gz``, or ``tar.bz2``." +msgstr "" + +#: ../cli_swift_archive_auto_extract.rst:69 +msgid "Auto-extract archive response" +msgstr "" + +#: ../cli_swift_archive_auto_extract.rst:71 +msgid "" +"When Object Storage processes the request, it performs multiple sub-" +"operations. Even if all sub-operations fail, the operation returns a 201 " +"``Created`` status. Some sub-operations might succeed while others fail. " +"Examine the response body to determine the results of each auto-extract " +"archive sub-operation." +msgstr "" + +#: ../cli_swift_archive_auto_extract.rst:77 +msgid "" +"You can set the ``Accept`` request header to one of these values to define " +"the response format:" +msgstr "" + +# #-#-#-#-# cli_swift_archive_auto_extract.pot (End User Guide 1.0.0) #-#-#-#-# +# #-#-#-#-# cli_swift_bulk_delete.pot (End User Guide 1.0.0) #-#-#-#-# +#: ../cli_swift_archive_auto_extract.rst:81 ../cli_swift_bulk_delete.rst:58 +msgid "" +"Formats response as plain text. If you omit the ``Accept`` header, ``text/" +"plain`` is the default." +msgstr "" + +# #-#-#-#-# cli_swift_archive_auto_extract.pot (End User Guide 1.0.0) #-#-#-#-# +# #-#-#-#-# cli_swift_bulk_delete.pot (End User Guide 1.0.0) #-#-#-#-# +#: ../cli_swift_archive_auto_extract.rst:82 ../cli_swift_bulk_delete.rst:59 +msgid "``text/plain``" +msgstr "" + +# #-#-#-#-# cli_swift_archive_auto_extract.pot (End User Guide 1.0.0) #-#-#-#-# +# #-#-#-#-# cli_swift_bulk_delete.pot (End User Guide 1.0.0) #-#-#-#-# +#: ../cli_swift_archive_auto_extract.rst:85 ../cli_swift_bulk_delete.rst:62 +msgid "Formats response as JSON." +msgstr "" + +# #-#-#-#-# cli_swift_archive_auto_extract.pot (End User Guide 1.0.0) #-#-#-#-# +# #-#-#-#-# cli_swift_bulk_delete.pot (End User Guide 1.0.0) #-#-#-#-# +#: ../cli_swift_archive_auto_extract.rst:85 ../cli_swift_bulk_delete.rst:62 +msgid "``application/json``" +msgstr "" + +# #-#-#-#-# cli_swift_archive_auto_extract.pot (End User Guide 1.0.0) #-#-#-#-# +# #-#-#-#-# cli_swift_bulk_delete.pot (End User Guide 1.0.0) #-#-#-#-# +#: ../cli_swift_archive_auto_extract.rst:88 +#: ../cli_swift_archive_auto_extract.rst:91 ../cli_swift_bulk_delete.rst:65 +msgid "Formats response as XML." +msgstr "" + +#: ../cli_swift_archive_auto_extract.rst:88 +msgid "``application/xml``" +msgstr "" + +#: ../cli_swift_archive_auto_extract.rst:91 +msgid "``text/xml``" +msgstr "" + +#: ../cli_swift_archive_auto_extract.rst:93 +msgid "" +"The following auto-extract archive files example shows a ``text/plain`` " +"response body where no failures occurred:" +msgstr "" + +#: ../cli_swift_archive_auto_extract.rst:101 +msgid "" +"The following auto-extract archive files example shows a ``text/plain`` " +"response where some failures occurred. In this example, the Object Storage " +"system is configured to reject certain character strings so that the 400 Bad " +"Request error occurs for any objects that use the restricted strings." +msgstr "" + +#: ../cli_swift_archive_auto_extract.rst:114 +msgid "" +"The following example shows the failure response in ``application/json`` " +"format." +msgstr "" + +#: ../cli_swift_bulk_delete.rst:5 +msgid "Bulk delete" +msgstr "" + +#: ../cli_swift_bulk_delete.rst:10 +msgid "" +"With bulk delete, you can delete up to 10,000 objects or containers " +"(configurable) in one request." +msgstr "" + +#: ../cli_swift_bulk_delete.rst:14 +msgid "Bulk delete request" +msgstr "" + +#: ../cli_swift_bulk_delete.rst:16 +msgid "" +"To perform a bulk delete operation, add the ``bulk-delete`` query parameter " +"to the path of a ``POST`` or ``DELETE`` operation." +msgstr "" + +#: ../cli_swift_bulk_delete.rst:21 +msgid "The ``DELETE`` operation is supported for backwards compatibility." +msgstr "" + +#: ../cli_swift_bulk_delete.rst:23 +msgid "" +"The path is the account, such as ``/v1/12345678912345``, that contains the " +"objects and containers." +msgstr "" + +#: ../cli_swift_bulk_delete.rst:26 +msgid "" +"In the request body of the ``POST`` or ``DELETE`` operation, list the " +"objects or containers to be deleted. Separate each name with a newline " +"character. You can include a maximum of 10,000 items (configurable) in the " +"list." +msgstr "" + +#: ../cli_swift_bulk_delete.rst:31 +msgid "In addition, you must:" +msgstr "" + +#: ../cli_swift_bulk_delete.rst:33 +msgid "UTF-8-encode and then URL-encode the names." +msgstr "" + +#: ../cli_swift_bulk_delete.rst:35 +msgid "" +"To indicate an object, specify the container and object name as: " +"``CONTAINER_NAME``/``OBJECT_NAME``." +msgstr "" + +#: ../cli_swift_bulk_delete.rst:38 +msgid "" +"To indicate a container, specify the container name as: ``CONTAINER_NAME``. " +"Make sure that the container is empty. If it contains objects, Object " +"Storage cannot delete the container." +msgstr "" + +#: ../cli_swift_bulk_delete.rst:42 +msgid "Set the ``Content-Type`` request header to ``text/plain``." +msgstr "" + +#: ../cli_swift_bulk_delete.rst:45 +msgid "Bulk delete response" +msgstr "" + +#: ../cli_swift_bulk_delete.rst:47 +msgid "" +"When Object Storage processes the request, it performs multiple sub-" +"operations. Even if all sub-operations fail, the operation returns a 200 " +"status. The bulk operation returns a response body that contains details " +"that indicate which sub-operations have succeeded and failed. Some sub-" +"operations might succeed while others fail. Examine the response body to " +"determine the results of each delete sub-operation." +msgstr "" + +#: ../cli_swift_bulk_delete.rst:54 +msgid "" +"You can set the ``Accept`` request header to one of the following values to " +"define the response format:" +msgstr "" + +#: ../cli_swift_bulk_delete.rst:65 +msgid "``application/xml`` or ``text/xml``" +msgstr "" + +#: ../cli_swift_bulk_delete.rst:67 +msgid "The response body contains the following information:" +msgstr "" + +#: ../cli_swift_bulk_delete.rst:69 +msgid "The number of files actually deleted." +msgstr "" + +#: ../cli_swift_bulk_delete.rst:71 +msgid "The number of not found objects." +msgstr "" + +#: ../cli_swift_bulk_delete.rst:73 +msgid "" +"Errors. A list of object names and associated error statuses for the objects " +"that failed to delete. The format depends on the value that you set in the " +"``Accept`` header." +msgstr "" + +#: ../cli_swift_bulk_delete.rst:77 +msgid "" +"The following bulk delete response is in ``application/xml`` format. In this " +"example, the ``mycontainer`` container is not empty, so it cannot be deleted." +msgstr "" + +#: ../cli_swift_create_containers.rst:3 +msgid "Create and manage containers" +msgstr "" + +#: ../cli_swift_create_containers.rst:5 +msgid "" +"To create a container, run the following command and replace ``CONTAINER`` " +"with the name of your container." +msgstr "" + +#: ../cli_swift_create_containers.rst:12 +msgid "To list all containers, run the following command:" +msgstr "" + +#: ../cli_swift_create_containers.rst:18 +msgid "To check the status of containers, run the following command:" +msgstr "" + +#: ../cli_swift_create_containers.rst:34 +msgid "" +"You can also use the ``swift stat`` command with the ``ACCOUNT`` or " +"``CONTAINER`` names as parameters." +msgstr "" + +#: ../cli_swift_discoverability.rst:5 +msgid "Discoverability" +msgstr "" + +#: ../cli_swift_discoverability.rst:7 +msgid "" +"Your Object Storage system might not enable all features that this document " +"describes. These features are:" +msgstr "" + +#: ../cli_swift_discoverability.rst:10 +msgid ":ref:`large-object-creation`" +msgstr "" + +#: ../cli_swift_discoverability.rst:11 +msgid ":ref:`archive-auto-extract`" +msgstr "" + +#: ../cli_swift_discoverability.rst:12 +msgid ":ref:`bulk-delete`" +msgstr "" + +#: ../cli_swift_discoverability.rst:13 +msgid ":ref:`static-website`" +msgstr "" + +#: ../cli_swift_discoverability.rst:15 +msgid "" +"To discover which features are enabled in your Object Storage system, use " +"the ``/info`` request." +msgstr "" + +#: ../cli_swift_discoverability.rst:18 +msgid "" +"To use the ``/info`` request, send a ``GET`` request using the ``/info`` " +"path to the Object Store endpoint as shown in this example:" +msgstr "" + +#: ../cli_swift_discoverability.rst:25 +msgid "This example shows a truncated response body:" +msgstr "" + +#: ../cli_swift_discoverability.rst:41 +msgid "" +"This output shows that the Object Storage system has enabled the static " +"website and temporary URL features." +msgstr "" + +#: ../cli_swift_discoverability.rst:46 +msgid "" +"In some cases, the ``/info`` request will return an error. This could be " +"because your service provider has disabled the ``/info`` request function, " +"or because you are using an older version that does not support it." +msgstr "" + +#: ../cli_swift_env_vars.rst:5 +msgid "Environment variables required to run examples" +msgstr "" + +#: ../cli_swift_env_vars.rst:7 +msgid "" +"To run the cURL command examples for the Object Storage API requests, set " +"these environment variables:" +msgstr "" + +#: ../cli_swift_env_vars.rst:11 +msgid "" +"The public URL that is the HTTP endpoint from where you can access Object " +"Storage. It includes the Object Storage API version number and your account " +"name. For example, ``https://23.253.72.207/v1/my_account``." +msgstr "" + +#: ../cli_swift_env_vars.rst:14 +msgid "publicURL" +msgstr "" + +#: ../cli_swift_env_vars.rst:17 +msgid "The authentication token for Object Storage." +msgstr "" + +#: ../cli_swift_env_vars.rst:17 +msgid "token" +msgstr "" + +#: ../cli_swift_env_vars.rst:19 +msgid "To obtain these values, run the ``swift stat -v`` command." +msgstr "" + +#: ../cli_swift_env_vars.rst:21 +msgid "" +"As shown in this example, the public URL appears in the ``StorageURL`` " +"field, and the token appears in the ``Auth Token`` field:" +msgstr "" + +#: ../cli_swift_large_lists.rst:3 +msgid "Page through large lists of containers or objects" +msgstr "" + +#: ../cli_swift_large_lists.rst:5 +msgid "" +"If you have a large number of containers or objects, you can use the " +"``marker``, ``limit``, and ``end_marker`` parameters to control how many " +"items are returned in a list and where the list starts or ends." +msgstr "" + +#: ../cli_swift_large_lists.rst:10 +msgid "" +"When you request a list of containers or objects, Object Storage returns a " +"maximum of 10,000 names for each request. To get subsequent names, you must " +"make another request with the ``marker`` parameter. Set the ``marker`` " +"parameter to the name of the last item returned in the previous list. You " +"must URL-encode the ``marker`` value before you send the HTTP request. " +"Object Storage returns a maximum of 10,000 names starting after the last " +"item returned." +msgstr "" + +#: ../cli_swift_large_lists.rst:17 +msgid "marker" +msgstr "" + +#: ../cli_swift_large_lists.rst:20 +msgid "" +"To return fewer than 10,000 names, use the ``limit`` parameter. If the " +"number of names returned equals the specified ``limit`` (or 10,000 if you " +"omit the ``limit`` parameter), you can assume there are more names to list. " +"If the number of names in the list is exactly divisible by the ``limit`` " +"value, the last request has no content." +msgstr "" + +#: ../cli_swift_large_lists.rst:25 +msgid "limit" +msgstr "" + +#: ../cli_swift_large_lists.rst:28 +msgid "" +"Limits the result set to names that are less than the ``end_marker`` " +"parameter value. You must URL-encode the ``end_marker`` value before you " +"send the HTTP request." +msgstr "" + +#: ../cli_swift_large_lists.rst:30 +msgid "end_marker" +msgstr "" + +#: ../cli_swift_large_lists.rst:33 +msgid "To page through a large list of containers" +msgstr "" + +#: ../cli_swift_large_lists.rst:35 +msgid "Assume the following list of container names:" +msgstr "" + +#: ../cli_swift_large_lists.rst:45 +msgid "Use a ``limit`` of two:" +msgstr "" + +#: ../cli_swift_large_lists.rst:56 +msgid "Because two container names are returned, there are more names to list." +msgstr "" + +#: ../cli_swift_large_lists.rst:59 +msgid "" +"Make another request with a ``marker`` parameter set to the name of the last " +"item returned:" +msgstr "" + +#: ../cli_swift_large_lists.rst:72 +msgid "Again, two items are returned, and there might be more." +msgstr "" + +#: ../cli_swift_large_lists.rst:74 +msgid "Make another request with a ``marker`` of the last item returned:" +msgstr "" + +#: ../cli_swift_large_lists.rst:85 +msgid "" +"You receive a one-item response, which is fewer than the ``limit`` number of " +"names. This indicates that this is the end of the list." +msgstr "" + +#: ../cli_swift_large_lists.rst:88 +msgid "" +"Use the ``end_marker`` parameter to limit the result set to object names " +"that are less than the ``end_marker`` parameter value:" +msgstr "" + +#: ../cli_swift_large_lists.rst:102 +msgid "" +"You receive a result set of all container names before the ``end-marker`` " +"value." +msgstr "" + +#: ../cli_swift_large_object_creation.rst:5 +msgid "Large objects" +msgstr "" + +#: ../cli_swift_large_object_creation.rst:11 +msgid "" +"By default, the content of an object cannot be greater than 5 GB. However, " +"you can use a number of smaller objects to construct a large object. The " +"large object is comprised of two types of objects:" +msgstr "" + +#: ../cli_swift_large_object_creation.rst:15 +msgid "" +"``Segment objects`` store the object content. You can divide your content " +"into segments, and upload each segment into its own segment object. Segment " +"objects do not have any special features. You create, update, download, and " +"delete segment objects just as you would normal objects." +msgstr "" + +#: ../cli_swift_large_object_creation.rst:21 +msgid "" +"A ``manifest object`` links the segment objects into one logical large " +"object. When you download a manifest object, Object Storage concatenates and " +"returns the contents of the segment objects in the response body of the " +"request. This behavior extends to the response headers returned by ``GET`` " +"and ``HEAD`` requests. The ``Content-Length`` response header value is the " +"total size of all segment objects. Object Storage calculates the ``ETag`` " +"response header value by taking the ``ETag`` value of each segment, " +"concatenating them together, and returning the MD5 checksum of the result. " +"The manifest object types are:" +msgstr "" + +#: ../cli_swift_large_object_creation.rst:33 +msgid "" +"The manifest object content is an ordered list of the names of the segment " +"objects in JSON format. See :ref:`static_large_objects`." +msgstr "" + +#: ../cli_swift_large_object_creation.rst:34 +#: ../cli_swift_large_object_creation.rst:55 +msgid "Static large objects" +msgstr "" + +#: ../cli_swift_large_object_creation.rst:37 +msgid "" +"The manifest object has no content but it has a ``X-Object-Manifest`` " +"metadata header. The value of this header is ``CONTAINER/PREFIX``, where " +"``CONTAINER`` is the name of the container where the segment objects are " +"stored, and ``PREFIX`` is a string that all segment objects have in common. " +"See :ref:`dynamic_large_objects`." +msgstr "" + +#: ../cli_swift_large_object_creation.rst:42 +#: ../cli_swift_large_object_creation.rst:156 +msgid "Dynamic large objects" +msgstr "" + +#: ../cli_swift_large_object_creation.rst:46 +msgid "" +"If you make a ``COPY`` request by using a manifest object as the source, the " +"new object is a normal, and not a segment, object. If the total size of the " +"source segment objects exceeds 5 GB, the ``COPY`` request fails. However, " +"you can make a duplicate of the manifest object and this new object can be " +"larger than 5 GB." +msgstr "" + +#: ../cli_swift_large_object_creation.rst:57 +msgid "" +"To create a static large object, divide your content into pieces and create " +"(upload) a segment object to contain each piece." +msgstr "" + +#: ../cli_swift_large_object_creation.rst:60 +msgid "" +"You must record the ``ETag`` response header that the ``PUT`` operation " +"returns. Alternatively, you can calculate the MD5 checksum of the segment " +"prior to uploading and include this in the ``ETag`` request header. This " +"ensures that the upload cannot corrupt your data." +msgstr "" + +#: ../cli_swift_large_object_creation.rst:65 +msgid "" +"List the name of each segment object along with its size and MD5 checksum in " +"order." +msgstr "" + +#: ../cli_swift_large_object_creation.rst:68 +msgid "" +"Create a manifest object. Include the ``?multipart-manifest=put`` query " +"string at the end of the manifest object name to indicate that this is a " +"manifest object." +msgstr "" + +#: ../cli_swift_large_object_creation.rst:72 +msgid "" +"The body of the ``PUT`` request on the manifest object comprises a JSON " +"list, where each element contains the following attributes:" +msgstr "" + +#: ../cli_swift_large_object_creation.rst:76 +msgid "" +"The container and object name in the format: ``CONTAINER_NAME/OBJECT_NAME``." +msgstr "" + +#: ../cli_swift_large_object_creation.rst:77 +msgid "path" +msgstr "" + +#: ../cli_swift_large_object_creation.rst:80 +msgid "" +"The MD5 checksum of the content of the segment object. This value must match " +"the ``ETag`` of that object." +msgstr "" + +#: ../cli_swift_large_object_creation.rst:81 +msgid "etag" +msgstr "" + +#: ../cli_swift_large_object_creation.rst:84 +msgid "" +"The size of the segment object. This value must match the ``Content-Length`` " +"of that object." +msgstr "" + +#: ../cli_swift_large_object_creation.rst:85 +msgid "size_bytes" +msgstr "" + +#: ../cli_swift_large_object_creation.rst:88 +msgid "Static large object manifest list" +msgstr "" + +#: ../cli_swift_large_object_creation.rst:90 +msgid "" +"This example shows three segment objects. You can use several containers and " +"the object names do not have to conform to a specific pattern, in contrast " +"to dynamic large objects." +msgstr "" + +#: ../cli_swift_large_object_creation.rst:116 +msgid "" +"The ``Content-Length`` request header must contain the length of the JSON " +"content—not the length of the segment objects. However, after the ``PUT`` " +"operation completes, the ``Content-Length`` metadata is set to the total " +"length of all the object segments. A similar situation applies to the " +"``ETag``. If used in the ``PUT`` operation, it must contain the MD5 checksum " +"of the JSON content. The ``ETag`` metadata value is then set to be the MD5 " +"checksum of the concatenated ``ETag`` values of the object segments. You can " +"also set the ``Content-Type`` request header and custom object metadata." +msgstr "" + +#: ../cli_swift_large_object_creation.rst:126 +msgid "" +"When the ``PUT`` operation sees the ``?multipart-manifest=put`` query " +"parameter, it reads the request body and verifies that each segment object " +"exists and that the sizes and ETags match. If there is a mismatch, the " +"``PUT`` operation fails." +msgstr "" + +#: ../cli_swift_large_object_creation.rst:131 +msgid "" +"If everything matches, the manifest object is created. The ``X-Static-Large-" +"Object`` metadata is set to ``true`` indicating that this is a static object " +"manifest." +msgstr "" + +#: ../cli_swift_large_object_creation.rst:135 +msgid "" +"Normally when you perform a ``GET`` operation on the manifest object, the " +"response body contains the concatenated content of the segment objects. To " +"download the manifest list, use the ``?multipart-manifest=get`` query " +"parameter. The resulting list is not formatted the same as the manifest you " +"originally used in the ``PUT`` operation." +msgstr "" + +#: ../cli_swift_large_object_creation.rst:142 +msgid "" +"If you use the ``DELETE`` operation on a manifest object, the manifest " +"object is deleted. The segment objects are not affected. However, if you add " +"the ``?multipart-manifest=delete`` query parameter, the segment objects are " +"deleted and if all are successfully deleted, the manifest object is also " +"deleted." +msgstr "" + +#: ../cli_swift_large_object_creation.rst:148 +msgid "" +"To change the manifest, use a ``PUT`` operation with the ``?multipart-" +"manifest=put`` query parameter. This request creates a manifest object. You " +"can also update the object metadata in the usual way." +msgstr "" + +#: ../cli_swift_large_object_creation.rst:158 +msgid "" +"You must segment objects that are larger than 5 GB before you can upload " +"them. You then upload the segment objects like you would any other object " +"and create a dynamic large manifest object. The manifest object tells Object " +"Storage how to find the segment objects that comprise the large object. The " +"segments remain individually addressable, but retrieving the manifest object " +"streams all the segments concatenated. There is no limit to the number of " +"segments that can be a part of a single large object." +msgstr "" + +#: ../cli_swift_large_object_creation.rst:167 +msgid "" +"To ensure the download works correctly, you must upload all the object " +"segments to the same container and ensure that each object name is prefixed " +"in such a way that it sorts in the order in which it should be concatenated. " +"You also create and upload a manifest file. The manifest file is a zero-byte " +"file with the extra ``X-Object-Manifest`` ``CONTAINER/PREFIX`` header, where " +"``CONTAINER`` is the container the object segments are in and ``PREFIX`` is " +"the common prefix for all the segments. You must UTF-8-encode and then URL-" +"encode the container and common prefix in the ``X-Object-Manifest`` header." +msgstr "" + +#: ../cli_swift_large_object_creation.rst:177 +msgid "" +"It is best to upload all the segments first and then create or update the " +"manifest. With this method, the full object is not available for downloading " +"until the upload is complete. Also, you can upload a new set of segments to " +"a second location and update the manifest to point to this new location. " +"During the upload of the new segments, the original manifest is still " +"available to download the first set of segments." +msgstr "" + +#: ../cli_swift_large_object_creation.rst:185 +msgid "Upload segment of large object request: HTTP" +msgstr "" + +#: ../cli_swift_large_object_creation.rst:196 +msgid "" +"No response body is returned. A status code of 2``nn`` (between 200 and 299, " +"inclusive) indicates a successful write; status 411 Length Required denotes " +"a missing ``Content-Length`` or ``Content-Type`` header in the request. If " +"the MD5 checksum of the data written to the storage system does NOT match " +"the (optionally) supplied ETag value, a 422 Unprocessable Entity response is " +"returned." +msgstr "" + +#: ../cli_swift_large_object_creation.rst:203 +msgid "" +"You can continue uploading segments, like this example shows, prior to " +"uploading the manifest." +msgstr "" + +#: ../cli_swift_large_object_creation.rst:207 +msgid "Upload next segment of large object request: HTTP" +msgstr "" + +#: ../cli_swift_large_object_creation.rst:218 +msgid "" +"Next, upload the manifest you created that indicates the container where the " +"object segments reside. Note that uploading additional segments after the " +"manifest is created causes the concatenated object to be that much larger " +"but you do not need to recreate the manifest file for subsequent additional " +"segments." +msgstr "" + +#: ../cli_swift_large_object_creation.rst:225 +msgid "Upload manifest request: HTTP" +msgstr "" + +#: ../cli_swift_large_object_creation.rst:237 +msgid "Upload manifest response: HTTP" +msgstr "" + +#: ../cli_swift_large_object_creation.rst:242 +msgid "" +"The ``Content-Type`` in the response for a ``GET`` or ``HEAD`` on the " +"manifest is the same as the ``Content-Type`` set during the ``PUT`` request " +"that created the manifest. You can change the ``Content-Type`` by reissuing " +"the ``PUT`` request." +msgstr "" + +#: ../cli_swift_large_object_creation.rst:248 +msgid "Comparison of static and dynamic large objects" +msgstr "" + +#: ../cli_swift_large_object_creation.rst:250 +msgid "" +"While static and dynamic objects have similar behavior, this table describes " +"their differences:" +msgstr "" + +# #-#-#-#-# cli_swift_large_object_creation.pot (End User Guide 1.0.0) #-#-#-#-# +# #-#-#-#-# cli_swift_serialized_response_formats.pot (End User Guide 1.0.0) #-#-#-#-# +#: ../cli_swift_large_object_creation.rst:258 +#: ../cli_swift_serialized_response_formats.rst:17 +msgid "Description" +msgstr "" + +#: ../cli_swift_large_object_creation.rst:259 +msgid "Static large object" +msgstr "" + +#: ../cli_swift_large_object_creation.rst:260 +msgid "Dynamic large object" +msgstr "" + +#: ../cli_swift_large_object_creation.rst:261 +msgid "End-to-end integrity" +msgstr "" + +#: ../cli_swift_large_object_creation.rst:262 +msgid "" +"Assured. The list of segments includes the MD5 checksum (``ETag``) of each " +"segment. You cannot upload the manifest object if the ``ETag`` in the list " +"differs from the uploaded segment object. If a segment is somehow lost, an " +"attempt to download the manifest object results in an error." +msgstr "" + +#: ../cli_swift_large_object_creation.rst:267 +msgid "" +"Not guaranteed. The eventual consistency model means that although you have " +"uploaded a segment object, it might not appear in the container listing " +"until later. If you download the manifest before it appears in the " +"container, it does not form part of the content returned in response to a " +"``GET`` request." +msgstr "" + +#: ../cli_swift_large_object_creation.rst:273 +msgid "Upload order" +msgstr "" + +#: ../cli_swift_large_object_creation.rst:274 +msgid "You must upload the segment objects before upload the manifest object." +msgstr "" + +#: ../cli_swift_large_object_creation.rst:276 +msgid "" +"You can upload manifest and segment objects in any order. You are " +"recommended to upload the manifest object after the segments in case a " +"premature download of the manifest occurs. However, this is not enforced." +msgstr "" + +#: ../cli_swift_large_object_creation.rst:280 +msgid "Removal or addition of segment objects" +msgstr "" + +#: ../cli_swift_large_object_creation.rst:281 +msgid "" +"You cannot add or remove segment objects from the manifest. However, you can " +"create a completely new manifest object of the same name with a different " +"manifest list." +msgstr "" + +#: ../cli_swift_large_object_creation.rst:284 +msgid "" +"You can upload new segment objects or remove existing segments. The names " +"must simply match the ``PREFIX`` supplied in ``X-Object-Manifest``." +msgstr "" + +#: ../cli_swift_large_object_creation.rst:287 +msgid "Segment object size and number" +msgstr "" + +#: ../cli_swift_large_object_creation.rst:288 +msgid "" +"Segment objects must be at least 1 MB in size (by default). The final " +"segment object can be any size. At most, 1000 segments are supported (by " +"default)." +msgstr "" + +#: ../cli_swift_large_object_creation.rst:291 +msgid "Segment objects can be any size." +msgstr "" + +#: ../cli_swift_large_object_creation.rst:292 +msgid "Segment object container name" +msgstr "" + +#: ../cli_swift_large_object_creation.rst:293 +msgid "" +"The manifest list includes the container name of each object. Segment " +"objects can be in different containers." +msgstr "" + +#: ../cli_swift_large_object_creation.rst:295 +msgid "All segment objects must be in the same container." +msgstr "" + +#: ../cli_swift_large_object_creation.rst:296 +msgid "Manfiest object metadata" +msgstr "" + +#: ../cli_swift_large_object_creation.rst:297 +msgid "" +"The object has ``X-Static-Large-Object`` set to ``true``. You do not set " +"this metadata directly. Instead the system sets it when you ``PUT`` a static " +"manifest object." +msgstr "" + +#: ../cli_swift_large_object_creation.rst:300 +msgid "" +"The ``X-Object-Manifest`` value is the ``CONTAINER/PREFIX``, which indicates " +"where the segment objects are located. You supply this request header in the " +"``PUT`` operation." +msgstr "" + +#: ../cli_swift_large_object_creation.rst:303 +msgid "Copying the manifest object" +msgstr "" + +#: ../cli_swift_large_object_creation.rst:304 +msgid "" +"Include the ``?multipart-manifest=get`` query string in the ``COPY`` " +"request. The new object contains the same manifest as the original. The " +"segment objects are not copied. Instead, both the original and new manifest " +"objects share the same set of segment objects." +msgstr "" + +#: ../cli_swift_large_object_creation.rst:309 +msgid "" +"The ``COPY`` operation does not create a manifest object. To duplicate a " +"manifest object, use the ``GET`` operation to read the value of ``X-Object-" +"Manifest`` and use this value in the ``X-Object-Manifest`` request header in " +"a ``PUT`` operation. This creates a new manifest object that shares the same " +"set of segment objects as the original manifest object." +msgstr "" + +#: ../cli_swift_manage_access_swift.rst:3 +msgid "Manage access" +msgstr "" + +#: ../cli_swift_manage_access_swift.rst:5 +msgid "" +"Users have roles on accounts. For example, a user with the admin role has " +"full access to all containers and objects in an account. You can set access " +"control lists (ACLs) at the container level and support lists for read and " +"write access, which you set with the ``X-Container-Read`` and ``X-Container-" +"Write`` headers." +msgstr "" + +#: ../cli_swift_manage_access_swift.rst:11 +msgid "" +"To give a user read access, use the ``swift post`` command with the ``-r`` " +"parameter. To give a user write access, use the ``-w`` parameter." +msgstr "" + +#: ../cli_swift_manage_access_swift.rst:15 +msgid "" +"The following example enables the ``testuser`` user to read objects in the " +"container:" +msgstr "" + +#: ../cli_swift_manage_access_swift.rst:22 +msgid "You can also use this command with a list of users." +msgstr "" + +#: ../cli_swift_manage_access_swift.rst:24 +msgid "" +"If you use StaticWeb middleware to enable Object Storage to serve public web " +"content, use ``.r:``, followed by a list of allowed referrers." +msgstr "" + +#: ../cli_swift_manage_access_swift.rst:28 +msgid "The following command gives object access to all referring domains:" +msgstr "" + +#: ../cli_swift_manage_objects.rst:3 +msgid "Manage objects" +msgstr "" + +#: ../cli_swift_manage_objects.rst:5 +msgid "To upload an object to a container, run the following command:" +msgstr "" + +#: ../cli_swift_manage_objects.rst:11 +msgid "To upload in chunks, for large files, run the following command:" +msgstr "" + +#: ../cli_swift_manage_objects.rst:17 +msgid "To check the status of the object, run the following command:" +msgstr "" + +#: ../cli_swift_manage_objects.rst:36 +msgid "To list the objects in a container, run the following command:" +msgstr "" + +#: ../cli_swift_manage_objects.rst:42 +msgid "To download an object from a container, run the following command:" +msgstr "" + +#: ../cli_swift_pseudo_hierarchical_folders_directories.rst:3 +msgid "Pseudo-hierarchical folders and directories" +msgstr "" + +#: ../cli_swift_pseudo_hierarchical_folders_directories.rst:5 +msgid "" +"Although you cannot nest directories in OpenStack Object Storage, you can " +"simulate a hierarchical structure within a single container by adding " +"forward slash characters (``/``) in the object name. To navigate the pseudo-" +"directory structure, you can use the ``delimiter`` query parameter. This " +"example shows you how to use pseudo-hierarchical folders and directories." +msgstr "" + +#: ../cli_swift_pseudo_hierarchical_folders_directories.rst:14 +msgid "" +"In this example, the objects reside in a container called ``backups``. " +"Within that container, the objects are organized in a pseudo-directory " +"called ``photos``. The container name is not displayed in the example, but " +"it is a part of the object URLs. For instance, the URL of the picture ``me." +"jpg`` is ``https://storage.swiftdrive.com/v1/CF_xer7_343/backups/photos/me." +"jpg``." +msgstr "" + +#: ../cli_swift_pseudo_hierarchical_folders_directories.rst:22 +msgid "List pseudo-hierarchical folders request: HTTP" +msgstr "" + +#: ../cli_swift_pseudo_hierarchical_folders_directories.rst:24 +msgid "" +"To display a list of all the objects in the storage container, use ``GET`` " +"without a ``delimiter`` or ``prefix``." +msgstr "" + +#: ../cli_swift_pseudo_hierarchical_folders_directories.rst:32 +msgid "" +"The system returns status code 2xx (between 200 and 299, inclusive) and the " +"requested list of the objects." +msgstr "" + +#: ../cli_swift_pseudo_hierarchical_folders_directories.rst:46 +msgid "" +"Use the delimiter parameter to limit the displayed results. To use " +"``delimiter`` with pseudo-directories, you must use the parameter slash (``/" +"``)." +msgstr "" + +#: ../cli_swift_pseudo_hierarchical_folders_directories.rst:55 +msgid "" +"The system returns status code 2xx (between 200 and 299, inclusive) and the " +"requested matching objects. Because you use the slash, only the pseudo-" +"directory ``photos/`` displays. The returned values from a slash " +"``delimiter`` query are not real objects. They have a content-type of " +"``application/directory`` and are in the ``subdir`` section of JSON and XML " +"results." +msgstr "" + +#: ../cli_swift_pseudo_hierarchical_folders_directories.rst:66 +msgid "" +"Use the ``prefix`` and ``delimiter`` parameters to view the objects inside a " +"pseudo-directory, including further nested pseudo-directories." +msgstr "" + +#: ../cli_swift_pseudo_hierarchical_folders_directories.rst:74 +msgid "" +"The system returns status code 2xx (between 200 and 299, inclusive) and the " +"objects and pseudo-directories within the top level pseudo-directory." +msgstr "" + +#: ../cli_swift_pseudo_hierarchical_folders_directories.rst:84 +msgid "" +"You can create an unlimited number of nested pseudo-directories. To navigate " +"through them, use a longer ``prefix`` parameter coupled with the " +"``delimiter`` parameter. In this sample output, there is a pseudo-directory " +"called ``dogs`` within the pseudo-directory ``animals``. To navigate " +"directly to the files contained within ``dogs``, enter the following command:" +msgstr "" + +#: ../cli_swift_pseudo_hierarchical_folders_directories.rst:96 +msgid "" +"The system returns status code 2xx (between 200 and 299, inclusive) and the " +"objects and pseudo-directories within the nested pseudo-directory." +msgstr "" + +#: ../cli_swift_serialized_response_formats.rst:3 +msgid "Serialized response formats" +msgstr "" + +#: ../cli_swift_serialized_response_formats.rst:5 +msgid "" +"By default, the Object Storage API uses a ``text/plain`` response format. In " +"addition, both JSON and XML data serialization response formats are " +"supported." +msgstr "" + +#: ../cli_swift_serialized_response_formats.rst:11 +msgid "" +"To run the cURL command examples, you must export environment variables. For " +"more information, see the section :ref:`env-vars`." +msgstr "" + +#: ../cli_swift_serialized_response_formats.rst:14 +msgid "To define the response format, use one of these methods:" +msgstr "" + +#: ../cli_swift_serialized_response_formats.rst:17 +msgid "Method" +msgstr "" + +#: ../cli_swift_serialized_response_formats.rst:19 +msgid "" +"Append this parameter to the URL for a ``GET`` request, where ``format`` is " +"``json`` or ``xml``." +msgstr "" + +#: ../cli_swift_serialized_response_formats.rst:19 +msgid "format= ``format`` query parameter" +msgstr "" + +#: ../cli_swift_serialized_response_formats.rst:22 +msgid "" +"Include this header in the ``GET`` request. The valid header values are:" +msgstr "" + +#: ../cli_swift_serialized_response_formats.rst:22 +msgid "``Accept`` request header" +msgstr "" + +#: ../cli_swift_serialized_response_formats.rst:25 +msgid "text/plain" +msgstr "" + +#: ../cli_swift_serialized_response_formats.rst:26 +msgid "Plain text response format. The default." +msgstr "" + +#: ../cli_swift_serialized_response_formats.rst:27 +msgid "application/jsontext" +msgstr "" + +#: ../cli_swift_serialized_response_formats.rst:28 +msgid "JSON data serialization response format." +msgstr "" + +#: ../cli_swift_serialized_response_formats.rst:29 +msgid "application/xml" +msgstr "" + +#: ../cli_swift_serialized_response_formats.rst:30 +#: ../cli_swift_serialized_response_formats.rst:32 +msgid "XML data serialization response format." +msgstr "" + +#: ../cli_swift_serialized_response_formats.rst:31 +msgid "text/xml" +msgstr "" + +#: ../cli_swift_serialized_response_formats.rst:36 +msgid "Example 1. JSON example with format query parameter" +msgstr "" + +#: ../cli_swift_serialized_response_formats.rst:38 +msgid "" +"For example, this request uses the ``format`` query parameter to ask for a " +"JSON response:" +msgstr "" + +#: ../cli_swift_serialized_response_formats.rst:59 +msgid "" +"Object Storage lists container names with additional information in JSON " +"format:" +msgstr "" + +#: ../cli_swift_serialized_response_formats.rst:79 +msgid "Example 2. XML example with Accept header" +msgstr "" + +#: ../cli_swift_serialized_response_formats.rst:81 +msgid "" +"This request uses the ``Accept`` request header to ask for an XML response:" +msgstr "" + +#: ../cli_swift_serialized_response_formats.rst:103 +msgid "" +"Object Storage lists container names with additional information in XML " +"format:" +msgstr "" + +#: ../cli_swift_serialized_response_formats.rst:122 +msgid "" +"The remainder of the examples in this guide use standard, non-serialized " +"responses. However, all ``GET`` requests that perform list operations accept " +"the ``format`` query parameter or ``Accept`` request header." +msgstr "" + +#: ../cli_swift_set_object_versions.rst:3 +msgid "Object versioning" +msgstr "" + +#: ../cli_swift_set_object_versions.rst:5 +msgid "" +"You can store multiple versions of your content so that you can recover from " +"unintended overwrites. Object versioning is an easy way to implement version " +"control, which you can use with any type of content." +msgstr "" + +#: ../cli_swift_set_object_versions.rst:11 +msgid "" +"You cannot version a large-object manifest file, but the large-object " +"manifest file can point to versioned segments." +msgstr "" + +#: ../cli_swift_set_object_versions.rst:14 +msgid "" +"We strongly recommend that you put non-current objects in a different " +"container than the container where current object versions reside." +msgstr "" + +#: ../cli_swift_set_object_versions.rst:18 +msgid "To enable and use object versioning" +msgstr "" + +#: ../cli_swift_set_object_versions.rst:20 +msgid "" +"To enable object versioning, ask your cloud provider to set the " +"``allow_versions`` option to ``TRUE`` in the container configuration file." +msgstr "" + +#: ../cli_swift_set_object_versions.rst:24 +msgid "Create an ``archive`` container to store older versions of objects:" +msgstr "" + +#: ../cli_swift_set_object_versions.rst:38 +msgid "Create a ``current`` container to store current versions of objects." +msgstr "" + +#: ../cli_swift_set_object_versions.rst:40 +msgid "" +"Include the ``X-Versions-Location`` header. This header defines the " +"container that holds the non-current versions of your objects. You must " +"UTF-8-encode and then URL-encode the container name before you include it in " +"the ``X-Versions-Location`` header. This header enables object versioning " +"for all objects in the ``current`` container. Changes to objects in the " +"``current`` container automatically create non-current versions in the " +"``archive`` container." +msgstr "" + +#: ../cli_swift_set_object_versions.rst:61 +msgid "Create the first version of an object in the ``current`` container:" +msgstr "" + +#: ../cli_swift_set_object_versions.rst:78 +msgid "" +"Nothing is written to the non-current version container when you initially " +"``PUT`` an object in the ``current`` container. However, subsequent ``PUT`` " +"requests that edit an object trigger the creation of a version of that " +"object in the ``archive`` container." +msgstr "" + +#: ../cli_swift_set_object_versions.rst:83 +msgid "These non-current versions are named as follows:" +msgstr "" + +#: ../cli_swift_set_object_versions.rst:89 +msgid "" +"Where ``length`` is the 3-character, zero-padded hexadecimal character " +"length of the object, ```` is the object name, and " +"```` is the time when the object was initially created as a " +"current version." +msgstr "" + +#: ../cli_swift_set_object_versions.rst:94 +msgid "Create a second version of the object in the ``current`` container:" +msgstr "" + +#: ../cli_swift_set_object_versions.rst:111 +msgid "" +"Issue a ``GET`` request to a versioned object to get the current version of " +"the object. You do not have to do any request redirects or metadata lookups." +msgstr "" + +#: ../cli_swift_set_object_versions.rst:115 +msgid "List older versions of the object in the ``archive`` container:" +msgstr "" + +#: ../cli_swift_set_object_versions.rst:138 +msgid "" +"A ``POST`` request to a versioned object updates only the metadata for the " +"object and does not create a new version of the object. New versions are " +"created only when the content of the object changes." +msgstr "" + +#: ../cli_swift_set_object_versions.rst:142 +msgid "" +"Issue a ``DELETE`` request to a versioned object to remove the current " +"version of the object and replace it with the next-most current version in " +"the non-current container." +msgstr "" + +#: ../cli_swift_set_object_versions.rst:159 +msgid "" +"List objects in the ``archive`` container to show that the archived object " +"was moved back to the ``current`` container:" +msgstr "" + +#: ../cli_swift_set_object_versions.rst:179 +msgid "" +"This next-most current version carries with it any metadata last set on it. " +"If you want to completely remove an object and you have five versions of it, " +"you must ``DELETE`` it five times." +msgstr "" + +#: ../cli_swift_set_object_versions.rst:183 +msgid "" +"To disable object versioning for the ``current`` container, remove its ``X-" +"Versions-Location`` metadata header by sending an empty key value." +msgstr "" + +#: ../cli_swift_static_website.rst:5 +msgid "Create static website" +msgstr "" + +#: ../cli_swift_static_website.rst:11 +msgid "" +"You can use your Object Storage account to create a static website. This " +"static website is created with Static Web middleware and serves container " +"data with a specified index file, error file resolution, and optional file " +"listings. This mode is normally active only for anonymous requests, which " +"provide no authentication token. To use it with authenticated requests, set " +"the header ``X-Web-Mode`` to ``TRUE`` on the request." +msgstr "" + +#: ../cli_swift_static_website.rst:18 +msgid "" +"The Static Web filter must be added to the pipeline in your ``/etc/swift/" +"proxy-server.conf`` file below any authentication middleware. You must also " +"add a Static Web middleware configuration section." +msgstr "" + +#: ../cli_swift_static_website.rst:23 +msgid "" +"See the Cloud Administrator Guide for an example of the `static web " +"configuration syntax `_." +msgstr "" + +#: ../cli_swift_static_website.rst:25 +msgid "" +"See the Cloud Administrator Guide for a complete example of the `/etc/swift/" +"proxy-server.conf file `_ (including static web)." +msgstr "" + +#: ../cli_swift_static_website.rst:27 +msgid "" +"Your publicly readable containers are checked for two headers, ``X-Container-" +"Meta-Web-Index`` and ``X-Container-Meta-Web-Error``. The ``X-Container-Meta-" +"Web-Error`` header is discussed below, in the section called :ref:" +"`set_error_static_website`." +msgstr "" + +#: ../cli_swift_static_website.rst:32 +msgid "" +"Use ``X-Container-Meta-Web-Index`` to determine the index file (or default " +"page served, such as ``index.html``) for your website. When someone " +"initially enters your site, the ``index.html`` file displays automatically. " +"If you create sub-directories for your site by creating pseudo-directories " +"in your container, the index page for each sub-directory is displayed by " +"default. If your pseudo-directory does not have a file with the same name as " +"your index file, visits to the sub-directory return a 404 error." +msgstr "" + +#: ../cli_swift_static_website.rst:41 +msgid "" +"You also have the option of displaying a list of files in your pseudo-" +"directory instead of a web page. To do this, set the ``X-Container-Meta-Web-" +"Listings`` header to ``TRUE``. You may add styles to your file listing by " +"setting ``X-Container-Meta-Web-Listings-CSS`` to a style sheet (for example, " +"``lists.css``)." +msgstr "" + +#: ../cli_swift_static_website.rst:48 +msgid "Static Web middleware through Object Storage" +msgstr "" + +#: ../cli_swift_static_website.rst:50 +msgid "" +"The following sections show how to use Static Web middleware through Object " +"Storage." +msgstr "" + +#: ../cli_swift_static_website.rst:54 +msgid "Make container publicly readable" +msgstr "" + +#: ../cli_swift_static_website.rst:56 +msgid "" +"Make the container publicly readable. Once the container is publicly " +"readable, you can access your objects directly, but you must set the index " +"file to browse the main site URL and its sub-directories." +msgstr "" + +#: ../cli_swift_static_website.rst:66 +msgid "Set site index file" +msgstr "" + +#: ../cli_swift_static_website.rst:68 +msgid "" +"Set the index file. In this case, ``index.html`` is the default file " +"displayed when the site appears." +msgstr "" + +#: ../cli_swift_static_website.rst:76 +msgid "Enable file listing" +msgstr "" + +#: ../cli_swift_static_website.rst:78 +msgid "" +"Turn on file listing. If you do not set the index file, the URL displays a " +"list of the objects in the container. Instructions on styling the list with " +"a CSS follow." +msgstr "" + +#: ../cli_swift_static_website.rst:87 +msgid "Enable CSS for file listing" +msgstr "" + +#: ../cli_swift_static_website.rst:89 +msgid "Style the file listing using a CSS." +msgstr "" + +#: ../cli_swift_static_website.rst:98 +msgid "Set error pages for static website" +msgstr "" + +#: ../cli_swift_static_website.rst:100 +msgid "" +"You can create and set custom error pages for visitors to your website; " +"currently, only 401 (Unauthorized) and 404 (Not Found) errors are supported. " +"To do this, set the metadata header, ``X-Container-Meta-Web-Error``." +msgstr "" + +#: ../cli_swift_static_website.rst:105 +msgid "" +"Error pages are served with the status code pre-pended to the name of the " +"error page you set. For instance, if you set ``X-Container-Meta-Web-Error`` " +"to ``error.html``, 401 errors will display the page ``401error.html``. " +"Similarly, 404 errors will display ``404error.html``. You must have both of " +"these pages created in your container when you set the ``X-Container-Meta-" +"Web-Error`` metadata, or your site will display generic error pages." +msgstr "" + +#: ../cli_swift_static_website.rst:113 +msgid "" +"You only have to set the ``X-Container-Meta-Web-Error`` metadata once for " +"your entire static website." +msgstr "" + +#: ../cli_swift_static_website.rst:117 +msgid "Set error pages for static website request" +msgstr "" + +#: ../cli_swift_static_website.rst:124 +msgid "Any 2\\ ``nn`` response indicates success." +msgstr "" + +#: ../cli_use_snapshots_to_migrate_instances.rst:3 +msgid "Use snapshots to migrate instances" +msgstr "" + +#: ../cli_use_snapshots_to_migrate_instances.rst:5 +msgid "" +"To use snapshots to migrate instances from OpenStack projects to clouds, " +"complete these steps." +msgstr "" + +#: ../cli_use_snapshots_to_migrate_instances.rst:8 +msgid "In the source project:" +msgstr "" + +#: ../cli_use_snapshots_to_migrate_instances.rst:10 +msgid ":ref:`Create_a_snapshot_of_the_instance`" +msgstr "" + +#: ../cli_use_snapshots_to_migrate_instances.rst:12 +msgid ":ref:`Download_the_snapshot_as_an_image`" +msgstr "" + +#: ../cli_use_snapshots_to_migrate_instances.rst:14 +msgid "In the destination project:" +msgstr "" + +#: ../cli_use_snapshots_to_migrate_instances.rst:16 +msgid ":ref:`Import_the_snapshot_to_the_new_environment`" +msgstr "" + +#: ../cli_use_snapshots_to_migrate_instances.rst:18 +msgid ":ref:`Boot_a_new_instance_from_the_snapshot`" +msgstr "" + +#: ../cli_use_snapshots_to_migrate_instances.rst:22 +msgid "Some cloud providers allow only administrators to perform this task." +msgstr "" + +#: ../cli_use_snapshots_to_migrate_instances.rst:27 +msgid "Create a snapshot of the instance" +msgstr "" + +#: ../cli_use_snapshots_to_migrate_instances.rst:29 +msgid "" +"Shut down the source VM before you take the snapshot to ensure that all data " +"is flushed to disk. If necessary, list the instances to view the instance " +"name::" +msgstr "" + +#: ../cli_use_snapshots_to_migrate_instances.rst:42 +msgid "" +"Use the :command:`nova list` command to confirm that the instance shows a " +"``SHUTOFF`` status::" +msgstr "" + +#: ../cli_use_snapshots_to_migrate_instances.rst:52 +msgid "Use the :command:`nova image-create` command to take a snapshot::" +msgstr "" + +#: ../cli_use_snapshots_to_migrate_instances.rst:57 +msgid "" +"Use the :command:`nova image-list` command to check the status until the " +"status is ``ACTIVE``::" +msgstr "" + +#: ../cli_use_snapshots_to_migrate_instances.rst:73 +msgid "Download the snapshot as an image" +msgstr "" + +#: ../cli_use_snapshots_to_migrate_instances.rst:75 +msgid "Get the image ID::" +msgstr "" + +#: ../cli_use_snapshots_to_migrate_instances.rst:84 +msgid "" +"Download the snapshot by using the image ID that was returned in the " +"previous step::" +msgstr "" + +#: ../cli_use_snapshots_to_migrate_instances.rst:92 +msgid "" +"The :command:`glance image-download` command requires the image ID and " +"cannot use the image name. Check there is sufficient space on the " +"destination file system for the image file." +msgstr "" + +#: ../cli_use_snapshots_to_migrate_instances.rst:97 +msgid "" +"Make the image available to the new environment, either through HTTP or " +"direct upload to a machine (``scp``)." +msgstr "" + +#: ../cli_use_snapshots_to_migrate_instances.rst:103 +msgid "Import the snapshot to the new environment" +msgstr "" + +#: ../cli_use_snapshots_to_migrate_instances.rst:105 +msgid "In the new project or cloud environment, import the snapshot:" +msgstr "" + +#: ../cli_use_snapshots_to_migrate_instances.rst:114 +msgid "Boot a new instance from the snapshot" +msgstr "" + +#: ../cli_use_snapshots_to_migrate_instances.rst:116 +msgid "" +"In the new project or cloud environment, use the snapshot to create the new " +"instance::" +msgstr "" + +#: ../configure_access_and_security_for_instances.rst:5 +msgid "" +"Before you launch an instance, you should add security group rules to enable " +"users to ping and use SSH to connect to the instance. Security groups are " +"sets of IP filter rules that define networking access and are applied to all " +"instances within a project. To do so, you either add rules to the default " +"security group :ref:`security_groups_add_rule` or add a new security group " +"with rules." +msgstr "" + +#: ../configure_access_and_security_for_instances.rst:12 +msgid "" +"Key pairs are SSH credentials that are injected into an instance when it is " +"launched. To use key pair injection, the image that the instance is based on " +"must contain the ``cloud-init`` package. Each project should have at least " +"one key pair. For more information, see the section :ref:`keypair_add`." +msgstr "" + +#: ../configure_access_and_security_for_instances.rst:18 +msgid "" +"If you have generated a key pair with an external tool, you can import it " +"into OpenStack. The key pair can be used for multiple instances that belong " +"to a project. For more information, see the section :ref:" +"`dashboard_import_keypair`." +msgstr "" + +#: ../configure_access_and_security_for_instances.rst:23 +msgid "" +"When an instance is created in OpenStack, it is automatically assigned a " +"fixed IP address in the network to which the instance is assigned. This IP " +"address is permanently associated with the instance until the instance is " +"terminated. However, in addition to the fixed IP address, a floating IP " +"address can also be attached to an instance. Unlike fixed IP addresses, " +"floating IP addresses are able to have their associations modified at any " +"time, regardless of the state of the instances involved." +msgstr "" + +#: ../configure_access_and_security_for_instances.rst:34 +msgid "Add a rule to the default security group" +msgstr "" + +#: ../configure_access_and_security_for_instances.rst:36 +msgid "" +"This procedure enables SSH and ICMP (ping) access to instances. The rules " +"apply to all instances within a given project, and should be set for every " +"project unless there is a reason to prohibit SSH or ICMP access to the " +"instances." +msgstr "" + +#: ../configure_access_and_security_for_instances.rst:41 +msgid "" +"This procedure can be adjusted as necessary to add additional security group " +"rules to a project, if your cloud requires them." +msgstr "" + +#: ../configure_access_and_security_for_instances.rst:44 +msgid "" +"When adding a rule, you must specify the protocol used with the destination " +"port or source port." +msgstr "" + +# #-#-#-#-# configure_access_and_security_for_instances.pot (End User Guide 1.0.0) #-#-#-#-# +# #-#-#-#-# dashboard_create_networks.pot (End User Guide 1.0.0) #-#-#-#-# +# #-#-#-#-# dashboard_databases.pot (End User Guide 1.0.0) #-#-#-#-# +# #-#-#-#-# dashboard_launch_instances.pot (End User Guide 1.0.0) #-#-#-#-# +# #-#-#-#-# dashboard_manage_containers.pot (End User Guide 1.0.0) #-#-#-#-# +# #-#-#-#-# dashboard_manage_images.pot (End User Guide 1.0.0) #-#-#-#-# +# #-#-#-#-# dashboard_manage_volumes.pot (End User Guide 1.0.0) #-#-#-#-# +# #-#-#-#-# dashboard_stacks.pot (End User Guide 1.0.0) #-#-#-#-# +#: ../configure_access_and_security_for_instances.rst:47 +#: ../configure_access_and_security_for_instances.rst:95 +#: ../configure_access_and_security_for_instances.rst:119 +#: ../configure_access_and_security_for_instances.rst:176 +#: ../dashboard_create_networks.rst:19 ../dashboard_create_networks.rst:71 +#: ../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:197 ../dashboard_launch_instances.rst:230 +#: ../dashboard_manage_containers.rst:19 ../dashboard_manage_containers.rst:40 +#: ../dashboard_manage_containers.rst:73 ../dashboard_manage_containers.rst:96 +#: ../dashboard_manage_containers.rst:127 +#: ../dashboard_manage_containers.rst:155 ../dashboard_manage_images.rst:27 +#: ../dashboard_manage_images.rst:94 ../dashboard_manage_images.rst:124 +#: ../dashboard_manage_volumes.rst:14 ../dashboard_manage_volumes.rst:66 +#: ../dashboard_manage_volumes.rst:109 ../dashboard_manage_volumes.rst:131 +#: ../dashboard_manage_volumes.rst:163 ../dashboard_stacks.rst:28 +#: ../dashboard_stacks.rst:123 ../dashboard_stacks.rst:143 +msgid "Log in to the dashboard." +msgstr "" + +# #-#-#-#-# configure_access_and_security_for_instances.pot (End User Guide 1.0.0) #-#-#-#-# +# #-#-#-#-# dashboard_create_networks.pot (End User Guide 1.0.0) #-#-#-#-# +# #-#-#-#-# dashboard_databases.pot (End User Guide 1.0.0) #-#-#-#-# +# #-#-#-#-# dashboard_launch_instances.pot (End User Guide 1.0.0) #-#-#-#-# +# #-#-#-#-# dashboard_manage_containers.pot (End User Guide 1.0.0) #-#-#-#-# +# #-#-#-#-# dashboard_manage_images.pot (End User Guide 1.0.0) #-#-#-#-# +# #-#-#-#-# dashboard_manage_volumes.pot (End User Guide 1.0.0) #-#-#-#-# +# #-#-#-#-# dashboard_stacks.pot (End User Guide 1.0.0) #-#-#-#-# +#: ../configure_access_and_security_for_instances.rst:49 +#: ../configure_access_and_security_for_instances.rst:97 +#: ../configure_access_and_security_for_instances.rst:121 +#: ../configure_access_and_security_for_instances.rst:178 +#: ../dashboard_create_networks.rst:21 ../dashboard_create_networks.rst:73 +#: ../dashboard_databases.rst:62 ../dashboard_databases.rst:117 +#: ../dashboard_databases.rst:148 ../dashboard_databases.rst:177 +#: ../dashboard_databases.rst:200 ../dashboard_launch_instances.rst:35 +#: ../dashboard_launch_instances.rst:199 ../dashboard_launch_instances.rst:232 +#: ../dashboard_manage_containers.rst:21 ../dashboard_manage_containers.rst:42 +#: ../dashboard_manage_containers.rst:75 ../dashboard_manage_containers.rst:98 +#: ../dashboard_manage_containers.rst:129 +#: ../dashboard_manage_containers.rst:157 ../dashboard_manage_images.rst:29 +#: ../dashboard_manage_images.rst:96 ../dashboard_manage_images.rst:126 +#: ../dashboard_manage_volumes.rst:16 ../dashboard_manage_volumes.rst:68 +#: ../dashboard_manage_volumes.rst:111 ../dashboard_manage_volumes.rst:133 +#: ../dashboard_manage_volumes.rst:139 ../dashboard_manage_volumes.rst:165 +#: ../dashboard_stacks.rst:29 ../dashboard_stacks.rst:124 +#: ../dashboard_stacks.rst:144 +msgid "" +"From the CURRENT PROJECT on the :guilabel:`Project` tab, select the " +"appropriate project." +msgstr "" + +#: ../configure_access_and_security_for_instances.rst:52 +msgid "" +"On the :guilabel:`Project` tab, open the :guilabel:`Compute` tab and click :" +"guilabel:`Access & Security` category. The :guilabel:`Security Groups` tab " +"shows the security groups that are available for this project." +msgstr "" + +#: ../configure_access_and_security_for_instances.rst:57 +msgid "Select the default security group and click :guilabel:`Manage Rules`." +msgstr "" + +#: ../configure_access_and_security_for_instances.rst:59 +msgid "To allow SSH access, click :guilabel:`Add Rule`." +msgstr "" + +#: ../configure_access_and_security_for_instances.rst:61 +#: ../configure_access_and_security_for_instances.rst:77 +msgid "In the :guilabel:`Add Rule` dialog box, enter the following values:" +msgstr "" + +#: ../configure_access_and_security_for_instances.rst:63 +msgid "**Rule**: ``SSH``" +msgstr "" + +#: ../configure_access_and_security_for_instances.rst:64 +msgid "**Remote**: ``CIDR``" +msgstr "" + +#: ../configure_access_and_security_for_instances.rst:66 +msgid "" +"To accept requests from a particular range of IP addresses, specify the IP " +"address block in the :guilabel:`CIDR` box." +msgstr "" + +#: ../configure_access_and_security_for_instances.rst:70 +#: ../configure_access_and_security_for_instances.rst:83 +msgid "Click :guilabel:`Add`." +msgstr "" + +#: ../configure_access_and_security_for_instances.rst:72 +msgid "" +"Instances will now have SSH port 22 open for requests from any IP address." +msgstr "" + +#: ../configure_access_and_security_for_instances.rst:75 +msgid "To add an ICMP rule, click :guilabel:`Add Rule`." +msgstr "" + +#: ../configure_access_and_security_for_instances.rst:79 +msgid "**Rule**: ``All ICMP``" +msgstr "" + +#: ../configure_access_and_security_for_instances.rst:80 +msgid "**Remote**: ``Ingress``" +msgstr "" + +#: ../configure_access_and_security_for_instances.rst:85 +msgid "Instances will now accept all incoming ICMP packets." +msgstr "" + +#: ../configure_access_and_security_for_instances.rst:92 +msgid "Create at least one key pair for each project." +msgstr "" + +#: ../configure_access_and_security_for_instances.rst:100 +#: ../configure_access_and_security_for_instances.rst:124 +#: ../configure_access_and_security_for_instances.rst:181 +msgid "" +"On the :guilabel:`Project` tab, open the :guilabel:`Compute` tab and click :" +"guilabel:`Access & Security` category." +msgstr "" + +#: ../configure_access_and_security_for_instances.rst:103 +#: ../configure_access_and_security_for_instances.rst:127 +msgid "" +"Click the :guilabel:`Key Pairs` tab, which shows the key pairs that are " +"available for this project." +msgstr "" + +#: ../configure_access_and_security_for_instances.rst:106 +msgid "Click :guilabel:`Create Key Pair`." +msgstr "" + +#: ../configure_access_and_security_for_instances.rst:108 +msgid "" +"In the :guilabel:`Create Key Pair` dialog box, enter a name for your key " +"pair, and click :guilabel:`Create Key Pair`." +msgstr "" + +#: ../configure_access_and_security_for_instances.rst:111 +msgid "Respond to the prompt to download the key pair." +msgstr "" + +#: ../configure_access_and_security_for_instances.rst:130 +msgid "Click :guilabel:`Import Key Pair`." +msgstr "" + +#: ../configure_access_and_security_for_instances.rst:132 +msgid "" +"In the :guilabel:`Import Key Pair` dialog box, enter the name of your key " +"pair, copy the public key into the :guilabel:`Public Key` box, and then " +"click :guilabel:`Import Key Pair`." +msgstr "" + +#: ../configure_access_and_security_for_instances.rst:136 +msgid "Save the ``*.pem`` file locally." +msgstr "" + +#: ../configure_access_and_security_for_instances.rst:138 +msgid "" +"To change its permissions so that only you can read and write to the file, " +"run the following command:" +msgstr "" + +#: ../configure_access_and_security_for_instances.rst:145 +msgid "" +"If you are using the Dashboard from a Windows computer, use PuTTYgen to load " +"the ``*.pem`` file and convert and save it as ``*.ppk``. For more " +"information see the `WinSCP web page for PuTTYgen `__." +msgstr "" + +#: ../configure_access_and_security_for_instances.rst:150 +msgid "To make the key pair known to SSH, run the **ssh-add** command." +msgstr "" + +#: ../configure_access_and_security_for_instances.rst:156 +msgid "The Compute database registers the public key of the key pair." +msgstr "" + +#: ../configure_access_and_security_for_instances.rst:158 +msgid "" +"The Dashboard lists the key pair on the :guilabel:`Access & Security` tab." +msgstr "" + +#: ../configure_access_and_security_for_instances.rst:161 +msgid "Allocate a floating IP address to an instance" +msgstr "" + +#: ../configure_access_and_security_for_instances.rst:163 +msgid "" +"When an instance is created in OpenStack, it is automatically assigned a " +"fixed IP address in the network to which the instance is assigned. This IP " +"address is permanently associated with the instance until the instance is " +"terminated." +msgstr "" + +#: ../configure_access_and_security_for_instances.rst:168 +msgid "" +"However, in addition to the fixed IP address, a floating IP address can also " +"be attached to an instance. Unlike fixed IP addresses, floating IP addresses " +"can have their associations modified at any time, regardless of the state of " +"the instances involved. This procedure details the reservation of a floating " +"IP address from an existing pool of addresses and the association of that " +"address with a specific instance." +msgstr "" + +#: ../configure_access_and_security_for_instances.rst:184 +msgid "" +"Click the :guilabel:`Floating IPs` tab, which shows the floating IP " +"addresses allocated to instances." +msgstr "" + +#: ../configure_access_and_security_for_instances.rst:187 +msgid "Click :guilabel:`Allocate IP To Project`." +msgstr "" + +#: ../configure_access_and_security_for_instances.rst:189 +msgid "Choose the pool from which to pick the IP address." +msgstr "" + +#: ../configure_access_and_security_for_instances.rst:191 +msgid "Click :guilabel:`Allocate IP`." +msgstr "" + +#: ../configure_access_and_security_for_instances.rst:193 +msgid "In the :guilabel:`Floating IPs` list, click :guilabel:`Associate`." +msgstr "" + +#: ../configure_access_and_security_for_instances.rst:195 +msgid "" +"In the :guilabel:`Manage Floating IP Associations` dialog box, choose the " +"following options:" +msgstr "" + +#: ../configure_access_and_security_for_instances.rst:198 +msgid "" +"The :guilabel:`IP Address` field is filled automatically, but you can add a " +"new IP address by clicking the :guilabel:`+` button." +msgstr "" + +#: ../configure_access_and_security_for_instances.rst:202 +msgid "" +"In the :guilabel:`Port to be associated` field, select a port from the list." +msgstr "" + +#: ../configure_access_and_security_for_instances.rst:205 +msgid "The list shows all the instances with their fixed IP addresses." +msgstr "" + +#: ../configure_access_and_security_for_instances.rst:207 +msgid "Click :guilabel:`Associate`." +msgstr "" + +#: ../configure_access_and_security_for_instances.rst:209 +msgid "" +"To disassociate an IP address from an instance, click the :guilabel:" +"`Disassociate` button." +msgstr "" + +#: ../configure_access_and_security_for_instances.rst:212 +msgid "" +"To release the floating IP address back into the pool of addresses, click " +"the :guilabel:`More` button and select the :guilabel:`Release Floating IP` " +"option." +msgstr "" + +#: ../create_db.rst:5 ../create_db.rst:13 +msgid "Create and access a database" +msgstr "" + +#: ../create_db.rst:6 +msgid "" +"Assume that you have installed the Database service and populated your data " +"store with images for the type and versions of databases that you want, and " +"that you can create and access a database." +msgstr "" + +#: ../create_db.rst:10 +msgid "This example shows you how to create and access a MySQL 5.5 database." +msgstr "" + +#: ../create_db.rst:15 +msgid "**Determine which flavor to use for your database**" +msgstr "" + +#: ../create_db.rst:17 +msgid "" +"When you create a database instance, you must specify a nova flavor. The " +"flavor indicates various characteristics of the instance, such as RAM, root " +"volume size, and so on. The default nova flavors are not sufficient to " +"create database instances. You might need to create or obtain some new nova " +"flavors that work for databases." +msgstr "" + +#: ../create_db.rst:23 +msgid "" +"The first step is to list flavors by using the nova ``flavor-list`` command." +msgstr "" + +#: ../create_db.rst:26 +msgid "" +"Here are the default flavors, although you may have additional custom " +"flavors in your environment:" +msgstr "" + +#: ../create_db.rst:42 +msgid "" +"Now take a look at the minimum requirements for various database instances:" +msgstr "" + +#: ../create_db.rst:46 +msgid "Database" +msgstr "" + +#: ../create_db.rst:46 +msgid "Disk (GB)" +msgstr "" + +#: ../create_db.rst:46 +msgid "RAM (MB)" +msgstr "" + +#: ../create_db.rst:46 +msgid "VCPUs" +msgstr "" + +#: ../create_db.rst:48 ../create_db.rst:50 ../create_db.rst:52 +#: ../create_db.rst:54 +msgid "1" +msgstr "" + +#: ../create_db.rst:48 ../create_db.rst:50 ../create_db.rst:52 +#: ../create_db.rst:54 +msgid "5" +msgstr "" + +#: ../create_db.rst:48 ../create_db.rst:54 +msgid "512" +msgstr "" + +#: ../create_db.rst:48 +msgid "MySQL" +msgstr "" + +#: ../create_db.rst:50 +msgid "2048" +msgstr "" + +#: ../create_db.rst:50 +msgid "Cassandra" +msgstr "" + +#: ../create_db.rst:52 +msgid "1024" +msgstr "" + +#: ../create_db.rst:52 +msgid "MongoDB" +msgstr "" + +#: ../create_db.rst:54 +msgid "Redis" +msgstr "" + +#: ../create_db.rst:57 +msgid "" +"If you have a custom flavor that meets the needs of the database that you " +"want to create, proceed to :ref:`Step 2 ` and use " +"that flavor." +msgstr "" + +#: ../create_db.rst:61 +msgid "" +"If your environment does not have a suitable flavor, an administrative user " +"must create a custom flavor by using the nova ``flavor-create`` command." +msgstr "" + +#: ../create_db.rst:65 +msgid "" +"**MySQL example. **\\ This example creates a flavor that you can use with a " +"MySQL database. This example has the following attributes:" +msgstr "" + +#: ../create_db.rst:68 +msgid "Flavor name: ``mysql_minimum``" +msgstr "" + +#: ../create_db.rst:70 +msgid "" +"Flavor ID: You must use an ID that is not already in use. In this example, " +"IDs 1 through 5 are in use, so use ID ``6``." +msgstr "" + +#: ../create_db.rst:73 +msgid "RAM: ``512``" +msgstr "" + +#: ../create_db.rst:75 +msgid "Root volume size in GB: ``5``" +msgstr "" + +#: ../create_db.rst:77 +msgid "Virtual CPUs: ``1``" +msgstr "" + +#: ../create_db.rst:90 +msgid "**Create a database instance**" +msgstr "" + +#: ../create_db.rst:92 +msgid "" +"This example creates a database instance with the following characteristics:" +msgstr "" + +#: ../create_db.rst:95 +msgid "Name of the instance: ``mysql_instance_1``" +msgstr "" + +#: ../create_db.rst:97 +msgid "Database flavor: ``6``" +msgstr "" + +#: ../create_db.rst:99 +msgid "In addition, this command specifies these options for the instance:" +msgstr "" + +#: ../create_db.rst:101 +msgid "A volume size of ``5`` (5 GB)." +msgstr "" + +#: ../create_db.rst:103 +msgid "The ``myDB`` database." +msgstr "" + +#: ../create_db.rst:105 +msgid "" +"The database is based on the ``mysql`` data store and the ``mysql-5.5`` " +"datastore\\_version." +msgstr "" + +#: ../create_db.rst:108 +msgid "The ``userA`` user with the ``password`` password." +msgstr "" + +#: ../create_db.rst:129 +msgid "**Get the IP address of the database instance**" +msgstr "" + +#: ../create_db.rst:131 +msgid "" +"First, use the trove ``list`` command to list all instances and their IDs:" +msgstr "" + +#: ../create_db.rst:143 +msgid "This command returns the instance ID of your new instance." +msgstr "" + +#: ../create_db.rst:145 +msgid "" +"You can now pass in the instance ID with the trove ``show`` command to get " +"the IP address of the instance. In this example, replace ``INSTANCE_ID`` " +"with ``5599dad6-731e-44df-bb60-488da3da9cfe``." +msgstr "" + +#: ../create_db.rst:167 +msgid "This command returns the IP address of the database instance." +msgstr "" + +#: ../create_db.rst:169 +msgid "**Access the new database**" +msgstr "" + +#: ../create_db.rst:171 +msgid "" +"You can now access the new database you just created (myDB) by using typical " +"database access commands. In this MySQL example, replace ``IP_ADDRESS`` with " +"``172.16.200.2``." +msgstr "" + +#: ../dashboard.rst:3 +msgid "OpenStack dashboard" +msgstr "" + +#: ../dashboard.rst:5 +msgid "" +"As a cloud end user, you can use the OpenStack dashboard to provision your " +"own resources within the limits set by administrators. You can modify the " +"examples provided in this section to create other types and sizes of server " +"instances." +msgstr "" + +#: ../dashboard_create_networks.rst:5 +msgid "" +"The OpenStack Networking service provides a scalable system for managing the " +"network connectivity within an OpenStack cloud deployment. It can easily and " +"quickly react to changing network needs (for example, creating and assigning " +"new IP addresses)." +msgstr "" + +#: ../dashboard_create_networks.rst:10 +msgid "" +"Networking in OpenStack is complex. This section provides the basic " +"instructions for creating a network and a router. For detailed information " +"about managing networks, refer to the `OpenStack Cloud Administrator Guide " +"`__." +msgstr "" + +#: ../dashboard_create_networks.rst:17 +msgid "Create a network" +msgstr "" + +#: ../dashboard_create_networks.rst:24 +msgid "" +"On the :guilabel:`Project` tab, open the :guilabel:`Network` tab and click :" +"guilabel:`Networks` category." +msgstr "" + +#: ../dashboard_create_networks.rst:27 +msgid "Click :guilabel:`Create Network`." +msgstr "" + +#: ../dashboard_create_networks.rst:29 +msgid "" +"In the :guilabel:`Create Network` dialog box, specify the following values." +msgstr "" + +#: ../dashboard_create_networks.rst:31 +msgid ":guilabel:`Network` tab" +msgstr "" + +#: ../dashboard_create_networks.rst:33 +msgid ":guilabel:`Network Name`: Specify a name to identify the network." +msgstr "" + +#: ../dashboard_create_networks.rst:35 +msgid ":guilabel:`Subnet` tab" +msgstr "" + +#: ../dashboard_create_networks.rst:37 +msgid ":guilabel:`Create Subnet`: Select this check box to create a subnet" +msgstr "" + +#: ../dashboard_create_networks.rst:39 +msgid "" +"You do not have to specify a subnet when you create a network, but if you do " +"not specify a subnet, any attached instance receives an Error status." +msgstr "" + +#: ../dashboard_create_networks.rst:42 +msgid ":guilabel:`Subnet Name`: Specify a name for the subnet." +msgstr "" + +#: ../dashboard_create_networks.rst:44 +msgid ":guilabel:`Network Address`: Specify the IP address for the subnet." +msgstr "" + +#: ../dashboard_create_networks.rst:46 +msgid ":guilabel:`IP Version`: Select IPv4 or IPv6." +msgstr "" + +#: ../dashboard_create_networks.rst:48 +msgid "" +":guilabel:`Gateway IP`: Specify an IP address for a specific gateway. This " +"parameter is optional." +msgstr "" + +#: ../dashboard_create_networks.rst:51 +msgid "" +":guilabel:`Disable Gateway`: Select this check box to disable a gateway IP " +"address." +msgstr "" + +#: ../dashboard_create_networks.rst:54 +msgid ":guilabel:`Subnet Detail` tab" +msgstr "" + +#: ../dashboard_create_networks.rst:56 +msgid ":guilabel:`Enable DHCP`: Select this check box to enable DHCP." +msgstr "" + +#: ../dashboard_create_networks.rst:58 +msgid ":guilabel:`Allocation Pools`: Specify IP address pools." +msgstr "" + +#: ../dashboard_create_networks.rst:60 +msgid ":guilabel:`DNS Name Servers`: Specify a name for the DNS server." +msgstr "" + +#: ../dashboard_create_networks.rst:62 +msgid ":guilabel:`Host Routes`: Specify the IP address of host routes." +msgstr "" + +# #-#-#-#-# dashboard_create_networks.pot (End User Guide 1.0.0) #-#-#-#-# +# #-#-#-#-# dashboard_manage_containers.pot (End User Guide 1.0.0) #-#-#-#-# +#: ../dashboard_create_networks.rst:64 ../dashboard_manage_containers.rst:176 +msgid "Click :guilabel:`Create`." +msgstr "" + +#: ../dashboard_create_networks.rst:66 +msgid "The dashboard shows the network on the :guilabel:`Networks` tab." +msgstr "" + +#: ../dashboard_create_networks.rst:69 +msgid "Create a router" +msgstr "" + +#: ../dashboard_create_networks.rst:76 +msgid "" +"On the :guilabel:`Project` tab, open the :guilabel:`Network` tab and click :" +"guilabel:`Routers` category." +msgstr "" + +#: ../dashboard_create_networks.rst:79 +msgid "Click :guilabel:`Create Router`." +msgstr "" + +#: ../dashboard_create_networks.rst:81 +msgid "" +"In the :guilabel:`Create Router` dialog box, specify a name for the router " +"and click :guilabel:`Create Router`." +msgstr "" + +#: ../dashboard_create_networks.rst:84 +msgid "The new router is now displayed in the :guilabel:`Routers` tab." +msgstr "" + +#: ../dashboard_create_networks.rst:86 +msgid "Click the new router's :guilabel:`Set Gateway` button." +msgstr "" + +#: ../dashboard_create_networks.rst:88 +msgid "" +"In the :guilabel:`External Network` field, specify the network to which the " +"router will connect, and then click :guilabel:`Set Gateway`." +msgstr "" + +#: ../dashboard_create_networks.rst:91 +msgid "" +"To connect a private network to the newly created router, perform the " +"following steps:" +msgstr "" + +#: ../dashboard_create_networks.rst:94 +msgid "On the :guilabel:`Routers` tab, click the name of the router." +msgstr "" + +#: ../dashboard_create_networks.rst:96 +msgid "" +"On the :guilabel:`Router Details` page, click the :guilabel:`Interfaces` " +"tab, then click :guilabel:`Add Interface`." +msgstr "" + +#: ../dashboard_create_networks.rst:99 +msgid "" +"In the :guilabel:`Add Interface` dialog box, select a :guilabel:`Subnet`." +msgstr "" + +#: ../dashboard_create_networks.rst:101 +msgid "" +"Optionally, in the :guilabel:`Add Interface` dialog box, set an :guilabel:" +"`IP Address` for the router interface for the selected subnet." +msgstr "" + +#: ../dashboard_create_networks.rst:104 +msgid "" +"If you choose not to set the :guilabel:`IP Address` value, then by default " +"OpenStack Networking uses the first host IP address in the subnet." +msgstr "" + +#: ../dashboard_create_networks.rst:108 +msgid "" +"The :guilabel:`Router Name` and :guilabel:`Router ID` fields are " +"automatically updated." +msgstr "" + +#: ../dashboard_create_networks.rst:111 +msgid "Click :guilabel:`Add Interface`." +msgstr "" + +#: ../dashboard_create_networks.rst:113 +msgid "" +"You have successfully created the router. You can view the new topology from " +"the :guilabel:`Network Topology` tab." +msgstr "" + +# #-#-#-#-# dashboard_databases.pot (End User Guide 1.0.0) #-#-#-#-# +# #-#-#-#-# trove-manage-db.pot (End User Guide 1.0.0) #-#-#-#-# +#: ../dashboard_databases.rst:3 ../trove-manage-db.rst:3 +msgid "Create and manage databases" +msgstr "" + +# #-#-#-#-# dashboard_databases.pot (End User Guide 1.0.0) #-#-#-#-# +# #-#-#-#-# trove-manage-db.pot (End User Guide 1.0.0) #-#-#-#-# +#: ../dashboard_databases.rst:5 ../trove-manage-db.rst:4 +msgid "" +"The Database service provides scalable and reliable cloud provisioning " +"functionality for both relational and non-relational database engines. Users " +"can quickly and easily use database features without the burden of handling " +"complex administrative tasks." +msgstr "" + +#: ../dashboard_databases.rst:13 +msgid "Create a database instance" +msgstr "" + +#: ../dashboard_databases.rst:15 +msgid "" +"**Prerequisites. **\\ Before you create a database instance, you need to " +"configure a default datastore and make sure you have an appropriate flavor " +"for the type of database instance you want." +msgstr "" + +#: ../dashboard_databases.rst:19 +msgid "**Configure a default datastore.**" +msgstr "" + +#: ../dashboard_databases.rst:21 +msgid "" +"Because the dashboard does not let you choose a specific datastore to use " +"with an instance, you need to configure a default datastore. The dashboard " +"then uses the default datastore to create the instance." +msgstr "" + +#: ../dashboard_databases.rst:25 +msgid "Add the following line to ``/etc/trove/trove.conf``:" +msgstr "" + +#: ../dashboard_databases.rst:31 +msgid "" +"Replace *``DATASTORE_NAME``* with the name that the administrative user set " +"when issuing the **trove-manage** command to create the datastore. You can " +"use the trove **datastore-list** command to display the datastores that are " +"available in your environment." +msgstr "" + +#: ../dashboard_databases.rst:36 +msgid "" +"For example, if your MySQL datastore name is set to ``mysql``, your entry " +"would look like this:" +msgstr "" + +#: ../dashboard_databases.rst:43 +msgid "Restart Database services on the controller node:" +msgstr "" + +#: ../dashboard_databases.rst:51 +msgid "**Verify flavor.**" +msgstr "" + +#: ../dashboard_databases.rst:53 +msgid "" +"Make sure an appropriate flavor exists for the type of database instance you " +"want." +msgstr "" + +#: ../dashboard_databases.rst:56 +msgid "" +"**Create database instance. **\\ Once you have configured a default " +"datastore and verified that you have an appropriate flavor, you can create a " +"database instance." +msgstr "" + +#: ../dashboard_databases.rst:65 +msgid "" +"On the :guilabel:`Project` tab, open the :guilabel:`Database` tab and click :" +"guilabel:`Instances` category. This lists the instances that already exist " +"in your environment." +msgstr "" + +#: ../dashboard_databases.rst:69 +msgid "Click :guilabel:`Launch Instance`." +msgstr "" + +#: ../dashboard_databases.rst:71 +msgid "" +"In the :guilabel:`Launch Database` dialog box, specify the following values." +msgstr "" + +#: ../dashboard_databases.rst:73 +msgid "Details" +msgstr "" + +#: ../dashboard_databases.rst:75 +msgid ":guilabel:`Database Name`: Specify a name for the database instance." +msgstr "" + +#: ../dashboard_databases.rst:77 +msgid ":guilabel:`Flavor`: Select an appropriate flavor for the instance." +msgstr "" + +#: ../dashboard_databases.rst:79 +msgid "" +":guilabel:`Volume Size`: Select a volume size. Volume size is expressed in " +"GB." +msgstr "" + +#: ../dashboard_databases.rst:82 +msgid ":guilabel:`Initialize Databases`: Initial Database" +msgstr "" + +#: ../dashboard_databases.rst:84 +msgid "" +"Optionally provide a comma separated list of databases to create, for " +"example:" +msgstr "" + +#: ../dashboard_databases.rst:87 +msgid "``database1``, ``database2``, ``database3``" +msgstr "" + +#: ../dashboard_databases.rst:89 +msgid "" +":guilabel:`Initial Admin User`: Create an initial admin user. This user will " +"have access to all the databases you create." +msgstr "" + +#: ../dashboard_databases.rst:92 +msgid "" +":guilabel:`Password`: Specify a password associated with the initial admin " +"user you just named." +msgstr "" + +#: ../dashboard_databases.rst:95 +msgid "" +":guilabel:`Host`: Optionally, allow the user to connect only from this host. " +"If you do not specify a host, this user will be allowed to connect from " +"anywhere." +msgstr "" + +#: ../dashboard_databases.rst:99 +msgid "" +"Click the :guilabel:`Launch` button. The new database instance appears in " +"the databases list." +msgstr "" + +#: ../dashboard_databases.rst:113 +msgid "To backup the database instance" +msgstr "" + +#: ../dashboard_databases.rst:120 ../dashboard_databases.rst:180 +#: ../dashboard_databases.rst:203 +msgid "" +"On the :guilabel:`Project` tab, open the :guilabel:`Database` tab and click :" +"guilabel:`Instances` category. This displays the existing instances in your " +"system." +msgstr "" + +#: ../dashboard_databases.rst:124 +msgid "Click :guilabel:`Create Backup`." +msgstr "" + +#: ../dashboard_databases.rst:126 +msgid "" +"In the :guilabel:`Backup Database` dialog box, specify the following values:" +msgstr "" + +#: ../dashboard_databases.rst:129 +msgid "Name" +msgstr "" + +#: ../dashboard_databases.rst:131 +msgid "Specify a name for the backup." +msgstr "" + +#: ../dashboard_databases.rst:133 +msgid "Database Instance" +msgstr "" + +#: ../dashboard_databases.rst:135 +msgid "Select the instance you want to back up." +msgstr "" + +#: ../dashboard_databases.rst:137 +msgid "Click :guilabel:`Backup`. The new backup appears in the backup list." +msgstr "" + +#: ../dashboard_databases.rst:140 +msgid "To restore a database instance" +msgstr "" + +#: ../dashboard_databases.rst:142 +msgid "" +"Now assume that your original database instance is damaged and you need to " +"restore it. You do the restore by using your backup to create a new database " +"instance." +msgstr "" + +#: ../dashboard_databases.rst:151 +msgid "" +"On the :guilabel:`Project` tab, open the :guilabel:`Database` tab and click :" +"guilabel:`Backups` category. This lists the available backups." +msgstr "" + +#: ../dashboard_databases.rst:154 +msgid "Check the backup you want to use and click :guilabel:`Restore Backup`." +msgstr "" + +#: ../dashboard_databases.rst:156 +msgid "" +"In the :guilabel:`Launch Database` dialog box, specify the values you want " +"for the new database instance." +msgstr "" + +#: ../dashboard_databases.rst:159 +msgid "" +"Click the :guilabel:`Restore From Database` tab and make sure that this new " +"instance is based on the correct backup." +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:162 +msgid "Click :guilabel:`Launch`." +msgstr "" + +#: ../dashboard_databases.rst:164 +msgid "The new instance appears in the database instances list." +msgstr "" + +#: ../dashboard_databases.rst:167 +msgid "Update a database instance" +msgstr "" + +#: ../dashboard_databases.rst:169 +msgid "" +"You can change various characteristics of a database instance, such as its " +"volume size and flavor." +msgstr "" + +#: ../dashboard_databases.rst:173 +msgid "To change the volume size of an instance" +msgstr "" + +#: ../dashboard_databases.rst:184 +msgid "" +"Check the instance you want to work with. In the :guilabel:`Actions` column, " +"expand the drop down menu and select :guilabel:`Resize Volume`." +msgstr "" + +#: ../dashboard_databases.rst:188 +msgid "" +"In the :guilabel:`Resize Database Volume` dialog box, fill in the :guilabel:" +"`New Size` field with an integer indicating the new size you want for the " +"instance. Express the size in GB, and note that the new size must be larger " +"than the current size." +msgstr "" + +#: ../dashboard_databases.rst:193 +msgid "Click :guilabel:`Resize Database Volume`." +msgstr "" + +#: ../dashboard_databases.rst:196 +msgid "To change the flavor of an instance" +msgstr "" + +#: ../dashboard_databases.rst:207 +msgid "" +"Check the instance you want to work with. In the :guilabel:`Actions` column, " +"expand the drop down menu and select :guilabel:`Resize Instance`." +msgstr "" + +#: ../dashboard_databases.rst:211 +msgid "" +"In the :guilabel:`Resize Database Instance` dialog box, expand the drop down " +"menu in the :guilabel:`New Flavor` field. Select the new flavor you want for " +"the instance." +msgstr "" + +#: ../dashboard_databases.rst:215 +msgid "Click :guilabel:`Resize Database Instance`." +msgstr "" + +#: ../dashboard_launch_instances.rst:3 +msgid "Launch and manage instances" +msgstr "" + +#: ../dashboard_launch_instances.rst:4 +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." +msgstr "" + +#: ../dashboard_launch_instances.rst:9 +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 " +"iSCSI." +msgstr "" + +#: ../dashboard_launch_instances.rst:14 +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:38 ../dashboard_manage_images.rst:32 +#: ../dashboard_manage_images.rst:99 ../dashboard_manage_images.rst:129 +msgid "" +"On the :guilabel:`Project` tab, open the :guilabel:`Compute` tab and click :" +"guilabel:`Images` category." +msgstr "" + +#: ../dashboard_launch_instances.rst:41 +msgid "" +"The dashboard shows the images that have been uploaded to OpenStack Image " +"service and are available for this project." +msgstr "" + +#: ../dashboard_launch_instances.rst:44 +msgid "" +"For details on creating images, see `Creating images manually `__ in " +"the *OpenStack Virtual Machine Image Guide*." +msgstr "" + +#: ../dashboard_launch_instances.rst:48 +msgid "Select an image and click :guilabel:`Launch Instance`." +msgstr "" + +#: ../dashboard_launch_instances.rst:50 +msgid "" +"In the :guilabel:`Launch Instance` dialog box, specify the following values:" +msgstr "" + +#: ../dashboard_launch_instances.rst:52 +msgid ":guilabel:`Details` tab" +msgstr "" + +#: ../dashboard_launch_instances.rst:55 +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:57 +msgid "Availability Zone" +msgstr "" + +#: ../dashboard_launch_instances.rst:60 +msgid "Assign a name to the virtual machine." +msgstr "" + +#: ../dashboard_launch_instances.rst:62 +msgid "The name you assign here becomes the initial host name of the server." +msgstr "" + +#: ../dashboard_launch_instances.rst:65 +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:69 +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:70 +msgid "Instance Name" +msgstr "" + +#: ../dashboard_launch_instances.rst:73 +msgid "Specify the size of the instance to launch." +msgstr "" + +#: ../dashboard_launch_instances.rst:75 +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 " +"value in the :guilabel:`Minimum RAM (MB)` field as 2048, then on selecting " +"the image, the default flavor is ``m1.small``." +msgstr "" + +#: ../dashboard_launch_instances.rst:79 +msgid "Flavor" +msgstr "" + +#: ../dashboard_launch_instances.rst:82 +msgid "" +"To launch multiple instances, enter a value greater than ``1``. The default " +"is ``1``." +msgstr "" + +#: ../dashboard_launch_instances.rst:83 +msgid "Instance Count" +msgstr "" + +#: ../dashboard_launch_instances.rst:86 +msgid "Your options are:" +msgstr "" + +#: ../dashboard_launch_instances.rst:89 +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:90 +msgid "Boot from image" +msgstr "" + +#: ../dashboard_launch_instances.rst:93 +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:94 +msgid "Boot from snapshot" +msgstr "" + +#: ../dashboard_launch_instances.rst:97 +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:98 +msgid "Boot from volume" +msgstr "" + +#: ../dashboard_launch_instances.rst:101 +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. " +"Click the :guilabel:`Delete on Terminate` option to delete the volume on " +"terminating the instance." +msgstr "" + +#: ../dashboard_launch_instances.rst:104 +msgid "Boot from image (creates a new volume)" +msgstr "" + +#: ../dashboard_launch_instances.rst:107 +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 :" +"guilabel:`Device Name` for your volume. Click the :guilabel:`Delete on " +"Terminate` option to delete the volume on terminating the instance." +msgstr "" + +#: ../dashboard_launch_instances.rst:111 +msgid "Boot from volume snapshot (creates a new volume)" +msgstr "" + +#: ../dashboard_launch_instances.rst:113 +msgid "" +"Since you are launching an instance from an image, :guilabel:`Boot from " +"image` is chosen by default." +msgstr "" + +#: ../dashboard_launch_instances.rst:114 +msgid "Instance Boot Source" +msgstr "" + +#: ../dashboard_launch_instances.rst:117 +msgid "" +"This field changes based on your previous selection. Since 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:119 +msgid "Image Name" +msgstr "" + +#: ../dashboard_launch_instances.rst:121 +msgid ":guilabel:`Access & Security` tab" +msgstr "" + +#: ../dashboard_launch_instances.rst:124 +msgid "Specify a key pair." +msgstr "" + +#: ../dashboard_launch_instances.rst:126 +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:128 +msgid "Keypair" +msgstr "" + +#: ../dashboard_launch_instances.rst:131 +msgid "Activate the security groups that you want to assign to the instance." +msgstr "" + +#: ../dashboard_launch_instances.rst:133 +msgid "" +"Security groups are a kind of cloud firewall that define which incoming " +"network traffic is forwarded to instances." +msgstr "" + +#: ../dashboard_launch_instances.rst:136 +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:137 +msgid "Security Groups" +msgstr "" + +#: ../dashboard_launch_instances.rst:139 +msgid ":guilabel:`Networking` tab" +msgstr "" + +#: ../dashboard_launch_instances.rst:142 +msgid "" +"To add a network to the instance, click the :guilabel:`+` in the :guilabel:" +"`Available Networks` field." +msgstr "" + +#: ../dashboard_launch_instances.rst:143 +msgid "Selected Networks" +msgstr "" + +#: ../dashboard_launch_instances.rst:145 +msgid ":guilabel:`Post-Creation` tab" +msgstr "" + +#: ../dashboard_launch_instances.rst:148 +msgid "Specify a customization script that runs after your instance launches." +msgstr "" + +#: ../dashboard_launch_instances.rst:149 +msgid "Customization Script" +msgstr "" + +#: ../dashboard_launch_instances.rst:151 +msgid ":guilabel:`Advanced Options` tab" +msgstr "" + +#: ../dashboard_launch_instances.rst:154 +msgid "Select the type of disk partition from the dropdown list:" +msgstr "" + +#: ../dashboard_launch_instances.rst:157 +msgid "Automatic" +msgstr "" + +#: ../dashboard_launch_instances.rst:157 +msgid "Entire disk is single partition and automatically resizes." +msgstr "" + +#: ../dashboard_launch_instances.rst:160 +msgid "Disk Partition" +msgstr "" + +#: ../dashboard_launch_instances.rst:160 +msgid "Faster build times but requires manual partitioning." +msgstr "" + +#: ../dashboard_launch_instances.rst:160 +msgid "Manual" +msgstr "" + +#: ../dashboard_launch_instances.rst:164 +msgid "The instance starts on a compute node in the cloud." +msgstr "" + +#: ../dashboard_launch_instances.rst:166 +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:169 +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:174 +msgid "Connect to your instance by using SSH" +msgstr "" + +#: ../dashboard_launch_instances.rst:176 +msgid "" +"To use SSH to connect to your instance, you use the downloaded keypair file." +msgstr "" + +#: ../dashboard_launch_instances.rst:179 +msgid "The user name is ``ubuntu`` for the Ubuntu cloud images on TryStack." +msgstr "" + +#: ../dashboard_launch_instances.rst:181 +msgid "Copy the IP address for your instance." +msgstr "" + +#: ../dashboard_launch_instances.rst:183 +msgid "" +"Use the :command:`ssh` command to make a secure connection to the instance. " +"For example::" +msgstr "" + +#: ../dashboard_launch_instances.rst:188 +msgid "At the prompt, type ``yes``." +msgstr "" + +#: ../dashboard_launch_instances.rst:191 +msgid "Track usage for instances" +msgstr "" + +#: ../dashboard_launch_instances.rst:193 +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:202 +msgid "" +"On the :guilabel:`Project` tab, open the :guilabel:`Compute` tab and click :" +"guilabel:`Overview` category." +msgstr "" + +#: ../dashboard_launch_instances.rst:205 +msgid "" +"To query the instance usage for a month, select a month and click :guilabel:" +"`Submit`." +msgstr "" + +#: ../dashboard_launch_instances.rst:208 +msgid "To download a summary, click :guilabel:`Download CSV Summary`." +msgstr "" + +#: ../dashboard_launch_instances.rst:213 +msgid "" +"Log in to the dashboard, choose a project, and click :guilabel:`Instances`." +msgstr "" + +#: ../dashboard_launch_instances.rst:215 +msgid "Select the instance from which to create a snapshot." +msgstr "" + +#: ../dashboard_launch_instances.rst:217 +msgid "In the :guilabel:`Actions` column, click :guilabel:`Create Snapshot`." +msgstr "" + +#: ../dashboard_launch_instances.rst:219 +msgid "" +"In the :guilabel:`Create Snapshot` dialog box, enter a name for the " +"snapshot, and click :guilabel:`Create Snapshot`." +msgstr "" + +#: ../dashboard_launch_instances.rst:222 +msgid "The Images category shows the instance snapshot." +msgstr "" + +#: ../dashboard_launch_instances.rst:224 +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:228 +msgid "Manage an instance" +msgstr "" + +#: ../dashboard_launch_instances.rst:235 +msgid "" +"On the :guilabel:`Project` tab, open the :guilabel:`Compute` tab and click :" +"guilabel:`Instances` category." +msgstr "" + +#: ../dashboard_launch_instances.rst:238 +msgid "Select an instance." +msgstr "" + +#: ../dashboard_launch_instances.rst:240 +msgid "" +"In the :guilabel:`More` list in the :guilabel:`Actions` column, select the " +"state." +msgstr "" + +#: ../dashboard_launch_instances.rst:243 +msgid "" +"You can resize or rebuild an instance. You can also choose to view the " +"instance console log, edit instance or the security groups. Depending on the " +"current state of the instance, you can pause, resume, suspend, soft or hard " +"reboot, or terminate it." +msgstr "" + +#: ../dashboard_manage_containers.rst:3 +msgid "Create and manage object containers" +msgstr "" + +#: ../dashboard_manage_containers.rst:5 +msgid "" +"OpenStack Object Storage provides a distributed, API-accessible storage " +"platform that can be integrated directly into an application or used to " +"store any type of file, including VM images, backups, archives, or media " +"files. In the OpenStack dashboard, you can only manage containers and " +"objects." +msgstr "" + +#: ../dashboard_manage_containers.rst:11 +msgid "" +"In OpenStack Object Storage, containers provide storage for objects in a " +"manner similar to a Windows folder or Linux file directory, though they " +"cannot be nested. An object in OpenStack consists of the file to be stored " +"in the container and any accompanying metadata." +msgstr "" + +#: ../dashboard_manage_containers.rst:17 +msgid "Create a container" +msgstr "" + +#: ../dashboard_manage_containers.rst:24 ../dashboard_manage_containers.rst:45 +#: ../dashboard_manage_containers.rst:78 +#: ../dashboard_manage_containers.rst:101 +#: ../dashboard_manage_containers.rst:132 +#: ../dashboard_manage_containers.rst:160 +msgid "" +"On the :guilabel:`Project` tab, open the :guilabel:`Object Store` tab and " +"click :guilabel:`Containers` category." +msgstr "" + +#: ../dashboard_manage_containers.rst:27 +msgid "Click :guilabel:`Create Container`." +msgstr "" + +#: ../dashboard_manage_containers.rst:29 +msgid "" +"In the :guilabel:`Create Container` dialog box, enter a name for the " +"container, and then click :guilabel:`Create Container`." +msgstr "" + +#: ../dashboard_manage_containers.rst:32 +msgid "You have successfully created a container." +msgstr "" + +#: ../dashboard_manage_containers.rst:34 +msgid "" +"To delete a container, click the :guilabel:`More` button and select :" +"guilabel:`Delete Container`." +msgstr "" + +#: ../dashboard_manage_containers.rst:38 +msgid "Upload an object" +msgstr "" + +#: ../dashboard_manage_containers.rst:48 ../dashboard_manage_containers.rst:81 +#: ../dashboard_manage_containers.rst:104 +#: ../dashboard_manage_containers.rst:135 +#: ../dashboard_manage_containers.rst:163 +msgid "Select the container in which you want to store your object." +msgstr "" + +#: ../dashboard_manage_containers.rst:50 ../dashboard_manage_containers.rst:61 +#: ../dashboard_manage_containers.rst:137 +msgid "Click :guilabel:`Upload Object`." +msgstr "" + +#: ../dashboard_manage_containers.rst:52 +msgid "" +"The :guilabel:`Upload Object To Container: ` dialog box appears. " +"*````* is the name of the container to which you are uploading the " +"object." +msgstr "" + +#: ../dashboard_manage_containers.rst:57 +#: ../dashboard_manage_containers.rst:145 +msgid "Enter a name for the object." +msgstr "" + +#: ../dashboard_manage_containers.rst:59 ../dashboard_manage_containers.rst:87 +msgid "Browse to and select the file that you want to upload." +msgstr "" + +#: ../dashboard_manage_containers.rst:63 +msgid "You have successfully uploaded an object to the container." +msgstr "" + +#: ../dashboard_manage_containers.rst:65 +msgid "" +"To delete an object, click the :guilabel:`More button` and select :guilabel:" +"`Delete Object`." +msgstr "" + +#: ../dashboard_manage_containers.rst:69 +msgid "Manage an object" +msgstr "" + +#: ../dashboard_manage_containers.rst:71 +msgid "**To edit an object**" +msgstr "" + +#: ../dashboard_manage_containers.rst:83 +msgid "" +"Click :guilabel:`More` and choose :guilabel:`Edit` from the dropdown list." +msgstr "" + +#: ../dashboard_manage_containers.rst:85 +msgid "The :guilabel:`Edit Object` dialog box is displayed." +msgstr "" + +#: ../dashboard_manage_containers.rst:89 +#: ../dashboard_manage_containers.rst:147 +msgid "Click :guilabel:`Update Object`." +msgstr "" + +#: ../dashboard_manage_containers.rst:91 +msgid "" +"To delete an object, click the :guilabel:`More` button and select :guilabel:" +"`Delete Object`." +msgstr "" + +#: ../dashboard_manage_containers.rst:94 +msgid "**To copy an object from one container to another**" +msgstr "" + +#: ../dashboard_manage_containers.rst:106 +msgid "" +"Click :guilabel:`More` and choose :guilabel:`Copy` from the dropdown list." +msgstr "" + +#: ../dashboard_manage_containers.rst:108 +msgid "" +"In the :guilabel:`Copy Object` launch dialog box, enter the following values:" +msgstr "" + +#: ../dashboard_manage_containers.rst:111 +msgid "" +":guilabel:`Destination Container`: Choose the destination container from the " +"list." +msgstr "" + +#: ../dashboard_manage_containers.rst:113 +msgid "" +":guilabel:`Path`: Specify a path in which the new copy should be stored " +"inside of the selected container." +msgstr "" + +#: ../dashboard_manage_containers.rst:115 +msgid "" +":guilabel:`Destination object name`: Enter a name for the object in the new " +"container." +msgstr "" + +#: ../dashboard_manage_containers.rst:118 +msgid "Click :guilabel:`Copy Object`." +msgstr "" + +#: ../dashboard_manage_containers.rst:120 +msgid "**To create a metadata-only object without a file**" +msgstr "" + +#: ../dashboard_manage_containers.rst:122 +msgid "" +"You can create a new object in container without a file available and can " +"upload the file later when it is ready. This temporary object acts a place-" +"holder for a new object, and enables the user to share object metadata and " +"URL info in advance." +msgstr "" + +#: ../dashboard_manage_containers.rst:139 +msgid "" +"The :guilabel:`Upload Object To Container`: *````* dialog box is " +"displayed." +msgstr "" + +#: ../dashboard_manage_containers.rst:142 +msgid "" +"*````* is the name of the container to which you are uploading the " +"object." +msgstr "" + +#: ../dashboard_manage_containers.rst:149 +msgid "**To create a pseudo-folder**" +msgstr "" + +#: ../dashboard_manage_containers.rst:151 +msgid "" +"Pseudo-folders are similar to folders in your desktop operating system. They " +"are virtual collections defined by a common prefix on the object's name." +msgstr "" + +#: ../dashboard_manage_containers.rst:165 +msgid "Click :guilabel:`Create Pseudo-folder`." +msgstr "" + +#: ../dashboard_manage_containers.rst:167 +msgid "" +"The :guilabel:`Create Pseudo-Folder in Container` *`` ``* dialog box " +"is displayed. *`` ``* is the name of the container to which you are " +"uploading the object." +msgstr "" + +#: ../dashboard_manage_containers.rst:171 +msgid "Enter a name for the pseudo-folder." +msgstr "" + +#: ../dashboard_manage_containers.rst:173 +msgid "" +"A slash (/) character is used as the delimiter for pseudo-folders in Object " +"Storage." +msgstr "" + +#: ../dashboard_manage_images.rst:3 +msgid "Upload and manage images" +msgstr "" + #: ../dashboard_manage_images.rst:5 msgid "" "A virtual machine image, referred to in this document simply as an image, is " @@ -969,30 +6173,1451 @@ msgid "" "guide/content/>`_." msgstr "" -#: ../create_db.rst:101 -msgid "A volume size of ``5`` (5 GB)." +#: ../dashboard_manage_images.rst:12 +msgid "" +"Depending on your role, you may have permission to upload and manage virtual " +"machine images. Operators might restrict the upload and management of images " +"to cloud administrators or operators only. If you have the appropriate " +"privileges, you can use the dashboard to upload and manage images in the " +"admin project." +msgstr "" + +#: ../dashboard_manage_images.rst:18 +msgid "" +"You can also use the :command:`glance` and :command:`nova` command-line " +"clients or the Image service and Compute APIs to manage images." +msgstr "" + +# #-#-#-#-# dashboard_manage_images.pot (End User Guide 1.0.0) #-#-#-#-# +# #-#-#-#-# sdk_manage_images.pot (End User Guide 1.0.0) #-#-#-#-# +#: ../dashboard_manage_images.rst:23 ../sdk_manage_images.rst:120 +msgid "Upload an image" +msgstr "" + +#: ../dashboard_manage_images.rst:25 +msgid "Follow this procedure to upload an image to a project:" +msgstr "" + +#: ../dashboard_manage_images.rst:35 ../dashboard_manage_images.rst:84 +msgid "Click :guilabel:`Create Image`." +msgstr "" + +#: ../dashboard_manage_images.rst:37 +msgid "The :guilabel:`Create An Image` dialog box appears." +msgstr "" + +#: ../dashboard_manage_images.rst:39 +msgid "Enter the following values:" +msgstr "" + +#: ../dashboard_manage_images.rst:42 +msgid ":guilabel:`Name`" +msgstr "" + +#: ../dashboard_manage_images.rst:42 +msgid "Enter a name for the image." +msgstr "" + +#: ../dashboard_manage_images.rst:44 +msgid ":guilabel:`Description`" +msgstr "" + +#: ../dashboard_manage_images.rst:44 +msgid "Enter a brief description of the image." +msgstr "" + +#: ../dashboard_manage_images.rst:47 +msgid ":guilabel:`Image Source`" +msgstr "" + +#: ../dashboard_manage_images.rst:47 +msgid "" +"Choose the image source from the dropdown list. Your choices are :guilabel:" +"`Image Location` and :guilabel:`Image File`." +msgstr "" + +#: ../dashboard_manage_images.rst:52 +msgid ":guilabel:`Image File` or :guilabel:`Image Location`" +msgstr "" + +#: ../dashboard_manage_images.rst:52 +msgid "" +"Based on your selection for :guilabel:`Image Source`, you either enter the " +"location URL of the image in the :guilabel:`Image Location` field, or browse " +"for the image file on your file system and add it." +msgstr "" + +#: ../dashboard_manage_images.rst:61 +msgid ":guilabel:`Format`" +msgstr "" + +#: ../dashboard_manage_images.rst:61 +msgid "Select the image format (for example, QCOW2) for the image." +msgstr "" + +#: ../dashboard_manage_images.rst:64 +msgid ":guilabel:`Architecture`" +msgstr "" + +#: ../dashboard_manage_images.rst:64 +msgid "" +"Specify the architecture. For example, ``i386`` for a 32-bit architecture or " +"``x86_64`` for a 64-bit architecture." +msgstr "" + +#: ../dashboard_manage_images.rst:69 +msgid ":guilabel:`Minimum Disk (GB)` and :guilabel:`Minimum RAM (MB)`" +msgstr "" + +#: ../dashboard_manage_images.rst:69 +msgid "Leave these fields empty." +msgstr "" + +#: ../dashboard_manage_images.rst:73 +msgid ":guilabel:`Public`" +msgstr "" + +#: ../dashboard_manage_images.rst:73 +msgid "" +"Select this check box to make the image public to all users with access to " +"the current project." +msgstr "" + +#: ../dashboard_manage_images.rst:78 +msgid ":guilabel:`Protected`" +msgstr "" + +#: ../dashboard_manage_images.rst:78 +msgid "" +"Select this check box to ensure that only users with permissions can delete " +"the image." +msgstr "" + +#: ../dashboard_manage_images.rst:86 +msgid "" +"The image is queued to be uploaded. It might take some time before the " +"status changes from Queued to Active." +msgstr "" + +#: ../dashboard_manage_images.rst:90 +msgid "Update an image" +msgstr "" + +#: ../dashboard_manage_images.rst:92 +msgid "Follow this procedure to update an existing image." +msgstr "" + +# #-#-#-#-# dashboard_manage_images.pot (End User Guide 1.0.0) #-#-#-#-# +# #-#-#-#-# dashboard_manage_volumes.pot (End User Guide 1.0.0) #-#-#-#-# +#: ../dashboard_manage_images.rst:102 ../dashboard_manage_volumes.rst:144 +msgid "Select the image that you want to edit." +msgstr "" + +#: ../dashboard_manage_images.rst:104 +msgid "" +"In the :guilabel:`Actions` column, click :guilabel:`More` and then select :" +"guilabel:`Edit Image` from the list." +msgstr "" + +#: ../dashboard_manage_images.rst:107 +msgid "" +"In the :guilabel:`Update Image` dialog box, you can perform the following " +"actions:" +msgstr "" + +#: ../dashboard_manage_images.rst:110 +msgid "Change the name of the image." +msgstr "" + +#: ../dashboard_manage_images.rst:112 +msgid "Select the :guilabel:`Public` check box to make the image public." +msgstr "" + +#: ../dashboard_manage_images.rst:114 +msgid "Clear the :guilabel:`Public` check box to make the image private." +msgstr "" + +#: ../dashboard_manage_images.rst:116 +msgid "Click :guilabel:`Update Image`." +msgstr "" + +#: ../dashboard_manage_images.rst:119 +msgid "Delete an image" +msgstr "" + +#: ../dashboard_manage_images.rst:121 +msgid "" +"Deletion of images is permanent and **cannot** be reversed. Only users with " +"the appropriate permissions can delete images." +msgstr "" + +#: ../dashboard_manage_images.rst:132 +msgid "Select the images that you want to delete." +msgstr "" + +#: ../dashboard_manage_images.rst:134 +msgid "Click :guilabel:`Delete Images`." +msgstr "" + +#: ../dashboard_manage_images.rst:136 +msgid "" +"In the :guilabel:`Confirm Delete Images` dialog box, click :guilabel:`Delete " +"Images` to confirm the deletion." +msgstr "" + +#: ../dashboard_manage_shares.rst:3 +msgid "Create and manage shares" +msgstr "" + +#: ../dashboard_manage_shares.rst:5 +msgid "" +"Shares are file storage that you provide access to instances. You can allow " +"access to a share to a running instance or deny access to a share and allow " +"access to it to another instance at any time. You can also delete a share. " +"You can create snapshot from a share if the driver supports it. Only " +"administrative users can create share types." +msgstr "" + +#: ../dashboard_manage_shares.rst:12 +msgid "Create a share" +msgstr "" + +#: ../dashboard_manage_shares.rst:14 ../dashboard_manage_shares.rst:42 +#: ../dashboard_manage_shares.rst:53 ../dashboard_manage_shares.rst:73 +#: ../dashboard_manage_shares.rst:87 ../dashboard_manage_shares.rst:102 +#: ../dashboard_manage_shares.rst:118 +msgid "" +"Log in to the dashboard, choose a project, and click :guilabel:`Shares`." +msgstr "" + +#: ../dashboard_manage_shares.rst:16 ../dashboard_manage_shares.rst:35 +msgid "Click :guilabel:`Create Share`." +msgstr "" + +# #-#-#-#-# dashboard_manage_shares.pot (End User Guide 1.0.0) #-#-#-#-# +# #-#-#-#-# dashboard_manage_volumes.pot (End User Guide 1.0.0) #-#-#-#-# +#: ../dashboard_manage_shares.rst:18 ../dashboard_manage_shares.rst:137 +#: ../dashboard_manage_shares.rst:189 ../dashboard_manage_volumes.rst:24 +msgid "In the dialog box that opens, enter or select the following values." +msgstr "" + +#: ../dashboard_manage_shares.rst:20 +msgid ":guilabel:`Share Name`: Specify a name for the share." +msgstr "" + +#: ../dashboard_manage_shares.rst:22 +msgid "" +":guilabel:`Description`: Optionally, provide a brief description for the " +"share." +msgstr "" + +#: ../dashboard_manage_shares.rst:25 +msgid ":guilabel:`Share Type`: Choose a share type." +msgstr "" + +#: ../dashboard_manage_shares.rst:27 +msgid ":guilabel:`Size (GB)`: The size of the share in gibibytes (GiB)." +msgstr "" + +#: ../dashboard_manage_shares.rst:29 +msgid ":guilabel:`Share Protocol`: Select NFS, CIFS, GlusterFS, or HDFS." +msgstr "" + +#: ../dashboard_manage_shares.rst:31 +msgid ":guilabel:`Share Network`: Choose a share network." +msgstr "" + +#: ../dashboard_manage_shares.rst:33 +msgid ":guilabel:`Metadata`: Enter metadata for the share creation if needed." +msgstr "" + +#: ../dashboard_manage_shares.rst:37 +msgid "The dashboard shows the share on the :guilabel:`Shares` tab." +msgstr "" + +#: ../dashboard_manage_shares.rst:40 +msgid "Delete a share" +msgstr "" + +#: ../dashboard_manage_shares.rst:44 +msgid "Select the check boxes for the shares that you want to delete." +msgstr "" + +#: ../dashboard_manage_shares.rst:46 +msgid "Click :guilabel:`Delete Shares` and confirm your choice." +msgstr "" + +# #-#-#-#-# dashboard_manage_shares.pot (End User Guide 1.0.0) #-#-#-#-# +# #-#-#-#-# dashboard_manage_volumes.pot (End User Guide 1.0.0) #-#-#-#-# +#: ../dashboard_manage_shares.rst:48 ../dashboard_manage_shares.rst:68 +#: ../dashboard_manage_shares.rst:82 ../dashboard_manage_shares.rst:97 +#: ../dashboard_manage_shares.rst:113 ../dashboard_manage_shares.rst:127 +#: ../dashboard_manage_shares.rst:162 ../dashboard_manage_shares.rst:179 +#: ../dashboard_manage_shares.rst:225 ../dashboard_manage_shares.rst:242 +#: ../dashboard_manage_volumes.rst:104 ../dashboard_manage_volumes.rst:175 +msgid "A message indicates whether the action was successful." +msgstr "" + +#: ../dashboard_manage_shares.rst:51 +msgid "Allow access" +msgstr "" + +#: ../dashboard_manage_shares.rst:55 +msgid "" +"Go to the share that you want to allow access and choose :guilabel:`Manage " +"Rules` from Actions." +msgstr "" + +#: ../dashboard_manage_shares.rst:58 +msgid "Click :guilabel:`Add rule`." +msgstr "" + +#: ../dashboard_manage_shares.rst:60 +msgid ":guilabel:`Access Type`: Choose ip, user, or cert." +msgstr "" + +#: ../dashboard_manage_shares.rst:62 +msgid ":guilabel:`Access Level`: Choose read-write or read-only." +msgstr "" + +#: ../dashboard_manage_shares.rst:64 +msgid ":guilabel:`Access To`: Fill in Access To field." +msgstr "" + +#: ../dashboard_manage_shares.rst:66 +msgid "Click :guilabel:`Add Rule`." +msgstr "" + +#: ../dashboard_manage_shares.rst:71 +msgid "Deny access" +msgstr "" + +#: ../dashboard_manage_shares.rst:75 +msgid "" +"Go to the share that you want to deny access and choose :guilabel:`Manage " +"Rules` from Actions." +msgstr "" + +#: ../dashboard_manage_shares.rst:78 +msgid "Choose the rule you want to delete." +msgstr "" + +#: ../dashboard_manage_shares.rst:80 +msgid "Click :guilabel:`Delete rule` and confirm your choice." +msgstr "" + +#: ../dashboard_manage_shares.rst:85 +msgid "Edit share metadata" +msgstr "" + +#: ../dashboard_manage_shares.rst:89 +msgid "" +"Go to the share that you want to edit and choose :guilabel:`Edit Share " +"Metadata` from Actions." +msgstr "" + +#: ../dashboard_manage_shares.rst:92 +msgid "" +":guilabel:`Metadata`: To add share metadata, use key=value. To unset " +"metadata, use key." +msgstr "" + +#: ../dashboard_manage_shares.rst:95 +msgid "Click :guilabel:`Edit Share Metadata`." +msgstr "" + +#: ../dashboard_manage_shares.rst:100 +msgid "Edit share" +msgstr "" + +#: ../dashboard_manage_shares.rst:104 +msgid "" +"Go to the share that you want to edit and choose :guilabel:`Edit Share` from " +"Actions." +msgstr "" + +#: ../dashboard_manage_shares.rst:107 +msgid ":guilabel:`Share Name`: Enter a new share name." +msgstr "" + +#: ../dashboard_manage_shares.rst:109 ../dashboard_manage_shares.rst:175 +#: ../dashboard_manage_shares.rst:238 +msgid ":guilabel:`Description`: Enter a new description." +msgstr "" + +#: ../dashboard_manage_shares.rst:111 +msgid "Click :guilabel:`Edit Share`." +msgstr "" + +#: ../dashboard_manage_shares.rst:116 +msgid "Extend share" +msgstr "" + +#: ../dashboard_manage_shares.rst:120 +msgid "" +"Go to the share that you want to edit and choose :guilabel:`Extend Share` " +"from Actions." +msgstr "" + +#: ../dashboard_manage_shares.rst:123 +msgid ":guilabel:`New Size (GB)`: Enter new size." +msgstr "" + +#: ../dashboard_manage_shares.rst:125 +msgid "Click :guilabel:`Extend Share`." +msgstr "" + +#: ../dashboard_manage_shares.rst:130 +msgid "Create share network" +msgstr "" + +#: ../dashboard_manage_shares.rst:132 ../dashboard_manage_shares.rst:155 +#: ../dashboard_manage_shares.rst:167 +msgid "" +"Log in to the dashboard, choose a project, click :guilabel:`Shares`, and " +"click :guilabel:`Share Networks`." +msgstr "" + +#: ../dashboard_manage_shares.rst:135 ../dashboard_manage_shares.rst:148 +msgid "Click :guilabel:`Create Share Network`." +msgstr "" + +#: ../dashboard_manage_shares.rst:139 +msgid ":guilabel:`Name`: Specify a name for the share network." +msgstr "" + +#: ../dashboard_manage_shares.rst:141 +msgid "" +":guilabel:`Description`: Optionally, provide a brief description for the " +"share network." +msgstr "" + +#: ../dashboard_manage_shares.rst:144 +msgid ":guilabel:`Neutron Net`: Choose a neutron network." +msgstr "" + +#: ../dashboard_manage_shares.rst:146 +msgid ":guilabel:`Neutron Subnet`: Choose a neutron subnet." +msgstr "" + +#: ../dashboard_manage_shares.rst:150 +msgid "" +"The dashboard shows the share network on the :guilabel:`Share Networks` tab." +msgstr "" + +#: ../dashboard_manage_shares.rst:153 +msgid "Delete a share network" +msgstr "" + +#: ../dashboard_manage_shares.rst:158 +msgid "Select the check boxes for the share networks that you want to delete." +msgstr "" + +#: ../dashboard_manage_shares.rst:160 +msgid "Click :guilabel:`Delete Share Networks` and confirm your choice." +msgstr "" + +#: ../dashboard_manage_shares.rst:165 +msgid "Edit share network" +msgstr "" + +#: ../dashboard_manage_shares.rst:170 +msgid "" +"Go to the share network that you want to edit and choose :guilabel:`Edit " +"Share Network` from Actions." +msgstr "" + +#: ../dashboard_manage_shares.rst:173 +msgid ":guilabel:`Name`: Enter a new share network name." +msgstr "" + +#: ../dashboard_manage_shares.rst:177 +msgid "Click :guilabel:`Edit Share Network`." +msgstr "" + +#: ../dashboard_manage_shares.rst:182 +msgid "Create security service" +msgstr "" + +#: ../dashboard_manage_shares.rst:184 ../dashboard_manage_shares.rst:218 +#: ../dashboard_manage_shares.rst:230 +msgid "" +"Log in to the dashboard, choose a project, click :guilabel:`Shares`, and " +"click :guilabel:`Security Services`." +msgstr "" + +#: ../dashboard_manage_shares.rst:187 ../dashboard_manage_shares.rst:210 +msgid "Click :guilabel:`Create Security Service`." +msgstr "" + +#: ../dashboard_manage_shares.rst:191 +msgid ":guilabel:`Name`: Specify a name for the security service." +msgstr "" + +#: ../dashboard_manage_shares.rst:193 +msgid ":guilabel:`DNS IP`: Enter the DNS IP address." +msgstr "" + +#: ../dashboard_manage_shares.rst:195 +msgid ":guilabel:`Server`: Enter the server name." +msgstr "" + +#: ../dashboard_manage_shares.rst:197 +msgid ":guilabel:`Domain`: Enter the domain name." +msgstr "" + +#: ../dashboard_manage_shares.rst:199 +msgid ":guilabel:`User`: Enter the user name." +msgstr "" + +#: ../dashboard_manage_shares.rst:201 +msgid ":guilabel:`Password`: Enter the password." +msgstr "" + +#: ../dashboard_manage_shares.rst:203 +msgid ":guilabel:`Confirm Password`: Enter the password again to confirm." +msgstr "" + +#: ../dashboard_manage_shares.rst:205 +msgid "" +":guilabel:`Type`: Choose the type from Active Directory, LDAP, or Kerberos." +msgstr "" + +#: ../dashboard_manage_shares.rst:207 +msgid "" +":guilabel:`Description`: Optionally, provide a brief description for the " +"security service." +msgstr "" + +#: ../dashboard_manage_shares.rst:212 +msgid "" +"The dashboard shows the security service on the :guilabel:`Security " +"Services` tab." +msgstr "" + +#: ../dashboard_manage_shares.rst:216 +msgid "Delete a security service" +msgstr "" + +#: ../dashboard_manage_shares.rst:221 +msgid "" +"Select the check boxes for the security services that you want to delete." +msgstr "" + +#: ../dashboard_manage_shares.rst:223 +msgid "Click :guilabel:`Delete Security Services` and confirm your choice." +msgstr "" + +#: ../dashboard_manage_shares.rst:228 +msgid "Edit security service" +msgstr "" + +#: ../dashboard_manage_shares.rst:233 +msgid "" +"Go to the security service that you want to edit and choose :guilabel:`Edit " +"Security Service` from Actions." +msgstr "" + +#: ../dashboard_manage_shares.rst:236 +msgid ":guilabel:`Name`: Enter a new security service name." +msgstr "" + +#: ../dashboard_manage_shares.rst:240 +msgid "Click :guilabel:`Edit Security Service`." +msgstr "" + +#: ../dashboard_manage_volumes.rst:3 +msgid "Create and manage volumes" +msgstr "" + +#: ../dashboard_manage_volumes.rst:5 +msgid "" +"Volumes are block storage devices that you attach to instances to enable " +"persistent storage. You can attach a volume to a running instance or detach " +"a volume and attach it to another instance at any time. You can also create " +"a snapshot from or delete a volume. Only administrative users can create " +"volume types." +msgstr "" + +#: ../dashboard_manage_volumes.rst:12 +msgid "Create a volume" +msgstr "" + +#: ../dashboard_manage_volumes.rst:19 ../dashboard_manage_volumes.rst:71 +#: ../dashboard_manage_volumes.rst:114 ../dashboard_manage_volumes.rst:136 +#: ../dashboard_manage_volumes.rst:168 +msgid "" +"On the :guilabel:`Project` tab, open the :guilabel:`Compute` tab and click :" +"guilabel:`Volumes` category." +msgstr "" + +#: ../dashboard_manage_volumes.rst:22 ../dashboard_manage_volumes.rst:56 +msgid "Click :guilabel:`Create Volume`." +msgstr "" + +#: ../dashboard_manage_volumes.rst:26 +msgid ":guilabel:`Volume Name`: Specify a name for the volume." +msgstr "" + +#: ../dashboard_manage_volumes.rst:28 +msgid "" +":guilabel:`Description`: Optionally, provide a brief description for the " +"volume." +msgstr "" + +#: ../dashboard_manage_volumes.rst:31 +msgid ":guilabel:`Type`: Leave this field blank." +msgstr "" + +#: ../dashboard_manage_volumes.rst:33 +msgid ":guilabel:`Size (GB)`: The size of the volume in gibibytes (GiB)." +msgstr "" + +#: ../dashboard_manage_volumes.rst:35 +msgid ":guilabel:`Volume Source`: Select one of the following options:" +msgstr "" + +#: ../dashboard_manage_volumes.rst:37 +msgid "" +"No source, empty volume: Creates an empty volume. An empty volume does not " +"contain a file system or a partition table." +msgstr "" + +#: ../dashboard_manage_volumes.rst:40 +msgid "" +"Snapshot: If you choose this option, a new field for Use snapshot as a " +"source displays. You can select the snapshot from the list." +msgstr "" + +#: ../dashboard_manage_volumes.rst:43 +msgid "" +"Image: If you choose this option, a new field for Use image as a source " +"displays. You can select the image from the list." +msgstr "" + +#: ../dashboard_manage_volumes.rst:46 +msgid "" +"Availability Zone: Select the Availability Zone from the list. 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_manage_volumes.rst:51 +msgid "" +"Volume: If you choose this option, a new field for :guilabel:`Use volume as " +"a source` displays. You can select the volume from the list. Options to use " +"a snapshot or a volume as the source for a volume are displayed only if " +"there are existing snapshots or volumes." +msgstr "" + +#: ../dashboard_manage_volumes.rst:58 +msgid "The dashboard shows the volume on the :guilabel:`Volumes` tab." +msgstr "" + +#: ../dashboard_manage_volumes.rst:61 +msgid "Attach a volume to an instance" +msgstr "" + +#: ../dashboard_manage_volumes.rst:63 +msgid "" +"After you create one or more volumes, you can attach them to instances. You " +"can attach a volume to one instance at a time." +msgstr "" + +#: ../dashboard_manage_volumes.rst:74 +msgid "" +"Select the volume to add to an instance and click :guilabel:`Edit " +"Attachments`." +msgstr "" + +#: ../dashboard_manage_volumes.rst:77 +msgid "" +"In the :guilabel:`Manage Volume Attachments` dialog box, select an instance." +msgstr "" + +#: ../dashboard_manage_volumes.rst:79 +msgid "" +"Enter the name of the device from which the volume is accessible by the " +"instance." +msgstr "" + +#: ../dashboard_manage_volumes.rst:82 +msgid "" +"The actual device name might differ from the volume name because of " +"hypervisor settings." +msgstr "" + +#: ../dashboard_manage_volumes.rst:85 +msgid "Click :guilabel:`Attach Volume`." +msgstr "" + +#: ../dashboard_manage_volumes.rst:87 +msgid "" +"The dashboard shows the instance to which the volume is now attached and the " +"device name." +msgstr "" + +#: ../dashboard_manage_volumes.rst:90 +msgid "" +"You can view the status of a volume in the Volumes tab of the dashboard. The " +"volume is either Available or In-Use." +msgstr "" + +#: ../dashboard_manage_volumes.rst:93 +msgid "Now you can log in to the instance and mount, format, and use the disk." +msgstr "" + +#: ../dashboard_manage_volumes.rst:96 +msgid "Detach a volume from an instance" +msgstr "" + +#: ../dashboard_manage_volumes.rst:98 +msgid "" +"Log in to the dashboard, choose a project, and click :guilabel:`Volumes`." +msgstr "" + +#: ../dashboard_manage_volumes.rst:100 +msgid "Select the volume and click :guilabel:`Edit Attachments`." +msgstr "" + +#: ../dashboard_manage_volumes.rst:102 +msgid "Click :guilabel:`Detach Volume` and confirm your changes." +msgstr "" + +#: ../dashboard_manage_volumes.rst:107 +msgid "Create a snapshot from a volume" +msgstr "" + +#: ../dashboard_manage_volumes.rst:117 +msgid "Select a volume from which to create a snapshot." +msgstr "" + +#: ../dashboard_manage_volumes.rst:119 +msgid "From the :guilabel:`More` list, select :guilabel:`Create Snapshot`." +msgstr "" + +#: ../dashboard_manage_volumes.rst:121 +msgid "" +"In the dialog box that opens, enter a snapshot name and a brief description." +msgstr "" + +#: ../dashboard_manage_volumes.rst:124 +msgid "Confirm your changes." +msgstr "" + +#: ../dashboard_manage_volumes.rst:126 +msgid "The dashboard shows the new volume snapshot in Volume Snapshots tab." +msgstr "" + +#: ../dashboard_manage_volumes.rst:129 +msgid "Edit a volume" +msgstr "" + +#: ../dashboard_manage_volumes.rst:142 +msgid "On the :guilabel:`Project` tab, click :guilabel:`Volumes`." +msgstr "" + +#: ../dashboard_manage_volumes.rst:146 +msgid "In the :guilabel:`Actions` column, click :guilabel:`Edit Volume`." +msgstr "" + +#: ../dashboard_manage_volumes.rst:148 +msgid "" +"In the :guilabel:`Edit Volume` dialog box, update the name and description " +"of the image." +msgstr "" + +#: ../dashboard_manage_volumes.rst:151 +msgid "Click :guilabel:`Edit Volume`." +msgstr "" + +#: ../dashboard_manage_volumes.rst:153 +msgid "" +"You can extend a volume by using the :guilabel:`Extend Volume` option " +"available in the :guilabel:`More` dropdown list and entering the new value " +"for volume size." +msgstr "" + +#: ../dashboard_manage_volumes.rst:158 +msgid "Delete a volume" +msgstr "" + +#: ../dashboard_manage_volumes.rst:160 +msgid "" +"When you delete an instance, the data in its attached volumes is not " +"destroyed." +msgstr "" + +#: ../dashboard_manage_volumes.rst:171 +msgid "Select the check boxes for the volumes that you want to delete." +msgstr "" + +#: ../dashboard_manage_volumes.rst:173 +msgid "Click :guilabel:`Delete Volumes` and confirm your choice." +msgstr "" + +#: ../dashboard_stacks.rst:3 +msgid "Launch and manage stacks" +msgstr "" + +#: ../dashboard_stacks.rst:5 +msgid "" +"OpenStack Orchestration is a service that you can use to orchestrate " +"multiple composite cloud applications. This service supports the use of both " +"the Amazon Web Services (AWS) CloudFormation template format through both a " +"Query API that is compatible with CloudFormation and the native OpenStack :" +"term:`Heat Orchestration Template (HOT)` format through a REST API." +msgstr "" + +#: ../dashboard_stacks.rst:12 +msgid "" +"These flexible template languages enable application developers to describe " +"and automate the deployment of infrastructure, services, and applications. " +"The templates enable creation of most OpenStack resource types, such as " +"instances, floating IP addresses, volumes, security groups, and users. Once " +"created, the resources are referred to as stacks." +msgstr "" + +#: ../dashboard_stacks.rst:20 +msgid "" +"The template languages are described in the `Template Guide `_ in the `Heat " +"developer documentation `_." +msgstr "" + +#: ../dashboard_stacks.rst:26 +msgid "Launch a stack" +msgstr "" + +#: ../dashboard_stacks.rst:31 ../dashboard_stacks.rst:126 +#: ../dashboard_stacks.rst:146 +msgid "" +"On the :guilabel:`Project` tab, open the :guilabel:`Orchestration` tab and " +"click :guilabel:`Stacks` category." +msgstr "" + +#: ../dashboard_stacks.rst:33 +msgid "Click :guilabel:`Launch Stack`." +msgstr "" + +#: ../dashboard_stacks.rst:34 +msgid "" +"In the :guilabel:`Select Template` dialog box, specify the following values:" +msgstr "" + +#: ../dashboard_stacks.rst:38 +msgid ":guilabel:`Template Source`" +msgstr "" + +#: ../dashboard_stacks.rst:38 +msgid "Choose the source of the template from the list." +msgstr "" + +#: ../dashboard_stacks.rst:41 +msgid ":guilabel:`Template URL/File/Data`" +msgstr "" + +#: ../dashboard_stacks.rst:41 +msgid "" +"Depending on the source that you select, enter the URL, browse to the file " +"location, or directly include the template." +msgstr "" + +#: ../dashboard_stacks.rst:47 +msgid ":guilabel:`Environment Source`" +msgstr "" + +#: ../dashboard_stacks.rst:47 +msgid "" +"Choose the source of the environment from the list. The environment files " +"contain additional settings for the stack." +msgstr "" + +#: ../dashboard_stacks.rst:53 +msgid ":guilabel:`Environment File/Data`" +msgstr "" + +#: ../dashboard_stacks.rst:53 +msgid "" +"Depending on the source that you select, browse to the file location, " +"directly include the environment" +msgstr "" + +#: ../dashboard_stacks.rst:59 ../dashboard_stacks.rst:132 +msgid "Click :guilabel:`Next`." +msgstr "" + +#: ../dashboard_stacks.rst:60 +msgid "" +"In the :guilabel:`Launch Stack` dialog box, specify the following values:" +msgstr "" + +#: ../dashboard_stacks.rst:64 +msgid ":guilabel:`Stack Name`" +msgstr "" + +#: ../dashboard_stacks.rst:64 +msgid "Enter a name to identify the stack." +msgstr "" + +#: ../dashboard_stacks.rst:67 +msgid ":guilabel:`Creation Timeout` :guilabel:`(minutes)`" +msgstr "" + +#: ../dashboard_stacks.rst:67 +msgid "" +"Specify the number of minutes that can elapse before the launch of the stack " +"times out." +msgstr "" + +#: ../dashboard_stacks.rst:71 +msgid ":guilabel:`Rollback On Failure`" +msgstr "" + +#: ../dashboard_stacks.rst:71 +msgid "" +"Select this check box if you want the service to roll back changes if the " +"stack fails to launch." +msgstr "" + +#: ../dashboard_stacks.rst:76 +msgid ":guilabel:`Password for user` :guilabel:`\"demo\"`" +msgstr "" + +#: ../dashboard_stacks.rst:76 +msgid "" +"Specify the password that the default user uses when the stack is created." +msgstr "" + +#: ../dashboard_stacks.rst:80 +msgid ":guilabel:`DBUsername`" +msgstr "" + +#: ../dashboard_stacks.rst:80 +msgid "Specify the name of the database user." +msgstr "" + +#: ../dashboard_stacks.rst:83 +msgid ":guilabel:`LinuxDistribution`" +msgstr "" + +#: ../dashboard_stacks.rst:83 +msgid "Specify the Linux distribution that is used in the stack." +msgstr "" + +#: ../dashboard_stacks.rst:86 +msgid ":guilabel:`DBRootPassword`" +msgstr "" + +#: ../dashboard_stacks.rst:86 +msgid "Specify the root password for the database." +msgstr "" + +#: ../dashboard_stacks.rst:89 +msgid ":guilabel:`KeyName`" +msgstr "" + +#: ../dashboard_stacks.rst:89 +msgid "Specify the name of the key pair to use to log in to the stack." +msgstr "" + +#: ../dashboard_stacks.rst:92 +msgid ":guilabel:`DBName`" +msgstr "" + +#: ../dashboard_stacks.rst:92 +msgid "Specify the name of the database." +msgstr "" + +#: ../dashboard_stacks.rst:95 +msgid ":guilabel:`DBPassword`" +msgstr "" + +#: ../dashboard_stacks.rst:95 +msgid "Specify the password of the database." +msgstr "" + +#: ../dashboard_stacks.rst:98 +msgid ":guilabel:`InstanceType`" +msgstr "" + +#: ../dashboard_stacks.rst:98 +msgid "Specify the flavor for the instance." +msgstr "" + +#: ../dashboard_stacks.rst:102 +msgid "" +"Click :guilabel:`Launch` to create a stack. The :guilabel:`Stacks` tab shows " +"the stack." +msgstr "" + +#: ../dashboard_stacks.rst:105 +msgid "" +"After the stack is created, click on the stack name to see the following " +"details:" +msgstr "" + +#: ../dashboard_stacks.rst:109 +msgid "The topology of the stack." +msgstr "" + +#: ../dashboard_stacks.rst:109 +msgid "Topology" +msgstr "" + +#: ../dashboard_stacks.rst:112 +msgid "Overview" +msgstr "" + +#: ../dashboard_stacks.rst:112 +msgid "The parameters and details of the stack." +msgstr "" + +#: ../dashboard_stacks.rst:115 +msgid "Resources" +msgstr "" + +#: ../dashboard_stacks.rst:115 +msgid "The resources used by the stack." +msgstr "" + +#: ../dashboard_stacks.rst:118 +msgid "Events" +msgstr "" + +#: ../dashboard_stacks.rst:118 +msgid "The events related to the stack." +msgstr "" + +#: ../dashboard_stacks.rst:121 +msgid "Manage a stack" +msgstr "" + +#: ../dashboard_stacks.rst:128 +msgid "Select the stack that you want to update." +msgstr "" + +#: ../dashboard_stacks.rst:129 +msgid "Click :guilabel:`Change Stack Template`." +msgstr "" + +#: ../dashboard_stacks.rst:130 +msgid "" +"In the :guilabel:`Select Template` dialog box, select the new template " +"source or environment source." +msgstr "" + +#: ../dashboard_stacks.rst:134 +msgid "The :guilabel:`Update Stack Parameters` window appears." +msgstr "" + +#: ../dashboard_stacks.rst:135 +msgid "Enter new values for any parameters that you want to update." +msgstr "" + +#: ../dashboard_stacks.rst:136 +msgid "Click :guilabel:`Update`." +msgstr "" + +#: ../dashboard_stacks.rst:139 +msgid "Delete a stack" +msgstr "" + +#: ../dashboard_stacks.rst:141 +msgid "When you delete a stack, you cannot undo this action." +msgstr "" + +#: ../dashboard_stacks.rst:148 +msgid "Select the stack that you want to delete." +msgstr "" + +#: ../dashboard_stacks.rst:149 +msgid "Click :guilabel:`Delete Stack`." +msgstr "" + +#: ../dashboard_stacks.rst:150 +msgid "" +"In the confirmation dialog box, click :guilabel:`Delete Stack` to confirm " +"the deletion." +msgstr "" + +#: ../hot.rst:3 +msgid "HOT Guide" +msgstr "" + +#: ../hot.rst:5 +msgid "" +"The HOT Guide is now maintained as part of the Heat repository and is " +"available on the OpenStack developer documentation website: `Heat Template " +"Guide `__" +msgstr "" + +#: ../index.rst:3 +msgid "OpenStack End User Guide" msgstr "" #: ../index.rst:6 msgid "Abstract" msgstr "" -#: ../cli_access_instance_through_a_console.rst:3 -msgid "Access an instance through a console" +#: ../index.rst:8 +msgid "" +"OpenStack is an open-source cloud computing platform for public and private " +"clouds. A series of interrelated projects deliver a cloud infrastructure " +"solution. This guide shows OpenStack end users how to create and manage " +"resources in an OpenStack cloud with the OpenStack dashboard and OpenStack " +"client commands." msgstr "" -#: ../cli_launch_instances.rst:34 +#: ../index.rst:14 msgid "" -"Access and security credentials, which include one or both of the following " -"credentials:" +"This guide documents OpenStack Kilo, OpenStack Juno, and OpenStack Icehouse " +"releases." msgstr "" -#: ../sdk_configure_access_security_instances.rst:157 +#: ../index.rst:18 +msgid "Contents" +msgstr "" + +#: ../index.rst:36 +msgid "Search in this guide" +msgstr "" + +#: ../index.rst:38 +msgid ":ref:`search`" +msgstr "" + +#: ../intro-user.rst:3 +msgid "How can I use an OpenStack cloud?" +msgstr "" + +#: ../intro-user.rst:5 msgid "" -"Access the security group rules from the ``rules`` attribute of a " -"`novaclient.v1\\_1.security\\_groups.SecurityGroup `__ object:" +"As an OpenStack cloud end user, you can provision your own resources within " +"the limits set by administrators." +msgstr "" + +#: ../intro-user.rst:8 +msgid "" +"The examples in this guide show you how to perform tasks by using the " +"following methods:" +msgstr "" + +#: ../intro-user.rst:11 +msgid "" +"OpenStack dashboard. Use this web-based graphical interface, code named " +"`horizon `__, to view, " +"create, and manage resources." +msgstr "" + +#: ../intro-user.rst:13 +msgid "" +"OpenStack command-line clients. Each core OpenStack project has a command-" +"line client that you can use to run simple commands to view, create, and " +"manage resources in a cloud and automate tasks by using scripts." +msgstr "" + +#: ../intro-user.rst:18 +msgid "You can modify these examples for your specific use cases." +msgstr "" + +#: ../intro-user.rst:20 +msgid "" +"In addition to these ways of interacting with a cloud, you can access the " +"OpenStack APIs directly or indirectly through `cURL `__ " +"commands or open SDKs. You can automate access or build tools to manage " +"resources and services by using the native OpenStack APIs or the EC2 " +"compatibility API." +msgstr "" + +#: ../intro-user.rst:26 +msgid "" +"To use the OpenStack APIs, it helps to be familiar with HTTP/1.1, RESTful " +"web services, the OpenStack services, and JSON or XML data serialization " +"formats." +msgstr "" + +#: ../intro-user.rst:31 +msgid "Who should read this book?" +msgstr "" + +#: ../intro-user.rst:33 +msgid "" +"This book is written for anyone who uses virtual machines and cloud " +"resources to develop software or perform research. You should have years of " +"experience with Linux-based tool sets and be comfortable using both GUI and " +"CLI based tools. While this book includes some information about using " +"Python to create and manage cloud resources, Python knowledge is not a pre-" +"requisite for reading this book." +msgstr "" + +#: ../manage_db_config.rst:3 +msgid "Manage database configuration" +msgstr "" + +#: ../manage_db_config.rst:5 +msgid "" +"You can manage database configuration tasks by using configuration groups. " +"Configuration groups let you set configuration options, in bulk, on one or " +"more databases." +msgstr "" + +#: ../manage_db_config.rst:9 +msgid "" +"This example assumes you have created a MySQL database and shows you how to " +"use a configuration group to configure it. Although this example sets just " +"one option on one database, you can use these same procedures to set " +"multiple options on multiple database instances throughout your environment. " +"This can provide significant time savings in managing your cloud." +msgstr "" + +#: ../manage_db_config.rst:18 +msgid "Bulk-configure a database or databases" +msgstr "" + +#: ../manage_db_config.rst:20 +msgid "**List available options**" +msgstr "" + +#: ../manage_db_config.rst:22 +msgid "" +"First, determine which configuration options you can set. Different data " +"store versions have different configuration options." +msgstr "" + +#: ../manage_db_config.rst:25 +msgid "" +"List the names and IDs of all available versions of the ``mysql`` data store:" +msgstr "" + +#: ../manage_db_config.rst:37 +msgid "" +"Pass in the data store version ID with the trove ``configuration-parameter-" +"list`` command to get the available options:" +msgstr "" + +#: ../manage_db_config.rst:83 +msgid "" +"In this example, the ``configuration-parameter-list`` command returns a list " +"of options that work with MySQL 5.5." +msgstr "" + +#: ../manage_db_config.rst:86 +msgid "**Create a configuration group**" +msgstr "" + +#: ../manage_db_config.rst:88 +msgid "" +"A configuration group contains a comma-separated list of key-value pairs. " +"Each pair consists of a configuration option and its value." +msgstr "" + +#: ../manage_db_config.rst:91 +msgid "" +"You can create a configuration group by using the trove ``configuration-" +"create`` command. The general syntax for this command is:" +msgstr "" + +#: ../manage_db_config.rst:99 +msgid "*NAME*. The name you want to use for this group." +msgstr "" + +#: ../manage_db_config.rst:101 +msgid "*VALUES*. The list of key-value pairs." +msgstr "" + +#: ../manage_db_config.rst:103 +msgid "*DATASTORE_NAME*. The name of the associated data store." +msgstr "" + +#: ../manage_db_config.rst:105 +msgid "Set *VALUES* as a JSON dictionary, for example:" +msgstr "" + +#: ../manage_db_config.rst:111 +msgid "" +"This example creates a configuration group called ``group1``. ``group1`` " +"contains just one key and value pair, and this pair sets the ``sync_binlog`` " +"option to ``1``." +msgstr "" + +#: ../manage_db_config.rst:128 +msgid "**Examine your existing configuration**" +msgstr "" + +#: ../manage_db_config.rst:130 +msgid "" +"Before you use the newly-created configuration group, look at how the " +"``sync_binlog`` option is configured on your database. Replace the following " +"sample connection values with values that connect to your database:" +msgstr "" + +#: ../manage_db_config.rst:147 +msgid "" +"As you can see, the ``sync_binlog`` option is currently set to ``0`` for the " +"``myDB7`` database." +msgstr "" + +#: ../manage_db_config.rst:150 +msgid "**Change the database configuration using a configuration group**" +msgstr "" + +#: ../manage_db_config.rst:152 +msgid "" +"You can change a database's configuration by attaching a configuration group " +"to a database instance. You do this by using the trove ``configuration-" +"attach`` command and passing in the ID of the database instance and the ID " +"of the configuration group." +msgstr "" + +#: ../manage_db_config.rst:157 +msgid "Get the ID of the database instance:" +msgstr "" + +#: ../manage_db_config.rst:168 +msgid "Get the ID of the configuration group:" +msgstr "" + +#: ../manage_db_config.rst:179 +msgid "Attach the configuration group to the database instance:" +msgstr "" + +#: ../manage_db_config.rst:181 +msgid "" +"This command syntax pertains only to python-troveclient version 1.0.6 and " +"later. Earlier versions require you to pass in the configuration group ID as " +"the first argument." +msgstr "" + +#: ../manage_db_config.rst:189 +msgid "**Re-examine the database configuration**" +msgstr "" + +#: ../manage_db_config.rst:191 +msgid "Display the ``sync_binlog`` setting again:" +msgstr "" + +#: ../manage_db_config.rst:202 +msgid "" +"As you can see, the ``sync_binlog`` option is now set to ``1``, as specified " +"in the ``group1`` configuration group." +msgstr "" + +#: ../manage_db_config.rst:205 +msgid "" +"**Conclusion. **\\ Using a configuration group to set a single option on a " +"single database is obviously a trivial example. However, configuration " +"groups can provide major efficiencies when you consider that:" +msgstr "" + +#: ../manage_db_config.rst:209 +msgid "A configuration group can specify a large number of option values." +msgstr "" + +#: ../manage_db_config.rst:211 +msgid "" +"You can apply a configuration group to hundreds or thousands of database " +"instances in your environment." +msgstr "" + +#: ../manage_db_config.rst:214 +msgid "" +"Used in this way, configuration groups let you modify your database cloud " +"configuration, on the fly, on a massive scale." +msgstr "" + +#: ../manage_db_config.rst:217 +msgid "" +"**Maintenance. **\\ There are also a number of useful maintenance features " +"for working with configuration groups. You can:" +msgstr "" + +#: ../manage_db_config.rst:220 +msgid "" +"Disassociate a configuration group from a database instance, using the trove " +"``configuration-detach`` command." +msgstr "" + +#: ../manage_db_config.rst:223 +msgid "" +"Modify a configuration group on the fly, using the trove ``configuration-" +"patch`` command." +msgstr "" + +#: ../manage_db_config.rst:226 +msgid "" +"Find out what instances are using a configuration group, using the trove " +"``configuration-instances`` command." +msgstr "" + +#: ../manage_db_config.rst:229 +msgid "" +"Delete a configuration group, using the trove ``configuration-delete`` " +"command. You might want to do this if no instances use a group." +msgstr "" + +#: ../managing-openstack-object-storage-with-swift-cli.rst:3 +msgid "Manage objects and containers" +msgstr "" + +#: ../managing-openstack-object-storage-with-swift-cli.rst:5 +msgid "" +"The OpenStack Object Storage service provides the ``swift`` client, which is " +"a command-line interface (CLI). Use this client to list objects and " +"containers, upload objects to containers, and download or delete objects " +"from containers. You can also gather statistics and update metadata for " +"accounts, containers, and objects." +msgstr "" + +#: ../managing-openstack-object-storage-with-swift-cli.rst:11 +msgid "" +"This client is based on the native swift client library, ``client.py``, " +"which seamlessly re-authenticates if the current token expires during " +"processing, retries operations multiple times, and provides a processing " +"concurrency of 10." +msgstr "" + +#: ../sdk.rst:3 +msgid "OpenStack Python SDK" +msgstr "" + +#: ../sdk.rst:5 +msgid "" +"The OpenStack Python Software Development Kit (SDK) is used to write Python " +"automation scripts that create and manage resources in your OpenStack cloud. " +"The SDK implements Python bindings to the OpenStack API, which enables you " +"to perform automation tasks in Python by making calls on Python objects, " +"rather than making REST calls directly. All OpenStack command-line tools are " +"implemented using the Python SDK." +msgstr "" + +#: ../sdk.rst:12 +msgid "You should also be familiar with:" +msgstr "" + +#: ../sdk.rst:14 +msgid "RESTful web services" +msgstr "" + +#: ../sdk.rst:15 +msgid "HTTP/1.1" +msgstr "" + +#: ../sdk.rst:16 +msgid "JSON and XML data serialization formats" +msgstr "" + +#: ../sdk_assign_cors_headers.rst:3 +msgid "Assign CORS headers to requests" +msgstr "" + +#: ../sdk_assign_cors_headers.rst:5 +msgid "" +":term:`Cross-Origin Resource Sharing (CORS)` is a specification that defines " +"how browsers and servers communicate across origins by using HTTP headers, " +"such as those assigned by Object Storage API requests. The Object Storage " +"API supports the following headers:" msgstr "" #: ../sdk_assign_cors_headers.rst:10 @@ -1023,3996 +7648,37 @@ msgstr "" msgid "Access-Control-Request-Method" msgstr "" -#: ../dashboard_launch_instances.rst:131 -msgid "Activate the security groups that you want to assign to the instance." +#: ../sdk_assign_cors_headers.rst:17 +msgid "Origin" msgstr "" -# #-#-#-#-# cli_nova_configure_access_security_for_instances.pot (End User Guide 1.0.0) #-#-#-#-# -# #-#-#-#-# configure_access_and_security_for_instances.pot (End User Guide 1.0.0) #-#-#-#-# -#: ../cli_nova_configure_access_security_for_instances.rst:61 -#: ../configure_access_and_security_for_instances.rst:94 -msgid "Add a key pair" -msgstr "" - -#: ../sdk_configure_access_security_instances.rst:14 -msgid "Add a keypair" -msgstr "" - -#: ../cli_manage_bare_metal_nodes.rst:83 -msgid "Add a network interface to the node" -msgstr "" - -#: ../configure_access_and_security_for_instances.rst:34 -msgid "Add a rule to the default security group" -msgstr "" - -#: ../cli_cheat_sheet.rst:255 +#: ../sdk_assign_cors_headers.rst:19 msgid "" -"Add rules to default security group allowing ping and SSH between instances " -"in the default security group" +"You can only assign these headers to objects. For more information, see `www." +"w3.org/TR/access-control/ `__." msgstr "" -#: ../dashboard_databases.rst:25 -msgid "Add the following line to ``/etc/trove/trove.conf``:" -msgstr "" - -#: ../cli_manage_bare_metal_nodes.rst:25 -msgid "Adds a network interface to a bare-metal node." -msgstr "" - -#: ../cli_nova_launch_instance_using_ISO_image.rst:113 +#: ../sdk_assign_cors_headers.rst:22 msgid "" -"After the image is successfully uploaded, you can use the new image to boot " -"instances." -msgstr "" - -#: ../cli_nova_launch_instance_using_ISO_image.rst:63 -msgid "" -"After the instance is successfully launched, connect to the instance using a " -"remote console and follow the instructions to install the system as using " -"ISO images on regular computers. When the installation is finished and " -"system is rebooted, the instance asks you again to install the operating " -"system, which means your instance is not usable. If you have problems with " -"image creation, please check the `Virtual Machine Image Guide `_ for " -"reference." -msgstr "" - -#: ../dashboard_launch_instances.rst:65 -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_stacks.rst:105 -msgid "" -"After the stack is created, click on the stack name to see the following " -"details:" -msgstr "" - -#: ../cli_manage_ip_addresses.rst:116 -msgid "" -"After you associate the IP address and configure security group rules for " -"the instance, the instance is publicly available at the floating IP address." -msgstr "" - -#: ../dashboard_manage_volumes.rst:63 -msgid "" -"After you create one or more volumes, you can attach them to instances. You " -"can attach a volume to one instance at a time." -msgstr "" - -#: ../cli_nova_launch_instance_using_ISO_image.rst:84 -msgid "" -"After you delete the instance, the system you have just installed using your " -"ISO image remains, because the parameter ``shutdown=preserve`` was set, so " -"run the following command::" -msgstr "" - -#: ../cli_launch_instances.rst:153 -msgid "" -"After you gather required parameters, run the following command to launch an " -"instance. Specify the server name, flavor ID, and image ID::" -msgstr "" - -#: ../cli_launch_instances.rst:66 -msgid "" -"After you gather the parameters that you need to launch an instance, you can " -"launch it from an image_ or a :ref:`volume`. You can launch an instance " -"directly from one of the available OpenStack images or from an image that " -"you have copied to a persistent volume. The OpenStack Image service provides " -"a pool of images that are accessible to members of different projects." -msgstr "" - -#: ../sdk_authenticate_against_identity_endpoint.rst:22 -msgid "" -"After you instantiate a ``Client`` object, you can retrieve the token by " -"accessing its ``auth_token`` attribute object:" -msgstr "" - -#: ../cli_swift_large_lists.rst:72 -msgid "Again, two items are returned, and there might be more." -msgstr "" - -#: ../cli_ceilometer.rst:60 -msgid "Alarm" -msgstr "" - -#: ../cli_swift_large_object_creation.rst:295 -msgid "All segment objects must be in the same container." -msgstr "" - -#: ../configure_access_and_security_for_instances.rst:163 -msgid "Allocate a floating IP address to an instance" -msgstr "" - -#: ../cli_nova_configure_access_security_for_instances.rst:161 -msgid "" -"Allow UDP access from IP addresses, specified as IP subnet ``0.0.0.0/0`` in " -"CIDR notation::" -msgstr "" - -#: ../dashboard_manage_shares.rst:51 -msgid "Allow access" -msgstr "" - -#: ../cli_nova_configure_access_security_for_instances.rst:132 -msgid "" -"Allow access from all IP addresses, specified as IP subnet ``0.0.0.0/0`` in " -"CIDR notation::" -msgstr "" - -#: ../cli_nova_configure_access_security_for_instances.rst:137 -msgid "" -"Allow access only from IP addresses from other security groups (source " -"groups) to access the specified port::" -msgstr "" - -#: ../cli_nova_configure_access_security_for_instances.rst:166 -msgid "" -"Allow only IP addresses from other security groups (source groups) to access " -"the specified port::" -msgstr "" - -#: ../cli_nova_configure_access_security_for_instances.rst:152 -msgid "" -"Allow only members of other security groups (source groups) to ping " -"instances::" -msgstr "" - -#: ../cli_nova_configure_access_security_for_instances.rst:145 -msgid "" -"Allow pinging from all IP addresses, specified as IP subnet ``0.0.0.0/0`` in " -"CIDR notation::" -msgstr "" - -#: ../sdk_authenticate_against_compute_endpoint.rst:22 -msgid "" -"Alternatively, you can instantiate a ``novaclient.client.Client`` object and " -"pass the version number:" -msgstr "" - -#: ../cli_swift_pseudo_hierarchical_folders_directories.rst:5 -msgid "" -"Although you cannot nest directories in OpenStack Object Storage, you can " -"simulate a hierarchical structure within a single container by adding " -"forward slash characters (``/``) in the object name. To navigate the pseudo-" -"directory structure, you can use the ``delimiter`` query parameter. This " -"example shows you how to use pseudo-hierarchical folders and directories." -msgstr "" - -#: ../cli_swift_archive_auto_extract.rst:31 -msgid "An account" -msgstr "" - -#: ../cli_config_drive.rst:47 -msgid "" -"An image built with a recent version of the cloud-init package can " -"automatically access metadata passed through the configuration drive. The " -"cloud-init package version 0.7.1 works with Ubuntu and Fedora based images, " -"such as Red Hat Enterprise Linux." -msgstr "" - -#: ../cli_access_instance_through_a_console.rst:13 -msgid "An in-browser VNC client implemented using HTML5 Canvas and WebSockets" -msgstr "" - -#: ../cli_ceilometer.rst:34 -msgid "" -"An individual data point that is associated with a specific meter. A sample " -"has the same attributes as the associated meter, with the addition of time " -"stamp and value attributes. The value attribute is also known as the sample " -"``volume``." -msgstr "" - -#: ../sdk_schedule_objects_for_deletion.rst:25 -msgid "" -"An integer value which specifies the number of seconds from the time of the " -"request to when you want to delete the object. This header is converted to a " -"``X-Delete-At`` header that is set to the sum of the ``X-Delete-After`` " -"value plus the current time, in seconds." -msgstr "" - -#: ../cli_launch_instances.rst:25 -msgid "" -"Any **user data** files. A user data file is a special key in the metadata " -"service that holds a file that cloud-aware applications in the guest " -"instance can access. For example, one application that uses user data is the " -"`cloud-init `__ system, which " -"is an open-source package from Ubuntu that is available on various Linux " -"distributions and that handles early initialization of a cloud instance." -msgstr "" - -#: ../cli_swift_static_website.rst:124 -msgid "Any 2\\ ``nn`` response indicates success." -msgstr "" - -#: ../cli_config_drive.rst:17 -msgid "" -"Any modern guest operating system that is capable of mounting an ISO 9660 or " -"VFAT file system can use the configuration drive." -msgstr "" - -#: ../cli_swift_serialized_response_formats.rst:19 -msgid "" -"Append this parameter to the URL for a ``GET`` request, where ``format`` is " -"``json`` or ``xml``." -msgstr "" - -#: ../dashboard.rst:5 -msgid "" -"As a cloud end user, you can use the OpenStack dashboard to provision your " -"own resources within the limits set by administrators. You can modify the " -"examples provided in this section to create other types and sizes of server " -"instances." -msgstr "" - -#: ../intro-user.rst:5 -msgid "" -"As an OpenStack cloud end user, you can provision your own resources within " -"the limits set by administrators." -msgstr "" - -#: ../sdk_neutron_apis.rst:20 -msgid "" -"As an example, see the sample shell file that sets these variables to get " -"credentials:" -msgstr "" - -#: ../backup_db.rst:14 -msgid "" -"As background, assume that you have created a database instance with the " -"following characteristics:" -msgstr "" - -#: ../cli_swift_env_vars.rst:21 -msgid "" -"As shown in this example, the public URL appears in the ``StorageURL`` " -"field, and the token appears in the ``Auth Token`` field:" -msgstr "" - -#: ../manage_db_config.rst:147 -msgid "" -"As you can see, the ``sync_binlog`` option is currently set to ``0`` for the " -"``myDB7`` database." -msgstr "" - -#: ../manage_db_config.rst:202 -msgid "" -"As you can see, the ``sync_binlog`` option is now set to ``1``, as specified " -"in the ``group1`` configuration group." -msgstr "" - -#: ../sdk_assign_cors_headers.rst:3 -msgid "Assign CORS headers to requests" -msgstr "" - -#: ../dashboard_launch_instances.rst:60 -msgid "Assign a name to the virtual machine." -msgstr "" - -#: ../cli_manage_ip_addresses.rst:98 -msgid "Associate an IP address with an instance in the project, as follows::" -msgstr "" - -#: ../cli_manage_ip_addresses.rst:64 -msgid "Associate floating IP addresses" -msgstr "" - -#: ../cli_manage_ip_addresses.rst:19 -msgid "" -"Associate the floating IP address with an instance of the project. Only one " -"floating IP address can be allocated to an instance at any given time." -msgstr "" - -#: ../create_db.rst:6 -msgid "" -"Assume that you have installed the Database service and populated your data " -"store with images for the type and versions of databases that you want, and " -"that you can create and access a database." -msgstr "" - -#: ../cli_swift_large_lists.rst:35 -msgid "Assume the following list of container names:" -msgstr "" - -#: ../cli_swift_large_object_creation.rst:262 -msgid "" -"Assured. The list of segments includes the MD5 checksum (``ETag``) of each " -"segment. You cannot upload the manifest object if the ``ETag`` in the list " -"differs from the uploaded segment object. If a segment is somehow lost, an " -"attempt to download the manifest object results in an error." -msgstr "" - -#: ../dashboard_launch_instances.rst:188 -msgid "At the prompt, type ``yes``." -msgstr "" - -#: ../backup_db.rst:216 -msgid "" -"At this point, you might want to delete the disabled ``guest1`` instance, by " -"using the trove ``delete`` command." -msgstr "" - -#: ../cli_nova_launch_instance_from_volume.rst:21 -#: ../cli_nova_launch_instance_from_volume.rst:31 -msgid "Attach a swap disk to an instance." -msgstr "" - -#: ../dashboard_manage_volumes.rst:61 -msgid "Attach a volume to an instance" -msgstr "" - -#: ../cli_nova_launch_instance_from_volume.rst:34 -msgid "Attach an ephemeral disk to an instance." -msgstr "" - -#: ../cli_nova_launch_instance_from_volume.rst:263 -msgid "Attach swap or ephemeral disk to an instance" -msgstr "" - -#: ../manage_db_config.rst:179 -msgid "Attach the configuration group to the database instance:" -msgstr "" - -#: ../cli_cheat_sheet.rst:303 -msgid "" -"Attach volume to instance after instance is active, and volume is available" +"This example assigns the file origin to the ``Origin`` header, which ensures " +"that the file originated from a reputable source::" msgstr "" #: ../sdk_authenticate.rst:5 msgid "Authenticate" msgstr "" -#: ../sdk_authenticate_against_compute_endpoint.rst:6 -msgid "Authenticate against a Compute endpoint" -msgstr "" - -#: ../sdk_authenticate_against_networking_endpoint.rst:6 -msgid "Authenticate against a Networking endpoint" -msgstr "" - -#: ../sdk_authenticate_against_identity_endpoint.rst:6 -msgid "Authenticate against an Identity endpoint" -msgstr "" - -#: ../sdk_authenticate_against_image_service_endpoint.rst:6 -msgid "Authenticate against an Image service endpoint" -msgstr "" - -#: ../cli_swift_archive_auto_extract.rst:5 -msgid "Auto-extract archive files" -msgstr "" - -#: ../cli_swift_archive_auto_extract.rst:17 -msgid "Auto-extract archive request" -msgstr "" - -#: ../cli_swift_archive_auto_extract.rst:69 -msgid "Auto-extract archive response" -msgstr "" - -#: ../dashboard_launch_instances.rst:157 -msgid "Automatic" -msgstr "" - -#: ../dashboard_launch_instances.rst:57 -msgid "Availability Zone" -msgstr "" - -#: ../dashboard_manage_volumes.rst:46 -msgid "" -"Availability Zone: Select the Availability Zone from the list. 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 "" - -#: ../backup_db.rst:40 -msgid "" -"Back up the database instance by using the trove ``backup-create`` command. " -"In this example, the backup is called ``backup1``. In this example, replace " -"``INSTANCE_ID`` with ``97b4b853-80f6-414f-ba6f-c6f455a79ae6``:" -msgstr "" - -# #-#-#-#-# backup_db.pot (End User Guide 1.0.0) #-#-#-#-# -# #-#-#-#-# dashboard_databases.pot (End User Guide 1.0.0) #-#-#-#-# -#: ../backup_db.rst:3 ../dashboard_databases.rst:103 -msgid "Backup and restore a database" -msgstr "" - -#: ../dashboard_manage_images.rst:52 -msgid "" -"Based on your selection for :guilabel:`Image Source`, you either enter the " -"location URL of the image in the :guilabel:`Image Location` field, or browse " -"for the image file on your file system and add it." -msgstr "" - -#: ../dashboard_databases.rst:21 -msgid "" -"Because the dashboard does not let you choose a specific datastore to use " -"with an instance, you need to configure a default datastore. The dashboard " -"then uses the default datastore to create the instance." -msgstr "" - -#: ../cli_swift_large_lists.rst:56 -msgid "Because two container names are returned, there are more names to list." -msgstr "" - -#: ../cli_launch_instances.rst:76 -msgid "Before you begin, source the OpenStack RC file." -msgstr "" - -#: ../cli_launch_instances.rst:13 -msgid "Before you can launch an instance, gather the following parameters:" -msgstr "" - -#: ../configure_access_and_security_for_instances.rst:5 -msgid "" -"Before you launch an instance, you should add security group rules to enable " -"users to ping and use SSH to connect to the instance. Security groups are " -"sets of IP filter rules that define networking access and are applied to all " -"instances within a project. To do so, you either add rules to the default " -"security group :ref:`security_groups_add_rule` or add a new security group " -"with rules." -msgstr "" - -#: ../cli_create_and_manage_networks.rst:5 -msgid "Before you run commands, set the following environment variables:" -msgstr "" - -#: ../manage_db_config.rst:130 -msgid "" -"Before you use the newly-created configuration group, look at how the " -"``sync_binlog`` option is configured on your database. Replace the following " -"sample connection values with values that connect to your database:" -msgstr "" - -#: ../cli_cheat_sheet.rst:280 -msgid "Block Storage (cinder)" -msgstr "" - -#: ../cli_use_snapshots_to_migrate_instances.rst:114 -msgid "Boot a new instance from the snapshot" -msgstr "" - -#: ../cli_cheat_sheet.rst:291 -msgid "Boot an instance and attach to volume" -msgstr "" - -#: ../cli_nova_launch_instance_using_ISO_image.rst:8 -msgid "Boot an instance from an ISO image" -msgstr "" - -#: ../cli_nova_launch_instance_from_volume.rst:17 -msgid "Boot an instance from an image and attach a non-bootable volume." -msgstr "" - -#: ../cli_nova_launch_instance_from_volume.rst:91 -msgid "" -"Boot an instance from an image and attach the empty volume to the instance::" -msgstr "" - -#: ../cli_cheat_sheet.rst:103 -msgid "Boot an instance using flavor and image names (if names are unique)" -msgstr "" - -#: ../cli_nova_launch_instance_from_volume.rst:269 -msgid "Boot an instance with a 512 MB swap disk and 2 GB ephemeral disk::" -msgstr "" - -#: ../cli_nova_launch_instance_from_volume.rst:28 -msgid "Boot from an existing source image, volume, or snapshot." -msgstr "" - -#: ../dashboard_launch_instances.rst:90 -msgid "Boot from image" -msgstr "" - -#: ../dashboard_launch_instances.rst:104 -msgid "Boot from image (creates a new volume)" -msgstr "" - -#: ../dashboard_launch_instances.rst:94 -msgid "Boot from snapshot" -msgstr "" - -#: ../dashboard_launch_instances.rst:98 -msgid "Boot from volume" -msgstr "" - -#: ../dashboard_launch_instances.rst:111 -msgid "Boot from volume snapshot (creates a new volume)" -msgstr "" - -#: ../cli_nova_launch_instance_from_volume.rst:46 -msgid "Boot instance from image and attach non-bootable volume" -msgstr "" - -#: ../dashboard_manage_containers.rst:59 ../dashboard_manage_containers.rst:87 -msgid "Browse to and select the file that you want to upload." -msgstr "" - -#: ../cli_swift_bulk_delete.rst:5 -msgid "Bulk delete" -msgstr "" - -#: ../cli_swift_bulk_delete.rst:14 -msgid "Bulk delete request" -msgstr "" - -#: ../cli_swift_bulk_delete.rst:45 -msgid "Bulk delete response" -msgstr "" - -#: ../manage_db_config.rst:18 -msgid "Bulk-configure a database or databases" -msgstr "" - -#: ../cli_change_the_size_of_your_server.rst:68 -msgid "" -"By default, the :command:`nova resize` command gives the guest operating " -"system a chance to perform a controlled shutdown before the instance is " -"powered off and the instance is resized. The shutdown behavior is configured " -"by the ``shutdown_timeout`` parameter that can be set in the :file:`nova." -"conf` file. Its value stands for the overall period (in seconds) a guest " -"operation system is allowed to complete the shutdown. The default timeout is " -"60 seconds. See `Description of Compute configuration options `_ for details." -msgstr "" - -#: ../cli_stop_and_start_an_instance.rst:55 -msgid "" -"By default, the :command:`nova shelve` command gives the guest operating " -"system a chance to perform a controlled shutdown before the instance is " -"powered off. The shutdown behavior is configured by the ``shutdown_timeout`` " -"parameter that can be set in the :file:`nova.conf` file. Its value stands " -"for the overall period (in seconds) a guest operation system is allowed to " -"complete the shutdown. The default timeout is 60 seconds. See `Description " -"of Compute configuration options `_ for details." -msgstr "" - -#: ../cli_swift_serialized_response_formats.rst:5 -msgid "" -"By default, the Object Storage API uses a ``text/plain`` response format. In " -"addition, both JSON and XML data serialization response formats are " -"supported." -msgstr "" - -#: ../cli_swift_large_object_creation.rst:11 -msgid "" -"By default, the content of an object cannot be greater than 5 GB. However, " -"you can use a number of smaller objects to construct a large object. The " -"large object is comprised of two types of objects:" -msgstr "" - -#: ../dashboard_launch_instances.rst:55 -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 "" - -#: ../cli_reboot_an_instance.rst:9 -msgid "By default, when you reboot an instance, it is a soft reboot." -msgstr "" - -#: ../cli_config_drive.rst:261 -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 :file:`/etc/nova/nova.conf` file::" -msgstr "" - -#: ../sdk_compute_apis.rst:315 -msgid "Call ``print_server`` again to check the update server details:" -msgstr "" - -#: ../sdk_compute_apis.rst:301 -msgid "" -"Call ``server.update`` on the server object with the new value for ``name`` " -"variable:" -msgstr "" - -#: ../create_db.rst:50 -msgid "Cassandra" -msgstr "" - -#: ../dashboard_manage_images.rst:110 -msgid "Change the name of the image." -msgstr "" - -#: ../cli_change_the_size_of_your_server.rst:5 -msgid "Change the size of a server by changing its flavor." -msgstr "" - -#: ../cli_change_the_size_of_your_server.rst:3 -msgid "Change the size of your server" -msgstr "" - -#: ../cli_launch_instances.rst:244 -msgid "Check if the instance is online::" -msgstr "" - -#: ../dashboard_databases.rst:154 -msgid "Check the backup you want to use and click :guilabel:`Restore Backup`." -msgstr "" - -#: ../dashboard_databases.rst:207 -msgid "" -"Check the instance you want to work with. In the :guilabel:`Actions` column, " -"expand the drop down menu and select :guilabel:`Resize Instance`." -msgstr "" - -#: ../dashboard_databases.rst:184 -msgid "" -"Check the instance you want to work with. In the :guilabel:`Actions` column, " -"expand the drop down menu and select :guilabel:`Resize Volume`." -msgstr "" - -#: ../dashboard_manage_images.rst:47 -msgid "" -"Choose the image source from the dropdown list. Your choices are :guilabel:" -"`Image Location` and :guilabel:`Image File`." -msgstr "" - -#: ../configure_access_and_security_for_instances.rst:190 -msgid "Choose the pool from which to pick the IP address." -msgstr "" - -#: ../dashboard_manage_shares.rst:78 -msgid "Choose the rule you want to delete." -msgstr "" - -#: ../dashboard_stacks.rst:47 -msgid "" -"Choose the source of the environment from the list. The environment files " -"contain additional settings for the stack." -msgstr "" - -#: ../dashboard_stacks.rst:38 -msgid "Choose the source of the template from the list." -msgstr "" - -#: ../dashboard_manage_images.rst:114 -msgid "Clear the :guilabel:`Public` check box to make the image private." -msgstr "" - -#: ../dashboard_create_networks.rst:111 -msgid "Click :guilabel:`Add Interface`." -msgstr "" - -#: ../dashboard_manage_shares.rst:66 -msgid "Click :guilabel:`Add Rule`." -msgstr "" - -#: ../dashboard_manage_shares.rst:58 -msgid "Click :guilabel:`Add rule`." -msgstr "" - -#: ../configure_access_and_security_for_instances.rst:72 -#: ../configure_access_and_security_for_instances.rst:87 -msgid "Click :guilabel:`Add`." -msgstr "" - -#: ../configure_access_and_security_for_instances.rst:188 -msgid "Click :guilabel:`Allocate IP To Project`." -msgstr "" - -#: ../configure_access_and_security_for_instances.rst:192 -msgid "Click :guilabel:`Allocate IP`." -msgstr "" - -#: ../configure_access_and_security_for_instances.rst:208 -msgid "Click :guilabel:`Associate`." -msgstr "" - -#: ../dashboard_manage_volumes.rst:85 -msgid "Click :guilabel:`Attach Volume`." -msgstr "" - -#: ../dashboard_databases.rst:137 -msgid "Click :guilabel:`Backup`. The new backup appears in the backup list." -msgstr "" - -#: ../dashboard_stacks.rst:129 -msgid "Click :guilabel:`Change Stack Template`." -msgstr "" - -#: ../dashboard_manage_containers.rst:118 -msgid "Click :guilabel:`Copy Object`." -msgstr "" - -#: ../dashboard_databases.rst:124 -msgid "Click :guilabel:`Create Backup`." -msgstr "" - -#: ../dashboard_manage_containers.rst:27 -msgid "Click :guilabel:`Create Container`." -msgstr "" - -#: ../dashboard_manage_images.rst:35 ../dashboard_manage_images.rst:84 -msgid "Click :guilabel:`Create Image`." -msgstr "" - -#: ../configure_access_and_security_for_instances.rst:109 -msgid "Click :guilabel:`Create Key Pair`." -msgstr "" - -#: ../dashboard_create_networks.rst:27 -msgid "Click :guilabel:`Create Network`." -msgstr "" - -#: ../dashboard_manage_containers.rst:165 -msgid "Click :guilabel:`Create Pseudo-folder`." -msgstr "" - -#: ../dashboard_create_networks.rst:79 -msgid "Click :guilabel:`Create Router`." -msgstr "" - -#: ../dashboard_manage_shares.rst:187 ../dashboard_manage_shares.rst:210 -msgid "Click :guilabel:`Create Security Service`." -msgstr "" - -#: ../dashboard_manage_shares.rst:135 ../dashboard_manage_shares.rst:148 -msgid "Click :guilabel:`Create Share Network`." -msgstr "" - -#: ../dashboard_manage_shares.rst:16 ../dashboard_manage_shares.rst:35 -msgid "Click :guilabel:`Create Share`." -msgstr "" - -#: ../dashboard_manage_volumes.rst:22 ../dashboard_manage_volumes.rst:56 -msgid "Click :guilabel:`Create Volume`." -msgstr "" - -# #-#-#-#-# dashboard_create_networks.pot (End User Guide 1.0.0) #-#-#-#-# -# #-#-#-#-# dashboard_manage_containers.pot (End User Guide 1.0.0) #-#-#-#-# -#: ../dashboard_create_networks.rst:64 ../dashboard_manage_containers.rst:176 -msgid "Click :guilabel:`Create`." -msgstr "" - -#: ../dashboard_manage_images.rst:134 -msgid "Click :guilabel:`Delete Images`." -msgstr "" - -#: ../dashboard_manage_shares.rst:223 -msgid "Click :guilabel:`Delete Security Services` and confirm your choice." -msgstr "" - -#: ../dashboard_manage_shares.rst:160 -msgid "Click :guilabel:`Delete Share Networks` and confirm your choice." -msgstr "" - -#: ../dashboard_manage_shares.rst:46 -msgid "Click :guilabel:`Delete Shares` and confirm your choice." -msgstr "" - -#: ../dashboard_stacks.rst:149 -msgid "Click :guilabel:`Delete Stack`." -msgstr "" - -#: ../dashboard_manage_volumes.rst:173 -msgid "Click :guilabel:`Delete Volumes` and confirm your choice." -msgstr "" - -#: ../dashboard_manage_shares.rst:80 -msgid "Click :guilabel:`Delete rule` and confirm your choice." -msgstr "" - -#: ../dashboard_manage_volumes.rst:102 -msgid "Click :guilabel:`Detach Volume` and confirm your changes." -msgstr "" - -#: ../dashboard_manage_shares.rst:240 -msgid "Click :guilabel:`Edit Security Service`." -msgstr "" - -#: ../dashboard_manage_shares.rst:95 -msgid "Click :guilabel:`Edit Share Metadata`." -msgstr "" - -#: ../dashboard_manage_shares.rst:177 -msgid "Click :guilabel:`Edit Share Network`." -msgstr "" - -#: ../dashboard_manage_shares.rst:111 -msgid "Click :guilabel:`Edit Share`." -msgstr "" - -#: ../dashboard_manage_volumes.rst:151 -msgid "Click :guilabel:`Edit Volume`." -msgstr "" - -#: ../dashboard_manage_shares.rst:125 -msgid "Click :guilabel:`Extend Share`." -msgstr "" - -#: ../configure_access_and_security_for_instances.rst:132 -msgid "Click :guilabel:`Import Key Pair`." -msgstr "" - -#: ../dashboard_databases.rst:69 -msgid "Click :guilabel:`Launch Instance`." -msgstr "" - -#: ../dashboard_stacks.rst:33 -msgid "Click :guilabel:`Launch Stack`." -msgstr "" - -#: ../dashboard_stacks.rst:102 -msgid "" -"Click :guilabel:`Launch` to create a stack. The :guilabel:`Stacks` tab shows " -"the stack." -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:162 -msgid "Click :guilabel:`Launch`." -msgstr "" - -#: ../dashboard_manage_containers.rst:106 -msgid "" -"Click :guilabel:`More` and choose :guilabel:`Copy` from the dropdown list." -msgstr "" - -#: ../dashboard_manage_containers.rst:83 -msgid "" -"Click :guilabel:`More` and choose :guilabel:`Edit` from the dropdown list." -msgstr "" - -#: ../dashboard_stacks.rst:59 ../dashboard_stacks.rst:132 -msgid "Click :guilabel:`Next`." -msgstr "" - -#: ../dashboard_databases.rst:215 -msgid "Click :guilabel:`Resize Database Instance`." -msgstr "" - -#: ../dashboard_databases.rst:193 -msgid "Click :guilabel:`Resize Database Volume`." -msgstr "" - -#: ../dashboard_manage_images.rst:116 -msgid "Click :guilabel:`Update Image`." -msgstr "" - -#: ../dashboard_manage_containers.rst:89 -#: ../dashboard_manage_containers.rst:147 -msgid "Click :guilabel:`Update Object`." -msgstr "" - -#: ../dashboard_stacks.rst:136 -msgid "Click :guilabel:`Update`." -msgstr "" - -#: ../dashboard_manage_containers.rst:50 ../dashboard_manage_containers.rst:61 -#: ../dashboard_manage_containers.rst:137 -msgid "Click :guilabel:`Upload Object`." -msgstr "" - -#: ../configure_access_and_security_for_instances.rst:185 -msgid "" -"Click the :guilabel:`Floating IPs` tab, which shows the floating IP " -"addresses allocated to instances." -msgstr "" - -#: ../configure_access_and_security_for_instances.rst:106 -#: ../configure_access_and_security_for_instances.rst:129 -msgid "" -"Click the :guilabel:`Key Pairs` tab, which shows the key pairs that are " -"available for this project." -msgstr "" - -#: ../dashboard_databases.rst:99 -msgid "" -"Click the :guilabel:`Launch` button. The new database instance appears in " -"the databases list." -msgstr "" - -#: ../dashboard_databases.rst:159 -msgid "" -"Click the :guilabel:`Restore From Database` tab and make sure that this new " -"instance is based on the correct backup." -msgstr "" - -#: ../dashboard_create_networks.rst:86 -msgid "Click the new router's :guilabel:`Set Gateway` button." -msgstr "" - -#: ../cli_manage_bare_metal_nodes.rst:20 -msgid "Commands" -msgstr "" - -#: ../cli_swift_large_object_creation.rst:248 -msgid "Comparison of static and dynamic large objects" -msgstr "" - -#: ../sdk_compute_apis.rst:6 -msgid "Compute" -msgstr "" - -#: ../cli_cheat_sheet.rst:83 -msgid "Compute (nova)" -msgstr "" - -#: ../cli_config_drive.rst:139 -msgid "Configuration drive contents" -msgstr "" - -#: ../cli_config_drive.rst:253 -msgid "Configuration drive format" -msgstr "" - -# #-#-#-#-# cli_nova_configure_access_security_for_instances.pot (End User Guide 1.0.0) #-#-#-#-# -# #-#-#-#-# configure_access_and_security_for_instances.pot (End User Guide 1.0.0) #-#-#-#-# -# #-#-#-#-# sdk_configure_access_security_instances.pot (End User Guide 1.0.0) #-#-#-#-# -#: ../cli_nova_configure_access_security_for_instances.rst:3 -#: ../configure_access_and_security_for_instances.rst:3 -#: ../sdk_configure_access_security_instances.rst:6 -msgid "Configure access and security for instances" -msgstr "" - -#: ../cli_change_the_size_of_your_server.rst:96 -msgid "Confirm the resize,for example::" -msgstr "" - -#: ../dashboard_manage_volumes.rst:124 -msgid "Confirm your changes." -msgstr "" - -#: ../dashboard_launch_instances.rst:174 -msgid "Connect to your instance by using SSH" -msgstr "" - -#: ../index.rst:18 -msgid "Contents" -msgstr "" - -#: ../dashboard_launch_instances.rst:181 -msgid "Copy the IP address for your instance." -msgstr "" - -#: ../cli_launch_instances.rst:226 -msgid "" -"Copy the administrative password value from the ``adminPass`` field. Use the " -"password to log in to your server." -msgstr "" - -#: ../cli_launch_instances.rst:223 -msgid "" -"Copy the server ID value from the ``id`` field in the output. Use the ID to " -"get server details or to delete your server." -msgstr "" - -#: ../cli_swift_large_object_creation.rst:303 -msgid "Copying the manifest object" -msgstr "" - -#: ../cli_swift_set_object_versions.rst:38 -msgid "Create a ``current`` container to store current versions of objects." -msgstr "" - -#: ../cli_manage_bare_metal_nodes.rst:46 -msgid "Create a bare-metal node" -msgstr "" - -#: ../cli_nova_launch_instance_from_volume.rst:209 -msgid "" -"Create a bootable volume from an image, before the instance boots. The " -"volume is not deleted when the instance is terminated::" -msgstr "" - -#: ../set_up_clustering.rst:37 -msgid "" -"Create a cluster by using the trove ``cluster-create`` command. This command " -"creates a one-shard cluster. Pass in:" -msgstr "" - -#: ../dashboard_manage_containers.rst:17 -msgid "Create a container" -msgstr "" - -#: ../dashboard_databases.rst:13 -msgid "Create a database instance" -msgstr "" - -#: ../cli_cheat_sheet.rst:337 -msgid "Create a file on the volume" -msgstr "" - -#: ../cli_swift_large_object_creation.rst:68 -msgid "" -"Create a manifest object. Include the ``?multipart-manifest=put`` query " -"string at the end of the manifest object name to indicate that this is a " -"manifest object." -msgstr "" - -#: ../cli_cheat_sheet.rst:325 -msgid "Create a mountpoint" -msgstr "" - -#: ../dashboard_create_networks.rst:17 -msgid "Create a network" -msgstr "" - -#: ../cli_create_and_manage_networks.rst:59 -msgid "Create a network with specified provider network type::" -msgstr "" - -#: ../cli_create_and_manage_networks.rst:34 -msgid "Create a network::" -msgstr "" - -#: ../set_up_replication.rst:38 -msgid "" -"Create a new instance that will be a replica of the original instance. You " -"do this by passing in the ``--replica_of`` option with the trove ``create`` " -"command. This example creates a replica called ``replica_1``. ``replica_1`` " -"is a replica of the original instance, ``base_1``:" -msgstr "" - -#: ../cli_cheat_sheet.rst:284 -msgid "Create a new volume" -msgstr "" - -#: ../cli_nova_launch_instance_from_volume.rst:48 -msgid "" -"Create a non-bootable volume and attach that volume to an instance that you " -"boot from an image." -msgstr "" - -#: ../cli_nova_launch_instance_from_volume.rst:55 -msgid "Create a non-bootable volume::" -msgstr "" - -#: ../cli_create_and_manage_networks.rst:168 -msgid "Create a port with specified IP address::" -msgstr "" - -#: ../cli_create_and_manage_networks.rst:200 -msgid "Create a port without specified IP address::" -msgstr "" - -#: ../dashboard_create_networks.rst:69 -msgid "Create a router" -msgstr "" - -#: ../sdk_neutron_apis.rst:328 -msgid "Create a router and add a port to the subnet:" -msgstr "" - -#: ../cli_create_and_manage_networks.rst:132 -msgid "Create a router::" -msgstr "" - -#: ../cli_swift_set_object_versions.rst:94 -msgid "Create a second version of the object in the ``current`` container:" -msgstr "" - -#: ../dashboard_manage_shares.rst:12 -msgid "Create a share" -msgstr "" - -#: ../dashboard_manage_volumes.rst:107 -msgid "Create a snapshot from a volume" -msgstr "" - -#: ../cli_use_snapshots_to_migrate_instances.rst:27 -msgid "Create a snapshot of the instance" -msgstr "" - -#: ../cli_create_and_manage_stacks.rst:24 -msgid "Create a stack from an example template file" -msgstr "" - -#: ../cli_cheat_sheet.rst:272 -msgid "Create a subnet" -msgstr "" - -#: ../cli_create_and_manage_networks.rst:86 -msgid "Create a subnet::" -msgstr "" - -#: ../dashboard_manage_volumes.rst:12 -msgid "Create a volume" -msgstr "" - -#: ../cli_nova_launch_instance_from_volume.rst:24 -msgid "Create a volume from an image and boot an instance from that volume." -msgstr "" - -#: ../cli_swift_set_object_versions.rst:24 -msgid "Create an ``archive`` container to store older versions of objects:" -msgstr "" - -#: ../cli_swift_archive_auto_extract.rst:44 -msgid "Create an archive for auto-extract" -msgstr "" - -#: ../cli_ceilometer.rst:65 -msgid "" -"Create an auto-scaling stack by running the following command. The :option:`-" -"f` option specifies the name of the stack template file, and the :option:`-" -"P` option specifies the :code:`KeyName` parameter as :code:`heat_key`::" -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:142 ../dashboard_launch_instances.rst:211 -msgid "Create an instance snapshot" -msgstr "" - -#: ../create_db.rst:5 ../create_db.rst:13 -msgid "Create and access a database" -msgstr "" - -#: ../cli_swift_create_containers.rst:3 -msgid "Create and manage containers" -msgstr "" - -# #-#-#-#-# dashboard_databases.pot (End User Guide 1.0.0) #-#-#-#-# -# #-#-#-#-# trove-manage-db.pot (End User Guide 1.0.0) #-#-#-#-# -#: ../dashboard_databases.rst:3 ../trove-manage-db.rst:3 -msgid "Create and manage databases" -msgstr "" - -# #-#-#-#-# cli_create_and_manage_networks.pot (End User Guide 1.0.0) #-#-#-#-# -# #-#-#-#-# dashboard_create_networks.pot (End User Guide 1.0.0) #-#-#-#-# -#: ../cli_create_and_manage_networks.rst:3 ../dashboard_create_networks.rst:3 -msgid "Create and manage networks" -msgstr "" - -#: ../dashboard_manage_containers.rst:3 -msgid "Create and manage object containers" -msgstr "" - -# #-#-#-#-# cli_nova_configure_access_security_for_instances.pot (End User Guide 1.0.0) #-#-#-#-# -# #-#-#-#-# sdk_configure_access_security_instances.pot (End User Guide 1.0.0) #-#-#-#-# -#: ../cli_nova_configure_access_security_for_instances.rst:119 -#: ../sdk_configure_access_security_instances.rst:155 -msgid "Create and manage security group rules" -msgstr "" - -# #-#-#-#-# cli_nova_configure_access_security_for_instances.pot (End User Guide 1.0.0) #-#-#-#-# -# #-#-#-#-# sdk_configure_access_security_instances.pot (End User Guide 1.0.0) #-#-#-#-# -#: ../cli_nova_configure_access_security_for_instances.rst:96 -#: ../sdk_configure_access_security_instances.rst:105 -msgid "Create and manage security groups" -msgstr "" - -#: ../dashboard_manage_shares.rst:3 -msgid "Create and manage shares" -msgstr "" - -#: ../cli_create_and_manage_stacks.rst:3 -msgid "Create and manage stacks" -msgstr "" - -#: ../dashboard_manage_volumes.rst:3 -msgid "Create and manage volumes" -msgstr "" - -#: ../backup_db_incremental.rst:28 -msgid "Create and use incremental backups" -msgstr "" - -#: ../configure_access_and_security_for_instances.rst:96 -msgid "Create at least one key pair for each project." -msgstr "" - -#: ../cli_cheat_sheet.rst:232 -msgid "Create keypair" -msgstr "" - -# #-#-#-#-# cli_cheat_sheet.pot (End User Guide 1.0.0) #-#-#-#-# -# #-#-#-#-# sdk_neutron_apis.pot (End User Guide 1.0.0) #-#-#-#-# -#: ../cli_cheat_sheet.rst:266 ../sdk_neutron_apis.rst:131 -msgid "Create network" -msgstr "" - -#: ../cli_create_and_manage_networks.rst:15 -msgid "Create networks" -msgstr "" - -# #-#-#-#-# cli_create_and_manage_networks.pot (End User Guide 1.0.0) #-#-#-#-# -# #-#-#-#-# sdk_neutron_apis.pot (End User Guide 1.0.0) #-#-#-#-# -#: ../cli_create_and_manage_networks.rst:166 ../sdk_neutron_apis.rst:188 -msgid "Create ports" -msgstr "" - -#: ../sdk_neutron_apis.rst:301 -msgid "Create router and add port to subnet" -msgstr "" - -#: ../sdk_neutron_apis.rst:360 -msgid "Create router: complete code listing example" -msgstr "" - -#: ../cli_create_and_manage_networks.rst:130 -msgid "Create routers" -msgstr "" - -#: ../dashboard_manage_shares.rst:182 -msgid "Create security service" -msgstr "" - -#: ../sdk_compute_apis.rst:90 -msgid "Create server (API v2)" -msgstr "" - -#: ../sdk_compute_apis.rst:141 -msgid "Create server code listing example" -msgstr "" - -#: ../dashboard_manage_shares.rst:130 -msgid "Create share network" -msgstr "" - -#: ../cli_swift_static_website.rst:5 -msgid "Create static website" -msgstr "" - -#: ../cli_create_and_manage_networks.rst:84 -msgid "Create subnets" -msgstr "" - -#: ../cli_swift_set_object_versions.rst:61 -msgid "Create the first version of an object in the ``current`` container:" -msgstr "" - -#: ../cli_nova_launch_instance_from_volume.rst:134 -msgid "Create volume from image and boot instance" -msgstr "" - -#: ../cli_manage_bare_metal_nodes.rst:34 -msgid "Creates a bare-metal node." -msgstr "" - -#: ../dashboard_launch_instances.rst:149 -msgid "Customization Script" -msgstr "" - -#: ../create_db.rst:46 -msgid "Database" -msgstr "" - -#: ../dashboard_databases.rst:133 -msgid "Database Instance" -msgstr "" - -#: ../create_db.rst:97 -msgid "Database flavor: ``6``" -msgstr "" - -#: ../backup_db.rst:24 -msgid "Databases: ``db1`` and ``db2``" -msgstr "" - -#: ../set_up_clustering.rst:152 -msgid "Delete a cluster, using the trove ``cluster-delete`` command." -msgstr "" - -#: ../manage_db_config.rst:229 -msgid "" -"Delete a configuration group, using the trove ``configuration-delete`` " -"command. You might want to do this if no instances use a group." -msgstr "" - -#: ../cli_manage_ip_addresses.rst:24 -msgid "" -"Delete a floating IP from the project which automatically deletes that IP's " -"associations." -msgstr "" - -#: ../sdk_neutron_apis.rst:404 -msgid "Delete a network" -msgstr "" - -#: ../cli_nova_configure_access_security_for_instances.rst:173 -msgid "Delete a security group rule" -msgstr "" - -#: ../dashboard_manage_shares.rst:216 -msgid "Delete a security service" -msgstr "" - -#: ../dashboard_manage_shares.rst:40 -msgid "Delete a share" -msgstr "" - -#: ../dashboard_manage_shares.rst:153 -msgid "Delete a share network" -msgstr "" - -#: ../dashboard_stacks.rst:139 -msgid "Delete a stack" -msgstr "" - -#: ../dashboard_manage_volumes.rst:158 -msgid "Delete a volume" -msgstr "" - -#: ../dashboard_manage_images.rst:119 -msgid "Delete an image" -msgstr "" - -#: ../cli_delete_an_instance.rst:3 -msgid "Delete an instance" -msgstr "" - -#: ../sdk_neutron_apis.rst:451 -msgid "Delete network: complete code listing example" -msgstr "" - -#: ../sdk_compute_apis.rst:169 -msgid "Delete server (API v2)" -msgstr "" - -#: ../sdk_compute_apis.rst:222 -msgid "Delete server code example" -msgstr "" - -#: ../cli_cheat_sheet.rst:31 -msgid "Delete specified image" -msgstr "" - -#: ../cli_nova_launch_instance_using_ISO_image.rst:80 -msgid "Delete the instance using the following command::" -msgstr "" - -#: ../sdk_neutron_apis.rst:426 -msgid "Delete the network:" -msgstr "" - -#: ../dashboard_manage_images.rst:121 -msgid "" -"Deletion of images is permanent and **cannot** be reversed. Only users with " -"the appropriate permissions can delete images." -msgstr "" - -#: ../dashboard_manage_shares.rst:71 -msgid "Deny access" -msgstr "" - -#: ../cli_launch_instances.rst:184 -msgid "" -"Depending on the parameters that you provide, the command returns a list of " -"server properties::" -msgstr "" - -#: ../dashboard_stacks.rst:53 -msgid "" -"Depending on the source that you select, browse to the file location, " -"directly include the environment" -msgstr "" - -#: ../dashboard_stacks.rst:41 -msgid "" -"Depending on the source that you select, enter the URL, browse to the file " -"location, or directly include the template." -msgstr "" - -#: ../dashboard_manage_images.rst:12 -msgid "" -"Depending on your role, you may have permission to upload and manage virtual " -"machine images. Operators might restrict the upload and management of images " -"to cloud administrators or operators only. If you have the appropriate " -"privileges, you can use the dashboard to upload and manage images in the " -"admin project." -msgstr "" - -#: ../cli_cheat_sheet.rst:37 -msgid "Describe a specific image" -msgstr "" - -# #-#-#-#-# cli_swift_large_object_creation.pot (End User Guide 1.0.0) #-#-#-#-# -# #-#-#-#-# cli_swift_serialized_response_formats.pot (End User Guide 1.0.0) #-#-#-#-# -#: ../cli_swift_large_object_creation.rst:258 -#: ../cli_swift_serialized_response_formats.rst:17 -msgid "Description" -msgstr "" - -#: ../dashboard_manage_volumes.rst:96 -msgid "Detach a volume from an instance" -msgstr "" - -#: ../dashboard_databases.rst:73 -msgid "Details" -msgstr "" - -#: ../sdk_compute_apis.rst:191 -msgid "Determine whether the ``vm1`` server exists:" -msgstr "" - -#: ../configure_access_and_security_for_instances.rst:82 -msgid "Direction" -msgstr "" - -#: ../manage_db_config.rst:220 -msgid "" -"Disassociate a configuration group from a database instance, using the trove " -"``configuration-detach`` command." -msgstr "" - -#: ../cli_manage_ip_addresses.rst:22 -msgid "Disassociate a floating IP address from an instance in the project." -msgstr "" - -#: ../cli_manage_ip_addresses.rst:132 -msgid "Disassociate floating IP addresses" -msgstr "" - -#: ../cli_swift_discoverability.rst:5 -msgid "Discoverability" -msgstr "" - -#: ../create_db.rst:46 -msgid "Disk (GB)" -msgstr "" - -#: ../dashboard_launch_instances.rst:160 -msgid "Disk Partition" -msgstr "" - -#: ../set_up_clustering.rst:71 -msgid "" -"Display information about a cluster by using the trove ``cluster-show`` " -"command. Pass in the ID of the cluster." -msgstr "" - -#: ../cli_cheat_sheet.rst:353 -msgid "Display information for the account, container, or object" -msgstr "" - -#: ../manage_db_config.rst:191 -msgid "Display the ``sync_binlog`` setting again:" -msgstr "" - -#: ../cli_config_drive.rst:64 -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_use_snapshots_to_migrate_instances.rst:73 -msgid "Download the snapshot as an image" -msgstr "" - -#: ../cli_use_snapshots_to_migrate_instances.rst:84 -msgid "" -"Download the snapshot by using the image ID that was returned in the " -"previous step::" -msgstr "" - -#: ../cli_swift_large_object_creation.rst:260 -msgid "Dynamic large object" -msgstr "" - -#: ../cli_swift_large_object_creation.rst:42 -#: ../cli_swift_large_object_creation.rst:156 -msgid "Dynamic large objects" -msgstr "" - -#: ../cli_config_drive.rst:201 -msgid "EC2 metadata format" -msgstr "" - -#: ../sdk_install.rst:4 -msgid "" -"Each OpenStack project has its own Python library. These libraries are " -"bundled with the command-line clients. For example, the Python bindings for " -"the Compute API are bundled with the python-novaclient package." -msgstr "" - -#: ../set_up_clustering.rst:161 -msgid "" -"Each cluster includes at least one query router and one config server. Query " -"routers and config servers count against your quota. When you delete a " -"cluster, the system deletes the associated query router(s) and config " -"server(s)." -msgstr "" - -#: ../set_up_clustering.rst:8 -msgid "Each cluster includes:" -msgstr "" - -#: ../cli_manage_ip_addresses.rst:5 -msgid "" -"Each instance has a private, fixed IP address and can also have a public, or " -"floating IP address. Private IP addresses are used for communication between " -"instances, and public addresses are used for communication with networks " -"outside the cloud, including the Internet." -msgstr "" - -#: ../dashboard_manage_volumes.rst:129 -msgid "Edit a volume" -msgstr "" - -#: ../dashboard_manage_shares.rst:228 -msgid "Edit security service" -msgstr "" - -#: ../dashboard_manage_shares.rst:100 -msgid "Edit share" -msgstr "" - -#: ../dashboard_manage_shares.rst:85 -msgid "Edit share metadata" -msgstr "" - -#: ../dashboard_manage_shares.rst:165 -msgid "Edit share network" -msgstr "" - -#: ../cli_swift_static_website.rst:87 -msgid "Enable CSS for file listing" -msgstr "" - -#: ../cli_config_drive.rst:76 -msgid "Enable and access the configuration drive" -msgstr "" - -#: ../cli_swift_static_website.rst:76 -msgid "Enable file listing" -msgstr "" - -#: ../cli_swift_large_object_creation.rst:261 -msgid "End-to-end integrity" -msgstr "" - -#: ../cli_config_drive.rst:114 -msgid "" -"Ensure that you use at least version 0.3.1 of CirrOS for configuration drive " -"support." -msgstr "" - -#: ../dashboard_manage_images.rst:44 -msgid "Enter a brief description of the image." -msgstr "" - -#: ../dashboard_manage_images.rst:42 -msgid "Enter a name for the image." -msgstr "" - -#: ../dashboard_manage_containers.rst:57 -#: ../dashboard_manage_containers.rst:145 -msgid "Enter a name for the object." -msgstr "" - -#: ../dashboard_manage_containers.rst:171 -msgid "Enter a name for the pseudo-folder." -msgstr "" - -#: ../dashboard_stacks.rst:64 -msgid "Enter a name to identify the stack." -msgstr "" - -#: ../dashboard_stacks.rst:135 -msgid "Enter new values for any parameters that you want to update." -msgstr "" - -#: ../dashboard_manage_images.rst:39 -msgid "Enter the following values:" -msgstr "" - -#: ../dashboard_manage_volumes.rst:79 -msgid "" -"Enter the name of the device from which the volume is accessible by the " -"instance." -msgstr "" - -#: ../dashboard_launch_instances.rst:157 -msgid "Entire disk is single partition and automatically resizes." -msgstr "" - -#: ../cli_swift_env_vars.rst:5 -msgid "Environment variables required to run examples" -msgstr "" - -#: ../cli_swift_static_website.rst:105 -msgid "" -"Error pages are served with the status code pre-pended to the name of the " -"error page you set. For instance, if you set ``X-Container-Meta-Web-Error`` " -"to ``error.html``, 401 errors will display the page ``401error.html``. " -"Similarly, 404 errors will display ``404error.html``. You must have both of " -"these pages created in your container when you set the ``X-Container-Meta-" -"Web-Error`` metadata, or your site will display generic error pages." -msgstr "" - -#: ../cli_swift_bulk_delete.rst:73 -msgid "" -"Errors. A list of object names and associated error statuses for the objects " -"that failed to delete. The format depends on the value that you set in the " -"``Accept`` header." -msgstr "" - -#: ../dashboard_stacks.rst:118 -msgid "Events" -msgstr "" - -#: ../cli_access_instance_through_a_console.rst:23 -msgid "Example:" -msgstr "" - -#: ../cli_swift_serialized_response_formats.rst:36 -msgid "Example 1. JSON example with format query parameter" -msgstr "" - -#: ../cli_swift_serialized_response_formats.rst:79 -msgid "Example 2. XML example with Accept header" -msgstr "" - -#: ../dashboard_manage_shares.rst:116 -msgid "Extend share" -msgstr "" - -#: ../dashboard_launch_instances.rst:160 -msgid "Faster build times but requires manual partitioning." -msgstr "" - -#: ../manage_db_config.rst:226 -msgid "" -"Find out what instances are using a configuration group, using the trove " -"``configuration-instances`` command." -msgstr "" - -#: ../manage_db_config.rst:22 -msgid "" -"First, determine which configuration options you can set. Different data " -"store versions have different configuration options." -msgstr "" - -#: ../backup_db.rst:28 -msgid "" -"First, get the ID of the ``guest1`` database instance by using the trove " -"``list`` command:" -msgstr "" - -#: ../create_db.rst:131 -msgid "" -"First, use the trove ``list`` command to list all instances and their IDs:" -msgstr "" - -#: ../dashboard_launch_instances.rst:79 -msgid "Flavor" -msgstr "" - -#: ../create_db.rst:70 -msgid "" -"Flavor ID: You must use an ID that is not already in use. In this example, " -"IDs 1 through 5 are in use, so use ID ``6``." -msgstr "" - -#: ../backup_db.rst:20 -msgid "Flavor ID: ``10``" -msgstr "" - -#: ../create_db.rst:68 -msgid "Flavor name: ``mysql_minimum``" -msgstr "" - -#: ../dashboard_manage_images.rst:92 -msgid "Follow this procedure to update an existing image." -msgstr "" - -#: ../dashboard_manage_images.rst:25 -msgid "Follow this procedure to upload an image to a project:" -msgstr "" - -#: ../sdk_neutron_apis.rst:251 -msgid "For ``get_credentials`` see :ref:`Get credentials `." -msgstr "" - -#: ../sdk_neutron_apis.rst:229 -msgid "For ``get_credentials``, see :ref:`Get credentials `." -msgstr "" - -#: ../sdk_neutron_apis.rst:226 -msgid "" -"For ``get_nova_credentials``, see :ref:`Get Nova credentials `." -msgstr "" - -#: ../sdk_neutron_apis.rst:183 ../sdk_neutron_apis.rst:253 -#: ../sdk_neutron_apis.rst:517 -msgid "For ``print_values``, see :ref:`Print values `." -msgstr "" - -#: ../sdk_install.rst:8 -msgid "" -"For details about how to install the clients, see :doc:`../common/" -"cli_install_openstack_command_line_clients`." -msgstr "" - -#: ../dashboard_launch_instances.rst:44 -msgid "" -"For details on creating images, see `Creating images manually `__ in " -"the *OpenStack Virtual Machine Image Guide*." -msgstr "" - -#: ../cli_manage_bare_metal_nodes.rst:85 -msgid "" -"For each NIC on the node, you must create an interface, specifying the " -"interface's MAC address." -msgstr "" - -#: ../cli_manage_ip_addresses.rst:57 -msgid "" -"For each floating IP address that is allocated to the current project, the " -"command outputs the floating IP address, the ID for the instance to which " -"the floating IP address is assigned, the associated fixed IP address, and " -"the pool from which the floating IP address was allocated." -msgstr "" - -#: ../cli_swift_archive_auto_extract.rst:37 -msgid "" -"For example, if the first object in the tar archive is ``/home/file1.txt`` " -"and you specify the ``/v1/12345678912345/mybackup/castor/`` path, the " -"operation creates the ``castor/home/file1.txt`` object in the ``mybackup`` " -"container in the ``12345678912345`` account." -msgstr "" - -#: ../dashboard_databases.rst:36 -msgid "" -"For example, if your MySQL datastore name is set to ``mysql``, your entry " -"would look like this:" -msgstr "" - -#: ../cli_swift_serialized_response_formats.rst:38 -msgid "" -"For example, this request uses the ``format`` query parameter to ask for a " -"JSON response:" -msgstr "" - -#: ../cli_nova_configure_access_security_for_instances.rst:178 -msgid "" -"For example, to delete the security group rule that permits SSH access from " -"all IP addresses, run the following command::" -msgstr "" - -# #-#-#-#-# cli_manage_ip_addresses.pot (End User Guide 1.0.0) #-#-#-#-# -# #-#-#-#-# cli_nova_launch_instance_from_volume.pot (End User Guide 1.0.0) #-#-#-#-# -#: ../cli_manage_ip_addresses.rst:102 -#: ../cli_nova_launch_instance_from_volume.rst:172 -msgid "For example::" -msgstr "" - -#: ../cli_access_instance_through_a_console.rst:50 -msgid "" -"For further information and comparisons (including security considerations), " -"see the `Security Guide `__." -msgstr "" - -#: ../cli_create_and_manage_networks.rst:125 -msgid "" -"For information and examples on more advanced use of neutron's ``subnet`` " -"subcommand, see the `Cloud Administrator Guide `__." -msgstr "" - -#: ../cli_config_drive.rst:267 -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 " -"format because ISO 9660 is widely supported across operating systems. " -"However, to use the VFAT format, add the following line to the :file:`/etc/" -"nova/nova.conf` file::" -msgstr "" - -# #-#-#-#-# cli_swift_archive_auto_extract.pot (End User Guide 1.0.0) #-#-#-#-# -# #-#-#-#-# cli_swift_bulk_delete.pot (End User Guide 1.0.0) #-#-#-#-# -#: ../cli_swift_archive_auto_extract.rst:85 ../cli_swift_bulk_delete.rst:62 -msgid "Formats response as JSON." -msgstr "" - -# #-#-#-#-# cli_swift_archive_auto_extract.pot (End User Guide 1.0.0) #-#-#-#-# -# #-#-#-#-# cli_swift_bulk_delete.pot (End User Guide 1.0.0) #-#-#-#-# -#: ../cli_swift_archive_auto_extract.rst:88 -#: ../cli_swift_archive_auto_extract.rst:91 ../cli_swift_bulk_delete.rst:65 -msgid "Formats response as XML." -msgstr "" - -# #-#-#-#-# cli_swift_archive_auto_extract.pot (End User Guide 1.0.0) #-#-#-#-# -# #-#-#-#-# cli_swift_bulk_delete.pot (End User Guide 1.0.0) #-#-#-#-# -#: ../cli_swift_archive_auto_extract.rst:81 ../cli_swift_bulk_delete.rst:58 -msgid "" -"Formats response as plain text. If you omit the ``Accept`` header, ``text/" -"plain`` is the default." -msgstr "" - -#: ../dashboard_manage_volumes.rst:119 -msgid "From the :guilabel:`More` list, select :guilabel:`Create Snapshot`." -msgstr "" - -# #-#-#-#-# configure_access_and_security_for_instances.pot (End User Guide 1.0.0) #-#-#-#-# -# #-#-#-#-# dashboard_create_networks.pot (End User Guide 1.0.0) #-#-#-#-# -# #-#-#-#-# dashboard_databases.pot (End User Guide 1.0.0) #-#-#-#-# -# #-#-#-#-# dashboard_launch_instances.pot (End User Guide 1.0.0) #-#-#-#-# -# #-#-#-#-# dashboard_manage_containers.pot (End User Guide 1.0.0) #-#-#-#-# -# #-#-#-#-# dashboard_manage_images.pot (End User Guide 1.0.0) #-#-#-#-# -# #-#-#-#-# dashboard_manage_volumes.pot (End User Guide 1.0.0) #-#-#-#-# -# #-#-#-#-# dashboard_stacks.pot (End User Guide 1.0.0) #-#-#-#-# -#: ../configure_access_and_security_for_instances.rst:49 -#: ../configure_access_and_security_for_instances.rst:100 -#: ../configure_access_and_security_for_instances.rst:123 -#: ../configure_access_and_security_for_instances.rst:179 -#: ../dashboard_create_networks.rst:21 ../dashboard_create_networks.rst:73 -#: ../dashboard_databases.rst:62 ../dashboard_databases.rst:117 -#: ../dashboard_databases.rst:148 ../dashboard_databases.rst:177 -#: ../dashboard_databases.rst:200 ../dashboard_launch_instances.rst:35 -#: ../dashboard_launch_instances.rst:199 ../dashboard_launch_instances.rst:232 -#: ../dashboard_manage_containers.rst:21 ../dashboard_manage_containers.rst:42 -#: ../dashboard_manage_containers.rst:75 ../dashboard_manage_containers.rst:98 -#: ../dashboard_manage_containers.rst:129 -#: ../dashboard_manage_containers.rst:157 ../dashboard_manage_images.rst:29 -#: ../dashboard_manage_images.rst:96 ../dashboard_manage_images.rst:126 -#: ../dashboard_manage_volumes.rst:16 ../dashboard_manage_volumes.rst:68 -#: ../dashboard_manage_volumes.rst:111 ../dashboard_manage_volumes.rst:133 -#: ../dashboard_manage_volumes.rst:139 ../dashboard_manage_volumes.rst:165 -#: ../dashboard_stacks.rst:29 ../dashboard_stacks.rst:124 -#: ../dashboard_stacks.rst:144 -msgid "" -"From the CURRENT PROJECT on the :guilabel:`Project` tab, select the " -"appropriate project." -msgstr "" - -#: ../cli_launch_instances.rst:74 -msgid "Gather parameters to launch an instance" -msgstr "" - -#: ../sdk_neutron_apis.rst:318 -msgid "" -"Get Nova Credentials. See :ref:'Get Nova credentials '." -msgstr "" - -#: ../sdk_neutron_apis.rst:61 -msgid "Get Nova credentials" -msgstr "" - -#: ../sdk_compute_apis.rst:58 ../sdk_compute_apis.rst:181 -msgid "" -"Get Nova credentials. See :ref:`Get OpenStack credentials (API v2) `." -msgstr "" - -#: ../sdk_compute_apis.rst:280 -msgid "" -"Get OpenStack Credentials. See :ref:`Get OpenStack credentials (API v2) `." -msgstr "" - -#: ../sdk_compute_apis.rst:20 -msgid "Get OpenStack credentials (API v2)" -msgstr "" - -#: ../sdk_compute_apis.rst:374 -msgid "" -"Get OpenStack credentials. :ref:`Get OpenStack credentials (API v2) `." -msgstr "" - -#: ../sdk_compute_apis.rst:102 ../sdk_compute_apis.rst:444 -#: ../sdk_compute_apis.rst:511 -msgid "" -"Get OpenStack credentials. See :ref:`Get OpenStack credentials (API v2) `." -msgstr "" - -#: ../sdk_neutron_apis.rst:34 -msgid "Get credentials" -msgstr "" - -#: ../sdk_neutron_apis.rst:603 -msgid "Get credentials. See :ref:'Get credentials '." -msgstr "" - -#: ../sdk_neutron_apis.rst:417 ../sdk_neutron_apis.rst:499 -msgid "" -"Get credentials. See :ref:`Get Nova credentials `." -msgstr "" - -#: ../sdk_neutron_apis.rst:553 -msgid "Get credentials. See :ref:`Get credentials `." -msgstr "" - -#: ../sdk_manage_images.rst:88 -msgid "Get image by ID" -msgstr "" - -#: ../sdk_manage_images.rst:103 -msgid "Get image by name" -msgstr "" - -#: ../cli_create_and_manage_stacks.rst:62 -msgid "Get information about stacks" -msgstr "" - -#: ../manage_db_config.rst:168 -msgid "Get the ID of the configuration group:" -msgstr "" - -#: ../manage_db_config.rst:157 -msgid "Get the ID of the database instance:" -msgstr "" - -#: ../set_up_replication.rst:25 -msgid "Get the ID of the original instance you want to replicate:" -msgstr "" - -#: ../sdk_compute_apis.rst:112 -msgid "" -"Get the flavor and image to use to create a server. This code uses the " -"``cirros`` image, the ``m1.tiny`` flavor, and the ``private`` network:" -msgstr "" - -#: ../cli_use_snapshots_to_migrate_instances.rst:75 -msgid "Get the image ID::" -msgstr "" - -#: ../sdk_compute_apis.rst:291 -msgid "" -"Get the server instance using ``server_id`` and print the details by calling " -"``print_server`` method:" -msgstr "" - -#: ../sdk_compute_apis.rst:309 -msgid "Get the updated instance of the server:" -msgstr "" - -#: ../dashboard_manage_shares.rst:233 -msgid "" -"Go to the security service that you want to edit and choose :guilabel:`Edit " -"Security Service` from Actions." -msgstr "" - -#: ../dashboard_manage_shares.rst:170 -msgid "" -"Go to the share network that you want to edit and choose :guilabel:`Edit " -"Share Network` from Actions." -msgstr "" - -#: ../dashboard_manage_shares.rst:55 -msgid "" -"Go to the share that you want to allow access and choose :guilabel:`Manage " -"Rules` from Actions." -msgstr "" - -#: ../dashboard_manage_shares.rst:75 -msgid "" -"Go to the share that you want to deny access and choose :guilabel:`Manage " -"Rules` from Actions." -msgstr "" - -#: ../dashboard_manage_shares.rst:89 -msgid "" -"Go to the share that you want to edit and choose :guilabel:`Edit Share " -"Metadata` from Actions." -msgstr "" - -#: ../dashboard_manage_shares.rst:104 -msgid "" -"Go to the share that you want to edit and choose :guilabel:`Edit Share` from " -"Actions." -msgstr "" - -#: ../dashboard_manage_shares.rst:120 -msgid "" -"Go to the share that you want to edit and choose :guilabel:`Extend Share` " -"from Actions." -msgstr "" - -#: ../hot.rst:3 -msgid "HOT Guide" -msgstr "" - -#: ../sdk.rst:15 -msgid "HTTP/1.1" -msgstr "" - -#: ../create_db.rst:26 -msgid "" -"Here are the default flavors, although you may have additional custom " -"flavors in your environment:" -msgstr "" - -#: ../cli_cheat_sheet.rst:5 -msgid "Here is a list of common commands for reference." -msgstr "" - -#: ../intro-user.rst:3 -msgid "How can I use an OpenStack cloud?" -msgstr "" - -#: ../configure_access_and_security_for_instances.rst:170 -msgid "" -"However, in addition to the fixed IP address, a floating IP address can also " -"be attached to an instance. Unlike fixed IP addresses, floating IP addresses " -"can have their associations modified at any time, regardless of the state of " -"the instances involved. This procedure details the reservation of a floating " -"IP address from an existing pool of addresses and the association of that " -"address with a specific instance." -msgstr "" - -#: ../backup_db_incremental.rst:21 -msgid "" -"ID of the instance (``INSTANCE_ID``): ``792a6a56-278f-4a01-9997-" -"d997fa126370``" -msgstr "" - -#: ../backup_db_incremental.rst:24 -msgid "" -"ID of the regular backup artifact (``BACKUP_ID``): " -"``6dc3a9b7-1f3e-4954-8582-3f2e4942cddd``" -msgstr "" - -#: ../cli_cheat_sheet.rst:8 -msgid "Identity (keystone)" -msgstr "" - -#: ../cli_config_drive.rst:99 -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:52 -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 " -"boot, reads the data from the drive, and takes appropriate action such as " -"adding the public key to an account. You can read more details about how " -"data is organized on the configuration drive." -msgstr "" - -#: ../cli_nova_configure_access_security_for_instances.rst:13 -msgid "" -"If an image uses a static root password or a static key set (neither is " -"recommended), you must not provide a key pair when you launch the instance." -msgstr "" - -#: ../cli_manage_ip_addresses.rst:122 -msgid "" -"If an instance is connected to multiple networks, you can associate a " -"floating IP address with a specific fixed IP address using the optional ``--" -"fixed-address`` parameter:" -msgstr "" - -#: ../cli_swift_large_object_creation.rst:131 -msgid "" -"If everything matches, the manifest object is created. The ``X-Static-Large-" -"Object`` metadata is set to ``true`` indicating that this is a static object " -"manifest." -msgstr "" - -#: ../cli_manage_ip_addresses.rst:81 -msgid "" -"If more than one IP address pool is available, you can specify from which " -"pool to allocate the IP address, using the pool's name. For example, to " -"allocate a floating IP address from the ``test`` pool, run::" -msgstr "" - -#: ../cli_launch_instances.rst:49 -msgid "" -"If needed, you can assign a **floating (public) IP address** to a running " -"instance." -msgstr "" - -#: ../sdk_authenticate_against_identity_endpoint.rst:31 -msgid "" -"If the OpenStack cloud is configured to use public-key infrastructure (PKI) " -"tokens, the Python script output looks something like this::" -msgstr "" - -#: ../dashboard_launch_instances.rst:126 -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 "" - -#: ../set_up_replication.rst:101 -msgid "" -"If the original instance goes down, you can detach the replica. The replica " -"becomes a standalone database instance. You can then take the new standalone " -"instance and create a new replica of that instance." -msgstr "" - -#: ../cli_change_the_size_of_your_server.rst:102 -msgid "" -"If the resize fails or does not work as expected, you can revert the resize. " -"For example::" -msgstr "" - -#: ../sdk_compute_apis.rst:214 -msgid "" -"If the server exists, run the ``delete`` method of the ``nova_client." -"servers`` object:" -msgstr "" - -#: ../cli_launch_instances.rst:259 -msgid "If the status for the instance is ACTIVE, the instance is online." -msgstr "" - -#: ../cli_manage_ip_addresses.rst:43 -msgid "" -"If this list is empty, the cloud administrator must configure a pool of " -"floating IP addresses." -msgstr "" - -#: ../sdk_compute_apis.rst:197 -msgid "" -"If true, set the variable name ``server_exists`` to ``True`` and break from " -"the for loop:" -msgstr "" - -#: ../cli_create_and_manage_stacks.rst:59 -msgid "If validation fails, the response returns an error message." -msgstr "" - -#: ../cli_launch_instances.rst:121 -msgid "" -"If you are an admin user, specify the ``--all-tenants`` parameter to list " -"groups for all tenants." -msgstr "" - -#: ../configure_access_and_security_for_instances.rst:147 -msgid "" -"If you are using the dashboard from a Windows computer, use PuTTYgen to load " -"the ``*.pem`` file and convert and save it as ``*.ppk``. For more " -"information see the `WinSCP web page for PuTTYgen `__." -msgstr "" - -#: ../sdk_authenticate_against_compute_endpoint.rst:36 -msgid "" -"If you authenticate against an endpoint that uses a custom authentication " -"back end, you must load the authentication plug-in and pass it to the " -"constructor." -msgstr "" - -#: ../cli_launch_instances.rst:169 -msgid "" -"If you boot an instance with an INSTANCE_NAME greater than 63 characters, " -"Compute truncates it automatically when turning it into a hostname to ensure " -"the correct work of dnsmasq. The corresponding warning is written into the " -"nova-network.log file." -msgstr "" - -#: ../cli_config_drive.rst:275 -msgid "If you choose VFAT, the configuration drive is 64 MB." -msgstr "" - -#: ../dashboard_create_networks.rst:104 -msgid "" -"If you choose not to set the :guilabel:`IP Address` value, then by default " -"OpenStack Networking uses the first host IP address in the subnet." -msgstr "" - -#: ../dashboard_launch_instances.rst:89 -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 -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 -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:169 -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 "" - -#: ../cli_launch_instances.rst:268 -msgid "" -"If you did not provide a key pair, security groups, or rules, you can access " -"the instance only from inside the cloud through VNC. Even pinging the " -"instance is not possible." -msgstr "" - -#: ../create_db.rst:57 -msgid "" -"If you have a custom flavor that meets the needs of the database that you " -"want to create, proceed to :ref:`Step 2 ` and use " -"that flavor." -msgstr "" - -#: ../cli_swift_large_lists.rst:5 -msgid "" -"If you have a large number of containers or objects, you can use the " -"``marker``, ``limit``, and ``end_marker`` parameters to control how many " -"items are returned in a list and where the list starts or ends." -msgstr "" - -#: ../cli_nova_configure_access_security_for_instances.rst:81 -msgid "" -"If you have already generated a key pair and the public key is located at " -"``~/.ssh/id_rsa.pub``, run the following command to upload the public key::" -msgstr "" - -#: ../sdk_configure_access_security_instances.rst:69 -msgid "" -"If you have already generated a keypair with the public key located at ``~/." -"ssh/id_rsa.pub``, pass the contents of the file to the `novaclient.v1\\_1." -"keypairs.KeypairManager.create `__ method to import the public key to Compute:" -msgstr "" - -#: ../configure_access_and_security_for_instances.rst:18 -msgid "" -"If you have generated a key pair with an external tool, you can import it " -"into OpenStack. The key pair can be used for multiple instances that belong " -"to a project. For more information, see the section :ref:" -"`dashboard_import_keypair`." -msgstr "" - -#: ../dashboard_launch_instances.rst:136 -msgid "" -"If you have not created any security groups, you can assign only the default " -"security group to the instance." -msgstr "" - -#: ../cli_launch_instances.rst:136 -msgid "" -"If you have not created any security groups, you can assign the instance to " -"only the default security group." -msgstr "" - -#: ../cli_swift_large_object_creation.rst:46 -msgid "" -"If you make a ``COPY`` request by using a manifest object as the source, the " -"new object is a normal, and not a segment, object. If the total size of the " -"source segment objects exceeds 5 GB, the ``COPY`` request fails. However, " -"you can make a duplicate of the manifest object and this new object can be " -"larger than 5 GB." -msgstr "" - -#: ../sdk_authenticate_against_compute_endpoint.rst:65 -msgid "" -"If you set the ``OS_AUTH_SYSTEM`` environment variable, check for this " -"variable in your Python script to determine whether you need to load a " -"custom authentication back end:" -msgstr "" - -#: ../cli_swift_manage_access_swift.rst:24 -msgid "" -"If you use StaticWeb middleware to enable Object Storage to serve public web " -"content, use ``.r:``, followed by a list of allowed referrers." -msgstr "" - -#: ../cli_config_drive.rst:58 -msgid "" -"If you use Xen with a configuration drive, use the ``xenapi_disable_agent`` " -"configuration parameter to disable the agent." -msgstr "" - -#: ../cli_swift_large_object_creation.rst:142 -msgid "" -"If you use the ``DELETE`` operation on a manifest object, the manifest " -"object is deleted. The segment objects are not affected. However, if you add " -"the ``?multipart-manifest=delete`` query parameter, the segment objects are " -"deleted and if all are successfully deleted, the manifest object is also " -"deleted." -msgstr "" - -#: ../cli_manage_bare_metal_nodes.rst:11 -msgid "" -"If you use the bare-metal driver, you must create a network interface and " -"add it to a bare-metal node. Then, you can launch an instance from a bare-" -"metal image." -msgstr "" - -#: ../cli_reboot_an_instance.rst:64 -msgid "" -"If you want to rescue an instance with a specific image, rather than the " -"default one, use the ``--rescue_image_ref`` parameter::" -msgstr "" - -#: ../create_db.rst:61 -msgid "" -"If your environment does not have a suitable flavor, an administrative user " -"must create a custom flavor by using the nova ``flavor-create`` command." -msgstr "" - -#: ../cli_config_drive.rst:117 -msgid "" -"If your guest operating system does not use ``udev``, the ``/dev/disk/by-" -"label`` directory is not present." -msgstr "" - -#: ../cli_config_drive.rst:103 -msgid "" -"If your guest operating system supports accessing disk by label, you can " -"mount the configuration drive as the ``/dev/disk/by-label/" -"configurationDriveVolumeLabel`` device. In the following example, the " -"configuration drive has the ``config-2`` volume label::" -msgstr "" - -#: ../dashboard_launch_instances.rst:119 -msgid "Image Name" -msgstr "" - -#: ../dashboard_launch_instances.rst:9 -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 " -"iSCSI." -msgstr "" - -#: ../dashboard_manage_volumes.rst:43 -msgid "" -"Image: If you choose this option, a new field for Use image as a source " -"displays. You can select the image from the list." -msgstr "" - -#: ../cli_cheat_sheet.rst:23 -msgid "Images (glance)" -msgstr "" - -#: ../dashboard_launch_instances.rst:7 -msgid "Images uploaded to the OpenStack Image service." -msgstr "" - -# #-#-#-#-# cli_nova_configure_access_security_for_instances.pot (End User Guide 1.0.0) #-#-#-#-# -# #-#-#-#-# configure_access_and_security_for_instances.pot (End User Guide 1.0.0) #-#-#-#-# -#: ../cli_nova_configure_access_security_for_instances.rst:79 -#: ../configure_access_and_security_for_instances.rst:119 -msgid "Import a key pair" -msgstr "" - -#: ../sdk_configure_access_security_instances.rst:67 -msgid "Import a keypair" -msgstr "" - -# #-#-#-#-# sdk_compute_apis.pot (End User Guide 1.0.0) #-#-#-#-# -# #-#-#-#-# sdk_neutron_apis.pot (End User Guide 1.0.0) #-#-#-#-# -#: ../sdk_compute_apis.rst:51 ../sdk_compute_apis.rst:94 -#: ../sdk_compute_apis.rst:173 ../sdk_compute_apis.rst:256 -#: ../sdk_compute_apis.rst:353 ../sdk_compute_apis.rst:420 -#: ../sdk_compute_apis.rst:489 ../sdk_neutron_apis.rst:307 -#: ../sdk_neutron_apis.rst:410 ../sdk_neutron_apis.rst:490 -#: ../sdk_neutron_apis.rst:545 ../sdk_neutron_apis.rst:595 -msgid "Import the following modules:" -msgstr "" - -#: ../cli_use_snapshots_to_migrate_instances.rst:103 -msgid "Import the snapshot to the new environment" -msgstr "" - -#: ../cli_cheat_sheet.rst:120 -msgid "" -"In CirrOS the password for user ``cirros`` is \"cubswin:)\" without the " -"quotes." -msgstr "" - -#: ../dashboard_manage_containers.rst:11 -msgid "" -"In OpenStack Object Storage, containers provide storage for objects in a " -"manner similar to a Windows folder or Linux file directory, though they " -"cannot be nested. An object in OpenStack consists of the file to be stored " -"in the container and any accompanying metadata." -msgstr "" - -#: ../intro-user.rst:20 -msgid "" -"In addition to these ways of interacting with a cloud, you can access the " -"OpenStack APIs directly or indirectly through `cURL `__ " -"commands or open SDKs. You can automate access or build tools to manage " -"resources and services by using the native OpenStack APIs or the EC2 " -"compatibility API." -msgstr "" - -#: ../create_db.rst:99 -msgid "In addition, this command specifies these options for the instance:" -msgstr "" - -#: ../cli_swift_bulk_delete.rst:31 -msgid "In addition, you must:" -msgstr "" - -#: ../cli_config_drive.rst:279 -msgid "" -"In current version (Kilo) of OpenStack Compute, live migration with " -"``config_drive`` on local disk is forbidden due to the bug in libvirt of " -"copying a read-only disk. However, if we use VFAT as the format of " -"``config_drive``, the function of live migration works well." -msgstr "" - -#: ../cli_swift_discoverability.rst:46 -msgid "" -"In some cases, the ``/info`` request will return an error. This could be " -"because your service provider has disabled the ``/info`` request function, " -"or because you are using an older version that does not support it." -msgstr "" - -#: ../dashboard_launch_instances.rst:217 -msgid "In the :guilabel:`Actions` column, click :guilabel:`Create Snapshot`." -msgstr "" - -#: ../dashboard_manage_volumes.rst:146 -msgid "In the :guilabel:`Actions` column, click :guilabel:`Edit Volume`." -msgstr "" - -#: ../dashboard_manage_images.rst:104 -msgid "" -"In the :guilabel:`Actions` column, click :guilabel:`More` and then select :" -"guilabel:`Edit` from the list." -msgstr "" - -#: ../dashboard_create_networks.rst:99 -msgid "" -"In the :guilabel:`Add Interface` dialog box, select a :guilabel:`Subnet`." -msgstr "" - -#: ../configure_access_and_security_for_instances.rst:61 -#: ../configure_access_and_security_for_instances.rst:79 -msgid "In the :guilabel:`Add Rule` dialog box, enter the following values:" -msgstr "" - -#: ../dashboard_databases.rst:126 -msgid "" -"In the :guilabel:`Backup Database` dialog box, specify the following values:" -msgstr "" - -#: ../dashboard_manage_images.rst:136 -msgid "" -"In the :guilabel:`Confirm Delete Image` dialog box, click :guilabel:`Delete " -"Images` to confirm the deletion." -msgstr "" - -#: ../dashboard_manage_containers.rst:108 -msgid "" -"In the :guilabel:`Copy Object` launch dialog box, enter the following values:" -msgstr "" - -#: ../dashboard_manage_containers.rst:29 -msgid "" -"In the :guilabel:`Create Container` dialog box, enter a name for the " -"container, and then click :guilabel:`Create Container`." -msgstr "" - -#: ../configure_access_and_security_for_instances.rst:111 -msgid "" -"In the :guilabel:`Create Key Pair` dialog box, enter a name for your key " -"pair, and click :guilabel:`Create Key Pair`." -msgstr "" - -#: ../dashboard_create_networks.rst:29 -msgid "" -"In the :guilabel:`Create Network` dialog box, specify the following values." -msgstr "" - -#: ../dashboard_create_networks.rst:81 -msgid "" -"In the :guilabel:`Create Router` dialog box, specify a name for the router " -"and click :guilabel:`Create Router`." -msgstr "" - -#: ../dashboard_launch_instances.rst:219 -msgid "" -"In the :guilabel:`Create Snapshot` dialog box, enter a name for the " -"snapshot, and click :guilabel:`Create Snapshot`." -msgstr "" - -#: ../dashboard_manage_volumes.rst:148 -msgid "" -"In the :guilabel:`Edit Volume` dialog box, update the name and description " -"of the image." -msgstr "" - -#: ../dashboard_create_networks.rst:88 -msgid "" -"In the :guilabel:`External Network` field, specify the network to which the " -"router will connect, and then click :guilabel:`Set Gateway`." -msgstr "" - -#: ../configure_access_and_security_for_instances.rst:194 -msgid "In the :guilabel:`Floating IPs` list, click :guilabel:`Associate`." -msgstr "" - -#: ../configure_access_and_security_for_instances.rst:134 -msgid "" -"In the :guilabel:`Import Key Pair` dialog box, enter the name of your key " -"pair, copy the public key into the :guilabel:`Public Key` box, and then " -"click :guilabel:`Import Key Pair`." -msgstr "" - -#: ../dashboard_databases.rst:71 -msgid "" -"In the :guilabel:`Launch Database` dialog box, specify the following values." -msgstr "" - -#: ../dashboard_databases.rst:156 -msgid "" -"In the :guilabel:`Launch Database` dialog box, specify the values you want " -"for the new database instance." -msgstr "" - -#: ../dashboard_launch_instances.rst:50 -msgid "" -"In the :guilabel:`Launch Instance` dialog box, specify the following values:" -msgstr "" - -#: ../dashboard_stacks.rst:60 -msgid "" -"In the :guilabel:`Launch Stack` dialog box, specify the following values:" -msgstr "" - -#: ../configure_access_and_security_for_instances.rst:196 -msgid "" -"In the :guilabel:`Manage Floating IP Associations` dialog box, choose the " -"following options:" -msgstr "" - -#: ../dashboard_manage_volumes.rst:77 -msgid "" -"In the :guilabel:`Manage Volume Attachments` dialog box, select an instance." -msgstr "" - -#: ../dashboard_launch_instances.rst:240 -msgid "" -"In the :guilabel:`More` list in the :guilabel:`Actions` column, select the " -"state." -msgstr "" - -#: ../configure_access_and_security_for_instances.rst:203 -msgid "" -"In the :guilabel:`Port to be associated` field, select a port from the list." -msgstr "" - -#: ../dashboard_databases.rst:211 -msgid "" -"In the :guilabel:`Resize Database Instance` dialog box, expand the drop down " -"menu in the :guilabel:`New Flavor` field. Select the new flavor you want for " -"the instance." -msgstr "" - -#: ../dashboard_databases.rst:188 -msgid "" -"In the :guilabel:`Resize Database Volume` dialog box, fill in the :guilabel:" -"`New Size` field with an integer indicating the new size you want for the " -"instance. Express the size in GB, and note that the new size must be larger " -"than the current size." -msgstr "" - -#: ../dashboard_stacks.rst:130 -msgid "" -"In the :guilabel:`Select Template` dialog box, select the new template " -"source or environment source." -msgstr "" - -#: ../dashboard_stacks.rst:34 -msgid "" -"In the :guilabel:`Select Template` dialog box, specify the following values:" -msgstr "" - -#: ../dashboard_manage_images.rst:107 -msgid "" -"In the :guilabel:`Update Image` dialog box, you can perform the following " -"actions:" -msgstr "" - -#: ../cli_swift_archive_auto_extract.rst:29 -msgid "In the ``PUT`` request, you can specify the path for:" -msgstr "" - -#: ../dashboard_stacks.rst:150 -msgid "" -"In the confirmation dialog box, click :guilabel:`Delete Stack` to confirm " -"the deletion." -msgstr "" - -#: ../cli_use_snapshots_to_migrate_instances.rst:14 -msgid "In the destination project:" -msgstr "" - -#: ../dashboard_manage_volumes.rst:121 -msgid "" -"In the dialog box that opens, enter a snapshot name and a brief description." -msgstr "" - -# #-#-#-#-# dashboard_manage_shares.pot (End User Guide 1.0.0) #-#-#-#-# -# #-#-#-#-# dashboard_manage_volumes.pot (End User Guide 1.0.0) #-#-#-#-# -#: ../dashboard_manage_shares.rst:18 ../dashboard_manage_shares.rst:137 -#: ../dashboard_manage_shares.rst:189 ../dashboard_manage_volumes.rst:24 -msgid "In the dialog box that opens, enter or select the following values." -msgstr "" - -#: ../cli_use_snapshots_to_migrate_instances.rst:105 -msgid "In the new project or cloud environment, import the snapshot:" -msgstr "" - -#: ../cli_use_snapshots_to_migrate_instances.rst:116 -msgid "" -"In the new project or cloud environment, use the snapshot to create the new " -"instance::" -msgstr "" - -#: ../cli_create_and_manage_networks.rst:190 -msgid "" -"In the previous command, ``net1`` is the network name, which is a positional " -"argument. ``--fixed-ip ip_address=192.168.2.40`` is an option, which " -"specifies the port's fixed IP address we wanted." -msgstr "" - -#: ../cli_swift_bulk_delete.rst:26 -msgid "" -"In the request body of the ``POST`` or ``DELETE`` operation, list the " -"objects or containers to be deleted. Separate each name with a newline " -"character. You can include a maximum of 10,000 items (configurable) in the " -"list." -msgstr "" - -#: ../cli_use_snapshots_to_migrate_instances.rst:8 -msgid "In the source project:" -msgstr "" - -#: ../cli_nova_launch_instance_using_ISO_image.rst:53 -msgid "" -"In this command, ``ubuntu-14.04.2-server-amd64.iso`` is the ISO image, and " -"``INSTANCE_NAME`` is the name of the new instance. ``NETWORK_UUID`` is a " -"valid network id in your system." -msgstr "" - -#: ../cli_create_and_manage_networks.rst:122 -msgid "In this example, ``--name subnet1`` specifies the name of the subnet." -msgstr "" - -#: ../cli_create_and_manage_networks.rst:117 -msgid "" -"In this example, ``192.168.2.0/24`` is a positional argument that specifies " -"the CIDR." -msgstr "" - -#: ../cli_create_and_manage_networks.rst:112 -msgid "" -"In this example, ``net1`` is a positional argument that specifies the " -"network name." -msgstr "" - -#: ../sdk_schedule_objects_for_deletion.rst:47 -msgid "" -"In this example, the ``X-Delete-After`` header is set to 864000 seconds. The " -"object expires after this time." -msgstr "" - -#: ../sdk_schedule_objects_for_deletion.rst:38 -msgid "" -"In this example, the ``X-Delete-At`` header is assigned a UNIX epoch " -"timestamp in integer form for ``Mon, 11 Jun 2012 15:38:25 GMT``." -msgstr "" - -#: ../manage_db_config.rst:83 -msgid "" -"In this example, the ``configuration-parameter-list`` command returns a list " -"of options that work with MySQL 5.5." -msgstr "" - -#: ../cli_config_drive.rst:141 -msgid "" -"In this example, the contents of the configuration drive are as follows::" -msgstr "" - -#: ../cli_swift_pseudo_hierarchical_folders_directories.rst:14 -msgid "" -"In this example, the objects reside in a container called ``backups``. " -"Within that container, the objects are organized in a pseudo-directory " -"called ``photos``. The container name is not displayed in the example, but " -"it is a part of the object URLs. For instance, the URL of the picture ``me." -"jpg`` is ``https://storage.swiftdrive.com/v1/CF_xer7_343/backups/photos/me." -"jpg``." -msgstr "" - -#: ../cli_swift_large_object_creation.rst:304 -msgid "" -"Include the ``?multipart-manifest=get`` query string in the ``COPY`` " -"request. The new object contains the same manifest as the original. The " -"segment objects are not copied. Instead, both the original and new manifest " -"objects share the same set of segment objects." -msgstr "" - -#: ../cli_swift_set_object_versions.rst:40 -msgid "" -"Include the ``X-Versions-Location`` header. This header defines the " -"container that holds the non-current versions of your objects. You must " -"UTF-8-encode and then URL-encode the container name before you include it in " -"the ``X-Versions-Location`` header. This header enables object versioning " -"for all objects in the ``current`` container. Changes to objects in the " -"``current`` container automatically create non-current versions in the " -"``archive`` container." -msgstr "" - -#: ../cli_swift_serialized_response_formats.rst:22 -msgid "" -"Include this header in the ``GET`` request. The valid header values are:" -msgstr "" - -#: ../backup_db_incremental.rst:5 -msgid "" -"Incremental backups let you chain together a series of backups. You start " -"with a regular backup. Then, when you want to create a subsequent " -"incremental backup, you specify the parent backup." -msgstr "" - -#: ../cli_nova_launch_instance_from_volume.rst:16 -msgid "Information" -msgstr "" - -#: ../cli_cheat_sheet.rst:229 -msgid "" -"Inject a keypair into an instance and access the instance with that keypair" -msgstr "" - -#: ../cli_cheat_sheet.rst:218 -msgid "Inject user data and files into an instance" -msgstr "" - -#: ../sdk_install.rst:2 -msgid "Installing OpenStack SDK" -msgstr "" - -#: ../dashboard_launch_instances.rst:114 -msgid "Instance Boot Source" -msgstr "" - -#: ../dashboard_launch_instances.rst:83 -msgid "Instance Count" -msgstr "" - -#: ../dashboard_launch_instances.rst:70 -msgid "Instance Name" -msgstr "" - -#: ../backup_db_incremental.rst:19 -msgid "Instance name: ``guest1``" -msgstr "" - -#: ../cli_manage_instances_hosts.rst:5 -msgid "" -"Instances are virtual machines that run inside the cloud on physical compute " -"nodes. The Compute service manages instances. A host is the node on which a " -"group of instances resides." -msgstr "" - -#: ../cli_launch_instances.rst:11 -msgid "Instances are virtual machines that run inside the cloud." -msgstr "" - -#: ../dashboard_launch_instances.rst:4 -msgid "" -"Instances are virtual machines that run inside the cloud. You can launch an " -"instance from the following sources:" -msgstr "" - -# #-#-#-#-# cli_launch_instances.pot (End User Guide 1.0.0) #-#-#-#-# -# #-#-#-#-# cli_nova_configure_access_security_for_instances.pot (End User Guide 1.0.0) #-#-#-#-# -#: ../cli_launch_instances.rst:57 -#: ../cli_nova_configure_access_security_for_instances.rst:51 -msgid "" -"Instances that use the default security group cannot, by default, be " -"accessed from any IP address outside of the cloud. If you want those IP " -"addresses to access the instances, you must modify the rules for the default " -"security group." -msgstr "" - -#: ../configure_access_and_security_for_instances.rst:89 -msgid "Instances will now accept all incoming ICMP packets." -msgstr "" - -#: ../configure_access_and_security_for_instances.rst:74 -msgid "" -"Instances will now have SSH port 22 open for requests from any IP address." -msgstr "" - -#: ../sdk_neutron_apis.rst:419 ../sdk_neutron_apis.rst:501 -#: ../sdk_neutron_apis.rst:555 ../sdk_neutron_apis.rst:605 -msgid "" -"Instantiate the ``neutron`` client object by using the ``credentials`` " -"dictionary object:" -msgstr "" - -# #-#-#-#-# sdk_compute_apis.pot (End User Guide 1.0.0) #-#-#-#-# -# #-#-#-#-# sdk_neutron_apis.pot (End User Guide 1.0.0) #-#-#-#-# -#: ../sdk_compute_apis.rst:61 ../sdk_compute_apis.rst:105 -#: ../sdk_compute_apis.rst:184 ../sdk_compute_apis.rst:283 -#: ../sdk_compute_apis.rst:377 ../sdk_compute_apis.rst:447 -#: ../sdk_compute_apis.rst:514 ../sdk_neutron_apis.rst:321 -msgid "" -"Instantiate the ``nova_client`` client object by using the ``credentials`` " -"dictionary object:" -msgstr "" - -#: ../cli_swift_set_object_versions.rst:142 -msgid "" -"Issue a ``DELETE`` request to a versioned object to remove the current " -"version of the object and replace it with the next-most current version in " -"the non-current container." -msgstr "" - -#: ../cli_swift_set_object_versions.rst:111 -msgid "" -"Issue a ``GET`` request to a versioned object to get the current version of " -"the object. You do not have to do any request redirects or metadata lookups." -msgstr "" - -#: ../cli_reboot_an_instance.rst:19 -msgid "" -"It is also possible to reboot a running instance into rescue mode. For " -"example, this operation may be required, if a filesystem of an instance " -"becomes corrupted with prolonged use." -msgstr "" - -#: ../cli_swift_large_object_creation.rst:177 -msgid "" -"It is best to upload all the segments first and then create or update the " -"manifest. With this method, the full object is not available for downloading " -"until the upload is complete. Also, you can upload a new set of segments to " -"a second location and update the manifest to point to this new location. " -"During the upload of the new segments, the original manifest is still " -"available to download the first set of segments." -msgstr "" - -#: ../sdk_compute_apis.rst:195 -msgid "Iterate over ``servers_list`` and compare name with ``vm1``." -msgstr "" - -#: ../sdk.rst:16 -msgid "JSON and XML data serialization formats" -msgstr "" - -#: ../cli_swift_serialized_response_formats.rst:28 -msgid "JSON data serialization response format." -msgstr "" - -#: ../cli_create_and_manage_networks.rst:80 -msgid "" -"Just as shown previously, the unknown option ``--provider:network-type`` is " -"used to create a ``local`` provider network." -msgstr "" - -#: ../configure_access_and_security_for_instances.rst:12 -msgid "" -"Key pairs are SSH credentials that are injected into an instance when it is " -"launched. To use key pair injection, the image that the instance is based on " -"must contain the ``cloud-init`` package. Each project should have at least " -"one key pair. For more information, see the section :ref:`keypair_add`." -msgstr "" - -#: ../dashboard_launch_instances.rst:128 -msgid "Keypair" -msgstr "" - -#: ../cli_swift_large_object_creation.rst:5 -msgid "Large objects" -msgstr "" - -#: ../backup_db.rst:70 -msgid "" -"Later on, use the trove ``backup-list`` command to get this information:" -msgstr "" - -#: ../dashboard_stacks.rst:26 -msgid "Launch a stack" -msgstr "" - -#: ../dashboard_launch_instances.rst:14 -msgid "Launch an instance" -msgstr "" - -#: ../cli_manage_bare_metal_nodes.rst:101 -msgid "Launch an instance from a bare-metal image" -msgstr "" - -#: ../cli_nova_launch_instance_from_volume.rst:3 -msgid "Launch an instance from a volume" -msgstr "" - -#: ../cli_launch_instances.rst:151 -msgid "Launch an instance from an image" -msgstr "" - -#: ../cli_nova_launch_instance_using_ISO_image.rst:3 -msgid "Launch an instance using ISO image" -msgstr "" - -#: ../dashboard_launch_instances.rst:3 -msgid "Launch and manage instances" -msgstr "" - -#: ../dashboard_stacks.rst:3 -msgid "Launch and manage stacks" -msgstr "" - -#: ../cli_launch_instances.rst:3 -msgid "Launch instances" -msgstr "" - -#: ../dashboard_manage_images.rst:69 -msgid "Leave these fields empty." -msgstr "" - -#: ../cli_swift_large_lists.rst:28 -msgid "" -"Limits the result set to names that are less than the ``end_marker`` " -"parameter value. You must URL-encode the ``end_marker`` value before you " -"send the HTTP request." -msgstr "" - -#: ../cli_create_and_manage_networks.rst:151 -msgid "Link the router to the external provider network::" -msgstr "" - -#: ../cli_create_and_manage_networks.rst:158 -msgid "Link the router to the subnet::" -msgstr "" - -#: ../cli_cheat_sheet.rst:16 -msgid "List Identity service catalog" -msgstr "" - -#: ../sdk_neutron_apis.rst:562 -msgid "List Security groups" -msgstr "" - -#: ../cli_delete_an_instance.rst:7 -msgid "List all instances::" -msgstr "" - -#: ../cli_manage_ip_addresses.rst:87 -msgid "" -"List all project instances with which a floating IP address could be " -"associated::" -msgstr "" - -#: ../set_up_clustering.rst:137 -msgid "" -"List all the clusters in your system, using the trove ``cluster-list`` " -"command." -msgstr "" - -#: ../cli_cheat_sheet.rst:10 -msgid "List all users" -msgstr "" - -#: ../cli_manage_bare_metal_nodes.rst:134 -msgid "List bare-metal nodes and interfaces" -msgstr "" - -#: ../cli_cheat_sheet.rst:362 -msgid "List containers" -msgstr "" - -#: ../cli_cheat_sheet.rst:97 -msgid "List flavors" -msgstr "" - -#: ../sdk_compute_apis.rst:348 -msgid "List flavors (API v2)" -msgstr "" - -#: ../sdk_compute_apis.rst:384 -msgid "List flavors by calling ``list()`` on ``nova_client.flavors`` object:" -msgstr "" - -#: ../sdk_compute_apis.rst:397 -msgid "List flavors code listing example" -msgstr "" - -#: ../cli_manage_ip_addresses.rst:30 -msgid "List floating IP address information" -msgstr "" - -#: ../sdk_compute_apis.rst:415 -msgid "List floating IPs (API v2)" -msgstr "" - -#: ../sdk_compute_apis.rst:454 -msgid "" -"List floating IPs by calling ``list()`` on ``nova_client.floating_ips`` " -"object:" -msgstr "" - -#: ../sdk_compute_apis.rst:468 -msgid "List floating IPs code listing example" -msgstr "" - -#: ../sdk_compute_apis.rst:485 -msgid "List hosts (API v2)" -msgstr "" - -#: ../sdk_compute_apis.rst:521 -msgid "List hosts by calling ``list()`` on ``nova_client.hosts`` object:" -msgstr "" - -#: ../sdk_compute_apis.rst:534 -msgid "List hosts code listing example" -msgstr "" - -# #-#-#-#-# cli_cheat_sheet.pot (End User Guide 1.0.0) #-#-#-#-# -# #-#-#-#-# sdk_manage_images.pot (End User Guide 1.0.0) #-#-#-#-# -#: ../cli_cheat_sheet.rst:91 ../sdk_manage_images.rst:14 -msgid "List images" -msgstr "" - -#: ../cli_cheat_sheet.rst:25 -msgid "List images you can access" -msgstr "" - -#: ../cli_cheat_sheet.rst:85 -msgid "List instances, check status of instance" -msgstr "" - -#: ../sdk_configure_access_security_instances.rst:89 -msgid "List keypairs" -msgstr "" - -#: ../sdk_neutron_apis.rst:165 -msgid "List networks" -msgstr "" - -#: ../cli_swift_set_object_versions.rst:159 -msgid "" -"List objects in the ``archive`` container to show that the archived object " -"was moved back to the ``current`` container:" -msgstr "" - -#: ../cli_swift_set_object_versions.rst:115 -msgid "List older versions of the object in the ``archive`` container:" -msgstr "" - -#: ../sdk_neutron_apis.rst:234 -msgid "List ports" -msgstr "" - -#: ../cli_swift_pseudo_hierarchical_folders_directories.rst:22 -msgid "List pseudo-hierarchical folders request: HTTP" -msgstr "" - -#: ../sdk_neutron_apis.rst:486 -msgid "List routers" -msgstr "" - -#: ../sdk_neutron_apis.rst:520 -msgid "List routers: complete code listing example" -msgstr "" - -#: ../cli_ceilometer.rst:110 -msgid "List samples::" -msgstr "" - -#: ../sdk_neutron_apis.rst:541 -msgid "List security groups" -msgstr "" - -#: ../sdk_neutron_apis.rst:570 -msgid "List security groups: complete code listing example" -msgstr "" - -#: ../sdk_compute_apis.rst:75 -msgid "List server code listing example" -msgstr "" - -#: ../sdk_neutron_apis.rst:258 -msgid "List server ports" -msgstr "" - -#: ../sdk_compute_apis.rst:47 -msgid "List servers (API v2)" -msgstr "" - -#: ../sdk_compute_apis.rst:68 -msgid "List servers by calling ``servers.list`` on ``nova_client`` object:" -msgstr "" - -#: ../sdk_compute_apis.rst:193 -msgid "List servers: ``servers_list``." -msgstr "" - -#: ../cli_cheat_sheet.rst:313 -msgid "List storage devices" -msgstr "" - -#: ../sdk_neutron_apis.rst:591 -msgid "List subnets" -msgstr "" - -#: ../sdk_neutron_apis.rst:612 -msgid "List subnets:" -msgstr "" - -#: ../sdk_neutron_apis.rst:620 -msgid "List subnets: complete code listing example" -msgstr "" - -#: ../cli_ceilometer.rst:89 -msgid "List the alarms that are set::" -msgstr "" - -#: ../cli_change_the_size_of_your_server.rst:44 -msgid "List the available flavors with the following command::" -msgstr "" - -# #-#-#-#-# cli_launch_instances.pot (End User Guide 1.0.0) #-#-#-#-# -# #-#-#-#-# cli_nova_launch_instance_from_volume.pot (End User Guide 1.0.0) #-#-#-#-# -#: ../cli_launch_instances.rst:78 -#: ../cli_nova_launch_instance_from_volume.rst:154 -msgid "List the available flavors::" -msgstr "" - -# #-#-#-#-# cli_launch_instances.pot (End User Guide 1.0.0) #-#-#-#-# -# #-#-#-#-# cli_nova_launch_instance_from_volume.pot (End User Guide 1.0.0) #-#-#-#-# -#: ../cli_launch_instances.rst:94 -#: ../cli_nova_launch_instance_from_volume.rst:140 -msgid "List the available images::" -msgstr "" - -#: ../cli_launch_instances.rst:143 -msgid "" -"List the available key pairs, and note the key pair name that you use for " -"SSH access::" -msgstr "" - -#: ../cli_launch_instances.rst:115 -msgid "List the available security groups::" -msgstr "" - -#: ../cli_create_and_manage_networks.rst:17 -msgid "List the extensions of the system::" -msgstr "" - -#: ../cli_ceilometer.rst:72 -msgid "List the heat resources that were created::" -msgstr "" - -#: ../set_up_clustering.rst:103 -msgid "" -"List the instances in a cluster by using the trove ``cluster-instances`` " -"command." -msgstr "" - -#: ../cli_ceilometer.rst:99 -msgid "List the meters that are set::" -msgstr "" - -#: ../cli_swift_large_object_creation.rst:65 -msgid "" -"List the name of each segment object along with its size and MD5 checksum in " -"order." -msgstr "" - -#: ../manage_db_config.rst:25 -msgid "" -"List the names and IDs of all available versions of the ``mysql`` data store:" -msgstr "" - -#: ../sdk_neutron_apis.rst:508 -msgid "List the routers:" -msgstr "" - -#: ../cli_nova_launch_instance_from_volume.rst:250 -msgid "" -"List volumes to see the bootable volume and its attached " -"``myInstanceFromVolume`` instance::" -msgstr "" - -#: ../cli_cheat_sheet.rst:297 -msgid "List volumes, notice status of volume" -msgstr "" - -#: ../cli_nova_launch_instance_from_volume.rst:82 -msgid "List volumes::" -msgstr "" - -#: ../cli_manage_bare_metal_nodes.rst:40 -msgid "Lists available bare-metal nodes." -msgstr "" - -#: ../cli_manage_bare_metal_nodes.rst:28 -msgid "Lists network interfaces associated with a bare-metal node." -msgstr "" - -#: ../dashboard_launch_instances.rst:213 -msgid "" -"Log in to the dashboard, choose a project, and click :guilabel:`Instances`." -msgstr "" - -#: ../dashboard_manage_shares.rst:14 ../dashboard_manage_shares.rst:42 -#: ../dashboard_manage_shares.rst:53 ../dashboard_manage_shares.rst:73 -#: ../dashboard_manage_shares.rst:87 ../dashboard_manage_shares.rst:102 -#: ../dashboard_manage_shares.rst:118 -msgid "" -"Log in to the dashboard, choose a project, and click :guilabel:`Shares`." -msgstr "" - -#: ../dashboard_manage_volumes.rst:98 -msgid "" -"Log in to the dashboard, choose a project, and click :guilabel:`Volumes`." -msgstr "" - -#: ../dashboard_manage_shares.rst:184 ../dashboard_manage_shares.rst:218 -#: ../dashboard_manage_shares.rst:230 -msgid "" -"Log in to the dashboard, choose a project, click :guilabel:`Shares`, and " -"click :guilabel:`Security Services`." -msgstr "" - -#: ../dashboard_manage_shares.rst:132 ../dashboard_manage_shares.rst:155 -#: ../dashboard_manage_shares.rst:167 -msgid "" -"Log in to the dashboard, choose a project, click :guilabel:`Shares`, and " -"click :guilabel:`Share Networks`." -msgstr "" - -# #-#-#-#-# configure_access_and_security_for_instances.pot (End User Guide 1.0.0) #-#-#-#-# -# #-#-#-#-# dashboard_create_networks.pot (End User Guide 1.0.0) #-#-#-#-# -# #-#-#-#-# dashboard_databases.pot (End User Guide 1.0.0) #-#-#-#-# -# #-#-#-#-# dashboard_launch_instances.pot (End User Guide 1.0.0) #-#-#-#-# -# #-#-#-#-# dashboard_manage_containers.pot (End User Guide 1.0.0) #-#-#-#-# -# #-#-#-#-# dashboard_manage_images.pot (End User Guide 1.0.0) #-#-#-#-# -# #-#-#-#-# dashboard_manage_volumes.pot (End User Guide 1.0.0) #-#-#-#-# -# #-#-#-#-# dashboard_stacks.pot (End User Guide 1.0.0) #-#-#-#-# -#: ../configure_access_and_security_for_instances.rst:47 -#: ../configure_access_and_security_for_instances.rst:98 -#: ../configure_access_and_security_for_instances.rst:121 -#: ../configure_access_and_security_for_instances.rst:177 -#: ../dashboard_create_networks.rst:19 ../dashboard_create_networks.rst:71 -#: ../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:197 ../dashboard_launch_instances.rst:230 -#: ../dashboard_manage_containers.rst:19 ../dashboard_manage_containers.rst:40 -#: ../dashboard_manage_containers.rst:73 ../dashboard_manage_containers.rst:96 -#: ../dashboard_manage_containers.rst:127 -#: ../dashboard_manage_containers.rst:155 ../dashboard_manage_images.rst:27 -#: ../dashboard_manage_images.rst:94 ../dashboard_manage_images.rst:124 -#: ../dashboard_manage_volumes.rst:14 ../dashboard_manage_volumes.rst:66 -#: ../dashboard_manage_volumes.rst:109 ../dashboard_manage_volumes.rst:131 -#: ../dashboard_manage_volumes.rst:163 ../dashboard_stacks.rst:28 -#: ../dashboard_stacks.rst:123 ../dashboard_stacks.rst:143 -msgid "Log in to the dashboard." -msgstr "" - -#: ../cli_cheat_sheet.rst:111 -msgid "Login to instance" -msgstr "" - -#: ../cli_swift_large_lists.rst:74 -msgid "Make another request with a ``marker`` of the last item returned:" -msgstr "" - -#: ../cli_swift_large_lists.rst:59 -msgid "" -"Make another request with a ``marker`` parameter set to the name of the last " -"item returned:" -msgstr "" - -#: ../cli_swift_static_website.rst:54 -msgid "Make container publicly readable" -msgstr "" - -#: ../cli_cheat_sheet.rst:319 -msgid "Make filesystem on volume" -msgstr "" - -#: ../dashboard_databases.rst:53 -msgid "" -"Make sure an appropriate flavor exists for the type of database instance you " -"want." -msgstr "" - -#: ../sdk_neutron_apis.rst:18 -msgid "Make sure that you set the relevant environment variables." -msgstr "" - -#: ../cli_swift_static_website.rst:56 -msgid "" -"Make the container publicly readable. Once the container is publicly " -"readable, you can access your objects directly, but you must set the index " -"file to browse the main site URL and its sub-directories." -msgstr "" - -#: ../cli_use_snapshots_to_migrate_instances.rst:97 -msgid "" -"Make the image available to the new environment, either through HTTP or " -"direct upload to a machine (``scp``)." -msgstr "" - -#: ../cli_nova_launch_instance_using_ISO_image.rst:75 -msgid "Make the instances booted from ISO image functional" -msgstr "" - -#: ../cli_manage_ip_addresses.rst:3 -msgid "Manage IP addresses" -msgstr "" - -#: ../dashboard_stacks.rst:121 -msgid "Manage a stack" -msgstr "" - -#: ../cli_swift_manage_access_swift.rst:3 -msgid "Manage access" -msgstr "" - -#: ../dashboard_launch_instances.rst:228 -msgid "Manage an instance" -msgstr "" - -#: ../dashboard_manage_containers.rst:69 -msgid "Manage an object" -msgstr "" - -#: ../cli_manage_bare_metal_nodes.rst:3 -msgid "Manage bare-metal nodes" -msgstr "" - -#: ../manage_db_config.rst:3 -msgid "Manage database configuration" -msgstr "" - -#: ../sdk_manage_images.rst:6 -msgid "Manage images" -msgstr "" - -#: ../cli_manage_instances_hosts.rst:3 -msgid "Manage instances and hosts" -msgstr "" - -#: ../cli_swift_manage_objects.rst:3 -msgid "Manage objects" -msgstr "" - -#: ../managing-openstack-object-storage-with-swift-cli.rst:3 -msgid "Manage objects and containers" -msgstr "" - -#: ../cli_cheat_sheet.rst:253 -msgid "Manage security groups" -msgstr "" - -#: ../cli_cheat_sheet.rst:311 -msgid "Manage volumes after login into the instance" -msgstr "" - -#: ../cli_swift_large_object_creation.rst:296 -msgid "Manfiest object metadata" -msgstr "" - -#: ../dashboard_launch_instances.rst:160 -msgid "Manual" -msgstr "" - -#: ../cli_ceilometer.rst:3 -msgid "Measure cloud resources" -msgstr "" - -#: ../cli_ceilometer.rst:12 -msgid "" -"Measures a specific aspect of resource usage, such as the existence of a " -"running instance, or ongoing performance, such as the CPU utilization for an " -"instance. Meters exist for each type of resource. For example, a separate " -"``cpu_util`` meter exists for each instance. The life cycle of a meter is " -"decoupled from the existence of its related resource. The meter persists " -"after the resource goes away." -msgstr "" - -#: ../cli_ceilometer.rst:31 -msgid "Meter" -msgstr "" - -#: ../cli_swift_serialized_response_formats.rst:17 -msgid "Method" -msgstr "" - -#: ../manage_db_config.rst:223 -msgid "" -"Modify a configuration group on the fly, using the trove ``configuration-" -"patch`` command." -msgstr "" - -#: ../cli_nova_configure_access_security_for_instances.rst:121 -msgid "" -"Modify security group rules with the :command:`nova secgroup-*-rule` " -"commands. Before you begin, source the OpenStack RC file. For details, see :" -"doc:`../common/cli_set_environment_variables_using_openstack_rc`." -msgstr "" - -#: ../create_db.rst:52 -msgid "MongoDB" -msgstr "" - -#: ../cli_cheat_sheet.rst:331 -msgid "Mount the volume at the mountpoint" -msgstr "" - -#: ../create_db.rst:48 -msgid "MySQL" -msgstr "" - -#: ../dashboard_databases.rst:129 -msgid "Name" -msgstr "" - -#: ../backup_db.rst:18 -msgid "Name of the database instance: ``guest1``" -msgstr "" - -#: ../create_db.rst:95 -msgid "Name of the instance: ``mysql_instance_1``" -msgstr "" - -#: ../sdk_neutron_apis.rst:6 -msgid "Networking" -msgstr "" - -#: ../cli_cheat_sheet.rst:264 -msgid "Networking (neutron)" -msgstr "" - -#: ../dashboard_create_networks.rst:10 -msgid "" -"Networking in OpenStack is complex. This section provides the basic " -"instructions for creating a network and a router. For detailed information " -"about managing networks, refer to the `OpenStack Cloud Administrator Guide " -"`__." -msgstr "" - -#: ../cli_swift_large_object_creation.rst:218 -msgid "" -"Next, upload the manifest you created that indicates the container where the " -"object segments reside. Note that uploading additional segments after the " -"manifest is created causes the concatenated object to be that much larger " -"but you do not need to recreate the manifest file for subsequent additional " -"segments." -msgstr "" - -#: ../cli_swift_large_object_creation.rst:196 -msgid "" -"No response body is returned. A status code of 2``nn`` (between 200 and 299, " -"inclusive) indicates a successful write; status 411 Length Required denotes " -"a missing ``Content-Length`` or ``Content-Type`` header in the request. If " -"the MD5 checksum of the data written to the storage system does NOT match " -"the (optionally) supplied ETag value, a 422 Unprocessable Entity response is " -"returned." -msgstr "" - -#: ../dashboard_manage_volumes.rst:37 -msgid "" -"No source, empty volume: Creates an empty volume. An empty volume does not " -"contain a file system or a partition table." -msgstr "" - -#: ../cli_swift_large_object_creation.rst:135 -msgid "" -"Normally when you perform a ``GET`` operation on the manifest object, the " -"response body contains the concatenated content of the segment objects. To " -"download the manifest list, use the ``?multipart-manifest=get`` query " -"parameter. The resulting list is not formatted the same as the manifest you " -"originally used in the ``PUT`` operation." -msgstr "" - -#: ../cli_swift_large_object_creation.rst:267 -msgid "" -"Not guaranteed. The eventual consistency model means that although you have " -"uploaded a segment object, it might not appear in the container listing " -"until later. If you download the manifest before it appears in the " -"container, it does not form part of the content returned in response to a " -"``GET`` request." -msgstr "" - -#: ../backup_db.rst:67 -msgid "" -"Note that the command returns both the ID of the original instance " -"(``instance_id``) and the ID of the backup artifact (``id``)." -msgstr "" - -#: ../backup_db.rst:176 -msgid "" -"Note that the data store, flavor ID, and volume size have the same values as " -"in the original ``guest1`` instance." -msgstr "" - -#: ../cli_create_and_manage_networks.rst:224 -msgid "" -"Note that the system allocates one IP address if you do not specify an IP " -"address in the ``neutron port-create`` command." -msgstr "" - -#: ../backup_db_incremental.rst:62 -msgid "" -"Note that this command returns both the ID of the database instance you are " -"incrementally backing up (``instance_id``) and a new ID for the new " -"incremental backup artifact you just created (``id``)." -msgstr "" - -#: ../cli_launch_instances.rst:82 -msgid "Note the ID of the flavor that you want to use for your instance::" -msgstr "" - -#: ../cli_nova_launch_instance_from_volume.rst:167 -msgid "Note the ID of the flavor that you want to use to create a volume." -msgstr "" - -#: ../cli_launch_instances.rst:98 -msgid "Note the ID of the image from which you want to boot your instance::" -msgstr "" - -#: ../cli_nova_launch_instance_from_volume.rst:152 -msgid "Note the ID of the image that you want to use to create a volume." -msgstr "" - -#: ../cli_launch_instances.rst:126 -msgid "" -"Note the ID of the security group that you want to use for your instance::" -msgstr "" - -#: ../cli_config_drive.rst:193 -msgid "" -"Note the effect of the ``--file /etc/network/interfaces=/home/myuser/" -"instance-interfaces`` argument that was passed to the :command:`nova boot` " -"command. The contents of this file are contained in the :file:`openstack/" -"content/0000` file on the configuration drive, and the path is specified as :" -"file:`/etc/network/interfaces` in the :file:`meta_data.json` file." -msgstr "" - -#: ../cli_swift_set_object_versions.rst:78 -msgid "" -"Nothing is written to the non-current version container when you initially " -"``PUT`` an object in the ``current`` container. However, subsequent ``PUT`` " -"requests that edit an object trigger the creation of a version of that " -"object in the ``archive`` container." -msgstr "" - -#: ../backup_db_incremental.rst:93 -msgid "" -"Now assume that your ``guest1`` database instance is damaged and you need to " -"restore it from your incremental backups. In this example, you use the trove " -"``create`` command to create a new database instance called ``guest2``." -msgstr "" - -#: ../backup_db.rst:106 -msgid "" -"Now assume that your ``guest1`` database instance is damaged and you need to " -"restore it. In this example, you use the trove ``create`` command to create " -"a new database instance called ``guest2``." -msgstr "" - -#: ../dashboard_databases.rst:142 -msgid "" -"Now assume that your original database instance is damaged and you need to " -"restore it. You do the restore by using your backup to create a new database " -"instance." -msgstr "" - -#: ../backup_db.rst:138 -msgid "" -"Now check that the new ``guest2`` instance has the same characteristics as " -"the original ``guest1`` instance." -msgstr "" - -#: ../cli_nova_launch_instance_using_ISO_image.rst:77 -msgid "" -"Now complete the following steps to make your instances created using ISO " -"image actually functional." -msgstr "" - -#: ../set_up_replication.rst:74 -msgid "" -"Now pass in ``base_1``'s instance ID with the trove ``show`` command to list " -"the replica(s) associated with the original instance. Note that the " -"``replicas`` property is set to the ID of ``replica_1``. If there are " -"multiple replicas, they appear as a comma-separated list." -msgstr "" - -#: ../create_db.rst:42 -msgid "" -"Now take a look at the minimum requirements for various database instances:" -msgstr "" - -#: ../dashboard_manage_volumes.rst:93 -msgid "Now you can log in to the instance and mount, format, and use the disk." -msgstr "" - -#: ../cli_cheat_sheet.rst:351 -msgid "Object Storage (swift)" -msgstr "" - -#: ../cli_swift_serialized_response_formats.rst:59 -msgid "" -"Object Storage lists container names with additional information in JSON " -"format:" -msgstr "" - -#: ../cli_swift_serialized_response_formats.rst:103 -msgid "" -"Object Storage lists container names with additional information in XML " -"format:" -msgstr "" - -#: ../cli_swift_set_object_versions.rst:3 -msgid "Object versioning" -msgstr "" - -#: ../cli_reboot_an_instance.rst:41 -msgid "" -"On running the :command:`nova rescue` command, an instance performs a soft " -"shutdown first. This means that the guest operating system has a chance to " -"perform a controlled shutdown before the instance is powered off. The " -"shutdown behavior is configured by the ``shutdown_timeout`` parameter that " -"can be set in the :file:`nova.conf` file. Its value stands for the overall " -"period (in seconds) a guest operation system is allowed to complete the " -"shutdown. The default timeout is 60 seconds. See `Description of Compute " -"configuration options `_ for details." -msgstr "" - -#: ../dashboard_manage_volumes.rst:142 -msgid "On the :guilabel:`Project` tab, click :guilabel:`Volumes`." -msgstr "" - -#: ../configure_access_and_security_for_instances.rst:103 -#: ../configure_access_and_security_for_instances.rst:126 -#: ../configure_access_and_security_for_instances.rst:182 -msgid "" -"On the :guilabel:`Project` tab, open the :guilabel:`Compute` tab and click :" -"guilabel:`Access & Security` category." -msgstr "" - -#: ../configure_access_and_security_for_instances.rst:52 -msgid "" -"On the :guilabel:`Project` tab, open the :guilabel:`Compute` tab and click :" -"guilabel:`Access & Security` category. The :guilabel:`Security Groups` tab " -"shows the security groups that are available for this project." -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:38 ../dashboard_manage_images.rst:32 -#: ../dashboard_manage_images.rst:99 ../dashboard_manage_images.rst:129 -msgid "" -"On the :guilabel:`Project` tab, open the :guilabel:`Compute` tab and click :" -"guilabel:`Images` category." -msgstr "" - -#: ../dashboard_launch_instances.rst:235 -msgid "" -"On the :guilabel:`Project` tab, open the :guilabel:`Compute` tab and click :" -"guilabel:`Instances` category." -msgstr "" - -#: ../dashboard_launch_instances.rst:202 -msgid "" -"On the :guilabel:`Project` tab, open the :guilabel:`Compute` tab and click :" -"guilabel:`Overview` category." -msgstr "" - -#: ../dashboard_manage_volumes.rst:19 ../dashboard_manage_volumes.rst:71 -#: ../dashboard_manage_volumes.rst:114 ../dashboard_manage_volumes.rst:136 -#: ../dashboard_manage_volumes.rst:168 -msgid "" -"On the :guilabel:`Project` tab, open the :guilabel:`Compute` tab and click :" -"guilabel:`Volumes` category." -msgstr "" - -#: ../dashboard_databases.rst:151 -msgid "" -"On the :guilabel:`Project` tab, open the :guilabel:`Database` tab and click :" -"guilabel:`Backups` category. This lists the available backups." -msgstr "" - -#: ../dashboard_databases.rst:65 -msgid "" -"On the :guilabel:`Project` tab, open the :guilabel:`Database` tab and click :" -"guilabel:`Instances` category. This lists the instances that already exist " -"in your environment." -msgstr "" - -#: ../dashboard_databases.rst:120 ../dashboard_databases.rst:180 -#: ../dashboard_databases.rst:203 -msgid "" -"On the :guilabel:`Project` tab, open the :guilabel:`Database` tab and click :" -"guilabel:`Instances` category. This displays the existing instances in your " -"system." -msgstr "" - -#: ../dashboard_create_networks.rst:24 -msgid "" -"On the :guilabel:`Project` tab, open the :guilabel:`Network` tab and click :" -"guilabel:`Networks` category." -msgstr "" - -#: ../dashboard_create_networks.rst:76 -msgid "" -"On the :guilabel:`Project` tab, open the :guilabel:`Network` tab and click :" -"guilabel:`Routers` category." -msgstr "" - -#: ../dashboard_manage_containers.rst:24 ../dashboard_manage_containers.rst:45 -#: ../dashboard_manage_containers.rst:78 -#: ../dashboard_manage_containers.rst:101 -#: ../dashboard_manage_containers.rst:132 -#: ../dashboard_manage_containers.rst:160 -msgid "" -"On the :guilabel:`Project` tab, open the :guilabel:`Object Store` tab and " -"click :guilabel:`Containers` category." -msgstr "" - -#: ../dashboard_stacks.rst:31 ../dashboard_stacks.rst:126 -#: ../dashboard_stacks.rst:146 -msgid "" -"On the :guilabel:`Project` tab, open the :guilabel:`Orchestration` tab and " -"click :guilabel:`Stacks` category." -msgstr "" - -#: ../dashboard_create_networks.rst:96 -msgid "" -"On the :guilabel:`Router Details` page, click the :guilabel:`Interfaces` " -"tab, then click :guilabel:`Add Interface`." -msgstr "" - -#: ../dashboard_create_networks.rst:94 -msgid "On the :guilabel:`Routers` tab, click the name of the router." -msgstr "" - -#: ../cli_config_drive.rst:133 -msgid "Once identified, you can mount the device::" -msgstr "" - -#: ../set_up_clustering.rst:19 -msgid "" -"One or more *config servers*. Config servers store the metadata that links " -"requested data with the shard that contains it." -msgstr "" - -#: ../set_up_clustering.rst:13 -msgid "" -"One or more *query routers*. A query router is the machine that your " -"application actually connects to. This machine is responsible for " -"communicating with the config server to figure out where the requested data " -"is stored. It then accesses and returns the data from the appropriate " -"shard(s)." -msgstr "" - -#: ../set_up_clustering.rst:10 -msgid "" -"One or more *shards*. Each shard consists of a three member replica set " -"(three instances organized as a replica set)." -msgstr "" - -#: ../cli_config_drive.rst:10 -msgid "" -"One use case for using the configuration drive is to pass a networking " -"configuration when you do not use DHCP to assign IP addresses to instances. " -"For example, you might pass the IP address configuration for the instance " -"through the configuration drive, which the instance can mount and access " -"before you configure the network settings for the instance." -msgstr "" - -#: ../index.rst:3 -msgid "OpenStack End User Guide" -msgstr "" - -#: ../dashboard_manage_containers.rst:5 -msgid "" -"OpenStack Object Storage provides a distributed, API-accessible storage " -"platform that can be integrated directly into an application or used to " -"store any type of file, including VM images, backups, archives, or media " -"files. In the OpenStack dashboard, you can only manage containers and " -"objects." -msgstr "" - -#: ../dashboard_stacks.rst:5 -msgid "" -"OpenStack Orchestration is a service that you can use to orchestrate " -"multiple composite cloud applications. This service supports the use of both " -"the Amazon Web Services (AWS) CloudFormation template format through both a " -"Query API that is compatible with CloudFormation and the native OpenStack :" -"term:`Heat Orchestration Template (HOT)` format through a REST API." -msgstr "" - -#: ../sdk.rst:3 -msgid "OpenStack Python SDK" -msgstr "" - -#: ../cli.rst:3 -msgid "OpenStack command-line clients" -msgstr "" - -#: ../intro-user.rst:13 -msgid "" -"OpenStack command-line clients. Each core OpenStack project has a command-" -"line client that you can use to run simple commands to view, create, and " -"manage resources in a cloud and automate tasks by using scripts." -msgstr "" - -#: ../cli_cheat_sheet.rst:3 -msgid "OpenStack command-line interface cheat sheet" -msgstr "" - -#: ../dashboard.rst:3 -msgid "OpenStack dashboard" -msgstr "" - -#: ../intro-user.rst:11 -msgid "" -"OpenStack dashboard. Use this web-based graphical interface, code named " -"`horizon `__, to view, " -"create, and manage resources." -msgstr "" - -#: ../index.rst:8 -msgid "" -"OpenStack is an open-source cloud computing platform for public and private " -"clouds. A series of interrelated projects deliver a cloud infrastructure " -"solution. This guide shows OpenStack end users how to create and manage " -"resources in an OpenStack cloud with the OpenStack dashboard and OpenStack " -"client commands." -msgstr "" - -#: ../cli_config_drive.rst:159 -msgid "OpenStack metadata format" -msgstr "" - -#: ../cli_nova_launch_instance_using_ISO_image.rst:10 -msgid "" -"OpenStack supports booting instances using ISO images. But before you make " -"such instances functional, use the :command:`nova boot` command with the " -"following parameters to boot an instance::" -msgstr "" - -#: ../dashboard_databases.rst:84 -msgid "" -"Optionally provide a comma separated list of databases to create, for " -"example:" -msgstr "" - -#: ../cli_swift_archive_auto_extract.rst:33 -msgid "Optionally, a specific container" -msgstr "" - -#: ../cli_swift_archive_auto_extract.rst:35 -msgid "Optionally, a specific object prefix" -msgstr "" - -#: ../dashboard_create_networks.rst:101 -msgid "" -"Optionally, in the :guilabel:`Add Interface` dialog box, set an :guilabel:" -"`IP Address` for the router interface for the selected subnet." -msgstr "" - -#: ../cli_launch_instances.rst:160 -msgid "" -"Optionally, you can provide a key name for access control and a security " -"group for security. You can also include metadata key and value pairs. For " -"example, you can add a description for your server by providing the ``--meta " -"description=\"My Server\"`` parameter." -msgstr "" - -#: ../cli_nova_launch_instance_from_volume.rst:205 -msgid "Orders the boot disks. Use ``0`` to boot from this volume." -msgstr "" - -#: ../sdk_assign_cors_headers.rst:17 -msgid "Origin" -msgstr "" - -#: ../dashboard_stacks.rst:112 -msgid "Overview" -msgstr "" - -#: ../cli_swift_large_lists.rst:3 -msgid "Page through large lists of containers or objects" -msgstr "" - -#: ../set_up_replication.rst:51 -msgid "" -"Pass in ``replica_1``'s instance ID with the trove ``show`` command to " -"verify that the newly created ``replica_1`` instance is a replica of the " -"original ``base_1``. Note that the ``replica_of`` property is set to the ID " -"of ``base_1``." -msgstr "" - -#: ../manage_db_config.rst:37 -msgid "" -"Pass in the data store version ID with the trove ``configuration-parameter-" -"list`` command to get the available options:" -msgstr "" - -#: ../cli_cheat_sheet.rst:152 -msgid "Pause" -msgstr "" - -#: ../cli_stop_and_start_an_instance.rst:8 -msgid "Pause and unpause an instance" -msgstr "" - -#: ../cli_reboot_an_instance.rst:25 -msgid "" -"Pause, suspend, and stop operations are not allowed when an instance is " -"running in rescue mode, as triggering these actions causes the loss of the " -"original instance state, and makes it impossible to unrescue the instance." -msgstr "" - -#: ../cli_cheat_sheet.rst:150 -msgid "Pause, suspend, stop, rescue, resize, rebuild, reboot an instance" -msgstr "" - -#: ../cli_swift_serialized_response_formats.rst:26 -msgid "Plain text response format. The default." -msgstr "" - -#: ../cli_create_and_manage_stacks.rst:51 +#: ../sdk_authenticate.rst:7 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 "" - -#: ../sdk_compute_apis.rst:390 -msgid "Print the flavor details, id and name by calling ``print_flavors``:" -msgstr "" - -#: ../sdk_compute_apis.rst:461 -msgid "Print the floating IP object details by calling ``print_values_ip``:" +"When using the SDK, you must authenticate against an OpenStack endpoint " +"before you can use OpenStack services. Each project uses a slightly " +"different syntax for authentication." msgstr "" -#: ../sdk_compute_apis.rst:527 -msgid "Print the host object details by calling ``print_hosts(host_list)``:" -msgstr "" - -#: ../sdk_neutron_apis.rst:89 -msgid "Print values" -msgstr "" - -#: ../cli_provide_user_data_to_instances.rst:3 -msgid "Provide user data to instances" -msgstr "" - -#: ../dashboard_manage_containers.rst:151 +#: ../sdk_authenticate.rst:11 msgid "" -"Pseudo-folders are similar to folders in your desktop operating system. They " -"are virtual collections defined by a common prefix on the object's name." -msgstr "" - -#: ../cli_swift_pseudo_hierarchical_folders_directories.rst:3 -msgid "Pseudo-hierarchical folders and directories" +"You must typically authenticate against a specific version of a service. For " +"example, a client might need to authenticate against Identity v2.0." msgstr "" #: ../sdk_authenticate.rst:14 @@ -5024,860 +7690,29 @@ msgid "" "credentials by using the environment variables in the Python scripts." msgstr "" -#: ../cli_create_and_manage_networks.rst:227 -msgid "Query ports with specified fixed IP addresses::" +#: ../sdk_authenticate_against_compute_endpoint.rst:6 +msgid "Authenticate against a Compute endpoint" msgstr "" -#: ../set_up_clustering.rst:159 -msgid "Query routers and config servers" -msgstr "" - -#: ../create_db.rst:46 -msgid "RAM (MB)" -msgstr "" - -#: ../create_db.rst:73 -msgid "RAM: ``512``" -msgstr "" - -#: ../sdk.rst:14 -msgid "RESTful web services" -msgstr "" - -#: ../cli_cheat_sheet.rst:211 -msgid "Reboot" -msgstr "" - -#: ../cli_reboot_an_instance.rst:3 -msgid "Reboot an instance" -msgstr "" - -#: ../cli_cheat_sheet.rst:204 -msgid "Rebuild" -msgstr "" - -#: ../create_db.rst:54 -msgid "Redis" -msgstr "" - -#: ../cli_cheat_sheet.rst:74 -msgid "Register raw image" -msgstr "" - -#: ../configure_access_and_security_for_instances.rst:64 -msgid "Remote" -msgstr "" - -#: ../cli_swift_large_object_creation.rst:280 -msgid "Removal or addition of segment objects" -msgstr "" - -#: ../cli_stop_and_start_an_instance.rst:77 +#: ../sdk_authenticate_against_compute_endpoint.rst:8 msgid "" -"Remove a shelved instance - Removes the instance from the server; data and " -"resource associations are deleted. If an instance is no longer needed, you " -"can move the instance off the hypervisor in order to minimize resource usage." +"To authenticate against a Compute endpoint, instantiate a `novaclient.v" +"\\_1\\_1.client.Client `__ " +"object:" msgstr "" -#: ../cli_manage_bare_metal_nodes.rst:37 -msgid "Removes a bare-metal node and any associated interfaces." -msgstr "" - -#: ../cli_manage_bare_metal_nodes.rst:31 -msgid "Removes a network interface from a bare-metal node." -msgstr "" - -#: ../dashboard_databases.rst:31 +#: ../sdk_authenticate_against_compute_endpoint.rst:22 msgid "" -"Replace *``DATASTORE_NAME``* with the name that the administrative user set " -"when issuing the **trove-manage** command to create the datastore. You can " -"use the trove **datastore-list** command to display the datastores that are " -"available in your environment." +"Alternatively, you can instantiate a ``novaclient.client.Client`` object and " +"pass the version number:" msgstr "" -#: ../cli_create_and_manage_networks.rst:155 +#: ../sdk_authenticate_against_compute_endpoint.rst:36 msgid "" -"Replace ROUTER with the unique identifier of the router, replace NETWORK " -"with the unique identifier of the external provider network." -msgstr "" - -#: ../cli_create_and_manage_networks.rst:162 -msgid "" -"Replace ROUTER with the unique identifier of the router, replace SUBNET with " -"the unique identifier of the subnet." -msgstr "" - -#: ../set_up_replication.rst:9 -msgid "Replicas are read-only." -msgstr "" - -#: ../cli_config_drive.rst:21 -msgid "Requirements and guidelines" -msgstr "" - -#: ../cli_cheat_sheet.rst:189 -msgid "Rescue" -msgstr "" - -#: ../cli_reboot_an_instance.rst:30 -msgid "" -"Rescue mode provides a mechanism for access, even if an image renders the " -"instance inaccessible. By default, it starts an instance from the initial " -"image attaching the current boot disk as a secondary one." -msgstr "" - -#: ../cli_cheat_sheet.rst:196 -msgid "Resize" -msgstr "" - -#: ../dashboard_stacks.rst:115 -msgid "Resources" -msgstr "" - -#: ../configure_access_and_security_for_instances.rst:114 -msgid "Respond to the prompt to download the key pair." -msgstr "" - -#: ../dashboard_databases.rst:43 -msgid "Restart Database services on the controller node:" -msgstr "" - -#: ../backup_db_incremental.rst:9 -msgid "" -"Restoring a database instance from an incremental backup is the same as " -"creating a database instance from a regular backup—the Database service " -"handles the complexities of applying the chain of incremental backups." -msgstr "" - -#: ../create_db.rst:75 -msgid "Root volume size in GB: ``5``" -msgstr "" - -#: ../backup_db.rst:22 -msgid "Root volume size: ``2``" -msgstr "" - -#: ../configure_access_and_security_for_instances.rst:64 -#: ../configure_access_and_security_for_instances.rst:82 -msgid "Rule" -msgstr "" - -#: ../cli_nova_configure_access_security_for_instances.rst:47 -msgid "Rules are automatically enforced as soon as you create or modify them." -msgstr "" - -#: ../sdk_compute_apis.rst:130 -msgid "" -"Run the \"Sleep for five seconds\" command, and determine whether the server/" -"vm was created by calling ``nova_client.servers.list()``:" -msgstr "" - -#: ../cli_delete_an_instance.rst:19 -msgid "" -"Run the :command:`nova delete` command to delete the instance. The following " -"example shows deletion of the ``newServer`` instance, which is in ``ERROR`` " -"state::" -msgstr "" - -#: ../cli_manage_ip_addresses.rst:68 -msgid "" -"Run the following command to allocate a floating IP address to the current " -"project. By default, the floating IP address is allocated from the public " -"pool. The command outputs the allocated IP address::" -msgstr "" - -#: ../cli_ceilometer.rst:37 -msgid "Sample" -msgstr "" - -#: ../configure_access_and_security_for_instances.rst:138 -msgid "Save the ``*.pem`` file locally." -msgstr "" - -#: ../sdk_schedule_objects_for_deletion.rst:3 -msgid "Schedule objects for deletion" -msgstr "" - -#: ../sdk_schedule_objects_for_deletion.rst:9 -msgid "" -"Scheduling an object for deletion is helpful for managing objects that you " -"do not want to permanently store, such as log files, recurring full backups " -"of a dataset, or documents or images that become outdated at a specified " -"time." -msgstr "" - -#: ../cli_search_instance_with_ip_address.rst:3 -msgid "Search for an instance using IP address" -msgstr "" - -#: ../index.rst:36 -msgid "Search in this guide" -msgstr "" - -#: ../dashboard_launch_instances.rst:137 -msgid "Security Groups" -msgstr "" - -#: ../dashboard_launch_instances.rst:133 -msgid "" -"Security groups are a kind of cloud firewall that define which incoming " -"network traffic is forwarded to instances." -msgstr "" - -#: ../cli_swift_static_website.rst:25 -msgid "" -"See the Cloud Administrator Guide for a complete example of the `/etc/swift/" -"proxy-server.conf file `_ (including static web)." -msgstr "" - -#: ../cli_swift_static_website.rst:23 -msgid "" -"See the Cloud Administrator Guide for an example of the `static web " -"configuration syntax `_." -msgstr "" - -#: ../cli_swift_large_object_creation.rst:292 -msgid "Segment object container name" -msgstr "" - -#: ../cli_swift_large_object_creation.rst:287 -msgid "Segment object size and number" -msgstr "" - -#: ../cli_swift_large_object_creation.rst:291 -msgid "Segment objects can be any size." -msgstr "" - -#: ../cli_swift_large_object_creation.rst:288 -msgid "" -"Segment objects must be at least 1 MB in size (by default). The final " -"segment object can be any size. At most, 1000 segments are supported (by " -"default)." -msgstr "" - -#: ../dashboard_manage_volumes.rst:117 -msgid "Select a volume from which to create a snapshot." -msgstr "" - -#: ../dashboard_launch_instances.rst:48 -msgid "Select an image and click :guilabel:`Launch Instance`." -msgstr "" - -#: ../dashboard_launch_instances.rst:238 -msgid "Select an instance." -msgstr "" - -#: ../dashboard_manage_images.rst:112 -msgid "Select the :guilabel:`Public` check box to make the image public." -msgstr "" - -#: ../dashboard_manage_shares.rst:221 -msgid "" -"Select the check boxes for the security services that you want to delete." -msgstr "" - -#: ../dashboard_manage_shares.rst:158 -msgid "Select the check boxes for the share networks that you want to delete." -msgstr "" - -#: ../dashboard_manage_shares.rst:44 -msgid "Select the check boxes for the shares that you want to delete." -msgstr "" - -#: ../dashboard_manage_volumes.rst:171 -msgid "Select the check boxes for the volumes that you want to delete." -msgstr "" - -#: ../dashboard_manage_containers.rst:48 ../dashboard_manage_containers.rst:81 -#: ../dashboard_manage_containers.rst:104 -#: ../dashboard_manage_containers.rst:135 -#: ../dashboard_manage_containers.rst:163 -msgid "Select the container in which you want to store your object." -msgstr "" - -#: ../configure_access_and_security_for_instances.rst:57 -msgid "Select the default security group and click :guilabel:`Manage Rules`." -msgstr "" - -#: ../dashboard_manage_images.rst:61 -msgid "Select the image format (for example, QCOW2) for the image." -msgstr "" - -# #-#-#-#-# dashboard_manage_images.pot (End User Guide 1.0.0) #-#-#-#-# -# #-#-#-#-# dashboard_manage_volumes.pot (End User Guide 1.0.0) #-#-#-#-# -#: ../dashboard_manage_images.rst:102 ../dashboard_manage_volumes.rst:144 -msgid "Select the image that you want to edit." -msgstr "" - -#: ../dashboard_manage_images.rst:132 -msgid "Select the images that you want to delete." -msgstr "" - -#: ../dashboard_launch_instances.rst:215 -msgid "Select the instance from which to create a snapshot." -msgstr "" - -#: ../dashboard_databases.rst:135 -msgid "Select the instance you want to back up." -msgstr "" - -#: ../dashboard_stacks.rst:148 -msgid "Select the stack that you want to delete." -msgstr "" - -#: ../dashboard_stacks.rst:128 -msgid "Select the stack that you want to update." -msgstr "" - -#: ../dashboard_launch_instances.rst:154 -msgid "Select the type of disk partition from the dropdown list:" -msgstr "" - -#: ../dashboard_manage_volumes.rst:100 -msgid "Select the volume and click :guilabel:`Edit Attachments`." -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_manage_volumes.rst:74 -msgid "" -"Select the volume to add to an instance and click :guilabel:`Edit " -"Attachments`." -msgstr "" - -#: ../dashboard_stacks.rst:71 -msgid "" -"Select this check box if you want the service to roll back changes if the " -"stack fails to launch." -msgstr "" - -#: ../dashboard_manage_images.rst:78 -msgid "" -"Select this check box to ensure that only users with permissions can delete " -"the image." -msgstr "" - -#: ../dashboard_manage_images.rst:73 -msgid "" -"Select this check box to make the image public to all users with access to " -"the current project." -msgstr "" - -#: ../dashboard_launch_instances.rst:143 -msgid "Selected Networks" -msgstr "" - -#: ../cli_swift_serialized_response_formats.rst:3 -msgid "Serialized response formats" -msgstr "" - -#: ../dashboard_launch_instances.rst:69 -msgid "" -"Server names are not guaranteed to be unique when created so you could have " -"two instances with the same host name." -msgstr "" - -#: ../manage_db_config.rst:105 -msgid "Set *VALUES* as a JSON dictionary, for example:" -msgstr "" - -# #-#-#-#-# sdk_compute_apis.pot (End User Guide 1.0.0) #-#-#-#-# -# #-#-#-#-# sdk_neutron_apis.pot (End User Guide 1.0.0) #-#-#-#-# -#: ../sdk_compute_apis.rst:12 ../sdk_neutron_apis.rst:16 -msgid "Set environment variables" -msgstr "" - -#: ../cli_swift_static_website.rst:98 -msgid "Set error pages for static website" -msgstr "" - -#: ../cli_swift_static_website.rst:117 -msgid "Set error pages for static website request" -msgstr "" - -#: ../cli_cheat_sheet.rst:136 -msgid "Set metadata on an instance" -msgstr "" - -#: ../cli_swift_static_website.rst:66 -msgid "Set site index file" -msgstr "" - -#: ../cli_manage_bare_metal_nodes.rst:122 -msgid "" -"Set the ``--availability_zone`` parameter to specify which zone or node to " -"use to start the server. Separate the zone from the host name with a comma. " -"For example:" -msgstr "" - -#: ../cli_swift_bulk_delete.rst:42 -msgid "Set the ``Content-Type`` request header to ``text/plain``." -msgstr "" - -#: ../cli_swift_static_website.rst:68 -msgid "" -"Set the index file. In this case, ``index.html`` is the default file " -"displayed when the site appears." -msgstr "" - -#: ../set_up_clustering.rst:33 -msgid "Set up clustering" -msgstr "" - -#: ../set_up_clustering.rst:3 -msgid "Set up database clustering" -msgstr "" - -#: ../set_up_replication.rst:3 -msgid "Set up database replication" -msgstr "" - -#: ../set_up_replication.rst:21 -msgid "Set up replication" -msgstr "" - -#: ../dashboard_manage_shares.rst:5 -msgid "" -"Shares are file storage that you provide access to instances. You can allow " -"access to a share to a running instance or deny access to a share and allow " -"access to it to another instance at any time. You can also delete a share. " -"You can create snapshot from a share if the driver supports it. Only " -"administrative users can create share types." -msgstr "" - -#: ../cli_stop_and_start_an_instance.rst:45 -msgid "" -"Shelve an instance - Shuts down the instance, and stores it together with " -"associated data and resources (a snapshot is taken if not volume backed). " -"Anything in memory is lost." -msgstr "" - -#: ../cli_stop_and_start_an_instance.rst:34 -msgid "Shelve and unshelve an instance" -msgstr "" - -#: ../cli_stop_and_start_an_instance.rst:36 -msgid "" -"Shelving is useful if you have an instance that you are not using, but would " -"like retain in your list of servers. For example, you can stop an instance " -"at the end of a work week, and resume work again at the start of the next " -"week. All associated data and resources are kept; however, anything still in " -"memory is not retained. If a shelved instance is no longer needed, it can " -"also be entirely removed." -msgstr "" - -#: ../cli_manage_bare_metal_nodes.rst:150 -msgid "Show details for a bare-metal node" -msgstr "" - -#: ../cli_cheat_sheet.rst:123 -msgid "Show details of instance" -msgstr "" - -#: ../cli_change_the_size_of_your_server.rst:7 -msgid "" -"Show information about your server, including its size, which is shown as " -"the value of the flavor property::" -msgstr "" - -#: ../cli_change_the_size_of_your_server.rst:85 -msgid "Show the status for your server::" -msgstr "" - -#: ../cli_manage_bare_metal_nodes.rst:43 -msgid "Shows information about a bare-metal node." -msgstr "" - -#: ../cli_use_snapshots_to_migrate_instances.rst:29 -msgid "" -"Shut down the source VM before you take the snapshot to ensure that all data " -"is flushed to disk. If necessary, list the instances to view the instance " -"name::" -msgstr "" - -#: ../dashboard_launch_instances.rst:113 -msgid "" -"Since you are launching an instance from an image, :guilabel:`Boot from " -"image` is chosen by default." -msgstr "" - -#: ../dashboard_manage_volumes.rst:40 -msgid "" -"Snapshot: If you choose this option, a new field for Use snapshot as a " -"source displays. You can select the snapshot from the list." -msgstr "" - -#: ../cli_use_snapshots_to_migrate_instances.rst:22 -msgid "Some cloud providers allow only administrators to perform this task." -msgstr "" - -#: ../cli_create_and_manage_networks.rst:57 -msgid "Some fields of the created network are invisible to non-admin users." -msgstr "" - -#: ../cli_create_and_manage_stacks.rst:135 -msgid "" -"Some resources are updated in-place, while others are replaced with new " -"resources." -msgstr "" - -#: ../cli_create_and_manage_stacks.rst:97 -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 "" - -#: ../dashboard_launch_instances.rst:148 -msgid "Specify a customization script that runs after your instance launches." -msgstr "" - -#: ../dashboard_launch_instances.rst:124 -msgid "Specify a key pair." -msgstr "" - -#: ../dashboard_databases.rst:131 -msgid "Specify a name for the backup." -msgstr "" - -#: ../dashboard_stacks.rst:83 -msgid "Specify the Linux distribution that is used in the stack." -msgstr "" - -#: ../dashboard_manage_images.rst:64 -msgid "" -"Specify the architecture. For example, ``i386`` for a 32-bit architecture or " -"``x86_64`` for a 64-bit architecture." -msgstr "" - -#: ../dashboard_stacks.rst:98 -msgid "Specify the flavor for the instance." -msgstr "" - -#: ../dashboard_stacks.rst:80 -msgid "Specify the name of the database user." -msgstr "" - -#: ../dashboard_stacks.rst:92 -msgid "Specify the name of the database." -msgstr "" - -#: ../dashboard_stacks.rst:89 -msgid "Specify the name of the key pair to use to log in to the stack." -msgstr "" - -#: ../dashboard_stacks.rst:67 -msgid "" -"Specify the number of minutes that can elapse before the launch of the stack " -"times out." -msgstr "" - -#: ../dashboard_stacks.rst:95 -msgid "Specify the password of the database." -msgstr "" - -#: ../dashboard_stacks.rst:76 -msgid "" -"Specify the password that the default user uses when the stack is created." -msgstr "" - -#: ../dashboard_stacks.rst:86 -msgid "Specify the root password for the database." -msgstr "" - -#: ../dashboard_launch_instances.rst:73 -msgid "Specify the size of the instance to launch." -msgstr "" - -#: ../cli_cheat_sheet.rst:183 -msgid "Start" -msgstr "" - -#: ../cli_cheat_sheet.rst:239 -msgid "Start an instance (boot)" -msgstr "" - -#: ../backup_db.rst:141 -msgid "Start by getting the ID of the new ``guest2`` instance." -msgstr "" - -#: ../cli_swift_static_website.rst:48 -msgid "Static Web middleware through Object Storage" -msgstr "" - -#: ../cli_swift_large_object_creation.rst:259 -msgid "Static large object" -msgstr "" - -#: ../cli_swift_large_object_creation.rst:88 -msgid "Static large object manifest list" -msgstr "" - -#: ../cli_swift_large_object_creation.rst:34 -#: ../cli_swift_large_object_creation.rst:55 -msgid "Static large objects" -msgstr "" - -#: ../cli_ceilometer.rst:48 -msgid "Statistic" -msgstr "" - -#: ../cli_cheat_sheet.rst:177 -msgid "Stop" -msgstr "" - -#: ../cli_stop_and_start_an_instance.rst:3 -msgid "Stop and start an instance" -msgstr "" - -#: ../cli_config_drive.rst:3 -msgid "Store metadata on a configuration drive" -msgstr "" - -#: ../cli_ceilometer.rst:24 -msgid "String name" -msgstr "" - -#: ../cli_swift_static_website.rst:89 -msgid "Style the file listing using a CSS." -msgstr "" - -#: ../cli_cheat_sheet.rst:165 -msgid "Suspend" -msgstr "" - -#: ../cli_stop_and_start_an_instance.rst:22 -msgid "Suspend and resume an instance" -msgstr "" - -#: ../cli_create_and_manage_networks.rst:148 -msgid "" -"Take note of the unique router identifier returned, this will be required in " -"subsequent steps." -msgstr "" - -#: ../cli_nova_launch_instance_from_volume.rst:14 -msgid "Task" -msgstr "" - -#: ../cli_ceilometer.rst:5 -msgid "" -"Telemetry measures cloud resources in OpenStack. It collects data related to " -"billing. Currently, this metering service is available through only the :" -"command:`ceilometer` command-line client." -msgstr "" - -#: ../backup_db.rst:208 -msgid "" -"Tell the users who were accessing the now-disabled ``guest1`` database " -"instance that they can now access ``guest2``. Provide them with ``guest2``'s " -"name, IP address, and any other information they might need. (You can get " -"this information by using the trove ``show`` command.)" -msgstr "" - -#: ../cli_launch_instances.rst:20 -msgid "" -"The **flavor** for your instance, which defines the compute, memory, and " -"storage capacity of nova computing instances. A flavor is an available " -"hardware configuration for a server. It defines the size of a virtual server " -"that can be launched." -msgstr "" - -#: ../cli_launch_instances.rst:15 -msgid "" -"The **instance source** can be an image, snapshot, or block storage volume " -"that contains an image or snapshot." -msgstr "" - -#: ../cli_use_snapshots_to_migrate_instances.rst:92 -msgid "" -"The :command:`glance image-download` command requires the image ID and " -"cannot use the image name. Check there is sufficient space on the " -"destination file system for the image file." -msgstr "" - -#: ../cli_config_drive.rst:247 -msgid "" -"The :file:`openstack/2012-08-10/user_data`, :file:`openstack/latest/" -"user_data`, :file:`ec2/2009-04-04/user-data`, and :file:`ec2/latest/user-" -"data` file are present only if the ``--user-data`` flag and the contents of " -"the user data file are passed to the :command:`nova boot` command." -msgstr "" - -#: ../dashboard_manage_images.rst:37 -msgid "The :guilabel:`Create An Image` dialog box appears." -msgstr "" - -#: ../dashboard_manage_containers.rst:167 -msgid "" -"The :guilabel:`Create Pseudo-Folder in Container` *`` ``* dialog box " -"is displayed. *`` ``* is the name of the container to which you are " -"uploading the object." -msgstr "" - -#: ../dashboard_manage_containers.rst:85 -msgid "The :guilabel:`Edit Object` dialog box is displayed." -msgstr "" - -#: ../configure_access_and_security_for_instances.rst:199 -msgid "" -"The :guilabel:`IP Address` field is filled automatically, but you can add a " -"new IP address by clicking the :guilabel:`+` button." -msgstr "" - -#: ../dashboard_launch_instances.rst:166 -msgid "" -"The :guilabel:`Instances` tab shows the instance's name, its private and " -"public IP addresses, size, status, task, and power state." -msgstr "" - -#: ../dashboard_create_networks.rst:108 -msgid "" -"The :guilabel:`Router Name` and :guilabel:`Router ID` fields are " -"automatically updated." -msgstr "" - -#: ../dashboard_stacks.rst:134 -msgid "The :guilabel:`Update Stack Parameters` window appears." -msgstr "" - -#: ../dashboard_manage_containers.rst:52 -msgid "" -"The :guilabel:`Upload Object To Container: ` dialog box appears. " -"*````* is the name of the container to which you are uploading the " -"object." -msgstr "" - -#: ../dashboard_manage_containers.rst:139 -msgid "" -"The :guilabel:`Upload Object To Container`: *````* dialog box is " -"displayed." -msgstr "" - -#: ../cli_create_and_manage_stacks.rst:33 -msgid "" -"The :option:`--parameters` values that you specify depend on the parameters " -"that are defined in the template. If a website hosts the template file, you " -"can specify the URL with the :option:`--template-url` parameter instead of " -"the :option:`--template-file` parameter." -msgstr "" - -#: ../cli_create_and_manage_networks.rst:115 -msgid "The CIDR of the subnet." -msgstr "" - -#: ../configure_access_and_security_for_instances.rst:158 -msgid "The Compute database registers the public key of the key pair." -msgstr "" - -# #-#-#-#-# dashboard_databases.pot (End User Guide 1.0.0) #-#-#-#-# -# #-#-#-#-# trove-manage-db.pot (End User Guide 1.0.0) #-#-#-#-# -#: ../dashboard_databases.rst:5 ../trove-manage-db.rst:4 -msgid "" -"The Database service provides scalable and reliable cloud provisioning " -"functionality for both relational and non-relational database engines. Users " -"can quickly and easily use database features without the burden of handling " -"complex administrative tasks." -msgstr "" - -#: ../cli_swift_archive_auto_extract.rst:57 -msgid "" -"The GNU tar format. Includes the long name, long link, and sparse extensions." -msgstr "" - -#: ../hot.rst:5 -msgid "" -"The HOT Guide is now maintained as part of the Heat repository and is " -"available on the OpenStack developer documentation website: `Heat Template " -"Guide `__" -msgstr "" - -#: ../cli_nova_launch_instance_from_volume.rst:190 -msgid "The ID of the source object." -msgstr "" - -#: ../cli_manage_ip_addresses.rst:142 -msgid "" -"The IP address is returned to the pool of IP addresses that is available for " -"all projects. If the IP address is still associated with a running instance, " -"it is automatically disassociated from that instance." -msgstr "" - -#: ../sdk_manage_images.rst:105 -msgid "" -"The Image service Python bindings do not support the retrieval of an image " -"object by name. However, the Compute Python bindings enable you to get an " -"image object by name. To get an image object by name, call the ``novaclient." -"v1_1.images.ImageManager.find`` method:" -msgstr "" - -#: ../dashboard_launch_instances.rst:222 -msgid "The Images category shows the instance snapshot." -msgstr "" - -#: ../cli_swift_large_object_creation.rst:80 -msgid "" -"The MD5 checksum of the content of the segment object. This value must match " -"the ``ETag`` of that object." -msgstr "" - -#: ../cli_swift_archive_auto_extract.rst:13 -msgid "" -"The Object Storage system extracts files from the archive file and creates " -"an object." -msgstr "" - -#: ../dashboard_create_networks.rst:5 -msgid "" -"The OpenStack Networking service provides a scalable system for managing the " -"network connectivity within an OpenStack cloud deployment. It can easily and " -"quickly react to changing network needs (for example, creating and assigning " -"new IP addresses)." -msgstr "" - -#: ../managing-openstack-object-storage-with-swift-cli.rst:5 -msgid "" -"The OpenStack Object Storage service provides the ``swift`` client, which is " -"a command-line interface (CLI). Use this client to list objects and " -"containers, upload objects to containers, and download or delete objects " -"from containers. You can also gather statistics and update metadata for " -"accounts, containers, and objects." -msgstr "" - -#: ../sdk.rst:5 -msgid "" -"The OpenStack Python Software Development Kit (SDK) is used to write Python " -"automation scripts that create and manage resources in your OpenStack cloud. " -"The SDK implements Python bindings to the OpenStack API, which enables you " -"to perform automation tasks in Python by making calls on Python objects, " -"rather than making REST calls directly. All OpenStack command-line tools are " -"implemented using the Python SDK." -msgstr "" - -#: ../cli_create_and_manage_stacks.rst:5 -msgid "" -"The Orchestration module enables you to orchestrate multiple composite cloud " -"applications. This module supports use of both the Amazon Web Services (AWS) " -"CloudFormation template format through both a Query API that is compatible " -"with CloudFormation and the native OpenStack :term:`Heat Orchestration " -"Template (HOT)` format through a REST API." -msgstr "" - -#: ../cli_swift_archive_auto_extract.rst:55 -msgid "The POSIX.1-1988 Ustar format." -msgstr "" - -#: ../cli_swift_archive_auto_extract.rst:60 -msgid "The POSIX.1-2001 pax format." -msgstr "" - -#: ../sdk_configure_access_security_instances.rst:30 -msgid "The Python script output looks something like this:" +"If you authenticate against an endpoint that uses a custom authentication " +"back end, you must load the authentication plug-in and pass it to the " +"constructor." msgstr "" #: ../sdk_authenticate_against_compute_endpoint.rst:40 @@ -5891,1019 +7726,15 @@ msgid "" "authenticate against the Rackspace custom authentication back end." msgstr "" -#: ../cli_swift_static_website.rst:18 +#: ../sdk_authenticate_against_compute_endpoint.rst:65 msgid "" -"The Static Web filter must be added to the pipeline in your ``/etc/swift/" -"proxy-server.conf`` file below any authentication middleware. You must also " -"add a Static Web middleware configuration section." +"If you set the ``OS_AUTH_SYSTEM`` environment variable, check for this " +"variable in your Python script to determine whether you need to load a " +"custom authentication back end:" msgstr "" -#: ../backup_db_incremental.rst:40 -msgid "" -"The ``BACKUP_ID`` of the parent backup. In this case, the parent is the " -"regular backup, with an ID of ``6dc3a9b7-1f3e-4954-8582-3f2e4942cddd``" -msgstr "" - -#: ../cli_swift_large_object_creation.rst:309 -msgid "" -"The ``COPY`` operation does not create a manifest object. To duplicate a " -"manifest object, use the ``GET`` operation to read the value of ``X-Object-" -"Manifest`` and use this value in the ``X-Object-Manifest`` request header in " -"a ``PUT`` operation. This creates a new manifest object that shares the same " -"set of segment objects as the original manifest object." -msgstr "" - -#: ../cli_swift_large_object_creation.rst:116 -msgid "" -"The ``Content-Length`` request header must contain the length of the JSON " -"content—not the length of the segment objects. However, after the ``PUT`` " -"operation completes, the ``Content-Length`` metadata is set to the total " -"length of all the object segments. A similar situation applies to the " -"``ETag``. If used in the ``PUT`` operation, it must contain the MD5 checksum " -"of the JSON content. The ``ETag`` metadata value is then set to be the MD5 " -"checksum of the concatenated ``ETag`` values of the object segments. You can " -"also set the ``Content-Type`` request header and custom object metadata." -msgstr "" - -#: ../cli_swift_large_object_creation.rst:242 -msgid "" -"The ``Content-Type`` in the response for a ``GET`` or ``HEAD`` on the " -"manifest is the same as the ``Content-Type`` set during the ``PUT`` request " -"that created the manifest. You can change the ``Content-Type`` by reissuing " -"the ``PUT`` request." -msgstr "" - -#: ../cli_swift_bulk_delete.rst:21 -msgid "The ``DELETE`` operation is supported for backwards compatibility." -msgstr "" - -#: ../backup_db_incremental.rst:34 -msgid "" -"The ``INSTANCE_ID`` of the database instance you are doing the incremental " -"backup for (in this example, ``792a6a56-278f-4a01-9997-d997fa126370``)" -msgstr "" - -#: ../cli_nova_launch_instance_using_ISO_image.rst:109 -msgid "" -"The ``VOLUME_UUID`` is the uuid of the volume that is attached to your ISO " -"created instance, and the ``IMAGE_NAME`` is the name that you give to your " -"new image." -msgstr "" - -#: ../cli_swift_large_object_creation.rst:300 -msgid "" -"The ``X-Object-Manifest`` value is the ``CONTAINER/PREFIX``, which indicates " -"where the segment objects are located. You supply this request header in the " -"``PUT`` operation." -msgstr "" - -#: ../create_db.rst:103 -msgid "The ``myDB`` database." -msgstr "" - -#: ../sdk_compute_apis.rst:361 -msgid "" -"The ``print_flavors`` method is defined in ``utils.py`` and prints the " -"flavor details:" -msgstr "" - -#: ../sdk_compute_apis.rst:497 -msgid "" -"The ``print_hosts`` method is defined in ``utils.py`` and prints the host " -"object details:" -msgstr "" - -#: ../sdk_compute_apis.rst:428 -msgid "" -"The ``print_values_ip`` method is defined in ``utils.py`` and prints the " -"floating\\_ip object details:" -msgstr "" - -#: ../cli_create_and_manage_networks.rst:107 -msgid "" -"The ``subnet-create`` command has the following positional and optional " -"parameters:" -msgstr "" - -#: ../create_db.rst:108 -msgid "The ``userA`` user with the ``password`` password." -msgstr "" - -#: ../dashboard_manage_volumes.rst:82 -msgid "" -"The actual device name might differ from the volume name because of " -"hypervisor settings." -msgstr "" - -#: ../set_up_clustering.rst:29 -msgid "" -"The administrative user has created an appropriate :ref:`flavor that meets " -"the MongoDB minimum requirements `." -msgstr "" - -#: ../set_up_clustering.rst:26 -msgid "" -"The administrative user has registered a MongoDB datastore type and version." -msgstr "" - -#: ../cli_swift_archive_auto_extract.rst:53 -msgid "The archive auto-extract feature supports these formats:" -msgstr "" - -#: ../cli_nova_configure_access_security_for_instances.rst:24 -msgid "" -"The associated *rules* in each security group control the traffic to " -"instances in the group. Any incoming traffic that is not matched by a rule " -"is denied access by default. You can add rules to or remove rules from a " -"security group, and you can modify rules for the default and any other " -"security group." -msgstr "" - -#: ../cli_swift_env_vars.rst:17 -msgid "The authentication token for Object Storage." -msgstr "" - -#: ../cli_manage_bare_metal_nodes.rst:5 -msgid "" -"The bare-metal driver for OpenStack Compute manages provisioning of physical " -"hardware by using common cloud APIs and tools such as Orchestration (Heat). " -"The use case for this driver is for single tenant clouds such as a high-" -"performance computing cluster, or for deploying OpenStack itself." -msgstr "" - -#: ../cli_swift_large_object_creation.rst:72 -msgid "" -"The body of the ``PUT`` request on the manifest object comprises a JSON " -"list, where each element contains the following attributes:" -msgstr "" - -#: ../set_up_clustering.rst:74 -msgid "" -"The cluster ID displays when you first create a cluster. (If you need to " -"find it later on, use the trove ``cluster-list`` command to list the names " -"and IDs of all the clusters in your system.)" -msgstr "" - -#: ../cli_delete_an_instance.rst:25 -msgid "The command does not notify that your server was deleted." -msgstr "" - -#: ../cli_access_instance_through_a_console.rst:32 -msgid "The command returns a URL from which you can access your instance:" -msgstr "" - -#: ../cli_create_and_manage_stacks.rst:38 -msgid "The command returns the following output::" -msgstr "" - -#: ../cli_swift_large_object_creation.rst:76 -msgid "" -"The container and object name in the format: ``CONTAINER_NAME/OBJECT_NAME``." -msgstr "" - -#: ../configure_access_and_security_for_instances.rst:160 -msgid "" -"The dashboard lists the key pair on the :guilabel:`Access & Security` tab." -msgstr "" - -#: ../dashboard_launch_instances.rst:41 -msgid "" -"The dashboard shows the images that have been uploaded to OpenStack Image " -"service and are available for this project." -msgstr "" - -#: ../dashboard_manage_volumes.rst:87 -msgid "" -"The dashboard shows the instance to which the volume is now attached and the " -"device name." -msgstr "" - -#: ../dashboard_create_networks.rst:66 -msgid "The dashboard shows the network on the :guilabel:`Networks` tab." -msgstr "" - -#: ../dashboard_manage_volumes.rst:126 -msgid "The dashboard shows the new volume snapshot in Volume Snapshots tab." -msgstr "" - -#: ../dashboard_manage_shares.rst:212 -msgid "" -"The dashboard shows the security service on the :guilabel:`Security " -"Services` tab." -msgstr "" - -#: ../dashboard_manage_shares.rst:150 -msgid "" -"The dashboard shows the share network on the :guilabel:`Share Networks` tab." -msgstr "" - -#: ../dashboard_manage_shares.rst:37 -msgid "The dashboard shows the share on the :guilabel:`Shares` tab." -msgstr "" - -#: ../dashboard_manage_volumes.rst:58 -msgid "The dashboard shows the volume on the :guilabel:`Volumes` tab." -msgstr "" - -#: ../create_db.rst:105 -msgid "" -"The database is based on the ``mysql`` data store and the ``mysql-5.5`` " -"datastore\\_version." -msgstr "" - -#: ../cli_config_drive.rst:255 -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 :file:" -"`/etc/nova/nova.conf` file::" -msgstr "" - -#: ../cli_delete_an_instance.rst:38 -msgid "The deleted instance does not appear in the list." -msgstr "" - -#: ../dashboard_stacks.rst:118 -msgid "The events related to the stack." -msgstr "" - -#: ../intro-user.rst:8 -msgid "" -"The examples in this guide show you how to perform tasks by using the " -"following methods:" -msgstr "" - -#: ../sdk_neutron_apis.rst:36 -msgid "The examples in this section use the ``get_credentials`` method:" -msgstr "" - -#: ../sdk_neutron_apis.rst:63 -msgid "The examples in this section use the ``get_nova_credentials`` method:" -msgstr "" - -#: ../sdk_neutron_apis.rst:91 -msgid "" -"The examples in this section use the ``print_values`` and " -"``print_values_server`` methods:" -msgstr "" - -#: ../cli_config_drive.rst:155 -msgid "" -"The files that appear on the configuration drive depend on the arguments " -"that you pass to the :command:`nova boot` command." -msgstr "" - -#: ../create_db.rst:23 -msgid "" -"The first step is to list flavors by using the nova ``flavor-list`` command." -msgstr "" - -#: ../cli_nova_launch_instance_from_volume.rst:275 -msgid "" -"The flavor defines the maximum swap and ephemeral disk size. You cannot " -"exceed these maximum values." -msgstr "" - -#: ../dashboard_launch_instances.rst:75 -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 " -"value in the :guilabel:`Minimum RAM (MB)` field as 2048, then on selecting " -"the image, the default flavor is ``m1.small``." -msgstr "" - -#: ../cli_swift_archive_auto_extract.rst:93 -msgid "" -"The following auto-extract archive files example shows a ``text/plain`` " -"response body where no failures occurred:" -msgstr "" - -#: ../cli_swift_archive_auto_extract.rst:101 -msgid "" -"The following auto-extract archive files example shows a ``text/plain`` " -"response where some failures occurred. In this example, the Object Storage " -"system is configured to reject certain character strings so that the 400 Bad " -"Request error occurs for any objects that use the restricted strings." -msgstr "" - -#: ../cli_swift_bulk_delete.rst:77 -msgid "" -"The following bulk delete response is in ``application/xml`` format. In this " -"example, the ``mycontainer`` container is not empty, so it cannot be deleted." -msgstr "" - -#: ../cli_swift_manage_access_swift.rst:28 -msgid "The following command gives object access to all referring domains:" -msgstr "" - -#: ../cli_launch_instances.rst:174 -msgid "" -"The following command launches the ``MyCirrosServer`` instance with the ``m1." -"small`` flavor (ID of ``1``), ``cirros-0.3.2-x86_64-uec`` image (ID of " -"``397e713c-b95b-4186-ad46-6126863ea0a9``), ``default`` security group, " -"``KeyPair01`` key, and a user data file called ``cloudinit.file``::" -msgstr "" - -#: ../cli_manage_bare_metal_nodes.rst:22 -msgid "The following commands can be used to manage bare-metal nodes." -msgstr "" - -#: ../cli_swift_manage_access_swift.rst:15 -msgid "" -"The following example enables the ``testuser`` user to read objects in the " -"container:" -msgstr "" - -#: ../cli_config_drive.rst:81 -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_manage_bare_metal_nodes.rst:57 -msgid "" -"The following example shows the command and results from creating a node " -"with the PM address ``1.2.3.4``, the PM user name ipmi, and password " -"``ipmi``." -msgstr "" - -#: ../cli_config_drive.rst:203 -msgid "" -"The following example shows the contents of the :file:`ec2/2009-04-04/meta-" -"data.json` and the :file:`ec2/latest/meta-data.json` files. These files are " -"identical. The file contents are formatted to improve readability." -msgstr "" - -#: ../cli_config_drive.rst:161 -msgid "" -"The following example shows the contents of the :file:`openstack/2012-08-10/" -"meta_data.json` and :file:`openstack/latest/meta_data.json` files. These " -"files are identical. The file contents are formatted for readability." -msgstr "" - -#: ../cli_swift_archive_auto_extract.rst:114 -msgid "" -"The following example shows the failure response in ``application/json`` " -"format." -msgstr "" - -#: ../cli_search_instance_with_ip_address.rst:12 -msgid "The following example shows the results of a search on ``10.0.0.4``." -msgstr "" - -#: ../cli_config_drive.rst:28 -msgid "" -"The following hypervisors support the configuration drive: libvirt, " -"XenServer, Hyper-V, and VMware." -msgstr "" - -#: ../sdk_neutron_apis.rst:133 -msgid "The following program creates a network:" -msgstr "" - -#: ../sdk_neutron_apis.rst:190 -msgid "The following program creates a port:" -msgstr "" - -#: ../sdk_compute_apis.rst:92 -msgid "" -"The following program creates a server (VM) by using the Compute API v2." -msgstr "" - -#: ../sdk_compute_apis.rst:171 -msgid "" -"The following program deletes a server (VM) by using the Compute API v2." -msgstr "" - -#: ../sdk_compute_apis.rst:350 -msgid "" -"The following program lists flavors and their details by using the Compute " -"API v2." -msgstr "" - -#: ../sdk_neutron_apis.rst:167 -msgid "The following program lists networks:" -msgstr "" - -#: ../sdk_neutron_apis.rst:236 -msgid "The following program lists ports:" -msgstr "" - -#: ../sdk_compute_apis.rst:49 -msgid "The following program lists servers by using the Compute API v2." -msgstr "" - -#: ../sdk_compute_apis.rst:417 -msgid "" -"The following program lists the floating IPs and their details by using the " -"Compute API v2." -msgstr "" - -#: ../sdk_compute_apis.rst:487 -msgid "The following program lists the hosts by using the Compute API v2." -msgstr "" - -#: ../sdk_neutron_apis.rst:260 -msgid "The following program lists the ports for a server:" -msgstr "" - -#: ../sdk_compute_apis.rst:253 -msgid "" -"The following program updates the name of a server (VM) by using the Compute " -"API v2." -msgstr "" - -#: ../cli_swift_static_website.rst:50 -msgid "" -"The following sections show how to use Static Web middleware through Object " -"Storage." -msgstr "" - -#: ../dashboard_manage_images.rst:86 -msgid "" -"The image is queued to be uploaded. It might take some time before the " -"status changes from Queued to Active." -msgstr "" - -#: ../sdk_manage_images.rst:25 -msgid "" -"The images method returns a Python generator, as shown in the following " -"interaction with the Python interpreter:" -msgstr "" - -#: ../cli_manage_ip_addresses.rst:106 -msgid "The instance is now associated with two IP addresses::" -msgstr "" - -#: ../dashboard_launch_instances.rst:164 -msgid "The instance starts on a compute node in the cloud." -msgstr "" - -#: ../cli_nova_launch_instance_using_ISO_image.rst:116 -msgid "" -"The instances launched using this image contain the system that you have " -"just installed using the ISO image." -msgstr "" - -#: ../configure_access_and_security_for_instances.rst:206 -msgid "The list shows all the instances with their fixed IP addresses." -msgstr "" - -#: ../cli_launch_instances.rst:248 -msgid "" -"The list shows the ID, name, status, and private (and if assigned, public) " -"IP addresses for all instances in the project to which you belong::" -msgstr "" - -#: ../cli_swift_large_object_creation.rst:293 -msgid "" -"The manifest list includes the container name of each object. Segment " -"objects can be in different containers." -msgstr "" - -#: ../cli_swift_large_object_creation.rst:33 -msgid "" -"The manifest object content is an ordered list of the names of the segment " -"objects in JSON format. See :ref:`static_large_objects`." -msgstr "" - -#: ../cli_swift_large_object_creation.rst:37 -msgid "" -"The manifest object has no content but it has a ``X-Object-Manifest`` " -"metadata header. The value of this header is ``CONTAINER/PREFIX``, where " -"``CONTAINER`` is the name of the container where the segment objects are " -"stored, and ``PREFIX`` is a string that all segment objects have in common. " -"See :ref:`dynamic_large_objects`." -msgstr "" - -#: ../set_up_clustering.rst:42 -msgid "The name and version of the datastore you want to use." -msgstr "" - -#: ../set_up_clustering.rst:40 -msgid "The name of the cluster." -msgstr "" - -#: ../backup_db_incremental.rst:38 -msgid "The name of the incremental backup you are creating: ``backup1.1``" -msgstr "" - -#: ../backup_db_incremental.rst:68 -msgid "" -"The name of your second incremental backup is ``backup1.2``. This time, when " -"you specify the parent, pass in the ID of the incremental backup you just " -"created in the previous step (``backup1.1``). In this example, it is " -"``1d474981-a006-4f62-b25f-43d7b8a7097e``." -msgstr "" - -#: ../cli_create_and_manage_networks.rst:110 -msgid "The name or ID of the network to which the subnet belongs." -msgstr "" - -#: ../dashboard_launch_instances.rst:62 -msgid "The name you assign here becomes the initial host name of the server." -msgstr "" - -#: ../dashboard_databases.rst:164 -msgid "The new instance appears in the database instances list." -msgstr "" - -#: ../dashboard_create_networks.rst:84 -msgid "The new router is now displayed in the :guilabel:`Routers` tab." -msgstr "" - -#: ../cli_swift_bulk_delete.rst:69 -msgid "The number of files actually deleted." -msgstr "" - -#: ../cli_swift_bulk_delete.rst:71 -msgid "The number of not found objects." -msgstr "" - -#: ../cli_swift_large_object_creation.rst:297 -msgid "" -"The object has ``X-Static-Large-Object`` set to ``true``. You do not set " -"this metadata directly. Instead the system sets it when you ``PUT`` a static " -"manifest object." -msgstr "" - -#: ../dashboard_stacks.rst:112 -msgid "The parameters and details of the stack." -msgstr "" - -#: ../cli_nova_launch_instance_from_volume.rst:178 -msgid "The parameters are:" -msgstr "" - -#: ../cli_swift_bulk_delete.rst:23 -msgid "" -"The path is the account, such as ``/v1/12345678912345``, that contains the " -"objects and containers." -msgstr "" - -#: ../cli_swift_archive_auto_extract.rst:26 -msgid "" -"The path you specify in the ``PUT`` request is used for the location of the " -"object and the prefix for the resulting object names." -msgstr "" - -#: ../cli_swift_env_vars.rst:11 -msgid "" -"The public URL that is the HTTP endpoint from where you can access Object " -"Storage. It includes the Object Storage API version number and your account " -"name. For example, ``https://23.253.72.207/v1/my_account``." -msgstr "" - -#: ../cli_swift_serialized_response_formats.rst:122 -msgid "" -"The remainder of the examples in this guide use standard, non-serialized " -"responses. However, all ``GET`` requests that perform list operations accept " -"the ``format`` query parameter or ``Accept`` request header." -msgstr "" - -#: ../dashboard_stacks.rst:115 -msgid "The resources used by the stack." -msgstr "" - -#: ../cli_swift_bulk_delete.rst:67 -msgid "The response body contains the following information:" -msgstr "" - -#: ../cli_change_the_size_of_your_server.rst:100 -#: ../cli_change_the_size_of_your_server.rst:108 -msgid "The server status becomes ACTIVE." -msgstr "" - -#: ../cli_change_the_size_of_your_server.rst:42 -msgid "The size (flavor) of the server is ``m1.small (2)``." -msgstr "" - -#: ../cli_swift_large_object_creation.rst:84 -msgid "" -"The size of the segment object. This value must match the ``Content-Length`` " -"of that object." -msgstr "" - -#: ../cli_nova_launch_instance_from_volume.rst:197 -msgid "The size of the volume that is created." -msgstr "" - -#: ../cli_create_and_manage_networks.rst:120 -msgid "The subnet name, which is optional." -msgstr "" - -#: ../cli_swift_pseudo_hierarchical_folders_directories.rst:96 -msgid "" -"The system returns status code 2xx (between 200 and 299, inclusive) and the " -"objects and pseudo-directories within the nested pseudo-directory." -msgstr "" - -#: ../cli_swift_pseudo_hierarchical_folders_directories.rst:74 -msgid "" -"The system returns status code 2xx (between 200 and 299, inclusive) and the " -"objects and pseudo-directories within the top level pseudo-directory." -msgstr "" - -#: ../cli_swift_pseudo_hierarchical_folders_directories.rst:32 -msgid "" -"The system returns status code 2xx (between 200 and 299, inclusive) and the " -"requested list of the objects." -msgstr "" - -#: ../cli_swift_pseudo_hierarchical_folders_directories.rst:55 -msgid "" -"The system returns status code 2xx (between 200 and 299, inclusive) and the " -"requested matching objects. Because you use the slash, only the pseudo-" -"directory ``photos/`` displays. The returned values from a slash " -"``delimiter`` query are not real objects. They have a content-type of " -"``application/directory`` and are in the ``subdir`` section of JSON and XML " -"results." -msgstr "" - -#: ../cli_create_and_manage_stacks.rst:18 -msgid "" -"The template languages are described in `the Template Guide `__ in the `Heat " -"developer documentation `__." -msgstr "" - -#: ../dashboard_stacks.rst:20 -msgid "" -"The template languages are described in the `Template Guide `_ in the `Heat " -"developer documentation `_." -msgstr "" - -#: ../set_up_clustering.rst:44 -msgid "" -"The three instances you want to include in the replication set for the first " -"shard. Specify each instance by using the ``--instance`` argument and the " -"associated flavor ID and volume size. Use the same flavor ID and volume size " -"for each instance. In this example, flavor ``7`` is a custom flavor that " -"meets the MongoDB minimum requirements." -msgstr "" - -# #-#-#-#-# cli_change_the_size_of_your_server.pot (End User Guide 1.0.0) #-#-#-#-# -# #-#-#-#-# cli_reboot_an_instance.pot (End User Guide 1.0.0) #-#-#-#-# -# #-#-#-#-# cli_stop_and_start_an_instance.pot (End User Guide 1.0.0) #-#-#-#-# -#: ../cli_change_the_size_of_your_server.rst:80 -#: ../cli_reboot_an_instance.rst:54 ../cli_stop_and_start_an_instance.rst:66 -msgid "" -"The timeout value can be overridden on a per image basis by means of " -"``os_shutdown_timeout`` that is an image metadata setting allowing different " -"types of operating systems to specify how much time they need to shut down " -"cleanly." -msgstr "" - -#: ../dashboard_stacks.rst:109 -msgid "The topology of the stack." -msgstr "" - -#: ../cli_nova_launch_instance_from_volume.rst:186 -msgid "" -"The type of object used to create the block device. Valid values are " -"``volume``, ``snapshot``, ``image``, and ``blank``." -msgstr "" - -#: ../cli_nova_launch_instance_from_volume.rst:193 -msgid "" -"The type of the target virtual device. Valid values are ``volume`` and " -"``local``." -msgstr "" - -#: ../dashboard_launch_instances.rst:179 -msgid "The user name is ``ubuntu`` for the Ubuntu cloud images on TryStack." -msgstr "" - -#: ../cli_access_instance_through_a_console.rst:9 -msgid "" -"There are three remote console access methods commonly used with OpenStack:" -msgstr "" - -#: ../dashboard_stacks.rst:12 -msgid "" -"These flexible template languages enable application developers to describe " -"and automate the deployment of infrastructure, services, and applications. " -"The templates enable creation of most OpenStack resource types, such as " -"instances, floating IP addresses, volumes, security groups, and users. Once " -"created, the resources are referred to as stacks." -msgstr "" - -#: ../cli_create_and_manage_stacks.rst:11 -msgid "" -"These flexible template languages enable application developers to describe " -"and automate the deployment of infrastructure, services, and applications. " -"The templates enable creation of most OpenStack resource types, such as " -"instances, floating IP addresses, volumes, security groups, and users. The " -"resources, once created, are referred to as stacks." -msgstr "" - -#: ../cli_swift_set_object_versions.rst:83 -msgid "These non-current versions are named as follows:" -msgstr "" - -#: ../cli_nova_configure_access_security_for_instances.rst:150 -msgid "This allows access to all codes and all types of ICMP traffic." -msgstr "" - -#: ../intro-user.rst:33 -msgid "" -"This book is written for anyone who uses virtual machines and cloud " -"resources to develop software or perform research. You should have years of " -"experience with Linux-based tool sets and be comfortable using both GUI and " -"CLI based tools. While this book includes some information about using " -"Python to create and manage cloud resources, Python knowledge is not a pre-" -"requisite for reading this book." -msgstr "" - -#: ../managing-openstack-object-storage-with-swift-cli.rst:11 -msgid "" -"This client is based on the native swift client library, ``client.py``, " -"which seamlessly re-authenticates if the current token expires during " -"processing, retries operations multiple times, and provides a processing " -"concurrency of 10." -msgstr "" - -# #-#-#-#-# sdk_compute_apis.pot (End User Guide 1.0.0) #-#-#-#-# -# #-#-#-#-# sdk_neutron_apis.pot (End User Guide 1.0.0) #-#-#-#-# -#: ../sdk_compute_apis.rst:36 ../sdk_neutron_apis.rst:49 -#: ../sdk_neutron_apis.rst:76 -msgid "" -"This code resides in the ``credentials.py`` file, which all samples import." -msgstr "" - -#: ../sdk_neutron_apis.rst:126 -msgid "This code resides in the ``utils.py`` file, which all samples import." -msgstr "" - -#: ../cli_nova_configure_access_security_for_instances.rst:69 -msgid "" -"This command generates a key pair with the name that you specify for KEY" -"\\_NAME, writes the private key to the :file:`.pem` file that you specify, " -"and registers the public key to the Nova database." -msgstr "" - -#: ../cli_nova_configure_access_security_for_instances.rst:87 -msgid "" -"This command registers the public key at the Nova database and names the key " -"pair the name that you specify for ``KEY_NAME``." -msgstr "" - -#: ../create_db.rst:167 -msgid "This command returns the IP address of the database instance." -msgstr "" - -#: ../create_db.rst:143 -msgid "This command returns the instance ID of your new instance." -msgstr "" - -#: ../cli_stop_and_start_an_instance.rst:14 -msgid "" -"This command stores the state of the VM in RAM. A paused instance continues " -"to run in a frozen state." -msgstr "" - -#: ../backup_db.rst:45 -msgid "" -"This command syntax pertains only to python-troveclient version 1.0.6 and " -"later. Earlier versions require you to pass in the backup name as the first " -"argument." -msgstr "" - -#: ../manage_db_config.rst:181 -msgid "" -"This command syntax pertains only to python-troveclient version 1.0.6 and " -"later. Earlier versions require you to pass in the configuration group ID as " -"the first argument." -msgstr "" - -#: ../sdk_assign_cors_headers.rst:22 -msgid "" -"This example assigns the file origin to the ``Origin`` header, which ensures " -"that the file originated from a reputable source::" -msgstr "" - -#: ../manage_db_config.rst:9 -msgid "" -"This example assumes you have created a MySQL database and shows you how to " -"use a configuration group to configure it. Although this example sets just " -"one option on one database, you can use these same procedures to set " -"multiple options on multiple database instances throughout your environment. " -"This can provide significant time savings in managing your cloud." -msgstr "" - -#: ../manage_db_config.rst:111 -msgid "" -"This example creates a configuration group called ``group1``. ``group1`` " -"contains just one key and value pair, and this pair sets the ``sync_binlog`` " -"option to ``1``." -msgstr "" - -#: ../create_db.rst:92 -msgid "" -"This example creates a database instance with the following characteristics:" -msgstr "" - -#: ../sdk_neutron_apis.rst:303 -msgid "" -"This example queries OpenStack Networking to create a router and add a port " -"to a subnet." -msgstr "" - -#: ../sdk_neutron_apis.rst:406 -msgid "This example queries OpenStack Networking to delete a network." -msgstr "" - -#: ../sdk_neutron_apis.rst:488 -msgid "This example queries OpenStack Networking to list all routers." -msgstr "" - -#: ../sdk_neutron_apis.rst:543 -msgid "This example queries OpenStack Networking to list security groups." -msgstr "" - -#: ../sdk_neutron_apis.rst:593 -msgid "This example queries OpenStack Networking to list subnets." -msgstr "" - -#: ../sdk_authenticate_against_identity_endpoint.rst:43 -msgid "" -"This example shows a subset of a PKI token. A complete token is over 5000 " -"characters long." -msgstr "" - -#: ../cli_swift_discoverability.rst:25 -msgid "This example shows a truncated response body:" -msgstr "" - -#: ../cli_swift_large_object_creation.rst:90 -msgid "" -"This example shows three segment objects. You can use several containers and " -"the object names do not have to conform to a specific pattern, in contrast " -"to dynamic large objects." -msgstr "" - -# #-#-#-#-# backup_db.pot (End User Guide 1.0.0) #-#-#-#-# -# #-#-#-#-# dashboard_databases.pot (End User Guide 1.0.0) #-#-#-#-# -#: ../backup_db.rst:10 ../dashboard_databases.rst:110 -msgid "This example shows you how to back up and restore a MySQL database." -msgstr "" - -#: ../create_db.rst:10 -msgid "This example shows you how to create and access a MySQL 5.5 database." -msgstr "" - -#: ../set_up_replication.rst:18 -msgid "This example shows you how to replicate a MySQL database instance." -msgstr "" - -#: ../set_up_clustering.rst:22 -msgid "This example shows you how to set up a MongoDB sharded cluster." -msgstr "" - -#: ../backup_db_incremental.rst:13 -msgid "" -"This example shows you how to use incremental backups with a MySQL database." -msgstr "" - -#: ../cli_ceilometer.rst:62 -msgid "" -"This example uses the :command:`heat` client to create an auto-scaling stack " -"and the :command:`ceilometer` client to measure resources." -msgstr "" - -#: ../sdk_compute_apis.rst:22 -msgid "This example uses the ``get_nova_credentials_v2`` method:" -msgstr "" - -#: ../dashboard_launch_instances.rst:117 -msgid "" -"This field changes based on your previous selection. Since 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 "" - -#: ../index.rst:14 -msgid "" -"This guide documents OpenStack Kilo, OpenStack Juno, and OpenStack Icehouse " -"releases." -msgstr "" - -#: ../cli_swift_set_object_versions.rst:179 -msgid "" -"This next-most current version carries with it any metadata last set on it. " -"If you want to completely remove an object and you have five versions of it, " -"you must ``DELETE`` it five times." -msgstr "" - -#: ../cli_swift_discoverability.rst:41 -msgid "" -"This output shows that the Object Storage system has enabled the static " -"website and temporary URL features." -msgstr "" - -#: ../configure_access_and_security_for_instances.rst:41 -msgid "" -"This procedure can be adjusted as necessary to add additional security group " -"rules to a project, if your cloud requires them." -msgstr "" - -#: ../configure_access_and_security_for_instances.rst:36 -msgid "" -"This procedure enables SSH and ICMP (ping) access to instances. The rules " -"apply to all instances within a given project, and should be set for every " -"project unless there is a reason to prohibit SSH or ICMP access to the " -"instances." -msgstr "" - -#: ../cli_swift_serialized_response_formats.rst:81 -msgid "" -"This request uses the ``Accept`` request header to ask for an XML response:" -msgstr "" - -#: ../cli_manage_instances_hosts.rst:9 -msgid "" -"This section describes how to perform the different tasks involved in " -"instance management, such as adding floating IP addresses, stopping and " -"starting instances, and terminating instances. This section also discusses " -"node management tasks." -msgstr "" - -#: ../configure_access_and_security_for_instances.rst:69 -msgid "" -"To accept requests from a particular range of IP addresses, specify the IP " -"address block in the :guilabel:`CIDR` box." -msgstr "" - -#: ../cli_access_instance_through_a_console.rst:25 -msgid "" -"To access an instance through a remote console, run the following command:" -msgstr "" - -#: ../dashboard_launch_instances.rst:142 -msgid "" -"To add a network to the instance, click the :guilabel:`+` in the :guilabel:" -"`Available Networks` field." -msgstr "" - -#: ../sdk_configure_access_security_instances.rst:169 -msgid "" -"To add a rule to a security group, call the `novaclient.v1\\_1.security" -"\\_group\\_rules.SecurityGroupRuleManager.create `__ method:" -msgstr "" - -#: ../configure_access_and_security_for_instances.rst:77 -msgid "To add an ICMP rule, click :guilabel:`Add Rule`." -msgstr "" - -#: ../cli_nova_configure_access_security_for_instances.rst:129 -msgid "" -"To allow SSH access to the instances, choose one of the following options:" -msgstr "" - -#: ../configure_access_and_security_for_instances.rst:59 -msgid "To allow SSH access, click :guilabel:`Add Rule`." -msgstr "" - -#: ../cli_nova_configure_access_security_for_instances.rst:158 -msgid "" -"To allow access through a UDP port, such as allowing access to a DNS server " -"that runs on a VM, choose one of the following options:" -msgstr "" - -#: ../cli_nova_configure_access_security_for_instances.rst:143 -msgid "To allow pinging of the instances, choose one of the following options:" -msgstr "" - -#: ../cli_nova_launch_instance_from_volume.rst:40 -msgid "" -"To attach a volume to a running instance, see :ref:" -"`Attach_a_volume_to_an_instance`." -msgstr "" - -#: ../sdk_authenticate_against_compute_endpoint.rst:8 -msgid "" -"To authenticate against a Compute endpoint, instantiate a `novaclient.v" -"\\_1\\_1.client.Client `__ " -"object:" -msgstr "" - -#: ../sdk_authenticate_against_networking_endpoint.rst:8 -msgid "" -"To authenticate against a Networking endpoint, instantiate a ``neutronclient." -"v_2_0.client.Client`` object:" -msgstr "" - -#: ../sdk_authenticate_against_image_service_endpoint.rst:8 -msgid "" -"To authenticate against an Image service endpoint, instantiate a " -"`glanceclient.v2.client.Client `__ object:" +#: ../sdk_authenticate_against_identity_endpoint.rst:6 +msgid "Authenticate against an Identity endpoint" msgstr "" #: ../sdk_authenticate_against_identity_endpoint.rst:8 @@ -6914,254 +7745,355 @@ msgid "" "v2_0.client.Client>`__ object:" msgstr "" -#: ../dashboard_databases.rst:113 -msgid "To backup the database instance" -msgstr "" - -#: ../dashboard_launch_instances.rst:23 +#: ../sdk_authenticate_against_identity_endpoint.rst:22 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." +"After you instantiate a ``Client`` object, you can retrieve the token by " +"accessing its ``auth_token`` attribute object:" msgstr "" -#: ../configure_access_and_security_for_instances.rst:140 +#: ../sdk_authenticate_against_identity_endpoint.rst:31 msgid "" -"To change its permissions so that only you can read and write to the file, " -"run the following command:" +"If the OpenStack cloud is configured to use public-key infrastructure (PKI) " +"tokens, the Python script output looks something like this::" msgstr "" -#: ../dashboard_databases.rst:196 -msgid "To change the flavor of an instance" -msgstr "" - -#: ../cli_swift_large_object_creation.rst:148 +#: ../sdk_authenticate_against_identity_endpoint.rst:43 msgid "" -"To change the manifest, use a ``PUT`` operation with the ``?multipart-" -"manifest=put`` query parameter. This request creates a manifest object. You " -"can also update the object metadata in the usual way." +"This example shows a subset of a PKI token. A complete token is over 5000 " +"characters long." msgstr "" -#: ../dashboard_databases.rst:173 -msgid "To change the volume size of an instance" +#: ../sdk_authenticate_against_image_service_endpoint.rst:6 +msgid "Authenticate against an Image service endpoint" msgstr "" -#: ../cli_swift_create_containers.rst:18 -msgid "To check the status of containers, run the following command:" -msgstr "" - -#: ../cli_swift_manage_objects.rst:17 -msgid "To check the status of the object, run the following command:" -msgstr "" - -#: ../cli_nova_launch_instance_from_volume.rst:7 +#: ../sdk_authenticate_against_image_service_endpoint.rst:8 msgid "" -"To complete these tasks, use these parameters on the :command:`nova boot` " -"command:" +"To authenticate against an Image service endpoint, instantiate a " +"`glanceclient.v2.client.Client `__ object:" msgstr "" -#: ../dashboard_create_networks.rst:91 -msgid "" -"To connect a private network to the newly created router, perform the " -"following steps:" +#: ../sdk_authenticate_against_networking_endpoint.rst:6 +msgid "Authenticate against a Networking endpoint" msgstr "" -#: ../cli_nova_launch_instance_from_volume.rst:169 +#: ../sdk_authenticate_against_networking_endpoint.rst:8 msgid "" -"To create a bootable volume from an image and launch an instance from this " -"volume, use the ``--block-device`` parameter." +"To authenticate against a Networking endpoint, instantiate a ``neutronclient." +"v_2_0.client.Client`` object:" msgstr "" -#: ../cli_swift_create_containers.rst:5 +#: ../sdk_authenticate_against_networking_endpoint.rst:22 msgid "" -"To create a container, run the following command and replace ``CONTAINER`` " -"with the name of your container." +"You can also authenticate by explicitly specifying the endpoint and token:" msgstr "" -#: ../cli_nova_launch_instance_from_volume.rst:51 -msgid "" -"To create a non-bootable volume, do not create it from an image. The volume " -"must be entirely empty with no partition table and no file system." +#: ../sdk_compute_apis.rst:6 +msgid "Compute" msgstr "" -#: ../sdk_configure_access_security_instances.rst:119 +#: ../sdk_compute_apis.rst:8 msgid "" -"To create a security group with a specified name and description, call the " -"`novaclient.v\\_1.security\\_groups.SecurityGroupManager.create `__ method:" +"To use the information in this section, you must be familiar with OpenStack " +"Compute." msgstr "" -#: ../cli_nova_configure_access_security_for_instances.rst:103 -msgid "" -"To create a security group with a specified name and description, enter the " -"following command::" +# #-#-#-#-# sdk_compute_apis.pot (End User Guide 1.0.0) #-#-#-#-# +# #-#-#-#-# sdk_neutron_apis.pot (End User Guide 1.0.0) #-#-#-#-# +#: ../sdk_compute_apis.rst:12 ../sdk_neutron_apis.rst:16 +msgid "Set environment variables" msgstr "" -#: ../cli_create_and_manage_stacks.rst:26 +#: ../sdk_compute_apis.rst:14 msgid "" -"To create a stack, or template, from an `example template file `__, run the following command::" +"To set up environmental variables and authenticate against Compute API " +"endpoints, see :ref:`sdk_authenticate`." msgstr "" -#: ../cli_swift_large_object_creation.rst:57 +#: ../sdk_compute_apis.rst:20 +msgid "Get OpenStack credentials (API v2)" +msgstr "" + +#: ../sdk_compute_apis.rst:22 +msgid "This example uses the ``get_nova_credentials_v2`` method:" +msgstr "" + +# #-#-#-#-# sdk_compute_apis.pot (End User Guide 1.0.0) #-#-#-#-# +# #-#-#-#-# sdk_neutron_apis.pot (End User Guide 1.0.0) #-#-#-#-# +#: ../sdk_compute_apis.rst:36 ../sdk_neutron_apis.rst:49 +#: ../sdk_neutron_apis.rst:76 msgid "" -"To create a static large object, divide your content into pieces and create " -"(upload) a segment object to contain each piece." +"This code resides in the ``credentials.py`` file, which all samples import." +msgstr "" + +#: ../sdk_compute_apis.rst:39 +msgid "" +"Use the ``get_nova_credentials_v2()`` method to populate and get a " +"dictionary:" +msgstr "" + +#: ../sdk_compute_apis.rst:47 +msgid "List servers (API v2)" +msgstr "" + +#: ../sdk_compute_apis.rst:49 +msgid "The following program lists servers by using the Compute API v2." +msgstr "" + +# #-#-#-#-# sdk_compute_apis.pot (End User Guide 1.0.0) #-#-#-#-# +# #-#-#-#-# sdk_neutron_apis.pot (End User Guide 1.0.0) #-#-#-#-# +#: ../sdk_compute_apis.rst:51 ../sdk_compute_apis.rst:94 +#: ../sdk_compute_apis.rst:173 ../sdk_compute_apis.rst:256 +#: ../sdk_compute_apis.rst:353 ../sdk_compute_apis.rst:420 +#: ../sdk_compute_apis.rst:489 ../sdk_neutron_apis.rst:307 +#: ../sdk_neutron_apis.rst:410 ../sdk_neutron_apis.rst:490 +#: ../sdk_neutron_apis.rst:545 ../sdk_neutron_apis.rst:595 +msgid "Import the following modules:" +msgstr "" + +#: ../sdk_compute_apis.rst:58 ../sdk_compute_apis.rst:181 +msgid "" +"Get Nova credentials. See :ref:`Get OpenStack credentials (API v2) `." +msgstr "" + +# #-#-#-#-# sdk_compute_apis.pot (End User Guide 1.0.0) #-#-#-#-# +# #-#-#-#-# sdk_neutron_apis.pot (End User Guide 1.0.0) #-#-#-#-# +#: ../sdk_compute_apis.rst:61 ../sdk_compute_apis.rst:105 +#: ../sdk_compute_apis.rst:184 ../sdk_compute_apis.rst:283 +#: ../sdk_compute_apis.rst:377 ../sdk_compute_apis.rst:447 +#: ../sdk_compute_apis.rst:514 ../sdk_neutron_apis.rst:321 +msgid "" +"Instantiate the ``nova_client`` client object by using the ``credentials`` " +"dictionary object:" +msgstr "" + +#: ../sdk_compute_apis.rst:68 +msgid "List servers by calling ``servers.list`` on ``nova_client`` object:" +msgstr "" + +#: ../sdk_compute_apis.rst:75 +msgid "List server code listing example" +msgstr "" + +#: ../sdk_compute_apis.rst:90 +msgid "Create server (API v2)" +msgstr "" + +#: ../sdk_compute_apis.rst:92 +msgid "" +"The following program creates a server (VM) by using the Compute API v2." +msgstr "" + +#: ../sdk_compute_apis.rst:102 ../sdk_compute_apis.rst:444 +#: ../sdk_compute_apis.rst:511 +msgid "" +"Get OpenStack credentials. See :ref:`Get OpenStack credentials (API v2) `." +msgstr "" + +#: ../sdk_compute_apis.rst:112 +msgid "" +"Get the flavor and image to use to create a server. This code uses the " +"``cirros`` image, the ``m1.tiny`` flavor, and the ``private`` network:" msgstr "" #: ../sdk_compute_apis.rst:122 msgid "To create the server, use the network, image, and flavor:" msgstr "" -#: ../cli_swift_serialized_response_formats.rst:14 -msgid "To define the response format, use one of these methods:" -msgstr "" - -#: ../dashboard_manage_containers.rst:34 +#: ../sdk_compute_apis.rst:130 msgid "" -"To delete a container, click the :guilabel:`More` button and select :" -"guilabel:`Delete Container`." +"Run the \"Sleep for five seconds\" command, and determine whether the server/" +"vm was created by calling ``nova_client.servers.list()``:" msgstr "" -#: ../sdk_neutron_apis.rst:408 -msgid "To delete a network:" +#: ../sdk_compute_apis.rst:141 +msgid "Create server code listing example" msgstr "" -#: ../cli_nova_configure_access_security_for_instances.rst:175 +#: ../sdk_compute_apis.rst:169 +msgid "Delete server (API v2)" +msgstr "" + +#: ../sdk_compute_apis.rst:171 msgid "" -"To delete a security group rule, specify the same arguments that you used to " -"create the rule." +"The following program deletes a server (VM) by using the Compute API v2." msgstr "" -#: ../sdk_configure_access_security_instances.rst:131 +#: ../sdk_compute_apis.rst:191 +msgid "Determine whether the ``vm1`` server exists:" +msgstr "" + +#: ../sdk_compute_apis.rst:193 +msgid "List servers: ``servers_list``." +msgstr "" + +#: ../sdk_compute_apis.rst:195 +msgid "Iterate over ``servers_list`` and compare name with ``vm1``." +msgstr "" + +#: ../sdk_compute_apis.rst:197 msgid "" -"To delete a security group, call the `novaclient.v\\_1.security\\_groups." -"SecurityGroupManager.delete `__ method, passing either a " -"`novaclient.v1\\_1.security\\_groups.SecurityGroup `__ object or group ID " -"as an argument:" +"If true, set the variable name ``server_exists`` to ``True`` and break from " +"the for loop:" msgstr "" -#: ../cli_nova_configure_access_security_for_instances.rst:108 -msgid "To delete a specified group, enter the following command::" -msgstr "" - -#: ../dashboard_manage_containers.rst:65 +#: ../sdk_compute_apis.rst:214 msgid "" -"To delete an object, click the :guilabel:`More button` and select :guilabel:" -"`Delete Object`." +"If the server exists, run the ``delete`` method of the ``nova_client." +"servers`` object:" msgstr "" -#: ../dashboard_manage_containers.rst:91 +#: ../sdk_compute_apis.rst:222 +msgid "Delete server code example" +msgstr "" + +#: ../sdk_compute_apis.rst:251 +msgid "Update server (API v2)" +msgstr "" + +#: ../sdk_compute_apis.rst:253 msgid "" -"To delete an object, click the :guilabel:`More` button and select :guilabel:" -"`Delete Object`." +"The following program updates the name of a server (VM) by using the Compute " +"API v2." msgstr "" -#: ../sdk_schedule_objects_for_deletion.rst:5 +#: ../sdk_compute_apis.rst:264 msgid "" -"To determine whether your Object Storage system supports this feature, see :" -"doc:`managing-openstack-object-storage-with-swift-cli`. Alternatively, check " -"with your service provider." +"``print_server`` is a method defined in ``utils.py`` and prints the server " +"details as shown in the code listing below:" msgstr "" -#: ../cli_swift_set_object_versions.rst:183 +#: ../sdk_compute_apis.rst:280 msgid "" -"To disable object versioning for the ``current`` container, remove its ``X-" -"Versions-Location`` metadata header by sending an empty key value." +"Get OpenStack Credentials. See :ref:`Get OpenStack credentials (API v2) `." msgstr "" -#: ../cli_manage_ip_addresses.rst:134 -msgid "To disassociate a floating IP address from an instance::" -msgstr "" - -#: ../configure_access_and_security_for_instances.rst:210 +#: ../sdk_compute_apis.rst:291 msgid "" -"To disassociate an IP address from an instance, click the :guilabel:" -"`Disassociate` button." +"Get the server instance using ``server_id`` and print the details by calling " +"``print_server`` method:" msgstr "" -# #-#-#-#-# cli_swift_archive_auto_extract.pot (End User Guide 1.0.0) #-#-#-#-# -# #-#-#-#-# cli_swift_bulk_delete.pot (End User Guide 1.0.0) #-#-#-#-# -# #-#-#-#-# cli_swift_large_object_creation.pot (End User Guide 1.0.0) #-#-#-#-# -# #-#-#-#-# cli_swift_static_website.pot (End User Guide 1.0.0) #-#-#-#-# -#: ../cli_swift_archive_auto_extract.rst:7 ../cli_swift_bulk_delete.rst:7 -#: ../cli_swift_large_object_creation.rst:7 ../cli_swift_static_website.rst:7 +#: ../sdk_compute_apis.rst:301 msgid "" -"To discover whether your Object Storage system supports this feature, see :" -"ref:`discoverability`. Alternatively, check with your service provider." +"Call ``server.update`` on the server object with the new value for ``name`` " +"variable:" msgstr "" -#: ../cli_swift_discoverability.rst:15 +#: ../sdk_compute_apis.rst:309 +msgid "Get the updated instance of the server:" +msgstr "" + +#: ../sdk_compute_apis.rst:315 +msgid "Call ``print_server`` again to check the update server details:" +msgstr "" + +#: ../sdk_compute_apis.rst:322 +msgid "Update server code listing example" +msgstr "" + +#: ../sdk_compute_apis.rst:348 +msgid "List flavors (API v2)" +msgstr "" + +#: ../sdk_compute_apis.rst:350 msgid "" -"To discover which features are enabled in your Object Storage system, use " -"the ``/info`` request." +"The following program lists flavors and their details by using the Compute " +"API v2." msgstr "" -#: ../cli_swift_pseudo_hierarchical_folders_directories.rst:24 +#: ../sdk_compute_apis.rst:361 msgid "" -"To display a list of all the objects in the storage container, use ``GET`` " -"without a ``delimiter`` or ``prefix``." +"The ``print_flavors`` method is defined in ``utils.py`` and prints the " +"flavor details:" msgstr "" -#: ../cli_create_and_manage_stacks.rst:55 -msgid "To do so, run the following command::" -msgstr "" - -#: ../dashboard_launch_instances.rst:208 -msgid "To download a summary, click :guilabel:`Download CSV Summary`." -msgstr "" - -#: ../cli_swift_manage_objects.rst:42 -msgid "To download an object from a container, run the following command:" -msgstr "" - -#: ../cli_swift_set_object_versions.rst:18 -msgid "To enable and use object versioning" -msgstr "" - -#: ../cli_swift_set_object_versions.rst:20 +#: ../sdk_compute_apis.rst:374 msgid "" -"To enable object versioning, ask your cloud provider to set the " -"``allow_versions`` option to ``TRUE`` in the container configuration file." +"Get OpenStack credentials. :ref:`Get OpenStack credentials (API v2) `." msgstr "" -#: ../cli_config_drive.rst:78 +#: ../sdk_compute_apis.rst:384 +msgid "List flavors by calling ``list()`` on ``nova_client.flavors`` object:" +msgstr "" + +#: ../sdk_compute_apis.rst:390 +msgid "Print the flavor details, id and name by calling ``print_flavors``:" +msgstr "" + +#: ../sdk_compute_apis.rst:397 +msgid "List flavors code listing example" +msgstr "" + +#: ../sdk_compute_apis.rst:415 +msgid "List floating IPs (API v2)" +msgstr "" + +#: ../sdk_compute_apis.rst:417 msgid "" -"To enable the configuration drive, pass the ``--config-drive true`` " -"parameter to the :command:`nova boot` command." +"The following program lists the floating IPs and their details by using the " +"Compute API v2." msgstr "" -#: ../cli_nova_configure_access_security_for_instances.rst:90 +#: ../sdk_compute_apis.rst:428 msgid "" -"To ensure that the key pair has been successfully imported, list key pairs " -"as follows::" +"The ``print_values_ip`` method is defined in ``utils.py`` and prints the " +"floating\\_ip object details:" msgstr "" -#: ../cli_swift_large_object_creation.rst:167 +#: ../sdk_compute_apis.rst:454 msgid "" -"To ensure the download works correctly, you must upload all the object " -"segments to the same container and ensure that each object name is prefixed " -"in such a way that it sorts in the order in which it should be concatenated. " -"You also create and upload a manifest file. The manifest file is a zero-byte " -"file with the extra ``X-Object-Manifest`` ``CONTAINER/PREFIX`` header, where " -"``CONTAINER`` is the container the object segments are in and ``PREFIX`` is " -"the common prefix for all the segments. You must UTF-8-encode and then URL-" -"encode the container and common prefix in the ``X-Object-Manifest`` header." +"List floating IPs by calling ``list()`` on ``nova_client.floating_ips`` " +"object:" msgstr "" -#: ../cli_create_and_manage_stacks.rst:64 +#: ../sdk_compute_apis.rst:461 +msgid "Print the floating IP object details by calling ``print_values_ip``:" +msgstr "" + +#: ../sdk_compute_apis.rst:468 +msgid "List floating IPs code listing example" +msgstr "" + +#: ../sdk_compute_apis.rst:485 +msgid "List hosts (API v2)" +msgstr "" + +#: ../sdk_compute_apis.rst:487 +msgid "The following program lists the hosts by using the Compute API v2." +msgstr "" + +#: ../sdk_compute_apis.rst:497 msgid "" -"To explore the state and history of a particular stack, you can run a number " -"of commands." +"The ``print_hosts`` method is defined in ``utils.py`` and prints the host " +"object details:" msgstr "" -#: ../cli_nova_configure_access_security_for_instances.rst:65 -msgid "To generate a key pair, run the following command::" +#: ../sdk_compute_apis.rst:521 +msgid "List hosts by calling ``list()`` on ``nova_client.hosts`` object:" +msgstr "" + +#: ../sdk_compute_apis.rst:527 +msgid "Print the host object details by calling ``print_hosts(host_list)``:" +msgstr "" + +#: ../sdk_compute_apis.rst:534 +msgid "List hosts code listing example" +msgstr "" + +#: ../sdk_configure_access_security_instances.rst:8 +msgid "" +"When working with images in the SDK, you will call ``novaclient`` methods." +msgstr "" + +#: ../sdk_configure_access_security_instances.rst:14 +msgid "Add a keypair" msgstr "" #: ../sdk_configure_access_security_instances.rst:16 @@ -7172,62 +8104,33 @@ msgid "" "create>`__ method:" msgstr "" -#: ../cli_swift_manage_access_swift.rst:11 +#: ../sdk_configure_access_security_instances.rst:30 +msgid "The Python script output looks something like this:" +msgstr "" + +#: ../sdk_configure_access_security_instances.rst:42 msgid "" -"To give a user read access, use the ``swift post`` command with the ``-r`` " -"parameter. To give a user write access, use the ``-w`` parameter." +"You typically write the private key to a file to use it later. The file must " +"be readable and writeable by only the file owner; otherwise, the SSH client " +"will refuse to read the private key file. The safest way is to create the " +"file with the appropriate permissions, as shown in the following example:" msgstr "" -#: ../backup_db_incremental.rst:98 +#: ../sdk_configure_access_security_instances.rst:67 +msgid "Import a keypair" +msgstr "" + +#: ../sdk_configure_access_security_instances.rst:69 msgid "" -"To incorporate your incremental backups, you simply use the ``--backup`` " -"parameter to pass in the ``BACKUP_ID`` of your most recent incremental " -"backup. The Database service handles the complexities of applying the chain " -"of all previous incremental backups." +"If you have already generated a keypair with the public key located at ``~/." +"ssh/id_rsa.pub``, pass the contents of the file to the `novaclient.v1\\_1." +"keypairs.KeypairManager.create `__ method to import the public key to Compute:" msgstr "" -#: ../cli_swift_bulk_delete.rst:38 -msgid "" -"To indicate a container, specify the container name as: ``CONTAINER_NAME``. " -"Make sure that the container is empty. If it contains objects, Object " -"Storage cannot delete the container." -msgstr "" - -#: ../cli_swift_bulk_delete.rst:35 -msgid "" -"To indicate an object, specify the container and object name as: " -"``CONTAINER_NAME``/``OBJECT_NAME``." -msgstr "" - -#: ../cli_stop_and_start_an_instance.rst:24 -msgid "" -"To initiate a hypervisor-level suspend operation, run the following command::" -msgstr "" - -#: ../dashboard_launch_instances.rst:224 -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:82 -msgid "" -"To launch multiple instances, enter a value greater than ``1``. The default " -"is ``1``." -msgstr "" - -#: ../cli_swift_create_containers.rst:12 -msgid "To list all containers, run the following command:" -msgstr "" - -#: ../cli_manage_ip_addresses.rst:46 -msgid "" -"To list all floating IP addresses that are allocated to the current project, " -"run::" -msgstr "" - -#: ../cli_manage_ip_addresses.rst:32 -msgid "To list all pools that provide floating IP addresses, run::" +#: ../sdk_configure_access_security_instances.rst:89 +msgid "List keypairs" msgstr "" #: ../sdk_configure_access_security_instances.rst:91 @@ -7245,97 +8148,85 @@ msgid "" "html#novaclient.v1_1.security_groups. SecurityGroupManager.list>`__ method:" msgstr "" +#: ../sdk_configure_access_security_instances.rst:119 +msgid "" +"To create a security group with a specified name and description, call the " +"`novaclient.v\\_1.security\\_groups.SecurityGroupManager.create `__ method:" +msgstr "" + +#: ../sdk_configure_access_security_instances.rst:131 +msgid "" +"To delete a security group, call the `novaclient.v\\_1.security\\_groups." +"SecurityGroupManager.delete `__ method, passing either a " +"`novaclient.v1\\_1.security\\_groups.SecurityGroup `__ object or group ID " +"as an argument:" +msgstr "" + +#: ../sdk_configure_access_security_instances.rst:157 +msgid "" +"Access the security group rules from the ``rules`` attribute of a " +"`novaclient.v1\\_1.security\\_groups.SecurityGroup `__ object:" +msgstr "" + +#: ../sdk_configure_access_security_instances.rst:169 +msgid "" +"To add a rule to a security group, call the `novaclient.v1\\_1.security" +"\\_group\\_rules.SecurityGroupRuleManager.create `__ method:" +msgstr "" + +#: ../sdk_install.rst:2 +msgid "Installing OpenStack SDK" +msgstr "" + +#: ../sdk_install.rst:4 +msgid "" +"Each OpenStack project has its own Python library. These libraries are " +"bundled with the command-line clients. For example, the Python bindings for " +"the Compute API are bundled with the python-novaclient package." +msgstr "" + +#: ../sdk_install.rst:8 +msgid "" +"For details about how to install the clients, see :doc:`../common/" +"cli_install_openstack_command_line_clients`." +msgstr "" + +#: ../sdk_manage_images.rst:6 +msgid "Manage images" +msgstr "" + +#: ../sdk_manage_images.rst:8 +msgid "" +"When working with images in the SDK, you will call both ``glance`` and " +"``nova`` methods." +msgstr "" + #: ../sdk_manage_images.rst:16 msgid "" "To list the available images, call the ``glanceclient.v2.images.Controller." "list`` method:" msgstr "" -#: ../cli_swift_manage_objects.rst:36 -msgid "To list the objects in a container, run the following command:" -msgstr "" - -#: ../cli_nova_configure_access_security_for_instances.rst:125 -msgid "To list the rules for a security group, run the following command::" -msgstr "" - -#: ../cli_nova_configure_access_security_for_instances.rst:98 +#: ../sdk_manage_images.rst:25 msgid "" -"To list the security groups for the current project, including descriptions, " -"enter the following command::" +"The images method returns a Python generator, as shown in the following " +"interaction with the Python interpreter:" msgstr "" -#: ../configure_access_and_security_for_instances.rst:152 -msgid "To make the key pair known to SSH, run the **ssh-add** command." -msgstr "" - -#: ../cli_ceilometer.rst:9 -msgid "To model data, Telemetry uses the following abstractions:" -msgstr "" - -#: ../cli_swift_env_vars.rst:19 -msgid "To obtain these values, run the ``swift stat -v`` command." -msgstr "" - -#: ../cli_swift_large_lists.rst:33 -msgid "To page through a large list of containers" -msgstr "" - -#: ../cli_stop_and_start_an_instance.rst:10 -msgid "To pause an instance, run the following command::" -msgstr "" - -#: ../cli_swift_bulk_delete.rst:16 -msgid "" -"To perform a bulk delete operation, add the ``bulk-delete`` query parameter " -"to the path of a ``POST`` or ``DELETE`` operation." -msgstr "" - -#: ../cli_reboot_an_instance.rst:15 -msgid "To perform a hard reboot, pass the ``--hard`` parameter, as follows::" -msgstr "" - -#: ../cli_reboot_an_instance.rst:34 -msgid "" -"To perform an instance reboot into rescue mode, run the following command::" -msgstr "" - -#: ../dashboard_launch_instances.rst:205 -msgid "" -"To query the instance usage for a month, select a month and click :guilabel:" -"`Submit`." -msgstr "" - -#: ../configure_access_and_security_for_instances.rst:213 -msgid "" -"To release the floating IP address back into the pool of addresses, click " -"the :guilabel:`More` button and select the :guilabel:`Release Floating IP` " -"option." -msgstr "" - -#: ../cli_manage_ip_addresses.rst:138 -msgid "To remove the floating IP address from a project::" -msgstr "" - -#: ../cli_change_the_size_of_your_server.rst:57 -msgid "" -"To resize the server, use the ``nova resize`` command and add the server ID " -"or name and the new flavor. Include the ``--poll`` parameter to display the " -"resize progress. For example::" -msgstr "" - -#: ../cli_reboot_an_instance.rst:59 -msgid "" -"To restart the instance from the normal boot disk, run the following " -"command::" -msgstr "" - -#: ../dashboard_databases.rst:140 -msgid "To restore a database instance" -msgstr "" - -#: ../cli_stop_and_start_an_instance.rst:29 -msgid "To resume a suspended instance, run the following command::" +#: ../sdk_manage_images.rst:88 +msgid "Get image by ID" msgstr "" #: ../sdk_manage_images.rst:90 @@ -7344,88 +8235,16 @@ msgid "" "Controller.get`` method:" msgstr "" -#: ../cli_swift_large_lists.rst:20 +#: ../sdk_manage_images.rst:103 +msgid "Get image by name" +msgstr "" + +#: ../sdk_manage_images.rst:105 msgid "" -"To return fewer than 10,000 names, use the ``limit`` parameter. If the " -"number of names returned equals the specified ``limit`` (or 10,000 if you " -"omit the ``limit`` parameter), you can assume there are more names to list. " -"If the number of names in the list is exactly divisible by the ``limit`` " -"value, the last request has no content." -msgstr "" - -#: ../cli_swift_env_vars.rst:7 -msgid "" -"To run the cURL command examples for the Object Storage API requests, set " -"these environment variables:" -msgstr "" - -#: ../cli_swift_serialized_response_formats.rst:11 -msgid "" -"To run the cURL command examples, you must export environment variables. For " -"more information, see the section :ref:`env-vars`." -msgstr "" - -#: ../sdk_schedule_objects_for_deletion.rst:14 -msgid "" -"To schedule an object for deletion, include one of these headers with the " -"``PUT`` or ``POST`` request on the object:" -msgstr "" - -#: ../cli_create_and_manage_stacks.rst:67 -msgid "" -"To see which stacks are visible to the current user, run the following " -"command::" -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 "" - -#: ../cli_nova_configure_access_security_for_instances.rst:73 -msgid "" -"To set the permissions of the :file:`.pem` file so that only you can read " -"and write to it, run the following command::" -msgstr "" - -#: ../sdk_compute_apis.rst:14 -msgid "" -"To set up environmental variables and authenticate against Compute API " -"endpoints, see :ref:`sdk_authenticate`." -msgstr "" - -#: ../cli_create_and_manage_stacks.rst:114 -msgid "To show the details for a particular event, run the following command::" -msgstr "" - -#: ../cli_create_and_manage_stacks.rst:92 -msgid "" -"To show the details for a specific resource in a stack, run the following " -"command::" -msgstr "" - -#: ../cli_create_and_manage_stacks.rst:78 -msgid "To show the details of a stack, run the following command::" -msgstr "" - -#: ../cli_stop_and_start_an_instance.rst:17 -msgid "To unpause an instance, run the following command::" -msgstr "" - -#: ../cli_create_and_manage_stacks.rst:122 -msgid "" -"To update an existing stack from a modified template file, run a command " -"like the following command::" -msgstr "" - -#: ../cli_swift_archive_auto_extract.rst:19 -msgid "" -"To upload an archive file, make a ``PUT`` request. Add the ``extract-" -"archive=format`` query parameter to indicate that you are uploading a tar " -"archive file instead of normal content." +"The Image service Python bindings do not support the retrieval of an image " +"object by name. However, the Compute Python bindings enable you to get an " +"image object by name. To get an image object by name, call the ``novaclient." +"v1_1.images.ImageManager.find`` method:" msgstr "" #: ../sdk_manage_images.rst:122 @@ -7434,63 +8253,8 @@ msgid "" "method:" msgstr "" -#: ../cli_swift_manage_objects.rst:5 -msgid "To upload an object to a container, run the following command:" -msgstr "" - -#: ../cli_swift_manage_objects.rst:11 -msgid "To upload in chunks, for large files, run the following command:" -msgstr "" - -#: ../dashboard_launch_instances.rst:176 -msgid "" -"To use SSH to connect to your instance, you use the downloaded keypair file." -msgstr "" - -#: ../cli_config_drive.rst:39 -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 " -"must set the ``qemu_img_cmd`` value in the ``hyperv`` configuration section " -"to the full path to an :command:`qemu-img` command installation." -msgstr "" - -#: ../cli_config_drive.rst:31 -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_use_snapshots_to_migrate_instances.rst:5 -msgid "" -"To use snapshots to migrate instances from OpenStack projects to clouds, " -"complete these steps." -msgstr "" - -#: ../intro-user.rst:26 -msgid "" -"To use the OpenStack APIs, it helps to be familiar with HTTP/1.1, RESTful " -"web services, the OpenStack services, and JSON or XML data serialization " -"formats." -msgstr "" - -#: ../cli_swift_discoverability.rst:18 -msgid "" -"To use the ``/info`` request, send a ``GET`` request using the ``/info`` " -"path to the Object Store endpoint as shown in this example:" -msgstr "" - -#: ../cli_config_drive.rst:23 -msgid "" -"To use the configuration drive, you must follow the following requirements " -"for the compute host and image." -msgstr "" - -#: ../sdk_compute_apis.rst:8 -msgid "" -"To use the information in this section, you must be familiar with OpenStack " -"Compute." +#: ../sdk_neutron_apis.rst:6 +msgid "Networking" msgstr "" #: ../sdk_neutron_apis.rst:8 @@ -7501,149 +8265,264 @@ msgid "" "implements the Networking API v2.0." msgstr "" -#: ../cli_cheat_sheet.rst:226 +#: ../sdk_neutron_apis.rst:18 +msgid "Make sure that you set the relevant environment variables." +msgstr "" + +#: ../sdk_neutron_apis.rst:20 msgid "" -"To validate that the file was injected, use ssh to connect to the instance, " -"and look in ``/var/lib/cloud`` for the file." +"As an example, see the sample shell file that sets these variables to get " +"credentials:" msgstr "" -#: ../cli_delete_an_instance.rst:27 +#: ../sdk_neutron_apis.rst:34 +msgid "Get credentials" +msgstr "" + +#: ../sdk_neutron_apis.rst:36 +msgid "The examples in this section use the ``get_credentials`` method:" +msgstr "" + +#: ../sdk_neutron_apis.rst:52 +msgid "Use the ``get_credentials()`` method to populate and get a dictionary:" +msgstr "" + +#: ../sdk_neutron_apis.rst:61 +msgid "Get Nova credentials" +msgstr "" + +#: ../sdk_neutron_apis.rst:63 +msgid "The examples in this section use the ``get_nova_credentials`` method:" +msgstr "" + +#: ../sdk_neutron_apis.rst:79 msgid "" -"To verify that the server was deleted, run the :command:`nova list` command::" +"Use the ``get_nova_credentials()`` method to populate and get a dictionary:" msgstr "" -#: ../cli_launch_instances.rst:261 +#: ../sdk_neutron_apis.rst:89 +msgid "Print values" +msgstr "" + +#: ../sdk_neutron_apis.rst:91 msgid "" -"To view the available options for the :command:`nova list` command, run the " -"following command::" +"The examples in this section use the ``print_values`` and " +"``print_values_server`` methods:" msgstr "" -#: ../dashboard_stacks.rst:109 -msgid "Topology" +#: ../sdk_neutron_apis.rst:126 +msgid "This code resides in the ``utils.py`` file, which all samples import." msgstr "" -#: ../dashboard_launch_instances.rst:191 -msgid "Track usage for instances" +#: ../sdk_neutron_apis.rst:133 +msgid "The following program creates a network:" msgstr "" -#: ../cli_swift_static_website.rst:78 +#: ../sdk_neutron_apis.rst:165 +msgid "List networks" +msgstr "" + +#: ../sdk_neutron_apis.rst:167 +msgid "The following program lists networks:" +msgstr "" + +#: ../sdk_neutron_apis.rst:183 ../sdk_neutron_apis.rst:253 +#: ../sdk_neutron_apis.rst:517 +msgid "For ``print_values``, see :ref:`Print values `." +msgstr "" + +#: ../sdk_neutron_apis.rst:190 +msgid "The following program creates a port:" +msgstr "" + +#: ../sdk_neutron_apis.rst:226 msgid "" -"Turn on file listing. If you do not set the index file, the URL displays a " -"list of the objects in the container. Instructions on styling the list with " -"a CSS follow." +"For ``get_nova_credentials``, see :ref:`Get Nova credentials `." msgstr "" -#: ../cli_swift_bulk_delete.rst:33 -msgid "UTF-8-encode and then URL-encode the names." +#: ../sdk_neutron_apis.rst:229 +msgid "For ``get_credentials``, see :ref:`Get credentials `." msgstr "" -#: ../cli_cheat_sheet.rst:344 -msgid "Unmount the volume" +#: ../sdk_neutron_apis.rst:234 +msgid "List ports" msgstr "" -#: ../cli_cheat_sheet.rst:159 -msgid "Unpause" +#: ../sdk_neutron_apis.rst:236 +msgid "The following program lists ports:" msgstr "" -#: ../cli_stop_and_start_an_instance.rst:71 -msgid "Unshelve an instance - Restores the instance." +#: ../sdk_neutron_apis.rst:251 +msgid "For ``get_credentials`` see :ref:`Get credentials `." msgstr "" -#: ../cli_cheat_sheet.rst:171 -msgid "Unsuspend" +#: ../sdk_neutron_apis.rst:258 +msgid "List server ports" msgstr "" -#: ../dashboard_databases.rst:167 -msgid "Update a database instance" +#: ../sdk_neutron_apis.rst:260 +msgid "The following program lists the ports for a server:" msgstr "" -#: ../cli_create_and_manage_stacks.rst:120 -msgid "Update a stack" +#: ../sdk_neutron_apis.rst:301 +msgid "Create router and add port to subnet" msgstr "" -#: ../dashboard_manage_images.rst:90 -msgid "Update an image" -msgstr "" - -#: ../cli_cheat_sheet.rst:43 -msgid "Update image" -msgstr "" - -#: ../sdk_compute_apis.rst:251 -msgid "Update server (API v2)" -msgstr "" - -#: ../sdk_compute_apis.rst:322 -msgid "Update server code listing example" -msgstr "" - -#: ../cli_cheat_sheet.rst:57 -msgid "Upload RAM image" -msgstr "" - -# #-#-#-#-# dashboard_manage_images.pot (End User Guide 1.0.0) #-#-#-#-# -# #-#-#-#-# sdk_manage_images.pot (End User Guide 1.0.0) #-#-#-#-# -#: ../dashboard_manage_images.rst:23 ../sdk_manage_images.rst:120 -msgid "Upload an image" -msgstr "" - -#: ../dashboard_manage_containers.rst:38 -msgid "Upload an object" -msgstr "" - -#: ../dashboard_manage_images.rst:3 -msgid "Upload and manage images" -msgstr "" - -#: ../cli_cheat_sheet.rst:49 -msgid "Upload kernel image" -msgstr "" - -#: ../cli_swift_large_object_creation.rst:225 -msgid "Upload manifest request: HTTP" -msgstr "" - -#: ../cli_swift_large_object_creation.rst:237 -msgid "Upload manifest response: HTTP" -msgstr "" - -#: ../cli_swift_large_object_creation.rst:207 -msgid "Upload next segment of large object request: HTTP" -msgstr "" - -#: ../cli_swift_large_object_creation.rst:273 -msgid "Upload order" -msgstr "" - -#: ../cli_swift_large_object_creation.rst:185 -msgid "Upload segment of large object request: HTTP" -msgstr "" - -#: ../cli_nova_launch_instance_using_ISO_image.rst:99 -msgid "Upload the volume to glance::" -msgstr "" - -#: ../cli_cheat_sheet.rst:65 -msgid "Upload three-part image" -msgstr "" - -#: ../cli_swift_static_website.rst:32 +#: ../sdk_neutron_apis.rst:303 msgid "" -"Use ``X-Container-Meta-Web-Index`` to determine the index file (or default " -"page served, such as ``index.html``) for your website. When someone " -"initially enters your site, the ``index.html`` file displays automatically. " -"If you create sub-directories for your site by creating pseudo-directories " -"in your container, the index page for each sub-directory is displayed by " -"default. If your pseudo-directory does not have a file with the same name as " -"your index file, visits to the sub-directory return a 404 error." +"This example queries OpenStack Networking to create a router and add a port " +"to a subnet." msgstr "" -#: ../cli_swift_large_lists.rst:45 -msgid "Use a ``limit`` of two:" +#: ../sdk_neutron_apis.rst:318 +msgid "" +"Get Nova Credentials. See :ref:'Get Nova credentials '." msgstr "" -#: ../cli_swift_archive_auto_extract.rst:62 -msgid "Use gzip or bzip2 to compress the archive." +#: ../sdk_neutron_apis.rst:328 +msgid "Create a router and add a port to the subnet:" +msgstr "" + +#: ../sdk_neutron_apis.rst:360 +msgid "Create router: complete code listing example" +msgstr "" + +#: ../sdk_neutron_apis.rst:404 +msgid "Delete a network" +msgstr "" + +#: ../sdk_neutron_apis.rst:406 +msgid "This example queries OpenStack Networking to delete a network." +msgstr "" + +#: ../sdk_neutron_apis.rst:408 +msgid "To delete a network:" +msgstr "" + +#: ../sdk_neutron_apis.rst:417 ../sdk_neutron_apis.rst:499 +msgid "" +"Get credentials. See :ref:`Get Nova credentials `." +msgstr "" + +#: ../sdk_neutron_apis.rst:419 ../sdk_neutron_apis.rst:501 +#: ../sdk_neutron_apis.rst:555 ../sdk_neutron_apis.rst:605 +msgid "" +"Instantiate the ``neutron`` client object by using the ``credentials`` " +"dictionary object:" +msgstr "" + +#: ../sdk_neutron_apis.rst:426 +msgid "Delete the network:" +msgstr "" + +#: ../sdk_neutron_apis.rst:451 +msgid "Delete network: complete code listing example" +msgstr "" + +#: ../sdk_neutron_apis.rst:486 +msgid "List routers" +msgstr "" + +#: ../sdk_neutron_apis.rst:488 +msgid "This example queries OpenStack Networking to list all routers." +msgstr "" + +#: ../sdk_neutron_apis.rst:508 +msgid "List the routers:" +msgstr "" + +#: ../sdk_neutron_apis.rst:520 +msgid "List routers: complete code listing example" +msgstr "" + +#: ../sdk_neutron_apis.rst:541 +msgid "List security groups" +msgstr "" + +#: ../sdk_neutron_apis.rst:543 +msgid "This example queries OpenStack Networking to list security groups." +msgstr "" + +#: ../sdk_neutron_apis.rst:553 +msgid "Get credentials. See :ref:`Get credentials `." +msgstr "" + +#: ../sdk_neutron_apis.rst:562 +msgid "List Security groups" +msgstr "" + +#: ../sdk_neutron_apis.rst:570 +msgid "List security groups: complete code listing example" +msgstr "" + +#: ../sdk_neutron_apis.rst:591 +msgid "List subnets" +msgstr "" + +#: ../sdk_neutron_apis.rst:593 +msgid "This example queries OpenStack Networking to list subnets." +msgstr "" + +#: ../sdk_neutron_apis.rst:603 +msgid "Get credentials. See :ref:'Get credentials '." +msgstr "" + +#: ../sdk_neutron_apis.rst:612 +msgid "List subnets:" +msgstr "" + +#: ../sdk_neutron_apis.rst:620 +msgid "List subnets: complete code listing example" +msgstr "" + +#: ../sdk_schedule_objects_for_deletion.rst:3 +msgid "Schedule objects for deletion" +msgstr "" + +#: ../sdk_schedule_objects_for_deletion.rst:5 +msgid "" +"To determine whether your Object Storage system supports this feature, see :" +"doc:`managing-openstack-object-storage-with-swift-cli`. Alternatively, check " +"with your service provider." +msgstr "" + +#: ../sdk_schedule_objects_for_deletion.rst:9 +msgid "" +"Scheduling an object for deletion is helpful for managing objects that you " +"do not want to permanently store, such as log files, recurring full backups " +"of a dataset, or documents or images that become outdated at a specified " +"time." +msgstr "" + +#: ../sdk_schedule_objects_for_deletion.rst:14 +msgid "" +"To schedule an object for deletion, include one of these headers with the " +"``PUT`` or ``POST`` request on the object:" +msgstr "" + +#: ../sdk_schedule_objects_for_deletion.rst:18 +msgid "" +"A UNIX epoch timestamp, in integer form. For example, ``1348691905`` " +"represents ``Wed, 26 Sept 2012 20:38:25 GMT``. It specifies the time you " +"want the object to expire, no longer be served, and be deleted completely " +"from the object store." +msgstr "" + +#: ../sdk_schedule_objects_for_deletion.rst:22 +msgid "X-Delete-At" +msgstr "" + +#: ../sdk_schedule_objects_for_deletion.rst:25 +msgid "" +"An integer value which specifies the number of seconds from the time of the " +"request to when you want to delete the object. This header is converted to a " +"``X-Delete-At`` header that is set to the sum of the ``X-Delete-After`` " +"value plus the current time, in seconds." +msgstr "" + +#: ../sdk_schedule_objects_for_deletion.rst:29 +msgid "X-Delete-After" msgstr "" #: ../sdk_schedule_objects_for_deletion.rst:32 @@ -7652,599 +8531,201 @@ msgid "" "timestamps and for batch conversions." msgstr "" -#: ../backup_db_incremental.rst:3 -msgid "Use incremental backups" -msgstr "" - -#: ../cli_stop_and_start_an_instance.rst:5 -msgid "Use one of the following methods to stop and start an instance." -msgstr "" - -#: ../cli_use_snapshots_to_migrate_instances.rst:3 -msgid "Use snapshots to migrate instances" -msgstr "" - -#: ../cli_cheat_sheet.rst:246 -msgid "Use ssh to connect to the instance" -msgstr "" - -#: ../cli_manage_bare_metal_nodes.rst:136 -msgid "" -"Use the :command:`nova baremetal-node-list` command to view all bare-metal " -"nodes and interfaces. When a node is in use, its status includes the UUID of " -"the instance that runs on it:" -msgstr "" - -#: ../cli_manage_bare_metal_nodes.rst:152 -msgid "" -"Use the :command:`nova baremetal-node-list` command to view the details for " -"a bare-metal node:" -msgstr "" - -#: ../cli_manage_ip_addresses.rst:27 -msgid "" -"Use the :command:`nova floating-ip-*` commands to manage floating IP " -"addresses." -msgstr "" - -#: ../cli_use_snapshots_to_migrate_instances.rst:52 -msgid "Use the :command:`nova image-create` command to take a snapshot::" -msgstr "" - -#: ../cli_use_snapshots_to_migrate_instances.rst:57 -msgid "" -"Use the :command:`nova image-list` command to check the status until the " -"status is ``ACTIVE``::" -msgstr "" - -#: ../cli_use_snapshots_to_migrate_instances.rst:42 -msgid "" -"Use the :command:`nova list` command to confirm that the instance shows a " -"``SHUTOFF`` status::" -msgstr "" - -#: ../dashboard_launch_instances.rst:183 -msgid "" -"Use the :command:`ssh` command to make a secure connection to the instance. " -"For example::" -msgstr "" - #: ../sdk_schedule_objects_for_deletion.rst:35 msgid "" "Use the POST method to assign expiration headers to existing objects that " "you want to expire." msgstr "" -#: ../cli_swift_large_lists.rst:88 +#: ../sdk_schedule_objects_for_deletion.rst:38 msgid "" -"Use the ``end_marker`` parameter to limit the result set to object names " -"that are less than the ``end_marker`` parameter value:" +"In this example, the ``X-Delete-At`` header is assigned a UNIX epoch " +"timestamp in integer form for ``Mon, 11 Jun 2012 15:38:25 GMT``." msgstr "" -#: ../cli_swift_archive_auto_extract.rst:64 +#: ../sdk_schedule_objects_for_deletion.rst:47 msgid "" -"Use the ``extract-archive`` query parameter to specify the format. Valid " -"values for this parameter are ``tar``, ``tar.gz``, or ``tar.bz2``." +"In this example, the ``X-Delete-After`` header is set to 864000 seconds. The " +"object expires after this time." msgstr "" -#: ../sdk_neutron_apis.rst:52 -msgid "Use the ``get_credentials()`` method to populate and get a dictionary:" +#: ../set_up_clustering.rst:3 +msgid "Set up database clustering" msgstr "" -#: ../sdk_neutron_apis.rst:79 +#: ../set_up_clustering.rst:5 msgid "" -"Use the ``get_nova_credentials()`` method to populate and get a dictionary:" +"You can store data across multiple machines by setting up MongoDB sharded " +"clusters." msgstr "" -#: ../sdk_compute_apis.rst:39 +#: ../set_up_clustering.rst:8 +msgid "Each cluster includes:" +msgstr "" + +#: ../set_up_clustering.rst:10 msgid "" -"Use the ``get_nova_credentials_v2()`` method to populate and get a " -"dictionary:" +"One or more *shards*. Each shard consists of a three member replica set " +"(three instances organized as a replica set)." msgstr "" -#: ../cli_config_drive.rst:35 +#: ../set_up_clustering.rst:13 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." +"One or more *query routers*. A query router is the machine that your " +"application actually connects to. This machine is responsible for " +"communicating with the config server to figure out where the requested data " +"is stored. It then accesses and returns the data from the appropriate " +"shard(s)." msgstr "" -#: ../cli_swift_pseudo_hierarchical_folders_directories.rst:66 +#: ../set_up_clustering.rst:19 msgid "" -"Use the ``prefix`` and ``delimiter`` parameters to view the objects inside a " -"pseudo-directory, including further nested pseudo-directories." +"One or more *config servers*. Config servers store the metadata that links " +"requested data with the shard that contains it." msgstr "" -#: ../cli_swift_archive_auto_extract.rst:11 -msgid "Use the auto-extract archive feature to upload a tar archive file." +#: ../set_up_clustering.rst:22 +msgid "This example shows you how to set up a MongoDB sharded cluster." msgstr "" -#: ../cli_swift_pseudo_hierarchical_folders_directories.rst:46 +#: ../set_up_clustering.rst:24 +msgid "**Before you begin. **\\ Make sure that:" +msgstr "" + +#: ../set_up_clustering.rst:26 msgid "" -"Use the delimiter parameter to limit the displayed results. To use " -"``delimiter`` with pseudo-directories, you must use the parameter slash (``/" -"``)." +"The administrative user has registered a MongoDB datastore type and version." msgstr "" -#: ../cli_nova_launch_instance_from_volume.rst:265 +#: ../set_up_clustering.rst:29 msgid "" -"Use the nova ``boot`` ``--swap`` parameter to attach a swap disk on boot or " -"the nova ``boot`` ``--ephemeral`` parameter to attach an ephemeral disk on " -"boot. When you terminate the instance, both disks are deleted." +"The administrative user has created an appropriate :ref:`flavor that meets " +"the MongoDB minimum requirements `." msgstr "" -#: ../backup_db_incremental.rst:32 -msgid "Use the trove ``backup-create`` command and specify:" +#: ../set_up_clustering.rst:33 +msgid "Set up clustering" msgstr "" -#: ../backup_db.rst:179 +#: ../set_up_clustering.rst:35 +msgid "**Create a cluster**" +msgstr "" + +#: ../set_up_clustering.rst:37 msgid "" -"Use the trove ``database-list`` command to check that the original databases " -"(``db1`` and ``db2``) are present on the restored instance." +"Create a cluster by using the trove ``cluster-create`` command. This command " +"creates a one-shard cluster. Pass in:" msgstr "" -#: ../backup_db.rst:153 +#: ../set_up_clustering.rst:40 +msgid "The name of the cluster." +msgstr "" + +#: ../set_up_clustering.rst:42 +msgid "The name and version of the datastore you want to use." +msgstr "" + +#: ../set_up_clustering.rst:44 msgid "" -"Use the trove ``show`` command to display information about the new guest2 " -"instance. Pass in guest2's ``INSTANCE_ID``, which is ``ac7a2b35-a9b4-4ff6-" -"beac-a1bcee86d04b``." +"The three instances you want to include in the replication set for the first " +"shard. Specify each instance by using the ``--instance`` argument and the " +"associated flavor ID and volume size. Use the same flavor ID and volume size " +"for each instance. In this example, flavor ``7`` is a custom flavor that " +"meets the MongoDB minimum requirements." msgstr "" -#: ../backup_db.rst:194 +#: ../set_up_clustering.rst:69 +msgid "**Display cluster information**" +msgstr "" + +#: ../set_up_clustering.rst:71 msgid "" -"Use the trove ``user-list`` command to check that the original user " -"(``user1``) is present on the restored instance." +"Display information about a cluster by using the trove ``cluster-show`` " +"command. Pass in the ID of the cluster." msgstr "" -#: ../manage_db_config.rst:214 +#: ../set_up_clustering.rst:74 msgid "" -"Used in this way, configuration groups let you modify your database cloud " -"configuration, on the fly, on a massive scale." +"The cluster ID displays when you first create a cluster. (If you need to " +"find it later on, use the trove ``cluster-list`` command to list the names " +"and IDs of all the clusters in your system.)" msgstr "" -#: ../cli_cheat_sheet.rst:282 -msgid "Used to manage volumes and volume snapshots that attach to instances." -msgstr "" - -#: ../cli_config_drive.rst:245 -msgid "User data" -msgstr "" - -#: ../cli_swift_manage_access_swift.rst:5 +#: ../set_up_clustering.rst:96 msgid "" -"Users have roles on accounts. For example, a user with the admin role has " -"full access to all containers and objects in an account. You can set access " -"control lists (ACLs) at the container level and support lists for read and " -"write access, which you set with the ``X-Container-Read`` and ``X-Container-" -"Write`` headers." +"**Your application connects to this IP address. **\\ The trove ``cluster-" +"show`` command displays the IP address of the query router. This is the IP " +"address your application uses to retrieve data from the database." msgstr "" -#: ../backup_db.rst:26 -msgid "Users: The ``user1`` user with the ``password`` password" +#: ../set_up_clustering.rst:101 +msgid "**List cluster instances**" msgstr "" -#: ../dashboard_launch_instances.rst:107 +#: ../set_up_clustering.rst:103 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 :" -"guilabel:`Device Name` for your volume. Click the :guilabel:`Delete on " -"Terminate` option to delete the volume on terminating the instance." +"List the instances in a cluster by using the trove ``cluster-instances`` " +"command." msgstr "" -#: ../create_db.rst:46 -msgid "VCPUs" -msgstr "" - -#: ../cli_access_instance_through_a_console.rst:5 +#: ../set_up_clustering.rst:117 msgid "" -"VNC or SPICE is used to view the console output of an instance, regardless " -"of whether or not the console log has output. This allows relaying keyboard " -"and mouse activity to and from an instance." +"**Naming conventions for replication sets and instances. **\\ Note that the " +"``Name`` column displays an instance name that includes the replication set " +"name. The replication set names and instance names are automatically " +"generated, following these rules:" msgstr "" -#: ../cli_access_instance_through_a_console.rst:42 +#: ../set_up_clustering.rst:122 msgid "" -"VNC\\_TYPE can be replaced by any of the above values as connection types." +"**Replication set name. **\\ This name consists of the cluster name, " +"followed by the string -rs\\ *n*, where *n* is 1 for the first replication " +"set you create, 2 for the second replication set, and so on. In this " +"example, the cluster name is ``cluster1``, and there is only one replication " +"set, so the replication set name is ``cluster1-rs1``." msgstr "" -#: ../cli_swift_archive_auto_extract.rst:23 +#: ../set_up_clustering.rst:129 msgid "" -"Valid values for the ``format`` variable are ``tar``, ``tar.gz``, or ``tar." -"bz2``." +"**Instance name. **\\ This name consists of the replication set name " +"followed by the string -*n*, where *n* is 1 for the first instance in a " +"replication set, 2 for the second instance, and so on. In this example, the " +"instance names are ``cluster1-rs1-1``, ``cluster1-rs1-2``, and ``cluster1-" +"rs1-3``." msgstr "" -#: ../cli_cheat_sheet.rst:130 -msgid "View console log of instance" +#: ../set_up_clustering.rst:135 +msgid "**List clusters**" msgstr "" -#: ../cli_ceilometer.rst:119 -msgid "View statistics::" -msgstr "" - -#: ../create_db.rst:77 -msgid "Virtual CPUs: ``1``" -msgstr "" - -#: ../dashboard_manage_volumes.rst:51 +#: ../set_up_clustering.rst:137 msgid "" -"Volume: If you choose this option, a new field for :guilabel:`Use volume as " -"a source` displays. You can select the volume from the list. Options to use " -"a snapshot or a volume as the source for a volume are displayed only if " -"there are existing snapshots or volumes." +"List all the clusters in your system, using the trove ``cluster-list`` " +"command." msgstr "" -#: ../dashboard_manage_volumes.rst:5 +#: ../set_up_clustering.rst:150 +msgid "**Delete a cluster**" +msgstr "" + +#: ../set_up_clustering.rst:152 +msgid "Delete a cluster, using the trove ``cluster-delete`` command." +msgstr "" + +#: ../set_up_clustering.rst:159 +msgid "Query routers and config servers" +msgstr "" + +#: ../set_up_clustering.rst:161 msgid "" -"Volumes are block storage devices that you attach to instances to enable " -"persistent storage. You can attach a volume to a running instance or detach " -"a volume and attach it to another instance at any time. You can also create " -"a snapshot from or delete a volume. Only administrative users can create " -"volume types." +"Each cluster includes at least one query router and one config server. Query " +"routers and config servers count against your quota. When you delete a " +"cluster, the system deletes the associated query router(s) and config " +"server(s)." msgstr "" -#: ../cli_swift_set_object_versions.rst:14 -msgid "" -"We strongly recommend that you put non-current objects in a different " -"container than the container where current object versions reside." -msgstr "" - -#: ../cli_nova_launch_instance_from_volume.rst:200 -msgid "" -"What to do with the volume when the instance is deleted. ``preserve`` does " -"not delete the volume. ``remove`` deletes the volume." -msgstr "" - -#: ../cli_swift_bulk_delete.rst:47 -msgid "" -"When Object Storage processes the request, it performs multiple sub-" -"operations. Even if all sub-operations fail, the operation returns a 200 " -"status. The bulk operation returns a response body that contains details " -"that indicate which sub-operations have succeeded and failed. Some sub-" -"operations might succeed while others fail. Examine the response body to " -"determine the results of each delete sub-operation." -msgstr "" - -#: ../cli_swift_archive_auto_extract.rst:71 -msgid "" -"When Object Storage processes the request, it performs multiple sub-" -"operations. Even if all sub-operations fail, the operation returns a 201 " -"``Created`` status. Some sub-operations might succeed while others fail. " -"Examine the response body to determine the results of each auto-extract " -"archive sub-operation." -msgstr "" - -#: ../configure_access_and_security_for_instances.rst:44 -msgid "" -"When adding a rule, you must specify the protocol used with the destination " -"port or source port." -msgstr "" - -#: ../configure_access_and_security_for_instances.rst:165 -msgid "" -"When an instance is created in OpenStack, it is automatically assigned a " -"fixed IP address in the network to which the instance is assigned. This IP " -"address is permanently associated with the instance until the instance is " -"terminated." -msgstr "" - -#: ../configure_access_and_security_for_instances.rst:23 -msgid "" -"When an instance is created in OpenStack, it is automatically assigned a " -"fixed IP address in the network to which the instance is assigned. This IP " -"address is permanently associated with the instance until the instance is " -"terminated. However, in addition to the fixed IP address, a floating IP " -"address can also be attached to an instance. Unlike fixed IP addresses, " -"floating IP addresses are able to have their associations modified at any " -"time, regardless of the state of the instances involved." -msgstr "" - -#: ../cli_create_and_manage_networks.rst:196 -msgid "" -"When creating a port, you can specify any unallocated IP in the subnet even " -"if the address is not in a pre-defined pool of allocated IP addresses (set " -"by your cloud provider)." -msgstr "" - -#: ../cli_swift_large_object_creation.rst:126 -msgid "" -"When the ``PUT`` operation sees the ``?multipart-manifest=put`` query " -"parameter, it reads the request body and verifies that each segment object " -"exists and that the sizes and ETags match. If there is a mismatch, the " -"``PUT`` operation fails." -msgstr "" - -#: ../cli_change_the_size_of_your_server.rst:94 -msgid "When the resize completes, the status becomes VERIFY\\_RESIZE." -msgstr "" - -#: ../cli_access_instance_through_a_console.rst:45 -msgid "" -"When using SPICE to view the console of an instance, a browser plugin can be " -"used directly on the instance page, or the ``get-vnc-console`` command can " -"be used with it, as well, by returning a token-authenticated address, as in " -"the example above." -msgstr "" - -#: ../sdk_authenticate.rst:7 -msgid "" -"When using the SDK, you must authenticate against an OpenStack endpoint " -"before you can use OpenStack services. Each project uses a slightly " -"different syntax for authentication." -msgstr "" - -#: ../sdk_configure_access_security_instances.rst:8 -msgid "" -"When working with images in the SDK, you will call ``novaclient`` methods." -msgstr "" - -#: ../sdk_manage_images.rst:8 -msgid "" -"When working with images in the SDK, you will call both ``glance`` and " -"``nova`` methods." -msgstr "" - -#: ../cli_manage_bare_metal_nodes.rst:48 -msgid "" -"When you create a bare-metal node, your PM address, user name, and password " -"should match the information in your hardware's BIOS/IPMI configuration." -msgstr "" - -#: ../create_db.rst:17 -msgid "" -"When you create a database instance, you must specify a nova flavor. The " -"flavor indicates various characteristics of the instance, such as RAM, root " -"volume size, and so on. The default nova flavors are not sufficient to " -"create database instances. You might need to create or obtain some new nova " -"flavors that work for databases." -msgstr "" - -#: ../set_up_replication.rst:11 -msgid "" -"When you create a replica, do not specify the ``--users`` or ``--databases`` " -"options." -msgstr "" - -#: ../cli_config_drive.rst:68 -msgid "" -"When you create images that access configuration drive data and multiple " -"directories are under the ``openstack`` directory, always select the highest " -"API version by date that your consumer supports. For example, if your guest " -"image supports the 2012-03-05, 2012-08-05, and 2013-04-13 versions, try " -"2013-04-13 first and fall back to a previous version if 2013-04-13 is not " -"present." -msgstr "" - -#: ../dashboard_stacks.rst:141 -msgid "When you delete a stack, you cannot undo this action." -msgstr "" - -#: ../dashboard_manage_volumes.rst:160 -msgid "" -"When you delete an instance, the data in its attached volumes is not " -"destroyed." -msgstr "" - -#: ../cli_nova_configure_access_security_for_instances.rst:5 -msgid "" -"When you launch a virtual machine, you can inject a *key pair*, which " -"provides SSH access to your instance. For this to work, the image must " -"contain the ``cloud-init`` package." -msgstr "" - -#: ../dashboard_launch_instances.rst:16 -msgid "When you launch an instance from a volume, note the following steps:" -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 "" - -#: ../cli_manage_ip_addresses.rst:10 -msgid "" -"When you launch an instance, it is automatically assigned a private IP " -"address that stays the same until you explicitly terminate the instance. " -"Rebooting an instance has no effect on the private IP address." -msgstr "" - -#: ../cli_delete_an_instance.rst:5 -msgid "When you no longer need an instance, you can delete it." -msgstr "" - -#: ../cli_swift_large_lists.rst:10 -msgid "" -"When you request a list of containers or objects, Object Storage returns a " -"maximum of 10,000 names for each request. To get subsequent names, you must " -"make another request with the ``marker`` parameter. Set the ``marker`` " -"parameter to the name of the last item returned in the previous list. You " -"must URL-encode the ``marker`` value before you send the HTTP request. " -"Object Storage returns a maximum of 10,000 names starting after the last " -"item returned." -msgstr "" - -#: ../cli_swift_set_object_versions.rst:89 -msgid "" -"Where ``length`` is the 3-character, zero-padded hexadecimal character " -"length of the object, ```` is the object name, and " -"```` is the time when the object was initially created as a " -"current version." -msgstr "" - -#: ../cli_swift_large_object_creation.rst:250 -msgid "" -"While static and dynamic objects have similar behavior, this table describes " -"their differences:" -msgstr "" - -#: ../intro-user.rst:31 -msgid "Who should read this book?" -msgstr "" - -#: ../cli_swift_bulk_delete.rst:10 -msgid "" -"With bulk delete, you can delete up to 10,000 objects or containers " -"(configurable) in one request." -msgstr "" - -#: ../dashboard_launch_instances.rst:101 -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. " -"Click the :guilabel:`Delete on Terminate` option to delete the volume on " -"terminating the instance." -msgstr "" - -#: ../sdk_schedule_objects_for_deletion.rst:29 -msgid "X-Delete-After" -msgstr "" - -#: ../sdk_schedule_objects_for_deletion.rst:22 -msgid "X-Delete-At" -msgstr "" - -#: ../cli_swift_serialized_response_formats.rst:30 -#: ../cli_swift_serialized_response_formats.rst:32 -msgid "XML data serialization response format." -msgstr "" - -#: ../cli_swift_static_website.rst:41 -msgid "" -"You also have the option of displaying a list of files in your pseudo-" -"directory instead of a web page. To do this, set the ``X-Container-Meta-Web-" -"Listings`` header to ``TRUE``. You may add styles to your file listing by " -"setting ``X-Container-Meta-Web-Listings-CSS`` to a style sheet (for example, " -"``lists.css``)." -msgstr "" - -# #-#-#-#-# cli_launch_instances.pot (End User Guide 1.0.0) #-#-#-#-# -# #-#-#-#-# cli_nova_configure_access_security_for_instances.pot (End User Guide 1.0.0) #-#-#-#-# -#: ../cli_launch_instances.rst:62 -#: ../cli_nova_configure_access_security_for_instances.rst:56 -msgid "" -"You can also assign a floating IP address to a running instance to make it " -"accessible from outside the cloud. See :doc:`cli_manage_ip_addresses`." -msgstr "" - -#: ../cli_launch_instances.rst:52 -msgid "" -"You can also attach a block storage device, or **volume**, for persistent " -"storage." -msgstr "" - -#: ../sdk_authenticate_against_networking_endpoint.rst:22 -msgid "" -"You can also authenticate by explicitly specifying the endpoint and token:" -msgstr "" - -#: ../cli_config_drive.rst:91 -msgid "" -"You can also configure the Compute service to always create a configuration " -"drive by setting the following option in the :file:`/etc/nova/nova.conf` " -"file::" -msgstr "" - -#: ../cli_launch_instances.rst:108 -msgid "" -"You can also filter the image list by using ``grep`` to find a specific " -"image, as follows::" -msgstr "" - -#: ../cli_launch_instances.rst:231 -msgid "" -"You can also place arbitrary local files into the instance file system at " -"creation time by using the ``--file `` option. You can " -"store up to five files. For example, if you have a special authorized keys " -"file named ``special_authorized_keysfile`` that you want to put on the " -"instance rather than using the regular SSH key injection, you can use the " -"``--file`` option as shown in the following example." -msgstr "" - -#: ../dashboard_manage_images.rst:18 -msgid "" -"You can also use the :command:`glance` and :command:`nova` command-line " -"clients or the Image service and Compute APIs to manage images." -msgstr "" - -#: ../cli_create_and_manage_stacks.rst:46 -msgid "" -"You can also use the :command:`template-validate` command to validate a " -"template file without creating a stack from it." -msgstr "" - -#: ../cli_swift_create_containers.rst:34 -msgid "" -"You can also use the ``swift stat`` command with the ``ACCOUNT`` or " -"``CONTAINER`` names as parameters." -msgstr "" - -#: ../cli_swift_manage_access_swift.rst:22 -msgid "You can also use this command with a list of users." -msgstr "" - -#: ../manage_db_config.rst:211 -msgid "" -"You can apply a configuration group to hundreds or thousands of database " -"instances in your environment." -msgstr "" - -#: ../cli_manage_ip_addresses.rst:66 -msgid "You can assign a floating IP address to a project and to an instance." -msgstr "" - -#: ../cli_nova_launch_instance_from_volume.rst:5 -msgid "You can boot instances from a volume instead of an image." -msgstr "" - -#: ../manage_db_config.rst:152 -msgid "" -"You can change a database's configuration by attaching a configuration group " -"to a database instance. You do this by using the trove ``configuration-" -"attach`` command and passing in the ID of the database instance and the ID " -"of the configuration group." -msgstr "" - -#: ../dashboard_databases.rst:169 -msgid "" -"You can change various characteristics of a database instance, such as its " -"volume size and flavor." -msgstr "" - -#: ../set_up_replication.rst:14 -msgid "" -"You can choose a smaller volume or flavor for a replica than for the " -"original, but the replica's volume must be big enough to hold the data " -"snapshot from the original." -msgstr "" - -#: ../cli_config_drive.rst:4 -msgid "" -"You can configure OpenStack to write metadata to a special configuration " -"drive that attaches to the instance when it boots. The instance can mount " -"this drive and read files from it to get information that is normally " -"available through the `metadata service `__. This metadata " -"is different from the user data." -msgstr "" - -#: ../cli_swift_large_object_creation.rst:203 -msgid "" -"You can continue uploading segments, like this example shows, prior to " -"uploading the manifest." -msgstr "" - -#: ../manage_db_config.rst:91 -msgid "" -"You can create a configuration group by using the trove ``configuration-" -"create`` command. The general syntax for this command is:" -msgstr "" - -#: ../dashboard_manage_containers.rst:122 -msgid "" -"You can create a new object in container without a file available and can " -"upload the file later when it is ready. This temporary object acts a place-" -"holder for a new object, and enables the user to share object metadata and " -"URL info in advance." +#: ../set_up_replication.rst:3 +msgid "Set up database replication" msgstr "" #: ../set_up_replication.rst:5 @@ -8254,576 +8735,82 @@ msgid "" "applies those changes to the replica." msgstr "" -#: ../cli_nova_launch_instance_from_volume.rst:136 +#: ../set_up_replication.rst:9 +msgid "Replicas are read-only." +msgstr "" + +#: ../set_up_replication.rst:11 msgid "" -"You can create a volume from an existing image, volume, or snapshot. This " -"procedure shows you how to create a volume from an image, and use the volume " -"to boot an instance." +"When you create a replica, do not specify the ``--users`` or ``--databases`` " +"options." msgstr "" -#: ../cli_swift_pseudo_hierarchical_folders_directories.rst:84 +#: ../set_up_replication.rst:14 msgid "" -"You can create an unlimited number of nested pseudo-directories. To navigate " -"through them, use a longer ``prefix`` parameter coupled with the " -"``delimiter`` parameter. In this sample output, there is a pseudo-directory " -"called ``dogs`` within the pseudo-directory ``animals``. To navigate " -"directly to the files contained within ``dogs``, enter the following command:" +"You can choose a smaller volume or flavor for a replica than for the " +"original, but the replica's volume must be big enough to hold the data " +"snapshot from the original." msgstr "" -#: ../cli_swift_static_website.rst:100 +#: ../set_up_replication.rst:18 +msgid "This example shows you how to replicate a MySQL database instance." +msgstr "" + +#: ../set_up_replication.rst:21 +msgid "Set up replication" +msgstr "" + +#: ../set_up_replication.rst:23 +msgid "**Get the instance ID**" +msgstr "" + +#: ../set_up_replication.rst:25 +msgid "Get the ID of the original instance you want to replicate:" +msgstr "" + +#: ../set_up_replication.rst:36 +msgid "**Create the replica**" +msgstr "" + +#: ../set_up_replication.rst:38 msgid "" -"You can create and set custom error pages for visitors to your website; " -"currently, only 401 (Unauthorized) and 404 (Not Found) errors are supported. " -"To do this, set the metadata header, ``X-Container-Meta-Web-Error``." +"Create a new instance that will be a replica of the original instance. You " +"do this by passing in the ``--replica_of`` option with the trove ``create`` " +"command. This example creates a replica called ``replica_1``. ``replica_1`` " +"is a replica of the original instance, ``base_1``:" msgstr "" -#: ../cli_nova_configure_access_security_for_instances.rst:9 +#: ../set_up_replication.rst:49 +msgid "**Verify replication status**" +msgstr "" + +#: ../set_up_replication.rst:51 msgid "" -"You can create at least one key pair for each project. You can use the key " -"pair for multiple instances that belong to that project. If you generate a " -"key pair with an external tool, you can import it into OpenStack." +"Pass in ``replica_1``'s instance ID with the trove ``show`` command to " +"verify that the newly created ``replica_1`` instance is a replica of the " +"original ``base_1``. Note that the ``replica_of`` property is set to the ID " +"of ``base_1``." msgstr "" -#: ../dashboard_manage_volumes.rst:153 +#: ../set_up_replication.rst:74 msgid "" -"You can extend a volume by using the :guilabel:`Extend Volume` option " -"available in the :guilabel:`More` dropdown list and entering the new value " -"for volume size." +"Now pass in ``base_1``'s instance ID with the trove ``show`` command to list " +"the replica(s) associated with the original instance. Note that the " +"``replicas`` property is set to the ID of ``replica_1``. If there are " +"multiple replicas, they appear as a comma-separated list." msgstr "" -#: ../cli_nova_configure_access_security_for_instances.rst:63 -msgid "You can generate a key pair or upload an existing public key." +#: ../set_up_replication.rst:99 +msgid "**Detach the replica**" msgstr "" -#: ../backup_db.rst:82 +#: ../set_up_replication.rst:101 msgid "" -"You can get additional information about the backup by using the trove " -"``backup-show`` command and passing in the ``BACKUP_ID``, which is " -"``8af30763-61fd-4aab-8fe8-57d528911138``." -msgstr "" - -#: ../cli_manage_bare_metal_nodes.rst:15 -msgid "" -"You can list and delete bare-metal nodes. When you delete a node, any " -"associated network interfaces are removed. You can list and remove network " -"interfaces that are associated with a bare-metal node." -msgstr "" - -#: ../manage_db_config.rst:5 -msgid "" -"You can manage database configuration tasks by using configuration groups. " -"Configuration groups let you set configuration options, in bulk, on one or " -"more databases." -msgstr "" - -#: ../cli_nova_configure_access_security_for_instances.rst:30 -msgid "" -"You can modify the rules in a security group to allow access to instances " -"through different ports and protocols. For example, you can modify rules to " -"allow access to instances through SSH, to ping instances, or to allow UDP " -"traffic; for example, for a DNS server running on an instance. You specify " -"the following parameters for rules:" -msgstr "" - -#: ../intro-user.rst:18 -msgid "You can modify these examples for your specific use cases." -msgstr "" - -#: ../create_db.rst:171 -msgid "" -"You can now access the new database you just created (myDB) by using typical " -"database access commands. In this MySQL example, replace ``IP_ADDRESS`` with " -"``172.16.200.2``." -msgstr "" - -#: ../create_db.rst:145 -msgid "" -"You can now pass in the instance ID with the trove ``show`` command to get " -"the IP address of the instance. In this example, replace ``INSTANCE_ID`` " -"with ``5599dad6-731e-44df-bb60-488da3da9cfe``." -msgstr "" - -#: ../sdk_assign_cors_headers.rst:19 -msgid "" -"You can only assign these headers to objects. For more information, see `www." -"w3.org/TR/access-control/ `__." -msgstr "" - -#: ../cli_launch_instances.rst:165 -msgid "" -"You can pass user data in a local file at instance launch by using the ``--" -"user-data USER-DATA-FILE`` parameter." -msgstr "" - -#: ../cli_provide_user_data_to_instances.rst:13 -msgid "" -"You can place user data in a local file and pass it through the ``--user-" -"data `` parameter at instance creation::" -msgstr "" - -#: ../dashboard_launch_instances.rst:243 -msgid "" -"You can resize or rebuild an instance. You can also choose to view the " -"instance console log, edit instance or the security groups. Depending on the " -"current state of the instance, you can pause, resume, suspend, soft or hard " -"reboot, or terminate it." -msgstr "" - -#: ../cli_stop_and_start_an_instance.rst:43 -msgid "You can run the following shelving tasks:" -msgstr "" - -#: ../cli_search_instance_with_ip_address.rst:5 -msgid "" -"You can search for an instance using the IP address parameter, ``--ip``, " -"with the :command:`nova list` command." -msgstr "" - -#: ../cli_swift_bulk_delete.rst:54 -msgid "" -"You can set the ``Accept`` request header to one of the following values to " -"define the response format:" -msgstr "" - -#: ../cli_swift_archive_auto_extract.rst:77 -msgid "" -"You can set the ``Accept`` request header to one of these values to define " -"the response format:" -msgstr "" - -#: ../cli_reboot_an_instance.rst:5 -msgid "" -"You can soft or hard reboot a running instance. A soft reboot attempts a " -"graceful shut down and restart of the instance. A hard reboot power cycles " -"the instance." -msgstr "" - -#: ../set_up_clustering.rst:5 -msgid "" -"You can store data across multiple machines by setting up MongoDB sharded " -"clusters." -msgstr "" - -#: ../cli_swift_set_object_versions.rst:5 -msgid "" -"You can store multiple versions of your content so that you can recover from " -"unintended overwrites. Object versioning is an easy way to implement version " -"control, which you can use with any type of content." -msgstr "" - -#: ../dashboard_launch_instances.rst:193 -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 "" - -#: ../cli_swift_large_object_creation.rst:276 -msgid "" -"You can upload manifest and segment objects in any order. You are " -"recommended to upload the manifest object after the segments in case a " -"premature download of the manifest occurs. However, this is not enforced." -msgstr "" - -#: ../cli_swift_large_object_creation.rst:284 -msgid "" -"You can upload new segment objects or remove existing segments. The names " -"must simply match the ``PREFIX`` supplied in ``X-Object-Manifest``." -msgstr "" - -#: ../cli_swift_archive_auto_extract.rst:48 -msgid "" -"You can upload regular files but you cannot upload other items (for example, " -"empty directories or symbolic links)." -msgstr "" - -# #-#-#-#-# backup_db.pot (End User Guide 1.0.0) #-#-#-#-# -# #-#-#-#-# dashboard_databases.pot (End User Guide 1.0.0) #-#-#-#-# -#: ../backup_db.rst:5 ../dashboard_databases.rst:105 -msgid "" -"You can use Database services to backup a database and store the backup " -"artifact in the Object Storage module. Later on, if the original database is " -"damaged, you can use the backup artifact to restore the database. The " -"restore process creates a database instance." -msgstr "" - -#: ../cli_config_drive.rst:120 -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_swift_static_website.rst:11 -msgid "" -"You can use your Object Storage account to create a static website. This " -"static website is created with Static Web middleware and serves container " -"data with a specified index file, error file resolution, and optional file " -"listings. This mode is normally active only for anonymous requests, which " -"provide no authentication token. To use it with authenticated requests, set " -"the header ``X-Web-Mode`` to ``TRUE`` on the request." -msgstr "" - -#: ../cli_launch_instances.rst:139 -msgid "You can view rules for a specified security group::" -msgstr "" - -#: ../dashboard_manage_volumes.rst:90 -msgid "" -"You can view the status of a volume in the Volumes tab of the dashboard. The " -"volume is either Available or In-Use." -msgstr "" - -#: ../cli_swift_large_object_creation.rst:281 -msgid "" -"You cannot add or remove segment objects from the manifest. However, you can " -"create a completely new manifest object of the same name with a different " -"manifest list." -msgstr "" - -#: ../cli_nova_configure_access_security_for_instances.rst:114 -msgid "" -"You cannot delete the default security group for a project. Also, you cannot " -"delete a security group that is assigned to a running instance." -msgstr "" - -#: ../cli_swift_set_object_versions.rst:11 -msgid "" -"You cannot version a large-object manifest file, but the large-object " -"manifest file can point to versioned segments." +"If the original instance goes down, you can detach the replica. The replica " +"becomes a standalone database instance. You can then take the new standalone " +"instance and create a new replica of that instance." msgstr "" #: ../set_up_replication.rst:105 msgid "You detach a replica using the trove ``detach-replica`` command:" msgstr "" - -#: ../dashboard_create_networks.rst:39 -msgid "" -"You do not have to specify a subnet when you create a network, but if you do " -"not specify a subnet, any attached instance receives an Error status." -msgstr "" - -#: ../cli_nova_launch_instance_using_ISO_image.rst:95 -msgid "" -"You get a list with all the volumes in your system. In this list, you can " -"find the volume that is attached to your ISO created instance, with the " -"false bootable property." -msgstr "" - -#: ../dashboard_manage_containers.rst:32 -msgid "You have successfully created a container." -msgstr "" - -#: ../dashboard_create_networks.rst:113 -msgid "" -"You have successfully created the router. You can view the new topology from " -"the :guilabel:`Network Topology` tab." -msgstr "" - -#: ../dashboard_manage_containers.rst:63 -msgid "You have successfully uploaded an object to the container." -msgstr "" - -#: ../cli_swift_archive_auto_extract.rst:51 -msgid "You must UTF-8-encode the member names." -msgstr "" - -#: ../cli_swift_large_object_creation.rst:60 -msgid "" -"You must record the ``ETag`` response header that the ``PUT`` operation " -"returns. Alternatively, you can calculate the MD5 checksum of the segment " -"prior to uploading and include this in the ``ETag`` request header. This " -"ensures that the upload cannot corrupt your data." -msgstr "" - -#: ../cli_swift_large_object_creation.rst:158 -msgid "" -"You must segment objects that are larger than 5 GB before you can upload " -"them. You then upload the segment objects like you would any other object " -"and create a dynamic large manifest object. The manifest object tells Object " -"Storage how to find the segment objects that comprise the large object. The " -"segments remain individually addressable, but retrieving the manifest object " -"streams all the segments concatenated. There is no limit to the number of " -"segments that can be a part of a single large object." -msgstr "" - -#: ../sdk_authenticate.rst:11 -msgid "" -"You must typically authenticate against a specific version of a service. For " -"example, a client might need to authenticate against Identity v2.0." -msgstr "" - -#: ../cli_swift_large_object_creation.rst:274 -msgid "You must upload the segment objects before upload the manifest object." -msgstr "" - -#: ../cli_swift_archive_auto_extract.rst:46 -msgid "You must use the tar utility to create the tar archive file." -msgstr "" - -#: ../cli_nova_launch_instance_using_ISO_image.rst:59 -msgid "" -"You need the Block Storage service, and the parameter ``shutdown=preserve`` " -"is also mandatory, thus the volume will be preserved after the shutdown of " -"the instance." -msgstr "" - -#: ../cli_swift_static_website.rst:113 -msgid "" -"You only have to set the ``X-Container-Meta-Web-Error`` metadata once for " -"your entire static website." -msgstr "" - -#: ../cli_swift_large_lists.rst:85 -msgid "" -"You receive a one-item response, which is fewer than the ``limit`` number of " -"names. This indicates that this is the end of the list." -msgstr "" - -#: ../cli_swift_large_lists.rst:102 -msgid "" -"You receive a result set of all container names before the ``end-marker`` " -"value." -msgstr "" - -#: ../sdk.rst:12 -msgid "You should also be familiar with:" -msgstr "" - -#: ../backup_db.rst:110 -msgid "" -"You specify that the new ``guest2`` instance has the same flavor (``10``) " -"and the same root volume size (``2``) as the original ``guest1`` instance." -msgstr "" - -#: ../sdk_configure_access_security_instances.rst:42 -msgid "" -"You typically write the private key to a file to use it later. The file must " -"be readable and writeable by only the file owner; otherwise, the SSH client " -"will refuse to read the private key file. The safest way is to create the " -"file with the appropriate permissions, as shown in the following example:" -msgstr "" - -#: ../backup_db.rst:114 -msgid "" -"You use the ``--backup`` argument to indicate that this new instance is " -"based on the backup artifact identified by ``BACKUP_ID``. In this example, " -"replace ``BACKUP_ID`` with ``8af30763-61fd-4aab-8fe8-57d528911138``." -msgstr "" - -#: ../cli_swift_discoverability.rst:7 -msgid "" -"Your Object Storage system might not enable all features that this document " -"describes. These features are:" -msgstr "" - -#: ../dashboard_launch_instances.rst:86 -msgid "Your options are:" -msgstr "" - -#: ../cli_swift_static_website.rst:27 -msgid "" -"Your publicly readable containers are checked for two headers, ``X-Container-" -"Meta-Web-Index`` and ``X-Container-Meta-Web-Error``. The ``X-Container-Meta-" -"Web-Error`` header is discussed below, in the section called :ref:" -"`set_error_static_website`." -msgstr "" - -#: ../cli_nova_launch_instance_from_volume.rst:19 -#: ../cli_nova_launch_instance_from_volume.rst:26 -#: ../cli_nova_launch_instance_from_volume.rst:29 -msgid "``--block-device``" -msgstr "" - -#: ../cli_nova_launch_instance_from_volume.rst:182 -msgid "" -"``--block-device`` source=SOURCE,id=ID,dest=DEST,size=SIZE,shutdown=PRESERVE," -"bootindex=INDEX" -msgstr "" - -#: ../cli_nova_launch_instance_from_volume.rst:35 -msgid "``--ephemeral``" -msgstr "" - -#: ../cli_create_and_manage_networks.rst:239 -msgid "" -"``--fixed-ips ip_address=192.168.2.2 ip_address=192.168.2.40`` is one " -"unknown option." -msgstr "" - -#: ../cli_nova_launch_instance_from_volume.rst:180 -msgid "``--flavor`` FLAVOR. The flavor ID or name." -msgstr "" - -#: ../cli_nova_launch_instance_from_volume.rst:22 -#: ../cli_nova_launch_instance_from_volume.rst:32 -msgid "``--swap``" -msgstr "" - -#: ../cli_swift_serialized_response_formats.rst:22 -msgid "``Accept`` request header" -msgstr "" - -#: ../configure_access_and_security_for_instances.rst:84 -msgid "``All ICMP``" -msgstr "" - -#: ../configure_access_and_security_for_instances.rst:66 -msgid "``CIDR``" -msgstr "" - -#: ../configure_access_and_security_for_instances.rst:84 -msgid "``Ingress``" -msgstr "" - -#: ../cli_nova_launch_instance_from_volume.rst:207 -msgid "``NAME``. The name for the server." -msgstr "" - -#: ../configure_access_and_security_for_instances.rst:66 -msgid "``SSH``" -msgstr "" - -#: ../cli_swift_large_object_creation.rst:15 -msgid "" -"``Segment objects`` store the object content. You can divide your content " -"into segments, and upload each segment into its own segment object. Segment " -"objects do not have any special features. You create, update, download, and " -"delete segment objects just as you would normal objects." -msgstr "" - -# #-#-#-#-# cli_swift_archive_auto_extract.pot (End User Guide 1.0.0) #-#-#-#-# -# #-#-#-#-# cli_swift_bulk_delete.pot (End User Guide 1.0.0) #-#-#-#-# -#: ../cli_swift_archive_auto_extract.rst:85 ../cli_swift_bulk_delete.rst:62 -msgid "``application/json``" -msgstr "" - -#: ../cli_swift_archive_auto_extract.rst:88 -msgid "``application/xml``" -msgstr "" - -#: ../cli_swift_bulk_delete.rst:65 -msgid "``application/xml`` or ``text/xml``" -msgstr "" - -#: ../cli_manage_bare_metal_nodes.rst:25 -msgid "``baremetal-interface-add``" -msgstr "" - -#: ../cli_manage_bare_metal_nodes.rst:28 -msgid "``baremetal-interface-list``" -msgstr "" - -#: ../cli_manage_bare_metal_nodes.rst:31 -msgid "``baremetal-interface-remove``" -msgstr "" - -#: ../cli_manage_bare_metal_nodes.rst:34 -msgid "``baremetal-node-create``" -msgstr "" - -#: ../cli_manage_bare_metal_nodes.rst:37 -msgid "``baremetal-node-delete``" -msgstr "" - -#: ../cli_manage_bare_metal_nodes.rst:40 -msgid "``baremetal-node-list``" -msgstr "" - -#: ../cli_manage_bare_metal_nodes.rst:43 -msgid "``baremetal-node-show``" -msgstr "" - -#: ../dashboard_databases.rst:87 -msgid "``database1``, ``database2``, ``database3``" -msgstr "" - -#: ../cli_manage_bare_metal_nodes.rst:130 -msgid "" -"``host`` is optional for the ``--availability_zone`` parameter. You can " -"simply specify ``zone:,node``, still including the comma." -msgstr "" - -#: ../sdk_compute_apis.rst:264 -msgid "" -"``print_server`` is a method defined in ``utils.py`` and prints the server " -"details as shown in the code listing below:" -msgstr "" - -# #-#-#-#-# cli_swift_archive_auto_extract.pot (End User Guide 1.0.0) #-#-#-#-# -# #-#-#-#-# cli_swift_bulk_delete.pot (End User Guide 1.0.0) #-#-#-#-# -#: ../cli_swift_archive_auto_extract.rst:82 ../cli_swift_bulk_delete.rst:59 -msgid "``text/plain``" -msgstr "" - -#: ../cli_swift_archive_auto_extract.rst:91 -msgid "``text/xml``" -msgstr "" - -#: ../cli_swift_serialized_response_formats.rst:27 -msgid "application/jsontext" -msgstr "" - -#: ../cli_swift_serialized_response_formats.rst:29 -msgid "application/xml" -msgstr "" - -#: ../cli_swift_large_lists.rst:30 -msgid "end_marker" -msgstr "" - -#: ../cli_swift_large_object_creation.rst:81 -msgid "etag" -msgstr "" - -#: ../cli_swift_serialized_response_formats.rst:19 -msgid "format= ``format`` query parameter" -msgstr "" - -#: ../cli_swift_large_lists.rst:25 -msgid "limit" -msgstr "" - -#: ../cli_swift_large_lists.rst:17 -msgid "marker" -msgstr "" - -#: ../cli_nova_launch_instance_from_volume.rst:15 -msgid "nova boot parameter" -msgstr "" - -#: ../cli_access_instance_through_a_console.rst:14 -msgid "novnc" -msgstr "" - -#: ../cli_swift_large_object_creation.rst:77 -msgid "path" -msgstr "" - -#: ../cli_swift_env_vars.rst:14 -msgid "publicURL" -msgstr "" - -#: ../cli_swift_large_object_creation.rst:85 -msgid "size_bytes" -msgstr "" - -#: ../cli_access_instance_through_a_console.rst:18 -msgid "spice" -msgstr "" - -#: ../cli_swift_serialized_response_formats.rst:25 -msgid "text/plain" -msgstr "" - -#: ../cli_swift_serialized_response_formats.rst:31 -msgid "text/xml" -msgstr "" - -#: ../cli_swift_env_vars.rst:17 -msgid "token" -msgstr "" - -#: ../cli_access_instance_through_a_console.rst:21 -msgid "xvpvnc" -msgstr ""