diff --git a/doc/openstack-ops/locale/ja.po b/doc/openstack-ops/locale/ja.po index 337a3c61..729cbec3 100644 --- a/doc/openstack-ops/locale/ja.po +++ b/doc/openstack-ops/locale/ja.po @@ -29,9 +29,9 @@ msgid "" msgstr "" "Project-Id-Version: OpenStack Manuals\n" -"POT-Creation-Date: 2015-08-24 06:23+0000\n" -"PO-Revision-Date: 2015-08-25 04:20+0000\n" -"Last-Translator: Tomoyuki KATO \n" +"POT-Creation-Date: 2015-08-25 15:05+0000\n" +"PO-Revision-Date: 2015-08-25 15:06+0000\n" +"Last-Translator: openstackjenkins \n" "Language-Team: Japanese (http://www.transifex.com/openstack/openstack-" "manuals-i18n/language/ja/)\n" "MIME-Version: 1.0\n" @@ -3401,22 +3401,6 @@ msgstr "" "これはユーザーには透過的に行われます。OpenStack のダッシュボードをブラウザで" "開いた状態にすると、仮想マシンの一覧が 30 秒毎に更新されます。" -msgid "" -"Aside from the direct-to-blueprint pathway, there is another very well-" -"regarded mechanism to influence the development roadmap: the user survey. " -"Found at , it allows " -"you to provide details of your deployments and needs, anonymously by " -"default. Each cycle, the user committee analyzes the results and produces a " -"report, including providing specific information to the technical committee " -"and technical leads of the projects." -msgstr "" -"開発ロードマップに影響を与えるために、直接ブループリントに関わる道以外に、非" -"常に高く評価された別の方法があります。ユーザー調査です。 にあります。基本的に匿名で、お使いの環" -"境の詳細、要望を送ることができます。各サイクルで、ユーザーコミッティーが結果" -"を分析して、報告書を作成します。具体的な情報を TC や PTL に提供することを含み" -"ます。" - msgid "Aspects to Watch" msgstr "ウォッチの観点" @@ -10736,6 +10720,30 @@ msgstr "" "と、そのバグは一般には公開されなくなり、脆弱性管理チームだけが参照できるよう" "になります。" +msgid "" +"Open vSwitch, as used in the previous OpenStack Networking examples is a " +"full-featured multilayer virtual switch licensed under the open source " +"Apache 2.0 license. Full documentation can be found at the project's website. In practice, given " +"the preceding configuration, the most common issues are being sure that the " +"required bridges (br-int, br-tun, and br-ex) exist and have the proper ports connected to them.Open vSwitchtroubleshootingtroubleshootingOpen vSwitch" +msgstr "" +"前の OpenStack Networking の例で使用されていたように、Open vSwitch は、オープ" +"ンソースの Apache 2.0 license にてライセンスされている、完全な機能を持つマル" +"チレイヤー仮想スイッチです。ドキュメント全体はプロジェクトの Web サイトにあります。実際のところ、" +"前述の設定を用いた場合、最も一般的な問題は、必要となるブリッジ (br-" +"intbr-tunbr-ex) が存在し、それらに接続さ" +"れる適切なポートを持つことを確認することです。Open vSwitchtroubleshootingtroubleshootingOpen vSwitch" + msgid "OpenStack" msgstr "OpenStack" @@ -15355,6 +15363,17 @@ msgstr "" "す。新しい設定ファイルと関連付けられた表記法を適用して、アップグレードプロセ" "ス完了後に既存の設定ファイルをマージすることを検討すべきです。" +msgid "" +"The packaging system prompts you to update the /etc/cinder/api-" +"paste.ini file. Like the controller upgrade, reject these changes " +"and review the .dpkg-dist file after the the upgrade " +"process completes." +msgstr "" +"パッケージシステムが /etc/cinder/api-paste.ini ファイル" +"を更新するようプロンプトを出します。コントローラーのアップグレードのように、" +"これらの変更を拒否して、アップグレード作業の完了後に .dpkg-dist ファイルをレビューします。" + msgid "" "The packet is then received on the network node. Note that any traffic to " "the l3-agent or dhcp-agent will be visible only within their network " diff --git a/doc/openstack-ops/locale/openstack-ops.pot b/doc/openstack-ops/locale/openstack-ops.pot index 2dd505fd..4c36b893 100644 --- a/doc/openstack-ops/locale/openstack-ops.pot +++ b/doc/openstack-ops/locale/openstack-ops.pot @@ -1,7 +1,7 @@ msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" -"POT-Creation-Date: 2015-08-24 06:01+0000\n" +"POT-Creation-Date: 2015-08-26 06:03+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -1732,7 +1732,7 @@ msgid "To determine the potential features going in to future releases, or to lo msgstr "" #: ./doc/openstack-ops/app_roadmaps.xml:441(para) -msgid "Aside from the direct-to-blueprint pathway, there is another very well-regarded mechanism to influence the development roadmap: the user survey. Found at , it allows you to provide details of your deployments and needs, anonymously by default. Each cycle, the user committee analyzes the results and produces a report, including providing specific information to the technical committee and technical leads of the projects." +msgid "Aside from the direct-to-blueprint pathway, there is another very well-regarded mechanism to influence the development roadmap: the user survey. Found at , it allows you to provide details of your deployments and needs, anonymously by default. Each cycle, the user committee analyzes the results and produces a report, including providing specific information to the technical committee and project team leads." msgstr "" #: ./doc/openstack-ops/app_roadmaps.xml:452(title)