openstack/openstack-manuals
Code Issues Proposed changes
78035f31b4
openstack-manuals/doc/install-guide/locale/install-guide.pot
OpenStack Proposal Bot e161b84a19 Imported Translations from Transifex 
Change-Id: I7f56ac03a9601bb4e69002d36efd90b8e548d3a9
2014-05-08 06:44:43 +00:00

6332 lines
390 KiB
Plaintext
Raw Blame History

This file contains invisible Unicode characters

This file contains invisible Unicode characters that are indistinguishable to humans but may be processed differently by a computer. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"POT-Creation-Date: 2014-05-08 06:25+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#: ./doc/install-guide/section_keystone-users.xml:5(title)
msgid "Define users, tenants, and roles"
msgstr ""
#: ./doc/install-guide/section_keystone-users.xml:7(para)
msgid "After you install the Identity Service, set up <glossterm baseform=\"user\">users</glossterm>, <glossterm baseform=\"tenant\">tenants</glossterm>, and <glossterm baseform=\"role\">roles</glossterm> to authenticate against. These are used to allow access to services and <glossterm baseform=\"endpoint\">endpoints</glossterm>, described in the next section."
msgstr ""
#: ./doc/install-guide/section_keystone-users.xml:26(replaceable) ./doc/install-guide/section_keystone-users.xml:29(replaceable) ./doc/install-guide/section_trove-install.xml:136(replaceable)
msgid "ADMIN_TOKEN"
msgstr ""
#: ./doc/install-guide/section_keystone-users.xml:15(para)
msgid "Typically, you would indicate a user and password to authenticate with the Identity Service. At this point, however, you have not created any users, so you have to use the authorization token created in an earlier step, see <xref linkend=\"keystone-install\"/> for further details. You can pass this with the <option>--os-token</option> option to the <placeholder-1/> command or set the <envar>OS_SERVICE_TOKEN</envar> environment variable. Set <envar>OS_SERVICE_TOKEN</envar>, as well as <envar>OS_SERVICE_ENDPOINT</envar> to specify where the Identity Service is running. Replace <placeholder-2/> with your authorization token."
msgstr ""
#: ./doc/install-guide/section_keystone-users.xml:33(title)
msgid "Create an administrative user"
msgstr ""
#: ./doc/install-guide/section_keystone-users.xml:34(para)
msgid "Follow these steps to create an administrative user, role, and tenant. You will use this account for administrative interaction with the OpenStack cloud."
msgstr ""
#: ./doc/install-guide/section_keystone-users.xml:39(para)
msgid "By default, the Identity Service creates a special <literal>_member_</literal> role. The OpenStack dashboard automatically grants access to users with this role. You will give the <literal>admin</literal> user access to this role in addition to the <literal>admin</literal> role."
msgstr ""
#: ./doc/install-guide/section_keystone-users.xml:47(para)
msgid "Any role that you create must map to roles specified in the <filename>policy.json</filename> file included with each OpenStack service. The default policy file for most services grants administrative access to the <literal>admin</literal> role."
msgstr ""
#: ./doc/install-guide/section_keystone-users.xml:55(para)
msgid "Create the <literal>admin</literal> user:"
msgstr ""
#: ./doc/install-guide/section_keystone-users.xml:58(replaceable) ./doc/install-guide/section_trove-install.xml:135(replaceable) ./doc/install-guide/section_trove-install.xml:164(replaceable) ./doc/install-guide/section_trove-install.xml:210(replaceable) ./doc/install-guide/section_keystone-verify.xml:25(replaceable) ./doc/install-guide/section_keystone-verify.xml:35(replaceable) ./doc/install-guide/section_keystone-verify.xml:49(replaceable) ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:408(replaceable) ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:376(replaceable) ./doc/install-guide/section_neutron-single-flat.xml:485(replaceable)
msgid "ADMIN_PASS"
msgstr ""
#: ./doc/install-guide/section_keystone-users.xml:58(replaceable)
msgid "ADMIN_EMAIL"
msgstr ""
#: ./doc/install-guide/section_keystone-users.xml:59(para)
msgid "Replace <replaceable>ADMIN_PASS</replaceable> with a secure password and replace <replaceable>ADMIN_EMAIL</replaceable> with an email address to associate with the account."
msgstr ""
#: ./doc/install-guide/section_keystone-users.xml:66(para)
msgid "Create the <literal>admin</literal> role:"
msgstr ""
#: ./doc/install-guide/section_keystone-users.xml:72(para)
msgid "Create the <literal>admin</literal> tenant:"
msgstr ""
#: ./doc/install-guide/section_keystone-users.xml:78(para)
msgid "You must now link the <literal>admin</literal> user, <literal>admin</literal> role, and <literal>admin</literal> tenant together using the <option>user-role-add</option> option:"
msgstr ""
#: ./doc/install-guide/section_keystone-users.xml:86(para)
msgid "Link the <literal>admin</literal> user, <literal>_member_</literal> role, and <literal>admin</literal> tenant:"
msgstr ""
#: ./doc/install-guide/section_keystone-users.xml:94(title)
msgid "Create a normal user"
msgstr ""
#: ./doc/install-guide/section_keystone-users.xml:95(para)
msgid "Follow these steps to create a normal user and tenant, and link them to the special <literal>_member_</literal> role. You will use this account for daily non-administrative interaction with the OpenStack cloud. You can also repeat this procedure to create additional cloud users with different usernames and passwords. Skip the tenant creation step when creating these users."
msgstr ""
#: ./doc/install-guide/section_keystone-users.xml:104(para)
msgid "Create the <literal>demo</literal> user:"
msgstr ""
#: ./doc/install-guide/section_keystone-users.xml:107(replaceable) ./doc/install-guide/ch_clients.xml:40(replaceable)
msgid "DEMO_PASS"
msgstr ""
#: ./doc/install-guide/section_keystone-users.xml:107(replaceable)
msgid "DEMO_EMAIL"
msgstr ""
#: ./doc/install-guide/section_keystone-users.xml:108(para)
msgid "Replace <replaceable>DEMO_PASS</replaceable> with a secure password and replace <replaceable>DEMO_EMAIL</replaceable> with an email address to associate with the account."
msgstr ""
#: ./doc/install-guide/section_keystone-users.xml:115(para)
msgid "Create the <literal>demo</literal> tenant:"
msgstr ""
#: ./doc/install-guide/section_keystone-users.xml:120(para)
msgid "Do not repeat this step when adding additional users."
msgstr ""
#: ./doc/install-guide/section_keystone-users.xml:126(para)
msgid "Link the <literal>demo</literal> user, <literal>_member_</literal> role, and <literal>demo</literal> tenant:"
msgstr ""
#: ./doc/install-guide/section_keystone-users.xml:134(title)
msgid "Create a <literal>service</literal> tenant"
msgstr ""
#: ./doc/install-guide/section_keystone-users.xml:135(para)
msgid "OpenStack services also require a username, tenant, and role to access other OpenStack services. In a basic installation, OpenStack services typically share a single tenant named <literal>service</literal>."
msgstr ""
#: ./doc/install-guide/section_keystone-users.xml:140(para)
msgid "You will create additional usernames and roles under this tenant as you install and configure each service."
msgstr ""
#: ./doc/install-guide/section_keystone-users.xml:145(para)
msgid "Create the <literal>service</literal> tenant:"
msgstr ""
#: ./doc/install-guide/section_nova-networking-initial-network.xml:5(title)
msgid "Create initial network"
msgstr ""
#: ./doc/install-guide/section_nova-networking-initial-network.xml:6(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 <emphasis>from</emphasis> instances. You can enable internet access <emphasis>to</emphasis> individual instances using a <glossterm>floating IP address</glossterm> and suitable <glossterm>security group</glossterm> rules. The <literal>admin</literal> tenant owns this network because it provides external network access for multiple tenants."
msgstr ""
#: ./doc/install-guide/section_nova-networking-initial-network.xml:15(para)
msgid "This network shares the same <glossterm>subnet</glossterm> associated with the physical network connected to the external <glossterm>interface</glossterm> 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/install-guide/section_nova-networking-initial-network.xml:21(para) ./doc/install-guide/section_neutron-initial-networks.xml:40(para) ./doc/install-guide/section_neutron-initial-networks.xml:127(para)
msgid "Perform these commands on the controller node."
msgstr ""
#: ./doc/install-guide/section_nova-networking-initial-network.xml:24(title)
msgid "To create the network"
msgstr ""
#: ./doc/install-guide/section_nova-networking-initial-network.xml:26(para) ./doc/install-guide/section_neutron-initial-networks.xml:45(para)
msgid "Source the <literal>admin</literal> tenant credentials:"
msgstr ""
#: ./doc/install-guide/section_nova-networking-initial-network.xml:30(para) ./doc/install-guide/section_neutron-initial-networks.xml:49(para) ./doc/install-guide/section_neutron-initial-networks.xml:136(para)
msgid "Create the network:"
msgstr ""
#: ./doc/install-guide/section_nova-networking-initial-network.xml:31(para)
msgid "Replace <replaceable>NETWORK_CIDR</replaceable> with the subnet associated with the physical network."
msgstr ""
#: ./doc/install-guide/section_nova-networking-initial-network.xml:34(replaceable)
msgid "NETWORK_CIDR"
msgstr ""
#: ./doc/install-guide/section_nova-networking-initial-network.xml:35(para)
msgid "For example, using an exclusive slice of <literal>203.0.113.0/24</literal> with IP address range <literal>203.0.113.24</literal> to <literal>203.0.113.32</literal>:"
msgstr ""
#: ./doc/install-guide/section_nova-networking-initial-network.xml:42(para) ./doc/install-guide/section_launch-instance-nova.xml:26(para) ./doc/install-guide/section_launch-instance-neutron.xml:26(para) ./doc/install-guide/section_launch-instance-neutron.xml:245(para)
msgid "This command provides no output."
msgstr ""
#: ./doc/install-guide/section_nova-networking-initial-network.xml:46(para)
msgid "Verify creation of the network:"
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/install-guide/section_debconf-api-endpoints.xml:29(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/install-guide/section_debconf-api-endpoints.xml:40(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/install-guide/section_debconf-api-endpoints.xml:54(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/install-guide/section_debconf-api-endpoints.xml:69(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/install-guide/section_debconf-api-endpoints.xml:81(None)
msgid "@@image: 'figures/debconf-screenshots/api-endpoint_5_region_name.png'; md5=a6bce0acf5a1cb85f161290f0cf30733"
msgstr ""
#: ./doc/install-guide/section_debconf-api-endpoints.xml:6(title)
msgid "Register API endpoints"
msgstr ""
#: ./doc/install-guide/section_debconf-api-endpoints.xml:7(para)
msgid "All Debian packages for API services, except the <package>heat-api</package> package, register the service in the Identity Service catalog. This feature is helpful because API endpoints are difficult to remember."
msgstr ""
#: ./doc/install-guide/section_debconf-api-endpoints.xml:12(para)
msgid "The <package>heat-common</package> package and not the <package>heat-api</package> package configures the Orchestration service."
msgstr ""
#: ./doc/install-guide/section_debconf-api-endpoints.xml:16(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 <package>debconf</package> database. Consequently, you are prompted to re-register the service with the Identity Service. If you already registered the API service, respond <literal>no</literal> when you upgrade."
msgstr ""
#: ./doc/install-guide/section_debconf-api-endpoints.xml:33(para)
msgid "This screen registers packages in the Identity Service catalog:"
msgstr ""
#: ./doc/install-guide/section_debconf-api-endpoints.xml:44(para)
msgid "You are prompted for the Identity Service <literal>admin_token</literal> value. The Identity Service uses this value to register the API service. When you set up the <package>keystone</package> package, this value is configured automatically."
msgstr ""
#: ./doc/install-guide/section_debconf-api-endpoints.xml:58(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 (<code>/sbin/route</code> and <code>/sbin/ip</code>)."
msgstr ""
#: ./doc/install-guide/section_debconf-api-endpoints.xml:62(para)
msgid "Unless you have a unique set up for your network, press <keycap>ENTER</keycap>."
msgstr ""
#: ./doc/install-guide/section_debconf-api-endpoints.xml:73(para)
msgid "This screen configures the region name for the service. For example, <code>us-east-coast</code> or <code>europe-paris</code>."
msgstr ""
#: ./doc/install-guide/ch_glance.xml:6(title)
msgid "Configure the Image Service"
msgstr ""
#: ./doc/install-guide/ch_glance.xml:7(para)
msgid "The OpenStack Image Service enables users to discover, register, and retrieve virtual machine images. Also known as the glance project, the Image Service offers a <glossterm baseform=\"RESTful\">REST</glossterm> 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/install-guide/ch_glance.xml:16(para)
msgid "For simplicity, this guide configures the Image Service to use the <literal>file</literal> back end. This means that images uploaded to the Image Service are stored in a directory on the same system that hosts the service. By default, this directory is <filename>/var/lib/glance/images/</filename>."
msgstr ""
#: ./doc/install-guide/ch_glance.xml:21(para)
msgid "Before you proceed, ensure that the system has sufficient space available in this directory to store virtual machine images and snapshots. At an absolute minimum, several gigabytes of space should be available for use by the Image Service in a proof of concept deployment. To see requirements for other back ends, see <link href=\"http://docs.openstack.org/trunk/config-reference/content/ch_configuring-openstack-image-service.html\"><citetitle>Configuration Reference</citetitle></link>."
msgstr ""
#: ./doc/install-guide/ch_cinder.xml:6(title)
msgid "Add the Block Storage service"
msgstr ""
#: ./doc/install-guide/ch_cinder.xml:7(para)
msgid "The OpenStack Block Storage service works through the interaction of a series of daemon processes named <systemitem role=\"process\">cinder-*</systemitem> 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/install-guide/ch_cinder.xml:20(title) ./doc/install-guide/ch_swift.xml:30(title) ./doc/install-guide/ch_networking.xml:37(title) ./doc/install-guide/ch_horizon.xml:38(title) ./doc/install-guide/ch_ceilometer.xml:18(title) ./doc/install-guide/ch_heat.xml:14(title)
msgid "Next steps"
msgstr ""
#: ./doc/install-guide/ch_cinder.xml:21(para)
msgid "Your OpenStack environment now includes Block Storage. You can <link linkend=\"launch-instance\">launch an instance</link> or add more services to your environment in the following chapters."
msgstr ""
#: ./doc/install-guide/section_basics-passwords.xml:6(title)
msgid "Passwords"
msgstr ""
#: ./doc/install-guide/section_basics-passwords.xml:7(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 <application>pwgen</application> program. Or, to create passwords one at a time, use the output of this command repeatedly: <placeholder-1/>"
msgstr ""
#: ./doc/install-guide/section_basics-passwords.xml:17(para)
msgid "This guide uses the convention that <literal><replaceable>SERVICE_PASS</replaceable></literal> is the password to access the service <literal>SERVICE</literal> and <literal><replaceable>SERVICE_DBPASS</replaceable></literal> is the database password used by the service SERVICE to access the database."
msgstr ""
#: ./doc/install-guide/section_basics-passwords.xml:24(para)
msgid "The complete list of passwords you need to define in this guide are: <table rules=\"all\"><caption>Passwords</caption><thead><tr><th>Password name</th><th>Description</th></tr></thead><tbody><tr><td>Database password (no variable used)</td><td>Root password for the database</td></tr><tr os=\"ubuntu;opensuse;sles\"><td><literal><replaceable>RABBIT_PASS</replaceable></literal></td><td>Password of user guest of RabbitMQ</td></tr><tr><td><literal><replaceable>KEYSTONE_DBPASS</replaceable></literal></td><td>Database password of Identity service</td></tr><tr><td><literal><replaceable>DEMO_PASS</replaceable></literal></td><td>Password of user <literal>demo</literal></td></tr><tr><td><literal><replaceable>ADMIN_PASS</replaceable></literal></td><td>Password of user <literal>admin</literal></td></tr><tr><td><literal><replaceable>GLANCE_DBPASS</replaceable></literal></td><td>Database password for Image Service</td></tr><tr><td><literal><replaceable>GLANCE_PASS</replaceable></literal></td><td>Password of Image Service user <literal>glance</literal></td></tr><tr><td><literal><replaceable>NOVA_DBPASS</replaceable></literal></td><td>Database password for Compute service</td></tr><tr><td><literal><replaceable>NOVA_PASS</replaceable></literal></td><td>Password of Compute service user <literal>nova</literal></td></tr><tr><td><literal><replaceable>DASH_DBPASS</replaceable></literal></td><td>Database password for the dashboard</td></tr><tr><td><literal><replaceable>CINDER_DBPASS</replaceable></literal></td><td>Database password for the Block Storage service</td></tr><tr><td><literal><replaceable>CINDER_PASS</replaceable></literal></td><td>Password of Block Storage service user <literal>cinder</literal></td></tr><tr><td><literal><replaceable>NEUTRON_DBPASS</replaceable></literal></td><td>Database password for the Networking service</td></tr><tr><td><literal><replaceable>NEUTRON_PASS</replaceable></literal></td><td>Password of Networking service user <literal>neutron</literal></td></tr><tr><td><literal><replaceable>HEAT_DBPASS</replaceable></literal></td><td>Database password for the Orchestration service</td></tr><tr><td><literal><replaceable>HEAT_PASS</replaceable></literal></td><td>Password of Orchestration service user <literal>heat</literal></td></tr><tr><td><literal><replaceable>CEILOMETER_DBPASS</replaceable></literal></td><td>Database password for the Telemetry service</td></tr><tr><td><literal><replaceable>CEILOMETER_PASS</replaceable></literal></td><td>Password of Telemetry service user <literal>ceilometer</literal></td></tr><tr><td><literal><replaceable>TROVE_DBPASS</replaceable></literal></td><td>Database password of Database service</td></tr><tr><td><literal><replaceable>TROVE_PASS</replaceable></literal></td><td>Password of Database Service user <literal>trove</literal></td></tr></tbody></table>"
msgstr ""
#: ./doc/install-guide/section_basics-database.xml:6(title)
msgid "Database"
msgstr ""
#: ./doc/install-guide/section_basics-database.xml:7(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/install-guide/section_basics-database.xml:13(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/install-guide/section_basics-database.xml:22(title)
msgid "Controller setup"
msgstr ""
#: ./doc/install-guide/section_basics-database.xml:23(para)
msgid "<phrase os=\"sles\">For SUSE Linux Enterprise Server: </phrase> On the controller node, install the MySQL client and server packages, and the Python library."
msgstr ""
#: ./doc/install-guide/section_basics-database.xml:27(para)
msgid "For openSUSE: On the controller node, install the MariaDB client and database server packages, and the MySQL Python library."
msgstr ""
#: ./doc/install-guide/section_basics-database.xml:34(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/install-guide/section_basics-database.xml:38(para)
msgid "The MySQL configuration requires some changes to work with OpenStack."
msgstr ""
#: ./doc/install-guide/section_basics-database.xml:42(para)
msgid "Edit the <filename>/etc/mysql/my.cnf</filename> file:"
msgstr ""
#: ./doc/install-guide/section_basics-database.xml:44(para)
msgid "Edit the <filename>/etc/my.cnf</filename> file:"
msgstr ""
#: ./doc/install-guide/section_basics-database.xml:48(para)
msgid "Under the <literal>[mysqld]</literal> section, set the <literal>bind-address</literal> key to the management IP address of the controller node to enable access by other nodes via the management network:"
msgstr ""
#: ./doc/install-guide/section_basics-database.xml:57(para)
msgid "Under the <literal>[mysqld]</literal> section, set the following keys to enable InnoDB, UTF-8 character set, and UTF-8 collation by default:"
msgstr ""
#: ./doc/install-guide/section_basics-database.xml:70(para)
msgid "Restart the MySQL service to apply the changes:"
msgstr ""
#: ./doc/install-guide/section_basics-database.xml:73(para)
msgid "Start the <phrase os=\"rhel;fedora;centos\">MySQL</phrase><phrase os=\"opensuse;sles\">MariaDB or MySQL</phrase> database server and set it to start automatically when the system boots:"
msgstr ""
#: ./doc/install-guide/section_basics-database.xml:82(para)
msgid "Finally, you should set a root password for your <phrase os=\"rhel;fedora;centos\">MySQL</phrase><phrase os=\"opensuse;sles\">MariaDB or MySQL</phrase> database. The OpenStack programs that set up databases and tables prompt you for this password if it is set."
msgstr ""
#: ./doc/install-guide/section_basics-database.xml:88(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 <placeholder-1/> command. Note that if <placeholder-2/> fails you might need to use <placeholder-3/> first:"
msgstr ""
#: ./doc/install-guide/section_basics-database.xml:97(para)
msgid "<phrase os=\"rhel;centos;fedora;opensuse;sles\">If you have not already set a root database password, press <keycap>ENTER</keycap> when you are prompted for the password.</phrase> This command presents a number of options for you to secure your database installation. Respond <placeholder-1/> to all prompts unless you have a good reason to do otherwise."
msgstr ""
#: ./doc/install-guide/section_basics-database.xml:106(title)
msgid "Node setup"
msgstr ""
#: ./doc/install-guide/section_basics-database.xml:107(para)
msgid "On all nodes other than the controller node, install the MySQL Python library:"
msgstr ""
#: ./doc/install-guide/section_basics-packages.xml:6(title)
msgid "OpenStack packages"
msgstr ""
#: ./doc/install-guide/section_basics-packages.xml:7(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/install-guide/section_basics-packages.xml:11(para)
msgid "This section describes the configuration you must complete after you configure machines to install the latest OpenStack packages."
msgstr ""
#: ./doc/install-guide/section_basics-packages.xml:14(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. To enable the RDO repository, download and install the <package>rdo-release-icehouse</package> package:"
msgstr ""
#: ./doc/install-guide/section_basics-packages.xml:21(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 <package>epel-release</package> package (see <link href=\"http://download.fedoraproject.org/pub/epel/6/x86_64/repoview/epel-release.html\">http://download.fedoraproject.org/pub/epel/6/x86_64/repoview/epel-release.html</link>). For example:"
msgstr ""
#: ./doc/install-guide/section_basics-packages.xml:30(para)
msgid "The <package>openstack-utils</package> package contains utility programs that make installation and configuration easier. These programs are used throughout this guide. Install <package>openstack-utils</package>. This verifies that you can access the RDO repository:"
msgstr ""
#: ./doc/install-guide/section_basics-packages.xml:37(para)
msgid "Use the Open Build Service repositories for <glossterm>Icehouse</glossterm> based on your openSUSE or SUSE Linux Enterprise Server version."
msgstr ""
#: ./doc/install-guide/section_basics-packages.xml:40(para)
msgid "For openSUSE 13.1 use:"
msgstr ""
#: ./doc/install-guide/section_basics-packages.xml:42(para)
msgid "If you use SUSE Linux Enterprise Server 11 SP3, use:"
msgstr ""
#: ./doc/install-guide/section_basics-packages.xml:45(para)
msgid "The <package>openstack-utils</package> package contains utility programs that make installation and configuration easier. These programs are used throughout this guide. Install <package>openstack-utils</package>. This verifies that you can access the Open Build Service repository:"
msgstr ""
#: ./doc/install-guide/section_basics-packages.xml:52(para)
msgid "The <application>openstack-config</application> program in the <package>openstack-utils</package> package uses <application>crudini</application> to manipulate configuration files. However, <application>crudini</application> version 0.3 does not support multi valued options. See <link href=\"https://bugs.launchpad.net/openstack-manuals/+bug/1269271\">https://bugs.launchpad.net/openstack-manuals/+bug/1269271</link>. 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/install-guide/section_basics-packages.xml:64(para)
msgid "The <package>openstack-selinux</package> 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 <package>openstack-selinux</package>:"
msgstr ""
#: ./doc/install-guide/section_basics-packages.xml:71(para)
msgid "Upgrade your system packages:"
msgstr ""
#: ./doc/install-guide/section_basics-packages.xml:75(para)
msgid "If the upgrade included a new kernel package, reboot the system to ensure the new kernel is running:"
msgstr ""
#: ./doc/install-guide/section_basics-packages.xml:79(title)
msgid "To use the Ubuntu Cloud Archive for Icehouse"
msgstr ""
#: ./doc/install-guide/section_basics-packages.xml:80(para)
msgid "The <link href=\"https://wiki.ubuntu.com/ServerTeam/CloudArchive\">Ubuntu Cloud Archive</link> is a special repository that allows you to install newer releases of OpenStack on the stable supported version of Ubuntu."
msgstr ""
#: ./doc/install-guide/section_basics-packages.xml:85(para)
msgid "Icehouse is in the main repository for 14.04 - this step is not required."
msgstr ""
#: ./doc/install-guide/section_basics-packages.xml:88(para)
msgid "Install the Ubuntu Cloud Archive for <glossterm>Icehouse</glossterm>: <placeholder-1/>"
msgstr ""
#: ./doc/install-guide/section_basics-packages.xml:94(para)
msgid "Update the package database and upgrade your system:"
msgstr ""
#: ./doc/install-guide/section_basics-packages.xml:99(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/install-guide/section_basics-packages.xml:103(para)
msgid "Install the Ubuntu 13.10 backported kernel:"
msgstr ""
#: ./doc/install-guide/section_basics-packages.xml:107(para)
msgid "Reboot the system for all changes to take effect:"
msgstr ""
#: ./doc/install-guide/section_basics-packages.xml:112(title)
msgid "To use the Debian Wheezy backports archive for Icehouse"
msgstr ""
#: ./doc/install-guide/section_basics-packages.xml:114(para)
msgid "The <glossterm>Icehouse</glossterm> 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/install-guide/section_basics-packages.xml:120(para)
msgid "Install the Debian Wheezy backport repository Icehouse:"
msgstr ""
#: ./doc/install-guide/section_basics-packages.xml:125(para)
msgid "Install the Debian Wheezy OpenStack repository for Icehouse:"
msgstr ""
#: ./doc/install-guide/section_basics-packages.xml:130(para)
msgid "Update the repository database and install the key:"
msgstr ""
#: ./doc/install-guide/section_basics-packages.xml:134(para)
msgid "Update the package database, upgrade your system, and reboot for all changes to take effect:"
msgstr ""
#: ./doc/install-guide/section_basics-packages.xml:140(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 <link href=\"http://archive.gplhost.com/readme.mirrors\">http://archive.gplhost.com/readme.mirrors</link>."
msgstr ""
#: ./doc/install-guide/section_basics-packages.xml:147(title)
msgid "Manually install python-argparse"
msgstr ""
#: ./doc/install-guide/section_basics-packages.xml:148(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/install-guide/section_basics-packages.xml:152(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 <package>python-argparse</package> package separately. In Python 2.7, this package is installed by default. Unfortunately, in Python 2.7, this package does not include <code>Provides: python-argparse</code> directive."
msgstr ""
#: ./doc/install-guide/section_basics-packages.xml:160(para)
msgid "Because the packages are maintained in Sid where the <code>Provides: python-argparse</code> directive causes an error, and the Debian OpenStack maintainer wants to maintain one version of the OpenStack packages, you must manually install the <package>python-argparse</package> 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/install-guide/section_basics-packages.xml:169(para)
msgid "This caveat applies to most OpenStack packages in Wheezy."
msgstr ""
#: ./doc/install-guide/section_basics-networking.xml:6(title)
msgid "Networking"
msgstr ""
#: ./doc/install-guide/section_basics-networking.xml:7(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 <link os=\"ubuntu\" href=\"https://help.ubuntu.com/lts/serverguide/network-configuration.html\">documentation.</link><link os=\"debian\" href=\"https://wiki.debian.org/NetworkConfiguration\">documentation.</link><link os=\"rhel;centos;fedora\" href=\"https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/s1-networkscripts-interfaces.html\">documentation.</link><link os=\"sles;opensuse\" href=\"https://www.suse.com/documentation/sles11/book_sle_admin/data/sec_basicnet_manconf.html\">SLES 11</link><phrase os=\"sles;opensuse\"> or </phrase><link os=\"sles;opensuse\" href=\"http://activedoc.opensuse.org/book/opensuse-reference/chapter-13-basic-networking\">openSUSE documentation.</link>"
msgstr ""
#: ./doc/install-guide/section_basics-networking.xml:30(title)
msgid "To disable <systemitem class=\"service\">NetworkManager</systemitem> and enable the <systemitem class=\"service\">network</systemitem> service:"
msgstr ""
#: ./doc/install-guide/section_basics-networking.xml:41(title)
msgid "To disable <systemitem class=\"service\">NetworkManager</systemitem>:"
msgstr ""
#: ./doc/install-guide/section_basics-networking.xml:43(para)
msgid "Use the YaST network module:"
msgstr ""
#: ./doc/install-guide/section_basics-networking.xml:45(para)
msgid "For more information, see the <link href=\"https://www.suse.com/documentation/sles11/book_sle_admin/data/sec_nm_activate.html\">SLES </link> or the <link href=\"http://activedoc.opensuse.org/book/opensuse-reference/chapter-13-basic-networking#sec.basicnet.yast.netcard.global\"> openSUSE documentation</link>."
msgstr ""
#: ./doc/install-guide/section_basics-networking.xml:53(para)
msgid "RHEL and derivatives including CentOS and Scientific Linux enable a restrictive <glossterm>firewall</glossterm> 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 <link href=\"http://docs.openstack.org/sec/\"> OpenStack Security Guide</link>."
msgstr ""
#: ./doc/install-guide/section_basics-networking.xml:60(para)
msgid "On Fedora, <literal>firewalld</literal> replaces <literal>iptables</literal> as the default firewall system. While you can use <literal>firewalld</literal> successfully, this guide references <literal>iptables</literal> for compatibility with other distributions."
msgstr ""
#: ./doc/install-guide/section_basics-networking.xml:66(title)
msgid "To disable <literal>firewalld</literal> and enable <literal>iptables</literal>:"
msgstr ""
#: ./doc/install-guide/section_basics-networking.xml:75(para)
msgid "Proceed to network configuration for the example <link linkend=\"basics-networking-neutron\">OpenStack Networking (neutron) </link> or <link linkend=\"basics-networking-nova\">legacy networking (nova-network)</link> architecture."
msgstr ""
#: ./doc/install-guide/section_cinder-verify.xml:5(title)
msgid "Verify the Block Storage installation"
msgstr ""
#: ./doc/install-guide/section_cinder-verify.xml:6(para)
msgid "To verify that the Block Storage is installed and configured properly, create a new volume."
msgstr ""
#: ./doc/install-guide/section_cinder-verify.xml:8(para)
msgid "For more information about how to manage volumes, see the <link href=\"http://docs.openstack.org/user-guide/content/index.html\"><citetitle>OpenStack User Guide</citetitle></link>."
msgstr ""
#: ./doc/install-guide/section_cinder-verify.xml:13(para)
msgid "Source the <filename>demo-openrc.sh</filename> file:"
msgstr ""
#: ./doc/install-guide/section_cinder-verify.xml:18(para)
msgid "Use the <placeholder-1/> command to create a new volume:"
msgstr ""
#: ./doc/install-guide/section_cinder-verify.xml:40(para)
msgid "Make sure that the volume has been correctly created with the <placeholder-1/> command:"
msgstr ""
#: ./doc/install-guide/section_cinder-verify.xml:48(para)
msgid "If the status value is not <literal>available</literal>, the volume creation failed. Check the log files in the <filename>/var/log/cinder/</filename> directory on the controller and volume nodes to get information about the failure."
msgstr ""
#: ./doc/install-guide/section_glance-verify.xml:5(title)
msgid "Verify the Image Service installation"
msgstr ""
#: ./doc/install-guide/section_glance-verify.xml:6(para)
msgid "To test the Image Service installation, download at least one virtual machine image that is known to work with OpenStack. For example, CirrOS is a small test image that is often used for testing OpenStack deployments (<link href=\"http://download.cirros-cloud.net/\">CirrOS downloads</link>). This walk through uses the 64-bit CirrOS QCOW2 image."
msgstr ""
#: ./doc/install-guide/section_glance-verify.xml:13(para)
msgid "For more information about how to download and build images, see <link href=\"http://docs.openstack.org/image-guide/content/index.html\"><citetitle>OpenStack Virtual Machine Image Guide</citetitle></link>. For information about how to manage images, see the <link href=\"http://docs.openstack.org/user-guide/content/index.html\"><citetitle>OpenStack User Guide</citetitle></link>."
msgstr ""
#: ./doc/install-guide/section_glance-verify.xml:24(para)
msgid "Download the image into a dedicated directory using <placeholder-1/> or <placeholder-2/>:"
msgstr ""
#: ./doc/install-guide/section_glance-verify.xml:32(para)
msgid "Upload the image to the Image Service:"
msgstr ""
#: ./doc/install-guide/section_glance-verify.xml:33(replaceable) ./doc/install-guide/section_glance-verify.xml:38(replaceable)
msgid "IMAGELABEL"
msgstr ""
#: ./doc/install-guide/section_glance-verify.xml:33(replaceable) ./doc/install-guide/section_glance-verify.xml:45(replaceable)
msgid "FILEFORMAT"
msgstr ""
#: ./doc/install-guide/section_glance-verify.xml:34(replaceable) ./doc/install-guide/section_glance-verify.xml:65(replaceable)
msgid "CONTAINERFORMAT"
msgstr ""
#: ./doc/install-guide/section_glance-verify.xml:34(replaceable) ./doc/install-guide/section_glance-verify.xml:86(replaceable)
msgid "ACCESSVALUE"
msgstr ""
#: ./doc/install-guide/section_glance-verify.xml:34(replaceable) ./doc/install-guide/section_glance-verify.xml:101(replaceable)
msgid "IMAGEFILE"
msgstr ""
#: ./doc/install-guide/section_glance-verify.xml:35(para)
msgid "Where:"
msgstr ""
#: ./doc/install-guide/section_glance-verify.xml:40(para)
msgid "Arbitrary label. The name by which users refer to the image."
msgstr ""
#: ./doc/install-guide/section_glance-verify.xml:47(para)
msgid "Specifies the format of the image file. Valid formats include <literal>qcow2</literal>, <literal>raw</literal>, <literal>vhd</literal>, <literal>vmdk</literal>, <literal>vdi</literal>, <literal>iso</literal>, <literal>aki</literal>, <literal>ari</literal>, and <literal>ami</literal>."
msgstr ""
#: ./doc/install-guide/section_glance-verify.xml:58(para)
msgid "You can verify the format using the <placeholder-1/> command: <placeholder-2/>"
msgstr ""
#: ./doc/install-guide/section_glance-verify.xml:67(para)
msgid "Specifies the container format. Valid formats include: <literal>bare</literal>, <literal>ovf</literal>, <literal>aki</literal>, <literal>ari</literal> and <literal>ami</literal>."
msgstr ""
#: ./doc/install-guide/section_glance-verify.xml:73(para)
msgid "Specify <literal>bare</literal> to indicate that the image file is not in a file format that contains metadata about the virtual machine. Although this field is currently required, it is not actually used by any of the OpenStack services and has no effect on system behavior. Because the value is not used anywhere, it is safe to always specify <literal>bare</literal> as the container format."
msgstr ""
#: ./doc/install-guide/section_glance-verify.xml:90(para)
msgid "true - All users can view and use the image."
msgstr ""
#: ./doc/install-guide/section_glance-verify.xml:94(para)
msgid "false - Only administrators can view and use the image."
msgstr ""
#: ./doc/install-guide/section_glance-verify.xml:88(para)
msgid "Specifies image access: <placeholder-1/>"
msgstr ""
#: ./doc/install-guide/section_glance-verify.xml:103(para)
msgid "Specifies the name of your downloaded image file."
msgstr ""
#: ./doc/install-guide/section_glance-verify.xml:108(para) ./doc/install-guide/section_glance-verify.xml:157(para)
msgid "For example:"
msgstr ""
#: ./doc/install-guide/section_glance-verify.xml:133(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/install-guide/section_glance-verify.xml:139(para)
msgid "Confirm that the image was uploaded and display its attributes:"
msgstr ""
#: ./doc/install-guide/section_glance-verify.xml:149(para)
msgid "You can now remove the locally downloaded image, since it is stored and available through the Image Service."
msgstr ""
#: ./doc/install-guide/section_glance-verify.xml:156(para)
msgid "Alternatively, the upload to the Image Service can be done without having to use local disk space to store the file, by use of the <parameter>--copy-from</parameter> parameter."
msgstr ""
#: ./doc/install-guide/ch_clients.xml:6(title)
msgid "Install and configure the OpenStack clients"
msgstr ""
#: ./doc/install-guide/ch_clients.xml:7(para)
msgid "The following sections contain information about working with the OpenStack clients. Recall: in the previous section, you used the <placeholder-1/> client."
msgstr ""
#: ./doc/install-guide/ch_clients.xml:10(para)
msgid "You must install the client tools to complete the rest of the installation."
msgstr ""
#: ./doc/install-guide/ch_clients.xml:12(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/install-guide/ch_clients.xml:20(title)
msgid "Create openrc.sh files"
msgstr ""
#: ./doc/install-guide/ch_clients.xml:22(para)
msgid "As explained in <xref linkend=\"openrc-create\"/>, <phrase os=\"rhel;centos;fedora;opensuse;sles;ubuntu\"> use the credentials from <xref linkend=\"keystone-users\"/> and</phrase> create the following <filename><replaceable>PROJECT</replaceable>-openrc.sh</filename> files:"
msgstr ""
#: ./doc/install-guide/ch_clients.xml:32(para)
msgid "<filename>admin-openrc.sh</filename> for the administrative user"
msgstr ""
#: ./doc/install-guide/ch_clients.xml:42(replaceable) ./doc/install-guide/section_ceilometer-install.xml:102(replaceable) ./doc/install-guide/section_ceilometer-install.xml:111(replaceable) ./doc/install-guide/section_ceilometer-install.xml:118(replaceable) ./doc/install-guide/section_ceilometer-install.xml:145(replaceable) ./doc/install-guide/section_ceilometer-install.xml:148(replaceable) ./doc/install-guide/section_ceilometer-install.xml:190(replaceable) ./doc/install-guide/section_ceilometer-install.xml:198(replaceable) ./doc/install-guide/section_ceilometer-install.xml:202(replaceable) ./doc/install-guide/section_ceilometer-install.xml:217(replaceable) ./doc/install-guide/section_ceilometer-install.xml:224(replaceable) ./doc/install-guide/section_ceilometer-install.xml:238(replaceable) ./doc/install-guide/section_ceilometer-install.xml:239(replaceable) ./doc/install-guide/section_ceilometer-install.xml:240(replaceable) ./doc/install-guide/section_trove-install.xml:66(replaceable) ./doc/install-guide/section_trove-install.xml:67(replaceable) ./doc/install-guide/section_trove-install.xml:68(replaceable) ./doc/install-guide/section_trove-install.xml:69(replaceable) ./doc/install-guide/section_trove-install.xml:70(replaceable) ./doc/install-guide/section_trove-install.xml:71(replaceable) ./doc/install-guide/section_trove-install.xml:84(replaceable) ./doc/install-guide/section_trove-install.xml:86(replaceable) ./doc/install-guide/section_trove-install.xml:88(replaceable) ./doc/install-guide/section_trove-install.xml:111(replaceable) ./doc/install-guide/section_trove-install.xml:113(replaceable) ./doc/install-guide/section_trove-install.xml:115(replaceable) ./doc/install-guide/section_trove-install.xml:131(replaceable) ./doc/install-guide/section_trove-install.xml:207(replaceable) ./doc/install-guide/section_trove-install.xml:212(replaceable) ./doc/install-guide/section_trove-install.xml:233(replaceable) ./doc/install-guide/section_trove-install.xml:234(replaceable) ./doc/install-guide/section_trove-install.xml:235(replaceable) ./doc/install-guide/section_nova-controller.xml:44(replaceable) ./doc/install-guide/section_nova-controller.xml:59(replaceable) ./doc/install-guide/section_nova-controller.xml:140(replaceable) ./doc/install-guide/section_nova-controller.xml:141(replaceable) ./doc/install-guide/section_nova-controller.xml:160(replaceable) ./doc/install-guide/section_nova-controller.xml:177(replaceable) ./doc/install-guide/section_nova-controller.xml:178(replaceable) ./doc/install-guide/section_nova-controller.xml:179(replaceable) ./doc/install-guide/section_neutron-ovs-compute-node.xml:143(replaceable) ./doc/install-guide/section_neutron-ovs-compute-node.xml:145(replaceable) ./doc/install-guide/section_neutron-ovs-compute-node.xml:179(replaceable) ./doc/install-guide/section_neutron-ovs-compute-node.xml:180(replaceable) ./doc/install-guide/section_neutron-ovs-compute-node.xml:194(replaceable) ./doc/install-guide/section_neutron-ovs-compute-node.xml:205(replaceable) ./doc/install-guide/section_neutron-ovs-compute-node.xml:214(replaceable) ./doc/install-guide/section_neutron-ovs-compute-node.xml:232(replaceable) ./doc/install-guide/section_neutron-ovs-compute-node.xml:242(replaceable) ./doc/install-guide/section_neutron-ovs-compute-node.xml:253(replaceable) ./doc/install-guide/section_neutron-ovs-compute-node.xml:258(replaceable) ./doc/install-guide/section_neutron-ml2-controller-node.xml:49(replaceable) ./doc/install-guide/section_neutron-ml2-controller-node.xml:50(replaceable) ./doc/install-guide/section_neutron-ml2-controller-node.xml:51(replaceable) ./doc/install-guide/section_neutron-ml2-controller-node.xml:87(replaceable) ./doc/install-guide/section_neutron-ml2-controller-node.xml:100(replaceable) ./doc/install-guide/section_neutron-ml2-controller-node.xml:113(replaceable) ./doc/install-guide/section_neutron-ml2-controller-node.xml:115(replaceable) ./doc/install-guide/section_neutron-ml2-controller-node.xml:145(replaceable) ./doc/install-guide/section_neutron-ml2-controller-node.xml:146(replaceable) ./doc/install-guide/section_neutron-ml2-controller-node.xml:174(replaceable) ./doc/install-guide/section_neutron-ml2-controller-node.xml:189(replaceable) ./doc/install-guide/section_neutron-ml2-controller-node.xml:202(replaceable) ./doc/install-guide/section_neutron-ml2-controller-node.xml:210(replaceable) ./doc/install-guide/section_neutron-ml2-controller-node.xml:229(replaceable) ./doc/install-guide/section_neutron-ml2-controller-node.xml:233(replaceable) ./doc/install-guide/section_neutron-ml2-controller-node.xml:350(replaceable) ./doc/install-guide/section_neutron-ml2-controller-node.xml:360(replaceable) ./doc/install-guide/section_neutron-ml2-controller-node.xml:384(replaceable) ./doc/install-guide/section_neutron-ml2-controller-node.xml:389(replaceable) ./doc/install-guide/section_keystone-services.xml:47(replaceable) ./doc/install-guide/section_keystone-services.xml:48(replaceable) ./doc/install-guide/section_keystone-services.xml:49(replaceable) ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:181(replaceable) ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:186(replaceable) ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:194(replaceable) ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:199(replaceable) ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:271(replaceable) ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:276(replaceable) ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:326(replaceable) ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:410(replaceable) ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:116(replaceable) ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:177(replaceable) ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:181(replaceable) ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:185(replaceable) ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:191(replaceable) ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:222(replaceable) ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:226(replaceable) ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:234(replaceable) ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:321(replaceable) ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:325(replaceable) ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:329(replaceable) ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:335(replaceable) ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:377(replaceable) ./doc/install-guide/section_neutron-ovs-controller-node.xml:55(replaceable) ./doc/install-guide/section_neutron-ovs-controller-node.xml:56(replaceable) ./doc/install-guide/section_neutron-ovs-controller-node.xml:57(replaceable) ./doc/install-guide/section_neutron-ovs-controller-node.xml:81(replaceable) ./doc/install-guide/section_neutron-ovs-controller-node.xml:98(replaceable) ./doc/install-guide/section_neutron-ovs-controller-node.xml:100(replaceable) ./doc/install-guide/section_neutron-ovs-controller-node.xml:133(replaceable) ./doc/install-guide/section_neutron-ovs-controller-node.xml:134(replaceable) ./doc/install-guide/section_neutron-ovs-controller-node.xml:161(replaceable) ./doc/install-guide/section_neutron-ovs-controller-node.xml:179(replaceable) ./doc/install-guide/section_neutron-ovs-controller-node.xml:229(replaceable) ./doc/install-guide/section_neutron-ovs-controller-node.xml:239(replaceable) ./doc/install-guide/section_neutron-ovs-controller-node.xml:250(replaceable) ./doc/install-guide/section_neutron-ovs-controller-node.xml:255(replaceable) ./doc/install-guide/section_ceilometer-glance.xml:17(replaceable) ./doc/install-guide/section_ceilometer-glance.xml:23(replaceable) ./doc/install-guide/section_basics-networking-nova.xml:202(replaceable) ./doc/install-guide/section_basics-networking-neutron.xml:277(replaceable) ./doc/install-guide/section_basics-networking-neutron.xml:321(replaceable) ./doc/install-guide/section_neutron-ovs-network-node.xml:97(replaceable) ./doc/install-guide/section_neutron-ovs-network-node.xml:99(replaceable) ./doc/install-guide/section_neutron-ovs-network-node.xml:130(replaceable) ./doc/install-guide/section_neutron-ovs-network-node.xml:131(replaceable) ./doc/install-guide/section_neutron-ovs-network-node.xml:145(replaceable) ./doc/install-guide/section_neutron-ovs-network-node.xml:156(replaceable) ./doc/install-guide/section_neutron-ovs-network-node.xml:165(replaceable) ./doc/install-guide/section_neutron-ovs-network-node.xml:389(replaceable) ./doc/install-guide/section_neutron-ovs-network-node.xml:394(replaceable) ./doc/install-guide/section_neutron-ovs-network-node.xml:399(replaceable) ./doc/install-guide/section_neutron-ovs-network-node.xml:409(replaceable) ./doc/install-guide/section_neutron-single-flat.xml:193(replaceable) ./doc/install-guide/section_neutron-single-flat.xml:212(replaceable) ./doc/install-guide/section_neutron-single-flat.xml:229(replaceable) ./doc/install-guide/section_neutron-single-flat.xml:234(replaceable) ./doc/install-guide/section_neutron-single-flat.xml:284(replaceable) ./doc/install-guide/section_neutron-single-flat.xml:287(replaceable) ./doc/install-guide/section_neutron-single-flat.xml:291(replaceable) ./doc/install-guide/section_neutron-single-flat.xml:301(replaceable) ./doc/install-guide/section_neutron-single-flat.xml:334(replaceable) ./doc/install-guide/section_neutron-single-flat.xml:339(replaceable) ./doc/install-guide/section_neutron-single-flat.xml:348(replaceable) ./doc/install-guide/section_neutron-single-flat.xml:367(replaceable) ./doc/install-guide/section_neutron-single-flat.xml:426(replaceable) ./doc/install-guide/section_neutron-single-flat.xml:451(replaceable) ./doc/install-guide/section_neutron-single-flat.xml:487(replaceable) ./doc/install-guide/section_cinder-node.xml:113(replaceable) ./doc/install-guide/section_cinder-node.xml:115(replaceable) ./doc/install-guide/section_cinder-node.xml:131(replaceable) ./doc/install-guide/section_cinder-node.xml:132(replaceable) ./doc/install-guide/section_cinder-node.xml:150(replaceable) ./doc/install-guide/section_cinder-node.xml:161(replaceable) ./doc/install-guide/section_cinder-node.xml:170(replaceable) ./doc/install-guide/section_cinder-node.xml:183(replaceable) ./doc/install-guide/section_cinder-node.xml:186(replaceable) ./doc/install-guide/section_cinder-node.xml:202(replaceable) ./doc/install-guide/section_cinder-node.xml:205(replaceable) ./doc/install-guide/section_cinder-controller.xml:44(replaceable) ./doc/install-guide/section_cinder-controller.xml:47(replaceable) ./doc/install-guide/section_cinder-controller.xml:83(replaceable) ./doc/install-guide/section_cinder-controller.xml:85(replaceable) ./doc/install-guide/section_cinder-controller.xml:101(replaceable) ./doc/install-guide/section_cinder-controller.xml:102(replaceable) ./doc/install-guide/section_cinder-controller.xml:120(replaceable) ./doc/install-guide/section_cinder-controller.xml:153(replaceable) ./doc/install-guide/section_cinder-controller.xml:154(replaceable) ./doc/install-guide/section_cinder-controller.xml:155(replaceable) ./doc/install-guide/section_cinder-controller.xml:163(replaceable) ./doc/install-guide/section_cinder-controller.xml:164(replaceable) ./doc/install-guide/section_cinder-controller.xml:165(replaceable) ./doc/install-guide/section_neutron-ml2-network-node.xml:65(replaceable) ./doc/install-guide/section_neutron-ml2-network-node.xml:67(replaceable) ./doc/install-guide/section_neutron-ml2-network-node.xml:97(replaceable) ./doc/install-guide/section_neutron-ml2-network-node.xml:98(replaceable) ./doc/install-guide/section_neutron-ml2-network-node.xml:115(replaceable) ./doc/install-guide/section_neutron-ml2-network-node.xml:126(replaceable) ./doc/install-guide/section_neutron-ml2-network-node.xml:141(replaceable) ./doc/install-guide/section_neutron-ml2-network-node.xml:269(replaceable) ./doc/install-guide/section_neutron-ml2-network-node.xml:279(replaceable) ./doc/install-guide/section_neutron-ml2-network-node.xml:300(replaceable) ./doc/install-guide/section_neutron-ml2-network-node.xml:305(replaceable) ./doc/install-guide/section_neutron-ml2-compute-node.xml:62(replaceable) ./doc/install-guide/section_neutron-ml2-compute-node.xml:64(replaceable) ./doc/install-guide/section_neutron-ml2-compute-node.xml:94(replaceable) ./doc/install-guide/section_neutron-ml2-compute-node.xml:95(replaceable) ./doc/install-guide/section_neutron-ml2-compute-node.xml:112(replaceable) ./doc/install-guide/section_neutron-ml2-compute-node.xml:123(replaceable) ./doc/install-guide/section_neutron-ml2-compute-node.xml:138(replaceable) ./doc/install-guide/section_neutron-ml2-compute-node.xml:294(replaceable) ./doc/install-guide/section_neutron-ml2-compute-node.xml:304(replaceable) ./doc/install-guide/section_neutron-ml2-compute-node.xml:328(replaceable) ./doc/install-guide/section_neutron-ml2-compute-node.xml:333(replaceable) ./doc/install-guide/section_heat-install.xml:40(replaceable) ./doc/install-guide/section_heat-install.xml:46(replaceable) ./doc/install-guide/section_heat-install.xml:92(replaceable) ./doc/install-guide/section_heat-install.xml:95(replaceable) ./doc/install-guide/section_heat-install.xml:113(replaceable) ./doc/install-guide/section_heat-install.xml:116(replaceable) ./doc/install-guide/section_heat-install.xml:122(replaceable) ./doc/install-guide/section_heat-install.xml:133(replaceable) ./doc/install-guide/section_heat-install.xml:134(replaceable) ./doc/install-guide/section_heat-install.xml:135(replaceable) ./doc/install-guide/section_heat-install.xml:140(replaceable) ./doc/install-guide/section_heat-install.xml:141(replaceable) ./doc/install-guide/section_heat-install.xml:142(replaceable) ./doc/install-guide/section_ceilometer-nova.xml:79(replaceable) ./doc/install-guide/section_ceilometer-nova.xml:85(replaceable) ./doc/install-guide/section_ceilometer-nova.xml:91(replaceable) ./doc/install-guide/section_ceilometer-nova.xml:107(replaceable) ./doc/install-guide/section_ceilometer-nova.xml:122(replaceable) ./doc/install-guide/section_nova-compute.xml:74(replaceable) ./doc/install-guide/section_nova-compute.xml:75(replaceable) ./doc/install-guide/section_nova-compute.xml:93(replaceable) ./doc/install-guide/section_nova-compute.xml:94(replaceable) ./doc/install-guide/section_nova-compute.xml:106(replaceable) ./doc/install-guide/section_nova-compute.xml:131(replaceable) ./doc/install-guide/section_nova-compute.xml:143(replaceable) ./doc/install-guide/section_nova-compute.xml:151(replaceable) ./doc/install-guide/section_nova-compute.xml:154(replaceable) ./doc/install-guide/section_glance-install.xml:55(replaceable) ./doc/install-guide/section_glance-install.xml:57(replaceable) ./doc/install-guide/section_glance-install.xml:65(replaceable) ./doc/install-guide/section_glance-install.xml:74(replaceable) ./doc/install-guide/section_glance-install.xml:89(replaceable) ./doc/install-guide/section_glance-install.xml:102(replaceable) ./doc/install-guide/section_glance-install.xml:147(replaceable) ./doc/install-guide/section_glance-install.xml:149(replaceable) ./doc/install-guide/section_glance-install.xml:163(replaceable) ./doc/install-guide/section_glance-install.xml:165(replaceable) ./doc/install-guide/section_glance-install.xml:188(replaceable) ./doc/install-guide/section_glance-install.xml:189(replaceable) ./doc/install-guide/section_glance-install.xml:213(replaceable) ./doc/install-guide/section_glance-install.xml:214(replaceable) ./doc/install-guide/section_glance-install.xml:215(replaceable) ./doc/install-guide/section_keystone-install.xml:30(replaceable) ./doc/install-guide/section_keystone-install.xml:38(replaceable) ./doc/install-guide/object-storage/section_object-storage-install-config-proxy-node.xml:82(replaceable) ./doc/install-guide/object-storage/section_object-storage-install.xml:95(replaceable) ./doc/install-guide/object-storage/section_object-storage-install.xml:96(replaceable) ./doc/install-guide/object-storage/section_object-storage-install.xml:97(replaceable)
msgid "controller"
msgstr ""
#: ./doc/install-guide/ch_clients.xml:37(para)
msgid "<filename>demo-openrc.sh</filename> for the normal user: <placeholder-1/>"
msgstr ""
#: ./doc/install-guide/section_launch-instance-nova.xml:6(title)
msgid "Launch an instance with legacy networking (nova-network)"
msgstr ""
#: ./doc/install-guide/section_launch-instance-nova.xml:8(title) ./doc/install-guide/section_launch-instance-neutron.xml:8(title)
msgid "To generate a keypair"
msgstr ""
#: ./doc/install-guide/section_launch-instance-nova.xml:9(para) ./doc/install-guide/section_launch-instance-neutron.xml:9(para)
msgid "Most cloud images support <glossterm>public key authentication</glossterm> rather than conventional username/password authentication. Before launching an instance, you must generate a public/private key pair using <placeholder-1/> and add the public key to your OpenStack environment."
msgstr ""
#: ./doc/install-guide/section_launch-instance-nova.xml:15(para) ./doc/install-guide/section_launch-instance-neutron.xml:15(para) ./doc/install-guide/section_neutron-initial-networks.xml:132(para)
msgid "Source the <literal>demo</literal> tenant credentials:"
msgstr ""
#: ./doc/install-guide/section_launch-instance-nova.xml:19(para) ./doc/install-guide/section_launch-instance-neutron.xml:19(para)
msgid "Generate a key pair:"
msgstr ""
#: ./doc/install-guide/section_launch-instance-nova.xml:23(para) ./doc/install-guide/section_launch-instance-neutron.xml:23(para)
msgid "Add the public key to your OpenStack environment:"
msgstr ""
#: ./doc/install-guide/section_launch-instance-nova.xml:30(para) ./doc/install-guide/section_launch-instance-neutron.xml:30(para)
msgid "Verify addition of the public key:"
msgstr ""
#: ./doc/install-guide/section_launch-instance-nova.xml:40(title) ./doc/install-guide/section_launch-instance-neutron.xml:40(title)
msgid "To launch an instance"
msgstr ""
#: ./doc/install-guide/section_launch-instance-nova.xml:41(para) ./doc/install-guide/section_launch-instance-neutron.xml:41(para)
msgid "To launch an instance, you must at least specify the flavor, image name, network, security group, key, and instance name."
msgstr ""
#: ./doc/install-guide/section_launch-instance-nova.xml:44(para) ./doc/install-guide/section_launch-instance-neutron.xml:44(para)
msgid "A flavor specifies a virtual resource allocation profile which includes processor, memory, and storage."
msgstr ""
#: ./doc/install-guide/section_launch-instance-nova.xml:46(para) ./doc/install-guide/section_launch-instance-neutron.xml:46(para)
msgid "List available flavors:"
msgstr ""
#: ./doc/install-guide/section_launch-instance-nova.xml:57(para) ./doc/install-guide/section_launch-instance-neutron.xml:57(para)
msgid "Your first instance uses the <literal>m1.tiny</literal> flavor."
msgstr ""
#: ./doc/install-guide/section_launch-instance-nova.xml:60(para) ./doc/install-guide/section_launch-instance-neutron.xml:60(para)
msgid "You can also reference a flavor by ID."
msgstr ""
#: ./doc/install-guide/section_launch-instance-nova.xml:64(para) ./doc/install-guide/section_launch-instance-neutron.xml:64(para)
msgid "List available images:"
msgstr ""
#: ./doc/install-guide/section_launch-instance-nova.xml:71(para) ./doc/install-guide/section_launch-instance-neutron.xml:71(para)
msgid "Your first instance uses the <literal>cirros-0.3.2-x86_64</literal> image."
msgstr ""
#: ./doc/install-guide/section_launch-instance-nova.xml:75(para) ./doc/install-guide/section_launch-instance-neutron.xml:75(para)
msgid "List available networks:"
msgstr ""
#: ./doc/install-guide/section_launch-instance-nova.xml:77(para)
msgid "You must source the <literal>admin</literal> tenant credentials for this step and then source the <literal>demo</literal> tenant credentials for the remaining steps."
msgstr ""
#: ./doc/install-guide/section_launch-instance-nova.xml:88(para) ./doc/install-guide/section_launch-instance-neutron.xml:83(para)
msgid "Your first instance uses the <literal>demo-net</literal> tenant network. However, you must reference this network using the ID instead of the name."
msgstr ""
#: ./doc/install-guide/section_launch-instance-nova.xml:93(para) ./doc/install-guide/section_launch-instance-neutron.xml:88(para)
msgid "List available security groups:"
msgstr ""
#: ./doc/install-guide/section_launch-instance-nova.xml:100(para)
msgid "Your first instance uses the <literal>default</literal> 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 <link linkend=\"launch-instance-nova-remoteaccess\"> configure remote access</link>."
msgstr ""
#: ./doc/install-guide/section_launch-instance-nova.xml:108(para) ./doc/install-guide/section_launch-instance-neutron.xml:103(para)
msgid "Launch the instance:"
msgstr ""
#: ./doc/install-guide/section_launch-instance-nova.xml:109(para) ./doc/install-guide/section_launch-instance-neutron.xml:104(para)
msgid "Replace <replaceable>DEMO_NET_ID</replaceable> with the ID of the <literal>demo-net</literal> tenant network."
msgstr ""
#: ./doc/install-guide/section_launch-instance-nova.xml:111(replaceable) ./doc/install-guide/section_launch-instance-neutron.xml:106(replaceable)
msgid "DEMO_NET_ID"
msgstr ""
#: ./doc/install-guide/section_launch-instance-nova.xml:112(replaceable) ./doc/install-guide/section_launch-instance-nova.xml:162(replaceable) ./doc/install-guide/section_launch-instance-neutron.xml:107(replaceable) ./doc/install-guide/section_launch-instance-neutron.xml:157(replaceable)
msgid "demo-instance1"
msgstr ""
#: ./doc/install-guide/section_launch-instance-nova.xml:145(para) ./doc/install-guide/section_launch-instance-neutron.xml:140(para)
msgid "Check the status of your instance:"
msgstr ""
#: ./doc/install-guide/section_launch-instance-nova.xml:152(para) ./doc/install-guide/section_launch-instance-neutron.xml:147(para)
msgid "The status changes from <literal>BUILD</literal> to <literal>ACTIVE</literal> when your instance finishes the build process."
msgstr ""
#: ./doc/install-guide/section_launch-instance-nova.xml:158(title) ./doc/install-guide/section_launch-instance-neutron.xml:153(title)
msgid "To access your instance using a virtual console"
msgstr ""
#: ./doc/install-guide/section_launch-instance-nova.xml:160(para) ./doc/install-guide/section_launch-instance-neutron.xml:155(para)
msgid "Obtain a <glossterm>Virtual Network Computing (VNC)</glossterm> session URL for your instance and access it from a web browser:"
msgstr ""
#: ./doc/install-guide/section_launch-instance-nova.xml:169(para) ./doc/install-guide/section_launch-instance-neutron.xml:164(para)
msgid "If your web browser runs on a host that cannot resolve the <replaceable>controller</replaceable> host name, you can replace <replaceable>controller</replaceable> with the IP address of the management interface on your controller node."
msgstr ""
#: ./doc/install-guide/section_launch-instance-nova.xml:174(para) ./doc/install-guide/section_launch-instance-neutron.xml:169(para)
msgid "The CirrOS image includes conventional username/password authentication and provides these credentials at the login prompt. After logging into CirrOS, we recommend that you verify network connectivity using <placeholder-1/>."
msgstr ""
#: ./doc/install-guide/section_launch-instance-nova.xml:178(para)
msgid "Verify the <literal>demo-net</literal> network:"
msgstr ""
#: ./doc/install-guide/section_launch-instance-nova.xml:192(title) ./doc/install-guide/section_launch-instance-neutron.xml:199(title)
msgid "To access your instance remotely"
msgstr ""
#: ./doc/install-guide/section_launch-instance-nova.xml:194(para) ./doc/install-guide/section_launch-instance-neutron.xml:201(para)
msgid "Add rules to the <literal>default</literal> security group:"
msgstr ""
#: ./doc/install-guide/section_launch-instance-nova.xml:197(para) ./doc/install-guide/section_launch-instance-neutron.xml:204(para)
msgid "Permit <glossterm>ICMP</glossterm> (ping):"
msgstr ""
#: ./doc/install-guide/section_launch-instance-nova.xml:206(para) ./doc/install-guide/section_launch-instance-neutron.xml:213(para)
msgid "Permit secure shell (SSH) access:"
msgstr ""
#: ./doc/install-guide/section_launch-instance-nova.xml:217(para) ./doc/install-guide/section_launch-instance-neutron.xml:258(para)
msgid "Verify network connectivity using <placeholder-1/> from the controller node or any host on the external network:"
msgstr ""
#: ./doc/install-guide/section_launch-instance-nova.xml:231(para) ./doc/install-guide/section_launch-instance-neutron.xml:272(para)
msgid "Access your instance using SSH from the controller node or any host on the external network:"
msgstr ""
#: ./doc/install-guide/section_launch-instance-nova.xml:240(para) ./doc/install-guide/section_launch-instance-neutron.xml:281(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 <literal>cirros</literal> user."
msgstr ""
#: ./doc/install-guide/section_launch-instance-nova.xml:246(para) ./doc/install-guide/section_launch-instance-neutron.xml:287(para)
msgid "If your instance does not launch or seem to work as you expect, see the <link href=\"http://docs.openstack.org/ops\"><citetitle>OpenStack Operations Guide</citetitle></link> for more information or use one of the <link linkend=\"app_community_support\">many other options</link> to seek assistance. We want your environment to work!"
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/install-guide/section_debconf-keystone_authtoken.xml:30(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/install-guide/section_debconf-keystone_authtoken.xml:37(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/install-guide/section_debconf-keystone_authtoken.xml:44(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/install-guide/section_debconf-keystone_authtoken.xml:51(None)
msgid "@@image: 'figures/debconf-screenshots/service_keystone_authtoken_admin_password.png'; md5=0c30c80315d5e636dbe93a938fc2822b"
msgstr ""
#: ./doc/install-guide/section_debconf-keystone_authtoken.xml:6(title)
msgid "Services and the [keystone_authtoken]"
msgstr ""
#: ./doc/install-guide/section_debconf-keystone_authtoken.xml:7(para)
msgid "Because most OpenStack services must access the Identity Service, you must configure the IP address of the <code>keystone</code> server to be able to access it. You must also configure the <code>admin_tenant_name</code>, <code>admin_user</code>, and <code>admin_password</code> options for each service to work."
msgstr ""
#: ./doc/install-guide/section_debconf-keystone_authtoken.xml:13(para)
msgid "Generally, this section looks like this:"
msgstr ""
#: ./doc/install-guide/section_debconf-keystone_authtoken.xml:21(para)
msgid "The debconf system helps users configure the <code>auth_host</code>, <code>admin_tenant_name</code>, <code>admin_user</code> and <code>admin_password</code> options."
msgstr ""
#: ./doc/install-guide/section_debconf-keystone_authtoken.xml:25(para)
msgid "The following screens show an example Image Service configuration:"
msgstr ""
#: ./doc/install-guide/section_debconf-keystone_authtoken.xml:55(para)
msgid "This information is stored in the configuration file for each service. For example:"
msgstr ""
#: ./doc/install-guide/section_debconf-keystone_authtoken.xml:63(para)
msgid "The Debian OpenStack packages offer automation for this, so OpenStack users do not have to manually edit the configuration files."
msgstr ""
#: ./doc/install-guide/ch_swift.xml:6(title)
msgid "Add Object Storage"
msgstr ""
#: ./doc/install-guide/ch_swift.xml:7(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/install-guide/ch_swift.xml:31(para)
msgid "Your OpenStack environment now includes Object Storage. You can <link linkend=\"launch-instance\">launch an instance</link> or add more services to your environment in the following chapters."
msgstr ""
#: ./doc/install-guide/section_neutron-concepts.xml:6(title)
msgid "Networking concepts"
msgstr ""
#: ./doc/install-guide/section_neutron-concepts.xml:7(para)
msgid "OpenStack Networking (neutron) manages all of the 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 allows tenants to create advanced virtual network topologies including services such as <glossterm baseform=\"firewall\">firewalls</glossterm>, <glossterm baseform=\"load balancer\">load balancers</glossterm>, and <glossterm baseform=\"virtual private network (VPN)\"> virtual private networks (VPNs)</glossterm>."
msgstr ""
#: ./doc/install-guide/section_neutron-concepts.xml:16(para)
msgid "Networking provides the following object abstractions: networks, subnets, and routers. Each has functionality that mimics its physical counterpart: networks contain subnets, and routers route traffic between different subnet and networks."
msgstr ""
#: ./doc/install-guide/section_neutron-concepts.xml:20(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/install-guide/section_neutron-concepts.xml:28(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/install-guide/section_neutron-concepts.xml:33(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/install-guide/section_neutron-concepts.xml:40(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/install-guide/section_neutron-concepts.xml:45(para)
msgid "Networking also supports <emphasis role=\"italic\">security groups</emphasis>. 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/install-guide/section_neutron-concepts.xml:51(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-balancing-as-a-service (LBaaS) plug-ins are available."
msgstr ""
#: ./doc/install-guide/section_ceilometer-install.xml:10(title)
msgid "Install the Telemetry module"
msgstr ""
#: ./doc/install-guide/section_ceilometer-install.xml:12(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/install-guide/section_ceilometer-install.xml:18(para)
msgid "Install the Telemetry service on the controller node:"
msgstr ""
#: ./doc/install-guide/section_ceilometer-install.xml:30(para)
msgid "Respond to the prompts for <link linkend=\"debconf-keystone_authtoken\"><literal>[keystone_authtoken]</literal> settings</link>, <link linkend=\"debconf-rabbitqm\">RabbitMQ credentials</link> and <link linkend=\"debconf-api-endpoints\">API endpoint</link> registration."
msgstr ""
#: ./doc/install-guide/section_ceilometer-install.xml:38(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/install-guide/section_ceilometer-install.xml:46(para)
msgid "By default MongoDB is configured to create several 1 GB files in the <filename>/var/lib/mongodb/journal/</filename> directory to support database journaling."
msgstr ""
#: ./doc/install-guide/section_ceilometer-install.xml:51(para)
msgid "If you need to minimize the space allocated to support database journaling then set the <option>smallfiles</option> configuration key to <literal>true</literal> in the <filename>/etc/mongodb.conf</filename> configuration file. This configuration reduces the size of each journaling file to 512 MB."
msgstr ""
#: ./doc/install-guide/section_ceilometer-install.xml:59(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/install-guide/section_ceilometer-install.xml:67(para)
msgid "For more information on the <option>smallfiles</option> configuration key refer to the MongoDB documentation at <link href=\"http://docs.mongodb.org/manual/reference/configuration-options/#smallfiles\"/>."
msgstr ""
#: ./doc/install-guide/section_ceilometer-install.xml:72(para)
msgid "For instructions detailing the steps to disable database journaling entirely refer to <link href=\"http://docs.mongodb.org/manual/tutorial/manage-journaling/\"/>."
msgstr ""
#: ./doc/install-guide/section_ceilometer-install.xml:80(para)
msgid "Configure MongoDB to make it listen on the controller management IP address. Edit the <filename>/etc/mongodb.conf</filename> file and modify the <literal>bind_ip</literal> key:"
msgstr ""
#: ./doc/install-guide/section_ceilometer-install.xml:86(para)
msgid "Restart the MongoDB service to apply the configuration change:"
msgstr ""
#: ./doc/install-guide/section_ceilometer-install.xml:90(para)
msgid "Start the MongoDB server and configure it to start when the system boots:"
msgstr ""
#: ./doc/install-guide/section_ceilometer-install.xml:100(para)
msgid "Create the database and a <literal>ceilometer</literal> database user:"
msgstr ""
#: ./doc/install-guide/section_ceilometer-install.xml:105(replaceable) ./doc/install-guide/section_ceilometer-install.xml:111(replaceable) ./doc/install-guide/section_ceilometer-install.xml:118(replaceable)
msgid "CEILOMETER_DBPASS"
msgstr ""
#: ./doc/install-guide/section_ceilometer-install.xml:109(para)
msgid "Configure the Telemetry service to use the database:"
msgstr ""
#: ./doc/install-guide/section_ceilometer-install.xml:112(para)
msgid "Edit the <filename>/etc/ceilometer/ceilometer.conf</filename> file and change the <literal>[database]</literal> section:"
msgstr ""
#: ./doc/install-guide/section_ceilometer-install.xml:122(para)
msgid "You must define a secret key that is used as a shared secret among Telemetry service nodes. Use <placeholder-1/> to generate a random token and store it in the configuration file:"
msgstr ""
#: ./doc/install-guide/section_ceilometer-install.xml:129(para)
msgid "For SUSE Linux Enterprise, run the following command:"
msgstr ""
#: ./doc/install-guide/section_ceilometer-install.xml:133(para)
msgid "Edit the <filename>/etc/ceilometer/ceilometer.conf</filename> file and change the <literal>[publisher]</literal> section. Replace <replaceable>CEILOMETER_TOKEN</replaceable> with the results of the <literal>openssl</literal> command:"
msgstr ""
#: ./doc/install-guide/section_ceilometer-install.xml:140(replaceable) ./doc/install-guide/section_ceilometer-nova.xml:62(replaceable) ./doc/install-guide/section_ceilometer-nova.xml:70(replaceable)
msgid "CEILOMETER_TOKEN"
msgstr ""
#: ./doc/install-guide/section_ceilometer-install.xml:144(para) ./doc/install-guide/section_ceilometer-nova.xml:74(para)
msgid "Configure the RabbitMQ access:"
msgstr ""
#: ./doc/install-guide/section_ceilometer-install.xml:146(replaceable) ./doc/install-guide/section_ceilometer-install.xml:149(replaceable) ./doc/install-guide/section_trove-install.xml:97(replaceable) ./doc/install-guide/section_trove-install.xml:117(replaceable) ./doc/install-guide/section_trove-install.xml:119(replaceable) ./doc/install-guide/section_trove-install.xml:121(replaceable) ./doc/install-guide/section_trove-install.xml:208(replaceable) ./doc/install-guide/section_nova-controller.xml:70(replaceable) ./doc/install-guide/section_nova-controller.xml:78(replaceable) ./doc/install-guide/section_neutron-ovs-compute-node.xml:198(replaceable) ./doc/install-guide/section_neutron-ovs-compute-node.xml:207(replaceable) ./doc/install-guide/section_neutron-ml2-controller-node.xml:167(replaceable) ./doc/install-guide/section_neutron-ml2-controller-node.xml:190(replaceable) ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:182(replaceable) ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:195(replaceable) ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:272(replaceable) ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:327(replaceable) ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:113(replaceable) ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:178(replaceable) ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:189(replaceable) ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:322(replaceable) ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:333(replaceable) ./doc/install-guide/section_neutron-ovs-controller-node.xml:153(replaceable) ./doc/install-guide/section_neutron-ovs-controller-node.xml:180(replaceable) ./doc/install-guide/section_ceilometer-glance.xml:18(replaceable) ./doc/install-guide/section_ceilometer-glance.xml:24(replaceable) ./doc/install-guide/section_neutron-ovs-network-node.xml:149(replaceable) ./doc/install-guide/section_neutron-ovs-network-node.xml:158(replaceable) ./doc/install-guide/section_neutron-single-flat.xml:207(replaceable) ./doc/install-guide/section_neutron-single-flat.xml:230(replaceable) ./doc/install-guide/section_neutron-single-flat.xml:335(replaceable) ./doc/install-guide/section_neutron-single-flat.xml:362(replaceable) ./doc/install-guide/section_neutron-single-flat.xml:427(replaceable) ./doc/install-guide/section_neutron-single-flat.xml:446(replaceable) ./doc/install-guide/section_cinder-node.xml:153(replaceable) ./doc/install-guide/section_cinder-node.xml:174(replaceable) ./doc/install-guide/section_cinder-controller.xml:123(replaceable) ./doc/install-guide/section_cinder-controller.xml:145(replaceable) ./doc/install-guide/section_neutron-ml2-network-node.xml:119(replaceable) ./doc/install-guide/section_neutron-ml2-network-node.xml:142(replaceable) ./doc/install-guide/section_neutron-ml2-compute-node.xml:116(replaceable) ./doc/install-guide/section_neutron-ml2-compute-node.xml:139(replaceable) ./doc/install-guide/section_basics-queue.xml:77(replaceable) ./doc/install-guide/section_heat-install.xml:93(replaceable) ./doc/install-guide/section_heat-install.xml:96(replaceable) ./doc/install-guide/section_ceilometer-nova.xml:76(replaceable) ./doc/install-guide/section_ceilometer-nova.xml:80(replaceable) ./doc/install-guide/section_nova-compute.xml:115(replaceable) ./doc/install-guide/section_nova-compute.xml:121(replaceable) ./doc/install-guide/section_glance-install.xml:90(replaceable) ./doc/install-guide/section_glance-install.xml:104(replaceable)
msgid "RABBIT_PASS"
msgstr ""
#: ./doc/install-guide/section_ceilometer-install.xml:147(para) ./doc/install-guide/section_ceilometer-install.xml:160(para) ./doc/install-guide/section_ceilometer-nova.xml:77(para) ./doc/install-guide/section_ceilometer-nova.xml:130(para)
msgid "Edit the <filename>/etc/ceilometer/ceilometer.conf</filename> file and update the <literal>[DEFAULT]</literal> section:"
msgstr ""
#: ./doc/install-guide/section_ceilometer-install.xml:153(para)
msgid "Configure the collector dispatcher:"
msgstr ""
#: ./doc/install-guide/section_ceilometer-install.xml:159(para) ./doc/install-guide/section_ceilometer-nova.xml:129(para)
msgid "Configure the log directory."
msgstr ""
#: ./doc/install-guide/section_ceilometer-install.xml:167(para)
msgid "Create a <literal>ceilometer</literal> user that the Telemetry service uses to authenticate with the Identity Service. Use the <literal>service</literal> tenant and give the user the <literal>admin</literal> role:"
msgstr ""
#: ./doc/install-guide/section_ceilometer-install.xml:171(replaceable) ./doc/install-guide/section_ceilometer-install.xml:200(replaceable) ./doc/install-guide/section_ceilometer-install.xml:208(replaceable) ./doc/install-guide/section_ceilometer-install.xml:220(replaceable) ./doc/install-guide/section_ceilometer-install.xml:227(replaceable) ./doc/install-guide/section_ceilometer-nova.xml:99(replaceable) ./doc/install-guide/section_ceilometer-nova.xml:105(replaceable) ./doc/install-guide/section_ceilometer-nova.xml:118(replaceable) ./doc/install-guide/section_ceilometer-nova.xml:125(replaceable)
msgid "CEILOMETER_PASS"
msgstr ""
#: ./doc/install-guide/section_ceilometer-install.xml:171(replaceable)
msgid "ceilometer@example.com"
msgstr ""
#: ./doc/install-guide/section_ceilometer-install.xml:175(para)
msgid "Configure the Telemetry service to authenticate with the Identity Service."
msgstr ""
#: ./doc/install-guide/section_ceilometer-install.xml:177(para)
msgid "Set the <option>auth_strategy</option> value to <literal>keystone</literal> in the <filename>/etc/ceilometer/ceilometer.conf</filename> file:"
msgstr ""
#: ./doc/install-guide/section_ceilometer-install.xml:187(para)
msgid "Add the credentials to the configuration files for the Telemetry service:"
msgstr ""
#: ./doc/install-guide/section_ceilometer-install.xml:209(para) ./doc/install-guide/section_ceilometer-nova.xml:108(para)
msgid "Edit the <filename>/etc/ceilometer/ceilometer.conf</filename> file and change the <literal>[keystone_authtoken]</literal> section:"
msgstr ""
#: ./doc/install-guide/section_ceilometer-install.xml:221(para) ./doc/install-guide/section_ceilometer-nova.xml:119(para)
msgid "Also set the <literal>[service_credentials]</literal> section:"
msgstr ""
#: ./doc/install-guide/section_ceilometer-install.xml:230(para)
msgid "Register the Telemetry service with the Identity Service so that other OpenStack services can locate it. Use the <placeholder-1/> command to register the service and specify the endpoint:"
msgstr ""
#: ./doc/install-guide/section_ceilometer-install.xml:243(para)
msgid "Restart the services with their new settings:"
msgstr ""
#: ./doc/install-guide/section_ceilometer-install.xml:252(para)
msgid "Start the <systemitem class=\"service\">openstack-ceilometer-api</systemitem>, <systemitem class=\"service\" os=\"opensuse;sles\">openstack-ceilometer-agent-central</systemitem><systemitem class=\"service\" os=\"rhel;fedora;centos\">openstack-ceilometer-central</systemitem>, <systemitem class=\"service\">openstack-ceilometer-collector</systemitem>, <systemitem class=\"service\" os=\"opensuse;sles\">openstack-ceilometer-alarm-evaluator</systemitem>, and <systemitem class=\"service\" os=\"opensuse;sles\">openstack-ceilometer-alarm-notifier</systemitem> services and configure them to start when the system boots:"
msgstr ""
#: ./doc/install-guide/section_ceilometer-verify.xml:5(title)
msgid "Verify the Telemetry installation"
msgstr ""
#: ./doc/install-guide/section_ceilometer-verify.xml:6(para)
msgid "To test the Telemetry installation, download an image from the Image Service, and use the <placeholder-1/> command to display usage statistics."
msgstr ""
#: ./doc/install-guide/section_ceilometer-verify.xml:11(para)
msgid "Use the <literal>ceilometer meter-list</literal> command to test the access to Telemetry:"
msgstr ""
#: ./doc/install-guide/section_ceilometer-verify.xml:22(para)
msgid "Download an image from the Image Service:"
msgstr ""
#: ./doc/install-guide/section_ceilometer-verify.xml:26(para)
msgid "Call the <literal>ceilometer meter-list</literal> command again to validate that the download has been detected and stored by the Telemetry:"
msgstr ""
#: ./doc/install-guide/section_ceilometer-verify.xml:39(para)
msgid "You can now get usage statistics for the various meters:"
msgstr ""
#: ./doc/install-guide/section_trove-install.xml:3(title)
msgid "Install the Database service"
msgstr ""
#: ./doc/install-guide/section_trove-install.xml:4(para)
msgid "This procedure installs the Database module on the controller node."
msgstr ""
#: ./doc/install-guide/section_trove-install.xml:7(title) ./doc/install-guide/section_neutron-ovs-compute-node.xml:28(title) ./doc/install-guide/section_neutron-ml2-controller-node.xml:8(title) ./doc/install-guide/section_neutron-ovs-controller-node.xml:24(title) ./doc/install-guide/section_neutron-ml2-network-node.xml:8(title) ./doc/install-guide/section_neutron-ml2-compute-node.xml:8(title)
msgid "Prerequisites"
msgstr ""
#: ./doc/install-guide/section_trove-install.xml:8(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/install-guide/section_trove-install.xml:13(title)
msgid "Ubuntu 14.04 Only"
msgstr ""
#: ./doc/install-guide/section_trove-install.xml:14(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/install-guide/section_trove-install.xml:18(para)
msgid "To install the Database module on the controller:"
msgstr ""
#: ./doc/install-guide/section_trove-install.xml:21(para)
msgid "Install required packages:"
msgstr ""
#: ./doc/install-guide/section_trove-install.xml:29(para)
msgid "Prepare OpenStack:"
msgstr ""
#: ./doc/install-guide/section_trove-install.xml:32(para)
msgid "Source the <filename>admin-openrc.sh</filename> file."
msgstr ""
#: ./doc/install-guide/section_trove-install.xml:37(para)
msgid "Create a <literal>trove</literal> user that Compute uses to authenticate with the Identity service. Use the <literal>service</literal> tenant and give the user the <literal>admin</literal> role:"
msgstr ""
#: ./doc/install-guide/section_trove-install.xml:42(replaceable)
msgid "TROVE_PASS"
msgstr ""
#: ./doc/install-guide/section_trove-install.xml:43(replaceable)
msgid "trove@example.com"
msgstr ""
#: ./doc/install-guide/section_trove-install.xml:51(para)
msgid "Edit the following configuration files, taking the below actions for each file:"
msgstr ""
#: ./doc/install-guide/section_trove-install.xml:54(filename)
msgid "trove.conf"
msgstr ""
#: ./doc/install-guide/section_trove-install.xml:55(filename)
msgid "trove-taskmanager.conf"
msgstr ""
#: ./doc/install-guide/section_trove-install.xml:56(filename)
msgid "trove-conductor.conf"
msgstr ""
#: ./doc/install-guide/section_trove-install.xml:60(para)
msgid "Edit the <literal>[DEFAULT]</literal> section of each file and set appropriate values for the OpenStack service URLs, logging and messaging configuration, and SQL connections:"
msgstr ""
#: ./doc/install-guide/section_trove-install.xml:70(literal)
msgid "TROVE_DBPASS"
msgstr ""
#: ./doc/install-guide/section_trove-install.xml:75(para)
msgid "Set these configuration keys to configure the Database module to use the Qpid message broker:"
msgstr ""
#: ./doc/install-guide/section_trove-install.xml:92(para)
msgid "Configure the Database module to use the RabbitMQ message broker by setting the rabbit_password in the <literal>[DEFAULT]</literal> configuration group of each file:"
msgstr ""
#: ./doc/install-guide/section_trove-install.xml:102(para)
msgid "Set these configuration keys to configure the Database module to use the RabbitMQ message broker:"
msgstr ""
#: ./doc/install-guide/section_trove-install.xml:127(para)
msgid "Edit the <literal>[filter:authtoken]</literal> section of the <filename>api-paste.ini</filename> file so it matches the listing shown below:"
msgstr ""
#: ./doc/install-guide/section_trove-install.xml:141(para)
msgid "Edit the <filename>trove.conf</filename> file so it includes appropriate values for the default datastore and network label regex as shown below:"
msgstr ""
#: ./doc/install-guide/section_trove-install.xml:154(para)
msgid "Edit the <filename>trove-taskmanager.conf</filename> file so it includes the appropriate service credentials required to connect to the OpenStack Compute service as shown below:"
msgstr ""
#: ./doc/install-guide/section_trove-install.xml:170(para)
msgid "Prepare the trove admin database:"
msgstr ""
#: ./doc/install-guide/section_trove-install.xml:178(para)
msgid "Prepare the Database service:"
msgstr ""
#: ./doc/install-guide/section_trove-install.xml:181(para)
msgid "Initialize the database:"
msgstr ""
#: ./doc/install-guide/section_trove-install.xml:185(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/install-guide/section_trove-install.xml:194(para)
msgid "Create a trove image."
msgstr ""
#: ./doc/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/install-guide/section_trove-install.xml:197(para)
msgid "This image must have the trove guest agent installed, and it must have the <filename>trove-guestagent.conf</filename> file configured to connect to your OpenStack environment. To correctly configure the <filename>trove-guestagent.conf</filename> file, follow these steps on the guest instance you are using to build your image:"
msgstr ""
#: ./doc/install-guide/section_trove-install.xml:206(para)
msgid "Add the following lines to <filename>trove-guestagent.conf</filename>:"
msgstr ""
#: ./doc/install-guide/section_trove-install.xml:218(para)
msgid "Update the datastore to use the new image, using the <placeholder-1/> command."
msgstr ""
#: ./doc/install-guide/section_trove-install.xml:220(para)
msgid "This example shows you how to create a MySQL 5.5 datastore:"
msgstr ""
#: ./doc/install-guide/section_trove-install.xml:222(replaceable)
msgid "glance_image_ID"
msgstr ""
#: ./doc/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/install-guide/section_trove-install.xml:239(para)
msgid "Start Database services and configure them to start when the system boots:"
msgstr ""
#: ./doc/install-guide/section_trove-install.xml:242(para)
msgid "Restart Database services:"
msgstr ""
#: ./doc/install-guide/section_nova-networking-compute-node.xml:5(title) ./doc/install-guide/section_neutron-ovs-compute-node.xml:6(title) ./doc/install-guide/section_neutron-ml2-compute-node.xml:6(title)
msgid "Configure compute node"
msgstr ""
#: ./doc/install-guide/section_nova-networking-compute-node.xml:6(para)
msgid "This section covers deployment of a simple <glossterm>flat network</glossterm> that provides IP addresses to your instances via <glossterm>DHCP</glossterm>. If your environment includes multiple compute nodes, the <glossterm>multi-host</glossterm> feature provides redundancy by spreading network functions across compute nodes."
msgstr ""
#: ./doc/install-guide/section_nova-networking-compute-node.xml:13(title)
msgid "To install legacy networking components"
msgstr ""
#: ./doc/install-guide/section_nova-networking-compute-node.xml:21(title) ./doc/install-guide/section_nova-networking-controller-node.xml:9(title)
msgid "To configure legacy networking"
msgstr ""
#: ./doc/install-guide/section_nova-networking-compute-node.xml:23(para) ./doc/install-guide/section_neutron-ml2-controller-node.xml:299(para) ./doc/install-guide/section_neutron-ml2-controller-node.xml:343(para) ./doc/install-guide/section_ceilometer-glance.xml:20(para) ./doc/install-guide/section_nova-networking-controller-node.xml:11(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:192(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:226(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:262(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:355(para) ./doc/install-guide/section_neutron-ml2-compute-node.xml:189(para) ./doc/install-guide/section_neutron-ml2-compute-node.xml:287(para) ./doc/install-guide/section_heat-install.xml:94(para)
msgid "Run the following commands:"
msgstr ""
#: ./doc/install-guide/section_nova-networking-compute-node.xml:24(para) ./doc/install-guide/section_nova-networking-compute-node.xml:57(para)
msgid "Replace <replaceable>INTERFACE_NAME</replaceable> with the actual interface name for the external network. For example, <emphasis>eth1</emphasis> or <emphasis>ens224</emphasis>."
msgstr ""
#: ./doc/install-guide/section_nova-networking-compute-node.xml:50(replaceable) ./doc/install-guide/section_nova-networking-compute-node.xml:52(replaceable) ./doc/install-guide/section_nova-networking-compute-node.xml:73(replaceable) ./doc/install-guide/section_nova-networking-compute-node.xml:74(replaceable) ./doc/install-guide/section_basics-networking-nova.xml:99(replaceable) ./doc/install-guide/section_basics-networking-nova.xml:100(replaceable) ./doc/install-guide/section_basics-networking-nova.xml:110(replaceable) ./doc/install-guide/section_basics-networking-neutron.xml:108(replaceable) ./doc/install-guide/section_basics-networking-neutron.xml:109(replaceable) ./doc/install-guide/section_basics-networking-neutron.xml:119(replaceable) ./doc/install-guide/section_neutron-ml2-network-node.xml:461(replaceable) ./doc/install-guide/section_neutron-ml2-network-node.xml:469(replaceable)
msgid "INTERFACE_NAME"
msgstr ""
#: ./doc/install-guide/section_nova-networking-compute-node.xml:55(para) ./doc/install-guide/section_nova-networking-controller-node.xml:18(para)
msgid "Edit the <filename>/etc/nova/nova.conf</filename> file and add the following keys to the <literal>[DEFAULT]</literal> section:"
msgstr ""
#: ./doc/install-guide/section_nova-networking-compute-node.xml:77(para)
msgid "Restart the services:"
msgstr ""
#: ./doc/install-guide/section_nova-networking-compute-node.xml:80(para)
msgid "Start the services and configure them to start when the system boots:"
msgstr ""
#: ./doc/install-guide/section_trove-verify.xml:5(title)
msgid "Verify the Database service installation"
msgstr ""
#: ./doc/install-guide/section_trove-verify.xml:6(para)
msgid "To verify that the Database service is installed and configured correctly, try executing a Trove command:"
msgstr ""
#: ./doc/install-guide/section_trove-verify.xml:10(para)
msgid "Source the <filename>demo-openrc.sh</filename> file."
msgstr ""
#: ./doc/install-guide/section_trove-verify.xml:14(para)
msgid "Retrieve the Trove instances list:"
msgstr ""
#: ./doc/install-guide/section_trove-verify.xml:16(para)
msgid "You should see output similar to this:"
msgstr ""
#: ./doc/install-guide/section_trove-verify.xml:23(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 <placeholder-1/> command."
msgstr ""
#: ./doc/install-guide/section_trove-verify.xml:30(para)
msgid "This example shows you how to create a MySQL 5.5 database:"
msgstr ""
#: ./doc/install-guide/section_trove-verify.xml:32(replaceable)
msgid "name"
msgstr ""
#: ./doc/install-guide/section_trove-verify.xml:32(replaceable)
msgid "DBNAME"
msgstr ""
#: ./doc/install-guide/section_trove-verify.xml:33(replaceable)
msgid "USER"
msgstr ""
#: ./doc/install-guide/section_trove-verify.xml:33(replaceable)
msgid "PASSWORD"
msgstr ""
#: ./doc/install-guide/section_nova-controller.xml:5(title)
msgid "Install Compute controller services"
msgstr ""
#: ./doc/install-guide/section_nova-controller.xml:6(para)
msgid "Compute is a collection of services that enable you to launch virtual machine instances. You can configure these services to run on separate nodes or the same node. In this guide, most services run on the controller node and the service that launches virtual machines runs on a dedicated compute node. This section shows you how to install and configure these services on the controller node."
msgstr ""
#: ./doc/install-guide/section_nova-controller.xml:15(para)
msgid "Install the Compute packages necessary for the controller node."
msgstr ""
#: ./doc/install-guide/section_nova-controller.xml:27(para)
msgid "Respond to the prompts for <link linkend=\"debconf-dbconfig-common\">database management</link>, <link linkend=\"debconf-keystone_authtoken\"><literal>[keystone_authtoken]</literal> settings</link>, <link linkend=\"debconf-rabbitqm\">RabbitMQ credentials</link>, and <link linkend=\"debconf-api-endpoints\">API endpoint</link> registration. The <placeholder-1/> command runs automatically."
msgstr ""
#: ./doc/install-guide/section_nova-controller.xml:38(para)
msgid "Compute stores information in a database. In this guide, we use a MySQL database on the controller node. Configure Compute with the database location and credentials. Replace <replaceable>NOVA_DBPASS</replaceable> with the password for the database that you will create in a later step."
msgstr ""
#: ./doc/install-guide/section_nova-controller.xml:44(replaceable) ./doc/install-guide/section_nova-controller.xml:51(replaceable) ./doc/install-guide/section_nova-controller.xml:119(replaceable) ./doc/install-guide/section_nova-controller.xml:121(replaceable) ./doc/install-guide/section_nova-compute.xml:72(replaceable)
msgid "NOVA_DBPASS"
msgstr ""
#: ./doc/install-guide/section_nova-controller.xml:45(para)
msgid "Edit the <literal>[database]</literal> section in the <filename>/etc/nova/nova.conf</filename> file, adding it if necessary, to modify this key:"
msgstr ""
#: ./doc/install-guide/section_nova-controller.xml:55(para)
msgid "Set these configuration keys to configure Compute to use the Qpid message broker:"
msgstr ""
#: ./doc/install-guide/section_nova-controller.xml:62(para) ./doc/install-guide/section_nova-compute.xml:107(para)
msgid "Configure the Compute service to use the RabbitMQ message broker by setting these configuration keys in the <literal>[DEFAULT]</literal> configuration group of the <filename>/etc/nova/nova.conf</filename> file:"
msgstr ""
#: ./doc/install-guide/section_nova-controller.xml:73(para)
msgid "Set these configuration keys to configure Compute to use the RabbitMQ message broker:"
msgstr ""
#: ./doc/install-guide/section_nova-controller.xml:81(para)
msgid "Set the <option>my_ip</option>, <option>vncserver_listen</option>, and <option>vncserver_proxyclient_address</option> configuration options to the management interface IP address of the controller node:"
msgstr ""
#: ./doc/install-guide/section_nova-controller.xml:89(para)
msgid "Edit the <filename>/etc/nova/nova.conf</filename> file and add these lines to the <literal>[DEFAULT]</literal> section:"
msgstr ""
#: ./doc/install-guide/section_nova-controller.xml:92(para)
msgid "In Debian, the <package>debconf</package> package automatically sets up <literal>my_ip</literal> parameter but you must edit the <filename>/etc/nova/nova.conf</filename> file to configure the <option>vncserver_listen</option> and <option>vncserver_proxyclient_address</option> options, which appear at the end of the file:"
msgstr ""
#: ./doc/install-guide/section_nova-controller.xml:107(para)
msgid "By default, the Ubuntu packages create an SQLite database. Delete the <filename>nova.sqlite</filename> file created in the <filename>/var/lib/nova/</filename> directory so that it does not get used by mistake:"
msgstr ""
#: ./doc/install-guide/section_nova-controller.xml:114(para)
msgid "Use the password you created previously to log in as root. Create a <literal>nova</literal> database user:"
msgstr ""
#: ./doc/install-guide/section_nova-controller.xml:124(para)
msgid "Create the Compute service tables:"
msgstr ""
#: ./doc/install-guide/section_nova-controller.xml:128(para)
msgid "Create a <literal>nova</literal> user that Compute uses to authenticate with the Identity Service. Use the <literal>service</literal> tenant and give the user the <literal>admin</literal> role:"
msgstr ""
#: ./doc/install-guide/section_nova-controller.xml:132(replaceable) ./doc/install-guide/section_nova-controller.xml:146(replaceable) ./doc/install-guide/section_nova-controller.xml:166(replaceable) ./doc/install-guide/section_neutron-ml2-controller-node.xml:208(replaceable) ./doc/install-guide/section_neutron-ml2-controller-node.xml:232(replaceable) ./doc/install-guide/section_nova-compute.xml:80(replaceable) ./doc/install-guide/section_nova-compute.xml:99(replaceable)
msgid "NOVA_PASS"
msgstr ""
#: ./doc/install-guide/section_nova-controller.xml:132(replaceable)
msgid "nova@example.com"
msgstr ""
#: ./doc/install-guide/section_nova-controller.xml:136(para)
msgid "Configure Compute to use these credentials with the Identity Service running on the controller. Replace <replaceable>NOVA_PASS</replaceable> with your Compute password."
msgstr ""
#: ./doc/install-guide/section_nova-controller.xml:147(para)
msgid "Edit the <literal>[DEFAULT]</literal> section in the <filename>/etc/nova/nova.conf</filename> file to add this key:"
msgstr ""
#: ./doc/install-guide/section_nova-controller.xml:155(para)
msgid "Add these keys to the <literal>[keystone_authtoken]</literal> section:"
msgstr ""
#: ./doc/install-guide/section_nova-controller.xml:169(para)
msgid "You must register Compute with the Identity Service so that other OpenStack services can locate it. Register the service and specify the endpoint:"
msgstr ""
#: ./doc/install-guide/section_nova-controller.xml:182(para)
msgid "Start Compute services and configure them to start when the system boots:"
msgstr ""
#: ./doc/install-guide/section_nova-controller.xml:185(para)
msgid "Restart Compute services:"
msgstr ""
#: ./doc/install-guide/section_nova-controller.xml:206(para)
msgid "To verify your configuration, list available images:"
msgstr ""
#: ./doc/install-guide/section_neutron-ovs-compute-node.xml:8(para)
msgid "This section details set up for any node that runs the <literal>nova-compute</literal> component but does not run the full network stack."
msgstr ""
#: ./doc/install-guide/section_neutron-ovs-compute-node.xml:13(para)
msgid "By default, the <literal>system-config-firewall</literal> automated firewall configuration tool is in place on RHEL. This graphical interface (and a curses-style interface with <literal>-tui</literal> 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 <guilabel>Enabled</guilabel> check box."
msgstr ""
#: ./doc/install-guide/section_neutron-ovs-compute-node.xml:22(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/install-guide/section_neutron-ovs-compute-node.xml:30(para)
msgid "Disable packet destination filtering (route verification) to let the networking services route traffic to the VMs. Edit the <filename>/etc/sysctl.conf</filename> file and run the following command to activate changes:"
msgstr ""
#: ./doc/install-guide/section_neutron-ovs-compute-node.xml:41(title)
msgid "Install Open vSwitch plug-in"
msgstr ""
#: ./doc/install-guide/section_neutron-ovs-compute-node.xml:42(para) ./doc/install-guide/section_neutron-ovs-controller-node.xml:185(para) ./doc/install-guide/section_neutron-ovs-network-node.xml:176(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/install-guide/section_neutron-ovs-compute-node.xml:47(para) ./doc/install-guide/section_neutron-ovs-network-node.xml:181(para)
msgid "Install the Open vSwitch plug-in and its dependencies:"
msgstr ""
#: ./doc/install-guide/section_neutron-ovs-compute-node.xml:54(para)
msgid "Restart Open vSwitch:"
msgstr ""
#: ./doc/install-guide/section_neutron-ovs-compute-node.xml:58(para)
msgid "Start Open vSwitch and configure it to start when the system boots:"
msgstr ""
#: ./doc/install-guide/section_neutron-ovs-compute-node.xml:66(para)
msgid "You must set some common configuration options no matter which networking technology you choose to use with Open vSwitch. You must add the <literal>br-int</literal> integration bridge, which connects to the VMs."
msgstr ""
#: ./doc/install-guide/section_neutron-ovs-compute-node.xml:74(para)
msgid "You must set some common configuration options. You must configure Networking core to use <acronym>OVS</acronym>. Edit the <filename>/etc/neutron/neutron.conf</filename> file:"
msgstr ""
#: ./doc/install-guide/section_neutron-ovs-compute-node.xml:83(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 <filename>/etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini</filename> file and set the <literal>firewall_driver</literal> value under the <literal>securitygroup</literal> 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/install-guide/section_neutron-ovs-compute-node.xml:96(para) ./doc/install-guide/section_neutron-ovs-network-node.xml:313(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/install-guide/section_neutron-ovs-compute-node.xml:102(para) ./doc/install-guide/section_neutron-ovs-network-node.xml:319(para)
msgid "Configure the <acronym>OVS</acronym> plug-in to start on boot."
msgstr ""
#: ./doc/install-guide/section_neutron-ovs-compute-node.xml:108(para)
msgid "Tell the <acronym>OVS</acronym> plug-in to use GRE tunneling with a <literal>br-int</literal> integration bridge, a <literal>br-tun</literal> tunneling bridge, and a local IP for the tunnel of <replaceable>DATA_INTERFACE</replaceable>'s IP Edit the <filename>/etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini</filename> file:"
msgstr ""
#: ./doc/install-guide/section_neutron-ovs-compute-node.xml:123(replaceable)
msgid "DATA_INTERFACE_IP"
msgstr ""
#: ./doc/install-guide/section_neutron-ovs-compute-node.xml:127(title)
msgid "Configure common components"
msgstr ""
#: ./doc/install-guide/section_neutron-ovs-compute-node.xml:129(para) ./doc/install-guide/section_neutron-ovs-network-node.xml:82(para)
msgid "Configure Networking to use <systemitem class=\"service\">keystone</systemitem> for authentication:"
msgstr ""
#: ./doc/install-guide/section_neutron-ovs-compute-node.xml:132(para) ./doc/install-guide/section_neutron-ovs-compute-node.xml:166(para)
msgid "Set the <literal>auth_strategy</literal> configuration key to <literal>keystone</literal> in the <literal>[DEFAULT]</literal> section of the file:"
msgstr ""
#: ./doc/install-guide/section_neutron-ovs-compute-node.xml:138(para) ./doc/install-guide/section_neutron-ovs-controller-node.xml:95(para) ./doc/install-guide/section_neutron-ovs-network-node.xml:91(para)
msgid "Set the <systemitem class=\"service\">neutron</systemitem> configuration for <systemitem class=\"service\">keystone</systemitem> authentication:"
msgstr ""
#: ./doc/install-guide/section_neutron-ovs-compute-node.xml:155(replaceable) ./doc/install-guide/section_neutron-ovs-compute-node.xml:185(replaceable) ./doc/install-guide/section_neutron-ovs-compute-node.xml:240(replaceable) ./doc/install-guide/section_neutron-ovs-compute-node.xml:257(replaceable) ./doc/install-guide/section_neutron-ml2-controller-node.xml:33(replaceable) ./doc/install-guide/section_neutron-ml2-controller-node.xml:125(replaceable) ./doc/install-guide/section_neutron-ml2-controller-node.xml:151(replaceable) ./doc/install-guide/section_neutron-ml2-controller-node.xml:358(replaceable) ./doc/install-guide/section_neutron-ml2-controller-node.xml:388(replaceable) ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:191(replaceable) ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:236(replaceable) ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:132(replaceable) ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:225(replaceable) ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:237(replaceable) ./doc/install-guide/section_neutron-ovs-controller-node.xml:46(replaceable) ./doc/install-guide/section_neutron-ovs-controller-node.xml:110(replaceable) ./doc/install-guide/section_neutron-ovs-controller-node.xml:139(replaceable) ./doc/install-guide/section_neutron-ovs-controller-node.xml:237(replaceable) ./doc/install-guide/section_neutron-ovs-controller-node.xml:254(replaceable) ./doc/install-guide/section_neutron-ovs-network-node.xml:109(replaceable) ./doc/install-guide/section_neutron-ovs-network-node.xml:136(replaceable) ./doc/install-guide/section_neutron-ovs-network-node.xml:393(replaceable) ./doc/install-guide/section_neutron-ovs-network-node.xml:407(replaceable) ./doc/install-guide/section_neutron-single-flat.xml:190(replaceable) ./doc/install-guide/section_neutron-single-flat.xml:239(replaceable) ./doc/install-guide/section_neutron-single-flat.xml:283(replaceable) ./doc/install-guide/section_neutron-single-flat.xml:299(replaceable) ./doc/install-guide/section_neutron-ml2-network-node.xml:77(replaceable) ./doc/install-guide/section_neutron-ml2-network-node.xml:103(replaceable) ./doc/install-guide/section_neutron-ml2-network-node.xml:277(replaceable) ./doc/install-guide/section_neutron-ml2-network-node.xml:304(replaceable) ./doc/install-guide/section_neutron-ml2-compute-node.xml:74(replaceable) ./doc/install-guide/section_neutron-ml2-compute-node.xml:100(replaceable) ./doc/install-guide/section_neutron-ml2-compute-node.xml:302(replaceable) ./doc/install-guide/section_neutron-ml2-compute-node.xml:332(replaceable)
msgid "NEUTRON_PASS"
msgstr ""
#: ./doc/install-guide/section_neutron-ovs-compute-node.xml:160(para) ./doc/install-guide/section_neutron-ovs-network-node.xml:113(para)
msgid "To configure <systemitem class=\"service\">neutron</systemitem> to use <systemitem class=\"service\">keystone</systemitem> for authentication, edit the <filename>/etc/neutron/neutron.conf</filename> file."
msgstr ""
#: ./doc/install-guide/section_neutron-ovs-compute-node.xml:174(para) ./doc/install-guide/section_neutron-ovs-network-node.xml:125(para)
msgid "Add these lines to the <literal>[keystone_authtoken]</literal> section of the file:"
msgstr ""
#: ./doc/install-guide/section_neutron-ovs-compute-node.xml:190(para) ./doc/install-guide/section_neutron-ovs-controller-node.xml:144(para) ./doc/install-guide/section_neutron-ovs-network-node.xml:141(para) ./doc/install-guide/section_neutron-single-flat.xml:199(para) ./doc/install-guide/section_neutron-single-flat.xml:354(para) ./doc/install-guide/section_neutron-single-flat.xml:438(para)
msgid "Configure access to the <application>RabbitMQ</application> service:"
msgstr ""
#: ./doc/install-guide/section_neutron-ovs-compute-node.xml:201(para)
msgid "Configure the <application>RabbitMQ</application> access. Edit the <filename>/etc/neutron/neutron.conf</filename> file to modify the following parameters in the <literal>[DEFAULT]</literal> section."
msgstr ""
#: ./doc/install-guide/section_neutron-ovs-compute-node.xml:210(para) ./doc/install-guide/section_neutron-ovs-controller-node.xml:156(para) ./doc/install-guide/section_neutron-ovs-network-node.xml:161(para) ./doc/install-guide/section_neutron-single-flat.xml:208(para) ./doc/install-guide/section_neutron-single-flat.xml:363(para) ./doc/install-guide/section_neutron-single-flat.xml:447(para)
msgid "Configure access to the <application>Qpid</application> message queue:"
msgstr ""
#: ./doc/install-guide/section_neutron-ovs-compute-node.xml:218(replaceable) ./doc/install-guide/section_neutron-ovs-compute-node.xml:220(replaceable) ./doc/install-guide/section_neutron-ovs-controller-node.xml:165(replaceable) ./doc/install-guide/section_neutron-ovs-controller-node.xml:167(replaceable) ./doc/install-guide/section_neutron-ovs-network-node.xml:169(replaceable) ./doc/install-guide/section_neutron-ovs-network-node.xml:171(replaceable) ./doc/install-guide/section_neutron-single-flat.xml:216(replaceable) ./doc/install-guide/section_neutron-single-flat.xml:218(replaceable) ./doc/install-guide/section_neutron-single-flat.xml:371(replaceable) ./doc/install-guide/section_neutron-single-flat.xml:373(replaceable) ./doc/install-guide/section_neutron-single-flat.xml:455(replaceable) ./doc/install-guide/section_neutron-single-flat.xml:457(replaceable)
msgid "guest"
msgstr ""
#: ./doc/install-guide/section_neutron-ovs-compute-node.xml:224(title) ./doc/install-guide/section_neutron-ovs-controller-node.xml:220(title)
msgid "Configure Compute services for Networking"
msgstr ""
#: ./doc/install-guide/section_neutron-ovs-compute-node.xml:226(para)
msgid "Configure OpenStack Compute to use OpenStack Networking services. Configure the <filename>/etc/nova/nova.conf</filename> file as per instructions below:"
msgstr ""
#: ./doc/install-guide/section_neutron-ovs-compute-node.xml:249(para)
msgid "Configure OpenStack Compute to use OpenStack Networking services. Edit the <filename>/etc/nova/nova.conf</filename> file:"
msgstr ""
#: ./doc/install-guide/section_neutron-ovs-compute-node.xml:265(para)
msgid "No matter which firewall driver you chose when you configured the network and compute nodes, you must edit the <filename>/etc/nova/nova.conf</filename> file to set the firewall driver to <literal>nova.virt.firewall.NoopFirewallDriver</literal>. Because OpenStack Networking handles the firewall, this statement instructs Compute to not use a firewall."
msgstr ""
#: ./doc/install-guide/section_neutron-ovs-compute-node.xml:275(para)
msgid "If you want Networking to handle the firewall, edit the <filename>/etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini</filename> file to set the <code>firewall_driver</code> option to the firewall for the plug-in. For example, with <acronym>OVS</acronym>, edit the file as follows:"
msgstr ""
#: ./doc/install-guide/section_neutron-ovs-compute-node.xml:290(para)
msgid "If you do not want to use a firewall in Compute or Networking, edit both configuration files and set <code>firewall_driver=nova.virt.firewall.NoopFirewallDriver</code>. Also, edit the <filename>/etc/nova/nova.conf</filename> file and comment out or remove the <code>security_group_api=neutron</code> statement."
msgstr ""
#: ./doc/install-guide/section_neutron-ovs-compute-node.xml:298(para)
msgid "Otherwise, when you issue <placeholder-1/> commands, the <errortext>ERROR: The server has either erred or is incapable of performing the requested operation. (HTTP 500)</errortext> error might be returned."
msgstr ""
#: ./doc/install-guide/section_neutron-ovs-compute-node.xml:309(title) ./doc/install-guide/section_neutron-ovs-controller-node.xml:322(title) ./doc/install-guide/section_neutron-ovs-network-node.xml:432(title)
msgid "Finalize installation"
msgstr ""
#: ./doc/install-guide/section_neutron-ovs-compute-node.xml:311(para) ./doc/install-guide/section_neutron-ovs-controller-node.xml:298(para) ./doc/install-guide/section_neutron-ovs-network-node.xml:434(para)
msgid "The <systemitem class=\"service\">neutron-server</systemitem> initialization script expects a symbolic link <filename>/etc/neutron/plugin.ini</filename> pointing to the configuration file associated with your chosen plug-in. Using Open vSwitch, for example, the symbolic link must point to <filename>/etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini</filename>. If this symbolic link does not exist, create it using the following commands:"
msgstr ""
#: ./doc/install-guide/section_neutron-ovs-compute-node.xml:323(para) ./doc/install-guide/section_neutron-ovs-controller-node.xml:310(para) ./doc/install-guide/section_neutron-ovs-network-node.xml:446(para)
msgid "The <systemitem class=\"service\">openstack-neutron</systemitem> initialization script expects the variable <literal>NEUTRON_PLUGIN_CONF</literal> in file <filename>/etc/sysconfig/neutron</filename> to reference the configuration file associated with your chosen plug-in. Using Open vSwitch, for example, edit the <filename>/etc/sysconfig/neutron</filename> file and add the following:"
msgstr ""
#: ./doc/install-guide/section_neutron-ovs-compute-node.xml:334(para) ./doc/install-guide/section_neutron-ovs-network-node.xml:457(para)
msgid "Restart Networking services."
msgstr ""
#: ./doc/install-guide/section_neutron-ovs-compute-node.xml:340(para)
msgid "Restart the Compute service."
msgstr ""
#: ./doc/install-guide/section_dashboard-system-reqs.xml:6(title)
msgid "System requirements"
msgstr ""
#: ./doc/install-guide/section_dashboard-system-reqs.xml:7(para)
msgid "Before you install the OpenStack dashboard, you must meet the following system requirements:"
msgstr ""
#: ./doc/install-guide/section_dashboard-system-reqs.xml:11(para)
msgid "OpenStack Compute installation. Enable the Identity Service for user and project management."
msgstr ""
#: ./doc/install-guide/section_dashboard-system-reqs.xml:13(para)
msgid "Note the URLs of the Identity Service and Compute endpoints."
msgstr ""
#: ./doc/install-guide/section_dashboard-system-reqs.xml:17(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/install-guide/section_dashboard-system-reqs.xml:23(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/install-guide/section_dashboard-system-reqs.xml:29(para)
msgid "Then, install and configure the dashboard on a node that can contact the Identity Service."
msgstr ""
#: ./doc/install-guide/section_dashboard-system-reqs.xml:31(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/install-guide/section_dashboard-system-reqs.xml:36(para)
msgid "The public IP address from which they can access the dashboard"
msgstr ""
#: ./doc/install-guide/section_dashboard-system-reqs.xml:40(para)
msgid "The user name and password with which they can access the dashboard"
msgstr ""
#: ./doc/install-guide/section_dashboard-system-reqs.xml:44(para)
msgid "Your web browser, and that of your users, must support HTML5 and have cookies and JavaScript enabled."
msgstr ""
#: ./doc/install-guide/section_dashboard-system-reqs.xml:48(para)
msgid "To use the VNC client with the dashboard, the browser must support HTML5 Canvas and HTML5 WebSockets."
msgstr ""
#: ./doc/install-guide/section_dashboard-system-reqs.xml:50(para)
msgid "For details about browsers that support noVNC, see <link href=\"https://github.com/kanaka/noVNC/blob/master/README.md\">https://github.com/kanaka/noVNC/blob/master/README.md</link>, and <link href=\"https://github.com/kanaka/noVNC/wiki/Browser-support\">https://github.com/kanaka/noVNC/wiki/Browser-support</link>, respectively."
msgstr ""
#: ./doc/install-guide/section_launch-instance-neutron.xml:6(title)
msgid "Launch an instance with OpenStack Networking (neutron)"
msgstr ""
#: ./doc/install-guide/section_launch-instance-neutron.xml:95(para)
msgid "Your first instance uses the <literal>default</literal> 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 <link linkend=\"launch-instance-neutron-remoteaccess\"> configure remote access</link>."
msgstr ""
#: ./doc/install-guide/section_launch-instance-neutron.xml:173(para)
msgid "Verify the <literal>demo-net</literal> tenant network gateway:"
msgstr ""
#: ./doc/install-guide/section_launch-instance-neutron.xml:185(para)
msgid "Verify the <literal>ext-net</literal> external network:"
msgstr ""
#: ./doc/install-guide/section_launch-instance-neutron.xml:224(para)
msgid "Create a <glossterm>floating IP address</glossterm> on the <literal>ext-net</literal> external network:"
msgstr ""
#: ./doc/install-guide/section_launch-instance-neutron.xml:242(para)
msgid "Associate the floating IP address with your instance:"
msgstr ""
#: ./doc/install-guide/section_launch-instance-neutron.xml:249(para)
msgid "Check the status of your floating IP address:"
msgstr ""
#: ./doc/install-guide/ch_launch-instance.xml:5(title)
msgid "Launch an instance"
msgstr ""
#: ./doc/install-guide/ch_launch-instance.xml:6(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 <glossterm>CirrOS</glossterm> image that you added to your environment in the <xref linkend=\"ch_glance\"/> 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 <link href=\"http://docs.openstack.org/user-guide/content/ch_dashboard.html\"><citetitle>OpenStack User Guide</citetitle></link>."
msgstr ""
#: ./doc/install-guide/ch_launch-instance.xml:15(para)
msgid "Launch an instance using <link linkend=\"launch-instance-neutron\">OpenStack Networking (neutron) </link> or <link linkend=\"launch-instance-nova\">legacy networking (nova-network) </link>. For more information, see the <link href=\"http://docs.openstack.org/user-guide/content/cli_launch_instances.html\"><citetitle>OpenStack User Guide</citetitle></link>."
msgstr ""
#: ./doc/install-guide/ch_launch-instance.xml:25(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/install-guide/section_neutron-ml2-controller-node.xml:6(title) ./doc/install-guide/section_neutron-ovs-controller-node.xml:6(title) ./doc/install-guide/section_nova-networking-controller-node.xml:5(title)
msgid "Configure controller node"
msgstr ""
#: ./doc/install-guide/section_neutron-ml2-controller-node.xml:9(para)
msgid "Before you configure OpenStack Networking (neutron), you must create a database and Identity service credentials including a user and service."
msgstr ""
#: ./doc/install-guide/section_neutron-ml2-controller-node.xml:13(para)
msgid "Connect to the database as the root user, create the <literal>neutron</literal> database, and grant the proper access to it:"
msgstr ""
#: ./doc/install-guide/section_neutron-ml2-controller-node.xml:16(para) ./doc/install-guide/section_neutron-ml2-controller-node.xml:84(para)
msgid "Replace <replaceable>NEUTRON_DBPASS</replaceable> with a suitable password."
msgstr ""
#: ./doc/install-guide/section_neutron-ml2-controller-node.xml:21(replaceable) ./doc/install-guide/section_neutron-ml2-controller-node.xml:23(replaceable) ./doc/install-guide/section_neutron-ml2-controller-node.xml:87(replaceable) ./doc/install-guide/section_neutron-ml2-controller-node.xml:100(replaceable) ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:186(replaceable) ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:199(replaceable) ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:276(replaceable) ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:116(replaceable) ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:181(replaceable) ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:185(replaceable) ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:191(replaceable) ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:325(replaceable) ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:329(replaceable) ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:335(replaceable) ./doc/install-guide/section_neutron-ovs-controller-node.xml:38(replaceable) ./doc/install-guide/section_neutron-ovs-controller-node.xml:40(replaceable) ./doc/install-guide/section_neutron-ovs-controller-node.xml:71(replaceable) ./doc/install-guide/section_neutron-ovs-controller-node.xml:81(replaceable) ./doc/install-guide/section_neutron-single-flat.xml:193(replaceable) ./doc/install-guide/section_neutron-single-flat.xml:234(replaceable) ./doc/install-guide/section_neutron-single-flat.xml:339(replaceable) ./doc/install-guide/section_neutron-single-flat.xml:348(replaceable)
msgid "NEUTRON_DBPASS"
msgstr ""
#: ./doc/install-guide/section_neutron-ml2-controller-node.xml:26(para)
msgid "Create Identity service credentials for Networking:"
msgstr ""
#: ./doc/install-guide/section_neutron-ml2-controller-node.xml:29(para)
msgid "Create the <literal>neutron</literal> user:"
msgstr ""
#: ./doc/install-guide/section_neutron-ml2-controller-node.xml:30(para)
msgid "Replace <replaceable>NEUTRON_PASS</replaceable> with a suitable password and <replaceable>neutron@example.com</replaceable> with a suitable e-mail address."
msgstr ""
#: ./doc/install-guide/section_neutron-ml2-controller-node.xml:33(replaceable) ./doc/install-guide/section_neutron-ovs-controller-node.xml:46(replaceable)
msgid "neutron@example.com"
msgstr ""
#: ./doc/install-guide/section_neutron-ml2-controller-node.xml:36(para)
msgid "Link the <literal>neutron</literal> user to the <literal>service</literal> tenant and <literal>admin</literal> role:"
msgstr ""
#: ./doc/install-guide/section_neutron-ml2-controller-node.xml:42(para)
msgid "Create the <literal>neutron</literal> service:"
msgstr ""
#: ./doc/install-guide/section_neutron-ml2-controller-node.xml:46(para)
msgid "Create the service endpoint:"
msgstr ""
#: ./doc/install-guide/section_neutron-ml2-controller-node.xml:57(title) ./doc/install-guide/section_neutron-ml2-network-node.xml:24(title) ./doc/install-guide/section_neutron-ml2-compute-node.xml:23(title)
msgid "To install the Networking components"
msgstr ""
#: ./doc/install-guide/section_neutron-ml2-controller-node.xml:63(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:38(para) ./doc/install-guide/section_neutron-ml2-compute-node.xml:35(para)
msgid "SUSE does not use a separate ML2 plug-in package."
msgstr ""
#: ./doc/install-guide/section_neutron-ml2-controller-node.xml:68(title)
msgid "To configure the Networking server component"
msgstr ""
#: ./doc/install-guide/section_neutron-ml2-controller-node.xml:69(para)
msgid "The Networking server component configuration includes the database, authentication mechanism, message broker, topology change notifier, and plug-in."
msgstr ""
#: ./doc/install-guide/section_neutron-ml2-controller-node.xml:73(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:47(para) ./doc/install-guide/section_neutron-ml2-compute-node.xml:44(para)
msgid "Respond to prompts for <link linkend=\"debconf-dbconfig-common\">database management</link>, <link linkend=\"debconf-keystone_authtoken\">Identity service credentials</link>, <link linkend=\"debconf-api-endpoints\">service endpoint registration</link>, and <link linkend=\"debconf-rabbitqm\">message broker credentials</link>."
msgstr ""
#: ./doc/install-guide/section_neutron-ml2-controller-node.xml:83(para) ./doc/install-guide/section_neutron-ml2-controller-node.xml:90(para)
msgid "Configure Networking to use the database:"
msgstr ""
#: ./doc/install-guide/section_neutron-ml2-controller-node.xml:93(para)
msgid "Edit the <filename>/etc/neutron/neutron.conf</filename> file and add the following key to the <literal>[database]</literal> section:"
msgstr ""
#: ./doc/install-guide/section_neutron-ml2-controller-node.xml:96(para)
msgid "Replace <replaceable>NEUTRON_DBPASS</replaceable> with the password you chose for the database."
msgstr ""
#: ./doc/install-guide/section_neutron-ml2-controller-node.xml:105(para) ./doc/install-guide/section_neutron-ml2-controller-node.xml:128(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:57(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:80(para) ./doc/install-guide/section_neutron-ml2-compute-node.xml:54(para) ./doc/install-guide/section_neutron-ml2-compute-node.xml:77(para)
msgid "Configure Networking to use the Identity service for authentication:"
msgstr ""
#: ./doc/install-guide/section_neutron-ml2-controller-node.xml:107(para) ./doc/install-guide/section_neutron-ml2-controller-node.xml:140(para) ./doc/install-guide/section_neutron-ml2-controller-node.xml:344(para) ./doc/install-guide/section_neutron-ml2-controller-node.xml:378(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:59(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:92(para) ./doc/install-guide/section_neutron-ml2-compute-node.xml:56(para) ./doc/install-guide/section_neutron-ml2-compute-node.xml:89(para) ./doc/install-guide/section_neutron-ml2-compute-node.xml:288(para) ./doc/install-guide/section_neutron-ml2-compute-node.xml:322(para)
msgid "Replace <replaceable>NEUTRON_PASS</replaceable> with the password you chose for the <literal>neutron</literal> user in the Identity service."
msgstr ""
#: ./doc/install-guide/section_neutron-ml2-controller-node.xml:132(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:84(para) ./doc/install-guide/section_neutron-ml2-compute-node.xml:81(para)
msgid "Edit the <filename>/etc/neutron/neutron.conf</filename> file and add the following key to the <literal>[DEFAULT]</literal> section:"
msgstr ""
#: ./doc/install-guide/section_neutron-ml2-controller-node.xml:138(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:90(para) ./doc/install-guide/section_neutron-ml2-compute-node.xml:87(para)
msgid "Add the following keys to the <literal>[keystone_authtoken]</literal> section:"
msgstr ""
#: ./doc/install-guide/section_neutron-ml2-controller-node.xml:156(para) ./doc/install-guide/section_neutron-ml2-controller-node.xml:170(para) ./doc/install-guide/section_neutron-ml2-controller-node.xml:177(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:108(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:122(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:129(para) ./doc/install-guide/section_neutron-ml2-compute-node.xml:105(para) ./doc/install-guide/section_neutron-ml2-compute-node.xml:119(para) ./doc/install-guide/section_neutron-ml2-compute-node.xml:126(para)
msgid "Configure Networking to use the message broker:"
msgstr ""
#: ./doc/install-guide/section_neutron-ml2-controller-node.xml:157(para) ./doc/install-guide/section_neutron-ml2-controller-node.xml:183(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:109(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:135(para) ./doc/install-guide/section_neutron-ml2-compute-node.xml:106(para) ./doc/install-guide/section_neutron-ml2-compute-node.xml:132(para) ./doc/install-guide/section_glance-install.xml:83(para) ./doc/install-guide/section_glance-install.xml:96(para)
msgid "Replace <replaceable>RABBIT_PASS</replaceable> with the password you chose for the <literal>guest</literal> account in <application>RabbitMQ</application>."
msgstr ""
#: ./doc/install-guide/section_neutron-ml2-controller-node.xml:180(para) ./doc/install-guide/section_neutron-ml2-controller-node.xml:222(para) ./doc/install-guide/section_neutron-ml2-controller-node.xml:270(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:132(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:165(para) ./doc/install-guide/section_neutron-ml2-compute-node.xml:129(para) ./doc/install-guide/section_neutron-ml2-compute-node.xml:162(para)
msgid "Edit the <filename>/etc/neutron/neutron.conf</filename> file and add the following keys to the <literal>[DEFAULT]</literal> section:"
msgstr ""
#: ./doc/install-guide/section_neutron-ml2-controller-node.xml:195(para) ./doc/install-guide/section_neutron-ml2-controller-node.xml:213(para)
msgid "Configure Networking to notify Compute about network topology changes:"
msgstr ""
#: ./doc/install-guide/section_neutron-ml2-controller-node.xml:215(para)
msgid "Replace <replaceable>SERVICE_TENANT_ID</replaceable> with the <literal>service</literal> tenant identifier (id) in the Identity service and <replaceable>NOVA_PASS</replaceable> with the password you chose for the <literal>nova</literal> user in the Identity service."
msgstr ""
#: ./doc/install-guide/section_neutron-ml2-controller-node.xml:231(replaceable)
msgid "SERVICE_TENANT_ID"
msgstr ""
#: ./doc/install-guide/section_neutron-ml2-controller-node.xml:237(para)
msgid "To obtain the <literal>service</literal> tenant identifier (id):"
msgstr ""
#: ./doc/install-guide/section_neutron-ml2-controller-node.xml:252(para) ./doc/install-guide/section_neutron-ml2-controller-node.xml:266(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:147(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:161(para) ./doc/install-guide/section_neutron-ml2-compute-node.xml:144(para) ./doc/install-guide/section_neutron-ml2-compute-node.xml:158(para)
msgid "Configure Networking to use the Modular Layer 2 (ML2) plug-in and associated services:"
msgstr ""
#: ./doc/install-guide/section_neutron-ml2-controller-node.xml:259(para) ./doc/install-guide/section_neutron-ml2-controller-node.xml:279(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:154(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:174(para) ./doc/install-guide/section_neutron-ml2-compute-node.xml:151(para) ./doc/install-guide/section_neutron-ml2-compute-node.xml:171(para)
msgid "We recommend adding <literal>verbose = True</literal> to the <literal>[DEFAULT]</literal> section in <filename>/etc/neutron/neutron.conf</filename> to assist with troubleshooting."
msgstr ""
#: ./doc/install-guide/section_neutron-ml2-controller-node.xml:288(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:183(para) ./doc/install-guide/section_neutron-ml2-compute-node.xml:180(para)
msgid "Comment out any lines in the <literal>[service_providers]</literal> section."
msgstr ""
#: ./doc/install-guide/section_neutron-ml2-controller-node.xml:293(title) ./doc/install-guide/section_neutron-ml2-network-node.xml:351(title) ./doc/install-guide/section_neutron-ml2-compute-node.xml:185(title)
msgid "To configure the Modular Layer 2 (ML2) plug-in"
msgstr ""
#: ./doc/install-guide/section_neutron-ml2-controller-node.xml:294(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/install-guide/section_neutron-ml2-controller-node.xml:314(para) ./doc/install-guide/section_neutron-ml2-compute-node.xml:217(para)
msgid "Edit the <filename>/etc/neutron/plugins/ml2/ml2_conf.ini</filename> file:"
msgstr ""
#: ./doc/install-guide/section_neutron-ml2-controller-node.xml:317(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:386(para) ./doc/install-guide/section_neutron-ml2-compute-node.xml:220(para)
msgid "Add the following keys to the <literal>[ml2]</literal> section:"
msgstr ""
#: ./doc/install-guide/section_neutron-ml2-controller-node.xml:324(para)
msgid "Add the following key to the <literal>[ml2_type_gre]</literal> section:"
msgstr ""
#: ./doc/install-guide/section_neutron-ml2-controller-node.xml:329(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:409(para) ./doc/install-guide/section_neutron-ml2-compute-node.xml:243(para)
msgid "Add the <literal>[securitygroup]</literal> section and the following keys to it:"
msgstr ""
#: ./doc/install-guide/section_neutron-ml2-controller-node.xml:338(title) ./doc/install-guide/section_neutron-ml2-compute-node.xml:282(title)
msgid "To configure Compute to use Networking"
msgstr ""
#: ./doc/install-guide/section_neutron-ml2-controller-node.xml:339(para) ./doc/install-guide/section_neutron-ml2-compute-node.xml:283(para)
msgid "By default, most distributions configure Compute to use legacy networking. You must reconfigure Compute to manage networks through Networking."
msgstr ""
#: ./doc/install-guide/section_neutron-ml2-controller-node.xml:368(para) ./doc/install-guide/section_neutron-ml2-controller-node.xml:394(para) ./doc/install-guide/section_neutron-ml2-compute-node.xml:312(para) ./doc/install-guide/section_neutron-ml2-compute-node.xml:338(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 <literal>nova.virt.firewall.NoopFirewallDriver</literal> firewall driver."
msgstr ""
#: ./doc/install-guide/section_neutron-ml2-controller-node.xml:376(para) ./doc/install-guide/section_neutron-ml2-compute-node.xml:320(para)
msgid "Edit the <filename>/etc/nova/nova.conf</filename> and add the following keys to the <literal>[DEFAULT]</literal> section:"
msgstr ""
#: ./doc/install-guide/section_neutron-ml2-controller-node.xml:403(title) ./doc/install-guide/section_basics-queue.xml:96(title)
msgid "To finalize installation"
msgstr ""
#: ./doc/install-guide/section_neutron-ml2-controller-node.xml:405(para)
msgid "The Networking service initialization scripts expect a symbolic link <filename>/etc/neutron/plugin.ini</filename> pointing to the configuration file associated with your chosen plug-in. Using ML2, for example, the symbolic link must point to <filename>/etc/neutron/plugins/ml2/ml2_conf.ini</filename>. If this symbolic link does not exist, create it using the following commands:"
msgstr ""
#: ./doc/install-guide/section_neutron-ml2-controller-node.xml:415(para)
msgid "The Networking service initialization scripts expect the variable <literal>NEUTRON_PLUGIN_CONF</literal> in file <filename>/etc/sysconfig/neutron</filename> to reference the configuration file associated with your chosen plug-in. Using ML2, for example, edit the <filename>/etc/sysconfig/neutron</filename> file and add the following:"
msgstr ""
#: ./doc/install-guide/section_neutron-ml2-controller-node.xml:425(para) ./doc/install-guide/section_neutron-ovs-controller-node.xml:331(para) ./doc/install-guide/section_nova-networking-controller-node.xml:26(para)
msgid "Restart the Compute services:"
msgstr ""
#: ./doc/install-guide/section_neutron-ml2-controller-node.xml:434(para) ./doc/install-guide/section_neutron-ovs-controller-node.xml:337(para)
msgid "Start the Networking service and configure it to start when the system boots:"
msgstr ""
#: ./doc/install-guide/section_neutron-ml2-controller-node.xml:442(para) ./doc/install-guide/section_neutron-single-flat.xml:258(para)
msgid "Restart the Networking service:"
msgstr ""
#: ./doc/install-guide/section_keystone-services.xml:4(title)
msgid "Define services and API endpoints"
msgstr ""
#: ./doc/install-guide/section_keystone-services.xml:5(para)
msgid "So that the Identity Service can track which OpenStack services are installed and where they are located on the network, you must register each service in your OpenStack installation. To register a service, run these commands:"
msgstr ""
#: ./doc/install-guide/section_keystone-services.xml:11(para)
msgid "<placeholder-1/>. Describes the service."
msgstr ""
#: ./doc/install-guide/section_keystone-services.xml:15(para)
msgid "<placeholder-1/>. Associates <glossterm baseform=\"API endpoint\">API endpoints</glossterm> with the service."
msgstr ""
#: ./doc/install-guide/section_keystone-services.xml:20(para)
msgid "You must also register the Identity Service itself. Use the <code>OS_SERVICE_TOKEN</code> environment variable, as set previously, for authentication."
msgstr ""
#: ./doc/install-guide/section_keystone-services.xml:25(para)
msgid "Create a service entry for the Identity Service:"
msgstr ""
#: ./doc/install-guide/section_keystone-services.xml:36(para) ./doc/install-guide/object-storage/section_object-storage-install.xml:83(para)
msgid "The service ID is randomly generated and is different from the one shown here."
msgstr ""
#: ./doc/install-guide/section_keystone-services.xml:40(para)
msgid "Specify an API endpoint for the Identity 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 <literal>controller</literal> host name is used. Note that the Identity Service uses a different port for the admin API."
msgstr ""
#: ./doc/install-guide/section_keystone-services.xml:63(para)
msgid "You will need to create an additional endpoint for each service added to your OpenStack environment. The sections of this guide associated with the installation of each service include the endpoint creation step specific to the service."
msgstr ""
#: ./doc/install-guide/section_keystone-verify.xml:6(title)
msgid "Verify the Identity Service installation"
msgstr ""
#: ./doc/install-guide/section_keystone-verify.xml:9(para)
msgid "To verify that the Identity Service is installed and configured correctly, clear the values in the <envar>OS_SERVICE_TOKEN</envar> and <envar>OS_SERVICE_ENDPOINT</envar> environment variables:"
msgstr ""
#: ./doc/install-guide/section_keystone-verify.xml:15(para)
msgid "These variables, which were used to bootstrap the administrative user and register the Identity Service, are no longer needed."
msgstr ""
#: ./doc/install-guide/section_keystone-verify.xml:20(para)
msgid "You can now use regular user name-based authentication."
msgstr ""
#: ./doc/install-guide/section_keystone-verify.xml:22(para)
msgid "Request a authentication token by using the <literal>admin</literal> user and the password you chose for that user:"
msgstr ""
#: ./doc/install-guide/section_keystone-verify.xml:27(para)
msgid "In response, you receive a token paired with your user ID. This verifies that the Identity Service is running on the expected endpoint and that your user account is established with the expected credentials."
msgstr ""
#: ./doc/install-guide/section_keystone-verify.xml:33(para)
msgid "Verify that authorization behaves as expected. To do so, request authorization on a tenant:"
msgstr ""
#: ./doc/install-guide/section_keystone-verify.xml:38(para)
msgid "In response, you receive a token that includes the ID of the tenant that you specified. This verifies that your user account has an explicitly defined role on the specified tenant and the tenant exists as expected."
msgstr ""
#: ./doc/install-guide/section_keystone-verify.xml:44(para)
msgid "You can also set your <literal>--os-*</literal> variables in your environment to simplify command-line usage. Set up a <filename>admin-openrc.sh</filename> file with the admin credentials and admin endpoint:"
msgstr ""
#: ./doc/install-guide/section_keystone-verify.xml:54(para)
msgid "Source this file to read in the environment variables:"
msgstr ""
#: ./doc/install-guide/section_keystone-verify.xml:59(para)
msgid "Verify that your <filename>admin-openrc.sh</filename> file is configured correctly. Run the same command without the <literal>--os-*</literal> arguments:"
msgstr ""
#: ./doc/install-guide/section_keystone-verify.xml:63(para)
msgid "The command returns a token and the ID of the specified tenant. This verifies that you have configured your environment variables correctly."
msgstr ""
#: ./doc/install-guide/section_keystone-verify.xml:68(para)
msgid "Verify that your admin account has authorization to perform administrative commands:"
msgstr ""
#: ./doc/install-guide/section_keystone-verify.xml:85(para)
msgid "Seeing that the <literal>id</literal> in the output from the <placeholder-1/> command matches the <literal>user_id</literal> in the <placeholder-2/> command, and that the admin role is listed for that user, for the related tenant, this verifies that your user account has the <literal>admin</literal> role, which matches the role used in the Identity Service <filename>policy.json</filename> file."
msgstr ""
#: ./doc/install-guide/section_keystone-verify.xml:95(para)
msgid "As long as you define your credentials and the Identity Service endpoint through the command line or environment variables, you can run all OpenStack client commands from any machine. For details, see <xref linkend=\"ch_clients\"/>."
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/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:15(None) ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:862(None)
msgid "@@image: '../common/figures/UseCase-MultiRouter.png'; md5=5695d4b003e2f8442eab135cbcd1f842"
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/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:25(None)
msgid "@@image: '../common/figures/demo_routers_with_private_networks.png'; md5=985b8cacfd7161ce50ee13106b27f854"
msgstr ""
#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:6(title)
msgid "Per-tenant routers with private networks"
msgstr ""
#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:7(para)
msgid "This section describes how to install the OpenStack Networking service and its components for a use case that has per-tenant routers with private networks."
msgstr ""
#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:19(para)
msgid "The following figure shows the setup:"
msgstr ""
#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:29(para)
msgid "As shown in the figure, the setup includes:"
msgstr ""
#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:32(para)
msgid "An interface for management traffic on each node."
msgstr ""
#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:36(para)
msgid "Use of the Open vSwitch plug-in."
msgstr ""
#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:39(para)
msgid "GRE tunnels for data transport on all agents."
msgstr ""
#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:42(para)
msgid "Floating IPs and router gateway ports that are configured in an external network, and a physical router that connects the floating IPs and router gateway ports to the outside world."
msgstr ""
#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:49(para)
msgid "Because this example runs a DHCP agent and L3 agent on one node, you must set the <literal>use_namespace</literal> option to <literal>True</literal> in the configuration file for each agent. The default is <literal>True</literal>."
msgstr ""
#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:55(para)
msgid "This table describes the nodes:"
msgstr ""
#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:61(th) ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:31(th) ./doc/install-guide/section_neutron-single-flat.xml:32(th)
msgid "Node"
msgstr ""
#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:62(th) ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:32(th) ./doc/install-guide/app_reserved_uids.xml:28(th) ./doc/install-guide/section_neutron-single-flat.xml:33(th)
msgid "Description"
msgstr ""
#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:67(td) ./doc/install-guide/section_neutron-single-flat.xml:38(td)
msgid "Controller Node"
msgstr ""
#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:68(para)
msgid "Runs Networking, Identity Service, and all Compute services that are required to deploy VMs (<systemitem class=\"service\">nova-api</systemitem>, <systemitem class=\"service\">nova-scheduler</systemitem>, for example). The node must have at least one network interface, which connects to the Management Network. The host name is <literal>controlnode</literal>, which other nodes resolve to the IP of the controller node."
msgstr ""
#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:80(para)
msgid "The <systemitem class=\"service\">nova-network</systemitem> service should not be running. This is replaced by Networking."
msgstr ""
#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:87(td) ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:281(title) ./doc/install-guide/section_neutron-single-flat.xml:70(td)
msgid "Compute Node"
msgstr ""
#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:90(systemitem) ./doc/install-guide/section_neutron-single-flat.xml:73(systemitem)
msgid "nova-compute"
msgstr ""
#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:92(systemitem)
msgid "nova-*"
msgstr ""
#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:88(td)
msgid "Runs the Networking L2 agent and the Compute services that run VMs (<placeholder-1/> specifically, and optionally other <placeholder-2/> services depending on configuration). The node must have at least two network interfaces. One interface communicates with the controller node through the management network. The other node is used for the VM traffic on the data network. The VM receives its IP address from the DHCP agent on this network."
msgstr ""
#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:101(td) ./doc/install-guide/section_neutron-single-flat.xml:84(td)
msgid "Network Node"
msgstr ""
#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:102(td)
msgid "Runs Networking L2 agent, DHCP agent and L3 agent. This node has access to the external network. The DHCP agent allocates IP addresses to the VMs on data network. (Technically, the addresses are allocated by the Networking server, and distributed by the dhcp agent.) The node must have at least two network interfaces. One interface communicates with the controller node through the management network. The other interface is used as external network. GRE tunnels are set up as data networks."
msgstr ""
#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:115(td) ./doc/install-guide/section_neutron-single-flat.xml:94(td)
msgid "Router"
msgstr ""
#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:116(td) ./doc/install-guide/section_neutron-single-flat.xml:95(td)
msgid "Router has IP 30.0.0.1, which is the default gateway for all VMs. The router must be able to access public networks."
msgstr ""
#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:122(para)
msgid "The use case assumes the following:"
msgstr ""
#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:123(emphasis) ./doc/install-guide/section_basics-networking-nova.xml:42(title) ./doc/install-guide/section_basics-networking-neutron.xml:46(title) ./doc/install-guide/section_neutron-single-flat.xml:102(emphasis)
msgid "Controller node"
msgstr ""
#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:126(para) ./doc/install-guide/section_neutron-single-flat.xml:105(para)
msgid "Relevant Compute services are installed, configured, and running."
msgstr ""
#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:130(para)
msgid "Glance is installed, configured, and running. In addition, an image named <literal>tty</literal> must be present."
msgstr ""
#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:135(para)
msgid "Identity is installed, configured, and running. A Networking user named <emphasis role=\"bold\">neutron</emphasis> should be created on tenant <emphasis role=\"bold\">service</emphasis> with password <replaceable>NEUTRON_PASS</replaceable>."
msgstr ""
#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:145(para)
msgid "RabbitMQ is running with default guest and password <replaceable>RABBIT_PASS</replaceable>."
msgstr ""
#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:150(para) ./doc/install-guide/section_neutron-single-flat.xml:133(para)
msgid "MySQL server (user is <emphasis role=\"bold\">root</emphasis>)."
msgstr ""
#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:143(para)
msgid "Additional services: <placeholder-1/>"
msgstr ""
#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:156(emphasis) ./doc/install-guide/section_basics-networking-nova.xml:74(title) ./doc/install-guide/section_basics-networking-neutron.xml:163(title) ./doc/install-guide/section_neutron-single-flat.xml:139(emphasis)
msgid "Compute node"
msgstr ""
#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:157(para)
msgid "Install and configure Compute."
msgstr ""
#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:159(title) ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:91(title) ./doc/install-guide/section_neutron-single-flat.xml:146(title)
msgid "Install"
msgstr ""
#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:162(emphasis) ./doc/install-guide/section_neutron-single-flat.xml:149(emphasis)
msgid "Controller node - Networking server"
msgstr ""
#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:166(para) ./doc/install-guide/section_neutron-single-flat.xml:154(para)
msgid "Install the Networking server."
msgstr ""
#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:169(para) ./doc/install-guide/section_neutron-single-flat.xml:168(para)
msgid "Create database <emphasis role=\"bold\">ovs_neutron</emphasis>."
msgstr ""
#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:173(para)
msgid "Update the Networking configuration file, <filename> /etc/neutron/neutron.conf</filename>, with plug-in choice and Identity Service user as necessary:"
msgstr ""
#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:202(para)
msgid "Update the plug-in configuration file, <filename>/etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini</filename>:"
msgstr ""
#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:210(para)
msgid "Start the Networking server."
msgstr ""
#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:211(para)
msgid "The Networking server can be a service of the operating system. The command to start the service depends on your operating system. The following command runs the Networking server directly:"
msgstr ""
#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:223(emphasis) ./doc/install-guide/section_neutron-single-flat.xml:265(emphasis)
msgid "Compute node - Compute"
msgstr ""
#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:225(para)
msgid "Install Compute services."
msgstr ""
#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:228(para)
msgid "Update the Compute <filename> /etc/nova/nova.conf</filename> configuration file. Make sure the following line appears at the end of this file:"
msgstr ""
#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:243(para)
msgid "Restart relevant Compute services."
msgstr ""
#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:249(emphasis)
msgid "Compute and Networking node - L2 agent"
msgstr ""
#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:253(para)
msgid "Install and start Open vSwitch."
msgstr ""
#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:256(para)
msgid "Install the L2 agent (Neutron Open vSwitch agent)."
msgstr ""
#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:260(para) ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:168(para)
msgid "Add the integration bridge to the Open vSwitch:"
msgstr ""
#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:265(para)
msgid "Update the Networking configuration file, <filename> /etc/neutron/neutron.conf</filename>:"
msgstr ""
#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:279(para)
msgid "Update the plug-in configuration file, <filename> /etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini</filename>."
msgstr ""
#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:282(para)
msgid "Compute node:"
msgstr ""
#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:288(para)
msgid "Network node:"
msgstr ""
#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:296(para)
msgid "Create the integration bridge <emphasis role=\"bold\">br-int</emphasis>:"
msgstr ""
#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:301(para)
msgid "Start the Networking L2 agent"
msgstr ""
#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:302(para)
msgid "The Networking Open vSwitch L2 agent can be a service of the operating system. The command to start depends on your operating system. The following command runs the service directly:"
msgstr ""
#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:313(emphasis) ./doc/install-guide/section_neutron-single-flat.xml:411(emphasis)
msgid "Network node - DHCP agent"
msgstr ""
#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:317(para) ./doc/install-guide/section_neutron-single-flat.xml:414(para)
msgid "Install the DHCP agent."
msgstr ""
#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:320(para)
msgid "Update the Networking configuration file, <filename> /etc/neutron/neutron.conf</filename>"
msgstr ""
#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:331(literal)
msgid "allow_overlapping_ips"
msgstr ""
#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:330(emphasis)
msgid "Set <placeholder-1/> because TenantA and TenantC use overlapping subnets."
msgstr ""
#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:336(para)
msgid "Update the DHCP <filename> /etc/neutron/dhcp_agent.ini</filename> configuration file:"
msgstr ""
#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:342(para)
msgid "Start the DHCP agent."
msgstr ""
#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:343(para)
msgid "The Networking DHCP agent can be a service of operating system. The command to start the service depends on your operating system. The following command runs the service directly:"
msgstr ""
#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:354(emphasis)
msgid "Network node - L3 agent"
msgstr ""
#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:358(para)
msgid "Install the L3 agent."
msgstr ""
#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:361(para)
msgid "Add the external network bridge"
msgstr ""
#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:365(para)
msgid "Add the physical interface, for example eth0, that is connected to the outside network to this bridge:"
msgstr ""
#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:371(para)
msgid "Update the L3 configuration file <filename> /etc/neutron/l3_agent.ini</filename>:"
msgstr ""
#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:378(literal)
msgid "use_namespaces"
msgstr ""
#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:377(emphasis)
msgid "Set the <placeholder-1/> option (it is True by default) because TenantA and TenantC have overlapping subnets, and the routers are hosted on one l3 agent network node."
msgstr ""
#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:386(para)
msgid "Start the L3 agent"
msgstr ""
#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:387(para)
msgid "The Networking L3 agent can be a service of the operating system. The command to start the service depends on your operating system. The following command starts the agent directly:"
msgstr ""
#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:401(title) ./doc/install-guide/section_neutron-single-flat.xml:477(title)
msgid "Configure logical network"
msgstr ""
#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:402(para)
msgid "You can run these commands on the network node."
msgstr ""
#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:404(para)
msgid "Ensure that the following environment variables are set. Various clients use these to access the Identity Service."
msgstr ""
#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:414(para) ./doc/install-guide/section_neutron-single-flat.xml:490(para)
msgid "Get the tenant ID (Used as $TENANT_ID later):"
msgstr ""
#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:428(para)
msgid "Get user information:"
msgstr ""
#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:441(para)
msgid "Create the external network and its subnet by admin user:"
msgstr ""
#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:479(literal)
msgid "provider:network_type local"
msgstr ""
#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:482(literal)
msgid "router:external true"
msgstr ""
#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:478(emphasis)
msgid "<placeholder-1/> means that Networking does not have to realize this network through provider network. <placeholder-2/> means that an external network is created where you can create the floating IP and router gateway port."
msgstr ""
#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:488(para)
msgid "Add an IP on the external network to br-ex."
msgstr ""
#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:489(para)
msgid "Because br-ex is the external network bridge, add an IP 30.0.0.100/24 to br-ex and ping the floating IP of the VM from our network node."
msgstr ""
#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:497(para)
msgid "Serve TenantA."
msgstr ""
#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:498(para)
msgid "For TenantA, create a private network, subnet, server, router, and floating IP."
msgstr ""
#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:502(para)
msgid "Create a network for TenantA:"
msgstr ""
#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:518(para)
msgid "After that, you can use admin user to query the provider network information:"
msgstr ""
#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:537(para)
msgid "The network has GRE tunnel ID (for example, provider:segmentation_id) 1."
msgstr ""
#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:542(para)
msgid "Create a subnet on the network TenantA-Net:"
msgstr ""
#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:564(para)
msgid "Create a server for TenantA:"
msgstr ""
#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:576(para)
msgid "It is important to understand that you should not attach the instance to Ext-Net directly. Instead, you must use a floating IP to make it accessible from the external network."
msgstr ""
#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:585(para)
msgid "Create and configure a router for TenantA:"
msgstr ""
#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:603(para)
msgid "Added interface to router TenantA-R1"
msgstr ""
#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:612(para)
msgid "Associate a floating IP for TenantA_VM1."
msgstr ""
#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:616(para)
msgid "Create a floating IP:"
msgstr ""
#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:633(para)
msgid "Get the port ID of the VM with ID 7c5e6499-7ef7-4e36-8216-62c2941d21ff:"
msgstr ""
#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:645(para)
msgid "Associate the floating IP with the VM port:"
msgstr ""
#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:663(para)
msgid "Ping the public network from the server of TenantA."
msgstr ""
#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:665(para)
msgid "In my environment, 192.168.1.0/24 is my public network connected with my physical router, which also connects to the external network 30.0.0.0/24. With the floating IP and virtual router, you can ping the public network within the server of tenant A:"
msgstr ""
#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:683(para)
msgid "Ping the floating IP of TenantA's server:"
msgstr ""
#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:696(para)
msgid "Create other servers for TenantA."
msgstr ""
#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:697(para)
msgid "You can create more servers for TenantA and add floating IPs for them."
msgstr ""
#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:701(para)
msgid "Serve TenantC."
msgstr ""
#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:702(para)
msgid "For TenantC, you create two private networks with subnet 10.0.0.0/24 and subnet 10.0.1.0/24, some servers, one router to connect to these two subnets and some floating IPs."
msgstr ""
#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:708(para)
msgid "Create networks and subnets for TenantC:"
msgstr ""
#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:720(para)
msgid "After that you can use admin user to query the network's provider network information:"
msgstr ""
#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:756(para)
msgid "You can see GRE tunnel IDs (such as, provider:segmentation_id) 2 and 3. And also note the network IDs and subnet IDs because you use them to create VMs and the router."
msgstr ""
#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:763(para)
msgid "Create a server TenantC-VM1 for TenantC on TenantC-Net1."
msgstr ""
#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:770(para)
msgid "Create a server TenantC-VM3 for TenantC on TenantC-Net2."
msgstr ""
#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:777(para)
msgid "List servers of TenantC."
msgstr ""
#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:786(para)
msgid "Note the server IDs because you use them later."
msgstr ""
#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:790(para)
msgid "Make sure servers get their IPs."
msgstr ""
#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:791(para)
msgid "You can use VNC to log on the VMs to check if they get IPs. If not, you must make sure that the Networking components are running correctly and the GRE tunnels work."
msgstr ""
#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:798(para)
msgid "Create and configure a router for TenantC:"
msgstr ""
#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:813(para)
msgid "Checkpoint: ping from within TenantC's servers."
msgstr ""
#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:815(para)
msgid "Because a router connects to two subnets, the VMs on these subnets can ping each other. And because the gateway for the router is set, TenantC's servers can ping external network IPs, such as 192.168.1.1, 30.0.0.1, and so on."
msgstr ""
#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:823(para) ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:834(para)
msgid "Associate floating IPs for TenantC's servers."
msgstr ""
#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:825(para)
msgid "Because a router connects to two subnets, the VMs on these subnets can ping each other. And because the gateway interface for the router is set, TenantC's servers can ping external network IPs, such as 192.168.1.1, 30.0.0.1, and so on."
msgstr ""
#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:836(para)
msgid "You can use similar commands to the ones used in the section for TenantA."
msgstr ""
#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:844(title)
msgid "Use case: per-tenant routers with private networks"
msgstr ""
#: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml:846(para)
msgid "This use case represents a more advanced router scenario in which each tenant gets at least one router, and potentially has access to the Networking API to create additional routers. The tenant can create their own networks, potentially uplinking those networks to a router. This model enables tenant-defined, multi-tier applications, with each tier being a separate network behind the router. Because there are multiple routers, tenant subnets can overlap without conflicting, because access to external networks all happens through SNAT or floating IPs. Each router uplink and floating IP is allocated from the external network subnet."
msgstr ""
#: ./doc/install-guide/ch_networking.xml:6(title)
msgid "Add a networking service"
msgstr ""
#: ./doc/install-guide/ch_networking.xml:7(para)
msgid "Configuring networking in OpenStack can be a bewildering experience. This guide provides step-by-step instructions for both OpenStack Networking (neutron) and the legacy networking (nova-network) service. If you are unsure which to use, we recommend trying OpenStack Networking because it offers a considerable number of features and flexibility including <glossterm baseform=\"plug-in\">plug-ins</glossterm> for a variety of emerging products supporting <glossterm>virtual networking</glossterm>. See the <link href=\"http://docs.openstack.org/admin-guide-cloud/content/ch_networking.html\">Networking</link> chapter of the <citetitle>OpenStack Cloud Administrator Guide</citetitle> for more information."
msgstr ""
#: ./doc/install-guide/ch_networking.xml:20(title) ./doc/install-guide/section_basics-networking-neutron.xml:6(title)
msgid "OpenStack Networking (neutron)"
msgstr ""
#: ./doc/install-guide/ch_networking.xml:23(title)
msgid "Modular Layer 2 (ML2) plug-in"
msgstr ""
#: ./doc/install-guide/ch_networking.xml:31(title) ./doc/install-guide/section_basics-networking-nova.xml:6(title)
msgid "Legacy networking (nova-network)"
msgstr ""
#: ./doc/install-guide/ch_networking.xml:38(para)
msgid "Your OpenStack environment now includes the core components necessary to launch a basic instance. You can <link linkend=\"launch-instance\">launch an instance</link> or add more services to your environment in the following chapters."
msgstr ""
#: ./doc/install-guide/ch_horizon.xml:6(title)
msgid "Add the dashboard"
msgstr ""
#: ./doc/install-guide/ch_horizon.xml:7(para)
msgid "The OpenStack dashboard, also known as <link href=\"https://github.com/openstack/horizon/\">Horizon</link>, is a Web interface that enables cloud administrators and users to manage various OpenStack resources and services."
msgstr ""
#: ./doc/install-guide/ch_horizon.xml:12(para)
msgid "The dashboard enables web-based interactions with the OpenStack Compute cloud controller through the OpenStack APIs."
msgstr ""
#: ./doc/install-guide/ch_horizon.xml:15(para)
msgid "These instructions show an example deployment configured with an Apache web server."
msgstr ""
#: ./doc/install-guide/ch_horizon.xml:17(para)
msgid "After you <link linkend=\"install_dashboard\">install and configure the dashboard</link>, you can complete the following tasks:"
msgstr ""
#: ./doc/install-guide/ch_horizon.xml:22(para)
msgid "Customize your dashboard. See section <link href=\"http://docs.openstack.org/admin-guide-cloud/content/ch_install-dashboard.html#dashboard-custom-brand\">Customize the dashboard</link> in the <link href=\"http://docs.openstack.org/admin-guide-cloud/content/\"><citetitle>OpenStack Cloud Administrator Guide</citetitle></link>."
msgstr ""
#: ./doc/install-guide/ch_horizon.xml:30(para)
msgid "Set up session storage for the dashboard. See <xref linkend=\"dashboard-sessions\"/>."
msgstr ""
#: ./doc/install-guide/ch_horizon.xml:39(para)
msgid "Your OpenStack environment now includes the dashboard. You can <link linkend=\"launch-instance\">launch an instance</link> or add more services to your environment in the following chapters."
msgstr ""
#: ./doc/install-guide/section_heat-verify.xml:6(title)
msgid "Verify the Orchestration service installation"
msgstr ""
#: ./doc/install-guide/section_heat-verify.xml:8(para)
msgid "To verify that the Orchestration service is installed and configured correctly, make sure that your credentials are set up correctly in the <filename>demo-openrc.sh</filename> file. Source the file, as follows:"
msgstr ""
#: ./doc/install-guide/section_heat-verify.xml:14(para)
msgid "The Orchestration Module uses templates to describe stacks. To learn about the template languages, see <link href=\"http://docs.openstack.org/developer/heat/template_guide/index.html\">the Template Guide</link> in the <link href=\"http://docs.openstack.org/developer/heat/\">Heat developer documentation</link>."
msgstr ""
#: ./doc/install-guide/section_heat-verify.xml:20(para)
msgid "Create a test template in the <filename>test-stack.yml</filename> file with the following content:"
msgstr ""
#: ./doc/install-guide/section_heat-verify.xml:24(para)
msgid "Use the <placeholder-1/> command to create a stack from this template:"
msgstr ""
#: ./doc/install-guide/section_heat-verify.xml:35(para)
msgid "Verify that the stack was created successfully with the <placeholder-1/> command:"
msgstr ""
#: ./doc/install-guide/ch_ceilometer.xml:6(title)
msgid "Add the Telemetry module"
msgstr ""
#: ./doc/install-guide/ch_ceilometer.xml:7(para)
msgid "Telemetry provides a framework for monitoring and metering the OpenStack cloud. It is also known as the Ceilometer project."
msgstr ""
#: ./doc/install-guide/ch_ceilometer.xml:19(para)
msgid "Your OpenStack environment now includes Telemetry. You can <link linkend=\"launch-instance\">launch an instance</link> or add more services to your environment in the previous chapters."
msgstr ""
#: ./doc/install-guide/ch_keystone.xml:6(title)
msgid "Configure the Identity Service"
msgstr ""
#: ./doc/install-guide/ch_heat.xml:6(title)
msgid "Add the Orchestration service"
msgstr ""
#: ./doc/install-guide/ch_heat.xml:7(para)
msgid "Use the Orchestration module to create cloud resources using a template language called HOT. The integrated project name is Heat."
msgstr ""
#: ./doc/install-guide/ch_heat.xml:15(para)
msgid "Your OpenStack environment now includes Orchestration. You can <link linkend=\"launch-instance\">launch an instance</link> 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/install-guide/section_debconf-rabbitqm.xml:15(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/install-guide/section_debconf-rabbitqm.xml:22(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/install-guide/section_debconf-rabbitqm.xml:29(None)
msgid "@@image: 'figures/debconf-screenshots/rabbitmq-password.png'; md5=6385185200d20e96b6316ae15ae1255d"
msgstr ""
#: ./doc/install-guide/section_debconf-rabbitqm.xml:6(title)
msgid "RabbitMQ credentials parameters"
msgstr ""
#: ./doc/install-guide/section_debconf-rabbitqm.xml:7(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 <systemitem class=\"service\">ceilometer-common</systemitem> package:"
msgstr ""
#: ./doc/install-guide/section_debconf-rabbitqm.xml:33(para)
msgid "These debconf screens appear in: <systemitem class=\"service\">ceilometer-common</systemitem>, <systemitem class=\"service\">cinder-common</systemitem>, <systemitem class=\"service\">glance-common</systemitem>, <systemitem class=\"service\">heat-common</systemitem>, <systemitem class=\"service\">neutron-common</systemitem> and <systemitem class=\"service\">nova-common</systemitem>."
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/install-guide/section_neutron-provider-router-with-private_networks.xml:16(None)
msgid "@@image: '../common/figures/Neutron-PhysNet-Diagram.png'; md5=ea581fd58c57da1a6c9512b82027a195"
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/install-guide/section_neutron-provider-router-with-private_networks.xml:660(None)
msgid "@@image: '../common/figures/UseCase-SingleRouter.png'; md5=63d21d52d32ed7fa1c1dad1a1fd88eb5"
msgstr ""
#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:6(title)
msgid "Provider router with private networks"
msgstr ""
#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:7(para)
msgid "This section describes how to install the OpenStack Networking service and its components for a single router use case: a provider router with private networks."
msgstr ""
#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:10(para)
msgid "This figure shows the set up:"
msgstr ""
#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:21(para)
msgid "Because you run the DHCP agent and L3 agent on one node, you must set <literal>use_namespaces</literal> to <literal>True</literal> (which is the default) in the configuration files for both agents."
msgstr ""
#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:26(para)
msgid "The configuration includes these nodes:"
msgstr ""
#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:28(caption)
msgid "Nodes for use case"
msgstr ""
#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:37(para) ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:93(title)
msgid "Controller"
msgstr ""
#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:38(para)
msgid "Runs the Networking service, Identity Service, and all Compute services that are required to deploy a VM."
msgstr ""
#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:41(para)
msgid "The service must have at least two network interfaces. The first should be connected to the Management Network to communicate with the compute and network nodes. The second interface should be connected to the API/public network."
msgstr ""
#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:49(para)
msgid "Compute"
msgstr ""
#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:50(para)
msgid "Runs Compute and the Networking L2 agent."
msgstr ""
#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:52(para)
msgid "This node does not have access to the public network."
msgstr ""
#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:54(para)
msgid "The node must have a network interface that communicates with the controller node through the management network. The VM receives its IP address from the DHCP agent on this network."
msgstr ""
#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:61(para)
msgid "Network"
msgstr ""
#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:62(para)
msgid "Runs Networking L2 agent, DHCP agent, and L3 agent."
msgstr ""
#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:64(para)
msgid "This node has access to the public network. The DHCP agent allocates IP addresses to the VMs on the network. The L3 agent performs NAT and enables the VMs to access the public network."
msgstr ""
#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:71(para)
msgid "A network interface that communicates with the controller node through the management network"
msgstr ""
#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:77(para)
msgid "A network interface on the data network that manages VM traffic"
msgstr ""
#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:82(para)
msgid "A network interface that connects to the external gateway on the network"
msgstr ""
#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:69(para)
msgid "The node must have:<placeholder-1/>"
msgstr ""
#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:95(title)
msgid "To install and configure the controller node"
msgstr ""
#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:98(para)
msgid "Run this command:"
msgstr ""
#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:104(para)
msgid "Configure Networking services:"
msgstr ""
#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:107(para)
msgid "Edit the <filename>/etc/neutron/neutron.conf</filename> file and add these lines:"
msgstr ""
#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:119(para) ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:338(para)
msgid "Edit the <filename> /etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini</filename> file and add these lines:"
msgstr ""
#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:127(para)
msgid "Edit the <filename> /etc/neutron/api-paste.ini</filename> file and add these lines:"
msgstr ""
#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:137(para)
msgid "Start the services:"
msgstr ""
#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:144(title) ./doc/install-guide/section_basics-networking-neutron.xml:81(title)
msgid "Network node"
msgstr ""
#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:146(title)
msgid "Install and configure the network node"
msgstr ""
#. FIXME Review Fedora instructions
#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:148(para) ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:287(para)
msgid "Install the packages:"
msgstr ""
#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:157(para)
msgid "Start Open vSwitch<phrase os=\"rhel;centos;fedora;opensuse;sles\"> and configure it to start when the system boots</phrase>:"
msgstr ""
#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:173(para)
msgid "Update the OpenStack Networking <filename>/etc/neutron/neutron.conf</filename> configuration file:"
msgstr ""
#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:194(para)
msgid "Update the plug-in <filename>/etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini</filename> configuration file:"
msgstr ""
#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:203(para)
msgid "All VM communication between the nodes occurs through the <literal>br-eth1</literal> bridge."
msgstr ""
#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:206(para) ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:311(para)
msgid "Create the <literal>br-eth1</literal> network bridge:"
msgstr ""
#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:212(para)
msgid "Create the external network bridge to the Open vSwitch:"
msgstr ""
#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:218(para)
msgid "Edit the <filename>/etc/neutron/l3_agent.ini</filename> file and add these lines:"
msgstr ""
#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:230(para)
msgid "Edit the <filename>/etc/neutron/api-paste.ini</filename> file and add these lines:"
msgstr ""
#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:240(para)
msgid "Edit the <filename>/etc/neutron/dhcp_agent.ini</filename> file and add this line:"
msgstr ""
#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:246(para)
msgid "Restart networking services:"
msgstr ""
#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:252(para) ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:352(para)
msgid "Start and permanently enable networking services:"
msgstr ""
#. FIXME: Required on Debian/Ubuntu?
#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:269(para)
msgid "Enable the <systemitem class=\"service\">neutron-ovs-cleanup</systemitem> service. This service starts on boot and ensures that Networking has full control over the creation and management of <literal>tap</literal> devices."
msgstr ""
#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:284(title)
msgid "Install and configure the compute node"
msgstr ""
#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:293(para)
msgid "Start the OpenvSwitch service<phrase os=\"rhel;centos;fedora;opensuse;sles\"> and configure it to start when the system boots</phrase>:"
msgstr ""
#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:304(para)
msgid "Create the integration bridge:"
msgstr ""
#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:308(para)
msgid "All VM communication between the nodes occur through the <literal>br-eth1</literal> bridge."
msgstr ""
#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:317(para)
msgid "Edit the OpenStack Networking <filename>/etc/neutron/neutron.conf</filename> configuration file and add this line:"
msgstr ""
#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:347(para)
msgid "Restart the OpenvSwitch Neutron plug-in agent:"
msgstr ""
#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:363(title)
msgid "Logical network configuration"
msgstr ""
#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:365(para)
msgid "Run these commands on the network node."
msgstr ""
#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:366(para) ./doc/install-guide/section_neutron-single-flat.xml:480(para)
msgid "Ensure that the following environment variables are set. Various clients use these variables to access the Identity Service."
msgstr ""
#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:372(para)
msgid "Create an <filename>adminrc</filename> file that contains these lines:"
msgstr ""
#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:381(para)
msgid "Export the environment variables in the <filename>adminrc</filename> file:"
msgstr ""
#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:386(para)
msgid "The <literal>admin</literal> tenant can define resources that other tenants can use but cannot modify. These resources are a provider network and its associated router."
msgstr ""
#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:390(para)
msgid "The <literal>admin</literal> user creates a network and subnet on behalf of <literal>tenant_A</literal>."
msgstr ""
#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:392(para)
msgid "A <literal>tenant_A</literal> user can also complete these steps."
msgstr ""
#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:395(title)
msgid "Configure internal networking"
msgstr ""
#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:397(para)
msgid "Get the <literal>tenant_A</literal> tenant ID:"
msgstr ""
#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:402(para)
msgid "Create the <literal>net1</literal> internal network for the <literal>tenant_A</literal> tenant:"
msgstr ""
#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:423(para)
msgid "Create a subnet on the <literal>net1</literal> network and store its ID in a variable:"
msgstr ""
#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:443(replaceable)
msgid "c395cb5d-ba03-41ee-8a12-7e792d51a167"
msgstr ""
#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:445(para) ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:473(para)
msgid "The <literal>id</literal> value will be different on your system."
msgstr ""
#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:450(para)
msgid "A user with the <literal>admin</literal> role in the <literal>admin</literal> tenant must complete these steps."
msgstr ""
#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:454(title)
msgid "Configure the router and external networking"
msgstr ""
#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:457(para)
msgid "Create a <literal>router1</literal> router and store its ID in the <literal>ROUTER_ID</literal> variable:"
msgstr ""
#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:471(replaceable)
msgid "685f64e7-a020-4fdf-a8ad-e41194ae124b"
msgstr ""
#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:477(para)
msgid "The <parameter>--tenant-id</parameter> parameter is not specified, so this router is assigned to the <literal>admin</literal> tenant."
msgstr ""
#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:484(para)
msgid "Add an interface to the <literal>router1</literal> router and attach it to the subnet from <literal>net1</literal>:"
msgstr ""
#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:491(para)
msgid "You can repeat this step to add interfaces for networks that belong to other tenants."
msgstr ""
#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:497(para)
msgid "Create the <literal>ext_net</literal> external network and store its ID in a the <literal>EXTERNAL_NETWORK_ID</literal> variable:"
msgstr ""
#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:519(replaceable)
msgid "8858732b-0400-41f6-8e5c-25590e67ffeb"
msgstr ""
#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:522(para)
msgid "Create the subnet for floating IPs."
msgstr ""
#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:524(para)
msgid "The DHCP service is disabled for this subnet."
msgstr ""
#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:547(para)
msgid "Set the gateway for the router to the external network:"
msgstr ""
#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:553(para)
msgid "A user from <literal>tenant_A</literal> completes these steps, so the credentials in the environment variables are different than those in the previous procedure."
msgstr ""
#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:557(title)
msgid "Allocate floating IP addresses"
msgstr ""
#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:559(para)
msgid "You can associate a floating IP address with a VM after it starts. Store the port ID that was allocated for the VM in the <literal>PORT_ID</literal> variable:"
msgstr ""
#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:569(replaceable)
msgid "1cdc671d-a296-4476-9a75-f9ca1d92fd26"
msgstr ""
#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:575(replaceable)
msgid "9aa47099-b87b-488c-8c1d-32f993626a30"
msgstr ""
#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:578(para)
msgid "Allocate a floating IP and store its ID in the <literal>FLOATING_ID</literal> variable:"
msgstr ""
#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:593(replaceable)
msgid "7.7.7.131"
msgstr ""
#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:596(para)
msgid "Associate the floating IP with the port for the VM:"
msgstr ""
#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:602(para)
msgid "Show the floating IP:"
msgstr ""
#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:617(para)
msgid "Test the floating IP:"
msgstr ""
#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:626(title)
msgid "Use case: provider router with private networks"
msgstr ""
#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:627(para)
msgid "This use case provides each tenant with one or more private networks that connect to the outside world through an OpenStack Networking router. When each tenant gets exactly one network, this architecture maps to the same logical topology as the VlanManager in Compute (although of course, Networking does not require VLANs). Using the Networking API, the tenant can only see a network for each private network assigned to that tenant. The router object in the API is created and owned by the cloud administrator."
msgstr ""
#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:637(para)
msgid "This model supports assigning public addresses to VMs by using <glossterm baseform=\"floating IP\">floating IPs</glossterm>; the router maps public addresses from the external network to fixed IPs on private networks. Hosts without floating IPs can still create outbound connections to the external network because the provider router performs SNAT to the router's external IP. The IP address of the physical router is used as the <literal>gateway_ip</literal> of the external network subnet, so the provider has a default router for Internet traffic."
msgstr ""
#: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml:648(para)
msgid "The router provides L3 connectivity among private networks. Tenants can reach instances for other tenants (unless you use additional filtering, such as, security groups). With a single router, tenant networks cannot use overlapping IPs. To resolve this issue, the administrator can create private networks on behalf of the tenants."
msgstr ""
#: ./doc/install-guide/ch_nova.xml:7(title)
msgid "Configure Compute services"
msgstr ""
#: ./doc/install-guide/section_ceilometer-cinder.xml:7(title)
msgid "Add the Block Storage service agent for Telemetry"
msgstr ""
#: ./doc/install-guide/section_ceilometer-cinder.xml:10(para)
msgid "To retrieve volume samples, you must configure the Block Storage service to send notifications to the bus."
msgstr ""
#: ./doc/install-guide/section_ceilometer-cinder.xml:13(para)
msgid "Edit <filename>/etc/cinder/cinder.conf</filename> and add in the <literal>[DEFAULT]</literal> section on the controller and volume nodes:"
msgstr ""
#: ./doc/install-guide/section_ceilometer-cinder.xml:19(para)
msgid "Run the following commands on the controller and volume nodes:"
msgstr ""
#: ./doc/install-guide/section_ceilometer-cinder.xml:26(para)
msgid "Restart the Block Storage services with their new settings."
msgstr ""
#: ./doc/install-guide/section_ceilometer-cinder.xml:28(para)
msgid "On the controller node:"
msgstr ""
#: ./doc/install-guide/section_ceilometer-cinder.xml:33(para)
msgid "On the volume node:"
msgstr ""
#: ./doc/install-guide/app_reserved_uids.xml:6(title) ./doc/install-guide/app_reserved_uids.xml:24(caption)
msgid "Reserved user IDs"
msgstr ""
#: ./doc/install-guide/app_reserved_uids.xml:8(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/install-guide/app_reserved_uids.xml:16(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/install-guide/app_reserved_uids.xml:27(th)
msgid "Name"
msgstr ""
#: ./doc/install-guide/app_reserved_uids.xml:29(th)
msgid "ID"
msgstr ""
#: ./doc/install-guide/app_reserved_uids.xml:35(td)
msgid "ceilometer"
msgstr ""
#: ./doc/install-guide/app_reserved_uids.xml:36(td)
msgid "OpenStack Ceilometer Daemons"
msgstr ""
#: ./doc/install-guide/app_reserved_uids.xml:37(td)
msgid "166"
msgstr ""
#: ./doc/install-guide/app_reserved_uids.xml:38(td) ./doc/install-guide/app_reserved_uids.xml:44(td) ./doc/install-guide/app_reserved_uids.xml:50(td) ./doc/install-guide/app_reserved_uids.xml:56(td) ./doc/install-guide/app_reserved_uids.xml:62(td) ./doc/install-guide/app_reserved_uids.xml:68(td) ./doc/install-guide/app_reserved_uids.xml:75(td) ./doc/install-guide/app_reserved_uids.xml:81(td) ./doc/install-guide/app_reserved_uids.xml:87(td)
msgid "Assigned during package installation"
msgstr ""
#: ./doc/install-guide/app_reserved_uids.xml:41(td)
msgid "cinder"
msgstr ""
#: ./doc/install-guide/app_reserved_uids.xml:42(td)
msgid "OpenStack Cinder Daemons"
msgstr ""
#: ./doc/install-guide/app_reserved_uids.xml:43(td)
msgid "165"
msgstr ""
#: ./doc/install-guide/app_reserved_uids.xml:47(td)
msgid "glance"
msgstr ""
#: ./doc/install-guide/app_reserved_uids.xml:48(td)
msgid "OpenStack Glance Daemons"
msgstr ""
#: ./doc/install-guide/app_reserved_uids.xml:49(td)
msgid "161"
msgstr ""
#: ./doc/install-guide/app_reserved_uids.xml:53(td)
msgid "heat"
msgstr ""
#: ./doc/install-guide/app_reserved_uids.xml:54(td)
msgid "OpenStack Heat Daemons"
msgstr ""
#: ./doc/install-guide/app_reserved_uids.xml:55(td)
msgid "187"
msgstr ""
#: ./doc/install-guide/app_reserved_uids.xml:59(td)
msgid "keystone"
msgstr ""
#: ./doc/install-guide/app_reserved_uids.xml:60(td)
msgid "OpenStack Keystone Daemons"
msgstr ""
#: ./doc/install-guide/app_reserved_uids.xml:61(td)
msgid "163"
msgstr ""
#: ./doc/install-guide/app_reserved_uids.xml:65(td)
msgid "neutron"
msgstr ""
#: ./doc/install-guide/app_reserved_uids.xml:66(td)
msgid "OpenStack Neutron Daemons"
msgstr ""
#: ./doc/install-guide/app_reserved_uids.xml:67(td)
msgid "164"
msgstr ""
#: ./doc/install-guide/app_reserved_uids.xml:71(td)
msgid "nova"
msgstr ""
#: ./doc/install-guide/app_reserved_uids.xml:72(td)
msgid "OpenStack Nova Daemons"
msgstr ""
#: ./doc/install-guide/app_reserved_uids.xml:73(td)
msgid "162"
msgstr ""
#: ./doc/install-guide/app_reserved_uids.xml:74(td)
msgid "96"
msgstr ""
#: ./doc/install-guide/app_reserved_uids.xml:78(td)
msgid "swift"
msgstr ""
#: ./doc/install-guide/app_reserved_uids.xml:79(td)
msgid "OpenStack Swift Daemons"
msgstr ""
#: ./doc/install-guide/app_reserved_uids.xml:80(td)
msgid "160"
msgstr ""
#: ./doc/install-guide/app_reserved_uids.xml:84(td)
msgid "trove"
msgstr ""
#: ./doc/install-guide/app_reserved_uids.xml:85(td)
msgid "OpenStack Trove Daemons"
msgstr ""
#: ./doc/install-guide/app_reserved_uids.xml:86(td)
msgid "Unknown FIXME"
msgstr ""
#: ./doc/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/install-guide/section_neutron-ovs-controller-node.xml:8(para)
msgid "By default, the <literal>system-config-firewall</literal> automated firewall configuration tool is in place on RHEL. This graphical interface (and a curses-style interface with <literal>-tui</literal> 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 <guilabel>Enabled</guilabel> check box."
msgstr ""
#: ./doc/install-guide/section_neutron-ovs-controller-node.xml:18(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/install-guide/section_neutron-ovs-controller-node.xml:25(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/install-guide/section_neutron-ovs-controller-node.xml:32(para)
msgid "Connect to the MySQL database as the root user, create the <literal>neutron</literal> database, and grant the proper access to it:"
msgstr ""
#: ./doc/install-guide/section_neutron-ovs-controller-node.xml:43(para)
msgid "Create the required user, service, and endpoint so that Networking can interface with the Identity Service."
msgstr ""
#: ./doc/install-guide/section_neutron-ovs-controller-node.xml:45(para)
msgid "Create a <literal>neutron</literal> user:"
msgstr ""
#: ./doc/install-guide/section_neutron-ovs-controller-node.xml:47(para)
msgid "Add the user role to the neutron user:"
msgstr ""
#: ./doc/install-guide/section_neutron-ovs-controller-node.xml:49(para)
msgid "Create the neutron service:"
msgstr ""
#: ./doc/install-guide/section_neutron-ovs-controller-node.xml:52(para)
msgid "Create a Networking endpoint:"
msgstr ""
#: ./doc/install-guide/section_neutron-ovs-controller-node.xml:61(title)
msgid "Install and configure server component"
msgstr ""
#: ./doc/install-guide/section_neutron-ovs-controller-node.xml:63(para)
msgid "Install the server component of Networking and any dependencies."
msgstr ""
#: ./doc/install-guide/section_neutron-ovs-controller-node.xml:69(para) ./doc/install-guide/section_neutron-single-flat.xml:191(para)
msgid "Configure Networking to connect to the database:"
msgstr ""
#: ./doc/install-guide/section_neutron-ovs-controller-node.xml:74(para)
msgid "Configure Networking to use your MySQL database. Edit the <filename>/etc/neutron/neutron.conf</filename> file and add the following key under the <literal>[database]</literal> section. Replace <replaceable>NEUTRON_DBPASS</replaceable> with the password you chose for the Neutron database."
msgstr ""
#: ./doc/install-guide/section_neutron-ovs-controller-node.xml:84(para)
msgid "Configure Networking to use <systemitem class=\"service\">keystone</systemitem> as the Identity Service for authentication:"
msgstr ""
#: ./doc/install-guide/section_neutron-ovs-controller-node.xml:89(para) ./doc/install-guide/section_neutron-ovs-network-node.xml:85(para) ./doc/install-guide/section_neutron-ovs-network-node.xml:119(para)
msgid "Set the <literal>auth_strategy</literal> configuration key to <literal>keystone</literal> in the <literal>DEFAULT</literal> section of the file:"
msgstr ""
#: ./doc/install-guide/section_neutron-ovs-controller-node.xml:115(para)
msgid "Configure Networking to use <systemitem class=\"service\">keystone</systemitem> as the Identity Service for authentication."
msgstr ""
#: ./doc/install-guide/section_neutron-ovs-controller-node.xml:120(para)
msgid "Edit the <filename>/etc/neutron/neutron.conf</filename> file and add the file and add the following key under the <literal>[DEFAULT]</literal> section."
msgstr ""
#: ./doc/install-guide/section_neutron-ovs-controller-node.xml:127(para)
msgid "Add the following keys under the <literal>[keystone_authtoken]</literal> section. Replace <replaceable>NEUTRON_PASS</replaceable> with the password you chose for the Neutron user in Keystone."
msgstr ""
#: ./doc/install-guide/section_neutron-ovs-controller-node.xml:170(para)
msgid "Configure Networking to use your message broker. Edit the <filename>/etc/neutron/neutron.conf</filename> file and add the following keys under the <literal>[DEFAULT]</literal> section."
msgstr ""
#: ./doc/install-guide/section_neutron-ovs-controller-node.xml:174(para)
msgid "Replace <replaceable>RABBIT_PASS</replaceable> with the password you chose for RabbitMQ."
msgstr ""
#: ./doc/install-guide/section_neutron-ovs-controller-node.xml:184(title)
msgid "Install and configure Open vSwitch (OVS) plug-in"
msgstr ""
#: ./doc/install-guide/section_neutron-ovs-controller-node.xml:190(para)
msgid "Install the Open vSwitch plug-in:"
msgstr ""
#: ./doc/install-guide/section_neutron-ovs-controller-node.xml:196(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 <acronym>OVS</acronym>. Edit the <filename>/etc/neutron/neutron.conf</filename> file:"
msgstr ""
#: ./doc/install-guide/section_neutron-ovs-controller-node.xml:204(para)
msgid "The dedicated controller node does not need to run Open vSwitch or the Open vSwitch agent."
msgstr ""
#: ./doc/install-guide/section_neutron-ovs-controller-node.xml:209(para)
msgid "Configure the <acronym>OVS</acronym> plug-in to use GRE tunneling. Edit the <filename>/etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini</filename> file:"
msgstr ""
#: ./doc/install-guide/section_neutron-ovs-controller-node.xml:222(para)
msgid "Configure Compute to use OpenStack Networking services. Configure the <filename>/etc/nova/nova.conf</filename> file as per instructions below:"
msgstr ""
#: ./doc/install-guide/section_neutron-ovs-controller-node.xml:246(para)
msgid "Configure Compute to use OpenStack Networking services. Edit the <filename>/etc/nova/nova.conf</filename> file:"
msgstr ""
#: ./doc/install-guide/section_neutron-ovs-controller-node.xml:262(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 <systemitem class=\"service\">nova</systemitem> firewall, and because <systemitem class=\"service\">neutron</systemitem> handles the Firewall, you must tell <systemitem class=\"service\">nova</systemitem> not to use one."
msgstr ""
#: ./doc/install-guide/section_neutron-ovs-controller-node.xml:269(para)
msgid "When Networking handles the firewall, the option <code>firewall_driver</code> should be set according to the specified plug-in. For example with <acronym>OVS</acronym>, edit the <filename>/etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini</filename> file:"
msgstr ""
#: ./doc/install-guide/section_neutron-ovs-controller-node.xml:283(para)
msgid "If you do not want to use a firewall in Compute or Networking, set <code>firewall_driver=nova.virt.firewall.NoopFirewallDriver</code> in both config files, and comment out or remove <code>security_group_api=neutron</code> in the <filename>/etc/nova/nova.conf</filename> file, otherwise you may encounter <errortext>ERROR: The server has either erred or is incapable of performing the requested operation. (HTTP 500)</errortext> when issuing <placeholder-1/> commands."
msgstr ""
#: ./doc/install-guide/section_neutron-ovs-controller-node.xml:324(para)
msgid "Restart the Compute and Networking services:"
msgstr ""
#: ./doc/install-guide/section_basics-ntp.xml:6(title)
msgid "Network Time Protocol (NTP)"
msgstr ""
#: ./doc/install-guide/section_basics-ntp.xml:7(para)
msgid "To synchronize services across multiple machines, you must install <glossterm baseform=\"Network Time Protocol (NTP)\">NTP</glossterm>. The examples in this guide configure the controller node as the reference server and any additional nodes to set their time from the controller node."
msgstr ""
#: ./doc/install-guide/section_basics-ntp.xml:12(para)
msgid "Install the <literal>ntp</literal> package on each system running OpenStack services:"
msgstr ""
#: ./doc/install-guide/section_basics-ntp.xml:17(para)
msgid "Set up the NTP server on your controller node so that it receives data by modifying the <filename>ntp.conf</filename> file and restarting the service:"
msgstr ""
#: ./doc/install-guide/section_basics-ntp.xml:25(para)
msgid "It is advised that you configure additional nodes to synchronize their time from the controller node rather than from outside of your LAN. To do so, install the ntp daemon as above, then edit <filename>/etc/ntp.conf</filename> and change the <code>server</code> directive to use the controller node as internet time source."
msgstr ""
#: ./doc/install-guide/section_ceilometer-glance.xml:6(title)
msgid "Configure the Image Service for Telemetry"
msgstr ""
#: ./doc/install-guide/section_ceilometer-glance.xml:9(para)
msgid "To retrieve image samples, you must configure the Image Service to send notifications to the bus."
msgstr ""
#: ./doc/install-guide/section_ceilometer-glance.xml:12(para)
msgid "Edit <filename>/etc/glance/glance-api.conf</filename> and modify the <literal>[DEFAULT]</literal> section:"
msgstr ""
#: ./doc/install-guide/section_ceilometer-glance.xml:31(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/install-guide/section_basics-networking-nova.xml:25(None) ./doc/install-guide/ch_overview.xml:147(None)
msgid "@@image: 'figures/installguide_arch-nova.png'; md5=da24b356516c960a33ab2b4b72840774"
msgstr ""
#: ./doc/install-guide/section_basics-networking-nova.xml:7(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 <glossterm>management network</glossterm>. The compute node contains one network interface on the management network and one on the <glossterm>external network</glossterm>."
msgstr ""
#: ./doc/install-guide/section_basics-networking-nova.xml:14(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/install-guide/section_basics-networking-nova.xml:21(title) ./doc/install-guide/ch_overview.xml:143(title)
msgid "Two-node architecture with legacy networking (nova-network)"
msgstr ""
#: ./doc/install-guide/section_basics-networking-nova.xml:29(para) ./doc/install-guide/section_basics-networking-neutron.xml:33(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 <replaceable>controller</replaceable> name must resolve to <literal>10.0.0.11</literal>, the IP address of the management interface on the controller node."
msgstr ""
#: ./doc/install-guide/section_basics-networking-nova.xml:37(para) ./doc/install-guide/section_basics-networking-neutron.xml:41(para)
msgid "Reconfiguring network interfaces will interrupt network connectivity. We recommend using a local terminal session for these procedures."
msgstr ""
#: ./doc/install-guide/section_basics-networking-nova.xml:44(title) ./doc/install-guide/section_basics-networking-nova.xml:76(title) ./doc/install-guide/section_basics-networking-neutron.xml:48(title) ./doc/install-guide/section_basics-networking-neutron.xml:83(title) ./doc/install-guide/section_basics-networking-neutron.xml:165(title)
msgid "To configure networking:"
msgstr ""
#: ./doc/install-guide/section_basics-networking-nova.xml:46(para) ./doc/install-guide/section_basics-networking-nova.xml:78(para) ./doc/install-guide/section_basics-networking-neutron.xml:50(para) ./doc/install-guide/section_basics-networking-neutron.xml:85(para) ./doc/install-guide/section_basics-networking-neutron.xml:167(para)
msgid "Configure the first interface as the management interface:"
msgstr ""
#: ./doc/install-guide/section_basics-networking-nova.xml:47(para) ./doc/install-guide/section_basics-networking-neutron.xml:51(para)
msgid "IP address: 10.0.0.11"
msgstr ""
#: ./doc/install-guide/section_basics-networking-nova.xml:48(para) ./doc/install-guide/section_basics-networking-nova.xml:80(para) ./doc/install-guide/section_basics-networking-neutron.xml:52(para) ./doc/install-guide/section_basics-networking-neutron.xml:87(para) ./doc/install-guide/section_basics-networking-neutron.xml:94(para) ./doc/install-guide/section_basics-networking-neutron.xml:169(para) ./doc/install-guide/section_basics-networking-neutron.xml:180(para)
msgid "Network mask: 255.255.255.0 (or /24)"
msgstr ""
#: ./doc/install-guide/section_basics-networking-nova.xml:49(para) ./doc/install-guide/section_basics-networking-nova.xml:81(para) ./doc/install-guide/section_basics-networking-neutron.xml:53(para) ./doc/install-guide/section_basics-networking-neutron.xml:88(para) ./doc/install-guide/section_basics-networking-neutron.xml:170(para)
msgid "Default gateway: 10.0.0.1"
msgstr ""
#: ./doc/install-guide/section_basics-networking-nova.xml:53(title) ./doc/install-guide/section_basics-networking-nova.xml:131(title) ./doc/install-guide/section_basics-networking-neutron.xml:57(title) ./doc/install-guide/section_basics-networking-neutron.xml:140(title) ./doc/install-guide/section_basics-networking-neutron.xml:188(title)
msgid "To configure name resolution:"
msgstr ""
#: ./doc/install-guide/section_basics-networking-nova.xml:55(para) ./doc/install-guide/section_basics-networking-neutron.xml:59(para)
msgid "Set the hostname of the node to <code><replaceable>controller</replaceable></code>."
msgstr ""
#: ./doc/install-guide/section_basics-networking-nova.xml:59(para) ./doc/install-guide/section_basics-networking-nova.xml:136(para) ./doc/install-guide/section_basics-networking-neutron.xml:63(para) ./doc/install-guide/section_basics-networking-neutron.xml:145(para) ./doc/install-guide/section_basics-networking-neutron.xml:193(para)
msgid "Edit the <filename>/etc/hosts</filename> file to contain the following:"
msgstr ""
#: ./doc/install-guide/section_basics-networking-nova.xml:67(para) ./doc/install-guide/section_basics-networking-nova.xml:144(para) ./doc/install-guide/section_basics-networking-neutron.xml:74(para) ./doc/install-guide/section_basics-networking-neutron.xml:156(para) ./doc/install-guide/section_basics-networking-neutron.xml:204(para)
msgid "You must remove or comment the line beginning with <literal>127.0.1.1</literal>."
msgstr ""
#: ./doc/install-guide/section_basics-networking-nova.xml:79(para) ./doc/install-guide/section_basics-networking-neutron.xml:168(para)
msgid "IP address: 10.0.0.31"
msgstr ""
#: ./doc/install-guide/section_basics-networking-nova.xml:83(para) ./doc/install-guide/section_basics-networking-neutron.xml:172(para)
msgid "Additional compute nodes should use 10.0.0.32, 10.0.0.33, and so on."
msgstr ""
#: ./doc/install-guide/section_basics-networking-nova.xml:88(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/install-guide/section_basics-networking-nova.xml:91(para)
msgid "Replace <replaceable>INTERFACE_NAME</replaceable> with the actual interface name. For example, <emphasis>eth1</emphasis> or <emphasis>ens224</emphasis>."
msgstr ""
#: ./doc/install-guide/section_basics-networking-nova.xml:96(para) ./doc/install-guide/section_basics-networking-neutron.xml:105(para)
msgid "Edit the <filename>/etc/network/interfaces</filename> file to contain the following:"
msgstr ""
#: ./doc/install-guide/section_basics-networking-nova.xml:105(para) ./doc/install-guide/section_basics-networking-neutron.xml:114(para)
msgid "Edit the <filename>/etc/sysconfig/network-scripts/ifcfg-<replaceable>INTERFACE_NAME</replaceable></filename> file to contain the following:"
msgstr ""
#: ./doc/install-guide/section_basics-networking-nova.xml:108(para) ./doc/install-guide/section_basics-networking-neutron.xml:117(para)
msgid "Do not change the <literal>HWADDR</literal> and <literal>UUID</literal> keys."
msgstr ""
#: ./doc/install-guide/section_basics-networking-nova.xml:116(para) ./doc/install-guide/section_basics-networking-neutron.xml:125(para)
msgid "Edit the <filename>/etc/sysconfig/network/ifcfg-<replaceable>INTERFACE_NAME</replaceable></filename> file to contain the following:"
msgstr ""
#: ./doc/install-guide/section_basics-networking-nova.xml:125(para) ./doc/install-guide/section_basics-networking-neutron.xml:134(para)
msgid "Restart networking:"
msgstr ""
#: ./doc/install-guide/section_basics-networking-nova.xml:133(para) ./doc/install-guide/section_basics-networking-neutron.xml:190(para)
msgid "Set the hostname of the node to <code>compute1</code>."
msgstr ""
#: ./doc/install-guide/section_basics-networking-nova.xml:151(title) ./doc/install-guide/section_basics-networking-neutron.xml:211(title) ./doc/install-guide/section_neutron-initial-networks.xml:228(title)
msgid "Verify connectivity"
msgstr ""
#: ./doc/install-guide/section_basics-networking-nova.xml:152(para) ./doc/install-guide/section_basics-networking-neutron.xml:212(para)
msgid "We recommend that you verify network connectivity to the internet and among the nodes before proceeding further."
msgstr ""
#: ./doc/install-guide/section_basics-networking-nova.xml:156(para) ./doc/install-guide/section_basics-networking-neutron.xml:216(para)
msgid "From the <emphasis>controller</emphasis> node, <placeholder-1/> a site on the internet:"
msgstr ""
#: ./doc/install-guide/section_basics-networking-nova.xml:170(para) ./doc/install-guide/section_basics-networking-neutron.xml:245(para)
msgid "From the <emphasis>controller</emphasis> node, <placeholder-1/> the management interface on the <emphasis>compute</emphasis> node:"
msgstr ""
#: ./doc/install-guide/section_basics-networking-nova.xml:173(replaceable) ./doc/install-guide/section_basics-networking-neutron.xml:248(replaceable)
msgid "compute1"
msgstr ""
#: ./doc/install-guide/section_basics-networking-nova.xml:185(para) ./doc/install-guide/section_basics-networking-neutron.xml:304(para)
msgid "From the <emphasis>compute</emphasis> node, <placeholder-1/> a site on the internet:"
msgstr ""
#: ./doc/install-guide/section_basics-networking-nova.xml:199(para) ./doc/install-guide/section_basics-networking-neutron.xml:318(para)
msgid "From the <emphasis>compute</emphasis> node, <placeholder-1/> the management interface on the <emphasis>controller</emphasis> node:"
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/install-guide/section_basics-networking-neutron.xml:29(None) ./doc/install-guide/ch_overview.xml:98(None)
msgid "@@image: 'figures/installguide_arch-neutron.png'; md5=9b3d2f2e5f9d88d198511ecbca829c6d"
msgstr ""
#: ./doc/install-guide/section_basics-networking-neutron.xml:7(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 <glossterm>management network</glossterm>. The network node contains one network interface on the management network, one on the <glossterm>instance tunnels network</glossterm>, and one on the <glossterm>external network</glossterm>. The compute node contains one network interface on the management network and one on the instance tunnels network."
msgstr ""
#: ./doc/install-guide/section_basics-networking-neutron.xml:17(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/install-guide/section_basics-networking-neutron.xml:25(title) ./doc/install-guide/ch_overview.xml:94(title)
msgid "Three-node architecture with OpenStack Networking (neutron)"
msgstr ""
#: ./doc/install-guide/section_basics-networking-neutron.xml:86(para)
msgid "IP address: 10.0.0.21"
msgstr ""
#: ./doc/install-guide/section_basics-networking-neutron.xml:91(para) ./doc/install-guide/section_basics-networking-neutron.xml:177(para)
msgid "Configure the second interface as the instance tunnels interface:"
msgstr ""
#: ./doc/install-guide/section_basics-networking-neutron.xml:93(para)
msgid "IP address: 10.0.1.21"
msgstr ""
#: ./doc/install-guide/section_basics-networking-neutron.xml:97(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/install-guide/section_basics-networking-neutron.xml:100(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:458(para)
msgid "Replace <replaceable>INTERFACE_NAME</replaceable> with the actual interface name. For example, <emphasis>eth2</emphasis> or <emphasis>ens256</emphasis>."
msgstr ""
#: ./doc/install-guide/section_basics-networking-neutron.xml:142(para)
msgid "Set the hostname of the node to <code>network</code>."
msgstr ""
#: ./doc/install-guide/section_basics-networking-neutron.xml:179(para)
msgid "IP address: 10.0.1.31"
msgstr ""
#: ./doc/install-guide/section_basics-networking-neutron.xml:182(para)
msgid "Additional compute nodes should use 10.0.1.32, 10.0.1.33, and so on."
msgstr ""
#: ./doc/install-guide/section_basics-networking-neutron.xml:230(para)
msgid "From the <emphasis>controller</emphasis> node, <placeholder-1/> the management interface on the <emphasis>network</emphasis> node:"
msgstr ""
#: ./doc/install-guide/section_basics-networking-neutron.xml:233(replaceable)
msgid "network"
msgstr ""
#: ./doc/install-guide/section_basics-networking-neutron.xml:260(para)
msgid "From the <emphasis>network</emphasis> node, <placeholder-1/> a site on the internet:"
msgstr ""
#: ./doc/install-guide/section_basics-networking-neutron.xml:274(para)
msgid "From the <emphasis>network</emphasis> node, <placeholder-1/> the management interface on the <emphasis>controller</emphasis> node:"
msgstr ""
#: ./doc/install-guide/section_basics-networking-neutron.xml:289(para)
msgid "From the <emphasis>network</emphasis> node, <placeholder-1/> the instance tunnels interface on the <emphasis>compute</emphasis> node:"
msgstr ""
#: ./doc/install-guide/section_basics-networking-neutron.xml:333(para)
msgid "From the <emphasis>compute</emphasis> node, <placeholder-1/> the instance tunnels interface on the <emphasis>network</emphasis> node:"
msgstr ""
#: ./doc/install-guide/section_basics-prerequisites.xml:6(title) ./doc/install-guide/object-storage/section_object-storage-install.xml:28(title)
msgid "Before you begin"
msgstr ""
#: ./doc/install-guide/section_basics-prerequisites.xml:7(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 <glossterm>CirrOS</glossterm> instances:"
msgstr ""
#: ./doc/install-guide/section_basics-prerequisites.xml:13(para)
msgid "Controller Node: 1 processor, 2 GB memory, and 5 GB storage"
msgstr ""
#: ./doc/install-guide/section_basics-prerequisites.xml:17(para)
msgid "Network Node: 1 processor, 512 MB memory, and 5 GB storage"
msgstr ""
#: ./doc/install-guide/section_basics-prerequisites.xml:21(para)
msgid "Compute Node: 1 processor, 2 GB memory, and 10 GB storage"
msgstr ""
#: ./doc/install-guide/section_basics-prerequisites.xml:25(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/install-guide/section_basics-prerequisites.xml:32(para)
msgid "A single disk partition on each node works for most basic installations. However, you should consider <glossterm>Logical Volume Manager (LVM)</glossterm> for installations with optional services such as Block Storage."
msgstr ""
#: ./doc/install-guide/section_basics-prerequisites.xml:37(para)
msgid "Many users build their test environments on <glossterm baseform=\"virtual machine (VM)\">virtual machines (VMs)</glossterm>. The primary benefits of VMs include the following:"
msgstr ""
#: ./doc/install-guide/section_basics-prerequisites.xml:43(para)
msgid "One physical server can support multiple nodes, each with almost any number of network interfaces."
msgstr ""
#: ./doc/install-guide/section_basics-prerequisites.xml:47(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/install-guide/section_basics-prerequisites.xml:52(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/install-guide/section_basics-prerequisites.xml:56(para)
msgid "If you choose to install on VMs, make sure your hypervisor permits <glossterm>promiscuous mode</glossterm> on the <glossterm>external network</glossterm>."
msgstr ""
#: ./doc/install-guide/section_basics-prerequisites.xml:60(para)
msgid "For more information about system requirements, see the <link href=\"http://docs.openstack.org/ops/\">OpenStack Operations Guide</link>."
msgstr ""
#: ./doc/install-guide/ch_trove.xml:6(title)
msgid "Add the Database service"
msgstr ""
#: ./doc/install-guide/ch_trove.xml:7(para)
msgid "Use the <glossterm baseform=\"Database Service\">Database module</glossterm> to create cloud database resources. The integrated project name is <glossterm>trove</glossterm>."
msgstr ""
#: ./doc/install-guide/ch_trove.xml:10(para)
msgid "This chapter is a work in progress. It may contain incorrect information, and will be updated frequently."
msgstr ""
#: ./doc/install-guide/section_neutron-ovs-network-node.xml:6(title) ./doc/install-guide/section_neutron-ml2-network-node.xml:6(title)
msgid "Configure network node"
msgstr ""
#: ./doc/install-guide/section_neutron-ovs-network-node.xml:8(para)
msgid "Before you start, set up a machine as a dedicated network node. Dedicated network nodes have a <replaceable>MGMT_INTERFACE</replaceable> NIC, a <replaceable>DATA_INTERFACE</replaceable> NIC, and an <replaceable>EXTERNAL_INTERFACE</replaceable> NIC."
msgstr ""
#: ./doc/install-guide/section_neutron-ovs-network-node.xml:13(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/install-guide/section_neutron-ovs-network-node.xml:20(para)
msgid "By default, the <literal>system-config-firewall</literal> automated firewall configuration tool is in place on RHEL. This graphical interface (and a curses-style interface with <literal>-tui</literal> 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 <guilabel>Enabled</guilabel> check box."
msgstr ""
#: ./doc/install-guide/section_neutron-ovs-network-node.xml:29(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/install-guide/section_neutron-ovs-network-node.xml:35(title)
msgid "Install agents and configure common components"
msgstr ""
#: ./doc/install-guide/section_neutron-ovs-network-node.xml:37(para)
msgid "Install the Networking packages and any dependencies."
msgstr ""
#: ./doc/install-guide/section_neutron-ovs-network-node.xml:45(para)
msgid "Respond to prompts for <link linkend=\"debconf-dbconfig-common\">database management</link>, <link linkend=\"debconf-keystone_authtoken\"><literal>[keystone_authtoken]</literal> settings</link>, <link linkend=\"debconf-rabbitqm\">RabbitMQ credentials</link> and <link linkend=\"debconf-api-endpoints\">API endpoint</link> registration."
msgstr ""
#: ./doc/install-guide/section_neutron-ovs-network-node.xml:56(para)
msgid "Configure Networking agents to start at boot time:"
msgstr ""
#: ./doc/install-guide/section_neutron-ovs-network-node.xml:61(para)
msgid "Enable packet forwarding and disable packet destination filtering so that the network node can coordinate traffic for the VMs. Edit the <filename>/etc/sysctl.conf</filename> file, as follows:"
msgstr ""
#: ./doc/install-guide/section_neutron-ovs-network-node.xml:68(para)
msgid "Use the <placeholder-1/> command to ensure the changes made to the <filename>/etc/sysctl.conf</filename> file take effect:"
msgstr ""
#: ./doc/install-guide/section_neutron-ovs-network-node.xml:73(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/install-guide/section_neutron-ovs-network-node.xml:152(para)
msgid "Configure the <application>RabbitMQ</application> access. Edit the <filename>/etc/neutron/neutron.conf</filename> file to modify the following parameters in the <literal>DEFAULT</literal> section."
msgstr ""
#: ./doc/install-guide/section_neutron-ovs-network-node.xml:175(title)
msgid "Install and configure the Open vSwitch (OVS) plug-in"
msgstr ""
#: ./doc/install-guide/section_neutron-ovs-network-node.xml:188(para)
msgid "Start Open vSwitch:"
msgstr ""
#: ./doc/install-guide/section_neutron-ovs-network-node.xml:192(para)
msgid "And configure it to start when the system boots:"
msgstr ""
#: ./doc/install-guide/section_neutron-ovs-network-node.xml:198(para)
msgid "No matter which networking technology you use, you must add the <literal>br-int</literal> integration bridge, which connects to the VMs, and the <literal>br-ex</literal> external bridge, which connects to the outside world."
msgstr ""
#: ./doc/install-guide/section_neutron-ovs-network-node.xml:207(para)
msgid "Add a <glossterm>port</glossterm> (connection) from the <replaceable>EXTERNAL_INTERFACE</replaceable> interface to <literal>br-ex</literal> interface:"
msgstr ""
#: ./doc/install-guide/section_neutron-ovs-network-node.xml:210(replaceable) ./doc/install-guide/section_neutron-ovs-network-node.xml:220(replaceable)
msgid "EXTERNAL_INTERFACE"
msgstr ""
#: ./doc/install-guide/section_neutron-ovs-network-node.xml:212(para)
msgid "The host must have an IP address associated with an interface other than <replaceable>EXTERNAL_INTERFACE</replaceable>, and your remote terminal session must be associated with this other IP address."
msgstr ""
#: ./doc/install-guide/section_neutron-ovs-network-node.xml:217(para)
msgid "If you associate an IP address with <replaceable>EXTERNAL_INTERFACE</replaceable>, that IP address stops working after you issue the <placeholder-1/> command. If you associate a remote terminal session with that IP address, you lose connectivity with the host."
msgstr ""
#: ./doc/install-guide/section_neutron-ovs-network-node.xml:223(para)
msgid "For more details about this behavior, see the <emphasis>Configuration Problems</emphasis> section of the <link href=\"http://git.openvswitch.org/cgi-bin/gitweb.cgi?p=openvswitch;a=blob_plain;f=FAQ;hb=HEAD\">Open vSwitch FAQ</link>."
msgstr ""
#: ./doc/install-guide/section_neutron-ovs-network-node.xml:229(para)
msgid "Configure the <replaceable>EXTERNAL_INTERFACE</replaceable> without an IP address and in promiscuous mode. Additionally, you must set the newly created <literal>br-ex</literal> interface to have the IP address that formerly belonged to <replaceable>EXTERNAL_INTERFACE</replaceable>."
msgstr ""
#: ./doc/install-guide/section_neutron-ovs-network-node.xml:236(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/install-guide/section_neutron-ovs-network-node.xml:241(para)
msgid "Edit the <filename>/etc/sysconfig/network-scripts/ifcfg-EXTERNAL_INTERFACE</filename> file:"
msgstr ""
#: ./doc/install-guide/section_neutron-ovs-network-node.xml:250(para)
msgid "Create and edit the <filename>/etc/sysconfig/network-scripts/ifcfg-br-ex</filename> file:"
msgstr ""
#: ./doc/install-guide/section_neutron-ovs-network-node.xml:262(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 <acronym>OVS</acronym> and namespaces. Edit the <filename>/etc/neutron/l3_agent.ini</filename> and <filename>/etc/neutron/dhcp_agent.ini</filename> files, respectively:"
msgstr ""
#: ./doc/install-guide/section_neutron-ovs-network-node.xml:272(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 <filename>/etc/neutron/l3_agent.ini</filename> and <filename>/etc/neutron/dhcp_agent.ini</filename> files, respectively:"
msgstr ""
#: ./doc/install-guide/section_neutron-ovs-network-node.xml:279(para)
msgid "Edit the <filename>/etc/neutron/neutron.conf</filename> file to disable overlapping IP addresses:"
msgstr ""
#: ./doc/install-guide/section_neutron-ovs-network-node.xml:282(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/install-guide/section_neutron-ovs-network-node.xml:285(para)
msgid "You must complete additional steps after you create the initial Neutron virtual networks and router."
msgstr ""
#: ./doc/install-guide/section_neutron-ovs-network-node.xml:291(para)
msgid "Similarly, you must also tell Neutron core to use <acronym>OVS</acronym>. Edit the <filename>/etc/neutron/neutron.conf</filename> file:"
msgstr ""
#: ./doc/install-guide/section_neutron-ovs-network-node.xml:298(para)
msgid "Configure a firewall plug-in. If you do not wish to enforce firewall rules, called <glossterm baseform=\"security group\">security groups</glossterm> by OpenStack, you can use <literal>neutron.agent.firewall.NoopFirewall</literal>. 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 <filename>/etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini</filename> file:"
msgstr ""
#: ./doc/install-guide/section_neutron-ovs-network-node.xml:325(para)
msgid "Configure the <acronym>OVS</acronym> plug-in to use GRE tunneling, the <literal>br-int</literal> integration bridge, the <literal>br-tun</literal> tunneling bridge, and a local IP for the <replaceable>DATA_INTERFACE</replaceable> tunnel IP. Edit the <filename>/etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini</filename> file:"
msgstr ""
#: ./doc/install-guide/section_neutron-ovs-network-node.xml:344(title)
msgid "Configure the agents"
msgstr ""
#: ./doc/install-guide/section_neutron-ovs-network-node.xml:346(para)
msgid "To perform DHCP on the software-defined networks, Networking supports several different plug-ins. However, in general, you use the <application>dnsmasq</application> plug-in."
msgstr ""
#: ./doc/install-guide/section_neutron-ovs-network-node.xml:349(para)
msgid "Configure the <filename>/etc/neutron/dhcp_agent.ini</filename> file:"
msgstr ""
#: ./doc/install-guide/section_neutron-ovs-network-node.xml:357(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/install-guide/section_neutron-ovs-network-node.xml:361(para)
msgid "On the controller, edit the <filename>/etc/nova/nova.conf</filename> file to define a secret key that will be shared between the Compute service and the Networking metadata agent."
msgstr ""
#: ./doc/install-guide/section_neutron-ovs-network-node.xml:365(para)
msgid "Add to the <literal>[DEFAULT]</literal> section:"
msgstr ""
#: ./doc/install-guide/section_neutron-ovs-network-node.xml:369(replaceable) ./doc/install-guide/section_neutron-ovs-network-node.xml:375(replaceable) ./doc/install-guide/section_neutron-ovs-network-node.xml:395(replaceable) ./doc/install-guide/section_neutron-ovs-network-node.xml:411(replaceable)
msgid "METADATA_PASS"
msgstr ""
#: ./doc/install-guide/section_neutron-ovs-network-node.xml:371(para)
msgid "Set the <literal>neutron_metadata_proxy_shared_secret</literal> key:"
msgstr ""
#: ./doc/install-guide/section_neutron-ovs-network-node.xml:378(para)
msgid "Restart the <systemitem class=\"service\">nova-api</systemitem> service:"
msgstr ""
#: ./doc/install-guide/section_neutron-ovs-network-node.xml:382(para)
msgid "On the network node, modify the metadata agent configuration."
msgstr ""
#: ./doc/install-guide/section_neutron-ovs-network-node.xml:384(para)
msgid "Edit the <filename>/etc/neutron/metadata_agent.ini</filename> file and modify the <literal>[DEFAULT]</literal> section:"
msgstr ""
#: ./doc/install-guide/section_neutron-ovs-network-node.xml:396(para) ./doc/install-guide/section_neutron-ovs-network-node.xml:426(para)
msgid "Set the required keys:"
msgstr ""
#: ./doc/install-guide/section_neutron-ovs-network-node.xml:413(para)
msgid "The value of <literal>auth_region</literal> is case-sensitive and must match the endpoint region defined in Keystone."
msgstr ""
#: ./doc/install-guide/section_neutron-ovs-network-node.xml:418(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/install-guide/section_neutron-ovs-network-node.xml:422(para)
msgid "Add this statement to the <literal>[DEFAULT]</literal> section:"
msgstr ""
#: ./doc/install-guide/section_nova-networking-controller-node.xml:6(para)
msgid "Legacy networking primarily involves compute nodes. However, you must configure the controller node to use it."
msgstr ""
#: ./doc/install-guide/section_debconf-concepts.xml:7(title)
msgid "debconf concepts"
msgstr ""
#: ./doc/install-guide/section_debconf-concepts.xml:8(para)
msgid "This chapter explains how to use the Debian <systemitem class=\"library\">debconf</systemitem> and <systemitem class=\"library\">dbconfig-common</systemitem> packages to configure OpenStack services. These packages enable users to perform configuration tasks. When users install OpenStack packages, <package>debconf</package> 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 <placeholder-1/> program."
msgstr ""
#: ./doc/install-guide/section_debconf-concepts.xml:18(para)
msgid "If you are familiar with these packages and pre-seeding, you can proceed to <xref linkend=\"ch_keystone\"/>."
msgstr ""
#: ./doc/install-guide/section_debconf-concepts.xml:21(title)
msgid "The Debian packages"
msgstr ""
#: ./doc/install-guide/section_debconf-concepts.xml:22(para)
msgid "The rules described here are from the <link href=\"http://www.debian.org/doc/debian-policy/\"><citetitle>Debian Policy Manual</citetitle></link>. If any rule described in this chapter is not respected, you have found a serious bug that must be fixed."
msgstr ""
#: ./doc/install-guide/section_debconf-concepts.xml:27(para)
msgid "When you install or upgrade a Debian package, all configuration file values are preserved. Using the <systemitem class=\"library\">debconf</systemitem> database as a registry is considered a bug in Debian. If you edit something in any OpenStack configuration file, the <systemitem class=\"library\">debconf</systemitem> 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/install-guide/section_debconf-concepts.xml:36(para)
msgid "To opt out of using the <systemitem class=\"library\">debconf</systemitem> package, run the <placeholder-1/> command and select non-interactive mode:"
msgstr ""
#: ./doc/install-guide/section_debconf-concepts.xml:41(para)
msgid "Then, <systemitem class=\"library\">debconf</systemitem> does not prompt you."
msgstr ""
#: ./doc/install-guide/section_debconf-concepts.xml:43(para)
msgid "Another way to disable the <systemitem class=\"library\">debconf</systemitem> package is to prefix the <placeholder-1/> command with <literal>DEBIAN_FRONTEND=noninteractive</literal>, as follows:"
msgstr ""
#: ./doc/install-guide/section_debconf-concepts.xml:49(para)
msgid "If you configure a package with <systemitem class=\"library\">debconf</systemitem> incorrectly, you can re-configure it, as follows:"
msgstr ""
#: ./doc/install-guide/section_debconf-concepts.xml:52(replaceable)
msgid "PACKAGE-NAME"
msgstr ""
#: ./doc/install-guide/section_debconf-concepts.xml:53(para)
msgid "This calls the post-installation script for the <replaceable>PACKAGE-NAME</replaceable> 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/install-guide/section_debconf-concepts.xml:58(para)
msgid "Generally, the <systemitem class=\"library\">-common</systemitem> packages install the configuration files. For example, the <literal>glance-common</literal> package installs the <filename>glance-api.conf</filename> and <filename>glance-registry.conf</filename> files. So, for the Image Service, you must re-configure the <literal>glance-common</literal> package. The same applies for <literal>cinder-common</literal>, <literal>nova-common</literal>, and <literal>heat-common</literal> packages."
msgstr ""
#: ./doc/install-guide/section_debconf-concepts.xml:68(para)
msgid "In <systemitem class=\"library\">debconf</systemitem>, the higher the priority for a screen, the greater the chance that the user sees that screen. If a <systemitem class=\"library\">debconf</systemitem> screen has <literal>medium</literal> priority and you configure the Debian system to show only <literal>critical</literal> prompts, which is the default in Debian, the user does not see that <systemitem class=\"library\">debconf</systemitem> screen. Instead, the default for the related package is used. In the Debian OpenStack packages, a number of <systemitem class=\"library\">debconf</systemitem> screens are set with <literal>medium</literal> priority. Consequently, if you want to respond to all <systemitem class=\"library\">debconf</systemitem> screens from the Debian OpenStack packages, you must run the following command and select the <literal>medium</literal> priority before you install any packages:"
msgstr ""
#: ./doc/install-guide/section_debconf-concepts.xml:87(para)
msgid "The packages do not require pre-depends. If <systemitem class=\"library\">dbconfig-common</systemitem> is already installed on the system, the user sees all prompts. However, you cannot define the order in which the <systemitem class=\"library\">debconf</systemitem> screens appear. The user must make sense of it even if the prompts appear in an illogical order."
msgstr ""
#: ./doc/install-guide/section_ceilometer-swift.xml:6(title)
msgid "Configure the Object Storage service for Telemetry"
msgstr ""
#: ./doc/install-guide/section_ceilometer-swift.xml:9(para)
msgid "To retrieve object store statistics, the Telemetry service needs access to Object Storage with the <literal>ResellerAdmin</literal> role. Give this role to your <literal>os_username</literal> user for the <literal>os_tenant_name</literal> tenant:"
msgstr ""
#: ./doc/install-guide/section_ceilometer-swift.xml:23(replaceable)
msgid "462fa46c13fd4798a95a3bfbe27b5e54"
msgstr ""
#: ./doc/install-guide/section_ceilometer-swift.xml:26(para)
msgid "You must also add the Telemetry middleware to Object Storage to handle incoming and outgoing traffic. Add these lines to the <filename>/etc/swift/proxy-server.conf</filename> file:"
msgstr ""
#: ./doc/install-guide/section_ceilometer-swift.xml:35(para)
msgid "Add <literal>ceilometer</literal> to the <literal>pipeline</literal> parameter of that same file:"
msgstr ""
#: ./doc/install-guide/section_ceilometer-swift.xml:41(para) ./doc/install-guide/section_heat-install.xml:180(para) ./doc/install-guide/section_ceilometer-nova.xml:137(para)
msgid "Restart the service with its new settings:"
msgstr ""
#: ./doc/install-guide/section_debconf-preseeding.xml:6(title)
msgid "Pre-seed debconf prompts"
msgstr ""
#: ./doc/install-guide/section_debconf-preseeding.xml:7(para)
msgid "You can pre-seed all <systemitem class=\"library\">debconf</systemitem> prompts. To pre-seed means to store responses in the <package>debconf</package> database so that <package>debconf</package> 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/install-guide/section_debconf-preseeding.xml:14(para)
msgid "The following example shows how to pre-seed an automated MySQL Server installation:"
msgstr ""
#: ./doc/install-guide/section_debconf-preseeding.xml:16(replaceable) ./doc/install-guide/section_debconf-preseeding.xml:17(replaceable) ./doc/install-guide/section_debconf-preseeding.xml:19(replaceable)
msgid "MYSQL_PASSWORD"
msgstr ""
#: ./doc/install-guide/section_debconf-preseeding.xml:23(para)
msgid "The <code>seen true</code> option tells <package>debconf</package> that a specified screen was already seen by the user so do not show it again. This option is useful for upgrades."
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/install-guide/section_neutron-single-flat.xml:22(None)
msgid "@@image: '../common/figures/demo_flat_install.png'; md5=27b45d5871859ff4951c92df7c8763d8"
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/install-guide/section_neutron-single-flat.xml:623(None)
msgid "@@image: '../common/figures/UseCase-SingleFlat.png'; md5=bdd61f2967fb1a55e4f50d766db7b113"
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/install-guide/section_neutron-single-flat.xml:639(None)
msgid "@@image: '../common/figures/UseCase-MultiFlat.png'; md5=289e38a7a13a2a4413e5a1e62ce55b3e"
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/install-guide/section_neutron-single-flat.xml:661(None)
msgid "@@image: '../common/figures/UseCase-MixedFlatPrivate.png'; md5=8da4ceb5a1e5a2357394478645af7449"
msgstr ""
#: ./doc/install-guide/section_neutron-single-flat.xml:6(title)
msgid "Single flat network"
msgstr ""
#: ./doc/install-guide/section_neutron-single-flat.xml:7(para)
msgid "This section describes how to install the OpenStack Networking service and its components for a single flat network use case."
msgstr ""
#: ./doc/install-guide/section_neutron-single-flat.xml:10(para)
msgid "The following diagram shows the set up. For simplicity, all nodes should have one interface for management traffic and one or more interfaces for traffic to and from VMs. The management network is 100.1.1.0/24 with controller node at 100.1.1.2. The example uses the Open vSwitch plug-in and agent."
msgstr ""
#: ./doc/install-guide/section_neutron-single-flat.xml:16(para)
msgid "You can modify this set up to make use of another supported plug-in and its agent."
msgstr ""
#: ./doc/install-guide/section_neutron-single-flat.xml:25(para)
msgid "The following table describes some nodes in the set up:"
msgstr ""
#: ./doc/install-guide/section_neutron-single-flat.xml:39(para)
msgid "Runs the Networking service, Identity Service, and Compute services that are required to deploy VMs (<systemitem class=\"service\">nova-api</systemitem>, <systemitem class=\"service\">nova-scheduler</systemitem>, for example). The node must have at least one network interface, which is connected to the Management Network. The host name is <literal>controller</literal>, which every other node resolves to the IP of the controller node."
msgstr ""
#: ./doc/install-guide/section_neutron-single-flat.xml:52(para)
msgid "The <systemitem class=\"service\">nova-network</systemitem> service should not be running. This is replaced by the OpenStack Networking component, <systemitem class=\"service\">neutron</systemitem>. To delete a network, run this command:"
msgstr ""
#: ./doc/install-guide/section_neutron-single-flat.xml:64(para)
msgid "Note that a network must first be disassociated from a project using the <code>nova network-disassociate</code> command before it can be deleted."
msgstr ""
#: ./doc/install-guide/section_neutron-single-flat.xml:71(td)
msgid "Runs the Networking L2 agent and the Compute services that run VMs (<placeholder-1/> specifically, and optionally other nova-* services depending on configuration). The node must have at least two network interfaces. The first communicates with the controller node through the management network. The second interface handles the VM traffic on the data network. The VM can receive its IP address from the DHCP agent on this network."
msgstr ""
#: ./doc/install-guide/section_neutron-single-flat.xml:85(td)
msgid "Runs Networking L2 agent and the DHCP agent. The DHCP agent allocates IP addresses to the VMs on the network. The node must have at least two network interfaces. The first communicates with the controller node through the management network. The second interface handles the VM traffic on the data network."
msgstr ""
#: ./doc/install-guide/section_neutron-single-flat.xml:101(para)
msgid "The demo assumes the following prerequisites:"
msgstr ""
#: ./doc/install-guide/section_neutron-single-flat.xml:109(para)
msgid "Glance is installed, configured, and running. Additionally, an image must be available."
msgstr ""
#: ./doc/install-guide/section_neutron-single-flat.xml:113(para)
msgid "OpenStack Identity is installed, configured, and running. A Networking user <emphasis role=\"bold\">neutron</emphasis> is in place on tenant <emphasis role=\"bold\">service</emphasis> with password <replaceable>NEUTRON_PASS</replaceable>."
msgstr ""
#: ./doc/install-guide/section_neutron-single-flat.xml:121(para)
msgid "Additional services:"
msgstr ""
#: ./doc/install-guide/section_neutron-single-flat.xml:124(para)
msgid "RabbitMQ is running with the default guest user and password <replaceable>RABBIT_PASS</replaceable>."
msgstr ""
#: ./doc/install-guide/section_neutron-single-flat.xml:129(para)
msgid "Qpid is running with the default guest user and password."
msgstr ""
#: ./doc/install-guide/section_neutron-single-flat.xml:142(para)
msgid "Compute is installed and configured."
msgstr ""
#: ./doc/install-guide/section_neutron-single-flat.xml:155(para)
msgid "Install the Networking server and respond to <systemitem class=\"library\">debconf</systemitem> prompts to configure the database, the <code>keystone_authtoken</code>, and the RabbitMQ credentials."
msgstr ""
#: ./doc/install-guide/section_neutron-single-flat.xml:162(para)
msgid "See <xref linkend=\"neutron-controller-node\"/> for installation instructions."
msgstr ""
#: ./doc/install-guide/section_neutron-single-flat.xml:171(para)
msgid "See <xref linkend=\"neutron-network-node\"/> for database creation details."
msgstr ""
#: ./doc/install-guide/section_neutron-single-flat.xml:177(para)
msgid "If not already configured, update the Networking <filename> /etc/neutron/neutron.conf</filename> configuration file to use the Identity Service, the plug-in, and database configuration:"
msgstr ""
#: ./doc/install-guide/section_neutron-single-flat.xml:194(para) ./doc/install-guide/section_neutron-single-flat.xml:349(para)
msgid "Configure Networking to use your chosen plug-in:"
msgstr ""
#: ./doc/install-guide/section_neutron-single-flat.xml:221(para)
msgid "If not already configured, update the Networking <filename> /etc/neutron/neutron.conf</filename> configuration file to choose a plug-in and Identity Service user as necessary:"
msgstr ""
#: ./doc/install-guide/section_neutron-single-flat.xml:243(para)
msgid "Update the plug-in <filename> /etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini</filename> configuration file with the bridge mappings:"
msgstr ""
#: ./doc/install-guide/section_neutron-single-flat.xml:267(para)
msgid "Install the <systemitem class=\"service\">nova-compute</systemitem> service."
msgstr ""
#: ./doc/install-guide/section_neutron-single-flat.xml:271(para)
msgid "See <xref linkend=\"nova-compute\"/> for installation instructions."
msgstr ""
#: ./doc/install-guide/section_neutron-single-flat.xml:276(para)
msgid "Update the Compute <filename> /etc/nova/nova.conf</filename> configuration file to make use of OpenStack Networking:"
msgstr ""
#: ./doc/install-guide/section_neutron-single-flat.xml:304(para)
msgid "Restart the Compute services"
msgstr ""
#: ./doc/install-guide/section_neutron-single-flat.xml:311(emphasis)
msgid "Compute and Network node - L2 agent"
msgstr ""
#: ./doc/install-guide/section_neutron-single-flat.xml:314(para)
msgid "Install and start Open vSwitch. Then, configure <systemitem class=\"service\">neutron</systemitem> accordingly."
msgstr ""
#: ./doc/install-guide/section_neutron-single-flat.xml:323(para)
msgid "Add the integration bridge to Open vSwitch:"
msgstr ""
#: ./doc/install-guide/section_neutron-single-flat.xml:328(para) ./doc/install-guide/section_neutron-single-flat.xml:420(para)
msgid "Update the Networking <filename> /etc/neutron/neutron.conf</filename> configuration file:"
msgstr ""
#: ./doc/install-guide/section_neutron-single-flat.xml:343(para)
msgid "If not already configured, update the Networking <filename> /etc/neutron/neutron.conf</filename> configuration file to use the plug-in, message queue, and database configuration:"
msgstr ""
#: ./doc/install-guide/section_neutron-single-flat.xml:376(para)
msgid "Update the plug-in <filename> /etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini</filename> configuration file:"
msgstr ""
#: ./doc/install-guide/section_neutron-single-flat.xml:390(para)
msgid "Create a symbolic link from <filename>/etc/neutron/plugin.ini</filename> to <filename>/etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini</filename> or <code>neutron-server</code> will not run:"
msgstr ""
#: ./doc/install-guide/section_neutron-single-flat.xml:395(para)
msgid "Create the <emphasis role=\"bold\">br-eth0</emphasis> network bridge to handle communication between nodes using eth0:"
msgstr ""
#: ./doc/install-guide/section_neutron-single-flat.xml:403(para)
msgid "Restart the OpenStack Networking L2 agent:"
msgstr ""
#: ./doc/install-guide/section_neutron-single-flat.xml:415(para)
msgid "See <xref linkend=\"neutron-network-node\"/> for <emphasis role=\"bold\">generic</emphasis> installation instructions."
msgstr ""
#: ./doc/install-guide/section_neutron-single-flat.xml:431(para)
msgid "If not already configured, update the Networking <filename> /etc/neutron/neutron.conf</filename> configuration file to use the plug-in and message queue."
msgstr ""
#: ./doc/install-guide/section_neutron-single-flat.xml:460(para)
msgid "Ensure that the DHCP agent is using the correct plug-in my changing the configuration in <filename> /etc/neutron/dhcp_agent.ini</filename>:"
msgstr ""
#: ./doc/install-guide/section_neutron-single-flat.xml:468(para)
msgid "Restart the DHCP agent:"
msgstr ""
#: ./doc/install-guide/section_neutron-single-flat.xml:478(para)
msgid "Use the following commands on the network node."
msgstr ""
#: ./doc/install-guide/section_neutron-single-flat.xml:504(para)
msgid "Get the user information:"
msgstr ""
#: ./doc/install-guide/section_neutron-single-flat.xml:517(para)
msgid "Create a internal shared network on the demo tenant ($TENANT_ID is b7445f221cda4f4a8ac7db6b218b1339):"
msgstr ""
#: ./doc/install-guide/section_neutron-single-flat.xml:540(para)
msgid "Create a subnet on the network:"
msgstr ""
#: ./doc/install-guide/section_neutron-single-flat.xml:560(para)
msgid "Create a server for tenant A:"
msgstr ""
#: ./doc/install-guide/section_neutron-single-flat.xml:573(para)
msgid "Ping the server of tenant A:"
msgstr ""
#: ./doc/install-guide/section_neutron-single-flat.xml:579(para)
msgid "Ping the public network within the server of tenant A:"
msgstr ""
#: ./doc/install-guide/section_neutron-single-flat.xml:591(para)
msgid "The 192.168.1.1 is an IP on public network to which the router connects."
msgstr ""
#: ./doc/install-guide/section_neutron-single-flat.xml:596(para)
msgid "Create servers for other tenants with similar commands. Because all VMs share the same subnet, they can access each other."
msgstr ""
#: ./doc/install-guide/section_neutron-single-flat.xml:603(title)
msgid "Use case: single flat network"
msgstr ""
#: ./doc/install-guide/section_neutron-single-flat.xml:604(para)
msgid "The simplest use case is a single network. This is a \"shared\" network, meaning it is visible to all tenants via the Networking API. Tenant VMs have a single NIC, and receive a fixed IP address from the subnet(s) associated with that network. This use case essentially maps to the FlatManager and FlatDHCPManager models provided by Compute. Floating IPs are not supported."
msgstr ""
#: ./doc/install-guide/section_neutron-single-flat.xml:611(para)
msgid "This network type is often created by the OpenStack administrator to map directly to an existing physical network in the data center (called a \"provider network\"). This allows the provider to use a physical router on that data center network as the gateway for VMs to reach the outside world. For each subnet on an external network, the gateway configuration on the physical router must be manually configured outside of OpenStack."
msgstr ""
#: ./doc/install-guide/section_neutron-single-flat.xml:630(title)
msgid "Use case: multiple flat network"
msgstr ""
#: ./doc/install-guide/section_neutron-single-flat.xml:631(para)
msgid "This use case is similar to the above single flat network use case, except that tenants can see multiple shared networks via the Networking API and can choose which network (or networks) to plug into."
msgstr ""
#: ./doc/install-guide/section_neutron-single-flat.xml:645(title)
msgid "Use case: mixed flat and private network"
msgstr ""
#: ./doc/install-guide/section_neutron-single-flat.xml:646(para)
msgid "This use case is an extension of the above Flat Network use cases. In addition to being able to see one or more shared networks via the OpenStack Networking API, tenants can also have access to private per-tenant networks (only visible to tenant users)."
msgstr ""
#: ./doc/install-guide/section_neutron-single-flat.xml:651(para)
msgid "Created VMs can have NICs on any of the shared or private networks that the tenant owns. This enables the creation of multi-tier topologies that use VMs with multiple NICs. It also enables a VM to act as a gateway so that it can provide services such as routing, NAT, and load balancing."
msgstr ""
#: ./doc/install-guide/ch_basics.xml:5(title)
msgid "Basic environment configuration"
msgstr ""
#: ./doc/install-guide/ch_basics.xml:6(para)
msgid "This chapter explains how to configure each node in the <link linkend=\"architecture_example-architectures\">example architectures</link> including the <link linkend=\"example-architecture-with-legacy-networking\"> two-node architecture with legacy networking</link> and <link linkend=\"example-architecture-with-neutron-networking\">three-node architecture with OpenStack Networking (neutron)</link>."
msgstr ""
#: ./doc/install-guide/ch_basics.xml:13(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 <xref linkend=\"object-storage-system-requirements\"/>. However, the dashboard will not work without at least OpenStack Image Service and Compute."
msgstr ""
#: ./doc/install-guide/ch_basics.xml:22(para)
msgid "You must use an account with administrative privileges to configure each node. Either run the commands as the <literal>root</literal> user or configure the <literal>sudo</literal> utility."
msgstr ""
#: ./doc/install-guide/section_cinder-node.xml:6(title)
msgid "Configure a Block Storage service node"
msgstr ""
#: ./doc/install-guide/section_cinder-node.xml:7(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/install-guide/section_cinder-node.xml:10(para) ./doc/install-guide/section_cinder-controller.xml:16(para)
msgid "You can configure OpenStack to use various storage systems. This example uses LVM."
msgstr ""
#: ./doc/install-guide/section_cinder-node.xml:14(para)
msgid "Use the instructions in <xref linkend=\"ch_basics\"/> to configure the system. Note the following differences from the installation instructions for the controller node:"
msgstr ""
#: ./doc/install-guide/section_cinder-node.xml:19(para)
msgid "Set the host name to <literal>block1</literal> and use <literal>10.0.0.41</literal> 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 <filename>/etc/hosts</filename> file on each system."
msgstr ""
#: ./doc/install-guide/section_cinder-node.xml:27(para)
msgid "Follow the instructions in <xref linkend=\"basics-ntp\"/> to synchronize from the controller node."
msgstr ""
#: ./doc/install-guide/section_cinder-node.xml:33(para)
msgid "Install the required LVM packages, if they are not already installed:"
msgstr ""
#: ./doc/install-guide/section_cinder-node.xml:38(para)
msgid "Create the LVM physical and logical volumes. This guide assumes a second disk <literal>/dev/sdb</literal> that is used for this purpose:"
msgstr ""
#: ./doc/install-guide/section_cinder-node.xml:45(para)
msgid "Add a filter entry to the <literal>devices</literal> section in the <filename>/etc/lvm/lvm.conf</filename> file to keep LVM from scanning devices used by virtual machines:"
msgstr ""
#: ./doc/install-guide/section_cinder-node.xml:55(para)
msgid "You must add required physical volumes for LVM on the Block Storage host. Run the <placeholder-1/> command to get a list or required volumes."
msgstr ""
#: ./doc/install-guide/section_cinder-node.xml:59(para)
msgid "Each item in the filter array starts with either an <literal>a</literal> for accept, or an <literal>r</literal> for reject. The physical volumes that are required on the Block Storage host have names that begin with <literal>a</literal>. The array must end with \"<literal>r/.*/</literal>\" to reject any device not listed."
msgstr ""
#: ./doc/install-guide/section_cinder-node.xml:66(para)
msgid "In this example, <literal>/dev/sda1</literal> is the volume where the volumes for the operating system for the node reside, while <literal>/dev/sdb</literal> is the volume reserved for <literal>cinder-volumes</literal>."
msgstr ""
#: ./doc/install-guide/section_cinder-node.xml:72(para)
msgid "After you configure the operating system, install the appropriate packages for the Block Storage service:"
msgstr ""
#: ./doc/install-guide/section_cinder-node.xml:79(para)
msgid "Respond to the <systemitem class=\"library\">debconf</systemitem> prompts about the <link linkend=\"debconf-dbconfig-common\">database management</link>, <link linkend=\"debconf-keystone_authtoken\"><literal>[keystone_authtoken]</literal> settings</link>, and <link linkend=\"debconf-rabbitqm\">RabbitMQ credentials</link>. Make sure to enter the same details as you did for your Block Storage service controller node."
msgstr ""
#: ./doc/install-guide/section_cinder-node.xml:87(para)
msgid "Another screen prompts you for the <systemitem class=\"library\">volume-group</systemitem> to use. The Debian package configuration script detects every active volume group and tries to use the first one it sees, provided that the <systemitem class=\"library\">lvm2</systemitem> package was installed before Block Storage. This should be the case if you configured the volume group first, as this guide recommends."
msgstr ""
#: ./doc/install-guide/section_cinder-node.xml:94(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 <systemitem class=\"service\">cinder-volume</systemitem> package because it is detected automatically. If no <systemitem class=\"library\">volume-group</systemitem> is available when you install <systemitem class=\"service\">cinder-common</systemitem>, you must use <placeholder-1/> to manually configure or re-configure <systemitem class=\"service\">cinder-common</systemitem>."
msgstr ""
#: ./doc/install-guide/section_cinder-node.xml:106(para)
msgid "Copy the <filename>/etc/cinder/cinder.conf</filename> configuration file from the controller, or perform the following steps to set the keystone credentials:"
msgstr ""
#: ./doc/install-guide/section_cinder-node.xml:125(replaceable) ./doc/install-guide/section_cinder-node.xml:137(replaceable) ./doc/install-guide/section_cinder-controller.xml:74(replaceable) ./doc/install-guide/section_cinder-controller.xml:95(replaceable) ./doc/install-guide/section_cinder-controller.xml:107(replaceable)
msgid "CINDER_PASS"
msgstr ""
#: ./doc/install-guide/section_cinder-node.xml:126(para) ./doc/install-guide/section_cinder-controller.xml:96(para)
msgid "Edit the <filename>/etc/cinder/cinder.conf</filename> configuration file and add this section for keystone credentials:"
msgstr ""
#: ./doc/install-guide/section_cinder-node.xml:140(para) ./doc/install-guide/section_cinder-controller.xml:110(para) ./doc/install-guide/section_cinder-controller.xml:134(para)
msgid "Configure Block Storage to use the RabbitMQ message broker."
msgstr ""
#: ./doc/install-guide/section_cinder-node.xml:142(para)
msgid "In the <literal>[DEFAULT]</literal> configuration section of the <filename>/etc/cinder/cinder.conf</filename> file, set these configuration keys and replace <replaceable>RABBIT_PASS</replaceable> with the password you chose for RabbitMQ:"
msgstr ""
#: ./doc/install-guide/section_cinder-node.xml:156(para) ./doc/install-guide/section_cinder-controller.xml:126(para)
msgid "Configure Block Storage to use the Qpid message broker:"
msgstr ""
#: ./doc/install-guide/section_cinder-node.xml:164(para)
msgid "Configure Block Storage to use the RabbitMQ message broker. Replace <replaceable>RABBIT_PASS</replaceable> with the password you chose for RabbitMQ:"
msgstr ""
#: ./doc/install-guide/section_cinder-node.xml:177(para)
msgid "Configure Block Storage to use your MySQL database. Edit the <filename>/etc/cinder/cinder.conf</filename> file and add the following key to the <literal>[database]</literal> section. Replace <replaceable>CINDER_DBPASS</replaceable> with the password you chose for the Block Storage database:"
msgstr ""
#: ./doc/install-guide/section_cinder-node.xml:183(replaceable) ./doc/install-guide/section_cinder-node.xml:186(replaceable) ./doc/install-guide/section_cinder-controller.xml:44(replaceable) ./doc/install-guide/section_cinder-controller.xml:47(replaceable) ./doc/install-guide/section_cinder-controller.xml:59(replaceable) ./doc/install-guide/section_cinder-controller.xml:61(replaceable)
msgid "CINDER_DBPASS"
msgstr ""
#: ./doc/install-guide/section_cinder-node.xml:188(para) ./doc/install-guide/section_cinder-controller.xml:48(para)
msgid "In some distributions, the <filename>/etc/cinder/cinder.conf</filename> file does not include the <literal>[database]</literal> section header. You must add this section header to the end of the file before you proceed."
msgstr ""
#: ./doc/install-guide/section_cinder-node.xml:196(para)
msgid "Configure Block Storage to use the Image Service. Block Storage needs access to images to create bootable volumes. Edit the <filename>/etc/cinder/cinder.conf</filename> file and update the <option>glance_host</option> option in the <literal>[DEFAULT]</literal> section:"
msgstr ""
#: ./doc/install-guide/section_cinder-node.xml:208(para) ./doc/install-guide/section_cinder-controller.xml:168(para)
msgid "Restart the Block Storage services with the new settings:"
msgstr ""
#: ./doc/install-guide/section_cinder-node.xml:214(para)
msgid "Configure the iSCSI target service to discover Block Storage volumes. Add the following line to the beginning of the <filename>/etc/tgt/targets.conf</filename> file, if it is not already present:"
msgstr ""
#: ./doc/install-guide/section_cinder-node.xml:221(para) ./doc/install-guide/section_cinder-controller.xml:174(para)
msgid "Start and configure the Block Storage services to start when the system boots:"
msgstr ""
#: ./doc/install-guide/section_cinder-controller.xml:5(title)
msgid "Configure a Block Storage service controller"
msgstr ""
#: ./doc/install-guide/section_cinder-controller.xml:7(para)
msgid "This scenario configures OpenStack Block Storage services on the <glossterm baseform=\"controller node\">Controller node</glossterm> and assumes that a second node provides storage through the <systemitem class=\"service\">cinder-volume</systemitem> service."
msgstr ""
#: ./doc/install-guide/section_cinder-controller.xml:12(para)
msgid "For instructions on how to configure the second node, see <xref linkend=\"cinder-node\"/>."
msgstr ""
#: ./doc/install-guide/section_cinder-controller.xml:20(para)
msgid "Install the appropriate packages for the Block Storage service:"
msgstr ""
#: ./doc/install-guide/section_cinder-controller.xml:27(para)
msgid "Respond to the prompts for database management, <literal>[keystone_authtoken]</literal> settings, RabbitMQ credentials and API endpoint registration."
msgstr ""
#: ./doc/install-guide/section_cinder-controller.xml:31(para)
msgid "Configure Block Storage to use your database."
msgstr ""
#: ./doc/install-guide/section_cinder-controller.xml:32(para)
msgid "Run the following command to set <literal>connection</literal> option in the <literal>[database]</literal> section, which is in the <filename>/etc/cinder/cinder.conf</filename> file, replace <replaceable>CINDER_DBPASS</replaceable> with the password for the Block Storage database that you will create in a later step:"
msgstr ""
#: ./doc/install-guide/section_cinder-controller.xml:38(para)
msgid "In the <filename>/etc/cinder/cinder.conf</filename> file, set the <literal>connection</literal> option in the <literal>[database]</literal> section and replace <replaceable>CINDER_DBPASS</replaceable> with the password for the Block Storage database that you will create in a later step:"
msgstr ""
#: ./doc/install-guide/section_cinder-controller.xml:54(para)
msgid "Use the password that you set to log in as root to create a <literal>cinder</literal> database:"
msgstr ""
#: ./doc/install-guide/section_cinder-controller.xml:64(para)
msgid "Create the database tables for the Block Storage service:"
msgstr ""
#: ./doc/install-guide/section_cinder-controller.xml:69(para)
msgid "Create a <literal>cinder</literal> user."
msgstr ""
#: ./doc/install-guide/section_cinder-controller.xml:70(para)
msgid "The Block Storage service uses this user to authenticate with the Identity service."
msgstr ""
#: ./doc/install-guide/section_cinder-controller.xml:72(para)
msgid "Use the <literal>service</literal> tenant and give the user the <literal>admin</literal> role:"
msgstr ""
#: ./doc/install-guide/section_cinder-controller.xml:74(replaceable)
msgid "cinder@example.com"
msgstr ""
#: ./doc/install-guide/section_cinder-controller.xml:78(para)
msgid "Edit the <filename>/etc/cinder/cinder.conf</filename> configuration file:"
msgstr ""
#: ./doc/install-guide/section_cinder-controller.xml:112(para)
msgid "In the <literal>[DEFAULT]</literal> section in the <filename>/etc/cinder/cinder.conf</filename> file, set these configuration keys and replace <replaceable>RABBIT_PASS</replaceable> with the password you chose for RabbitMQ:"
msgstr ""
#: ./doc/install-guide/section_cinder-controller.xml:136(para)
msgid "Replace <replaceable>RABBIT_PASS</replaceable> with the password you chose for RabbitMQ:"
msgstr ""
#: ./doc/install-guide/section_cinder-controller.xml:148(para)
msgid "Register the Block Storage service with the Identity service so that other OpenStack services can locate it:"
msgstr ""
#: ./doc/install-guide/section_cinder-controller.xml:158(para)
msgid "Register a service and endpoint for version 2 of the Block Storage service API:"
msgstr ""
#: ./doc/install-guide/bk_openstackinstallguide.xml:7(title)
msgid "OpenStack Installation Guide for <phrase os=\"rhel;centos;fedora\">Red Hat Enterprise Linux, CentOS, and Fedora</phrase><phrase os=\"ubuntu\">Ubuntu 12.04/14.04 (LTS)</phrase><phrase os=\"debian\">Debian 7.0 (Wheezy)</phrase><phrase os=\"opensuse\">openSUSE and SUSE Linux Enterprise Server</phrase>"
msgstr ""
#: ./doc/install-guide/bk_openstackinstallguide.xml:15(phrase)
msgid "Red Hat Enterprise Linux, CentOS, and Fedora"
msgstr ""
#: ./doc/install-guide/bk_openstackinstallguide.xml:16(phrase)
msgid "Ubuntu 12.04/14.04 (LTS)"
msgstr ""
#: ./doc/install-guide/bk_openstackinstallguide.xml:17(phrase)
msgid "openSUSE and SUSE Linux Enterprise Server"
msgstr ""
#: ./doc/install-guide/bk_openstackinstallguide.xml:18(phrase)
msgid "Debian 7.0 (Wheezy)"
msgstr ""
#: ./doc/install-guide/bk_openstackinstallguide.xml:14(titleabbrev)
msgid "OpenStack Installation Guide for <placeholder-1/><placeholder-2/><placeholder-3/><placeholder-4/>"
msgstr ""
#: ./doc/install-guide/bk_openstackinstallguide.xml:27(orgname)
msgid "OpenStack"
msgstr ""
#: ./doc/install-guide/bk_openstackinstallguide.xml:31(year)
msgid "2012"
msgstr ""
#: ./doc/install-guide/bk_openstackinstallguide.xml:32(year)
msgid "2013"
msgstr ""
#: ./doc/install-guide/bk_openstackinstallguide.xml:33(holder)
msgid "OpenStack Foundation"
msgstr ""
#: ./doc/install-guide/bk_openstackinstallguide.xml:35(releaseinfo)
msgid "icehouse"
msgstr ""
#: ./doc/install-guide/bk_openstackinstallguide.xml:36(productname)
msgid "OpenStack Installation Guide"
msgstr ""
#: ./doc/install-guide/bk_openstackinstallguide.xml:40(remark)
msgid "Copyright details are filled in by the template."
msgstr ""
#: ./doc/install-guide/bk_openstackinstallguide.xml:45(para)
msgid "The OpenStack® system consists of several key projects that you install separately but that work together depending on your cloud needs. These projects include Compute, Identity Service, Networking, Image Service, Block Storage, Object Storage, Telemetry, Orchestration, and Database. You can install any of these projects separately and configure them stand-alone or as connected entities. <phrase os=\"debian\">This guide walks through an installation by using packages available through Debian 7.0 (code name: Wheezy).</phrase><phrase os=\"ubuntu\">This guide walks through an installation by using packages available through Ubuntu 12.04 (LTS) or 14.04 (LTS).</phrase><phrase os=\"rhel;centos;fedora\">This guide shows you how to install OpenStack by using packages available through Fedora 20 as well as on Red Hat Enterprise Linux and its derivatives through the EPEL repository.</phrase><phrase os=\"opensuse\">This guide shows you how to install OpenStack by using packages on openSUSE through the Open Build Service Cloud repository.</phrase> Explanations of configuration options and sample configuration files are included."
msgstr ""
#: ./doc/install-guide/bk_openstackinstallguide.xml:73(date)
msgid "2014-04-16"
msgstr ""
#: ./doc/install-guide/bk_openstackinstallguide.xml:77(para)
msgid "Update for Icehouse, rework Networking setup to use ML2 as plugin, add new chapter for Database Service setup, improved basic configuration."
msgstr ""
#: ./doc/install-guide/bk_openstackinstallguide.xml:86(date)
msgid "2013-10-25"
msgstr ""
#: ./doc/install-guide/bk_openstackinstallguide.xml:90(para)
msgid "Added initial Debian support."
msgstr ""
#: ./doc/install-guide/bk_openstackinstallguide.xml:96(date)
msgid "2013-10-17"
msgstr ""
#: ./doc/install-guide/bk_openstackinstallguide.xml:100(para)
msgid "Havana release."
msgstr ""
#: ./doc/install-guide/bk_openstackinstallguide.xml:106(date)
msgid "2013-10-16"
msgstr ""
#: ./doc/install-guide/bk_openstackinstallguide.xml:110(para)
msgid "Add support for SUSE Linux Enterprise."
msgstr ""
#: ./doc/install-guide/bk_openstackinstallguide.xml:117(date)
msgid "2013-10-08"
msgstr ""
#: ./doc/install-guide/bk_openstackinstallguide.xml:121(para)
msgid "Complete reorganization for Havana."
msgstr ""
#: ./doc/install-guide/bk_openstackinstallguide.xml:128(date)
msgid "2013-09-09"
msgstr ""
#: ./doc/install-guide/bk_openstackinstallguide.xml:132(para)
msgid "Build also for openSUSE."
msgstr ""
#: ./doc/install-guide/bk_openstackinstallguide.xml:138(date)
msgid "2013-08-01"
msgstr ""
#: ./doc/install-guide/bk_openstackinstallguide.xml:142(para)
msgid "Fixes to Object Storage verification steps. Fix bug <link href=\"https://bugs.launchpad.net/openstack-manuals/+bug/1207347\">1207347</link>."
msgstr ""
#: ./doc/install-guide/bk_openstackinstallguide.xml:151(date)
msgid "2013-07-25"
msgstr ""
#: ./doc/install-guide/bk_openstackinstallguide.xml:155(para)
msgid "Adds creation of cinder user and addition to the service tenant. Fix bug <link href=\"https://bugs.launchpad.net/openstack-manuals/+bug/1205057\">1205057</link>."
msgstr ""
#: ./doc/install-guide/bk_openstackinstallguide.xml:165(date)
msgid "2013-05-08"
msgstr ""
#: ./doc/install-guide/bk_openstackinstallguide.xml:169(para)
msgid "Updated the book title for consistency."
msgstr ""
#: ./doc/install-guide/bk_openstackinstallguide.xml:176(date)
msgid "2013-05-02"
msgstr ""
#: ./doc/install-guide/bk_openstackinstallguide.xml:180(para)
msgid "Updated cover and fixed small errors in appendix."
msgstr ""
#: ./doc/install-guide/ch_debconf.xml:6(title)
msgid "Configure OpenStack with debconf"
msgstr ""
#: ./doc/install-guide/section_neutron-ml2-network-node.xml:9(para) ./doc/install-guide/section_neutron-ml2-compute-node.xml:9(para)
msgid "Before you configure OpenStack Networking, you must enable certain kernel networking functions."
msgstr ""
#: ./doc/install-guide/section_neutron-ml2-network-node.xml:12(para) ./doc/install-guide/section_neutron-ml2-compute-node.xml:12(para)
msgid "Edit <filename>/etc/sysctl.conf</filename> to contain the following:"
msgstr ""
#: ./doc/install-guide/section_neutron-ml2-network-node.xml:19(para) ./doc/install-guide/section_neutron-ml2-compute-node.xml:18(para)
msgid "Implement the changes:"
msgstr ""
#: ./doc/install-guide/section_neutron-ml2-network-node.xml:33(para) ./doc/install-guide/section_neutron-ml2-compute-node.xml:30(para)
msgid "Ubuntu installations using Linux kernel version 3.11 or newer do not require the <emphasis>openvswitch-datapath-dkms</emphasis> package."
msgstr ""
#: ./doc/install-guide/section_neutron-ml2-network-node.xml:43(title) ./doc/install-guide/section_neutron-ml2-compute-node.xml:40(title)
msgid "To configure the Networking common components"
msgstr ""
#: ./doc/install-guide/section_neutron-ml2-network-node.xml:44(para) ./doc/install-guide/section_neutron-ml2-compute-node.xml:41(para)
msgid "The Networking common component configuration includes the authentication mechanism, message broker, and plug-in."
msgstr ""
#: ./doc/install-guide/section_neutron-ml2-network-node.xml:188(title)
msgid "To configure the Layer-3 (L3) agent"
msgstr ""
#: ./doc/install-guide/section_neutron-ml2-network-node.xml:189(para)
msgid "The <glossterm>Layer-3 (L3) agent</glossterm> provides routing services for instance virtual networks."
msgstr ""
#: ./doc/install-guide/section_neutron-ml2-network-node.xml:198(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:213(para)
msgid "We recommend adding <literal>verbose = True</literal> to the <literal>[DEFAULT]</literal> section in <filename>/etc/neutron/l3_agent.ini</filename> to assist with troubleshooting."
msgstr ""
#: ./doc/install-guide/section_neutron-ml2-network-node.xml:205(para)
msgid "Edit the <filename>/etc/neutron/l3_agent.ini</filename> file and add the following keys to the <literal>[DEFAULT]</literal> section:"
msgstr ""
#: ./doc/install-guide/section_neutron-ml2-network-node.xml:221(title)
msgid "To configure the DHCP agent"
msgstr ""
#: ./doc/install-guide/section_neutron-ml2-network-node.xml:222(para)
msgid "The <glossterm>DHCP agent</glossterm> provides <glossterm>DHCP</glossterm> services for instance virtual networks."
msgstr ""
#: ./doc/install-guide/section_neutron-ml2-network-node.xml:234(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:250(para)
msgid "We recommend adding <literal>verbose = True</literal> to the <literal>[DEFAULT]</literal> section in <filename>/etc/neutron/dhcp_agent.ini</filename> to assist with troubleshooting."
msgstr ""
#: ./doc/install-guide/section_neutron-ml2-network-node.xml:241(para)
msgid "Edit the <filename>/etc/neutron/dhcp_agent.ini</filename> file and add the following keys to the <literal>[DEFAULT]</literal> section:"
msgstr ""
#: ./doc/install-guide/section_neutron-ml2-network-node.xml:258(title)
msgid "To configure the metadata agent"
msgstr ""
#: ./doc/install-guide/section_neutron-ml2-network-node.xml:259(para)
msgid "The <glossterm>metadata agent</glossterm> provides configuration information such as credentials for remote access to instances."
msgstr ""
#: ./doc/install-guide/section_neutron-ml2-network-node.xml:263(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:293(para)
msgid "Replace <replaceable>NEUTRON_PASS</replaceable> with the password you chose for the <literal>neutron</literal> user in the Identity service. Replace <replaceable>METADATA_SECRET</replaceable> with a suitable secret for the metadata proxy."
msgstr ""
#: ./doc/install-guide/section_neutron-ml2-network-node.xml:281(replaceable) ./doc/install-guide/section_neutron-ml2-network-node.xml:306(replaceable) ./doc/install-guide/section_neutron-ml2-network-node.xml:329(replaceable) ./doc/install-guide/section_neutron-ml2-network-node.xml:341(replaceable)
msgid "METADATA_SECRET"
msgstr ""
#: ./doc/install-guide/section_neutron-ml2-network-node.xml:283(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:308(para)
msgid "We recommend adding <literal>verbose = True</literal> to the <literal>[DEFAULT]</literal> section in <filename>/etc/neutron/metadata_agent.ini</filename> to assist with troubleshooting."
msgstr ""
#: ./doc/install-guide/section_neutron-ml2-network-node.xml:290(para)
msgid "Edit the <filename>/etc/neutron/metadata_agent.ini</filename> file and add the following keys to the <literal>[DEFAULT]</literal> section:"
msgstr ""
#: ./doc/install-guide/section_neutron-ml2-network-node.xml:316(para)
msgid "Perform the next two steps on the <emphasis>controller</emphasis> node."
msgstr ""
#: ./doc/install-guide/section_neutron-ml2-network-node.xml:321(para)
msgid "On the <emphasis>controller</emphasis> node, configure Compute to use the metadata service:"
msgstr ""
#: ./doc/install-guide/section_neutron-ml2-network-node.xml:323(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:335(para)
msgid "Replace <replaceable>METADATA_SECRET</replaceable> with the secret you chose for the metadata proxy."
msgstr ""
#: ./doc/install-guide/section_neutron-ml2-network-node.xml:332(para)
msgid "On the <emphasis>controller</emphasis> node, edit the <filename>/etc/nova/nova.conf</filename> file and add the following keys to the <literal>[DEFAULT]</literal> section:"
msgstr ""
#: ./doc/install-guide/section_neutron-ml2-network-node.xml:344(para)
msgid "On the <emphasis>controller</emphasis> node, restart the Compute <glossterm>API</glossterm> service:"
msgstr ""
#: ./doc/install-guide/section_neutron-ml2-network-node.xml:352(para)
msgid "The ML2 plug-in uses the Open vSwitch (OVS) mechanism (agent) to build virtual networking framework for instances."
msgstr ""
#: ./doc/install-guide/section_neutron-ml2-network-node.xml:356(para)
msgid "Replace <replaceable>INSTANCE_TUNNELS_INTERFACE_IP_ADDRESS</replaceable> with the IP address of the instance tunnels network interface on your network node. This guide uses <literal>10.0.1.21</literal> for the IP address of the instance tunnels network interface on the network node."
msgstr ""
#: ./doc/install-guide/section_neutron-ml2-network-node.xml:372(replaceable) ./doc/install-guide/section_neutron-ml2-network-node.xml:406(replaceable) ./doc/install-guide/section_neutron-ml2-compute-node.xml:206(replaceable) ./doc/install-guide/section_neutron-ml2-compute-node.xml:240(replaceable)
msgid "INSTANCE_TUNNELS_INTERFACE_IP_ADDRESS"
msgstr ""
#: ./doc/install-guide/section_neutron-ml2-network-node.xml:383(para)
msgid "Edit the <filename>/etc/neutron/plugins/ml2/ml2_conf.ini</filename> file."
msgstr ""
#: ./doc/install-guide/section_neutron-ml2-network-node.xml:393(para) ./doc/install-guide/section_neutron-ml2-compute-node.xml:227(para)
msgid "Add the following keys to the <literal>[ml2_type_gre]</literal> section:"
msgstr ""
#: ./doc/install-guide/section_neutron-ml2-network-node.xml:398(para) ./doc/install-guide/section_neutron-ml2-compute-node.xml:232(para)
msgid "Add the <literal>[ovs]</literal> section and the following keys to it:"
msgstr ""
#: ./doc/install-guide/section_neutron-ml2-network-node.xml:400(para)
msgid "Replace <replaceable>INSTANCE_TUNNELS_INTERFACE_IP_ADDRESS</replaceable> with the IP address of the instance tunnels network interface on your network node."
msgstr ""
#: ./doc/install-guide/section_neutron-ml2-network-node.xml:418(title) ./doc/install-guide/section_neutron-ml2-compute-node.xml:252(title)
msgid "To configure the Open vSwitch (OVS) service"
msgstr ""
#: ./doc/install-guide/section_neutron-ml2-network-node.xml:419(para)
msgid "The OVS service provides the underlying virtual networking framework for instances. The integration bridge <literal>br-int</literal> handles internal instance network traffic within OVS. The external bridge <literal>br-ext</literal> 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/install-guide/section_neutron-ml2-network-node.xml:428(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:434(para) ./doc/install-guide/section_neutron-ml2-compute-node.xml:257(para) ./doc/install-guide/section_neutron-ml2-compute-node.xml:263(para)
msgid "Start the OVS service and configure it to start when the system boots:"
msgstr ""
#: ./doc/install-guide/section_neutron-ml2-network-node.xml:440(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:444(para) ./doc/install-guide/section_neutron-ml2-compute-node.xml:269(para) ./doc/install-guide/section_neutron-ml2-compute-node.xml:273(para)
msgid "Restart the OVS service:"
msgstr ""
#: ./doc/install-guide/section_neutron-ml2-network-node.xml:448(para) ./doc/install-guide/section_neutron-ml2-compute-node.xml:277(para)
msgid "Add the integration bridge:"
msgstr ""
#: ./doc/install-guide/section_neutron-ml2-network-node.xml:452(para)
msgid "Add the external bridge:"
msgstr ""
#: ./doc/install-guide/section_neutron-ml2-network-node.xml:456(para)
msgid "Add a port to the external bridge that connects to the physical external network interface:"
msgstr ""
#: ./doc/install-guide/section_neutron-ml2-network-node.xml:463(para)
msgid "Depending on your network interface driver, you may need to disable <glossterm>Generic Receive Offload (GRO)</glossterm> to achieve suitable throughput between your instances and the external network."
msgstr ""
#: ./doc/install-guide/section_neutron-ml2-network-node.xml:467(para)
msgid "To temporarily disable GRO on the external network interface while testing your environment:"
msgstr ""
#: ./doc/install-guide/section_neutron-ml2-network-node.xml:474(title) ./doc/install-guide/section_neutron-ml2-compute-node.xml:347(title)
msgid "To finalize the installation"
msgstr ""
#: ./doc/install-guide/section_neutron-ml2-network-node.xml:476(para) ./doc/install-guide/section_neutron-ml2-compute-node.xml:349(para)
msgid "The Networking service initialization scripts expect a symbolic link <filename>/etc/neutron/plugin.ini</filename> pointing to the configuration file associated with your chosen plug-in. Using the ML2 plug-in, for example, the symbolic link must point to <filename>/etc/neutron/plugins/ml2/ml2_conf.ini</filename>. If this symbolic link does not exist, create it using the following commands:"
msgstr ""
#. https://bugzilla.redhat.com/show_bug.cgi?id=1087647
#: ./doc/install-guide/section_neutron-ml2-network-node.xml:485(para) ./doc/install-guide/section_neutron-ml2-compute-node.xml:358(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 <filename>/etc/neutron/plugin.ini</filename> pointing to the ML2 plug-in configuration file. Run the following commands to resolve this issue:"
msgstr ""
#: ./doc/install-guide/section_neutron-ml2-network-node.xml:495(para) ./doc/install-guide/section_neutron-ml2-compute-node.xml:368(para)
msgid "The Networking service initialization scripts expect the variable <literal>NEUTRON_PLUGIN_CONF</literal> in the <filename>/etc/sysconfig/neutron</filename> file to reference the configuration file associated with your chosen plug-in. Using ML2, for example, edit the <filename>/etc/sysconfig/neutron</filename> file and add the following:"
msgstr ""
#: ./doc/install-guide/section_neutron-ml2-network-node.xml:505(para)
msgid "Start the Networking services and configure them to start when the system boots:"
msgstr ""
#: ./doc/install-guide/section_neutron-ml2-network-node.xml:525(para)
msgid "Restart the Networking services:"
msgstr ""
#: ./doc/install-guide/section_neutron-ml2-compute-node.xml:186(para)
msgid "The ML2 plug-in uses the Open vSwitch (OVS) mechanism (agent) to build the virtual networking framework for instances."
msgstr ""
#: ./doc/install-guide/section_neutron-ml2-compute-node.xml:190(para)
msgid "Replace <replaceable>INSTANCE_TUNNELS_INTERFACE_IP_ADDRESS</replaceable> with the IP address of the instance tunnels network interface on your compute node. This guide uses <literal>10.0.1.31</literal> for the IP address of the instance tunnels network interface on the first compute node."
msgstr ""
#: ./doc/install-guide/section_neutron-ml2-compute-node.xml:234(para)
msgid "Replace <replaceable>INSTANCE_TUNNELS_INTERFACE_IP_ADDRESS</replaceable> with the IP address of the instance tunnels network interface on your compute node."
msgstr ""
#: ./doc/install-guide/section_neutron-ml2-compute-node.xml:253(para)
msgid "The OVS service provides the underlying virtual networking framework for instances. The integration bridge <literal>br-int</literal> handles internal instance network traffic within OVS."
msgstr ""
#: ./doc/install-guide/section_neutron-ml2-compute-node.xml:378(para) ./doc/install-guide/section_ceilometer-nova.xml:53(para) ./doc/install-guide/section_nova-compute.xml:208(para)
msgid "Restart the Compute service:"
msgstr ""
#: ./doc/install-guide/section_neutron-ml2-compute-node.xml:383(para)
msgid "Start the Open vSwitch (OVS) agent and configure it to start when the system boots:"
msgstr ""
#: ./doc/install-guide/section_neutron-ml2-compute-node.xml:391(para)
msgid "Restart the Open vSwitch (OVS) agent:"
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/install-guide/ch_overview.xml:35(None)
msgid "@@image: '../common/figures/openstack_havana_conceptual_arch.png'; md5=96e1d5492d4c865fc9145710bb294a91"
msgstr ""
#: ./doc/install-guide/ch_overview.xml:6(title)
msgid "Architecture"
msgstr ""
#: ./doc/install-guide/ch_overview.xml:8(title)
msgid "Overview"
msgstr ""
#: ./doc/install-guide/ch_overview.xml:9(para)
msgid "The <glossterm>OpenStack</glossterm> 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/install-guide/ch_overview.xml:14(para)
msgid "OpenStack provides an Infrastructure-as-a-Service (<glossterm>IaaS</glossterm>) solution through a variety of complemental services. Each service offers an application programming interface (<glossterm>API</glossterm>) that facilitates this integration. The following table provides a list of OpenStack services:"
msgstr ""
#: ./doc/install-guide/ch_overview.xml:21(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/install-guide/ch_overview.xml:26(title) ./doc/install-guide/ch_overview.xml:31(title)
msgid "Conceptual architecture"
msgstr ""
#: ./doc/install-guide/ch_overview.xml:27(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/install-guide/ch_overview.xml:41(title)
msgid "Example architectures"
msgstr ""
#: ./doc/install-guide/ch_overview.xml:42(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/install-guide/ch_overview.xml:49(para)
msgid "Three-node architecture with OpenStack Networking (neutron). See <xref linkend=\"example-architecture-with-neutron-networking\"/>."
msgstr ""
#: ./doc/install-guide/ch_overview.xml:52(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, <glossterm>message broker</glossterm>, and <glossterm>Network Time Protocol (NTP)</glossterm>."
msgstr ""
#: ./doc/install-guide/ch_overview.xml:59(para) ./doc/install-guide/ch_overview.xml:114(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/install-guide/ch_overview.xml:65(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, <glossterm baseform=\"Network Address Translation (NAT)\">NAT</glossterm> , and <glossterm>DHCP</glossterm>. This node also handles external (internet) connectivity for tenant virtual machines or instances."
msgstr ""
#: ./doc/install-guide/ch_overview.xml:75(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/install-guide/ch_overview.xml:81(para) ./doc/install-guide/ch_overview.xml:130(para)
msgid "Optionally, the compute node also runs the Telemetry agent. This component provides additional features for your environment."
msgstr ""
#: ./doc/install-guide/ch_overview.xml:87(para)
msgid "When you implement this architecture, skip <xref linkend=\"section_nova-networking\"/> in <xref linkend=\"ch_networking\"/>. To use optional services, you might need to install additional nodes, as described in subsequent chapters."
msgstr ""
#: ./doc/install-guide/ch_overview.xml:104(para)
msgid "Two-node architecture with legacy networking (nova-network). See <xref linkend=\"example-architecture-with-legacy-networking\"/>."
msgstr ""
#: ./doc/install-guide/ch_overview.xml:108(para)
msgid "The basic <glossterm baseform=\"cloud controller node\">controller node</glossterm> 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/install-guide/ch_overview.xml:120(para)
msgid "The basic <glossterm>compute node</glossterm> runs the <glossterm>hypervisor</glossterm> portion of Compute, which operates <glossterm>tenant</glossterm><glossterm baseform=\"virtual machine (VM)\">virtual machines</glossterm> or instances. By default, Compute uses <glossterm baseform=\"kernel-based VM (KVM)\">KVM</glossterm> as the <glossterm>hypervisor</glossterm>. Compute also provisions and operates tenant networks and implements <glossterm baseform=\"security group\">security groups</glossterm>. You can run more than one compute node."
msgstr ""
#: ./doc/install-guide/ch_overview.xml:136(para)
msgid "When you implement this architecture, skip <xref linkend=\"section_neutron-networking\"/> in <xref linkend=\"ch_networking\"/>. To use optional services, you might need to install additional nodes, as described in subsequent chapters."
msgstr ""
#: ./doc/install-guide/section_dashboard-install.xml:7(title)
msgid "Install the dashboard"
msgstr ""
#: ./doc/install-guide/section_dashboard-install.xml:8(para)
msgid "Before you can install and configure the dashboard, meet the requirements in <xref linkend=\"dashboard-system-requirements\"/>."
msgstr ""
#: ./doc/install-guide/section_dashboard-install.xml:12(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/install-guide/section_dashboard-install.xml:16(para)
msgid "For more information about how to deploy the dashboard, see <link href=\"http://docs.openstack.org/developer/horizon/topics/deployment.html\">deployment topics in the developer documentation</link>."
msgstr ""
#: ./doc/install-guide/section_dashboard-install.xml:22(para)
msgid "Install the dashboard on the node that can contact the Identity Service as root:"
msgstr ""
#: ./doc/install-guide/section_dashboard-install.xml:28(title)
msgid "Note for Ubuntu users"
msgstr ""
#: ./doc/install-guide/section_dashboard-install.xml:30(para)
msgid "Remove the <literal>openstack-dashboard-ubuntu-theme</literal> package. This theme prevents translations, several menus as well as the network map from rendering correctly: <placeholder-1/>"
msgstr ""
#: ./doc/install-guide/section_dashboard-install.xml:39(title)
msgid "Note for Debian users"
msgstr ""
#: ./doc/install-guide/section_dashboard-install.xml:40(para)
msgid "To install the Apache package:"
msgstr ""
#: ./doc/install-guide/section_dashboard-install.xml:42(para)
msgid "This command installs and configures Apache correctly, provided that the user asks for it during the <package>debconf</package> 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/install-guide/section_dashboard-install.xml:51(para)
msgid "Modify the value of <literal>CACHES['default']['LOCATION']</literal> in <filename os=\"ubuntu;debian\">/etc/openstack-dashboard/local_settings.py</filename><filename os=\"centos;fedora;rhel\">/etc/openstack-dashboard/local_settings</filename><filename os=\"opensuse;sles\">/srv/www/openstack-dashboard/openstack_dashboard/local/local_settings.py</filename> to match the ones set in <filename os=\"ubuntu;debian\">/etc/memcached.conf</filename><filename os=\"centos;fedora;rhel;opensuse;sles\">/etc/sysconfig/memcached</filename>."
msgstr ""
#: ./doc/install-guide/section_dashboard-install.xml:63(para)
msgid "Open <filename os=\"ubuntu;debian\">/etc/openstack-dashboard/local_settings.py</filename><filename os=\"centos;fedora;rhel\">/etc/openstack-dashboard/local_settings</filename> and look for this line:"
msgstr ""
#: ./doc/install-guide/section_dashboard-install.xml:76(title) ./doc/install-guide/object-storage/section_object-storage-sys-requirements.xml:29(td)
msgid "Notes"
msgstr ""
#: ./doc/install-guide/section_dashboard-install.xml:79(para)
msgid "The address and port must match the ones set in <filename os=\"ubuntu;debian\">/etc/memcached.conf</filename><filename os=\"centos;fedora;rhel;opensuse;sles\">/etc/sysconfig/memcached</filename>."
msgstr ""
#: ./doc/install-guide/section_dashboard-install.xml:84(para)
msgid "If you change the memcached settings, you must restart the Apache web server for the changes to take effect."
msgstr ""
#: ./doc/install-guide/section_dashboard-install.xml:89(para)
msgid "You can use options other than memcached option for session storage. Set the session back-end through the <parameter>SESSION_ENGINE</parameter> option."
msgstr ""
#: ./doc/install-guide/section_dashboard-install.xml:96(para)
msgid "To change the timezone, use the dashboard or edit the <filename os=\"centos;fedora;rhel\">/etc/openstack-dashboard/local_settings</filename><filename os=\"ubuntu;debian\">/etc/openstack-dashboard/local_settings.py</filename><filename os=\"opensuse;sles\">/srv/www/openstack-dashboard/openstack_dashboard/local/local_settings.py</filename> file."
msgstr ""
#: ./doc/install-guide/section_dashboard-install.xml:105(para)
msgid "Change the following parameter: <code>TIME_ZONE = \"UTC\"</code>"
msgstr ""
#: ./doc/install-guide/section_dashboard-install.xml:112(para)
msgid "Update the <literal>ALLOWED_HOSTS</literal> in <filename>local_settings.py</filename> to include the addresses you wish to access the dashboard from."
msgstr ""
#: ./doc/install-guide/section_dashboard-install.xml:116(para)
msgid "Edit <filename os=\"centos;fedora;rhel\">/etc/openstack-dashboard/local_settings</filename><filename os=\"ubuntu;debian\">/etc/openstack-dashboard/local_settings.py</filename><filename os=\"opensuse;sles\">/srv/www/openstack-dashboard/openstack_dashboard/local/local_settings.py</filename>:"
msgstr ""
#: ./doc/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 <filename>local_settings.py</filename>."
msgstr ""
#: ./doc/install-guide/section_dashboard-install.xml:132(para)
msgid "Edit <filename os=\"centos;fedora;rhel\">/etc/openstack-dashboard/local_settings</filename><filename os=\"ubuntu;debian\">/etc/openstack-dashboard/local_settings.py</filename><filename os=\"opensuse;sles\">/srv/www/openstack-dashboard/openstack_dashboard/local/local_settings.py</filename> and change <literal>OPENSTACK_HOST</literal> to the hostname of your Identity Service:"
msgstr ""
#: ./doc/install-guide/section_dashboard-install.xml:144(para)
msgid "Setup Apache configuration: <placeholder-1/>"
msgstr ""
#: ./doc/install-guide/section_dashboard-install.xml:151(para)
msgid "By default, the <systemitem>openstack-dashboard</systemitem> package enables a database as session store. Before you continue, either change the session store set up as described in <xref linkend=\"dashboard-sessions\"/> or finish the setup of the database session store as explained in <xref linkend=\"dashboard-session-database\"/>."
msgstr ""
#: ./doc/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/install-guide/section_dashboard-install.xml:168(para)
msgid "Start the Apache web server and memcached:"
msgstr ""
#: ./doc/install-guide/section_dashboard-install.xml:181(para)
msgid "You can now access the dashboard at <uri os=\"ubuntu\">http://controller/horizon</uri><uri os=\"debian\">https://controller/</uri><uri os=\"centos;fedora;rhel\">http://controller/dashboard</uri><uri os=\"opensuse;sles\">http://controller</uri>."
msgstr ""
#: ./doc/install-guide/section_dashboard-install.xml:188(para)
msgid "Login with credentials for any user that you created with the OpenStack Identity Service."
msgstr ""
#: ./doc/install-guide/section_basics-queue.xml:6(title)
msgid "Messaging server"
msgstr ""
#: ./doc/install-guide/section_basics-queue.xml:7(para)
msgid "OpenStack uses a <glossterm>message broker</glossterm> to coordinate operations and status information among services. The message broker service typically runs on the controller node. OpenStack supports several message brokers including <application>RabbitMQ</application>, <application>Qpid</application>, and <application>ZeroMQ</application>. However, most distributions that package OpenStack support a particular message broker. This guide covers the message broker supported by each distribution. If you prefer to implement a different message broker, consult the documentation associated with it."
msgstr ""
#: ./doc/install-guide/section_basics-queue.xml:18(link)
msgid "RabbitMQ"
msgstr ""
#: ./doc/install-guide/section_basics-queue.xml:21(link)
msgid "Qpid"
msgstr ""
#: ./doc/install-guide/section_basics-queue.xml:24(link)
msgid "ZeroMQ"
msgstr ""
#: ./doc/install-guide/section_basics-queue.xml:28(title)
msgid "To install the message broker service"
msgstr ""
#: ./doc/install-guide/section_basics-queue.xml:30(para)
msgid "Ubuntu and Debian use <application>RabbitMQ</application>."
msgstr ""
#: ./doc/install-guide/section_basics-queue.xml:34(para)
msgid "Red Hat Enterprise Linux (RHEL), CentOS, Scientific Linux, and Fedora use <application>Qpid</application>."
msgstr ""
#: ./doc/install-guide/section_basics-queue.xml:40(para)
msgid "SUSE Linux Enterprise Server (SLES) and openSUSE use <application>RabbitMQ</application>."
msgstr ""
#: ./doc/install-guide/section_basics-queue.xml:46(title)
msgid "To configure the message broker service"
msgstr ""
#: ./doc/install-guide/section_basics-queue.xml:48(para)
msgid "To simplify installation of your test environment, we recommend that you disable authentication."
msgstr ""
#: ./doc/install-guide/section_basics-queue.xml:50(para)
msgid "Edit the <filename>/etc/qpidd.conf</filename> file and change the following key:"
msgstr ""
#: ./doc/install-guide/section_basics-queue.xml:54(para)
msgid "For production environments, you should enable authentication. For more information on securing the message broker, see the <link href=\"http://qpid.apache.org/books/trunk/AMQP-Messaging-Broker-CPP-Book/html/chap-Messaging_User_Guide-Security.html\">documentation</link>."
msgstr ""
#: ./doc/install-guide/section_basics-queue.xml:59(para)
msgid "If you decide to enable authentication for your test environment, you must configure the <literal>qpid_username</literal> and <literal>qpid_password</literal> keys in the configuration file of each OpenStack service that uses the message broker."
msgstr ""
#: ./doc/install-guide/section_basics-queue.xml:66(para)
msgid "Start the message broker service:"
msgstr ""
#: ./doc/install-guide/section_basics-queue.xml:70(para)
msgid "The message broker creates a default account that uses <literal>guest</literal> 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/install-guide/section_basics-queue.xml:74(para) ./doc/install-guide/section_nova-compute.xml:159(para) ./doc/install-guide/section_nova-compute.xml:178(para)
msgid "Run the following command:"
msgstr ""
#: ./doc/install-guide/section_basics-queue.xml:75(para)
msgid "Replace <replaceable>RABBIT_PASS</replaceable> with a suitable password."
msgstr ""
#: ./doc/install-guide/section_basics-queue.xml:78(para)
msgid "You must configure the <literal>rabbit_password</literal> key in the configuration file for each OpenStack service that uses the message broker."
msgstr ""
#: ./doc/install-guide/section_basics-queue.xml:82(para)
msgid "For production environments, you should create a unique account with suitable password. For more information on securing the message broker, see the <link href=\"https://www.rabbitmq.com/man/rabbitmqctl.1.man.html\">documentation</link>."
msgstr ""
#: ./doc/install-guide/section_basics-queue.xml:87(para)
msgid "If you decide to create a unique account with suitable password for your test environment, you must configure the <literal>rabbit_userid</literal> and <literal>rabbit_password</literal> keys in the configuration file of each OpenStack service that uses the message broker."
msgstr ""
#: ./doc/install-guide/section_basics-queue.xml:98(para)
msgid "Start the message broker service and configure it to start when the system boots:"
msgstr ""
#: ./doc/install-guide/section_basics-queue.xml:104(para)
msgid "Configure the message broker service to start when the system boots:"
msgstr ""
#: ./doc/install-guide/section_basics-queue.xml:109(para)
msgid "Congratulations, now you are ready to install OpenStack services!"
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/install-guide/section_neutron-initial-networks.xml:23(None)
msgid "@@image: 'figures/installguide_neutron-initial-networks.png'; md5=df1d74b6f91feefe5cfaf7824aac86e1"
msgstr ""
#: ./doc/install-guide/section_neutron-initial-networks.xml:6(title)
msgid "Create initial networks"
msgstr ""
#: ./doc/install-guide/section_neutron-initial-networks.xml:7(para)
msgid "Before launching your first instance, you must create the necessary virtual network infrastructure to which the instance will connect, including the <link linkend=\"neutron_initial-external-network\">external network</link> and <link linkend=\"neutron_initial-tenant-network\">tenant network</link>. See <xref linkend=\"neutron_figure-neutron-initial-networks\"/>. After creating this infrastructure, we recommend that you <link linkend=\"neutron_initial-networks-verify\">verify connectivity</link> and resolve any issues before proceeding further."
msgstr ""
#: ./doc/install-guide/section_neutron-initial-networks.xml:19(title)
msgid "Initial networks"
msgstr ""
#: ./doc/install-guide/section_neutron-initial-networks.xml:28(title)
msgid "External network"
msgstr ""
#: ./doc/install-guide/section_neutron-initial-networks.xml:29(para)
msgid "The external network typically provides internet access for your instances. By default, this network only allows internet access <emphasis>from</emphasis> instances using <glossterm>Network Address Translation (NAT)</glossterm>. You can enable internet access <emphasis>to</emphasis> individual instances using a <glossterm>floating IP address</glossterm> and suitable <glossterm>security group</glossterm> rules. The <literal>admin</literal> 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/install-guide/section_neutron-initial-networks.xml:43(title)
msgid "To create the external network"
msgstr ""
#: ./doc/install-guide/section_neutron-initial-networks.xml:69(para)
msgid "Like a physical network, a virtual network requires a <glossterm>subnet</glossterm> assigned to it. The external network shares the same subnet and <glossterm>gateway</glossterm> associated with the physical network connected to the external interface on the network node. You should specify an exclusive slice of this subnet for <glossterm>router</glossterm> and floating IP addresses to prevent interference with other devices on the external network."
msgstr ""
#: ./doc/install-guide/section_neutron-initial-networks.xml:76(para)
msgid "Replace <replaceable>FLOATING_IP_START</replaceable> and <replaceable>FLOATING_IP_END</replaceable> with the first and last IP addresses of the range that you want to allocate for floating IP addresses. Replace <replaceable>EXTERNAL_NETWORK_CIDR</replaceable> with the subnet associated with the physical network. Replace <replaceable>EXTERNAL_NETWORK_GATEWAY</replaceable> with the gateway associated with the physical network, typically the \".1\" IP address. You should disable <glossterm>DHCP</glossterm> on this subnet because instances do not connect directly to the external network and floating IP addresses require manual assignment."
msgstr ""
#: ./doc/install-guide/section_neutron-initial-networks.xml:87(title)
msgid "To create a subnet on the external network"
msgstr ""
#: ./doc/install-guide/section_neutron-initial-networks.xml:89(para) ./doc/install-guide/section_neutron-initial-networks.xml:164(para)
msgid "Create the subnet:"
msgstr ""
#: ./doc/install-guide/section_neutron-initial-networks.xml:91(replaceable)
msgid "FLOATING_IP_START"
msgstr ""
#: ./doc/install-guide/section_neutron-initial-networks.xml:91(replaceable)
msgid "FLOATING_IP_END"
msgstr ""
#: ./doc/install-guide/section_neutron-initial-networks.xml:92(replaceable)
msgid "EXTERNAL_NETWORK_GATEWAY"
msgstr ""
#: ./doc/install-guide/section_neutron-initial-networks.xml:92(replaceable)
msgid "EXTERNAL_NETWORK_CIDR"
msgstr ""
#: ./doc/install-guide/section_neutron-initial-networks.xml:93(para)
msgid "For example, using <literal>203.0.113.0/24</literal> with floating IP address range <literal>203.0.113.101</literal> to <literal>203.0.113.200</literal>:"
msgstr ""
#: ./doc/install-guide/section_neutron-initial-networks.xml:121(title)
msgid "Tenant network"
msgstr ""
#: ./doc/install-guide/section_neutron-initial-networks.xml:122(para)
msgid "The tenant network provides internal network access for instances. The architecture isolates this type of network from other tenants. The <literal>demo</literal> tenant owns this network because it only provides network access for instances within it."
msgstr ""
#: ./doc/install-guide/section_neutron-initial-networks.xml:130(title)
msgid "To create the tenant network"
msgstr ""
#: ./doc/install-guide/section_neutron-initial-networks.xml:152(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 <replaceable>TENANT_NETWORK_CIDR</replaceable> with the subnet you want to associate with the tenant network. Replace <replaceable>TENANT_NETWORK_GATEWAY</replaceable> 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/install-guide/section_neutron-initial-networks.xml:162(title)
msgid "To create a subnet on the tenant network"
msgstr ""
#: ./doc/install-guide/section_neutron-initial-networks.xml:166(replaceable)
msgid "TENANT_NETWORK_GATEWAY"
msgstr ""
#: ./doc/install-guide/section_neutron-initial-networks.xml:166(replaceable)
msgid "TENANT_NETWORK_CIDR"
msgstr ""
#: ./doc/install-guide/section_neutron-initial-networks.xml:167(para)
msgid "Example using <literal>192.168.1.0/24</literal>:"
msgstr ""
#: ./doc/install-guide/section_neutron-initial-networks.xml:190(para)
msgid "A virtual router passes network traffic between two or more virtual networks. Each router requires one or more <glossterm baseform=\"interface\">interfaces</glossterm> 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/install-guide/section_neutron-initial-networks.xml:196(title)
msgid "To create a router on the tenant network and attach the external and tenant networks to it"
msgstr ""
#: ./doc/install-guide/section_neutron-initial-networks.xml:199(para)
msgid "Create the router:"
msgstr ""
#: ./doc/install-guide/section_neutron-initial-networks.xml:214(para)
msgid "Attach the router to the <literal>demo</literal> tenant subnet:"
msgstr ""
#: ./doc/install-guide/section_neutron-initial-networks.xml:220(para)
msgid "Attach the router to the external network by setting it as the gateway:"
msgstr ""
#: ./doc/install-guide/section_neutron-initial-networks.xml:229(para)
msgid "We recommend that you verify network connectivity and resolve any issues before proceeding further. Following the external network subnet example using <literal>203.0.113.0/24</literal>, the tenant router gateway should occupy the lowest IP address in the floating IP address range, <literal>203.0.113.101</literal>. If you configured your external physical network and virtual networks correctly, you you should be able to <placeholder-1/> this IP address from any host on your external physical network."
msgstr ""
#: ./doc/install-guide/section_neutron-initial-networks.xml:238(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/install-guide/section_neutron-initial-networks.xml:243(title)
msgid "To verify network connectivity"
msgstr ""
#: ./doc/install-guide/section_neutron-initial-networks.xml:245(para)
msgid "Ping the tenant router gateway:"
msgstr ""
#: ./doc/install-guide/section_heat-install.xml:5(title)
msgid "Install the Orchestration service"
msgstr ""
#: ./doc/install-guide/section_heat-install.xml:8(para) ./doc/install-guide/section_heat-install.xml:24(para)
msgid "Install the Orchestration module on the controller node:"
msgstr ""
#: ./doc/install-guide/section_heat-install.xml:13(para)
msgid "Respond to prompts for <link linkend=\"debconf-dbconfig-common\">database management</link>, <link linkend=\"debconf-keystone_authtoken\"><systemitem>[keystone_authtoken]</systemitem> settings</link>, <link linkend=\"debconf-rabbitqm\">RabbitMQ credentials</link> and <link linkend=\"debconf-api-endpoints\">API endpoint</link> registration."
msgstr ""
#: ./doc/install-guide/section_heat-install.xml:33(para)
msgid "In the configuration file, specify the location of the database where the Orchestration service stores data. These examples use a MySQL database with a <literal>heat</literal> user on the controller node. Replace <replaceable>HEAT_DBPASS</replaceable> with the password for the database user:"
msgstr ""
#: ./doc/install-guide/section_heat-install.xml:40(replaceable) ./doc/install-guide/section_heat-install.xml:46(replaceable) ./doc/install-guide/section_heat-install.xml:61(replaceable) ./doc/install-guide/section_heat-install.xml:63(replaceable)
msgid "HEAT_DBPASS"
msgstr ""
#: ./doc/install-guide/section_heat-install.xml:41(para)
msgid "Edit <filename>/etc/heat/heat.conf</filename> and modify the <literal>[database]</literal> section:"
msgstr ""
#: ./doc/install-guide/section_heat-install.xml:49(para)
msgid "By default, the Ubuntu packages create an SQLite database. Delete the <filename>heat.sqlite</filename> file that was created in the <filename>/var/lib/heat/</filename> directory so that it does not get used by mistake:"
msgstr ""
#: ./doc/install-guide/section_heat-install.xml:56(para)
msgid "Use the password that you set previously to log in as <literal>root</literal> and create a <literal>heat</literal> database user:"
msgstr ""
#: ./doc/install-guide/section_heat-install.xml:66(para)
msgid "Create the heat service tables:"
msgstr ""
#: ./doc/install-guide/section_heat-install.xml:69(para)
msgid "Ignore <errortext>DeprecationWarning</errortext> errors."
msgstr ""
#: ./doc/install-guide/section_heat-install.xml:74(para)
msgid "The Ubuntu packages do not correctly set up logging. Edit the <filename>/etc/heat/heat.conf</filename> file and change the <literal>[DEFAULT]</literal> section:"
msgstr ""
#: ./doc/install-guide/section_heat-install.xml:88(para)
msgid "Configure the Orchestration Service to use the RabbitMQ message broker."
msgstr ""
#: ./doc/install-guide/section_heat-install.xml:90(para)
msgid "Edit <filename>/etc/heat/heat.conf</filename> and modify the <literal>[DEFAULT]</literal> section:"
msgstr ""
#: ./doc/install-guide/section_heat-install.xml:99(para)
msgid "Create a <literal>heat</literal> user that the Orchestration service can use to authenticate with the Identity Service. Use the <literal>service</literal> tenant and give the user the <literal>admin</literal> role:"
msgstr ""
#: ./doc/install-guide/section_heat-install.xml:103(replaceable) ./doc/install-guide/section_heat-install.xml:119(replaceable)
msgid "HEAT_PASS"
msgstr ""
#: ./doc/install-guide/section_heat-install.xml:104(replaceable)
msgid "heat@example.com"
msgstr ""
#: ./doc/install-guide/section_heat-install.xml:108(para)
msgid "Edit the <filename>/etc/heat/heat.conf</filename> file to change the <literal>[keystone_authtoken]</literal> and <literal>[ec2authtoken]</literal> sections to add credentials to the Orchestration Service:"
msgstr ""
#: ./doc/install-guide/section_heat-install.xml:125(para)
msgid "Register the Heat and CloudFormation APIs with the Identity Service so that other OpenStack services can locate these APIs. Register the services and specify the endpoints:"
msgstr ""
#: ./doc/install-guide/section_heat-install.xml:145(para)
msgid "Create the <literal>heat_stack_user</literal> role."
msgstr ""
#: ./doc/install-guide/section_heat-install.xml:146(para)
msgid "This role is used as the default role for users created by the Orchestration module."
msgstr ""
#: ./doc/install-guide/section_heat-install.xml:148(para)
msgid "Run the following command to create the <literal>heat_stack_user</literal> role:"
msgstr ""
#: ./doc/install-guide/section_heat-install.xml:153(para)
msgid "Configure the metadata and waitcondition servers' URLs."
msgstr ""
#: ./doc/install-guide/section_heat-install.xml:154(para)
msgid "Edit the <filename>/etc/heat/heat.conf</filename> file and modify the following options in the <literal>[DEFAULT]</literal> section:"
msgstr ""
#: ./doc/install-guide/section_heat-install.xml:160(replaceable) ./doc/install-guide/section_heat-install.xml:163(replaceable) ./doc/install-guide/section_heat-install.xml:168(replaceable) ./doc/install-guide/section_heat-install.xml:170(replaceable)
msgid "10.0.0.11"
msgstr ""
#: ./doc/install-guide/section_heat-install.xml:164(para)
msgid "Run the following commands to modify the <literal>[DEFAULT]</literal> section of the <filename>/etc/heat/heat.conf</filename> file:"
msgstr ""
#: ./doc/install-guide/section_heat-install.xml:172(para)
msgid "The example uses the IP address of the controller (10.0.0.11) instead of the <literal>controller</literal> host name since our example architecture does not include a DNS setup. Make sure that the instances can resolve the controller host name if you choose to use it in the URLs."
msgstr ""
#: ./doc/install-guide/section_heat-install.xml:186(para)
msgid "Start the <systemitem class=\"service\">heat-api</systemitem>, <systemitem class=\"service\">heat-api-cfn</systemitem> and <systemitem class=\"service\">heat-engine</systemitem> services and configure them to start when the system boots:"
msgstr ""
#: ./doc/install-guide/section_ceilometer-nova.xml:7(title)
msgid "Install the Compute agent for Telemetry"
msgstr ""
#: ./doc/install-guide/section_ceilometer-nova.xml:9(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/install-guide/section_ceilometer-nova.xml:14(para)
msgid "Install the Telemetry service on the compute node:"
msgstr ""
#: ./doc/install-guide/section_ceilometer-nova.xml:20(para)
msgid "Set the following options in the <filename>/etc/nova/nova.conf</filename> file:"
msgstr ""
#: ./doc/install-guide/section_ceilometer-nova.xml:30(para)
msgid "The <option>notification_driver</option> option is a multi valued option, which <application>openstack-config</application> cannot set properly. See <xref linkend=\"basics-packages\"/>."
msgstr ""
#: ./doc/install-guide/section_ceilometer-nova.xml:36(para)
msgid "Edit the <filename>/etc/nova/nova.conf</filename> file and add the following lines to the <literal>[DEFAULT]</literal> section:"
msgstr ""
#: ./doc/install-guide/section_ceilometer-nova.xml:58(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/install-guide/section_ceilometer-nova.xml:63(para)
msgid "Edit the <filename>/etc/ceilometer/ceilometer.conf</filename> file and change these lines in the <literal>[publisher]</literal> section. Replace <replaceable>CEILOMETER_TOKEN</replaceable> with the ceilometer token that you created previously:"
msgstr ""
#: ./doc/install-guide/section_ceilometer-nova.xml:84(para)
msgid "Configure the QPid access:"
msgstr ""
#: ./doc/install-guide/section_ceilometer-nova.xml:89(para)
msgid "Add the Identity service credentials:"
msgstr ""
#: ./doc/install-guide/section_ceilometer-nova.xml:141(para)
msgid "Start the service and configure it to start when the system boots:"
msgstr ""
#: ./doc/install-guide/section_neutron-deploy-use-cases.xml:6(title)
msgid "Neutron deployment use cases"
msgstr ""
#: ./doc/install-guide/section_neutron-deploy-use-cases.xml:7(para)
msgid "This section describes how to configure the Networking service and its components for some typical use cases."
msgstr ""
#: ./doc/install-guide/section_nova-compute.xml:5(title)
msgid "Configure a compute node"
msgstr ""
#: ./doc/install-guide/section_nova-compute.xml:6(para)
msgid "After you configure the Compute service on the controller node, you must configure another system as a compute node. The compute node receives requests from the controller node and hosts virtual machine instances. You can run all services on a single node, but the examples in this guide use separate systems. This makes it easy to scale horizontally by adding additional Compute nodes following the instructions in this section."
msgstr ""
#: ./doc/install-guide/section_nova-compute.xml:13(para)
msgid "The Compute service relies on a hypervisor to run virtual machine instances. OpenStack can use various hypervisors, but this guide uses KVM."
msgstr ""
#: ./doc/install-guide/section_nova-compute.xml:18(para)
msgid "Install the Compute packages:"
msgstr ""
#: ./doc/install-guide/section_nova-compute.xml:20(para)
msgid "When prompted to create a <literal>supermin</literal> appliance, respond <placeholder-1/>."
msgstr ""
#: ./doc/install-guide/section_nova-compute.xml:25(para)
msgid "To use the meta-packages and install other components on your compute node, such as OpenStack Networking and Ceilometer agents, run this command:"
msgstr ""
#: ./doc/install-guide/section_nova-compute.xml:29(para)
msgid "The controller node has the <package>openstack-proxy-node</package> and <package>openstack-toaster</package> meta-packages that install <package>openstack-proxy-node</package> and <package>openstack-toaster</package> at the same time."
msgstr ""
#: ./doc/install-guide/section_nova-compute.xml:41(para)
msgid "Respond to the prompts for <link linkend=\"debconf-dbconfig-common\">database management</link>, <link linkend=\"debconf-keystone_authtoken\"><literal>[keystone_authtoken]</literal> settings</link>, <link linkend=\"debconf-rabbitqm\">RabbitMQ credentials</link>, and <link linkend=\"debconf-api-endpoints\">API endpoint</link> registration."
msgstr ""
#: ./doc/install-guide/section_nova-compute.xml:50(para)
msgid "For security reasons, the Linux kernel is not readable by normal users which restricts hypervisor services such as qemu and libguestfs. For details, see <link href=\"https://bugs.launchpad.net/ubuntu/+source/linux/+bug/759725\">this bug</link>. To make the current kernel readable, run: <placeholder-1/> To also enable this override for all future kernel updates, create the file <filename>/etc/kernel/postinst.d/statoverride</filename> containing:<placeholder-2/> Remember to make the file executable: <placeholder-3/>"
msgstr ""
#: ./doc/install-guide/section_nova-compute.xml:69(para)
msgid "Edit the <filename>/etc/nova/nova.conf</filename> configuration file:"
msgstr ""
#: ./doc/install-guide/section_nova-compute.xml:81(para)
msgid "Edit the <filename>/etc/nova/nova.conf</filename> configuration file and add these lines to the appropriate sections:"
msgstr ""
#: ./doc/install-guide/section_nova-compute.xml:102(para)
msgid "Configure the Compute service to use the Qpid message broker by setting these configuration keys:"
msgstr ""
#: ./doc/install-guide/section_nova-compute.xml:116(para)
msgid "Configure the Compute service to use the RabbitMQ message broker by setting these configuration keys:"
msgstr ""
#: ./doc/install-guide/section_nova-compute.xml:125(para)
msgid "Configure Compute to provide remote console access to instances."
msgstr ""
#: ./doc/install-guide/section_nova-compute.xml:132(para)
msgid "Edit <filename>/etc/nova/nova.conf</filename> and add the following keys under the <literal>[DEFAULT]</literal> section:"
msgstr ""
#: ./doc/install-guide/section_nova-compute.xml:146(para)
msgid "Specify the host that runs the Image Service.<phrase os=\"ubuntu;debian\"> Edit <filename>/etc/nova/nova.conf</filename> file and add these lines to the <literal>[DEFAULT]</literal> section:</phrase>"
msgstr ""
#: ./doc/install-guide/section_nova-compute.xml:157(para)
msgid "You must determine whether your system's processor and/or hypervisor support hardware acceleration for virtual machines."
msgstr ""
#: ./doc/install-guide/section_nova-compute.xml:161(para)
msgid "If this command returns a value of <emphasis>one or greater</emphasis>, your system supports hardware acceleration which typically requires no additional configuration."
msgstr ""
#: ./doc/install-guide/section_nova-compute.xml:165(para)
msgid "If this command returns a value of <emphasis>zero</emphasis>, your system does not support hardware acceleration and you must configure <literal>libvirt</literal> to use QEMU instead of KVM."
msgstr ""
#: ./doc/install-guide/section_nova-compute.xml:170(para)
msgid "Edit the <literal>[libvirt]</literal> section in the <filename>/etc/nova/nova-compute.conf</filename> file to modify this key:"
msgstr ""
#: ./doc/install-guide/section_nova-compute.xml:183(para)
msgid "On Ubuntu 12.04, kernels backported from newer releases may not automatically load the KVM modules for hardware acceleration when the system boots. In this case, launching an instance will fail with the following message in the <filename>/var/log/nova/nova-compute.log</filename> file:"
msgstr ""
#: ./doc/install-guide/section_nova-compute.xml:189(para)
msgid "As a workaround for this issue, you must add the appropriate module for your system to the <filename>/etc/modules</filename> file."
msgstr ""
#: ./doc/install-guide/section_nova-compute.xml:192(para)
msgid "For systems with Intel processors, run the following command:"
msgstr ""
#: ./doc/install-guide/section_nova-compute.xml:195(para)
msgid "For systems with AMD processors, run the following command:"
msgstr ""
#: ./doc/install-guide/section_nova-compute.xml:201(para)
msgid "Remove the SQLite database created by the packages:"
msgstr ""
#: ./doc/install-guide/section_nova-compute.xml:205(para)
msgid "Start the Compute service and configure it 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/install-guide/section_glance-install.xml:38(None)
msgid "@@image: 'figures/debconf-screenshots/glance-common_pipeline_flavor.png'; md5=78bef92c36a140ad042074f6345d8917"
msgstr ""
#: ./doc/install-guide/section_glance-install.xml:5(title)
msgid "Install the Image Service"
msgstr ""
#: ./doc/install-guide/section_glance-install.xml:6(para)
msgid "The OpenStack Image Service acts as a registry for virtual disk images. Users can add new images or take a snapshot of an image from an existing server for immediate storage. Use snapshots for back up and as templates to launch new servers. You can store registered images in Object Storage or in other locations. For example, you can store images in simple file systems or external web servers."
msgstr ""
#: ./doc/install-guide/section_glance-install.xml:14(para)
msgid "This procedure assumes you set the appropriate environment variables to your credentials as described in <xref linkend=\"keystone-verify\"/>."
msgstr ""
#: ./doc/install-guide/section_glance-install.xml:20(para)
msgid "Install the Image Service on the controller node:"
msgstr ""
#: ./doc/install-guide/section_glance-install.xml:27(para)
msgid "Respond to prompts for <link linkend=\"debconf-dbconfig-common\">database management</link>, <link linkend=\"debconf-keystone_authtoken\"><literal>[keystone_authtoken]</literal> settings</link>, <link linkend=\"debconf-rabbitqm\">RabbitMQ credentials</link> and <link linkend=\"debconf-api-endpoints\">API endpoint</link> registration. You must also select the caching type:"
msgstr ""
#: ./doc/install-guide/section_glance-install.xml:43(para)
msgid "The Image Service stores information about images in a database. The examples in this guide use the MySQL database that is used by other OpenStack services."
msgstr ""
#: ./doc/install-guide/section_glance-install.xml:46(para)
msgid "Configure the location of the database. The Image Service provides the <systemitem class=\"service\">glance-api</systemitem> and <systemitem class=\"service\">glance-registry</systemitem> services, each with its own configuration file. You must update both configuration files throughout this section. Replace <replaceable>GLANCE_DBPASS</replaceable> with your Image Service database password."
msgstr ""
#: ./doc/install-guide/section_glance-install.xml:55(replaceable) ./doc/install-guide/section_glance-install.xml:57(replaceable) ./doc/install-guide/section_glance-install.xml:120(replaceable) ./doc/install-guide/section_glance-install.xml:122(replaceable)
msgid "GLANCE_DBPASS"
msgstr ""
#: ./doc/install-guide/section_glance-install.xml:58(para)
msgid "Edit <filename>/etc/glance/glance-api.conf</filename> and <filename>/etc/glance/glance-registry.conf</filename> and edit the <literal>[database]</literal> section of each file:"
msgstr ""
#: ./doc/install-guide/section_glance-install.xml:70(para) ./doc/install-guide/section_glance-install.xml:77(para) ./doc/install-guide/section_glance-install.xml:95(para)
msgid "Configure the Image Service to use the message broker:"
msgstr ""
#: ./doc/install-guide/section_glance-install.xml:80(para)
msgid "Edit the <filename>/etc/glance/glance-api.conf</filename> file and add the following keys to the <literal>[DEFAULT]</literal> section:"
msgstr ""
#: ./doc/install-guide/section_glance-install.xml:108(para)
msgid "By default, the Ubuntu packages create an SQLite database. Delete the <filename>glance.sqlite</filename> file created in the <filename>/var/lib/glance/</filename> directory so that it does not get used by mistake:"
msgstr ""
#: ./doc/install-guide/section_glance-install.xml:115(para)
msgid "Use the password you created to log in as root and create a <literal>glance</literal> database user:"
msgstr ""
#: ./doc/install-guide/section_glance-install.xml:125(para)
msgid "Create the database tables for the Image Service:"
msgstr ""
#: ./doc/install-guide/section_glance-install.xml:129(para)
msgid "Create a <literal>glance</literal> user that the Image Service can use to authenticate with the Identity service. Choose a password and specify an email address for the <literal>glance</literal> user. Use the <literal>service</literal> tenant and give the user the <literal>admin</literal> role:"
msgstr ""
#: ./doc/install-guide/section_glance-install.xml:135(replaceable) ./doc/install-guide/section_glance-install.xml:159(replaceable) ./doc/install-guide/section_glance-install.xml:175(replaceable) ./doc/install-guide/section_glance-install.xml:194(replaceable)
msgid "GLANCE_PASS"
msgstr ""
#: ./doc/install-guide/section_glance-install.xml:136(replaceable)
msgid "glance@example.com"
msgstr ""
#: ./doc/install-guide/section_glance-install.xml:140(para)
msgid "Configure the Image Service to use the Identity Service for authentication."
msgstr ""
#: ./doc/install-guide/section_glance-install.xml:142(para)
msgid "Run the following commands and replace <replaceable>GLANCE_PASS</replaceable> with the password you chose for the <literal>glance</literal> user in the Identity Service:"
msgstr ""
#: ./doc/install-guide/section_glance-install.xml:178(para)
msgid "Edit the <filename>/etc/glance/glance-api.conf</filename> and <filename>/etc/glance/glance-registry.conf</filename> files. Replace <replaceable>GLANCE_PASS</replaceable> with the password you chose for the <literal>glance</literal> user in the Identity service."
msgstr ""
#: ./doc/install-guide/section_glance-install.xml:185(para)
msgid "Add or modify the following keys under the <literal>[keystone_authtoken]</literal> section:"
msgstr ""
#: ./doc/install-guide/section_glance-install.xml:197(para)
msgid "Modify the following key under the <literal>[paste_deploy]</literal> section:"
msgstr ""
#: ./doc/install-guide/section_glance-install.xml:206(para)
msgid "Register the Image Service with the Identity service so that other OpenStack services can locate it. Register the service and create the endpoint:"
msgstr ""
#: ./doc/install-guide/section_glance-install.xml:218(para)
msgid "Restart the <systemitem class=\"service\">glance</systemitem> service with its new settings:"
msgstr ""
#: ./doc/install-guide/section_glance-install.xml:224(para)
msgid "Start the <systemitem class=\"service\">glance-api</systemitem> and <systemitem class=\"service\">glance-registry</systemitem> services and configure them 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/install-guide/section_debconf-dbconfig-common.xml:30(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/install-guide/section_debconf-dbconfig-common.xml:39(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/install-guide/section_debconf-dbconfig-common.xml:78(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/install-guide/section_debconf-dbconfig-common.xml:87(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/install-guide/section_debconf-dbconfig-common.xml:96(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/install-guide/section_debconf-dbconfig-common.xml:105(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/install-guide/section_debconf-dbconfig-common.xml:114(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/install-guide/section_debconf-dbconfig-common.xml:123(None)
msgid "@@image: 'figures/debconf-screenshots/dbconfig-common_6_mysql_app_password_confirm.png'; md5=060cc90aaf6f6fd5cea718064829c1b1"
msgstr ""
#: ./doc/install-guide/section_debconf-dbconfig-common.xml:6(title)
msgid "Configure the database with dbconfig-common"
msgstr ""
#: ./doc/install-guide/section_debconf-dbconfig-common.xml:7(para)
msgid "The <package>dbconfig-common</package> package provides a standard Debian interface that enables you to configure Debian database parameters. It includes localized prompts for many languages and it supports the OpenStack database back ends: SQLite, MySQL, and PostgreSQL."
msgstr ""
#: ./doc/install-guide/section_debconf-dbconfig-common.xml:12(para)
msgid "By default, the <package>dbconfig-common</package> package configures the OpenStack services to use SQLite3. So if you use <package>debconf</package> in non-interactive mode and without pre-seeding, the OpenStack services that you install use SQLite3."
msgstr ""
#: ./doc/install-guide/section_debconf-dbconfig-common.xml:17(para)
msgid "By default, <package>dbconfig-common</package> does not provide access to database servers over a network. If you want the <package>dbconfig-common</package> 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/install-guide/section_debconf-dbconfig-common.xml:23(para)
msgid "These screens appear when you re-configure the <package>dbconfig-common</package> package:"
msgstr ""
#: ./doc/install-guide/section_debconf-dbconfig-common.xml:43(para)
msgid "Unlike other <package>debconf</package> prompts, you cannot pre-seed the responses for the <package>dbconfig-common</package> prompts by using <placeholder-1/>. Instead, you must create a file in <filename>/etc/dbconfig-common</filename>. For example, you might create a keystone configuration file for <package>dbconfig-common</package> that is located in <filename>/etc/dbconfig-common/keystone.conf</filename>, as follows:"
msgstr ""
#: ./doc/install-guide/section_debconf-dbconfig-common.xml:66(para)
msgid "After you create this file, run this command:"
msgstr ""
#: ./doc/install-guide/section_debconf-dbconfig-common.xml:68(para)
msgid "The Identity Service is installed with MySQL as the database back end, <literal>keystonedb</literal> as database name, and the localhost socket file."
msgstr ""
#: ./doc/install-guide/section_debconf-dbconfig-common.xml:71(para)
msgid "The <package>cinder-common</package> package displays these screens:"
msgstr ""
#: ./doc/install-guide/section_debconf-dbconfig-common.xml:127(para)
msgid "To access a MySQL server remotely, you must make it accessible as root from a remote server. To do so, run the <package>openstack-proxy-node</package> package command:"
msgstr ""
#: ./doc/install-guide/section_debconf-dbconfig-common.xml:131(para)
msgid "Alternatively, if you do not want to install this package, run this script to enable remote root access:"
msgstr ""
#: ./doc/install-guide/section_debconf-dbconfig-common.xml:154(para)
msgid "You must enable remote access before you install OpenStack services."
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/install-guide/section_keystone-install.xml:79(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/install-guide/section_keystone-install.xml:104(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/install-guide/section_keystone-install.xml:113(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/install-guide/section_keystone-install.xml:122(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/install-guide/section_keystone-install.xml:131(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/install-guide/section_keystone-install.xml:140(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/install-guide/section_keystone-install.xml:154(None)
msgid "@@image: 'figures/debconf-screenshots/keystone_7_register_endpoint.png'; md5=d24d84133bfee936267e79631a2666e6"
msgstr ""
#: ./doc/install-guide/section_keystone-install.xml:6(title)
msgid "Install the Identity Service"
msgstr ""
#: ./doc/install-guide/section_keystone-install.xml:9(para)
msgid "Install the OpenStack Identity Service on the controller node, together with <application>python-keystoneclient</application> (which is a dependency):"
msgstr ""
#: ./doc/install-guide/section_keystone-install.xml:17(para)
msgid "Answer to the <systemitem class=\"library\">debconf</systemitem> and <systemitem class=\"library\">dbconfig-common</systemitem> questions for setting-up the database."
msgstr ""
#: ./doc/install-guide/section_keystone-install.xml:23(para)
msgid "The Identity Service uses a database to store information. Specify the location of the database in the configuration file. In this guide, we use a MySQL database on the controller node with the username <literal>keystone</literal>. Replace <literal><replaceable>KEYSTONE_DBPASS</replaceable></literal> with a suitable password for the database user."
msgstr ""
#: ./doc/install-guide/section_keystone-install.xml:30(replaceable) ./doc/install-guide/section_keystone-install.xml:38(replaceable) ./doc/install-guide/section_keystone-install.xml:57(replaceable) ./doc/install-guide/section_keystone-install.xml:59(replaceable)
msgid "KEYSTONE_DBPASS"
msgstr ""
#: ./doc/install-guide/section_keystone-install.xml:31(para)
msgid "Edit <filename>/etc/keystone/keystone.conf</filename> and change the <literal>[database]</literal> section:"
msgstr ""
#: ./doc/install-guide/section_keystone-install.xml:44(para)
msgid "By default, the Ubuntu packages create a SQLite database. Delete the <filename>keystone.db</filename> file created in the <filename>/var/lib/keystone/</filename> directory so that it does not get used by mistake:"
msgstr ""
#: ./doc/install-guide/section_keystone-install.xml:51(para)
msgid "Use the password that you set previously to log in as root. Create a <literal>keystone</literal> database user:"
msgstr ""
#: ./doc/install-guide/section_keystone-install.xml:63(para)
msgid "Create the database tables for the Identity Service:"
msgstr ""
#: ./doc/install-guide/section_keystone-install.xml:67(para)
msgid "Define an authorization token to use as a shared secret between the Identity Service and other OpenStack services. Respond to the <package>debconf</package> prompt with the value in the <code>admin_token</code> directive in the <filename>keystone.conf</filename> file. Use the <placeholder-1/> command to generate this password."
msgstr ""
#: ./doc/install-guide/section_keystone-install.xml:83(para)
msgid "Later, you can verify that the <filename>/etc/keystone/keystone.conf</filename> file contains the password you have set using <package>debconf</package>: <placeholder-1/>"
msgstr ""
#: ./doc/install-guide/section_keystone-install.xml:91(para)
msgid "If you omit a password (for example by pressing Enter at the <package>debconf</package> prompt, or installing Keystone using the Debconf non-interactive mode) the package generates a random <literal>ADMIN_TOKEN</literal> value."
msgstr ""
#: ./doc/install-guide/section_keystone-install.xml:97(para)
msgid "Respond to the prompts to create an administrative tenant:"
msgstr ""
#: ./doc/install-guide/section_keystone-install.xml:146(para)
msgid "If this is the first time you have installed the Identity Service, register the Identity Service in the service catalog:"
msgstr ""
#: ./doc/install-guide/section_keystone-install.xml:160(para)
msgid "Define an authorization token to use as a shared secret between the Identity Service and other OpenStack services. Use <placeholder-1/> to generate a random token and store it in the configuration file:"
msgstr ""
#: ./doc/install-guide/section_keystone-install.xml:169(para)
msgid "For SUSE Linux Enterprise use instead as first command:"
msgstr ""
#: ./doc/install-guide/section_keystone-install.xml:172(para)
msgid "Edit <filename>/etc/keystone/keystone.conf</filename> and change the <literal>[DEFAULT]</literal> section, replacing ADMIN_TOKEN with the results of the command:"
msgstr ""
#: ./doc/install-guide/section_keystone-install.xml:182(para)
msgid "By default, Keystone uses PKI tokens. Create the signing keys and certificates and restrict access to the generated data:"
msgstr ""
#: ./doc/install-guide/section_keystone-install.xml:189(para)
msgid "Configure the log directory. Edit the <filename>/etc/keystone/keystone.conf</filename> file and update the <literal>[DEFAULT]</literal> section:"
msgstr ""
#: ./doc/install-guide/section_keystone-install.xml:197(para)
msgid "Restart the Identity Service:"
msgstr ""
#: ./doc/install-guide/section_keystone-install.xml:201(para)
msgid "Start the Identity Service and enable it to start when the system boots:"
msgstr ""
#: ./doc/install-guide/section_keystone-install.xml:207(para)
msgid "By default, the Identity Service stores expired tokens in the database indefinitely. While potentially useful for auditing in production environments, the accumulation of expired tokens will considerably increase database size and may decrease service performance, particularly in test environments with limited resources. We recommend configuring a periodic task using <systemitem class=\"service\">cron</systemitem> to purge expired tokens hourly."
msgstr ""
#: ./doc/install-guide/section_keystone-install.xml:217(para)
msgid "Run the following command to purge expired tokens every hour and log the output to <filename>/var/log/keystone/keystone-tokenflush.log</filename>:"
msgstr ""
#: ./doc/install-guide/object-storage/section_object-storage-verifying-install.xml:6(title)
msgid "Verify the installation"
msgstr ""
#: ./doc/install-guide/object-storage/section_object-storage-verifying-install.xml:7(para)
msgid "You can run these commands from the proxy server or any server that has access to the Identity Service."
msgstr ""
#: ./doc/install-guide/object-storage/section_object-storage-verifying-install.xml:11(para)
msgid "Make sure that your credentials are set up correctly in the <filename>admin-openrc.sh</filename> file and source it:"
msgstr ""
#: ./doc/install-guide/object-storage/section_object-storage-verifying-install.xml:15(para)
msgid "Run the following <placeholder-1/> command:"
msgstr ""
#: ./doc/install-guide/object-storage/section_object-storage-verifying-install.xml:27(para)
msgid "Run the following <placeholder-1/> commands to upload files to a container. Create the <filename>test.txt</filename> and <filename>test2.txt</filename> test files locally if needed."
msgstr ""
#: ./doc/install-guide/object-storage/section_object-storage-verifying-install.xml:34(para)
msgid "Run the following <placeholder-1/> command to download all files from the <literal>myfiles</literal> container:"
msgstr ""
#: ./doc/install-guide/object-storage/section_object-storage-install-config-proxy-node.xml:6(title)
msgid "Install and configure the proxy node"
msgstr ""
#: ./doc/install-guide/object-storage/section_object-storage-install-config-proxy-node.xml:7(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 <filename>/etc/swift/proxy-server.conf</filename> file."
msgstr ""
#: ./doc/install-guide/object-storage/section_object-storage-install-config-proxy-node.xml:13(para)
msgid "The Object Storage processes run under a separate user and group, set by configuration options, and referred to as <literal>swift:swift</literal>. The default user is <literal>swift</literal>."
msgstr ""
#: ./doc/install-guide/object-storage/section_object-storage-install-config-proxy-node.xml:20(para)
msgid "Install swift-proxy service:"
msgstr ""
#: ./doc/install-guide/object-storage/section_object-storage-install-config-proxy-node.xml:26(para)
msgid "Modify memcached to listen on the default interface on a local, non-public network. Edit this line in the <filename>/etc/memcached.conf</filename> file:"
msgstr ""
#: ./doc/install-guide/object-storage/section_object-storage-install-config-proxy-node.xml:30(para)
msgid "Change it to:"
msgstr ""
#: ./doc/install-guide/object-storage/section_object-storage-install-config-proxy-node.xml:31(replaceable) ./doc/install-guide/object-storage/section_object-storage-install-config-proxy-node.xml:37(replaceable) ./doc/install-guide/object-storage/section_object-storage-install-config-proxy-node.xml:38(replaceable) ./doc/install-guide/object-storage/section_object-storage-adding-proxy-server.xml:36(replaceable)
msgid "PROXY_LOCAL_NET_IP"
msgstr ""
#: ./doc/install-guide/object-storage/section_object-storage-install-config-proxy-node.xml:34(para)
msgid "Modify memcached to listen on the default interface on a local, non-public network. Edit the <filename>/etc/sysconfig/memcached</filename> file:"
msgstr ""
#: ./doc/install-guide/object-storage/section_object-storage-install-config-proxy-node.xml:41(para)
msgid "Restart the memcached service:"
msgstr ""
#: ./doc/install-guide/object-storage/section_object-storage-install-config-proxy-node.xml:45(para)
msgid "Start the memcached service and configure it to start when the system boots:"
msgstr ""
#: ./doc/install-guide/object-storage/section_object-storage-install-config-proxy-node.xml:51(para)
msgid "<phrase os=\"ubuntu;debian\">Create</phrase><phrase os=\"rhel;centos;fedora;opensuse;sles\">Edit</phrase><filename>/etc/swift/proxy-server.conf</filename>:"
msgstr ""
#: ./doc/install-guide/object-storage/section_object-storage-install-config-proxy-node.xml:88(replaceable) ./doc/install-guide/object-storage/section_object-storage-install.xml:65(replaceable)
msgid "SWIFT_PASS"
msgstr ""
#: ./doc/install-guide/object-storage/section_object-storage-install-config-proxy-node.xml:100(para)
msgid "If you run multiple memcache servers, put the multiple IP:port listings in the [filter:cache] section of the <filename>/etc/swift/proxy-server.conf</filename> file:"
msgstr ""
#: ./doc/install-guide/object-storage/section_object-storage-install-config-proxy-node.xml:105(para)
msgid "Only the proxy server uses memcache."
msgstr ""
#: ./doc/install-guide/object-storage/section_object-storage-install-config-proxy-node.xml:109(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/install-guide/object-storage/section_object-storage-install-config-proxy-node.xml:125(para)
msgid "For every storage device on each node add entries to each ring:"
msgstr ""
#: ./doc/install-guide/object-storage/section_object-storage-install-config-proxy-node.xml:127(replaceable) ./doc/install-guide/object-storage/section_object-storage-install-config-proxy-node.xml:128(replaceable) ./doc/install-guide/object-storage/section_object-storage-install-config-proxy-node.xml:129(replaceable)
msgid "ZONE"
msgstr ""
#: ./doc/install-guide/object-storage/section_object-storage-install-config-proxy-node.xml:127(replaceable) ./doc/install-guide/object-storage/section_object-storage-install-config-storage-nodes.xml:54(replaceable)
msgid "STORAGE_LOCAL_NET_IP"
msgstr ""
#: ./doc/install-guide/object-storage/section_object-storage-install-config-proxy-node.xml:127(replaceable) ./doc/install-guide/object-storage/section_object-storage-install-config-proxy-node.xml:128(replaceable) ./doc/install-guide/object-storage/section_object-storage-install-config-proxy-node.xml:129(replaceable) ./doc/install-guide/object-storage/section_object-storage-install-config-storage-nodes.xml:80(replaceable)
msgid "STORAGE_REPLICATION_NET_IP"
msgstr ""
#: ./doc/install-guide/object-storage/section_object-storage-install-config-proxy-node.xml:127(replaceable) ./doc/install-guide/object-storage/section_object-storage-install-config-proxy-node.xml:128(replaceable) ./doc/install-guide/object-storage/section_object-storage-install-config-proxy-node.xml:129(replaceable)
msgid "DEVICE"
msgstr ""
#: ./doc/install-guide/object-storage/section_object-storage-install-config-proxy-node.xml:128(replaceable) ./doc/install-guide/object-storage/section_object-storage-install-config-proxy-node.xml:129(replaceable)
msgid "STORAGE_LOCAL_NET_IP_1"
msgstr ""
#: ./doc/install-guide/object-storage/section_object-storage-install-config-proxy-node.xml:131(para)
msgid "You must omit the optional <parameter>STORAGE_REPLICATION_NET_IP</parameter> parameter if you do not want to use dedicated network for replication."
msgstr ""
#: ./doc/install-guide/object-storage/section_object-storage-install-config-proxy-node.xml:135(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 <filename>/srv/node/sdb1</filename>, and the path in <filename>/etc/rsyncd.conf</filename> is <filename>/srv/node/</filename>, the DEVICE would be sdb1 and the commands are:"
msgstr ""
#: ./doc/install-guide/object-storage/section_object-storage-install-config-proxy-node.xml:146(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/install-guide/object-storage/section_object-storage-install-config-proxy-node.xml:152(para)
msgid "Verify the ring contents for each ring:"
msgstr ""
#: ./doc/install-guide/object-storage/section_object-storage-install-config-proxy-node.xml:158(para)
msgid "Rebalance the rings:"
msgstr ""
#: ./doc/install-guide/object-storage/section_object-storage-install-config-proxy-node.xml:163(para)
msgid "Rebalancing rings can take some time."
msgstr ""
#: ./doc/install-guide/object-storage/section_object-storage-install-config-proxy-node.xml:167(para)
msgid "Copy the <filename>account.ring.gz</filename>, <filename>container.ring.gz</filename>, and <filename>object.ring.gz</filename> files to each of the Proxy and Storage nodes in <filename>/etc/swift</filename>."
msgstr ""
#: ./doc/install-guide/object-storage/section_object-storage-install-config-proxy-node.xml:173(para)
msgid "Make sure the swift user owns all configuration files:"
msgstr ""
#: ./doc/install-guide/object-storage/section_object-storage-install-config-proxy-node.xml:177(para)
msgid "Restart the Proxy service:"
msgstr ""
#: ./doc/install-guide/object-storage/section_object-storage-install-config-proxy-node.xml:181(para)
msgid "Start the Proxy service and configure it to start when the system boots:"
msgstr ""
#: ./doc/install-guide/object-storage/section_object-storage-adding-proxy-server.xml:6(title)
msgid "Add another proxy server"
msgstr ""
#: ./doc/install-guide/object-storage/section_object-storage-adding-proxy-server.xml:7(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/install-guide/object-storage/section_object-storage-adding-proxy-server.xml:12(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/install-guide/object-storage/section_object-storage-adding-proxy-server.xml:25(para)
msgid "Update the list of memcache servers in the <filename>/etc/swift/proxy-server.conf</filename> 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/install-guide/object-storage/section_object-storage-adding-proxy-server.xml:39(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/install-guide/object-storage/section_object-storage-adding-proxy-server.xml:46(para)
msgid "After you sync all nodes, make sure that the admin has keys in <filename>/etc/swift</filename> and the ownership for the ring file is correct."
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/install-guide/object-storage/section_object-storage-network-planning.xml:35(None)
msgid "@@image: '../figures/networking-interactions-swift.png'; md5=2190892da42f344e407b4cef71b8f3cf"
msgstr ""
#: ./doc/install-guide/object-storage/section_object-storage-network-planning.xml:6(title)
msgid "Plan networking for Object Storage"
msgstr ""
#: ./doc/install-guide/object-storage/section_object-storage-network-planning.xml:7(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/install-guide/object-storage/section_object-storage-network-planning.xml:15(para)
msgid "A mandatory public network. Connects to the proxy server."
msgstr ""
#: ./doc/install-guide/object-storage/section_object-storage-network-planning.xml:19(para)
msgid "A mandatory storage network. Not accessible from outside the cluster. All nodes connect to this network."
msgstr ""
#: ./doc/install-guide/object-storage/section_object-storage-network-planning.xml:23(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/install-guide/object-storage/section_object-storage-network-planning.xml:13(para)
msgid "This guide describes the following networks:<placeholder-1/>"
msgstr ""
#: ./doc/install-guide/object-storage/section_object-storage-network-planning.xml:28(para)
msgid "This figure shows the basic architecture for the public network, the storage network, and the optional replication network."
msgstr ""
#: ./doc/install-guide/object-storage/section_object-storage-network-planning.xml:38(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 <literal>STORAGE_LOCAL_NET</literal> IP addresses."
msgstr ""
#: ./doc/install-guide/object-storage/section_object-storage-network-planning.xml:42(para)
msgid "If you configure a replication network in the Ring, the Account, Container and Object servers listen on both the <literal>STORAGE_LOCAL_NET</literal> and <literal>STORAGE_REPLICATION_NET</literal> IP addresses. The rsync daemon only listens on the <literal>STORAGE_REPLICATION_NET</literal> IP address."
msgstr ""
#: ./doc/install-guide/object-storage/section_object-storage-network-planning.xml:50(term)
msgid "Public Network (Publicly routable IP range)"
msgstr ""
#: ./doc/install-guide/object-storage/section_object-storage-network-planning.xml:52(para)
msgid "Provides public IP accessibility to the API endpoints within the cloud infrastructure."
msgstr ""
#: ./doc/install-guide/object-storage/section_object-storage-network-planning.xml:54(para)
msgid "Minimum size: one IP address for each proxy server."
msgstr ""
#: ./doc/install-guide/object-storage/section_object-storage-network-planning.xml:59(term)
msgid "Storage Network (RFC1918 IP Range, not publicly routable)"
msgstr ""
#: ./doc/install-guide/object-storage/section_object-storage-network-planning.xml:62(para)
msgid "Manages all inter-server communications within the Object Storage infrastructure."
msgstr ""
#: ./doc/install-guide/object-storage/section_object-storage-network-planning.xml:64(para)
msgid "Minimum size: one IP address for each storage node and proxy server."
msgstr ""
#: ./doc/install-guide/object-storage/section_object-storage-network-planning.xml:66(para)
msgid "Recommended size: as above, with room for expansion to the largest your cluster size. For example, 255 or CIDR /24."
msgstr ""
#: ./doc/install-guide/object-storage/section_object-storage-network-planning.xml:72(term)
msgid "Replication Network (RFC1918 IP Range, not publicly routable)"
msgstr ""
#: ./doc/install-guide/object-storage/section_object-storage-network-planning.xml:75(para)
msgid "Manages replication-related communications among storage servers within the Object Storage infrastructure."
msgstr ""
#: ./doc/install-guide/object-storage/section_object-storage-network-planning.xml:77(para)
msgid "Recommended size: as for <literal>STORAGE_LOCAL_NET</literal>."
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/install-guide/object-storage/section_object-storage-example-install-arch.xml:52(None)
msgid "@@image: '../figures/swift_install_arch.png'; md5=bbda527d20235d54a95eb29279ba2680"
msgstr ""
#: ./doc/install-guide/object-storage/section_object-storage-example-install-arch.xml:6(title)
msgid "Example of Object Storage installation architecture"
msgstr ""
#: ./doc/install-guide/object-storage/section_object-storage-example-install-arch.xml:9(para)
msgid "Node: A host machine that runs one or more OpenStack Object Storage services."
msgstr ""
#: ./doc/install-guide/object-storage/section_object-storage-example-install-arch.xml:13(para)
msgid "Proxy node: Runs proxy services."
msgstr ""
#: ./doc/install-guide/object-storage/section_object-storage-example-install-arch.xml:16(para)
msgid "Storage node: Runs account, container, and object services. Contains the SQLite databases."
msgstr ""
#: ./doc/install-guide/object-storage/section_object-storage-example-install-arch.xml:20(para)
msgid "Ring: A set of mappings between OpenStack Object Storage data to physical devices."
msgstr ""
#: ./doc/install-guide/object-storage/section_object-storage-example-install-arch.xml:24(para)
msgid "Replica: A copy of an object. By default, three copies are maintained in the cluster."
msgstr ""
#: ./doc/install-guide/object-storage/section_object-storage-example-install-arch.xml:28(para)
msgid "Zone: A logically separate section of the cluster, related to independent failure characteristics."
msgstr ""
#: ./doc/install-guide/object-storage/section_object-storage-example-install-arch.xml:32(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/install-guide/object-storage/section_object-storage-example-install-arch.xml:39(para)
msgid "To increase reliability and performance, you can add additional proxy servers."
msgstr ""
#: ./doc/install-guide/object-storage/section_object-storage-example-install-arch.xml:41(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 ""
#: ./doc/install-guide/object-storage/section_object-storage-install.xml:6(title)
msgid "Install Object Storage"
msgstr ""
#: ./doc/install-guide/object-storage/section_object-storage-install.xml:7(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/install-guide/object-storage/section_object-storage-install.xml:11(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 <link href=\"http://swift.openstack.org/development_saio.html\">http://swift.openstack.org/development_saio.html</link> for manual instructions or <link href=\"http://devstack.org\">http://devstack.org</link> for all-in-one including authentication with the Identity Service (keystone) v2.0 API."
msgstr ""
#: ./doc/install-guide/object-storage/section_object-storage-install.xml:20(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/install-guide/object-storage/section_object-storage-install.xml:29(para)
msgid "Have a copy of the operating system installation media available if you are installing on a new server."
msgstr ""
#: ./doc/install-guide/object-storage/section_object-storage-install.xml:31(para)
msgid "These steps assume you have set up repositories for packages for your operating system as shown in <link linkend=\"basics-packages\">OpenStack Packages</link>."
msgstr ""
#: ./doc/install-guide/object-storage/section_object-storage-install.xml:34(para)
msgid "This document demonstrates how to install a cluster by using the following types of nodes:"
msgstr ""
#: ./doc/install-guide/object-storage/section_object-storage-install.xml:38(para)
msgid "One proxy node which runs the swift-proxy-server processes. The proxy server proxies requests to the appropriate storage nodes."
msgstr ""
#: ./doc/install-guide/object-storage/section_object-storage-install.xml:43(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/install-guide/object-storage/section_object-storage-install.xml:51(para)
msgid "Fewer storage nodes can be used initially, but a minimum of five is recommended for a production cluster."
msgstr ""
#: ./doc/install-guide/object-storage/section_object-storage-install.xml:56(title)
msgid "General installation steps"
msgstr ""
#: ./doc/install-guide/object-storage/section_object-storage-install.xml:59(para)
msgid "Create a <literal>swift</literal> user that the Object Storage Service can use to authenticate with the Identity Service. Choose a password and specify an email address for the <literal>swift</literal> user. Use the <literal>service</literal> tenant and give the user the <literal>admin</literal> role:"
msgstr ""
#: ./doc/install-guide/object-storage/section_object-storage-install.xml:66(replaceable)
msgid "swift@example.com"
msgstr ""
#: ./doc/install-guide/object-storage/section_object-storage-install.xml:70(para)
msgid "Create a service entry for the Object Storage Service:"
msgstr ""
#: ./doc/install-guide/object-storage/section_object-storage-install.xml:88(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 <literal>controller</literal> host name is used:"
msgstr ""
#: ./doc/install-guide/object-storage/section_object-storage-install.xml:110(para)
msgid "Create the configuration directory on all nodes:"
msgstr ""
#: ./doc/install-guide/object-storage/section_object-storage-install.xml:114(para)
msgid "Create <filename>/etc/swift/swift.conf</filename> on all nodes:"
msgstr ""
#: ./doc/install-guide/object-storage/section_object-storage-install.xml:120(para)
msgid "The suffix value in <filename>/etc/swift/swift.conf</filename> 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/install-guide/object-storage/section_object-storage-install.xml:125(para)
msgid "Next, set up your storage nodes and proxy node. This example uses the Identity Service for the common authentication piece."
msgstr ""
#: ./doc/install-guide/object-storage/section_start-storage-node-services.xml:7(title)
msgid "Start services on the storage nodes"
msgstr ""
#: ./doc/install-guide/object-storage/section_start-storage-node-services.xml:8(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/install-guide/object-storage/section_start-storage-node-services.xml:22(para)
msgid "To start all swift services at once, run the command:"
msgstr ""
#: ./doc/install-guide/object-storage/section_start-storage-node-services.xml:24(para)
msgid "To know more about <literal>swift-init</literal> command, run:"
msgstr ""
#: ./doc/install-guide/object-storage/section_object-storage-install-config-storage-nodes.xml:6(title)
msgid "Install and configure storage nodes"
msgstr ""
#: ./doc/install-guide/object-storage/section_object-storage-install-config-storage-nodes.xml:8(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 <link href=\"http://docs.openstack.org/trunk/config-reference/content/\"><citetitle>OpenStack Configuration Reference</citetitle></link> for additional recommendations."
msgstr ""
#: ./doc/install-guide/object-storage/section_object-storage-install-config-storage-nodes.xml:20(para)
msgid "Install storage node packages:"
msgstr ""
#: ./doc/install-guide/object-storage/section_object-storage-install-config-storage-nodes.xml:29(para)
msgid "For each device on the node that you want to use for storage, set up the XFS volume (<literal>/dev/sdb</literal> 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/install-guide/object-storage/section_object-storage-install-config-storage-nodes.xml:46(para)
msgid "Create <filename>/etc/rsyncd.conf</filename>:"
msgstr ""
#: ./doc/install-guide/object-storage/section_object-storage-install-config-storage-nodes.xml:48(para)
msgid "Replace the content of <filename>/etc/rsyncd.conf</filename> with:"
msgstr ""
#: ./doc/install-guide/object-storage/section_object-storage-install-config-storage-nodes.xml:75(para)
msgid "(Optional) If you want to separate rsync and replication traffic to replication network, set <literal>STORAGE_REPLICATION_NET_IP</literal> instead of <literal>STORAGE_LOCAL_NET_IP</literal>:"
msgstr ""
#: ./doc/install-guide/object-storage/section_object-storage-install-config-storage-nodes.xml:83(para)
msgid "Edit the following line in <filename>/etc/default/rsync</filename>:"
msgstr ""
#: ./doc/install-guide/object-storage/section_object-storage-install-config-storage-nodes.xml:88(para)
msgid "Edit the following line in <filename>/etc/xinetd.d/rsync</filename>:"
msgstr ""
#: ./doc/install-guide/object-storage/section_object-storage-install-config-storage-nodes.xml:93(para)
msgid "Start the <systemitem class=\"service\">rsync</systemitem> service:"
msgstr ""
#: ./doc/install-guide/object-storage/section_object-storage-install-config-storage-nodes.xml:96(para)
msgid "Start the <systemitem class=\"service\">xinetd</systemitem> service:"
msgstr ""
#: ./doc/install-guide/object-storage/section_object-storage-install-config-storage-nodes.xml:99(para)
msgid "Start the <systemitem class=\"service\">xinetd</systemitem> service and configure it to start when the system boots:"
msgstr ""
#: ./doc/install-guide/object-storage/section_object-storage-install-config-storage-nodes.xml:105(para)
msgid "The rsync service requires no authentication, so run it on a local, private network."
msgstr ""
#: ./doc/install-guide/object-storage/section_object-storage-install-config-storage-nodes.xml:110(para)
msgid "Create the swift recon cache directory and set its permissions:"
msgstr ""
#: ./doc/install-guide/object-storage/section_object-storage-sys-requirements.xml:11(title)
msgid "System requirements for Object Storage"
msgstr ""
#: ./doc/install-guide/object-storage/section_object-storage-sys-requirements.xml:12(para)
msgid "<emphasis role=\"bold\">Hardware</emphasis>: OpenStack Object Storage is designed to run on commodity hardware."
msgstr ""
#: ./doc/install-guide/object-storage/section_object-storage-sys-requirements.xml:15(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/install-guide/object-storage/section_object-storage-sys-requirements.xml:20(caption)
msgid "Hardware recommendations"
msgstr ""
#: ./doc/install-guide/object-storage/section_object-storage-sys-requirements.xml:27(td)
msgid "Server"
msgstr ""
#: ./doc/install-guide/object-storage/section_object-storage-sys-requirements.xml:28(td)
msgid "Recommended Hardware"
msgstr ""
#: ./doc/install-guide/object-storage/section_object-storage-sys-requirements.xml:34(para)
msgid "Object Storage object servers"
msgstr ""
#: ./doc/install-guide/object-storage/section_object-storage-sys-requirements.xml:36(para) ./doc/install-guide/object-storage/section_object-storage-sys-requirements.xml:65(para) ./doc/install-guide/object-storage/section_object-storage-sys-requirements.xml:75(para)
msgid "Processor: dual quad core"
msgstr ""
#: ./doc/install-guide/object-storage/section_object-storage-sys-requirements.xml:37(para) ./doc/install-guide/object-storage/section_object-storage-sys-requirements.xml:66(para)
msgid "Memory: 8 or 12 GB RAM"
msgstr ""
#: ./doc/install-guide/object-storage/section_object-storage-sys-requirements.xml:38(para)
msgid "Disk space: optimized for cost per GB"
msgstr ""
#: ./doc/install-guide/object-storage/section_object-storage-sys-requirements.xml:39(para) ./doc/install-guide/object-storage/section_object-storage-sys-requirements.xml:67(para)
msgid "Network: one 1 GB Network Interface Card (NIC)"
msgstr ""
#: ./doc/install-guide/object-storage/section_object-storage-sys-requirements.xml:41(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/install-guide/object-storage/section_object-storage-sys-requirements.xml:53(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/install-guide/object-storage/section_object-storage-sys-requirements.xml:62(para)
msgid "Object Storage container/account servers"
msgstr ""
#: ./doc/install-guide/object-storage/section_object-storage-sys-requirements.xml:69(para)
msgid "Optimized for IOPS due to tracking with SQLite databases."
msgstr ""
#: ./doc/install-guide/object-storage/section_object-storage-sys-requirements.xml:73(para)
msgid "Object Storage proxy server"
msgstr ""
#: ./doc/install-guide/object-storage/section_object-storage-sys-requirements.xml:76(para)
msgid "Network: one 1 GB Network Interface Card (NIC)"
msgstr ""
#: ./doc/install-guide/object-storage/section_object-storage-sys-requirements.xml:78(para)
msgid "Higher network throughput offers better performance for supporting many API requests."
msgstr ""
#: ./doc/install-guide/object-storage/section_object-storage-sys-requirements.xml:81(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/install-guide/object-storage/section_object-storage-sys-requirements.xml:90(para)
msgid "<emphasis role=\"bold\">Operating system</emphasis>: OpenStack Object Storage currently runs on Ubuntu, RHEL, CentOS, Fedora, openSUSE, or SLES."
msgstr ""
#: ./doc/install-guide/object-storage/section_object-storage-sys-requirements.xml:93(para)
msgid "<emphasis role=\"bold\">Networking</emphasis>: 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/install-guide/object-storage/section_object-storage-sys-requirements.xml:98(para)
msgid "<emphasis role=\"bold\">Database</emphasis>: For OpenStack Object Storage, a SQLite database is part of the OpenStack Object Storage container and account management process."
msgstr ""
#: ./doc/install-guide/object-storage/section_object-storage-sys-requirements.xml:102(para)
msgid "<emphasis role=\"bold\">Permissions</emphasis>: 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 ""
#. Put one translator per line, in the form of NAME <EMAIL>, YEAR1, YEAR2
#: ./doc/install-guide/object-storage/section_object-storage-sys-requirements.xml:0(None)
msgid "translator-credits"
msgstr ""
View Git Blame Copy Permalink