Imported Translations from Zanata
For more information about this automatic import see: https://wiki.openstack.org/wiki/Translations/Infrastructure Change-Id: Iaefa2dd0b588fa47c92d8944168253fc71a7cb19
This commit is contained in:
OpenStack Proposal Bot
parent
8c3e974821
commit
49b1ba8869
File diff suppressed because it is too large
Load Diff
@ -1,7 +1,7 @@
|
||||
msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: PACKAGE VERSION\n"
|
||||
"POT-Creation-Date: 2015-11-03 06:30+0000\n"
|
||||
"POT-Creation-Date: 2015-11-09 06:12+0000\n"
|
||||
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
|
||||
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
|
||||
"Language-Team: LANGUAGE <LL@li.org>\n"
|
||||
@ -3110,11 +3110,11 @@ msgid "OpenStack services architecture"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/multi_site/section_architecture_multi_site.xml:30(para)
|
||||
msgid "The OpenStack Identity service, which is used by all other OpenStack components for authorization and the catalog of service endpoints, supports the concept of regions. A region is a logical construct used to group OpenStack services in close proximity to one another. The concept of regions is flexible; it may can contain OpenStack service endpoints located within a distinct geographic region or regions. It may be smaller in scope, where a region is a single rack within a data center, with multiple regions existing in adjacent racks in the same data center."
|
||||
msgid "The Identity service, which is used by all other OpenStack components for authorization and the catalog of service endpoints, supports the concept of regions. A region is a logical construct used to group OpenStack services in close proximity to one another. The concept of regions is flexible; it may contain OpenStack service endpoints located within a distinct geographic region or regions. It may be smaller in scope, where a region is a single rack within a data center, with multiple regions existing in adjacent racks in the same data center."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/multi_site/section_architecture_multi_site.xml:40(para)
|
||||
msgid "The majority of OpenStack components are designed to run within the context of a single region. The OpenStack Compute service is designed to manage compute resources within a region, with support for subdivisions of compute resources by using availability zones and cells. The OpenStack Networking service can be used to manage network resources in the same broadcast domain or collection of switches that are linked. The OpenStack Block Storage service controls storage resources within a region with all storage resources residing on the same storage network. Like the OpenStack Compute service, the OpenStack Block Storage service also supports the availability zone construct which can be used to subdivide storage resources."
|
||||
msgid "The majority of OpenStack components are designed to run within the context of a single region. The Compute service is designed to manage compute resources within a region, with support for subdivisions of compute resources by using availability zones and cells. The Networking service can be used to manage network resources in the same broadcast domain or collection of switches that are linked. The OpenStack Block Storage service controls storage resources within a region with all storage resources residing on the same storage network. Like the OpenStack Compute service, the OpenStack Block Storage service also supports the availability zone construct which can be used to subdivide storage resources."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/multi_site/section_architecture_multi_site.xml:52(para)
|
||||
@ -3130,7 +3130,7 @@ msgid "In order to scale the Object Storage service to meet the workload of mult
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/multi_site/section_architecture_multi_site.xml:73(para)
|
||||
msgid "If the cloud is designed with a separate Object Storage Service endpoint made available in each region, applications are required to handle synchronization (if desired) and other management operations to ensure consistency across the nodes. For some applications, having multiple Object Storage Service endpoints located in the same region as the application may be desirable due to reduced latency, cross region bandwidth, and ease of deployment."
|
||||
msgid "If the cloud is designed with a separate Object Storage service endpoint made available in each region, applications are required to handle synchronization (if desired) and other management operations to ensure consistency across the nodes. For some applications, having multiple Object Storage Service endpoints located in the same region as the application may be desirable due to reduced latency, cross region bandwidth, and ease of deployment."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/multi_site/section_architecture_multi_site.xml:82(para)
|
||||
@ -3138,7 +3138,7 @@ msgid "For the Block Storage service, the most important decisions are the selec
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/multi_site/section_architecture_multi_site.xml:90(para)
|
||||
msgid "When connecting multiple regions together there are several design considerations. The overlay network technology choice determines how packets are transmitted between regions and how the logical network and addresses present to the application. If there are security or regulatory requirements, encryption should be implemented to secure the traffic between regions. For networking inside a region, the overlay network technology for tenant networks is equally important. The overlay technology and the network traffic of an application generates or receives can be either complementary or be at cross purpose. For example, using an overlay technology for an application that transmits a large amount of small packets could add excessive latency or overhead to each packet if not configured properly."
|
||||
msgid "When connecting multiple regions together, there are several design considerations. The overlay network technology choice determines how packets are transmitted between regions and how the logical network and addresses present to the application. If there are security or regulatory requirements, encryption should be implemented to secure the traffic between regions. For networking inside a region, the overlay network technology for tenant networks is equally important. The overlay technology and the network traffic that an application generates or receives can be either complementary or serve cross purposes. For example, using an overlay technology for an application that transmits a large amount of small packets could add excessive latency or overhead to each packet if not configured properly."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/multi_site/section_architecture_multi_site.xml:105(title) ./doc/arch-design/introduction/section_methodology.xml:86(term)
|
||||
@ -4086,7 +4086,7 @@ msgid "Implementing a baseline of upper-layer services across all of the cloud p
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/hybrid/section_architecture_hybrid.xml:69(para)
|
||||
msgid "For example, through the <glossterm>Database service</glossterm> for OpenStack (<glossterm>trove</glossterm>), OpenStack supports MySQL as a service but not NoSQL databases in production. To move from or run alongside AWS, a NoSQL workload must use an automation tool, such as the Orchestration service (heat), to recreate the NoSQL database on top of OpenStack."
|
||||
msgid "For example, through the <glossterm>Database service</glossterm> for OpenStack (<glossterm>trove</glossterm>), OpenStack supports MySQL-as-a-Service but not NoSQL databases in production. To move from or run alongside AWS, a NoSQL workload must use an automation tool, such as the Orchestration service (heat), to recreate the NoSQL database on top of OpenStack."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/hybrid/section_architecture_hybrid.xml:79(para)
|
||||
|
||||
@ -12,7 +12,7 @@
|
||||
msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: PACKAGE VERSION\n"
|
||||
"POT-Creation-Date: 2015-11-02 22:23+0000\n"
|
||||
"POT-Creation-Date: 2015-11-09 05:54+0000\n"
|
||||
"MIME-Version: 1.0\n"
|
||||
"Content-Type: text/plain; charset=UTF-8\n"
|
||||
"Content-Transfer-Encoding: 8bit\n"
|
||||
@ -4096,24 +4096,6 @@ msgstr ""
|
||||
"加冗余的电力供应和结对的交换机来实现，加入遇到这样的需求，硬件需要支持冗余的"
|
||||
"配置。"
|
||||
|
||||
msgid ""
|
||||
"The majority of OpenStack components are designed to run within the context "
|
||||
"of a single region. The OpenStack Compute service is designed to manage "
|
||||
"compute resources within a region, with support for subdivisions of compute "
|
||||
"resources by using availability zones and cells. The OpenStack Networking "
|
||||
"service can be used to manage network resources in the same broadcast domain "
|
||||
"or collection of switches that are linked. The OpenStack Block Storage "
|
||||
"service controls storage resources within a region with all storage "
|
||||
"resources residing on the same storage network. Like the OpenStack Compute "
|
||||
"service, the OpenStack Block Storage service also supports the availability "
|
||||
"zone construct which can be used to subdivide storage resources."
|
||||
msgstr ""
|
||||
"多数的OpenStack组件被设计为运行在单个region上下文中。OpenStack计算服务被设计"
|
||||
"为在一个region中管理计算资源，支持使用可用区域和单元来往下拆分。OpenStack网络"
|
||||
"服务可用于在同一广播域中或者说相互连接的交换机来管理网路资源。OpenStack块存储"
|
||||
"服务控制单一region中的存储资源，且这些资源须在统一存储网络中。和OpenStack计算"
|
||||
"服务一样，OpenStack块存储服务同样支持可用区域的构造，用于往下拆分存储资源。"
|
||||
|
||||
msgid ""
|
||||
"The management tools used for Ubuntu and Kinstance differ from the "
|
||||
"management tools for VMware vSphere. Although both OS and hypervisor "
|
||||
@ -4691,26 +4673,6 @@ msgstr ""
|
||||
"当尝试构建一个基于行业标准核心的灵活设计时，实现这个的一个办法，可能是通过使"
|
||||
"用不同的后端服务于不同的使用场景。"
|
||||
|
||||
msgid ""
|
||||
"When connecting multiple regions together there are several design "
|
||||
"considerations. The overlay network technology choice determines how packets "
|
||||
"are transmitted between regions and how the logical network and addresses "
|
||||
"present to the application. If there are security or regulatory "
|
||||
"requirements, encryption should be implemented to secure the traffic between "
|
||||
"regions. For networking inside a region, the overlay network technology for "
|
||||
"tenant networks is equally important. The overlay technology and the network "
|
||||
"traffic of an application generates or receives can be either complementary "
|
||||
"or be at cross purpose. For example, using an overlay technology for an "
|
||||
"application that transmits a large amount of small packets could add "
|
||||
"excessive latency or overhead to each packet if not configured properly."
|
||||
msgstr ""
|
||||
"当连接多个region到一起时需要考虑很多设计因素。覆盖网络技术的选择决定了网络包"
|
||||
"如何在region之间传输，以及如何给应用赋予逻辑网络和地址。如果有安全或监管需"
|
||||
"求，还得使用加密技术实现region之间的安全传输。在region内部网络，租户网络的覆"
|
||||
"盖网络技术亦同等重要，网络覆盖技术和应用生成或接受的网络流量可以是互补的或者"
|
||||
"交叉目的。例如，使用覆盖技术为一个应用，而中间传输使用了大量的小网络包，如果"
|
||||
"配置不当会引起大量的延迟或增大每个包的开销。"
|
||||
|
||||
msgid ""
|
||||
"When considering performance of OpenStack Block Storage, hardware and "
|
||||
"architecture choice is important. Block Storage can use enterprise back-end "
|
||||
|
||||
File diff suppressed because one or more lines are too long
@ -8,7 +8,7 @@ msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: Common documents 1.0.0\n"
|
||||
"Report-Msgid-Bugs-To: \n"
|
||||
"POT-Creation-Date: 2015-11-03 06:31+0000\n"
|
||||
"POT-Creation-Date: 2015-11-09 06:13+0000\n"
|
||||
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
|
||||
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
|
||||
"Language-Team: LANGUAGE <LL@li.org>\n"
|
||||
@ -1718,7 +1718,7 @@ msgstr ""
|
||||
|
||||
#: ../common/cli_overview.rst:73
|
||||
msgid ""
|
||||
"Gathers statistics, lists items, updates metedata, and uploads, downloads, "
|
||||
"Gathers statistics, lists items, updates metadata, and uploads, downloads, "
|
||||
"and deletes files stored by the Object Storage service. Gains access to an "
|
||||
"Object Storage installation for ad hoc processing."
|
||||
msgstr ""
|
||||
@ -6396,7 +6396,7 @@ msgstr ""
|
||||
|
||||
#: ../common/glossary.rst:1586
|
||||
msgid ""
|
||||
"OpenStack project to provide governance as a service across any collection "
|
||||
"OpenStack project to provide Governance-as-a-Service across any collection "
|
||||
"of cloud services in order to monitor, enforce, and audit policy over "
|
||||
"dynamic infrastructure. The code name for the project is congress."
|
||||
msgstr ""
|
||||
|
||||
@ -12,17 +12,18 @@
|
||||
# Akira YOSHIYAMA <akirayoshiyama@gmail.com>, 2015. #zanata
|
||||
# KATO Tomoyuki <kato.tomoyuki@jp.fujitsu.com>, 2015. #zanata
|
||||
# OpenStack Infra <zanata@openstack.org>, 2015. #zanata
|
||||
# Shu Muto <shu-mutou@rf.jp.nec.com>, 2015. #zanata
|
||||
# Yuta Hono <yuta.hono@ntt.com>, 2015. #zanata
|
||||
msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: Common documents 1.0.0\n"
|
||||
"Report-Msgid-Bugs-To: \n"
|
||||
"POT-Creation-Date: 2015-10-30 03:20+0000\n"
|
||||
"POT-Creation-Date: 2015-11-09 05:55+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-27 02:48+0000\n"
|
||||
"Last-Translator: Yuta Hono <yuta.hono@ntt.com>\n"
|
||||
"PO-Revision-Date: 2015-11-09 12:50+0000\n"
|
||||
"Last-Translator: Shu Muto <shu-mutou@rf.jp.nec.com>\n"
|
||||
"Language: ja\n"
|
||||
"Plural-Forms: nplurals=1; plural=0;\n"
|
||||
"X-Generator: Zanata 3.7.1\n"
|
||||
@ -802,6 +803,13 @@ msgstr ""
|
||||
"Object Storage がキャッシュのために使用する、メモリーオブジェクトの分散キャッ"
|
||||
"シュシステム。"
|
||||
|
||||
msgid ""
|
||||
"A distributed, highly fault-tolerant file system designed to run on low-cost "
|
||||
"commodity hardware."
|
||||
msgstr ""
|
||||
"低価格のコモディティーサーバー上で動作することを念頭に設計された、耐故障性に"
|
||||
"優れた分散ファイルシステム。"
|
||||
|
||||
msgid ""
|
||||
"A domain within a parent domain. Subdomains cannot be registered. Subdomains "
|
||||
"enable you to delegate domains. Subdomains can themselves have subdomains, "
|
||||
@ -836,6 +844,15 @@ msgstr ""
|
||||
"負荷分散サービスの機能の 1 つ。ノードがオンラインである限り、強制的に一連の接"
|
||||
"続を同じノードにリダイレクトしようとする。"
|
||||
|
||||
msgid ""
|
||||
"A file sharing protocol. It is a public or open variation of the original "
|
||||
"Server Message Block (SMB) protocol developed and used by Microsoft. Like "
|
||||
"the SMB protocol, CIFS runs at a higher level and uses the TCP/IP protocol."
|
||||
msgstr ""
|
||||
"ファイル共有プロトコル。 Microsoft が開発し使用している Server Message Block "
|
||||
"(SMB) プロトコルが公開されオープンになったものです。 SMB プロトコルと同様"
|
||||
"に、 CIFS は上位レイヤーで動作し、TCP/IP プロトコルを使用します。"
|
||||
|
||||
msgid ""
|
||||
"A file system designed to aggregate NAS hosts, compatible with OpenStack."
|
||||
msgstr ""
|
||||
@ -1148,6 +1165,15 @@ msgstr ""
|
||||
"なコンピューティングリソースの共有プールにアクセスできるモデル。最小限の管理"
|
||||
"作業やサービスプロバイダーとのやりとりで、迅速に配備できてリリースできる。"
|
||||
|
||||
msgid ""
|
||||
"A network authentication protocol which works on the basis of tickets. "
|
||||
"Kerberos allows nodes communication over a non-secure network, and allows "
|
||||
"nodes to prove their identity to one another in a secure manner."
|
||||
msgstr ""
|
||||
"チケットベースで機能するネットワーク認証プロトコル。 Kerberos により、安全で"
|
||||
"ないネットワークを通したノード通信ができ、ノードは安全な方法で互いに本人確認"
|
||||
"ができるようになります。"
|
||||
|
||||
msgid ""
|
||||
"A network protocol used by a network client to obtain an IP address from a "
|
||||
"configuration server. Provided in Compute through the dnsmasq daemon when "
|
||||
@ -1673,6 +1699,15 @@ msgstr "ATA over Ethernet (AoE)"
|
||||
msgid "AWS"
|
||||
msgstr "AWS"
|
||||
|
||||
msgid ""
|
||||
"AWS CloudFormation allows AWS users to create and manage a collection of "
|
||||
"related resources. The Orchestration service supports a CloudFormation-"
|
||||
"compatible format (CFN)."
|
||||
msgstr ""
|
||||
"AWS CloudFormation により、AWS ユーザーは関連するリソース群を作成し、管理でき"
|
||||
"るようになる。オーケストレーションサービスは CloudFormation 互換形式 (CFN) を"
|
||||
"サポートする。"
|
||||
|
||||
msgid "AWS CloudFormation template"
|
||||
msgstr "AWS CloudFormation テンプレート"
|
||||
|
||||
@ -2334,6 +2369,21 @@ msgstr ""
|
||||
msgid "An object within Object Storage that is larger than 5 GB."
|
||||
msgstr "5 GB より大きい Object Storage 内のオブジェクト。"
|
||||
|
||||
msgid ""
|
||||
"An official OpenStack project. Currently consists of Compute (nova), Object "
|
||||
"Storage (swift), Image service (glance), Identity (keystone), Dashboard "
|
||||
"(horizon), Networking (neutron), and Block Storage (cinder), Telemetry "
|
||||
"(ceilometer), Orchestration (heat), Database service (trove), Bare Metal "
|
||||
"service (ironic), Data processing service (sahara). However, this definition "
|
||||
"is changing based on community discussions about the \"Big Tent\"."
|
||||
msgstr ""
|
||||
"OpenStack の公式プロジェクト。現在、 Compute (nova), Object Storage (swift), "
|
||||
"Image service (glance), Identity (keystone), Dashboard (horizon), Networking "
|
||||
"(neutron), and Block Storage (cinder), Telemetry (ceilometer), Orchestration "
|
||||
"(heat), Database service (trove), Bare Metal service (ironic), Data "
|
||||
"processing service (sahara) がある。しかしながら、この定義は「Big Tent」に関"
|
||||
"するコミュニティーの議論に基づき変更されてきている。"
|
||||
|
||||
msgid "An open source LDAP server. Supported by both Compute and Identity."
|
||||
msgstr ""
|
||||
"オープンソース LDAP サーバー。Compute と Identity によりサポートされる。"
|
||||
@ -3441,6 +3491,17 @@ msgstr "OpenStack RC ファイルのダウンロードと読み込み"
|
||||
msgid "Drivers"
|
||||
msgstr "ドライバー"
|
||||
|
||||
msgid ""
|
||||
"Drivers or a service back end are integrated to the centralized server. They "
|
||||
"are used for accessing identity information in repositories external to "
|
||||
"OpenStack, and may already exist in the infrastructure where OpenStack is "
|
||||
"deployed (for example, SQL databases or LDAP servers)."
|
||||
msgstr ""
|
||||
"ドライバーやサービスバックエンドは、中央サーバーと統合されています。これら"
|
||||
"は、OpenStack の外部にあるリポジトリーにある認証情報にアクセスするために使用"
|
||||
"されます。OpenStack が導入されているインフラストラクチャーにすでに存在するか"
|
||||
"もしれません (例えば、SQL データベースやLDAP サーバー)。"
|
||||
|
||||
msgid ""
|
||||
"During the set up or testing of OpenStack, you might have questions about "
|
||||
"how a specific task is completed or be in a situation where a feature does "
|
||||
@ -3904,7 +3965,7 @@ msgstr ""
|
||||
"一覧からプロジェクトを選択します。"
|
||||
|
||||
msgid ""
|
||||
"Gathers statistics, lists items, updates metedata, and uploads, downloads, "
|
||||
"Gathers statistics, lists items, updates metadata, and uploads, downloads, "
|
||||
"and deletes files stored by the Object Storage service. Gains access to an "
|
||||
"Object Storage installation for ad hoc processing."
|
||||
msgstr ""
|
||||
@ -5318,6 +5379,17 @@ msgstr "OpenStack Image service"
|
||||
msgid "OpenStack Networking"
|
||||
msgstr "OpenStack Networking"
|
||||
|
||||
msgid ""
|
||||
"OpenStack Networking (neutron) allows you to create and attach interface "
|
||||
"devices managed by other OpenStack services to networks. Plug-ins can be "
|
||||
"implemented to accommodate different networking equipment and software, "
|
||||
"providing flexibility to OpenStack architecture and deployment."
|
||||
msgstr ""
|
||||
"OpenStack Networking (neutron) により、他の OpenStack サービスにより管理され"
|
||||
"ているインターフェースデバイスを作成して、ネットワークに接続できます。プラグ"
|
||||
"インは、OpenStack のアーキテクチャーと環境に柔軟性を提供している、異なるネッ"
|
||||
"トワーク設備とソフトウェアを適応させるために実装されます。"
|
||||
|
||||
msgid ""
|
||||
"OpenStack Networking agent that provides DHCP services for virtual networks."
|
||||
msgstr ""
|
||||
@ -5363,6 +5435,9 @@ msgstr "OpenStack のサービス"
|
||||
msgid "OpenStack Shared File Systems service"
|
||||
msgstr "OpenStack Shared File Systems サービス"
|
||||
|
||||
msgid "OpenStack Telemetry service"
|
||||
msgstr "OpenStack Telemetry サービス"
|
||||
|
||||
msgid "OpenStack code name"
|
||||
msgstr "OpenStack コード名"
|
||||
|
||||
@ -5538,7 +5613,7 @@ msgstr ""
|
||||
"ロジェクトのコード名は ironic です。"
|
||||
|
||||
msgid ""
|
||||
"OpenStack project to provide governance as a service across any collection "
|
||||
"OpenStack project to provide Governance-as-a-Service across any collection "
|
||||
"of cloud services in order to monitor, enforce, and audit policy over "
|
||||
"dynamic infrastructure. The code name for the project is congress."
|
||||
msgstr ""
|
||||
@ -6940,6 +7015,12 @@ msgstr ""
|
||||
"マシンに対するリモートデスクトップアクセスを提供する。VNC の代替品。SPICE は "
|
||||
"OpenStack によりサポートされる。"
|
||||
|
||||
msgid "The Telemetry service consists of the following components:"
|
||||
msgstr "Telemetry サービスは、以下のコンポーネントから構成されます。"
|
||||
|
||||
msgid "The Telemetry service performs the following functions:"
|
||||
msgstr "Telemetry サービスは、以下の機能から構成されます。"
|
||||
|
||||
msgid ""
|
||||
"The URL where the data for this image resides. For example, if the image "
|
||||
"data is stored in swift, you could specify ``swift://account:key@example.com/"
|
||||
@ -7653,6 +7734,13 @@ msgstr ""
|
||||
"#setuptools <http://www.lfd.uci.edu/~gohlke/ pythonlibs/#setuptools>`__) を使"
|
||||
"用することです。"
|
||||
|
||||
msgid ""
|
||||
"The registry is a private internal service meant for use by OpenStack Image "
|
||||
"service. Do not expose this service to users."
|
||||
msgstr ""
|
||||
"レジストリーは OpenStack Image service 自身により使用されるプライベートな内部"
|
||||
"サービスです。ユーザーに開示しないでください。"
|
||||
|
||||
msgid "The report has the following sections:"
|
||||
msgstr "以下のセクションがレポートされます。"
|
||||
|
||||
@ -9115,6 +9203,9 @@ msgstr "``nova-xvpvncproxy`` デーモン"
|
||||
msgid "``nova`` - Compute API and extensions"
|
||||
msgstr "``nova`` - Compute API および拡張"
|
||||
|
||||
msgid "``nova`` client"
|
||||
msgstr "``nova`` クライアント"
|
||||
|
||||
msgid "``openstack`` - Common OpenStack client supporting multiple services"
|
||||
msgstr ""
|
||||
"``openstack`` - 複数の OpenStack サービスをサポートする共通クライアント"
|
||||
@ -9728,6 +9819,22 @@ msgstr "ハイパーバイザープール"
|
||||
msgid "iSCSI"
|
||||
msgstr "iSCSI"
|
||||
|
||||
msgid ""
|
||||
"iSCSI Qualified Name (IQN) is the format most commonly used for iSCSI names, "
|
||||
"which uniquely identify nodes in an iSCSI network. All IQNs follow the "
|
||||
"pattern iqn.yyyy-mm.domain:identifier, where 'yyyy-mm' is the year and month "
|
||||
"in which the domain was registered, 'domain' is the reversed domain name of "
|
||||
"the issuing organization, and 'identifier' is an optional string which makes "
|
||||
"each IQN under the same domain unique. For example, 'iqn.2015-10.org."
|
||||
"openstack.408ae959bce1'."
|
||||
msgstr ""
|
||||
"iSCSI Qualified Name (IQN) は iSCSI の名前として最も広く使われている形式で、 "
|
||||
"iSCSI ネットワークで一意にノードを識別するのに使われます。すべての IQN は "
|
||||
"iqn.yyyy-mm.domain:identifier という形式です。ここで、 'yyyy-mm' はそのドメイ"
|
||||
"ンが登録された年と月、 'domain' は発行組織の登録されたドメイン名、 "
|
||||
"'identifier' は同じドメイン内の各 IQN 番号を一意なものにするためのオプション"
|
||||
"文字列です。例えば 'iqn.2015-10.org.openstack.408ae959bce1'"
|
||||
|
||||
msgid "ide"
|
||||
msgstr "ide"
|
||||
|
||||
|
||||
@ -13,7 +13,7 @@ msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: Common documents 1.0.0\n"
|
||||
"Report-Msgid-Bugs-To: \n"
|
||||
"POT-Creation-Date: 2015-10-30 03:20+0000\n"
|
||||
"POT-Creation-Date: 2015-11-09 05:55+0000\n"
|
||||
"MIME-Version: 1.0\n"
|
||||
"Content-Type: text/plain; charset=UTF-8\n"
|
||||
"Content-Transfer-Encoding: 8bit\n"
|
||||
@ -3597,16 +3597,6 @@ msgstr ""
|
||||
"Dự án của OpenStack có quy định về dịch vụ bare-metal, đối lập với các máy "
|
||||
"ảo. Tên mã của dự án này là Ironic."
|
||||
|
||||
msgid ""
|
||||
"OpenStack project to provide governance as a service across any collection "
|
||||
"of cloud services in order to monitor, enforce, and audit policy over "
|
||||
"dynamic infrastructure. The code name for the project is congress."
|
||||
msgstr ""
|
||||
"Dự án của OpenStack có tác dụng cung cấp tính năng quản lý như là một dịch "
|
||||
"vụ trên bât kì tập hợp các dịch vụ điện toán đám mây nào nhằm mục đích giám "
|
||||
"sát, thi hành, và theo dõi chính sách trên cơ sở hạ tầng động. Tên mã của dự "
|
||||
"án này là congress."
|
||||
|
||||
msgid "OpenStack supports accessing the Amazon EC2 API through Compute."
|
||||
msgstr "OpenStack hỗ trợ truy cập vào Amazon EC2 API thông qua Compute."
|
||||
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: PACKAGE VERSION\n"
|
||||
"POT-Creation-Date: 2015-10-30 06:28+0000\n"
|
||||
"POT-Creation-Date: 2015-11-09 06:13+0000\n"
|
||||
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
|
||||
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
|
||||
"Language-Team: LANGUAGE <LL@li.org>\n"
|
||||
@ -220,23 +220,23 @@ msgid "Integrate Identity with LDAP"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/common/section_keystone_config_ldap.xml:8(para)
|
||||
msgid "The Openstack Identity Service supports integration with existing LDAP directories for authentication and authorization services."
|
||||
msgid "The OpenStack Identity service supports integration with existing LDAP directories for authentication and authorization services."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/common/section_keystone_config_ldap.xml:11(para)
|
||||
msgid "When the Openstack Identity service is configured to use LDAP back ends, you can split authentication (using the <emphasis>identity</emphasis> feature) and authorization (using the <emphasis>assignment</emphasis> feature)."
|
||||
msgid "When the OpenStack Identity service is configured to use LDAP back ends, you can split authentication (using the <emphasis>identity</emphasis> feature) and authorization (using the <emphasis>assignment</emphasis> feature)."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/common/section_keystone_config_ldap.xml:16(para)
|
||||
msgid "The identity feature enables administrators to manage users and groups by each domain or the Openstack Identity Service entirely."
|
||||
msgid "The identity feature enables administrators to manage users and groups by each domain or the OpenStack Identity service entirely."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/common/section_keystone_config_ldap.xml:18(para)
|
||||
msgid "The Assignments feature enables administrators to manage project role authorization using the Openstack Identity service SQL database, while providing user authentication through the LDAP directory."
|
||||
msgid "The Assignments feature enables administrators to manage project role authorization using the OpenStack Identity service SQL database, while providing user authentication through the LDAP directory."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/common/section_keystone_config_ldap.xml:23(para)
|
||||
msgid "For OpenStack Identity service to access LDAP servers, you must enable the <placeholder-1/> boolean value for SELinux on the Openstack Identity server. To enable and make the option persistent across reboots:"
|
||||
msgid "For OpenStack Identity service to access LDAP servers, you must enable the <placeholder-1/> boolean value for SELinux on the server running the OpenStack Identity service. To enable and make the option persistent across reboots:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/common/section_keystone_config_ldap.xml:29(para)
|
||||
@ -244,7 +244,7 @@ msgid "Identity configuration is split into two separate back ends: identity (ba
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/common/section_keystone_config_ldap.xml:39(para)
|
||||
msgid "Multiple back ends are supported. You can integrate the Openstack Identity service with a single LDAP server (configure both identity and assignments to LDAP, or set identity and assignments back end with SQL or LDAP), or multiple back ends using domain-specific configuration files."
|
||||
msgid "Multiple back ends are supported. You can integrate the OpenStack Identity service with a single LDAP server (configure both identity and assignments to LDAP, or set identity and assignments back end with SQL or LDAP), or multiple back ends using domain-specific configuration files."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/common/section_keystone_config_ldap.xml:45(title)
|
||||
@ -316,7 +316,7 @@ msgid "Use <placeholder-1/> to enable LDAP connection pooling for end user authe
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/common/section_keystone_config_ldap.xml:130(para)
|
||||
msgid "When you have finished configuration, restart the Openstack Identity service:"
|
||||
msgid "When you have finished configuration, restart the OpenStack Identity service:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/common/section_keystone_config_ldap.xml:132(para) ./doc/common/section_keystone_config_ldap-assignments.xml:74(para) ./doc/common/section_keystone_config_ldap-identity.xml:64(para) ./doc/common/section_keystone_config_ldap-identity.xml:159(para)
|
||||
|
||||
File diff suppressed because it is too large
Load Diff
@ -1,7 +1,7 @@
|
||||
msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: PACKAGE VERSION\n"
|
||||
"POT-Creation-Date: 2015-10-30 06:28+0000\n"
|
||||
"POT-Creation-Date: 2015-11-09 06:13+0000\n"
|
||||
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
|
||||
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
|
||||
"Language-Team: LANGUAGE <LL@li.org>\n"
|
||||
@ -2694,7 +2694,7 @@ msgid "Governance service"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/glossary/glossary-terms.xml:3769(para)
|
||||
msgid "OpenStack project to provide governance as a service across any collection of cloud services in order to monitor, enforce, and audit policy over dynamic infrastructure. The code name for the project is congress."
|
||||
msgid "OpenStack project to provide Governance-as-a-Service across any collection of cloud services in order to monitor, enforce, and audit policy over dynamic infrastructure. The code name for the project is congress."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/glossary/glossary-terms.xml:3779(glossterm) ./doc/glossary/glossary-terms.xml:3781(primary)
|
||||
|
||||
@ -8,16 +8,17 @@
|
||||
# Akihiro Motoki <amotoki@gmail.com>, 2015. #zanata
|
||||
# KATO Tomoyuki <kato.tomoyuki@jp.fujitsu.com>, 2015. #zanata
|
||||
# OpenStack Infra <zanata@openstack.org>, 2015. #zanata
|
||||
# Shu Muto <shu-mutou@rf.jp.nec.com>, 2015. #zanata
|
||||
# Yuta Hono <yuta.hono@ntt.com>, 2015. #zanata
|
||||
msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: PACKAGE VERSION\n"
|
||||
"POT-Creation-Date: 2015-10-30 03:20+0000\n"
|
||||
"POT-Creation-Date: 2015-11-09 05:55+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-27 02:12+0000\n"
|
||||
"Last-Translator: Yuta Hono <yuta.hono@ntt.com>\n"
|
||||
"PO-Revision-Date: 2015-11-09 12:33+0000\n"
|
||||
"Last-Translator: Shu Muto <shu-mutou@rf.jp.nec.com>\n"
|
||||
"Language: ja\n"
|
||||
"Plural-Forms: nplurals=1; plural=0;\n"
|
||||
"X-Generator: Zanata 3.7.1\n"
|
||||
@ -1229,6 +1230,15 @@ msgstr "AWS"
|
||||
msgid "AWS (Amazon Web Services)"
|
||||
msgstr "AWS (Amazon Web Services)"
|
||||
|
||||
msgid ""
|
||||
"AWS CloudFormation allows AWS users to create and manage a collection of "
|
||||
"related resources. The Orchestration service supports a CloudFormation-"
|
||||
"compatible format (CFN)."
|
||||
msgstr ""
|
||||
"AWS CloudFormation により、AWS ユーザーは関連するリソース群を作成し、管理でき"
|
||||
"るようになる。オーケストレーションサービスは CloudFormation 互換形式 (CFN) を"
|
||||
"サポートする。"
|
||||
|
||||
msgid "AWS CloudFormation template"
|
||||
msgstr "AWS CloudFormation テンプレート"
|
||||
|
||||
@ -1822,6 +1832,21 @@ msgstr ""
|
||||
msgid "An object within Object Storage that is larger than 5GB."
|
||||
msgstr "5GB より大きい Object Storage 内のオブジェクト。"
|
||||
|
||||
msgid ""
|
||||
"An official OpenStack project. Currently consists of Compute (nova), Object "
|
||||
"Storage (swift), Image service (glance), Identity (keystone), Dashboard "
|
||||
"(horizon), Networking (neutron), and Block Storage (cinder), Telemetry "
|
||||
"(ceilometer), Orchestration (heat), Database service (trove), Bare Metal "
|
||||
"service (ironic), Data processing service (sahara). However, this definition "
|
||||
"is changing based on community discussions about the \"Big Tent\"."
|
||||
msgstr ""
|
||||
"OpenStack の公式プロジェクト。現在、 Compute (nova), Object Storage (swift), "
|
||||
"Image service (glance), Identity (keystone), Dashboard (horizon), Networking "
|
||||
"(neutron), and Block Storage (cinder), Telemetry (ceilometer), Orchestration "
|
||||
"(heat), Database service (trove), Bare Metal service (ironic), Data "
|
||||
"processing service (sahara) がある。しかしながら、この定義は「Big Tent」に関"
|
||||
"するコミュニティーの議論に基づき変更されてきている。"
|
||||
|
||||
msgid "An open source LDAP server. Supported by both Compute and Identity."
|
||||
msgstr ""
|
||||
"オープンソース LDAP サーバー。Compute と Identity によりサポートされる。"
|
||||
@ -3951,7 +3976,7 @@ msgstr ""
|
||||
"ロジェクトのコード名は ironic です。"
|
||||
|
||||
msgid ""
|
||||
"OpenStack project to provide governance as a service across any collection "
|
||||
"OpenStack project to provide Governance-as-a-Service across any collection "
|
||||
"of cloud services in order to monitor, enforce, and audit policy over "
|
||||
"dynamic infrastructure. The code name for the project is congress."
|
||||
msgstr ""
|
||||
|
||||
@ -16,7 +16,7 @@
|
||||
msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: PACKAGE VERSION\n"
|
||||
"POT-Creation-Date: 2015-10-30 03:20+0000\n"
|
||||
"POT-Creation-Date: 2015-11-09 05:55+0000\n"
|
||||
"MIME-Version: 1.0\n"
|
||||
"Content-Type: text/plain; charset=UTF-8\n"
|
||||
"Content-Transfer-Encoding: 8bit\n"
|
||||
@ -3942,16 +3942,6 @@ msgstr ""
|
||||
"Dự án của OpenStack có quy định về dịch vụ bare-metal, đối lập với các máy "
|
||||
"ảo. Tên mã của dự án này là Ironic."
|
||||
|
||||
msgid ""
|
||||
"OpenStack project to provide governance as a service across any collection "
|
||||
"of cloud services in order to monitor, enforce, and audit policy over "
|
||||
"dynamic infrastructure. The code name for the project is congress."
|
||||
msgstr ""
|
||||
"Dự án của OpenStack có tác dụng cung cấp tính năng quản lý như là một dịch "
|
||||
"vụ trên bât kì tập hợp các dịch vụ điện toán đám mây nào nhằm mục đích giám "
|
||||
"sát, thi hành, và theo dõi chính sách trên cơ sở hạ tầng động. Tên mã của dự "
|
||||
"án này là congress."
|
||||
|
||||
msgid "OpenStack supports accessing the Amazon EC2 API through Compute."
|
||||
msgstr "OpenStack hỗ trợ truy cập vào Amazon EC2 API thông qua Compute."
|
||||
|
||||
|
||||
@ -8,7 +8,7 @@ msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: Installation Guide 0.1\n"
|
||||
"Report-Msgid-Bugs-To: \n"
|
||||
"POT-Creation-Date: 2015-10-30 06:28+0000\n"
|
||||
"POT-Creation-Date: 2015-11-09 06:13+0000\n"
|
||||
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
|
||||
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
|
||||
"Language-Team: LANGUAGE <LL@li.org>\n"
|
||||
@ -468,7 +468,7 @@ msgstr ""
|
||||
|
||||
#: ../ceilometer-nova.rst:137
|
||||
msgid ""
|
||||
"Notifications in real-time allow administrars to observe and resolve "
|
||||
"Notifications in real-time allow administrators to observe and resolve "
|
||||
"emergencies when the cloud environment experiences errors or faults."
|
||||
msgstr ""
|
||||
|
||||
@ -872,7 +872,7 @@ msgstr ""
|
||||
# #-#-#-#-# nova-controller-install.pot (Installation Guide 0.1) #-#-#-#-#
|
||||
# #-#-#-#-# swift-finalize-installation.pot (Installation Guide 0.1) #-#-#-#-#
|
||||
#: ../cinder-controller-install.rst:362 ../cinder-storage-install.rst:313
|
||||
#: ../glance-install.rst:371 ../heat-install.rst:488
|
||||
#: ../glance-install.rst:373 ../heat-install.rst:488
|
||||
#: ../neutron-compute-install.rst:179 ../neutron-controller-install.rst:254
|
||||
#: ../nova-compute-install.rst:207 ../nova-controller-install.rst:361
|
||||
#: ../swift-finalize-installation.rst:2
|
||||
@ -3052,13 +3052,13 @@ msgid ""
|
||||
"Identity service:"
|
||||
msgstr ""
|
||||
|
||||
#: ../glance-install.rst:375
|
||||
#: ../glance-install.rst:377
|
||||
msgid ""
|
||||
"Start the Image service services and configure them to start when the system "
|
||||
"boots:"
|
||||
msgstr ""
|
||||
|
||||
#: ../glance-install.rst:387
|
||||
#: ../glance-install.rst:389
|
||||
msgid "Restart the Image service services:"
|
||||
msgstr ""
|
||||
|
||||
@ -6759,11 +6759,11 @@ msgid ""
|
||||
"from the Object Storage source repository:"
|
||||
msgstr ""
|
||||
|
||||
#: ../swift-storage-install.rst:183 ../swift-storage-install.rst:211
|
||||
#: ../swift-storage-install.rst:183 ../swift-storage-install.rst:201
|
||||
msgid "Ensure proper ownership of the mount point directory structure:"
|
||||
msgstr ""
|
||||
|
||||
#: ../swift-storage-install.rst:199 ../swift-storage-install.rst:217
|
||||
#: ../swift-storage-install.rst:189 ../swift-storage-install.rst:207
|
||||
msgid "Create the ``recon`` directory and ensure proper ownership of it:"
|
||||
msgstr ""
|
||||
|
||||
|
||||
@ -15,7 +15,7 @@ msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: Installation Guide 0.1\n"
|
||||
"Report-Msgid-Bugs-To: \n"
|
||||
"POT-Creation-Date: 2015-11-02 22:24+0000\n"
|
||||
"POT-Creation-Date: 2015-11-09 05:55+0000\n"
|
||||
"MIME-Version: 1.0\n"
|
||||
"Content-Type: text/plain; charset=UTF-8\n"
|
||||
"Content-Transfer-Encoding: 8bit\n"
|
||||
@ -3343,13 +3343,6 @@ msgstr ""
|
||||
"通知メッセージは、OpenStack のメッセージングシステムに書き込まれます。イベン"
|
||||
"トがアラートを発行するときには、AMQP を使って情報が送信されます。"
|
||||
|
||||
msgid ""
|
||||
"Notifications in real-time allow administrars to observe and resolve "
|
||||
"emergencies when the cloud environment experiences errors or faults."
|
||||
msgstr ""
|
||||
"リアルタイムの通知により、クラウド環境にエラーや障害が発生したときに、管理者"
|
||||
"が緊急事態に気づき、解決できるようになります。"
|
||||
|
||||
msgid "Object Storage"
|
||||
msgstr "Object Storage"
|
||||
|
||||
|
||||
@ -8,7 +8,7 @@ msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: Networking Guide 0.9\n"
|
||||
"Report-Msgid-Bugs-To: \n"
|
||||
"POT-Creation-Date: 2015-11-03 06:31+0000\n"
|
||||
"POT-Creation-Date: 2015-11-09 06:13+0000\n"
|
||||
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
|
||||
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
|
||||
"Language-Team: LANGUAGE <LL@li.org>\n"
|
||||
@ -837,8 +837,8 @@ msgstr ""
|
||||
msgid ""
|
||||
"VPNaaS supports IPv6, but support in Kilo and prior releases will have some "
|
||||
"bugs that may limit how it can be used. More thorough and complete testing "
|
||||
"and bug fixing is being done as part of the Liberty release. IPv6-based VPN "
|
||||
"as a service is configured similar to the IPv4 configuration. Either or both "
|
||||
"and bug fixing is being done as part of the Liberty release. IPv6-based VPN-"
|
||||
"as-a-Service is configured similar to the IPv4 configuration. Either or both "
|
||||
"the ``peer_address`` and the ``peer_cidr`` can specified as an IPv6 address. "
|
||||
"The choice of addressing modes and router modes described above should not "
|
||||
"impact support."
|
||||
@ -1445,7 +1445,7 @@ msgstr ""
|
||||
|
||||
#: ../adv_config_sriov.rst:29
|
||||
msgid ""
|
||||
"Physical Function. This is the physical ethernet controller that supports SR-"
|
||||
"Physical Function. This is the physical Ethernet controller that supports SR-"
|
||||
"IOV."
|
||||
msgstr ""
|
||||
|
||||
@ -1456,7 +1456,7 @@ msgstr ""
|
||||
#: ../adv_config_sriov.rst:32
|
||||
msgid ""
|
||||
"Virtual Function. This is a virtual PCIe device created from a physical "
|
||||
"ethernet controller."
|
||||
"Ethernet controller."
|
||||
msgstr ""
|
||||
|
||||
#: ../adv_config_sriov.rst:36
|
||||
@ -1566,7 +1566,7 @@ msgstr ""
|
||||
|
||||
#: ../adv_config_sriov.rst:99
|
||||
msgid ""
|
||||
"The step to create VFs differ between SR-IOV card ethernet controller "
|
||||
"The step to create VFs differ between SR-IOV card Ethernet controller "
|
||||
"manufacturers. Currently the following manufacturers are known to work:"
|
||||
msgstr ""
|
||||
|
||||
@ -1584,13 +1584,13 @@ msgstr ""
|
||||
|
||||
#: ../adv_config_sriov.rst:106
|
||||
msgid ""
|
||||
"For **Mellanox SR-IOV ethernet cards** see: `Mellanox: HowTo Configure SR-"
|
||||
"For **Mellanox SR-IOV Ethernet cards** see: `Mellanox: HowTo Configure SR-"
|
||||
"IOV VFs <https://community.mellanox.com/docs/DOC-1484>`_"
|
||||
msgstr ""
|
||||
|
||||
#: ../adv_config_sriov.rst:110
|
||||
msgid ""
|
||||
"To create the VFs on Ubuntu for **Intel SR-IOV ethernet cards**, do the "
|
||||
"To create the VFs on Ubuntu for **Intel SR-IOV Ethernet cards**, do the "
|
||||
"following:"
|
||||
msgstr ""
|
||||
|
||||
@ -1636,7 +1636,7 @@ msgstr ""
|
||||
|
||||
#: ../adv_config_sriov.rst:158
|
||||
msgid ""
|
||||
"For **QLogic SR-IOV ethernet cards** see: `User's Guide OpenStack Deployment "
|
||||
"For **QLogic SR-IOV Ethernet cards** see: `User's Guide OpenStack Deployment "
|
||||
"with SR-IOV Configuration <http://www.qlogic.com/solutions/Documents/"
|
||||
"UsersGuide_OpenStack_SR-IOV.pdf>`_"
|
||||
msgstr ""
|
||||
@ -1959,7 +1959,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:223
|
||||
#: ../config_ml2_plug_in.rst:88 ../intro_basic_networking.rst:228
|
||||
#: ../intro_os_networking_service.rst:51
|
||||
msgid "DHCP"
|
||||
msgstr ""
|
||||
@ -2258,7 +2258,14 @@ msgid ""
|
||||
"and netmask, and this example would be written as ``192.168.1.5/24``."
|
||||
msgstr ""
|
||||
|
||||
#: ../intro_basic_networking.rst:172
|
||||
#: ../intro_basic_networking.rst:173
|
||||
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
|
||||
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 "
|
||||
@ -2266,7 +2273,7 @@ msgid ""
|
||||
"``10.10.53.24/16``, then we would say the subnet is ``10.10.0.0/16``."
|
||||
msgstr ""
|
||||
|
||||
#: ../intro_basic_networking.rst:178
|
||||
#: ../intro_basic_networking.rst:183
|
||||
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`` "
|
||||
@ -2276,40 +2283,40 @@ msgid ""
|
||||
"host *B*."
|
||||
msgstr ""
|
||||
|
||||
#: ../intro_basic_networking.rst:185
|
||||
#: ../intro_basic_networking.rst:190
|
||||
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:190
|
||||
#: ../intro_basic_networking.rst:195
|
||||
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:193
|
||||
#: ../intro_basic_networking.rst:198
|
||||
msgid "Host *B* responds with a response like this:"
|
||||
msgstr ""
|
||||
|
||||
#: ../intro_basic_networking.rst:195
|
||||
#: ../intro_basic_networking.rst:200
|
||||
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:198
|
||||
#: ../intro_basic_networking.rst:203
|
||||
msgid "Host *A* then sends Ethernet frames to host *B*."
|
||||
msgstr ""
|
||||
|
||||
#: ../intro_basic_networking.rst:200
|
||||
#: ../intro_basic_networking.rst:205
|
||||
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:211
|
||||
#: ../intro_basic_networking.rst:216
|
||||
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 "
|
||||
@ -2317,14 +2324,14 @@ msgid ""
|
||||
"command::"
|
||||
msgstr ""
|
||||
|
||||
#: ../intro_basic_networking.rst:225
|
||||
#: ../intro_basic_networking.rst:230
|
||||
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:230
|
||||
#: ../intro_basic_networking.rst:235
|
||||
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 "
|
||||
@ -2336,49 +2343,49 @@ msgid ""
|
||||
"client. The exchange looks like this:"
|
||||
msgstr ""
|
||||
|
||||
#: ../intro_basic_networking.rst:240
|
||||
#: ../intro_basic_networking.rst:245
|
||||
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:242
|
||||
#: ../intro_basic_networking.rst:247
|
||||
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:244
|
||||
#: ../intro_basic_networking.rst:249
|
||||
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:246
|
||||
#: ../intro_basic_networking.rst:251
|
||||
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:250
|
||||
#: ../intro_basic_networking.rst:255
|
||||
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:260
|
||||
#: ../intro_basic_networking.rst:265
|
||||
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:269
|
||||
#: ../intro_basic_networking.rst:274
|
||||
msgid "IP"
|
||||
msgstr ""
|
||||
|
||||
#: ../intro_basic_networking.rst:271
|
||||
#: ../intro_basic_networking.rst:276
|
||||
msgid ""
|
||||
"The Internet Protocol (IP) specifies how to route packets between hosts that "
|
||||
"are connected to different local networks. IP relies on special network "
|
||||
@ -2388,14 +2395,14 @@ msgid ""
|
||||
"networks it is connected to."
|
||||
msgstr ""
|
||||
|
||||
#: ../intro_basic_networking.rst:278
|
||||
#: ../intro_basic_networking.rst:283
|
||||
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:282
|
||||
#: ../intro_basic_networking.rst:287
|
||||
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 "
|
||||
@ -2404,17 +2411,17 @@ msgid ""
|
||||
"routers that are on these local networks."
|
||||
msgstr ""
|
||||
|
||||
#: ../intro_basic_networking.rst:288
|
||||
#: ../intro_basic_networking.rst:293
|
||||
msgid ""
|
||||
"On a Linux machine, any of the following commands displays the routing "
|
||||
"table::"
|
||||
msgstr ""
|
||||
|
||||
#: ../intro_basic_networking.rst:294
|
||||
#: ../intro_basic_networking.rst:299
|
||||
msgid "Here is an example of output from ``ip route show``::"
|
||||
msgstr ""
|
||||
|
||||
#: ../intro_basic_networking.rst:302
|
||||
#: ../intro_basic_networking.rst:307
|
||||
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 "
|
||||
@ -2424,45 +2431,45 @@ msgid ""
|
||||
"with the client's IP address and a netmask."
|
||||
msgstr ""
|
||||
|
||||
#: ../intro_basic_networking.rst:309
|
||||
#: ../intro_basic_networking.rst:314
|
||||
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:312
|
||||
#: ../intro_basic_networking.rst:317
|
||||
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:315
|
||||
#: ../intro_basic_networking.rst:320
|
||||
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:318
|
||||
#: ../intro_basic_networking.rst:323
|
||||
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:330
|
||||
#: ../intro_basic_networking.rst:335
|
||||
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:337
|
||||
#: ../intro_basic_networking.rst:342
|
||||
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:343
|
||||
#: ../intro_basic_networking.rst:348
|
||||
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`` "
|
||||
@ -2470,11 +2477,11 @@ msgid ""
|
||||
"traverses along its path to its destination."
|
||||
msgstr ""
|
||||
|
||||
#: ../intro_basic_networking.rst:351
|
||||
#: ../intro_basic_networking.rst:356
|
||||
msgid "TCP/UDP/ICMP"
|
||||
msgstr ""
|
||||
|
||||
#: ../intro_basic_networking.rst:353
|
||||
#: ../intro_basic_networking.rst:358
|
||||
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 "
|
||||
@ -2484,7 +2491,7 @@ msgid ""
|
||||
"associated numbers."
|
||||
msgstr ""
|
||||
|
||||
#: ../intro_basic_networking.rst:362
|
||||
#: ../intro_basic_networking.rst:367
|
||||
msgid ""
|
||||
"The *Transmission Control Protocol* (TCP) is the most commonly used layer 4 "
|
||||
"protocol in networked applications. TCP is a *connection-oriented* protocol: "
|
||||
@ -2493,19 +2500,19 @@ msgid ""
|
||||
"interaction in a TCP-based application proceeds as follows:"
|
||||
msgstr ""
|
||||
|
||||
#: ../intro_basic_networking.rst:370
|
||||
#: ../intro_basic_networking.rst:375
|
||||
msgid "Client connects to server."
|
||||
msgstr ""
|
||||
|
||||
#: ../intro_basic_networking.rst:371
|
||||
#: ../intro_basic_networking.rst:376
|
||||
msgid "Client and server exchange data."
|
||||
msgstr ""
|
||||
|
||||
#: ../intro_basic_networking.rst:372
|
||||
#: ../intro_basic_networking.rst:377
|
||||
msgid "Client or server disconnects."
|
||||
msgstr ""
|
||||
|
||||
#: ../intro_basic_networking.rst:374
|
||||
#: ../intro_basic_networking.rst:379
|
||||
msgid ""
|
||||
"Because a network host may have multiple TCP-based applications running, TCP "
|
||||
"uses an addressing scheme called *ports* to uniquely identify TCP-based "
|
||||
@ -2514,7 +2521,7 @@ msgid ""
|
||||
"time, a restriction that is enforced by the operating system."
|
||||
msgstr ""
|
||||
|
||||
#: ../intro_basic_networking.rst:380
|
||||
#: ../intro_basic_networking.rst:385
|
||||
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, "
|
||||
@ -2522,7 +2529,7 @@ msgid ""
|
||||
"TCP port."
|
||||
msgstr ""
|
||||
|
||||
#: ../intro_basic_networking.rst:385
|
||||
#: ../intro_basic_networking.rst:390
|
||||
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 "
|
||||
@ -2530,7 +2537,7 @@ msgid ""
|
||||
"port number. These types of ports are referred to as *ephemeral ports*."
|
||||
msgstr ""
|
||||
|
||||
#: ../intro_basic_networking.rst:391
|
||||
#: ../intro_basic_networking.rst:396
|
||||
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. "
|
||||
@ -2541,7 +2548,7 @@ msgid ""
|
||||
"deployment."
|
||||
msgstr ""
|
||||
|
||||
#: ../intro_basic_networking.rst:404
|
||||
#: ../intro_basic_networking.rst:409
|
||||
msgid ""
|
||||
"The most common application programming interface (API) for writing TCP-"
|
||||
"based applications is called *Berkeley sockets*, also known as *BSD sockets* "
|
||||
@ -2559,7 +2566,7 @@ msgid ""
|
||||
"*reliable* protocol."
|
||||
msgstr ""
|
||||
|
||||
#: ../intro_basic_networking.rst:419
|
||||
#: ../intro_basic_networking.rst:424
|
||||
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* "
|
||||
@ -2571,7 +2578,7 @@ msgid ""
|
||||
"they were sent in."
|
||||
msgstr ""
|
||||
|
||||
#: ../intro_basic_networking.rst:428
|
||||
#: ../intro_basic_networking.rst:433
|
||||
msgid ""
|
||||
"UDP, like TCP, uses the notion of ports to distinguish between different "
|
||||
"applications running on the same system. Note, however, that operating "
|
||||
@ -2580,7 +2587,7 @@ msgid ""
|
||||
"separate application to be associated with UDP port 16543."
|
||||
msgstr ""
|
||||
|
||||
#: ../intro_basic_networking.rst:434
|
||||
#: ../intro_basic_networking.rst:439
|
||||
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 "
|
||||
@ -2590,14 +2597,14 @@ msgid ""
|
||||
"responsible for implementing this functionality in the application code."
|
||||
msgstr ""
|
||||
|
||||
#: ../intro_basic_networking.rst:441
|
||||
#: ../intro_basic_networking.rst:446
|
||||
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:444
|
||||
#: ../intro_basic_networking.rst:449
|
||||
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 "
|
||||
@ -2611,7 +2618,7 @@ msgid ""
|
||||
"routing. VXLAN is an example of a UDP-based protocol that uses IP multicast."
|
||||
msgstr ""
|
||||
|
||||
#: ../intro_basic_networking.rst:456
|
||||
#: ../intro_basic_networking.rst:461
|
||||
msgid ""
|
||||
"The *Internet Control Message Protocol* (ICMP) is a protocol used for "
|
||||
"sending control messages over an IP network. For example, a router that "
|
||||
@ -2622,7 +2629,7 @@ msgid ""
|
||||
"\"don't fragment\" flag is set)."
|
||||
msgstr ""
|
||||
|
||||
#: ../intro_basic_networking.rst:464
|
||||
#: ../intro_basic_networking.rst:469
|
||||
msgid ""
|
||||
"The *ping* and *mtr* Linux command-line tools are two examples of network "
|
||||
"utilities that use ICMP."
|
||||
@ -3117,9 +3124,9 @@ msgstr ""
|
||||
#: ../intro_os_networking_overview.rst:116
|
||||
msgid ""
|
||||
"A port is a connection point for attaching a single device, such as the NIC "
|
||||
"of a virtual server, to a virtual network. Also describes the associated "
|
||||
"network configuration, such as the MAC and IP addresses to be used on that "
|
||||
"port."
|
||||
"of a virtual server, to a virtual network. The port also describes the "
|
||||
"associated network configuration, such as the MAC and IP addresses to be "
|
||||
"used on that port."
|
||||
msgstr ""
|
||||
|
||||
#: ../intro_os_networking_overview.rst:124
|
||||
@ -3161,7 +3168,7 @@ msgstr ""
|
||||
|
||||
#: ../intro_os_networking_overview.rst:150
|
||||
msgid ""
|
||||
"The OpenStack networking service is extensible. Extensions serve two "
|
||||
"The OpenStack Networking service is extensible. Extensions serve two "
|
||||
"purposes: they allow the introduction of new features in the API without "
|
||||
"requiring a version change and they allow the introduction of vendor "
|
||||
"specific niche functionality. Applications can programmatically list "
|
||||
|
||||
Loading…
Reference in New Issue
Block a user