openstack
/
openstack-manuals
Code Issues Proposed changes
openstack-manuals/doc/user-guide-admin/source/locale/user-guide-admin.pot

3819 lines
113 KiB
Plaintext
Raw Blame History

This file contains invisible Unicode characters

This file contains invisible Unicode characters that are indistinguishable to humans but may be processed differently by a computer. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2015, OpenStack contributors
# This file is distributed under the same license as the Admin User Guide package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Admin User Guide 1.0.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2015-12-31 06:14+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#: ../analyzing-log-files-with-swift-cli.rst:3
msgid "Analyze log files"
msgstr ""
#: ../analyzing-log-files-with-swift-cli.rst:5
msgid "Use the swift command-line client to analyze log files."
msgstr ""
#: ../analyzing-log-files-with-swift-cli.rst:7
msgid "The swift client is simple to use, scalable, and flexible."
msgstr ""
#: ../analyzing-log-files-with-swift-cli.rst:9
msgid ""
"Use the swift client :option:`-o` or :option:`-output` option to get short "
"answers to questions about logs."
msgstr ""
#: ../analyzing-log-files-with-swift-cli.rst:12
msgid ""
"You can use the :option:`-o` or :option:`--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 ""
#: ../analyzing-log-files-with-swift-cli.rst:18
msgid "Upload and analyze log files"
msgstr ""
#: ../analyzing-log-files-with-swift-cli.rst:20
msgid ""
"This example assumes that ``logtest`` directory contains the following log "
"files."
msgstr ""
#: ../analyzing-log-files-with-swift-cli.rst:31
msgid "Each file uses the following line format."
msgstr ""
#: ../analyzing-log-files-with-swift-cli.rst:39
msgid "Change into the ``logtest`` directory."
msgstr ""
#: ../analyzing-log-files-with-swift-cli.rst:45
msgid "Upload the log files into the ``logtest`` container."
msgstr ""
#: ../analyzing-log-files-with-swift-cli.rst:58
msgid "Get statistics for the account."
msgstr ""
#: ../analyzing-log-files-with-swift-cli.rst:72
msgid "Get statistics for the ``logtest`` container."
msgstr ""
#: ../analyzing-log-files-with-swift-cli.rst:88
msgid "List all objects in the logtest container."
msgstr ""
#: ../analyzing-log-files-with-swift-cli.rst:103
msgid "Download and analyze an object"
msgstr ""
#: ../analyzing-log-files-with-swift-cli.rst:105
msgid ""
"This example uses the :option:`-o` option and a hyphen (``-``) to get "
"information about an object."
msgstr ""
#: ../analyzing-log-files-with-swift-cli.rst:108
msgid ""
"Use the :command:`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:112
msgid ""
"Using the log line format, find the request type in column 9 and the return "
"code in column 12."
msgstr ""
#: ../analyzing-log-files-with-swift-cli.rst:115
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 ""
#: ../analyzing-log-files-with-swift-cli.rst:119
msgid "Download an object."
msgstr ""
#: ../analyzing-log-files-with-swift-cli.rst:160
msgid "Discover how many PUT requests are in each log file."
msgstr ""
#: ../analyzing-log-files-with-swift-cli.rst:162
msgid ""
"Use a bash for loop with awk and swift with the :option:`-o` or :option:`--"
"output` option and a hyphen (``-``) to discover how many PUT requests are in "
"each log file."
msgstr ""
#: ../analyzing-log-files-with-swift-cli.rst:166
msgid ""
"Run the :command:`swift list` command to list objects in the logtest "
"container. Then, for each item in the list, run the :command:`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:187
msgid "List the object names that begin with a specified string."
msgstr ""
#: ../analyzing-log-files-with-swift-cli.rst:189
msgid ""
"Run the :command:`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:192
msgid ""
"For each item in the list, run the :command:`swift download -o -` command."
msgstr ""
#: ../analyzing-log-files-with-swift-cli.rst:194
msgid ""
"Pipe the output to :command:`grep` and :command:`wc`. Use the :command:"
"`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 <http://docs.openstack.org/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 <http://"
"docs.openstack.org/admin-guide-cloud/networking_adv-features.html>`_ . 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:30
msgid "To list all floating IP addresses for all projects, run:"
msgstr ""
#: ../cli_admin_manage_ip_addresses.rst:62
msgid "Bulk create floating IP addresses"
msgstr ""
#: ../cli_admin_manage_ip_addresses.rst:64
msgid "To create a range of floating IP addresses, run:"
msgstr ""
# #-#-#-#-# cli_admin_manage_ip_addresses.pot (Admin User Guide 1.0.0) #-#-#-#-#
# #-#-#-#-# cli_cinder_quotas.pot (Admin User Guide 1.0.0) #-#-#-#-#
# #-#-#-#-# cli_keystone_manage_services.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) #-#-#-#-#
# #-#-#-#-# nova_cli_manage_projects_security.pot (Admin User Guide 1.0.0) #-#-#-#-#
#: ../cli_admin_manage_ip_addresses.rst:70
#: ../cli_admin_manage_ip_addresses.rst:103 ../cli_cinder_quotas.rst:44
#: ../cli_cinder_quotas.rst:103 ../cli_keystone_manage_services.rst:95
#: ../cli_keystone_manage_services.rst:156 ../cli_nova_specify_host.rst:13
#: ../cli_set_compute_quotas.rst:56 ../cli_set_compute_quotas.rst:85
#: ../cli_set_compute_quotas.rst:106 ../cli_set_compute_quotas.rst:144
#: ../cli_set_compute_quotas.rst:200 ../cli_set_compute_quotas.rst:244
#: ../nova_cli_manage_projects_security.rst:69
#: ../nova_cli_manage_projects_security.rst:106
#: ../nova_cli_manage_projects_security.rst:180
#: ../nova_cli_manage_projects_security.rst:204
msgid "For example:"
msgstr ""
#: ../cli_admin_manage_ip_addresses.rst:76
msgid ""
"By default, ``floating-ip-bulk-create`` uses the ``public`` pool and "
"``eth0`` interface values."
msgstr ""
#: ../cli_admin_manage_ip_addresses.rst:81
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:85
msgid ""
"Pick a small range (/29 gives an 8 address range, 6 of which will be usable)."
msgstr ""
#: ../cli_admin_manage_ip_addresses.rst:88
msgid ""
"Use :command:`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 :command:`nmap -sn "
"192.168.1.56/29` to check whether the entire range is currently unused."
msgstr ""
#: ../cli_admin_manage_ip_addresses.rst:95
msgid "Bulk delete floating IP addresses"
msgstr ""
#: ../cli_admin_manage_ip_addresses.rst:97
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 <http://docs.openstack.org/user-guide/dashboard_stacks.html>`_"
msgstr ""
#: ../cli_admin_manage_stacks.rst:24
msgid ""
"**heat** CLI commands, see the `OpenStack Command Line Interface Reference "
"<http://docs.openstack.org/cli-reference/content/heatclient_commands.html>`_"
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:37
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:38
msgid "View Block Storage service quotas for a project."
msgstr ""
#: ../cli_cinder_quotas.rst:58
msgid "Show the current usage of a per-tenant quota:"
msgstr ""
#: ../cli_cinder_quotas.rst:73
msgid "Edit and update Block Storage service quotas"
msgstr ""
#: ../cli_cinder_quotas.rst:75
msgid "Administrative users can edit and update Block Storage service quotas."
msgstr ""
#: ../cli_cinder_quotas.rst:78 ../cli_cinder_quotas.rst:118
msgid "Clear per-tenant quota limits."
msgstr ""
#: ../cli_cinder_quotas.rst:84
msgid ""
"To update a default value for a new project, update the property in the :"
"guilabel:`cinder.quota` section of the ``/etc/cinder/cinder.conf`` file. For "
"more information, see the `Block Storage Configuration Reference <http://"
"docs.openstack.org/liberty/config-reference/content/ch_configuring-openstack-"
"block-storage.html>`_."
msgstr ""
#: ../cli_cinder_quotas.rst:90
msgid ""
"To update Block Storage service quotas, place the tenant ID in a variable."
msgstr ""
# #-#-#-#-# cli_cinder_quotas.pot (Admin User Guide 1.0.0) #-#-#-#-#
# #-#-#-#-# cli_set_compute_quotas.pot (Admin User Guide 1.0.0) #-#-#-#-#
#: ../cli_cinder_quotas.rst:97 ../cli_set_compute_quotas.rst:138
msgid "Update a particular quota value."
msgstr ""
#: ../cli_cinder_quotas.rst:125
msgid "Remove a service"
msgstr ""
#: ../cli_cinder_quotas.rst:127
msgid "Determine the binary and host of the service you want to remove."
msgstr ""
#: ../cli_cinder_quotas.rst:140
msgid "Disable the service."
msgstr ""
#: ../cli_cinder_quotas.rst:146
msgid "Remove the service from the database."
msgstr ""
#: ../cli_cinder_scheduling.rst:3
msgid "Manage Block Storage scheduling"
msgstr ""
#: ../cli_cinder_scheduling.rst:5
msgid ""
"As an administrative user, you have some control over which volume back end "
"your volumes reside on. You can specify affinity or anti-affinity between "
"two volumes. Affinity between volumes means that they are stored on the same "
"back end, whereas anti-affinity means that they are stored on different back "
"ends."
msgstr ""
#: ../cli_cinder_scheduling.rst:11
msgid ""
"For information on how to set up multiple back ends for Cinder, refer to the "
"guide for `Configuring multiple-storage back ends <http://docs.openstack.org/"
"admin-guide-cloud/blockstorage_multi_backend.html>`__."
msgstr ""
#: ../cli_cinder_scheduling.rst:16
msgid "Example Usages"
msgstr ""
#: ../cli_cinder_scheduling.rst:18
msgid "Create new volume on the same back end as Volume_A:"
msgstr ""
#: ../cli_cinder_scheduling.rst:24
msgid "Create new volume on a different back end than Volume_A:"
msgstr ""
#: ../cli_cinder_scheduling.rst:30
msgid "Create new volume on the same back end as Volume_A and Volume_B:"
msgstr ""
#: ../cli_cinder_scheduling.rst:36 ../cli_cinder_scheduling.rst:48
msgid "Or:"
msgstr ""
#: ../cli_cinder_scheduling.rst:42
msgid ""
"Create new volume on a different back end than both Volume_A and Volume_B:"
msgstr ""
#: ../cli_keystone_manage_services.rst:3
msgid "Create and manage services and service users"
msgstr ""
#: ../cli_keystone_manage_services.rst:5
msgid "The Identity service enables you to define services, as follows:"
msgstr ""
#: ../cli_keystone_manage_services.rst:8
msgid ""
"Service catalog template. The Identity service acts as a service catalog of "
"endpoints for other OpenStack services. The ``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:16
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:21
msgid ""
"The ``auth_token`` middleware supports the use of either a shared secret or "
"users for each service."
msgstr ""
#: ../cli_keystone_manage_services.rst:25
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:30
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:37
msgid "Create a service"
msgstr ""
#: ../cli_keystone_manage_services.rst:39
msgid "List the available services:"
msgstr ""
#: ../cli_keystone_manage_services.rst:59
msgid "To create a service, run this command:"
msgstr ""
#: ../cli_keystone_manage_services.rst:66
msgid "``service_name``: the unique name of the new service."
msgstr ""
#: ../cli_keystone_manage_services.rst:67
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:70
msgid "The arguments are:"
msgstr ""
#: ../cli_keystone_manage_services.rst:70
msgid "``service_description``: the description of the service."
msgstr ""
#: ../cli_keystone_manage_services.rst:72
msgid ""
"For example, to create a ``swift`` service of type ``object-store``, run "
"this command:"
msgstr ""
#: ../cli_keystone_manage_services.rst:89
msgid "To get details for a service, run this command:"
msgstr ""
#: ../cli_keystone_manage_services.rst:112
msgid "Create service users"
msgstr ""
#: ../cli_keystone_manage_services.rst:114
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:131
msgid "Create service users for the relevant services for your deployment."
msgstr ""
#: ../cli_keystone_manage_services.rst:134
msgid "Assign the admin role to the user-project pair."
msgstr ""
#: ../cli_keystone_manage_services.rst:148
msgid "Delete a service"
msgstr ""
#: ../cli_keystone_manage_services.rst:150
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:13
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 <http://docs.openstack.org/admin-guide-"
"cloud/compute-flavors.html>`_."
msgstr ""
#: ../cli_manage_flavors.rst:18
msgid "A flavor consists of the following parameters:"
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:21 ../cli_manage_flavors.rst:90
#: ../dashboard_manage_flavors.rst:36
msgid ""
"Unique ID (integer or UUID) for the new flavor. If specifying 'auto', a UUID "
"will be automatically generated."
msgstr ""
#: ../cli_manage_flavors.rst:22
msgid "Flavor ID"
msgstr ""
#: ../cli_manage_flavors.rst:25
msgid "Name"
msgstr ""
#: ../cli_manage_flavors.rst:25
msgid "Name for the new flavor."
msgstr ""
#: ../cli_manage_flavors.rst:28
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:28 ../cli_manage_flavors.rst:54
#: ../dashboard_manage_flavors.rst:12 ../dashboard_set_quotas.rst:68
msgid "VCPUs"
msgstr ""
#: ../cli_manage_flavors.rst:31
msgid "Amount of RAM to use (in megabytes)."
msgstr ""
#: ../cli_manage_flavors.rst:31
msgid "Memory MB"
msgstr ""
#: ../cli_manage_flavors.rst:34
msgid "Amount of disk space (in gigabytes) to use for the root (/) partition."
msgstr ""
#: ../cli_manage_flavors.rst:35
msgid "Root Disk GB"
msgstr ""
#: ../cli_manage_flavors.rst:38
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:45
msgid "Ephemeral Disk GB"
msgstr ""
#: ../cli_manage_flavors.rst:48
msgid ""
"Amount of swap space (in megabytes) to use. If unspecified, the value is 0 "
"by default."
msgstr ""
#: ../cli_manage_flavors.rst:49
msgid "Swap"
msgstr ""
#: ../cli_manage_flavors.rst:51
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:54 ../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:54 ../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:54 ../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:56 ../cli_manage_flavors.rst:57
#: ../dashboard_manage_flavors.rst:14 ../dashboard_manage_flavors.rst:15
msgid "1"
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: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:56 ../dashboard_manage_flavors.rst:14
msgid "m1.tiny"
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:15
msgid "20"
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:15
msgid "2048"
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: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:16
msgid "2"
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:16
msgid "40"
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:16
msgid "4096"
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: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:17
msgid "4"
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:17
msgid "80"
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:17
msgid "8192"
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: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:60 ../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:60 ../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:60 ../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:60 ../dashboard_manage_flavors.rst:18
msgid "m1.xlarge"
msgstr ""
#: ../cli_manage_flavors.rst:63
msgid ""
"You can create and manage flavors with the nova **flavor-*** commands "
"provided by the ``python-novaclient`` package."
msgstr ""
#: ../cli_manage_flavors.rst:68
msgid "Create a flavor"
msgstr ""
#: ../cli_manage_flavors.rst:70
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 ""
#: ../cli_manage_flavors.rst:80
msgid ""
"To create a flavor, specify a name, ID, RAM size, disk size, and the number "
"of VCPUs for the flavor, as follows:"
msgstr ""
#: ../cli_manage_flavors.rst:93
msgid ""
"Here is an example with additional optional parameters filled in that "
"creates a public ``extra tiny`` flavor that automatically gets an ID "
"assigned, with 256 MB memory, no disk space, and one VCPU. The rxtx-factor "
"indicates the slice of bandwidth that the instances with this flavor can use "
"(through the Virtual Interface (vif) creation in the hypervisor):"
msgstr ""
#: ../cli_manage_flavors.rst:106
msgid ""
"If an individual user or group of users needs a custom flavor that you do "
"not want other tenants to have access to, you can change the flavor's access "
"to make it a private flavor. See `Private Flavors in the OpenStack "
"Operations Guide <http://docs.openstack.org/openstack-ops/content/private-"
"flavors.html>`_."
msgstr ""
#: ../cli_manage_flavors.rst:111 ../cli_manage_flavors.rst:137
msgid "For a list of optional parameters, run this command:"
msgstr ""
#: ../cli_manage_flavors.rst:117
msgid ""
"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:125
msgid ""
"In addition, you can set or unset ``extra_spec`` for the existing flavor. "
"The ``extra_spec`` metadata keys can influence the instance directly when it "
"is launched. If a flavor sets the ``extra_spec key/value quota:"
"vif_outbound_peak=65536``, the instance's out bound peak bandwidth I/O "
"should be LTE 512 Mbps. There are several aspects that can work for an "
"instance including ``CPU limits``, ``Disk tuning``, ``Bandwidth I/O``, "
"``Watchdog behavior``, and ``Random-number generator``. For information "
"about supporting metadata keys, see the `OpenStack Cloud Administrator Guide "
"<http://docs.openstack.org/admin-guide-cloud/compute-flavors.html>`__."
msgstr ""
#: ../cli_manage_flavors.rst:144
msgid "Delete a flavor"
msgstr ""
#: ../cli_manage_flavors.rst:145
msgid "Delete a specified flavor, as follows:"
msgstr ""
#: ../cli_manage_services.rst:3
msgid "Manage services"
msgstr ""
#: ../cli_manage_shares.rst:5
msgid "Manage shares"
msgstr ""
#: ../cli_manage_shares.rst:7
msgid ""
"A share is provided by file storage. You can give access to a share to "
"instances. To create and manage shares, you use ``manila`` client commands."
msgstr ""
#: ../cli_manage_shares.rst:11
msgid "Migrate a share"
msgstr ""
#: ../cli_manage_shares.rst:13
msgid ""
"As an administrator, you can migrate a share with its data from one location "
"to another in a manner that is transparent to users and workloads."
msgstr ""
#: ../cli_manage_shares.rst:17
msgid "Possible use cases for data migration include:"
msgstr ""
#: ../cli_manage_shares.rst:19
msgid ""
"Bring down a physical storage device for maintenance without disrupting "
"workloads."
msgstr ""
#: ../cli_manage_shares.rst:22
msgid "Modify the properties of a share."
msgstr ""
#: ../cli_manage_shares.rst:24
msgid "Free up space in a thinly-provisioned back end."
msgstr ""
#: ../cli_manage_shares.rst:26
msgid ""
"Migrate a share with the :command:`manila migrate` command, as shown in the "
"following example:"
msgstr ""
#: ../cli_manage_shares.rst:33
msgid ""
"In this example, :option:`--force-host-copy True` forces the generic host-"
"based migration mechanism and bypasses any driver optimizations. "
"``destinationHost`` is in this format ``host#pool`` which includes "
"destination host and pool."
msgstr ""
#: ../cli_manage_shares.rst:40
msgid "If the user is not an administrator, the migration fails."
msgstr ""
#: ../cli_nova_evacuate.rst:3
msgid "Evacuate instances"
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_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_nova_evacuate.rst:15
msgid ""
"To list hosts and find a different host for the evacuated instance, run:"
msgstr ""
#: ../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 ""
#: ../cli_nova_evacuate.rst:32
msgid ""
"The instance is rebuilt from the original image or volume, but preserves its "
"configuration including its ID, name, uid, IP address, and so on. The "
"command returns a password."
msgstr ""
#: ../cli_nova_evacuate.rst:44
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 <http://docs.openstack.org/admin-guide-cloud/compute-configuring-"
"migrations.html>`_ 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:3
msgid "Migrate single instance to another compute host"
msgstr ""
#: ../cli_nova_migrate.rst:5
msgid ""
"When you want to move an instance from one compute host to another, you can "
"use the :command:`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:11
msgid "To list the VMs you want to migrate, run:"
msgstr ""
#: ../cli_nova_migrate.rst:17
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:24
msgid "Now, use the :command:`nova migrate` command."
msgstr ""
#: ../cli_nova_migrate.rst:30
msgid ""
"To migrate of an instance and watch the status, use this example script:"
msgstr ""
#: ../cli_nova_migrate.rst:69
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:74
msgid ""
"``ERROR (Forbidden): Policy doesn't allow compute_extension:admin_actions:"
"migrate to be performed. (HTTP 403)``"
msgstr ""
#: ../cli_nova_migrate.rst:77
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 "
"virtual hardware of the instance. OpenStack Compute uses libvirt to tune "
"instances to take advantage of NUMA topologies. The libvirt driver boot "
"process looks at the NUMA topology field of both the instance and the host "
"it is being booted on, and uses that information to generate an appropriate "
"configuration."
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 ""
#: ../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_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 ``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 :option:`--"
"availability_zone ZONE:HOST` parameter on the :command:`nova boot` command."
msgstr ""
#: ../cli_nova_specify_host.rst:19
msgid ""
"To specify which roles can launch an instance on a specified host, enable "
"the ``create:forced_host`` option in the ``policy.json`` file. By default, "
"this option is enabled for only the admin role."
msgstr ""
#: ../cli_nova_specify_host.rst:24
msgid ""
"To view the list of valid compute hosts, use the :command:`nova hypervisor-"
"list` command."
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
msgid ""
"Number of fixed IP addresses allowed per tenant. This number must be equal "
"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: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 ""
#: ../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: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_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:49
msgid "To view and update default quota values"
msgstr ""
#: ../cli_set_compute_quotas.rst:50
msgid "List all default quotas for all tenants:"
msgstr ""
#: ../cli_set_compute_quotas.rst:79
msgid "Update a default value for a new tenant."
msgstr ""
#: ../cli_set_compute_quotas.rst:92
msgid "To view quota values for an existing tenant (project)"
msgstr ""
#: ../cli_set_compute_quotas.rst:94
msgid "Place the tenant ID in a usable variable."
msgstr ""
#: ../cli_set_compute_quotas.rst:100
msgid "List the currently set quota values for a tenant."
msgstr ""
#: ../cli_set_compute_quotas.rst:130
msgid "To update quota values for an existing tenant (project)"
msgstr ""
#: ../cli_set_compute_quotas.rst:132
msgid "Obtain the tenant ID."
msgstr ""
#: ../cli_set_compute_quotas.rst:170 ../cli_set_compute_quotas.rst:270
msgid "To view a list of options for the :command:`quota-update` command, run:"
msgstr ""
#: ../cli_set_compute_quotas.rst:177
msgid "View and update Compute quotas for a tenant user"
msgstr ""
#: ../cli_set_compute_quotas.rst:180
msgid "To view quota values for a tenant user"
msgstr ""
#: ../cli_set_compute_quotas.rst:182 ../cli_set_compute_quotas.rst:226
msgid "Place the user ID in a usable variable."
msgstr ""
#: ../cli_set_compute_quotas.rst:188 ../cli_set_compute_quotas.rst:232
msgid "Place the user's tenant ID in a usable variable, as follows:"
msgstr ""
#: ../cli_set_compute_quotas.rst:194
msgid "List the currently set quota values for a tenant user."
msgstr ""
#: ../cli_set_compute_quotas.rst:224
msgid "To update quota values for a tenant user"
msgstr ""
#: ../cli_set_compute_quotas.rst:238
msgid "Update a particular quota value, as follows:"
msgstr ""
#: ../cli_set_compute_quotas.rst:277
msgid "To display the current quota usage for a tenant user"
msgstr ""
#: ../cli_set_compute_quotas.rst:279
msgid ""
"Use :command:`nova absolute-limits` to get a list of the current quota "
"values and the current quota usage:"
msgstr ""
#: ../cli_set_quotas.rst:3
msgid "Manage quotas"
msgstr ""
# #-#-#-#-# cli_set_quotas.pot (Admin User Guide 1.0.0) #-#-#-#-#
# #-#-#-#-# dashboard_set_quotas.pot (Admin User Guide 1.0.0) #-#-#-#-#
#: ../cli_set_quotas.rst:5 ../dashboard_set_quotas.rst:10
msgid ""
"To prevent system capacities from being exhausted without notification, you "
"can set up quotas. Quotas are operational limits. For example, the number of "
"gigabytes allowed for each tenant can be controlled so that cloud resources "
"are optimized. Quotas can be enforced at both the tenant (or project) and "
"the tenant-user level."
msgstr ""
#: ../cli_set_quotas.rst:12
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."
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:22
msgid "To view all tenants (projects), run:"
msgstr ""
#: ../cli_set_quotas.rst:37
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 <http://docs."
"openstack.org/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:11
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 ``policy.json`` file available "
"for each service in the ``/etc/SERVICE/policy.json`` file. For example, the "
"policy defined for OpenStack Identity service is defined in the ``/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:22
#: ../manage_projects_users_and_roles.rst:233
msgid "Create a role"
msgstr ""
#: ../dashboard_admin_manage_roles.rst:24
#: ../dashboard_admin_manage_roles.rst:35
#: ../dashboard_admin_manage_roles.rst:51
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:26
#: ../dashboard_admin_manage_roles.rst:37
#: ../dashboard_admin_manage_roles.rst:53
msgid "On the :guilabel:`Admin` tab, click the :guilabel:`Roles` category."
msgstr ""
#: ../dashboard_admin_manage_roles.rst:27
msgid "Click the :guilabel:`Create Role` button."
msgstr ""
#: ../dashboard_admin_manage_roles.rst:29
msgid "In the :guilabel:`Create Role` window, enter a name for the role."
msgstr ""
#: ../dashboard_admin_manage_roles.rst:30
msgid "Click the :guilabel:`Create Role` button to confirm your changes."
msgstr ""
#: ../dashboard_admin_manage_roles.rst:33
msgid "Edit a role"
msgstr ""
#: ../dashboard_admin_manage_roles.rst:38
msgid "Click the :guilabel:`Edit` button."
msgstr ""
#: ../dashboard_admin_manage_roles.rst:40
msgid "In the :guilabel:`Update Role` window, enter a new name for the role."
msgstr ""
#: ../dashboard_admin_manage_roles.rst:41
msgid "Click the :guilabel:`Update Role` button to confirm your changes."
msgstr ""
#: ../dashboard_admin_manage_roles.rst:45
msgid "Using the dashboard, you can edit only the name assigned to a role."
msgstr ""
#: ../dashboard_admin_manage_roles.rst:49
msgid "Delete a role"
msgstr ""
#: ../dashboard_admin_manage_roles.rst:54
msgid ""
"Select the role you want to delete and click the :guilabel:`Delete Roles` "
"button."
msgstr ""
#: ../dashboard_admin_manage_roles.rst:56
msgid ""
"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:59 ../dashboard_manage_images.rst:116
msgid "You cannot undo this action."
msgstr ""
#: ../dashboard_admin_manage_stacks.rst:3
msgid "Launch and manage stacks using the Dashboard"
msgstr ""
#: ../dashboard_admin_manage_stacks.rst:5
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 ""
#: ../dashboard_admin_manage_stacks.rst:11
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 ""
#: ../dashboard_admin_manage_stacks.rst:22
msgid ""
"administrative tasks on the command-line, see :doc:`cli_admin_manage_stacks`."
msgstr ""
#: ../dashboard_admin_manage_stacks.rst:27
msgid ""
"There are no administration-specific tasks that can be done through the "
"Dashboard."
msgstr ""
#: ../dashboard_admin_manage_stacks.rst:30
msgid ""
"the basic creation and deletion of Orchestration stacks, refer to the "
"`OpenStack End User Guide <http://docs.openstack.org/user-guide/"
"dashboard_stacks.html>`__."
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 ""
#: ../dashboard_manage_flavors.rst:9
msgid "The following table lists the default flavors."
msgstr ""
#: ../dashboard_manage_flavors.rst:22
msgid "Create flavors"
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:88 ../dashboard_manage_flavors.rst:154
#: ../dashboard_manage_host_aggregates.rst:19
#: ../dashboard_manage_images.rst:23
msgid "Log in to the dashboard."
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:26 ../dashboard_manage_flavors.rst:75
#: ../dashboard_manage_flavors.rst:90 ../dashboard_manage_flavors.rst:155
#: ../dashboard_manage_host_aggregates.rst:21
#: ../dashboard_manage_host_aggregates.rst:57
#: ../dashboard_manage_images.rst:25
msgid ""
"Choose the :guilabel:`admin` project from the drop-down list at the top of "
"the page."
msgstr ""
#: ../dashboard_manage_flavors.rst:28 ../dashboard_manage_flavors.rst:77
#: ../dashboard_manage_flavors.rst:92 ../dashboard_manage_flavors.rst:157
msgid ""
"In the :guilabel:`Admin` tab, open the :guilabel:`System` tab and click the :"
"guilabel:`Flavors` category."
msgstr ""
#: ../dashboard_manage_flavors.rst:30 ../dashboard_manage_flavors.rst:69
msgid "Click :guilabel:`Create Flavor`."
msgstr ""
#: ../dashboard_manage_flavors.rst:31
msgid ""
"In the :guilabel:`Create Flavor` window, enter or select the parameters for "
"the flavor in the :guilabel:`Flavor Information` tab."
msgstr ""
#: ../dashboard_manage_flavors.rst:35
msgid "**Name**"
msgstr ""
#: ../dashboard_manage_flavors.rst:35
msgid "Enter the flavor name."
msgstr ""
#: ../dashboard_manage_flavors.rst:36
msgid "**ID**"
msgstr ""
#: ../dashboard_manage_flavors.rst:39
msgid "**VCPUs**"
msgstr ""
#: ../dashboard_manage_flavors.rst:39
msgid "Enter the number of virtual CPUs to use."
msgstr ""
#: ../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:79
msgid "Select the flavor that you want to edit. Click :guilabel:`Edit Flavor`."
msgstr ""
#: ../dashboard_manage_flavors.rst:81
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:83 ../dashboard_manage_flavors.rst:99
msgid "Click :guilabel:`Save`."
msgstr ""
#: ../dashboard_manage_flavors.rst:86
msgid "Update Metadata"
msgstr ""
#: ../dashboard_manage_flavors.rst:94
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:97
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:101
msgid "**Optional metadata keys**"
msgstr ""
#: ../dashboard_manage_flavors.rst:104
msgid "quota:cpu_shares"
msgstr ""
#: ../dashboard_manage_flavors.rst:106
msgid "**CPU limits**"
msgstr ""
#: ../dashboard_manage_flavors.rst:106
msgid "quota:cpu_period"
msgstr ""
#: ../dashboard_manage_flavors.rst:108
msgid "quota:cpu_limit"
msgstr ""
#: ../dashboard_manage_flavors.rst:110
msgid "quota:cpu_reservation"
msgstr ""
#: ../dashboard_manage_flavors.rst:112
msgid "quota:cpu_quota"
msgstr ""
#: ../dashboard_manage_flavors.rst:114
msgid "quota:disk_read_bytes_sec"
msgstr ""
#: ../dashboard_manage_flavors.rst:116
msgid "**Disk tuning**"
msgstr ""
#: ../dashboard_manage_flavors.rst:116
msgid "quota:disk_read_iops_sec"
msgstr ""
#: ../dashboard_manage_flavors.rst:118
msgid "quota:disk_write_bytes_sec"
msgstr ""
#: ../dashboard_manage_flavors.rst:120
msgid "quota:disk_write_iops_sec"
msgstr ""
#: ../dashboard_manage_flavors.rst:122
msgid "quota:disk_total_bytes_sec"
msgstr ""
#: ../dashboard_manage_flavors.rst:124
msgid "quota:disk_total_iops_sec"
msgstr ""
#: ../dashboard_manage_flavors.rst:126
msgid "quota:vif_inbound_average"
msgstr ""
#: ../dashboard_manage_flavors.rst:128
msgid "**Bandwidth I/O**"
msgstr ""
#: ../dashboard_manage_flavors.rst:128
msgid "quota:vif_inbound_burst"
msgstr ""
#: ../dashboard_manage_flavors.rst:130
msgid "quota:vif_inbound_peak"
msgstr ""
#: ../dashboard_manage_flavors.rst:132
msgid "quota:vif_outbound_average"
msgstr ""
#: ../dashboard_manage_flavors.rst:134
msgid "quota:vif_outbound_burst"
msgstr ""
#: ../dashboard_manage_flavors.rst:136
msgid "quota:vif_outbound_peak"
msgstr ""
#: ../dashboard_manage_flavors.rst:138
msgid "**Watchdog behavior**"
msgstr ""
#: ../dashboard_manage_flavors.rst:138
msgid "hw:watchdog_action"
msgstr ""
#: ../dashboard_manage_flavors.rst:140
msgid "hw_rng:allowed"
msgstr ""
#: ../dashboard_manage_flavors.rst:142
msgid "**Random-number generator**"
msgstr ""
#: ../dashboard_manage_flavors.rst:142
msgid "hw_rng:rate_bytes"
msgstr ""
#: ../dashboard_manage_flavors.rst:144
msgid "hw_rng:rate_period"
msgstr ""
#: ../dashboard_manage_flavors.rst:147
msgid ""
"For information about supporting metadata keys, see the `OpenStack Cloud "
"Administrator Guide <http://docs.openstack.org/admin-guide-cloud/compute-"
"flavors.html>`__."
msgstr ""
#: ../dashboard_manage_flavors.rst:152
msgid "Delete flavors"
msgstr ""
#: ../dashboard_manage_flavors.rst:159
msgid "Select the flavors that you want to delete."
msgstr ""
#: ../dashboard_manage_flavors.rst:160
msgid "Click :guilabel:`Delete Flavors`."
msgstr ""
#: ../dashboard_manage_flavors.rst:161
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 <http://docs.openstack.org/liberty/config-"
"reference/content/section_compute-scheduler.html>`__."
msgstr ""
#: ../dashboard_manage_host_aggregates.rst:17
msgid "To create a host aggregate"
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 Information` tab:"
msgstr ""
#: ../dashboard_manage_host_aggregates.rst:32
msgid ":guilabel:`Name`: The host aggregate name."
msgstr ""
#: ../dashboard_manage_host_aggregates.rst:34
msgid ""
":guilabel:`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 <http://docs.openstack.org/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 "
"<http://docs.openstack.org/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:`Architecture`"
msgstr ""
#: ../dashboard_manage_images.rst:61
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:66
msgid ":guilabel:`Minimum Disk (GB)`"
msgstr ""
#: ../dashboard_manage_images.rst:66 ../dashboard_manage_images.rst:68
msgid "Leave this field empty."
msgstr ""
#: ../dashboard_manage_images.rst:68
msgid ":guilabel:`Minimum RAM (MB)`"
msgstr ""
#: ../dashboard_manage_images.rst:70
msgid ":guilabel:`Copy Data`"
msgstr ""
#: ../dashboard_manage_images.rst:70
msgid "Specify this option to copy image data to the Image service."
msgstr ""
#: ../dashboard_manage_images.rst:73
msgid ":guilabel:`Public`"
msgstr ""
#: ../dashboard_manage_images.rst:73
msgid "Select this option to make the image public to all users."
msgstr ""
#: ../dashboard_manage_images.rst:76
msgid ":guilabel:`Protected`"
msgstr ""
#: ../dashboard_manage_images.rst:76
msgid ""
"Select this option to ensure that only users with permissions can delete it."
msgstr ""
#: ../dashboard_manage_images.rst:81
msgid "Click :guilabel:`Create Image`."
msgstr ""
#: ../dashboard_manage_images.rst:83
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:87
msgid "Update images"
msgstr ""
#: ../dashboard_manage_images.rst:89 ../dashboard_manage_images.rst:106
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:92
msgid ""
"On the :guilabel:`Admin` tab, open the :guilabel:`System` tab and click the :"
"guilabel:`Images` category."
msgstr ""
#: ../dashboard_manage_images.rst:94
msgid "Select the images that you want to edit. Click :guilabel:`Edit Image`."
msgstr ""
#: ../dashboard_manage_images.rst:95
msgid "In the :guilabel:`Update Image` window, you can change the image name."
msgstr ""
#: ../dashboard_manage_images.rst:97
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 :guilabel:`Kernel "
"ID`, :guilabel:`Ramdisk ID`, or :guilabel:`Architecture` attributes for an "
"image."
msgstr ""
#: ../dashboard_manage_images.rst:101
msgid "Click :guilabel:`Update Image`."
msgstr ""
#: ../dashboard_manage_images.rst:104
msgid "Delete images"
msgstr ""
#: ../dashboard_manage_images.rst:109
msgid ""
"On the :guilabel:`Admin tab`, open the :guilabel:`System` tab and click the :"
"guilabel:`Images` category."
msgstr ""
#: ../dashboard_manage_images.rst:111
msgid "Select the images that you want to delete."
msgstr ""
#: ../dashboard_manage_images.rst:112
msgid "Click :guilabel:`Delete Images`."
msgstr ""
#: ../dashboard_manage_images.rst:113
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 <http://docs.openstack.org/user-"
"guide/dashboard_launch_instances.html>`__."
msgstr ""
#: ../dashboard_manage_instances.rst:14
msgid "Create instance snapshots"
msgstr ""
#: ../dashboard_manage_instances.rst:16 ../dashboard_manage_instances.rst:38
#: ../dashboard_manage_instances.rst:67
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: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 <http://docs.openstack.org/user-guide/"
"dashboard_launch_instances.html>`__."
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 ""
"From the 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 "
"(actions in red color 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 :guilabel:`Overview` category to track usage of instances for each "
"project."
msgstr ""
#: ../dashboard_manage_instances.rst:64
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:70
msgid "On the :guilabel:`Admin` tab, click the :guilabel:`Instances` category."
msgstr ""
#: ../dashboard_manage_instances.rst:72
msgid ""
"Select a month and click :guilabel:`Submit` to query the instance usage for "
"that month."
msgstr ""
#: ../dashboard_manage_instances.rst:75
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_shares.rst:3
msgid "Manage shares and share types"
msgstr ""
#: ../dashboard_manage_shares.rst:5
msgid ""
"Shares are file storage that instances can have access to. Users can allow "
"or deny a running instance to have access to a share at any time. For "
"information about using the dashboard to create and manage shares as an end "
"user, see the `OpenStack End User Guide <http://docs.openstack.org/user-"
"guide/dashboard_manage_shares.html>`_."
msgstr ""
#: ../dashboard_manage_shares.rst:11
msgid ""
"As an administrative user, you can manage shares and share types for users "
"in various projects. You can create and delete share types, and you can view "
"and delete shares."
msgstr ""
#: ../dashboard_manage_shares.rst:18
msgid "Create a share type"
msgstr ""
# #-#-#-#-# dashboard_manage_shares.pot (Admin User Guide 1.0.0) #-#-#-#-#
# #-#-#-#-# dashboard_manage_volumes.pot (Admin User Guide 1.0.0) #-#-#-#-#
#: ../dashboard_manage_shares.rst:20 ../dashboard_manage_shares.rst:46
#: ../dashboard_manage_shares.rst:73 ../dashboard_manage_shares.rst:94
#: ../dashboard_manage_shares.rst:114 ../dashboard_manage_shares.rst:134
#: ../dashboard_manage_volumes.rst:21 ../dashboard_manage_volumes.rst:125
#: ../dashboard_manage_volumes.rst:149
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_shares.rst:23 ../dashboard_manage_shares.rst:49
#: ../dashboard_manage_shares.rst:76 ../dashboard_manage_shares.rst:97
msgid ""
"On the :guilabel:`Admin` tab, open the :guilabel:`System` tab and click the :"
"guilabel:`Shares` category."
msgstr ""
#: ../dashboard_manage_shares.rst:26
msgid ""
"Click the :guilabel:`Share Types` tab, and click :guilabel:`Create Share "
"Type` button. In the :guilabel:`Create Share Type` window, enter or select "
"the following values."
msgstr ""
#: ../dashboard_manage_shares.rst:31
msgid ":guilabel:`Name`: Enter a name for the share type."
msgstr ""
#: ../dashboard_manage_shares.rst:33
msgid ":guilabel:`Driver handles share servers`: Choose True or False"
msgstr ""
#: ../dashboard_manage_shares.rst:35
msgid ":guilabel:`Extra specs`: To add extra specs, use key=value."
msgstr ""
#: ../dashboard_manage_shares.rst:37
msgid "Click :guilabel:`Create Share Type` button to confirm your changes."
msgstr ""
# #-#-#-#-# dashboard_manage_shares.pot (Admin User Guide 1.0.0) #-#-#-#-#
# #-#-#-#-# dashboard_manage_volumes.pot (Admin User Guide 1.0.0) #-#-#-#-#
#: ../dashboard_manage_shares.rst:41 ../dashboard_manage_shares.rst:66
#: ../dashboard_manage_shares.rst:89 ../dashboard_manage_shares.rst:109
#: ../dashboard_manage_shares.rst:129 ../dashboard_manage_shares.rst:149
#: ../dashboard_manage_volumes.rst:35 ../dashboard_manage_volumes.rst:141
#: ../dashboard_manage_volumes.rst:164
msgid "A message indicates whether the action succeeded."
msgstr ""
#: ../dashboard_manage_shares.rst:44
msgid "Update share type"
msgstr ""
#: ../dashboard_manage_shares.rst:52
msgid ""
"Click the :guilabel:`Share Types` tab, select the share type that you want "
"to update."
msgstr ""
#: ../dashboard_manage_shares.rst:55
msgid "Select :guilabel:`Update Share Type` from Actions."
msgstr ""
#: ../dashboard_manage_shares.rst:57
msgid "In the :guilabel:`Update Share Type` window, update extra specs."
msgstr ""
#: ../dashboard_manage_shares.rst:59
msgid ""
":guilabel:`Extra specs`: To add extra specs, use key=value. To unset extra "
"specs, use key."
msgstr ""
#: ../dashboard_manage_shares.rst:62
msgid "Click :guilabel:`Update Share Type` button to confirm your changes."
msgstr ""
#: ../dashboard_manage_shares.rst:69
msgid "Delete share types"
msgstr ""
#: ../dashboard_manage_shares.rst:71
msgid "When you delete a share type, shares of that type are not deleted."
msgstr ""
#: ../dashboard_manage_shares.rst:79
msgid ""
"Click the :guilabel:`Share Types` tab, select the share type or types that "
"you want to delete."
msgstr ""
#: ../dashboard_manage_shares.rst:82
msgid "Click :guilabel:`Delete Share Types` button."
msgstr ""
#: ../dashboard_manage_shares.rst:84
msgid ""
"In the :guilabel:`Confirm Delete Share Types` window, click the :guilabel:"
"`Delete Share Types` button to confirm the action."
msgstr ""
#: ../dashboard_manage_shares.rst:92
msgid "Delete shares"
msgstr ""
#: ../dashboard_manage_shares.rst:100
msgid "Select the share or shares that you want to delete."
msgstr ""
#: ../dashboard_manage_shares.rst:102
msgid "Click :guilabel:`Delete Shares` button."
msgstr ""
#: ../dashboard_manage_shares.rst:104
msgid ""
"In the :guilabel:`Confirm Delete Shares` window, click the :guilabel:`Delete "
"Shares` button to confirm the action."
msgstr ""
#: ../dashboard_manage_shares.rst:112
msgid "Delete share server"
msgstr ""
#: ../dashboard_manage_shares.rst:117
msgid ""
"On the :guilabel:`Admin` tab, open the :guilabel:`System` tab and click the :"
"guilabel:`Share Servers` category."
msgstr ""
#: ../dashboard_manage_shares.rst:120
msgid "Select the share that you want to delete."
msgstr ""
#: ../dashboard_manage_shares.rst:122
msgid "Click :guilabel:`Delete Share Server` button."
msgstr ""
#: ../dashboard_manage_shares.rst:124
msgid ""
"In the :guilabel:`Confirm Delete Share Server` window, click the :guilabel:"
"`Delete Share Server` button to confirm the action."
msgstr ""
#: ../dashboard_manage_shares.rst:132
msgid "Delete share networks"
msgstr ""
#: ../dashboard_manage_shares.rst:137
msgid ""
"On the :guilabel:`Admin` tab, open the :guilabel:`System` tab and click the :"
"guilabel:`Share Networks` category."
msgstr ""
#: ../dashboard_manage_shares.rst:140
msgid "Select the share network or share networks that you want to delete."
msgstr ""
#: ../dashboard_manage_shares.rst:142
msgid "Click :guilabel:`Delete Share Networks` button."
msgstr ""
#: ../dashboard_manage_shares.rst:144
msgid ""
"In the :guilabel:`Confirm Delete Share Networks` window, click the :guilabel:"
"`Delete Share Networks` button to confirm the action."
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 <http://docs.openstack.org/user-"
"guide/dashboard_manage_volumes.html>`_."
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:24 ../dashboard_manage_volumes.rst:128
#: ../dashboard_manage_volumes.rst:152
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:38
msgid "Create an encrypted volume type"
msgstr ""
#: ../dashboard_manage_volumes.rst:40
msgid ""
"Create a volume type using the steps above for :ref:`create-a-volume-type`."
msgstr ""
#: ../dashboard_manage_volumes.rst:42
msgid ""
"Click :guilabel:`Create Encryption` in the Actions column of the newly "
"created volume type."
msgstr ""
#: ../dashboard_manage_volumes.rst:45
msgid ""
"Configure the encrypted volume by setting the parameters below from "
"available options (see table):"
msgstr ""
#: ../dashboard_manage_volumes.rst:48 ../dashboard_manage_volumes.rst:74
msgid "Provider"
msgstr ""
#: ../dashboard_manage_volumes.rst:49
msgid "Specifies the class responsible for configuring the encryption."
msgstr ""
#: ../dashboard_manage_volumes.rst:51 ../dashboard_manage_volumes.rst:85
msgid "Control Location"
msgstr ""
#: ../dashboard_manage_volumes.rst:51
msgid ""
"Specifies whether the encryption is from the front end (nova) or the back "
"end (cinder)."
msgstr ""
#: ../dashboard_manage_volumes.rst:53 ../dashboard_manage_volumes.rst:101
msgid "Cipher"
msgstr ""
#: ../dashboard_manage_volumes.rst:54
msgid "Specifies the encryption algorithm."
msgstr ""
#: ../dashboard_manage_volumes.rst:56 ../dashboard_manage_volumes.rst:108
msgid "Key Size (bits)"
msgstr ""
#: ../dashboard_manage_volumes.rst:56
msgid "Specifies the encryption key size."
msgstr ""
#: ../dashboard_manage_volumes.rst:58
msgid "Click :guilabel:`Create Volume Type Encryption`."
msgstr ""
#: ../dashboard_manage_volumes.rst:62
msgid ""
"Once a volume type is updated by the :guilabel:`Create Encryption` option, "
"the volume type cannot be deleted."
msgstr ""
#: ../dashboard_manage_volumes.rst:65
msgid "**Encryption Options**"
msgstr ""
#: ../dashboard_manage_volumes.rst:67
msgid ""
"The table below provides a few alternatives available for creating encrypted "
"volumes."
msgstr ""
#: ../dashboard_manage_volumes.rst:71
msgid "Comments"
msgstr ""
#: ../dashboard_manage_volumes.rst:71
msgid "Encryption parameters"
msgstr ""
#: ../dashboard_manage_volumes.rst:71
msgid "Parameter options"
msgstr ""
#: ../dashboard_manage_volumes.rst:74
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:74
msgid "nova.volume.encryptors. luks.LuksEncryptor (Recommended)"
msgstr ""
#: ../dashboard_manage_volumes.rst:81
msgid "Less disk overhead than LUKS"
msgstr ""
#: ../dashboard_manage_volumes.rst:81
msgid "nova.volume.encryptors. cryptsetup. CryptsetupEncryptor"
msgstr ""
#: ../dashboard_manage_volumes.rst:85
msgid ""
"The encryption occurs within nova so that the data transmitted over the "
"network is encrypted"
msgstr ""
#: ../dashboard_manage_volumes.rst:85
msgid "front-end (Recommended)"
msgstr ""
#: ../dashboard_manage_volumes.rst:91
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:91
msgid "back-end"
msgstr ""
#: ../dashboard_manage_volumes.rst:101
msgid "See NIST reference below to see advantages*"
msgstr ""
#: ../dashboard_manage_volumes.rst:101
msgid "aes-xts-plain64 (Recommended)"
msgstr ""
#: ../dashboard_manage_volumes.rst:104
msgid ""
"Note: On the command line, type 'cryptsetup benchmark' for additional options"
msgstr ""
#: ../dashboard_manage_volumes.rst:104
msgid "aes-cbc-essiv"
msgstr ""
#: ../dashboard_manage_volumes.rst:108
msgid ""
"512 (Recommended for aes-xts-plain64. 256 should be used for aes-cbc-essiv)"
msgstr ""
#: ../dashboard_manage_volumes.rst:108
msgid ""
"Using this selection for aes-xts, the underlying key size would only be 256-"
"bits*"
msgstr ""
#: ../dashboard_manage_volumes.rst:113
msgid "256"
msgstr ""
#: ../dashboard_manage_volumes.rst:113
msgid ""
"Using this selection for aes-xts, the underlying key size would only be 128-"
"bits*"
msgstr ""
#: ../dashboard_manage_volumes.rst:118
msgid ""
"`*` Source `NIST SP 800-38E <http://csrc.nist.gov/publications/"
"nistpubs/800-38E/nist-sp-800-38E.pdf>`_"
msgstr ""
#: ../dashboard_manage_volumes.rst:121
msgid "Delete volume types"
msgstr ""
#: ../dashboard_manage_volumes.rst:123
msgid "When you delete a volume type, volumes of that type are not deleted."
msgstr ""
#: ../dashboard_manage_volumes.rst:131
msgid ""
"Click the :guilabel:`Volume Types` tab, select the volume type or types that "
"you want to delete."
msgstr ""
#: ../dashboard_manage_volumes.rst:134
msgid "Click :guilabel:`Delete Volume Types` button."
msgstr ""
#: ../dashboard_manage_volumes.rst:136
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:144
msgid "Delete volumes"
msgstr ""
#: ../dashboard_manage_volumes.rst:146
msgid ""
"When you delete an instance, the data of its attached volumes is not "
"destroyed."
msgstr ""
#: ../dashboard_manage_volumes.rst:155
msgid "Select the volume or volumes that you want to delete."
msgstr ""
#: ../dashboard_manage_volumes.rst:157
msgid "Click :guilabel:`Delete Volumes` button."
msgstr ""
#: ../dashboard_manage_volumes.rst:159
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:24
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:30
msgid ""
"The following table describes the Compute and Block Storage service quotas:"
msgstr ""
#: ../dashboard_set_quotas.rst:34
msgid "**Quota Descriptions**"
msgstr ""
#: ../dashboard_set_quotas.rst:37
msgid "Quota Name"
msgstr ""
#: ../dashboard_set_quotas.rst:37
msgid "Service"
msgstr ""
#: ../dashboard_set_quotas.rst:39 ../dashboard_set_quotas.rst:65
#: ../dashboard_set_quotas.rst:71
msgid "Block Storage"
msgstr ""
#: ../dashboard_set_quotas.rst:39
msgid "Gigabytes"
msgstr ""
#: ../dashboard_set_quotas.rst:39
msgid "Volume gigabytes allowed for each project."
msgstr ""
#: ../dashboard_set_quotas.rst:42 ../dashboard_set_quotas.rst:45
#: ../dashboard_set_quotas.rst:48 ../dashboard_set_quotas.rst:51
#: ../dashboard_set_quotas.rst:53 ../dashboard_set_quotas.rst:56
#: ../dashboard_set_quotas.rst:59 ../dashboard_set_quotas.rst:62
#: ../dashboard_set_quotas.rst:68
msgid "Compute"
msgstr ""
#: ../dashboard_set_quotas.rst:42
msgid "Instances"
msgstr ""
#: ../dashboard_set_quotas.rst:42
msgid "Instances allowed for each project."
msgstr ""
#: ../dashboard_set_quotas.rst:45
msgid "Injected Files"
msgstr ""
#: ../dashboard_set_quotas.rst:45
msgid "Injected files allowed for each project."
msgstr ""
#: ../dashboard_set_quotas.rst:48
msgid "Content bytes allowed for each injected file."
msgstr ""
#: ../dashboard_set_quotas.rst:48
msgid "Injected File Content Bytes"
msgstr ""
#: ../dashboard_set_quotas.rst:51
msgid "Keypairs"
msgstr ""
#: ../dashboard_set_quotas.rst:51
msgid "Number of keypairs."
msgstr ""
#: ../dashboard_set_quotas.rst:53
msgid "Metadata Items"
msgstr ""
#: ../dashboard_set_quotas.rst:53
msgid "Metadata items allowed for each instance."
msgstr ""
#: ../dashboard_set_quotas.rst:56
msgid "RAM (MB)"
msgstr ""
#: ../dashboard_set_quotas.rst:56
msgid "RAM megabytes allowed for each instance."
msgstr ""
#: ../dashboard_set_quotas.rst:59
msgid "Security Groups"
msgstr ""
#: ../dashboard_set_quotas.rst:59
msgid "Security groups allowed for each project."
msgstr ""
#: ../dashboard_set_quotas.rst:62
msgid "Rules allowed for each security group."
msgstr ""
#: ../dashboard_set_quotas.rst:62
msgid "Security Group Rules"
msgstr ""
#: ../dashboard_set_quotas.rst:65
msgid "Snapshots"
msgstr ""
#: ../dashboard_set_quotas.rst:65
msgid "Volume snapshots allowed for each project."
msgstr ""
#: ../dashboard_set_quotas.rst:68
msgid "Instance cores allowed for each project."
msgstr ""
#: ../dashboard_set_quotas.rst:71
msgid "Volumes"
msgstr ""
#: ../dashboard_set_quotas.rst:71
msgid "Volumes allowed for each project."
msgstr ""
#: ../dashboard_set_quotas.rst:78
msgid "View default project quotas"
msgstr ""
#: ../dashboard_set_quotas.rst:80 ../dashboard_set_quotas.rst:97
msgid "Log in to the OpenStack dashboard."
msgstr ""
#: ../dashboard_set_quotas.rst:82 ../dashboard_set_quotas.rst:99
msgid ""
"On the :guilabel:`Admin` tab, open the :guilabel:`System` tab and click the :"
"guilabel:`Defaults` category."
msgstr ""
#: ../dashboard_set_quotas.rst:85
msgid "The default quota values are displayed."
msgstr ""
#: ../dashboard_set_quotas.rst:89
msgid ""
"You can sort the table by clicking on either the :guilabel:`Quota Name` or :"
"guilabel:`Limit` column headers."
msgstr ""
#: ../dashboard_set_quotas.rst:95
msgid "Update project quotas"
msgstr ""
#: ../dashboard_set_quotas.rst:102 ../dashboard_set_quotas.rst:107
msgid "Click the :guilabel:`Update Defaults` button."
msgstr ""
#: ../dashboard_set_quotas.rst:104
msgid ""
"In the :guilabel:`Update Default Quotas` window, you can edit the default "
"quota values."
msgstr ""
#: ../dashboard_set_quotas.rst:111
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 service 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 <http://docs.openstack.org/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 Liberty, OpenStack Kilo, and OpenStack Juno "
"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 <https://git.openstack.org/cgit/openstack/horizon>`__, to view, "
"create, and manage resources and services."
msgstr ""
#: ../intro-admin.rst:15
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:20
msgid "You can modify these examples for your specific use cases."
msgstr ""
#: ../intro-admin.rst:22
msgid ""
"In addition to these ways of interacting with a cloud, you can access the "
"OpenStack APIs directly or indirectly through `cURL <http://curl.haxx.se>`__ "
"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:28
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:33
msgid "Who should read this book?"
msgstr ""
#: ../intro-admin.rst:35
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 <http://docs.openstack.org/"
"ops>`__."
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 <http://"
"docs.openstack.org/user-guide/common/"
"cli_set_environment_variables_using_openstack_rc.html>`__."
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:63
msgid "Create a project"
msgstr ""
#: ../manage_projects_users_and_roles.rst:65
msgid "Create a project named ``new-project``:"
msgstr ""
#: ../manage_projects_users_and_roles.rst:81
msgid "Update a project"
msgstr ""
#: ../manage_projects_users_and_roles.rst:83
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:86
msgid "To temporarily disable a project:"
msgstr ""
#: ../manage_projects_users_and_roles.rst:92
msgid "To enable a disabled project:"
msgstr ""
#: ../manage_projects_users_and_roles.rst:98
msgid "To update the name of a project:"
msgstr ""
#: ../manage_projects_users_and_roles.rst:104
msgid "To verify your changes, show information for the updated project:"
msgstr ""
#: ../manage_projects_users_and_roles.rst:120
msgid "Delete a project"
msgstr ""
#: ../manage_projects_users_and_roles.rst:122
msgid "Specify the project ID to delete a project:"
msgstr ""
#: ../manage_projects_users_and_roles.rst:129
msgid "User"
msgstr ""
#: ../manage_projects_users_and_roles.rst:132
msgid "List users"
msgstr ""
#: ../manage_projects_users_and_roles.rst:134
msgid "List all users:"
msgstr ""
#: ../manage_projects_users_and_roles.rst:150
msgid "Create a user"
msgstr ""
#: ../manage_projects_users_and_roles.rst:152
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:157
msgid "Create the ``new-user`` user:"
msgstr ""
#: ../manage_projects_users_and_roles.rst:174
msgid "Update a user"
msgstr ""
#: ../manage_projects_users_and_roles.rst:176
msgid "You can update the name, email address, and enabled status for a user."
msgstr ""
#: ../manage_projects_users_and_roles.rst:178
msgid "To temporarily disable a user account:"
msgstr ""
#: ../manage_projects_users_and_roles.rst:184
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:188
msgid "To enable a disabled user account:"
msgstr ""
#: ../manage_projects_users_and_roles.rst:194
msgid "To change the name and description for a user account:"
msgstr ""
#: ../manage_projects_users_and_roles.rst:202
msgid "Delete a user"
msgstr ""
#: ../manage_projects_users_and_roles.rst:204
msgid "Delete a specified user account:"
msgstr ""
#: ../manage_projects_users_and_roles.rst:211
msgid "Roles and role assignments"
msgstr ""
#: ../manage_projects_users_and_roles.rst:214
msgid "List available roles"
msgstr ""
#: ../manage_projects_users_and_roles.rst:216
msgid "List the available roles:"
msgstr ""
#: ../manage_projects_users_and_roles.rst:235
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:238
msgid "Create the ``new-role`` role:"
msgstr ""
#: ../manage_projects_users_and_roles.rst:252
msgid "Assign a role"
msgstr ""
#: ../manage_projects_users_and_roles.rst:254
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:258
msgid "List users and note the user ID you want to assign to the role:"
msgstr ""
#: ../manage_projects_users_and_roles.rst:275
msgid "List role IDs and note the role ID you want to assign:"
msgstr ""
#: ../manage_projects_users_and_roles.rst:292
msgid "List projects and note the project ID you want to assign to the role:"
msgstr ""
#: ../manage_projects_users_and_roles.rst:311
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:318
msgid "Verify the role assignment:"
msgstr ""
#: ../manage_projects_users_and_roles.rst:331
msgid "View role details"
msgstr ""
#: ../manage_projects_users_and_roles.rst:333
msgid "View details for a specified role:"
msgstr ""
#: ../manage_projects_users_and_roles.rst:347
msgid "Remove a role"
msgstr ""
#: ../manage_projects_users_and_roles.rst:349
msgid "Remove a role from a user-project pair:"
msgstr ""
#: ../manage_projects_users_and_roles.rst:351
msgid "Run the :command:`openstack role remove` command:"
msgstr ""
#: ../manage_projects_users_and_roles.rst:357
msgid "Verify the role removal:"
msgstr ""
#: ../manage_projects_users_and_roles.rst:363
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 ``neutron.conf`` "
"configuration file. To disable quotas for a specific resource, such as "
"network, subnet, or port, remove a corresponding item from ``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 ``neutron."
"conf`` file:"
msgstr ""
#: ../networking_advanced_quotas.rst:61 ../networking_advanced_quotas.rst:79
msgid "The ``quota_items`` option does not affect these quotas."
msgstr ""
#: ../networking_advanced_quotas.rst:63
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 ``neutron.conf`` file:"
msgstr ""
#: ../networking_advanced_quotas.rst:84
msgid "Configure per-tenant quotas"
msgstr ""
#: ../networking_advanced_quotas.rst:85
msgid ""
"OpenStack Networking also supports per-tenant quota limit by quota extension "
"API."
msgstr ""
#: ../networking_advanced_quotas.rst:88
msgid "Use these commands to manage per-tenant quotas:"
msgstr ""
#: ../networking_advanced_quotas.rst:91
msgid "Delete defined quotas for a specified tenant"
msgstr ""
#: ../networking_advanced_quotas.rst:91
msgid "neutron quota-delete"
msgstr ""
#: ../networking_advanced_quotas.rst:94
msgid "Lists defined quotas for all tenants"
msgstr ""
#: ../networking_advanced_quotas.rst:94
msgid "neutron quota-list"
msgstr ""
#: ../networking_advanced_quotas.rst:97
msgid "Shows quotas for a specified tenant"
msgstr ""
#: ../networking_advanced_quotas.rst:97
msgid "neutron quota-show"
msgstr ""
#: ../networking_advanced_quotas.rst:100
msgid "Updates quotas for a specified tenant"
msgstr ""
#: ../networking_advanced_quotas.rst:100
msgid "neutron quota-update"
msgstr ""
#: ../networking_advanced_quotas.rst:102
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:106
msgid "Configure Networking to show per-tenant quotas"
msgstr ""
#: ../networking_advanced_quotas.rst:108
msgid "Set the ``quota_driver`` option in the ``neutron.conf`` file."
msgstr ""
#: ../networking_advanced_quotas.rst:114
msgid ""
"When you set this option, the output for Networking commands shows "
"``quotas``."
msgstr ""
#: ../networking_advanced_quotas.rst:116
msgid "List Networking extensions."
msgstr ""
#: ../networking_advanced_quotas.rst:118
msgid "To list the Networking extensions, run this command:"
msgstr ""
#: ../networking_advanced_quotas.rst:124
msgid ""
"The command shows the ``quotas`` extension, which provides per-tenant quota "
"management support."
msgstr ""
#: ../networking_advanced_quotas.rst:143
msgid "Show information for the quotas extension."
msgstr ""
#: ../networking_advanced_quotas.rst:145
msgid "To show information for the ``quotas`` extension, run this command:"
msgstr ""
#: ../networking_advanced_quotas.rst:164
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:170
msgid "List tenants who have per-tenant quota support."
msgstr ""
#: ../networking_advanced_quotas.rst:172
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:187
msgid "Show per-tenant quota values."
msgstr ""
#: ../networking_advanced_quotas.rst:189
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 :option:`--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:210
msgid ""
"The following command shows the command output for a non-administrative user."
msgstr ""
#: ../networking_advanced_quotas.rst:227
msgid "Update quota values for a specified tenant."
msgstr ""
#: ../networking_advanced_quotas.rst:229
msgid ""
"Use the :command:`quota-update` command to update a quota for a specified "
"tenant."
msgstr ""
#: ../networking_advanced_quotas.rst:246
msgid "You can update quotas for multiple resources through one command."
msgstr ""
#: ../networking_advanced_quotas.rst:263
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:267
msgid ""
"This example updates the limit of the number of floating IPs for the "
"specified tenant."
msgstr ""
#: ../networking_advanced_quotas.rst:284
msgid ""
"You can update the limits of multiple resources by including L2 resources "
"and L3 resource through one command:"
msgstr ""
#: ../networking_advanced_quotas.rst:302
msgid "Delete per-tenant quota values."
msgstr ""
#: ../networking_advanced_quotas.rst:304
msgid ""
"To clear per-tenant quota limits, use the :command:`quota-delete` command."
msgstr ""
#: ../networking_advanced_quotas.rst:312
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 ``/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 <http://docs.openstack.org/user-guide-admin/cli_set_quotas.html>`_ "
"section)."
msgstr ""
#: ../nova_cli_manage_projects_security.rst:37
msgid "List and view current security groups"
msgstr ""
#: ../nova_cli_manage_projects_security.rst:39
msgid ""
"From the command-line you can get a list of security groups for the project, "
"using the :command:`nova` command:"
msgstr ""
#: ../nova_cli_manage_projects_security.rst:42
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:50
msgid "Output security groups, as follows:"
msgstr ""
#: ../nova_cli_manage_projects_security.rst:63
msgid "View the details of a group, as follows:"
msgstr ""
#: ../nova_cli_manage_projects_security.rst:83
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:90
msgid "Create a security group"
msgstr ""
#: ../nova_cli_manage_projects_security.rst:91
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:97
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:100
msgid "Add the new security group, as follows:"
msgstr ""
#: ../nova_cli_manage_projects_security.rst:118
msgid "Add a new group rule, as follows:"
msgstr ""
#: ../nova_cli_manage_projects_security.rst:124
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:139
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:152
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:155
msgid "View all rules for the new security group, as follows:"
msgstr ""
#: ../nova_cli_manage_projects_security.rst:169
msgid "Delete a security group"
msgstr ""
#: ../nova_cli_manage_projects_security.rst:171
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:174
msgid "Delete the new security group, as follows:"
msgstr ""
#: ../nova_cli_manage_projects_security.rst:187
msgid "Create security group rules for a cluster of instances"
msgstr ""
#: ../nova_cli_manage_projects_security.rst:189
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 user's 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:195
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:198
msgid "Add a source group, as follows:"
msgstr ""
#: ../nova_cli_manage_projects_security.rst:210
msgid ""
"The ``cluster`` rule allows ssh access from any other instance that uses the "
"``global_http`` group."
msgstr ""
View Git Blame Copy Permalink