# SOME DESCRIPTIVE TITLE. # Copyright (C) 2015-2016, OpenStack contributors # This file is distributed under the same license as the End User Guide package. # FIRST AUTHOR , YEAR. # #, fuzzy msgid "" msgstr "" "Project-Id-Version: End User Guide 1.0.0\n" "Report-Msgid-Bugs-To: \n" "POT-Creation-Date: 2016-04-29 06:25+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" # #-#-#-#-# backup_db.pot (End User Guide 1.0.0) #-#-#-#-# # #-#-#-#-# dashboard_databases.pot (End User Guide 1.0.0) #-#-#-#-# #: ../backup_db.rst:3 ../dashboard_databases.rst:103 msgid "Backup and restore a database" msgstr "" # #-#-#-#-# backup_db.pot (End User Guide 1.0.0) #-#-#-#-# # #-#-#-#-# dashboard_databases.pot (End User Guide 1.0.0) #-#-#-#-# #: ../backup_db.rst:5 ../dashboard_databases.rst:105 msgid "" "You can use Database services to backup a database and store the backup " "artifact in the Object Storage service. Later on, if the original database " "is damaged, you can use the backup artifact to restore the database. The " "restore process creates a database instance." msgstr "" # #-#-#-#-# backup_db.pot (End User Guide 1.0.0) #-#-#-#-# # #-#-#-#-# dashboard_databases.pot (End User Guide 1.0.0) #-#-#-#-# #: ../backup_db.rst:10 ../dashboard_databases.rst:110 msgid "This example shows you how to back up and restore a MySQL database." msgstr "" #: ../backup_db.rst:12 msgid "**Backup the database instance**" msgstr "" #: ../backup_db.rst:14 msgid "" "As background, assume that you have created a database instance with the " "following characteristics:" msgstr "" #: ../backup_db.rst:18 msgid "Name of the database instance: ``guest1``" msgstr "" #: ../backup_db.rst:20 msgid "Flavor ID: ``10``" msgstr "" #: ../backup_db.rst:22 msgid "Root volume size: ``2``" msgstr "" #: ../backup_db.rst:24 msgid "Databases: ``db1`` and ``db2``" msgstr "" #: ../backup_db.rst:26 msgid "Users: The ``user1`` user with the ``password`` password" msgstr "" #: ../backup_db.rst:28 msgid "" "First, get the ID of the ``guest1`` database instance by using the :command:" "`trove list` command:" msgstr "" #: ../backup_db.rst:41 msgid "" "Back up the database instance by using the :command:`trove backup-create` " "command. In this example, the backup is called ``backup1``. In this example, " "replace ``INSTANCE_ID`` with ``97b4b853-80f6-414f-ba6f-c6f455a79ae6``:" msgstr "" #: ../backup_db.rst:48 msgid "" "This command syntax pertains only to python-troveclient version 1.0.6 and " "later. Earlier versions require you to pass in the backup name as the first " "argument." msgstr "" #: ../backup_db.rst:71 msgid "" "Note that the command returns both the ID of the original instance " "(``instance_id``) and the ID of the backup artifact (``id``)." msgstr "" #: ../backup_db.rst:74 msgid "" "Later on, use the :command:`trove backup-list` command to get this " "information:" msgstr "" #: ../backup_db.rst:86 msgid "" "You can get additional information about the backup by using the :command:" "`trove backup-show` command and passing in the ``BACKUP_ID``, which is " "``8af30763-61fd-4aab-8fe8-57d528911138``." msgstr "" #: ../backup_db.rst:109 msgid "**Restore a database instance**" msgstr "" #: ../backup_db.rst:111 msgid "" "Now assume that your ``guest1`` database instance is damaged and you need to " "restore it. In this example, you use the :command:`trove create` command to " "create a new database instance called ``guest2``." msgstr "" #: ../backup_db.rst:115 msgid "" "You specify that the new ``guest2`` instance has the same flavor (``10``) " "and the same root volume size (``2``) as the original ``guest1`` instance." msgstr "" #: ../backup_db.rst:119 msgid "" "You use the :option:`--backup` argument to indicate that this new instance " "is based on the backup artifact identified by ``BACKUP_ID``. In this " "example, replace ``BACKUP_ID`` with ``8af30763-61fd-4aab-8fe8-57d528911138``." msgstr "" #: ../backup_db.rst:142 msgid "**Verify backup**" msgstr "" #: ../backup_db.rst:144 msgid "" "Now check that the new ``guest2`` instance has the same characteristics as " "the original ``guest1`` instance." msgstr "" #: ../backup_db.rst:147 msgid "Start by getting the ID of the new ``guest2`` instance." msgstr "" #: ../backup_db.rst:160 msgid "" "Use the :command:`trove show` command to display information about the new " "guest2 instance. Pass in guest2's ``INSTANCE_ID``, which is ``ac7a2b35-" "a9b4-4ff6-beac-a1bcee86d04b``." msgstr "" #: ../backup_db.rst:184 msgid "" "Note that the data store, flavor ID, and volume size have the same values as " "in the original ``guest1`` instance." msgstr "" #: ../backup_db.rst:187 msgid "" "Use the :command:`trove database-list` command to check that the original " "databases (``db1`` and ``db2``) are present on the restored instance." msgstr "" #: ../backup_db.rst:203 msgid "" "Use the :command:`trove user-list` command to check that the original user " "(``user1``) is present on the restored instance." msgstr "" #: ../backup_db.rst:216 msgid "**Notify users**" msgstr "" #: ../backup_db.rst:218 msgid "" "Tell the users who were accessing the now-disabled ``guest1`` database " "instance that they can now access ``guest2``. Provide them with ``guest2``'s " "name, IP address, and any other information they might need. (You can get " "this information by using the :command:`trove show` command.)" msgstr "" #: ../backup_db.rst:224 msgid "**Clean up**" msgstr "" #: ../backup_db.rst:226 msgid "" "At this point, you might want to delete the disabled ``guest1`` instance, by " "using the :command:`trove delete` command." msgstr "" #: ../backup_db_incremental.rst:3 msgid "Use incremental backups" msgstr "" #: ../backup_db_incremental.rst:5 msgid "" "Incremental backups let you chain together a series of backups. You start " "with a regular backup. Then, when you want to create a subsequent " "incremental backup, you specify the parent backup." msgstr "" #: ../backup_db_incremental.rst:9 msgid "" "Restoring a database instance from an incremental backup is the same as " "creating a database instance from a regular backup—the Database service " "handles the complexities of applying the chain of incremental backups." msgstr "" #: ../backup_db_incremental.rst:13 msgid "" "This example shows you how to use incremental backups with a MySQL database." msgstr "" #: ../backup_db_incremental.rst:16 msgid "" "**Assumptions.** Assume that you have created a regular backup for the " "following database instance:" msgstr "" #: ../backup_db_incremental.rst:19 msgid "Instance name: ``guest1``" msgstr "" #: ../backup_db_incremental.rst:21 msgid "" "ID of the instance (``INSTANCE_ID``): ``792a6a56-278f-4a01-9997-" "d997fa126370``" msgstr "" #: ../backup_db_incremental.rst:24 msgid "" "ID of the regular backup artifact (``BACKUP_ID``): " "``6dc3a9b7-1f3e-4954-8582-3f2e4942cddd``" msgstr "" #: ../backup_db_incremental.rst:28 msgid "Create and use incremental backups" msgstr "" #: ../backup_db_incremental.rst:30 msgid "**Create your first incremental backup**" msgstr "" #: ../backup_db_incremental.rst:32 msgid "Use the :command:`trove backup-create` command and specify:" msgstr "" #: ../backup_db_incremental.rst:34 msgid "" "The ``INSTANCE_ID`` of the database instance you are doing the incremental " "backup for (in this example, ``792a6a56-278f-4a01-9997-d997fa126370``)" msgstr "" #: ../backup_db_incremental.rst:38 msgid "The name of the incremental backup you are creating: ``backup1.1``" msgstr "" #: ../backup_db_incremental.rst:40 msgid "" "The ``BACKUP_ID`` of the parent backup. In this case, the parent is the " "regular backup, with an ID of ``6dc3a9b7-1f3e-4954-8582-3f2e4942cddd``" msgstr "" #: ../backup_db_incremental.rst:63 msgid "" "Note that this command returns both the ID of the database instance you are " "incrementally backing up (``instance_id``) and a new ID for the new " "incremental backup artifact you just created (``id``)." msgstr "" #: ../backup_db_incremental.rst:67 msgid "**Create your second incremental backup**" msgstr "" #: ../backup_db_incremental.rst:69 msgid "" "The name of your second incremental backup is ``backup1.2``. This time, when " "you specify the parent, pass in the ID of the incremental backup you just " "created in the previous step (``backup1.1``). In this example, it is " "``1d474981-a006-4f62-b25f-43d7b8a7097e``." msgstr "" #: ../backup_db_incremental.rst:93 msgid "**Restore using incremental backups**" msgstr "" #: ../backup_db_incremental.rst:95 msgid "" "Now assume that your ``guest1`` database instance is damaged and you need to " "restore it from your incremental backups. In this example, you use the :" "command:`trove create` command to create a new database instance called " "``guest2``." msgstr "" #: ../backup_db_incremental.rst:100 msgid "" "To incorporate your incremental backups, you simply use the :option:`--" "backup` parameter to pass in the ``BACKUP_ID`` of your most recent " "incremental backup. The Database service handles the complexities of " "applying the chain of all previous incremental backups." msgstr "" #: ../cli.rst:3 msgid "OpenStack command-line clients" msgstr "" #: ../cli_access_instance_through_a_console.rst:3 msgid "Access an instance through a console" msgstr "" #: ../cli_access_instance_through_a_console.rst:5 msgid "" "VNC or SPICE is used to view the console output of an instance, regardless " "of whether or not the console log has output. This allows relaying keyboard " "and mouse activity to and from an instance." msgstr "" #: ../cli_access_instance_through_a_console.rst:9 msgid "" "There are three remote console access methods commonly used with OpenStack:" msgstr "" #: ../cli_access_instance_through_a_console.rst:13 msgid "An in-browser VNC client implemented using HTML5 Canvas and WebSockets" msgstr "" #: ../cli_access_instance_through_a_console.rst:14 msgid "novnc" msgstr "" #: ../cli_access_instance_through_a_console.rst:17 msgid "" "A complete in-browser client solution for interaction with virtualized " "instances" msgstr "" #: ../cli_access_instance_through_a_console.rst:18 msgid "spice" msgstr "" #: ../cli_access_instance_through_a_console.rst:21 msgid "A Java client offering console access to an instance" msgstr "" #: ../cli_access_instance_through_a_console.rst:21 msgid "xvpvnc" msgstr "" #: ../cli_access_instance_through_a_console.rst:23 msgid "Example:" msgstr "" #: ../cli_access_instance_through_a_console.rst:25 msgid "" "To access an instance through a remote console, run the following command:" msgstr "" #: ../cli_access_instance_through_a_console.rst:32 msgid "The command returns a URL from which you can access your instance:" msgstr "" #: ../cli_access_instance_through_a_console.rst:42 msgid "" "VNC\\_TYPE can be replaced by any of the above values as connection types." msgstr "" #: ../cli_access_instance_through_a_console.rst:45 msgid "" "When using SPICE to view the console of an instance, a browser plugin can be " "used directly on the instance page, or the :command:`get-vnc-console` " "command can be used with it, as well, by returning a token-authenticated " "address, as in the example above." msgstr "" #: ../cli_access_instance_through_a_console.rst:50 msgid "" "For further information and comparisons (including security considerations), " "see the `Security Guide `__." msgstr "" #: ../cli_ceilometer.rst:3 msgid "Measure cloud resources" msgstr "" #: ../cli_ceilometer.rst:5 msgid "" "Telemetry measures cloud resources in OpenStack. It collects data related to " "billing. Currently, this metering service is available through only the :" "command:`ceilometer` command-line client." msgstr "" #: ../cli_ceilometer.rst:9 msgid "To model data, Telemetry uses the following abstractions:" msgstr "" #: ../cli_ceilometer.rst:12 msgid "" "Measures a specific aspect of resource usage, such as the existence of a " "running instance, or ongoing performance, such as the CPU utilization for an " "instance. Meters exist for each type of resource. For example, a separate " "``cpu_util`` meter exists for each instance. The lifecycle of a meter is " "decoupled from the existence of its related resource. The meter persists " "after the resource goes away." msgstr "" #: ../cli_ceilometer.rst:22 msgid "A meter has the following attributes:" msgstr "" #: ../cli_ceilometer.rst:24 msgid "String name" msgstr "" #: ../cli_ceilometer.rst:26 msgid "A unit of measurement" msgstr "" #: ../cli_ceilometer.rst:28 msgid "" "A type, which indicates whether values increase monotonically (cumulative), " "are interpreted as a change from the previous value (delta), or are stand-" "alone and relate only to the current duration (gauge)" msgstr "" #: ../cli_ceilometer.rst:31 msgid "Meter" msgstr "" #: ../cli_ceilometer.rst:34 msgid "" "An individual data point that is associated with a specific meter. A sample " "has the same attributes as the associated meter, with the addition of time " "stamp and value attributes. The value attribute is also known as the sample " "``volume``." msgstr "" #: ../cli_ceilometer.rst:37 msgid "Sample" msgstr "" #: ../cli_ceilometer.rst:40 msgid "" "A set of data point aggregates over a time duration. (In contrast, a sample " "represents a single data point.) The Telemetry service employs the following " "aggregation functions:" msgstr "" #: ../cli_ceilometer.rst:44 msgid "**count**. The number of samples in each period." msgstr "" #: ../cli_ceilometer.rst:45 msgid "**max**. The maximum number of sample volumes in each period." msgstr "" #: ../cli_ceilometer.rst:46 msgid "**min**. The minimum number of sample volumes in each period." msgstr "" #: ../cli_ceilometer.rst:47 msgid "**avg**. The average of sample volumes over each period." msgstr "" #: ../cli_ceilometer.rst:48 msgid "**sum**. The sum of sample volumes over each period." msgstr "" #: ../cli_ceilometer.rst:48 msgid "Statistic" msgstr "" #: ../cli_ceilometer.rst:51 msgid "" "A set of rules that define a monitor and a current state, with edge-" "triggered actions associated with target states. Alarms provide user-" "oriented Monitoring-as-a-Service and a general purpose utility for " "OpenStack. Orchestration auto scaling is a typical use case. Alarms follow a " "tristate model of ``ok``, ``alarm``, and ``insufficient data``. For " "conventional threshold-oriented alarms, a static threshold value and " "comparison operator govern state transitions. The comparison operator " "compares a selected meter statistic against an evaluation window of " "configurable length into the recent past." msgstr "" #: ../cli_ceilometer.rst:60 msgid "Alarm" msgstr "" #: ../cli_ceilometer.rst:62 msgid "" "This example uses the :command:`heat` client to create an auto-scaling stack " "and the :command:`ceilometer` client to measure resources." msgstr "" #: ../cli_ceilometer.rst:65 msgid "" "Create an auto-scaling stack by running the following command. The :option:`-" "f` option specifies the name of the stack template file, and the :option:`-" "P` option specifies the ``KeyName`` parameter as ``heat_key``:" msgstr "" #: ../cli_ceilometer.rst:74 msgid "List the heat resources that were created:" msgstr "" #: ../cli_ceilometer.rst:94 msgid "List the alarms that are set:" msgstr "" #: ../cli_ceilometer.rst:106 msgid "List the meters that are set:" msgstr "" #: ../cli_ceilometer.rst:119 msgid "List samples:" msgstr "" #: ../cli_ceilometer.rst:130 msgid "View statistics:" msgstr "" #: ../cli_change_the_size_of_your_server.rst:3 msgid "Change the size of your server" msgstr "" #: ../cli_change_the_size_of_your_server.rst:5 msgid "Change the size of a server by changing its flavor." msgstr "" #: ../cli_change_the_size_of_your_server.rst:7 msgid "" "Show information about your server, including its size, which is shown as " "the value of the flavor property:" msgstr "" #: ../cli_change_the_size_of_your_server.rst:44 msgid "The size (flavor) of the server is ``m1.small (2)``." msgstr "" #: ../cli_change_the_size_of_your_server.rst:46 msgid "List the available flavors with the following command:" msgstr "" #: ../cli_change_the_size_of_your_server.rst:61 msgid "" "To resize the server, use the :command:`nova resize` command and add the " "server ID or name and the new flavor. Include the :option:`--poll` parameter " "to display the resize progress. For example:" msgstr "" #: ../cli_change_the_size_of_your_server.rst:74 msgid "" "By default, the :command:`nova resize` command gives the guest operating " "system a chance to perform a controlled shutdown before the instance is " "powered off and the instance is resized. The shutdown behavior is configured " "by the ``shutdown_timeout`` parameter that can be set in the ``nova.conf`` " "file. Its value stands for the overall period (in seconds) a guest operation " "system is allowed to complete the shutdown. The default timeout is 60 " "seconds. See `Description of Compute configuration options `_ for " "details." msgstr "" # #-#-#-#-# cli_change_the_size_of_your_server.pot (End User Guide 1.0.0) #-#-#-#-# # #-#-#-#-# cli_reboot_an_instance.pot (End User Guide 1.0.0) #-#-#-#-# # #-#-#-#-# cli_stop_and_start_an_instance.pot (End User Guide 1.0.0) #-#-#-#-# #: ../cli_change_the_size_of_your_server.rst:86 #: ../cli_reboot_an_instance.rst:58 ../cli_stop_and_start_an_instance.rst:74 msgid "" "The timeout value can be overridden on a per image basis by means of " "``os_shutdown_timeout`` that is an image metadata setting allowing different " "types of operating systems to specify how much time they need to shut down " "cleanly." msgstr "" #: ../cli_change_the_size_of_your_server.rst:91 msgid "Show the status for your server." msgstr "" #: ../cli_change_the_size_of_your_server.rst:102 msgid "When the resize completes, the status becomes VERIFY\\_RESIZE." msgstr "" #: ../cli_change_the_size_of_your_server.rst:104 msgid "Confirm the resize,for example:" msgstr "" #: ../cli_change_the_size_of_your_server.rst:110 #: ../cli_change_the_size_of_your_server.rst:119 msgid "The server status becomes ACTIVE." msgstr "" #: ../cli_change_the_size_of_your_server.rst:112 msgid "" "If the resize fails or does not work as expected, you can revert the resize. " "For example:" msgstr "" #: ../cli_cheat_sheet.rst:3 msgid "OpenStack command-line interface cheat sheet" msgstr "" #: ../cli_cheat_sheet.rst:5 msgid "Here is a list of common commands for reference." msgstr "" #: ../cli_cheat_sheet.rst:8 msgid "Identity (keystone)" msgstr "" #: ../cli_cheat_sheet.rst:10 msgid "List all users" msgstr "" #: ../cli_cheat_sheet.rst:16 msgid "List Identity service catalog" msgstr "" #: ../cli_cheat_sheet.rst:23 msgid "Images (glance)" msgstr "" #: ../cli_cheat_sheet.rst:25 msgid "List images you can access" msgstr "" #: ../cli_cheat_sheet.rst:31 msgid "Delete specified image" msgstr "" #: ../cli_cheat_sheet.rst:37 msgid "Describe a specific image" msgstr "" #: ../cli_cheat_sheet.rst:43 msgid "Update image" msgstr "" #: ../cli_cheat_sheet.rst:49 msgid "Upload kernel image" msgstr "" #: ../cli_cheat_sheet.rst:57 msgid "Upload RAM image" msgstr "" #: ../cli_cheat_sheet.rst:65 msgid "Upload three-part image" msgstr "" #: ../cli_cheat_sheet.rst:74 msgid "Register raw image" msgstr "" #: ../cli_cheat_sheet.rst:83 msgid "Compute (nova)" msgstr "" #: ../cli_cheat_sheet.rst:85 msgid "List instances, check status of instance" msgstr "" # #-#-#-#-# cli_cheat_sheet.pot (End User Guide 1.0.0) #-#-#-#-# # #-#-#-#-# sdk_manage_images.pot (End User Guide 1.0.0) #-#-#-#-# #: ../cli_cheat_sheet.rst:91 ../sdk_manage_images.rst:11 msgid "List images" msgstr "" #: ../cli_cheat_sheet.rst:97 msgid "List flavors" msgstr "" #: ../cli_cheat_sheet.rst:103 msgid "Boot an instance using flavor and image names (if names are unique)" msgstr "" #: ../cli_cheat_sheet.rst:111 msgid "Login to instance" msgstr "" #: ../cli_cheat_sheet.rst:122 msgid "" "In CirrOS the password for user ``cirros`` is \"cubswin:)\" without the " "quotes." msgstr "" #: ../cli_cheat_sheet.rst:125 msgid "Show details of instance" msgstr "" #: ../cli_cheat_sheet.rst:132 msgid "View console log of instance" msgstr "" #: ../cli_cheat_sheet.rst:138 msgid "Set metadata on an instance" msgstr "" # #-#-#-#-# cli_cheat_sheet.pot (End User Guide 1.0.0) #-#-#-#-# # #-#-#-#-# dashboard_launch_instances.pot (End User Guide 1.0.0) #-#-#-#-# #: ../cli_cheat_sheet.rst:144 ../dashboard_launch_instances.rst:246 msgid "Create an instance snapshot" msgstr "" #: ../cli_cheat_sheet.rst:152 msgid "Pause, suspend, stop, rescue, resize, rebuild, reboot an instance" msgstr "" #: ../cli_cheat_sheet.rst:154 msgid "Pause" msgstr "" #: ../cli_cheat_sheet.rst:161 msgid "Unpause" msgstr "" #: ../cli_cheat_sheet.rst:167 msgid "Suspend" msgstr "" #: ../cli_cheat_sheet.rst:173 msgid "Unsuspend" msgstr "" #: ../cli_cheat_sheet.rst:179 msgid "Stop" msgstr "" #: ../cli_cheat_sheet.rst:185 msgid "Start" msgstr "" #: ../cli_cheat_sheet.rst:191 msgid "Rescue" msgstr "" #: ../cli_cheat_sheet.rst:198 msgid "Resize" msgstr "" #: ../cli_cheat_sheet.rst:206 msgid "Rebuild" msgstr "" #: ../cli_cheat_sheet.rst:213 msgid "Reboot" msgstr "" #: ../cli_cheat_sheet.rst:220 msgid "Inject user data and files into an instance" msgstr "" #: ../cli_cheat_sheet.rst:228 msgid "" "To validate that the file was injected, use ssh to connect to the instance, " "and look in ``/var/lib/cloud`` for the file." msgstr "" #: ../cli_cheat_sheet.rst:231 msgid "" "Inject a keypair into an instance and access the instance with that keypair" msgstr "" #: ../cli_cheat_sheet.rst:234 msgid "Create keypair" msgstr "" #: ../cli_cheat_sheet.rst:241 msgid "Start an instance (boot)" msgstr "" #: ../cli_cheat_sheet.rst:248 msgid "Use ssh to connect to the instance" msgstr "" #: ../cli_cheat_sheet.rst:255 msgid "Manage security groups" msgstr "" #: ../cli_cheat_sheet.rst:257 msgid "" "Add rules to default security group allowing ping and SSH between instances " "in the default security group" msgstr "" #: ../cli_cheat_sheet.rst:266 msgid "Networking (neutron)" msgstr "" # #-#-#-#-# cli_cheat_sheet.pot (End User Guide 1.0.0) #-#-#-#-# # #-#-#-#-# sdk_neutron_apis.pot (End User Guide 1.0.0) #-#-#-#-# #: ../cli_cheat_sheet.rst:268 ../sdk_neutron_apis.rst:124 msgid "Create network" msgstr "" #: ../cli_cheat_sheet.rst:274 msgid "Create a subnet" msgstr "" #: ../cli_cheat_sheet.rst:282 msgid "Block Storage (cinder)" msgstr "" #: ../cli_cheat_sheet.rst:284 msgid "Used to manage volumes and volume snapshots that attach to instances." msgstr "" #: ../cli_cheat_sheet.rst:286 msgid "Create a new volume" msgstr "" #: ../cli_cheat_sheet.rst:293 msgid "Boot an instance and attach to volume" msgstr "" #: ../cli_cheat_sheet.rst:299 msgid "List volumes, notice status of volume" msgstr "" #: ../cli_cheat_sheet.rst:305 msgid "" "Attach volume to instance after instance is active, and volume is available" msgstr "" #: ../cli_cheat_sheet.rst:315 msgid "" "On the Xen Hypervisor it is possible to provide a specific device name " "instead of automatic allocation. For example:" msgstr "" #: ../cli_cheat_sheet.rst:322 msgid "" "This is not currently possible when using non-Xen hypervisors with OpenStack." msgstr "" #: ../cli_cheat_sheet.rst:324 msgid "Manage volumes after login into the instance" msgstr "" #: ../cli_cheat_sheet.rst:326 msgid "List storage devices" msgstr "" #: ../cli_cheat_sheet.rst:332 msgid "Make filesystem on volume" msgstr "" #: ../cli_cheat_sheet.rst:338 msgid "Create a mountpoint" msgstr "" #: ../cli_cheat_sheet.rst:344 msgid "Mount the volume at the mountpoint" msgstr "" #: ../cli_cheat_sheet.rst:350 msgid "Create a file on the volume" msgstr "" #: ../cli_cheat_sheet.rst:357 msgid "Unmount the volume" msgstr "" #: ../cli_cheat_sheet.rst:364 msgid "Object Storage (swift)" msgstr "" #: ../cli_cheat_sheet.rst:366 msgid "Display information for the account, container, or object" msgstr "" #: ../cli_cheat_sheet.rst:375 msgid "List containers" msgstr "" #: ../cli_config_drive.rst:3 msgid "Store metadata on a configuration drive" msgstr "" #: ../cli_config_drive.rst:4 msgid "" "You can configure OpenStack to write metadata to a special configuration " "drive that attaches to the instance when it boots. The instance can mount " "this drive and read files from it to get information that is normally " "available through the `metadata service `__. This metadata is " "different from the user data." msgstr "" #: ../cli_config_drive.rst:10 msgid "" "One use case for using the configuration drive is to pass a networking " "configuration when you do not use DHCP to assign IP addresses to instances. " "For example, you might pass the IP address configuration for the instance " "through the configuration drive, which the instance can mount and access " "before you configure the network settings for the instance." msgstr "" #: ../cli_config_drive.rst:17 msgid "" "Any modern guest operating system that is capable of mounting an ISO 9660 or " "VFAT file system can use the configuration drive." msgstr "" #: ../cli_config_drive.rst:21 msgid "Requirements and guidelines" msgstr "" #: ../cli_config_drive.rst:23 msgid "" "To use the configuration drive, you must follow the following requirements " "for the compute host and image." msgstr "" #: ../cli_config_drive.rst:26 msgid "**Compute host requirements**" msgstr "" #: ../cli_config_drive.rst:28 msgid "" "The following hypervisors support the configuration drive: libvirt, " "XenServer, Hyper-V, and VMware." msgstr "" #: ../cli_config_drive.rst:31 msgid "Also, the Bare Metal service supports the configuration drive." msgstr "" #: ../cli_config_drive.rst:33 msgid "" "To use configuration drive with libvirt, XenServer, or VMware, you must " "first install the genisoimage package on each compute host. Otherwise, " "instances do not boot properly." msgstr "" #: ../cli_config_drive.rst:37 msgid "" "Use the ``mkisofs_cmd`` flag to set the path where you install the " "genisoimage program. If genisoimage is in same path as the ``nova-compute`` " "service, you do not need to set this flag." msgstr "" #: ../cli_config_drive.rst:41 msgid "" "To use configuration drive with Hyper-V, you must set the ``mkisofs_cmd`` " "value to the full path to an ``mkisofs.exe`` installation. Additionally, you " "must set the ``qemu_img_cmd`` value in the ``hyperv`` configuration section " "to the full path to an :command:`qemu-img` command installation." msgstr "" #: ../cli_config_drive.rst:47 msgid "" "To use configuration drive with the Bare Metal service, you do not need to " "prepare anything because the Bare Metal service treats the configuration " "drive properly." msgstr "" #: ../cli_config_drive.rst:51 msgid "**Image requirements**" msgstr "" #: ../cli_config_drive.rst:53 msgid "" "An image built with a recent version of the cloud-init package can " "automatically access metadata passed through the configuration drive. The " "cloud-init package version 0.7.1 works with Ubuntu, Fedora based images " "(such as Red Hat Enterprise Linux) and openSUSE based images (such as SUSE " "Linux Enterprise Server)." msgstr "" #: ../cli_config_drive.rst:59 msgid "" "If an image does not have the cloud-init package installed, you must " "customize the image to run a script that mounts the configuration drive on " "boot, reads the data from the drive, and takes appropriate action such as " "adding the public key to an account. You can read more details about how " "data is organized on the configuration drive." msgstr "" #: ../cli_config_drive.rst:65 msgid "" "If you use Xen with a configuration drive, use the ``xenapi_disable_agent`` " "configuration parameter to disable the agent." msgstr "" #: ../cli_config_drive.rst:69 msgid "**Guidelines**" msgstr "" #: ../cli_config_drive.rst:71 msgid "" "Do not rely on the presence of the EC2 metadata in the configuration drive, " "because this content might be removed in a future release. For example, do " "not rely on files in the ``ec2`` directory." msgstr "" #: ../cli_config_drive.rst:75 msgid "" "When you create images that access configuration drive data and multiple " "directories are under the ``openstack`` directory, always select the highest " "API version by date that your consumer supports. For example, if your guest " "image supports the 2012-03-05, 2012-08-05, and 2013-04-13 versions, try " "2013-04-13 first and fall back to a previous version if 2013-04-13 is not " "present." msgstr "" #: ../cli_config_drive.rst:83 msgid "Enable and access the configuration drive" msgstr "" #: ../cli_config_drive.rst:85 msgid "" "To enable the configuration drive, pass the ``--config-drive true`` " "parameter to the :command:`nova boot` command." msgstr "" #: ../cli_config_drive.rst:88 msgid "" "The following example enables the configuration drive and passes user data, " "two files, and two key/value metadata pairs, all of which are accessible " "from the configuration drive:" msgstr "" #: ../cli_config_drive.rst:100 msgid "" "You can also configure the Compute service to always create a configuration " "drive by setting the following option in the ``/etc/nova/nova.conf`` file:" msgstr "" #: ../cli_config_drive.rst:110 msgid "" "If a user passes the ``--config-drive true`` flag to the :command:`nova " "boot` command, an administrator cannot disable the configuration drive." msgstr "" #: ../cli_config_drive.rst:114 msgid "" "If your guest operating system supports accessing disk by label, you can " "mount the configuration drive as the ``/dev/disk/by-label/" "configurationDriveVolumeLabel`` device. In the following example, the " "configuration drive has the ``config-2`` volume label:" msgstr "" #: ../cli_config_drive.rst:127 msgid "" "Ensure that you use at least version 0.3.1 of CirrOS for configuration drive " "support." msgstr "" #: ../cli_config_drive.rst:130 msgid "" "If your guest operating system does not use ``udev``, the ``/dev/disk/by-" "label`` directory is not present." msgstr "" #: ../cli_config_drive.rst:133 msgid "" "You can use the :command:`blkid` command to identify the block device that " "corresponds to the configuration drive. For example, when you boot the " "CirrOS image with the ``m1.tiny`` flavor, the device is ``/dev/vdb``:" msgstr "" #: ../cli_config_drive.rst:146 msgid "Once identified, you can mount the device:" msgstr "" #: ../cli_config_drive.rst:154 msgid "Configuration drive contents" msgstr "" #: ../cli_config_drive.rst:156 msgid "" "In this example, the contents of the configuration drive are as follows::" msgstr "" #: ../cli_config_drive.rst:170 msgid "" "The files that appear on the configuration drive depend on the arguments " "that you pass to the :command:`nova boot` command." msgstr "" #: ../cli_config_drive.rst:174 msgid "OpenStack metadata format" msgstr "" #: ../cli_config_drive.rst:176 msgid "" "The following example shows the contents of the ``openstack/2012-08-10/" "meta_data.json`` and ``openstack/latest/meta_data.json`` files. These files " "are identical. The file contents are formatted for readability." msgstr "" #: ../cli_config_drive.rst:208 msgid "" "Note the effect of the ``--file /etc/network/interfaces=/home/myuser/" "instance-interfaces`` argument that was passed to the :command:`nova boot` " "command. The contents of this file are contained in the ``openstack/" "content/0000`` file on the configuration drive, and the path is specified as " "``/etc/network/interfaces`` in the ``meta_data.json`` file." msgstr "" #: ../cli_config_drive.rst:216 msgid "EC2 metadata format" msgstr "" #: ../cli_config_drive.rst:218 msgid "" "The following example shows the contents of the ``ec2/2009-04-04/meta-data." "json`` and the ``ec2/latest/meta-data.json`` files. These files are " "identical. The file contents are formatted to improve readability." msgstr "" #: ../cli_config_drive.rst:260 msgid "User data" msgstr "" #: ../cli_config_drive.rst:262 msgid "" "The ``openstack/2012-08-10/user_data``, ``openstack/latest/user_data``, " "``ec2/2009-04-04/user-data``, and ``ec2/latest/user-data`` file are present " "only if the ``--user-data`` flag and the contents of the user data file are " "passed to the :command:`nova boot` command." msgstr "" #: ../cli_config_drive.rst:268 msgid "Configuration drive format" msgstr "" #: ../cli_config_drive.rst:270 msgid "" "The default format of the configuration drive as an ISO 9660 file system. To " "explicitly specify the ISO 9660 format, add the following line to the ``/etc/" "nova/nova.conf`` file:" msgstr "" #: ../cli_config_drive.rst:278 msgid "" "By default, you cannot attach the configuration drive image as a CD drive " "instead of as a disk drive. To attach a CD drive, add the following line to " "the ``/etc/nova/nova.conf`` file:" msgstr "" #: ../cli_config_drive.rst:286 msgid "" "For legacy reasons, you can configure the configuration drive to use VFAT " "format instead of ISO 9660. It is unlikely that you would require VFAT " "format because ISO 9660 is widely supported across operating systems. " "However, to use the VFAT format, add the following line to the ``/etc/nova/" "nova.conf`` file:" msgstr "" #: ../cli_config_drive.rst:296 msgid "If you choose VFAT, the configuration drive is 64 MB." msgstr "" #: ../cli_config_drive.rst:300 msgid "" "In current version (Liberty) of OpenStack Compute, live migration with " "``config_drive`` on local disk is forbidden due to the bug in libvirt of " "copying a read-only disk. However, if we use VFAT as the format of " "``config_drive``, the function of live migration works well." msgstr "" # #-#-#-#-# cli_create_and_manage_networks.pot (End User Guide 1.0.0) #-#-#-#-# # #-#-#-#-# dashboard_create_networks.pot (End User Guide 1.0.0) #-#-#-#-# #: ../cli_create_and_manage_networks.rst:3 ../dashboard_create_networks.rst:3 msgid "Create and manage networks" msgstr "" #: ../cli_create_and_manage_networks.rst:5 msgid "Before you run commands, set the following environment variables:" msgstr "" #: ../cli_create_and_manage_networks.rst:15 msgid "Create networks" msgstr "" #: ../cli_create_and_manage_networks.rst:17 msgid "List the extensions of the system:" msgstr "" #: ../cli_create_and_manage_networks.rst:36 msgid "Create a network:" msgstr "" #: ../cli_create_and_manage_networks.rst:61 msgid "Some fields of the created network are invisible to non-admin users." msgstr "" #: ../cli_create_and_manage_networks.rst:63 msgid "Create a network with specified provider network type." msgstr "" #: ../cli_create_and_manage_networks.rst:86 msgid "" "Just as shown previously, the unknown option ``--provider:network-type`` is " "used to create a ``local`` provider network." msgstr "" #: ../cli_create_and_manage_networks.rst:90 msgid "Create subnets" msgstr "" #: ../cli_create_and_manage_networks.rst:92 msgid "Create a subnet:" msgstr "" #: ../cli_create_and_manage_networks.rst:115 msgid "" "The ``subnet-create`` command has the following positional and optional " "parameters:" msgstr "" #: ../cli_create_and_manage_networks.rst:118 msgid "The name or ID of the network to which the subnet belongs." msgstr "" #: ../cli_create_and_manage_networks.rst:120 msgid "" "In this example, ``net1`` is a positional argument that specifies the " "network name." msgstr "" #: ../cli_create_and_manage_networks.rst:123 msgid "The CIDR of the subnet." msgstr "" #: ../cli_create_and_manage_networks.rst:125 msgid "" "In this example, ``192.168.2.0/24`` is a positional argument that specifies " "the CIDR." msgstr "" #: ../cli_create_and_manage_networks.rst:128 msgid "The subnet name, which is optional." msgstr "" #: ../cli_create_and_manage_networks.rst:130 msgid "In this example, ``--name subnet1`` specifies the name of the subnet." msgstr "" #: ../cli_create_and_manage_networks.rst:133 msgid "" "For information and examples on more advanced use of neutron's ``subnet`` " "subcommand, see the `OpenStack Administrator Guide `__." msgstr "" #: ../cli_create_and_manage_networks.rst:138 msgid "Create routers" msgstr "" #: ../cli_create_and_manage_networks.rst:140 msgid "Create a router:" msgstr "" #: ../cli_create_and_manage_networks.rst:158 msgid "" "Take note of the unique router identifier returned, this will be required in " "subsequent steps." msgstr "" #: ../cli_create_and_manage_networks.rst:161 msgid "Link the router to the external provider network:" msgstr "" #: ../cli_create_and_manage_networks.rst:167 msgid "" "Replace ROUTER with the unique identifier of the router, replace NETWORK " "with the unique identifier of the external provider network." msgstr "" #: ../cli_create_and_manage_networks.rst:170 msgid "Link the router to the subnet:" msgstr "" #: ../cli_create_and_manage_networks.rst:176 msgid "" "Replace ROUTER with the unique identifier of the router, replace SUBNET with " "the unique identifier of the subnet." msgstr "" # #-#-#-#-# cli_create_and_manage_networks.pot (End User Guide 1.0.0) #-#-#-#-# # #-#-#-#-# sdk_neutron_apis.pot (End User Guide 1.0.0) #-#-#-#-# #: ../cli_create_and_manage_networks.rst:180 ../sdk_neutron_apis.rst:179 msgid "Create ports" msgstr "" #: ../cli_create_and_manage_networks.rst:182 msgid "Create a port with specified IP address:" msgstr "" #: ../cli_create_and_manage_networks.rst:206 msgid "" "In the previous command, ``net1`` is the network name, which is a positional " "argument. :option:`--fixed-ip ip_address=192.168.2.40` is an option which " "specifies the port's fixed IP address we wanted." msgstr "" #: ../cli_create_and_manage_networks.rst:212 msgid "" "When creating a port, you can specify any unallocated IP in the subnet even " "if the address is not in a pre-defined pool of allocated IP addresses (set " "by your cloud provider)." msgstr "" #: ../cli_create_and_manage_networks.rst:216 msgid "Create a port without specified IP address:" msgstr "" #: ../cli_create_and_manage_networks.rst:242 msgid "" "Note that the system allocates one IP address if you do not specify an IP " "address in the :command:`neutron port-create` command." msgstr "" #: ../cli_create_and_manage_networks.rst:245 msgid "Query ports with specified fixed IP addresses:" msgstr "" #: ../cli_create_and_manage_networks.rst:259 msgid "" ":option:`--fixed-ips ip_address=192.168.2.2 ip_address=192.168.2.40` is one " "unknown option." msgstr "" #: ../cli_create_and_manage_networks.rst:262 msgid "" "**How to find unknown options** The unknown options can be easily found by " "watching the output of :command:`create_xxx` or :command:`show_xxx` command. " "For example, in the port creation command, we see the fixed\\_ips fields, " "which can be used as an unknown option." msgstr "" #: ../cli_create_and_manage_stacks.rst:3 msgid "Create and manage stacks" msgstr "" #: ../cli_create_and_manage_stacks.rst:5 msgid "" "The Orchestration service enables you to orchestrate multiple composite " "cloud applications. This service supports use of both the Amazon Web " "Services (AWS) CloudFormation template format through both a Query API that " "is compatible with CloudFormation and the native OpenStack :term:`Heat " "Orchestration Template (HOT)` format through a REST API." msgstr "" #: ../cli_create_and_manage_stacks.rst:11 msgid "" "These flexible template languages enable application developers to describe " "and automate the deployment of infrastructure, services, and applications. " "The templates enable creation of most OpenStack resource types, such as " "instances, floating IP addresses, volumes, security groups, and users. The " "resources, once created, are referred to as stacks." msgstr "" #: ../cli_create_and_manage_stacks.rst:18 msgid "" "The template languages are described in the `Template Guide `__ in the `Heat " "developer documentation `__." msgstr "" #: ../cli_create_and_manage_stacks.rst:24 msgid "Create a stack from an example template file" msgstr "" #: ../cli_create_and_manage_stacks.rst:26 msgid "" "To create a stack, or template, from an `example template file `__, run the following command:" msgstr "" #: ../cli_create_and_manage_stacks.rst:35 msgid "" "The :option:`--parameters` values that you specify depend on the parameters " "that are defined in the template. If a website hosts the template file, you " "can specify the URL with the :option:`--template-url` parameter instead of " "the :option:`--template-file` parameter." msgstr "" #: ../cli_create_and_manage_stacks.rst:40 msgid "The command returns the following output:" msgstr "" #: ../cli_create_and_manage_stacks.rst:52 msgid "" "When you run the :command:`heat stack-create` command with the :option:`--" "poll` option, it prints the :command:`heat stack-show` output first, and " "then continuously prints the events in log format until the stack completes " "its action with success or failure." msgstr "" #: ../cli_create_and_manage_stacks.rst:57 msgid "" "You can also use the :command:`template-validate` command to validate a " "template file without creating a stack from it." msgstr "" #: ../cli_create_and_manage_stacks.rst:62 msgid "" "Previous versions of the heat client used :command:`validate` instead of :" "command:`template-validate`, but it has been deprecated in favor of :command:" "`template-validate`." msgstr "" #: ../cli_create_and_manage_stacks.rst:66 msgid "To do so, run the following command:" msgstr "" #: ../cli_create_and_manage_stacks.rst:72 msgid "If validation fails, the response returns an error message." msgstr "" #: ../cli_create_and_manage_stacks.rst:75 msgid "Get information about stacks" msgstr "" #: ../cli_create_and_manage_stacks.rst:77 msgid "" "To explore the state and history of a particular stack, you can run a number " "of commands." msgstr "" #: ../cli_create_and_manage_stacks.rst:80 msgid "" "To see which stacks are visible to the current user, run the following " "command:" msgstr "" #: ../cli_create_and_manage_stacks.rst:93 msgid "To show the details of a stack, run the following command:" msgstr "" #: ../cli_create_and_manage_stacks.rst:99 msgid "" "A stack consists of a collection of resources. To list the resources and " "their status, run the following command:" msgstr "" #: ../cli_create_and_manage_stacks.rst:111 msgid "" "To show the details for a specific resource in a stack, run the following " "command:" msgstr "" #: ../cli_create_and_manage_stacks.rst:118 msgid "" "Some resources have associated metadata which can change throughout the " "lifecycle of a resource. Show the metadata by running the following command:" msgstr "" #: ../cli_create_and_manage_stacks.rst:126 msgid "" "A series of events is generated during the lifecycle of a stack. To display " "lifecycle events, run the following command:" msgstr "" #: ../cli_create_and_manage_stacks.rst:139 msgid "To show the details for a particular event, run the following command:" msgstr "" #: ../cli_create_and_manage_stacks.rst:147 msgid "Update a stack" msgstr "" #: ../cli_create_and_manage_stacks.rst:149 msgid "" "To update an existing stack from a modified template file, run a command " "like the following command:" msgstr "" #: ../cli_create_and_manage_stacks.rst:164 msgid "" "Some resources are updated in-place, while others are replaced with new " "resources." msgstr "" #: ../cli_delete_an_instance.rst:3 msgid "Delete an instance" msgstr "" #: ../cli_delete_an_instance.rst:5 msgid "When you no longer need an instance, you can delete it." msgstr "" #: ../cli_delete_an_instance.rst:7 msgid "List all instances:" msgstr "" #: ../cli_delete_an_instance.rst:20 msgid "" "Run the :command:`nova delete` command to delete the instance. The following " "example shows deletion of the ``newServer`` instance, which is in ``ERROR`` " "state:" msgstr "" #: ../cli_delete_an_instance.rst:28 msgid "The command does not notify that your server was deleted." msgstr "" #: ../cli_delete_an_instance.rst:30 msgid "" "To verify that the server was deleted, run the :command:`nova list` command:" msgstr "" #: ../cli_delete_an_instance.rst:43 msgid "The deleted instance does not appear in the list." msgstr "" #: ../cli_launch_instances.rst:3 msgid "Launch instances" msgstr "" #: ../cli_launch_instances.rst:5 msgid "Instances are virtual machines that run inside the cloud." msgstr "" #: ../cli_launch_instances.rst:7 msgid "Before you can launch an instance, gather the following parameters:" msgstr "" #: ../cli_launch_instances.rst:9 msgid "" "The **instance source** can be an image, snapshot, or block storage volume " "that contains an image or snapshot." msgstr "" #: ../cli_launch_instances.rst:12 msgid "A **name** for your instance." msgstr "" #: ../cli_launch_instances.rst:14 msgid "" "The **flavor** for your instance, which defines the compute, memory, and " "storage capacity of nova computing instances. A flavor is an available " "hardware configuration for a server. It defines the size of a virtual server " "that can be launched." msgstr "" #: ../cli_launch_instances.rst:19 msgid "" "Any **user data** files. A user data file is a special key in the metadata " "service that holds a file that cloud-aware applications in the guest " "instance can access. For example, one application that uses user data is the " "`cloud-init `__ system, which " "is an open-source package from Ubuntu that is available on various Linux " "distributions and that handles early initialization of a cloud instance." msgstr "" #: ../cli_launch_instances.rst:28 msgid "" "Access and security credentials, which include one or both of the following " "credentials:" msgstr "" #: ../cli_launch_instances.rst:31 msgid "" "A **key pair** for your instance, which are SSH credentials that are " "injected into images when they are launched. For the key pair to be " "successfully injected, the image must contain the ``cloud-init`` package. " "Create at least one key pair for each project. If you already have generated " "a key pair with an external tool, you can import it into OpenStack. You can " "use the key pair for multiple instances that belong to that project." msgstr "" #: ../cli_launch_instances.rst:39 msgid "" "A **security group** that defines which incoming network traffic is " "forwarded to instances. Security groups hold a set of firewall policies, " "known as *security group rules*." msgstr "" #: ../cli_launch_instances.rst:43 msgid "" "If needed, you can assign a **floating (public) IP address** to a running " "instance." msgstr "" #: ../cli_launch_instances.rst:46 msgid "" "You can also attach a block storage device, or **volume**, for persistent " "storage." msgstr "" # #-#-#-#-# cli_launch_instances.pot (End User Guide 1.0.0) #-#-#-#-# # #-#-#-#-# cli_nova_configure_access_security_for_instances.pot (End User Guide 1.0.0) #-#-#-#-# #: ../cli_launch_instances.rst:51 #: ../cli_nova_configure_access_security_for_instances.rst:57 msgid "" "Instances that use the default security group cannot, by default, be " "accessed from any IP address outside of the cloud. If you want those IP " "addresses to access the instances, you must modify the rules for the default " "security group." msgstr "" # #-#-#-#-# cli_launch_instances.pot (End User Guide 1.0.0) #-#-#-#-# # #-#-#-#-# cli_nova_configure_access_security_for_instances.pot (End User Guide 1.0.0) #-#-#-#-# #: ../cli_launch_instances.rst:56 #: ../cli_nova_configure_access_security_for_instances.rst:62 msgid "" "You can also assign a floating IP address to a running instance to make it " "accessible from outside the cloud. See :doc:`cli_manage_ip_addresses`." msgstr "" #: ../cli_launch_instances.rst:60 msgid "" "After you gather the parameters that you need to launch an instance, you can " "launch it from an :doc:`image` or a :" "doc:`volume`. You can launch an " "instance directly from one of the available OpenStack images or from an " "image that you have copied to a persistent volume. The OpenStack Image " "service provides a pool of images that are accessible to members of " "different projects." msgstr "" #: ../cli_launch_instances.rst:69 msgid "Gather parameters to launch an instance" msgstr "" #: ../cli_launch_instances.rst:71 msgid "Before you begin, source the OpenStack RC file." msgstr "" # #-#-#-#-# cli_launch_instances.pot (End User Guide 1.0.0) #-#-#-#-# # #-#-#-#-# cli_nova_launch_instance_from_volume.pot (End User Guide 1.0.0) #-#-#-#-# #: ../cli_launch_instances.rst:73 #: ../cli_nova_launch_instance_from_volume.rst:184 msgid "List the available flavors." msgstr "" #: ../cli_launch_instances.rst:79 msgid "Note the ID of the flavor that you want to use for your instance::" msgstr "" # #-#-#-#-# cli_launch_instances.pot (End User Guide 1.0.0) #-#-#-#-# # #-#-#-#-# cli_nova_launch_instance_from_volume.pot (End User Guide 1.0.0) #-#-#-#-# #: ../cli_launch_instances.rst:91 #: ../cli_nova_launch_instance_from_volume.rst:143 msgid "List the available images." msgstr "" #: ../cli_launch_instances.rst:97 msgid "Note the ID of the image from which you want to boot your instance::" msgstr "" #: ../cli_launch_instances.rst:107 msgid "" "You can also filter the image list by using :command:`grep` to find a " "specific image, as follows:" msgstr "" #: ../cli_launch_instances.rst:116 msgid "List the available security groups." msgstr "" #: ../cli_launch_instances.rst:124 msgid "" "If you are an admin user, specify the :option:`--all-tenants` parameter to " "list groups for all tenants." msgstr "" #: ../cli_launch_instances.rst:129 msgid "" "Note the ID of the security group that you want to use for your instance::" msgstr "" #: ../cli_launch_instances.rst:139 msgid "" "If you have not created any security groups, you can assign the instance to " "only the default security group." msgstr "" #: ../cli_launch_instances.rst:142 msgid "You can view rules for a specified security group:" msgstr "" #: ../cli_launch_instances.rst:148 msgid "" "List the available key pairs, and note the key pair name that you use for " "SSH access." msgstr "" # #-#-#-#-# cli_launch_instances.pot (End User Guide 1.0.0) #-#-#-#-# # #-#-#-#-# dashboard_launch_instances.pot (End User Guide 1.0.0) #-#-#-#-# #: ../cli_launch_instances.rst:156 ../dashboard_launch_instances.rst:17 msgid "Launch an instance" msgstr "" #: ../cli_launch_instances.rst:158 msgid "You can launch an instance from various sources." msgstr "" #: ../cli_manage_bare_metal_nodes.rst:3 msgid "Manage bare-metal nodes" msgstr "" #: ../cli_manage_bare_metal_nodes.rst:5 msgid "" "The bare-metal driver for OpenStack Compute manages provisioning of physical " "hardware by using common cloud APIs and tools such as Orchestration (Heat). " "The use case for this driver is for single tenant clouds such as a high-" "performance computing cluster, or for deploying OpenStack itself." msgstr "" #: ../cli_manage_bare_metal_nodes.rst:11 msgid "" "If you use the bare-metal driver, you must create a network interface and " "add it to a bare-metal node. Then, you can launch an instance from a bare-" "metal image." msgstr "" #: ../cli_manage_bare_metal_nodes.rst:15 msgid "" "You can list and delete bare-metal nodes. When you delete a node, any " "associated network interfaces are removed. You can list and remove network " "interfaces that are associated with a bare-metal node." msgstr "" #: ../cli_manage_bare_metal_nodes.rst:20 msgid "Commands" msgstr "" #: ../cli_manage_bare_metal_nodes.rst:22 msgid "The following commands can be used to manage bare-metal nodes." msgstr "" #: ../cli_manage_bare_metal_nodes.rst:25 msgid "Adds a network interface to a bare-metal node." msgstr "" #: ../cli_manage_bare_metal_nodes.rst:25 msgid "``baremetal-interface-add``" msgstr "" #: ../cli_manage_bare_metal_nodes.rst:28 msgid "Lists network interfaces associated with a bare-metal node." msgstr "" #: ../cli_manage_bare_metal_nodes.rst:28 msgid "``baremetal-interface-list``" msgstr "" #: ../cli_manage_bare_metal_nodes.rst:31 msgid "Removes a network interface from a bare-metal node." msgstr "" #: ../cli_manage_bare_metal_nodes.rst:31 msgid "``baremetal-interface-remove``" msgstr "" #: ../cli_manage_bare_metal_nodes.rst:34 msgid "Creates a bare-metal node." msgstr "" #: ../cli_manage_bare_metal_nodes.rst:34 msgid "``baremetal-node-create``" msgstr "" #: ../cli_manage_bare_metal_nodes.rst:37 msgid "Removes a bare-metal node and any associated interfaces." msgstr "" #: ../cli_manage_bare_metal_nodes.rst:37 msgid "``baremetal-node-delete``" msgstr "" #: ../cli_manage_bare_metal_nodes.rst:40 msgid "Lists available bare-metal nodes." msgstr "" #: ../cli_manage_bare_metal_nodes.rst:40 msgid "``baremetal-node-list``" msgstr "" #: ../cli_manage_bare_metal_nodes.rst:43 msgid "Shows information about a bare-metal node." msgstr "" #: ../cli_manage_bare_metal_nodes.rst:43 msgid "``baremetal-node-show``" msgstr "" #: ../cli_manage_bare_metal_nodes.rst:46 msgid "Create a bare-metal node" msgstr "" #: ../cli_manage_bare_metal_nodes.rst:48 msgid "" "When you create a bare-metal node, your PM address, user name, and password " "should match the information in your hardware's BIOS/IPMI configuration." msgstr "" #: ../cli_manage_bare_metal_nodes.rst:57 msgid "" "The following example shows the command and results from creating a node " "with the PM address ``1.2.3.4``, the PM user name ipmi, and password " "``ipmi``." msgstr "" #: ../cli_manage_bare_metal_nodes.rst:83 msgid "Add a network interface to the node" msgstr "" #: ../cli_manage_bare_metal_nodes.rst:85 msgid "" "For each NIC on the node, you must create an interface, specifying the " "interface's MAC address." msgstr "" #: ../cli_manage_bare_metal_nodes.rst:101 msgid "Launch an instance from a bare-metal image" msgstr "" #: ../cli_manage_bare_metal_nodes.rst:103 msgid "" "A bare-metal instance is an instance created directly on a physical machine, " "without any virtualization layer running underneath it. Nova retains power " "control via IPMI. In some situations, Nova may retain network control via " "Neutron and OpenFlow." msgstr "" #: ../cli_manage_bare_metal_nodes.rst:122 msgid "" "Set the ``--availability_zone`` parameter to specify which zone or node to " "use to start the server. Separate the zone from the host name with a comma. " "For example:" msgstr "" #: ../cli_manage_bare_metal_nodes.rst:130 msgid "" "``host`` is optional for the ``--availability_zone`` parameter. You can " "simply specify ``zone:,node``, still including the comma." msgstr "" #: ../cli_manage_bare_metal_nodes.rst:134 msgid "List bare-metal nodes and interfaces" msgstr "" #: ../cli_manage_bare_metal_nodes.rst:136 msgid "" "Use the :command:`nova baremetal-node-list` command to view all bare-metal " "nodes and interfaces. When a node is in use, its status includes the UUID of " "the instance that runs on it:" msgstr "" #: ../cli_manage_bare_metal_nodes.rst:150 msgid "Show details for a bare-metal node" msgstr "" #: ../cli_manage_bare_metal_nodes.rst:152 msgid "" "Use the :command:`nova baremetal-node-show` command to view the details for " "a bare-metal node:" msgstr "" #: ../cli_manage_images_curl.rst:3 msgid "Manage images using cURL" msgstr "" #: ../cli_manage_images_curl.rst:5 msgid "" "This section is intended to provide a series of commands a typical client of " "the API might use to create and modify an image." msgstr "" #: ../cli_manage_images_curl.rst:8 msgid "" "These commands assume the implementation of the v2 Images API using the " "Identity Service for authentication and authorization. The X-Auth-Token " "header is used to provide the authentication token issued by the Identity " "Service." msgstr "" #: ../cli_manage_images_curl.rst:13 msgid "" "The strings ``$OS_IMAGE_URL`` and ``$OS_AUTH_TOKEN`` represent variables " "defined in the client's environment. ``$OS_IMAGE_URL`` is the full path to " "your image service endpoint, for example, ``http://example.com``. ``" "$OS_AUTH_TOKEN`` represents an auth token generated by the Identity Service, " "for example, ``6583fb17c27b48b4b4a6033fe9cc0fe0``." msgstr "" #: ../cli_manage_images_curl.rst:20 msgid "Create an image" msgstr "" #: ../cli_manage_images_curl.rst:52 msgid "Update the image" msgstr "" #: ../cli_manage_images_curl.rst:82 msgid "Upload binary image data" msgstr "" #: ../cli_manage_images_curl.rst:97 msgid "Download binary image data" msgstr "" # #-#-#-#-# cli_manage_images_curl.pot (End User Guide 1.0.0) #-#-#-#-# # #-#-#-#-# dashboard_manage_images.pot (End User Guide 1.0.0) #-#-#-#-# #: ../cli_manage_images_curl.rst:111 ../dashboard_manage_images.rst:122 msgid "Delete an image" msgstr "" #: ../cli_manage_instances_hosts.rst:3 msgid "Manage instances and hosts" msgstr "" #: ../cli_manage_instances_hosts.rst:5 msgid "" "Instances are virtual machines that run inside the cloud on physical compute " "nodes. The Compute service manages instances. A host is the node on which a " "group of instances resides." msgstr "" #: ../cli_manage_instances_hosts.rst:9 msgid "" "This section describes how to perform the different tasks involved in " "instance management, such as adding floating IP addresses, stopping and " "starting instances, and terminating instances. This section also discusses " "node management tasks." msgstr "" #: ../cli_manage_ip_addresses.rst:3 msgid "Manage IP addresses" msgstr "" #: ../cli_manage_ip_addresses.rst:5 msgid "" "Each instance has a private, fixed IP address and can also have a public, or " "floating IP address. Private IP addresses are used for communication between " "instances, and public addresses are used for communication with networks " "outside the cloud, including the Internet." msgstr "" #: ../cli_manage_ip_addresses.rst:10 msgid "" "When you launch an instance, it is automatically assigned a private IP " "address that stays the same until you explicitly terminate the instance. " "Rebooting an instance has no effect on the private IP address." msgstr "" #: ../cli_manage_ip_addresses.rst:14 msgid "" "A pool of floating IP addresses, configured by the cloud administrator, is " "available in OpenStack Compute. The project quota defines the maximum number " "of floating IP addresses that you can allocate to the project. After you " "allocate a floating IP address to a project, you can:" msgstr "" #: ../cli_manage_ip_addresses.rst:19 msgid "" "Associate the floating IP address with an instance of the project. Only one " "floating IP address can be allocated to an instance at any given time." msgstr "" #: ../cli_manage_ip_addresses.rst:22 msgid "Disassociate a floating IP address from an instance in the project." msgstr "" #: ../cli_manage_ip_addresses.rst:24 msgid "" "Delete a floating IP from the project which automatically deletes that IP's " "associations." msgstr "" #: ../cli_manage_ip_addresses.rst:27 msgid "" "Use the :command:`nova floating-ip-*` commands to manage floating IP " "addresses." msgstr "" #: ../cli_manage_ip_addresses.rst:30 msgid "List floating IP address information" msgstr "" #: ../cli_manage_ip_addresses.rst:32 msgid "To list all pools that provide floating IP addresses, run:" msgstr "" #: ../cli_manage_ip_addresses.rst:46 msgid "" "If this list is empty, the cloud administrator must configure a pool of " "floating IP addresses." msgstr "" #: ../cli_manage_ip_addresses.rst:49 msgid "" "To list all floating IP addresses that are allocated to the current project, " "run:" msgstr "" #: ../cli_manage_ip_addresses.rst:62 msgid "" "For each floating IP address that is allocated to the current project, the " "command outputs the floating IP address, the ID for the instance to which " "the floating IP address is assigned, the associated fixed IP address, and " "the pool from which the floating IP address was allocated." msgstr "" #: ../cli_manage_ip_addresses.rst:69 msgid "Associate floating IP addresses" msgstr "" #: ../cli_manage_ip_addresses.rst:71 msgid "You can assign a floating IP address to a project and to an instance." msgstr "" #: ../cli_manage_ip_addresses.rst:73 msgid "" "Run the following command to allocate a floating IP address to the current " "project. By default, the floating IP address is allocated from the public " "pool. The command outputs the allocated IP address:" msgstr "" #: ../cli_manage_ip_addresses.rst:88 msgid "" "If more than one IP address pool is available, you can specify from which " "pool to allocate the IP address, using the pool's name. For example, to " "allocate a floating IP address from the ``test`` pool, run:" msgstr "" #: ../cli_manage_ip_addresses.rst:96 msgid "" "List all project instances with which a floating IP address could be " "associated." msgstr "" #: ../cli_manage_ip_addresses.rst:109 msgid "Associate an IP address with an instance in the project, as follows:" msgstr "" # #-#-#-#-# cli_manage_ip_addresses.pot (End User Guide 1.0.0) #-#-#-#-# # #-#-#-#-# cli_nova_launch_instance_from_volume.pot (End User Guide 1.0.0) #-#-#-#-# #: ../cli_manage_ip_addresses.rst:115 #: ../cli_nova_launch_instance_from_volume.rst:204 msgid "For example:" msgstr "" #: ../cli_manage_ip_addresses.rst:121 msgid "The instance is now associated with two IP addresses:" msgstr "" #: ../cli_manage_ip_addresses.rst:133 msgid "" "After you associate the IP address and configure security group rules for " "the instance, the instance is publicly available at the floating IP address." msgstr "" #: ../cli_manage_ip_addresses.rst:139 msgid "" "If an instance is connected to multiple networks, you can associate a " "floating IP address with a specific fixed IP address using the optional :" "option:`--fixed-address` parameter:" msgstr "" #: ../cli_manage_ip_addresses.rst:149 msgid "Disassociate floating IP addresses" msgstr "" #: ../cli_manage_ip_addresses.rst:151 msgid "To disassociate a floating IP address from an instance:" msgstr "" #: ../cli_manage_ip_addresses.rst:157 msgid "To remove the floating IP address from a project:" msgstr "" #: ../cli_manage_ip_addresses.rst:163 msgid "" "The IP address is returned to the pool of IP addresses that is available for " "all projects. If the IP address is still associated with a running instance, " "it is automatically disassociated from that instance." msgstr "" #: ../cli_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 "Create a share network" msgstr "" #: ../cli_manage_shares.rst:13 msgid "Create a share network." msgstr "" #: ../cli_manage_shares.rst:40 msgid "List share networks." msgstr "" # #-#-#-#-# cli_manage_shares.pot (End User Guide 1.0.0) #-#-#-#-# # #-#-#-#-# dashboard_manage_shares.pot (End User Guide 1.0.0) #-#-#-#-# #: ../cli_manage_shares.rst:52 ../dashboard_manage_shares.rst:12 msgid "Create a share" msgstr "" #: ../cli_manage_shares.rst:54 msgid "Create a share." msgstr "" #: ../cli_manage_shares.rst:92 msgid "Show a share." msgstr "" #: ../cli_manage_shares.rst:137 ../cli_manage_shares.rst:321 #: ../cli_manage_shares.rst:387 msgid "List shares." msgstr "" #: ../cli_manage_shares.rst:148 msgid "List share export locations." msgstr "" #: ../cli_manage_shares.rst:161 msgid "Allow read-write access" msgstr "" #: ../cli_manage_shares.rst:163 ../cli_manage_shares.rst:195 msgid "Allow access." msgstr "" #: ../cli_manage_shares.rst:179 ../cli_manage_shares.rst:211 #: ../cli_manage_shares.rst:235 msgid "List access." msgstr "" #: ../cli_manage_shares.rst:190 ../cli_manage_shares.rst:223 msgid "The access is created." msgstr "" #: ../cli_manage_shares.rst:193 msgid "Allow read-only access" msgstr "" # #-#-#-#-# cli_manage_shares.pot (End User Guide 1.0.0) #-#-#-#-# # #-#-#-#-# dashboard_manage_shares.pot (End User Guide 1.0.0) #-#-#-#-# #: ../cli_manage_shares.rst:226 ../dashboard_manage_shares.rst:71 msgid "Deny access" msgstr "" #: ../cli_manage_shares.rst:228 msgid "Deny access." msgstr "" #: ../cli_manage_shares.rst:245 msgid "The access is removed." msgstr "" #: ../cli_manage_shares.rst:248 msgid "Create snapshot" msgstr "" #: ../cli_manage_shares.rst:250 msgid "Create a snapshot." msgstr "" #: ../cli_manage_shares.rst:270 msgid "List snapshots." msgstr "" #: ../cli_manage_shares.rst:282 msgid "Create share from snapshot" msgstr "" #: ../cli_manage_shares.rst:284 msgid "Create a share from a snapshot." msgstr "" #: ../cli_manage_shares.rst:333 msgid "Show the share created from snapshot." msgstr "" #: ../cli_manage_shares.rst:379 msgid "Delete share" msgstr "" #: ../cli_manage_shares.rst:381 msgid "Delete a share." msgstr "" #: ../cli_manage_shares.rst:399 msgid "The share is being deleted." msgstr "" #: ../cli_manage_shares.rst:402 msgid "Delete snapshot" msgstr "" #: ../cli_manage_shares.rst:404 msgid "List snapshots before deleting." msgstr "" #: ../cli_manage_shares.rst:415 msgid "Delete a snapshot." msgstr "" #: ../cli_manage_shares.rst:421 msgid "List snapshots after deleting." msgstr "" #: ../cli_manage_shares.rst:432 msgid "The snapshot is deleted." msgstr "" # #-#-#-#-# cli_manage_shares.pot (End User Guide 1.0.0) #-#-#-#-# # #-#-#-#-# dashboard_manage_shares.pot (End User Guide 1.0.0) #-#-#-#-# #: ../cli_manage_shares.rst:435 ../dashboard_manage_shares.rst:116 msgid "Extend share" msgstr "" #: ../cli_manage_shares.rst:437 msgid "Extend share." msgstr "" #: ../cli_manage_shares.rst:443 msgid "Show the share while it is being extended." msgstr "" #: ../cli_manage_shares.rst:488 msgid "Show the share after it is extended." msgstr "" #: ../cli_manage_shares.rst:534 msgid "Shrink share" msgstr "" #: ../cli_manage_shares.rst:536 msgid "Shrink a share." msgstr "" #: ../cli_manage_shares.rst:542 msgid "Show the share while it is being shrunk." msgstr "" #: ../cli_manage_shares.rst:587 msgid "Show the share after it is being shrunk." msgstr "" # #-#-#-#-# cli_nova_configure_access_security_for_instances.pot (End User Guide 1.0.0) #-#-#-#-# # #-#-#-#-# configure_access_and_security_for_instances.pot (End User Guide 1.0.0) #-#-#-#-# # #-#-#-#-# sdk_configure_access_security_instances.pot (End User Guide 1.0.0) #-#-#-#-# #: ../cli_nova_configure_access_security_for_instances.rst:3 #: ../configure_access_and_security_for_instances.rst:3 #: ../sdk_configure_access_security_instances.rst:3 msgid "Configure access and security for instances" msgstr "" #: ../cli_nova_configure_access_security_for_instances.rst:5 msgid "" "When you launch a virtual machine, you can inject a *key pair*, which " "provides SSH access to your instance. For this to work, the image must " "contain the ``cloud-init`` package." msgstr "" #: ../cli_nova_configure_access_security_for_instances.rst:9 msgid "" "You can create at least one key pair for each project. You can use the key " "pair for multiple instances that belong to that project. If you generate a " "key pair with an external tool, you can import it into OpenStack." msgstr "" # #-#-#-#-# cli_nova_configure_access_security_for_instances.pot (End User Guide 1.0.0) #-#-#-#-# # #-#-#-#-# configure_access_and_security_for_instances.pot (End User Guide 1.0.0) #-#-#-#-# #: ../cli_nova_configure_access_security_for_instances.rst:15 #: ../configure_access_and_security_for_instances.rst:25 msgid "" "A key pair belongs to an individual user, not to a project. To share a key " "pair across multiple users, each user needs to import that key pair." msgstr "" #: ../cli_nova_configure_access_security_for_instances.rst:19 msgid "" "If an image uses a static root password or a static key set (neither is " "recommended), you must not provide a key pair when you launch the instance." msgstr "" #: ../cli_nova_configure_access_security_for_instances.rst:23 msgid "" "A *security group* is a named collection of network access rules that are " "use to limit the types of traffic that have access to instances. When you " "launch an instance, you can assign one or more security groups to it. If you " "do not create security groups, new instances are automatically assigned to " "the default security group, unless you explicitly specify a different " "security group." msgstr "" #: ../cli_nova_configure_access_security_for_instances.rst:30 msgid "" "The associated *rules* in each security group control the traffic to " "instances in the group. Any incoming traffic that is not matched by a rule " "is denied access by default. You can add rules to or remove rules from a " "security group, and you can modify rules for the default and any other " "security group." msgstr "" #: ../cli_nova_configure_access_security_for_instances.rst:36 msgid "" "You can modify the rules in a security group to allow access to instances " "through different ports and protocols. For example, you can modify rules to " "allow access to instances through SSH, to ping instances, or to allow UDP " "traffic; for example, for a DNS server running on an instance. You specify " "the following parameters for rules:" msgstr "" #: ../cli_nova_configure_access_security_for_instances.rst:42 msgid "" "**Source of traffic**. Enable traffic to instances from either IP addresses " "inside the cloud from other group members or from all IP addresses." msgstr "" #: ../cli_nova_configure_access_security_for_instances.rst:46 msgid "**Protocol**. Choose TCP for SSH, ICMP for pings, or UDP." msgstr "" #: ../cli_nova_configure_access_security_for_instances.rst:48 msgid "" "**Destination port on virtual machine**. Define a port range. To open a " "single port only, enter the same value twice. ICMP does not support ports; " "instead, you enter values to define the codes and types of ICMP traffic to " "be allowed." msgstr "" #: ../cli_nova_configure_access_security_for_instances.rst:53 msgid "Rules are automatically enforced as soon as you create or modify them." msgstr "" # #-#-#-#-# cli_nova_configure_access_security_for_instances.pot (End User Guide 1.0.0) #-#-#-#-# # #-#-#-#-# configure_access_and_security_for_instances.pot (End User Guide 1.0.0) #-#-#-#-# #: ../cli_nova_configure_access_security_for_instances.rst:67 #: ../configure_access_and_security_for_instances.rst:101 msgid "Add a key pair" msgstr "" #: ../cli_nova_configure_access_security_for_instances.rst:69 msgid "You can generate a key pair or upload an existing public key." msgstr "" #: ../cli_nova_configure_access_security_for_instances.rst:71 msgid "To generate a key pair, run the following command." msgstr "" #: ../cli_nova_configure_access_security_for_instances.rst:77 msgid "" "This command generates a key pair with the name that you specify for KEY" "\\_NAME, writes the private key to the ``.pem`` file that you specify, and " "registers the public key to the Nova database." msgstr "" #: ../cli_nova_configure_access_security_for_instances.rst:81 msgid "" "To set the permissions of the ``.pem`` file so that only you can read and " "write to it, run the following command." msgstr "" # #-#-#-#-# cli_nova_configure_access_security_for_instances.pot (End User Guide 1.0.0) #-#-#-#-# # #-#-#-#-# configure_access_and_security_for_instances.pot (End User Guide 1.0.0) #-#-#-#-# #: ../cli_nova_configure_access_security_for_instances.rst:89 #: ../configure_access_and_security_for_instances.rst:126 msgid "Import a key pair" msgstr "" #: ../cli_nova_configure_access_security_for_instances.rst:91 msgid "" "If you have already generated a key pair and the public key is located at " "``~/.ssh/id_rsa.pub``, run the following command to upload the public key." msgstr "" #: ../cli_nova_configure_access_security_for_instances.rst:99 msgid "" "This command registers the public key at the Nova database and names the key " "pair the name that you specify for ``KEY_NAME``." msgstr "" #: ../cli_nova_configure_access_security_for_instances.rst:102 msgid "" "To ensure that the key pair has been successfully imported, list key pairs " "as follows:" msgstr "" # #-#-#-#-# cli_nova_configure_access_security_for_instances.pot (End User Guide 1.0.0) #-#-#-#-# # #-#-#-#-# sdk_configure_access_security_instances.pot (End User Guide 1.0.0) #-#-#-#-# #: ../cli_nova_configure_access_security_for_instances.rst:110 #: ../sdk_configure_access_security_instances.rst:99 msgid "Create and manage security groups" msgstr "" #: ../cli_nova_configure_access_security_for_instances.rst:112 msgid "" "To list the security groups for the current project, including descriptions, " "enter the following command:" msgstr "" #: ../cli_nova_configure_access_security_for_instances.rst:119 msgid "" "To create a security group with a specified name and description, enter the " "following command:" msgstr "" #: ../cli_nova_configure_access_security_for_instances.rst:126 msgid "To delete a specified group, enter the following command:" msgstr "" #: ../cli_nova_configure_access_security_for_instances.rst:134 msgid "" "You cannot delete the default security group for a project. Also, you cannot " "delete a security group that is assigned to a running instance." msgstr "" # #-#-#-#-# cli_nova_configure_access_security_for_instances.pot (End User Guide 1.0.0) #-#-#-#-# # #-#-#-#-# sdk_configure_access_security_instances.pot (End User Guide 1.0.0) #-#-#-#-# #: ../cli_nova_configure_access_security_for_instances.rst:139 #: ../sdk_configure_access_security_instances.rst:148 msgid "Create and manage security group rules" msgstr "" #: ../cli_nova_configure_access_security_for_instances.rst:141 msgid "" "Modify security group rules with the :command:`nova secgroup-*-rule` " "commands. Before you begin, source the OpenStack RC file. For details, see :" "doc:`../common/cli_set_environment_variables_using_openstack_rc`." msgstr "" #: ../cli_nova_configure_access_security_for_instances.rst:145 msgid "To list the rules for a security group, run the following command:" msgstr "" #: ../cli_nova_configure_access_security_for_instances.rst:151 msgid "" "To allow SSH access to the instances, choose one of the following options:" msgstr "" #: ../cli_nova_configure_access_security_for_instances.rst:154 msgid "" "Allow access from all IP addresses, specified as IP subnet ``0.0.0.0/0`` in " "CIDR notation:" msgstr "" #: ../cli_nova_configure_access_security_for_instances.rst:161 msgid "" "Allow access only from IP addresses from other security groups (source " "groups) to access the specified port:" msgstr "" #: ../cli_nova_configure_access_security_for_instances.rst:169 msgid "To allow pinging of the instances, choose one of the following options:" msgstr "" #: ../cli_nova_configure_access_security_for_instances.rst:171 msgid "" "Allow pinging from all IP addresses, specified as IP subnet ``0.0.0.0/0`` in " "CIDR notation." msgstr "" #: ../cli_nova_configure_access_security_for_instances.rst:178 msgid "This allows access to all codes and all types of ICMP traffic." msgstr "" #: ../cli_nova_configure_access_security_for_instances.rst:180 msgid "" "Allow only members of other security groups (source groups) to ping " "instances." msgstr "" #: ../cli_nova_configure_access_security_for_instances.rst:188 msgid "" "To allow access through a UDP port, such as allowing access to a DNS server " "that runs on a VM, choose one of the following options:" msgstr "" #: ../cli_nova_configure_access_security_for_instances.rst:191 msgid "" "Allow UDP access from IP addresses, specified as IP subnet ``0.0.0.0/0`` in " "CIDR notation." msgstr "" #: ../cli_nova_configure_access_security_for_instances.rst:198 msgid "" "Allow only IP addresses from other security groups (source groups) to access " "the specified port." msgstr "" #: ../cli_nova_configure_access_security_for_instances.rst:207 msgid "Delete a security group rule" msgstr "" #: ../cli_nova_configure_access_security_for_instances.rst:209 msgid "" "To delete a security group rule, specify the same arguments that you used to " "create the rule." msgstr "" #: ../cli_nova_configure_access_security_for_instances.rst:212 msgid "" "For example, to delete the security group rule that permits SSH access from " "all IP addresses, run the following command." msgstr "" #: ../cli_nova_launch_instance_from_image.rst:3 msgid "Launch an instance from an image" msgstr "" #: ../cli_nova_launch_instance_from_image.rst:5 msgid "Follow the steps below to launch an instance from an image." msgstr "" #: ../cli_nova_launch_instance_from_image.rst:7 msgid "" "After you gather required parameters, run the following command to launch an " "instance. Specify the server name, flavor ID, and image ID." msgstr "" #: ../cli_nova_launch_instance_from_image.rst:16 msgid "" "Optionally, you can provide a key name for access control and a security " "group for security. You can also include metadata key and value pairs. For " "example, you can add a description for your server by providing the ``--meta " "description=\"My Server\"`` parameter." msgstr "" #: ../cli_nova_launch_instance_from_image.rst:21 msgid "" "You can pass user data in a local file at instance launch by using the ``--" "user-data USER-DATA-FILE`` parameter." msgstr "" #: ../cli_nova_launch_instance_from_image.rst:26 msgid "" "If you boot an instance with an INSTANCE_NAME greater than 63 characters, " "Compute truncates it automatically when turning it into a host name to " "ensure the correct work of dnsmasq. The corresponding warning is written " "into the ``nova-network.log`` file." msgstr "" #: ../cli_nova_launch_instance_from_image.rst:31 msgid "" "The following command launches the ``MyCirrosServer`` instance with the ``m1." "small`` flavor (ID of ``1``), ``cirros-0.3.2-x86_64-uec`` image (ID of " "``397e713c-b95b-4186-ad46-6126863ea0a9``), ``default`` security group, " "``KeyPair01`` key, and a user data file called ``cloudinit.file``:" msgstr "" #: ../cli_nova_launch_instance_from_image.rst:43 msgid "" "Depending on the parameters that you provide, the command returns a list of " "server properties." msgstr "" #: ../cli_nova_launch_instance_from_image.rst:79 msgid "" "A status of ``BUILD`` indicates that the instance has started, but is not " "yet online." msgstr "" #: ../cli_nova_launch_instance_from_image.rst:82 msgid "A status of ``ACTIVE`` indicates that the instance is active." msgstr "" #: ../cli_nova_launch_instance_from_image.rst:84 msgid "" "Copy the server ID value from the ``id`` field in the output. Use the ID to " "get server details or to delete your server." msgstr "" #: ../cli_nova_launch_instance_from_image.rst:87 msgid "" "Copy the administrative password value from the ``adminPass`` field. Use the " "password to log in to your server." msgstr "" #: ../cli_nova_launch_instance_from_image.rst:92 msgid "" "You can also place arbitrary local files into the instance file system at " "creation time by using the ``--file `` option. You can " "store up to five files. For example, if you have a special authorized keys " "file named ``special_authorized_keysfile`` that you want to put on the " "instance rather than using the regular SSH key injection, you can use the :" "option:`--file` option as shown in the following example." msgstr "" #: ../cli_nova_launch_instance_from_image.rst:105 msgid "Check if the instance is online." msgstr "" #: ../cli_nova_launch_instance_from_image.rst:111 msgid "" "The list shows the ID, name, status, and private (and if assigned, public) " "IP addresses for all instances in the project to which you belong:" msgstr "" #: ../cli_nova_launch_instance_from_image.rst:124 msgid "If the status for the instance is ACTIVE, the instance is online." msgstr "" #: ../cli_nova_launch_instance_from_image.rst:126 msgid "" "To view the available options for the :command:`nova list` command, run the " "following command:" msgstr "" #: ../cli_nova_launch_instance_from_image.rst:135 msgid "" "If you did not provide a key pair, security groups, or rules, you can access " "the instance only from inside the cloud through VNC. Even pinging the " "instance is not possible." msgstr "" #: ../cli_nova_launch_instance_from_volume.rst:3 msgid "Launch an instance from a volume" msgstr "" #: ../cli_nova_launch_instance_from_volume.rst:5 msgid "You can boot instances from a volume instead of an image." msgstr "" #: ../cli_nova_launch_instance_from_volume.rst:7 msgid "" "To complete these tasks, use these parameters on the :command:`nova boot` " "command:" msgstr "" #: ../cli_nova_launch_instance_from_volume.rst:14 msgid "Task" msgstr "" #: ../cli_nova_launch_instance_from_volume.rst:15 msgid "nova boot parameter" msgstr "" #: ../cli_nova_launch_instance_from_volume.rst:16 msgid "Information" msgstr "" #: ../cli_nova_launch_instance_from_volume.rst:17 msgid "Boot an instance from an image and attach a non-bootable volume." msgstr "" #: ../cli_nova_launch_instance_from_volume.rst:19 #: ../cli_nova_launch_instance_from_volume.rst:23 #: ../cli_nova_launch_instance_from_volume.rst:26 msgid "``--block-device``" msgstr "" #: ../cli_nova_launch_instance_from_volume.rst:20 msgid ":ref:`Boot_instance_from_image_and_attach_non-bootable_volume`" msgstr "" #: ../cli_nova_launch_instance_from_volume.rst:21 msgid "Create a volume from an image and boot an instance from that volume." msgstr "" #: ../cli_nova_launch_instance_from_volume.rst:24 #: ../cli_nova_launch_instance_from_volume.rst:27 msgid ":ref:`Create_volume_from_image_and_boot_instance`" msgstr "" #: ../cli_nova_launch_instance_from_volume.rst:25 msgid "Boot from an existing source image, volume, or snapshot." msgstr "" #: ../cli_nova_launch_instance_from_volume.rst:28 msgid "Attach a swap disk to an instance." msgstr "" #: ../cli_nova_launch_instance_from_volume.rst:29 msgid "``--swap``" msgstr "" #: ../cli_nova_launch_instance_from_volume.rst:30 #: ../cli_nova_launch_instance_from_volume.rst:33 msgid ":ref:`Attach_swap_or_ephemeral_disk_to_an_instance`" msgstr "" #: ../cli_nova_launch_instance_from_volume.rst:31 msgid "Attach an ephemeral disk to an instance." msgstr "" #: ../cli_nova_launch_instance_from_volume.rst:32 msgid "``--ephemeral``" msgstr "" #: ../cli_nova_launch_instance_from_volume.rst:37 msgid "" "To attach a volume to a running instance, see :ref:" "`Attach_a_volume_to_an_instance`." msgstr "" #: ../cli_nova_launch_instance_from_volume.rst:43 msgid "Boot instance from image and attach non-bootable volume" msgstr "" #: ../cli_nova_launch_instance_from_volume.rst:45 msgid "" "Create a non-bootable volume and attach that volume to an instance that you " "boot from an image." msgstr "" #: ../cli_nova_launch_instance_from_volume.rst:48 msgid "" "To create a non-bootable volume, do not create it from an image. The volume " "must be entirely empty with no partition table and no file system." msgstr "" #: ../cli_nova_launch_instance_from_volume.rst:52 msgid "Create a non-bootable volume." msgstr "" #: ../cli_nova_launch_instance_from_volume.rst:81 msgid "List volumes." msgstr "" #: ../cli_nova_launch_instance_from_volume.rst:92 msgid "" "Boot an instance from an image and attach the empty volume to the instance." msgstr "" #: ../cli_nova_launch_instance_from_volume.rst:137 msgid "Create volume from image and boot instance" msgstr "" #: ../cli_nova_launch_instance_from_volume.rst:139 msgid "" "You can create a volume from an existing image, volume, or snapshot. This " "procedure shows you how to create a volume from an image, and use the volume " "to boot an instance." msgstr "" #: ../cli_nova_launch_instance_from_volume.rst:157 msgid "Note the ID of the image that you want to use to create a volume." msgstr "" #: ../cli_nova_launch_instance_from_volume.rst:159 msgid "" "If you want to create a volume to a specific storage backend, you need to " "use an image which has *cinder_img_volume_type* property. In this case, a " "new volume will be created as *storage_backend1* volume type." msgstr "" #: ../cli_nova_launch_instance_from_volume.rst:199 msgid "Note the ID of the flavor that you want to use to create a volume." msgstr "" #: ../cli_nova_launch_instance_from_volume.rst:201 msgid "" "To create a bootable volume from an image and launch an instance from this " "volume, use the ``--block-device`` parameter." msgstr "" #: ../cli_nova_launch_instance_from_volume.rst:212 msgid "The parameters are:" msgstr "" #: ../cli_nova_launch_instance_from_volume.rst:214 msgid "``--flavor`` FLAVOR. The flavor ID or name." msgstr "" #: ../cli_nova_launch_instance_from_volume.rst:216 msgid "" "``--block-device`` source=SOURCE,id=ID,dest=DEST,size=SIZE,shutdown=PRESERVE," "bootindex=INDEX" msgstr "" #: ../cli_nova_launch_instance_from_volume.rst:220 msgid "" "The type of object used to create the block device. Valid values are " "``volume``, ``snapshot``, ``image``, and ``blank``." msgstr "" #: ../cli_nova_launch_instance_from_volume.rst:221 msgid "**source=SOURCE**" msgstr "" #: ../cli_nova_launch_instance_from_volume.rst:224 msgid "**id=ID**" msgstr "" #: ../cli_nova_launch_instance_from_volume.rst:224 msgid "The ID of the source object." msgstr "" #: ../cli_nova_launch_instance_from_volume.rst:227 msgid "" "The type of the target virtual device. Valid values are ``volume`` and " "``local``." msgstr "" #: ../cli_nova_launch_instance_from_volume.rst:228 msgid "**dest=DEST**" msgstr "" #: ../cli_nova_launch_instance_from_volume.rst:231 msgid "**size=SIZE**" msgstr "" #: ../cli_nova_launch_instance_from_volume.rst:231 msgid "The size of the volume that is created." msgstr "" #: ../cli_nova_launch_instance_from_volume.rst:234 msgid "" "What to do with the volume when the instance is deleted. ``preserve`` does " "not delete the volume. ``remove`` deletes the volume." msgstr "" #: ../cli_nova_launch_instance_from_volume.rst:236 msgid "**shutdown={preserve\\|remove}**" msgstr "" #: ../cli_nova_launch_instance_from_volume.rst:239 msgid "**bootindex=INDEX**" msgstr "" #: ../cli_nova_launch_instance_from_volume.rst:239 msgid "Orders the boot disks. Use ``0`` to boot from this volume." msgstr "" #: ../cli_nova_launch_instance_from_volume.rst:241 msgid "``NAME``. The name for the server." msgstr "" #: ../cli_nova_launch_instance_from_volume.rst:243 msgid "" "Create a bootable volume from an image, before the instance boots. The " "volume is not deleted when the instance is terminated." msgstr "" #: ../cli_nova_launch_instance_from_volume.rst:286 msgid "" "List volumes to see the bootable volume and its attached " "``myInstanceFromVolume`` instance." msgstr "" #: ../cli_nova_launch_instance_from_volume.rst:301 msgid "Attach swap or ephemeral disk to an instance" msgstr "" #: ../cli_nova_launch_instance_from_volume.rst:303 msgid "" "Use the nova ``boot`` ``--swap`` parameter to attach a swap disk on boot or " "the nova ``boot`` ``--ephemeral`` parameter to attach an ephemeral disk on " "boot. When you terminate the instance, both disks are deleted." msgstr "" #: ../cli_nova_launch_instance_from_volume.rst:307 msgid "Boot an instance with a 512 MB swap disk and 2 GB ephemeral disk." msgstr "" #: ../cli_nova_launch_instance_from_volume.rst:315 msgid "" "The flavor defines the maximum swap and ephemeral disk size. You cannot " "exceed these maximum values." msgstr "" #: ../cli_nova_launch_instance_using_ISO_image.rst:3 msgid "Launch an instance using ISO image" msgstr "" #: ../cli_nova_launch_instance_using_ISO_image.rst:8 msgid "Boot an instance from an ISO image" msgstr "" #: ../cli_nova_launch_instance_using_ISO_image.rst:10 msgid "" "OpenStack supports booting instances using ISO images. But before you make " "such instances functional, use the :command:`nova boot` command with the " "following parameters to boot an instance." msgstr "" #: ../cli_nova_launch_instance_using_ISO_image.rst:55 msgid "" "In this command, ``ubuntu-14.04.2-server-amd64.iso`` is the ISO image, and " "``INSTANCE_NAME`` is the name of the new instance. ``NETWORK_UUID`` is a " "valid network id in your system." msgstr "" #: ../cli_nova_launch_instance_using_ISO_image.rst:61 msgid "" "You need the Block Storage service, and the parameter ``shutdown=preserve`` " "is also mandatory, thus the volume will be preserved after the shutdown of " "the instance." msgstr "" #: ../cli_nova_launch_instance_using_ISO_image.rst:65 msgid "" "After the instance is successfully launched, connect to the instance using a " "remote console and follow the instructions to install the system as using " "ISO images on regular computers. When the installation is finished and " "system is rebooted, the instance asks you again to install the operating " "system, which means your instance is not usable. If you have problems with " "image creation, please check the `Virtual Machine Image Guide `_ for reference." msgstr "" #: ../cli_nova_launch_instance_using_ISO_image.rst:78 msgid "Make the instances booted from ISO image functional" msgstr "" #: ../cli_nova_launch_instance_using_ISO_image.rst:80 msgid "" "Now complete the following steps to make your instances created using ISO " "image actually functional." msgstr "" #: ../cli_nova_launch_instance_using_ISO_image.rst:83 msgid "Delete the instance using the following command." msgstr "" #: ../cli_nova_launch_instance_using_ISO_image.rst:89 msgid "" "After you delete the instance, the system you have just installed using your " "ISO image remains, because the parameter ``shutdown=preserve`` was set, so " "run the following command." msgstr "" #: ../cli_nova_launch_instance_using_ISO_image.rst:102 msgid "" "You get a list with all the volumes in your system. In this list, you can " "find the volume that is attached to your ISO created instance, with the " "false bootable property." msgstr "" #: ../cli_nova_launch_instance_using_ISO_image.rst:106 msgid "Upload the volume to glance." msgstr "" #: ../cli_nova_launch_instance_using_ISO_image.rst:118 msgid "" "The ``VOLUME_UUID`` is the uuid of the volume that is attached to your ISO " "created instance, and the ``IMAGE_NAME`` is the name that you give to your " "new image." msgstr "" #: ../cli_nova_launch_instance_using_ISO_image.rst:122 msgid "" "After the image is successfully uploaded, you can use the new image to boot " "instances." msgstr "" #: ../cli_nova_launch_instance_using_ISO_image.rst:125 msgid "" "The instances launched using this image contain the system that you have " "just installed using the ISO image." msgstr "" #: ../cli_provide_user_data_to_instances.rst:3 msgid "Provide user data to instances" msgstr "" #: ../cli_provide_user_data_to_instances.rst:5 msgid "" "A user data file is a special key in the metadata service that holds a file " "that cloud-aware applications in the guest instance can access. For example, " "one application that uses :term:`user data` is the `cloud-init `__ system, which is an open-source package " "from Ubuntu that is available on various Linux distributions and which " "handles early initialization of a cloud instance." msgstr "" #: ../cli_provide_user_data_to_instances.rst:13 msgid "" "You can place user data in a local file and pass it through the ``--user-" "data `` parameter at instance creation." msgstr "" #: ../cli_reboot_an_instance.rst:3 msgid "Reboot an instance" msgstr "" #: ../cli_reboot_an_instance.rst:5 msgid "" "You can soft or hard reboot a running instance. A soft reboot attempts a " "graceful shut down and restart of the instance. A hard reboot power cycles " "the instance." msgstr "" #: ../cli_reboot_an_instance.rst:9 msgid "By default, when you reboot an instance, it is a soft reboot." msgstr "" #: ../cli_reboot_an_instance.rst:15 msgid "" "To perform a hard reboot, pass the :option:`--hard` parameter, as follows:" msgstr "" #: ../cli_reboot_an_instance.rst:21 msgid "" "It is also possible to reboot a running instance into rescue mode. For " "example, this operation may be required, if a filesystem of an instance " "becomes corrupted with prolonged use." msgstr "" #: ../cli_reboot_an_instance.rst:27 msgid "" "Pause, suspend, and stop operations are not allowed when an instance is " "running in rescue mode, as triggering these actions causes the loss of the " "original instance state, and makes it impossible to unrescue the instance." msgstr "" #: ../cli_reboot_an_instance.rst:32 msgid "" "Rescue mode provides a mechanism for access, even if an image renders the " "instance inaccessible. By default, it starts an instance from the initial " "image attaching the current boot disk as a secondary one." msgstr "" #: ../cli_reboot_an_instance.rst:36 msgid "" "To perform an instance reboot into rescue mode, run the following command:" msgstr "" #: ../cli_reboot_an_instance.rst:45 msgid "" "On running the :command:`nova rescue` command, an instance performs a soft " "shutdown first. This means that the guest operating system has a chance to " "perform a controlled shutdown before the instance is powered off. The " "shutdown behavior is configured by the ``shutdown_timeout`` parameter that " "can be set in the ``nova.conf`` file. Its value stands for the overall " "period (in seconds) a guest operation system is allowed to complete the " "shutdown. The default timeout is 60 seconds. See `Description of Compute " "configuration options `_ for details." msgstr "" #: ../cli_reboot_an_instance.rst:63 msgid "" "To restart the instance from the normal boot disk, run the following command:" msgstr "" #: ../cli_reboot_an_instance.rst:70 msgid "" "If you want to rescue an instance with a specific image, rather than the " "default one, use the :option:`--rescue_image_ref` parameter:" msgstr "" #: ../cli_search_instance_with_ip_address.rst:3 msgid "Search for an instance using IP address" msgstr "" #: ../cli_search_instance_with_ip_address.rst:5 msgid "" "You can search for an instance using the IP address parameter, :option:`--" "ip`, with the :command:`nova list` command." msgstr "" #: ../cli_search_instance_with_ip_address.rst:12 msgid "The following example shows the results of a search on ``10.0.0.4``." msgstr "" #: ../cli_stop_and_start_an_instance.rst:3 msgid "Stop and start an instance" msgstr "" #: ../cli_stop_and_start_an_instance.rst:5 msgid "Use one of the following methods to stop and start an instance." msgstr "" #: ../cli_stop_and_start_an_instance.rst:8 msgid "Pause and unpause an instance" msgstr "" #: ../cli_stop_and_start_an_instance.rst:10 msgid "To pause an instance, run the following command:" msgstr "" #: ../cli_stop_and_start_an_instance.rst:16 msgid "" "This command stores the state of the VM in RAM. A paused instance continues " "to run in a frozen state." msgstr "" #: ../cli_stop_and_start_an_instance.rst:19 msgid "To unpause an instance, run the following command:" msgstr "" #: ../cli_stop_and_start_an_instance.rst:26 msgid "Suspend and resume an instance" msgstr "" #: ../cli_stop_and_start_an_instance.rst:28 msgid "" "To initiate a hypervisor-level suspend operation, run the following command:" msgstr "" #: ../cli_stop_and_start_an_instance.rst:35 msgid "To resume a suspended instance, run the following command:" msgstr "" #: ../cli_stop_and_start_an_instance.rst:42 msgid "Shelve and unshelve an instance" msgstr "" #: ../cli_stop_and_start_an_instance.rst:44 msgid "" "Shelving is useful if you have an instance that you are not using, but would " "like retain in your list of servers. For example, you can stop an instance " "at the end of a work week, and resume work again at the start of the next " "week. All associated data and resources are kept; however, anything still in " "memory is not retained. If a shelved instance is no longer needed, it can " "also be entirely removed." msgstr "" #: ../cli_stop_and_start_an_instance.rst:51 msgid "You can run the following shelving tasks:" msgstr "" #: ../cli_stop_and_start_an_instance.rst:53 msgid "" "Shelve an instance - Shuts down the instance, and stores it together with " "associated data and resources (a snapshot is taken if not volume backed). " "Anything in memory is lost." msgstr "" #: ../cli_stop_and_start_an_instance.rst:63 msgid "" "By default, the :command:`nova shelve` command gives the guest operating " "system a chance to perform a controlled shutdown before the instance is " "powered off. The shutdown behavior is configured by the ``shutdown_timeout`` " "parameter that can be set in the ``nova.conf`` file. Its value stands for " "the overall period (in seconds) a guest operation system is allowed to " "complete the shutdown. The default timeout is 60 seconds. See `Description " "of Compute configuration options `_ for details." msgstr "" #: ../cli_stop_and_start_an_instance.rst:79 msgid "Unshelve an instance - Restores the instance." msgstr "" #: ../cli_stop_and_start_an_instance.rst:85 msgid "" "Remove a shelved instance - Removes the instance from the server; data and " "resource associations are deleted. If an instance is no longer needed, you " "can move the instance off the hypervisor in order to minimize resource usage." msgstr "" #: ../cli_swift_archive_auto_extract.rst:5 msgid "Auto-extract archive files" msgstr "" # #-#-#-#-# cli_swift_archive_auto_extract.pot (End User Guide 1.0.0) #-#-#-#-# # #-#-#-#-# cli_swift_bulk_delete.pot (End User Guide 1.0.0) #-#-#-#-# # #-#-#-#-# cli_swift_static_website.pot (End User Guide 1.0.0) #-#-#-#-# #: ../cli_swift_archive_auto_extract.rst:7 ../cli_swift_bulk_delete.rst:7 #: ../cli_swift_static_website.rst:7 msgid "" "To discover whether your Object Storage system supports this feature, see :" "ref:`discoverability`. Alternatively, check with your service provider." msgstr "" #: ../cli_swift_archive_auto_extract.rst:11 msgid "Use the auto-extract archive feature to upload a tar archive file." msgstr "" #: ../cli_swift_archive_auto_extract.rst:13 msgid "" "The Object Storage system extracts files from the archive file and creates " "an object." msgstr "" #: ../cli_swift_archive_auto_extract.rst:17 msgid "Auto-extract archive request" msgstr "" #: ../cli_swift_archive_auto_extract.rst:19 msgid "" "To upload an archive file, make a ``PUT`` request. Add the ``extract-" "archive=format`` query parameter to indicate that you are uploading a tar " "archive file instead of normal content." msgstr "" #: ../cli_swift_archive_auto_extract.rst:23 msgid "" "Valid values for the ``format`` variable are ``tar``, ``tar.gz``, or ``tar." "bz2``." msgstr "" #: ../cli_swift_archive_auto_extract.rst:26 msgid "" "The path you specify in the ``PUT`` request is used for the location of the " "object and the prefix for the resulting object names." msgstr "" #: ../cli_swift_archive_auto_extract.rst:29 msgid "In the ``PUT`` request, you can specify the path for:" msgstr "" #: ../cli_swift_archive_auto_extract.rst:31 msgid "An account" msgstr "" #: ../cli_swift_archive_auto_extract.rst:33 msgid "Optionally, a specific container" msgstr "" #: ../cli_swift_archive_auto_extract.rst:35 msgid "Optionally, a specific object prefix" msgstr "" #: ../cli_swift_archive_auto_extract.rst:37 msgid "" "For example, if the first object in the tar archive is ``/home/file1.txt`` " "and you specify the ``/v1/12345678912345/mybackup/castor/`` path, the " "operation creates the ``castor/home/file1.txt`` object in the ``mybackup`` " "container in the ``12345678912345`` account." msgstr "" #: ../cli_swift_archive_auto_extract.rst:44 msgid "Create an archive for auto-extract" msgstr "" #: ../cli_swift_archive_auto_extract.rst:46 msgid "You must use the tar utility to create the tar archive file." msgstr "" #: ../cli_swift_archive_auto_extract.rst:48 msgid "" "You can upload regular files but you cannot upload other items (for example, " "empty directories or symbolic links)." msgstr "" #: ../cli_swift_archive_auto_extract.rst:51 msgid "You must UTF-8-encode the member names." msgstr "" #: ../cli_swift_archive_auto_extract.rst:53 msgid "The archive auto-extract feature supports these formats:" msgstr "" #: ../cli_swift_archive_auto_extract.rst:55 msgid "The POSIX.1-1988 Ustar format." msgstr "" #: ../cli_swift_archive_auto_extract.rst:57 msgid "" "The GNU tar format. Includes the long name, long link, and sparse extensions." msgstr "" #: ../cli_swift_archive_auto_extract.rst:60 msgid "The POSIX.1-2001 pax format." msgstr "" #: ../cli_swift_archive_auto_extract.rst:62 msgid "Use gzip or bzip2 to compress the archive." msgstr "" #: ../cli_swift_archive_auto_extract.rst:64 msgid "" "Use the ``extract-archive`` query parameter to specify the format. Valid " "values for this parameter are ``tar``, ``tar.gz``, or ``tar.bz2``." msgstr "" #: ../cli_swift_archive_auto_extract.rst:69 msgid "Auto-extract archive response" msgstr "" #: ../cli_swift_archive_auto_extract.rst:71 msgid "" "When Object Storage processes the request, it performs multiple sub-" "operations. Even if all sub-operations fail, the operation returns a 201 " "``Created`` status. Some sub-operations might succeed while others fail. " "Examine the response body to determine the results of each auto-extract " "archive sub-operation." msgstr "" #: ../cli_swift_archive_auto_extract.rst:77 msgid "" "You can set the ``Accept`` request header to one of these values to define " "the response format:" msgstr "" # #-#-#-#-# cli_swift_archive_auto_extract.pot (End User Guide 1.0.0) #-#-#-#-# # #-#-#-#-# cli_swift_bulk_delete.pot (End User Guide 1.0.0) #-#-#-#-# #: ../cli_swift_archive_auto_extract.rst:81 ../cli_swift_bulk_delete.rst:58 msgid "" "Formats response as plain text. If you omit the ``Accept`` header, ``text/" "plain`` is the default." msgstr "" # #-#-#-#-# cli_swift_archive_auto_extract.pot (End User Guide 1.0.0) #-#-#-#-# # #-#-#-#-# cli_swift_bulk_delete.pot (End User Guide 1.0.0) #-#-#-#-# #: ../cli_swift_archive_auto_extract.rst:82 ../cli_swift_bulk_delete.rst:59 msgid "``text/plain``" msgstr "" # #-#-#-#-# cli_swift_archive_auto_extract.pot (End User Guide 1.0.0) #-#-#-#-# # #-#-#-#-# cli_swift_bulk_delete.pot (End User Guide 1.0.0) #-#-#-#-# #: ../cli_swift_archive_auto_extract.rst:85 ../cli_swift_bulk_delete.rst:62 msgid "Formats response as JSON." msgstr "" # #-#-#-#-# cli_swift_archive_auto_extract.pot (End User Guide 1.0.0) #-#-#-#-# # #-#-#-#-# cli_swift_bulk_delete.pot (End User Guide 1.0.0) #-#-#-#-# #: ../cli_swift_archive_auto_extract.rst:85 ../cli_swift_bulk_delete.rst:62 msgid "``application/json``" msgstr "" # #-#-#-#-# cli_swift_archive_auto_extract.pot (End User Guide 1.0.0) #-#-#-#-# # #-#-#-#-# cli_swift_bulk_delete.pot (End User Guide 1.0.0) #-#-#-#-# #: ../cli_swift_archive_auto_extract.rst:88 #: ../cli_swift_archive_auto_extract.rst:91 ../cli_swift_bulk_delete.rst:65 msgid "Formats response as XML." msgstr "" #: ../cli_swift_archive_auto_extract.rst:88 msgid "``application/xml``" msgstr "" #: ../cli_swift_archive_auto_extract.rst:91 msgid "``text/xml``" msgstr "" #: ../cli_swift_archive_auto_extract.rst:93 msgid "" "The following auto-extract archive files example shows a ``text/plain`` " "response body where no failures occurred:" msgstr "" #: ../cli_swift_archive_auto_extract.rst:101 msgid "" "The following auto-extract archive files example shows a ``text/plain`` " "response where some failures occurred. In this example, the Object Storage " "system is configured to reject certain character strings so that the 400 Bad " "Request error occurs for any objects that use the restricted strings." msgstr "" #: ../cli_swift_archive_auto_extract.rst:114 msgid "" "The following example shows the failure response in ``application/json`` " "format." msgstr "" #: ../cli_swift_bulk_delete.rst:5 msgid "Bulk delete" msgstr "" #: ../cli_swift_bulk_delete.rst:10 msgid "" "With bulk delete, you can delete up to 10,000 objects or containers " "(configurable) in one request." msgstr "" #: ../cli_swift_bulk_delete.rst:14 msgid "Bulk delete request" msgstr "" #: ../cli_swift_bulk_delete.rst:16 msgid "" "To perform a bulk delete operation, add the ``bulk-delete`` query parameter " "to the path of a ``POST`` or ``DELETE`` operation." msgstr "" #: ../cli_swift_bulk_delete.rst:21 msgid "The ``DELETE`` operation is supported for backwards compatibility." msgstr "" #: ../cli_swift_bulk_delete.rst:23 msgid "" "The path is the account, such as ``/v1/12345678912345``, that contains the " "objects and containers." msgstr "" #: ../cli_swift_bulk_delete.rst:26 msgid "" "In the request body of the ``POST`` or ``DELETE`` operation, list the " "objects or containers to be deleted. Separate each name with a newline " "character. You can include a maximum of 10,000 items (configurable) in the " "list." msgstr "" #: ../cli_swift_bulk_delete.rst:31 msgid "In addition, you must:" msgstr "" #: ../cli_swift_bulk_delete.rst:33 msgid "UTF-8-encode and then URL-encode the names." msgstr "" #: ../cli_swift_bulk_delete.rst:35 msgid "" "To indicate an object, specify the container and object name as: " "``CONTAINER_NAME``/``OBJECT_NAME``." msgstr "" #: ../cli_swift_bulk_delete.rst:38 msgid "" "To indicate a container, specify the container name as: ``CONTAINER_NAME``. " "Make sure that the container is empty. If it contains objects, Object " "Storage cannot delete the container." msgstr "" #: ../cli_swift_bulk_delete.rst:42 msgid "Set the ``Content-Type`` request header to ``text/plain``." msgstr "" #: ../cli_swift_bulk_delete.rst:45 msgid "Bulk delete response" msgstr "" #: ../cli_swift_bulk_delete.rst:47 msgid "" "When Object Storage processes the request, it performs multiple sub-" "operations. Even if all sub-operations fail, the operation returns a 200 " "status. The bulk operation returns a response body that contains details " "that indicate which sub-operations have succeeded and failed. Some sub-" "operations might succeed while others fail. Examine the response body to " "determine the results of each delete sub-operation." msgstr "" #: ../cli_swift_bulk_delete.rst:54 msgid "" "You can set the ``Accept`` request header to one of the following values to " "define the response format:" msgstr "" #: ../cli_swift_bulk_delete.rst:65 msgid "``application/xml`` or ``text/xml``" msgstr "" #: ../cli_swift_bulk_delete.rst:67 msgid "The response body contains the following information:" msgstr "" #: ../cli_swift_bulk_delete.rst:69 msgid "The number of files actually deleted." msgstr "" #: ../cli_swift_bulk_delete.rst:71 msgid "The number of not found objects." msgstr "" #: ../cli_swift_bulk_delete.rst:73 msgid "" "Errors. A list of object names and associated error statuses for the objects " "that failed to delete. The format depends on the value that you set in the " "``Accept`` header." msgstr "" #: ../cli_swift_bulk_delete.rst:77 msgid "" "The following bulk delete response is in ``application/xml`` format. In this " "example, the ``mycontainer`` container is not empty, so it cannot be deleted." msgstr "" #: ../cli_swift_create_containers.rst:3 msgid "Create and manage containers" msgstr "" #: ../cli_swift_create_containers.rst:5 msgid "" "To create a container, run the following command and replace ``CONTAINER`` " "with the name of your container." msgstr "" #: ../cli_swift_create_containers.rst:12 msgid "To list all containers, run the following command:" msgstr "" #: ../cli_swift_create_containers.rst:18 msgid "To check the status of containers, run the following command:" msgstr "" #: ../cli_swift_create_containers.rst:34 msgid "" "You can also use the :command:`swift stat` command with the ``ACCOUNT`` or " "``CONTAINER`` names as parameters." msgstr "" #: ../cli_swift_discoverability.rst:5 msgid "Discoverability" msgstr "" #: ../cli_swift_discoverability.rst:7 msgid "" "Your Object Storage system might not enable all features that this document " "describes. These features are:" msgstr "" #: ../cli_swift_discoverability.rst:10 msgid ":ref:`large-object-creation`" msgstr "" #: ../cli_swift_discoverability.rst:11 msgid ":ref:`archive-auto-extract`" msgstr "" #: ../cli_swift_discoverability.rst:12 msgid ":ref:`bulk-delete`" msgstr "" #: ../cli_swift_discoverability.rst:13 msgid ":ref:`static-website`" msgstr "" #: ../cli_swift_discoverability.rst:15 msgid "" "To discover which features are enabled in your Object Storage system, use " "the ``/info`` request." msgstr "" #: ../cli_swift_discoverability.rst:18 msgid "" "To use the ``/info`` request, send a ``GET`` request using the ``/info`` " "path to the Object Store endpoint as shown in this example:" msgstr "" #: ../cli_swift_discoverability.rst:25 msgid "This example shows a truncated response body:" msgstr "" #: ../cli_swift_discoverability.rst:41 msgid "" "This output shows that the Object Storage system has enabled the static " "website and temporary URL features." msgstr "" #: ../cli_swift_discoverability.rst:46 msgid "" "In some cases, the ``/info`` request will return an error. This could be " "because your service provider has disabled the ``/info`` request function, " "or because you are using an older version that does not support it." msgstr "" #: ../cli_swift_env_vars.rst:5 msgid "Environment variables required to run examples" msgstr "" #: ../cli_swift_env_vars.rst:7 msgid "" "To run the cURL command examples for the Object Storage API requests, set " "these environment variables:" msgstr "" #: ../cli_swift_env_vars.rst:11 msgid "" "The public URL that is the HTTP endpoint from where you can access Object " "Storage. It includes the Object Storage API version number and your account " "name. For example, ``https://23.253.72.207/v1/my_account``." msgstr "" #: ../cli_swift_env_vars.rst:14 msgid "publicURL" msgstr "" #: ../cli_swift_env_vars.rst:17 msgid "The authentication token for Object Storage." msgstr "" #: ../cli_swift_env_vars.rst:17 msgid "token" msgstr "" #: ../cli_swift_env_vars.rst:19 msgid "To obtain these values, run the :command:`swift stat -v` command." msgstr "" #: ../cli_swift_env_vars.rst:21 msgid "" "As shown in this example, the public URL appears in the ``StorageURL`` " "field, and the token appears in the ``Auth Token`` field:" msgstr "" #: ../cli_swift_large_lists.rst:3 msgid "Page through large lists of containers or objects" msgstr "" #: ../cli_swift_large_lists.rst:5 msgid "" "If you have a large number of containers or objects, you can use the " "``marker``, ``limit``, and ``end_marker`` parameters to control how many " "items are returned in a list and where the list starts or ends." msgstr "" #: ../cli_swift_large_lists.rst:10 msgid "" "When you request a list of containers or objects, Object Storage returns a " "maximum of 10,000 names for each request. To get subsequent names, you must " "make another request with the ``marker`` parameter. Set the ``marker`` " "parameter to the name of the last item returned in the previous list. You " "must URL-encode the ``marker`` value before you send the HTTP request. " "Object Storage returns a maximum of 10,000 names starting after the last " "item returned." msgstr "" #: ../cli_swift_large_lists.rst:17 msgid "marker" msgstr "" #: ../cli_swift_large_lists.rst:20 msgid "" "To return fewer than 10,000 names, use the ``limit`` parameter. If the " "number of names returned equals the specified ``limit`` (or 10,000 if you " "omit the ``limit`` parameter), you can assume there are more names to list. " "If the number of names in the list is exactly divisible by the ``limit`` " "value, the last request has no content." msgstr "" #: ../cli_swift_large_lists.rst:25 msgid "limit" msgstr "" #: ../cli_swift_large_lists.rst:28 msgid "" "Limits the result set to names that are less than the ``end_marker`` " "parameter value. You must URL-encode the ``end_marker`` value before you " "send the HTTP request." msgstr "" #: ../cli_swift_large_lists.rst:30 msgid "end_marker" msgstr "" #: ../cli_swift_large_lists.rst:33 msgid "To page through a large list of containers" msgstr "" #: ../cli_swift_large_lists.rst:35 msgid "Assume the following list of container names:" msgstr "" #: ../cli_swift_large_lists.rst:45 msgid "Use a ``limit`` of two:" msgstr "" #: ../cli_swift_large_lists.rst:56 msgid "Because two container names are returned, there are more names to list." msgstr "" #: ../cli_swift_large_lists.rst:59 msgid "" "Make another request with a ``marker`` parameter set to the name of the last " "item returned:" msgstr "" #: ../cli_swift_large_lists.rst:72 msgid "Again, two items are returned, and there might be more." msgstr "" #: ../cli_swift_large_lists.rst:74 msgid "Make another request with a ``marker`` of the last item returned:" msgstr "" #: ../cli_swift_large_lists.rst:85 msgid "" "You receive a one-item response, which is fewer than the ``limit`` number of " "names. This indicates that this is the end of the list." msgstr "" #: ../cli_swift_large_lists.rst:88 msgid "" "Use the ``end_marker`` parameter to limit the result set to object names " "that are less than the ``end_marker`` parameter value:" msgstr "" #: ../cli_swift_large_lists.rst:102 msgid "" "You receive a result set of all container names before the ``end-marker`` " "value." msgstr "" #: ../cli_swift_large_object_creation.rst:5 msgid "Large objects" msgstr "" #: ../cli_swift_large_object_creation.rst:7 msgid "" "To discover whether your Object Storage system supports this feature, see :" "ref:`discoverability` or check with your service provider." msgstr "" #: ../cli_swift_large_object_creation.rst:10 msgid "" "By default, the content of an object cannot be greater than 5 GB. However, " "you can use a number of smaller objects to construct a large object. The " "large object is comprised of two types of objects:" msgstr "" #: ../cli_swift_large_object_creation.rst:14 msgid "" "``Segment objects`` store the object content. You can divide your content " "into segments and upload each segment into its own segment object. Segment " "objects do not have any special features. You create, update, download, and " "delete segment objects just as you do with normal objects." msgstr "" #: ../cli_swift_large_object_creation.rst:19 msgid "" "A ``manifest object`` links the segment objects into one logical large " "object. When you download a manifest object, Object Storage concatenates and " "returns the contents of the segment objects in the response body. This " "behavior extends to the response headers returned by ``GET`` and ``HEAD`` " "requests. The ``Content-Length`` response header contains the total size of " "all segment objects." msgstr "" #: ../cli_swift_large_object_creation.rst:26 msgid "" "Object Storage takes the ``ETag`` value of each segment, concatenates them " "together, and returns the MD5 checksum of the result to calculate the " "``ETag`` response header value. The manifest object types are:" msgstr "" #: ../cli_swift_large_object_creation.rst:31 msgid "" "The manifest object content is an ordered list of the names of the segment " "objects in JSON format. See :ref:`static_large_objects`." msgstr "" #: ../cli_swift_large_object_creation.rst:32 #: ../cli_swift_large_object_creation.rst:53 msgid "Static large objects" msgstr "" #: ../cli_swift_large_object_creation.rst:35 msgid "" "The manifest object has no content but it has a ``X-Object-Manifest`` " "metadata header. The value of this header is ``CONTAINER/PREFIX``, where " "``CONTAINER`` is the name of the container where the segment objects are " "stored, and ``PREFIX`` is a string that all segment objects have in common. " "See :ref:`dynamic_large_objects`." msgstr "" #: ../cli_swift_large_object_creation.rst:40 #: ../cli_swift_large_object_creation.rst:153 msgid "Dynamic large objects" msgstr "" #: ../cli_swift_large_object_creation.rst:44 msgid "" "If you use a manifest object as the source of a ``COPY`` request, the new " "object is a normal, and not a segment, object. If the total size of the " "source segment objects exceeds 5 GB, the ``COPY`` request fails. However, " "you can make a duplicate of the manifest object and this new object can be " "larger than 5 GB." msgstr "" #: ../cli_swift_large_object_creation.rst:55 msgid "" "To create a static large object, divide your content into pieces and create " "(upload) a segment object to contain each piece." msgstr "" #: ../cli_swift_large_object_creation.rst:58 msgid "" "You must record the ``ETag`` response header value that the ``PUT`` " "operation returns. Alternatively, you can calculate the MD5 checksum of the " "segment before you perform the upload and include this value in the ``ETag`` " "request header. This action ensures that the upload cannot corrupt your data." msgstr "" #: ../cli_swift_large_object_creation.rst:63 msgid "" "List the name of each segment object along with its size and MD5 checksum in " "order." msgstr "" #: ../cli_swift_large_object_creation.rst:66 msgid "" "Create a manifest object. Include the ``?multipart-manifest=put`` query " "string at the end of the manifest object name to indicate that this is a " "manifest object." msgstr "" #: ../cli_swift_large_object_creation.rst:70 msgid "" "The body of the ``PUT`` request on the manifest object comprises a JSON list " "where each element contains these attributes:" msgstr "" #: ../cli_swift_large_object_creation.rst:74 msgid "" "The container and object name in the format: ``CONTAINER_NAME/OBJECT_NAME``." msgstr "" #: ../cli_swift_large_object_creation.rst:75 msgid "path" msgstr "" #: ../cli_swift_large_object_creation.rst:78 msgid "" "The MD5 checksum of the content of the segment object. This value must match " "the ``ETag`` of that object." msgstr "" #: ../cli_swift_large_object_creation.rst:79 msgid "etag" msgstr "" #: ../cli_swift_large_object_creation.rst:82 msgid "" "The size of the segment object. This value must match the ``Content-Length`` " "of that object." msgstr "" #: ../cli_swift_large_object_creation.rst:83 msgid "size_bytes" msgstr "" #: ../cli_swift_large_object_creation.rst:86 msgid "Static large object manifest list" msgstr "" #: ../cli_swift_large_object_creation.rst:88 msgid "" "This example shows three segment objects. You can use several containers and " "the object names do not have to conform to a specific pattern, in contrast " "to dynamic large objects." msgstr "" #: ../cli_swift_large_object_creation.rst:114 msgid "" "The ``Content-Length`` request header must contain the length of the JSON " "content and not the length of the segment objects. However, after the " "``PUT`` operation completes, the ``Content-Length`` metadata is set to the " "total length of all the object segments. A similar situation applies to the " "``ETag``. If used in the ``PUT`` operation, it must contain the MD5 checksum " "of the JSON content. The ``ETag`` metadata value is then set to be the MD5 " "checksum of the concatenated ``ETag`` values of the object segments. You can " "also set the ``Content-Type`` request header and custom object metadata." msgstr "" #: ../cli_swift_large_object_creation.rst:124 msgid "" "When the ``PUT`` operation sees the ``?multipart-manifest=put`` query " "parameter, it reads the request body and verifies that each segment object " "exists and that the sizes and ETags match. If there is a mismatch, the " "``PUT`` operation fails." msgstr "" #: ../cli_swift_large_object_creation.rst:129 msgid "" "If everything matches, the API creates the manifest object and sets the ``X-" "Static-Large-Object`` metadata to ``true`` to indicate that the manifest is " "a static object manifest." msgstr "" #: ../cli_swift_large_object_creation.rst:133 msgid "" "Normally when you perform a ``GET`` operation on the manifest object, the " "response body contains the concatenated content of the segment objects. To " "download the manifest list, use the ``?multipart-manifest=get`` query " "parameter. The list in the response is not formatted the same as the " "manifest that you originally used in the ``PUT`` operation." msgstr "" #: ../cli_swift_large_object_creation.rst:139 msgid "" "If you use the ``DELETE`` operation on a manifest object, the manifest " "object is deleted. The segment objects are not affected. However, if you add " "the ``?multipart-manifest=delete`` query parameter, the segment objects are " "deleted and if all are successfully deleted, the manifest object is also " "deleted." msgstr "" #: ../cli_swift_large_object_creation.rst:145 msgid "" "To change the manifest, use a ``PUT`` operation with the ``?multipart-" "manifest=put`` query parameter. This request creates a manifest object. You " "can also update the object metadata in the usual way." msgstr "" #: ../cli_swift_large_object_creation.rst:155 msgid "" "Before you can upload objects that are larger than 5 GB, you must segment " "them. You upload the segment objects like you do with any other object and " "create a dynamic large manifest object. The manifest object tells Object " "Storage how to find the segment objects that comprise the large object. You " "can still access each segment individually, but when you retrieve the " "manifest object, the API concatenates the segments. You can include any " "number of segments in a single large object." msgstr "" #: ../cli_swift_large_object_creation.rst:163 msgid "" "To ensure the download works correctly, you must upload all the object " "segments to the same container and prefix each object name so that the " "segments sort in correct concatenation order." msgstr "" #: ../cli_swift_large_object_creation.rst:167 msgid "" "You also create and upload a manifest file. The manifest file is a zero-byte " "file with the extra ``X-Object-Manifest`` ``CONTAINER/PREFIX`` header. The " "``CONTAINER`` is the container the object segments are in and ``PREFIX`` is " "the common prefix for all the segments. You must UTF-8-encode and then URL-" "encode the container and common prefix in the ``X-Object-Manifest`` header." msgstr "" #: ../cli_swift_large_object_creation.rst:173 msgid "" "It is best to upload all the segments first and then create or update the " "manifest. With this method, the full object is not available for downloading " "until the upload is complete. Also, you can upload a new set of segments to " "a second location and update the manifest to point to this new location. " "During the upload of the new segments, the original manifest is still " "available to download the first set of segments." msgstr "" #: ../cli_swift_large_object_creation.rst:181 msgid "Upload segment of large object request: HTTP" msgstr "" #: ../cli_swift_large_object_creation.rst:192 msgid "No response body is returned." msgstr "" #: ../cli_swift_large_object_creation.rst:194 msgid "" "The 2``nn`` response code indicates a successful write. ``nn`` is a value " "from 00 to 99." msgstr "" #: ../cli_swift_large_object_creation.rst:197 msgid "" "The ``Length Required (411)`` response code indicates that the request does " "not include a required ``Content-Length`` or ``Content-Type`` header." msgstr "" #: ../cli_swift_large_object_creation.rst:200 msgid "" "The ``Unprocessable Entity (422)`` response code indicates that the MD5 " "checksum of the data written to the storage system does NOT match the " "optional ETag value." msgstr "" #: ../cli_swift_large_object_creation.rst:204 msgid "" "You can continue to upload segments, like this example shows, before you " "upload the manifest." msgstr "" #: ../cli_swift_large_object_creation.rst:208 msgid "Upload next segment of large object request: HTTP" msgstr "" #: ../cli_swift_large_object_creation.rst:219 msgid "" "Next, upload the manifest. This manifest specifies the container where the " "object segments reside. Note that if you upload additional segments after " "you create the manifest, the concatenated object becomes that much larger " "but you do not need to recreate the manifest file for subsequent additional " "segments." msgstr "" #: ../cli_swift_large_object_creation.rst:225 msgid "Upload manifest request: HTTP" msgstr "" #: ../cli_swift_large_object_creation.rst:237 msgid "Upload manifest response: HTTP" msgstr "" #: ../cli_swift_large_object_creation.rst:242 msgid "" "A ``GET`` or ``HEAD`` request on the manifest returns a ``Content-Type`` " "response header value that is the same as the ``Content-Type`` request " "header value in the ``PUT`` request that created the manifest. To change the " "``Content- Type``, reissue the ``PUT`` request." msgstr "" #: ../cli_swift_large_object_creation.rst:248 msgid "Extra transaction information" msgstr "" #: ../cli_swift_large_object_creation.rst:250 msgid "" "You can use the ``X-Trans-Id-Extra`` request header to include extra " "information to help you debug any errors that might occur with large object " "upload and other Object Storage transactions." msgstr "" #: ../cli_swift_large_object_creation.rst:254 msgid "" "The Object Storage API appends the first 32 characters of the ``X-Trans-Id-" "Extra`` request header value to the transaction ID value in the generated " "``X-Trans-Id`` response header. You must UTF-8-encode and then URL-encode " "the extra transaction information before you include it in the ``X-Trans-Id-" "Extra`` request header." msgstr "" #: ../cli_swift_large_object_creation.rst:260 msgid "" "For example, you can include extra transaction information when you upload " "large objects such as images." msgstr "" #: ../cli_swift_large_object_creation.rst:263 msgid "" "When you upload each segment and the manifest, include the same value in the " "``X-Trans-Id-Extra`` request header. If an error occurs, you can find all " "requests that are related to the large object upload in the Object Storage " "logs." msgstr "" #: ../cli_swift_large_object_creation.rst:268 msgid "" "You can also use ``X-Trans-Id-Extra`` strings to help operators debug " "requests that fail to receive responses. The operator can search for the " "extra information in the logs." msgstr "" #: ../cli_swift_large_object_creation.rst:273 msgid "Comparison of static and dynamic large objects" msgstr "" #: ../cli_swift_large_object_creation.rst:275 msgid "" "While static and dynamic objects have similar behavior, this table describes " "their differences:" msgstr "" # #-#-#-#-# cli_swift_large_object_creation.pot (End User Guide 1.0.0) #-#-#-#-# # #-#-#-#-# cli_swift_serialized_response_formats.pot (End User Guide 1.0.0) #-#-#-#-# #: ../cli_swift_large_object_creation.rst:283 #: ../cli_swift_serialized_response_formats.rst:17 msgid "Description" msgstr "" #: ../cli_swift_large_object_creation.rst:284 msgid "Static large object" msgstr "" #: ../cli_swift_large_object_creation.rst:285 msgid "Dynamic large object" msgstr "" #: ../cli_swift_large_object_creation.rst:286 msgid "End-to-end integrity" msgstr "" #: ../cli_swift_large_object_creation.rst:287 msgid "" "Assured. The list of segments includes the MD5 checksum (``ETag``) of each " "segment. You cannot upload the manifest object if the ``ETag`` in the list " "differs from the uploaded segment object. If a segment is somehow lost, an " "attempt to download the manifest object results in an error." msgstr "" #: ../cli_swift_large_object_creation.rst:292 msgid "" "Not guaranteed. The eventual consistency model means that although you have " "uploaded a segment object, it might not appear in the container listing " "until later. If you download the manifest before it appears in the " "container, it does not form part of the content returned in response to a " "``GET`` request." msgstr "" #: ../cli_swift_large_object_creation.rst:298 msgid "Upload order" msgstr "" #: ../cli_swift_large_object_creation.rst:299 msgid "You must upload the segment objects before upload the manifest object." msgstr "" #: ../cli_swift_large_object_creation.rst:301 msgid "" "You can upload manifest and segment objects in any order. You are " "recommended to upload the manifest object after the segments in case a " "premature download of the manifest occurs. However, this is not enforced." msgstr "" #: ../cli_swift_large_object_creation.rst:305 msgid "Removal or addition of segment objects" msgstr "" #: ../cli_swift_large_object_creation.rst:306 msgid "" "You cannot add or remove segment objects from the manifest. However, you can " "create a completely new manifest object of the same name with a different " "manifest list." msgstr "" #: ../cli_swift_large_object_creation.rst:309 msgid "" "You can upload new segment objects or remove existing segments. The names " "must simply match the ``PREFIX`` supplied in ``X-Object-Manifest``." msgstr "" #: ../cli_swift_large_object_creation.rst:312 msgid "Segment object size and number" msgstr "" #: ../cli_swift_large_object_creation.rst:313 msgid "" "Segment objects must be at least 1 MB in size (by default). The final " "segment object can be any size. At most, 1000 segments are supported (by " "default)." msgstr "" #: ../cli_swift_large_object_creation.rst:316 msgid "Segment objects can be any size." msgstr "" #: ../cli_swift_large_object_creation.rst:317 msgid "Segment object container name" msgstr "" #: ../cli_swift_large_object_creation.rst:318 msgid "" "The manifest list includes the container name of each object. Segment " "objects can be in different containers." msgstr "" #: ../cli_swift_large_object_creation.rst:320 msgid "All segment objects must be in the same container." msgstr "" #: ../cli_swift_large_object_creation.rst:321 msgid "Manifest object metadata" msgstr "" #: ../cli_swift_large_object_creation.rst:322 msgid "" "The object has ``X-Static-Large-Object`` set to ``true``. You do not set " "this metadata directly. Instead the system sets it when you ``PUT`` a static " "manifest object." msgstr "" #: ../cli_swift_large_object_creation.rst:325 msgid "" "The ``X-Object-Manifest`` value is the ``CONTAINER/PREFIX``, which indicates " "where the segment objects are located. You supply this request header in the " "``PUT`` operation." msgstr "" #: ../cli_swift_large_object_creation.rst:328 msgid "Copying the manifest object" msgstr "" #: ../cli_swift_large_object_creation.rst:329 msgid "" "Include the ``?multipart-manifest=get`` query string in the ``COPY`` " "request. The new object contains the same manifest as the original. The " "segment objects are not copied. Instead, both the original and new manifest " "objects share the same set of segment objects." msgstr "" #: ../cli_swift_large_object_creation.rst:334 msgid "" "The ``COPY`` operation does not create a manifest object. To duplicate a " "manifest object, use the ``GET`` operation to read the value of ``X-Object-" "Manifest`` and use this value in the ``X-Object-Manifest`` request header in " "a ``PUT`` operation. This creates a new manifest object that shares the same " "set of segment objects as the original manifest object." msgstr "" #: ../cli_swift_manage_access_swift.rst:3 msgid "Manage access" msgstr "" #: ../cli_swift_manage_access_swift.rst:5 msgid "" "Users have roles on accounts. For example, a user with the admin role has " "full access to all containers and objects in an account. You can set access " "control lists (ACLs) at the container level and support lists for read and " "write access, which you set with the ``X-Container-Read`` and ``X-Container-" "Write`` headers." msgstr "" #: ../cli_swift_manage_access_swift.rst:11 msgid "" "To give a user read access, use the :command:`swift post` command with the :" "option:`-r` parameter. To give a user write access, use the :option:`-w` " "parameter." msgstr "" #: ../cli_swift_manage_access_swift.rst:15 msgid "" "The following example enables the ``testuser`` user to read objects in the " "container:" msgstr "" #: ../cli_swift_manage_access_swift.rst:22 msgid "You can also use this command with a list of users." msgstr "" #: ../cli_swift_manage_access_swift.rst:24 msgid "" "If you use StaticWeb middleware to enable Object Storage to serve public web " "content, use ``.r:``, followed by a list of allowed referrers." msgstr "" #: ../cli_swift_manage_access_swift.rst:28 msgid "The following command gives object access to all referring domains:" msgstr "" #: ../cli_swift_manage_objects.rst:3 msgid "Manage objects" msgstr "" #: ../cli_swift_manage_objects.rst:5 msgid "To upload an object to a container, run the following command:" msgstr "" #: ../cli_swift_manage_objects.rst:11 msgid "To upload in chunks, for large files, run the following command:" msgstr "" #: ../cli_swift_manage_objects.rst:17 msgid "To check the status of the object, run the following command:" msgstr "" #: ../cli_swift_manage_objects.rst:36 msgid "To list the objects in a container, run the following command:" msgstr "" #: ../cli_swift_manage_objects.rst:42 msgid "To download an object from a container, run the following command:" msgstr "" #: ../cli_swift_pseudo_hierarchical_folders_directories.rst:3 msgid "Pseudo-hierarchical folders and directories" msgstr "" #: ../cli_swift_pseudo_hierarchical_folders_directories.rst:5 msgid "" "Although you cannot nest directories in OpenStack Object Storage, you can " "simulate a hierarchical structure within a single container by adding " "forward slash characters (``/``) in the object name. To navigate the pseudo-" "directory structure, you can use the ``delimiter`` query parameter. This " "example shows you how to use pseudo-hierarchical folders and directories." msgstr "" #: ../cli_swift_pseudo_hierarchical_folders_directories.rst:14 msgid "" "In this example, the objects reside in a container called ``backups``. " "Within that container, the objects are organized in a pseudo-directory " "called ``photos``. The container name is not displayed in the example, but " "it is a part of the object URLs. For instance, the URL of the picture ``me." "jpg`` is ``https://storage.swiftdrive.com/v1/CF_xer7_343/backups/photos/me." "jpg``." msgstr "" #: ../cli_swift_pseudo_hierarchical_folders_directories.rst:22 msgid "List pseudo-hierarchical folders request: HTTP" msgstr "" #: ../cli_swift_pseudo_hierarchical_folders_directories.rst:24 msgid "" "To display a list of all the objects in the storage container, use ``GET`` " "without a ``delimiter`` or ``prefix``." msgstr "" #: ../cli_swift_pseudo_hierarchical_folders_directories.rst:32 msgid "" "The system returns status code 2xx (between 200 and 299, inclusive) and the " "requested list of the objects." msgstr "" #: ../cli_swift_pseudo_hierarchical_folders_directories.rst:46 msgid "" "Use the delimiter parameter to limit the displayed results. To use " "``delimiter`` with pseudo-directories, you must use the parameter slash (``/" "``)." msgstr "" #: ../cli_swift_pseudo_hierarchical_folders_directories.rst:55 msgid "" "The system returns status code 2xx (between 200 and 299, inclusive) and the " "requested matching objects. Because you use the slash, only the pseudo-" "directory ``photos/`` displays. The returned values from a slash " "``delimiter`` query are not real objects. The value will refer to a real " "object if it does not end with a slash. The pseudo-directories have no " "content-type, rather, each pseudo-directory has its own ``subdir`` entry in " "the response of JSON and XML results. For example:" msgstr "" #: ../cli_swift_pseudo_hierarchical_folders_directories.rst:114 msgid "" "Use the ``prefix`` and ``delimiter`` parameters to view the objects inside a " "pseudo-directory, including further nested pseudo-directories." msgstr "" #: ../cli_swift_pseudo_hierarchical_folders_directories.rst:122 msgid "" "The system returns status code 2xx (between 200 and 299, inclusive) and the " "objects and pseudo-directories within the top level pseudo-directory." msgstr "" #: ../cli_swift_pseudo_hierarchical_folders_directories.rst:132 msgid "" "You can create an unlimited number of nested pseudo-directories. To navigate " "through them, use a longer ``prefix`` parameter coupled with the " "``delimiter`` parameter. In this sample output, there is a pseudo-directory " "called ``dogs`` within the pseudo-directory ``animals``. To navigate " "directly to the files contained within ``dogs``, enter the following command:" msgstr "" #: ../cli_swift_pseudo_hierarchical_folders_directories.rst:144 msgid "" "The system returns status code 2xx (between 200 and 299, inclusive) and the " "objects and pseudo-directories within the nested pseudo-directory." msgstr "" #: ../cli_swift_serialized_response_formats.rst:3 msgid "Serialized response formats" msgstr "" #: ../cli_swift_serialized_response_formats.rst:5 msgid "" "By default, the Object Storage API uses a ``text/plain`` response format. In " "addition, both JSON and XML data serialization response formats are " "supported." msgstr "" #: ../cli_swift_serialized_response_formats.rst:11 msgid "" "To run the cURL command examples, you must export environment variables. For " "more information, see the section :ref:`env-vars`." msgstr "" #: ../cli_swift_serialized_response_formats.rst:14 msgid "To define the response format, use one of these methods:" msgstr "" #: ../cli_swift_serialized_response_formats.rst:17 msgid "Method" msgstr "" #: ../cli_swift_serialized_response_formats.rst:19 msgid "" "Append this parameter to the URL for a ``GET`` request, where ``format`` is " "``json`` or ``xml``." msgstr "" #: ../cli_swift_serialized_response_formats.rst:19 msgid "format= ``format`` query parameter" msgstr "" #: ../cli_swift_serialized_response_formats.rst:22 msgid "" "Include this header in the ``GET`` request. The valid header values are:" msgstr "" #: ../cli_swift_serialized_response_formats.rst:22 msgid "``Accept`` request header" msgstr "" #: ../cli_swift_serialized_response_formats.rst:25 msgid "text/plain" msgstr "" #: ../cli_swift_serialized_response_formats.rst:26 msgid "Plain text response format. The default." msgstr "" #: ../cli_swift_serialized_response_formats.rst:27 msgid "application/jsontext" msgstr "" #: ../cli_swift_serialized_response_formats.rst:28 msgid "JSON data serialization response format." msgstr "" #: ../cli_swift_serialized_response_formats.rst:29 msgid "application/xml" msgstr "" #: ../cli_swift_serialized_response_formats.rst:30 #: ../cli_swift_serialized_response_formats.rst:32 msgid "XML data serialization response format." msgstr "" #: ../cli_swift_serialized_response_formats.rst:31 msgid "text/xml" msgstr "" #: ../cli_swift_serialized_response_formats.rst:36 msgid "Example 1. JSON example with format query parameter" msgstr "" #: ../cli_swift_serialized_response_formats.rst:38 msgid "" "For example, this request uses the ``format`` query parameter to ask for a " "JSON response:" msgstr "" #: ../cli_swift_serialized_response_formats.rst:59 msgid "" "Object Storage lists container names with additional information in JSON " "format:" msgstr "" #: ../cli_swift_serialized_response_formats.rst:79 msgid "Example 2. XML example with Accept header" msgstr "" #: ../cli_swift_serialized_response_formats.rst:81 msgid "" "This request uses the ``Accept`` request header to ask for an XML response:" msgstr "" #: ../cli_swift_serialized_response_formats.rst:103 msgid "" "Object Storage lists container names with additional information in XML " "format:" msgstr "" #: ../cli_swift_serialized_response_formats.rst:122 msgid "" "The remainder of the examples in this guide use standard, non-serialized " "responses. However, all ``GET`` requests that perform list operations accept " "the ``format`` query parameter or ``Accept`` request header." msgstr "" #: ../cli_swift_set_object_versions.rst:3 msgid "Object versioning" msgstr "" #: ../cli_swift_set_object_versions.rst:5 msgid "" "You can store multiple versions of your content so that you can recover from " "unintended overwrites. Object versioning is an easy way to implement version " "control, which you can use with any type of content." msgstr "" #: ../cli_swift_set_object_versions.rst:11 msgid "" "You cannot version a large-object manifest file, but the large-object " "manifest file can point to versioned segments." msgstr "" #: ../cli_swift_set_object_versions.rst:14 msgid "" "We strongly recommend that you put non-current objects in a different " "container than the container where current object versions reside." msgstr "" #: ../cli_swift_set_object_versions.rst:18 msgid "To enable and use object versioning" msgstr "" #: ../cli_swift_set_object_versions.rst:20 msgid "" "To enable object versioning, ask your cloud provider to set the " "``allow_versions`` option to ``TRUE`` in the container configuration file." msgstr "" #: ../cli_swift_set_object_versions.rst:24 msgid "Create an ``archive`` container to store older versions of objects:" msgstr "" #: ../cli_swift_set_object_versions.rst:38 msgid "Create a ``current`` container to store current versions of objects." msgstr "" #: ../cli_swift_set_object_versions.rst:40 msgid "" "Include the ``X-Versions-Location`` header. This header defines the " "container that holds the non-current versions of your objects. You must " "UTF-8-encode and then URL-encode the container name before you include it in " "the ``X-Versions-Location`` header. This header enables object versioning " "for all objects in the ``current`` container. Changes to objects in the " "``current`` container automatically create non-current versions in the " "``archive`` container." msgstr "" #: ../cli_swift_set_object_versions.rst:61 msgid "Create the first version of an object in the ``current`` container:" msgstr "" #: ../cli_swift_set_object_versions.rst:78 msgid "" "Nothing is written to the non-current version container when you initially " "``PUT`` an object in the ``current`` container. However, subsequent ``PUT`` " "requests that edit an object trigger the creation of a version of that " "object in the ``archive`` container." msgstr "" #: ../cli_swift_set_object_versions.rst:83 msgid "These non-current versions are named as follows:" msgstr "" #: ../cli_swift_set_object_versions.rst:89 msgid "" "Where ``length`` is the 3-character, zero-padded hexadecimal character " "length of the object, ```` is the object name, and " "```` is the time when the object was initially created as a " "current version." msgstr "" #: ../cli_swift_set_object_versions.rst:94 msgid "Create a second version of the object in the ``current`` container:" msgstr "" #: ../cli_swift_set_object_versions.rst:111 msgid "" "Issue a ``GET`` request to a versioned object to get the current version of " "the object. You do not have to do any request redirects or metadata lookups." msgstr "" #: ../cli_swift_set_object_versions.rst:115 msgid "List older versions of the object in the ``archive`` container:" msgstr "" #: ../cli_swift_set_object_versions.rst:138 msgid "" "A ``POST`` request to a versioned object updates only the metadata for the " "object and does not create a new version of the object. New versions are " "created only when the content of the object changes." msgstr "" #: ../cli_swift_set_object_versions.rst:142 msgid "" "Issue a ``DELETE`` request to a versioned object to remove the current " "version of the object and replace it with the next-most current version in " "the non-current container." msgstr "" #: ../cli_swift_set_object_versions.rst:159 msgid "" "List objects in the ``archive`` container to show that the archived object " "was moved back to the ``current`` container:" msgstr "" #: ../cli_swift_set_object_versions.rst:179 msgid "" "This next-most current version carries with it any metadata last set on it. " "If you want to completely remove an object and you have five versions of it, " "you must ``DELETE`` it five times." msgstr "" #: ../cli_swift_set_object_versions.rst:183 msgid "" "To disable object versioning for the ``current`` container, remove its ``X-" "Versions-Location`` metadata header by sending an empty key value." msgstr "" #: ../cli_swift_static_website.rst:5 msgid "Create static website" msgstr "" #: ../cli_swift_static_website.rst:11 msgid "" "You can use your Object Storage account to create a static website. This " "static website is created with Static Web middleware and serves container " "data with a specified index file, error file resolution, and optional file " "listings. This mode is normally active only for anonymous requests, which " "provide no authentication token. To use it with authenticated requests, set " "the header ``X-Web-Mode`` to ``TRUE`` on the request." msgstr "" #: ../cli_swift_static_website.rst:18 msgid "" "The Static Web filter must be added to the pipeline in your ``/etc/swift/" "proxy-server.conf`` file below any authentication middleware. You must also " "add a Static Web middleware configuration section." msgstr "" #: ../cli_swift_static_website.rst:23 msgid "" "See the Cloud Administrator Guide for an example of the `static web " "configuration syntax `_." msgstr "" #: ../cli_swift_static_website.rst:25 msgid "" "See the Cloud Administrator Guide for a complete example of the `/etc/swift/" "proxy-server.conf file `_ " "(including static web)." msgstr "" #: ../cli_swift_static_website.rst:28 msgid "" "Your publicly readable containers are checked for two headers, ``X-Container-" "Meta-Web-Index`` and ``X-Container-Meta-Web-Error``. The ``X-Container-Meta-" "Web-Error`` header is discussed below, in the section called :ref:" "`set_error_static_website`." msgstr "" #: ../cli_swift_static_website.rst:33 msgid "" "Use ``X-Container-Meta-Web-Index`` to determine the index file (or default " "page served, such as ``index.html``) for your website. When someone " "initially enters your site, the ``index.html`` file displays automatically. " "If you create sub-directories for your site by creating pseudo-directories " "in your container, the index page for each sub-directory is displayed by " "default. If your pseudo-directory does not have a file with the same name as " "your index file, visits to the sub-directory return a 404 error." msgstr "" #: ../cli_swift_static_website.rst:42 msgid "" "You also have the option of displaying a list of files in your pseudo-" "directory instead of a web page. To do this, set the ``X-Container-Meta-Web-" "Listings`` header to ``TRUE``. You may add styles to your file listing by " "setting ``X-Container-Meta-Web-Listings-CSS`` to a style sheet (for example, " "``lists.css``)." msgstr "" #: ../cli_swift_static_website.rst:49 msgid "Static Web middleware through Object Storage" msgstr "" #: ../cli_swift_static_website.rst:51 msgid "" "The following sections show how to use Static Web middleware through Object " "Storage." msgstr "" #: ../cli_swift_static_website.rst:55 msgid "Make container publicly readable" msgstr "" #: ../cli_swift_static_website.rst:57 msgid "" "Make the container publicly readable. Once the container is publicly " "readable, you can access your objects directly, but you must set the index " "file to browse the main site URL and its sub-directories." msgstr "" #: ../cli_swift_static_website.rst:67 msgid "Set site index file" msgstr "" #: ../cli_swift_static_website.rst:69 msgid "" "Set the index file. In this case, ``index.html`` is the default file " "displayed when the site appears." msgstr "" #: ../cli_swift_static_website.rst:77 msgid "Enable file listing" msgstr "" #: ../cli_swift_static_website.rst:79 msgid "" "Turn on file listing. If you do not set the index file, the URL displays a " "list of the objects in the container. Instructions on styling the list with " "a CSS follow." msgstr "" #: ../cli_swift_static_website.rst:88 msgid "Enable CSS for file listing" msgstr "" #: ../cli_swift_static_website.rst:90 msgid "Style the file listing using a CSS." msgstr "" #: ../cli_swift_static_website.rst:99 msgid "Set error pages for static website" msgstr "" #: ../cli_swift_static_website.rst:101 msgid "" "You can create and set custom error pages for visitors to your website; " "currently, only 401 (Unauthorized) and 404 (Not Found) errors are supported. " "To do this, set the metadata header, ``X-Container-Meta-Web-Error``." msgstr "" #: ../cli_swift_static_website.rst:106 msgid "" "Error pages are served with the status code pre-pended to the name of the " "error page you set. For instance, if you set ``X-Container-Meta-Web-Error`` " "to ``error.html``, 401 errors will display the page ``401error.html``. " "Similarly, 404 errors will display ``404error.html``. You must have both of " "these pages created in your container when you set the ``X-Container-Meta-" "Web-Error`` metadata, or your site will display generic error pages." msgstr "" #: ../cli_swift_static_website.rst:114 msgid "" "You only have to set the ``X-Container-Meta-Web-Error`` metadata once for " "your entire static website." msgstr "" #: ../cli_swift_static_website.rst:118 msgid "Set error pages for static website request" msgstr "" #: ../cli_swift_static_website.rst:125 msgid "Any 2\\ ``nn`` response indicates success." msgstr "" #: ../cli_use_snapshots_to_migrate_instances.rst:3 msgid "Use snapshots to migrate instances" msgstr "" #: ../cli_use_snapshots_to_migrate_instances.rst:5 msgid "" "To use snapshots to migrate instances from OpenStack projects to clouds, " "complete these steps." msgstr "" #: ../cli_use_snapshots_to_migrate_instances.rst:8 msgid "In the source project:" msgstr "" #: ../cli_use_snapshots_to_migrate_instances.rst:10 msgid ":ref:`Create_a_snapshot_of_the_instance`" msgstr "" #: ../cli_use_snapshots_to_migrate_instances.rst:12 msgid ":ref:`Download_the_snapshot_as_an_image`" msgstr "" #: ../cli_use_snapshots_to_migrate_instances.rst:14 msgid "In the destination project:" msgstr "" #: ../cli_use_snapshots_to_migrate_instances.rst:16 msgid ":ref:`Import_the_snapshot_to_the_new_environment`" msgstr "" #: ../cli_use_snapshots_to_migrate_instances.rst:18 msgid ":ref:`Boot_a_new_instance_from_the_snapshot`" msgstr "" #: ../cli_use_snapshots_to_migrate_instances.rst:22 msgid "Some cloud providers allow only administrators to perform this task." msgstr "" #: ../cli_use_snapshots_to_migrate_instances.rst:27 msgid "Create a snapshot of the instance" msgstr "" #: ../cli_use_snapshots_to_migrate_instances.rst:29 msgid "" "Shut down the source VM before you take the snapshot to ensure that all data " "is flushed to disk. If necessary, list the instances to view the instance " "name:" msgstr "" #: ../cli_use_snapshots_to_migrate_instances.rst:42 msgid "Use the :command:`nova stop` command to shut down the instance:" msgstr "" #: ../cli_use_snapshots_to_migrate_instances.rst:48 msgid "" "Use the :command:`nova list` command to confirm that the instance shows a " "``SHUTOFF`` status:" msgstr "" #: ../cli_use_snapshots_to_migrate_instances.rst:60 msgid "Use the :command:`nova image-create` command to take a snapshot:" msgstr "" #: ../cli_use_snapshots_to_migrate_instances.rst:67 msgid "" "Use the :command:`nova image-list` command to check the status until the " "status is ``ACTIVE``:" msgstr "" #: ../cli_use_snapshots_to_migrate_instances.rst:85 msgid "Download the snapshot as an image" msgstr "" #: ../cli_use_snapshots_to_migrate_instances.rst:87 msgid "Get the image ID:" msgstr "" #: ../cli_use_snapshots_to_migrate_instances.rst:98 msgid "" "Download the snapshot by using the image ID that was returned in the " "previous step:" msgstr "" #: ../cli_use_snapshots_to_migrate_instances.rst:107 msgid "" "The :command:`glance image-download` command requires the image ID and " "cannot use the image name. Check there is sufficient space on the " "destination file system for the image file." msgstr "" #: ../cli_use_snapshots_to_migrate_instances.rst:112 msgid "" "Make the image available to the new environment, either through HTTP or " "direct upload to a machine (``scp``)." msgstr "" #: ../cli_use_snapshots_to_migrate_instances.rst:118 msgid "Import the snapshot to the new environment" msgstr "" #: ../cli_use_snapshots_to_migrate_instances.rst:120 msgid "In the new project or cloud environment, import the snapshot:" msgstr "" #: ../cli_use_snapshots_to_migrate_instances.rst:130 msgid "Boot a new instance from the snapshot" msgstr "" #: ../cli_use_snapshots_to_migrate_instances.rst:132 msgid "" "In the new project or cloud environment, use the snapshot to create the new " "instance:" msgstr "" #: ../configure_access_and_security_for_instances.rst:5 msgid "" "Before you launch an instance, you should add security group rules to enable " "users to ping and use SSH to connect to the instance. Security groups are " "sets of IP filter rules that define networking access and are applied to all " "instances within a project. To do so, you either add rules to the default " "security group :ref:`security_groups_add_rule` or add a new security group " "with rules." msgstr "" #: ../configure_access_and_security_for_instances.rst:12 msgid "" "Key pairs are SSH credentials that are injected into an instance when it is " "launched. To use key pair injection, the image that the instance is based on " "must contain the ``cloud-init`` package. Each project should have at least " "one key pair. For more information, see the section :ref:`keypair_add`." msgstr "" #: ../configure_access_and_security_for_instances.rst:18 msgid "" "If you have generated a key pair with an external tool, you can import it " "into OpenStack. The key pair can be used for multiple instances that belong " "to a project. For more information, see the section :ref:" "`dashboard_import_keypair`." msgstr "" #: ../configure_access_and_security_for_instances.rst:29 msgid "" "When an instance is created in OpenStack, it is automatically assigned a " "fixed IP address in the network to which the instance is assigned. This IP " "address is permanently associated with the instance until the instance is " "terminated. However, in addition to the fixed IP address, a floating IP " "address can also be attached to an instance. Unlike fixed IP addresses, " "floating IP addresses are able to have their associations modified at any " "time, regardless of the state of the instances involved." msgstr "" #: ../configure_access_and_security_for_instances.rst:40 msgid "Add a rule to the default security group" msgstr "" #: ../configure_access_and_security_for_instances.rst:42 msgid "" "This procedure enables SSH and ICMP (ping) access to instances. The rules " "apply to all instances within a given project, and should be set for every " "project unless there is a reason to prohibit SSH or ICMP access to the " "instances." msgstr "" #: ../configure_access_and_security_for_instances.rst:47 msgid "" "This procedure can be adjusted as necessary to add additional security group " "rules to a project, if your cloud requires them." msgstr "" #: ../configure_access_and_security_for_instances.rst:52 msgid "" "When adding a rule, you must specify the protocol used with the destination " "port or source port." msgstr "" # #-#-#-#-# configure_access_and_security_for_instances.pot (End User Guide 1.0.0) #-#-#-#-# # #-#-#-#-# dashboard_create_networks.pot (End User Guide 1.0.0) #-#-#-#-# # #-#-#-#-# dashboard_databases.pot (End User Guide 1.0.0) #-#-#-#-# # #-#-#-#-# dashboard_launch_instances.pot (End User Guide 1.0.0) #-#-#-#-# # #-#-#-#-# dashboard_manage_containers.pot (End User Guide 1.0.0) #-#-#-#-# # #-#-#-#-# dashboard_manage_images.pot (End User Guide 1.0.0) #-#-#-#-# # #-#-#-#-# dashboard_manage_volumes.pot (End User Guide 1.0.0) #-#-#-#-# # #-#-#-#-# dashboard_stacks.pot (End User Guide 1.0.0) #-#-#-#-# #: ../configure_access_and_security_for_instances.rst:55 #: ../configure_access_and_security_for_instances.rst:106 #: ../configure_access_and_security_for_instances.rst:128 #: ../configure_access_and_security_for_instances.rst:186 #: ../dashboard_create_networks.rst:19 ../dashboard_create_networks.rst:72 #: ../dashboard_create_networks.rst:114 ../dashboard_databases.rst:60 #: ../dashboard_databases.rst:115 ../dashboard_databases.rst:146 #: ../dashboard_databases.rst:175 ../dashboard_databases.rst:198 #: ../dashboard_launch_instances.rst:19 ../dashboard_launch_instances.rst:233 #: ../dashboard_launch_instances.rst:248 ../dashboard_launch_instances.rst:270 #: ../dashboard_manage_containers.rst:24 ../dashboard_manage_containers.rst:46 #: ../dashboard_manage_containers.rst:80 #: ../dashboard_manage_containers.rst:104 #: ../dashboard_manage_containers.rst:134 #: ../dashboard_manage_containers.rst:161 ../dashboard_manage_images.rst:30 #: ../dashboard_manage_images.rst:103 ../dashboard_manage_images.rst:127 #: ../dashboard_manage_volumes.rst:14 ../dashboard_manage_volumes.rst:64 #: ../dashboard_manage_volumes.rst:97 ../dashboard_manage_volumes.rst:113 #: ../dashboard_manage_volumes.rst:134 ../dashboard_manage_volumes.rst:162 #: ../dashboard_stacks.rst:28 ../dashboard_stacks.rst:122 #: ../dashboard_stacks.rst:141 msgid "Log in to the dashboard." msgstr "" # #-#-#-#-# configure_access_and_security_for_instances.pot (End User Guide 1.0.0) #-#-#-#-# # #-#-#-#-# dashboard_create_networks.pot (End User Guide 1.0.0) #-#-#-#-# # #-#-#-#-# dashboard_launch_instances.pot (End User Guide 1.0.0) #-#-#-#-# # #-#-#-#-# dashboard_manage_containers.pot (End User Guide 1.0.0) #-#-#-#-# # #-#-#-#-# dashboard_manage_images.pot (End User Guide 1.0.0) #-#-#-#-# # #-#-#-#-# dashboard_manage_volumes.pot (End User Guide 1.0.0) #-#-#-#-# # #-#-#-#-# dashboard_stacks.pot (End User Guide 1.0.0) #-#-#-#-# #: ../configure_access_and_security_for_instances.rst:57 #: ../configure_access_and_security_for_instances.rst:108 #: ../configure_access_and_security_for_instances.rst:130 #: ../configure_access_and_security_for_instances.rst:188 #: ../dashboard_create_networks.rst:21 ../dashboard_create_networks.rst:74 #: ../dashboard_launch_instances.rst:21 ../dashboard_launch_instances.rst:235 #: ../dashboard_launch_instances.rst:250 ../dashboard_launch_instances.rst:272 #: ../dashboard_manage_containers.rst:26 ../dashboard_manage_containers.rst:48 #: ../dashboard_manage_containers.rst:82 #: ../dashboard_manage_containers.rst:106 #: ../dashboard_manage_containers.rst:136 #: ../dashboard_manage_containers.rst:163 ../dashboard_manage_images.rst:32 #: ../dashboard_manage_images.rst:105 ../dashboard_manage_images.rst:129 #: ../dashboard_manage_volumes.rst:16 ../dashboard_manage_volumes.rst:66 #: ../dashboard_manage_volumes.rst:99 ../dashboard_manage_volumes.rst:115 #: ../dashboard_manage_volumes.rst:136 ../dashboard_manage_volumes.rst:164 #: ../dashboard_stacks.rst:29 ../dashboard_stacks.rst:123 #: ../dashboard_stacks.rst:142 msgid "Select the appropriate project from the drop down menu at the top left." msgstr "" #: ../configure_access_and_security_for_instances.rst:59 msgid "" "On the :guilabel:`Project` tab, open the :guilabel:`Compute` tab and click :" "guilabel:`Access & Security` category. The :guilabel:`Security Groups` tab " "shows the security groups that are available for this project." msgstr "" #: ../configure_access_and_security_for_instances.rst:64 msgid "Select the default security group and click :guilabel:`Manage Rules`." msgstr "" #: ../configure_access_and_security_for_instances.rst:66 msgid "To allow SSH access, click :guilabel:`Add Rule`." msgstr "" #: ../configure_access_and_security_for_instances.rst:68 #: ../configure_access_and_security_for_instances.rst:87 msgid "In the :guilabel:`Add Rule` dialog box, enter the following values:" msgstr "" #: ../configure_access_and_security_for_instances.rst:70 msgid "**Rule**: ``SSH``" msgstr "" #: ../configure_access_and_security_for_instances.rst:71 #: ../configure_access_and_security_for_instances.rst:91 msgid "**Remote**: ``CIDR``" msgstr "" #: ../configure_access_and_security_for_instances.rst:72 #: ../configure_access_and_security_for_instances.rst:92 msgid "**CIDR**: ``0.0.0.0/0``" msgstr "" #: ../configure_access_and_security_for_instances.rst:76 msgid "" "To accept requests from a particular range of IP addresses, specify the IP " "address block in the :guilabel:`CIDR` box." msgstr "" #: ../configure_access_and_security_for_instances.rst:80 #: ../configure_access_and_security_for_instances.rst:94 msgid "Click :guilabel:`Add`." msgstr "" #: ../configure_access_and_security_for_instances.rst:82 msgid "" "Instances will now have SSH port 22 open for requests from any IP address." msgstr "" #: ../configure_access_and_security_for_instances.rst:85 msgid "To add an ICMP rule, click :guilabel:`Add Rule`." msgstr "" #: ../configure_access_and_security_for_instances.rst:89 msgid "**Rule**: ``All ICMP``" msgstr "" #: ../configure_access_and_security_for_instances.rst:90 msgid "**Direction**: ``Ingress``" msgstr "" #: ../configure_access_and_security_for_instances.rst:96 msgid "Instances will now accept all incoming ICMP packets." msgstr "" #: ../configure_access_and_security_for_instances.rst:103 msgid "Create at least one key pair for each project." msgstr "" #: ../configure_access_and_security_for_instances.rst:110 #: ../configure_access_and_security_for_instances.rst:132 #: ../configure_access_and_security_for_instances.rst:190 msgid "" "On the :guilabel:`Project` tab, open the :guilabel:`Compute` tab and click :" "guilabel:`Access & Security` category." msgstr "" #: ../configure_access_and_security_for_instances.rst:113 #: ../configure_access_and_security_for_instances.rst:135 msgid "" "Click the :guilabel:`Key Pairs` tab, which shows the key pairs that are " "available for this project." msgstr "" #: ../configure_access_and_security_for_instances.rst:116 msgid "Click :guilabel:`Create Key Pair`." msgstr "" #: ../configure_access_and_security_for_instances.rst:118 msgid "" "In the :guilabel:`Create Key Pair` dialog box, enter a name for your key " "pair, and click :guilabel:`Create Key Pair`." msgstr "" #: ../configure_access_and_security_for_instances.rst:121 msgid "Respond to the prompt to download the key pair." msgstr "" #: ../configure_access_and_security_for_instances.rst:138 msgid "Click :guilabel:`Import Key Pair`." msgstr "" #: ../configure_access_and_security_for_instances.rst:140 msgid "" "In the :guilabel:`Import Key Pair` dialog box, enter the name of your key " "pair, copy the public key into the :guilabel:`Public Key` box, and then " "click :guilabel:`Import Key Pair`." msgstr "" #: ../configure_access_and_security_for_instances.rst:144 msgid "Save the ``*.pem`` file locally." msgstr "" #: ../configure_access_and_security_for_instances.rst:146 msgid "" "To change its permissions so that only you can read and write to the file, " "run the following command:" msgstr "" #: ../configure_access_and_security_for_instances.rst:155 msgid "" "If you are using the Dashboard from a Windows computer, use PuTTYgen to load " "the ``*.pem`` file and convert and save it as ``*.ppk``. For more " "information see the `WinSCP web page for PuTTYgen `__." msgstr "" #: ../configure_access_and_security_for_instances.rst:160 msgid "To make the key pair known to SSH, run the :command:`ssh-add` command." msgstr "" #: ../configure_access_and_security_for_instances.rst:166 msgid "The Compute database registers the public key of the key pair." msgstr "" #: ../configure_access_and_security_for_instances.rst:168 msgid "" "The Dashboard lists the key pair on the :guilabel:`Access & Security` tab." msgstr "" #: ../configure_access_and_security_for_instances.rst:171 msgid "Allocate a floating IP address to an instance" msgstr "" #: ../configure_access_and_security_for_instances.rst:173 msgid "" "When an instance is created in OpenStack, it is automatically assigned a " "fixed IP address in the network to which the instance is assigned. This IP " "address is permanently associated with the instance until the instance is " "terminated." msgstr "" #: ../configure_access_and_security_for_instances.rst:178 msgid "" "However, in addition to the fixed IP address, a floating IP address can also " "be attached to an instance. Unlike fixed IP addresses, floating IP addresses " "can have their associations modified at any time, regardless of the state of " "the instances involved. This procedure details the reservation of a floating " "IP address from an existing pool of addresses and the association of that " "address with a specific instance." msgstr "" #: ../configure_access_and_security_for_instances.rst:193 msgid "" "Click the :guilabel:`Floating IPs` tab, which shows the floating IP " "addresses allocated to instances." msgstr "" #: ../configure_access_and_security_for_instances.rst:196 msgid "Click :guilabel:`Allocate IP To Project`." msgstr "" #: ../configure_access_and_security_for_instances.rst:198 msgid "Choose the pool from which to pick the IP address." msgstr "" #: ../configure_access_and_security_for_instances.rst:200 msgid "Click :guilabel:`Allocate IP`." msgstr "" #: ../configure_access_and_security_for_instances.rst:202 msgid "In the :guilabel:`Floating IPs` list, click :guilabel:`Associate`." msgstr "" #: ../configure_access_and_security_for_instances.rst:204 msgid "" "In the :guilabel:`Manage Floating IP Associations` dialog box, choose the " "following options:" msgstr "" #: ../configure_access_and_security_for_instances.rst:207 msgid "" "The :guilabel:`IP Address` field is filled automatically, but you can add a " "new IP address by clicking the :guilabel:`+` button." msgstr "" #: ../configure_access_and_security_for_instances.rst:211 msgid "" "In the :guilabel:`Port to be associated` field, select a port from the list." msgstr "" #: ../configure_access_and_security_for_instances.rst:214 msgid "The list shows all the instances with their fixed IP addresses." msgstr "" #: ../configure_access_and_security_for_instances.rst:216 msgid "Click :guilabel:`Associate`." msgstr "" #: ../configure_access_and_security_for_instances.rst:220 msgid "" "To disassociate an IP address from an instance, click the :guilabel:" "`Disassociate` button." msgstr "" #: ../configure_access_and_security_for_instances.rst:223 msgid "" "To release the floating IP address back into the pool of addresses, click " "the :guilabel:`Release Floating IP` option at the :guilabel:`Actions` column." msgstr "" #: ../create_db.rst:5 ../create_db.rst:13 msgid "Create and access a database" msgstr "" #: ../create_db.rst:6 msgid "" "Assume that you have installed the Database service and populated your data " "store with images for the type and versions of databases that you want, and " "that you can create and access a database." msgstr "" #: ../create_db.rst:10 msgid "This example shows you how to create and access a MySQL 5.5 database." msgstr "" #: ../create_db.rst:15 msgid "**Determine which flavor to use for your database**" msgstr "" #: ../create_db.rst:17 msgid "" "When you create a database instance, you must specify a nova flavor. The " "flavor indicates various characteristics of the instance, such as RAM, root " "volume size, and so on. The default nova flavors are not sufficient to " "create database instances. You might need to create or obtain some new nova " "flavors that work for databases." msgstr "" #: ../create_db.rst:23 msgid "" "The first step is to list flavors by using the :command:`nova flavor-list` " "command." msgstr "" #: ../create_db.rst:26 msgid "" "Here are the default flavors, although you may have additional custom " "flavors in your environment:" msgstr "" #: ../create_db.rst:43 msgid "" "Now take a look at the minimum requirements for various database instances:" msgstr "" #: ../create_db.rst:47 msgid "Database" msgstr "" #: ../create_db.rst:47 msgid "Disk (GB)" msgstr "" #: ../create_db.rst:47 msgid "RAM (MB)" msgstr "" #: ../create_db.rst:47 msgid "VCPUs" msgstr "" #: ../create_db.rst:49 ../create_db.rst:51 ../create_db.rst:53 #: ../create_db.rst:55 msgid "1" msgstr "" #: ../create_db.rst:49 ../create_db.rst:51 ../create_db.rst:53 #: ../create_db.rst:55 msgid "5" msgstr "" #: ../create_db.rst:49 ../create_db.rst:55 msgid "512" msgstr "" #: ../create_db.rst:49 msgid "MySQL" msgstr "" #: ../create_db.rst:51 msgid "2048" msgstr "" #: ../create_db.rst:51 msgid "Cassandra" msgstr "" #: ../create_db.rst:53 msgid "1024" msgstr "" #: ../create_db.rst:53 msgid "MongoDB" msgstr "" #: ../create_db.rst:55 msgid "Redis" msgstr "" #: ../create_db.rst:58 msgid "" "If you have a custom flavor that meets the needs of the database that you " "want to create, proceed to :ref:`Step 2 ` and use " "that flavor." msgstr "" #: ../create_db.rst:62 msgid "" "If your environment does not have a suitable flavor, an administrative user " "must create a custom flavor by using the :command:`nova flavor-create` " "command." msgstr "" #: ../create_db.rst:66 msgid "" "**MySQL example.** This example creates a flavor that you can use with a " "MySQL database. This example has the following attributes:" msgstr "" #: ../create_db.rst:69 msgid "Flavor name: ``mysql_minimum``" msgstr "" #: ../create_db.rst:71 msgid "" "Flavor ID: You must use an ID that is not already in use. In this example, " "IDs 1 through 5 are in use, so use ID ``6``." msgstr "" #: ../create_db.rst:74 msgid "RAM: ``512``" msgstr "" #: ../create_db.rst:76 msgid "Root volume size in GB: ``5``" msgstr "" #: ../create_db.rst:78 msgid "Virtual CPUs: ``1``" msgstr "" #: ../create_db.rst:91 msgid "**Create a database instance**" msgstr "" #: ../create_db.rst:93 msgid "" "This example creates a database instance with the following characteristics:" msgstr "" #: ../create_db.rst:96 msgid "Name of the instance: ``mysql_instance_1``" msgstr "" #: ../create_db.rst:98 msgid "Database flavor: ``6``" msgstr "" #: ../create_db.rst:100 msgid "In addition, this command specifies these options for the instance:" msgstr "" #: ../create_db.rst:102 msgid "A volume size of ``5`` (5 GB)." msgstr "" #: ../create_db.rst:104 msgid "The ``myDB`` database." msgstr "" #: ../create_db.rst:106 msgid "" "The database is based on the ``mysql`` data store and the ``mysql-5.5`` " "datastore\\_version." msgstr "" #: ../create_db.rst:109 msgid "The ``userA`` user with the ``password`` password." msgstr "" #: ../create_db.rst:130 msgid "**Get the IP address of the database instance**" msgstr "" #: ../create_db.rst:132 msgid "" "First, use the :command:`trove list` command to list all instances and their " "IDs:" msgstr "" #: ../create_db.rst:144 msgid "This command returns the instance ID of your new instance." msgstr "" #: ../create_db.rst:146 msgid "" "You can now pass in the instance ID with the :command:`trove show` command " "to get the IP address of the instance. In this example, replace " "``INSTANCE_ID`` with ``5599dad6-731e-44df-bb60-488da3da9cfe``." msgstr "" #: ../create_db.rst:169 msgid "This command returns the IP address of the database instance." msgstr "" #: ../create_db.rst:171 msgid "**Access the new database**" msgstr "" #: ../create_db.rst:173 msgid "" "You can now access the new database you just created (myDB) by using typical " "database access commands. In this MySQL example, replace ``IP_ADDRESS`` with " "``172.16.200.2``." msgstr "" #: ../dashboard.rst:3 msgid "OpenStack dashboard" msgstr "" #: ../dashboard.rst:5 msgid "" "As a cloud end user, you can use the OpenStack dashboard to provision your " "own resources within the limits set by administrators. You can modify the " "examples provided in this section to create other types and sizes of server " "instances." msgstr "" #: ../dashboard_create_networks.rst:5 msgid "" "The OpenStack Networking service provides a scalable system for managing the " "network connectivity within an OpenStack cloud deployment. It can easily and " "quickly react to changing network needs (for example, creating and assigning " "new IP addresses)." msgstr "" #: ../dashboard_create_networks.rst:10 msgid "" "Networking in OpenStack is complex. This section provides the basic " "instructions for creating a network and a router. For detailed information " "about managing networks, refer to the `OpenStack Administrator Guide `__." msgstr "" #: ../dashboard_create_networks.rst:17 msgid "Create a network" msgstr "" #: ../dashboard_create_networks.rst:23 msgid "" "On the :guilabel:`Project` tab, open the :guilabel:`Network` tab and click :" "guilabel:`Networks` category." msgstr "" #: ../dashboard_create_networks.rst:26 msgid "Click :guilabel:`Create Network`." msgstr "" #: ../dashboard_create_networks.rst:28 msgid "" "In the :guilabel:`Create Network` dialog box, specify the following values." msgstr "" # #-#-#-#-# dashboard_create_networks.pot (End User Guide 1.0.0) #-#-#-#-# # #-#-#-#-# dashboard_log_in.pot (End User Guide 1.0.0) #-#-#-#-# #: ../dashboard_create_networks.rst:30 ../dashboard_log_in.rst:108 msgid ":guilabel:`Network` tab" msgstr "" #: ../dashboard_create_networks.rst:32 msgid ":guilabel:`Network Name`: Specify a name to identify the network." msgstr "" #: ../dashboard_create_networks.rst:34 msgid ":guilabel:`Admin State`: The state to start the network in." msgstr "" #: ../dashboard_create_networks.rst:36 msgid ":guilabel:`Create Subnet`: Select this check box to create a subnet" msgstr "" #: ../dashboard_create_networks.rst:38 msgid "" "You do not have to specify a subnet when you create a network, but if you do " "not specify a subnet, any attached instance receives an Error status." msgstr "" #: ../dashboard_create_networks.rst:41 msgid ":guilabel:`Subnet` tab" msgstr "" #: ../dashboard_create_networks.rst:43 msgid ":guilabel:`Subnet Name`: Specify a name for the subnet." msgstr "" #: ../dashboard_create_networks.rst:45 msgid ":guilabel:`Network Address`: Specify the IP address for the subnet." msgstr "" #: ../dashboard_create_networks.rst:47 msgid ":guilabel:`IP Version`: Select IPv4 or IPv6." msgstr "" #: ../dashboard_create_networks.rst:49 msgid "" ":guilabel:`Gateway IP`: Specify an IP address for a specific gateway. This " "parameter is optional." msgstr "" #: ../dashboard_create_networks.rst:52 msgid "" ":guilabel:`Disable Gateway`: Select this check box to disable a gateway IP " "address." msgstr "" #: ../dashboard_create_networks.rst:55 msgid ":guilabel:`Subnet Details` tab" msgstr "" #: ../dashboard_create_networks.rst:57 msgid ":guilabel:`Enable DHCP`: Select this check box to enable DHCP." msgstr "" #: ../dashboard_create_networks.rst:59 msgid ":guilabel:`Allocation Pools`: Specify IP address pools." msgstr "" #: ../dashboard_create_networks.rst:61 msgid ":guilabel:`DNS Name Servers`: Specify a name for the DNS server." msgstr "" #: ../dashboard_create_networks.rst:63 msgid ":guilabel:`Host Routes`: Specify the IP address of host routes." msgstr "" # #-#-#-#-# dashboard_create_networks.pot (End User Guide 1.0.0) #-#-#-#-# # #-#-#-#-# dashboard_manage_containers.pot (End User Guide 1.0.0) #-#-#-#-# #: ../dashboard_create_networks.rst:65 ../dashboard_manage_containers.rst:181 msgid "Click :guilabel:`Create`." msgstr "" #: ../dashboard_create_networks.rst:67 msgid "The dashboard shows the network on the :guilabel:`Networks` tab." msgstr "" #: ../dashboard_create_networks.rst:70 msgid "Create a router" msgstr "" #: ../dashboard_create_networks.rst:76 msgid "" "On the :guilabel:`Project` tab, open the :guilabel:`Network` tab and click :" "guilabel:`Routers` category." msgstr "" #: ../dashboard_create_networks.rst:79 msgid "Click :guilabel:`Create Router`." msgstr "" #: ../dashboard_create_networks.rst:81 msgid "" "In the :guilabel:`Create Router` dialog box, specify a name for the router " "and :guilabel:`External Network`, and click :guilabel:`Create Router`." msgstr "" #: ../dashboard_create_networks.rst:84 msgid "The new router is now displayed in the :guilabel:`Routers` tab." msgstr "" #: ../dashboard_create_networks.rst:86 msgid "" "To connect a private network to the newly created router, perform the " "following steps:" msgstr "" #: ../dashboard_create_networks.rst:89 msgid "On the :guilabel:`Routers` tab, click the name of the router." msgstr "" #: ../dashboard_create_networks.rst:91 msgid "" "On the :guilabel:`Router Details` page, click the :guilabel:`Interfaces` " "tab, then click :guilabel:`Add Interface`." msgstr "" #: ../dashboard_create_networks.rst:94 msgid "" "In the :guilabel:`Add Interface` dialog box, select a :guilabel:`Subnet`." msgstr "" #: ../dashboard_create_networks.rst:96 msgid "" "Optionally, in the :guilabel:`Add Interface` dialog box, set an :guilabel:" "`IP Address` for the router interface for the selected subnet." msgstr "" #: ../dashboard_create_networks.rst:99 msgid "" "If you choose not to set the :guilabel:`IP Address` value, then by default " "OpenStack Networking uses the first host IP address in the subnet." msgstr "" #: ../dashboard_create_networks.rst:103 msgid "" "The :guilabel:`Router Name` and :guilabel:`Router ID` fields are " "automatically updated." msgstr "" #: ../dashboard_create_networks.rst:106 msgid "Click :guilabel:`Add Interface`." msgstr "" #: ../dashboard_create_networks.rst:108 msgid "" "You have successfully created the router. You can view the new topology from " "the :guilabel:`Network Topology` tab." msgstr "" #: ../dashboard_create_networks.rst:112 msgid "Create a port" msgstr "" #: ../dashboard_create_networks.rst:116 msgid "Select the appropriate project from the drop-down menu at the top left." msgstr "" #: ../dashboard_create_networks.rst:118 msgid "On the :guilabel:`Admin` tab, click :guilabel:`Networks` category." msgstr "" #: ../dashboard_create_networks.rst:120 msgid "" "Click on the :guilabel:`Network Name` of the network in which the port has " "to be created." msgstr "" #: ../dashboard_create_networks.rst:123 msgid "" "In the :guilabel:`Create Port` dialog box, specify the following values." msgstr "" #: ../dashboard_create_networks.rst:125 msgid ":guilabel:`Name`: Specify name to identify the port." msgstr "" #: ../dashboard_create_networks.rst:127 msgid ":guilabel:`Device ID`: Device ID attached to the port." msgstr "" #: ../dashboard_create_networks.rst:129 msgid ":guilabel:`Device Owner`: Device owner attached to the port." msgstr "" #: ../dashboard_create_networks.rst:131 msgid "" ":guilabel:`Binding Host`: The ID of the host where the port is allocated." msgstr "" #: ../dashboard_create_networks.rst:133 msgid "" ":guilabel:`Binding VNIC Type`: Select the VNIC type that is bound to the " "neutron port." msgstr "" #: ../dashboard_create_networks.rst:136 msgid "Click :guilabel:`Create Port`." msgstr "" #: ../dashboard_create_networks.rst:138 msgid "The new port is now displayed in the :guilabel:`Ports` list." msgstr "" # #-#-#-#-# dashboard_databases.pot (End User Guide 1.0.0) #-#-#-#-# # #-#-#-#-# trove-manage-db.pot (End User Guide 1.0.0) #-#-#-#-# #: ../dashboard_databases.rst:3 ../trove-manage-db.rst:3 msgid "Create and manage databases" msgstr "" # #-#-#-#-# dashboard_databases.pot (End User Guide 1.0.0) #-#-#-#-# # #-#-#-#-# trove-manage-db.pot (End User Guide 1.0.0) #-#-#-#-# #: ../dashboard_databases.rst:5 ../trove-manage-db.rst:5 msgid "" "The Database service provides scalable and reliable cloud provisioning " "functionality for both relational and non-relational database engines. Users " "can quickly and easily use database features without the burden of handling " "complex administrative tasks." msgstr "" #: ../dashboard_databases.rst:13 msgid "Create a database instance" msgstr "" #: ../dashboard_databases.rst:15 msgid "" "**Prerequisites.** Before you create a database instance, you need to " "configure a default datastore and make sure you have an appropriate flavor " "for the type of database instance you want." msgstr "" #: ../dashboard_databases.rst:19 msgid "**Configure a default datastore.**" msgstr "" #: ../dashboard_databases.rst:21 msgid "" "Because the dashboard does not let you choose a specific datastore to use " "with an instance, you need to configure a default datastore. The dashboard " "then uses the default datastore to create the instance." msgstr "" #: ../dashboard_databases.rst:25 msgid "Add the following line to ``/etc/trove/trove.conf``:" msgstr "" #: ../dashboard_databases.rst:31 msgid "" "Replace ``DATASTORE_NAME`` with the name that the administrative user set " "when issuing the :command:`trove-manage` command to create the datastore. " "You can use the trove :command:`datastore-list` command to display the " "datastores that are available in your environment." msgstr "" #: ../dashboard_databases.rst:36 msgid "" "For example, if your MySQL data store name is set to ``mysql``, your entry " "would look like this:" msgstr "" #: ../dashboard_databases.rst:43 msgid "Restart Database services on the controller node:" msgstr "" #: ../dashboard_databases.rst:51 msgid "**Verify flavor.**" msgstr "" #: ../dashboard_databases.rst:53 msgid "" "Make sure an appropriate flavor exists for the type of database instance you " "want." msgstr "" #: ../dashboard_databases.rst:56 msgid "" "**Create database instance.** Once you have configured a default datastore " "and verified that you have an appropriate flavor, you can create a database " "instance." msgstr "" #: ../dashboard_databases.rst:62 ../dashboard_databases.rst:117 #: ../dashboard_databases.rst:148 ../dashboard_databases.rst:177 #: ../dashboard_databases.rst:200 msgid "" "From the CURRENT PROJECT on the :guilabel:`Project` tab, select the " "appropriate project." msgstr "" #: ../dashboard_databases.rst:65 msgid "" "On the :guilabel:`Project` tab, open the :guilabel:`Database` tab and click :" "guilabel:`Instances` category. This lists the instances that already exist " "in your environment." msgstr "" # #-#-#-#-# dashboard_databases.pot (End User Guide 1.0.0) #-#-#-#-# # #-#-#-#-# dashboard_launch_instances.pot (End User Guide 1.0.0) #-#-#-#-# #: ../dashboard_databases.rst:69 ../dashboard_launch_instances.rst:29 msgid "Click :guilabel:`Launch Instance`." msgstr "" #: ../dashboard_databases.rst:71 msgid "" "In the :guilabel:`Launch Database` dialog box, specify the following values." msgstr "" #: ../dashboard_databases.rst:73 msgid "Details" msgstr "" #: ../dashboard_databases.rst:75 msgid ":guilabel:`Database Name`: Specify a name for the database instance." msgstr "" #: ../dashboard_databases.rst:77 msgid ":guilabel:`Flavor`: Select an appropriate flavor for the instance." msgstr "" #: ../dashboard_databases.rst:79 msgid "" ":guilabel:`Volume Size`: Select a volume size. Volume size is expressed in " "GB." msgstr "" #: ../dashboard_databases.rst:82 msgid ":guilabel:`Initialize Databases`: Initial Database" msgstr "" #: ../dashboard_databases.rst:84 msgid "" "Optionally provide a comma separated list of databases to create, for " "example:" msgstr "" #: ../dashboard_databases.rst:87 msgid "``database1``, ``database2``, ``database3``" msgstr "" #: ../dashboard_databases.rst:89 msgid "" ":guilabel:`Initial Admin User`: Create an initial admin user. This user will " "have access to all the databases you create." msgstr "" #: ../dashboard_databases.rst:92 msgid "" ":guilabel:`Password`: Specify a password associated with the initial admin " "user you just named." msgstr "" #: ../dashboard_databases.rst:95 msgid "" ":guilabel:`Host`: Optionally, allow the user to connect only from this host. " "If you do not specify a host, this user will be allowed to connect from " "anywhere." msgstr "" #: ../dashboard_databases.rst:99 msgid "" "Click the :guilabel:`Launch` button. The new database instance appears in " "the databases list." msgstr "" #: ../dashboard_databases.rst:113 msgid "To backup the database instance" msgstr "" #: ../dashboard_databases.rst:120 ../dashboard_databases.rst:180 #: ../dashboard_databases.rst:203 msgid "" "On the :guilabel:`Project` tab, open the :guilabel:`Database` tab and click :" "guilabel:`Instances` category. This displays the existing instances in your " "system." msgstr "" #: ../dashboard_databases.rst:124 msgid "Click :guilabel:`Create Backup`." msgstr "" #: ../dashboard_databases.rst:126 msgid "" "In the :guilabel:`Backup Database` dialog box, specify the following values:" msgstr "" #: ../dashboard_databases.rst:129 msgid "Name" msgstr "" #: ../dashboard_databases.rst:131 msgid "Specify a name for the backup." msgstr "" #: ../dashboard_databases.rst:133 msgid "Database Instance" msgstr "" #: ../dashboard_databases.rst:135 msgid "Select the instance you want to back up." msgstr "" #: ../dashboard_databases.rst:137 msgid "Click :guilabel:`Backup`. The new backup appears in the backup list." msgstr "" #: ../dashboard_databases.rst:140 msgid "To restore a database instance" msgstr "" #: ../dashboard_databases.rst:142 msgid "" "Now assume that your original database instance is damaged and you need to " "restore it. You do the restore by using your backup to create a new database " "instance." msgstr "" #: ../dashboard_databases.rst:151 msgid "" "On the :guilabel:`Project` tab, open the :guilabel:`Database` tab and click :" "guilabel:`Backups` category. This lists the available backups." msgstr "" #: ../dashboard_databases.rst:154 msgid "Check the backup you want to use and click :guilabel:`Restore Backup`." msgstr "" #: ../dashboard_databases.rst:156 msgid "" "In the :guilabel:`Launch Database` dialog box, specify the values you want " "for the new database instance." msgstr "" #: ../dashboard_databases.rst:159 msgid "" "Click the :guilabel:`Restore From Database` tab and make sure that this new " "instance is based on the correct backup." msgstr "" # #-#-#-#-# dashboard_databases.pot (End User Guide 1.0.0) #-#-#-#-# # #-#-#-#-# dashboard_launch_instances.pot (End User Guide 1.0.0) #-#-#-#-# #: ../dashboard_databases.rst:162 ../dashboard_launch_instances.rst:164 msgid "Click :guilabel:`Launch`." msgstr "" #: ../dashboard_databases.rst:164 msgid "The new instance appears in the database instances list." msgstr "" #: ../dashboard_databases.rst:167 msgid "Update a database instance" msgstr "" #: ../dashboard_databases.rst:169 msgid "" "You can change various characteristics of a database instance, such as its " "volume size and flavor." msgstr "" #: ../dashboard_databases.rst:173 msgid "To change the volume size of an instance" msgstr "" #: ../dashboard_databases.rst:184 msgid "" "Check the instance you want to work with. In the :guilabel:`Actions` column, " "expand the drop down menu and select :guilabel:`Resize Volume`." msgstr "" #: ../dashboard_databases.rst:188 msgid "" "In the :guilabel:`Resize Database Volume` dialog box, fill in the :guilabel:" "`New Size` field with an integer indicating the new size you want for the " "instance. Express the size in GB, and note that the new size must be larger " "than the current size." msgstr "" #: ../dashboard_databases.rst:193 msgid "Click :guilabel:`Resize Database Volume`." msgstr "" #: ../dashboard_databases.rst:196 msgid "To change the flavor of an instance" msgstr "" #: ../dashboard_databases.rst:207 msgid "" "Check the instance you want to work with. In the :guilabel:`Actions` column, " "expand the drop down menu and select :guilabel:`Resize Instance`." msgstr "" #: ../dashboard_databases.rst:211 msgid "" "In the :guilabel:`Resize Database Instance` dialog box, expand the drop down " "menu in the :guilabel:`New Flavor` field. Select the new flavor you want for " "the instance." msgstr "" #: ../dashboard_databases.rst:215 msgid "Click :guilabel:`Resize Database Instance`." msgstr "" #: ../dashboard_launch_instances.rst:3 msgid "Launch and manage instances" msgstr "" #: ../dashboard_launch_instances.rst:5 msgid "" "Instances are virtual machines that run inside the cloud. You can launch an " "instance from the following sources:" msgstr "" #: ../dashboard_launch_instances.rst:8 msgid "Images uploaded to the Image service." msgstr "" #: ../dashboard_launch_instances.rst:10 msgid "" "Image that you have copied to a persistent volume. The instance launches " "from the volume, which is provided by the ``cinder-volume`` API through " "iSCSI." msgstr "" #: ../dashboard_launch_instances.rst:14 msgid "Instance snapshot that you took." msgstr "" #: ../dashboard_launch_instances.rst:23 ../dashboard_launch_instances.rst:274 msgid "" "On the :guilabel:`Project` tab, open the :guilabel:`Compute` tab and click :" "guilabel:`Instances` category." msgstr "" #: ../dashboard_launch_instances.rst:26 msgid "" "The dashboard shows the instances with its name, its private and floating IP " "addresses, size, status, task, power state, and so on." msgstr "" #: ../dashboard_launch_instances.rst:31 msgid "" "In the :guilabel:`Launch Instance` dialog box, specify the following values:" msgstr "" #: ../dashboard_launch_instances.rst:33 msgid ":guilabel:`Details` tab" msgstr "" #: ../dashboard_launch_instances.rst:36 msgid "" "By default, this value is set to the availability zone given by the cloud " "provider (for example, ``us-west`` or ``apac-south``). For some cases, it " "could be ``nova``." msgstr "" #: ../dashboard_launch_instances.rst:38 msgid "Availability Zone" msgstr "" #: ../dashboard_launch_instances.rst:41 msgid "Assign a name to the virtual machine." msgstr "" #: ../dashboard_launch_instances.rst:45 msgid "The name you assign here becomes the initial host name of the server." msgstr "" #: ../dashboard_launch_instances.rst:48 msgid "" "After the server is built, if you change the server name in the API or " "change the host name directly, the names are not updated in the dashboard." msgstr "" #: ../dashboard_launch_instances.rst:52 msgid "" "Server names are not guaranteed to be unique when created so you could have " "two instances with the same host name." msgstr "" #: ../dashboard_launch_instances.rst:53 msgid "Instance Name" msgstr "" #: ../dashboard_launch_instances.rst:56 msgid "Specify the size of the instance to launch." msgstr "" #: ../dashboard_launch_instances.rst:60 msgid "" "The flavor is selected based on the size of the image selected for launching " "an instance. For example, while creating an image, if you have entered the " "value in the :guilabel:`Minimum RAM (MB)` field as 2048, then on selecting " "the image, the default flavor is ``m1.small``." msgstr "" #: ../dashboard_launch_instances.rst:64 msgid "Flavor" msgstr "" #: ../dashboard_launch_instances.rst:67 msgid "" "To launch multiple instances, enter a value greater than ``1``. The default " "is ``1``." msgstr "" #: ../dashboard_launch_instances.rst:68 msgid "Instance Count" msgstr "" #: ../dashboard_launch_instances.rst:71 msgid "Your options are:" msgstr "" #: ../dashboard_launch_instances.rst:74 msgid "" "If you choose this option, a new field for :guilabel:`Image Name` displays. " "You can select the image from the list." msgstr "" #: ../dashboard_launch_instances.rst:75 msgid "Boot from image" msgstr "" #: ../dashboard_launch_instances.rst:78 msgid "" "If you choose this option, a new field for :guilabel:`Instance Snapshot` " "displays. You can select the snapshot from the list." msgstr "" #: ../dashboard_launch_instances.rst:79 msgid "Boot from snapshot" msgstr "" #: ../dashboard_launch_instances.rst:82 msgid "" "If you choose this option, a new field for :guilabel:`Volume` displays. You " "can select the volume from the list." msgstr "" #: ../dashboard_launch_instances.rst:83 msgid "Boot from volume" msgstr "" #: ../dashboard_launch_instances.rst:86 msgid "" "With this option, you can boot from an image and create a volume by entering " "the :guilabel:`Device Size` and :guilabel:`Device Name` for your volume. " "Click the :guilabel:`Delete Volume on Instance Delete` option to delete the " "volume on deleting the instance." msgstr "" #: ../dashboard_launch_instances.rst:90 msgid "Boot from image (creates a new volume)" msgstr "" #: ../dashboard_launch_instances.rst:93 msgid "" "Using this option, you can boot from a volume snapshot and create a new " "volume by choosing :guilabel:`Volume Snapshot` from a list and adding a :" "guilabel:`Device Name` for your volume. Click the :guilabel:`Delete Volume " "on Instance Delete` option to delete the volume on deleting the instance." msgstr "" #: ../dashboard_launch_instances.rst:97 msgid "Boot from volume snapshot (creates a new volume)" msgstr "" #: ../dashboard_launch_instances.rst:97 msgid "Instance Boot Source" msgstr "" #: ../dashboard_launch_instances.rst:100 msgid "" "This field changes based on your previous selection. If you have chosen to " "launch an instance using an image, the :guilabel:`Image Name` field " "displays. Select the image name from the dropdown list." msgstr "" #: ../dashboard_launch_instances.rst:102 msgid "Image Name" msgstr "" #: ../dashboard_launch_instances.rst:105 msgid "" "This field changes based on your previous selection. If you have chosen to " "launch an instance using a snapshot, the :guilabel:`Instance Snapshot` field " "displays. Select the snapshot name from the dropdown list." msgstr "" #: ../dashboard_launch_instances.rst:108 msgid "Instance Snapshot" msgstr "" #: ../dashboard_launch_instances.rst:111 msgid "" "This field changes based on your previous selection. If you have chosen to " "launch an instance using a volume, the :guilabel:`Volume` field displays. " "Select the volume name from the dropdown list. If you want to delete the " "volume on instance delete, check the :guilabel:`Delete Volume on Instance " "Delete` option." msgstr "" #: ../dashboard_launch_instances.rst:115 msgid "Volume" msgstr "" #: ../dashboard_launch_instances.rst:117 msgid ":guilabel:`Access & Security` tab" msgstr "" #: ../dashboard_launch_instances.rst:120 msgid "Specify a key pair." msgstr "" #: ../dashboard_launch_instances.rst:122 msgid "" "If the image uses a static root password or a static key set (neither is " "recommended), you do not need to provide a key pair to launch the instance." msgstr "" #: ../dashboard_launch_instances.rst:124 msgid "Key Pair" msgstr "" #: ../dashboard_launch_instances.rst:127 msgid "Activate the security groups that you want to assign to the instance." msgstr "" #: ../dashboard_launch_instances.rst:129 msgid "" "Security groups are a kind of cloud firewall that define which incoming " "network traffic is forwarded to instances." msgstr "" #: ../dashboard_launch_instances.rst:132 msgid "" "If you have not created any security groups, you can assign only the default " "security group to the instance." msgstr "" #: ../dashboard_launch_instances.rst:133 msgid "Security Groups" msgstr "" #: ../dashboard_launch_instances.rst:135 msgid ":guilabel:`Networking` tab" msgstr "" #: ../dashboard_launch_instances.rst:138 msgid "" "To add a network to the instance, click the :guilabel:`+` in the :guilabel:" "`Available Networks` field." msgstr "" #: ../dashboard_launch_instances.rst:140 msgid "Selected Networks" msgstr "" #: ../dashboard_launch_instances.rst:142 msgid ":guilabel:`Network Ports` tab" msgstr "" #: ../dashboard_launch_instances.rst:145 msgid "Activate the ports that you want to assign to the instance." msgstr "" #: ../dashboard_launch_instances.rst:145 msgid "Ports" msgstr "" #: ../dashboard_launch_instances.rst:147 msgid ":guilabel:`Post-Creation` tab" msgstr "" #: ../dashboard_launch_instances.rst:150 msgid "Specify a customization script that runs after your instance launches." msgstr "" #: ../dashboard_launch_instances.rst:151 msgid "Customization Script Source" msgstr "" #: ../dashboard_launch_instances.rst:153 msgid ":guilabel:`Advanced Options` tab" msgstr "" #: ../dashboard_launch_instances.rst:156 msgid "Select the type of disk partition from the dropdown list:" msgstr "" #: ../dashboard_launch_instances.rst:159 msgid "Automatic" msgstr "" #: ../dashboard_launch_instances.rst:159 msgid "Entire disk is single partition and automatically resizes." msgstr "" #: ../dashboard_launch_instances.rst:162 msgid "Disk Partition" msgstr "" #: ../dashboard_launch_instances.rst:162 msgid "Faster build times but requires manual partitioning." msgstr "" #: ../dashboard_launch_instances.rst:162 msgid "Manual" msgstr "" #: ../dashboard_launch_instances.rst:166 msgid "The instance starts on a compute node in the cloud." msgstr "" #: ../dashboard_launch_instances.rst:170 msgid "" "If you did not provide a key pair, security groups, or rules, users can " "access the instance only from inside the cloud through VNC. Even pinging the " "instance is not possible without an ICMP rule configured." msgstr "" #: ../dashboard_launch_instances.rst:174 msgid "" "You can also launch an instance from the :guilabel:`Images` or :guilabel:" "`Volumes` category when you launch an instance from an image or a volume " "respectively." msgstr "" #: ../dashboard_launch_instances.rst:178 msgid "" "When you launch an instance from an image, OpenStack creates a local copy of " "the image on the compute node where the instance starts." msgstr "" #: ../dashboard_launch_instances.rst:181 msgid "" "For details on creating images, see `Creating images manually `_ in the *OpenStack " "Virtual Machine Image Guide*." msgstr "" #: ../dashboard_launch_instances.rst:185 msgid "When you launch an instance from a volume, note the following steps:" msgstr "" #: ../dashboard_launch_instances.rst:187 msgid "" "To select the volume from which to launch, launch an instance from an " "arbitrary image on the volume. The arbitrary image that you select does not " "boot. Instead, it is replaced by the image on the volume that you choose in " "the next steps." msgstr "" #: ../dashboard_launch_instances.rst:192 msgid "" "To boot a Xen image from a volume, the image you launch in must be the same " "type, fully virtualized or paravirtualized, as the one on the volume." msgstr "" #: ../dashboard_launch_instances.rst:196 msgid "" "Select the volume or volume snapshot from which to boot. Enter a device " "name. Enter ``vda`` for KVM images or ``xvda`` for Xen images." msgstr "" #: ../dashboard_launch_instances.rst:200 msgid "Connect to your instance by using SSH" msgstr "" #: ../dashboard_launch_instances.rst:202 msgid "" "To use SSH to connect to your instance, use the downloaded keypair file." msgstr "" #: ../dashboard_launch_instances.rst:207 msgid "The user name is ``ubuntu`` for the Ubuntu cloud images on TryStack." msgstr "" #: ../dashboard_launch_instances.rst:209 msgid "Copy the IP address for your instance." msgstr "" #: ../dashboard_launch_instances.rst:211 msgid "" "Use the :command:`ssh` command to make a secure connection to the instance. " "For example:" msgstr "" #: ../dashboard_launch_instances.rst:218 msgid "At the prompt, type ``yes``." msgstr "" #: ../dashboard_launch_instances.rst:220 msgid "" "It is also possible to SSH into an instance without an SSH keypair, if the " "administrator has enabled root password injection. For more information " "about root password injection, see `Injecting the administrator password " "`_ in the *OpenStack Administrator Guide*." msgstr "" #: ../dashboard_launch_instances.rst:227 msgid "Track usage for instances" msgstr "" #: ../dashboard_launch_instances.rst:229 msgid "" "You can track usage for instances for each project. You can track costs per " "month by showing meters like number of vCPUs, disks, RAM, and uptime for all " "your instances." msgstr "" #: ../dashboard_launch_instances.rst:237 msgid "" "On the :guilabel:`Project` tab, open the :guilabel:`Compute` tab and click :" "guilabel:`Overview` category." msgstr "" #: ../dashboard_launch_instances.rst:240 msgid "" "To query the instance usage for a month, select a month and click :guilabel:" "`Submit`." msgstr "" #: ../dashboard_launch_instances.rst:243 msgid "To download a summary, click :guilabel:`Download CSV Summary`." msgstr "" #: ../dashboard_launch_instances.rst:252 msgid "" "On the :guilabel:`Project` tab, open the :guilabel:`Compute` tab and click " "the :guilabel:`Instances` category." msgstr "" #: ../dashboard_launch_instances.rst:255 msgid "Select the instance from which to create a snapshot." msgstr "" # #-#-#-#-# dashboard_launch_instances.pot (End User Guide 1.0.0) #-#-#-#-# # #-#-#-#-# dashboard_manage_volumes.pot (End User Guide 1.0.0) #-#-#-#-# #: ../dashboard_launch_instances.rst:257 ../dashboard_manage_volumes.rst:122 msgid "In the :guilabel:`Actions` column, click :guilabel:`Create Snapshot`." msgstr "" #: ../dashboard_launch_instances.rst:259 msgid "" "In the :guilabel:`Create Snapshot` dialog box, enter a name for the " "snapshot, and click :guilabel:`Create Snapshot`." msgstr "" #: ../dashboard_launch_instances.rst:262 msgid "The Images category shows the instance snapshot." msgstr "" #: ../dashboard_launch_instances.rst:264 msgid "" "To launch an instance from the snapshot, select the snapshot and click :" "guilabel:`Launch`. Proceed with launching an instance." msgstr "" #: ../dashboard_launch_instances.rst:268 msgid "Manage an instance" msgstr "" #: ../dashboard_launch_instances.rst:277 msgid "Select an instance." msgstr "" #: ../dashboard_launch_instances.rst:279 msgid "In the menu list in the :guilabel:`Actions` column, select the state." msgstr "" #: ../dashboard_launch_instances.rst:281 msgid "" "You can resize or rebuild an instance. You can also choose to view the " "instance console log, edit instance or the security groups. Depending on the " "current state of the instance, you can pause, resume, suspend, soft or hard " "reboot, or terminate it." msgstr "" #: ../dashboard_log_in.rst:3 msgid "Log in to the dashboard" msgstr "" #: ../dashboard_log_in.rst:5 msgid "The dashboard is generally installed on the controller node." msgstr "" #: ../dashboard_log_in.rst:7 msgid "" "Ask the cloud operator for the host name or public IP address from which you " "can access the dashboard, and for your user name and password. If the cloud " "supports multi-domain model, you also need to ask for your domain name." msgstr "" #: ../dashboard_log_in.rst:12 msgid "Open a web browser that has JavaScript and cookies enabled." msgstr "" #: ../dashboard_log_in.rst:16 msgid "" "To use the Virtual Network Computing (VNC) client for the dashboard, your " "browser must support HTML5 Canvas and HTML5 WebSockets. The VNC client is " "based on noVNC. For details, see `noVNC: HTML5 VNC Client `__. For a list of supported " "browsers, see `Browser support `__." msgstr "" #: ../dashboard_log_in.rst:23 msgid "" "In the address bar, enter the host name or IP address for the dashboard, for " "example ``https://ipAddressOrHostName/``." msgstr "" #: ../dashboard_log_in.rst:28 msgid "" "If a certificate warning appears when you try to access the URL for the " "first time, a self-signed certificate is in use, which is not considered " "trustworthy by default. Verify the certificate or add an exception in the " "browser to bypass the warning." msgstr "" #: ../dashboard_log_in.rst:33 msgid "" "On the Log In page, enter your user name and password, and click :guilabel:" "`Sign In`. If the cloud supports multi-domain model, you also need to enter " "your domain name." msgstr "" #: ../dashboard_log_in.rst:37 msgid "" "The top of the window displays your user name. You can also access the :" "guilabel:`Settings` tab (:ref:`dashboard-settings-tab`) or sign out of the " "dashboard." msgstr "" #: ../dashboard_log_in.rst:41 msgid "" "The visible tabs and functions in the dashboard depend on the access " "permissions, or roles, of the user you are logged in as." msgstr "" #: ../dashboard_log_in.rst:44 msgid "" "If you are logged in as an end user, the :guilabel:`Project` tab (:ref:" "`dashboard-project-tab`) and :guilabel:`Identity` tab (:ref:`dashboard-" "identity-tab`) are displayed." msgstr "" #: ../dashboard_log_in.rst:48 msgid "" "If you are logged in as an administrator, the :guilabel:`Project` tab (:ref:" "`dashboard-project-tab`) and :guilabel:`Admin` tab (:ref:`dashboard-admin-" "tab`) and :guilabel:`Identity` tab (:ref:`dashboard-identity-tab`) are " "displayed." msgstr "" #: ../dashboard_log_in.rst:57 msgid "OpenStack dashboard — :guilabel:`Project` tab" msgstr "" #: ../dashboard_log_in.rst:59 msgid "" "Projects are organizational units in the cloud, and are also known as " "tenants or accounts. Each user is a member of one or more projects. Within a " "project, a user creates and manages instances." msgstr "" #: ../dashboard_log_in.rst:63 msgid "" "From the :guilabel:`Project` tab, you can view and manage the resources in a " "selected project, including instances and images. You can select the project " "from the drop down menu at the top left. If the cloud supports multi-domain " "model, you can also select the domain from this menu." msgstr "" #: ../dashboard_log_in.rst:71 msgid "**Figure: Project tab**" msgstr "" #: ../dashboard_log_in.rst:73 msgid "" "From the :guilabel:`Project` tab, you can access the following categories:" msgstr "" #: ../dashboard_log_in.rst:76 msgid ":guilabel:`Compute` tab" msgstr "" #: ../dashboard_log_in.rst:78 msgid ":guilabel:`Overview`: View reports for the project." msgstr "" #: ../dashboard_log_in.rst:80 msgid "" ":guilabel:`Instances`: View, launch, create a snapshot from, stop, pause, or " "reboot instances, or connect to them through VNC." msgstr "" #: ../dashboard_log_in.rst:83 ../dashboard_log_in.rst:169 msgid ":guilabel:`Volumes`: Use the following tabs to complete these tasks:" msgstr "" #: ../dashboard_log_in.rst:85 msgid ":guilabel:`Volumes`: View, create, edit, and delete volumes." msgstr "" #: ../dashboard_log_in.rst:87 msgid "" ":guilabel:`Volume Snapshots`: View, create, edit, and delete volume " "snapshots." msgstr "" #: ../dashboard_log_in.rst:90 msgid "" ":guilabel:`Images`: View images and instance snapshots created by project " "users, plus any images that are publicly available. Create, edit, and delete " "images, and launch instances from images and snapshots." msgstr "" #: ../dashboard_log_in.rst:94 msgid "" ":guilabel:`Access & Security`: Use the following tabs to complete these " "tasks:" msgstr "" #: ../dashboard_log_in.rst:97 msgid "" ":guilabel:`Security Groups`: View, create, edit, and delete security groups " "and security group rules." msgstr "" #: ../dashboard_log_in.rst:100 msgid "" ":guilabel:`Key Pairs`: View, create, edit, import, and delete key pairs." msgstr "" #: ../dashboard_log_in.rst:102 msgid "" ":guilabel:`Floating IPs`: Allocate an IP address to or release it from a " "project." msgstr "" #: ../dashboard_log_in.rst:105 msgid ":guilabel:`API Access`: View API endpoints." msgstr "" #: ../dashboard_log_in.rst:110 msgid ":guilabel:`Network Topology`: View the network topology." msgstr "" #: ../dashboard_log_in.rst:112 msgid ":guilabel:`Networks`: Create and manage public and private networks." msgstr "" #: ../dashboard_log_in.rst:114 msgid ":guilabel:`Routers`: Create and manage routers." msgstr "" #: ../dashboard_log_in.rst:117 msgid ":guilabel:`Orchestration` tab" msgstr "" #: ../dashboard_log_in.rst:119 msgid "" ":guilabel:`Stacks`: Use the REST API to orchestrate multiple composite cloud " "applications." msgstr "" #: ../dashboard_log_in.rst:122 msgid "" ":guilabel:`Resource Types`: Show a list of all the supported resource types " "for HOT templates." msgstr "" #: ../dashboard_log_in.rst:126 msgid ":guilabel:`Object Store` tab" msgstr "" #: ../dashboard_log_in.rst:128 msgid ":guilabel:`Containers`: Create and manage containers and objects." msgstr "" #: ../dashboard_log_in.rst:133 msgid "OpenStack dashboard — :guilabel:`Admin` tab" msgstr "" #: ../dashboard_log_in.rst:135 msgid "" "Administrative users can use the :guilabel:`Admin` tab to view usage and to " "manage instances, volumes, flavors, images, networks and so on." msgstr "" #: ../dashboard_log_in.rst:142 msgid "**Figure: Admin tab**" msgstr "" #: ../dashboard_log_in.rst:144 msgid "" "From the :guilabel:`Admin` tab, you can access the following category to " "complete these tasks:" msgstr "" #: ../dashboard_log_in.rst:148 msgid ":guilabel:`System` tab" msgstr "" #: ../dashboard_log_in.rst:150 msgid ":guilabel:`Overview`: View basic reports." msgstr "" #: ../dashboard_log_in.rst:152 msgid "" ":guilabel:`Resource Usage`: Use the following tabs to view the following " "usages:" msgstr "" #: ../dashboard_log_in.rst:155 msgid ":guilabel:`Usage Report`: View the usage report." msgstr "" #: ../dashboard_log_in.rst:157 msgid ":guilabel:`Stats`: View the statistics of all resources." msgstr "" #: ../dashboard_log_in.rst:159 msgid ":guilabel:`Hypervisors`: View the hypervisor summary." msgstr "" #: ../dashboard_log_in.rst:161 msgid "" ":guilabel:`Host Aggregates`: View, create, and edit host aggregates. View " "the list of availability zones." msgstr "" #: ../dashboard_log_in.rst:164 msgid "" ":guilabel:`Instances`: View, pause, resume, suspend, migrate, soft or hard " "reboot, and delete running instances that belong to users of some, but not " "all, projects. Also, view the log for an instance or access an instance " "through VNC." msgstr "" #: ../dashboard_log_in.rst:171 msgid ":guilabel:`Volumes`: View, create, manage, and delete volumes." msgstr "" #: ../dashboard_log_in.rst:173 msgid "" ":guilabel:`Volume Types`: View, create, manage, and delete volume types." msgstr "" #: ../dashboard_log_in.rst:175 msgid "" ":guilabel:`Volume Snapshots`: View, manage, and delete volume snapshots." msgstr "" #: ../dashboard_log_in.rst:177 msgid "" ":guilabel:`Flavors`: View, create, edit, view extra specifications for, and " "delete flavors. A flavor is size of an instance." msgstr "" #: ../dashboard_log_in.rst:180 msgid "" ":guilabel:`Images`: View, create, edit properties for, and delete custom " "images." msgstr "" #: ../dashboard_log_in.rst:183 msgid "" ":guilabel:`Networks`: View, create, edit properties for, and delete networks." msgstr "" #: ../dashboard_log_in.rst:186 msgid "" ":guilabel:`Routers`: View, create, edit properties for, and delete routers." msgstr "" #: ../dashboard_log_in.rst:188 msgid "" ":guilabel:`Defaults`: View default quota values. Quotas are hard-coded in " "OpenStack Compute and define the maximum allowable size and number of " "resources." msgstr "" #: ../dashboard_log_in.rst:192 msgid "" ":guilabel:`Metadata Definitions`: Import namespace and view the metadata " "information." msgstr "" #: ../dashboard_log_in.rst:195 msgid "" ":guilabel:`System Information`: Use the following tabs to view the service " "information:" msgstr "" #: ../dashboard_log_in.rst:198 msgid ":guilabel:`Services`: View a list of the services." msgstr "" #: ../dashboard_log_in.rst:200 msgid ":guilabel:`Compute Services`: View a list of all Compute services." msgstr "" #: ../dashboard_log_in.rst:202 msgid "" ":guilabel:`Block Storage Services`: View a list of all Block Storage " "services." msgstr "" #: ../dashboard_log_in.rst:205 msgid ":guilabel:`Network Agents`: View the network agents." msgstr "" #: ../dashboard_log_in.rst:207 msgid "" ":guilabel:`Orchestration Services`: View a list of all Orchestration " "services." msgstr "" #: ../dashboard_log_in.rst:213 msgid "OpenStack dashboard — :guilabel:`Identity` tab" msgstr "" #: ../dashboard_log_in.rst:218 msgid "**Figure:Identity tab**" msgstr "" #: ../dashboard_log_in.rst:220 msgid "" ":guilabel:`Projects`: View, create, assign users to, remove users from, and " "delete projects." msgstr "" #: ../dashboard_log_in.rst:223 msgid ":guilabel:`Users`: View, create, enable, disable, and delete users." msgstr "" #: ../dashboard_log_in.rst:228 msgid "OpenStack dashboard — :guilabel:`Settings` tab" msgstr "" #: ../dashboard_log_in.rst:233 msgid "**Figure:Settings tab**" msgstr "" #: ../dashboard_log_in.rst:235 msgid "" "Click the :guilabel:`Settings` button from the user drop down menu at the " "top right of any page, you will see the :guilabel:`Settings` tab." msgstr "" #: ../dashboard_log_in.rst:238 msgid ":guilabel:`User Settings`: View and manage dashboard settings." msgstr "" #: ../dashboard_log_in.rst:240 msgid ":guilabel:`Change Password`: Change the password of the user." msgstr "" #: ../dashboard_manage_containers.rst:3 msgid "Create and manage object containers" msgstr "" #: ../dashboard_manage_containers.rst:5 msgid "" "OpenStack Object Storage (swift) is used for redundant, scalable data " "storage using clusters of standardized servers to store petabytes of " "accessible data. It is a long-term storage system for large amounts of " "static data which can be retrieved and updated." msgstr "" #: ../dashboard_manage_containers.rst:10 msgid "" "OpenStack Object Storage provides a distributed, API-accessible storage " "platform that can be integrated directly into an application or used to " "store any type of file, including VM images, backups, archives, or media " "files. In the OpenStack dashboard, you can only manage containers and " "objects." msgstr "" #: ../dashboard_manage_containers.rst:16 msgid "" "In OpenStack Object Storage, containers provide storage for objects in a " "manner similar to a Windows folder or Linux file directory, though they " "cannot be nested. An object in OpenStack consists of the file to be stored " "in the container and any accompanying metadata." msgstr "" #: ../dashboard_manage_containers.rst:22 msgid "Create a container" msgstr "" #: ../dashboard_manage_containers.rst:28 ../dashboard_manage_containers.rst:50 #: ../dashboard_manage_containers.rst:84 #: ../dashboard_manage_containers.rst:108 #: ../dashboard_manage_containers.rst:138 #: ../dashboard_manage_containers.rst:165 msgid "" "On the :guilabel:`Project` tab, open the :guilabel:`Object Store` tab and " "click :guilabel:`Containers` category." msgstr "" #: ../dashboard_manage_containers.rst:31 msgid "Click :guilabel:`Create Container`." msgstr "" #: ../dashboard_manage_containers.rst:33 msgid "" "In the :guilabel:`Create Container` dialog box, enter a name for the " "container, and then click :guilabel:`Create Container`." msgstr "" #: ../dashboard_manage_containers.rst:36 msgid "You have successfully created a container." msgstr "" #: ../dashboard_manage_containers.rst:40 msgid "" "To delete a container, click the :guilabel:`More` button and select :" "guilabel:`Delete Container`." msgstr "" #: ../dashboard_manage_containers.rst:44 msgid "Upload an object" msgstr "" #: ../dashboard_manage_containers.rst:53 ../dashboard_manage_containers.rst:87 #: ../dashboard_manage_containers.rst:111 #: ../dashboard_manage_containers.rst:141 #: ../dashboard_manage_containers.rst:168 msgid "Select the container in which you want to store your object." msgstr "" #: ../dashboard_manage_containers.rst:55 ../dashboard_manage_containers.rst:66 #: ../dashboard_manage_containers.rst:143 msgid "Click :guilabel:`Upload Object`." msgstr "" #: ../dashboard_manage_containers.rst:57 msgid "" "The :guilabel:`Upload Object To Container: ` dialog box appears. " "```` is the name of the container to which you are uploading the " "object." msgstr "" #: ../dashboard_manage_containers.rst:62 #: ../dashboard_manage_containers.rst:151 msgid "Enter a name for the object." msgstr "" #: ../dashboard_manage_containers.rst:64 ../dashboard_manage_containers.rst:93 msgid "Browse to and select the file that you want to upload." msgstr "" #: ../dashboard_manage_containers.rst:68 msgid "You have successfully uploaded an object to the container." msgstr "" #: ../dashboard_manage_containers.rst:72 msgid "" "To delete an object, click the :guilabel:`More button` and select :guilabel:" "`Delete Object`." msgstr "" #: ../dashboard_manage_containers.rst:76 msgid "Manage an object" msgstr "" #: ../dashboard_manage_containers.rst:78 msgid "**To edit an object**" msgstr "" #: ../dashboard_manage_containers.rst:89 msgid "" "Click the menu button and choose :guilabel:`Edit` from the dropdown list." msgstr "" #: ../dashboard_manage_containers.rst:91 msgid "The :guilabel:`Edit Object` dialog box is displayed." msgstr "" #: ../dashboard_manage_containers.rst:95 #: ../dashboard_manage_containers.rst:153 msgid "Click :guilabel:`Update Object`." msgstr "" #: ../dashboard_manage_containers.rst:99 msgid "" "To delete an object, click the menu button and select :guilabel:`Delete " "Object`." msgstr "" #: ../dashboard_manage_containers.rst:102 msgid "**To copy an object from one container to another**" msgstr "" #: ../dashboard_manage_containers.rst:113 msgid "" "Click the menu button and choose :guilabel:`Copy` from the dropdown list." msgstr "" #: ../dashboard_manage_containers.rst:115 msgid "" "In the :guilabel:`Copy Object` launch dialog box, enter the following values:" msgstr "" #: ../dashboard_manage_containers.rst:118 msgid "" ":guilabel:`Destination Container`: Choose the destination container from the " "list." msgstr "" #: ../dashboard_manage_containers.rst:120 msgid "" ":guilabel:`Path`: Specify a path in which the new copy should be stored " "inside of the selected container." msgstr "" #: ../dashboard_manage_containers.rst:122 msgid "" ":guilabel:`Destination object name`: Enter a name for the object in the new " "container." msgstr "" #: ../dashboard_manage_containers.rst:125 msgid "Click :guilabel:`Copy Object`." msgstr "" #: ../dashboard_manage_containers.rst:127 msgid "**To create a metadata-only object without a file**" msgstr "" #: ../dashboard_manage_containers.rst:129 msgid "" "You can create a new object in container without a file available and can " "upload the file later when it is ready. This temporary object acts a place-" "holder for a new object, and enables the user to share object metadata and " "URL info in advance." msgstr "" #: ../dashboard_manage_containers.rst:145 msgid "" "The :guilabel:`Upload Object To Container`: ```` dialog box is " "displayed." msgstr "" #: ../dashboard_manage_containers.rst:148 msgid "" "```` is the name of the container to which you are uploading the " "object." msgstr "" #: ../dashboard_manage_containers.rst:155 msgid "**To create a pseudo-folder**" msgstr "" #: ../dashboard_manage_containers.rst:157 msgid "" "Pseudo-folders are similar to folders in your desktop operating system. They " "are virtual collections defined by a common prefix on the object's name." msgstr "" #: ../dashboard_manage_containers.rst:170 msgid "Click :guilabel:`Create Pseudo-folder`." msgstr "" #: ../dashboard_manage_containers.rst:172 msgid "" "The :guilabel:`Create Pseudo-Folder in Container` ```` dialog box is " "displayed. ```` is the name of the container to which you are " "uploading the object." msgstr "" #: ../dashboard_manage_containers.rst:176 msgid "Enter a name for the pseudo-folder." msgstr "" #: ../dashboard_manage_containers.rst:178 msgid "" "A slash (/) character is used as the delimiter for pseudo-folders in Object " "Storage." msgstr "" #: ../dashboard_manage_images.rst:3 msgid "Upload and manage images" msgstr "" #: ../dashboard_manage_images.rst:5 msgid "" "A virtual machine image, referred to in this document simply as an image, is " "a single file that contains a virtual disk that has a bootable operating " "system installed on it. Images are used to create virtual machine instances " "within the cloud. For information about creating image files, see the " "`OpenStack Virtual Machine Image Guide `_." msgstr "" #: ../dashboard_manage_images.rst:12 msgid "" "Depending on your role, you may have permission to upload and manage virtual " "machine images. Operators might restrict the upload and management of images " "to cloud administrators or operators only. If you have the appropriate " "privileges, you can use the dashboard to upload and manage images in the " "admin project." msgstr "" #: ../dashboard_manage_images.rst:20 msgid "" "You can also use the :command:`openstack`, :command:`glance` and :command:" "`nova` command-line clients or the Image service and Compute APIs to manage " "images. For more information see :doc:`../common/cli_manage_images`." msgstr "" # #-#-#-#-# dashboard_manage_images.pot (End User Guide 1.0.0) #-#-#-#-# # #-#-#-#-# sdk_manage_images.pot (End User Guide 1.0.0) #-#-#-#-# #: ../dashboard_manage_images.rst:26 ../sdk_manage_images.rst:117 msgid "Upload an image" msgstr "" #: ../dashboard_manage_images.rst:28 msgid "Follow this procedure to upload an image to a project:" msgstr "" #: ../dashboard_manage_images.rst:34 ../dashboard_manage_images.rst:131 msgid "" "On the :guilabel:`Project` tab, open the :guilabel:`Compute` tab and click :" "guilabel:`Images` category." msgstr "" #: ../dashboard_manage_images.rst:37 ../dashboard_manage_images.rst:93 msgid "Click :guilabel:`Create Image`." msgstr "" #: ../dashboard_manage_images.rst:39 msgid "The :guilabel:`Create An Image` dialog box appears." msgstr "" #: ../dashboard_manage_images.rst:43 msgid "**Dashboard — Create Image**" msgstr "" #: ../dashboard_manage_images.rst:45 msgid "Enter the following values:" msgstr "" #: ../dashboard_manage_images.rst:48 msgid ":guilabel:`Name`" msgstr "" #: ../dashboard_manage_images.rst:48 msgid "Enter a name for the image." msgstr "" #: ../dashboard_manage_images.rst:50 msgid ":guilabel:`Description`" msgstr "" #: ../dashboard_manage_images.rst:50 msgid "Enter a brief description of the image." msgstr "" #: ../dashboard_manage_images.rst:53 msgid ":guilabel:`Image Source`" msgstr "" #: ../dashboard_manage_images.rst:53 msgid "" "Choose the image source from the dropdown list. Your choices are :guilabel:" "`Image Location` and :guilabel:`Image File`." msgstr "" #: ../dashboard_manage_images.rst:58 msgid ":guilabel:`Image File` or :guilabel:`Image Location`" msgstr "" #: ../dashboard_manage_images.rst:58 msgid "" "Based on your selection for :guilabel:`Image Source`, you either enter the " "location URL of the image in the :guilabel:`Image Location` field, or browse " "for the image file on your file system and add it." msgstr "" #: ../dashboard_manage_images.rst:67 msgid ":guilabel:`Format`" msgstr "" #: ../dashboard_manage_images.rst:67 msgid "Select the image format (for example, QCOW2) for the image." msgstr "" #: ../dashboard_manage_images.rst:70 msgid ":guilabel:`Architecture`" msgstr "" #: ../dashboard_manage_images.rst:70 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:75 msgid ":guilabel:`Minimum Disk (GB)`" msgstr "" #: ../dashboard_manage_images.rst:75 ../dashboard_manage_images.rst:77 msgid "Leave this field empty." msgstr "" #: ../dashboard_manage_images.rst:77 msgid ":guilabel:`Minimum RAM (MB)`" msgstr "" #: ../dashboard_manage_images.rst:79 msgid ":guilabel:`Copy Data`" msgstr "" #: ../dashboard_manage_images.rst:79 msgid "Specify this option to copy image data to the Image service." msgstr "" #: ../dashboard_manage_images.rst:82 msgid ":guilabel:`Public`" msgstr "" #: ../dashboard_manage_images.rst:82 msgid "" "Select this check box to make the image public to all users with access to " "the current project." msgstr "" #: ../dashboard_manage_images.rst:87 msgid ":guilabel:`Protected`" msgstr "" #: ../dashboard_manage_images.rst:87 msgid "" "Select this check box to ensure that only users with permissions can delete " "the image." msgstr "" #: ../dashboard_manage_images.rst:95 msgid "" "The image is queued to be uploaded. It might take some time before the " "status changes from Queued to Active." msgstr "" #: ../dashboard_manage_images.rst:99 msgid "Update an image" msgstr "" #: ../dashboard_manage_images.rst:101 msgid "Follow this procedure to update an existing image." msgstr "" #: ../dashboard_manage_images.rst:107 msgid "Select the image that you want to edit." msgstr "" #: ../dashboard_manage_images.rst:109 msgid "" "In the :guilabel:`Actions` column, click the menu button and then select :" "guilabel:`Edit Image` from the list." msgstr "" #: ../dashboard_manage_images.rst:112 msgid "" "In the :guilabel:`Update Image` dialog box, you can perform various actions. " "For example:" msgstr "" #: ../dashboard_manage_images.rst:115 msgid "Change the name of the image." msgstr "" #: ../dashboard_manage_images.rst:116 msgid "Select the :guilabel:`Public` check box to make the image public." msgstr "" #: ../dashboard_manage_images.rst:117 msgid "Clear the :guilabel:`Public` check box to make the image private." msgstr "" #: ../dashboard_manage_images.rst:119 msgid "Click :guilabel:`Update Image`." msgstr "" #: ../dashboard_manage_images.rst:124 msgid "" "Deletion of images is permanent and **cannot** be reversed. Only users with " "the appropriate permissions can delete images." msgstr "" #: ../dashboard_manage_images.rst:134 msgid "Select the images that you want to delete." msgstr "" #: ../dashboard_manage_images.rst:136 msgid "Click :guilabel:`Delete Images`." msgstr "" #: ../dashboard_manage_images.rst:138 msgid "" "In the :guilabel:`Confirm Delete Images` dialog box, click :guilabel:`Delete " "Images` to confirm the deletion." msgstr "" #: ../dashboard_manage_lbaasv2.rst:3 msgid "View and manage load balancers v2" msgstr "" #: ../dashboard_manage_lbaasv2.rst:5 msgid "" "Load-Balancer-as-a-Service (LBaaS) enables networking to distribute incoming " "requests evenly among designated instances. This distribution ensures that " "the workload is shared predictably among instances and enables more " "effective use of system resources. Use one of these load-balancing methods " "to distribute incoming requests:" msgstr "" #: ../dashboard_manage_lbaasv2.rst:11 msgid "Round robin: Rotates requests evenly between multiple instances." msgstr "" #: ../dashboard_manage_lbaasv2.rst:12 msgid "" "Source IP: Requests from a unique source IP address are consistently " "directed to the same instance." msgstr "" #: ../dashboard_manage_lbaasv2.rst:14 msgid "" "Least connections: Allocates requests to the instance with the least number " "of active connections." msgstr "" #: ../dashboard_manage_lbaasv2.rst:17 msgid "" "As an end user, you can create and manage load balancers and related objects " "for users in various projects. You can also delete load balancers and " "related objects." msgstr "" #: ../dashboard_manage_lbaasv2.rst:21 msgid "LBaaS v2 has several new concepts to understand:" msgstr "" #: ../dashboard_manage_lbaasv2.rst:24 msgid "" "The load balancer occupies a neutron network port and has an IP address " "assigned from a subnet." msgstr "" #: ../dashboard_manage_lbaasv2.rst:25 msgid "Load balancer" msgstr "" #: ../dashboard_manage_lbaasv2.rst:28 msgid "" "Each port that listens for traffic on a particular load balancer is " "configured separately and tied to the load balancer. Multiple listeners can " "be associated with the same load balancer." msgstr "" #: ../dashboard_manage_lbaasv2.rst:30 msgid "Listener" msgstr "" #: ../dashboard_manage_lbaasv2.rst:33 msgid "" "A pool is a group of hosts that sits behind the load balancer and serves " "traffic through the load balancer." msgstr "" #: ../dashboard_manage_lbaasv2.rst:34 msgid "Pool" msgstr "" #: ../dashboard_manage_lbaasv2.rst:37 msgid "" "Members are the actual IP addresses that receive traffic from the load " "balancer. Members are associated with pools." msgstr "" #: ../dashboard_manage_lbaasv2.rst:38 msgid "Member" msgstr "" #: ../dashboard_manage_lbaasv2.rst:41 msgid "" "Members may go offline from time to time and health monitors diverts traffic " "away from members that are not responding properly. Health monitors are " "associated with pools." msgstr "" #: ../dashboard_manage_lbaasv2.rst:43 msgid "Health monitor" msgstr "" #: ../dashboard_manage_lbaasv2.rst:46 msgid "View existing load balancers" msgstr "" #: ../dashboard_manage_lbaasv2.rst:48 ../dashboard_manage_lbaasv2.rst:59 msgid "Log in to the OpenStack dashboard." msgstr "" #: ../dashboard_manage_lbaasv2.rst:49 ../dashboard_manage_lbaasv2.rst:60 msgid "" "On the :guilabel:`Project` tab, open the :guilabel:`Network` tab, and click " "the :guilabel:`Load Balancers` category." msgstr "" #: ../dashboard_manage_lbaasv2.rst:53 msgid "" "This view shows the list of existing load balancers. To view details of any " "of the load balancers, click on the specific load balancer." msgstr "" #: ../dashboard_manage_lbaasv2.rst:57 msgid "Create a load balancer" msgstr "" #: ../dashboard_manage_lbaasv2.rst:63 msgid "Click the :guilabel:`Create Load Balancer` button." msgstr "" #: ../dashboard_manage_lbaasv2.rst:65 msgid "" "Use the concepts described in the overview section to fill in the necessary " "information about the load balancer you want to create." msgstr "" #: ../dashboard_manage_lbaasv2.rst:68 msgid "" "Keep in mind, the health checks routinely run against each instance within a " "target load balancer and the result of the health check is used to determine " "if the instance receives new connections." msgstr "" #: ../dashboard_manage_lbaasv2.rst:73 msgid "A message indicates whether the action succeeded." msgstr "" #: ../dashboard_manage_lbaasv2.rst:76 msgid "Delete a load balancer" msgstr "" #: ../dashboard_manage_lbaasv2.rst:78 msgid "" "Select the load balancer you want to delete and click the :guilabel:`Delete " "Load Balancer` button." msgstr "" #: ../dashboard_manage_lbaasv2.rst:81 msgid "" "To be deleted successfully, a load balancer must not have any listeners or " "pools associated with it. The delete action is also available in the :" "guilabel:`Actions` column for the individual load balancers." msgstr "" #: ../dashboard_manage_shares.rst:3 msgid "Create and manage shares" msgstr "" #: ../dashboard_manage_shares.rst:5 msgid "" "Shares are file storage that you provide access to instances. You can allow " "access to a share to a running instance or deny access to a share and allow " "access to it to another instance at any time. You can also delete a share. " "You can create snapshot from a share if the driver supports it. Only " "administrative users can create share types." msgstr "" #: ../dashboard_manage_shares.rst:14 ../dashboard_manage_shares.rst:42 #: ../dashboard_manage_shares.rst:53 ../dashboard_manage_shares.rst:73 #: ../dashboard_manage_shares.rst:87 ../dashboard_manage_shares.rst:102 #: ../dashboard_manage_shares.rst:118 msgid "" "Log in to the dashboard, choose a project, and click :guilabel:`Shares`." msgstr "" #: ../dashboard_manage_shares.rst:16 ../dashboard_manage_shares.rst:35 msgid "Click :guilabel:`Create Share`." msgstr "" # #-#-#-#-# dashboard_manage_shares.pot (End User Guide 1.0.0) #-#-#-#-# # #-#-#-#-# dashboard_manage_volumes.pot (End User Guide 1.0.0) #-#-#-#-# #: ../dashboard_manage_shares.rst:18 ../dashboard_manage_shares.rst:137 #: ../dashboard_manage_shares.rst:189 ../dashboard_manage_volumes.rst:23 msgid "In the dialog box that opens, enter or select the following values." msgstr "" #: ../dashboard_manage_shares.rst:20 msgid ":guilabel:`Share Name`: Specify a name for the share." msgstr "" #: ../dashboard_manage_shares.rst:22 msgid "" ":guilabel:`Description`: Optionally, provide a brief description for the " "share." msgstr "" #: ../dashboard_manage_shares.rst:25 msgid ":guilabel:`Share Type`: Choose a share type." msgstr "" #: ../dashboard_manage_shares.rst:27 msgid ":guilabel:`Size (GB)`: The size of the share in gibibytes (GiB)." msgstr "" #: ../dashboard_manage_shares.rst:29 msgid ":guilabel:`Share Protocol`: Select NFS, CIFS, GlusterFS, or HDFS." msgstr "" #: ../dashboard_manage_shares.rst:31 msgid ":guilabel:`Share Network`: Choose a share network." msgstr "" #: ../dashboard_manage_shares.rst:33 msgid ":guilabel:`Metadata`: Enter metadata for the share creation if needed." msgstr "" #: ../dashboard_manage_shares.rst:37 msgid "The dashboard shows the share on the :guilabel:`Shares` tab." msgstr "" #: ../dashboard_manage_shares.rst:40 msgid "Delete a share" msgstr "" #: ../dashboard_manage_shares.rst:44 msgid "Select the check boxes for the shares that you want to delete." msgstr "" #: ../dashboard_manage_shares.rst:46 msgid "Click :guilabel:`Delete Shares` and confirm your choice." msgstr "" # #-#-#-#-# dashboard_manage_shares.pot (End User Guide 1.0.0) #-#-#-#-# # #-#-#-#-# dashboard_manage_volumes.pot (End User Guide 1.0.0) #-#-#-#-# #: ../dashboard_manage_shares.rst:48 ../dashboard_manage_shares.rst:68 #: ../dashboard_manage_shares.rst:82 ../dashboard_manage_shares.rst:97 #: ../dashboard_manage_shares.rst:113 ../dashboard_manage_shares.rst:127 #: ../dashboard_manage_shares.rst:162 ../dashboard_manage_shares.rst:179 #: ../dashboard_manage_shares.rst:225 ../dashboard_manage_shares.rst:242 #: ../dashboard_manage_volumes.rst:108 ../dashboard_manage_volumes.rst:173 msgid "A message indicates whether the action was successful." msgstr "" #: ../dashboard_manage_shares.rst:51 msgid "Allow access" msgstr "" #: ../dashboard_manage_shares.rst:55 msgid "" "Go to the share that you want to allow access and choose :guilabel:`Manage " "Rules` from Actions." msgstr "" #: ../dashboard_manage_shares.rst:58 msgid "Click :guilabel:`Add rule`." msgstr "" #: ../dashboard_manage_shares.rst:60 msgid ":guilabel:`Access Type`: Choose ip, user, or cert." msgstr "" #: ../dashboard_manage_shares.rst:62 msgid ":guilabel:`Access Level`: Choose read-write or read-only." msgstr "" #: ../dashboard_manage_shares.rst:64 msgid ":guilabel:`Access To`: Fill in Access To field." msgstr "" #: ../dashboard_manage_shares.rst:66 msgid "Click :guilabel:`Add Rule`." msgstr "" #: ../dashboard_manage_shares.rst:75 msgid "" "Go to the share that you want to deny access and choose :guilabel:`Manage " "Rules` from Actions." msgstr "" #: ../dashboard_manage_shares.rst:78 msgid "Choose the rule you want to delete." msgstr "" #: ../dashboard_manage_shares.rst:80 msgid "Click :guilabel:`Delete rule` and confirm your choice." msgstr "" #: ../dashboard_manage_shares.rst:85 msgid "Edit share metadata" msgstr "" #: ../dashboard_manage_shares.rst:89 msgid "" "Go to the share that you want to edit and choose :guilabel:`Edit Share " "Metadata` from Actions." msgstr "" #: ../dashboard_manage_shares.rst:92 msgid "" ":guilabel:`Metadata`: To add share metadata, use key=value. To unset " "metadata, use key." msgstr "" #: ../dashboard_manage_shares.rst:95 msgid "Click :guilabel:`Edit Share Metadata`." msgstr "" #: ../dashboard_manage_shares.rst:100 msgid "Edit share" msgstr "" #: ../dashboard_manage_shares.rst:104 msgid "" "Go to the share that you want to edit and choose :guilabel:`Edit Share` from " "Actions." msgstr "" #: ../dashboard_manage_shares.rst:107 msgid ":guilabel:`Share Name`: Enter a new share name." msgstr "" #: ../dashboard_manage_shares.rst:109 ../dashboard_manage_shares.rst:175 #: ../dashboard_manage_shares.rst:238 msgid ":guilabel:`Description`: Enter a new description." msgstr "" #: ../dashboard_manage_shares.rst:111 msgid "Click :guilabel:`Edit Share`." msgstr "" #: ../dashboard_manage_shares.rst:120 msgid "" "Go to the share that you want to edit and choose :guilabel:`Extend Share` " "from Actions." msgstr "" #: ../dashboard_manage_shares.rst:123 msgid ":guilabel:`New Size (GB)`: Enter new size." msgstr "" #: ../dashboard_manage_shares.rst:125 msgid "Click :guilabel:`Extend Share`." msgstr "" #: ../dashboard_manage_shares.rst:130 msgid "Create share network" msgstr "" #: ../dashboard_manage_shares.rst:132 ../dashboard_manage_shares.rst:155 #: ../dashboard_manage_shares.rst:167 msgid "" "Log in to the dashboard, choose a project, click :guilabel:`Shares`, and " "click :guilabel:`Share Networks`." msgstr "" #: ../dashboard_manage_shares.rst:135 ../dashboard_manage_shares.rst:148 msgid "Click :guilabel:`Create Share Network`." msgstr "" #: ../dashboard_manage_shares.rst:139 msgid ":guilabel:`Name`: Specify a name for the share network." msgstr "" #: ../dashboard_manage_shares.rst:141 msgid "" ":guilabel:`Description`: Optionally, provide a brief description for the " "share network." msgstr "" #: ../dashboard_manage_shares.rst:144 msgid ":guilabel:`Neutron Net`: Choose a neutron network." msgstr "" #: ../dashboard_manage_shares.rst:146 msgid ":guilabel:`Neutron Subnet`: Choose a neutron subnet." msgstr "" #: ../dashboard_manage_shares.rst:150 msgid "" "The dashboard shows the share network on the :guilabel:`Share Networks` tab." msgstr "" #: ../dashboard_manage_shares.rst:153 msgid "Delete a share network" msgstr "" #: ../dashboard_manage_shares.rst:158 msgid "Select the check boxes for the share networks that you want to delete." msgstr "" #: ../dashboard_manage_shares.rst:160 msgid "Click :guilabel:`Delete Share Networks` and confirm your choice." msgstr "" #: ../dashboard_manage_shares.rst:165 msgid "Edit share network" msgstr "" #: ../dashboard_manage_shares.rst:170 msgid "" "Go to the share network that you want to edit and choose :guilabel:`Edit " "Share Network` from Actions." msgstr "" #: ../dashboard_manage_shares.rst:173 msgid ":guilabel:`Name`: Enter a new share network name." msgstr "" #: ../dashboard_manage_shares.rst:177 msgid "Click :guilabel:`Edit Share Network`." msgstr "" #: ../dashboard_manage_shares.rst:182 msgid "Create security service" msgstr "" #: ../dashboard_manage_shares.rst:184 ../dashboard_manage_shares.rst:218 #: ../dashboard_manage_shares.rst:230 msgid "" "Log in to the dashboard, choose a project, click :guilabel:`Shares`, and " "click :guilabel:`Security Services`." msgstr "" #: ../dashboard_manage_shares.rst:187 ../dashboard_manage_shares.rst:210 msgid "Click :guilabel:`Create Security Service`." msgstr "" #: ../dashboard_manage_shares.rst:191 msgid ":guilabel:`Name`: Specify a name for the security service." msgstr "" #: ../dashboard_manage_shares.rst:193 msgid ":guilabel:`DNS IP`: Enter the DNS IP address." msgstr "" #: ../dashboard_manage_shares.rst:195 msgid ":guilabel:`Server`: Enter the server name." msgstr "" #: ../dashboard_manage_shares.rst:197 msgid ":guilabel:`Domain`: Enter the domain name." msgstr "" #: ../dashboard_manage_shares.rst:199 msgid ":guilabel:`User`: Enter the user name." msgstr "" #: ../dashboard_manage_shares.rst:201 msgid ":guilabel:`Password`: Enter the password." msgstr "" #: ../dashboard_manage_shares.rst:203 msgid ":guilabel:`Confirm Password`: Enter the password again to confirm." msgstr "" #: ../dashboard_manage_shares.rst:205 msgid "" ":guilabel:`Type`: Choose the type from Active Directory, LDAP, or Kerberos." msgstr "" #: ../dashboard_manage_shares.rst:207 msgid "" ":guilabel:`Description`: Optionally, provide a brief description for the " "security service." msgstr "" #: ../dashboard_manage_shares.rst:212 msgid "" "The dashboard shows the security service on the :guilabel:`Security " "Services` tab." msgstr "" #: ../dashboard_manage_shares.rst:216 msgid "Delete a security service" msgstr "" #: ../dashboard_manage_shares.rst:221 msgid "" "Select the check boxes for the security services that you want to delete." msgstr "" #: ../dashboard_manage_shares.rst:223 msgid "Click :guilabel:`Delete Security Services` and confirm your choice." msgstr "" #: ../dashboard_manage_shares.rst:228 msgid "Edit security service" msgstr "" #: ../dashboard_manage_shares.rst:233 msgid "" "Go to the security service that you want to edit and choose :guilabel:`Edit " "Security Service` from Actions." msgstr "" #: ../dashboard_manage_shares.rst:236 msgid ":guilabel:`Name`: Enter a new security service name." msgstr "" #: ../dashboard_manage_shares.rst:240 msgid "Click :guilabel:`Edit Security Service`." msgstr "" #: ../dashboard_manage_volumes.rst:3 msgid "Create and manage volumes" msgstr "" #: ../dashboard_manage_volumes.rst:5 msgid "" "Volumes are block storage devices that you attach to instances to enable " "persistent storage. You can attach a volume to a running instance or detach " "a volume and attach it to another instance at any time. You can also create " "a snapshot from or delete a volume. Only administrative users can create " "volume types." msgstr "" #: ../dashboard_manage_volumes.rst:12 msgid "Create a volume" msgstr "" #: ../dashboard_manage_volumes.rst:18 ../dashboard_manage_volumes.rst:68 #: ../dashboard_manage_volumes.rst:117 ../dashboard_manage_volumes.rst:138 #: ../dashboard_manage_volumes.rst:166 msgid "" "On the :guilabel:`Project` tab, open the :guilabel:`Compute` tab and click :" "guilabel:`Volumes` category." msgstr "" #: ../dashboard_manage_volumes.rst:21 ../dashboard_manage_volumes.rst:52 msgid "Click :guilabel:`Create Volume`." msgstr "" #: ../dashboard_manage_volumes.rst:25 msgid ":guilabel:`Volume Name`: Specify a name for the volume." msgstr "" #: ../dashboard_manage_volumes.rst:27 msgid "" ":guilabel:`Description`: Optionally, provide a brief description for the " "volume." msgstr "" #: ../dashboard_manage_volumes.rst:30 msgid ":guilabel:`Volume Source`: Select one of the following options:" msgstr "" #: ../dashboard_manage_volumes.rst:32 msgid "" "No source, empty volume: Creates an empty volume. An empty volume does not " "contain a file system or a partition table." msgstr "" #: ../dashboard_manage_volumes.rst:35 msgid "" "Image: If you choose this option, a new field for :guilabel:`Use image as a " "source` displays. You can select the image from the list." msgstr "" #: ../dashboard_manage_volumes.rst:38 msgid "" "Volume: If you choose this option, a new field for :guilabel:`Use volume as " "a source` displays. You can select the volume from the list. Options to use " "a snapshot or a volume as the source for a volume are displayed only if " "there are existing snapshots or volumes." msgstr "" #: ../dashboard_manage_volumes.rst:43 msgid ":guilabel:`Type`: Leave this field blank." msgstr "" #: ../dashboard_manage_volumes.rst:45 msgid ":guilabel:`Size (GB)`: The size of the volume in gibibytes (GiB)." msgstr "" #: ../dashboard_manage_volumes.rst:47 msgid "" ":guilabel:`Availability Zone`: Select the Availability Zone from the list. " "By default, this value is set to the availability zone given by the cloud " "provider (for example, ``us-west`` or ``apac-south``). For some cases, it " "could be ``nova``." msgstr "" #: ../dashboard_manage_volumes.rst:54 msgid "The dashboard shows the volume on the :guilabel:`Volumes` tab." msgstr "" #: ../dashboard_manage_volumes.rst:59 msgid "Attach a volume to an instance" msgstr "" #: ../dashboard_manage_volumes.rst:61 msgid "" "After you create one or more volumes, you can attach them to instances. You " "can attach a volume to one instance at a time." msgstr "" #: ../dashboard_manage_volumes.rst:71 msgid "" "Select the volume to add to an instance and click :guilabel:`Manage " "Attachments`." msgstr "" #: ../dashboard_manage_volumes.rst:74 msgid "" "In the :guilabel:`Manage Volume Attachments` dialog box, select an instance." msgstr "" #: ../dashboard_manage_volumes.rst:76 msgid "" "Enter the name of the device from which the volume is accessible by the " "instance." msgstr "" #: ../dashboard_manage_volumes.rst:81 msgid "" "The actual device name might differ from the volume name because of " "hypervisor settings." msgstr "" #: ../dashboard_manage_volumes.rst:84 msgid "Click :guilabel:`Attach Volume`." msgstr "" #: ../dashboard_manage_volumes.rst:86 msgid "" "The dashboard shows the instance to which the volume is now attached and the " "device name." msgstr "" #: ../dashboard_manage_volumes.rst:89 msgid "" "You can view the status of a volume in the Volumes tab of the dashboard. The " "volume is either Available or In-Use." msgstr "" #: ../dashboard_manage_volumes.rst:92 msgid "Now you can log in to the instance and mount, format, and use the disk." msgstr "" #: ../dashboard_manage_volumes.rst:95 msgid "Detach a volume from an instance" msgstr "" #: ../dashboard_manage_volumes.rst:101 msgid "" "On the :guilabel:`Project` tab, open the :guilabel:`Compute` tab and click " "the :guilabel:`Volumes` category." msgstr "" #: ../dashboard_manage_volumes.rst:104 msgid "Select the volume and click :guilabel:`Manage Attachments`." msgstr "" #: ../dashboard_manage_volumes.rst:106 msgid "Click :guilabel:`Detach Volume` and confirm your changes." msgstr "" #: ../dashboard_manage_volumes.rst:111 msgid "Create a snapshot from a volume" msgstr "" #: ../dashboard_manage_volumes.rst:120 msgid "Select a volume from which to create a snapshot." msgstr "" #: ../dashboard_manage_volumes.rst:124 msgid "" "In the dialog box that opens, enter a snapshot name and a brief description." msgstr "" #: ../dashboard_manage_volumes.rst:127 msgid "Confirm your changes." msgstr "" #: ../dashboard_manage_volumes.rst:129 msgid "The dashboard shows the new volume snapshot in Volume Snapshots tab." msgstr "" #: ../dashboard_manage_volumes.rst:132 msgid "Edit a volume" msgstr "" #: ../dashboard_manage_volumes.rst:141 msgid "Select the volume that you want to edit." msgstr "" #: ../dashboard_manage_volumes.rst:143 msgid "In the :guilabel:`Actions` column, click :guilabel:`Edit Volume`." msgstr "" #: ../dashboard_manage_volumes.rst:145 msgid "" "In the :guilabel:`Edit Volume` dialog box, update the name and description " "of the volume." msgstr "" #: ../dashboard_manage_volumes.rst:148 msgid "Click :guilabel:`Edit Volume`." msgstr "" #: ../dashboard_manage_volumes.rst:152 msgid "" "You can extend a volume by using the :guilabel:`Extend Volume` option " "available in the :guilabel:`More` dropdown list and entering the new value " "for volume size." msgstr "" #: ../dashboard_manage_volumes.rst:157 msgid "Delete a volume" msgstr "" #: ../dashboard_manage_volumes.rst:159 msgid "" "When you delete an instance, the data in its attached volumes is not deleted." msgstr "" #: ../dashboard_manage_volumes.rst:169 msgid "Select the check boxes for the volumes that you want to delete." msgstr "" #: ../dashboard_manage_volumes.rst:171 msgid "Click :guilabel:`Delete Volumes` and confirm your choice." msgstr "" #: ../dashboard_stacks.rst:3 msgid "Launch and manage stacks" msgstr "" #: ../dashboard_stacks.rst:5 msgid "" "OpenStack Orchestration is a service that you can use to orchestrate " "multiple composite cloud applications. This service supports the use of both " "the Amazon Web Services (AWS) CloudFormation template format through both a " "Query API that is compatible with CloudFormation and the native OpenStack :" "term:`Heat Orchestration Template (HOT)` format through a REST API." msgstr "" #: ../dashboard_stacks.rst:12 msgid "" "These flexible template languages enable application developers to describe " "and automate the deployment of infrastructure, services, and applications. " "The templates enable creation of most OpenStack resource types, such as " "instances, floating IP addresses, volumes, security groups, and users. Once " "created, the resources are referred to as stacks." msgstr "" #: ../dashboard_stacks.rst:20 msgid "" "The template languages are described in the `Template Guide `_ in the `Heat " "developer documentation `_." msgstr "" #: ../dashboard_stacks.rst:26 msgid "Launch a stack" msgstr "" #: ../dashboard_stacks.rst:30 ../dashboard_stacks.rst:124 #: ../dashboard_stacks.rst:143 msgid "" "On the :guilabel:`Project` tab, open the :guilabel:`Orchestration` tab and " "click :guilabel:`Stacks` category." msgstr "" #: ../dashboard_stacks.rst:32 msgid "Click :guilabel:`Launch Stack`." msgstr "" #: ../dashboard_stacks.rst:33 msgid "" "In the :guilabel:`Select Template` dialog box, specify the following values:" msgstr "" #: ../dashboard_stacks.rst:37 msgid ":guilabel:`Template Source`" msgstr "" #: ../dashboard_stacks.rst:37 msgid "Choose the source of the template from the list." msgstr "" #: ../dashboard_stacks.rst:40 msgid ":guilabel:`Template URL/File/Data`" msgstr "" #: ../dashboard_stacks.rst:40 msgid "" "Depending on the source that you select, enter the URL, browse to the file " "location, or directly include the template." msgstr "" #: ../dashboard_stacks.rst:46 msgid ":guilabel:`Environment Source`" msgstr "" #: ../dashboard_stacks.rst:46 msgid "" "Choose the source of the environment from the list. The environment files " "contain additional settings for the stack." msgstr "" #: ../dashboard_stacks.rst:52 msgid ":guilabel:`Environment File/Data`" msgstr "" #: ../dashboard_stacks.rst:52 msgid "" "Depending on the source that you select, browse to the file location, " "directly include the environment" msgstr "" #: ../dashboard_stacks.rst:58 ../dashboard_stacks.rst:130 msgid "Click :guilabel:`Next`." msgstr "" #: ../dashboard_stacks.rst:59 msgid "" "In the :guilabel:`Launch Stack` dialog box, specify the following values:" msgstr "" #: ../dashboard_stacks.rst:63 msgid ":guilabel:`Stack Name`" msgstr "" #: ../dashboard_stacks.rst:63 msgid "Enter a name to identify the stack." msgstr "" #: ../dashboard_stacks.rst:66 msgid ":guilabel:`Creation Timeout` :guilabel:`(minutes)`" msgstr "" #: ../dashboard_stacks.rst:66 msgid "" "Specify the number of minutes that can elapse before the launch of the stack " "times out." msgstr "" #: ../dashboard_stacks.rst:70 msgid ":guilabel:`Rollback On Failure`" msgstr "" #: ../dashboard_stacks.rst:70 msgid "" "Select this check box if you want the service to roll back changes if the " "stack fails to launch." msgstr "" #: ../dashboard_stacks.rst:75 msgid ":guilabel:`Password for user` :guilabel:`\"demo\"`" msgstr "" #: ../dashboard_stacks.rst:75 msgid "" "Specify the password that the default user uses when the stack is created." msgstr "" #: ../dashboard_stacks.rst:79 msgid ":guilabel:`DBUsername`" msgstr "" #: ../dashboard_stacks.rst:79 msgid "Specify the name of the database user." msgstr "" #: ../dashboard_stacks.rst:82 msgid ":guilabel:`LinuxDistribution`" msgstr "" #: ../dashboard_stacks.rst:82 msgid "Specify the Linux distribution that is used in the stack." msgstr "" #: ../dashboard_stacks.rst:85 msgid ":guilabel:`DBRootPassword`" msgstr "" #: ../dashboard_stacks.rst:85 msgid "Specify the root password for the database." msgstr "" #: ../dashboard_stacks.rst:88 msgid ":guilabel:`KeyName`" msgstr "" #: ../dashboard_stacks.rst:88 msgid "Specify the name of the key pair to use to log in to the stack." msgstr "" #: ../dashboard_stacks.rst:91 msgid ":guilabel:`DBName`" msgstr "" #: ../dashboard_stacks.rst:91 msgid "Specify the name of the database." msgstr "" #: ../dashboard_stacks.rst:94 msgid ":guilabel:`DBPassword`" msgstr "" #: ../dashboard_stacks.rst:94 msgid "Specify the password of the database." msgstr "" #: ../dashboard_stacks.rst:97 msgid ":guilabel:`InstanceType`" msgstr "" #: ../dashboard_stacks.rst:97 msgid "Specify the flavor for the instance." msgstr "" #: ../dashboard_stacks.rst:101 msgid "" "Click :guilabel:`Launch` to create a stack. The :guilabel:`Stacks` tab shows " "the stack." msgstr "" #: ../dashboard_stacks.rst:104 msgid "" "After the stack is created, click on the stack name to see the following " "details:" msgstr "" #: ../dashboard_stacks.rst:108 msgid "The topology of the stack." msgstr "" #: ../dashboard_stacks.rst:108 msgid "Topology" msgstr "" #: ../dashboard_stacks.rst:111 msgid "Overview" msgstr "" #: ../dashboard_stacks.rst:111 msgid "The parameters and details of the stack." msgstr "" #: ../dashboard_stacks.rst:114 msgid "Resources" msgstr "" #: ../dashboard_stacks.rst:114 msgid "The resources used by the stack." msgstr "" #: ../dashboard_stacks.rst:117 msgid "Events" msgstr "" #: ../dashboard_stacks.rst:117 msgid "The events related to the stack." msgstr "" #: ../dashboard_stacks.rst:120 msgid "Manage a stack" msgstr "" #: ../dashboard_stacks.rst:126 msgid "Select the stack that you want to update." msgstr "" #: ../dashboard_stacks.rst:127 msgid "Click :guilabel:`Change Stack Template`." msgstr "" #: ../dashboard_stacks.rst:128 msgid "" "In the :guilabel:`Select Template` dialog box, select the new template " "source or environment source." msgstr "" #: ../dashboard_stacks.rst:132 msgid "The :guilabel:`Update Stack Parameters` window appears." msgstr "" #: ../dashboard_stacks.rst:133 msgid "Enter new values for any parameters that you want to update." msgstr "" #: ../dashboard_stacks.rst:134 msgid "Click :guilabel:`Update`." msgstr "" #: ../dashboard_stacks.rst:137 msgid "Delete a stack" msgstr "" #: ../dashboard_stacks.rst:139 msgid "When you delete a stack, you cannot undo this action." msgstr "" #: ../dashboard_stacks.rst:145 msgid "Select the stack that you want to delete." msgstr "" #: ../dashboard_stacks.rst:146 msgid "Click :guilabel:`Delete Stack`." msgstr "" #: ../dashboard_stacks.rst:147 msgid "" "In the confirmation dialog box, click :guilabel:`Delete Stack` to confirm " "the deletion." msgstr "" #: ../hot.rst:3 msgid "HOT Guide" msgstr "" #: ../hot.rst:5 msgid "" "The HOT Guide is now maintained as part of the Heat repository and is " "available on the OpenStack developer documentation website: `Heat Template " "Guide `__" msgstr "" #: ../index.rst:3 msgid "OpenStack End User Guide" msgstr "" #: ../index.rst:6 msgid "Abstract" msgstr "" #: ../index.rst:8 msgid "" "OpenStack is an open-source cloud computing platform for public and private " "clouds. A series of interrelated projects deliver a cloud infrastructure " "solution. This guide shows OpenStack end users how to create and manage " "resources in an OpenStack cloud with the OpenStack dashboard and OpenStack " "client commands." msgstr "" #: ../index.rst:14 msgid "" "This guide documents OpenStack Mitaka, OpenStack Liberty, and OpenStack Kilo " "releases." msgstr "" #: ../index.rst:18 msgid "Contents" msgstr "" #: ../index.rst:36 msgid "Search in this guide" msgstr "" #: ../index.rst:38 msgid ":ref:`search`" msgstr "" #: ../intro-user.rst:3 msgid "How can I use an OpenStack cloud?" msgstr "" #: ../intro-user.rst:5 msgid "" "As an OpenStack cloud end user, you can provision your own resources within " "the limits set by cloud administrators." msgstr "" #: ../intro-user.rst:8 msgid "" "The examples in this guide show you how to perform tasks by using the " "following methods:" msgstr "" #: ../intro-user.rst:11 msgid "" "OpenStack dashboard: Use this web-based graphical interface, code named " "`horizon `__, to view, " "create, and manage resources." msgstr "" #: ../intro-user.rst: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 in a cloud and automate tasks by using scripts." msgstr "" #: ../intro-user.rst:20 msgid "You can modify these examples for your specific use cases." msgstr "" #: ../intro-user.rst:22 msgid "" "In addition to these ways of interacting with a cloud, you can access the " "OpenStack APIs directly or indirectly through `cURL `__ " "commands or open SDKs. You can automate access or build tools to manage " "resources and services by using the native OpenStack APIs or the EC2 " "compatibility API." msgstr "" #: ../intro-user.rst: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-user.rst:33 msgid "Who should read this book?" msgstr "" #: ../intro-user.rst:35 msgid "" "This book is written for anyone who uses virtual machines and cloud " "resources to develop software or perform research. You should have years of " "experience with Linux-based tool sets and be comfortable using both GUI and " "CLI based tools. While this book includes some information about using " "Python to create and manage cloud resources, Python knowledge is not a pre-" "requisite for reading this book." msgstr "" #: ../manage_db_config.rst:3 msgid "Manage database configuration" msgstr "" #: ../manage_db_config.rst:5 msgid "" "You can manage database configuration tasks by using configuration groups. " "Configuration groups let you set configuration options, in bulk, on one or " "more databases." msgstr "" #: ../manage_db_config.rst:9 msgid "" "This example assumes you have created a MySQL database and shows you how to " "use a configuration group to configure it. Although this example sets just " "one option on one database, you can use these same procedures to set " "multiple options on multiple database instances throughout your environment. " "This can provide significant time savings in managing your cloud." msgstr "" #: ../manage_db_config.rst:18 msgid "Bulk-configure a database or databases" msgstr "" #: ../manage_db_config.rst:20 msgid "**List available options**" msgstr "" #: ../manage_db_config.rst:22 msgid "" "First, determine which configuration options you can set. Different data " "store versions have different configuration options." msgstr "" #: ../manage_db_config.rst:25 msgid "" "List the names and IDs of all available versions of the ``mysql`` data store:" msgstr "" #: ../manage_db_config.rst:38 msgid "" "Pass in the data store version ID with the :command:`trove configuration-" "parameter-list` command to get the available options:" msgstr "" #: ../manage_db_config.rst:85 msgid "" "In this example, the :command:`configuration-parameter-list` command returns " "a list of options that work with MySQL 5.5." msgstr "" #: ../manage_db_config.rst:88 msgid "**Create a configuration group**" msgstr "" #: ../manage_db_config.rst:90 msgid "" "A configuration group contains a comma-separated list of key-value pairs. " "Each pair consists of a configuration option and its value." msgstr "" #: ../manage_db_config.rst:93 msgid "" "You can create a configuration group by using the :command:`trove " "configuration-create` command. The general syntax for this command is:" msgstr "" #: ../manage_db_config.rst:101 msgid "*NAME*. The name you want to use for this group." msgstr "" #: ../manage_db_config.rst:103 msgid "*VALUES*. The list of key-value pairs." msgstr "" #: ../manage_db_config.rst:105 msgid "*DATASTORE_NAME*. The name of the associated data store." msgstr "" #: ../manage_db_config.rst:107 msgid "Set *VALUES* as a JSON dictionary, for example:" msgstr "" #: ../manage_db_config.rst:113 msgid "" "This example creates a configuration group called ``group1``. ``group1`` " "contains just one key and value pair, and this pair sets the ``sync_binlog`` " "option to ``1``." msgstr "" #: ../manage_db_config.rst:131 msgid "**Examine your existing configuration**" msgstr "" #: ../manage_db_config.rst:133 msgid "" "Before you use the newly-created configuration group, look at how the " "``sync_binlog`` option is configured on your database. Replace the following " "sample connection values with values that connect to your database:" msgstr "" #: ../manage_db_config.rst:150 msgid "" "As you can see, the ``sync_binlog`` option is currently set to ``0`` for the " "``myDB7`` database." msgstr "" #: ../manage_db_config.rst:153 msgid "**Change the database configuration using a configuration group**" msgstr "" #: ../manage_db_config.rst:155 msgid "" "You can change a database's configuration by attaching a configuration group " "to a database instance. You do this by using the :command:`trove " "configuration-attach` command and passing in the ID of the database instance " "and the ID of the configuration group." msgstr "" #: ../manage_db_config.rst:160 msgid "Get the ID of the database instance:" msgstr "" #: ../manage_db_config.rst:172 msgid "Get the ID of the configuration group:" msgstr "" #: ../manage_db_config.rst:184 msgid "Attach the configuration group to the database instance:" msgstr "" #: ../manage_db_config.rst:188 msgid "" "This command syntax pertains only to python-troveclient version 1.0.6 and " "later. Earlier versions require you to pass in the configuration group ID as " "the first argument." msgstr "" #: ../manage_db_config.rst:196 msgid "**Re-examine the database configuration**" msgstr "" #: ../manage_db_config.rst:198 msgid "Display the ``sync_binlog`` setting again:" msgstr "" #: ../manage_db_config.rst:209 msgid "" "As you can see, the ``sync_binlog`` option is now set to ``1``, as specified " "in the ``group1`` configuration group." msgstr "" #: ../manage_db_config.rst:212 msgid "" "**Conclusion.** Using a configuration group to set a single option on a " "single database is obviously a trivial example. However, configuration " "groups can provide major efficiencies when you consider that:" msgstr "" #: ../manage_db_config.rst:216 msgid "A configuration group can specify a large number of option values." msgstr "" #: ../manage_db_config.rst:218 msgid "" "You can apply a configuration group to hundreds or thousands of database " "instances in your environment." msgstr "" #: ../manage_db_config.rst:221 msgid "" "Used in this way, configuration groups let you modify your database cloud " "configuration, on the fly, on a massive scale." msgstr "" #: ../manage_db_config.rst:224 msgid "" "**Maintenance.** There are also a number of useful maintenance features for " "working with configuration groups. You can:" msgstr "" #: ../manage_db_config.rst:227 msgid "" "Disassociate a configuration group from a database instance, using the :" "command:`trove configuration-detach` command." msgstr "" #: ../manage_db_config.rst:230 msgid "" "Modify a configuration group on the fly, using the :command:`trove " "configuration-patch` command." msgstr "" #: ../manage_db_config.rst:233 msgid "" "Find out what instances are using a configuration group, using the :command:" "`trove configuration-instances` command." msgstr "" #: ../manage_db_config.rst:236 msgid "" "Delete a configuration group, using the :command:`trove configuration-" "delete` command. You might want to do this if no instances use a group." msgstr "" #: ../managing-openstack-object-storage-with-swift-cli.rst:3 msgid "Manage objects and containers" msgstr "" #: ../managing-openstack-object-storage-with-swift-cli.rst:5 msgid "" "The OpenStack Object Storage service provides the ``swift`` client, which is " "a command-line interface (CLI). Use this client to list objects and " "containers, upload objects to containers, and download or delete objects " "from containers. You can also gather statistics and update metadata for " "accounts, containers, and objects." msgstr "" #: ../managing-openstack-object-storage-with-swift-cli.rst:11 msgid "" "This client is based on the native swift client library, ``client.py``, " "which seamlessly re-authenticates if the current token expires during " "processing, retries operations multiple times, and provides a processing " "concurrency of 10." msgstr "" #: ../sdk.rst:3 msgid "OpenStack Python SDK" msgstr "" #: ../sdk.rst:5 msgid "" "The OpenStack Python Software Development Kit (SDK) is used to write Python " "automation scripts that create and manage resources in your OpenStack cloud. " "The SDK implements Python bindings to the OpenStack API, which enables you " "to perform automation tasks in Python by making calls on Python objects, " "rather than making REST calls directly. All OpenStack command-line tools are " "implemented using the Python SDK." msgstr "" #: ../sdk.rst:12 msgid "You should also be familiar with:" msgstr "" #: ../sdk.rst:14 msgid "RESTful web services" msgstr "" #: ../sdk.rst:15 msgid "HTTP/1.1" msgstr "" #: ../sdk.rst:16 msgid "JSON and XML data serialization formats" msgstr "" #: ../sdk_assign_cors_headers.rst:3 msgid "Assign CORS headers to requests" msgstr "" #: ../sdk_assign_cors_headers.rst:5 msgid "" ":term:`Cross-Origin Resource Sharing (CORS)` is a specification that defines " "how browsers and servers communicate across origins by using HTTP headers, " "such as those assigned by Object Storage API requests. The Object Storage " "API supports the following headers:" msgstr "" #: ../sdk_assign_cors_headers.rst:10 msgid "Access-Control-Allow-Credentials" msgstr "" #: ../sdk_assign_cors_headers.rst:11 msgid "Access-Control-Allow-Methods" msgstr "" #: ../sdk_assign_cors_headers.rst:12 msgid "Access-Control-Allow-Origin" msgstr "" #: ../sdk_assign_cors_headers.rst:13 msgid "Access-Control-Expose-Headers" msgstr "" #: ../sdk_assign_cors_headers.rst:14 msgid "Access-Control-Max-Age" msgstr "" #: ../sdk_assign_cors_headers.rst:15 msgid "Access-Control-Request-Headers" msgstr "" #: ../sdk_assign_cors_headers.rst:16 msgid "Access-Control-Request-Method" msgstr "" #: ../sdk_assign_cors_headers.rst:17 msgid "Origin" msgstr "" #: ../sdk_assign_cors_headers.rst:19 msgid "" "You can only assign these headers to objects. For more information, see `www." "w3.org/TR/access-control/ `__." msgstr "" #: ../sdk_assign_cors_headers.rst:22 msgid "" "This example assigns the file origin to the ``Origin`` header, which ensures " "that the file originated from a reputable source." msgstr "" #: ../sdk_authenticate.rst:5 msgid "Authenticate" msgstr "" #: ../sdk_authenticate.rst:7 msgid "" "When using the SDK, you must authenticate against an OpenStack endpoint " "before you can use OpenStack services. Each project uses a slightly " "different syntax for authentication." msgstr "" #: ../sdk_authenticate.rst:11 msgid "" "You must typically authenticate against a specific version of a service. For " "example, a client might need to authenticate against Identity v2.0." msgstr "" #: ../sdk_authenticate.rst:14 msgid "" "Python scripts that use the OpenStack SDK must have access to the " "credentials contained in the OpenStack RC file. Because credentials are " "sensitive information, do not include them in your scripts. This guide " "assumes that users source the PROJECT-openrc.sh file and access the " "credentials by using the environment variables in the Python scripts." msgstr "" #: ../sdk_authenticate_against_compute_endpoint.rst:3 msgid "Authenticate against a Compute endpoint" msgstr "" #: ../sdk_authenticate_against_compute_endpoint.rst:5 msgid "" "To authenticate against a Compute endpoint, instantiate a `novaclient.v2." "client.Client `__ object:" msgstr "" #: ../sdk_authenticate_against_compute_endpoint.rst:18 msgid "" "Alternatively, you can instantiate a ``novaclient.client.Client`` object and " "pass the version number:" msgstr "" #: ../sdk_authenticate_against_compute_endpoint.rst:31 msgid "" "If you authenticate against an endpoint that uses a custom authentication " "back end, you must load the authentication plug-in and pass it to the " "constructor." msgstr "" #: ../sdk_authenticate_against_compute_endpoint.rst:35 msgid "" "The Rackspace public cloud is an OpenStack deployment that uses a custom " "authentication back end. To authenticate against this cloud, you must " "install the `rackspace-novaclient `__ library that contains the Rackspace authentication plug-in, " "called ``rackspace``. The following Python code shows the additional " "modifications required to instantiate a ``Client`` object that can " "authenticate against the Rackspace custom authentication back end." msgstr "" #: ../sdk_authenticate_against_compute_endpoint.rst:59 msgid "" "If you set the ``OS_AUTH_SYSTEM`` environment variable, check for this " "variable in your Python script to determine whether you need to load a " "custom authentication back end:" msgstr "" #: ../sdk_authenticate_against_identity_endpoint.rst:3 msgid "Authenticate against an Identity endpoint" msgstr "" #: ../sdk_authenticate_against_identity_endpoint.rst:5 msgid "" "To authenticate against the Identity v2.0 endpoint, instantiate a " "`keystoneclient.v2\\_0.client.Client `__ object:" msgstr "" #: ../sdk_authenticate_against_identity_endpoint.rst:18 msgid "" "After you instantiate a ``Client`` object, you can retrieve the token by " "accessing its ``auth_token`` attribute object:" msgstr "" #: ../sdk_authenticate_against_identity_endpoint.rst:27 msgid "" "If the OpenStack cloud is configured to use public-key infrastructure (PKI) " "tokens, the Python script output looks something like this::" msgstr "" #: ../sdk_authenticate_against_identity_endpoint.rst:40 msgid "" "This example shows a subset of a PKI token. A complete token is over 5000 " "characters long." msgstr "" #: ../sdk_authenticate_against_image_service_endpoint.rst:3 msgid "Authenticate against an Image service endpoint" msgstr "" #: ../sdk_authenticate_against_image_service_endpoint.rst:5 msgid "" "To authenticate against an Image service endpoint, instantiate a " "`glanceclient.v2.client.Client `__ object:" msgstr "" #: ../sdk_authenticate_against_networking_endpoint.rst:3 msgid "Authenticate against a Networking endpoint" msgstr "" #: ../sdk_authenticate_against_networking_endpoint.rst:5 msgid "" "To authenticate against a Networking endpoint, instantiate a ``neutronclient." "v2_0.client.Client`` object:" msgstr "" #: ../sdk_authenticate_against_networking_endpoint.rst:18 msgid "" "You can also authenticate by explicitly specifying the endpoint and token:" msgstr "" #: ../sdk_compute_apis.rst:3 msgid "Compute" msgstr "" #: ../sdk_compute_apis.rst:5 msgid "" "To use the information in this section, you must be familiar with OpenStack " "Compute." msgstr "" # #-#-#-#-# sdk_compute_apis.pot (End User Guide 1.0.0) #-#-#-#-# # #-#-#-#-# sdk_neutron_apis.pot (End User Guide 1.0.0) #-#-#-#-# #: ../sdk_compute_apis.rst:9 ../sdk_neutron_apis.rst:13 msgid "Set environment variables" msgstr "" #: ../sdk_compute_apis.rst:11 msgid "" "To set up environmental variables and authenticate against Compute API " "endpoints, see :ref:`sdk_authenticate`." msgstr "" #: ../sdk_compute_apis.rst:17 msgid "Get OpenStack credentials (API v2)" msgstr "" #: ../sdk_compute_apis.rst:19 msgid "This example uses the ``get_nova_credentials_v2`` method:" msgstr "" # #-#-#-#-# sdk_compute_apis.pot (End User Guide 1.0.0) #-#-#-#-# # #-#-#-#-# sdk_neutron_apis.pot (End User Guide 1.0.0) #-#-#-#-# #: ../sdk_compute_apis.rst:32 ../sdk_neutron_apis.rst:44 #: ../sdk_neutron_apis.rst:70 msgid "" "This code resides in the ``credentials.py`` file, which all samples import." msgstr "" #: ../sdk_compute_apis.rst:35 msgid "" "Use the ``get_nova_credentials_v2()`` method to populate and get a " "dictionary:" msgstr "" #: ../sdk_compute_apis.rst:43 msgid "List servers (API v2)" msgstr "" #: ../sdk_compute_apis.rst:45 msgid "The following program lists servers by using the Compute API v2." msgstr "" # #-#-#-#-# sdk_compute_apis.pot (End User Guide 1.0.0) #-#-#-#-# # #-#-#-#-# sdk_neutron_apis.pot (End User Guide 1.0.0) #-#-#-#-# #: ../sdk_compute_apis.rst:47 ../sdk_compute_apis.rst:89 #: ../sdk_compute_apis.rst:167 ../sdk_compute_apis.rst:248 #: ../sdk_compute_apis.rst:342 ../sdk_compute_apis.rst:407 #: ../sdk_compute_apis.rst:474 ../sdk_neutron_apis.rst:295 #: ../sdk_neutron_apis.rst:395 ../sdk_neutron_apis.rst:473 #: ../sdk_neutron_apis.rst:525 ../sdk_neutron_apis.rst:574 msgid "Import the following modules:" msgstr "" #: ../sdk_compute_apis.rst:54 ../sdk_compute_apis.rst:175 msgid "" "Get Nova credentials. See :ref:`Get OpenStack credentials (API v2) `." msgstr "" # #-#-#-#-# sdk_compute_apis.pot (End User Guide 1.0.0) #-#-#-#-# # #-#-#-#-# sdk_neutron_apis.pot (End User Guide 1.0.0) #-#-#-#-# #: ../sdk_compute_apis.rst:57 ../sdk_compute_apis.rst:100 #: ../sdk_compute_apis.rst:178 ../sdk_compute_apis.rst:274 #: ../sdk_compute_apis.rst:365 ../sdk_compute_apis.rst:433 #: ../sdk_compute_apis.rst:498 ../sdk_neutron_apis.rst:308 msgid "" "Instantiate the ``nova_client`` client object by using the ``credentials`` " "dictionary object:" msgstr "" #: ../sdk_compute_apis.rst:64 msgid "List servers by calling ``servers.list`` on ``nova_client`` object:" msgstr "" #: ../sdk_compute_apis.rst:71 msgid "List server code listing example" msgstr "" #: ../sdk_compute_apis.rst:85 msgid "Create server (API v2)" msgstr "" #: ../sdk_compute_apis.rst:87 msgid "" "The following program creates a server (VM) by using the Compute API v2." msgstr "" #: ../sdk_compute_apis.rst:97 ../sdk_compute_apis.rst:430 #: ../sdk_compute_apis.rst:495 msgid "" "Get OpenStack credentials. See :ref:`Get OpenStack credentials (API v2) `." msgstr "" #: ../sdk_compute_apis.rst:107 msgid "" "Get the flavor and image to use to create a server. This code uses the " "``cirros`` image, the ``m1.tiny`` flavor, and the ``private`` network:" msgstr "" #: ../sdk_compute_apis.rst:117 msgid "To create the server, use the network, image, and flavor:" msgstr "" #: ../sdk_compute_apis.rst:125 msgid "" "Run the \"Sleep for five seconds\" command, and determine whether the server/" "vm was created by calling ``nova_client.servers.list()``:" msgstr "" #: ../sdk_compute_apis.rst:136 msgid "Create server code listing example" msgstr "" #: ../sdk_compute_apis.rst:163 msgid "Delete server (API v2)" msgstr "" #: ../sdk_compute_apis.rst:165 msgid "" "The following program deletes a server (VM) by using the Compute API v2." msgstr "" #: ../sdk_compute_apis.rst:185 msgid "Determine whether the ``vm1`` server exists:" msgstr "" #: ../sdk_compute_apis.rst:187 msgid "List servers: ``servers_list``." msgstr "" #: ../sdk_compute_apis.rst:189 msgid "Iterate over ``servers_list`` and compare name with ``vm1``." msgstr "" #: ../sdk_compute_apis.rst:191 msgid "" "If true, set the variable name ``server_exists`` to ``True`` and break from " "the for loop:" msgstr "" #: ../sdk_compute_apis.rst:207 msgid "" "If the server exists, run the ``delete`` method of the ``nova_client." "servers`` object:" msgstr "" #: ../sdk_compute_apis.rst:215 msgid "Delete server code example" msgstr "" #: ../sdk_compute_apis.rst:243 msgid "Update server (API v2)" msgstr "" #: ../sdk_compute_apis.rst:245 msgid "" "The following program updates the name of a server (VM) by using the Compute " "API v2." msgstr "" #: ../sdk_compute_apis.rst:256 msgid "" "``print_server`` is a method defined in ``utils.py`` and prints the server " "details as shown in the code listing below:" msgstr "" #: ../sdk_compute_apis.rst:271 msgid "" "Get OpenStack Credentials. See :ref:`Get OpenStack credentials (API v2) `." msgstr "" #: ../sdk_compute_apis.rst:282 msgid "" "Get the server instance using ``server_id`` and print the details by calling " "``print_server`` method:" msgstr "" #: ../sdk_compute_apis.rst:292 msgid "" "Call ``server.update`` on the server object with the new value for ``name`` " "variable:" msgstr "" #: ../sdk_compute_apis.rst:299 msgid "Get the updated instance of the server:" msgstr "" #: ../sdk_compute_apis.rst:305 msgid "Call ``print_server`` again to check the update server details:" msgstr "" #: ../sdk_compute_apis.rst:312 msgid "Update server code listing example" msgstr "" #: ../sdk_compute_apis.rst:337 msgid "List flavors (API v2)" msgstr "" #: ../sdk_compute_apis.rst:339 msgid "" "The following program lists flavors and their details by using the Compute " "API v2." msgstr "" #: ../sdk_compute_apis.rst:350 msgid "" "The ``print_flavors`` method is defined in ``utils.py`` and prints the " "flavor details:" msgstr "" #: ../sdk_compute_apis.rst:362 msgid "" "Get OpenStack credentials. :ref:`Get OpenStack credentials (API v2) `." msgstr "" #: ../sdk_compute_apis.rst:372 msgid "List flavors by calling ``list()`` on ``nova_client.flavors`` object:" msgstr "" #: ../sdk_compute_apis.rst:378 msgid "Print the flavor details, id and name by calling ``print_flavors``:" msgstr "" #: ../sdk_compute_apis.rst:385 msgid "List flavors code listing example" msgstr "" #: ../sdk_compute_apis.rst:402 msgid "List floating IPs (API v2)" msgstr "" #: ../sdk_compute_apis.rst:404 msgid "" "The following program lists the floating IPs and their details by using the " "Compute API v2." msgstr "" #: ../sdk_compute_apis.rst:415 msgid "" "The ``print_values_ip`` method is defined in ``utils.py`` and prints the " "floating\\_ip object details:" msgstr "" #: ../sdk_compute_apis.rst:440 msgid "" "List floating IPs by calling ``list()`` on ``nova_client.floating_ips`` " "object:" msgstr "" #: ../sdk_compute_apis.rst:447 msgid "Print the floating IP object details by calling ``print_values_ip``:" msgstr "" #: ../sdk_compute_apis.rst:454 msgid "List floating IPs code listing example" msgstr "" #: ../sdk_compute_apis.rst:470 msgid "List hosts (API v2)" msgstr "" #: ../sdk_compute_apis.rst:472 msgid "The following program lists the hosts by using the Compute API v2." msgstr "" #: ../sdk_compute_apis.rst:482 msgid "" "The ``print_hosts`` method is defined in ``utils.py`` and prints the host " "object details:" msgstr "" #: ../sdk_compute_apis.rst:505 msgid "List hosts by calling ``list()`` on ``nova_client.hosts`` object:" msgstr "" #: ../sdk_compute_apis.rst:511 msgid "Print the host object details by calling ``print_hosts(host_list)``:" msgstr "" #: ../sdk_compute_apis.rst:518 msgid "List hosts code listing example" msgstr "" #: ../sdk_configure_access_security_instances.rst:5 msgid "" "When working with images in the SDK, you will call ``novaclient`` methods." msgstr "" #: ../sdk_configure_access_security_instances.rst:11 msgid "Add a keypair" msgstr "" #: ../sdk_configure_access_security_instances.rst:13 msgid "" "To generate a keypair, call the `novaclient.v1\\_1.keypairs.KeypairManager." "create `__ method:" msgstr "" #: ../sdk_configure_access_security_instances.rst:26 msgid "The Python script output looks something like this:" msgstr "" #: ../sdk_configure_access_security_instances.rst:38 msgid "" "You typically write the private key to a file to use it later. The file must " "be readable and writeable by only the file owner; otherwise, the SSH client " "will refuse to read the private key file. The safest way is to create the " "file with the appropriate permissions, as shown in the following example:" msgstr "" #: ../sdk_configure_access_security_instances.rst:62 msgid "Import a keypair" msgstr "" #: ../sdk_configure_access_security_instances.rst:64 msgid "" "If you have already generated a keypair with the public key located at ``~/." "ssh/id_rsa.pub``, pass the contents of the file to the `novaclient.v1\\_1." "keypairs.KeypairManager.create `__ method to import the public key to Compute:" msgstr "" #: ../sdk_configure_access_security_instances.rst:83 msgid "List keypairs" msgstr "" #: ../sdk_configure_access_security_instances.rst:85 msgid "" "To list keypairs, call the `novaclient.v1\\_1.keypairs.KeypairManager.list " "`__ method:" msgstr "" #: ../sdk_configure_access_security_instances.rst:101 msgid "" "To list security groups for the current project, call the `novaclient.v\\_1." "security\\_groups.SecurityGroupManager.list `__ method:" msgstr "" #: ../sdk_configure_access_security_instances.rst:113 msgid "" "To create a security group with a specified name and description, call the " "`novaclient.v\\_1.security\\_groups.SecurityGroupManager.create `__ method:" msgstr "" #: ../sdk_configure_access_security_instances.rst:125 msgid "" "To delete a security group, call the `novaclient.v\\_1.security\\_groups." "SecurityGroupManager.delete `__ method, passing either a " "`novaclient.v1\\_1.security\\_groups.SecurityGroup `__ object or group ID " "as an argument:" msgstr "" #: ../sdk_configure_access_security_instances.rst:150 msgid "" "Access the security group rules from the ``rules`` attribute of a " "`novaclient.v1\\_1.security\\_groups.SecurityGroup `__ object:" msgstr "" #: ../sdk_configure_access_security_instances.rst:162 msgid "" "To add a rule to a security group, call the `novaclient.v1\\_1.security" "\\_group\\_rules.SecurityGroupRuleManager.create `__ method:" msgstr "" #: ../sdk_install.rst:2 msgid "Installing OpenStack SDK" msgstr "" #: ../sdk_install.rst:4 msgid "" "Each OpenStack project has its own Python library. These libraries are " "bundled with the command-line clients. For example, the Python bindings for " "the Compute API are bundled with the python-novaclient package." msgstr "" #: ../sdk_install.rst:8 msgid "" "For details about how to install the clients, see :doc:`../common/" "cli_install_openstack_command_line_clients`." msgstr "" #: ../sdk_manage_images.rst:3 msgid "Manage images" msgstr "" #: ../sdk_manage_images.rst:5 msgid "" "When working with images in the SDK, you will call both ``glance`` and " "``nova`` methods." msgstr "" #: ../sdk_manage_images.rst:13 msgid "" "To list the available images, call the ``glanceclient.v2.images.Controller." "list`` method:" msgstr "" #: ../sdk_manage_images.rst:22 msgid "" "The images method returns a Python generator, as shown in the following " "interaction with the Python interpreter:" msgstr "" #: ../sdk_manage_images.rst:85 msgid "Get image by ID" msgstr "" #: ../sdk_manage_images.rst:87 msgid "" "To retrieve an image object from its ID, call the ``glanceclient.v2.images." "Controller.get`` method:" msgstr "" #: ../sdk_manage_images.rst:100 msgid "Get image by name" msgstr "" #: ../sdk_manage_images.rst:102 msgid "" "The Image service Python bindings do not support the retrieval of an image " "object by name. However, the Compute Python bindings enable you to get an " "image object by name. To get an image object by name, call the ``novaclient." "v1_1.images.ImageManager.find`` method:" msgstr "" #: ../sdk_manage_images.rst:119 msgid "" "To upload an image, call the ``glanceclient.v2.images.ImageManager.create`` " "method:" msgstr "" #: ../sdk_neutron_apis.rst:3 msgid "Networking" msgstr "" #: ../sdk_neutron_apis.rst:5 msgid "" "To use the information in this section, you should have a general " "understanding of OpenStack Networking, OpenStack Compute, and the " "integration between the two. You should also have access to a plug-in that " "implements the Networking API v2.0." msgstr "" #: ../sdk_neutron_apis.rst:15 msgid "Make sure that you set the relevant environment variables." msgstr "" #: ../sdk_neutron_apis.rst:17 msgid "" "As an example, see the sample shell file that sets these variables to get " "credentials:" msgstr "" #: ../sdk_neutron_apis.rst:30 msgid "Get credentials" msgstr "" #: ../sdk_neutron_apis.rst:32 msgid "The examples in this section use the ``get_credentials`` method:" msgstr "" #: ../sdk_neutron_apis.rst:47 msgid "Use the ``get_credentials()`` method to populate and get a dictionary:" msgstr "" #: ../sdk_neutron_apis.rst:56 msgid "Get Nova credentials" msgstr "" #: ../sdk_neutron_apis.rst:58 msgid "The examples in this section use the ``get_nova_credentials`` method:" msgstr "" #: ../sdk_neutron_apis.rst:73 msgid "" "Use the ``get_nova_credentials()`` method to populate and get a dictionary:" msgstr "" #: ../sdk_neutron_apis.rst:83 msgid "Print values" msgstr "" #: ../sdk_neutron_apis.rst:85 msgid "" "The examples in this section use the ``print_values`` and " "``print_values_server`` methods:" msgstr "" #: ../sdk_neutron_apis.rst:119 msgid "This code resides in the ``utils.py`` file, which all samples import." msgstr "" #: ../sdk_neutron_apis.rst:126 msgid "The following program creates a network:" msgstr "" #: ../sdk_neutron_apis.rst:157 msgid "List networks" msgstr "" #: ../sdk_neutron_apis.rst:159 msgid "The following program lists networks:" msgstr "" #: ../sdk_neutron_apis.rst:174 ../sdk_neutron_apis.rst:242 #: ../sdk_neutron_apis.rst:498 msgid "For ``print_values``, see :ref:`Print values `." msgstr "" #: ../sdk_neutron_apis.rst:181 msgid "The following program creates a port:" msgstr "" #: ../sdk_neutron_apis.rst:216 msgid "" "For ``get_nova_credentials``, see :ref:`Get Nova credentials `." msgstr "" #: ../sdk_neutron_apis.rst:219 msgid "For ``get_credentials``, see :ref:`Get credentials `." msgstr "" #: ../sdk_neutron_apis.rst:224 msgid "List ports" msgstr "" #: ../sdk_neutron_apis.rst:226 msgid "The following program lists ports:" msgstr "" #: ../sdk_neutron_apis.rst:240 msgid "For ``get_credentials`` see :ref:`Get credentials `." msgstr "" #: ../sdk_neutron_apis.rst:247 msgid "List server ports" msgstr "" #: ../sdk_neutron_apis.rst:249 msgid "The following program lists the ports for a server:" msgstr "" #: ../sdk_neutron_apis.rst:289 msgid "Create router and add port to subnet" msgstr "" #: ../sdk_neutron_apis.rst:291 msgid "" "This example queries OpenStack Networking to create a router and add a port " "to a subnet." msgstr "" #: ../sdk_neutron_apis.rst:305 msgid "" "Get Nova Credentials. See :ref:'Get Nova credentials '." msgstr "" #: ../sdk_neutron_apis.rst:315 msgid "Create a router and add a port to the subnet:" msgstr "" #: ../sdk_neutron_apis.rst:346 msgid "Create router: complete code listing example" msgstr "" #: ../sdk_neutron_apis.rst:389 msgid "Delete a network" msgstr "" #: ../sdk_neutron_apis.rst:391 msgid "This example queries OpenStack Networking to delete a network." msgstr "" #: ../sdk_neutron_apis.rst:393 msgid "To delete a network:" msgstr "" #: ../sdk_neutron_apis.rst:402 ../sdk_neutron_apis.rst:481 msgid "" "Get credentials. See :ref:`Get Nova credentials `." msgstr "" #: ../sdk_neutron_apis.rst:404 ../sdk_neutron_apis.rst:483 #: ../sdk_neutron_apis.rst:535 ../sdk_neutron_apis.rst:584 msgid "" "Instantiate the ``neutron`` client object by using the ``credentials`` " "dictionary object:" msgstr "" #: ../sdk_neutron_apis.rst:411 msgid "Delete the network:" msgstr "" #: ../sdk_neutron_apis.rst:435 msgid "Delete network: complete code listing example" msgstr "" #: ../sdk_neutron_apis.rst:469 msgid "List routers" msgstr "" #: ../sdk_neutron_apis.rst:471 msgid "This example queries OpenStack Networking to list all routers." msgstr "" #: ../sdk_neutron_apis.rst:490 msgid "List the routers:" msgstr "" #: ../sdk_neutron_apis.rst:501 msgid "List routers: complete code listing example" msgstr "" #: ../sdk_neutron_apis.rst:521 msgid "List security groups" msgstr "" #: ../sdk_neutron_apis.rst:523 msgid "This example queries OpenStack Networking to list security groups." msgstr "" #: ../sdk_neutron_apis.rst:533 msgid "Get credentials. See :ref:`Get credentials `." msgstr "" #: ../sdk_neutron_apis.rst:542 msgid "List Security groups" msgstr "" #: ../sdk_neutron_apis.rst:550 msgid "List security groups: complete code listing example" msgstr "" #: ../sdk_neutron_apis.rst:570 msgid "List subnets" msgstr "" #: ../sdk_neutron_apis.rst:572 msgid "This example queries OpenStack Networking to list subnets." msgstr "" #: ../sdk_neutron_apis.rst:582 msgid "Get credentials. See :ref:'Get credentials '." msgstr "" #: ../sdk_neutron_apis.rst:591 msgid "List subnets:" msgstr "" #: ../sdk_neutron_apis.rst:599 msgid "List subnets: complete code listing example" msgstr "" #: ../sdk_schedule_objects_for_deletion.rst:3 msgid "Schedule objects for deletion" msgstr "" #: ../sdk_schedule_objects_for_deletion.rst:5 msgid "" "To determine whether your Object Storage system supports this feature, see :" "doc:`managing-openstack-object-storage-with-swift-cli`. Alternatively, check " "with your service provider." msgstr "" #: ../sdk_schedule_objects_for_deletion.rst:9 msgid "" "Scheduling an object for deletion is helpful for managing objects that you " "do not want to permanently store, such as log files, recurring full backups " "of a dataset, or documents or images that become outdated at a specified " "time." msgstr "" #: ../sdk_schedule_objects_for_deletion.rst:14 msgid "" "To schedule an object for deletion, include one of these headers with the " "``PUT`` or ``POST`` request on the object:" msgstr "" #: ../sdk_schedule_objects_for_deletion.rst:18 msgid "" "A UNIX epoch timestamp, in integer form. For example, ``1348691905`` " "represents ``Wed, 26 Sept 2012 20:38:25 GMT``. It specifies the time you " "want the object to expire, no longer be served, and be deleted completely " "from the object store." msgstr "" #: ../sdk_schedule_objects_for_deletion.rst:22 msgid "X-Delete-At" msgstr "" #: ../sdk_schedule_objects_for_deletion.rst:25 msgid "" "An integer value which specifies the number of seconds from the time of the " "request to when you want to delete the object. This header is converted to a " "``X-Delete-At`` header that is set to the sum of the ``X-Delete-After`` " "value plus the current time, in seconds." msgstr "" #: ../sdk_schedule_objects_for_deletion.rst:29 msgid "X-Delete-After" msgstr "" #: ../sdk_schedule_objects_for_deletion.rst:33 msgid "" "Use http://www.epochconverter.com/ to convert dates to and from epoch " "timestamps and for batch conversions." msgstr "" #: ../sdk_schedule_objects_for_deletion.rst:36 msgid "" "Use the POST method to assign expiration headers to existing objects that " "you want to expire." msgstr "" #: ../sdk_schedule_objects_for_deletion.rst:39 msgid "" "In this example, the ``X-Delete-At`` header is assigned a UNIX epoch " "timestamp in integer form for ``Mon, 11 Jun 2012 15:38:25 GMT``." msgstr "" #: ../sdk_schedule_objects_for_deletion.rst:48 msgid "" "In this example, the ``X-Delete-After`` header is set to 864000 seconds. The " "object expires after this time." msgstr "" #: ../set_up_clustering.rst:3 msgid "Set up database clustering" msgstr "" #: ../set_up_clustering.rst:5 msgid "" "You can store data across multiple machines by setting up MongoDB sharded " "clusters." msgstr "" #: ../set_up_clustering.rst:8 msgid "Each cluster includes:" msgstr "" #: ../set_up_clustering.rst:10 msgid "" "One or more *shards*. Each shard consists of a three member replica set " "(three instances organized as a replica set)." msgstr "" #: ../set_up_clustering.rst:13 msgid "" "One or more *query routers*. A query router is the machine that your " "application actually connects to. This machine is responsible for " "communicating with the config server to figure out where the requested data " "is stored. It then accesses and returns the data from the appropriate " "shard(s)." msgstr "" #: ../set_up_clustering.rst:19 msgid "" "One or more *config servers*. Config servers store the metadata that links " "requested data with the shard that contains it." msgstr "" #: ../set_up_clustering.rst:22 msgid "This example shows you how to set up a MongoDB sharded cluster." msgstr "" #: ../set_up_clustering.rst:26 msgid "**Before you begin.** Make sure that:" msgstr "" #: ../set_up_clustering.rst:28 msgid "" "The administrative user has registered a MongoDB datastore type and version." msgstr "" #: ../set_up_clustering.rst:31 msgid "" "The administrative user has created an appropriate :ref:`flavor that meets " "the MongoDB minimum requirements `." msgstr "" #: ../set_up_clustering.rst:35 msgid "Set up clustering" msgstr "" #: ../set_up_clustering.rst:37 msgid "**Create a cluster**" msgstr "" #: ../set_up_clustering.rst:39 msgid "" "Create a cluster by using the :command:`trove cluster-create` command. This " "command creates a one-shard cluster. Pass in:" msgstr "" #: ../set_up_clustering.rst:42 msgid "The name of the cluster." msgstr "" #: ../set_up_clustering.rst:44 msgid "The name and version of the datastore you want to use." msgstr "" #: ../set_up_clustering.rst:46 msgid "" "The three instances you want to include in the replication set for the first " "shard. Specify each instance by using the :option:`--instance` argument and " "the associated flavor ID and volume size. Use the same flavor ID and volume " "size for each instance. In this example, flavor ``7`` is a custom flavor " "that meets the MongoDB minimum requirements." msgstr "" #: ../set_up_clustering.rst:71 msgid "**Display cluster information**" msgstr "" #: ../set_up_clustering.rst:73 msgid "" "Display information about a cluster by using the :command:`trove cluster-" "show` command. Pass in the ID of the cluster." msgstr "" #: ../set_up_clustering.rst:76 msgid "" "The cluster ID displays when you first create a cluster. (If you need to " "find it later on, use the :command:`trove cluster-list` command to list the " "names and IDs of all the clusters in your system.)" msgstr "" #: ../set_up_clustering.rst:100 msgid "" "**Your application connects to this IP address.** The trove :command:" "`cluster-show` command displays the IP address of the query router. This is " "the IP address your application uses to retrieve data from the database." msgstr "" #: ../set_up_clustering.rst:105 msgid "**List cluster instances**" msgstr "" #: ../set_up_clustering.rst:107 msgid "" "List the instances in a cluster by using the :command:`trove cluster-" "instances` command." msgstr "" #: ../set_up_clustering.rst:121 msgid "" "**Naming conventions for replication sets and instances.** Note that the " "``Name`` column displays an instance name that includes the replication set " "name. The replication set names and instance names are automatically " "generated, following these rules:" msgstr "" #: ../set_up_clustering.rst:126 msgid "" "**Replication set name.** This name consists of the cluster name, followed " "by the string -rs\\ *n*, where *n* is 1 for the first replication set you " "create, 2 for the second replication set, and so on. In this example, the " "cluster name is ``cluster1``, and there is only one replication set, so the " "replication set name is ``cluster1-rs1``." msgstr "" #: ../set_up_clustering.rst:133 msgid "" "**Instance name.** This name consists of the replication set name followed " "by the string -*n*, where *n* is 1 for the first instance in a replication " "set, 2 for the second instance, and so on. In this example, the instance " "names are ``cluster1-rs1-1``, ``cluster1-rs1-2``, and ``cluster1-rs1-3``." msgstr "" #: ../set_up_clustering.rst:139 msgid "**List clusters**" msgstr "" #: ../set_up_clustering.rst:141 msgid "" "List all the clusters in your system, using the :command:`trove cluster-" "list` command." msgstr "" #: ../set_up_clustering.rst:154 msgid "**Delete a cluster**" msgstr "" #: ../set_up_clustering.rst:156 msgid "Delete a cluster, using the :command:`trove cluster-delete` command." msgstr "" #: ../set_up_clustering.rst:163 msgid "Query routers and config servers" msgstr "" #: ../set_up_clustering.rst:165 msgid "" "Each cluster includes at least one query router and one config server. Query " "routers and config servers count against your quota. When you delete a " "cluster, the system deletes the associated query router(s) and config " "server(s)." msgstr "" #: ../set_up_replication.rst:3 msgid "Set up database replication" msgstr "" #: ../set_up_replication.rst:5 msgid "" "You can create a replica of an existing database instance. When you make " "subsequent changes to the original instance, the system automatically " "applies those changes to the replica." msgstr "" #: ../set_up_replication.rst:9 msgid "Replicas are read-only." msgstr "" #: ../set_up_replication.rst:11 msgid "" "When you create a replica, do not specify the :option:`--users` or :option:" "`--databases` options." msgstr "" #: ../set_up_replication.rst:14 msgid "" "You can choose a smaller volume or flavor for a replica than for the " "original, but the replica's volume must be big enough to hold the data " "snapshot from the original." msgstr "" #: ../set_up_replication.rst:18 msgid "This example shows you how to replicate a MySQL database instance." msgstr "" #: ../set_up_replication.rst:21 msgid "Set up replication" msgstr "" #: ../set_up_replication.rst:23 msgid "**Get the instance ID**" msgstr "" #: ../set_up_replication.rst:25 msgid "Get the ID of the original instance you want to replicate:" msgstr "" #: ../set_up_replication.rst:36 msgid "**Create the replica**" msgstr "" #: ../set_up_replication.rst:38 msgid "" "Create a new instance that will be a replica of the original instance. You " "do this by passing in the :option:`--replica_of` option with the :command:" "`trove create` command. This example creates a replica called ``replica_1``. " "``replica_1`` is a replica of the original instance, ``base_1``:" msgstr "" #: ../set_up_replication.rst:49 msgid "**Verify replication status**" msgstr "" #: ../set_up_replication.rst:51 msgid "" "Pass in ``replica_1``'s instance ID with the :command:`trove show` command " "to verify that the newly created ``replica_1`` instance is a replica of the " "original ``base_1``. Note that the ``replica_of`` property is set to the ID " "of ``base_1``." msgstr "" #: ../set_up_replication.rst:74 msgid "" "Now pass in ``base_1``'s instance ID with the :command:`trove show` command " "to list the replica(s) associated with the original instance. Note that the " "``replicas`` property is set to the ID of ``replica_1``. If there are " "multiple replicas, they appear as a comma-separated list." msgstr "" #: ../set_up_replication.rst:99 msgid "**Detach the replica**" msgstr "" #: ../set_up_replication.rst:101 msgid "" "If the original instance goes down, you can detach the replica. The replica " "becomes a standalone database instance. You can then take the new standalone " "instance and create a new replica of that instance." msgstr "" #: ../set_up_replication.rst:105 msgid "You detach a replica using the :command:`trove detach-replica` command:" msgstr ""