From c7f05c9712f083d948d6676f18e30ca1da394174 Mon Sep 17 00:00:00 2001 From: OpenStack Proposal Bot Date: Sat, 19 Jul 2014 06:00:11 +0000 Subject: [PATCH] Imported Translations from Transifex Change-Id: I8207d0ed6c4e28dab7a8cd38f3c8de33dd0001eb --- .../locale/training-guides.pot | 6613 ++++++++++++++++- 1 file changed, 6510 insertions(+), 103 deletions(-) diff --git a/doc/training-guides/locale/training-guides.pot b/doc/training-guides/locale/training-guides.pot index d4564dd7..0a31b504 100644 --- a/doc/training-guides/locale/training-guides.pot +++ b/doc/training-guides/locale/training-guides.pot @@ -1,7 +1,7 @@ msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" -"POT-Creation-Date: 2014-07-17 06:00+0000\n" +"POT-Creation-Date: 2014-07-19 06:00+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -263,7 +263,7 @@ msgstr "" msgid " big dummy example image" msgstr "" -#: ./doc/training-guides/user-story-includes-template.xml:22(para) ./doc/training-guides/bk000-preface.xml:129(para) ./doc/training-guides/bk000-preface.xml:136(para) ./doc/training-guides/bk000-preface.xml:143(para) ./doc/training-guides/operator-guide/bk002-ch004-operator-controller-node.xml:17(para) ./doc/training-guides/operator-guide/bk002-ch004-operator-controller-node.xml:24(para) ./doc/training-guides/operator-guide/bk002-ch004-operator-controller-node.xml:31(para) ./doc/training-guides/operator-guide/bk002-ch013-operator-object-storage-node.xml:17(para) ./doc/training-guides/operator-guide/bk002-ch013-operator-object-storage-node.xml:32(para) ./doc/training-guides/operator-guide/bk002-ch007-operator-compute-node.xml:17(para) ./doc/training-guides/operator-guide/bk002-ch007-operator-compute-node.xml:24(para) ./doc/training-guides/operator-guide/bk002-ch007-operator-compute-node.xml:31(para) ./doc/training-guides/operator-guide/bk002-ch011-operator-network-node-lab.xml:15(para) ./doc/training-guides/operator-guide/bk002-ch010-operator-network-node.xml:17(para) ./doc/training-guides/operator-guide/bk002-ch010-operator-network-node.xml:24(para) ./doc/training-guides/operator-guide/bk002-ch010-operator-network-node.xml:35(para) ./doc/training-guides/operator-guide/bk002-ch010-operator-network-node.xml:42(para) ./doc/training-guides/operator-guide/bk002-ch010-operator-network-node.xml:49(para) ./doc/training-guides/operator-guide/bk002-ch005-operator-controller-node-lab.xml:15(para) ./doc/training-guides/operator-guide/bk002-ch002-operator-getting-started-lab.xml:15(para) ./doc/training-guides/operator-guide/bk002-ch002-operator-getting-started-lab.xml:22(para) ./doc/training-guides/operator-guide/bk002-ch002-operator-getting-started-lab.xml:29(para) ./doc/training-guides/operator-guide/bk002-ch002-operator-getting-started-lab.xml:36(para) ./doc/training-guides/operator-guide/bk002-ch002-operator-getting-started-lab.xml:43(para) ./doc/training-guides/operator-guide/bk002-ch001-operator-getting-started.xml:25(para) ./doc/training-guides/operator-guide/bk002-ch001-operator-getting-started.xml:32(para) ./doc/training-guides/operator-guide/bk002-ch001-operator-getting-started.xml:39(para) ./doc/training-guides/operator-guide/bk002-ch001-operator-getting-started.xml:46(para) ./doc/training-guides/operator-guide/bk002-ch001-operator-getting-started.xml:53(para) ./doc/training-guides/operator-guide/bk002-ch008-operator-compute-node-lab.xml:15(para) ./doc/training-guides/operator-guide/bk002-ch014-operator-object-storage-node-lab.xml:15(para) ./doc/training-guides/operator-guide/bk002-ch014-operator-object-storage-node-lab.xml:22(para) ./doc/training-guides/operator-guide/bk002-ch014-operator-object-storage-node-lab.xml:29(para) ./doc/training-guides/operator-guide/bk002-ch014-operator-object-storage-node-lab.xml:36(para) ./doc/training-guides/associate-guide/bk001-ch005-associate-compute-node.xml:17(para) ./doc/training-guides/associate-guide/bk001-ch005-associate-compute-node.xml:24(para) ./doc/training-guides/associate-guide/bk001-ch005-associate-compute-node.xml:31(para) ./doc/training-guides/associate-guide/bk001-ch005-associate-compute-node.xml:40(para) ./doc/training-guides/associate-guide/bk001-ch005-associate-compute-node.xml:47(para) ./doc/training-guides/associate-guide/bk001-ch005-associate-compute-node.xml:54(para) ./doc/training-guides/associate-guide/bk001-ch005-associate-compute-node.xml:61(para) ./doc/training-guides/associate-guide/bk001-ch005-associate-compute-node.xml:68(para) ./doc/training-guides/associate-guide/bk001-ch005-associate-compute-node.xml:75(para) ./doc/training-guides/associate-guide/bk001-ch007-associate-network-node.xml:17(para) ./doc/training-guides/associate-guide/bk001-ch007-associate-network-node.xml:24(para) ./doc/training-guides/associate-guide/bk001-ch007-associate-network-node.xml:33(para) ./doc/training-guides/associate-guide/bk001-ch007-associate-network-node.xml:40(para) ./doc/training-guides/associate-guide/bk001-ch001-associate-getting-started.xml:27(para) ./doc/training-guides/associate-guide/bk001-ch001-associate-getting-started.xml:34(para) ./doc/training-guides/associate-guide/bk001-ch001-associate-getting-started.xml:41(para) ./doc/training-guides/associate-guide/bk001-ch001-associate-getting-started.xml:48(para) ./doc/training-guides/associate-guide/bk001-ch001-associate-getting-started.xml:55(para) ./doc/training-guides/associate-guide/bk001-ch009-associate-object-storage-node.xml:17(para) ./doc/training-guides/associate-guide/bk001-ch009-associate-object-storage-node.xml:24(para) ./doc/training-guides/associate-guide/bk001-ch009-associate-object-storage-node.xml:33(para) ./doc/training-guides/associate-guide/bk001-ch003-associate-controller-node.xml:17(para) ./doc/training-guides/associate-guide/bk001-ch003-associate-controller-node.xml:24(para) ./doc/training-guides/associate-guide/bk001-ch003-associate-controller-node.xml:31(para) ./doc/training-guides/associate-guide/bk001-ch003-associate-controller-node.xml:40(para) ./doc/training-guides/associate-guide/bk001-ch003-associate-controller-node.xml:47(para) ./doc/training-guides/associate-guide/bk001-ch003-associate-controller-node.xml:54(para) ./doc/training-guides/associate-guide/bk001-ch003-associate-controller-node.xml:61(para) ./doc/training-guides/associate-guide/bk001-ch003-associate-controller-node.xml:68(para) ./doc/training-guides/associate-guide/bk001-ch003-associate-controller-node.xml:75(para) ./doc/training-guides/associate-guide/bk001-ch003-associate-controller-node.xml:82(para) ./doc/training-guides/developer-guide/bk003-ch001-developer-getting-started.xml:25(para) ./doc/training-guides/developer-guide/bk003-ch001-developer-getting-started.xml:32(para) ./doc/training-guides/developer-guide/bk003-ch001-developer-getting-started.xml:39(para) ./doc/training-guides/developer-guide/bk003-ch001-developer-getting-started.xml:46(para) ./doc/training-guides/developer-guide/bk003-ch001-developer-getting-started.xml:53(para) ./doc/training-guides/developer-guide/bk003-ch002-developer-getting-started-lab.xml:15(para) ./doc/training-guides/developer-guide/bk003-ch002-developer-getting-started-lab.xml:22(para) ./doc/training-guides/developer-guide/bk003-ch002-developer-getting-started-lab.xml:29(para) ./doc/training-guides/developer-guide/bk003-ch002-developer-getting-started-lab.xml:36(para) ./doc/training-guides/developer-guide/bk003-ch002-developer-getting-started-lab.xml:43(para) +#: ./doc/training-guides/user-story-includes-template.xml:22(para) ./doc/training-guides/bk000-preface.xml:129(para) ./doc/training-guides/bk000-preface.xml:136(para) ./doc/training-guides/bk000-preface.xml:143(para) ./doc/training-guides/operator-guide/bk002-ch004-operator-controller-node.xml:17(para) ./doc/training-guides/operator-guide/bk002-ch004-operator-controller-node.xml:24(para) ./doc/training-guides/operator-guide/bk002-ch004-operator-controller-node.xml:31(para) ./doc/training-guides/operator-guide/bk002-ch013-operator-object-storage-node.xml:17(para) ./doc/training-guides/operator-guide/bk002-ch013-operator-object-storage-node.xml:32(para) ./doc/training-guides/operator-guide/bk002-ch007-operator-compute-node.xml:17(para) ./doc/training-guides/operator-guide/bk002-ch007-operator-compute-node.xml:24(para) ./doc/training-guides/operator-guide/bk002-ch007-operator-compute-node.xml:31(para) ./doc/training-guides/operator-guide/bk002-ch011-operator-network-node-lab.xml:15(para) ./doc/training-guides/operator-guide/bk002-ch010-operator-network-node.xml:17(para) ./doc/training-guides/operator-guide/bk002-ch010-operator-network-node.xml:24(para) ./doc/training-guides/operator-guide/bk002-ch010-operator-network-node.xml:35(para) ./doc/training-guides/operator-guide/bk002-ch010-operator-network-node.xml:42(para) ./doc/training-guides/operator-guide/bk002-ch010-operator-network-node.xml:49(para) ./doc/training-guides/operator-guide/bk002-ch005-operator-controller-node-lab.xml:15(para) ./doc/training-guides/operator-guide/bk002-ch002-operator-getting-started-lab.xml:15(para) ./doc/training-guides/operator-guide/bk002-ch002-operator-getting-started-lab.xml:22(para) ./doc/training-guides/operator-guide/bk002-ch002-operator-getting-started-lab.xml:29(para) ./doc/training-guides/operator-guide/bk002-ch002-operator-getting-started-lab.xml:36(para) ./doc/training-guides/operator-guide/bk002-ch002-operator-getting-started-lab.xml:43(para) ./doc/training-guides/operator-guide/bk002-ch001-operator-getting-started.xml:25(para) ./doc/training-guides/operator-guide/bk002-ch001-operator-getting-started.xml:32(para) ./doc/training-guides/operator-guide/bk002-ch001-operator-getting-started.xml:39(para) ./doc/training-guides/operator-guide/bk002-ch001-operator-getting-started.xml:46(para) ./doc/training-guides/operator-guide/bk002-ch001-operator-getting-started.xml:53(para) ./doc/training-guides/operator-guide/bk002-ch008-operator-compute-node-lab.xml:15(para) ./doc/training-guides/operator-guide/bk002-ch014-operator-object-storage-node-lab.xml:15(para) ./doc/training-guides/operator-guide/bk002-ch014-operator-object-storage-node-lab.xml:22(para) ./doc/training-guides/operator-guide/bk002-ch014-operator-object-storage-node-lab.xml:29(para) ./doc/training-guides/operator-guide/bk002-ch014-operator-object-storage-node-lab.xml:36(para) ./doc/training-guides/associate-guide/bk001-ch005-associate-compute-node.xml:17(para) ./doc/training-guides/associate-guide/bk001-ch005-associate-compute-node.xml:24(para) ./doc/training-guides/associate-guide/bk001-ch005-associate-compute-node.xml:31(para) ./doc/training-guides/associate-guide/bk001-ch005-associate-compute-node.xml:40(para) ./doc/training-guides/associate-guide/bk001-ch005-associate-compute-node.xml:47(para) ./doc/training-guides/associate-guide/bk001-ch005-associate-compute-node.xml:54(para) ./doc/training-guides/associate-guide/bk001-ch005-associate-compute-node.xml:61(para) ./doc/training-guides/associate-guide/bk001-ch005-associate-compute-node.xml:68(para) ./doc/training-guides/associate-guide/bk001-ch005-associate-compute-node.xml:75(para) ./doc/training-guides/associate-guide/bk001-ch001-associate-getting-started.xml:27(para) ./doc/training-guides/associate-guide/bk001-ch001-associate-getting-started.xml:34(para) ./doc/training-guides/associate-guide/bk001-ch001-associate-getting-started.xml:41(para) ./doc/training-guides/associate-guide/bk001-ch001-associate-getting-started.xml:48(para) ./doc/training-guides/associate-guide/bk001-ch001-associate-getting-started.xml:55(para) ./doc/training-guides/associate-guide/bk001-ch009-associate-object-storage-node.xml:17(para) ./doc/training-guides/associate-guide/bk001-ch009-associate-object-storage-node.xml:24(para) ./doc/training-guides/associate-guide/bk001-ch009-associate-object-storage-node.xml:33(para) ./doc/training-guides/associate-guide/bk001-ch003-associate-controller-node.xml:17(para) ./doc/training-guides/associate-guide/bk001-ch003-associate-controller-node.xml:24(para) ./doc/training-guides/associate-guide/bk001-ch003-associate-controller-node.xml:31(para) ./doc/training-guides/associate-guide/bk001-ch003-associate-controller-node.xml:40(para) ./doc/training-guides/associate-guide/bk001-ch003-associate-controller-node.xml:47(para) ./doc/training-guides/associate-guide/bk001-ch003-associate-controller-node.xml:54(para) ./doc/training-guides/associate-guide/bk001-ch003-associate-controller-node.xml:61(para) ./doc/training-guides/associate-guide/bk001-ch003-associate-controller-node.xml:68(para) ./doc/training-guides/associate-guide/bk001-ch003-associate-controller-node.xml:75(para) ./doc/training-guides/associate-guide/bk001-ch003-associate-controller-node.xml:82(para) ./doc/training-guides/developer-guide/bk003-ch001-developer-getting-started.xml:25(para) ./doc/training-guides/developer-guide/bk003-ch001-developer-getting-started.xml:32(para) ./doc/training-guides/developer-guide/bk003-ch001-developer-getting-started.xml:39(para) ./doc/training-guides/developer-guide/bk003-ch001-developer-getting-started.xml:46(para) ./doc/training-guides/developer-guide/bk003-ch001-developer-getting-started.xml:53(para) ./doc/training-guides/developer-guide/bk003-ch002-developer-getting-started-lab.xml:15(para) ./doc/training-guides/developer-guide/bk003-ch002-developer-getting-started-lab.xml:22(para) ./doc/training-guides/developer-guide/bk003-ch002-developer-getting-started-lab.xml:29(para) ./doc/training-guides/developer-guide/bk003-ch002-developer-getting-started-lab.xml:36(para) ./doc/training-guides/developer-guide/bk003-ch002-developer-getting-started-lab.xml:43(para) msgid "image source" msgstr "" @@ -341,11 +341,11 @@ msgstr "" msgid "Important Terms" msgstr "" -#: ./doc/training-guides/bk000-preface.xml:129(para) ./doc/training-guides/bk000-preface.xml:136(para) ./doc/training-guides/bk000-preface.xml:143(para) ./doc/training-guides/operator-guide/bk002-ch004-operator-controller-node.xml:17(para) ./doc/training-guides/operator-guide/bk002-ch004-operator-controller-node.xml:24(para) ./doc/training-guides/operator-guide/bk002-ch004-operator-controller-node.xml:31(para) ./doc/training-guides/operator-guide/bk002-ch013-operator-object-storage-node.xml:17(para) ./doc/training-guides/operator-guide/bk002-ch013-operator-object-storage-node.xml:32(para) ./doc/training-guides/operator-guide/bk002-ch007-operator-compute-node.xml:17(para) ./doc/training-guides/operator-guide/bk002-ch007-operator-compute-node.xml:24(para) ./doc/training-guides/operator-guide/bk002-ch007-operator-compute-node.xml:31(para) ./doc/training-guides/operator-guide/bk002-ch011-operator-network-node-lab.xml:15(para) ./doc/training-guides/operator-guide/bk002-ch010-operator-network-node.xml:17(para) ./doc/training-guides/operator-guide/bk002-ch010-operator-network-node.xml:24(para) ./doc/training-guides/operator-guide/bk002-ch010-operator-network-node.xml:35(para) ./doc/training-guides/operator-guide/bk002-ch010-operator-network-node.xml:42(para) ./doc/training-guides/operator-guide/bk002-ch010-operator-network-node.xml:49(para) ./doc/training-guides/operator-guide/bk002-ch005-operator-controller-node-lab.xml:15(para) ./doc/training-guides/operator-guide/bk002-ch002-operator-getting-started-lab.xml:15(para) ./doc/training-guides/operator-guide/bk002-ch002-operator-getting-started-lab.xml:22(para) ./doc/training-guides/operator-guide/bk002-ch002-operator-getting-started-lab.xml:29(para) ./doc/training-guides/operator-guide/bk002-ch002-operator-getting-started-lab.xml:36(para) ./doc/training-guides/operator-guide/bk002-ch002-operator-getting-started-lab.xml:43(para) ./doc/training-guides/operator-guide/bk002-ch001-operator-getting-started.xml:25(para) ./doc/training-guides/operator-guide/bk002-ch001-operator-getting-started.xml:32(para) ./doc/training-guides/operator-guide/bk002-ch001-operator-getting-started.xml:39(para) ./doc/training-guides/operator-guide/bk002-ch001-operator-getting-started.xml:46(para) ./doc/training-guides/operator-guide/bk002-ch001-operator-getting-started.xml:53(para) ./doc/training-guides/operator-guide/bk002-ch008-operator-compute-node-lab.xml:15(para) ./doc/training-guides/operator-guide/bk002-ch014-operator-object-storage-node-lab.xml:15(para) ./doc/training-guides/operator-guide/bk002-ch014-operator-object-storage-node-lab.xml:22(para) ./doc/training-guides/operator-guide/bk002-ch014-operator-object-storage-node-lab.xml:29(para) ./doc/training-guides/operator-guide/bk002-ch014-operator-object-storage-node-lab.xml:36(para) ./doc/training-guides/associate-guide/bk001-ch005-associate-compute-node.xml:17(para) ./doc/training-guides/associate-guide/bk001-ch005-associate-compute-node.xml:24(para) ./doc/training-guides/associate-guide/bk001-ch005-associate-compute-node.xml:31(para) ./doc/training-guides/associate-guide/bk001-ch005-associate-compute-node.xml:40(para) ./doc/training-guides/associate-guide/bk001-ch005-associate-compute-node.xml:47(para) ./doc/training-guides/associate-guide/bk001-ch005-associate-compute-node.xml:54(para) ./doc/training-guides/associate-guide/bk001-ch005-associate-compute-node.xml:61(para) ./doc/training-guides/associate-guide/bk001-ch005-associate-compute-node.xml:68(para) ./doc/training-guides/associate-guide/bk001-ch005-associate-compute-node.xml:75(para) ./doc/training-guides/associate-guide/bk001-ch007-associate-network-node.xml:17(para) ./doc/training-guides/associate-guide/bk001-ch007-associate-network-node.xml:24(para) ./doc/training-guides/associate-guide/bk001-ch007-associate-network-node.xml:33(para) ./doc/training-guides/associate-guide/bk001-ch007-associate-network-node.xml:40(para) ./doc/training-guides/associate-guide/bk001-ch001-associate-getting-started.xml:27(para) ./doc/training-guides/associate-guide/bk001-ch001-associate-getting-started.xml:34(para) ./doc/training-guides/associate-guide/bk001-ch001-associate-getting-started.xml:41(para) ./doc/training-guides/associate-guide/bk001-ch001-associate-getting-started.xml:48(para) ./doc/training-guides/associate-guide/bk001-ch001-associate-getting-started.xml:55(para) ./doc/training-guides/associate-guide/bk001-ch009-associate-object-storage-node.xml:17(para) ./doc/training-guides/associate-guide/bk001-ch009-associate-object-storage-node.xml:24(para) ./doc/training-guides/associate-guide/bk001-ch009-associate-object-storage-node.xml:33(para) ./doc/training-guides/associate-guide/bk001-ch003-associate-controller-node.xml:17(para) ./doc/training-guides/associate-guide/bk001-ch003-associate-controller-node.xml:24(para) ./doc/training-guides/associate-guide/bk001-ch003-associate-controller-node.xml:31(para) ./doc/training-guides/associate-guide/bk001-ch003-associate-controller-node.xml:40(para) ./doc/training-guides/associate-guide/bk001-ch003-associate-controller-node.xml:47(para) ./doc/training-guides/associate-guide/bk001-ch003-associate-controller-node.xml:54(para) ./doc/training-guides/associate-guide/bk001-ch003-associate-controller-node.xml:61(para) ./doc/training-guides/associate-guide/bk001-ch003-associate-controller-node.xml:68(para) ./doc/training-guides/associate-guide/bk001-ch003-associate-controller-node.xml:75(para) ./doc/training-guides/associate-guide/bk001-ch003-associate-controller-node.xml:82(para) ./doc/training-guides/developer-guide/bk003-ch001-developer-getting-started.xml:25(para) ./doc/training-guides/developer-guide/bk003-ch001-developer-getting-started.xml:32(para) ./doc/training-guides/developer-guide/bk003-ch001-developer-getting-started.xml:39(para) ./doc/training-guides/developer-guide/bk003-ch001-developer-getting-started.xml:46(para) ./doc/training-guides/developer-guide/bk003-ch001-developer-getting-started.xml:53(para) ./doc/training-guides/developer-guide/bk003-ch002-developer-getting-started-lab.xml:15(para) ./doc/training-guides/developer-guide/bk003-ch002-developer-getting-started-lab.xml:22(para) ./doc/training-guides/developer-guide/bk003-ch002-developer-getting-started-lab.xml:29(para) ./doc/training-guides/developer-guide/bk003-ch002-developer-getting-started-lab.xml:36(para) ./doc/training-guides/developer-guide/bk003-ch002-developer-getting-started-lab.xml:43(para) +#: ./doc/training-guides/bk000-preface.xml:129(para) ./doc/training-guides/bk000-preface.xml:136(para) ./doc/training-guides/bk000-preface.xml:143(para) ./doc/training-guides/operator-guide/bk002-ch004-operator-controller-node.xml:17(para) ./doc/training-guides/operator-guide/bk002-ch004-operator-controller-node.xml:24(para) ./doc/training-guides/operator-guide/bk002-ch004-operator-controller-node.xml:31(para) ./doc/training-guides/operator-guide/bk002-ch013-operator-object-storage-node.xml:17(para) ./doc/training-guides/operator-guide/bk002-ch013-operator-object-storage-node.xml:32(para) ./doc/training-guides/operator-guide/bk002-ch007-operator-compute-node.xml:17(para) ./doc/training-guides/operator-guide/bk002-ch007-operator-compute-node.xml:24(para) ./doc/training-guides/operator-guide/bk002-ch007-operator-compute-node.xml:31(para) ./doc/training-guides/operator-guide/bk002-ch011-operator-network-node-lab.xml:15(para) ./doc/training-guides/operator-guide/bk002-ch010-operator-network-node.xml:17(para) ./doc/training-guides/operator-guide/bk002-ch010-operator-network-node.xml:24(para) ./doc/training-guides/operator-guide/bk002-ch010-operator-network-node.xml:35(para) ./doc/training-guides/operator-guide/bk002-ch010-operator-network-node.xml:42(para) ./doc/training-guides/operator-guide/bk002-ch010-operator-network-node.xml:49(para) ./doc/training-guides/operator-guide/bk002-ch005-operator-controller-node-lab.xml:15(para) ./doc/training-guides/operator-guide/bk002-ch002-operator-getting-started-lab.xml:15(para) ./doc/training-guides/operator-guide/bk002-ch002-operator-getting-started-lab.xml:22(para) ./doc/training-guides/operator-guide/bk002-ch002-operator-getting-started-lab.xml:29(para) ./doc/training-guides/operator-guide/bk002-ch002-operator-getting-started-lab.xml:36(para) ./doc/training-guides/operator-guide/bk002-ch002-operator-getting-started-lab.xml:43(para) ./doc/training-guides/operator-guide/bk002-ch001-operator-getting-started.xml:25(para) ./doc/training-guides/operator-guide/bk002-ch001-operator-getting-started.xml:32(para) ./doc/training-guides/operator-guide/bk002-ch001-operator-getting-started.xml:39(para) ./doc/training-guides/operator-guide/bk002-ch001-operator-getting-started.xml:46(para) ./doc/training-guides/operator-guide/bk002-ch001-operator-getting-started.xml:53(para) ./doc/training-guides/operator-guide/bk002-ch008-operator-compute-node-lab.xml:15(para) ./doc/training-guides/operator-guide/bk002-ch014-operator-object-storage-node-lab.xml:15(para) ./doc/training-guides/operator-guide/bk002-ch014-operator-object-storage-node-lab.xml:22(para) ./doc/training-guides/operator-guide/bk002-ch014-operator-object-storage-node-lab.xml:29(para) ./doc/training-guides/operator-guide/bk002-ch014-operator-object-storage-node-lab.xml:36(para) ./doc/training-guides/associate-guide/bk001-ch005-associate-compute-node.xml:17(para) ./doc/training-guides/associate-guide/bk001-ch005-associate-compute-node.xml:24(para) ./doc/training-guides/associate-guide/bk001-ch005-associate-compute-node.xml:31(para) ./doc/training-guides/associate-guide/bk001-ch005-associate-compute-node.xml:40(para) ./doc/training-guides/associate-guide/bk001-ch005-associate-compute-node.xml:47(para) ./doc/training-guides/associate-guide/bk001-ch005-associate-compute-node.xml:54(para) ./doc/training-guides/associate-guide/bk001-ch005-associate-compute-node.xml:61(para) ./doc/training-guides/associate-guide/bk001-ch005-associate-compute-node.xml:68(para) ./doc/training-guides/associate-guide/bk001-ch005-associate-compute-node.xml:75(para) ./doc/training-guides/associate-guide/bk001-ch001-associate-getting-started.xml:27(para) ./doc/training-guides/associate-guide/bk001-ch001-associate-getting-started.xml:34(para) ./doc/training-guides/associate-guide/bk001-ch001-associate-getting-started.xml:41(para) ./doc/training-guides/associate-guide/bk001-ch001-associate-getting-started.xml:48(para) ./doc/training-guides/associate-guide/bk001-ch001-associate-getting-started.xml:55(para) ./doc/training-guides/associate-guide/bk001-ch009-associate-object-storage-node.xml:17(para) ./doc/training-guides/associate-guide/bk001-ch009-associate-object-storage-node.xml:24(para) ./doc/training-guides/associate-guide/bk001-ch009-associate-object-storage-node.xml:33(para) ./doc/training-guides/associate-guide/bk001-ch003-associate-controller-node.xml:17(para) ./doc/training-guides/associate-guide/bk001-ch003-associate-controller-node.xml:24(para) ./doc/training-guides/associate-guide/bk001-ch003-associate-controller-node.xml:31(para) ./doc/training-guides/associate-guide/bk001-ch003-associate-controller-node.xml:40(para) ./doc/training-guides/associate-guide/bk001-ch003-associate-controller-node.xml:47(para) ./doc/training-guides/associate-guide/bk001-ch003-associate-controller-node.xml:54(para) ./doc/training-guides/associate-guide/bk001-ch003-associate-controller-node.xml:61(para) ./doc/training-guides/associate-guide/bk001-ch003-associate-controller-node.xml:68(para) ./doc/training-guides/associate-guide/bk001-ch003-associate-controller-node.xml:75(para) ./doc/training-guides/associate-guide/bk001-ch003-associate-controller-node.xml:82(para) ./doc/training-guides/developer-guide/bk003-ch001-developer-getting-started.xml:25(para) ./doc/training-guides/developer-guide/bk003-ch001-developer-getting-started.xml:32(para) ./doc/training-guides/developer-guide/bk003-ch001-developer-getting-started.xml:39(para) ./doc/training-guides/developer-guide/bk003-ch001-developer-getting-started.xml:46(para) ./doc/training-guides/developer-guide/bk003-ch001-developer-getting-started.xml:53(para) ./doc/training-guides/developer-guide/bk003-ch002-developer-getting-started-lab.xml:15(para) ./doc/training-guides/developer-guide/bk003-ch002-developer-getting-started-lab.xml:22(para) ./doc/training-guides/developer-guide/bk003-ch002-developer-getting-started-lab.xml:29(para) ./doc/training-guides/developer-guide/bk003-ch002-developer-getting-started-lab.xml:36(para) ./doc/training-guides/developer-guide/bk003-ch002-developer-getting-started-lab.xml:43(para) msgid "Remote content not available" msgstr "" -#: ./doc/training-guides/bk000-preface.xml:129(link) ./doc/training-guides/bk000-preface.xml:136(link) ./doc/training-guides/bk000-preface.xml:143(link) ./doc/training-guides/operator-guide/bk002-ch004-operator-controller-node.xml:17(link) ./doc/training-guides/operator-guide/bk002-ch004-operator-controller-node.xml:24(link) ./doc/training-guides/operator-guide/bk002-ch004-operator-controller-node.xml:31(link) ./doc/training-guides/operator-guide/bk002-ch013-operator-object-storage-node.xml:17(link) ./doc/training-guides/operator-guide/bk002-ch013-operator-object-storage-node.xml:32(link) ./doc/training-guides/operator-guide/bk002-ch007-operator-compute-node.xml:17(link) ./doc/training-guides/operator-guide/bk002-ch007-operator-compute-node.xml:24(link) ./doc/training-guides/operator-guide/bk002-ch007-operator-compute-node.xml:31(link) ./doc/training-guides/operator-guide/bk002-ch011-operator-network-node-lab.xml:15(link) ./doc/training-guides/operator-guide/bk002-ch010-operator-network-node.xml:17(link) ./doc/training-guides/operator-guide/bk002-ch010-operator-network-node.xml:24(link) ./doc/training-guides/operator-guide/bk002-ch010-operator-network-node.xml:35(link) ./doc/training-guides/operator-guide/bk002-ch010-operator-network-node.xml:42(link) ./doc/training-guides/operator-guide/bk002-ch010-operator-network-node.xml:49(link) ./doc/training-guides/operator-guide/bk002-ch005-operator-controller-node-lab.xml:15(link) ./doc/training-guides/operator-guide/bk002-ch002-operator-getting-started-lab.xml:15(link) ./doc/training-guides/operator-guide/bk002-ch002-operator-getting-started-lab.xml:22(link) ./doc/training-guides/operator-guide/bk002-ch002-operator-getting-started-lab.xml:29(link) ./doc/training-guides/operator-guide/bk002-ch002-operator-getting-started-lab.xml:36(link) ./doc/training-guides/operator-guide/bk002-ch002-operator-getting-started-lab.xml:43(link) ./doc/training-guides/operator-guide/bk002-ch001-operator-getting-started.xml:25(link) ./doc/training-guides/operator-guide/bk002-ch001-operator-getting-started.xml:32(link) ./doc/training-guides/operator-guide/bk002-ch001-operator-getting-started.xml:39(link) ./doc/training-guides/operator-guide/bk002-ch001-operator-getting-started.xml:46(link) ./doc/training-guides/operator-guide/bk002-ch001-operator-getting-started.xml:53(link) ./doc/training-guides/operator-guide/bk002-ch008-operator-compute-node-lab.xml:15(link) ./doc/training-guides/operator-guide/bk002-ch014-operator-object-storage-node-lab.xml:15(link) ./doc/training-guides/operator-guide/bk002-ch014-operator-object-storage-node-lab.xml:22(link) ./doc/training-guides/operator-guide/bk002-ch014-operator-object-storage-node-lab.xml:29(link) ./doc/training-guides/operator-guide/bk002-ch014-operator-object-storage-node-lab.xml:36(link) ./doc/training-guides/associate-guide/bk001-ch005-associate-compute-node.xml:17(link) ./doc/training-guides/associate-guide/bk001-ch005-associate-compute-node.xml:24(link) ./doc/training-guides/associate-guide/bk001-ch005-associate-compute-node.xml:31(link) ./doc/training-guides/associate-guide/bk001-ch005-associate-compute-node.xml:40(link) ./doc/training-guides/associate-guide/bk001-ch005-associate-compute-node.xml:47(link) ./doc/training-guides/associate-guide/bk001-ch005-associate-compute-node.xml:54(link) ./doc/training-guides/associate-guide/bk001-ch005-associate-compute-node.xml:61(link) ./doc/training-guides/associate-guide/bk001-ch005-associate-compute-node.xml:68(link) ./doc/training-guides/associate-guide/bk001-ch005-associate-compute-node.xml:75(link) ./doc/training-guides/associate-guide/bk001-ch007-associate-network-node.xml:17(link) ./doc/training-guides/associate-guide/bk001-ch007-associate-network-node.xml:24(link) ./doc/training-guides/associate-guide/bk001-ch007-associate-network-node.xml:33(link) ./doc/training-guides/associate-guide/bk001-ch007-associate-network-node.xml:40(link) ./doc/training-guides/associate-guide/bk001-ch001-associate-getting-started.xml:27(link) ./doc/training-guides/associate-guide/bk001-ch001-associate-getting-started.xml:34(link) ./doc/training-guides/associate-guide/bk001-ch001-associate-getting-started.xml:41(link) ./doc/training-guides/associate-guide/bk001-ch001-associate-getting-started.xml:48(link) ./doc/training-guides/associate-guide/bk001-ch001-associate-getting-started.xml:55(link) ./doc/training-guides/associate-guide/bk001-ch009-associate-object-storage-node.xml:17(link) ./doc/training-guides/associate-guide/bk001-ch009-associate-object-storage-node.xml:24(link) ./doc/training-guides/associate-guide/bk001-ch009-associate-object-storage-node.xml:33(link) ./doc/training-guides/associate-guide/bk001-ch003-associate-controller-node.xml:17(link) ./doc/training-guides/associate-guide/bk001-ch003-associate-controller-node.xml:24(link) ./doc/training-guides/associate-guide/bk001-ch003-associate-controller-node.xml:31(link) ./doc/training-guides/associate-guide/bk001-ch003-associate-controller-node.xml:40(link) ./doc/training-guides/associate-guide/bk001-ch003-associate-controller-node.xml:47(link) ./doc/training-guides/associate-guide/bk001-ch003-associate-controller-node.xml:54(link) ./doc/training-guides/associate-guide/bk001-ch003-associate-controller-node.xml:61(link) ./doc/training-guides/associate-guide/bk001-ch003-associate-controller-node.xml:68(link) ./doc/training-guides/associate-guide/bk001-ch003-associate-controller-node.xml:75(link) ./doc/training-guides/associate-guide/bk001-ch003-associate-controller-node.xml:82(link) ./doc/training-guides/developer-guide/bk003-ch001-developer-getting-started.xml:25(link) ./doc/training-guides/developer-guide/bk003-ch001-developer-getting-started.xml:32(link) ./doc/training-guides/developer-guide/bk003-ch001-developer-getting-started.xml:39(link) ./doc/training-guides/developer-guide/bk003-ch001-developer-getting-started.xml:46(link) ./doc/training-guides/developer-guide/bk003-ch001-developer-getting-started.xml:53(link) ./doc/training-guides/developer-guide/bk003-ch002-developer-getting-started-lab.xml:15(link) ./doc/training-guides/developer-guide/bk003-ch002-developer-getting-started-lab.xml:22(link) ./doc/training-guides/developer-guide/bk003-ch002-developer-getting-started-lab.xml:29(link) ./doc/training-guides/developer-guide/bk003-ch002-developer-getting-started-lab.xml:36(link) ./doc/training-guides/developer-guide/bk003-ch002-developer-getting-started-lab.xml:43(link) +#: ./doc/training-guides/bk000-preface.xml:129(link) ./doc/training-guides/bk000-preface.xml:136(link) ./doc/training-guides/bk000-preface.xml:143(link) ./doc/training-guides/operator-guide/bk002-ch004-operator-controller-node.xml:17(link) ./doc/training-guides/operator-guide/bk002-ch004-operator-controller-node.xml:24(link) ./doc/training-guides/operator-guide/bk002-ch004-operator-controller-node.xml:31(link) ./doc/training-guides/operator-guide/bk002-ch013-operator-object-storage-node.xml:17(link) ./doc/training-guides/operator-guide/bk002-ch013-operator-object-storage-node.xml:32(link) ./doc/training-guides/operator-guide/bk002-ch007-operator-compute-node.xml:17(link) ./doc/training-guides/operator-guide/bk002-ch007-operator-compute-node.xml:24(link) ./doc/training-guides/operator-guide/bk002-ch007-operator-compute-node.xml:31(link) ./doc/training-guides/operator-guide/bk002-ch011-operator-network-node-lab.xml:15(link) ./doc/training-guides/operator-guide/bk002-ch010-operator-network-node.xml:17(link) ./doc/training-guides/operator-guide/bk002-ch010-operator-network-node.xml:24(link) ./doc/training-guides/operator-guide/bk002-ch010-operator-network-node.xml:35(link) ./doc/training-guides/operator-guide/bk002-ch010-operator-network-node.xml:42(link) ./doc/training-guides/operator-guide/bk002-ch010-operator-network-node.xml:49(link) ./doc/training-guides/operator-guide/bk002-ch005-operator-controller-node-lab.xml:15(link) ./doc/training-guides/operator-guide/bk002-ch002-operator-getting-started-lab.xml:15(link) ./doc/training-guides/operator-guide/bk002-ch002-operator-getting-started-lab.xml:22(link) ./doc/training-guides/operator-guide/bk002-ch002-operator-getting-started-lab.xml:29(link) ./doc/training-guides/operator-guide/bk002-ch002-operator-getting-started-lab.xml:36(link) ./doc/training-guides/operator-guide/bk002-ch002-operator-getting-started-lab.xml:43(link) ./doc/training-guides/operator-guide/bk002-ch001-operator-getting-started.xml:25(link) ./doc/training-guides/operator-guide/bk002-ch001-operator-getting-started.xml:32(link) ./doc/training-guides/operator-guide/bk002-ch001-operator-getting-started.xml:39(link) ./doc/training-guides/operator-guide/bk002-ch001-operator-getting-started.xml:46(link) ./doc/training-guides/operator-guide/bk002-ch001-operator-getting-started.xml:53(link) ./doc/training-guides/operator-guide/bk002-ch008-operator-compute-node-lab.xml:15(link) ./doc/training-guides/operator-guide/bk002-ch014-operator-object-storage-node-lab.xml:15(link) ./doc/training-guides/operator-guide/bk002-ch014-operator-object-storage-node-lab.xml:22(link) ./doc/training-guides/operator-guide/bk002-ch014-operator-object-storage-node-lab.xml:29(link) ./doc/training-guides/operator-guide/bk002-ch014-operator-object-storage-node-lab.xml:36(link) ./doc/training-guides/associate-guide/bk001-ch005-associate-compute-node.xml:17(link) ./doc/training-guides/associate-guide/bk001-ch005-associate-compute-node.xml:24(link) ./doc/training-guides/associate-guide/bk001-ch005-associate-compute-node.xml:31(link) ./doc/training-guides/associate-guide/bk001-ch005-associate-compute-node.xml:40(link) ./doc/training-guides/associate-guide/bk001-ch005-associate-compute-node.xml:47(link) ./doc/training-guides/associate-guide/bk001-ch005-associate-compute-node.xml:54(link) ./doc/training-guides/associate-guide/bk001-ch005-associate-compute-node.xml:61(link) ./doc/training-guides/associate-guide/bk001-ch005-associate-compute-node.xml:68(link) ./doc/training-guides/associate-guide/bk001-ch005-associate-compute-node.xml:75(link) ./doc/training-guides/associate-guide/bk001-ch001-associate-getting-started.xml:27(link) ./doc/training-guides/associate-guide/bk001-ch001-associate-getting-started.xml:34(link) ./doc/training-guides/associate-guide/bk001-ch001-associate-getting-started.xml:41(link) ./doc/training-guides/associate-guide/bk001-ch001-associate-getting-started.xml:48(link) ./doc/training-guides/associate-guide/bk001-ch001-associate-getting-started.xml:55(link) ./doc/training-guides/associate-guide/bk001-ch009-associate-object-storage-node.xml:17(link) ./doc/training-guides/associate-guide/bk001-ch009-associate-object-storage-node.xml:24(link) ./doc/training-guides/associate-guide/bk001-ch009-associate-object-storage-node.xml:33(link) ./doc/training-guides/associate-guide/bk001-ch003-associate-controller-node.xml:17(link) ./doc/training-guides/associate-guide/bk001-ch003-associate-controller-node.xml:24(link) ./doc/training-guides/associate-guide/bk001-ch003-associate-controller-node.xml:31(link) ./doc/training-guides/associate-guide/bk001-ch003-associate-controller-node.xml:40(link) ./doc/training-guides/associate-guide/bk001-ch003-associate-controller-node.xml:47(link) ./doc/training-guides/associate-guide/bk001-ch003-associate-controller-node.xml:54(link) ./doc/training-guides/associate-guide/bk001-ch003-associate-controller-node.xml:61(link) ./doc/training-guides/associate-guide/bk001-ch003-associate-controller-node.xml:68(link) ./doc/training-guides/associate-guide/bk001-ch003-associate-controller-node.xml:75(link) ./doc/training-guides/associate-guide/bk001-ch003-associate-controller-node.xml:82(link) ./doc/training-guides/developer-guide/bk003-ch001-developer-getting-started.xml:25(link) ./doc/training-guides/developer-guide/bk003-ch001-developer-getting-started.xml:32(link) ./doc/training-guides/developer-guide/bk003-ch001-developer-getting-started.xml:39(link) ./doc/training-guides/developer-guide/bk003-ch001-developer-getting-started.xml:46(link) ./doc/training-guides/developer-guide/bk003-ch001-developer-getting-started.xml:53(link) ./doc/training-guides/developer-guide/bk003-ch002-developer-getting-started-lab.xml:15(link) ./doc/training-guides/developer-guide/bk003-ch002-developer-getting-started-lab.xml:22(link) ./doc/training-guides/developer-guide/bk003-ch002-developer-getting-started-lab.xml:29(link) ./doc/training-guides/developer-guide/bk003-ch002-developer-getting-started-lab.xml:36(link) ./doc/training-guides/developer-guide/bk003-ch002-developer-getting-started-lab.xml:43(link) msgid "https://docs.google.com/drawings/d/1J2LZSxmc06xKyxMgPjv5fC0blV7qK6956-AeTmFOZD4/edit?usp=sharing" msgstr "" @@ -535,7 +535,7 @@ msgstr "" msgid "Day 1, 09:00 to 11:00, 11:15 to 12:30" msgstr "" -#: ./doc/training-guides/operator-guide/bk002-ch001-operator-getting-started.xml:12(title) ./doc/training-guides/associate-guide/bk001-ch001-associate-getting-started.xml:12(title) ./doc/training-guides/developer-guide/bk003-ch001-developer-getting-started.xml:12(title) ./doc/training-guides/developer-guide/bk003-ch023-developer-how-to-participate-bootcamp.xml:12(title) ./doc/training-guides/common/module001-ch006-overview-horizon-cli.xml:33(guilabel) ./doc/training-guides/common/module001-ch006-overview-horizon-cli.xml:119(emphasis) ./doc/training-guides/common/module001-ch006-overview-horizon-cli.xml:835(guilabel) +#: ./doc/training-guides/operator-guide/bk002-ch001-operator-getting-started.xml:12(title) ./doc/training-guides/associate-guide/bk001-ch001-associate-getting-started.xml:12(title) ./doc/training-guides/basic-install-guide/ch_overview.xml:10(title) ./doc/training-guides/developer-guide/bk003-ch001-developer-getting-started.xml:12(title) ./doc/training-guides/developer-guide/bk003-ch023-developer-how-to-participate-bootcamp.xml:12(title) ./doc/training-guides/common/module001-ch006-overview-horizon-cli.xml:33(guilabel) ./doc/training-guides/common/module001-ch006-overview-horizon-cli.xml:119(emphasis) ./doc/training-guides/common/module001-ch006-overview-horizon-cli.xml:835(guilabel) msgid "Overview" msgstr "" @@ -543,7 +543,7 @@ msgstr "" msgid "Training would take 2.5 months self paced, (5) 2 week periods with a user group meeting, or 40 hours instructor led with 40 hours of self paced lab time." msgstr "" -#: ./doc/training-guides/operator-guide/bk002-ch001-operator-getting-started.xml:15(para) ./doc/training-guides/associate-guide/bk001-ch001-associate-getting-started.xml:15(para) ./doc/training-guides/developer-guide/bk003-ch001-developer-getting-started.xml:15(para) ./doc/training-guides/developer-guide/bk003-ch023-developer-how-to-participate-bootcamp.xml:14(para) +#: ./doc/training-guides/operator-guide/bk002-ch001-operator-getting-started.xml:15(para) ./doc/training-guides/associate-guide/bk001-ch001-associate-getting-started.xml:15(para) ./doc/training-guides/basic-install-guide/section_neutron-ovs-compute-node.xml:29(title) ./doc/training-guides/basic-install-guide/section_trove-install.xml:11(title) ./doc/training-guides/basic-install-guide/section_neutron-ml2-controller-node.xml:9(title) ./doc/training-guides/basic-install-guide/section_neutron-ovs-controller-node.xml:25(title) ./doc/training-guides/developer-guide/bk003-ch001-developer-getting-started.xml:15(para) ./doc/training-guides/developer-guide/bk003-ch023-developer-how-to-participate-bootcamp.xml:14(para) msgid "Prerequisites" msgstr "" @@ -629,7 +629,7 @@ msgstr "" #. When image changes, this message will be marked fuzzy or untranslated for you. #. It doesn't matter what you translate it to: it's not used at all. -#: ./doc/training-guides/associate-guide/bk001-ch005-associate-compute-node.xml:17(None) ./doc/training-guides/associate-guide/bk001-ch005-associate-compute-node.xml:24(None) ./doc/training-guides/associate-guide/bk001-ch005-associate-compute-node.xml:31(None) ./doc/training-guides/associate-guide/bk001-ch005-associate-compute-node.xml:40(None) ./doc/training-guides/associate-guide/bk001-ch005-associate-compute-node.xml:47(None) ./doc/training-guides/associate-guide/bk001-ch005-associate-compute-node.xml:54(None) ./doc/training-guides/associate-guide/bk001-ch005-associate-compute-node.xml:61(None) ./doc/training-guides/associate-guide/bk001-ch005-associate-compute-node.xml:68(None) ./doc/training-guides/associate-guide/bk001-ch005-associate-compute-node.xml:75(None) ./doc/training-guides/associate-guide/bk001-ch007-associate-network-node.xml:17(None) ./doc/training-guides/associate-guide/bk001-ch007-associate-network-node.xml:24(None) ./doc/training-guides/associate-guide/bk001-ch007-associate-network-node.xml:33(None) ./doc/training-guides/associate-guide/bk001-ch007-associate-network-node.xml:40(None) ./doc/training-guides/associate-guide/bk001-ch001-associate-getting-started.xml:27(None) ./doc/training-guides/associate-guide/bk001-ch001-associate-getting-started.xml:34(None) ./doc/training-guides/associate-guide/bk001-ch001-associate-getting-started.xml:41(None) ./doc/training-guides/associate-guide/bk001-ch001-associate-getting-started.xml:48(None) ./doc/training-guides/associate-guide/bk001-ch001-associate-getting-started.xml:55(None) ./doc/training-guides/associate-guide/bk001-ch009-associate-object-storage-node.xml:17(None) ./doc/training-guides/associate-guide/bk001-ch009-associate-object-storage-node.xml:24(None) ./doc/training-guides/associate-guide/bk001-ch009-associate-object-storage-node.xml:33(None) ./doc/training-guides/associate-guide/bk001-ch003-associate-controller-node.xml:17(None) ./doc/training-guides/associate-guide/bk001-ch003-associate-controller-node.xml:24(None) ./doc/training-guides/associate-guide/bk001-ch003-associate-controller-node.xml:31(None) ./doc/training-guides/associate-guide/bk001-ch003-associate-controller-node.xml:40(None) ./doc/training-guides/associate-guide/bk001-ch003-associate-controller-node.xml:47(None) ./doc/training-guides/associate-guide/bk001-ch003-associate-controller-node.xml:54(None) ./doc/training-guides/associate-guide/bk001-ch003-associate-controller-node.xml:61(None) ./doc/training-guides/associate-guide/bk001-ch003-associate-controller-node.xml:68(None) ./doc/training-guides/associate-guide/bk001-ch003-associate-controller-node.xml:75(None) ./doc/training-guides/associate-guide/bk001-ch003-associate-controller-node.xml:82(None) +#: ./doc/training-guides/associate-guide/bk001-ch005-associate-compute-node.xml:17(None) ./doc/training-guides/associate-guide/bk001-ch005-associate-compute-node.xml:24(None) ./doc/training-guides/associate-guide/bk001-ch005-associate-compute-node.xml:31(None) ./doc/training-guides/associate-guide/bk001-ch005-associate-compute-node.xml:40(None) ./doc/training-guides/associate-guide/bk001-ch005-associate-compute-node.xml:47(None) ./doc/training-guides/associate-guide/bk001-ch005-associate-compute-node.xml:54(None) ./doc/training-guides/associate-guide/bk001-ch005-associate-compute-node.xml:61(None) ./doc/training-guides/associate-guide/bk001-ch005-associate-compute-node.xml:68(None) ./doc/training-guides/associate-guide/bk001-ch005-associate-compute-node.xml:75(None) ./doc/training-guides/associate-guide/bk001-ch001-associate-getting-started.xml:27(None) ./doc/training-guides/associate-guide/bk001-ch001-associate-getting-started.xml:34(None) ./doc/training-guides/associate-guide/bk001-ch001-associate-getting-started.xml:41(None) ./doc/training-guides/associate-guide/bk001-ch001-associate-getting-started.xml:48(None) ./doc/training-guides/associate-guide/bk001-ch001-associate-getting-started.xml:55(None) ./doc/training-guides/associate-guide/bk001-ch009-associate-object-storage-node.xml:17(None) ./doc/training-guides/associate-guide/bk001-ch009-associate-object-storage-node.xml:24(None) ./doc/training-guides/associate-guide/bk001-ch009-associate-object-storage-node.xml:33(None) ./doc/training-guides/associate-guide/bk001-ch003-associate-controller-node.xml:17(None) ./doc/training-guides/associate-guide/bk001-ch003-associate-controller-node.xml:24(None) ./doc/training-guides/associate-guide/bk001-ch003-associate-controller-node.xml:31(None) ./doc/training-guides/associate-guide/bk001-ch003-associate-controller-node.xml:40(None) ./doc/training-guides/associate-guide/bk001-ch003-associate-controller-node.xml:47(None) ./doc/training-guides/associate-guide/bk001-ch003-associate-controller-node.xml:54(None) ./doc/training-guides/associate-guide/bk001-ch003-associate-controller-node.xml:61(None) ./doc/training-guides/associate-guide/bk001-ch003-associate-controller-node.xml:68(None) ./doc/training-guides/associate-guide/bk001-ch003-associate-controller-node.xml:75(None) ./doc/training-guides/associate-guide/bk001-ch003-associate-controller-node.xml:82(None) msgid "@@image: 'figures/openstack-training-remote-content-not-available.png'; md5=THIS FILE DOESN'T EXIST" msgstr "" @@ -649,7 +649,7 @@ msgstr "" msgid "OpenStack Block Storage" msgstr "" -#: ./doc/training-guides/associate-guide/bk001-ch005-associate-compute-node.xml:35(title) ./doc/training-guides/associate-guide/bk001-ch007-associate-network-node.xml:28(title) ./doc/training-guides/associate-guide/bk001-ch009-associate-object-storage-node.xml:28(title) ./doc/training-guides/associate-guide/bk001-ch003-associate-controller-node.xml:35(title) +#: ./doc/training-guides/associate-guide/bk001-ch005-associate-compute-node.xml:35(title) ./doc/training-guides/associate-guide/bk001-ch007-associate-network-node.xml:26(title) ./doc/training-guides/associate-guide/bk001-ch009-associate-object-storage-node.xml:28(title) ./doc/training-guides/associate-guide/bk001-ch003-associate-controller-node.xml:35(title) msgid "Administration Tasks" msgstr "" @@ -685,15 +685,15 @@ msgstr "" msgid "Networking in OpenStack" msgstr "" -#: ./doc/training-guides/associate-guide/bk001-ch007-associate-network-node.xml:21(title) ./doc/training-guides/common/module002-ch002-openstack-networking-concepts.xml:7(title) +#: ./doc/training-guides/associate-guide/bk001-ch007-associate-network-node.xml:20(title) ./doc/training-guides/common/module002-ch002-openstack-networking-concepts.xml:7(title) msgid "OpenStack Networking Concepts" msgstr "" -#: ./doc/training-guides/associate-guide/bk001-ch007-associate-network-node.xml:30(title) +#: ./doc/training-guides/associate-guide/bk001-ch007-associate-network-node.xml:28(title) msgid "Network CLI Commands" msgstr "" -#: ./doc/training-guides/associate-guide/bk001-ch007-associate-network-node.xml:37(title) +#: ./doc/training-guides/associate-guide/bk001-ch007-associate-network-node.xml:34(title) msgid "Manage Networks" msgstr "" @@ -941,11 +941,11 @@ msgstr "" msgid "The AMQP supports the following messaging bus options: (choose all that apply)" msgstr "" -#: ./doc/training-guides/associate-guide/bk001-ch004-associate-controller-node-quiz.xml:277(para) +#: ./doc/training-guides/associate-guide/bk001-ch004-associate-controller-node-quiz.xml:277(para) ./doc/training-guides/basic-install-guide/section_basics-queue.xml:27(link) msgid "ZeroMQ" msgstr "" -#: ./doc/training-guides/associate-guide/bk001-ch004-associate-controller-node-quiz.xml:280(para) ./doc/training-guides/basic-install-guide/lab001-control-node.xml:146(emphasis) ./doc/training-guides/common/module001-ch008-queues-messaging.xml:146(title) ./doc/training-guides/common/module001-ch008-queues-messaging.xml:181(title) ./doc/training-guides/common/module001-ch008-queues-messaging.xml:204(title) +#: ./doc/training-guides/associate-guide/bk001-ch004-associate-controller-node-quiz.xml:280(para) ./doc/training-guides/basic-install-guide/lab001-control-node.xml:146(emphasis) ./doc/training-guides/basic-install-guide/section_basics-queue.xml:21(link) ./doc/training-guides/common/module001-ch008-queues-messaging.xml:146(title) ./doc/training-guides/common/module001-ch008-queues-messaging.xml:181(title) ./doc/training-guides/common/module001-ch008-queues-messaging.xml:204(title) msgid "RabbitMQ" msgstr "" @@ -957,7 +957,7 @@ msgstr "" msgid "IBM WebSphere Message Broker" msgstr "" -#: ./doc/training-guides/associate-guide/bk001-ch004-associate-controller-node-quiz.xml:289(para) +#: ./doc/training-guides/associate-guide/bk001-ch004-associate-controller-node-quiz.xml:289(para) ./doc/training-guides/basic-install-guide/section_basics-queue.xml:24(link) msgid "Qpid" msgstr "" @@ -1201,7 +1201,7 @@ msgstr "" msgid "Day 2, 11:30 to 12:30, 13:30 to 14:45" msgstr "" -#: ./doc/training-guides/associate-guide/bk001-ch009-associate-object-storage-node.xml:14(title) +#: ./doc/training-guides/associate-guide/bk001-ch009-associate-object-storage-node.xml:14(title) ./doc/training-guides/basic-install-guide/common/section_objectstorage-intro.xml:7(title) msgid "Introduction to Object Storage" msgstr "" @@ -1305,6 +1305,796 @@ msgstr "" msgid "Message Queue Configuration" msgstr "" +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/training-guides/basic-install-guide/section_keystone-install.xml:115(None) +msgid "@@image: 'figures/debconf-screenshots/keystone_1_admin_token.png'; md5=29a51caaf09c3d6e3f0fda73c256a17a" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/training-guides/basic-install-guide/section_keystone-install.xml:131(None) +msgid "@@image: 'figures/debconf-screenshots/keystone_2_register_admin_tenant_yes_no.png'; md5=25c9a90b1df2d979aae6ce9975c7285b" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/training-guides/basic-install-guide/section_keystone-install.xml:140(None) +msgid "@@image: 'figures/debconf-screenshots/keystone_3_admin_user_name.png'; md5=173cf7ed13252df1425109be588b2ad6" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/training-guides/basic-install-guide/section_keystone-install.xml:149(None) +msgid "@@image: 'figures/debconf-screenshots/keystone_4_admin_user_email.png'; md5=b7f0d34350ccc0aa9ae4e766b7ac80c1" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/training-guides/basic-install-guide/section_keystone-install.xml:158(None) +msgid "@@image: 'figures/debconf-screenshots/keystone_5_admin_user_pass.png'; md5=e6b32d8d80af90f07a66abc8fb256c84" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/training-guides/basic-install-guide/section_keystone-install.xml:167(None) +msgid "@@image: 'figures/debconf-screenshots/keystone_6_admin_user_pass_confirm.png'; md5=1fbf9223e4923c93030d53278d1771cc" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/training-guides/basic-install-guide/section_keystone-install.xml:179(None) +msgid "@@image: 'figures/debconf-screenshots/keystone_7_register_endpoint.png'; md5=d24d84133bfee936267e79631a2666e6" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_keystone-install.xml:7(title) ./doc/training-guides/basic-install-guide/section_glance-install.xml:7(title) +msgid "Install and configure" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_keystone-install.xml:8(para) +msgid "This section describes how to install and configure the OpenStack Identity service on the controller node." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_keystone-install.xml:11(title) ./doc/training-guides/basic-install-guide/section_keystone-install.xml:36(title) ./doc/training-guides/basic-install-guide/section_keystone-users.xml:28(title) ./doc/training-guides/basic-install-guide/section_nova-controller-install.xml:11(title) ./doc/training-guides/basic-install-guide/section_glance-install.xml:18(title) ./doc/training-guides/basic-install-guide/section_heat-install.xml:11(title) ./doc/training-guides/basic-install-guide/section_keystone-services.xml:13(title) +msgid "To configure prerequisites" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_keystone-install.xml:12(para) +msgid "Before you configure the OpenStack Identity service, you must create a database and an administration token." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_keystone-install.xml:15(para) +msgid "As the root user, connect to the database to create the keystone database and grant the proper access to it:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_keystone-install.xml:21(replaceable) ./doc/training-guides/basic-install-guide/section_keystone-install.xml:23(replaceable) ./doc/training-guides/basic-install-guide/section_keystone-install.xml:69(replaceable) +msgid "KEYSTONE_DBPASS" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_keystone-install.xml:25(para) +msgid "Replace KEYSTONE_DBPASS with a suitable password." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_keystone-install.xml:29(para) ./doc/training-guides/basic-install-guide/section_keystone-install.xml:38(para) +msgid "Generate a random value to use as the administration token during initial configuration:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_keystone-install.xml:44(title) ./doc/training-guides/basic-install-guide/section_keystone-install.xml:98(title) +msgid "To install and configure the components" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_keystone-install.xml:46(para) ./doc/training-guides/basic-install-guide/section_keystone-install.xml:100(para) +msgid "Run the following command to install the packages:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_keystone-install.xml:52(para) +msgid "Edit the /etc/keystone/keystone.conf file." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_keystone-install.xml:56(para) +msgid "In the [DEFAULT] section, define the value of the initial administration token:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_keystone-install.xml:60(replaceable) ./doc/training-guides/basic-install-guide/section_keystone-users.xml:31(replaceable) ./doc/training-guides/basic-install-guide/section_trove-install.xml:131(replaceable) +msgid "ADMIN_TOKEN" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_keystone-install.xml:61(para) +msgid "Replace ADMIN_TOKEN with the random value that you generated in a previous step." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_keystone-install.xml:65(para) ./doc/training-guides/basic-install-guide/section_nova-controller-install.xml:95(para) ./doc/training-guides/basic-install-guide/section_glance-install.xml:97(para) ./doc/training-guides/basic-install-guide/section_glance-install.xml:145(para) ./doc/training-guides/basic-install-guide/section_nova-compute-install.xml:34(para) ./doc/training-guides/basic-install-guide/section_heat-install.xml:85(para) +msgid "In the [database] section, configure database access:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_keystone-install.xml:69(replaceable) ./doc/training-guides/basic-install-guide/section_cinder-controller.xml:51(replaceable) ./doc/training-guides/basic-install-guide/section_cinder-controller.xml:54(replaceable) ./doc/training-guides/basic-install-guide/section_cinder-controller.xml:90(replaceable) ./doc/training-guides/basic-install-guide/section_cinder-controller.xml:92(replaceable) ./doc/training-guides/basic-install-guide/section_cinder-controller.xml:108(replaceable) ./doc/training-guides/basic-install-guide/section_cinder-controller.xml:109(replaceable) ./doc/training-guides/basic-install-guide/section_cinder-controller.xml:127(replaceable) ./doc/training-guides/basic-install-guide/section_cinder-controller.xml:152(replaceable) ./doc/training-guides/basic-install-guide/section_cinder-controller.xml:153(replaceable) ./doc/training-guides/basic-install-guide/section_cinder-controller.xml:154(replaceable) ./doc/training-guides/basic-install-guide/section_cinder-controller.xml:162(replaceable) ./doc/training-guides/basic-install-guide/section_cinder-controller.xml:163(replaceable) ./doc/training-guides/basic-install-guide/section_cinder-controller.xml:164(replaceable) ./doc/training-guides/basic-install-guide/section_keystone-users.xml:39(replaceable) ./doc/training-guides/basic-install-guide/section_ceilometer-nova.xml:80(replaceable) ./doc/training-guides/basic-install-guide/section_ceilometer-nova.xml:87(replaceable) ./doc/training-guides/basic-install-guide/section_ceilometer-nova.xml:103(replaceable) ./doc/training-guides/basic-install-guide/section_ceilometer-nova.xml:118(replaceable) ./doc/training-guides/basic-install-guide/section_basics-networking-neutron.xml:279(replaceable) ./doc/training-guides/basic-install-guide/section_basics-networking-neutron.xml:323(replaceable) ./doc/training-guides/basic-install-guide/section_neutron-ovs-compute-node.xml:136(replaceable) ./doc/training-guides/basic-install-guide/section_neutron-ovs-compute-node.xml:138(replaceable) ./doc/training-guides/basic-install-guide/section_neutron-ovs-compute-node.xml:172(replaceable) ./doc/training-guides/basic-install-guide/section_neutron-ovs-compute-node.xml:173(replaceable) ./doc/training-guides/basic-install-guide/section_neutron-ovs-compute-node.xml:187(replaceable) ./doc/training-guides/basic-install-guide/section_neutron-ovs-compute-node.xml:198(replaceable) ./doc/training-guides/basic-install-guide/section_neutron-ovs-compute-node.xml:212(replaceable) ./doc/training-guides/basic-install-guide/section_neutron-ovs-compute-node.xml:222(replaceable) ./doc/training-guides/basic-install-guide/section_neutron-ovs-compute-node.xml:233(replaceable) ./doc/training-guides/basic-install-guide/section_neutron-ovs-compute-node.xml:238(replaceable) ./doc/training-guides/basic-install-guide/section_ceilometer-install.xml:103(replaceable) ./doc/training-guides/basic-install-guide/section_ceilometer-install.xml:112(replaceable) ./doc/training-guides/basic-install-guide/section_ceilometer-install.xml:119(replaceable) ./doc/training-guides/basic-install-guide/section_ceilometer-install.xml:146(replaceable) ./doc/training-guides/basic-install-guide/section_ceilometer-install.xml:149(replaceable) ./doc/training-guides/basic-install-guide/section_ceilometer-install.xml:191(replaceable) ./doc/training-guides/basic-install-guide/section_ceilometer-install.xml:199(replaceable) ./doc/training-guides/basic-install-guide/section_ceilometer-install.xml:203(replaceable) ./doc/training-guides/basic-install-guide/section_ceilometer-install.xml:218(replaceable) ./doc/training-guides/basic-install-guide/section_ceilometer-install.xml:225(replaceable) ./doc/training-guides/basic-install-guide/section_ceilometer-install.xml:239(replaceable) ./doc/training-guides/basic-install-guide/section_ceilometer-install.xml:240(replaceable) ./doc/training-guides/basic-install-guide/section_ceilometer-install.xml:241(replaceable) ./doc/training-guides/basic-install-guide/section_basics-ntp.xml:74(replaceable) ./doc/training-guides/basic-install-guide/ch_clients.xml:43(replaceable) ./doc/training-guides/basic-install-guide/section_nova-controller-install.xml:72(replaceable) ./doc/training-guides/basic-install-guide/section_nova-controller-install.xml:73(replaceable) ./doc/training-guides/basic-install-guide/section_nova-controller-install.xml:74(replaceable) ./doc/training-guides/basic-install-guide/section_nova-controller-install.xml:109(replaceable) ./doc/training-guides/basic-install-guide/section_nova-controller-install.xml:121(replaceable) ./doc/training-guides/basic-install-guide/section_nova-controller-install.xml:122(replaceable) ./doc/training-guides/basic-install-guide/section_nova-controller-install.xml:154(replaceable) ./doc/training-guides/basic-install-guide/section_glance-install.xml:79(replaceable) ./doc/training-guides/basic-install-guide/section_glance-install.xml:80(replaceable) ./doc/training-guides/basic-install-guide/section_glance-install.xml:81(replaceable) ./doc/training-guides/basic-install-guide/section_glance-install.xml:101(replaceable) ./doc/training-guides/basic-install-guide/section_glance-install.xml:111(replaceable) ./doc/training-guides/basic-install-guide/section_glance-install.xml:123(replaceable) ./doc/training-guides/basic-install-guide/section_glance-install.xml:124(replaceable) ./doc/training-guides/basic-install-guide/section_glance-install.xml:149(replaceable) ./doc/training-guides/basic-install-guide/section_glance-install.xml:159(replaceable) ./doc/training-guides/basic-install-guide/section_glance-install.xml:160(replaceable) ./doc/training-guides/basic-install-guide/section_cinder-node.xml:115(replaceable) ./doc/training-guides/basic-install-guide/section_cinder-node.xml:117(replaceable) ./doc/training-guides/basic-install-guide/section_cinder-node.xml:133(replaceable) ./doc/training-guides/basic-install-guide/section_cinder-node.xml:134(replaceable) ./doc/training-guides/basic-install-guide/section_cinder-node.xml:152(replaceable) ./doc/training-guides/basic-install-guide/section_cinder-node.xml:164(replaceable) ./doc/training-guides/basic-install-guide/section_cinder-node.xml:177(replaceable) ./doc/training-guides/basic-install-guide/section_cinder-node.xml:180(replaceable) ./doc/training-guides/basic-install-guide/section_cinder-node.xml:196(replaceable) ./doc/training-guides/basic-install-guide/section_cinder-node.xml:199(replaceable) ./doc/training-guides/basic-install-guide/section_neutron-ml2-compute-node.xml:60(replaceable) ./doc/training-guides/basic-install-guide/section_neutron-ml2-compute-node.xml:62(replaceable) ./doc/training-guides/basic-install-guide/section_neutron-ml2-compute-node.xml:93(replaceable) ./doc/training-guides/basic-install-guide/section_neutron-ml2-compute-node.xml:94(replaceable) ./doc/training-guides/basic-install-guide/section_neutron-ml2-compute-node.xml:111(replaceable) ./doc/training-guides/basic-install-guide/section_neutron-ml2-compute-node.xml:134(replaceable) ./doc/training-guides/basic-install-guide/section_neutron-ml2-compute-node.xml:280(replaceable) ./doc/training-guides/basic-install-guide/section_neutron-ml2-compute-node.xml:290(replaceable) ./doc/training-guides/basic-install-guide/section_neutron-ml2-compute-node.xml:318(replaceable) ./doc/training-guides/basic-install-guide/section_neutron-ml2-compute-node.xml:323(replaceable) ./doc/training-guides/basic-install-guide/section_basics-networking-nova.xml:204(replaceable) ./doc/training-guides/basic-install-guide/section_trove-install.xml:78(replaceable) ./doc/training-guides/basic-install-guide/section_trove-install.xml:79(replaceable) ./doc/training-guides/basic-install-guide/section_trove-install.xml:80(replaceable) ./doc/training-guides/basic-install-guide/section_trove-install.xml:81(replaceable) ./doc/training-guides/basic-install-guide/section_trove-install.xml:82(replaceable) ./doc/training-guides/basic-install-guide/section_trove-install.xml:83(replaceable) ./doc/training-guides/basic-install-guide/section_trove-install.xml:106(replaceable) ./doc/training-guides/basic-install-guide/section_trove-install.xml:108(replaceable) ./doc/training-guides/basic-install-guide/section_trove-install.xml:110(replaceable) ./doc/training-guides/basic-install-guide/section_trove-install.xml:126(replaceable) ./doc/training-guides/basic-install-guide/section_trove-install.xml:207(replaceable) ./doc/training-guides/basic-install-guide/section_trove-install.xml:212(replaceable) ./doc/training-guides/basic-install-guide/section_trove-install.xml:233(replaceable) ./doc/training-guides/basic-install-guide/section_trove-install.xml:234(replaceable) ./doc/training-guides/basic-install-guide/section_trove-install.xml:235(replaceable) ./doc/training-guides/basic-install-guide/section_neutron-ml2-controller-node.xml:50(replaceable) ./doc/training-guides/basic-install-guide/section_neutron-ml2-controller-node.xml:51(replaceable) ./doc/training-guides/basic-install-guide/section_neutron-ml2-controller-node.xml:52(replaceable) ./doc/training-guides/basic-install-guide/section_neutron-ml2-controller-node.xml:114(replaceable) ./doc/training-guides/basic-install-guide/section_neutron-ml2-controller-node.xml:127(replaceable) ./doc/training-guides/basic-install-guide/section_neutron-ml2-controller-node.xml:140(replaceable) ./doc/training-guides/basic-install-guide/section_neutron-ml2-controller-node.xml:142(replaceable) ./doc/training-guides/basic-install-guide/section_neutron-ml2-controller-node.xml:172(replaceable) ./doc/training-guides/basic-install-guide/section_neutron-ml2-controller-node.xml:173(replaceable) ./doc/training-guides/basic-install-guide/section_neutron-ml2-controller-node.xml:209(replaceable) ./doc/training-guides/basic-install-guide/section_neutron-ml2-controller-node.xml:222(replaceable) ./doc/training-guides/basic-install-guide/section_neutron-ml2-controller-node.xml:230(replaceable) ./doc/training-guides/basic-install-guide/section_neutron-ml2-controller-node.xml:249(replaceable) ./doc/training-guides/basic-install-guide/section_neutron-ml2-controller-node.xml:253(replaceable) ./doc/training-guides/basic-install-guide/section_neutron-ml2-controller-node.xml:366(replaceable) ./doc/training-guides/basic-install-guide/section_neutron-ml2-controller-node.xml:376(replaceable) ./doc/training-guides/basic-install-guide/section_neutron-ml2-controller-node.xml:400(replaceable) ./doc/training-guides/basic-install-guide/section_neutron-ml2-controller-node.xml:405(replaceable) ./doc/training-guides/basic-install-guide/section_nova-compute-install.xml:38(replaceable) ./doc/training-guides/basic-install-guide/section_nova-compute-install.xml:48(replaceable) ./doc/training-guides/basic-install-guide/section_nova-compute-install.xml:60(replaceable) ./doc/training-guides/basic-install-guide/section_nova-compute-install.xml:61(replaceable) ./doc/training-guides/basic-install-guide/section_nova-compute-install.xml:92(replaceable) ./doc/training-guides/basic-install-guide/section_nova-compute-install.xml:117(replaceable) ./doc/training-guides/basic-install-guide/section_neutron-ovs-controller-node.xml:56(replaceable) ./doc/training-guides/basic-install-guide/section_neutron-ovs-controller-node.xml:57(replaceable) ./doc/training-guides/basic-install-guide/section_neutron-ovs-controller-node.xml:58(replaceable) ./doc/training-guides/basic-install-guide/section_neutron-ovs-controller-node.xml:82(replaceable) ./doc/training-guides/basic-install-guide/section_neutron-ovs-controller-node.xml:99(replaceable) ./doc/training-guides/basic-install-guide/section_neutron-ovs-controller-node.xml:101(replaceable) ./doc/training-guides/basic-install-guide/section_neutron-ovs-controller-node.xml:134(replaceable) ./doc/training-guides/basic-install-guide/section_neutron-ovs-controller-node.xml:135(replaceable) ./doc/training-guides/basic-install-guide/section_neutron-ovs-controller-node.xml:166(replaceable) ./doc/training-guides/basic-install-guide/section_neutron-ovs-controller-node.xml:216(replaceable) ./doc/training-guides/basic-install-guide/section_neutron-ovs-controller-node.xml:226(replaceable) ./doc/training-guides/basic-install-guide/section_neutron-ovs-controller-node.xml:237(replaceable) ./doc/training-guides/basic-install-guide/section_neutron-ovs-controller-node.xml:242(replaceable) ./doc/training-guides/basic-install-guide/section_heat-install.xml:63(replaceable) ./doc/training-guides/basic-install-guide/section_heat-install.xml:64(replaceable) ./doc/training-guides/basic-install-guide/section_heat-install.xml:65(replaceable) ./doc/training-guides/basic-install-guide/section_heat-install.xml:68(replaceable) ./doc/training-guides/basic-install-guide/section_heat-install.xml:69(replaceable) ./doc/training-guides/basic-install-guide/section_heat-install.xml:70(replaceable) ./doc/training-guides/basic-install-guide/section_heat-install.xml:89(replaceable) ./doc/training-guides/basic-install-guide/section_heat-install.xml:99(replaceable) ./doc/training-guides/basic-install-guide/section_heat-install.xml:111(replaceable) ./doc/training-guides/basic-install-guide/section_heat-install.xml:112(replaceable) ./doc/training-guides/basic-install-guide/section_heat-install.xml:121(replaceable) ./doc/training-guides/basic-install-guide/section_heat-install.xml:131(replaceable) ./doc/training-guides/basic-install-guide/section_heat-install.xml:132(replaceable) ./doc/training-guides/basic-install-guide/section_heat-install.xml:177(replaceable) ./doc/training-guides/basic-install-guide/section_neutron-ml2-network-node.xml:66(replaceable) ./doc/training-guides/basic-install-guide/section_neutron-ml2-network-node.xml:68(replaceable) ./doc/training-guides/basic-install-guide/section_neutron-ml2-network-node.xml:99(replaceable) ./doc/training-guides/basic-install-guide/section_neutron-ml2-network-node.xml:100(replaceable) ./doc/training-guides/basic-install-guide/section_neutron-ml2-network-node.xml:117(replaceable) ./doc/training-guides/basic-install-guide/section_neutron-ml2-network-node.xml:137(replaceable) ./doc/training-guides/basic-install-guide/section_neutron-ml2-network-node.xml:264(replaceable) ./doc/training-guides/basic-install-guide/section_neutron-ml2-network-node.xml:274(replaceable) ./doc/training-guides/basic-install-guide/section_neutron-ml2-network-node.xml:296(replaceable) ./doc/training-guides/basic-install-guide/section_neutron-ml2-network-node.xml:301(replaceable) ./doc/training-guides/basic-install-guide/section_ceilometer-glance.xml:18(replaceable) ./doc/training-guides/basic-install-guide/section_ceilometer-glance.xml:24(replaceable) ./doc/training-guides/basic-install-guide/section_keystone-services.xml:55(replaceable) ./doc/training-guides/basic-install-guide/section_keystone-services.xml:56(replaceable) ./doc/training-guides/basic-install-guide/section_keystone-services.xml:57(replaceable) ./doc/training-guides/basic-install-guide/section_neutron-ovs-network-node.xml:98(replaceable) ./doc/training-guides/basic-install-guide/section_neutron-ovs-network-node.xml:100(replaceable) ./doc/training-guides/basic-install-guide/section_neutron-ovs-network-node.xml:131(replaceable) ./doc/training-guides/basic-install-guide/section_neutron-ovs-network-node.xml:132(replaceable) ./doc/training-guides/basic-install-guide/section_neutron-ovs-network-node.xml:146(replaceable) ./doc/training-guides/basic-install-guide/section_neutron-ovs-network-node.xml:157(replaceable) ./doc/training-guides/basic-install-guide/section_neutron-ovs-network-node.xml:374(replaceable) ./doc/training-guides/basic-install-guide/section_neutron-ovs-network-node.xml:379(replaceable) ./doc/training-guides/basic-install-guide/section_neutron-ovs-network-node.xml:384(replaceable) ./doc/training-guides/basic-install-guide/section_neutron-ovs-network-node.xml:394(replaceable) ./doc/training-guides/basic-install-guide/object-storage/section_object-storage-install-config-proxy-node.xml:80(replaceable) ./doc/training-guides/basic-install-guide/object-storage/section_object-storage-install.xml:102(replaceable) ./doc/training-guides/basic-install-guide/object-storage/section_object-storage-install.xml:103(replaceable) ./doc/training-guides/basic-install-guide/object-storage/section_object-storage-install.xml:104(replaceable) +msgid "controller" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_keystone-install.xml:70(para) +msgid "Replace KEYSTONE_DBPASS with the password you chose for the database." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_keystone-install.xml:74(para) +msgid "In the [DEFAULT] section, configure the log directory:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_keystone-install.xml:83(para) +msgid "By default, the Identity service uses public key infrastructure (PKI)." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_keystone-install.xml:85(para) +msgid "Create generic certificates and keys and restrict access to the associated files:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_keystone-install.xml:92(para) +msgid "Run the following command to populate the Identity service database:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_keystone-install.xml:104(para) +msgid "Respond to prompts for database management." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_keystone-install.xml:109(para) +msgid "Configure the initial administration token:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_keystone-install.xml:119(para) +msgid "Use the random value that you generated in a previous step. If you install using non-interactive mode or you do not specify this token, the configuration tool generates a random value." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_keystone-install.xml:124(para) +msgid "Create the admin tenant and user:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_keystone-install.xml:173(para) +msgid "Register the Identity service in the catalog:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_keystone-install.xml:186(title) ./doc/training-guides/basic-install-guide/section_nova-controller-install.xml:197(title) ./doc/training-guides/basic-install-guide/section_glance-install.xml:211(title) ./doc/training-guides/basic-install-guide/section_neutron-ml2-controller-node.xml:419(title) ./doc/training-guides/basic-install-guide/section_nova-compute-install.xml:140(title) ./doc/training-guides/basic-install-guide/section_heat-install.xml:183(title) +msgid "To finalize installation" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_keystone-install.xml:188(para) +msgid "Restart the Identity service:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_keystone-install.xml:192(para) +msgid "Start the Identity service and configure it to start when the system boots:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_keystone-install.xml:198(para) ./doc/training-guides/basic-install-guide/section_heat-install.xml:201(para) +msgid "By default, the Ubuntu packages create a SQLite database." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_keystone-install.xml:200(para) ./doc/training-guides/basic-install-guide/section_nova-controller-install.xml:225(para) ./doc/training-guides/basic-install-guide/section_glance-install.xml:227(para) ./doc/training-guides/basic-install-guide/section_nova-compute-install.xml:214(para) ./doc/training-guides/basic-install-guide/section_heat-install.xml:202(para) +msgid "Because this configuration uses a SQL database server, you can remove the SQLite database file:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_keystone-install.xml:205(para) +msgid "By default, the Identity service stores expired tokens in the database indefinitely. The accumulation of expired tokens considerably increases the database size and might degrade service performance, particularly in test environments with limited resources." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_keystone-install.xml:210(para) +msgid "We recommend that you use cron to configure a periodic task that purges expired tokens hourly." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_keystone-install.xml:213(para) +msgid "Run the following command to purge expired tokens every hour and log the output to the /var/log/keystone/keystone-tokenflush.log file:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_basics-database.xml:8(title) ./doc/training-guides/sources/cinder/unit_tests.xml:113(title) +msgid "Database" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_basics-database.xml:9(para) +msgid "Most OpenStack services require a database to store information. These examples use a MySQL database that runs on the controller node. You must install the MySQL database on the controller node. You must install the MySQL Python library on any additional nodes that access MySQL." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_basics-database.xml:15(para) +msgid "Most OpenStack services require a database to store information. This guide uses a MySQL database on SUSE Linux Enterprise Server and a compatible database on openSUSE running on the controller node. This compatible database for openSUSE is MariaDB. You must install the MariaDB database on the controller node. You must install the MySQL Python library on any additional nodes that access MySQL or MariaDB." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_basics-database.xml:24(title) +msgid "Controller setup" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_basics-database.xml:25(para) +msgid "For SUSE Linux Enterprise Server: On the controller node, install the MySQL client and server packages, and the Python library." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_basics-database.xml:29(para) +msgid "For openSUSE: On the controller node, install the MariaDB client and database server packages, and the MySQL Python library." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_basics-database.xml:36(para) +msgid "When you install the server package, you are prompted for the root password for the database. Choose a strong password and remember it." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_basics-database.xml:40(para) +msgid "The MySQL configuration requires some changes to work with OpenStack." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_basics-database.xml:44(para) +msgid "Edit the /etc/mysql/my.cnf file:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_basics-database.xml:46(para) +msgid "Edit the /etc/my.cnf file:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_basics-database.xml:50(para) +msgid "Under the [mysqld] section, set the bind-address key to the management IP address of the controller node to enable access by other nodes via the management network:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_basics-database.xml:59(para) +msgid "Under the [mysqld] section, set the following keys to enable InnoDB, UTF-8 character set, and UTF-8 collation by default:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_basics-database.xml:73(para) +msgid "Restart the MySQL service to apply the changes:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_basics-database.xml:76(para) +msgid "Start the MySQLMariaDB or MySQL database server and set it to start automatically when the system boots:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_basics-database.xml:85(para) +msgid "Finally, you should set a root password for your MySQLMariaDB or MySQL database. The OpenStack programs that set up databases and tables prompt you for this password if it is set." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_basics-database.xml:91(para) +msgid "You must delete the anonymous users that are created when the database is first started. Otherwise, database connection problems occur when you follow the instructions in this guide. To do this, use the command. Note that if fails you might need to use first:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_basics-database.xml:100(para) +msgid "If you have not already set a root database password, press ENTER when you are prompted for the password. This command presents a number of options for you to secure your database installation. Respond to all prompts unless you have a good reason to do otherwise." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_basics-database.xml:109(title) +msgid "Node setup" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_basics-database.xml:110(para) +msgid "On all nodes other than the controller node, install the MySQL Python library:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_cinder-controller.xml:7(title) +msgid "Configure a Block Storage service controller" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_cinder-controller.xml:9(para) +msgid "This scenario configures OpenStack Block Storage services on the Controller node and assumes that a second node provides storage through the cinder-volume service." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_cinder-controller.xml:14(para) +msgid "For instructions on how to configure the second node, see ." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_cinder-controller.xml:18(para) ./doc/training-guides/basic-install-guide/section_cinder-node.xml:12(para) +msgid "You can configure OpenStack to use various storage systems. This example uses LVM." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_cinder-controller.xml:22(para) +msgid "Install the appropriate packages for the Block Storage service:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_cinder-controller.xml:29(para) +msgid "Respond to the prompts for database management, [keystone_authtoken] settings, RabbitMQ credentials, and API endpoint registration." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_cinder-controller.xml:38(para) +msgid "Configure Block Storage to use your database." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_cinder-controller.xml:39(para) +msgid "Run the following command to set connection option in the [database] section, which is in the /etc/cinder/cinder.conf file, replace CINDER_DBPASS with the password for the Block Storage database that you will create in a later step:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_cinder-controller.xml:45(para) +msgid "In the /etc/cinder/cinder.conf file, set the connection option in the [database] section and replace CINDER_DBPASS with the password for the Block Storage database that you will create in a later step:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_cinder-controller.xml:51(replaceable) ./doc/training-guides/basic-install-guide/section_cinder-controller.xml:54(replaceable) ./doc/training-guides/basic-install-guide/section_cinder-controller.xml:66(replaceable) ./doc/training-guides/basic-install-guide/section_cinder-controller.xml:68(replaceable) ./doc/training-guides/basic-install-guide/section_cinder-node.xml:177(replaceable) ./doc/training-guides/basic-install-guide/section_cinder-node.xml:180(replaceable) +msgid "CINDER_DBPASS" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_cinder-controller.xml:55(para) ./doc/training-guides/basic-install-guide/section_cinder-node.xml:182(para) +msgid "In some distributions, the /etc/cinder/cinder.conf file does not include the [database] section header. You must add this section header to the end of the file before you proceed." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_cinder-controller.xml:61(para) +msgid "Use the password that you set to log in as root to create a cinder database:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_cinder-controller.xml:71(para) +msgid "Create the database tables for the Block Storage service:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_cinder-controller.xml:76(para) +msgid "Create a cinder user." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_cinder-controller.xml:77(para) +msgid "The Block Storage service uses this user to authenticate with the Identity service." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_cinder-controller.xml:79(para) +msgid "Use the service tenant and give the user the admin role:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_cinder-controller.xml:81(replaceable) ./doc/training-guides/basic-install-guide/section_cinder-controller.xml:102(replaceable) ./doc/training-guides/basic-install-guide/section_cinder-controller.xml:114(replaceable) ./doc/training-guides/basic-install-guide/section_cinder-node.xml:127(replaceable) ./doc/training-guides/basic-install-guide/section_cinder-node.xml:139(replaceable) +msgid "CINDER_PASS" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_cinder-controller.xml:81(replaceable) +msgid "cinder@example.com" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_cinder-controller.xml:85(para) +msgid "Edit the /etc/cinder/cinder.conf configuration file:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_cinder-controller.xml:103(para) ./doc/training-guides/basic-install-guide/section_cinder-node.xml:128(para) +msgid "Edit the /etc/cinder/cinder.conf configuration file and add this section for keystone credentials:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_cinder-controller.xml:117(para) ./doc/training-guides/basic-install-guide/section_cinder-controller.xml:133(para) ./doc/training-guides/basic-install-guide/section_cinder-node.xml:142(para) +msgid "Configure Block Storage to use the RabbitMQ message broker." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_cinder-controller.xml:119(para) +msgid "In the [DEFAULT] section in the /etc/cinder/cinder.conf file, set these configuration keys and replace RABBIT_PASS with the password you chose for RabbitMQ:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_cinder-controller.xml:130(replaceable) ./doc/training-guides/basic-install-guide/section_cinder-controller.xml:144(replaceable) ./doc/training-guides/basic-install-guide/section_ceilometer-nova.xml:77(replaceable) ./doc/training-guides/basic-install-guide/section_ceilometer-nova.xml:81(replaceable) ./doc/training-guides/basic-install-guide/section_neutron-ovs-compute-node.xml:191(replaceable) ./doc/training-guides/basic-install-guide/section_neutron-ovs-compute-node.xml:200(replaceable) ./doc/training-guides/basic-install-guide/section_ceilometer-install.xml:147(replaceable) ./doc/training-guides/basic-install-guide/section_ceilometer-install.xml:150(replaceable) ./doc/training-guides/basic-install-guide/section_nova-controller-install.xml:110(replaceable) ./doc/training-guides/basic-install-guide/section_glance-install.xml:112(replaceable) ./doc/training-guides/basic-install-guide/section_cinder-node.xml:155(replaceable) ./doc/training-guides/basic-install-guide/section_cinder-node.xml:168(replaceable) ./doc/training-guides/basic-install-guide/section_neutron-ml2-compute-node.xml:115(replaceable) ./doc/training-guides/basic-install-guide/section_neutron-ml2-compute-node.xml:135(replaceable) ./doc/training-guides/basic-install-guide/section_trove-install.xml:92(replaceable) ./doc/training-guides/basic-install-guide/section_trove-install.xml:112(replaceable) ./doc/training-guides/basic-install-guide/section_trove-install.xml:114(replaceable) ./doc/training-guides/basic-install-guide/section_trove-install.xml:116(replaceable) ./doc/training-guides/basic-install-guide/section_trove-install.xml:208(replaceable) ./doc/training-guides/basic-install-guide/section_neutron-ml2-controller-node.xml:194(replaceable) ./doc/training-guides/basic-install-guide/section_neutron-ml2-controller-node.xml:210(replaceable) ./doc/training-guides/basic-install-guide/section_nova-compute-install.xml:49(replaceable) ./doc/training-guides/basic-install-guide/section_neutron-ovs-controller-node.xml:154(replaceable) ./doc/training-guides/basic-install-guide/section_neutron-ovs-controller-node.xml:167(replaceable) ./doc/training-guides/basic-install-guide/section_heat-install.xml:100(replaceable) ./doc/training-guides/basic-install-guide/section_neutron-ml2-network-node.xml:121(replaceable) ./doc/training-guides/basic-install-guide/section_neutron-ml2-network-node.xml:138(replaceable) ./doc/training-guides/basic-install-guide/section_ceilometer-glance.xml:19(replaceable) ./doc/training-guides/basic-install-guide/section_ceilometer-glance.xml:25(replaceable) ./doc/training-guides/basic-install-guide/section_basics-queue.xml:58(replaceable) ./doc/training-guides/basic-install-guide/section_neutron-ovs-network-node.xml:150(replaceable) ./doc/training-guides/basic-install-guide/section_neutron-ovs-network-node.xml:159(replaceable) +msgid "RABBIT_PASS" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_cinder-controller.xml:135(para) +msgid "Replace RABBIT_PASS with the password you chose for RabbitMQ:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_cinder-controller.xml:147(para) +msgid "Register the Block Storage service with the Identity service so that other OpenStack services can locate it:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_cinder-controller.xml:157(para) +msgid "Register a service and endpoint for version 2 of the Block Storage service API:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_cinder-controller.xml:167(para) ./doc/training-guides/basic-install-guide/section_cinder-node.xml:202(para) +msgid "Restart the Block Storage services with the new settings:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_cinder-controller.xml:173(para) ./doc/training-guides/basic-install-guide/section_cinder-node.xml:215(para) +msgid "Start and configure the Block Storage services to start when the system boots:" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/training-guides/basic-install-guide/section_debconf-dbconfig-common.xml:37(None) +msgid "@@image: 'figures/debconf-screenshots/dbconfig-common_keep_admin_pass.png'; md5=01af4867c16e458306b8abd78a1fccc9" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/training-guides/basic-install-guide/section_debconf-dbconfig-common.xml:46(None) +msgid "@@image: 'figures/debconf-screenshots/dbconfig-common_used_for_remote_db.png'; md5=c6ec966bbfdee18ad87456cf4d44a56f" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/training-guides/basic-install-guide/section_debconf-dbconfig-common.xml:96(None) +msgid "@@image: 'figures/debconf-screenshots/dbconfig-common_1_configure-with-dbconfig-yes-no.png'; md5=4e9d7bce27cc6c7bd68ce8622c80b60f" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/training-guides/basic-install-guide/section_debconf-dbconfig-common.xml:105(None) +msgid "@@image: 'figures/debconf-screenshots/dbconfig-common_2_db-types.png'; md5=a77beb7e13b487cf79716c2140f258c2" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/training-guides/basic-install-guide/section_debconf-dbconfig-common.xml:114(None) +msgid "@@image: 'figures/debconf-screenshots/dbconfig-common_3_connection_method.png'; md5=6cc592e5dd5ea404ad7aad98b37a71f6" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/training-guides/basic-install-guide/section_debconf-dbconfig-common.xml:123(None) +msgid "@@image: 'figures/debconf-screenshots/dbconfig-common_4_mysql_root_password.png'; md5=873ec338742e37305583e9e692bcfdc6" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/training-guides/basic-install-guide/section_debconf-dbconfig-common.xml:132(None) +msgid "@@image: 'figures/debconf-screenshots/dbconfig-common_5_mysql_app_password.png'; md5=3651970770d05892f21d1b5741afbee6" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/training-guides/basic-install-guide/section_debconf-dbconfig-common.xml:141(None) +msgid "@@image: 'figures/debconf-screenshots/dbconfig-common_6_mysql_app_password_confirm.png'; md5=060cc90aaf6f6fd5cea718064829c1b1" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_debconf-dbconfig-common.xml:7(title) +msgid "Configure the database with dbconfig-common" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_debconf-dbconfig-common.xml:8(para) +msgid "Many of the OpenStack services need to be configured to access a database. These are configured through a DSN (Database Source Name) directive as follows:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_debconf-dbconfig-common.xml:13(para) +msgid "This connection directive will be handled by the dbconfig-common package, which provides a standard Debian interface. It enables you to configure Debian database parameters. It includes localized prompts for many languages and it supports the following database backends: SQLite, MySQL, and PostgreSQL." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_debconf-dbconfig-common.xml:19(para) +msgid "By default, the dbconfig-common package configures the OpenStack services to use SQLite. So if you use debconf in non-interactive mode and without pre-seeding, the OpenStack services that you install will use SQLite." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_debconf-dbconfig-common.xml:24(para) +msgid "By default, dbconfig-common does not provide access to database servers over a network. If you want the dbconfig-common package to prompt for remote database servers that are accessed over a network and not through a UNIX socket file, reconfigure it, as follows:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_debconf-dbconfig-common.xml:30(para) +msgid "These screens appear when you re-configure the dbconfig-common package:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_debconf-dbconfig-common.xml:50(para) +msgid "Unlike other debconf prompts, you cannot pre-seed the responses for the dbconfig-common prompts by using . Instead, you must create a file in /etc/dbconfig-common. For example, you might create a keystone configuration file for dbconfig-common that is located in /etc/dbconfig-common/keystone.conf, as follows:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_debconf-dbconfig-common.xml:73(para) +msgid "After you create this file, run this command:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_debconf-dbconfig-common.xml:75(para) +msgid "The Identity Service is installed with MySQL as the database back end, keystonedb as database name, and the localhost socket file. The corresponding DNS will then be:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_debconf-dbconfig-common.xml:80(para) +msgid "The dbconfig-common package will configure MySQL for these access rights, and create the database for you. Since OpenStack 2014.1.1, all OpenStack packages in Debian are performing the following MySQL query after database creation (if you decide to use MySQL as a back-end):" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_debconf-dbconfig-common.xml:86(para) +msgid "So, if using Debian, you wont need to care about database creation, access rights and character sets. All that is handled for you by the packages." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_debconf-dbconfig-common.xml:89(para) +msgid "As an example, here are screenshots from the cinder-common package:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_debconf-dbconfig-common.xml:145(para) +msgid "By default in Debian, you can access the MySQL server from either localhost through the socket file or 127.0.0.1. To access it over the network, you must edit the /etc/mysql/my.cnf file, and the mysql.user table. To do so, Debian provides a helper script in the openstack-deploy package. To use it, install the package and run:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_debconf-dbconfig-common.xml:152(para) +msgid "Alternatively, if you do not want to install this package, run this script to enable remote root access:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_debconf-dbconfig-common.xml:175(para) +msgid "You must enable remote access before you install OpenStack services on multiple nodes." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/ch_launch-instance.xml:7(title) +msgid "Launch an instance" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/ch_launch-instance.xml:8(para) +msgid "An instance is a VM that OpenStack provisions on a compute node. This guide shows you how to launch a minimal instance using the CirrOS image that you added to your environment in the chapter. In these steps, you use the command-line interface (CLI) on your controller node or any system with the appropriate OpenStack client libraries. To use the dashboard, see the OpenStack User Guide." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/ch_launch-instance.xml:17(para) +msgid "Launch an instance using OpenStack Networking (neutron) or legacy networking (nova-network) . For more information, see the OpenStack User Guide." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/ch_launch-instance.xml:27(para) +msgid "These steps reference example components created in previous chapters. You must adjust certain values such as IP addresses to match your environment." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_ceilometer-swift.xml:7(title) +msgid "Configure the Object Storage service for Telemetry" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_ceilometer-swift.xml:10(para) +msgid "To retrieve object store statistics, the Telemetry service needs access to Object Storage with the ResellerAdmin role. Give this role to your os_username user for the os_tenant_name tenant:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_ceilometer-swift.xml:24(replaceable) +msgid "462fa46c13fd4798a95a3bfbe27b5e54" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_ceilometer-swift.xml:27(para) +msgid "You must also add the Telemetry middleware to Object Storage to handle incoming and outgoing traffic. Add these lines to the /etc/swift/proxy-server.conf file:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_ceilometer-swift.xml:36(para) +msgid "Add ceilometer to the pipeline parameter of that same file:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_ceilometer-swift.xml:42(para) ./doc/training-guides/basic-install-guide/section_ceilometer-nova.xml:133(para) +msgid "Restart the service with its new settings:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_keystone-users.xml:8(title) +msgid "Create tenants, users, and roles" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_keystone-users.xml:9(para) +msgid "After you install the Identity service, create tenants (projects), users, and roles for your environment. You must use the temporary administration token that you created in and manually configure the location (endpoint) of the Identity service before you run commands." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_keystone-users.xml:17(para) +msgid "You can pass the value of the administration token to the command with the option or set the temporary OS_SERVICE_TOKEN environment variable. Similarly, you can pass the location of the Identity service to the command with the option or set the temporary OS_SERVICE_ENDPOINT environment variable. This guide uses environment variables to reduce command length." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_keystone-users.xml:25(para) +msgid "For more information, see the Operations Guide - Managing Project and Users." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_keystone-users.xml:30(para) +msgid "Configure the administration token:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_keystone-users.xml:32(para) +msgid "Replace ADMIN_TOKEN with the administration token that you generated in . For example:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_keystone-users.xml:38(para) +msgid "Configure the endpoint:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_keystone-users.xml:43(title) +msgid "To create tenants, users, and roles" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_keystone-users.xml:45(para) +msgid "Create an administrative tenant, user, and role for administrative operations in your environment:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_keystone-users.xml:49(para) +msgid "Create the admin tenant:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_keystone-users.xml:60(para) ./doc/training-guides/basic-install-guide/section_keystone-verify.xml:48(para) ./doc/training-guides/basic-install-guide/section_keystone-services.xml:38(para) +msgid "Because OpenStack generates IDs dynamically, you will see different values from this example command output." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_keystone-users.xml:65(para) +msgid "Create the admin user:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_keystone-users.xml:66(replaceable) ./doc/training-guides/basic-install-guide/section_keystone-verify.xml:19(replaceable) ./doc/training-guides/basic-install-guide/section_keystone-verify.xml:38(replaceable) ./doc/training-guides/basic-install-guide/section_keystone-verify.xml:60(replaceable) ./doc/training-guides/basic-install-guide/section_keystone-verify.xml:77(replaceable) ./doc/training-guides/basic-install-guide/section_trove-install.xml:130(replaceable) ./doc/training-guides/basic-install-guide/section_trove-install.xml:159(replaceable) ./doc/training-guides/basic-install-guide/section_trove-install.xml:210(replaceable) +msgid "ADMIN_PASS" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_keystone-users.xml:66(replaceable) ./doc/training-guides/basic-install-guide/section_keystone-users.xml:144(replaceable) ./doc/training-guides/basic-install-guide/section_nova-controller-install.xml:51(replaceable) ./doc/training-guides/basic-install-guide/section_glance-install.xml:57(replaceable) ./doc/training-guides/basic-install-guide/section_heat-install.xml:32(replaceable) +msgid "EMAIL_ADDRESS" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_keystone-users.xml:76(para) +msgid "Replace ADMIN_PASS with a suitable password and EMAIL_ADDRESS with a suitable e-mail address." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_keystone-users.xml:81(para) +msgid "Create the admin role:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_keystone-users.xml:91(para) +msgid "Add the admin tenant and user to the admin role:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_keystone-users.xml:95(para) ./doc/training-guides/basic-install-guide/section_keystone-users.xml:109(para) ./doc/training-guides/basic-install-guide/section_keystone-users.xml:163(para) ./doc/training-guides/basic-install-guide/section_nova-networking-initial-network.xml:44(para) ./doc/training-guides/basic-install-guide/section_launch-instance-nova.xml:27(para) ./doc/training-guides/basic-install-guide/section_launch-instance-neutron.xml:27(para) ./doc/training-guides/basic-install-guide/section_launch-instance-neutron.xml:246(para) +msgid "This command provides no output." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_keystone-users.xml:99(para) +msgid "By default, the Identity service creates a special _member_ role. The OpenStack dashboard automatically grants access to users with this role. You must give the admin user access to this role in addition to the admin role." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_keystone-users.xml:105(para) +msgid "Add the admin tenant and user to the _member_ role:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_keystone-users.xml:114(para) +msgid "Any roles that you create must map to roles specified in the policy.json file included with each OpenStack service. The default policy for most services grants administrative access to the admin role. For more information, see the Operations Guide - Managing Projects and Users." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_keystone-users.xml:123(para) +msgid "Create a demo tenant and user for typical operations in your environment:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_keystone-users.xml:127(para) +msgid "Create the demo tenant:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_keystone-users.xml:138(para) +msgid "Do not repeat this step when creating additional users for this tenant." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_keystone-users.xml:143(para) +msgid "Create the demo user:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_keystone-users.xml:144(replaceable) ./doc/training-guides/basic-install-guide/section_keystone-verify.xml:89(replaceable) ./doc/training-guides/basic-install-guide/section_keystone-verify.xml:101(replaceable) ./doc/training-guides/basic-install-guide/ch_clients.xml:41(replaceable) +msgid "DEMO_PASS" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_keystone-users.xml:154(para) +msgid "Replace DEMO_PASS with a suitable password and EMAIL_ADDRESS with a suitable e-mail address." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_keystone-users.xml:159(para) +msgid "Add the demo tenant and user to the _member_ role:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_keystone-users.xml:168(para) +msgid "You can repeat this procedure to create additional tenants and users." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_keystone-users.xml:173(para) +msgid "OpenStack services also require a tenant, user, and role to interact with other services. You will create a user in the service tenant for each service that you install." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_keystone-users.xml:179(para) +msgid "Create the service tenant:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_ceilometer-nova.xml:8(title) +msgid "Install the Compute agent for Telemetry" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_ceilometer-nova.xml:10(para) +msgid "Telemetry provides an API service that provides a collector and a range of disparate agents. This procedure details how to install the agent that runs on the compute node." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_ceilometer-nova.xml:15(para) +msgid "Install the Telemetry service on the compute node:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_ceilometer-nova.xml:21(para) +msgid "Set the following options in the /etc/nova/nova.conf file:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_ceilometer-nova.xml:31(para) +msgid "The option is a multi valued option, which openstack-config cannot set properly. See ." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_ceilometer-nova.xml:37(para) +msgid "Edit the /etc/nova/nova.conf file and add the following lines to the [DEFAULT] section:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_ceilometer-nova.xml:54(para) ./doc/training-guides/basic-install-guide/section_neutron-ml2-compute-node.xml:369(para) ./doc/training-guides/basic-install-guide/section_nova-compute-install.xml:181(para) +msgid "Restart the Compute service:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_ceilometer-nova.xml:59(para) +msgid "You must set the secret key that you defined previously. The Telemetry service nodes share this key as a shared secret:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_ceilometer-nova.xml:63(replaceable) ./doc/training-guides/basic-install-guide/section_ceilometer-nova.xml:71(replaceable) ./doc/training-guides/basic-install-guide/section_ceilometer-install.xml:141(replaceable) +msgid "CEILOMETER_TOKEN" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_ceilometer-nova.xml:64(para) +msgid "Edit the /etc/ceilometer/ceilometer.conf file and change these lines in the [publisher] section. Replace CEILOMETER_TOKEN with the ceilometer token that you created previously:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_ceilometer-nova.xml:75(para) ./doc/training-guides/basic-install-guide/section_ceilometer-install.xml:145(para) +msgid "Configure the RabbitMQ access:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_ceilometer-nova.xml:78(para) ./doc/training-guides/basic-install-guide/section_ceilometer-nova.xml:126(para) ./doc/training-guides/basic-install-guide/section_ceilometer-install.xml:148(para) ./doc/training-guides/basic-install-guide/section_ceilometer-install.xml:161(para) +msgid "Edit the /etc/ceilometer/ceilometer.conf file and update the [DEFAULT] section:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_ceilometer-nova.xml:85(para) +msgid "Add the Identity service credentials:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_ceilometer-nova.xml:95(replaceable) ./doc/training-guides/basic-install-guide/section_ceilometer-nova.xml:101(replaceable) ./doc/training-guides/basic-install-guide/section_ceilometer-nova.xml:114(replaceable) ./doc/training-guides/basic-install-guide/section_ceilometer-nova.xml:121(replaceable) ./doc/training-guides/basic-install-guide/section_ceilometer-install.xml:172(replaceable) ./doc/training-guides/basic-install-guide/section_ceilometer-install.xml:201(replaceable) ./doc/training-guides/basic-install-guide/section_ceilometer-install.xml:209(replaceable) ./doc/training-guides/basic-install-guide/section_ceilometer-install.xml:221(replaceable) ./doc/training-guides/basic-install-guide/section_ceilometer-install.xml:228(replaceable) +msgid "CEILOMETER_PASS" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_ceilometer-nova.xml:104(para) ./doc/training-guides/basic-install-guide/section_ceilometer-install.xml:210(para) +msgid "Edit the /etc/ceilometer/ceilometer.conf file and change the [keystone_authtoken] section:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_ceilometer-nova.xml:115(para) ./doc/training-guides/basic-install-guide/section_ceilometer-install.xml:222(para) +msgid "Also set the [service_credentials] section:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_ceilometer-nova.xml:125(para) ./doc/training-guides/basic-install-guide/section_ceilometer-install.xml:160(para) +msgid "Configure the log directory." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_ceilometer-nova.xml:137(para) +msgid "Start the service and configure it to start when the system boots:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_ceilometer-cinder.xml:8(title) +msgid "Add the Block Storage service agent for Telemetry" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_ceilometer-cinder.xml:11(para) +msgid "To retrieve volume samples, you must configure the Block Storage service to send notifications to the bus." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_ceilometer-cinder.xml:14(para) +msgid "Edit /etc/cinder/cinder.conf and add in the [DEFAULT] section on the controller and volume nodes:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_ceilometer-cinder.xml:20(para) +msgid "Run the following commands on the controller and volume nodes:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_ceilometer-cinder.xml:27(para) +msgid "Restart the Block Storage services with their new settings." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_ceilometer-cinder.xml:29(para) +msgid "On the controller node:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_ceilometer-cinder.xml:34(para) +msgid "On the volume node:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_glance-verify.xml:7(title) ./doc/training-guides/basic-install-guide/section_keystone-verify.xml:7(title) ./doc/training-guides/basic-install-guide/section_heat-verify.xml:7(title) ./doc/training-guides/basic-install-guide/section_basics-ntp.xml:95(title) ./doc/training-guides/basic-install-guide/section_nova-verify.xml:7(title) +msgid "Verify operation" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_glance-verify.xml:8(para) +msgid "This section describes how to verify operation of the Image Service using CirrOS, a small Linux image that helps you test your OpenStack deployment." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_glance-verify.xml:12(para) +msgid "For more information about how to download and build images, see OpenStack Virtual Machine Image Guide. For information about how to manage images, see the OpenStack User Guide." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_glance-verify.xml:22(para) +msgid "Create and change into a temporary local directory:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_glance-verify.xml:27(para) +msgid "Download the image to the local directory:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_glance-verify.xml:31(para) ./doc/training-guides/basic-install-guide/section_nova-controller-install.xml:41(para) ./doc/training-guides/basic-install-guide/section_nova-verify.xml:15(para) ./doc/training-guides/basic-install-guide/section_glance-install.xml:48(para) +msgid "Source the admin credentials to gain access to admin-only CLI commands:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_glance-verify.xml:36(para) +msgid "Upload the image to the Image Service:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_glance-verify.xml:59(para) +msgid "For information about the parameters for the command, see Image Service command-line client in the OpenStack Command-Line Interface Reference." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_glance-verify.xml:65(para) +msgid "For information about disk and container formats for images, see Disk and container formats for images in the OpenStack Virtual Machine Image Guide." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_glance-verify.xml:71(para) +msgid "Because the returned image ID is generated dynamically, your deployment generates a different ID than the one shown in this example." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_glance-verify.xml:77(para) +msgid "Confirm upload of the image and validate attributes:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_glance-verify.xml:87(para) +msgid "Remove the temporary local directory:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/ch_debconf.xml:8(title) +msgid "Configure OpenStack with debconf" +msgstr "" + #. When image changes, this message will be marked fuzzy or untranslated for you. #. It doesn't matter what you translate it to: it's not used at all. #: ./doc/training-guides/basic-install-guide/lab001-control-node.xml:13(None) ./doc/training-guides/basic-install-guide/lab000-virtualbox-basics.xml:126(None) ./doc/training-guides/basic-install-guide/lab003-compute-node.xml:18(None) ./doc/training-guides/basic-install-guide/lab002-network-node.xml:15(None) @@ -1340,7 +2130,7 @@ msgid "To avoid issues on the VirtualBox virtual machine (controller node), /etc/network/interfaces/etc/network/interfaces and edit file as mentioned:" +msgid "Open /etc/network/interfaces and edit the file as mentioned:" msgstr "" #: ./doc/training-guides/basic-install-guide/lab001-control-node.xml:107(para) @@ -1384,7 +2174,7 @@ msgid "After saving the interfaces file, restart the networking service:" msgstr "" #: ./doc/training-guides/basic-install-guide/lab001-control-node.xml:113(para) -msgid "You should see the expected network interface cards having the required IP Addresses." +msgid "You should see the expected network interface cards with the required IP Addresses." msgstr "" #: ./doc/training-guides/basic-install-guide/lab001-control-node.xml:117(emphasis) @@ -1392,11 +2182,11 @@ msgid "SSH from HOST" msgstr "" #: ./doc/training-guides/basic-install-guide/lab001-control-node.xml:120(para) -msgid "Create an SSH key pair for your Control Node. Follow the same steps as you did in the starting section of the article for your host machine." +msgid "Create an SSH key pair for your Control Node. Follow the same steps as you did in the begin of the article for your host machine." msgstr "" #: ./doc/training-guides/basic-install-guide/lab001-control-node.xml:125(para) -msgid "To SSH into the Control Node from the Host Machine type the below command." +msgid "To SSH into the Control Node from the Host Machine, type the below command." msgstr "" #: ./doc/training-guides/basic-install-guide/lab001-control-node.xml:131(para) @@ -1420,7 +2210,7 @@ msgid "Install RabbitMQ:" msgstr "" #: ./doc/training-guides/basic-install-guide/lab001-control-node.xml:153(para) -msgid "Install NTP service:" +msgid "Install the NTP service:" msgstr "" #: ./doc/training-guides/basic-install-guide/lab001-control-node.xml:157(para) @@ -1456,7 +2246,7 @@ msgid "Keystone is an OpenStack project that provides Identity, Token, Catalog a msgstr "" #: ./doc/training-guides/basic-install-guide/lab001-control-node.xml:203(para) -msgid "Install Keystone packages:" +msgid "Install the Keystone packages:" msgstr "" #: ./doc/training-guides/basic-install-guide/lab001-control-node.xml:207(para) @@ -1664,7 +2454,7 @@ msgid "Cinder" msgstr "" #: ./doc/training-guides/basic-install-guide/lab001-control-node.xml:556(para) -msgid "Cinder is an OpenStack project to provide “block storage as a service”." +msgid "Cinder is an OpenStack project that provides “block storage as a service”." msgstr "" #: ./doc/training-guides/basic-install-guide/lab001-control-node.xml:560(para) @@ -1691,7 +2481,7 @@ msgstr "" msgid "Configure the iSCSI services:" msgstr "" -#: ./doc/training-guides/basic-install-guide/lab001-control-node.xml:591(para) +#: ./doc/training-guides/basic-install-guide/lab001-control-node.xml:591(para) ./doc/training-guides/basic-install-guide/section_nova-networking-compute-node.xml:79(para) msgid "Restart the services:" msgstr "" @@ -1724,7 +2514,7 @@ msgid "Restart the Cinder services:" msgstr "" #: ./doc/training-guides/basic-install-guide/lab001-control-node.xml:663(para) -msgid "Verify if Cinder services are running:" +msgid "Verify that the Cinder services are running:" msgstr "" #: ./doc/training-guides/basic-install-guide/lab001-control-node.xml:667(emphasis) @@ -1747,6 +2537,1166 @@ msgstr "" msgid "Reload Apache and memcached:" msgstr "" +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/training-guides/basic-install-guide/section_basics-networking-neutron.xml:31(None) ./doc/training-guides/basic-install-guide/ch_overview.xml:94(None) +msgid "@@image: 'figures/installguide_arch-neutron.png'; md5=9b3d2f2e5f9d88d198511ecbca829c6d" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_basics-networking-neutron.xml:8(title) ./doc/training-guides/basic-install-guide/ch_networking.xml:23(title) +msgid "OpenStack Networking (neutron)" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_basics-networking-neutron.xml:9(para) +msgid "The example architecture with OpenStack Networking (neutron) requires one controller node, one network node, and at least one compute node. The controller node contains one network interface on the management network. The network node contains one network interface on the management network, one on the instance tunnels network, and one on the external network. The compute node contains one network interface on the management network and one on the instance tunnels network." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_basics-networking-neutron.xml:19(para) +msgid "Network interface names vary by distribution. Traditionally, interfaces use \"eth\" followed by a sequential number. To cover all variations, this guide simply refers to the first interface as the interface with the lowest number, the second interface as the interface with the middle number, and the third interface as the interface with the highest number." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_basics-networking-neutron.xml:27(title) ./doc/training-guides/basic-install-guide/ch_overview.xml:90(title) +msgid "Three-node architecture with OpenStack Networking (neutron)" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_basics-networking-neutron.xml:35(para) ./doc/training-guides/basic-install-guide/section_basics-networking-nova.xml:31(para) +msgid "Unless you intend to use the exact configuration provided in this example architecture, you must modify the networks in this procedure to match your environment. Also, each node must resolve the other nodes by name in addition to IP address. For example, the controller name must resolve to 10.0.0.11, the IP address of the management interface on the controller node." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_basics-networking-neutron.xml:43(para) ./doc/training-guides/basic-install-guide/section_basics-networking-nova.xml:39(para) +msgid "Reconfiguring network interfaces will interrupt network connectivity. We recommend using a local terminal session for these procedures." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_basics-networking-neutron.xml:48(title) ./doc/training-guides/basic-install-guide/section_basics-networking-nova.xml:44(title) +msgid "Controller node" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_basics-networking-neutron.xml:50(title) ./doc/training-guides/basic-install-guide/section_basics-networking-neutron.xml:85(title) ./doc/training-guides/basic-install-guide/section_basics-networking-neutron.xml:167(title) ./doc/training-guides/basic-install-guide/section_basics-networking-nova.xml:46(title) ./doc/training-guides/basic-install-guide/section_basics-networking-nova.xml:78(title) +msgid "To configure networking:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_basics-networking-neutron.xml:52(para) ./doc/training-guides/basic-install-guide/section_basics-networking-neutron.xml:87(para) ./doc/training-guides/basic-install-guide/section_basics-networking-neutron.xml:169(para) ./doc/training-guides/basic-install-guide/section_basics-networking-nova.xml:48(para) ./doc/training-guides/basic-install-guide/section_basics-networking-nova.xml:80(para) +msgid "Configure the first interface as the management interface:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_basics-networking-neutron.xml:53(para) ./doc/training-guides/basic-install-guide/section_basics-networking-nova.xml:49(para) +msgid "IP address: 10.0.0.11" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_basics-networking-neutron.xml:54(para) ./doc/training-guides/basic-install-guide/section_basics-networking-neutron.xml:89(para) ./doc/training-guides/basic-install-guide/section_basics-networking-neutron.xml:96(para) ./doc/training-guides/basic-install-guide/section_basics-networking-neutron.xml:171(para) ./doc/training-guides/basic-install-guide/section_basics-networking-neutron.xml:182(para) ./doc/training-guides/basic-install-guide/section_basics-networking-nova.xml:50(para) ./doc/training-guides/basic-install-guide/section_basics-networking-nova.xml:82(para) +msgid "Network mask: 255.255.255.0 (or /24)" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_basics-networking-neutron.xml:55(para) ./doc/training-guides/basic-install-guide/section_basics-networking-neutron.xml:90(para) ./doc/training-guides/basic-install-guide/section_basics-networking-neutron.xml:172(para) ./doc/training-guides/basic-install-guide/section_basics-networking-nova.xml:51(para) ./doc/training-guides/basic-install-guide/section_basics-networking-nova.xml:83(para) +msgid "Default gateway: 10.0.0.1" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_basics-networking-neutron.xml:59(title) ./doc/training-guides/basic-install-guide/section_basics-networking-neutron.xml:142(title) ./doc/training-guides/basic-install-guide/section_basics-networking-neutron.xml:190(title) ./doc/training-guides/basic-install-guide/section_basics-networking-nova.xml:55(title) ./doc/training-guides/basic-install-guide/section_basics-networking-nova.xml:133(title) +msgid "To configure name resolution:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_basics-networking-neutron.xml:61(para) ./doc/training-guides/basic-install-guide/section_basics-networking-nova.xml:57(para) +msgid "Set the hostname of the node to controller." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_basics-networking-neutron.xml:65(para) ./doc/training-guides/basic-install-guide/section_basics-networking-neutron.xml:147(para) ./doc/training-guides/basic-install-guide/section_basics-networking-neutron.xml:195(para) ./doc/training-guides/basic-install-guide/section_basics-networking-nova.xml:61(para) ./doc/training-guides/basic-install-guide/section_basics-networking-nova.xml:138(para) +msgid "Edit the /etc/hosts file to contain the following:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_basics-networking-neutron.xml:76(para) ./doc/training-guides/basic-install-guide/section_basics-networking-neutron.xml:158(para) ./doc/training-guides/basic-install-guide/section_basics-networking-neutron.xml:206(para) ./doc/training-guides/basic-install-guide/section_basics-networking-nova.xml:69(para) ./doc/training-guides/basic-install-guide/section_basics-networking-nova.xml:146(para) +msgid "You must remove or comment the line beginning with 127.0.1.1." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_basics-networking-neutron.xml:83(title) ./doc/training-guides/basic-install-guide/lab000-virtualbox-basics.xml:453(title) +msgid "Network node" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_basics-networking-neutron.xml:88(para) +msgid "IP address: 10.0.0.21" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_basics-networking-neutron.xml:93(para) ./doc/training-guides/basic-install-guide/section_basics-networking-neutron.xml:179(para) +msgid "Configure the second interface as the instance tunnels interface:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_basics-networking-neutron.xml:95(para) +msgid "IP address: 10.0.1.21" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_basics-networking-neutron.xml:99(para) +msgid "The external interface uses a special configuration without an IP address assigned to it. Configure the third interface as the external interface:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_basics-networking-neutron.xml:102(para) ./doc/training-guides/basic-install-guide/section_neutron-ml2-network-node.xml:450(para) +msgid "Replace INTERFACE_NAME with the actual interface name. For example, eth2 or ens256." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_basics-networking-neutron.xml:107(para) ./doc/training-guides/basic-install-guide/section_basics-networking-nova.xml:98(para) +msgid "Edit the /etc/network/interfaces file to contain the following:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_basics-networking-neutron.xml:110(replaceable) ./doc/training-guides/basic-install-guide/section_basics-networking-neutron.xml:111(replaceable) ./doc/training-guides/basic-install-guide/section_basics-networking-neutron.xml:121(replaceable) ./doc/training-guides/basic-install-guide/section_nova-networking-compute-node.xml:52(replaceable) ./doc/training-guides/basic-install-guide/section_nova-networking-compute-node.xml:54(replaceable) ./doc/training-guides/basic-install-guide/section_nova-networking-compute-node.xml:75(replaceable) ./doc/training-guides/basic-install-guide/section_nova-networking-compute-node.xml:76(replaceable) ./doc/training-guides/basic-install-guide/section_basics-networking-nova.xml:101(replaceable) ./doc/training-guides/basic-install-guide/section_basics-networking-nova.xml:102(replaceable) ./doc/training-guides/basic-install-guide/section_basics-networking-nova.xml:112(replaceable) ./doc/training-guides/basic-install-guide/section_neutron-ml2-network-node.xml:453(replaceable) ./doc/training-guides/basic-install-guide/section_neutron-ml2-network-node.xml:461(replaceable) +msgid "INTERFACE_NAME" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_basics-networking-neutron.xml:116(para) ./doc/training-guides/basic-install-guide/section_basics-networking-nova.xml:107(para) +msgid "Edit the /etc/sysconfig/network-scripts/ifcfg-INTERFACE_NAME file to contain the following:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_basics-networking-neutron.xml:119(para) ./doc/training-guides/basic-install-guide/section_basics-networking-nova.xml:110(para) +msgid "Do not change the HWADDR and UUID keys." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_basics-networking-neutron.xml:127(para) ./doc/training-guides/basic-install-guide/section_basics-networking-nova.xml:118(para) +msgid "Edit the /etc/sysconfig/network/ifcfg-INTERFACE_NAME file to contain the following:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_basics-networking-neutron.xml:136(para) ./doc/training-guides/basic-install-guide/section_basics-networking-nova.xml:127(para) +msgid "Restart networking:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_basics-networking-neutron.xml:144(para) +msgid "Set the hostname of the node to network." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_basics-networking-neutron.xml:165(title) ./doc/training-guides/basic-install-guide/lab000-virtualbox-basics.xml:550(title) ./doc/training-guides/basic-install-guide/section_basics-networking-nova.xml:76(title) +msgid "Compute node" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_basics-networking-neutron.xml:170(para) ./doc/training-guides/basic-install-guide/section_basics-networking-nova.xml:81(para) +msgid "IP address: 10.0.0.31" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_basics-networking-neutron.xml:174(para) ./doc/training-guides/basic-install-guide/section_basics-networking-nova.xml:85(para) +msgid "Additional compute nodes should use 10.0.0.32, 10.0.0.33, and so on." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_basics-networking-neutron.xml:181(para) +msgid "IP address: 10.0.1.31" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_basics-networking-neutron.xml:184(para) +msgid "Additional compute nodes should use 10.0.1.32, 10.0.1.33, and so on." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_basics-networking-neutron.xml:192(para) ./doc/training-guides/basic-install-guide/section_basics-networking-nova.xml:135(para) +msgid "Set the hostname of the node to compute1." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_basics-networking-neutron.xml:213(title) ./doc/training-guides/basic-install-guide/section_neutron-initial-networks.xml:229(title) ./doc/training-guides/basic-install-guide/section_basics-networking-nova.xml:153(title) +msgid "Verify connectivity" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_basics-networking-neutron.xml:214(para) ./doc/training-guides/basic-install-guide/section_basics-networking-nova.xml:154(para) +msgid "We recommend that you verify network connectivity to the internet and among the nodes before proceeding further." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_basics-networking-neutron.xml:218(para) ./doc/training-guides/basic-install-guide/section_basics-networking-nova.xml:158(para) +msgid "From the controller node, a site on the internet:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_basics-networking-neutron.xml:232(para) +msgid "From the controller node, the management interface on the network node:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_basics-networking-neutron.xml:235(replaceable) ./doc/training-guides/common/module001-ch008-queues-messaging.xml:260(para) +msgid "network" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_basics-networking-neutron.xml:247(para) ./doc/training-guides/basic-install-guide/section_basics-networking-nova.xml:172(para) +msgid "From the controller node, the management interface on the compute node:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_basics-networking-neutron.xml:250(replaceable) ./doc/training-guides/basic-install-guide/section_basics-networking-nova.xml:175(replaceable) +msgid "compute1" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_basics-networking-neutron.xml:262(para) +msgid "From the network node, a site on the internet:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_basics-networking-neutron.xml:276(para) +msgid "From the network node, the management interface on the controller node:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_basics-networking-neutron.xml:291(para) +msgid "From the network node, the instance tunnels interface on the compute node:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_basics-networking-neutron.xml:306(para) ./doc/training-guides/basic-install-guide/section_basics-networking-nova.xml:187(para) +msgid "From the compute node, a site on the internet:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_basics-networking-neutron.xml:320(para) ./doc/training-guides/basic-install-guide/section_basics-networking-nova.xml:201(para) +msgid "From the compute node, the management interface on the controller node:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_basics-networking-neutron.xml:335(para) +msgid "From the compute node, the instance tunnels interface on the network node:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_basics-passwords.xml:8(title) +msgid "Passwords" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_basics-passwords.xml:9(para) +msgid "The various OpenStack services and the required software like the database and the messaging server have to be password protected. You use these passwords when configuring a service and then again to access the service. You have to choose a password while configuring the service and later remember to use the same password when accessing it. Optionally, you can generate random passwords with the pwgen program. Or, to create passwords one at a time, use the output of this command repeatedly: " +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_basics-passwords.xml:19(para) +msgid "This guide uses the convention that SERVICE_PASS is the password to access the service SERVICE and SERVICE_DBPASS is the database password used by the service SERVICE to access the database." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_basics-passwords.xml:26(para) +msgid "The complete list of passwords you need to define in this guide are:
Passwords
Password nameDescription
Database password (no variable used)Root password for the database
RABBIT_PASSPassword of user guest of RabbitMQ
KEYSTONE_DBPASSDatabase password of Identity service
DEMO_PASSPassword of user demo
ADMIN_PASSPassword of user admin
GLANCE_DBPASSDatabase password for Image Service
GLANCE_PASSPassword of Image Service user glance
NOVA_DBPASSDatabase password for Compute service
NOVA_PASSPassword of Compute service user nova
DASH_DBPASSDatabase password for the dashboard
CINDER_DBPASSDatabase password for the Block Storage service
CINDER_PASSPassword of Block Storage service user cinder
NEUTRON_DBPASSDatabase password for the Networking service
NEUTRON_PASSPassword of Networking service user neutron
HEAT_DBPASSDatabase password for the Orchestration service
HEAT_PASSPassword of Orchestration service user heat
CEILOMETER_DBPASSDatabase password for the Telemetry service
CEILOMETER_PASSPassword of Telemetry service user ceilometer
TROVE_DBPASSDatabase password of Database service
TROVE_PASSPassword of Database Service user trove
" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/ch_keystone.xml:7(title) +msgid "Add the Identity service" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/ch_swift.xml:7(title) +msgid "Add Object Storage" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/ch_swift.xml:8(para) +msgid "The OpenStack Object Storage services work together to provide object storage and retrieval through a REST API. For this example architecture, you must have already installed the Identity Service, also known as Keystone." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/ch_swift.xml:31(title) ./doc/training-guides/basic-install-guide/ch_horizon.xml:39(title) ./doc/training-guides/basic-install-guide/ch_heat.xml:14(title) ./doc/training-guides/basic-install-guide/ch_ceilometer.xml:19(title) ./doc/training-guides/basic-install-guide/ch_cinder.xml:21(title) ./doc/training-guides/basic-install-guide/ch_networking.xml:40(title) +msgid "Next steps" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/ch_swift.xml:32(para) +msgid "Your OpenStack environment now includes Object Storage. You can launch an instance or add more services to your environment in the following chapters." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-concepts.xml:7(title) +msgid "Networking concepts" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-concepts.xml:8(para) +msgid "OpenStack Networking (neutron) manages all networking facets for the Virtual Networking Infrastructure (VNI) and the access layer aspects of the Physical Networking Infrastructure (PNI) in your OpenStack environment. OpenStack Networking enables tenants to create advanced virtual network topologies including services such as firewalls, load balancers, and virtual private networks (VPNs)." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-concepts.xml:17(para) +msgid "Networking provides the networks, subnets, and routers object abstractions. Each abstraction has functionality that mimics its physical counterpart: networks contain subnets, and routers route traffic between different subnet and networks." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-concepts.xml:21(para) +msgid "Each router has one gateway that connects to a network, and many interfaces connected to subnets. Subnets can access machines on other subnets connected to the same router." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-concepts.xml:24(para) +msgid "Any given Networking set up has at least one external network. This network, unlike the other networks, is not merely a virtually defined network. Instead, it represents the view into a slice of the external network that is accessible outside the OpenStack installation. IP addresses on the Networking external network are accessible by anybody physically on the outside network. Because this network merely represents a slice of the outside network, DHCP is disabled on this network." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-concepts.xml:32(para) +msgid "In addition to external networks, any Networking set up has one or more internal networks. These software-defined networks connect directly to the VMs. Only the VMs on any given internal network, or those on subnets connected through interfaces to a similar router, can access VMs connected to that network directly." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-concepts.xml:38(para) +msgid "For the outside network to access VMs, and vice versa, routers between the networks are needed. Each router has one gateway that is connected to a network and many interfaces that are connected to subnets. Like a physical router, subnets can access machines on other subnets that are connected to the same router, and machines can access the outside network through the gateway for the router." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-concepts.xml:45(para) +msgid "Additionally, you can allocate IP addresses on external networks to ports on the internal network. Whenever something is connected to a subnet, that connection is called a port.You can associate external network IP addresses with ports to VMs. This way, entities on the outside network can access VMs." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-concepts.xml:50(para) +msgid "Networking also supports security groups. Security groups enable administrators to define firewall rules in groups. A VM can belong to one or more security groups, and Networking applies the rules in those security groups to block or unblock ports, port ranges, or traffic types for that VM." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-concepts.xml:56(para) +msgid "Each plug-in that Networking uses has its own concepts. While not vital to operating Networking, understanding these concepts can help you set up Networking. All Networking installations use a core plug-in and a security group plug-in (or just the No-Op security group plug-in). Additionally, Firewall-as-a-Service (FWaaS) and Load-Balancer-as-a-Service (LBaaS) plug-ins are available." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_nova-networking-initial-network.xml:7(title) +msgid "Create initial network" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_nova-networking-initial-network.xml:8(para) +msgid "Before launching your first instance, you must create the necessary virtual network infrastructure to which the instance will connect. This network typically provides internet access from instances. You can enable internet access to individual instances using a floating IP address and suitable security group rules. The admin tenant owns this network because it provides external network access for multiple tenants." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_nova-networking-initial-network.xml:17(para) +msgid "This network shares the same subnet associated with the physical network connected to the external interface on the compute node. You should specify an exclusive slice of this subnet to prevent interference with other devices on the external network." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_nova-networking-initial-network.xml:23(para) ./doc/training-guides/basic-install-guide/section_neutron-initial-networks.xml:41(para) ./doc/training-guides/basic-install-guide/section_neutron-initial-networks.xml:128(para) ./doc/training-guides/basic-install-guide/section_nova-verify.xml:12(para) +msgid "Perform these commands on the controller node." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_nova-networking-initial-network.xml:26(title) +msgid "To create the network" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_nova-networking-initial-network.xml:28(para) ./doc/training-guides/basic-install-guide/section_neutron-initial-networks.xml:46(para) +msgid "Source the admin tenant credentials:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_nova-networking-initial-network.xml:32(para) ./doc/training-guides/basic-install-guide/section_neutron-initial-networks.xml:50(para) ./doc/training-guides/basic-install-guide/section_neutron-initial-networks.xml:137(para) +msgid "Create the network:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_nova-networking-initial-network.xml:33(para) +msgid "Replace NETWORK_CIDR with the subnet associated with the physical network." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_nova-networking-initial-network.xml:36(replaceable) +msgid "NETWORK_CIDR" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_nova-networking-initial-network.xml:37(para) +msgid "For example, using an exclusive slice of 203.0.113.0/24 with IP address range 203.0.113.24 to 203.0.113.32:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_nova-networking-initial-network.xml:48(para) +msgid "Verify creation of the network:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/ch_horizon.xml:7(title) +msgid "Add the dashboard" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/ch_horizon.xml:8(para) +msgid "The OpenStack dashboard, also known as Horizon, is a Web interface that enables cloud administrators and users to manage various OpenStack resources and services." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/ch_horizon.xml:13(para) +msgid "The dashboard enables web-based interactions with the OpenStack Compute cloud controller through the OpenStack APIs." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/ch_horizon.xml:16(para) +msgid "These instructions show an example deployment configured with an Apache web server." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/ch_horizon.xml:18(para) +msgid "After you install and configure the dashboard, you can complete the following tasks:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/ch_horizon.xml:23(para) +msgid "Customize your dashboard. See section Customize the dashboard in the OpenStack Cloud Administrator Guide." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/ch_horizon.xml:31(para) +msgid "Set up session storage for the dashboard. See ." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/ch_horizon.xml:40(para) +msgid "Your OpenStack environment now includes the dashboard. You can launch an instance or add more services to your environment in the following chapters." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_keystone-verify.xml:8(para) +msgid "This section describes how to verify operation of the Identity service." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_keystone-verify.xml:12(para) +msgid "Unset the temporary OS_SERVICE_TOKEN and OS_SERVICE_ENDPOINT environment variables:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_keystone-verify.xml:17(para) +msgid "As the admin tenant and user, request an authentication token:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_keystone-verify.xml:21(para) +msgid "Replace ADMIN_PASS with the password you chose for the admin user in the Identity service. You might need to use single quotes (') around your password if it includes special characters." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_keystone-verify.xml:25(para) +msgid "Lengthy output that includes a token value verifies operation for the admin tenant and user." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_keystone-verify.xml:29(para) +msgid "As the admin tenant and user, list tenants to verify that the admin tenant and user can execute admin-only CLI commands and that the Identity service contains the tenants that you created in :" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_keystone-verify.xml:34(para) +msgid "As the admin tenant and user, list tenants to verify that the admin tenant and user can execute admin-only CLI commands and that the Identity service contains the tenants created by the configuration tool:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_keystone-verify.xml:53(para) +msgid "As the admin tenant and user, list users to verify that the Identity service contains the users that you created in :" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_keystone-verify.xml:57(para) +msgid "As the admin tenant and user, list users to verify that the Identity service contains the users created by the configuration tool:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_keystone-verify.xml:70(para) +msgid "As the admin tenant and user, list roles to verify that the Identity service contains the role that you created in :" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_keystone-verify.xml:74(para) +msgid "As the admin tenant and user, list roles to verify that the Identity service contains the role created by the configuration tool:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_keystone-verify.xml:87(para) +msgid "As the demo tenant and user, request an authentication token:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_keystone-verify.xml:91(para) +msgid "Replace DEMO_PASS with the password you chose for the demo user in the Identity service." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_keystone-verify.xml:94(para) +msgid "Lengthy output that includes a token value verifies operation for the demo tenant and user." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_keystone-verify.xml:98(para) +msgid "As the demo tenant and user, attempt to list users to verify that you cannot execute admin-only CLI commands:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_keystone-verify.xml:105(para) +msgid "Each OpenStack service references a policy.json file to determine the operations available to a particular tenant, user, or role. For more information, see the Operations Guide - Managing Projects and Users." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_basics-packages.xml:8(title) +msgid "OpenStack packages" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_basics-packages.xml:9(para) +msgid "Distributions might release OpenStack packages as part of their distribution or through other methods because the OpenStack and distribution release times are independent of each other." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_basics-packages.xml:13(para) +msgid "This section describes the configuration you must complete after you configure machines to install the latest OpenStack packages." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_basics-packages.xml:16(para) +msgid "The examples in this guide use the OpenStack packages from the RDO repository. These packages work on Red Hat Enterprise Linux 6, compatible versions of CentOS, and Fedora 20." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_basics-packages.xml:20(para) +msgid "Install the yum-plugin-priorities plug-in. This package allows the assignment of relative priorities to the configured software repositories. This functionality is used by the RDO release packages:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_basics-packages.xml:26(para) +msgid "To enable the RDO repository, download and install the rdo-release-juno package:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_basics-packages.xml:31(para) +msgid "The EPEL package includes GPG keys for package signing and repository information. This should only be installed on Red Hat Enterprise Linux and CentOS, not Fedora. Install the latest epel-release package (see http://download.fedoraproject.org/pub/epel/6/x86_64/repoview/epel-release.html). For example:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_basics-packages.xml:40(para) +msgid "The openstack-utils package contains utility programs that make installation and configuration easier. These programs are used throughout this guide. Install openstack-utils. This verifies that you can access the RDO repository:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_basics-packages.xml:47(para) +msgid "Use the Open Build Service repositories for Juno based on your openSUSE or SUSE Linux Enterprise Server version." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_basics-packages.xml:50(para) +msgid "For openSUSE 13.1 use:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_basics-packages.xml:52(para) +msgid "If you use SUSE Linux Enterprise Server 11 SP3, use:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_basics-packages.xml:55(para) +msgid "The packages are signed by GPG key 893A90DAD85F9316. You should verify the fingerprint of the imported GPG key before using it. " +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_basics-packages.xml:62(para) +msgid "The openstack-utils package contains utility programs that make installation and configuration easier. These programs are used throughout this guide. Install openstack-utils. This verifies that you can access the Open Build Service repository:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_basics-packages.xml:69(para) +msgid "The openstack-config program in the openstack-utils package uses crudini to manipulate configuration files. However, crudini version 0.3 does not support multi valued options. See https://bugs.launchpad.net/openstack-manuals/+bug/1269271. As a work around, you must manually set any multi valued options or the new value overwrites the previous value instead of creating a new option." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_basics-packages.xml:81(para) +msgid "The openstack-selinux package includes the policy files that are required to configure SELinux during OpenStack installation on RHEL and CentOS. This step is not required during OpenStack installation on Fedora. Install openstack-selinux:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_basics-packages.xml:88(para) +msgid "Upgrade your system packages:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_basics-packages.xml:92(para) +msgid "If the upgrade included a new kernel package, reboot the system to ensure the new kernel is running:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_basics-packages.xml:96(title) +msgid "To use the Ubuntu Cloud Archive for Juno" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_basics-packages.xml:97(para) +msgid "The Ubuntu Cloud Archive is a special repository that allows you to install newer releases of OpenStack on the stable supported version of Ubuntu." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_basics-packages.xml:103(para) +msgid "Install the Ubuntu Cloud Archive for Juno: " +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_basics-packages.xml:109(para) +msgid "Update the package database and upgrade your system:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_basics-packages.xml:114(para) +msgid "If you intend to use OpenStack Networking with Ubuntu 12.04, you should install a backported Linux kernel to improve the stability of your system. This installation is not needed if you intend to use the legacy networking service." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_basics-packages.xml:118(para) +msgid "Install the Ubuntu 13.10 backported kernel:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_basics-packages.xml:122(para) +msgid "Reboot the system for all changes to take effect:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_basics-packages.xml:127(title) +msgid "To use the Debian Wheezy backports archive for Juno" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_basics-packages.xml:129(para) +msgid "The Juno release is available only in Debian Sid (otherwise called Unstable). However, the Debian maintainers of OpenStack also maintain a non-official Debian repository for OpenStack containing Wheezy backports." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_basics-packages.xml:135(para) +msgid "Install the Debian Wheezy backport repository Juno:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_basics-packages.xml:140(para) +msgid "Install the Debian Wheezy OpenStack repository for Juno:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_basics-packages.xml:145(para) +msgid "Update the repository database and install the key:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_basics-packages.xml:149(para) +msgid "Update the package database, upgrade your system, and reboot for all changes to take effect:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_basics-packages.xml:155(para) +msgid "Numerous archive.gplhost.com mirrors are available around the world. All are available with both FTP and HTTP protocols (you should use the closest mirror). The list of mirrors is available at http://archive.gplhost.com/readme.mirrors." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_basics-packages.xml:162(title) +msgid "Manually install python-argparse" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_basics-packages.xml:163(para) +msgid "The Debian OpenStack packages are maintained on Debian Sid (also known as Debian Unstable) - the current development version. Backported packages run correctly on Debian Wheezy with one caveat:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_basics-packages.xml:167(para) +msgid "All OpenStack packages are written in Python. Wheezy uses Python 2.6 and 2.7, with Python 2.6 as the default interpreter; Sid has only Python 2.7. There is one packaging change between these two. In Python 2.6, you installed the python-argparse package separately. In Python 2.7, this package is installed by default. Unfortunately, in Python 2.7, this package does not include Provides: python-argparse directive." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_basics-packages.xml:175(para) +msgid "Because the packages are maintained in Sid where the Provides: python-argparse directive causes an error, and the Debian OpenStack maintainer wants to maintain one version of the OpenStack packages, you must manually install the python-argparse on each OpenStack system that runs Debian Wheezy before you install the other OpenStack packages. Use the following command to install the package:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_basics-packages.xml:184(para) +msgid "This caveat applies to most OpenStack packages in Wheezy." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ovs-compute-node.xml:7(title) ./doc/training-guides/basic-install-guide/section_nova-networking-compute-node.xml:7(title) ./doc/training-guides/basic-install-guide/section_neutron-ml2-compute-node.xml:7(title) +msgid "Configure compute node" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ovs-compute-node.xml:9(para) +msgid "This section details set up for any node that runs the nova-compute component but does not run the full network stack." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ovs-compute-node.xml:14(para) +msgid "By default, the system-config-firewall automated firewall configuration tool is in place on RHEL. This graphical interface (and a curses-style interface with -tui on the end of the name) enables you to configure IP tables as a basic firewall. You should disable it when you work with OpenStack Networking unless you are familiar with the underlying network technologies, as, by default, it blocks various types of network traffic that are important to neutron services. To disable it, launch the program and clear the Enabled check box." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ovs-compute-node.xml:23(para) +msgid "After you successfully set up OpenStack Networking with Neutron, you can re-enable and configure the tool. However, during OpenStack Networking setup, disable the tool to make it easier to debug network issues." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ovs-compute-node.xml:31(para) +msgid "Disable packet destination filtering (route verification) to let the networking services route traffic to the VMs. Edit the /etc/sysctl.conf file and run the following command to activate changes:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ovs-compute-node.xml:42(title) +msgid "Install Open vSwitch plug-in" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ovs-compute-node.xml:43(para) ./doc/training-guides/basic-install-guide/section_neutron-ovs-controller-node.xml:172(para) ./doc/training-guides/basic-install-guide/section_neutron-ovs-network-node.xml:164(para) +msgid "OpenStack Networking supports a variety of plug-ins. For simplicity, we chose to cover the most common plug-in, Open vSwitch, and configure it to use basic GRE tunnels for tenant network traffic." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ovs-compute-node.xml:48(para) ./doc/training-guides/basic-install-guide/section_neutron-ovs-network-node.xml:169(para) +msgid "Install the Open vSwitch plug-in and its dependencies:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ovs-compute-node.xml:55(para) +msgid "Restart Open vSwitch:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ovs-compute-node.xml:59(para) +msgid "Start Open vSwitch and configure it to start when the system boots:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ovs-compute-node.xml:67(para) +msgid "You must set some common configuration options. You must configure Networking core to use OVS. Edit the /etc/neutron/neutron.conf file:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ovs-compute-node.xml:76(para) +msgid "You must configure a firewall as well. You should use the same firewall plug-in that you chose to use when you set up the network node. To do this, edit /etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini file and set the firewall_driver value under the securitygroup to the same value used on the network node. For instance, if you chose to use the Hybrid OVS-IPTables plug-in, your configuration looks like this:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ovs-compute-node.xml:89(para) ./doc/training-guides/basic-install-guide/section_neutron-ovs-network-node.xml:298(para) +msgid "You must use at least the No-Op firewall. Otherwise, Horizon and other OpenStack services cannot get and set required VM boot options." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ovs-compute-node.xml:95(para) ./doc/training-guides/basic-install-guide/section_neutron-ovs-network-node.xml:304(para) +msgid "Configure the OVS plug-in to start on boot." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ovs-compute-node.xml:101(para) +msgid "Tell the OVS plug-in to use GRE tunneling with a br-int integration bridge, a br-tun tunneling bridge, and a local IP for the tunnel of DATA_INTERFACE's IP Edit the /etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini file:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ovs-compute-node.xml:116(replaceable) +msgid "DATA_INTERFACE_IP" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ovs-compute-node.xml:120(title) +msgid "Configure common components" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ovs-compute-node.xml:122(para) ./doc/training-guides/basic-install-guide/section_neutron-ovs-network-node.xml:83(para) +msgid "Configure Networking to use keystone for authentication:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ovs-compute-node.xml:125(para) ./doc/training-guides/basic-install-guide/section_neutron-ovs-compute-node.xml:159(para) +msgid "Set the auth_strategy configuration key to keystone in the [DEFAULT] section of the file:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ovs-compute-node.xml:131(para) ./doc/training-guides/basic-install-guide/section_neutron-ovs-controller-node.xml:96(para) ./doc/training-guides/basic-install-guide/section_neutron-ovs-network-node.xml:92(para) +msgid "Set the neutron configuration for keystone authentication:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ovs-compute-node.xml:148(replaceable) ./doc/training-guides/basic-install-guide/section_neutron-ovs-compute-node.xml:178(replaceable) ./doc/training-guides/basic-install-guide/section_neutron-ovs-compute-node.xml:220(replaceable) ./doc/training-guides/basic-install-guide/section_neutron-ovs-compute-node.xml:237(replaceable) ./doc/training-guides/basic-install-guide/section_neutron-ml2-compute-node.xml:72(replaceable) ./doc/training-guides/basic-install-guide/section_neutron-ml2-compute-node.xml:99(replaceable) ./doc/training-guides/basic-install-guide/section_neutron-ml2-compute-node.xml:288(replaceable) ./doc/training-guides/basic-install-guide/section_neutron-ml2-compute-node.xml:322(replaceable) ./doc/training-guides/basic-install-guide/section_neutron-ml2-controller-node.xml:34(replaceable) ./doc/training-guides/basic-install-guide/section_neutron-ml2-controller-node.xml:152(replaceable) ./doc/training-guides/basic-install-guide/section_neutron-ml2-controller-node.xml:178(replaceable) ./doc/training-guides/basic-install-guide/section_neutron-ml2-controller-node.xml:374(replaceable) ./doc/training-guides/basic-install-guide/section_neutron-ml2-controller-node.xml:404(replaceable) ./doc/training-guides/basic-install-guide/section_neutron-ovs-controller-node.xml:47(replaceable) ./doc/training-guides/basic-install-guide/section_neutron-ovs-controller-node.xml:111(replaceable) ./doc/training-guides/basic-install-guide/section_neutron-ovs-controller-node.xml:140(replaceable) ./doc/training-guides/basic-install-guide/section_neutron-ovs-controller-node.xml:224(replaceable) ./doc/training-guides/basic-install-guide/section_neutron-ovs-controller-node.xml:241(replaceable) ./doc/training-guides/basic-install-guide/section_neutron-ml2-network-node.xml:78(replaceable) ./doc/training-guides/basic-install-guide/section_neutron-ml2-network-node.xml:105(replaceable) ./doc/training-guides/basic-install-guide/section_neutron-ml2-network-node.xml:272(replaceable) ./doc/training-guides/basic-install-guide/section_neutron-ml2-network-node.xml:300(replaceable) ./doc/training-guides/basic-install-guide/section_neutron-ovs-network-node.xml:110(replaceable) ./doc/training-guides/basic-install-guide/section_neutron-ovs-network-node.xml:137(replaceable) ./doc/training-guides/basic-install-guide/section_neutron-ovs-network-node.xml:378(replaceable) ./doc/training-guides/basic-install-guide/section_neutron-ovs-network-node.xml:392(replaceable) +msgid "NEUTRON_PASS" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ovs-compute-node.xml:153(para) ./doc/training-guides/basic-install-guide/section_neutron-ovs-network-node.xml:114(para) +msgid "To configure neutron to use keystone for authentication, edit the /etc/neutron/neutron.conf file." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ovs-compute-node.xml:167(para) ./doc/training-guides/basic-install-guide/section_neutron-ovs-network-node.xml:126(para) +msgid "Add these lines to the [keystone_authtoken] section of the file:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ovs-compute-node.xml:183(para) ./doc/training-guides/basic-install-guide/section_neutron-ovs-controller-node.xml:145(para) ./doc/training-guides/basic-install-guide/section_neutron-ovs-network-node.xml:142(para) +msgid "Configure access to the RabbitMQ service:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ovs-compute-node.xml:194(para) +msgid "Configure the RabbitMQ access. Edit the /etc/neutron/neutron.conf file to modify the following parameters in the [DEFAULT] section." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ovs-compute-node.xml:204(title) ./doc/training-guides/basic-install-guide/section_neutron-ovs-controller-node.xml:207(title) +msgid "Configure Compute services for Networking" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ovs-compute-node.xml:206(para) +msgid "Configure OpenStack Compute to use OpenStack Networking services. Configure the /etc/nova/nova.conf file as per instructions below:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ovs-compute-node.xml:229(para) +msgid "Configure OpenStack Compute to use OpenStack Networking services. Edit the /etc/nova/nova.conf file:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ovs-compute-node.xml:245(para) +msgid "No matter which firewall driver you chose when you configured the network and compute nodes, you must edit the /etc/nova/nova.conf file to set the firewall driver to nova.virt.firewall.NoopFirewallDriver. Because OpenStack Networking handles the firewall, this statement instructs Compute to not use a firewall." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ovs-compute-node.xml:255(para) +msgid "If you want Networking to handle the firewall, edit the /etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini file to set the firewall_driver option to the firewall for the plug-in. For example, with OVS, edit the file as follows:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ovs-compute-node.xml:270(para) +msgid "If you do not want to use a firewall in Compute or Networking, edit both configuration files and set firewall_driver=nova.virt.firewall.NoopFirewallDriver. Also, edit the /etc/nova/nova.conf file and comment out or remove the security_group_api=neutron statement." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ovs-compute-node.xml:278(para) +msgid "Otherwise, when you issue commands, the ERROR: The server has either erred or is incapable of performing the requested operation. (HTTP 500) error might be returned." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ovs-compute-node.xml:289(title) ./doc/training-guides/basic-install-guide/section_neutron-ovs-controller-node.xml:309(title) ./doc/training-guides/basic-install-guide/section_neutron-ovs-network-node.xml:417(title) +msgid "Finalize installation" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ovs-compute-node.xml:291(para) ./doc/training-guides/basic-install-guide/section_neutron-ovs-controller-node.xml:285(para) ./doc/training-guides/basic-install-guide/section_neutron-ovs-network-node.xml:419(para) +msgid "The neutron-server initialization script expects a symbolic link /etc/neutron/plugin.ini pointing to the configuration file associated with your chosen plug-in. Using Open vSwitch, for example, the symbolic link must point to /etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini. If this symbolic link does not exist, create it using the following commands:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ovs-compute-node.xml:303(para) ./doc/training-guides/basic-install-guide/section_neutron-ovs-controller-node.xml:297(para) ./doc/training-guides/basic-install-guide/section_neutron-ovs-network-node.xml:431(para) +msgid "The openstack-neutron initialization script expects the variable NEUTRON_PLUGIN_CONF in file /etc/sysconfig/neutron to reference the configuration file associated with your chosen plug-in. Using Open vSwitch, for example, edit the /etc/sysconfig/neutron file and add the following:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ovs-compute-node.xml:314(para) ./doc/training-guides/basic-install-guide/section_neutron-ovs-network-node.xml:442(para) +msgid "Restart Networking services." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ovs-compute-node.xml:320(para) +msgid "Restart the Compute service." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_debconf-preseeding.xml:7(title) +msgid "Pre-seed debconf prompts" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_debconf-preseeding.xml:8(para) +msgid "You can pre-seed all debconf prompts. To pre-seed means to store responses in the debconf database so that debconf does not prompt the user for responses. Pre-seeding enables a hands-free installation for users. The package maintainer creates scripts that automatically configure the services." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_debconf-preseeding.xml:15(para) +msgid "The following example shows how to pre-seed an automated MySQL Server installation:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_debconf-preseeding.xml:17(replaceable) ./doc/training-guides/basic-install-guide/section_debconf-preseeding.xml:18(replaceable) ./doc/training-guides/basic-install-guide/section_debconf-preseeding.xml:20(replaceable) +msgid "MYSQL_PASSWORD" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_debconf-preseeding.xml:24(para) +msgid "The seen true option tells debconf that a specified screen was already seen by the user so do not show it again. This option is useful for upgrades." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_ceilometer-install.xml:11(title) +msgid "Install the Telemetry module" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_ceilometer-install.xml:13(para) +msgid "Telemetry provides an API service that provides a collector and a range of disparate agents. Before you can install these agents on nodes such as the compute node, you must use this procedure to install the core components on the controller node." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_ceilometer-install.xml:19(para) +msgid "Install the Telemetry service on the controller node:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_ceilometer-install.xml:31(para) +msgid "Respond to the prompts for [keystone_authtoken] settings, RabbitMQ credentials and API endpoint registration." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_ceilometer-install.xml:39(para) +msgid "The Telemetry service uses a database to store information. Specify the location of the database in the configuration file. The examples use a MongoDB database on the controller node:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_ceilometer-install.xml:47(para) +msgid "By default MongoDB is configured to create several 1 GB files in the /var/lib/mongodb/journal/ directory to support database journaling." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_ceilometer-install.xml:52(para) +msgid "If you need to minimize the space allocated to support database journaling then set the configuration key to true in the /etc/mongodb.conf configuration file. This configuration reduces the size of each journaling file to 512 MB." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_ceilometer-install.xml:60(para) +msgid "As the files are created the first time the MongoDB service starts you must stop the service and remove the files for this change to take effect:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_ceilometer-install.xml:68(para) +msgid "For more information on the configuration key refer to the MongoDB documentation at ." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_ceilometer-install.xml:73(para) +msgid "For instructions detailing the steps to disable database journaling entirely refer to ." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_ceilometer-install.xml:81(para) +msgid "Configure MongoDB to make it listen on the controller management IP address. Edit the /etc/mongodb.conf file and modify the bind_ip key:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_ceilometer-install.xml:87(para) +msgid "Restart the MongoDB service to apply the configuration change:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_ceilometer-install.xml:91(para) +msgid "Start the MongoDB server and configure it to start when the system boots:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_ceilometer-install.xml:101(para) +msgid "Create the database and a ceilometer database user:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_ceilometer-install.xml:106(replaceable) ./doc/training-guides/basic-install-guide/section_ceilometer-install.xml:112(replaceable) ./doc/training-guides/basic-install-guide/section_ceilometer-install.xml:119(replaceable) +msgid "CEILOMETER_DBPASS" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_ceilometer-install.xml:110(para) +msgid "Configure the Telemetry service to use the database:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_ceilometer-install.xml:113(para) +msgid "Edit the /etc/ceilometer/ceilometer.conf file and change the [database] section:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_ceilometer-install.xml:123(para) +msgid "You must define a secret key that is used as a shared secret among Telemetry service nodes. Use to generate a random token and store it in the configuration file:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_ceilometer-install.xml:130(para) +msgid "For SUSE Linux Enterprise, run the following command:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_ceilometer-install.xml:134(para) +msgid "Edit the /etc/ceilometer/ceilometer.conf file and change the [publisher] section. Replace CEILOMETER_TOKEN with the results of the openssl command:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_ceilometer-install.xml:154(para) +msgid "Configure the collector dispatcher:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_ceilometer-install.xml:168(para) +msgid "Create a ceilometer user that the Telemetry service uses to authenticate with the Identity Service. Use the service tenant and give the user the admin role:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_ceilometer-install.xml:172(replaceable) +msgid "ceilometer@example.com" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_ceilometer-install.xml:176(para) +msgid "Configure the Telemetry service to authenticate with the Identity Service." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_ceilometer-install.xml:178(para) +msgid "Set the value to keystone in the /etc/ceilometer/ceilometer.conf file:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_ceilometer-install.xml:188(para) +msgid "Add the credentials to the configuration files for the Telemetry service:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_ceilometer-install.xml:231(para) +msgid "Register the Telemetry service with the Identity Service so that other OpenStack services can locate it. Use the command to register the service and specify the endpoint:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_ceilometer-install.xml:244(para) +msgid "Restart the services with their new settings:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_ceilometer-install.xml:253(para) +msgid "Start the openstack-ceilometer-api, openstack-ceilometer-agent-centralopenstack-ceilometer-central, openstack-ceilometer-collector, openstack-ceilometer-alarm-evaluator, and openstack-ceilometer-alarm-notifier services and configure them to start when the system boots:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_heat-verify.xml:8(para) +msgid "This section describes how to verify operation of the Orchestration module (heat)." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_heat-verify.xml:12(para) ./doc/training-guides/basic-install-guide/section_neutron-initial-networks.xml:133(para) ./doc/training-guides/basic-install-guide/section_launch-instance-nova.xml:16(para) ./doc/training-guides/basic-install-guide/section_launch-instance-neutron.xml:16(para) +msgid "Source the demo tenant credentials:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_heat-verify.xml:16(para) +msgid "The Orchestration module uses templates to describe stacks. To learn about the template language, see the Template Guide in the Heat developer documentation." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_heat-verify.xml:22(para) +msgid "Create a test template in the test-stack.yml file with the following content:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_heat-verify.xml:27(para) +msgid "Use the command to create a stack from the template:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_heat-verify.xml:39(para) +msgid "Use the command to verify successful creation of the stack:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/ch_heat.xml:7(title) +msgid "Add the Orchestration module" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/ch_heat.xml:8(para) +msgid "The Orchestration module (heat) uses a heat orchestration template (HOT) to create and manage cloud resources." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/ch_heat.xml:15(para) +msgid "Your OpenStack environment now includes Orchestration. You can launch an instance or add more services to your environment in the following chapters." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_basics-ntp.xml:8(title) +msgid "Network Time Protocol (NTP)" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_basics-ntp.xml:9(para) +msgid "You must install NTP to properly synchronize services among nodes. We recommend that you configure the controller node to reference upstream servers and other nodes to reference the controller node." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_basics-ntp.xml:15(title) ./doc/training-guides/basic-install-guide/section_nova-networking-controller-node.xml:7(title) ./doc/training-guides/basic-install-guide/section_neutron-ml2-controller-node.xml:7(title) ./doc/training-guides/basic-install-guide/section_neutron-ovs-controller-node.xml:7(title) +msgid "Configure controller node" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_basics-ntp.xml:17(title) ./doc/training-guides/basic-install-guide/section_basics-ntp.xml:59(title) +msgid "To install the NTP service" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_basics-ntp.xml:25(title) ./doc/training-guides/basic-install-guide/section_basics-ntp.xml:67(title) +msgid "To configure the NTP service" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_basics-ntp.xml:26(para) +msgid "By default, the controller node synchronizes the time via a pool of public servers. However, you can optionally edit the /etc/ntp.conf file to configure alternative servers such as those provided by your organization." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_basics-ntp.xml:31(para) ./doc/training-guides/basic-install-guide/section_basics-ntp.xml:71(para) +msgid "Edit the /etc/ntp.conf file:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_basics-ntp.xml:32(para) +msgid "Add, change, or remove the server keys as necessary for your environment. Replace NTP_SERVER with the hostname or IP address of suitable NTP server." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_basics-ntp.xml:36(replaceable) +msgid "NTP_SERVER" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_basics-ntp.xml:38(para) ./doc/training-guides/basic-install-guide/section_basics-ntp.xml:76(para) +msgid "Remove the /var/lib/ntp/ntp.conf.dhcp file if it exists." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_basics-ntp.xml:43(para) ./doc/training-guides/basic-install-guide/section_basics-ntp.xml:81(para) +msgid "Restart the NTP service:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_basics-ntp.xml:47(para) ./doc/training-guides/basic-install-guide/section_basics-ntp.xml:85(para) +msgid "Start the NTP service and configure it to start when the system boots:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_basics-ntp.xml:57(title) +msgid "Configure other nodes" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_basics-ntp.xml:68(para) +msgid "Configure the network and compute nodes to reference the controller node." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_basics-ntp.xml:72(para) +msgid "Comment out or remove all but one server key and change it to reference the controller node." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_basics-ntp.xml:96(para) +msgid "We recommend that you verify NTP synchronization before proceeding further. Some nodes, particularly those that reference the controller node, can take several minutes to synchronize." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_basics-ntp.xml:100(title) +msgid "To verify NTP synchronization" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_basics-ntp.xml:102(para) ./doc/training-guides/basic-install-guide/section_basics-ntp.xml:117(para) +msgid "Run this command on the controller node:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_basics-ntp.xml:109(para) +msgid "Contents in the remote column should indicate the hostname or IP address of one or more NTP servers." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_basics-ntp.xml:112(para) ./doc/training-guides/basic-install-guide/section_basics-ntp.xml:136(para) +msgid "Contents in the refid column typically reference IP addresses of upstream servers." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_basics-ntp.xml:124(para) +msgid "Contents in the condition column should indicate sys.peer for at least one server." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_basics-ntp.xml:128(para) ./doc/training-guides/basic-install-guide/section_basics-ntp.xml:141(para) +msgid "Run this command on all other nodes:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_basics-ntp.xml:133(para) +msgid "Contents in the remote column should indicate the hostname of the controller node." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_basics-ntp.xml:147(para) +msgid "Contents in the condition column should indicate sys.peer." +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/training-guides/basic-install-guide/section_neutron-initial-networks.xml:24(None) +msgid "@@image: 'figures/installguide_neutron-initial-networks.png'; md5=df1d74b6f91feefe5cfaf7824aac86e1" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-initial-networks.xml:7(title) +msgid "Create initial networks" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-initial-networks.xml:8(para) +msgid "Before launching your first instance, you must create the necessary virtual network infrastructure to which the instance will connect, including the external network and tenant network. See . After creating this infrastructure, we recommend that you verify connectivity and resolve any issues before proceeding further." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-initial-networks.xml:20(title) +msgid "Initial networks" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-initial-networks.xml:29(title) +msgid "External network" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-initial-networks.xml:30(para) +msgid "The external network typically provides internet access for your instances. By default, this network only allows internet access from instances using Network Address Translation (NAT). You can enable internet access to individual instances using a floating IP address and suitable security group rules. The admin tenant owns this network because it provides external network access for multiple tenants. You must also enable sharing to allow access by those tenants." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-initial-networks.xml:44(title) +msgid "To create the external network" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-initial-networks.xml:70(para) +msgid "Like a physical network, a virtual network requires a subnet assigned to it. The external network shares the same subnet and gateway associated with the physical network connected to the external interface on the network node. You should specify an exclusive slice of this subnet for router and floating IP addresses to prevent interference with other devices on the external network." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-initial-networks.xml:77(para) +msgid "Replace FLOATING_IP_START and FLOATING_IP_END with the first and last IP addresses of the range that you want to allocate for floating IP addresses. Replace EXTERNAL_NETWORK_CIDR with the subnet associated with the physical network. Replace EXTERNAL_NETWORK_GATEWAY with the gateway associated with the physical network, typically the \".1\" IP address. You should disable DHCP on this subnet because instances do not connect directly to the external network and floating IP addresses require manual assignment." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-initial-networks.xml:88(title) +msgid "To create a subnet on the external network" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-initial-networks.xml:90(para) ./doc/training-guides/basic-install-guide/section_neutron-initial-networks.xml:165(para) +msgid "Create the subnet:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-initial-networks.xml:92(replaceable) +msgid "FLOATING_IP_START" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-initial-networks.xml:92(replaceable) +msgid "FLOATING_IP_END" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-initial-networks.xml:93(replaceable) +msgid "EXTERNAL_NETWORK_GATEWAY" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-initial-networks.xml:93(replaceable) +msgid "EXTERNAL_NETWORK_CIDR" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-initial-networks.xml:94(para) +msgid "For example, using 203.0.113.0/24 with floating IP address range 203.0.113.101 to 203.0.113.200:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-initial-networks.xml:122(title) +msgid "Tenant network" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-initial-networks.xml:123(para) +msgid "The tenant network provides internal network access for instances. The architecture isolates this type of network from other tenants. The demo tenant owns this network because it only provides network access for instances within it." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-initial-networks.xml:131(title) +msgid "To create the tenant network" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-initial-networks.xml:153(para) +msgid "Like the external network, your tenant network also requires a subnet attached to it. You can specify any valid subnet because the architecture isolates tenant networks. Replace TENANT_NETWORK_CIDR with the subnet you want to associate with the tenant network. Replace TENANT_NETWORK_GATEWAY with the gateway you want to associate with this network, typically the \".1\" IP address. By default, this subnet will use DHCP so your instances can obtain IP addresses." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-initial-networks.xml:163(title) +msgid "To create a subnet on the tenant network" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-initial-networks.xml:167(replaceable) +msgid "TENANT_NETWORK_GATEWAY" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-initial-networks.xml:167(replaceable) +msgid "TENANT_NETWORK_CIDR" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-initial-networks.xml:168(para) +msgid "Example using 192.168.1.0/24:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-initial-networks.xml:191(para) +msgid "A virtual router passes network traffic between two or more virtual networks. Each router requires one or more interfaces and/or gateways that provide access to specific networks. In this case, you will create a router and attach your tenant and external networks to it." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-initial-networks.xml:197(title) +msgid "To create a router on the tenant network and attach the external and tenant networks to it" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-initial-networks.xml:200(para) +msgid "Create the router:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-initial-networks.xml:215(para) +msgid "Attach the router to the demo tenant subnet:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-initial-networks.xml:221(para) +msgid "Attach the router to the external network by setting it as the gateway:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-initial-networks.xml:230(para) +msgid "We recommend that you verify network connectivity and resolve any issues before proceeding further. Following the external network subnet example using 203.0.113.0/24, the tenant router gateway should occupy the lowest IP address in the floating IP address range, 203.0.113.101. If you configured your external physical network and virtual networks correctly, you should be able to this IP address from any host on your external physical network." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-initial-networks.xml:239(para) +msgid "If you are building your OpenStack nodes as virtual machines, you must configure the hypervisor to permit promiscuous mode on the external network." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-initial-networks.xml:244(title) +msgid "To verify network connectivity" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-initial-networks.xml:246(para) +msgid "Ping the tenant router gateway:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/ch_clients.xml:7(title) +msgid "Install and configure the OpenStack clients" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/ch_clients.xml:8(para) +msgid "The following sections contain information about working with the OpenStack clients. Recall: in the previous section, you used the client." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/ch_clients.xml:11(para) +msgid "You must install the client tools to complete the rest of the installation." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/ch_clients.xml:13(para) +msgid "Configure the clients on your desktop rather than on the server so that you have a similar experience to your users." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/ch_clients.xml:21(title) +msgid "Create openrc.sh files" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/ch_clients.xml:23(para) +msgid "As explained in , use the credentials from and create the following PROJECT-openrc.sh files:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/ch_clients.xml:33(para) +msgid "admin-openrc.sh for the administrative user" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/ch_clients.xml:38(para) +msgid "demo-openrc.sh for the normal user: " +msgstr "" + +#: ./doc/training-guides/basic-install-guide/ch_basics.xml:8(title) +msgid "Basic environment configuration" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/ch_basics.xml:11(para) +msgid "The trunk version of this guide focuses on the future Juno release and will not work for the current Icehouse release. If you want to install Icehouse, you must use the Icehouse version of this guide instead." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/ch_basics.xml:20(para) +msgid "This chapter explains how to configure each node in the example architectures including the two-node architecture with legacy networking and three-node architecture with OpenStack Networking (neutron)." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/ch_basics.xml:27(para) +msgid "Although most environments include OpenStack Identity, Image Service, Compute, at least one networking service, and the dashboard, OpenStack Object Storage can operate independently of most other services. If your use case only involves Object Storage, you can skip to . However, the dashboard will not work without at least OpenStack Image Service and Compute." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/ch_basics.xml:36(para) +msgid "You must use an account with administrative privileges to configure each node. Either run the commands as the root user or configure the sudo utility." +msgstr "" + #: ./doc/training-guides/basic-install-guide/lab004-openstack-production.xml:7(title) msgid "OpenStack In Production" msgstr "" @@ -1755,6 +3705,386 @@ msgstr "" msgid "More Content To be Added." msgstr "" +#: ./doc/training-guides/basic-install-guide/section_nova-controller-install.xml:7(title) +msgid "Install and configure controller node" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_nova-controller-install.xml:8(para) +msgid "This section describes how to install and configure the Compute service, code-named nova, on the controller node." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_nova-controller-install.xml:12(para) +msgid "Before you install and configure Compute, you must create a database and Identity service credentials including endpoints." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_nova-controller-install.xml:15(para) ./doc/training-guides/basic-install-guide/section_glance-install.xml:22(para) +msgid "To create the database, complete these steps:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_nova-controller-install.xml:18(para) ./doc/training-guides/basic-install-guide/section_glance-install.xml:25(para) +msgid "Use the database access client to connect to the database server as the root user:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_nova-controller-install.xml:23(para) +msgid "Create the nova database:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_nova-controller-install.xml:27(para) +msgid "Grant proper access to the nova database:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_nova-controller-install.xml:29(replaceable) ./doc/training-guides/basic-install-guide/section_nova-controller-install.xml:30(replaceable) ./doc/training-guides/basic-install-guide/section_nova-controller-install.xml:99(replaceable) ./doc/training-guides/basic-install-guide/section_nova-compute-install.xml:38(replaceable) +msgid "NOVA_DBPASS" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_nova-controller-install.xml:31(para) +msgid "Replace NOVA_DBPASS with a suitable password." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_nova-controller-install.xml:35(para) ./doc/training-guides/basic-install-guide/section_glance-install.xml:42(para) +msgid "Exit the database access client:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_nova-controller-install.xml:46(para) ./doc/training-guides/basic-install-guide/section_glance-install.xml:53(para) +msgid "To create the Identity service credentials, complete these steps:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_nova-controller-install.xml:50(para) +msgid "Create the nova user:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_nova-controller-install.xml:51(replaceable) ./doc/training-guides/basic-install-guide/section_nova-controller-install.xml:127(replaceable) ./doc/training-guides/basic-install-guide/section_neutron-ml2-controller-node.xml:228(replaceable) ./doc/training-guides/basic-install-guide/section_neutron-ml2-controller-node.xml:252(replaceable) ./doc/training-guides/basic-install-guide/section_nova-compute-install.xml:66(replaceable) +msgid "NOVA_PASS" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_nova-controller-install.xml:52(para) +msgid "Replace NOVA_PASS with a suitable password and EMAIL_ADDRESS with a suitable e-mail address." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_nova-controller-install.xml:57(para) +msgid "Link the nova user to the service tenant and admin role:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_nova-controller-install.xml:63(para) +msgid "Create the nova service:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_nova-controller-install.xml:69(para) +msgid "Create the Compute service endpoints:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_nova-controller-install.xml:78(title) +msgid "To install and configure Compute controller components" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_nova-controller-install.xml:80(para) ./doc/training-guides/basic-install-guide/section_nova-controller-install.xml:166(para) ./doc/training-guides/basic-install-guide/section_glance-install.xml:87(para) ./doc/training-guides/basic-install-guide/section_glance-install.xml:185(para) ./doc/training-guides/basic-install-guide/section_nova-compute-install.xml:24(para) ./doc/training-guides/basic-install-guide/section_nova-compute-install.xml:125(para) +msgid "Install the packages:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_nova-controller-install.xml:91(para) ./doc/training-guides/basic-install-guide/section_nova-controller-install.xml:181(para) ./doc/training-guides/basic-install-guide/section_nova-compute-install.xml:30(para) +msgid "Edit the /etc/nova/nova.conf file and complete the following actions:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_nova-controller-install.xml:100(para) ./doc/training-guides/basic-install-guide/section_nova-compute-install.xml:39(para) +msgid "Replace NOVA_DBPASS with the password you chose for the Compute database." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_nova-controller-install.xml:104(para) ./doc/training-guides/basic-install-guide/section_glance-install.xml:106(para) ./doc/training-guides/basic-install-guide/section_nova-compute-install.xml:43(para) ./doc/training-guides/basic-install-guide/section_heat-install.xml:94(para) +msgid "In the [DEFAULT] section, configure RabbitMQ message broker access:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_nova-controller-install.xml:111(para) ./doc/training-guides/basic-install-guide/section_glance-install.xml:113(para) ./doc/training-guides/basic-install-guide/section_neutron-ml2-compute-node.xml:116(para) ./doc/training-guides/basic-install-guide/section_neutron-ml2-compute-node.xml:128(para) ./doc/training-guides/basic-install-guide/section_neutron-ml2-controller-node.xml:184(para) ./doc/training-guides/basic-install-guide/section_neutron-ml2-controller-node.xml:203(para) ./doc/training-guides/basic-install-guide/section_nova-compute-install.xml:50(para) ./doc/training-guides/basic-install-guide/section_heat-install.xml:101(para) ./doc/training-guides/basic-install-guide/section_neutron-ml2-network-node.xml:111(para) ./doc/training-guides/basic-install-guide/section_neutron-ml2-network-node.xml:131(para) +msgid "Replace RABBIT_PASS with the password you chose for the guest account in RabbitMQ." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_nova-controller-install.xml:116(para) +msgid "In the [keystone_authtoken] section, configure Identity service access:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_nova-controller-install.xml:128(para) ./doc/training-guides/basic-install-guide/section_nova-compute-install.xml:67(para) +msgid "Replace NOVA_PASS with the password you chose for the nova user in the Identity service." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_nova-controller-install.xml:133(para) +msgid "In the [DEFAULT] section, configure the my_ip key to use the management interface IP address of the controller node:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_nova-controller-install.xml:141(para) ./doc/training-guides/basic-install-guide/section_nova-controller-install.xml:185(para) +msgid "In the [DEFAULT] section, configure the VNC proxy to use the management interface IP address of the controller node:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_nova-controller-install.xml:150(para) ./doc/training-guides/basic-install-guide/section_nova-compute-install.xml:113(para) +msgid "In the [DEFAULT] section, configure the location of the Image Service:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_nova-controller-install.xml:159(para) +msgid "Populate the Compute database:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_nova-controller-install.xml:164(title) +msgid "To install and configure the Compute controller components" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_nova-controller-install.xml:171(para) ./doc/training-guides/basic-install-guide/section_glance-install.xml:189(para) ./doc/training-guides/basic-install-guide/section_neutron-ml2-compute-node.xml:46(para) ./doc/training-guides/basic-install-guide/section_neutron-ml2-controller-node.xml:78(para) ./doc/training-guides/basic-install-guide/section_heat-install.xml:156(para) ./doc/training-guides/basic-install-guide/section_neutron-ml2-network-node.xml:49(para) +msgid "Respond to prompts for database management, Identity service credentials, service endpoint registration, and message broker credentials." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_nova-controller-install.xml:199(para) ./doc/training-guides/basic-install-guide/section_nova-networking-controller-node.xml:28(para) ./doc/training-guides/basic-install-guide/section_neutron-ml2-controller-node.xml:441(para) ./doc/training-guides/basic-install-guide/section_neutron-ovs-controller-node.xml:318(para) +msgid "Restart the Compute services:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_nova-controller-install.xml:208(para) +msgid "Start the Compute services and configure them to start when the system boots:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_nova-controller-install.xml:224(para) ./doc/training-guides/basic-install-guide/section_glance-install.xml:226(para) ./doc/training-guides/basic-install-guide/section_nova-compute-install.xml:213(para) +msgid "By default, the Ubuntu packages create an SQLite database." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_dashboard-system-reqs.xml:7(title) +msgid "System requirements" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_dashboard-system-reqs.xml:8(para) +msgid "Before you install the OpenStack dashboard, you must meet the following system requirements:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_dashboard-system-reqs.xml:12(para) +msgid "OpenStack Compute installation. Enable the Identity Service for user and project management." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_dashboard-system-reqs.xml:14(para) +msgid "Note the URLs of the Identity Service and Compute endpoints." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_dashboard-system-reqs.xml:18(para) +msgid "Identity Service user with sudo privileges. Because Apache does not serve content from a root user, users must run the dashboard as an Identity Service user with sudo privileges." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_dashboard-system-reqs.xml:24(para) +msgid "Python 2.6 or 2.7. The Python version must support Django. The Python version should run on any system, including Mac OS X. Installation prerequisites might differ by platform." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_dashboard-system-reqs.xml:30(para) +msgid "Then, install and configure the dashboard on a node that can contact the Identity Service." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_dashboard-system-reqs.xml:32(para) +msgid "Provide users with the following information so that they can access the dashboard through a web browser on their local machine:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_dashboard-system-reqs.xml:37(para) +msgid "The public IP address from which they can access the dashboard" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_dashboard-system-reqs.xml:41(para) +msgid "The user name and password with which they can access the dashboard" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_dashboard-system-reqs.xml:45(para) +msgid "Your web browser, and that of your users, must support HTML5 and have cookies and JavaScript enabled." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_dashboard-system-reqs.xml:49(para) +msgid "To use the VNC client with the dashboard, the browser must support HTML5 Canvas and HTML5 WebSockets." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_dashboard-system-reqs.xml:51(para) +msgid "For details about browsers that support noVNC, see https://github.com/kanaka/noVNC/blob/master/README.md, and https://github.com/kanaka/noVNC/wiki/Browser-support, respectively." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_launch-instance-nova.xml:7(title) +msgid "Launch an instance with legacy networking (nova-network)" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_launch-instance-nova.xml:9(title) ./doc/training-guides/basic-install-guide/section_launch-instance-neutron.xml:9(title) +msgid "To generate a keypair" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_launch-instance-nova.xml:10(para) ./doc/training-guides/basic-install-guide/section_launch-instance-neutron.xml:10(para) +msgid "Most cloud images support public key authentication rather than conventional user name/password authentication. Before launching an instance, you must generate a public/private key pair using and add the public key to your OpenStack environment." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_launch-instance-nova.xml:20(para) ./doc/training-guides/basic-install-guide/section_launch-instance-neutron.xml:20(para) +msgid "Generate a key pair:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_launch-instance-nova.xml:24(para) ./doc/training-guides/basic-install-guide/section_launch-instance-neutron.xml:24(para) +msgid "Add the public key to your OpenStack environment:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_launch-instance-nova.xml:31(para) ./doc/training-guides/basic-install-guide/section_launch-instance-neutron.xml:31(para) +msgid "Verify addition of the public key:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_launch-instance-nova.xml:41(title) ./doc/training-guides/basic-install-guide/section_launch-instance-neutron.xml:41(title) ./doc/training-guides/common/module001-ch006-overview-horizon-cli.xml:1701(para) +msgid "To launch an instance" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_launch-instance-nova.xml:42(para) ./doc/training-guides/basic-install-guide/section_launch-instance-neutron.xml:42(para) +msgid "To launch an instance, you must at least specify the flavor, image name, network, security group, key, and instance name." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_launch-instance-nova.xml:45(para) ./doc/training-guides/basic-install-guide/section_launch-instance-neutron.xml:45(para) +msgid "A flavor specifies a virtual resource allocation profile which includes processor, memory, and storage." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_launch-instance-nova.xml:47(para) ./doc/training-guides/basic-install-guide/section_launch-instance-neutron.xml:47(para) +msgid "List available flavors:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_launch-instance-nova.xml:58(para) ./doc/training-guides/basic-install-guide/section_launch-instance-neutron.xml:58(para) +msgid "Your first instance uses the m1.tiny flavor." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_launch-instance-nova.xml:61(para) ./doc/training-guides/basic-install-guide/section_launch-instance-neutron.xml:61(para) +msgid "You can also reference a flavor by ID." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_launch-instance-nova.xml:65(para) ./doc/training-guides/basic-install-guide/section_launch-instance-neutron.xml:65(para) +msgid "List available images:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_launch-instance-nova.xml:72(para) ./doc/training-guides/basic-install-guide/section_launch-instance-neutron.xml:72(para) +msgid "Your first instance uses the cirros-0.3.2-x86_64 image." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_launch-instance-nova.xml:76(para) ./doc/training-guides/basic-install-guide/section_launch-instance-neutron.xml:76(para) +msgid "List available networks:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_launch-instance-nova.xml:78(para) +msgid "You must source the admin tenant credentials for this step and then source the demo tenant credentials for the remaining steps." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_launch-instance-nova.xml:89(para) ./doc/training-guides/basic-install-guide/section_launch-instance-neutron.xml:84(para) +msgid "Your first instance uses the demo-net tenant network. However, you must reference this network using the ID instead of the name." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_launch-instance-nova.xml:94(para) ./doc/training-guides/basic-install-guide/section_launch-instance-neutron.xml:89(para) +msgid "List available security groups:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_launch-instance-nova.xml:101(para) +msgid "Your first instance uses the default security group. By default, this security group implements a firewall that blocks remote access to instances. If you would like to permit remote access to your instance, launch it and then configure remote access." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_launch-instance-nova.xml:109(para) ./doc/training-guides/basic-install-guide/section_launch-instance-neutron.xml:104(para) +msgid "Launch the instance:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_launch-instance-nova.xml:110(para) ./doc/training-guides/basic-install-guide/section_launch-instance-neutron.xml:105(para) +msgid "Replace DEMO_NET_ID with the ID of the demo-net tenant network." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_launch-instance-nova.xml:112(replaceable) ./doc/training-guides/basic-install-guide/section_launch-instance-neutron.xml:107(replaceable) +msgid "DEMO_NET_ID" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_launch-instance-nova.xml:113(replaceable) ./doc/training-guides/basic-install-guide/section_launch-instance-nova.xml:163(replaceable) ./doc/training-guides/basic-install-guide/section_launch-instance-neutron.xml:108(replaceable) ./doc/training-guides/basic-install-guide/section_launch-instance-neutron.xml:158(replaceable) +msgid "demo-instance1" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_launch-instance-nova.xml:146(para) ./doc/training-guides/basic-install-guide/section_launch-instance-neutron.xml:141(para) +msgid "Check the status of your instance:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_launch-instance-nova.xml:153(para) ./doc/training-guides/basic-install-guide/section_launch-instance-neutron.xml:148(para) +msgid "The status changes from BUILD to ACTIVE when your instance finishes the build process." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_launch-instance-nova.xml:159(title) ./doc/training-guides/basic-install-guide/section_launch-instance-neutron.xml:154(title) +msgid "To access your instance using a virtual console" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_launch-instance-nova.xml:161(para) ./doc/training-guides/basic-install-guide/section_launch-instance-neutron.xml:156(para) +msgid "Obtain a Virtual Network Computing (VNC) session URL for your instance and access it from a web browser:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_launch-instance-nova.xml:170(para) ./doc/training-guides/basic-install-guide/section_launch-instance-neutron.xml:165(para) +msgid "If your web browser runs on a host that cannot resolve the controller host name, you can replace controller with the IP address of the management interface on your controller node." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_launch-instance-nova.xml:175(para) ./doc/training-guides/basic-install-guide/section_launch-instance-neutron.xml:170(para) +msgid "The CirrOS image includes conventional user name/password authentication and provides these credentials at the login prompt. After logging into CirrOS, we recommend that you verify network connectivity using ." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_launch-instance-nova.xml:179(para) +msgid "Verify the demo-net network:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_launch-instance-nova.xml:193(title) ./doc/training-guides/basic-install-guide/section_launch-instance-neutron.xml:200(title) +msgid "To access your instance remotely" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_launch-instance-nova.xml:195(para) ./doc/training-guides/basic-install-guide/section_launch-instance-neutron.xml:202(para) +msgid "Add rules to the default security group:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_launch-instance-nova.xml:198(para) ./doc/training-guides/basic-install-guide/section_launch-instance-neutron.xml:205(para) +msgid "Permit ICMP (ping):" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_launch-instance-nova.xml:207(para) ./doc/training-guides/basic-install-guide/section_launch-instance-neutron.xml:214(para) +msgid "Permit secure shell (SSH) access:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_launch-instance-nova.xml:218(para) ./doc/training-guides/basic-install-guide/section_launch-instance-neutron.xml:259(para) +msgid "Verify network connectivity using from the controller node or any host on the external network:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_launch-instance-nova.xml:232(para) ./doc/training-guides/basic-install-guide/section_launch-instance-neutron.xml:273(para) +msgid "Access your instance using SSH from the controller node or any host on the external network:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_launch-instance-nova.xml:241(para) ./doc/training-guides/basic-install-guide/section_launch-instance-neutron.xml:282(para) +msgid "If your host does not contain the public/private key pair created in an earlier step, SSH prompts for the default password associated with the cirros user." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_launch-instance-nova.xml:247(para) ./doc/training-guides/basic-install-guide/section_launch-instance-neutron.xml:288(para) +msgid "If your instance does not launch or seem to work as you expect, see the OpenStack Operations Guide for more information or use one of the many other options to seek assistance. We want your environment to work!" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/ch_trove.xml:7(title) +msgid "Add the Database service" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/ch_trove.xml:8(para) +msgid "Use the Database module to create cloud database resources. The integrated project name is trove." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/ch_trove.xml:11(para) +msgid "This chapter is a work in progress. It may contain incorrect information, and will be updated frequently." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_nova-networking-compute-node.xml:8(para) +msgid "This section covers deployment of a simple flat network that provides IP addresses to your instances via DHCP. If your environment includes multiple compute nodes, the multi-host feature provides redundancy by spreading network functions across compute nodes." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_nova-networking-compute-node.xml:15(title) +msgid "To install legacy networking components" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_nova-networking-compute-node.xml:23(title) ./doc/training-guides/basic-install-guide/section_nova-networking-controller-node.xml:11(title) +msgid "To configure legacy networking" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_nova-networking-compute-node.xml:25(para) ./doc/training-guides/basic-install-guide/section_neutron-ml2-compute-node.xml:184(para) ./doc/training-guides/basic-install-guide/section_neutron-ml2-compute-node.xml:276(para) ./doc/training-guides/basic-install-guide/lab003-compute-node.xml:82(para) ./doc/training-guides/basic-install-guide/section_nova-networking-controller-node.xml:13(para) ./doc/training-guides/basic-install-guide/section_neutron-ml2-controller-node.xml:315(para) ./doc/training-guides/basic-install-guide/section_neutron-ml2-controller-node.xml:359(para) ./doc/training-guides/basic-install-guide/section_neutron-ml2-network-node.xml:186(para) ./doc/training-guides/basic-install-guide/section_neutron-ml2-network-node.xml:220(para) ./doc/training-guides/basic-install-guide/section_neutron-ml2-network-node.xml:257(para) ./doc/training-guides/basic-install-guide/section_neutron-ml2-network-node.xml:351(para) ./doc/training-guides/basic-install-guide/section_ceilometer-glance.xml:21(para) ./doc/training-guides/basic-install-guide/lab002-network-node.xml:76(para) +msgid "Run the following commands:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_nova-networking-compute-node.xml:26(para) ./doc/training-guides/basic-install-guide/section_nova-networking-compute-node.xml:59(para) +msgid "Replace INTERFACE_NAME with the actual interface name for the external network. For example, eth1 or ens224." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_nova-networking-compute-node.xml:57(para) ./doc/training-guides/basic-install-guide/section_nova-networking-controller-node.xml:20(para) +msgid "Edit the /etc/nova/nova.conf file and add the following keys to the [DEFAULT] section:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_nova-networking-compute-node.xml:82(para) +msgid "Start the services and configure them to start when the system boots:" +msgstr "" + #: ./doc/training-guides/basic-install-guide/lab000-important-terms.xml:6(title) msgid "Important terms" msgstr "" @@ -1803,6 +4133,232 @@ msgstr "" msgid "After the network interfaces file has been setup, you can switch to an SSH session by using an OpenSSH client to log in remotely to the required server node (Control, Network, Compute). Open a terminal on your host machine and run the following command: " msgstr "" +#: ./doc/training-guides/basic-install-guide/section_nova-verify.xml:8(para) +msgid "This section describes how to verify operation of the Compute service." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_nova-verify.xml:20(para) +msgid "List service components to verify successful launch of each process:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_nova-verify.xml:33(para) +msgid "This output should indicate four components enabled on the controller node one component enabled on the compute node." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_nova-verify.xml:38(para) +msgid "List images in the Image Service catalog to verify connectivity with the Identity service and Image Service:" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/training-guides/basic-install-guide/section_glance-install.xml:205(None) +msgid "@@image: 'figures/debconf-screenshots/glance-common_pipeline_flavor.png'; md5=78bef92c36a140ad042074f6345d8917" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_glance-install.xml:8(para) +msgid "This section describes how to install and configure the Image Service, code-named glance, on the controller node. For simplicity, this configuration stores images on the local file system." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_glance-install.xml:12(para) +msgid "This section assumes proper installation, configuration, and operation of the Identity service as described in and ." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_glance-install.xml:19(para) +msgid "Before you install and configure the Image Service, you must create a database and Identity service credentials including endpoints." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_glance-install.xml:30(para) +msgid "Create the glance database:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_glance-install.xml:34(para) +msgid "Grant proper access to the glance database:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_glance-install.xml:36(replaceable) ./doc/training-guides/basic-install-guide/section_glance-install.xml:37(replaceable) ./doc/training-guides/basic-install-guide/section_glance-install.xml:101(replaceable) ./doc/training-guides/basic-install-guide/section_glance-install.xml:149(replaceable) +msgid "GLANCE_DBPASS" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_glance-install.xml:38(para) +msgid "Replace GLANCE_DBPASS with a suitable password." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_glance-install.xml:56(para) +msgid "Create the glance user:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_glance-install.xml:57(replaceable) ./doc/training-guides/basic-install-guide/section_glance-install.xml:129(replaceable) ./doc/training-guides/basic-install-guide/section_glance-install.xml:165(replaceable) +msgid "GLANCE_PASS" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_glance-install.xml:58(para) +msgid "Replace GLANCE_PASS with a suitable password and EMAIL_ADDRESS with a suitable e-mail address." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_glance-install.xml:63(para) +msgid "Link the glance user to the service tenant and admin role:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_glance-install.xml:69(para) +msgid "Create the glance service:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_glance-install.xml:76(para) ./doc/training-guides/basic-install-guide/section_heat-install.xml:60(para) +msgid "Create the Identity service endpoints:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_glance-install.xml:85(title) ./doc/training-guides/basic-install-guide/section_glance-install.xml:183(title) +msgid "To install and configure the Image Service components" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_glance-install.xml:93(para) +msgid "Edit the /etc/glance/glance-api.conf file and complete the following actions:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_glance-install.xml:102(para) ./doc/training-guides/basic-install-guide/section_glance-install.xml:150(para) +msgid "Replace GLANCE_DBPASS with the password you chose for the Image Service database." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_glance-install.xml:118(para) ./doc/training-guides/basic-install-guide/section_glance-install.xml:154(para) +msgid "In the [keystone_authtoken] and [paste_deploy] sections, configure Identity service access:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_glance-install.xml:134(para) ./doc/training-guides/basic-install-guide/section_glance-install.xml:170(para) +msgid "Replace GLANCE_PASS with the password you chose for the glance user in the Identity service." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_glance-install.xml:141(para) +msgid "Edit the /etc/glance/glance-registry.conf file and complete the following actions:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_glance-install.xml:177(para) +msgid "Populate the Image Service database:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_glance-install.xml:199(para) +msgid "Select the keystone pipeline to configure the Image Service to use the Identity service:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_glance-install.xml:213(para) +msgid "Restart the Image Service services:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_glance-install.xml:218(para) +msgid "Start the Image Service services and configure them to start when the system boots:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_dashboard-install.xml:8(title) +msgid "Install the dashboard" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_dashboard-install.xml:9(para) +msgid "Before you can install and configure the dashboard, meet the requirements in ." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_dashboard-install.xml:13(para) +msgid "When you install only Object Storage and the Identity Service, even if you install the dashboard, it does not pull up projects and is unusable." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_dashboard-install.xml:17(para) +msgid "For more information about how to deploy the dashboard, see deployment topics in the developer documentation." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_dashboard-install.xml:24(para) +msgid "Install the dashboard on the node that can contact the Identity Service as root:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_dashboard-install.xml:30(title) +msgid "Note for Ubuntu users" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_dashboard-install.xml:32(para) +msgid "Remove the openstack-dashboard-ubuntu-theme package. This theme prevents translations, several menus as well as the network map from rendering correctly: " +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_dashboard-install.xml:41(title) +msgid "Note for Debian users" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_dashboard-install.xml:42(para) +msgid "To install the Apache package:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_dashboard-install.xml:44(para) +msgid "This command installs and configures Apache correctly, provided that the user asks for it during the debconf prompts. The default SSL certificate is self-signed, and it is probably wise to have it signed by a root Certificate Authority (CA)." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_dashboard-install.xml:53(para) +msgid "Modify the value of CACHES['default']['LOCATION'] in /etc/openstack-dashboard/local_settings.py/etc/openstack-dashboard/local_settings/srv/www/openstack-dashboard/openstack_dashboard/local/local_settings.py to match the ones set in /etc/memcached.conf/etc/sysconfig/memcached." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_dashboard-install.xml:65(para) +msgid "Open /etc/openstack-dashboard/local_settings.py/etc/openstack-dashboard/local_settings and look for this line:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_dashboard-install.xml:77(title) ./doc/training-guides/basic-install-guide/object-storage/section_object-storage-sys-requirements.xml:30(td) +msgid "Notes" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_dashboard-install.xml:80(para) +msgid "The address and port must match the ones set in /etc/memcached.conf/etc/sysconfig/memcached." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_dashboard-install.xml:85(para) +msgid "If you change the memcached settings, you must restart the Apache web server for the changes to take effect." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_dashboard-install.xml:90(para) +msgid "You can use options other than memcached option for session storage. Set the session back-end through the SESSION_ENGINE option." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_dashboard-install.xml:97(para) +msgid "To change the timezone, use the dashboard or edit the /etc/openstack-dashboard/local_settings/etc/openstack-dashboard/local_settings.py/srv/www/openstack-dashboard/openstack_dashboard/local/local_settings.py file." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_dashboard-install.xml:106(para) +msgid "Change the following parameter: TIME_ZONE = \"UTC\"" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_dashboard-install.xml:113(para) +msgid "Update the ALLOWED_HOSTS in local_settings.py to include the addresses you wish to access the dashboard from." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_dashboard-install.xml:117(para) +msgid "Edit /etc/openstack-dashboard/local_settings/etc/openstack-dashboard/local_settings.py/srv/www/openstack-dashboard/openstack_dashboard/local/local_settings.py:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_dashboard-install.xml:127(para) +msgid "This guide assumes that you are running the Dashboard on the controller node. You can easily run the dashboard on a separate server, by changing the appropriate settings in local_settings.py." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_dashboard-install.xml:132(para) +msgid "Edit /etc/openstack-dashboard/local_settings/etc/openstack-dashboard/local_settings.py/srv/www/openstack-dashboard/openstack_dashboard/local/local_settings.py and change OPENSTACK_HOST to the hostname of your Identity Service:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_dashboard-install.xml:144(para) +msgid "Setup Apache configuration: " +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_dashboard-install.xml:151(para) +msgid "By default, the openstack-dashboard package enables a database as session store. Before you continue, either change the session store set up as described in or finish the setup of the database session store as explained in ." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_dashboard-install.xml:161(para) +msgid "Ensure that the SELinux policy of the system is configured to allow network connections to the HTTP server." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_dashboard-install.xml:167(para) +msgid "Start the Apache web server and memcached:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_dashboard-install.xml:180(para) +msgid "You can now access the dashboard at http://controller/horizonhttps://controller/http://controller/dashboardhttp://controller." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_dashboard-install.xml:187(para) +msgid "Login with credentials for any user that you created with the OpenStack Identity Service." +msgstr "" + #. When image changes, this message will be marked fuzzy or untranslated for you. #. It doesn't matter what you translate it to: it's not used at all. #: ./doc/training-guides/basic-install-guide/lab000-virtualbox-basics.xml:206(None) @@ -2328,10 +4884,6 @@ msgstr "" msgid "Install SSH server when asked for custom software to install. The rest of the packages are not required and may come in the way of OpenStack packages - like DNS servers etc. (not necessary). Unless you know what you are doing." msgstr "" -#: ./doc/training-guides/basic-install-guide/lab000-virtualbox-basics.xml:453(title) -msgid "Network node" -msgstr "" - #: ./doc/training-guides/basic-install-guide/lab000-virtualbox-basics.xml:455(para) msgid "Create a new virtual machine, minimum RAM is 512 MB. The remainder can be left as default. The minimum HDD space is 8 GB." msgstr "" @@ -2388,10 +4940,6 @@ msgstr "" msgid "Install the SSH server when you are prompted for the custom software to install. The rest of the packages are not required and may come in the way of OpenStack packages - like DNS servers." msgstr "" -#: ./doc/training-guides/basic-install-guide/lab000-virtualbox-basics.xml:550(title) -msgid "Compute node" -msgstr "" - #: ./doc/training-guides/basic-install-guide/lab000-virtualbox-basics.xml:552(para) msgid "Create a virtual machine with at least 1,000 MB RAM and 8 GB HDD. For other settings, use the defaults." msgstr "" @@ -2440,6 +4988,375 @@ msgstr "" msgid "Congratulations! You are now setup with the infrastructure for deploying OpenStack. Just make sure that the Ubuntu Server is installed on the above setup Virtual Box instances. In the next section we will go through deploying OpenStack using the above created Virtual Box instances." msgstr "" +#: ./doc/training-guides/basic-install-guide/section_basics-networking.xml:8(title) +msgid "Networking" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_basics-networking.xml:9(para) +msgid "After installing the operating system on each node for the architecture that you choose to deploy, you must configure the network interfaces. We recommend that you disable any automated network management tools and manually edit the appropriate configuration files for your distribution. For more information on how to configure networking on your distribution, see the documentation.documentation.documentation.SLES 11 or openSUSE documentation." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_basics-networking.xml:32(title) +msgid "To disable NetworkManager and enable the network service:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_basics-networking.xml:43(title) +msgid "To disable NetworkManager:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_basics-networking.xml:45(para) +msgid "Use the YaST network module:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_basics-networking.xml:47(para) +msgid "For more information, see the SLES or the openSUSE documentation." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_basics-networking.xml:55(para) +msgid "RHEL and derivatives including CentOS and Scientific Linux enable a restrictive firewall by default. During this installation, certain steps will fail unless you alter or disable the firewall. For further information about securing your installation, refer to the OpenStack Security Guide." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_basics-networking.xml:62(para) +msgid "On Fedora, firewalld replaces iptables as the default firewall system. While you can use firewalld successfully, this guide references iptables for compatibility with other distributions." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_basics-networking.xml:68(title) +msgid "To disable firewalld and enable iptables:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_basics-networking.xml:77(para) +msgid "Proceed to network configuration for the example OpenStack Networking (neutron) or legacy networking (nova-network) architecture." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_cinder-verify.xml:7(title) +msgid "Verify the Block Storage installation" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_cinder-verify.xml:8(para) +msgid "To verify that the Block Storage is installed and configured properly, create a new volume." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_cinder-verify.xml:10(para) +msgid "For more information about how to manage volumes, see the OpenStack User Guide." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_cinder-verify.xml:15(para) +msgid "Source the demo-openrc.sh file:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_cinder-verify.xml:20(para) +msgid "Use the command to create a new volume:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_cinder-verify.xml:42(para) +msgid "Make sure that the volume has been correctly created with the command:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_cinder-verify.xml:50(para) +msgid "If the status value is not available, the volume creation failed. Check the log files in the /var/log/cinder/ directory on the controller and volume nodes to get information about the failure." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_cinder-node.xml:8(title) +msgid "Configure a Block Storage service node" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_cinder-node.xml:9(para) +msgid "After you configure the services on the controller node, configure a second system to be a Block Storage service node. This node contains the disk that serves volumes." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_cinder-node.xml:16(para) +msgid "Use the instructions in to configure the system. Note the following differences from the installation instructions for the controller node:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_cinder-node.xml:21(para) +msgid "Set the host name to block1 and use 10.0.0.41 as IP address on the management network interface. Ensure that the IP addresses and host names for both controller node and Block Storage service node are listed in the /etc/hosts file on each system." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_cinder-node.xml:29(para) +msgid "Follow the instructions in to synchronize from the controller node." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_cinder-node.xml:35(para) +msgid "Install the required LVM packages, if they are not already installed:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_cinder-node.xml:40(para) +msgid "Create the LVM physical and logical volumes. This guide assumes a second disk /dev/sdb that is used for this purpose:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_cinder-node.xml:47(para) +msgid "Add a filter entry to the devices section in the /etc/lvm/lvm.conf file to keep LVM from scanning devices used by virtual machines:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_cinder-node.xml:57(para) +msgid "You must add required physical volumes for LVM on the Block Storage host. Run the command to get a list or required volumes." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_cinder-node.xml:61(para) +msgid "Each item in the filter array starts with either an a for accept, or an r for reject. The physical volumes that are required on the Block Storage host have names that begin with a. The array must end with \"r/.*/\" to reject any device not listed." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_cinder-node.xml:68(para) +msgid "In this example, /dev/sda1 is the volume where the volumes for the operating system for the node reside, while /dev/sdb is the volume reserved for cinder-volumes." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_cinder-node.xml:74(para) +msgid "After you configure the operating system, install the appropriate packages for the Block Storage service:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_cinder-node.xml:81(para) +msgid "Respond to the debconf prompts about the database management, [keystone_authtoken] settings, and RabbitMQ credentials. Make sure to enter the same details as you did for your Block Storage service controller node." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_cinder-node.xml:89(para) +msgid "Another screen prompts you for the volume-group to use. The Debian package configuration script detects every active volume group and tries to use the first one it sees, provided that the lvm2 package was installed before Block Storage. This should be the case if you configured the volume group first, as this guide recommends." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_cinder-node.xml:96(para) +msgid "If you have only one active volume group on your Block Storage service node, you do not need to manually enter its name when you install the cinder-volume package because it is detected automatically. If no volume-group is available when you install cinder-common, you must use to manually configure or re-configure cinder-common." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_cinder-node.xml:108(para) +msgid "Copy the /etc/cinder/cinder.conf configuration file from the controller, or perform the following steps to set the keystone credentials:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_cinder-node.xml:144(para) +msgid "In the [DEFAULT] configuration section of the /etc/cinder/cinder.conf file, set these configuration keys and replace RABBIT_PASS with the password you chose for RabbitMQ:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_cinder-node.xml:158(para) +msgid "Configure Block Storage to use the RabbitMQ message broker. Replace RABBIT_PASS with the password you chose for RabbitMQ:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_cinder-node.xml:171(para) +msgid "Configure Block Storage to use your MySQL database. Edit the /etc/cinder/cinder.conf file and add the following key to the [database] section. Replace CINDER_DBPASS with the password you chose for the Block Storage database:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_cinder-node.xml:190(para) +msgid "Configure Block Storage to use the Image Service. Block Storage needs access to images to create bootable volumes. Edit the /etc/cinder/cinder.conf file and update the option in the [DEFAULT] section:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_cinder-node.xml:208(para) +msgid "Configure the iSCSI target service to discover Block Storage volumes. Add the following line to the beginning of the /etc/tgt/targets.conf file, if it is not already present:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_ceilometer-verify.xml:7(title) +msgid "Verify the Telemetry installation" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_ceilometer-verify.xml:8(para) +msgid "To test the Telemetry installation, download an image from the Image Service, and use the command to display usage statistics." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_ceilometer-verify.xml:13(para) +msgid "Use the ceilometer meter-list command to test the access to Telemetry:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_ceilometer-verify.xml:24(para) +msgid "Download an image from the Image Service:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_ceilometer-verify.xml:28(para) +msgid "Call the ceilometer meter-list command again to validate that the download has been detected and stored by the Telemetry:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_ceilometer-verify.xml:41(para) +msgid "You can now get usage statistics for the various meters:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/bk-openstack-basic-install-guide.xml:7(title) +msgid "OpenStack Installation Guide for Ubuntu 12.04/14.04 (LTS)" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/bk-openstack-basic-install-guide.xml:15(phrase) +msgid "Red Hat Enterprise Linux, CentOS, and Fedora" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/bk-openstack-basic-install-guide.xml:16(phrase) +msgid "Ubuntu 12.04/14.04 (LTS)" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/bk-openstack-basic-install-guide.xml:17(phrase) +msgid "openSUSE and SUSE Linux Enterprise Server" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/bk-openstack-basic-install-guide.xml:14(titleabbrev) +msgid "OpenStack Installation Guide for " +msgstr "" + +#: ./doc/training-guides/basic-install-guide/ch_ceilometer.xml:7(title) +msgid "Add the Telemetry module" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/ch_ceilometer.xml:8(para) +msgid "Telemetry provides a framework for monitoring and metering the OpenStack cloud. It is also known as the ceilometer project." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/ch_ceilometer.xml:20(para) +msgid "Your OpenStack environment now includes Telemetry. You can launch an instance or add more services to your environment in the previous chapters." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ml2-compute-node.xml:8(para) ./doc/training-guides/basic-install-guide/section_neutron-ml2-network-node.xml:8(para) +msgid "Before you install and configure OpenStack Networking, you must enable certain kernel networking functions." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ml2-compute-node.xml:11(title) ./doc/training-guides/basic-install-guide/section_neutron-ml2-network-node.xml:11(title) +msgid "To enable kernel networking functions" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ml2-compute-node.xml:13(para) +msgid "Edit the /etc/sysctl.conf file and add the following lines:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ml2-compute-node.xml:19(para) ./doc/training-guides/basic-install-guide/section_neutron-ml2-network-node.xml:20(para) +msgid "Implement the changes:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ml2-compute-node.xml:24(title) ./doc/training-guides/basic-install-guide/section_neutron-ml2-controller-node.xml:58(title) ./doc/training-guides/basic-install-guide/section_neutron-ml2-network-node.xml:25(title) +msgid "To install the Networking components" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ml2-compute-node.xml:31(para) +msgid "Ubuntu installations that use Linux kernel version 3.11 or later do not require the openvswitch-datapath-dkms package." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ml2-compute-node.xml:37(para) ./doc/training-guides/basic-install-guide/section_neutron-ml2-controller-node.xml:65(para) ./doc/training-guides/basic-install-guide/section_neutron-ml2-network-node.xml:40(para) +msgid "SUSE does not use a separate ML2 plug-in package." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ml2-compute-node.xml:42(title) ./doc/training-guides/basic-install-guide/section_neutron-ml2-network-node.xml:45(title) +msgid "To configure the Networking common components" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ml2-compute-node.xml:43(para) ./doc/training-guides/basic-install-guide/section_neutron-ml2-network-node.xml:46(para) +msgid "The Networking common component configuration includes the authentication mechanism, message broker, and plug-in." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ml2-compute-node.xml:55(para) ./doc/training-guides/basic-install-guide/section_neutron-ml2-compute-node.xml:78(para) ./doc/training-guides/basic-install-guide/section_neutron-ml2-controller-node.xml:132(para) ./doc/training-guides/basic-install-guide/section_neutron-ml2-controller-node.xml:155(para) ./doc/training-guides/basic-install-guide/section_neutron-ml2-network-node.xml:58(para) ./doc/training-guides/basic-install-guide/section_neutron-ml2-network-node.xml:81(para) +msgid "Configure Networking to use the Identity service for authentication:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ml2-compute-node.xml:73(para) ./doc/training-guides/basic-install-guide/section_neutron-ml2-compute-node.xml:100(para) ./doc/training-guides/basic-install-guide/section_neutron-ml2-compute-node.xml:297(para) ./doc/training-guides/basic-install-guide/section_neutron-ml2-compute-node.xml:312(para) ./doc/training-guides/basic-install-guide/section_neutron-ml2-controller-node.xml:134(para) ./doc/training-guides/basic-install-guide/section_neutron-ml2-controller-node.xml:167(para) ./doc/training-guides/basic-install-guide/section_neutron-ml2-controller-node.xml:360(para) ./doc/training-guides/basic-install-guide/section_neutron-ml2-controller-node.xml:394(para) ./doc/training-guides/basic-install-guide/section_neutron-ml2-network-node.xml:60(para) ./doc/training-guides/basic-install-guide/section_neutron-ml2-network-node.xml:94(para) +msgid "Replace NEUTRON_PASS with the password you chose for the neutron user in the Identity service." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ml2-compute-node.xml:82(para) ./doc/training-guides/basic-install-guide/section_neutron-ml2-controller-node.xml:159(para) ./doc/training-guides/basic-install-guide/section_neutron-ml2-network-node.xml:85(para) +msgid "Edit the /etc/neutron/neutron.conf file and add the following key to the [DEFAULT] section:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ml2-compute-node.xml:89(para) ./doc/training-guides/basic-install-guide/section_neutron-ml2-controller-node.xml:165(para) ./doc/training-guides/basic-install-guide/section_neutron-ml2-network-node.xml:92(para) +msgid "Add the following keys to the [keystone_authtoken] section:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ml2-compute-node.xml:107(para) ./doc/training-guides/basic-install-guide/section_neutron-ml2-compute-node.xml:121(para) ./doc/training-guides/basic-install-guide/section_neutron-ml2-controller-node.xml:183(para) ./doc/training-guides/basic-install-guide/section_neutron-ml2-controller-node.xml:197(para) ./doc/training-guides/basic-install-guide/section_neutron-ml2-network-node.xml:110(para) ./doc/training-guides/basic-install-guide/section_neutron-ml2-network-node.xml:124(para) +msgid "Configure Networking to use the message broker:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ml2-compute-node.xml:124(para) ./doc/training-guides/basic-install-guide/section_neutron-ml2-compute-node.xml:158(para) ./doc/training-guides/basic-install-guide/section_neutron-ml2-controller-node.xml:200(para) ./doc/training-guides/basic-install-guide/section_neutron-ml2-controller-node.xml:242(para) ./doc/training-guides/basic-install-guide/section_neutron-ml2-controller-node.xml:290(para) ./doc/training-guides/basic-install-guide/section_neutron-ml2-network-node.xml:127(para) ./doc/training-guides/basic-install-guide/section_neutron-ml2-network-node.xml:161(para) +msgid "Edit the /etc/neutron/neutron.conf file and add the following keys to the [DEFAULT] section:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ml2-compute-node.xml:140(para) ./doc/training-guides/basic-install-guide/section_neutron-ml2-compute-node.xml:154(para) ./doc/training-guides/basic-install-guide/section_neutron-ml2-controller-node.xml:272(para) ./doc/training-guides/basic-install-guide/section_neutron-ml2-controller-node.xml:286(para) ./doc/training-guides/basic-install-guide/section_neutron-ml2-network-node.xml:143(para) ./doc/training-guides/basic-install-guide/section_neutron-ml2-network-node.xml:157(para) +msgid "Configure Networking to use the Modular Layer 2 (ML2) plug-in and associated services:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ml2-compute-node.xml:147(para) ./doc/training-guides/basic-install-guide/section_neutron-ml2-compute-node.xml:168(para) ./doc/training-guides/basic-install-guide/section_neutron-ml2-network-node.xml:150(para) ./doc/training-guides/basic-install-guide/section_neutron-ml2-network-node.xml:171(para) +msgid "To assist with troubleshooting, add verbose = True to the [DEFAULT] section in the /etc/neutron/neutron.conf file." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ml2-compute-node.xml:179(title) ./doc/training-guides/basic-install-guide/section_neutron-ml2-controller-node.xml:309(title) ./doc/training-guides/basic-install-guide/section_neutron-ml2-network-node.xml:346(title) +msgid "To configure the Modular Layer 2 (ML2) plug-in" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ml2-compute-node.xml:180(para) +msgid "The ML2 plug-in uses the Open vSwitch (OVS) mechanism (agent) to build the virtual networking framework for instances." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ml2-compute-node.xml:194(replaceable) ./doc/training-guides/basic-install-guide/section_neutron-ml2-compute-node.xml:234(replaceable) ./doc/training-guides/basic-install-guide/section_neutron-ml2-network-node.xml:367(replaceable) ./doc/training-guides/basic-install-guide/section_neutron-ml2-network-node.xml:401(replaceable) +msgid "INSTANCE_TUNNELS_INTERFACE_IP_ADDRESS" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ml2-compute-node.xml:203(para) +msgid "Replace INSTANCE_TUNNELS_INTERFACE_IP_ADDRESS with the IP address of the instance tunnels network interface on your compute node. This guide uses 10.0.1.31 for the IP address of the instance tunnels network interface on the first compute node." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ml2-compute-node.xml:212(para) +msgid "Edit the /etc/neutron/plugins/ml2/ml2_conf.ini file and add the following keys to the [ml2] section:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ml2-compute-node.xml:221(para) ./doc/training-guides/basic-install-guide/section_neutron-ml2-network-node.xml:388(para) +msgid "Add the following keys to the [ml2_type_gre] section:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ml2-compute-node.xml:226(para) ./doc/training-guides/basic-install-guide/section_neutron-ml2-network-node.xml:393(para) +msgid "Add the [ovs] section and the following keys to it:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ml2-compute-node.xml:228(para) +msgid "Replace INSTANCE_TUNNELS_INTERFACE_IP_ADDRESS with the IP address of the instance tunnels network interface on your compute node." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ml2-compute-node.xml:237(para) ./doc/training-guides/basic-install-guide/section_neutron-ml2-controller-node.xml:345(para) ./doc/training-guides/basic-install-guide/section_neutron-ml2-network-node.xml:404(para) +msgid "Add the [securitygroup] section and the following keys to it:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ml2-compute-node.xml:246(title) ./doc/training-guides/basic-install-guide/section_neutron-ml2-network-node.xml:413(title) +msgid "To configure the Open vSwitch (OVS) service" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ml2-compute-node.xml:247(para) +msgid "The OVS service provides the underlying virtual networking framework for instances." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ml2-compute-node.xml:250(para) ./doc/training-guides/basic-install-guide/section_neutron-ml2-compute-node.xml:256(para) ./doc/training-guides/basic-install-guide/section_neutron-ml2-network-node.xml:424(para) ./doc/training-guides/basic-install-guide/section_neutron-ml2-network-node.xml:430(para) +msgid "Start the OVS service and configure it to start when the system boots:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ml2-compute-node.xml:262(para) ./doc/training-guides/basic-install-guide/section_neutron-ml2-compute-node.xml:266(para) ./doc/training-guides/basic-install-guide/section_neutron-ml2-network-node.xml:436(para) ./doc/training-guides/basic-install-guide/section_neutron-ml2-network-node.xml:440(para) +msgid "Restart the OVS service:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ml2-compute-node.xml:271(title) ./doc/training-guides/basic-install-guide/section_neutron-ml2-controller-node.xml:354(title) +msgid "To configure Compute to use Networking" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ml2-compute-node.xml:272(para) ./doc/training-guides/basic-install-guide/section_neutron-ml2-controller-node.xml:355(para) +msgid "By default, most distributions configure Compute to use legacy networking. You must reconfigure Compute to manage networks through Networking." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ml2-compute-node.xml:301(para) ./doc/training-guides/basic-install-guide/section_neutron-ml2-compute-node.xml:328(para) ./doc/training-guides/basic-install-guide/section_neutron-ml2-controller-node.xml:384(para) ./doc/training-guides/basic-install-guide/section_neutron-ml2-controller-node.xml:410(para) +msgid "By default, Compute uses an internal firewall service. Since Networking includes a firewall service, you must disable the Compute firewall service by using the nova.virt.firewall.NoopFirewallDriver firewall driver." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ml2-compute-node.xml:309(para) ./doc/training-guides/basic-install-guide/section_neutron-ml2-controller-node.xml:392(para) +msgid "Edit the /etc/nova/nova.conf and add the following keys to the [DEFAULT] section:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ml2-compute-node.xml:337(title) ./doc/training-guides/basic-install-guide/section_neutron-ml2-network-node.xml:466(title) +msgid "To finalize the installation" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ml2-compute-node.xml:339(para) ./doc/training-guides/basic-install-guide/section_neutron-ml2-network-node.xml:468(para) +msgid "The Networking service initialization scripts expect a symbolic link /etc/neutron/plugin.ini pointing to the configuration file associated with your chosen plug-in. Using the ML2 plug-in, for example, the symbolic link must point to /etc/neutron/plugins/ml2/ml2_conf.ini. If this symbolic link does not exist, create it using the following commands:" +msgstr "" + +#. https://bugzilla.redhat.com/show_bug.cgi?id=1087647 +#: ./doc/training-guides/basic-install-guide/section_neutron-ml2-compute-node.xml:349(para) ./doc/training-guides/basic-install-guide/section_neutron-ml2-network-node.xml:478(para) +msgid "Due to a packaging bug, the Open vSwitch agent initialization script explicitly looks for the Open vSwitch plug-in configuration file rather than a symbolic link /etc/neutron/plugin.ini pointing to the ML2 plug-in configuration file. Run the following commands to resolve this issue:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ml2-compute-node.xml:359(para) ./doc/training-guides/basic-install-guide/section_neutron-ml2-network-node.xml:488(para) +msgid "The Networking service initialization scripts expect the variable NEUTRON_PLUGIN_CONF in the /etc/sysconfig/neutron file to reference the configuration file associated with your chosen plug-in. Using ML2, for example, edit the /etc/sysconfig/neutron file and add the following:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ml2-compute-node.xml:374(para) +msgid "Start the Open vSwitch (OVS) agent and configure it to start when the system boots:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ml2-compute-node.xml:382(para) +msgid "Restart the Open vSwitch (OVS) agent:" +msgstr "" + #: ./doc/training-guides/basic-install-guide/lab003-compute-node.xml:25(para) ./doc/training-guides/basic-install-guide/lab002-network-node.xml:22(para) msgid "Vboxnet0, Vboxnet1, Vboxnet2 - are virtual networks setup up by virtual box with your host machine. This is the way your host can communicate with the virtual machines. These networks are in turn used by virtual box VM’s for OpenStack networks, so that OpenStack’s services can communicate with each other." msgstr "" @@ -2452,6 +5369,10 @@ msgstr "" msgid "Preparing Ubuntu 12.04" msgstr "" +#: ./doc/training-guides/basic-install-guide/lab003-compute-node.xml:38(para) ./doc/training-guides/basic-install-guide/lab002-network-node.xml:32(para) +msgid "After you install Ubuntu Server, go in sudo mode" +msgstr "" + #: ./doc/training-guides/basic-install-guide/lab003-compute-node.xml:59(para) ./doc/training-guides/basic-install-guide/lab002-network-node.xml:53(para) msgid "Install NTP and other services:" msgstr "" @@ -2464,10 +5385,6 @@ msgstr "" msgid "Enable IP Forwarding by adding the following to /etc/sysctl.conf" msgstr "" -#: ./doc/training-guides/basic-install-guide/lab003-compute-node.xml:82(para) ./doc/training-guides/basic-install-guide/lab002-network-node.xml:76(para) -msgid "Run the following commands:" -msgstr "" - #: ./doc/training-guides/basic-install-guide/lab003-compute-node.xml:94(para) msgid "Install KVM:" msgstr "" @@ -2540,6 +5457,1276 @@ msgstr "" msgid "List nova services (Check for the Smiley Faces to know if the services are running):" msgstr "" +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/training-guides/basic-install-guide/section_basics-networking-nova.xml:27(None) ./doc/training-guides/basic-install-guide/ch_overview.xml:134(None) +msgid "@@image: 'figures/installguide_arch-nova.png'; md5=da24b356516c960a33ab2b4b72840774" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_basics-networking-nova.xml:8(title) ./doc/training-guides/basic-install-guide/ch_networking.xml:34(title) +msgid "Legacy networking (nova-network)" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_basics-networking-nova.xml:9(para) +msgid "The example architecture with legacy networking (nova-network) requires a controller node and at least one compute node. The controller node contains one network interface on the management network. The compute node contains one network interface on the management network and one on the external network." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_basics-networking-nova.xml:16(para) +msgid "Network interface names vary by distribution. Traditionally, interfaces use \"eth\" followed by a sequential number. To cover all variations, this guide simply refers to the first interface as the interface with the lowest number and the second interface as the interface with the highest number." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_basics-networking-nova.xml:23(title) ./doc/training-guides/basic-install-guide/ch_overview.xml:130(title) +msgid "Two-node architecture with legacy networking (nova-network)" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_basics-networking-nova.xml:90(para) +msgid "The external interface uses a special configuration without an IP address assigned to it. Configure the second interface as the external interface:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_basics-networking-nova.xml:93(para) +msgid "Replace INTERFACE_NAME with the actual interface name. For example, eth1 or ens224." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_trove-install.xml:7(title) +msgid "Install the Database service" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_trove-install.xml:8(para) +msgid "This procedure installs the Database module on the controller node." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_trove-install.xml:12(para) +msgid "This chapter assumes that you already have a working OpenStack environment with at least the following components installed: Compute, Image Service, Identity." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_trove-install.xml:17(title) +msgid "Ubuntu 14.04 Only" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_trove-install.xml:18(para) +msgid "The Database module is only available under Ubuntu 14.04. Packages are not available for 12.04, or via the Ubuntu Cloud Archive." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_trove-install.xml:22(para) +msgid "To install the Database module on the controller:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_trove-install.xml:25(para) +msgid "Install required packages:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_trove-install.xml:32(para) +msgid "Respond to the prompts for database management and [keystone_authtoken] settings, and API endpoint registration. The command runs automatically." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_trove-install.xml:41(para) +msgid "Prepare OpenStack:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_trove-install.xml:44(para) +msgid "Source the admin-openrc.sh file." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_trove-install.xml:49(para) +msgid "Create a trove user that Compute uses to authenticate with the Identity service. Use the service tenant and give the user the admin role:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_trove-install.xml:54(replaceable) +msgid "TROVE_PASS" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_trove-install.xml:55(replaceable) +msgid "trove@example.com" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_trove-install.xml:63(para) +msgid "Edit the following configuration files, taking the below actions for each file:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_trove-install.xml:66(filename) +msgid "trove.conf" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_trove-install.xml:67(filename) +msgid "trove-taskmanager.conf" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_trove-install.xml:68(filename) +msgid "trove-conductor.conf" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_trove-install.xml:72(para) +msgid "Edit the [DEFAULT] section of each file and set appropriate values for the OpenStack service URLs, logging and messaging configuration, and SQL connections:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_trove-install.xml:82(literal) +msgid "TROVE_DBPASS" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_trove-install.xml:87(para) +msgid "Configure the Database module to use the RabbitMQ message broker by setting the rabbit_password in the [DEFAULT] configuration group of each file:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_trove-install.xml:97(para) +msgid "Set these configuration keys to configure the Database module to use the RabbitMQ message broker:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_trove-install.xml:122(para) +msgid "Edit the [filter:authtoken] section of the api-paste.ini file so it matches the listing shown below:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_trove-install.xml:136(para) +msgid "Edit the trove.conf file so it includes appropriate values for the default datastore and network label regex as shown below:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_trove-install.xml:149(para) +msgid "Edit the trove-taskmanager.conf file so it includes the appropriate service credentials required to connect to the OpenStack Compute service as shown below:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_trove-install.xml:165(para) +msgid "Prepare the trove admin database:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_trove-install.xml:173(para) +msgid "Prepare the Database service:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_trove-install.xml:176(para) +msgid "Initialize the database:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_trove-install.xml:180(para) ./doc/training-guides/basic-install-guide/section_trove-install.xml:188(para) +msgid "Create a datastore. You need to create a separate datastore for each type of database you want to use, for example, MySQL, MongoDB, Cassandra. This example shows you how to create a datastore for a MySQL database:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_trove-install.xml:194(para) +msgid "Create a trove image." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_trove-install.xml:195(para) +msgid "Create an image for the type of database you want to use, for example, MySQL, MongoDB, Cassandra." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_trove-install.xml:197(para) +msgid "This image must have the trove guest agent installed, and it must have the trove-guestagent.conf file configured to connect to your OpenStack environment. To correctly configure the trove-guestagent.conf file, follow these steps on the guest instance you are using to build your image:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_trove-install.xml:206(para) +msgid "Add the following lines to trove-guestagent.conf:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_trove-install.xml:218(para) +msgid "Update the datastore to use the new image, using the command." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_trove-install.xml:220(para) +msgid "This example shows you how to create a MySQL 5.5 datastore:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_trove-install.xml:222(replaceable) +msgid "glance_image_ID" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_trove-install.xml:226(para) +msgid "You must register the Database module with the Identity service so that other OpenStack services can locate it. Register the service and specify the endpoint:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_trove-install.xml:239(para) +msgid "Start Database services and configure them to start when the system boots:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_trove-install.xml:242(para) +msgid "Restart Database services:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/ch_cinder.xml:7(title) +msgid "Add the Block Storage service" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/ch_cinder.xml:8(para) +msgid "The OpenStack Block Storage service works through the interaction of a series of daemon processes named cinder-* that reside persistently on the host machine or machines. You can run the binaries from a single node or across multiple nodes. You can also run them on the same node as other OpenStack services. The following sections introduce Block Storage service components and concepts and show you how to configure and install the Block Storage service." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/ch_cinder.xml:22(para) +msgid "Your OpenStack environment now includes Block Storage. You can launch an instance or add more services to your environment in the following chapters." +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/training-guides/basic-install-guide/section_debconf-rabbitmq.xml:16(None) +msgid "@@image: 'figures/debconf-screenshots/rabbitmq-host.png'; md5=5353ad857884a2d31847cf82efbdc6b6" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/training-guides/basic-install-guide/section_debconf-rabbitmq.xml:23(None) +msgid "@@image: 'figures/debconf-screenshots/rabbitmq-user.png'; md5=33a3c1182e79ed65f1b1b63f2156792c" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/training-guides/basic-install-guide/section_debconf-rabbitmq.xml:30(None) +msgid "@@image: 'figures/debconf-screenshots/rabbitmq-password.png'; md5=6385185200d20e96b6316ae15ae1255d" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_debconf-rabbitmq.xml:7(title) +msgid "RabbitMQ credentials parameters" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_debconf-rabbitmq.xml:8(para) +msgid "For every package that must connect to a Messaging Server, the Debian package enables you to configure the IP address for that server and the user name and password that is used to connect. The following example shows configuration with the ceilometer-common package:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_debconf-rabbitmq.xml:34(para) +msgid "These debconf screens appear in: ceilometer-common, cinder-common, glance-common, heat-common, neutron-common and nova-common." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_debconf-rabbitmq.xml:41(para) +msgid "This will configure the below directives (example from nova.conf):" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_debconf-rabbitmq.xml:47(para) +msgid "The other directives concerning RabbitMQ will stay untouched." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_debconf-concepts.xml:8(title) +msgid "debconf concepts" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_debconf-concepts.xml:9(para) +msgid "This chapter explains how to use the Debian debconf and dbconfig-common packages to configure OpenStack services. These packages enable users to perform configuration tasks. When users install OpenStack packages, debconf prompts the user for responses, which seed the contents of configuration files associated with that package. After package installation, users can update the configuration of a package by using the program." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_debconf-concepts.xml:19(para) +msgid "If you are familiar with these packages and pre-seeding, you can proceed to ." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_debconf-concepts.xml:22(title) +msgid "The Debian packages" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_debconf-concepts.xml:23(para) +msgid "The rules described here are from the Debian Policy Manual. If any rule described in this chapter is not respected, you have found a serious bug that must be fixed." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_debconf-concepts.xml:28(para) +msgid "When you install or upgrade a Debian package, all configuration file values are preserved. Using the debconf database as a registry is considered a bug in Debian. If you edit something in any OpenStack configuration file, the debconf package reads that value when it prepares to prompt the user. For example, to change the log in name for the RabbitMQ messaging queue for a service, you can edit its value in the corresponding configuration file." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_debconf-concepts.xml:37(para) +msgid "To opt out of using the debconf package, run the command and select non-interactive mode:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_debconf-concepts.xml:42(para) +msgid "Then, debconf does not prompt you." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_debconf-concepts.xml:44(para) +msgid "Another way to disable the debconf package is to prefix the command with DEBIAN_FRONTEND=noninteractive, as follows:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_debconf-concepts.xml:50(para) +msgid "If you configure a package with debconf incorrectly, you can re-configure it, as follows:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_debconf-concepts.xml:53(replaceable) +msgid "PACKAGE-NAME" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_debconf-concepts.xml:54(para) +msgid "This calls the post-installation script for the PACKAGE-NAME package after the user responds to all prompts. If you cannot install a Debian package in a non-interactive way, you have found a release-critical bug in Debian. Report it to the Debian bug tracking system." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_debconf-concepts.xml:59(para) +msgid "Generally, the -common packages install the configuration files. For example, the glance-common package installs the glance-api.conf and glance-registry.conf files. So, for the Image Service, you must re-configure the glance-common package. The same applies for cinder-common, nova-common, and heat-common packages." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_debconf-concepts.xml:69(para) +msgid "In debconf, the higher the priority for a screen, the greater the chance that the user sees that screen. If a debconf screen has medium priority and you configure the Debian system to show only critical prompts, which is the default in Debian, the user does not see that debconf screen. Instead, the default for the related package is used. In the Debian OpenStack packages, a number of debconf screens are set with medium priority. Consequently, if you want to respond to all debconf screens from the Debian OpenStack packages, you must run the following command and select the medium priority before you install any packages:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_debconf-concepts.xml:88(para) +msgid "The packages do not require pre-depends. If dbconfig-common is already installed on the system, the user sees all prompts. However, you cannot define the order in which the debconf screens appear. The user must make sense of it even if the prompts appear in an illogical order." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_nova-networking-controller-node.xml:8(para) +msgid "Legacy networking primarily involves compute nodes. However, you must configure the controller node to use it." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/ch_nova.xml:8(title) +msgid "Add the Compute service" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/ch_networking.xml:7(title) +msgid "Add a networking component" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/ch_networking.xml:8(para) +msgid "This chapter explains how to install and configure either OpenStack Networking (neutron) or the legacy nova-network networking service. The nova-network service enables you to deploy one network type per instance and is suitable for basic network functionality. OpenStack Networking enables you to deploy multiple network types per instance and includes plug-ins for a variety of products that support virtual networking." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/ch_networking.xml:18(para) +msgid "For more information, see the Networking chapter of the OpenStack Cloud Administrator Guide." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/ch_networking.xml:26(title) +msgid "Modular Layer 2 (ML2) plug-in" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/ch_networking.xml:41(para) +msgid "Your OpenStack environment now includes the core components necessary to launch a basic instance. You can launch an instance or add more OpenStack services to your environment." +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/training-guides/basic-install-guide/section_neutron-ml2-controller-node.xml:97(None) +msgid "@@image: 'figures/debconf-screenshots/neutron_1_plugin_selection.png'; md5=adf41c33778a691a560b7098908792db" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ml2-controller-node.xml:10(para) +msgid "Before you configure OpenStack Networking (neutron), you must create a database and Identity service credentials including a user and service." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ml2-controller-node.xml:14(para) +msgid "Connect to the database as the root user, create the neutron database, and grant the proper access to it:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ml2-controller-node.xml:17(para) ./doc/training-guides/basic-install-guide/section_neutron-ml2-controller-node.xml:111(para) +msgid "Replace NEUTRON_DBPASS with a suitable password." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ml2-controller-node.xml:22(replaceable) ./doc/training-guides/basic-install-guide/section_neutron-ml2-controller-node.xml:24(replaceable) ./doc/training-guides/basic-install-guide/section_neutron-ml2-controller-node.xml:114(replaceable) ./doc/training-guides/basic-install-guide/section_neutron-ml2-controller-node.xml:127(replaceable) ./doc/training-guides/basic-install-guide/section_neutron-ovs-controller-node.xml:39(replaceable) ./doc/training-guides/basic-install-guide/section_neutron-ovs-controller-node.xml:41(replaceable) ./doc/training-guides/basic-install-guide/section_neutron-ovs-controller-node.xml:72(replaceable) ./doc/training-guides/basic-install-guide/section_neutron-ovs-controller-node.xml:82(replaceable) +msgid "NEUTRON_DBPASS" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ml2-controller-node.xml:27(para) +msgid "Create Identity service credentials for Networking:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ml2-controller-node.xml:30(para) +msgid "Create the neutron user:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ml2-controller-node.xml:31(para) +msgid "Replace NEUTRON_PASS with a suitable password and neutron@example.com with a suitable e-mail address." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ml2-controller-node.xml:34(replaceable) ./doc/training-guides/basic-install-guide/section_neutron-ovs-controller-node.xml:47(replaceable) +msgid "neutron@example.com" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ml2-controller-node.xml:37(para) +msgid "Link the neutron user to the service tenant and admin role:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ml2-controller-node.xml:43(para) +msgid "Create the neutron service:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ml2-controller-node.xml:47(para) +msgid "Create the service endpoint:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ml2-controller-node.xml:68(para) +msgid "Debian does not use a separate ML2 plug-in package." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ml2-controller-node.xml:73(title) +msgid "To configure the Networking server component" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ml2-controller-node.xml:74(para) +msgid "The Networking server component configuration includes the database, authentication mechanism, message broker, topology change notifier, and plug-in." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ml2-controller-node.xml:88(para) +msgid "During the installation, you will also be prompted for which Networking plug-in to use. This will automatically fill the directive in the /etc/neutron/neutron.conf file." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ml2-controller-node.xml:101(para) +msgid "If the ML2 plug-in is selected, then the option will be filled with neutron.plugins.ml2.plugin.Ml2Plugin, which is the full class name for the ML2 plug-in. In Debian, you cannot (yet) use the short names for the plug-ins. The and options are filled with the appropriate values by default, so it is fine to not touch them." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ml2-controller-node.xml:110(para) ./doc/training-guides/basic-install-guide/section_neutron-ml2-controller-node.xml:117(para) +msgid "Configure Networking to use the database:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ml2-controller-node.xml:120(para) +msgid "Edit the /etc/neutron/neutron.conf file and add the following key to the [database] section:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ml2-controller-node.xml:123(para) +msgid "Replace NEUTRON_DBPASS with the password you chose for the database." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ml2-controller-node.xml:215(para) ./doc/training-guides/basic-install-guide/section_neutron-ml2-controller-node.xml:233(para) +msgid "Configure Networking to notify Compute about network topology changes:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ml2-controller-node.xml:235(para) +msgid "Replace SERVICE_TENANT_ID with the service tenant identifier (id) in the Identity service and NOVA_PASS with the password you chose for the nova user in the Identity service." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ml2-controller-node.xml:251(replaceable) +msgid "SERVICE_TENANT_ID" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ml2-controller-node.xml:257(para) +msgid "To obtain the service tenant identifier (id):" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ml2-controller-node.xml:279(para) ./doc/training-guides/basic-install-guide/section_neutron-ml2-controller-node.xml:299(para) +msgid "We recommend adding verbose = True to the [DEFAULT] section in /etc/neutron/neutron.conf to assist with troubleshooting." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ml2-controller-node.xml:310(para) +msgid "The ML2 plug-in uses the Open vSwitch (OVS) mechanism (agent) to build the virtual networking framework for instances. However, the controller node does not need the OVS agent or service because it does not handle instance network traffic." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ml2-controller-node.xml:330(para) +msgid "Edit the /etc/neutron/plugins/ml2/ml2_conf.ini file:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ml2-controller-node.xml:333(para) ./doc/training-guides/basic-install-guide/section_neutron-ml2-network-node.xml:381(para) +msgid "Add the following keys to the [ml2] section:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ml2-controller-node.xml:340(para) +msgid "Add the following key to the [ml2_type_gre] section:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ml2-controller-node.xml:421(para) +msgid "The Networking service initialization scripts expect a symbolic link /etc/neutron/plugin.ini pointing to the configuration file associated with your chosen plug-in. Using ML2, for example, the symbolic link must point to /etc/neutron/plugins/ml2/ml2_conf.ini. If this symbolic link does not exist, create it using the following commands:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ml2-controller-node.xml:431(para) +msgid "The Networking service initialization scripts expect the variable NEUTRON_PLUGIN_CONF in file /etc/sysconfig/neutron to reference the configuration file associated with your chosen plug-in. Using ML2, for example, edit the /etc/sysconfig/neutron file and add the following:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ml2-controller-node.xml:450(para) ./doc/training-guides/basic-install-guide/section_neutron-ovs-controller-node.xml:324(para) +msgid "Start the Networking service and configure it to start when the system boots:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ml2-controller-node.xml:458(para) +msgid "Restart the Networking service:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_launch-instance-neutron.xml:7(title) +msgid "Launch an instance with OpenStack Networking (neutron)" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_launch-instance-neutron.xml:96(para) +msgid "Your first instance uses the default security group. By default, this security group implements a firewall that blocks remote access to instances. If you would like to permit remote access to your instance, launch it and then configure remote access." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_launch-instance-neutron.xml:174(para) +msgid "Verify the demo-net tenant network gateway:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_launch-instance-neutron.xml:186(para) +msgid "Verify the ext-net external network:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_launch-instance-neutron.xml:225(para) +msgid "Create a floating IP address on the ext-net external network:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_launch-instance-neutron.xml:243(para) +msgid "Associate the floating IP address with your instance:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_launch-instance-neutron.xml:250(para) +msgid "Check the status of your floating IP address:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_nova-compute-install.xml:7(title) +msgid "Install and configure a compute node" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_nova-compute-install.xml:8(para) +msgid "This section describes how to install and configure the Compute service on a compute node. The service supports several hypervisors to deploy instances or VMs. For simplicity, this configuration uses the QEMU hypervisor with the KVM extension on compute nodes that support hardware acceleration for virtual machines. On legacy hardware, this configuration uses the generic QEMU hypervisor. You can follow these instructions with minor modifications to horizontally scale your environment with additional compute nodes." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_nova-compute-install.xml:22(title) ./doc/training-guides/basic-install-guide/section_nova-compute-install.xml:123(title) +msgid "To install and configure the Compute hypervisor components" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_nova-compute-install.xml:55(para) +msgid "In the [keystone_authtoken] section, configure Identity service access:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_nova-compute-install.xml:72(para) +msgid "In the [DEFAULT] section, configure the my_ip key:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_nova-compute-install.xml:76(replaceable) ./doc/training-guides/basic-install-guide/section_nova-compute-install.xml:91(replaceable) +msgid "MANAGEMENT_INTERFACE_IP_ADDRESS" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_nova-compute-install.xml:77(para) ./doc/training-guides/basic-install-guide/section_nova-compute-install.xml:98(para) +msgid "Replace MANAGEMENT_INTERFACE_IP_ADDRESS with the IP address of the management network interface on your first compute node, typically 10.0.0.31 in the example architecture." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_nova-compute-install.xml:85(para) +msgid "In the [DEFAULT] section, enable and configure remote console access:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_nova-compute-install.xml:93(para) +msgid "The server component listens on all IP addresses and the proxy component only listens on the management interface IP address of the compute node. The base URL indicates the location where you can use a web browser to access remote consoles of instances on this compute node." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_nova-compute-install.xml:105(para) +msgid "If the web browser to access remote consoles resides on a host that cannot resolve the controller hostname, you must replace controller with the management interface IP address of the controller node." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_nova-compute-install.xml:129(para) +msgid "Respond to the prompts for database management, Identity service credentials, service endpoint registration, and message broker credentials.." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_nova-compute-install.xml:142(para) +msgid "Determine whether your compute node supports hardware acceleration for virtual machines:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_nova-compute-install.xml:145(para) +msgid "If this command returns a value of one or greater, your compute node supports hardware acceleration which typically requires no additional configuration." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_nova-compute-install.xml:149(para) +msgid "If this command returns a value of zero, your compute node does not support hardware acceleration and you must configure libvirt to use QEMU instead of KVM." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_nova-compute-install.xml:154(para) +msgid "Edit the [libvirt] section in the /etc/nova/nova-compute.conf/etc/nova/nova.conf file as follows:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_nova-compute-install.xml:163(para) +msgid "On Ubuntu 12.04, kernels backported from newer releases may not automatically load the KVM modules for hardware acceleration when the compute node boots. In this case, launching an instance will fail with the following message in the /var/log/nova/nova-compute.log file:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_nova-compute-install.xml:169(para) +msgid "As a workaround for this issue, you must add the appropriate module for your compute node to the /etc/modules file." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_nova-compute-install.xml:172(para) +msgid "For systems with Intel processors:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_nova-compute-install.xml:174(para) +msgid "For systems with AMD processors:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_nova-compute-install.xml:185(para) +msgid "Start the Compute service including its dependencies and configure them to start automatically when the system boots:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_nova-compute-install.xml:189(para) +msgid "For RHEL, CentOS, and compatible derivatives:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_nova-compute-install.xml:198(para) +msgid "For Fedora:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/ch_glance.xml:7(title) +msgid "Add the Image Service" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/ch_glance.xml:8(para) +msgid "The OpenStack Image Service (glance) enables users to discover, register, and retrieve virtual machine images. It offers a REST API that enables you to query virtual machine image metadata and retrieve an actual image. You can store virtual machine images made available through the Image Service in a variety of locations, from simple file systems to object-storage systems like OpenStack Object Storage." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/ch_glance.xml:16(para) +msgid "For simplicity, this guide describes configuring the Image Service to use the file back end, which uploads and stores in a directory on the controller node hosting the Image Service. By default, this directory is /var/lib/glance/images/." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/ch_glance.xml:21(para) +msgid "Before you proceed, ensure that the controller node has at least several gigabytes of space available in this directory." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/ch_glance.xml:23(para) +msgid "For information on requirements for other back ends, see Configuration Reference." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_basics-prerequisites.xml:8(title) ./doc/training-guides/basic-install-guide/object-storage/section_object-storage-install.xml:29(title) +msgid "Before you begin" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_basics-prerequisites.xml:9(para) +msgid "For a functional environment, OpenStack doesn't require a significant amount of resources. We recommend that your environment meets or exceeds the following minimum requirements which can support several minimal CirrOS instances:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_basics-prerequisites.xml:15(para) +msgid "Controller Node: 1 processor, 2 GB memory, and 5 GB storage" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_basics-prerequisites.xml:19(para) +msgid "Network Node: 1 processor, 512 MB memory, and 5 GB storage" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_basics-prerequisites.xml:23(para) +msgid "Compute Node: 1 processor, 2 GB memory, and 10 GB storage" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_basics-prerequisites.xml:27(para) +msgid "To minimize clutter and provide more resources for OpenStack, we recommend a minimal installation of your Linux distribution. Also, we strongly recommend that you install a 64-bit version of your distribution on at least the compute node. If you install a 32-bit version of your distribution on the compute node, attempting to start an instance using a 64-bit image will fail." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_basics-prerequisites.xml:34(para) +msgid "A single disk partition on each node works for most basic installations. However, you should consider Logical Volume Manager (LVM) for installations with optional services such as Block Storage." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_basics-prerequisites.xml:39(para) +msgid "Many users build their test environments on virtual machines (VMs). The primary benefits of VMs include the following:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_basics-prerequisites.xml:45(para) +msgid "One physical server can support multiple nodes, each with almost any number of network interfaces." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_basics-prerequisites.xml:49(para) +msgid "Ability to take periodic \"snap shots\" throughout the installation process and \"roll back\" to a working configuration in the event of a problem." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_basics-prerequisites.xml:54(para) +msgid "However, VMs will reduce performance of your instances, particularly if your hypervisor and/or processor lacks support for hardware acceleration of nested VMs." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_basics-prerequisites.xml:58(para) +msgid "If you choose to install on VMs, make sure your hypervisor permits promiscuous mode on the external network." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_basics-prerequisites.xml:62(para) +msgid "For more information about system requirements, see the OpenStack Operations Guide." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/app_reserved_uids.xml:7(title) ./doc/training-guides/basic-install-guide/app_reserved_uids.xml:25(caption) +msgid "Reserved user IDs" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/app_reserved_uids.xml:9(para) +msgid "In OpenStack, certain user IDs are reserved and used to run specific OpenStack services and own specific OpenStack files. These users are set up according to the distribution packages. The following table gives an overview." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/app_reserved_uids.xml:17(para) +msgid "Some OpenStack packages generate and assign user IDs automatically during package installation. In these cases, the user ID value is not important. The existence of the user ID is what matters." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/app_reserved_uids.xml:28(th) +msgid "Name" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/app_reserved_uids.xml:29(th) +msgid "Description" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/app_reserved_uids.xml:30(th) +msgid "ID" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/app_reserved_uids.xml:36(td) +msgid "ceilometer" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/app_reserved_uids.xml:37(td) +msgid "OpenStack Ceilometer Daemons" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/app_reserved_uids.xml:38(td) +msgid "166" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/app_reserved_uids.xml:39(td) ./doc/training-guides/basic-install-guide/app_reserved_uids.xml:45(td) ./doc/training-guides/basic-install-guide/app_reserved_uids.xml:51(td) ./doc/training-guides/basic-install-guide/app_reserved_uids.xml:57(td) ./doc/training-guides/basic-install-guide/app_reserved_uids.xml:63(td) ./doc/training-guides/basic-install-guide/app_reserved_uids.xml:69(td) ./doc/training-guides/basic-install-guide/app_reserved_uids.xml:76(td) ./doc/training-guides/basic-install-guide/app_reserved_uids.xml:82(td) ./doc/training-guides/basic-install-guide/app_reserved_uids.xml:87(td) +msgid "Assigned during package installation" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/app_reserved_uids.xml:42(td) +msgid "cinder" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/app_reserved_uids.xml:43(td) +msgid "OpenStack Cinder Daemons" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/app_reserved_uids.xml:44(td) +msgid "165" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/app_reserved_uids.xml:48(td) +msgid "glance" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/app_reserved_uids.xml:49(td) +msgid "OpenStack Glance Daemons" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/app_reserved_uids.xml:50(td) +msgid "161" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/app_reserved_uids.xml:54(td) +msgid "heat" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/app_reserved_uids.xml:55(td) +msgid "OpenStack Heat Daemons" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/app_reserved_uids.xml:56(td) +msgid "187" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/app_reserved_uids.xml:60(td) +msgid "keystone" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/app_reserved_uids.xml:61(td) +msgid "OpenStack Keystone Daemons" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/app_reserved_uids.xml:62(td) +msgid "163" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/app_reserved_uids.xml:66(td) +msgid "neutron" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/app_reserved_uids.xml:67(td) +msgid "OpenStack Neutron Daemons" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/app_reserved_uids.xml:68(td) +msgid "164" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/app_reserved_uids.xml:72(td) +msgid "nova" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/app_reserved_uids.xml:73(td) +msgid "OpenStack Nova Daemons" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/app_reserved_uids.xml:74(td) +msgid "162" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/app_reserved_uids.xml:75(td) +msgid "96" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/app_reserved_uids.xml:79(td) +msgid "swift" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/app_reserved_uids.xml:80(td) +msgid "OpenStack Swift Daemons" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/app_reserved_uids.xml:81(td) +msgid "160" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/app_reserved_uids.xml:85(td) +msgid "trove" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/app_reserved_uids.xml:86(td) +msgid "OpenStack Trove Daemons" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/app_reserved_uids.xml:91(para) +msgid "Each user belongs to a user group with the same name as the user." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ovs-controller-node.xml:9(para) +msgid "By default, the system-config-firewall automated firewall configuration tool is in place on RHEL. This graphical interface (and a curses-style interface with -tui on the end of the name) enables you to configure IP tables as a basic firewall. You should disable it when you work with Neutron unless you are familiar with the underlying network technologies, as, by default, it blocks various types of network traffic that are important to Neutron. To disable it, simple launch the program and clear the Enabled check box." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ovs-controller-node.xml:19(para) +msgid "After you successfully set up OpenStack with Neutron, you can re-enable and configure the tool. However, during Neutron set up, disable the tool to make it easier to debug network issues." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ovs-controller-node.xml:26(para) +msgid "Before you configure individual nodes for Networking, you must create the required OpenStack components: user, service, database, and one or more endpoints. After you complete these steps on the controller node, follow the instructions in this guide to set up OpenStack Networking nodes." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ovs-controller-node.xml:33(para) +msgid "Connect to the MySQL database as the root user, create the neutron database, and grant the proper access to it:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ovs-controller-node.xml:44(para) +msgid "Create the required user, service, and endpoint so that Networking can interface with the Identity Service." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ovs-controller-node.xml:46(para) +msgid "Create a neutron user:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ovs-controller-node.xml:48(para) +msgid "Add the user role to the neutron user:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ovs-controller-node.xml:50(para) +msgid "Create the neutron service:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ovs-controller-node.xml:53(para) +msgid "Create a Networking endpoint:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ovs-controller-node.xml:62(title) +msgid "Install and configure server component" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ovs-controller-node.xml:64(para) +msgid "Install the server component of Networking and any dependencies." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ovs-controller-node.xml:70(para) +msgid "Configure Networking to connect to the database:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ovs-controller-node.xml:75(para) +msgid "Configure Networking to use your MySQL database. Edit the /etc/neutron/neutron.conf file and add the following key under the [database] section. Replace NEUTRON_DBPASS with the password you chose for the Neutron database." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ovs-controller-node.xml:85(para) +msgid "Configure Networking to use keystone as the Identity Service for authentication:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ovs-controller-node.xml:90(para) ./doc/training-guides/basic-install-guide/section_neutron-ovs-network-node.xml:86(para) ./doc/training-guides/basic-install-guide/section_neutron-ovs-network-node.xml:120(para) +msgid "Set the auth_strategy configuration key to keystone in the DEFAULT section of the file:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ovs-controller-node.xml:116(para) +msgid "Configure Networking to use keystone as the Identity Service for authentication." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ovs-controller-node.xml:121(para) +msgid "Edit the /etc/neutron/neutron.conf file and add the file and add the following key under the [DEFAULT] section." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ovs-controller-node.xml:128(para) +msgid "Add the following keys under the [keystone_authtoken] section. Replace NEUTRON_PASS with the password you chose for the Neutron user in Keystone." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ovs-controller-node.xml:157(para) +msgid "Configure Networking to use your message broker. Edit the /etc/neutron/neutron.conf file and add the following keys under the [DEFAULT] section." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ovs-controller-node.xml:161(para) +msgid "Replace RABBIT_PASS with the password you chose for RabbitMQ." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ovs-controller-node.xml:171(title) +msgid "Install and configure Open vSwitch (OVS) plug-in" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ovs-controller-node.xml:177(para) +msgid "Install the Open vSwitch plug-in:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ovs-controller-node.xml:183(para) +msgid "You must set some common configuration options no matter which networking technology you choose to use with Open vSwitch. You must configure Networking core to use OVS. Edit the /etc/neutron/neutron.conf file:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ovs-controller-node.xml:191(para) +msgid "The dedicated controller node does not need to run Open vSwitch or the Open vSwitch agent." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ovs-controller-node.xml:196(para) +msgid "Configure the OVS plug-in to use GRE tunneling. Edit the /etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini file:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ovs-controller-node.xml:209(para) +msgid "Configure Compute to use OpenStack Networking services. Configure the /etc/nova/nova.conf file as per instructions below:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ovs-controller-node.xml:233(para) +msgid "Configure Compute to use OpenStack Networking services. Edit the /etc/nova/nova.conf file:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ovs-controller-node.xml:249(para) +msgid "Regardless of which firewall driver you chose when you configured the network and compute nodes, set this driver as the No-Op firewall. This firewall is a nova firewall, and because neutron handles the Firewall, you must tell nova not to use one." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ovs-controller-node.xml:256(para) +msgid "When Networking handles the firewall, the option firewall_driver should be set according to the specified plug-in. For example with OVS, edit the /etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini file:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ovs-controller-node.xml:270(para) +msgid "If you do not want to use a firewall in Compute or Networking, set firewall_driver=nova.virt.firewall.NoopFirewallDriver in both config files, and comment out or remove security_group_api=neutron in the /etc/nova/nova.conf file, otherwise you may encounter ERROR: The server has either erred or is incapable of performing the requested operation. (HTTP 500) when issuing commands." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ovs-controller-node.xml:311(para) +msgid "Restart the Compute and Networking services:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_heat-install.xml:7(title) +msgid "Install and configure Orchestration" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_heat-install.xml:8(para) +msgid "This section describes how to install and configure the Orchestration module (heat) on the controller node." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_heat-install.xml:12(para) +msgid "Before you install and configure Orchestration, you must create a database and Identity service credentials including endpoints." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_heat-install.xml:15(para) +msgid "Connect to the database server as the root user:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_heat-install.xml:17(para) +msgid "Create the heat database:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_heat-install.xml:19(para) +msgid "Grant the proper access to the database:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_heat-install.xml:21(replaceable) ./doc/training-guides/basic-install-guide/section_heat-install.xml:22(replaceable) ./doc/training-guides/basic-install-guide/section_heat-install.xml:89(replaceable) +msgid "HEAT_DBPASS" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_heat-install.xml:24(para) +msgid "Replace HEAT_DBPASS with a suitable password." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_heat-install.xml:28(para) +msgid "Create Identity service credentials:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_heat-install.xml:31(para) +msgid "Create the heat user:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_heat-install.xml:32(replaceable) ./doc/training-guides/basic-install-guide/section_heat-install.xml:117(replaceable) +msgid "HEAT_PASS" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_heat-install.xml:33(para) +msgid "Replace HEAT_PASS with a suitable password and EMAIL_ADDRESS with a suitable e-mail address." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_heat-install.xml:38(para) +msgid "Link the heat user to the service tenant and admin role:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_heat-install.xml:44(para) +msgid "Create the heat and heat-cfn services:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_heat-install.xml:52(para) +msgid "Create the heat_stack_user and heat_stack_owner roles:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_heat-install.xml:53(para) +msgid "By default, users created by Orchestration use the role heat_stack_user." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_heat-install.xml:74(title) ./doc/training-guides/basic-install-guide/section_heat-install.xml:150(title) +msgid "To install and configure the Orchestration components" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_heat-install.xml:76(para) ./doc/training-guides/basic-install-guide/section_heat-install.xml:152(para) +msgid "Run the following commands to install the packages:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_heat-install.xml:82(para) ./doc/training-guides/basic-install-guide/section_heat-install.xml:170(para) +msgid "Edit the /etc/heat/heat.conf file." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_heat-install.xml:90(para) +msgid "Replace HEAT_DBPASS with the password you chose for the Orchestration database." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_heat-install.xml:106(para) +msgid "In the [keystone_authtoken] and [ec2authtoken] sections, configure Identity service access:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_heat-install.xml:122(para) +msgid "Replace HEAT_PASS with the password you chose for the heat user in the Identity service." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_heat-install.xml:127(para) +msgid "In the [DEFAULT] section, configure the metadata and wait condition URLs:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_heat-install.xml:135(para) +msgid "Configure the log directory in the [DEFAULT] section:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_heat-install.xml:144(para) +msgid "Run the following command to populate the Orchestration database:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_heat-install.xml:166(para) +msgid "Respond to the debconf configuration tool prompts." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_heat-install.xml:173(para) +msgid "In the [ec2authtoken] section, configure Identity service access for EC2 operations:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_heat-install.xml:185(para) +msgid "Restart the Orchestration services:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_heat-install.xml:191(para) +msgid "Start the Orchestration services and configure them to start when the system boots:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ml2-network-node.xml:7(title) ./doc/training-guides/basic-install-guide/section_neutron-ovs-network-node.xml:7(title) +msgid "Configure network node" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ml2-network-node.xml:13(para) +msgid "Edit /etc/sysctl.conf to contain the following:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ml2-network-node.xml:34(para) +msgid "Ubuntu installations using Linux kernel version 3.11 or newer do not require the openvswitch-datapath-dkms package." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ml2-network-node.xml:182(title) +msgid "To configure the Layer-3 (L3) agent" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ml2-network-node.xml:183(para) +msgid "The Layer-3 (L3) agent provides routing services for instance virtual networks." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ml2-network-node.xml:192(para) ./doc/training-guides/basic-install-guide/section_neutron-ml2-network-node.xml:207(para) +msgid "To assist with troubleshooting, add verbose = True to the [DEFAULT] section in the /etc/neutron/l3_agent.ini file." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ml2-network-node.xml:199(para) +msgid "Edit the /etc/neutron/l3_agent.ini file and add the following keys to the [DEFAULT] section:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ml2-network-node.xml:215(title) +msgid "To configure the DHCP agent" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ml2-network-node.xml:216(para) +msgid "The DHCP agent provides DHCP services for instance virtual networks." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ml2-network-node.xml:228(para) ./doc/training-guides/basic-install-guide/section_neutron-ml2-network-node.xml:244(para) +msgid "To assist with troubleshooting, add verbose = True to the [DEFAULT] section in the /etc/neutron/dhcp_agent.ini file." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ml2-network-node.xml:235(para) +msgid "Edit the /etc/neutron/dhcp_agent.ini file and add the following keys to the [DEFAULT] section:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ml2-network-node.xml:252(title) +msgid "To configure the metadata agent" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ml2-network-node.xml:253(para) +msgid "The metadata agent provides configuration information such as credentials for remote access to instances." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ml2-network-node.xml:258(para) ./doc/training-guides/basic-install-guide/section_neutron-ml2-network-node.xml:289(para) +msgid "Replace NEUTRON_PASS with the password you chose for the neutron user in the Identity service. Replace METADATA_SECRET with a suitable secret for the metadata proxy." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ml2-network-node.xml:276(replaceable) ./doc/training-guides/basic-install-guide/section_neutron-ml2-network-node.xml:302(replaceable) ./doc/training-guides/basic-install-guide/section_neutron-ml2-network-node.xml:324(replaceable) ./doc/training-guides/basic-install-guide/section_neutron-ml2-network-node.xml:336(replaceable) +msgid "METADATA_SECRET" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ml2-network-node.xml:278(para) ./doc/training-guides/basic-install-guide/section_neutron-ml2-network-node.xml:304(para) +msgid "To assist with troubleshooting, add verbose = True to the [DEFAULT] section in the /etc/neutron/metadata_agent.ini file." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ml2-network-node.xml:285(para) +msgid "Edit the /etc/neutron/metadata_agent.ini file and add the following keys to the [DEFAULT] section:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ml2-network-node.xml:312(para) +msgid "Perform the next two steps on the controller node." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ml2-network-node.xml:317(para) +msgid "On the controller node, configure Compute to use the metadata service:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ml2-network-node.xml:319(para) ./doc/training-guides/basic-install-guide/section_neutron-ml2-network-node.xml:331(para) +msgid "Replace METADATA_SECRET with the secret you chose for the metadata proxy." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ml2-network-node.xml:327(para) +msgid "On the controller node, edit the /etc/nova/nova.conf file and add the following keys to the [DEFAULT] section:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ml2-network-node.xml:339(para) +msgid "On the controller node, restart the Compute API service:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ml2-network-node.xml:347(para) +msgid "The ML2 plug-in uses the Open vSwitch (OVS) mechanism (agent) to build virtual networking framework for instances." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ml2-network-node.xml:352(para) +msgid "Replace INSTANCE_TUNNELS_INTERFACE_IP_ADDRESS with the IP address of the instance tunnels network interface on your network node. This guide uses 10.0.1.21 for the IP address of the instance tunnels network interface on the network node." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ml2-network-node.xml:378(para) +msgid "Edit the /etc/neutron/plugins/ml2/ml2_conf.ini file." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ml2-network-node.xml:395(para) +msgid "Replace INSTANCE_TUNNELS_INTERFACE_IP_ADDRESS with the IP address of the instance tunnels network interface on your network node." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ml2-network-node.xml:414(para) +msgid "The OVS service provides the underlying virtual networking framework for instances. The integration bridge br-int handles internal instance network traffic within OVS. The external bridge br-ex handles external instance network traffic within OVS. The external bridge requires a port on the physical external network interface to provide instances with external network access. In essence, this port bridges the virtual and physical external networks in your environment." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ml2-network-node.xml:444(para) +msgid "Add the external bridge:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ml2-network-node.xml:448(para) +msgid "Add a port to the external bridge that connects to the physical external network interface:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ml2-network-node.xml:455(para) +msgid "Depending on your network interface driver, you may need to disable Generic Receive Offload (GRO) to achieve suitable throughput between your instances and the external network." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ml2-network-node.xml:459(para) +msgid "To temporarily disable GRO on the external network interface while testing your environment:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ml2-network-node.xml:498(para) +msgid "Start the Networking services and configure them to start when the system boots:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ml2-network-node.xml:520(para) +msgid "Restart the Networking services:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_ceilometer-glance.xml:7(title) +msgid "Configure the Image Service for Telemetry" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_ceilometer-glance.xml:10(para) +msgid "To retrieve image samples, you must configure the Image Service to send notifications to the bus." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_ceilometer-glance.xml:13(para) +msgid "Edit /etc/glance/glance-api.conf and modify the [DEFAULT] section:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_ceilometer-glance.xml:29(para) +msgid "Restart the Image Services with their new settings:" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/training-guides/basic-install-guide/section_debconf-keystone_authtoken.xml:31(None) +msgid "@@image: 'figures/debconf-screenshots/service_keystone_authtoken_server_hostname.png'; md5=aafd53894e1d960531d4901123952117" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/training-guides/basic-install-guide/section_debconf-keystone_authtoken.xml:38(None) +msgid "@@image: 'figures/debconf-screenshots/service_keystone_authtoken_admin_tenant_name.png'; md5=a935563e4fba9b00040e35cdcfffc732" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/training-guides/basic-install-guide/section_debconf-keystone_authtoken.xml:45(None) +msgid "@@image: 'figures/debconf-screenshots/service_keystone_authtoken_tenant_admin_user.png'; md5=fe3dc93c591b3e9783d4d05556efcf25" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/training-guides/basic-install-guide/section_debconf-keystone_authtoken.xml:52(None) +msgid "@@image: 'figures/debconf-screenshots/service_keystone_authtoken_admin_password.png'; md5=0c30c80315d5e636dbe93a938fc2822b" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_debconf-keystone_authtoken.xml:7(title) +msgid "Services and the [keystone_authtoken]" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_debconf-keystone_authtoken.xml:8(para) +msgid "Because most OpenStack services must access the Identity Service, you must configure the IP address of the keystone server to be able to access it. You must also configure the admin_tenant_name, admin_user, and admin_password options for each service to work." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_debconf-keystone_authtoken.xml:14(para) +msgid "Generally, this section looks like this:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_debconf-keystone_authtoken.xml:22(para) +msgid "The debconf system helps users configure the auth_host, admin_tenant_name, admin_user and admin_password options." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_debconf-keystone_authtoken.xml:26(para) +msgid "The following screens show an example Image Service configuration:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_debconf-keystone_authtoken.xml:56(para) +msgid "This information is stored in the configuration file for each service. For example:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_debconf-keystone_authtoken.xml:64(para) +msgid "The Debian OpenStack packages offer automation for this, so OpenStack users do not have to manually edit the configuration files." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_basics-queue.xml:8(title) +msgid "Messaging server" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_basics-queue.xml:9(para) +msgid "OpenStack uses a message broker to coordinate operations and status information among services. The message broker service typically runs on the controller node. OpenStack supports several message brokers including RabbitMQ, Qpid, and ZeroMQ. However, most distributions that package OpenStack support a particular message broker. This guide covers the RabbitMQ message broker which is supported by each distribution. If you prefer to implement a different message broker, consult the documentation associated with it." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_basics-queue.xml:31(title) +msgid "To install the RabbitMQ message broker service" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_basics-queue.xml:43(title) +msgid "To configure the message broker service" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_basics-queue.xml:45(para) +msgid "Start the message broker service and enable it to start when the system boots:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_basics-queue.xml:51(para) +msgid "The message broker creates a default account that uses guest for the username and password. To simplify installation of your test environment, we recommend that you use this account, but change the password for it." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_basics-queue.xml:55(para) +msgid "Run the following command:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_basics-queue.xml:56(para) +msgid "Replace RABBIT_PASS with a suitable password." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_basics-queue.xml:59(para) +msgid "You must configure the rabbit_password key in the configuration file for each OpenStack service that uses the message broker." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_basics-queue.xml:63(para) +msgid "For production environments, you should create a unique account with suitable password. For more information on securing the message broker, see the documentation." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_basics-queue.xml:68(para) +msgid "If you decide to create a unique account with suitable password for your test environment, you must configure the rabbit_userid and rabbit_password keys in the configuration file of each OpenStack service that uses the message broker." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_basics-queue.xml:76(para) +msgid "Congratulations, now you are ready to install OpenStack services!" +msgstr "" + #: ./doc/training-guides/basic-install-guide/lab002-network-node.xml:28(para) msgid "Start your Controller Node the one you setup in previous section." msgstr "" @@ -2600,6 +6787,2286 @@ msgstr "" msgid "Edit Network Interfaces file /etc/network/interfaces:" msgstr "" +#: ./doc/training-guides/basic-install-guide/section_keystone-services.xml:8(title) +msgid "Create the service entity and API endpoint" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_keystone-services.xml:9(para) +msgid "After you create tenants, users, and roles, you must create the service entity and API endpoint for the Identity service." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_keystone-services.xml:15(para) +msgid "Set the OS_SERVICE_TOKEN and OS_SERVICE_ENDPOINT environment variables, as described in ." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_keystone-services.xml:21(title) +msgid "To create the service entity and API endpoint" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_keystone-services.xml:23(para) +msgid "The Identity service manages a catalog of services in your OpenStack environment. Services use this catalog to locate other services in your environment." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_keystone-services.xml:26(para) +msgid "Create the service entity for the Identity service:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_keystone-services.xml:43(para) +msgid "The Identity service manages a catalog of API endpoints associated with the services in your OpenStack environment. Services use this catalog to determine how to communicate with other services in your environment." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_keystone-services.xml:47(para) +msgid "OpenStack provides three API endpoint variations for each service: admin, internal, and public. In a production environment, the variants might reside on separate networks that service different types of users for security reasons. For simplicity, this configuration uses the management network for all variations." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_keystone-services.xml:52(para) +msgid "Create the API endpoint for the Identity service:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_keystone-services.xml:69(para) +msgid "This command references the ID of the service that you created in the previous step." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_keystone-services.xml:75(para) +msgid "Each service that you add to your OpenStack environment requires adding information such as API endpoints to the Identity service. The sections of this guide that cover service installation include steps to add the appropriate information to the Identity service." +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/training-guides/basic-install-guide/section_debconf-api-endpoints.xml:30(None) +msgid "@@image: 'figures/debconf-screenshots/api-endpoint_1_register_endpoint.png'; md5=d534be231be4f725820a1050fbf44231" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/training-guides/basic-install-guide/section_debconf-api-endpoints.xml:41(None) +msgid "@@image: 'figures/debconf-screenshots/api-endpoint_2_keystone_server_ip.png'; md5=d2c5a5b82dd433fcf9cde6f5ac34c30e" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/training-guides/basic-install-guide/section_debconf-api-endpoints.xml:55(None) +msgid "@@image: 'figures/debconf-screenshots/api-endpoint_3_keystone_authtoken.png'; md5=1f3b05ebe671f64d672ac70d246e4f39" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/training-guides/basic-install-guide/section_debconf-api-endpoints.xml:70(None) +msgid "@@image: 'figures/debconf-screenshots/api-endpoint_4_service_endpoint_ip_address.png'; md5=6853f0ae2ef8d5fddb22c466d465de15" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/training-guides/basic-install-guide/section_debconf-api-endpoints.xml:82(None) +msgid "@@image: 'figures/debconf-screenshots/api-endpoint_5_region_name.png'; md5=a6bce0acf5a1cb85f161290f0cf30733" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_debconf-api-endpoints.xml:7(title) +msgid "Register API endpoints" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_debconf-api-endpoints.xml:8(para) +msgid "All Debian packages for API services, except the heat-api package, register the service in the Identity Service catalog. This feature is helpful because API endpoints are difficult to remember." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_debconf-api-endpoints.xml:13(para) +msgid "The heat-common package and not the heat-api package configures the Orchestration service." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_debconf-api-endpoints.xml:17(para) +msgid "When you install a package for an API service, you are prompted to register that service. However, after you install or upgrade the package for an API service, Debian immediately removes your response to this prompt from the debconf database. Consequently, you are prompted to re-register the service with the Identity Service. If you already registered the API service, respond no when you upgrade." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_debconf-api-endpoints.xml:34(para) +msgid "This screen registers packages in the Identity Service catalog:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_debconf-api-endpoints.xml:45(para) +msgid "You are prompted for the Identity Service admin_token value. The Identity Service uses this value to register the API service. When you set up the keystone package, this value is configured automatically." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_debconf-api-endpoints.xml:59(para) +msgid "This screen configures the IP addresses for the service. The configuration script automatically detects the IP address used by the interface that is connected to the default route (/sbin/route and /sbin/ip)." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_debconf-api-endpoints.xml:63(para) +msgid "Unless you have a unique set up for your network, press ENTER." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_debconf-api-endpoints.xml:74(para) +msgid "This screen configures the region name for the service. For example, us-east-coast or europe-paris." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_debconf-api-endpoints.xml:86(para) +msgid "The Debian package post installation scripts will then perform the below commands for you:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_debconf-api-endpoints.xml:98(para) +msgid "The values of AUTH_TOKEN, KEYSTONE_ENDPOINT_IP, PKG_ENDPOINT_IP and REGION_NAME depend on the answer you will provide to the debconf prompts. But the values of SERVICE_NAME, SERVICE_TYPE, SERVICE_DESC and SERVICE_URL are already pre-wired in each package, so you don't have to remember them." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ovs-network-node.xml:9(para) +msgid "Before you start, set up a machine as a dedicated network node. Dedicated network nodes have a MGMT_INTERFACE NIC, a DATA_INTERFACE NIC, and an EXTERNAL_INTERFACE NIC." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ovs-network-node.xml:14(para) +msgid "The management network handles communication among nodes. The data network handles communication coming to and from VMs. The external NIC connects the network node, and optionally to the controller node, so your VMs can connect to the outside world." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ovs-network-node.xml:21(para) +msgid "By default, the system-config-firewall automated firewall configuration tool is in place on RHEL. This graphical interface (and a curses-style interface with -tui on the end of the name) enables you to configure IP tables as a basic firewall. You should disable it when you work with Networking unless you are familiar with the underlying network technologies. By default, it blocks various types of network traffic that are important to Networking. To disable it, simply launch the program and clear the Enabled check box." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ovs-network-node.xml:30(para) +msgid "After you successfully set up OpenStack Networking, you can re-enable and configure the tool. However, during Networking set up, disable the tool to make it easier to debug network issues." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ovs-network-node.xml:36(title) +msgid "Install agents and configure common components" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ovs-network-node.xml:38(para) +msgid "Install the Networking packages and any dependencies." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ovs-network-node.xml:46(para) +msgid "Respond to prompts for database management, [keystone_authtoken] settings, RabbitMQ credentials and API endpoint registration." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ovs-network-node.xml:57(para) +msgid "Configure Networking agents to start at boot time:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ovs-network-node.xml:62(para) +msgid "Enable packet forwarding and disable packet destination filtering so that the network node can coordinate traffic for the VMs. Edit the /etc/sysctl.conf file, as follows:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ovs-network-node.xml:69(para) +msgid "Use the command to ensure the changes made to the /etc/sysctl.conf file take effect:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ovs-network-node.xml:74(para) +msgid "It is recommended that the networking service is restarted after changing values related to the networking configuration. This ensures that all modified values take effect immediately:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ovs-network-node.xml:153(para) +msgid "Configure the RabbitMQ access. Edit the /etc/neutron/neutron.conf file to modify the following parameters in the DEFAULT section." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ovs-network-node.xml:163(title) +msgid "Install and configure the Open vSwitch (OVS) plug-in" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ovs-network-node.xml:176(para) +msgid "Start Open vSwitch:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ovs-network-node.xml:180(para) +msgid "And configure it to start when the system boots:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ovs-network-node.xml:186(para) +msgid "No matter which networking technology you use, you must add the br-ex external bridge, which connects to the outside world." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ovs-network-node.xml:192(para) +msgid "Add a port (connection) from the EXTERNAL_INTERFACE interface to br-ex interface:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ovs-network-node.xml:195(replaceable) ./doc/training-guides/basic-install-guide/section_neutron-ovs-network-node.xml:205(replaceable) +msgid "EXTERNAL_INTERFACE" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ovs-network-node.xml:197(para) +msgid "The host must have an IP address associated with an interface other than EXTERNAL_INTERFACE, and your remote terminal session must be associated with this other IP address." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ovs-network-node.xml:202(para) +msgid "If you associate an IP address with EXTERNAL_INTERFACE, that IP address stops working after you issue the command. If you associate a remote terminal session with that IP address, you lose connectivity with the host." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ovs-network-node.xml:208(para) +msgid "For more details about this behavior, see the Configuration Problems section of the Open vSwitch FAQ." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ovs-network-node.xml:214(para) +msgid "Configure the EXTERNAL_INTERFACE without an IP address and in promiscuous mode. Additionally, you must set the newly created br-ex interface to have the IP address that formerly belonged to EXTERNAL_INTERFACE." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ovs-network-node.xml:221(para) +msgid "Generic Receive Offload (GRO) should not be enabled on this interface as it can cause severe performance problems. It can be disabled with the ethtool utility." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ovs-network-node.xml:226(para) +msgid "Edit the /etc/sysconfig/network-scripts/ifcfg-EXTERNAL_INTERFACE file:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ovs-network-node.xml:235(para) +msgid "Create and edit the /etc/sysconfig/network-scripts/ifcfg-br-ex file:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ovs-network-node.xml:247(para) +msgid "You must set some common configuration options no matter which networking technology you choose to use with Open vSwitch. Configure the L3 and DHCP agents to use OVS and namespaces. Edit the /etc/neutron/l3_agent.ini and /etc/neutron/dhcp_agent.ini files, respectively:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ovs-network-node.xml:257(para) +msgid "While the examples in this guide enable network namespaces by default, you can disable them if issues occur or your kernel does not support them. Edit the /etc/neutron/l3_agent.ini and /etc/neutron/dhcp_agent.ini files, respectively:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ovs-network-node.xml:264(para) +msgid "Edit the /etc/neutron/neutron.conf file to disable overlapping IP addresses:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ovs-network-node.xml:267(para) +msgid "Note that when network namespaces are disabled, you can have only one router for each network node and overlapping IP addresses are not supported." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ovs-network-node.xml:270(para) +msgid "You must complete additional steps after you create the initial Neutron virtual networks and router." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ovs-network-node.xml:276(para) +msgid "Similarly, you must also tell Neutron core to use OVS. Edit the /etc/neutron/neutron.conf file:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ovs-network-node.xml:283(para) +msgid "Configure a firewall plug-in. If you do not wish to enforce firewall rules, called security groups by OpenStack, you can use neutron.agent.firewall.NoopFirewall. Otherwise, you can choose one of the Networking firewall plug-ins. The most common choice is the Hybrid OVS-IPTables driver, but you can also use the Firewall-as-a-Service driver. Edit the /etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini file:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ovs-network-node.xml:310(para) +msgid "Configure the OVS plug-in to use GRE tunneling, the br-int integration bridge, the br-tun tunneling bridge, and a local IP for the DATA_INTERFACE tunnel IP. Edit the /etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini file:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ovs-network-node.xml:329(title) +msgid "Configure the agents" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ovs-network-node.xml:331(para) +msgid "To perform DHCP on the software-defined networks, Networking supports several different plug-ins. However, in general, you use the dnsmasq plug-in." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ovs-network-node.xml:334(para) +msgid "Configure the /etc/neutron/dhcp_agent.ini file:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ovs-network-node.xml:342(para) +msgid "To allow virtual machines to access the Compute metadata information, the Networking metadata agent must be enabled and configured. The agent will act as a proxy for the Compute metadata service." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ovs-network-node.xml:346(para) +msgid "On the controller, edit the /etc/nova/nova.conf file to define a secret key that will be shared between the Compute service and the Networking metadata agent." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ovs-network-node.xml:350(para) +msgid "Add to the [DEFAULT] section:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ovs-network-node.xml:354(replaceable) ./doc/training-guides/basic-install-guide/section_neutron-ovs-network-node.xml:360(replaceable) ./doc/training-guides/basic-install-guide/section_neutron-ovs-network-node.xml:380(replaceable) ./doc/training-guides/basic-install-guide/section_neutron-ovs-network-node.xml:396(replaceable) +msgid "METADATA_PASS" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ovs-network-node.xml:356(para) +msgid "Set the neutron_metadata_proxy_shared_secret key:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ovs-network-node.xml:363(para) +msgid "Restart the nova-api service:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ovs-network-node.xml:367(para) +msgid "On the network node, modify the metadata agent configuration." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ovs-network-node.xml:369(para) +msgid "Edit the /etc/neutron/metadata_agent.ini file and modify the [DEFAULT] section:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ovs-network-node.xml:381(para) ./doc/training-guides/basic-install-guide/section_neutron-ovs-network-node.xml:411(para) +msgid "Set the required keys:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ovs-network-node.xml:398(para) +msgid "The value of auth_region is case-sensitive and must match the endpoint region defined in Keystone." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ovs-network-node.xml:403(para) +msgid "If you serve the OpenStack Networking API over HTTPS with self-signed certificates, you must perform additional configuration for the metadata agent because Networking cannot validate the SSL certificates from the service catalog." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_neutron-ovs-network-node.xml:407(para) +msgid "Add this statement to the [DEFAULT] section:" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/training-guides/basic-install-guide/ch_overview.xml:37(None) +msgid "@@image: 'http://git.openstack.org/cgit/openstack/openstack-manuals/plain/doc/common/figures/openstack_havana_conceptual_arch.png'; md5=THIS FILE DOESN'T EXIST" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/ch_overview.xml:8(title) ./doc/training-guides/sources/cinder/architecture.xml:7(title) +msgid "Architecture" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/ch_overview.xml:11(para) +msgid "The OpenStack project is an open source cloud computing platform that supports all types of cloud environments. The project aims for simple implementation, massive scalability, and a rich set of features. Cloud computing experts from around the world contribute to the project." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/ch_overview.xml:16(para) +msgid "OpenStack provides an Infrastructure-as-a-Service (IaaS) solution through a variety of complemental services. Each service offers an application programming interface (API) that facilitates this integration. The following table provides a list of OpenStack services:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/ch_overview.xml:23(para) +msgid "This guide describes how to deploy these services in a functional test environment and, by example, teaches you how to build a production environment." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/ch_overview.xml:28(title) ./doc/training-guides/basic-install-guide/ch_overview.xml:33(title) +msgid "Conceptual architecture" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/ch_overview.xml:29(para) +msgid "Launching a virtual machine or instance involves many interactions among several services. The following diagram provides the conceptual architecture of a typical OpenStack environment." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/ch_overview.xml:43(title) +msgid "Example architectures" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/ch_overview.xml:44(para) +msgid "OpenStack is highly configurable to meet different needs with various compute, networking, and storage options. This guide enables you to choose your own OpenStack adventure using a combination of basic and optional services. This guide uses the following example architectures:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/ch_overview.xml:51(para) +msgid "Three-node architecture with OpenStack Networking (neutron). To be implemented" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/ch_overview.xml:55(para) +msgid "The basic controller node runs the Identity service, Image Service, management portions of Compute and Networking, Networking plug-in, and the dashboard. It also includes supporting services such as a database, message broker, and Network Time Protocol (NTP)." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/ch_overview.xml:62(para) ./doc/training-guides/basic-install-guide/ch_overview.xml:108(para) +msgid "Optionally, the controller node also runs portions of Block Storage, Object Storage, Database Service, Orchestration, and Telemetry. These components provide additional features for your environment." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/ch_overview.xml:68(para) +msgid "The network node runs the Networking plug-in, layer 2 agent, and several layer 3 agents that provision and operate tenant networks. Layer 2 services include provisioning of virtual networks and tunnels. Layer 3 services include routing, NAT , and DHCP. This node also handles external (internet) connectivity for tenant virtual machines or instances." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/ch_overview.xml:78(para) +msgid "The compute node runs the hypervisor portion of Compute, which operates tenant virtual machines or instances. By default Compute uses KVM as the hypervisor. The compute node also runs the Networking plug-in and layer 2 agent which operate tenant networks and implement security groups. You can run more than one compute node." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/ch_overview.xml:84(para) ./doc/training-guides/basic-install-guide/ch_overview.xml:124(para) +msgid "Optionally, the compute node also runs the Telemetry agent. This component provides additional features for your environment." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/ch_overview.xml:102(para) +msgid "The basic controller node runs the Identity service, Image Service, management portion of Compute, and the dashboard necessary to launch a simple instance. It also includes supporting services such as a database, message broker, and NTP." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/ch_overview.xml:114(para) +msgid "The basic compute node runs the hypervisor portion of Compute, which operates tenantvirtual machines or instances. By default, Compute uses KVM as the hypervisor. Compute also provisions and operates tenant networks and implements security groups. You can run more than one compute node." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_trove-verify.xml:7(title) +msgid "Verify the Database service installation" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_trove-verify.xml:8(para) +msgid "To verify that the Database service is installed and configured correctly, try executing a Trove command:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_trove-verify.xml:12(para) +msgid "Source the demo-openrc.sh file." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_trove-verify.xml:16(para) +msgid "Retrieve the Trove instances list:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_trove-verify.xml:18(para) +msgid "You should see output similar to this:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_trove-verify.xml:25(para) +msgid "Assuming you have created an image for the type of database you want, and have updated the datastore to use that image, you can now create a Trove instance (database). To do this, use the trove command." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_trove-verify.xml:32(para) +msgid "This example shows you how to create a MySQL 5.5 database:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_trove-verify.xml:34(replaceable) ./doc/training-guides/common/module001-ch006-overview-horizon-cli.xml:1761(para) +msgid "name" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_trove-verify.xml:34(replaceable) +msgid "DBNAME" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_trove-verify.xml:35(replaceable) +msgid "USER" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/section_trove-verify.xml:35(replaceable) +msgid "PASSWORD" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/object-storage/section_object-storage-adding-proxy-server.xml:7(title) +msgid "Add another proxy server" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/object-storage/section_object-storage-adding-proxy-server.xml:8(para) +msgid "To provide additional reliability and bandwidth to your cluster, you can add proxy servers. You can set up an additional proxy node the same way that you set up the first proxy node but with additional configuration steps." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/object-storage/section_object-storage-adding-proxy-server.xml:13(para) +msgid "After you have more than two proxies, you must load balance them; your storage endpoint (what clients use to connect to your storage) also changes. You can select from different strategies for load balancing. For example, you could use round-robin DNS, or a software or hardware load balancer (like pound) in front of the two proxies. You can then point your storage URL to the load balancer, configure an initial proxy node and complete these steps to add proxy servers." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/object-storage/section_object-storage-adding-proxy-server.xml:26(para) +msgid "Update the list of memcache servers in the /etc/swift/proxy-server.conf file for added proxy servers. If you run multiple memcache servers, use this pattern for the multiple IP:port listings in each proxy server configuration file:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/object-storage/section_object-storage-adding-proxy-server.xml:37(replaceable) ./doc/training-guides/basic-install-guide/object-storage/section_object-storage-install-config-proxy-node.xml:32(replaceable) ./doc/training-guides/basic-install-guide/object-storage/section_object-storage-install-config-proxy-node.xml:38(replaceable) ./doc/training-guides/basic-install-guide/object-storage/section_object-storage-install-config-proxy-node.xml:39(replaceable) +msgid "PROXY_LOCAL_NET_IP" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/object-storage/section_object-storage-adding-proxy-server.xml:40(para) +msgid "Copy ring information to all nodes, including new proxy nodes. Also, ensure that the ring information gets to all storage nodes." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/object-storage/section_object-storage-adding-proxy-server.xml:47(para) +msgid "After you sync all nodes, make sure that the admin has keys in /etc/swift and the ownership for the ring file is correct." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/object-storage/section_object-storage-install-config-proxy-node.xml:7(title) +msgid "Install and configure the proxy node" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/object-storage/section_object-storage-install-config-proxy-node.xml:8(para) +msgid "The proxy server takes each request and looks up locations for the account, container, or object and routes the requests correctly. The proxy server also handles API requests. You enable account management by configuring it in the /etc/swift/proxy-server.conf file." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/object-storage/section_object-storage-install-config-proxy-node.xml:14(para) +msgid "The Object Storage processes run under a separate user and group, set by configuration options, and referred to as swift:swift. The default user is swift." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/object-storage/section_object-storage-install-config-proxy-node.xml:21(para) +msgid "Install swift-proxy service:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/object-storage/section_object-storage-install-config-proxy-node.xml:27(para) +msgid "Modify memcached to listen on the default interface on a local, non-public network. Edit this line in the /etc/memcached.conf file:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/object-storage/section_object-storage-install-config-proxy-node.xml:31(para) +msgid "Change it to:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/object-storage/section_object-storage-install-config-proxy-node.xml:35(para) +msgid "Modify memcached to listen on the default interface on a local, non-public network. Edit the /etc/sysconfig/memcached file:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/object-storage/section_object-storage-install-config-proxy-node.xml:42(para) +msgid "Restart the memcached service:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/object-storage/section_object-storage-install-config-proxy-node.xml:46(para) +msgid "Start the memcached service and configure it to start when the system boots:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/object-storage/section_object-storage-install-config-proxy-node.xml:52(para) +msgid "CreateEdit/etc/swift/proxy-server.conf:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/object-storage/section_object-storage-install-config-proxy-node.xml:86(replaceable) ./doc/training-guides/basic-install-guide/object-storage/section_object-storage-install.xml:72(replaceable) +msgid "SWIFT_PASS" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/object-storage/section_object-storage-install-config-proxy-node.xml:106(para) +msgid "If you run multiple memcache servers, put the multiple IP:port listings in the [filter:cache] section of the /etc/swift/proxy-server.conf file:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/object-storage/section_object-storage-install-config-proxy-node.xml:111(para) +msgid "Only the proxy server uses memcache." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/object-storage/section_object-storage-install-config-proxy-node.xml:114(para) +msgid "keystoneclient.middleware.auth_token: You must configure auth_uri to point to the public identity endpoint. Otherwise, clients might not be able to authenticate against an admin endpoint." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/object-storage/section_object-storage-install-config-proxy-node.xml:122(para) +msgid "Create the account, container, and object rings. The builder command creates a builder file with a few parameters. The parameter with the value of 18 represents 2 ^ 18th, the value that the partition is sized to. Set this “partition power” value based on the total amount of storage you expect your entire ring to use. The value 3 represents the number of replicas of each object, with the last value being the number of hours to restrict moving a partition more than once." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/object-storage/section_object-storage-install-config-proxy-node.xml:138(para) +msgid "For every storage device on each node add entries to each ring:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/object-storage/section_object-storage-install-config-proxy-node.xml:140(replaceable) ./doc/training-guides/basic-install-guide/object-storage/section_object-storage-install-config-proxy-node.xml:141(replaceable) ./doc/training-guides/basic-install-guide/object-storage/section_object-storage-install-config-proxy-node.xml:142(replaceable) +msgid "ZONE" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/object-storage/section_object-storage-install-config-proxy-node.xml:140(replaceable) ./doc/training-guides/basic-install-guide/object-storage/section_object-storage-install-config-storage-nodes.xml:55(replaceable) +msgid "STORAGE_LOCAL_NET_IP" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/object-storage/section_object-storage-install-config-proxy-node.xml:140(replaceable) ./doc/training-guides/basic-install-guide/object-storage/section_object-storage-install-config-proxy-node.xml:141(replaceable) ./doc/training-guides/basic-install-guide/object-storage/section_object-storage-install-config-proxy-node.xml:142(replaceable) ./doc/training-guides/basic-install-guide/object-storage/section_object-storage-install-config-storage-nodes.xml:81(replaceable) +msgid "STORAGE_REPLICATION_NET_IP" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/object-storage/section_object-storage-install-config-proxy-node.xml:140(replaceable) ./doc/training-guides/basic-install-guide/object-storage/section_object-storage-install-config-proxy-node.xml:141(replaceable) ./doc/training-guides/basic-install-guide/object-storage/section_object-storage-install-config-proxy-node.xml:142(replaceable) +msgid "DEVICE" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/object-storage/section_object-storage-install-config-proxy-node.xml:141(replaceable) ./doc/training-guides/basic-install-guide/object-storage/section_object-storage-install-config-proxy-node.xml:142(replaceable) +msgid "STORAGE_LOCAL_NET_IP_1" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/object-storage/section_object-storage-install-config-proxy-node.xml:144(para) +msgid "You must omit the optional STORAGE_REPLICATION_NET_IP parameter if you do not want to use dedicated network for replication." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/object-storage/section_object-storage-install-config-proxy-node.xml:148(para) +msgid "For example, if a storage node has a partition in Zone 1 on IP 10.0.0.1, the storage node has address 10.0.1.1 from replication network. The mount point of this partition is /srv/node/sdb1, and the path in /etc/rsyncd.conf is /srv/node/, the DEVICE would be sdb1 and the commands are:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/object-storage/section_object-storage-install-config-proxy-node.xml:159(para) +msgid "If you assume five zones with one node for each zone, start ZONE at 1. For each additional node, increment ZONE by 1." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/object-storage/section_object-storage-install-config-proxy-node.xml:165(para) +msgid "Verify the ring contents for each ring:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/object-storage/section_object-storage-install-config-proxy-node.xml:171(para) +msgid "Rebalance the rings:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/object-storage/section_object-storage-install-config-proxy-node.xml:176(para) +msgid "Rebalancing rings can take some time." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/object-storage/section_object-storage-install-config-proxy-node.xml:180(para) +msgid "Copy the account.ring.gz, container.ring.gz, and object.ring.gz files to each of the Proxy and Storage nodes in /etc/swift." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/object-storage/section_object-storage-install-config-proxy-node.xml:186(para) +msgid "Make sure the swift user owns all configuration files:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/object-storage/section_object-storage-install-config-proxy-node.xml:190(para) +msgid "Restart the Proxy service:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/object-storage/section_object-storage-install-config-proxy-node.xml:194(para) +msgid "Start the Proxy service and configure it to start when the system boots:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/object-storage/section_object-storage-install.xml:7(title) +msgid "Install Object Storage" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/object-storage/section_object-storage-install.xml:8(para) +msgid "Though you can install OpenStack Object Storage for development or testing purposes on one server, a multiple-server installation enables the high availability and redundancy you want in a production distributed object storage system." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/object-storage/section_object-storage-install.xml:12(para) +msgid "To perform a single-node installation for development purposes from source code, use the Swift All In One instructions (Ubuntu) or DevStack (multiple distros). See http://swift.openstack.org/development_saio.html for manual instructions or http://devstack.org for all-in-one including authentication with the Identity Service (keystone) v2.0 API." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/object-storage/section_object-storage-install.xml:21(para) +msgid "In this guide we recommend installing and configuring the Identity service so that it implements Identity API v2.0. The Object Storage service is unaware of domains when implementing Access Control Lists (ACLs), so you must use the v2.0 API to avoid having identical user names in different domains, which would enable two users to access the same objects." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/object-storage/section_object-storage-install.xml:30(para) +msgid "Have a copy of the operating system installation media available if you are installing on a new server." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/object-storage/section_object-storage-install.xml:32(para) +msgid "These steps assume you have set up repositories for packages for your operating system as shown in OpenStack Packages." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/object-storage/section_object-storage-install.xml:35(para) +msgid "This document demonstrates how to install a cluster by using the following types of nodes:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/object-storage/section_object-storage-install.xml:39(para) +msgid "One proxy node which runs the swift-proxy-server processes. The proxy server proxies requests to the appropriate storage nodes." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/object-storage/section_object-storage-install.xml:45(para) +msgid "Five storage nodes that run the swift-account-server, swift-container-server, and swift-object-server processes which control storage of the account databases, the container databases, as well as the actual stored objects." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/object-storage/section_object-storage-install.xml:58(para) +msgid "Fewer storage nodes can be used initially, but a minimum of five is recommended for a production cluster." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/object-storage/section_object-storage-install.xml:63(title) +msgid "General installation steps" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/object-storage/section_object-storage-install.xml:66(para) +msgid "Create a swift user that the Object Storage Service can use to authenticate with the Identity Service. Choose a password and specify an email address for the swift user. Use the service tenant and give the user the admin role:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/object-storage/section_object-storage-install.xml:73(replaceable) +msgid "swift@example.com" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/object-storage/section_object-storage-install.xml:77(para) +msgid "Create a service entry for the Object Storage Service:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/object-storage/section_object-storage-install.xml:90(para) +msgid "The service ID is randomly generated and is different from the one shown here." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/object-storage/section_object-storage-install.xml:95(para) +msgid "Specify an API endpoint for the Object Storage Service by using the returned service ID. When you specify an endpoint, you provide URLs for the public API, internal API, and admin API. In this guide, the controller host name is used:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/object-storage/section_object-storage-install.xml:117(para) +msgid "Create the configuration directory on all nodes:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/object-storage/section_object-storage-install.xml:121(para) +msgid "Create /etc/swift/swift.conf on all nodes:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/object-storage/section_object-storage-install.xml:127(para) +msgid "The prefix and suffix value in /etc/swift/swift.conf should be set to some random string of text to be used as a salt when hashing to determine mappings in the ring. This file must be the same on every node in the cluster!" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/object-storage/section_object-storage-install.xml:132(para) +msgid "Next, set up your storage nodes and proxy node. This example uses the Identity Service for the common authentication piece." +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/training-guides/basic-install-guide/object-storage/section_object-storage-network-planning.xml:36(None) +msgid "@@image: '../figures/networking-interactions-swift.png'; md5=2190892da42f344e407b4cef71b8f3cf" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/object-storage/section_object-storage-network-planning.xml:7(title) +msgid "Plan networking for Object Storage" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/object-storage/section_object-storage-network-planning.xml:8(para) +msgid "For both conserving network resources and ensuring that network administrators understand the needs for networks and public IP addresses for providing access to the APIs and storage network as necessary, this section offers recommendations and required minimum sizes. Throughput of at least 1000 Mbps is suggested." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/object-storage/section_object-storage-network-planning.xml:16(para) +msgid "A mandatory public network. Connects to the proxy server." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/object-storage/section_object-storage-network-planning.xml:20(para) +msgid "A mandatory storage network. Not accessible from outside the cluster. All nodes connect to this network." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/object-storage/section_object-storage-network-planning.xml:24(para) +msgid "An optional replication network. Not accessible from outside the cluster. Dedicated to replication traffic among storage nodes. Must be configured in the Ring." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/object-storage/section_object-storage-network-planning.xml:14(para) +msgid "This guide describes the following networks:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/object-storage/section_object-storage-network-planning.xml:29(para) +msgid "This figure shows the basic architecture for the public network, the storage network, and the optional replication network." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/object-storage/section_object-storage-network-planning.xml:39(para) +msgid "By default, all of the OpenStack Object Storage services, as well as the rsync daemon on the storage nodes, are configured to listen on their STORAGE_LOCAL_NET IP addresses." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/object-storage/section_object-storage-network-planning.xml:43(para) +msgid "If you configure a replication network in the Ring, the Account, Container and Object servers listen on both the STORAGE_LOCAL_NET and STORAGE_REPLICATION_NET IP addresses. The rsync daemon only listens on the STORAGE_REPLICATION_NET IP address." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/object-storage/section_object-storage-network-planning.xml:51(term) +msgid "Public Network (Publicly routable IP range)" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/object-storage/section_object-storage-network-planning.xml:53(para) +msgid "Provides public IP accessibility to the API endpoints within the cloud infrastructure." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/object-storage/section_object-storage-network-planning.xml:55(para) +msgid "Minimum size: one IP address for each proxy server." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/object-storage/section_object-storage-network-planning.xml:60(term) +msgid "Storage Network (RFC1918 IP Range, not publicly routable)" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/object-storage/section_object-storage-network-planning.xml:63(para) +msgid "Manages all inter-server communications within the Object Storage infrastructure." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/object-storage/section_object-storage-network-planning.xml:65(para) +msgid "Minimum size: one IP address for each storage node and proxy server." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/object-storage/section_object-storage-network-planning.xml:67(para) +msgid "Recommended size: as above, with room for expansion to the largest your cluster size. For example, 255 or CIDR /24." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/object-storage/section_object-storage-network-planning.xml:73(term) +msgid "Replication Network (RFC1918 IP Range, not publicly routable)" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/object-storage/section_object-storage-network-planning.xml:76(para) +msgid "Manages replication-related communications among storage servers within the Object Storage infrastructure." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/object-storage/section_object-storage-network-planning.xml:78(para) +msgid "Recommended size: as for STORAGE_LOCAL_NET." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/object-storage/section_object-storage-verifying-install.xml:7(title) +msgid "Verify the installation" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/object-storage/section_object-storage-verifying-install.xml:8(para) +msgid "You can run these commands from the proxy server or any server that has access to the Identity Service." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/object-storage/section_object-storage-verifying-install.xml:12(para) +msgid "Make sure that your credentials are set up correctly in the admin-openrc.sh file and source it:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/object-storage/section_object-storage-verifying-install.xml:16(para) +msgid "Run the following command:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/object-storage/section_object-storage-verifying-install.xml:28(para) +msgid "Run the following commands to upload files to a container. Create the test.txt and test2.txt test files locally if needed." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/object-storage/section_object-storage-verifying-install.xml:35(para) +msgid "Run the following command to download all files from the myfiles container:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/object-storage/section_start-storage-node-services.xml:8(title) +msgid "Start services on the storage nodes" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/object-storage/section_start-storage-node-services.xml:9(para) +msgid "Now that the ring files are on each storage node, you can start the services. On each storage node, run the following command:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/object-storage/section_start-storage-node-services.xml:23(para) +msgid "To start all swift services at once, run the command:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/object-storage/section_start-storage-node-services.xml:25(para) +msgid "To know more about swift-init command, run:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/object-storage/section_object-storage-install-config-storage-nodes.xml:7(title) +msgid "Install and configure storage nodes" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/object-storage/section_object-storage-install-config-storage-nodes.xml:9(para) +msgid "Object Storage works on any file system that supports Extended Attributes (XATTRS). XFS shows the best overall performance for the swift use case after considerable testing and benchmarking at Rackspace. It is also the only file system that has been thoroughly tested. See the OpenStack Configuration Reference for additional recommendations." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/object-storage/section_object-storage-install-config-storage-nodes.xml:21(para) +msgid "Install storage node packages:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/object-storage/section_object-storage-install-config-storage-nodes.xml:30(para) +msgid "For each device on the node that you want to use for storage, set up the XFS volume (/dev/sdb is used as an example). Use a single partition per drive. For example, in a server with 12 disks you may use one or two disks for the operating system which should not be touched in this step. The other 10 or 11 disks should be partitioned with a single partition, then formatted in XFS." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/object-storage/section_object-storage-install-config-storage-nodes.xml:47(para) +msgid "Create /etc/rsyncd.conf:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/object-storage/section_object-storage-install-config-storage-nodes.xml:49(para) +msgid "Replace the content of /etc/rsyncd.conf with:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/object-storage/section_object-storage-install-config-storage-nodes.xml:76(para) +msgid "(Optional) If you want to separate rsync and replication traffic to replication network, set STORAGE_REPLICATION_NET_IP instead of STORAGE_LOCAL_NET_IP:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/object-storage/section_object-storage-install-config-storage-nodes.xml:84(para) +msgid "Edit the following line in /etc/default/rsync:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/object-storage/section_object-storage-install-config-storage-nodes.xml:89(para) +msgid "Edit the following line in /etc/xinetd.d/rsync:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/object-storage/section_object-storage-install-config-storage-nodes.xml:94(para) +msgid "Start the rsync service:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/object-storage/section_object-storage-install-config-storage-nodes.xml:97(para) +msgid "Start the xinetd service:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/object-storage/section_object-storage-install-config-storage-nodes.xml:100(para) +msgid "Start the xinetd service and configure it to start when the system boots:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/object-storage/section_object-storage-install-config-storage-nodes.xml:106(para) +msgid "The rsync service requires no authentication, so run it on a local, private network." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/object-storage/section_object-storage-install-config-storage-nodes.xml:111(para) +msgid "Create the swift recon cache directory and set its permissions:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/object-storage/section_object-storage-sys-requirements.xml:12(title) +msgid "System requirements for Object Storage" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/object-storage/section_object-storage-sys-requirements.xml:13(para) +msgid "Hardware: OpenStack Object Storage is designed to run on commodity hardware." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/object-storage/section_object-storage-sys-requirements.xml:16(para) +msgid "When you install only the Object Storage and Identity Service, you cannot use the dashboard unless you also install Compute and the Image Service." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/object-storage/section_object-storage-sys-requirements.xml:21(caption) +msgid "Hardware recommendations" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/object-storage/section_object-storage-sys-requirements.xml:28(td) +msgid "Server" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/object-storage/section_object-storage-sys-requirements.xml:29(td) +msgid "Recommended Hardware" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/object-storage/section_object-storage-sys-requirements.xml:35(para) +msgid "Object Storage object servers" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/object-storage/section_object-storage-sys-requirements.xml:37(para) ./doc/training-guides/basic-install-guide/object-storage/section_object-storage-sys-requirements.xml:66(para) ./doc/training-guides/basic-install-guide/object-storage/section_object-storage-sys-requirements.xml:76(para) +msgid "Processor: dual quad core" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/object-storage/section_object-storage-sys-requirements.xml:38(para) ./doc/training-guides/basic-install-guide/object-storage/section_object-storage-sys-requirements.xml:67(para) +msgid "Memory: 8 or 12 GB RAM" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/object-storage/section_object-storage-sys-requirements.xml:39(para) +msgid "Disk space: optimized for cost per GB" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/object-storage/section_object-storage-sys-requirements.xml:40(para) ./doc/training-guides/basic-install-guide/object-storage/section_object-storage-sys-requirements.xml:68(para) ./doc/training-guides/basic-install-guide/object-storage/section_object-storage-sys-requirements.xml:77(para) +msgid "Network: one 1 GB Network Interface Card (NIC)" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/object-storage/section_object-storage-sys-requirements.xml:42(para) +msgid "The amount of disk space depends on how much you can fit into the rack efficiently. You want to optimize these for best cost per GB while still getting industry-standard failure rates. At Rackspace, our storage servers are currently running fairly generic 4U servers with 24 2T SATA drives and 8 cores of processing power. RAID on the storage drives is not required and not recommended. Swift's disk usage pattern is the worst case possible for RAID, and performance degrades very quickly using RAID 5 or 6." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/object-storage/section_object-storage-sys-requirements.xml:54(para) +msgid "As an example, Rackspace runs Cloud Files storage servers with 24 2T SATA drives and 8 cores of processing power. Most services support either a worker or concurrency value in the settings. This allows the services to make effective use of the cores available." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/object-storage/section_object-storage-sys-requirements.xml:63(para) +msgid "Object Storage container/account servers" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/object-storage/section_object-storage-sys-requirements.xml:70(para) +msgid "Optimized for IOPS due to tracking with SQLite databases." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/object-storage/section_object-storage-sys-requirements.xml:74(para) +msgid "Object Storage proxy server" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/object-storage/section_object-storage-sys-requirements.xml:79(para) +msgid "Higher network throughput offers better performance for supporting many API requests." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/object-storage/section_object-storage-sys-requirements.xml:82(para) +msgid "Optimize your proxy servers for best CPU performance. The Proxy Services are more CPU and network I/O intensive. If you are using 10 GB networking to the proxy, or are terminating SSL traffic at the proxy, greater CPU power is required." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/object-storage/section_object-storage-sys-requirements.xml:91(para) +msgid "Operating system: OpenStack Object Storage currently runs on Ubuntu, RHEL, CentOS, Fedora, openSUSE, or SLES." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/object-storage/section_object-storage-sys-requirements.xml:94(para) +msgid "Networking: 1 Gbps or 10 Gbps is suggested internally. For OpenStack Object Storage, an external network should connect the outside world to the proxy servers, and the storage network is intended to be isolated on a private network or multiple private networks." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/object-storage/section_object-storage-sys-requirements.xml:99(para) +msgid "Database: For OpenStack Object Storage, a SQLite database is part of the OpenStack Object Storage container and account management process." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/object-storage/section_object-storage-sys-requirements.xml:103(para) +msgid "Permissions: You can install OpenStack Object Storage either as root or as a user with sudo permissions if you configure the sudoers file to enable all the permissions." +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/training-guides/basic-install-guide/object-storage/section_object-storage-example-install-arch.xml:53(None) +msgid "@@image: '../figures/swift_install_arch.png'; md5=bbda527d20235d54a95eb29279ba2680" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/object-storage/section_object-storage-example-install-arch.xml:7(title) +msgid "Example of Object Storage installation architecture" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/object-storage/section_object-storage-example-install-arch.xml:10(para) +msgid "Node: A host machine that runs one or more OpenStack Object Storage services." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/object-storage/section_object-storage-example-install-arch.xml:14(para) +msgid "Proxy node: Runs proxy services." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/object-storage/section_object-storage-example-install-arch.xml:17(para) +msgid "Storage node: Runs account, container, and object services. Contains the SQLite databases." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/object-storage/section_object-storage-example-install-arch.xml:21(para) +msgid "Ring: A set of mappings between OpenStack Object Storage data to physical devices." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/object-storage/section_object-storage-example-install-arch.xml:25(para) +msgid "Replica: A copy of an object. By default, three copies are maintained in the cluster." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/object-storage/section_object-storage-example-install-arch.xml:29(para) +msgid "Zone: A logically separate section of the cluster, related to independent failure characteristics." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/object-storage/section_object-storage-example-install-arch.xml:33(para) +msgid "Region (optional): A logically separate section of the cluster, representing distinct physical locations such as cities or countries. Similar to zones but representing physical locations of portions of the cluster rather than logical segments." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/object-storage/section_object-storage-example-install-arch.xml:40(para) +msgid "To increase reliability and performance, you can add additional proxy servers." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/object-storage/section_object-storage-example-install-arch.xml:42(para) +msgid "This document describes each storage node as a separate zone in the ring. At a minimum, five zones are recommended. A zone is a group of nodes that are as isolated as possible from other nodes (separate servers, network, power, even geography). The ring guarantees that every replica is stored in a separate zone. This diagram shows one possible configuration for a minimal installation:" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-arch.xml:23(None) +msgid "@@image: '../common/figures/objectstorage-arch.png'; md5=90f6c7cf3947d7987eeb55d657cdc927" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-arch.xml:60(None) +msgid "@@image: '../common/figures/objectstorage-nodes.png'; md5=2aa7eb3bddcf6826f33469920dc2a9c3" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-arch.xml:11(title) +msgid "Cluster architecture" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-arch.xml:13(title) +msgid "Access tier" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-arch.xml:14(para) +msgid "Large-scale deployments segment off an access tier, which is considered the Object Storage system's central hub. The access tier fields the incoming API requests from clients and moves data in and out of the system. This tier consists of front-end load balancers, ssl-terminators, and authentication services. It runs the (distributed) brain of the Object Storage system: the proxy server processes." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-arch.xml:20(title) +msgid "Object Storage architecture" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-arch.xml:27(para) +msgid "Because access servers are collocated in their own tier, you can scale out read/write access regardless of the storage capacity. For example, if a cluster is on the public Internet, requires SSL termination, and has a high demand for data access, you can provision many access servers. However, if the cluster is on a private network and used primarily for archival purposes, you need fewer access servers." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-arch.xml:32(para) +msgid "Since this is an HTTP addressable storage service, you may incorporate a load balancer into the access tier." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-arch.xml:34(para) +msgid "Typically, the tier consists of a collection of 1U servers. These machines use a moderate amount of RAM and are network I/O intensive. Since these systems field each incoming API request, you should provision them with two high-throughput (10GbE) interfaces - one for the incoming \"front-end\" requests and the other for the \"back-end\" access to the object storage nodes to put and fetch data." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-arch.xml:40(title) ./doc/training-guides/basic-install-guide/common/section_objectstorage-arch.xml:69(title) +msgid "Factors to consider" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-arch.xml:41(para) +msgid "For most publicly facing deployments as well as private deployments available across a wide-reaching corporate network, you use SSL to encrypt traffic to the client. SSL adds significant processing load to establish sessions between clients, which is why you have to provision more capacity in the access layer. SSL may not be required for private deployments on trusted networks." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-arch.xml:49(title) +msgid "Storage nodes" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-arch.xml:50(para) +msgid "In most configurations, each of the five zones should have an equal amount of storage capacity. Storage nodes use a reasonable amount of memory and CPU. Metadata needs to be readily available to return objects quickly. The object stores run services not only to field incoming requests from the access tier, but to also run replicators, auditors, and reapers. You can provision object stores provisioned with single gigabit or 10 gigabit network interface depending on the expected workload and desired performance." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-arch.xml:57(title) ./doc/training-guides/basic-install-guide/common/section_objectstorage-characteristics.xml:46(title) +msgid "Object Storage (swift)" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-arch.xml:64(para) +msgid "Currently, a 2 TB or 3 TB SATA disk delivers good performance for the price. You can use desktop-grade drives if you have responsive remote hands in the datacenter and enterprise-grade drives if you don't." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-arch.xml:70(para) +msgid "You should keep in mind the desired I/O performance for single-threaded requests . This system does not use RAID, so a single disk handles each request for an object. Disk performance impacts single-threaded response rates." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-arch.xml:73(para) +msgid "To achieve apparent higher throughput, the object storage system is designed to handle concurrent uploads/downloads. The network I/O capacity (1GbE, bonded 1GbE pair, or 10GbE) should match your desired concurrent throughput needs for reads and writes." +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/training-guides/basic-install-guide/common/section_compute-configure-vnc.xml:64(None) +msgid "@@image: '../common/figures/novnc/SCH_5009_V00_NUAC-VNC_OpenStack.png'; md5=182dc38019a220c851e1c94aa50f4565" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_compute-configure-vnc.xml:7(title) +msgid "VNC console proxy" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_compute-configure-vnc.xml:8(para) +msgid "The VNC proxy is an OpenStack component that enables compute service users to access their instances through VNC clients." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_compute-configure-vnc.xml:11(para) +msgid "The VNC console connection works as follows:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_compute-configure-vnc.xml:14(para) +msgid "A user connects to the API and gets an access_url such as, http://ip:port/?token=xyz." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_compute-configure-vnc.xml:20(para) +msgid "The user pastes the URL in a browser or uses it as a client parameter." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_compute-configure-vnc.xml:24(para) +msgid "The browser or client connects to the proxy." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_compute-configure-vnc.xml:27(para) +msgid "The proxy talks to nova-consoleauth to authorize the token for the user, and maps the token to the private host and port of the VNC server for an instance." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_compute-configure-vnc.xml:32(para) +msgid "The compute host specifies the address that the proxy should use to connect through the nova.conf file option, . In this way, the VNC proxy works as a bridge between the public network and private host network." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_compute-configure-vnc.xml:40(para) +msgid "The proxy initiates the connection to VNC server and continues to proxy until the session ends." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_compute-configure-vnc.xml:44(para) +msgid "The proxy also tunnels the VNC protocol over WebSockets so that the noVNC client can talk to VNC servers. In general, the VNC proxy:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_compute-configure-vnc.xml:49(para) +msgid "Bridges between the public network where the clients live and the private network where VNC servers live." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_compute-configure-vnc.xml:53(para) +msgid "Mediates token authentication." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_compute-configure-vnc.xml:56(para) +msgid "Transparently deals with hypervisor-specific connection details to provide a uniform client experience." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_compute-configure-vnc.xml:59(title) +msgid "noVNC process" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_compute-configure-vnc.xml:72(title) +msgid "About nova-consoleauth" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_compute-configure-vnc.xml:74(para) +msgid "Both client proxies leverage a shared service to manage token authentication called nova-consoleauth. This service must be running for either proxy to work. Many proxies of either type can be run against a single nova-consoleauth service in a cluster configuration." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_compute-configure-vnc.xml:81(para) +msgid "Do not confuse the nova-consoleauth shared service with nova-console, which is a XenAPI-specific service that most recent VNC proxy architectures do not use." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_compute-configure-vnc.xml:88(title) +msgid "Typical deployment" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_compute-configure-vnc.xml:89(para) +msgid "A typical deployment has the following components:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_compute-configure-vnc.xml:92(para) +msgid "A nova-consoleauth process. Typically runs on the controller host." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_compute-configure-vnc.xml:97(para) +msgid "One or more nova-novncproxy services. Supports browser-based noVNC clients. For simple deployments, this service typically runs on the same machine as nova-api because it operates as a proxy between the public network and the private compute host network." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_compute-configure-vnc.xml:106(para) +msgid "One or more nova-xvpvncproxy services. Supports the special Java client discussed here. For simple deployments, this service typically runs on the same machine as nova-api because it acts as a proxy between the public network and the private compute host network." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_compute-configure-vnc.xml:115(para) +msgid "One or more compute hosts. These compute hosts must have correctly configured options, as follows." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_compute-configure-vnc.xml:121(title) +msgid "VNC configuration options" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_compute-configure-vnc.xml:122(para) +msgid "To customize the VNC console, use the following configuration options:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_compute-configure-vnc.xml:125(para) +msgid "To support live migration, you cannot specify a specific IP address for vncserver_listen, because that IP address does not exist on the destination host." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_compute-configure-vnc.xml:135(para) +msgid "The vncserver_proxyclient_address defaults to 127.0.0.1, which is the address of the compute host that Compute instructs proxies to use when connecting to instance servers." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_compute-configure-vnc.xml:140(para) +msgid "For all-in-one XenServer domU deployments, set this to 169.254.0.1." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_compute-configure-vnc.xml:141(para) +msgid "For multi-host XenServer domU deployments, set to a dom0 management IP on the same network as the proxies." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_compute-configure-vnc.xml:143(para) +msgid "For multi-host libvirt deployments, set to a host management IP on the same network as the proxies." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_compute-configure-vnc.xml:151(title) +msgid "nova-novncproxy (noVNC)" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_compute-configure-vnc.xml:153(para) +msgid "You must install the noVNC package, which contains the nova-novncproxy service. As root, run the following command:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_compute-configure-vnc.xml:157(para) +msgid "The service starts automatically on installation." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_compute-configure-vnc.xml:158(para) +msgid "To restart the service, run:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_compute-configure-vnc.xml:160(para) +msgid "The configuration option parameter should point to your nova.conf file, which includes the message queue server address and credentials." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_compute-configure-vnc.xml:163(para) +msgid "By default, nova-novncproxy binds on 0.0.0.0:6080." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_compute-configure-vnc.xml:166(para) +msgid "To connect the service to your Compute deployment, add the following configuration options to your nova.conf file:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_compute-configure-vnc.xml:170(para) +msgid "vncserver_listen=0.0.0.0" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_compute-configure-vnc.xml:173(para) +msgid "Specifies the address on which the VNC service should bind. Make sure it is assigned one of the compute node interfaces. This address is the one used by your domain file." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_compute-configure-vnc.xml:179(para) +msgid "To use live migration, use the 0.0.0.0 address." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_compute-configure-vnc.xml:184(para) +msgid "vncserver_proxyclient_address=127.0.0.1" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_compute-configure-vnc.xml:187(para) +msgid "The address of the compute host that Compute instructs proxies to use when connecting to instance vncservers." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_compute-configure-vnc.xml:194(title) +msgid "Frequently asked questions about VNC access to virtual machines" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_compute-configure-vnc.xml:200(literal) +msgid "nova-xvpvncproxy" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_compute-configure-vnc.xml:201(systemitem) +msgid "nova-novncproxy" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_compute-configure-vnc.xml:199(emphasis) +msgid "Q: What is the difference between and ?" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_compute-configure-vnc.xml:203(para) +msgid "A: nova-xvpvncproxy, which ships with OpenStack Compute, is a proxy that supports a simple Java client. nova-novncproxy uses noVNC to provide VNC support through a web browser." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_compute-configure-vnc.xml:209(emphasis) +msgid "Q: I want VNC support in the OpenStack dashboard. What services do I need?" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_compute-configure-vnc.xml:211(para) +msgid "A: You need nova-novncproxy, nova-consoleauth, and correctly configured compute hosts." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_compute-configure-vnc.xml:217(emphasis) +msgid "Q: When I use or click on the VNC tab of the OpenStack dashboard, it hangs. Why?" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_compute-configure-vnc.xml:219(para) +msgid "A: Make sure you are running nova-consoleauth (in addition to nova-novncproxy). The proxies rely on nova-consoleauth to validate tokens, and waits for a reply from them until a timeout is reached." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_compute-configure-vnc.xml:228(emphasis) +msgid "Q: My VNC proxy worked fine during my all-in-one test, but now it doesn't work on multi host. Why?" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_compute-configure-vnc.xml:231(para) +msgid "A: The default options work for an all-in-one install, but changes must be made on your compute hosts once you start to build a cluster. As an example, suppose you have two servers:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_compute-configure-vnc.xml:237(para) +msgid "Your nova-compute configuration file must set the following values:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_compute-configure-vnc.xml:249(para) +msgid "novncproxy_base_url and xvpvncproxy_base_url use a public IP; this is the URL that is ultimately returned to clients, which generally do not have access to your private network. Your PROXYSERVER must be able to reach vncserver_proxyclient_address, because that is the address over which the VNC connection is proxied." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_compute-configure-vnc.xml:261(emphasis) +msgid "Q: My noVNC does not work with recent versions of web browsers. Why?" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_compute-configure-vnc.xml:264(para) +msgid "A: Make sure you have installed python-numpy, which is required to support a newer version of the WebSocket protocol (HyBi-07+)." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_compute-configure-vnc.xml:271(emphasis) +msgid "Q: How do I adjust the dimensions of the VNC window image in the OpenStack dashboard?" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_compute-configure-vnc.xml:274(para) +msgid "A: These values are hard-coded in a Django HTML template. To alter them, edit the _detail_vnc.html template file. The location of this file varies based on Linux distribution. On Ubuntu 12.04, the file is at /usr/share/pyshared/horizon/dashboards/nova/instances/templates/instances/_detail_vnc.html." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_compute-configure-vnc.xml:280(para) +msgid "Modify the and options, as follows:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-troubleshoot.xml:7(title) +msgid "Troubleshoot Object Storage" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-troubleshoot.xml:8(para) +msgid "For Object Storage, everything is logged in /var/log/syslog (or messages on some distros). Several settings enable further customization of logging, such as log_name, log_facility, and log_level, within the object server configuration files." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-troubleshoot.xml:12(title) +msgid "Drive failure" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-troubleshoot.xml:13(para) +msgid "In the event that a drive has failed, the first step is to make sure the drive is unmounted. This will make it easier for Object Storage to work around the failure until it has been resolved. If the drive is going to be replaced immediately, then it is just best to replace the drive, format it, remount it, and let replication fill it up." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-troubleshoot.xml:17(para) +msgid "If the drive can’t be replaced immediately, then it is best to leave it unmounted, and remove the drive from the ring. This will allow all the replicas that were on that drive to be replicated elsewhere until the drive is replaced. Once the drive is replaced, it can be re-added to the ring." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-troubleshoot.xml:21(para) +msgid "You can look at error messages in /var/log/kern.log for hints of drive failure." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-troubleshoot.xml:24(title) +msgid "Server failure" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-troubleshoot.xml:25(para) +msgid "If a server is having hardware issues, it is a good idea to make sure the Object Storage services are not running. This will allow Object Storage to work around the failure while you troubleshoot." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-troubleshoot.xml:28(para) +msgid "If the server just needs a reboot, or a small amount of work that should only last a couple of hours, then it is probably best to let Object Storage work around the failure and get the machine fixed and back online. When the machine comes back online, replication will make sure that anything that is missing during the downtime will get updated." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-troubleshoot.xml:33(para) +msgid "If the server has more serious issues, then it is probably best to remove all of the server’s devices from the ring. Once the server has been repaired and is back online, the server’s devices can be added back into the ring. It is important that the devices are reformatted before putting them back into the ring as it is likely to be responsible for a different set of partitions than before." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-troubleshoot.xml:41(title) +msgid "Detect failed drives" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-troubleshoot.xml:42(para) +msgid "It has been our experience that when a drive is about to fail, error messages will spew into /var/log/kern.log. There is a script called swift-drive-audit that can be run via cron to watch for bad drives. If errors are detected, it will unmount the bad drive, so that Object Storage can work around it. The script takes a configuration file with the following settings:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-troubleshoot.xml:48(para) +msgid "This script has only been tested on Ubuntu 10.04, so if you are using a different distro or OS, some care should be taken before using in production." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-troubleshoot.xml:53(title) +msgid "Emergency recovery of ring builder files" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-troubleshoot.xml:54(para) +msgid "You should always keep a backup of swift ring builder files. However, if an emergency occurs, this procedure may assist in returning your cluster to an operational state." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-troubleshoot.xml:57(para) +msgid "Using existing swift tools, there is no way to recover a builder file from a ring.gz file. However, if you have a knowledge of Python, it is possible to construct a builder file that is pretty close to the one you have lost. The following is what you will need to do." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-troubleshoot.xml:62(para) +msgid "This procedure is a last-resort for emergency circumstances. It requires knowledge of the swift python code and may not succeed." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-troubleshoot.xml:65(para) +msgid "First, load the ring and a new ringbuilder object in a Python REPL:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-troubleshoot.xml:68(para) +msgid "Now, start copying the data we have in the ring into the builder." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-troubleshoot.xml:85(para) +msgid "This is the extent of the recoverable fields. For min_part_hours you'll either have to remember what the value you used was, or just make up a new one." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-troubleshoot.xml:90(para) +msgid "Try some validation: if this doesn't raise an exception, you may feel some hope. Not too much, though." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-troubleshoot.xml:93(para) +msgid "Save the builder." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-troubleshoot.xml:97(para) +msgid "You should now have a file called 'account.builder' in the current working directory. Next, run swift-ring-builder account.builder write_ring and compare the new account.ring.gz to the account.ring.gz that you started from. They probably won't be byte-for-byte identical, but if you load them up in a REPL and their _replica2part2dev_id and devs attributes are the same (or nearly so), then you're in good shape." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-troubleshoot.xml:104(para) +msgid "Next, repeat the procedure for container.ring.gz and object.ring.gz, and you might get usable builder files." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-account-reaper.xml:7(title) +msgid "Account reaper" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-account-reaper.xml:8(para) +msgid "In the background, the account reaper removes data from the deleted accounts." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-account-reaper.xml:9(para) +msgid "A reseller marks an account for deletion by issuing a DELETE request on the account’s storage URL. This action sets the status column of the account_stat table in the account database and replicas to DELETED, marking the account's data for deletion." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-account-reaper.xml:17(para) +msgid "It's on the developers' to-do list to write a utility that performs this task, preferably through a ReST call." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-account-reaper.xml:12(para) +msgid "Typically, a specific retention time or undelete are not provided. However, you can set a delay_reaping value in the [account-reaper] section of the account-server.conf to delay the actual deletion of data. At this time, to undelete you have to update the account database replicas directly, setting the status column to an empty string and updating the put_timestamp to be greater than the delete_timestamp. " +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-account-reaper.xml:20(para) +msgid "The account reaper runs on each account server and scans the server occasionally for account databases marked for deletion. It only fires up on the accounts for which the server is the primary node, so that multiple account servers aren’t trying to do it simultaneously. Using multiple servers to delete one account might improve the deletion speed but requires coordination to avoid duplication. Speed really is not a big concern with data deletion, and large accounts aren’t deleted often." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-account-reaper.xml:26(para) +msgid "Deleting an account is simple. For each account container, all objects are deleted and then the container is deleted. Deletion requests that fail will not stop the overall process but will cause the overall process to fail eventually (for example, if an object delete times out, you will not be able to delete the container or the account). The account reaper keeps trying to delete an account until it is empty, at which point the database reclaim process within the db_replicator will remove the database files." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-account-reaper.xml:32(para) +msgid "A persistent error state may prevent the deletion of an object or container. If this happens, you will see a message such as “Account <name> has not been reaped since <date>” in the log. You can control when this is logged with the reap_warn_after value in the [account-reaper] section of the account-server.conf file. The default value is 30 days." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage_tenant-specific-image-storage.xml:7(title) +msgid "Configure tenant-specific image locations with Object Storage" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage_tenant-specific-image-storage.xml:15(para) +msgid "The tenant who owns the image" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage_tenant-specific-image-storage.xml:18(para) +msgid "Tenants that are defined in and that have admin-level accounts" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage_tenant-specific-image-storage.xml:9(para) +msgid "For some deployers, it is not ideal to store all images in one place to enable all tenants and users to access them. You can configure the Image Service to store image data in tenant-specific image locations. Then, only the following tenants can use the Image Service to access the created image:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage_tenant-specific-image-storage.xml:24(title) +msgid "To configure tenant-specific image locations" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage_tenant-specific-image-storage.xml:26(para) +msgid "Configure swift as your in the glance-api.conf file." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage_tenant-specific-image-storage.xml:34(para) +msgid ". Set to True to enable tenant-specific storage locations. Default is False." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage_tenant-specific-image-storage.xml:40(para) +msgid ". Specify a list of tenant IDs that can grant read and write access to all Object Storage containers that are created by the Image Service." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage_tenant-specific-image-storage.xml:31(para) +msgid "Set these configuration options in the glance-api.conf file: " +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage_tenant-specific-image-storage.xml:49(para) +msgid "With this configuration, images are stored in an Object Storage service (swift) endpoint that is pulled from the service catalog for the authenticated user." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-ringbuilder.xml:7(title) +msgid "Ring-builder" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-ringbuilder.xml:8(para) +msgid "Use the swift-ring-builder utility to build and manage rings. This utility assigns partitions to devices and writes an optimized Python structure to a gzipped, serialized file on disk for transmission to the servers. The server processes occasionally check the modification time of the file and reload in-memory copies of the ring structure as needed. If you use a slightly older version of the ring, one of the three replicas for a partition subset will be incorrect because of the way the ring-builder manages changes to the ring. You can work around this issue." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-ringbuilder.xml:18(para) +msgid "The ring-builder also keeps its own builder file with the ring information and additional data required to build future rings. It is very important to keep multiple backup copies of these builder files. One option is to copy the builder files out to every server while copying the ring files themselves. Another is to upload the builder files into the cluster itself. If you lose the builder file, you have to create a new ring from scratch. Nearly all partitions would be assigned to different devices and, therefore, nearly all of the stored data would have to be replicated to new locations. So, recovery from a builder file loss is possible, but data would be unreachable for an extended time." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-ringbuilder.xml:31(title) +msgid "Ring data structure" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-ringbuilder.xml:32(para) +msgid "The ring data structure consists of three top level fields: a list of devices in the cluster, a list of lists of device ids indicating partition to device assignments, and an integer indicating the number of bits to shift an MD5 hash to calculate the partition for the hash." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-ringbuilder.xml:39(title) +msgid "Partition assignment list" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-ringbuilder.xml:40(para) +msgid "This is a list of array(‘H’) of devices ids. The outermost list contains an array(‘H’) for each replica. Each array(‘H’) has a length equal to the partition count for the ring. Each integer in the array(‘H’) is an index into the above list of devices. The partition list is known internally to the Ring class as _replica2part2dev_id." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-ringbuilder.xml:49(para) +msgid "So, to create a list of device dictionaries assigned to a partition, the Python code would look like: " +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-ringbuilder.xml:53(para) +msgid "That code is a little simplistic because it does not account for the removal of duplicate devices. If a ring has more replicas than devices, a partition will have more than one replica on a device." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-ringbuilder.xml:57(para) +msgid "array(‘H’) is used for memory conservation as there may be millions of partitions." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-ringbuilder.xml:62(title) +msgid "Replica counts" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-ringbuilder.xml:63(para) +msgid "To support the gradual change in replica counts, a ring can have a real number of replicas and is not restricted to an integer number of replicas." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-ringbuilder.xml:66(para) +msgid "A fractional replica count is for the whole ring and not for individual partitions. It indicates the average number of replicas for each partition. For example, a replica count of 3.2 means that 20 percent of partitions have four replicas and 80 percent have three replicas." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-ringbuilder.xml:71(para) +msgid "The replica count is adjustable." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-ringbuilder.xml:72(para) +msgid "Example:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-ringbuilder.xml:75(para) +msgid "You must rebalance the replica ring in globally distributed clusters. Operators of these clusters generally want an equal number of replicas and regions. Therefore, when an operator adds or removes a region, the operator adds or removes a replica. Removing unneeded replicas saves on the cost of disks." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-ringbuilder.xml:81(para) +msgid "You can gradually increase the replica count at a rate that does not adversely affect cluster performance." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-ringbuilder.xml:83(para) +msgid "For example:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-ringbuilder.xml:91(para) +msgid "Changes take effect after the ring is rebalanced. Therefore, if you intend to change from 3 replicas to 3.01 but you accidentally type 2.01, no data is lost." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-ringbuilder.xml:96(replaceable) +msgid "X.builder" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-ringbuilder.xml:95(para) +msgid "Additionally, can now take a decimal argument for the number of replicas." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-ringbuilder.xml:101(title) +msgid "Partition shift value" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-ringbuilder.xml:102(para) +msgid "The partition shift value is known internally to the Ring class as _part_shift. This value is used to shift an MD5 hash to calculate the partition where the data for that hash should reside. Only the top four bytes of the hash is used in this process. For example, to compute the partition for the /account/container/object path, the Python code might look like the following code: " +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-ringbuilder.xml:113(para) +msgid "For a ring generated with part_power P, the partition shift value is 32 - P." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-ringbuilder.xml:117(title) +msgid "Build the ring" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-ringbuilder.xml:118(para) +msgid "The ring builder process includes these high-level steps:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-ringbuilder.xml:122(para) +msgid "The utility calculates the number of partitions to assign to each device based on the weight of the device. For example, for a partition at the power of 20, the ring has 1,048,576 partitions. One thousand devices of equal weight each want 1,048.576 partitions. The devices are sorted by the number of partitions they desire and kept in order throughout the initialization process." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-ringbuilder.xml:132(para) +msgid "Each device is also assigned a random tiebreaker value that is used when two devices desire the same number of partitions. This tiebreaker is not stored on disk anywhere, and so two different rings created with the same parameters will have different partition assignments. For repeatable partition assignments, RingBuilder.rebalance() takes an optional seed value that seeds the Python pseudo-random number generator." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-ringbuilder.xml:146(para) +msgid "The ring builder assigns each partition replica to the device that requires most partitions at that point while keeping it as far away as possible from other replicas. The ring builder prefers to assign a replica to a device in a region that does not already have a replica. If no such region is available, the ring builder searches for a device in a different zone, or on a different server. If it does not find one, it looks for a device with no replicas. Finally, if all options are exhausted, the ring builder assigns the replica to the device that has the fewest replicas already assigned." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-ringbuilder.xml:160(para) +msgid "The ring builder assigns multiple replicas to one device only if the ring has fewer devices than it has replicas." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-ringbuilder.xml:166(para) +msgid "When building a new ring from an old ring, the ring builder recalculates the desired number of partitions that each device wants." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-ringbuilder.xml:175(para) +msgid "The ring builder unassigns any assigned partitions from any removed devices and adds these partitions to the gathered list." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-ringbuilder.xml:181(para) +msgid "The ring builder unassigns any partition replicas that can be spread out for better durability and adds these partitions to the gathered list." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-ringbuilder.xml:188(para) +msgid "The ring builder unassigns random partitions from any devices that have more partitions than they need and adds these partitions to the gathered list." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-ringbuilder.xml:171(para) +msgid "The ring builder unassigns partitions and gathers these partitions for reassignment, as follows: " +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-ringbuilder.xml:198(para) +msgid "The ring builder reassigns the gathered partitions to devices by using a similar method to the one described previously." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-ringbuilder.xml:203(para) +msgid "When the ring builder reassigns a replica to a partition, the ring builder records the time of the reassignment. The ring builder uses this value when it gathers partitions for reassignment so that no partition is moved twice in a configurable amount of time. The RingBuilder class knows this configurable amount of time as min_part_hours. The ring builder ignores this restriction for replicas of partitions on removed devices because removal of a device happens on device failure only, and reassignment is the only choice." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-ringbuilder.xml:217(para) +msgid "Theses steps do not always perfectly rebalance a ring due to the random nature of gathering partitions for reassignment. To help reach a more balanced ring, the rebalance process is repeated until near perfect (less than 1 percent off) or when the balance does not improve by at least 1 percent (indicating we probably cannot get perfect balance due to wildly imbalanced zones or too many partitions recently moved)." +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-characteristics.xml:49(None) +msgid "@@image: '../common/figures/objectstorage.png'; md5=e26e374ace84070f5fed24e73adcd562" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-characteristics.xml:7(title) +msgid "Object Storage characteristics" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-characteristics.xml:8(para) +msgid "The key characteristics of Object Storage are that:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-characteristics.xml:11(para) +msgid "All objects stored in Object Storage have a URL." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-characteristics.xml:14(para) +msgid "All objects stored are replicated 3✕ in as-unique-as-possible zones, which can be defined as a group of drives, a node, a rack, and so on." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-characteristics.xml:18(para) +msgid "All objects have their own metadata." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-characteristics.xml:21(para) +msgid "Developers interact with the object storage system through a RESTful HTTP API." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-characteristics.xml:25(para) +msgid "Object data can be located anywhere in the cluster." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-characteristics.xml:28(para) +msgid "The cluster scales by adding additional nodes without sacrificing performance, which allows a more cost-effective linear storage expansion than fork-lift upgrades." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-characteristics.xml:33(para) +msgid "Data doesn't have to be migrate to an entirely new storage system." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-characteristics.xml:36(para) +msgid "New nodes can be added to the cluster without downtime." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-characteristics.xml:39(para) +msgid "Failed nodes and disks can be swapped out without downtime." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-characteristics.xml:42(para) +msgid "It runs on industry-standard hardware, such as Dell, HP, and Supermicro." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-characteristics.xml:53(para) +msgid "Developers can either write directly to the Swift API or use one of the many client libraries that exist for all of the popular programming languages, such as Java, Python, Ruby, and C#. Amazon S3 and RackSpace Cloud Files users should be very familiar with Object Storage. Users new to object storage systems will have to adjust to a different approach and mindset than those required for a traditional filesystem." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-replication.xml:7(title) ./doc/training-guides/basic-install-guide/common/section_objectstorage-components.xml:192(title) ./doc/training-guides/common/module003-ch006-more-concepts.xml:156(guilabel) +msgid "Replication" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-replication.xml:8(para) +msgid "Because each replica in Object Storage functions independently and clients generally require only a simple majority of nodes to respond to consider an operation successful, transient failures like network partitions can quickly cause replicas to diverge. These differences are eventually reconciled by asynchronous, peer-to-peer replicator processes. The replicator processes traverse their local file systems and concurrently perform operations in a manner that balances load across physical disks." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-replication.xml:17(para) +msgid "Replication uses a push model, with records and files generally only being copied from local to remote replicas. This is important because data on the node might not belong there (as in the case of hand offs and ring changes), and a replicator cannot know which data it should pull in from elsewhere in the cluster. Any node that contains data must ensure that data gets to where it belongs. The ring handles replica placement." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-replication.xml:25(para) +msgid "To replicate deletions in addition to creations, every deleted record or file in the system is marked by a tombstone. The replication process cleans up tombstones after a time period known as the consistency window. This window defines the duration of the replication and how long transient failure can remove a node from the cluster. Tombstone cleanup must be tied to replication to reach replica convergence." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-replication.xml:33(para) +msgid "If a replicator detects that a remote drive has failed, the replicator uses the get_more_nodes interface for the ring to choose an alternate node with which to synchronize. The replicator can maintain desired levels of replication during disk failures, though some replicas might not be in an immediately usable location." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-replication.xml:40(para) +msgid "The replicator does not maintain desired levels of replication when failures such as entire node failures occur; most failures are transient." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-replication.xml:44(para) +msgid "The main replication types are:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-replication.xml:47(para) +msgid "Database replication. Replicates containers and objects." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-replication.xml:52(para) +msgid "Object replication. Replicates object data." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-replication.xml:57(title) +msgid "Database replication" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-replication.xml:58(para) +msgid "Database replication completes a low-cost hash comparison to determine whether two replicas already match. Normally, this check can quickly verify that most databases in the system are already synchronized. If the hashes differ, the replicator synchronizes the databases by sharing records added since the last synchronization point." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-replication.xml:65(para) +msgid "This synchronization point is a high water mark that notes the last record at which two databases were known to be synchronized, and is stored in each database as a tuple of the remote database ID and record ID. Database IDs are unique across all replicas of the database, and record IDs are monotonically increasing integers. After all new records are pushed to the remote database, the entire synchronization table of the local database is pushed, so the remote database can guarantee that it is synchronized with everything with which the local database was previously synchronized." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-replication.xml:76(para) +msgid "If a replica is missing, the whole local database file is transmitted to the peer by using rsync(1) and is assigned a new unique ID." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-replication.xml:79(para) +msgid "In practice, database replication can process hundreds of databases per concurrency setting per second (up to the number of available CPUs or disks) and is bound by the number of database transactions that must be performed." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-replication.xml:86(title) +msgid "Object replication" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-replication.xml:87(para) +msgid "The initial implementation of object replication performed an rsync to push data from a local partition to all remote servers where it was expected to reside. While this worked at small scale, replication times skyrocketed once directory structures could no longer be held in RAM. This scheme was modified to save a hash of the contents for each suffix directory to a per-partition hashes file. The hash for a suffix directory is no longer valid when the contents of that suffix directory is modified." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-replication.xml:96(para) +msgid "The object replication process reads in hash files and calculates any invalidated hashes. Then, it transmits the hashes to each remote server that should hold the partition, and only suffix directories with differing hashes on the remote server are rsynced. After pushing files to the remote server, the replication process notifies it to recalculate hashes for the rsynced suffix directories." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-replication.xml:104(para) +msgid "The number of uncached directories that object replication must traverse, usually as a result of invalidated suffix directory hashes, impedes performance. To provide acceptable replication speeds, object replication is designed to invalidate around 2 percent of the hash space on a normal node each day." +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-components.xml:43(None) +msgid "@@image: '../common/figures/objectstorage-buildingblocks.png'; md5=ed79466c8464513dbeaf1e0954280e5e" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-components.xml:86(None) +msgid "@@image: '../common/figures/objectstorage-ring.png'; md5=a94e26734cec6980c3684d9e824eac2d" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-components.xml:126(None) +msgid "@@image: '../common/figures/objectstorage-zones.png'; md5=1b1dc0abe6ea0c516f22ce399deb75ed" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-components.xml:144(None) +msgid "@@image: '../common/figures/objectstorage-accountscontainers.png'; md5=4b15e5a202db5bde53c9b369058aeab8" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-components.xml:169(None) +msgid "@@image: '../common/figures/objectstorage-partitions.png'; md5=2c161c2e92d6fefc8140ec86e79e9492" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-components.xml:195(None) +msgid "@@image: '../common/figures/objectstorage-replication.png'; md5=9d55594d7f445764569ab04d8d4373b2" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-components.xml:222(None) +msgid "@@image: '../common/figures/objectstorage-usecase.png'; md5=07480e7175b383171173775fb96d70d7" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-components.xml:7(title) ./doc/training-guides/sources/cinder/architecture.xml:33(title) +msgid "Components" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-components.xml:8(para) +msgid "The components that enable Object Storage to deliver high availability, high durability, and high concurrency are:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-components.xml:12(para) +msgid "Proxy servers. Handle all of the incoming API requests." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-components.xml:16(para) +msgid "Rings. Map logical names of data to locations on particular disks." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-components.xml:20(para) +msgid "Zones. Isolate data from other zones. A failure in one zone doesn’t impact the rest of the cluster because data is replicated across zones." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-components.xml:25(para) +msgid "Accounts and containers. Each account and container are individual databases that are distributed across the cluster. An account database contains the list of containers in that account. A container database contains the list of objects in that container." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-components.xml:31(para) +msgid "Objects. The data itself." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-components.xml:34(para) +msgid "Partitions. A partition stores objects, account databases, and container databases and helps manage locations where data lives in the cluster." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-components.xml:40(title) +msgid "Object Storage building blocks" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-components.xml:48(title) +msgid "Proxy servers" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-components.xml:49(para) +msgid "Proxy servers are the public face of Object Storage and handle all of the incoming API requests. Once a proxy server receives a request, it determines the storage node based on the object's URL, for example, https://swift.example.com/v1/account/container/object. Proxy servers also coordinate responses, handle failures, and coordinate timestamps." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-components.xml:54(para) +msgid "Proxy servers use a shared-nothing architecture and can be scaled as needed based on projected workloads. A minimum of two proxy servers should be deployed for redundancy. If one proxy server fails, the others take over." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-components.xml:59(title) +msgid "Rings" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-components.xml:60(para) +msgid "A ring represents a mapping between the names of entities stored on disk and their physical locations. There are separate rings for accounts, containers, and objects. When other components need to perform any operation on an object, container, or account, they need to interact with the appropriate ring to determine their location in the cluster." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-components.xml:65(para) +msgid "The ring maintains this mapping using zones, devices, partitions, and replicas. Each partition in the ring is replicated, by default, three times across the cluster, and partition locations are stored in the mapping maintained by the ring. The ring is also responsible for determining which devices are used for handoff in failure scenarios." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-components.xml:70(para) +msgid "Data can be isolated into zones in the ring. Each partition replica is guaranteed to reside in a different zone. A zone could represent a drive, a server, a cabinet, a switch, or even a data center." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-components.xml:73(para) +msgid "The partitions of the ring are equally divided among all of the devices in the Object Storage installation. When partitions need to be moved around (for example, if a device is added to the cluster), the ring ensures that a minimum number of partitions are moved at a time, and only one replica of a partition is moved at a time." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-components.xml:77(para) +msgid "You can use weights to balance the distribution of partitions on drives across the cluster. This can be useful, for example, when differently sized drives are used in a cluster." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-components.xml:80(para) +msgid "The ring is used by the proxy server and several background processes (like replication)." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-components.xml:83(title) +msgid "The ring" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-components.xml:90(para) +msgid "These rings are externally managed, in that the server processes themselves do not modify the rings, they are instead given new rings modified by other tools." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-components.xml:92(para) +msgid "The ring uses a configurable number of bits from an MD5 hash for a path as a partition index that designates a device. The number of bits kept from the hash is known as the partition power, and 2 to the partition power indicates the partition count. Partitioning the full MD5 hash ring allows other parts of the cluster to work in batches of items at once which ends up either more efficient or at least less complex than working with each item separately or the entire cluster all at once." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-components.xml:101(para) +msgid "Another configurable value is the replica count, which indicates how many of the partition-device assignments make up a single ring. For a given partition number, each replica’s device will not be in the same zone as any other replica's device. Zones can be used to group devices based on physical locations, power separations, network separations, or any other attribute that would improve the availability of multiple replicas at the same time." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-components.xml:109(title) ./doc/training-guides/basic-install-guide/common/section_objectstorage-components.xml:123(title) +msgid "Zones" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-components.xml:110(para) +msgid "Object Storage allows configuring zones in order to isolate failure boundaries. Each data replica resides in a separate zone, if possible. At the smallest level, a zone could be a single drive or a grouping of a few drives. If there were five object storage servers, then each server would represent its own zone. Larger deployments would have an entire rack (or multiple racks) of object servers, each representing a zone. The goal of zones is to allow the cluster to tolerate significant outages of storage servers without losing all replicas of the data." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-components.xml:117(para) +msgid "As mentioned earlier, everything in Object Storage is stored, by default, three times. Swift will place each replica \"as-uniquely-as-possible\" to ensure both high availability and high durability. This means that when chosing a replica location, Object Storage chooses a server in an unused zone before an unused server in a zone that already has a replica of the data." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-components.xml:130(para) +msgid "When a disk fails, replica data is automatically distributed to the other zones to ensure there are three copies of the data." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-components.xml:134(title) ./doc/training-guides/basic-install-guide/common/section_objectstorage-components.xml:141(title) +msgid "Accounts and containers" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-components.xml:135(para) +msgid "Each account and container is an individual SQLite database that is distributed across the cluster. An account database contains the list of containers in that account. A container database contains the list of objects in that container." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-components.xml:148(para) +msgid "To keep track of object data locations, each account in the system has a database that references all of its containers, and each container database references each object." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-components.xml:153(title) ./doc/training-guides/basic-install-guide/common/section_objectstorage-components.xml:166(title) +msgid "Partitions" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-components.xml:154(para) +msgid "A partition is a collection of stored data, including account databases, container databases, and objects. Partitions are core to the replication system." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-components.xml:156(para) +msgid "Think of a partition as a bin moving throughout a fulfillment center warehouse. Individual orders get thrown into the bin. The system treats that bin as a cohesive entity as it moves throughout the system. A bin is easier to deal with than many little things. It makes for fewer moving parts throughout the system." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-components.xml:160(para) +msgid "System replicators and object uploads/downloads operate on partitions. As the system scales up, its behavior continues to be predictable because the number of partitions is a fixed number." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-components.xml:163(para) +msgid "Implementing a partition is conceptually simple, a partition is just a directory sitting on a disk with a corresponding hash table of what it contains." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-components.xml:175(title) +msgid "Replicators" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-components.xml:176(para) +msgid "In order to ensure that there are three copies of the data everywhere, replicators continuously examine each partition. For each local partition, the replicator compares it against the replicated copies in the other zones to see if there are any differences." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-components.xml:180(para) +msgid "The replicator knows if replication needs to take place by examining hashes. A hash file is created for each partition, which contains hashes of each directory in the partition. Each of the three hash files is compared. For a given partition, the hash files for each of the partition's copies are compared. If the hashes are different, then it is time to replicate, and the directory that needs to be replicated is copied over." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-components.xml:186(para) +msgid "This is where partitions come in handy. With fewer things in the system, larger chunks of data are transferred around (rather than lots of little TCP connections, which is inefficient) and there is a consistent number of hashes to compare." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-components.xml:189(para) +msgid "The cluster eventually has a consistent behavior where the newest data has a priority." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-components.xml:199(para) +msgid "If a zone goes down, one of the nodes containing a replica notices and proactively copies data to a handoff location." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-components.xml:203(title) +msgid "Use cases" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-components.xml:204(para) +msgid "The following sections show use cases for object uploads and downloads and introduce the components." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-components.xml:206(title) +msgid "Upload" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-components.xml:207(para) +msgid "A client uses the REST API to make a HTTP request to PUT an object into an existing container. The cluster receives the request. First, the system must figure out where the data is going to go. To do this, the account name, container name, and object name are all used to determine the partition where this object should live." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-components.xml:211(para) +msgid "Then a lookup in the ring figures out which storage nodes contain the partitions in question." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-components.xml:213(para) +msgid "The data is then sent to each storage node where it is placed in the appropriate partition. At least two of the three writes must be successful before the client is notified that the upload was successful." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-components.xml:216(para) +msgid "Next, the container database is updated asynchronously to reflect that there is a new object in it." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-components.xml:219(title) +msgid "Object Storage in use" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-components.xml:228(title) +msgid "Download" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-components.xml:229(para) +msgid "A request comes in for an account/container/object. Using the same consistent hashing, the partition name is generated. A lookup in the ring reveals which storage nodes contain that partition. A request is made to one of the storage nodes to fetch the object and, if that fails, requests are made to the other nodes." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-intro.xml:8(para) +msgid "OpenStack Object Storage (code-named swift) is open source software for creating redundant, scalable data storage using clusters of standardized servers to store petabytes of accessible data. It is a long-term storage system for large amounts of static data that can be retrieved, leveraged, and updated. Object Storage uses a distributed architecture with no central point of control, providing greater scalability, redundancy, and permanence. Objects are written to multiple hardware devices, with the OpenStack software responsible for ensuring data replication and integrity across the cluster. Storage clusters scale horizontally by adding new nodes. Should a node fail, OpenStack works to replicate its content from other active nodes. Because OpenStack uses software logic to ensure data replication and distribution across different devices, inexpensive commodity hard drives and servers can be used in lieu of more expensive equipment." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-intro.xml:19(para) +msgid "Object Storage is ideal for cost effective, scale-out storage. It provides a fully distributed, API-accessible storage platform that can be integrated directly into applications or used for backup, archiving, and data retention." +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: ./doc/training-guides/basic-install-guide/common/section_keystone-concepts.xml:136(None) ./doc/training-guides/basic-install-guide/common/section_keystone-concepts.xml:141(None) +msgid "@@image: 'figures/SCH_5002_V00_NUAC-Keystone.png'; md5=734714c50c99fc1d74bdfd9f9cd049a6" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_keystone-concepts.xml:8(title) +msgid "OpenStack Identity concepts" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_keystone-concepts.xml:9(para) +msgid "The OpenStackIdentity Service performs the following functions:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_keystone-concepts.xml:13(para) +msgid "Tracking users and their permissions." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_keystone-concepts.xml:16(para) +msgid "Providing a catalog of available services with their API endpoints." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_keystone-concepts.xml:20(para) +msgid "When installing OpenStack Identity service, you must register each service in your OpenStack installation. Identity service can then track which OpenStack services are installed, and where they are located on the network." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_keystone-concepts.xml:24(para) +msgid "To understand OpenStack Identity, you must understand the following concepts:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_keystone-concepts.xml:28(term) ./doc/training-guides/common/module001-ch007-keystone-arch.xml:25(emphasis) +msgid "User" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_keystone-concepts.xml:30(para) +msgid "Digital representation of a person, system, or service who uses OpenStack cloud services. The Identity service validates that incoming requests are made by the user who claims to be making the call. Users have a login and may be assigned tokens to access resources. Users can be directly assigned to a particular tenant and behave as if they are contained in that tenant." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_keystone-concepts.xml:41(term) ./doc/training-guides/common/module001-ch007-keystone-arch.xml:38(emphasis) +msgid "Credentials" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_keystone-concepts.xml:43(para) +msgid "Data that confirms the user's identity. For example: user name and password, user name and API key, or an authentication token provided by the Identity Service." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_keystone-concepts.xml:50(term) ./doc/training-guides/common/module001-ch007-keystone-arch.xml:57(emphasis) +msgid "Authentication" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_keystone-concepts.xml:52(para) +msgid "The process of confirming the identity of a user. OpenStack Identity confirms an incoming request by validating a set of credentials supplied by the user." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_keystone-concepts.xml:56(para) +msgid "These credentials are initially a user name and password, or a user name and API key. When user credentials are validated, OpenStack Identity issues an authentication token which the user provides in subsequent requests." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_keystone-concepts.xml:64(term) ./doc/training-guides/common/module001-ch007-keystone-arch.xml:71(emphasis) +msgid "Token" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_keystone-concepts.xml:66(para) +msgid "An alpha-numeric string of text used to access OpenStack APIs and resources. A token may be revoked at any time and is valid for a finite duration." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_keystone-concepts.xml:70(para) +msgid "While OpenStack Identity supports token-based authentication in this release, the intention is to support additional protocols in the future. Its main purpose is to be an integration service, and not aspire to be a full-fledged identity store and management solution." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_keystone-concepts.xml:79(term) ./doc/training-guides/common/module001-ch007-keystone-arch.xml:86(emphasis) +msgid "Tenant" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_keystone-concepts.xml:81(para) +msgid "A container used to group or isolate resources. Tenants also group or isolate identity objects. Depending on the service operator, a tenant may map to a customer, account, organization, or project." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_keystone-concepts.xml:88(term) ./doc/training-guides/common/module001-ch007-keystone-arch.xml:96(emphasis) +msgid "Service" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_keystone-concepts.xml:90(para) +msgid "An OpenStack service, such as Compute (nova), Object Storage (swift), or Image Service (glance). It provides one or more endpoints in which users can access resources and perform operations." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_keystone-concepts.xml:97(term) ./doc/training-guides/common/module001-ch007-keystone-arch.xml:105(emphasis) +msgid "Endpoint" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_keystone-concepts.xml:99(para) +msgid "A network-accessible address where you access a service, usually a URL address. If you are using an extension for templates, an endpoint template can be created, which represents the templates of all the consumable services that are available across the regions." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_keystone-concepts.xml:107(term) ./doc/training-guides/common/module001-ch007-keystone-arch.xml:116(emphasis) +msgid "Role" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_keystone-concepts.xml:109(para) +msgid "A personality with a defined set of user rights and privileges to perform a specific set of operations." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_keystone-concepts.xml:111(para) +msgid "In the Identity service, a token that is issued to a user includes the list of roles. Services that are being called by that user determine how they interpret the set of roles a user has and to which operations or resources each role grants access." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_keystone-concepts.xml:119(term) +msgid "Keystone Client" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_keystone-concepts.xml:121(para) +msgid "A command line interface for the OpenStack Identity API. For example, users can run the and commands to register services in their OpenStack installations." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_keystone-concepts.xml:130(para) +msgid "The following diagram shows the OpenStack Identity process flow:" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-features.xml:7(title) +msgid "Features and benefits" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-features.xml:12(th) +msgid "Features" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-features.xml:13(th) +msgid "Benefits" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-features.xml:18(emphasis) +msgid "Leverages commodity hardware" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-features.xml:19(td) +msgid "No lock-in, lower price/GB." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-features.xml:22(emphasis) +msgid "HDD/node failure agnostic" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-features.xml:23(td) +msgid "Self-healing, reliable, data redundancy protects from failures." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-features.xml:27(emphasis) +msgid "Unlimited storage" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-features.xml:28(td) +msgid "Large and flat namespace, highly scalable read/write access, able to serve content directly from storage system." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-features.xml:32(emphasis) +msgid "Multi-dimensional scalability" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-features.xml:34(td) +msgid "Scale-out architecture: Scale vertically and horizontally-distributed storage. Backs up and archives large amounts of data with linear performance." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-features.xml:39(emphasis) +msgid "Account/container/object structure" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-features.xml:40(td) +msgid "No nesting, not a traditional file system: Optimized for scale, it scales to multiple petabytes and billions of objects." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-features.xml:45(emphasis) +msgid "Built-in replication 3✕ + data redundancy (compared with 2✕ on RAID)" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-features.xml:48(td) +msgid "A configurable number of accounts, containers and object copies for high availability." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-features.xml:52(emphasis) +msgid "Easily add capacity (unlike RAID resize)" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-features.xml:54(td) +msgid "Elastic data scaling with ease" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-features.xml:57(emphasis) +msgid "No central database" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-features.xml:58(td) +msgid "Higher performance, no bottlenecks" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-features.xml:61(emphasis) +msgid "RAID not required" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-features.xml:62(td) +msgid "Handle many small, random reads and writes efficiently" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-features.xml:65(emphasis) +msgid "Built-in management utilities" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-features.xml:66(td) +msgid "Account management: Create, add, verify, and delete users; Container management: Upload, download, and verify; Monitoring: Capacity, host, network, log trawling, and cluster health." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-features.xml:72(emphasis) +msgid "Drive auditing" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-features.xml:73(td) +msgid "Detect drive failures preempting data corruption" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-features.xml:76(emphasis) +msgid "Expiring objects" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-features.xml:77(td) +msgid "Users can set an expiration time or a TTL on an object to control access" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-features.xml:81(emphasis) +msgid "Direct object access" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-features.xml:82(td) +msgid "Enable direct browser access to content, such as for a control panel" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-features.xml:86(emphasis) +msgid "Realtime visibility into client requests" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-features.xml:88(td) +msgid "Know what users are requesting." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-features.xml:91(emphasis) +msgid "Supports S3 API" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-features.xml:92(td) +msgid "Utilize tools that were designed for the popular S3 API." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-features.xml:96(emphasis) +msgid "Restrict containers per account" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-features.xml:98(td) +msgid "Limit access to control usage by user." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-features.xml:101(emphasis) +msgid "Support for NetApp, Nexenta, SolidFire" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-features.xml:103(td) +msgid "Unified support for block volumes using a variety of storage systems." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-features.xml:107(emphasis) +msgid "Snapshot and backup API for block volumes" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-features.xml:109(td) +msgid "Data protection and recovery for VM data." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-features.xml:112(emphasis) +msgid "Standalone volume API available" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-features.xml:114(td) +msgid "Separate endpoint and API for integration with other compute systems." +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-features.xml:118(emphasis) +msgid "Integration with Compute" +msgstr "" + +#: ./doc/training-guides/basic-install-guide/common/section_objectstorage-features.xml:120(td) +msgid "Fully integrated with Compute for attaching block volumes and reporting on usage." +msgstr "" + #: ./doc/training-guides/developer-guide/bk003-ch001-developer-getting-started.xml:22(title) msgid "Review Operator Introduction" msgstr "" @@ -2948,10 +9415,6 @@ msgstr "" msgid "Architect Training Guide Coming Soon" msgstr "" -#: ./doc/training-guides/sources/cinder/architecture.xml:7(title) -msgid "Architecture" -msgstr "" - #: ./doc/training-guides/sources/cinder/architecture.xml:9(title) ./doc/training-guides/sources/cinder/development.environment.xml:9(title) ./doc/training-guides/sources/cinder/unit_tests.xml:9(title) ./doc/training-guides/sources/cinder/threading.xml:9(title) msgid "Header" msgstr "" @@ -2968,10 +9431,6 @@ msgstr "" msgid "The OpenStack Block Storage service is intended to run on one or more nodes. Block Storage uses a SQL-based central database that is shared by all Block Storage services in the system. The amount and depth of the data fits into a SQL database quite well. For small deployments this seems like an optimal solution. For larger deployments, and especially if security is a concern, Block Storage will be moving towards multiple data stores with some kind of aggregation system." msgstr "" -#: ./doc/training-guides/sources/cinder/architecture.xml:33(title) -msgid "Components" -msgstr "" - #: ./doc/training-guides/sources/cinder/architecture.xml:52(para) msgid "DB: SQL database for data storage. Used by all components (LINKS NOT SHOWN)" msgstr "" @@ -3116,10 +9575,6 @@ msgstr "" msgid "---------- By default, the tests use the Python packages installed inside a virtualenv [#f2]_. (This is equivalent to using the ``-V, --virtualenv`` flag). If the virtualenv does not exist, it will be created the first time the tests are run. If you wish to recreate the virtualenv, call ``run_tests.sh`` with the flag:: -f, --force Recreating the virtualenv is useful if the package dependencies have changed since the virtualenv was last created. If the ``requirements.txt`` or ``tools/install_venv.py`` files have changed, it's a good idea to recreate the virtualenv. By default, the unit tests will see both the packages in the virtualenv and the packages that have been installed in the Python global environment. In some cases, the packages in the Python global environment may cause a conflict with the packages in the virtualenv. If this occurs, you can isolate the virtualenv from the global environment by using the flag:: -s, --no-site packages If you do not wish to use a virtualenv at all, use the flag:: -N, --no-virtual-env" msgstr "" -#: ./doc/training-guides/sources/cinder/unit_tests.xml:113(title) -msgid "Database" -msgstr "" - #: ./doc/training-guides/sources/cinder/unit_tests.xml:114(para) msgid "-------- Some of the unit tests make queries against a SQLite database [#f3]_. By default, the test database (``tests.sqlite``) is deleted and recreated each time ``run_tests.sh`` is invoked (This is equivalent to using the ``-r, --recreate-db`` flag). To reduce testing time if a database already exists it can be reused by using the flag:: -n, --no-recreate-db Reusing an existing database may cause tests to fail if the schema has changed. If any files in the ``cinder/db/sqlalchemy`` have changed, it's a good idea to recreate the test database." msgstr "" @@ -3782,7 +10237,7 @@ msgid "UML- User Mode Linux (visit http://go msgstr "" #: ./doc/training-guides/common/module001-ch005-vm-provisioning-walk-through.xml:58(para) -msgid "VMWare vSphere4.1 update 1 and newer (visit http://goo.gl/0DBeo5)" +msgid "VMware vSphere4.1 update 1 and newer (visit http://goo.gl/0DBeo5)" msgstr "" #: ./doc/training-guides/common/module001-ch005-vm-provisioning-walk-through.xml:63(para) @@ -4719,11 +11174,11 @@ msgid "qcow2 (Qemu/KVM)" msgstr "" #: ./doc/training-guides/common/module001-ch003-core-projects.xml:594(para) -msgid "VMDK (VMWare)" +msgid "VMDK (VMware)" msgstr "" #: ./doc/training-guides/common/module001-ch003-core-projects.xml:597(para) -msgid "OVF (VMWare, others)" +msgid "OVF (VMware, others)" msgstr "" #: ./doc/training-guides/common/module001-ch003-core-projects.xml:600(para) @@ -6448,10 +12903,6 @@ msgstr "" msgid "Copy the value in the ID field for your volume." msgstr "" -#: ./doc/training-guides/common/module001-ch006-overview-horizon-cli.xml:1701(para) -msgid "To launch an instance" -msgstr "" - #: ./doc/training-guides/common/module001-ch006-overview-horizon-cli.xml:1704(para) msgid "Enter the nova boot command with the --block_device_mapping parameter, as follows:" msgstr "" @@ -6504,10 +12955,6 @@ msgstr "" msgid "False or 0" msgstr "" -#: ./doc/training-guides/common/module001-ch006-overview-horizon-cli.xml:1761(para) -msgid "name" -msgstr "" - #: ./doc/training-guides/common/module001-ch006-overview-horizon-cli.xml:1764(para) msgid "The name for the server." msgstr "" @@ -7353,18 +13800,10 @@ msgstr "" msgid "To understand the Identity Service, you must understand these concepts:" msgstr "" -#: ./doc/training-guides/common/module001-ch007-keystone-arch.xml:25(emphasis) -msgid "User" -msgstr "" - #: ./doc/training-guides/common/module001-ch007-keystone-arch.xml:27(para) msgid "Digital representation of a person, system, or service who uses OpenStack cloud services. Identity authentication services will validate that incoming requests are being made by the user who claims to be making the call. Users have a login and may be assigned tokens to access resources. Users may be directly assigned to a particular tenant and behave as if they are contained in that tenant." msgstr "" -#: ./doc/training-guides/common/module001-ch007-keystone-arch.xml:38(emphasis) -msgid "Credentials" -msgstr "" - #: ./doc/training-guides/common/module001-ch007-keystone-arch.xml:40(para) msgid "Data that is known only by a user that proves who they are. In the Identity Service, examples are:" msgstr "" @@ -7381,18 +13820,10 @@ msgstr "" msgid "An authentication token provided by the Identity Service" msgstr "" -#: ./doc/training-guides/common/module001-ch007-keystone-arch.xml:57(emphasis) -msgid "Authentication" -msgstr "" - #: ./doc/training-guides/common/module001-ch007-keystone-arch.xml:59(para) msgid "The act of confirming the identity of a user. The Identity Service confirms an incoming request by validating a set of credentials supplied by the user. These credentials are initially a username and password or a username and API key. In response to these credentials, the Identity Service issues the user an authentication token, which the user provides in subsequent requests." msgstr "" -#: ./doc/training-guides/common/module001-ch007-keystone-arch.xml:71(emphasis) -msgid "Token" -msgstr "" - #: ./doc/training-guides/common/module001-ch007-keystone-arch.xml:73(para) msgid "An arbitrary bit of text that is used to access resources. Each token has a scope which describes which resources are accessible with it. A token may be revoked at anytime and is valid for a finite duration." msgstr "" @@ -7401,34 +13832,18 @@ msgstr "" msgid "While the Identity Service supports token-based authentication in this release, the intention is for it to support additional protocols in the future. The intent is for it to be an integration service foremost, and not aspire to be a full-fledged identity store and management solution." msgstr "" -#: ./doc/training-guides/common/module001-ch007-keystone-arch.xml:86(emphasis) -msgid "Tenant" -msgstr "" - #: ./doc/training-guides/common/module001-ch007-keystone-arch.xml:88(para) msgid "A container used to group or isolate resources and/or identity objects. Depending on the service operator, a tenant may map to a customer, account, organization, or project." msgstr "" -#: ./doc/training-guides/common/module001-ch007-keystone-arch.xml:96(emphasis) -msgid "Service" -msgstr "" - #: ./doc/training-guides/common/module001-ch007-keystone-arch.xml:98(para) msgid "An OpenStack service, such as Compute (Nova), Object Storage (Swift), or Image Service (Glance). Provides one or more endpoints through which users can access resources and perform operations." msgstr "" -#: ./doc/training-guides/common/module001-ch007-keystone-arch.xml:105(emphasis) -msgid "Endpoint" -msgstr "" - #: ./doc/training-guides/common/module001-ch007-keystone-arch.xml:107(para) msgid "An network-accessible address, usually described by URL, from where you access a service. If using an extension for templates, you can create an endpoint template, which represents the templates of all the consumable services that are available across the regions." msgstr "" -#: ./doc/training-guides/common/module001-ch007-keystone-arch.xml:116(emphasis) -msgid "Role" -msgstr "" - #: ./doc/training-guides/common/module001-ch007-keystone-arch.xml:118(para) msgid "A personality that a user assumes which enables them to perform a specific set of operations. A role includes a set of rights and privileges. A user assuming that role inherits those rights and privileges." msgstr "" @@ -7953,10 +14368,6 @@ msgstr "" msgid "The Account Server is very similar to the Container Server, excepting that it is responsible for listings of containers rather than objects." msgstr "" -#: ./doc/training-guides/common/module003-ch006-more-concepts.xml:156(guilabel) -msgid "Replication" -msgstr "" - #: ./doc/training-guides/common/module003-ch006-more-concepts.xml:157(para) msgid "Replication is designed to keep the system in a consistent state in the face of temporary error conditions like network outages or drive failures." msgstr "" @@ -8181,10 +14592,6 @@ msgstr "" msgid "network.phantom (phantom is the hostname)" msgstr "" -#: ./doc/training-guides/common/module001-ch008-queues-messaging.xml:260(para) -msgid "network" -msgstr "" - #: ./doc/training-guides/common/module001-ch008-queues-messaging.xml:263(para) msgid "scheduler.phantom (phantom is the hostname)" msgstr ""