From 1aff709eb3381357a39b18bfe2cab41b92bad336 Mon Sep 17 00:00:00 2001 From: OpenStack Proposal Bot Date: Thu, 19 Nov 2015 06:18:37 +0000 Subject: [PATCH] Imported Translations from Zanata For more information about this automatic import see: https://wiki.openstack.org/wiki/Translations/Infrastructure Change-Id: Ifbcf75e1302e2fbba49f70a39df909788510dd99 --- .../source/locale/admin-guide-cloud.pot | 455 +++++++++++++++++- .../locale/ja/LC_MESSAGES/common-rst.po | 395 ++++++++++++++- doc/glossary/locale/ja.po | 138 +++++- .../locale/ja/LC_MESSAGES/install-guide.po | 7 +- .../source/locale/networking-guide.pot | 170 +++---- 5 files changed, 1060 insertions(+), 105 deletions(-) diff --git a/doc/admin-guide-cloud/source/locale/admin-guide-cloud.pot b/doc/admin-guide-cloud/source/locale/admin-guide-cloud.pot index ee6e776290..8163999845 100644 --- a/doc/admin-guide-cloud/source/locale/admin-guide-cloud.pot +++ b/doc/admin-guide-cloud/source/locale/admin-guide-cloud.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Cloud Administrator Guide 0.9\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2015-11-16 06:14+0000\n" +"POT-Creation-Date: 2015-11-19 06:15+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -11651,6 +11651,439 @@ msgid "" "valid X.509 certificate from a known CA::" msgstr "" +#: ../keystone_fernet_token_faq.rst:3 +msgid "fernet - Frequently Asked Questions" +msgstr "" + +#: ../keystone_fernet_token_faq.rst:5 +msgid "" +"The following questions have been asked periodically since the initial " +"release of the fernet token format in Kilo." +msgstr "" + +#: ../keystone_fernet_token_faq.rst:9 +msgid "What are the different types of keys?" +msgstr "" + +#: ../keystone_fernet_token_faq.rst:11 +msgid "" +"A key repository is required by keystone in order to create fernet tokens. " +"These keys are used to encrypt and decrypt the information that makes up the " +"payload of the token. Each key in the repository can have one of three " +"states. The state of the key determines how keystone uses a key with fernet " +"tokens. The different types are as follows:" +msgstr "" + +#: ../keystone_fernet_token_faq.rst:18 +msgid "" +"There is only ever one primary key in a key repository. The primary key is " +"allowed to encrypt and decrypt tokens. This key is always named as the " +"highest index in the repository." +msgstr "" + +#: ../keystone_fernet_token_faq.rst:19 +msgid "Primary key:" +msgstr "" + +#: ../keystone_fernet_token_faq.rst:22 +msgid "" +"A secondary key was at one point a primary key, but has been demoted in " +"place of another primary key. It is only allowed to decrypt tokens. Since it " +"was the primary at some point in time, its existence in the key repository " +"is justified. Keystone needs to be able to decrypt tokens that were created " +"with old primary keys." +msgstr "" + +#: ../keystone_fernet_token_faq.rst:25 +msgid "Secondary key:" +msgstr "" + +#: ../keystone_fernet_token_faq.rst:28 +msgid "" +"The staged key is a special key that shares some similarities with secondary " +"keys. There can only ever be one staged key in a repository and it must " +"exist. Just like secondary keys, staged keys have the ability to decrypt " +"tokens. Unlike secondary keys, staged keys have never been a primary key. In " +"fact, they are opposites since the staged key will always be the next " +"primary key. This helps clarify the name because they are the next key " +"staged to be the primary key. This key is always named as ``0`` in the key " +"repository." +msgstr "" + +#: ../keystone_fernet_token_faq.rst:34 +msgid "Staged key:" +msgstr "" + +#: ../keystone_fernet_token_faq.rst:37 +msgid "So, how does a staged key help me and why do I care about it?" +msgstr "" + +#: ../keystone_fernet_token_faq.rst:39 +msgid "" +"The fernet keys have a natural lifecycle. Each key starts as a staged key, " +"is promoted to be the primary key, and then demoted to be a secondary key. " +"New tokens can only be encrypted with a primary key. Secondary and staged " +"keys are never used to encrypt token. The staged key is a special key given " +"the order of events and the attributes of each type of key. The staged key " +"is the only key in the repository that has not had a chance to encrypt any " +"tokens yet, but it is still allowed to decrypt tokens. As an operator, this " +"gives you the chance to perform a key rotation on one keystone node, and " +"distribute the new key set over a span of time. This does not require the " +"distribution to take place in an ultra short period of time. Tokens " +"encrypted with a primary key can be decrypted, and validated, on other nodes " +"where that key is still staged." +msgstr "" + +#: ../keystone_fernet_token_faq.rst:52 +msgid "Where do I put my key repository?" +msgstr "" + +#: ../keystone_fernet_token_faq.rst:54 +msgid "" +"The key repository is specified using the ``key_repository`` option in the " +"keystone configuration file. The keystone process should be able to read and " +"write to this location but it should be kept secret otherwise. Currently, " +"keystone only supports file-backed key repositories." +msgstr "" + +#: ../keystone_fernet_token_faq.rst:59 +msgid "..code-block:: ini" +msgstr "" + +#: ../keystone_fernet_token_faq.rst:61 +msgid "[fernet_tokens] key_repository = /etc/keystone/fernet-keys/" +msgstr "" + +#: ../keystone_fernet_token_faq.rst:65 +msgid "What is the recommended way to rotate and distribute keys?" +msgstr "" + +#: ../keystone_fernet_token_faq.rst:67 +msgid "" +"The ``keystone-manage`` command line utility includes a key rotation " +"mechanism. This mechanism will initialize and rotate keys but does not make " +"an effort to distribute keys across keystone nodes. The distribution of keys " +"across a keystone deployment is best handled through configuration " +"management tooling. Use ``keystone-manage fernet_rotate`` to rotate the key " +"repository." +msgstr "" + +#: ../keystone_fernet_token_faq.rst:74 +msgid "Do fernet tokens still expires?" +msgstr "" + +#: ../keystone_fernet_token_faq.rst:76 +msgid "" +"Yes, fernet tokens can expire just like any other keystone token formats." +msgstr "" + +#: ../keystone_fernet_token_faq.rst:79 +msgid "Why should I choose fernet tokens over UUID tokens?" +msgstr "" + +#: ../keystone_fernet_token_faq.rst:81 +msgid "" +"Even though fernet tokens operate very similarly to UUID tokens, they do not " +"require persistence. The keystone token database no longer suffers bloat as " +"a side effect of authentication. Pruning expired tokens from the token " +"database is no longer required when using fernet tokens. Because fernet " +"tokens do not require persistence, they do not have to be replicated. As " +"long as each keystone node shares the same key repository, fernet tokens can " +"be created and validated instantly across nodes." +msgstr "" + +#: ../keystone_fernet_token_faq.rst:90 +msgid "Why should I choose fernet tokens over PKI or PKIZ tokens?" +msgstr "" + +#: ../keystone_fernet_token_faq.rst:92 +msgid "" +"The arguments for using fernet over PKI and PKIZ remain the same as UUID, in " +"addition to the fact that fernet tokens are much smaller than PKI and PKIZ " +"tokens. PKI and PKIZ tokens still require persistent storage and can " +"sometimes cause issues due to their size. This issue is mitigated when " +"switching to fernet because fernet tokens are kept under a 250 byte limit. " +"PKI and PKIZ tokens typically exceed 1600 bytes in length. The length of a " +"PKI or PKIZ token is dependent on the size of the deployment. Bigger service " +"catalogs will result in longer token lengths. This pattern does not exist " +"with fernet tokens because the contents of the encrypted payload is kept to " +"a minimum." +msgstr "" + +#: ../keystone_fernet_token_faq.rst:103 +msgid "" +"Should I rotate and distribute keys from the same keystone node every " +"rotation?" +msgstr "" + +#: ../keystone_fernet_token_faq.rst:105 +msgid "" +"No, but the relationship between rotation and distribution should be lock-" +"step. Once you rotate keys on one keystone node, the key repository from " +"that node should be distributed to the rest of the cluster. Once you confirm " +"that each node has the same key repository state, you could rotate and " +"distribute from any other node in the cluster." +msgstr "" + +#: ../keystone_fernet_token_faq.rst:111 +msgid "" +"If the rotation and distribution are not lock-step, a single keystone node " +"in the deployment will create tokens with a primary key that no other node " +"has as a staged key. This will cause tokens generated from one keystone node " +"to fail validation on other keystone nodes." +msgstr "" + +#: ../keystone_fernet_token_faq.rst:117 +msgid "How do I add new keystone nodes to a deployment?" +msgstr "" + +#: ../keystone_fernet_token_faq.rst:119 +msgid "" +"The keys used to create fernet tokens should be treated like super secret " +"configuration files, similar to an SSL secret key. Before a node is allowed " +"to join an existing cluster, issuing and validating tokens, it should have " +"the same key repository as the rest of the nodes in the cluster." +msgstr "" + +#: ../keystone_fernet_token_faq.rst:125 +msgid "How should I approach key distribution?" +msgstr "" + +#: ../keystone_fernet_token_faq.rst:127 +msgid "" +"Remember that key distribution is only required in multi-node keystone " +"deployments. If you only have one keystone node serving requests in your " +"deployment, key distribution is unnecessary." +msgstr "" + +#: ../keystone_fernet_token_faq.rst:131 +msgid "" +"Key distribution is a problem best approached from the deployment's current " +"configuration management system. Since not all deployments use the same " +"configuration management systems, it makes sense to explore options around " +"what is already available for managing keys, while keeping the secrecy of " +"the keys in mind. Many configuration management tools can leverage something " +"like ``rsync`` to manage key distribution." +msgstr "" + +#: ../keystone_fernet_token_faq.rst:138 +msgid "" +"Key rotation is a single operation that promotes the current staged key to " +"primary, creates a new staged key, and prunes old secondary keys. It is " +"easiest to do this on a single node and verify the rotation took place " +"properly before distributing the key repository to the rest of the cluster. " +"The concept behind the staged key breaks the expectation that key rotation " +"and key distribution have to be done in a single step. With the staged key, " +"we have time to inspect the new key repository before syncing state with the " +"rest of the cluster. Key distribution should be an operation that can run in " +"succession until it succeeds. The following might help illustrate the " +"isolation between key rotation and key distribution." +msgstr "" + +#: ../keystone_fernet_token_faq.rst:149 +msgid "" +"Ensure all keystone nodes in the deployment have the same key repository." +msgstr "" + +#: ../keystone_fernet_token_faq.rst:150 +msgid "Pick a keystone node in the cluster to rotate from." +msgstr "" + +#: ../keystone_fernet_token_faq.rst:153 +msgid "" +"If no, investigate issues with the particular keystone node you rotated keys " +"on. Fernet keys are small and the operation for rotation is trivial. There " +"should not be much room for error in key rotation. It is possible that the " +"user does not have the ability to write new keys to the key repository. Log " +"output from ``keystone-manage fernet_rotate`` should give more information " +"into specific failures." +msgstr "" + +#: ../keystone_fernet_token_faq.rst:160 +msgid "" +"If yes, you should see a new staged key. The old staged key should be the " +"new primary. Depending on the ``max_active_keys`` limit you might have " +"secondary keys that were pruned. At this point, the node that you rotated on " +"will be creating fernet tokens with a primary key that all other nodes " +"should have as the staged key. This is why we checked the state of all key " +"repositories in Step one. All other nodes in the cluster should be able to " +"decrypt tokens created with the new primary key. At this point, we are ready " +"to distribute the new key set." +msgstr "" + +#: ../keystone_fernet_token_faq.rst:167 +msgid "Rotate keys." +msgstr "" + +#: ../keystone_fernet_token_faq.rst:167 +msgid "Was is successful?" +msgstr "" + +#: ../keystone_fernet_token_faq.rst:171 +msgid "" +"If yes, you should be able to confirm that all nodes in the cluster have the " +"same key repository that was introduced in Step 3. All nodes in the cluster " +"will be creating tokens with the primary key that was promoted in Step 3. No " +"further action is required until the next schedule key rotation." +msgstr "" + +#: ../keystone_fernet_token_faq.rst:176 +msgid "" +"If no, try distributing again. Remember that we already rotated the " +"repository and performing another rotation at this point will result in " +"tokens that cannot be validated across certain hosts. Specifically, the " +"hosts that did not get the latest key set. You should be able to distribe " +"keys until it is successful. If certain nodes have issues syncing, it could " +"be permission or network issues and those should be resolved before " +"subsequent rotations." +msgstr "" + +#: ../keystone_fernet_token_faq.rst:182 +msgid "Distribute the new key repository." +msgstr "" + +#: ../keystone_fernet_token_faq.rst:182 +msgid "Was it successful?" +msgstr "" + +#: ../keystone_fernet_token_faq.rst:185 +msgid "How long should I keep my keys around?" +msgstr "" + +#: ../keystone_fernet_token_faq.rst:187 +msgid "" +"The fernet tokens that keystone creates are only secure as the keys creating " +"them. With staged keys the penalty of key rotation is low, allowing you to " +"err on the side of security and rotate weekly, daily, or even hourly. " +"Ultimately, this should be less time than it takes an attacker to break a " +"``AES256`` key and a ``SHA256 HMAC``." +msgstr "" + +#: ../keystone_fernet_token_faq.rst:194 +msgid "Is a fernet token still a bearer token?" +msgstr "" + +#: ../keystone_fernet_token_faq.rst:196 +msgid "" +"Yes, and they follow exactly the same validation path as UUID tokens, with " +"the exception of being written to, and read from, a back end. If someone " +"compromises your fernet token, they have the power to do all the operations " +"you are allowed to do." +msgstr "" + +#: ../keystone_fernet_token_faq.rst:202 +msgid "What if I need to revoke all my tokens?" +msgstr "" + +#: ../keystone_fernet_token_faq.rst:204 +msgid "" +"To invalidate every token issued from keystone and start fresh, remove the " +"current key repository, create a new key set, and redistribute it to all " +"nodes in the cluster. This will render every token issued from keystone as " +"invalid regardless if the token has actually expired. When a client goes to " +"re-authenticate, the new token will have been created with a new fernet key." +msgstr "" + +#: ../keystone_fernet_token_faq.rst:211 +msgid "" +"What can an attacker do if they compromise a fernet key in my deployment?" +msgstr "" + +#: ../keystone_fernet_token_faq.rst:213 +msgid "" +"If any key used in the key repository is compromised, an attacker will be " +"able to build their own tokens. If they know the ID of an administrator on a " +"project, they could generate administrator tokens for the project. They will " +"be able to generate their own tokens until the compromised key has been " +"removed from from the repository." +msgstr "" + +#: ../keystone_fernet_token_faq.rst:220 +msgid "I rotated keys and now tokens are invalidating early, what did I do?" +msgstr "" + +#: ../keystone_fernet_token_faq.rst:222 +msgid "" +"Using fernet tokens requires some awareness around token expiration and the " +"key lifecycle. You do not want to rotate so often that secondary keys are " +"removed that might still be needed to decrypt unexpired tokens. If this " +"happens, you will not be able to decrypt the token because the key the was " +"used to encrypt it is now gone. Only remove keys that you know are not being " +"used to encrypt or decrypt tokens." +msgstr "" + +#: ../keystone_fernet_token_faq.rst:229 +msgid "" +"For example, your token is valid for 24 hours and we want to rotate keys " +"every six hours. We will need to make sure tokens that were created at 08:00 " +"AM on Monday are still valid at 07:00 AM on Tuesday, assuming they were not " +"prematurely revoked. To accomplish this, we will want to make sure we set " +"``max_active_keys=6`` in our keystone configuration file. This will allow us " +"to hold all keys that might still be required to validate a previous token, " +"but keeps the key repository limited to only the keys that are needed." +msgstr "" + +#: ../keystone_fernet_token_faq.rst:237 +msgid "" +"The number of ``max_active_keys`` for a deployment can be determined by " +"dividing the token lifetime, in hours, by the frequency of rotation in hours " +"and adding two. Better illustrated as::" +msgstr "" + +#: ../keystone_fernet_token_faq.rst:245 +msgid "" +"The reason for adding two additional keys to the count is to include the " +"staged key and a buffer key. This can be shown based on the previous " +"example. We initially setup the key repository at 6:00 AM on Monday, and the " +"initial state looks like::" +msgstr "" + +#: ../keystone_fernet_token_faq.rst:256 +msgid "" +"All tokens created after 6:00 AM are encrypted with key ``1``. At 12:00 PM " +"we will rotate keys again, resulting in::" +msgstr "" + +#: ../keystone_fernet_token_faq.rst:266 +msgid "" +"We are still able to validate tokens created between 6:00 - 11:59 AM because " +"the ``1`` key still exists as a secondary key. All tokens issued after 12:00 " +"PM will be encrypted with key ``2``. At 6:00 PM we do our next rotation, " +"resulting in::" +msgstr "" + +#: ../keystone_fernet_token_faq.rst:279 +msgid "" +"It is still possible to validate tokens issued from 6:00 AM - 5:59 PM " +"because keys ``1`` and ``2`` exist as secondary keys. Every token issued " +"until 11:59 PM will be encrypted with key ``3``, and at 12:00 AM we do our " +"next rotation::" +msgstr "" + +#: ../keystone_fernet_token_faq.rst:292 +msgid "" +"Just like before, we can still validate tokens issued from 6:00 AM the " +"previous day until 5:59 AM today because keys ``1`` - ``4`` are present. At " +"6:00 AM, tokens issued from the previous day will start to expire and we do " +"our next scheduled rotation::" +msgstr "" + +#: ../keystone_fernet_token_faq.rst:307 +msgid "" +"Tokens will naturally expire after 6:00 AM, but we will not be able to " +"remove key ``1`` until the next rotation because it encrypted all tokens " +"from 6:00 AM to 12:00 PM the day before. Once we do our next rotation, which " +"is at 12:00 PM, the ``1`` key will be pruned from the repository::" +msgstr "" + +#: ../keystone_fernet_token_faq.rst:322 +msgid "" +"If keystone were to receive a token that was created between 6:00 AM and " +"12:00 PM the day before, encrypted with the ``1`` key, it would not be valid " +"because it was already expired. This makes it possible for us to remove the " +"``1`` key from the repository without negative validation side-effects." +msgstr "" + #: ../keystone_integrate_assignment_backend_ldap.rst:5 msgid "Integrate assignment back end with LDAP" msgstr "" @@ -12303,7 +12736,7 @@ msgid "" "Tokens are used to interact with the various OpenStack APIs. The token type " "issued by keystone is configurable through the :file:`etc/keystone.conf` " "file. Currently, there are four supported token types and they include UUID, " -"Fernet, PKI, and PKIZ." +"fernet, PKI, and PKIZ." msgstr "" #: ../keystone_tokens.rst:11 @@ -12324,20 +12757,22 @@ msgstr "" #: ../keystone_tokens.rst:21 msgid "" -"Fernet tokens were introduced in the OpenStack Kilo release. Unlike the " -"other token types mentioned in this document, Fernet tokens do not need to " -"be persisted in a back end. ``AES256`` encryption is used to protect the " +"The fernet token format was introduced in the OpenStack Kilo release. Unlike " +"the other token types mentioned in this document, fernet tokens do not need " +"to be persisted in a back end. ``AES256`` encryption is used to protect the " "information stored in the token and integrity is verified with a ``SHA256 " "HMAC`` signature. Only the Identity service should have access to the keys " -"used to encrypt and decrypt Fernet tokens. Like UUID tokens, Fernet tokens " -"must be passed back to the Identity service in order to validate them." +"used to encrypt and decrypt fernet tokens. Like UUID tokens, fernet tokens " +"must be passed back to the Identity service in order to validate them. For " +"more information on the fernet token type, see the :ref:" +"`keystone_fernet_token_faq`." msgstr "" -#: ../keystone_tokens.rst:30 +#: ../keystone_tokens.rst:31 msgid "PKI and PKIZ tokens" msgstr "" -#: ../keystone_tokens.rst:32 +#: ../keystone_tokens.rst:33 msgid "" "PKI tokens are signed documents that contain the authentication context, as " "well as the service catalog. Depending on the size of the OpenStack " @@ -12346,7 +12781,7 @@ msgid "" "tokens." msgstr "" -#: ../keystone_tokens.rst:37 +#: ../keystone_tokens.rst:38 msgid "" "The same concepts from PKI tokens apply to PKIZ tokens. The only difference " "between the two is PKIZ tokens are compressed to help mitigate the size " diff --git a/doc/common-rst/source/locale/ja/LC_MESSAGES/common-rst.po b/doc/common-rst/source/locale/ja/LC_MESSAGES/common-rst.po index b6966b4c3d..67ab1912df 100644 --- a/doc/common-rst/source/locale/ja/LC_MESSAGES/common-rst.po +++ b/doc/common-rst/source/locale/ja/LC_MESSAGES/common-rst.po @@ -18,11 +18,11 @@ msgid "" msgstr "" "Project-Id-Version: Common documents 1.0.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2015-11-18 05:45+0000\n" +"POT-Creation-Date: 2015-11-19 03:46+0000\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" -"PO-Revision-Date: 2015-11-17 11:46+0000\n" +"PO-Revision-Date: 2015-11-18 05:12+0000\n" "Last-Translator: Akihiro Motoki \n" "Language: ja\n" "Plural-Forms: nplurals=1; plural=0;\n" @@ -570,6 +570,15 @@ msgstr "" "Object Storage コンテナーとコンテナーメタデータを保存する SQLite データベー" "ス。コンテナーサーバーは、このデータベースにアクセスする。" +msgid "" +"A Shared File Systems service that provides a stable RESTful API. The " +"service authenticates and routes requests throughout the Shared File Systems " +"service. There is python-manilaclient to interact with the API." +msgstr "" +"安定版の RESTful API を提供する Shared File Systems サービス。 Shared File " +"Systems サービスへのすべてのリクエストの認証と転送を行う。この API と通信する" +"ための python-manilaclient が提供されています。" + msgid "" "A VM image that does not save changes made to its volumes and reverts them " "to their original state after the instance is terminated." @@ -645,6 +654,13 @@ msgstr "" "エンドのストレージと相互作用する cinder のコンポーネント。cinder-volume デー" "モンにより提供される。" +msgid "" +"A cli tool used to retrieve various metrics and telemetry information about " +"a cluster that has been collected by the swift-recon middleware." +msgstr "" +"swift-recon ミドルウェアによる収集された、クラスターの様々な性能情報や統計情" +"報を取得するために使用する CLI ツール。" + msgid "" "A collection of command-line tools for administering VMs; most are " "compatible with OpenStack." @@ -1407,6 +1423,15 @@ msgid "" "the domain." msgstr "特定のドメインに関する情報を指定し、ドメインに所属するレコード。" +msgid "" +"A remote, mountable file system in the context of the Shared File Systems. " +"You can mount a share to, and access a share from, several hosts by several " +"users at a time." +msgstr "" +"Shared File System サービスにおいて、リモートのマウント可能なファイルシステム" +"のこと。同時に、複数のユーザーが複数のホストから、共有をマウントしたり、アク" +"セスしたりできる。" + msgid "A routing algorithm in the Compute RabbitMQ." msgstr "Compute RabbitMQ におけるルーティングアルゴリズム。" @@ -1762,6 +1787,18 @@ msgstr "" msgid "Accepts Image API calls for image discovery, retrieval, and storage." msgstr "イメージの検索、取得、保存のために Image API を受け付けます。" +msgid "" +"Accepts OpenStack Object Storage API and raw HTTP requests to upload files, " +"modify metadata, and create containers. It also serves file or container " +"listings to web browsers. To improve performance, the proxy server can use " +"an optional cache that is usually deployed with memcache." +msgstr "" +"OpenStack Object Storage API と生の HTTP リクエストを受け付け、ファイルのアッ" +"プロード、メタデータの変更、コンテナーの作成などを行います。ウェブブラウザー" +"に対するファイルやコンテナーの一覧表示も行えます。性能を向上させるために、プ" +"ロキシーサーバーがキャッシュを使うこともできます。通常はキャッシュには " +"memcache が使用されます。" + msgid "" "Accepts and responds to end user compute API calls. The service supports the " "OpenStack Compute API, the Amazon EC2 API, and a special Admin API for " @@ -2033,6 +2070,13 @@ msgstr "API サーバー (``ceilometer-api``)" msgid "An API that is accessible to tenants." msgstr "テナントにアクセス可能な API。" +msgid "" +"An AWS Query API that is compatible with AWS CloudFormation. It processes " +"API requests by sending them to the heat-engine over RPC." +msgstr "" +"AWS CloudFormation 互換の AWS Query API を提供します。受け取った API リスクエ" +"ストを RPC 経由で heat-engine に送信します。" + msgid "" "An Amazon EBS storage volume that contains a bootable VM image, currently " "unsupported in OpenStack." @@ -2102,6 +2146,23 @@ msgstr "" "異なるネットワーク間でネットワーク通信を中継する、IP アドレス。一般的にはルー" "ターに割り当てられる。" +msgid "" +"An Identity API v3 entity. Represents a collection of projects, groups and " +"users that defines administrative boundaries for managing OpenStack Identity " +"entities. On the Internet, separates a website from other sites. Often, the " +"domain name has two or more parts that are separated by dots. For example, " +"yahoo.com, usa.gov, harvard.edu, or mail.yahoo.com. Also, a domain is an " +"entity or container of all DNS-related information containing one or more " +"records." +msgstr "" +"Identity API v3 のエンティティー。プロジェクト、グループ、ユーザーの集合体" +"で、 OpenStack Identity のエンティティー管理において管理境界を定義するための" +"ものである。インターネット分野では、ドメインによりウェブサイトが区別され、多" +"くの場合、ドメイン名はドット区切りの 2 以上の部分から構成される。例えば、 " +"yahoo.com, usa.gov, harvard.edu, mail.yahoo.com など。また、ドメインは、DNS " +"関連情報のエンティティーや 1 つ以上のレコードを持つ DNS 関連の情報の入れ物を" +"表すのにも使用される。" + msgid "" "An Identity service API access token that is associated with a specific " "tenant." @@ -2267,6 +2328,23 @@ msgstr "" "る。OpenStack のリリース間隔が 3 か月から 6 か月になったとき、リリースのコー" "ド名が前のサミットと地理的に近いところになるように変更された。" +msgid "" +"An OpenStack service that provides a set of services for management of " +"shared file systems in a multi-tenant cloud environment. The service is " +"similar to how OpenStack provides block-based storage management through the " +"OpenStack Block Storage service project. With the Shared File Systems " +"service, you can create a remote file system and mount the file system on " +"your instances. You can also read and write data from your instances to and " +"from your file system. The project name of the Shared File Systems service " +"is manila." +msgstr "" +"マルチテナントのクラウド環境で共有ファイルシステムを管理するためのサービス群" +"を提供する OpenStack サービス。 OpenStack がブロックベースのストレージ管理" +"を、 OpenStack Block Storage サービスプロジェクトとして提供しているのと類似し" +"ている。 Shared File Systems サービスを使うと、リモートファイルシステムを作成" +"し、自分のインスタンスからそのファイルシステムをマウントし、インスタンスから" +"そのファイルシステムの読み書きを行える。このプロジェクトのコード名は manila。" + msgid "" "An OpenStack service, such as Compute, Object Storage, or Image service. " "Provides one or more endpoints through which users can access resources and " @@ -2276,6 +2354,13 @@ msgstr "" "がリソースにアクセスしたり、操作を実行したりできる 1 つ以上のエンドポイントを" "提供する。" +msgid "" +"An OpenStack-native REST API that processes API requests by sending them to " +"the heat-engine over Remote Procedure Call (RPC)." +msgstr "" +"OpenStack 独自の REST API を提供します。 受け取った API リスクエストを、リ" +"モートプロシージャコール (RPC) 経由で heat-engine に送信します。" + msgid "An OpenStack-provided image." msgstr "OpenStack が提供するイメージ。" @@ -2303,6 +2388,12 @@ msgstr "" "Identity と安全に通信するために Compute により使用される、管理者により定義さ" "れたトークン。" +msgid "An alarm evaluator (``ceilometer-alarm-evaluator``)" +msgstr "アラーム評価器 (``ceilometer-alarm-evaluator``)" + +msgid "An alarm notifier (``ceilometer-alarm-notifier``)" +msgstr "アラーム通知器 (``ceilometer-alarm-notifier``)" + msgid "" "An alpha-numeric string of text used to access OpenStack APIs and resources." msgstr "OpenStack API やリソースへのアクセスに使用される英数字文字列。" @@ -2360,6 +2451,17 @@ msgstr "" "指定されたホスト上で現在進行中の build, snapshot, migrate, resize の操作数を" "元に計算される、Compute のキャパシティキャッシュの１要素。" +msgid "" +"An entity in the context of the Shared File Systems that encapsulates " +"interaction with the Networking service. If the driver you selected runs in " +"the mode requiring such kind of interaction, you need to specify the share " +"network to create a share." +msgstr "" +"Shared File System サービスにおいて、Networking サービスとのやり取りを抽象化" +"するエンティティー。選択したドライバーが Networking サービスとのやり取りを必" +"要とするモードで動作している場合、共有を作成する際にネットワーク共有 (share " +"network) を指定する必要がある。" + msgid "" "An entity that maps Object Storage data to partitions. A separate ring " "exists for each service, such as account, object, and container." @@ -2489,6 +2591,10 @@ msgstr "" "イメージをすぐに削除する代わりに、事前定義した秒数経過後に削除するための、" "Image service 内のオプション。" +msgid "Analytics-as-a-Service for ad-hoc or bursty analytic workloads." +msgstr "" +"その場限りやバースト的な分析ワークロードに対応できる Analytics-as-a-Service" + msgid "" "Another option is to use the unofficial binary installer provided by " "Christoph Gohlke (http://www.lfd.uci.edu/~gohlke/pythonlibs/#pip)." @@ -2601,6 +2707,19 @@ msgstr "" "状態でボリュームを別の場所に移動することができます。スナップショットを持たな" "い、切断されているボリュームだけが移動できます。" +msgid "" +"As shown in :ref:`get_started_conceptual_architecture`, OpenStack consists " +"of several independent parts, named the OpenStack services. All services " +"authenticate through a common Identity service. Individual services interact " +"with each other through public APIs, except where privileged administrator " +"commands are necessary." +msgstr "" +":ref:`get_started_conceptual_architecture` にあるように、 OpenStack は " +"OpenStack サービスと呼ばれる複数の独立した部品で構成されています。すべての" +"サービスは共通の Identity service を通して認証を行います。個々のサービスは、" +"パブリック API を通じて互いに連携します。ただし、特権管理コマンドが必要な場合" +"もいくつかあります。" + msgid "" "As the volume donor, request a volume transfer authorization code for a " "specific volume:" @@ -3456,7 +3575,7 @@ msgid "Designate" msgstr "Designate" msgid "Designed as an OpenStack component." -msgstr "OpenStack のコンポーネントとして設計されました。" +msgstr "OpenStack のコンポーネントとして設計されています。" msgid "Desktop-as-a-Service" msgstr "Desktop-as-a-Service" @@ -3668,6 +3787,9 @@ msgstr "" "非常に格好良く聞こえる、状態フラグの要素に保証される。コード名は、一般的な投" "票により選択される。" +msgid "Easily scalable for future growth" +msgstr "将来のサイズ増加に応じて容易に拡張可能" + msgid "Efficiently polls metering data related to OpenStack services." msgstr "OpenStack サービスに関連する計測データを効率的に取得します。" @@ -3735,6 +3857,14 @@ msgstr "" "ユーザーをテナント管理者もしくはエンドユーザーとしてコマンドを送信可能にしま" "す。" +msgid "" +"Enables users to submit commands to the REST API through a command-line " +"client authorized as either a admin user, reseller user, or swift user." +msgstr "" +"ユーザーがコマンドラインクライアントを使って REST API にコマンドを発行するの" +"に使用します。管理者ユーザー、 reseller ユーザー、 swift ユーザーのいずれの" +"ユーザーでも使用できます。" + msgid "" "Encrypted HTTP communications using SSL or TLS; most OpenStack API endpoints " "and many inter-component communications support HTTPS communication." @@ -3827,6 +3957,10 @@ msgstr "" msgid "FakeLDAP" msgstr "FakeLDAP" +msgid "" +"Fast provisioning of Hadoop clusters on OpenStack for development and QA." +msgstr "開発や QA 目的での Hadoop クラスターの OpenStack 上への迅速な構築" + msgid "" "Feature in modern Ethernet networks that supports frames up to approximately " "9000 bytes." @@ -3931,6 +4065,18 @@ msgstr "" "クストレージボリュームを作成し、物理デバイスからデータをコピーしてから、デバ" "イスの所有権をエンドユーザーに転送する。" +msgid "" +"For communication between the processes of one service, an AMQP message " +"broker is used. The service's state is stored in a database. When deploying " +"and configuring your OpenStack cloud, you can choose among several message " +"broker and database solutions, such as RabbitMQ, Qpid, MySQL, MariaDB, and " +"SQLite." +msgstr "" +"あるサービス内のプロセス間の通信には、 AMQP メッセージブローカーが使用されま" +"す。サービスの状態はデータベースに保存されます。 OpenStack クラウドをデプロイ" +"する際には、メッセージブローカーとデータベースを RabbitMQ、 Qpid、 MySQL、 " +"MariaDB、 SQLite などのいくつかの選択肢から選択できます。" + msgid "" "For details about image creation, see the `Virtual Machine Image Guide " "`__." @@ -4017,6 +4163,18 @@ msgstr "FormPost" msgid "Free up space in a thinly-provisioned back end." msgstr "シンプロビジョニングされたバックエンドで空き容量を解放する" +msgid "" +"From a network architecture point of view, this service must be accessible " +"to customers and the public API for each OpenStack service. To use the " +"administrator functionality for other services, it must also connect to " +"Admin API endpoints, which should not be accessible by customers." +msgstr "" +"ネットワークアーキテクチャーの観点で見ると、このサービスは顧客からアクセスす" +"ることができる必要があると同時に、各 OpenStack サービスのパブリック API にも" +"アクセスできる必要があります。他の OpenStack サービスの管理機能を利用するに" +"は、管理 API エンドポイントにもアクセスできる必要があります。管理 API エンド" +"ポイントは顧客からはアクセスできないようにすべきです。" + msgid "" "From the :guilabel:`Admin` tab, you can access the following category to " "complete these tasks:" @@ -4462,6 +4620,9 @@ msgstr "" "ゲスト仮想マシンの超えられない制限。合計メモリー容量、最大仮想 CPU 数、最大" "ディスク容量の設定。" +msgid "Implemented as a filesystem underlying OpenStack Compute" +msgstr "OpenStack Compute が動作するファイルシステムとして実装" + msgid "" "In Compute and Block Storage, the ability to set resource limits on a per-" "project basis." @@ -4647,6 +4808,13 @@ msgstr "" "インスタンスの展開、インスタンスのライフサイクルの管理、インスタンス上の処理" "の実行をサポートする複雑なシステムフローを備えます。" +msgid "" +"Integration with vendor specific management tools, such as Apache Ambari or " +"Cloudera Management Console." +msgstr "" +"ベンダー固有の管理ツールとの統合。 Apache Ambari や Cloudera Management " +"Console など。" + msgid "" "Intelligent Platform Management Interface. IPMI is a standardized computer " "system interface used by system administrators for out-of-band management of " @@ -4670,6 +4838,32 @@ msgstr "" "送、Object Storage のオブジェクトの完全性検査など、ユーザーから見えにくい操作" "や処理。" +msgid "" +"Interacts directly with the Block Storage service, and processes such as the " +"cinder-scheduler. It also interacts with these processes through a message " +"queue. The cinder-volume service responds to read and write requests sent to " +"the Block Storage service to maintain state. It can interact with a variety " +"of storage providers through a driver architecture." +msgstr "" +"cinder-scheduler などの Block Storage サービスやプロセスと直接やり取りを行い" +"ます。また、メッセージキュー経由でもこれらのプロセスと連携します。 cinder-" +"volume サービスは、Block Storage サービスへ送られた読み出し、書き込みリクエス" +"トに応答し、状態を管理します。ドライバーアーキテクチャーになっており、様々な" +"ストレージプロバイダーと連携できます。" + +msgid "" +"Interacts directly with the Shared File Systems service and processes such " +"as the manila-scheduler. It also interacts with these processes through a " +"message queue. The manila-share service responds to read and write requests " +"sent to the Shared File Systems service to maintain state. It can interact " +"with a variety of storage providers through a driver architecture." +msgstr "" +"manila-scheduler などの Shared File Systems サービスやプロセスと直接やり取り" +"を行います。また、メッセージキュー経由でもこれらのプロセスと連携します。 " +"manila-share サービスは、Shared File Systems サービスへ送られた読み出し、書き" +"込みリクエストに応答し、状態を管理します。ドライバーアーキテクチャーになって" +"おり、様々なストレージプロバイダーと連携できます。" + msgid "" "Interface within Networking that enables organizations to create custom plug-" "ins for advanced features, such as QoS, ACLs, or IDS." @@ -4677,6 +4871,19 @@ msgstr "" "組織が QoS、ACL、IDS などの高度な機能向けのカスタムプラグインを作成できるよう" "にする、Networking 内のインターフェース。" +msgid "" +"Internally, OpenStack services are composed of several processes. All " +"services have at least one API process, which listens for API requests, " +"preprocesses them and passes them on to other parts of the service. With the " +"exception of the Identity service, the actual work is done by distinct " +"processes." +msgstr "" +"内部では、 それぞれの OpenStack サービスは複数のプロセスから構成されていま" +"す。すべてのサービスには少なくとも 1 つの API プロセスがあり、この API プロセ" +"スは API リクエストを待ち受け、API リクエストの前処理を行ってから、そのサービ" +"スの別の構成要素にそのリクエストを渡します。実際の処理は別のプロセスによって" +"行わます。ただし、 Identity service は例外です。" + msgid "" "Internally, each command uses cURL command-line tools, which embed API " "requests. OpenStack APIs are RESTful APIs, and use the HTTP protocol. They " @@ -4731,7 +4938,7 @@ msgid "Key Manager service" msgstr "Key Manager サービス" msgid "Key features are:" -msgstr "主要機能:" +msgstr "主要機能な以下の通りです。" msgid "Key management service" msgstr "Key management サービス" @@ -4923,6 +5130,12 @@ msgstr "イメージの管理" msgid "Manage volumes" msgstr "ボリュームの管理" +msgid "" +"Managed through REST API with UI available as part of OpenStack dashboard." +msgstr "" +"REST API 経由で管理でき、 OpenStack dashboard の一部として UI も提供されてい" +"ます。" + msgid "Manages accounts defined with Object Storage." msgstr "Object Storage で定義されるアカウントを管理します。" @@ -5585,6 +5798,16 @@ msgstr "" msgid "OpenStack mailing lists" msgstr "OpenStack メーリングリスト" +msgid "" +"OpenStack project that aims to make cloud services easier to consume and " +"integrate with application development process by automating the source-to-" +"image process, and simplifying app-centric deployment. The project name is " +"solum." +msgstr "" +"クラウドサービスをより簡単に利用し、アプリケーション開発プロセスと統合するこ" +"とを目的とする OpenStack プロジェクト。ソースからイメージまでの手順を自動化" +"し、アプリケーション中心の開発を単純化します。プロジェクト名は solum。" + msgid "" "OpenStack project that aims to produce an OpenStack messaging service that " "affords a variety of distributed application patterns in an efficient, " @@ -5808,6 +6031,11 @@ msgstr "" "で、ネイティブの HOT テンプレート形式または AWS CloudFormation テンプレート形" "式を使用することにより、複数の混合クラウドアプリケーションを統合します。" +msgid "" +"Orchestrates the launching of templates and provides events back to the API " +"consumer." +msgstr "テンプレートの起動全体を指揮し、API 利用者に返すイベントを生成します。" + msgid "Orchestration" msgstr "Orchestration" @@ -6063,6 +6291,13 @@ msgstr "" "る OpenStack サービスを操作するために、ウェブベースのセルフサービスポータルを" "提供します。" +msgid "" +"Provides an OpenStack-native RESTful API that supports JSON to provision and " +"manage Trove instances." +msgstr "" +"Trove インスタンスの作成と管理を行うための、JSON に対応した OpenStack 固有の " +"RESTful API を提供します。" + msgid "" "Provides an authentication and authorization service for other OpenStack " "services. Provides a catalog of endpoints for all OpenStack services." @@ -6641,6 +6876,14 @@ msgstr "" msgid "Storage repository for image files" msgstr "イメージファイルのストレージリポジトリー" +msgid "" +"Storage ring build and rebalance utility. Documented in http://docs." +"openstack.org/developer/swift/admin_guide.html#managing-the-rings." +msgstr "" +"ストレージリングの作成とリバランスを行うツール。ドキュメントは http://docs." +"openstack.org/developer/swift/admin_guide.html#managing-the-rings にありま" +"す。" + msgid "Storage types" msgstr "ストレージ種別" @@ -6700,7 +6943,7 @@ msgstr "" "物理 CPU を分割する。インスタンスは、これらの分割したものを使用できる。" msgid "Support for different Hadoop distributions:" -msgstr "さまざまな Hadoop ディストリビューションのサポート:" +msgstr "さまざまな Hadoop ディストリビューションをサポートしています。" msgid "Supported model values" msgstr "サポートされるモデルの値" @@ -6892,6 +7135,23 @@ msgstr "" msgid "The Compute setting that enables or disables RAM overcommitment." msgstr "RAM オーバーコミットを有効化または無効化する Compute の設定。" +msgid "" +"The Data processing service for OpenStack (sahara) aims to provide users " +"with a simple means to provision data processing (Hadoop, Spark) clusters by " +"specifying several parameters like Hadoop version, cluster topology, node " +"hardware details and a few more. After a user fills in all the parameters, " +"the Data processing service deploys the cluster in a few minutes. Sahara " +"also provides a means to scale already provisioned clusters by adding or " +"removing worker nodes on demand." +msgstr "" +"OpenStack 用 Data processing サービス (sahara) の目的は、 Hadoop バージョン、" +"クラスターのトポロジー、ノードハードウェアの詳細などのいくつかのパラメーター" +"を指定するだけで、(Hadoop や Spark の) データ処理クラスターをセットアップする" +"簡単な方法をユーザーに提供することです。ユーザーが必要なパラメーターをすべて" +"入力すると、 Data processing サービスは数分でクラスターを展開します。 要求に" +"応じてワーカーノードの追加、削除を行って、すでに展開済みのクラスターのサイズ" +"を変更する手段も提供しています。" + msgid "The Database service includes the following components:" msgstr "Database は以下のコンポーネントを含みます。" @@ -7001,6 +7261,20 @@ msgstr "" "OpenLDAP、OpenStack Identity などの認証サービスのユーザーアカウントと混同しな" "いこと。" +msgid "" +"The OpenStack :term:`Identity service ` provides a single point of " +"integration for managing authentication, authorization, and service catalog " +"services. Other OpenStack services use the Identity service as a common " +"unified API. Additionally, services that provide information about users but " +"that are not included in OpenStack (such as LDAP services) can be integrated " +"into a pre-existing infrastructure." +msgstr "" +"OpenStack :term:`Identity service ` は、認証、認可、サービスカタロ" +"グサービスを管理する OpenStack で唯一のサービスです。他の OpenStack サービス" +"は共通の統一 API として Identity service を使用します。また、ユーザー関連の情" +"報を提供する OpenStack 外のサービス (LDAP サービスなど) なども既存のインフラ" +"に統合できます。" + msgid "" "The OpenStack Administrator configures the basic infrastructure using the " "following steps:" @@ -7025,6 +7299,20 @@ msgstr "OpenStack IRC チャネル" msgid "The OpenStack Image service includes the following components:" msgstr "OpenStack Image service は、以下のコンポーネントを含みます。" +msgid "" +"The OpenStack Image service is central to Infrastructure-as-a-Service (IaaS) " +"as shown in :ref:`get_started_conceptual_architecture`. It accepts API " +"requests for disk or server images, and image metadata from end users or " +"OpenStack Compute components. It also supports the storage of disk or server " +"images on various repository types, including OpenStack Object Storage." +msgstr "" +"OpenStack Image service は、:ref:`get_started_conceptual_architecture`に書か" +"れているように Infrastructure-as-a-Service (IaaS) の中核です。エンドユーザー" +"や OpenStack Compute のコンポーネントからの、ディスクやサーバーイメージ、イ" +"メージメタデータに関する API リクエストを受け付けます。ディスクやサーバーイ" +"メージの保管場所として、OpenStack Object Storage などの様々な種類のレポジト" +"リーに対応しています。" + msgid "" "The OpenStack Object Storage is a multi-tenant object storage system. It is " "highly scalable and can manage large amounts of unstructured data at low " @@ -7034,6 +7322,19 @@ msgstr "" "です。高いスケーラビリティーを持ちます。RESTful HTTP API 経由で大規模な非構造" "データを低コストで管理できます。" +msgid "" +"The OpenStack Shared File Systems service (manila) provides file storage to " +"a virtual machine. The Shared File Systems service provides an " +"infrastructure for managing shares and provides access to shares to " +"instances. The service also enables management of share types as well as " +"share snapshots if a driver supports snapshots." +msgstr "" +"OpenStack Shared Files Systems サービス (manila) は、仮想マシンにファイルスト" +"レージを提供します。 Shared File Systems サービスは、ファイル共有を管理し、イ" +"ンスタンスに共有へのアクセスを提供するための基盤を提供します。共有種別を管理" +"することができ、ドライバーがスナップショットに対応している場合には共有のス" +"ナップショットを取ることもできます。" + msgid "" "The OpenStack community lives in the #openstack IRC channel on the Freenode " "network. You can hang out, ask questions, or get immediate feedback for " @@ -7155,6 +7456,40 @@ msgstr "" "ティ、豊富な機能を目指しています。世界中の開発者とクラウドコンピューティング" "技術者が the OpenStack project を作成します。" +msgid "" +"The OpenStack project that OpenStack project that implements clustering " +"services and libraries for the management of groups of homogeneous objects " +"exposed by other OpenStack services. The project name of Clustering service " +"is senlin." +msgstr "" +"クラスタリングサービスと、他の OpenStack サービスにより公開された均質なオブ" +"ジェクトグループを管理するためのライブラリーを実現する OpenStack プロジェク" +"ト。このプロジェクトのコード名は senlin。" + +msgid "" +"The OpenStack project that provides a multi-tenant, highly scalable, " +"performant, fault-tolerant Monitoring-as-a-Service solution for metrics, " +"complex event processing, and logging. It builds an extensible platform for " +"advanced monitoring services that can be used by both operators and tenants " +"to gain operational insight and visibility, ensuring availability and " +"stability. The project name is monasca." +msgstr "" +"マルチテナントで、高いスケーラビリティーを持ち、高性能で、耐障害性のある、" +"Monitoring-as-a-Service ソリューションを提供する OpenStack プロジェクト。 計" +"測情報、複合イベント処理 (complex event processing)、ログ監視が対象。オペレー" +"ター、テナントの両者が利用できる、高度なモニタリングサービスに対応できる拡張" +"性のあるプラットフォームを開発しており、可用性と安定性を確保しながら、運用上" +"の問題の特定や可視化を実現できる。プロジェクト名は monasca。" + +msgid "" +"The OpenStack project that provides integrated tooling for backing up, " +"restoring, and recovering file systems, instances, or database backups. The " +"project name is freezer." +msgstr "" +"ファイルシステム、インスタンス、データベースバックアップのバックアップ、リス" +"トア、リカバリー用の統合ツールを提供する OpenStack プロジェクト。プロジェクト" +"名は freezer。" + msgid "The OpenStack stack uses the following storage types:" msgstr "OpenStack のスタックは、以下のストレージ種別を使用します。" @@ -7164,6 +7499,26 @@ msgstr "OpenStack wiki" msgid "The Orchestration service consists of the following components:" msgstr "Orchestration サービスは、以下のコンポーネントから構成されます。" +msgid "" +"The Orchestration service provides a template-based orchestration for " +"describing a cloud application by running OpenStack API calls to generate " +"running cloud applications. The software integrates other core components of " +"OpenStack into a one-file template system. The templates allow you to create " +"most OpenStack resource types, such as instances, floating IPs, volumes, " +"security groups and users. It also provides advanced functionality, such as " +"instance high availability, instance auto-scaling, and nested stacks. This " +"enables OpenStack core projects to receive a larger user base." +msgstr "" +"Orchestration サービスは、クラウドアプリケーションを記述できるテンプレート" +"ベースのオーケストレーション機能を提供します。 OpenStack API を呼び出して、実" +"際に動くクラウドアプリケーションを生成します。このサービスにより、他の " +"OpenStack のコアコンポーネントを 1ファイルのテンプレートシステムに統合できま" +"す。テンプレートを使って、ほとんどの種類の OpenStack リソースを作成できます。" +"例えば、インスタンス、 Floating IP、ボリューム、セキュリティーグループ、ユー" +"ザーなどです。インスタンスの高可用化、インスタンスのオートスケーリング、入れ" +"子になったスタックといった、高度な機能も提供しています。これにより、より多く" +"のユーザーが OpenStack コアプロジェクトを利用することになります。" + msgid "The POSIX-compliant file system provided by Ceph." msgstr "Ceph により提供される POSIX 互換ファイルシステム。" @@ -7939,6 +8294,13 @@ msgstr "" "スに割り当てられたリソースの合計と、ホスト自体の仮想マシンに割り当てられたリ" "ソースを表示します。" +msgid "" +"The service enables deployers to integrate with the Orchestration service " +"directly or through custom plug-ins." +msgstr "" +"オペレーターは 直接、あるいはカスタムプラグイン経由で様々なものを " +"Orchestration サービスと統合できます。" + msgid "" "The software package used to provide AMQP messaging capabilities within " "Compute. Default package is RabbitMQ." @@ -8614,6 +8976,23 @@ msgstr "" "Hive や Pig をベースにした、アドホックな分析クエリー向けのユーザーフレンド" "リーな UI。" +msgid "" +"Users can access OpenStack via the web-based user interface implemented by " +"the :ref:`get_started_dashboard`, via `command-line clients `__ and by issuing API requests through " +"tools like browser plug-ins or :command:`curl`. For applications, `several " +"SDKs `__ are available. Ultimately, all " +"these access methods issue REST API calls to the various OpenStack services." +msgstr "" +"ユーザーが OpenStack にアクセスする方法はいくつかあり、 :ref:" +"`get_started_dashboard` が提供するウェブベースのユーザーインターフェースを使" +"う方法、 `コマンドラインクライアント `__ を使う方法、ブラウザーのプラグインや :command:`curl` " +"のようなツールを使って API リクエストを発行する方法などがあります。アプリケー" +"ション向けには `様々な SDK `__ がありま" +"す。最終的には、これらのアクセスはいずれも各種の OpenStack サービスへの REST " +"API 呼び出しになります。" + msgid "" "Users of Object Storage interact with the service through the proxy server, " "which in turn looks up the location of the requested data within the ring " @@ -8622,6 +9001,12 @@ msgstr "" "Object Storage のユーザーは、リング中にあるリクエストされたデータの場所を参照" "してユーザに結果を返すプロキシサーバーを介して、このサービスに通信する。" +msgid "" +"Utilization of unused compute power from general purpose OpenStack IaaS " +"cloud." +msgstr "" +"汎用的な OpenStack IaaS クラウドの使用されていないコンピュートリソースの活用" + msgid "VIF UUID" msgstr "VIF UUID" diff --git a/doc/glossary/locale/ja.po b/doc/glossary/locale/ja.po index a60b8a4cb6..0311ddc184 100644 --- a/doc/glossary/locale/ja.po +++ b/doc/glossary/locale/ja.po @@ -13,11 +13,11 @@ msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" -"POT-Creation-Date: 2015-11-15 02:57+0000\n" +"POT-Creation-Date: 2015-11-19 03:46+0000\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" -"PO-Revision-Date: 2015-11-14 01:33+0000\n" +"PO-Revision-Date: 2015-11-18 05:12+0000\n" "Last-Translator: Akihiro Motoki \n" "Language: ja\n" "Plural-Forms: nplurals=1; plural=0;\n" @@ -205,6 +205,15 @@ msgstr "" "Object Storage コンテナーとコンテナーメタデータを保存する SQLite データベー" "ス。コンテナーサーバーは、このデータベースにアクセスする。" +msgid "" +"A Shared File Systems service that provides a stable RESTful API. The " +"service authenticates and routes requests throughout the Shared File Systems " +"service. There is python-manilaclient to interact with the API." +msgstr "" +"安定版の RESTful API を提供する Shared File Systems サービス。 Shared File " +"Systems サービスへのすべてのリクエストの認証と転送を行う。この API と通信する" +"ための python-manilaclient が提供されています。" + msgid "" "A VM image that does not save changes made to its volumes and reverts them " "to their original state after the instance is terminated." @@ -952,6 +961,15 @@ msgid "" "the domain." msgstr "特定のドメインに関する情報を指定し、ドメインに所属するレコード。" +msgid "" +"A remote, mountable file system in the context of the Shared File Systems. " +"You can mount a share to, and access a share from, several hosts by several " +"users at a time." +msgstr "" +"Shared File System サービスにおいて、リモートのマウント可能なファイルシステム" +"のこと。同時に、複数のユーザーが複数のホストから、共有をマウントしたり、アク" +"セスしたりできる。" + msgid "A routing algorithm in the Compute RabbitMQ." msgstr "Compute RabbitMQ におけるルーティングアルゴリズム。" @@ -1677,6 +1695,23 @@ msgstr "" "2011年春に登場した OpenStack 関連のプロジェクトリリース。Compute (Nova), " "Object Storage (Swift), Image Service (Glance) が含まれていた。" +msgid "" +"An OpenStack service that provides a set of services for management of " +"shared file systems in a multi-tenant cloud environment. The service is " +"similar to how OpenStack provides block-based storage management through the " +"OpenStack Block Storage service project. With the Shared File Systems " +"service, you can create a remote file system and mount the file system on " +"your instances. You can also read and write data from your instances to and " +"from your file system. The project name of the Shared File Systems service " +"is manila." +msgstr "" +"マルチテナントのクラウド環境で共有ファイルシステムを管理するためのサービス群" +"を提供する OpenStack サービス。 OpenStack がブロックベースのストレージ管理" +"を、 OpenStack Block Storage サービスプロジェクトとして提供しているのと類似し" +"ている。 Shared File Systems サービスを使うと、リモートファイルシステムを作成" +"し、自分のインスタンスからそのファイルシステムをマウントし、インスタンスから" +"そのファイルシステムの読み書きを行える。このプロジェクトのコード名は manila。" + msgid "" "An OpenStack service, such as Compute, Object Storage, or Image service. " "Provides one or more endpoints through which users can access resources and " @@ -1770,6 +1805,17 @@ msgstr "" "指定されたホスト上で現在進行中の build, snapshot, migrate, resize の操作数を" "元に計算される、Compute のキャパシティキャッシュの１要素。" +msgid "" +"An entity in the context of the Shared File Systems that encapsulates " +"interaction with the Networking service. If the driver you selected runs in " +"the mode requiring such kind of interaction, you need to specify the share " +"network to create a share." +msgstr "" +"Shared File System サービスにおいて、Networking サービスとのやり取りを抽象化" +"するエンティティー。選択したドライバーが Networking サービスとのやり取りを必" +"要とするモードで動作している場合、共有を作成する際にネットワーク共有 (share " +"network) を指定する必要がある。" + msgid "" "An entity that maps Object Storage data to partitions. A separate ring " "exists for each service, such as account, object, and container." @@ -2261,6 +2307,9 @@ msgstr "Cloud Infrastructure Management Interface (CIMI)" msgid "Cloudbase-Init" msgstr "Cloudbase-Init" +msgid "Clustering" +msgstr "Clustering" + msgid "Code name for the DNS service project for OpenStack." msgstr "OpenStack の DNS サービスプロジェクトのコード名。" @@ -3545,6 +3594,9 @@ msgstr "モニター (LBaaS)" msgid "Monitor (Mon)" msgstr "モニター (Mon)" +msgid "Monitoring" +msgstr "Monitoring" + msgid "MultiNic" msgstr "MultiNic" @@ -3838,6 +3890,16 @@ msgstr "" "フェースからリソースを配備できる。Apache License 2.0 に基づき許諾されるオープ" "ンソースのプロジェクト。" +msgid "" +"OpenStack project that aims to make cloud services easier to consume and " +"integrate with application development process by automating the source-to-" +"image process, and simplifying app-centric deployment. The project name is " +"solum." +msgstr "" +"クラウドサービスをより簡単に利用し、アプリケーション開発プロセスと統合するこ" +"とを目的とする OpenStack プロジェクト。ソースからイメージまでの手順を自動化" +"し、アプリケーション中心の開発を単純化します。プロジェクト名は solum。" + msgid "" "OpenStack project that aims to produce an OpenStack messaging service that " "affords a variety of distributed application patterns in an efficient, " @@ -3865,6 +3927,19 @@ msgstr "" "OpenStack プロジェクトに共有されるコードを含む Python ライブラリー群を作成す" "る OpenStack プロジェクト。" +msgid "OpenStack project that provides a Clustering service." +msgstr "クラスタリングサービスを提供する OpenStack プロジェクト。" + +msgid "OpenStack project that provides a Monitoring service." +msgstr "モニタリングサービスを提供する OpenStack プロジェクト。" + +msgid "" +"OpenStack project that provides a Software Development Lifecycle Automation " +"service." +msgstr "" +"ソフトウェア開発ライフサイクル自動化サービスを提供する OpenStack プロジェク" +"ト。" + msgid "OpenStack project that provides a dashboard, which is a web interface." msgstr "" "ダッシュボードを提供する OpenStack プロジェクト。Web インターフェース。" @@ -3931,6 +4006,13 @@ msgstr "" "サービスを提供する OpenStack プロジェクト。このプロジェクトのコード名は " "murano。" +msgid "" +"OpenStack project that provides backup restore and disaster recovery as a " +"service." +msgstr "" +"バックアップリストアとディザスターリカバリーをサービスとして提供する " +"OpenStack プロジェクト。" + msgid "OpenStack project that provides compute services." msgstr "コンピュートサービスを提供する OpenStack プロジェクト。" @@ -4374,6 +4456,9 @@ msgstr "" "Compute の仮想マシンインスタンスが送受信できるネットワーク通信量のソフト制" "限。" +msgid "Software Development Lifecycle Automation service" +msgstr "ソフトウェア開発ライフサイクル自動化サービス" + msgid "" "Software component providing the actual implementation for Networking APIs, " "or for Compute APIs, depending on the context." @@ -4778,6 +4863,40 @@ msgstr "" "取得、といった機能を提供する、OpenStack のコアプロジェクト。OpenStack Object " "Storage のプロジェクト名は swift。" +msgid "" +"The OpenStack project that OpenStack project that implements clustering " +"services and libraries for the management of groups of homogeneous objects " +"exposed by other OpenStack services. The project name of Clustering service " +"is senlin." +msgstr "" +"クラスタリングサービスと、他の OpenStack サービスにより公開された均質なオブ" +"ジェクトグループを管理するためのライブラリーを実現する OpenStack プロジェク" +"ト。このプロジェクトのコード名は senlin。" + +msgid "" +"The OpenStack project that provides a multi-tenant, highly scalable, " +"performant, fault-tolerant Monitoring-as-a-Service solution for metrics, " +"complex event processing, and logging. It builds an extensible platform for " +"advanced monitoring services that can be used by both operators and tenants " +"to gain operational insight and visibility, ensuring availability and " +"stability. The project name is monasca." +msgstr "" +"マルチテナントで、高いスケーラビリティーを持ち、高性能で、耐障害性のある、" +"Monitoring-as-a-Service ソリューションを提供する OpenStack プロジェクト。 計" +"測情報、複合イベント処理 (complex event processing)、ログ監視が対象。オペレー" +"ター、テナントの両者が利用できる、高度なモニタリングサービスに対応できる拡張" +"性のあるプラットフォームを開発しており、可用性と安定性を確保しながら、運用上" +"の問題の特定や可視化を実現できる。プロジェクト名は monasca。" + +msgid "" +"The OpenStack project that provides integrated tooling for backing up, " +"restoring, and recovering file systems, instances, or database backups. The " +"project name is freezer." +msgstr "" +"ファイルシステム、インスタンス、データベースバックアップのバックアップ、リス" +"トア、リカバリー用の統合ツールを提供する OpenStack プロジェクト。プロジェクト" +"名は freezer。" + msgid "The POSIX-compliant file system provided by Ceph." msgstr "Ceph により提供される POSIX 互換ファイルシステム。" @@ -5831,6 +5950,9 @@ msgstr "バックエンド操作" msgid "back-end store" msgstr "バックエンドストア" +msgid "backup restore and disaster recovery as a service" +msgstr "backup restore and disaster recovery as a service" + msgid "bandwidth" msgstr "帯域" @@ -6386,6 +6508,9 @@ msgstr "Floating" msgid "floating IP address" msgstr "Floating IP アドレス" +msgid "freezer" +msgstr "freezer" + msgid "front end" msgstr "フロントエンド" @@ -6690,6 +6815,9 @@ msgstr "マイグレーション" msgid "mistral" msgstr "mistral" +msgid "monasca" +msgstr "monasca" + msgid "multi-factor authentication" msgstr "多要素認証" @@ -7179,6 +7307,9 @@ msgstr "分割オブジェクト" msgid "self-service" msgstr "セルフサービス" +msgid "senlin" +msgstr "senlin" + msgid "server" msgstr "サーバー" @@ -7254,6 +7385,9 @@ msgstr "スナップショット" msgid "soft reboot" msgstr "ソフトリブート" +msgid "solum" +msgstr "solum" + msgid "spread-first" msgstr "分散優先" diff --git a/doc/install-guide/source/locale/ja/LC_MESSAGES/install-guide.po b/doc/install-guide/source/locale/ja/LC_MESSAGES/install-guide.po index ddcd448004..3445d64244 100644 --- a/doc/install-guide/source/locale/ja/LC_MESSAGES/install-guide.po +++ b/doc/install-guide/source/locale/ja/LC_MESSAGES/install-guide.po @@ -8,15 +8,16 @@ # Tomoyuki KATO , 2013-2015 # yfukuda , 2013 # Akihiro Motoki , 2015. #zanata +# KATO Tomoyuki , 2015. #zanata msgid "" msgstr "" "Project-Id-Version: Installation Guide 0.1\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2015-11-18 05:45+0000\n" +"POT-Creation-Date: 2015-11-19 03:46+0000\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" -"PO-Revision-Date: 2015-11-17 10:31+0000\n" +"PO-Revision-Date: 2015-11-18 07:38+0000\n" "Last-Translator: Akihiro Motoki \n" "Language: ja\n" "Plural-Forms: nplurals=1; plural=0;\n" @@ -4409,7 +4410,7 @@ msgid "Restart the Orchestration services:" msgstr "Orchestration を再起動します。" msgid "Restart the Telemetry services:" -msgstr "Telemetry のサービスを再起動します。" +msgstr "Telemetry サービスを再起動します。" msgid "Restart the agent:" msgstr "エージェントを再起動します。" diff --git a/doc/networking-guide/source/locale/networking-guide.pot b/doc/networking-guide/source/locale/networking-guide.pot index 87c136b7c1..15ce2a299a 100644 --- a/doc/networking-guide/source/locale/networking-guide.pot +++ b/doc/networking-guide/source/locale/networking-guide.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Networking Guide 0.9\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2015-11-18 06:16+0000\n" +"POT-Creation-Date: 2015-11-19 06:16+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -1222,8 +1222,9 @@ msgstr "" #: ../adv_config_qos.rst:29 msgid "" "Details about the DB models, API extension, and use cases are out of the " -"scope of this guide but can be found here: `qos spec `" +"scope of this guide but can be found in the `Neutron QoS specification " +"`_." msgstr "" #: ../adv_config_qos.rst:35 @@ -1954,7 +1955,7 @@ msgstr "" # #-#-#-#-# config_ml2_plug_in.pot (Networking Guide 0.9) #-#-#-#-# # #-#-#-#-# intro_basic_networking.pot (Networking Guide 0.9) #-#-#-#-# # #-#-#-#-# intro_os_networking_service.pot (Networking Guide 0.9) #-#-#-#-# -#: ../config_ml2_plug_in.rst:88 ../intro_basic_networking.rst:228 +#: ../config_ml2_plug_in.rst:88 ../intro_basic_networking.rst:227 #: ../intro_os_networking_service.rst:51 msgid "DHCP" msgstr "" @@ -2054,19 +2055,18 @@ msgstr "" #: ../intro_basic_networking.rst:16 msgid "" "In an Ethernet network, the hosts connected to the network communicate by " -"exchanging *frames*, which is the Ethernet terminology for packets. Every " -"host on an Ethernet network is uniquely identified by an address called the " -"media access control (MAC) address. In particular, in an OpenStack " -"environment, every virtual machine instance has a unique MAC address, which " -"is different from the MAC address of the compute host. A MAC address has 48 " -"bits and is typically represented as a hexadecimal string, such as " -"``08:00:27:b9:88:74``. The MAC address is hard-coded into the NIC by the " -"manufacturer, although modern NICs allow you to change the MAC address " -"programatically. In Linux, you can retrieve the MAC address of a NIC using " -"the ``ip`` command::" +"exchanging *frames*. Every host on an Ethernet network is uniquely " +"identified by an address called the media access control (MAC) address. In " +"particular, in an OpenStack environment, every virtual machine instance has " +"a unique MAC address, which is different from the MAC address of the compute " +"host. A MAC address has 48 bits and is typically represented as a " +"hexadecimal string, such as ``08:00:27:b9:88:74``. The MAC address is hard-" +"coded into the NIC by the manufacturer, although modern NICs allow you to " +"change the MAC address programatically. In Linux, you can retrieve the MAC " +"address of a NIC using the ``ip`` command::" msgstr "" -#: ../intro_basic_networking.rst:32 +#: ../intro_basic_networking.rst:31 msgid "" "Conceptually, you can think of an Ethernet network as a single bus that each " "of the network hosts connects to. In early implementations, an Ethernet " @@ -2079,7 +2079,7 @@ msgid "" "Ethernet network referred to as a *layer 2 segment*." msgstr "" -#: ../intro_basic_networking.rst:43 +#: ../intro_basic_networking.rst:42 msgid "" "In an Ethernet network, every host on the network can send a frame directly " "to every other host. An Ethernet network also supports broadcasts, so that " @@ -2090,7 +2090,7 @@ msgid "" "*broadcast domain*." msgstr "" -#: ../intro_basic_networking.rst:51 +#: ../intro_basic_networking.rst:50 msgid "" "When a NIC receives an Ethernet frame, by default the NIC checks to see if " "the destination MAC address matches the address of the NIC (or the broadcast " @@ -2102,7 +2102,7 @@ msgid "" "have the appropriate NICs configured for promiscuous mode." msgstr "" -#: ../intro_basic_networking.rst:61 +#: ../intro_basic_networking.rst:60 msgid "" "As mentioned earlier, modern Ethernet networks use switches to interconnect " "the network hosts. A switch is a box of networking hardware with a large " @@ -2119,11 +2119,11 @@ msgid "" "connection of switches and hosts behaves like a single network." msgstr "" -#: ../intro_basic_networking.rst:79 +#: ../intro_basic_networking.rst:78 msgid "VLANs" msgstr "" -#: ../intro_basic_networking.rst:81 +#: ../intro_basic_networking.rst:80 msgid "" "VLAN is a networking technology that enables a single switch to act as if it " "was multiple independent switches. Specifically, two hosts that are " @@ -2134,7 +2134,7 @@ msgid "" "1 and 4095. We say \"VLAN 15\" to refer to the VLAN with numerical ID of 15." msgstr "" -#: ../intro_basic_networking.rst:90 +#: ../intro_basic_networking.rst:89 msgid "" "To understand how VLANs work, let's consider VLAN applications in a " "traditional IT environment, where physical hosts are attached to a physical " @@ -2149,7 +2149,7 @@ msgid "" "VLANs." msgstr "" -#: ../intro_basic_networking.rst:102 +#: ../intro_basic_networking.rst:101 msgid "" "Now consider the scenario that all of the switchports in the first switch " "become occupied, and so the organization buys a second switch and connects " @@ -2161,7 +2161,7 @@ msgid "" "switch 2, it must communicate that the frame is associated with VLAN ID 10." msgstr "" -#: ../intro_basic_networking.rst:112 +#: ../intro_basic_networking.rst:111 msgid "" "If two switches are to be connected together, and the switches are " "configured for VLANs, then the switchports used for cross-connecting the " @@ -2171,7 +2171,7 @@ msgid "" "only hosts on the matching VLAN are eligible to receive the frame." msgstr "" -#: ../intro_basic_networking.rst:119 +#: ../intro_basic_networking.rst:118 msgid "" "When a switchport is configured to pass frames from all VLANs and tag them " "with the VLAN IDs it is called a *trunk port*. IEEE 802.1Q is the network " @@ -2179,14 +2179,14 @@ msgid "" "trunking is being used." msgstr "" -#: ../intro_basic_networking.rst:124 +#: ../intro_basic_networking.rst:123 msgid "" "Note that if you are using VLANs on your physical switches to implement " "tenant isolation in your OpenStack cloud, you must ensure that all of your " "switchports are configured as trunk ports." msgstr "" -#: ../intro_basic_networking.rst:128 +#: ../intro_basic_networking.rst:127 msgid "" "It is important that you select a VLAN range that your current network " "infrastructure is not using. For example, if you estimate that your cloud " @@ -2196,25 +2196,25 @@ msgid "" "range." msgstr "" -#: ../intro_basic_networking.rst:134 +#: ../intro_basic_networking.rst:133 msgid "" "Trunking is used to connect between different switches. Each trunk uses a " "tag to identify which VLAN is in use. This ensures that switches on the same " "VLAN can communicate." msgstr "" -#: ../intro_basic_networking.rst:142 +#: ../intro_basic_networking.rst:141 msgid "Subnets and ARP" msgstr "" -#: ../intro_basic_networking.rst:144 +#: ../intro_basic_networking.rst:143 msgid "" "While NICs use MAC addresses to address network hosts, TCP/IP applications " "use IP addresses. The Address Resolution Protocol (ARP) bridges the gap " "between Ethernet and IP by translating IP addresses into MAC addresses." msgstr "" -#: ../intro_basic_networking.rst:148 +#: ../intro_basic_networking.rst:147 msgid "" "IP addresses are broken up into two parts: a *network number* and a *host " "identifier*. Two hosts are on the same *subnet* if they have the same " @@ -2226,26 +2226,26 @@ msgid "" "local network, otherwise ARP does not work properly." msgstr "" -#: ../intro_basic_networking.rst:157 +#: ../intro_basic_networking.rst:156 msgid "" "To calculate the network number of an IP address, you must know the " "*netmask* associated with the address. A netmask indicates how many of the " "bits in the 32-bit IP address make up the network number." msgstr "" -#: ../intro_basic_networking.rst:161 +#: ../intro_basic_networking.rst:160 msgid "There are two syntaxes for expressing a netmask:" msgstr "" -#: ../intro_basic_networking.rst:163 +#: ../intro_basic_networking.rst:162 msgid "dotted quad" msgstr "" -#: ../intro_basic_networking.rst:164 +#: ../intro_basic_networking.rst:163 msgid "classless inter-domain routing (CIDR)" msgstr "" -#: ../intro_basic_networking.rst:166 +#: ../intro_basic_networking.rst:165 msgid "" "Consider an IP address of 192.168.1.5, where the first 24 bits of the " "address are the network number. In dotted quad notation, the netmask would " @@ -2253,14 +2253,14 @@ msgid "" "and netmask, and this example would be written as ``192.168.1.5/24``." msgstr "" -#: ../intro_basic_networking.rst:173 +#: ../intro_basic_networking.rst:172 msgid "" "Creating CIDR subnets including a multicast address or a loopback address " "cannot be used in an OpenStack environment. For example, creating a subnet " "using ``224.0.0.0/16`` or ``127.0.1.0/24`` is not supported." msgstr "" -#: ../intro_basic_networking.rst:177 +#: ../intro_basic_networking.rst:176 msgid "" "Sometimes we want to refer to a subnet, but not any particular IP address on " "the subnet. A common convention is to set the host identifier to all zeros " @@ -2268,7 +2268,7 @@ msgid "" "``10.10.53.24/16``, then we would say the subnet is ``10.10.0.0/16``." msgstr "" -#: ../intro_basic_networking.rst:183 +#: ../intro_basic_networking.rst:182 msgid "" "To understand how ARP translates IP addresses to MAC addresses, consider the " "following example. Assume host *A* has an IP address of ``192.168.1.5/24`` " @@ -2278,40 +2278,40 @@ msgid "" "host *B*." msgstr "" -#: ../intro_basic_networking.rst:190 +#: ../intro_basic_networking.rst:189 msgid "" "The first time host *A* attempts to communicate with host *B*, the " "destination MAC address is not known. Host *A* makes an ARP request to the " "local network. The request is a broadcast with a message like this:" msgstr "" -#: ../intro_basic_networking.rst:195 +#: ../intro_basic_networking.rst:194 msgid "" "*To: everybody (ff:ff:ff:ff:ff:ff). I am looking for the computer who has IP " "address 192.168.1.7. Signed: MAC address fc:99:47:49:d4:a0*." msgstr "" -#: ../intro_basic_networking.rst:198 +#: ../intro_basic_networking.rst:197 msgid "Host *B* responds with a response like this:" msgstr "" -#: ../intro_basic_networking.rst:200 +#: ../intro_basic_networking.rst:199 msgid "" "*To: fc:99:47:49:d4:a0. I have IP address 192.168.1.7. Signed: MAC address " "54:78:1a:86:00:a5.*" msgstr "" -#: ../intro_basic_networking.rst:203 +#: ../intro_basic_networking.rst:202 msgid "Host *A* then sends Ethernet frames to host *B*." msgstr "" -#: ../intro_basic_networking.rst:205 +#: ../intro_basic_networking.rst:204 msgid "" "You can initiate an ARP request manually using the *arping* command. For " "example, to send an ARP request to IP address ``10.30.0.132``::" msgstr "" -#: ../intro_basic_networking.rst:216 +#: ../intro_basic_networking.rst:215 msgid "" "To reduce the number of ARP requests, operating systems maintain an ARP " "cache that contains the mappings of IP addresses to MAC address. On a Linux " @@ -2319,14 +2319,14 @@ msgid "" "command::" msgstr "" -#: ../intro_basic_networking.rst:230 +#: ../intro_basic_networking.rst:229 msgid "" "Hosts connected to a network use the Dynamic Host Configuration Protocol (:" "term:`DHCP`) to dynamically obtain IP addresses. A DHCP server hands out the " "IP addresses to network hosts, which are the DHCP clients." msgstr "" -#: ../intro_basic_networking.rst:235 +#: ../intro_basic_networking.rst:234 msgid "" "DHCP clients locate the DHCP server by sending a UDP_ packet from port 68 to " "address ``255.255.255.255`` on port 67. Address ``255.255.255.255`` is the " @@ -2338,49 +2338,49 @@ msgid "" "client. The exchange looks like this:" msgstr "" -#: ../intro_basic_networking.rst:245 +#: ../intro_basic_networking.rst:244 msgid "" "The client sends a discover (\"I’m a client at MAC address ``08:00:27:" "b9:88:74``, I need an IP address\")" msgstr "" -#: ../intro_basic_networking.rst:247 +#: ../intro_basic_networking.rst:246 msgid "" "The server sends an offer (\"OK ``08:00:27:b9:88:74``, I’m offering IP " "address ``10.10.0.112``\")" msgstr "" -#: ../intro_basic_networking.rst:249 +#: ../intro_basic_networking.rst:248 msgid "" "The client sends a request (\"Server ``10.10.0.131``, I would like to have " "IP ``10.10.0.112``\")" msgstr "" -#: ../intro_basic_networking.rst:251 +#: ../intro_basic_networking.rst:250 msgid "" "The server sends an acknowledgement (\"OK ``08:00:27:b9:88:74``, IP " "``10.10.0.112`` is yours\")" msgstr "" -#: ../intro_basic_networking.rst:255 +#: ../intro_basic_networking.rst:254 msgid "" "OpenStack uses a third-party program called dnsmasq_ to implement the DHCP " "server. Dnsmasq writes to the syslog, where you can observe the DHCP request " "and replies::" msgstr "" -#: ../intro_basic_networking.rst:265 +#: ../intro_basic_networking.rst:264 msgid "" "When troubleshooting an instance that is not reachable over the network, it " "can be helpful to examine this log to verify that all four steps of the DHCP " "protocol were carried out for the instance in question." msgstr "" -#: ../intro_basic_networking.rst:274 +#: ../intro_basic_networking.rst:273 msgid "IP" msgstr "" -#: ../intro_basic_networking.rst:276 +#: ../intro_basic_networking.rst:275 msgid "" "The Internet Protocol (IP) specifies how to route packets between hosts that " "are connected to different local networks. IP relies on special network " @@ -2390,14 +2390,14 @@ msgid "" "networks it is connected to." msgstr "" -#: ../intro_basic_networking.rst:283 +#: ../intro_basic_networking.rst:282 msgid "" "In the OSI model of networking protocols, IP occupies the third layer, which " "is known as the network layer. When discussing IP, you will often hear terms " "such as *layer 3*, *L3*, and *network layer*." msgstr "" -#: ../intro_basic_networking.rst:287 +#: ../intro_basic_networking.rst:286 msgid "" "A host sending a packet to an IP address consults its *routing table* to " "determine which machine on the local network(s) the packet should be sent " @@ -2406,17 +2406,17 @@ msgid "" "routers that are on these local networks." msgstr "" -#: ../intro_basic_networking.rst:293 +#: ../intro_basic_networking.rst:292 msgid "" "On a Linux machine, any of the following commands displays the routing " "table::" msgstr "" -#: ../intro_basic_networking.rst:299 +#: ../intro_basic_networking.rst:298 msgid "Here is an example of output from ``ip route show``::" msgstr "" -#: ../intro_basic_networking.rst:307 +#: ../intro_basic_networking.rst:306 msgid "" "Line 1 of the output specifies the location of the default route, which is " "the effective routing rule if none of the other rules match. The router " @@ -2426,45 +2426,45 @@ msgid "" "with the client's IP address and a netmask." msgstr "" -#: ../intro_basic_networking.rst:314 +#: ../intro_basic_networking.rst:313 msgid "" "Line 2 of the output specifies that IPs in the 10.0.2.0/24 subnet are on the " "local network associated with the network interface eth0." msgstr "" -#: ../intro_basic_networking.rst:317 +#: ../intro_basic_networking.rst:316 msgid "" "Line 3 of the output specifies that IPs in the 192.168.27.0/24 subnet are on " "the local network associated with the network interface eth1." msgstr "" -#: ../intro_basic_networking.rst:320 +#: ../intro_basic_networking.rst:319 msgid "" "Line 4 of the output specifies that IPs in the 192.168.122/24 subnet are on " "the local network associated with the network interface virbr0." msgstr "" -#: ../intro_basic_networking.rst:323 +#: ../intro_basic_networking.rst:322 msgid "" "The output of the ``route -n`` and ``netstat -rn`` commands are formatted in " "a slightly different way. This example shows how the same routes would be " "formatted using these commands::" msgstr "" -#: ../intro_basic_networking.rst:335 +#: ../intro_basic_networking.rst:334 msgid "" "The ``ip route get`` command outputs the route for a destination IP address. " "From the above example, destination IP address 10.0.2.14 is on the local " "network of eth0 and would be sent directly::" msgstr "" -#: ../intro_basic_networking.rst:342 +#: ../intro_basic_networking.rst:341 msgid "" "The destination IP address 93.184.216.34 is not on any of the connected " "local networks and would be forwarded to the default gateway at 10.0.2.2::" msgstr "" -#: ../intro_basic_networking.rst:348 +#: ../intro_basic_networking.rst:347 msgid "" "It is common for a packet to hop across multiple routers to reach its final " "destination. On a Linux machine, the ``traceroute`` and more recent ``mtr`` " @@ -2472,11 +2472,11 @@ msgid "" "traverses along its path to its destination." msgstr "" -#: ../intro_basic_networking.rst:356 +#: ../intro_basic_networking.rst:355 msgid "TCP/UDP/ICMP" msgstr "" -#: ../intro_basic_networking.rst:358 +#: ../intro_basic_networking.rst:357 msgid "" "For networked software applications to communicate over an IP network, they " "must use a protocol layered atop IP. These protocols occupy the fourth layer " @@ -2486,7 +2486,7 @@ msgid "" "associated numbers." msgstr "" -#: ../intro_basic_networking.rst:367 +#: ../intro_basic_networking.rst:366 msgid "" "The *Transmission Control Protocol* (TCP) is the most commonly used layer 4 " "protocol in networked applications. TCP is a *connection-oriented* protocol: " @@ -2495,19 +2495,19 @@ msgid "" "interaction in a TCP-based application proceeds as follows:" msgstr "" -#: ../intro_basic_networking.rst:375 +#: ../intro_basic_networking.rst:374 msgid "Client connects to server." msgstr "" -#: ../intro_basic_networking.rst:376 +#: ../intro_basic_networking.rst:375 msgid "Client and server exchange data." msgstr "" -#: ../intro_basic_networking.rst:377 +#: ../intro_basic_networking.rst:376 msgid "Client or server disconnects." msgstr "" -#: ../intro_basic_networking.rst:379 +#: ../intro_basic_networking.rst:378 msgid "" "Because a network host may have multiple TCP-based applications running, TCP " "uses an addressing scheme called *ports* to uniquely identify TCP-based " @@ -2516,7 +2516,7 @@ msgid "" "time, a restriction that is enforced by the operating system." msgstr "" -#: ../intro_basic_networking.rst:385 +#: ../intro_basic_networking.rst:384 msgid "" "A TCP server is said to *listen* on a port. For example, an SSH server " "typically listens on port 22. For a client to connect to a server using TCP, " @@ -2524,7 +2524,7 @@ msgid "" "TCP port." msgstr "" -#: ../intro_basic_networking.rst:390 +#: ../intro_basic_networking.rst:389 msgid "" "The operating system of the TCP client application automatically assigns a " "port number to the client. The client owns this port number until the TCP " @@ -2532,7 +2532,7 @@ msgid "" "port number. These types of ports are referred to as *ephemeral ports*." msgstr "" -#: ../intro_basic_networking.rst:396 +#: ../intro_basic_networking.rst:395 msgid "" "IANA maintains a `registry of port numbers`_ for many TCP-based services, as " "well as services that use other layer 4 protocols that employ ports. " @@ -2543,7 +2543,7 @@ msgid "" "deployment." msgstr "" -#: ../intro_basic_networking.rst:409 +#: ../intro_basic_networking.rst:408 msgid "" "The most common application programming interface (API) for writing TCP-" "based applications is called *Berkeley sockets*, also known as *BSD sockets* " @@ -2561,7 +2561,7 @@ msgid "" "*reliable* protocol." msgstr "" -#: ../intro_basic_networking.rst:424 +#: ../intro_basic_networking.rst:423 msgid "" "The *User Datagram Protocol* (UDP) is another layer 4 protocol that is the " "basis of several well-known networking protocols. UDP is a *connectionless* " @@ -2573,7 +2573,7 @@ msgid "" "they were sent in." msgstr "" -#: ../intro_basic_networking.rst:433 +#: ../intro_basic_networking.rst:432 msgid "" "UDP, like TCP, uses the notion of ports to distinguish between different " "applications running on the same system. Note, however, that operating " @@ -2582,7 +2582,7 @@ msgid "" "separate application to be associated with UDP port 16543." msgstr "" -#: ../intro_basic_networking.rst:439 +#: ../intro_basic_networking.rst:438 msgid "" "Like TCP, the sockets API is the most common API for writing UDP-based " "applications. The sockets API provides a *message-oriented* interface for " @@ -2592,14 +2592,14 @@ msgid "" "responsible for implementing this functionality in the application code." msgstr "" -#: ../intro_basic_networking.rst:446 +#: ../intro_basic_networking.rst:445 msgid "" "DHCP_, the Domain Name System (DNS), the Network Time Protocol (NTP), and :" "ref:`VXLAN` are examples of UDP-based protocols used in OpenStack " "deployments." msgstr "" -#: ../intro_basic_networking.rst:449 +#: ../intro_basic_networking.rst:448 msgid "" "UDP has support for one-to-many communication: sending a single packet to " "multiple hosts. An application can broadcast a UDP packet to all of the " @@ -2613,7 +2613,7 @@ msgid "" "routing. VXLAN is an example of a UDP-based protocol that uses IP multicast." msgstr "" -#: ../intro_basic_networking.rst:461 +#: ../intro_basic_networking.rst:460 msgid "" "The *Internet Control Message Protocol* (ICMP) is a protocol used for " "sending control messages over an IP network. For example, a router that " @@ -2624,7 +2624,7 @@ msgid "" "\"don't fragment\" flag is set)." msgstr "" -#: ../intro_basic_networking.rst:469 +#: ../intro_basic_networking.rst:468 msgid "" "The *ping* and *mtr* Linux command-line tools are two examples of network " "utilities that use ICMP."