From 489e80b2ef2ad71f92df3719c0606fd02afd6fa8 Mon Sep 17 00:00:00 2001 From: OpenStack Proposal Bot Date: Fri, 3 Jun 2016 07:12:18 +0000 Subject: [PATCH] Imported Translations from Zanata For more information about this automatic import see: https://wiki.openstack.org/wiki/Translations/Infrastructure Change-Id: Ie7d07bb29ce9857ea87a7660419f1841b4c1825a --- .../locale/de/LC_MESSAGES/api-quick-start.po | 13 +- .../locale/ja/LC_MESSAGES/api-quick-start.po | 21 +- .../ko_KR/LC_MESSAGES/api-quick-start.po | 15 +- .../LC_MESSAGES/api-quick-start.po} | 659 ++- api-ref-guides/locale/api-ref-guides.pot | 176 - api-ref/locale/api-ref.pot | 3840 ----------------- api-ref/locale/fr.po | 5 +- firstapp/source/locale/firstapp.pot | 3726 ---------------- 8 files changed, 319 insertions(+), 8136 deletions(-) rename api-quick-start/source/locale/{api-quick-start.pot => zh_CN/LC_MESSAGES/api-quick-start.po} (53%) delete mode 100644 api-ref-guides/locale/api-ref-guides.pot delete mode 100644 api-ref/locale/api-ref.pot delete mode 100644 firstapp/source/locale/firstapp.pot diff --git a/api-quick-start/source/locale/de/LC_MESSAGES/api-quick-start.po b/api-quick-start/source/locale/de/LC_MESSAGES/api-quick-start.po index fbad7b14d..925e5ce91 100644 --- a/api-quick-start/source/locale/de/LC_MESSAGES/api-quick-start.po +++ b/api-quick-start/source/locale/de/LC_MESSAGES/api-quick-start.po @@ -1,14 +1,15 @@ # Andreas Jaeger , 2015. #zanata # OpenStack Infra , 2015. #zanata +# Andreas Jaeger , 2016. #zanata msgid "" msgstr "" "Project-Id-Version: API-Quick-Start 0.1\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2016-01-19 03:21+0000\n" +"POT-Creation-Date: 2016-06-03 05:11+0000\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" -"PO-Revision-Date: 2015-10-10 07:10+0000\n" +"PO-Revision-Date: 2016-06-01 09:51+0000\n" "Last-Translator: Andreas Jaeger \n" "Language: de\n" "Plural-Forms: nplurals=2; plural=(n != 1)\n" @@ -27,6 +28,9 @@ msgstr "**REST Clients**" msgid "**cURL**" msgstr "**cURL**" +msgid "*tenantId* (Optional)" +msgstr "*tenantId* (Optional)" + msgid "*tenantName* (Optional)" msgstr "*tenantName* (optional)" @@ -200,6 +204,11 @@ msgstr "" "python.org/pypi>`__ bekommen. Außerdem lässt Sie ``pip`` Pakete " "aktualisieren oder entfernen. " +msgid "Use the Compute API to list images:" +msgstr "" +"Benutzen Sie die Compute API wie folgt, um eine Liste von Abbildern " +"anzuzeigen:" + msgid "" "Use this SDK to write Python automation scripts that create and manage " "resources in your OpenStack cloud. The SDK implements Python bindings to the " diff --git a/api-quick-start/source/locale/ja/LC_MESSAGES/api-quick-start.po b/api-quick-start/source/locale/ja/LC_MESSAGES/api-quick-start.po index 995c3eea4..79bda3619 100644 --- a/api-quick-start/source/locale/ja/LC_MESSAGES/api-quick-start.po +++ b/api-quick-start/source/locale/ja/LC_MESSAGES/api-quick-start.po @@ -5,11 +5,11 @@ msgid "" msgstr "" "Project-Id-Version: API-Quick-Start 0.1\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2016-04-12 16:15+0000\n" +"POT-Creation-Date: 2016-06-03 05:11+0000\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" -"PO-Revision-Date: 2016-02-09 06:36+0000\n" +"PO-Revision-Date: 2016-06-03 06:18+0000\n" "Last-Translator: KATO Tomoyuki \n" "Language: ja\n" "Plural-Forms: nplurals=1; plural=0\n" @@ -134,6 +134,19 @@ msgstr "" "す。以下の例は、TryStack エンドポイントを使用しますが、必要に応じて環境変数と" "して `$OS_IDENTITYENDPOINT` を使用することもできます。" +msgid "" +"For complete information about the OpenStack clients, including how to " +"source the ``openrc`` file, see `OpenStack End User Guide `__, `OpenStack Administrator Guide `__, and `OpenStack Command-Line Interface " +"Reference `__." +msgstr "" +"``openrc`` ファイルの読み込み方法など、OpenStack クライアントの詳細は、" +"`OpenStack エンドユーザーガイド `__ 、`OpenStack 管理者ガイド `__ 、" +"`OpenStack Command-Line Interface Reference `__ を参照してください。" + msgid "For example, install the ``openstack`` client:" msgstr "例えば、 以下は ``openstack`` クライアントをインストールします。" @@ -275,8 +288,8 @@ msgstr "" msgid "" "The tenant ID. Both the *tenantId* and *tenantName* are optional and " "mutually exclusive. If you specify both attributes, the server returns the " -"Bad Request (400) response code. If you do not know the tenant name ID, send " -"a request with \"\" for the tenant name or ID. The response returns the " +"Bad Request (400) response code. If you do not know the tenant name or ID, " +"send a request with \"\" for the tenant name or ID. The response returns the " "tenant name or ID." msgstr "" "テナント ID。 *tenantId* と *tenantName* はどちらもオプションですが、両方同時" diff --git a/api-quick-start/source/locale/ko_KR/LC_MESSAGES/api-quick-start.po b/api-quick-start/source/locale/ko_KR/LC_MESSAGES/api-quick-start.po index a9078ef5a..ea65821df 100644 --- a/api-quick-start/source/locale/ko_KR/LC_MESSAGES/api-quick-start.po +++ b/api-quick-start/source/locale/ko_KR/LC_MESSAGES/api-quick-start.po @@ -5,7 +5,7 @@ msgid "" msgstr "" "Project-Id-Version: API-Quick-Start 0.1\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2016-04-25 15:31+0000\n" +"POT-Creation-Date: 2016-06-03 05:11+0000\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" @@ -277,19 +277,6 @@ msgstr "사용자의 암호입니다." msgid "The payload of credentials to authenticate contains these parameters:" msgstr "인증 credential에 대한 payload는 다음과 같은 매개 변수를 가집니다:" -msgid "" -"The tenant ID. Both the *tenantId* and *tenantName* are optional and " -"mutually exclusive. If you specify both attributes, the server returns the " -"Bad Request (400) response code. If you do not know the tenant name ID, send " -"a request with \"\" for the tenant name or ID. The response returns the " -"tenant name or ID." -msgstr "" -"Tenant ID입니다. *tenantId* 와 *tenantName* 은 선택 사항이며 상호 배타적인 성" -"격을 띱니다. 두 항목을 모두 사용하는 경우, 서버에서는 잘못된 요청 (400) 응답 " -"코드를 반환합니다. tenant 이름에 대한 ID를 알지 못한다면 요청을 보낼 때 " -"tenant 이름 또는 ID를 \"\"으로 보냅니다. 반환 값에서 tenant 이름 또는 ID를 확" -"인할 수 있습니다." - msgid "" "The tenant name. Both the *tenantId* and *tenantName* are optional and " "mutually exclusive. If you specify both attributes, the server returns the " diff --git a/api-quick-start/source/locale/api-quick-start.pot b/api-quick-start/source/locale/zh_CN/LC_MESSAGES/api-quick-start.po similarity index 53% rename from api-quick-start/source/locale/api-quick-start.pot rename to api-quick-start/source/locale/zh_CN/LC_MESSAGES/api-quick-start.po index 284f241ae..bf763e5b8 100644 --- a/api-quick-start/source/locale/api-quick-start.pot +++ b/api-quick-start/source/locale/zh_CN/LC_MESSAGES/api-quick-start.po @@ -1,347 +1,60 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2015, OpenStack contributors -# This file is distributed under the same license as the API-Quick-Start package. -# FIRST AUTHOR , YEAR. -# -#, fuzzy +# OpenStack Infra , 2015. #zanata +# Zheng Xi Zhou , 2016. #zanata +# hanchao <409007319@qq.com>, 2016. #zanata msgid "" msgstr "" "Project-Id-Version: API-Quick-Start 0.1\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2016-04-13 06:01+0000\n" -"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" -"Last-Translator: FULL NAME \n" -"Language-Team: LANGUAGE \n" +"POT-Creation-Date: 2016-06-03 05:11+0000\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" +"PO-Revision-Date: 2016-06-01 03:11+0000\n" +"Last-Translator: hanchao <409007319@qq.com>\n" +"Language: zh-CN\n" +"Plural-Forms: nplurals=1; plural=0\n" +"X-Generator: Zanata 3.7.3\n" +"Language-Team: Chinese (China)\n" -#: ../api-quick-start.rst:5 -msgid "OpenStack APIs" -msgstr "" +msgid "**OpenStack Python Software Development Kit (SDK)**" +msgstr "OpenStack Python软件开发工具包。" -#: ../api-quick-start.rst:7 -msgid "" -"To authenticate access to OpenStack services, you must first issue an " -"authentication request with a payload of credentials to OpenStack Identity " -"to get an authentication token." -msgstr "" +msgid "**OpenStack command-line client**" +msgstr "OpenStack命令行客户端。" -#: ../api-quick-start.rst:11 -msgid "" -"Credentials are usually a combination of your user name and password, and " -"optionally, the name or ID of the tenant where your cloud runs. Ask your " -"cloud administrator for your user name, password, and tenant so that you can " -"generate authentication tokens. Alternatively, you can supply a token rather " -"than a user name and password." -msgstr "" +msgid "**REST clients**" +msgstr "REST客户端。" -#: ../api-quick-start.rst:17 -msgid "" -"When you send API requests, you include the token in the ``X-Auth-Token`` " -"header. If you access multiple OpenStack services, you must get a token for " -"each service. A token is valid for a limited time before it expires. A token " -"can also become invalid for other reasons. For example, if the roles for a " -"user change, existing tokens for that user are no longer valid." -msgstr "" +msgid "**cURL**" +msgstr "cURL" -#: ../api-quick-start.rst:24 -msgid "Authentication and API request workflow" -msgstr "" - -#: ../api-quick-start.rst:26 -msgid "" -"Request an authentication token from the Identity endpoint that your cloud " -"administrator gave you. Send a payload of credentials in the request as " -"shown in :ref:`authenticate`. If the request succeeds, the server returns an " -"authentication token." -msgstr "" - -#: ../api-quick-start.rst:31 -msgid "" -"Send API requests and include the token in the ``X-Auth-Token`` header. " -"Continue to send API requests with that token until the service completes " -"the request or the Unauthorized (401) error occurs." -msgstr "" - -#: ../api-quick-start.rst:35 -msgid "If the Unauthorized (401) error occurs, request another token." -msgstr "" - -#: ../api-quick-start.rst:37 -msgid "" -"The examples in this section use cURL commands. For information about cURL, " -"see http://curl.haxx.se/. For information about the OpenStack APIs, see " -"`OpenStack API Reference `__." -msgstr "" - -#: ../api-quick-start.rst:45 -msgid "Authenticate" -msgstr "" - -#: ../api-quick-start.rst:47 -msgid "The payload of credentials to authenticate contains these parameters:" -msgstr "" - -#: ../api-quick-start.rst:50 -msgid "Description" -msgstr "" - -#: ../api-quick-start.rst:50 -msgid "Parameter" -msgstr "" - -#: ../api-quick-start.rst:50 -msgid "Type" -msgstr "" - -#: ../api-quick-start.rst:52 -msgid "" -"The user name. If you do not provide a user name and password, you must " -"provide a token." -msgstr "" - -#: ../api-quick-start.rst:52 -msgid "username (required)" -msgstr "" - -#: ../api-quick-start.rst:52 ../api-quick-start.rst:56 -#: ../api-quick-start.rst:58 ../api-quick-start.rst:65 -#: ../api-quick-start.rst:75 -msgid "xsd:string" -msgstr "" - -#: ../api-quick-start.rst:56 -msgid "The password for the user." -msgstr "" - -#: ../api-quick-start.rst:56 -msgid "password (required)" -msgstr "" - -#: ../api-quick-start.rst:58 -msgid "*tenantName* (Optional)" -msgstr "" - -#: ../api-quick-start.rst:58 -msgid "" -"The tenant name. Both the *tenantId* and *tenantName* are optional and " -"mutually exclusive. If you specify both attributes, the server returns the " -"Bad Request (400) response code." -msgstr "" - -#: ../api-quick-start.rst:65 msgid "*tenantId* (Optional)" -msgstr "" +msgstr "*tenantId* (可选)" + +msgid "*tenantName* (Optional)" +msgstr "*tenantName* (可选)" -#: ../api-quick-start.rst:65 msgid "" -"The tenant ID. Both the *tenantId* and *tenantName* are optional and " -"mutually exclusive. If you specify both attributes, the server returns the " -"Bad Request (400) response code. If you do not know the tenant name ID, send " -"a request with \"\" for the tenant name or ID. The response returns the " -"tenant name or ID." +"A command-line tool that lets you send HTTP requests and receive responses. " +"See the section called :ref:`openstack_API_quick_guide`." msgstr "" +"命令行工具可以让你发送HTTP请求和接收响应。请参考“openstack_API_quick_guide”。" -#: ../api-quick-start.rst:75 msgid "" "A token. If you do not provide a token, you must provide a user name and " "password." -msgstr "" +msgstr "令牌。假如您不提供令牌，则必须提供用户名和密码。" -#: ../api-quick-start.rst:75 -msgid "token (Optional)" -msgstr "" - -#: ../api-quick-start.rst:81 msgid "" -"In a typical OpenStack deployment that runs Identity, you can specify your " -"tenant name, and user name and password credentials to authenticate." +"After you authenticate through Identity, you can use the other OpenStack " +"APIs to create and manage resources in your OpenStack cloud. You can launch " +"instances from images and assign metadata to instances through the Compute " +"API or the **openstack** command-line client." msgstr "" +"当你通过认证服务认证后，你可以使用其他的OpenStack APIs 来创建和管理你" +"OpenStack云环境下的资源。你可以通过计算服务API或者“OpenStack”命令行客户端用镜" +"像创建实例和为实例配置参数" -#: ../api-quick-start.rst:84 -msgid "" -"First, export your tenant name to the `OS_TENANT_NAME` environment variable, " -"your user name to the `OS_USERNAME` environment variable, and your password " -"to the `OS_PASSWORD` environment variable. The example below uses a TryStack " -"endpoint but you can also use `$OS_IDENTITYENDPOINT` as an environment " -"variable as needed." -msgstr "" - -#: ../api-quick-start.rst:89 -msgid "Then, run this cURL command to request a token:" -msgstr "" - -#: ../api-quick-start.rst:98 -msgid "" -"If the request succeeds, it returns the ``OK (200)`` response code followed " -"by a response body that contains a token in the form ``\"id\":\"token\"`` " -"and an expiration date and time in the form ``\"expires\":\"datetime\"``." -msgstr "" - -#: ../api-quick-start.rst:104 -msgid "" -"If you do not know the tenant name or ID, send a request with \"\" for the " -"tenant name or ID. The response returns the tenant name or ID." -msgstr "" - -#: ../api-quick-start.rst:114 -msgid "The following example shows a successful response:" -msgstr "" - -#: ../api-quick-start.rst:339 -msgid "Send API requests" -msgstr "" - -#: ../api-quick-start.rst:341 -msgid "" -"This section shows how to make some basic Compute API calls. For a complete " -"list of Compute API calls, see `Compute API (CURRENT) `__." -msgstr "" - -#: ../api-quick-start.rst:345 -msgid "" -"Export the token ID to the ``OS_TOKEN`` environment variable. For example:" -msgstr "" - -#: ../api-quick-start.rst:351 -msgid "The token expires every 24 hours." -msgstr "" - -#: ../api-quick-start.rst:353 -msgid "" -"Export the tenant name to the ``OS_TENANT_NAME`` environment variable. For " -"example:" -msgstr "" - -#: ../api-quick-start.rst:359 -msgid "Then, use the Compute API to list flavors:" -msgstr "" - -#: ../api-quick-start.rst:444 -msgid "Use the Compute API to list images:" -msgstr "" - -#: ../api-quick-start.rst:554 -msgid "Use the Compute API to list servers:" -msgstr "" - -#: ../api-quick-start.rst:586 -msgid "OpenStack command-line clients" -msgstr "" - -#: ../api-quick-start.rst:588 -msgid "" -"For scripting work and simple requests, you can use a command-line client " -"like the ``openstack-client`` client. This client enables you to use the " -"Identity, Compute, Block Storage, and Object Storage APIs through a command-" -"line interface. Also, each OpenStack project has a related client project " -"that includes Python API bindings and a command-line interface (CLI)." -msgstr "" - -#: ../api-quick-start.rst:594 -msgid "" -"For information about the command-line clients, see `OpenStack Command-Line " -"Interface Reference `__." -msgstr "" - -#: ../api-quick-start.rst:598 -msgid "Install the clients" -msgstr "" - -#: ../api-quick-start.rst:600 -msgid "" -"Use ``pip`` to install the OpenStack clients on a Mac OS X or Linux system. " -"It is easy and ensures that you get the latest version of the client from " -"the `Python Package Index `__. Also, ``pip`` " -"lets you update or remove a package." -msgstr "" - -#: ../api-quick-start.rst:605 -msgid "" -"You must install the client for each project separately, but the ``python-" -"openstackclient`` covers multiple projects." -msgstr "" - -#: ../api-quick-start.rst:608 -msgid "Install or update a client package:" -msgstr "" - -#: ../api-quick-start.rst:614 -msgid "Where *PROJECT* is the project name." -msgstr "" - -#: ../api-quick-start.rst:616 -msgid "For example, install the ``openstack`` client:" -msgstr "" - -#: ../api-quick-start.rst:622 -msgid "To update the ``openstack`` client, run this command:" -msgstr "" - -#: ../api-quick-start.rst:628 -msgid "To remove the ``openstack`` client, run this command:" -msgstr "" - -#: ../api-quick-start.rst:634 -msgid "" -"Before you can issue client commands, you must download and source the " -"``openrc`` file to set environment variables." -msgstr "" - -#: ../api-quick-start.rst:637 -msgid "" -"For complete information about the OpenStack clients, including how to " -"source the ``openrc`` file, see `OpenStack End User Guide `__, `OpenStack Administrator Guide `__, and `OpenStack Command-Line Interface " -"Reference `__." -msgstr "" - -#: ../api-quick-start.rst:643 -msgid "Launch an instance" -msgstr "" - -#: ../api-quick-start.rst:645 -msgid "" -"To launch instances, you must choose a name, an image, and a flavor for your " -"instance." -msgstr "" - -#: ../api-quick-start.rst:648 -msgid "" -"To list available images, call the Compute API through the ``openstack`` " -"client:" -msgstr "" - -#: ../api-quick-start.rst:663 -msgid "To list flavors, run this command:" -msgstr "" - -#: ../api-quick-start.rst:683 -msgid "To launch an instance, note the IDs of your desired image and flavor." -msgstr "" - -#: ../api-quick-start.rst:685 -msgid "" -"To launch the ``my_instance`` instance, run the ``openstack server create`` " -"command with the image and flavor IDs and the server name:" -msgstr "" - -#: ../api-quick-start.rst:727 -msgid "" -"For information about the default ports that the OpenStack components use, " -"see `Firewalls and default ports `_ in the *OpenStack " -"Configuration Reference*." -msgstr "" - -#: ../index.rst:3 -msgid "OpenStack API Guide" -msgstr "" - -#: ../index.rst:5 msgid "" "Although you install each OpenStack service separately, the OpenStack " "services work together to meet your cloud needs: Identity, Compute, Images, " @@ -350,67 +63,273 @@ msgid "" "installation, these services work together in the background of the " "installation." msgstr "" +"尽管你单独地安装了每个OpenStack服务，OpenStack的计算，镜像，块存储，网络，对" +"象存储，数据库和监控服务可以一起运行来满足你的云需求。安装以后，上述服务可以" +"共同运行。" + +msgid "Authenticate" +msgstr "认证" + +msgid "Authentication and API request workflow" +msgstr "认证与 API 请求工作流" -#: ../index.rst:12 msgid "" -"After you authenticate through Identity, you can use the other OpenStack " -"APIs to create and manage resources in your OpenStack cloud. You can launch " -"instances from images and assign metadata to instances through the Compute " -"API or the **openstack** command-line client." -msgstr "" +"Before you can issue client commands, you must download and source the " +"``openrc`` file to set environment variables." +msgstr "在执行客户端命令之前，你必须下载并source“openrc”文件来设置环境变量。" -#: ../index.rst:17 -msgid "To begin sending API requests, use one of the following methods:" -msgstr "" - -#: ../index.rst:19 -msgid "**cURL**" -msgstr "" - -#: ../index.rst:21 -msgid "" -"A command-line tool that lets you send HTTP requests and receive responses. " -"See the section called :ref:`openstack_API_quick_guide`." -msgstr "" - -#: ../index.rst:24 -msgid "**OpenStack command-line client**" -msgstr "" - -#: ../index.rst:26 -msgid "" -"The OpenStack project provides a command-line client that enables you to " -"access APIs through easy-to-use commands. See the section called :ref:" -"`client-intro`." -msgstr "" - -#: ../index.rst:30 -msgid "**REST clients**" -msgstr "" - -#: ../index.rst:32 msgid "" "Both Mozilla and Google provide browser-based graphical interfaces for REST. " "For Firefox, see `RESTClient `__. For Chrome, see `rest-client `__." msgstr "" +"Mozilla和Google都为REST提供了基于浏览器的图形接口。对于Firefox浏览器，请参" +"看“RESTClient ”，" +"对于Chrome浏览器，请参看“rest-client ”。" -#: ../index.rst:38 -msgid "**OpenStack Python Software Development Kit (SDK)**" -msgstr "" +msgid "Description" +msgstr "描述" -#: ../index.rst:40 msgid "" -"Use this SDK to write Python automation scripts that create and manage " -"resources in your OpenStack cloud. The SDK implements Python bindings to the " -"OpenStack API, which enables you to perform automation tasks in Python by " -"making calls on Python objects rather than making REST calls directly. All " -"OpenStack command-line tools are implemented by using the Python SDK. See " -"`OpenStack Python SDK `__ in " -"the *OpenStack End User Guide*." -msgstr "" +"Export the tenant name to the ``OS_TENANT_NAME`` environment variable. For " +"example:" +msgstr "将租户的名字传递给环境变量“OS_TENANT_NAME”，例如：" -#: ../index.rst:50 -msgid "Learn more" +msgid "" +"Export the token ID to the ``OS_TOKEN`` environment variable. For example:" +msgstr "将token ID传递给环境变量“OS_TOKEN”，例如：" + +msgid "" +"First, export your tenant name to the `OS_TENANT_NAME` environment variable, " +"your user name to the `OS_USERNAME` environment variable, and your password " +"to the `OS_PASSWORD` environment variable. The example below uses a TryStack " +"endpoint but you can also use `$OS_IDENTITYENDPOINT` as an environment " +"variable as needed." msgstr "" +"首先，将你的租户名传递给环境变量“OS_TENANT_NAME”，你的用户名传递给环境变" +"量“OS_USERNAME”，你的密码传递给环境变量“OS_PASSWORD”。下面的例子使用TryStack" +"作为环境变量，如果需要的话，你也可以使用“OS_IDENTITYENDPOINT”作为换进变量。" + +msgid "" +"For complete information about the OpenStack clients, including how to " +"source the ``openrc`` file, see `OpenStack End User Guide `__, `OpenStack Administrator Guide `__, and `OpenStack Command-Line Interface " +"Reference `__." +msgstr "" +"获取更多关于OpenStack客户端的信息，包括如何source “openrc”文件，请" +"看“OpenStack End User Guide ”和“OpenStack Command-Line Interface Reference ”。" + +msgid "For example, install the ``openstack`` client:" +msgstr "例如，安装“openstack”客户端：" + +msgid "" +"For information about the command-line clients, see `OpenStack Command-Line " +"Interface Reference `__." +msgstr "" +"获取更多关于命令行客户端的信息，请看OpenStack命令行接口参考文献： " + +msgid "" +"For information about the default ports that the OpenStack components use, " +"see `Firewalls and default ports `_ in the *OpenStack " +"Configuration Reference*." +msgstr "" +"获取更多关于OpenStack组建使用的默认端口，查看OpenStack配置文档中的“Firewalls " +"and default ports ”。" + +msgid "" +"For scripting work and simple requests, you can use a command-line client " +"like the ``openstack-client`` client. This client enables you to use the " +"Identity, Compute, Block Storage, and Object Storage APIs through a command-" +"line interface. Also, each OpenStack project has a related client project " +"that includes Python API bindings and a command-line interface (CLI)." +msgstr "" +"对于脚本操作和简单的请求，你可以使用像“openstack-client”这样的客户端命令行，" +"这个客户端能让你通过命令行借口去使用认证，计算，块存储，对象存储API。同时每个" +"openstack项目都会提供包含Python API和命令行接口的客户端。" + +msgid "If the Unauthorized (401) error occurs, request another token." +msgstr "如果Unauthorized (401)错误出现, 请再申请一个令牌。" + +msgid "" +"If the request succeeds, it returns the ``OK (200)`` response code followed " +"by a response body that contains a token in the form ``\"id\":\"token\"`` " +"and an expiration date and time in the form ``\"expires\":\"datetime\"``." +msgstr "" +"当请求成功时，将会返回响应码“OK(200)”，响应码跟随着响应体，响应体包含着一个" +"以'' “id”: \"token\" ''这种形式的token，还有一个以'' \"expires\" :\"datetime" +"\" '' 形式的有效时间。" + +msgid "" +"If you do not know the tenant name or ID, send a request with \"\" for the " +"tenant name or ID. The response returns the tenant name or ID." +msgstr "" +"如果你不知道租户的名字或者ID，你可以发送“”获取租户名字或ID，响应将返回租户的" +"名字或ID。" + +msgid "" +"In a typical OpenStack deployment that runs Identity, you can specify your " +"tenant name, and user name and password credentials to authenticate." +msgstr "" +"在一个运行着认证服务的典型OpenStack环境中，你可以指定你的租户凭借用户名和密码" +"进行身份验证。" + +msgid "Install or update a client package:" +msgstr "安装或者更新一个客户端：" + +msgid "Install the clients" +msgstr "安装客户端" + +msgid "Launch an instance" +msgstr "启动一个实例" + +msgid "Learn more" +msgstr "获取更多" + +msgid "OpenStack API Guide" +msgstr "OpenStack API 指南" + +msgid "OpenStack APIs" +msgstr "OpenStack API" + +msgid "OpenStack command-line clients" +msgstr "OpenStack 命令行客户端" + +msgid "Parameter" +msgstr "参数" + +msgid "Send API requests" +msgstr "发送 API 请求" + +msgid "" +"The OpenStack project provides a command-line client that enables you to " +"access APIs through easy-to-use commands. See the section called :ref:" +"`client-intro`." +msgstr "" +"OpenStack工程提供了一个能够让你通过简单命令去访问APIs的命令行客户端，请参" +"考“client-intro”。" + +msgid "" +"The examples in this section use cURL commands. For information about cURL, " +"see http://curl.haxx.se/. For information about the OpenStack APIs, see " +"`OpenStack API Reference `__." +msgstr "" +"该部分的实例使用了cURL命令。关于cURL的信息，请参考http://curl.haxx.se/。关于" +"OpenStack API的信息，请参考`OpenStack API Reference `__。" + +msgid "The following example shows a successful response:" +msgstr "下面的例子展示了一个成功的响应：" + +msgid "The password for the user." +msgstr "该用户的密码。" + +msgid "" +"The tenant name. Both the *tenantId* and *tenantName* are optional and " +"mutually exclusive. If you specify both attributes, the server returns the " +"Bad Request (400) response code." +msgstr "" +"租户名称。*tenantId*和*tenantName*都是可选的，但不能被同时使用。如果这两个属" +"性值都被指定了，服务将会返回Bad Request (400) 码。" + +msgid "The token expires every 24 hours." +msgstr "每个token的有效时间是24小时。" + +msgid "" +"The user name. If you do not provide a user name and password, you must " +"provide a token." +msgstr "用户名。如果您不提供用户名和密码，那么必须提供令牌。" + +msgid "Then, run this cURL command to request a token:" +msgstr "然后，运行cURL命令去请求一个token。" + +msgid "Then, use the Compute API to list flavors:" +msgstr "然后，使用计算服务API列出虚拟机：" + +#, fuzzy +msgid "" +"To authenticate access to OpenStack services, you must first issue an " +"authentication request with a payload of credentials to OpenStack Identity " +"to get an authentication token." +msgstr "" +"为了认证对 OpenStack 服务的访问，你首先需要向 OpenStack 认证服务发出携带证书" +"信息的认证请求以获得认证令牌。" + +msgid "To begin sending API requests, use one of the following methods:" +msgstr "使用如下的方法之一以发送 API 请求：" + +msgid "To launch an instance, note the IDs of your desired image and flavor." +msgstr "启动虚拟机实例前，记录下您所需的镜像和云主机类型的 ID。" + +msgid "" +"To launch instances, you must choose a name, an image, and a flavor for your " +"instance." +msgstr "启动虚拟机实例前，需要为其选择名称，镜像和云主机类型。" + +msgid "" +"To launch the ``my_instance`` instance, run the ``openstack server create`` " +"command with the image and flavor IDs and the server name:" +msgstr "创建一个实例，记录下你使用的镜像和云主机类型的ID。" + +msgid "" +"To list available images, call the Compute API through the ``openstack`` " +"client:" +msgstr "通过“openstack”客户端列出可用的镜像，调用计算服务API。" + +msgid "To list flavors, run this command:" +msgstr "运行如下命令以列出云主机类型：" + +msgid "To remove the ``openstack`` client, run this command:" +msgstr "运行如下命令移除“openstack”客户端。" + +msgid "To update the ``openstack`` client, run this command:" +msgstr "运行如下命令更新“openstack”客户端。" + +msgid "Type" +msgstr "类型" + +msgid "" +"Use ``pip`` to install the OpenStack clients on a Mac OS X or Linux system. " +"It is easy and ensures that you get the latest version of the client from " +"the `Python Package Index `__. Also, ``pip`` " +"lets you update or remove a package." +msgstr "" +"使用“pip”在Mac OS X系统或者Linux系统上安装OpenStack客户端，确保从“Python " +"Package Index”获取最新版本的客户端。你可以使" +"用“pip”去更新或者移除一个包。" + +msgid "Use the Compute API to list images:" +msgstr "使用计算服务API列出镜像：" + +msgid "Use the Compute API to list servers:" +msgstr "使用计算服务API列出服务器：" + +msgid "Where *PROJECT* is the project name." +msgstr "“PROJECT”是一个工程名。" + +msgid "" +"You must install the client for each project separately, but the ``python-" +"openstackclient`` covers multiple projects." +msgstr "" +"你必须为每个工程单独安装客户端，但是“python-openstackclient”可以覆盖多个工" +"程。" + +msgid "password (required)" +msgstr "password (必需)" + +msgid "token (Optional)" +msgstr "token (可选)" + +msgid "username (required)" +msgstr "username (必需)" + +msgid "xsd:string" +msgstr "xsd:string" diff --git a/api-ref-guides/locale/api-ref-guides.pot b/api-ref-guides/locale/api-ref-guides.pot deleted file mode 100644 index b27c33091..000000000 --- a/api-ref-guides/locale/api-ref-guides.pot +++ /dev/null @@ -1,176 +0,0 @@ -msgid "" -msgstr "" -"Project-Id-Version: PACKAGE VERSION\n" -"POT-Creation-Date: 2016-01-19 06:04+0000\n" -"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" -"Last-Translator: FULL NAME \n" -"Language-Team: LANGUAGE \n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" - -#: ./api-ref-guides/src/bk-api-ref-networking-v2.xml:11(title) -msgid "OpenStack Networking (neutron) API v2.0 and Extensions Reference" -msgstr "" - -#: ./api-ref-guides/src/bk-api-ref-networking-v2.xml:15(titleabbrev) ./api-ref-guides/src/bk-api-ref-compute-v2.1.xml:12(titleabbrev) ./api-ref-guides/src/bk-api-ref-identity-v3.xml:11(titleabbrev) ./api-ref-guides/src/bk-api-ref-blockstorage-v1.xml:12(titleabbrev) ./api-ref-guides/src/bk-api-ref-share-v2.xml:12(titleabbrev) ./api-ref-guides/src/bk-api-ref-database-v1.xml:12(titleabbrev) ./api-ref-guides/src/bk-api-ref-identity-v2.xml:11(titleabbrev) ./api-ref-guides/src/bk-api-ref-telemetry-v2.xml:12(titleabbrev) ./api-ref-guides/src/bk-api-ref-data-processing-v1.1.xml:12(titleabbrev) ./api-ref-guides/src/bk-api-ref-orchestration-v1.xml:12(titleabbrev) ./api-ref-guides/src/bk-api-ref-clustering-v1.xml:12(titleabbrev) ./api-ref-guides/src/bk-api-ref-image-v1.xml:12(titleabbrev) ./api-ref-guides/src/bk-api-ref-image-v2.xml:12(titleabbrev) ./api-ref-guides/src/bk-api-ref-objectstorage-v1.xml:12(titleabbrev) ./api-ref-guides/src/bk-api-ref-blockstorage-v2.xml:12(titleabbrev) ./api-ref-guides/src/bk-api-ref-share-v1.xml:12(titleabbrev) -msgid "API Reference" -msgstr "" - -#: ./api-ref-guides/src/bk-api-ref-networking-v2.xml:22(orgname) ./api-ref-guides/src/bk-api-ref-networking-v2.xml:27(holder) ./api-ref-guides/src/bk-api-ref-compute-v2.1.xml:19(orgname) ./api-ref-guides/src/bk-api-ref-compute-v2.1.xml:24(holder) ./api-ref-guides/src/bk-api-ref-identity-v3.xml:18(orgname) ./api-ref-guides/src/bk-api-ref-identity-v3.xml:23(holder) ./api-ref-guides/src/bk-api-ref-blockstorage-v1.xml:19(orgname) ./api-ref-guides/src/bk-api-ref-blockstorage-v1.xml:24(holder) ./api-ref-guides/src/bk-api-ref-share-v2.xml:19(orgname) ./api-ref-guides/src/bk-api-ref-share-v2.xml:24(holder) ./api-ref-guides/src/bk-api-ref-database-v1.xml:19(orgname) ./api-ref-guides/src/bk-api-ref-database-v1.xml:24(holder) ./api-ref-guides/src/bk-api-ref-identity-v2.xml:18(orgname) ./api-ref-guides/src/bk-api-ref-identity-v2.xml:23(holder) ./api-ref-guides/src/bk-api-ref-telemetry-v2.xml:19(orgname) ./api-ref-guides/src/bk-api-ref-telemetry-v2.xml:24(holder) ./api-ref-guides/src/bk-api-ref-data-processing-v1.1.xml:19(orgname) ./api-ref-guides/src/bk-api-ref-data-processing-v1.1.xml:24(holder) ./api-ref-guides/src/bk-api-ref-orchestration-v1.xml:19(orgname) ./api-ref-guides/src/bk-api-ref-orchestration-v1.xml:24(holder) ./api-ref-guides/src/bk-api-ref.xml:19(orgname) ./api-ref-guides/src/bk-api-ref.xml:24(holder) ./api-ref-guides/src/bk-api-ref-clustering-v1.xml:19(orgname) ./api-ref-guides/src/bk-api-ref-clustering-v1.xml:24(holder) ./api-ref-guides/src/bk-api-ref-image-v1.xml:19(orgname) ./api-ref-guides/src/bk-api-ref-image-v1.xml:24(holder) ./api-ref-guides/src/bk-api-ref-image-v2.xml:19(orgname) ./api-ref-guides/src/bk-api-ref-image-v2.xml:24(holder) ./api-ref-guides/src/bk-api-ref-objectstorage-v1.xml:19(orgname) ./api-ref-guides/src/bk-api-ref-objectstorage-v1.xml:24(holder) ./api-ref-guides/src/bk-api-ref-blockstorage-v2.xml:19(orgname) ./api-ref-guides/src/bk-api-ref-blockstorage-v2.xml:24(holder) ./api-ref-guides/src/bk-api-ref-share-v1.xml:19(orgname) ./api-ref-guides/src/bk-api-ref-share-v1.xml:24(holder) -msgid "OpenStack Foundation" -msgstr "" - -#: ./api-ref-guides/src/bk-api-ref-networking-v2.xml:26(year) ./api-ref-guides/src/bk-api-ref-compute-v2.1.xml:23(year) ./api-ref-guides/src/bk-api-ref-identity-v3.xml:22(year) ./api-ref-guides/src/bk-api-ref-blockstorage-v1.xml:23(year) ./api-ref-guides/src/bk-api-ref-database-v1.xml:23(year) ./api-ref-guides/src/bk-api-ref-identity-v2.xml:22(year) ./api-ref-guides/src/bk-api-ref-telemetry-v2.xml:23(year) ./api-ref-guides/src/bk-api-ref-data-processing-v1.1.xml:23(year) ./api-ref-guides/src/bk-api-ref-orchestration-v1.xml:23(year) ./api-ref-guides/src/bk-api-ref.xml:23(year) ./api-ref-guides/src/bk-api-ref-clustering-v1.xml:23(year) ./api-ref-guides/src/bk-api-ref-image-v1.xml:23(year) ./api-ref-guides/src/bk-api-ref-image-v2.xml:23(year) ./api-ref-guides/src/bk-api-ref-objectstorage-v1.xml:23(year) ./api-ref-guides/src/bk-api-ref-blockstorage-v2.xml:23(year) -msgid "2010-2016" -msgstr "" - -#: ./api-ref-guides/src/bk-api-ref-networking-v2.xml:29(productname) -msgid "OpenStack Networking (neutron)" -msgstr "" - -#: ./api-ref-guides/src/bk-api-ref-networking-v2.xml:33(remark) ./api-ref-guides/src/bk-api-ref-compute-v2.1.xml:30(remark) ./api-ref-guides/src/bk-api-ref-identity-v3.xml:29(remark) ./api-ref-guides/src/bk-api-ref-blockstorage-v1.xml:30(remark) ./api-ref-guides/src/bk-api-ref-share-v2.xml:30(remark) ./api-ref-guides/src/bk-api-ref-database-v1.xml:30(remark) ./api-ref-guides/src/bk-api-ref-identity-v2.xml:29(remark) ./api-ref-guides/src/bk-api-ref-telemetry-v2.xml:30(remark) ./api-ref-guides/src/bk-api-ref-data-processing-v1.1.xml:30(remark) ./api-ref-guides/src/bk-api-ref-orchestration-v1.xml:30(remark) ./api-ref-guides/src/bk-api-ref.xml:30(remark) ./api-ref-guides/src/bk-api-ref-clustering-v1.xml:30(remark) ./api-ref-guides/src/bk-api-ref-image-v1.xml:30(remark) ./api-ref-guides/src/bk-api-ref-image-v2.xml:30(remark) ./api-ref-guides/src/bk-api-ref-objectstorage-v1.xml:30(remark) ./api-ref-guides/src/bk-api-ref-blockstorage-v2.xml:30(remark) ./api-ref-guides/src/bk-api-ref-share-v1.xml:30(remark) -msgid "Copyright details are filled in by the template." -msgstr "" - -#: ./api-ref-guides/src/bk-api-ref-compute-v2.1.xml:11(title) -msgid "OpenStack Compute API Reference" -msgstr "" - -#: ./api-ref-guides/src/bk-api-ref-compute-v2.1.xml:26(productname) -msgid "OpenStack Compute" -msgstr "" - -#: ./api-ref-guides/src/bk-api-ref-identity-v3.xml:10(title) -msgid "OpenStack Identity API v3 Reference" -msgstr "" - -#: ./api-ref-guides/src/bk-api-ref-identity-v3.xml:25(productname) ./api-ref-guides/src/bk-api-ref-identity-v2.xml:25(productname) -msgid "OpenStack Identity" -msgstr "" - -#: ./api-ref-guides/src/bk-api-ref-blockstorage-v1.xml:11(title) -msgid "OpenStack Block Storage API v1 Reference" -msgstr "" - -#: ./api-ref-guides/src/bk-api-ref-blockstorage-v1.xml:26(productname) ./api-ref-guides/src/bk-api-ref-blockstorage-v2.xml:26(productname) -msgid "OpenStack Block Storage" -msgstr "" - -#: ./api-ref-guides/src/bk-api-ref-share-v2.xml:11(title) -msgid "OpenStack Shared File Systems API v2 Reference" -msgstr "" - -#: ./api-ref-guides/src/bk-api-ref-share-v2.xml:23(year) -msgid "2015-2016" -msgstr "" - -#: ./api-ref-guides/src/bk-api-ref-share-v2.xml:26(productname) ./api-ref-guides/src/bk-api-ref-share-v1.xml:26(productname) -msgid "OpenStack Shared File Systems" -msgstr "" - -#: ./api-ref-guides/src/bk-api-ref-database-v1.xml:11(title) -msgid "OpenStack Database Service API v1.0 Reference" -msgstr "" - -#: ./api-ref-guides/src/bk-api-ref-database-v1.xml:26(productname) -msgid "OpenStack Database Service" -msgstr "" - -#: ./api-ref-guides/src/bk-api-ref-identity-v2.xml:10(title) -msgid "OpenStack Identity API v2.0 Reference" -msgstr "" - -#: ./api-ref-guides/src/bk-api-ref-telemetry-v2.xml:11(title) -msgid "OpenStack Telemetry API v2 Reference" -msgstr "" - -#: ./api-ref-guides/src/bk-api-ref-telemetry-v2.xml:26(productname) -msgid "OpenStack Telemetry" -msgstr "" - -#: ./api-ref-guides/src/bk-api-ref-data-processing-v1.1.xml:11(title) -msgid "OpenStack Data Processing API v1.1 Reference" -msgstr "" - -#: ./api-ref-guides/src/bk-api-ref-data-processing-v1.1.xml:26(productname) -msgid "OpenStack Data Processing" -msgstr "" - -#: ./api-ref-guides/src/preface.xml:13(title) -msgid "Preface" -msgstr "" - -#: ./api-ref-guides/src/preface.xml:14(para) -msgid "Use the OpenStack APIs and extensions in your OpenStack cloud." -msgstr "" - -#: ./api-ref-guides/src/preface.xml:18(para) -msgid "You must install the packages for each API separately. After you authenticate through the Identity API, you can use the other APIs and extensions to launch server instances, create images, assign metadata to instances and images, create containers and objects, and complete other actions in your OpenStack cloud. To get started with the APIs, see the OpenStack API Guide." -msgstr "" - -#: ./api-ref-guides/src/bk-api-ref-orchestration-v1.xml:11(title) -msgid "OpenStack Orchestration API v1 Reference" -msgstr "" - -#: ./api-ref-guides/src/bk-api-ref-orchestration-v1.xml:26(productname) -msgid "OpenStack Orchestration" -msgstr "" - -#: ./api-ref-guides/src/bk-api-ref.xml:11(title) -msgid "OpenStack API Complete Reference" -msgstr "" - -#: ./api-ref-guides/src/bk-api-ref.xml:12(titleabbrev) -msgid "API Complete Reference" -msgstr "" - -#: ./api-ref-guides/src/bk-api-ref.xml:26(productname) -msgid "OpenStack" -msgstr "" - -#: ./api-ref-guides/src/bk-api-ref-clustering-v1.xml:11(title) -msgid "OpenStack Clustering Service API v1 Reference" -msgstr "" - -#: ./api-ref-guides/src/bk-api-ref-clustering-v1.xml:26(productname) -msgid "OpenStack Clustering Service" -msgstr "" - -#: ./api-ref-guides/src/bk-api-ref-image-v1.xml:11(title) -msgid "OpenStack Image Service API v1 Reference" -msgstr "" - -#: ./api-ref-guides/src/bk-api-ref-image-v1.xml:26(productname) ./api-ref-guides/src/bk-api-ref-image-v2.xml:26(productname) -msgid "OpenStack Image Service" -msgstr "" - -#: ./api-ref-guides/src/bk-api-ref-image-v2.xml:11(title) -msgid "OpenStack Image Service API v2 Reference" -msgstr "" - -#: ./api-ref-guides/src/bk-api-ref-objectstorage-v1.xml:11(title) -msgid "OpenStack Object Storage API v1 Reference" -msgstr "" - -#: ./api-ref-guides/src/bk-api-ref-objectstorage-v1.xml:26(productname) -msgid "OpenStack Object Storage" -msgstr "" - -#: ./api-ref-guides/src/bk-api-ref-blockstorage-v2.xml:11(title) -msgid "OpenStack Block Storage API v2 Reference" -msgstr "" - -#: ./api-ref-guides/src/bk-api-ref-share-v1.xml:11(title) -msgid "OpenStack Shared File Systems API v1 Reference" -msgstr "" - -#: ./api-ref-guides/src/bk-api-ref-share-v1.xml:23(year) -msgid "2015" -msgstr "" - -#. Put one translator per line, in the form of NAME , YEAR1, YEAR2 -#: ./api-ref-guides/src/bk-api-ref-share-v1.xml:0(None) -msgid "translator-credits" -msgstr "" - diff --git a/api-ref/locale/api-ref.pot b/api-ref/locale/api-ref.pot deleted file mode 100644 index 1c458bdcb..000000000 --- a/api-ref/locale/api-ref.pot +++ /dev/null @@ -1,3840 +0,0 @@ -msgid "" -msgstr "" -"Project-Id-Version: PACKAGE VERSION\n" -"POT-Creation-Date: 2016-04-27 06:07+0000\n" -"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" -"Last-Translator: FULL NAME \n" -"Language-Team: LANGUAGE \n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" - -#: ./api-ref/src/docbkx/api-ref-database-v1.xml:11(title) -msgid "OpenStack Database Service API v1.0 (CURRENT)" -msgstr "" - -#: ./api-ref/src/docbkx/api-ref-database-v1.xml:13(year) ./api-ref/src/docbkx/api-ref-identity-v2.xml:13(year) ./api-ref/src/docbkx/api-ref-telemetry-v2.xml:13(year) ./api-ref/src/docbkx/api-ref-blockstorage-v1.xml:13(year) ./api-ref/src/docbkx/api-ref-identity-v3.xml:13(year) ./api-ref/src/docbkx/api-ref-identity-admin-v2.xml:13(year) ./api-ref/src/docbkx/api-ref-data-processing-v1.1.xml:12(year) ./api-ref/src/docbkx/api-ref-networking-v2-ext.xml:13(year) ./api-ref/src/docbkx/api-ref-orchestration-v1.xml:13(year) ./api-ref/src/docbkx/api-ref.xml:13(year) ./api-ref/src/docbkx/api-ref-objectstorage-v1.xml:13(year) ./api-ref/src/docbkx/api-ref-image-v1.xml:13(year) ./api-ref/src/docbkx/api-ref-compute-v2.1.xml:13(year) ./api-ref/src/docbkx/api-ref-identity-v3-ext.xml:13(year) ./api-ref/src/docbkx/api-ref-image-v2.xml:13(year) ./api-ref/src/docbkx/api-ref-identity-v2-ext.xml:13(year) ./api-ref/src/docbkx/api-ref-networking-v2.xml:13(year) ./api-ref/src/docbkx/api-ref-blockstorage-v2.xml:13(year) -msgid "2010-2016" -msgstr "" - -#: ./api-ref/src/docbkx/api-ref-identity-v2.xml:11(title) -msgid "OpenStack Identity API v2 (DEPRECATED)" -msgstr "" - -#: ./api-ref/src/docbkx/api-ref-share-v2.xml:11(title) -msgid "OpenStack Shared File Systems API v2.0 (CURRENT)" -msgstr "" - -#: ./api-ref/src/docbkx/api-ref-share-v2.xml:13(year) ./api-ref/src/docbkx/api-ref-share-v1.xml:13(year) -msgid "2015" -msgstr "" - -#: ./api-ref/src/docbkx/api-ref-telemetry-v2.xml:11(title) -msgid "OpenStack Telemetry API v2 (CURRENT)" -msgstr "" - -#: ./api-ref/src/docbkx/api-ref-blockstorage-v1.xml:11(title) -msgid "OpenStack Block Storage API v1 (SUPPORTED)" -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-admin-v2.xml:10(title) -msgid "Identity Admin API v2.0 (SUPPORTED)" -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-admin-v2.xml:11(para) -msgid "Gets an authentication token that permits access to the Compute API." -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-admin-v2.xml:13(title) -msgid "Versions" -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-admin-v2.xml:21(title) ./api-ref/src/docbkx/ch_identity-v2.xml:25(title) ./api-ref/src/docbkx/ch_networking-v2-ext.xml:16(title) -msgid "Extensions" -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-admin-v2.xml:22(para) -msgid "For information about Identity API v2.0 extensions, see Extensions." -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-admin-v2.xml:28(title) -msgid "Tokens" -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-admin-v2.xml:44(title) ./api-ref/src/docbkx/ch_identity-v3.xml:103(link) -msgid "Users" -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-admin-v2.xml:61(title) -msgid "Tenants" -msgstr "" - -#: ./api-ref/src/docbkx/api-ref-identity-v3.xml:11(title) -msgid "OpenStack Identity API v3 (CURRENT)" -msgstr "" - -#: ./api-ref/src/docbkx/ch_images-v2.xml:10(title) ./api-ref/src/docbkx/itemizedlist-service-list.xml:70(link) -msgid "Image service API v2 (CURRENT)" -msgstr "" - -#: ./api-ref/src/docbkx/ch_images-v2.xml:11(para) -msgid "Image service API v2.0, API v2.1, API v2.2, and API v2.3." -msgstr "" - -#: ./api-ref/src/docbkx/ch_images-v2.xml:12(para) ./api-ref/src/docbkx/ch_images-v1.xml:15(para) -msgid "Cloud providers can configure property protections that prevent non-administrative users from updating and deleting protected properties. For more information, see Image property protection in the OpenStack Cloud Administrator Guide." -msgstr "" - -#: ./api-ref/src/docbkx/ch_images-v2.xml:21(title) ./api-ref/src/docbkx/ch_networking-v2.xml:26(title) ./api-ref/src/docbkx/ch_database-v1.xml:12(title) ./api-ref/src/docbkx/ch_blockstorage-api-v1.xml:37(title) ./api-ref/src/docbkx/ch_identity-v2.xml:14(title) ./api-ref/src/docbkx/ch_images-v1.xml:22(title) ./api-ref/src/docbkx/ch_share-v2.xml:49(title) ./api-ref/src/docbkx/ch_compute-v2.1.xml:39(title) ./api-ref/src/docbkx/ch_orchestration-v1.xml:23(title) ./api-ref/src/docbkx/ch_clustering-v1.xml:17(title) ./api-ref/src/docbkx/ch_blockstorage-api-v2.xml:16(title) -msgid "API versions" -msgstr "" - -#: ./api-ref/src/docbkx/ch_images-v2.xml:29(title) -msgid "Images (images)" -msgstr "" - -#: ./api-ref/src/docbkx/ch_images-v2.xml:30(para) -msgid "Creates, lists, updates, and deletes images." -msgstr "" - -#: ./api-ref/src/docbkx/ch_images-v2.xml:31(para) -msgid "Image operations show all fields in the response body. Any field with no value is set to null value (JSON null data type)." -msgstr "" - -#: ./api-ref/src/docbkx/ch_images-v2.xml:36(para) -msgid "The possible status values for images are:" -msgstr "" - -#: ./api-ref/src/docbkx/ch_images-v2.xml:40(caption) -msgid "Image status" -msgstr "" - -#: ./api-ref/src/docbkx/ch_images-v2.xml:45(th) ./api-ref/src/docbkx/ch_share-v2.xml:170(th) ./api-ref/src/docbkx/ch_share-v2.xml:733(th) ./api-ref/src/docbkx/ch_networking-v2-ext.xml:123(th) ./api-ref/src/docbkx/ch_networking-v2-ext.xml:182(th) ./api-ref/src/docbkx/ch_blockstorage-api-v2.xml:68(th) ./api-ref/src/docbkx/ch_blockstorage-api-v2.xml:216(th) ./api-ref/src/docbkx/ch_blockstorage-api-v2.xml:428(th) -msgid "Status" -msgstr "" - -#: ./api-ref/src/docbkx/ch_images-v2.xml:46(th) ./api-ref/src/docbkx/ch_objectstorage-v1.xml:128(th) ./api-ref/src/docbkx/ch_identity-v3.xml:201(th) ./api-ref/src/docbkx/ch_share-v2.xml:171(th) ./api-ref/src/docbkx/ch_share-v2.xml:734(th) ./api-ref/src/docbkx/ch_networking-v2-ext.xml:124(th) ./api-ref/src/docbkx/ch_networking-v2-ext.xml:183(th) ./api-ref/src/docbkx/ch_blockstorage-api-v2.xml:69(th) ./api-ref/src/docbkx/ch_blockstorage-api-v2.xml:217(th) ./api-ref/src/docbkx/ch_blockstorage-api-v2.xml:429(th) -msgid "Description" -msgstr "" - -#: ./api-ref/src/docbkx/ch_images-v2.xml:51(para) -msgid "queued" -msgstr "" - -#: ./api-ref/src/docbkx/ch_images-v2.xml:53(para) -msgid "The Image service reserved an image ID for the image in the registry but did not yet upload any image data." -msgstr "" - -#: ./api-ref/src/docbkx/ch_images-v2.xml:61(para) -msgid "saving" -msgstr "" - -#: ./api-ref/src/docbkx/ch_images-v2.xml:63(para) -msgid "The Image service is currently uploading the raw data for the image." -msgstr "" - -#: ./api-ref/src/docbkx/ch_images-v2.xml:70(para) ./api-ref/src/docbkx/ch_share-v2.xml:740(code) -msgid "active" -msgstr "" - -#: ./api-ref/src/docbkx/ch_images-v2.xml:72(para) -msgid "The image is active and fully available in the Image service." -msgstr "" - -#: ./api-ref/src/docbkx/ch_images-v2.xml:79(para) -msgid "killed" -msgstr "" - -#: ./api-ref/src/docbkx/ch_images-v2.xml:81(para) -msgid "An image data upload error occurred." -msgstr "" - -#: ./api-ref/src/docbkx/ch_images-v2.xml:87(para) -msgid "deleted" -msgstr "" - -#: ./api-ref/src/docbkx/ch_images-v2.xml:89(para) -msgid "The Image service retains information about the image but the image is no longer available for use." -msgstr "" - -#: ./api-ref/src/docbkx/ch_images-v2.xml:97(para) -msgid "pending_delete" -msgstr "" - -#: ./api-ref/src/docbkx/ch_images-v2.xml:99(para) -msgid "Similar to the deleted status. An image in this state is not recoverable." -msgstr "" - -#: ./api-ref/src/docbkx/ch_images-v2.xml:127(title) -msgid "Image data (images, file)" -msgstr "" - -#: ./api-ref/src/docbkx/ch_images-v2.xml:128(para) -msgid "Uploads and downloads raw image data." -msgstr "" - -#: ./api-ref/src/docbkx/ch_images-v2.xml:139(title) -msgid "Image tags (images, tags)" -msgstr "" - -#: ./api-ref/src/docbkx/ch_images-v2.xml:140(para) -msgid "Adds and deletes image tags." -msgstr "" - -#: ./api-ref/src/docbkx/ch_images-v2.xml:151(title) -msgid "Members (images, members)" -msgstr "" - -#: ./api-ref/src/docbkx/ch_images-v2.xml:152(para) -msgid "Creates, lists, updates, and deletes image members." -msgstr "" - -#: ./api-ref/src/docbkx/ch_images-v2.xml:168(title) -msgid "Image schemas (schemas, image, images, member, members)" -msgstr "" - -#: ./api-ref/src/docbkx/ch_images-v2.xml:169(para) -msgid "Gets a JSON-schema document that represents an images or image entity." -msgstr "" - -#: ./api-ref/src/docbkx/ch_images-v2.xml:177(title) -msgid "Metadata definition resource types (since API v2.0) (metadefs, namespaces, resource_types)" -msgstr "" - -#: ./api-ref/src/docbkx/ch_images-v2.xml:178(para) -msgid "Lists resource types. Also, creates, lists, and removes resource type associations in a namespace." -msgstr "" - -#: ./api-ref/src/docbkx/ch_images-v2.xml:186(title) -msgid "Metadata definition namespaces (since API v2.0) (metadefs, namespaces)" -msgstr "" - -#: ./api-ref/src/docbkx/ch_images-v2.xml:187(para) -msgid "Creates, lists, shows details for, updates, and deletes metadata definition namespaces. Defines namespaces that can contain property definitions, object definitions, and resource type associations." -msgstr "" - -#: ./api-ref/src/docbkx/ch_images-v2.xml:197(title) -msgid "Metadata definition properties (since API v2.0) (metadefs, namespaces, properties)" -msgstr "" - -#: ./api-ref/src/docbkx/ch_images-v2.xml:198(para) -msgid "Creates, lists, shows details for, updates, and deletes metadata definition properties." -msgstr "" - -#: ./api-ref/src/docbkx/ch_images-v2.xml:206(title) -msgid "Metadata definition objects (since API v2.0) (metadefs, namespaces, objects)" -msgstr "" - -#: ./api-ref/src/docbkx/ch_images-v2.xml:207(para) -msgid "Creates, lists, shows details for, updates, and deletes metadata definition objects." -msgstr "" - -#: ./api-ref/src/docbkx/ch_images-v2.xml:215(title) -msgid "Metadata definition tags (since API v2.0) (metadefs, namespaces, tags)" -msgstr "" - -#: ./api-ref/src/docbkx/ch_images-v2.xml:216(para) -msgid "Creates, lists, shows details for, updates, and deletes metadata definition tags." -msgstr "" - -#: ./api-ref/src/docbkx/ch_images-v2.xml:224(title) -msgid "Metadata definition schemas (schemas, metadefs, namespace, namespaces, object, objects, property, properties, tag, tags, resource_type, resource_types)" -msgstr "" - -#: ./api-ref/src/docbkx/ch_images-v2.xml:225(para) -msgid "Gets a JSON-schema document that represents a metadata definition entity." -msgstr "" - -#: ./api-ref/src/docbkx/ch_images-v2.xml:233(title) -msgid "Tasks (since API v2.2) (tasks)" -msgstr "" - -#: ./api-ref/src/docbkx/ch_images-v2.xml:234(para) -msgid "Creates, lists, and shows details for tasks." -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-v2-ext.xml:14(title) ./api-ref/src/docbkx/itemizedlist-service-list.xml:65(link) -msgid "Identity API v2.0 extensions (SUPPORTED)" -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-v2-ext.xml:15(para) -msgid "To list available Identity API v2.0 extensions, issue a request to v2.0/extensions." -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-v2-ext.xml:20(title) -msgid "OS-KSADM admin extension" -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-v2-ext.xml:21(para) -msgid "Supports create, read, update, and delete (CRUD) operations for users, tenants, roles, and services. Requires administrator privileges." -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-v2-ext.xml:30(title) -msgid "OS-KSCATALOG admin extension" -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-v2-ext.xml:31(para) -msgid "Supports CRUD operations for endpoint templates and endpoints. Requires administrator privileges." -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-v2-ext.xml:40(title) -msgid "OS-KSEC2 admin extension" -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-v2-ext.xml:41(para) -msgid "Supports Amazon Elastic Compute (EC2) style authentication." -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-v2-ext.xml:49(title) -msgid "OS-KSS3 admin extension" -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-v2-ext.xml:55(title) -msgid "OS-KSVALIDATE admin extension" -msgstr "" - -#: ./api-ref/src/docbkx/ch_networking-v2.xml:10(title) ./api-ref/src/docbkx/itemizedlist-service-list.xml:80(link) -msgid "Networking API v2.0 (CURRENT)" -msgstr "" - -#: ./api-ref/src/docbkx/ch_networking-v2.xml:11(para) -msgid "Use virtual networking services among devices that the OpenStack Compute service manages. The Networking (neutron) API v2.0 combines the API v1.1 functionality with some essential Internet Protocol Address Management (IPAM) functionality. The API enables users to associate IP address blocks and other network configuration settings with an OpenStack Networking network. You can choose an IP address from the block or let OpenStack Networking choose the first available IP address." -msgstr "" - -#: ./api-ref/src/docbkx/ch_networking-v2.xml:21(para) -msgid "Effective in the OpenStack Liberty release, the Networking API v2.0 does not support XML requests and responses." -msgstr "" - -#: ./api-ref/src/docbkx/ch_networking-v2.xml:27(para) -msgid "Lists information for all Networking API versions." -msgstr "" - -#: ./api-ref/src/docbkx/ch_networking-v2.xml:36(title) -msgid "Networks" -msgstr "" - -#: ./api-ref/src/docbkx/ch_networking-v2.xml:37(para) -msgid "Lists, shows details for, creates, updates, and deletes networks." -msgstr "" - -#: ./api-ref/src/docbkx/ch_networking-v2.xml:56(title) -msgid "Subnets" -msgstr "" - -#: ./api-ref/src/docbkx/ch_networking-v2.xml:57(para) -msgid "Lists, shows details for, creates, updates, and deletes subnet resources." -msgstr "" - -#: ./api-ref/src/docbkx/ch_networking-v2.xml:65(title) -msgid "Ports" -msgstr "" - -#: ./api-ref/src/docbkx/ch_networking-v2.xml:66(para) -msgid "Lists, shows details for, creates, updates, and deletes ports." -msgstr "" - -#: ./api-ref/src/docbkx/ch_networking-v2.xml:73(title) -msgid "Service providers" -msgstr "" - -#: ./api-ref/src/docbkx/ch_networking-v2.xml:74(para) -msgid "Lists service providers." -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-v3-ext.xml:14(title) ./api-ref/src/docbkx/itemizedlist-service-list.xml:50(link) -msgid "Identity API v3 extensions (CURRENT)" -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-v3-ext.xml:15(para) -msgid "This page describes these Identity API v3 extensions:" -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-v3-ext.xml:21(link) ./api-ref/src/docbkx/ch_identity-v3-ext.xml:56(title) -msgid "OS-ENDPOINT-POLICY extension (OS-ENDPOINT-POLICY)" -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-v3-ext.xml:28(link) ./api-ref/src/docbkx/ch_identity-v3-ext.xml:127(title) -msgid "OS-INHERIT extension (OS-INHERIT)" -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-v3-ext.xml:35(link) ./api-ref/src/docbkx/ch_identity-v3-ext.xml:141(title) -msgid "Key Distribution Server (KDS) extension (OS-KDS)" -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-v3-ext.xml:42(link) ./api-ref/src/docbkx/ch_identity-v3-ext.xml:364(title) -msgid "OAuth extension (OS-OAUTH1)" -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-v3-ext.xml:49(link) ./api-ref/src/docbkx/ch_identity-v3-ext.xml:431(title) -msgid "Trust extension (OS-TRUST)" -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-v3-ext.xml:57(para) -msgid "Creates, verifies, and deletes associations between service endpoints and policies. Such associations enable an endpoint to request its policy." -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-v3-ext.xml:62(para) -msgid "To create, check, or delete an association, you reference a policy by its ID in the Identity server." -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-v3-ext.xml:66(para) -msgid "The extension supports these associations:" -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-v3-ext.xml:71(para) -msgid "A policy and endpoint association." -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-v3-ext.xml:76(para) -msgid "A policy and service-type endpoint in a region association." -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-v3-ext.xml:81(para) -msgid "A policy and service-type endpoint association." -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-v3-ext.xml:86(para) -msgid "This order reflects policies in their most to least-specific order." -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-v3-ext.xml:89(para) -msgid "When an endpoint requests the appropriate policy for itself, the extension finds the policy by traversing the ordered sequence of methods of association. The extension shows the policy for the first association that it finds." -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-v3-ext.xml:95(para) -msgid "If the region of the endpoint has a parent, the extension examines the region associations up the region tree in ascending order. For region associations, the extension examines any parent regions in ascending order. The extension does not combine polices." -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-v3-ext.xml:128(para) -msgid "Enables projects to inherit role assignments from either their owning domain or projects that are higher in the hierarchy." -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-v3-ext.xml:132(para) -msgid "(Since API v3.4) The OS-INHERIT extension allows inheritance from both projects and domains. To access project inheritance, the Identity service server must run at least API v3.4." -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-v3-ext.xml:142(para) -msgid "The Key Distribution Server (KDS) is a trusted third party that generates and securely distributes signing and encryption keys to communicating parties. These shared keys enable parties to exchange authenticated, confidential messages. KDS is an integral part of the RPC message security implementation. To establish a trusted relationship between the party and the KDS, a properly authorized user, such as a cloud administrator, must assign a long-term shared key to the communicating party. Assigning a key to a party requires assigning an identity to that party in the KDS. An identity includes a unique party name and the associated long-term shared key. This party name is used to identify a party when it communicates with KDS or another party." -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-v3-ext.xml:156(para) -msgid "The KDS enables two individual parties or one individual party and a group party to exchange secure messages. To get keys so that it can communicate with another party, a party makes an authenticated request to KDS for a ticket. The KDS returns an encrypted ticket to the requesting party. The KDS encrypts the ticket with the long-term shared key that is associated with that party. Only the associated party or the KDS itself can decrypt the ticket." -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-v3-ext.xml:165(para) -msgid "The KDS issues a ticket that contains a copy of the shared encryption and signing keys. These keys are for the source party, which is the party that requests the ticket. The ticket also contains a payload that is intended for the destination party, which is the party with whom the source party wants to communicate. This payload contains the information that the destination party can use to derive the shared encryption and signing keys. When the destination party is:" -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-v3-ext.xml:177(para) -msgid "An individual. The payload is encrypted with the long-term shared key that is associated with the destination party." -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-v3-ext.xml:183(para) -msgid "A group. The payload is encrypted with a shared group key that the KDS makes available to all members of the group. This encryption enables the destination party to trust that the information in the payload was supplied by the KDS." -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-v3-ext.xml:192(para) -msgid "When the source party is ready to communicate with the destination party, it sends this encrypted payload to the destination party along with whatever data it has protected with the shared signing and encryption keys. The destination party can decrypt the payload and derive the shared encryption and signing keys by using the payload information. Both parties have a copy of the shared signing and encryption keys that are trusted as being issued by the KDS. The destination party uses these shared keys to authenticate and decrypt the data sent by the source party." -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-v3-ext.xml:203(para) -msgid "Other guidelines:" -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-v3-ext.xml:206(para) -msgid "When a source party must send secure messages to multiple recipients, an authorized user can define a KDS group for the recipients. Membership in a group is determined by comparing a party name with the group name. The party is considered a member if the party name matches <group name>.*. For example, a party named scheduler.host.example.com is considered a member of the scheduler group. This method is the same method that is used to name message queues in OpenStack." -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-v3-ext.xml:220(para) -msgid "When a source party requests a ticket for a destination party that is a group, KDS generates a short-lived group key and assigns it to the group. This group key is used to encrypt the payload in the ticket, which contains the information that the destination party uses to derive the shared signing and encryption keys." -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-v3-ext.xml:230(para) -msgid "When an individual destination party must decrypt the payload that it receives from the source party as a part of a group message, it makes an authenticated request to KDS to get the short-lived group key. If the requester is a member of the target group, KDS provides the short-lived group key encrypted with the long-term shared key associated with the individual destination party. The individual destination party can then decrypt the group key, which enables it to decrypt the payload and derive the shared signing and encryption keys to use to authenticate and decrypt the data sent by the source party." -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-v3-ext.xml:246(para) -msgid "When a sender gets keys to send a message to a group, all group members and the sender share the signing and encryption keys, which makes it impossible for an individual destination party to determine whether a message was sent by the source party or by another destination party who is a group member. The destination party can confirm only that the message was sent by a party who has the shared signing and encryption keys. When a sender uses keys to send a message to a group, all group members must trust other members to operate in good faith." -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-v3-ext.xml:260(para) -msgid "The signing and encryption keys that communicating parties share are short-lived. The life span of these keys is defined by a validity period that is set by the KDS when it issues the ticket. A suggested reasonable default validity period is 15 minutes, though the implementation determines the appropriate validity period." -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-v3-ext.xml:268(para) -msgid "After the validity period for the keys expires, a party should refuse to use those keys to prevent the use of compromised keys. This requires the source party to request a new ticket from the KDS to get a new set of keys. An implementation can implement a grace period to account for clock skew between parties. This grace period enables a destination party to accept messages that use recently expired keys. If you use a grace period, its duration should be five or fewer minutes." -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-v3-ext.xml:278(para) -msgid "A key server, unlike a pure public key-based system, can regulate the encryption and signing key exchange. When keys are requested, the key server actively distributes keys to communicating parties, applies access control, and denies communication between arbitrary peers in the system. This enables centralized access control, prevents unauthorized communication, and eliminates the need to perform post-authentication access control and policy lookups on the receiving side." -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-v3-ext.xml:288(para) -msgid "The KDS requires that all ticket requests are authenticated and, where appropriate, data is encrypted. You must pass any time stamp value to the API as a UTCISO 8601 date and time string that includes microseconds. For example, 2012-03-26T10:01:01.720000." -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-v3-ext.xml:297(para) -msgid "The default algorithms for message authentication and encryption are, respectively, HMAC-SHA-256 and AES-128-CBC. Therefore, the default block size is 128 bit." -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-v3-ext.xml:302(para) -msgid "The source party that requests a ticket must send the encrypted esek payload to the destination party. The source and destination strings used when requesting the ticket also must be sent to the destination party to enable it to derive the shared signing end encryption keys. The messaging implementation is responsible for transferring this data to the destination party." -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-v3-ext.xml:310(para) -msgid "The key derivation used to generate the shared signing and encryption keys uses the Hashed Message Authentication Code (HMAC)-based key derivation function (HKDF) standard, as described in RFC 5869. The destination party must use the HKDF expand function by using the information that it receives from the source party to complete derivation of the shared signing and encryption keys. The inputs to the HKDF expand function are:" -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-v3-ext.xml:321(para) -msgid "The info input for the HKDF expand function is a string that concatenates the source, destination, and esek.timestamp strings by using a comma (,) separator between each element. The following example shows a valid info string where scheduler.host.example.com is the source, compute.host.example.com is the destination, and 2012-03-26T10:01:01.720000 is the esek.timestamp:" -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-v3-ext.xml:333(para) -msgid "The output of the HKDF expand function is an array of bytes of 256 bit length. The first half is the signing key, and the second half is the encryption key." -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-v3-ext.xml:338(para) -msgid "Create and delete requests for long-term keys are restricted to authorized users, such as cloud administrators. The authentication and authorization for these requests is left up to the implementation, though the implementation should leverage the Identity API for these purposes." -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-v3-ext.xml:365(para) -msgid "Enables users to delegate roles to third-party consumers through The OAuth 1.0 Protocol." -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-v3-ext.xml:370(para) -msgid "A user is an Identity API user who delegates its roles and who authorizes request tokens." -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-v3-ext.xml:374(para) -msgid "A consumer is a third-party application that uses OAuth to access a protected resource." -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-v3-ext.xml:378(para) -msgid "Administrative users use an OAuth-derived token to act on behalf of the authorizing user." -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-v3-ext.xml:382(para) -msgid "The consumer uses a request token to get authorization from the user. The consumer provides an OAuth verifier string with the request token in exchange for an access token." -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-v3-ext.xml:387(para) -msgid "The consumer uses an access token to request Identity API tokens on behalf of the authorizing user instead of using the credentials for the user." -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-v3-ext.xml:392(para) -msgid "Request and access tokens use token keys to identify themselves. For OpenStack purposes, the token key is the token ID. The consumer uses a token secret to establish ownership of a token. Both request and access tokens have token secrets." -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-v3-ext.xml:398(para) -msgid "Delegated authentication through OAuth occurs as follows:" -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-v3-ext.xml:403(para) -msgid "A user creates a consumer." -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-v3-ext.xml:406(para) -msgid "The consumer gets an unauthorized request token. Then, the consumer uses the request token to initiate user authorization." -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-v3-ext.xml:411(para) -msgid "The user authorizes the request token." -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-v3-ext.xml:414(para) -msgid "The consumer exchanges the authorized request token and the OAuth verifier for an access token." -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-v3-ext.xml:418(para) -msgid "The authorizing user receives the request token key from the consumer out-of-band." -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-v3-ext.xml:422(para) -msgid "The consumer uses the access token to request an Identity API token." -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-v3-ext.xml:432(para) -msgid "Creates a trust." -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-v3-ext.xml:435(para) -msgid "A trust is an OpenStack Identity extension that enables delegation and, optionally, impersonation through keystone. A trust extension defines a relationship between a trustor and trustee. A trustor is the user who delegates a limited set of their own rights to another user, known as the trustee, for a limited time." -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-v3-ext.xml:443(para) -msgid "The trust can eventually enable the trustee to impersonate the trustor. For security reasons, some safety measures are added. For example, if a trustor loses a given role, the API automatically revokes any trusts and the related tokens that the user issued with that role." -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-v3-ext.xml:450(para) -msgid "For more information, see Use trusts." -msgstr "" - -#: ./api-ref/src/docbkx/api-ref-identity-admin-v2.xml:11(title) -msgid "OpenStack Identity Admin API v2 (SUPPORTED)" -msgstr "" - -#: ./api-ref/src/docbkx/api-ref-data-processing-v1.1.xml:10(title) -msgid "OpenStack Data Processing API v1.1 (CURRENT)" -msgstr "" - -#: ./api-ref/src/docbkx/ch_objectstorage-v1.xml:14(title) ./api-ref/src/docbkx/itemizedlist-service-list.xml:90(link) -msgid "Object Storage API v1 (SUPPORTED)" -msgstr "" - -#: ./api-ref/src/docbkx/ch_objectstorage-v1.xml:15(para) -msgid "Manages the accounts, containers, and objects in the Object Storage system." -msgstr "" - -#: ./api-ref/src/docbkx/ch_objectstorage-v1.xml:19(para) -msgid "To run the cURL command examples for these requests, set these environment variables:" -msgstr "" - -#: ./api-ref/src/docbkx/ch_objectstorage-v1.xml:25(para) -msgid "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." -msgstr "" - -#: ./api-ref/src/docbkx/ch_objectstorage-v1.xml:33(para) -msgid "token. The authentication token for Object Storage." -msgstr "" - -#: ./api-ref/src/docbkx/ch_objectstorage-v1.xml:39(para) -msgid "To obtain these values, run the command." -msgstr "" - -#: ./api-ref/src/docbkx/ch_objectstorage-v1.xml:43(para) -msgid "As shown in this example, the public URL appears in the StorageURL field, and the token appears in the Auth Token field:" -msgstr "" - -#: ./api-ref/src/docbkx/ch_objectstorage-v1.xml:59(para) -msgid "For a complete description of HTTP 1.1 header definitions, see Header Field Definitions." -msgstr "" - -#: ./api-ref/src/docbkx/ch_objectstorage-v1.xml:64(para) -msgid "The API returns the Range Not Satisfiable (416) response code for any ranged requests that specify more than:" -msgstr "" - -#: ./api-ref/src/docbkx/ch_objectstorage-v1.xml:70(para) -msgid "Fifty ranges." -msgstr "" - -#: ./api-ref/src/docbkx/ch_objectstorage-v1.xml:75(para) -msgid "Three overlapping ranges." -msgstr "" - -#: ./api-ref/src/docbkx/ch_objectstorage-v1.xml:80(para) -msgid "Eight non-increasing ranges." -msgstr "" - -#: ./api-ref/src/docbkx/ch_objectstorage-v1.xml:86(title) -msgid "Discoverability" -msgstr "" - -#: ./api-ref/src/docbkx/ch_objectstorage-v1.xml:87(para) -msgid "If configured, lists the activated capabilities for this version of the OpenStack Object Storage API." -msgstr "" - -#: ./api-ref/src/docbkx/ch_objectstorage-v1.xml:98(title) -msgid "Endpoints" -msgstr "" - -#: ./api-ref/src/docbkx/ch_objectstorage-v1.xml:99(para) -msgid "If configured, lists endpoints for an account." -msgstr "" - -#: ./api-ref/src/docbkx/ch_objectstorage-v1.xml:110(title) -msgid "Accounts" -msgstr "" - -#: ./api-ref/src/docbkx/ch_objectstorage-v1.xml:111(para) -msgid "Lists containers for an account. Creates, updates, shows, and deletes account metadata." -msgstr "" - -#: ./api-ref/src/docbkx/ch_objectstorage-v1.xml:115(para) -msgid "Account metadata operations work differently than container and object metadata operations work. Depending on the contents of your account metadata request, the Object Storage API updates the metadata in one of these ways:" -msgstr "" - -#: ./api-ref/src/docbkx/ch_objectstorage-v1.xml:122(caption) -msgid "Account metadata operations" -msgstr "" - -#: ./api-ref/src/docbkx/ch_objectstorage-v1.xml:127(th) -msgid "POST request body contains" -msgstr "" - -#: ./api-ref/src/docbkx/ch_objectstorage-v1.xml:134(para) ./api-ref/src/docbkx/ch_objectstorage-v1.xml:150(para) -msgid "A metadata key without a value." -msgstr "" - -#: ./api-ref/src/docbkx/ch_objectstorage-v1.xml:137(para) ./api-ref/src/docbkx/ch_objectstorage-v1.xml:169(para) -msgid "The metadata key already exists for the account." -msgstr "" - -#: ./api-ref/src/docbkx/ch_objectstorage-v1.xml:142(para) -msgid "The API removes the metadata item from the account." -msgstr "" - -#: ./api-ref/src/docbkx/ch_objectstorage-v1.xml:153(para) ./api-ref/src/docbkx/ch_objectstorage-v1.xml:184(para) -msgid "The metadata key does not already exist for the account." -msgstr "" - -#: ./api-ref/src/docbkx/ch_objectstorage-v1.xml:159(para) -msgid "The API ignores the metadata key." -msgstr "" - -#: ./api-ref/src/docbkx/ch_objectstorage-v1.xml:166(para) ./api-ref/src/docbkx/ch_objectstorage-v1.xml:181(para) -msgid "A metadata key value." -msgstr "" - -#: ./api-ref/src/docbkx/ch_objectstorage-v1.xml:174(para) -msgid "The API updates the metadata key value for the account." -msgstr "" - -#: ./api-ref/src/docbkx/ch_objectstorage-v1.xml:190(para) -msgid "The API adds the metadata key and value pair, or item, to the account." -msgstr "" - -#: ./api-ref/src/docbkx/ch_objectstorage-v1.xml:198(para) -msgid "One or more account metadata items are omitted." -msgstr "" - -#: ./api-ref/src/docbkx/ch_objectstorage-v1.xml:201(para) -msgid "The metadata items already exist for the account." -msgstr "" - -#: ./api-ref/src/docbkx/ch_objectstorage-v1.xml:207(para) -msgid "The API does not change the existing metadata items." -msgstr "" - -#: ./api-ref/src/docbkx/ch_objectstorage-v1.xml:215(para) -msgid "For these requests, specifying the X-Remove-Account-Meta-* request header for the key with any value is equivalent to specifying the X-Account-Meta-* request header with an empty value." -msgstr "" - -#: ./api-ref/src/docbkx/ch_objectstorage-v1.xml:220(para) -msgid "Metadata keys must be treated as case-insensitive at all times. These keys can contain ASCII 7-bit characters that are not control (0-31) characters, DEL, or a separator character, according to HTTP/1.1. Also, Object Storage does not support the underscore character, which it silently converts to a hyphen." -msgstr "" - -#: ./api-ref/src/docbkx/ch_objectstorage-v1.xml:228(para) -msgid "The metadata values in Object Storage do not follow HTTP/1.1 rules for character encodings. You must use a UTF-8 encoding to get a byte array for any string that contains characters that are not in the 7-bit ASCII 0-127 range. Otherwise, Object Storage returns the 404 response code for ISO-8859-1 characters in the 128-255 range, which is a direct violation of the HTTP/1.1 basic rules." -msgstr "" - -#: ./api-ref/src/docbkx/ch_objectstorage-v1.xml:247(title) -msgid "Containers" -msgstr "" - -#: ./api-ref/src/docbkx/ch_objectstorage-v1.xml:248(para) -msgid "Lists objects in a container. Creates, shows details for, and deletes containers. Creates, updates, shows, and deletes container metadata." -msgstr "" - -#: ./api-ref/src/docbkx/ch_objectstorage-v1.xml:265(title) -msgid "Objects" -msgstr "" - -#: ./api-ref/src/docbkx/ch_objectstorage-v1.xml:266(para) -msgid "Creates, replaces, shows details for, and deletes objects. Copies objects from another object with a new or different name. Updates object metadata." -msgstr "" - -#: ./api-ref/src/docbkx/ch_database-v1.xml:10(title) ./api-ref/src/docbkx/itemizedlist-service-list.xml:40(link) -msgid "Database Service API v1.0 (CURRENT)" -msgstr "" - -#: ./api-ref/src/docbkx/ch_database-v1.xml:13(para) -msgid "Lists information for all Database Service API versions and shows Database Service v1.0 details." -msgstr "" - -#: ./api-ref/src/docbkx/ch_database-v1.xml:30(title) -msgid "Database instances (instances)" -msgstr "" - -#: ./api-ref/src/docbkx/ch_database-v1.xml:31(para) -msgid "Creates, lists, shows details for, attaches a configuration group to, detaches a configuration group from, deletes, lists configuration defaults, creates root, and determines whether root is enables for instances." -msgstr "" - -#: ./api-ref/src/docbkx/ch_database-v1.xml:57(title) -msgid "Database instance actions (action)" -msgstr "" - -#: ./api-ref/src/docbkx/ch_database-v1.xml:58(para) -msgid "Resizes instances and volumes and restarts instances." -msgstr "" - -#: ./api-ref/src/docbkx/ch_database-v1.xml:73(title) -msgid "Databases (databases)" -msgstr "" - -#: ./api-ref/src/docbkx/ch_database-v1.xml:74(para) -msgid "Creates, lists all, and deletes databases." -msgstr "" - -#: ./api-ref/src/docbkx/ch_database-v1.xml:90(title) -msgid "Users (users)" -msgstr "" - -#: ./api-ref/src/docbkx/ch_database-v1.xml:91(para) -msgid "Creates, lists all, and deletes users." -msgstr "" - -#: ./api-ref/src/docbkx/ch_database-v1.xml:110(title) -msgid "Flavors (flavors)" -msgstr "" - -#: ./api-ref/src/docbkx/ch_database-v1.xml:111(para) -msgid "Lists all flavors and shows details for a flavor, by ID." -msgstr "" - -#: ./api-ref/src/docbkx/ch_database-v1.xml:126(title) -msgid "Data stores (datastores)" -msgstr "" - -#: ./api-ref/src/docbkx/ch_database-v1.xml:127(para) -msgid "Lists data store versions, lists parameters for data stores, and shows parameter details for a data store version." -msgstr "" - -#: ./api-ref/src/docbkx/ch_database-v1.xml:146(title) -msgid "Configuration groups (configurations)" -msgstr "" - -#: ./api-ref/src/docbkx/ch_database-v1.xml:147(para) -msgid "Creates and lists all configuration groups." -msgstr "" - -#: ./api-ref/src/docbkx/ch_blockstorage-api-v1.xml:10(title) ./api-ref/src/docbkx/itemizedlist-service-list.xml:20(link) -msgid "Block Storage API v1 (DEPRECATED)" -msgstr "" - -#: ./api-ref/src/docbkx/ch_blockstorage-api-v1.xml:11(para) -msgid "Block Storage API v1 is deprecated in Kilo." -msgstr "" - -#: ./api-ref/src/docbkx/ch_blockstorage-api-v1.xml:14(para) ./api-ref/src/docbkx/ch_blockstorage-api-v2.xml:11(para) -msgid "Manages volumes and snapshots for use with the Block Storage API, also known as cinder services." -msgstr "" - -#: ./api-ref/src/docbkx/ch_blockstorage-api-v1.xml:18(para) -msgid "When you create, list, or delete volumes, the following status values are possible:" -msgstr "" - -#: ./api-ref/src/docbkx/ch_blockstorage-api-v1.xml:23(para) -msgid "CREATING. The volume is being created." -msgstr "" - -#: ./api-ref/src/docbkx/ch_blockstorage-api-v1.xml:24(para) -msgid "AVAILABLE. The volume is ready to attach to an instance." -msgstr "" - -#: ./api-ref/src/docbkx/ch_blockstorage-api-v1.xml:26(para) -msgid "ATTACHING. The volume is attaching to an instance." -msgstr "" - -#: ./api-ref/src/docbkx/ch_blockstorage-api-v1.xml:28(para) -msgid "IN-USE. The volume is attached to an instance." -msgstr "" - -#: ./api-ref/src/docbkx/ch_blockstorage-api-v1.xml:30(para) -msgid "DELETING. The volume is being deleted." -msgstr "" - -#: ./api-ref/src/docbkx/ch_blockstorage-api-v1.xml:31(para) -msgid "ERROR. An error occurred." -msgstr "" - -#: ./api-ref/src/docbkx/ch_blockstorage-api-v1.xml:32(para) -msgid "ERROR_DELETING. A volume deletion error occurred." -msgstr "" - -#: ./api-ref/src/docbkx/ch_blockstorage-api-v1.xml:38(para) -msgid "Lists information about API versions." -msgstr "" - -#: ./api-ref/src/docbkx/ch_blockstorage-api-v1.xml:51(title) -msgid "Volumes" -msgstr "" - -#: ./api-ref/src/docbkx/ch_blockstorage-api-v1.xml:52(para) -msgid "The snapshot_id and source_volid parameters specify the ID of the snapshot or volume from which the volume originates. If the volume was not created from a snapshot or source volume, these values are null." -msgstr "" - -#: ./api-ref/src/docbkx/ch_blockstorage-api-v1.xml:73(title) -msgid "Volume types" -msgstr "" - -#: ./api-ref/src/docbkx/ch_blockstorage-api-v1.xml:74(para) -msgid "Lists, creates, updates, shows information for, and deletes volume types." -msgstr "" - -#: ./api-ref/src/docbkx/ch_blockstorage-api-v1.xml:91(title) -msgid "Snapshots" -msgstr "" - -#: ./api-ref/src/docbkx/ch_blockstorage-api-v1.xml:92(para) -msgid "Creates, lists, shows information for, and deletes snapshots. Shows and updates snapshot metadata." -msgstr "" - -#: ./api-ref/src/docbkx/ch_blockstorage-api-v1.xml:115(title) ./api-ref/src/docbkx/ch_blockstorage-api-v2.xml:340(title) -msgid "Quota sets extension (os-quota-sets)" -msgstr "" - -#: ./api-ref/src/docbkx/ch_blockstorage-api-v1.xml:116(para) ./api-ref/src/docbkx/ch_blockstorage-api-v2.xml:341(para) ./api-ref/src/docbkx/ch_blockstorage-api-v2.xml:368(para) -msgid "Administrators only, depending on policy settings." -msgstr "" - -#: ./api-ref/src/docbkx/ch_blockstorage-api-v1.xml:119(para) ./api-ref/src/docbkx/ch_blockstorage-api-v2.xml:344(para) -msgid "Shows, updates, and deletes quotas for a tenant." -msgstr "" - -#: ./api-ref/src/docbkx/api-ref-baremetal-v1.xml:11(title) -msgid "OpenStack Bare Metal API v1 (CURRENT)" -msgstr "" - -#: ./api-ref/src/docbkx/api-ref-baremetal-v1.xml:13(year) -msgid "2016" -msgstr "" - -#: ./api-ref/src/docbkx/preface.xml:9(title) -msgid "OpenStack API Complete Reference" -msgstr "" - -#: ./api-ref/src/docbkx/preface.xml:10(para) -msgid "Use the OpenStack APIs and extensions to launch server instances, create images, assign metadata to instances and images, create containers and objects, and complete other actions in your OpenStack cloud." -msgstr "" - -#: ./api-ref/src/docbkx/preface.xml:16(para) -msgid "The API status reflects the state of the endpoint on the service. CURRENT is a stable version that is up-to-date, recent, and might receive future versions. This endpoint should be prioritized over all others. SUPPORTED is a stable version that is available on the server. However, it is not likely the most recent available and might not be updated or might be deprecated at some time in the future. DEPRECATED is a stable version that is still available but is being deprecated and might be removed in the future. EXPERIMENTAL is not a stable version. This version is under development or contains features that are otherwise subject to change. For more information about API status values and version information, see Version Discovery." -msgstr "" - -#: ./api-ref/src/docbkx/preface.xml:34(para) -msgid "You must install the packages for each API separately." -msgstr "" - -#: ./api-ref/src/docbkx/preface.xml:37(para) -msgid "You can use the APIs and extensions after you authenticate through the Identity API. In exchange for a set of authentication credentials, the Identity service generates tokens. A token represents the authenticated identity of a user and, optionally, grants authorization on a specific project or domain." -msgstr "" - -#: ./api-ref/src/docbkx/preface.xml:44(para) ./api-ref/src/docbkx/ch_identity-v3.xml:134(para) -msgid "The body of an authentication request must include a payload that specifies the authentication method, which is password or token, the credentials, and, optionally, the authorization scope. You can scope a token to a project or domain, or the token can be unscoped. You cannot scope a token to both a project and domain." -msgstr "" - -#: ./api-ref/src/docbkx/preface.xml:61(para) -msgid "To get started with the APIs, see the OpenStack API Guide." -msgstr "" - -#: ./api-ref/src/docbkx/api-ref-networking-v2-ext.xml:11(title) -msgid "OpenStack Networking API v2.0 extensions (CURRENT)" -msgstr "" - -#: ./api-ref/src/docbkx/api-ref-orchestration-v1.xml:11(title) -msgid "OpenStack Orchestration API v1 (CURRENT)" -msgstr "" - -#: ./api-ref/src/docbkx/ch_telemetry-v2.xml:10(title) ./api-ref/src/docbkx/itemizedlist-service-list.xml:110(link) -msgid "Telemetry API v2 (CURRENT)" -msgstr "" - -#: ./api-ref/src/docbkx/ch_telemetry-v2.xml:11(para) -msgid "Manages alarms, meters, samples, resources, and capabilities through a set of services:" -msgstr "" - -#: ./api-ref/src/docbkx/ch_telemetry-v2.xml:17(para) -msgid "Aodh. An alarm service." -msgstr "" - -#: ./api-ref/src/docbkx/ch_telemetry-v2.xml:23(para) -msgid " Ceilometer . A data collection service." -msgstr "" - -#: ./api-ref/src/docbkx/ch_telemetry-v2.xml:29(para) -msgid "Gnocchi. A time-series database and resource indexing service." -msgstr "" - -#: ./api-ref/src/docbkx/ch_telemetry-v2.xml:36(para) -msgid "If Gnocchi is enabled, meters, samples, and resources API operations return the 410 response code." -msgstr "" - -#: ./api-ref/src/docbkx/ch_telemetry-v2.xml:41(title) -msgid "Alarms" -msgstr "" - -#: ./api-ref/src/docbkx/ch_telemetry-v2.xml:42(para) -msgid "Lists, creates, gets details for, updates, and deletes alarms." -msgstr "" - -#: ./api-ref/src/docbkx/ch_telemetry-v2.xml:70(title) -msgid "Meters" -msgstr "" - -#: ./api-ref/src/docbkx/ch_telemetry-v2.xml:71(para) -msgid "Lists all meters, adds samples to meters, and lists samples for meters. For list operations, if you do not explicitly set the limit query parameter, a default limit is applied. The default limit is the default_api_return_limit configuration option value." -msgstr "" - -#: ./api-ref/src/docbkx/ch_telemetry-v2.xml:78(para) -msgid "Also, computes and lists statistics for samples in a time range. You can use the aggregate query parameter in the statistics URI to explicitly select the stddev, cardinality, or any other standard function. For example:" -msgstr "" - -#: ./api-ref/src/docbkx/ch_telemetry-v2.xml:86(para) -msgid "The aggregate.param parameter value is optional for all functions except the cardinality function." -msgstr "" - -#: ./api-ref/src/docbkx/ch_telemetry-v2.xml:90(para) -msgid "The API silently ignores any duplicate aggregate function and parameter pairs." -msgstr "" - -#: ./api-ref/src/docbkx/ch_telemetry-v2.xml:94(para) -msgid "The API accepts and storage drivers support duplicate functions with different parameter values. In this example, the cardinality function is accepted twice with two different parameter values:" -msgstr "" - -#: ./api-ref/src/docbkx/ch_telemetry-v2.xml:102(emphasis) -msgid "Examples:" -msgstr "" - -#: ./api-ref/src/docbkx/ch_telemetry-v2.xml:103(para) -msgid "Use the stddev function to request the standard deviation of CPU utilization:" -msgstr "" - -#: ./api-ref/src/docbkx/ch_telemetry-v2.xml:108(para) ./api-ref/src/docbkx/ch_telemetry-v2.xml:150(para) -msgid "The response looks like this:" -msgstr "" - -#: ./api-ref/src/docbkx/ch_telemetry-v2.xml:126(para) -msgid "Use the cardinality function with the project ID to return the number of distinct tenants with images:" -msgstr "" - -#: ./api-ref/src/docbkx/ch_telemetry-v2.xml:131(para) -msgid "The following, more complex, example determines:" -msgstr "" - -#: ./api-ref/src/docbkx/ch_telemetry-v2.xml:136(para) -msgid "The number of distinct instances (cardinality)" -msgstr "" - -#: ./api-ref/src/docbkx/ch_telemetry-v2.xml:141(para) -msgid "The total number of instance samples (count) for a tenant in 15-minute intervals (period and groupby options)" -msgstr "" - -#: ./api-ref/src/docbkx/ch_telemetry-v2.xml:223(title) -msgid "Samples" -msgstr "" - -#: ./api-ref/src/docbkx/ch_telemetry-v2.xml:224(para) -msgid "Lists all samples and gets information for a sample." -msgstr "" - -#: ./api-ref/src/docbkx/ch_telemetry-v2.xml:227(para) -msgid "For list operations, if you do not explicitly set the limit query parameter, a default limit is applied. The default limit is the default_api_return_limit configuration option value." -msgstr "" - -#: ./api-ref/src/docbkx/ch_telemetry-v2.xml:245(title) -msgid "Resources" -msgstr "" - -#: ./api-ref/src/docbkx/ch_telemetry-v2.xml:246(para) -msgid "Lists all and gets information for resources." -msgstr "" - -#: ./api-ref/src/docbkx/ch_telemetry-v2.xml:259(title) -msgid "Capabilities" -msgstr "" - -#: ./api-ref/src/docbkx/ch_telemetry-v2.xml:260(para) -msgid "Gets information for API and storage capabilities." -msgstr "" - -#: ./api-ref/src/docbkx/ch_telemetry-v2.xml:261(para) -msgid "The Telemetry service enables you to store samples, events, and alarm definitions in supported database back ends. The capabilities resource enables you to list the capabilities that a database supports." -msgstr "" - -#: ./api-ref/src/docbkx/ch_telemetry-v2.xml:267(para) -msgid "The capabilities resource returns a flattened dictionary of capability properties, each with an associated boolean value. A value of true indicates that the corresponding capability is available in the back end." -msgstr "" - -#: ./api-ref/src/docbkx/ch_telemetry-v2.xml:273(para) -msgid "You can optionally configure separate database back ends for samples, events, and alarms definitions. The capabilities response shows a value of true to indicate that the definitions database for samples, events, or alarms is ready to use in a production environment." -msgstr "" - -#: ./api-ref/src/docbkx/ch_telemetry-v2.xml:289(title) ./api-ref/src/docbkx/ch_clustering-v1.xml:90(title) -msgid "Events" -msgstr "" - -#: ./api-ref/src/docbkx/ch_telemetry-v2.xml:290(para) -msgid "Lists all events and shows details for an event." -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-v3.xml:14(title) ./api-ref/src/docbkx/itemizedlist-service-list.xml:45(link) -msgid "Identity API v3 (CURRENT)" -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-v3.xml:15(para) -msgid "The Identity service generates authentication tokens that permit access to the OpenStack services REST APIs. Clients obtain this token and the URL endpoints for other service APIs by supplying their valid credentials to the authentication service." -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-v3.xml:21(para) -msgid "Each time you make a REST API request to an OpenStack service, you supply your authentication token in the X-Auth-Token request header." -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-v3.xml:26(para) -msgid "Like most OpenStack projects, OpenStack Identity protects its APIs by defining policy rules based on a role-based access control (RBAC) approach." -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-v3.xml:31(para) -msgid "The Identity service keystone.conf configuration file sets the name and location of a JSON policy file that stores these rules." -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-v3.xml:36(para) -msgid "For information about Identity API protection, see Identity API protection with role-based access control (RBAC) in the OpenStack Cloud Administrator Guide." -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-v3.xml:42(para) -msgid "This page lists the Identity API operations in the following order:" -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-v3.xml:53(link) -msgid "Authentication and token management" -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-v3.xml:58(link) -msgid "Credentials" -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-v3.xml:63(link) -msgid "Domains" -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-v3.xml:68(link) -msgid "Domain configuration" -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-v3.xml:73(link) -msgid "Groups" -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-v3.xml:78(link) ./api-ref/src/docbkx/ch_clustering-v1.xml:125(title) -msgid "Policies" -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-v3.xml:83(link) -msgid "Projects" -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-v3.xml:88(link) -msgid "Regions" -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-v3.xml:93(link) -msgid "Roles and role assignments" -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-v3.xml:98(link) -msgid "Service catalog and endpoints" -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-v3.xml:127(title) -msgid "Authentication and token management (auth, tokens)" -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-v3.xml:128(para) -msgid "In exchange for a set of authentication credentials, the Identity service generates tokens. A token represents the authenticated identity of a user and, optionally, grants authorization on a specific project or domain." -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-v3.xml:142(para) -msgid "Tokens have IDs, which the Identity API returns in the X-Subject-Token response header." -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-v3.xml:146(para) -msgid "Also, validates an authentication token and lists the domains, projects, roles, and endpoints to which the token gives access. Forces the immediate revocation of a token." -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-v3.xml:151(para) -msgid "After you obtain an authentication token, you can:" -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-v3.xml:156(para) -msgid "Make REST API requests to other OpenStack services. You supply the ID of your authentication token in the X-Auth-Token request header." -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-v3.xml:163(para) -msgid "Validate your authentication token and list the domains, projects, roles, and endpoints that your token gives you access to." -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-v3.xml:170(para) -msgid "Use your token to request another token scoped for a different domain and project." -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-v3.xml:176(para) -msgid "Force the immediate revocation of a token." -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-v3.xml:181(para) -msgid "List revoked public key infrastructure (PKI) tokens." -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-v3.xml:186(para) -msgid "The Identity API treats expired tokens as no longer valid tokens. The deployment determines how long expired tokens are stored." -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-v3.xml:191(para) -msgid "These authentication errors can occur:" -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-v3.xml:195(caption) -msgid "Authentication errors" -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-v3.xml:200(th) -msgid "Response code" -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-v3.xml:208(code) -msgid "Bad Request (400)" -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-v3.xml:212(para) -msgid "The Identity service failed to parse the request as expected. One of the following errors occurred:" -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-v3.xml:218(para) -msgid "A required attribute was missing." -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-v3.xml:223(para) -msgid "An attribute that is not allowed was specified, such as an ID on a request in a basic CRUD operation." -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-v3.xml:230(para) -msgid "An attribute of an unexpected data type was specified." -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-v3.xml:241(code) -msgid "Unauthorized (401)" -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-v3.xml:245(para) -msgid "One of the following errors occurred:" -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-v3.xml:250(para) -msgid "Authentication was not performed." -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-v3.xml:255(para) -msgid "The specified X-Auth-Token header is not valid." -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-v3.xml:261(para) -msgid "The authentication credentials are not valid." -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-v3.xml:271(code) -msgid "Forbidden (403)" -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-v3.xml:275(para) -msgid "The identity was successfully authenticated but it is not authorized to perform the requested action." -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-v3.xml:284(code) -msgid "Not Found (404)" -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-v3.xml:288(para) -msgid "An operation failed because a referenced entity cannot be found by ID. For a request, the referenced entity might be specified in the request body rather than in the resource path." -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-v3.xml:299(code) -msgid "Conflict (409)" -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-v3.xml:303(para) -msgid "A or operation failed. For example, a client tried to update a unique attribute for an entity, which conflicts with that of another entity in the same collection." -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-v3.xml:309(para) -msgid "Or, a client issued a create operation twice on a collection with a user-defined, unique attribute. For example, a client made a /users request two times for the unique, user-defined name attribute for a user entity." -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-v3.xml:339(title) -msgid "Credentials (credentials)" -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-v3.xml:340(para) -msgid "In exchange for a set of authentication credentials that the user submits, the Identity service generates and returns a token. A token represents the authenticated identity of a user and, optionally, grants authorization on a specific project or domain." -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-v3.xml:346(para) -msgid "You can list all credentials, and create, show details for, update, and delete a credential." -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-v3.xml:359(title) -msgid "Domains (domains, users, groups, roles)" -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-v3.xml:360(para) -msgid "A domain is a collection of users, groups, and projects. Each group and project is owned by exactly one domain." -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-v3.xml:364(para) -msgid "Each domain defines a namespace where certain API-visible name attributes exist, which affects whether those names must be globally unique or unique within that domain. In the Identity API, the uniqueness of these attributes is as follows:" -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-v3.xml:372(para) -msgid "Domain name. Globally unique across all domains." -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-v3.xml:378(para) -msgid "Role name. Globally unique across all domains." -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-v3.xml:384(para) -msgid "User name. Unique within the owning domain." -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-v3.xml:390(para) -msgid "Project name. Unique within the owning domain." -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-v3.xml:396(para) -msgid "Group name. Unique within the owning domain." -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-v3.xml:420(title) -msgid "Domain configuration (domains, config) (since v3.4) (EXPERIMENTAL)" -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-v3.xml:421(para) -msgid "You can manage domain-specific configuration options." -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-v3.xml:424(para) -msgid "Domain-specific configuration options are structured within their group objects. The API supports only the identity and ldap groups. These groups override the default configuration settings for the storage of users and groups by the Identity server." -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-v3.xml:431(para) -msgid "You can create, update, and delete domain-specific configuration options by using the HTTP , , and methods. When updating, it is only necessary to include those options that are being updated." -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-v3.xml:437(para) -msgid "To create an option, use the method. The Identity API does not return options that are considered sensitive, although you can create and update these options. The only option currently considered sensitive is the password option within the ldap group." -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-v3.xml:444(para) -msgid "The API enables you to include sensitive options as part of non- sensitive options. For example, you can include the password as part of the url option." -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-v3.xml:449(para) -msgid "If you try to create or update configuration options for groups other than the identity or ldap groups, the Forbidden (403) response code is returned." -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-v3.xml:455(para) -msgid "For information about how to integrate the Identity service with LDAP, see Integrate Identity with LDAP." -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-v3.xml:470(title) -msgid "Groups (groups, users)" -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-v3.xml:471(para) -msgid "A group is a collection of users. Each group is owned by a domain." -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-v3.xml:474(para) -msgid "When you grant a role to a group, you explicitly associate that group with a project or domain. This action is equivalent to granting the role to each group member on that project and domain." -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-v3.xml:479(para) -msgid "When you grant a role to a group, that role is automatically granted to any user that you add to the group. When you revoke a role from a group, that role is automatically revoked from any user that you remove from the group. Any token that authenticates that user, project, and domain is revoked." -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-v3.xml:486(para) -msgid "As with users, a group without any role grants is useless from the perspective an OpenStack service and has no access to resources. However, a group without role grants is permitted as a way of acquiring or loading users and groups from external sources before mapping them to projects and domains." -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-v3.xml:504(title) -msgid "Policies (policies)" -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-v3.xml:505(para) -msgid "A policy is an arbitrarily serialized policy engine rule set to be consumed by a remote service." -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-v3.xml:509(para) -msgid "You encode policy rule sets into a blob that remote services can consume. To do so, set type to application/json and specify policy rules as JSON strings in a blob. For example:" -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-v3.xml:538(title) -msgid "Projects (projects, users, groups, roles)" -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-v3.xml:539(para) -msgid "A project is the base unit of ownership. Resources are owned by a specific project. A project is owned by a specific domain." -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-v3.xml:543(para) -msgid "(Since v3.4) You can create a hierarchy of projects by setting a parent ID when you create projects. All projects in a hierarchy must be owned by the same domain." -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-v3.xml:548(para) -msgid "(Since v3.6) Optionally, you can create a project that behaves both as a project and a domain. As a domain, the project provides a name space in which you can create users, groups, and other projects. If you create a project that behaves as a domain, you cannot update this project to behave like a regular project." -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-v3.xml:575(title) -msgid "Regions (regions) (since v3.2)" -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-v3.xml:576(para) -msgid "A region is a general division of an OpenStack deployment. You can associate zero or more sub-regions with a region to create a tree-like structured hierarchy." -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-v3.xml:581(para) -msgid "Although a region does not have a geographical connotation, a deployment can use a geographical name for a region, such as us-east." -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-v3.xml:586(para) -msgid "You can list, create, update, show details for, and delete regions." -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-v3.xml:600(title) -msgid "Roles (roles)" -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-v3.xml:601(para) -msgid "Roles grant a user a set of permitted actions for either a specific project or an entire domain." -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-v3.xml:605(para) -msgid "You can grant roles to a user on a project, including projects owned by other domains." -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-v3.xml:609(para) -msgid "You can create, list, and delete roles. You can also list roles assigned to a specified domain, project, or user." -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-v3.xml:613(para) -msgid "You can list role assignments and, since v3.6, all role assignments within a tree of projects. Use the query parameters to filter the list because the role assignments list can be long. Some typical examples are:" -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-v3.xml:621(para) -msgid "List role assignments for the specified user:" -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-v3.xml:629(para) -msgid "List role assignments for the specified project:" -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-v3.xml:637(para) -msgid "List all role assignments for a specified project and its sub- projects:" -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-v3.xml:643(para) -msgid "If you specify include_subtree=true, you must also specify the scope.project.id. Otherwise, this call returns the Bad Request (400) response code." -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-v3.xml:651(para) -msgid "Each role assignment entity in the collection contains a link to the assignment that created the entity." -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-v3.xml:655(para) -msgid "Use the effective query parameter to list effective assignments at the user, project, and domain level. This parameter allows for the effects of group membership. The group role assignment entities themselves are not returned in the collection. This represents the effective role assignments that would be included in a scoped token." -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-v3.xml:663(para) -msgid "In the response, the links entity section for entities for group members also contains a URL that enables access to the membership of the group." -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-v3.xml:668(para) -msgid "You can use the other query parameters with the effective parameter, such as:" -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-v3.xml:674(para) -msgid "Determine what a user can actually do:" -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-v3.xml:682(para) -msgid "Get the equivalent set of role assignments that are included in a project-scoped token response:" -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-v3.xml:746(title) -msgid "Service catalog and endpoints (services, endpoints)" -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-v3.xml:747(para) -msgid "A service is an OpenStack web service that you can access through a URL, or endpoint." -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-v3.xml:751(para) -msgid "A service catalog lists the services that are available to the caller based upon the current authorization." -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-v3.xml:755(para) -msgid "You can create, list, show details for, update, and delete services. When you create or update a service, you can enable the service, which causes it and its endpoints to appear in the service catalog." -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-v3.xml:761(para) -msgid "You can create, list, show details for, update, and delete endpoints." -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-v3.xml:775(title) -msgid "Users (users, groups, projects, roles)" -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-v3.xml:776(para) -msgid "A user is an individual API consumer that is owned by a domain. A role explicitly associates a user with projects or domains. A user with no assigned roles has no access to OpenStack resources." -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-v3.xml:781(para) -msgid "You can list, create, show details for, update, delete, and change the password for users." -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-v3.xml:784(para) -msgid "You can also list groups, projects, and roles for a specified user. To list user roles, see Roles." -msgstr "" - -#: ./api-ref/src/docbkx/api-ref.xml:11(title) -msgid "OpenStack API Reference" -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-v2.xml:10(title) ./api-ref/src/docbkx/itemizedlist-service-list.xml:55(link) -msgid "Identity API v2.0 (SUPPORTED)" -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-v2.xml:11(para) -msgid "Gets an authentication token that permits access to the OpenStack services REST API." -msgstr "" - -#: ./api-ref/src/docbkx/ch_identity-v2.xml:36(title) -msgid "Tokens and tenants" -msgstr "" - -#: ./api-ref/src/docbkx/api-ref-clustering-v1.xml:11(title) -msgid "OpenStack Clustering API v1 (CURRENT)" -msgstr "" - -#: ./api-ref/src/docbkx/api-ref-clustering-v1.xml:13(year) -msgid "2015-2016" -msgstr "" - -#: ./api-ref/src/docbkx/api-ref-objectstorage-v1.xml:11(title) -msgid "OpenStack Object Storage API v1 (SUPPORTED)" -msgstr "" - -#: ./api-ref/src/docbkx/ch_images-v1.xml:10(title) ./api-ref/src/docbkx/itemizedlist-service-list.xml:75(link) -msgid "Image service API v1 (SUPPORTED)" -msgstr "" - -#: ./api-ref/src/docbkx/ch_images-v1.xml:11(para) -msgid "Loads images for use at launch time by the Compute API. Also, assigns metadata to images." -msgstr "" - -#: ./api-ref/src/docbkx/ch_images-v1.xml:13(para) -msgid "Some cloud implementations do not expose this API and offer pretested images only." -msgstr "" - -#: ./api-ref/src/docbkx/ch_images-v1.xml:40(title) ./api-ref/src/docbkx/ch_compute-v2.1.xml:460(title) -msgid "Images" -msgstr "" - -#: ./api-ref/src/docbkx/ch_images-v1.xml:58(title) -msgid "Members" -msgstr "" - -#: ./api-ref/src/docbkx/ch_images-v1.xml:70(title) -msgid "Shared images" -msgstr "" - -#: ./api-ref/src/docbkx/api-ref-image-v1.xml:11(title) -msgid "OpenStack Image Service API v1 (SUPPORTED)" -msgstr "" - -#: ./api-ref/src/docbkx/api-ref-compute-v2.1.xml:11(title) -msgid "OpenStack Compute API (CURRENT)" -msgstr "" - -#: ./api-ref/src/docbkx/itemizedlist-service-list.xml:10(link) ./api-ref/src/docbkx/ch_baremetal-api-v1.xml:10(title) -msgid "Bare Metal API v1 (CURRENT)" -msgstr "" - -#: ./api-ref/src/docbkx/itemizedlist-service-list.xml:15(link) ./api-ref/src/docbkx/ch_blockstorage-api-v2.xml:10(title) -msgid "Block Storage API v2 (CURRENT)" -msgstr "" - -#: ./api-ref/src/docbkx/itemizedlist-service-list.xml:25(link) ./api-ref/src/docbkx/ch_clustering-v1.xml:10(title) -msgid "Clustering API v1 (CURRENT)" -msgstr "" - -#: ./api-ref/src/docbkx/itemizedlist-service-list.xml:30(link) ./api-ref/src/docbkx/ch_compute-v2.1.xml:15(title) -msgid "Compute API (CURRENT)" -msgstr "" - -#: ./api-ref/src/docbkx/itemizedlist-service-list.xml:35(link) -msgid "Data Processing v1.1 (CURRENT)" -msgstr "" - -#: ./api-ref/src/docbkx/itemizedlist-service-list.xml:60(link) -msgid "Identity admin API v2.0 (SUPPORTED)" -msgstr "" - -#: ./api-ref/src/docbkx/itemizedlist-service-list.xml:85(link) ./api-ref/src/docbkx/ch_networking-v2-ext.xml:14(title) -msgid "Networking API v2.0 extensions (CURRENT)" -msgstr "" - -#: ./api-ref/src/docbkx/itemizedlist-service-list.xml:95(link) ./api-ref/src/docbkx/ch_orchestration-v1.xml:10(title) -msgid "Orchestration API v1 (CURRENT)" -msgstr "" - -#: ./api-ref/src/docbkx/itemizedlist-service-list.xml:100(link) ./api-ref/src/docbkx/ch_share-v2.xml:15(title) -msgid "Shared File Systems API v2 (CURRENT)" -msgstr "" - -#: ./api-ref/src/docbkx/itemizedlist-service-list.xml:105(link) ./api-ref/src/docbkx/ch_share-v1.xml:14(title) -msgid "Shared File Systems API v1 (SUPPORTED)" -msgstr "" - -#: ./api-ref/src/docbkx/api-ref-identity-v3-ext.xml:11(title) -msgid "OpenStack Identity API v3 extensions (CURRENT)" -msgstr "" - -#: ./api-ref/src/docbkx/api-ref-image-v2.xml:11(title) -msgid "OpenStack Image service API v2 (CURRENT)" -msgstr "" - -#: ./api-ref/src/docbkx/api-ref-identity-v2-ext.xml:11(title) -msgid "OpenStack Identity API v2 extensions (DEPRECATED)" -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v2.xml:16(para) ./api-ref/src/docbkx/ch_share-v1.xml:15(para) -msgid "Provides coordinated access to shared or distributed file systems." -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v2.xml:19(para) -msgid "The Shared File Systems API uses Compute-style micro-versions. Use the HTTP X-Openstack-Manila-Api-Version request header to specify a valid micro-version. For example, \"X-Openstack-Manila-Api-Version: 2.15\". If you omit this header, the default micro-version is 2.0." -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v2.xml:25(para) -msgid "Other than the switch to the micro-versions approach, the Shared File Systems API v2.0 is functionally identical to the Shared File Systems API v1. " -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v2.xml:32(para) -msgid "Subsequent API v2 micro-versions, such as v2.1, differ from API v1. Look for notes that identify in which post-v2 micro-version a feature, method, or parameter was introduced." -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v2.xml:37(para) -msgid "Latest micro-version for Liberty release of Manila is 2.6" -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v2.xml:40(para) -msgid "Latest micro-version for Mitaka release of Manila is 2.15" -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v2.xml:44(link) -msgid "History of all Manila API changes." -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v2.xml:50(para) -msgid "Lists information for all Shared File Systems API versions." -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v2.xml:61(title) -msgid "API extensions" -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v2.xml:62(para) -msgid "Lists available Shared File Systems API extensions." -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v2.xml:72(title) -msgid "Limits" -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v2.xml:73(para) -msgid "Limits are the resource limitations that are allowed for each tenant (project). An administrator can configure limits in the manila.conf file." -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v2.xml:78(para) -msgid "Users can query their rate and absolute limits. The absolute limits contain information about:" -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v2.xml:84(para) -msgid "Total maximum share memory, in GBs." -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v2.xml:87(para) -msgid "Number of share-networks." -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v2.xml:90(para) -msgid "Number of share-snapshots." -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v2.xml:93(para) -msgid "Number of shares." -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v2.xml:96(para) -msgid "Shares and total used memory, in GBs." -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v2.xml:99(para) -msgid "Snapshots and total used memory, in GBs." -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v2.xml:102(para) -msgid "Rate limits control the frequency at which users can issue specific API requests. Administrators use rate limiting to configure limits on the type and number of API calls that can be made in a specific time interval. For example, a rate limit can control the number of requests that can be processed during a one-minute period." -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v2.xml:117(title) -msgid "Shares" -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v2.xml:118(para) -msgid "A share is a remote, mountable file system. You can mount a share to and access a share from several hosts by several users at a time." -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v2.xml:123(para) -msgid "You can create a share and associate it with a network, list shares, and show information for, update, and delete a share." -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v2.xml:127(para) -msgid "To create a share, specify one of these supported protocols:" -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v2.xml:132(para) -msgid "NFS. Network File System (NFS)." -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v2.xml:137(para) -msgid "CIFS. Common Internet File System (CIFS)." -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v2.xml:142(para) -msgid "GLUSTERFS. Gluster file system (GlusterFS)." -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v2.xml:147(para) -msgid "HDFS. Hadoop Distributed File System (HDFS)." -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v2.xml:152(para) -msgid "CEPHFS. Ceph File System (CephFS)." -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v2.xml:157(para) -msgid "You can also create snapshots of shares. To create a snapshot, you specify the ID of the share that you want to snapshot." -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v2.xml:161(para) -msgid "A share has one of these status values:" -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v2.xml:165(caption) -msgid "Share statuses" -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v2.xml:177(code) ./api-ref/src/docbkx/ch_share-v2.xml:449(code) ./api-ref/src/docbkx/ch_share-v2.xml:503(code) ./api-ref/src/docbkx/ch_share-v2.xml:766(code) ./api-ref/src/docbkx/ch_blockstorage-api-v2.xml:74(para) ./api-ref/src/docbkx/ch_blockstorage-api-v2.xml:223(para) ./api-ref/src/docbkx/ch_blockstorage-api-v2.xml:435(para) -msgid "creating" -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v2.xml:180(para) -msgid "The share is being created." -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v2.xml:185(code) ./api-ref/src/docbkx/ch_share-v2.xml:452(code) ./api-ref/src/docbkx/ch_share-v2.xml:506(code) ./api-ref/src/docbkx/ch_share-v2.xml:757(code) ./api-ref/src/docbkx/ch_blockstorage-api-v2.xml:93(para) ./api-ref/src/docbkx/ch_blockstorage-api-v2.xml:247(para) ./api-ref/src/docbkx/ch_blockstorage-api-v2.xml:459(para) -msgid "deleting" -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v2.xml:188(para) -msgid "The share is being deleted." -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v2.xml:193(code) ./api-ref/src/docbkx/ch_share-v2.xml:446(code) ./api-ref/src/docbkx/ch_share-v2.xml:500(code) ./api-ref/src/docbkx/ch_share-v2.xml:748(code) ./api-ref/src/docbkx/ch_blockstorage-api-v2.xml:97(para) ./api-ref/src/docbkx/ch_blockstorage-api-v2.xml:259(para) ./api-ref/src/docbkx/ch_blockstorage-api-v2.xml:471(para) -msgid "error" -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v2.xml:196(para) -msgid "An error occurred during share creation." -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v2.xml:203(code) ./api-ref/src/docbkx/ch_share-v2.xml:455(code) ./api-ref/src/docbkx/ch_share-v2.xml:509(code) ./api-ref/src/docbkx/ch_blockstorage-api-v2.xml:103(para) ./api-ref/src/docbkx/ch_blockstorage-api-v2.xml:483(para) -msgid "error_deleting" -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v2.xml:206(para) -msgid "An error occurred during share deletion." -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v2.xml:213(code) ./api-ref/src/docbkx/ch_share-v2.xml:443(code) ./api-ref/src/docbkx/ch_share-v2.xml:497(code) ./api-ref/src/docbkx/ch_blockstorage-api-v2.xml:78(para) ./api-ref/src/docbkx/ch_blockstorage-api-v2.xml:235(para) ./api-ref/src/docbkx/ch_blockstorage-api-v2.xml:447(para) -msgid "available" -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v2.xml:216(para) -msgid "The share is ready to use." -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v2.xml:221(code) ./api-ref/src/docbkx/ch_share-v2.xml:512(code) -msgid "manage_starting" -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v2.xml:224(para) -msgid "Share manage started." -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v2.xml:229(code) ./api-ref/src/docbkx/ch_share-v2.xml:515(code) -msgid "manage_error" -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v2.xml:232(para) -msgid "Share manage failed." -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v2.xml:237(code) ./api-ref/src/docbkx/ch_share-v2.xml:518(code) -msgid "unmanage_starting" -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v2.xml:240(para) -msgid "Share unmanage started." -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v2.xml:245(code) ./api-ref/src/docbkx/ch_share-v2.xml:521(code) -msgid "unmanage_error" -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v2.xml:248(para) -msgid "Share cannot be unmanaged." -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v2.xml:253(code) -msgid "unmanaged" -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v2.xml:256(para) -msgid "Share was unmanaged." -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v2.xml:261(code) -msgid "extending" -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v2.xml:264(para) -msgid "The extend, or increase, share size request was issued successfully." -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v2.xml:272(code) -msgid "extending_error" -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v2.xml:275(para) -msgid "Extend share failed." -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v2.xml:280(code) -msgid "shrinking" -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v2.xml:283(para) -msgid "Share is being shrunk." -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v2.xml:288(code) -msgid "shrinking_error" -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v2.xml:291(para) -msgid "Failed to update quota on share shrinking." -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v2.xml:296(code) -msgid "shrinking_possible_data_loss_error" -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v2.xml:299(para) -msgid "Shrink share failed due to possible data loss." -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v2.xml:316(para) -msgid "Configures Shared File Systems to manage a share. This API is available for micro-versions later than or equal to 2.7" -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v2.xml:331(title) -msgid "Share export locations (since API v2.9)" -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v2.xml:332(para) -msgid "Set of APIs used for viewing export locations of shares." -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v2.xml:335(para) ./api-ref/src/docbkx/ch_share-v2.xml:813(para) -msgid "By default, these APIs are admin-only. Use the policy.json file to grant permissions for these actions to other roles." -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v2.xml:344(para) -msgid "Lists all export locations for a share." -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v2.xml:353(para) -msgid "Show details of an export location belonging to a share." -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v2.xml:362(title) -msgid "Share metadata" -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v2.xml:363(para) -msgid "Shows, sets, updates, and unsets share metadata." -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v2.xml:378(title) -msgid "Share actions" -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v2.xml:379(para) -msgid "Grants or revokes share access, lists the permissions for a share, and explicitly updates the state of a share." -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v2.xml:383(para) -msgid "To grant or revoke share access, specify one of these supported share access levels:" -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v2.xml:389(para) -msgid "rw. Read and write (RW) access." -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v2.xml:394(para) -msgid "ro. Read-only (RO) access." -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v2.xml:399(para) -msgid "You must also specify one of these supported authentication methods:" -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v2.xml:405(para) -msgid "ip. Authenticates an instance through its IP address. A valid format is XX.XX.XX.XX or XX.XX.XX.XX/XX. For example 0.0.0.0/0." -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v2.xml:412(para) -msgid "cert. Authenticates an instance through a TLS certificate. Specify the TLS identity as the IDENTKEY. A valid value is any string up to 64 characters long in the common name (CN) of the certificate. The meaning of a string depends on its interpretation." -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v2.xml:421(para) -msgid "user. Authenticates by a user or group name. A valid value is an alphanumeric string that can contain some special characters and is from 4 to 32 characters long." -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v2.xml:428(para) -msgid "To verify that the access rules (ACL) were configured correctly for a share, you list permissions for a share." -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v2.xml:432(para) -msgid "As administrator, you can reset the state of a share and force-delete a share in any state. Use the policy.json file to grant permissions for this action to other roles." -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v2.xml:438(para) -msgid "You can set the state of a share to one of these supported states:" -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v2.xml:459(para) -msgid "If micro-version 1.0-2.6 is used then all share actions, defined below, should include prefix os- in top element of request JSON's body." -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v2.xml:464(para) -msgid "For example: {\"access_list\": null} is valid for v2.7+. And {\"os-access_list\": null} is valid for v1.0-2.6" -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v2.xml:483(title) -msgid "Share snapshots" -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v2.xml:484(para) -msgid "Use the shared file service to make snapshots of shares. A share snapshot is a point-in-time, read-only copy of the data that is contained in a share. You can create, manage, update, and delete share snapshots. After you create or manage a share snapshot, you can create a share from it." -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v2.xml:491(para) -msgid "You can update a share snapshot to rename it, change its description, or update its state to one of these supported states:" -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v2.xml:524(para) -msgid "As administrator, you can also reset the state of a snapshot and force-delete a share snapshot in any state. Use the policy.json file to grant permissions for these actions to other roles." -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v2.xml:554(title) -msgid "Share networks" -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v2.xml:555(para) -msgid "A share network stores network information that share servers can use where shares are hosted. You can associate a share with a single share network. When you create a share, you can optionally specify the ID of a share network through which instances can access the share." -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v2.xml:562(para) -msgid "You can create, update, view, and delete a share network." -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v2.xml:565(para) -msgid "When you create a share network, you can specify only one type of network:" -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v2.xml:570(para) -msgid "Neutron network. Specify a network ID and subnet ID." -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v2.xml:574(para) -msgid "Nova network. Specify a network ID." -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v2.xml:578(para) -msgid "For more information about supported plug-ins for share networks, see Manila Network Plugins." -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v2.xml:584(para) -msgid "A share network has these attributes:" -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v2.xml:589(para) -msgid "The IP block in Classless Inter-Domain Routing (CIDR) notation from which to allocate the network." -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v2.xml:595(para) -msgid "The IP version of the network." -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v2.xml:600(para) -msgid "The network type, which is vlan, vxlan, gre, or flat." -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v2.xml:607(para) -msgid "If the network uses segmentation, a segmentation identifier. For example, VLAN, VXLAN, and GRE networks use segmentation." -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v2.xml:634(title) -msgid "Security services" -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v2.xml:635(para) -msgid "You can create, update, view, and delete a security service. A security service stores configuration information for clients for authentication and authorization (AuthN/AuthZ). For example, a share server will be the client for an existing service such as LDAP, Kerberos, or Microsoft Active Directory." -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v2.xml:642(para) -msgid "You can associate a share with from one to three security service types:" -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v2.xml:648(para) -msgid "ldap. LDAP." -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v2.xml:652(para) -msgid "kerberos. Kerberos." -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v2.xml:657(para) -msgid "active_directory. Microsoft Active Directory." -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v2.xml:662(para) -msgid "You can configure a security service with these options:" -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v2.xml:667(para) -msgid "A DNS IP address." -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v2.xml:670(para) -msgid "An IP address or host name." -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v2.xml:673(para) -msgid "A domain." -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v2.xml:676(para) -msgid "A user or group name." -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v2.xml:680(para) -msgid "The password for the user, if you specify a user name." -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v2.xml:699(title) -msgid "Share servers" -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v2.xml:700(para) -msgid "A share server is created by multi-tenant back-end drivers where shares are hosted. For example, with the generic driver, shares are hosted on Compute VMs. With the cluster_mode driver from NetApp, shares are hosted on virtual storage servers, also known as Vservers or SVMs." -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v2.xml:707(para) -msgid "Administrators can perform read and delete actions for share servers. An administrator can delete an active share server only if it contains no dependent shares. If an administrator deletes the share server, the Shared File Systems service creates a share server in response to a subsequent create share request." -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v2.xml:714(para) -msgid "An administrator can use the policy.json file to grant permissions for share server actions to other roles." -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v2.xml:718(para) -msgid "The status of a share server indicates its current state. After you successfully set up a share server, its status is active. If errors occur during set up such as when server data is not valid, its status is error." -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v2.xml:724(para) -msgid "The possible share servers statuses are:" -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v2.xml:728(caption) -msgid "Share server statuses" -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v2.xml:743(para) -msgid "Share server was successfully set up." -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v2.xml:751(para) -msgid "The set up or deletion of the share server failed." -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v2.xml:760(para) -msgid "The share server has no dependent shares and is being deleted." -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v2.xml:769(para) -msgid "The share server is being created on the back end with data from the database." -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v2.xml:788(title) -msgid "Share instances (since API v2.3)" -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v2.xml:789(para) -msgid "Administrators can list, show information for, explicitly set the state of, and force-delete share instances. Use the policy.json file to grant permissions for these actions to other roles." -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v2.xml:809(title) -msgid "Share instance export locations (since API v2.9)" -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v2.xml:810(para) -msgid "Set of APIs used to view export locations of share instances." -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v2.xml:822(para) -msgid "Lists all export locations for a share instance." -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v2.xml:831(para) -msgid "Show details of an export location belonging to a share instance." -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v2.xml:840(title) -msgid "Share types" -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v2.xml:841(para) -msgid "A share type enables you to filter or choose back ends before you create a share. A share type behaves in the same way as a Block Storage volume type behaves." -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v2.xml:846(para) -msgid "You set a share type to private or public and manage the access to the private share types." -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v2.xml:850(para) -msgid "When you issue a create a share type request, you can submit a request body with either a share_type or volume_type object. The use of the volume_type object is deprecated but supported. It is recommended that you use the share_type object when you create a share type." -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v2.xml:858(para) -msgid "No matter which object type you include in the request, the API creates both a volume_type object and a share_type object. Both objects have the same ID. When you issue a list share types request, the response shows both share_types and volume_types objects." -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v2.xml:865(para) -msgid "You can set share types as either public or private. By default a share type is created as publicly accessible. Set share_type_access:is_public ( os-share-type-access:is_public for micro-versions 1.0-2.6) to False to make the share type private." -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v2.xml:872(para) -msgid "You can manage the access to the private share types for the different projects. You can add access, remove access, and get information about access for a private share type." -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v2.xml:877(para) -msgid "Administrators can create share types with these extra specifications that are used to filter back ends:" -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v2.xml:883(para) -msgid "driver_handles_share_servers. Required. Defines the driver mode for share server, or storage, life cycle management. The Shared File Systems service creates a share server for the export of shares." -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v2.xml:888(para) -msgid "Set to True when the share driver manages, or handles, the share server life cycle." -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v2.xml:892(para) -msgid "Set to False when an administrator rather than a share driver manages the storage life cycle." -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v2.xml:898(para) -msgid "snapshot_support. Filters back ends by whether they do or do not support share snapshots." -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v2.xml:902(para) -msgid "Set to True to find back ends that support share snapshots." -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v2.xml:905(para) -msgid "Set to False to find back ends that do not support share snapshots." -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v2.xml:911(para) -msgid "Administrators can also set additional extra specifications for a share type for the following purposes:" -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v2.xml:917(para) -msgid "Filter back ends. Specify these unqualified extra specifications in this format: extra_spec=value. For example, netapp_raid_type=raid4." -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v2.xml:925(para) -msgid "Set data for the driver. Except for the special capabilities prefix, you specify these qualified extra specifications with its prefix followed by a colon: vendor:extra_spec=value. For example, netapp:thin_provisioned=true." -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v2.xml:934(para) -msgid "The scheduler uses the special capabilities prefix for filtering. The scheduler can only create a share on a back end that reports capabilities that match the unscoped extra-spec keys for the share type. For details, see Capabilities and Extra-Specs." -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v2.xml:941(para) -msgid "Each driver implementation determines which extra specification keys it uses. For details, see the documentation for the driver." -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v2.xml:945(para) -msgid "An administrator can use the policy.json file to grant permissions for share type creation with extra specifications to other roles." -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v2.xml:978(title) ./api-ref/src/docbkx/ch_blockstorage-api-v2.xml:531(title) -msgid "Back-end storage pools" -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v2.xml:979(para) -msgid "An administrator can list all back-end storage pools that are known to the scheduler service." -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v2.xml:993(title) -msgid "Services" -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v2.xml:994(para) -msgid "Lists services. Services include manila-share and manila-scheduler and their binaries, hosts, availability zones, current statuses, and states (up or down)." -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v2.xml:1000(para) -msgid "Administrators can also enable or disable a service." -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v2.xml:1004(para) -msgid "For old microversions 1.0-2.6 replace URL part services with os-services." -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v2.xml:1022(title) -msgid "Availability zones" -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v2.xml:1023(para) -msgid "Describes availability zones." -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v2.xml:1027(para) -msgid "For old microversions 1.0-2.6 replace URL part availability-zones with os-availability-zone." -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v2.xml:1039(title) -msgid "Manage share" -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v2.xml:1040(para) -msgid "Configures Shared File Systems to manage or unmanage a share." -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v2.xml:1043(para) -msgid "The share unmanage operation is not supported for shares that are created on top of share servers (created with share networks)." -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v2.xml:1047(para) -msgid "You can unmanage a share that has no dependent snapshots." -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v2.xml:1050(para) -msgid "These APIs are available for micro-versions 1.0-2.6" -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v2.xml:1053(para) -msgid "Starting with micro-version 2.7 these APIs are available under 'shares' API group." -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v2.xml:1060(para) -msgid "Configures Shared File Systems to manage a share." -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v2.xml:1072(title) -msgid "Quota sets" -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v2.xml:1073(para) -msgid "Provides quotas management support." -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v2.xml:1077(para) -msgid "For old microversions 1.0-2.6 replace URL part quota-sets with os-quota-sets." -msgstr "" - -#: ./api-ref/src/docbkx/ch_baremetal-api-v1.xml:11(para) -msgid "Manages chassis, drivers, links, nodes, and ports for use with the Bare Metal API, also known as ironic services." -msgstr "" - -#: ./api-ref/src/docbkx/ch_baremetal-api-v1.xml:15(para) -msgid "Each Bare Metal API response returns the X-OpenStack-Ironic-API-Minimum-Version and X-OpenStack-Ironic-API-Maximum-Version headers, which indicate, respectively, the minimum and maximum supported API versions that the server supports." -msgstr "" - -#: ./api-ref/src/docbkx/ch_baremetal-api-v1.xml:22(para) -msgid "The client can use the X-OpenStack-Ironic-API-Version request header to request an API version. If the client does not request an API version, the default is API v1.1, which is the minimum supported version. The client has access to the features that the requested API version supports. OpenStack recommends that clients always request a specific version of API. However, you can request the latest value, which always requests the most current, supported API version." -msgstr "" - -#: ./api-ref/src/docbkx/ch_baremetal-api-v1.xml:51(title) -msgid "Chassis (chassis)" -msgstr "" - -#: ./api-ref/src/docbkx/ch_baremetal-api-v1.xml:52(para) -msgid "Chassis operations." -msgstr "" - -#: ./api-ref/src/docbkx/ch_baremetal-api-v1.xml:71(title) -msgid "Drivers (drivers)" -msgstr "" - -#: ./api-ref/src/docbkx/ch_baremetal-api-v1.xml:91(title) -msgid "Nodes (nodes)" -msgstr "" - -#: ./api-ref/src/docbkx/ch_baremetal-api-v1.xml:108(title) -msgid "Ports (ports)" -msgstr "" - -#: ./api-ref/src/docbkx/ch_compute-v2.1.xml:16(para) -msgid "This documentation supports the API v2.1 base version. If you enable all extensions, the Compute API v1.1 and v2.0 requests and responses match the API v2.1 requests and responses." -msgstr "" - -#: ./api-ref/src/docbkx/ch_compute-v2.1.xml:21(para) -msgid "Each API version lists the extensions that it requires to make the full request and responses available. API v2.1 must enable all extensions all the time. It uses micro-version headers to expose any additional functionality." -msgstr "" - -#: ./api-ref/src/docbkx/ch_compute-v2.1.xml:28(para) -msgid "Effective in the OpenStack Kilo release, the Compute API no longer supports XML in requests and responses." -msgstr "" - -#: ./api-ref/src/docbkx/ch_compute-v2.1.xml:33(para) -msgid "For details about the Compute API, see the Compute API." -msgstr "" - -#: ./api-ref/src/docbkx/ch_compute-v2.1.xml:40(para) -msgid "Lists information for all API versions." -msgstr "" - -#: ./api-ref/src/docbkx/ch_compute-v2.1.xml:59(title) -msgid "Servers (servers)" -msgstr "" - -#: ./api-ref/src/docbkx/ch_compute-v2.1.xml:60(para) -msgid "Lists, creates, shows details for, updates, and deletes servers." -msgstr "" - -#: ./api-ref/src/docbkx/ch_compute-v2.1.xml:61(emphasis) -msgid "Passwords" -msgstr "" - -#: ./api-ref/src/docbkx/ch_compute-v2.1.xml:62(para) -msgid "When you create a server, you can specify a password through the optional adminPass attribute. The password must meet the complexity requirements set by your OpenStack Compute provider. The server might enter an ERROR state if the complexity requirements are not met. In this case, a client might issue a change password action to reset the server password." -msgstr "" - -#: ./api-ref/src/docbkx/ch_compute-v2.1.xml:70(para) -msgid "If you do not specify a password, the API generates and assigns a random password that it returns in the response object. This password meets the security requirements set by the compute provider. For security reasons, subsequent calls do not require this password." -msgstr "" - -#: ./api-ref/src/docbkx/ch_compute-v2.1.xml:76(emphasis) -msgid "Server metadata" -msgstr "" - -#: ./api-ref/src/docbkx/ch_compute-v2.1.xml:77(para) -msgid "You can specify custom server metadata at server launch time. The maximum size for each metadata key-value pair is 255 bytes. The compute provider determines the maximum number of key-value pairs for each server. You can query this value through the maxServerMeta absolute limit." -msgstr "" - -#: ./api-ref/src/docbkx/ch_compute-v2.1.xml:84(emphasis) -msgid "Server networks" -msgstr "" - -#: ./api-ref/src/docbkx/ch_compute-v2.1.xml:85(para) -msgid "You can specify one or more networks to which the server connects at launch time. Users can also specify a specific port on the network or the fixed IP address to assign to the server interface." -msgstr "" - -#: ./api-ref/src/docbkx/ch_compute-v2.1.xml:91(para) -msgid "You can use both IPv4 and IPv6 addresses as access addresses and you can assign both addresses simultaneously. You can update access addresses after you create a server." -msgstr "" - -#: ./api-ref/src/docbkx/ch_compute-v2.1.xml:97(emphasis) -msgid "Server personality" -msgstr "" - -#: ./api-ref/src/docbkx/ch_compute-v2.1.xml:98(para) -msgid "To customize the personality of a server instance, you can inject data into its file system. For example, you might insert ssh keys, set configuration files, or store data that you want to retrieve from inside the instance. This customization method provides minimal launch-time personalization. If you require significant customization, create a custom image." -msgstr "" - -#: ./api-ref/src/docbkx/ch_compute-v2.1.xml:107(para) -msgid "Follow these guidelines when you inject files:" -msgstr "" - -#: ./api-ref/src/docbkx/ch_compute-v2.1.xml:112(para) -msgid "The maximum size of the file path data is 255 bytes." -msgstr "" - -#: ./api-ref/src/docbkx/ch_compute-v2.1.xml:117(para) -msgid "Encode the file contents as a Base64 string. The compute provider determines the maximum size of the file contents. The image that you use to create the server determines this value." -msgstr "" - -#: ./api-ref/src/docbkx/ch_compute-v2.1.xml:123(para) -msgid "The maximum limit refers to the number of bytes in the decoded data and not to the number of characters in the encoded data." -msgstr "" - -#: ./api-ref/src/docbkx/ch_compute-v2.1.xml:130(para) -msgid "The maxPersonality absolute limit defines the maximum number of file path and content pairs that you can supply. The compute provider determines this value." -msgstr "" - -#: ./api-ref/src/docbkx/ch_compute-v2.1.xml:138(para) -msgid "The maxPersonalitySize absolute limit is a byte limit that applies to all images in the deployment. Providers can set additional per-image personality limits." -msgstr "" - -#: ./api-ref/src/docbkx/ch_compute-v2.1.xml:145(para) -msgid "The file injection might not occur until after the server builds and boots." -msgstr "" - -#: ./api-ref/src/docbkx/ch_compute-v2.1.xml:149(para) -msgid "After file injection, only system administrators can access personality files. For example, on Linux, all files have root as the owner and the root group as the group owner, and allow only user and group read access (chmod 440)." -msgstr "" - -#: ./api-ref/src/docbkx/ch_compute-v2.1.xml:155(emphasis) -msgid "Server access addresses" -msgstr "" - -#: ./api-ref/src/docbkx/ch_compute-v2.1.xml:156(para) -msgid "In a hybrid environment, the underlying implementation might not control the IP address of a server. Instead, the access IP address might be part of the dedicated hardware; for example, a router/NAT device. In this case, you cannot use the addresses that the implementation provides to access the server from outside the local LAN. Instead, the API might assign a separate access address at creation time to provide access to the server. This address might not be directly bound to a network interface on the server and might not necessarily appear when you query the server addresses. However, clients should use an access address to access the server directly." -msgstr "" - -#: ./api-ref/src/docbkx/ch_compute-v2.1.xml:173(title) -msgid "Servers multiple create (servers)" -msgstr "" - -#: ./api-ref/src/docbkx/ch_compute-v2.1.xml:174(para) -msgid "Creates one or more servers." -msgstr "" - -#: ./api-ref/src/docbkx/ch_compute-v2.1.xml:177(para) -msgid "Optionally, you can set \"return_reservation_id\": \"True\" in the request body to request that a reservation ID be returned instead of the newly created instance information. With this parameter, the response shows only the reservation ID." -msgstr "" - -#: ./api-ref/src/docbkx/ch_compute-v2.1.xml:188(title) -msgid "Servers - run an action (servers, action)" -msgstr "" - -#: ./api-ref/src/docbkx/ch_compute-v2.1.xml:189(para) -msgid "Enables all users to performs an action on a server. Specify the action in the request body." -msgstr "" - -#: ./api-ref/src/docbkx/ch_compute-v2.1.xml:193(para) -msgid "You can associate a fixed or floating IP address with a server instance, or disassociate a fixed or floating IP address from a server instance. You can attach a volume to a server." -msgstr "" - -#: ./api-ref/src/docbkx/ch_compute-v2.1.xml:198(para) -msgid "You can create an image from a server, evacuate a server from a failed host to a new host, and force-delete a server before deferred cleanup. You can lock, pause, reboot, rebuild, rescue, resize, resume, confirm the resize of, revert a pending resize for, shelve, shelf-offload, unshelve, start, stop, unlock, unpause, and unrescue a server. You can also change the password of the server and add a security group to or remove a security group from a server. You can also trigger a crash dump into a server since Mitaka release." -msgstr "" - -#: ./api-ref/src/docbkx/ch_compute-v2.1.xml:208(para) -msgid "You can get an RDP, serial, SPICE, or VNC console for a server." -msgstr "" - -#: ./api-ref/src/docbkx/ch_compute-v2.1.xml:285(title) -msgid "Servers - run an administrative action (servers, action)" -msgstr "" - -#: ./api-ref/src/docbkx/ch_compute-v2.1.xml:286(para) -msgid "Enables administrators to perform an action on a server. Specify the action in the request body." -msgstr "" - -#: ./api-ref/src/docbkx/ch_compute-v2.1.xml:290(para) -msgid "You can change the administrative password for, create a back up of, and inject network information into a server." -msgstr "" - -#: ./api-ref/src/docbkx/ch_compute-v2.1.xml:294(para) -msgid "You can migrate, live-migrate, reset networking on, and reset the state of a server." -msgstr "" - -#: ./api-ref/src/docbkx/ch_compute-v2.1.xml:303(title) -msgid "Servers diagnostics (servers, diagnostics)" -msgstr "" - -#: ./api-ref/src/docbkx/ch_compute-v2.1.xml:304(para) -msgid "Shows the usage data for a server." -msgstr "" - -#: ./api-ref/src/docbkx/ch_compute-v2.1.xml:312(title) -msgid "Servers IPs (servers, ips)" -msgstr "" - -#: ./api-ref/src/docbkx/ch_compute-v2.1.xml:313(para) -msgid "Lists the IP addresses for an instance and shows details for an IP address." -msgstr "" - -#: ./api-ref/src/docbkx/ch_compute-v2.1.xml:322(title) -msgid "Server metadata (servers, metadata)" -msgstr "" - -#: ./api-ref/src/docbkx/ch_compute-v2.1.xml:323(para) -msgid "Lists metadata, creates or replaces one or more metadata items, and updates one or more metadata items for a server." -msgstr "" - -#: ./api-ref/src/docbkx/ch_compute-v2.1.xml:327(para) -msgid "Shows details for, creates or replaces, and updates a metadata item, by key, for a server." -msgstr "" - -#: ./api-ref/src/docbkx/ch_compute-v2.1.xml:336(title) -msgid "Servers - list actions (servers, os-instance-actions)" -msgstr "" - -#: ./api-ref/src/docbkx/ch_compute-v2.1.xml:337(para) -msgid "All users can list available actions for a server." -msgstr "" - -#: ./api-ref/src/docbkx/ch_compute-v2.1.xml:340(para) -msgid "All users can show details for a server action; however, only administrators can view server events in server action details." -msgstr "" - -#: ./api-ref/src/docbkx/ch_compute-v2.1.xml:349(title) -msgid "Port interfaces (servers, os-interface)" -msgstr "" - -#: ./api-ref/src/docbkx/ch_compute-v2.1.xml:350(para) -msgid "Creates a port interface and uses it to attach a port to a server and detaches a port interface from a server. Also, lists all port interfaces and shows details for a port interface." -msgstr "" - -#: ./api-ref/src/docbkx/ch_compute-v2.1.xml:360(title) -msgid "Servers password (servers, os-server-password)" -msgstr "" - -#: ./api-ref/src/docbkx/ch_compute-v2.1.xml:361(para) -msgid "Shows the encrypted administrative password. Also, clears the encrypted administrative password for a server, which removes it from the metadata server." -msgstr "" - -#: ./api-ref/src/docbkx/ch_compute-v2.1.xml:371(title) -msgid "Servers virtual interfaces (servers, os-virtual-interfaces)" -msgstr "" - -#: ./api-ref/src/docbkx/ch_compute-v2.1.xml:372(para) -msgid "Lists virtual interfaces for a server instance." -msgstr "" - -#: ./api-ref/src/docbkx/ch_compute-v2.1.xml:380(title) -msgid "Servers with volume attachments (servers, os-volume_attachments)" -msgstr "" - -#: ./api-ref/src/docbkx/ch_compute-v2.1.xml:381(para) -msgid "Attaches volumes that are created through the volume API to server instances. Also, lists volume attachments for a server instance, shows details for a volume attachment, and detaches a volume." -msgstr "" - -#: ./api-ref/src/docbkx/ch_compute-v2.1.xml:391(title) -msgid "Flavors with extended attributes (flavors)" -msgstr "" - -#: ./api-ref/src/docbkx/ch_compute-v2.1.xml:392(para) -msgid "Shows information about flavors." -msgstr "" - -#: ./api-ref/src/docbkx/ch_compute-v2.1.xml:400(title) -msgid "Flavors access (flavors, os-flavor-access, action)" -msgstr "" - -#: ./api-ref/src/docbkx/ch_compute-v2.1.xml:401(para) -msgid "Lists tenants who have access to a private flavor and adds private flavor access to and removes private flavor access from tenants. By default, only administrators can manage private flavor access. A private flavor has is_public set to false while a public flavor has is_public set to true." -msgstr "" - -#: ./api-ref/src/docbkx/ch_compute-v2.1.xml:419(title) -msgid "Flavors extra-specs (flavors, os-flavor-extra-specs)" -msgstr "" - -#: ./api-ref/src/docbkx/ch_compute-v2.1.xml:420(para) -msgid "Lists, creates, deletes, and updates the extra-specs or keys for a flavor." -msgstr "" - -#: ./api-ref/src/docbkx/ch_compute-v2.1.xml:429(title) -msgid "Keypairs (keypairs)" -msgstr "" - -#: ./api-ref/src/docbkx/ch_compute-v2.1.xml:430(para) -msgid "Generates, imports, and deletes SSH keys." -msgstr "" - -#: ./api-ref/src/docbkx/ch_compute-v2.1.xml:436(title) ./api-ref/src/docbkx/ch_blockstorage-api-v2.xml:35(title) -msgid "Limits (limits)" -msgstr "" - -#: ./api-ref/src/docbkx/ch_compute-v2.1.xml:437(para) -msgid "Shows rate and absolute limits for the tenant." -msgstr "" - -#: ./api-ref/src/docbkx/ch_compute-v2.1.xml:445(title) -msgid "Extensions (extensions)" -msgstr "" - -#: ./api-ref/src/docbkx/ch_compute-v2.1.xml:446(para) -msgid "Lists available extensions and shows information for an extension, by alias." -msgstr "" - -#: ./api-ref/src/docbkx/ch_compute-v2.1.xml:450(para) -msgid "OpenStack Compute API v2.0 supports extensions. However, extensions are deprecated in Compute API v2.1. For information about extensions, see Extensions." -msgstr "" - -#: ./api-ref/src/docbkx/ch_compute-v2.1.xml:461(para) -msgid "Lists, shows details for, and deletes images. Also sets, lists, shows details for, and deletes image metadata." -msgstr "" - -#: ./api-ref/src/docbkx/ch_compute-v2.1.xml:465(para) -msgid "An image is a collection of files that you use to create and rebuild a server. By default, operators provide pre-built operating system images. You can also create custom images. See Compute server actions." -msgstr "" - -#: ./api-ref/src/docbkx/ch_compute-v2.1.xml:471(para) -msgid "By default, the policy.json file authorizes all users to view the image size in the OS-EXT-IMG-SIZE:size extended attribute." -msgstr "" - -#: ./api-ref/src/docbkx/ch_compute-v2.1.xml:490(title) -msgid "Image metadata" -msgstr "" - -#: ./api-ref/src/docbkx/ch_compute-v2.1.xml:491(para) -msgid "Shows details for, sets, updates, and deletes image metadata or metadata items." -msgstr "" - -#: ./api-ref/src/docbkx/ch_compute-v2.1.xml:510(title) -msgid "Guest agents (os-agents)" -msgstr "" - -#: ./api-ref/src/docbkx/ch_compute-v2.1.xml:511(para) -msgid "Creates, lists, updates, and deletes guest agent builds. Use guest agents to access files on the disk, configure networking, or run other applications or scripts in the guest while the agent runs. This hypervisor-specific extension is not currently enabled for KVM. Use of guest agents is possible only if the underlying service provider uses the Xen driver." -msgstr "" - -#: ./api-ref/src/docbkx/ch_compute-v2.1.xml:524(title) -msgid "Host aggregates (os-aggregates, action)" -msgstr "" - -#: ./api-ref/src/docbkx/ch_compute-v2.1.xml:525(para) -msgid "Creates and manages host aggregates. An aggregate assigns metadata to groups of compute nodes. Aggregates are only visible to the cloud provider." -msgstr "" - -#: ./api-ref/src/docbkx/ch_compute-v2.1.xml:535(title) -msgid "Assisted volume snapshots (os-assisted-volume-snapshots)" -msgstr "" - -#: ./api-ref/src/docbkx/ch_compute-v2.1.xml:536(para) -msgid "Creates and deletes snapshots through an emulator/hypervisor. The qcow2 file format is supported." -msgstr "" - -#: ./api-ref/src/docbkx/ch_compute-v2.1.xml:540(para) -msgid "An internal snapshot that lacks storage such as NFS or GlusterFS can use an emulator/hypervisor to add the snapshot feature." -msgstr "" - -#: ./api-ref/src/docbkx/ch_compute-v2.1.xml:549(title) -msgid "Availability zones (os-availability-zone)" -msgstr "" - -#: ./api-ref/src/docbkx/ch_compute-v2.1.xml:550(para) -msgid "Shows availability zone information." -msgstr "" - -#: ./api-ref/src/docbkx/ch_compute-v2.1.xml:558(title) -msgid "Bare metal nodes (os-baremetal-nodes)" -msgstr "" - -#: ./api-ref/src/docbkx/ch_compute-v2.1.xml:559(para) -msgid "Bare metal nodes." -msgstr "" - -#: ./api-ref/src/docbkx/ch_compute-v2.1.xml:565(title) -msgid "Cells (os-cells, capacities)" -msgstr "" - -#: ./api-ref/src/docbkx/ch_compute-v2.1.xml:566(para) -msgid "Adds neighbor cells, lists neighbor cells, and shows the capabilities of the local cell." -msgstr "" - -#: ./api-ref/src/docbkx/ch_compute-v2.1.xml:575(title) -msgid "Root certificates (os-certificates)" -msgstr "" - -#: ./api-ref/src/docbkx/ch_compute-v2.1.xml:576(para) -msgid "Creates and shows details for a root certificate." -msgstr "" - -#: ./api-ref/src/docbkx/ch_compute-v2.1.xml:582(title) -msgid "Cloudpipe (os-cloudpipe)" -msgstr "" - -#: ./api-ref/src/docbkx/ch_compute-v2.1.xml:583(para) -msgid "Manages virtual VPNs for projects." -msgstr "" - -#: ./api-ref/src/docbkx/ch_compute-v2.1.xml:589(title) -msgid "Server consoles (servers, os-consoles, os-console-auth-token)" -msgstr "" - -#: ./api-ref/src/docbkx/ch_compute-v2.1.xml:590(para) -msgid "Manages server consoles." -msgstr "" - -#: ./api-ref/src/docbkx/ch_compute-v2.1.xml:596(title) -msgid "Fixed IPs (os-fixed-ips)" -msgstr "" - -#: ./api-ref/src/docbkx/ch_compute-v2.1.xml:597(para) -msgid "Shows data for a fixed IP, such as host name, CIDR, and address. Also, reserves and frees a fixed IP address." -msgstr "" - -#: ./api-ref/src/docbkx/ch_compute-v2.1.xml:606(title) -msgid "Floating IP DNS records (os-floating-ip-dns)" -msgstr "" - -#: ./api-ref/src/docbkx/ch_compute-v2.1.xml:607(para) -msgid "Manages DNS records associated with floating IP addresses. The API dispatches requests to a DNS driver that is selected at startup." -msgstr "" - -#: ./api-ref/src/docbkx/ch_compute-v2.1.xml:616(title) -msgid "Floating IP pools (os-floating-ip-pools)" -msgstr "" - -#: ./api-ref/src/docbkx/ch_compute-v2.1.xml:617(para) -msgid "Manages groups of floating IPs." -msgstr "" - -#: ./api-ref/src/docbkx/ch_compute-v2.1.xml:625(title) -msgid "Floating IPs (os-floating-ips)" -msgstr "" - -#: ./api-ref/src/docbkx/ch_compute-v2.1.xml:626(para) -msgid "Lists floating IP addresses for a project. Also, creates (allocates) a floating IP address for a project, shows floating IP address details, and deletes (deallocates) a floating IP address from a project." -msgstr "" - -#: ./api-ref/src/docbkx/ch_compute-v2.1.xml:631(para) -msgid "The cloud administrator configures a pool of floating IP addresses 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 for a project, you can:" -msgstr "" - -#: ./api-ref/src/docbkx/ch_compute-v2.1.xml:642(para) -msgid "Add (associate) the floating IP address with an instance in the project. You can associate only one floating IP address with an instance at a time." -msgstr "" - -#: ./api-ref/src/docbkx/ch_compute-v2.1.xml:651(para) -msgid "Remove (disassociate) the floating IP address from an instance in the project." -msgstr "" - -#: ./api-ref/src/docbkx/ch_compute-v2.1.xml:657(para) -msgid "Delete, or deallocate, a floating IP from the project, which automatically deletes any associations for that IP address." -msgstr "" - -#: ./api-ref/src/docbkx/ch_compute-v2.1.xml:668(title) -msgid "Floating IPs bulk (os-floating-ips-bulk)" -msgstr "" - -#: ./api-ref/src/docbkx/ch_compute-v2.1.xml:669(para) -msgid "(nova-network only) Bulk-creates, deletes, and lists floating IPs. Default pool name is nova." -msgstr "" - -#: ./api-ref/src/docbkx/ch_compute-v2.1.xml:673(para) -msgid "To view available pools, use the os-floating-ip-pools extension." -msgstr "" - -#: ./api-ref/src/docbkx/ch_compute-v2.1.xml:682(title) -msgid "Ping instances (os-fping)" -msgstr "" - -#: ./api-ref/src/docbkx/ch_compute-v2.1.xml:683(para) -msgid "Pings instances and reports which ones are alive." -msgstr "" - -#: ./api-ref/src/docbkx/ch_compute-v2.1.xml:691(title) -msgid "Hosts (os-hosts)" -msgstr "" - -#: ./api-ref/src/docbkx/ch_compute-v2.1.xml:692(para) -msgid "Manages physical hosts. Some virt drivers don not support all host functions. For more information, see nova virt support matrix" -msgstr "" - -#: ./api-ref/src/docbkx/ch_compute-v2.1.xml:703(title) -msgid "Hypervisors (os-hypervisors)" -msgstr "" - -#: ./api-ref/src/docbkx/ch_compute-v2.1.xml:704(para) -msgid "Lists all hypervisors, shows summary statistics for all hypervisors over all compute nodes, shows details for a hypervisor, and shows the uptime for a hypervisor." -msgstr "" - -#: ./api-ref/src/docbkx/ch_compute-v2.1.xml:714(title) -msgid "Instance usage audit log (os-instance-usage-audit-log)" -msgstr "" - -#: ./api-ref/src/docbkx/ch_compute-v2.1.xml:715(para) -msgid "Administrator only. Monitors task logs." -msgstr "" - -#: ./api-ref/src/docbkx/ch_compute-v2.1.xml:723(title) -msgid "Migrations (os-migrations)" -msgstr "" - -#: ./api-ref/src/docbkx/ch_compute-v2.1.xml:724(para) -msgid "Shows data on migrations." -msgstr "" - -#: ./api-ref/src/docbkx/ch_compute-v2.1.xml:732(title) -msgid "Networks (os-networks)" -msgstr "" - -#: ./api-ref/src/docbkx/ch_compute-v2.1.xml:733(para) -msgid "Creates, lists, shows information for, and deletes networks." -msgstr "" - -#: ./api-ref/src/docbkx/ch_compute-v2.1.xml:736(para) -msgid "Adds network to a project, disassociates a network from a project, and disassociates a project from a network." -msgstr "" - -#: ./api-ref/src/docbkx/ch_compute-v2.1.xml:740(para) -msgid "Associates host with and disassociates host from a network." -msgstr "" - -#: ./api-ref/src/docbkx/ch_compute-v2.1.xml:748(title) -msgid "Quota class (os-quota-class-sets)" -msgstr "" - -#: ./api-ref/src/docbkx/ch_compute-v2.1.xml:749(para) -msgid "Provides quota classes management support." -msgstr "" - -#: ./api-ref/src/docbkx/ch_compute-v2.1.xml:756(title) -msgid "Quota sets (os-quota-sets)" -msgstr "" - -#: ./api-ref/src/docbkx/ch_compute-v2.1.xml:757(para) -msgid "Permits administrators, depending on policy settings, to view default quotas, view details for quotas, revert quotas to defaults, and update the quotas for a project or a project and user." -msgstr "" - -#: ./api-ref/src/docbkx/ch_compute-v2.1.xml:776(title) -msgid "Security groups (os-security-groups)" -msgstr "" - -#: ./api-ref/src/docbkx/ch_compute-v2.1.xml:777(para) -msgid "Lists, shows information for, creates, and deletes security groups." -msgstr "" - -#: ./api-ref/src/docbkx/ch_compute-v2.1.xml:785(title) -msgid "Rules for default security group (os-security-group-default-rules)" -msgstr "" - -#: ./api-ref/src/docbkx/ch_compute-v2.1.xml:787(para) -msgid "Lists, shows information for, and creates default security group rules." -msgstr "" - -#: ./api-ref/src/docbkx/ch_compute-v2.1.xml:796(title) -msgid "Rules for security group (os-security-group-rules)" -msgstr "" - -#: ./api-ref/src/docbkx/ch_compute-v2.1.xml:797(para) -msgid "Creates and deletes security group rules." -msgstr "" - -#: ./api-ref/src/docbkx/ch_compute-v2.1.xml:805(title) -msgid "Create external events (os-server-external-events)" -msgstr "" - -#: ./api-ref/src/docbkx/ch_compute-v2.1.xml:806(para) -msgid "Creates one or more external events. The API dispatches each event to a server instance." -msgstr "" - -#: ./api-ref/src/docbkx/ch_compute-v2.1.xml:815(title) -msgid "Server groups (os-server-groups)" -msgstr "" - -#: ./api-ref/src/docbkx/ch_compute-v2.1.xml:816(para) -msgid "Lists, shows information for, creates, and deletes server groups." -msgstr "" - -#: ./api-ref/src/docbkx/ch_compute-v2.1.xml:833(title) -msgid "Compute services (os-services)" -msgstr "" - -#: ./api-ref/src/docbkx/ch_compute-v2.1.xml:834(para) -msgid "Lists all running Compute services for a tenant, enables or disables scheduling for a Compute service, logs disabled Compute service information, and deletes a Compute service." -msgstr "" - -#: ./api-ref/src/docbkx/ch_compute-v2.1.xml:839(para) -msgid "For an overview of Compute services, see OpenStack Compute." -msgstr "" - -#: ./api-ref/src/docbkx/ch_compute-v2.1.xml:847(title) -msgid "Usage reports (os-simple-tenant-usage)" -msgstr "" - -#: ./api-ref/src/docbkx/ch_compute-v2.1.xml:848(para) -msgid "Reports usage statistics on compute and storage resources." -msgstr "" - -#: ./api-ref/src/docbkx/ch_compute-v2.1.xml:856(title) -msgid "Project networks (os-tenant-networks)" -msgstr "" - -#: ./api-ref/src/docbkx/ch_compute-v2.1.xml:857(para) -msgid "Creates, lists, shows information for, and deletes project networks." -msgstr "" - -#: ./api-ref/src/docbkx/ch_compute-v2.1.xml:865(title) -msgid "Volume extension (os-volumes, os-snapshots)" -msgstr "" - -#: ./api-ref/src/docbkx/ch_compute-v2.1.xml:866(para) -msgid "Manages volumes and snapshots for use with the Compute API." -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v2-experimental.xml:15(title) -msgid "Shared File Systems API v2 (EXPERIMENTAL)" -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v2-experimental.xml:16(para) -msgid "Contributors can change or remove the experimental part of the Shared File Systems API without maintaining backward compatibility." -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v2-experimental.xml:21(title) -msgid "Experimental share actions" -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v2-experimental.xml:29(title) -msgid "Consistency groups (since API v2.4)" -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v2-experimental.xml:30(para) -msgid "Consistency groups enable you to create snapshots at the exact same point in time from multiple file system shares. For example, a database might place its tables, logs, and configuration on separate shares. To restore this database from a previous point in time, it makes sense to restore the logs, tables, and configuration together from the exact same point in time." -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v2-experimental.xml:38(para) -msgid "As an administrator, you can also reset the state of a consistency group and force-delete a consistency group in any state. Use the policy.json file to grant permissions for these actions to other roles." -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v2-experimental.xml:64(title) -msgid "Consistency group snapshots (since API v2.4)" -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v2-experimental.xml:65(para) -msgid "You can create snapshots of consistency groups. To create a snapshot, you specify the ID of the consistency group that you want to snapshot. After you create a consistency group snapshot, you can create a consistency group from it." -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v2-experimental.xml:71(para) -msgid "A consistency group snapshot can have member shares. To add a member share, include the consistency_group_id parameter in the create share request. This ID must match the ID of the consistency group from which the consistency group snapshot was created. Then, when you use consistency group snapshots to restore data, you can easily determine which shares belong to a consistency group." -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v2-experimental.xml:80(para) -msgid "As an administrator, you can also reset the state of a consistency group snapshot and force-delete a consistency group snapshot in any state. Use the policy.json file to grant permissions for these actions to other roles." -msgstr "" - -#: ./api-ref/src/docbkx/ch_data-processing-v1.1.xml:10(title) -msgid "Data Processing API v1.1 (CURRENT)" -msgstr "" - -#: ./api-ref/src/docbkx/ch_data-processing-v1.1.xml:11(para) -msgid "Produce data processing operations." -msgstr "" - -#: ./api-ref/src/docbkx/ch_data-processing-v1.1.xml:13(title) -msgid "Plugins" -msgstr "" - -#: ./api-ref/src/docbkx/ch_data-processing-v1.1.xml:14(para) -msgid "A plugin object defines the Hadoop or Spark version that it can install and which configurations can be set for the cluster." -msgstr "" - -#: ./api-ref/src/docbkx/ch_data-processing-v1.1.xml:22(title) -msgid "Image registry" -msgstr "" - -#: ./api-ref/src/docbkx/ch_data-processing-v1.1.xml:23(para) -msgid "Use the image registry tool to manage images, add tags to and remove tags from images, and define the user name for an instance operating system. Each plugin lists required tags for an image. To run remote operations, the Data Processing service requires a user name with which to log in to the operating system for an instance." -msgstr "" - -#: ./api-ref/src/docbkx/ch_data-processing-v1.1.xml:34(title) -msgid "Node group templates" -msgstr "" - -#: ./api-ref/src/docbkx/ch_data-processing-v1.1.xml:35(para) -msgid "A cluster is a group of nodes with the same configuration. A node group template configures a node in the cluster." -msgstr "" - -#: ./api-ref/src/docbkx/ch_data-processing-v1.1.xml:39(para) -msgid "A template configures Hadoop processes and VM characteristics, such as the number of reduced slots for task tracker, the number of CPUs, and the amount of RAM. The template specifies the VM characteristics through an OpenStack flavor." -msgstr "" - -#: ./api-ref/src/docbkx/ch_data-processing-v1.1.xml:49(title) -msgid "Cluster templates" -msgstr "" - -#: ./api-ref/src/docbkx/ch_data-processing-v1.1.xml:50(para) -msgid "A cluster template configures a Hadoop cluster. A cluster template lists node groups with the number of instances in each group. You can also define cluster-scoped configurations in a cluster template." -msgstr "" - -#: ./api-ref/src/docbkx/ch_data-processing-v1.1.xml:60(title) ./api-ref/src/docbkx/ch_clustering-v1.xml:54(title) -msgid "Clusters" -msgstr "" - -#: ./api-ref/src/docbkx/ch_data-processing-v1.1.xml:61(para) -msgid "A cluster is a group of nodes with the same configuration." -msgstr "" - -#: ./api-ref/src/docbkx/ch_data-processing-v1.1.xml:68(title) -msgid "Event log" -msgstr "" - -#: ./api-ref/src/docbkx/ch_data-processing-v1.1.xml:69(para) -msgid "The event log feature provides information about cluster provisioning. In the event of errors, the event log shows the reason for the failure." -msgstr "" - -#: ./api-ref/src/docbkx/ch_data-processing-v1.1.xml:77(title) -msgid "Data sources" -msgstr "" - -#: ./api-ref/src/docbkx/ch_data-processing-v1.1.xml:78(para) -msgid "A data source object defines the location of input or output for MapReduce jobs and might reference different types of storage." -msgstr "" - -#: ./api-ref/src/docbkx/ch_data-processing-v1.1.xml:82(para) -msgid "The Data Processing service does not validate data source locations." -msgstr "" - -#: ./api-ref/src/docbkx/ch_data-processing-v1.1.xml:90(title) -msgid "Job binary internals" -msgstr "" - -#: ./api-ref/src/docbkx/ch_data-processing-v1.1.xml:91(para) -msgid "Job binary internal objects represent data processing applications and libraries that are stored in the internal database." -msgstr "" - -#: ./api-ref/src/docbkx/ch_data-processing-v1.1.xml:99(title) -msgid "Job binaries" -msgstr "" - -#: ./api-ref/src/docbkx/ch_data-processing-v1.1.xml:100(para) -msgid "Job binary objects represent data processing applications and libraries that are stored in either the internal database or the Object Storage service." -msgstr "" - -#: ./api-ref/src/docbkx/ch_data-processing-v1.1.xml:109(title) -msgid "Jobs" -msgstr "" - -#: ./api-ref/src/docbkx/ch_data-processing-v1.1.xml:110(para) -msgid "A job object lists the binaries that a job needs to run. To run a job, you must specify data sources and job parameters." -msgstr "" - -#: ./api-ref/src/docbkx/ch_data-processing-v1.1.xml:114(para) -msgid "You can run a job on an existing or new transient cluster." -msgstr "" - -#: ./api-ref/src/docbkx/ch_data-processing-v1.1.xml:121(title) -msgid "Job executions" -msgstr "" - -#: ./api-ref/src/docbkx/ch_data-processing-v1.1.xml:122(para) -msgid "A job execution object represents a Hadoop job that runs on a cluster. A job execution polls the status of a running job and reports it to the user. Also a user can cancel a running job." -msgstr "" - -#: ./api-ref/src/docbkx/ch_data-processing-v1.1.xml:131(title) -msgid "Job types" -msgstr "" - -#: ./api-ref/src/docbkx/ch_data-processing-v1.1.xml:132(para) -msgid "Each plugin that supports EDP also supports specific job types. Different versions of a plugin might actually support different job types. Configuration options vary by plugin, version, and job type." -msgstr "" - -#: ./api-ref/src/docbkx/ch_data-processing-v1.1.xml:138(para) -msgid "The job types provide information about which plugins support which job types and how to configure the job types." -msgstr "" - -#: ./api-ref/src/docbkx/api-ref-networking-v2.xml:11(title) -msgid "OpenStack Networking API v2.0 (CURRENT)" -msgstr "" - -#: ./api-ref/src/docbkx/ch_orchestration-v1.xml:11(para) -msgid "Uses a template language to orchestrate OpenStack services." -msgstr "" - -#: ./api-ref/src/docbkx/ch_orchestration-v1.xml:14(title) -msgid "General API information" -msgstr "" - -#: ./api-ref/src/docbkx/ch_orchestration-v1.xml:15(para) -msgid "Authenticated calls that target a known URI but that use an HTTP method that the implementation does not support return a 405 Method Not Allowed error code. In addition, the HTTP OPTIONS method is supported for each known URI. In both cases, the Allow response header indicates the HTTP methods that are supported for the resource." -msgstr "" - -#: ./api-ref/src/docbkx/ch_orchestration-v1.xml:32(title) -msgid "Stacks" -msgstr "" - -#: ./api-ref/src/docbkx/ch_orchestration-v1.xml:91(title) -msgid "Stack actions" -msgstr "" - -#: ./api-ref/src/docbkx/ch_orchestration-v1.xml:92(para) -msgid "Performs non-lifecycle operations on the stack. Specify the action in the request body." -msgstr "" - -#: ./api-ref/src/docbkx/ch_orchestration-v1.xml:105(title) -msgid "Stack resources" -msgstr "" - -#: ./api-ref/src/docbkx/ch_orchestration-v1.xml:126(title) -msgid "Stack events" -msgstr "" - -#: ./api-ref/src/docbkx/ch_orchestration-v1.xml:148(title) -msgid "Templates" -msgstr "" - -#: ./api-ref/src/docbkx/ch_orchestration-v1.xml:177(title) -msgid "Build info" -msgstr "" - -#: ./api-ref/src/docbkx/ch_orchestration-v1.xml:186(title) -msgid "Software configuration" -msgstr "" - -#: ./api-ref/src/docbkx/ch_orchestration-v1.xml:215(title) -msgid "Manage service" -msgstr "" - -#: ./api-ref/src/docbkx/ch_clustering-v1.xml:11(para) -msgid "Clustering service for OpenStack." -msgstr "" - -#: ./api-ref/src/docbkx/ch_clustering-v1.xml:12(para) -msgid "For more information, see Senlin." -msgstr "" - -#: ./api-ref/src/docbkx/ch_clustering-v1.xml:18(para) -msgid "Lists information for all Clustering API versions." -msgstr "" - -#: ./api-ref/src/docbkx/ch_clustering-v1.xml:28(title) -msgid "Actions" -msgstr "" - -#: ./api-ref/src/docbkx/ch_clustering-v1.xml:29(para) -msgid "Lists all actions and shows details for an action." -msgstr "" - -#: ./api-ref/src/docbkx/ch_clustering-v1.xml:42(title) -msgid "Build information" -msgstr "" - -#: ./api-ref/src/docbkx/ch_clustering-v1.xml:43(para) -msgid "Shows build information for a Senlin deployment." -msgstr "" - -#: ./api-ref/src/docbkx/ch_clustering-v1.xml:55(para) -msgid "Lists all clusters and creates, shows information for, updates, deletes, and triggers an action on a cluster." -msgstr "" - -#: ./api-ref/src/docbkx/ch_clustering-v1.xml:75(title) -msgid "Cluster policies" -msgstr "" - -#: ./api-ref/src/docbkx/ch_clustering-v1.xml:76(para) -msgid "Lists all cluster policies and shows information for a cluster policy." -msgstr "" - -#: ./api-ref/src/docbkx/ch_clustering-v1.xml:91(para) -msgid "Lists all events and shows information for an event." -msgstr "" - -#: ./api-ref/src/docbkx/ch_clustering-v1.xml:104(title) -msgid "Nodes" -msgstr "" - -#: ./api-ref/src/docbkx/ch_clustering-v1.xml:105(para) -msgid "Lists all nodes, and creates, shows information for, updates, deletes a node." -msgstr "" - -#: ./api-ref/src/docbkx/ch_clustering-v1.xml:126(para) -msgid "Lists all policies and creates, shows information for, updates, and deletes a policy." -msgstr "" - -#: ./api-ref/src/docbkx/ch_clustering-v1.xml:143(title) -msgid "Policy types" -msgstr "" - -#: ./api-ref/src/docbkx/ch_clustering-v1.xml:144(para) -msgid "Lists all policy types and shows details for a policy type." -msgstr "" - -#: ./api-ref/src/docbkx/ch_clustering-v1.xml:157(title) -msgid "Profiles" -msgstr "" - -#: ./api-ref/src/docbkx/ch_clustering-v1.xml:158(para) -msgid "Lists all profiles and creates, shows information for, updates, and deletes a profile." -msgstr "" - -#: ./api-ref/src/docbkx/ch_clustering-v1.xml:175(title) -msgid "Profile types" -msgstr "" - -#: ./api-ref/src/docbkx/ch_clustering-v1.xml:176(para) -msgid "Lists all profile types and shows details for a profile type." -msgstr "" - -#: ./api-ref/src/docbkx/ch_clustering-v1.xml:189(title) -msgid "Receivers" -msgstr "" - -#: ./api-ref/src/docbkx/ch_clustering-v1.xml:190(para) -msgid "Lists all receivers and creates, shows information for, and deletes a receiver." -msgstr "" - -#: ./api-ref/src/docbkx/ch_clustering-v1.xml:206(title) -msgid "Webhooks" -msgstr "" - -#: ./api-ref/src/docbkx/ch_clustering-v1.xml:207(para) -msgid "Triggers an action represented by a webhook." -msgstr "" - -#: ./api-ref/src/docbkx/api-ref-share-v1.xml:11(title) -msgid "OpenStack Shared File Systems API v1 (CURRENT)" -msgstr "" - -#: ./api-ref/src/docbkx/ch_networking-v2-ext.xml:17(para) -msgid "Lists available Networking API v2.0 extensions and shows details for an extension." -msgstr "" - -#: ./api-ref/src/docbkx/ch_networking-v2-ext.xml:32(title) -msgid "Networking Flavors Framework v2.0 (CURRENT) (flavor, service_profile)" -msgstr "" - -#: ./api-ref/src/docbkx/ch_networking-v2-ext.xml:33(para) -msgid "Extension that allows user selection of operator-curated flavors during resource creation." -msgstr "" - -#: ./api-ref/src/docbkx/ch_networking-v2-ext.xml:37(para) -msgid "Service q-flavors must be enabled in the configuration to use this feature." -msgstr "" - -#: ./api-ref/src/docbkx/ch_networking-v2-ext.xml:45(title) -msgid "FWaaS v2.0 (CURRENT) (fw, firewalls, firewall_policies, firewall_rules)" -msgstr "" - -#: ./api-ref/src/docbkx/ch_networking-v2-ext.xml:46(para) -msgid "Use the Firewall-as-a-Service (FWaaS) v2.0 extension to deploy firewalls to protect your networks." -msgstr "" - -#: ./api-ref/src/docbkx/ch_networking-v2-ext.xml:50(para) -msgid "The FWaaS extension enables you to:" -msgstr "" - -#: ./api-ref/src/docbkx/ch_networking-v2-ext.xml:55(para) -msgid "Apply firewall rules on traffic entering and leaving tenant networks." -msgstr "" - -#: ./api-ref/src/docbkx/ch_networking-v2-ext.xml:59(para) -msgid "Apply TCP, UDP, ICMP, or protocol-agnostic rules." -msgstr "" - -#: ./api-ref/src/docbkx/ch_networking-v2-ext.xml:64(para) -msgid "Create and share firewall policies that hold an ordered collection of the firewall rules." -msgstr "" - -#: ./api-ref/src/docbkx/ch_networking-v2-ext.xml:70(para) -msgid "Audit firewall rules and policies." -msgstr "" - -#: ./api-ref/src/docbkx/ch_networking-v2-ext.xml:73(para) ./api-ref/src/docbkx/ch_networking-v2-ext.xml:373(para) ./api-ref/src/docbkx/ch_networking-v2-ext.xml:492(para) -msgid "This extension introduces these resources:" -msgstr "" - -#: ./api-ref/src/docbkx/ch_networking-v2-ext.xml:76(para) -msgid "firewall. A logical firewall resource that a tenant can instantiate and manage. A firewall can have one firewall policy." -msgstr "" - -#: ./api-ref/src/docbkx/ch_networking-v2-ext.xml:83(para) -msgid "firewall_policy. An ordered collection of firewall rules. You can share a firewall policy across tenants. You can include a firewall policy as part of an audit workflow so that an authorized relevant entity can audit the firewall policy. This entity can differ from the tenant who created, or the tenants that use, the firewall policy." -msgstr "" - -#: ./api-ref/src/docbkx/ch_networking-v2-ext.xml:93(para) -msgid "firewall_rule. A collection of attributes, such as ports and IP addresses. These attributes define match criteria and an action to take, such as allow or deny, on matched data traffic." -msgstr "" - -#: ./api-ref/src/docbkx/ch_networking-v2-ext.xml:105(title) -msgid "LBaaS 2.0 (STABLE) (lbaas, loadbalancers, listeners, health_monitors, pools, members)" -msgstr "" - -#: ./api-ref/src/docbkx/ch_networking-v2-ext.xml:106(para) -msgid "The Load-Balancer-as-a-Service (LBaaS) version 2.0 extension pairs with the Networking 2.0 API to enable OpenStack tenants to manage load balancers for their VMs. With this extension you can load- balance client traffic from one network to application services, such as VMs, on the same network." -msgstr "" - -#: ./api-ref/src/docbkx/ch_networking-v2-ext.xml:113(para) -msgid "Use this extension to create and manage load balancers, listeners, pools, members of a pool, and health monitors and view status of a resource." -msgstr "" - -#: ./api-ref/src/docbkx/ch_networking-v2-ext.xml:118(caption) ./api-ref/src/docbkx/ch_networking-v2-ext.xml:177(caption) -msgid "Load balancer statuses" -msgstr "" - -#: ./api-ref/src/docbkx/ch_networking-v2-ext.xml:129(para) ./api-ref/src/docbkx/ch_networking-v2-ext.xml:188(para) -msgid "ACTIVE" -msgstr "" - -#: ./api-ref/src/docbkx/ch_networking-v2-ext.xml:130(para) ./api-ref/src/docbkx/ch_networking-v2-ext.xml:189(para) -msgid "The resource is ready and active." -msgstr "" - -#: ./api-ref/src/docbkx/ch_networking-v2-ext.xml:133(para) ./api-ref/src/docbkx/ch_networking-v2-ext.xml:192(para) -msgid "PENDING_CREATE" -msgstr "" - -#: ./api-ref/src/docbkx/ch_networking-v2-ext.xml:134(para) ./api-ref/src/docbkx/ch_networking-v2-ext.xml:193(para) -msgid "The resource is being created." -msgstr "" - -#: ./api-ref/src/docbkx/ch_networking-v2-ext.xml:137(para) ./api-ref/src/docbkx/ch_networking-v2-ext.xml:196(para) -msgid "PENDING_UPDATE" -msgstr "" - -#: ./api-ref/src/docbkx/ch_networking-v2-ext.xml:138(para) ./api-ref/src/docbkx/ch_networking-v2-ext.xml:197(para) -msgid "The resource is being updated." -msgstr "" - -#: ./api-ref/src/docbkx/ch_networking-v2-ext.xml:141(para) ./api-ref/src/docbkx/ch_networking-v2-ext.xml:200(para) -msgid "PENDING_DELETE" -msgstr "" - -#: ./api-ref/src/docbkx/ch_networking-v2-ext.xml:142(para) ./api-ref/src/docbkx/ch_networking-v2-ext.xml:201(para) -msgid "The resource is pending deletion." -msgstr "" - -#: ./api-ref/src/docbkx/ch_networking-v2-ext.xml:145(para) ./api-ref/src/docbkx/ch_networking-v2-ext.xml:204(para) -msgid "INACTIVE" -msgstr "" - -#: ./api-ref/src/docbkx/ch_networking-v2-ext.xml:146(para) ./api-ref/src/docbkx/ch_networking-v2-ext.xml:205(para) -msgid "The resource is not active." -msgstr "" - -#: ./api-ref/src/docbkx/ch_networking-v2-ext.xml:149(para) ./api-ref/src/docbkx/ch_networking-v2-ext.xml:208(para) -msgid "ERROR" -msgstr "" - -#: ./api-ref/src/docbkx/ch_networking-v2-ext.xml:150(para) ./api-ref/src/docbkx/ch_networking-v2-ext.xml:210(para) -msgid "An object within the service is not working. The error_details attribute provides an explanation for the error, its cause, and possibly a solution." -msgstr "" - -#: ./api-ref/src/docbkx/ch_networking-v2-ext.xml:164(title) -msgid "LBaaS 1.0 (DEPRECATED) (lb, vips, health_monitors, pools, members)" -msgstr "" - -#: ./api-ref/src/docbkx/ch_networking-v2-ext.xml:165(para) -msgid "The Load-Balancer-as-a-Service (LBaaS) v1.0 extension pairs with the Networking v2.0 API to enable OpenStack tenants to manage load balancers for their VMs. With this extension, you can load-balance client traffic from one network to application services, such as VMs, on the same network." -msgstr "" - -#: ./api-ref/src/docbkx/ch_networking-v2-ext.xml:172(para) -msgid "Use this extension to create and manage virtual IP addresses (VIPs), pools, members of a pool, health monitors, and view status of a resource." -msgstr "" - -#: ./api-ref/src/docbkx/ch_networking-v2-ext.xml:226(title) -msgid "Metering labels and rules (metering-labels, metering-label-rules)" -msgstr "" - -#: ./api-ref/src/docbkx/ch_networking-v2-ext.xml:227(para) -msgid "Creates, modifies, and deletes OpenStack Layer3 metering labels and rules." -msgstr "" - -#: ./api-ref/src/docbkx/ch_networking-v2-ext.xml:232(title) -msgid "Networks provider extended attributes (networks)" -msgstr "" - -#: ./api-ref/src/docbkx/ch_networking-v2-ext.xml:233(para) -msgid "Lists, creates, shows information for, updates, and deletes networks." -msgstr "" - -#: ./api-ref/src/docbkx/ch_networking-v2-ext.xml:236(para) -msgid "The provider extension decorates network resources with additional attributes. These attributes are provider:network_type, provider:physical_network, and provider:segmentation_id. The validation rules for these attributes are the same as for the Networks multiple provider extension. You cannot use both extensions at the same time." -msgstr "" - -#: ./api-ref/src/docbkx/ch_networking-v2-ext.xml:251(title) -msgid "Networks multiple provider extension (networks)" -msgstr "" - -#: ./api-ref/src/docbkx/ch_networking-v2-ext.xml:252(para) -msgid "Enables administrative users to define multiple physical bindings for an OpenStack Networking network and list or show details for networks with multiple physical bindings." -msgstr "" - -#: ./api-ref/src/docbkx/ch_networking-v2-ext.xml:257(para) -msgid "You cannot update any provider attributes. If you try to do so, an error occurs." -msgstr "" - -#: ./api-ref/src/docbkx/ch_networking-v2-ext.xml:261(para) -msgid "To delete a network with multiple physical bindings, issue a normal delete network request." -msgstr "" - -#: ./api-ref/src/docbkx/ch_networking-v2-ext.xml:265(para) -msgid "To define multiple physical bindings for a network, include a segments list in the request body of a POST /v2.0/networks request. Each element in the segments list has the same structure as the provider network attributes. These attributes are provider:network_type, provider:physical_network, and provider:segmentation_id. The validation rules for these attributes are the same as for the Networks provider extended attributes. You cannot use both extensions at the same time." -msgstr "" - -#: ./api-ref/src/docbkx/ch_networking-v2-ext.xml:279(para) -msgid "The NSX and ML2 plug-ins support this extension. With the ML2 plug-in, you can specify multiple VLANs for a network, a VXLAN tunnel ID, and a VLAN." -msgstr "" - -#: ./api-ref/src/docbkx/ch_networking-v2-ext.xml:288(title) -msgid "VLAN transparency extension (networks)" -msgstr "" - -#: ./api-ref/src/docbkx/ch_networking-v2-ext.xml:289(para) -msgid "Enables plug-ins that support VLAN transparency to deliver VLAN-transparent trunk networks. If the service does not support VLAN transparency and a user requests a VLAN-transparent network, the plug-in refuses to create one and returns an appropriate error to the user." -msgstr "" - -#: ./api-ref/src/docbkx/ch_networking-v2-ext.xml:296(para) -msgid "You cannot update the vlan-transparent attribute. If you try to do so, an error occurs." -msgstr "" - -#: ./api-ref/src/docbkx/ch_networking-v2-ext.xml:300(para) -msgid "To delete a VLAN-transparent network, issue a normal delete network request." -msgstr "" - -#: ./api-ref/src/docbkx/ch_networking-v2-ext.xml:304(para) -msgid "The ML2 plug-in currently supports this extension. With the ML2 plug-in, you can set the vlan-transparent attribute to either true or false." -msgstr "" - -#: ./api-ref/src/docbkx/ch_networking-v2-ext.xml:313(title) -msgid "Ports binding extended attributes (ports)" -msgstr "" - -#: ./api-ref/src/docbkx/ch_networking-v2-ext.xml:314(para) -msgid "Lists, creates, shows information for, updates, and deletes ports." -msgstr "" - -#: ./api-ref/src/docbkx/ch_networking-v2-ext.xml:330(title) -msgid "QoS policies (qos)" -msgstr "" - -#: ./api-ref/src/docbkx/ch_networking-v2-ext.xml:331(para) -msgid "Lists, creates, shows information for, and updates QoS policies." -msgstr "" - -#: ./api-ref/src/docbkx/ch_networking-v2-ext.xml:336(title) -msgid "Quotas extension (quotas)" -msgstr "" - -#: ./api-ref/src/docbkx/ch_networking-v2-ext.xml:337(para) -msgid "Lists quotas for tenants who have non-default quota values, and lists, updates, and resets quotas for a tenant." -msgstr "" - -#: ./api-ref/src/docbkx/ch_networking-v2-ext.xml:341(para) -msgid "A quota value of -1 means that quota has no limit." -msgstr "" - -#: ./api-ref/src/docbkx/ch_networking-v2-ext.xml:348(title) -msgid "Extra routes (routers)" -msgstr "" - -#: ./api-ref/src/docbkx/ch_networking-v2-ext.xml:349(para) -msgid "Adds extra routes to the router resource." -msgstr "" - -#: ./api-ref/src/docbkx/ch_networking-v2-ext.xml:351(para) -msgid "You can update a router to add a set of next hop IPs and destination CIDRs." -msgstr "" - -#: ./api-ref/src/docbkx/ch_networking-v2-ext.xml:354(para) -msgid "The next hop IP must be part of a subnet to which the router interfaces are connected. You can configure the routes attribute on only update operations." -msgstr "" - -#: ./api-ref/src/docbkx/ch_networking-v2-ext.xml:367(title) -msgid "Layer-3 networking (routers, floatingips)" -msgstr "" - -#: ./api-ref/src/docbkx/ch_networking-v2-ext.xml:368(para) -msgid "Routes packets between subnets, forwards packets from internal networks to external ones, and accesses instances from external networks through floating IPs." -msgstr "" - -#: ./api-ref/src/docbkx/ch_networking-v2-ext.xml:378(para) -msgid "router. A logical entity for forwarding packets across internal subnets and NATting them on external networks through an appropriate external gateway." -msgstr "" - -#: ./api-ref/src/docbkx/ch_networking-v2-ext.xml:385(para) -msgid "floatingip. An external IP address that you map to a port in an internal network." -msgstr "" - -#: ./api-ref/src/docbkx/ch_networking-v2-ext.xml:395(title) -msgid "Security groups (security-groups)" -msgstr "" - -#: ./api-ref/src/docbkx/ch_networking-v2-ext.xml:396(para) -msgid "Lists, creates, shows information for, updates, and deletes security groups." -msgstr "" - -#: ./api-ref/src/docbkx/ch_networking-v2-ext.xml:413(title) -msgid "Security group rules (security-group-rules)" -msgstr "" - -#: ./api-ref/src/docbkx/ch_networking-v2-ext.xml:414(para) -msgid "Lists, creates, shows information for, and deletes security group rules." -msgstr "" - -#: ./api-ref/src/docbkx/ch_networking-v2-ext.xml:432(title) -msgid "Subnet pools extension (subnetpools)" -msgstr "" - -#: ./api-ref/src/docbkx/ch_networking-v2-ext.xml:433(para) -msgid "Lists, creates, shows details for, updates, and deletes subnet pools." -msgstr "" - -#: ./api-ref/src/docbkx/ch_networking-v2-ext.xml:449(title) -msgid "Tag extension (tags)" -msgstr "" - -#: ./api-ref/src/docbkx/ch_networking-v2-ext.xml:450(para) -msgid "Shows details for, updates, and deletes tags. This extension is available since Mitaka release." -msgstr "" - -#: ./api-ref/src/docbkx/ch_networking-v2-ext.xml:458(title) -msgid "VPNaaS 2.0 (CURRENT) (vpn, vpnservices, ikepolicies, ipsecpolicies, endpoint-groups, ipsec-site-connections)" -msgstr "" - -#: ./api-ref/src/docbkx/ch_networking-v2-ext.xml:459(para) -msgid "The Virtual-Private-Network-as-a-Service (VPNaaS) extension enables OpenStack tenants to extend private networks across the public telecommunication infrastructure." -msgstr "" - -#: ./api-ref/src/docbkx/ch_networking-v2-ext.xml:464(para) -msgid "This initial implementation of the VPNaaS extension provides:" -msgstr "" - -#: ./api-ref/src/docbkx/ch_networking-v2-ext.xml:469(para) -msgid "Site-to-site VPN that connects two private networks." -msgstr "" - -#: ./api-ref/src/docbkx/ch_networking-v2-ext.xml:473(para) -msgid "Multiple VPN connections per tenant." -msgstr "" - -#: ./api-ref/src/docbkx/ch_networking-v2-ext.xml:476(para) -msgid "IKEv1 policy support with 3des, aes-128, aes-256, or aes-192 encryption." -msgstr "" - -#: ./api-ref/src/docbkx/ch_networking-v2-ext.xml:480(para) -msgid "IPSec policy support with 3des, aes-128, aes-192, or aes-256 encryption, sha1 authentication, ESP, AH, or AH-ESP transform protocol, and tunnel or transport mode encapsulation." -msgstr "" - -#: ./api-ref/src/docbkx/ch_networking-v2-ext.xml:488(para) -msgid "Dead Peer Detection (DPD) with hold, clear, restart, disabled, or restart-by-peer actions." -msgstr "" - -#: ./api-ref/src/docbkx/ch_networking-v2-ext.xml:495(para) -msgid "service. A parent object that associates VPN with a specific subnet and router." -msgstr "" - -#: ./api-ref/src/docbkx/ch_networking-v2-ext.xml:499(para) -msgid "ikepolicy. The Internet Key Exchange (IKE) policy that identifies the authentication and encryption algorithm to use during phase one and two negotiation of a VPN connection." -msgstr "" - -#: ./api-ref/src/docbkx/ch_networking-v2-ext.xml:506(para) -msgid "ipsecpolicy. The IP security policy that specifies the authentication and encryption algorithm and encapsulation mode to use for the established VPN connection." -msgstr "" - -#: ./api-ref/src/docbkx/ch_networking-v2-ext.xml:514(para) -msgid "ipsec-site-connection. Details for the site-to-site IPsec connection, including the peer CIDRs, MTU, authentication mode, peer address, DPD settings, and status." -msgstr "" - -#: ./api-ref/src/docbkx/ch_networking-v2-ext.xml:527(title) -msgid "Network IP availability and usage stats" -msgstr "" - -#: ./api-ref/src/docbkx/ch_networking-v2-ext.xml:528(para) -msgid "List and show the network IP usage stats of all networks and a specified network. These operations are available in the Mitaka release (April 2016)." -msgstr "" - -#: ./api-ref/src/docbkx/api-ref-blockstorage-v2.xml:11(title) -msgid "OpenStack Block Storage API v2 (CURRENT)" -msgstr "" - -#: ./api-ref/src/docbkx/ch_blockstorage-api-v2.xml:27(title) -msgid "API extensions (extensions)" -msgstr "" - -#: ./api-ref/src/docbkx/ch_blockstorage-api-v2.xml:36(para) -msgid "Shows absolute limits for a tenant." -msgstr "" - -#: ./api-ref/src/docbkx/ch_blockstorage-api-v2.xml:39(para) -msgid "An absolute limit value of -1 indicates that the absolute limit for the item is infinite." -msgstr "" - -#: ./api-ref/src/docbkx/ch_blockstorage-api-v2.xml:47(title) -msgid "Volumes (volumes)" -msgstr "" - -#: ./api-ref/src/docbkx/ch_blockstorage-api-v2.xml:48(para) -msgid "A volume is a detachable block storage device similar to a USB hard drive. You can attach a volume to one instance at a time." -msgstr "" - -#: ./api-ref/src/docbkx/ch_blockstorage-api-v2.xml:52(para) -msgid "The snapshot_id and source_volid parameters specify the ID of the snapshot or volume from which this volume originates. If the volume was not created from a snapshot or source volume, these values are null." -msgstr "" - -#: ./api-ref/src/docbkx/ch_blockstorage-api-v2.xml:58(para) -msgid "When you create, list, update, or delete volumes, the possible status values are:" -msgstr "" - -#: ./api-ref/src/docbkx/ch_blockstorage-api-v2.xml:63(caption) -msgid "Volume statuses" -msgstr "" - -#: ./api-ref/src/docbkx/ch_blockstorage-api-v2.xml:75(para) -msgid "The volume is being created." -msgstr "" - -#: ./api-ref/src/docbkx/ch_blockstorage-api-v2.xml:79(para) -msgid "The volume is ready to attach to an instance." -msgstr "" - -#: ./api-ref/src/docbkx/ch_blockstorage-api-v2.xml:83(para) -msgid "attaching" -msgstr "" - -#: ./api-ref/src/docbkx/ch_blockstorage-api-v2.xml:84(para) -msgid "The volume is attaching to an instance." -msgstr "" - -#: ./api-ref/src/docbkx/ch_blockstorage-api-v2.xml:88(para) -msgid "in-use" -msgstr "" - -#: ./api-ref/src/docbkx/ch_blockstorage-api-v2.xml:89(para) -msgid "The volume is attached to an instance." -msgstr "" - -#: ./api-ref/src/docbkx/ch_blockstorage-api-v2.xml:94(para) -msgid "The volume is being deleted." -msgstr "" - -#: ./api-ref/src/docbkx/ch_blockstorage-api-v2.xml:98(para) -msgid "A volume creation error occurred." -msgstr "" - -#: ./api-ref/src/docbkx/ch_blockstorage-api-v2.xml:104(para) -msgid "A volume deletion error occurred." -msgstr "" - -#: ./api-ref/src/docbkx/ch_blockstorage-api-v2.xml:108(para) -msgid "backing-up" -msgstr "" - -#: ./api-ref/src/docbkx/ch_blockstorage-api-v2.xml:109(para) -msgid "The volume is being backed up." -msgstr "" - -#: ./api-ref/src/docbkx/ch_blockstorage-api-v2.xml:112(para) -msgid "restoring-backup" -msgstr "" - -#: ./api-ref/src/docbkx/ch_blockstorage-api-v2.xml:113(para) -msgid "A backup is being restored to the volume." -msgstr "" - -#: ./api-ref/src/docbkx/ch_blockstorage-api-v2.xml:117(para) ./api-ref/src/docbkx/ch_blockstorage-api-v2.xml:283(para) -msgid "error_restoring" -msgstr "" - -#: ./api-ref/src/docbkx/ch_blockstorage-api-v2.xml:118(para) ./api-ref/src/docbkx/ch_blockstorage-api-v2.xml:288(para) -msgid "A backup restoration error occurred." -msgstr "" - -#: ./api-ref/src/docbkx/ch_blockstorage-api-v2.xml:121(para) -msgid "error_extending" -msgstr "" - -#: ./api-ref/src/docbkx/ch_blockstorage-api-v2.xml:122(para) -msgid "An error occurred while attempting to extend a volume." -msgstr "" - -#: ./api-ref/src/docbkx/ch_blockstorage-api-v2.xml:149(title) -msgid "Volume type access (volumes)" -msgstr "" - -#: ./api-ref/src/docbkx/ch_blockstorage-api-v2.xml:150(para) -msgid "Private volume type access to project." -msgstr "" - -#: ./api-ref/src/docbkx/ch_blockstorage-api-v2.xml:153(para) -msgid "By default, volumes types are public. To create a private volume type, set the is_public boolean field to false at volume type creation time. To control access to a private volume type, user needs to add a project to or remove a project from the volume type. Private volume types without projects are only accessible by users with the administrative role and context." -msgstr "" - -#: ./api-ref/src/docbkx/ch_blockstorage-api-v2.xml:173(title) -msgid "Volume actions (volumes, action)" -msgstr "" - -#: ./api-ref/src/docbkx/ch_blockstorage-api-v2.xml:174(para) -msgid "Extends the size of, resets statuses for, sets image metadata for, and removes image metadata from a volume. Attaches a volume to a server, detaches a volume from a server, and removes a volume from Block Storage management without actually removing the back-end storage object associated with it." -msgstr "" - -#: ./api-ref/src/docbkx/ch_blockstorage-api-v2.xml:196(title) -msgid "Backups (backups)" -msgstr "" - -#: ./api-ref/src/docbkx/ch_blockstorage-api-v2.xml:197(para) -msgid "A backup is a full copy of a volume stored in an external service. The service can be configured. The only supported service is Object Storage. A backup can subsequently be restored from the external service to either the same volume that the backup was originally taken from or to a new volume. Backup and restore operations can only be carried out on volumes that are in an unattached and available state." -msgstr "" - -#: ./api-ref/src/docbkx/ch_blockstorage-api-v2.xml:206(para) -msgid "When you create, list, or delete backups, these status values are possible:" -msgstr "" - -#: ./api-ref/src/docbkx/ch_blockstorage-api-v2.xml:211(caption) -msgid "Backup statuses" -msgstr "" - -#: ./api-ref/src/docbkx/ch_blockstorage-api-v2.xml:228(para) -msgid "The backup is being created." -msgstr "" - -#: ./api-ref/src/docbkx/ch_blockstorage-api-v2.xml:240(para) -msgid "The backup is ready to restore to a volume." -msgstr "" - -#: ./api-ref/src/docbkx/ch_blockstorage-api-v2.xml:252(para) -msgid "The backup is being deleted." -msgstr "" - -#: ./api-ref/src/docbkx/ch_blockstorage-api-v2.xml:264(para) -msgid "A backup error occurred." -msgstr "" - -#: ./api-ref/src/docbkx/ch_blockstorage-api-v2.xml:271(para) -msgid "restoring" -msgstr "" - -#: ./api-ref/src/docbkx/ch_blockstorage-api-v2.xml:276(para) -msgid "The backup is being restored to a volume." -msgstr "" - -#: ./api-ref/src/docbkx/ch_blockstorage-api-v2.xml:296(para) -msgid "If an error occurs, you can find more information about the error in the fail_reason field for the backup." -msgstr "" - -#: ./api-ref/src/docbkx/ch_blockstorage-api-v2.xml:318(title) -msgid "Backup actions (backups, action)" -msgstr "" - -#: ./api-ref/src/docbkx/ch_blockstorage-api-v2.xml:319(para) -msgid "Force-deletes a backup." -msgstr "" - -#: ./api-ref/src/docbkx/ch_blockstorage-api-v2.xml:329(title) -msgid "Capabilities for storage back ends (capabilities)" -msgstr "" - -#: ./api-ref/src/docbkx/ch_blockstorage-api-v2.xml:330(para) -msgid "Shows capabilities for a storage back end." -msgstr "" - -#: ./api-ref/src/docbkx/ch_blockstorage-api-v2.xml:367(title) -msgid "Quality of service (QoS) specifications (qos-specs)" -msgstr "" - -#: ./api-ref/src/docbkx/ch_blockstorage-api-v2.xml:371(para) -msgid "Creates, lists, shows details for, associates, disassociates, sets keys, unsets keys, and deletes quality of service (QoS) specifications." -msgstr "" - -#: ./api-ref/src/docbkx/ch_blockstorage-api-v2.xml:397(title) -msgid "Volume types (types)" -msgstr "" - -#: ./api-ref/src/docbkx/ch_blockstorage-api-v2.xml:413(title) -msgid "Volume snapshots (snapshots)" -msgstr "" - -#: ./api-ref/src/docbkx/ch_blockstorage-api-v2.xml:414(para) -msgid "A snapshot is a point-in-time copy of the data that a volume contains." -msgstr "" - -#: ./api-ref/src/docbkx/ch_blockstorage-api-v2.xml:418(para) -msgid "When you create, list, or delete snapshots, these status values are possible:" -msgstr "" - -#: ./api-ref/src/docbkx/ch_blockstorage-api-v2.xml:423(caption) -msgid "Snapshot statuses" -msgstr "" - -#: ./api-ref/src/docbkx/ch_blockstorage-api-v2.xml:440(para) -msgid "The snapshot is being created." -msgstr "" - -#: ./api-ref/src/docbkx/ch_blockstorage-api-v2.xml:452(para) -msgid "The snapshot is ready to use." -msgstr "" - -#: ./api-ref/src/docbkx/ch_blockstorage-api-v2.xml:464(para) -msgid "The snapshot is being deleted." -msgstr "" - -#: ./api-ref/src/docbkx/ch_blockstorage-api-v2.xml:476(para) -msgid "A snapshot creation error occurred." -msgstr "" - -#: ./api-ref/src/docbkx/ch_blockstorage-api-v2.xml:488(para) -msgid "A snapshot deletion error occurred." -msgstr "" - -#: ./api-ref/src/docbkx/ch_blockstorage-api-v2.xml:516(title) -msgid "Volume manage extension (os-volume-manage)" -msgstr "" - -#: ./api-ref/src/docbkx/ch_blockstorage-api-v2.xml:517(para) -msgid "Creates volumes by using existing storage instead of allocating new storage." -msgstr "" - -#: ./api-ref/src/docbkx/ch_blockstorage-api-v2.xml:524(title) -msgid "Volume image metadata extension (os-vol-image-meta)" -msgstr "" - -#: ./api-ref/src/docbkx/ch_blockstorage-api-v2.xml:525(para) -msgid "Shows image metadata that is associated with a volume." -msgstr "" - -#: ./api-ref/src/docbkx/ch_blockstorage-api-v2.xml:532(para) -msgid "Administrator only. Lists all back-end storage pools that are known to the scheduler service." -msgstr "" - -#: ./api-ref/src/docbkx/ch_blockstorage-api-v2.xml:539(title) -msgid "Volume transfer" -msgstr "" - -#: ./api-ref/src/docbkx/ch_blockstorage-api-v2.xml:540(para) -msgid "Transfers a volume from one user to another user." -msgstr "" - -#: ./api-ref/src/docbkx/ch_blockstorage-api-v2.xml:546(title) -msgid "Consistency groups" -msgstr "" - -#: ./api-ref/src/docbkx/ch_blockstorage-api-v2.xml:547(para) -msgid "Consistency groups enable you to create snapshots at the exact same point in time from multiple volumes. For example, a database might place its tables, logs, and configuration on separate volumes. To restore this database from a previous point in time, it makes sense to restore the logs, tables, and configuration together from the exact same point in time." -msgstr "" - -#: ./api-ref/src/docbkx/ch_blockstorage-api-v2.xml:555(para) -msgid "Use the policy.json file to grant permissions for these actions to limit roles." -msgstr "" - -#: ./api-ref/src/docbkx/ch_blockstorage-api-v2.xml:562(title) -msgid "Consistency group snapshots" -msgstr "" - -#: ./api-ref/src/docbkx/ch_blockstorage-api-v2.xml:563(para) -msgid "Lists all, lists all with details, shows details for, creates, and deletes consistency group snapshots." -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v1.xml:18(para) -msgid "The Shared File Systems API v1 is functionally identical to the Shared File Systems API v2. Subsequent API v2 micro-versions, such as v2.1, differ from API v1." -msgstr "" - -#: ./api-ref/src/docbkx/ch_share-v1.xml:24(para) -msgid "(Since API v2.0) The API uses Compute-style micro-versions." -msgstr "" - -#. Put one translator per line, in the form of NAME , YEAR1, YEAR2 -#: ./api-ref/src/docbkx/ch_share-v1.xml:0(None) -msgid "translator-credits" -msgstr "" - diff --git a/api-ref/locale/fr.po b/api-ref/locale/fr.po index 728465548..9e0e47a79 100644 --- a/api-ref/locale/fr.po +++ b/api-ref/locale/fr.po @@ -11,7 +11,7 @@ msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" -"POT-Creation-Date: 2016-04-12 16:15+0000\n" +"POT-Creation-Date: 2016-06-03 05:11+0000\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" @@ -382,9 +382,6 @@ msgstr "Extension de fournisseur de réseaux multiple (réseaux)" msgid "Networks provider extended attributes (networks)" msgstr "Attibuts étendus de fournisseur de réseaux (réseaux)" -msgid "OAuth extension (OS-OAUTH1)" -msgstr "Extension OAuth (OS-OAUTH1)" - msgid "OS-INHERIT extension (OS-INHERIT)" msgstr "L'extension OS-INHERIT (OS-INHERIT)" diff --git a/firstapp/source/locale/firstapp.pot b/firstapp/source/locale/firstapp.pot deleted file mode 100644 index 605b7a1f3..000000000 --- a/firstapp/source/locale/firstapp.pot +++ /dev/null @@ -1,3726 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2015, OpenStack contributors -# This file is distributed under the same license as the FirstApp package. -# FIRST AUTHOR , YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: FirstApp 0.1\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2016-04-13 06:01+0000\n" -"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" -"Last-Translator: FULL NAME \n" -"Language-Team: LANGUAGE \n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" - -#: ../advice.rst:3 -msgid "Advice for developers new to operations" -msgstr "" - -#: ../advice.rst:5 -msgid "" -"This section introduces some operational concepts and tasks to developers " -"who have not written cloud applications before." -msgstr "" - -#: ../advice.rst:9 -msgid "Monitoring" -msgstr "" - -#: ../advice.rst:11 -msgid "" -"Monitoring is essential for 'scalable' cloud applications. You must know how " -"many requests are coming in and the impact that these requests have on " -"various services. You must have enough information to determine whether to " -"start another worker or API service as you did in :doc:`/scaling_out`." -msgstr "" - -#: ../advice.rst:20 -msgid "" -"In addition to this kind of monitoring, you should consider availability " -"monitoring. Although your application might not care about a failed worker, " -"it should care about a failed database server." -msgstr "" - -#: ../advice.rst:24 -msgid "" -"Use the `Health Endpoint Monitoring Pattern ` to implement functional checks within your " -"application that external tools can access through exposed endpoints at " -"regular intervals." -msgstr "" - -#: ../advice.rst:30 -msgid "Backups" -msgstr "" - -#: ../advice.rst:32 -msgid "" -"Just as you back up information on a non-cloud server, you must back up non-" -"reproducible information, such as information on a database server, file " -"server, or in application log files. Just because something is 'in the " -"cloud' does not mean that the underlying hardware or systems cannot fail." -msgstr "" - -#: ../advice.rst:38 -msgid "" -"OpenStack provides a couple of tools that make it easy to back up data. If " -"your provider runs OpenStack Object Storage, you can use its API calls and " -"CLI tools to work with archive files." -msgstr "" - -#: ../advice.rst:42 -msgid "" -"You can also use the OpenStack API to create snapshots of running instances " -"and persistent volumes. For more information, see your SDK documentation." -msgstr "" - -#: ../advice.rst:49 -msgid "" -"In addition to configuring backups, review your policies about what you back " -"up and how long to retain each backed up item." -msgstr "" - -#: ../advice.rst:53 -msgid "Phoenix servers" -msgstr "" - -#: ../advice.rst:55 -msgid "" -"`Phoenix Servers `_, named " -"for the mythical bird that is consumed by fire and rises from the ashes to " -"live again, make it easy to start over with new instances." -msgstr "" - -#: ../advice.rst:60 -msgid "" -"Application developers and operators who use phoenix servers have access to " -"systems that are built from a known baseline, such as a specific operating " -"system version, and to tooling that automatically builds, installs, and " -"configures a system." -msgstr "" - -#: ../advice.rst:65 -msgid "" -"If you deploy your application on a regular basis, you can resolve outages " -"and make security updates without manual intervention. If an outage occurs, " -"you can provision more resources in another region. If you must patch " -"security holes, you can provision additional compute nodes that are built " -"with the updated software. Then, you can terminate vulnerable nodes and " -"automatically fail-over traffic to the new instances." -msgstr "" - -#: ../advice.rst:74 -msgid "Security" -msgstr "" - -#: ../advice.rst:76 -msgid "" -"If one application instance is compromised, all instances with the same " -"image and configuration will likely suffer the same vulnerability. The " -"safest path is to use configuration management to rebuild all instances." -msgstr "" - -#: ../advice.rst:82 -msgid "Configuration management" -msgstr "" - -#: ../advice.rst:84 -msgid "" -"Configuration management tools, such as Ansible, Chef, and Puppet, enable " -"you to describe exactly what to install and configure on an instance. Using " -"these descriptions, these tools implement the changes that are required to " -"get to the desired state." -msgstr "" - -#: ../advice.rst:89 -msgid "" -"These tools vastly reduce the effort it takes to work with large numbers of " -"servers, and also improve the ability to recreate, update, move, and " -"distribute applications." -msgstr "" - -#: ../advice.rst:94 -msgid "Application deployment" -msgstr "" - -#: ../advice.rst:96 -msgid "" -"How do you deploy your application? For example, do you pull the latest code " -"from a source control repository? Do you make packaged releases that update " -"infrequently? Do you perform haphazard tests in a development environment " -"and deploy only after major changes?" -msgstr "" - -#: ../advice.rst:101 -msgid "" -"One of the latest trends in scalable cloud application deployment is " -"`continuous integration `_ and `continuous deployment `_ (CI/CD)." -msgstr "" - -#: ../advice.rst:106 -msgid "" -"CI/CD means that you always test your application and make frequent " -"deployments to production." -msgstr "" - -#: ../advice.rst:109 -msgid "" -"In this tutorial, we have downloaded the latest version of our application " -"from source and installed it on a standard image. Our magic installation " -"script also updates the standard image to have the latest dependencies that " -"you need to run the application." -msgstr "" - -#: ../advice.rst:114 -msgid "" -"Another approach is to create a 'gold' image, which pre-installs your " -"application and its dependencies. A 'gold' image enables faster boot times " -"and more control over what is on the instance. However, if you use 'gold' " -"images, you must have a process in place to ensure that these images do not " -"fall behind on security updates." -msgstr "" - -#: ../advice.rst:121 -msgid "Fail fast" -msgstr "" - -#: ../appendix.rst:3 -msgid "Appendix" -msgstr "" - -#: ../appendix.rst:6 -msgid "Bootstrap your network" -msgstr "" - -#: ../appendix.rst:8 -msgid "" -"Most cloud providers provision all network objects that are required to boot " -"an instance. To determine whether these objects were created for you, access " -"the Network Topology section of the OpenStack dashboard." -msgstr "" - -#: ../appendix.rst:21 -msgid "Specify a network during instance build" -msgstr "" - -#: ../block_storage.rst:3 -msgid "Block Storage" -msgstr "" - -#: ../block_storage.rst:8 -msgid "" -"By default, data in OpenStack instances is stored on 'ephemeral' disks. " -"These disks remain with the instance throughout its lifetime. When you " -"terminate the instance, that storage and all the data stored on it " -"disappears. Ephemeral storage is allocated to a single instance and cannot " -"be moved to another instance." -msgstr "" - -#: ../block_storage.rst:14 -msgid "" -"This section introduces block storage, also known as volume storage, which " -"provides access to persistent storage devices. You interact with block " -"storage by attaching volumes to running instances just as you might attach a " -"USB drive to a physical server. You can detach volumes from one instance and " -"reattach them to another instance and the data remains intact. The OpenStack " -"Block Storage (cinder) project implements block storage." -msgstr "" - -#: ../block_storage.rst:22 -msgid "" -"Though you might have configured Object Storage to store images, the Fractal " -"application needs a database to track the location of, and parameters that " -"were used to create, images in Object Storage. This database server cannot " -"fail." -msgstr "" - -#: ../block_storage.rst:27 -msgid "" -"If you are an advanced user, think about how you might remove the database " -"from the architecture and replace it with Object Storage metadata, and then " -"contribute these steps to :doc:`craziness`." -msgstr "" - -#: ../block_storage.rst:31 -msgid "" -"Otherwise, continue reading to learn how to work with, and move the Fractal " -"application database server to use, block storage." -msgstr "" - -#: ../block_storage.rst:35 -msgid "Basics" -msgstr "" - -#: ../block_storage.rst:37 -msgid "" -"Later on, you will use a Block Storage volume to provide persistent storage " -"for the database server for the Fractal application. But first, learn how to " -"create and attach a Block Storage device." -msgstr "" - -#: ../block_storage.rst:43 ../durability.rst:70 ../introduction.rst:14 -msgid "This section has not yet been completed for the .NET SDK." -msgstr "" - -#: ../block_storage.rst:47 -msgid "This section has not yet been completed for the fog SDK." -msgstr "" - -#: ../block_storage.rst:51 ../introduction.rst:22 -msgid "This section has not yet been completed for the jclouds SDK." -msgstr "" - -#: ../block_storage.rst:55 ../durability.rst:109 ../introduction.rst:26 -msgid "This section has not yet been completed for the pkgcloud SDK." -msgstr "" - -#: ../block_storage.rst:59 ../durability.rst:113 ../networking.rst:56 -msgid "This section has not yet been completed for the OpenStack SDK." -msgstr "" - -#: ../block_storage.rst:67 -msgid "Connect to the API endpoint:" -msgstr "" - -#: ../block_storage.rst:83 -msgid "To try it out, make a 1GB volume called :test'." -msgstr "" - -#: ../block_storage.rst:103 -msgid "The parameter :code:`size` is in gigabytes." -msgstr "" - -#: ../block_storage.rst:105 -msgid "To see if the volume creation was successful, list all volumes:" -msgstr "" - -#: ../block_storage.rst:125 -msgid "Attach the storage volume to a running instance." -msgstr "" - -#: ../block_storage.rst:128 -msgid "Use Block Storage for the Fractal database server" -msgstr "" - -#: ../block_storage.rst:130 -msgid "" -"You need a server for the dedicated database. Use the image, flavor, and " -"keypair that you used in :doc:`/getting_started` to launch an :code:`app-" -"database` instance." -msgstr "" - -#: ../block_storage.rst:134 -msgid "" -"You also need a security group to permit access to the database server (for " -"MySQL, port 3306) from the network:" -msgstr "" - -#: ../block_storage.rst:151 -msgid "" -"Create a volume object by using the unique identifier (UUID) for the volume. " -"Then, use the server object from the previous code snippet to attach the " -"volume to it at :code:`/dev/vdb`:" -msgstr "" - -#: ../block_storage.rst:169 -msgid "Log in to the server to run the following steps." -msgstr "" - -#: ../block_storage.rst:171 -msgid "" -"Replace :code:`IP_SERVICES` with the IP address of the services instance and " -"USERNAME to the appropriate user name." -msgstr "" - -#: ../block_storage.rst:174 -msgid "Now prepare the empty block device." -msgstr "" - -#: ../block_storage.rst:186 -msgid "" -"Stop the running MySQL database service and move the database files from :" -"file:`/var/lib/mysql` to the new volume, which is temporarily mounted at :" -"file:`/mnt/database`." -msgstr "" - -#: ../block_storage.rst:195 -msgid "" -"Sync the file systems and mount the block device that contains the database " -"files to :file:`/var/lib/mysql`." -msgstr "" - -#: ../block_storage.rst:206 -msgid "" -"Finally, start the stopped MySQL database service and validate that " -"everything works as expected." -msgstr "" - -#: ../block_storage.rst:215 -msgid "Extras" -msgstr "" - -#: ../block_storage.rst:217 -msgid "" -"You can detach the volume and reattach it elsewhere, or use the following " -"steps to delete the volume." -msgstr "" - -#: ../block_storage.rst:221 -msgid "The following operations are destructive and result in data loss." -msgstr "" - -#: ../block_storage.rst:223 -msgid "To detach and delete a volume:" -msgstr "" - -#: ../block_storage.rst:235 -msgid "" -":code:`detach_volume` and :code:`destroy_volume` take a volume object, not a " -"name." -msgstr "" - -#: ../block_storage.rst:247 -msgid "" -"Other features, such as creating volume snapshots, are useful for backups:" -msgstr "" - -#: ../block_storage.rst:257 -msgid "" -"For information about these and other calls, see `libcloud documentation " -"`_." -msgstr "" - -#: ../block_storage.rst:261 -msgid "Work with the OpenStack Database service" -msgstr "" - -#: ../block_storage.rst:263 -msgid "" -"Previously, you manually created the database, which is useful for a single " -"database that you rarely update. However, the OpenStack :code:`trove` " -"component provides Database as a Service (DBaaS)." -msgstr "" - -#: ../block_storage.rst:267 -msgid "" -"This OpenStack Database service is not installed in many clouds right now, " -"but if your cloud supports it, it can make your life a lot easier when " -"working with databases." -msgstr "" - -#: ../block_storage.rst:271 -msgid "" -"SDKs do not generally support the service yet, but you can use the 'trove' " -"command-line client to work with it instead." -msgstr "" - -#: ../block_storage.rst:274 -msgid "" -"To install the 'trove' command-line client, see `Install the OpenStack " -"command-line clients `_." -msgstr "" - -#: ../block_storage.rst:278 -msgid "" -"To set up environment variables for your cloud in an :file:`openrc.sh` file, " -"see `Set environment variables using the OpenStack RC file `_." -msgstr "" - -#: ../block_storage.rst:282 -msgid "" -"Ensure you have an :file:`openrc.sh` file, source it, and validate that your " -"trove client works:" -msgstr "" - -#: ../block_storage.rst:299 -msgid "" -"For information about supported features and how to work with an existing " -"database service installation, see `Database as a Service in OpenStack " -"`_." -msgstr "" - -#: ../block_storage.rst:304 ../craziness.rst:72 ../durability.rst:531 -#: ../getting_started.rst:1585 ../introduction.rst:790 ../networking.rst:797 -#: ../orchestration.rst:482 ../scaling_out.rst:473 -msgid "Next steps" -msgstr "" - -#: ../block_storage.rst:306 -msgid "" -"You should now be fairly confident working with Block Storage volumes. For " -"information about other calls, see the volume documentation for your SDK. " -"Or, try one of these tutorial steps:" -msgstr "" - -#: ../block_storage.rst:310 ../durability.rst:548 ../getting_started.rst:1594 -#: ../introduction.rst:806 ../scaling_out.rst:492 -msgid ":doc:`/orchestration`: Automatically orchestrate your application." -msgstr "" - -#: ../block_storage.rst:311 ../durability.rst:549 ../getting_started.rst:1595 -#: ../introduction.rst:807 ../orchestration.rst:489 ../scaling_out.rst:493 -msgid ":doc:`/networking`: Learn about complex networking." -msgstr "" - -#: ../block_storage.rst:312 ../durability.rst:550 ../getting_started.rst:1596 -#: ../introduction.rst:808 ../networking.rst:803 ../orchestration.rst:490 -#: ../scaling_out.rst:494 -msgid ":doc:`/advice`: Get advice about operations." -msgstr "" - -#: ../craziness.rst:3 -msgid "Going crazy" -msgstr "" - -#: ../craziness.rst:5 -msgid "This section explores options for expanding the sample application." -msgstr "" - -#: ../craziness.rst:8 -msgid "Regions and geographic diversity" -msgstr "" - -#: ../craziness.rst:10 -msgid "" -"For more information about multi-site clouds, see the `Multi-Site chapter " -"`_ in the " -"Architecture Design Guide." -msgstr "" - -#: ../craziness.rst:14 -msgid "" -"OpenStack supports 'regions', which are geographically-separated " -"installations that are connected to a single service catalog. This section " -"explains how to expand the Fractal application to use multiple regions for " -"high availability." -msgstr "" - -#: ../craziness.rst:19 ../craziness.rst:33 ../craziness.rst:40 -#: ../craziness.rst:69 -msgid "This section is incomplete. Please help us finish it!" -msgstr "" - -#: ../craziness.rst:22 -msgid "Multiple clouds" -msgstr "" - -#: ../craziness.rst:24 -msgid "" -"For more information about hybrid clouds, see the `Hybrid Cloud chapter " -"`_ in the Architecture " -"Design Guide." -msgstr "" - -#: ../craziness.rst:29 -msgid "" -"You might want to use multiple clouds, such as a private cloud inside your " -"organization and a public cloud. This section attempts to do exactly that." -msgstr "" - -#: ../craziness.rst:36 -msgid "High availability" -msgstr "" - -#: ../craziness.rst:38 -msgid "Using Pacemaker to look at the API." -msgstr "" - -#: ../craziness.rst:43 -msgid "conf.d, etc.d" -msgstr "" - -#: ../craziness.rst:45 -msgid "Use conf.d and etc.d." -msgstr "" - -#: ../craziness.rst:47 -msgid "" -"In earlier sections, the Fractal application used an installation script " -"into which the metadata API passed parameters to bootstrap the cluster. " -"`Etcd `_ is \"a distributed, consistent key-" -"value store for shared configuration and service discovery\" that you can " -"use to store configurations. You can write updated versions of the Fractal " -"worker component to connect to Etcd or use `Confd `_ to poll for changes from Etcd and write changes to " -"a configuration file on the local file system, which the Fractal worker can " -"use for configuration." -msgstr "" - -#: ../craziness.rst:58 -msgid "Use Object Storage instead of a database" -msgstr "" - -#: ../craziness.rst:60 -msgid "" -"We have not quite figured out how to stop using a database, but the general " -"steps are:" -msgstr "" - -#: ../craziness.rst:63 -msgid "" -"Change the Fractal upload code to store metadata with the object in Object " -"Storage." -msgstr "" - -#: ../craziness.rst:66 -msgid "" -"Change the API code, such as \"list fractals,\" to query Object Storage to " -"get the metadata." -msgstr "" - -#: ../craziness.rst:74 -msgid "" -"Wow! If you have made it through this section, you know more than the " -"authors of this guide know about working with OpenStack clouds." -msgstr "" - -#: ../craziness.rst:77 -msgid "" -"Perhaps you can `contribute `_?" -msgstr "" - -#: ../durability.rst:3 -msgid "Make it durable" -msgstr "" - -#: ../durability.rst:14 -msgid "This section introduces object storage." -msgstr "" - -#: ../durability.rst:16 -msgid "" -"`OpenStack Object Storage `_ (code-named swift) is open-source software that enables you to " -"create redundant, scalable data storage by using clusters of standardized " -"servers to store petabytes of accessible data. It is a long-term storage " -"system for large amounts of static data that you can retrieve, leverage, and " -"update. Unlike more traditional storage systems that you access through a " -"file system, you access Object Storage through an API." -msgstr "" - -#: ../durability.rst:24 -msgid "The Object Storage API is organized around objects and containers." -msgstr "" - -#: ../durability.rst:26 -msgid "" -"Similar to the UNIX programming model, an object, such as a document or an " -"image, is a \"bag of bytes\" that contains data. You use containers to group " -"objects. You can place many objects inside a container, and your account can " -"have many containers." -msgstr "" - -#: ../durability.rst:31 -msgid "" -"If you think about how you traditionally make what you store durable, you " -"quickly conclude that keeping multiple copies of your objects on separate " -"systems is a good way strategy. However, keeping track of those multiple " -"copies is difficult, and building that into an app requires complicated " -"logic." -msgstr "" - -#: ../durability.rst:36 -msgid "" -"OpenStack Object Storage automatically replicates each object at least twice " -"before returning 'write success' to your API call. A good strategy is to " -"keep three copies of objects, by default, at all times, replicating them " -"across the system in case of hardware failure, maintenance, network outage, " -"or another kind of breakage. This strategy is very convenient for app " -"creation. You can just dump objects into object storage and not worry about " -"the additional work that it takes to keep them safe." -msgstr "" - -#: ../durability.rst:46 -msgid "Use Object Storage to store fractals" -msgstr "" - -#: ../durability.rst:48 -msgid "" -"The Fractals app currently uses the local file system on the instance to " -"store the images that it generates. For a number of reasons, this approach " -"is not scalable or durable." -msgstr "" - -#: ../durability.rst:52 -msgid "" -"Because the local file system is ephemeral storage, the fractal images are " -"lost along with the instance when the instance is terminated. Block-based " -"storage, which the :doc:`/block_storage` section discusses, avoids that " -"problem, but like local file systems, it requires administration to ensure " -"that it does not fill up, and immediate attention if disks fail." -msgstr "" - -#: ../durability.rst:58 -msgid "" -"The Object Storage service manages many of the tasks normally managed by the " -"application owner. The Object Storage service provides a scalable and " -"durable API that you can use for the fractals app, eliminating the need to " -"be aware of the low level details of how objects are stored and replicated, " -"and how to grow the storage pool. Object Storage handles replication for " -"you. It stores multiple copies of each object. You can use the Object " -"Storage API to return an object, on demand." -msgstr "" - -#: ../durability.rst:66 -msgid "First, learn how to connect to the Object Storage endpoint:" -msgstr "" - -#: ../durability.rst:94 -msgid "" -"Libcloud 0.16 and 0.17 are afflicted with a bug that means authentication to " -"a swift endpoint can fail with `a Python exception `_. If you encounter this, you can upgrade your " -"libcloud version, or apply a simple `2-line patch `_." -msgstr "" - -#: ../durability.rst:102 -msgid "" -"Libcloud uses a different connector for Object Storage to all other " -"OpenStack services, so a conn object from previous sections will not work " -"here and we have to create a new one named :code:`swift`." -msgstr "" - -#: ../durability.rst:121 -msgid "" -"To begin to store objects, we must first make a container. Call yours :code:" -"`fractals`:" -msgstr "" - -#: ../durability.rst:130 ../durability.rst:149 ../durability.rst:164 -#: ../durability.rst:183 -msgid "You should see output such as:" -msgstr "" - -#: ../durability.rst:155 -msgid "" -"You should now be able to see this container appear in a listing of all " -"containers in your account:" -msgstr "" - -#: ../durability.rst:189 -msgid "" -"The next logical step is to upload an object. Find a photo of a goat on " -"line, name it :code:`goat.jpg`, and upload it to your :code:`fractals` " -"container:" -msgstr "" - -#: ../durability.rst:212 -msgid "" -"List objects in your :code:`fractals` container to see if the upload was " -"successful. Then, download the file to verify that the md5sum is the same:" -msgstr "" - -#: ../durability.rst:305 -msgid "Finally, clean up by deleting the test object:" -msgstr "" - -#: ../durability.rst:326 -msgid "You must pass in objects and not object names to the delete commands." -msgstr "" - -#: ../durability.rst:328 -msgid "Now, no more objects are available in the :code:`fractals` container." -msgstr "" - -#: ../durability.rst:339 -msgid "Back up the Fractals from the database on the Object Storage" -msgstr "" - -#: ../durability.rst:341 -msgid "" -"Back up the Fractals app images, which are currently stored inside the " -"database, on Object Storage." -msgstr "" - -#: ../durability.rst:344 -msgid "Place the images in the :code:`fractals` container:" -msgstr "" - -#: ../durability.rst:365 -msgid "" -"Next, back up all existing fractals from the database to the swift " -"container. A simple loop takes care of that:" -msgstr "" - -#: ../durability.rst:368 ../durability.rst:395 -msgid "Replace :code:`IP_API_1` with the IP address of the API instance." -msgstr "" - -#: ../durability.rst:397 -msgid "" -"The example code uses the awesome `Requests library `_. Before you try to run the previous script, make " -"sure that it is installed on your system." -msgstr "" - -#: ../durability.rst:404 -msgid "Configure the Fractals app to use Object Storage" -msgstr "" - -#: ../durability.rst:406 -msgid "" -"Currently, you cannot directly store generated images in OpenStack Object " -"Storage. Please revisit this section again in the future." -msgstr "" - -#: ../durability.rst:411 -msgid "Extra features" -msgstr "" - -#: ../durability.rst:414 -msgid "Delete containers" -msgstr "" - -#: ../durability.rst:416 -msgid "" -"To delete a container, you must first remove all objects from the container. " -"Otherwise, the delete operation fails:" -msgstr "" - -#: ../durability.rst:438 -msgid "It is not possible to restore deleted objects. Be careful." -msgstr "" - -#: ../durability.rst:441 -msgid "Add metadata to objects" -msgstr "" - -#: ../durability.rst:443 -msgid "" -"You can complete advanced tasks such as uploading an object with metadata, " -"as shown in following example. For more information, see the documentation " -"for your SDK." -msgstr "" - -#: ../durability.rst:449 ../durability.rst:467 -msgid "" -"This option also uses a bit stream to upload the file, iterating bit by bit " -"over the file and passing those bits to Object Storage as they come. " -"Compared to loading the entire file in memory and then sending it, this " -"method is more efficient, especially for larger files." -msgstr "" - -#: ../durability.rst:479 -msgid "Large objects" -msgstr "" - -#: ../durability.rst:481 -msgid "" -"For efficiency, most Object Storage installations treat large objects, :code:" -"`> 5GB`, differently than smaller objects." -msgstr "" - -#: ../durability.rst:492 -msgid "" -"If you work with large objects, use the :code:`RegionScopedBlobStoreContext` " -"class family instead of the ones used so far." -msgstr "" - -#: ../durability.rst:495 -msgid "" -"Large file uploads that use the :code:`openstack-swift` provider are " -"supported in only jclouds V2, currently in beta. Also, the default chunk " -"size is 64 Mb. Consider changing this as homework." -msgstr "" - -#: ../durability.rst:506 -msgid "" -"If you work with large objects, use the :code:`ex_multipart_upload_object` " -"call instead of the simpler :code:`upload_object` call. The call splits the " -"large object into chunks and creates a manifest so that the chunks can be " -"recombined on download. Change the :code:`chunk_size` parameter, in bytes, " -"to a value that your cloud can accept." -msgstr "" - -#: ../durability.rst:519 ../getting_started.rst:1602 ../introduction.rst:812 -#: ../scaling_out.rst:498 -msgid "Complete code sample" -msgstr "" - -#: ../durability.rst:521 -msgid "" -"This file contains all the code from this tutorial section. This class lets " -"you view and run the code." -msgstr "" - -#: ../durability.rst:524 -msgid "" -"Before you run this class, confirm that you have configured it for your " -"cloud and the instance running the Fractals application." -msgstr "" - -#: ../durability.rst:533 -msgid "" -"You should now be fairly confident working with Object Storage. You can find " -"more information about the Object Storage SDK calls at:" -msgstr "" - -#: ../durability.rst:538 -msgid "" -"https://github.com/fog/fog/blob/master/lib/fog/openstack/docs/storage.md" -msgstr "" - -#: ../durability.rst:542 -msgid "https://libcloud.readthedocs.org/en/latest/storage/api.html" -msgstr "" - -#: ../durability.rst:544 -msgid "Or, try one of these tutorial steps:" -msgstr "" - -#: ../durability.rst:546 ../getting_started.rst:1592 ../introduction.rst:804 -#: ../scaling_out.rst:490 -msgid "" -":doc:`/block_storage`: Migrate the database to block storage, or use the " -"database-as-a-service component." -msgstr "" - -#: ../durability.rst:551 ../getting_started.rst:1597 ../introduction.rst:809 -#: ../networking.rst:804 ../orchestration.rst:491 ../scaling_out.rst:495 -msgid "" -":doc:`/craziness`: Learn some crazy things that you might not think to do ;)" -msgstr "" - -#: ../getting_started.rst:0 -msgid "OpenStack SDKs" -msgstr "" - -#: ../getting_started.rst:3 -msgid "Getting started" -msgstr "" - -#: ../getting_started.rst:6 -msgid "Who should read this guide" -msgstr "" - -#: ../getting_started.rst:8 -msgid "" -"This guide is for experienced software developers who want to deploy " -"applications to OpenStack clouds." -msgstr "" - -#: ../getting_started.rst:11 -msgid "" -"If you are familiar with OpenStack but have not created a cloud application " -"in general or an OpenStack application in particular, this section teaches " -"you how to program with OpenStack components." -msgstr "" - -#: ../getting_started.rst:16 -msgid "What you will learn" -msgstr "" - -#: ../getting_started.rst:18 -msgid "" -"Deploying applications in a cloud environment can be very different from " -"deploying them in a traditional IT environment. This guide teaches you how " -"to deploy applications on OpenStack and some best practices for cloud " -"application development." -msgstr "" - -#: ../getting_started.rst:24 -msgid "A general overview" -msgstr "" - -#: ../getting_started.rst:26 -msgid "" -"This tutorial shows two applications. The first application is a simple " -"fractal generator that uses mathematical equations to generate beautiful " -"`fractal images `_. We show you this " -"application in its entirety so that you can compare it to a second, more " -"robust, application." -msgstr "" - -#: ../getting_started.rst:32 -msgid "The second application is an OpenStack application that enables you to:" -msgstr "" - -#: ../getting_started.rst:34 -msgid "" -"Create and delete compute resources. These resources are virtual machine " -"instances where the Fractals application runs." -msgstr "" - -#: ../getting_started.rst:36 -msgid "" -"Make cloud-related architecture decisions such as turning functions into " -"micro-services and modularizing them." -msgstr "" - -#: ../getting_started.rst:38 -msgid "Scale available resources up and down." -msgstr "" - -#: ../getting_started.rst:39 -msgid "Use Object and Block storage for file and database persistence." -msgstr "" - -#: ../getting_started.rst:40 -msgid "Use Orchestration services to automatically adjust to the environment." -msgstr "" - -#: ../getting_started.rst:41 -msgid "Customize networking for better performance and segregation." -msgstr "" - -#: ../getting_started.rst:42 -msgid "Explore and apply advanced OpenStack cloud features." -msgstr "" - -#: ../getting_started.rst:45 -msgid "Choose your OpenStack SDK" -msgstr "" - -#: ../getting_started.rst:47 -msgid "" -"Anyone with a programming background can easily read the code in this guide. " -"Although this guide focuses on a particular SDK, you can use other languages " -"and toolkits with the OpenStack cloud:" -msgstr "" - -#: ../getting_started.rst:56 -msgid "Language" -msgstr "" - -#: ../getting_started.rst:57 -msgid "Name" -msgstr "" - -#: ../getting_started.rst:58 ../introduction.rst:579 ../introduction.rst:655 -msgid "Description" -msgstr "" - -#: ../getting_started.rst:59 -msgid "URL" -msgstr "" - -#: ../getting_started.rst:60 ../getting_started.rst:65 -#: ../getting_started.rst:69 -msgid "Python" -msgstr "" - -#: ../getting_started.rst:61 -msgid "`Libcloud `_" -msgstr "" - -#: ../getting_started.rst:62 -msgid "" -"A Python-based library that the Apache Foundation manages. Use it to work " -"with multiple cloud types." -msgstr "" - -#: ../getting_started.rst:64 -msgid "" -"https://libcloud.readthedocs.org/en/latest/compute/drivers/openstack.html" -msgstr "" - -#: ../getting_started.rst:66 -msgid "OpenStack SDK" -msgstr "" - -#: ../getting_started.rst:67 -msgid "A Python-based library for OpenStack." -msgstr "" - -#: ../getting_started.rst:68 -msgid "http://git.openstack.org/cgit/openstack/python-openstacksdk" -msgstr "" - -#: ../getting_started.rst:70 -msgid "Shade" -msgstr "" - -#: ../getting_started.rst:71 -msgid "" -"A Python-based library developed by OpenStack Infra team. Use it to operate " -"multiple OpenStack clouds." -msgstr "" - -#: ../getting_started.rst:73 -msgid "http://git.openstack.org/cgit/openstack-infra/shade" -msgstr "" - -#: ../getting_started.rst:74 -msgid "Java" -msgstr "" - -#: ../getting_started.rst:75 -msgid "`jClouds `_" -msgstr "" - -#: ../getting_started.rst:76 -msgid "" -"A Java-based library that the Apache Foundation manages. Use it to work with " -"multiple cloud types." -msgstr "" - -#: ../getting_started.rst:78 -msgid "https://jclouds.apache.org/guides/openstack/" -msgstr "" - -#: ../getting_started.rst:79 -msgid "Ruby" -msgstr "" - -#: ../getting_started.rst:80 -msgid "`fog `_" -msgstr "" - -#: ../getting_started.rst:81 -msgid "A Ruby-based SDK. Use it to work with multiple clouds." -msgstr "" - -#: ../getting_started.rst:83 -msgid "" -"https://github.com/fog/fog-openstack/blob/master/lib/fog/openstack/docs/" -"getting_started.md" -msgstr "" - -#: ../getting_started.rst:84 -msgid "node.js" -msgstr "" - -#: ../getting_started.rst:85 -msgid "`pkgcloud `_" -msgstr "" - -#: ../getting_started.rst:86 -msgid "A Node.js-based SDK. Use it work with multiple clouds." -msgstr "" - -#: ../getting_started.rst:88 -msgid "" -"https://github.com/pkgcloud/pkgcloud/tree/master/docs/providers/openstack" -msgstr "" - -#: ../getting_started.rst:89 -msgid "PHP" -msgstr "" - -#: ../getting_started.rst:90 -msgid "`php-opencloud `_" -msgstr "" - -#: ../getting_started.rst:91 -msgid "" -"A PHP-based library. Use it to write PHP code that works with OpenStack " -"clouds." -msgstr "" - -#: ../getting_started.rst:93 -msgid "" -"http://php-opencloud.readthedocs.org/en/latest/getting-started-with-" -"openstack.html" -msgstr "" - -#: ../getting_started.rst:94 -msgid ".NET Framework" -msgstr "" - -#: ../getting_started.rst:95 -msgid "OpenStack SDK for Microsoft .NET" -msgstr "" - -#: ../getting_started.rst:96 -msgid "" -"A .NET-based library. Use it to write C++ or C# code for Microsoft " -"applications." -msgstr "" - -#: ../getting_started.rst:98 -msgid "https://www.nuget.org/packages/openstack.net" -msgstr "" - -#: ../getting_started.rst:99 -msgid "Go" -msgstr "" - -#: ../getting_started.rst:100 -msgid "`gophercloud `_" -msgstr "" - -#: ../getting_started.rst:101 -msgid "A go-based SDK. Use it with multiple clouds." -msgstr "" - -#: ../getting_started.rst:103 -msgid "http://gophercloud.io/" -msgstr "" - -#: ../getting_started.rst:105 -msgid "" -"For a list of available SDKs, see `Software Development Kits `_." -msgstr "" - -#: ../getting_started.rst:107 -msgid "" -"Other versions of this guide show you how to use the other SDKs and " -"languages to complete these tasks. If you are a developer for another " -"toolkit that you would like this guide to include, feel free to submit code " -"snippets. For more information, contact `OpenStack Documentation team " -"`_ members." -msgstr "" - -#: ../getting_started.rst:114 -msgid "What you need" -msgstr "" - -#: ../getting_started.rst:116 -msgid "" -"We assume that you can already access an OpenStack cloud. You must have a " -"project, also known as a tenant, with a minimum quota of six instances. " -"Because the Fractals application runs in Ubuntu, Debian, Fedora-based, and " -"openSUSE-based distributions, you must create instances that use one of " -"these operating systems." -msgstr "" - -#: ../getting_started.rst:122 -msgid "To interact with the cloud, you must also have" -msgstr "" - -#: ../getting_started.rst:126 -msgid "" -"`OpenStack Cloud SDK for Microsoft .NET 1.4.0.1 or later installed `_." -msgstr "" - -#: ../getting_started.rst:131 -msgid "" -"To install the OpenStack .NET SDK, use the NeGet Package Manager that is " -"included with Visual Studio and Xamarin Studio. You simply add a package " -"named 'openstack.net' and the NeGet Package Manager automatically installs " -"the necessary dependencies." -msgstr "" - -#: ../getting_started.rst:138 -msgid "This document has not yet been completed for the .NET SDK." -msgstr "" - -#: ../getting_started.rst:142 -msgid "" -"`fog 1.19 or higher installed `_ and working with ruby gems 1.9." -msgstr "" - -#: ../getting_started.rst:148 -msgid "This document has not yet been completed for the fog SDK." -msgstr "" - -#: ../getting_started.rst:152 -msgid "" -"`jClouds 1.8 or higher installed `_." -msgstr "" - -#: ../getting_started.rst:156 -msgid "This document has not yet been completed for the jclouds SDK." -msgstr "" - -#: ../getting_started.rst:160 -msgid "" -"`libcloud 0.15.1 or higher installed `_." -msgstr "" - -#: ../getting_started.rst:165 -msgid "" -"`pkgcloud 1.2 or higher installed `_." -msgstr "" - -#: ../getting_started.rst:172 -msgid "" -"a recent version of `openstacksdk `_ installed." -msgstr "" - -#: ../getting_started.rst:185 -msgid "" -"`a recent version of shade library installed `_." -msgstr "" - -#: ../getting_started.rst:187 -msgid "Before proceeding, install the latest version of shade." -msgstr "" - -#: ../getting_started.rst:194 -msgid "Obtain the following information from your cloud provider:" -msgstr "" - -#: ../getting_started.rst:196 -msgid "auth URL" -msgstr "" - -#: ../getting_started.rst:197 -msgid "user name" -msgstr "" - -#: ../getting_started.rst:198 -msgid "password" -msgstr "" - -#: ../getting_started.rst:199 -msgid "project ID or name (projects are also known as tenants)" -msgstr "" - -#: ../getting_started.rst:200 -msgid "cloud region" -msgstr "" - -#: ../getting_started.rst:202 -msgid "" -"You can also download the OpenStack RC file from the OpenStack Horizon " -"dashboard. Log in to the dashboard and click :guilabel:`Project->Access & " -"Security->API Access->Download OpenStack RC file`. If you use this method, " -"be aware that the \"auth URL\" does not include the path. For example, if " -"your :file:`openrc.sh` file shows:" -msgstr "" - -#: ../getting_started.rst:212 -msgid "The actual auth URL is:" -msgstr "" - -#: ../getting_started.rst:219 -msgid "How you interact with OpenStack" -msgstr "" - -#: ../getting_started.rst:221 -msgid "" -"In this tutorial, you interact with your OpenStack cloud through the SDK " -"that you chose in \"Choose your OpenStack SDK.\" This guide assumes that you " -"know how to run code snippets in your language of choice." -msgstr "" - -#: ../getting_started.rst:234 -msgid "" -"To try it, add the following code to a Python script (or use an interactive " -"Python shell) by calling :code:`python -i`." -msgstr "" - -#: ../getting_started.rst:243 -msgid "" -"To try it out, add the following code to a Python script (or use an " -"interactive Python shell) by calling :code:`python -i`." -msgstr "" - -#: ../getting_started.rst:252 -msgid "" -"To try it, use an interactive Node.js shell by calling :code:`node` or add " -"the following code to a script." -msgstr "" - -#: ../getting_started.rst:261 -msgid "" -"To use the OpenStack .NET SDK, add the following code in the required " -"namespace section." -msgstr "" - -#: ../getting_started.rst:270 -msgid "" -"Because all service endpoints use the Identity Service for authentication " -"and authorization, place the following code in the 'void Main()' entry-point " -"function." -msgstr "" - -#: ../getting_started.rst:281 -msgid "" -"Because the tutorial reuses the :code:`conn` object, make sure that you " -"always have one handy." -msgstr "" - -#: ../getting_started.rst:286 -msgid "" -"If you receive the :code:`libcloud.common.types.InvalidCredsError: 'Invalid " -"credentials with the provider'` exception when you run one of these API " -"calls, double-check your credentials." -msgstr "" - -#: ../getting_started.rst:291 -msgid "" -"If your provider does not support regions, try a blank string ('') for the " -"`region_name`." -msgstr "" - -#: ../getting_started.rst:296 -msgid "" -"Use your credentials above to specify the cloud provider name, user name, " -"password, project_name and region_name in the file :file:`~/.config/" -"openstack/clouds.yml`." -msgstr "" - -#: ../getting_started.rst:303 -msgid "" -"If you do use a public cloud `known by shade `_, you can avoid " -"specifying :code:`auth_url:` and instead specify :code:`profile: " -"$PROVIDER_NAME` in the clouds.yml file." -msgstr "" - -#: ../getting_started.rst:308 -msgid "" -"To configure shade using a profile, use your credentials above to specify " -"the cloud provider name, username, password, project name, and region name " -"in the file :file:`~/.config/openstack/clouds.yml`." -msgstr "" - -#: ../getting_started.rst:315 -msgid "" -"See `configure shade `_, to configure your cloud using a profile." -msgstr "" - -#: ../getting_started.rst:324 -msgid "" -"If you receive the exception :code:`openstack.exceptions.HttpException: " -"HttpException: 401 Client Error: Unauthorized,` while trying to run one of " -"the following API calls please double-check your credentials." -msgstr "" - -#: ../getting_started.rst:343 -msgid "Flavors and images" -msgstr "" - -#: ../getting_started.rst:345 -msgid "" -"To run your application, you must launch an instance. This instance serves " -"as a virtual machine." -msgstr "" - -#: ../getting_started.rst:348 -msgid "" -"To launch an instance, you choose a flavor and an image. The flavor " -"represents the size of the instance, including the number of CPUs and amount " -"of RAM and disk space. An image is a prepared OS installation from which you " -"clone your instance. When you boot instances in a public cloud, larger " -"flavors can be more expensive than smaller ones in terms of resources and " -"monetary cost." -msgstr "" - -#: ../getting_started.rst:354 -msgid "" -"To list the images that are available in your cloud, run some API calls:" -msgstr "" - -#: ../getting_started.rst:369 ../getting_started.rst:382 -#: ../getting_started.rst:407 ../getting_started.rst:423 -#: ../getting_started.rst:490 ../getting_started.rst:506 -#: ../getting_started.rst:531 ../getting_started.rst:550 -#: ../getting_started.rst:643 ../getting_started.rst:655 -#: ../getting_started.rst:673 ../getting_started.rst:685 -#: ../getting_started.rst:749 ../getting_started.rst:761 -#: ../getting_started.rst:780 ../getting_started.rst:794 -#: ../getting_started.rst:876 ../getting_started.rst:900 -#: ../getting_started.rst:914 -msgid "This code returns output like this:" -msgstr "" - -#: ../getting_started.rst:453 ../getting_started.rst:582 -#: ../getting_started.rst:715 ../getting_started.rst:826 -msgid "You should see output something like this:" -msgstr "" - -#: ../getting_started.rst:475 -msgid "You can also get information about available flavors:" -msgstr "" - -#: ../getting_started.rst:611 -msgid "Your images and flavors will be different, of course." -msgstr "" - -#: ../getting_started.rst:613 -msgid "" -"Choose an image and flavor for your instance. You need about 1GB RAM, 1 CPU, " -"and a 1GB disk. This example uses the Ubuntu image with a small flavor, " -"which is a safe choice. In subsequent tutorial sections in this guide, you " -"must change the image and flavor IDs to correspond to the image and flavor " -"that you choose." -msgstr "" - -#: ../getting_started.rst:619 -msgid "" -"If the image that you want is not available in your cloud, you can usually " -"upload one depending on the policy settings of your cloud. For information " -"about how to upload images, see `obtaining images `_." -msgstr "" - -#: ../getting_started.rst:624 -msgid "" -"Set the image and size variables to appropriate values for your cloud. We " -"will use these variables in later sections." -msgstr "" - -#: ../getting_started.rst:627 -msgid "" -"First, tell the connection to get a specified image by using the ID of the " -"image that you picked in the previous section:" -msgstr "" - -#: ../getting_started.rst:734 -msgid "Next, tell the script which flavor you want to use:" -msgstr "" - -#: ../getting_started.rst:788 -msgid "Specify the flavor ID that you would like to use." -msgstr "" - -#: ../getting_started.rst:845 -msgid "Now, you can launch the instance." -msgstr "" - -#: ../getting_started.rst:848 -msgid "Launch an instance" -msgstr "" - -#: ../getting_started.rst:850 -msgid "Use your selected image and flavor to create an instance." -msgstr "" - -#: ../getting_started.rst:852 -msgid "" -"The following instance creation example assumes that you have a single-" -"tenant network. If you receive the 'Exception: 400 Bad Request Multiple " -"possible networks found, use a Network ID to be more specific' error, you " -"have multiple-tenant networks. You must add a `networks` parameter to the " -"call that creates the server. See :doc:`/appendix` for details." -msgstr "" - -#: ../getting_started.rst:859 -msgid "Create the instance." -msgstr "" - -#: ../getting_started.rst:861 -msgid "Your SDK might call an instance a 'node' or 'server'." -msgstr "" - -#: ../getting_started.rst:888 -msgid "You should see output something like:" -msgstr "" - -#: ../getting_started.rst:939 -msgid "If you list existing instances:" -msgstr "" - -#: ../getting_started.rst:988 -msgid "The new instance appears." -msgstr "" - -#: ../getting_started.rst:1100 -msgid "Before you continue, you must do one more thing." -msgstr "" - -#: ../getting_started.rst:1103 -msgid "Destroy an instance" -msgstr "" - -#: ../getting_started.rst:1105 -msgid "" -"Cloud resources, such as running instances that you no longer use, can cost " -"money. To avoid unexpected expenses, destroy cloud resources." -msgstr "" - -#: ../getting_started.rst:1154 -msgid "If you list the instances again, the instance disappears." -msgstr "" - -#: ../getting_started.rst:1156 -msgid "" -"Leave your shell open to use it for another instance deployment in this " -"section." -msgstr "" - -#: ../getting_started.rst:1160 -msgid "Deploy the application to a new instance" -msgstr "" - -#: ../getting_started.rst:1162 -msgid "" -"Now that you know how to create and delete instances, you can deploy the " -"sample application. The instance that you create for the application is " -"similar to the first instance that you created, but this time, we introduce " -"a few extra concepts." -msgstr "" - -#: ../getting_started.rst:1167 -msgid "" -"Internet connectivity from your cloud instance is required to download the " -"application." -msgstr "" - -#: ../getting_started.rst:1170 -msgid "" -"When you create an instance for the application, you want to give it a bit " -"more information than you supplied to the bare instance that you just " -"created and deleted. We will go into more detail in later sections, but for " -"now, simply create the following resources so that you can feed them to the " -"instance:" -msgstr "" - -#: ../getting_started.rst:1176 -msgid "" -"A key pair. To access your instance, you must import an SSH public key into " -"OpenStack to create a key pair. OpenStack installs this key pair on the new " -"instance. Typically, your public key is written to :code:`.ssh/id_rsa.pub`. " -"If you do not have an SSH public key file, follow `these instructions " -"`_ first. We will " -"cover these instructions in depth in :doc:`/introduction`." -msgstr "" - -#: ../getting_started.rst:1183 -msgid "" -"In the following example, set :code:`pub_key_file` to the location of your " -"public SSH key file." -msgstr "" - -#: ../getting_started.rst:1233 -msgid "" -"Network access. By default, OpenStack filters all traffic. You must create a " -"security group and apply it to your instance. The security group allows HTTP " -"and SSH access. We will go into more detail in :doc:`/introduction`." -msgstr "" - -#: ../getting_started.rst:1275 -msgid "" -"Userdata. During instance creation, you can provide userdata to OpenStack to " -"configure instances after they boot. The cloud-init service applies the user " -"data to an instance. You must pre-install the cloud-init service on your " -"chosen image. We will go into more detail in :doc:`/introduction`." -msgstr "" - -#: ../getting_started.rst:1307 -msgid "User data in openstacksdk must be encoded to Base64" -msgstr "" - -#: ../getting_started.rst:1320 -msgid "Now, you can boot and configure the instance." -msgstr "" - -#: ../getting_started.rst:1323 -msgid "Boot and configure an instance" -msgstr "" - -#: ../getting_started.rst:1325 -msgid "" -"Use the image, flavor, key pair, and userdata to create an instance. After " -"you request the instance, wait for it to build." -msgstr "" - -#: ../getting_started.rst:1349 -msgid "The shade framework can select and assign a free floating IP quickly" -msgstr "" - -#: ../getting_started.rst:1368 -msgid "" -"When the instance boots, the `ex_userdata` variable value instructs the " -"instance to deploy the Fractals application." -msgstr "" - -#: ../getting_started.rst:1372 -msgid "Associate a floating IP for external connectivity" -msgstr "" - -#: ../getting_started.rst:1374 -msgid "We cover networking in detail in :doc:`/networking`." -msgstr "" - -#: ../getting_started.rst:1376 -msgid "" -"To see the application running, you must know where to look for it. By " -"default, your instance has outbound network access. To make your instance " -"reachable from the Internet, you need an IP address. By default in some " -"cases, your instance is provisioned with a publicly rout-able IP address. In " -"this case, you see an IP address listed under `public_ips` or `private_ips` " -"when you list the instances. If not, you must create and attach a floating " -"IP address to your instance." -msgstr "" - -#: ../getting_started.rst:1392 -msgid "This gets an IP address that you can assign to your instance:" -msgstr "" - -#: ../getting_started.rst:1401 -msgid "To see whether a private IP address is assigned to your instance:" -msgstr "" - -#: ../getting_started.rst:1407 -msgid "" -"If one is assigned, users can use this address to access the instance on " -"some OpenStack clouds." -msgstr "" - -#: ../getting_started.rst:1410 -msgid "To determine whether a public IP address is assigned to your instance:" -msgstr "" - -#: ../getting_started.rst:1416 -msgid "If one is assigned, users can use this address to access the instance." -msgstr "" - -#: ../getting_started.rst:1418 -msgid "To create a floating IP address to use with your instance:" -msgstr "" - -#: ../getting_started.rst:1420 -msgid "" -"Use :code:`ex_list_floating_ip_pools()` and select the first floating IP " -"address pool. Allocate this pool to your project and use it to get a " -"floating IP address." -msgstr "" - -#: ../getting_started.rst:1428 ../getting_started.rst:1450 -#: ../getting_started.rst:1480 -msgid "This code returns the floating IP address:" -msgstr "" - -#: ../getting_started.rst:1442 -msgid "" -"Use :code:`getFloatingIps` to check for unused addresses. Select the first " -"available address. Otherwise, use :code:`allocateNewFloatingIp` to allocate " -"a floating IP to your project from the default address pool." -msgstr "" - -#: ../getting_started.rst:1456 -msgid "Attach the floating IP address to the instance:" -msgstr "" - -#: ../getting_started.rst:1470 -msgid "" -"For this example, we take a floating IP pool from the 'public' network, " -"which is your external network." -msgstr "" - -#: ../getting_started.rst:1473 -msgid "" -"List all available floating IPs for this project and select the first free " -"one. Allocate a new floating IP if none is available." -msgstr "" - -#: ../getting_started.rst:1486 -msgid "You can then attach it to the instance:" -msgstr "" - -#: ../getting_started.rst:1532 -msgid "Run the script to start the deployment." -msgstr "" - -#: ../getting_started.rst:1535 -msgid "Access the application" -msgstr "" - -#: ../getting_started.rst:1537 -msgid "" -"Deploying application data and configuration to the instance can take some " -"time. Consider enjoying a cup of coffee while you wait. After the " -"application deploys, you can use your preferred browser to visit the awesome " -"graphic interface at the following link." -msgstr "" - -#: ../getting_started.rst:1574 -msgid "" -"If you do not use floating IP addresses, substitute another IP address, as " -"appropriate." -msgstr "" - -#: ../getting_started.rst:1587 -msgid "" -"Do not worry if these concepts are not yet completely clear. In :doc:`/" -"introduction`, we explore these concepts in more detail." -msgstr "" - -#: ../getting_started.rst:1590 -msgid ":doc:`/scaling_out`: Learn how to scale your application." -msgstr "" - -#: ../getting_started.rst:1591 -msgid "" -":doc:`/durability`: Learn how to use Object Storage to make your application " -"durable." -msgstr "" - -#: ../getting_started.rst:1604 ../introduction.rst:814 -msgid "" -"The following file contains all of the code from this section of the " -"tutorial. This comprehensive code sample lets you view and run the code as a " -"single script." -msgstr "" - -#: ../getting_started.rst:1608 ../introduction.rst:818 ../scaling_out.rst:504 -msgid "" -"Before you run this script, confirm that you have set your authentication " -"information, the flavor ID, and image ID." -msgstr "" - -#: ../index.rst:3 -msgid "Writing your first OpenStack application" -msgstr "" - -#: ../index.rst:6 -msgid "Contents" -msgstr "" - -#: ../index.rst:27 -msgid "Search in this guide" -msgstr "" - -#: ../index.rst:29 -msgid ":ref:`search`" -msgstr "" - -#: ../introduction.rst:3 -msgid "Introduction to the fractals application architecture" -msgstr "" - -#: ../introduction.rst:5 -msgid "" -"This section introduces the application architecture and explains how it was " -"designed to take advantage of cloud features in general and OpenStack in " -"particular. It also describes some commands in the previous section." -msgstr "" - -#: ../introduction.rst:35 -msgid "Cloud application architecture principles" -msgstr "" - -#: ../introduction.rst:37 -msgid "" -"Cloud applications typically share several design principles. These " -"principles influenced the design of the Fractals application." -msgstr "" - -#: ../introduction.rst:45 -msgid "Modularity and micro-services" -msgstr "" - -#: ../introduction.rst:47 -msgid "" -"`Micro-services `_ are an " -"important design pattern that helps achieve application modularity. " -"Separating logical application functions into independent services " -"simplifies maintenance and re-use. Decoupling components also makes it " -"easier to selectively scale individual components, as required. Further, " -"application modularity is a required feature of applications that scale out " -"well and are fault tolerant." -msgstr "" - -#: ../introduction.rst:55 -msgid "Scalability" -msgstr "" - -#: ../introduction.rst:57 -msgid "" -"Cloud applications often use many small instances rather than a few large " -"instances. Provided that an application is sufficiently modular, you can " -"easily distribute micro-services across as many instances as required. This " -"architecture enables an application to grow past the limit imposed by the " -"maximum size of an instance. It is like trying to move a large number of " -"people from one place to another; there is only so many people you can put " -"on the largest bus, but you can use an unlimited number of buses or small " -"cars, which provide just the capacity you need - and no more." -msgstr "" - -#: ../introduction.rst:67 -msgid "Fault tolerance" -msgstr "" - -#: ../introduction.rst:69 -msgid "" -"In cloud programming, there is a well-known analogy known as \"cattle vs pets" -"\". If you have not heard it before, it goes like this:" -msgstr "" - -#: ../introduction.rst:72 -msgid "" -"When you deal with pets, you name and care for them. If they get sick, you " -"nurse them back to health, which can be difficult and very time consuming. " -"When you deal with cattle, you attach a numbered tag to their ear. If they " -"get sick, you put them down and move on." -msgstr "" - -#: ../introduction.rst:77 -msgid "" -"That, as it happens, is the new reality of programming. Applications and " -"systems used to be created on large, expensive servers, cared for by " -"operations staff dedicated to keeping them healthy. If something went wrong " -"with one of those servers, the staff's job was to do whatever it took to " -"make it right again and save the server and the application." -msgstr "" - -#: ../introduction.rst:84 -msgid "" -"In cloud programming, it is very different. Rather than large, expensive " -"servers, you have virtual machines that are disposable; if something goes " -"wrong, you shut the server down and spin up a new one. There is still " -"operations staff, but rather than nursing individual servers back to health, " -"their job is to monitor the health of the overall system." -msgstr "" - -#: ../introduction.rst:91 -msgid "" -"There are definite advantages to this architecture. It is easy to get a \"new" -"\" server, without any of the issues that inevitably arise when a server has " -"been up and running for months, or even years." -msgstr "" - -#: ../introduction.rst:95 -msgid "" -"As with classical infrastructure, failures of the underpinning cloud " -"infrastructure (hardware, networks, and software) are unavoidable. When you " -"design for the cloud, it is crucial that your application is designed for an " -"environment where failures can happen at any moment. This may sound like a " -"liability, but it is not; by designing your application with a high degree " -"of fault tolerance, you also make it resilient, and more adaptable, in the " -"face of change." -msgstr "" - -#: ../introduction.rst:103 -msgid "Fault tolerance is essential to the cloud-based application." -msgstr "" - -#: ../introduction.rst:106 -msgid "Automation" -msgstr "" - -#: ../introduction.rst:108 -msgid "" -"If an application is meant to automatically scale up and down to meet " -"demand, it is not feasible have any manual steps in the process of deploying " -"any component of the application. Automation also decreases the time to " -"recovery for your application in the event of component failures, increasing " -"fault tolerance and resilience." -msgstr "" - -#: ../introduction.rst:115 -msgid "Programmatic interfaces (APIs)" -msgstr "" - -#: ../introduction.rst:117 -msgid "" -"Like many cloud applications, the Fractals application has a `RESTful API " -"`_. You can " -"connect to it directly and generate fractals, or you can integrate it as a " -"component of a larger application. Any time a standard interface such as an " -"API is available, automated testing becomes much more feasible, increasing " -"software quality." -msgstr "" - -#: ../introduction.rst:125 -msgid "Fractals application architecture" -msgstr "" - -#: ../introduction.rst:127 -msgid "" -"The Fractals application was designed with the principles of the previous " -"subsection in mind. You will note that in :doc:`getting_started`, we " -"deployed the application in an all-in-one style, on a single virtual " -"machine. This is not a good practice, but because the application uses micro-" -"services to decouple logical application functions, we can change this " -"easily." -msgstr "" - -#: ../introduction.rst:135 -msgid "" -"Message queues are used to facilitate communication between the Fractal " -"application services. The Fractal application uses a `work queue `_ (or task queue) to " -"distribute tasks to the worker services." -msgstr "" - -#: ../introduction.rst:140 -msgid "" -"Message queues work in a way similar to a queue (or a line, for those of us " -"on the other side of the ocean) in a bank being served by multiple clerks. " -"The message queue in our application provides a feed of work requests that " -"can be taken one-at-a-time by worker services, whether there is a single " -"worker service or hundreds of them." -msgstr "" - -#: ../introduction.rst:146 -msgid "" -"This is a `useful pattern `_ for many cloud applications that have long lists of requests coming " -"in and a pool of resources from which to service them. This also means that " -"a worker may crash and the tasks will be processed by other workers." -msgstr "" - -#: ../introduction.rst:151 -msgid "" -"The `RabbitMQ getting started tutorial `_ provides a great introduction to message queues." -msgstr "" - -#: ../introduction.rst:157 -msgid "" -"The worker service consumes messages from the work queue and then processes " -"them to create the corresponding fractal image file." -msgstr "" - -#: ../introduction.rst:160 -msgid "" -"Of course there is also a web interface which offers a more human friendly " -"way of accessing the API to view the created fractal images, and a simple " -"command line interface." -msgstr "" - -#: ../introduction.rst:172 -msgid "" -"There are also multiple storage back ends (to store the generated fractal " -"images) and a database component (to store the state of tasks), but we will " -"talk about those in :doc:`/durability` and :doc:`/block_storage` " -"respectively." -msgstr "" - -#: ../introduction.rst:178 -msgid "How the Fractals application interacts with OpenStack" -msgstr "" - -#: ../introduction.rst:191 -msgid "The magic revisited" -msgstr "" - -#: ../introduction.rst:193 -msgid "" -"So what exactly was that request doing at the end of the previous section? " -"Let us look at it again. In this subsection, we are just explaining what you " -"have already done in the previous section; you do not need to run these " -"commands again." -msgstr "" - -#: ../introduction.rst:223 -msgid "" -"We explained image and flavor in :doc:`getting_started`, so in the following " -"sections, we will explain the other parameters in detail, including :code:" -"`ex_userdata` (cloud-init) and :code:`ex_keyname` (key pairs)." -msgstr "" - -#: ../introduction.rst:229 -msgid "" -"In openstacksdk parameter :code:`ex_userdata` is called :code:`user_data` " -"and parameter :code:`ex_keyname` is called :code:`key_name`." -msgstr "" - -#: ../introduction.rst:234 -msgid "Introduction to cloud-init" -msgstr "" - -#: ../introduction.rst:236 -msgid "" -"`cloud-init `_ is a tool that " -"performs instance configuration tasks during the boot of a cloud instance, " -"and comes installed on most cloud images. :code:`ex_userdata`, which was " -"passed to :code:`create_node`, is the configuration data passed to cloud-" -"init." -msgstr "" - -#: ../introduction.rst:242 -msgid "" -"In this case, we are presenting a shell script as the `userdata `_. " -"When :code:`create_node` creates the instance, :code:`cloud-init` executes " -"the shell script in the :code:`userdata` variable." -msgstr "" - -#: ../introduction.rst:247 -msgid "" -"When an SSH public key is provided during instance creation, cloud-init " -"installs this key on a user account. (The user name varies between cloud " -"images.) See the `Obtaining Images `_ section of the image guide for guidance about which " -"user name you should use when SSHing. If you still have problems logging in, " -"ask your cloud provider to confirm the user name." -msgstr "" - -#: ../introduction.rst:279 -msgid "User data in openstacksdk must be encoded to Base64." -msgstr "" - -#: ../introduction.rst:281 -msgid "" -"After the instance is created, cloud-init downloads and runs a script " -"called :code:`install.sh`. This script installs the Fractals application. " -"Cloud-init can consume bash scripts and a number of different types of data. " -"You can even provide multiple types of data. You can find more information " -"about cloud-init in the `official documentation `_." -msgstr "" - -#: ../introduction.rst:288 -msgid "Introduction to key pairs" -msgstr "" - -#: ../introduction.rst:290 -msgid "" -"Security is important when it comes to your instances; you can not have just " -"anyone accessing them. To enable logging into an instance, you must provide " -"the public key of an SSH key pair during instance creation. In section one, " -"you created and uploaded a key pair to OpenStack, and cloud-init installed " -"it for the user account." -msgstr "" - -#: ../introduction.rst:296 -msgid "" -"Even with a key in place, however, you must have the appropriate security " -"group rules in place to access your instance." -msgstr "" - -#: ../introduction.rst:300 -msgid "Introduction to security groups" -msgstr "" - -#: ../introduction.rst:302 -msgid "" -"Security groups are sets of network access rules that are applied to an " -"instance's networking. By default, only egress (outbound) traffic is " -"allowed. You must explicitly enable ingress (inbound) network access by " -"creating a security group rule." -msgstr "" - -#: ../introduction.rst:307 -msgid "" -"Removing the egress rule created by OpenStack will cause your instance " -"networking to break." -msgstr "" - -#: ../introduction.rst:310 -msgid "" -"Start by creating a security group for the all-in-one instance and adding " -"the appropriate rules, such as HTTP (TCP port 80) and SSH (TCP port 22):" -msgstr "" - -#: ../introduction.rst:333 -msgid "" -":code:`ex_create_security_group_rule()` takes ranges of ports as input. This " -"is why ports 80 and 22 are passed twice." -msgstr "" - -#: ../introduction.rst:343 -msgid "You can list available security groups with:" -msgstr "" - -#: ../introduction.rst:370 -msgid "Once you have created a rule or group, you can also delete it:" -msgstr "" - -#: ../introduction.rst:397 -msgid "To see which security groups apply to an instance, you can:" -msgstr "" - -#: ../introduction.rst:426 -msgid "" -"Once you have configured permissions, you must know where to access the " -"application." -msgstr "" - -#: ../introduction.rst:430 -msgid "Introduction to Floating IPs" -msgstr "" - -#: ../introduction.rst:432 -msgid "" -"As in traditional IT, cloud instances are accessed through IP addresses that " -"OpenStack assigns. How this is actually done depends on the networking setup " -"for your cloud. In some cases, you will simply get an Internet rout-able IP " -"address assigned directly to your instance." -msgstr "" - -#: ../introduction.rst:437 -msgid "" -"The most common way for OpenStack clouds to allocate Internet rout-able IP " -"addresses to instances, however, is through the use of floating IPs. A " -"floating IP is an address that exists as an entity unto itself, and can be " -"associated to a specific instance network interface. When a floating IP " -"address is associated to an instance network interface, OpenStack re-directs " -"traffic bound for that address to the address of the instance's internal " -"network interface address. Your cloud provider will generally offer pools of " -"floating IPs for your use." -msgstr "" - -#: ../introduction.rst:447 -msgid "" -"To use a floating IP, you must first allocate an IP to your project, then " -"associate it to your instance's network interface." -msgstr "" - -#: ../introduction.rst:452 -msgid "" -"Allocating a floating IP address to an instance does not change the IP " -"address of the instance, it causes OpenStack to establish the network " -"translation rules to allow an *additional* IP address." -msgstr "" - -#: ../introduction.rst:462 ../introduction.rst:484 -msgid "" -"If you have no free floating IPs that have been previously allocated for " -"your project, first select a floating IP pool offered by your provider. In " -"this example, we have selected the first one and assume that it has " -"available IP addresses." -msgstr "" - -#: ../introduction.rst:471 ../introduction.rst:493 -msgid "" -"Now request that an address from this pool be allocated to your project." -msgstr "" - -#: ../introduction.rst:512 -msgid "" -"If you have no free floating IPs that have been allocated for your project, " -"first select a network which offer allocation of floating IPs. In this " -"example we use network which is called :code:`public`." -msgstr "" - -#: ../introduction.rst:521 -msgid "" -"Now request an address from this network to be allocated to your project." -msgstr "" - -#: ../introduction.rst:527 -msgid "" -"Now that you have an unused floating IP address allocated to your project, " -"attach it to an instance." -msgstr "" - -#: ../introduction.rst:555 -msgid "" -"That brings us to where we ended up at the end of :doc:`/getting_started`. " -"But where do we go from here?" -msgstr "" - -#: ../introduction.rst:559 -msgid "Splitting services across multiple instances" -msgstr "" - -#: ../introduction.rst:561 -msgid "" -"We have talked about separating functions into different micro-services, and " -"how that enables us to make use of the cloud architecture. Now let us see " -"that in action." -msgstr "" - -#: ../introduction.rst:565 -msgid "" -"The rest of this tutorial will not reference the all-in-one instance you " -"created in section one. Take a moment to delete this instance." -msgstr "" - -#: ../introduction.rst:568 -msgid "" -"It is easy to split out services into multiple instances. We will create a " -"controller instance called :code:`app-controller`, which hosts the API, " -"database, and messaging services. We will also create a worker instance " -"called :code:`app-worker-1`, which just generates fractals." -msgstr "" - -#: ../introduction.rst:574 -msgid "" -"The first step is to start the controller instance. The instance has the API " -"service, the database, and the messaging service, as you can see from the " -"parameters passed to the installation script." -msgstr "" - -#: ../introduction.rst:579 ../introduction.rst:655 -msgid "Parameter" -msgstr "" - -#: ../introduction.rst:579 -msgid "Values" -msgstr "" - -#: ../introduction.rst:581 -msgid ":code:`-i`" -msgstr "" - -#: ../introduction.rst:581 -msgid "" -":code:`messaging` (install RabbitMQ) and :code:`faafo` (install the Faafo " -"app)." -msgstr "" - -#: ../introduction.rst:581 -msgid "Install a service" -msgstr "" - -#: ../introduction.rst:582 -msgid ":code:`-r`" -msgstr "" - -#: ../introduction.rst:582 -msgid "" -":code:`api` (enable and start the API service), :code:`worker` (enable and " -"start the worker service), and :code:`demo` (run the demo mode to request " -"random fractals)." -msgstr "" - -#: ../introduction.rst:582 -msgid "Enable/start something" -msgstr "" - -#: ../introduction.rst:613 -msgid "" -"Note that this time, when you create a security group, you include a rule " -"that applies to only instances that are part of the worker group." -msgstr "" - -#: ../introduction.rst:616 -msgid "Next, start a second instance, which will be the worker instance:" -msgstr "" - -#: ../introduction.rst:645 -msgid "" -"Notice that you have added this instance to the worker_group, so it can " -"access the controller." -msgstr "" - -#: ../introduction.rst:648 -msgid "" -"As you can see from the parameters passed to the installation script, you " -"define this instance as the worker instance. But, you also pass the address " -"of the API instance and the message queue so the worker can pick up " -"requests. The Fractals application installation script accepts several " -"parameters." -msgstr "" - -#: ../introduction.rst:655 -msgid "Example" -msgstr "" - -#: ../introduction.rst:657 -msgid ":code:`-e`" -msgstr "" - -#: ../introduction.rst:657 -msgid "The endpoint URL of the API service." -msgstr "" - -#: ../introduction.rst:657 -msgid "http://localhost/" -msgstr "" - -#: ../introduction.rst:658 -msgid ":code:`-m`" -msgstr "" - -#: ../introduction.rst:658 -msgid "The transport URL of the messaging service." -msgstr "" - -#: ../introduction.rst:658 -msgid "amqp://guest:guest@localhost:5672/" -msgstr "" - -#: ../introduction.rst:659 -msgid ":code:`-d`" -msgstr "" - -#: ../introduction.rst:659 -msgid "The connection URL for the database (not used here)." -msgstr "" - -#: ../introduction.rst:659 -msgid "sqlite:////tmp/sqlite.db" -msgstr "" - -#: ../introduction.rst:662 -msgid "" -"Now if you make a request for a new fractal, you connect to the controller " -"instance, :code:`app-controller`, but the work will actually be performed by " -"a separate worker instance - :code:`app-worker-1`." -msgstr "" - -#: ../introduction.rst:668 -msgid "Login with SSH and use the Fractal app" -msgstr "" - -#: ../introduction.rst:670 -msgid "" -"Login to the worker instance, :code:`app-worker-1`, with SSH, using the " -"previous added SSH key pair \"demokey\". Start by getting the IP address of " -"the worker:" -msgstr "" - -#: ../introduction.rst:699 -msgid "Now you can SSH into the instance:" -msgstr "" - -#: ../introduction.rst:705 -msgid "" -"Replace :code:`IP_WORKER_1` with the IP address of the worker instance and " -"USERNAME to the appropriate user name." -msgstr "" - -#: ../introduction.rst:708 -msgid "" -"Once you have logged in, check to see whether the worker service process is " -"running as expected. You can find the logs of the worker service in the " -"directory :code:`/var/log/supervisor/`." -msgstr "" - -#: ../introduction.rst:717 -msgid "" -"Open :code:`top` to monitor the CPU usage of the :code:`faafo-worker` " -"process." -msgstr "" - -#: ../introduction.rst:719 -msgid "" -"Now log into the controller instance, :code:`app-controller`, also with SSH, " -"using the previously added SSH key pair \"demokey\"." -msgstr "" - -#: ../introduction.rst:726 -msgid "" -"Replace :code:`IP_CONTROLLER` with the IP address of the controller instance " -"and USERNAME to the appropriate user name." -msgstr "" - -#: ../introduction.rst:729 -msgid "" -"Check to see whether the API service process is running like expected. You " -"can find the logs for the API service in the directory :file:`/var/log/" -"supervisor/`." -msgstr "" - -#: ../introduction.rst:738 -msgid "" -"Now call the Fractal application's command line interface (:code:`faafo`) to " -"request a few new fractals. The following command requests a few fractals " -"with random parameters:" -msgstr "" - -#: ../introduction.rst:747 -msgid "" -"Watch :code:`top` on the worker instance. Right after calling :code:`faafo` " -"the :code:`faafo-worker` process should start consuming a lot of CPU cycles." -msgstr "" - -#: ../introduction.rst:756 -msgid "" -"To show the details of a specific fractal use the subcommand :code:`show` of " -"the Faafo CLI." -msgstr "" - -#: ../introduction.rst:777 -msgid "" -"There are more commands available; find out more details about them with :" -"code:`faafo get --help`, :code:`faafo list --help`, and :code:`faafo delete " -"--help`." -msgstr "" - -#: ../introduction.rst:781 -msgid "" -"The application stores the generated fractal images directly in the database " -"used by the API service instance. Storing image files in a database is not " -"good practice. We are doing it here as an example only as an easy way to " -"enable multiple instances to have access to the data. For best practice, we " -"recommend storing objects in Object Storage, which is covered in :doc:" -"`durability`." -msgstr "" - -#: ../introduction.rst:792 -msgid "" -"You should now have a basic understanding of the architecture of cloud-based " -"applications. In addition, you have had practice starting new instances, " -"automatically configuring them at boot, and even modularizing an application " -"so that you may use multiple instances to run it. These are the basic steps " -"for requesting and using compute resources in order to run your application " -"on an OpenStack cloud." -msgstr "" - -#: ../introduction.rst:800 -msgid "" -"From here, go to :doc:`/scaling_out` to learn how to further scale your " -"application. Or, try one of these steps in the tutorial:" -msgstr "" - -#: ../introduction.rst:803 -msgid "" -":doc:`/durability`: Learn how to use Object Storage to make your application " -"more durable." -msgstr "" - -#: ../networking.rst:3 -msgid "Networking" -msgstr "" - -#: ../networking.rst:8 -msgid "" -"In previous chapters, all nodes that comprise the fractal application were " -"attached to the same network." -msgstr "" - -#: ../networking.rst:11 -msgid "" -"This chapter introduces the Networking API. This will enable us to build " -"networking topologies that separate public traffic accessing the application " -"from traffic between the API and the worker components. We also introduce " -"load balancing for resilience, and create a secure back-end network for " -"communication between the database, web server, file storage, and worker " -"components." -msgstr "" - -#: ../networking.rst:18 -msgid "" -"This section assumes that your cloud provider has implemented the OpenStack " -"Networking API (neutron). Users of clouds which have implemented legacy " -"networking (nova-network) will have access to networking via the Compute " -"API. Log in to the Horizon dashboard and navigate to :guilabel:`Project-" -">Access & Security->API Access`. If you see a service endpoint for the " -"Network API, your cloud is most likely running the Networking API. If you " -"are still in doubt, ask your cloud provider for more information." -msgstr "" - -#: ../networking.rst:29 -msgid "This section has not yet been completed for the .NET SDK" -msgstr "" - -#: ../networking.rst:33 -msgid "" -"fog `supports `_ the OpenStack Networking API, but this section has not yet been " -"completed." -msgstr "" - -#: ../networking.rst:40 -msgid "" -"jClouds supports the OpenStack Networking API, but section has not yet been " -"completed. Please see `this `_ in the meantime." -msgstr "" - -#: ../networking.rst:47 -msgid "Libcloud does not support the OpenStack Networking API." -msgstr "" - -#: ../networking.rst:51 -msgid "" -"Pkgcloud supports the OpenStack Networking API, but this section has not " -"been completed." -msgstr "" - -#: ../networking.rst:64 -msgid "Work with the CLI" -msgstr "" - -#: ../networking.rst:66 -msgid "" -"Because the SDKs do not fully support the OpenStack Networking API, this " -"section uses the command-line clients." -msgstr "" - -#: ../networking.rst:69 -msgid "" -"Use this guide to install the 'neutron' command-line client: http://docs." -"openstack.org/cli-reference/common/" -"cli_install_openstack_command_line_clients.html#install-the-clients" -msgstr "" - -#: ../networking.rst:72 ../orchestration.rst:51 -msgid "" -"Use this guide to set up the necessary variables for your cloud in an " -"'openrc' file: http://docs.openstack.org/cli-reference/common/" -"cli_set_environment_variables_using_openstack_rc.html" -msgstr "" - -#: ../networking.rst:76 -msgid "" -"Ensure you have an openrc.sh file, source it, and then check that your " -"neutron client works: ::" -msgstr "" - -#: ../networking.rst:92 -msgid "Networking segmentation" -msgstr "" - -#: ../networking.rst:94 -msgid "" -"In traditional data centers, network segments are dedicated to specific " -"types of network traffic." -msgstr "" - -#: ../networking.rst:97 -msgid "" -"The fractal application we are building contains these types of network " -"traffic:" -msgstr "" - -#: ../networking.rst:100 -msgid "public-facing web traffic" -msgstr "" - -#: ../networking.rst:101 -msgid "API traffic" -msgstr "" - -#: ../networking.rst:102 -msgid "internal worker traffic" -msgstr "" - -#: ../networking.rst:104 -msgid "" -"For performance reasons, it makes sense to have a network for each tier, so " -"that traffic from one tier does not \"crowd out\" other types of traffic and " -"cause the application to fail. In addition, having separate networks makes " -"controlling access to parts of the application easier to manage, improving " -"the overall security of the application." -msgstr "" - -#: ../networking.rst:110 -msgid "" -"Prior to this section, the network layout for the Fractal application would " -"be similar to the following diagram:" -msgstr "" - -#: ../networking.rst:133 -msgid "" -"In this network layout, we assume that the OpenStack cloud in which you have " -"been building your application has a public network and tenant router that " -"was previously created by your cloud provider or by yourself, following the " -"instructions in the appendix." -msgstr "" - -#: ../networking.rst:138 -msgid "" -"Many of the network concepts that are discussed in this section are already " -"present in the diagram above. A tenant router provides routing and external " -"access for the worker nodes, and floating IP addresses are associated with " -"each node in the Fractal application cluster to facilitate external access." -msgstr "" - -#: ../networking.rst:144 -msgid "" -"At the end of this section, you make some slight changes to the networking " -"topology by using the OpenStack Networking API to create the 10.0.1.0/24 " -"network to which the worker nodes attach. You use the 10.0.3.0/24 API " -"network to attach the Fractal API servers. Web server instances have their " -"own 10.0.2.0/24 network, which is accessible by fractal aficionados " -"worldwide, by allocating floating IPs from the public network." -msgstr "" - -#: ../networking.rst:183 -msgid "Introduction to tenant networking" -msgstr "" - -#: ../networking.rst:185 -msgid "" -"With the OpenStack Networking API, the workflow for creating a network " -"topology that separates the public-facing Fractals app API from the worker " -"back end is as follows:" -msgstr "" - -#: ../networking.rst:189 -msgid "Create a network and subnet for the web server nodes." -msgstr "" - -#: ../networking.rst:191 -msgid "" -"Create a network and subnet for the worker nodes. This is the private data " -"network." -msgstr "" - -#: ../networking.rst:193 -msgid "Create a router for the private data network." -msgstr "" - -#: ../networking.rst:195 -msgid "Allocate floating ips and assign them to the web server nodes." -msgstr "" - -#: ../networking.rst:198 -msgid "Create networks" -msgstr "" - -#: ../networking.rst:200 -msgid "" -"Most cloud providers make a public network accessible to you. We will attach " -"a router to this public network to grant Internet access to our instances. " -"After also attaching this router to our internal networks, we will allocate " -"floating IPs from the public network for instances which need to be accessed " -"from the Internet." -msgstr "" - -#: ../networking.rst:206 -msgid "" -"Confirm that we have a public network by listing the networks our tenant has " -"access to. The public network does not have to be named public - it could be " -"'external', 'net04_ext' or something else - the important thing is it exists " -"and can be used to reach the Internet." -msgstr "" - -#: ../networking.rst:221 -msgid "Next, create a network and subnet for the workers." -msgstr "" - -#: ../networking.rst:260 -msgid "Now, create a network and subnet for the web servers." -msgstr "" - -#: ../networking.rst:300 -msgid "Next, create a network and subnet for the API servers." -msgstr "" - -#: ../networking.rst:340 -msgid "" -"Now that you have got the networks created, go ahead and create two Floating " -"IPs, for web servers. Ensure that you replace 'public' with the name of the " -"public/external network offered by your cloud provider." -msgstr "" - -#: ../networking.rst:376 -msgid "" -"The world is running out of IPv4 addresses. If you get the \"No more IP " -"addresses available on network\" error, contact your cloud administrator. " -"You may also want to ask about IPv6 :)" -msgstr "" - -#: ../networking.rst:383 -msgid "Connecting to the Internet" -msgstr "" - -#: ../networking.rst:385 -msgid "" -"Most instances require access to the Internet. The instances in your " -"Fractals app are no exception! Add routers to pass traffic between the " -"various networks that you use." -msgstr "" - -#: ../networking.rst:405 -msgid "" -"Specify an external gateway for your router to tell OpenStack which network " -"to use for Internet access." -msgstr "" - -#: ../networking.rst:428 -msgid "Now, attach your router to the worker, API, and web server subnets." -msgstr "" - -#: ../networking.rst:442 -msgid "Booting a worker" -msgstr "" - -#: ../networking.rst:444 -msgid "" -"Now that you have prepared the networking infrastructure, you can go ahead " -"and boot an instance on it. Ensure you use appropriate flavor and image " -"values for your cloud - see :doc:`getting_started` if you have not already." -msgstr "" - -#: ../networking.rst:487 -msgid "Load balancing" -msgstr "" - -#: ../networking.rst:489 -msgid "" -"After separating the Fractal worker nodes into their own networks, the next " -"logical step is to move the Fractal API service to a load balancer, so that " -"multiple API workers can handle requests. By using a load balancer, the API " -"service can be scaled out in a similar fashion to the worker nodes." -msgstr "" - -#: ../networking.rst:496 -msgid "Neutron LbaaS API" -msgstr "" - -#: ../networking.rst:498 -msgid "" -"This section is based on the Neutron LBaaS API version 1.0 http://docs." -"openstack.org/admin-guide/networking_adv-features.html#basic-load-balancer-" -"as-a-service-operations" -msgstr "" - -#: ../networking.rst:505 -msgid "" -"The OpenStack Networking API provides support for creating loadbalancers, " -"which can be used to scale the Fractal app web service. In the following " -"example, we create two compute instances via the Compute API, then " -"instantiate a load balancer that will use a virtual IP (VIP) for accessing " -"the web service offered by the two compute nodes. The end result will be the " -"following network topology:" -msgstr "" - -#: ../networking.rst:530 -msgid "" -"libcloud support added 0.14: https://developer.rackspace.com/blog/libcloud-0-" -"dot-14-released/" -msgstr "" - -#: ../networking.rst:533 -msgid "Start by looking at what is already in place." -msgstr "" - -#: ../networking.rst:545 -msgid "Go ahead and create two instances." -msgstr "" - -#: ../networking.rst:581 -msgid "Confirm that they were added:" -msgstr "" - -#: ../networking.rst:593 -msgid "Look at which ports are available:" -msgstr "" - -#: ../networking.rst:607 -msgid "" -"Next, create additional floating IPs. Specify the fixed IP addresses they " -"should point to and the ports that they should use:" -msgstr "" - -#: ../networking.rst:641 -msgid "" -"You are ready to create members for the load balancer pool, which reference " -"the floating IPs:" -msgstr "" - -#: ../networking.rst:678 -msgid "You should be able to see them in the member list:" -msgstr "" - -#: ../networking.rst:690 -msgid "" -"Now, create a health monitor that will ensure that members of the load " -"balancer pool are active and able to respond to requests. If a member in the " -"pool dies or is unresponsive, the member is removed from the pool so that " -"client requests are routed to another active member." -msgstr "" - -#: ../networking.rst:717 -msgid "" -"Now create a virtual IP that will be used to direct traffic between the " -"various members of the pool:" -msgstr "" - -#: ../networking.rst:744 -msgid "And confirm it is in place:" -msgstr "" - -#: ../networking.rst:755 -msgid "Now, look at the big picture." -msgstr "" - -#: ../networking.rst:758 -msgid "Final result" -msgstr "" - -#: ../networking.rst:760 -msgid "" -"With the addition of the load balancer, the Fractal app's networking " -"topology now reflects the modular nature of the application itself." -msgstr "" - -#: ../networking.rst:799 -msgid "" -"You should now be fairly confident working with the Network API. To see " -"calls that we did not cover, see the volume documentation of your SDK, or " -"try one of these tutorial steps:" -msgstr "" - -#: ../orchestration.rst:3 -msgid "Orchestration" -msgstr "" - -#: ../orchestration.rst:5 -msgid "" -"This chapter explains the importance of durability and scalability for your " -"cloud-based applications. In most cases, really achieving these qualities " -"means automating tasks such as scaling and other operational tasks." -msgstr "" - -#: ../orchestration.rst:10 -msgid "" -"The Orchestration service provides a template-based way to describe a cloud " -"application, then coordinates running the needed OpenStack API calls to run " -"cloud applications. The templates enable you to create most OpenStack " -"resource types, such as instances, networking information, volumes, security " -"groups, and even users. It also provides more advanced functionality, such " -"as instance high availability, instance auto-scaling, and nested stacks." -msgstr "" - -#: ../orchestration.rst:18 -msgid "" -"The OpenStack Orchestration API uses the stacks, resources, and templates " -"constructs." -msgstr "" - -#: ../orchestration.rst:21 -msgid "" -"You create stacks from templates, which contain resources. Resources are an " -"abstraction in the HOT (Heat Orchestration Template) template language, " -"which enables you to define different cloud resources by setting the :code:" -"`type` attribute." -msgstr "" - -#: ../orchestration.rst:26 -msgid "" -"For example, you might use the Orchestration API to create two compute " -"instances by creating a stack and by passing a template to the Orchestration " -"API. That template contains two resources with the :code:`type` attribute " -"set to :code:`OS::Nova::Server`." -msgstr "" - -#: ../orchestration.rst:31 -msgid "" -"That example is simplistic, of course, but the flexibility of the resource " -"object enables the creation of templates that contain all the required cloud " -"infrastructure to run an application, such as load balancers, block storage " -"volumes, compute instances, networking topology, and security policies." -msgstr "" - -#: ../orchestration.rst:36 -msgid "" -"The Orchestration service is not deployed by default in every cloud. If " -"these commands do not work, it means the Orchestration API is not available; " -"ask your support team for assistance." -msgstr "" - -#: ../orchestration.rst:40 -msgid "" -"This section introduces the `HOT templating language `_, and takes you through " -"some common OpenStack Orchestration calls." -msgstr "" - -#: ../orchestration.rst:44 -msgid "" -"In previous sections, you used your SDK to programatically interact with " -"OpenStack. In this section, you use the 'heat' command-line client to access " -"the Orchestration API directly through template files." -msgstr "" - -#: ../orchestration.rst:48 -msgid "" -"Install the 'heat' command-line client by following this guide: http://docs." -"openstack.org/cli-reference/common/" -"cli_install_openstack_command_line_clients.html#install-the-clients" -msgstr "" - -#: ../orchestration.rst:57 -msgid "the .NET SDK does not currently support OpenStack Orchestration." -msgstr "" - -#: ../orchestration.rst:61 -msgid "" -"fog `does support OpenStack Orchestration `_." -msgstr "" - -#: ../orchestration.rst:66 -msgid "" -"Jclouds does not currently support OpenStack Orchestration. See this `bug " -"report `_." -msgstr "" - -#: ../orchestration.rst:71 -msgid "libcloud does not currently support OpenStack Orchestration." -msgstr "" - -#: ../orchestration.rst:75 -msgid "" -"Pkgcloud supports OpenStack Orchestration :D:D:D but this section is `not " -"written yet `_" -msgstr "" - -#: ../orchestration.rst:80 -msgid "The OpenStack SDK does not currently support OpenStack Orchestration." -msgstr "" - -#: ../orchestration.rst:87 -msgid "HOT templating language" -msgstr "" - -#: ../orchestration.rst:89 -msgid "" -"To learn about the template syntax for OpenStack Orchestration, how to " -"create basic templates, and their inputs and outputs, see `Heat " -"Orchestration Template (HOT) Guide `_." -msgstr "" - -#: ../orchestration.rst:94 -msgid "Work with stacks: Basics" -msgstr "" - -#: ../orchestration.rst:96 -msgid "**Stack create**" -msgstr "" - -#: ../orchestration.rst:98 -msgid "" -"The `hello_faafo `_ Hot template demonstrates how to " -"create a compute instance that builds and runs the Fractal application as an " -"all-in-one installation." -msgstr "" - -#: ../orchestration.rst:103 -msgid "You pass in these configuration settings as parameters:" -msgstr "" - -#: ../orchestration.rst:105 -msgid "The flavor" -msgstr "" - -#: ../orchestration.rst:106 -msgid "Your ssh key name" -msgstr "" - -#: ../orchestration.rst:107 -msgid "The unique identifier (UUID) of the image" -msgstr "" - -#: ../orchestration.rst:120 -msgid "The stack automatically creates a Nova instance, as follows:" -msgstr "" - -#: ../orchestration.rst:131 -msgid "Verify that the stack was successfully created:" -msgstr "" - -#: ../orchestration.rst:142 -msgid "" -"The stack reports an initial :code:`CREATE_IN_PROGRESS` status. When all " -"software is installed, the status changes to :code:`CREATE_COMPLETE`." -msgstr "" - -#: ../orchestration.rst:145 -msgid "" -"You might have to run the :code:`stack-list` command a few times before the " -"stack creation is complete." -msgstr "" - -#: ../orchestration.rst:148 -msgid "**Show information about the stack**" -msgstr "" - -#: ../orchestration.rst:150 -msgid "Get more information about the stack:" -msgstr "" - -#: ../orchestration.rst:156 -msgid "" -"The `outputs` property shows the URL through which you can access the " -"Fractal application. You can SSH into the instance." -msgstr "" - -#: ../orchestration.rst:159 -msgid "**Remove the stack**" -msgstr "" - -#: ../orchestration.rst:170 -msgid "Verify the nova instance was deleted when the stack was removed:" -msgstr "" - -#: ../orchestration.rst:180 -msgid "" -"While this stack starts a single instance that builds and runs the Fractal " -"application as an all-in-one installation, you can make very complicated " -"templates that impact dozens of instances or that add and remove instances " -"on demand. Continue to the next section to learn more." -msgstr "" - -#: ../orchestration.rst:185 -msgid "Work with stacks: Advanced" -msgstr "" - -#: ../orchestration.rst:187 -msgid "" -"With the Orchestration API, the Fractal application can create an auto-" -"scaling group for all parts of the application, to dynamically provision " -"more compute resources during periods of heavy utilization, and also " -"terminate compute instances to scale down, as demand decreases." -msgstr "" - -#: ../orchestration.rst:192 -msgid "" -"To learn about auto-scaling with the Orchestration API, read these articles:" -msgstr "" - -#: ../orchestration.rst:194 -msgid "" -"http://superuser.openstack.org/articles/simple-auto-scaling-environment-with-" -"heat" -msgstr "" - -#: ../orchestration.rst:195 -msgid "" -"http://superuser.openstack.org/articles/understanding-openstack-heat-auto-" -"scaling" -msgstr "" - -#: ../orchestration.rst:197 -msgid "" -"Initially, the focus is on scaling the workers because they consume the most " -"resources." -msgstr "" - -#: ../orchestration.rst:200 -msgid "" -"The example template depends on the ceilometer project, which is part of the " -"`Telemetry service `_." -msgstr "" - -#: ../orchestration.rst:203 -msgid "" -"The Telemetry service is not deployed by default in every cloud. If the " -"ceilometer commands do not work, this example does not work; ask your " -"support team for assistance." -msgstr "" - -#: ../orchestration.rst:207 -msgid "" -"To better understand how the template works, use this guide to install the " -"'ceilometer' command-line client:" -msgstr "" - -#: ../orchestration.rst:210 -msgid "" -"http://docs.openstack.org/cli-reference/common/" -"cli_install_openstack_command_line_clients.html#install-the-clients" -msgstr "" - -#: ../orchestration.rst:212 -msgid "" -"To set up the necessary variables for your cloud in an 'openrc' file, use " -"this guide:" -msgstr "" - -#: ../orchestration.rst:215 -msgid "" -"http://docs.openstack.org/cli-reference/common/" -"cli_set_environment_variables_using_openstack_rc.html" -msgstr "" - -#: ../orchestration.rst:217 -msgid "" -"The Telemetry service uses meters to measure a given aspect of a resources " -"usage. The meter that we are interested in is the :code:`cpu_util` meter." -msgstr "" - -#: ../orchestration.rst:220 -msgid "The value of a meter is regularly sampled and saved with a timestamp." -msgstr "" - -#: ../orchestration.rst:222 -msgid "" -"These saved samples are aggregated to produce a statistic. The statistic " -"that we are interested in is **avg**: the average of the samples over a " -"given period." -msgstr "" - -#: ../orchestration.rst:225 -msgid "" -"We are interested because the Telemetry service supports alarms: an alarm is " -"fired when our average statistic breaches a configured threshold. When the " -"alarm fires, an associated action is performed." -msgstr "" - -#: ../orchestration.rst:229 -msgid "" -"The stack we will be building uses the firing of alarms to control the " -"addition or removal of worker instances." -msgstr "" - -#: ../orchestration.rst:232 -msgid "To verify that ceilometer is installed, list the known meters:" -msgstr "" - -#: ../orchestration.rst:238 -msgid "" -"This command returns a very long list of meters. Once a meter is created, it " -"is never thrown away!" -msgstr "" - -#: ../orchestration.rst:241 -msgid "Launch the stack with auto-scaling workers:" -msgstr "" - -#: ../orchestration.rst:256 -msgid "As before, pass in configuration settings as parameters." -msgstr "" - -#: ../orchestration.rst:258 -msgid "And as before, the stack takes a few minutes to build!" -msgstr "" - -#: ../orchestration.rst:260 -msgid "Wait for it to reach the :code:`CREATE_COMPLETE` status:" -msgstr "" - -#: ../orchestration.rst:271 -msgid "" -"Run the :code:`nova list` command. This template created three instances:" -msgstr "" - -#: ../orchestration.rst:284 -msgid "" -"Note that the worker instance is part of an :code:`OS::Heat::" -"AutoScalingGroup`." -msgstr "" - -#: ../orchestration.rst:286 -msgid "Confirm that the stack created two alarms:" -msgstr "" - -#: ../orchestration.rst:298 -msgid "" -"If either alarm reports the :code:`insufficient data` state, the default " -"sampling period of the stack is probably too low for your cloud; ask your " -"support team for assistance. You can set the period through the :code:" -"`period` parameter of the stack to match your clouds requirements." -msgstr "" - -#: ../orchestration.rst:304 -msgid "Use the stack ID to get more information about the stack:" -msgstr "" - -#: ../orchestration.rst:310 -msgid "" -"The outputs section of the stack contains two ceilometer command-line " -"queries:" -msgstr "" - -#: ../orchestration.rst:312 -msgid "" -":code:`ceilometer_sample_query`: shows the samples used to build the " -"statistics." -msgstr "" - -#: ../orchestration.rst:313 -msgid "" -":code:`ceilometer_statistics_query`: shows the statistics used to trigger " -"the alarms." -msgstr "" - -#: ../orchestration.rst:315 -msgid "These queries provide a view into the behavior of the stack." -msgstr "" - -#: ../orchestration.rst:317 -msgid "" -"In a new Terminal window, SSH into the 'api' API instance. Use the key pair " -"name that you passed in as a parameter." -msgstr "" - -#: ../orchestration.rst:325 -msgid "In your SSH session, confirm that no fractals were generated:" -msgstr "" - -#: ../orchestration.rst:336 -msgid "Then, create a pair of large fractals:" -msgstr "" - -#: ../orchestration.rst:342 -msgid "" -"In the Terminal window where you run ceilometer, run :code:" -"`ceilometer_sample_query` to see the samples." -msgstr "" - -#: ../orchestration.rst:357 -msgid "" -"The CPU utilization across workers increases as workers start to create the " -"fractals." -msgstr "" - -#: ../orchestration.rst:359 -msgid "" -"Run the :code:`ceilometer_statistics_query`: command to see the derived " -"statistics." -msgstr "" - -#: ../orchestration.rst:373 -msgid "The samples and the statistics are listed in opposite time order!" -msgstr "" - -#: ../orchestration.rst:375 -msgid "See the state of the alarms set up by the template:" -msgstr "" - -#: ../orchestration.rst:387 -msgid "" -"Run the :code:`nova list` command to confirm that the :code:`OS::Heat::" -"AutoScalingGroup` has created more instances:" -msgstr "" - -#: ../orchestration.rst:403 -msgid "" -"Now, wait until all the fractals are generated and the instances have idled " -"for some time." -msgstr "" - -#: ../orchestration.rst:406 -msgid "" -"Run the :code:`nova list` command to confirm that the :code:`OS::Heat::" -"AutoScalingGroup` removed the unneeded instances:" -msgstr "" - -#: ../orchestration.rst:420 -msgid "" -"The :code:`OS::Heat::AutoScalingGroup` removes instances in creation order. " -"So the worker instance that was created first is the first instance to be " -"removed." -msgstr "" - -#: ../orchestration.rst:424 -msgid "In the outputs section of the stack, you can run these web API calls:" -msgstr "" - -#: ../orchestration.rst:426 -msgid "" -":code:`scale__workers_up_url`: A post to this url will add worker instances." -msgstr "" - -#: ../orchestration.rst:427 -msgid "" -":code:`scale_workers_down_url`: A post to this url will remove worker " -"instances." -msgstr "" - -#: ../orchestration.rst:429 -msgid "" -"These demonstrate how the Ceilometer alarms add and remove instances. To use " -"them:" -msgstr "" - -#: ../orchestration.rst:436 -msgid "To recap:" -msgstr "" - -#: ../orchestration.rst:438 -msgid "" -"The auto-scaling stack sets up an API instance, a services instance, and an " -"auto-scaling group with a single worker instance. It also sets up ceilometer " -"alarms that add worker instances to the auto-scaling group when it is under " -"load, and removes instances when the group is idling. To do this, the alarms " -"post to URLs." -msgstr "" - -#: ../orchestration.rst:444 -msgid "" -"In this template, the alarms use metadata that is attached to each worker " -"instance. The metadata is in the :code:`metering.stack=stack_id` format." -msgstr "" - -#: ../orchestration.rst:447 -msgid "The prefix is `metering.` For example, `metering.some_name`." -msgstr "" - -#: ../orchestration.rst:456 -msgid "" -"You can aggregate samples and calculate statistics across all instances with " -"the `metering.some_name` metadata that has `some_value` by using a query of " -"the form:" -msgstr "" - -#: ../orchestration.rst:464 -msgid "For example:" -msgstr "" - -#: ../orchestration.rst:471 -msgid "The alarms have the form:" -msgstr "" - -#: ../orchestration.rst:477 -msgid "" -"Spend some time playing with the stack and the Fractal app to see how it " -"works." -msgstr "" - -#: ../orchestration.rst:479 -msgid "" -"The message queue can take a while to notice that worker instances have died." -msgstr "" - -#: ../orchestration.rst:484 -msgid "" -"You should now be fairly confident working with the Orchestration service. " -"To see the calls that we did not cover and more, see the volume " -"documentation of your SDK. Or, try one of these steps in the tutorial:" -msgstr "" - -#: ../scaling_out.rst:3 ../scaling_out.rst:143 -msgid "Scaling out" -msgstr "" - -#: ../scaling_out.rst:11 -msgid "" -"An often-cited reason for designing applications by using cloud patterns is " -"the ability to **scale out**. That is: to add additional resources, as " -"required. Contrast this strategy to the previous one of increasing capacity " -"by scaling up the size of existing resources. To scale out, you must:" -msgstr "" - -#: ../scaling_out.rst:17 -msgid "Architect your application to make use of additional resources." -msgstr "" - -#: ../scaling_out.rst:18 -msgid "Make it possible to add new resources to your application." -msgstr "" - -#: ../scaling_out.rst:22 -msgid "" -"The :doc:`/introduction` section describes how to build in a modular " -"fashion, create an API, and other aspects of the application architecture. " -"Now you will see why those strategies are so important. By creating a " -"modular application with decoupled services, you can identify components " -"that cause application performance bottlenecks and scale them out. Just as " -"importantly, you can also remove resources when they are no longer " -"necessary. It is very difficult to overstate the cost savings that this " -"feature can bring, as compared to traditional infrastructure." -msgstr "" - -#: ../scaling_out.rst:32 -msgid "" -"Of course, having access to additional resources is only part of the game " -"plan; while you can manually add or delete resources, you get more value and " -"more responsiveness if the application automatically requests additional " -"resources when it needs them." -msgstr "" - -#: ../scaling_out.rst:37 -msgid "" -"This section continues to illustrate the separation of services onto " -"multiple instances and highlights some of the choices that we have made that " -"facilitate scalability in the application architecture." -msgstr "" - -#: ../scaling_out.rst:41 -msgid "" -"You will progressively ramp up to use up six instances, so make sure that " -"your cloud account has the appropriate quota." -msgstr "" - -#: ../scaling_out.rst:44 -msgid "" -"The previous section uses two virtual machines - one 'control' service and " -"one 'worker'. The speed at which your application can generate fractals " -"depends on the number of workers. With just one worker, you can produce only " -"one fractal at a time. Before long, you will need more resources." -msgstr "" - -#: ../scaling_out.rst:50 -msgid "" -"If you do not have a working application, follow the steps in :doc:" -"`introduction` to create one." -msgstr "" - -#: ../scaling_out.rst:57 -msgid "Generate load" -msgstr "" - -#: ../scaling_out.rst:59 -msgid "" -"To test what happens when the Fractals application is under load, you can:" -msgstr "" - -#: ../scaling_out.rst:62 -msgid "" -"Load the worker: Create a lot of tasks to max out the CPU of existing worker " -"instances" -msgstr "" - -#: ../scaling_out.rst:64 -msgid "Load the API: Create a lot of API service requests" -msgstr "" - -#: ../scaling_out.rst:67 -msgid "Create more tasks" -msgstr "" - -#: ../scaling_out.rst:69 ../scaling_out.rst:106 -msgid "" -"Use SSH with the existing SSH keypair to log in to the :code:`app-" -"controller` controller instance." -msgstr "" - -#: ../scaling_out.rst:76 ../scaling_out.rst:113 -msgid "" -"Replace :code:`IP_CONTROLLER` with the IP address of the controller instance " -"and USERNAME with the appropriate user name." -msgstr "" - -#: ../scaling_out.rst:80 -msgid "" -"Call the :code:`faafo` command-line interface to request the generation of " -"five large fractals." -msgstr "" - -#: ../scaling_out.rst:87 -msgid "" -"If you check the load on the worker, you can see that the instance is not " -"doing well. On the single CPU flavor instance, a load average greater than 1 " -"means that the server is at capacity." -msgstr "" - -#: ../scaling_out.rst:96 -msgid "" -"Replace :code:`IP_WORKER` with the IP address of the worker instance and " -"USERNAME with the appropriate user name." -msgstr "" - -#: ../scaling_out.rst:101 -msgid "Create more API service requests" -msgstr "" - -#: ../scaling_out.rst:103 -msgid "" -"API load is a slightly different problem than the previous one regarding " -"capacity to work. We can simulate many requests to the API, as follows:" -msgstr "" - -#: ../scaling_out.rst:117 -msgid "" -"Use a for loop to call the :code:`faafo` command-line interface to request a " -"random set of fractals 500 times:" -msgstr "" - -#: ../scaling_out.rst:124 -msgid "" -"Replace :code:`IP_CONTROLLER` with the IP address of the controller instance." -msgstr "" - -#: ../scaling_out.rst:127 -msgid "" -"If you check the load on the :code:`app-controller` API service instance, " -"you see that the instance is not doing well. On your single CPU flavor " -"instance, a load average greater than 1 means that the server is at capacity." -msgstr "" - -#: ../scaling_out.rst:137 -msgid "" -"The sheer number of requests means that some requests for fractals might not " -"make it to the message queue for processing. To ensure that you can cope " -"with demand, you must also scale out the API capability of the Fractals " -"application." -msgstr "" - -#: ../scaling_out.rst:146 -msgid "Remove the existing app" -msgstr "" - -#: ../scaling_out.rst:148 -msgid "" -"Go ahead and delete the existing instances and security groups that you " -"created in previous sections. Remember, when instances in the cloud are no " -"longer working, remove them and re-create something new." -msgstr "" - -#: ../scaling_out.rst:179 -msgid "Extra security groups" -msgstr "" - -#: ../scaling_out.rst:181 -msgid "" -"As you change the topology of your applications, you must update or create " -"security groups. Here, you re-create the required security groups." -msgstr "" - -#: ../scaling_out.rst:211 -msgid "A floating IP helper function" -msgstr "" - -#: ../scaling_out.rst:213 -msgid "" -"Define a short function to locate unused or allocate floating IPs. This " -"saves a few lines of code and prevents you from reaching your floating IP " -"quota too quickly." -msgstr "" - -#: ../scaling_out.rst:243 -msgid "Split the database and message queue" -msgstr "" - -#: ../scaling_out.rst:245 -msgid "" -"Before you scale out your application services, like the API service or the " -"workers, you must add a central database and an :code:`app-services` " -"messaging instance. The database and messaging queue will be used to track " -"the state of fractals and to coordinate the communication between the " -"services." -msgstr "" - -#: ../scaling_out.rst:276 -msgid "Scale the API service" -msgstr "" - -#: ../scaling_out.rst:278 -msgid "" -"With multiple workers producing fractals as fast as they can, the system " -"must be able to receive the requests for fractals as quickly as possible. If " -"our application becomes popular, many thousands of users might connect to " -"our API to generate fractals." -msgstr "" - -#: ../scaling_out.rst:283 -msgid "" -"Armed with a security group, image, and flavor size, you can add multiple " -"API services:" -msgstr "" - -#: ../scaling_out.rst:311 -msgid "" -"These services are client-facing, so unlike the workers they do not use a " -"message queue to distribute tasks. Instead, you must introduce some kind of " -"load balancing mechanism to share incoming requests between the different " -"API services." -msgstr "" - -#: ../scaling_out.rst:316 -msgid "" -"A simple solution is to give half of your friends one address and half the " -"other, but that solution is not sustainable. Instead, you can use a `DNS " -"round robin `_ to do that " -"automatically. However, OpenStack networking can provide Load Balancing as a " -"Service, which :doc:`/networking` explains." -msgstr "" - -#: ../scaling_out.rst:328 -msgid "Scale the workers" -msgstr "" - -#: ../scaling_out.rst:330 -msgid "To increase the overall capacity, add three workers:" -msgstr "" - -#: ../scaling_out.rst:357 -msgid "" -"Adding this capacity enables you to deal with a higher number of requests " -"for fractals. As soon as these worker instances start, they begin checking " -"the message queue for requests, reducing the overall backlog like a new " -"register opening in the supermarket." -msgstr "" - -#: ../scaling_out.rst:362 -msgid "" -"This process was obviously a very manual one. Figuring out that we needed " -"more workers and then starting new ones required some effort. Ideally the " -"system would do this itself. If you build your application to detect these " -"situations, you can have it automatically request and remove resources, " -"which saves you the effort of doing this work yourself. Instead, the " -"OpenStack Orchestration service can monitor load and start instances, as " -"appropriate. To find out how to set that up, see :doc:`orchestration`." -msgstr "" - -#: ../scaling_out.rst:372 -msgid "Verify that we have had an impact" -msgstr "" - -#: ../scaling_out.rst:374 -msgid "" -"In the previous steps, you split out several services and expanded capacity. " -"To see the new features of the Fractals application, SSH to one of the app " -"instances and create a few fractals." -msgstr "" - -#: ../scaling_out.rst:382 -msgid "" -"Replace :code:`IP_API_1` with the IP address of the first API instance and " -"USERNAME with the appropriate user name." -msgstr "" - -#: ../scaling_out.rst:385 -msgid "Use the :code:`faafo create` command to generate fractals." -msgstr "" - -#: ../scaling_out.rst:387 -msgid "" -"Use the :code:`faafo list` command to watch the progress of fractal " -"generation." -msgstr "" - -#: ../scaling_out.rst:390 -msgid "Use the :code:`faafo UUID` command to examine some of the fractals." -msgstr "" - -#: ../scaling_out.rst:392 -msgid "" -"The `generated_by` field shows the worker that created the fractal. Because " -"multiple worker instances share the work, fractals are generated more " -"quickly and users might not even notice when a worker fails." -msgstr "" - -#: ../scaling_out.rst:442 -msgid "" -"The fractals are now available from any of the app-api hosts. To verify, " -"visit http://IP_API_1/fractal/FRACTAL_UUID and http://IP_API_2/fractal/" -"FRACTAL_UUID. You now have multiple redundant web services. If one fails, " -"you can use the others." -msgstr "" - -#: ../scaling_out.rst:447 -msgid "" -"Replace :code:`IP_API_1` and :code:`IP_API_2` with the corresponding " -"floating IPs. Replace FRACTAL_UUID with the UUID of an existing fractal." -msgstr "" - -#: ../scaling_out.rst:451 -msgid "" -"Go ahead and test the fault tolerance. Start deleting workers and API " -"instances. As long as you have one of each, your application is fine. " -"However, be aware of one weak point. The database contains the fractals and " -"fractal metadata. If you lose that instance, the application stops. Future " -"sections will explain how to address this weak point." -msgstr "" - -#: ../scaling_out.rst:458 -msgid "" -"If you had a load balancer, you could distribute this load between the two " -"different API services. You have several options. The :doc:`networking` " -"section shows you one option." -msgstr "" - -#: ../scaling_out.rst:462 -msgid "" -"In theory, you could use a simple script to monitor the load on your workers " -"and API services and trigger the creation of instances, which you already " -"know how to do. Congratulations! You are ready to create scalable cloud " -"applications." -msgstr "" - -#: ../scaling_out.rst:467 -msgid "" -"Of course, creating a monitoring system for a single application might not " -"make sense. To learn how to use the OpenStack Orchestration monitoring and " -"auto-scaling capabilities to automate these steps, see :doc:`orchestration`." -msgstr "" - -#: ../scaling_out.rst:475 -msgid "" -"You should be fairly confident about starting instances and distributing " -"services from an application among these instances." -msgstr "" - -#: ../scaling_out.rst:478 -msgid "" -"As mentioned in :doc:`/introduction`, the generated fractal images are saved " -"on the local file system of the API service instances. Because you have " -"multiple API instances up and running, the fractal images are spread across " -"multiple API services, which causes a number of :code:`IOError: [Errno 2] No " -"such file or directory` exceptions when trying to download a fractal image " -"from an API service instance that does not have the fractal image on its " -"local file system." -msgstr "" - -#: ../scaling_out.rst:486 -msgid "" -"Go to :doc:`/durability` to learn how to use Object Storage to solve this " -"problem in a elegant way. Or, you can proceed to one of these sections:" -msgstr "" - -#: ../scaling_out.rst:500 -msgid "" -"This file contains all the code from this tutorial section. This " -"comprehensive code sample lets you view and run the code as a single script." -msgstr ""