diff --git a/README.rst b/README.rst
index 8f3519f819..91ca57b440 100644
--- a/README.rst
+++ b/README.rst
@@ -22,7 +22,6 @@ It includes these manuals:
* Command-Line Interface Reference
* Configuration Reference
* Documentation Contributor Guide
- * End User Guide
* High Availability Guide
* Installation Tutorials
* Networking Guide
@@ -54,17 +53,18 @@ virtual environment and build all guides (HTML only):
You can also build a specific guide.
-For example, to build *OpenStack End User Guide*, use the following command::
+For example, to build *OpenStack Virtual Machine Image Guide*, use the
+following command::
- $ tox -e build -- user-guide
+ $ tox -e build -- image-guide
You can find the root of the generated HTML documentation at::
- doc/user-guide/build/html/index.html
+ doc/image-guide/build/html/index.html
To build a specific guide with a PDF file, add a ``-pdf`` option like::
- $ tox -e build -- user-guide --pdf
+ $ tox -e build -- image-guide --pdf
The generated PDF file will be copied to the root directory of the
generated HTML documentation.
diff --git a/doc-tools-check-languages.conf b/doc-tools-check-languages.conf
index 4d27ad7084..59fc1861fc 100644
--- a/doc-tools-check-languages.conf
+++ b/doc-tools-check-languages.conf
@@ -7,12 +7,12 @@ declare -A BOOKS=(
["cs"]="install-guide"
["de"]="install-guide"
["fr"]="install-guide"
- ["id"]="image-guide install-guide user-guide"
- ["ja"]="ha-guide image-guide install-guide ops-guide user-guide"
+ ["id"]="image-guide install-guide"
+ ["ja"]="ha-guide image-guide install-guide ops-guide"
["ko_KR"]="install-guide"
["ru"]="install-guide"
["tr_TR"]="image-guide install-guide arch-design"
- ["zh_CN"]="install-guide user-guide"
+ ["zh_CN"]="install-guide"
)
# draft books
@@ -48,7 +48,6 @@ declare -A SPECIAL_BOOKS=(
["install-guide"]="RST"
["networking-guide"]="RST"
["ops-guide"]="RST"
- ["user-guide"]="RST"
# Do not translate for now, we need to fix our scripts first to
# generate the content properly.
["install-guide-debconf"]="skip"
diff --git a/doc/common/app-support.rst b/doc/common/app-support.rst
index ef893bb9db..dc58f8f3af 100644
--- a/doc/common/app-support.rst
+++ b/doc/common/app-support.rst
@@ -60,10 +60,7 @@ The following books explain how to configure and run an OpenStack cloud:
* `Virtual Machine Image Guide `_
-The following books explain how to use the OpenStack Dashboard and
-command-line clients:
-
-* `End User Guide `_
+The following book explains how to use the command-line clients:
* `Command-Line Interface Reference
`_
diff --git a/doc/contributor-guide/source/blueprints-and-specs.rst b/doc/contributor-guide/source/blueprints-and-specs.rst
index cf49a694a4..3bf5ad9e8a 100644
--- a/doc/contributor-guide/source/blueprints-and-specs.rst
+++ b/doc/contributor-guide/source/blueprints-and-specs.rst
@@ -204,9 +204,6 @@ Guides for deployers and administrators
Guides for end users
--------------------
-* `OpenStack End User Guide `_:
- Shows OpenStack end users how to create and manage resources in an
- OpenStack cloud with the OpenStack dashboard and OpenStack client commands.
* `OpenStack API Guide
`_:
A brief overview of how to send REST API requests to endpoints for
@@ -222,10 +219,6 @@ Guides for end users
- Source location
- Target location
- * - OpenStack End User Guide
- - https://git.openstack.org/cgit/openstack/openstack-manuals/tree/doc/user-guide
- - https://docs.openstack.org/user-guide/
-
* - OpenStack API Guide
- https://git.openstack.org/cgit/openstack/api-site/tree/api-quick-start
- https://developer.openstack.org/api-guide/quick-start/
diff --git a/doc/contributor-guide/source/docs-builds.rst b/doc/contributor-guide/source/docs-builds.rst
index defd583109..ffddc1d7e7 100644
--- a/doc/contributor-guide/source/docs-builds.rst
+++ b/doc/contributor-guide/source/docs-builds.rst
@@ -183,7 +183,7 @@ To get the ``.html`` output locally, switch to the directory containing a
The RST source is built into HTML using Sphinx, so that it is displayed on
the *docs.openstack.org/*. For example:
-https://docs.openstack.org/user-guide/.
+https://docs.openstack.org/image-guide/.
Using Tox to check builds
-------------------------
diff --git a/doc/contributor-guide/source/rst-conv/references.rst b/doc/contributor-guide/source/rst-conv/references.rst
index e1484546c6..459e6bf5d6 100644
--- a/doc/contributor-guide/source/rst-conv/references.rst
+++ b/doc/contributor-guide/source/rst-conv/references.rst
@@ -61,14 +61,14 @@ To link to some external locations, format the RST source as follows:
.. code-block:: none
- Here is a link to the User guide: https://docs.openstack.org/user-guide/.
+ Here is a link to the Image guide: https://docs.openstack.org/image-guide/.
Here is an external web link with a link title:
- `User guide `_.
+ `Image guide `_.
**Output**
-Here is a link to the User guide: https://docs.openstack.org/user-guide/.
+Here is a link to the Image guide: https://docs.openstack.org/image-guide/.
Here is an external web link with a link title:
-`User guide `_.
+`Image guide `_.
diff --git a/doc/contributor-guide/source/topic-tags.rst b/doc/contributor-guide/source/topic-tags.rst
index 35eafd81ea..57f7d2c9a3 100644
--- a/doc/contributor-guide/source/topic-tags.rst
+++ b/doc/contributor-guide/source/topic-tags.rst
@@ -53,9 +53,6 @@ Based on the topic your request refers to, use the following tags:
[training]
Training labs, Training guides, and Upstream Training materials
-[user-guide]
- OpenStack End User Guide
-
[WIP]
A marker that means the commit is a work in progress
diff --git a/doc/image-guide/source/centos-image.rst b/doc/image-guide/source/centos-image.rst
index c0d0f5aa83..99a9edefd9 100644
--- a/doc/image-guide/source/centos-image.rst
+++ b/doc/image-guide/source/centos-image.rst
@@ -390,5 +390,5 @@ The underlying image file that you created with the
For example, you can upload the ``/tmp/centos.qcow2``
image to the Image service by using the :command:`openstack image create`
command. For more information, see the
-`Create or update an image
-`__.
+`python-openstackclient command list
+`__.
diff --git a/doc/image-guide/source/fedora-image.rst b/doc/image-guide/source/fedora-image.rst
index 14a7a7d9d7..70db3b4119 100644
--- a/doc/image-guide/source/fedora-image.rst
+++ b/doc/image-guide/source/fedora-image.rst
@@ -279,5 +279,5 @@ The underlying image file that you created with the
For example, you can upload the ``/tmp/fedora.qcow2``
image to the Image service by using the :command:`openstack image create`
command. For more information, see the
-`Create or update an image
-`__.
+`python-openstackclient command list
+`__.
diff --git a/doc/image-guide/source/obtain-images.rst b/doc/image-guide/source/obtain-images.rst
index 2b7f9fd435..7697abbccb 100644
--- a/doc/image-guide/source/obtain-images.rst
+++ b/doc/image-guide/source/obtain-images.rst
@@ -9,8 +9,8 @@ support the SSH key pair and user data injection.
Because many of the images disable SSH password authentication
by default, boot the image with an injected key pair.
You can ``SSH`` into the instance with the private key and default
-login account. See the `OpenStack End User Guide
-`_
+login account. See `Configure access and security for instances
+`_
for more information on how to create and inject key pairs with OpenStack.
CentOS
diff --git a/doc/image-guide/source/openstack-images.rst b/doc/image-guide/source/openstack-images.rst
index 9ab07ce87d..469b39782f 100644
--- a/doc/image-guide/source/openstack-images.rst
+++ b/doc/image-guide/source/openstack-images.rst
@@ -276,8 +276,7 @@ Process user data and other metadata (cloud-init)
In addition to the ssh public key, an image might need
additional information from OpenStack, such as
-`Provide user data to instances `_,
+to povide user data to instances,
that the user submitted when requesting the image.
For example, you might want to set the host name of the instance
when it is booted. Or, you might wish to configure your image
diff --git a/doc/user-guide/setup.cfg b/doc/user-guide/setup.cfg
deleted file mode 100644
index ba421141a8..0000000000
--- a/doc/user-guide/setup.cfg
+++ /dev/null
@@ -1,27 +0,0 @@
-[metadata]
-name = openstackuserguide
-summary = OpenStack End User Guide
-author = OpenStack
-author-email = openstack-docs@lists.openstack.org
-home-page = https://docs.openstack.org/
-classifier =
-Environment :: OpenStack
-Intended Audience :: Information Technology
-Intended Audience :: System Administrators
-License :: OSI Approved :: Apache Software License
-Operating System :: POSIX :: Linux
-Topic :: Documentation
-
-[global]
-setup-hooks =
- pbr.hooks.setup_hook
-
-[files]
-
-[build_sphinx]
-warning-is-error = 1
-build-dir = build
-source-dir = source
-
-[wheel]
-universal = 1
diff --git a/doc/user-guide/setup.py b/doc/user-guide/setup.py
deleted file mode 100644
index 736375744d..0000000000
--- a/doc/user-guide/setup.py
+++ /dev/null
@@ -1,30 +0,0 @@
-#!/usr/bin/env python
-# Copyright (c) 2013 Hewlett-Packard Development Company, L.P.
-#
-# Licensed under the Apache License, Version 2.0 (the "License");
-# you may not use this file except in compliance with the License.
-# You may obtain a copy of the License at
-#
-# http://www.apache.org/licenses/LICENSE-2.0
-#
-# Unless required by applicable law or agreed to in writing, software
-# distributed under the License is distributed on an "AS IS" BASIS,
-# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
-# implied.
-# See the License for the specific language governing permissions and
-# limitations under the License.
-
-# THIS FILE IS MANAGED BY THE GLOBAL REQUIREMENTS REPO - DO NOT EDIT
-import setuptools
-
-# In python < 2.7.4, a lazy loading of package `pbr` will break
-# setuptools if some other modules registered functions in `atexit`.
-# solution from: http://bugs.python.org/issue15881#msg170215
-try:
- import multiprocessing # noqa
-except ImportError:
- pass
-
-setuptools.setup(
- setup_requires=['pbr'],
- pbr=True)
diff --git a/doc/user-guide/source/backup-db-incremental.rst b/doc/user-guide/source/backup-db-incremental.rst
deleted file mode 100644
index cd08792532..0000000000
--- a/doc/user-guide/source/backup-db-incremental.rst
+++ /dev/null
@@ -1,127 +0,0 @@
-=======================
-Use incremental backups
-=======================
-
-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.
-
-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.
-
-This example shows you how to use incremental backups with a MySQL
-database.
-
-**Assumptions.** Assume that you have created a regular
-backup for the following database instance:
-
-- Instance name: ``guest1``
-
-- ID of the instance (``INSTANCE_ID``):
- ``792a6a56-278f-4a01-9997-d997fa126370``
-
-- ID of the regular backup artifact (``BACKUP_ID``):
- ``6dc3a9b7-1f3e-4954-8582-3f2e4942cddd``
-
-Create and use incremental backups
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-#. **Create your first incremental backup**
-
- Use the :command:`trove backup-create` command and specify:
-
- - The ``INSTANCE_ID`` of the database instance you are doing the
- incremental backup for (in this example,
- ``792a6a56-278f-4a01-9997-d997fa126370``)
-
- - The name of the incremental backup you are creating: ``backup1.1``
-
- - 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``
-
- .. code-block:: console
-
- $ trove backup-create INSTANCE_ID backup1.1 --parent BACKUP_ID
-
- +-------------+--------------------------------------+
- | Property | Value |
- +-------------+--------------------------------------+
- | created | 2014-03-19T14:09:13 |
- | description | None |
- | id | 1d474981-a006-4f62-b25f-43d7b8a7097e |
- | instance_id | 792a6a56-278f-4a01-9997-d997fa126370 |
- | locationRef | None |
- | name | backup1.1 |
- | parent_id | 6dc3a9b7-1f3e-4954-8582-3f2e4942cddd |
- | size | None |
- | status | NEW |
- | updated | 2014-03-19T14:09:13 |
- +-------------+--------------------------------------+
-
- 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``).
-
-#. **Create your second incremental backup**
-
- 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``.
-
- .. code-block:: console
-
- $ trove backup-create INSTANCE_ID backup1.2 --parent BACKUP_ID
-
- +-------------+--------------------------------------+
- | Property | Value |
- +-------------+--------------------------------------+
- | created | 2014-03-19T14:09:13 |
- | description | None |
- | id | bb84a240-668e-49b5-861e-6a98b67e7a1f |
- | instance_id | 792a6a56-278f-4a01-9997-d997fa126370 |
- | locationRef | None |
- | name | backup1.2 |
- | parent_id | 1d474981-a006-4f62-b25f-43d7b8a7097e |
- | size | None |
- | status | NEW |
- | updated | 2014-03-19T14:09:13 |
- +-------------+--------------------------------------+
-
-#. **Restore using incremental backups**
-
- 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``.
-
- To incorporate your incremental backups, you simply use the
- `--backup`` parameter to pass in the ``BACKUP_ID`` of your most
- recent incremental backup. The Database service handles the
- complexities of applying the chain of all previous incremental
- backups.
-
- .. code-block:: console
-
- $ trove create guest2 10 --size 1 --backup BACKUP_ID
-
- +-------------------+-----------------------------------------------------------+
- | Property | Value |
- +-------------------+-----------------------------------------------------------+
- | created | 2014-03-19T14:10:56 |
- | datastore | {u'version': u'mysql-5.5', u'type': u'mysql'} |
- | datastore_version | mysql-5.5 |
- | flavor | {u'id': u'10', u'links': |
- | | [{u'href': u'https://10.125.1.135:8779/v1.0/ |
- | | 626734041baa4254ae316de52a20b390/flavors/10', u'rel': |
- | | u'self'}, {u'href': u'https://10.125.1.135:8779/ |
- | | flavors/10', u'rel': u'bookmark'}]} |
- | id | a3680953-eea9-4cf2-918b-5b8e49d7e1b3 |
- | name | guest2 |
- | status | BUILD |
- | updated | 2014-03-19T14:10:56 |
- | volume | {u'size': 1} |
- +-------------------+-----------------------------------------------------------+
-
diff --git a/doc/user-guide/source/backup-db.rst b/doc/user-guide/source/backup-db.rst
deleted file mode 100644
index cb7f26f2b2..0000000000
--- a/doc/user-guide/source/backup-db.rst
+++ /dev/null
@@ -1,232 +0,0 @@
-=============================
-Backup and restore a database
-=============================
-
-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.
-
-This example shows you how to back up and restore a MySQL database.
-
-#. **Backup the database instance**
-
- As background, assume that you have created a database
- instance with the following
- characteristics:
-
- - Name of the database instance: ``guest1``
-
- - Flavor ID: ``10``
-
- - Root volume size: ``2``
-
- - Databases: ``db1`` and ``db2``
-
- - Users: The ``user1`` user with the ``password`` password
-
- First, get the ID of the ``guest1`` database instance by using the
- :command:`trove list` command:
-
- .. code-block:: console
-
- $ trove list
-
- +--------------------------------------+--------+-----------+-------------------+--------+-----------+------+
- | id | name | datastore | datastore_version | status | flavor_id | size |
- +--------------------------------------+--------+-----------+-------------------+--------+-----------+------+
- | 97b4b853-80f6-414f-ba6f-c6f455a79ae6 | guest1 | mysql | mysql-5.5 | ACTIVE | 10 | 2 |
- +--------------------------------------+--------+-----------+-------------------+--------+-----------+------+
-
- 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``:
-
- .. note::
-
- 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.
-
- .. code-block:: console
-
- $ trove backup-create INSTANCE_ID backup1
-
- +-------------+--------------------------------------+
- | Property | Value |
- +-------------+--------------------------------------+
- | created | 2014-03-18T17:09:07 |
- | description | None |
- | id | 8af30763-61fd-4aab-8fe8-57d528911138 |
- | instance_id | 97b4b853-80f6-414f-ba6f-c6f455a79ae6 |
- | locationRef | None |
- | name | backup1 |
- | parent_id | None |
- | size | None |
- | status | NEW |
- | updated | 2014-03-18T17:09:07 |
- +-------------+--------------------------------------+
-
- Note that the command returns both the ID of the original instance
- (``instance_id``) and the ID of the backup artifact (``id``).
-
- Later on, use the :command:`trove backup-list` command to get this
- information:
-
- .. code-block:: console
-
- $ trove backup-list
- +--------------------------------------+--------------------------------------+---------+-----------+-----------+---------------------+
- | id | instance_id | name | status | parent_id | updated |
- +--------------------------------------+--------------------------------------+---------+-----------+-----------+---------------------+
- | 8af30763-61fd-4aab-8fe8-57d528911138 | 97b4b853-80f6-414f-ba6f-c6f455a79ae6 | backup1 | COMPLETED | None | 2014-03-18T17:09:11 |
- +--------------------------------------+--------------------------------------+---------+-----------+-----------+---------------------+
-
- 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``.
-
- .. code-block:: console
-
- $ trove backup-show BACKUP_ID
-
- +-------------+----------------------------------------------------+
- | Property | Value |
- +-------------+----------------------------------------------------+
- | created | 2014-03-18T17:09:07 |
- | description | None |
- | id | 8af...138 |
- | instance_id | 97b...ae6 |
- | locationRef | http://10.0.0.1:.../.../8af...138.xbstream.gz.enc |
- | name | backup1 |
- | parent_id | None |
- | size | 0.17 |
- | status | COMPLETED |
- | updated | 2014-03-18T17:09:11 |
- +-------------+----------------------------------------------------+
-
-#. **Restore a database instance**
-
- 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``.
-
- - You specify that the new ``guest2`` instance has the same flavor
- (``10``) and the same root volume size (``2``) as the original
- ``guest1`` instance.
-
- - You use the ``--backup`` argument to indicate that this new
- instance is based on the backup artifact identified by
- ``BACKUP_ID``. In this example, replace ``BACKUP_ID`` with
- ``8af30763-61fd-4aab-8fe8-57d528911138``.
-
- .. code-block:: console
-
- $ trove create guest2 10 --size 2 --backup BACKUP_ID
-
- +-------------------+----------------------------------------------+
- | Property | Value |
- +-------------------+----------------------------------------------+
- | created | 2014-03-18T17:12:03 |
- | datastore | {u'version': u'mysql-5.5', u'type': u'mysql'}|
- |datastore_version | mysql-5.5 |
- | flavor | {u'id': u'10', u'links': [{u'href': ...]} |
- | id | ac7a2b35-a9b4-4ff6-beac-a1bcee86d04b |
- | name | guest2 |
- | status | BUILD |
- | updated | 2014-03-18T17:12:03 |
- | volume | {u'size': 2} |
- +-------------------+----------------------------------------------+
-
-#. **Verify backup**
-
- Now check that the new ``guest2`` instance has the same
- characteristics as the original ``guest1`` instance.
-
- Start by getting the ID of the new ``guest2`` instance.
-
- .. code-block:: console
-
- $ trove list
-
- +-----------+--------+-----------+-------------------+--------+-----------+------+
- | id | name | datastore | datastore_version | status | flavor_id | size |
- +-----------+--------+-----------+-------------------+--------+-----------+------+
- | 97b...ae6 | guest1 | mysql | mysql-5.5 | ACTIVE | 10 | 2 |
- | ac7...04b | guest2 | mysql | mysql-5.5 | ACTIVE | 10 | 2 |
- +-----------+--------+-----------+-------------------+--------+-----------+------+
-
- 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``.
-
- .. code-block:: console
-
- $ trove show INSTANCE_ID
-
- +-------------------+--------------------------------------+
- | Property | Value |
- +-------------------+--------------------------------------+
- | created | 2014-03-18T17:12:03 |
- | datastore | mysql |
- | datastore_version | mysql-5.5 |
- | flavor | 10 |
- | id | ac7a2b35-a9b4-4ff6-beac-a1bcee86d04b |
- | ip | 10.0.0.3 |
- | name | guest2 |
- | status | ACTIVE |
- | updated | 2014-03-18T17:12:06 |
- | volume | 2 |
- | volume_used | 0.18 |
- +-------------------+--------------------------------------+
-
- Note that the data store, flavor ID, and volume size have the same
- values as in the original ``guest1`` instance.
-
- Use the :command:`trove database-list` command to check that the original
- databases (``db1`` and ``db2``) are present on the restored instance.
-
- .. code-block:: console
-
- $ trove database-list INSTANCE_ID
-
- +--------------------+
- | name |
- +--------------------+
- | db1 |
- | db2 |
- | performance_schema |
- | test |
- +--------------------+
-
- Use the :command:`trove user-list` command to check that the original user
- (``user1``) is present on the restored instance.
-
- .. code-block:: console
-
- $ trove user-list INSTANCE_ID
-
- +--------+------+-----------+
- | name | host | databases |
- +--------+------+-----------+
- | user1 | % | db1, db2 |
- +--------+------+-----------+
-
-#. **Notify users**
-
- 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.)
-
-#. **Clean up**
-
- At this point, you might want to delete the disabled ``guest1``
- instance, by using the :command:`trove delete` command.
-
- .. code-block:: console
-
- $ trove delete INSTANCE_ID
-
diff --git a/doc/user-guide/source/cli-access-instance-through-a-console.rst b/doc/user-guide/source/cli-access-instance-through-a-console.rst
deleted file mode 100644
index a6244c757f..0000000000
--- a/doc/user-guide/source/cli-access-instance-through-a-console.rst
+++ /dev/null
@@ -1,52 +0,0 @@
-====================================
-Access an instance through a console
-====================================
-
-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.
-
-There are three remote console access methods commonly used with
-OpenStack:
-
-novnc
- An in-browser VNC client implemented using HTML5 Canvas and
- WebSockets
-
-spice
- A complete in-browser client solution for interaction with
- virtualized instances
-
-xvpvnc
- A Java client offering console access to an instance
-
-Example:
-
-To access an instance through a remote console, run the following
-command:
-
-.. code-block:: console
-
- $ openstack console url show INSTANCE_NAME --xvpvnc
-
-The command returns a URL from which you can access your instance:
-
-.. code-block:: console
-
- +--------+------------------------------------------------------------------------------+
- | Type | Url |
- +--------+------------------------------------------------------------------------------+
- | xvpvnc | http://192.168.5.96:6081/console?token=c83ae3a3-15c4-4890-8d45-aefb494a8d6c |
- +--------+------------------------------------------------------------------------------+
-
-``--xvpvnc`` can be replaced by any of the above values as connection
-types.
-
-When using SPICE to view the console of an instance, a browser plugin
-can be used directly on the instance page, or the
-:command:`openstack console url show` command can be used with it, as well, by
-returning a token-authenticated address, as in the example above.
-
-For further information and comparisons (including security
-considerations), see the `Security
-Guide `__.
diff --git a/doc/user-guide/source/cli-ceilometer.rst b/doc/user-guide/source/cli-ceilometer.rst
deleted file mode 100644
index d75a3bc8bd..0000000000
--- a/doc/user-guide/source/cli-ceilometer.rst
+++ /dev/null
@@ -1,132 +0,0 @@
-=======================
-Measure cloud resources
-=======================
-
-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.
-
-To model data, Telemetry uses the following abstractions:
-
-Meter
- 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.
-
- A meter has the following attributes:
-
- * String name
-
- * A unit of measurement
-
- * 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)
-
-Sample
- 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``.
-
-Statistic
- 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:
-
- * **count**. The number of samples in each period.
- * **max**. The maximum number of sample volumes in each period.
- * **min**. The minimum number of sample volumes in each period.
- * **avg**. The average of sample volumes over each period.
- * **sum**. The sum of sample volumes over each period.
-
-Alarm
- 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.
-
-This example uses the :command:`openstack` client to create an auto-scaling
-stack and the :command:`ceilometer` client to measure resources.
-
-#. Create an auto-scaling stack by running the following command.
- The ``-f`` option specifies the name of the stack template
- file, and the ``-P`` option specifies the ``KeyName``
- parameter as ``heat_key``:
-
- .. code-block:: console
-
- $ openstack stack create --template cfn/F17/AutoScalingCeilometer.yaml \
- --parameter "KeyName=heat_key" mystack
-
-#. List the heat resources that were created:
-
- .. code-block:: console
-
- $ openstack stack resource list mystack
- +---------------+--------------------------------------+------------------+-----------------+---------------------+
- | resource_name | physical_resource_id | resource_type | resource_status | updated_time |
- +---------------+--------------------------------------+------------------+-----------------+---------------------+
- | server | 1b3a7c13-42be-4999-a2a1-8fbefd00062b | OS::Nova::Server | CREATE_COMPLETE | 2013-10-02T05:53:41Z |
- | ... | ... | ... | ... | ... |
- +---------------+--------------------------------------+------------------+-----------------+---------------------+
-
-#. List the alarms that are set:
-
- .. code-block:: console
-
- $ ceilometer alarm-list
- +--------------------------------------+------------------------------+-------------------+---------+------------+----------------------------------+
- | Alarm ID | Name | State | Enabled | Continuous | Alarm condition |
- +--------------------------------------+------------------------------+-------------------+---------+------------+----------------------------------+
- | 4f896b40-0859-460b-9c6a-b0d329814496 | as-CPUAlarmLow-i6qqgkf2fubs | insufficient data | True | False | cpu_util < 15.0 during 1x 60s |
- | 75d8ecf7-afc5-4bdc-95ff-19ed9ba22920 | as-CPUAlarmHigh-sf4muyfruy5m | insufficient data | True | False | cpu_util > 50.0 during 1x 60s |
- +--------------------------------------+------------------------------+-------------------+---------+------------+----------------------------------+
-
-#. List the meters that are set:
-
- .. code-block:: console
-
- $ ceilometer meter-list
- +-------------+------------+----------+--------------------------------------+----------------------------------+----------------------------------+
- | Name | Type | Unit | Resource ID | User ID | Project ID |
- +-------------+------------+----------+--------------------------------------+----------------------------------+----------------------------------+
- | cpu | cumulative | ns | 3965b41b-81b0-4386-bea5-6ec37c8841c1 | d1a2996d3b1f4e0e8645ba9650308011 | bf03bf32e3884d489004ac995ff7a61c |
- | cpu | cumulative | ns | 62520a83-73c7-4084-be54-275fe770ef2c | d1a2996d3b1f4e0e8645ba9650308011 | bf03bf32e3884d489004ac995ff7a61c |
- | cpu_util | gauge | % | 3965b41b-81b0-4386-bea5-6ec37c8841c1 | d1a2996d3b1f4e0e8645ba9650308011 | bf03bf32e3884d489004ac995ff7a61c |
- +-------------+------------+----------+--------------------------------------+----------------------------------+----------------------------------+
-
-#. List samples:
-
- .. code-block:: console
-
- $ ceilometer sample-list -m cpu_util
- +--------------------------------------+----------+-------+---------------+------+---------------------+
- | Resource ID | Name | Type | Volume | Unit | Timestamp |
- +--------------------------------------+----------+-------+---------------+------+---------------------+
- | 3965b41b-81b0-4386-bea5-6ec37c8841c1 | cpu_util | gauge | 3.98333333333 | % | 2013-10-02T10:50:12 |
- +--------------------------------------+----------+-------+---------------+------+---------------------+
-
-#. View statistics:
-
- .. code-block:: console
-
- $ ceilometer statistics -m cpu_util
- +--------+---------------------+---------------------+-------+---------------+---------------+---------------+---------------+----------+---------------------+---------------------+
- | Period | Period Start | Period End | Count | Min | Max | Sum | Avg | Duration | Duration Start | Duration End |
- +--------+---------------------+---------------------+-------+---------------+---------------+---------------+---------------+----------+---------------------+---------------------+
- | 0 | 2013-10-02T10:50:12 | 2013-10-02T10:50:12 | 1 | 3.98333333333 | 3.98333333333 | 3.98333333333 | 3.98333333333 | 0.0 | 2013-10-02T10:50:12 | 2013-10-02T10:50:12 |
- +--------+---------------------+---------------------+-------+---------------+---------------+---------------+---------------+----------+---------------------+---------------------+
diff --git a/doc/user-guide/source/cli-change-the-size-of-your-server.rst b/doc/user-guide/source/cli-change-the-size-of-your-server.rst
deleted file mode 100644
index 792f6ea101..0000000000
--- a/doc/user-guide/source/cli-change-the-size-of-your-server.rst
+++ /dev/null
@@ -1,120 +0,0 @@
-==============================
-Change the size of your server
-==============================
-
-Change the size of a server by changing its flavor.
-
-#. Show information about your server, including its size, which is shown
- as the value of the flavor property:
-
- .. code-block:: console
-
- $ openstack server show myCirrosServer
- +--------------------------------------+----------------------------------------------------------+
- | Field | Value |
- +--------------------------------------+----------------------------------------------------------+
- | OS-DCF:diskConfig | AUTO |
- | OS-EXT-AZ:availability_zone | nova |
- | OS-EXT-SRV-ATTR:host | node-7.domain.tld |
- | OS-EXT-SRV-ATTR:hypervisor_hostname | node-7.domain.tld |
- | OS-EXT-SRV-ATTR:instance_name | instance-000000f3 |
- | OS-EXT-STS:power_state | 1 |
- | OS-EXT-STS:task_state | None |
- | OS-EXT-STS:vm_state | active |
- | OS-SRV-USG:launched_at | 2016-10-26T01:13:15.000000 |
- | OS-SRV-USG:terminated_at | None |
- | accessIPv4 | |
- | accessIPv6 | |
- | addresses | admin_internal_net=192.168.111.139 |
- | config_drive | True |
- | created | 2016-10-26T01:12:38Z |
- | flavor | m1.small (2) |
- | hostId | d815539ce1a8fad3d597c3438c13f1229d3a2ed66d1a75447845a2f3 |
- | id | 67bc9a9a-5928-47c4-852c-3631fef2a7e8 |
- | image | cirros-test (dc5ec4b8-5851-4be8-98aa-df7a9b8f538f) |
- | key_name | None |
- | name | myCirrosServer |
- | os-extended-volumes:volumes_attached | [] |
- | progress | 0 |
- | project_id | c08367f25666480f9860c6a0122dfcc4 |
- | properties | |
- | security_groups | [{u'name': u'default'}] |
- | status | ACTIVE |
- | updated | 2016-10-26T01:13:00Z |
- | user_id | 0209430e30924bf9b5d8869990234e44 |
- +--------------------------------------+----------------------------------------------------------+
-
- The size (flavor) of the server is ``m1.small (2)``.
-
-#. List the available flavors with the following command:
-
- .. code-block:: console
-
- $ openstack flavor list
- +-----+-----------+-------+------+-----------+-------+-----------+
- | ID | Name | RAM | Disk | Ephemeral | VCPUs | Is_Public |
- +-----+-----------+-------+------+-----------+-------+-----------+
- | 1 | m1.tiny | 512 | 1 | 0 | 1 | True |
- | 2 | m1.small | 2048 | 20 | 0 | 1 | True |
- | 3 | m1.medium | 4096 | 40 | 0 | 2 | True |
- | 4 | m1.large | 8192 | 80 | 0 | 4 | True |
- | 5 | m1.xlarge | 16384 | 160 | 0 | 8 | True |
- +-----+-----------+-------+------+-----------+-------+-----------+
-
-#. To resize the server, use the :command:`openstack server resize` command and
- add the server ID or name and the new flavor. For example:
-
- .. code-block:: console
-
- $ openstack server resize --flavor 4 myCirrosServer
-
-
- .. note::
-
- By default, the :command:`openstack server 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 operating system is allowed
- to complete the shutdown. The default timeout is 60 seconds.
- See `Description of Compute configuration options
- `_
- for details.
-
- 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.
-
-#. Show the status for your server.
-
- .. code-block:: console
-
- $ openstack server list
- +----------------------+----------------+--------+-----------------------------------------+
- | ID | Name | Status | Networks |
- +----------------------+----------------+--------+-----------------------------------------+
- | 67bc9a9a-5928-47c... | myCirrosServer | RESIZE | admin_internal_net=192.168.111.139 |
- +----------------------+----------------+--------+-----------------------------------------+
-
- When the resize completes, the status becomes VERIFY\_RESIZE.
-
-#. Confirm the resize,for example:
-
- .. code-block:: console
-
- $ openstack server resize --confirm 67bc9a9a-5928-47c4-852c-3631fef2a7e8
-
- The server status becomes ACTIVE.
-
-#. If the resize fails or does not work as expected, you can revert the
- resize. For example:
-
- .. code-block:: console
-
- $ openstack server resize --revert 67bc9a9a-5928-47c4-852c-3631fef2a7e8
-
- The server status becomes ACTIVE.
diff --git a/doc/user-guide/source/cli-cheat-sheet.rst b/doc/user-guide/source/cli-cheat-sheet.rst
deleted file mode 100644
index 9c72dec74a..0000000000
--- a/doc/user-guide/source/cli-cheat-sheet.rst
+++ /dev/null
@@ -1,400 +0,0 @@
-============================================
-OpenStack command-line interface cheat sheet
-============================================
-
-Here is a list of common commands for reference.
-
-Identity (keystone)
-~~~~~~~~~~~~~~~~~~~
-
-List all users
-
-.. code-block:: console
-
- $ openstack user list
-
-List Identity service catalog
-
-.. code-block:: console
-
- $ openstack catalog list
-
-Images (glance)
-~~~~~~~~~~~~~~~
-
-List images you can access
-
-.. code-block:: console
-
- $ openstack image list
-
-Delete specified image
-
-.. code-block:: console
-
- $ openstack image delete IMAGE
-
-Describe a specific image
-
-.. code-block:: console
-
- $ openstack image show IMAGE
-
-Update image
-
-.. code-block:: console
-
- $ openstack image set IMAGE
-
-Upload kernel image
-
-.. code-block:: console
-
- $ openstack image create "cirros-threepart-kernel" \
- --disk-format aki --container-format aki --public \
- --file ~/images/cirros-0.3.5-x86_64-kernel
-
-Upload RAM image
-
-.. code-block:: console
-
- $ openstack image create "cirros-threepart-ramdisk" \
- --disk-format ari --container-format ari --public \
- --file ~/images/cirros-0.3.5-x86_64-initramfs
-
-Upload three-part image
-
-.. code-block:: console
-
- $ openstack image create "cirros-threepart" --disk-format ami \
- --container-format ami --public \
- --property kernel_id=$KID-property ramdisk_id=$RID \
- --file ~/images/cirros-0.3.5-x86_64-rootfs.img
-
-Register raw image
-
-.. code-block:: console
-
- $ openstack image create "cirros-raw" --disk-format raw \
- --container-format bare --public \
- --file ~/images/cirros-0.3.5-x86_64-disk.img
-
-Compute (nova)
-~~~~~~~~~~~~~~
-
-List instances, check status of instance
-
-.. code-block:: console
-
- $ openstack server list
-
-List images
-
-.. code-block:: console
-
- $ openstack image list
-
-Create a flavor named m1.tiny
-
-.. code-block:: console
-
- $ openstack flavor create --ram 512 --disk 1 --vcpus 1 m1.tiny
-
-List flavors
-
-.. code-block:: console
-
- $ openstack flavor list
-
-Boot an instance using flavor and image names (if names are unique)
-
-.. code-block:: console
-
- $ openstack server create --image IMAGE --flavor FLAVOR INSTANCE_NAME
- $ openstack server create --image cirros-0.3.5-x86_64-uec --flavor m1.tiny \
- MyFirstInstance
-
-Log in to the instance (from Linux)
-
-.. note::
-
- The :command:`ip` command is available only on Linux. Using :command:`ip netns` provides your
- environment a copy of the network stack with its own routes, firewall
- rules, and network devices for better troubleshooting.
-
-.. code-block:: console
-
- # ip netns
- # ip netns exec NETNS_NAME ssh USER@SERVER
- # ip netns exec qdhcp-6021a3b4-8587-4f9c-8064-0103885dfba2 \
- ssh cirros@10.0.0.2
-
-.. note::
-
- In CirrOS, the password for user ``cirros`` is ``cubswin:)``.
- For any other operating system, use SSH keys.
-
-Log in to the instance with a public IP address (from Mac)
-
-.. code-block:: console
-
- $ ssh cloud-user@128.107.37.150
-
-Show details of instance
-
-.. code-block:: console
-
- $ openstack server show NAME
- $ openstack server show MyFirstInstance
-
-View console log of instance
-
-.. code-block:: console
-
- $ openstack console log show MyFirstInstance
-
-Set metadata on an instance
-
-.. code-block:: console
-
- $ nova meta volumeTwoImage set newmeta='my meta data'
-
-Create an instance snapshot
-
-.. code-block:: console
-
- $ openstack image create volumeTwoImage snapshotOfVolumeImage
- $ openstack image show snapshotOfVolumeImage
-
-Pause, suspend, stop, rescue, resize, rebuild, reboot an instance
------------------------------------------------------------------
-
-Pause
-
-.. code-block:: console
-
- $ openstack server pause NAME
- $ openstack server pause volumeTwoImage
-
-Unpause
-
-.. code-block:: console
-
- $ openstack server unpause NAME
-
-Suspend
-
-.. code-block:: console
-
- $ openstack server suspend NAME
-
-Unsuspend
-
-.. code-block:: console
-
- $ openstack server resume NAME
-
-Stop
-
-.. code-block:: console
-
- $ openstack server stop NAME
-
-Start
-
-.. code-block:: console
-
- $ openstack server start NAME
-
-Rescue
-
-.. code-block:: console
-
- $ openstack server rescue NAME
- $ openstack server rescue NAME --rescue_image_ref RESCUE_IMAGE
-
-Resize
-
-.. code-block:: console
-
- $ openstack server resize NAME FLAVOR
- $ openstack server resize my-pem-server m1.small
- $ openstack server resize --confirm my-pem-server1
-
-Rebuild
-
-.. code-block:: console
-
- $ openstack server rebuild NAME IMAGE
- $ openstack server rebuild newtinny cirros-qcow2
-
-Reboot
-
-.. code-block:: console
-
- $ openstack server reboot NAME
- $ openstack server reboot newtinny
-
-Inject user data and files into an instance
-
-.. code-block:: console
-
- $ openstack server create --user-data FILE INSTANCE
- $ openstack server create --user-data userdata.txt --image cirros-qcow2 \
- --flavor m1.tiny MyUserdataInstance2
-
-To validate that the file was injected, use ssh to connect to the instance,
-and look in ``/var/lib/cloud`` for the file.
-
-Inject a keypair into an instance and access the instance with that
-keypair
-
-Create keypair
-
-.. code-block:: console
-
- $ openstack keypair create test > test.pem
- $ chmod 600 test.pem
-
-Start an instance (boot)
-
-.. code-block:: console
-
- $ openstack server create --image cirros-0.3.5-x86_64 --flavor m1.small \
- --key-name test MyFirstServer
-
-Use ssh to connect to the instance
-
-.. code-block:: console
-
- # ip netns exec qdhcp-98f09f1e-64c4-4301-a897-5067ee6d544f \
- ssh -i test.pem cirros@10.0.0.4
-
-Manage security groups
-
-Add rules to default security group allowing ping and SSH between
-instances in the default security group
-
-.. code-block:: console
-
- $ openstack security group rule create default \
- --remote-group default --protocol icmp
- $ openstack security group rule create default \
- --remote-group default --dst-port 22
-
-Networking (neutron)
-~~~~~~~~~~~~~~~~~~~~
-
-Create network
-
-.. code-block:: console
-
- $ openstack network create NETWORK_NAME
-
-Create a subnet
-
-.. code-block:: console
-
- $ openstack subnet create --subnet-pool SUBNET --network NETWORK SUBNET_NAME
- $ openstack subnet create --subnet-pool 10.0.0.0/29 --network net1 subnet1
-
-Block Storage (cinder)
-~~~~~~~~~~~~~~~~~~~~~~
-
-Used to manage volumes and volume snapshots that attach to instances.
-
-Create a new volume
-
-.. code-block:: console
-
- $ openstack volume create --size SIZE_IN_GB NAME
- $ openstack volume create --size 1 MyFirstVolume
-
-Boot an instance and attach to volume
-
-.. code-block:: console
-
- $ openstack server create --image cirros-qcow2 --flavor m1.tiny MyVolumeInstance
-
-List all volumes, noticing the volume status
-
-.. code-block:: console
-
- $ openstack volume list
-
-Attach a volume to an instance after the instance is active, and the
-volume is available
-
-.. code-block:: console
-
- $ openstack server add volume INSTANCE_ID VOLUME_ID
- $ openstack server add volume MyVolumeInstance 573e024d-5235-49ce-8332-be1576d323f8
-
-.. note::
-
- On the Xen Hypervisor it is possible to provide a specific device name instead of
- automatic allocation. For example:
-
-.. code-block:: console
-
- $ openstack server add volume --device /dev/vdb MyVolumeInstance 573e024d..1576d323f8
-
- This is not currently possible when using non-Xen hypervisors with OpenStack.
-
-Manage volumes after login into the instance
-
-List storage devices
-
-.. code-block:: console
-
- # fdisk -l
-
-Make filesystem on volume
-
-.. code-block:: console
-
- # mkfs.ext3 /dev/vdb
-
-Create a mountpoint
-
-.. code-block:: console
-
- # mkdir /myspace
-
-Mount the volume at the mountpoint
-
-.. code-block:: console
-
- # mount /dev/vdb /myspace
-
-Create a file on the volume
-
-.. code-block:: console
-
- # touch /myspace/helloworld.txt
- # ls /myspace
-
-Unmount the volume
-
-.. code-block:: console
-
- # umount /myspace
-
-Object Storage (swift)
-~~~~~~~~~~~~~~~~~~~~~~
-
-Display information for the account, container, or object
-
-.. code-block:: console
-
- $ swift stat
- $ swift stat ACCOUNT
- $ swift stat CONTAINER
- $ swift stat OBJECT
-
-List containers
-
-.. code-block:: console
-
- $ swift list
-
diff --git a/doc/user-guide/source/cli-config-drive.rst b/doc/user-guide/source/cli-config-drive.rst
deleted file mode 100644
index c0b4739d85..0000000000
--- a/doc/user-guide/source/cli-config-drive.rst
+++ /dev/null
@@ -1,315 +0,0 @@
-=======================================
-Store metadata on a configuration drive
-=======================================
-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.
-
-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.
-
-Any modern guest operating system that is capable of mounting an ISO
-9660 or VFAT file system can use the configuration drive.
-
-Requirements and guidelines
-~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-To use the configuration drive, you must follow the following
-requirements for the compute host and image.
-
-**Compute host requirements**
-
-- The following hypervisors support the configuration drive: libvirt,
- XenServer, Hyper-V, and VMware.
-
- Also, the Bare Metal service supports the configuration drive.
-
-- 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.
-
- 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.
-
-- 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.
-
-- 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.
-
-**Image requirements**
-
-- An image built with a recent version of the cloud-init package can
- automatically access metadata passed through the configuration drive.
- The following table lists the references for cloud-init versions mapped
- to a particular operating system:
-
- .. list-table::
- :widths: 50 50
- :header-rows: 1
-
- * - Operating system
- - Reference for cloud-init version
- * - Ubuntu
- - http://packages.ubuntu.com/search?keywords=cloud-init
- * - Fedora (RHEL)
- - https://www.rpmfind.net/linux/rpm2html/search.php?query=cloud-init
- * - openSUSE (SLE)
- - http://software.opensuse.org/download.html?project=Cloud%3ATools&package=cloud-init
-
-- 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.
-
-- If you use Xen with a configuration drive, use the
- ``xenapi_disable_agent`` configuration parameter to disable the
- agent.
-
-**Guidelines**
-
-- 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.
-
-- 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.
-
-Enable and access the configuration drive
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-#. To enable the configuration drive, pass the ``--config-drive true``
- parameter to the :command:`openstack server create` command.
-
- 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:
-
- .. code-block:: console
-
- $ openstack server create --config-drive true --image my-image-name \
- --flavor 1 --key-name mykey --user-data ./my-user-data.txt \
- --file /etc/network/interfaces=/home/myuser/instance-interfaces \
- --file known_hosts=/home/myuser/.ssh/known_hosts \
- --property role=webservers --property essential=false MYINSTANCE
-
- 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:
-
- .. code-block:: console
-
- force_config_drive = true
-
- .. note::
-
- If a user passes the ``--config-drive true`` flag to the :command:`nova
- boot` command, an administrator cannot disable the configuration
- drive.
-
-#. 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:
-
- .. code-block:: console
-
- # mkdir -p /mnt/config
- # mount /dev/disk/by-label/config-2 /mnt/config
-
-.. note::
-
- Ensure that you use at least version 0.3.1 of CirrOS for
- configuration drive support.
-
- If your guest operating system does not use ``udev``, the
- ``/dev/disk/by-label`` directory is not present.
-
- 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``:
-
- .. code-block:: console
-
- # blkid -t LABEL="config-2" -odevice
-
- .. code-block:: console
-
- /dev/vdb
-
- Once identified, you can mount the device:
-
- .. code-block:: console
-
- # mkdir -p /mnt/config
- # mount /dev/vdb /mnt/config
-
-Configuration drive contents
-----------------------------
-
-In this example, the contents of the configuration drive are as follows::
-
- ec2/2009-04-04/meta-data.json
- ec2/2009-04-04/user-data
- ec2/latest/meta-data.json
- ec2/latest/user-data
- openstack/2012-08-10/meta_data.json
- openstack/2012-08-10/user_data
- openstack/content
- openstack/content/0000
- openstack/content/0001
- openstack/latest/meta_data.json
- openstack/latest/user_data
-
-The files that appear on the configuration drive depend on the arguments
-that you pass to the :command:`openstack server create` command.
-
-OpenStack metadata format
--------------------------
-
-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.
-
-.. code-block:: json
-
- {
- "availability_zone": "nova",
- "files": [
- {
- "content_path": "/content/0000",
- "path": "/etc/network/interfaces"
- },
- {
- "content_path": "/content/0001",
- "path": "known_hosts"
- }
- ],
- "hostname": "test.novalocal",
- "launch_index": 0,
- "name": "test",
- "meta": {
- "role": "webservers",
- "essential": "false"
- },
- "public_keys": {
- "mykey": "ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAAAgQDBqUfVvCSez0/Wfpd8dLLgZXV9GtXQ7hnMN+Z0OWQUyebVEHey1CXuin0uY1cAJMhUq8j98SiW+cU0sU4J3x5l2+xi1bodDm1BtFWVeLIOQINpfV1n8fKjHB+ynPpe1F6tMDvrFGUlJs44t30BrujMXBe8Rq44cCk6wqyjATA3rQ== Generated by Nova\n"
- },
- "uuid": "83679162-1378-4288-a2d4-70e13ec132aa"
- }
-
-Note the effect of the
-``--file /etc/network/interfaces=/home/myuser/instance-interfaces``
-argument that was passed to the :command:`openstack server create` 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.
-
-EC2 metadata format
--------------------
-
-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.
-
-.. code-block:: json
-
- {
- "ami-id": "ami-00000001",
- "ami-launch-index": 0,
- "ami-manifest-path": "FIXME",
- "block-device-mapping": {
- "ami": "sda1",
- "ephemeral0": "sda2",
- "root": "/dev/sda1",
- "swap": "sda3"
- },
- "hostname": "test.novalocal",
- "instance-action": "none",
- "instance-id": "i-00000001",
- "instance-type": "m1.tiny",
- "kernel-id": "aki-00000002",
- "local-hostname": "test.novalocal",
- "local-ipv4": null,
- "placement": {
- "availability-zone": "nova"
- },
- "public-hostname": "test.novalocal",
- "public-ipv4": "",
- "public-keys": {
- "0": {
- "openssh-key": "ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAAAgQDBqUfVvCSez0/Wfpd8dLLgZXV9GtXQ7hnMN+Z0OWQUyebVEHey1CXuin0uY1cAJMhUq8j98SiW+cU0sU4J3x5l2+xi1bodDm1BtFWVeLIOQINpfV1n8fKjHB+ynPpe1F6tMDvrFGUlJs44t30BrujMXBe8Rq44cCk6wqyjATA3rQ== Generated by Nova\n"
- }
- },
- "ramdisk-id": "ari-00000003",
- "reservation-id": "r-7lfps8wj",
- "security-groups": [
- "default"
- ]
- }
-
-User data
----------
-
-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:`openstack server create` command.
-
-Configuration drive format
---------------------------
-
-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:
-
-.. code-block:: console
-
- config_drive_format=iso9660
-
-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:
-
-.. code-block:: console
-
- config_drive_cdrom=true
-
-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:
-
-.. code-block:: console
-
- config_drive_format=vfat
-
-If you choose VFAT, the configuration drive is 64 MB.
-
-.. note::
-
- 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.
diff --git a/doc/user-guide/source/cli-create-and-manage-networks.rst b/doc/user-guide/source/cli-create-and-manage-networks.rst
deleted file mode 100644
index 587a71dd5f..0000000000
--- a/doc/user-guide/source/cli-create-and-manage-networks.rst
+++ /dev/null
@@ -1,313 +0,0 @@
-==========================
-Create and manage networks
-==========================
-
-Before you run commands, `set environment variables using the OpenStack RC file
-`_.
-
-Create networks
-~~~~~~~~~~~~~~~
-
-#. List the extensions of the system:
-
- .. code-block:: console
-
- $ openstack extension list -c Alias -c Name --network
- +------------------------------------------+---------------------------+
- | Name | Alias |
- +------------------------------------------+---------------------------+
- | Default Subnetpools | default-subnetpools |
- | Network IP Availability | network-ip-availability |
- | Auto Allocated Topology Services | auto-allocated-topology |
- | Neutron L3 Configurable external gateway | ext-gw-mode |
- | Address scope | address-scope |
- | Neutron Extra Route | extraroute |
- +------------------------------------------+---------------------------+
-
-#. Create a network:
-
- .. code-block:: console
-
- $ openstack network create net1
- Created a new network:
- +---------------------------+--------------------------------------+
- | Field | Value |
- +---------------------------+--------------------------------------+
- | admin_state_up | UP |
- | availability_zone_hints | |
- | availability_zones | |
- | created_at | 2016-12-21T08:32:54Z |
- | description | |
- | headers | |
- | id | 180620e3-9eae-4ba7-9739-c5847966e1f0 |
- | ipv4_address_scope | None |
- | ipv6_address_scope | None |
- | mtu | 1450 |
- | name | net1 |
- | port_security_enabled | True |
- | project_id | c961a8f6d3654657885226378ade8220 |
- | provider:network_type | vxlan |
- | provider:physical_network | None |
- | provider:segmentation_id | 14 |
- | revision_number | 3 |
- | router:external | Internal |
- | shared | False |
- | status | ACTIVE |
- | subnets | |
- | tags | [] |
- | updated_at | 2016-12-21T08:32:54Z |
- +---------------------------+--------------------------------------+
-
- .. note::
-
- Some fields of the created network are invisible to non-admin users.
-
-#. Create a network with specified provider network type.
-
- .. code-block:: console
-
- $ openstack network create net2 --provider-network-type vxlan
- Created a new network:
- +---------------------------+--------------------------------------+
- | Field | Value |
- +---------------------------+--------------------------------------+
- | admin_state_up | UP |
- | availability_zone_hints | |
- | availability_zones | |
- | created_at | 2016-12-21T08:33:34Z |
- | description | |
- | headers | |
- | id | c0a563d5-ef7d-46b3-b30d-6b9d4138b6cf |
- | ipv4_address_scope | None |
- | ipv6_address_scope | None |
- | mtu | 1450 |
- | name | net2 |
- | port_security_enabled | True |
- | project_id | c961a8f6d3654657885226378ade8220 |
- | provider:network_type | vxlan |
- | provider:physical_network | None |
- | provider:segmentation_id | 87 |
- | revision_number | 3 |
- | router:external | Internal |
- | shared | False |
- | status | ACTIVE |
- | subnets | |
- | tags | [] |
- | updated_at | 2016-12-21T08:33:34Z |
- +---------------------------+--------------------------------------+
-
-Create subnets
-~~~~~~~~~~~~~~
-
-Create a subnet:
-
-.. code-block:: console
-
- $ openstack subnet create subnet1 --network net1
- --subnet-range 192.0.2.0/24
- +-------------------+--------------------------------------+
- | Field | Value |
- +-------------------+--------------------------------------+
- | allocation_pools | 192.0.2.2-192.0.2.254 |
- | cidr | 192.0.2.0/24 |
- | created_at | 2016-12-22T18:47:52Z |
- | description | |
- | dns_nameservers | |
- | enable_dhcp | True |
- | gateway_ip | 192.0.2.1 |
- | headers | |
- | host_routes | |
- | id | a394689c-f547-4834-9778-3e0bb22130dc |
- | ip_version | 4 |
- | ipv6_address_mode | None |
- | ipv6_ra_mode | None |
- | name | subnet1 |
- | network_id | 180620e3-9eae-4ba7-9739-c5847966e1f0 |
- | project_id | c961a8f6d3654657885226378ade8220 |
- | revision_number | 2 |
- | service_types | |
- | subnetpool_id | None |
- | updated_at | 2016-12-22T18:47:52Z |
- +-------------------+--------------------------------------+
-
-
-The ``subnet-create`` command has the following positional and optional
-parameters:
-
-- The name or ID of the network to which the subnet belongs.
-
- In this example, ``net1`` is a positional argument that specifies the
- network name.
-
-- The CIDR of the subnet.
-
- In this example, ``192.0.2.0/24`` is a positional argument that
- specifies the CIDR.
-
-- The subnet name, which is optional.
-
- In this example, ``--name subnet1`` specifies the name of the
- subnet.
-
-For information and examples on more advanced use of neutron's
-``subnet`` subcommand, see the `OpenStack Administrator
-Guide `__.
-
-Create routers
-~~~~~~~~~~~~~~
-
-#. Create a router:
-
- .. code-block:: console
-
- $ openstack router create router1
- +-------------------------+--------------------------------------+
- | Field | Value |
- +-------------------------+--------------------------------------+
- | admin_state_up | UP |
- | availability_zone_hints | |
- | availability_zones | |
- | created_at | 2016-12-22T18:48:57Z |
- | description | |
- | distributed | True |
- | external_gateway_info | null |
- | flavor_id | None |
- | ha | False |
- | headers | |
- | id | e25a24ee-3458-45c7-b16e-edf49092aab7 |
- | name | router1 |
- | project_id | e17431afc0524e0690484889a04b7fa0 |
- | revision_number | 1 |
- | routes | |
- | status | ACTIVE |
- | updated_at | 2016-12-22T18:48:57Z |
- +-------------------------+--------------------------------------+
-
-
- Take note of the unique router identifier returned, this will be
- required in subsequent steps.
-
-#. Link the router to the external provider network:
-
- .. code-block:: console
-
- $ openstack router set ROUTER --external-gateway NETWORK
-
- Replace ROUTER with the unique identifier of the router, replace NETWORK
- with the unique identifier of the external provider network.
-
-#. Link the router to the subnet:
-
- .. code-block:: console
-
- $ openstack router add subnet ROUTER SUBNET
-
- Replace ROUTER with the unique identifier of the router, replace SUBNET
- with the unique identifier of the subnet.
-
-Create ports
-~~~~~~~~~~~~
-
-#. Create a port with specified IP address:
-
- .. code-block:: console
-
- $ openstack port create --network net1 --fixed-ip subnet=subnet1,ip-address=192.0.2.40 port1
- +-----------------------+-----------------------------------------+
- | Field | Value |
- +-----------------------+-----------------------------------------+
- | admin_state_up | UP |
- | allowed_address_pairs | |
- | binding_host_id | |
- | binding_profile | |
- | binding_vif_details | |
- | binding_vif_type | unbound |
- | binding_vnic_type | normal |
- | created_at | 2016-12-22T18:54:43Z |
- | description | |
- | device_id | |
- | device_owner | |
- | extra_dhcp_opts | |
- | fixed_ips | ip_address='192.0.2.40', subnet_id='a |
- | | 394689c-f547-4834-9778-3e0bb22130dc' |
- | headers | |
- | id | 031ddba8-3e3f-4c3c-ae26-7776905eb24f |
- | mac_address | fa:16:3e:df:3d:c7 |
- | name | port1 |
- | network_id | 180620e3-9eae-4ba7-9739-c5847966e1f0 |
- | port_security_enabled | True |
- | project_id | c961a8f6d3654657885226378ade8220 |
- | revision_number | 5 |
- | security_groups | 84abb9eb-dc59-40c1-802c-4e173c345b6a |
- | status | DOWN |
- | updated_at | 2016-12-22T18:54:44Z |
- +-----------------------+-----------------------------------------+
-
- In the previous command, ``net1`` is the network name, which is a
- positional argument. ``--fixed-ip subnet,ip-address=192.0.2.40`` is
- an option which specifies the port's fixed IP address we wanted.
-
- .. note::
-
- 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).
-
-#. Create a port without specified IP address:
-
- .. code-block:: console
-
- $ openstack port create port2 --network net1
- +-----------------------+-----------------------------------------+
- | Field | Value |
- +-----------------------+-----------------------------------------+
- | admin_state_up | UP |
- | allowed_address_pairs | |
- | binding_host_id | |
- | binding_profile | |
- | binding_vif_details | |
- | binding_vif_type | unbound |
- | binding_vnic_type | normal |
- | created_at | 2016-12-22T18:56:06Z |
- | description | |
- | device_id | |
- | device_owner | |
- | extra_dhcp_opts | |
- | fixed_ips | ip_address='192.0.2.10', subnet_id='a |
- | | 394689c-f547-4834-9778-3e0bb22130dc' |
- | headers | |
- | id | eac47fcd-07ac-42dd-9993-5b36ac1f201b |
- | mac_address | fa:16:3e:96:ae:6e |
- | name | port2 |
- | network_id | 180620e3-9eae-4ba7-9739-c5847966e1f0 |
- | port_security_enabled | True |
- | project_id | c961a8f6d3654657885226378ade8220 |
- | revision_number | 5 |
- | security_groups | 84abb9eb-dc59-40c1-802c-4e173c345b6a |
- | status | DOWN |
- | updated_at | 2016-12-22T18:56:06Z |
- +-----------------------+-----------------------------------------+
-
- .. note::
-
- Note that the system allocates one IP address if you do not specify
- an IP address in the :command:`openstack port create` command.
-
- .. note::
-
- You can specify a MAC address with ``--mac-address MAC_ADDRESS``.
- If you specify an invalid MAC address, including ``00:00:00:00:00:00``
- or ``ff:ff:ff:ff:ff:ff``, you will get an error.
-
-#. Query ports with specified fixed IP addresses:
-
- .. code-block:: console
-
- $ neutron port-list --fixed-ips ip_address=192.0.2.2 \
- ip_address=192.0.2.40
- +----------------+------+-------------------+-------------------------------------------------+
- | id | name | mac_address | fixed_ips |
- +----------------+------+-------------------+-------------------------------------------------+
- | baf13412-26... | | fa:16:3e:f6:ec:c7 | {"subnet_id"... ..."ip_address": "192.0.2.2"} |
- | f7a08fe4-e7... | | fa:16:3e:97:e0:fc | {"subnet_id"... ..."ip_address": "192.0.2.40"} |
- +----------------+------+-------------------+-------------------------------------------------+
diff --git a/doc/user-guide/source/cli-create-and-manage-stacks.rst b/doc/user-guide/source/cli-create-and-manage-stacks.rst
deleted file mode 100644
index fd9505f19e..0000000000
--- a/doc/user-guide/source/cli-create-and-manage-stacks.rst
+++ /dev/null
@@ -1,157 +0,0 @@
-========================
-Create and manage stacks
-========================
-
-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.
-
-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.
-
-The template languages are described in the `Template
-Guide `__
-in the `Heat developer
-documentation `__.
-
-Create a stack from an example template file
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-- To create a stack, or template, from an `example template
- file `__, run
- the following command:
-
- .. code-block:: console
-
- $ openstack stack create --template server_console.yaml \
- --parameter "image=cirros" MYSTACK
-
- The ``--parameter`` values that you specify depend on the parameters
- that are defined in the template. If a website hosts the template
- file, you can also specify the URL with the ``--template`` parameter.
-
- The command returns the following output:
-
- .. code-block:: console
-
- +---------------------+----------------------------------------------------------------+
- | Field | Value |
- +---------------------+----------------------------------------------------------------+
- | id | 70b9feca-8f99-418e-b2f1-cc38d61b3ffb |
- | stack_name | MYSTACK |
- | description | The heat template is used to demo the 'console_urls' attribute |
- | | of OS::Nova::Server. |
- | | |
- | creation_time | 2016-06-08T09:54:15 |
- | updated_time | None |
- | stack_status | CREATE_IN_PROGRESS |
- | stack_status_reason | |
- +---------------------+----------------------------------------------------------------+
-
-- You can also use the ``--dry-run`` option with the
- :command:`openstack stack create` command to validate a
- template file without creating a stack from it.
-
- If validation fails, the response returns an error message.
-
-Get information about stacks
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-To explore the state and history of a particular stack, you can run a
-number of commands.
-
-- To see which stacks are visible to the current user, run the
- following command:
-
- .. code-block:: console
-
- $ openstack stack list
- +--------------------------------------+------------+-----------------+---------------------+--------------+
- | ID | Stack Name | Stack Status | Creation Time | Updated Time |
- +--------------------------------------+------------+-----------------+---------------------+--------------+
- | 70b9feca-8f99-418e-b2f1-cc38d61b3ffb | MYSTACK | CREATE_COMPLETE | 2016-06-08T09:54:15 | None |
- +--------------------------------------+------------+-----------------+---------------------+--------------+
-
-- To show the details of a stack, run the following command:
-
- .. code-block:: console
-
- $ openstack stack show MYSTACK
-
-- A stack consists of a collection of resources. To list the resources
- and their status, run the following command:
-
- .. code-block:: console
-
- $ openstack stack resource list MYSTACK
- +---------------+--------------------------------------+------------------+-----------------+---------------------+
- | resource_name | physical_resource_id | resource_type | resource_status | updated_time |
- +---------------+--------------------------------------+------------------+-----------------+---------------------+
- | server | 1b3a7c13-42be-4999-a2a1-8fbefd00062b | OS::Nova::Server | CREATE_COMPLETE | 2016-06-08T09:54:15 |
- +---------------+--------------------------------------+------------------+-----------------+---------------------+
-
-- To show the details for a specific resource in a stack, run the
- following command:
-
- .. code-block:: console
-
- $ openstack stack resource show MYSTACK server
-
-- Some resources have associated metadata which can change throughout
- the lifecycle of a resource. Show the metadata by running the
- following command:
-
- .. code-block:: console
-
- $ openstack stack resource metadata MYSTACK server
-
-- A series of events is generated during the lifecycle of a stack. To
- display lifecycle events, run the following command:
-
- .. code-block:: console
-
- $ openstack stack event list MYSTACK
- 2016-06-08 09:54:15 [MYSTACK]: CREATE_IN_PROGRESS Stack CREATE started
- 2016-06-08 09:54:15 [server]: CREATE_IN_PROGRESS state changed
- 2016-06-08 09:54:41 [server]: CREATE_COMPLETE state changed
- 2016-06-08 09:54:41 [MYSTACK]: CREATE_COMPLETE Stack CREATE completed successfully
-
-- To show the details for a particular event, run the following
- command:
-
- .. code-block:: console
-
- $ openstack stack event show MYSTACK server EVENT
-
-Update a stack
-~~~~~~~~~~~~~~
-
-To update an existing stack from a modified template file, run a command
-like the following command:
-
-.. code-block:: console
-
- $ openstack stack update --template server_console.yaml \
- --parameter "image=ubuntu" MYSTACK
- +---------------------+----------------------------------------------------------------+
- | Field | Value |
- +---------------------+----------------------------------------------------------------+
- | id | 267a459a-a8cd-4d3e-b5a1-8c08e945764f |
- | stack_name | mystack |
- | description | The heat template is used to demo the 'console_urls' attribute |
- | | of OS::Nova::Server. |
- | | |
- | creation_time | 2016-06-08T09:54:15 |
- | updated_time | 2016-06-08T10:41:18 |
- | stack_status | UPDATE_IN_PROGRESS |
- | stack_status_reason | Stack UPDATE started |
- +---------------------+----------------------------------------------------------------+
-
-Some resources are updated in-place, while others are replaced with new
-resources.
diff --git a/doc/user-guide/source/cli-delete-an-instance.rst b/doc/user-guide/source/cli-delete-an-instance.rst
deleted file mode 100644
index d67a4d7853..0000000000
--- a/doc/user-guide/source/cli-delete-an-instance.rst
+++ /dev/null
@@ -1,43 +0,0 @@
-==================
-Delete an instance
-==================
-
-When you no longer need an instance, you can delete it.
-
-#. List all instances:
-
- .. code-block:: console
-
- $ openstack server list
- +-------------+----------------------+--------+------------+-------------+------------------+------------+
- | ID | Name | Status | Task State | Power State | Networks | Image Name |
- +-------------+----------------------+--------+------------+-------------+------------------+------------+
- | 84c6e57d... | myCirrosServer | ACTIVE | None | Running | private=10.0.0.3 | cirros |
- | 8a99547e... | myInstanceFromVolume | ACTIVE | None | Running | private=10.0.0.4 | ubuntu |
- | d7efd3e4... | newServer | ERROR | None | NOSTATE | | centos |
- +-------------+----------------------+--------+------------+-------------+------------------+------------+
-
-#. Run the :command:`openstack server delete` command to delete the instance.
- The following example shows deletion of the ``newServer`` instance, which
- is in ``ERROR`` state:
-
- .. code-block:: console
-
- $ openstack server delete newServer
-
- The command does not notify that your server was deleted.
-
-#. To verify that the server was deleted, run the
- :command:`openstack server list` command:
-
- .. code-block:: console
-
- $ openstack server list
- +-------------+----------------------+--------+------------+-------------+------------------+------------+
- | ID | Name | Status | Task State | Power State | Networks | Image Name |
- +-------------+----------------------+--------+------------+-------------+------------------+------------+
- | 84c6e57d... | myCirrosServer | ACTIVE | None | Running | private=10.0.0.3 | cirros |
- | 8a99547e... | myInstanceFromVolume | ACTIVE | None | Running | private=10.0.0.4 | ubuntu |
- +-------------+----------------------+--------+------------+-------------+------------------+------------+
-
- The deleted instance does not appear in the list.
diff --git a/doc/user-guide/source/cli-launch-instances.rst b/doc/user-guide/source/cli-launch-instances.rst
deleted file mode 100644
index 210c2eed22..0000000000
--- a/doc/user-guide/source/cli-launch-instances.rst
+++ /dev/null
@@ -1,168 +0,0 @@
-================
-Launch instances
-================
-
-Instances are virtual machines that run inside the cloud.
-
-Before you can launch an instance, gather the following parameters:
-
-- The **instance source** can be an image, snapshot, or block storage
- volume that contains an image or snapshot.
-
-- A **name** for your instance.
-
-- 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.
-
-- 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.
-
-- Access and security credentials, which include one or both of the
- following credentials:
-
- - 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.
-
- - 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*.
-
-- If needed, you can assign a **floating (public) IP address** to a
- running instance.
-
-- You can also attach a block storage device, or **volume**, for
- persistent storage.
-
-.. note::
-
- 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.
-
- 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`.
-
-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.
-
-Gather parameters to launch an instance
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-Before you begin, source the OpenStack RC file.
-
-#. Create a flavor.
-
- .. code-block:: console
-
- $ openstack flavor create --ram 512 --disk 1 --vcpus 1 m1.tiny
-
-#. List the available flavors.
-
- .. code-block:: console
-
- $ openstack flavor list
-
- Note the ID of the flavor that you want to use for your instance::
-
- +-----+-----------+-------+------+-----------+-------+-----------+
- | ID | Name | RAM | Disk | Ephemeral | VCPUs | Is_Public |
- +-----+-----------+-------+------+-----------+-------+-----------+
- | 1 | m1.tiny | 512 | 1 | 0 | 1 | True |
- | 2 | m1.small | 2048 | 20 | 0 | 1 | True |
- | 3 | m1.medium | 4096 | 40 | 0 | 2 | True |
- | 4 | m1.large | 8192 | 80 | 0 | 4 | True |
- | 5 | m1.xlarge | 16384 | 160 | 0 | 8 | True |
- +-----+-----------+-------+------+-----------+-------+-----------+
-
-#. List the available images.
-
- .. code-block:: console
-
- $ openstack image list
-
- Note the ID of the image from which you want to boot your instance::
-
- +--------------------------------------+---------------------------------+--------+
- | ID | Name | Status |
- +--------------------------------------+---------------------------------+--------+
- | 397e713c-b95b-4186-ad46-6126863ea0a9 | cirros-0.3.5-x86_64-uec | active |
- | df430cc2-3406-4061-b635-a51c16e488ac | cirros-0.3.5-x86_64-uec-kernel | active |
- | 3cf852bd-2332-48f4-9ae4-7d926d50945e | cirros-0.3.5-x86_64-uec-ramdisk | active |
- +--------------------------------------+---------------------------------+--------+
-
- You can also filter the image list by using :command:`grep` to find a specific
- image, as follows:
-
- .. code-block:: console
-
- $ openstack image list | grep 'kernel'
-
- | df430cc2-3406-4061-b635-a51c16e488ac | cirros-0.3.5-x86_64-uec-kernel | active |
-
-#. List the available security groups.
-
- .. code-block:: console
-
- $ openstack security group list
-
- .. note::
-
- If you are an admin user, this command will list groups for all tenants.
-
- Note the ID of the security group that you want to use for your instance::
-
- +--------------------------------------+---------+------------------------+----------------------------------+
- | ID | Name | Description | Project |
- +--------------------------------------+---------+------------------------+----------------------------------+
- | b0d78827-0981-45ef-8561-93aee39bbd9f | default | Default security group | 5669caad86a04256994cdf755df4d3c1 |
- | ec02e79e-83e1-48a5-86ad-14ab9a8c375f | default | Default security group | 1eaaf6ede7a24e78859591444abf314a |
- +--------------------------------------+---------+------------------------+----------------------------------+
-
- If you have not created any security groups, you can assign the instance
- to only the default security group.
-
- You can view rules for a specified security group:
-
- .. code-block:: console
-
- $ openstack security group rule list default
-
-#. List the available key pairs, and note the key pair name that you use for
- SSH access.
-
- .. code-block:: console
-
- $ openstack keypair list
-
-Launch an instance
-~~~~~~~~~~~~~~~~~~
-
-You can launch an instance from various sources.
-
-.. toctree::
- :maxdepth: 2
-
- cli-nova-launch-instance-from-image.rst
- cli-nova-launch-instance-from-volume.rst
- cli-nova-launch-instance-using-ISO-image.rst
-
diff --git a/doc/user-guide/source/cli-manage-bare-metal-nodes.rst b/doc/user-guide/source/cli-manage-bare-metal-nodes.rst
deleted file mode 100644
index eee09b3418..0000000000
--- a/doc/user-guide/source/cli-manage-bare-metal-nodes.rst
+++ /dev/null
@@ -1,176 +0,0 @@
-=======================
-Manage bare-metal nodes
-=======================
-
-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 project
-clouds such as a high-performance computing cluster, or for deploying
-OpenStack itself.
-
-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.
-
-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.
-
-Commands
-~~~~~~~~
-
-The following commands can be used to manage bare-metal nodes.
-
-``baremetal-interface-add``
- Adds a network interface to a bare-metal node.
-
-``baremetal-interface-list``
- Lists network interfaces associated with a bare-metal node.
-
-``baremetal-interface-remove``
- Removes a network interface from a bare-metal node.
-
-``baremetal-node-create``
- Creates a bare-metal node.
-
-``baremetal-node-delete``
- Removes a bare-metal node and any associated interfaces.
-
-``baremetal-node-list``
- Lists available bare-metal nodes.
-
-``baremetal-node-show``
- Shows information about a bare-metal node.
-
-Create a bare-metal node
-~~~~~~~~~~~~~~~~~~~~~~~~
-
-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.
-
-.. code-block:: console
-
- $ nova baremetal-node-create --pm_address PM_ADDRESS --pm_user PM_USERNAME \
- --pm_password PM_PASSWORD $(hostname -f) 1 512 10 aa:bb:cc:dd:ee:ff
-
-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``.
-
-.. code-block:: console
-
- $ nova baremetal-node-create --pm_address 1.2.3.4 --pm_user ipmi \
- --pm_password ipmi $(hostname -f) 1 512 10 aa:bb:cc:dd:ee:ff
- +------------------+-------------------+
- | Property | Value |
- +------------------+-------------------+
- | instance_uuid | None |
- | pm_address | 1.2.3.4 |
- | interfaces | [] |
- | prov_vlan_id | None |
- | cpus | 1 |
- | memory_mb | 512 |
- | prov_mac_address | aa:bb:cc:dd:ee:ff |
- | service_host | ubuntu |
- | local_gb | 10 |
- | id | 1 |
- | pm_user | ipmi |
- | terminal_port | None |
- +------------------+-------------------+
-
-Add a network interface to the node
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-For each NIC on the node, you must create an interface, specifying the
-interface's MAC address.
-
-.. code-block:: console
-
- $ nova baremetal-interface-add 1 aa:bb:cc:dd:ee:ff
- +-------------+-------------------+
- | Property | Value |
- +-------------+-------------------+
- | datapath_id | 0 |
- | id | 1 |
- | port_no | 0 |
- | address | aa:bb:cc:dd:ee:ff |
- +-------------+-------------------+
-
-Launch an instance from a bare-metal image
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-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.
-
-.. code-block:: console
-
- $ openstack server create --image my-baremetal-image --flavor \
- my-baremetal-flavor test
- +-----------------------------+--------------------------------------+
- | Property | Value |
- +-----------------------------+--------------------------------------+
- | status | BUILD |
- | id | cc302a8f-cd81-484b-89a8-b75eb3911b1b |
- +-----------------------------+--------------------------------------+
-
- ... wait for instance to become active ...
-
-.. note::
-
- 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:
-
- .. code-block:: console
-
- $ openstack server create --availability-zone zone:HOST,NODE
-
- ``host`` is optional for the ``--availability-zone`` parameter. You
- can simply specify ``zone:,node``, still including the comma.
-
-List bare-metal nodes and interfaces
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-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:
-
-.. code-block:: console
-
- $ nova baremetal-node-list
- +----+--------+------+-----------+---------+-------------------+------+------------+-------------+-------------+---------------+
- | ID | Host | CPUs | Memory_MB | Disk_GB | MAC Address | VLAN | PM Address | PM Username | PM Password | Terminal Port |
- +----+--------+------+-----------+---------+-------------------+------+------------+-------------+-------------+---------------+
- | 1 | ubuntu | 1 | 512 | 10 | aa:bb:cc:dd:ee:ff | None | 1.2.3.4 | ipmi | | None |
- +----+--------+------+-----------+---------+-------------------+------+------------+-------------+-------------+---------------+
-
-Show details for a bare-metal node
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-Use the :command:`nova baremetal-node-show` command to view the details for a
-bare-metal node:
-
-.. code-block:: console
-
- $ nova baremetal-node-show 1
- +------------------+--------------------------------------+
- | Property | Value |
- +------------------+--------------------------------------+
- | instance_uuid | cc302a8f-cd81-484b-89a8-b75eb3911b1b |
- | pm_address | 1.2.3.4 |
- | interfaces | [{u'datapath_id': u'0', u'id': 1, |
- | | u'port_no': 0, |
- | | u'address': u'aa:bb:cc:dd:ee:ff'}] |
- | prov_vlan_id | None |
- | cpus | 1 |
- | memory_mb | 512 |
- | prov_mac_address | aa:bb:cc:dd:ee:ff |
- | service_host | ubuntu |
- | local_gb | 10 |
- | id | 1 |
- | pm_user | ipmi |
- | terminal_port | None |
- +------------------+--------------------------------------+
diff --git a/doc/user-guide/source/cli-manage-images-curl.rst b/doc/user-guide/source/cli-manage-images-curl.rst
deleted file mode 100644
index 95425b43f4..0000000000
--- a/doc/user-guide/source/cli-manage-images-curl.rst
+++ /dev/null
@@ -1,120 +0,0 @@
-========================
-Manage images using cURL
-========================
-
-This section is intended to provide a series of commands a typical
-client of the API might use to create and modify an image.
-
-These commands assume the implementation of the v2 Image 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.
-
-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``.
-
-Create an image
-~~~~~~~~~~~~~~~
-
-.. code-block:: console
-
- $ curl -i -X POST -H "X-Auth-Token: $OS_AUTH_TOKEN" \
- -H "Content-Type: application/json" \
- -d '{"name": "Ubuntu 14.04", \
- "tags": ["ubuntu", "14.04", "trusty"]}' \
- $OS_IMAGE_URL/v2/images
-
- HTTP/1.1 201 Created
- Content-Length: 451
- Content-Type: application/json; charset=UTF-8
- Location: http://example.com:9292/v2/images
- /7b97f37c-899d-44e8-aaa0-543edbc4eaad
- Date: Fri, 11 Mar 2016 12:25:32 GMT
-
- {
- "id": "7b97f37c-899d-44e8-aaa0-543edbc4eaad",
- "name": "Ubuntu 14.04",
- "status": "queued",
- "visibility": "private",
- "protected": false,
- "tags": ["ubuntu", "14.04", "trusty"],
- "created_at": "2016-03-11T12:25:32Z",
- "updated_at": "2016-03-11T12:25:32Z",
- "file": "/v2/images/7b97f37c-899d-44e8-aaa0-543edbc4eaad/file",
- "self": "/v2/images/7b97f37c-899d-44e8-aaa0-543edbc4eaad",
- "schema": "/v2/schemas/image"
- }
-
-Update the image
-~~~~~~~~~~~~~~~~
-
-.. code-block:: console
-
- $ curl -i -X PATCH -H "X-Auth-Token: $OS_AUTH_TOKEN" \
- -H "Content-Type: application/json" \
- -d '[{"op": "add", "path": "/login-user", "value": "root"}]' \
- $OS_IMAGE_URL/v2/images/7b97f37c-899d-44e8-aaa0-543edbc4eaad
-
- HTTP/1.1 200 OK
- Content-Length: 477
- Content-Type: application/json; charset=UTF-8
- Date: Fri, 11 Mar 2016 12:44:56 GMT
-
- {
- "id": "7b97f37c-899d-44e8-aaa0-543edbc4eaad",
- "name": "Ubuntu 14.04",
- "status": "queued",
- "visibility": "private",
- "protected": false,
- "tags": ["ubuntu", "14.04", "trusty"],
- "login_user": "root",
- "created_at": "2016-03-11T12:25:32Z",
- "updated_at": "2016-03-11T12:44:56Z",
- "file": "/v2/images/7b97f37c-899d-44e8-aaa0-543edbc4eaad/file",
- "self": "/v2/images/7b97f37c-899d-44e8-aaa0-543edbc4eaad",
- "schema": "/v2/schemas/image"
- }
-
-Upload binary image data
-~~~~~~~~~~~~~~~~~~~~~~~~
-
-.. code-block:: console
-
- $ curl -i -X PUT -H "X-Auth-Token: $OS_AUTH_TOKEN" \
- -H "Content-Type: application/octet-stream" \
- --data-binary @/home/glance/ubuntu-14.04.qcow2 \
- $OS_IMAGE_URL/v2/images/7b97f37c-899d-44e8-aaa0-543edbc4eaad/file
-
- HTTP/1.1 100 Continue
- HTTP/1.1 201 Created
- Content-Length: 0
- Date: Fri, 11 Mar 2016 12:51:02 GMT
-
-Download binary image data
-~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-.. code-block:: console
-
- $ curl -i -X GET -H "X-Auth-Token: $OS_AUTH_TOKEN" \
- $OS_IMAGE_URL/v2/images/7b97f37c-899d-44e8-aaa0-543edbc4eaad/file
-
- HTTP/1.1 200 OK
- Content-Type: application/octet-stream
- Content-Md5: 912ec803b2ce49e4a541068d495ab570
- Transfer-Encoding: chunked
- Date: Fri, 11 Mar 2016 12:57:41 GMT
-
-Delete an image
-~~~~~~~~~~~~~~~
-
-.. code-block:: console
-
- $ curl -i -X DELETE -H "X-Auth-Token: $OS_AUTH_TOKEN" \
- $OS_IMAGE_URL/v2/images/7b97f37c-899d-44e8-aaa0-543edbc4eaad
-
- HTTP/1.1 204 No Content
- Content-Length: 0
- Date: Fri, 11 Mar 2016 12:59:11 GMT
diff --git a/doc/user-guide/source/cli-manage-instances-hosts.rst b/doc/user-guide/source/cli-manage-instances-hosts.rst
deleted file mode 100644
index 4ad38a51ec..0000000000
--- a/doc/user-guide/source/cli-manage-instances-hosts.rst
+++ /dev/null
@@ -1,25 +0,0 @@
-==========================
-Manage instances and hosts
-==========================
-
-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.
-
-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.
-
-.. toctree::
- :maxdepth: 2
-
- cli-manage-ip-addresses.rst
- cli-change-the-size-of-your-server.rst
- cli-stop-and-start-an-instance.rst
- cli-search-instance-with-ip-address.rst
- cli-reboot-an-instance.rst
- cli-delete-an-instance.rst
- cli-access-instance-through-a-console.rst
- cli-manage-bare-metal-nodes.rst
-
diff --git a/doc/user-guide/source/cli-manage-ip-addresses.rst b/doc/user-guide/source/cli-manage-ip-addresses.rst
deleted file mode 100644
index 106e5ba648..0000000000
--- a/doc/user-guide/source/cli-manage-ip-addresses.rst
+++ /dev/null
@@ -1,249 +0,0 @@
-===================
-Manage IP addresses
-===================
-
-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.
-
-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.
-
-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:
-
-- 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.
-
-- Disassociate a floating IP address from an instance in the project.
-
-- Delete a floating IP from the project which automatically deletes that IP's
- associations.
-
-Use the :command:`openstack` commands to manage floating IP addresses.
-
-Create an external network
-~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-#. Create an external network named ``public``:
-
-.. code-block:: console
-
- $ openstack network create public --external
-
- +---------------------------+--------------------------------------+
- | Field | Value |
- +---------------------------+--------------------------------------+
- | admin_state_up | UP |
- | availability_zone_hints | |
- | availability_zones | |
- | created_at | 2017-05-18T05:06:06Z |
- | description | |
- | dns_domain | None |
- | id | 5a6c74b9-5659-4b9e-951e-85ffca212139 |
- | ipv4_address_scope | None |
- | ipv6_address_scope | None |
- | is_default | False |
- | mtu | 1450 |
- | name | public |
- | port_security_enabled | False |
- | project_id | b3abf186ac64462e85741315376e9ca7 |
- | provider:network_type | vxlan |
- | provider:physical_network | None |
- | provider:segmentation_id | 9 |
- | qos_policy_id | None |
- | revision_number | 3 |
- | router:external | External |
- | segments | None |
- | shared | False |
- | status | ACTIVE |
- | subnets | |
- | updated_at | 2017-05-18T05:06:06Z |
- +---------------------------+--------------------------------------+
-
-#. Create a subnet of the ``public`` external network:
-
-.. code-block:: console
-
- $ openstack subnet create --network public --subnet-range 172.24.4.0/24 public_subnet
-
- +-------------------------+--------------------------------------+
- | Field | Value |
- +-------------------------+--------------------------------------+
- | allocation_pools | 172.24.4.2-172.24.4.254 |
- | cidr | 172.24.4.0/24 |
- | created_at | 2017-05-18T05:16:46Z |
- | description | |
- | dns_nameservers | |
- | enable_dhcp | True |
- | gateway_ip | 172.24.4.1 |
- | host_routes | |
- | id | f61a73b3-6097-48ff-b7ef-98da203e6b18 |
- | ip_version | 4 |
- | ipv6_address_mode | None |
- | ipv6_ra_mode | None |
- | name | public_subnet |
- | network_id | 5a6c74b9-5659-4b9e-951e-85ffca212139 |
- | project_id | b3abf186ac64462e85741315376e9ca7 |
- | revision_number | 2 |
- | segment_id | None |
- | service_types | |
- | subnetpool_id | None |
- | updated_at | 2017-05-18T05:16:46Z |
- | use_default_subnet_pool | None |
- +-------------------------+--------------------------------------+
-
-List floating IP address information
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-To list all pools that provide floating IP addresses, run:
-
-.. code-block:: console
-
- $ openstack floating ip pool list
- +--------+
- | name |
- +--------+
- | public |
- | test |
- +--------+
-
-.. note::
-
- If this list is empty, the cloud administrator must configure a pool
- of floating IP addresses.
- This command is only available in ``nova-network``. If you use the OpenStack
- Networking service, run the following command to list external networks:
-
- .. code-block:: console
-
- $ openstack network list --external
-
- +--------------------------------------+-------------+--------------------------------------+
- | ID | Name | Subnets |
- +--------------------------------------+-------------+--------------------------------------+
- | 5a6c74b9-5659-4b9e-951e-85ffca212139 | public | f61a73b3-6097-48ff-b7ef-98da203e6b18 |
- | 9839a22d-33b7-4173-9708-985f091bb892 | public1 | 19f1fbb4-f411-4465-8ed9-b641c7fc73d0 |
- +--------------------------------------+-------------+--------------------------------------+
-
-
-To list all floating IP addresses that are allocated to the current project,
-run:
-
-.. code-block:: console
-
- $ openstack floating ip list
- +--------------------------------------+---------------------+------------------+------+
- | ID | Floating IP Address | Fixed IP Address | Port |
- +--------------------------------------+---------------------+------------------+------+
- | 760963b2-779c-4a49-a50d-f073c1ca5b9e | 172.24.4.228 | None | None |
- | 89532684-13e1-4af3-bd79-f434c9920cc3 | 172.24.4.235 | None | None |
- | ea3ebc6d-a146-47cd-aaa8-35f06e1e8c3d | 172.24.4.229 | None | None |
- +--------------------------------------+---------------------+------------------+------+
-
-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.
-
-Associate floating IP addresses
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-You can assign a floating IP address to a project and to an instance.
-
-#. 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:
-
- .. code-block:: console
-
- $ openstack floating ip create public
- +---------------------+--------------------------------------+
- | Field | Value |
- +---------------------+--------------------------------------+
- | created_at | 2017-03-30T12:35:25Z |
- | description | |
- | fixed_ip_address | None |
- | floating_ip_address | 172.24.4.230 |
- | floating_network_id | c213f520-aade-42eb-8bf1-6826505d74bb |
- | id | 1e777f9e-4fc8-4df8-be6f-89f5caba3c0f |
- | name | None |
- | port_id | None |
- | project_id | b3abf186ac64462e85741315376e9ca7 |
- | revision_number | 1 |
- | router_id | None |
- | status | DOWN |
- | updated_at | 2017-03-30T12:35:25Z |
- +---------------------+--------------------------------------+
-
-#. List all project instances with which a floating IP address could be
- associated.
-
- .. code-block:: console
-
- $ openstack server list
- +---------------------+------+---------+------------+-------------+------------------+------------+
- | ID | Name | Status | Task State | Power State | Networks | Image Name |
- +---------------------+------+---------+------------+-------------+------------------+------------+
- | d5c854f9-d3e5-4f... | VM1 | ACTIVE | - | Running | private=10.0.0.3 | cirros |
- | 42290b01-0968-43... | VM2 | SHUTOFF | - | Shutdown | private=10.0.0.4 | centos |
- +---------------------+------+---------+------------+-------------+------------------+------------+
-
-#. Associate an IP address with an instance in the project, as follows:
-
- .. code-block:: console
-
- $ openstack server add floating ip INSTANCE_NAME_OR_ID FLOATING_IP_ADDRESS
-
- For example:
-
- .. code-block:: console
-
- $ openstack server add floating ip VM1 172.24.4.225
-
- The instance is now associated with two IP addresses:
-
- .. code-block:: console
-
- $ openstack server list
- +------------------+------+--------+------------+-------------+-------------------------------+------------+
- | ID | Name | Status | Task State | Power State | Networks | Image Name |
- +------------------+------+--------+------------+-------------+-------------------------------+------------+
- | d5c854f9-d3e5... | VM1 | ACTIVE | - | Running | private=10.0.0.3, 172.24.4.225| cirros |
- | 42290b01-0968... | VM2 | SHUTOFF| - | Shutdown | private=10.0.0.4 | centos |
- +------------------+------+--------+------------+-------------+-------------------------------+------------+
-
- After you associate the IP address and configure security group rules
- for the instance, the instance is publicly available at the floating IP
- address.
-
- .. note::
-
- The :command:`openstack server` command does not allow users to associate a
- floating IP address with a specific fixed IP address using the optional
- ``--fixed-address`` parameter, which legacy commands required as an
- argument.
-
-Disassociate floating IP addresses
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-To disassociate a floating IP address from an instance:
-
-.. code-block:: console
-
- $ openstack server remove floating ip INSTANCE_NAME_OR_ID FLOATING_IP_ADDRESS
-
-To remove the floating IP address from a project:
-
-.. code-block:: console
-
- $ openstack floating ip delete FLOATING_IP_ADDRESS
-
-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.
diff --git a/doc/user-guide/source/cli-manage-shares.rst b/doc/user-guide/source/cli-manage-shares.rst
deleted file mode 100644
index 150545d59b..0000000000
--- a/doc/user-guide/source/cli-manage-shares.rst
+++ /dev/null
@@ -1,630 +0,0 @@
-.. _share:
-
-=============
-Manage shares
-=============
-
-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.
-
-Create a share network
-~~~~~~~~~~~~~~~~~~~~~~
-
-#. Create a share network.
-
- .. code-block:: console
-
- $ manila share-network-create \
- --name mysharenetwork \
- --description "My Manila network" \
- --neutron-net-id dca0efc7-523d-43ef-9ded-af404a02b055 \
- --neutron-subnet-id 29ecfbd5-a9be-467e-8b4a-3415d1f82888
- +-------------------+--------------------------------------+
- | Property | Value |
- +-------------------+--------------------------------------+
- | name | mysharenetwork |
- | segmentation_id | None |
- | created_at | 2016-03-24T14:13:02.888816 |
- | neutron_subnet_id | 29ecfbd5-a9be-467e-8b4a-3415d1f82888 |
- | updated_at | None |
- | network_type | None |
- | neutron_net_id | dca0efc7-523d-43ef-9ded-af404a02b055 |
- | ip_version | None |
- | nova_net_id | None |
- | cidr | None |
- | project_id | 907004508ef4447397ce6741a8f037c1 |
- | id | c895fe26-92be-4152-9e6c-f2ad230efb13 |
- | description | My Manila network |
- +-------------------+--------------------------------------+
-
-#. List share networks.
-
- .. code-block:: console
-
- $ manila share-network-list
- +--------------------------------------+----------------+
- | id | name |
- +--------------------------------------+----------------+
- | c895fe26-92be-4152-9e6c-f2ad230efb13 | mysharenetwork |
- +--------------------------------------+----------------+
-
-Create a share
-~~~~~~~~~~~~~~
-
-#. Create a share.
-
- .. code-block:: console
-
- $ manila create NFS 1 \
- --name myshare \
- --description "My Manila share" \
- --share-network mysharenetwork \
- --share-type default
- +-----------------------------+--------------------------------------+
- | Property | Value |
- +-----------------------------+--------------------------------------+
- | status | creating |
- | share_type_name | default |
- | description | My Manila share |
- | availability_zone | None |
- | share_network_id | c895fe26-92be-4152-9e6c-f2ad230efb13 |
- | share_server_id | None |
- | host | |
- | access_rules_status | active |
- | snapshot_id | None |
- | is_public | False |
- | task_state | None |
- | snapshot_support | True |
- | id | 8d8b854b-ec32-43f1-acc0-1b2efa7c3400 |
- | size | 1 |
- | name | myshare |
- | share_type | bf6ada49-990a-47c3-88bc-c0cb31d5c9bf |
- | has_replicas | False |
- | replication_type | None |
- | created_at | 2016-03-24T14:15:34.000000 |
- | share_proto | NFS |
- | consistency_group_id | None |
- | source_cgsnapshot_member_id | None |
- | project_id | 907004508ef4447397ce6741a8f037c1 |
- | metadata | {} |
- +-----------------------------+--------------------------------------+
-
-#. Show a share.
-
- .. code-block:: console
-
- $ manila show myshare
- +-----------------------------+---------------------------------------------------------------+
- | Property | Value |
- +-----------------------------+---------------------------------------------------------------+
- | status | available |
- | share_type_name | default |
- | description | My Manila share |
- | availability_zone | nova |
- | share_network_id | c895fe26-92be-4152-9e6c-f2ad230efb13 |
- | export_locations | |
- | | path = 10.254.0.3:/share-e1c2d35e-fe67-4028-ad7a-45f668732b1d |
- | | preferred = False |
- | | is_admin_only = False |
- | | id = b6bd76ce-12a2-42a9-a30a-8a43b503867d |
- | | share_instance_id = e1c2d35e-fe67-4028-ad7a-45f668732b1d |
- | | path = 10.0.0.3:/share-e1c2d35e-fe67-4028-ad7a-45f668732b1d |
- | | preferred = False |
- | | is_admin_only = True |
- | | id = 6921e862-88bc-49a5-a2df-efeed9acd583 |
- | | share_instance_id = e1c2d35e-fe67-4028-ad7a-45f668732b1d |
- | share_server_id | 2e9d2d02-883f-47b5-bb98-e053b8d1e683 |
- | host | nosb-devstack@london#LONDON |
- | access_rules_status | active |
- | snapshot_id | None |
- | is_public | False |
- | task_state | None |
- | snapshot_support | True |
- | id | 8d8b854b-ec32-43f1-acc0-1b2efa7c3400 |
- | size | 1 |
- | name | myshare |
- | share_type | bf6ada49-990a-47c3-88bc-c0cb31d5c9bf |
- | has_replicas | False |
- | replication_type | None |
- | created_at | 2016-03-24T14:15:34.000000 |
- | share_proto | NFS |
- | consistency_group_id | None |
- | source_cgsnapshot_member_id | None |
- | project_id | 907004508ef4447397ce6741a8f037c1 |
- | metadata | {} |
- +-----------------------------+---------------------------------------------------------------+
-
-#. List shares.
-
- .. code-block:: console
-
- $ manila list
- +--------------------------------------+---------+------+-------------+-----------+-----------+-----------------+-----------------------------+-------------------+
- | ID | Name | Size | Share Proto | Status | Is Public | Share Type Name | Host | Availability Zone |
- +--------------------------------------+---------+------+-------------+-----------+-----------+-----------------+-----------------------------+-------------------+
- | 8d8b854b-ec32-43f1-acc0-1b2efa7c3400 | myshare | 1 | NFS | available | False | default | nosb-devstack@london#LONDON | nova |
- +--------------------------------------+---------+------+-------------+-----------+-----------+-----------------+-----------------------------+-------------------+
-
-#. List share export locations.
-
- .. code-block:: console
-
- $ manila share-export-location-list myshare
- +--------------------------------------+--------------------------------------------------------+-----------+
- | ID | Path | Preferred |
- +--------------------------------------+--------------------------------------------------------+-----------+
- | 6921e862-88bc-49a5-a2df-efeed9acd583 | 10.0.0.3:/share-e1c2d35e-fe67-4028-ad7a-45f668732b1d | False |
- | b6bd76ce-12a2-42a9-a30a-8a43b503867d | 10.254.0.3:/share-e1c2d35e-fe67-4028-ad7a-45f668732b1d | False |
- +--------------------------------------+--------------------------------------------------------+-----------+
-
-Allow read-write access
-~~~~~~~~~~~~~~~~~~~~~~~
-
-#. Allow access.
-
- .. code-block:: console
-
- $ manila access-allow myshare ip 10.0.0.0/24
- +--------------+--------------------------------------+
- | Property | Value |
- +--------------+--------------------------------------+
- | share_id | 8d8b854b-ec32-43f1-acc0-1b2efa7c3400 |
- | access_type | ip |
- | access_to | 10.0.0.0/24 |
- | access_level | rw |
- | state | new |
- | id | 0c8470ca-0d77-490c-9e71-29e1f453bf97 |
- +--------------+--------------------------------------+
-
-#. List access.
-
- .. code-block:: console
-
- $ manila access-list myshare
- +--------------------------------------+-------------+-------------+--------------+--------+
- | id | access_type | access_to | access_level | state |
- +--------------------------------------+-------------+-------------+--------------+--------+
- | 0c8470ca-0d77-490c-9e71-29e1f453bf97 | ip | 10.0.0.0/24 | rw | active |
- +--------------------------------------+-------------+-------------+--------------+--------+
-
- The access is created.
-
-Allow read-only access
-~~~~~~~~~~~~~~~~~~~~~~
-
-#. Allow access.
-
- .. code-block:: console
-
- $ manila access-allow myshare ip 20.0.0.0/24 --access-level ro
- +--------------+--------------------------------------+
- | Property | Value |
- +--------------+--------------------------------------+
- | share_id | 8d8b854b-ec32-43f1-acc0-1b2efa7c3400 |
- | access_type | ip |
- | access_to | 20.0.0.0/24 |
- | access_level | ro |
- | state | new |
- | id | f151ad17-654d-40ce-ba5d-98a5df67aadc |
- +--------------+--------------------------------------+
-
-#. List access.
-
- .. code-block:: console
-
- $ manila access-list myshare
- +--------------------------------------+-------------+-------------+--------------+--------+
- | id | access_type | access_to | access_level | state |
- +--------------------------------------+-------------+-------------+--------------+--------+
- | 0c8470ca-0d77-490c-9e71-29e1f453bf97 | ip | 10.0.0.0/24 | rw | active |
- | f151ad17-654d-40ce-ba5d-98a5df67aadc | ip | 20.0.0.0/24 | ro | active |
- +--------------------------------------+-------------+-------------+--------------+--------+
-
- The access is created.
-
-Deny access
-~~~~~~~~~~~
-
-#. Deny access.
-
- .. code-block:: console
-
- $ manila access-deny myshare 0c8470ca-0d77-490c-9e71-29e1f453bf97
- $ manila access-deny myshare f151ad17-654d-40ce-ba5d-98a5df67aadc
-
-#. List access.
-
- .. code-block:: console
-
- $ manila access-list myshare
- +----+-------------+-----------+--------------+-------+
- | id | access type | access to | access level | state |
- +----+-------------+-----------+--------------+-------+
- +----+-------------+-----------+--------------+-------+
-
- The access is removed.
-
-Create snapshot
-~~~~~~~~~~~~~~~
-
-#. Create a snapshot.
-
- .. code-block:: console
-
- $ manila snapshot-create --name mysnapshot --description "My Manila snapshot" myshare
- +-------------------+--------------------------------------+
- | Property | Value |
- +-------------------+--------------------------------------+
- | status | creating |
- | share_id | 8d8b854b-ec32-43f1-acc0-1b2efa7c3400 |
- | description | My Manila snapshot |
- | created_at | 2016-03-24T14:39:58.232844 |
- | share_proto | NFS |
- | provider_location | None |
- | id | e744ca47-0931-4e81-9d9f-2ead7d7c1640 |
- | size | 1 |
- | share_size | 1 |
- | name | mysnapshot |
- +-------------------+--------------------------------------+
-
-#. List snapshots.
-
- .. code-block:: console
-
- $ manila snapshot-list
- +--------------------------------------+--------------------------------------+-----------+------------+------------+
- | ID | Share ID | Status | Name | Share Size |
- +--------------------------------------+--------------------------------------+-----------+------------+------------+
- | e744ca47-0931-4e81-9d9f-2ead7d7c1640 | 8d8b854b-ec32-43f1-acc0-1b2efa7c3400 | available | mysnapshot | 1 |
- +--------------------------------------+--------------------------------------+-----------+------------+------------+
-
-Create share from snapshot
-~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-#. Create a share from a snapshot.
-
- .. code-block:: console
-
- $ manila create NFS 1 \
- --snapshot-id e744ca47-0931-4e81-9d9f-2ead7d7c1640 \
- --share-network mysharenetwork \
- --name mysharefromsnap
- +-----------------------------+--------------------------------------+
- | Property | Value |
- +-----------------------------+--------------------------------------+
- | status | creating |
- | share_type_name | default |
- | description | None |
- | availability_zone | nova |
- | share_network_id | c895fe26-92be-4152-9e6c-f2ad230efb13 |
- | share_server_id | None |
- | host | nosb-devstack@london#LONDON |
- | access_rules_status | active |
- | snapshot_id | e744ca47-0931-4e81-9d9f-2ead7d7c1640 |
- | is_public | False |
- | task_state | None |
- | snapshot_support | True |
- | id | e73ebcd3-4764-44f0-9b42-fab5cf34a58b |
- | size | 1 |
- | name | mysharefromsnap |
- | share_type | bf6ada49-990a-47c3-88bc-c0cb31d5c9bf |
- | has_replicas | False |
- | replication_type | None |
- | created_at | 2016-03-24T14:41:36.000000 |
- | share_proto | NFS |
- | consistency_group_id | None |
- | source_cgsnapshot_member_id | None |
- | project_id | 907004508ef4447397ce6741a8f037c1 |
- | metadata | {} |
- +-----------------------------+--------------------------------------+
-
-#. List shares.
-
- .. code-block:: console
-
- $ manila list
- +--------------------------------------+-----------------+------+-------------+-----------+-----------+-----------------+-----------------------------+-------------------+
- | ID | Name | Size | Share Proto | Status | Is Public | Share Type Name | Host | Availability Zone |
- +--------------------------------------+-----------------+------+-------------+-----------+-----------+-----------------+-----------------------------+-------------------+
- | 8d8b854b-ec32-43f1-acc0-1b2efa7c3400 | myshare | 1 | NFS | available | False | default | nosb-devstack@london#LONDON | nova |
- | e73ebcd3-4764-44f0-9b42-fab5cf34a58b | mysharefromsnap | 1 | NFS | available | False | default | nosb-devstack@london#LONDON | nova |
- +--------------------------------------+-----------------+------+-------------+-----------+-----------+-----------------+-----------------------------+-------------------+
-
-#. Show the share created from snapshot.
-
- .. code-block:: console
-
- $ manila show mysharefromsnap
- +-----------------------------+---------------------------------------------------------------+
- | Property | Value |
- +-----------------------------+---------------------------------------------------------------+
- | status | available |
- | share_type_name | default |
- | description | None |
- | availability_zone | nova |
- | share_network_id | c895fe26-92be-4152-9e6c-f2ad230efb13 |
- | export_locations | |
- | | path = 10.254.0.3:/share-4c00cb49-51d9-478e-abc1-d1853efaf6d3 |
- | | preferred = False |
- | | is_admin_only = False |
- | | id = 5419fb40-04b9-4a52-b08e-19aa1ce13a5c |
- | | share_instance_id = 4c00cb49-51d9-478e-abc1-d1853efaf6d3 |
- | | path = 10.0.0.3:/share-4c00cb49-51d9-478e-abc1-d1853efaf6d3 |
- | | preferred = False |
- | | is_admin_only = True |
- | | id = 26f55e4c-6edc-4e55-8c55-c62b7db1aa9f |
- | | share_instance_id = 4c00cb49-51d9-478e-abc1-d1853efaf6d3 |
- | share_server_id | 2e9d2d02-883f-47b5-bb98-e053b8d1e683 |
- | host | nosb-devstack@london#LONDON |
- | access_rules_status | active |
- | snapshot_id | e744ca47-0931-4e81-9d9f-2ead7d7c1640 |
- | is_public | False |
- | task_state | None |
- | snapshot_support | True |
- | id | e73ebcd3-4764-44f0-9b42-fab5cf34a58b |
- | size | 1 |
- | name | mysharefromsnap |
- | share_type | bf6ada49-990a-47c3-88bc-c0cb31d5c9bf |
- | has_replicas | False |
- | replication_type | None |
- | created_at | 2016-03-24T14:41:36.000000 |
- | share_proto | NFS |
- | consistency_group_id | None |
- | source_cgsnapshot_member_id | None |
- | project_id | 907004508ef4447397ce6741a8f037c1 |
- | metadata | {} |
- +-----------------------------+---------------------------------------------------------------+
-
-Delete share
-~~~~~~~~~~~~
-
-#. Delete a share.
-
- .. code-block:: console
-
- $ manila delete mysharefromsnap
-
-#. List shares.
-
- .. code-block:: console
-
- $ manila list
- +--------------------------------------+-----------------+------+-------------+-----------+-----------+-----------------+-----------------------------+-------------------+
- | ID | Name | Size | Share Proto | Status | Is Public | Share Type Name | Host | Availability Zone |
- +--------------------------------------+-----------------+------+-------------+-----------+-----------+-----------------+-----------------------------+-------------------+
- | 8d8b854b-ec32-43f1-acc0-1b2efa7c3400 | myshare | 1 | NFS | available | False | default | nosb-devstack@london#LONDON | nova |
- | e73ebcd3-4764-44f0-9b42-fab5cf34a58b | mysharefromsnap | 1 | NFS | deleting | False | default | nosb-devstack@london#LONDON | nova |
- +--------------------------------------+-----------------+------+-------------+-----------+-----------+-----------------+-----------------------------+-------------------+
-
- The share is being deleted.
-
-Delete snapshot
-~~~~~~~~~~~~~~~
-
-#. List snapshots before deleting.
-
- .. code-block:: console
-
- $ manila snapshot-list
- +--------------------------------------+--------------------------------------+-----------+------------+------------+
- | ID | Share ID | Status | Name | Share Size |
- +--------------------------------------+--------------------------------------+-----------+------------+------------+
- | e744ca47-0931-4e81-9d9f-2ead7d7c1640 | 8d8b854b-ec32-43f1-acc0-1b2efa7c3400 | available | mysnapshot | 1 |
- +--------------------------------------+--------------------------------------+-----------+------------+------------+
-
-#. Delete a snapshot.
-
- .. code-block:: console
-
- $ manila snapshot-delete mysnapshot
-
-#. List snapshots after deleting.
-
- .. code-block:: console
-
- $ manila snapshot-list
-
- +----+----------+--------+------+------------+
- | ID | Share ID | Status | Name | Share Size |
- +----+----------+--------+------+------------+
- +----+----------+--------+------+------------+
-
- The snapshot is deleted.
-
-Extend share
-~~~~~~~~~~~~
-
-#. Extend share.
-
- .. code-block:: console
-
- $ manila extend myshare 2
-
-#. Show the share while it is being extended.
-
- .. code-block:: console
-
- $ manila show myshare
- +-----------------------------+---------------------------------------------------------------+
- | Property | Value |
- +-----------------------------+---------------------------------------------------------------+
- | status | extending |
- | share_type_name | default |
- | description | My Manila share |
- | availability_zone | nova |
- | share_network_id | c895fe26-92be-4152-9e6c-f2ad230efb13 |
- | export_locations | |
- | | path = 10.254.0.3:/share-e1c2d35e-fe67-4028-ad7a-45f668732b1d |
- | | preferred = False |
- | | is_admin_only = False |
- | | id = b6bd76ce-12a2-42a9-a30a-8a43b503867d |
- | | share_instance_id = e1c2d35e-fe67-4028-ad7a-45f668732b1d |
- | | path = 10.0.0.3:/share-e1c2d35e-fe67-4028-ad7a-45f668732b1d |
- | | preferred = False |
- | | is_admin_only = True |
- | | id = 6921e862-88bc-49a5-a2df-efeed9acd583 |
- | | share_instance_id = e1c2d35e-fe67-4028-ad7a-45f668732b1d |
- | share_server_id | 2e9d2d02-883f-47b5-bb98-e053b8d1e683 |
- | host | nosb-devstack@london#LONDON |
- | access_rules_status | active |
- | snapshot_id | None |
- | is_public | False |
- | task_state | None |
- | snapshot_support | True |
- | id | 8d8b854b-ec32-43f1-acc0-1b2efa7c3400 |
- | size | 1 |
- | name | myshare |
- | share_type | bf6ada49-990a-47c3-88bc-c0cb31d5c9bf |
- | has_replicas | False |
- | replication_type | None |
- | created_at | 2016-03-24T14:15:34.000000 |
- | share_proto | NFS |
- | consistency_group_id | None |
- | source_cgsnapshot_member_id | None |
- | project_id | 907004508ef4447397ce6741a8f037c1 |
- | metadata | {} |
- +-----------------------------+---------------------------------------------------------------+
-
-#. Show the share after it is extended.
-
- .. code-block:: console
-
- $ manila show myshare
- +-----------------------------+---------------------------------------------------------------+
- | Property | Value |
- +-----------------------------+---------------------------------------------------------------+
- | status | available |
- | share_type_name | default |
- | description | My Manila share |
- | availability_zone | nova |
- | share_network_id | c895fe26-92be-4152-9e6c-f2ad230efb13 |
- | export_locations | |
- | | path = 10.254.0.3:/share-e1c2d35e-fe67-4028-ad7a-45f668732b1d |
- | | preferred = False |
- | | is_admin_only = False |
- | | id = b6bd76ce-12a2-42a9-a30a-8a43b503867d |
- | | share_instance_id = e1c2d35e-fe67-4028-ad7a-45f668732b1d |
- | | path = 10.0.0.3:/share-e1c2d35e-fe67-4028-ad7a-45f668732b1d |
- | | preferred = False |
- | | is_admin_only = True |
- | | id = 6921e862-88bc-49a5-a2df-efeed9acd583 |
- | | share_instance_id = e1c2d35e-fe67-4028-ad7a-45f668732b1d |
- | share_server_id | 2e9d2d02-883f-47b5-bb98-e053b8d1e683 |
- | host | nosb-devstack@london#LONDON |
- | access_rules_status | active |
- | snapshot_id | None |
- | is_public | False |
- | task_state | None |
- | snapshot_support | True |
- | id | 8d8b854b-ec32-43f1-acc0-1b2efa7c3400 |
- | size | 2 |
- | name | myshare |
- | share_type | bf6ada49-990a-47c3-88bc-c0cb31d5c9bf |
- | has_replicas | False |
- | replication_type | None |
- | created_at | 2016-03-24T14:15:34.000000 |
- | share_proto | NFS |
- | consistency_group_id | None |
- | source_cgsnapshot_member_id | None |
- | project_id | 907004508ef4447397ce6741a8f037c1 |
- | metadata | {} |
- +-----------------------------+---------------------------------------------------------------+
-
-Shrink share
-~~~~~~~~~~~~
-
-#. Shrink a share.
-
- .. code-block:: console
-
- $ manila shrink myshare 1
-
-#. Show the share while it is being shrunk.
-
- .. code-block:: console
-
- $ manila show myshare
- +-----------------------------+---------------------------------------------------------------+
- | Property | Value |
- +-----------------------------+---------------------------------------------------------------+
- | status | shrinking |
- | share_type_name | default |
- | description | My Manila share |
- | availability_zone | nova |
- | share_network_id | c895fe26-92be-4152-9e6c-f2ad230efb13 |
- | export_locations | |
- | | path = 10.254.0.3:/share-e1c2d35e-fe67-4028-ad7a-45f668732b1d |
- | | preferred = False |
- | | is_admin_only = False |
- | | id = b6bd76ce-12a2-42a9-a30a-8a43b503867d |
- | | share_instance_id = e1c2d35e-fe67-4028-ad7a-45f668732b1d |
- | | path = 10.0.0.3:/share-e1c2d35e-fe67-4028-ad7a-45f668732b1d |
- | | preferred = False |
- | | is_admin_only = True |
- | | id = 6921e862-88bc-49a5-a2df-efeed9acd583 |
- | | share_instance_id = e1c2d35e-fe67-4028-ad7a-45f668732b1d |
- | share_server_id | 2e9d2d02-883f-47b5-bb98-e053b8d1e683 |
- | host | nosb-devstack@london#LONDON |
- | access_rules_status | active |
- | snapshot_id | None |
- | is_public | False |
- | task_state | None |
- | snapshot_support | True |
- | id | 8d8b854b-ec32-43f1-acc0-1b2efa7c3400 |
- | size | 2 |
- | name | myshare |
- | share_type | bf6ada49-990a-47c3-88bc-c0cb31d5c9bf |
- | has_replicas | False |
- | replication_type | None |
- | created_at | 2016-03-24T14:15:34.000000 |
- | share_proto | NFS |
- | consistency_group_id | None |
- | source_cgsnapshot_member_id | None |
- | project_id | 907004508ef4447397ce6741a8f037c1 |
- | metadata | {} |
- +-----------------------------+---------------------------------------------------------------+
-
-#. Show the share after it is being shrunk.
-
- .. code-block:: console
-
- $ manila show myshare
- +-----------------------------+---------------------------------------------------------------+
- | Property | Value |
- +-----------------------------+---------------------------------------------------------------+
- | status | available |
- | share_type_name | default |
- | description | My Manila share |
- | availability_zone | nova |
- | share_network_id | c895fe26-92be-4152-9e6c-f2ad230efb13 |
- | export_locations | |
- | | path = 10.254.0.3:/share-e1c2d35e-fe67-4028-ad7a-45f668732b1d |
- | | preferred = False |
- | | is_admin_only = False |
- | | id = b6bd76ce-12a2-42a9-a30a-8a43b503867d |
- | | share_instance_id = e1c2d35e-fe67-4028-ad7a-45f668732b1d |
- | | path = 10.0.0.3:/share-e1c2d35e-fe67-4028-ad7a-45f668732b1d |
- | | preferred = False |
- | | is_admin_only = True |
- | | id = 6921e862-88bc-49a5-a2df-efeed9acd583 |
- | | share_instance_id = e1c2d35e-fe67-4028-ad7a-45f668732b1d |
- | share_server_id | 2e9d2d02-883f-47b5-bb98-e053b8d1e683 |
- | host | nosb-devstack@london#LONDON |
- | access_rules_status | active |
- | snapshot_id | None |
- | is_public | False |
- | task_state | None |
- | snapshot_support | True |
- | id | 8d8b854b-ec32-43f1-acc0-1b2efa7c3400 |
- | size | 1 |
- | name | myshare |
- | share_type | bf6ada49-990a-47c3-88bc-c0cb31d5c9bf |
- | has_replicas | False |
- | replication_type | None |
- | created_at | 2016-03-24T14:15:34.000000 |
- | share_proto | NFS |
- | consistency_group_id | None |
- | source_cgsnapshot_member_id | None |
- | project_id | 907004508ef4447397ce6741a8f037c1 |
- | metadata | {} |
- +-----------------------------+---------------------------------------------------------------+
diff --git a/doc/user-guide/source/cli-nova-configure-access-security-for-instances.rst b/doc/user-guide/source/cli-nova-configure-access-security-for-instances.rst
deleted file mode 100644
index 5aa6db3c51..0000000000
--- a/doc/user-guide/source/cli-nova-configure-access-security-for-instances.rst
+++ /dev/null
@@ -1,217 +0,0 @@
-===========================================
-Configure access and security for instances
-===========================================
-
-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.
-
-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.
-
-.. note::
-
- 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.
-
-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.
-
-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.
-
-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.
-
-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:
-
-- **Source of traffic**. Enable traffic to instances from either IP
- addresses inside the cloud from other group members or from all IP
- addresses.
-
-- **Protocol**. Choose TCP for SSH, ICMP for pings, or UDP.
-
-- **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.
-
-Rules are automatically enforced as soon as you create or modify them.
-
-.. note::
-
- 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. Additionally, security groups will
- automatically drop DHCP responses coming from instances.
-
- 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`.
-
-Add a key pair
-~~~~~~~~~~~~~~
-
-You can generate a key pair or upload an existing public key.
-
-#. To generate a key pair, run the following command.
-
- .. code-block:: console
-
- $ openstack keypair create KEY_NAME > MY_KEY.pem
-
- 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.
-
-#. To set the permissions of the ``.pem`` file so that only you can read
- and write to it, run the following command.
-
- .. code-block:: console
-
- $ chmod 600 MY_KEY.pem
-
-Import a key pair
-~~~~~~~~~~~~~~~~~
-
-#. 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.
-
- .. code-block:: console
-
- $ openstack keypair create --public-key ~/.ssh/id_rsa.pub KEY_NAME
-
- This command registers the public key at the Nova database and names the
- key pair the name that you specify for ``KEY_NAME``.
-
-#. To ensure that the key pair has been successfully imported, list key
- pairs as follows:
-
- .. code-block:: console
-
- $ openstack keypair list
-
-Create and manage security groups
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-#. To list the security groups for the current project, including
- descriptions, enter the following command:
-
- .. code-block:: console
-
- $ openstack security group list
-
-#. To create a security group with a specified name and description, enter
- the following command:
-
- .. code-block:: console
-
- $ openstack security group create SECURITY_GROUP_NAME --description GROUP_DESCRIPTION
-
-#. To delete a specified group, enter the following command:
-
- .. code-block:: console
-
- $ openstack security group delete SECURITY_GROUP_NAME
-
-.. note::
-
- You cannot delete the default security group for a project. Also,
- you cannot delete a security group that is assigned to a running
- instance.
-
-Create and manage security group rules
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-Modify security group rules with the :command:`openstack security group rule`
-commands. Before you begin, source the OpenStack RC file. For details,
-see :doc:`../common/cli-set-environment-variables-using-openstack-rc`.
-
-#. To list the rules for a security group, run the following command:
-
- .. code-block:: console
-
- $ openstack security group rule list SECURITY_GROUP_NAME
-
-#. To allow SSH access to the instances, choose one of the following
- options:
-
- - Allow access from all IP addresses, specified as IP subnet ``0.0.0.0/0``
- in CIDR notation:
-
- .. code-block:: console
-
- $ openstack security group rule create SECURITY_GROUP_NAME \
- --protocol tcp --dst-port 22:22 --remote-ip 0.0.0.0/0
-
- - Allow access only from IP addresses from other security groups
- (source groups) to access the specified port:
-
- .. code-block:: console
-
- $ openstack security group rule create SECURITY_GROUP_NAME \
- --protocol tcp --dst-port 22:22 --remote-group SOURCE_GROUP_NAME
-
-#. To allow pinging of the instances, choose one of the following options:
-
- - Allow pinging from all IP addresses, specified as IP subnet
- ``0.0.0.0/0`` in CIDR notation.
-
- .. code-block:: console
-
- $ openstack security group rule create --protocol icmp \
- SECURITY_GROUP_NAME
-
- This allows access to all codes and all types of ICMP traffic.
-
- - Allow only members of other security groups (source groups) to ping
- instances.
-
- .. code-block:: console
-
- $ openstack security group rule create --protocol icmp \
- --remote-group SOURCE_GROUP_NAME SECURITY_GROUP
-
-#. 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:
-
- - Allow UDP access from IP addresses, specified as IP subnet
- ``0.0.0.0/0`` in CIDR notation.
-
- .. code-block:: console
-
- $ openstack security group rule create --protocol udp \
- --dst-port 53:53 SECURITY_GROUP
-
- - Allow only IP addresses from other security groups (source groups) to
- access the specified port.
-
- .. code-block:: console
-
- $ openstack security group rule create --protocol udp \
- --dst-port 53:53 --remote-group SOURCE_GROUP_NAME SECURITY_GROUP
-
-Delete a security group rule
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-To delete a security group rule, specify the ID of the rule.
-
-.. code-block:: console
-
- $ openstack security group rule delete RULE_ID
diff --git a/doc/user-guide/source/cli-nova-launch-instance-from-image.rst b/doc/user-guide/source/cli-nova-launch-instance-from-image.rst
deleted file mode 100644
index 700fab6797..0000000000
--- a/doc/user-guide/source/cli-nova-launch-instance-from-image.rst
+++ /dev/null
@@ -1,143 +0,0 @@
-================================
-Launch an instance from an image
-================================
-
-Follow the steps below to launch an instance from an image.
-
-#. After you gather required parameters, run the following command to
- launch an instance. Specify the server name, flavor ID, and image ID.
-
- .. code-block:: console
-
- $ openstack server create --flavor FLAVOR_ID --image IMAGE_ID --key-name KEY_NAME \
- --user-data USER_DATA_FILE --security-group SEC_GROUP_NAME --property KEY=VALUE \
- INSTANCE_NAME
-
- 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
- ``--property description="My Server"`` parameter.
-
- You can pass user data in a local file at instance launch by using the
- ``--user-data USER-DATA-FILE`` parameter.
-
- .. important::
-
- 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 ``neutron-dnsmasq.log`` file.
-
- 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``:
-
- .. code-block:: console
-
- $ openstack server create --flavor 1 --image 397e713c-b95b-4186-ad46-6126863ea0a9 \
- --security-group default --key-name KeyPair01 --user-data cloudinit.file \
- myCirrosServer
-
- Depending on the parameters that you provide, the command returns a list
- of server properties.
-
- .. code-block:: console
-
- +--------------------------------------+-----------------------------------------------+
- | Field | Value |
- +--------------------------------------+-----------------------------------------------+
- | OS-DCF:diskConfig | MANUAL |
- | OS-EXT-AZ:availability_zone | |
- | OS-EXT-SRV-ATTR:host | None |
- | OS-EXT-SRV-ATTR:hypervisor_hostname | None |
- | OS-EXT-SRV-ATTR:instance_name | |
- | OS-EXT-STS:power_state | NOSTATE |
- | OS-EXT-STS:task_state | scheduling |
- | OS-EXT-STS:vm_state | building |
- | OS-SRV-USG:launched_at | None |
- | OS-SRV-USG:terminated_at | None |
- | accessIPv4 | |
- | accessIPv6 | |
- | addresses | |
- | adminPass | E4Ksozt4Efi8 |
- | config_drive | |
- | created | 2016-11-30T14:48:05Z |
- | flavor | m1.tiny |
- | hostId | |
- | id | 89015cc9-bdf1-458a-8518-fdca2b4a5785 |
- | image | cirros (397e713c-b95b-4186-ad46-6126863ea0a9) |
- | key_name | KeyPair01 |
- | name | myCirrosServer |
- | os-extended-volumes:volumes_attached | [] |
- | progress | 0 |
- | project_id | 5669caad86a04256994cdf755df4d3c1 |
- | properties | |
- | security_groups | [{u'name': u'default'}] |
- | status | BUILD |
- | updated | 2016-11-30T14:48:05Z |
- | user_id | c36cec73b0e44876a4478b1e6cd749bb |
- | metadata | {u'KEY': u'VALUE'} |
- +--------------------------------------+-----------------------------------------------+
-
- A status of ``BUILD`` indicates that the instance has started, but is
- not yet online.
-
- A status of ``ACTIVE`` indicates that the instance is active.
-
-#. Copy the server ID value from the ``id`` field in the output. Use the
- ID to get server details or to delete your server.
-
-#. Copy the administrative password value from the ``adminPass`` field. Use the
- password to log in to your server.
-
- .. note::
-
- You can also place arbitrary local files into the instance file
- system at creation time by using the ``--file ``
- option. You can store up to five files. For example, if you have a
- special authorized keys file named ``special_authorized_keysfile`` that
- you want to put on the instance rather than using the regular SSH key
- injection, you can use the ``--file`` option as shown in the following
- example.
-
- .. code-block:: console
-
- $ openstack server create --image ubuntu-cloudimage --flavor 1 vm-name \
- --file /root/.ssh/authorized_keys=special_authorized_keysfile
-
-#. Check if the instance is online.
-
- .. code-block:: console
-
- $ openstack server list
-
- 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:
-
- .. code-block:: console
-
- +-------------+----------------------+--------+------------+-------------+------------------+------------+
- | ID | Name | Status | Task State | Power State | Networks | Image Name |
- +-------------+----------------------+--------+------------+-------------+------------------+------------+
- | 84c6e57d... | myCirrosServer | ACTIVE | None | Running | private=10.0.0.3 | cirros |
- | 8a99547e... | myInstanceFromVolume | ACTIVE | None | Running | private=10.0.0.4 | centos |
- +-------------+----------------------+--------+------------+-------------+------------------+------------+
-
- If the status for the instance is ACTIVE, the instance is online.
-
-#. To view the available options for the :command:`openstack server list`
- command, run the following command:
-
- .. code-block:: console
-
- $ openstack help server list
-
- .. note::
-
- 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.
-
diff --git a/doc/user-guide/source/cli-nova-launch-instance-from-volume.rst b/doc/user-guide/source/cli-nova-launch-instance-from-volume.rst
deleted file mode 100644
index e3415b8dfc..0000000000
--- a/doc/user-guide/source/cli-nova-launch-instance-from-volume.rst
+++ /dev/null
@@ -1,335 +0,0 @@
-================================
-Launch an instance from a volume
-================================
-
-You can boot instances from a volume instead of an image.
-
-To complete these tasks, use these parameters on the
-:command:`openstack server create` command:
-
-.. tabularcolumns:: |p{0.3\textwidth}|p{0.25\textwidth}|p{0.4\textwidth}|
-.. list-table::
- :header-rows: 1
- :widths: 30 15 30
-
- * - Task
- - openstack server create parameter
- - Information
- * - Boot an instance from an image and attach a non-bootable
- volume.
- - ``--block-device-mapping``
- - :ref:`Boot_instance_from_image_and_attach_non-bootable_volume`
- * - Create a volume from an image and boot an instance from that
- volume.
- - ``--volume``
- - :ref:`Create_volume_from_image_and_boot_instance`
- * - Boot from an existing source volume or snapshot.
- - ``--volume``
- - :ref:`Create_volume_from_image_and_boot_instance`
-
-.. note::
-
- To attach a volume to a running instance, see
- :ref:`Attach_a_volume_to_an_instance`.
-
-.. _Boot_instance_from_image_and_attach_non-bootable_volume:
-
-Boot instance from image and attach non-bootable volume
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-Create a non-bootable volume and attach that volume to an instance that
-you boot from an image.
-
-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.
-
-#. Create a non-bootable volume.
-
- .. code-block:: console
-
- $ openstack volume create --size 8 my-volume
- +---------------------+--------------------------------------+
- | Field | Value |
- +---------------------+--------------------------------------+
- | attachments | [] |
- | availability_zone | nova |
- | bootable | false |
- | consistencygroup_id | None |
- | created_at | 2017-06-10T13:45:19.588269 |
- | description | None |
- | encrypted | False |
- | id | e77b30a9-2c1b-4f3a-b161-e09685296a83 |
- | migration_status | None |
- | multiattach | False |
- | name | my-volume |
- | properties | |
- | replication_status | disabled |
- | size | 8 |
- | snapshot_id | None |
- | source_volid | None |
- | status | creating |
- | type | lvmdriver-1 |
- | updated_at | None |
- | user_id | 07a3f50419714d90b55edb6505b7cc1d |
- +---------------------+--------------------------------------+
-
-#. List volumes.
-
- .. code-block:: console
-
- $ openstack volume list
- +--------------------------------------+--------------+-----------+------+-------------+
- | ID | Display Name | Status | Size | Attached to |
- +--------------------------------------+--------------+-----------+------+-------------+
- | e77b30a9-2c1b-4f3a-b161-e09685296a83 | my-volume | available | 8 | |
- +--------------------------------------+--------------+-----------+------+-------------+
-
-#. Boot an instance from an image and attach the empty volume to the
- instance, use the ``--block-device-mapping`` parameter.
-
- For example:
-
- .. code-block:: console
-
- $ openstack server create --flavor FLAVOR --image IMAGE \
- --block-device-mapping DEV-NAME=ID:TYPE:SIZE:DELETE_ON_TERMINATE \
- NAME
-
- The parameters are:
-
- - ``--flavor``
- The flavor ID or name.
-
- - ``--image``
- The image ID or name.
-
- - ``--block-device-mapping``
- DEV-NAME=ID:TYPE:SIZE:DELETE_ON_TERMINATE
-
- **DEV-NAME**
- The device name to attch the volume when the instance is booted.
-
- **ID**
- The ID of the source object.
-
- **TYPE**
- Which type object to create the volume.
- ``volume`` chooses volume to create. ``snapshot`` chooses snapshot
- to create.
-
- **SIZE**
- The size(GB) of the volume that is created.
-
- **DELETE_ON_TERMINATE**
- What to do with the volume when the instance is terminated.
- ``false`` does not delete the volume. ``true`` deletes the
- volume.
-
- - ``NAME``. The name for the server.
-
- .. code-block:: console
-
- $ openstack server create --flavor 2 --image c76cf108-1760-45aa-8559-28176f2c0530 \
- --block-device-mapping \
- myVolumeAttach=e77b30a9-2c1b-4f3a-b161-e09685296a83:volume:8:false \
- myInstanceWithVolume
- +--------------------------------------+--------------------------------------------+
- | Field | Value |
- +--------------------------------------+--------------------------------------------+
- | OS-DCF:diskConfig | MANUAL |
- | OS-EXT-AZ:availability_zone | |
- | OS-EXT-SRV-ATTR:host | None |
- | OS-EXT-SRV-ATTR:hypervisor_hostname | None |
- | OS-EXT-SRV-ATTR:instance_name | instance-00000004 |
- | OS-EXT-STS:power_state | NOSTATE |
- | OS-EXT-STS:task_state | scheduling |
- | OS-EXT-STS:vm_state | building |
- | OS-SRV-USG:launched_at | None |
- | OS-SRV-USG:terminated_at | None |
- | accessIPv4 | |
- | accessIPv6 | |
- | addresses | |
- | adminPass | UAwJJ7FZWxmA |
- | config_drive | |
- | created | 2017-06-10T13:50:47Z |
- | flavor | m1.small (2) |
- | hostId | |
- | id | 555cf3e2-9ba3-46bf-9aa5-0a0c73d5b538 |
- | image | cirros-0.3.5-x86_64-uec (c76cf108-1760-... |
- | key_name | None |
- | name | InstanceWithVolume |
- | os-extended-volumes:volumes_attached | [{u'id': u'e77b30a9-2c1b-4f3a-b161-e096... |
- | progress | 0 |
- | project_id | ff903e4825c74f8dbc1aea6432e4f2fd |
- | properties | |
- | security_groups | [{u'name': u'default'}] |
- | status | BUILD |
- | updated | 2017-06-10T13:50:48Z |
- | user_id | 07a3f50419714d90b55edb6505b7cc1d |
- +--------------------------------------+--------------------------------------------+
-
-.. _Create_volume_from_image_and_boot_instance:
-
-Create volume from image and boot instance
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-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.
-
-#. List the available images.
-
- .. code-block:: console
-
- $ openstack image list
- +-----------------+---------------------------------+--------+
- | ID | Name | Status |
- +-----------------+---------------------------------+--------+
- | dfcd8407-486... | Fedora-x86_64-20-20131211.1-sda | active |
- | c76cf108-176... | cirros-0.3.5-x86_64-uec | active |
- | 02d6b27f-40b... | cirros-0.3.5-x86_64-uec-kernel | active |
- | 47b90a42-8f4... | cirros-0.3.5-x86_64-uec-ramdisk | active |
- +-----------------+---------------------------------+--------+
-
- Note the ID of the image that you want to use to create a volume.
-
- 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.
-
- .. code-block:: console
-
- $ openstack image show dfcd8407-4865-4d82-93f3-7fef323a5951
- +------------------+------------------------------------------------------+
- | Field | Value |
- +------------------+------------------------------------------------------+
- | checksum | eb9139e4942121f22bbc2afc0400b2a4 |
- | container_format | bare |
- | created_at | 2017-06-10T06:46:26Z |
- | disk_format | qcow2 |
- | file | /v2/images/dfcd8407-4865-4d82-93f3-7fef323a5951/file |
- | id | dfcd8407-4865-4d82-93f3-7fef323a5951 |
- | min_disk | 0 |
- | min_ram | 0 |
- | name | Fedora-x86_64-20-20131211.1-sda |
- | owner | 5ed8a204e27d462a8709bc8ec491e873 |
- | protected | False |
- | schema | /v2/schemas/image |
- | size | 25165824 |
- | status | active |
- | tags | |
- | updated_at | 2017-06-10T13:36:55Z |
- | virtual_size | None |
- | visibility | public |
- +------------------+------------------------------------------------------+
-
-#. List the available flavors.
-
- .. code-block:: console
-
- $ openstack flavor list
- +-----+-----------+-------+------+-----------+-------+-----------+
- | ID | Name | RAM | Disk | Ephemeral | VCPUs | Is_Public |
- +-----+-----------+-------+------+-----------+-------+-----------+
- | 1 | m1.tiny | 512 | 1 | 0 | 1 | True |
- | 2 | m1.small | 2048 | 20 | 0 | 1 | True |
- | 3 | m1.medium | 4096 | 40 | 0 | 2 | True |
- | 4 | m1.large | 8192 | 80 | 0 | 4 | True |
- | 5 | m1.xlarge | 16384 | 160 | 0 | 8 | True |
- +-----+-----------+-------+------+-----------+-------+-----------+
-
- Note the ID of the flavor that you want to use to create a volume.
-
-#. Create a bootable volume from an image. Cinder makes a volume bootable
- when ``--image`` parameter is passed.
-
- .. code-block:: console
-
- $ openstack volume create --image IMAGE_ID --size SIZE_IN_GB bootable_volume
-
-#. Create a VM from previously created bootable volume,
- use the ``--volume`` parameter. The volume is not
- deleted when the instance is terminated.
-
- .. code-block:: console
-
- $ openstack server create --flavor 2 --volume VOLUME_ID \
- myInstanceFromVolume
- +--------------------------------------+----------------------------------+
- | Field | Value |
- +--------------------------------------+----------------------------------+
- | OS-DCF:diskConfig | MANUAL |
- | OS-EXT-AZ:availability_zone | |
- | OS-EXT-SRV-ATTR:host | None |
- | OS-EXT-SRV-ATTR:hypervisor_hostname | None |
- | OS-EXT-SRV-ATTR:instance_name | instance-00000005 |
- | OS-EXT-STS:power_state | NOSTATE |
- | OS-EXT-STS:task_state | scheduling |
- | OS-EXT-STS:vm_state | building |
- | OS-SRV-USG:launched_at | None |
- | OS-SRV-USG:terminated_at | None |
- | accessIPv4 | |
- | accessIPv6 | |
- | addresses | |
- | adminPass | dizZcBMnWH8i |
- | config_drive | |
- | created | 2017-06-10T14:15:10Z |
- | flavor | m1.small (2) |
- | hostId | |
- | id | 7074c21a-22b3-4e91-9ea1-6a22c... |
- | image | |
- | key_name | None |
- | name | myInstanceFromVolume |
- | os-extended-volumes:volumes_attached | [{u'id': u'3da01e5a-7d81-4a34... |
- | progress | 0 |
- | project_id | ff903e4825c74f8dbc1aea6432e4f2fd |
- | properties | |
- | security_groups | [{u'name': u'default'}] |
- | status | BUILD |
- | updated | 2017-06-10T14:15:11Z |
- | user_id | 07a3f50419714d90b55edb6505b7cc1d |
- +--------------------------------------+----------------------------------+
-
-#. List volumes to see the bootable volume and its attached
- ``myInstanceFromVolume`` instance.
-
- .. code-block:: console
-
- $ openstack volume list
- +---------------------+-----------------+--------+------+---------------------------------+
- | ID | Display Name | Status | Size | Attached to |
- +---------------------+-----------------+--------+------+---------------------------------+
- | 3da01e5a-7d81-4a34- | bootable_volume | in-use | 2 | Attached to myInstanceFromVolume|
- | a182-1958d10f7758 | | | | on /dev/vda |
- +---------------------+-----------------+--------+------+---------------------------------+
-
-.. _Attach_swap_or_ephemeral_disk_to_an_instance:
-
-Attach swap or ephemeral disk to an instance
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-To attach swap or ephemeral disk to an instance, you need create new
-flavor first. This procedure shows you how to boot an instance with
-a 512 MB swap disk and 2 GB ephemeral disk.
-
-#. Create a new flavor.
-
- .. code-block:: console
-
- $ openstack flavor create --vcpus 1 --ram 64 --disk 1 \
- --swap 512 --ephemeral 2 my_flavor
-
- .. note::
-
- The flavor defines the maximum swap and ephemeral disk size. You
- cannot exceed these maximum values.
-
-#. Create a server with 512 MB swap disk and 2 GB ephemeral disk.
-
- .. code-block:: console
-
- $ openstack server create --image IMAGE_ID --flavor \
- my_flavor NAME
-
diff --git a/doc/user-guide/source/cli-nova-launch-instance-using-ISO-image.rst b/doc/user-guide/source/cli-nova-launch-instance-using-ISO-image.rst
deleted file mode 100644
index 2e018b7c0f..0000000000
--- a/doc/user-guide/source/cli-nova-launch-instance-using-ISO-image.rst
+++ /dev/null
@@ -1,147 +0,0 @@
-==================================
-Launch an instance using ISO image
-==================================
-
-.. _Boot_instance_from_ISO_image:
-
-Boot an instance from an ISO image
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-OpenStack supports booting instances using ISO images. But before you
-make such instances functional, use the :command:`openstack server create`
-command with the following parameters to boot an instance:
-
-.. code-block:: console
-
- $ openstack server create --image ubuntu-14.04.2-server-amd64.iso \
- --nic net-id = NETWORK_UUID \
- --flavor 2 INSTANCE_NAME
- +--------------------------------------+--------------------------------------------+
- | Field | Value |
- +--------------------------------------+--------------------------------------------+
- | OS-DCF:diskConfig | MANUAL |
- | OS-EXT-AZ:availability_zone | nova |
- | OS-EXT-SRV-ATTR:host | - |
- | OS-EXT-SRV-ATTR:hypervisor_hostname | - |
- | OS-EXT-SRV-ATTR:instance_name | instance-00000004 |
- | OS-EXT-STS:power_state | 0 |
- | OS-EXT-STS:task_state | scheduling |
- | OS-EXT-STS:vm_state | building |
- | OS-SRV-USG:launched_at | - |
- | OS-SRV-USG:terminated_at | - |
- | accessIPv4 | |
- | accessIPv6 | |
- | adminPass | ZaiYeC8iucgU |
- | config_drive | |
- | created | 2015-06-01T16:34:50Z |
- | flavor | m1.small (2) |
- | hostId | |
- | id | 1e1797f3-1662-49ff-ae8c-a77e82ee1571 |
- | image | ubuntu-14.04.2-server-amd64.iso |
- | key_name | - |
- | metadata | {} |
- | name | INSTANCE_NAME |
- | os-extended-volumes:volumes_attached | [] |
- | progress | 0 |
- | security_groups | default |
- | status | BUILD |
- | tenant_id | ccef9e62b1e645df98728fb2b3076f27 |
- | updated | 2014-05-09T16:34:51Z |
- | user_id | fef060ae7bfd4024b3edb97dff59017a |
- +--------------------------------------+--------------------------------------------+
-
-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.
-
-Create a bootable volume for the instance to reside on after shutdown.
-
-#. Create the volume:
-
- .. code-block:: console
-
- $ openstack volume create \
- --size \
- --bootable VOLUME_NAME
-
-#. Attach the instance to the volume:
-
- .. code-block:: console
-
- $ openstack server add volume
- INSTANCE_NAME \
- VOLUME_NAME \
- --device /dev/vda
-
-.. note::
-
- You need the Block Storage service to preserve the instance after
- shutdown. The ``--block-device`` argument, used with the
- legacy :command:`nova boot`, will not work with the OpenStack
- :command:`openstack server create` command. Instead, the
- :command:`openstack volume create` and
- :command:`openstack server add volume` commands create persistent storage.
-
-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.
-
-.. _Make_instance_booted_from_ISO_image_functional:
-
-Make the instances booted from ISO image functional
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-Now complete the following steps to make your instances created
-using ISO image actually functional.
-
-#. Delete the instance using the following command.
-
- .. code-block:: console
-
- $ openstack server delete INSTANCE_NAME
-
-#. 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.
-
- .. code-block:: console
-
- $ openstack volume list
- +--------------------------+-------------------------+-----------+------+-------------+
- | ID | Display Name | Status | Size | Attached to |
- +--------------------------+-------------------------+-----------+------+-------------+
- | 8edd7c97-1276-47a5-9563- |dc01d873-d0f1-40b6-bfcc- | available | 10 | |
- | 1025f4264e4f | 26a8d955a1d9-blank-vol | | | |
- +--------------------------+-------------------------+-----------+------+-------------+
-
- 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.
-
-#. Upload the volume to glance.
-
- .. code-block:: console
-
- $ openstack image create --volume SOURCE_VOLUME IMAGE_NAME
- $ openstack image list
- +-------------------+------------+--------+
- | ID | Name | Status |
- +-------------------+------------+--------+
- | 74303284-f802-... | IMAGE_NAME | active |
- +-------------------+------------+--------+
-
- The ``SOURCE_VOLUME`` is the UUID or a name 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.
-
-#. After the image is successfully uploaded, you can use the new
- image to boot instances.
-
- The instances launched using this image contain the system that
- you have just installed using the ISO image.
diff --git a/doc/user-guide/source/cli-provide-user-data-to-instances.rst b/doc/user-guide/source/cli-provide-user-data-to-instances.rst
deleted file mode 100644
index 96cef9c8e4..0000000000
--- a/doc/user-guide/source/cli-provide-user-data-to-instances.rst
+++ /dev/null
@@ -1,19 +0,0 @@
-==============================
-Provide user data to instances
-==============================
-
-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.
-
-You can place user data in a local file and pass it through the
-``--user-data `` parameter at instance creation.
-
-.. code-block:: console
-
- $ openstack server create --image ubuntu-cloudimage --flavor 1 \
- --user-data mydata.file VM_INSTANCE
diff --git a/doc/user-guide/source/cli-reboot-an-instance.rst b/doc/user-guide/source/cli-reboot-an-instance.rst
deleted file mode 100644
index f9966ee82b..0000000000
--- a/doc/user-guide/source/cli-reboot-an-instance.rst
+++ /dev/null
@@ -1,75 +0,0 @@
-==================
-Reboot an instance
-==================
-
-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.
-
-By default, when you reboot an instance, it is a soft reboot.
-
-.. code-block:: console
-
- $ openstack server reboot SERVER
-
-To perform a hard reboot, pass the ``--hard`` parameter, as follows:
-
-.. code-block:: console
-
- $ openstack server reboot --hard SERVER
-
-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.
-
-.. note::
-
- 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.
-
-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.
-
-To perform an instance reboot into rescue mode, run the following
-command:
-
-.. code-block:: console
-
- $ openstack server rescue SERVER
-
-.. note::
-
- On running the :command:`openstack server 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 operating system is allowed to complete the shutdown.
- The default timeout is 60 seconds. See `Description of
- Compute configuration options
- `_
- for details.
-
- 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.
-
-To restart the instance from the normal boot disk, run the following
-command:
-
-.. code-block:: console
-
- $ openstack server unrescue SERVER
-
-If you want to rescue an instance with a specific image, rather than the
-default one, use the ``--image`` parameter:
-
-.. code-block:: console
-
- $ nova rescue --image IMAGE_ID SERVER
diff --git a/doc/user-guide/source/cli-search-instance-with-ip-address.rst b/doc/user-guide/source/cli-search-instance-with-ip-address.rst
deleted file mode 100644
index 7d475cdb67..0000000000
--- a/doc/user-guide/source/cli-search-instance-with-ip-address.rst
+++ /dev/null
@@ -1,21 +0,0 @@
-=======================================
-Search for an instance using IP address
-=======================================
-
-You can search for an instance using the IP address parameter, ``--ip``,
-with the :command:`openstack server list` command.
-
-.. code-block:: console
-
- $ openstack server list --ip IP_ADDRESS
-
-The following example shows the results of a search on ``10.0.0.4``.
-
-.. code-block:: console
-
- $ openstack server list --ip 10.0.0.4
- +------------------+----------------------+--------+------------+-------------+------------------+------------+
- | ID | Name | Status | Task State | Power State | Networks | Image Name |
- +------------------+----------------------+--------+------------+-------------+------------------+------------+
- | 8a99547e-7385... | myInstanceFromVolume | ACTIVE | None | Running | private=10.0.0.4 | cirros |
- +------------------+----------------------+--------+------------+-------------+------------------+------------+
diff --git a/doc/user-guide/source/cli-stop-and-start-an-instance.rst b/doc/user-guide/source/cli-stop-and-start-an-instance.rst
deleted file mode 100644
index 5f76b897fd..0000000000
--- a/doc/user-guide/source/cli-stop-and-start-an-instance.rst
+++ /dev/null
@@ -1,92 +0,0 @@
-==========================
-Stop and start an instance
-==========================
-
-Use one of the following methods to stop and start an instance.
-
-Pause and unpause an instance
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-To pause an instance, run the following command:
-
-.. code-block:: console
-
- $ openstack server pause INSTANCE_NAME
-
-This command stores the state of the VM in RAM. A paused instance
-continues to run in a frozen state.
-
-To unpause an instance, run the following command:
-
-.. code-block:: console
-
- $ openstack server unpause INSTANCE_NAME
-
-Suspend and resume an instance
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-To initiate a hypervisor-level suspend operation, run the following
-command:
-
-.. code-block:: console
-
- $ openstack server suspend INSTANCE_NAME
-
-To resume a suspended instance, run the following command:
-
-.. code-block:: console
-
- $ openstack server resume INSTANCE_NAME
-
-Shelve and unshelve an instance
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-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.
-
-You can run the following shelving tasks:
-
-- 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.
-
-.. code-block:: console
-
- $ openstack server shelve SERVERNAME
-
-.. note::
-
- By default, the :command:`openstack server shelve` command gives the guest
- operating system a chance to perform a controlled shutdown before the
- instance is powered off. The shutdown behavior is configured by the
- ``shutdown_timeout`` parameter that can be set in the
- :file:`nova.conf` file. Its value stands for the overall
- period (in seconds) a guest operating system is allowed
- to complete the shutdown. The default timeout is 60 seconds.
- See `Description of Compute configuration options
- `_
- for details.
-
- 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.
-
-- Unshelve an instance - Restores the instance.
-
-.. code-block:: console
-
- $ openstack server unshelve SERVERNAME
-
-- 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.
-
-.. code-block:: console
-
- $ nova shelve-offload SERVERNAME
diff --git a/doc/user-guide/source/cli-swift-archive-auto-extract.rst b/doc/user-guide/source/cli-swift-archive-auto-extract.rst
deleted file mode 100644
index 49ec9c1031..0000000000
--- a/doc/user-guide/source/cli-swift-archive-auto-extract.rst
+++ /dev/null
@@ -1,132 +0,0 @@
-.. _archive-auto-extract:
-
-==========================
-Auto-extract archive files
-==========================
-
-To discover whether your Object Storage system supports this feature,
-see :ref:`discoverability`. Alternatively, check with your service
-provider.
-
-Use the auto-extract archive feature to upload a tar archive file.
-
-The Object Storage system extracts files from the archive file and
-creates an object.
-
-Auto-extract archive request
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-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.
-
-Valid values for the ``format`` variable are ``tar``, ``tar.gz``, or
-``tar.bz2``.
-
-The path you specify in the ``PUT`` request is used for the location of
-the object and the prefix for the resulting object names.
-
-In the ``PUT`` request, you can specify the path for:
-
-- An account
-
-- Optionally, a specific container
-
-- Optionally, a specific object prefix
-
-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.
-
-Create an archive for auto-extract
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-You must use the tar utility to create the tar archive file.
-
-You can upload regular files but you cannot upload other items (for
-example, empty directories or symbolic links).
-
-You must UTF-8-encode the member names.
-
-The archive auto-extract feature supports these formats:
-
-- The POSIX.1-1988 Ustar format.
-
-- The GNU tar format. Includes the long name, long link, and sparse
- extensions.
-
-- The POSIX.1-2001 pax format.
-
- Use gzip or bzip2 to compress the archive.
-
- Use the ``extract-archive`` query parameter to specify the format.
- Valid values for this parameter are ``tar``, ``tar.gz``, or
- ``tar.bz2``.
-
-Auto-extract archive response
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-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.
-
-You can set the ``Accept`` request header to one of these values to
-define the response format:
-
-``text/plain``
- Formats response as plain text. If you omit the ``Accept`` header,
- ``text/plain`` is the default.
-
-``application/json``
- Formats response as JSON.
-
-``application/xml``
- Formats response as XML.
-
-``text/xml``
- Formats response as XML.
-
-The following auto-extract archive files example shows a ``text/plain``
-response body where no failures occurred:
-
-.. code-block:: console
-
- Number Files Created: 10
- Errors:
-
-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.
-
-.. code-block:: console
-
- Number Files Created: 8
- Errors:
- /v1/12345678912345/mycontainer/home/xx%3Cyy, 400 Bad Request
- /v1/12345678912345/mycontainer/../image.gif, 400 Bad Request
-
-The following example shows the failure response in ``application/json``
-format.
-
-.. code-block:: json
-
- {
- "Number Files Created":1,
- "Errors":[
- [
- "/v1/12345678912345/mycontainer/home/xx%3Cyy",
- "400 Bad Request"
- ],
- [
- "/v1/12345678912345/mycontainer/../image.gif",
- "400 Bad Request"
- ]
- ]
- }
-
diff --git a/doc/user-guide/source/cli-swift-bulk-delete.rst b/doc/user-guide/source/cli-swift-bulk-delete.rst
deleted file mode 100644
index 367eed3aa8..0000000000
--- a/doc/user-guide/source/cli-swift-bulk-delete.rst
+++ /dev/null
@@ -1,93 +0,0 @@
-.. _bulk-delete:
-
-===========
-Bulk delete
-===========
-
-To discover whether your Object Storage system supports this feature,
-see :ref:`discoverability`. Alternatively, check with your service provider.
-
-With bulk delete, you can delete up to 10,000 objects or containers
-(configurable) in one request.
-
-Bulk delete request
-~~~~~~~~~~~~~~~~~~~
-
-To perform a bulk delete operation, add the ``bulk-delete`` query
-parameter to the path of a ``POST`` or ``DELETE`` operation.
-
-.. note::
-
- The ``DELETE`` operation is supported for backwards compatibility.
-
-The path is the account, such as ``/v1/12345678912345``, that contains
-the objects and containers.
-
-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.
-
-In addition, you must:
-
-- UTF-8-encode and then URL-encode the names.
-
-- To indicate an object, specify the container and object name as:
- ``CONTAINER_NAME``/``OBJECT_NAME``.
-
-- 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.
-
-- Set the ``Content-Type`` request header to ``text/plain``.
-
-Bulk delete response
-~~~~~~~~~~~~~~~~~~~~
-
-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.
-
-You can set the ``Accept`` request header to one of the following values
-to define the response format:
-
-``text/plain``
- Formats response as plain text. If you omit the
- ``Accept`` header, ``text/plain`` is the default.
-
-``application/json``
- Formats response as JSON.
-
-``application/xml`` or ``text/xml``
- Formats response as XML.
-
-The response body contains the following information:
-
-- The number of files actually deleted.
-
-- The number of not found objects.
-
-- 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.
-
-The following bulk delete response is in ``application/xml`` format. In
-this example, the ``mycontainer`` container is not empty, so it cannot
-be deleted.
-
-.. code-block:: xml
-
-
- 2
- 4
-
-
-
-
-
diff --git a/doc/user-guide/source/cli-swift-create-containers.rst b/doc/user-guide/source/cli-swift-create-containers.rst
deleted file mode 100644
index 8a19f70329..0000000000
--- a/doc/user-guide/source/cli-swift-create-containers.rst
+++ /dev/null
@@ -1,53 +0,0 @@
-============================
-Create and manage containers
-============================
-
-- To create a container, run the following command and replace
- ``CONTAINER`` with the name of your container.
-
- .. code-block:: console
-
- $ swift post CONTAINER
-
-- To list all containers, run the following command:
-
- .. code-block:: console
-
- $ swift list
-
-- To check the status of containers, run the following command:
-
- .. code-block:: console
-
- $ swift stat
-
- .. code-block:: console
-
- Account: AUTH_7b5970fbe7724bf9b74c245e77c03bcg
- Containers: 2
- Objects: 3
- Bytes: 268826
- Accept-Ranges: bytes
- X-Timestamp: 1392683866.17952
- Content-Type: text/plain; charset=utf-8
-
- You can also use the :command:`swift stat` command with the ``ACCOUNT`` or
- ``CONTAINER`` names as parameters.
-
- .. code-block:: console
-
- $ swift stat CONTAINER
-
- .. code-block:: console
-
- Account: AUTH_7b5970fbe7724bf9b74c245e77c03bcg
- Container: storage1
- Objects: 2
- Bytes: 240221
- Read ACL:
- Write ACL:
- Sync To:
- Sync Key:
- Accept-Ranges: bytes
- X-Timestamp: 1392683866.20180
- Content-Type: text/plain; charset=utf-8
diff --git a/doc/user-guide/source/cli-swift-discoverability.rst b/doc/user-guide/source/cli-swift-discoverability.rst
deleted file mode 100644
index 74047046ff..0000000000
--- a/doc/user-guide/source/cli-swift-discoverability.rst
+++ /dev/null
@@ -1,49 +0,0 @@
-.. _discoverability:
-
-===============
-Discoverability
-===============
-
-Your Object Storage system might not enable all features that this
-document describes. These features are:
-
-* :ref:`large-object-creation`
-* :ref:`archive-auto-extract`
-* :ref:`bulk-delete`
-* :ref:`static-website`
-
-To discover which features are enabled in your Object Storage system,
-use the ``/info`` request.
-
-To use the ``/info`` request, send a ``GET`` request using the ``/info``
-path to the Object Store endpoint as shown in this example:
-
-.. code-block:: console
-
- $ curl https://storage.example.com/info
-
-This example shows a truncated response body:
-
-.. code-block:: json
-
- {
- "swift":{
- "version":"1.11.0"
- },
- "staticweb":{
-
- },
- "tempurl":{
-
- }
- }
-
-This output shows that the Object Storage system has enabled the static
-website and temporary URL features.
-
-.. note::
-
- 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.
diff --git a/doc/user-guide/source/cli-swift-env-vars.rst b/doc/user-guide/source/cli-swift-env-vars.rst
deleted file mode 100644
index 3074eac634..0000000000
--- a/doc/user-guide/source/cli-swift-env-vars.rst
+++ /dev/null
@@ -1,36 +0,0 @@
-.. _env-vars:
-
-==============================================
-Environment variables required to run examples
-==============================================
-
-To run the cURL command examples for the Object Storage API requests,
-set these environment variables:
-
-publicURL
- 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``.
-
-token
- The authentication token for Object Storage.
-
-To obtain these values, run the :command:`swift stat -v` command.
-
-As shown in this example, the public URL appears in the ``StorageURL``
-field, and the token appears in the ``Auth Token`` field:
-
-.. code-block:: console
-
- StorageURL: https://23.253.72.207/v1/my_account
- Auth Token: {token}
- Account: my_account
- Containers: 2
- Objects: 3
- Bytes: 47
- Meta Book: MobyDick
- X-Timestamp: 1389453423.35964
- X-Trans-Id: txee55498935404a2caad89-0052dd3b77
- Content-Type: text/plain; charset=utf-8
- Accept-Ranges: bytes
diff --git a/doc/user-guide/source/cli-swift-large-lists.rst b/doc/user-guide/source/cli-swift-large-lists.rst
deleted file mode 100644
index 61f92500fd..0000000000
--- a/doc/user-guide/source/cli-swift-large-lists.rst
+++ /dev/null
@@ -1,103 +0,0 @@
-=================================================
-Page through large lists of containers or objects
-=================================================
-
-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.
-
-* marker
- 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.
-
-* limit
- 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.
-
-* end_marker
- 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.
-
-To page through a large list of containers
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-Assume the following list of container names:
-
-.. code-block:: console
-
- apples
- bananas
- kiwis
- oranges
- pears
-
-#. Use a ``limit`` of two:
-
- .. code-block:: console
-
- # curl -i $publicURL/?limit=2 -X GET -H "X-Auth-Token: $token"
-
- .. code-block:: console
-
- apples
- bananas
-
- Because two container names are returned, there are more names to
- list.
-
-#. Make another request with a ``marker`` parameter set to the name of
- the last item returned:
-
- .. code-block:: console
-
- # curl -i $publicURL/?limit=2&marker=bananas -X GET -H \
- “X-Auth-Token: $token"
-
- .. code-block:: console
-
- kiwis
- oranges
-
- Again, two items are returned, and there might be more.
-
-#. Make another request with a ``marker`` of the last item returned:
-
- .. code-block:: console
-
- # curl -i $publicURL/?limit=2&marker=oranges -X GET -H \”
- X-Auth-Token: $token"
-
- .. code-block:: console
-
- pears
-
- 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.
-
-#. Use the ``end_marker`` parameter to limit the result set to object
- names that are less than the ``end_marker`` parameter value:
-
- .. code-block:: console
-
- # curl -i $publicURL/?end_marker=oranges -X GET -H \”
- X-Auth-Token: $token"
-
- .. code-block:: console
-
- apples
- bananas
- kiwis
-
- You receive a result set of all container names before the
- ``end-marker`` value.
diff --git a/doc/user-guide/source/cli-swift-large-object-creation.rst b/doc/user-guide/source/cli-swift-large-object-creation.rst
deleted file mode 100644
index 5474b61c07..0000000000
--- a/doc/user-guide/source/cli-swift-large-object-creation.rst
+++ /dev/null
@@ -1,368 +0,0 @@
-.. _large-object-creation:
-
-=============
-Large objects
-=============
-
-To discover whether your Object Storage system supports this feature, see
-:ref:`discoverability` or check with your service provider.
-
-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:
-
-* ``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.
-
-* 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.
-
- 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:
-
- Static large objects
- The manifest object content is an ordered list of the names of
- the segment objects in JSON format. See :ref:`static_large_objects`.
-
- Dynamic large objects
- 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`.
-
-.. note::
-
- 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.
-
-.. _static_large_objects:
-
-Static large objects
-~~~~~~~~~~~~~~~~~~~~
-
-To create a static large object, divide your content into pieces and create
-(upload) a segment object to contain each piece.
-
-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.
-
-List the name of each segment object along with its size and MD5
-checksum in order.
-
-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.
-
-The body of the ``PUT`` request on the manifest object comprises a JSON
-list where each element contains these attributes:
-
-path
- The container and object name in the format:
- ``CONTAINER_NAME/OBJECT_NAME``.
-
-etag
- The MD5 checksum of the content of the segment object. This value
- must match the ``ETag`` of that object.
-
-size_bytes
- The size of the segment object. This value must match the
- ``Content-Length`` of that object.
-
-Static large object manifest list
----------------------------------
-
-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.
-
-.. code-block:: json
-
- [
- {
- "path": "mycontainer/objseg1",
- "etag": "0228c7926b8b642dfb29554cd1f00963",
- "size_bytes": 1468006
- },
- {
- "path": "mycontainer/pseudodir/seg-obj2",
- "etag": "5bfc9ea51a00b790717eeb934fb77b9b",
- "size_bytes": 1572864
- },
- {
- "path": "other-container/seg-final",
- "etag": "b9c3da507d2557c1ddc51f27c54bae51",
- "size_bytes": 256
- }
- ]
-
-|
-
-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.
-
-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.
-
-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.
-
-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.
-
-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.
-
-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.
-
-.. _dynamic_large_objects:
-
-Dynamic large objects
-~~~~~~~~~~~~~~~~~~~~~
-
-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.
-
-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.
-
-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.
-
-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.
-
-Upload segment of large object request: HTTP
---------------------------------------------
-
-.. code-block:: console
-
- PUT /API_VERSION/ACCOUNT/CONTAINER/OBJECT HTTP/1.1
- Host: storage.example.com
- X-Auth-Token: eaaafd18-0fed-4b3a-81b4-663c99ec1cbb
- ETag: 8a964ee2a5e88be344f36c22562a6486
- Content-Length: 1
- X-Object-Meta-PIN: 1234
-
-No response body is returned.
-
-The 2``nn`` response code indicates a successful write. ``nn`` is a value from
-00 to 99.
-
-The ``Length Required (411)`` response code indicates that the request does
-not include a required ``Content-Length`` or ``Content-Type`` header.
-
-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.
-
-You can continue to upload segments, like this example shows, before you
-upload the manifest.
-
-Upload next segment of large object request: HTTP
--------------------------------------------------
-
-.. code-block:: console
-
- PUT /API_VERSION/ACCOUNT/CONTAINER/OBJECT HTTP/1.1
- Host: storage.example.com
- X-Auth-Token: eaaafd18-0fed-4b3a-81b4-663c99ec1cbb
- ETag: 8a964ee2a5e88be344f36c22562a6486
- Content-Length: 1
- X-Object-Meta-PIN: 1234
-
-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.
-
-Upload manifest request: HTTP
------------------------------
-
-.. code-block:: console
-
- PUT /API_VERSION/ACCOUNT/CONTAINER/OBJECT HTTP/1.1
- Host: storage.clouddrive.com
- X-Auth-Token: eaaafd18-0fed-4b3a-81b4-663c99ec1cbb
- Content-Length: 0
- X-Object-Meta-PIN: 1234
- X-Object-Manifest: CONTAINER/PREFIX
-
-Upload manifest response: HTTP
-------------------------------
-.. code-block:: console
-
- [...]
-
-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.
-
-Extra transaction information
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-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.
-
-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.
-
-For example, you can include extra transaction information when you upload
-large objects such as images.
-
-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.
-
-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.
-
-Comparison of static and dynamic large objects
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-While static and dynamic objects have similar behavior, this table describes
-their differences:
-
-.. tabularcolumns:: |p{0.2\textwidth}|p{0.35\textwidth}|p{0.35\textwidth}|
-.. list-table::
- :header-rows: 1
- :widths: 20 25 25
- :stub-columns: 1
-
- * - Description
- - Static large object
- - Dynamic large object
- * - End-to-end integrity
- - 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.
- - 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.
- * - Upload order
- - You must upload the segment objects before upload the manifest
- object.
- - 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.
- * - Removal or addition of segment objects
- - 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.
- - You can upload new segment objects or remove existing segments.
- The names must simply match the ``PREFIX`` supplied in
- ``X-Object-Manifest``.
- * - Segment object size and number
- - 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).
- - Segment objects can be any size.
- * - Segment object container name
- - The manifest list includes the container name of each object.
- Segment objects can be in different containers.
- - All segment objects must be in the same container.
- * - Manifest object metadata
- - 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.
- - 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.
- * - Copying the manifest object
- - 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.
- - 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.
-
-Upload large objects with python-swiftclient
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-You can use ``python-swiftclient`` to easily upload large objects.
-
-* Upload a large file by specifying the segment size with the
- ``--segment-size`` or ``-S`` arguments:
-
- .. code-block:: console
-
- $ swift upload CONTAINER OBJECT_FILENAME --segment-size
-
- This will automatically break the file into the desired segment size
- and upload segments to a container named ``_segments``.
-
-* After upload has completed, you can download the large object as a
- single file:
-
- .. code-block:: console
-
- $ swift download CONTAINER OBJECT_FILENAME
-
-* Additional large object arguments can be found by using ``--help``:
-
- .. code-block:: console
-
- $ swift upload --help
diff --git a/doc/user-guide/source/cli-swift-manage-access-swift.rst b/doc/user-guide/source/cli-swift-manage-access-swift.rst
deleted file mode 100644
index 294de88bac..0000000000
--- a/doc/user-guide/source/cli-swift-manage-access-swift.rst
+++ /dev/null
@@ -1,91 +0,0 @@
-=============
-Manage access
-=============
-
-- 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.
-
- To give a user read access, use the :command:`swift post` command with the
- ``-r`` parameter. To give a user write access, use the
- ``-w`` parameter.
-
-- The following are examples of `read` ACLs for containers:
-
- A request with any HTTP referer header can read container contents:
-
- .. code-block:: console
-
- $ swift post CONTAINER -r ".r:*"
-
- A request with any HTTP referer header can read and list container
- contents:
-
- .. code-block:: console
-
- $ swift post CONTAINER -r ".r:*,.rlistings"
-
- A list of specific HTTP referer headers permitted to read container
- contents:
-
- .. code-block:: console
-
- $ swift post CONTAINER -r \
- ".r:openstack.example.com,.r:swift.example.com,.r:storage.example.com"
-
- A list of specific HTTP referer headers denied read access:
-
- .. code-block:: console
-
- $ swift post CONTAINER -r \
- ".r:*,.r:-openstack.example.com,.r:-swift.example.com,.r:-storage.example.com"
-
- All users residing in project1 can read container contents:
-
- .. code-block:: console
-
- $ swift post CONTAINER -r "project1:*"
-
- User1 from project1 can read container contents:
-
- .. code-block:: console
-
- $ swift post CONTAINER -r "project1:user1"
-
- A list of specific users and projects permitted to read container contents:
-
- .. code-block:: console
-
- $ swift post CONTAINER -r \
- "project1:user1,project1:user2,project3:*,project4:user1"
-
-- The following are examples of `write` ACLs for containers:
-
- All users residing in project1 can write to the container:
-
- .. code-block:: console
-
- $ swift post CONTAINER -w "project1:*"
-
- User1 from project1 can write to the container:
-
- .. code-block:: console
-
- $ swift post CONTAINER -w "project1:user1"
-
- A list of specific users and projects permitted to write to the container:
-
- .. code-block:: console
-
- $ swift post CONTAINER -w \
- "project1:user1,project1:user2,project3:*,project4:user1"
-
-.. note::
-
- To successfully write to a container, a user must have read privileges
- (in addition to write) on the container. For all aforementioned
- read/write ACL examples, one can replace the project/user name with
- project/user UUID, i.e. ``:``. If using multiple
- keystone domains, UUID format is required.
diff --git a/doc/user-guide/source/cli-swift-manage-objects.rst b/doc/user-guide/source/cli-swift-manage-objects.rst
deleted file mode 100644
index c194d88c67..0000000000
--- a/doc/user-guide/source/cli-swift-manage-objects.rst
+++ /dev/null
@@ -1,52 +0,0 @@
-==============
-Manage objects
-==============
-
-- To upload an object to a container, run the following command:
-
- .. code-block:: console
-
- $ swift upload CONTAINER OBJECT_FILENAME
-
- To upload an object in chunks, for larger than 5GB files, run the following
- command:
-
- .. code-block:: console
-
- $ swift upload -S CHUNK_SIZE CONTAINER OBJECT_FILENAME
-
- .. important::
-
- Uploading objects in chunks is mandatory if uploading an object larger
- than 5GB.
-
-- To check the status of the object, run the following command:
-
- .. code-block:: console
-
- $ swift stat CONTAINER OBJECT_FILENAME
-
- .. code-block:: console
-
- Account: AUTH_7b5970fbe7724bf9b74c245e77c03bcg
- Container: storage1
- Object: images
- Content Type: application/octet-stream
- Content Length: 211616
- Last Modified: Tue, 18 Feb 2014 00:40:36 GMT
- ETag: 82169623d55158f70a0d720f238ec3ef
- Meta Orig-Filename: images.jpg
- Accept-Ranges: bytes
- X-Timestamp: 1392684036.33306
-
-- To list the objects in a container, run the following command:
-
- .. code-block:: console
-
- $ swift list CONTAINER
-
-- To download an object from a container, run the following command:
-
- .. code-block:: console
-
- $ swift download CONTAINER OBJECT_FILENAME
diff --git a/doc/user-guide/source/cli-swift-pseudo-hierarchical-folders-directories.rst b/doc/user-guide/source/cli-swift-pseudo-hierarchical-folders-directories.rst
deleted file mode 100644
index 8101d5a5fa..0000000000
--- a/doc/user-guide/source/cli-swift-pseudo-hierarchical-folders-directories.rst
+++ /dev/null
@@ -1,151 +0,0 @@
-===========================================
-Pseudo-hierarchical folders and directories
-===========================================
-
-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.
-
-.. note::
-
- 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``.
-
-List pseudo-hierarchical folders request: HTTP
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-To display a list of all the objects in the storage container, use
-``GET`` without a ``delimiter`` or ``prefix``.
-
-.. code-block:: console
-
- $ curl -X GET -i -H "X-Auth-Token: $token" \
- $publicurl/v1/AccountString/backups
-
-The system returns status code 2xx (between 200 and 299, inclusive) and
-the requested list of the objects.
-
-.. code-block:: console
-
- photos/animals/cats/persian.jpg
- photos/animals/cats/siamese.jpg
- photos/animals/dogs/corgi.jpg
- photos/animals/dogs/poodle.jpg
- photos/animals/dogs/terrier.jpg
- photos/me.jpg
- photos/plants/fern.jpg
- photos/plants/rose.jpg
-
-Use the delimiter parameter to limit the displayed results. To use
-``delimiter`` with pseudo-directories, you must use the parameter slash
-(``/``).
-
-.. code-block:: console
-
- $ curl -X GET -i -H "X-Auth-Token: $token" \
- $publicurl/v1/AccountString/backups?delimiter=/
-
-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:
-
-.. code-block:: JSON
-
- [
- {
- "subdir": "photos/"
- }
- ]
-
- [
- {
- "subdir": "photos/animals/"
- },
- {
- "hash": "b249a153f8f38b51e92916bbc6ea57ad",
- "last_modified": "2015-12-03T17:31:28.187370",
- "bytes": 2906,
- "name": "photos/me.jpg",
- "content_type": "image/jpeg"
- },
- {
- "subdir": "photos/plants/"
- }
- ]
-
-.. code-block:: XML
-
-
-
-
- photos/
-
-
-
-
-
-
- photos/animals/
-
-
-
- photos/plants/
-
-
-
-Use the ``prefix`` and ``delimiter`` parameters to view the objects
-inside a pseudo-directory, including further nested pseudo-directories.
-
-.. code-block:: console
-
- $ curl -X GET -i -H "X-Auth-Token: $token" \
- $publicurl/v1/AccountString/backups?prefix=photos/&delimiter=/
-
-The system returns status code 2xx (between 200 and 299, inclusive) and
-the objects and pseudo-directories within the top level
-pseudo-directory.
-
-.. code-block:: console
-
- photos/animals/
- photos/me.jpg
- photos/plants/
-
-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:
-
-.. code-block:: console
-
- $ curl -X GET -i -H "X-Auth-Token: $token" \
- $publicurl/v1/AccountString/backups?prefix=photos/animals/dogs/&delimiter=/
-
-The system returns status code 2xx (between 200 and 299, inclusive) and
-the objects and pseudo-directories within the nested pseudo-directory.
-
-.. code-block:: console
-
- photos/animals/dogs/corgi.jpg
- photos/animals/dogs/poodle.jpg
- photos/animals/dogs/terrier.jpg
diff --git a/doc/user-guide/source/cli-swift-serialized-response-formats.rst b/doc/user-guide/source/cli-swift-serialized-response-formats.rst
deleted file mode 100644
index 94703769d6..0000000000
--- a/doc/user-guide/source/cli-swift-serialized-response-formats.rst
+++ /dev/null
@@ -1,124 +0,0 @@
-===========================
-Serialized response formats
-===========================
-
-By default, the Object Storage API uses a ``text/plain`` response
-format. In addition, both JSON and XML data serialization response
-formats are supported.
-
-.. note::
-
- To run the cURL command examples, you must export environment variables. For more
- information, see the section :ref:`env-vars`.
-
-To define the response format, use one of these methods:
-
-+-------------------+-------------------------------------------------------+
-|Method |Description |
-+===================+=======================================================+
-|format= ``format`` |Append this parameter to the URL for a ``GET`` request,|
-|query parameter |where ``format`` is ``json`` or ``xml``. |
-+-------------------+-------------------------------------------------------+
-|``Accept`` request |Include this header in the ``GET`` request. |
-|header |The valid header values are: |
-| | |
-| |text/plain |
-| | Plain text response format. The default. |
-| |application/jsontext |
-| | JSON data serialization response format. |
-| |application/xml |
-| | XML data serialization response format. |
-| |text/xml |
-| | XML data serialization response format. |
-+-------------------+-------------------------------------------------------+
-
-Example 1. JSON example with format query parameter
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-For example, this request uses the ``format`` query parameter to ask
-for a JSON response:
-
-.. code-block:: console
-
- $ curl -i $publicURL?format=json -X GET -H "X-Auth-Token: $token"
-
-.. code-block:: console
-
- HTTP/1.1 200 OK
- Content-Length: 96
- X-Account-Object-Count: 1
- X-Timestamp: 1389453423.35964
- X-Account-Meta-Subject: Literature
- X-Account-Bytes-Used: 14
- X-Account-Container-Count: 2
- Content-Type: application/json; charset=utf-8
- Accept-Ranges: bytes
- X-Trans-Id: tx274a77a8975c4a66aeb24-0052d95365
- Date: Fri, 17 Jan 2014 15:59:33 GMT
-
-Object Storage lists container names with additional information in JSON
-format:
-
-.. code-block:: json
-
- [
- {
- "count":0,
- "bytes":0,
- "name":"janeausten"
- },
- {
- "count":1,
- "bytes":14,
- "name":"marktwain"
- }
- ]
-
-
-Example 2. XML example with Accept header
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-This request uses the ``Accept`` request header to ask for an XML
-response:
-
-.. code-block:: console
-
- $ curl -i $publicURL -X GET -H "X-Auth-Token: $token" -H \
- ”Accept: application/xml; charset=utf-8"
-
-.. code-block:: console
-
- HTTP/1.1 200 OK
- Content-Length: 263
- X-Account-Object-Count: 3
- X-Account-Meta-Book: MobyDick
- X-Timestamp: 1389453423.35964
- X-Account-Bytes-Used: 47
- X-Account-Container-Count: 2
- Content-Type: application/xml; charset=utf-8
- Accept-Ranges: bytes
- X-Trans-Id: txf0b4c9727c3e491694019-0052e03420
- Date: Wed, 22 Jan 2014 21:12:00 GMT
-
-Object Storage lists container names with additional information in XML
-format:
-
-.. code-block:: xml
-
-
-
-
- janeausten
- 2
- 33
-
-
- marktwain
- 1
- 14
-
-
-
-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.
diff --git a/doc/user-guide/source/cli-swift-set-object-expiration.rst b/doc/user-guide/source/cli-swift-set-object-expiration.rst
deleted file mode 100644
index e101b4de5e..0000000000
--- a/doc/user-guide/source/cli-swift-set-object-expiration.rst
+++ /dev/null
@@ -1,48 +0,0 @@
-=================
-Object expiration
-=================
-
-You can schedule Object Storage (swift) objects to expire by setting the
-``X-Delete-At`` or ``X-Delete-After`` header. Once the object is deleted,
-swift will no longer serve the object and it will be deleted from the cluster
-shortly thereafter.
-
-* Set an object to expire at an absolute time (in Unix time). You
- can get the current Unix time by running ``date +'%s'``.
-
- .. code-block:: console
-
- $ swift post CONTAINER OBJECT_FILENAME -H "X-Delete-At:UNIX_TIME"
-
- Verify the ``X-Delete-At`` header has posted to the object:
-
- .. code-block:: console
-
- $ swift stat CONTAINER OBJECT_FILENAME
-
-* Set an object to expire after a relative amount of time (in seconds):
-
- .. code-block:: console
-
- $ swift post CONTAINER OBJECT_FILENAME -H "X-Delete-After:SECONDS"
-
- The ``X-Delete-After`` header will be converted to ``X-Delete-At``.
- Verify the ``X-Delete-At`` header has posted to the object:
-
- .. code-block:: console
-
- $ swift stat CONTAINER OBJECT_FILENAME
-
- If you no longer want to expire the object, you can remove the
- ``X-Delete-At`` header:
-
- .. code-block:: console
-
- $ swift post CONTAINER OBJECT_FILENAME -H "X-Remove-Delete-At:"
-
-.. note::
-
- In order for object expiration to work properly, the
- ``swift-object-expirer`` daemon will need access to all backend
- servers in the cluster. The daemon does not need access to the
- proxy-server or public network.
diff --git a/doc/user-guide/source/cli-swift-set-object-versions.rst b/doc/user-guide/source/cli-swift-set-object-versions.rst
deleted file mode 100644
index c6f57abcd1..0000000000
--- a/doc/user-guide/source/cli-swift-set-object-versions.rst
+++ /dev/null
@@ -1,217 +0,0 @@
-=================
-Object versioning
-=================
-
-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.
-
-.. note::
-
- You cannot version a large-object manifest file, but the large-object
- manifest file can point to versioned segments.
-
-We strongly recommend that you put non-current objects in a different
-container than the container where current object versions reside.
-
-To enable and use object versioning
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-#. To enable object versioning, ask your cloud provider to set the
- ``allow_versions`` option to ``TRUE`` in the container configuration
- file.
-
-#. Create an ``archive`` container to store older versions of objects:
-
- .. code-block:: console
-
- $ curl -i $publicURL/archive -X PUT -H "Content-Length: 0" -H "X-Auth-Token: $token"
-
- .. code-block:: console
-
- HTTP/1.1 201 Created
- Content-Length: 0
- Content-Type: text/html; charset=UTF-8
- X-Trans-Id: tx46f8c29050834d88b8d7e-0052e1859d
- Date: Thu, 23 Jan 2014 21:11:57 GMT
-
-#. Create a ``current`` container to store current versions of objects.
-
- 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.
-
- .. code-block:: console
-
- $ curl -i $publicURL/current -X PUT -H "Content-Length: 0" -H \
- ”X-Auth-Token: $token" -H "X-Versions-Location: archive"
-
- .. code-block:: console
-
- HTTP/1.1 201 Created
- Content-Length: 0
- Content-Type: text/html; charset=UTF-8
- X-Trans-Id: txb91810fb717347d09eec8-0052e18997
- Date: Thu, 23 Jan 2014 21:28:55 GMT
-
-#. Create the first version of an object in the ``current`` container:
-
- .. code-block:: console
-
- $ curl -i $publicURL/current/my_object --data-binary 1 -X PUT -H \
- ”Content-Length: 0" -H "X-Auth-Token: $token"
-
- .. code-block:: console
-
- HTTP/1.1 201 Created
- Last-Modified: Thu, 23 Jan 2014 21:31:22 GMT
- Content-Length: 0
- Etag: d41d8cd98f00b204e9800998ecf8427e
- Content-Type: text/html; charset=UTF-8
- X-Trans-Id: tx5992d536a4bd4fec973aa-0052e18a2a
- Date: Thu, 23 Jan 2014 21:31:22 GMT
-
- 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.
-
- These non-current versions are named as follows:
-
- .. code-block:: console
-
-
-
- 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.
-
-#. Create a second version of the object in the ``current`` container:
-
- .. code-block:: console
-
- $ curl -i $publicURL/current/my_object --data-binary 2 -X PUT -H \
- “Content-Length: 0" -H "X-Auth-Token: $token"
-
- .. code-block:: console
-
- HTTP/1.1 201 Created
- Last-Modified: Thu, 23 Jan 2014 21:41:32 GMT
- Content-Length: 0
- Etag: d41d8cd98f00b204e9800998ecf8427e
- Content-Type: text/html; charset=UTF-8
- X-Trans-Id: tx468287ce4fc94eada96ec-0052e18c8c
- Date: Thu, 23 Jan 2014 21:41:32 GMT
-
-#. 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.
-
- List older versions of the object in the ``archive`` container:
-
- .. code-block:: console
-
- $ curl -i $publicURL/archive?prefix=009my_object -X GET -H \
- "X-Auth-Token: $token"
-
- .. code-block:: console
-
- HTTP/1.1 200 OK
- Content-Length: 30
- X-Container-Object-Count: 1
- Accept-Ranges: bytes
- X-Timestamp: 1390513280.79684
- X-Container-Bytes-Used: 0
- Content-Type: text/plain; charset=utf-8
- X-Trans-Id: tx9a441884997542d3a5868-0052e18d8e
- Date: Thu, 23 Jan 2014 21:45:50 GMT
-
- 009my_object/1390512682.92052
-
- .. note::
-
- 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.
-
-#. 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.
-
- .. code-block:: console
-
- $ curl -i $publicURL/current/my_object -X DELETE -H \
- "X-Auth-Token: $token"
-
- .. code-block:: console
-
- HTTP/1.1 204 No Content
- Content-Length: 0
- Content-Type: text/html; charset=UTF-8
- X-Trans-Id: tx006d944e02494e229b8ee-0052e18edd
- Date: Thu, 23 Jan 2014 21:51:25 GMT
-
- List objects in the ``archive`` container to show that the archived
- object was moved back to the ``current`` container:
-
- .. code-block:: console
-
- $ curl -i $publicURL/archive?prefix=009my_object -X GET -H \
- "X-Auth-Token: $token"
-
- .. code-block:: console
-
- HTTP/1.1 204 No Content
- Content-Length: 0
- X-Container-Object-Count: 0
- Accept-Ranges: bytes
- X-Timestamp: 1390513280.79684
- X-Container-Bytes-Used: 0
- Content-Type: text/html; charset=UTF-8
- X-Trans-Id: tx044f2a05f56f4997af737-0052e18eed
- Date: Thu, 23 Jan 2014 21:51:41 GMT
-
- 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.
-
-#. To disable object versioning for the ``current`` container, remove
- its ``X-Versions-Location`` metadata header by sending an empty key
- value.
-
- .. code-block:: console
-
- $ curl -i $publicURL/current -X PUT -H "Content-Length: 0" -H \
- "X-Auth-Token: $token" -H "X-Versions-Location: "
-
- .. code-block:: console
-
- HTTP/1.1 202 Accepted
- Content-Length: 76
- Content-Type: text/html; charset=UTF-8
- X-Trans-Id: txe2476de217134549996d0-0052e19038
- Date: Thu, 23 Jan 2014 21:57:12 GMT
-
-
Accepted
The request is accepted for processing.
-
-Versioning with python-swiftclient
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-You can utilize ``python-swiftclient`` to enable object versioning.
-
-* Create an additional container to hold previous versions:
-
- .. code-block:: console
-
- $ swift post CONTAINER_versions
-
-* Enable object versioning on your desired container:
-
- .. code-block:: console
-
- $ swift post CONTAINER -H "X-Versions-Location:CONTAINER-versions"
diff --git a/doc/user-guide/source/cli-swift-static-website.rst b/doc/user-guide/source/cli-swift-static-website.rst
deleted file mode 100644
index b4fd617a3c..0000000000
--- a/doc/user-guide/source/cli-swift-static-website.rst
+++ /dev/null
@@ -1,125 +0,0 @@
-.. _static-website:
-
-=====================
-Create static website
-=====================
-
-To discover whether your Object Storage system supports this feature,
-see :ref:`discoverability`. Alternatively, check with your service
-provider.
-
-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.
-
-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.
-
-See the Cloud Administrator Guide for an example of the `static web configuration syntax `_.
-
-See the Cloud Administrator Guide for a complete example of the `/etc/swift/proxy-server.conf file `_
-(including static web).
-
-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`.
-
-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.
-
-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``).
-
-Static Web middleware through Object Storage
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-The following sections show how to use Static Web middleware through
-Object Storage.
-
-Make container publicly readable
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-
-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.
-
-.. code-block:: console
-
- $ swift post -r '.r:*,.rlistings' container
-
-
-Set site index file
-^^^^^^^^^^^^^^^^^^^
-
-Set the index file. In this case, ``index.html`` is the default file
-displayed when the site appears.
-
-.. code-block:: console
-
- $ swift post -m 'web-index:index.html' container
-
-Enable file listing
-^^^^^^^^^^^^^^^^^^^
-
-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.
-
-.. code-block:: console
-
- $ swift post -m 'web-listings: true' container
-
-Enable CSS for file listing
-^^^^^^^^^^^^^^^^^^^^^^^^^^^
-
-Style the file listing using a CSS.
-
-.. code-block:: console
-
- $ swift post -m 'web-listings-css:listings.css' container
-
-.. _set_error_static_website:
-
-Set error pages for static website
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-
-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``.
-
-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.
-
-You only have to set the ``X-Container-Meta-Web-Error`` metadata once
-for your entire static website.
-
-Set error pages for static website request
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-
-.. code-block:: console
-
- $ swift post -m 'web-error:error.html' container
-
-
-Any 2\ ``nn`` response indicates success.
diff --git a/doc/user-guide/source/cli-use-snapshots-to-migrate-instances.rst b/doc/user-guide/source/cli-use-snapshots-to-migrate-instances.rst
deleted file mode 100644
index 56345bcb80..0000000000
--- a/doc/user-guide/source/cli-use-snapshots-to-migrate-instances.rst
+++ /dev/null
@@ -1,139 +0,0 @@
-==================================
-Use snapshots to migrate instances
-==================================
-
-To use snapshots to migrate instances from OpenStack projects to clouds,
-complete these steps.
-
-In the source project:
-
-#. :ref:`Create_a_snapshot_of_the_instance`
-
-#. :ref:`Download_the_snapshot_as_an_image`
-
-In the destination project:
-
-#. :ref:`Import_the_snapshot_to_the_new_environment`
-
-#. :ref:`Boot_a_new_instance_from_the_snapshot`
-
-.. note::
-
- Some cloud providers allow only administrators to perform this task.
-
-.. _Create_a_snapshot_of_the_instance:
-
-Create a snapshot of the instance
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-#. 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:
-
- .. code-block:: console
-
- $ openstack server list
- +--------------------------------------+------------+--------+------------------------------+------------+
- | ID | Name | Status | Networks | Image Name |
- +--------------------------------------+------------+--------+------------------------------+------------+
- | c41f3074-c82a-4837-8673-fa7e9fea7e11 | myInstance | ACTIVE | private=10.0.0.3 | cirros |
- +--------------------------------------+------------+--------+------------------------------+------------+
-
-#. Use the :command:`openstack server stop` command to shut down the instance:
-
- .. code-block:: console
-
- $ openstack server stop myInstance
-
-#. Use the :command:`openstack server list` command to confirm that the
- instance shows a ``SHUTOFF`` status:
-
- .. code-block:: console
-
- $ openstack server list
- +--------------------------------------+------------+---------+------------------+------------+
- | ID | Name | Status | Networks | Image Name |
- +--------------------------------------+------------+---------+------------------+------------+
- | c41f3074-c82a-4837-8673-fa7e9fea7e11 | myInstance | SHUTOFF | private=10.0.0.3 | cirros |
- +--------------------------------------+------------+---------+------------------+------------+
-
-#. Use the :command:`openstack server image create` command to take a snapshot:
-
- .. code-block:: console
-
- $ openstack server image create myInstance --name myInstanceSnapshot
-
- The above command creates the image ``myInstance`` by taking a snapshot
- of a running server.
-
-#. Use the :command:`openstack image list` command to check the status
- until the status is ``active``:
-
- .. code-block:: console
-
- $ openstack image list
- +--------------------------------------+---------------------------------+--------+
- | ID | Name | Status |
- +--------------------------------------+---------------------------------+--------+
- | 657ebb01-6fae-47dc-986a-e49c4dd8c433 | cirros-0.3.5-x86_64-uec | active |
- | 72074c6d-bf52-4a56-a61c-02a17bf3819b | cirros-0.3.5-x86_64-uec-kernel | active |
- | 3c5e5f06-637b-413e-90f6-ca7ed015ec9e | cirros-0.3.5-x86_64-uec-ramdisk | active |
- | f30b204e-1ce6-40e7-b8d9-b353d4d84e7d | myInstanceSnapshot | active |
- +--------------------------------------+---------------------------------+--------+
-
-.. _Download_the_snapshot_as_an_image:
-
-Download the snapshot as an image
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-#. Get the image ID:
-
- .. code-block:: console
-
- $ openstack image list
- +-------------------+-------------------+--------+
- | ID | Name | Status |
- +-------------------+-------------------+--------+
- | f30b204e-1ce6... | myInstanceSnapshot| active |
- +-------------------+-------------------+--------+
-
-#. Download the snapshot by using the image ID that was returned in the
- previous step:
-
- .. code-block:: console
-
- $ openstack image save --file snapshot.raw f30b204e-1ce6-40e7-b8d9-b353d4d84e7d
-
- .. note::
-
- The :command:`openstack image save` command requires the image ID or
- the image name.
- Check there is sufficient space on the destination file system for
- the image file.
-
-#. Make the image available to the new environment, either through HTTP or
- direct upload to a machine (``scp``).
-
-.. _Import_the_snapshot_to_the_new_environment:
-
-Import the snapshot to the new environment
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-In the new project or cloud environment, import the snapshot:
-
-.. code-block:: console
-
- $ openstack image create NEW_IMAGE_NAME \
- --container-format bare --disk-format qcow2 --file IMAGE_URL
-
-.. _Boot_a_new_instance_from_the_snapshot:
-
-Boot a new instance from the snapshot
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-In the new project or cloud environment, use the snapshot to create the
-new instance:
-
-.. code-block:: console
-
- $ openstack server create --flavor m1.tiny --image myInstanceSnapshot myNewInstance
diff --git a/doc/user-guide/source/cli.rst b/doc/user-guide/source/cli.rst
deleted file mode 100644
index 36ed12bd04..0000000000
--- a/doc/user-guide/source/cli.rst
+++ /dev/null
@@ -1,27 +0,0 @@
-==============================
-OpenStack command-line clients
-==============================
-
-.. toctree::
- :maxdepth: 2
-
- common/cli-overview.rst
- common/cli-install-openstack-command-line-clients.rst
- common/cli-discover-version-number-for-a-client.rst
- common/cli-set-environment-variables-using-openstack-rc.rst
- common/cli-manage-images.rst
- cli-manage-images-curl.rst
- common/cli-manage-volumes.rst
- cli-manage-shares.rst
- cli-nova-configure-access-security-for-instances.rst
- cli-launch-instances.rst
- cli-manage-instances-hosts.rst
- cli-provide-user-data-to-instances.rst
- cli-use-snapshots-to-migrate-instances.rst
- cli-config-drive.rst
- cli-create-and-manage-networks.rst
- managing-openstack-object-storage-with-swift-cli.rst
- cli-create-and-manage-stacks.rst
- cli-ceilometer.rst
- trove-manage-db.rst
- database-module-usage.rst
diff --git a/doc/user-guide/source/common b/doc/user-guide/source/common
deleted file mode 120000
index dc879abe93..0000000000
--- a/doc/user-guide/source/common
+++ /dev/null
@@ -1 +0,0 @@
-../../common
\ No newline at end of file
diff --git a/doc/user-guide/source/conf.py b/doc/user-guide/source/conf.py
deleted file mode 100644
index 8dae14d687..0000000000
--- a/doc/user-guide/source/conf.py
+++ /dev/null
@@ -1,307 +0,0 @@
-# Licensed under the Apache License, Version 2.0 (the "License");
-# you may not use this file except in compliance with the License.
-# You may obtain a copy of the License at
-#
-# http://www.apache.org/licenses/LICENSE-2.0
-#
-# Unless required by applicable law or agreed to in writing, software
-# distributed under the License is distributed on an "AS IS" BASIS,
-# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
-# implied.
-# See the License for the specific language governing permissions and
-# limitations under the License.
-
-# This file is execfile()d with the current directory set to its
-# containing dir.
-#
-# Note that not all possible configuration values are present in this
-# autogenerated file.
-#
-# All configuration values have a default; values that are commented out
-# serve to show the default.
-
-import os
-# import sys
-
-import openstackdocstheme
-
-# If extensions (or modules to document with autodoc) are in another directory,
-# add these directories to sys.path here. If the directory is relative to the
-# documentation root, use os.path.abspath to make it absolute, like shown here.
-# sys.path.insert(0, os.path.abspath('.'))
-
-# -- General configuration ------------------------------------------------
-
-# If your documentation needs a minimal Sphinx version, state it here.
-# needs_sphinx = '1.0'
-
-# Add any Sphinx extension module names here, as strings. They can be
-# extensions coming with Sphinx (named 'sphinx.ext.*') or your custom
-# ones.
-extensions = ['openstackdocstheme']
-
-# Add any paths that contain templates here, relative to this directory.
-# templates_path = ['_templates']
-
-# The suffix of source filenames.
-source_suffix = '.rst'
-
-# The encoding of source files.
-# source_encoding = 'utf-8-sig'
-
-# The master toctree document.
-master_doc = 'index'
-
-# General information about the project.
-repository_name = "openstack/openstack-manuals"
-bug_project = 'openstack-manuals'
-project = u'End User Guide'
-bug_tag = u'user-guide'
-
-copyright = u'2015-2017, OpenStack contributors'
-
-# The version info for the project you're documenting, acts as replacement for
-# |version| and |release|, also used in various other places throughout the
-# built documents.
-#
-# The short X.Y version.
-version = '15.0'
-# The full version, including alpha/beta/rc tags.
-release = '15.0.0'
-
-# The language for content autogenerated by Sphinx. Refer to documentation
-# for a list of supported languages.
-# language = None
-
-# There are two options for replacing |today|: either, you set today to some
-# non-false value, then it is used:
-# today = ''
-# Else, today_fmt is used as the format for a strftime call.
-# today_fmt = '%B %d, %Y'
-
-# List of patterns, relative to source directory, that match files and
-# directories to ignore when looking for source files.
-exclude_patterns = ['common/nova*', 'common/get-started-*']
-
-# The reST default role (used for this markup: `text`) to use for all
-# documents.
-# default_role = None
-
-# If true, '()' will be appended to :func: etc. cross-reference text.
-# add_function_parentheses = True
-
-# If true, the current module name will be prepended to all description
-# unit titles (such as .. function::).
-# add_module_names = True
-
-# If true, sectionauthor and moduleauthor directives will be shown in the
-# output. They are ignored by default.
-# show_authors = False
-
-# The name of the Pygments (syntax highlighting) style to use.
-pygments_style = 'sphinx'
-
-# A list of ignored prefixes for module index sorting.
-# modindex_common_prefix = []
-
-# If true, keep warnings as "system message" paragraphs in the built documents.
-# keep_warnings = False
-
-
-# -- Options for HTML output ----------------------------------------------
-
-# The theme to use for HTML and HTML Help pages. See the documentation for
-# a list of builtin themes.
-html_theme = 'openstackdocs'
-
-# Theme options are theme-specific and customize the look and feel of a theme
-# further. For a list of options available for each theme, see the
-# documentation.
-# html_theme_options = {}
-
-# Add any paths that contain custom themes here, relative to this directory.
-# html_theme_path = [openstackdocstheme.get_html_theme_path()]
-
-# The name for this set of Sphinx documents. If None, it defaults to
-# " v documentation".
-# html_title = None
-
-# A shorter title for the navigation bar. Default is the same as html_title.
-# html_short_title = None
-
-# The name of an image file (relative to this directory) to place at the top
-# of the sidebar.
-# html_logo = None
-
-# The name of an image file (within the static path) to use as favicon of the
-# docs. This file should be a Windows icon file (.ico) being 16x16 or 32x32
-# pixels large.
-# html_favicon = None
-
-# Add any paths that contain custom static files (such as style sheets) here,
-# relative to this directory. They are copied after the builtin static files,
-# so a file named "default.css" will overwrite the builtin "default.css".
-# html_static_path = []
-
-# Add any extra paths that contain custom files (such as robots.txt or
-# .htaccess) here, relative to this directory. These files are copied
-# directly to the root of the documentation.
-# html_extra_path = []
-
-# If not '', a 'Last updated on:' timestamp is inserted at every page bottom,
-# using the given strftime format.
-# So that we can enable "log-a-bug" links from each output HTML page, this
-# variable must be set to a format that includes year, month, day, hours and
-# minutes.
-html_last_updated_fmt = '%Y-%m-%d %H:%M'
-
-
-# If true, SmartyPants will be used to convert quotes and dashes to
-# typographically correct entities.
-# html_use_smartypants = True
-
-# Custom sidebar templates, maps document names to template names.
-# html_sidebars = {}
-
-# Additional templates that should be rendered to pages, maps page names to
-# template names.
-# html_additional_pages = {}
-
-# If false, no module index is generated.
-# html_domain_indices = True
-
-# If false, no index is generated.
-html_use_index = False
-
-# If true, the index is split into individual pages for each letter.
-# html_split_index = False
-
-# If true, links to the reST sources are added to the pages.
-html_show_sourcelink = False
-
-# If true, "Created using Sphinx" is shown in the HTML footer. Default is True.
-# html_show_sphinx = True
-
-# If true, "(C) Copyright ..." is shown in the HTML footer. Default is True.
-# html_show_copyright = True
-
-# If true, an OpenSearch description file will be output, and all pages will
-# contain a tag referring to it. The value of this option must be the
-# base URL from which the finished HTML is served.
-# html_use_opensearch = ''
-
-# This is the file name suffix for HTML files (e.g. ".xhtml").
-# html_file_suffix = None
-
-# Output file base name for HTML help builder.
-htmlhelp_basename = 'user-guide'
-
-# If true, publish source files
-html_copy_source = False
-
-# -- Options for linkcheck ------------------------------------------------
-linkcheck_ignore = [r'https://build.opensuse.org']
-
-# -- Options for LaTeX output ---------------------------------------------
-pdf_theme_path = openstackdocstheme.get_pdf_theme_path()
-openstack_logo = openstackdocstheme.get_openstack_logo_path()
-
-latex_custom_template = r"""
-\newcommand{\openstacklogo}{%s}
-\usepackage{%s}
-""" % (openstack_logo, pdf_theme_path)
-
-latex_engine = 'xelatex'
-
-latex_elements = {
- # The paper size ('letterpaper' or 'a4paper').
- 'papersize': 'a4paper',
-
- # The font size ('10pt', '11pt' or '12pt').
- 'pointsize': '11pt',
-
- #Default figure align
- 'figure_align': 'H',
-
- # Not to generate blank page after chapter
- 'classoptions': ',openany',
-
- # Additional stuff for the LaTeX preamble.
- 'preamble': latex_custom_template,
-}
-
-# Grouping the document tree into LaTeX files. List of tuples
-# (source start file, target name, title,
-# author, documentclass [howto, manual, or own class]).
-latex_documents = [
- ('index', 'UserGuide.tex', u'User Guide',
- u'OpenStack contributors', 'manual'),
-]
-
-# The name of an image file (relative to this directory) to place at the top of
-# the title page.
-# latex_logo = None
-
-# For "manual" documents, if this is true, then toplevel headings are parts,
-# not chapters.
-# latex_use_parts = False
-
-# If true, show page references after internal links.
-# latex_show_pagerefs = False
-
-# If true, show URL addresses after external links.
-# latex_show_urls = False
-
-# Documents to append as an appendix to all manuals.
-# latex_appendices = []
-
-# If false, no module index is generated.
-# latex_domain_indices = True
-
-
-# -- Options for manual page output ---------------------------------------
-
-# One entry per manual page. List of tuples
-# (source start file, name, description, authors, manual section).
-man_pages = [
- ('index', 'userguide', u'User Guide',
- [u'OpenStack contributors'], 1)
-]
-
-# If true, show URL addresses after external links.
-# man_show_urls = False
-
-
-# -- Options for Texinfo output -------------------------------------------
-
-# Grouping the document tree into Texinfo files. List of tuples
-# (source start file, target name, title, author,
-# dir menu entry, description, category)
-texinfo_documents = [
- ('index', 'UserGuide', u'User Guide',
- u'OpenStack contributors', 'UserGuide',
- 'This guide shows OpenStack end users how to create and manage resources '
- 'in an OpenStack cloud with the OpenStack dashboard and OpenStack client '
- 'commands.', 'Miscellaneous'),
-]
-
-# Documents to append as an appendix to all manuals.
-# texinfo_appendices = []
-
-# If false, no module index is generated.
-# texinfo_domain_indices = True
-
-# How to display URL addresses: 'footnote', 'no', or 'inline'.
-# texinfo_show_urls = 'footnote'
-
-# If true, do not generate a @detailmenu in the "Top" node's menu.
-# texinfo_no_detailmenu = False
-
-# -- Options for Internationalization output ------------------------------
-locale_dirs = ['locale/']
-
-# -- Options for PDF output --------------------------------------------------
-
-pdf_documents = [
- ('index', u'UserGuides', u'End User Guide', u'OpenStack contributors')
-]
diff --git a/doc/user-guide/source/configure-access-and-security-for-instances.rst b/doc/user-guide/source/configure-access-and-security-for-instances.rst
deleted file mode 100644
index d55d07212e..0000000000
--- a/doc/user-guide/source/configure-access-and-security-for-instances.rst
+++ /dev/null
@@ -1,224 +0,0 @@
-===========================================
-Configure access and security for instances
-===========================================
-
-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.
-
-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`.
-
-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`.
-
-.. note::
-
- 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.
-
-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.
-
-.. _security_groups_add_rule:
-
-Add a rule to the default security group
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-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.
-
-This procedure can be adjusted as necessary to add additional security
-group rules to a project, if your cloud requires them.
-
-.. note::
-
- When adding a rule, you must specify the protocol used with the
- destination port or source port.
-
-#. Log in to the dashboard.
-
-#. Select the appropriate project from the drop down menu at the top left.
-
-#. 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.
-
-#. Select the default security group and click :guilabel:`Manage Rules`.
-
-#. To allow SSH access, click :guilabel:`Add Rule`.
-
-#. In the :guilabel:`Add Rule` dialog box, enter the following values:
-
- * **Rule**: ``SSH``
- * **Remote**: ``CIDR``
- * **CIDR**: ``0.0.0.0/0``
-
- .. note::
-
- To accept requests from a particular range of IP
- addresses, specify the IP address block in the
- :guilabel:`CIDR` box.
-
-#. Click :guilabel:`Add`.
-
- Instances will now have SSH port 22 open for requests from any IP
- address.
-
-#. To add an ICMP rule, click :guilabel:`Add Rule`.
-
-#. In the :guilabel:`Add Rule` dialog box, enter the following values:
-
- * **Rule**: ``All ICMP``
- * **Direction**: ``Ingress``
- * **Remote**: ``CIDR``
- * **CIDR**: ``0.0.0.0/0``
-
-#. Click :guilabel:`Add`.
-
- Instances will now accept all incoming ICMP packets.
-
-.. _keypair_add:
-
-Add a key pair
-~~~~~~~~~~~~~~
-
-Create at least one key pair for each project.
-
-
-#. Log in to the dashboard.
-
-#. Select the appropriate project from the drop down menu at the top left.
-
-#. On the :guilabel:`Project` tab, open the :guilabel:`Compute` tab and
- click :guilabel:`Access & Security` category.
-
-#. Click the :guilabel:`Key Pairs` tab, which shows the key pairs that
- are available for this project.
-
-#. Click :guilabel:`Create Key Pair`.
-
-#. In the :guilabel:`Create Key Pair` dialog box, enter a name for your
- key pair, and click :guilabel:`Create Key Pair`.
-
-#. Respond to the prompt to download the key pair.
-
-.. _dashboard_import_keypair:
-
-Import a key pair
-~~~~~~~~~~~~~~~~~
-
-#. Log in to the dashboard.
-
-#. Select the appropriate project from the drop down menu at the top left.
-
-#. On the :guilabel:`Project` tab, open the :guilabel:`Compute` tab and
- click :guilabel:`Access & Security` category.
-
-#. Click the :guilabel:`Key Pairs` tab, which shows the key pairs that
- are available for this project.
-
-#. Click :guilabel:`Import Key Pair`.
-
-#. 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`.
-
-#. Save the ``*.pem`` file locally.
-
-#. To change its permissions so that only you can read and write to the
- file, run the following command:
-
- .. code-block:: console
-
- $ chmod 0600 yourPrivateKey.pem
-
- .. note::
-
- 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 `__.
-
-#. To make the key pair known to SSH, run the :command:`ssh-add` command.
-
- .. code-block:: console
-
- $ ssh-add yourPrivateKey.pem
-
-The Compute database registers the public key of the key pair.
-
-The Dashboard lists the key pair on the :guilabel:`Access & Security` tab.
-
-Allocate a floating IP address to an instance
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-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 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.
-
-
-#. Log in to the dashboard.
-
-#. Select the appropriate project from the drop down menu at the top left.
-
-#. On the :guilabel:`Project` tab, open the :guilabel:`Compute` tab and
- click :guilabel:`Access & Security` category.
-
-#. Click the :guilabel:`Floating IPs` tab, which shows the floating IP
- addresses allocated to instances.
-
-#. Click :guilabel:`Allocate IP To Project`.
-
-#. Choose the pool from which to pick the IP address.
-
-#. Click :guilabel:`Allocate IP`.
-
-#. In the :guilabel:`Floating IPs` list, click :guilabel:`Associate`.
-
-#. In the :guilabel:`Manage Floating IP Associations` dialog box,
- choose the following options:
-
- - The :guilabel:`IP Address` field is filled automatically,
- but you can add a new IP address by clicking the
- :guilabel:`+` button.
-
- - In the :guilabel:`Port to be associated` field, select a port
- from the list.
-
- The list shows all the instances with their fixed IP addresses.
-
-#. Click :guilabel:`Associate`.
-
-.. note::
-
- To disassociate an IP address from an instance, click the
- :guilabel:`Disassociate` button.
-
-To release the floating IP address back into the floating IP pool, click
-the :guilabel:`Release Floating IP` option in the :guilabel:`Actions` column.
diff --git a/doc/user-guide/source/create-db.rst b/doc/user-guide/source/create-db.rst
deleted file mode 100644
index 30c6cd27ac..0000000000
--- a/doc/user-guide/source/create-db.rst
+++ /dev/null
@@ -1,176 +0,0 @@
-.. _create_db:
-
-============================
-Create and access a database
-============================
-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.
-
-This example shows you how to create and access a MySQL 5.5 database.
-
-Create and access a database
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-#. **Determine which flavor to use for your database**
-
- When you create a database instance, you must specify a nova flavor.
- The flavor indicates various characteristics of the instance, such as
- RAM and root volume size. You will need to create or
- obtain new nova flavors that work for databases.
-
- The first step is to list flavors by using the
- :command:`openstack flavor list` command.
-
- .. code-block:: console
-
- $ openstack flavor list
-
- Now take a look at the minimum requirements for various database
- instances:
-
- +--------------------+--------------------+--------------------+--------------------+
- | Database | RAM (MB) | Disk (GB) | VCPUs |
- +====================+====================+====================+====================+
- | MySQL | 512 | 5 | 1 |
- +--------------------+--------------------+--------------------+--------------------+
- | Cassandra | 2048 | 5 | 1 |
- +--------------------+--------------------+--------------------+--------------------+
- | MongoDB | 1024 | 5 | 1 |
- +--------------------+--------------------+--------------------+--------------------+
- | Redis | 512 | 5 | 1 |
- +--------------------+--------------------+--------------------+--------------------+
-
- - 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.
-
- - If your environment does not have a suitable flavor, an
- administrative user must create a custom flavor by using the
- :command:`openstack flavor create` command.
-
- **MySQL example.** This example creates a flavor that you can use
- with a MySQL database. This example has the following attributes:
-
- - Flavor name: ``mysql_minimum``
-
- - 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``.
-
- - RAM: ``512``
-
- - Root volume size in GB: ``5``
-
- - Virtual CPUs: ``1``
-
- .. code-block:: console
-
- $ openstack flavor create mysql-minimum --id 6 --ram 512 --disk 5 --vcpus 1
- +----------------------------+---------------+
- | Field | Value |
- +----------------------------+---------------+
- | OS-FLV-DISABLED:disabled | False |
- | OS-FLV-EXT-DATA:ephemeral | 0 |
- | disk | 5 |
- | id | 6 |
- | name | mysql-minimum |
- | os-flavor-access:is_public | True |
- | properties | |
- | ram | 512 |
- | rxtx_factor | 1.0 |
- | swap | |
- | vcpus | 1 |
- +----------------------------+---------------+
-
- .. _create-database-instance:
-
-#. **Create a database instance**
-
- This example creates a database instance with the following
- characteristics:
-
- - Name of the instance: ``mysql_instance_1``
-
- - Database flavor: ``6``
-
- In addition, this command specifies these options for the instance:
-
- - A volume size of ``5`` (5 GB).
-
- - The ``myDB`` database.
-
- - The database is based on the ``mysql`` data store and the
- ``mysql-5.5`` datastore\_version.
-
- - The ``userA`` user with the ``password`` password.
-
- .. code-block:: console
-
- $ trove create mysql_instance_1 6 --size 5 --databases myDB \
- --users userA:password --datastore_version mysql-5.5 \
- --datastore mysql
- +-------------------+---------------------------------------------------------------------------------------t-----------------------------------------------------------------------------------------------------------------+
- | Property | Value |
- +-------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
- | created | 2014-05-29T21:26:21 |
- | datastore | {u'version': u'mysql-5.5', u'type': u'mysql'} |
- | datastore_version | mysql-5.5 |
- | flavor | {u'id': u'6', u'links': [{u'href': u'https://controller:8779/v1.0/46d0bc4fc32e4b9e8520f8fc62199f58/flavors/6', u'rel': u'self'}, {u'href': u'https://controller:8779/flavors/6', u'rel': u'bookmark'}]} |
- | id | 5599dad6-731e-44df-bb60-488da3da9cfe |
- | name | mysql_instance_1 |
- | status | BUILD |
- | updated | 2014-05-29T21:26:21 |
- | volume | {u'size': 5} |
- +-------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-
-#. **Get the IP address of the database instance**
-
- First, use the :command:`trove list` command to list all instances and
- their IDs:
-
- .. code-block:: console
-
- $ trove list
- +--------------------------------------+------------------+-----------+-------------------+--------+-----------+------+
- | id | name | datastore | datastore_version | status | flavor_id | size |
- +--------------------------------------+------------------+-----------+-------------------+--------+-----------+------+
- | 5599dad6-731e-44df-bb60-488da3da9cfe | mysql_instance_1 | mysql | mysql-5.5 | BUILD | 6 | 5 |
- +--------------------------------------+------------------+-----------+-------------------+--------+-----------+------+
-
- This command returns the instance ID of your new instance.
-
- 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``.
-
- .. code-block:: console
-
- $ trove show INSTANCE_ID
-
- +-------------------+--------------------------------------+
- | Property | Value |
- +-------------------+--------------------------------------+
- | created | 2014-05-29T21:26:21 |
- | datastore | mysql |
- | datastore_version | mysql-5.5 |
- | flavor | 6 |
- | id | 5599dad6-731e-44df-bb60-488da3da9cfe |
- | ip | 172.16.200.2 |
- | name | mysql_instance_1 |
- | status | BUILD |
- | updated | 2014-05-29T21:26:54 |
- | volume | 5 |
- +-------------------+--------------------------------------+
-
- This command returns the IP address of the database instance.
-
-#. **Access the new database**
-
- 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``.
-
- .. code-block:: console
-
- $ mysql -u userA -p password -h IP_ADDRESS myDB
-
diff --git a/doc/user-guide/source/dashboard-create-networks.rst b/doc/user-guide/source/dashboard-create-networks.rst
deleted file mode 100644
index 00006e3eb0..0000000000
--- a/doc/user-guide/source/dashboard-create-networks.rst
+++ /dev/null
@@ -1,146 +0,0 @@
-==========================
-Create and manage networks
-==========================
-
-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).
-
-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 `__.
-
-Create a network
-~~~~~~~~~~~~~~~~
-
-#. Log in to the dashboard.
-
-#. Select the appropriate project from the drop down menu at the top left.
-
-#. On the :guilabel:`Project` tab, open the :guilabel:`Network` tab and
- click :guilabel:`Networks` category.
-
-#. Click :guilabel:`Create Network`.
-
-#. In the :guilabel:`Create Network` dialog box, specify the following values.
-
- :guilabel:`Network` tab
-
- :guilabel:`Network Name`: Specify a name to identify the network.
-
- :guilabel:`Shared`: Share the network with other projects. Non admin users
- are not allowed to set shared option.
-
- :guilabel:`Admin State`: The state to start the network in.
-
- :guilabel:`Create Subnet`: Select this check box to create a subnet
-
- You do not have to specify a subnet when you create a network, but if
- you do not specify a subnet, the network can not be attached to an instance.
-
- :guilabel:`Subnet` tab
-
- :guilabel:`Subnet Name`: Specify a name for the subnet.
-
- :guilabel:`Network Address`: Specify the IP address for the subnet.
-
- :guilabel:`IP Version`: Select IPv4 or IPv6.
-
- :guilabel:`Gateway IP`: Specify an IP address for a specific gateway. This
- parameter is optional.
-
- :guilabel:`Disable Gateway`: Select this check box to disable a gateway IP
- address.
-
- :guilabel:`Subnet Details` tab
-
- :guilabel:`Enable DHCP`: Select this check box to enable DHCP.
-
- :guilabel:`Allocation Pools`: Specify IP address pools.
-
- :guilabel:`DNS Name Servers`: Specify a name for the DNS server.
-
- :guilabel:`Host Routes`: Specify the IP address of host routes.
-
-#. Click :guilabel:`Create`.
-
- The dashboard shows the network on the :guilabel:`Networks` tab.
-
-Create a router
-~~~~~~~~~~~~~~~
-
-#. Log in to the dashboard.
-
-#. Select the appropriate project from the drop down menu at the top left.
-
-#. On the :guilabel:`Project` tab, open the :guilabel:`Network` tab and
- click :guilabel:`Routers` category.
-
-#. Click :guilabel:`Create Router`.
-
-#. In the :guilabel:`Create Router` dialog box, specify a name for the router
- and :guilabel:`External Network`, and click :guilabel:`Create Router`.
-
- The new router is now displayed in the :guilabel:`Routers` tab.
-
-#. To connect a private network to the newly created router, perform the
- following steps:
-
- A) On the :guilabel:`Routers` tab, click the name of the router.
-
- B) On the :guilabel:`Router Details` page, click the :guilabel:`Interfaces`
- tab, then click :guilabel:`Add Interface`.
-
- C) In the :guilabel:`Add Interface` dialog box, select a :guilabel:`Subnet`.
-
- Optionally, in the :guilabel:`Add Interface` dialog box, set an
- :guilabel:`IP Address` for the router interface for the selected subnet.
-
- 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.
-
- The :guilabel:`Router Name` and :guilabel:`Router ID` fields are
- automatically updated.
-
-#. Click :guilabel:`Add Interface`.
-
-You have successfully created the router. You can view the new topology
-from the :guilabel:`Network Topology` tab.
-
-Create a port
-~~~~~~~~~~~~~
-
-.. warning::
-
- Creating and managing ports requires administrator privileges.
- Contact an administrator before adding or changing ports.
-
-#. Log in to the dashboard.
-
-#. Select the appropriate project from the drop-down menu at the top left.
-
-#. On the :guilabel:`Admin` tab, click :guilabel:`Networks` category.
-
-#. Click on the :guilabel:`Network Name` of the network in which the port
- has to be created.
-
-#. In the :guilabel:`Create Port` dialog box, specify the following values.
-
- :guilabel:`Name`: Specify name to identify the port.
-
- :guilabel:`Device ID`: Device ID attached to the port.
-
- :guilabel:`Device Owner`: Device owner attached to the port.
-
- :guilabel:`Binding Host`: The ID of the host where the port is allocated.
-
- :guilabel:`Binding VNIC Type`: Select the VNIC type that is bound to the
- neutron port.
-
-#. Click :guilabel:`Create Port`.
-
- The new port is now displayed in the :guilabel:`Ports` list.
diff --git a/doc/user-guide/source/dashboard-databases.rst b/doc/user-guide/source/dashboard-databases.rst
deleted file mode 100644
index a6ac8dad63..0000000000
--- a/doc/user-guide/source/dashboard-databases.rst
+++ /dev/null
@@ -1,216 +0,0 @@
-===========================
-Create and manage databases
-===========================
-
-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.
-
-.. _dashboard_create_db_instance:
-
-Create a database instance
-~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-**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.
-
-#. **Configure a default datastore.**
-
- 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.
-
- #. Add the following line to ``/etc/trove/trove.conf``:
-
- .. code-block:: console
-
- default_datastore = DATASTORE_NAME
-
- 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.
-
- For example, if your MySQL data store name is set to ``mysql``,
- your entry would look like this:
-
- .. code-block:: console
-
- default_datastore = mysql
-
- #. Restart Database services on the controller node:
-
- .. code-block:: console
-
- # service trove-api restart
- # service trove-taskmanager restart
- # service trove-conductor restart
-
-#. **Verify flavor.**
-
- Make sure an appropriate flavor exists for the type of
- database instance you want.
-
-**Create database instance.** Once you have configured a default
-datastore and verified that you have an appropriate flavor, you can
-create a database instance.
-
-#. Log in to the dashboard.
-
-#. From the CURRENT PROJECT on the :guilabel:`Project` tab, select the
- appropriate project.
-
-#. 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.
-
-#. Click :guilabel:`Launch Instance`.
-
-#. In the :guilabel:`Launch Database` dialog box, specify the following values.
-
- Details
-
- :guilabel:`Database Name`: Specify a name for the database instance.
-
- :guilabel:`Flavor`: Select an appropriate flavor for the instance.
-
- :guilabel:`Volume Size`: Select a volume size. Volume size is expressed in
- GB.
-
- :guilabel:`Initialize Databases`: Initial Database
-
- Optionally provide a comma separated list of databases to create, for
- example:
-
- ``database1``, ``database2``, ``database3``
-
- :guilabel:`Initial Admin User`: Create an initial admin user. This user will
- have access to all the databases you create.
-
- :guilabel:`Password`: Specify a password associated with the initial admin
- user you just named.
-
- :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.
-
-#. Click the :guilabel:`Launch` button. The new database instance appears in
- the databases list.
-
-Backup and restore a database
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-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.
-
-This example shows you how to back up and restore a MySQL database.
-
-To backup the database instance
--------------------------------
-
-#. Log in to the dashboard.
-
-#. From the CURRENT PROJECT on the :guilabel:`Project` tab, select the
- appropriate project.
-
-#. On the :guilabel:`Project` tab, open the :guilabel:`Database` tab and
- click :guilabel:`Instances` category. This displays the existing
- instances in your system.
-
-#. Click :guilabel:`Create Backup`.
-
-#. In the :guilabel:`Backup Database` dialog box, specify the following
- values:
-
- Name
-
- Specify a name for the backup.
-
- Database Instance
-
- Select the instance you want to back up.
-
-#. Click :guilabel:`Backup`. The new backup appears in the backup list.
-
-To restore a database instance
-------------------------------
-
-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.
-
-#. Log in to the dashboard.
-
-#. From the CURRENT PROJECT on the :guilabel:`Project` tab, select the
- appropriate project.
-
-#. On the :guilabel:`Project` tab, open the :guilabel:`Database` tab and
- click :guilabel:`Backups` category. This lists the available backups.
-
-#. Check the backup you want to use and click :guilabel:`Restore Backup`.
-
-#. In the :guilabel:`Launch Database` dialog box, specify the values you
- want for the new database instance.
-
-#. Click the :guilabel:`Restore From Database` tab and make sure that this
- new instance is based on the correct backup.
-
-#. Click :guilabel:`Launch`.
-
- The new instance appears in the database instances list.
-
-Update a database instance
-~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-You can change various characteristics of a database instance,
-such as its volume size and flavor.
-
-To change the volume size of an instance
-----------------------------------------
-
-#. Log in to the dashboard.
-
-#. From the CURRENT PROJECT on the :guilabel:`Project` tab, select the
- appropriate project.
-
-#. On the :guilabel:`Project` tab, open the :guilabel:`Database` tab and
- click :guilabel:`Instances` category. This displays the existing
- instances in your system.
-
-#. Check the instance you want to work with.
- In the :guilabel:`Actions` column, expand the drop down menu
- and select :guilabel:`Resize Volume`.
-
-#. 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.
-
-#. Click :guilabel:`Resize Database Volume`.
-
-To change the flavor of an instance
------------------------------------
-
-#. Log in to the dashboard.
-
-#. From the CURRENT PROJECT on the :guilabel:`Project` tab, select the
- appropriate project.
-
-#. On the :guilabel:`Project` tab, open the :guilabel:`Database` tab and
- click :guilabel:`Instances` category. This displays the existing
- instances in your system.
-
-#. Check the instance you want to work with. In the
- :guilabel:`Actions` column, expand the drop down menu and
- select :guilabel:`Resize Instance`.
-
-#. 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.
-
-#. Click :guilabel:`Resize Database Instance`.
-
diff --git a/doc/user-guide/source/dashboard-launch-instances.rst b/doc/user-guide/source/dashboard-launch-instances.rst
deleted file mode 100644
index ed50a905c4..0000000000
--- a/doc/user-guide/source/dashboard-launch-instances.rst
+++ /dev/null
@@ -1,295 +0,0 @@
-===========================
-Launch and manage instances
-===========================
-
-Instances are virtual machines that run inside the cloud.
-You can launch an instance from the following sources:
-
-* Images uploaded to the Image service.
-
-* 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.
-
-* Instance snapshot that you took.
-
-Launch an instance
-~~~~~~~~~~~~~~~~~~
-
-#. Log in to the dashboard.
-
-#. Select the appropriate project from the drop down menu at the top left.
-
-#. On the :guilabel:`Project` tab, open the :guilabel:`Compute` tab and
- click :guilabel:`Instances` category.
-
- The dashboard shows the instances with its name, its private and
- floating IP addresses, size, status, task, power state, and so on.
-
-#. Click :guilabel:`Launch Instance`.
-
-#. In the :guilabel:`Launch Instance` dialog box, specify the following values:
-
- :guilabel:`Details` tab
-
- Instance Name
- Assign a name to the virtual machine.
-
- Availability Zone
- 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``.
-
- .. note::
-
- The name you assign here becomes the initial host name of the server.
- If the name is longer than 63 characters, the Compute service
- truncates it automatically to ensure dnsmasq works correctly.
-
- 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.
-
- Server names are not guaranteed to be unique when created so you
- could have two instances with the same host name.
-
- Count
- To launch multiple instances, enter a value greater than ``1``. The
- default is ``1``.
-
- :guilabel:`Source` tab
-
- Instance Boot Source
- Your options are:
-
- Boot from image
- If you choose this option, a new field for :guilabel:`Image Name`
- displays. You can select the image from the list.
-
- Boot from snapshot
- If you choose this option, a new field for :guilabel:`Instance
- Snapshot` displays. You can select the snapshot from the list.
-
- Boot from volume
- If you choose this option, a new field for :guilabel:`Volume`
- displays. You can select the volume from the list.
-
- Boot from image (creates a new volume)
- 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.
-
- Boot from volume snapshot (creates a new volume)
- 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.
-
- Image Name
- 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.
-
- Instance Snapshot
- 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.
-
- Volume
- 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.
-
- :guilabel:`Flavor` tab
-
- Flavor
- Specify the size of the instance to launch.
-
- .. note::
-
- 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``.
-
- :guilabel:`Networks` tab
-
- Selected Networks
- To add a network to the instance, click the :guilabel:`+` in the
- :guilabel:`Available` field.
-
- :guilabel:`Network Ports` tab
-
- Ports
- Activate the ports that you want to assign to the instance.
-
- :guilabel:`Security Groups` tab
-
- Security Groups
- Activate the security groups that you want to assign to the instance.
-
- Security groups are a kind of cloud firewall that define which
- incoming network traffic is forwarded to instances.
-
- If you have not created any security groups, you can assign
- only the default security group to the instance.
-
- :guilabel:`Key Pair` tab
-
- Key Pair
- Specify a key pair.
-
- 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.
-
- :guilabel:`Configuration` tab
-
- Customization Script Source
- Specify a customization script that runs after your instance
- launches.
-
- :guilabel:`Metadata` tab
-
- Available Metadata
- Add Metadata items to your instance.
-
-#. Click :guilabel:`Launch Instance`.
-
- The instance starts on a compute node in the cloud.
-
-.. note::
-
- 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.
-
-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.
-
-When you launch an instance from an image, OpenStack creates a local
-copy of the image on the compute node where the instance starts.
-
-For details on creating images, see `Creating images
-manually `_
-in the *OpenStack Virtual Machine Image Guide*.
-
-When you launch an instance from a volume, note the following steps:
-
-* 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.
-
- 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.
-
-* Select the volume or volume snapshot from which to boot. Enter a
- device name. Enter ``vda`` for KVM images or ``xvda`` for Xen images.
-
-.. note::
-
- When running QEMU without support for the hardware virtualization, set
- ``cpu_mode="none"`` alongside ``virt_type=qemu`` in
- ``/etc/nova/nova-compute.conf`` to solve the following error:
-
- .. code-block:: console
-
- libvirtError: unsupported configuration: CPU mode 'host-model'
- for ``x86_64`` qemu domain on ``x86_64`` host is not supported by hypervisor
-
-Connect to your instance by using SSH
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-To use SSH to connect to your instance, use the downloaded keypair
-file.
-
-.. note::
-
- The user name is ``ubuntu`` for the Ubuntu cloud images on TryStack.
-
-#. Copy the IP address for your instance.
-
-#. Use the :command:`ssh` command to make a secure connection to the instance.
- For example:
-
- .. code-block:: console
-
- $ ssh -i MyKey.pem ubuntu@10.0.0.2
-
-#. At the prompt, type ``yes``.
-
-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*.
-
-Track usage for instances
-~~~~~~~~~~~~~~~~~~~~~~~~~
-
-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.
-
-#. Log in to the dashboard.
-
-#. Select the appropriate project from the drop down menu at the top left.
-
-#. On the :guilabel:`Project` tab, open the :guilabel:`Compute` tab and
- click :guilabel:`Overview` category.
-
-#. To query the instance usage for a month, select a month and click
- :guilabel:`Submit`.
-
-#. To download a summary, click :guilabel:`Download CSV Summary`.
-
-Create an instance snapshot
-~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-#. Log in to the dashboard.
-
-#. Select the appropriate project from the drop down menu at the top left.
-
-#. On the :guilabel:`Project` tab, open the :guilabel:`Compute` tab and
- click the :guilabel:`Instances` category.
-
-#. Select the instance from which to create a snapshot.
-
-#. In the actions column, click :guilabel:`Create Snapshot`.
-
-#. In the :guilabel:`Create Snapshot` dialog box, enter a name for the
- snapshot, and click :guilabel:`Create Snapshot`.
-
- The :guilabel:`Images` category shows the instance snapshot.
-
-To launch an instance from the snapshot, select the snapshot and click
-:guilabel:`Launch`. Proceed with launching an instance.
-
-Manage an instance
-~~~~~~~~~~~~~~~~~~
-
-#. Log in to the dashboard.
-
-#. Select the appropriate project from the drop down menu at the top left.
-
-#. On the :guilabel:`Project` tab, open the :guilabel:`Compute` tab and
- click :guilabel:`Instances` category.
-
-#. Select an instance.
-
-#. In the menu list in the actions column, select the state.
-
- 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.
diff --git a/doc/user-guide/source/dashboard-log-in.rst b/doc/user-guide/source/dashboard-log-in.rst
deleted file mode 100644
index 389e0a2a63..0000000000
--- a/doc/user-guide/source/dashboard-log-in.rst
+++ /dev/null
@@ -1,284 +0,0 @@
-=======================
-Log in to the dashboard
-=======================
-
-The dashboard is generally installed on the controller node.
-
-#. 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.
-
-#. Open a web browser that has JavaScript and cookies enabled.
-
- .. note::
-
- 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 `__.
-
-#. In the address bar, enter the host name or IP address for the
- dashboard, for example, ``https://ipAddressOrHostName/``.
-
- .. note::
-
- 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.
-
-#. On the :guilabel:`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.
-
- 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.
-
- The visible tabs and functions in the dashboard depend on the access
- permissions, or roles, of the user you are logged in as.
-
- * 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.
-
- * 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.
-
-.. note::
-
- Some tabs, such as :guilabel:`Orchestration` and :guilabel:`Firewalls`,
- only appear on the dashboard if they are properly configured.
-
-.. _dashboard-project-tab:
-
-OpenStack dashboard — Project tab
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-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.
-
-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.
-
-.. figure:: figures/dashboard_project_tab.png
- :width: 100%
-
- **Figure: Project tab**
-
-From the :guilabel:`Project` tab, you can access the following categories:
-
-Compute tab
------------
-
-* :guilabel:`Overview`: View reports for the project.
-
-* :guilabel:`Instances`: View, launch, create a snapshot from, stop, pause,
- or reboot instances, or connect to them through VNC.
-
-* :guilabel:`Volumes`: Use the following tabs to complete these tasks:
-
- * :guilabel:`Volumes`: View, create, edit, and delete volumes.
-
- * :guilabel:`Volume Snapshots`: View, create, edit, and delete volume
- snapshots.
-
-* :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.
-
-* :guilabel:`Access & Security`: Use the following tabs to complete these
- tasks:
-
- * :guilabel:`Security Groups`: View, create, edit, and delete security
- groups and security group rules.
-
- * :guilabel:`Key Pairs`: View, create, edit, import, and delete key pairs.
-
- * :guilabel:`Floating IPs`: Allocate an IP address to or release it from a
- project.
-
- * :guilabel:`API Access`: View API endpoints.
-
-* :guilabel:`Shares`: Use the following tabs to complete these tasks:
-
- * :guilabel:`Shares`: View, create, manage, and delete shares.
-
- * :guilabel:`Snapshots`: View, manage, and delete volume snapshots.
-
- * :guilabel:`Share Networks`: View, manage, and delete share networks.
-
- * :guilabel:`Security Services`: View, manage, and delete security services.
-
-Network tab
------------
-
-* :guilabel:`Network Topology`: View the network topology.
-
-* :guilabel:`Networks`: Create and manage public and private networks.
-
-* :guilabel:`Routers`: Create and manage routers.
-
-* :guilabel:`Load Balancers`: Create and manage load balancers.
-
- * :guilabel:`Pools`: Add and manage pools.
-
- * :guilabel:`Members`: Add and manage members.
-
- * :guilabel:`Monitors`: Add and manage monitors.
-
-* :guilabel:`Firewalls`: Create and manage firewalls.
-
- * :guilabel:`Firewalls`: Create and manage firewalls.
-
- * :guilabel:`Firewall Policies`: Add and manage firewall policies.
-
- * :guilabel:`Firewall Rules`: Add and manage firewall rules.
-
-Orchestration tab
------------------
-
-* :guilabel:`Stacks`: Use the REST API to orchestrate multiple composite
- cloud applications.
-
-* :guilabel:`Resource Types`: Show a list of all the supported resource
- types for HOT templates.
-
-Object Store tab
-----------------
-
-* :guilabel:`Containers`: Create and manage containers and objects.
-
-.. _dashboard-admin-tab:
-
-OpenStack dashboard — Admin tab
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-Administrative users can use the :guilabel:`Admin` tab to view usage and to
-manage instances, volumes, flavors, images, networks, and so on.
-
-
-.. figure:: figures/dashboard_admin_tab.png
- :width: 100%
-
- **Figure: Admin tab**
-
-From the :guilabel:`Admin` tab, you can access the following category
-to complete these tasks:
-
-System tab
-----------
-
-* :guilabel:`Overview`: View basic reports.
-
-* :guilabel:`Resource Usage`: Use the following tabs to view the following
- usages:
-
- * :guilabel:`Usage Report`: View the usage report.
-
- * :guilabel:`Stats`: View the statistics of all resources.
-
-* :guilabel:`Hypervisors`: View the hypervisor summary.
-
-* :guilabel:`Host Aggregates`: View, create, and edit host aggregates.
- View the list of availability zones.
-
-* :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.
-
-* :guilabel:`Volumes`: Use the following tabs to complete these tasks:
-
- * :guilabel:`Volumes`: View, create, manage, and delete volumes.
-
- * :guilabel:`Volume Types`: View, create, manage, and delete volume types.
-
- * :guilabel:`Volume Snapshots`: View, manage, and delete volume snapshots.
-
-* :guilabel:`Flavors`: View, create, edit, view extra specifications for,
- and delete flavors. A flavor is the size of an instance.
-
-* :guilabel:`Images`: View, create, edit properties for, and delete custom
- images.
-
-* :guilabel:`Networks`: View, create, edit properties for, and delete
- networks.
-
-* :guilabel:`Routers`: View, create, edit properties for, and delete routers.
-
-* :guilabel:`Defaults`: View default quota values. Quotas are hard-coded in
- OpenStack Compute and define the maximum allowable size and number of
- resources.
-
-* :guilabel:`Metadata Definitions`: Import namespace and view the metadata
- information.
-
-* :guilabel:`System Information`: Use the following tabs to view the service
- information:
-
- * :guilabel:`Services`: View a list of the services.
-
- * :guilabel:`Compute Services`: View a list of all Compute services.
-
- * :guilabel:`Block Storage Services`: View a list of all Block Storage
- services.
-
- * :guilabel:`Network Agents`: View the network agents.
-
- * :guilabel:`Orchestration Services`: View a list of all Orchestration
- services.
-
-* :guilabel:`Shares`: Use the following tabs to complete these tasks:
-
- * :guilabel:`Shares`: View, create, manage, and delete shares.
-
- * :guilabel:`Snapshots`: View, manage, and delete volume snapshots.
-
- * :guilabel:`Share Networks`: View, manage, and delete share networks.
-
- * :guilabel:`Security Services`: View, manage, and delete security services.
-
- * :guilabel:`Share Types`: View, create, manage, and delete share types.
-
- * :guilabel:`Share Servers`: View, manage, and delete share servers.
-
-.. _dashboard-identity-tab:
-
-OpenStack dashboard — Identity tab
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-.. figure:: figures/dashboard_identity_tab.png
- :width: 100%
-
- **Figure:Identity tab**
-
-* :guilabel:`Projects`: View, create, assign users to, remove users from,
- and delete projects.
-
-* :guilabel:`Users`: View, create, enable, disable, and delete users.
-
-.. _dashboard-settings-tab:
-
-OpenStack dashboard — Settings tab
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-.. figure:: figures/dashboard_settings_tab.png
- :width: 100%
-
- **Figure:Settings tab**
-
-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.
-
-* :guilabel:`User Settings`: View and manage dashboard settings.
-
-* :guilabel:`Change Password`: Change the password of the user.
diff --git a/doc/user-guide/source/dashboard-manage-containers.rst b/doc/user-guide/source/dashboard-manage-containers.rst
deleted file mode 100644
index 477ac0a2d2..0000000000
--- a/doc/user-guide/source/dashboard-manage-containers.rst
+++ /dev/null
@@ -1,181 +0,0 @@
-===================================
-Create and manage object containers
-===================================
-
-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.
-
-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.
-
-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.
-
-Create a container
-~~~~~~~~~~~~~~~~~~
-
-#. Log in to the dashboard.
-
-#. Select the appropriate project from the drop down menu at the top left.
-
-#. On the :guilabel:`Project` tab, open the :guilabel:`Object Store` tab and
- click :guilabel:`Containers` category.
-
-#. Click :guilabel:`Container`.
-
-#. In the :guilabel:`Create Container` dialog box, enter a name for the
- container, and then click :guilabel:`Create`.
-
-You have successfully created a container.
-
-.. note::
-
- To delete a container, click the :guilabel:`More` button and select
- :guilabel:`Delete Container`.
-
-Upload an object
-~~~~~~~~~~~~~~~~
-
-#. Log in to the dashboard.
-
-#. Select the appropriate project from the drop down menu at the top left.
-
-#. On the :guilabel:`Project` tab, open the :guilabel:`Object Store` tab and
- click :guilabel:`Containers` category.
-
-#. Select the container in which you want to store your object.
-
-#. Click the :guilabel:`Upload File` icon.
-
- The :guilabel:`Upload File To Container: ` dialog box
- appears.
- ```` is the name of the container to which you are uploading
- the object.
-
-#. Enter a name for the object.
-
-#. Browse to and select the file that you want to upload.
-
-#. Click :guilabel:`Upload File`.
-
-You have successfully uploaded an object to the container.
-
-.. note::
-
- To delete an object, click the :guilabel:`More button` and select
- :guilabel:`Delete Object`.
-
-Manage an object
-~~~~~~~~~~~~~~~~
-
-**To edit an object**
-
-#. Log in to the dashboard.
-
-#. Select the appropriate project from the drop down menu at the top left.
-
-#. On the :guilabel:`Project` tab, open the :guilabel:`Object Store` tab and
- click :guilabel:`Containers` category.
-
-#. Select the container in which you want to store your object.
-
-#. Click the menu button and choose :guilabel:`Edit` from the dropdown list.
-
- The :guilabel:`Edit Object` dialog box is displayed.
-
-#. Browse to and select the file that you want to upload.
-
-#. Click :guilabel:`Update Object`.
-
-.. note::
-
- To delete an object, click the menu button and select
- :guilabel:`Delete Object`.
-
-**To copy an object from one container to another**
-
-#. Log in to the dashboard.
-
-#. Select the appropriate project from the drop down menu at the top left.
-
-#. On the :guilabel:`Project` tab, open the :guilabel:`Object Store` tab and
- click :guilabel:`Containers` category.
-
-#. Select the container in which you want to store your object.
-
-#. Click the menu button and choose :guilabel:`Copy` from the dropdown list.
-
-#. In the :guilabel:`Copy Object` launch dialog box, enter the following
- values:
-
- * :guilabel:`Destination Container`: Choose the destination container from
- the list.
- * :guilabel:`Path`: Specify a path in which the new copy should be stored
- inside of the selected container.
- * :guilabel:`Destination object name`: Enter a name for the object in the
- new container.
-
-#. Click :guilabel:`Copy Object`.
-
-**To create a metadata-only object without a file**
-
-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.
-
-#. Log in to the dashboard.
-
-#. Select the appropriate project from the drop down menu at the top left.
-
-#. On the :guilabel:`Project` tab, open the :guilabel:`Object Store` tab and
- click :guilabel:`Containers` category.
-
-#. Select the container in which you want to store your object.
-
-#. Click :guilabel:`Upload Object`.
-
- The :guilabel:`Upload Object To Container`: ```` dialog box is
- displayed.
-
- ```` is the name of the container to which you are uploading
- the object.
-
-#. Enter a name for the object.
-
-#. Click :guilabel:`Update Object`.
-
-**To create a pseudo-folder**
-
-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.
-
-#. Log in to the dashboard.
-
-#. Select the appropriate project from the drop down menu at the top left.
-
-#. On the :guilabel:`Project` tab, open the :guilabel:`Object Store` tab and
- click :guilabel:`Containers` category.
-
-#. Select the container in which you want to store your object.
-
-#. Click :guilabel:`Create Pseudo-folder`.
-
- The :guilabel:`Create Pseudo-Folder in Container` ```` dialog box
- is displayed. ```` is the name of the container to which you
- are uploading the object.
-
-#. Enter a name for the pseudo-folder.
-
- A slash (/) character is used as the delimiter for pseudo-folders in
- Object Storage.
-
-#. Click :guilabel:`Create`.
diff --git a/doc/user-guide/source/dashboard-manage-images.rst b/doc/user-guide/source/dashboard-manage-images.rst
deleted file mode 100644
index 2865b86a80..0000000000
--- a/doc/user-guide/source/dashboard-manage-images.rst
+++ /dev/null
@@ -1,144 +0,0 @@
-========================
-Upload and manage images
-========================
-
-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 `_.
-
-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.
-
-.. note::
-
- You can also use the :command:`openstack` and :command:`glance`
- command-line clients or the Image service to manage images.
- For more information see :doc:`../common/cli-manage-images`.
-
-Upload an image
-~~~~~~~~~~~~~~~
-
-Follow this procedure to upload an image to a project:
-
-#. Log in to the dashboard.
-
-#. Select the appropriate project from the drop down menu at the top left.
-
-#. On the :guilabel:`Project` tab, open the :guilabel:`Compute` tab and
- click :guilabel:`Images` category.
-
-#. Click :guilabel:`Create Image`.
-
- The :guilabel:`Create An Image` dialog box appears.
-
- .. figure:: figures/create_image.png
-
- **Dashboard — Create Image**
-
-#. Enter the following values:
-
- +-------------------------------+---------------------------------+
- | :guilabel:`Image Name` | Enter a name for the image. |
- +-------------------------------+---------------------------------+
- | :guilabel:`Image Description` | Enter a brief description of |
- | | the image. |
- +-------------------------------+---------------------------------+
- | :guilabel:`Image Source` | Choose the image source from |
- | | the dropdown list. Your choices |
- | | are :guilabel:`Image Location` |
- | | and :guilabel:`Image File`. |
- +-------------------------------+---------------------------------+
- | :guilabel:`Image File` or | Based on your selection for |
- | :guilabel:`Image Location` | :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. |
- +-------------------------------+---------------------------------+
- | :guilabel:`Format` | Select the image format (for |
- | | example, QCOW2) for the image. |
- +-------------------------------+---------------------------------+
- | :guilabel:`Architecture` | Specify the architecture. For |
- | | example, ``i386`` for a 32-bit |
- | | architecture or ``x86_64`` for |
- | | a 64-bit architecture. |
- +-------------------------------+---------------------------------+
- | :guilabel:`Minimum Disk (GB)` | Leave this field empty. |
- +-------------------------------+---------------------------------+
- | :guilabel:`Minimum RAM (MB)` | Leave this field empty. |
- +-------------------------------+---------------------------------+
- | :guilabel:`Copy Data` | Specify this option to copy |
- | | image data to the Image service.|
- +-------------------------------+---------------------------------+
- | :guilabel:`Visibility` | The access permission for the |
- | | image. |
- | | ``Public`` or ``Private``. |
- +-------------------------------+---------------------------------+
- | :guilabel:`Protected` | Select this check box to ensure |
- | | that only users with |
- | | permissions can delete the |
- | | image. ``Yes`` or ``No``. |
- +-------------------------------+---------------------------------+
- | :guilabel:`Image Metadata` | Specify this option to add |
- | | resource metadata. The glance |
- | | Metadata Catalog provides a list|
- | | of metadata image definitions. |
- | | (Note: Not all cloud providers |
- | | enable this feature.) |
- +-------------------------------+---------------------------------+
-
-#. Click :guilabel:`Create Image`.
-
- The image is queued to be uploaded. It might take some time before
- the status changes from Queued to Active.
-
-Update an image
-~~~~~~~~~~~~~~~
-
-Follow this procedure to update an existing image.
-
-#. Log in to the dashboard.
-
-#. Select the appropriate project from the drop down menu at the top left.
-
-#. Select the image that you want to edit.
-
-#. In the :guilabel:`Actions` column, click the menu button and then
- select :guilabel:`Edit Image` from the list.
-
-#. In the :guilabel:`Edit Image` dialog box, you can perform various
- actions. For example:
-
- * Change the name of the image.
- * Select the :guilabel:`Public` check box to make the image public.
- * Clear the :guilabel:`Public` check box to make the image private.
-
-#. Click :guilabel:`Edit Image`.
-
-Delete an image
-~~~~~~~~~~~~~~~
-
-Deletion of images is permanent and **cannot** be reversed. Only users
-with the appropriate permissions can delete images.
-
-#. Log in to the dashboard.
-
-#. Select the appropriate project from the drop down menu at the top left.
-
-#. On the :guilabel:`Project` tab, open the :guilabel:`Compute` tab and
- click :guilabel:`Images` category.
-
-#. Select the images that you want to delete.
-
-#. Click :guilabel:`Delete Images`.
-
-#. In the :guilabel:`Confirm Delete Images` dialog box, click
- :guilabel:`Delete Images` to confirm the deletion.
diff --git a/doc/user-guide/source/dashboard-manage-lbaasv2.rst b/doc/user-guide/source/dashboard-manage-lbaasv2.rst
deleted file mode 100644
index b401e5b1c8..0000000000
--- a/doc/user-guide/source/dashboard-manage-lbaasv2.rst
+++ /dev/null
@@ -1,85 +0,0 @@
-=================================
-View and manage load balancers v2
-=================================
-
-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:
-
-* Round robin: Rotates requests evenly between multiple instances.
-* Source IP: Requests from a unique source IP address are consistently
- directed to the same instance.
-* Least connections: Allocates requests to the instance with the
- least number of active connections.
-
-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.
-
-LBaaS v2 has several new concepts to understand:
-
-Load balancer
- The load balancer occupies a neutron network port and
- has an IP address assigned from a subnet.
-
-Listener
- 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.
-
-Pool
- A pool is a group of hosts that sits behind the load balancer and
- serves traffic through the load balancer.
-
-Member
- Members are the actual IP addresses that receive traffic from
- the load balancer. Members are associated with pools.
-
-Health monitor
- 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.
-
-View existing load balancers
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-#. Log in to the OpenStack dashboard.
-#. On the :guilabel:`Project` tab, open the
- :guilabel:`Network` tab, and click the
- :guilabel:`Load Balancers` category.
-
- This view shows the list of existing load balancers. To view details
- of any of the load balancers, click on the specific load balancer.
-
-Create a load balancer
-~~~~~~~~~~~~~~~~~~~~~~
-
-#. Log in to the OpenStack dashboard.
-#. On the :guilabel:`Project` tab, open the
- :guilabel:`Network` tab, and click the
- :guilabel:`Load Balancers` category.
-#. Click the :guilabel:`Create Load Balancer` button.
-
- Use the concepts described in the overview section to fill in
- the necessary information about the load balancer you want to create.
-
- 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.
-
-.. note::
- A message indicates whether the action succeeded.
-
-Delete a load balancer
-~~~~~~~~~~~~~~~~~~~~~~
-
-#. Select the load balancer you want to delete
- and click the :guilabel:`Delete Load Balancer` button.
-
- 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.
-
diff --git a/doc/user-guide/source/dashboard-manage-shares.rst b/doc/user-guide/source/dashboard-manage-shares.rst
deleted file mode 100644
index 10a4bea945..0000000000
--- a/doc/user-guide/source/dashboard-manage-shares.rst
+++ /dev/null
@@ -1,242 +0,0 @@
-=========================
-Create and manage shares
-=========================
-
-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.
-
-Create a share
-~~~~~~~~~~~~~~~
-
-#. Log in to the dashboard, choose a project, and click :guilabel:`Shares`.
-
-#. Click :guilabel:`Create Share`.
-
- In the dialog box that opens, enter or select the following values.
-
- :guilabel:`Share Name`: Specify a name for the share.
-
- :guilabel:`Description`: Optionally, provide a brief description for the
- share.
-
- :guilabel:`Share Type`: Choose a share type.
-
- :guilabel:`Size (GB)`: The size of the share in gibibytes (GiB).
-
- :guilabel:`Share Protocol`: Select NFS, CIFS, GlusterFS, or HDFS.
-
- :guilabel:`Share Network`: Choose a share network.
-
- :guilabel:`Metadata`: Enter metadata for the share creation if needed.
-
-#. Click :guilabel:`Create Share`.
-
-The dashboard shows the share on the :guilabel:`Shares` tab.
-
-Delete a share
-~~~~~~~~~~~~~~~
-
-#. Log in to the dashboard, choose a project, and click :guilabel:`Shares`.
-
-#. Select the check boxes for the shares that you want to delete.
-
-#. Click :guilabel:`Delete Shares` and confirm your choice.
-
- A message indicates whether the action was successful.
-
-Allow access
-~~~~~~~~~~~~
-
-#. Log in to the dashboard, choose a project, and click :guilabel:`Shares`.
-
-#. Go to the share that you want to allow access and choose
- :guilabel:`Manage Rules` from Actions.
-
-#. Click :guilabel:`Add rule`.
-
- :guilabel:`Access Type`: Choose ip, user, or cert.
-
- :guilabel:`Access Level`: Choose read-write or read-only.
-
- :guilabel:`Access To`: Fill in Access To field.
-
-#. Click :guilabel:`Add Rule`.
-
- A message indicates whether the action was successful.
-
-Deny access
-~~~~~~~~~~~
-
-#. Log in to the dashboard, choose a project, and click :guilabel:`Shares`.
-
-#. Go to the share that you want to deny access and choose
- :guilabel:`Manage Rules` from Actions.
-
-#. Choose the rule you want to delete.
-
-#. Click :guilabel:`Delete rule` and confirm your choice.
-
- A message indicates whether the action was successful.
-
-Edit share metadata
-~~~~~~~~~~~~~~~~~~~
-
-#. Log in to the dashboard, choose a project, and click :guilabel:`Shares`.
-
-#. Go to the share that you want to edit and choose
- :guilabel:`Edit Share Metadata` from Actions.
-
-#. :guilabel:`Metadata`: To add share metadata, use key=value. To unset
- metadata, use key.
-
-#. Click :guilabel:`Edit Share Metadata`.
-
- A message indicates whether the action was successful.
-
-Edit share
-~~~~~~~~~~
-
-#. Log in to the dashboard, choose a project, and click :guilabel:`Shares`.
-
-#. Go to the share that you want to edit and choose :guilabel:`Edit Share` from
- Actions.
-
-#. :guilabel:`Share Name`: Enter a new share name.
-
-#. :guilabel:`Description`: Enter a new description.
-
-#. Click :guilabel:`Edit Share`.
-
- A message indicates whether the action was successful.
-
-Extend share
-~~~~~~~~~~~~
-
-#. Log in to the dashboard, choose a project, and click :guilabel:`Shares`.
-
-#. Go to the share that you want to edit and choose :guilabel:`Extend Share`
- from Actions.
-
-#. :guilabel:`New Size (GB)`: Enter new size.
-
-#. Click :guilabel:`Extend Share`.
-
- A message indicates whether the action was successful.
-
-Create share network
-~~~~~~~~~~~~~~~~~~~~
-
-#. Log in to the dashboard, choose a project, click :guilabel:`Shares`,
- and click :guilabel:`Share Networks`.
-
-#. Click :guilabel:`Create Share Network`.
-
- In the dialog box that opens, enter or select the following values.
-
- :guilabel:`Name`: Specify a name for the share network.
-
- :guilabel:`Description`: Optionally, provide a brief description for the
- share network.
-
- :guilabel:`Neutron Net`: Choose a neutron network.
-
- :guilabel:`Neutron Subnet`: Choose a neutron subnet.
-
-#. Click :guilabel:`Create Share Network`.
-
-The dashboard shows the share network on the :guilabel:`Share Networks` tab.
-
-Delete a share network
-~~~~~~~~~~~~~~~~~~~~~~
-
-#. Log in to the dashboard, choose a project, click :guilabel:`Shares`, and
- click :guilabel:`Share Networks`.
-
-#. Select the check boxes for the share networks that you want to delete.
-
-#. Click :guilabel:`Delete Share Networks` and confirm your choice.
-
- A message indicates whether the action was successful.
-
-Edit share network
-~~~~~~~~~~~~~~~~~~
-
-#. Log in to the dashboard, choose a project, click :guilabel:`Shares`, and
- click :guilabel:`Share Networks`.
-
-#. Go to the share network that you want to edit and choose
- :guilabel:`Edit Share Network` from Actions.
-
-#. :guilabel:`Name`: Enter a new share network name.
-
-#. :guilabel:`Description`: Enter a new description.
-
-#. Click :guilabel:`Edit Share Network`.
-
- A message indicates whether the action was successful.
-
-Create security service
-~~~~~~~~~~~~~~~~~~~~~~~
-
-#. Log in to the dashboard, choose a project, click :guilabel:`Shares`,
- and click :guilabel:`Security Services`.
-
-#. Click :guilabel:`Create Security Service`.
-
- In the dialog box that opens, enter or select the following values.
-
- :guilabel:`Name`: Specify a name for the security service.
-
- :guilabel:`DNS IP`: Enter the DNS IP address.
-
- :guilabel:`Server`: Enter the server name.
-
- :guilabel:`Domain`: Enter the domain name.
-
- :guilabel:`User`: Enter the user name.
-
- :guilabel:`Password`: Enter the password.
-
- :guilabel:`Confirm Password`: Enter the password again to confirm.
-
- :guilabel:`Type`: Choose the type from Active Directory, LDAP, or Kerberos.
-
- :guilabel:`Description`: Optionally, provide a brief description for the
- security service.
-
-#. Click :guilabel:`Create Security Service`.
-
-The dashboard shows the security service on the :guilabel:`Security Services`
-tab.
-
-Delete a security service
-~~~~~~~~~~~~~~~~~~~~~~~~~
-
-#. Log in to the dashboard, choose a project, click :guilabel:`Shares`, and
- click :guilabel:`Security Services`.
-
-#. Select the check boxes for the security services that you want to delete.
-
-#. Click :guilabel:`Delete Security Services` and confirm your choice.
-
- A message indicates whether the action was successful.
-
-Edit security service
-~~~~~~~~~~~~~~~~~~~~~
-
-#. Log in to the dashboard, choose a project, click :guilabel:`Shares`,
- and click :guilabel:`Security Services`.
-
-#. Go to the security service that you want to edit and choose
- :guilabel:`Edit Security Service` from Actions.
-
-#. :guilabel:`Name`: Enter a new security service name.
-
-#. :guilabel:`Description`: Enter a new description.
-
-#. Click :guilabel:`Edit Security Service`.
-
- A message indicates whether the action was successful.
diff --git a/doc/user-guide/source/dashboard-manage-volumes.rst b/doc/user-guide/source/dashboard-manage-volumes.rst
deleted file mode 100644
index 8e2bf0190b..0000000000
--- a/doc/user-guide/source/dashboard-manage-volumes.rst
+++ /dev/null
@@ -1,177 +0,0 @@
-=========================
-Create and manage volumes
-=========================
-
-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.
-
-Create a volume
-~~~~~~~~~~~~~~~
-
-#. Log in to the dashboard.
-
-#. Select the appropriate project from the drop down menu at the top left.
-
-#. On the :guilabel:`Project` tab, open the :guilabel:`Compute` tab and
- click :guilabel:`Volumes` category.
-
-#. Click :guilabel:`Create Volume`.
-
- In the dialog box that opens, enter or select the following values.
-
- :guilabel:`Volume Name`: Specify a name for the volume.
-
- :guilabel:`Description`: Optionally, provide a brief description for the
- volume.
-
- :guilabel:`Volume Source`: Select one of the following options:
-
- * No source, empty volume: Creates an empty volume. An empty volume does
- not contain a file system or a partition table.
-
- * Snapshot: If you choose this option, a new field for
- :guilabel:`Use snapshot as a source` displays. You can select the
- snapshot from the list.
-
- * 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.
-
- * 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.
-
- :guilabel:`Type`: Leave this field blank.
-
- :guilabel:`Size (GB)`: The size of the volume in gibibytes (GiB).
-
- :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``.
-
-#. Click :guilabel:`Create Volume`.
-
-The dashboard shows the volume on the :guilabel:`Volumes` tab.
-
-.. _attach_a_volume_to_an_instance_dash:
-
-Attach a volume to an instance
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-After you create one or more volumes, you can attach them to instances.
-You can attach a volume to one instance at a time.
-
-#. Log in to the dashboard.
-
-#. Select the appropriate project from the drop down menu at the top left.
-
-#. On the :guilabel:`Project` tab, open the :guilabel:`Compute` tab and
- click :guilabel:`Volumes` category.
-
-#. Select the volume to add to an instance and click
- :guilabel:`Manage Attachments`.
-
-#. In the :guilabel:`Manage Volume Attachments` dialog box, select an instance.
-
-#. Enter the name of the device from which the volume is accessible by
- the instance.
-
- .. note::
-
- The actual device name might differ from the volume name because
- of hypervisor settings.
-
-#. Click :guilabel:`Attach Volume`.
-
- The dashboard shows the instance to which the volume is now attached
- and the device name.
-
-You can view the status of a volume in the Volumes tab of the dashboard.
-The volume is either Available or In-Use.
-
-Now you can log in to the instance and mount, format, and use the disk.
-
-Detach a volume from an instance
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-#. Log in to the dashboard.
-
-#. Select the appropriate project from the drop down menu at the top left.
-
-#. On the :guilabel:`Project` tab, open the :guilabel:`Compute` tab and
- click the :guilabel:`Volumes` category.
-
-#. Select the volume and click :guilabel:`Manage Attachments`.
-
-#. Click :guilabel:`Detach Volume` and confirm your changes.
-
-A message indicates whether the action was successful.
-
-Create a snapshot from a volume
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-#. Log in to the dashboard.
-
-#. Select the appropriate project from the drop down menu at the top left.
-
-#. On the :guilabel:`Project` tab, open the :guilabel:`Compute` tab and
- click :guilabel:`Volumes` category.
-
-#. Select a volume from which to create a snapshot.
-
-#. In the :guilabel:`Actions` column, click :guilabel:`Create Snapshot`.
-
-#. In the dialog box that opens, enter a snapshot name and a brief
- description.
-
-#. Confirm your changes.
-
- The dashboard shows the new volume snapshot in Volume Snapshots tab.
-
-Edit a volume
-~~~~~~~~~~~~~
-
-#. Log in to the dashboard.
-
-#. Select the appropriate project from the drop down menu at the top left.
-
-#. On the :guilabel:`Project` tab, open the :guilabel:`Compute` tab and
- click :guilabel:`Volumes` category.
-
-#. Select the volume that you want to edit.
-
-#. In the :guilabel:`Actions` column, click :guilabel:`Edit Volume`.
-
-#. In the :guilabel:`Edit Volume` dialog box, update the name and description
- of the volume.
-
-#. Click :guilabel:`Edit Volume`.
-
- .. note::
-
- 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.
-
-Delete a volume
-~~~~~~~~~~~~~~~
-
-When you delete an instance, the data in its attached volumes is not
-deleted.
-
-#. Log in to the dashboard.
-
-#. Select the appropriate project from the drop down menu at the top left.
-
-#. On the :guilabel:`Project` tab, open the :guilabel:`Compute` tab and
- click :guilabel:`Volumes` category.
-
-#. Select the check boxes for the volumes that you want to delete.
-
-#. Click :guilabel:`Delete Volumes` and confirm your choice.
-
- A message indicates whether the action was successful.
diff --git a/doc/user-guide/source/dashboard-stacks.rst b/doc/user-guide/source/dashboard-stacks.rst
deleted file mode 100644
index bf808c2eff..0000000000
--- a/doc/user-guide/source/dashboard-stacks.rst
+++ /dev/null
@@ -1,151 +0,0 @@
-========================
-Launch and manage stacks
-========================
-
-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.
-
-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.
-
-The template languages are described in the `Template Guide
-`_ in the `Heat developer documentation `_.
-
-Launch a stack
-~~~~~~~~~~~~~~
-
-#. Log in to the dashboard.
-#. Select the appropriate project from the drop down menu at the top left.
-#. On the :guilabel:`Project` tab, open the :guilabel:`Orchestration` tab and
- click :guilabel:`Stacks` category.
-#. Click :guilabel:`Launch Stack`.
-#. In the :guilabel:`Select Template` dialog box, specify the
- following values:
-
- +---------------------------------------+-------------------------------+
- | :guilabel:`Template Source` | Choose the source of the |
- | | template from the list. |
- +---------------------------------------+-------------------------------+
- | :guilabel:`Template URL/File/Data` | Depending on the source that |
- | | you select, enter the URL, |
- | | browse to the file location, |
- | | or directly include the |
- | | template. |
- +---------------------------------------+-------------------------------+
- | :guilabel:`Environment Source` | Choose the source of the |
- | | environment from the list. |
- | | The environment files contain |
- | | additional settings for the |
- | | stack. |
- +---------------------------------------+-------------------------------+
- | :guilabel:`Environment File/Data` | Depending on the source that |
- | | you select, browse to the |
- | | file location, directly |
- | | include the environment |
- +---------------------------------------+-------------------------------+
-
-#. Click :guilabel:`Next`.
-#. In the :guilabel:`Launch Stack` dialog box, specify the
- following values:
-
- +---------------------------------+---------------------------------+
- | :guilabel:`Stack Name` | Enter a name to identify |
- | | the stack. |
- +---------------------------------+---------------------------------+
- | :guilabel:`Creation Timeout` | Specify the number of minutes |
- | :guilabel:`(minutes)` | that can elapse before the |
- | | launch of the stack times out. |
- +---------------------------------+---------------------------------+
- | :guilabel:`Rollback On Failure` | Select this check box if you |
- | | want the service to roll back |
- | | changes if the stack fails to |
- | | launch. |
- +---------------------------------+---------------------------------+
- | :guilabel:`Password for user` | Specify the password that |
- | :guilabel:`"demo"` | the default user uses when the |
- | | stack is created. |
- +---------------------------------+---------------------------------+
- | :guilabel:`DBUsername` | Specify the name of the |
- | | database user. |
- +---------------------------------+---------------------------------+
- | :guilabel:`LinuxDistribution` | Specify the Linux distribution |
- | | that is used in the stack. |
- +---------------------------------+---------------------------------+
- | :guilabel:`DBRootPassword` | Specify the root password for |
- | | the database. |
- +---------------------------------+---------------------------------+
- | :guilabel:`KeyName` | Specify the name of the key pair|
- | | to use to log in to the stack. |
- +---------------------------------+---------------------------------+
- | :guilabel:`DBName` | Specify the name of the |
- | | database. |
- +---------------------------------+---------------------------------+
- | :guilabel:`DBPassword` | Specify the password of the |
- | | database. |
- +---------------------------------+---------------------------------+
- | :guilabel:`InstanceType` | Specify the flavor for the |
- | | instance. |
- +---------------------------------+---------------------------------+
-
-#. Click :guilabel:`Launch` to create a stack. The :guilabel:`Stacks`
- tab shows the stack.
-
-After the stack is created, click on the stack name to see the
-following details:
-
-Topology
- The topology of the stack.
-
-Overview
- The parameters and details of the stack.
-
-Resources
- The resources used by the stack.
-
-Events
- The events related to the stack.
-
-Template
- The template for the stack.
-
-Manage a stack
-~~~~~~~~~~~~~~
-
-#. Log in to the dashboard.
-#. Select the appropriate project from the drop down menu at the top left.
-#. On the :guilabel:`Project` tab, open the :guilabel:`Orchestration` tab and
- click :guilabel:`Stacks` category.
-#. Select the stack that you want to update.
-#. Click :guilabel:`Change Stack Template`.
-#. In the :guilabel:`Select Template` dialog box, select the
- new template source or environment source.
-#. Click :guilabel:`Next`.
-
- The :guilabel:`Update Stack Parameters` window appears.
-#. Enter new values for any parameters that you want to update.
-#. Click :guilabel:`Update`.
-
-Delete a stack
-~~~~~~~~~~~~~~
-
-When you delete a stack, you cannot undo this action.
-
-#. Log in to the dashboard.
-#. Select the appropriate project from the drop down menu at the top left.
-#. On the :guilabel:`Project` tab, open the :guilabel:`Orchestration` tab and
- click :guilabel:`Stacks` category.
-#. Select the stack that you want to delete.
-#. Click :guilabel:`Delete Stack`.
-#. In the confirmation dialog box, click :guilabel:`Delete Stack`
- to confirm the deletion.
diff --git a/doc/user-guide/source/dashboard.rst b/doc/user-guide/source/dashboard.rst
deleted file mode 100644
index e6d7c51e8a..0000000000
--- a/doc/user-guide/source/dashboard.rst
+++ /dev/null
@@ -1,25 +0,0 @@
-===================
-OpenStack dashboard
-===================
-
-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.
-
-
-.. toctree::
- :maxdepth: 2
-
- dashboard-log-in.rst
- dashboard-manage-images.rst
- configure-access-and-security-for-instances.rst
- dashboard-launch-instances.rst
- dashboard-create-networks.rst
- dashboard-manage-containers.rst
- dashboard-manage-volumes.rst
- dashboard-manage-shares.rst
- dashboard-stacks.rst
- dashboard-databases.rst
- dashboard-manage-lbaasv2.rst
-
diff --git a/doc/user-guide/source/database-module-usage.rst b/doc/user-guide/source/database-module-usage.rst
deleted file mode 100644
index f96d8c0b5f..0000000000
--- a/doc/user-guide/source/database-module-usage.rst
+++ /dev/null
@@ -1,409 +0,0 @@
-.. _database_module_usage:
-
-=====================================
-Create and use modules for a database
-=====================================
-
-To continue with this document, we recommend 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.
-
-This example shows you how to create and apply modules to a MySQL 5.6
-database and redis 3.2.6 database cluster.
-
-Create and apply a module to a mysql database
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-#. **Create the module file and trove module**
-
- If you wish to apply a module, you must create the module first
- and register it with the trove service. A user can not directly
- apply a module to a trove instance.
-
- The module created here is a demo module called ping. It is the
- basic type made for testing purposes. To create it, it is as
- simple as the following :command: ``echo`` command:
-
- .. code-block:: console
-
- $ echo "message=Module.V1" > ping1.dat
-
- You can create a test module and mysql database with the module
- applied by doing the following:
-
- .. code-block:: console
-
- $ trove module-create mymod ping ping1.dat --live_update \
- --datastore mysql
-
- +----------------------+--------------------------------------+
- | Property | Value |
- +----------------------+--------------------------------------+
- | apply_order | 5 |
- | auto_apply | False |
- | created | 2017-06-02T17:06:21 |
- | datastore | all |
- | datastore_id | None |
- | datastore_version | all |
- | datastore_version_id | None |
- | description | None |
- | id | 0065a8ed-0668-4db5-a4ad-d88d0a166388 |
- | instance_count | 2 |
- | is_admin | True |
- | live_update | True |
- | md5 | 7f700cc7b99606615f8b51946f6d3228 |
- | name | mymod |
- | priority_apply | False |
- | tenant | eac1e46e5f7840e39012aff46a92073a |
- | tenant_id | eac1e46e5f7840e39012aff46a92073a |
- | type | ping |
- | updated | 2017-06-02T17:06:21 |
- | visible | True |
- +----------------------+--------------------------------------+
-
- $ trove create myinst 15 --size 1 --module mymod --datastore mysql
-
- +-------------------------+--------------------------------------+
- | Property | Value |
- +-------------------------+--------------------------------------+
- | created | 2017-06-02T17:22:24 |
- | datastore | mysql |
- | datastore_version | 5.6 |
- | encrypted_rpc_messaging | True |
- | flavor | 15 |
- | id | 6221b30c-8292-4378-b624-c7e9b0f8ba9e |
- | name | myinst |
- | region | RegionOne |
- | server_id | None |
- | status | BUILD |
- | tenant_id | eac1e46e5f7840e39012aff46a92073a |
- | updated | 2017-06-02T17:22:24 |
- | volume | 1 |
- | volume_id | None |
- +-------------------------+--------------------------------------+
-
-.. _show_and_list_modules:
-
-#. **Show and list modules**
-
- You can view the modules on your instance by doing the following:
-
- .. code-block:: console
-
- $ trove module-query myinst
-
- +-------+------+-----------+---------+--------+-----------+------------------------+------------------------+
- | Name | Type | Datastore | Version | Status | Message | Created | Updated |
- +-------+------+-----------+---------+--------+-----------+------------------------+------------------------+
- | mymod | ping | all | all | OK | Module.V1 | 2017-06-02 17:23:40.50 | 2017-06-02 17:23:40.50 |
- +-------+------+-----------+---------+--------+-----------+------------------------+------------------------+
-
- You can count the instances each module is applied to by doing the
- following:
-
- .. code-block:: console
-
- $ trove module-instance-count mymod
-
- +-------------+---------------------+---------------------+----------------------------------+---------+-------+
- | Module Name | Min Updated Date | Max Updated Date | Module MD5 | Current | Count |
- +-------------+---------------------+---------------------+----------------------------------+---------+-------+
- | mymod | 2017-06-02T17:22:25 | 2017-06-02T17:22:25 | 7f700cc7b99606615f8b51946f6d3228 | True | 1 |
- +-------------+---------------------+---------------------+----------------------------------+---------+-------+
-
- You can list the instances that have a particular module applied
- by doing the following:
-
- .. code-block:: console
-
- $ trove module-instances mymod
-
- +--------------------------------------+--------+-----------+-------------------+--------+-----------+------+-----------+----------------------------------+
- | ID | Name | Datastore | Datastore Version | Status | Flavor ID | Size | Region | Tenant ID |
- +--------------------------------------+--------+-----------+-------------------+--------+-----------+------+-----------+----------------------------------+
- | 6221b30c-8292-4378-b624-c7e9b0f8ba9e | myinst | mysql | 5.6 | ACTIVE | 15 | 1 | RegionOne | eac1e46e5f7840e39012aff46a92073a |
- +--------------------------------------+--------+-----------+-------------------+--------+-----------+------+-----------+----------------------------------+
-
-
-Updating and creating a second module for a redis cluster
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-To update a module you should have another file ready to update the
-module with:
-
-.. code-block:: console
-
- $ echo "message=Module.V2" > ping2.dat
- $ trove module-update mymod --file ping2.dat
-
- +----------------------+--------------------------------------+
- | Property | Value |
- +----------------------+--------------------------------------+
- | apply_order | 5 |
- | auto_apply | False |
- | created | 2017-06-02T17:06:21 |
- | datastore | all |
- | datastore_id | None |
- | datastore_version | all |
- | datastore_version_id | None |
- | description | None |
- | id | 0065a8ed-0668-4db5-a4ad-d88d0a166388 |
- | is_admin | True |
- | live_update | True |
- | md5 | ba7c204979c8de54be6efb70a17d40b9 |
- | name | mymod |
- | priority_apply | False |
- | tenant | eac1e46e5f7840e39012aff46a92073a |
- | tenant_id | eac1e46e5f7840e39012aff46a92073a |
- | type | ping |
- | updated | 2017-06-02T17:56:12 |
- | visible | True |
- +----------------------+--------------------------------------+
-
-Now to show the usage with a redis cluster, create as follows:
-
-.. code-block:: console
-
- $ trove cluster-create myclust redis 3.2.6 \
- --instance=flavor=15,volume=1,module=mymod \
- --instance=flavor=15,volume=1,module=mymod \
- --instance=flavor=15,volume=1,module=mymod
-
- +-------------------+--------------------------------------+
- | Property | Value |
- +-------------------+--------------------------------------+
- | created | 2017-06-02T18:00:17 |
- | datastore | redis |
- | datastore_version | 3.2.6 |
- | id | e4d91ca6-5980-430c-94d0-bf7abc63f712 |
- | instance_count | 3 |
- | name | myclust |
- | task_description | Building the initial cluster. |
- | task_name | BUILDING |
- | updated | 2017-06-02T18:00:17 |
- +-------------------+--------------------------------------+
-
-The original :command: ``count`` command will show the first instance,
-unless the ``--include_clustered`` option is used. You can see the
-MD5 from each applied module, and you know that the single instance
-one is not current.
-
-.. code-block:: console
-
- $ trove module-instance-count mymod
-
- +-------------+---------------------+---------------------+----------------------------------+---------+-------+
- | Module Name | Min Updated Date | Max Updated Date | Module MD5 | Current | Count |
- +-------------+---------------------+---------------------+----------------------------------+---------+-------+
- | mymod | 2017-06-02T17:22:25 | 2017-06-02T17:22:25 | 7f700cc7b99606615f8b51946f6d3228 | False | 1 |
- +-------------+---------------------+---------------------+----------------------------------+---------+-------+
-
- $ trove module-instance-count mymod --include_clustered
-
- +-------------+---------------------+---------------------+----------------------------------+---------+-------+
- | Module Name | Min Updated Date | Max Updated Date | Module MD5 | Current | Count |
- +-------------+---------------------+---------------------+----------------------------------+---------+-------+
- | mymod | 2017-06-02T17:22:25 | 2017-06-02T17:22:25 | 7f700cc7b99606615f8b51946f6d3228 | False | 1 |
- | mymod | 2017-06-02T18:00:18 | 2017-06-02T18:00:18 | ba7c204979c8de54be6efb70a17d40b9 | True | 3 |
- +-------------+---------------------+---------------------+----------------------------------+---------+-------+
-
-Update the module again. By doing this, it will cause the instances
-to report their module is not current.
-
-.. code-block:: console
-
- $ echo "message=Module.V3" > ping3.dat
- $ trove module-update mymod --file ping3.dat
-
- +----------------------+--------------------------------------+
- | Property | Value |
- +----------------------+--------------------------------------+
- | apply_order | 5 |
- | auto_apply | False |
- | created | 2017-06-02T17:06:21 |
- | datastore | all |
- | datastore_id | None |
- | datastore_version | all |
- | datastore_version_id | None |
- | description | None |
- | id | 0065a8ed-0668-4db5-a4ad-d88d0a166388 |
- | is_admin | True |
- | live_update | True |
- | md5 | 869744bdd18e306a96c145df562065ab |
- | name | mymod |
- | priority_apply | False |
- | tenant | eac1e46e5f7840e39012aff46a92073a |
- | tenant_id | eac1e46e5f7840e39012aff46a92073a |
- | type | ping |
- | updated | 2017-06-02T18:06:53 |
- | visible | True |
- +----------------------+--------------------------------------+
-
- $ trove module-instance-count mymod --include_clustered
-
- +-------------+---------------------+---------------------+----------------------------------+---------+-------+
- | Module Name | Min Updated Date | Max Updated Date | Module MD5 | Current | Count |
- +-------------+---------------------+---------------------+----------------------------------+---------+-------+
- | mymod | 2017-06-02T17:22:25 | 2017-06-02T17:22:25 | 7f700cc7b99606615f8b51946f6d3228 | False | 1 |
- | mymod | 2017-06-02T18:00:18 | 2017-06-02T18:00:18 | ba7c204979c8de54be6efb70a17d40b9 | False | 3 |
- +-------------+---------------------+---------------------+----------------------------------+---------+-------+
-
-To update an instance in a cluster you can use the
-:command:`trove module-apply` command:
-
-.. code-block:: console
-
- $ trove cluster-instances myclust
-
- +--------------------------------------+------------------+-----------+------+--------+
- | ID | Name | Flavor ID | Size | Status |
- +--------------------------------------+------------------+-----------+------+--------+
- | 393462d5-906d-4214-af0d-538b7f618b2d | myclust-member-2 | 15 | 1 | ACTIVE |
- | a3fc5326-e1b6-456a-a8b1-08ad6bbb2278 | myclust-member-3 | 15 | 1 | ACTIVE |
- | cba31d4b-d038-42c2-ab03-56c6c176b49d | myclust-member-1 | 15 | 1 | ACTIVE |
- +--------------------------------------+------------------+-----------+------+--------+
-
- $ trove module-apply 393462d5-906d-4214-af0d-538b7f618b2d mymod
-
- +-------+------+-----------+---------+--------+-----------+
- | Name | Type | Datastore | Version | Status | Message |
- +-------+------+-----------+---------+--------+-----------+
- | mymod | ping | all | all | OK | Module.V3 |
- +-------+------+-----------+---------+--------+-----------+
-
- $ trove module-instance-count mymod --include_clustered
-
- +-------------+---------------------+---------------------+----------------------------------+---------+-------+
- | Module Name | Min Updated Date | Max Updated Date | Module MD5 | Current | Count |
- +-------------+---------------------+---------------------+----------------------------------+---------+-------+
- | mymod | 2017-06-02T17:22:25 | 2017-06-02T17:22:25 | 7f700cc7b99606615f8b51946f6d3228 | False | 1 |
- | mymod | 2017-06-02T18:00:18 | 2017-06-02T18:00:18 | ba7c204979c8de54be6efb70a17d40b9 | False | 2 |
- | mymod | 2017-06-02T18:18:37 | 2017-06-02T18:18:37 | 869744bdd18e306a96c145df562065ab | True | 1 |
- +-------------+---------------------+---------------------+----------------------------------+---------+-------+
-
-For variety in this example, create one more instance and module:
-
-.. code-block:: console
-
- $ trove create myinst_2 15 --size 1 --module mymod
-
- +-------------------------+--------------------------------------+
- | Property | Value |
- +-------------------------+--------------------------------------+
- | created | 2017-06-02T18:21:56 |
- | datastore | redis |
- | datastore_version | 3.2.6 |
- | encrypted_rpc_messaging | True |
- | flavor | 15 |
- | id | cdd85d94-13a0-4d90-89eb-9c05523d2ac6 |
- | name | myinst_2 |
- | region | RegionOne |
- | server_id | None |
- | status | BUILD |
- | tenant_id | eac1e46e5f7840e39012aff46a92073a |
- | updated | 2017-06-02T18:21:56 |
- | volume | 1 |
- | volume_id | None |
- +-------------------------+--------------------------------------+
-
- $ echo "message=Module.V4" > ping4.dat
- $ trove module-update mymod --file ping4.dat
-
- +----------------------+--------------------------------------+
- | Property | Value |
- +----------------------+--------------------------------------+
- | apply_order | 5 |
- | auto_apply | False |
- | created | 2017-06-02T17:06:21 |
- | datastore | all |
- | datastore_id | None |
- | datastore_version | all |
- | datastore_version_id | None |
- | description | None |
- | id | 0065a8ed-0668-4db5-a4ad-d88d0a166388 |
- | is_admin | True |
- | live_update | True |
- | md5 | 6e2c81c1547d640b4c6e7752ed0e33ab |
- | name | mymod |
- | priority_apply | False |
- | tenant | eac1e46e5f7840e39012aff46a92073a |
- | tenant_id | eac1e46e5f7840e39012aff46a92073a |
- | type | ping |
- | updated | 2017-06-02T18:26:22 |
- | visible | True |
- +----------------------+--------------------------------------+
-
-Now we have 2 single instances, and 3 cluster instances on various
-versions of the module, none current.
-
-.. code-block:: console
-
- $ trove list
-
- +--------------------------------------+----------+-----------+-------------------+--------+-----------+------+-----------+
- | ID | Name | Datastore | Datastore Version | Status | Flavor ID | Size | Region |
- +--------------------------------------+----------+-----------+-------------------+--------+-----------+------+-----------+
- | 6221b30c-8292-4378-b624-c7e9b0f8ba9e | myinst | mysql | 5.6 | ACTIVE | 15 | 1 | RegionOne |
- | cdd85d94-13a0-4d90-89eb-9c05523d2ac6 | myinst_2 | redis | 3.2.6 | ACTIVE | 15 | 1 | RegionOne |
- +--------------------------------------+----------+-----------+-------------------+--------+-----------+------+-----------+
-
- $ trove module-instance-count mymod --include_clustered
-
- +-------------+---------------------+---------------------+----------------------------------+---------+-------+
- | Module Name | Min Updated Date | Max Updated Date | Module MD5 | Current | Count |
- +-------------+---------------------+---------------------+----------------------------------+---------+-------+
- | mymod | 2017-06-02T17:22:25 | 2017-06-02T17:22:25 | 7f700cc7b99606615f8b51946f6d3228 | False | 1 |
- | mymod | 2017-06-02T18:00:18 | 2017-06-02T18:00:18 | ba7c204979c8de54be6efb70a17d40b9 | False | 2 |
- | mymod | 2017-06-02T18:18:37 | 2017-06-02T18:21:57 | 869744bdd18e306a96c145df562065ab | False | 2 |
- +-------------+---------------------+---------------------+----------------------------------+---------+-------+
-
-When the latest module was created, the ``--include_clustered`` was
-not used. Use the :command:`trove module-reapply` command:
-
-.. code-block:: console
-
- $ trove module-reapply mymod --md5=869744bdd18e306a96c145df562065ab --include_clustered
- $ trove module-instance-count mymod --include_clustered
-
- +-------------+---------------------+---------------------+----------------------------------+---------+-------+
- | Module Name | Min Updated Date | Max Updated Date | Module MD5 | Current | Count |
- +-------------+---------------------+---------------------+----------------------------------+---------+-------+
- | mymod | 2017-06-02T17:22:25 | 2017-06-02T17:22:25 | 7f700cc7b99606615f8b51946f6d3228 | False | 1 |
- | mymod | 2017-06-02T18:00:18 | 2017-06-02T18:00:18 | ba7c204979c8de54be6efb70a17d40b9 | False | 2 |
- | mymod | 2017-06-02T18:38:48 | 2017-06-02T18:38:48 | 6e2c81c1547d640b4c6e7752ed0e33ab | True | 2 |
- +-------------+---------------------+---------------------+----------------------------------+---------+-------+
-
-Now they are both updated. If the ``--force`` flag is used, it can
-reapply to already applied instances. Notice that the only thing that
-changes is the minimum and maximum updated date fields.
-
-.. code-block:: console
-
- $ trove module-reapply mymod --md5=6e2c81c1547d640b4c6e7752ed0e33ab --include_clustered --force
- $ trove module-instance-count mymod --include_clustered
-
- +-------------+---------------------+---------------------+----------------------------------+---------+-------+
- | Module Name | Min Updated Date | Max Updated Date | Module MD5 | Current | Count |
- +-------------+---------------------+---------------------+----------------------------------+---------+-------+
- | mymod | 2017-06-02T17:22:25 | 2017-06-02T17:22:25 | 7f700cc7b99606615f8b51946f6d3228 | False | 1 |
- | mymod | 2017-06-02T18:00:18 | 2017-06-02T18:00:18 | ba7c204979c8de54be6efb70a17d40b9 | False | 2 |
- | mymod | 2017-06-02T18:40:45 | 2017-06-02T18:40:46 | 6e2c81c1547d640b4c6e7752ed0e33ab | True | 2 |
- +-------------+---------------------+---------------------+----------------------------------+---------+-------+
-
-To bring every instance to the current version, use some of the
-optional arguments to control how many instances are updated at the
-same time. This is useful to avoid potential network issues, if the
-module payload is large. Since we are not using the ``--force`` flag,
-the minimum updated date will not change.
-
-.. code-block:: console
-
- $ trove module-reapply mymod --include_clustered --batch_size=1 --delay=3
- $ trove module-instance-count mymod --include_clustered
-
- +-------------+---------------------+---------------------+----------------------------------+---------+-------+
- | Module Name | Min Updated Date | Max Updated Date | Module MD5 | Current | Count |
- +-------------+---------------------+---------------------+----------------------------------+---------+-------+
- | mymod | 2017-06-02T18:40:45 | 2017-06-02T18:44:10 | 6e2c81c1547d640b4c6e7752ed0e33ab | True | 5 |
- +-------------+---------------------+---------------------+----------------------------------+---------+-------+
diff --git a/doc/user-guide/source/figures/create_image.png b/doc/user-guide/source/figures/create_image.png
deleted file mode 100644
index b07d10b92e..0000000000
Binary files a/doc/user-guide/source/figures/create_image.png and /dev/null differ
diff --git a/doc/user-guide/source/figures/dashboard_admin_tab.png b/doc/user-guide/source/figures/dashboard_admin_tab.png
deleted file mode 100644
index b26f8aca85..0000000000
Binary files a/doc/user-guide/source/figures/dashboard_admin_tab.png and /dev/null differ
diff --git a/doc/user-guide/source/figures/dashboard_identity_tab.png b/doc/user-guide/source/figures/dashboard_identity_tab.png
deleted file mode 100644
index a9c4541270..0000000000
Binary files a/doc/user-guide/source/figures/dashboard_identity_tab.png and /dev/null differ
diff --git a/doc/user-guide/source/figures/dashboard_project_tab.png b/doc/user-guide/source/figures/dashboard_project_tab.png
deleted file mode 100644
index 8b5732e7e2..0000000000
Binary files a/doc/user-guide/source/figures/dashboard_project_tab.png and /dev/null differ
diff --git a/doc/user-guide/source/figures/dashboard_settings_tab.png b/doc/user-guide/source/figures/dashboard_settings_tab.png
deleted file mode 100644
index 896609859c..0000000000
Binary files a/doc/user-guide/source/figures/dashboard_settings_tab.png and /dev/null differ
diff --git a/doc/user-guide/source/hot.rst b/doc/user-guide/source/hot.rst
deleted file mode 100644
index 1d800ee014..0000000000
--- a/doc/user-guide/source/hot.rst
+++ /dev/null
@@ -1,10 +0,0 @@
-=========
-HOT Guide
-=========
-
-Orchestration is compatible with the CloudFormation template, but you can also
-write heat templates to orchestrate cloud resources.
-
-To learn how, refer to the `Template Guide
-`__
-on the OpenStack developer documentation website.
diff --git a/doc/user-guide/source/index.rst b/doc/user-guide/source/index.rst
deleted file mode 100644
index e44dda1604..0000000000
--- a/doc/user-guide/source/index.rst
+++ /dev/null
@@ -1,29 +0,0 @@
-========================
-OpenStack End User Guide
-========================
-
-Abstract
-~~~~~~~~
-
-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.
-
-This guide documents OpenStack Ocata, Newton and Mitaka releases.
-
-Contents
-~~~~~~~~
-
-.. toctree::
- :maxdepth: 2
-
- common/conventions.rst
- intro-user.rst
- dashboard.rst
- cli.rst
- sdk.rst
- hot.rst
- cli-cheat-sheet.rst
- common/appendix.rst
diff --git a/doc/user-guide/source/intro-user.rst b/doc/user-guide/source/intro-user.rst
deleted file mode 100644
index b4d3bcf049..0000000000
--- a/doc/user-guide/source/intro-user.rst
+++ /dev/null
@@ -1,39 +0,0 @@
-=================================
-How can I use an OpenStack cloud?
-=================================
-
-As an OpenStack cloud end user, you can provision your own resources
-within the limits set by cloud administrators.
-
-The examples in this guide show you how to perform tasks by using the
-following methods:
-
-* OpenStack dashboard: Use this web-based graphical interface, code named
- `horizon `__, to view,
- create, and manage resources.
-
-* 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.
-
-You can modify these examples for your specific use cases.
-
-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 OpenStack APIs.
-
-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.
-
-Who should read this book?
-~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-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.
diff --git a/doc/user-guide/source/locale/id/LC_MESSAGES/user-guide.po b/doc/user-guide/source/locale/id/LC_MESSAGES/user-guide.po
deleted file mode 100644
index 717923d9ad..0000000000
--- a/doc/user-guide/source/locale/id/LC_MESSAGES/user-guide.po
+++ /dev/null
@@ -1,10531 +0,0 @@
-# SOME DESCRIPTIVE TITLE.
-# Copyright (C) 2015, OpenStack contributors
-# This file is distributed under the same license as the End User Guide package.
-#
-# Translators:
-# Mahardhika Gilang , 2013
-# OpenStack Infra , 2015. #zanata
-# suhartono , 2016. #zanata
-# suhartono , 2017. #zanata
-msgid ""
-msgstr ""
-"Project-Id-Version: End User Guide 15.0\n"
-"Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2017-06-21 14:03+0000\n"
-"MIME-Version: 1.0\n"
-"Content-Type: text/plain; charset=UTF-8\n"
-"Content-Transfer-Encoding: 8bit\n"
-"PO-Revision-Date: 2017-06-10 03:50+0000\n"
-"Last-Translator: suhartono \n"
-"Language: id\n"
-"Plural-Forms: nplurals=1; plural=0;\n"
-"X-Generator: Zanata 3.9.6\n"
-"Language-Team: Indonesian\n"
-
-msgid "**Access the new database**"
-msgstr "**Access the new database**"
-
-msgid ""
-"**Assumptions.** Assume that you have created a regular backup for the "
-"following database instance:"
-msgstr ""
-"**Assumptions.** Asumsikan bahwa Anda telah membuat cadangan reguler untuk "
-"database name berikut:"
-
-msgid "**Backup the database instance**"
-msgstr "**Backup the database instance** (cadangan instance database)"
-
-msgid "**Before you begin.** Make sure that:"
-msgstr "**Before you begin.** Make sure that:"
-
-msgid "**CIDR**: ``0.0.0.0/0``"
-msgstr "**CIDR**: ``0.0.0.0/0``"
-
-msgid "**Change the database configuration using a configuration group**"
-msgstr ""
-"**Change the database configuration using a configuration group** (mengubah "
-"konfigurasi database menggunakan kelompok konfigurasi)"
-
-msgid "**Clean up**"
-msgstr "**Clean up** (Membersihkan)"
-
-msgid "**Compute host requirements**"
-msgstr "**Compute host requirements** (Persyaratan host Compute)"
-
-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 ""
-"**Conclusion** (kesimpulan) Menggunakan kelompok konfigurasi untuk "
-"menetapkan opsi tunggal pada database tunggal jelas contoh sepele. Namun, "
-"kelompok konfigurasi dapat memberikan efisiensi besar ketika Anda "
-"mempertimbangkan bahwa:"
-
-msgid "**Configure a default datastore.**"
-msgstr "**Configure a default datastore.**"
-
-msgid "**Create a cluster**"
-msgstr "**Create a cluster** (buat kluster)"
-
-msgid "**Create a configuration group**"
-msgstr "**Create a configuration group** (buat kelompok konfigurasi)"
-
-msgid "**Create a database instance**"
-msgstr "**Create a database instance**"
-
-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 ""
-"**Create database instance.** (buat instance database). Setelah Anda "
-"mengkonfigurasi datastore default dan memverifikasi bahwa Anda memiliki "
-"flavor yang tepat, Anda dapat membuat sebuah instance database."
-
-msgid "**Create the module file and trove module**"
-msgstr "** Buat file modul dan modul trove **"
-
-msgid "**Create the replica**"
-msgstr "**Create the replica** (buat replika)"
-
-msgid "**Create your first incremental backup**"
-msgstr ""
-"**Create your first incremental backup** (Buat backup inkremental pertama "
-"Anda)"
-
-msgid "**Create your second incremental backup**"
-msgstr ""
-"**Create your second incremental backup** (Buat inkremental backup kedua "
-"Anda)"
-
-msgid "**Dashboard — Create Image**"
-msgstr "**Dashboard — Create Image**"
-
-msgid "**Delete a cluster**"
-msgstr "**Delete a cluster** (hapus cluster)"
-
-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 ""
-"**Destination port on virtual machine**. Mendefinisikan berbagai port. "
-"Untuk membuka port tunggal saja, masukkan nilai yang sama dua kali. ICMP "
-"tidak mendukung port; sebaliknya, Anda memasukkan nilai untuk menentukan "
-"kode dan tipe traffic ICMP yang akan diizinkan."
-
-msgid "**Detach the replica**"
-msgstr "**Detach the replica** (lepaskan replika)"
-
-msgid "**Determine which flavor to use for your database**"
-msgstr ""
-"**Determine which flavor to use for your database** (menentukan flavor "
-"digunakan untuk database Anda) "
-
-msgid "**Direction**: ``Ingress``"
-msgstr "**Direction**: ``Ingress``"
-
-msgid "**Display cluster information**"
-msgstr "**Display cluster information** (tampilan informasi klaster)"
-
-msgid "**Examine your existing configuration**"
-msgstr "**Examine your existing configuration** (periksa konfigurasi yang ada)"
-
-msgid "**Figure: Admin tab**"
-msgstr "**Figure: Admin tab**"
-
-msgid "**Figure: Project tab**"
-msgstr "**Figure: Project tab**"
-
-msgid "**Figure:Identity tab**"
-msgstr "**Figure:Identity tab**"
-
-msgid "**Figure:Settings tab**"
-msgstr "**Figure:Settings tab**"
-
-msgid "**Get the IP address of the database instance**"
-msgstr ""
-"**Get the IP address of the database instance** (dapatkan alamat IP dari "
-"database instance)"
-
-msgid "**Get the instance ID**"
-msgstr "**Get the instance ID** (dapatkan ID instance)"
-
-msgid "**Guidelines**"
-msgstr "**Guidelines** (pedoman)"
-
-msgid "**Image requirements**"
-msgstr "**Image requirements** (persyaratan image)"
-
-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 ""
-"**Instance name.** Nama ini terdiri dari nama set replikasi diikuti oleh "
-"string -*n*, dimana *n* adalah 1 untuk instance pertama dalam set replikasi, "
-"2 untuk instance kedua, dan seterusnya. Dalam contoh ini, nama instance "
-"adalah ``cluster1-rs1-1``, ``cluster1-rs1-2``, dan ``cluster1-rs1-3``."
-
-msgid "**List available options**"
-msgstr "**List available options** (daftar pilihan yang tersedia)"
-
-msgid "**List cluster instances**"
-msgstr "**List cluster instances** (daftar instance kluster)"
-
-msgid "**List clusters**"
-msgstr "**List clusters** (dafter kluste)"
-
-msgid ""
-"**Maintenance.** There are also a number of useful maintenance features for "
-"working with configuration groups. You can:"
-msgstr ""
-"**Maintenance.** (pemeliharaan) Ada juga sejumlah fitur pemeliharaan berguna "
-"untuk bekerja dengan kelompok konfigurasi. Kamu bisa:"
-
-msgid ""
-"**MySQL example.** This example creates a flavor that you can use with a "
-"MySQL database. This example has the following attributes:"
-msgstr ""
-"**MySQL example.** Contoh ini menciptakan flavor yang dapat Anda gunakan "
-"dengan database MySQL. Contoh ini memiliki atribut sebagai berikut:"
-
-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 ""
-"**Naming conventions for replication sets and instances.** Perhatikan bahwa "
-"kolom ``Name`` menampilkan nama instance yang mencakup nama set replikasi. "
-"Nama set replikasi dan nama instance secara otomatis akan dihasilkan, "
-"berikut aturan-aturan ini:"
-
-msgid "**Notify users**"
-msgstr "**Notify users** (Beritahu pengguna)"
-
-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 ""
-"**Prerequisites.** (prasyarat) Sebelum Anda membuat sebuah instance "
-"database, Anda perlu mengkonfigurasi datastore default dan pastikan Anda "
-"memiliki flavor yang sesuai untuk tipe instance database yang Anda inginkan."
-
-msgid "**Protocol**. Choose TCP for SSH, ICMP for pings, or UDP."
-msgstr "**Protocol**. Pilih TCP untuk SSH, ICMP untuk ping, atau UDP."
-
-msgid "**Re-examine the database configuration**"
-msgstr ""
-"**Re-examine the database configuration** (pemeriksaan kembali konfigurasi "
-"database)"
-
-msgid "**Remote**: ``CIDR``"
-msgstr "**Remote**: ``CIDR``"
-
-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 ""
-"**Replication set name.** Nama ini terdiri dari nama cluster, diikuti oleh "
-"string -rs\\ *n*, dimana *n* adalah 1 untuk set replikasi pertama dimana "
-"Anda buat, 2 untuk set replikasi kedua, dan seterusnya. Dalam contoh ini, "
-"nama cluster ``cluster1``, dan hanya ada satu set replikasi, sehingga nama "
-"set replikasi adalah ``cluster1-rs1``."
-
-msgid "**Restore a database instance**"
-msgstr "**Restore a database instance** (Kembalikan instance database)"
-
-msgid "**Restore using incremental backups**"
-msgstr ""
-"**Restore using incremental backups** (Restore menggunakan inkremental "
-"backup)"
-
-msgid "**Rule**: ``All ICMP``"
-msgstr "**Rule**: ``All ICMP``"
-
-msgid "**Rule**: ``SSH``"
-msgstr "**Rule**: ``SSH``"
-
-msgid "**Show and list modules**"
-msgstr "** Tampilkan dan daftar modul **"
-
-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 ""
-"**Source of traffic**. Aktifkan lalu lintas (traffic) ke instance dari "
-"alamat IP di dalam cloud dari anggota kelompok lain atau dari semua alamat "
-"IP."
-
-msgid "**To copy an object from one container to another**"
-msgstr "**To copy an object from one container to another**"
-
-msgid "**To create a metadata-only object without a file**"
-msgstr "**To create a metadata-only object without a file**"
-
-msgid "**To create a pseudo-folder**"
-msgstr "**To create a pseudo-folder**"
-
-msgid "**To edit an object**"
-msgstr "**To edit an object**"
-
-msgid "**Verify backup**"
-msgstr "**Verify backup** (Verifikasi cadangan)"
-
-msgid "**Verify flavor.**"
-msgstr "**Verify flavor.**"
-
-msgid "**Verify replication status**"
-msgstr "**Verify replication status** (pastikan status replikasi)"
-
-msgid ""
-"**Your application connects to this IP address.** The :command:`trove "
-"cluster-show` command displays the IP address of the query router. This is "
-"the IP address your application uses to retrieve data from the database."
-msgstr ""
-"**Your application connects to this IP address.** Perintah :command:`trove "
-"cluster-show` akan menampilkan alamat IP dari router kueri. Ini adalah "
-"alamat IP aplikasi Anda berguna untuk mengambil data dari database."
-
-msgid "**avg**. The average of sample volumes over each period."
-msgstr "**avg**. Rata-rata volume sampel lebih dari setiap periode."
-
-msgid "**count**. The number of samples in each period."
-msgstr "**count**. Jumlah sampel di setiap periode."
-
-msgid "**max**. The maximum number of sample volumes in each period."
-msgstr "**max**. Jumlah maksimum volume sampel di setiap periode."
-
-msgid "**min**. The minimum number of sample volumes in each period."
-msgstr "**min**. Jumlah minimum volume sampel di setiap periode."
-
-msgid "**sum**. The sum of sample volumes over each period."
-msgstr "**sum**. Jumlah volume sampel lebih dari setiap periode."
-
-msgid "*DATASTORE_NAME*. The name of the associated data store."
-msgstr "*DATASTORE_NAME*. Nama penyimpanan data yang terkait."
-
-msgid "*NAME*. The name you want to use for this group."
-msgstr "*NAME*. Nama Anda ingin gunakan untuk kelompok ini."
-
-msgid "*VALUES*. The list of key-value pairs."
-msgstr "*VALUES*. Daftar pasangan kunci-nilai (key-value pair)."
-
-msgid "1"
-msgstr "1"
-
-msgid "1024"
-msgstr "1024"
-
-msgid "2048"
-msgstr "2048"
-
-msgid "5"
-msgstr "5"
-
-msgid "512"
-msgstr "512"
-
-msgid ":guilabel:`API Access`: View API endpoints."
-msgstr ":guilabel:`API Access`: Melihat endpoint API."
-
-msgid ""
-":guilabel:`Access & Security`: Use the following tabs to complete these "
-"tasks:"
-msgstr ""
-":guilabel:`Access & Security`: Gunakan tab berikut untuk menyelesaikan tugas "
-"ini:"
-
-msgid ":guilabel:`Access Level`: Choose read-write or read-only."
-msgstr ":guilabel:`Access Level`: Pilih baca-tulis atau hanya untuk dibaca."
-
-msgid ":guilabel:`Access To`: Fill in Access To field."
-msgstr ":guilabel:`Access To`: Isi Access To field."
-
-msgid ":guilabel:`Access Type`: Choose ip, user, or cert."
-msgstr ":guilabel:`Access Type`: Pilih ip, pengguna, atau cert."
-
-msgid ":guilabel:`Admin State`: The state to start the network in."
-msgstr ":guilabel:`Admin State`: Kondisi untuk memulai jaringan masuk."
-
-msgid ":guilabel:`Allocation Pools`: Specify IP address pools."
-msgstr ":guilabel:`Allocation Pools`: Tentukan kolam alamat IP."
-
-msgid ":guilabel:`Architecture`"
-msgstr ":guilabel:`Architecture`"
-
-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 ""
-":guilabel:`Availability Zone`: Pilih Zona Ketersediaan dari daftar. Secara "
-"default, nilai ini diatur ke zona ketersediaan diberikan oleh penyedia cloud "
-"(for example, ``us-west`` atau ``apac-south``). Untuk beberapa kasus, hal "
-"itu bisa menjadi ``nova``."
-
-msgid ""
-":guilabel:`Binding Host`: The ID of the host where the port is allocated."
-msgstr ":guilabel:`Binding Host`: ID dari host dimana port dialokasikan."
-
-msgid ""
-":guilabel:`Binding VNIC Type`: Select the VNIC type that is bound to the "
-"neutron port."
-msgstr ""
-":guilabel:`Binding VNIC Type`: Pilih tipe VNIC yang terikat ke port neutron."
-
-msgid ""
-":guilabel:`Block Storage Services`: View a list of all Block Storage "
-"services."
-msgstr ""
-":guilabel:`Block Storage Services`: Melihat daftar semua layanan Block "
-"Storage."
-
-msgid ":guilabel:`Change Password`: Change the password of the user."
-msgstr ":guilabel:`Change Password`: Mengubah password pengguna."
-
-msgid ":guilabel:`Compute Services`: View a list of all Compute services."
-msgstr ":guilabel:`Compute Services`: Melihat daftar semua layanan Compute."
-
-msgid ":guilabel:`Configuration` tab"
-msgstr "Tab :guilabel:`Configuration`"
-
-msgid ":guilabel:`Confirm Password`: Enter the password again to confirm."
-msgstr ":guilabel:`Confirm Password`: Masukkan password lagi untuk konfirmasi."
-
-msgid ":guilabel:`Containers`: Create and manage containers and objects."
-msgstr ""
-":guilabel:`Containers`: Membuat dan mengelola wadah (container) dan objek."
-
-msgid ":guilabel:`Copy Data`"
-msgstr ":guilabel:`Copy Data`"
-
-msgid ":guilabel:`Create Subnet`: Select this check box to create a subnet"
-msgstr ""
-":guilabel:`Create Subnet`: Pilih (select) check box ini untuk membuat subnet"
-
-msgid ":guilabel:`Creation Timeout` :guilabel:`(minutes)`"
-msgstr ":guilabel:`Creation Timeout` :guilabel:`(minutes)`"
-
-msgid ":guilabel:`DBName`"
-msgstr ":guilabel:`DBName`"
-
-msgid ":guilabel:`DBPassword`"
-msgstr ":guilabel:`DBPassword`"
-
-msgid ":guilabel:`DBRootPassword`"
-msgstr ":guilabel:`DBRootPassword`"
-
-msgid ":guilabel:`DBUsername`"
-msgstr ":guilabel:`DBUsername`"
-
-msgid ":guilabel:`DNS IP`: Enter the DNS IP address."
-msgstr ":guilabel:`DNS IP`: Masukkan alamat IP DNS."
-
-msgid ":guilabel:`DNS Name Servers`: Specify a name for the DNS server."
-msgstr ":guilabel:`DNS Name Servers`: Tentukan nama untuk server DNS."
-
-msgid ":guilabel:`Database Name`: Specify a name for the database instance."
-msgstr ":guilabel:`Database Name`: Tentukan nama untuk instance database."
-
-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 ""
-":guilabel:`Defaults`: Melihat nilai kuota default. Kuota adalah hard-coded "
-"di OpenStack Compute dan menentukan ukuran maksimum dan jumlah sumber daya."
-
-msgid ":guilabel:`Description`: Enter a new description."
-msgstr ":guilabel:`Description`: Masukkan deskripsi baru."
-
-msgid ""
-":guilabel:`Description`: Optionally, provide a brief description for the "
-"security service."
-msgstr ""
-":guilabel:`Description`: Secara opsional, berikan penjelasan singkat untuk "
-"layanan keamanan."
-
-msgid ""
-":guilabel:`Description`: Optionally, provide a brief description for the "
-"share network."
-msgstr ""
-":guilabel:`Description`: secara opsional, berikan penjelasan singkat untuk "
-"jaringan bersama."
-
-msgid ""
-":guilabel:`Description`: Optionally, provide a brief description for the "
-"share."
-msgstr ""
-":guilabel:`Description`: Secara opsional, memberikan penjelasan singkat "
-"untuk berbagi."
-
-msgid ""
-":guilabel:`Description`: Optionally, provide a brief description for the "
-"volume."
-msgstr ""
-":guilabel:`Description`: Secara opsional, berikan penjelasan singkat untuk "
-"volume."
-
-msgid ""
-":guilabel:`Destination Container`: Choose the destination container from the "
-"list."
-msgstr ":guilabel:`Destination Container`: Pilih kontainer tujuan dari daftar."
-
-msgid ""
-":guilabel:`Destination object name`: Enter a name for the object in the new "
-"container."
-msgstr ""
-":guilabel:`Destination object name`: Masukkan nama untuk objek dalam wadah "
-"(container) baru."
-
-msgid ":guilabel:`Details` tab"
-msgstr "Tab :guilabel:`Details`"
-
-msgid ":guilabel:`Device ID`: Device ID attached to the port."
-msgstr ":guilabel:`Device ID`: Device ID terhubung port."
-
-msgid ":guilabel:`Device Owner`: Device owner attached to the port."
-msgstr ":guilabel:`Device Owner`: Pemilik perangkat yang terpasang ke port."
-
-msgid ""
-":guilabel:`Disable Gateway`: Select this check box to disable a gateway IP "
-"address."
-msgstr ""
-":guilabel:`Disable Gateway`: Pilih check box ini untuk menonaktifkan alamat "
-"IP gateway."
-
-msgid ":guilabel:`Domain`: Enter the domain name."
-msgstr ":guilabel:`Domain`: Masukkan nama domain."
-
-msgid ":guilabel:`Enable DHCP`: Select this check box to enable DHCP."
-msgstr ":guilabel:`Enable DHCP`: Pilih check box ini untuk mengaktifkan DHCP."
-
-msgid ":guilabel:`Environment File/Data`"
-msgstr ":guilabel:`Environment File/Data`"
-
-msgid ":guilabel:`Environment Source`"
-msgstr ":guilabel:`Environment Source`"
-
-msgid ":guilabel:`Firewall Policies`: Add and manage firewall policies."
-msgstr ""
-":guilabel:`Firewall Policies`: Menambahkan dan mengelola kebijakan firewall."
-
-msgid ":guilabel:`Firewall Rules`: Add and manage firewall rules."
-msgstr ":guilabel:`Firewall Rules`: Menambahkan dan mengelola aturan firewall."
-
-msgid ":guilabel:`Firewalls`: Create and manage firewalls."
-msgstr ":guilabel:`Firewalls`: Membuat dan mengelola firewall."
-
-msgid ":guilabel:`Flavor` tab"
-msgstr "Tab :guilabel:`Flavor`"
-
-msgid ":guilabel:`Flavor`: Select an appropriate flavor for the instance."
-msgstr ":guilabel:`Flavor`: Pilih flavor yang sesuai instance."
-
-msgid ""
-":guilabel:`Flavors`: View, create, edit, view extra specifications for, and "
-"delete flavors. A flavor is the size of an instance."
-msgstr ""
-":guilabel:`Flavors`: Melihat, membuat, mengedit, melihat spesifikasi "
-"tambahan, dan menghapus flavor. Flavor adalah ukuran sebuah instance."
-
-msgid ""
-":guilabel:`Floating IPs`: Allocate an IP address to or release it from a "
-"project."
-msgstr ""
-":guilabel:`Floating IPs`: Mengalokasikan alamat IP atau melepaskannya dari "
-"proyek."
-
-msgid ":guilabel:`Format`"
-msgstr ":guilabel:`Format`"
-
-msgid ""
-":guilabel:`Gateway IP`: Specify an IP address for a specific gateway. This "
-"parameter is optional."
-msgstr ""
-":guilabel:`Gateway IP`: Menentukan alamat IP untuk gateway tertentu. "
-"Parameter ini bersifat opsional."
-
-msgid ""
-":guilabel:`Host Aggregates`: View, create, and edit host aggregates. View "
-"the list of availability zones."
-msgstr ""
-":guilabel:`Host Aggregates`: Melihat, membuat, dan mengedit agregat host. "
-"Lihat daftar zona ketersediaan."
-
-msgid ":guilabel:`Host Routes`: Specify the IP address of host routes."
-msgstr ":guilabel:`Host Routes`: Tentukan alamat IP dari rute host."
-
-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 ""
-":guilabel:`Host`: Secara opsional, memungkinkan pengguna untuk menghubungkan "
-"hanya dari host ini. Jika Anda tidak menentukan host, pengguna ini akan "
-"diizinkan untuk terhubung dari mana saja."
-
-msgid ":guilabel:`Hypervisors`: View the hypervisor summary."
-msgstr ":guilabel:`Hypervisors`: Melihat ringkasan hypervisor."
-
-msgid ":guilabel:`IP Version`: Select IPv4 or IPv6."
-msgstr ":guilabel:`IP Version`: Pilih IPv4 atau IPv6."
-
-msgid ":guilabel:`Image Description`"
-msgstr ":guilabel:`Image Description`"
-
-msgid ":guilabel:`Image File` or :guilabel:`Image Location`"
-msgstr ":guilabel:`Image File` atau :guilabel:`Image Location`"
-
-msgid ":guilabel:`Image Metadata`"
-msgstr ":guilabel:`Image Metadata`"
-
-msgid ":guilabel:`Image Name`"
-msgstr ":guilabel:`Image Name`"
-
-msgid ":guilabel:`Image Source`"
-msgstr ":guilabel:`Image Source`"
-
-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 ""
-":guilabel:`Images`: Melihat foto dan snapshot instance yang dibuat oleh "
-"pengguna proyek, ditambah image yang tersedia untuk umum. Membuat, mengedit, "
-"dan menghapus image, dan meluncurkan instance dari image dan snapshot."
-
-msgid ""
-":guilabel:`Images`: View, create, edit properties for, and delete custom "
-"images."
-msgstr ""
-":guilabel:`Images`: Melihat, membuat, mengedit properti untuk, dan menghapus "
-"image kustom."
-
-msgid ""
-":guilabel:`Initial Admin User`: Create an initial admin user. This user will "
-"have access to all the databases you create."
-msgstr ""
-":guilabel:`Initial Admin User`: Buat user admin awal. Pengguna ini akan "
-"memiliki akses ke semua database yang Anda buat."
-
-msgid ":guilabel:`Initialize Databases`: Initial Database"
-msgstr ":guilabel:`Initialize Databases`: Database awal "
-
-msgid ":guilabel:`InstanceType`"
-msgstr ":guilabel:`InstanceType`"
-
-msgid ""
-":guilabel:`Instances`: View, launch, create a snapshot from, stop, pause, or "
-"reboot instances, or connect to them through VNC."
-msgstr ""
-":guilabel:`Instances`: Melihat, meluncurkan, membuat snapshot dari, "
-"menghentikan, pause, atau reboot instance, atau menghubungkan ke mereka "
-"melalui VNC."
-
-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 ""
-":guilabel:`Instances`: Melihat, melakukan jeda, melanjutkan, menangguhkan, "
-"bermigrasi, reboot lembut atau keras, dan menghapus menjalankan instance "
-"milik pengguna dari beberapa, tapi tidak semua, proyek. Juga, melihat log "
-"untuk sebuah instance atau mengakses instance melalui VNC."
-
-msgid ":guilabel:`Key Pair` tab"
-msgstr "Tab :guilabel:`Key Pair`"
-
-msgid ""
-":guilabel:`Key Pairs`: View, create, edit, import, and delete key pairs."
-msgstr ""
-":guilabel:`Key Pairs`: MeLihat, membuat, mengedit, impor, dan menghapus "
-"pasangan kunci (key pair)."
-
-msgid ":guilabel:`KeyName`"
-msgstr ":guilabel:`KeyName`"
-
-msgid ":guilabel:`LinuxDistribution`"
-msgstr ":guilabel:`LinuxDistribution`"
-
-msgid ":guilabel:`Load Balancers`: Create and manage load balancers."
-msgstr ""
-":guilabel:`Load Balancers`: Membuat dan mengelola penyeimbang beban (load "
-"balancer)."
-
-msgid ":guilabel:`Members`: Add and manage members."
-msgstr ":guilabel:`Members`: Menambahkan dan mengelola anggota."
-
-msgid ""
-":guilabel:`Metadata Definitions`: Import namespace and view the metadata "
-"information."
-msgstr ""
-":guilabel:`Metadata Definitions`: Impor namespace dan melihat informasi "
-"metadata."
-
-msgid ":guilabel:`Metadata` tab"
-msgstr "Tab :guilabel:`Metadata`"
-
-msgid ":guilabel:`Metadata`: Enter metadata for the share creation if needed."
-msgstr ""
-":guilabel:`Metadata`: Masukkan metadata untuk pembuatan share jika "
-"diperlukan."
-
-msgid ""
-":guilabel:`Metadata`: To add share metadata, use key=value. To unset "
-"metadata, use key."
-msgstr ""
-":guilabel:`Metadata`: Untuk menambahkan metadata share, menggunakan "
-"key=value. Untuk metadata tanpa pengaturan (unset), gunakan kunci."
-
-msgid ":guilabel:`Minimum Disk (GB)`"
-msgstr ":guilabel:`Minimum Disk (GB)`"
-
-msgid ":guilabel:`Minimum RAM (MB)`"
-msgstr ":guilabel:`Minimum RAM (MB)`"
-
-msgid ":guilabel:`Monitors`: Add and manage monitors."
-msgstr ":guilabel:`Monitors`: Menambahkan dan mengelola monitor."
-
-msgid ":guilabel:`Name`: Enter a new security service name."
-msgstr ":guilabel:`Name`: Masukkan nama layanan keamanan baru."
-
-msgid ":guilabel:`Name`: Enter a new share network name."
-msgstr ":guilabel:`Name`: Masukkan nama jaringan bersama baru."
-
-msgid ":guilabel:`Name`: Specify a name for the security service."
-msgstr ":guilabel:`Name`: Tentukan nama untuk layanan keamanan."
-
-msgid ":guilabel:`Name`: Specify a name for the share network."
-msgstr ":guilabel:`Name`: Tentukan nama untuk jaringan bersama."
-
-msgid ":guilabel:`Name`: Specify name to identify the port."
-msgstr ":guilabel:`Name`: Tentukan nama untuk mengidentifikasi port."
-
-msgid ":guilabel:`Network Address`: Specify the IP address for the subnet."
-msgstr ":guilabel:`Network Address`: Tentukan alamat IP untuk subnet."
-
-msgid ":guilabel:`Network Agents`: View the network agents."
-msgstr ":guilabel:`Network Agents`: Lihat agen jaringan."
-
-msgid ":guilabel:`Network Name`: Specify a name to identify the network."
-msgstr ""
-":guilabel:`Network Name`: Tentukan nama untuk mengidentifikasi jaringan."
-
-msgid ":guilabel:`Network Ports` tab"
-msgstr "Tab :guilabel:`Network Ports`"
-
-msgid ":guilabel:`Network Topology`: View the network topology."
-msgstr ":guilabel:`Network Topology`: Melihat topologi jaringan."
-
-msgid ":guilabel:`Network` tab"
-msgstr "Tab :guilabel:`Network`"
-
-msgid ":guilabel:`Networks` tab"
-msgstr "Tab :guilabel:`Networks`"
-
-msgid ":guilabel:`Networks`: Create and manage public and private networks."
-msgstr ""
-":guilabel:`Networks`: Membuat dan mengelola jaringan publik dan private."
-
-msgid ""
-":guilabel:`Networks`: View, create, edit properties for, and delete networks."
-msgstr ""
-":guilabel:`Networks`: Melihat, membuat, mengedit properti untuk, dan "
-"menghapus jaringan."
-
-msgid ":guilabel:`Neutron Net`: Choose a neutron network."
-msgstr ":guilabel:`Neutron Net`: Pilih jaringan neutron."
-
-msgid ":guilabel:`Neutron Subnet`: Choose a neutron subnet."
-msgstr ":guilabel:`Neutron Subnet`: Pilih subnet neutron."
-
-msgid ":guilabel:`New Size (GB)`: Enter new size."
-msgstr ":guilabel:`New Size (GB)`: Masukkan ukuran baru."
-
-msgid ""
-":guilabel:`Orchestration Services`: View a list of all Orchestration "
-"services."
-msgstr ""
-":guilabel:`Orchestration Services`: Melihat daftar semua layanan "
-"Orchestration."
-
-msgid ":guilabel:`Overview`: View basic reports."
-msgstr ":guilabel:`Overview`: Melihat laporan dasar."
-
-msgid ":guilabel:`Overview`: View reports for the project."
-msgstr ":guilabel:`Overview`: Lihat laporan untuk proyek tersebut."
-
-msgid ":guilabel:`Password for user` :guilabel:`\"demo\"`"
-msgstr ":guilabel:`Password for user` :guilabel:`\"demo\"`"
-
-msgid ":guilabel:`Password`: Enter the password."
-msgstr ":guilabel:`Password`: Masukkan password."
-
-msgid ""
-":guilabel:`Password`: Specify a password associated with the initial admin "
-"user you just named."
-msgstr ""
-":guilabel:`Password`: Tentukan password yang terkait dengan user admin awal "
-"yang Anda baru namakan."
-
-msgid ""
-":guilabel:`Path`: Specify a path in which the new copy should be stored "
-"inside of the selected container."
-msgstr ""
-":guilabel:`Path`: Menentukan jalur dimana salinan baru harus disimpan dalam "
-"wadah (container) yang dipilih."
-
-msgid ":guilabel:`Pools`: Add and manage pools."
-msgstr ":guilabel:`Pools`: Menambahkan dan mengelola kolam (pool)."
-
-msgid ""
-":guilabel:`Projects`: View, create, assign users to, remove users from, and "
-"delete projects."
-msgstr ""
-":guilabel:`Projects`: Melihat, membuat, menetapkan pengguna untuk, menghapus "
-"pengguna dari, dan menghapus proyek."
-
-msgid ":guilabel:`Protected`"
-msgstr ":guilabel:`Protected`"
-
-msgid ""
-":guilabel:`Resource Types`: Show a list of all the supported resource types "
-"for HOT templates."
-msgstr ""
-":guilabel:`Resource Types`: Menampilkan daftar semua jenis sumber daya yang "
-"didukung untuk template HOT."
-
-msgid ""
-":guilabel:`Resource Usage`: Use the following tabs to view the following "
-"usages:"
-msgstr ""
-":guilabel:`Resource Usage`: Gunakan tab berikut untuk melihat penggunaan "
-"berikut:"
-
-msgid ":guilabel:`Rollback On Failure`"
-msgstr ":guilabel:`Rollback On Failure`"
-
-msgid ":guilabel:`Routers`: Create and manage routers."
-msgstr ":guilabel:`Routers`: Membuat dan mengelola router."
-
-msgid ""
-":guilabel:`Routers`: View, create, edit properties for, and delete routers."
-msgstr ""
-":guilabel:`Routers`: Melihat, membuat, mengedit properti, dan menghapus "
-"router."
-
-msgid ":guilabel:`Security Groups` tab"
-msgstr "Tab :guilabel:`Security Groups`"
-
-msgid ""
-":guilabel:`Security Groups`: View, create, edit, and delete security groups "
-"and security group rules."
-msgstr ""
-":guilabel:`Security Groups`: Melihat, membuat, mengedit, dan menghapus "
-"kelompok keamanan dan aturan kelompok keamanan."
-
-msgid ""
-":guilabel:`Security Services`: View, manage, and delete security services."
-msgstr ""
-":guilabel:`Security Services`: Melihat, mengelola, dan menghapus layanan "
-"keamanan."
-
-msgid ":guilabel:`Server`: Enter the server name."
-msgstr ":guilabel:`Server`: Masukkan nama server."
-
-msgid ":guilabel:`Services`: View a list of the services."
-msgstr ":guilabel:`Services`: Melihat daftar layanan."
-
-msgid ":guilabel:`Share Name`: Enter a new share name."
-msgstr ":guilabel:`Share Name`: Masukkan nama share baru."
-
-msgid ":guilabel:`Share Name`: Specify a name for the share."
-msgstr ":guilabel:`Share Name`: Tentukan nama untuk berbagi."
-
-msgid ":guilabel:`Share Network`: Choose a share network."
-msgstr ":guilabel:`Share Network`: Pilih jaringan berbagi (share)."
-
-msgid ":guilabel:`Share Networks`: View, manage, and delete share networks."
-msgstr ""
-":guilabel:`Share Networks`: Melihat, mengelola, dan menghapus jaringan "
-"bersama."
-
-msgid ":guilabel:`Share Protocol`: Select NFS, CIFS, GlusterFS, or HDFS."
-msgstr ":guilabel:`Share Protocol`: Pilih NFS, CIFS, GlusterFS, atau HDFS."
-
-msgid ":guilabel:`Share Servers`: View, manage, and delete share servers."
-msgstr ""
-":guilabel:`Share Servers`: Melihat, mengelola, dan menghapus server bersama."
-
-msgid ":guilabel:`Share Type`: Choose a share type."
-msgstr ":guilabel:`Share Type`: Pilih tipe share."
-
-msgid ":guilabel:`Share Types`: View, create, manage, and delete share types."
-msgstr ""
-":guilabel:`Share Types`: Melihat, membuat, mengelola, dan menghapus tipe "
-"share."
-
-msgid ""
-":guilabel:`Shared`: Share the network with other projects. Non admin users "
-"are not allowed to set shared option."
-msgstr ""
-":guilabel:`Shared`: Berbagi jaringan dengan proyek lainnya. Pengguna non "
-"admin tidak diizinkan untuk menetapkan pilihan bersama (shared option)."
-
-msgid ":guilabel:`Shares`: Use the following tabs to complete these tasks:"
-msgstr ":guilabel:`Shares`: Gunakan tab berikut untuk menyelesaikan tugas ini:"
-
-msgid ":guilabel:`Shares`: View, create, manage, and delete shares."
-msgstr ":guilabel:`Shares`: Melihat, membuat, mengelola, dan menghapus share."
-
-msgid ":guilabel:`Size (GB)`: The size of the share in gibibytes (GiB)."
-msgstr ":guilabel:`Size (GB)`: Ukuran share di gibibytes (GIB)."
-
-msgid ":guilabel:`Size (GB)`: The size of the volume in gibibytes (GiB)."
-msgstr ":guilabel:`Size (GB)`: Ukuran volume di gibibytes (GIB)."
-
-msgid ":guilabel:`Snapshots`: View, manage, and delete volume snapshots."
-msgstr ""
-":guilabel:`Snapshots`: Melihat, mengelola, dan menghapus snapshot volume."
-
-msgid ":guilabel:`Source` tab"
-msgstr "Tab :guilabel:`Source`"
-
-msgid ":guilabel:`Stack Name`"
-msgstr ":guilabel:`Stack Name`"
-
-msgid ""
-":guilabel:`Stacks`: Use the REST API to orchestrate multiple composite cloud "
-"applications."
-msgstr ""
-":guilabel:`Stacks`: Gunakan REST API untuk mengatur (orchestrate) beberapa "
-"aplikasi cloud komposit."
-
-msgid ":guilabel:`Stats`: View the statistics of all resources."
-msgstr ":guilabel:`Stats`: Melihat statistik dari semua sumber daya."
-
-msgid ":guilabel:`Subnet Details` tab"
-msgstr "Tab :guilabel:`Subnet Details`"
-
-msgid ":guilabel:`Subnet Name`: Specify a name for the subnet."
-msgstr ":guilabel:`Subnet Name`: Tentukan nama untuk subnet."
-
-msgid ":guilabel:`Subnet` tab"
-msgstr "Tab :guilabel:`Subnet`"
-
-msgid ""
-":guilabel:`System Information`: Use the following tabs to view the service "
-"information:"
-msgstr ""
-":guilabel:`System Information`: Gunakan tab berikut untuk melihat informasi "
-"layanan:"
-
-msgid ":guilabel:`Template Source`"
-msgstr ":guilabel:`Template Source`"
-
-msgid ":guilabel:`Template URL/File/Data`"
-msgstr ":guilabel:`Template URL/File/Data`"
-
-msgid ""
-":guilabel:`Type`: Choose the type from Active Directory, LDAP, or Kerberos."
-msgstr ""
-":guilabel:`Type`: Pilih tipe dari Active Directory, LDAP, atau Kerberos."
-
-msgid ":guilabel:`Type`: Leave this field blank."
-msgstr ":guilabel:`Type`: Tinggalkan field ini kosong. "
-
-msgid ":guilabel:`Usage Report`: View the usage report."
-msgstr ":guilabel:`Usage Report`: Melihat laporan penggunaan."
-
-msgid ":guilabel:`User Settings`: View and manage dashboard settings."
-msgstr ":guilabel:`User Settings`: Melihat dan mengelola pengaturan dashboard."
-
-msgid ":guilabel:`User`: Enter the user name."
-msgstr ":guilabel:`User`: Masukkan username."
-
-msgid ":guilabel:`Users`: View, create, enable, disable, and delete users."
-msgstr ""
-":guilabel:`Users`: Melihat, membuat, mengaktifkan, menonaktifkan, dan "
-"menghapus pengguna."
-
-msgid ":guilabel:`Visibility`"
-msgstr ":guilabel:`Visibility`"
-
-msgid ":guilabel:`Volume Name`: Specify a name for the volume."
-msgstr ":guilabel:`Volume Name`: Tentukan nama untuk volume."
-
-msgid ""
-":guilabel:`Volume Size`: Select a volume size. Volume size is expressed in "
-"GB."
-msgstr ""
-":guilabel:`Volume Size`: Pilih ukuran volume. Ukuran volume dinyatakan dalam "
-"GB."
-
-msgid ""
-":guilabel:`Volume Snapshots`: View, create, edit, and delete volume "
-"snapshots."
-msgstr ""
-":guilabel:`Volume Snapshots`: Melihat, membuat, mengedit, dan menghapus "
-"snapshot volume."
-
-msgid ""
-":guilabel:`Volume Snapshots`: View, manage, and delete volume snapshots."
-msgstr ""
-":guilabel:`Volume Snapshots`: Melihat, mengelola, dan menghapus snapshot "
-"volume."
-
-msgid ":guilabel:`Volume Source`: Select one of the following options:"
-msgstr ":guilabel:`Volume Source`: Pilih salah satu dari opsi berikut:"
-
-msgid ""
-":guilabel:`Volume Types`: View, create, manage, and delete volume types."
-msgstr ""
-":guilabel:`Volume Types`: Lihat, membuat, mengelola, dan menghapus jenis "
-"volume."
-
-msgid ":guilabel:`Volumes`: Use the following tabs to complete these tasks:"
-msgstr ""
-":guilabel:`Volumes`: Gunakan tab berikut untuk menyelesaikan tugas ini:"
-
-msgid ":guilabel:`Volumes`: View, create, edit, and delete volumes."
-msgstr ":guilabel:`Volumes`: Melihat, membuat, mengedit, dan menghapus volume."
-
-msgid ":guilabel:`Volumes`: View, create, manage, and delete volumes."
-msgstr ""
-":guilabel:`Volumes`: Melihat, membuat, mengelola, dan menghapus volume."
-
-msgid ":ref:`Boot_a_new_instance_from_the_snapshot`"
-msgstr ":ref:`Boot_a_new_instance_from_the_snapshot`"
-
-msgid ":ref:`Boot_instance_from_image_and_attach_non-bootable_volume`"
-msgstr ":ref:`Boot_instance_from_image_and_attach_non-bootable_volume`"
-
-msgid ":ref:`Create_a_snapshot_of_the_instance`"
-msgstr ":ref:`Create_a_snapshot_of_the_instance`"
-
-msgid ":ref:`Create_volume_from_image_and_boot_instance`"
-msgstr ":ref:`Create_volume_from_image_and_boot_instance`"
-
-msgid ":ref:`Download_the_snapshot_as_an_image`"
-msgstr ":ref:`Download_the_snapshot_as_an_image`"
-
-msgid ":ref:`Import_the_snapshot_to_the_new_environment`"
-msgstr ":ref:`Import_the_snapshot_to_the_new_environment`"
-
-msgid ":ref:`archive-auto-extract`"
-msgstr ":ref:`archive-auto-extract`"
-
-msgid ":ref:`bulk-delete`"
-msgstr ":ref:`bulk-delete`"
-
-msgid ":ref:`large-object-creation`"
-msgstr ":ref:`large-object-creation`"
-
-msgid ":ref:`static-website`"
-msgstr ":ref:`static-website`"
-
-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 ""
-":term:`Cross-Origin Resource Sharing (CORS)` adalah spesifikasi yang "
-"mendefinisikan bagaimana browser dan server berkomunikasi melintasi asal "
-"muasal dengan menggunakan header HTTP, seperti yang ditugaskan oleh "
-"permintaan API Object Storage. Objek Storage API mendukung header berikut:"
-
-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 ""
-"**key pair** (sepasang kunci) untuk instance Anda, yang mandat SSH yang "
-"disuntikkan ke dalam image ketika mereka diluncurkan. Untuk pasangan kunci "
-"supaya sukses disuntikkan, image harus berisi paket ``cloud-init`` . Buat "
-"setidaknya satu sepasang kunci untuk setiap proyek. Jika Anda sudah telah "
-"menghasilkan sepasang kunci dengan alat eksternal, Anda dapat mengimpor ke "
-"OpenStack. Anda dapat menggunakan sepasang kunci untuk beberapa instance "
-"yang tergabung dalam proyek itu."
-
-msgid "A **name** for your instance."
-msgstr "**name** untuk instance Anda."
-
-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 ""
-"Sebuah **security group** (kelompok keamanan) yang mendefinisikan yang lalu "
-"lintas jaringan yang masuk diteruskan ke instance. kelompok keamanan "
-"mengadakan serangkaian kebijakan firewall, dikenal sebagai *security group "
-"rules* (aturan kelompok keamanan)."
-
-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 ""
-"*security group* adalah kumpulan nama aturan akses jaringan yang digunakan "
-"untuk membatasi tipe traffic yang memiliki akses ke instance. Ketika Anda "
-"memulai sebuah instance, Anda dapat menetapkan satu atau lebih kelompok "
-"keamanan untuk itu. Jika Anda tidak membuat kelompok keamanan, instance baru "
-"secara otomatis ditetapkan ke kelompok keamanan secara default, kecuali Anda "
-"secara eksplisit menentukan kelompok keamanan yang berbeda."
-
-msgid "A Java client offering console access to an instance"
-msgstr "Sebuah klien Java menyediakan konsol akses ke sebuah instance"
-
-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 ""
-"Sebuah timestamp jangka waktu UNIX, dalam bentuk integer. Sebagai contoh, "
-"``1348691905`` merupakan ``Wed, 26 Sept 2012 20:38:25 GMT``. Ini menentukan "
-"waktu yang Anda inginkan obyek berakhir, tidak lagi dilayani, dan dihapus "
-"sepenuhnya dari penyimpanan objek."
-
-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 ""
-"Sebuah permintaan (request) ``GET`` atau ``HEAD`` di manifes mengembalikan "
-"nilai header respon ``Content-Type`` yang sama dengan nilai header request "
-"``Content-Type`` di request ``PUT` `yang membuat manifes. Untuk mengubah "
-"``Content Type``, terbitkan kembali request ``PUT``."
-
-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 ""
-"Sebuah request (permintaan) ``POST`` ke objek berversi update hanya "
-"metadata untuk objek dan tidak membuat versi baru dari objek. Versi baru "
-"diciptakan hanya bila ada perubahan isi dari objek."
-
-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 ""
-"Sebuah ``manifest object`` menghubungkan object segmen menjadi satu objek "
-"besar logis. Ketika Anda men-download sebuah objek nyata (manifest) , Object "
-"Storage concatenate (merangkai) dan mengembalikan isi dari object segmen "
-"dalam response body. Perilaku ini meluas ke header respon dikembalikan oleh "
-"permintaan (request) `` GET`` dan ``HEAD``. Respon header ``Content-Length`` "
-"berisi ukuran total semua object segmen."
-
-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 ""
-"Sebuah instance bare-metal adalah turunan langsung dibuat pada mesin fisik, "
-"tanpa lapisan virtualisasi berjalan di bawahnya. Nova mempertahankan kontrol "
-"daya melalui IPMI. Dalam beberapa situasi, Nova mungkin mempertahankan "
-"kontrol jaringan melalui Neutron dan OpenFlow."
-
-msgid ""
-"A complete in-browser client solution for interaction with virtualized "
-"instances"
-msgstr ""
-"Solusi klien in-browser lengkap untuk interaksi dengan instance virtual"
-
-msgid "A configuration group can specify a large number of option values."
-msgstr "Sekelompok konfigurasi dapat menentukan sejumlah besar nilai pilihan."
-
-msgid ""
-"A configuration group contains a comma-separated list of key-value pairs. "
-"Each pair consists of a configuration option and its value."
-msgstr ""
-"Sebuah kelompok konfigurasi berisi daftar pasangan kunci-nilai (key-value "
-"pair) yang dipisahkan koma (comma-separated) . Setiap pasangan terdiri dari "
-"opsi konfigurasi dan nilainya."
-
-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 ""
-"Key pair milik pengguna individu, bukan untuk sebuah proyek. Untuk share key "
-"pair di beberapa pengguna, setiap pengguna perlu mengimpor sepasang kunci "
-"itu."
-
-msgid "A list of specific HTTP referer headers denied read access:"
-msgstr "Daftar header referer HTTP spesifik membantah akses baca:"
-
-msgid ""
-"A list of specific HTTP referer headers permitted to read container contents:"
-msgstr ""
-"Daftar header referer HTTP tertentu diizinkan untuk membaca konten kontainer:"
-
-msgid ""
-"A list of specific users and projects permitted to read container contents:"
-msgstr ""
-"Daftar pengguna tertentu dan proyek diizinkan untuk membaca konten kontainer:"
-
-msgid ""
-"A list of specific users and projects permitted to write to the container:"
-msgstr ""
-"Daftar pengguna tertentu dan proyek diizinkan untuk menulis ke kontainer:"
-
-msgid "A message indicates whether the action succeeded."
-msgstr "Sebuah pesan menunjukkan apakah tindakan berhasil."
-
-msgid "A message indicates whether the action was successful."
-msgstr "Sebuah pesan menunjukkan apakah aksi itu berhasil."
-
-msgid "A meter has the following attributes:"
-msgstr "Meter memiliki atribut sebagai berikut:"
-
-msgid ""
-"A pool is a group of hosts that sits behind the load balancer and serves "
-"traffic through the load balancer."
-msgstr ""
-"Sebuah kolam (pool) adalah sekelompok host yang berada di belakang "
-"penyeimbang beban dan melayani lalu lintas melalui serves traffic through "
-"the load balancer."
-
-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 ""
-"Sebuah kolam alamat IP mengambang, dikonfigurasi oleh administrator cloud, "
-"tersedia dalam OpenStack Compute. Kuota proyek mendefinisikan jumlah "
-"maksimum alamat IP mengambang yang dapat Anda alokasikan untuk proyek. "
-"Setelah Anda mengalokasikan alamat IP mengambang untuk proyek, Anda dapat:"
-
-msgid ""
-"A request with any HTTP referer header can read and list container contents:"
-msgstr ""
-"Permintaan dengan header HTTP referer dapat membaca dan mendaftar konten "
-"kontainer:"
-
-msgid "A request with any HTTP referer header can read container contents:"
-msgstr "Permintaan dengan header HTTP referer dapat membaca isi kontainer:"
-
-msgid ""
-"A series of events is generated during the lifecycle of a stack. To display "
-"lifecycle events, run the following command:"
-msgstr ""
-"Serangkaian peristiwa (event) yang dihasilkan selama siklus hidup stack. "
-"Untuk menampilkan peristiwa siklus hidup, jalankan perintah berikut:"
-
-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 ""
-"Satu set data titik agregat (data point aggregates) selama durasi waktu. "
-"(Sebaliknya, sampel merupakan titik data tunggal.) Layanan Telemetry "
-"mempekerjakan fungsi agregasi berikut:"
-
-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 ""
-"Satu set aturan yang mendefinisikan monitor dan keadaan saat ini, dengan "
-"tindakan edge-triggered terkait dengan kondisi sasaran. Alarm menyediakan "
-"berorientasi pengguna Monitoring-as-a-Service dan tujuan utilitas umum untuk "
-"OpenStack. Skala auto Orchestration adalah kasus penggunaan yang khas. Alarm "
-"mengikuti model tristate dari ``ok``, ``alarm``, dan ``insufficient data``. "
-"Untuk alarm threshold-oriented` konvensional, nilai static threshold dan "
-"operator perbandingan mengatur transisi keadaan. Operator perbandingan "
-"membandingkan statistik meteran yang dipilih terhadap window evaluasi "
-"jangka waktu dikonfigurasi ke masa lalu."
-
-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 ""
-"Sebuah share disediakan oleh penyimpanan file. Anda dapat memberikan akses "
-"untuk berbagi untuk instance. Untuk membuat dan mengelola share, Anda "
-"menggunakan perintah klien ``manila``."
-
-msgid ""
-"A slash (/) character is used as the delimiter for pseudo-folders in Object "
-"Storage."
-msgstr ""
-"Sebuah karakter garis miring (/) slash digunakan sebagai pembatas untuk "
-"pseudo-folder dalam Object Storage."
-
-msgid ""
-"A stack consists of a collection of resources. To list the resources and "
-"their status, run the following command:"
-msgstr ""
-"Tumpukan (stack) terdiri dari koleksi sumber daya. Untuk daftar sumber daya "
-"dan status, jalankan perintah berikut:"
-
-msgid "A status of ``ACTIVE`` indicates that the instance is active."
-msgstr "Sebuah status ``ACTIVE`` menunjukkan bahwa instance aktif."
-
-msgid ""
-"A status of ``BUILD`` indicates that the instance has started, but is not "
-"yet online."
-msgstr ""
-"Sebuah status ``BUILD`` menunjukkan bahwa instance telah dimulai, namun "
-"belum online."
-
-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 ""
-"Sebuah tipe, yang menunjukkan apakah nilai-nilai meningkat secara monoton "
-"(kumulatif), yang diartikan sebagai perubahan dari nilai sebelumnya (delta), "
-"atau berdiri sendiri dan hanya berhubungan dengan durasi saat ini (gauge)"
-
-msgid "A unit of measurement"
-msgstr "Sebuah unit pengukuran"
-
-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 ""
-"Sebuah file data user (user data file) adalah kunci spesial dalam layanan "
-"metadata yang memegang sebuah file dimana aplikasi cloud-aware dalam "
-"instance tamu (guest) dapat mengakses. Misalnya, salah satu aplikasi yang "
-"menggunakan sistem :term:`user data` adalah `cloud-init `__ , yang merupakan paket open-source dari Ubuntu "
-"yang tersedia di berbagai distribusi Linux dan yang menangani inisialisasi "
-"awal dari instance cloud."
-
-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 ""
-"Sebuah image mesin virtual, disebut dalam dokumen ini hanya sebagai image, "
-"adalah satu file yang berisi disk virtual yang memiliki sistem operasi "
-"bootable yang diinstal di atasnya. Image yang digunakan untuk membuat "
-"instance mesin virtual dalam cloud. Untuk informasi tentang membuat file "
-"image, lihat `OpenStack Virtual Machine Image Guide `_."
-
-msgid "A volume size of ``5`` (5 GB)."
-msgstr "Ukuran volume ``5`` (5 GB)."
-
-msgid "Abstract"
-msgstr "Abstract"
-
-msgid "Access an instance through a console"
-msgstr "Mengakses instance melalui konsol"
-
-msgid ""
-"Access and security credentials, which include one or both of the following "
-"credentials:"
-msgstr ""
-"Akses dan keamanan kredensial, yang meliputi salah satu atau kedua "
-"kredensial berikut:"
-
-msgid ""
-"Access the security group rules from the ``rules`` attribute of a "
-"`novaclient.v1\\_1.security\\_groups.SecurityGroup `__ object:"
-msgstr ""
-"Mengakses aturan kelompok keamanan dari atribut ``rules`` dari objek "
-"`novaclient.v1\\_1.security\\_groups.SecurityGroup `__:"
-
-msgid "Access-Control-Allow-Credentials"
-msgstr "Access-Control-Allow-Credentials"
-
-msgid "Access-Control-Allow-Methods"
-msgstr "Access-Control-Allow-Methods"
-
-msgid "Access-Control-Allow-Origin"
-msgstr "Access-Control-Allow-Origin"
-
-msgid "Access-Control-Expose-Headers"
-msgstr "Access-Control-Expose-Headers"
-
-msgid "Access-Control-Max-Age"
-msgstr "Access-Control-Max-Age"
-
-msgid "Access-Control-Request-Headers"
-msgstr "Access-Control-Request-Headers"
-
-msgid "Access-Control-Request-Method"
-msgstr "Access-Control-Request-Method"
-
-msgid "Activate the ports that you want to assign to the instance."
-msgstr "Aktifkan port yang ingin Anda tetapkan untuk instance."
-
-msgid "Activate the security groups that you want to assign to the instance."
-msgstr "Aktifkan kelompok keamanan yang ingin Anda tetapkan untuk instance."
-
-msgid "Add Metadata items to your instance."
-msgstr "Tambahkan item Metadata ke instance Anda."
-
-msgid "Add a key pair"
-msgstr "Menambahkan sepasang kunci (key pair)"
-
-msgid "Add a keypair"
-msgstr "Menambahkan sepasang kunci (keypair)"
-
-msgid "Add a network interface to the node"
-msgstr "Menambahkan antarmuka jaringan ke node"
-
-msgid "Add a rule to the default security group"
-msgstr "Menambahkan sebuah aturan untuk kelompok keamanan default"
-
-msgid ""
-"Add rules to default security group allowing ping and SSH between instances "
-"in the default security group"
-msgstr ""
-"Menambahkan aturan ke default grup keamanan yang memungkinkan ping dan SSH "
-"antar instance dalam kelompok keamanan default"
-
-msgid "Add the following line to ``/etc/trove/trove.conf``:"
-msgstr "Tambahkan baris berikut untuk ``/etc/trove/trove.conf``:"
-
-msgid "Additional large object arguments can be found by using ``--help``:"
-msgstr "Additional large object arguments can be found by using ``--help``:"
-
-msgid "Adds a network interface to a bare-metal node."
-msgstr "Menambahkan antarmuka jaringan ke node bare-metal."
-
-msgid ""
-"Administrative users can use the :guilabel:`Admin` tab to view usage and to "
-"manage instances, volumes, flavors, images, networks, and so on."
-msgstr ""
-"Pengguna administrasi dapat menggunakan tab :guilabel:`Admin` untuk melihat "
-"penggunaan dan untuk mengelola instance, volume, flavor, image, jaringan, "
-"dan sebagainya."
-
-msgid ""
-"After the image is successfully uploaded, you can use the new image to boot "
-"instances."
-msgstr ""
-"Setelah image berhasil diupload, Anda dapat menggunakan image baru untuk "
-"boot instance."
-
-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 ""
-"Setelah instance tersebut berhasil diluncurkan, terhubung ke instance "
-"menggunakan konsol jarak jauh dan ikuti petunjuk untuk menginstal sistem "
-"dengan menggunakan image ISO di komputer biasa. Ketika instalasi selesai dan "
-"sistem reboot, instance akan meminta Anda lagi untuk menginstal sistem "
-"operasi, yang berarti instance Anda tidak bisa digunakan. Jika Anda memiliki "
-"masalah dengan penciptaan image, periksa `Virtual Machine Image Guide "
-"`_ "
-"sebagai referensi."
-
-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 ""
-"Setelah server dibangun, jika Anda mengubah nama server di API atau mengubah "
-"hostname langsung, nama-nama tidak diperbarui di dashboard."
-
-msgid ""
-"After the stack is created, click on the stack name to see the following "
-"details:"
-msgstr ""
-"Setelah stack dibuat, klik pada nama stack untuk melihat rincian sebagai "
-"berikut:"
-
-msgid ""
-"After upload has completed, you can download the large object as a single "
-"file:"
-msgstr ""
-"After upload has completed, you can download the large object as a single "
-"file:"
-
-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 ""
-"Setelah Anda mengasosiasikan alamat IP dan mengkonfigurasi aturan kelompok "
-"keamanan instance, kemudian instance ini tersedia untuk umum di alamat IP "
-"mengambang."
-
-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 ""
-"Setelah Anda membuat satu atau lebih volume, Anda dapat menghubungkan mereka "
-"untuk instance. Anda dapat menghubungkan volume ke satu instance pada suatu "
-"waktu."
-
-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 ""
-"Setelah Anda menghapus instance, sistem yang baru saja diinstal dengan "
-"menggunakan image ISO tetap Anda, karena parameter ``shutdown=preserve`` "
-"ditetapkan, sehingga jalankan perintah berikut."
-
-msgid ""
-"After you gather required parameters, run the following command to launch an "
-"instance. Specify the server name, flavor ID, and image ID."
-msgstr ""
-"Setelah Anda mengumpulkan parameter yang diperlukan, jalankan perintah "
-"berikut untuk memulai sebuah instance. Tentukan nama server, ID flavor, dan "
-"ID image."
-
-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 ""
-"Setelah Anda mengumpulkan parameter yang Anda butuhkan untuk memulai sebuah "
-"instance, Anda dapat memulai dari sebuah :doc:`image` atau :doc:`volume`. Anda dapat memulai sebuah instance langsung dari salah satu image "
-"OpenStack tersedia atau dari image yang telah disalin ke volume persisten "
-"(volume tetap). The OpenStack layanan Image menyediakan kolam renang image "
-"yang dapat diakses oleh anggota proyek yang berbeda."
-
-msgid "Again, two items are returned, and there might be more."
-msgstr "Sekali lagi, dua barang yang dikembalikan, dan mungkin ada lebih."
-
-msgid "Alarm"
-msgstr "Alarm"
-
-msgid ""
-"All of OpenStack's APIs are actually REST APIs. The `keystoneauth `_ library provides an object that "
-"looks very much like a `Session `_ object from the Python `requests `_ library that handles all of the authentication "
-"for you. If you are more comfortable just dealing with REST or if there is a "
-"feature implemented in your cloud that has not seen support in any of the "
-"libraries yet, this option is for you."
-msgstr ""
-"Semua API OpenStack adalah benar-benar REST API. `keystoneauth `_ perpustakaan memberikan sebuah "
-"object yang terlihat sangat banyak seperti `Session `_ objek dari Python `requests "
-"`_ perpustakaan yang menangani semua "
-"otentikasi untuk Anda. Jika Anda merasa lebih nyaman hanya berurusan dengan "
-"REST atau jika ada suatu fitur yang diimplementasikan dalam cloud Anda yang "
-"belum terlihat mendapat dukungan di salah satu perpustakaan, pilihan ini "
-"adalah untuk Anda."
-
-msgid ""
-"All of the legacy client objects can be constructed the same way - the only "
-"difference is the first argument to ``make_client``. The examples will use "
-"``compute`` to get a nova client, but neutron can be accessed instead by "
-"replacing ``compute`` with ``network``."
-msgstr ""
-"Semua objek klien warisan (legacy client object) dapat dibangun dengan cara "
-"yang sama - satu-satunya perbedaan adalah argumen pertama untuk "
-"``make_client``. Contoh akan menggunakan ``compute`` untuk mendapatkan klien "
-"nova, tetapi neutron dapat diakses bukan dengan penggantian ``compute`` "
-"dengan ``network``."
-
-msgid "All segment objects must be in the same container."
-msgstr "Semua objek segmen harus dalam wadah (container) yang sama."
-
-msgid "All users residing in project1 can read container contents:"
-msgstr "Semua pengguna yang berada di project1 dapat membaca konten kontainer:"
-
-msgid "All users residing in project1 can write to the container:"
-msgstr "Semua pengguna yang berada di project1 dapat menulis ke kontainer:"
-
-msgid "Allocate a floating IP address to an instance"
-msgstr "Mengalokasikan alamat IP mengambang ke sebuah Instance"
-
-msgid ""
-"Allow UDP access from IP addresses, specified as IP subnet ``0.0.0.0/0`` in "
-"CIDR notation."
-msgstr ""
-"Mengizinkan akses UDP dari alamat IP, ditetapkan sebagai IP subnet "
-"``0.0.0.0/0`` dalam notasi CIDR."
-
-msgid "Allow access"
-msgstr "Izinkan akses"
-
-msgid ""
-"Allow access from all IP addresses, specified as IP subnet ``0.0.0.0/0`` in "
-"CIDR notation:"
-msgstr ""
-"Mengizinkan akses dari semua alamat IP, ditetapkan sebagai IP subnet "
-"``0.0.0.0/0`` dalam notasi CIDR:"
-
-msgid ""
-"Allow access only from IP addresses from other security groups (source "
-"groups) to access the specified port:"
-msgstr ""
-"Mengizinkan akses hanya dari alamat IP dari kelompok keamanan lainnya "
-"(kelompok sumber) untuk mengakses port tertentu:"
-
-msgid "Allow access."
-msgstr "Izinkan akses"
-
-msgid ""
-"Allow only IP addresses from other security groups (source groups) to access "
-"the specified port."
-msgstr ""
-"Hanya mengizinkan alamat IP dari kelompok keamanan lainnya (source groups) "
-"untuk mengakses port tertentu."
-
-msgid ""
-"Allow only members of other security groups (source groups) to ping "
-"instances."
-msgstr ""
-"Hanya mengizinkan anggota kelompok keamanan lainnya (kelompok sumber) "
-"melakukan ping instance."
-
-msgid ""
-"Allow pinging from all IP addresses, specified as IP subnet ``0.0.0.0/0`` in "
-"CIDR notation."
-msgstr ""
-"Mengizinkan ping dari semua alamat IP, ditetapkan sebagai IP subnet "
-"``0.0.0.0/0`` dalam notasi CIDR."
-
-msgid "Allow read-only access"
-msgstr "Izinkan akses read-only (read-only)"
-
-msgid "Allow read-write access"
-msgstr "Izinkan akses baca-tulis (read-write)"
-
-msgid "Also, the Bare Metal service supports the configuration drive."
-msgstr "Juga, layanan Bare Metal mendukung drive konfigurasi."
-
-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 ""
-"Meskipun Anda tidak bisa membuat sarang direktori di OpenStack Object "
-"Storage, Anda dapat mensimulasikan struktur hirarki dalam satu kontainer "
-"dengan menambahkan garis miring karakter (`` / ``) dalam nama objek. Untuk "
-"menavigasi struktur pseudo-directory, Anda dapat menggunakan parameter kueri "
-"``delimiter``. Contoh ini menunjukkan kepada Anda bagaimana menggunakan "
-"folder dan direktori pseudo-hierarchical. "
-
-msgid "An account"
-msgstr "Sebuah akun (account)"
-
-msgid ""
-"An image built with a recent version of the cloud-init package can "
-"automatically access metadata passed through the configuration drive. The "
-"following table lists the references for cloud-init versions mapped to a "
-"particular operating system:"
-msgstr ""
-"Image yang dibuat dengan versi terbaru dari paket cloud-init secara otomatis "
-"dapat mengakses metadata melewati drive konfigurasi. Tabel berikut "
-"mencantumkan referensi untuk versi cloud-init yang dipetakan ke sistem "
-"operasi tertentu:"
-
-msgid "An in-browser VNC client implemented using HTML5 Canvas and WebSockets"
-msgstr ""
-"Sebuah klien VNC in-browser diimplementasikan menggunakan HTML5 Canvas dan "
-"WebSockets"
-
-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 ""
-"Titik data individual (individual data point) yang terkait dengan meteran "
-"tertentu. Sampel memiliki atribut yang sama seperti meteran terkait, dengan "
-"penambahan waktu yang tertera dan nilai atribut. Nilai atribut juga dikenal "
-"sebagai sampel ``volume``."
-
-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 ""
-"Nilai integer yang menentukan jumlah detik dari waktu permintaan ketika Anda "
-"ingin menghapus objek. Header ini diubah menjadi header ``X-Delete-At`` yang "
-"diatur untuk jumlah dari nilai ``X-Delete-After`` ditambah waktu saat ini, "
-"dalam detik."
-
-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 ""
-"File **user data**. Sebuah file data pengguna adalah kunci spesial (special "
-"key) dalam layanan metadata yang memegang sebuah file dimana aplikasi cloud-"
-"aware dalam instance tamu (quest) dapat mengakses. Misalnya, salah satu "
-"aplikasi yang menggunakan data pengguna adalah sistem `cloud-init ` __, yang merupakan paket open-source "
-"dari Ubuntu yang tersedia di berbagai distribusi Linux dan yang menangani "
-"inisialisasi awal dari instance cloud."
-
-msgid "Any 2\\ ``nn`` response indicates success."
-msgstr "Setiap response 2\\ ``nn`` menunjukkan keberhasilan."
-
-msgid ""
-"Any modern guest operating system that is capable of mounting an ISO 9660 or "
-"VFAT file system can use the configuration drive."
-msgstr ""
-"Setiap sistem operasi guest modern yang mampu pemasangan ISO 9660 atau "
-"berkas VFAT sistem dapat menggunakan drive konfigurasi."
-
-msgid ""
-"Append this parameter to the URL for a ``GET`` request, where ``format`` is "
-"``json`` or ``xml``."
-msgstr ""
-"Menambahkan parameter ini ke URL untuk permintaan ``GET``, dimana ``format`` "
-"adalah ``json`` atau ``xml``."
-
-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 ""
-"Sebagai pengguna akhir cloud (cloud end user), Anda dapat menggunakan "
-"dashboard OpenStack untuk penyediaan sumber daya Anda sendiri dalam batas "
-"yang ditetapkan oleh administrator. Anda dapat mengubah contoh yang "
-"diberikan dalam bagian ini untuk membuat tipe dan ukuran instance server "
-"lainnya."
-
-msgid ""
-"As an OpenStack cloud end user, you can provision your own resources within "
-"the limits set by cloud administrators."
-msgstr ""
-"Sebagai pengguna akhir cloud OpenStack, Anda bisa menyediakan sumber daya "
-"Anda sendiri dalam batas yang ditetapkan oleh administrator cloud."
-
-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 ""
-"Sebagai pengguna akhir (end user), Anda dapat membuat dan mengelola "
-"penyeimbang beban (load balancer) dan benda-benda terkait untuk pengguna "
-"dalam berbagai proyek. Anda juga dapat menghapus penyeimbang beban dan obyek "
-"terkait."
-
-msgid ""
-"As an example, see the sample shell file that sets these variables to get "
-"credentials:"
-msgstr ""
-"Sebagai contoh, lihat file shell contoh yang menetapkan variabel tersebut "
-"untuk mendapatkan mandat (credential):"
-
-msgid ""
-"As background, assume that you have created a database instance with the "
-"following characteristics:"
-msgstr ""
-"Sebagai latar belakang, menganggap bahwa Anda telah membuat instance "
-"database dengan karakteristik sebagai berikut:"
-
-msgid ""
-"As shown in this example, the public URL appears in the ``StorageURL`` "
-"field, and the token appears in the ``Auth Token`` field:"
-msgstr ""
-"Seperti ditunjukkan dalam contoh ini, URL publik muncul dalam field "
-"``StorageURL``, dan token muncul di field ``Auth Token`` :"
-
-msgid ""
-"As you can see, the ``sync_binlog`` option is currently set to ``0`` for the "
-"``myDB7`` database."
-msgstr ""
-"Seperti yang Anda lihat, opsi ``sync_binlog`` saat ini diatur ke ``0`` untuk "
-"database ``myDB7``."
-
-msgid ""
-"As you can see, the ``sync_binlog`` option is now set to ``1``, as specified "
-"in the ``group1`` configuration group."
-msgstr ""
-"Seperti yang Anda lihat, opsi ``sync_binlog`` ini telah diatur untuk ``1``, "
-"sebagaimana ditentukan dalam kelompok konfigurasi ``group1``."
-
-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 ""
-"Meminta operator cloud untuk nama host atau alamat IP publik dari mana Anda "
-"dapat mengakses dashboard, dan untuk nama pengguna dan password. Jika cloud "
-"mendukung model multi-domain, Anda juga perlu menanyakan nama domain Anda."
-
-msgid "Assign CORS headers to requests"
-msgstr "Menetapkan header CORS untuk permintaan (request)"
-
-msgid "Assign a name to the virtual machine."
-msgstr "Menetapkan nama untuk mesin virtual."
-
-msgid "Associate an IP address with an instance in the project, as follows:"
-msgstr ""
-"Mengasosiasikan alamat IP dengan sebuah instance dalam proyek, sebagai "
-"berikut:"
-
-msgid "Associate floating IP addresses"
-msgstr "Lakukan asosiasi alamat IP mengambang"
-
-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 ""
-"Mengasosiasikan alamat IP mengambang dengan instance proyek. Hanya satu "
-"alamat IP mengambang dapat dialokasikan ke sebuah instance pada waktu "
-"tertentu."
-
-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 ""
-"Asumsikan bahwa Anda telah menginstal layanan Database dan dihuni "
-"penyimpanan data Anda dengan image untuk tipe dan versi database yang Anda "
-"inginkan, dan bahwa Anda dapat membuat dan mengakses database."
-
-msgid "Assume the following list of container names:"
-msgstr "Asumsikan berikut daftar nama kontainer:"
-
-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 ""
-"Terjamin. Daftar segmen memasukkan MD5 checksum (``ETag``) dari setiap "
-"segmen. Anda tidak dapat meng-upload objek nyata (manifest) jika ``ETag`` "
-"dalam daftar berbeda dari objek segmen upload. Jika segmen hilang, upaya "
-"untuk men-download hasil objek nyata dalam kesalahan."
-
-msgid "At the prompt, type ``yes``."
-msgstr "Pada prompt, ketik ``yes``."
-
-msgid ""
-"At this point, you might want to delete the disabled ``guest1`` instance, by "
-"using the :command:`trove delete` command."
-msgstr ""
-"Pada titik ini, Anda mungkin ingin menghapus instance ``guest1`` disabled, "
-"dengan menggunakan perintah :command:`trove delete`."
-
-msgid "Attach a volume to an instance"
-msgstr "Hubungkan volume ke sebuah instance"
-
-msgid ""
-"Attach a volume to an instance after the instance is active, and the volume "
-"is available"
-msgstr ""
-"Hubungkan volume ke sebuah instance setelah instance aktif, dan volume "
-"tersedia"
-
-msgid "Attach swap or ephemeral disk to an instance"
-msgstr ""
-"Menghubungkan swap atau fana disk (ephemeral disk) pada sebuah instance"
-
-msgid "Attach the configuration group to the database instance:"
-msgstr "Menghubungkan kelompok konfigurasi ke instance database:"
-
-msgid "Attach the instance to the volume:"
-msgstr "Hubungkan instance ke volume:"
-
-msgid "Authenticate"
-msgstr "Authenticate (membuktikan)"
-
-msgid "Auto-extract archive files"
-msgstr "File arsip auto-ekstrak"
-
-msgid "Auto-extract archive request"
-msgstr "Permintaan arsip auto-extract"
-
-msgid "Auto-extract archive response"
-msgstr "Tanggapan (response) arsip auto-extract"
-
-msgid "Availability Zone"
-msgstr "Zona Tersedia (Availability Zone)"
-
-msgid "Available Metadata"
-msgstr "Metadata tersedia"
-
-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 ""
-"Back up database instance dengan menggunakan perintah :command:`trove backup-"
-"create`. Dalam contoh ini, cadangan ini disebut ``backup1``. Dalam contoh "
-"ini, menggantikan ``INSTANCE_ID`` dengan ``97b4b853-80f6-414f-ba6f-"
-"c6f455a79ae6``:"
-
-msgid "Backup and restore a database"
-msgstr "Backup and restore database (cadangan dan mengembalikan database)"
-
-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 ""
-"Berdasarkan pilihan Anda untuk :guilabel:`Image Source`, Anda memasukkan URL "
-"lokasi image di field (kolom) :guilabel:`Image Location`, atau cari file "
-"image pada sistem file Anda dan menambahkannya."
-
-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 ""
-"Karena dashboard tidak membiarkan Anda memilih datastore spesifik untuk "
-"digunakan dengan sebuah instance, Anda perlu mengkonfigurasi datastore "
-"default. Dashboard kemudian menggunakan datastore standar untuk membuat "
-"instance."
-
-msgid "Because two container names are returned, there are more names to list."
-msgstr "Karena dua nama kontainer dikembalikan, ada lebih nama untuk daftar."
-
-msgid "Before you begin, source the OpenStack RC file."
-msgstr "Sebelum Anda mulai, dapatkan sumber file OpenStack RC."
-
-msgid "Before you can launch an instance, gather the following parameters:"
-msgstr ""
-"Sebelum Anda dapat memulai sebuah instance, kumpulkan parameter berikut:"
-
-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 ""
-"Sebelum Anda dapat meng-upload object yang lebih besar dari 5 GB, Anda harus "
-"memotong mereka. Anda meng-upload object segmen seperti yang Anda lakukan "
-"dengan object lain dan menciptakan dinamika objek nyata (manifest) besar. "
-"Objek manifest memberitahu Object Storage bagaimana menemukan object segmen "
-"yang terdiri dari objek besar. Anda masih dapat mengakses setiap segmen "
-"individual, tetapi ketika Anda mengambil objek nyata, API merangkai segmen. "
-"Anda dapat menyertakan sejumlah segmen dalam sebuah objek tunggal yang besar."
-
-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 ""
-"Sebelum Anda memulai sebuah instance, Anda harus menambahkan aturan kelompok "
-"keamanan untuk mengaktifkan pengguna melakukan ping dan menggunakan SSH "
-"untuk koneksi ke instance. Kelompok keamanan adalah set aturan filter IP "
-"yang mendefinisikan jaringan akses dan diterapkan untuk semua instance dalam "
-"suatu proyek. Untuk melakukannya, Anda menambah aturan untuk kelompok "
-"keamanan default :ref: `security_groups_add_rule` ataupun menambahkan "
-"kelompok keamanan baru dengan aturan."
-
-msgid ""
-"Before you run commands, `set environment variables using the OpenStack RC "
-"file `_."
-msgstr ""
-"Sebelum Anda menjalankan perintah, `set environment variables using the "
-"OpenStack RC file `_."
-
-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 ""
-"Sebelum Anda menggunakan kelompok konfigurasi yang baru dibuat (newly-"
-"created configuration group), lihat bagaimana opsi ``sync_binlog`` "
-"dikonfigurasi pada database Anda. Gantilah nilai hubungan sampel berikut "
-"dengan nilai yang menghubungkan ke database Anda:"
-
-msgid "Block Storage (cinder)"
-msgstr "Block Storage (cinder)"
-
-msgid "Boot a new instance from the snapshot"
-msgstr "Boot instance baru dari snapshot"
-
-msgid "Boot an instance and attach to volume"
-msgstr "Boot instance dan mengkaitkan volume"
-
-msgid "Boot an instance from an ISO image"
-msgstr "Boot sebuah instance dari sebuah image ISO"
-
-msgid "Boot an instance from an image and attach a non-bootable volume."
-msgstr ""
-"Boot sebuah instance dari sebuah image dan menghubungkan volume non-"
-"bootable."
-
-msgid "Boot an instance using flavor and image names (if names are unique)"
-msgstr ""
-"Boot instance menggunakan nama flavor dan image (jika mempunyai nama unik)"
-
-msgid "Boot from image"
-msgstr "Boot dari image"
-
-msgid "Boot from image (creates a new volume)"
-msgstr "Boot dari image (menciptakan volume baru)"
-
-msgid "Boot from snapshot"
-msgstr "Boot dari snapshot"
-
-msgid "Boot from volume"
-msgstr "Boot dari volume"
-
-msgid "Boot from volume snapshot (creates a new volume)"
-msgstr "Boot dari volume snapshot (menciptakan volume baru)"
-
-msgid "Boot instance from image and attach non-bootable volume"
-msgstr "Boot instance dari image dan menghubungkan volume non-bootable"
-
-msgid "Browse to and select the file that you want to upload."
-msgstr "Browse ke dan pilih file yang ingin Anda upload."
-
-msgid "Bulk delete"
-msgstr "Bulk delete (penghapusan massal)"
-
-msgid "Bulk delete request"
-msgstr "Bulk delete request (permintaan penghapusan massal)"
-
-msgid "Bulk delete response"
-msgstr "Bulk delete response (tanggapan penghapusan massal)"
-
-msgid "Bulk-configure a database or databases"
-msgstr "Konfigurasi massal database (bulk-configure database) "
-
-msgid ""
-"By default, the :command:`openstack server 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 operating system is allowed to complete the shutdown. The default "
-"timeout is 60 seconds. See `Description of Compute configuration options "
-"`_ for details."
-msgstr ""
-"By default, the :command:`openstack server 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 operating system is allowed to complete the shutdown. The default "
-"timeout is 60 seconds. See `Description of Compute configuration options "
-"`_ for details."
-
-msgid ""
-"By default, the :command:`openstack server shelve` command gives the guest "
-"operating system a chance to perform a controlled shutdown before the "
-"instance is powered off. The shutdown behavior is configured by the "
-"``shutdown_timeout`` parameter that can be set in the :file:`nova.conf` "
-"file. Its value stands for the overall period (in seconds) a guest operating "
-"system is allowed to complete the shutdown. The default timeout is 60 "
-"seconds. See `Description of Compute configuration options `_ for "
-"details."
-msgstr ""
-"By default, the :command:`openstack server shelve` command gives the guest "
-"operating system a chance to perform a controlled shutdown before the "
-"instance is powered off. The shutdown behavior is configured by the "
-"``shutdown_timeout`` parameter that can be set in the :file:`nova.conf` "
-"file. Its value stands for the overall period (in seconds) a guest operating "
-"system is allowed to complete the shutdown. The default timeout is 60 "
-"seconds. See `Description of Compute configuration options `_ for "
-"details."
-
-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 ""
-"Secara default, Object Storage API menggunakan format respon ``text/"
-"plain`` . Selain itu, kedua format respon serialisasi data JSON dan XML juga "
-"didukung."
-
-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 ""
-"Secara default, isi dari sebuah objek tidak dapat lebih besar dari 5 GB. "
-"Namun, Anda dapat menggunakan sejumlah objek yang lebih kecil untuk "
-"membangun sebuah objek besar. Objek besar terdiri dari dua jenis object:"
-
-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 ""
-"Secara default, nilai ini diatur ke zona ketersediaan (availability zone) "
-"diberikan oleh penyedia cloud (for example, ``us-west`` atau ``apac-"
-"south``). Untuk beberapa kasus, hal itu bisa menjadi ``nova``."
-
-msgid "By default, when you reboot an instance, it is a soft reboot."
-msgstr ""
-"Secara default, ketika Anda reboot sebuah instance, itu adalah reboot lembut."
-
-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 ""
-"Secara default, Anda tidak dapat menghubungkan image drive konfigurasi "
-"sebagai drive CD bukan sebagai disk drive. Untuk menghubungkan CD drive, "
-"tambahkan baris berikut ke file ``/etc/nova/nova.conf``:"
-
-msgid "Call ``print_server`` again to check the update server details:"
-msgstr ""
-"Call (panggil) ``print_server``lagi untuk memeriksa rincian update server:"
-
-msgid ""
-"Call ``server.update`` on the server object with the new value for ``name`` "
-"variable:"
-msgstr ""
-"Call (panggil) ``server.update`` pada objek server dengan nilai baru untuk "
-"variable ``name``:"
-
-msgid "Cassandra"
-msgstr "Cassandra"
-
-msgid "Change the name of the image."
-msgstr "Mengubah nama image."
-
-msgid "Change the size of a server by changing its flavor."
-msgstr "Mengubah ukuran server dengan mengubah flavor."
-
-msgid "Change the size of your server"
-msgstr "Mengubah ukuran server Anda"
-
-msgid "Check if the instance is online."
-msgstr "Periksa apakah instance yang online."
-
-msgid "Check the backup you want to use and click :guilabel:`Restore Backup`."
-msgstr ""
-"Periksa cadangan (backup) yang ingin Anda gunakan dan klik :guilabel:"
-"`Restore Backup`."
-
-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 ""
-"Periksa instance dimana Anda ingin bekerja dengannya.. Dalam kolom :"
-"guilabel:`Actions`, perluas drop down menu dan pilih :guilabel:`Resize "
-"Instance`."
-
-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 ""
-"Periksa instance dimana Anda ingin bekerja dengannya. Dalam kolom :guilabel:"
-"`Actions`, perluas drop down menu dan pilih :guilabel:`Resize Volume`."
-
-msgid ""
-"Choose the image source from the dropdown list. Your choices are :guilabel:"
-"`Image Location` and :guilabel:`Image File`."
-msgstr ""
-"Pilih sumber image dari daftar dropdown. Pilihan Anda adalah :guilabel:"
-"`Image Location` dan :guilabel:`Image File`."
-
-msgid "Choose the pool from which to pick the IP address."
-msgstr "Pilih kolam (pool) untuk memilih alamat IP."
-
-msgid "Choose the rule you want to delete."
-msgstr "Pilih aturan yang ingin Anda hapus."
-
-msgid ""
-"Choose the source of the environment from the list. The environment files "
-"contain additional settings for the stack."
-msgstr ""
-"Pilih sumber lingkungan dari daftar. File lingkungan berisi pengaturan "
-"tambahan untuk stack."
-
-msgid "Choose the source of the template from the list."
-msgstr "Pilih sumber template dari daftar."
-
-msgid "Clear the :guilabel:`Public` check box to make the image private."
-msgstr "Bersihkan check box :guilabel:`Public` untuk membuat image private."
-
-msgid "Click :guilabel:`Add Interface`."
-msgstr "Klik :guilabel:`Add Interface`."
-
-msgid "Click :guilabel:`Add Rule`."
-msgstr "Klik :guilabel:`Add Rule`."
-
-msgid "Click :guilabel:`Add rule`."
-msgstr "Klik :guilabel:`Add rule`."
-
-msgid "Click :guilabel:`Add`."
-msgstr "Klik :guilabel:`Add`."
-
-msgid "Click :guilabel:`Allocate IP To Project`."
-msgstr "Klik :guilabel:`Allocate IP To Project`."
-
-msgid "Click :guilabel:`Allocate IP`."
-msgstr "Klik :guilabel:`Allocate IP`."
-
-msgid "Click :guilabel:`Associate`."
-msgstr "Klik :guilabel:`Associate`."
-
-msgid "Click :guilabel:`Attach Volume`."
-msgstr "Klik :guilabel:`Attach Volume`."
-
-msgid "Click :guilabel:`Backup`. The new backup appears in the backup list."
-msgstr ""
-"Klik :guilabel:`Backup`. Cadangan (backup) baru muncul dalam daftar cadangan."
-
-msgid "Click :guilabel:`Change Stack Template`."
-msgstr "Klik :guilabel:`Change Stack Template`."
-
-msgid "Click :guilabel:`Container`."
-msgstr "Klik :guilabel:`Container`."
-
-msgid "Click :guilabel:`Copy Object`."
-msgstr "Klik :guilabel:`Copy Object`."
-
-msgid "Click :guilabel:`Create Backup`."
-msgstr "Klik :guilabel:`Create Backup`."
-
-msgid "Click :guilabel:`Create Image`."
-msgstr "Klik :guilabel:`Create Image`."
-
-msgid "Click :guilabel:`Create Key Pair`."
-msgstr "Klik :guilabel:`Create Key Pair`."
-
-msgid "Click :guilabel:`Create Network`."
-msgstr "Klik :guilabel:`Create Network`."
-
-msgid "Click :guilabel:`Create Port`."
-msgstr "Click :guilabel:`Create Port`."
-
-msgid "Click :guilabel:`Create Pseudo-folder`."
-msgstr "Klik :guilabel:`Create Pseudo-folder`."
-
-msgid "Click :guilabel:`Create Router`."
-msgstr "Click :guilabel:`Create Router`."
-
-msgid "Click :guilabel:`Create Security Service`."
-msgstr "Klik :guilabel:`Create Security Service`."
-
-msgid "Click :guilabel:`Create Share Network`."
-msgstr "Klik :guilabel:`Create Share Network`."
-
-msgid "Click :guilabel:`Create Share`."
-msgstr "Klik :guilabel:`Create Share`."
-
-msgid "Click :guilabel:`Create Volume`."
-msgstr "Klik :guilabel:`Create Volume`."
-
-msgid "Click :guilabel:`Create`."
-msgstr "Klik :guilabel:`Create`."
-
-msgid "Click :guilabel:`Delete Images`."
-msgstr "Klik :guilabel:`Delete Images`."
-
-msgid "Click :guilabel:`Delete Security Services` and confirm your choice."
-msgstr ""
-"Klik :guilabel:`Delete Security Services` dan mengkonfirmasi pilihan Anda."
-
-msgid "Click :guilabel:`Delete Share Networks` and confirm your choice."
-msgstr ""
-"Klik :guilabel:`Delete Share Networks` dan mengkonfirmasi pilihan Anda."
-
-msgid "Click :guilabel:`Delete Shares` and confirm your choice."
-msgstr "Klik :guilabel:`Delete Shares` dan mengkonfirmasi pilihan Anda."
-
-msgid "Click :guilabel:`Delete Stack`."
-msgstr "Klik :guilabel:`Delete Stack`."
-
-msgid "Click :guilabel:`Delete Volumes` and confirm your choice."
-msgstr "Klik :guilabel:`Delete Volumes` dan mengkonfirmasi pilihan Anda."
-
-msgid "Click :guilabel:`Delete rule` and confirm your choice."
-msgstr "Klik :guilabel:`Delete rule` dan mengkonfirmasi pilihan Anda."
-
-msgid "Click :guilabel:`Detach Volume` and confirm your changes."
-msgstr "Klik :guilabel:`Detach Volume` dan mengkonfirmasi perubahan."
-
-msgid "Click :guilabel:`Edit Image`."
-msgstr "Klik :guilabel:`Edit Image`."
-
-msgid "Click :guilabel:`Edit Security Service`."
-msgstr "Klik :guilabel:`Edit Security Service`."
-
-msgid "Click :guilabel:`Edit Share Metadata`."
-msgstr "Klik :guilabel:`Edit Share Metadata`."
-
-msgid "Click :guilabel:`Edit Share Network`."
-msgstr "Klik :guilabel:`Edit Share Network`."
-
-msgid "Click :guilabel:`Edit Share`."
-msgstr "Klik :guilabel:`Edit Share`."
-
-msgid "Click :guilabel:`Edit Volume`."
-msgstr "Klik :guilabel:`Edit Volume`."
-
-msgid "Click :guilabel:`Extend Share`."
-msgstr "Klik :guilabel:`Extend Share`."
-
-msgid "Click :guilabel:`Import Key Pair`."
-msgstr "Klik :guilabel:`Import Key Pair`."
-
-msgid "Click :guilabel:`Launch Instance`."
-msgstr "Klik :guilabel:`Launch Instance`."
-
-msgid "Click :guilabel:`Launch Stack`."
-msgstr "Klik :guilabel:`Launch Stack`."
-
-msgid ""
-"Click :guilabel:`Launch` to create a stack. The :guilabel:`Stacks` tab shows "
-"the stack."
-msgstr ""
-"Klik :guilabel:`Launch` untuk buat stack. Tab :guilabel:`Stacks` menunjukkan "
-"tumpukan (stack)."
-
-msgid "Click :guilabel:`Launch`."
-msgstr "Klik :guilabel:`Launch`."
-
-msgid "Click :guilabel:`Next`."
-msgstr "Click :guilabel:`Next`."
-
-msgid "Click :guilabel:`Resize Database Instance`."
-msgstr "Klik :guilabel:`Resize Database Instance`."
-
-msgid "Click :guilabel:`Resize Database Volume`."
-msgstr "Klik :guilabel:`Resize Database Volume`."
-
-msgid "Click :guilabel:`Update Object`."
-msgstr "Klik :guilabel:`Update Object`."
-
-msgid "Click :guilabel:`Update`."
-msgstr "Klik :guilabel:`Update`."
-
-msgid "Click :guilabel:`Upload File`."
-msgstr "Klik :guilabel:`Upload File`."
-
-msgid "Click :guilabel:`Upload Object`."
-msgstr "Klik :guilabel:`Upload Object`."
-
-msgid ""
-"Click on the :guilabel:`Network Name` of the network in which the port has "
-"to be created."
-msgstr "Klik pada :guilabel:`Network Name` jaringan dimana port harus dibuat."
-
-msgid "Click the :guilabel:`Create Load Balancer` button."
-msgstr "Klik tombol :guilabel:`Create Load Balancer`."
-
-msgid ""
-"Click the :guilabel:`Floating IPs` tab, which shows the floating IP "
-"addresses allocated to instances."
-msgstr ""
-"Klik tab :guilabel:`Floating IPs`, yang menunjukkan alamat IP mengambang "
-"dialokasikan untuk Instance."
-
-msgid ""
-"Click the :guilabel:`Key Pairs` tab, which shows the key pairs that are "
-"available for this project."
-msgstr ""
-"Klik tab :guilabel:`Key Pairs`, yang menunjukkan pasangan kunci (key pair) "
-"yang tersedia untuk proyek ini."
-
-msgid ""
-"Click the :guilabel:`Launch` button. The new database instance appears in "
-"the databases list."
-msgstr ""
-"Klik tombol :guilabel:`Launch`. Instance database baru muncul dalam daftar "
-"database."
-
-msgid ""
-"Click the :guilabel:`Restore From Database` tab and make sure that this new "
-"instance is based on the correct backup."
-msgstr ""
-"Klik tab :guilabel:`Restore From Database` dan pastikan bahwa instance baru "
-"ini didasarkan pada cadangan (backup) yang benar."
-
-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 ""
-"Klik tombol :guilabel:`Settings` dari pengguna drop down menu di bagian "
-"kanan atas halaman manapun, Anda akan melihat tab :guilabel:`Settings`."
-
-msgid "Click the :guilabel:`Upload File` icon."
-msgstr "Klik icon :guilabel:`Upload File`."
-
-msgid ""
-"Click the menu button and choose :guilabel:`Copy` from the dropdown list."
-msgstr "Klik tombol menu dan pilih :guilabel:`Copy` dari daftar dropdown."
-
-msgid ""
-"Click the menu button and choose :guilabel:`Edit` from the dropdown list."
-msgstr "Klik tombol menu dan pilih :guilabel:`Edit` dari daftar dropdown."
-
-msgid "Commands"
-msgstr "Commands (perintah)"
-
-msgid "Comparison of static and dynamic large objects"
-msgstr "Perbandingan object besar (large object) statis dan dinamis "
-
-msgid "Compute"
-msgstr "Compute (komputasi)"
-
-msgid "Compute (nova)"
-msgstr "Compute (nova)"
-
-msgid "Compute tab"
-msgstr "Compute tab"
-
-msgid "Configuration drive contents"
-msgstr "Isi drive konfigurasi"
-
-msgid "Configuration drive format"
-msgstr "Format drive konfigurasi"
-
-msgid "Configure access and security for instances"
-msgstr "Mengkonfigurasi akses dan keamanan untuk instance"
-
-msgid "Confirm the resize,for example:"
-msgstr "Konfirmasi mengubah ukuran, misalnya:"
-
-msgid "Confirm your changes."
-msgstr "Mengonfirmasi perubahan."
-
-msgid "Connect to your instance by using SSH"
-msgstr "Terhubung ke instance Anda dengan menggunakan SSH"
-
-msgid "Contents"
-msgstr "Contents (konten)"
-
-msgid "Copy the IP address for your instance."
-msgstr "Salin alamat IP instance Anda."
-
-msgid ""
-"Copy the administrative password value from the ``adminPass`` field. Use the "
-"password to log in to your server."
-msgstr ""
-"Salin nilai password administrasi dari field ``adminPass``. Gunakan password "
-"untuk login ke server Anda."
-
-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 ""
-"Salin Server ID value dari field ``id`` dalam output. Gunakan ID untuk "
-"mendapatkan rincian server atau menghapus server Anda."
-
-msgid "Copying the manifest object"
-msgstr "Menyalin objek manifest"
-
-msgid "Count"
-msgstr "Count"
-
-msgid "Create a Legacy Client Object"
-msgstr "Create a Legacy Client Object (buat objek klien warisan) "
-
-msgid "Create a ``current`` container to store current versions of objects."
-msgstr ""
-"Buat wadah (container) ``current`` untuk menyimpan versi saat ini dari objek."
-
-msgid "Create a bare-metal node"
-msgstr "Buat node bare-metal."
-
-msgid "Create a bootable volume for the instance to reside on after shutdown."
-msgstr "Buat volume bootable instance untuk diam setelah shutdown."
-
-msgid ""
-"Create a bootable volume from an image. Cinder makes a volume bootable when "
-"``--image`` parameter is passed."
-msgstr ""
-"Buat volume bootable dari sebuah image. Cinder membuat bootable volume saat "
-"parameter ``--image`` dilewatkan."
-
-msgid ""
-"Create a cluster by using the :command:`trove cluster-create` command. This "
-"command creates a one-shard cluster. Pass in:"
-msgstr ""
-"Buat sebuah cluster dengan menggunakan perintah :command:`trove cluster-"
-"create`. Perintah ini akan membuat kluster one-shard. Lewatkan di:"
-
-msgid "Create a container"
-msgstr "Buat sebuah wadah (container)"
-
-msgid "Create a database instance"
-msgstr "Buat instance database"
-
-msgid "Create a file on the volume"
-msgstr "Buat file pada volume"
-
-msgid "Create a flavor named m1.tiny"
-msgstr "Buatlah flavor bernama m1.tiny"
-
-msgid "Create a flavor."
-msgstr "Membuat flavor."
-
-msgid "Create a load balancer"
-msgstr "Buat load balancer (penyeimbang beban)"
-
-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 ""
-"Buat objek nyata (manifest). Sertakan query string ``?multipart-"
-"manifest=put`` pada akhir nama objek nyata untuk menunjukkan bahwa ini "
-"adalah objek nyata."
-
-msgid "Create a mountpoint"
-msgstr "Buat mountpoint "
-
-msgid "Create a network"
-msgstr "Membuat jaringan (network)"
-
-msgid "Create a network with specified provider network type."
-msgstr "Membuat jaringan dengan ditentukan jenis jaringan penyedia."
-
-msgid "Create a network:"
-msgstr "Membuat jaringan:"
-
-msgid "Create a new flavor."
-msgstr "Create a new flavor."
-
-msgid ""
-"Create a new instance that will be a replica of the original instance. You "
-"do this by passing in the ``--replica_of`` option with the :command:`trove "
-"create` command. This example creates a replica called ``replica_1``. "
-"``replica_1`` is a replica of the original instance, ``base_1``:"
-msgstr ""
-"Buat instance baru yang akan menjadi replika instance asli. Anda melakukan "
-"ini dengan melewati dalam opsi ``--replica_of`` dengan perintah :command:"
-"`trove create`. Contoh ini membuat replika yang disebut ``replica_1``. "
-"``replica_1`` adalah replika instance asli, ``base_1``:"
-
-msgid "Create a new volume"
-msgstr "Membuat volume baru"
-
-msgid ""
-"Create a non-bootable volume and attach that volume to an instance that you "
-"boot from an image."
-msgstr ""
-"Membuat volume non-bootable dan menghubungkan dimana volume ke sebuah "
-"instance dimana Anda boot dari sebuah image."
-
-msgid "Create a non-bootable volume."
-msgstr "Membuat volume non-bootable."
-
-msgid "Create a port"
-msgstr "Buat port"
-
-msgid "Create a port with specified IP address:"
-msgstr "Membuat port dengan alamat IP tertentu:"
-
-msgid "Create a port without specified IP address:"
-msgstr "Membuat port tanpa alamat IP tertentu:"
-
-msgid "Create a router"
-msgstr "Buat router"
-
-msgid "Create a router and add a port to the subnet:"
-msgstr "Buat router dan menambahkan port untuk subnet:"
-
-msgid "Create a router:"
-msgstr "Buat router:"
-
-msgid "Create a second version of the object in the ``current`` container:"
-msgstr "Membuat versi kedua dari objek dalam kontainer ``current``:"
-
-msgid "Create a server with 512 MB swap disk and 2 GB ephemeral disk."
-msgstr "Create a server with 512 MB swap disk and 2 GB ephemeral disk."
-
-msgid "Create a share"
-msgstr "Buat share"
-
-msgid "Create a share from a snapshot."
-msgstr "Buat share dari snapshot."
-
-msgid "Create a share network"
-msgstr "Buat jaringan bersama (share)"
-
-msgid "Create a share network."
-msgstr "Buat jaringan bersama (share)"
-
-msgid "Create a share."
-msgstr "Buat share"
-
-msgid "Create a snapshot from a volume"
-msgstr "Membuat snapshot dari volume"
-
-msgid "Create a snapshot of the instance"
-msgstr "Membuat snapshot dari instance"
-
-msgid "Create a snapshot."
-msgstr "Membuat snapshot."
-
-msgid "Create a stack from an example template file"
-msgstr "Membuat tumpukan (stack) dari file template contoh"
-
-msgid "Create a subnet"
-msgstr "Buat subnet"
-
-msgid "Create a subnet of the ``public`` external network:"
-msgstr "Buat subnet dari jaringan eksternal ``public``:"
-
-msgid "Create a subnet:"
-msgstr "Buat subnet:"
-
-msgid "Create a volume"
-msgstr "Buat volume"
-
-msgid "Create a volume from an image and boot an instance from that volume."
-msgstr ""
-"Membuat volume dari sebuah image dan boot sebuah instance dari volume "
-"tersebut."
-
-msgid "Create an ``archive`` container to store older versions of objects:"
-msgstr "Buat wadah (container) ``archive`` untuk menyimpan versi objek:"
-
-msgid "Create an additional container to hold previous versions:"
-msgstr "Create an additional container to hold previous versions:"
-
-msgid "Create an archive for auto-extract"
-msgstr "Buat arsip untuk auto-extract"
-
-msgid ""
-"Create an auto-scaling stack by running the following command. The ``-f`` "
-"option specifies the name of the stack template file, and the ``-P`` option "
-"specifies the ``KeyName`` parameter as ``heat_key``:"
-msgstr ""
-"Buat tumpukan auto-scaling dengan menjalankan perintah berikut. Opsi ``-f`` "
-"menentukan nama file stack template, dan opsi ``-P`` menentukan parameter "
-"``KeyName`` sebagai ``heat_key``:"
-
-msgid "Create an external network"
-msgstr "Buat jaringan eksternal"
-
-msgid "Create an external network named ``public``:"
-msgstr "Buat jaringan eksternal bernama ``public``:"
-
-msgid "Create an image"
-msgstr "Membuat image"
-
-msgid "Create an instance snapshot"
-msgstr "Create instance snapshot"
-
-msgid "Create and access a database"
-msgstr "Membuat dan mengakses database"
-
-msgid "Create and apply a module to a mysql database"
-msgstr "Buat dan terapkan modul ke database mysql"
-
-msgid "Create and manage containers"
-msgstr "Membuat dan mengelola wadah (container)"
-
-msgid "Create and manage databases"
-msgstr "Membuat dan mengelola database"
-
-msgid "Create and manage networks"
-msgstr "Membuat dan mengelola jaringan"
-
-msgid "Create and manage object containers"
-msgstr "Membuat dan mengelola wadah objek (object container)"
-
-msgid "Create and manage security group rules"
-msgstr "Membuat dan mengelola aturan kelompok keamanan"
-
-msgid "Create and manage security groups"
-msgstr "Membuat dan mengelola kelompok keamanan"
-
-msgid "Create and manage shares"
-msgstr "Membuat dan mengelola share"
-
-msgid "Create and manage stacks"
-msgstr "Membuat dan mengelola tumpukan (stack)"
-
-msgid "Create and manage volumes"
-msgstr "Membuat dan mengelola volume"
-
-msgid "Create and use incremental backups"
-msgstr "Membuat dan menggunakan inkremental backup (cadangan) "
-
-msgid "Create and use modules for a database"
-msgstr "Buat dan gunakan modul untuk database"
-
-msgid "Create at least one key pair for each project."
-msgstr "Buat setidaknya satu sepasang kunci (key pair) untuk setiap proyek."
-
-msgid "Create keypair"
-msgstr "Buat keypair"
-
-msgid "Create network"
-msgstr "Buat jaringan (network)"
-
-msgid "Create networks"
-msgstr "Membuat jaringan:"
-
-msgid "Create ports"
-msgstr "Buat port"
-
-msgid "Create router and add port to subnet"
-msgstr "Buat router dan menambahkan port subnet"
-
-msgid "Create router: complete code listing example"
-msgstr "Buat router: kode lengkap daftar contoh"
-
-msgid "Create routers"
-msgstr "Buat router"
-
-msgid "Create security service"
-msgstr "Membuat layanan keamanan"
-
-msgid "Create server (API v2)"
-msgstr "Membuat server (API v2)"
-
-msgid "Create server code listing example"
-msgstr "Buat kode server pendaftaran contoh"
-
-msgid "Create share from snapshot"
-msgstr "Buat share dari snapshot"
-
-msgid "Create share network"
-msgstr "Buat jaringan bersama"
-
-msgid "Create snapshot"
-msgstr "Buat snapshot"
-
-msgid "Create static website"
-msgstr "Buat website statis"
-
-msgid "Create subnets"
-msgstr "Buat subnet"
-
-msgid "Create the first version of an object in the ``current`` container:"
-msgstr "Buat versi pertama dari sebuah objek dalam kontainer ``current``:"
-
-msgid "Create the volume:"
-msgstr "Buat volume:"
-
-msgid "Create volume from image and boot instance"
-msgstr "Membuat volume dari image dan boot instance"
-
-msgid "Creates a bare-metal node."
-msgstr "Buat node bare-metal."
-
-msgid ""
-"Creating and managing ports requires administrator privileges. Contact an "
-"administrator before adding or changing ports."
-msgstr ""
-"Membuat dan mengelola port membutuhkan hak administrator. Hubungi "
-"administrator sebelum menambahkan atau mengubah port."
-
-msgid "Customization Script Source"
-msgstr "Customization Script Source"
-
-msgid "Database"
-msgstr "Basis data"
-
-msgid "Database Instance"
-msgstr "Instance database"
-
-msgid "Database flavor: ``6``"
-msgstr "Database flavor: ``6``"
-
-msgid "Databases: ``db1`` and ``db2``"
-msgstr "Databases: ``db1`` and ``db2``"
-
-msgid "Delete a cluster, using the :command:`trove cluster-delete` command."
-msgstr "Hapus cluster, gunakan perintah :command:`trove cluster-delete`."
-
-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 ""
-"Menghapus kelompok konfigurasi, menggunakan perintah :command:`trove "
-"configuration-delete`. Anda mungkin ingin melakukan hal ini jika tidak ada "
-"instance menggunakan kelompok."
-
-msgid ""
-"Delete a floating IP from the project which automatically deletes that IP's "
-"associations."
-msgstr ""
-"Menghapus IP mengambang dari proyek yang secara otomatis menghapus dimana "
-"asosiasi IP."
-
-msgid "Delete a load balancer"
-msgstr "Delete (hapus) load balancer"
-
-msgid "Delete a network"
-msgstr "Hapus jaringan"
-
-msgid "Delete a security group rule"
-msgstr "Menghapus aturan kelompok keamanan"
-
-msgid "Delete a security service"
-msgstr "Hapus layanan keamanan"
-
-msgid "Delete a share"
-msgstr "Delete (hapus) share"
-
-msgid "Delete a share network"
-msgstr "Hapus jaringan bersama"
-
-msgid "Delete a share."
-msgstr "Hapus share."
-
-msgid "Delete a snapshot."
-msgstr "Hapus snapshot."
-
-msgid "Delete a stack"
-msgstr "Delete stack"
-
-msgid "Delete a volume"
-msgstr "Delete volume"
-
-msgid "Delete an image"
-msgstr "Menghapus image"
-
-msgid "Delete an instance"
-msgstr "Hapus instance"
-
-msgid "Delete network: complete code listing example"
-msgstr "Hapus jaringan: kode lengkap daftar contoh"
-
-msgid "Delete server (API v2)"
-msgstr "Hapus Server (API v2)"
-
-msgid "Delete server code example"
-msgstr "Hapus kode server contoh"
-
-msgid "Delete share"
-msgstr "Hapus share"
-
-msgid "Delete snapshot"
-msgstr "Hapus snapshot"
-
-msgid "Delete specified image"
-msgstr "Menghapus image tertentu"
-
-msgid "Delete the instance using the following command."
-msgstr "Hapus instance menggunakan perintah berikut."
-
-msgid "Delete the network:"
-msgstr "Hapus jaringan:"
-
-msgid ""
-"Deletion of images is permanent and **cannot** be reversed. Only users with "
-"the appropriate permissions can delete images."
-msgstr ""
-"Penghapusan image terjadi permanen dan tidak dapat dibalik (**cannot** be "
-"reversed). Hanya pengguna dengan hak akses yang sesuai dapat menghapus image."
-
-msgid "Deny access"
-msgstr "Tolak akses"
-
-msgid "Deny access."
-msgstr "Tolak akses"
-
-msgid ""
-"Depending on the parameters that you provide, the command returns a list of "
-"server properties."
-msgstr ""
-"Tergantung pada parameter yang Anda berikan, perintah mengembalikan daftar "
-"server properti."
-
-msgid ""
-"Depending on the source that you select, browse to the file location, "
-"directly include the environment"
-msgstr ""
-"Tergantung pada sumber yang Anda pilih, browse ke lokasi file, langsung "
-"masukan lingkungan"
-
-msgid ""
-"Depending on the source that you select, enter the URL, browse to the file "
-"location, or directly include the template."
-msgstr ""
-"Tergantung pada sumber yang Anda pilih, masukkan URL, browse ke lokasi file, "
-"atau langsung masukan template."
-
-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 ""
-"Tergantung pada peran Anda, Anda mungkin memiliki izin untuk mengunggah dan "
-"mengelola image mesin virtual. Operator mungkin membatasi upload dan "
-"manajemen image bagi cloud administrator atau operator saja. Jika Anda "
-"memiliki hak istimewa yang sesuai, Anda dapat menggunakan dashboard untuk "
-"meng-upload dan mengelola foto dalam proyek admin."
-
-msgid "Describe a specific image"
-msgstr "Jelaskan image tertentu"
-
-# #-#-#-#-# cli_swift_large_object_creation.pot (End User Guide 1.0.0)
-# #-#-#-#-#
-# #-#-#-#-# cli_swift_serialized_response_formats.pot (End User Guide 1.0.0)
-# #-#-#-#-#
-msgid "Description"
-msgstr "Deskripsi"
-
-msgid "Detach a volume from an instance"
-msgstr "Lepaskan volume dari sebuah instance"
-
-msgid "Details"
-msgstr "Rincian"
-
-msgid "Determine whether the ``vm1`` server exists:"
-msgstr "Menentukan apakah `` vm1`` Server ada:"
-
-msgid "Direct REST calls via keystoneauth"
-msgstr "Panggilan REST langsung melalui keystoneauth"
-
-msgid ""
-"Disassociate a configuration group from a database instance, using the :"
-"command:`trove configuration-detach` command."
-msgstr ""
-"Pisahkan kelompok konfigurasi dari instance database, gunakan perintah :"
-"command:`trove configuration-detach`."
-
-msgid "Disassociate a floating IP address from an instance in the project."
-msgstr "Memisahkan alamat IP mengambang dari sebuah instance dalam proyek."
-
-msgid "Disassociate floating IP addresses"
-msgstr "Memisahkan alamat IP mengambang"
-
-msgid "Discoverability"
-msgstr "Discoverability"
-
-msgid "Disk (GB)"
-msgstr "Disk (GB)"
-
-msgid ""
-"Display information about a cluster by using the :command:`trove cluster-"
-"show` command. Pass in the ID of the cluster."
-msgstr ""
-"Menampilkan informasi tentang cluster dengan menggunakan perintah :command:"
-"`trove cluster-show`. Lewatkan dalam ID cluster."
-
-msgid "Display information for the account, container, or object"
-msgstr "Menampilkan informasi untuk akun, wadah (container), atau objek"
-
-msgid "Display the ``sync_binlog`` setting again:"
-msgstr "Tampilkan kembali pengaturan ``sync_binlog``:"
-
-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 ""
-"Jangan mengandalkan kehadiran metadata EC2 di drive konfigurasi, karena "
-"konten ini mungkin dihapus di masa mendatang. Misalnya, tidak bergantung "
-"pada file dalam direktori ``ec2``."
-
-msgid "Download binary image data"
-msgstr "Download binary image data (unduh data citra biner)"
-
-msgid "Download the snapshot as an image"
-msgstr "Ambil snapshot sebagai image"
-
-msgid ""
-"Download the snapshot by using the image ID that was returned in the "
-"previous step:"
-msgstr ""
-"Download snapshot dengan menggunakan ID image yang telah dikembalikan ke "
-"dalam langkah sebelumnya:"
-
-msgid "Dynamic large object"
-msgstr "Objek besar Dinamis"
-
-msgid "Dynamic large objects"
-msgstr "Dynamic large objects (objek besar yang dinamis)"
-
-msgid "EC2 metadata format"
-msgstr "Format metadata EC2"
-
-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 ""
-"Setiap proyek OpenStack memiliki perpustakaan Python sendiri. Perpustakaan "
-"ini dibundel dengan klien baris perintah. Misalnya, Python bindings for the "
-"Compute API dibundel dengan paket python-novaclient."
-
-msgid ""
-"Each OpenStack project produces a client library that wraps its own REST "
-"API. Unless there is no other choice for some reason, the per-project "
-"libraries should be avoided."
-msgstr ""
-"Setiap proyek OpenStack menghasilkan perpustakaan klien yang membungkus REST "
-"API sendiri. Kecuali tidak ada pilihan lain untuk beberapa alasan, "
-"perpustakaan per-proyek harus dihindari."
-
-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 ""
-"Setiap cluster meliputi setidaknya satu router kueri dan satu server config. "
-"Router kueri dan server config menggunakan kuota Anda. Ketika Anda menghapus "
-"sebuah kluster, sistem akan menghapus router kueri dan server config terkait."
-
-msgid "Each cluster includes:"
-msgstr "Setiap kluster meliputi:"
-
-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 ""
-"Setiap instance memiliki, alamat IP pribadi yang tetap dan juga dapat "
-"memiliki alamat IP publik, atau alamat IP mengambang. Alamat IP pribadi yang "
-"digunakan untuk komunikasi antar instance, dan alamat publik yang digunakan "
-"untuk komunikasi dengan jaringan luar cloud, termasuk Internet."
-
-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 ""
-"Setiap port yang mendengarkan untuk lalu lintas pada penyeimbang beban "
-"tertentu dikonfigurasi secara terpisah dan diikat dengan penyeimbang beban. "
-"Beberapa pendengar dapat dikaitkan dengan penyeimbang beban yang sama."
-
-msgid "Edit a volume"
-msgstr "Edit volume"
-
-msgid "Edit security service"
-msgstr "Edit layanan keamanan"
-
-msgid "Edit share"
-msgstr "Edit share"
-
-msgid "Edit share metadata"
-msgstr "Edit share metadata"
-
-msgid "Edit share network"
-msgstr "Edit jaringan bersama"
-
-msgid "Enable CSS for file listing"
-msgstr "Aktifkan CSS untuk daftar file"
-
-msgid "Enable and access the configuration drive"
-msgstr "Mengaktifkan dan mengakses drive konfigurasi"
-
-msgid "Enable file listing"
-msgstr "Aktifkan daftar file"
-
-msgid "Enable object versioning on your desired container:"
-msgstr "Enable object versioning on your desired container:"
-
-msgid "End-to-end integrity"
-msgstr "Integritas end-to-end"
-
-msgid ""
-"Ensure that you use at least version 0.3.1 of CirrOS for configuration drive "
-"support."
-msgstr ""
-"Pastikan bahwa Anda menggunakan setidaknya versi 0.3.1 dari CirrOS untuk "
-"dukungan konfigurasi drive."
-
-msgid "Enter a brief description of the image."
-msgstr "Masukkan deskripsi singkat tentang image."
-
-msgid "Enter a name for the image."
-msgstr "Masukkan nama untuk image."
-
-msgid "Enter a name for the object."
-msgstr "Masukkan nama untuk objek."
-
-msgid "Enter a name for the pseudo-folder."
-msgstr "Masukkan nama untuk pseudo-folder."
-
-msgid "Enter a name to identify the stack."
-msgstr "Masukkan nama untuk mengidentifikasi stack."
-
-msgid "Enter new values for any parameters that you want to update."
-msgstr ""
-"Masukkan nilai baru untuk setiap parameter yang ingin Anda memperbarui."
-
-msgid "Enter the following values:"
-msgstr "Masukkan nilai berikut:"
-
-msgid ""
-"Enter the name of the device from which the volume is accessible by the "
-"instance."
-msgstr "Masukkan nama perangkat yang volume dapat diakses oleh instance."
-
-msgid "Environment variables required to run examples"
-msgstr "Variabel lingkungan yang diperlukan untuk menjalankan contoh"
-
-msgid "Environment variables via an openrc.sh file"
-msgstr "Variabel lingkungan melalui file openrc.sh"
-
-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 ""
-"Halaman error disajikan dengan kode status pra-pended dengan nama halaman "
-"error yang Anda ditetapkan. Misalnya, jika Anda menetapkan ``X-Container-"
-"Meta-Web-Error`` untuk ``error.html``, kesalahan 401 akan menampilkan "
-"halaman ``401error.html``. Demikian pula, kesalahan 404 akan menampilkan "
-"``404error.html``. Anda harus memiliki kedua halaman dibuat dalam kontainer "
-"Anda ketika Anda menetapkan metadata ``X-Container-Meta-Web-Error``, atau "
-"situs Anda akan menampilkan halaman error generik."
-
-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 ""
-"Errors (kesalahan). Daftar nama objek dan terkait status kesalahan untuk "
-"objek yang gagal untuk menghapus. Format tergantung pada nilai yang Anda "
-"tetapkan dalam header ``Accept``."
-
-msgid "Events"
-msgstr "Kejadian"
-
-msgid "Example:"
-msgstr "Contoh:"
-
-msgid "Example 1. JSON example with format query parameter"
-msgstr "Contoh 1. Contoh JSON dengan parameter keri format"
-
-msgid "Example 2. XML example with Accept header"
-msgstr "Contoh 2. Contoh XML dengan header Accept"
-
-msgid "Extend share"
-msgstr "Memperluas share"
-
-msgid "Extend share."
-msgstr "Memperluas share."
-
-msgid "Extra transaction information"
-msgstr "Informasi transaksi tambahan"
-
-msgid "Fedora (RHEL)"
-msgstr "Fedora (RHEL)"
-
-msgid ""
-"Find out what instances are using a configuration group, using the :command:"
-"`trove configuration-instances` command."
-msgstr ""
-"Cari tahu apakah instance menggunakan kelompok konfigurasi, menggunakan "
-"perintah :command:`trove configuration-instances`."
-
-msgid ""
-"First, determine which configuration options you can set. Different data "
-"store versions have different configuration options."
-msgstr ""
-"Pertama, tentukan opsi konfigurasi dimana Anda dapat mengatur. Versi "
-"penyimpanan data yang berbeda memiliki opsi konfigurasi yang berbeda."
-
-msgid ""
-"First, get the ID of the ``guest1`` database instance by using the :command:"
-"`trove list` command:"
-msgstr ""
-"Pertama, mendapatkan ID dari ``guest1`` instance database dengan menggunakan "
-"perintah :command:`trove list`:"
-
-msgid ""
-"First, use the :command:`trove list` command to list all instances and their "
-"IDs:"
-msgstr ""
-"Pertama, gunakan perintah :command:`trove list` untuk daftar semua instance "
-"dan ID nya:"
-
-msgid "Flavor"
-msgstr "Flavor"
-
-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 ""
-"Flavor ID: Anda harus menggunakan ID yang belum digunakan. Dalam contoh ini, "
-"adalah 1 sampai 5 yang digunakan, jadi gunakan ID ``6``."
-
-msgid "Flavor ID: ``10``"
-msgstr "Flavor ID: ``10``"
-
-msgid "Flavor name: ``mysql_minimum``"
-msgstr "Flavor name: ``mysql_minimum``"
-
-msgid "Follow the steps below to launch an instance from an image."
-msgstr ""
-"Ikuti langkah di bawah ini untuk memulai sebuah instance dari sebuah image."
-
-msgid "Follow this procedure to update an existing image."
-msgstr "Ikuti prosedur ini untuk memperbarui image yang ada."
-
-msgid "Follow this procedure to upload an image to a project:"
-msgstr "Ikuti prosedur ini untuk meng-upload image ke proyek:"
-
-msgid "For ``get_credentials`` see :ref:`Get credentials `."
-msgstr ""
-"Untuk ``get_credentials`` lihat :ref:`Get credentials `."
-
-msgid "For ``get_credentials``, see :ref:`Get credentials `."
-msgstr ""
-"Untuk ``get_credentials``, lihat :ref:`Get credentials `."
-
-msgid ""
-"For ``get_nova_credentials``, see :ref:`Get Nova credentials `."
-msgstr ""
-"Untuk ``get_nova_credentials``, lihat :ref:`Get Nova credentials `."
-
-msgid "For ``print_values``, see :ref:`Print values `."
-msgstr "Untuk ``print_values``, lihat :ref:`Print values `."
-
-msgid ""
-"For details about how to install the clients, see :doc:`../common/cli-"
-"install-openstack-command-line-clients`."
-msgstr ""
-"Untuk rincian tentang cara menginstal klien, lihat :doc:`../common/cli-"
-"install-openstack-command-line-clients`."
-
-msgid ""
-"For details on creating images, see `Creating images manually `_ in the *OpenStack "
-"Virtual Machine Image Guide*."
-msgstr ""
-"Untuk rincian tentang penciptaan image, lihat `Creating images manually "
-"`_ dalam "
-"*OpenStack Virtual Machine Image Guide*."
-
-msgid ""
-"For each NIC on the node, you must create an interface, specifying the "
-"interface's MAC address."
-msgstr ""
-"Untuk setiap NIC pada node, Anda harus membuat sebuah antarmuka, menentukan "
-"alamat MAC antarmuka ini."
-
-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 ""
-"Untuk setiap alamat IP mengambang yang dialokasikan untuk proyek ini, "
-"perintah output alamat IP mengambang, ID untuk instance yang alamat IP "
-"mengambang ditugaskan, alamat IP tetap yang terkait, dan kolam yang alamat "
-"IP mengambang dialokasikan."
-
-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 ""
-"Misalnya, jika objek pertama dalam arsip tar adalah ``/home/file1.txt`` dan "
-"Anda menentukan path ``/v1/12345678912345/mybackup/castor/``, operasi "
-"membuat objek ``castor/home/file1.txt`` di container ``mybackup`` di akun "
-"``12345678912345``."
-
-msgid ""
-"For example, if your MySQL data store name is set to ``mysql``, your entry "
-"would look like this:"
-msgstr ""
-"Sebagai contoh, jika nama penyimpang data MySQL Anda diatur ke ``mysql``, "
-"entri Anda akan terlihat seperti ini:"
-
-msgid ""
-"For example, this request uses the ``format`` query parameter to ask for a "
-"JSON response:"
-msgstr ""
-"Misalnya, request (permintaan) ini menggunakan parameter kueri ``format`` "
-"untuk meminta respon JSON:"
-
-msgid ""
-"For example, you can include extra transaction information when you upload "
-"large objects such as images."
-msgstr ""
-"Misalnya, Anda dapat memasukkan informasi transaksi tambahan ketika Anda "
-"meng-upload object besar seperti image."
-
-msgid "For example:"
-msgstr "Sebagai contoh:"
-
-msgid ""
-"For further information and comparisons (including security considerations), "
-"see the `Security Guide `__."
-msgstr ""
-"Untuk informasi lebih lanjut dan perbandingan (termasuk pertimbangan "
-"keamanan), lihat `Security Guide `__."
-
-msgid ""
-"For information and examples on more advanced use of neutron's ``subnet`` "
-"subcommand, see the `OpenStack Administrator Guide `__."
-msgstr ""
-"Untuk informasi dan contoh penggunaan subcommand ``subnet`` neutron yang "
-"lebih maju, lihat `OpenStack Administrator Guide `__."
-
-msgid ""
-"For instance, the Rackspace public cloud is an OpenStack deployment that has "
-"an optional custom authentication back end. While normal keystone password "
-"authentication works perfectly well, you may want to use the custom "
-"Rackspace keystoneauth API Key plugin found in `rackspace-keystoneauth-"
-"plugin `_."
-msgstr ""
-"Misalnya, cloud publik Rackspace adalah pengerah (deployment) OpenStack "
-"yang memiliki back end otentikasi kustom secara opsional. Sementara "
-"otentikasi password keystone normal berjalan dengan baik, Anda mungkin "
-"ingin menggunakan plugin Rackspace keystoneauth API Key kustom yang "
-"ditemukan di `rackspace-keystoneauth-plugin `_."
-
-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 ""
-"Untuk alasan warisan (legacy), Anda dapat mengkonfigurasi drive konfigurasi "
-"untuk menggunakan format VFAT bukan ISO 9660. Hal ini tidak mungkin bahwa "
-"Anda akan memerlukan Format VFAT karena ISO 9660 secara luas didukung di "
-"sistem operasi. Namun, untuk menggunakan format VFAT, tambahkan baris "
-"berikut ke file ``/etc/nova/nova.conf``:"
-
-msgid "For variety in this example, create one more instance and module:"
-msgstr "Untuk variasi dalam contoh ini, buat satu lagi instance dan modul:"
-
-msgid "Formats response as JSON."
-msgstr "Format respon sebagai JSON."
-
-msgid "Formats response as XML."
-msgstr "Format respon sebagai XML."
-
-msgid ""
-"Formats response as plain text. If you omit the ``Accept`` header, ``text/"
-"plain`` is the default."
-msgstr ""
-"Format respon sebagai teks biasa. Jika Anda menghilangkan header ``Accept``, "
-"dan ``text/plain`` adalah default."
-
-msgid ""
-"From the :guilabel:`Admin` tab, you can access the following category to "
-"complete these tasks:"
-msgstr ""
-"Dari tab :guilabel:`Admin` tab, Anda dapat mengakses kategori berikut untuk "
-"menyelesaikan tugas ini:"
-
-msgid ""
-"From the :guilabel:`Project` tab, you can access the following categories:"
-msgstr "Dari tab :guilabel:`Project`, Anda dapat mengakses kategori berikut:"
-
-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 ""
-"Dari tab :guilabel:`Project`, Anda dapat melihat dan mengelola sumber daya "
-"dalam proyek yang dipilih, termasuk instance dan image. Anda dapat memilih "
-"proyek dari menu drop-down di bagian kiri atas. Jika cloud mendukung model "
-"multi-domain, Anda juga dapat memilih domain dari menu ini."
-
-msgid ""
-"From the CURRENT PROJECT on the :guilabel:`Project` tab, select the "
-"appropriate project."
-msgstr ""
-"Dari CURRENT PROJECT pada tab :guilabel:`Project`, pilih proyek yang tepat."
-
-msgid "Gather parameters to launch an instance"
-msgstr "Mengumpulkan parameter untuk meluncurkan sebuah instance"
-
-msgid ""
-"Get Nova Credentials. See :ref:'Get Nova credentials '."
-msgstr ""
-"Dapatkan Nova Kredensial. Lihat :ref:'Get Nova credentials '."
-
-msgid "Get Nova credentials"
-msgstr "Dapatkan Nova kredensial"
-
-msgid ""
-"Get Nova credentials. See :ref:`Get OpenStack credentials (API v2) `."
-msgstr ""
-"Dapatkan Nova kredensial. Lihat :ref:`Get OpenStack credentials (API v2) "
-"`."
-
-msgid ""
-"Get OpenStack Credentials. See :ref:`Get OpenStack credentials (API v2) `."
-msgstr ""
-"Dapatkan OpenStack Kredensial. Lihat :ref:`Get OpenStack credentials (API "
-"v2) `."
-
-msgid "Get OpenStack credentials (API v2)"
-msgstr "Dapatkan kredensial OpenStack (API v2)"
-
-msgid ""
-"Get OpenStack credentials. :ref:`Get OpenStack credentials (API v2) `."
-msgstr ""
-"Dapatkan kredensial OpenStack. :ref:`Get OpenStack credentials (API v2) `."
-
-msgid ""
-"Get OpenStack credentials. See :ref:`Get OpenStack credentials (API v2) `."
-msgstr ""
-"Dapatkan kredensial OpenStack. Lihat :ref:`Get OpenStack credentials (API "
-"v2) `."
-
-msgid "Get credentials"
-msgstr "Dapatkan kredensial"
-
-msgid "Get credentials. See :ref:'Get credentials '."
-msgstr "Dapatkan kredensial. Lihat :ref:'Get credentials '."
-
-msgid ""
-"Get credentials. See :ref:`Get Nova credentials `."
-msgstr ""
-"Dapatkan kredensial. Lihat :ref:`Get Nova credentials `."
-
-msgid "Get credentials. See :ref:`Get credentials `."
-msgstr "Dapatkan kredensial. Lihat :ref:`Get credentials `."
-
-msgid "Get image by ID"
-msgstr "Dapatkan image dengan ID"
-
-msgid "Get image by name"
-msgstr "Dapatkan image dengan nama"
-
-msgid "Get information about stacks"
-msgstr "Dapatkan informasi tentang tumpukan (stack)"
-
-msgid "Get the ID of the configuration group:"
-msgstr "Dapatkan ID dari kelompok konfigurasi:"
-
-msgid "Get the ID of the database instance:"
-msgstr "Dapatkan ID dari database instance:"
-
-msgid "Get the ID of the original instance you want to replicate:"
-msgstr "Mendapatkan ID instance asli dimana Anda ingin meniru:"
-
-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 ""
-"Dapatkan flavor dan image untuk digunakan untuk membuat server. Kode ini "
-"menggunakan image ``cirros``, flavor ``m1.tiny``, dan jaringan ``private``:"
-
-msgid "Get the image ID:"
-msgstr "Dapatkan ID image:"
-
-msgid ""
-"Get the server instance using ``server_id`` and print the details by calling "
-"``print_server`` method:"
-msgstr ""
-"Dapatkan instance server menggunakan ``server_id`` dan mencetak rincian "
-"dengan calling method ``print_server``:"
-
-msgid "Get the updated instance of the server:"
-msgstr "Dapatkan instance terbaru dari server:"
-
-msgid ""
-"Go to the security service that you want to edit and choose :guilabel:`Edit "
-"Security Service` from Actions."
-msgstr ""
-"Jelajahi layanan keamanan yang ingin Anda edit dan pilih:guilabel:`Edit "
-"Security Service` dari Actions."
-
-msgid ""
-"Go to the share network that you want to edit and choose :guilabel:`Edit "
-"Share Network` from Actions."
-msgstr ""
-"Pergi ke jaringan bersama yang ingin Anda edit dan pilih:guilabel:`Edit "
-"Share Network` dari Actions."
-
-msgid ""
-"Go to the share that you want to allow access and choose :guilabel:`Manage "
-"Rules` from Actions."
-msgstr ""
-"Jelajahi share yang ingin Anda izinkan akses dan memilih :guilabel:`Manage "
-"Rules` dari Actions."
-
-msgid ""
-"Go to the share that you want to deny access and choose :guilabel:`Manage "
-"Rules` from Actions."
-msgstr ""
-"Jelajahi share yang ingin Anda tolak akses dan memilih:guilabel:`Manage "
-"Rules` dari Actions."
-
-msgid ""
-"Go to the share that you want to edit and choose :guilabel:`Edit Share "
-"Metadata` from Actions."
-msgstr ""
-"Kunjungi ke share yang ingin Anda edit dan pilih :guilabel:`Edit Share "
-"Metadata` from Actions."
-
-msgid ""
-"Go to the share that you want to edit and choose :guilabel:`Edit Share` from "
-"Actions."
-msgstr ""
-"Jelajahi share yang ingin Anda edit dan pilih :guilabel:`Edit Share` dari "
-"Actions."
-
-msgid ""
-"Go to the share that you want to edit and choose :guilabel:`Extend Share` "
-"from Actions."
-msgstr ""
-"Jelajahi share yang ingin Anda edit dan pilih :guilabel:`Extend Share` dari "
-"Actions."
-
-msgid "HOT Guide"
-msgstr "HOT Guide"
-
-msgid "HTTP/1.1"
-msgstr "HTTP/1.1"
-
-msgid "Health monitor"
-msgstr "Health monitor (monitor kesehatan)"
-
-msgid "Here is a list of common commands for reference."
-msgstr "Berikut adalah daftar perintah umum untuk referensi."
-
-msgid "How can I use an OpenStack cloud?"
-msgstr "Bagaimana saya bisa menggunakan cloud OpenStack?"
-
-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 ""
-"Namun, selain alamat IP tetap, alamat IP mengambang juga dapat dilampirkan "
-"ke sebuah Instance. Tidak seperti alamat IP tetap, alamat IP mengambang "
-"dapat memiliki asosiasi nya dapat diubah setiap saat, terlepas dari keadaan "
-"Instance yang terlibat. Prosedur ini merinci reservasi alamat IP mengambang "
-"dari kolam alamat yang ada dan alamat yang berasosiasi dengan instance "
-"spesifik."
-
-msgid ""
-"ID of the instance (``INSTANCE_ID``): ``792a6a56-278f-4a01-9997-"
-"d997fa126370``"
-msgstr ""
-"ID instance (``INSTANCE_ID``): ``792a6a56-278f-4a01-9997-d997fa126370``"
-
-msgid ""
-"ID of the regular backup artifact (``BACKUP_ID``): "
-"``6dc3a9b7-1f3e-4954-8582-3f2e4942cddd``"
-msgstr ""
-"ID regular backup artifact (``BACKUP_ID``): "
-"``6dc3a9b7-1f3e-4954-8582-3f2e4942cddd``"
-
-msgid "Identity (keystone)"
-msgstr "Identity (keystone)"
-
-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 ""
-"Jika peringatan sertifikat muncul ketika Anda mencoba untuk mengakses URL "
-"untuk pertama kalinya, sebuah sertifikat yang ditandatangani sendiri sedang "
-"digunakan, yang tidak dapat dipercaya secara default. Verifikasi sertifikat "
-"atau menambahkan pengecualian dalam browser untuk memotong peringatan."
-
-msgid ""
-"If a user passes the ``--config-drive true`` flag to the :command:`nova "
-"boot` command, an administrator cannot disable the configuration drive."
-msgstr ""
-"Jika pengguna melewatkan bendera (flag) ``--config-drive true`` ke perintah :"
-"command:`nova boot`, administrator tidak dapat menonaktifkan drive "
-"konfigurasi."
-
-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 ""
-"Jika image tidak memiliki paket cloud-init terinstal, Anda harus "
-"menyesuaikan image untuk menjalankan script yang me-mount drive konfigurasi "
-"pada boot, membaca data dari drive, dan mengambil tindakan yang tepat "
-"seperti menambahkan kunci publik (public key) ke akun . Anda dapat membaca "
-"lebih detail tentang bagaimana data diorganisasi pada drive konfigurasi."
-
-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 ""
-"Jika image menggunakan password root statis atau satu set kunci statis "
-"(tidak disarankan), Anda tidak harus memberikan sepasang kunci ketika Anda "
-"memulai instance."
-
-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 ""
-"Jika semuanya cocok, API membuat objek nyata (manifest) dan menetapkan "
-"metadata ``X-Static-besar-Object`` untuk ``true`` untuk menunjukkan bahwa "
-"manifes adalah objek nyata statis."
-
-msgid ""
-"If needed, you can assign a **floating (public) IP address** to a running "
-"instance."
-msgstr ""
-"Jika diperlukan, Anda dapat menetapkan **floating (public) IP address** "
-"(alamat IP mengambang (publik)) untuk instance berjalan."
-
-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 ""
-"Jika image menggunakan password root statis atau satu set kunci statis "
-"(tidak disarankan), Anda tidak perlu memberikan sepasang kunci (key pair) "
-"untuk meluncurkan instance."
-
-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 ""
-"Jika instance asli turun, Anda dapat melepaskan replika. Replika menjadi "
-"instance database standalone. Anda kemudian dapat mengambil instance mandiri "
-"(standalone) baru dan membuat replika baru dari instance itu."
-
-msgid ""
-"If the resize fails or does not work as expected, you can revert the resize. "
-"For example:"
-msgstr ""
-"Jika resize gagal atau tidak bekerja seperti yang diharapkan, Anda dapat "
-"mengembalikan ukurannya. Sebagai contoh:"
-
-msgid ""
-"If the server exists, run the ``delete`` method of the ``nova_client."
-"servers`` object:"
-msgstr ""
-"Jika server ada, jalankan metode ``delete`` dari objek ``nova_client."
-"servers``:"
-
-msgid "If the status for the instance is ACTIVE, the instance is online."
-msgstr "Jika status instance adalah ACTIVE, instance online."
-
-msgid ""
-"If this list is empty, the cloud administrator must configure a pool of "
-"floating IP addresses. This command is only available in ``nova-network``. "
-"If you use the OpenStack Networking service, run the following command to "
-"list external networks:"
-msgstr ""
-"Jika daftar ini kosong, administrator awan harus mengkonfigurasi kumpulan "
-"alamat IP terapung. Perintah ini hanya tersedia di ``nova-network``. Jika "
-"Anda menggunakan layanan OpenStack Networking, jalankan perintah berikut "
-"untuk menampilkan jaringan eksternal:"
-
-msgid ""
-"If true, set the variable name ``server_exists`` to ``True`` and break from "
-"the for loop:"
-msgstr ""
-"Jika benar, tetapkan nama variabel ``server_exists`` untuk ``True`` dan "
-"istirahat (break) dari for loop:"
-
-msgid "If validation fails, the response returns an error message."
-msgstr "Jika validasi gagal, respon akan kembalikan pesan kesalahan."
-
-msgid ""
-"If you are an admin user, this command will list groups for all tenants."
-msgstr ""
-"Jika Anda adalah seorang pengguna admin, perintah ini akan menampilkan "
-"kelompok untuk semua penyewa (tenant)"
-
-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 ""
-"Jika Anda login sebagai administrator, tab :guilabel:`Project` (:ref:"
-"`dashboard-project-tab`) dan tab :guilabel:`Admin` (:ref:`dashboard-admin-"
-"tab`) dan tab :guilabel:`Identity` (:ref:`dashboard-identity-tab`) akan "
-"ditampilkan"
-
-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 ""
-"Jika Anda login sebagai pengguna akhir, tab :guilabel:`Project` (:ref:"
-"`dashboard-project-tab`) dan tab :guilabel:`Identity` (:ref:`dashboard-"
-"identity-tab`) akan ditampilkan."
-
-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 ""
-"Jika Anda menggunakan Dashboard dari komputer Windows, gunakan PuTTYgen "
-"untuk memuat (load) file `` *.pem`` dan mengkonversi dan menyimpannya "
-"sebagai `` *.ppk``. Untuk informasi lebih lanjut lihat `WinSCP web page for "
-"PuTTYgen `__."
-
-msgid ""
-"If you authenticate against an endpoint that uses a custom authentication "
-"back end, you must provide the name of the plugin in the ``auth_type`` "
-"parameter."
-msgstr ""
-"Jika Anda mengotentikasi terhadap titik akhir (endpoint) yang menggunakan "
-"otentikasi kustom back end, Anda harus memberikan nama plugin di parameter "
-"``auth_type``."
-
-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 ``neutron-dnsmasq.log`` file."
-msgstr ""
-"Jika anda boot sebuah instance dengan INSTANCE_NAME lebih besar dari 63 "
-"karakter, Compute memotong secara otomatis ketika mengubahnya menjadi nama "
-"host untuk memastikan pekerjaan yang benar dnsmasq. Peringatan yang sesuai "
-"ditulis ke dalam file ``neutron-dnsmasq.log``."
-
-msgid "If you choose VFAT, the configuration drive is 64 MB."
-msgstr "Jika Anda memilih VFAT, drive konfigurasi adalah 64 MB."
-
-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 ""
-"Jika Anda memilih untuk tidak mengatur value :guilabel:`IP Address`, maka "
-"secara default OpenStack Networking menggunakan alamat IP host pertama dalam "
-"subnet."
-
-msgid ""
-"If you choose this option, a new field for :guilabel:`Image Name` displays. "
-"You can select the image from the list."
-msgstr ""
-"Jika Anda memilih opsi ini, kolom (field) baru untuk display :guilabel:"
-"`Image Name`. Anda dapat memilih image dari daftar."
-
-msgid ""
-"If you choose this option, a new field for :guilabel:`Instance Snapshot` "
-"displays. You can select the snapshot from the list."
-msgstr ""
-"Jika Anda memilih opsi ini, field (kolom) baru untuk display :guilabel:"
-"`Instance Snapshot`. Anda dapat memilih snapshot dari daftar."
-
-msgid ""
-"If you choose this option, a new field for :guilabel:`Volume` displays. You "
-"can select the volume from the list."
-msgstr ""
-"Jika Anda memilih opsi ini, field (kolom) baru untuk display :guilabel:"
-"`Volume`. Anda dapat memilih volume dari daftar."
-
-msgid ""
-"If you desire a specific micro-version of the Nova API, you can pass that as "
-"the ``version`` parameter:"
-msgstr ""
-"Jika Anda menginginkan micro-version spesifik dari Nova API, Anda dapat "
-"melewati itu sebagai parameter ``version``:"
-
-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 ""
-"Jika Anda tidak memberikan sepasang kunci, kelompok keamanan, atau aturan, "
-"pengguna dapat mengakses instance hanya dari dalam cloud melalui VNC. Bahkan "
-"ping instance tidak mungkin tanpa aturan ICMP dikonfigurasi."
-
-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 ""
-"Jika Anda tidak memberikan kunci pasangan, kelompok keamanan, atau aturan, "
-"Anda dapat mengakses instance hanya dari dalam cloud melalui VNC. Bahkan "
-"ping instance tidak mungkin."
-
-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 ""
-"Jika Anda memiliki flavor khusus yang memenuhi kebutuhan database yang ingin "
-"Anda buat, lanjutkan ke :ref:`Step 2 ` dan "
-"menggunakan flavor itu."
-
-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 ""
-"Jika Anda memiliki sejumlah besar kontainer atau objek, Anda dapat "
-"menggunakan parameter ``marker``, ``limit``, dan ``end_marker`` untuk "
-"mengontrol berapa banyak barang yang dikembalikan dalam daftar dan dimana "
-"daftar dimulai atau berakhir."
-
-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 ""
-"Jika Anda telah menghasilkan sepasang kunci dan kunci publik terletak di "
-"``~/.ssh/id_rsa.pub``, jalankan perintah berikut untuk meng-upload kunci "
-"publik."
-
-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 ""
-"Jika Anda telah dihasilkan sepasang kunci (keypair) dengan kunci publik "
-"(public key) yang terletak di ``~/.ssh/id_rsa.pub``, lewatkan isi file ke "
-"metode `novaclient.v1\\_1.keypairs.KeypairManager.create `__ untuk mengimpor "
-"kunci publik (public key) ke Compute:"
-
-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 ""
-"Jika Anda telah menghasilkan sepasang kunci (key pair) dengan alat "
-"eksternal, Anda dapat mengimpor ke OpenStack. Pasangan kunci dapat digunakan "
-"untuk beberapa instance milik proyek. Untuk informasi lebih lanjut, lihat "
-"bagian :ref: `dashboard_import_keypair`."
-
-msgid ""
-"If you have not created any security groups, you can assign only the default "
-"security group to the instance."
-msgstr ""
-"Jika Anda belum membuat kelompok keamanan, Anda hanya dapat menetapkan "
-"kelompok standar keamanan untuk instance."
-
-msgid ""
-"If you have not created any security groups, you can assign the instance to "
-"only the default security group."
-msgstr ""
-"Jika Anda belum membuat kelompok keamanan, Anda dapat menetapkan instance "
-"untuk hanya kelompok keamanan default."
-
-msgid ""
-"If you no longer want to expire the object, you can remove the ``X-Delete-"
-"At`` header:"
-msgstr ""
-"Jika Anda tidak ingin lagi mengakhiri objek, Anda dapat menghapus header ``X-"
-"Delete-At``:"
-
-msgid ""
-"If you use Xen with a configuration drive, use the ``xenapi_disable_agent`` "
-"configuration parameter to disable the agent."
-msgstr ""
-"Jika Anda menggunakan Xen dengan konfigurasi drive, gunakan parameter "
-"konfigurasi ``xenapi_disable_agent`` untuk menonaktifkan agen."
-
-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 ""
-"Jika Anda menggunakan objek bermanifestasi sebagai sumber dari permintaan "
-"``COPY``, objek baru adalah objek normal, dan tidak segmen,. Jika ukuran "
-"total sumber objek segmen melebihi 5 GB, permintaan ``COPY`` gagal. Namun, "
-"Anda dapat membuat duplikat dari objek nyata dan objek baru ini bisa lebih "
-"besar dari 5 GB."
-
-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 ""
-"Jika Anda menggunakan operasi ``DELETE`` pada objek nyata (manifest) , objek "
-"nyata dihapus. Object segmen tidak terpengaruh. Namun, jika Anda menambahkan "
-"parameter query ``?multipart-manifest = delete`` , obyek segmen akan dihapus "
-"dan jika semua berhasil dihapus, objek nyata juga dihapus."
-
-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 ""
-"Jika Anda menggunakan driver bare-metal, Anda harus membuat antarmuka "
-"jaringan dan menambahkannya ke node bare-metal. Kemudian, Anda dapat memulai "
-"sebuah instance dari image bare-metal."
-
-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 ""
-"Jika Anda ingin membuat volume ke backend penyimpanan tertentu, Anda perlu "
-"menggunakan image yang memiliki properti *cinder_img_volume_type*. Dalam hal "
-"ini, volume baru akan dibuat sebagai tipe volume *storage_backend1 *."
-
-msgid ""
-"If you want to rescue an instance with a specific image, rather than the "
-"default one, use the ``--image`` parameter:"
-msgstr ""
-"If you want to rescue an instance with a specific image, rather than the "
-"default one, use the ``--image`` parameter:"
-
-msgid ""
-"If you wish to apply a module, you must create the module first and register "
-"it with the trove service. A user can not directly apply a module to a trove "
-"instance."
-msgstr ""
-"Jika Anda ingin menerapkan modul, Anda harus membuat modul terlebih dahulu "
-"dan mendaftarkannya dengan layanan trove. Seorang pengguna tidak bisa "
-"langsung menerapkan modul ke instance trove."
-
-msgid ""
-"If your environment does not have a suitable flavor, an administrative user "
-"must create a custom flavor by using the :command:`openstack flavor create` "
-"command."
-msgstr ""
-"Jika lingkungan Anda tidak memiliki flavor cocok, pengguna administratif "
-"harus menciptakan flavor kustom dengan menggunakan perintah :command:"
-"`openstack flavor create`."
-
-msgid ""
-"If your guest operating system does not use ``udev``, the ``/dev/disk/by-"
-"label`` directory is not present."
-msgstr ""
-"Jika sistem operasi guest Anda tidak menggunakan ``udev``, direktori ``/dev/"
-"disk/by-label`` tidak hadir."
-
-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 ""
-"Jika sistem operasi guest Anda mendukung mengakses disk dengan label, Anda "
-"dapat me-mount drive konfigurasi sebagai perangkat ``/dev/disk/by-label/"
-"configurationDriveVolumeLabel``. Pada contoh berikut, drive konfigurasi "
-"memiliki label volume ``config-2``:"
-
-msgid "Image Name"
-msgstr "Nama Image"
-
-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 ""
-"Image dimana Anda telah menyalin ke volume persisten. Instance meluncur dari "
-"volume, yang disediakan oleh API ``cinder-volume`` melalui iSCSI."
-
-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 ""
-"Image: Jika Anda memilih opsi ini, filed baru untuk menampilkan :guilabel:"
-"`Use image as a source`. Anda dapat memilih image dari daftar."
-
-msgid "Images (glance)"
-msgstr "Images (glance)"
-
-msgid "Images uploaded to the Image service."
-msgstr "Image yang diunggah ke layanan Image."
-
-msgid "Import a key pair"
-msgstr "Import key pair"
-
-msgid "Import a keypair"
-msgstr "Mengimpor sepasang kunci (keypair)"
-
-msgid "Import the following modules:"
-msgstr "Mengimpor modul berikut:"
-
-msgid "Import the snapshot to the new environment"
-msgstr "Impor snapshot dengan lingkungan baru"
-
-msgid ""
-"In CirrOS, the password for user ``cirros`` is ``cubswin:)``. For any other "
-"operating system, use SSH keys."
-msgstr ""
-"Dalam CirrOS, password untuk pengguna ``cirros`` adalah `` cubswin:) ``. "
-"Untuk sistem operasi lain, menggunakan kunci SSH."
-
-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 ""
-"Dalam OpenStack Object Storage, wadah (container) menyediakan penyimpanan "
-"untuk objek dalam cara yang mirip dengan folder Windows atau direktori file "
-"Linux, meskipun mereka tidak dapat bersarang. Obyek dalam OpenStack terdiri "
-"dari file yang akan disimpan dalam kontainer dan metadata yang menyertainya."
-
-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 OpenStack APIs."
-msgstr ""
-"Selain cara berinteraksi dengan awan ini, Anda dapat mengakses OpenStack API "
-"secara langsung atau tidak langsung melalui perintah `cURL ` __ atau buka SDK. Anda dapat mengotomatisasi akses atau membangun alat "
-"untuk mengelola sumber daya dan layanan dengan menggunakan OpenStack API."
-
-msgid "In addition, this command specifies these options for the instance:"
-msgstr "Selain itu, perintah ini menentukan opsi ini untuk instance:"
-
-msgid "In addition, you must:"
-msgstr "Selain itu, Anda harus:"
-
-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 ""
-"Dalam versi saat ini (Liberty) dari OpenStack Compute, migrasi hidup dengan "
-"``config_drive`` pada disk lokal dilarang karena bug di libvirt menyalin "
-"disk read-only. Namun, jika kita menggunakan VFAT sebagai format "
-"``config_drive``, fungsi migrasi hidup bekerja dengan baik."
-
-msgid ""
-"In order for object expiration to work properly, the ``swift-object-"
-"expirer`` daemon will need access to all backend servers in the cluster. The "
-"daemon does not need access to the proxy-server or public network."
-msgstr ""
-"Agar objek kedaluwarsa untuk bekerja dengan baik, daemon ``swift-object-"
-"expirer`` akan memerlukan akses ke semua server backend di cluster. Daemon "
-"tidak perlu akses ke proxy-server atau jaringan publik."
-
-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 ""
-"Dalam beberapa kasus, permintaan ``/info`` akan kembali kesalahan. Ini bisa "
-"jadi karena penyedia layanan Anda telah menonaktifkan fungsi permintaan ``/"
-"info`` , atau karena Anda menggunakan versi lama yang tidak mendukung itu."
-
-msgid "In the :guilabel:`Actions` column, click :guilabel:`Create Snapshot`."
-msgstr "Dalam kolom :guilabel:`Actions`, klik :guilabel:`Create Snapshot`."
-
-msgid "In the :guilabel:`Actions` column, click :guilabel:`Edit Volume`."
-msgstr "Dalam kolom :guilabel:`Actions`, klik :guilabel:`Edit Volume`."
-
-msgid ""
-"In the :guilabel:`Actions` column, click the menu button and then select :"
-"guilabel:`Edit Image` from the list."
-msgstr ""
-"Dalam kolom :guilabel:`Actions`, klik tombol menu dan kemudian pilih :"
-"guilabel:`Edit Image` dari daftar."
-
-msgid ""
-"In the :guilabel:`Add Interface` dialog box, select a :guilabel:`Subnet`."
-msgstr "Dalam dialog box :guilabel:`Add Interface` , pilih :guilabel:`Subnet`."
-
-msgid "In the :guilabel:`Add Rule` dialog box, enter the following values:"
-msgstr "Dalam dialog box :guilabel:`Add Rule` , masukkan nilai berikut:"
-
-msgid ""
-"In the :guilabel:`Backup Database` dialog box, specify the following values:"
-msgstr "Dalam dialog box :guilabel:`Backup Database` , tentukan nilai berikut:"
-
-msgid ""
-"In the :guilabel:`Confirm Delete Images` dialog box, click :guilabel:`Delete "
-"Images` to confirm the deletion."
-msgstr ""
-"Dalam dialog box :guilabel:`Confirm Delete Images` , klik :guilabel:`Delete "
-"Images` untuk mengkonfirmasi penghapusan."
-
-msgid ""
-"In the :guilabel:`Copy Object` launch dialog box, enter the following values:"
-msgstr ""
-"Dalam kotak dialog meluncurkan :guilabel:`Copy Object`, masukkan nilai "
-"berikut:"
-
-msgid ""
-"In the :guilabel:`Create Container` dialog box, enter a name for the "
-"container, and then click :guilabel:`Create`."
-msgstr ""
-"Dalam dialog box :guilabel:`Create Container` , masukkan nama untuk wadah, "
-"lalu klik :guilabel:`Create`."
-
-msgid ""
-"In the :guilabel:`Create Key Pair` dialog box, enter a name for your key "
-"pair, and click :guilabel:`Create Key Pair`."
-msgstr ""
-"Dalam dialog box :guilabel:`Create Key Pair` , masukkan nama untuk sepasang "
-"kunci (key pair) Anda, dan klik :guilabel:`Create Key Pair`."
-
-msgid ""
-"In the :guilabel:`Create Network` dialog box, specify the following values."
-msgstr "Dalam dialog box :guilabel:`Create Network` , tentukan nilai berikut."
-
-msgid ""
-"In the :guilabel:`Create Port` dialog box, specify the following values."
-msgstr "Dalam dialog box :guilabel:`Create Port` , menentukan nilai berikut."
-
-msgid ""
-"In the :guilabel:`Create Router` dialog box, specify a name for the router "
-"and :guilabel:`External Network`, and click :guilabel:`Create Router`."
-msgstr ""
-"Dalam dialog box :guilabel:`Create Router` , tentukan nama untuk router dan :"
-"guilabel:`External Network`, dan klik :guilabel:`Create Router`."
-
-msgid ""
-"In the :guilabel:`Create Snapshot` dialog box, enter a name for the "
-"snapshot, and click :guilabel:`Create Snapshot`."
-msgstr ""
-"Dalam dialog box :guilabel:`Create Snapshot` , masukkan nama untuk snapshot, "
-"dan klik :guilabel:`Create Snapshot`."
-
-msgid ""
-"In the :guilabel:`Edit Image` dialog box, you can perform various actions. "
-"For example:"
-msgstr ""
-"Dalam dialog box :guilabel:`Edit Image` , Anda dapat melakukan berbagai "
-"tindakan. Sebagai contoh:"
-
-msgid ""
-"In the :guilabel:`Edit Volume` dialog box, update the name and description "
-"of the volume."
-msgstr ""
-"Dalam dialog box :guilabel:`Edit Volume` , perbarui (update) nama dan "
-"deskripsi dari volume."
-
-msgid "In the :guilabel:`Floating IPs` list, click :guilabel:`Associate`."
-msgstr "Dalam daftar :guilabel:`Floating IPs`, klik :guilabel:`Associate`."
-
-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 ""
-"Dalam dialog box :guilabel:`Import Key Pair` , masukkan nama pasangan kunci "
-"(key pair) Anda, salinlah kunci publik ke dalam box :guilabel:`Public Key`, "
-"dan kemudian klik :guilabel:`Import Key Pair`."
-
-msgid ""
-"In the :guilabel:`Launch Database` dialog box, specify the following values."
-msgstr "Dalam dialog box :guilabel:`Launch Database` , tentukan nilai berikut."
-
-msgid ""
-"In the :guilabel:`Launch Database` dialog box, specify the values you want "
-"for the new database instance."
-msgstr ""
-"Dalam dialog box :guilabel:`Launch Database` , tentukan nilai yang Anda "
-"inginkan untuk instance database baru."
-
-msgid ""
-"In the :guilabel:`Launch Instance` dialog box, specify the following values:"
-msgstr "Dalam dialog box :guilabel:`Launch Instance` , tentukan nilai berikut:"
-
-msgid ""
-"In the :guilabel:`Launch Stack` dialog box, specify the following values:"
-msgstr "Dalam dialog box :guilabel:`Launch Stack` , tentukan nilai berikut:"
-
-msgid ""
-"In the :guilabel:`Manage Floating IP Associations` dialog box, choose the "
-"following options:"
-msgstr ""
-"Dalam dialog box :guilabel:`Manage Floating IP Associations` , pilih opsi "
-"berikut:"
-
-msgid ""
-"In the :guilabel:`Manage Volume Attachments` dialog box, select an instance."
-msgstr ""
-"Dalam dialog box :guilabel:`Manage Volume Attachments` , pilihlah instance."
-
-msgid ""
-"In the :guilabel:`Port to be associated` field, select a port from the list."
-msgstr ""
-"Dalam field (kolom) :guilabel:`Port to be associated`, pilih port dari "
-"daftar."
-
-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 ""
-"Dalam dialog box :guilabel:`Resize Database Instance` , perluas drop down "
-"menu di field (kolom) :guilabel:`New Flavor`. Pilih flavor baru yang Anda "
-"inginkan instance."
-
-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 ""
-"Dalam dialog box :guilabel:`Resize Database Volume` , isi dalam field "
-"(kolom) :guilabel:`New Size` dengan sebuah integer yang menunjukkan ukuran "
-"baru dimana Anda menginginkan instance. Menyatakan ukuran dalam GB, dan "
-"perhatikan bahwa ukuran baru harus lebih besar dari ukuran saat ini."
-
-msgid ""
-"In the :guilabel:`Select Template` dialog box, select the new template "
-"source or environment source."
-msgstr ""
-"Dalam dialog box :guilabel:`Select Template` , pilih sumber template baru "
-"atau sumber lingkungan."
-
-msgid ""
-"In the :guilabel:`Select Template` dialog box, specify the following values:"
-msgstr "Dalam dialog box :guilabel:`Select Template` , tentukan nilai berikut:"
-
-msgid "In the ``PUT`` request, you can specify the path for:"
-msgstr "Dalam permintaan ``PUT``, Anda dapat menentukan jalan (path) untuk:"
-
-msgid "In the actions column, click :guilabel:`Create Snapshot`."
-msgstr "Dalam kolom tindakan, klik :guilabel:`Create Snapshot`."
-
-msgid ""
-"In the address bar, enter the host name or IP address for the dashboard, for "
-"example, ``https://ipAddressOrHostName/``."
-msgstr ""
-"Di address bar, masukkan hostname atau alamat IP untuk dashboard, misalnya, "
-"``https://ipAddressOrHostName/``."
-
-msgid ""
-"In the confirmation dialog box, click :guilabel:`Delete Stack` to confirm "
-"the deletion."
-msgstr ""
-"Pada kotak dialog konfirmasi, klik :guilabel:`Delete Stack` untuk "
-"mengkonfirmasi penghapusan."
-
-msgid "In the destination project:"
-msgstr "Dalam proyek tujuan (destination):"
-
-msgid ""
-"In the dialog box that opens, enter a snapshot name and a brief description."
-msgstr ""
-"Pada kotak dialog yang terbuka, masukkan nama snapshot dan deskripsi singkat."
-
-msgid "In the dialog box that opens, enter or select the following values."
-msgstr "Pada kotak dialog yang terbuka, masukkan atau pilih nilai berikut."
-
-msgid "In the menu list in the actions column, select the state."
-msgstr "Dalam daftar menu di kolom tindakan, pilih kondisi."
-
-msgid "In the new project or cloud environment, import the snapshot:"
-msgstr "Dalam proyek atau cloud lingkungan baru, impor snapshot:"
-
-msgid ""
-"In the new project or cloud environment, use the snapshot to create the new "
-"instance:"
-msgstr ""
-"Dalam proyek atau awan lingkungan baru, gunakan snapshot untuk membuat "
-"instance baru:"
-
-msgid ""
-"In the previous command, ``net1`` is the network name, which is a positional "
-"argument. ``--fixed-ip subnet,ip-address=192.0.2.40`` is an option "
-"which specifies the port's fixed IP address we wanted."
-msgstr ""
-"In the previous command, ``net1`` is the network name, which is a positional "
-"argument. ``--fixed-ip subnet,ip-address=192.0.2.40`` is an option "
-"which specifies the port's fixed IP address we wanted."
-
-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 ""
-"Dalam body request operasi ``POST`` atau ``DELETE``, daftarlah objek atau "
-"kontainer yang akan dihapus. Pisahkan setiap nama dengan karakter baris "
-"baru. Anda dapat menyertakan maksimal 10.000 item (dikonfigurasi) dalam "
-"daftar."
-
-msgid "In the source project:"
-msgstr "Dalam proyek sumber (source):"
-
-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 ""
-"Dalam perintah ini, ``ubuntu-14.04.2-server-amd64.iso`` adalah ISO image, "
-"dan `` INSTANCE_NAME`` adalah nama instance baru. ``NETWORK_UUID`` adalah id "
-"jaringan yang valid dalam sistem Anda."
-
-msgid "In this example, ``--name subnet1`` specifies the name of the subnet."
-msgstr "Dalam contoh ini, ``--name subnet1`` menentukan nama subnet."
-
-msgid ""
-"In this example, ``192.0.2.0/24`` is a positional argument that specifies "
-"the CIDR."
-msgstr ""
-"In this example, ``192.0.2.0/24`` is a positional argument that specifies "
-"the CIDR."
-
-msgid ""
-"In this example, ``net1`` is a positional argument that specifies the "
-"network name."
-msgstr ""
-"Dalam contoh ini, ``net1`` adalah argumen posisi yang menentukan nama "
-"jaringan."
-
-msgid ""
-"In this example, the :command:`trove configuration-parameter-list` command "
-"returns a list of options that work with MySQL 5.5."
-msgstr ""
-"Dalam contoh ini, perintah :command:`trove configuration-parameter-list` "
-"mengembalikan daftar pilihan yang berjalan dengan MySQL 5.5."
-
-msgid ""
-"In this example, the ``X-Delete-After`` header is set to 864000 seconds. The "
-"object expires after this time."
-msgstr ""
-"Dalam contoh ini, header ``X-Delete-After`` diatur untuk 864.000 detik. "
-"Objek berakhir setelah waktu ini."
-
-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 ""
-"Dalam contoh ini, header ``X-Delete-At`` diberikan a UNIX epoch timestamp "
-"dalam bentuk integer untuk ``Mon, 11 Jun 2012 15:38:25 GMT``."
-
-msgid ""
-"In this example, the contents of the configuration drive are as follows::"
-msgstr "Dalam contoh ini, isi dari drive konfigurasi adalah sebagai berikut ::"
-
-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 ""
-"Dalam contoh ini, objek berada dalam kontainer yang disebut ``backups``. "
-"Dalam wadah itu, objek yang diatur dalam pseudo-directory yang disebut "
-"``photos``. Nama kontainer tidak ditampilkan pada contoh, tetapi merupakan "
-"bagian dari URL objek. Sebagai contoh, URL dari gambar ``me.jpg`` adalah "
-"``https://storage.swiftdrive.com/v1/CF_xer7_343/backups/photos/me.jpg``."
-
-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 ""
-"Sertakan query string ``?multipart-manifest = get`` di permintaan ``COPY``. "
-"Objek baru berisi manifest yang sama seperti aslinya. Objek segmen tidak "
-"disalin. Sebaliknya, kedua objek nyata asli dan baru akan berbagi set "
-"(pengaturan) objek segmen yang sama."
-
-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 ""
-"Sertakan header ``X-Versi-Location``. Header ini mendefinisikan kontainer "
-"yang memegang versi non-current objek Anda. Anda harus utf-8-encode dan "
-"kemudian URL-encode nama kontainer sebelum Anda memasukkannya dalam header "
-"``X-Versi-Location``. Header ini memungkinkan objek versi untuk semua objek "
-"dalam kontainer ``current``. Perubahan ke objek dalam kontainer ``current`` "
-"otomatis membuat versi non-current di kontainer ``archive``."
-
-msgid ""
-"Include this header in the ``GET`` request. The valid header values are:"
-msgstr ""
-"Sertakan header ini di request (permintaan) ) ``GET``. Nilai header valid "
-"adalah:"
-
-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 ""
-"Inkremental backup (cadangan) membiarkan Anda rantai bersama serangkaian "
-"backup. Anda mulai dengan cadangan biasa. Kemudian, ketika Anda ingin "
-"membuat backup inkremental berikutnya, Anda menentukan cadangan parent "
-"(parent backup)."
-
-msgid "Information"
-msgstr "Informasi"
-
-msgid ""
-"Inject a keypair into an instance and access the instance with that keypair"
-msgstr ""
-"Inject keypair menjadi sebuah instance dan mengakses instance dengan keypair"
-
-msgid "Inject user data and files into an instance"
-msgstr "Inject data dan file user ke dalam instance"
-
-msgid "Installing OpenStack SDK"
-msgstr "Instalasi OpenStack SDK"
-
-msgid "Instance Boot Source"
-msgstr "Instance Boot Source"
-
-msgid "Instance Name"
-msgstr "Nama Instance"
-
-msgid "Instance Snapshot"
-msgstr "Instance Snapshot"
-
-msgid "Instance name: ``guest1``"
-msgstr "nama name: ``guest1``"
-
-msgid "Instance snapshot that you took."
-msgstr "Instance snapshot yang Anda ambil."
-
-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 ""
-"Instance adalah mesin virtual yang berjalan di dalam cloud pada node "
-"komputasi fisik. Layanan Compute mengelola instance. Sebuah host adalah node "
-"dimana sekelompok instance berada."
-
-msgid "Instances are virtual machines that run inside the cloud."
-msgstr "Instance adalah mesin virtual yang berjalan di dalam cloud."
-
-msgid ""
-"Instances are virtual machines that run inside the cloud. You can launch an "
-"instance from the following sources:"
-msgstr ""
-"Instance adalah mesin virtual yang berjalan di dalam cloud. Anda dapat "
-"memulai sebuah instance dari sumber berikut:"
-
-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 ""
-"Instance yang menggunakan kelompok keamanan default tidak bisa, secara "
-"default, diakses dari alamat IP di luar cloud. Jika Anda ingin mereka alamat "
-"IP untuk mengakses instance, Anda harus memodifikasi aturan untuk grup "
-"keamanan default."
-
-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. Additionally, security groups will automatically drop DHCP "
-"responses coming from instances."
-msgstr ""
-"Instance yang menggunakan kelompok keamanan default tidak bisa, secara "
-"default, diakses dari alamat IP di luar cloud. Jika Anda ingin alamat IP itu "
-"untuk mengakses instance, Anda harus memodifikasi aturan untuk grup keamanan "
-"default. Selain itu, kelompok keamanan otomatis akan turun tanggapan DHCP "
-"yang datang dari instance."
-
-msgid "Instances will now accept all incoming ICMP packets."
-msgstr "Instance sekarang akan menerima semua paket ICMP yang masuk."
-
-msgid ""
-"Instances will now have SSH port 22 open for requests from any IP address."
-msgstr ""
-"Instance tidak akan memiliki SSH port 22 terbuka untuk permintaan dari "
-"alamat IP."
-
-msgid ""
-"Instantiate the ``neutron`` client object by using the ``credentials`` "
-"dictionary object:"
-msgstr ""
-"Instantiate (mencontoh) objek klien ``neutron`` dengan menggunakan objek "
-"kamus ``credentials`` :"
-
-msgid ""
-"Instantiate the ``nova_client`` client object by using the ``credentials`` "
-"dictionary object:"
-msgstr ""
-"Mencontoh (instantiate) objek klien ``nova_client`` dengan menggunakan objek "
-"kamus ``credentials`` :"
-
-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 ""
-"Mengeluarkan request (permintaan) ``DELETE`` ke objek berversi untuk "
-"menghapus versi dari objek dan menggantinya dengan versi berikutnya terbaru "
-"dalam kontainer non-current ini."
-
-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 ""
-"Mengeluarkan request (permintaan) ``GET`` ke objek berversi untuk "
-"mendapatkan versi terbaru dari objek. Anda tidak perlu melakukan apapun "
-"pengalihan permintaan atau pencarian metadata."
-
-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 ""
-"Hal ini juga memungkinkan untuk melakukan SSH ke sebuah instance tanpa "
-"keypair SSH, jika administrator mengaktifkan root password injection. Untuk "
-"informasi lebih lanjut tentang root password injection., lihat `Injecting "
-"the administrator password `_ dalam *OpenStack Administrator Guide*."
-
-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 ""
-"Hal ini juga memungkinkan untuk reboot instance menjalankan ke mode rescue. "
-"Misalnya, operasi ini mungkin diperlukan, jika filesystem dari sebuah "
-"instance menjadi rusak dengan penggunaan jangka panjang."
-
-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 ""
-"Cara terbaik adalah untuk meng-upload semua segmen pertama dan kemudian "
-"membuat atau memperbarui manifes. Dengan metode ini, objek penuh tidak "
-"tersedia untuk di-download sampai upload selesai. Juga, Anda dapat meng-"
-"upload satu set segmen baru ke lokasi kedua dan memperbarui manifes untuk "
-"menunjuk ke lokasi baru ini. Selama upload segmen baru, manifes asli masih "
-"tersedia untuk men-download set segmen pertama."
-
-msgid "Iterate over ``servers_list`` and compare name with ``vm1``."
-msgstr ""
-"Iterasi (iterate) atas ``servers_list`` dan bandingkan nama dengan ``vm1``."
-
-msgid "JSON and data serialization formats"
-msgstr "JSON dan format serialisasi data"
-
-msgid "JSON data serialization response format."
-msgstr "Format respon serialisasi data JSON "
-
-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 ""
-"Perlu diingat, pemeriksaan kesehatan secara rutin dijalankan terhadap setiap "
-"instance dalam penyeimbang beban sasaran dan hasil dari pemeriksaan "
-"kesehatan digunakan untuk menentukan apakah instance akan menerima sambungan "
-"baru."
-
-msgid "Key Pair"
-msgstr "Key Pair (sepasang kunci)"
-
-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 ""
-"Pasangan kunci (key pair) adalah kredensial SSH yang disuntikkan ke sebuah "
-"instance ketika diluncurkan. Untuk menggunakan injeksi pasangan kunci, image "
-"dimana instance harus berdasarkan pada konten paket ``cloud-init``. Setiap "
-"proyek harus memiliki setidaknya satu sepasang kunci. Untuk informasi lebih "
-"lanjut, lihat bagian :ref:`keypair_add`."
-
-msgid "LBaaS v2 has several new concepts to understand:"
-msgstr "LBaaS v2 memiliki beberapa konsep baru untuk memahami:"
-
-msgid "Large objects"
-msgstr "Large objects (benda besar)"
-
-msgid ""
-"Later on, use the :command:`trove backup-list` command to get this "
-"information:"
-msgstr ""
-"Kemudian, gunakan perintah: `perintah harta backup-list` untuk mendapatkan "
-"informasi ini:"
-
-msgid "Launch a stack"
-msgstr "Meluncurkan stack"
-
-msgid "Launch an instance"
-msgstr "Meluncurkan sebuah instance"
-
-msgid "Launch an instance from a bare-metal image"
-msgstr "Meluncurkan sebuah instance dari image bare-metal."
-
-msgid "Launch an instance from a volume"
-msgstr "Meluncurkan sebuah instance dari volume"
-
-msgid "Launch an instance from an image"
-msgstr "Meluncurkan sebuah instance dari sebuah image"
-
-msgid "Launch an instance using ISO image"
-msgstr "Meluncurkan sebuah instance menggunakan image ISO"
-
-msgid "Launch and manage instances"
-msgstr "Peluncuran dan mengelola instance"
-
-msgid "Launch and manage stacks"
-msgstr "Memulai dan mengelola tumpukan (stack)"
-
-msgid "Launch instances"
-msgstr "Peluncuran instance"
-
-msgid ""
-"Least connections: Allocates requests to the instance with the least number "
-"of active connections."
-msgstr ""
-"Least connections: Mengalokasikan permintaan untuk instance dengan "
-"sedikitnya jumlah koneksi aktif."
-
-msgid "Leave this field empty."
-msgstr "Tinggalkan filed ini kosong."
-
-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 ""
-"Membatasi hasil ditetapkan untuk nama yang kurang dari nilai parameter "
-"``end_marker``. Anda harus URL-encode nilai ``end_marker`` sebelum Anda "
-"mengirim permintaan HTTP."
-
-msgid "Link the router to the external provider network:"
-msgstr "Menghubungkan router ke jaringan penyedia eksternal:"
-
-msgid "Link the router to the subnet:"
-msgstr "Menghubungkan router untuk subnet:"
-
-msgid "List Identity service catalog"
-msgstr "Lihat daftar Identity service catalog"
-
-msgid "List Security groups"
-msgstr "Daftar kelompok keamanan (security group)"
-
-msgid "List access."
-msgstr "Daftar akses"
-
-msgid "List all instances:"
-msgstr "Daftar semua instance:"
-
-msgid ""
-"List all project instances with which a floating IP address could be "
-"associated."
-msgstr ""
-"Daftar semua instance proyek dengan yang alamat IP mengambang dapat "
-"dikaitkan."
-
-msgid ""
-"List all the clusters in your system, using the :command:`trove cluster-"
-"list` command."
-msgstr ""
-"Daftar semua cluster dalam sistem anda, gunakan perintah :command:`trove "
-"cluster-list`."
-
-msgid "List all users"
-msgstr "Lihat daftar all users"
-
-msgid "List all volumes, noticing the volume status"
-msgstr "Daftar semua volume, memperhatikan status volume"
-
-msgid "List bare-metal nodes and interfaces"
-msgstr "Daftar node bare-metal dan interface"
-
-msgid "List containers"
-msgstr "Membuat daftar container (wadah)"
-
-msgid "List flavors"
-msgstr "Lihat daftar flavor"
-
-msgid "List flavors (API v2)"
-msgstr "Daftar flavor (API v2)"
-
-msgid "List flavors by calling ``list()`` on ``nova_client.flavors`` object:"
-msgstr ""
-"Daftar rasa dengan pemanggilan ``list()`` pada object ``nova_client."
-"flavors``:"
-
-msgid "List flavors code listing example"
-msgstr "Daftar flavor kode daftar contoh"
-
-msgid "List floating IP address information"
-msgstr "Daftar informasi alamat IP mengambang"
-
-msgid "List floating IPs (API v2)"
-msgstr "Daftar IP mengambang (API v2)"
-
-msgid ""
-"List floating IPs by calling ``list()`` on ``nova_client.floating_ips`` "
-"object:"
-msgstr ""
-"Daftar IP mengambang dengan pemanggilan ``list()`` pada object "
-"``nova_client.floating_ips``:"
-
-msgid "List floating IPs code listing example"
-msgstr "Daftar IP mengambang kode daftar contoh"
-
-msgid "List hosts (API v2)"
-msgstr "Daftar host (API v2)"
-
-msgid "List hosts by calling ``list()`` on ``nova_client.hosts`` object:"
-msgstr ""
-"Daftar hosts dengan pemanggilan ``list()`` pada object ``nova_client."
-"hosts``:"
-
-msgid "List hosts code listing example"
-msgstr "Daftar host kode daftar contoh"
-
-msgid "List images"
-msgstr "Lihat daftar images"
-
-msgid "List images you can access"
-msgstr "Lihat daftar images anda dapat mengakses"
-
-msgid "List instances, check status of instance"
-msgstr "Lihat daftar instances, periksa status instance"
-
-msgid "List keypairs"
-msgstr "Daftar pasangan kunci (keypair)"
-
-msgid "List networks"
-msgstr "Daftar networks"
-
-msgid ""
-"List objects in the ``archive`` container to show that the archived object "
-"was moved back to the ``current`` container:"
-msgstr ""
-"Daftar objek di kontainer ``archive`` untuk menunjukkan bahwa objek "
-"diarsipkan dipindahkan kembali ke kontainer ``current``:"
-
-msgid "List older versions of the object in the ``archive`` container:"
-msgstr "Daftar versi lama dari objek dalam kontainer ``archive``:"
-
-msgid "List ports"
-msgstr "Daftar port"
-
-msgid "List pseudo-hierarchical folders request: HTTP"
-msgstr "Daftar permintaan folder pseudo-hierarchical: HTTP"
-
-msgid "List routers"
-msgstr "Daftar routers"
-
-msgid "List routers: complete code listing example"
-msgstr "Daftar router: kode lengkap listing contoh"
-
-msgid "List samples:"
-msgstr "Lihat daftar sampel:"
-
-msgid "List security groups"
-msgstr "Daftar kelompok keamanan."
-
-msgid "List security groups: complete code listing example"
-msgstr "Daftar kelompok keamanan: kode lengkap daftar contoh"
-
-msgid "List server code listing example"
-msgstr "Daftar kode server pendaftaran contoh"
-
-msgid "List server ports"
-msgstr "Daftar port server"
-
-msgid "List servers (API v2)"
-msgstr "Daftar server (API v2)"
-
-msgid "List servers by calling ``servers.list`` on ``nova_client`` object:"
-msgstr ""
-"Daftar server dengan pemanggilan ``servers.list`` pada object "
-"``nova_client``:"
-
-msgid "List servers: ``servers_list``."
-msgstr "Daftar server: ``servers_list``."
-
-msgid "List share export locations."
-msgstr "Daftar lokasi ekspor share."
-
-msgid "List share networks."
-msgstr "Daftar jaringan bersama (share)"
-
-msgid "List shares."
-msgstr "Daftar share."
-
-msgid "List snapshots after deleting."
-msgstr "Daftar snapshot setelah menghapus."
-
-msgid "List snapshots before deleting."
-msgstr "Daftar snapshot sebelum menghapus."
-
-msgid "List snapshots."
-msgstr "Daftar snapshot."
-
-msgid "List storage devices"
-msgstr "Membuat daftar perangkat penyimpanan"
-
-msgid "List subnets"
-msgstr "Daftar subnets"
-
-msgid "List subnets:"
-msgstr "Daftar subnets:"
-
-msgid "List subnets: complete code listing example"
-msgstr "Daftar subnets: kode lengkap daftar contoh"
-
-msgid "List the alarms that are set:"
-msgstr "Lihat daftar alarm yang ditetapkan:"
-
-msgid "List the available flavors with the following command:"
-msgstr "Daftar flavor tersedia dengan perintah berikut:"
-
-msgid "List the available flavors."
-msgstr "Daftar rasa yang tersedia."
-
-msgid "List the available images."
-msgstr "Daftar image yang tersedia."
-
-msgid ""
-"List the available key pairs, and note the key pair name that you use for "
-"SSH access."
-msgstr ""
-"Daftar pasangan kunci (key pair) yang tersedia, dan perhatikan nama pasangan "
-"kunci yang Anda gunakan untuk akses SSH."
-
-msgid "List the available security groups."
-msgstr "Daftar kelompok keamanan yang tersedia."
-
-msgid "List the extensions of the system:"
-msgstr "Lihat daftar ekstensi dari sistem:"
-
-msgid "List the heat resources that were created:"
-msgstr "Lihat daftar heat resources yang diciptakan:"
-
-msgid ""
-"List the instances in a cluster by using the :command:`trove cluster-"
-"instances` command."
-msgstr ""
-"Daftar instance dalam sebuah cluster dengan menggunakan perintah :command:"
-"`trove cluster-instances`."
-
-msgid "List the meters that are set:"
-msgstr "Lihat daftar meter yang ditetapkan:"
-
-msgid ""
-"List the name of each segment object along with its size and MD5 checksum in "
-"order."
-msgstr ""
-"Daftar nama masing-masing objek segmen bersama dengan ukuran dan MD5 "
-"checksum secara teratur."
-
-msgid ""
-"List the names and IDs of all available versions of the ``mysql`` data store:"
-msgstr ""
-"Daftar nama dan ID dari semua versi yang tersedia dari penyimpanan data "
-"``mysql``:"
-
-msgid "List the routers:"
-msgstr "Daftar router:"
-
-msgid ""
-"List volumes to see the bootable volume and its attached "
-"``myInstanceFromVolume`` instance."
-msgstr ""
-"Daftar volume untuk melihat volume bootable dan yang melekat instance "
-"``myInstanceFromVolume``."
-
-msgid "List volumes."
-msgstr "Daftar volume."
-
-msgid "Listener"
-msgstr "Listener (pendengar)"
-
-msgid "Lists available bare-metal nodes."
-msgstr "Daftar tersedia node bare-metal."
-
-msgid "Lists network interfaces associated with a bare-metal node."
-msgstr "Daftar antarmuka jaringan berhubungan dengan node bare-metal."
-
-msgid "Load balancer"
-msgstr "Load balancer (penyeimbang beban)"
-
-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 ""
-"Load-Balancer-as-a-Service (LBaaS) memungkinkan jaringan untuk "
-"mendistribusikan permintaan yang masuk secara merata di antara instance yang "
-"ditunjuk. Distribusi ini memastikan bahwa beban kerja diperkirakan terbagi "
-"antar instance dan memungkinkan lebih efektif penggunaan sumber daya sistem. "
-"Gunakan salah satu metode load-balancing ini untuk mendistribusikan "
-"permintaan yang masuk:"
-
-msgid "Log in to the OpenStack dashboard."
-msgstr "Log in dashboard OpenStack."
-
-msgid "Log in to the dashboard"
-msgstr "Log in dashboard"
-
-msgid ""
-"Log in to the dashboard, choose a project, and click :guilabel:`Shares`."
-msgstr "Login ke dashboard, pilih proyek, dan klik :guilabel:`Shares`."
-
-msgid ""
-"Log in to the dashboard, choose a project, click :guilabel:`Shares`, and "
-"click :guilabel:`Security Services`."
-msgstr ""
-"Login ke dashboard, pilih proyek, klik :guilabel:`Shares`, dan klik :"
-"guilabel:`Security Services`."
-
-msgid ""
-"Log in to the dashboard, choose a project, click :guilabel:`Shares`, and "
-"click :guilabel:`Share Networks`."
-msgstr ""
-"Login ke dashboard, pilih proyek, klik :guilabel:`Shares`, dan klik :"
-"guilabel:`Share Networks`."
-
-msgid "Log in to the dashboard."
-msgstr "Login ke dashboard."
-
-msgid "Log in to the instance (from Linux)"
-msgstr "Log in ke instance (dari Linux)"
-
-msgid "Log in to the instance with a public IP address (from Mac)"
-msgstr "Log in ke instance dengan alamat IP publik (dari Mac)"
-
-msgid "Make another request with a ``marker`` of the last item returned:"
-msgstr "Membuat permintaan lain dengan ``marker`` dari item terakhir kembali:"
-
-msgid ""
-"Make another request with a ``marker`` parameter set to the name of the last "
-"item returned:"
-msgstr ""
-"Membuat permintaan lain dengan parameter ``marker`` set nama dari item "
-"terakhir kembali:"
-
-msgid "Make container publicly readable"
-msgstr "Membuat wadah (container) dibaca publik"
-
-msgid "Make filesystem on volume"
-msgstr "Membuat filesystem pada volume"
-
-msgid ""
-"Make sure an appropriate flavor exists for the type of database instance you "
-"want."
-msgstr ""
-"Pastikan flavor yang tepat ada untuk tipe instance database yang Anda "
-"inginkan."
-
-msgid "Make sure that you set the relevant environment variables."
-msgstr "Pastikan bahwa Anda mengatur variabel lingkungan yang relevan."
-
-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 ""
-"Membuat kontainer dibaca publik. Setelah kontainer dibaca publik, Anda dapat "
-"mengakses obyek langsung, tetapi Anda harus mengatur file indeks untuk "
-"menelusuri URL situs utama dan sub-direktori nya."
-
-msgid ""
-"Make the image available to the new environment, either through HTTP or "
-"direct upload to a machine (``scp``)."
-msgstr ""
-"Membuat image yang tersedia dengan lingkungan baru, baik melalui HTTP "
-"ataupun upload langsung ke mesin (``scp``)."
-
-msgid "Make the instances booted from ISO image functional"
-msgstr "Membuat instance boot dari ISO image fungsional"
-
-msgid "Manage IP addresses"
-msgstr "Mengelola alamat IP"
-
-msgid "Manage a stack"
-msgstr "Mengelola stack"
-
-msgid "Manage access"
-msgstr "Mengelola akses"
-
-msgid "Manage an instance"
-msgstr "Mengelola sebuah instance"
-
-msgid "Manage an object"
-msgstr "Mengelola obyek"
-
-msgid "Manage bare-metal nodes"
-msgstr "Mengelola node bare-metal"
-
-msgid "Manage database configuration"
-msgstr "Mengelola konfigurasi database"
-
-msgid "Manage images"
-msgstr "Mengelola image"
-
-msgid "Manage images using cURL"
-msgstr "Mengelola image menggunakan cURL"
-
-msgid "Manage instances and hosts"
-msgstr "Mengelola instance dan host"
-
-msgid "Manage objects"
-msgstr "Mengelola objek"
-
-msgid "Manage objects and containers"
-msgstr "Mengelola objek dan kontainer"
-
-msgid "Manage security groups"
-msgstr "Mengelola kelompok keamanan (security group)"
-
-msgid "Manage shares"
-msgstr "mengelola share"
-
-msgid "Manage volumes after login into the instance"
-msgstr "Mengelola volume setelah login ke instance"
-
-msgid "Manifest object metadata"
-msgstr "Metadata objek manifest"
-
-msgid "Measure cloud resources"
-msgstr "Mengukur sumber cloud"
-
-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 ""
-"Mengukur aspek tertentu dari penggunaan sumber daya, seperti adanya instance "
-"menjalankan (running), atau kinerja yang berkelanjutan, seperti penggunaan "
-"CPU untuk sebuah instance. Meter ada untuk setiap jenis sumber daya. "
-"Misalnya, meteran ``cpu_util`` terpisah ada untuk setiap instance. Siklus "
-"hidup meter dipisahkan dari keberadaan sumber daya terkait. Meteran "
-"berlanjut setelah sumber daya hilang."
-
-msgid "Member"
-msgstr "Member (anggota)"
-
-msgid ""
-"Members are the actual IP addresses that receive traffic from the load "
-"balancer. Members are associated with pools."
-msgstr ""
-"Anggota adalah alamat IP aktual yang menerima lalu lintas (traffic) dari "
-"load balancer (penyeimbang beban). Anggota berhubungan dengan kolam (pool)."
-
-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 ""
-"Anggota dapat offline dari waktu ke waktu dan monitor kesehatan mengalihkan "
-"lalu lintas dari anggota yang tidak merespon dengan baik. Monitor kesehatan "
-"berhubungan dengan kolam (pool).."
-
-msgid "Meter"
-msgstr "Meter"
-
-msgid "Method"
-msgstr "Method"
-
-msgid ""
-"Modify a configuration group on the fly, using the :command:`trove "
-"configuration-patch` command."
-msgstr ""
-"Memodifikasi kelompok konfigurasi dengan cepat, dengan menggunakan perintah :"
-"command:`trove configuration-patch`."
-
-msgid ""
-"Modify security group rules with the :command:`openstack security group "
-"rule` commands. Before you begin, source the OpenStack RC file. For details, "
-"see :doc:`../common/cli-set-environment-variables-using-openstack-rc`."
-msgstr ""
-"Memodifikasi aturan grup keamanan dengan perintah :command:`openstack "
-"security group rule`. Sebelum Anda mulai, dapatkan sumber file OpenStack RC. "
-"Untuk rincian, lihat :doc:`../common/cli-set-environment-variables-using-"
-"openstack-rc`."
-
-msgid "MongoDB"
-msgstr "MongoDB"
-
-msgid "Mount the volume at the mountpoint"
-msgstr "Melakukan mount volume pada mountpoint"
-
-msgid "MySQL"
-msgstr "MySQL"
-
-msgid "Name"
-msgstr "Nama"
-
-msgid "Name of the database instance: ``guest1``"
-msgstr "Nama database instance: ``guest1``"
-
-msgid "Name of the instance: ``mysql_instance_1``"
-msgstr "Nama instance: ``mysql_instance_1``"
-
-msgid "Network tab"
-msgstr "Network tab"
-
-msgid "Networking"
-msgstr "Networking"
-
-msgid "Networking (neutron)"
-msgstr "Networking (neutron)"
-
-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 ""
-"Networking dalam OpenStack adalah kompleks. Bagian ini memberikan petunjuk "
-"dasar untuk menciptakan jaringan dan router. Untuk informasi rinci tentang "
-"mengelola jaringan, mengacu pada `OpenStack Administrator Guide `__."
-
-msgid "New users should default to coding against the OpenStack SDK."
-msgstr ""
-"Pengguna baru harus standar (default) untuk pengkodean terhadap OpenStack "
-"SDK."
-
-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 ""
-"Berikutnya, upload manifest. Manifest ini menentukan Kontainer dimana segmen "
-"objek berada. Catatan bahwa jika Anda meng-upload segmen tambahan setelah "
-"Anda membuat manifes, objek bersambung (concatenated) menjadi yang jauh "
-"lebih besar tetapi Anda tidak perlu menciptakan file manifest untuk segmen "
-"tambahan berikutnya."
-
-msgid "No response body is returned."
-msgstr "Tidak ada response body dikembalikan (returned)."
-
-msgid ""
-"No source, empty volume: Creates an empty volume. An empty volume does not "
-"contain a file system or a partition table."
-msgstr ""
-"Tidak ada sumber, volume yang kosong: Membuat volume kosong. Volume kosong "
-"tidak berisi sistem file atau tabel partisi."
-
-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 ""
-"Biasanya, bila Anda melakukan operasi ``GET`` pada objek nyata (manifest), "
-"response body berisi konten bersambung objek segmen. Untuk men-download "
-"daftar manifest, gunakan parameter query ``multipart-manifest = get`` . "
-"Daftar dalam respon tidak diformat sama dengan manifest yang awalnya Anda "
-"gunakan dalam operasi ``PUT``."
-
-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 ""
-"Tidak dijamin. Model konsistensi akhir (eventual consistency model) berarti "
-"bahwa meskipun Anda telah meng-upload sebuah objek segmen, hal itu tidak "
-"mungkin akan muncul dalam daftar kontainer sampai nanti. Jika Anda men-"
-"download manifes sebelum muncul dalam kontainer, hal itu tidak merupakan "
-"bagian dari konten yang kembali dalam menanggapi permintaan ``GET``."
-
-msgid ""
-"Note that the command returns both the ID of the original instance "
-"(``instance_id``) and the ID of the backup artifact (``id``)."
-msgstr ""
-"Perhatikan bahwa hasil perintah kedua ID dari instance asli "
-"(``instance_id``) dan ID dari backup artifact (``id``)."
-
-msgid ""
-"Note that the data store, flavor ID, and volume size have the same values as "
-"in the original ``guest1`` instance."
-msgstr ""
-"Perhatikan bahwa data store, ID flavor, dan ukuran volume yang memiliki "
-"nilai yang sama seperti pada aslinya instance ``guest1``."
-
-msgid ""
-"Note that the system allocates one IP address if you do not specify an IP "
-"address in the :command:`openstack port create` command."
-msgstr ""
-"Perhatikan bahwa sistem akan mengalokasikan satu alamat IP jika Anda tidak "
-"menentukan alamat IP di perintah :command:`openstack port create`."
-
-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 ""
-"Perhatikan bahwa perintah ini kembali baik ID dari instance Anda backing up "
-"secara inkremental (``instance_id``) dan ID baru untuk artefak inkremental "
-"backup baru saja Anda buat (``id``)."
-
-msgid "Note the ID of the flavor that you want to use for your instance::"
-msgstr "Perhatikan ID rasa yang ingin Anda gunakan instance Anda ::"
-
-msgid "Note the ID of the flavor that you want to use to create a volume."
-msgstr "Perhatikan ID dari rasa yang ingin Anda gunakan untuk membuat volume."
-
-msgid "Note the ID of the image from which you want to boot your instance::"
-msgstr "Perhatikan ID dari image yang Anda ingin boot instance Anda ::"
-
-msgid "Note the ID of the image that you want to use to create a volume."
-msgstr "Perhatikan ID dari image yang ingin Anda gunakan untuk membuat volume."
-
-msgid ""
-"Note the ID of the security group that you want to use for your instance::"
-msgstr ""
-"Perhatikan ID dari grup keamanan yang ingin Anda gunakan instance Anda ::"
-
-msgid ""
-"Note the effect of the ``--file /etc/network/interfaces=/home/myuser/"
-"instance-interfaces`` argument that was passed to the :command:`openstack "
-"server create` 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 ""
-"Perhatikan efek dari argumen ``--file /etc/network/interfaces=/home/myuser/"
-"instance-interfaces`` yang dilewatkan ke perintah :command:`openstack server "
-"create`. Isi file ini terkandung dalam file ``openstack/content/0000`` pada "
-"drive konfigurasi, dan path ditetapkan sebagai ``/etc/network/interfaces`` "
-"dalam file ``meta_data.json``."
-
-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 ""
-"Tidak ada yang ditulis ke kontainer versi non-current ketika Anda awalnya "
-"``PUT`` obyek dalam kontainer ``current``. Namun, selanjutnya request "
-"(permintaan) ``PUT`` yang mengedit sebuah objek memicu penciptaan versi "
-"objek yang di kontainer ``archive``."
-
-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 ""
-"Sekarang asumsikan bahwa Anda basis data ``guest1`` instance rusak dan Anda "
-"perlu untuk mengembalikannya dari inkremental backup Anda. Dalam contoh ini, "
-"Anda menggunakan perintah :command:`trove create` untuk membuat sebuah "
-"instance database baru yang disebut ` `guest2``."
-
-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 ""
-"Sekarang asumsikan bahwa Anda basis data instance ``guest1`` rusak dan Anda "
-"perlu untuk mengembalikannya. Dalam contoh ini, Anda menggunakan perintah :"
-"command:`trove create` untuk membuat sebuah instance database baru yang "
-"disebut ` `guest2``."
-
-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 ""
-"Sekarang menganggap bahwa instance database asli Anda rusak dan Anda perlu "
-"untuk mengembalikannya. Anda restore dengan menggunakan cadangan (backup) "
-"Anda untuk membuat sebuah instance database baru."
-
-msgid ""
-"Now check that the new ``guest2`` instance has the same characteristics as "
-"the original ``guest1`` instance."
-msgstr ""
-"Sekarang periksa bahwa baru instance ``guest2`` memiliki karakteristik yang "
-"sama seperti aslinya instance ``guest1``."
-
-msgid ""
-"Now complete the following steps to make your instances created using ISO "
-"image actually functional."
-msgstr ""
-"Sekarang lakukan langkah berikut ini untuk membuat instance Anda yang dibuat "
-"menggunakan image ISO fungsional sebenarnya."
-
-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 ""
-"Sekarang lewatkan dalam ID instance ``base_1`` ini dengan perintah :command:"
-"`trove show` untuk mendaftar replika(s) terkait dengan instance asli. "
-"Perhatikan bahwa properti ``replicas`` diatur ke ID dari ``replica_1``. Jika "
-"ada beberapa replikas, mereka akan muncul sebagai daftar dipisahkan koma "
-"(comma-separated list)."
-
-msgid ""
-"Now take a look at the minimum requirements for various database instances:"
-msgstr ""
-"Sekarang kita lihat persyaratan minimum untuk berbagai Instance database:"
-
-msgid ""
-"Now they are both updated. If the ``--force`` flag is used, it can reapply "
-"to already applied instances. Notice that the only thing that changes is the "
-"minimum and maximum updated date fields."
-msgstr ""
-"Sekarang keduanya diperbarui. Jika flag ``--force`` digunakan, maka dapat "
-"mengajukan permohonan kembali ke instance yang sudah diterapkan. Perhatikan "
-"bahwa satu-satunya perubahan adalah bidang tanggal minimum dan maksimum yang "
-"diperbarui."
-
-msgid "Now to show the usage with a redis cluster, create as follows:"
-msgstr ""
-"Sekarang untuk menunjukkan penggunaan dengan cluster redis, buatlah sebagai "
-"berikut:"
-
-msgid ""
-"Now we have 2 single instances, and 3 cluster instances on various versions "
-"of the module, none current."
-msgstr ""
-"Sekarang kita memiliki 2 instance tunggal, dan 3 instance cluster pada "
-"berbagai versi modul, tidak ada yang ada saat ini."
-
-msgid "Now you can log in to the instance and mount, format, and use the disk."
-msgstr ""
-"Sekarang Anda dapat masuk ke instance dan mount, format, dan menggunakan "
-"disk."
-
-msgid "Object Storage (swift)"
-msgstr "Object Storage (swift)"
-
-msgid ""
-"Object Storage lists container names with additional information in JSON "
-"format:"
-msgstr ""
-"Object Storage berisi nama kontainer dengan informasi tambahan dalam format "
-"JSON:"
-
-msgid ""
-"Object Storage lists container names with additional information in XML "
-"format:"
-msgstr ""
-"Object Storage berisi nama kontainer dengan informasi tambahan dalam format "
-"XML:"
-
-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 ""
-"Object Storage mengambil nilai ``ETag`` dari setiap segmen, merangkai mereka "
-"bersama-sama, dan mengembalikan checksum MD5 hasilnya untuk menghitung nilai "
-"respon header (response header value) ``ETag``. Jenis objek nyata (manifest) "
-"adalah:"
-
-msgid "Object Store tab"
-msgstr "Object Store tab"
-
-msgid "Object expiration"
-msgstr "Objek kedaluwarsa"
-
-msgid "Object versioning"
-msgstr "Object versioning"
-
-msgid ""
-"On running the :command:`openstack server 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 operating system is allowed to "
-"complete the shutdown. The default timeout is 60 seconds. See `Description "
-"of Compute configuration options `_ for details."
-msgstr ""
-"On running the :command:`openstack server 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 operating system is allowed to "
-"complete the shutdown. The default timeout is 60 seconds. See `Description "
-"of Compute configuration options `_ for details."
-
-msgid "On the :guilabel:`Admin` tab, click :guilabel:`Networks` category."
-msgstr "Pada tab :guilabel:`Admin`, klik category :guilabel:`Networks`."
-
-msgid ""
-"On the :guilabel:`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 ""
-"Pada page :guilabel:`Log In`, masukkan username dan password Anda, dan klik :"
-"guilabel:`Sign In`. Jika cloud mendukung model multi-domain, Anda juga harus "
-"memasukkan nama domain Anda."
-
-msgid ""
-"On the :guilabel:`Project` tab, open the :guilabel:`Compute` tab and click :"
-"guilabel:`Access & Security` category."
-msgstr ""
-"Pada tab :guilabel:`Project`, buka tab :guilabel:`Compute`dan klik kategori :"
-"guilabel:`Access & Security`."
-
-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 ""
-"Pada tab :guilabel:`Project`, buka tab :guilabel:`Compute` dan klik "
-"kategori :guilabel:`Access & Security`. Tab :guilabel:`Security Groups` "
-"menunjukkan kelompok keamanan yang tersedia untuk proyek ini."
-
-msgid ""
-"On the :guilabel:`Project` tab, open the :guilabel:`Compute` tab and click :"
-"guilabel:`Images` category."
-msgstr ""
-"Pada tab :guilabel:`Project`, buka tab :guilabel:`Compute` dan klik "
-"kategori :guilabel:`Images`."
-
-msgid ""
-"On the :guilabel:`Project` tab, open the :guilabel:`Compute` tab and click :"
-"guilabel:`Instances` category."
-msgstr ""
-"Pada tab :guilabel:`Project`, buka tab :guilabel:`Compute` dan klik "
-"kategori :guilabel:`Instances`."
-
-msgid ""
-"On the :guilabel:`Project` tab, open the :guilabel:`Compute` tab and click :"
-"guilabel:`Overview` category."
-msgstr ""
-"Pada tab :guilabel:`Project`, buka tab :guilabel:`Compute` dan klik "
-"kategori :guilabel:`Overview`."
-
-msgid ""
-"On the :guilabel:`Project` tab, open the :guilabel:`Compute` tab and click :"
-"guilabel:`Volumes` category."
-msgstr ""
-"Pada tab :guilabel:`Project`, buka tab :guilabel:`Compute` dan klik "
-"kategori :guilabel:`Volumes`."
-
-msgid ""
-"On the :guilabel:`Project` tab, open the :guilabel:`Compute` tab and click "
-"the :guilabel:`Instances` category."
-msgstr ""
-"Pada tab :guilabel:`Project`, buka tab :guilabel:`Compute` dan klik kategori "
-"the :guilabel:`Instances`."
-
-msgid ""
-"On the :guilabel:`Project` tab, open the :guilabel:`Compute` tab and click "
-"the :guilabel:`Volumes` category."
-msgstr ""
-"Pada tab :guilabel:`Project`, buka tab :guilabel:`Compute` dan klik "
-"kategori :guilabel:`Volumes`."
-
-msgid ""
-"On the :guilabel:`Project` tab, open the :guilabel:`Database` tab and click :"
-"guilabel:`Backups` category. This lists the available backups."
-msgstr ""
-"Pada tab :guilabel:`Project`, buka tab :guilabel:`Database` dan klik "
-"kategori :guilabel:`Backups`. Ini berisi daftar backup yang tersedia."
-
-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 ""
-"Pada tab :guilabel:`Project`, buka tab :guilabel:`Database` dan klik "
-"kategori :guilabel:`Instances`. Ini berisi daftar instance yang sudah ada "
-"di lingkungan Anda."
-
-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 ""
-"Pada tab :guilabel:`Project`, buka tab :guilabel:`Database` dan klik "
-"kategori :guilabel:`Instances`. Ini menampilkan instance yang ada dalam "
-"sistem Anda."
-
-msgid ""
-"On the :guilabel:`Project` tab, open the :guilabel:`Network` tab and click :"
-"guilabel:`Networks` category."
-msgstr ""
-"Pada label gui: `tab project`, buka tab :guilabel:`Network` dan klik "
-"kategori :guilabel:`Networks`."
-
-msgid ""
-"On the :guilabel:`Project` tab, open the :guilabel:`Network` tab and click :"
-"guilabel:`Routers` category."
-msgstr ""
-"Pada tab :guilabel:`Project`, buka tab :guilabel:`Network`dan klick "
-"kategori :guilabel:`Routers`."
-
-msgid ""
-"On the :guilabel:`Project` tab, open the :guilabel:`Network` tab, and click "
-"the :guilabel:`Load Balancers` category."
-msgstr ""
-"Pada tab :guilabel:`Project` , buka tab :guilabel:`Network`, dan klik "
-"kategori :guilabel:`Load Balancers`."
-
-msgid ""
-"On the :guilabel:`Project` tab, open the :guilabel:`Object Store` tab and "
-"click :guilabel:`Containers` category."
-msgstr ""
-"Pada tab :guilabel:`Project`, buka tab :guilabel:`Object Store` dan klik "
-"kategori :guilabel:`Containers`."
-
-msgid ""
-"On the :guilabel:`Project` tab, open the :guilabel:`Orchestration` tab and "
-"click :guilabel:`Stacks` category."
-msgstr ""
-"Pada tab :guilabel:`Project`, buka tab :guilabel:`Orchestration` dan klik "
-"kategori :guilabel:`Stacks`."
-
-msgid ""
-"On the :guilabel:`Router Details` page, click the :guilabel:`Interfaces` "
-"tab, then click :guilabel:`Add Interface`."
-msgstr ""
-"Pada page :guilabel:`Router Details`, klick tab :guilabel:`Interfaces`, "
-"kemudian klik :guilabel:`Add Interface`."
-
-msgid "On the :guilabel:`Routers` tab, click the name of the router."
-msgstr "Pada tab :guilabel:`Routers`, klik nama router."
-
-msgid ""
-"On the Xen Hypervisor it is possible to provide a specific device name "
-"instead of automatic allocation. For example:"
-msgstr ""
-"Di Xen Hypervisor, sesuatu hal yang mungkin untuk memberikan nama perangkat "
-"tertentu bukannya alokasi otomatis. Sebagai contoh:"
-
-msgid "Once identified, you can mount the device:"
-msgstr "Setelah diidentifikasi, Anda dapat me-mount perangkat:"
-
-msgid ""
-"One or more *config servers*. Config servers store the metadata that links "
-"requested data with the shard that contains it."
-msgstr ""
-"Satu atau lebih *config server *. Server config menyimpan metadata yang "
-"menghubungkan data yang diminta dengan pecahan (shard) yang mengisi data "
-"itu."
-
-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 ""
-"Satu atau lebih *query routers*. Sebuah router kueri adalah mesin dimana "
-"aplikasi Anda benar-benar terhubung. Mesin ini bertanggung jawab untuk "
-"berkomunikasi dengan server config untuk mencari tahu dimana data yang "
-"diminta. Kemudian mesin ini mengakses dan mengembalikan data dari pecahan "
-"yang sesuai (appropriate shard)."
-
-msgid ""
-"One or more *shards*. Each shard consists of a three member replica set "
-"(three instances organized as a replica set)."
-msgstr ""
-"Satu atau lebih *shards*. Setiap pecahan (*shards*) terdiri dari set replika "
-"tiga anggota (tiga instance diatur sebagai satu set replika)."
-
-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 ""
-"Satu kasus digunakan untuk menggunakan drive konfigurasi adalah untuk lulus "
-"konfigurasi jaringan bila Anda tidak menggunakan DHCP untuk menetapkan "
-"alamat IP untuk instance. Misalnya, Anda mungkin lulus konfigurasi alamat IP "
-"untuk instance melalui drive konfigurasi, yang instance dapat me-mount dan "
-"akses sebelum Anda mengkonfigurasi pengaturan jaringan instance."
-
-msgid "Open a web browser that has JavaScript and cookies enabled."
-msgstr "Buka web browser yang memiliki JavaScript dan cookie diaktifkan."
-
-msgid "OpenStack End User Guide"
-msgstr "OpenStack End User Guide (Panduan End User OpenStack)"
-
-msgid ""
-"OpenStack Networking security groups are case-sensitive while the nova-"
-"network security groups are case-insensitive."
-msgstr ""
-"Kelompok keamanan OpenStack Networking berkarakter huruf case-sensitive "
-"sedangkan kelompok keamanan nova-network berkarakter huruf case-insensitive."
-
-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 ""
-"OpenStack Object Storage (swift) digunakan untuk penyimpanan berlebihan, "
-"data terukur menggunakan cluster server standar untuk menyimpan petabyte "
-"data diakses. Ini adalah sistem penyimpanan jangka panjang untuk sejumlah "
-"besar data statis yang dapat diambil dan diperbarui."
-
-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 ""
-"OpenStack Object Storage menyediakan didistribusikan, platform penyimpanan "
-"API-accessible yang dapat diintegrasikan langsung ke aplikasi atau digunakan "
-"untuk menyimpan semua jenis file, termasuk image VM, backup, arsip, atau "
-"file media. Di dashboard OpenStack, Anda hanya dapat mengelola kontainer dan "
-"objek."
-
-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 ""
-"OpenStack Orchestration adalah layanan yang dapat Anda gunakan untuk "
-"mengatur beberapa aplikasi cloud komposit. Layanan ini mendukung penggunaan "
-"format template Amazon Web Services (AWS) CloudFormation melalui format "
-"Query API yang kompatibel dengan CloudFormation ataupun format asli "
-"OpenStack :term:`Heat Orchestration Template (HOT)` melalui REST API."
-
-msgid "OpenStack Python SDK"
-msgstr "OpenStack Python SDK"
-
-msgid "OpenStack SDK"
-msgstr "OpenStack SDK"
-
-msgid "OpenStack command-line clients"
-msgstr "OpenStack klien baris perintah (command-line client)"
-
-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 ""
-"Klien baris perintah OpenStack: Setiap proyek OpenStack inti memiliki klien "
-"baris perintah (command-line client) yang dapat Anda gunakan untuk "
-"menjalankan perintah sederhana untuk melihat, membuat, dan mengelola sumber "
-"daya di cloud dan mengotomatisasi tugas dengan menggunakan script."
-
-msgid "OpenStack command-line interface cheat sheet"
-msgstr "OpenStack lembar contekan antarmuka baris perintah (command-line)"
-
-msgid "OpenStack dashboard"
-msgstr "Dashboard OpenStack"
-
-msgid "OpenStack dashboard — Admin tab"
-msgstr "OpenStack dashboard — Admin tab"
-
-msgid "OpenStack dashboard — Identity tab"
-msgstr "OpenStack dashboard — Identity tab"
-
-msgid "OpenStack dashboard — Project tab"
-msgstr "OpenStack dashboard — Project tab"
-
-msgid "OpenStack dashboard — Settings tab"
-msgstr "OpenStack dashboard — Settings tab"
-
-msgid ""
-"OpenStack dashboard: Use this web-based graphical interface, code named "
-"`horizon `__, to view, "
-"create, and manage resources."
-msgstr ""
-"OpenStack dashboard: Gunakan antarmuka grafis berbasis web ini, kode dinamai "
-"`horizon `__, untuk "
-"melihat, membuat, dan mengelola sumber daya."
-
-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 ""
-"OpenStack merupakan open-source platform komputasi cloud untuk cloud publik "
-"dan private. Serangkaian proyek yang saling terkait memberikan solusi "
-"infrastruktur cloud. Panduan ini menunjukkan pengguna akhir OpenStack "
-"tentang cara membuat dan mengelola sumber daya di cloud OpenStack dengan "
-"dashboard OpenStack dan perintah klien OpenStack."
-
-msgid "OpenStack metadata format"
-msgstr "Format metadata OpenStack"
-
-msgid ""
-"OpenStack provides four different options for interacting with its APIs from "
-"Python, each targeting a slightly different user:"
-msgstr ""
-"OpenStack menyediakan empat pilihan yang berbeda untuk berinteraksi dengan "
-"API dari Python, masing-masing menargetkan pengguna yang sedikit berbeda:"
-
-msgid ""
-"OpenStack supports booting instances using ISO images. But before you make "
-"such instances functional, use the :command:`openstack server create` "
-"command with the following parameters to boot an instance:"
-msgstr ""
-"OpenStack mendukung instance booting menggunakan image ISO. Tapi sebelum "
-"Anda membuat instance seperti fungsional, gunakan perintah :command:"
-"`openstack server create` dengan parameter berikut untuk boot sebuah "
-"instance:"
-
-msgid "Operating system"
-msgstr "Sistem operasi"
-
-msgid ""
-"Optionally provide a comma separated list of databases to create, for "
-"example:"
-msgstr ""
-"Secara opsional memberikan daftar database dipisahkan dengan koma dalam "
-"pembuatan, misalnya:"
-
-msgid "Optionally, a specific container"
-msgstr "Opsional, wadah spesifik (specific container)"
-
-msgid "Optionally, a specific object prefix"
-msgstr "Opsional, awalan objek spesifik (specific object prefix)"
-
-msgid ""
-"Optionally, in the :guilabel:`Add Interface` dialog box, set an :guilabel:"
-"`IP Address` for the router interface for the selected subnet."
-msgstr ""
-"Secara optional, dalam dialog box :guilabel:`Add Interface` , aturlah :"
-"guilabel:`IP Address` untuk antarmuka router untuk subnet yang dipilih."
-
-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 ``--"
-"property description=\"My Server\"`` parameter."
-msgstr ""
-"Secara opsional, Anda dapat memberikan nama kunci untuk kontrol akses dan "
-"kelompok keamanan untuk keamanan. Anda juga bisa memasukkan kunci metadata "
-"dan nilai pasangan. Misalnya, Anda dapat menambahkan deskripsi untuk server "
-"Anda dengan penyediaan parameter ``--property description = \"My Server\"``."
-
-msgid ""
-"Orchestration is compatible with the CloudFormation template, but you can "
-"also write heat templates to orchestrate cloud resources."
-msgstr ""
-"Orchestration kompatibel dengan template CloudFormation, tetapi Anda juga "
-"dapat menulis template heat (heat template) untuk mengatur sumber daya cloud."
-
-msgid "Orchestration tab"
-msgstr "Orchestration tab"
-
-msgid "Origin"
-msgstr "Origin (asal muasal)"
-
-msgid "Overview"
-msgstr "Iktisar"
-
-msgid "Page through large lists of containers or objects"
-msgstr ""
-"Halaman keseluruhan daftar besar kontainer atau objek (containers atau "
-"objects)"
-
-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 ""
-"Lewatkan dalam ID instance ``replica_1`` ini dengan perintah :command:"
-"`trove show` untuk memverifikasi bahwa instance ``replica_1`` baru dibuat "
-"adalah replika dari yang asli ``base_1``. Perhatikan bahwa ``replica_of`` "
-"properti diatur ke ID dari ``base_1``."
-
-msgid ""
-"Pass in the data store version ID with the :command:`trove configuration-"
-"parameter-list` command to get the available options:"
-msgstr ""
-"Melewatkan dalam ID versi penyimpanan data dengan perintah :command:`trove "
-"configuration-parameter-list` untuk mendapatkan opsi yang tersedia:"
-
-msgid "Pause"
-msgstr "Pause (berhenti sebentar)"
-
-msgid "Pause and unpause an instance"
-msgstr "Menunda dan melanjutkan sebuah instance"
-
-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 ""
-"Jeda, menangguhkan, dan berhenti operasi tidak diperbolehkan ketika sebuah "
-"instance berjalan dalam modus penyelamatan (rescue), seperti memicu tindakan "
-"ini menyebabkan hilangnya instance keadaan semula, dan tidak memungkinkan "
-"untuk unrescue instance."
-
-msgid "Pause, suspend, stop, rescue, resize, rebuild, reboot an instance"
-msgstr "Pause, suspend, stop, rescue, resize, rebuild, reboot instance"
-
-msgid "Per-project client libraries"
-msgstr " Perpustakaan klien per-proyek"
-
-msgid "Plain text response format. The default."
-msgstr "Format respon plain text. Default."
-
-msgid "Pool"
-msgstr "Pool (kolam)"
-
-msgid "Ports"
-msgstr "Ports"
-
-msgid "Print the flavor details, id and name by calling ``print_flavors``:"
-msgstr ""
-"Mencetak rincian flavor, id dan nama dengan pemanggilan ``print_flavors``:"
-
-msgid "Print the floating IP object details by calling ``print_values_ip``:"
-msgstr ""
-"Cetak rincian objek IP mengambang dengan pemanggilan ``print_values_ip``:"
-
-msgid "Print the host object details by calling ``print_hosts(host_list)``:"
-msgstr ""
-"Mencetak rincian obyek host dengan pemanggilan ``print_hosts(host_list)``:"
-
-msgid "Print values"
-msgstr "Cetak nilai"
-
-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 ""
-"Proyek adalah unit organisasi di cloud dan juga dikenal sebagai penyewa "
-"(tenant) atau rekening (account). Setiap pengguna (user) adalah anggota dari "
-"satu atau lebih proyek. Dalam sebuah proyek, pengguna membuat dan mengelola "
-"instance."
-
-msgid "Provide user data to instances"
-msgstr "Memberikan data user ke instance"
-
-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 ""
-"Pseudo-folder adalah serupa dengan folder dalam sistem operasi desktop Anda. "
-"Mereka adalah koleksi maya didefinisikan oleh prefiks umum pada nama objek."
-
-msgid "Pseudo-hierarchical folders and directories"
-msgstr "Folder dan direktori pseudo-hierarchical "
-
-msgid "Query ports with specified fixed IP addresses:"
-msgstr "Query port dengan alamat IP tetap tertentu:"
-
-msgid "Query routers and config servers"
-msgstr "Router kueri dan server config"
-
-msgid "RAM (MB)"
-msgstr "RAM (MB)"
-
-msgid "RAM: ``512``"
-msgstr "RAM: ``512``"
-
-msgid "RESTful web services"
-msgstr "Layanan web RESTful "
-
-msgid "Reboot"
-msgstr "Reboot (booting ulang)"
-
-msgid "Reboot an instance"
-msgstr "Reboot instance"
-
-msgid "Rebuild"
-msgstr "Rebuild (membangun kembali)"
-
-msgid "Redis"
-msgstr "Redis"
-
-msgid "Reference for cloud-init version"
-msgstr "Referensi untuk versi cloud-init"
-
-msgid "Register raw image"
-msgstr "Register raw image"
-
-msgid "Removal or addition of segment objects"
-msgstr "Penghapusan atau penambahan objek segmen"
-
-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 ""
-"Hapus instance dipetieskan - Menghapus instance dari server; asosiasi data "
-"dan sumber daya akan dihapus. Jika instance tidak lagi diperlukan, Anda "
-"dapat memindahkan instance dari hypervisor untuk meminimalkan penggunaan "
-"sumber daya."
-
-msgid "Removes a bare-metal node and any associated interfaces."
-msgstr "Menghapus node bare-metal dan setiap interface yang terkait."
-
-msgid "Removes a network interface from a bare-metal node."
-msgstr "Menghapus antarmuka jaringan dari node bare-metal."
-
-msgid ""
-"Replace ROUTER with the unique identifier of the router, replace NETWORK "
-"with the unique identifier of the external provider network."
-msgstr ""
-"Ganti ROUTER dengan identifier unik router, ganti NETWORK dengan identifier "
-"unik dari jaringan operator eksternal."
-
-msgid ""
-"Replace ROUTER with the unique identifier of the router, replace SUBNET with "
-"the unique identifier of the subnet."
-msgstr ""
-"Ganti ROUTER dengan identifier unik router, ganti SUBNET dengan identifier "
-"unik subnet."
-
-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 ""
-"Ganti ``DATASTORE_NAME`` dengan nama yang pengguna administratif ditetapkan "
-"pada saat menerbitkan perintah :command:`trove-manage` untuk membuat "
-"datastore. Anda dapat menggunakan perintah trove :command:`datastore-list` "
-"untuk menampilkan datastore yang tersedia di lingkungan Anda."
-
-msgid "Replicas are read-only."
-msgstr "Replika read-only."
-
-msgid "Requirements and guidelines"
-msgstr "Persyaratan dan pedoman"
-
-msgid "Rescue"
-msgstr "Rescue (menyelamatkan)"
-
-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 ""
-"Mode penyelamatan (rescue) menyediakan mekanisme untuk akses, bahkan jika "
-"image menjadikan instance tidak dapat diakses. Secara default, itu dimulai "
-"sebuah instance dari image awal menghubungkan boot disk saat ini sebagai "
-"salah satu instance sekunder."
-
-msgid "Resize"
-msgstr "Resize (mengubah ukuran)"
-
-msgid "Resources"
-msgstr "Summer days"
-
-msgid "Respond to the prompt to download the key pair."
-msgstr "Menanggapi permintaan untuk mengunduh sepasang kunci (key pair)."
-
-msgid "Restart Database services on the controller node:"
-msgstr "Restart layanan Database pada kontroler node:"
-
-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 ""
-"Memulihkan name database dari inkremental backup (cadangan) adalah sama "
-"seperti membuat name database dari cadangan-layanan database biasa menangani "
-"kompleksitas menerapkan rantai inkremental backup."
-
-msgid "Root volume size in GB: ``5``"
-msgstr "Ukuran volume root dalam GB: ``5``"
-
-msgid "Root volume size: ``2``"
-msgstr "Root volume size: ``2``"
-
-msgid "Round robin: Rotates requests evenly between multiple instances."
-msgstr "Round robin: Memutar permintaan merata antara beberapa instance."
-
-msgid "Rules are automatically enforced as soon as you create or modify them."
-msgstr ""
-"Aturan secara otomatis diberlakukan segera setelah Anda membuat atau "
-"memodifikasi mereka."
-
-msgid ""
-"Run the \"Sleep for five seconds\" command, and determine whether the server/"
-"vm was created by calling ``nova_client.servers.list()``:"
-msgstr ""
-"Jalankan (run) perintah \"Sleep for five seconds\", dan tentukan apakah "
-"server/vm dibuat dengan pemanggilan ``nova_client.servers.list()``:"
-
-msgid ""
-"Run the :command:`openstack server delete` command to delete the instance. "
-"The following example shows deletion of the ``newServer`` instance, which is "
-"in ``ERROR`` state:"
-msgstr ""
-"Jalankan perintah :command:`openstack server delete` untuk menghapus "
-"instance. Contoh berikut menunjukkan penghapusan instance ``newServer``, "
-"yang dalam keadaan ``ERROR``:"
-
-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 ""
-"Jalankan perintah berikut untuk mengalokasikan alamat IP mengambang untuk "
-"proyek ini. Secara default, alamat IP mengambang dialokasikan dari kolam "
-"umum (public pool). Perintah output alamat IP yang dialokasikan:"
-
-msgid "Sample"
-msgstr "Sample"
-
-msgid "Save the ``*.pem`` file locally."
-msgstr "Simpan file ``*.pem`` secara local."
-
-msgid "Schedule objects for deletion"
-msgstr "Jadwal objek untuk penghapusan"
-
-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 ""
-"Penjadwalan obyek untuk penghapusan membantu untuk mengelola objek yang Anda "
-"tidak ingin menyimpan secara permanen, seperti file log, backup penuh dari "
-"dataset berulang, atau dokumen atau image yang menjadi usang pada waktu "
-"tertentu."
-
-msgid "Search for an instance using IP address"
-msgstr "Mencari instance menggunakan alamat IP"
-
-msgid "Security Groups"
-msgstr "Security Groups (kelompok keamanan)"
-
-msgid ""
-"Security groups are a kind of cloud firewall that define which incoming "
-"network traffic is forwarded to instances."
-msgstr ""
-"Kelompok keamanan adalah jenis firewall cloud yang menentukan dimana traffic "
-"jaringan yang masuk diteruskan ke instance."
-
-msgid ""
-"See the Cloud Administrator Guide for a complete example of the `/etc/swift/"
-"proxy-server.conf file `_ "
-"(including static web)."
-msgstr ""
-"Lihat Cloud Administrator Guide untuk contoh lengkap dari `/etc/swift/proxy-"
-"server.conf file `_ "
-"(termasuk web statis)."
-
-msgid ""
-"See the Cloud Administrator Guide for an example of the `static web "
-"configuration syntax `_."
-msgstr ""
-"Lihat Cloud Administrator Guide untuk contoh `static web configuration "
-"syntax `_."
-
-msgid "Segment object container name"
-msgstr "Nama kontainer objek segmen "
-
-msgid "Segment object size and number"
-msgstr "Ukuran dan nomor objek segmen "
-
-msgid "Segment objects can be any size."
-msgstr "Objek segmen dapat berbagai ukuran."
-
-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 ""
-"Objek segmen harus minimal 1 MB (secara default). Objek segmen akhir dapat "
-"ukuran. Paling banyak, 1000 segmen yang didukung (secara default)."
-
-msgid "Select a volume from which to create a snapshot."
-msgstr "Pilih volume yang untuk membuat snapshot."
-
-msgid "Select an instance."
-msgstr "Pilih sebuah instance."
-
-msgid "Select the :guilabel:`Public` check box to make the image public."
-msgstr "Pilih check box :guilabel:`Public` untuk membuat image publik."
-
-msgid "Select the appropriate project from the drop down menu at the top left."
-msgstr "Pilih proyek yang sesuai dari menu drop down di bagian kiri atas."
-
-msgid "Select the appropriate project from the drop-down menu at the top left."
-msgstr "Pilih proyek yang sesuai dari menu drop-down di bagian kiri atas."
-
-msgid ""
-"Select the check boxes for the security services that you want to delete."
-msgstr ""
-"Pilih kotak centang (check box) untuk layanan keamanan yang ingin Anda hapus."
-
-msgid "Select the check boxes for the share networks that you want to delete."
-msgstr ""
-"Pilih kotak centang (check box) untuk jaringan bersama yang ingin Anda hapus."
-
-msgid "Select the check boxes for the shares that you want to delete."
-msgstr "Pilih kotak centang (check box) untuk share yang ingin Anda hapus."
-
-msgid "Select the check boxes for the volumes that you want to delete."
-msgstr "Pilih kotak centang (check box) untuk volume yang ingin Anda hapus."
-
-msgid "Select the container in which you want to store your object."
-msgstr "Pilih wadah di mana Anda ingin menyimpan objek."
-
-msgid "Select the default security group and click :guilabel:`Manage Rules`."
-msgstr "Pilih kelompok keamanan default dan klik :guilabel:`Manage Rules`."
-
-msgid "Select the image format (for example, QCOW2) for the image."
-msgstr "Pilih format image (misalnya, QCOW2) untuk image."
-
-msgid "Select the image that you want to edit."
-msgstr "Pilih image yang ingin Anda edit."
-
-msgid "Select the images that you want to delete."
-msgstr "Pilih image yang ingin Anda hapus."
-
-msgid "Select the instance from which to create a snapshot."
-msgstr "Pilih instance yang membuat snapshot."
-
-msgid "Select the instance you want to back up."
-msgstr "Pilih instance Anda ingin membuat cadangan (backup)"
-
-msgid ""
-"Select the load balancer you want to delete and click the :guilabel:`Delete "
-"Load Balancer` button."
-msgstr ""
-"Pilih penyeimbang beban yang ingin Anda hapus dan klik tombol :guilabel:"
-"`Delete Load Balancer`."
-
-msgid "Select the stack that you want to delete."
-msgstr "Pilih stack yang ingin Anda hapus."
-
-msgid "Select the stack that you want to update."
-msgstr "Pilih stack yang ingin Anda update."
-
-msgid "Select the volume and click :guilabel:`Manage Attachments`."
-msgstr "Pilih volume dan klik :guilabel:`Manage Attachments`."
-
-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 ""
-"Pilih volume atau volume snapshot dari mana untuk boot. Masukkan nama "
-"perangkat. Masukkan ``vda`` untuk image KVM atau ``xvda`` untuk image Xen."
-
-msgid "Select the volume that you want to edit."
-msgstr "Pilih volume yang ingin Anda edit."
-
-msgid ""
-"Select the volume to add to an instance and click :guilabel:`Manage "
-"Attachments`."
-msgstr ""
-"Pilih volume untuk menambahkan ke sebuah instance dan klik :guilabel:"
-"`Manage Attachments`."
-
-msgid ""
-"Select this check box if you want the service to roll back changes if the "
-"stack fails to launch."
-msgstr ""
-"Pilih kotak centang (check box) ini jika Anda ingin layanan untuk memutar "
-"kembali perubahan ke semula (roll back change) jika tumpukan gagal untuk "
-"memulai meluncur."
-
-msgid ""
-"Select this check box to ensure that only users with permissions can delete "
-"the image. ``Yes`` or ``No``."
-msgstr ""
-"Pilih kotak centang (check box) ini untuk memastikan bahwa hanya pengguna "
-"dengan hak akses dapat menghapus image. ``Yes`` atau ``No``."
-
-msgid "Selected Networks"
-msgstr "Jaringan yang dipilih (Selected Networks)"
-
-msgid "Serialized response formats"
-msgstr "Format respon serial"
-
-msgid ""
-"Server names are not guaranteed to be unique when created so you could have "
-"two instances with the same host name."
-msgstr ""
-"Nama server tidak dijamin untuk menjadi unik ketika dibuat sehingga Anda "
-"bisa memiliki dua instance dengan nama host yang sama."
-
-msgid "Set *VALUES* as a JSON dictionary, for example:"
-msgstr "Set *VALUES* sebagai kamus JSON, misalnya:"
-
-msgid "Set an object to expire after a relative amount of time (in seconds):"
-msgstr "Atur objek untuk berakhir setelah jumlah waktu relatif (dalam detik):"
-
-msgid ""
-"Set an object to expire at an absolute time (in Unix time). You can get the "
-"current Unix time by running ``date +'%s'``."
-msgstr ""
-"Atur objek untuk berakhir pada waktu yang mutlak (dalam waktu Unix). Anda "
-"bisa mendapatkan waktu Unix saat ini dengan menjalankan ``date +'%s'``."
-
-msgid "Set environment variables"
-msgstr "Atur variabel lingkungan"
-
-msgid "Set error pages for static website"
-msgstr "Mengatur halaman kesalahan untuk website statis"
-
-msgid "Set error pages for static website request"
-msgstr "Mengatur halaman kesalahan untuk permintaan website statis"
-
-msgid "Set metadata on an instance"
-msgstr "Set metadata on an instance (mengatur metadata pada instance)"
-
-msgid "Set site index file"
-msgstr "Atur file index site"
-
-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 ""
-"Atur parameter ``--availability-zone`` untuk menentukan zona atau node "
-"digunakan untuk memulai server. Pisahkan zona dari nama host dengan koma. "
-"Sebagai contoh:"
-
-msgid "Set the ``Content-Type`` request header to ``text/plain``."
-msgstr "Mengatur request header ``Content-Type`` ke ``text/plain``."
-
-msgid ""
-"Set the index file. In this case, ``index.html`` is the default file "
-"displayed when the site appears."
-msgstr ""
-"Mengatur file indeks. Dalam hal ini, ``index.html`` adalah file default "
-"ditampilkan ketika situs muncul."
-
-msgid "Set up clustering"
-msgstr "Mengatur pengelompokan (clustering)"
-
-msgid "Set up database clustering"
-msgstr "Pengaturan pengelompokan database"
-
-msgid "Set up database replication"
-msgstr "Mengatur replikasi database"
-
-msgid "Set up replication"
-msgstr "Mengatur replikasi"
-
-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 ""
-"Share adalah penyimpanan file yang Anda berikan akses ke instance. Anda "
-"dapat mengizinkan akses berbagi (share) untuk instance yang sedang berjalan "
-"atau menolak akses berbagi dan mengizinkan akses itu untuk instance lain "
-"setiap saat. Anda juga dapat menghapus share. Anda dapat membuat snapshot "
-"dari share jika driver mendukungnya. Hanya pengguna administratif dapat "
-"membuat tipe share."
-
-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 ""
-"Meletakan (shelve) sebuah instance - Mematikan (shut down) instance, "
-"danpenyimpanan bersama-sama dengan data terkait dan sumber daya (snapshot "
-"diambil jika bukan volume didukung). Apa pun di memori hilang."
-
-msgid "Shelve and unshelve an instance"
-msgstr "Meletakan (shelve) dan unshelve sebuah instance"
-
-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 ""
-"Peletakan (shelving) berguna jika Anda memiliki sebuah instance bahwa Anda "
-"tidak menggunakan, namun ingin mempertahankan di daftar server. Misalnya, "
-"Anda dapat menghentikan sebuah instance pada akhir minggu kerja, dan "
-"melanjutkan pekerjaan lagi pada awal minggu depan. Semua data dan sumber "
-"daya terkait disimpan; Namun, apa pun masih dalam memori tidak "
-"dipertahankan. Jika instance dipetieskan (shelved) tidak lagi diperlukan, "
-"juga dapat sepenuhnya dihapus."
-
-msgid "Show a share."
-msgstr "Tampilkan share"
-
-msgid "Show details for a bare-metal node"
-msgstr "Tampilkan detail untuk node bare-metal"
-
-msgid "Show details of instance"
-msgstr "Show details instance (tampilkan detail instance)"
-
-msgid ""
-"Show information about your server, including its size, which is shown as "
-"the value of the flavor property:"
-msgstr ""
-"Tampilkan informasi tentang server Anda, termasuk ukurannya, yang "
-"ditampilkan sebagai nilai properti flavor:"
-
-msgid "Show the share after it is being shrunk."
-msgstr "Tampilkan share setelah menyusut."
-
-msgid "Show the share after it is extended."
-msgstr "Tampilkan share setelah diperpanjang."
-
-msgid "Show the share created from snapshot."
-msgstr "Tampilkan share dibuat dari snapshot."
-
-msgid "Show the share while it is being extended."
-msgstr "Tampilkan share saat sedang diperpanjang."
-
-msgid "Show the share while it is being shrunk."
-msgstr "Tampilkan share saat sedang menyusut."
-
-msgid "Show the status for your server."
-msgstr "Tampilkan status server Anda."
-
-msgid "Shows information about a bare-metal node."
-msgstr "Menampilkan informasi tentang node bare-metal."
-
-msgid "Shrink a share."
-msgstr "Kecilkan share."
-
-msgid "Shrink share"
-msgstr "Kecilkan share"
-
-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 ""
-"Matikan (shut down) sumber VM sebelum Anda mengambil snapshot untuk "
-"memastikan bahwa semua data mengalir (flushed) ke disk. Jika perlu, "
-"daftarlah instance untuk melihat nama instance:"
-
-msgid ""
-"Snapshot: If you choose this option, a new field for :guilabel:`Use snapshot "
-"as a source` displays. You can select the snapshot from the list."
-msgstr ""
-"Snapshot: Jika Anda memilih opsi ini, field baru untuk menampilkan :"
-"guilabel:`Use snapshot as a source`. Anda dapat memilih snapshot dari daftar."
-
-msgid "Some cloud providers allow only administrators to perform this task."
-msgstr ""
-"Beberapa penyedia cloud mengizinkan hanya administrator untuk melakukan "
-"tugas ini."
-
-msgid "Some fields of the created network are invisible to non-admin users."
-msgstr ""
-"Beberapa bidang jaringan dibuat tidak terlihat oleh pengguna non-admin."
-
-msgid ""
-"Some resources are updated in-place, while others are replaced with new "
-"resources."
-msgstr ""
-"Beberapa sumber diperbarui di tempat, sementara yang lain diganti dengan "
-"sumber daya baru."
-
-msgid ""
-"Some resources have associated metadata which can change throughout the "
-"lifecycle of a resource. Show the metadata by running the following command:"
-msgstr ""
-"Beberapa sumber telah dikaitkan metadata yang dapat mengubah seluruh siklus "
-"hidup dari sumber daya. Tampilkan metadata dengan menjalankan perintah "
-"berikut:"
-
-msgid ""
-"Some tabs, such as :guilabel:`Orchestration` and :guilabel:`Firewalls`, only "
-"appear on the dashboard if they are properly configured."
-msgstr ""
-"Beberapa tab, seperti :guilabel:`Orchestration` dan :guilabel:`Firewalls`, "
-"hanya muncul di dashboard jika mereka dikonfigurasi dengan benar."
-
-msgid ""
-"Source IP: Requests from a unique source IP address are consistently "
-"directed to the same instance."
-msgstr ""
-"IP sumber (Source IP): Permintaan dari alamat IP sumber yang unik secara "
-"konsisten diarahkan untuk instance yang sama."
-
-msgid "Specify a customization script that runs after your instance launches."
-msgstr ""
-"Tentukan kustomisasi script yang sudah berjalan benar setelah instance Anda "
-"diluncurkan."
-
-msgid "Specify a key pair."
-msgstr "Tentukan sepasang kunci (key pair)."
-
-msgid "Specify a name for the backup."
-msgstr "Tentukan nama untuk cadangan (backup)"
-
-msgid "Specify the Linux distribution that is used in the stack."
-msgstr "Tentukan distribusi Linux yang digunakan dalam stack."
-
-msgid ""
-"Specify the architecture. For example, ``i386`` for a 32-bit architecture or "
-"``x86_64`` for a 64-bit architecture."
-msgstr ""
-"Tentukan arsitektur. Sebagai contoh, ``i386`` untuk 32-bit arsitektur atau "
-"``x86_64`` untuk 64-bit arsitektur."
-
-msgid "Specify the flavor for the instance."
-msgstr "Tentukan flavor instance."
-
-msgid "Specify the name of the database user."
-msgstr "Tentukan nama pengguna database."
-
-msgid "Specify the name of the database."
-msgstr "Tentukan nama database."
-
-msgid "Specify the name of the key pair to use to log in to the stack."
-msgstr ""
-"Tentukan nama pasangan kunci (key pair) digunakan untuk login ke stack."
-
-msgid ""
-"Specify the number of minutes that can elapse before the launch of the stack "
-"times out."
-msgstr ""
-"Tentukan jumlah menit yang dapat dilalui sebelum peluncuran stack habis "
-"waktu (times out)."
-
-msgid "Specify the password of the database."
-msgstr "Tentukan password dari database."
-
-msgid ""
-"Specify the password that the default user uses when the stack is created."
-msgstr ""
-"Tentukan password dimana user default menggunakan ketika stack (tumpukan) "
-"dibuat."
-
-msgid "Specify the root password for the database."
-msgstr "Tentukan password root untuk database."
-
-msgid "Specify the size of the instance to launch."
-msgstr "Tentukan ukuran instance untuk memulai."
-
-msgid ""
-"Specify this option to add resource metadata. The glance Metadata Catalog "
-"provides a list of metadata image definitions. (Note: Not all cloud "
-"providers enable this feature.)"
-msgstr ""
-"Tentukan pilihan ini untuk menambahkan metadata sumber daya. Glance "
-"Metadata Catalog menyediakan daftar definisi image metadata. (Catatan: "
-"Tidak semua cloud provider mengaktifkan fitur ini.)"
-
-msgid "Specify this option to copy image data to the Image service."
-msgstr "Tentukan pilihan ini untuk menyalin data image ke layanan Image."
-
-msgid "Start"
-msgstr "Start (memulai)"
-
-msgid "Start an instance (boot)"
-msgstr "Memulai instance (boot)"
-
-msgid "Start by getting the ID of the new ``guest2`` instance."
-msgstr "Mulai dengan mendapatkan ID yang baru instance ``guest2``."
-
-msgid "Static Web middleware through Object Storage"
-msgstr "Static Web middleware melalui Object Storage"
-
-msgid "Static large object"
-msgstr "Objek besar statis"
-
-msgid "Static large object manifest list"
-msgstr "Daftar manifest objek besar statis"
-
-msgid "Static large objects"
-msgstr "Static large objects (object besar statis)"
-
-msgid "Statistic"
-msgstr "Statistic (Statistik)"
-
-msgid "Stop"
-msgstr "Stop (berhenti)"
-
-msgid "Stop and start an instance"
-msgstr "Berhenti dan memulai sebuah instance"
-
-msgid "Store metadata on a configuration drive"
-msgstr "Menyimpan metadata pada drive konfigurasi."
-
-msgid "String name"
-msgstr "String name (nama string)"
-
-msgid "Style the file listing using a CSS."
-msgstr "Style (gaya) daftar file menggunakan CSS."
-
-msgid "Suspend"
-msgstr "Suspend (menangguhkan)"
-
-msgid "Suspend and resume an instance"
-msgstr "Menunda dan melanjutkan sebuah instance"
-
-msgid "System tab"
-msgstr "System tab"
-
-msgid ""
-"Take note of the unique router identifier returned, this will be required in "
-"subsequent steps."
-msgstr ""
-"Mencatat identifier router unik yang dikembalikan, ini akan diperlukan dalam "
-"langkah berikutnya."
-
-msgid "Task"
-msgstr "Tugas"
-
-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 ""
-"Telemetry mengukur sumber daya cloud di OpenStack. Ini mengumpulkan data "
-"terkait dengan penagihan. Saat ini, layanan metering ini tersedia melalui "
-"hanya baris perintah klien (command-line client) :command:`ceilometer` "
-
-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 ""
-"Memberitahu pengguna yang mengakses instance database now-disabled "
-"``guest1`` bahwa mereka sekarang dapat mengakses ``guest2``. Menyediakan "
-"mereka dengan nama ``guest2``, alamat IP, dan informasi lainnya yang mungkin "
-"mereka butuhkan. (Anda bisa mendapatkan informasi ini dengan menggunakan "
-"perintah :command:`trove show` )"
-
-msgid "Template"
-msgstr "Template"
-
-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 ""
-"**flavor** untuk instance Anda, yang mendefinisikan komputasi, memori, dan "
-"kapasitas penyimpanan dari instance komputasi nova. Rasa adalah konfigurasi "
-"hardware yang tersedia untuk server. Mendefinisikan ukuran server virtual "
-"yang dapat diluncurkan."
-
-msgid ""
-"The **instance source** can be an image, snapshot, or block storage volume "
-"that contains an image or snapshot."
-msgstr ""
-"**instance source** (sumber daya instance) bisa image, snapshot, atau volume "
-"penyimpanan blok yang berisi image atau snapshot."
-
-msgid ""
-"The 2``nn`` response code indicates a successful write. ``nn`` is a value "
-"from 00 to 99."
-msgstr ""
-"Kode respon 2``nn`` menunjukkan write (menulis) sukses. ``nn`` adalah nilai "
-"00-99."
-
-msgid ""
-"The :command:`ip` command is available only on Linux. Using :command:`ip "
-"netns` provides your environment a copy of the network stack with its own "
-"routes, firewall rules, and network devices for better troubleshooting."
-msgstr ""
-"Perintah :command:`ip` hanya tersedia di Linux. Penggunaan :command:`ip "
-"netns` menyediakan lingkungan Anda salinan network stack dengan rute "
-"sendiri, aturan firewall, dan perangkat jaringan untuk pemecahan masalah "
-"yang lebih baik."
-
-msgid ""
-"The :command:`openstack image save` command requires the image ID or the "
-"image name. Check there is sufficient space on the destination file system "
-"for the image file."
-msgstr ""
-"The :command:`openstack image save` command requires the image ID or the "
-"image name. Check there is sufficient space on the destination file system "
-"for the image file."
-
-msgid ""
-"The :command:`openstack server` command does not allow users to associate a "
-"floating IP address with a specific fixed IP address using the optional ``--"
-"fixed-address`` parameter, which legacy commands required as an argument."
-msgstr ""
-"Perintah :command:`openstack server` tidak mengizinkan pengguna untuk "
-"mengasosiasikan alamat IP mengambang dengan alamat IP tetap tertentu "
-"menggunakan opsional parameter ``--fixed-address``, dimana perintah legacy "
-"diperlukan sebagai argumen."
-
-msgid "The :guilabel:`Create An Image` dialog box appears."
-msgstr "Dialog box :guilabel:`Create An Image` akan muncul."
-
-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 ""
-"Dialog box :guilabel:`Create Pseudo-Folder in Container` ```` akan "
-"ditampilkan. ```` is nama kontainer dimana Anda sedang upload objek."
-
-msgid "The :guilabel:`Edit Object` dialog box is displayed."
-msgstr "Dialog box :guilabel:`Edit Object` akan ditampilkan."
-
-msgid ""
-"The :guilabel:`IP Address` field is filled automatically, but you can add a "
-"new IP address by clicking the :guilabel:`+` button."
-msgstr ""
-"Field (kolom) :guilabel:`IP Address` adalah diisi secara otomatis, tetapi "
-"Anda dapat menambahkan alamat IP baru dengan mengklik tombol :guilabel:`+`."
-
-msgid "The :guilabel:`Images` category shows the instance snapshot."
-msgstr "Kategori :guilabel:`Images` menunjukkan instance snapshot."
-
-msgid ""
-"The :guilabel:`Router Name` and :guilabel:`Router ID` fields are "
-"automatically updated."
-msgstr ""
-"Field (kolom) :guilabel:`Router Name` dan :guilabel:`Router ID` secara "
-"otomatis diperbarui."
-
-msgid "The :guilabel:`Update Stack Parameters` window appears."
-msgstr "Window :guilabel:`Update Stack Parameters` akan muncul."
-
-msgid ""
-"The :guilabel:`Upload File To Container: ` dialog box appears. "
-"```` is the name of the container to which you are uploading the "
-"object."
-msgstr ""
-"Muncul dialog box :guilabel:`Upload File To Container: `. ```` "
-"adalah nama dari kontainer dimana Anda sedang upload objek."
-
-msgid ""
-"The :guilabel:`Upload Object To Container`: ```` dialog box is "
-"displayed."
-msgstr ""
-"Dialog box :guilabel:`Upload Object To Container`: ```` akan "
-"ditampilkan."
-
-msgid "The CIDR of the subnet."
-msgstr "CIDR dari subnet."
-
-msgid "The Compute database registers the public key of the key pair."
-msgstr ""
-"Database Compute meregister kunci publik dari pasangan kunci (key pair)."
-
-msgid ""
-"The Dashboard lists the key pair on the :guilabel:`Access & Security` tab."
-msgstr ""
-"Dashboard mendaftar pasangan kunci (key pair) pada tab :guilabel:`Access & "
-"Security`."
-
-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 ""
-"Layanan Database menyediakan secara fungsionalitas cloud provisioning "
-"terukur (scalable) dan handal (reliable) untuk kedua mesin database "
-"relasional dan non-relasional. Pengguna dengan cepat dan mudah dapat "
-"menggunakan fitur database yang tanpa beban menangani tugas administrasi "
-"yang kompleks."
-
-msgid ""
-"The GNU tar format. Includes the long name, long link, and sparse extensions."
-msgstr ""
-"Format tar GNU. Termasuk nama panjang, hubungan yang panjang, dan ekstensi "
-"jarang."
-
-msgid "The ID of the source object."
-msgstr "ID dari objek sumber."
-
-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 ""
-"Alamat IP dikembalikan ke kolam alamat IP yang tersedia untuk semua proyek. "
-"Jika alamat IP masih berkaitan dengan instance menjalankan, maka secara "
-"otomatis memisahkan diri dari instance itu."
-
-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."
-"v2.images.ImageManager.find`` method:"
-msgstr ""
-"Image service Python bindings tidak mendukung pengambilan obyek image dengan "
-"nama. Namun, Compute Python bindings mengaktifkan Anda untuk mendapatkan "
-"sebuah objek image dengan nama. Untuk mendapatkan obyek image dengan nama, "
-"sebut (call) metode ``novaclient.v2.images.ImageManager.find``:"
-
-msgid ""
-"The MD5 checksum of the content of the segment object. This value must match "
-"the ``ETag`` of that object."
-msgstr ""
-"MD5 checksum dari isi dari objek segmen. Nilai ini harus sesuai dengan "
-"``ETag`` dari objek itu."
-
-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 ""
-"Objek Storage API menambahkan 32 karakter pertama dari nilai header "
-"permintaan (request) ``X-Trans-Id-Extra`` ke nilai ID transaksi di header "
-"respon ``X-Trans-Id`` yang dihasilkan. Anda harus UTF-8-encode dan kemudian "
-"URL-encode informasi transaksi tambahan sebelum Anda memasukkannya dalam "
-"header permintaan ``X-Trans-Id-Extra``."
-
-msgid ""
-"The Object Storage system extracts files from the archive file and creates "
-"an object."
-msgstr ""
-"Sistem Object Storage ekstrak file dari file arsip dan menciptakan sebuah "
-"objek."
-
-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 ""
-"Layanan OpenStack Networking menyediakan sistem scalable untuk mengelola "
-"konektivitas jaringan dalam pengerahan OpenStack cloud. Hal ini dapat dengan "
-"mudah dan cepat bereaksi terhadap perubahan kebutuhan jaringan (misalnya, "
-"menciptakan dan menetapkan alamat IP baru)."
-
-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 ""
-"Layanan Object Storage OpenStack menyediakan klien ``swift``, yang merupakan "
-"antarmuka baris perintah, command-line interface (CLI). Gunakan klien ini "
-"untuk daftar objek dan kontainer, upload objek untuk kontainer, dan download "
-"atau menghapus objek dari kontainer. Anda juga dapat mengumpulkan statistik "
-"dan memperbarui metadata piutang, kontainer, dan objek."
-
-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 ""
-"Layanan Orchestration memungkinkan Anda untuk mengatur beberapa aplikasi "
-"komposit cloud. Layanan ini mendukung penggunaan kedua Amazon Web Services "
-"(AWS) format template CloudFormation baik melalui API Query yang kompatibel "
-"dengan CloudFormation maupun OpenStack asli format :term:`Heat Orchestration "
-"Template (HOT)` melalui REST API."
-
-msgid "The POSIX.1-1988 Ustar format."
-msgstr "Format POSIX.1-1988 Ustar."
-
-msgid "The POSIX.1-2001 pax format."
-msgstr "Format pax POSIX.1-2001 "
-
-msgid "The Python script output looks something like this:"
-msgstr "Output script Python terlihat seperti ini:"
-
-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 ""
-"Static Web filter harus ditambahkan ke pipa (pipeline) di file Anda ``/etc/"
-"swift/proxy-server.conf`` di bawah setiap middleware otentikasi. Anda juga "
-"harus menambahkan bagian konfigurasi Web middleware statis."
-
-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."
-msgstr ""
-"`OpenStack Python Software Development Kit (SDK) `_ digunakan untuk menulis Python otomatisasi skrip yang "
-"membuat dan mengelola sumber daya di cloud OpenStack Anda. SDK "
-"mengimplementasikan Python binding ke API OpenStack, yang memungkinkan Anda "
-"untuk melakukan tugas otomatisasi di Python dengan membuat panggilan pada "
-"objek Python, daripada membuat panggilan REST langsung."
-
-msgid ""
-"The ``--parameter`` values that you specify depend on the parameters that "
-"are defined in the template. If a website hosts the template file, you can "
-"also specify the URL with the ``--template`` parameter."
-msgstr ""
-"Nilai ``--parameter`` dimana Anda tentukan tergantung pada parameter yang "
-"didefinisikan dalam template. Jika sebuah situs web menjadi host file "
-"template, Anda juga dapat menentukan URL dengan parameter ``--template``."
-
-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_ID`` dari cadangan parent (parent backup). Dalam hal ini, parent "
-"adalah backup secara teratur, dengan ID dari "
-"``6dc3a9b7-1f3e-4954-8582-3f2e4942cddd``"
-
-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 ""
-"Operasi ``COPY`` tidak membuat objek nyata. Untuk menduplikasi objek "
-"manifest, gunakan operasi ``GET`` untuk membaca nilai ``X-Object-Manifest`` "
-"dan menggunakan nilai ini dalam header request ``X-Object-Manifest`` dalam "
-"operasi ``PUT ``. Ini menciptakan objek manifest baru yang berbagi set "
-"(pengaturan) objek segmen yang sama sebagai objek manifest asli."
-
-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 ""
-" Header permintaan ``Content-Length`` harus berisi panjang konten JSON dan "
-"tidak panjang object segmen. Namun, setelah operasi ``PUT`` selesai, "
-"metadata ``Content-Length`` diatur untuk total panjang semua segmen objek. "
-"Situasi serupa berlaku untuk ``ETag``. Jika digunakan dalam operasi ``PUT``, "
-"itu harus berisi checksum MD5 dari konten JSON. Nilai metadata ``ETag`` "
-"kemudian diatur menjadi checksum MD5 dari nilai `` ETag`` bersambung "
-"(concatenated) dari segmen objek. Anda juga dapat mengatur header permintaan "
-"``Content-Type`` dan objek kustom metadata."
-
-msgid "The ``DELETE`` operation is supported for backwards compatibility."
-msgstr "Operasi ``DELETE`` didukung untuk kompatibilitas mundur."
-
-msgid ""
-"The ``INSTANCE_ID`` of the database instance you are doing the incremental "
-"backup for (in this example, ``792a6a56-278f-4a01-9997-d997fa126370``)"
-msgstr ""
-"``INSTANCE_ID`` dari name database Anda melakukan inkremental backup untuk "
-"(dalam contoh ini, ``792a6a56-278f-4a01-9997-d997fa126370``)"
-
-msgid ""
-"The ``Length Required (411)`` response code indicates that the request does "
-"not include a required ``Content-Length`` or ``Content-Type`` header."
-msgstr ""
-"Kode respon ``Length Required (411)`` menunjukkan bahwa permintaan tidak "
-"termasuk yang diperlukan header ``Content-Length`` atau ``Content-Type``."
-
-msgid ""
-"The ``SOURCE_VOLUME`` is the UUID or a name 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 ""
-"The ``SOURCE_VOLUME`` is the UUID or a name 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."
-
-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 ""
-"Kode respon ``Unprocessable Entity (422)`` menunjukkan bahwa checksum MD5 "
-"dari data ditulis ke sistem penyimpanan TIDAK cocok dengan nilai ETag "
-"opsional."
-
-msgid ""
-"The ``X-Delete-After`` header will be converted to ``X-Delete-At``. Verify "
-"the ``X-Delete-At`` header has posted to the object:"
-msgstr ""
-"Header ``X-Delete-After`` akan dikonversi ke ``X-Delete-At``. Lakukan "
-"verifikasi header ``X-Delete-At`` yang telah diposting ke objek:"
-
-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 ""
-"Nilai ``X-Object-Manifest`` adalah ``CONTAINER/PREFIX``, yang menunjukkan "
-"dimana objek segmen berada. Anda menyediakan header permintaan (request) ini "
-"dalam operasi ``PUT``."
-
-msgid "The ``myDB`` database."
-msgstr "Database ``myDB``."
-
-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:`openstack server create` command."
-msgstr ""
-"File ``openstack/2012-08-10/user_data``, ``openstack/latest/user_data``, "
-"``ec2/2009-04-04/user-data``, dan ``ec2/latest/user-data`` dihadirkan hanya "
-"jika flag ``--user-data`` dan isi dari file data pengguna dilewatkan ke "
-"perintah :command:`openstack server create`."
-
-msgid ""
-"The ``print_flavors`` method is defined in ``utils.py`` and prints the "
-"flavor details:"
-msgstr ""
-"Method ``print_flavors`` didefinisikan dalam ``utils.py`` dan mencetak "
-"rincian flavor:"
-
-msgid ""
-"The ``print_hosts`` method is defined in ``utils.py`` and prints the host "
-"object details:"
-msgstr ""
-"Metode ``print_hosts`` didefinisikan dalam ``utils.py`` dan mencetak rincian "
-"obyek host:"
-
-msgid ""
-"The ``print_values_ip`` method is defined in ``utils.py`` and prints the "
-"floating\\_ip object details:"
-msgstr ""
-"Metode ``print_values_ip`` didefinisikan dalam ``utils.py`` dan mencetak "
-"rincian objek floating\\_ip :"
-
-msgid ""
-"The ``subnet-create`` command has the following positional and optional "
-"parameters:"
-msgstr ""
-"Perintah ``subnet-create`` memiliki parameter posisi dan opsional berikut:"
-
-msgid "The ``userA`` user with the ``password`` password."
-msgstr "User ``userA`` dengan password ``password``."
-
-msgid ""
-"The above command creates the image ``myInstance`` by taking a snapshot of a "
-"running server."
-msgstr ""
-"The above command creates the image ``myInstance`` by taking a snapshot of a "
-"running server."
-
-msgid "The access is created."
-msgstr "Akses yang dibuat."
-
-msgid "The access is removed."
-msgstr "Akses akan dihapus."
-
-msgid "The access permission for the image. ``Public`` or ``Private``."
-msgstr "Izin akses untuk image. ``Public`` atau ``Private``."
-
-msgid ""
-"The actual device name might differ from the volume name because of "
-"hypervisor settings."
-msgstr ""
-"Nama perangkat yang sebenarnya mungkin berbeda dari nama volume karena "
-"pengaturan hypervisor."
-
-msgid ""
-"The administrative user has created an appropriate :ref:`flavor that meets "
-"the MongoDB minimum requirements `."
-msgstr ""
-"Pengguna administratif telah membuat flavour yang tepat :ref:`flavor that "
-"meets the MongoDB minimum requirements `."
-
-msgid ""
-"The administrative user has registered a MongoDB datastore type and version."
-msgstr ""
-"Pengguna administratif telah mendaftarkan tipe dan versi datastore MongoDB "
-
-msgid "The archive auto-extract feature supports these formats:"
-msgstr "Fitur auto-extract arsip mendukung format ini:"
-
-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 ""
-"*rules* terkait di setiap kontrol kelompok keamanan traffic ke instance "
-"dalam kelompok. Setiap traffic masuk yang tidak cocok dengan aturan ditolak "
-"akses secara default. Anda dapat menambahkan aturan atau menghapus aturan "
-"dari kelompok keamanan, dan Anda dapat memodifikasi aturan untuk default "
-"dan kelompok keamanan lainnya."
-
-msgid "The authentication token for Object Storage."
-msgstr "Otentikasi token untuk Object Storage."
-
-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 project clouds such as a high-"
-"performance computing cluster, or for deploying OpenStack itself."
-msgstr ""
-"Driver bare-metal untuk OpenStack Compute mengelola penyediaan perangkat "
-"keras fisik dengan menggunakan API cloud umum dan alat-alat seperti "
-"Orchestration (Heat). Kasus penggunaan untuk driver ini adalah untuk cloud "
-"proyek tunggal seperti cluster komputasi kinerja tinggi (high-performance), "
-"atau untuk menyebarkan (deploying) OpenStack sendiri."
-
-msgid ""
-"The body of the ``PUT`` request on the manifest object comprises a JSON list "
-"where each element contains these attributes:"
-msgstr ""
-"Body permintaan (request) ``PUT`` pada objek nyata terdiri dari daftar JSON "
-"dimana setiap elemen mengandung atribut ini:"
-
-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 ""
-"ID kluster akan tampil ketika Anda pertama kali membuat cluster. (Jika Anda "
-"perlu menemukan nanti, gunakan perintah :command:`trove cluster-list` untuk "
-"daftar nama dan ID semua kluster dalam sistem Anda.)"
-
-msgid "The command does not notify that your server was deleted."
-msgstr "Perintah tidak memberitahukan bahwa server Anda telah dihapus."
-
-msgid "The command returns a URL from which you can access your instance:"
-msgstr ""
-"Perintah mengembalikan URL dari mana Anda dapat mengakses instance Anda:"
-
-msgid "The command returns the following output:"
-msgstr "Perintah mengembalikan output sebagai berikut:"
-
-msgid ""
-"The container and object name in the format: ``CONTAINER_NAME/OBJECT_NAME``."
-msgstr ""
-"Wadah (container) dan objek nama dalam format: ``CONTAINER_NAME/"
-"OBJECT_NAME``."
-
-msgid "The dashboard is generally installed on the controller node."
-msgstr "Dashboard yang umumnya dipasang pada controller node."
-
-msgid ""
-"The dashboard shows the instance to which the volume is now attached and the "
-"device name."
-msgstr ""
-"Dashboard menunjukkan instance dimana volume terhubung sekarang dan nama "
-"perangkat."
-
-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 menunjukkan instance dengan nama, alamat IP pribadi dan "
-"mengambang, ukuran, status, tugas, kondisi daya, dan sebagainya."
-
-msgid "The dashboard shows the network on the :guilabel:`Networks` tab."
-msgstr "Dashboard menunjukkan jaringan pada tab :guilabel:`Networks`."
-
-msgid "The dashboard shows the new volume snapshot in Volume Snapshots tab."
-msgstr ""
-"Dashboard menunjukkan snapshot volume yang baru di tab Volume Snapshots."
-
-msgid ""
-"The dashboard shows the security service on the :guilabel:`Security "
-"Services` tab."
-msgstr ""
-"Dashboard menunjukkan layanan keamanan di tab :guilabel:`Security Services`."
-
-msgid ""
-"The dashboard shows the share network on the :guilabel:`Share Networks` tab."
-msgstr ""
-"Dashboard menunjukkan jaringan berbagi (share) pada tab :guilabel:`Share "
-"Networks`."
-
-msgid "The dashboard shows the share on the :guilabel:`Shares` tab."
-msgstr "Dashboard menunjukkan berbagi (share) pada tab :guilabel:`Shares`."
-
-msgid "The dashboard shows the volume on the :guilabel:`Volumes` tab."
-msgstr "Dashboard menunjukkan volume pada tab :guilabel:`Volumes`."
-
-msgid ""
-"The database is based on the ``mysql`` data store and the ``mysql-5.5`` "
-"datastore\\_version."
-msgstr ""
-"Database didasarkan pada data store ``mysql`` dan datastore\\_version "
-"``mysql-5.5`` ."
-
-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 ""
-"Format default dari drive konfigurasi sebagai sistem file ISO 9660. Secara "
-"eksplisit menentukan format ISO 9660, tambahkan baris berikut ke file ``/etc/"
-"nova/nova.conf``:"
-
-msgid "The deleted instance does not appear in the list."
-msgstr "Instance dihapus tidak muncul dalam daftar."
-
-msgid ""
-"The environment variables have been around the longest and are the form you "
-"are most likely to receive from your cloud provider. If you have one and "
-"only one cloud account, they are the most convenient way."
-msgstr ""
-"Variabel lingkungan telah berada lama di sekitar dan merupakan bentuk dimana "
-"Anda paling mungkin untuk menerima dari penyedia cloud Anda. Jika Anda "
-"memiliki satu dan hanya satu akun cloud, mereka adalah cara yang paling "
-"nyaman."
-
-msgid "The events related to the stack."
-msgstr "Kejadian yang berhubungan dengan stack."
-
-msgid ""
-"The examples in this guide show you how to perform tasks by using the "
-"following methods:"
-msgstr ""
-"Contoh dalam buku ini menunjukkan cara untuk melakukan tugas dengan "
-"menggunakan metode berikut:"
-
-msgid "The examples in this section use the ``get_credentials`` method:"
-msgstr "Contoh pada bagian ini menggunakan metode ``get_credentials``:"
-
-msgid "The examples in this section use the ``get_nova_credentials`` method:"
-msgstr "Contoh pada bagian ini menggunakan metode ``get_nova_credentials`` "
-
-msgid ""
-"The examples in this section use the ``print_values`` and "
-"``print_values_server`` methods:"
-msgstr ""
-"Contoh pada bagian ini menggunakan metode ``print_values`` dan "
-"``print_values_server```:"
-
-msgid ""
-"The files that appear on the configuration drive depend on the arguments "
-"that you pass to the :command:`openstack server create` command."
-msgstr ""
-"File-file yang muncul pada drive konfigurasi tergantung pada argumen dimana "
-"Anda melewatkan ke perintah :command:`openstack server create`."
-
-msgid ""
-"The first step is to list flavors by using the :command:`openstack flavor "
-"list` command."
-msgstr ""
-"Langkah pertama adalah mendaftar flavor dengan menggunakan perintah :"
-"command:`openstack flavor list`."
-
-msgid ""
-"The flavor defines the maximum swap and ephemeral disk size. You cannot "
-"exceed these maximum values."
-msgstr ""
-"Flavor mendefinisikan swap maksimum dan ukuran disk ephemeral (tidal kekal). "
-"Anda tidak dapat melebihi nilai-nilai maksimum."
-
-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 ""
-"Flavor dipilih berdasarkan ukuran image yang dipilih untuk meluncurkan "
-"sebuah instance. Misalnya, saat membuat image, jika Anda memasukkan nilai "
-"dalam field (kolom) :guilabel:`Minimum RAM (MB)` misalnya 2048, kemudian "
-"pada memilih image, flavor default adalah ``m1.small``."
-
-msgid "The following are examples of `read` ACLs for containers:"
-msgstr "Berikut ini adalah contoh dari ACL `read` untuk kontainer:"
-
-msgid "The following are examples of `write` ACLs for containers:"
-msgstr "Berikut ini adalah contoh dari ACL `write` untuk kontainer:"
-
-msgid ""
-"The following auto-extract archive files example shows a ``text/plain`` "
-"response body where no failures occurred:"
-msgstr ""
-"Berikut auto-extract file arsip contoh menunjukkan response body ``text/"
-"plain`` dimana ada kegagalan terjadi:"
-
-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 ""
-"Berikut contoh file arsip auto-extract menunjukkan respon ``text/plain`` "
-"dimana beberapa kegagalan terjadi. Dalam contoh ini, sistem Object Storage "
-"dikonfigurasi untuk menolak karakter string tertentu sehingga terjadi 400 "
-"Bad Request error untuk setiap objek yang menggunakan string dibatasi."
-
-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 ""
-"Berikut respon penghapusan massal berbentuk format ``application/xml``. "
-"Dalam contoh ini, wadah (container) ``mycontainer`` tidak kosong, sehingga "
-"tidak dapat dihapus."
-
-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 ""
-"Perintah berikut meluncurkan instance ``MyCirrosServer`` dengan ``m1.small`` "
-"flavor (ID of ``1``), ``cirros-0.3.2-x86_64-uec`` image (ID of ``397e713c-"
-"b95b-4186-ad46-6126863ea0a9``), ``default`` security group, key "
-"``KeyPair01``, dan file data pengguna yang disebut ``cloudinit.file``:"
-
-msgid "The following commands can be used to manage bare-metal nodes."
-msgstr "Perintah berikut dapat digunakan untuk mengelola node bare-metal."
-
-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 ""
-"Contoh berikut memungkinkan drive konfigurasi dan melewati data pengguna, "
-"dua file, dan dua kunci/nilai metadata pasangan (key/value metadata pair), "
-"yang semuanya dapat diakses dari drive konfigurasi:"
-
-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 ""
-"Contoh berikut menunjukkan perintah dan hasil dari pembuatan node dengan "
-"alamat PM ``1.2.3.4``, PM nama pengguna IPMI, dan password ``ipmi``."
-
-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 ""
-"Contoh berikut menunjukkan isi dari file ``ec2/2009-04-04/meta-data.json`` "
-"dan ``ec2/latest/meta-data.json``. File ini adalah identik. Isi file "
-"diformat agar lebih mudah dibaca."
-
-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 ""
-"Contoh berikut menunjukkan isi dari file ``openstack/2012-08-10/meta_data."
-"json`` dan ``openstack/latest/meta_data.json``. File ini adalah identik. "
-"Isi file diformat supaya dapat dibaca."
-
-msgid ""
-"The following example shows the failure response in ``application/json`` "
-"format."
-msgstr ""
-"Contoh berikut menunjukkan respon kegagalan dalam format ``application/"
-"json``."
-
-msgid "The following example shows the results of a search on ``10.0.0.4``."
-msgstr "Contoh berikut menunjukkan hasil pencarian di ``10.0.0.4``."
-
-msgid ""
-"The following hypervisors support the configuration drive: libvirt, "
-"XenServer, Hyper-V, and VMware."
-msgstr ""
-"Hypervisors berikut mendukung drive konfigurasi: libvirt, XenServer, Hyper-"
-"V, dan VMware."
-
-msgid "The following program creates a network:"
-msgstr "Program berikut membuat jaringan:"
-
-msgid "The following program creates a port:"
-msgstr "Program berikut membuat port:"
-
-msgid ""
-"The following program creates a server (VM) by using the Compute API v2."
-msgstr "Program berikut membuat server (VM) dengan menggunakan Compute API v2."
-
-msgid ""
-"The following program deletes a server (VM) by using the Compute API v2."
-msgstr ""
-"Program berikut menghapus server (VM) dengan menggunakan Compute API v2."
-
-msgid ""
-"The following program lists flavors and their details by using the Compute "
-"API v2."
-msgstr ""
-"Program berikut daftar flavor dan rincian mereka dengan menggunakan Compute "
-"API v2."
-
-msgid "The following program lists networks:"
-msgstr "Program berikut daftar jaringan:"
-
-msgid "The following program lists ports:"
-msgstr "Program berikut daftar port:"
-
-msgid "The following program lists servers by using the Compute API v2."
-msgstr "Program berikut ini berisi server dengan menggunakan Compute API v2."
-
-msgid ""
-"The following program lists the floating IPs and their details by using the "
-"Compute API v2."
-msgstr ""
-"Program berikut daftar IP mengambang dan rincian mereka dengan menggunakan "
-"Compute API v2."
-
-msgid "The following program lists the hosts by using the Compute API v2."
-msgstr "Program berikut berisi host dengan menggunakan Compute API v2."
-
-msgid "The following program lists the ports for a server:"
-msgstr "Program berikut berisi port untuk server:"
-
-msgid ""
-"The following program updates the name of a server (VM) by using the Compute "
-"API v2."
-msgstr ""
-"Program berikut men-update nama server (VM) dengan menggunakan Compute API "
-"v2."
-
-msgid ""
-"The following sections show how to use Static Web middleware through Object "
-"Storage."
-msgstr ""
-"Bagian berikut menunjukkan bagaimana menggunakan Static Web middleware "
-"melalui Object Storage."
-
-msgid ""
-"The image is queued to be uploaded. It might take some time before the "
-"status changes from Queued to Active."
-msgstr ""
-"Image diantrikan (queued) untuk di-upload. Mungkin butuh beberapa waktu "
-"sebelum perubahan statusnya dari Antri ke Aktif (Queued to Active)."
-
-msgid ""
-"The images method returns a Python generator, as shown in the following "
-"interaction with the Python interpreter:"
-msgstr ""
-"Image metode akan mengembalikan generator Python, seperti yang ditunjukkan "
-"dalam interaksi berikut dengan interpreter Python:"
-
-msgid "The instance is now associated with two IP addresses:"
-msgstr "Instance sekarang terkait dengan dua alamat IP:"
-
-msgid "The instance starts on a compute node in the cloud."
-msgstr "Instance dimulai pada node komputasi di cloud."
-
-msgid ""
-"The instances launched using this image contain the system that you have "
-"just installed using the ISO image."
-msgstr ""
-"Instance diluncurkan menggunakan image ini berisi sistem yang Anda baru saja "
-"menginstal menggunakan image ISO."
-
-msgid "The list shows all the instances with their fixed IP addresses."
-msgstr "Daftar menunjukkan semua Instance dengan alamat IP tetap nya."
-
-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 ""
-"Daftar ini menunjukkan ID, nama, status, dan alamat IP private (dan jika "
-"ditugaskan, publik) untuk semua instance dalam proyek yang Anda milik:"
-
-msgid ""
-"The load balancer occupies a neutron network port and has an IP address "
-"assigned from a subnet."
-msgstr ""
-"Penyeimbang beban (load balancer) menempati port jaringan neutron dan "
-"memiliki alamat IP yang ditetapkan dari subnet."
-
-msgid ""
-"The manifest list includes the container name of each object. Segment "
-"objects can be in different containers."
-msgstr ""
-"Daftar manifest mencakup nama wadah (container) setiap objek. Object segmen "
-"dapat dalam wadah yang berbeda."
-
-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 ""
-"Isi objek manifest adalah sebuah ordered list nama object segmen dalam "
-"format JSON. Lihat :ref: `static_large_objects`."
-
-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 ""
-"Objek manifest tidak memiliki konten tetapi memiliki metadata header ``X-"
-"Object-Manifest`` . Nilai dari header ini adalah ``CONTAINER/PREFIX``, "
-"dimana ``CONTAINER`` adalah nama dari kontainer dimana objek segmen "
-"disimpan, dan ``PREFIX`` adalah string bahwa semua object segmen memiliki "
-"kesamaan. Lihat :ref: `dynamic_large_objects`."
-
-msgid ""
-"The module created here is a demo module called ping. It is the basic type "
-"made for testing purposes. To create it, it is as simple as the following :"
-"command: ``echo`` command:"
-msgstr ""
-"Modul yang dibuat disini adalah modul demo yang disebut ping. Ini adalah "
-"jenis dasar yang dibuat untuk tujuan pengujian. Untuk membuatnya, "
-"sesederhana yang berikut perintah :command: ``echo``:"
-
-msgid "The name and version of the datastore you want to use."
-msgstr "Nama dan versi dari datastore yang ingin Anda gunakan."
-
-msgid "The name of the cluster."
-msgstr "Nama kluster."
-
-msgid "The name of the incremental backup you are creating: ``backup1.1``"
-msgstr "Nama inkremental backup Anda membuat: ``backup1.1``"
-
-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 ""
-"Nama inkremental backup kedua adalah ``backup1.2``. Kali ini, ketika Anda "
-"menentukan parent, lulus dalam ID dari inkremental backup yang baru saja "
-"dibuat pada langkah sebelumnya (``backup1.1``). Dalam contoh ini, itu adalah "
-"``1d474981-a006-4f62-b25f-43d7b8a7097e``."
-
-msgid "The name or ID of the network to which the subnet belongs."
-msgstr "Nama atau ID dari jaringan yang subnet kepemilikan (subnet belongs)."
-
-msgid ""
-"The name you assign here becomes the initial host name of the server. If the "
-"name is longer than 63 characters, the Compute service truncates it "
-"automatically to ensure dnsmasq works correctly."
-msgstr ""
-"Nama dimana Anda menetapkan disini menjadi nama host server awal. Jika nama "
-"lebih panjang dari 63 karakter, layanan Compute memotong secara otomatis "
-"untuk memastikan dnsmasq bekerja dengan benar."
-
-msgid "The new instance appears in the database instances list."
-msgstr "Instance baru muncul dalam daftar instance database."
-
-msgid "The new port is now displayed in the :guilabel:`Ports` list."
-msgstr "Port baru tidak ditampilkan dalam daftar :guilabel:`Ports`."
-
-msgid "The new router is now displayed in the :guilabel:`Routers` tab."
-msgstr "Router baru sekarang ditampilkan dalam tab :guilabel:`Routers`."
-
-msgid "The number of files actually deleted."
-msgstr "Jumlah file benar-benar dihapus."
-
-msgid "The number of not found objects."
-msgstr "Jumlah objek tidak ditemukan."
-
-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 ""
-"Objek memiliki ``X-Static-Large-Object`` diatur untuk ``true``. Anda tidak "
-"menetapkan metadata ini secara langsung. Sebaliknya, sistem mengatur itu "
-"ketika Anda ``PUT`` objek manifest statis."
-
-msgid ""
-"The original :command: ``count`` command will show the first instance, "
-"unless the ``--include_clustered`` option is used. You can see the MD5 from "
-"each applied module, and you know that the single instance one is not "
-"current."
-msgstr ""
-"Perintah :command: ``count`` asli akan menunjukkan instance pertama, kecuali "
-"opsi ``--include_clustered`` digunakan. Anda dapat melihat MD5 dari masing-"
-"masing modul yang diterapkan, dan Anda tahu bahwa instance tunggal tidak "
-"mutakhir."
-
-msgid "The parameters and details of the stack."
-msgstr "Parameter dan rincian dari stack."
-
-msgid "The parameters are:"
-msgstr "Parameter adalah:"
-
-msgid ""
-"The path is the account, such as ``/v1/12345678912345``, that contains the "
-"objects and containers."
-msgstr ""
-"Path adalah account, seperti ``/v1/12345678912345``, yang berisi objek dan "
-"kontainer."
-
-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 ""
-"Path yang Anda tentukan dalam permintaan ``PUT`` digunakan untuk lokasi "
-"objek dan awalan (prefix) untuk nama objek yang dihasilkan."
-
-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 ""
-"URL publik yang merupakan endpoint HTTP dari tempat Anda dapat mengakses "
-"Object Storage. Ini mencakup Object Storage nomor versi API dan nama akun "
-"Anda. Misalnya, ``https://23.253.72.207/v1/my_account``."
-
-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 ""
-"Contoh selanjutnya di buku ini menggunakan standar, tanggapan non-serial. "
-"Namun, semua request (permintaan) ``GET`` yang melakukan operasi "
-"pendaftaran menerima parameter kueri ``format`` atau header permintaan `` "
-"Accept``."
-
-msgid "The resources used by the stack."
-msgstr "Sumber daya yang digunakan oleh stack."
-
-msgid "The response body contains the following information:"
-msgstr "Response body berisi informasi berikut:"
-
-msgid "The server status becomes ACTIVE."
-msgstr "Status server menjadi ACTIVE."
-
-msgid "The share is being deleted."
-msgstr "Share sedang dihapus."
-
-msgid "The size (flavor) of the server is ``m1.small (2)``."
-msgstr "Ukuran (flavor) dari server ``m1.small (2) ``."
-
-msgid ""
-"The size of the segment object. This value must match the ``Content-Length`` "
-"of that object."
-msgstr ""
-"Ukuran dari objek segmen. Nilai ini harus sesuai dengan ``Content-Length`` "
-"dari objek itu."
-
-msgid "The snapshot is deleted."
-msgstr "Snapshot akan dihapus."
-
-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 ""
-"String ``$OS_IMAGE_URL`` dan ``$OS_AUTH_TOKEN`` mewakili variabel "
-"didefinisikan dalam lingkungan klien. ``$OS_IMAGE_URL`` adalah path lengkap "
-"ke layanan endpoint image Anda, misalnya, ```http://example.com``. ``"
-"$OS_AUTH_TOKEN`` merupakan token otentikasi yang dihasilkan oleh Identity "
-"Service, misalnya, ``6583fb17c27b48b4b4a6033fe9cc0fe0``."
-
-msgid "The subnet name, which is optional."
-msgstr "Nama subnet, yang opsional."
-
-msgid ""
-"The system returns status code 2xx (between 200 and 299, inclusive) and the "
-"objects and pseudo-directories within the nested pseudo-directory."
-msgstr ""
-"Sistem ini mengembalikan kode status 2xx (antara 200 dan 299, inklusif) dan "
-"objek dan pseudo-directory dalam pseudo-directory bersarang."
-
-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 ""
-"Sistem ini mengembalikan kode status 2xx (antara 200 dan 299, inklusif) dan "
-"objek dan pseudo-directory dalam pseudo-directory tingkat atas."
-
-msgid ""
-"The system returns status code 2xx (between 200 and 299, inclusive) and the "
-"requested list of the objects."
-msgstr ""
-"Sistem ini mengembalikan kode status 2xx (antara 200 dan 299, inklusif) dan "
-"daftar yang diminta dari objek."
-
-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 ""
-"Sistem ini mengembalikan kode status 2xx (antara 200 dan 299, inklusif) dan "
-"objek yang cocok dengan yang diminta. Karena Anda menggunakan garis miring, "
-"hanya menampilkan pseudo-directory ``photos/``. Nilai yang kembali dari "
-"query ``delimiter`` slash bukan obyek nyata. Nilai tersebut akan merujuk ke "
-"objek nyata jika tidak diakhiri dengan garis miring (slash). Pseudo-"
-"directory tidak memiliki content-type, bukan, setiap pseudo-directory "
-"memiliki entri ``subdir`` sendiri di respon hasil JSON dan XML. Sebagai "
-"contoh:"
-
-msgid "The template for the stack."
-msgstr "Template untuk stack."
-
-msgid ""
-"The template languages are described in the `Template Guide `_ in the `Heat "
-"developer documentation `_."
-msgstr ""
-"Bahasa template dijelaskan dalam `Template Guide `_ dalam `Heat developer "
-"documentation `_."
-
-msgid ""
-"The template languages are described in the `Template Guide `__ in the `Heat "
-"developer documentation `__."
-msgstr ""
-"Bahasa template dijelaskan dalam `Template Guide `__ dalam `Heat developer "
-"documentation `__."
-
-msgid ""
-"The three instances you want to include in the replication set for the first "
-"shard. Specify each instance by using the ``--instance`` argument and the "
-"associated flavor ID and volume size. Use the same flavor ID and volume size "
-"for each instance. In this example, flavor ``7`` is a custom flavor that "
-"meets the MongoDB minimum requirements."
-msgstr ""
-"Tiga instance yang ingin Anda sertakan dalam replikasi ditetapkan untuk "
-"pecahan pertama (first shard). Tentukan setiap instance dengan menggunakan "
-"argumen ``--instance`` dan ID flavor dan volume ukuran terkait. Gunakan ID "
-"flavor dan ukuran volume yang sama untuk setiap instance. Dalam contoh ini, "
-"flavor ``7`` adalah flavor kustom yang memenuhi persyaratan minimum MongoDB."
-
-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 ""
-"Nilai timeout dapat diganti pada basis per image dengan cara "
-"``os_shutdown_timeout`` yang merupakan pengaturan metadata image "
-"memungkinkan berbagai jenis sistem operasi untuk menentukan berapa banyak "
-"waktu yang mereka butuhkan untuk menutup (shut down) rapi."
-
-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 ""
-"Bagian atas jendela menampilkan nama pengguna. Anda juga dapat mengakses "
-"tab :guilabel:`Settings` (:ref:`dashboard-settings-tab`) atau keluar dari "
-"dashboard."
-
-msgid "The topology of the stack."
-msgstr "Topologi dari stack."
-
-msgid "The user name is ``ubuntu`` for the Ubuntu cloud images on TryStack."
-msgstr "Username adalah ``ubuntu`` untuk image cloud Ubuntu di TryStack."
-
-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 ""
-"Tab dan fungsi terlihat di dashboard tergantung pada hak akses, atau peran, "
-"pengguna dimana Anda login sebagai apa."
-
-msgid ""
-"There are three remote console access methods commonly used with OpenStack:"
-msgstr ""
-"Ada tiga metode akses remote konsol umumnya digunakan dengan OpenStack:"
-
-msgid ""
-"There are two basic ways to deal with your cloud config and credentials:"
-msgstr "Ada dua cara dasar untuk menangani konfigurasi cloud dan kredensial:"
-
-msgid ""
-"These commands assume the implementation of the v2 Image 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 ""
-"Perintah ini beranggapan pelaksanaan v2 Image API menggunakan Layanan "
-"Identity untuk otentikasi dan otorisasi. Header X-Auth-Token digunakan untuk "
-"menyediakan token otentikasi yang dikeluarkan oleh Identity Service."
-
-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 ""
-"Bahasa template fleksibel ini memungkinkan pengembang aplikasi untuk "
-"menggambarkan (describe) dan mengotomatisasi pengerahan (deployment) "
-"infrastruktur, layanan, dan aplikasi. Template memungkinkan pembuatan "
-"sebagian besar tipe sumber daya OpenStack, seperti instance, alamat IP "
-"mengambang, volume, kelompok keamanan, dan pengguna. Setelah dibuat, sumber "
-"daya ini diacu sebagai tumpukan (stack)."
-
-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 ""
-"Bahasa template fleksibel ini memungkinkan pengembang aplikasi untuk "
-"menggambarkan dan mengotomatisasi penyebaran (deployment) infrastruktur, "
-"layanan, dan aplikasi. Template memungkinkan penciptaan sebagian besar jenis "
-"sumber daya OpenStack, seperti instance, alamat IP mengambang, volume, "
-"kelompok keamanan, dan pengguna. Sumber daya, yang telah diciptakan, yang "
-"disebut sebagai tumpukan (stack)."
-
-msgid "These non-current versions are named as follows:"
-msgstr "Versi non-current ini diberi nama sebagai berikut:"
-
-msgid "This allows access to all codes and all types of ICMP traffic."
-msgstr ""
-"Hal ini Mengizinkan akses ke semua kode dan semua jenis lalu lintas ICMP."
-
-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 ""
-"Buku ini ditulis untuk siapa saja yang menggunakan mesin virtual dan sumber "
-"daya cloud untuk mengembangkan perangkat lunak atau melakukan penelitian. "
-"Anda harus memiliki pengalaman bertahun-tahun dengan set alat berbasis Linux "
-"dan nyaman menggunakan kedua GUI dan alat berbasis CLI. Meskipun buku ini "
-"mencakup beberapa informasi tentang menggunakan Python untuk membuat dan "
-"mengelola sumber daya cloud, Python pengetahuan bukanlah prasyarat untuk "
-"membaca buku ini."
-
-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 ""
-"Klien ini didasarkan pada perpustakaan klien cepat asli, (native swift "
-"client library) ``client.py``, yang secara mulus mengotentikasi kembali (re-"
-"authenticates) jika token saat ini berakhir selama pemrosesan, mencoba ulang "
-"operasi beberapa kali, dan menyediakan pengolahan konkurensi dari 10."
-
-msgid ""
-"This code resides in the ``credentials.py`` file, which all samples import."
-msgstr "Kode ini berada di file ``credentials.py``, yang semua sampel impor."
-
-msgid "This code resides in the ``utils.py`` file, which all samples import."
-msgstr "Kode ini berada di file ``utils.py``, yang semua sampel impor."
-
-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 ""
-"Perintah ini menghasilkan pasangan kunci (key pair) dengan nama yang Anda "
-"tentukan untuk KEY\\_NAME, menulis kunci pribadi (private key) ke file ``."
-"pem`` yang Anda tentukan, dan register kunci publik (public key) ke database "
-"Nova."
-
-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 ""
-"Perintah ini me-register kunci publik di Nova database dan nama kunci "
-"pasangan nama yang Anda tentukan untuk ``KEY_NAME``."
-
-msgid "This command returns the IP address of the database instance."
-msgstr "Perintah ini mengembalikan alamat IP dari instance database."
-
-msgid "This command returns the instance ID of your new instance."
-msgstr "Perintah ini mengembalikan instance ID dari instance baru Anda."
-
-msgid ""
-"This command stores the state of the VM in RAM. A paused instance continues "
-"to run in a frozen state."
-msgstr ""
-"Perintah ini menyimpan keadaan VM di RAM. Sebuah instance yang dijeda terus "
-"berjalan dalam keadaan beku."
-
-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 ""
-"Sintaks perintah ini berkaitan hanya dengan python-troveclient versi 1.0.6 "
-"dan kemudian. versi sebelumnya mengharuskan Anda untuk lulus dalam nama "
-"backup sebagai argumen pertama."
-
-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 ""
-"Sintaks perintah ini berkaitan hanya dengan python-troveclient versi 1.0.6 "
-"dan kemudian. Versi sebelumnya mengharuskan Anda untuk melewatkan dalam ID "
-"kelompok konfigurasi sebagai argumen pertama."
-
-msgid ""
-"This example assigns the file origin to the ``Origin`` header, which ensures "
-"that the file originated from a reputable source."
-msgstr ""
-"Contoh ini menetapkan asal muasal file ke header ``Origin``, yang menjamin "
-"bahwa file berasal dari sumber yang memiliki reputasi."
-
-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 ""
-"Contoh ini mengasumsikan Anda telah membuat database MySQL dan menunjukkan "
-"cara menggunakan kelompok konfigurasi untuk mengkonfigurasinya. Meskipun "
-"contoh ini menetapkan hanya satu pilihan pada satu database, Anda dapat "
-"menggunakan prosedur yang sama untuk mengatur beberapa pilihan di beberapa "
-"instance database seluruh lingkungan Anda. Hal ini dapat memberikan "
-"penghematan waktu yang signifikan dalam mengelola cloud Anda."
-
-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 ""
-"Contoh ini membuat kelompok konfigurasi yang disebut ``group1``. ``group1`` "
-"hanya mengandung satu pasangan kunci dan nilai, dan pasangan ini menetapkan "
-"opsi ``sync_binlog`` ke ``1``."
-
-msgid ""
-"This example creates a database instance with the following characteristics:"
-msgstr ""
-"Contoh ini menciptakan instance database dengan karakteristik sebagai "
-"berikut:"
-
-msgid ""
-"This example queries OpenStack Networking to create a router and add a port "
-"to a subnet."
-msgstr ""
-"Contoh ini melakukan kueri OpenStack Networking untuk membuat sebuah router "
-"dan menambahkan port untuk subnet."
-
-msgid "This example queries OpenStack Networking to delete a network."
-msgstr ""
-"Contoh ini melakukan kueri OpenStack Networking untuk menghapus jaringan."
-
-msgid "This example queries OpenStack Networking to list all routers."
-msgstr ""
-"Contoh ini melakukan kueri OpenStack Networking untuk daftar semua router."
-
-msgid "This example queries OpenStack Networking to list security groups."
-msgstr ""
-"Contoh ini melakukan kueri OpenStack Networking untuk daftar kelompok "
-"keamanan."
-
-msgid "This example queries OpenStack Networking to list subnets."
-msgstr "Contoh ini melakukan kueri OpenStack Networking untuk daftar subnet."
-
-msgid "This example shows a truncated response body:"
-msgstr ""
-"Contoh ini menunjukkan respon tubuh terpotong (truncated response body) :"
-
-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 ""
-"Contoh ini menunjukkan tiga objek segmen. Anda dapat menggunakan beberapa "
-"kontainer dan nama objek tidak harus sesuai dengan pola tertentu, berbeda "
-"dengan object besar yang dinamis."
-
-msgid "This example shows you how to back up and restore a MySQL database."
-msgstr ""
-"Contoh ini menunjukkan Anda bagaimana untuk backup dan restore database "
-"MySQL."
-
-msgid "This example shows you how to create and access a MySQL 5.5 database."
-msgstr ""
-"Contoh ini menunjukkan Anda bagaimana membuat dan mengakses database MySQL "
-"5.5 ."
-
-msgid ""
-"This example shows you how to create and apply modules to a MySQL 5.6 "
-"database and redis 3.2.6 database cluster."
-msgstr ""
-"Contoh ini menunjukkan cara membuat dan menerapkan modul ke database MySQL "
-"5.6 dan cluster database redis 3.2.6."
-
-msgid "This example shows you how to replicate a MySQL database instance."
-msgstr ""
-"Contoh ini menunjukkan Anda bagaimana meniru (replicate) instance database "
-"MySQL."
-
-msgid "This example shows you how to set up a MongoDB sharded cluster."
-msgstr ""
-"Contoh ini menunjukkan Anda bagaimana membuat sebuah kluster sharded MongoDB."
-
-msgid ""
-"This example shows you how to use incremental backups with a MySQL database."
-msgstr ""
-"Contoh ini menunjukkan kepada Anda bagaimana menggunakan inkremental backup "
-"(cadangan) dengan database MySQL."
-
-msgid ""
-"This example uses the :command:`openstack` client to create an auto-scaling "
-"stack and the :command:`ceilometer` client to measure resources."
-msgstr ""
-"Contoh ini menggunakan klien :command:`openstack` untuk membuat tumpukan "
-"auto-skala dan klien :command:`ceilometer` untuk mengukur sumber daya "
-"(resources)."
-
-msgid "This example uses the ``get_nova_credentials_v2`` method:"
-msgstr "Contoh ini menggunakan method ``get_nova_credentials_v2``:"
-
-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 ""
-"Perubahan field (kolom) ini berdasarkan pilihan Anda sebelumnya. Jika Anda "
-"telah memilih untuk memulai sebuah instance menggunakan snapshot, field "
-"menampilkan :guilabel:`Instance Snapshot` . Pilih nama snapshot dari daftar "
-"dropdown."
-
-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 ""
-"Perubahan field (kolom) ini berdasarkan pilihan Anda sebelumnya. Jika Anda "
-"telah memilih untuk memulai sebuah instance menggunakan volume, field "
-"menampilkan :guilabel:`Volume` . Pilih nama volume dari daftar dropdown. "
-"Jika Anda ingin menghapus volume pada penghapusan instance, periksa opsi :"
-"guilabel:`Delete Volume on Instance Delete`."
-
-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 ""
-"Perubahan filed (kolom) ini berdasarkan pilihan Anda sebelumnya. Jika Anda "
-"telah memilih untuk memulai sebuah instance menggunakan image, field "
-"menampilkan :guilabel:`Image Name` . Pilih nama image dari daftar dropdown."
-
-msgid "This guide documents OpenStack Ocata, Newton and Mitaka releases."
-msgstr ""
-"Panduan ini mendokumentasikan OpenStack rilis Ocata, Newton and Mitaka."
-
-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 ""
-"Versi terbaru berikutnya (next-most) ini membawa dengan semua set terakhir "
-"metadata. Jika Anda ingin benar-benar menghapus objek dan Anda memiliki lima "
-"versi itu, Anda harus ``DELETE`` lima kali."
-
-msgid ""
-"This output shows that the Object Storage system has enabled the static "
-"website and temporary URL features."
-msgstr ""
-"Output ini menunjukkan bahwa sistem Object Storage telah mengaktifkan "
-"website statis dan fitur URL sementara."
-
-msgid ""
-"This procedure can be adjusted as necessary to add additional security group "
-"rules to a project, if your cloud requires them."
-msgstr ""
-"Prosedur ini dapat disesuaikan seperlunya untuk menambahkan aturan kelompok "
-"keamanan tambahan untuk proyek, jika cloud Anda membutuhkan mereka."
-
-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 ""
-"Prosedur ini memungkinkan akses SSH dan ICMP (ping) ke instance. Aturan "
-"berlaku untuk semua instance dalam proyek tertentu, dan harus ditetapkan "
-"untuk setiap proyek kecuali ada alasan untuk melarang akses SSH atau ICMP ke "
-"instance."
-
-msgid ""
-"This request uses the ``Accept`` request header to ask for an XML response:"
-msgstr ""
-" Request (permintaan) ini menggunakan header permintaan ``Accept`` untuk "
-"meminta respon XML:"
-
-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 ""
-"Bagian ini menjelaskan cara untuk melakukan tugas yang berbeda yang terlibat "
-"dalam manajemen instance, seperti menambahkan alamat IP mengambang, "
-"berhenti dan mulai instance, dan mengakhiri instance. Bagian ini juga "
-"membahas tugas manajemen node."
-
-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 ""
-"Bagian ini dimaksudkan untuk memberikan serangkaian perintah klien tipikal "
-"API mungkin digunakan untuk membuat dan memodifikasi image."
-
-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 ""
-"Pandangan ini menunjukkan daftar penyeimbang beban yang ada. Untuk melihat "
-"rincian dari setiap penyeimbang beban, klik pada penyeimbang beban tertentu."
-
-msgid ""
-"This will automatically break the file into the desired segment size and "
-"upload segments to a container named ``_segments``."
-msgstr ""
-"This will automatically break the file into the desired segment size and "
-"upload segments to a container named ``_segments``."
-
-msgid ""
-"To accept requests from a particular range of IP addresses, specify the IP "
-"address block in the :guilabel:`CIDR` box."
-msgstr ""
-"Untuk menerima permintaan dari berbagai alamat IP tertentu, tentukan blok "
-"alamat IP di box :guilabel:`CIDR`."
-
-msgid ""
-"To access an instance through a remote console, run the following command:"
-msgstr ""
-"Untuk mengakses sebuah instance melalui remote konsol, jalankan perintah "
-"berikut:"
-
-msgid ""
-"To add a network to the instance, click the :guilabel:`+` in the :guilabel:"
-"`Available` field."
-msgstr ""
-"Untuk menambah jaringan ke instance, klik field (kolom) :guilabel:`+` dalam :"
-"guilabel:`Available`."
-
-msgid ""
-"To add a rule to a security group, call the `novaclient.v1\\_1.security"
-"\\_group\\_rules.SecurityGroupRuleManager.create `__ method:"
-msgstr ""
-"Untuk menambahkan aturan untuk grup keamanan, panggil `novaclient.v1\\_1."
-"security\\_group\\_rules.SecurityGroupRuleManager.create `__ metode:"
-
-msgid "To add an ICMP rule, click :guilabel:`Add Rule`."
-msgstr "Untuk menambahkan aturan ICMP, klik :guilabel:`Add Rule`."
-
-msgid ""
-"To allow SSH access to the instances, choose one of the following options:"
-msgstr ""
-"Untuk mengizinkan akses SSH ke instance, pilih salah satu opsi berikut:"
-
-msgid "To allow SSH access, click :guilabel:`Add Rule`."
-msgstr "Untuk mengizinkan akses SSH, klik :guilabel:`Add Rule`."
-
-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 ""
-"Untuk Mengizinkan akses melalui port UDP, seperti mengizinkan akses ke "
-"server DNS yang berjalan pada VM, pilih salah satu opsi berikut:"
-
-msgid "To allow pinging of the instances, choose one of the following options:"
-msgstr "Untuk Mengizinkan ping dari instance, pilih salah satu opsi berikut:"
-
-msgid ""
-"To attach a volume to a running instance, see :ref:"
-"`Attach_a_volume_to_an_instance`."
-msgstr ""
-"Untuk menghubungkan volume pada instance berjalan, lihat :ref: "
-"`Attach_a_volume_to_an_instance`."
-
-msgid ""
-"To attach swap or ephemeral disk to an instance, you need create new flavor "
-"first. This procedure shows you how to boot an instance with a 512 MB swap "
-"disk and 2 GB ephemeral disk."
-msgstr ""
-"To attach swap or ephemeral disk to an instance, you need create new flavor "
-"first. This procedure shows you how to boot an instance with a 512 MB swap "
-"disk and 2 GB ephemeral disk."
-
-msgid "To backup the database instance"
-msgstr "Untuk backup (cadangan) instance database"
-
-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 ""
-"Supaya dihapus berhasil, penyeimbang beban tidak harus memiliki pendengar "
-"atau kolam yang terkait dengan itu. Aksi penghapusan juga tersedia di kolom :"
-"guilabel: `Actions` untuk penyeimbang beban individu."
-
-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 ""
-"Untuk boot image Xen dari volume, image Anda memulai pada harus tipe yang "
-"sama, sepenuhnya virtual atau paravirtualized, sebagai salah satu pada "
-"volume."
-
-msgid ""
-"To bring every instance to the current version, use some of the optional "
-"arguments to control how many instances are updated at the same time. This "
-"is useful to avoid potential network issues, if the module payload is large. "
-"Since we are not using the ``--force`` flag, the minimum updated date will "
-"not change."
-msgstr ""
-"Untuk membawa setiap instance ke versi saat ini, gunakan beberapa argumen "
-"opsional untuk mengontrol jumlah instal yang diperbarui pada waktu yang "
-"bersamaan. Ini berguna untuk menghindari masalah jaringan potensial, jika "
-"muatan modulnya besar. Karena kita tidak menggunakan flag ``--force``, "
-"tanggal update minimum tidak akan berubah."
-
-msgid ""
-"To change its permissions so that only you can read and write to the file, "
-"run the following command:"
-msgstr ""
-"Untuk mengubah perizinannya sehingga hanya Anda yang dapat membaca dan "
-"menulis ke file, jalankan perintah berikut:"
-
-msgid "To change the flavor of an instance"
-msgstr "Untuk mengubah flavor sebuah instance"
-
-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 ""
-"Untuk mengubah manifes, menggunakan operasi ``PUT`` dengan parameter query "
-"``?multi-bagian-manifest = put`` . Permintaan ini membuat objek nyata "
-"(manifest). Anda juga dapat memperbarui metadata objek dengan cara yang "
-"biasa."
-
-msgid "To change the volume size of an instance"
-msgstr "Untuk mengubah ukuran volume instance"
-
-msgid "To check the status of containers, run the following command:"
-msgstr "Untuk memeriksa status kontainer, jalankan perintah berikut:"
-
-msgid "To check the status of the object, run the following command:"
-msgstr "Untuk memeriksa status dari objek, jalankan perintah berikut:"
-
-msgid ""
-"To complete these tasks, use these parameters on the :command:`openstack "
-"server create` command:"
-msgstr ""
-"Untuk menyelesaikan tugas ini, gunakan parameter ini pada perintah: :command:"
-"`openstack server create`:"
-
-msgid ""
-"To connect a private network to the newly created router, perform the "
-"following steps:"
-msgstr ""
-"Untuk menghubungkan jaringan pribadi ke router yang baru dibuat, lakukan "
-"langkah berikut:"
-
-msgid ""
-"To continue with this document, we recommend 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 ""
-"Untuk melanjutkan dokumen ini, kami merekomendasikan agar Anda telah "
-"menginstal layanan Database dan menyimpan data store Anda dengan image untuk "
-"jenis dan versi database yang Anda inginkan, dan Anda dapat membuat dan "
-"mengakses database."
-
-msgid ""
-"To create a container, run the following command and replace ``CONTAINER`` "
-"with the name of your container."
-msgstr ""
-"Untuk membuat sebuah kontainer, jalankan perintah berikut dan ganti "
-"``CONTAINER`` dengan nama kontainer Anda."
-
-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 ""
-"Untuk membuat volume non-bootable, jangan menciptakannya dari sebuah image. "
-"Volume harus sepenuhnya kosong tanpa tabel partisi dan tidak ada sistem file."
-
-msgid ""
-"To create a security group with a specified name and description, call the "
-"`novaclient.v\\_1.security\\_groups.SecurityGroupManager.create `__ method:"
-msgstr ""
-"Untuk membuat grup keamanan dengan nama tertentu dan deskripsinya, panggil "
-"`novaclient.v\\_1.security\\_groups.SecurityGroupManager.create `__ metode:"
-
-msgid ""
-"To create a security group with a specified name and description, enter the "
-"following command:"
-msgstr ""
-"Untuk membuat kelompok keamanan dengan nama tertentu dan deskripsi, masukkan "
-"perintah berikut:"
-
-msgid ""
-"To create a stack, or template, from an `example template file `__, run the following command:"
-msgstr ""
-"Untuk membuat tumpukan (stack), atau template, dari `example template file "
-"`__, jalankan "
-"perintah berikut:"
-
-msgid ""
-"To create a static large object, divide your content into pieces and create "
-"(upload) a segment object to contain each piece."
-msgstr ""
-"Untuk membuat sebuah objek besar statis, bagilah konten Anda menjadi "
-"potongan-potongan dan menciptakan (upload) objek segmen mengandung masing-"
-"masing bagian."
-
-msgid "To create the server, use the network, image, and flavor:"
-msgstr "Untuk membuat server, gunakan jaringan, image, dan flavor:"
-
-msgid "To define the response format, use one of these methods:"
-msgstr "Untuk menentukan format respon, gunakan salah satu metode ini:"
-
-msgid ""
-"To delete a container, click the :guilabel:`More` button and select :"
-"guilabel:`Delete Container`."
-msgstr ""
-"Untuk menghapus sebuah kontainer, klik tombol :guilabel:`More` dan pilih :"
-"guilabel:`Delete Container`."
-
-msgid "To delete a network:"
-msgstr "Untuk menghapus jaringan:"
-
-msgid "To delete a security group rule, specify the ID of the rule."
-msgstr "Untuk menghapus grup aturan keamanan, tentukan ID dari aturan."
-
-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 ""
-"Untuk menghapus grup keamanan, panggil `novaclient.v\\_1.security\\_groups."
-"SecurityGroupManager.delete `__ metode, melewati juga "
-"`novaclient.v1\\_1.security\\_groups.SecurityGroup `__ objek atau ID grup "
-"sebagai argumen:"
-
-msgid "To delete a specified group, enter the following command:"
-msgstr "Untuk menghapus kelompok tertentu, masukkan perintah berikut:"
-
-msgid ""
-"To delete an object, click the :guilabel:`More button` and select :guilabel:"
-"`Delete Object`."
-msgstr ""
-"Untuk menghapus sebuah objek, klik :guilabel:`More button` dan pilih :"
-"guilabel:`Delete Object`."
-
-msgid ""
-"To delete an object, click the menu button and select :guilabel:`Delete "
-"Object`."
-msgstr ""
-"Untuk menghapus sebuah objek, klik tombol menu dan pilih :guilabel:`Delete "
-"Object`."
-
-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 ""
-"Untuk menentukan apakah sistem Object Storage Anda mendukung fitur ini, "
-"lihat :doc:`managing-openstack-object-storage-with-swift-cli`. Atau, hubungi "
-"penyedia layanan Anda."
-
-msgid ""
-"To disable object versioning for the ``current`` container, remove its ``X-"
-"Versions-Location`` metadata header by sending an empty key value."
-msgstr ""
-"Untuk menonaktifkan objek versi kontainer ``current``, hapuslah header "
-"metadata ``X-Versi-Location`` dengan mengirimkan nilai kunci kosong."
-
-msgid "To disassociate a floating IP address from an instance:"
-msgstr "Untuk memisahkan alamat IP mengambang dari sebuah instance:"
-
-msgid ""
-"To disassociate an IP address from an instance, click the :guilabel:"
-"`Disassociate` button."
-msgstr ""
-"Untuk memisahkan alamat IP dari sebuah Instance, klik tombol :guilabel:"
-"`Disassociate`."
-
-msgid ""
-"To discover whether your Object Storage system supports this feature, see :"
-"ref:`discoverability` or check with your service provider."
-msgstr ""
-"Untuk mengetahui apakah sistem Storage Object Anda mendukung fitur ini, "
-"lihat :ref: `discoverability` atau hubungi penyedia layanan Anda."
-
-msgid ""
-"To discover whether your Object Storage system supports this feature, see :"
-"ref:`discoverability`. Alternatively, check with your service provider."
-msgstr ""
-"Untuk mengetahui apakah sistem Storage Object Anda mendukung fitur ini, "
-"lihat :ref: `discoverability`. Atau, hubungi penyedia layanan Anda."
-
-msgid ""
-"To discover which features are enabled in your Object Storage system, use "
-"the ``/info`` request."
-msgstr ""
-"Untuk menemukan fitur yang diaktifkan dalam sistem Storage Object Anda, "
-"gunakan permintaan (request) ``/info`."
-
-msgid ""
-"To display a list of all the objects in the storage container, use ``GET`` "
-"without a ``delimiter`` or ``prefix``."
-msgstr ""
-"Untuk menampilkan daftar semua objek dalam kontainer penyimpanan, gunakan "
-"``GET`` tanpa ``delimiter`` atau ``prefix``."
-
-msgid "To download a summary, click :guilabel:`Download CSV Summary`."
-msgstr "Untuk men-download ringkasan, klik :guilabel:`Download CSV Summary`."
-
-msgid "To download an object from a container, run the following command:"
-msgstr "Untuk men-download objek dari kontainer, jalankan perintah berikut:"
-
-msgid "To enable and use object versioning"
-msgstr "Untuk mengaktifkan dan menggunakan objek versioning"
-
-msgid ""
-"To enable object versioning, ask your cloud provider to set the "
-"``allow_versions`` option to ``TRUE`` in the container configuration file."
-msgstr ""
-"Untuk mengaktifkan objek versioning, mintalah penyedia cloud Anda untuk "
-"mengatur opsi ``allow_versions`` untuk ``TRUE`` di file konfigurasi "
-"kontainer."
-
-msgid ""
-"To enable the configuration drive, pass the ``--config-drive true`` "
-"parameter to the :command:`openstack server create` command."
-msgstr ""
-"Untuk mengaktifkan drive konfigurasi, lewatkan parameter ``--config-drive "
-"true`` ke perintah :command:`openstack server create`."
-
-msgid ""
-"To ensure that the key pair has been successfully imported, list key pairs "
-"as follows:"
-msgstr ""
-"Untuk memastikan bahwa pasangan kunci (key pair) telah berhasil diimpor, "
-"daftar pasangan kunci sebagai berikut:"
-
-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 ""
-"Untuk memastikan download bekerja dengan benar, Anda harus meng-upload semua "
-"segmen objek ke kontainer yang sama dan awalan (prefix) setiap nama objek "
-"sehingga segmen semacam agar rangkaian yang benar."
-
-msgid ""
-"To explore the state and history of a particular stack, you can run a number "
-"of commands."
-msgstr ""
-"Untuk menjelajahi kondisi dan sejarah (history) dari tumpukan (stack) "
-"tertentu, Anda dapat menjalankan sejumlah perintah."
-
-msgid "To generate a key pair, run the following command."
-msgstr "Untuk menghasilkan sepasang kunci, jalankan perintah berikut."
-
-msgid ""
-"To generate a keypair, call the `novaclient.v1\\_1.keypairs.KeypairManager."
-"create `__ method:"
-msgstr ""
-"Untuk menghasilkan keypair, panggil metode `novaclient.v1\\_1.keypairs."
-"KeypairManager.create `__:"
-
-msgid ""
-"To give a user read access, use the :command:`swift post` command with the "
-"``-r`` parameter. To give a user write access, use the ``-w`` parameter."
-msgstr ""
-"Untuk memberikan pengguna akses baca, gunakan perintah :command:`swift post` "
-"dengan parameter ``-r``. Untuk memberikan pengguna akses menulis, gunakan "
-"parameter ``-w``."
-
-msgid ""
-"To incorporate your incremental backups, you simply use the `--backup`` "
-"parameter to pass in the ``BACKUP_ID`` of your most recent incremental "
-"backup. The Database service handles the complexities of applying the chain "
-"of all previous incremental backups."
-msgstr ""
-"Untuk memasukkan incremental backup Anda, Anda hanya menggunakan parameter "
-"`--backup`` untuk melewatkan dalam` `BACKUP_ID`` dari incremental backup "
-"terbaru. Layanan Database menangani kompleksitas penerapan rantai dari semua "
-"incremental backup sebelumnya."
-
-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 ""
-"Untuk menunjukkan sebuah wadah (container), tentukan nama wadah sebagai: `` "
-"CONTAINER_NAME``. Pastikan bahwa wadah kosong. Jika berisi objek, Object "
-"Storage tidak dapat menghapus wadah."
-
-msgid ""
-"To indicate an object, specify the container and object name as: "
-"``CONTAINER_NAME``/``OBJECT_NAME``."
-msgstr ""
-"Untuk menunjukkan objek, tentukan wadah (container) dan objek nama sebagai: "
-"``CONTAINER_NAME``/``OBJECT_NAME``."
-
-msgid ""
-"To initiate a hypervisor-level suspend operation, run the following command:"
-msgstr ""
-"Untuk memulai hypervisor tingkat menangguhkan operasi, jalankan perintah "
-"berikut:"
-
-msgid ""
-"To launch an instance from the snapshot, select the snapshot and click :"
-"guilabel:`Launch`. Proceed with launching an instance."
-msgstr ""
-"Untuk memulai sebuah instance dari snapshot, pilih snapshot dan klik :"
-"guilabel:`Launch`. Lanjutkan dengan meluncurkan sebuah instance."
-
-msgid ""
-"To launch multiple instances, enter a value greater than ``1``. The default "
-"is ``1``."
-msgstr ""
-"Untuk meluncurkan beberapa instance, masukkan nilai lebih besar dari ``1``. "
-"Default adalah ``1``."
-
-msgid ""
-"To learn how, refer to the `Template Guide `__ on the OpenStack developer "
-"documentation website."
-msgstr ""
-"Untuk mempelajari caranya, merujuk pada `Template Guide `__ di situs "
-"dokumentasi pengembang OpenStack."
-
-msgid "To list all containers, run the following command:"
-msgstr "Untuk daftar semua kontainer, jalankan perintah berikut:"
-
-msgid ""
-"To list all floating IP addresses that are allocated to the current project, "
-"run:"
-msgstr ""
-"Untuk daftar semua alamat IP mengambang yang dialokasikan untuk proyek ini, "
-"jalankan:"
-
-msgid "To list all pools that provide floating IP addresses, run:"
-msgstr ""
-"Untuk daftar semua kolam (pool) yang menyediakan alamat IP mengambang, "
-"jalankan:"
-
-msgid ""
-"To list keypairs, call the `novaclient.v1\\_1.keypairs.KeypairManager.list "
-"`__ method:"
-msgstr ""
-"Untuk mendaftar pasangan kunci, panggil `novaclient.v1\\_1.keypairs."
-"KeypairManager.list `__ metode:"
-
-msgid ""
-"To list security groups for the current project, call the `novaclient.v\\_1."
-"security\\_groups.SecurityGroupManager.list `__ method:"
-msgstr ""
-"Untuk mendaftar kelompok keamanan untuk proyek saat ini, panggil "
-"`novaclient.v\\_1.security\\_groups.SecurityGroupManager.list `__ metode:"
-
-msgid ""
-"To list the available images, call the ``glanceclient.v2.images.Controller."
-"list`` method:"
-msgstr ""
-"Untuk daftar image yang tersedia, panggil metode ``glanceclient.v2.images."
-"Controller.list``:"
-
-msgid "To list the objects in a container, run the following command:"
-msgstr ""
-"Untuk mendaftar objek dalam sebuah kontainer, jalankan perintah berikut:"
-
-msgid "To list the rules for a security group, run the following command:"
-msgstr ""
-"Untuk mendaftar aturan untuk kelompok keamanan, jalankan perintah berikut:"
-
-msgid ""
-"To list the security groups for the current project, including descriptions, "
-"enter the following command:"
-msgstr ""
-"Untuk mendaftar kelompok keamanan untuk proyek ini, termasuk deskripsi, "
-"masukkan perintah berikut:"
-
-msgid "To make the key pair known to SSH, run the :command:`ssh-add` command."
-msgstr ""
-"Membuat pasangan kunci (key pair) untuk diketahui SSH, jalankan perintah :"
-"command:`ssh-add` ."
-
-msgid "To model data, Telemetry uses the following abstractions:"
-msgstr "Untuk data model, Telemetry menggunakan abstraksi berikut:"
-
-msgid "To obtain these values, run the :command:`swift stat -v` command."
-msgstr ""
-"Untuk mendapatkan nilai ini, jalankan perintah :command:`swift stat -v`."
-
-msgid "To page through a large list of containers"
-msgstr "Untuk halaman keseluruhan daftar besar kontainer"
-
-msgid "To pause an instance, run the following command:"
-msgstr "Untuk menghentikan instance, jalankan perintah berikut:"
-
-msgid ""
-"To perform a bulk delete operation, add the ``bulk-delete`` query parameter "
-"to the path of a ``POST`` or ``DELETE`` operation."
-msgstr ""
-"Untuk melakukan operasi penghapusan massal, tambahkan parameter query ``bulk-"
-"delete`` ke path operasi ``POST`` atau ``DELETE``."
-
-msgid "To perform a hard reboot, pass the ``--hard`` parameter, as follows:"
-msgstr ""
-"Untuk melakukan hard reboot, lewatkan parameter ``--hard``, sebagai berikut:"
-
-msgid ""
-"To perform an instance reboot into rescue mode, run the following command:"
-msgstr ""
-"Untuk melakukan sebuah instance reboot ke mode penyelamatan (rescue), "
-"jalankan perintah berikut:"
-
-msgid ""
-"To query the instance usage for a month, select a month and click :guilabel:"
-"`Submit`."
-msgstr ""
-"Untuk kueri penggunaan instance selama satu bulan, pilih bulan dan klik :"
-"guilabel:`Submit`."
-
-msgid ""
-"To release the floating IP address back into the floating IP pool, click "
-"the :guilabel:`Release Floating IP` option in the :guilabel:`Actions` column."
-msgstr ""
-"Untuk melepaskan alamat IP mengambang kembali ke pool IP mengambang, klik "
-"opsi :guilabel:`Release Floating IP` dalam kolom :guilabel:`Actions`."
-
-msgid "To remove the floating IP address from a project:"
-msgstr "Untuk menghapus alamat IP mengambang dari proyek:"
-
-msgid ""
-"To resize the server, use the :command:`openstack server resize` command and "
-"add the server ID or name and the new flavor. For example:"
-msgstr ""
-"Untuk mengubah ukuran server, gunakan: perintah :command:`openstack server "
-"resize` dan menambahkan ID server atau nama dan flavor baru. Sebagai contoh:"
-
-msgid ""
-"To restart the instance from the normal boot disk, run the following command:"
-msgstr ""
-"Untuk me-restart instance dari disk boot normal, jalankan perintah berikut:"
-
-msgid "To restore a database instance"
-msgstr "Untuk mengembalikan (restore) instance database"
-
-msgid "To resume a suspended instance, run the following command:"
-msgstr "Untuk melanjutkan instance ditangguhkan, jalankan perintah berikut:"
-
-msgid ""
-"To retrieve an image object from its ID, call the ``glanceclient.v2.images."
-"Controller.get`` method:"
-msgstr ""
-"Untuk mengambil objek image dari ID-nya, sebut metode ``glanceclient.v2."
-"images.Controller.get``:"
-
-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 ""
-"Untuk kembali kurang dari 10.000 nama, gunakan parameter ``limit``. Jika "
-"jumlah nama kembali sama ditentukan ``limit`` (atau 10.000 jika Anda "
-"menghilangkan parameter ``limit``), Anda dapat mengasumsikan ada lebih nama "
-"untuk daftar. Jika jumlah nama dalam daftar adalah tepat habis dibagi oleh "
-"nilai ``limit``, permintaan terakhir tidak memiliki konten."
-
-msgid ""
-"To run the cURL command examples for the Object Storage API requests, set "
-"these environment variables:"
-msgstr ""
-"Untuk menjalankan contoh perintah cURL untuk permintaan API Object Storage, "
-"atur variabel lingkungan ini:"
-
-msgid ""
-"To run the cURL command examples, you must export environment variables. For "
-"more information, see the section :ref:`env-vars`."
-msgstr ""
-"Untuk menjalankan contoh perintah Curl, Anda harus mengekspor variabel "
-"lingkungan. Untuk informasi lebih lanjut, lihat bagian :ref: `env-vars`."
-
-msgid ""
-"To schedule an object for deletion, include one of these headers with the "
-"``PUT`` or ``POST`` request on the object:"
-msgstr ""
-"Untuk menjadwalkan sebuah objek untuk penghapusan, masukkan salah satu tajuk "
-"(header) ini dengan permintaan ``PUT`` atau ``POST`` pada objek:"
-
-msgid ""
-"To see which stacks are visible to the current user, run the following "
-"command:"
-msgstr ""
-"Untuk melihat stacks yang terlihat untuk pengguna saat ini, jalankan "
-"perintah berikut:"
-
-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 ""
-"Untuk memilih volume dari mana untuk memulai, mulailah sebuah instance dari "
-"sebuah image apapun pada volume. Apapun image yang Anda pilih tidak bisa "
-"boot. Sebaliknya, itu diganti dengan image pada volume yang Anda pilih dalam "
-"langkah selanjutnya."
-
-msgid ""
-"To set the permissions of the ``.pem`` file so that only you can read and "
-"write to it, run the following command."
-msgstr ""
-"Untuk mengatur hak akses dari file ``.pem`` sehingga hanya Anda dapat "
-"membaca dan menulis untuk itu, jalankan perintah berikut."
-
-msgid ""
-"To set up environmental variables and authenticate against Compute API "
-"endpoints, see :ref:`sdk_authenticate`."
-msgstr ""
-"Untuk mengatur variabel lingkungan dan mengotentikasi terhadap endpoint "
-"Compute API, lihat :ref:`sdk_authenticate`."
-
-msgid "To show the details for a particular event, run the following command:"
-msgstr ""
-"Untuk menampilkan rincian untuk peristiwa tertentu, jalankan perintah "
-"berikut:"
-
-msgid ""
-"To show the details for a specific resource in a stack, run the following "
-"command:"
-msgstr ""
-"Untuk menampilkan rincian untuk sumber daya tertentu dalam tumpukan (stack), "
-"jalankan perintah berikut:"
-
-msgid "To show the details of a stack, run the following command:"
-msgstr ""
-"Untuk menampilkan rincian dari tumpukan (stack), jalankan perintah berikut:"
-
-msgid ""
-"To successfully write to a container, a user must have read privileges (in "
-"addition to write) on the container. For all aforementioned read/write ACL "
-"examples, one can replace the project/user name with project/user UUID, i.e. "
-"``:``. If using multiple keystone domains, UUID "
-"format is required."
-msgstr ""
-"Untuk berhasil menulis ke sebuah kontainer, pengguna harus memiliki hak baca "
-"(selain untuk menulis) pada kontainer. Untuk semua contoh membaca/menulis "
-"ACL tersebut, seseorang dapat menggantikan nama proyek/pengguna dengan UUID "
-"proyek/pengguna , yaitu ``: ``. Jika menggunakan "
-"beberapa domain keystone, Format UUID diperlukan."
-
-msgid "To unpause an instance, run the following command:"
-msgstr "Menghentikan jeda instance, jalankan perintah berikut:"
-
-msgid ""
-"To update a module you should have another file ready to update the module "
-"with:"
-msgstr ""
-"Untuk memperbarui modul Anda harus memiliki file lain yang siap untuk "
-"memperbarui modul dengan:"
-
-msgid ""
-"To update an existing stack from a modified template file, run a command "
-"like the following command:"
-msgstr ""
-"Untuk memperbarui tumpukan (stack) yang ada dari file template dimodifikasi, "
-"menjalankan perintah seperti perintah berikut:"
-
-msgid ""
-"To update an instance in a cluster you can use the :command:`trove module-"
-"apply` command:"
-msgstr ""
-"Untuk mengupdate sebuah instance di cluster Anda bisa menggunakan perintah :"
-"command:`trove module-apply`:"
-
-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 ""
-"Untuk meng-upload file arsip, buat permintaan ``PUT``. Tambahkan query "
-"parameter ``extract-archive=format`` untuk menunjukkan bahwa Anda meng-"
-"upload file arsip tar bukannya konten normal."
-
-msgid ""
-"To upload an image, call the ``glanceclient.v2.images.ImageManager.create`` "
-"method:"
-msgstr ""
-"Untuk mengupload image, panggil metode ``glanceclient.v2.images."
-"ImageManager.create``:"
-
-msgid ""
-"To upload an object in chunks, for larger than 5GB files, run the following "
-"command:"
-msgstr ""
-"To upload an object in chunks, for larger than 5GB files, run the following "
-"command:"
-
-msgid "To upload an object to a container, run the following command:"
-msgstr ""
-"Untuk meng-upload sebuah objek ke kontainer, jalankan perintah berikut:"
-
-msgid ""
-"To use SSH to connect to your instance, use the downloaded keypair file."
-msgstr ""
-"Untuk menggunakan SSH untuk koneksi ke instance Anda, gunakan file key pair "
-"yang di-download"
-
-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 ""
-"Untuk menggunakan drive konfigurasi dengan Hyper-V, Anda harus mengatur "
-"nilai ``mkisofs_cmd`` ke path lengkap ke instalasi ``mkisofs.exe``. Selain "
-"itu, Anda harus mengatur nilai ``qemu_img_cmd`` di bagian konfigurasi `` "
-"hyperv`` ke path lengkap ke instalasi perintah :command:`qemu-img`. "
-
-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 ""
-"Untuk menggunakan drive konfigurasi dengan libvirt, XenServer, atau VMware, "
-"Anda harus menginstal paket genisoimage pada setiap host komputasi. Jika "
-"tidak, instance tidak boot dengan benar."
-
-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 ""
-"Untuk menggunakan drive konfigurasi dengan layanan Bare Metal, Anda tidak "
-"perlu mempersiapkan apa-apa karena layanan Bare Metal memperlakukan drive "
-"konfigurasi benar."
-
-msgid ""
-"To use snapshots to migrate instances from OpenStack projects to clouds, "
-"complete these steps."
-msgstr ""
-"Untuk menggunakan snapshot memigrasikan instance dari proyek OpenStack ke "
-"cloud, lengkapi langkah ini."
-
-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 ""
-"Untuk menggunakan API OpenStack, keakraban hal berikut akan membantunya. Hal "
-"itu meliputi akrab dengan HTTP / 1.1, layanan web RESTful, layanan "
-"OpenStack, dan format serialisasi data JSON atau XML."
-
-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 ""
-"Untuk menggunakan klien Virtual Network Computing (VNC) dashboard, browser "
-"Anda harus mendukung HTML5 Canvas dan HTML5 WebSockets. Klien VNC "
-"berdasarkan noVNC. Untuk rincian, lihat `noVNC: HTML5 VNC Client `__. Untuk daftar browser yang "
-"didukung, lihat `Browser support `__."
-
-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 ""
-"Untuk menggunakan request (permintaan) ``/info``, kirim request "
-"``GET``menggunakan path ``/info`` ke endpoint Object Store seperti yang "
-"ditunjukkan dalam contoh ini:"
-
-msgid ""
-"To use the configuration drive, you must follow the following requirements "
-"for the compute host and image."
-msgstr ""
-"Untuk menggunakan drive konfigurasi, Anda harus mengikuti persyaratan "
-"berikut untuk host dan image komputasi"
-
-msgid ""
-"To use the information in this section, you must be familiar with OpenStack "
-"Compute."
-msgstr ""
-"Untuk menggunakan informasi dalam bagian ini, Anda harus terbiasa dengan "
-"OpenStack Compute."
-
-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 ""
-"Untuk menggunakan informasi dalam bagian ini, Anda harus memiliki pemahaman "
-"umum OpenStack Networking, OpenStack Compute, dan integrasi antara keduanya. "
-"Anda juga harus memiliki akses ke sebuah plug-in yang mengimplementasikan "
-"Networking API v2.0."
-
-msgid ""
-"To use the legacy ``python-novaclient`` with a Compute endpoint, instantiate "
-"a `novaclient.v2.client.Client `__ object using ``os-client-config``:"
-msgstr ""
-"Untuk menggunakan legacy ``python-novaclient`` dengan Compute endpoint, "
-"instantiate `novaclient.v2.client.Client `__ object using ``os-client-"
-"config``:"
-
-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 ""
-"Untuk memvalidasi bahwa file tersebut injected, gunakan ssh untuk menyambung "
-"ke instance, dan lihat file ``/var/lib/cloud``."
-
-msgid ""
-"To verify that the server was deleted, run the :command:`openstack server "
-"list` command:"
-msgstr ""
-"Untuk memverifikasi bahwa server telah dihapus, jalankan: perintah :command:"
-"`openstack server list`:"
-
-msgid ""
-"To view the available options for the :command:`openstack server list` "
-"command, run the following command:"
-msgstr ""
-"Untuk melihat pilihan yang tersedia untuk perintah :command:`openstack "
-"server list` jalankan perintah berikut:"
-
-msgid "Topology"
-msgstr "Topologi"
-
-msgid "Track usage for instances"
-msgstr "Track usage for instances (penggunaan jalur untuk instance)"
-
-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 ""
-"Aktifkan daftar file. Jika Anda tidak mengatur file indeks, URL menampilkan "
-"daftar objek dalam kontainer. Petunjuk tentang styling daftar dengan "
-"mengikuti CSS."
-
-msgid "UTF-8-encode and then URL-encode the names."
-msgstr "UTF-8-encode dan kemudian URL-encode nama."
-
-msgid "Ubuntu"
-msgstr "Ubuntu"
-
-msgid "Unmount the volume"
-msgstr "Melakukan unmount volume"
-
-msgid "Unpause"
-msgstr "Unpause (batalkan jeda)"
-
-msgid "Unshelve an instance - Restores the instance."
-msgstr "Unshelve (meletakan) instance - Restore (mengembalikan) instance."
-
-msgid "Unsuspend"
-msgstr "Unsuspend (batalkan penangguhan)"
-
-msgid "Update a database instance"
-msgstr "Update database instance"
-
-msgid "Update a stack"
-msgstr "Memperbarui stack"
-
-msgid "Update an image"
-msgstr "Update image"
-
-msgid "Update image"
-msgstr "Update image"
-
-msgid "Update server (API v2)"
-msgstr "Update server (API v2)"
-
-msgid "Update server code listing example"
-msgstr "Update kode server daftar contoh"
-
-msgid "Update the image"
-msgstr "Update image"
-
-msgid ""
-"Update the module again. By doing this, it will cause the instances to "
-"report their module is not current."
-msgstr ""
-"Perbaharui modul lagi. Dengan melakukan ini, akan menyebabkan instance untuk "
-"melaporkan modul mereka tidak saat ini."
-
-msgid "Updating and creating a second module for a redis cluster"
-msgstr "Memperbarui dan membuat modul kedua untuk cluster redis"
-
-msgid "Upload RAM image"
-msgstr "Upload RAM image"
-
-msgid ""
-"Upload a large file by specifying the segment size with the ``--segment-"
-"size`` or ``-S`` arguments:"
-msgstr ""
-"Upload a large file by specifying the segment size with the ``--segment-"
-"size`` or ``-S`` arguments:"
-
-msgid "Upload an image"
-msgstr "Upload image"
-
-msgid "Upload an object"
-msgstr "Upload object"
-
-msgid "Upload and manage images"
-msgstr "Upload dan mengelola image"
-
-msgid "Upload binary image data"
-msgstr "Upload binary image data (mengunggah data citra biner)"
-
-msgid "Upload kernel image"
-msgstr "Upload kernel image"
-
-msgid "Upload large objects with python-swiftclient"
-msgstr "Upload large objects with python-swiftclient"
-
-msgid "Upload manifest request: HTTP"
-msgstr "Upload permintaan (request) manifest: HTTP"
-
-msgid "Upload manifest response: HTTP"
-msgstr "Upload respon manifest: HTTP"
-
-msgid "Upload next segment of large object request: HTTP"
-msgstr "Upload segmen permintaan objek besar berikutnya: HTTP"
-
-msgid "Upload order"
-msgstr "Upload order (urutan upload)"
-
-msgid "Upload segment of large object request: HTTP"
-msgstr "Upload segmen permintaan (request) objek besar: HTTP"
-
-msgid "Upload the volume to glance."
-msgstr "Upload volume ke glance "
-
-msgid "Upload three-part image"
-msgstr "Upload three-part image"
-
-msgid ""
-"Uploading objects in chunks is mandatory if uploading an object larger than "
-"5GB."
-msgstr ""
-"Uploading objects in chunks is mandatory if uploading an object larger than "
-"5GB."
-
-msgid ""
-"Use `EpochConverter `_ to convert dates to "
-"and from epoch timestamps and for batch conversions."
-msgstr ""
-"Gunakan `EpochConverter `_ untuk "
-"mengkonversi tanggal ke dan dari cap waktu zaman dan untuk konversi batch."
-
-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 ""
-"Gunakan ``X-Container-Meta-Web-Index`` untuk menentukan file indeks (atau "
-"halaman default disajikan, seperti `index.html```) untuk website Anda. "
-"Ketika seseorang awalnya memasuki situs Anda, file ``index.html`` "
-"menampilkan otomatis. Jika Anda membuat sub-direktori untuk situs Anda "
-"dengan membuat pseudo-direktori dalam kontainer Anda, halaman indeks untuk "
-"setiap sub-direktori akan ditampilkan secara default. Jika Anda pseudo-"
-"direktori tidak memiliki file dengan nama yang sama dengan file indeks, "
-"kunjungan ke sub-direktori mengembalikan kesalahan 404."
-
-msgid "Use a ``limit`` of two:"
-msgstr "Gunakan `` limit`` dua:"
-
-msgid "Use gzip or bzip2 to compress the archive."
-msgstr "Gunakan gzip atau bzip2 untuk kompres arsip."
-
-msgid "Use incremental backups"
-msgstr "Gunakan inkremental backup (cadangan) "
-
-msgid "Use one of the following methods to stop and start an instance."
-msgstr ""
-"Gunakan salah satu metode berikut untuk berhenti dan memulai sebuah instance."
-
-msgid "Use snapshots to migrate instances"
-msgstr "Gunakan snapshot untuk bermigrasi instance."
-
-msgid "Use ssh to connect to the instance"
-msgstr "Gunakan ssh untuk terhubung ke instance"
-
-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 ""
-"Gunakan perintah :command:`nova baremetal-node-list` untuk melihat semua "
-"node bare-metal dan interface. Ketika sebuah node digunakan, statusnya "
-"termasuk UUID dari instance yang berjalan di atasnya:"
-
-msgid ""
-"Use the :command:`nova baremetal-node-show` command to view the details for "
-"a bare-metal node:"
-msgstr ""
-"Gunakan perintah :command:`nova baremetal-node-show` untuk melihat rincian "
-"node bare-metal:"
-
-msgid ""
-"Use the :command:`openstack image list` command to check the status until "
-"the status is ``active``:"
-msgstr ""
-"Gunakan perintah :command:`openstack image list` untuk memeriksa status "
-"sampai statusnya ``active``:"
-
-msgid ""
-"Use the :command:`openstack server image create` command to take a snapshot:"
-msgstr ""
-"Use the :command:`openstack server image create` command to take a snapshot:"
-
-msgid ""
-"Use the :command:`openstack server list` command to confirm that the "
-"instance shows a ``SHUTOFF`` status:"
-msgstr ""
-"Gunakan perintah :command:`openstack server list` untuk mengkonfirmasi bahwa "
-"instance menunjukkan status ``SHUTOFF``:"
-
-msgid ""
-"Use the :command:`openstack server stop` command to shut down the instance:"
-msgstr ""
-"Gunakan perintah :command:`openstack server stop` untuk menutup instance:"
-
-msgid "Use the :command:`openstack` commands to manage floating IP addresses."
-msgstr ""
-"Gunakan perintah :command:`openstack` untuk mengelola alamat IP mengambang."
-
-msgid ""
-"Use the :command:`ssh` command to make a secure connection to the instance. "
-"For example:"
-msgstr ""
-"Gunakan perintah :command:`ssh` untuk membuat sambungan aman untuk instance. "
-"Sebagai contoh:"
-
-msgid "Use the :command:`trove backup-create` command and specify:"
-msgstr "Gunankan perintah :command:`trove backup-create` dan tentukan:"
-
-msgid ""
-"Use the :command:`trove database-list` command to check that the original "
-"databases (``db1`` and ``db2``) are present on the restored instance."
-msgstr ""
-"Gunakan perintah :command:`trove database-list` untuk memeriksa bahwa "
-"database asli (` `db1`` dan` `db2``) yang hadir pada instance dipulihkan."
-
-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 ""
-"Gunakan perintah :command:`trove show` untuk menampilkan informasi tentang "
-"instance guest2 baru. Lulus dalam guest2 ini ``INSTANCE_ID``, yang merupakan "
-"``ac7a2b35-a9b4-4ff6-beac-a1bcee86d04b``."
-
-msgid ""
-"Use the :command:`trove user-list` command to check that the original user "
-"(``user1``) is present on the restored instance."
-msgstr ""
-"Gunakan perintah :command:`trove user-list` untuk memeriksa bahwa pengguna "
-"asli (` `user1``) hadir pada instance dipulihkan."
-
-msgid ""
-"Use the POST method to assign expiration headers to existing objects that "
-"you want to expire."
-msgstr ""
-"Menggunakan metode POST untuk menetapkan header kedaluwarsa objek yang ada "
-"dimana Anda ingin berakhir."
-
-msgid ""
-"Use the ``end_marker`` parameter to limit the result set to object names "
-"that are less than the ``end_marker`` parameter value:"
-msgstr ""
-"Gunakan parameter ``end_marker`` untuk membatasi hasil set ke objek nama "
-"yang kurang dari nilai parameter ``end_marker``:"
-
-msgid ""
-"Use the ``extract-archive`` query parameter to specify the format. Valid "
-"values for this parameter are ``tar``, ``tar.gz``, or ``tar.bz2``."
-msgstr ""
-"Gunakan parameter query ``extract-archive`` untuk menentukan format. Nilai "
-"yang valid untuk parameter ini adalah ``tar``, ``tar.gz``, atau ``tar.bz2``."
-
-msgid "Use the ``get_credentials()`` method to populate and get a dictionary:"
-msgstr ""
-"Gunakan metode ``get_credentials () `` untuk mengisi dan mendapatkan kamus "
-"(dictionary):"
-
-msgid ""
-"Use the ``get_nova_credentials()`` method to populate and get a dictionary:"
-msgstr ""
-"Gunakan metode ``get_nova_credentials()`` untuk mengisi dan mendapatkan "
-"kamus (dictionary):"
-
-msgid ""
-"Use the ``get_nova_credentials_v2()`` method to populate and get a "
-"dictionary:"
-msgstr ""
-"Gunakan metode ``get_nova_credentials_v2 () `` untuk mengisi dan mendapatkan "
-"kamus:"
-
-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 ""
-"Gunakan flag ``mkisofs_cmd``` untuk mengatur jalan dimana Anda menginstal "
-"program genisoimage. Jika genisoimage berada di jalur yang sama dengan "
-"layanan ``nova-compute``, Anda tidak perlu mengatur bendera (flag) ini."
-
-msgid ""
-"Use the ``prefix`` and ``delimiter`` parameters to view the objects inside a "
-"pseudo-directory, including further nested pseudo-directories."
-msgstr ""
-"Gunakan parameter ``prefix`` dan ``delimiter`` untuk melihat objek di dalam "
-"pseudo-directory, termasuk pseudo-directory bersarang lebih lanjut."
-
-msgid "Use the auto-extract archive feature to upload a tar archive file."
-msgstr "Gunakan fitur arsip auto-ekstrak untuk meng-upload file arsip tar."
-
-msgid ""
-"Use the concepts described in the overview section to fill in the necessary "
-"information about the load balancer you want to create."
-msgstr ""
-"Gunakan konsep yang dijelaskan di bagian overview untuk mengisi tentang "
-"informasi yang diperlukan untuk penyeimbang beban yang Anda ingin buat."
-
-msgid ""
-"Use the delimiter parameter to limit the displayed results. To use "
-"``delimiter`` with pseudo-directories, you must use the parameter slash (``/"
-"``)."
-msgstr ""
-"Gunakan parameter pembatas untuk membatasi hasil yang ditampilkan. Untuk "
-"menggunakan ``delimiter`` dengan pseudo-directory, Anda harus menggunakan "
-"parameter garis miring (`` / ``)."
-
-msgid ""
-"Used in this way, configuration groups let you modify your database cloud "
-"configuration, on the fly, on a massive scale."
-msgstr ""
-"Digunakan dengan cara ini, kelompok konfigurasi membiarkan Anda mengubah "
-"konfigurasi cloud database Anda, dengan cepat, dalam skala besar."
-
-msgid "Used to manage volumes and volume snapshots that attach to instances."
-msgstr ""
-"Digunakan untuk mengelola volume dan snapshot volume yang terkait instance."
-
-msgid "User data"
-msgstr "Data pengguna (user)"
-
-msgid "User1 from project1 can read container contents:"
-msgstr "User1 dari project1 dapat membaca konten kontainer:"
-
-msgid "User1 from project1 can write to the container:"
-msgstr "User1 dari project1 dapat menulis ke kontainer:"
-
-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 ""
-"Pengguna (user) memiliki peran di account (akun). Misalnya, pengguna dengan "
-"peran admin memiliki akses penuh ke semua kontainer dan objek dalam akun. "
-"Anda dapat mengatur daftar kontrol akses (ACL) di tingkat kontainer dan "
-"daftar dukungan untuk membaca dan menulis akses, dimana Anda mengatur dengan "
-"header ``X-Container-Read`` dan ``X-Container-Write``."
-
-msgid "Users: The ``user1`` user with the ``password`` password"
-msgstr "Pengguna: pengguna ``user1`` dengan kata sandi ``password``"
-
-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 ""
-"Menggunakan opsi ini, Anda dapat boot dari snapshot volume dan membuat "
-"volume baru dengan memilih :guilabel:`Volume Snapshot` dari daftar dan "
-"menambahkan :guilabel:`Device Name` untuk volume Anda. Klik opsi :guilabel:"
-"`Delete Volume on Instance Delete` untuk menghapus volume pada penghapusan "
-"instance."
-
-msgid "VCPUs"
-msgstr "VCPUs"
-
-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 ""
-"VNC atau SPICE digunakan untuk melihat konsol output dari sebuah instance, "
-"terlepas dari apakah log konsol memiliki output atau tidak. Hal ini "
-"memungkinkan menyampaikan aktivitas keyboard dan mouse ke dan dari sebuah "
-"instance."
-
-msgid ""
-"Valid values for the ``format`` variable are ``tar``, ``tar.gz``, or ``tar."
-"bz2``."
-msgstr ""
-"Nilai yang valid untuk variable ``format`` adalah ``tar``, ``tar.gz``, atau "
-"``tar.bz2``."
-
-msgid "Verify the ``X-Delete-At`` header has posted to the object:"
-msgstr ""
-"Lakukan verifikasi header ``X-Delete-At`` yang telah diposting ke objek:"
-
-msgid "Versioning with python-swiftclient"
-msgstr "Versioning with python-swiftclient"
-
-msgid "View and manage load balancers v2"
-msgstr "Melihat dan mengelola beban balancers v2"
-
-msgid "View console log of instance"
-msgstr "View console log instance (Lihat log konsol instance)"
-
-msgid "View existing load balancers"
-msgstr "Lihat load balancer (penyeimbang beban) yang ada"
-
-msgid "View statistics:"
-msgstr "Lihat statistik:"
-
-msgid "Virtual CPUs: ``1``"
-msgstr "Virtual CPUs: ``1``"
-
-msgid "Volume"
-msgstr "Volume"
-
-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 ""
-"Volume: Jika Anda memilih opsi ini, field baru untuk menampilkan :guilabel:"
-"`Use volume as a source`. Anda dapat memilih volume dari daftar. Pilihan "
-"untuk menggunakan snapshot atau volume sebagai sumber untuk volume "
-"ditampilkan hanya jika ada snapshot atau volume."
-
-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 ""
-"Volume adalah perangkat penyimpanan blok yang Anda hubungkan ke instance "
-"untuk mengaktifkan penyimpanan persisten. Anda dapat pasangkan volume untuk "
-"instance menjalankan atau melepaskan volume dan pasangkan ke instance lain "
-"setiap saat. Anda juga dapat membuat snapshot dari atau menghapus volume. "
-"Hanya pengguna administratif dapat membuat tipe volume."
-
-msgid ""
-"We strongly recommend that you put non-current objects in a different "
-"container than the container where current object versions reside."
-msgstr ""
-"Kami sangat menyarankan agar Anda menaruh objek non-current dalam kontainer "
-"berbeda dari kontainer dimana versi objek saat berada."
-
-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 ""
-"Ketika Object Storage memproses permintaan, ia melakukan beberapa sub-"
-"operasi. Bahkan jika semua sub-operasi gagal, operasi mengembalikan status "
-"200. Operasi massal mengembalikan response body yang berisi rincian yang "
-"menunjukkan yang sub-operasi telah berhasil dan gagal. Beberapa sub-operasi "
-"mungkin berhasil sementara yang lain gagal. Periksa response body untuk "
-"menentukan hasil setiap sub-operasi penghapusan."
-
-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 ""
-"Ketika Object Storage memproses permintaan, ia melakukan beberapa sub-"
-"operasi. Bahkan jika semua sub-operasi gagal, operasi mengembalikan status "
-"``Created`` 201. Beberapa sub-operasi mungkin berhasil sementara yang lain "
-"gagal. Periksa respon body untuk menentukan hasil setiap sub-operation arsip "
-"auto-extract "
-
-msgid ""
-"When adding a rule, you must specify the protocol used with the destination "
-"port or source port."
-msgstr ""
-"Ketika menambahkan aturan, Anda harus menentukan protokol akan digunakan "
-"dengan port tujuan atau port sumber."
-
-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 ""
-"Ketika sebuah Instance dibuat dalam OpenStack, maka secara otomatis diberi "
-"alamat IP tetap dalam jaringan dimana Instance ditugaskan. Alamat IP ini "
-"secara permanen terkait dengan Instance sampai Instance diakhiri."
-
-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 ""
-"Ketika sebuah instance dibuat dalam OpenStack, maka secara otomatis diberi "
-"alamat IP tetap dalam jaringan dimana instance ditugaskan. Alamat IP ini "
-"secara permanen terkait dengan instance sampai instance diakhiri. Namun, "
-"selain alamat IP tetap, alamat IP mengambang juga dapat dihubungkan ke "
-"sebuah instance. Tidak seperti alamat IP tetap, alamat IP mengambang dapat "
-"memiliki asosiasi nya yang dapat diubah setiap saat, terlepas dari keadaan "
-"instance yang terlibat."
-
-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 ""
-"Ketika membuat sebuah port, Anda dapat menentukan IP yang tidak terisi di "
-"subnet bahkan jika alamat tidak ada di kolam yang telah ditentukan (pre-"
-"defined pool) dari alamat IP dialokasikan (ditetapkan oleh penyedia cloud "
-"Anda)."
-
-msgid ""
-"When running QEMU without support for the hardware virtualization, set "
-"``cpu_mode=\"none\"`` alongside ``virt_type=qemu`` in ``/etc/nova/nova-"
-"compute.conf`` to solve the following error:"
-msgstr ""
-"Saat menjalankan QEMU tanpa dukungan untuk virtualisasi perangkat keras, "
-"atur ``cpu_mode = \"none\" `` di samping ``virt_type = qemu`` di ``/etc/nova/"
-"nova-compute.conf`` untuk mengatasi kesalahan berikut:"
-
-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 ""
-"Ketika operasi ``PUT`` melihat parameter query ``?multipart-manifest = "
-"put``, itu membaca request body dan memverifikasi bahwa setiap objek segmen "
-"ada, dan bahwa ukuran dan ETag cocok. Jika ada ketidakcocokan, operasi "
-"``PUT`` gagal."
-
-msgid ""
-"When the latest module was created, the ``--include_clustered`` was not "
-"used. Use the :command:`trove module-reapply` command:"
-msgstr ""
-"Saat modul terbaru dibuat, ``--include_clustered`` tidak digunakan. Gunakan "
-"perintah :command:`trove module-reapply`:"
-
-msgid "When the resize completes, the status becomes VERIFY\\_RESIZE."
-msgstr "Ketika mengubah ukuran selesai, status menjadi VERIFY\\_RESIZE."
-
-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:`openstack console url "
-"show` command can be used with it, as well, by returning a token-"
-"authenticated address, as in the example above."
-msgstr ""
-"Bila menggunakan SPICE untuk melihat konsol instance, sebuah plugin browser "
-"dapat digunakan langsung pada halaman instance, atau perintah :command:"
-"`openstack console url show` dapat digunakan dengan itu, juga, dengan "
-"kembali (returning) alamat token-authenticated, seperti dalam contoh di atas."
-
-msgid ""
-"When using the SDK, you must authenticate against an OpenStack endpoint "
-"before you can use OpenStack services. Because all projects use Keystone for "
-"authentication, the process is the same no matter which service or library "
-"you have decided to use. Each library also has more advanced and complicated "
-"ways to do things, should those be needed."
-msgstr ""
-"Bila menggunakan SDK, Anda harus mengotentikasi terhadap titik akhir "
-"(endpoint) OpenStack sebelum Anda dapat menggunakan layanan OpenStack. "
-"Karena semua proyek menggunakan Keystone untuk otentikasi, proses berjalan "
-"sama tidak peduli dengan layanan atau perpustakaan dimana Anda telah "
-"memutuskan untuk menggunakan. Setiap perpustakaan juga memiliki cara yang "
-"lebih canggih dan rumit untuk melakukan hal-hal, bila mereka itu dibutuhkan."
-
-msgid ""
-"When working with images in the SDK, you will call ``novaclient`` methods."
-msgstr ""
-"Ketika bekerja dengan image di SDK, Anda akan memanggil metode "
-"``novaclient``."
-
-msgid ""
-"When working with images in the SDK, you will call both ``glance`` and "
-"``nova`` methods."
-msgstr ""
-"Ketika bekerja dengan image di SDK, Anda akan memanggil metode ``glance`` "
-"dan ``nova``."
-
-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 ""
-"Bila Anda membuat node bare-metal, alamat PM Anda, nama pengguna, dan "
-"password harus sesuai dengan informasi dalam konfigurasi BIOS/IPMI hardware "
-"Anda."
-
-msgid ""
-"When you create a database instance, you must specify a nova flavor. The "
-"flavor indicates various characteristics of the instance, such as RAM and "
-"root volume size. You will need to create or obtain new nova flavors that "
-"work for databases."
-msgstr ""
-"Ketika Anda membuat sebuah instance database, Anda harus menentukan flavor "
-"nova. Flavor menunjukkan berbagai karakteristik instance, seperti ukuran RAM "
-"dan root volume. Anda akan perlu membuat atau mendapatkan flavors nova baru "
-"yang bekerja untuk database."
-
-msgid ""
-"When you create a replica, do not specify the ``--users`` or ``--databases`` "
-"options."
-msgstr ""
-"Bila Anda membuat replika, jangan menentukan opsi ``--users`` atau ``--"
-"databases``."
-
-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 ""
-"Bila Anda membuat image yang mengakses drive data konfigurasi dan beberapa "
-"direktori berada di bawah direktori ``openstack``, selalu pilih versi API "
-"tertinggi pada tanggal tersebut konsumen Anda mendukung. Misalnya, jika "
-"image guest Anda mendukung 2012/03/05, 2012/08/05, dan 2013/04/13 versi, "
-"cobalah petram 2013/04/13 dan jatuh kembali ke versi sebelumnya jika "
-"2013/04/13 adalah tidak hadir."
-
-msgid "When you delete a stack, you cannot undo this action."
-msgstr ""
-"Ketika Anda menghapus stack, Anda tidak dapat membatalkan tindakan ini."
-
-msgid ""
-"When you delete an instance, the data in its attached volumes is not deleted."
-msgstr ""
-"Ketika Anda menghapus sebuah instance, data dalam volume yang melekat tidak "
-"dihapus."
-
-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 ""
-"Ketika Anda memulai mesin virtual, Anda dapat menyuntikkan *key pair*, yang "
-"menyediakan akses SSH untuk instance Anda. Untuk ini untuk bekerja, image "
-"harus berisi paket ``cloud-init``."
-
-msgid "When you launch an instance from a volume, note the following steps:"
-msgstr ""
-"Ketika Anda memulai sebuah instance dari volume, perhatikan langkah berikut:"
-
-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 ""
-"Ketika Anda memulai sebuah instance dari sebuah image, OpenStack membuat "
-"copy lokal dari image pada node komputasi dimana instance dimulai."
-
-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 ""
-"Ketika Anda memulai sebuah instance, maka secara otomatis diberi alamat IP "
-"pribadi yang tetap sama sampai Anda secara eksplisit mengakhiri instance. "
-"Reboot instance tidak berpengaruh pada alamat IP pribadi."
-
-msgid "When you no longer need an instance, you can delete it."
-msgstr "Bila Anda tidak perlu lagi sebuah instance, Anda dapat menghapusnya."
-
-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 ""
-"Ketika Anda meminta daftar kontainer atau objek, Object Storage "
-"mengembalikan maksimum 10.000 nama untuk setiap permintaan. Untuk "
-"mendapatkan nama berikutnya, Anda harus membuat permintaan lain dengan "
-"parameter ``marker``. Mengatur parameter ``marker`` dengan nama item "
-"terakhir kembali dalam daftar sebelumnya. Anda harus URL-encode nilai "
-"``marker`` sebelum Anda mengirim permintaan HTTP. Object Storage "
-"mengembalikan maksimum 10.000 nama akan memulai setelah item terakhir "
-"kembali."
-
-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 ""
-"Ketika Anda meng-upload setiap segmen dan manifes, masukkan nilai yang sama "
-"dalam header permintaan (request) ``X-Trans-Id-Extra`` . Jika terjadi "
-"kesalahan, Anda dapat menemukan semua permintaan yang berhubungan dengan "
-"upload objek besar di log Object Storage."
-
-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 ""
-"Dimana ``length`` adalah 3 karakter, panjang karakter heksadesimal zero-"
-"padded dari objek, `` `` adalah nama objek, dan `` "
-"`` adalah waktu ketika objek itu awalnya diciptakan sebagai versi saat ini."
-
-msgid ""
-"While static and dynamic objects have similar behavior, this table describes "
-"their differences:"
-msgstr ""
-"Sementara objek statis dan dinamis memiliki perilaku yang sama, tabel ini "
-"menggambarkan perbedaan mereka:"
-
-msgid "Who should read this book?"
-msgstr "Siapa yang harus membaca buku ini?"
-
-msgid ""
-"With bulk delete, you can delete up to 10,000 objects or containers "
-"(configurable) in one request."
-msgstr ""
-"Dengan penghapusan massal, Anda dapat menghapus hingga 10.000 objek atau "
-"kontainer (dikonfigurasi) dalam satu permintaan."
-
-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 ""
-"Dengan opsi ini, Anda dapat boot dari image dan membuat volume dengan "
-"memasukkan :guilabel:`Device Size` dan :guilabel:`Device Name` untuk volume "
-"Anda. Klik opsi :guilabel:`Delete Volume on Instance Delete` untuk menghapus "
-"volume pada penghapusan instance."
-
-msgid "X-Delete-After"
-msgstr "X-Delete-After"
-
-msgid "X-Delete-At"
-msgstr "X-Delete-At"
-
-msgid "XML data serialization response format."
-msgstr "Format respon serialisasi data XML"
-
-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 ""
-"Anda juga membuat dan mengunggah file manifest. File manifest file nol-byte "
-"dengan tambahan header ``X-Object-Manifest`` ``CONTAINER/PREFIX``. "
-"``CONTAINER`` adalah kontainer dimana segmen objek berada di dalamnya, dan "
-"`` PREFIX`` adalah awalan umum untuk semua segmen. Anda harus utf-8-encode "
-"dan kemudian URL-encode kontainer dan awalan umum di header ``X-Object-"
-"Manifest``."
-
-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 ""
-"Anda juga memiliki pilihan untuk menampilkan daftar file dalam pseudo-"
-"direktori Anda bukan sebuah halaman web. Untuk melakukan hal ini, aturlah "
-"header ``X-Container-Meta-Web-Listings`` ke ``TRUE``. Anda dapat menambahkan "
-"gaya ke file daftar Anda dengan pengaturan ``X-Container-Meta-Web-Listings-"
-"CSS`` ke style sheet (misalnya, ``lists.css``)."
-
-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 ""
-"Anda juga dapat menetapkan alamat IP mengambang ke instance yang menjalankan "
-"supaya dapat diakses dari luar cloud. Lihat :doc:`cli-manage-ip-addresses`."
-
-msgid ""
-"You can also attach a block storage device, or **volume**, for persistent "
-"storage."
-msgstr ""
-"Anda juga dapat menghubungkan (attach) perangkat penyimpanan blok, atau "
-"**volume**, untuk penyimpanan persisten."
-
-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 ""
-"Anda juga dapat mengkonfigurasi layanan Compute untuk selalu membuat drive "
-"konfigurasi dengan menetapkan opsi berikut di file ``/etc/nova/nova.conf``:"
-
-msgid ""
-"You can also filter the image list by using :command:`grep` to find a "
-"specific image, as follows:"
-msgstr ""
-"Anda juga dapat menyaring daftar image dengan menggunakan :command:`grep` "
-"untuk menemukan image tertentu, sebagai berikut:"
-
-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 ""
-"Anda juga dapat meluncurkan sebuah instance dari kategori :guilabel:"
-"`Images` atau :guilabel:`Volumes` ketika Anda memulai sebuah instance dari "
-"sebuah image atau volume masing-masing."
-
-msgid ""
-"You can also place arbitrary local files into the instance file system at "
-"creation time by using the ``--file `` option. You can "
-"store up to five files. For example, if you have a special authorized keys "
-"file named ``special_authorized_keysfile`` that you want to put on the "
-"instance rather than using the regular SSH key injection, you can use the "
-"``--file`` option as shown in the following example."
-msgstr ""
-"Anda juga dapat menempatkan file lokal sembarang tempat ke dalam sistem file "
-"instance pada waktu pembuatan dengan menggunakan opsi ``--file ``. Anda dapat menyimpan hingga lima file. Misalnya, jika Anda memiliki "
-"file authorized keys khusus bernama ``special_authorized_keysfile`` dimana "
-"Anda ingin menempatkan pada instance daripada menggunakan injeksi kunci SSH "
-"biasa, Anda dapat menggunakan opsi ``--file`` seperti yang ditunjukkan dalam "
-"contoh berikut."
-
-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 ""
-"Anda juga dapat menggunakan string ``X-Trans-Id-Extra`` membantu permintaan "
-"operator debug yang gagal untuk menerima tanggapan. operator dapat mencari "
-"informasi tambahan di log."
-
-msgid ""
-"You can also use the :command:`openstack` and :command:`glance` command-line "
-"clients or the Image service to manage images. For more information see :doc:"
-"`../common/cli-manage-images`."
-msgstr ""
-"Anda juga dapat menggunakan command-line client :command:`openstack` dan :"
-"command:`glance` atau layanan Image untuk mengelola images. Untuk informasi "
-"lebih lanjut lihat :doc:`../common/cli-manage-images`."
-
-msgid ""
-"You can also use the :command:`swift stat` command with the ``ACCOUNT`` or "
-"``CONTAINER`` names as parameters."
-msgstr ""
-"Anda juga dapat menggunakan perintah :command:`swift stat` dengan nama "
-"``ACCOUNT`` atau ``CONTAINER`` sebagai parameter."
-
-msgid ""
-"You can also use the ``--dry-run`` option with the :command:`openstack stack "
-"create` command to validate a template file without creating a stack from it."
-msgstr ""
-"Anda juga dapat menggunakan opsi ``--dry-run`` dengan perintah :command:"
-"`openstack stack create` untuk memvalidasi file template tanpa membuat "
-"stack (tumpukan) dari itu."
-
-msgid ""
-"You can apply a configuration group to hundreds or thousands of database "
-"instances in your environment."
-msgstr ""
-"Anda dapat menerapkan kelompok konfigurasi untuk ratusan atau ribuan "
-"instance database di lingkungan Anda."
-
-msgid "You can assign a floating IP address to a project and to an instance."
-msgstr ""
-"Anda dapat menetapkan alamat IP mengambang untuk proyek dan untuk sebuah "
-"instance."
-
-msgid "You can boot instances from a volume instead of an image."
-msgstr "Anda dapat boot instance dari volume bukan image."
-
-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 ""
-"Anda dapat mengubah konfigurasi database dengan menghubungkan (attaching) "
-"kelompok konfigurasi untuk instance database. Anda melakukan ini dengan "
-"menggunakan perintah :command:`trove configuration-attach` dan lewatkan di "
-"ID dari database instance dan ID dari kelompok konfigurasi."
-
-msgid ""
-"You can change various characteristics of a database instance, such as its "
-"volume size and flavor."
-msgstr ""
-"Anda dapat mengubah berbagai karakteristik instance database, seperti ukuran "
-"volume dan flavor."
-
-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 ""
-"Anda dapat memilih volume atau flavor yang lebih kecil untuk replika "
-"daripada aslinya, tetapi volume replika ini harus cukup besar untuk "
-"menampung snapshot data dari aslinya."
-
-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 ""
-"Anda dapat mengkonfigurasi OpenStack untuk menulis metadata ke drive "
-"konfigurasi khusus yang melekat pada instance ketika boot. Instance dapat me-"
-"mount drive ini dan membaca file itu untuk mendapatkan informasi yang "
-"biasanya tersedia melalui `metadata service `__. Metadata ini "
-"berbeda dari data pengguna."
-
-msgid ""
-"You can continue to upload segments, like this example shows, before you "
-"upload the manifest."
-msgstr ""
-"Anda dapat terus meng-upload segmen, seperti yang ditunjukkan contoh ini, "
-"sebelum Anda meng-upload manifes."
-
-msgid ""
-"You can count the instances each module is applied to by doing the following:"
-msgstr ""
-"Anda dapat menghitung instance setiap modul yang diterapkan dengan melakukan "
-"hal berikut:"
-
-msgid ""
-"You can create a configuration group by using the :command:`trove "
-"configuration-create` command. The general syntax for this command is:"
-msgstr ""
-"Anda dapat membuat kelompok konfigurasi dengan menggunakan perintah :command:"
-"`trove configuration-create`. Sintaks umum untuk perintah ini adalah:"
-
-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 ""
-"Anda dapat membuat objek baru dalam kontainer tanpa file yang tersedia dan "
-"dapat meng-upload file kemudian waktu ketika file sudah siap. Objek "
-"sementara ini bertindak place-holder untuk objek baru, dan memungkinkan "
-"pengguna untuk berbagi metadata objek dan info URL pada waktu sebelumnya."
-
-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 ""
-"Anda dapat membuat replika dari sebuah instance database yang ada. Ketika "
-"Anda membuat perubahan selanjutnya ke instance asli, sistem secara otomatis "
-"menerapkan perubahan untuk replika."
-
-msgid ""
-"You can create a test module and mysql database with the module applied by "
-"doing the following:"
-msgstr ""
-"Anda bisa membuat test module dan database mysql dengan modul yang "
-"diaplikasikan dengan melakukan hal berikut:"
-
-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 ""
-"Anda dapat membuat volume dari sebuah image, volume, atau snapshot yang ada. "
-"Prosedur ini menunjukkan Anda bagaimana untuk membuat volume dari sebuah "
-"image, dan menggunakan volume untuk boot sebuah instance."
-
-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 ""
-"Anda dapat membuat jumlah yang tidak terbatas pseudo-directory bersarang. "
-"Untuk menavigasi melalui mereka, gunakan lebih panjang parameter ``prefix`` "
-"ditambah dengan parameter ``delimiter``. Dalam contoh output ini, ada pseudo-"
-"directory yang disebut ``dogs`` dalam pseudo-directory ``animals``. Untuk "
-"menavigasi langsung ke file yang terdapat dalam ``dogs``, masukkan perintah "
-"berikut:"
-
-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 ""
-"Anda dapat membuat dan mengatur halaman kesalahan kustom untuk pengunjung ke "
-"website Anda; Saat ini, hanya kesalahan 401 (Unauthorized/tak sah) dan 404 "
-"(Tidak Ditemukan/Not Found) yang didukung. Untuk melakukan hal ini, aturlah "
-"header metadata, ``X-Container-Meta-Web-Error``."
-
-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 ""
-"Anda dapat membuat setidaknya satu sepasang kunci (key pair) untuk setiap "
-"proyek. Anda dapat menggunakan sepasang kunci untuk beberapa instance yang "
-"tergabung dalam proyek itu. Jika Anda menghasilkan pasangan kunci dengan "
-"alat eksternal, Anda dapat mengimpor ke OpenStack."
-
-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 ""
-"Anda dapat memperbesar volume dengan menggunakan opsi tersedia :guilabel:"
-"`Extend Volume` dalam daftar dropdown :guilabel:`More` dan memasukkan nilai "
-"baru untuk ukuran volume."
-
-msgid "You can generate a key pair or upload an existing public key."
-msgstr ""
-"Anda dapat menghasilkan sepasang kunci atau meng-upload kunci publik (public "
-"key) yang ada."
-
-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 ""
-"Anda bisa mendapatkan informasi tambahan tentang backup (cadangan) dengan "
-"menggunakan perintah :command:`trove backup-show` dan melewat ``BACKUP_ID``, "
-"dimana ``8af30763-61fd-4aab-8fe8-57d528911138``."
-
-msgid "You can launch an instance from various sources."
-msgstr "Anda dapat memulai sebuah instance dari berbagai sumber."
-
-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 ""
-"Anda bisa daftar dan menghapus node bare-metal. Ketika Anda menghapus sebuah "
-"node, setiap antarmuka jaringan yang terkait akan dihapus. Anda bisa daftar "
-"dan menghapus antarmuka jaringan yang terkait dengan node bare-metal."
-
-msgid ""
-"You can list the instances that have a particular module applied by doing "
-"the following:"
-msgstr ""
-"Anda dapat mencantumkan instance yang memiliki modul tertentu yang "
-"diterapkan dengan melakukan hal berikut:"
-
-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 ""
-"Anda dapat mengelola tugas konfigurasi database dengan menggunakan kelompok "
-"konfigurasi. Kelompok konfigurasi memungkinkan Anda mengatur opsi "
-"konfigurasi, dalam jumlah besar, pada satu atau lebih database."
-
-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 ""
-"Anda dapat memodifikasi aturan dalam kelompok keamanan untuk memungkinkan "
-"akses ke instance melalui port yang berbeda dan protokol. Misalnya, Anda "
-"dapat mengubah aturan untuk memungkinkan akses ke instance melalui SSH, ping "
-"instance, atau untuk mengizinkan traffic UDP; misalnya, untuk server DNS "
-"berjalan pada sebuah instance. Anda menentukan parameter berikut untuk "
-"aturan:"
-
-msgid "You can modify these examples for your specific use cases."
-msgstr ""
-"Anda dapat mengubah contoh tersebut untuk kasus penggunaan spesifik Anda."
-
-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 ""
-"Anda sekarang dapat mengakses database baru yang baru saja dibuat (myDB) "
-"dengan menggunakan perintah akses database tipikal. Dalam contoh MySQL ini, "
-"menggantikan ``IP_ADDRESS`` dengan ``172.16.200.2``."
-
-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 ""
-"Anda sekarang dapat melewatkan instance ID dengan perintah :command:`trove "
-"show` untuk mendapatkan alamat IP dari instance. Dalam instance ini, "
-"gantikan ``INSTANCE_ID`` dengan ``5599dad6-731e-44df-bb60-488da3da9cfe``."
-
-msgid ""
-"You can only assign these headers to objects. For more information, see `www."
-"w3.org/TR/access-control/ `__."
-msgstr ""
-"Anda hanya dapat menetapkan header ini ke objek. Untuk informasi lebih "
-"lanjut, lihat `www.w3.org/TR/access-control/ `__."
-
-msgid ""
-"You can pass user data in a local file at instance launch by using the ``--"
-"user-data USER-DATA-FILE`` parameter."
-msgstr ""
-"Anda dapat melewatkan data pengguna dalam file lokal di peluncuran instance "
-"dengan menggunakan parameter ``--user-data USER-DATA-FILE``."
-
-msgid ""
-"You can place user data in a local file and pass it through the ``--user-"
-"data `` parameter at instance creation."
-msgstr ""
-"Anda dapat menempatkan data user dalam file lokal dan menyebarkannya melalui "
-"parameter ``--user-data `` di pembuatan instance."
-
-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 ""
-"Anda dapat mengubah ukuran atau membangun kembali sebuah instance. Anda juga "
-"dapat memilih untuk melihat log konsol instance, mengedit instance atau "
-"kelompok keamanan. Tergantung pada keadaan saat ini instance, Anda dapat "
-"menghentikan sebentar, melanjutkan, menangguhkan, reboot lembut atau keras, "
-"atau mengakhiri itu."
-
-msgid "You can run the following shelving tasks:"
-msgstr "Anda dapat menjalankan tugas peletakan (shelving) berikut:"
-
-msgid ""
-"You can schedule Object Storage (swift) objects to expire by setting the ``X-"
-"Delete-At`` or ``X-Delete-After`` header. Once the object is deleted, swift "
-"will no longer serve the object and it will be deleted from the cluster "
-"shortly thereafter."
-msgstr ""
-"Anda dapat menjadwalkan obyek dari Object Storage (swift) berakhir dengan "
-"menetapkan header ``X-Delete-At`` atau ``X-Delete-After``. Setelah objek "
-"dihapus, swift tidak akan lagi melayani objek dan akan dihapus dari cluster "
-"tidak lama kemudian."
-
-msgid ""
-"You can search for an instance using the IP address parameter, ``--ip``, "
-"with the :command:`openstack server list` command."
-msgstr ""
-"Anda dapat mencari instance menggunakan parameter alamat IP, ``--ip``, "
-"dengan perintah :command:`openstack server list`."
-
-msgid ""
-"You can set the ``Accept`` request header to one of the following values to "
-"define the response format:"
-msgstr ""
-"Anda dapat mengatur request header ``Accept`` ke salah satu nilai berikut "
-"untuk menentukan format respon:"
-
-msgid ""
-"You can set the ``Accept`` request header to one of these values to define "
-"the response format:"
-msgstr ""
-"Anda dapat mengatur header permintaan ``Accept`` ke salah satu nilai ini "
-"untuk menentukan format respon:"
-
-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 ""
-"Anda dapat reboot lembut atau keras dalam menjalankan instance. A reboot "
-"lembut mencoba shutdown anggun dan restart instance. Sebuah daya reboot "
-"keras memutar instance."
-
-msgid ""
-"You can specify a MAC address with ``--mac-address MAC_ADDRESS``. If you "
-"specify an invalid MAC address, including ``00:00:00:00:00:00`` or ``ff:ff:"
-"ff:ff:ff:ff``, you will get an error."
-msgstr ""
-"Anda dapat menentukan alamat MAC dengan ``--mac-address MAC_ADDRESS``. Jika "
-"Anda menentukan alamat MAC yang tidak valid, termasuk ``00:00:00:00:00:00`` "
-"atau ``ff:ff:ff:ff:ff:ff``, Anda akan mendapatkan error."
-
-msgid ""
-"You can store data across multiple machines by setting up MongoDB sharded "
-"clusters."
-msgstr ""
-"Anda dapat menyimpan data di beberapa mesin dengan pengaturan kluster "
-"sharded MongoDB ."
-
-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 ""
-"Anda dapat menyimpan beberapa versi dari konten Anda sehingga Anda dapat "
-"pulih dari timpaan yang tidak diinginkan. Objek versi adalah cara mudah "
-"untuk menerapkan kontrol versi, yang dapat Anda gunakan dengan semua tipe "
-"konten."
-
-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 ""
-"Anda dapat melacak penggunaan instance untuk setiap proyek. Anda dapat "
-"melacak biaya per bulan dengan menunjukkan meter seperti jumlah vCPUs, disk, "
-"RAM, dan uptime untuk semua instance Anda."
-
-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 ""
-"Anda dapat meng-upload manifest dan segmen objek dalam urutan apapun. Anda "
-"dianjurkan untuk meng-upload objek nyata setelah segmen dalam kasus download "
-"prematur manifes terjadi. Namun, hal ini tidak ditegakkan (not enforced)."
-
-msgid ""
-"You can upload new segment objects or remove existing segments. The names "
-"must simply match the ``PREFIX`` supplied in ``X-Object-Manifest``."
-msgstr ""
-"Anda dapat meng-upload object segmen baru atau menghapus segmen yang ada. "
-"Nama harus sungguh sesuai dengan ``PREFIX`` disediakan di ``X-Object-"
-"Manifest``."
-
-msgid ""
-"You can upload regular files but you cannot upload other items (for example, "
-"empty directories or symbolic links)."
-msgstr ""
-"Anda dapat meng-upload file biasa tetapi Anda tidak dapat meng-upload item "
-"lainnya (misalnya, direktori kosong atau link simbolik)."
-
-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 ""
-"Anda dapat menggunakan layanan database untuk backup (cadangan) database dan "
-"menyimpan artefak cadangan dalam pelayanan Object Storage. Kemudian, jika "
-"database asli rusak, Anda dapat menggunakan artefak cadangan untuk "
-"mengembalikan database. Proses pemulihan menciptakan instance database."
-
-msgid "You can use ``python-swiftclient`` to easily upload large objects."
-msgstr "You can use ``python-swiftclient`` to easily upload large objects."
-
-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 ""
-"Anda dapat menggunakan perintah :command:`blkid` untuk mengidentifikasi "
-"perangkat blok yang sesuai dengan drive konfigurasi. Misalnya, ketika anda "
-"boot image CirrOS dengan flavor ``m1.tiny``, perangkat ``/dev/vdb``:"
-
-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 ""
-"Anda dapat menggunakan header permintaan (request) ``X-Trans-Id-Extra`` "
-"untuk memasukkan informasi tambahan untuk membantu Anda debug kesalahan yang "
-"mungkin terjadi dengan meng-upload objek besar dan transaksi Object Storage "
-"lainnya."
-
-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 ""
-"Anda dapat menggunakan akun Object Storage Anda untuk membuat website "
-"statis. Website statis ini dibuat dengan Static Web middleware dan melayani "
-"data kontainer dengan file indek tertentu, resolusi file error, dan daftar "
-"file opsional. Mode ini biasanya hanya aktif untuk request (permintaan) "
-"anonim, yang tidak memberikan token otentikasi. Untuk menggunakannya dengan "
-"permintaan dikonfirmasi (authenticated request), aturlah header ``X-Web-"
-"Mode`` ke ``TRUE`` pada permintaan."
-
-msgid "You can utilize ``python-swiftclient`` to enable object versioning."
-msgstr "You can utilize ``python-swiftclient`` to enable object versioning."
-
-msgid "You can view rules for a specified security group:"
-msgstr ""
-"Anda dapat melihat aturan untuk kelompok keamanan tertentu (specified):"
-
-msgid "You can view the modules on your instance by doing the following:"
-msgstr ""
-"Anda dapat melihat modul di instance Anda dengan melakukan hal berikut:"
-
-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 ""
-"Anda dapat melihat status volume di tab Volume dashboard. Volume menunjukkan "
-"Available ataupun In-Use."
-
-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 ""
-"Anda tidak dapat menambah atau menghapus objek segmen dari manifes. Namun, "
-"Anda dapat membuat objek nyata (manifest) benar-benar baru dengan nama yang "
-"sama dengan daftar manifest yang berbeda."
-
-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 ""
-"Anda tidak dapat menghapus kelompok keamanan default untuk sebuah proyek. "
-"Juga, Anda tidak dapat menghapus kelompok keamanan yang ditugaskan untuk "
-"instance menjalankan."
-
-msgid ""
-"You cannot version a large-object manifest file, but the large-object "
-"manifest file can point to versioned segments."
-msgstr ""
-"Anda tidak bisa memversi file manifest large-object, tapi file manifest "
-"large-object dapat menunjuk ke segmen berversi."
-
-msgid "You detach a replica using the :command:`trove detach-replica` command:"
-msgstr ""
-"Anda melepaskan replika menggunakan perintah :command:`trove detach-replica`:"
-
-msgid ""
-"You do not have to specify a subnet when you create a network, but if you do "
-"not specify a subnet, the network can not be attached to an instance."
-msgstr ""
-"Anda tidak harus menentukan subnet ketika Anda membuat jaringan, tetapi jika "
-"Anda tidak menentukan subnet, jaringan tidak dapat dihubungkan ke sebuah "
-"instance."
-
-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 ""
-"Anda mendapatkan daftar dengan semua volume dalam sistem Anda. Dalam daftar "
-"ini, Anda dapat menemukan volume yang melekat pada ISO Anda membuat "
-"instance, dengan properti bootable palsu."
-
-msgid "You have successfully created a container."
-msgstr "Anda telah berhasil membuat sebuah wadah (container)."
-
-msgid ""
-"You have successfully created the router. You can view the new topology from "
-"the :guilabel:`Network Topology` tab."
-msgstr ""
-"Anda telah berhasil membuat router. Anda dapat melihat topologi baru dari "
-"tab :guilabel:`Network Topology`."
-
-msgid "You have successfully uploaded an object to the container."
-msgstr "Anda telah berhasil mengunggah sebuah objek untuk wadah."
-
-msgid "You must UTF-8-encode the member names."
-msgstr "Anda harus utf-8-encode nama anggota."
-
-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 ""
-"Anda harus mencatat nilai header respon ``ETag`` dimana pengembalian "
-"operation ``PUT``. Atau, Anda dapat menghitung checksum MD5 dari segmen "
-"sebelum Anda melakukan upload dan termasuk nilai ini dalam header permintaan "
-"``ETag``. Tindakan ini memastikan bahwa upload tidak dapat merusak data Anda."
-
-msgid "You must upload the segment objects before upload the manifest object."
-msgstr ""
-"Anda harus meng-upload benda segmen sebelum meng-upload objek nyata "
-"(manifest)."
-
-msgid "You must use the tar utility to create the tar archive file."
-msgstr "Anda harus menggunakan tar utility untuk membuat file arsip tar."
-
-msgid ""
-"You need the Block Storage service to preserve the instance after shutdown. "
-"The ``--block-device`` argument, used with the legacy :command:`nova boot`, "
-"will not work with the OpenStack :command:`openstack server create` command. "
-"Instead, the :command:`openstack volume create` and :command:`openstack "
-"server add volume` commands create persistent storage."
-msgstr ""
-"You need the Block Storage service to preserve the instance after shutdown. "
-"The ``--block-device`` argument, used with the legacy :command:`nova boot`, "
-"will not work with the OpenStack :command:`openstack server create` command. "
-"Instead, the :command:`openstack volume create` and :command:`openstack "
-"server add volume` commands create persistent storage."
-
-msgid ""
-"You only have to set the ``X-Container-Meta-Web-Error`` metadata once for "
-"your entire static website."
-msgstr ""
-"Anda harus mengatur metadata ``X-Container-Meta-Web-Error`` hanya sekali "
-"untuk website Anda seluruh statis."
-
-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 ""
-"Anda menerima respon one-item, yang lebih sedikit daripada jumlah ``limit`` "
-"nama. Hal ini menunjukkan bahwa ini adalah akhir dari daftar."
-
-msgid ""
-"You receive a result set of all container names before the ``end-marker`` "
-"value."
-msgstr ""
-"Anda menerima hasil set semua nama kontainer sebelum nilai `end-marker``."
-
-msgid "You should also be familiar with:"
-msgstr "Anda juga harus akrab dengan:"
-
-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 ""
-"Anda menentukan bahwa baru instance ``guest2`` memiliki flavor yang sama "
-"(``10``) dan ukuran volume akar yang sama (``2``) seperti aslinya ``guest1`` "
-"instance."
-
-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 ""
-"Anda biasanya menulis kunci pribadi (private key) ke file untuk digunakan "
-"nanti. File harus dibaca dan ditulisi dengan hanya pemilik file; jika tidak, "
-"klien SSH akan menolak untuk membaca file kunci pribadi. Cara paling aman "
-"adalah dengan membuat file dengan hak akses yang sesuai, seperti yang "
-"ditunjukkan dalam contoh berikut:"
-
-msgid ""
-"You use the ``--backup`` argument to indicate that this new instance is "
-"based on the backup artifact identified by ``BACKUP_ID``. In this example, "
-"replace ``BACKUP_ID`` with ``8af30763-61fd-4aab-8fe8-57d528911138``."
-msgstr ""
-"Anda menggunakan argumen ``--backup`` untuk menunjukkan bahwa instance baru "
-"ini didasarkan pada artefak cadangan yang diidentifikasi oleh ``BACKUP_ID``. "
-"Dalam contoh ini, gantilah ``BACKUP_ID`` dengan "
-"``8af30763-61fd-4aab-8fe8-57d528911138``."
-
-msgid ""
-"Your Object Storage system might not enable all features that this document "
-"describes. These features are:"
-msgstr ""
-"Sistem Object Storage Anda mungkin tidak memungkinkan semua fitur yang "
-"dokumen ini menjelaskan. Fitur-fitur ini:"
-
-msgid "Your options are:"
-msgstr "Pilihan Anda adalah:"
-
-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 ""
-"Kontainer Anda yang terbaca publik diperiksa untuk dua header, ``X-Container-"
-"Meta-Web-Index`` dan ``X-Container-Meta-Web-Error``. Header ``X-Container-"
-"Meta-Web-Error`` dibahas di bawah ini, di bagian yang disebut :ref:"
-"`set_error_static_website`."
-
-msgid "``--flavor`` The flavor ID or name."
-msgstr "``--flavor`` The flavor ID or name."
-
-msgid ""
-"``--xvpvnc`` can be replaced by any of the above values as connection types."
-msgstr ""
-"``--xvpvnc`` dapat digantikan oleh salah satu nilai di atas sebagai tipe "
-"koneksi."
-
-msgid ""
-"```` is the name of the container to which you are uploading the "
-"object."
-msgstr "```` adalah nama dari wadah (container) yang Anda upload objek."
-
-msgid "``Accept`` request header"
-msgstr "``Accept`` request header"
-
-msgid "``NAME``. The name for the server."
-msgstr "``NAME``. Nama untuk server."
-
-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 ""
-"`` Segmen objects`` menyimpan konten objek. Anda dapat membagi konten Anda "
-"ke dalam segmen dan meng-upload setiap segmen ke objek segmen sendiri. "
-"Object segmen tidak memiliki fitur spesial. Anda membuat, memperbarui, "
-"download, dan menghapus objek segmen seperti yang Anda lakukan dengan object "
-"yang normal."
-
-msgid "``application/json``"
-msgstr "``application/json``"
-
-msgid "``application/xml``"
-msgstr "``application/xml``"
-
-msgid "``application/xml`` or ``text/xml``"
-msgstr "``application/xml`` atau ``text/xml``"
-
-msgid "``baremetal-interface-add``"
-msgstr "``baremetal-interface-add``"
-
-msgid "``baremetal-interface-list``"
-msgstr "``baremetal-interface-list``"
-
-msgid "``baremetal-interface-remove``"
-msgstr "``baremetal-interface-remove``"
-
-msgid "``baremetal-node-create``"
-msgstr "``baremetal-node-create``"
-
-msgid "``baremetal-node-delete``"
-msgstr "``baremetal-node-delete``"
-
-msgid "``baremetal-node-list``"
-msgstr "``baremetal-node-list``"
-
-msgid "``baremetal-node-show``"
-msgstr "``baremetal-node-show``"
-
-msgid ""
-"``clouds.yaml`` is a bit newer and was designed to help folks who have more "
-"than one OpenStack cloud that they are using."
-msgstr ""
-"``clouds.yaml`` adalah hal lebih baru sedikit dan dirancang untuk membantu "
-"orang yang memiliki lebih dari satu cloud OpenStack yang mereka gunakan."
-
-msgid "``database1``, ``database2``, ``database3``"
-msgstr "``database1``, ``database2``, ``database3``"
-
-msgid ""
-"``host`` is optional for the ``--availability-zone`` parameter. You can "
-"simply specify ``zone:,node``, still including the comma."
-msgstr ""
-"``host`` adalah opsional untuk parameter ``--availability-zone``. Anda hanya "
-"dapat menentukan ``zona:,node``, masih termasuk koma."
-
-msgid ""
-"``print_server`` is a method defined in ``utils.py`` and prints the server "
-"details as shown in the code listing below:"
-msgstr ""
-"``print_server`` adalah metode didefinisikan dalam ``utils.py`` dan mencetak "
-"rincian server seperti yang ditunjukkan di daftar kode di bawah ini:"
-
-msgid "``text/plain``"
-msgstr "``text/plain``"
-
-msgid "``text/xml``"
-msgstr "``text/xml``"
-
-msgid ""
-"`shade `_ is an abstraction library "
-"focused on hiding implementation differences between OpenStack clouds. While "
-"the OpenStack SDK presents a clean object interface to the underlying REST "
-"APIs, shade hides them if doing so is advantageous. If you plan on running "
-"the same Python program against many OpenStack clouds, you may want to use "
-"shade - but if you need to access any features of a cloud that do not have a "
-"cloud-neutral abstraction mapping, you will be unable to do so with shade."
-msgstr ""
-"`shade `_ adalah perpustakaan abstraksi "
-"berfokus pada penyembunyian perbedaan implementasi antara cloud OpenStack. "
-"Sementara OpenStack SDK menyajikan antarmuka objek bersih untuk REST API "
-"yang mendasarinya, shade menyembunyikan mereka jika melakukan hal ini "
-"menguntungkan. Jika Anda berencana untuk menjalankan program Python yang "
-"sama terhadap banyak cloud OpenStack, Anda mungkin ingin menggunakan shade - "
-"tetapi jika Anda perlu untuk mengakses semua fitur dari cloud yang tidak "
-"memiliki pemetaan abstraksi cloud-neutral, Anda tidak akan dapat "
-"melakukannya dengan shade."
-
-msgid "application/jsontext"
-msgstr "application/jsontext"
-
-msgid "application/xml"
-msgstr "application/xml"
-
-msgid "clouds.yaml config file"
-msgstr "File konfigurasi clouds.yaml "
-
-msgid "end_marker"
-msgstr "end_marker"
-
-msgid "etag"
-msgstr "etag"
-
-msgid "format= ``format`` query parameter"
-msgstr "format= ``format`` query parameter"
-
-msgid "http://packages.ubuntu.com/search?keywords=cloud-init"
-msgstr "http://packages.ubuntu.com/search?keywords=cloud-init"
-
-msgid ""
-"http://software.opensuse.org/download.html?project=Cloud"
-"%3ATools&package=cloud-init"
-msgstr ""
-"http://software.opensuse.org/download.html?project=Cloud"
-"%3ATools&package=cloud-init"
-
-msgid "https://www.rpmfind.net/linux/rpm2html/search.php?query=cloud-init"
-msgstr "https://www.rpmfind.net/linux/rpm2html/search.php?query=cloud-init"
-
-msgid "limit"
-msgstr "limit"
-
-msgid "marker"
-msgstr "marker"
-
-msgid "novnc"
-msgstr "novnc"
-
-msgid "openSUSE (SLE)"
-msgstr "openSUSE (SLE)"
-
-msgid "openstack server create parameter"
-msgstr "openstack server create parameter"
-
-msgid "path"
-msgstr "path"
-
-msgid "publicURL"
-msgstr "publicURL"
-
-msgid "shade"
-msgstr "shade"
-
-msgid "size_bytes"
-msgstr "size_bytes"
-
-msgid "spice"
-msgstr "spice"
-
-msgid "text/plain"
-msgstr "text/plain"
-
-msgid "text/xml"
-msgstr "text/xml"
-
-msgid "token"
-msgstr "token"
-
-msgid "xvpvnc"
-msgstr "xvpvnc"
diff --git a/doc/user-guide/source/locale/ja/LC_MESSAGES/user-guide.po b/doc/user-guide/source/locale/ja/LC_MESSAGES/user-guide.po
deleted file mode 100644
index e43848c7cb..0000000000
--- a/doc/user-guide/source/locale/ja/LC_MESSAGES/user-guide.po
+++ /dev/null
@@ -1,10229 +0,0 @@
-# SOME DESCRIPTIVE TITLE.
-# Copyright (C) 2015, OpenStack contributors
-# This file is distributed under the same license as the End User Guide package.
-#
-# Translators:
-# Akihiro Motoki , 2013
-# Andreas Jaeger , 2014
-# myamamot , 2014
-# nao nishijima , 2015
-# Tomoyuki KATO , 2013-2015
-# yfukuda , 2014
-# ykatabam , 2014
-# Akihiro Motoki , 2015. #zanata
-# KATO Tomoyuki , 2015. #zanata
-# OpenStack Infra , 2015. #zanata
-# Yuta Hono , 2015. #zanata
-# Akihiro Motoki , 2016. #zanata
-# KATO Tomoyuki , 2016. #zanata
-# KATO Tomoyuki , 2017. #zanata
-msgid ""
-msgstr ""
-"Project-Id-Version: End User Guide 15.0\n"
-"Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2017-06-21 14:03+0000\n"
-"MIME-Version: 1.0\n"
-"Content-Type: text/plain; charset=UTF-8\n"
-"Content-Transfer-Encoding: 8bit\n"
-"PO-Revision-Date: 2017-03-22 02:37+0000\n"
-"Last-Translator: KATO Tomoyuki \n"
-"Language: ja\n"
-"Plural-Forms: nplurals=1; plural=0;\n"
-"X-Generator: Zanata 3.9.6\n"
-"Language-Team: Japanese\n"
-
-msgid "**Access the new database**"
-msgstr "**新しいデータベースへのアクセス**"
-
-msgid ""
-"**Assumptions.** Assume that you have created a regular backup for the "
-"following database instance:"
-msgstr ""
-"** 前提。** 以下のデータベースインスタンスのバックアップが作成されていること"
-"を仮定しています。"
-
-msgid "**Backup the database instance**"
-msgstr "**データベースインスタンスのバックアップ**"
-
-msgid "**Before you begin.** Make sure that:"
-msgstr "**始める前に** 以下を確認します。"
-
-msgid "**CIDR**: ``0.0.0.0/0``"
-msgstr "**CIDR**: ``0.0.0.0/0``"
-
-msgid "**Change the database configuration using a configuration group**"
-msgstr "**設定グループを用いたデータベース設定の変更**"
-
-msgid "**Clean up**"
-msgstr "**クリーンアップ**"
-
-msgid "**Compute host requirements**"
-msgstr "**コンピュートホストの要件**"
-
-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 ""
-"**結論。** 単一のオプションを単一のデータベースに設定するために、設定グループ"
-"を使用することは、明らかにささいな例です。しかしながら、設定グループは、以下"
-"を検討する際に大きな効果があります。"
-
-msgid "**Configure a default datastore.**"
-msgstr "**デフォルトのデータストアを設定します。**"
-
-msgid "**Create a cluster**"
-msgstr "**クラスターの作成**"
-
-msgid "**Create a configuration group**"
-msgstr "**設定グループの作成**"
-
-msgid "**Create a database instance**"
-msgstr "**データベースインスタンスの作成**"
-
-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 ""
-"**データベースインスタンスの作成。** デフォルトのデータストアを設定し、適切な"
-"フレーバーがきちんとあると、データベースインスタンスを作成できます。"
-
-msgid "**Create the replica**"
-msgstr "**レプリカの作成**"
-
-msgid "**Create your first incremental backup**"
-msgstr "**最初の増分バックアップの作成**"
-
-msgid "**Create your second incremental backup**"
-msgstr "**2 個目の増分バックアップの作成**"
-
-msgid "**Dashboard — Create Image**"
-msgstr "**ダッシュボード — イメージの作成**"
-
-msgid "**Delete a cluster**"
-msgstr "**クラスターの削除**"
-
-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 ""
-"**仮想マシンでの宛て先ポート番号**。ポートの範囲を定義します。ポート 1 つのみ"
-"を開くには、同じ値を 2 回入力します。ICMP はポートに対応していないため、許可"
-"する ICMP トラフィックのコードおよび種別を定義する値を代わりに入力します。"
-
-msgid "**Detach the replica**"
-msgstr "**複製の解除**"
-
-msgid "**Determine which flavor to use for your database**"
-msgstr "**データベースに使用するフレーバーの選択**"
-
-msgid "**Direction**: ``Ingress``"
-msgstr "**方向**: ``受信``"
-
-msgid "**Display cluster information**"
-msgstr "**クラスター情報の表示**"
-
-msgid "**Examine your existing configuration**"
-msgstr "**既存の設定の検査**"
-
-msgid "**Figure: Admin tab**"
-msgstr "**図: 管理タブ**"
-
-msgid "**Figure: Project tab**"
-msgstr "**図: プロジェクトタブ**"
-
-msgid "**Figure:Identity tab**"
-msgstr "**図: ユーザー管理タブ**"
-
-msgid "**Figure:Settings tab**"
-msgstr "**図: 設定タブ**"
-
-msgid "**Get the IP address of the database instance**"
-msgstr "**データベースインスタンスの IP アドレスの取得**"
-
-msgid "**Get the instance ID**"
-msgstr "**インスタンス ID の取得**"
-
-msgid "**Guidelines**"
-msgstr "**ガイドライン**"
-
-msgid "**Image requirements**"
-msgstr "**イメージの要件**"
-
-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 ""
-"**インスタンス名。** この名前は、複製セットの名前に -*n* を付けたものです。こ"
-"の *n* は、1 番目の複製セットが 1、2 番目が 2 と続きます。この例では、インス"
-"タンスの名前は ``cluster1-rs1-1``, ``cluster1-rs1-2``, ``cluster1-rs1-3`` に"
-"なります。"
-
-msgid "**List available options**"
-msgstr "**利用可能なオプションの一覧表示**"
-
-msgid "**List cluster instances**"
-msgstr "**クラスターインスタンスの一覧表示**"
-
-msgid "**List clusters**"
-msgstr "**クラスターの一覧表示**"
-
-msgid ""
-"**Maintenance.** There are also a number of useful maintenance features for "
-"working with configuration groups. You can:"
-msgstr ""
-"**メンテナンス。** 設定グループを用いて動作する、有用なメンテナンス機能がいろ"
-"いろとあります。以下を実行できます。"
-
-msgid ""
-"**MySQL example.** This example creates a flavor that you can use with a "
-"MySQL database. This example has the following attributes:"
-msgstr ""
-"**MySQL の例。** この例は MySQL データベースで使用できるフレーバーを作成しま"
-"す。この例は以下の属性を持ちます。"
-
-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 ""
-"**複製セットとインスタンスの命名規則。** 複製セットの名前を意味するインスタン"
-"ス名が ``Name`` 列に表示されることに注意してください。複製セットの名前とイン"
-"スタンス名は、以下のルールに従い、自動的に生成されます。"
-
-msgid "**Notify users**"
-msgstr "**ユーザーへの通知**"
-
-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 ""
-"**前提。** データベースインスタンスを作成する前に、デフォルトのデータストアを"
-"設定する必要があります。また、使用したいデータベースインスタンスの種類に応じ"
-"た適切なフレーバーが必ず必要になります。"
-
-msgid "**Protocol**. Choose TCP for SSH, ICMP for pings, or UDP."
-msgstr ""
-"**プロトコル**。SSH には TCP、ping には ICMP、あるいは UDP を選択します。"
-
-msgid "**Re-examine the database configuration**"
-msgstr "**データベース設定の再検査**"
-
-msgid "**Remote**: ``CIDR``"
-msgstr "**接続相手**: ``CIDR``"
-
-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 ""
-"**複製セットの名前。** この名前は、クラスターの名前に -rs\\ *n* を付けたもの"
-"です。この *n* は、1 番目の複製セットが 1、2 番目が 2 と続きます。この例で"
-"は、クラスターの名前が ``cluster1``、複製セットが 1 つだけあるので、複製セッ"
-"トの名前は ``cluster1-rs1`` になります。"
-
-msgid "**Restore a database instance**"
-msgstr "**データベースインスタンスのリストア**"
-
-msgid "**Restore using incremental backups**"
-msgstr "**増分バックアップを用いたリストア**"
-
-msgid "**Rule**: ``All ICMP``"
-msgstr "**ルール**: ``All ICMP``"
-
-msgid "**Rule**: ``SSH``"
-msgstr "**ルール**: ``SSH``"
-
-msgid ""
-"**Source of traffic**. Enable traffic to instances from either IP addresses "
-"inside the cloud from other group members or from all IP addresses."
-msgstr ""
-"**トラフィックソース**。クラウドの IP アドレスから、他のグループメンバーか"
-"ら、あるいは全 IP アドレスからインスタンスへのトラフィックを可能にします。"
-
-msgid "**To copy an object from one container to another**"
-msgstr "**コンテナーから別のコンテナーへのオブジェクトのコピー方法**"
-
-msgid "**To create a metadata-only object without a file**"
-msgstr "**ファイルなしのメタデータ専用オブジェクトの作成方法**"
-
-msgid "**To create a pseudo-folder**"
-msgstr "**擬似フォルダーの作成方法**"
-
-msgid "**To edit an object**"
-msgstr "**オブジェクトの編集方法**"
-
-msgid "**Verify backup**"
-msgstr "**バックアップの検証**"
-
-msgid "**Verify flavor.**"
-msgstr "**フレーバーを検証します。**"
-
-msgid "**Verify replication status**"
-msgstr "**複製状態の検証**"
-
-msgid ""
-"**Your application connects to this IP address.** The :command:`trove "
-"cluster-show` command displays the IP address of the query router. This is "
-"the IP address your application uses to retrieve data from the database."
-msgstr ""
-"**この IP アドレスに接続するアプリケーション。** :command:`trove cluster-"
-"show` コマンドにより、クエリールーターの IP アドレスを表示します。これは、ア"
-"プリケーションがデータベースからデータを取得するために使用する IP アドレスで"
-"す。"
-
-msgid "**avg**. The average of sample volumes over each period."
-msgstr "**平均**。各期間の平均サンプルボリューム数。"
-
-msgid "**count**. The number of samples in each period."
-msgstr "**数量**。各期間のサンプル数。"
-
-msgid "**max**. The maximum number of sample volumes in each period."
-msgstr "**最大**。各期間の最大サンプルボリューム数。"
-
-msgid "**min**. The minimum number of sample volumes in each period."
-msgstr "**最小**。各期間の最小サンプルボリューム数。"
-
-msgid "**sum**. The sum of sample volumes over each period."
-msgstr "**合計**。各期間の合計サンプルボリューム数。"
-
-msgid "*DATASTORE_NAME*. The name of the associated data store."
-msgstr "*DATASTORE_NAME*。関連付けたデータストアの名前。"
-
-msgid "*NAME*. The name you want to use for this group."
-msgstr "*NAME*。このグループに使用したい名前。"
-
-msgid "*VALUES*. The list of key-value pairs."
-msgstr "*VALUES*。キーと値のペアの一覧。"
-
-msgid "1"
-msgstr "1"
-
-msgid "1024"
-msgstr "1024"
-
-msgid "2048"
-msgstr "2048"
-
-msgid "5"
-msgstr "5"
-
-msgid "512"
-msgstr "512"
-
-msgid ":guilabel:`API Access`: View API endpoints."
-msgstr ":guilabel:`API アクセス`: API エンドポイントを表示します。"
-
-msgid ""
-":guilabel:`Access & Security`: Use the following tabs to complete these "
-"tasks:"
-msgstr ":guilabel:`アクセスとセキュリティー`: 以下のタブがあります。"
-
-msgid ":guilabel:`Access Level`: Choose read-write or read-only."
-msgstr ":guilabel:`アクセスレベル`: 読み書き、読み込み専用を選択します。"
-
-msgid ":guilabel:`Access To`: Fill in Access To field."
-msgstr ":guilabel:`アクセス先`: アクセス先の項目を入力します。"
-
-msgid ":guilabel:`Access Type`: Choose ip, user, or cert."
-msgstr ":guilabel:`アクセス種別`: IP、ユーザー、証明書を選択します。"
-
-msgid ":guilabel:`Admin State`: The state to start the network in."
-msgstr ":guilabel:`管理状態`: ネットワークの開始時の状態"
-
-msgid ":guilabel:`Allocation Pools`: Specify IP address pools."
-msgstr ":guilabel:`プールの確保`: IP アドレスプールを指定します。"
-
-msgid ":guilabel:`Architecture`"
-msgstr ":guilabel:`アーキテクチャー`"
-
-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 ""
-":guilabel:`アベイラビリティーゾーン`: 一覧からアベイラビリティーゾーンを選択"
-"します。デフォルトでは、この値はクラウドプロバイダーが指定したアベイラビリ"
-"ティゾーンに設定されます (例: ``us-west`` や ``apac-south``)。``nova`` となっ"
-"ている場合もあります。"
-
-msgid ""
-":guilabel:`Binding Host`: The ID of the host where the port is allocated."
-msgstr ":guilabel:`バインド: ホスト`:ポートが割り当てられたホストの ID。"
-
-msgid ""
-":guilabel:`Binding VNIC Type`: Select the VNIC type that is bound to the "
-"neutron port."
-msgstr ""
-":guilabel:`バインド: 仮想 NIC の種別`: neutron ポートにバインドされている仮"
-"想 NIC の種別を選択します。"
-
-msgid ""
-":guilabel:`Block Storage Services`: View a list of all Block Storage "
-"services."
-msgstr ""
-":guilabel:`ブロックストレージサービス`: 全 Block Storage サービスの一覧を見"
-"る。"
-
-msgid ":guilabel:`Change Password`: Change the password of the user."
-msgstr ":guilabel:`パスワードの変更`: ユーザーのパスワードを変更できます。"
-
-msgid ":guilabel:`Compute Services`: View a list of all Compute services."
-msgstr ":guilabel:`コンピュート`: コンピュートサービスの一覧の表示"
-
-msgid ":guilabel:`Configuration` tab"
-msgstr ":guilabel:`設定` タブ"
-
-msgid ":guilabel:`Confirm Password`: Enter the password again to confirm."
-msgstr ""
-":guilabel:`パスワード (確認)`: 確認のために、再びパスワードを入力します。"
-
-msgid ":guilabel:`Containers`: Create and manage containers and objects."
-msgstr ""
-":guilabel:`コンテナー`: コンテナーとオブジェクトの作成、管理を行います。"
-
-msgid ":guilabel:`Copy Data`"
-msgstr ":guilabel:`データのコピー`"
-
-msgid ":guilabel:`Create Subnet`: Select this check box to create a subnet"
-msgstr ""
-":guilabel:`サブネットの作成`: サブネットを作成する場合、このチェックボックス"
-"を選択します。"
-
-msgid ":guilabel:`Creation Timeout` :guilabel:`(minutes)`"
-msgstr ":guilabel:`作成タイムアウト時間` :guilabel:`(分単位)`"
-
-msgid ":guilabel:`DBName`"
-msgstr ":guilabel:`DBName`"
-
-msgid ":guilabel:`DBPassword`"
-msgstr ":guilabel:`DBPassword`"
-
-msgid ":guilabel:`DBRootPassword`"
-msgstr ":guilabel:`DBRootPassword`"
-
-msgid ":guilabel:`DBUsername`"
-msgstr ":guilabel:`DBUsername`"
-
-msgid ":guilabel:`DNS IP`: Enter the DNS IP address."
-msgstr ":guilabel:`DNS IP`: DNS の IP アドレスを入力します。"
-
-msgid ":guilabel:`DNS Name Servers`: Specify a name for the DNS server."
-msgstr ":guilabel:`DNS サーバー`: DNS サーバーの名前を指定します。"
-
-msgid ":guilabel:`Database Name`: Specify a name for the database instance."
-msgstr ""
-":guilabel:`データベース名`: データベースインスタンスの名前を指定します。"
-
-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 ""
-":guilabel:`デフォルト`: デフォルトのクォータの値を表示します。クォータは "
-"OpenStack Compute ではハードコードされており、最大許容サイズ、リソース数を定"
-"義します。"
-
-msgid ":guilabel:`Description`: Enter a new description."
-msgstr ":guilabel:`説明`: 説明を入力します。"
-
-msgid ""
-":guilabel:`Description`: Optionally, provide a brief description for the "
-"security service."
-msgstr ""
-":guilabel:`説明`: オプションとして、セキュリティーサービスの簡単な説明を入力"
-"します。"
-
-msgid ""
-":guilabel:`Description`: Optionally, provide a brief description for the "
-"share network."
-msgstr ""
-":guilabel:`説明`: オプションとして、ファイル共有ネットワークの簡単な説明を提"
-"供します。"
-
-msgid ""
-":guilabel:`Description`: Optionally, provide a brief description for the "
-"share."
-msgstr ""
-":guilabel:`説明`: オプションとして、ファイル共有の簡単な説明を提供します。"
-
-msgid ""
-":guilabel:`Description`: Optionally, provide a brief description for the "
-"volume."
-msgstr ""
-":guilabel:`説明`: オプションとして、ボリュームの簡単な説明を入力します。"
-
-msgid ""
-":guilabel:`Destination Container`: Choose the destination container from the "
-"list."
-msgstr ":guilabel:`宛先コンテナー`: 一覧から宛先コンテナーを選択します。"
-
-msgid ""
-":guilabel:`Destination object name`: Enter a name for the object in the new "
-"container."
-msgstr ""
-":guilabel:`宛先オブジェクト名`: 新しいコンテナーにおけるオブジェクトの名前を"
-"入力します。"
-
-msgid ":guilabel:`Details` tab"
-msgstr ":guilabel:`詳細` タブ"
-
-msgid ":guilabel:`Device ID`: Device ID attached to the port."
-msgstr ":guilabel:`デバイス ID`: ポートに接続されたデバイスの ID。"
-
-msgid ":guilabel:`Device Owner`: Device owner attached to the port."
-msgstr ":guilabel:`デバイス所有者`: ポートに接続されたデバイスの所有者。"
-
-msgid ""
-":guilabel:`Disable Gateway`: Select this check box to disable a gateway IP "
-"address."
-msgstr ""
-":guilabel:`ゲートウェイの無効化`: ゲートウェイの IP アドレスを無効化する場"
-"合、このチェックボックスを選択します。"
-
-msgid ":guilabel:`Domain`: Enter the domain name."
-msgstr ":guilabel:`ドメイン`: ドメイン名を入力します。"
-
-msgid ":guilabel:`Enable DHCP`: Select this check box to enable DHCP."
-msgstr ""
-":guilabel:`DHCP の有効化`: DHCP を有効化する場合、このチェックボックスを選択"
-"します。"
-
-msgid ":guilabel:`Environment File/Data`"
-msgstr ":guilabel:`環境ファイル/データ`"
-
-msgid ":guilabel:`Environment Source`"
-msgstr ":guilabel:`環境設定`"
-
-msgid ":guilabel:`Firewall Policies`: Add and manage firewall policies."
-msgstr ""
-":guilabel:`ファイアウォールポリシー`: ファイアウォールポリシーの追加、管理を"
-"行います。"
-
-msgid ":guilabel:`Firewall Rules`: Add and manage firewall rules."
-msgstr ""
-":guilabel:`ファイアウォールルール`: ファイアウォールルールの追加、管理を行い"
-"ます。"
-
-msgid ":guilabel:`Firewalls`: Create and manage firewalls."
-msgstr ":guilabel:`ファイアウォール`: ファイアウォールの作成、管理を行います。"
-
-msgid ":guilabel:`Flavor` tab"
-msgstr ":guilabel:`フレーバー` タブ"
-
-msgid ":guilabel:`Flavor`: Select an appropriate flavor for the instance."
-msgstr ""
-":guilabel:`フレーバー`: インスタンスに応じた適切なフレーバーを選択します。"
-
-msgid ""
-":guilabel:`Flavors`: View, create, edit, view extra specifications for, and "
-"delete flavors. A flavor is the size of an instance."
-msgstr ""
-":guilabel:`フレーバー`: フレーバーの作成、編集、追加仕様の参照、削除を行いま"
-"す。フレーバーはインスタンスのサイズです。"
-
-msgid ""
-":guilabel:`Floating IPs`: Allocate an IP address to or release it from a "
-"project."
-msgstr ""
-":guilabel:`Floating IP`: プロジェクトの IP アドレスの確保や解放を行います。"
-
-msgid ":guilabel:`Format`"
-msgstr ":guilabel:`形式`"
-
-msgid ""
-":guilabel:`Gateway IP`: Specify an IP address for a specific gateway. This "
-"parameter is optional."
-msgstr ""
-":guilabel:`ゲートウェイ IP`: ゲートウェイの IP アドレスを指定します。このパラ"
-"メーターはオプションです。"
-
-msgid ""
-":guilabel:`Host Aggregates`: View, create, and edit host aggregates. View "
-"the list of availability zones."
-msgstr ""
-":guilabel:`ホストアグリゲート`: ホストアグリゲートの表示、作成、編集を行いま"
-"す。アベイラビリティーゾーンの一覧を表示します。"
-
-msgid ":guilabel:`Host Routes`: Specify the IP address of host routes."
-msgstr ":guilabel:`ホストルート`: ホストルートの IP アドレスを指定します。"
-
-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 ""
-":guilabel:`ホスト`: オプションとして、ユーザーがこのホストのみから接続できる"
-"ようになります。ホストを指定しない場合、このユーザーはどこからでも接続できま"
-"す。"
-
-msgid ":guilabel:`Hypervisors`: View the hypervisor summary."
-msgstr ":guilabel:`ハイパーバイザー`: ハイパーバイザーの概要を表示します。"
-
-msgid ":guilabel:`IP Version`: Select IPv4 or IPv6."
-msgstr ":guilabel:`IP バージョン`: IPv4 または IPv6 を選択します。"
-
-msgid ":guilabel:`Image Description`"
-msgstr ":guilabel:`イメージの説明`"
-
-msgid ":guilabel:`Image File` or :guilabel:`Image Location`"
-msgstr ":guilabel:`イメージファイル` または :guilabel:`イメージの場所`"
-
-msgid ":guilabel:`Image Metadata`"
-msgstr ":guilabel:`イメージのメタデータ`"
-
-msgid ":guilabel:`Image Name`"
-msgstr ":guilabel:`イメージ名`"
-
-msgid ":guilabel:`Image Source`"
-msgstr ":guilabel:`イメージソース`"
-
-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 ""
-":guilabel:`イメージ`: プロジェクトのユーザーが作成したイメージやインスタンス"
-"のスナップショット、公開されているイメージを表示します。イメージの作成、編"
-"集、削除を行ったり、イメージやスナップショットからインスタンスを起動したりし"
-"ます。 "
-
-msgid ""
-":guilabel:`Images`: View, create, edit properties for, and delete custom "
-"images."
-msgstr ""
-":guilabel:`イメージ`: カスタムイメージのプロパティーの表示、作成、編集を行い"
-"ます。また、数タムイメージを削除できます。"
-
-msgid ""
-":guilabel:`Initial Admin User`: Create an initial admin user. This user will "
-"have access to all the databases you create."
-msgstr ""
-":guilabel:`初期管理`: 初期管理ユーザーを作成します。このユーザーは、作成する"
-"すべてのデータベースにアクセスできます。"
-
-msgid ":guilabel:`Initialize Databases`: Initial Database"
-msgstr ":guilabel:`データベースの初期化`: データベースを初期化します。"
-
-msgid ":guilabel:`InstanceType`"
-msgstr ":guilabel:`インスタンスタイプ`"
-
-msgid ""
-":guilabel:`Instances`: View, launch, create a snapshot from, stop, pause, or "
-"reboot instances, or connect to them through VNC."
-msgstr ""
-":guilabel:`インスタンス`: インスタンスの表示、起動、スナップショットの作成、"
-"停止、一時停止、リブートを行います。また、 VNC からインスタンスに接続します。"
-
-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 ""
-":guilabel:`インスタンス`: 一部のプロジェクト (全プロジェクトではない) のユー"
-"ザーに所属する実行中のインスタンスの表示、一時停止、再開、休止、移行、ソフト"
-"リブート、ハードリブート、削除を行います。また、インスタンスのログを表示した"
-"り、VNC 経由でインスタンスへアクセスしたりします。 "
-
-msgid ":guilabel:`Key Pair` tab"
-msgstr ":guilabel:`キーペア` タブ"
-
-msgid ""
-":guilabel:`Key Pairs`: View, create, edit, import, and delete key pairs."
-msgstr ""
-":guilabel:`キーペア`: キーペアの表示、作成、編集、インポート、削除を行いま"
-"す。"
-
-msgid ":guilabel:`KeyName`"
-msgstr ":guilabel:`キー名`"
-
-msgid ":guilabel:`LinuxDistribution`"
-msgstr ":guilabel:`Linux ディストリビューション`"
-
-msgid ":guilabel:`Load Balancers`: Create and manage load balancers."
-msgstr ":guilabel:`ロードバランサー`: ロードバランサーの作成、管理を行います。"
-
-msgid ":guilabel:`Members`: Add and manage members."
-msgstr ":guilabel:`メンバー`: メンバーの追加、管理を行います。"
-
-msgid ""
-":guilabel:`Metadata Definitions`: Import namespace and view the metadata "
-"information."
-msgstr ""
-":guilabel:`メタデータの定義`: 名前空間をインポートします。また、メタデータ情"
-"報を表示します。"
-
-msgid ":guilabel:`Metadata` tab"
-msgstr ":guilabel:`メタデータ` タブ"
-
-msgid ":guilabel:`Metadata`: Enter metadata for the share creation if needed."
-msgstr ""
-":guilabel:`メタデータ`: 必要に応じて、ファイル共有を作成するためのメタデータ"
-"を入力します。"
-
-msgid ""
-":guilabel:`Metadata`: To add share metadata, use key=value. To unset "
-"metadata, use key."
-msgstr ""
-":guilabel:`メタデータ`: ファイル共有のメタデータを追加するために、key=value "
-"を使用します。メタデータを解除する場合、key のみを使用します。"
-
-msgid ":guilabel:`Minimum Disk (GB)`"
-msgstr ":guilabel:`最小ディスク (GB)`"
-
-msgid ":guilabel:`Minimum RAM (MB)`"
-msgstr ":guilabel:`最小 RAM (MB)`"
-
-msgid ":guilabel:`Monitors`: Add and manage monitors."
-msgstr ":guilabel:`モニター`: モニターの追加、管理を行います。"
-
-msgid ":guilabel:`Name`: Enter a new security service name."
-msgstr ":guilabel:`名前`: 新しいセキュリティーサービスの名前を入力します。"
-
-msgid ":guilabel:`Name`: Enter a new share network name."
-msgstr ":guilabel:`名前`: 新しいファイル共有ネットワークの名前を入力します。"
-
-msgid ":guilabel:`Name`: Specify a name for the security service."
-msgstr ":guilabel:`名前`: セキュリティーグループの名前を指定します。"
-
-msgid ":guilabel:`Name`: Specify a name for the share network."
-msgstr ":guilabel:`名前`: ファイル共有ネットワークの名前を指定します。"
-
-msgid ":guilabel:`Name`: Specify name to identify the port."
-msgstr ":guilabel:`名前`: ポートを識別する名前を指定します。"
-
-msgid ":guilabel:`Network Address`: Specify the IP address for the subnet."
-msgstr ""
-":guilabel:`ネットワークアドレス`: サブネットの IP アドレスを指定します。"
-
-msgid ":guilabel:`Network Agents`: View the network agents."
-msgstr ""
-":guilabel:`ネットワークエージェント`: ネットワークエージェントを表示します。"
-
-msgid ":guilabel:`Network Name`: Specify a name to identify the network."
-msgstr ""
-":guilabel:`ネットワーク名`: ネットワークを識別するための名前を指定します。"
-
-msgid ":guilabel:`Network Ports` tab"
-msgstr ":guilabel:`ネットワークポート` タブ"
-
-msgid ":guilabel:`Network Topology`: View the network topology."
-msgstr ""
-":guilabel:`ネットワークトポロジー`: ネットワークトポロジーを表示します。"
-
-msgid ":guilabel:`Network` tab"
-msgstr ":guilabel:`ネットワーク` タブ"
-
-msgid ":guilabel:`Networks` tab"
-msgstr ":guilabel:`ネットワーク` タブ"
-
-msgid ":guilabel:`Networks`: Create and manage public and private networks."
-msgstr ""
-":guilabel:`ネットワーク`: パブリックネットワークとプライベートネットワークの"
-"作成、管理を行います。"
-
-msgid ""
-":guilabel:`Networks`: View, create, edit properties for, and delete networks."
-msgstr ""
-":guilabel:`ネットワーク`: ネットワークのプロパティーの表示、作成、編集を行い"
-"ます。また、ネットワークを削除できます。"
-
-msgid ":guilabel:`Neutron Net`: Choose a neutron network."
-msgstr ":guilabel:`Neutron Net`: neutron のネットワークを選択します。"
-
-msgid ":guilabel:`Neutron Subnet`: Choose a neutron subnet."
-msgstr ":guilabel:`Neutron Subnet`: neutron のサブネットを選択します。"
-
-msgid ":guilabel:`New Size (GB)`: Enter new size."
-msgstr ":guilabel:`新しい容量 (GB)`: 新しい容量を入力します。"
-
-msgid ""
-":guilabel:`Orchestration Services`: View a list of all Orchestration "
-"services."
-msgstr ""
-":guilabel:`オーケストレーションサービス`: すべての Orchestration サービスの一"
-"覧を表示します。"
-
-msgid ":guilabel:`Overview`: View basic reports."
-msgstr ":guilabel:`概要`: 基本的なレポートを表示します。"
-
-msgid ":guilabel:`Overview`: View reports for the project."
-msgstr ":guilabel:`概要`: プロジェクトのレポートを表示します。"
-
-msgid ":guilabel:`Password for user` :guilabel:`\"demo\"`"
-msgstr ":guilabel:`ユーザーのパスワード` :guilabel:`\"demo\"`"
-
-msgid ":guilabel:`Password`: Enter the password."
-msgstr ":guilabel:`パスワード`: パスワードを入力します。"
-
-msgid ""
-":guilabel:`Password`: Specify a password associated with the initial admin "
-"user you just named."
-msgstr ""
-":guilabel:`パスワード`: 名前をつけた初期管理ユーザーのパスワードを指定しま"
-"す。"
-
-msgid ""
-":guilabel:`Path`: Specify a path in which the new copy should be stored "
-"inside of the selected container."
-msgstr ""
-":guilabel:`パス`: 選択したコンテナー内に保存する新規コピーのパスを指定しま"
-"す。"
-
-msgid ":guilabel:`Pools`: Add and manage pools."
-msgstr ":guilabel:`プール`: プールの追加、管理を行います。"
-
-msgid ""
-":guilabel:`Projects`: View, create, assign users to, remove users from, and "
-"delete projects."
-msgstr ""
-":guilabel:`プロジェクト`: プロジェクトの表示、作成、削除を行います。また、"
-"ユーザーの割り当て、解除を行います。"
-
-msgid ":guilabel:`Protected`"
-msgstr ":guilabel:`保護`"
-
-msgid ""
-":guilabel:`Resource Types`: Show a list of all the supported resource types "
-"for HOT templates."
-msgstr ""
-":guilabel:`リソース種別`: HOT テンプレートにサポートされる、すべてのリソース"
-"種別を一覧表示します。"
-
-msgid ""
-":guilabel:`Resource Usage`: Use the following tabs to view the following "
-"usages:"
-msgstr ""
-":guilabel:`リソース使用状況`: 以下のタブを使用して、以下の使用状況を表示しま"
-"す。"
-
-msgid ":guilabel:`Rollback On Failure`"
-msgstr ":guilabel:`失敗時のロールバック`"
-
-msgid ":guilabel:`Routers`: Create and manage routers."
-msgstr ":guilabel:`ルーター`: ルーターの作成、管理を行います。"
-
-msgid ""
-":guilabel:`Routers`: View, create, edit properties for, and delete routers."
-msgstr ""
-":guilabel:`ルーター`: ルーターのプロパティーの表示、作成、編集を行います。ま"
-"た、ルーターを削除できます。"
-
-msgid ":guilabel:`Security Groups` tab"
-msgstr ":guilabel:`セキュリティーグループ` タブ"
-
-msgid ""
-":guilabel:`Security Groups`: View, create, edit, and delete security groups "
-"and security group rules."
-msgstr ""
-":guilabel:`セキュリティーグループ`: セキュリティーグループとセキュリティーグ"
-"ループルールの表示、作成、編集、削除を行います。"
-
-msgid ""
-":guilabel:`Security Services`: View, manage, and delete security services."
-msgstr ""
-":guilabel:`セキュリティーサービス`: セキュリティーサービスの管理、削除を行い"
-"ます。"
-
-msgid ":guilabel:`Server`: Enter the server name."
-msgstr ":guilabel:`サーバー`: サーバーの名前を入力します。"
-
-msgid ":guilabel:`Services`: View a list of the services."
-msgstr ":guilabel:`サービス`: サービスの一覧を表示します。"
-
-msgid ":guilabel:`Share Name`: Enter a new share name."
-msgstr ":guilabel:`ファイル共有名`: 新しいファイル共有の名前を入力します。"
-
-msgid ":guilabel:`Share Name`: Specify a name for the share."
-msgstr ":guilabel:`ファイル共有名`: ファイル共有の名前を指定します。"
-
-msgid ":guilabel:`Share Network`: Choose a share network."
-msgstr ""
-":guilabel:`ファイル共有ネットワーク`: ファイル共有ネットワークを選択します。"
-
-msgid ":guilabel:`Share Networks`: View, manage, and delete share networks."
-msgstr ""
-":guilabel:`ファイル共有ネットワーク`: ファイル共有ネットワークの管理、削除を"
-"行います。"
-
-msgid ":guilabel:`Share Protocol`: Select NFS, CIFS, GlusterFS, or HDFS."
-msgstr ""
-":guilabel:`ファイル共有プロトコル`: NFS、CIFS、GlusterFS、HDFS を選択します。"
-
-msgid ":guilabel:`Share Servers`: View, manage, and delete share servers."
-msgstr ""
-":guilabel:`ファイル共有サーバー`: ファイル共有サーバーの表示、作成、管理、削"
-"除を行います。"
-
-msgid ":guilabel:`Share Type`: Choose a share type."
-msgstr ":guilabel:`ファイル共有の種別`: ファイル共有の種別を選択します。"
-
-msgid ":guilabel:`Share Types`: View, create, manage, and delete share types."
-msgstr ""
-":guilabel:`ファイル共有種別`: ファイル共有種別の表示、作成、管理、削除を行い"
-"ます。"
-
-msgid ""
-":guilabel:`Shared`: Share the network with other projects. Non admin users "
-"are not allowed to set shared option."
-msgstr ""
-":guilabel:`共有`: 他のプロジェクトとネットワークを共有します。管理者ユーザー"
-"以外はこのオプションをセットすることはできません。"
-
-msgid ":guilabel:`Shares`: Use the following tabs to complete these tasks:"
-msgstr ":guilabel:`ファイル共有`: 以下のタブがあります。"
-
-msgid ":guilabel:`Shares`: View, create, manage, and delete shares."
-msgstr ""
-":guilabel:`ファイル共有`: ファイル共有の表示、作成、管理、削除を行います。"
-
-msgid ":guilabel:`Size (GB)`: The size of the share in gibibytes (GiB)."
-msgstr ":guilabel:`容量 (GB)`: ファイル共有の容量 (単位はギビバイト (GiB))。"
-
-msgid ":guilabel:`Size (GB)`: The size of the volume in gibibytes (GiB)."
-msgstr ":guilabel:`容量 (GB)`: ギガバイト (GiB) 単位のボリュームサイズ。"
-
-msgid ":guilabel:`Snapshots`: View, manage, and delete volume snapshots."
-msgstr ""
-":guilabel:`スナップショット`: ボリュームスナップショットの管理、削除を行いま"
-"す。"
-
-msgid ":guilabel:`Source` tab"
-msgstr ":guilabel:`システム` タブ"
-
-msgid ":guilabel:`Stack Name`"
-msgstr ":guilabel:`スタック名`"
-
-msgid ""
-":guilabel:`Stacks`: Use the REST API to orchestrate multiple composite cloud "
-"applications."
-msgstr ""
-":guilabel:`スタック`: REST API を使用して、複数の複合クラウドアプリケーション"
-"をオーケストレーションします。"
-
-msgid ":guilabel:`Stats`: View the statistics of all resources."
-msgstr ":guilabel:`統計情報`: すべてのリソースの統計情報を表示します。"
-
-msgid ":guilabel:`Subnet Details` tab"
-msgstr ":guilabel:`サブネット詳細` タブ"
-
-msgid ":guilabel:`Subnet Name`: Specify a name for the subnet."
-msgstr ":guilabel:`サブネット名`: サブネットの名前を指定します。"
-
-msgid ":guilabel:`Subnet` tab"
-msgstr ":guilabel:`サブネット` タブ"
-
-msgid ""
-":guilabel:`System Information`: Use the following tabs to view the service "
-"information:"
-msgstr ""
-":guilabel:`システム情報`: 以下のタブを使用して、サービスの情報を表示します。"
-
-msgid ":guilabel:`Template Source`"
-msgstr ":guilabel:`テンプレートソース`"
-
-msgid ":guilabel:`Template URL/File/Data`"
-msgstr ":guilabel:`テンプレート URL/ファイル/データ`"
-
-msgid ""
-":guilabel:`Type`: Choose the type from Active Directory, LDAP, or Kerberos."
-msgstr ""
-":guilabel:`種類`: Active Directory、LDAP、Kerberos から種類を選択します。"
-
-msgid ":guilabel:`Type`: Leave this field blank."
-msgstr ":guilabel:`形式`: この項目は空白にしておきます。"
-
-msgid ":guilabel:`Usage Report`: View the usage report."
-msgstr ":guilabel:`使用状況レポート`: 使用状況レポートを表示します。"
-
-msgid ":guilabel:`User Settings`: View and manage dashboard settings."
-msgstr ":guilabel:`ユーザー設定`: ダッシュボードの設定の表示、管理を行います。"
-
-msgid ":guilabel:`User`: Enter the user name."
-msgstr ":guilabel:`ユーザー`: ユーザー名を入力します。"
-
-msgid ":guilabel:`Users`: View, create, enable, disable, and delete users."
-msgstr ""
-":guilabel:`ユーザー`: ユーザーの表示、作成、有効化、無効化、削除を行います。"
-
-msgid ":guilabel:`Visibility`"
-msgstr ":guilabel:`公開範囲`"
-
-msgid ":guilabel:`Volume Name`: Specify a name for the volume."
-msgstr ":guilabel:`ボリューム名`: ボリュームの名前を指定します。"
-
-msgid ""
-":guilabel:`Volume Size`: Select a volume size. Volume size is expressed in "
-"GB."
-msgstr ""
-":guilabel:`ボリューム容量`: ボリューム容量を選択します。GB 単位で指定します。"
-
-msgid ""
-":guilabel:`Volume Snapshots`: View, create, edit, and delete volume "
-"snapshots."
-msgstr ""
-":guilabel:`ボリュームのスナップショット`: ボリュームのスナップショットの表"
-"示、作成、編集、削除を行います。"
-
-msgid ""
-":guilabel:`Volume Snapshots`: View, manage, and delete volume snapshots."
-msgstr ""
-":guilabel:`ボリュームのスナップショット`: ボリュームのスナップショットの表"
-"示、管理、削除を行います。"
-
-msgid ":guilabel:`Volume Source`: Select one of the following options:"
-msgstr ":guilabel:`ボリュームのソース`: 以下のオプションから選択します。"
-
-msgid ""
-":guilabel:`Volume Types`: View, create, manage, and delete volume types."
-msgstr ""
-":guilabel:`ボリューム種別`: ボリューム種別の表示、作成、管理、削除を行いま"
-"す。"
-
-msgid ":guilabel:`Volumes`: Use the following tabs to complete these tasks:"
-msgstr ":guilabel:`ボリューム`: 以下のタブがあります。"
-
-msgid ":guilabel:`Volumes`: View, create, edit, and delete volumes."
-msgstr ":guilabel:`ボリューム`: ボリュームの表示、作成、編集、削除を行います。"
-
-msgid ":guilabel:`Volumes`: View, create, manage, and delete volumes."
-msgstr ":guilabel:`ボリューム`: ボリュームの表示、作成、管理、削除を行います。"
-
-msgid ":ref:`Boot_a_new_instance_from_the_snapshot`"
-msgstr ":ref:`Boot_a_new_instance_from_the_snapshot`"
-
-msgid ":ref:`Boot_instance_from_image_and_attach_non-bootable_volume`"
-msgstr ":ref:`Boot_instance_from_image_and_attach_non-bootable_volume`"
-
-msgid ":ref:`Create_a_snapshot_of_the_instance`"
-msgstr ":ref:`Create_a_snapshot_of_the_instance`"
-
-msgid ":ref:`Create_volume_from_image_and_boot_instance`"
-msgstr ":ref:`Create_volume_from_image_and_boot_instance`"
-
-msgid ":ref:`Download_the_snapshot_as_an_image`"
-msgstr ":ref:`Download_the_snapshot_as_an_image`"
-
-msgid ":ref:`Import_the_snapshot_to_the_new_environment`"
-msgstr ":ref:`Import_the_snapshot_to_the_new_environment`"
-
-msgid ":ref:`archive-auto-extract`"
-msgstr ":ref:`archive-auto-extract`"
-
-msgid ":ref:`bulk-delete`"
-msgstr ":ref:`bulk-delete`"
-
-msgid ":ref:`large-object-creation`"
-msgstr ":ref:`large-object-creation`"
-
-msgid ":ref:`static-website`"
-msgstr ":ref:`static-website`"
-
-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 ""
-":term:`Cross-Origin Resource Sharing (CORS)` は、ブラウザーとサーバーがどのよ"
-"うにオリジンをまたがって通信するかを定義する仕様です。Object Storage API リク"
-"エストにより割り当てられたものなど、HTTP ヘッダーを使用します。Object "
-"Storage API は以下のヘッダーをサポートします。"
-
-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 ""
-"インスタンスの **キーペア**。イメージ起動時にイメージに注入される SSH 認証情"
-"報です。キーペアを正常にインジェクトさせるためには、イメージに **cloud-"
-"init** パッケージがインストールされている必要があります。プロジェクトごとに"
-"キーペアを最低でも 1 つ作成します。すでに外部のツールでキーペアを生成している"
-"場合は、OpenStack にそのキーペアをインポートすることができます。プロジェクト"
-"に所属する複数のインスタンスに対して、キーペアを使用することができます。"
-
-msgid "A **name** for your instance."
-msgstr "お使いのインスタンスの **名前**。"
-
-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 ""
-"**セキュリティーグループ**。どの受信ネットワークトラフィックがインスタンスに"
-"転送されるのかを定義します。セキュリティーグループは、**セキュリティーグルー"
-"プルール** と呼ばれるファイアウォールポリシーを保持しています。"
-
-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 ""
-"*セキュリティーグループ* は、インスタンスへアクセスが可能なトラフィックの種別"
-"を制限するために使用するネットワークのアクセスルールを名前を付けてまとめたも"
-"のです。インスタンスを起動して、1 つまたは複数のセキュリティーグループをイン"
-"スタンスに割り当てることができます。セキュリティーグループを作成しない場合、"
-"新しいインスタンスには明示的に別のセキュリティーグループを指定しない限り、自"
-"動的に Default のセキュリティーグループが割り当てられます。"
-
-msgid "A Java client offering console access to an instance"
-msgstr "インスタンスへのコンソールアクセスを提供する Java クライアント"
-
-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 ""
-"整数形式の UNIX エポック時間。例えば、``1348691905`` は ``Wed, 26 Sept 2012 "
-"20:38:25 GMT`` を表します。オブジェクトを期限切れにして、もはや処理されず、オ"
-"ブジェクトストアから完全に削除したい時間を指定します。"
-
-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 ""
-"マニフェストに対する ``GET`` や ``HEAD`` のリクエストでは、応答に ``Content-"
-"Type`` ヘッダー値が返されます。 ``Content-Type`` の値はマニフェストを作成し"
-"た ``PUT`` リクエストの ``Content-Type`` リクエストヘッダー値と同じになりま"
-"す。 ``Content-Type`` を変更するには、 ``PUT`` リクエストを再発行します。"
-
-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 ""
-"バージョン付きオブジェクトへの ``POST`` リクエストは、オブジェクトのメタデー"
-"タのみを更新し、オブジェクトの新しいバージョンを作成しません。オブジェクトの"
-"内容を変更する場合だけ、新しいバージョンが作成されます。"
-
-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 ""
-"``マニフェストオブジェクト`` は、分割されたオブジェクトを 1 つの論理ラージオ"
-"ブジェクトに結びつけます。マニフェストオブジェクトをダウンロードすると、"
-"Object Storage は分割オブジェクトの内容を結合して応答ボディーで返します。この"
-"動作は ``GET`` と ``HEAD`` のリクエストで返される応答ヘッダーにも適用されま"
-"す。応答ヘッダー ``Content-Length`` の値は、全分割オブジェクトの合計サイズに"
-"なります。"
-
-msgid ""
-"A bare-metal instance is an instance created directly on a physical machine, "
-"without any virtualization layer running underneath it. Nova retains power "
-"control via IPMI. In some situations, Nova may retain network control via "
-"Neutron and OpenFlow."
-msgstr ""
-"ベアメタルインスタンスは、物理マシンに直接作成されたインスタンスです。基盤と"
-"して仮想化レイヤーを持っていません。Nova は IPMI 経由で電源を制御します。いく"
-"つかの場合、Nova は Neutron や OpenFlow 経由でネットワークを制御するかもしれ"
-"ません。"
-
-msgid ""
-"A complete in-browser client solution for interaction with virtualized "
-"instances"
-msgstr ""
-"仮想化されたインスタンスと通信するための、完全なブラウザー型クライアントソ"
-"リューション"
-
-msgid "A configuration group can specify a large number of option values."
-msgstr "設定グループは、数多くのオプション値を指定できます。"
-
-msgid ""
-"A configuration group contains a comma-separated list of key-value pairs. "
-"Each pair consists of a configuration option and its value."
-msgstr ""
-"設定グループは、キーと値のペアのカンマ区切り一覧を含みます。各ペアは、設定オ"
-"プションとその値から構成されます。"
-
-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 ""
-"プロジェクトではなく、ユーザ個人に属したキーペア。キーペアを複数のユーザーに"
-"またがってシェアするためには、各ユーザーでそのキーペアのインポートが必要で"
-"す。"
-
-msgid "A list of specific HTTP referer headers denied read access:"
-msgstr ""
-"指定された HTTP referer ヘッダーがある場合、読み出しアクセスを拒否します。"
-
-msgid ""
-"A list of specific HTTP referer headers permitted to read container contents:"
-msgstr ""
-"指定された HTTP referer ヘッダーがある場合、コンテナーの内容の読み出しを許可"
-"します。"
-
-msgid ""
-"A list of specific users and projects permitted to read container contents:"
-msgstr ""
-"指定されたユーザーやプロジェクトがこのコンテナーの内容の読み出しができます。"
-
-msgid ""
-"A list of specific users and projects permitted to write to the container:"
-msgstr "指定されたユーザーやプロジェクトがこのコンテナーに書き込みができます。"
-
-msgid "A message indicates whether the action succeeded."
-msgstr "操作が成功したかどうかはメッセージでわかります。"
-
-# #-#-#-#-# dashboard_manage_shares.pot (End User Guide 1.0.0) #-#-#-#-#
-# #-#-#-#-# dashboard_manage_volumes.pot (End User Guide 1.0.0) #-#-#-#-#
-msgid "A message indicates whether the action was successful."
-msgstr "操作が成功したかどうかはメッセージでわかります。"
-
-msgid "A meter has the following attributes:"
-msgstr "メーターは以下の属性を持ちます。"
-
-msgid ""
-"A pool is a group of hosts that sits behind the load balancer and serves "
-"traffic through the load balancer."
-msgstr ""
-"プールは、ロードバランサーの背後に置かれ、ロードバランサー経由のトラフィック"
-"を処理するホストのグループです。"
-
-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 ""
-"Floating IP アドレスのプールは、クラウド管理者により設定され、OpenStack "
-"Compute で利用できます。プロジェクトのクォータが、プロジェクトに確保できる "
-"Floating IP アドレスの最大数を定義します。プロジェクトに Floating IP アドレス"
-"を確保した後、以下を実行できます。"
-
-msgid ""
-"A request with any HTTP referer header can read and list container contents:"
-msgstr ""
-"何らかの HTTP referer ヘッダーがある場合、コンテナーの内容の読み出しと一覧表"
-"示を許可します。"
-
-msgid "A request with any HTTP referer header can read container contents:"
-msgstr ""
-"何らかの HTTP referer ヘッダーがある場合、コンテナーの内容の読み出しを許可し"
-"ます。"
-
-msgid ""
-"A series of events is generated during the lifecycle of a stack. To display "
-"lifecycle events, run the following command:"
-msgstr ""
-"一連のイベントはスタックのライフサイクルを通して生成されます。ライフサイクル"
-"イベントを表示するために、以下のコマンドを実行します。"
-
-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 ""
-"データ群は、一定時間継続後に集約されます。(対照的に、サンプルはある単一の"
-"データ点を表します。)Telemetry は、以下の集約関数を利用します。"
-
-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 ""
-"監視項目と現在の状態を定義する一連のルール。指定した状態に関連づけられたエッ"
-"ジトリガー方式のアクションを持ちます。アラームは、ユーザー指向の Monitoring-"
-"as-a-Service、OpenStack の汎用的なユーティリティを提供します。アラートは、"
-"``ok``、``alarm``、``insufficient data`` の 3 つの状態を持ちます。伝統的な閾"
-"値によるアラームのために、静的な閾値と比較演算子により、状態を遷移させられま"
-"す。比較演算子は、選択したメーターの統計値を比較します。この比較間隔は、最近"
-"の範囲で設定可能な長さです。"
-
-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 ""
-"共有がファイルストレージにより提供されます。インスタンスが共有にアクセスでき"
-"るようできます。``manila`` クライアントコマンドを使用して、共有を作成および管"
-"理します。"
-
-msgid ""
-"A slash (/) character is used as the delimiter for pseudo-folders in Object "
-"Storage."
-msgstr ""
-"スラッシュ (/) 文字は、Object Storage において擬似フォルダーの区切り文字とし"
-"て使用されます。"
-
-msgid ""
-"A stack consists of a collection of resources. To list the resources and "
-"their status, run the following command:"
-msgstr ""
-"スタックはリソースの集合から構成されます。リソースとその状態を一覧表示するた"
-"めに、以下のコマンドを実行します。"
-
-msgid "A status of ``ACTIVE`` indicates that the instance is active."
-msgstr ""
-"``ACTIVE`` の状態は、インスタンスがアクティブであることを示しています。"
-
-msgid ""
-"A status of ``BUILD`` indicates that the instance has started, but is not "
-"yet online."
-msgstr ""
-"``BUILD`` の状態は、インスタンスが起動しているがオンラインにはなっていないこ"
-"とを示しています。"
-
-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 ""
-"種別。値が単調に増加するか (cumulative)、前の値からの変更量として解釈される"
-"か (delta)、単独の値として現在の計測間隔のみであるか (gauge) を意味します。"
-
-msgid "A unit of measurement"
-msgstr "計測単位"
-
-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 ""
-"ユーザーデータファイルは、メタデータサービス内の特別キーで、ゲストインスタン"
-"スにあるクラウド対応アプリケーションがアクセス可能なファイルを保持します。例"
-"えば、:term:`ユーザーデータ` を使用するアプリケーションの 1 つは `cloud-init "
-"`__ システムです。これは、さまざ"
-"まな Linux ディストリビューションで利用可能な Ubuntu 発祥のオープンソースパッ"
-"ケージです。クラウドインスタンスの初期設定を処理します。"
-
-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 ""
-"仮想マシンイメージ (このドキュメントでは単にイメージとする) は、ブート可能な"
-"オペレーティングシステムがインストールされた仮想ディスクを含む単一ファイルの"
-"ことです。イメージは仮想マシンインスタンスをクラウド内に作成するために使用さ"
-"れます。イメージファイルの作成については、`OpenStack 仮想マシンイメージガイ"
-"ド `_ を参照してください。"
-
-msgid "A volume size of ``5`` (5 GB)."
-msgstr "``5`` (5 GB) のボリューム容量。"
-
-msgid "Abstract"
-msgstr "概要"
-
-msgid "Access an instance through a console"
-msgstr "コンソール経由のインスタンスへのアクセス"
-
-msgid ""
-"Access and security credentials, which include one or both of the following "
-"credentials:"
-msgstr ""
-"アクセス、セキュリティークレデンシャル。以下のクレデンシャルの 1 つまたは両方"
-"が含まれます。"
-
-msgid ""
-"Access the security group rules from the ``rules`` attribute of a "
-"`novaclient.v1\\_1.security\\_groups.SecurityGroup `__ object:"
-msgstr ""
-"`novaclient.v1\\_1.security\\_groups.SecurityGroup `__ オブジェクトの "
-"``rules`` 属性からセキュリティーグループにアクセスします。 "
-
-msgid "Access-Control-Allow-Credentials"
-msgstr "Access-Control-Allow-Credentials"
-
-msgid "Access-Control-Allow-Methods"
-msgstr "Access-Control-Allow-Methods"
-
-msgid "Access-Control-Allow-Origin"
-msgstr "Access-Control-Allow-Origin"
-
-msgid "Access-Control-Expose-Headers"
-msgstr "Access-Control-Expose-Headers"
-
-msgid "Access-Control-Max-Age"
-msgstr "Access-Control-Max-Age"
-
-msgid "Access-Control-Request-Headers"
-msgstr "Access-Control-Request-Headers"
-
-msgid "Access-Control-Request-Method"
-msgstr "Access-Control-Request-Method"
-
-msgid "Activate the ports that you want to assign to the instance."
-msgstr "インスタンスに割り当てたいポートを有効化します。"
-
-msgid "Activate the security groups that you want to assign to the instance."
-msgstr "インスタンスに割り当てたいセキュリティーグループを有効化します。"
-
-msgid "Add Metadata items to your instance."
-msgstr "インスタンスにメタデータの項目を追加します。"
-
-# #-#-#-#-# cli_nova_configure_access_security_for_instances.pot (End User
-# Guide 1.0.0) #-#-#-#-#
-# #-#-#-#-# configure_access_and_security_for_instances.pot (End User Guide
-# 1.0.0) #-#-#-#-#
-msgid "Add a key pair"
-msgstr "キーペアの追加"
-
-msgid "Add a keypair"
-msgstr "キーペアの追加"
-
-msgid "Add a network interface to the node"
-msgstr "ノードへのネットワークインターフェースの追加"
-
-msgid "Add a rule to the default security group"
-msgstr "default セキュリティーグループへのルールの追加"
-
-msgid ""
-"Add rules to default security group allowing ping and SSH between instances "
-"in the default security group"
-msgstr ""
-"default セキュリティーグループでインスタンス間の ping と SSH を許可するルール"
-"の default セキュリティーグループへの追加"
-
-msgid "Add the following line to ``/etc/trove/trove.conf``:"
-msgstr "``/etc/trove/trove.conf`` を以下の行に追加します。"
-
-msgid "Additional large object arguments can be found by using ``--help``:"
-msgstr ""
-"その他のラージオブジェクト関連の引数は、``--help`` を使用して見つけられます。"
-
-msgid "Adds a network interface to a bare-metal node."
-msgstr "ベアメタルノードにネットワークインターフェースを追加します。"
-
-msgid ""
-"Administrative users can use the :guilabel:`Admin` tab to view usage and to "
-"manage instances, volumes, flavors, images, networks, and so on."
-msgstr ""
-"管理者は :guilabel:`管理` タブを使って、インスタンス、ボリューム、フレー"
-"バー、イメージ、ネットワークなどの使用状況の確認や管理ができます。"
-
-msgid ""
-"After the image is successfully uploaded, you can use the new image to boot "
-"instances."
-msgstr ""
-"イメージが正常にアップロードされた後、新しいイメージを使用してインスタンスを"
-"起動できます。"
-
-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 ""
-"インスタンスの正常起動後、リモートコンソールを使用してインスタンスに接続しま"
-"す。以下の説明に沿って、通常のコンピューターにおいて ISO イメージを使用するの"
-"と同じように、システムをインストールします。インストールが完了し、システムが"
-"再起動した後、インスタンスに再びオペレーティングシステムをインストールするか"
-"どうかを確認されます。これは、インスタンスが利用できないことを意味します。イ"
-"メージの作成に問題があれば、リファレンスとして `Virtual Machine Image Guide "
-"`_ を参照"
-"してください。"
-
-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 ""
-"サーバー稼働後、API でサーバー名を変更した場合、ホスト名を直接変更した場合、"
-"ダッシュボードに表示される名前は更新されません。"
-
-msgid ""
-"After the stack is created, click on the stack name to see the following "
-"details:"
-msgstr "スタックの作成後、スタック名をクリックして、以下の詳細を参照できます。"
-
-msgid ""
-"After upload has completed, you can download the large object as a single "
-"file:"
-msgstr ""
-"アップロードした後、ラージオブジェクトを単一ファイルとしてダウンロードするこ"
-"ともできます。"
-
-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 ""
-"インスタンスに IP アドレスを割り当てて、セキュリティーグループルールを設定し"
-"てから、インスタンスを Floating IP アドレスで公開します。"
-
-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 ""
-"ボリュームを作成した後、それらをインスタンスに接続できます。ボリュームは、同"
-"時に 1 つのインスタンスに接続できます。"
-
-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 ""
-"インスタンスを削除した後、ISO イメージを使用してインストールしたシステムが"
-"残ったままになります。これは、以下のコマンドを実行して、"
-"``shutdown=preserve`` パラメーターが設定されているためです。"
-
-msgid ""
-"After you gather required parameters, run the following command to launch an "
-"instance. Specify the server name, flavor ID, and image ID."
-msgstr ""
-"必要なパラメーターの収集後、インスタンスを起動するために、以下のコマンドを実"
-"行します。サーバー名、フレーバー ID、イメージ ID を指定します。"
-
-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 ""
-"インスタンスを起動するために必要なパラメーターを収集した後、:doc:`イメージ "
-"` や :doc:`ボリューム ` から起動できます。利用可能な OpenStack イメージの 1 つ"
-"または永続ボリュームにコピーしたイメージから直接インスタンスを起動することが"
-"できます。OpenStack Image service は、別のプロジェクトのメンバーがアクセスで"
-"きるイメージのプールを提供します。"
-
-msgid "Again, two items are returned, and there might be more."
-msgstr "再び、2 つの項目が返されます。さらにあるでしょう。"
-
-msgid "Alarm"
-msgstr "アラーム"
-
-msgid ""
-"All of OpenStack's APIs are actually REST APIs. The `keystoneauth `_ library provides an object that "
-"looks very much like a `Session `_ object from the Python `requests `_ library that handles all of the authentication "
-"for you. If you are more comfortable just dealing with REST or if there is a "
-"feature implemented in your cloud that has not seen support in any of the "
-"libraries yet, this option is for you."
-msgstr ""
-"すべての OpenStack の API はその実体は REST API です。 `keystoneauth "
-"`_ ライブラリーは、 "
-"Python の `requests `_ ライブラリーの "
-"`Session `_ "
-"オブジェクトによく似たオブジェクトを提供し、このオブジェクトは認証をすべて処"
-"理してくれます。 REST を直接扱う方がよい場合や、お使いのクラウドで他のライブ"
-"ラリーではまだサポートされていない機能が実装されている場合は、このオプション"
-"を使います。"
-
-msgid ""
-"All of the legacy client objects can be constructed the same way - the only "
-"difference is the first argument to ``make_client``. The examples will use "
-"``compute`` to get a nova client, but neutron can be accessed instead by "
-"replacing ``compute`` with ``network``."
-msgstr ""
-"従来からあるクライアントのオブジェクトはいずれも同じ方法で作成できます。唯一"
-"の違いは ``make_client`` の最初の引数です。 この例ではnova クライアントを取得"
-"するため ``compute`` を使用しますが、 ``compute`` を ``network`` に変えると "
-"neutron クライアントが得られます。"
-
-msgid "All segment objects must be in the same container."
-msgstr "分割オブジェクトは、すべて同じにコンテナーになければいけません。"
-
-msgid "All users residing in project1 can read container contents:"
-msgstr ""
-"project1 のすべてのユーザーがこのコンテナーの内容の読み出しができます。"
-
-msgid "All users residing in project1 can write to the container:"
-msgstr "project1 のすべてのユーザーがこのコンテナーに書き込みができます。"
-
-msgid "Allocate a floating IP address to an instance"
-msgstr "インスタンスへの Floating IP アドレスの割り当て"
-
-msgid ""
-"Allow UDP access from IP addresses, specified as IP subnet ``0.0.0.0/0`` in "
-"CIDR notation."
-msgstr ""
-"CIDR 表記で IP サブネット ``0.0.0.0/0`` として指定して、すべての IP アドレス"
-"からの UDP アクセスを許可します。"
-
-msgid "Allow access"
-msgstr "アクセスの許可"
-
-msgid ""
-"Allow access from all IP addresses, specified as IP subnet ``0.0.0.0/0`` in "
-"CIDR notation:"
-msgstr ""
-"CIDR 表記で IP サブネット ``0.0.0.0/0`` として指定して、すべての IP アドレス"
-"からのアクセスを許可します。"
-
-msgid ""
-"Allow access only from IP addresses from other security groups (source "
-"groups) to access the specified port:"
-msgstr ""
-"他のセキュリティーグループからの IP アドレス (ソースグループ) のみが指定した"
-"ポートにアクセスできるようにします。"
-
-msgid "Allow access."
-msgstr "アクセスを許可します。"
-
-msgid ""
-"Allow only IP addresses from other security groups (source groups) to access "
-"the specified port."
-msgstr ""
-"他のセキュリティーグループからの IP アドレス (ソースグループ) のみが指定した"
-"ポートにアクセスできるようにします。"
-
-msgid ""
-"Allow only members of other security groups (source groups) to ping "
-"instances."
-msgstr ""
-"他のセキュリティーグループ (ソースグループ) のメンバーのみがインスタンスに "
-"ping できるようにします。"
-
-msgid ""
-"Allow pinging from all IP addresses, specified as IP subnet ``0.0.0.0/0`` in "
-"CIDR notation."
-msgstr ""
-"CIDR 表記で IP サブネット ``0.0.0.0/0`` として指定して、すべての IP アドレス"
-"からの ping を許可します。"
-
-msgid "Allow read-only access"
-msgstr "読み取り専用アクセスの許可"
-
-msgid "Allow read-write access"
-msgstr "読み書きアクセスの許可"
-
-msgid "Also, the Bare Metal service supports the configuration drive."
-msgstr "Bare Metal サービスもコンフィグドライブをサポートしています。"
-
-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 ""
-"OpenStack Object Storage に複数階層のディレクトリーを作成できませんが、オブ"
-"ジェクトの名前にスラッシュ (``/``) を追加することにより、単一のコンテナー内に"
-"階層構造を模倣できます。``delimiter`` クエリーパラメーターを使用して、擬似"
-"ディレクトリーを移動できます。この例は、擬似階層フォルダーとディレクトリーの"
-"使い方を示しています。"
-
-msgid "An account"
-msgstr "アカウント"
-
-msgid "An in-browser VNC client implemented using HTML5 Canvas and WebSockets"
-msgstr ""
-"HTML5 Canvas と WebSockets を用いて実装された、ブラウザー型 VNC クライアント"
-
-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 ""
-"このデータは、特定のメーターに関連づけられた値を示します。サンプルは、関連づ"
-"けられたメーターと同じ属性を持ち、タイムスタンプと値の属性も持ちます。値の属"
-"性は、サンプル ``ボリューム`` としても知られています。"
-
-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 ""
-"リクエストした時間からオブジェクトを削除するまでの秒数を指定する整数値。この"
-"ヘッダーは、秒数形式の現在時刻に ``X-Delete-After`` の値を合計した値を ``X-"
-"Delete-At`` に変換します。"
-
-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 ""
-"任意の **ユーザーデータ** 。ユーザーデータファイルは、メタデータサービス内の"
-"特別キーで、ゲストインスタンスにあるクラウド対応アプリケーションがアクセス可"
-"能なファイルを保持します。例えば、ユーザーデータを使用するアプリケーションの "
-"1 つは `cloud-init `__ システム"
-"です。これは、さまざまな Linux ディストリビューションで利用可能な Ubuntu 発祥"
-"のオープンソースパッケージです。クラウドインスタンスの初期設定を処理します。"
-
-msgid "Any 2\\ ``nn`` response indicates success."
-msgstr "すべての 2\\ ``nn`` の応答は、正常を意味します。"
-
-msgid ""
-"Any modern guest operating system that is capable of mounting an ISO 9660 or "
-"VFAT file system can use the configuration drive."
-msgstr ""
-"コンフィグドライブは、ISO 9660 または VFAT のファイルシステムをマウントできる"
-"ゲストオペレーティングシステムからであればどれでも使用することができます。こ"
-"の機能は、最近のオペレーティングシステムのすべてで利用できるはずです。"
-
-msgid ""
-"Append this parameter to the URL for a ``GET`` request, where ``format`` is "
-"``json`` or ``xml``."
-msgstr ""
-"このパラメーターを ``GET`` リクエストの URL に追加します。ここで ``format`` "
-"は ``json`` か ``xml`` です。"
-
-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 ""
-"あなたはクラウドのエンドユーザーとして、OpenStack dashboard を使用できます。"
-"管理者により設定された制限の範囲内で自身のリソースを展開できます。他の種類や"
-"大きさのサーバーインスタンスを作成するために、このセクションで提供される例を"
-"変更できます。"
-
-msgid ""
-"As an OpenStack cloud end user, you can provision your own resources within "
-"the limits set by cloud administrators."
-msgstr ""
-"OpenStack クラウドのエンドユーザーとして、クラウド管理者により設定された制限"
-"の範囲内で自身のリソースを配備できます。"
-
-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 ""
-"エンドユーザーは、さまざまなプロジェクトのユーザー用のロードバランサーや関連"
-"オブジェクトの作成、管理ができます。ロードバランサーや関連オブジェクトの削除"
-"もできます。"
-
-msgid ""
-"As an example, see the sample shell file that sets these variables to get "
-"credentials:"
-msgstr ""
-"例として、クレデンシャルを取得するために、これらの変数を設定するサンプルシェ"
-"ルファイルを参照してください。"
-
-msgid ""
-"As background, assume that you have created a database instance with the "
-"following characteristics:"
-msgstr ""
-"背景として、以下の特性を持つデータベースインスタンスを作成してあることを仮定"
-"しています。"
-
-msgid ""
-"As shown in this example, the public URL appears in the ``StorageURL`` "
-"field, and the token appears in the ``Auth Token`` field:"
-msgstr ""
-"この例にあるように、パブリック URL が ``StorageURL`` の項目に、トークンが "
-"``Auth Token`` の項目に表示されます。"
-
-msgid ""
-"As you can see, the ``sync_binlog`` option is currently set to ``0`` for the "
-"``myDB7`` database."
-msgstr ""
-"確認できるように、``myDB7`` データベースの ``sync_binlog`` オプションが現在 "
-"``0`` に設定されています。"
-
-msgid ""
-"As you can see, the ``sync_binlog`` option is now set to ``1``, as specified "
-"in the ``group1`` configuration group."
-msgstr ""
-"確認できるように、``group1`` 設定グループに指定されているとおり、"
-"``sync_binlog`` オプションが現在 ``1`` に設定されています。"
-
-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 ""
-"ダッシュボードへのアクセスに使用するホスト名またはパブリック IP アドレス、"
-"ユーザー名、パスワードをクラウド運用者に問い合わせます。お使いのクラウドがマ"
-"ルチドメインをサポートしている場合、ドメイン名も確認する必要があります。"
-
-msgid "Assign CORS headers to requests"
-msgstr "CORS ヘッダーのリクエストへの割り当て"
-
-msgid "Assign a name to the virtual machine."
-msgstr "仮想マシンに名前を割り当てます。"
-
-msgid "Associate an IP address with an instance in the project, as follows:"
-msgstr "以下のように、IP アドレスをプロジェクトのインスタンスに割り当てます。"
-
-msgid "Associate floating IP addresses"
-msgstr "Floating IP アドレスの割り当て"
-
-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 ""
-"Floating IP アドレスをプロジェクトのインスタンスに割り当てます。Floating IP "
-"アドレスは、同時に 1 つだけインスタンスに割り当てられます。"
-
-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 ""
-"すでに Database がインストールしてあり、使用したいデータベースの種類とバー"
-"ジョンのイメージを用いて、データストアにデータを入力してあると仮定します。ま"
-"た、データベースを作成し、アクセスできると仮定します。"
-
-msgid "Assume the following list of container names:"
-msgstr "以下のコンテナー名の一覧を仮定します。"
-
-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 ""
-"保証されます。部品の一覧は、各部品の MD5 チェックサム (``ETag``) を含みます。"
-"一覧にある ``ETag`` がアップロードされる分割オブジェクトと異なる場合、マニ"
-"フェストオブジェクトをアップロードできません。部品が何かしら失われていると、"
-"マニフェストオブジェクトのダウンロード試行は、エラーになります。"
-
-msgid "At the prompt, type ``yes``."
-msgstr "プロンプトに ``yes`` と入力します。"
-
-msgid ""
-"At this point, you might want to delete the disabled ``guest1`` instance, by "
-"using the :command:`trove delete` command."
-msgstr ""
-"この時点で、 :command:`trove delete` コマンドを使用して、無効化された "
-"``guest1`` インスタンスを削除したいかもしれません。"
-
-msgid "Attach a volume to an instance"
-msgstr "ボリュームのインスタンスへの接続"
-
-msgid ""
-"Attach a volume to an instance after the instance is active, and the volume "
-"is available"
-msgstr ""
-"インスタンスの起動後、ボリュームをインスタンスに接続すると、ボリュームが利用"
-"可能になります。"
-
-msgid "Attach swap or ephemeral disk to an instance"
-msgstr "インスタンスへのスワップや一時ディスクの接続"
-
-msgid "Attach the configuration group to the database instance:"
-msgstr "設定グループをデータベースインスタンスに接続します。"
-
-msgid "Attach the instance to the volume:"
-msgstr "インスタンスにボリュームを接続します。"
-
-msgid "Authenticate"
-msgstr "認証"
-
-msgid "Auto-extract archive files"
-msgstr "自動展開アーカイブファイル"
-
-msgid "Auto-extract archive request"
-msgstr "自動展開アーカイブの要求"
-
-msgid "Auto-extract archive response"
-msgstr "自動展開アーカイブの応答"
-
-msgid "Availability Zone"
-msgstr "アベイラビリティゾーン"
-
-msgid "Available Metadata"
-msgstr "利用可能なメタデータ"
-
-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 ""
-":command:`trove backup-create` コマンドを使用して、データベースインスタン"
-"`backup1`` という名前です。``INSTANCE_ID`` を ``97b4b853-80f6-414f-ba6f-"
-"c6f455a79ae6`` に置き換えます。"
-
-# #-#-#-#-# backup_db.pot (End User Guide 1.0.0) #-#-#-#-#
-# #-#-#-#-# dashboard_databases.pot (End User Guide 1.0.0) #-#-#-#-#
-msgid "Backup and restore a database"
-msgstr "データベースのバックアップとリストア"
-
-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 ""
-":guilabel:`イメージソース` で選択した項目に応じて、:guilabel:`イメージの場所"
-"` の項目にイメージの場所の URL を入力するか、お使いのシステムにあるイメージ"
-"ファイルを参照して追加します。"
-
-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 ""
-"ダッシュボードは、インスタンスで使用する特定のデータストアを選択できないた"
-"め、デフォルトのデータストアを設定する必要があります。そして、ダッシュボード"
-"は、インスタンスを作成するためにデフォルトのデータストアを使用します。"
-
-msgid "Because two container names are returned, there are more names to list."
-msgstr "2 つのコンテナー名が返されるので、さらなる名前が一覧にあります。"
-
-msgid "Before you begin, source the OpenStack RC file."
-msgstr "開始前に OpenStack RC ファイルを読み込みます。"
-
-msgid "Before you can launch an instance, gather the following parameters:"
-msgstr "インスタンスを起動する前に、以下のパラメーターの情報を集めます。"
-
-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 ""
-"5 GB より大きいオブジェクトをアップロードする前に、ユーザーはそのオブジェクト"
-"を分割する必要があります。他のオブジェクトと同様に分割オブジェクトをアップ"
-"ロードして、動的ラージマニフェストオブジェクトを作成します。マニフェストオブ"
-"ジェクトは、ラージオブジェクトを構成する分割オブジェクトを検索する方法を "
-"Object Storage に知らせます。分割オブジェクトに個別にアクセスできますが、マニ"
-"フェストオブジェクトを取得する際には API は分割オブジェクトを結合します。1 つ"
-"のラージオブジェクトには任意の数の分割オブジェクトを含めることができます。"
-
-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 ""
-"インスタンスを起動する前に、セキュリティーグループルールを追加してユーザーが "
-"ping および SSH でインスタンスに接続できるようにします。これには、:ref:"
-"`security_groups_add_rule` をするか、ルールがすでに設定されているセキュリ"
-"ティーグループを追加します。 "
-
-msgid ""
-"Before you run commands, `set environment variables using the OpenStack RC "
-"file `_."
-msgstr ""
-"コマンドを実行する前に、 `OpenStack RC ファイルを使って環境変数を設定してく"
-"ださい `_ 。"
-
-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 ""
-"新しく作成した設定グループを使用する前に、どのように ``sync_binlog`` オプショ"
-"ンがデータベースを設定するのかを確認していきます。以下の connection の設定例"
-"を、お使いのデータベースに接続できる設定に置き換えます。"
-
-msgid "Block Storage (cinder)"
-msgstr "Block Storage (cinder)"
-
-msgid "Boot a new instance from the snapshot"
-msgstr "スナップショットから新しいインスタンスを起動します。"
-
-msgid "Boot an instance and attach to volume"
-msgstr "インスタンスの起動およびボリュームの接続"
-
-msgid "Boot an instance from an ISO image"
-msgstr "ISO イメージからのインスタンスの起動"
-
-msgid "Boot an instance from an image and attach a non-bootable volume."
-msgstr "イメージからインスタンスを起動し、ブート不可のボリュームを接続します。"
-
-msgid "Boot an instance using flavor and image names (if names are unique)"
-msgstr "フレーバーとイメージ名 (名前が一意な場合) を用いたインスタンスの起動"
-
-msgid "Boot from image"
-msgstr "イメージから起動"
-
-msgid "Boot from image (creates a new volume)"
-msgstr "イメージから起動 (新しいボリュームを作成)"
-
-msgid "Boot from snapshot"
-msgstr "スナップショットから起動"
-
-msgid "Boot from volume"
-msgstr "ボリュームから起動"
-
-msgid "Boot from volume snapshot (creates a new volume)"
-msgstr "ボリュームのスナップショットから起動 (新しいボリュームを作成)"
-
-msgid "Boot instance from image and attach non-bootable volume"
-msgstr "インスタンスをイメージから起動し、ブート不可のボリュームを接続します。"
-
-msgid "Browse to and select the file that you want to upload."
-msgstr "アップロードしたいファイルを選択します。"
-
-msgid "Bulk delete"
-msgstr "一括削除"
-
-msgid "Bulk delete request"
-msgstr "一括削除の要求"
-
-msgid "Bulk delete response"
-msgstr "一括削除の応答"
-
-msgid "Bulk-configure a database or databases"
-msgstr "データベースの一括設定"
-
-msgid ""
-"By default, the :command:`openstack server 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 operating system is allowed to complete the shutdown. The default "
-"timeout is 60 seconds. See `Description of Compute configuration options "
-"`_ for details."
-msgstr ""
-":command:`openstack server resize` コマンドはデフォルトで、インスタンスを停止"
-"してリサイズする前に、ゲストオペレーティングシステムに制御してシャットダウン"
-"する機会を与えます。シャットダウン動作は、 ``nova.conf`` ファイルに設定でき"
-"る ``shutdown_timeout`` パラメーターにより設定できます。その値は、ゲストオペ"
-"レーティングシステムがシャットダウンを完了するまでに許可される時間 (秒) を意"
-"味します。デフォルトのタイムアウトは 60 秒です。詳細は `Description of "
-"Compute configuration options `_ を参照してください。"
-
-msgid ""
-"By default, the :command:`openstack server shelve` command gives the guest "
-"operating system a chance to perform a controlled shutdown before the "
-"instance is powered off. The shutdown behavior is configured by the "
-"``shutdown_timeout`` parameter that can be set in the :file:`nova.conf` "
-"file. Its value stands for the overall period (in seconds) a guest operating "
-"system is allowed to complete the shutdown. The default timeout is 60 "
-"seconds. See `Description of Compute configuration options `_ for "
-"details."
-msgstr ""
-":command:`openstack server shelve` コマンドはデフォルトで、インスタンスを停止"
-"する前に、ゲストオペレーティングシステムに制御してシャットダウンする機会を与"
-"えます。シャットダウン動作は、 ``nova.conf`` ファイルに設定できる "
-"``shutdown_timeout`` パラメーターにより設定できます。その値は、ゲストオペレー"
-"ティングシステムがシャットダウンを完了するまでに許可される時間 (秒) を意味し"
-"ます。デフォルトのタイムアウトは 60 秒です。詳細は `Description of Compute "
-"configuration options `_ を参照してください。"
-
-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 ""
-"Object Storage API は、デフォルトで ``text/plain`` 応答形式を使用します。さら"
-"に、JSON と XML のデータシリアライズ応答形式もサポートします。"
-
-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 ""
-"オブジェクトのコンテンツは、デフォルトで 5 GB より大きくできません。しかしな"
-"がら、いくつかのより小さなオブジェクトを使用して、大きなオブジェクト (ラージ"
-"オブジェクト) を組み立てることができます。ラージオブジェクトは、2 種類のオブ"
-"ジェクトから構成されます。"
-
-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 ""
-"デフォルトでは、この値はクラウドプロバイダーが指定したアベイラビリティゾーン"
-"に設定されます (例: ``us-west`` や ``apac-south``)。``nova`` となっている場合"
-"もあります。"
-
-msgid "By default, when you reboot an instance, it is a soft reboot."
-msgstr ""
-"デフォルトでは、インスタンスをリブートする場合ソフトリブートとなっています。"
-
-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 ""
-"デフォルトでは、ディスクドライブの代わりに CD ドライブとしてコンフィグドライ"
-"ブのイメージを接続することはできません。CD ドライブを接続する場合は、``/etc/"
-"nova/nova.conf`` の以下の行を追加します。 "
-
-msgid "Call ``print_server`` again to check the update server details:"
-msgstr "再び ``print_server`` を呼び出し、更新したサーバーの詳細を確認します。"
-
-msgid ""
-"Call ``server.update`` on the server object with the new value for ``name`` "
-"variable:"
-msgstr ""
-"新しい ``name`` 変数の値を用いて、server オブジェクトの ``server.update`` を"
-"呼び出します。"
-
-msgid "Cassandra"
-msgstr "Cassandra"
-
-msgid "Change the name of the image."
-msgstr "イメージの名前を変更します。"
-
-msgid "Change the size of a server by changing its flavor."
-msgstr "フレーバーを変更して、サーバーの大きさを変更します。"
-
-msgid "Change the size of your server"
-msgstr "サーバーの大きさの変更"
-
-msgid "Check if the instance is online."
-msgstr "インスタンスがオンラインになっているかどうかをチェックします。"
-
-msgid "Check the backup you want to use and click :guilabel:`Restore Backup`."
-msgstr ""
-"使用したいバックアップを確認し、:guilabel:`バックアップのリストア` をクリック"
-"します。"
-
-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 ""
-"作業したいインスタンスを確認します。:guilabel:`アクション` 列にあるドロップダ"
-"ウンリストを展開し、:guilabel:`インスタンスのリサイズ` を選択します。"
-
-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 ""
-"作業したいインスタンスを確認します。:guilabel:`アクション` 列にあるドロップダ"
-"ウンリストを展開し、:guilabel:`ボリュームのリサイズ` を選択します。"
-
-msgid ""
-"Choose the image source from the dropdown list. Your choices are :guilabel:"
-"`Image Location` and :guilabel:`Image File`."
-msgstr ""
-"ドロップダウンリストからイメージソースを選択します。:guilabel:`イメージの場所"
-"` と :guilabel:`イメージファイル` から選びます。"
-
-msgid "Choose the pool from which to pick the IP address."
-msgstr "IP アドレスを確保するプールを選択します。"
-
-msgid "Choose the rule you want to delete."
-msgstr "削除したいルールを選択します。"
-
-msgid ""
-"Choose the source of the environment from the list. The environment files "
-"contain additional settings for the stack."
-msgstr ""
-"環境のソースを一覧から選択します。環境ファイルは、スタック向けの追加の文字列"
-"を含みます。"
-
-msgid "Choose the source of the template from the list."
-msgstr "テンプレートのソースを一覧から選択します。"
-
-msgid "Clear the :guilabel:`Public` check box to make the image private."
-msgstr ""
-":guilabel:`パブリック` チェックボックスをチェック解除して、イメージをプライ"
-"ベートにします。"
-
-msgid "Click :guilabel:`Add Interface`."
-msgstr ":guilabel:`インターフェースの追加` をクリックします。"
-
-msgid "Click :guilabel:`Add Rule`."
-msgstr ":guilabel:`ルールの追加` をクリックします。"
-
-msgid "Click :guilabel:`Add rule`."
-msgstr ":guilabel:`ルールの追加` をクリックします。"
-
-msgid "Click :guilabel:`Add`."
-msgstr ":guilabel:`追加` をクリックします。"
-
-msgid "Click :guilabel:`Allocate IP To Project`."
-msgstr ":guilabel:`Floating IP の確保` をクリックします。"
-
-msgid "Click :guilabel:`Allocate IP`."
-msgstr ":guilabel:`IP の確保` をクリックします。"
-
-msgid "Click :guilabel:`Associate`."
-msgstr ":guilabel:`割り当て` をクリックします。"
-
-msgid "Click :guilabel:`Attach Volume`."
-msgstr ":guilabel:`ボリュームの接続` をクリックします。"
-
-msgid "Click :guilabel:`Backup`. The new backup appears in the backup list."
-msgstr ""
-":guilabel:`バックアップ` をクリックします。新しいバックアップがバックアップ一"
-"覧に表示されます。"
-
-msgid "Click :guilabel:`Change Stack Template`."
-msgstr ":guilabel:`スタックテンプレートの変更` をクリックします。"
-
-msgid "Click :guilabel:`Container`."
-msgstr ":guilabel:`コンテナー` をクリックします。"
-
-msgid "Click :guilabel:`Copy Object`."
-msgstr ":guilabel:`オブジェクトのコピー` をクリックします。"
-
-msgid "Click :guilabel:`Create Backup`."
-msgstr ":guilabel:`バックアップの作成` をクリックします。"
-
-msgid "Click :guilabel:`Create Image`."
-msgstr ":guilabel:`イメージの作成` をクリックします。"
-
-msgid "Click :guilabel:`Create Key Pair`."
-msgstr ":guilabel:`キーペアの作成` をクリックします。"
-
-msgid "Click :guilabel:`Create Network`."
-msgstr ":guilabel:`ネットワークの作成` をクリックします。"
-
-msgid "Click :guilabel:`Create Port`."
-msgstr ":guilabel:`ポートの作成` をクリックします。"
-
-msgid "Click :guilabel:`Create Pseudo-folder`."
-msgstr ":guilabel:`擬似フォルダーの作成` をクリックします。"
-
-msgid "Click :guilabel:`Create Router`."
-msgstr ":guilabel:`ルーターの作成` をクリックします。"
-
-msgid "Click :guilabel:`Create Security Service`."
-msgstr ":guilabel:`セキュリティーサービスの作成` をクリックします。"
-
-msgid "Click :guilabel:`Create Share Network`."
-msgstr ":guilabel:`ファイル共有ネットワークの作成` をクリックします。"
-
-msgid "Click :guilabel:`Create Share`."
-msgstr ":guilabel:`ファイル共有の作成` をクリックします。"
-
-msgid "Click :guilabel:`Create Volume`."
-msgstr ":guilabel:`ボリュームの作成` をクリックします。"
-
-# #-#-#-#-# dashboard_create_networks.pot (End User Guide 1.0.0) #-#-#-#-#
-# #-#-#-#-# dashboard_manage_containers.pot (End User Guide 1.0.0) #-#-#-#-#
-msgid "Click :guilabel:`Create`."
-msgstr ":guilabel:`作成` をクリックします。"
-
-msgid "Click :guilabel:`Delete Images`."
-msgstr ":guilabel:`イメージの削除` をクリックします。"
-
-msgid "Click :guilabel:`Delete Security Services` and confirm your choice."
-msgstr ""
-":guilabel:`セキュリティーサービスの削除` をクリックして、内容を確認します。"
-
-msgid "Click :guilabel:`Delete Share Networks` and confirm your choice."
-msgstr ""
-":guilabel:`ファイル共有ネットワークの削除` をクリックして、内容を確認します。"
-
-msgid "Click :guilabel:`Delete Shares` and confirm your choice."
-msgstr ":guilabel:`ファイル共有の削除` をクリックして、内容を確認します。"
-
-msgid "Click :guilabel:`Delete Stack`."
-msgstr ":guilabel:`スタックの削除` をクリックします。"
-
-msgid "Click :guilabel:`Delete Volumes` and confirm your choice."
-msgstr ":guilabel:`ボリュームの削除` をクリックし、内容を確認します。"
-
-msgid "Click :guilabel:`Delete rule` and confirm your choice."
-msgstr ":guilabel:`ルールの削除` をクリックして、内容を確認します。"
-
-msgid "Click :guilabel:`Detach Volume` and confirm your changes."
-msgstr ":guilabel:`ボリュームの切断` をクリックして、変更内容を確認します。"
-
-msgid "Click :guilabel:`Edit Image`."
-msgstr ":guilabel:`イメージの編集` をクリックします。"
-
-msgid "Click :guilabel:`Edit Security Service`."
-msgstr ":guilabel:`セキュリティーサービスの編集` をクリックします。"
-
-msgid "Click :guilabel:`Edit Share Metadata`."
-msgstr ":guilabel:`ファイル共有のメタデータの編集` をクリックします。"
-
-msgid "Click :guilabel:`Edit Share Network`."
-msgstr ":guilabel:`ファイル共有ネットワークの編集` をクリックします。"
-
-msgid "Click :guilabel:`Edit Share`."
-msgstr ":guilabel:`ファイル共有の編集` をクリックします。"
-
-msgid "Click :guilabel:`Edit Volume`."
-msgstr ":guilabel:`ボリュームの編集` をクリックします。"
-
-msgid "Click :guilabel:`Extend Share`."
-msgstr ":guilabel:`ファイル共有の拡張` をクリックします。"
-
-msgid "Click :guilabel:`Import Key Pair`."
-msgstr ":guilabel:`キーペアのインポート` をクリックします。"
-
-msgid "Click :guilabel:`Launch Instance`."
-msgstr ":guilabel:`インスタンスの起動` をクリックします。"
-
-msgid "Click :guilabel:`Launch Stack`."
-msgstr ":guilabel:`スタックの起動` をクリックします。"
-
-msgid ""
-"Click :guilabel:`Launch` to create a stack. The :guilabel:`Stacks` tab shows "
-"the stack."
-msgstr ""
-":guilabel:`起動` をクリックして、スタックを作成します。:guilabel:`スタック` "
-"タブにスタックが表示されます。"
-
-# #-#-#-#-# dashboard_databases.pot (End User Guide 1.0.0) #-#-#-#-#
-# #-#-#-#-# dashboard_launch_instances.pot (End User Guide 1.0.0) #-#-#-#-#
-msgid "Click :guilabel:`Launch`."
-msgstr ":guilabel:`起動` をクリックします。"
-
-msgid "Click :guilabel:`Next`."
-msgstr ":guilabel:`次へ` をクリックします。"
-
-msgid "Click :guilabel:`Resize Database Instance`."
-msgstr ":guilabel:`データベースインスタンスのリサイズ` をクリックします。"
-
-msgid "Click :guilabel:`Resize Database Volume`."
-msgstr ":guilabel:`データベースボリュームのリサイズ` をクリックします。"
-
-msgid "Click :guilabel:`Update Object`."
-msgstr ":guilabel:`オブジェクトの更新` をクリックします。"
-
-msgid "Click :guilabel:`Update`."
-msgstr ":guilabel:`更新` をクリックします。"
-
-msgid "Click :guilabel:`Upload File`."
-msgstr ":guilabel:`ファイルのアップロード` をクリックします。"
-
-msgid "Click :guilabel:`Upload Object`."
-msgstr ":guilabel:`オブジェクトのアップロード` をクリックします。"
-
-msgid ""
-"Click on the :guilabel:`Network Name` of the network in which the port has "
-"to be created."
-msgstr ""
-"ポートを作成するネットワークの :guilabel:`ネットワーク名` をクリックします。"
-
-msgid "Click the :guilabel:`Create Load Balancer` button."
-msgstr ":guilabel:`ロードバランサーの作成` ボタンをクリックします。"
-
-msgid ""
-"Click the :guilabel:`Floating IPs` tab, which shows the floating IP "
-"addresses allocated to instances."
-msgstr ""
-":guilabel:`Floating IP` タブをクリックします。インスタンスに関連付けられた "
-"Floating IP アドレスが表示されます。"
-
-msgid ""
-"Click the :guilabel:`Key Pairs` tab, which shows the key pairs that are "
-"available for this project."
-msgstr ""
-":guilabel:`キーペア` タブをクリックします。このプロジェクトに利用可能なキーペ"
-"アが表示されます。"
-
-msgid ""
-"Click the :guilabel:`Launch` button. The new database instance appears in "
-"the databases list."
-msgstr ""
-":guilabel:`起動` ボタンをクリックします。新しいデータベースインスタンスがデー"
-"タベース一覧に表示されます。"
-
-msgid ""
-"Click the :guilabel:`Restore From Database` tab and make sure that this new "
-"instance is based on the correct backup."
-msgstr ""
-":guilabel:`データベースからのリストア` タブをクリックします。この新しいインス"
-"タンスが適切なバックアップからリストアされていることを確認します。"
-
-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 ""
-"ページの右上にあるユーザードロップダウンメニューの :guilabel:`設定` ボタンを"
-"クリックすると、 :guilabel:`設定` タブが表示されます。"
-
-msgid "Click the :guilabel:`Upload File` icon."
-msgstr ":guilabel:`ファイルのアップロード` のアイコンをクリックします。"
-
-msgid ""
-"Click the menu button and choose :guilabel:`Copy` from the dropdown list."
-msgstr ""
-"メニューボタンをクリックして、ドロップダウンリストから :guilabel:`コピー` を"
-"選択します。"
-
-msgid ""
-"Click the menu button and choose :guilabel:`Edit` from the dropdown list."
-msgstr ""
-"メニューボタンをクリックして、ドロップダウンリストから :guilabel:`編集` を選"
-"択します。"
-
-msgid "Commands"
-msgstr "コマンド"
-
-msgid "Comparison of static and dynamic large objects"
-msgstr "静的ラージオブジェクトと動的ラージオブジェクトの比較"
-
-msgid "Compute"
-msgstr "Compute"
-
-msgid "Compute (nova)"
-msgstr "Compute (nova)"
-
-msgid "Configuration drive contents"
-msgstr "コンフィグドライブの内容"
-
-msgid "Configuration drive format"
-msgstr "コンフィグドライブのフォーマット"
-
-# #-#-#-#-# cli_nova_configure_access_security_for_instances.pot (End User
-# Guide 1.0.0) #-#-#-#-#
-# #-#-#-#-# configure_access_and_security_for_instances.pot (End User Guide
-# 1.0.0) #-#-#-#-#
-# #-#-#-#-# sdk_configure_access_security_instances.pot (End User Guide
-# 1.0.0) #-#-#-#-#
-msgid "Configure access and security for instances"
-msgstr "インスタンスのアクセスとセキュリティーの設定"
-
-msgid "Confirm the resize,for example:"
-msgstr "例えば、リサイズされたことを確認します。"
-
-msgid "Confirm your changes."
-msgstr "変更を確認します。"
-
-msgid "Connect to your instance by using SSH"
-msgstr "インスタンスへの SSH 接続"
-
-msgid "Contents"
-msgstr "内容"
-
-msgid "Copy the IP address for your instance."
-msgstr "インスタンスの IP アドレスをコピーします。"
-
-msgid ""
-"Copy the administrative password value from the ``adminPass`` field. Use the "
-"password to log in to your server."
-msgstr ""
-"``adminPass`` フィールドから管理者パスワードの値をコピーして、このパスワード"
-"を使用してサーバーにログインします。"
-
-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 ""
-"出力の ``id`` フィールドからサーバー ID の値をコピーします。この ID を使用し"
-"てサーバーの詳細を取得するか、サーバーを削除します。"
-
-msgid "Copying the manifest object"
-msgstr "マニフェストオブジェクトのコピー"
-
-msgid "Count"
-msgstr "数"
-
-msgid "Create a Legacy Client Object"
-msgstr "従来のクライアントオブジェクトの作成"
-
-msgid "Create a ``current`` container to store current versions of objects."
-msgstr ""
-"最新バージョンのオブジェクトを保存するための ``current`` コンテナーを作成しま"
-"す。"
-
-msgid "Create a bare-metal node"
-msgstr "ベアメタルノードの作成"
-
-msgid "Create a bootable volume for the instance to reside on after shutdown."
-msgstr ""
-"インスタンスがシャットダウン後に保存される、ブート可能なボリュームを作成しま"
-"す。"
-
-msgid ""
-"Create a bootable volume from an image. Cinder makes a volume bootable when "
-"``--image`` parameter is passed."
-msgstr ""
-"イメージからブート可能なボリュームを作成します。 Cinder は ``--image`` パラ"
-"メーターを渡すと、ボリュームをブート可能に設定します。"
-
-msgid ""
-"Create a cluster by using the :command:`trove cluster-create` command. This "
-"command creates a one-shard cluster. Pass in:"
-msgstr ""
-":command:`trove cluster-create` コマンドを使用して、クラスターを作成します。"
-"このコマンドは、以下を渡して、シャード 1 つのクラスターを作成します。"
-
-msgid "Create a container"
-msgstr "コンテナーの作成"
-
-msgid "Create a database instance"
-msgstr "データベースインスタンスの作成"
-
-msgid "Create a file on the volume"
-msgstr "ボリュームへのファイルの作成"
-
-msgid "Create a flavor named m1.tiny"
-msgstr "m1.tiny という名前のフレーバーを作成します。"
-
-msgid "Create a flavor."
-msgstr "フレーバーを作成します。"
-
-msgid "Create a load balancer"
-msgstr "ロードバランサーの作成"
-
-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 ""
-"マニフェストオブジェクトを作成します。マニフェストオブジェクトの最後に ``?"
-"multipart-manifest=put`` クエリー文字列を含め、これがマニフェストオブジェクト"
-"であることを示します。"
-
-msgid "Create a mountpoint"
-msgstr "マウントポイントの作成"
-
-msgid "Create a network"
-msgstr "ネットワークの作成"
-
-msgid "Create a network with specified provider network type."
-msgstr "指定のプロバイダーネットワークタイプでネットワークを作成します。"
-
-msgid "Create a network:"
-msgstr "ネットワークを作成します。"
-
-msgid ""
-"Create a new instance that will be a replica of the original instance. You "
-"do this by passing in the ``--replica_of`` option with the :command:`trove "
-"create` command. This example creates a replica called ``replica_1``. "
-"``replica_1`` is a replica of the original instance, ``base_1``:"
-msgstr ""
-"元のインスタンスの複製になる、新しいインスタンスを作成します。 :command:"
-"`trove create` コマンドに ``--replica_of`` オプションを渡して実行します。こ"
-"の例は、``replica_1`` という名前の複製を作成します。``replica_1`` は、元のイ"
-"ンスタンス ``base_1`` の複製です。"
-
-msgid "Create a new volume"
-msgstr "新しいボリュームの作成"
-
-msgid ""
-"Create a non-bootable volume and attach that volume to an instance that you "
-"boot from an image."
-msgstr ""
-"ブート不可ボリュームを作成し、イメージから起動するインスタンスにそのボリュー"
-"ムを接続します。"
-
-msgid "Create a non-bootable volume."
-msgstr "ブート不可ボリュームを作成します。"
-
-msgid "Create a port"
-msgstr "ポートの作成"
-
-msgid "Create a port with specified IP address:"
-msgstr "指定の IP アドレスでポートを作成します。"
-
-msgid "Create a port without specified IP address:"
-msgstr "IP アドレス指定なしでポートを作成します。"
-
-msgid "Create a router"
-msgstr "ルーターの作成"
-
-msgid "Create a router and add a port to the subnet:"
-msgstr "ルーターを作成し、サブネットにポートを追加します。"
-
-msgid "Create a router:"
-msgstr "ルーターを作成します。"
-
-msgid "Create a second version of the object in the ``current`` container:"
-msgstr ""
-"``current`` コンテナーに 2 番目のバージョンのオブジェクトを作成します。"
-
-msgid "Create a share"
-msgstr "共有の作成"
-
-msgid "Create a share from a snapshot."
-msgstr "スナップショットから共有を作成します。"
-
-msgid "Create a share network"
-msgstr "共有ネットワークの作成"
-
-msgid "Create a share network."
-msgstr "共有ネットワークを作成します。"
-
-msgid "Create a share."
-msgstr "共有を作成します。"
-
-msgid "Create a snapshot from a volume"
-msgstr "ボリュームからのスナップショットの作成"
-
-msgid "Create a snapshot of the instance"
-msgstr "インスタンスのスナップショットの作成"
-
-msgid "Create a snapshot."
-msgstr "スナップショットを作成します。"
-
-msgid "Create a stack from an example template file"
-msgstr "サンプルテンプレートファイルからのスタックの作成"
-
-msgid "Create a subnet"
-msgstr "サブネットの作成"
-
-msgid "Create a subnet:"
-msgstr "サブネットを作成します。"
-
-msgid "Create a volume"
-msgstr "ボリュームの作成"
-
-msgid "Create a volume from an image and boot an instance from that volume."
-msgstr ""
-"イメージからボリュームを作成し、そのボリュームからインスタンスを起動します。"
-
-msgid "Create an ``archive`` container to store older versions of objects:"
-msgstr ""
-"古いバージョンのオブジェクトを保存するための ``archive`` コンテナーを作成しま"
-"す。"
-
-msgid "Create an additional container to hold previous versions:"
-msgstr "追加のコンテナーを作成して、前のバージョンを保持します。"
-
-msgid "Create an archive for auto-extract"
-msgstr "自動展開用アーカイブの作成"
-
-msgid ""
-"Create an auto-scaling stack by running the following command. The ``-f`` "
-"option specifies the name of the stack template file, and the ``-P`` option "
-"specifies the ``KeyName`` parameter as ``heat_key``:"
-msgstr ""
-"以下のコマンドを実行して、オートスケールするスタックを作成します。``-f`` オプ"
-"ションは、スタックテンプレートファイルの名前を指定します。 ``-P`` オプション"
-"は、 ``KeyName`` パラメーターを ``heat_key`` に指定します。::"
-
-msgid "Create an image"
-msgstr "イメージの作成"
-
-# #-#-#-#-# cli_cheat_sheet.pot (End User Guide 1.0.0) #-#-#-#-#
-# #-#-#-#-# dashboard_launch_instances.pot (End User Guide 1.0.0) #-#-#-#-#
-msgid "Create an instance snapshot"
-msgstr "インスタンスのスナップショットの作成"
-
-msgid "Create and access a database"
-msgstr "データベースの作成とアクセス"
-
-msgid "Create and manage containers"
-msgstr "コンテナーの作成と管理"
-
-# #-#-#-#-# dashboard_databases.pot (End User Guide 1.0.0) #-#-#-#-#
-# #-#-#-#-# trove-manage-db.pot (End User Guide 1.0.0) #-#-#-#-#
-msgid "Create and manage databases"
-msgstr "データベースの作成と管理"
-
-# #-#-#-#-# cli_create_and_manage_networks.pot (End User Guide 1.0.0)
-# #-#-#-#-#
-# #-#-#-#-# dashboard_create_networks.pot (End User Guide 1.0.0) #-#-#-#-#
-msgid "Create and manage networks"
-msgstr "ネットワークの作成と管理"
-
-msgid "Create and manage object containers"
-msgstr "オブジェクトコンテナーの作成と管理"
-
-# #-#-#-#-# cli_nova_configure_access_security_for_instances.pot (End User
-# Guide 1.0.0) #-#-#-#-#
-# #-#-#-#-# sdk_configure_access_security_instances.pot (End User Guide
-# 1.0.0) #-#-#-#-#
-msgid "Create and manage security group rules"
-msgstr "セキュリティーグループのルールの作成と管理"
-
-# #-#-#-#-# cli_nova_configure_access_security_for_instances.pot (End User
-# Guide 1.0.0) #-#-#-#-#
-# #-#-#-#-# sdk_configure_access_security_instances.pot (End User Guide
-# 1.0.0) #-#-#-#-#
-msgid "Create and manage security groups"
-msgstr "セキュリティーグループの作成と管理"
-
-msgid "Create and manage shares"
-msgstr "ファイル共有の作成と管理"
-
-msgid "Create and manage stacks"
-msgstr "スタックの管理と作成"
-
-msgid "Create and manage volumes"
-msgstr "ボリュームの作成と管理"
-
-msgid "Create and use incremental backups"
-msgstr "増分バックアップの作成および使用"
-
-msgid "Create at least one key pair for each project."
-msgstr "プロジェクトごとに少なくとも 1 つのキーペアを作成します。"
-
-msgid "Create keypair"
-msgstr "キーペアの作成"
-
-# #-#-#-#-# cli_cheat_sheet.pot (End User Guide 1.0.0) #-#-#-#-#
-# #-#-#-#-# sdk_neutron_apis.pot (End User Guide 1.0.0) #-#-#-#-#
-msgid "Create network"
-msgstr "ネットワークの作成"
-
-msgid "Create networks"
-msgstr "ネットワークの作成"
-
-# #-#-#-#-# cli_create_and_manage_networks.pot (End User Guide 1.0.0)
-# #-#-#-#-#
-# #-#-#-#-# sdk_neutron_apis.pot (End User Guide 1.0.0) #-#-#-#-#
-msgid "Create ports"
-msgstr "ポートの作成"
-
-msgid "Create router and add port to subnet"
-msgstr "ルーターの作成とサブネットへのポートの追加"
-
-msgid "Create router: complete code listing example"
-msgstr "ルーターの作成: サンプルコード全体"
-
-msgid "Create routers"
-msgstr "ルーターの作成"
-
-msgid "Create security service"
-msgstr "セキュリティーサービスの作成"
-
-msgid "Create server (API v2)"
-msgstr "サーバーの作成 (API v2)"
-
-msgid "Create server code listing example"
-msgstr "サーバーの作成のサンプルコード全体"
-
-msgid "Create share from snapshot"
-msgstr "共有からのスナップショットの作成"
-
-msgid "Create share network"
-msgstr "ファイル共有ネットワークの作成"
-
-msgid "Create snapshot"
-msgstr "スナップショットの作成"
-
-msgid "Create static website"
-msgstr "静的 Web サイトの作成"
-
-msgid "Create subnets"
-msgstr "サブネットの作成"
-
-msgid "Create the first version of an object in the ``current`` container:"
-msgstr "``current`` コンテナーに最初のバージョンのオブジェクトを作成します。"
-
-msgid "Create the volume:"
-msgstr "ボリュームを作成します。"
-
-msgid "Create volume from image and boot instance"
-msgstr "イメージからのボリュームの作成とインスタンスの起動"
-
-msgid "Creates a bare-metal node."
-msgstr "ベアメタルノードを作成します。"
-
-msgid ""
-"Creating and managing ports requires administrator privileges. Contact an "
-"administrator before adding or changing ports."
-msgstr ""
-"ポートの作成や管理を行うには管理者特権が必要です。ポートの追加や変更を行う際"
-"には管理者と連絡を取ってください。"
-
-msgid "Customization Script Source"
-msgstr "カスタマイズスクリプトの入力方法"
-
-msgid "Database"
-msgstr "データベース"
-
-msgid "Database Instance"
-msgstr "データベースインスタンス"
-
-msgid "Database flavor: ``6``"
-msgstr "Database フレーバー: ``6``"
-
-msgid "Databases: ``db1`` and ``db2``"
-msgstr "データベース: ``db1`` および ``db2``"
-
-msgid "Delete a cluster, using the :command:`trove cluster-delete` command."
-msgstr ""
-":command:`trove cluster-delete` コマンドを使用して、クラスターを削除します。"
-
-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 ""
-":command:`trove configuration-delete` コマンドを使用して、設定グループを削除"
-"します。グループを使用するインスタンスが無い場合、削除したいかもしれません。"
-
-msgid ""
-"Delete a floating IP from the project which automatically deletes that IP's "
-"associations."
-msgstr ""
-"プロジェクトから Floating IP アドレスを削除します。削除すると、その IP の割り"
-"当てが自動的に解除されます。"
-
-msgid "Delete a load balancer"
-msgstr "ロードバランサーの削除"
-
-msgid "Delete a network"
-msgstr "ネットワークの削除"
-
-msgid "Delete a security group rule"
-msgstr "セキュリティーグループのルールの削除"
-
-msgid "Delete a security service"
-msgstr "セキュリティーサービスの削除"
-
-msgid "Delete a share"
-msgstr "ファイル共有の削除"
-
-msgid "Delete a share network"
-msgstr "ファイル共有ネットワークの削除"
-
-msgid "Delete a share."
-msgstr "共有を削除します。"
-
-msgid "Delete a snapshot."
-msgstr "スナップショットを削除します。"
-
-msgid "Delete a stack"
-msgstr "スタックの削除"
-
-msgid "Delete a volume"
-msgstr "ボリュームの削除"
-
-msgid "Delete an image"
-msgstr "イメージの削除"
-
-msgid "Delete an instance"
-msgstr "インスタンスの削除"
-
-msgid "Delete network: complete code listing example"
-msgstr "ネットワークの削除: サンプルコード全体"
-
-msgid "Delete server (API v2)"
-msgstr "サーバーの削除 (API v2)"
-
-msgid "Delete server code example"
-msgstr "サーバーの削除のサンプルコード"
-
-msgid "Delete share"
-msgstr "共有の削除"
-
-msgid "Delete snapshot"
-msgstr "スナップショットの削除"
-
-msgid "Delete specified image"
-msgstr "指定したイメージの削除"
-
-msgid "Delete the instance using the following command."
-msgstr "以下のコマンドを使用して、インスタンスを削除します。"
-
-msgid "Delete the network:"
-msgstr "ネットワークを削除します。"
-
-msgid ""
-"Deletion of images is permanent and **cannot** be reversed. Only users with "
-"the appropriate permissions can delete images."
-msgstr ""
-"イメージの削除は、永続的であり、元に戻せ**ません**。適切なパーミッションを持"
-"つユーザーのみが、イメージを削除できます。"
-
-msgid "Deny access"
-msgstr "アクセスの拒否"
-
-msgid "Deny access."
-msgstr "アクセスを拒否します。"
-
-msgid ""
-"Depending on the parameters that you provide, the command returns a list of "
-"server properties."
-msgstr ""
-"指定のパラメーターにより、コマンドはサーバーのプロパティ一覧を返します。"
-
-msgid ""
-"Depending on the source that you select, browse to the file location, "
-"directly include the environment"
-msgstr ""
-"選択したソースに応じて、ファイルの場所を指定するか、環境を直接取り込みます。"
-
-msgid ""
-"Depending on the source that you select, enter the URL, browse to the file "
-"location, or directly include the template."
-msgstr ""
-"選択するソースに応じて、URL を入力する、ファイルの場所を指定する、テンプレー"
-"トを直接取り込みます。"
-
-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 ""
-"お使いのロールに応じて、仮想マシンイメージをアップロード、管理する権限がある"
-"かもしれません。運用者は、イメージのアップロードや管理をクラウド管理者や運用"
-"者のみに制限するかもしれません。適切な権限を持っていれば、ダッシュボードの "
-"admin プロジェクトで、イメージをアップロードおよび管理できます。"
-
-msgid "Describe a specific image"
-msgstr "指定したイメージの詳細表示"
-
-# #-#-#-#-# cli_swift_large_object_creation.pot (End User Guide 1.0.0)
-# #-#-#-#-#
-# #-#-#-#-# cli_swift_serialized_response_formats.pot (End User Guide 1.0.0)
-# #-#-#-#-#
-msgid "Description"
-msgstr "説明"
-
-msgid "Detach a volume from an instance"
-msgstr "ボリュームのインスタンスからの切断"
-
-msgid "Details"
-msgstr "詳細"
-
-msgid "Determine whether the ``vm1`` server exists:"
-msgstr "``vm1`` サーバーが存在するかどうかを確認します。"
-
-msgid "Direct REST calls via keystoneauth"
-msgstr "keystoneauth を使った REST の直接呼び出し"
-
-msgid ""
-"Disassociate a configuration group from a database instance, using the :"
-"command:`trove configuration-detach` command."
-msgstr ""
-":command:`trove configuration-detach` コマンドを使用して、データベースインス"
-"タンスから設定グループを解除します。"
-
-msgid "Disassociate a floating IP address from an instance in the project."
-msgstr ""
-"プロジェクトのインスタンスから Floating IP アドレスの割り当てを解除します。"
-
-msgid "Disassociate floating IP addresses"
-msgstr "Floating IP アドレスの割り当て解除"
-
-msgid "Discoverability"
-msgstr "発見可能性"
-
-msgid "Disk (GB)"
-msgstr "ディスク (GB)"
-
-msgid ""
-"Display information about a cluster by using the :command:`trove cluster-"
-"show` command. Pass in the ID of the cluster."
-msgstr ""
-":command:`trove cluster-show` コマンドを使用して、クラスターに関する情報を表"
-"示します。クラスターの ID を渡します。"
-
-msgid "Display information for the account, container, or object"
-msgstr "アカウント、コンテナー、オブジェクトの情報表示"
-
-msgid "Display the ``sync_binlog`` setting again:"
-msgstr "再び ``sync_binlog`` 設定を表示します。"
-
-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 ""
-"コンフィグドライブにある EC2 メタデータに依存しないようにしてください。この内"
-"容は将来のリリースで削除される可能性があります。たとえば、``ec2`` ディレクト"
-"リにあるファイルに依存しないでください。"
-
-msgid "Download binary image data"
-msgstr "バイナリーイメージデータのダウンロード"
-
-msgid "Download the snapshot as an image"
-msgstr "イメージとしてスナップショットのダウンロード"
-
-msgid ""
-"Download the snapshot by using the image ID that was returned in the "
-"previous step:"
-msgstr ""
-"前の手順で返されたイメージ ID を使用してスナップショットをダウンロードしま"
-"す。"
-
-msgid "Dynamic large object"
-msgstr "動的ラージオブジェクト"
-
-msgid "Dynamic large objects"
-msgstr "動的ラージオブジェクト"
-
-msgid "EC2 metadata format"
-msgstr "EC2 メタデータの形式"
-
-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 ""
-"各 OpenStack プロジェクトには、独自の Python ライブラリがそれぞれ存在します。"
-"これらのライブラリは、コマンドラインクライアントに同梱されています。例えば、"
-"Compute API の Python バインドは python-novaclient パッケージに同梱されていま"
-"す。"
-
-msgid ""
-"Each OpenStack project produces a client library that wraps its own REST "
-"API. Unless there is no other choice for some reason, the per-project "
-"libraries should be avoided."
-msgstr ""
-"各 OpenStack プロジェクトは、自身のプロジェクトの REST API を呼び出すクライア"
-"ントライブラリーを持っています。何らかの理由で他に選択肢がない場合を除き、プ"
-"ロジェクト毎のライブラリーを使うのは避けるべきです。"
-
-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 ""
-"各クラスターには、少なくとも 1 つのクエリールーターと 1 つの設定サーバーがあ"
-"ります。クエリールーターと設定サーバーは、クォータの計数対象になります。クラ"
-"スターを削除するとき、関連するクエリールーターと設定サーバーも削除されます。"
-
-msgid "Each cluster includes:"
-msgstr "各クラスターは以下のものを持ちます。"
-
-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 ""
-"各インスタンスは、プライベートな Fixed IP アドレスを持ちます。また、パブリッ"
-"クな Floating IP アドレスも持てます。プライベート IP アドレスは、インスタンス"
-"間の通信に使用されます。パブリックアドレスは、インターネットなどのクラウド外"
-"のネットワークと通信するために使用されます。"
-
-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 ""
-"あるロードバランサーでトラフィックをリッスンするポート番号は個別に設定でき、"
-"ロードバランサーに関連付けできます。同じロードバランサーに複数のリスナーを関"
-"連付けできます。"
-
-msgid "Edit a volume"
-msgstr "ボリュームの編集"
-
-msgid "Edit security service"
-msgstr "セキュリティーサービスの編集"
-
-msgid "Edit share"
-msgstr "ファイル共有の編集"
-
-msgid "Edit share metadata"
-msgstr "ファイル共有のメタデータの編集"
-
-msgid "Edit share network"
-msgstr "ファイル共有ネットワークの編集"
-
-msgid "Enable CSS for file listing"
-msgstr "ファイル一覧表示向けの CSS の有効化"
-
-msgid "Enable and access the configuration drive"
-msgstr "コンフィグドライブの有効化とアクセス"
-
-msgid "Enable file listing"
-msgstr "ファイル一覧表示の有効化"
-
-msgid "Enable object versioning on your desired container:"
-msgstr "希望するコンテナーにオブジ¥ェクトのバージョニングを有効化します。"
-
-msgid "End-to-end integrity"
-msgstr "エンド間の完全性"
-
-msgid ""
-"Ensure that you use at least version 0.3.1 of CirrOS for configuration drive "
-"support."
-msgstr ""
-"必ずコンフィグドライブをサポートする CirrOS バージョン 0.3.1 以降を利用してく"
-"ださい。"
-
-msgid "Enter a brief description of the image."
-msgstr "イメージの簡単な説明を入力します。"
-
-msgid "Enter a name for the image."
-msgstr "イメージの名前を入力します。"
-
-msgid "Enter a name for the object."
-msgstr "オブジェクトの名前を入力します。"
-
-msgid "Enter a name for the pseudo-folder."
-msgstr "擬似フォルダーの名前を入力します。"
-
-msgid "Enter a name to identify the stack."
-msgstr "スタックを識別するための名前を入力します。"
-
-msgid "Enter new values for any parameters that you want to update."
-msgstr "更新したいパラメーターの新しい値を入力します。"
-
-msgid "Enter the following values:"
-msgstr "以下の値を入力します。"
-
-msgid ""
-"Enter the name of the device from which the volume is accessible by the "
-"instance."
-msgstr "インスタンスがボリュームにアクセスできる、デバイスの名前を入力します。"
-
-msgid "Environment variables required to run examples"
-msgstr "サンプル実行に必要な環境変数"
-
-msgid "Environment variables via an openrc.sh file"
-msgstr "openrc.sh ファイルで定義される環境変数"
-
-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 ""
-"エラーページは、設定したエラーページの名前の前にステータスコードを付けて処理"
-"されます。例えば、``X-Container-Meta-Web-Error`` を ``error.html`` に設定した"
-"場合、401 エラーは ``401error.html`` のページが表示されます。同様に 404 エ"
-"ラーは ``404error.html`` が表示されます。``X-Container-Meta-Web-Error`` メタ"
-"データを設定するとき、これらのページをコンテナーに作成する必要があります。ま"
-"たは、汎用のエラーページを表示します。"
-
-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 ""
-"エラー。オブジェクトの名前、削除に失敗したオブジェクトに関連するエラー状態の"
-"一覧。この形式は、``Accept`` ヘッダーに設定した値により決まります。"
-
-msgid "Events"
-msgstr "イベント"
-
-msgid "Example:"
-msgstr "例:"
-
-msgid "Example 1. JSON example with format query parameter"
-msgstr "例 1. format クエリーパラメーターを用いた JSON の例"
-
-msgid "Example 2. XML example with Accept header"
-msgstr "例 2. Accept ヘッダーを用いた XML の例"
-
-msgid "Extend share"
-msgstr "共有の拡張"
-
-msgid "Extend share."
-msgstr "共有を拡張します。"
-
-msgid "Extra transaction information"
-msgstr "拡張トランザクション情報"
-
-msgid ""
-"Find out what instances are using a configuration group, using the :command:"
-"`trove configuration-instances` command."
-msgstr ""
-":command:`trove configuration-instances` コマンドを使用して、どのインスタンス"
-"が設定グループを使用しているか見つけます。"
-
-msgid ""
-"First, determine which configuration options you can set. Different data "
-"store versions have different configuration options."
-msgstr ""
-"まず、どの設定オプションを設定できるのかを確認します。異なるデータストアの"
-"バージョンは、異なる設定オプションを持ちます。"
-
-msgid ""
-"First, get the ID of the ``guest1`` database instance by using the :command:"
-"`trove list` command:"
-msgstr ""
-"まず、 :command:`trove list` コマンドを使用して、``guest1`` データベースイン"
-"スタンスの ID を取得します。"
-
-msgid ""
-"First, use the :command:`trove list` command to list all instances and their "
-"IDs:"
-msgstr ""
-"まず、 :command:`trove list` コマンドを使用して、すべてのインスタンスとその "
-"ID を一覧表示します。"
-
-msgid "Flavor"
-msgstr "フレーバー"
-
-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 ""
-"フレーバー ID: まだ使用されていない ID を使用する必要があります。この例では、"
-"ID 1 から 5 までが使用済みなので、ID ``6`` を使用します。"
-
-msgid "Flavor ID: ``10``"
-msgstr "フレーバー ID: ``10``"
-
-msgid "Flavor name: ``mysql_minimum``"
-msgstr "フレーバー名: ``mysql_minimum``"
-
-msgid "Follow the steps below to launch an instance from an image."
-msgstr "以下の手順に従って、インスタンスをイメージから起動します。"
-
-msgid "Follow this procedure to update an existing image."
-msgstr "既存のイメージを更新する場合、この手順を実行します。"
-
-msgid "Follow this procedure to upload an image to a project:"
-msgstr "以下の手順に従い、イメージをプロジェクトにアップロードします。 "
-
-msgid "For ``get_credentials`` see :ref:`Get credentials `."
-msgstr ""
-"``get_credentials`` は :ref:`Get credentials ` を参照してく"
-"ださい。"
-
-msgid "For ``get_credentials``, see :ref:`Get credentials `."
-msgstr ""
-"``get_credentials`` は :ref:`Get credentials ` を参照してく"
-"ださい。"
-
-msgid ""
-"For ``get_nova_credentials``, see :ref:`Get Nova credentials `."
-msgstr ""
-"``get_nova_credentials`` は :ref:`Get Nova credentials ` を参照してください。"
-
-msgid "For ``print_values``, see :ref:`Print values `."
-msgstr ""
-"``print_values`` は :ref:`Print values ` を参照してください。"
-
-msgid ""
-"For details about how to install the clients, see :doc:`../common/cli-"
-"install-openstack-command-line-clients`."
-msgstr ""
-"クライアントのインストール方法に関する詳細は、:doc:`../common/cli-install-"
-"openstack-command-line-clients` を参照してください。"
-
-msgid ""
-"For details on creating images, see `Creating images manually `_ in the *OpenStack "
-"Virtual Machine Image Guide*."
-msgstr ""
-"イメージ作成の詳細は、*OpenStack 仮想マシンイメージガイド* の `イメージの手動"
-"作成 `_ を参照してください。"
-
-msgid ""
-"For each NIC on the node, you must create an interface, specifying the "
-"interface's MAC address."
-msgstr ""
-"ノードの各 NIC は、インターフェースの MAC アドレスを指定して、インターフェー"
-"スを作成する必要があります。"
-
-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 ""
-"現在のプロジェクトに確保されている各 Floating IP アドレスに対して、このコマン"
-"ドは、Floating IP アドレス、Floating IP アドレスが割り当てられたインスタンス"
-"の ID、関連付けられた Fixed IP アドレス、Floating IP アドレスが確保されたプー"
-"ルを出力します。"
-
-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 ""
-"例えば、tar アーカイブの 1 番目のオブジェクトが ``/home/file1.txt`` であり、"
-"パスに ``/v1/12345678912345/mybackup/castor/`` を指定する場合、この処理によ"
-"り、``12345678912345`` アカウントの ``mybackup`` コンテナーに ``castor/home/"
-"file1.txt`` が作成されます。"
-
-msgid ""
-"For example, if your MySQL data store name is set to ``mysql``, your entry "
-"would look like this:"
-msgstr ""
-"例えば、MySQL データストアの名前が ``mysql`` に設定されている場合、このように"
-"なるでしょう。"
-
-msgid ""
-"For example, this request uses the ``format`` query parameter to ask for a "
-"JSON response:"
-msgstr ""
-"例えば、このリクエストは ``format`` クエリーパラメーターを使用して、JSON 応答"
-"を要求します。"
-
-msgid ""
-"For example, you can include extra transaction information when you upload "
-"large objects such as images."
-msgstr ""
-"例えば、イメージなどのラージオブジェクトをアップロードする際に追加のトランザ"
-"クション情報を含めることができます。"
-
-msgid "For example:"
-msgstr "例:"
-
-msgid ""
-"For further information and comparisons (including security considerations), "
-"see the `Security Guide `__."
-msgstr ""
-"詳細や比較情報 (セキュリティー考慮事項を含む) は、`セキュリティーガイド "
-"`__ を参照してくださ"
-"い。"
-
-msgid ""
-"For information and examples on more advanced use of neutron's ``subnet`` "
-"subcommand, see the `OpenStack Administrator Guide `__."
-msgstr ""
-"neutron の ``subnet`` サブコマンドの高度な使用法に関する詳細と例は、"
-"`OpenStack Administrator Guide `__ を参照してください。"
-
-msgid ""
-"For instance, the Rackspace public cloud is an OpenStack deployment that has "
-"an optional custom authentication back end. While normal keystone password "
-"authentication works perfectly well, you may want to use the custom "
-"Rackspace keystoneauth API Key plugin found in `rackspace-keystoneauth-"
-"plugin