openstack/openstack-manuals
Code Issues Proposed changes
492fecc62e
openstack-manuals/doc/install-guide/source/locale/install-guide.pot
OpenStack Proposal Bot 492fecc62e Imported Translations from Zanata 
For more information about this automatic import see:
https://wiki.openstack.org/wiki/Translations/Infrastructure

Change-Id: I2e4b8636c944ed7e4f822497c85a7edc81b73e0c
2015-12-04 06:13:25 +00:00

6738 lines
236 KiB
Plaintext
Raw Blame History

# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2015, OpenStack contributors
# This file is distributed under the same license as the Installation Guide package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Installation Guide 0.1\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2015-12-04 06:11+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"
#: ../ceilometer-cinder.rst:2
msgid "Enable Block Storage meters"
msgstr ""
#: ../ceilometer-cinder.rst:4
msgid ""
"Telemetry uses notifications to collect Block Storage service meters. "
"Perform these steps on the controller and Block Storage nodes."
msgstr ""
#: ../ceilometer-cinder.rst:9
msgid "Your environment must include the Block Storage service."
msgstr ""
#: ../ceilometer-cinder.rst:12
msgid "Configure Cinder to use Telemetry"
msgstr ""
# #-#-#-#-# ceilometer-cinder.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# cinder-controller-install.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# cinder-storage-install.pot (Installation Guide 0.1) #-#-#-#-#
#: ../ceilometer-cinder.rst:14 ../cinder-controller-install.rst:258
#: ../cinder-storage-install.rst:160
msgid ""
"Edit the ``/etc/cinder/cinder.conf`` file and complete the following actions:"
msgstr ""
#: ../ceilometer-cinder.rst:17
msgid "In the ``[DEFAULT]`` section, configure notifications:"
msgstr ""
# #-#-#-#-# ceilometer-cinder.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# ceilometer-glance.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# ceilometer-install.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# ceilometer-nova.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# ceilometer-swift.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# cinder-controller-install.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# cinder-storage-install.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# environment-nosql-database.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# environment-sql-database.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# glance-install.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# heat-install.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# horizon-install.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# neutron-compute-install.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# neutron-controller-install.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# nova-compute-install.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# nova-controller-install.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# swift-finalize-installation.pot (Installation Guide 0.1) #-#-#-#-#
#: ../ceilometer-cinder.rst:26 ../ceilometer-glance.rst:34
#: ../ceilometer-install.rst:305 ../ceilometer-nova.rst:120
#: ../ceilometer-swift.rst:115 ../cinder-controller-install.rst:378
#: ../cinder-storage-install.rst:313 ../environment-nosql-database.rst:145
#: ../environment-sql-database.rst:114 ../glance-install.rst:373
#: ../heat-install.rst:488 ../horizon-install.rst:241
#: ../neutron-compute-install.rst:179 ../neutron-controller-install.rst:256
#: ../nova-compute-install.rst:237 ../nova-controller-install.rst:395
#: ../swift-finalize-installation.rst:2
msgid "Finalize installation"
msgstr ""
#: ../ceilometer-cinder.rst:30 ../ceilometer-cinder.rst:44
msgid "Restart the Block Storage services on the controller node:"
msgstr ""
#: ../ceilometer-cinder.rst:36 ../ceilometer-cinder.rst:51
msgid "Restart the Block Storage services on the storage nodes:"
msgstr ""
#: ../ceilometer-cinder.rst:57
msgid ""
"Use the ``cinder-volume-usage-audit`` command on Block Storage nodes to "
"retrieve meters on demand. For more information, see the `Cloud "
"Administrator Guide <http://docs.openstack.org/admin-guide-cloud/ telemetry-"
"data-collection.html#block-storage-audit-script-setup-to-get- "
"notifications>`__."
msgstr ""
#: ../ceilometer-glance.rst:2
msgid "Enable Image service meters"
msgstr ""
#: ../ceilometer-glance.rst:4
msgid ""
"Telemetry uses notifications to collect Image service meters. Perform these "
"steps on the controller node."
msgstr ""
#: ../ceilometer-glance.rst:8
msgid "Configure the Image service to use Telemetry"
msgstr ""
#: ../ceilometer-glance.rst:10
msgid ""
"Edit the ``/etc/glance/glance-api.conf`` and ``/etc/glance/glance-registry."
"conf`` files and complete the following actions:"
msgstr ""
#: ../ceilometer-glance.rst:14
msgid ""
"In the ``[DEFAULT]`` and ``[oslo_messaging_rabbit]`` sections, configure "
"notifications and RabbitMQ message broker access:"
msgstr ""
# #-#-#-#-# ceilometer-glance.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# ceilometer-install.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# ceilometer-nova.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# ceilometer-swift.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# cinder-controller-install.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# cinder-storage-install.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# heat-install.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# nova-compute-install.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# nova-controller-install.pot (Installation Guide 0.1) #-#-#-#-#
#: ../ceilometer-glance.rst:30 ../ceilometer-install.rst:243
#: ../ceilometer-nova.rst:52 ../ceilometer-swift.rst:111
#: ../cinder-controller-install.rst:299 ../cinder-storage-install.rst:199
#: ../heat-install.rst:381 ../nova-compute-install.rst:82
#: ../nova-controller-install.rst:240
msgid ""
"Replace ``RABBIT_PASS`` with the password you chose for the ``openstack`` "
"account in ``RabbitMQ``."
msgstr ""
#: ../ceilometer-glance.rst:38 ../ceilometer-glance.rst:46
msgid "Restart the Image service:"
msgstr ""
# #-#-#-#-# ceilometer-install.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# glance-install.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# heat-install.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# horizon-install.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# keystone-install.pot (Installation Guide 0.1) #-#-#-#-#
#: ../ceilometer-install.rst:2 ../glance-install.rst:2 ../heat-install.rst:4
#: ../horizon-install.rst:2 ../keystone-install.rst:4
msgid "Install and configure"
msgstr ""
#: ../ceilometer-install.rst:4
msgid ""
"This section describes how to install and configure the Telemetry service, "
"code-named ceilometer, on the controller node. The Telemetry service "
"collects measurements from most OpenStack services and optionally triggers "
"alarms."
msgstr ""
# #-#-#-#-# ceilometer-install.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# ceilometer-swift.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# cinder-controller-install.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# cinder-storage-install.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# environment-packages.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# glance-install.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# heat-install.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# keystone-install.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# keystone-services.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# neutron-controller-install.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# nova-controller-install.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# swift-controller-install.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# swift-storage-install.pot (Installation Guide 0.1) #-#-#-#-#
#: ../ceilometer-install.rst:10 ../ceilometer-swift.rst:12
#: ../cinder-controller-install.rst:14 ../cinder-storage-install.rst:19
#: ../environment-packages.rst:31 ../glance-install.rst:11
#: ../heat-install.rst:12 ../keystone-install.rst:14
#: ../keystone-services.rst:10 ../neutron-controller-install.rst:7
#: ../nova-controller-install.rst:10 ../swift-controller-install.rst:16
#: ../swift-storage-install.rst:20
msgid "Prerequisites"
msgstr ""
#: ../ceilometer-install.rst:12
msgid ""
"Before you install and configure the Telemetry service, you must create a "
"database, service credentials, and API endpoints. However, unlike other "
"services, the Telemetry service uses a NoSQL database. See :ref:`environment-"
"nosql-database` to install and configure MongoDB before proceeding further."
msgstr ""
#: ../ceilometer-install.rst:20 ../ceilometer-install.rst:46
msgid "Create the ``ceilometer`` database:"
msgstr ""
#: ../ceilometer-install.rst:42 ../ceilometer-install.rst:60
msgid "Replace ``CEILOMETER_DBPASS`` with a suitable password."
msgstr ""
# #-#-#-#-# ceilometer-install.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# ceilometer-verify.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# cinder-controller-install.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# cinder-verify.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# glance-install.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# glance-verify.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# heat-install.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# neutron-controller-install.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# neutron-verify.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# nova-controller-install.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# nova-verify.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# swift-controller-install.pot (Installation Guide 0.1) #-#-#-#-#
#: ../ceilometer-install.rst:62 ../ceilometer-verify.rst:12
#: ../cinder-controller-install.rst:47 ../cinder-verify.rst:12
#: ../glance-install.rst:44 ../glance-verify.rst:23 ../heat-install.rst:46
#: ../neutron-controller-install.rst:39 ../neutron-verify.rst:4
#: ../nova-controller-install.rst:43 ../nova-verify.rst:10
#: ../swift-controller-install.rst:30
msgid ""
"Source the ``admin`` credentials to gain access to admin-only CLI commands:"
msgstr ""
# #-#-#-#-# ceilometer-install.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# cinder-controller-install.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# glance-install.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# heat-install.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# neutron-controller-install.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# nova-controller-install.pot (Installation Guide 0.1) #-#-#-#-#
#: ../ceilometer-install.rst:69 ../cinder-controller-install.rst:54
#: ../glance-install.rst:51 ../heat-install.rst:53
#: ../neutron-controller-install.rst:46 ../nova-controller-install.rst:50
msgid "To create the service credentials, complete these steps:"
msgstr ""
#: ../ceilometer-install.rst:71
msgid "Create the ``ceilometer`` user:"
msgstr ""
#: ../ceilometer-install.rst:87
msgid "Add the ``admin`` role to the ``ceilometer`` user."
msgstr ""
# #-#-#-#-# ceilometer-install.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# ceilometer-swift.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# cinder-controller-install.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# glance-install.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# heat-install.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# keystone-users.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# launch-instance-private.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# neutron-controller-install.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# nova-controller-install.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# swift-controller-install.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# swift-initial-rings.pot (Installation Guide 0.1) #-#-#-#-#
#: ../ceilometer-install.rst:95 ../ceilometer-swift.rst:45
#: ../cinder-controller-install.rst:80 ../glance-install.rst:78
#: ../heat-install.rst:79 ../heat-install.rst:256 ../heat-install.rst:279
#: ../keystone-users.rst:76 ../keystone-users.rst:170
#: ../launch-instance-private.rst:224 ../neutron-controller-install.rst:73
#: ../nova-controller-install.rst:76 ../swift-controller-install.rst:62
#: ../swift-initial-rings.rst:32 ../swift-initial-rings.rst:109
#: ../swift-initial-rings.rst:186
msgid "This command provides no output."
msgstr ""
#: ../ceilometer-install.rst:97
msgid "Create the ``ceilometer`` service entity:"
msgstr ""
#: ../ceilometer-install.rst:113
msgid "Create the Telemetry service API endpoints:"
msgstr ""
# #-#-#-#-# ceilometer-install.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# ceilometer-nova.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# cinder-controller-install.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# cinder-storage-install.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# environment-messaging.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# environment-nosql-database.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# environment-ntp-controller.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# environment-ntp-other.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# environment-sql-database.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# glance-install.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# heat-install.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# horizon-install.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# keystone-install.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# nova-compute-install.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# nova-controller-install.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# swift-controller-install.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# swift-storage-install.pot (Installation Guide 0.1) #-#-#-#-#
#: ../ceilometer-install.rst:166 ../ceilometer-nova.rst:8
#: ../cinder-controller-install.rst:224 ../cinder-storage-install.rst:134
#: ../environment-messaging.rst:16 ../environment-nosql-database.rst:16
#: ../environment-ntp-controller.rst:9 ../environment-ntp-other.rst:10
#: ../environment-sql-database.rst:11 ../glance-install.rst:149
#: ../heat-install.rst:307 ../horizon-install.rst:23
#: ../keystone-install.rst:57 ../nova-compute-install.rst:25
#: ../nova-controller-install.rst:147 ../swift-controller-install.rst:133
#: ../swift-storage-install.rst:139
msgid "Install and configure components"
msgstr ""
# #-#-#-#-# ceilometer-install.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# ceilometer-nova.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# ceilometer-swift.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# cinder-controller-install.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# cinder-storage-install.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# environment-ntp-controller.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# environment-ntp-other.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# environment-sql-database.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# glance-install.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# heat-install.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# horizon-install.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# nova-compute-install.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# nova-controller-install.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# swift-controller-install.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# swift-storage-install.pot (Installation Guide 0.1) #-#-#-#-#
#: ../ceilometer-install.rst:170 ../ceilometer-install.rst:183
#: ../ceilometer-install.rst:194 ../ceilometer-nova.rst:12
#: ../ceilometer-nova.rst:20 ../ceilometer-nova.rst:28
#: ../ceilometer-swift.rst:50 ../cinder-controller-install.rst:228
#: ../cinder-controller-install.rst:236 ../cinder-controller-install.rst:244
#: ../cinder-storage-install.rst:138 ../cinder-storage-install.rst:146
#: ../cinder-storage-install.rst:154 ../environment-ntp-controller.rst:11
#: ../environment-ntp-other.rst:12 ../environment-sql-database.rst:13
#: ../glance-install.rst:157 ../glance-install.rst:165
#: ../glance-install.rst:176 ../glance-install.rst:352 ../heat-install.rst:315
#: ../heat-install.rst:324 ../heat-install.rst:333 ../horizon-install.rst:31
#: ../horizon-install.rst:39 ../horizon-install.rst:47
#: ../horizon-install.rst:55 ../nova-compute-install.rst:31
#: ../nova-compute-install.rst:39 ../nova-compute-install.rst:47
#: ../nova-controller-install.rst:153 ../nova-controller-install.rst:164
#: ../nova-controller-install.rst:175 ../nova-controller-install.rst:185
#: ../swift-controller-install.rst:137 ../swift-storage-install.rst:147
msgid "Install the packages:"
msgstr ""
#: ../ceilometer-install.rst:205
msgid ""
"Respond to prompts for :doc:`Identity service credentials <debconf/debconf-"
"keystone-authtoken>`, :doc:`service endpoint registration <debconf/debconf-"
"api-endpoints>`, and :doc:`message broker credentials <debconf/debconf-"
"rabbitmq>`."
msgstr ""
# #-#-#-#-# ceilometer-install.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# ceilometer-nova.pot (Installation Guide 0.1) #-#-#-#-#
#: ../ceilometer-install.rst:210 ../ceilometer-nova.rst:34
msgid ""
"Edit the ``/etc/ceilometer/ceilometer.conf`` file and complete the following "
"actions:"
msgstr ""
# #-#-#-#-# ceilometer-install.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# cinder-controller-install.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# cinder-storage-install.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# glance-install.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# heat-install.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# keystone-install.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# neutron-controller-install-option1.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# neutron-controller-install-option2.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# nova-controller-install.pot (Installation Guide 0.1) #-#-#-#-#
#: ../ceilometer-install.rst:213 ../cinder-controller-install.rst:263
#: ../cinder-storage-install.rst:163 ../glance-install.rst:187
#: ../glance-install.rst:271 ../heat-install.rst:345
#: ../keystone-install.rst:133 ../neutron-controller-install-option1.rst:111
#: ../neutron-controller-install-option2.rst:69
#: ../nova-controller-install.rst:204
msgid "In the ``[database]`` section, configure database access:"
msgstr ""
#: ../ceilometer-install.rst:221
msgid ""
"Replace ``CEILOMETER_DBPASS`` with the password you chose for the Telemetry "
"service database. You must escape special characters such as ':', '/', '+', "
"and '@' in the connection string in accordance with RFC2396."
msgstr ""
# #-#-#-#-# ceilometer-install.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# ceilometer-nova.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# cinder-controller-install.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# cinder-storage-install.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# heat-install.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# nova-controller-install.pot (Installation Guide 0.1) #-#-#-#-#
#: ../ceilometer-install.rst:228 ../ceilometer-nova.rst:37
#: ../cinder-controller-install.rst:284 ../cinder-storage-install.rst:184
#: ../heat-install.rst:366 ../nova-controller-install.rst:225
msgid ""
"In the ``[DEFAULT]`` and ``[oslo_messaging_rabbit]`` sections, configure "
"``RabbitMQ`` message queue access:"
msgstr ""
# #-#-#-#-# ceilometer-install.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# ceilometer-nova.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# cinder-controller-install.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# cinder-storage-install.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# neutron-compute-install.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# neutron-controller-install-option1.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# neutron-controller-install-option2.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# nova-compute-install.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# nova-controller-install.pot (Installation Guide 0.1) #-#-#-#-#
#: ../ceilometer-install.rst:246 ../ceilometer-nova.rst:55
#: ../cinder-controller-install.rst:302 ../cinder-storage-install.rst:202
#: ../neutron-compute-install.rst:87
#: ../neutron-controller-install-option1.rst:160
#: ../neutron-controller-install-option2.rst:119
#: ../nova-compute-install.rst:85 ../nova-controller-install.rst:243
msgid ""
"In the ``[DEFAULT]`` and ``[keystone_authtoken]`` sections, configure "
"Identity service access:"
msgstr ""
# #-#-#-#-# ceilometer-install.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# ceilometer-nova.pot (Installation Guide 0.1) #-#-#-#-#
#: ../ceilometer-install.rst:266 ../ceilometer-install.rst:282
#: ../ceilometer-nova.rst:92
msgid ""
"Replace ``CEILOMETER_PASS`` with the password you chose for the "
"``ceilometer`` user in the Identity service."
msgstr ""
# #-#-#-#-# ceilometer-install.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# ceilometer-nova.pot (Installation Guide 0.1) #-#-#-#-#
#: ../ceilometer-install.rst:269 ../ceilometer-nova.rst:78
msgid ""
"In the ``[service_credentials]`` section, configure service credentials:"
msgstr ""
#: ../ceilometer-install.rst:287
msgid "In the ``[collector]`` section, configure the dispatcher:"
msgstr ""
# #-#-#-#-# ceilometer-install.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# ceilometer-nova.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# cinder-controller-install.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# cinder-storage-install.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# glance-install.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# heat-install.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# keystone-install.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# neutron-compute-install.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# neutron-controller-install-option1.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# neutron-controller-install-option2.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# neutron-controller-install.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# nova-compute-install.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# nova-controller-install.pot (Installation Guide 0.1) #-#-#-#-#
#: ../ceilometer-install.rst:295 ../ceilometer-nova.rst:95
#: ../cinder-controller-install.rst:349 ../cinder-storage-install.rst:303
#: ../glance-install.rst:259 ../glance-install.rst:333 ../heat-install.rst:447
#: ../keystone-install.rst:179 ../neutron-compute-install.rst:125
#: ../neutron-controller-install-option1.rst:223
#: ../neutron-controller-install-option1.rst:362
#: ../neutron-controller-install-option2.rst:182
#: ../neutron-controller-install-option2.rst:347
#: ../neutron-controller-install-option2.rst:376
#: ../neutron-controller-install.rst:215 ../nova-compute-install.rst:216
#: ../nova-controller-install.rst:369
msgid ""
"(Optional) To assist with troubleshooting, enable verbose logging in the "
"``[DEFAULT]`` section:"
msgstr ""
#: ../ceilometer-install.rst:309 ../ceilometer-install.rst:329
msgid ""
"Start the Telemetry services and configure them to start when the system "
"boots:"
msgstr ""
#: ../ceilometer-install.rst:349
msgid "Restart the Telemetry services:"
msgstr ""
# #-#-#-#-# ceilometer-next-steps.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# cinder-next-steps.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# heat-next-steps.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# horizon-next-steps.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# neutron-next-steps.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# swift-next-steps.pot (Installation Guide 0.1) #-#-#-#-#
#: ../ceilometer-next-steps.rst:3 ../cinder-next-steps.rst:5
#: ../heat-next-steps.rst:4 ../horizon-next-steps.rst:3
#: ../neutron-next-steps.rst:3 ../swift-next-steps.rst:3
msgid "Next steps"
msgstr ""
#: ../ceilometer-next-steps.rst:5
msgid ""
"Your OpenStack environment now includes Telemetry. You can :ref:`launch-"
"instance` or add more services to your environment."
msgstr ""
#: ../ceilometer-nova.rst:2
msgid "Enable Compute service meters"
msgstr ""
#: ../ceilometer-nova.rst:4
msgid ""
"Telemetry uses a combination of notifications and an agent to collect "
"Compute meters. Perform these steps on each compute node."
msgstr ""
#: ../ceilometer-nova.rst:75
msgid ""
"Replace ``CEILOMETER_PASS`` with the password you chose for the Telemetry "
"service database."
msgstr ""
#: ../ceilometer-nova.rst:105
msgid "Configure Compute to use Telemetry"
msgstr ""
#: ../ceilometer-nova.rst:107
msgid ""
"Edit the ``/etc/nova/nova.conf`` file and configure notifications in the "
"``[DEFAULT]`` section:"
msgstr ""
#: ../ceilometer-nova.rst:124 ../ceilometer-nova.rst:133
msgid "Start the agent and configure it to start when the system boots:"
msgstr ""
# #-#-#-#-# ceilometer-nova.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# neutron-compute-install.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# nova-compute-install.pot (Installation Guide 0.1) #-#-#-#-#
#: ../ceilometer-nova.rst:142 ../ceilometer-nova.rst:156
#: ../neutron-compute-install.rst:192 ../neutron-compute-install.rst:217
#: ../neutron-compute-install.rst:233 ../nova-compute-install.rst:298
msgid "Restart the Compute service:"
msgstr ""
#: ../ceilometer-nova.rst:150
msgid "Restart the agent:"
msgstr ""
#: ../ceilometer-swift.rst:2
msgid "Enable Object Storage meters"
msgstr ""
#: ../ceilometer-swift.rst:4
msgid ""
"Telemetry uses a combination of polling and notifications to collect Object "
"Storage meters."
msgstr ""
#: ../ceilometer-swift.rst:9
msgid "Your environment must include the Object Storage service."
msgstr ""
#: ../ceilometer-swift.rst:14
msgid ""
"The Telemetry service requires access to the Object Storage service using "
"the ``ResellerAdmin`` role. Perform these steps on the controller node."
msgstr ""
#: ../ceilometer-swift.rst:18
msgid ""
"Source the ``admin`` credentials to gain access to admin-only CLI commands."
msgstr ""
#: ../ceilometer-swift.rst:25
msgid "Create the ``ResellerAdmin`` role:"
msgstr ""
#: ../ceilometer-swift.rst:37
msgid "Add the ``ResellerAdmin`` role to the ``ceilometer`` user:"
msgstr ""
#: ../ceilometer-swift.rst:48
msgid "Install components"
msgstr ""
#: ../ceilometer-swift.rst:71
msgid "Configure Object Storage to use Telemetry"
msgstr ""
#: ../ceilometer-swift.rst:73
msgid ""
"Perform these steps on the controller and any other nodes that run the "
"Object Storage proxy service."
msgstr ""
# #-#-#-#-# ceilometer-swift.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# swift-controller-install.pot (Installation Guide 0.1) #-#-#-#-#
#: ../ceilometer-swift.rst:76 ../swift-controller-include.txt:1
msgid ""
"Edit the ``/etc/swift/proxy-server.conf`` file and complete the following "
"actions:"
msgstr ""
#: ../ceilometer-swift.rst:79
msgid ""
"In the ``[filter:keystoneauth]`` section, add the ``ResellerAdmin`` role:"
msgstr ""
#: ../ceilometer-swift.rst:88
msgid "In the ``[pipeline:main]`` section, add ``ceilometer``:"
msgstr ""
#: ../ceilometer-swift.rst:98
msgid "In the ``[filter:ceilometer]`` section, configure notifications:"
msgstr ""
#: ../ceilometer-swift.rst:119 ../ceilometer-swift.rst:127
msgid "Restart the Object Storage proxy service:"
msgstr ""
# #-#-#-#-# ceilometer-verify.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# cinder-verify.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# environment-ntp-verify.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# glance-verify.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# heat-verify.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# horizon-verify.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# keystone-verify.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# launch-instance-networks-private.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# neutron-verify.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# nova-verify.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# swift-verify.pot (Installation Guide 0.1) #-#-#-#-#
#: ../ceilometer-verify.rst:2 ../cinder-verify.rst:4
#: ../environment-ntp-verify.rst:4 ../glance-verify.rst:2 ../heat-verify.rst:4
#: ../horizon-verify.rst:2 ../keystone-verify.rst:2
#: ../launch-instance-networks-private.rst:196 ../neutron-verify.rst:2
#: ../nova-verify.rst:2 ../swift-verify.rst:2
msgid "Verify operation"
msgstr ""
#: ../ceilometer-verify.rst:4
msgid ""
"Verify operation of the Telemetry service. These steps only include the "
"Image service meters to reduce clutter. Environments with ceilometer "
"integration for additional services contain more meters."
msgstr ""
# #-#-#-#-# ceilometer-verify.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# environment-ntp-controller.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# swift-initial-rings.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# swift-verify.pot (Installation Guide 0.1) #-#-#-#-#
#: ../ceilometer-verify.rst:10 ../environment-ntp-controller.rst:6
#: ../swift-initial-rings.rst:15 ../swift-verify.rst:8
msgid "Perform these steps on the controller node."
msgstr ""
#: ../ceilometer-verify.rst:19
msgid "List available meters:"
msgstr ""
#: ../ceilometer-verify.rst:31
msgid "Download the CirrOS image from the Image service:"
msgstr ""
#: ../ceilometer-verify.rst:38
msgid ""
"List available meters again to validate detection of the image download:"
msgstr ""
#: ../ceilometer-verify.rst:53
msgid "Retrieve usage statistics from the ``image.download`` meter:"
msgstr ""
#: ../ceilometer-verify.rst:64
msgid "Remove the previously downloaded image file ``/tmp/cirros.img``:"
msgstr ""
#: ../ceilometer.rst:5
msgid "Add the Telemetry service"
msgstr ""
# #-#-#-#-# cinder-controller-install.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# neutron-controller-install.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# nova-controller-install.pot (Installation Guide 0.1) #-#-#-#-#
#: ../cinder-controller-install.rst:4 ../neutron-controller-install.rst:2
#: ../nova-controller-install.rst:2
msgid "Install and configure controller node"
msgstr ""
#: ../cinder-controller-install.rst:6
msgid ""
"This section describes how to install and configure the Block Storage "
"service, code-named cinder, on the controller node. This service requires at "
"least one additional storage node that provides volumes to instances."
msgstr ""
#: ../cinder-controller-install.rst:16
msgid ""
"Before you install and configure the Block Storage service, you must create "
"a database, service credentials, and API endpoints."
msgstr ""
# #-#-#-#-# cinder-controller-install.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# glance-install.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# heat-install.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# neutron-controller-install.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# nova-controller-install.pot (Installation Guide 0.1) #-#-#-#-#
#: ../cinder-controller-install.rst:19 ../glance-install.rst:16
#: ../heat-install.rst:18 ../neutron-controller-install.rst:12
#: ../nova-controller-install.rst:15
msgid "To create the database, complete these steps:"
msgstr ""
# #-#-#-#-# cinder-controller-install.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# glance-install.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# heat-install.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# keystone-install.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# neutron-controller-install.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# nova-controller-install.pot (Installation Guide 0.1) #-#-#-#-#
#: ../cinder-controller-install.rst:21 ../glance-install.rst:18
#: ../heat-install.rst:20 ../keystone-install.rst:21
#: ../neutron-controller-install.rst:14 ../nova-controller-install.rst:17
msgid ""
"Use the database access client to connect to the database server as the "
"``root`` user:"
msgstr ""
#: ../cinder-controller-install.rst:28
msgid "Create the ``cinder`` database:"
msgstr ""
#: ../cinder-controller-install.rst:34
msgid "Grant proper access to the ``cinder`` database:"
msgstr ""
#: ../cinder-controller-install.rst:43
msgid "Replace ``CINDER_DBPASS`` with a suitable password."
msgstr ""
# #-#-#-#-# cinder-controller-install.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# glance-install.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# heat-install.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# keystone-install.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# neutron-controller-install.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# nova-controller-install.pot (Installation Guide 0.1) #-#-#-#-#
#: ../cinder-controller-install.rst:45 ../glance-install.rst:42
#: ../heat-install.rst:44 ../keystone-install.rst:45
#: ../neutron-controller-install.rst:37 ../nova-controller-install.rst:41
msgid "Exit the database access client."
msgstr ""
#: ../cinder-controller-install.rst:56
msgid "Create a ``cinder`` user:"
msgstr ""
#: ../cinder-controller-install.rst:72
msgid "Add the ``admin`` role to the ``cinder`` user:"
msgstr ""
#: ../cinder-controller-install.rst:82
msgid "Create the ``cinder`` and ``cinderv2`` service entities:"
msgstr ""
#: ../cinder-controller-install.rst:114
msgid "The Block Storage services require two service entities."
msgstr ""
#: ../cinder-controller-install.rst:116
msgid "Create the Block Storage service API endpoints:"
msgstr ""
#: ../cinder-controller-install.rst:220
msgid "The Block Storage services require endpoints for each service entity."
msgstr ""
# #-#-#-#-# cinder-controller-install.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# glance-install.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# heat-install.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# nova-controller-install.pot (Installation Guide 0.1) #-#-#-#-#
#: ../cinder-controller-install.rst:252 ../glance-install.rst:358
#: ../heat-install.rst:470 ../nova-controller-install.rst:193
msgid ""
"Respond to prompts for :doc:`database management <debconf/debconf-dbconfig-"
"common>`, :doc:`Identity service credentials <debconf/debconf-keystone-"
"authtoken>`, :doc:`service endpoint registration <debconf/debconf-api-"
"endpoints>`, and :doc:`message broker credentials <debconf/debconf-"
"rabbitmq>`."
msgstr ""
# #-#-#-#-# cinder-controller-install.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# cinder-storage-install.pot (Installation Guide 0.1) #-#-#-#-#
#: ../cinder-controller-install.rst:281 ../cinder-storage-install.rst:181
msgid ""
"Replace ``CINDER_DBPASS`` with the password you chose for the Block Storage "
"database."
msgstr ""
# #-#-#-#-# cinder-controller-install.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# cinder-storage-install.pot (Installation Guide 0.1) #-#-#-#-#
#: ../cinder-controller-install.rst:322 ../cinder-storage-install.rst:222
msgid ""
"Replace ``CINDER_PASS`` with the password you chose for the ``cinder`` user "
"in the Identity service."
msgstr ""
# #-#-#-#-# cinder-controller-install.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# cinder-storage-install.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# glance-install.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# neutron-compute-install.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# neutron-controller-install-option1.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# neutron-controller-install-option2.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# nova-compute-install.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# nova-controller-install.pot (Installation Guide 0.1) #-#-#-#-#
#: ../cinder-controller-install.rst:327 ../cinder-storage-install.rst:227
#: ../glance-install.rst:233 ../glance-install.rst:317
#: ../neutron-compute-install.rst:112
#: ../neutron-controller-install-option1.rst:185
#: ../neutron-controller-install-option2.rst:144
#: ../nova-compute-install.rst:110 ../nova-controller-install.rst:268
msgid ""
"Comment out or remove any other options in the ``[keystone_authtoken]`` "
"section."
msgstr ""
# #-#-#-#-# cinder-controller-install.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# nova-controller-install.pot (Installation Guide 0.1) #-#-#-#-#
#: ../cinder-controller-install.rst:330 ../nova-controller-install.rst:271
msgid ""
"In the ``[DEFAULT]`` section, configure the ``my_ip`` option to use the "
"management interface IP address of the controller node:"
msgstr ""
# #-#-#-#-# cinder-controller-install.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# cinder-storage-install.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# neutron-compute-install.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# neutron-controller-install-option1.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# neutron-controller-install-option2.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# nova-compute-install.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# nova-controller-install.pot (Installation Guide 0.1) #-#-#-#-#
#: ../cinder-controller-install.rst:341 ../cinder-storage-install.rst:295
#: ../neutron-compute-install.rst:117
#: ../neutron-controller-install-option1.rst:215
#: ../neutron-controller-install-option2.rst:174
#: ../nova-compute-install.rst:198 ../nova-compute-install.rst:208
#: ../nova-controller-install.rst:333 ../nova-controller-install.rst:343
#: ../nova-controller-install.rst:353
msgid "In the ``[oslo_concurrency]`` section, configure the lock path:"
msgstr ""
#: ../cinder-controller-install.rst:360
msgid "Populate the Block Storage database:"
msgstr ""
#: ../cinder-controller-install.rst:367
msgid "Configure Compute to use Block Storage"
msgstr ""
#: ../cinder-controller-install.rst:369
msgid "Edit the ``/etc/nova/nova.conf`` file and add the following to it:"
msgstr ""
# #-#-#-#-# cinder-controller-install.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# neutron-controller-install.pot (Installation Guide 0.1) #-#-#-#-#
#: ../cinder-controller-install.rst:382 ../cinder-controller-install.rst:398
#: ../neutron-controller-install.rst:281 ../neutron-controller-install.rst:319
#: ../neutron-controller-install.rst:362
msgid "Restart the Compute API service:"
msgstr ""
#: ../cinder-controller-install.rst:388
msgid ""
"Start the Block Storage services and configure them to start when the system "
"boots:"
msgstr ""
#: ../cinder-controller-install.rst:404
msgid "Restart the Block Storage services:"
msgstr ""
# #-#-#-#-# cinder-controller-install.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# glance-install.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# heat-install.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# keystone-install.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# neutron-controller-install.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# nova-compute-install.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# nova-controller-install.pot (Installation Guide 0.1) #-#-#-#-#
#: ../cinder-controller-install.rst:413 ../glance-install.rst:396
#: ../heat-install.rst:514 ../keystone-install.rst:569
#: ../neutron-controller-install.rst:387 ../nova-compute-install.rst:306
#: ../nova-controller-install.rst:444
msgid "By default, the Ubuntu packages create an SQLite database."
msgstr ""
# #-#-#-#-# cinder-controller-install.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# glance-install.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# heat-install.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# keystone-install.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# neutron-controller-install.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# nova-compute-install.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# nova-controller-install.pot (Installation Guide 0.1) #-#-#-#-#
#: ../cinder-controller-install.rst:415 ../glance-install.rst:398
#: ../heat-install.rst:516 ../keystone-install.rst:571
#: ../neutron-controller-install.rst:389 ../nova-compute-install.rst:308
#: ../nova-controller-install.rst:446
msgid ""
"Because this configuration uses an SQL database server, you can remove the "
"SQLite database file:"
msgstr ""
#: ../cinder-next-steps.rst:7
msgid ""
"Your OpenStack environment now includes Block Storage. You can :doc:`launch "
"an instance <launch-instance>` or add more services to your environment in "
"the following chapters."
msgstr ""
#: ../cinder-storage-install.rst:4
msgid "Install and configure a storage node"
msgstr ""
#: ../cinder-storage-install.rst:6
msgid ""
"This section describes how to install and configure storage nodes for the "
"Block Storage service. For simplicity, this configuration references one "
"storage node with an empty local block storage device. The instructions use "
"``/dev/sdb``, but you can substitute a different value for your particular "
"node."
msgstr ""
#: ../cinder-storage-install.rst:12
msgid ""
"The service provisions logical volumes on this device using the :term:`LVM "
"<Logical Volume Manager (LVM)>` driver and provides them to instances via :"
"term:`iSCSI` transport. You can follow these instructions with minor "
"modifications to horizontally scale your environment with additional storage "
"nodes."
msgstr ""
#: ../cinder-storage-install.rst:21
msgid ""
"Before you install and configure the Block Storage service on the storage "
"node, you must prepare the storage device."
msgstr ""
#: ../cinder-storage-install.rst:26
msgid "Perform these steps on the storage node."
msgstr ""
# #-#-#-#-# cinder-storage-install.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# swift-storage-install.pot (Installation Guide 0.1) #-#-#-#-#
#: ../cinder-storage-install.rst:28 ../swift-storage-install.rst:29
msgid "Install the supporting utility packages:"
msgstr ""
#: ../cinder-storage-install.rst:32 ../cinder-storage-install.rst:47
msgid "Install the LVM packages:"
msgstr ""
#: ../cinder-storage-install.rst:38
msgid ""
"(Optional) If you intend to use non-raw image types such as QCOW2 and VMDK, "
"install the QEMU package:"
msgstr ""
#: ../cinder-storage-install.rst:53
msgid ""
"Start the LVM metadata service and configure it to start when the system "
"boots:"
msgstr ""
#: ../cinder-storage-install.rst:69
msgid "Some distributions include LVM by default."
msgstr ""
#: ../cinder-storage-install.rst:71
msgid "Create the LVM physical volume ``/dev/sdb``:"
msgstr ""
#: ../cinder-storage-install.rst:78
msgid "Create the LVM volume group ``cinder-volumes``:"
msgstr ""
#: ../cinder-storage-install.rst:85
msgid "The Block Storage service creates logical volumes in this volume group."
msgstr ""
#: ../cinder-storage-install.rst:87
msgid ""
"Only instances can access Block Storage volumes. However, the underlying "
"operating system manages the devices associated with the volumes. By "
"default, the LVM volume scanning tool scans the ``/dev`` directory for block "
"storage devices that contain volumes. If projects use LVM on their volumes, "
"the scanning tool detects these volumes and attempts to cache them which can "
"cause a variety of problems with both the underlying operating system and "
"project volumes. You must reconfigure LVM to scan only the devices that "
"contain the ``cinder-volume`` volume group. Edit the ``/etc/lvm/lvm.conf`` "
"file and complete the following actions:"
msgstr ""
#: ../cinder-storage-install.rst:98
msgid ""
"In the ``devices`` section, add a filter that accepts the ``/dev/sdb`` "
"device and rejects all other devices:"
msgstr ""
#: ../cinder-storage-install.rst:107
msgid ""
"Each item in the filter array begins with ``a`` for **accept** or ``r`` for "
"**reject** and includes a regular expression for the device name. The array "
"must end with ``r/.*/`` to reject any remaining devices. You can use the :"
"command:`vgs -vvvv` command to test filters."
msgstr ""
#: ../cinder-storage-install.rst:115
msgid ""
"If your storage nodes use LVM on the operating system disk, you must also "
"add the associated device to the filter. For example, if the ``/dev/sda`` "
"device contains the operating system:"
msgstr ""
#: ../cinder-storage-install.rst:123
msgid ""
"Similarly, if your compute nodes use LVM on the operating system disk, you "
"must also modify the filter in the ``/etc/lvm/lvm.conf`` file on those nodes "
"to include only the operating system disk. For example, if the ``/dev/sda`` "
"device contains the operating system:"
msgstr ""
# #-#-#-#-# cinder-storage-install.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# nova-compute-install.pot (Installation Guide 0.1) #-#-#-#-#
#: ../cinder-storage-install.rst:230 ../nova-compute-install.rst:132
msgid "In the ``[DEFAULT]`` section, configure the ``my_ip`` option:"
msgstr ""
#: ../cinder-storage-install.rst:238
msgid ""
"Replace ``MANAGEMENT_INTERFACE_IP_ADDRESS`` with the IP address of the "
"management network interface on your storage node, typically 10.0.0.41 for "
"the first node in the :ref:`example architecture <overview-example-"
"architectures>`."
msgstr ""
#: ../cinder-storage-install.rst:245 ../cinder-storage-install.rst:260
msgid ""
"In the ``[lvm]`` section, configure the LVM back end with the LVM driver, "
"``cinder-volumes`` volume group, iSCSI protocol, and appropriate iSCSI "
"service:"
msgstr ""
#: ../cinder-storage-install.rst:273
msgid "In the ``[DEFAULT]`` section, enable the LVM back end:"
msgstr ""
#: ../cinder-storage-install.rst:283
msgid ""
"Back-end names are arbitrary. As an example, this guide uses the name of the "
"driver as the name of the back end."
msgstr ""
#: ../cinder-storage-install.rst:286
msgid ""
"In the ``[DEFAULT]`` section, configure the location of the Image service:"
msgstr ""
#: ../cinder-storage-install.rst:317 ../cinder-storage-install.rst:327
msgid ""
"Start the Block Storage volume service including its dependencies and "
"configure them to start when the system boots:"
msgstr ""
#: ../cinder-storage-install.rst:337
msgid "Restart the Block Storage volume service including its dependencies:"
msgstr ""
#: ../cinder-storage-install.rst:344
msgid ""
"By default, the Ubuntu packages create an SQLite database. Because this "
"configuration uses an SQL database server, remove the SQLite database file:"
msgstr ""
#: ../cinder-verify.rst:6
msgid "Verify operation of the Block Storage service."
msgstr ""
# #-#-#-#-# cinder-verify.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# nova-verify.pot (Installation Guide 0.1) #-#-#-#-#
#: ../cinder-verify.rst:10 ../nova-verify.rst:8
msgid "Perform these commands on the controller node."
msgstr ""
#: ../cinder-verify.rst:19
msgid "List service components to verify successful launch of each process:"
msgstr ""
#: ../cinder.rst:5
msgid "Add the Block Storage service"
msgstr ""
#: ../cinder.rst:15
msgid ""
"The OpenStack Block Storage service provides block storage devices to guest "
"instances. The method in which the storage is provisioned and consumed is "
"determined by the Block Storage driver, or drivers in the case of a multi-"
"backend configuration. There are a variety of drivers that are available: "
"NAS/SAN, NFS, iSCSI, Ceph, and more. The Block Storage API and scheduler "
"services typically run on the controller nodes. Depending upon the drivers "
"used, the volume service can run on controllers, compute nodes, or "
"standalone storage nodes. For more information, see the `Configuration "
"Reference <http://docs.openstack.org/liberty/ config-reference/content/"
"section_volume-drivers.html>`__."
msgstr ""
#: ../cinder.rst:29
msgid ""
"This chapter omits the backup manager because it depends on the Object "
"Storage service."
msgstr ""
#: ../debconf/debconf-api-endpoints.rst:5
msgid "Register API endpoints"
msgstr ""
#: ../debconf/debconf-api-endpoints.rst:7
msgid ""
"All Debian packages for API services, except the ``heat-api`` package, "
"register the service in the Identity service catalog. This feature is "
"helpful because API endpoints are difficult to remember."
msgstr ""
#: ../debconf/debconf-api-endpoints.rst:13
msgid ""
"The ``heat-common`` package and not the ``heat-api`` package configures the "
"Orchestration service."
msgstr ""
#: ../debconf/debconf-api-endpoints.rst:16
msgid ""
"When you install a package for an API service, you are prompted to register "
"that service. However, after you install or upgrade the package for an API "
"service, Debian immediately removes your response to this prompt from the "
"debconf database. Consequently, you are prompted to re-register the service "
"with the Identity service. If you already registered the API service, "
"respond ``no`` when you upgrade."
msgstr ""
#: ../debconf/debconf-api-endpoints.rst:27
msgid "This screen registers packages in the Identity service catalog:"
msgstr ""
#: ../debconf/debconf-api-endpoints.rst:33
msgid ""
"You are prompted for the Identity service ``admin_token`` value. The "
"Identity Service uses this value to register the API service. When you set "
"up the ``keystone`` package, this value is configured automatically."
msgstr ""
#: ../debconf/debconf-api-endpoints.rst:41
msgid ""
"This screen configures the IP addresses for the service. The configuration "
"script automatically detects the IP address used by the interface that is "
"connected to the default route (``/sbin/route`` and ``/sbin/ip``)."
msgstr ""
#: ../debconf/debconf-api-endpoints.rst:46
msgid "Unless you have a unique set up for your network, press **ENTER**."
msgstr ""
#: ../debconf/debconf-api-endpoints.rst:52
msgid ""
"This screen configures the region name for the service. For example, ``us-"
"east-coast`` or ``europe-paris``."
msgstr ""
#: ../debconf/debconf-api-endpoints.rst:59
msgid ""
"The Debian package post installation scripts will then perform the below "
"commands for you:"
msgstr ""
#: ../debconf/debconf-api-endpoints.rst:97
msgid ""
"The values of ``AUTH_TOKEN``, ``KEYSTONE_ENDPOINT_IP``, ``PKG_ENDPOINT_IP``, "
"and ``REGION_NAME`` depend on the answer you will provide to the debconf "
"prompts. But the values of ``SERVICE_NAME``, ``SERVICE_TYPE``, "
"``SERVICE_DESC``, and ``SERVICE_URL`` are already pre-wired in each package, "
"so you don't have to remember them."
msgstr ""
#: ../debconf/debconf-concepts.rst:5
msgid "debconf concepts"
msgstr ""
#: ../debconf/debconf-concepts.rst:7
msgid ""
"This chapter explains how to use the Debian ``debconf`` and ``dbconfig-"
"common`` packages to configure OpenStack services. These packages enable "
"users to perform configuration tasks. When users install OpenStack packages, "
"``debconf`` prompts the user for responses, which seed the contents of "
"configuration files associated with that package. After package "
"installation, users can update the configuration of a package by using the :"
"command:`dpkg-reconfigure` program."
msgstr ""
#: ../debconf/debconf-concepts.rst:15
msgid ""
"If you are familiar with these packages and pre-seeding, you can proceed to :"
"doc:`../keystone`."
msgstr ""
#: ../debconf/debconf-concepts.rst:20
msgid "The Debian packages"
msgstr ""
#: ../debconf/debconf-concepts.rst:22
msgid ""
"The rules described here are from the `Debian Policy Manual <http://www."
"debian.org/doc/debian-policy/>`__. If any rule described in this chapter is "
"not respected, you have found a serious bug that must be fixed."
msgstr ""
#: ../debconf/debconf-concepts.rst:27
msgid ""
"When you install or upgrade a Debian package, all configuration file values "
"are preserved. Using the ``debconf`` database as a registry is considered a "
"bug in Debian. If you edit something in any OpenStack configuration file, "
"the ``debconf`` package reads that value when it prepares to prompt the "
"user. For example, to change the log in name for the RabbitMQ messaging "
"queue for a service, you can edit its value in the corresponding "
"configuration file."
msgstr ""
#: ../debconf/debconf-concepts.rst:35
msgid ""
"To opt out of using the ``debconf`` package, run the :command:`dpkg-"
"reconfigure` command and select non-interactive mode:"
msgstr ""
#: ../debconf/debconf-concepts.rst:42
msgid "Then, ``debconf`` does not prompt you."
msgstr ""
#: ../debconf/debconf-concepts.rst:44
msgid ""
"Another way to disable the ``debconf`` package is to prefix the :command:"
"`apt` command with ``DEBIAN_FRONTEND=noninteractive``, as follows:"
msgstr ""
#: ../debconf/debconf-concepts.rst:52
msgid ""
"If you configure a package with ``debconf`` incorrectly, you can re-"
"configure it, as follows:"
msgstr ""
#: ../debconf/debconf-concepts.rst:60
msgid ""
"This calls the post-installation script for the ``PACKAGE-NAME`` package "
"after the user responds to all prompts. If you cannot install a Debian "
"package in a non-interactive way, you have found a release-critical bug in "
"Debian. Report it to the Debian bug tracking system."
msgstr ""
#: ../debconf/debconf-concepts.rst:65
msgid ""
"Generally, the ``-common`` packages install the configuration files. For "
"example, the ``glance-common`` package installs the ``glance-api.conf`` and "
"``glance-registry.conf`` files. So, for the Image service, you must re-"
"configure the ``glance-common`` package. The same applies for ``cinder-"
"common``, ``nova-common``, and ``heat-common`` packages."
msgstr ""
#: ../debconf/debconf-concepts.rst:71
msgid ""
"In ``debconf``, the higher the priority for a screen, the greater the chance "
"that the user sees that screen. If a ``debconf`` screen has ``medium`` "
"priority and you configure the Debian system to show only ``critical`` "
"prompts, which is the default in Debian, the user does not see that "
"``debconf`` screen. Instead, the default for the related package is used. In "
"the Debian OpenStack packages, a number of ``debconf`` screens are set with "
"``medium`` priority. Consequently, if you want to respond to all ``debconf`` "
"screens from the Debian OpenStack packages, you must run the following "
"command and select the ``medium`` priority before you install any packages:"
msgstr ""
#: ../debconf/debconf-concepts.rst:88
msgid ""
"The packages do not require pre-depends. If ``dbconfig-common`` is already "
"installed on the system, the user sees all prompts. However, you cannot "
"define the order in which the ``debconf`` screens appear. The user must make "
"sense of it even if the prompts appear in an illogical order."
msgstr ""
#: ../debconf/debconf-concepts.rst:97
msgid "Pre-seed debconf prompts"
msgstr ""
#: ../debconf/debconf-concepts.rst:99
msgid ""
"You can pre-seed all ``debconf`` prompts. To pre-seed means to store "
"responses in the ``debconf`` database so that ``debconf`` does not prompt "
"the user for responses. Pre-seeding enables a hands-free installation for "
"users. The package maintainer creates scripts that automatically configure "
"the services."
msgstr ""
#: ../debconf/debconf-concepts.rst:105
msgid ""
"The following example shows how to pre-seed an automated MySQL Server "
"installation:"
msgstr ""
#: ../debconf/debconf-concepts.rst:118
msgid ""
"The ``seen true`` option tells ``debconf`` that a specified screen was "
"already seen by the user so do not show it again. This option is useful for "
"upgrades."
msgstr ""
#: ../debconf/debconf-dbconfig-common.rst:5
msgid "Configure the database with dbconfig-common"
msgstr ""
#: ../debconf/debconf-dbconfig-common.rst:7
msgid ""
"Many of the OpenStack services need to be configured to access a database. "
"These are configured through a DSN (Database Source Name) directive as "
"follows:"
msgstr ""
#: ../debconf/debconf-dbconfig-common.rst:16
msgid ""
"This ``connection`` directive will be handled by the ``dbconfig-common`` "
"package, which provides a standard Debian interface. It enables you to "
"configure Debian database parameters. It includes localized prompts for many "
"languages and it supports the following database backends: SQLite, MySQL, "
"and PostgreSQL."
msgstr ""
#: ../debconf/debconf-dbconfig-common.rst:22
msgid ""
"By default, the ``dbconfig-common`` package configures the OpenStack "
"services to use SQLite. So if you use debconf in non-interactive mode and "
"without pre-seeding, the OpenStack services that you install will use SQLite."
msgstr ""
#: ../debconf/debconf-dbconfig-common.rst:27
msgid ""
"By default, ``dbconfig-common`` does not provide access to database servers "
"over a network. If you want the ``dbconfig-common`` package to prompt for "
"remote database servers that are accessed over a network and not through a "
"UNIX socket file, reconfigure it, as follows:"
msgstr ""
#: ../debconf/debconf-dbconfig-common.rst:36
msgid ""
"These screens appear when you re-configure the ``dbconfig-common`` package:"
msgstr ""
#: ../debconf/debconf-dbconfig-common.rst:46
msgid ""
"Unlike other debconf prompts, you cannot pre-seed the responses for the "
"``dbconfig-common`` prompts by using ``debconf-set-selections``. Instead, "
"you must create a file in :file:`/etc/dbconfig-common`. For example, you "
"might create a keystone configuration file for ``dbconfig-common`` that is "
"located in :file:`/etc/dbconfig-common/keystone.conf`, as follows:"
msgstr ""
#: ../debconf/debconf-dbconfig-common.rst:69
msgid "After you create this file, run this command:"
msgstr ""
#: ../debconf/debconf-dbconfig-common.rst:75
msgid ""
"The Identity service is installed with MySQL as the database back end, "
"``keystonedb`` as database name, and the localhost socket file. The "
"corresponding DSN (Database Source Name) will then be:"
msgstr ""
#: ../debconf/debconf-dbconfig-common.rst:84
msgid ""
"The ``dbconfig-common`` package will configure MySQL for these access "
"rights, and create the database for you. Since OpenStack 2014.1.1, all "
"OpenStack packages in Debian are performing the following MySQL query after "
"database creation (if you decide to use MySQL as a back-end):"
msgstr ""
#: ../debconf/debconf-dbconfig-common.rst:93
msgid ""
"So, if using Debian, you wont need to care about database creation, access "
"rights and character sets. All that is handled for you by the packages."
msgstr ""
#: ../debconf/debconf-dbconfig-common.rst:97
msgid "As an example, here are screenshots from the ``cinder-common`` package:"
msgstr ""
#: ../debconf/debconf-dbconfig-common.rst:123
msgid ""
"By default in Debian, you can access the MySQL server from either localhost "
"through the socket file or 127.0.0.1. To access it over the network, you "
"must edit the :file:`/etc/mysql/my.cnf` file, and the ``mysql.user`` table. "
"To do so, Debian provides a helper script in the ``openstack-deploy`` "
"package. To use it, install the package:"
msgstr ""
#: ../debconf/debconf-dbconfig-common.rst:133
msgid "and run the helper script:"
msgstr ""
#: ../debconf/debconf-dbconfig-common.rst:139
msgid ""
"Alternatively, if you do not want to install this package, run this script "
"to enable remote root access:"
msgstr ""
#: ../debconf/debconf-dbconfig-common.rst:166
msgid ""
"You must enable remote access before you install OpenStack services on "
"multiple nodes."
msgstr ""
#: ../debconf/debconf-keystone-authtoken.rst:5
msgid "Services and the [keystone_authtoken]"
msgstr ""
#: ../debconf/debconf-keystone-authtoken.rst:7
msgid ""
"Because most OpenStack services must access the Identity service, you must "
"configure the IP address of the ``keystone`` server to be able to access it. "
"You must also configure the ``admin_tenant_name``, ``admin_user``, and "
"``admin_password`` options for each service to work."
msgstr ""
#: ../debconf/debconf-keystone-authtoken.rst:12
msgid "Generally, this section looks like this:"
msgstr ""
#: ../debconf/debconf-keystone-authtoken.rst:23
msgid ""
"The debconf system helps users configure the ``auth_uri``, ``identity_uri``, "
"``admin_tenant_name``, ``admin_user``, and ``admin_password`` options."
msgstr ""
#: ../debconf/debconf-keystone-authtoken.rst:27
msgid "The following screens show an example Image service configuration:"
msgstr ""
#: ../debconf/debconf-keystone-authtoken.rst:43
msgid ""
"This information is stored in the configuration file for each service. For "
"example:"
msgstr ""
#: ../debconf/debconf-keystone-authtoken.rst:55
msgid ""
"The Debian OpenStack packages offer automation for this, so OpenStack users "
"do not have to manually edit the configuration files."
msgstr ""
#: ../debconf/debconf-rabbitmq.rst:5
msgid "RabbitMQ credentials parameters"
msgstr ""
#: ../debconf/debconf-rabbitmq.rst:7
msgid ""
"For every package that must connect to a Messaging Server, the Debian "
"package enables you to configure the IP address for that server and the user "
"name and password that is used to connect. The following example shows "
"configuration with the ``ceilometer-common`` package:"
msgstr ""
#: ../debconf/debconf-rabbitmq.rst:24
msgid ""
"These debconf screens appear in: ``ceilometer-common``, ``cinder-common``, "
"``glance-common``, ``heat-common``, ``neutron-common``, and ``nova-common``."
msgstr ""
#: ../debconf/debconf-rabbitmq.rst:27
msgid "This will configure the below directives (example from ``nova.conf``):"
msgstr ""
#: ../debconf/debconf-rabbitmq.rst:36
msgid "The other directives concerning RabbitMQ will stay untouched."
msgstr ""
#: ../debconf/debconf.rst:5
msgid "Configure OpenStack with debconf"
msgstr ""
#: ../environment-messaging.rst:2
msgid "Message queue"
msgstr ""
#: ../environment-messaging.rst:4
msgid ""
"OpenStack uses a :term:`message queue` to coordinate operations and status "
"information among services. The message queue service typically runs on the "
"controller node. OpenStack supports several message queue services including "
"`RabbitMQ <http://www.rabbitmq.com>`__, `Qpid <http://qpid.apache.org>`__, "
"and `ZeroMQ <http://zeromq.org>`__. However, most distributions that package "
"OpenStack support a particular message queue service. This guide implements "
"the RabbitMQ message queue service because most distributions support it. If "
"you prefer to implement a different message queue service, consult the "
"documentation associated with it."
msgstr ""
#: ../environment-messaging.rst:18
msgid "Install the package:"
msgstr ""
#: ../environment-messaging.rst:40
msgid ""
"Start the message queue service and configure it to start when the system "
"boots:"
msgstr ""
#: ../environment-messaging.rst:50
msgid ""
"In case the message queue service does not start and returns a ``nodedown`` "
"error, perform the following actions:"
msgstr ""
#: ../environment-messaging.rst:53
msgid ""
"Copy the ``/usr/lib/systemd/system/epmd.socket`` file to the ``/etc/systemd/"
"system`` directory."
msgstr ""
#: ../environment-messaging.rst:56
msgid ""
"Edit the ``/etc/systemd/system/epmd.socket`` file to contain the following:"
msgstr ""
#: ../environment-messaging.rst:65
msgid ""
"Replace ``MANAGEMENT_INTERFACE_IP_ADDRESS`` with the IP address of the "
"management network interface on your controller node."
msgstr ""
#: ../environment-messaging.rst:68
msgid "Start the message queue service again."
msgstr ""
#: ../environment-messaging.rst:70 ../environment-messaging.rst:89
msgid "Add the ``openstack`` user:"
msgstr ""
#: ../environment-messaging.rst:77 ../environment-messaging.rst:96
msgid "Replace ``RABBIT_PASS`` with a suitable password."
msgstr ""
#: ../environment-messaging.rst:79 ../environment-messaging.rst:98
msgid ""
"Permit configuration, write, and read access for the ``openstack`` user:"
msgstr ""
#: ../environment-networking-compute.rst:2
msgid "Compute node"
msgstr ""
# #-#-#-#-# environment-networking-compute.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# environment-networking-controller.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# environment-networking-storage-cinder.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# environment-networking-storage-swift.pot (Installation Guide 0.1) #-#-#-#-#
#: ../environment-networking-compute.rst:5
#: ../environment-networking-controller.rst:5
#: ../environment-networking-storage-cinder.rst:8
#: ../environment-networking-storage-swift.rst:11
#: ../environment-networking-storage-swift.rst:34
msgid "Configure network interfaces"
msgstr ""
# #-#-#-#-# environment-networking-compute.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# environment-networking-controller.pot (Installation Guide 0.1) #-#-#-#-#
#: ../environment-networking-compute.rst:7
#: ../environment-networking-controller.rst:7
msgid "Configure the first interface as the management interface:"
msgstr ""
#: ../environment-networking-compute.rst:9
msgid "IP address: 10.0.0.31"
msgstr ""
# #-#-#-#-# environment-networking-compute.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# environment-networking-controller.pot (Installation Guide 0.1) #-#-#-#-#
#: ../environment-networking-compute.rst:11
#: ../environment-networking-controller.rst:11
msgid "Network mask: 255.255.255.0 (or /24)"
msgstr ""
# #-#-#-#-# environment-networking-compute.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# environment-networking-controller.pot (Installation Guide 0.1) #-#-#-#-#
#: ../environment-networking-compute.rst:13
#: ../environment-networking-controller.rst:13
msgid "Default gateway: 10.0.0.1"
msgstr ""
#: ../environment-networking-compute.rst:17
msgid "Additional compute nodes should use 10.0.0.32, 10.0.0.33, and so on."
msgstr ""
# #-#-#-#-# environment-networking-compute.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# environment-networking-controller.pot (Installation Guide 0.1) #-#-#-#-#
#: ../environment-networking-compute.rst:19
#: ../environment-networking-controller.rst:15
msgid ""
"The public interface uses a special configuration without an IP address "
"assigned to it. Configure the second interface as the public interface:"
msgstr ""
# #-#-#-#-# environment-networking-compute.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# environment-networking-controller.pot (Installation Guide 0.1) #-#-#-#-#
#: ../environment-networking-compute.rst:23
#: ../environment-networking-controller.rst:19
msgid ""
"Replace ``INTERFACE_NAME`` with the actual interface name. For example, "
"*eth1* or *ens224*."
msgstr ""
# #-#-#-#-# environment-networking-compute.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# environment-networking-controller.pot (Installation Guide 0.1) #-#-#-#-#
#: ../environment-networking-compute.rst:28
#: ../environment-networking-controller.rst:24
msgid "Edit the ``/etc/network/interfaces`` file to contain the following:"
msgstr ""
# #-#-#-#-# environment-networking-compute.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# environment-networking-controller.pot (Installation Guide 0.1) #-#-#-#-#
#: ../environment-networking-compute.rst:40
#: ../environment-networking-controller.rst:36
msgid ""
"Edit the ``/etc/sysconfig/network-scripts/ifcfg-INTERFACE_NAME`` file to "
"contain the following:"
msgstr ""
# #-#-#-#-# environment-networking-compute.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# environment-networking-controller.pot (Installation Guide 0.1) #-#-#-#-#
#: ../environment-networking-compute.rst:43
#: ../environment-networking-controller.rst:39
msgid "Do not change the ``HWADDR`` and ``UUID`` keys."
msgstr ""
# #-#-#-#-# environment-networking-compute.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# environment-networking-controller.pot (Installation Guide 0.1) #-#-#-#-#
#: ../environment-networking-compute.rst:54
#: ../environment-networking-controller.rst:50
msgid ""
"Edit the ``/etc/sysconfig/network/ifcfg-INTERFACE_NAME`` file to contain the "
"following:"
msgstr ""
# #-#-#-#-# environment-networking-compute.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# environment-networking-controller.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# environment-networking-storage-cinder.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# environment-networking-storage-swift.pot (Installation Guide 0.1) #-#-#-#-#
#: ../environment-networking-compute.rst:62
#: ../environment-networking-controller.rst:58
#: ../environment-networking-storage-cinder.rst:25
#: ../environment-networking-storage-swift.rst:28
#: ../environment-networking-storage-swift.rst:51
msgid "Reboot the system to activate the changes."
msgstr ""
# #-#-#-#-# environment-networking-compute.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# environment-networking-controller.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# environment-networking-storage-cinder.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# environment-networking-storage-swift.pot (Installation Guide 0.1) #-#-#-#-#
#: ../environment-networking-compute.rst:65
#: ../environment-networking-controller.rst:61
#: ../environment-networking-storage-cinder.rst:19
#: ../environment-networking-storage-swift.rst:22
#: ../environment-networking-storage-swift.rst:45
msgid "Configure name resolution"
msgstr ""
#: ../environment-networking-compute.rst:67
msgid "Set the hostname of the node to ``compute1``."
msgstr ""
# #-#-#-#-# environment-networking-controller.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# environment-ntp-controller.pot (Installation Guide 0.1) #-#-#-#-#
#: ../environment-networking-controller.rst:2
#: ../environment-ntp-controller.rst:4
msgid "Controller node"
msgstr ""
#: ../environment-networking-controller.rst:9
msgid "IP address: 10.0.0.11"
msgstr ""
#: ../environment-networking-controller.rst:63
msgid "Set the hostname of the node to ``controller``."
msgstr ""
#: ../environment-networking-storage-cinder.rst:2
msgid "Block storage node (Optional)"
msgstr ""
#: ../environment-networking-storage-cinder.rst:4
msgid ""
"If you want to deploy the Block Storage service, configure one additional "
"storage node."
msgstr ""
# #-#-#-#-# environment-networking-storage-cinder.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# environment-networking-storage-swift.pot (Installation Guide 0.1) #-#-#-#-#
#: ../environment-networking-storage-cinder.rst:10
#: ../environment-networking-storage-swift.rst:13
#: ../environment-networking-storage-swift.rst:36
msgid "Configure the management interface:"
msgstr ""
#: ../environment-networking-storage-cinder.rst:12
msgid "IP address: ``10.0.0.41``"
msgstr ""
# #-#-#-#-# environment-networking-storage-cinder.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# environment-networking-storage-swift.pot (Installation Guide 0.1) #-#-#-#-#
#: ../environment-networking-storage-cinder.rst:14
#: ../environment-networking-storage-swift.rst:17
#: ../environment-networking-storage-swift.rst:40
msgid "Network mask: ``255.255.255.0`` (or ``/24``)"
msgstr ""
# #-#-#-#-# environment-networking-storage-cinder.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# environment-networking-storage-swift.pot (Installation Guide 0.1) #-#-#-#-#
#: ../environment-networking-storage-cinder.rst:16
#: ../environment-networking-storage-swift.rst:19
#: ../environment-networking-storage-swift.rst:42
msgid "Default gateway: ``10.0.0.1``"
msgstr ""
#: ../environment-networking-storage-cinder.rst:21
msgid "Set the hostname of the node to ``block1``."
msgstr ""
#: ../environment-networking-storage-swift.rst:2
msgid "Object storage nodes (Optional)"
msgstr ""
#: ../environment-networking-storage-swift.rst:4
msgid ""
"If you want to deploy the Object Storage service, configure two additional "
"storage nodes."
msgstr ""
#: ../environment-networking-storage-swift.rst:8
msgid "First node"
msgstr ""
#: ../environment-networking-storage-swift.rst:15
msgid "IP address: ``10.0.0.51``"
msgstr ""
#: ../environment-networking-storage-swift.rst:24
msgid "Set the hostname of the node to ``object1``."
msgstr ""
#: ../environment-networking-storage-swift.rst:31
msgid "Second node"
msgstr ""
#: ../environment-networking-storage-swift.rst:38
msgid "IP address: ``10.0.0.52``"
msgstr ""
#: ../environment-networking-storage-swift.rst:47
msgid "Set the hostname of the node to ``object2``."
msgstr ""
#: ../environment-networking-verify.rst:2
msgid "Verify connectivity"
msgstr ""
#: ../environment-networking-verify.rst:4
msgid ""
"We recommend that you verify network connectivity to the Internet and among "
"the nodes before proceeding further."
msgstr ""
#: ../environment-networking-verify.rst:7
msgid "From the *controller* node, test access to the Internet:"
msgstr ""
#: ../environment-networking-verify.rst:22
msgid ""
"From the *controller* node, test access to the management interface on the "
"*compute* node:"
msgstr ""
#: ../environment-networking-verify.rst:38
msgid "From the *compute* node, test access to the Internet:"
msgstr ""
#: ../environment-networking-verify.rst:53
msgid ""
"From the *compute* node, test access to the management interface on the "
"*controller* node:"
msgstr ""
# #-#-#-#-# environment-networking.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# environment-networking-verify.pot (Installation Guide 0.1) #-#-#-#-#
#: ../environment-networking-verify.rst:73 ../environment-networking.rst:99
msgid ""
"Your distribution enables a restrictive :term:`firewall` by default. During "
"the installation process, certain steps will fail unless you alter or "
"disable the firewall. For more information about securing your environment, "
"refer to the `OpenStack Security Guide <http://docs.openstack.org/sec/>`__."
msgstr ""
# #-#-#-#-# environment-networking.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# environment-networking-verify.pot (Installation Guide 0.1) #-#-#-#-#
#: ../environment-networking-verify.rst:81 ../environment-networking.rst:107
msgid ""
"Your distribution does not enable a restrictive :term:`firewall` by default. "
"For more information about securing your environment, refer to the "
"`OpenStack Security Guide <http://docs.openstack.org/sec/>`__."
msgstr ""
#: ../environment-networking.rst:2
msgid "Host networking"
msgstr ""
#: ../environment-networking.rst:6
msgid ""
"After installing the operating system on each node for the architecture that "
"you choose to deploy, you must configure the network interfaces. We "
"recommend that you disable any automated network management tools and "
"manually edit the appropriate configuration files for your distribution. For "
"more information on how to configure networking on your distribution, see "
"the `documentation <https://help.ubuntu.com/lts/serverguide/network-"
"configuration.html>`__ ."
msgstr ""
#: ../environment-networking.rst:15
msgid ""
"After installing the operating system on each node for the architecture that "
"you choose to deploy, you must configure the network interfaces. We "
"recommend that you disable any automated network management tools and "
"manually edit the appropriate configuration files for your distribution. For "
"more information on how to configure networking on your distribution, see "
"the `documentation <https://wiki.debian.org/NetworkConfiguration>`__ ."
msgstr ""
#: ../environment-networking.rst:24
msgid ""
"After installing the operating system on each node for the architecture that "
"you choose to deploy, you must configure the network interfaces. We "
"recommend that you disable any automated network management tools and "
"manually edit the appropriate configuration files for your distribution. For "
"more information on how to configure networking on your distribution, see "
"the `documentation <https://access.redhat.com/documentation/en-US/"
"Red_Hat_Enterprise_Linux/7/html/Networking_Guide/sec-"
"Using_the_Command_Line_Interface.html>`__ ."
msgstr ""
#: ../environment-networking.rst:33
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 `SLES 12 <https://www.suse.com/documentation/sles-12/book_sle_admin/data/"
"sec_basicnet_manconf.html>`__ or `openSUSE <http://activedoc.opensuse.org/"
"book/opensuse-reference/chapter-13-basic-networking>`__ documentation."
msgstr ""
#: ../environment-networking.rst:40
msgid ""
"All nodes require Internet access for administrative purposes such as "
"package installation, security updates, :term:`DNS`, and :term:`NTP`. In "
"most cases, nodes should obtain internet access through the management "
"network interface. To highlight the importance of network separation, the "
"example architectures use `private address space <https://tools.ietf.org/"
"html/rfc1918>`__ for the management network and assume that the physical "
"network infrastructure provides Internet access via :term:`NAT` or other "
"method. The example architectures use routable IP address space for the "
"public network and assume that the physical network infrastructure provides "
"direct Internet access. In the provider networks architecture, all instances "
"attach directly to the public network. In the self-service networks "
"architecture, instances can attach to a private or public network. Private "
"networks can reside entirely within OpenStack or provide some level of "
"public network access using :term:`NAT`."
msgstr ""
#: ../environment-networking.rst:60
msgid "The example architectures assume use of the following networks:"
msgstr ""
#: ../environment-networking.rst:62
msgid "Management on 10.0.0.0/24 with gateway 10.0.0.1"
msgstr ""
#: ../environment-networking.rst:64
msgid ""
"This network requires a gateway to provide Internet access to all nodes for "
"administrative purposes such as package installation, security updates, :"
"term:`DNS`, and :term:`NTP`."
msgstr ""
#: ../environment-networking.rst:68
msgid "Public on 203.0.113.0/24 with gateway 203.0.113.1"
msgstr ""
#: ../environment-networking.rst:70
msgid ""
"This network requires a gateway to provide Internet access to instances in "
"your OpenStack environment."
msgstr ""
#: ../environment-networking.rst:73
msgid ""
"You can modify these ranges and gateways to work with your particular "
"network infrastructure."
msgstr ""
#: ../environment-networking.rst:76
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 ""
#: ../environment-networking.rst:82
msgid ""
"Unless you intend to use the exact configuration provided in this example "
"architecture, you must modify the networks in this procedure to match your "
"environment. Also, each node must resolve the other nodes by name in "
"addition to IP address. For example, the ``controller`` name must resolve to "
"``10.0.0.11``, the IP address of the management interface on the controller "
"node."
msgstr ""
#: ../environment-networking.rst:91
msgid ""
"Reconfiguring network interfaces will interrupt network connectivity. We "
"recommend using a local terminal session for these procedures."
msgstr ""
#: ../environment-nosql-database.rst:4
msgid "NoSQL database"
msgstr ""
#: ../environment-nosql-database.rst:6
msgid ""
"The Telemetry service uses a NoSQL database to store information. The "
"database typically runs on the controller node. The procedures in this guide "
"use MongoDB."
msgstr ""
#: ../environment-nosql-database.rst:12
msgid ""
"The installation of the NoSQL database server is only necessary when "
"installing the Telemetry service as documented in :ref:`install_ceilometer`."
msgstr ""
#: ../environment-nosql-database.rst:20
msgid ""
"Enable the Open Build Service repositories for MongoDB based on your "
"openSUSE or SLES version:"
msgstr ""
# #-#-#-#-# environment-nosql-database.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# environment-ntp-controller.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# environment-ntp-other.pot (Installation Guide 0.1) #-#-#-#-#
#: ../environment-nosql-database.rst:23 ../environment-ntp-controller.rst:27
#: ../environment-ntp-other.rst:28
msgid "On openSUSE:"
msgstr ""
# #-#-#-#-# environment-nosql-database.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# environment-ntp-controller.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# environment-ntp-other.pot (Installation Guide 0.1) #-#-#-#-#
#: ../environment-nosql-database.rst:29 ../environment-ntp-controller.rst:35
#: ../environment-ntp-other.rst:36
msgid "On SLES:"
msgstr ""
#: ../environment-nosql-database.rst:37
msgid ""
"The packages are signed by GPG key ``05905EA8``. You should verify the "
"fingerprint of the imported GPG key before using it."
msgstr ""
#: ../environment-nosql-database.rst:47
msgid "Install the MongoDB package:"
msgstr ""
#: ../environment-nosql-database.rst:55 ../environment-nosql-database.rst:63
msgid "Install the MongoDB packages:"
msgstr ""
#: ../environment-nosql-database.rst:71 ../environment-nosql-database.rst:121
msgid "Edit the ``/etc/mongodb.conf`` file and complete the following actions:"
msgstr ""
#: ../environment-nosql-database.rst:74 ../environment-nosql-database.rst:99
#: ../environment-nosql-database.rst:124
msgid ""
"Configure the ``bind_ip`` key to use the management interface IP address of "
"the controller node."
msgstr ""
#: ../environment-nosql-database.rst:81 ../environment-nosql-database.rst:106
#: ../environment-nosql-database.rst:131
msgid ""
"By default, MongoDB creates several 1 GB journal files in the ``/var/lib/"
"mongodb/journal`` directory. If you want to reduce the size of each journal "
"file to 128 MB and limit total journal space consumption to 512 MB, assert "
"the ``smallfiles`` key:"
msgstr ""
#: ../environment-nosql-database.rst:91 ../environment-nosql-database.rst:116
#: ../environment-nosql-database.rst:141
msgid ""
"You can also disable journaling. For more information, see the `MongoDB "
"manual <http://docs.mongodb.org/manual/>`__."
msgstr ""
#: ../environment-nosql-database.rst:96
msgid "Edit the ``/etc/mongod.conf`` file and complete the following actions:"
msgstr ""
#: ../environment-nosql-database.rst:149
msgid ""
"If you change the journaling configuration, stop the MongoDB service, remove "
"the initial journal files, and start the service:"
msgstr ""
#: ../environment-nosql-database.rst:160 ../environment-nosql-database.rst:170
msgid ""
"Start the MongoDB service and configure it to start when the system boots:"
msgstr ""
# #-#-#-#-# environment-ntp-controller.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# environment-ntp-other.pot (Installation Guide 0.1) #-#-#-#-#
#: ../environment-ntp-controller.rst:45 ../environment-ntp-other.rst:46
msgid ""
"The packages are signed by GPG key ``17280DDF``. You should verify the "
"fingerprint of the imported GPG key before using it."
msgstr ""
#: ../environment-ntp-controller.rst:57
msgid ""
"Edit the ``/etc/chrony/chrony.conf`` file and add, change, or remove the "
"following keys as necessary for your environment:"
msgstr ""
#: ../environment-ntp-controller.rst:64 ../environment-ntp-controller.rst:89
msgid ""
"Replace ``NTP_SERVER`` with the hostname or IP address of a suitable more "
"accurate (lower stratum) NTP server. The configuration supports multiple "
"``server`` keys."
msgstr ""
#: ../environment-ntp-controller.rst:70 ../environment-ntp-controller.rst:95
msgid ""
"By default, the controller node synchronizes the time via a pool of public "
"servers. However, you can optionally configure alternative servers such as "
"those provided by your organization."
msgstr ""
# #-#-#-#-# environment-ntp-controller.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# environment-ntp-other.pot (Installation Guide 0.1) #-#-#-#-#
#: ../environment-ntp-controller.rst:74 ../environment-ntp-other.rst:65
msgid "Restart the NTP service:"
msgstr ""
#: ../environment-ntp-controller.rst:82
msgid ""
"Edit the ``/etc/chrony.conf`` file and add, change, or remove the following "
"keys as necessary for your environment:"
msgstr ""
#: ../environment-ntp-controller.rst:99
msgid ""
"To enable other nodes to connect to the chrony daemon on the controller, add "
"the following key to the ``/etc/chrony.conf`` file:"
msgstr ""
#: ../environment-ntp-controller.rst:106
msgid ""
"If necessary, replace ``10.0.0.0/24`` with a description of your subnet."
msgstr ""
# #-#-#-#-# environment-ntp-controller.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# environment-ntp-other.pot (Installation Guide 0.1) #-#-#-#-#
#: ../environment-ntp-controller.rst:108 ../environment-ntp-other.rst:80
msgid "Start the NTP service and configure it to start when the system boots:"
msgstr ""
#: ../environment-ntp-other.rst:4
msgid "Other nodes"
msgstr ""
#: ../environment-ntp-other.rst:6
msgid ""
"Other nodes reference the controller node for clock synchronization. Perform "
"these steps on all other nodes."
msgstr ""
#: ../environment-ntp-other.rst:58
msgid ""
"Edit the ``/etc/chrony/chrony.conf`` file and comment out or remove all but "
"one ``server`` key. Change it to reference the controller node:"
msgstr ""
#: ../environment-ntp-other.rst:73
msgid ""
"Edit the ``/etc/chrony.conf`` file and comment out or remove all but one "
"``server`` key. Change it to reference the controller node:"
msgstr ""
#: ../environment-ntp-verify.rst:6
msgid ""
"We recommend that you verify NTP synchronization before proceeding further. "
"Some nodes, particularly those that reference the controller node, can take "
"several minutes to synchronize."
msgstr ""
#: ../environment-ntp-verify.rst:10
msgid "Run this command on the *controller* node:"
msgstr ""
#: ../environment-ntp-verify.rst:21
msgid ""
"Contents in the *Name/IP address* column should indicate the hostname or IP "
"address of one or more NTP servers. Contents in the *S* column should "
"indicate *\\** for the server to which the NTP service is currently "
"synchronized."
msgstr ""
#: ../environment-ntp-verify.rst:25
msgid "Run the same command on *all other* nodes:"
msgstr ""
#: ../environment-ntp-verify.rst:35
msgid ""
"Contents in the *Name/IP address* column should indicate the hostname of the "
"controller node."
msgstr ""
#: ../environment-ntp.rst:4
msgid "Network Time Protocol (NTP)"
msgstr ""
#: ../environment-ntp.rst:6
msgid ""
"You should install Chrony, an implementation of :term:`NTP`, to properly "
"synchronize services among nodes. We recommend that you configure the "
"controller node to reference more accurate (lower stratum) servers and other "
"nodes to reference the controller node."
msgstr ""
#: ../environment-packages.rst:2
msgid "OpenStack packages"
msgstr ""
#: ../environment-packages.rst:4
msgid ""
"Distributions release OpenStack packages as part of the distribution or "
"using other methods because of differing release schedules. Perform these "
"procedures on all nodes."
msgstr ""
#: ../environment-packages.rst:10
msgid ""
"Your hosts must contain the latest versions of base installation packages "
"available for your distribution before proceeding further."
msgstr ""
#: ../environment-packages.rst:15
msgid ""
"Disable or remove any automatic update services because they can impact your "
"OpenStack environment."
msgstr ""
#: ../environment-packages.rst:21 ../environment-packages.rst:54
#: ../environment-packages.rst:75
msgid "Enable the OpenStack repository"
msgstr ""
#: ../environment-packages.rst:33
msgid "Enable the `EPEL <https://fedoraproject.org/wiki/EPEL>`_ repository:"
msgstr ""
#: ../environment-packages.rst:39
msgid "On RHEL, enable additional repositories using the subscription manager:"
msgstr ""
#: ../environment-packages.rst:49
msgid "CentOS does not require these repositories."
msgstr ""
#: ../environment-packages.rst:56
msgid ""
"On CentOS, the *extras* repository provides the RPM that enables the "
"OpenStack repository. CentOS includes the *extras* repository by default, so "
"you can simply install the package to enable the OpenStack repository."
msgstr ""
#: ../environment-packages.rst:65
msgid ""
"On RHEL, download and install the RDO repository RPM to enable the OpenStack "
"repository."
msgstr ""
#: ../environment-packages.rst:77
msgid ""
"Enable the Open Build Service repositories based on your openSUSE or SLES "
"version:"
msgstr ""
#: ../environment-packages.rst:80
msgid "**On openSUSE 13.2:**"
msgstr ""
#: ../environment-packages.rst:86
msgid ""
"The openSUSE distribution uses the concept of patterns to represent "
"collections of packages. If you selected 'Minimal Server Selection (Text "
"Mode)' during the initial installation, you may be presented with a "
"dependency conflict when you attempt to install the OpenStack packages. To "
"avoid this, remove the minimal\\_base-conflicts package:"
msgstr ""
#: ../environment-packages.rst:96
msgid "**On SLES 12:**"
msgstr ""
#: ../environment-packages.rst:104
msgid ""
"The packages are signed by GPG key ``D85F9316``. You should verify the "
"fingerprint of the imported GPG key before using it."
msgstr ""
#: ../environment-packages.rst:117
msgid "Enable the backports repository"
msgstr ""
#: ../environment-packages.rst:119
msgid ""
"The Liberty release is available directly through the official Debian "
"backports repository. To use this repository, follow the instruction from "
"the official `Debian website <http://backports.debian.org/Instructions/>`_, "
"which basically suggest doing the following steps:"
msgstr ""
#: ../environment-packages.rst:125
msgid ""
"On all nodes, adding the Debian 8 (Jessie) backport repository to the source "
"list:"
msgstr ""
#: ../environment-packages.rst:135
msgid "Later you can use the following command to install a package:"
msgstr ""
# #-#-#-#-# environment-packages.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# keystone-install.pot (Installation Guide 0.1) #-#-#-#-#
#: ../environment-packages.rst:142 ../keystone-install.rst:559
msgid "Finalize the installation"
msgstr ""
#: ../environment-packages.rst:144
msgid "Upgrade the packages on your host:"
msgstr ""
#: ../environment-packages.rst:166
msgid ""
"If the upgrade process includes a new kernel, reboot your host to activate "
"it."
msgstr ""
#: ../environment-packages.rst:169
msgid "Install the OpenStack client:"
msgstr ""
#: ../environment-packages.rst:191
msgid ""
"RHEL and CentOS enable :term:`SELinux` by default. Install the ``openstack-"
"selinux`` package to automatically manage security policies for OpenStack "
"services:"
msgstr ""
#: ../environment-security.rst:0
msgid "**Passwords**"
msgstr ""
#: ../environment-security.rst:2
msgid "Security"
msgstr ""
#: ../environment-security.rst:4
msgid ""
"OpenStack services support various security methods including password, "
"policy, and encryption. Additionally, supporting services including the "
"database server and message broker support at least password security."
msgstr ""
#: ../environment-security.rst:8
msgid ""
"To ease the installation process, this guide only covers password security "
"where applicable. You can create secure passwords manually, generate them "
"using a tool such as `pwgen <http://sourceforge.net/projects/pwgen/>`__, or "
"by running the following command:"
msgstr ""
#: ../environment-security.rst:18
msgid ""
"For OpenStack services, this guide uses ``SERVICE_PASS`` to reference "
"service account passwords and ``SERVICE_DBPASS`` to reference database "
"passwords."
msgstr ""
#: ../environment-security.rst:22
msgid ""
"The following table provides a list of services that require passwords and "
"their associated references in the guide:"
msgstr ""
#: ../environment-security.rst:29
msgid "Password name"
msgstr ""
# #-#-#-#-# environment-security.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# overview.pot (Installation Guide 0.1) #-#-#-#-#
#: ../environment-security.rst:30 ../overview.rst:25
msgid "Description"
msgstr ""
#: ../environment-security.rst:31
msgid "Database password (no variable used)"
msgstr ""
#: ../environment-security.rst:32
msgid "Root password for the database"
msgstr ""
#: ../environment-security.rst:33
msgid "``ADMIN_PASS``"
msgstr ""
#: ../environment-security.rst:34
msgid "Password of user ``admin``"
msgstr ""
#: ../environment-security.rst:35
msgid "``CEILOMETER_DBPASS``"
msgstr ""
#: ../environment-security.rst:36
msgid "Database password for the Telemetry service"
msgstr ""
#: ../environment-security.rst:37
msgid "``CEILOMETER_PASS``"
msgstr ""
#: ../environment-security.rst:38
msgid "Password of Telemetry service user ``ceilometer``"
msgstr ""
#: ../environment-security.rst:39
msgid "``CINDER_DBPASS``"
msgstr ""
#: ../environment-security.rst:40
msgid "Database password for the Block Storage service"
msgstr ""
#: ../environment-security.rst:41
msgid "``CINDER_PASS``"
msgstr ""
#: ../environment-security.rst:42
msgid "Password of Block Storage service user ``cinder``"
msgstr ""
#: ../environment-security.rst:43
msgid "``DASH_DBPASS``"
msgstr ""
#: ../environment-security.rst:44
msgid "Database password for the dashboard"
msgstr ""
#: ../environment-security.rst:45
msgid "``DEMO_PASS``"
msgstr ""
#: ../environment-security.rst:46
msgid "Password of user ``demo``"
msgstr ""
#: ../environment-security.rst:47
msgid "``GLANCE_DBPASS``"
msgstr ""
#: ../environment-security.rst:48
msgid "Database password for Image service"
msgstr ""
#: ../environment-security.rst:49
msgid "``GLANCE_PASS``"
msgstr ""
#: ../environment-security.rst:50
msgid "Password of Image service user ``glance``"
msgstr ""
#: ../environment-security.rst:51
msgid "``HEAT_DBPASS``"
msgstr ""
#: ../environment-security.rst:52
msgid "Database password for the Orchestration service"
msgstr ""
#: ../environment-security.rst:53
msgid "``HEAT_DOMAIN_PASS``"
msgstr ""
#: ../environment-security.rst:54
msgid "Password of Orchestration domain"
msgstr ""
#: ../environment-security.rst:55
msgid "``HEAT_PASS``"
msgstr ""
#: ../environment-security.rst:56
msgid "Password of Orchestration service user ``heat``"
msgstr ""
#: ../environment-security.rst:57
msgid "``KEYSTONE_DBPASS``"
msgstr ""
#: ../environment-security.rst:58
msgid "Database password of Identity service"
msgstr ""
#: ../environment-security.rst:59
msgid "``NEUTRON_DBPASS``"
msgstr ""
#: ../environment-security.rst:60
msgid "Database password for the Networking service"
msgstr ""
#: ../environment-security.rst:61
msgid "``NEUTRON_PASS``"
msgstr ""
#: ../environment-security.rst:62
msgid "Password of Networking service user ``neutron``"
msgstr ""
#: ../environment-security.rst:63
msgid "``NOVA_DBPASS``"
msgstr ""
#: ../environment-security.rst:64
msgid "Database password for Compute service"
msgstr ""
#: ../environment-security.rst:65
msgid "``NOVA_PASS``"
msgstr ""
#: ../environment-security.rst:66
msgid "Password of Compute service user ``nova``"
msgstr ""
#: ../environment-security.rst:67
msgid "``RABBIT_PASS``"
msgstr ""
#: ../environment-security.rst:68
msgid "Password of user guest of RabbitMQ"
msgstr ""
#: ../environment-security.rst:69
msgid "``SWIFT_PASS``"
msgstr ""
#: ../environment-security.rst:70
msgid "Password of Object Storage service user ``swift``"
msgstr ""
#: ../environment-security.rst:72
msgid ""
"OpenStack and supporting services require administrative privileges during "
"installation and operation. In some cases, services perform modifications to "
"the host that can interfere with deployment automation tools such as "
"Ansible, Chef, and Puppet. For example, some OpenStack services add a root "
"wrapper to ``sudo`` that can interfere with security policies. See the "
"`Cloud Administrator Guide <http://docs.openstack.org/ admin-guide-cloud/"
"compute-root-wrap-reference.html>`__ for more information."
msgstr ""
#: ../environment-security.rst:81
msgid ""
"Also, the Networking service assumes default values for kernel network "
"parameters and modifies firewall rules. To avoid most issues during your "
"initial installation, we recommend using a stock deployment of a supported "
"distribution on your hosts. However, if you choose to automate deployment of "
"your hosts, review the configuration and policies applied to them before "
"proceeding further."
msgstr ""
#: ../environment-sql-database.rst:2
msgid "SQL database"
msgstr ""
#: ../environment-sql-database.rst:4
msgid ""
"Most OpenStack services use an SQL database to store information. The "
"database typically runs on the controller node. The procedures in this guide "
"use MariaDB or MySQL depending on the distribution. OpenStack services also "
"support other SQL databases including `PostgreSQL <http://www.postgresql.org/"
">`__."
msgstr ""
#: ../environment-sql-database.rst:41
msgid "Choose a suitable password for the database root account."
msgstr ""
#: ../environment-sql-database.rst:43
msgid ""
"Create and edit the ``/etc/mysql/conf.d/mysqld_openstack.cnf`` file and "
"complete the following actions:"
msgstr ""
#: ../environment-sql-database.rst:46 ../environment-sql-database.rst:76
msgid ""
"In the ``[mysqld]`` section, set the ``bind-address`` key to the management "
"IP address of the controller node to enable access by other nodes via the "
"management network:"
msgstr ""
#: ../environment-sql-database.rst:57 ../environment-sql-database.rst:87
msgid ""
"In the ``[mysqld]`` section, set the following keys to enable useful options "
"and the UTF-8 character set:"
msgstr ""
#: ../environment-sql-database.rst:73
msgid ""
"Create and edit the ``/etc/my.cnf.d/mariadb_openstack.cnf`` file and "
"complete the following actions:"
msgstr ""
#: ../environment-sql-database.rst:118
msgid "Restart the database service:"
msgstr ""
#: ../environment-sql-database.rst:126
msgid ""
"Start the database service and configure it to start when the system boots:"
msgstr ""
#: ../environment-sql-database.rst:145
msgid ""
"Secure the database service by running the ``mysql_secure_installation`` "
"script."
msgstr ""
#: ../environment.rst:5
msgid "Environment"
msgstr ""
#: ../environment.rst:7
msgid ""
"This section explains how to configure the controller and one compute node "
"using the example architecture."
msgstr ""
#: ../environment.rst:10
msgid ""
"Although most environments include Identity, Image service, Compute, at "
"least one networking service, and the dashboard, the Object Storage service "
"can operate independently. If your use case only involves Object Storage, "
"you can skip to :ref:`swift` after configuring the appropriate nodes for it. "
"However, the dashboard requires at least the Image service, Compute, and "
"Networking."
msgstr ""
#: ../environment.rst:16
msgid ""
"You must use an account with administrative privileges to configure each "
"node. Either run the commands as the ``root`` user or configure the ``sudo`` "
"utility."
msgstr ""
#: ../environment.rst:22
msgid ""
"The :command:`systemctl enable` call on openSUSE outputs a warning message "
"when the service uses SysV Init scripts instead of native systemd files. "
"This warning can be ignored."
msgstr ""
#: ../environment.rst:26
msgid ""
"For best performance, we recommend that your environment meets or exceeds "
"the hardware requirements in :ref:`figure-hwreqs`. However, OpenStack does "
"not require a significant amount of resources and the following minimum "
"requirements should support a proof-of-concept environment with core "
"services and several :term:`CirrOS` instances:"
msgstr ""
#: ../environment.rst:32
msgid "Controller Node: 1 processor, 2 GB memory, and 5 GB storage"
msgstr ""
#: ../environment.rst:34
msgid "Compute Node: 1 processor, 2 GB memory, and 10 GB storage"
msgstr ""
#: ../environment.rst:36
msgid ""
"To minimize clutter and provide more resources for OpenStack, we recommend a "
"minimal installation of your Linux distribution. Also, you must install a 64-"
"bit version of your distribution on each node."
msgstr ""
#: ../environment.rst:40
msgid ""
"A single disk partition on each node works for most basic installations. "
"However, you should consider :term:`Logical Volume Manager (LVM)` for "
"installations with optional services such as Block Storage."
msgstr ""
#: ../environment.rst:44
msgid ""
"For first-time installation and testing purposes, many users elect to build "
"each host as a :term:`virtual machine (VM)`. The primary benefits of VMs "
"include the following:"
msgstr ""
#: ../environment.rst:48
msgid ""
"One physical server can support multiple nodes, each with almost any number "
"of network interfaces."
msgstr ""
#: ../environment.rst:51
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 ""
#: ../environment.rst:55
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 ""
#: ../environment.rst:61
msgid ""
"If you choose to install on VMs, make sure your hypervisor provides a way to "
"disable MAC address filtering on the ``public`` network interface."
msgstr ""
#: ../environment.rst:65
msgid ""
"For more information about system requirements, see the `OpenStack "
"Operations Guide <http://docs.openstack.org/ops/>`_."
msgstr ""
#: ../glance-install.rst:4
msgid ""
"This section describes how to install and configure the Image service, code-"
"named glance, on the controller node. For simplicity, this configuration "
"stores images on the local file system."
msgstr ""
#: ../glance-install.rst:13
msgid ""
"Before you install and configure the Image service, you must create a "
"database, service credentials, and API endpoints."
msgstr ""
#: ../glance-install.rst:25
msgid "Create the ``glance`` database:"
msgstr ""
#: ../glance-install.rst:31
msgid "Grant proper access to the ``glance`` database:"
msgstr ""
#: ../glance-install.rst:40
msgid "Replace ``GLANCE_DBPASS`` with a suitable password."
msgstr ""
#: ../glance-install.rst:53
msgid "Create the ``glance`` user:"
msgstr ""
#: ../glance-install.rst:69
msgid "Add the ``admin`` role to the ``glance`` user and ``service`` project:"
msgstr ""
#: ../glance-install.rst:80
msgid "Create the ``glance`` service entity:"
msgstr ""
#: ../glance-install.rst:96
msgid "Create the Image service API endpoints:"
msgstr ""
#: ../glance-install.rst:184
msgid ""
"Edit the ``/etc/glance/glance-api.conf`` file and complete the following "
"actions:"
msgstr ""
#: ../glance-install.rst:205 ../glance-install.rst:289
msgid ""
"Replace ``GLANCE_DBPASS`` with the password you chose for the Image service "
"database."
msgstr ""
#: ../glance-install.rst:208 ../glance-install.rst:292
msgid ""
"In the ``[keystone_authtoken]`` and ``[paste_deploy]`` sections, configure "
"Identity service access:"
msgstr ""
#: ../glance-install.rst:228 ../glance-install.rst:312
msgid ""
"Replace ``GLANCE_PASS`` with the password you chose for the ``glance`` user "
"in the Identity service."
msgstr ""
#: ../glance-install.rst:236
msgid ""
"In the ``[glance_store]`` section, configure the local file system store and "
"location of image files:"
msgstr ""
#: ../glance-install.rst:246 ../glance-install.rst:320
msgid ""
"In the ``[DEFAULT]`` section, configure the ``noop`` notification driver to "
"disable notifications because they only pertain to the optional Telemetry "
"service:"
msgstr ""
#: ../glance-install.rst:256 ../glance-install.rst:330
msgid ""
"The Telemetry chapter provides an Image service configuration that enables "
"notifications."
msgstr ""
#: ../glance-install.rst:268
msgid ""
"Edit the ``/etc/glance/glance-registry.conf`` file and complete the "
"following actions:"
msgstr ""
#: ../glance-install.rst:344
msgid "Populate the Image service database:"
msgstr ""
#: ../glance-install.rst:364
msgid ""
"Select the ``keystone`` pipeline to configure the Image service to use the "
"Identity service:"
msgstr ""
#: ../glance-install.rst:377
msgid ""
"Start the Image service services and configure them to start when the system "
"boots:"
msgstr ""
#: ../glance-install.rst:389
msgid "Restart the Image service services:"
msgstr ""
#: ../glance-verify.rst:4
msgid ""
"Verify operation of the Image service using `CirrOS <http://launchpad.net/"
"cirros>`__, a small Linux image that helps you test your OpenStack "
"deployment."
msgstr ""
#: ../glance-verify.rst:8
msgid ""
"For more information about how to download and build images, see `OpenStack "
"Virtual Machine Image Guide <http://docs.openstack.org/image-guide/>`__. For "
"information about how to manage images, see the `OpenStack User Guide "
"<http://docs.openstack.org/user-guide/common/cli_manage_images.html>`__."
msgstr ""
#: ../glance-verify.rst:15
msgid ""
"In each client environment script, configure the Image service client to use "
"API version 2.0:"
msgstr ""
#: ../glance-verify.rst:30
msgid "Download the source image:"
msgstr ""
#: ../glance-verify.rst:36
msgid ""
"Upload the image to the Image service using the :term:`QCOW2 <QEMU Copy On "
"Write 2 (QCOW2)>` disk format, :term:`bare` container format, and public "
"visibility so all projects can access it:"
msgstr ""
#: ../glance-verify.rst:68
msgid ""
"For information about the :command:`glance image-create` parameters, see "
"`Image service command-line client <http://docs.openstack.org/cli-reference/"
"content/ glanceclient_commands.html#glanceclient_subcommand_image-"
"create_v2>`__ in the ``OpenStack Command-Line Interface Reference``."
msgstr ""
#: ../glance-verify.rst:74
msgid ""
"For information about disk and container formats for images, see `Disk and "
"container formats for images <http://docs.openstack.org/image-guide/image-"
"formats.html>`__ in the ``OpenStack Virtual Machine Image Guide``."
msgstr ""
# #-#-#-#-# glance-verify.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# keystone-services.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# keystone-users.pot (Installation Guide 0.1) #-#-#-#-#
#: ../glance-verify.rst:81 ../keystone-services.rst:99
#: ../keystone-users.rst:36
msgid ""
"OpenStack generates IDs dynamically, so you will see different values in the "
"example command output."
msgstr ""
#: ../glance-verify.rst:84
msgid "Confirm upload of the image and validate attributes:"
msgstr ""
#: ../glance.rst:3
msgid "Add the Image service"
msgstr ""
#: ../glance.rst:11
msgid ""
"The OpenStack Image service (glance) enables users to discover, register, "
"and retrieve virtual machine images. It offers a :term:`REST <RESTful>` 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 ""
#: ../glance.rst:21
msgid ""
"For simplicity, this guide describes configuring the Image service to use "
"the ``file`` back end, which uploads and stores in a directory on the "
"controller node hosting the Image service. By default, this directory is ``/"
"var/lib/glance/images/``."
msgstr ""
#: ../glance.rst:26
msgid ""
"Before you proceed, ensure that the controller node has at least several "
"gigabytes of space available in this directory."
msgstr ""
#: ../glance.rst:29
msgid ""
"For information on requirements for other back ends, see `Configuration "
"Reference <http://docs.openstack.org/liberty/ config-reference/content/ "
"ch_configuring-openstack-image-service.html>`__."
msgstr ""
#: ../heat-install.rst:6
msgid ""
"This section describes how to install and configure the Orchestration "
"service, code-named heat, on the controller node."
msgstr ""
#: ../heat-install.rst:14
msgid ""
"Before you install and configure Orchestration, you must create a database, "
"service credentials, API endpoints. Orchestration also requires additional "
"information in the Identity service."
msgstr ""
#: ../heat-install.rst:27
msgid "Create the ``heat`` database:"
msgstr ""
#: ../heat-install.rst:33
msgid "Grant proper access to the ``heat`` database:"
msgstr ""
#: ../heat-install.rst:42
msgid "Replace ``HEAT_DBPASS`` with a suitable password."
msgstr ""
#: ../heat-install.rst:55
msgid "Create the ``heat`` user:"
msgstr ""
#: ../heat-install.rst:71
msgid "Add the ``admin`` role to the ``heat`` user:"
msgstr ""
#: ../heat-install.rst:81
msgid "Create the ``heat`` and ``heat-cfn`` service entities:"
msgstr ""
#: ../heat-install.rst:109
msgid "Create the Orchestration service API endpoints:"
msgstr ""
#: ../heat-install.rst:211
msgid ""
"Orchestration requires additional information in the Identity service to "
"manage stacks. To add this information, complete these steps:"
msgstr ""
#: ../heat-install.rst:214
msgid "Create the ``heat`` domain that contains projects and users for stacks:"
msgstr ""
#: ../heat-install.rst:229
msgid ""
"Create the ``heat_domain_admin`` user to manage projects and users in the "
"``heat`` domain:"
msgstr ""
#: ../heat-install.rst:246
msgid ""
"Add the ``admin`` role to the ``heat_domain_admin`` user in the ``heat`` "
"domain to enable administrative stack management privileges by the "
"``heat_domain_admin`` user:"
msgstr ""
#: ../heat-install.rst:258
msgid "Create the ``heat_stack_owner`` role:"
msgstr ""
#: ../heat-install.rst:270
msgid ""
"Add the ``heat_stack_owner`` role to the ``demo`` project and user to enable "
"stack management by the ``demo`` user:"
msgstr ""
#: ../heat-install.rst:283
msgid ""
"You must add the ``heat_stack_owner`` role to each user that manages stacks."
msgstr ""
#: ../heat-install.rst:286
msgid "Create the ``heat_stack_user`` role:"
msgstr ""
#: ../heat-install.rst:300
msgid ""
"The Orchestration service automatically assigns the ``heat_stack_user`` role "
"to users that it creates during stack deployment. By default, this role "
"restricts :term:`API` operations. To avoid conflicts, do not add this role "
"to users with the ``heat_stack_owner`` role."
msgstr ""
#: ../heat-install.rst:342 ../heat-install.rst:476
msgid ""
"Edit the ``/etc/heat/heat.conf`` file and complete the following actions:"
msgstr ""
#: ../heat-install.rst:363
msgid ""
"Replace ``HEAT_DBPASS`` with the password you chose for the Orchestration "
"database."
msgstr ""
#: ../heat-install.rst:384
msgid ""
"In the ``[keystone_authtoken]``, ``[trustee]``, ``[clients_keystone]``, and "
"``[ec2authtoken]`` sections, configure Identity service access:"
msgstr ""
#: ../heat-install.rst:420
msgid ""
"Replace ``HEAT_PASS`` with the password you chose for the ``heat`` user in "
"the Identity service."
msgstr ""
#: ../heat-install.rst:423
msgid ""
"In the ``[DEFAULT]`` section, configure the metadata and wait condition URLs:"
msgstr ""
#: ../heat-install.rst:433
msgid ""
"In the ``[DEFAULT]`` section, configure the stack domain and administrative "
"credentials:"
msgstr ""
#: ../heat-install.rst:444
msgid ""
"Replace ``HEAT_DOMAIN_PASS`` with the password you chose for the "
"``heat_domain_admin`` user in the Identity service."
msgstr ""
#: ../heat-install.rst:456
msgid "Populate the Orchestration database:"
msgstr ""
#: ../heat-install.rst:464
msgid "Run the following commands to install the packages:"
msgstr ""
#: ../heat-install.rst:479
msgid "In the ``[ec2authtoken]`` section, configure Identity service access:"
msgstr ""
#: ../heat-install.rst:492
msgid ""
"Start the Orchestration services and configure them to start when the system "
"boots:"
msgstr ""
#: ../heat-install.rst:504
msgid "Restart the Orchestration services:"
msgstr ""
#: ../heat-next-steps.rst:6
msgid ""
"Your OpenStack environment now includes Orchestration. You can :ref:`launch-"
"instance` or add more services to your environment in the following chapters."
msgstr ""
#: ../heat-verify.rst:6
msgid "Verify operation of the Orchestration service."
msgstr ""
#: ../heat-verify.rst:8
msgid "Source the ``admin`` tenant credentials:"
msgstr ""
# #-#-#-#-# heat-verify.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# nova-verify.pot (Installation Guide 0.1) #-#-#-#-#
#: ../heat-verify.rst:14 ../nova-verify.rst:17
msgid ""
"List service components to verify successful launch and registration of each "
"process:"
msgstr ""
#: ../heat-verify.rst:31
msgid ""
"This output should indicate four ``heat-engine`` components on the "
"controller node."
msgstr ""
#: ../heat.rst:3
msgid "Add the Orchestration service"
msgstr ""
#: ../heat.rst:12
msgid ""
"The Orchestration service (heat) uses a heat orchestration template (HOT) to "
"create and manage cloud resources."
msgstr ""
#: ../horizon-install.rst:4
msgid ""
"This section describes how to install and configure the dashboard on the "
"controller node."
msgstr ""
#: ../horizon-install.rst:7
msgid ""
"The dashboard relies on functional core services including Identity, Image "
"service, Compute, and either Networking (neutron) or legacy networking (nova-"
"network). Environments with stand-alone services such as Object Storage "
"cannot use the dashboard. For more information, see the `developer "
"documentation <http://docs.openstack.org/developer/ horizon/topics/"
"deployment.html>`__."
msgstr ""
#: ../horizon-install.rst:17
msgid ""
"This section assumes proper installation, configuration, and operation of "
"the Identity service using the Apache HTTP server and Memcached service as "
"described in the :ref:`Install and configure the Identity service <keystone-"
"install>` section."
msgstr ""
#: ../horizon-install.rst:61
msgid "Respond to prompts for web server configuration."
msgstr ""
#: ../horizon-install.rst:65
msgid ""
"The automatic configuration process generates a self-signed SSL certificate. "
"Consider obtaining an official certificate for production environments."
msgstr ""
#: ../horizon-install.rst:71
msgid ""
"There are two modes of installation. One using ``/horizon`` as the URL, "
"keeping your default vhost and only adding an Alias directive: this is the "
"default. The other mode will remove the default Apache vhost and install the "
"dashboard on the webroot. It was the only available option before the "
"Liberty release. If you prefer to set the Apache configuration manually, "
"install the ``openstack-dashboard`` package instead of ``openstack-dashboard-"
"apache``."
msgstr ""
#: ../horizon-install.rst:81
msgid "Configure the web server:"
msgstr ""
#: ../horizon-install.rst:89
msgid ""
"Edit the ``/srv/www/openstack-dashboard/openstack_dashboard/local/"
"local_settings.py`` file and complete the following actions:"
msgstr ""
#: ../horizon-install.rst:93 ../horizon-install.rst:144
#: ../horizon-install.rst:195
msgid ""
"Configure the dashboard to use OpenStack services on the ``controller`` node:"
msgstr ""
#: ../horizon-install.rst:100 ../horizon-install.rst:151
#: ../horizon-install.rst:202
msgid "Allow all hosts to access the dashboard:"
msgstr ""
#: ../horizon-install.rst:106 ../horizon-install.rst:157
#: ../horizon-install.rst:208
msgid "Configure the ``memcached`` session storage service:"
msgstr ""
#: ../horizon-install.rst:119 ../horizon-install.rst:170
#: ../horizon-install.rst:221
msgid "Comment out any other session storage configuration."
msgstr ""
#: ../horizon-install.rst:121 ../horizon-install.rst:172
#: ../horizon-install.rst:223
msgid ""
"Configure ``user`` as the default role for users that you create via the "
"dashboard:"
msgstr ""
#: ../horizon-install.rst:128 ../horizon-install.rst:179
#: ../horizon-install.rst:230
msgid "Optionally, configure the time zone:"
msgstr ""
#: ../horizon-install.rst:134 ../horizon-install.rst:185
#: ../horizon-install.rst:236
msgid ""
"Replace ``TIME_ZONE`` with an appropriate time zone identifier. For more "
"information, see the `list of time zones <http://en.wikipedia.org/wiki/"
"List_of_tz_database_time_zones>`__."
msgstr ""
#: ../horizon-install.rst:140
msgid ""
"Edit the ``/etc/openstack-dashboard/local_settings`` file and complete the "
"following actions:"
msgstr ""
#: ../horizon-install.rst:191
msgid ""
"Edit the ``/etc/openstack-dashboard/local_settings.py`` file and complete "
"the following actions:"
msgstr ""
#: ../horizon-install.rst:245
msgid "Reload the web server configuration:"
msgstr ""
#: ../horizon-install.rst:253 ../horizon-install.rst:266
msgid "Restart the web server and session storage service:"
msgstr ""
#: ../horizon-install.rst:261 ../horizon-install.rst:274
msgid ""
"The ``systemctl restart`` command starts each service if not currently "
"running."
msgstr ""
#: ../horizon-next-steps.rst:5
msgid ""
"Your OpenStack environment now includes the dashboard. You can :ref:`launch-"
"instance` or add more services to your environment."
msgstr ""
#: ../horizon-next-steps.rst:8
msgid ""
"After you install and configure the dashboard, you can complete the "
"following tasks:"
msgstr ""
#: ../horizon-next-steps.rst:11
msgid ""
"Provide users with a public IP address, a username, and a password so they "
"can access the dashboard through a web browser. In case of any SSL "
"certificate connection problems, point the server IP address to a domain "
"name, and give users access."
msgstr ""
#: ../horizon-next-steps.rst:16
msgid ""
"Customize your dashboard. See section `Customize the dashboard <http://docs."
"openstack.org/admin-guide-cloud/common/dashboard_customizing.html>`__."
msgstr ""
#: ../horizon-next-steps.rst:20
msgid ""
"Set up session storage. See `Set up session storage for the dashboard "
"<http://docs.openstack.org/admin-guide-cloud/dashboard_sessions.html>`__."
msgstr ""
#: ../horizon-next-steps.rst:24
msgid ""
"To use the VNC client with the dashboard, the browser must support HTML5 "
"Canvas and HTML5 WebSockets."
msgstr ""
#: ../horizon-next-steps.rst:27
msgid ""
"For details about browsers that support noVNC, see `README <https://github."
"com/kanaka/noVNC/blob/master/README.md>`__ and `browser support <https://"
"github.com/kanaka/noVNC/wiki/Browser-support>`__."
msgstr ""
#: ../horizon-verify.rst:4
msgid "Verify operation of the dashboard."
msgstr ""
#: ../horizon-verify.rst:8
msgid "Access the dashboard using a web browser at ``http://controller/``."
msgstr ""
#: ../horizon-verify.rst:13
msgid ""
"Access the dashboard using a web browser at ``http://controller/dashboard``."
msgstr ""
#: ../horizon-verify.rst:18
msgid ""
"Access the dashboard using a web browser at ``http://controller/horizon``."
msgstr ""
#: ../horizon-verify.rst:21
msgid "Authenticate using ``admin`` or ``demo`` user credentials."
msgstr ""
#: ../horizon.rst:3
msgid "Add the dashboard"
msgstr ""
#: ../horizon.rst:5
msgid ""
"The OpenStack Dashboard, also known as `horizon <https://git.openstack.org/"
"cgit/openstack/horizon>`__ is a web interface that enables cloud "
"administrators and users to manage various OpenStack resources and services."
msgstr ""
#: ../horizon.rst:10
msgid ""
"The Dashboard enables web-based interactions with the OpenStack Compute "
"cloud controller through the OpenStack APIs."
msgstr ""
#: ../horizon.rst:13
msgid "Horizon enables you to customize the brand of the dashboard."
msgstr ""
#: ../horizon.rst:15
msgid ""
"Horizon provides a set of core classes and reusable templates and tools."
msgstr ""
#: ../horizon.rst:17
msgid "This example deployment uses an Apache web server."
msgstr ""
#: ../index.rst:9
msgid "OpenStack Installation Guide for Red Hat Enterprise Linux and CentOS"
msgstr ""
#: ../index.rst:15
msgid "OpenStack Installation Guide for openSUSE and SUSE Linux Enterprise"
msgstr ""
#: ../index.rst:21
msgid "OpenStack Installation Guide for Ubuntu"
msgstr ""
#: ../index.rst:27
msgid "OpenStack Installation Guide for Debian"
msgstr ""
#: ../index.rst:31
msgid "Abstract"
msgstr ""
#: ../index.rst:33
msgid ""
"The OpenStack system consists of several key projects that you install "
"separately. These projects 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."
msgstr ""
#: ../index.rst:42
msgid ""
"This guide shows you how to install OpenStack by using packages available on "
"Red Hat Enterprise Linux 7 and its derivatives through the EPEL repository."
msgstr ""
#: ../index.rst:48
msgid ""
"This guide walks through an installation by using packages available through "
"Canonical's Ubuntu Cloud archive repository."
msgstr ""
#: ../index.rst:53
msgid ""
"This guide shows you how to install OpenStack by using packages on openSUSE "
"13.2 and SUSE Linux Enterprise Server 12 through the Open Build Service "
"Cloud repository."
msgstr ""
#: ../index.rst:59
msgid ""
"This guide walks through an installation by using packages available through "
"Debian 8 (code name: Jessie)."
msgstr ""
#: ../index.rst:62
msgid ""
"Explanations of configuration options and sample configuration files are "
"included."
msgstr ""
#: ../index.rst:65
msgid "This guide documents OpenStack Liberty release."
msgstr ""
#: ../index.rst:69
msgid ""
"This guide is a work-in-progress and is subject to frequent updates. Pre-"
"release packages have been used for testing, and some instructions might not "
"work with final versions. Please help us make this guide better by reporting "
"any errors you encounter."
msgstr ""
#: ../index.rst:75
msgid "Contents"
msgstr ""
#: ../index.rst:130
msgid "Search in this guide"
msgstr ""
#: ../index.rst:132
msgid ":ref:`search`"
msgstr ""
#: ../keystone-install.rst:6
msgid ""
"This section describes how to install and configure the OpenStack Identity "
"service, code-named keystone, on the controller node. For performance, this "
"configuration deploys the Apache HTTP server to handle requests and "
"Memcached to store tokens instead of an SQL database."
msgstr ""
#: ../keystone-install.rst:16
msgid ""
"Before you configure the OpenStack Identity service, you must create a "
"database and an administration token."
msgstr ""
#: ../keystone-install.rst:19
msgid "To create the database, complete the following actions:"
msgstr ""
#: ../keystone-install.rst:28
msgid "Create the ``keystone`` database:"
msgstr ""
#: ../keystone-install.rst:34
msgid "Grant proper access to the ``keystone`` database:"
msgstr ""
#: ../keystone-install.rst:43
msgid "Replace ``KEYSTONE_DBPASS`` with a suitable password."
msgstr ""
#: ../keystone-install.rst:47 ../keystone-install.rst:224
msgid ""
"Generate a random value to use as the administration token during initial "
"configuration:"
msgstr ""
#: ../keystone-install.rst:62
msgid ""
"In Kilo and Liberty releases, the keystone project deprecates eventlet in "
"favor of a separate web server with WSGI extensions. This guide uses the "
"Apache HTTP server with ``mod_wsgi`` to serve Identity service requests on "
"port 5000 and 35357. By default, the keystone service still listens on ports "
"5000 and 35357. Therefore, this guide disables the keystone service. The "
"keystone project plans to remove eventlet support in Mitaka."
msgstr ""
#: ../keystone-install.rst:72
msgid ""
"Disable the keystone service from starting automatically after installation:"
msgstr ""
#: ../keystone-install.rst:79 ../keystone-install.rst:90
#: ../keystone-install.rst:201
msgid "Run the following command to install the packages:"
msgstr ""
#: ../keystone-install.rst:108
msgid ""
"Start the Memcached service and configure it to start when the system boots:"
msgstr ""
#: ../keystone-install.rst:118
msgid ""
"Edit the ``/etc/keystone/keystone.conf`` file and complete the following "
"actions:"
msgstr ""
#: ../keystone-install.rst:121
msgid ""
"In the ``[DEFAULT]`` section, define the value of the initial administration "
"token:"
msgstr ""
#: ../keystone-install.rst:130
msgid ""
"Replace ``ADMIN_TOKEN`` with the random value that you generated in a "
"previous step."
msgstr ""
#: ../keystone-install.rst:151
msgid ""
"Replace ``KEYSTONE_DBPASS`` with the password you chose for the database."
msgstr ""
#: ../keystone-install.rst:153
msgid "In the ``[memcache]`` section, configure the Memcache service:"
msgstr ""
#: ../keystone-install.rst:161
msgid ""
"In the ``[token]`` section, configure the UUID token provider and Memcached "
"driver:"
msgstr ""
#: ../keystone-install.rst:171
msgid "In the ``[revoke]`` section, configure the SQL revocation driver:"
msgstr ""
#: ../keystone-install.rst:190
msgid "Populate the Identity service database:"
msgstr ""
#: ../keystone-install.rst:199
msgid "Install and configure the components"
msgstr ""
#: ../keystone-install.rst:207
msgid ""
"Respond to prompts for :doc:`debconf/debconf-dbconfig-common`, which will "
"fill the below database access directive."
msgstr ""
#: ../keystone-install.rst:216
msgid ""
"If you decide to not use ``dbconfig-common``, then you have to create the "
"database and manage its access rights yourself, and run the following by "
"hand."
msgstr ""
#: ../keystone-install.rst:231
msgid "Configure the initial administration token:"
msgstr ""
#: ../keystone-install.rst:236
msgid ""
"Use the random value that you generated in a previous step. If you install "
"using non-interactive mode or you do not specify this token, the "
"configuration tool generates a random value."
msgstr ""
#: ../keystone-install.rst:240
msgid ""
"Later on, the package will configure the below directive with the value you "
"entered:"
msgstr ""
#: ../keystone-install.rst:249
msgid "Create the ``admin`` project and user:"
msgstr ""
#: ../keystone-install.rst:251
msgid ""
"During the final stage of the package installation, it is possible to "
"automatically create an ``admin`` and ``service`` project, and an ``admin`` "
"user. This can later be used for other OpenStack services to contact the "
"Identity service. This is the equivalent of running the below commands:"
msgstr ""
#: ../keystone-install.rst:314
msgid ""
"In Debian, the Keystone package offers automatic registration of Keystone in "
"the service catalogue. This is equivalent of running the below commands:"
msgstr ""
#: ../keystone-install.rst:353
msgid "Configure the Apache HTTP server"
msgstr ""
#: ../keystone-install.rst:357
msgid ""
"Edit the ``/etc/httpd/conf/httpd.conf`` file and configure the "
"``ServerName`` option to reference the controller node:"
msgstr ""
#: ../keystone-install.rst:364
msgid ""
"Create the ``/etc/httpd/conf.d/wsgi-keystone.conf`` file with the following "
"content:"
msgstr ""
#: ../keystone-install.rst:420
msgid ""
"Edit the ``/etc/apache2/apache2.conf`` file and configure the ``ServerName`` "
"option to reference the controller node:"
msgstr ""
#: ../keystone-install.rst:427
msgid ""
"Create the ``/etc/apache2/sites-available/wsgi-keystone.conf`` file with the "
"following content:"
msgstr ""
#: ../keystone-install.rst:481
msgid "Enable the Identity service virtual hosts:"
msgstr ""
#: ../keystone-install.rst:489
msgid ""
"Edit the ``/etc/sysconfig/apache2`` file and configure the "
"``APACHE_SERVERNAME`` option to reference the controller node:"
msgstr ""
#: ../keystone-install.rst:496
msgid ""
"Create the ``/etc/apache2/conf.d/wsgi-keystone.conf`` file with the "
"following content:"
msgstr ""
#: ../keystone-install.rst:550
msgid "Recursively change the ownership of the ``/etc/keystone`` directory:"
msgstr ""
#: ../keystone-install.rst:563
msgid "Restart the Apache HTTP server:"
msgstr ""
#: ../keystone-install.rst:580 ../keystone-install.rst:595
msgid ""
"Start the Apache HTTP service and configure it to start when the system "
"boots:"
msgstr ""
#: ../keystone-install.rst:589
msgid "Activate the Apache module ``mod_version``:"
msgstr ""
#: ../keystone-openrc.rst:2
msgid "Create OpenStack client environment scripts"
msgstr ""
#: ../keystone-openrc.rst:4
msgid ""
"The previous section used a combination of environment variables and command "
"options to interact with the Identity service via the ``openstack`` client. "
"To increase efficiency of client operations, OpenStack supports simple "
"client environment scripts also known as OpenRC files. These scripts "
"typically contain common options for all clients, but also support unique "
"options. For more information, see the `OpenStack User Guide <http://docs."
"openstack.org/user-guide/common/ "
"cli_set_environment_variables_using_openstack_rc.html>`__."
msgstr ""
#: ../keystone-openrc.rst:14
msgid "Creating the scripts"
msgstr ""
#: ../keystone-openrc.rst:16
msgid ""
"Create client environment scripts for the ``admin`` and ``demo`` projects "
"and users. Future portions of this guide reference these scripts to load "
"appropriate credentials for client operations."
msgstr ""
#: ../keystone-openrc.rst:20
msgid "Edit the ``admin-openrc.sh`` file and add the following content:"
msgstr ""
#: ../keystone-openrc.rst:33
msgid ""
"Replace ``ADMIN_PASS`` with the password you chose for the ``admin`` user in "
"the Identity service."
msgstr ""
#: ../keystone-openrc.rst:36
msgid "Edit the ``demo-openrc.sh`` file and add the following content:"
msgstr ""
#: ../keystone-openrc.rst:49
msgid ""
"Replace ``DEMO_PASS`` with the password you chose for the ``demo`` user in "
"the Identity service."
msgstr ""
#: ../keystone-openrc.rst:53
msgid "Using the scripts"
msgstr ""
#: ../keystone-openrc.rst:55
msgid ""
"To run clients as a specific project and user, you can simply load the "
"associated client environment script prior to running them. For example:"
msgstr ""
#: ../keystone-openrc.rst:59
msgid ""
"Load the ``admin-openrc.sh`` file to populate environment variables with the "
"location of the Identity service and the ``admin`` project and user "
"credentials:"
msgstr ""
#: ../keystone-openrc.rst:67
msgid "Request an authentication token:"
msgstr ""
#: ../keystone-services.rst:2 ../keystone-services.rst:75
msgid "Create the service entity and API endpoints"
msgstr ""
#: ../keystone-services.rst:4
msgid ""
"The Identity service provides a catalog of services and their locations. "
"Each service that you add to your OpenStack environment requires a :term:"
"`service` entity and several :term:`API endpoints<API endpoint>` in the "
"catalog."
msgstr ""
#: ../keystone-services.rst:14
msgid ""
"By default, the Identity service database contains no information to support "
"conventional authentication and catalog services. You must use a temporary "
"authentication token that you created in the section called :doc:`keystone-"
"install` to initialize the service entity and API endpoint for the Identity "
"service."
msgstr ""
#: ../keystone-services.rst:24
msgid ""
"The packages can automatically create the service entity and API endpoints."
msgstr ""
#: ../keystone-services.rst:27
msgid ""
"You must pass the value of the authentication token to the :command:"
"`openstack` command with the ``--os-token`` parameter or set the OS_TOKEN "
"environment variable. Similarly, you must also pass the value of the "
"Identity service URL to the :command:`openstack` command with the ``--os-"
"url`` parameter or set the OS_URL environment variable. This guide uses "
"environment variables to reduce command length."
msgstr ""
#: ../keystone-services.rst:36
msgid ""
"For security reasons, do not use the temporary authentication token for "
"longer than necessary to initialize the Identity service."
msgstr ""
#: ../keystone-services.rst:39
msgid "Configure the authentication token:"
msgstr ""
#: ../keystone-services.rst:47
msgid ""
"Replace ``ADMIN_TOKEN`` with the authentication token that you generated in "
"the section called :doc:`keystone-install`. For example:"
msgstr ""
#: ../keystone-services.rst:55
msgid "Configure the endpoint URL:"
msgstr ""
#: ../keystone-services.rst:65
msgid ""
"The packages can automatically create the service entity and API endpoint."
msgstr ""
#: ../keystone-services.rst:68
msgid "Configure the Identity API version:"
msgstr ""
#: ../keystone-services.rst:77
msgid ""
"The Identity service manages a catalog of services in your OpenStack "
"environment. Services use this catalog to determine the other services "
"available in your environment."
msgstr ""
#: ../keystone-services.rst:81
msgid "Create the service entity for the Identity service:"
msgstr ""
#: ../keystone-services.rst:102
msgid ""
"The Identity service manages a catalog of API endpoints associated with the "
"services in your OpenStack environment. Services use this catalog to "
"determine how to communicate with other services in your environment."
msgstr ""
#: ../keystone-services.rst:106
msgid ""
"OpenStack uses three API endpoint variants for each service: admin, "
"internal, and public. The admin API endpoint allows modifying users and "
"tenants by default, while the public and internal APIs do not allow these "
"operations. In a production environment, the variants might reside on "
"separate networks that service different types of users for security "
"reasons. For instance, the public API network might be visible from the "
"Internet so customers can manage their clouds. The admin API network might "
"be restricted to operators within the organization that manages cloud "
"infrastructure. The internal API network might be restricted to the hosts "
"that contain OpenStack services. Also, OpenStack supports multiple regions "
"for scalability. For simplicity, this guide uses the management network for "
"all endpoint variations and the default ``RegionOne`` region."
msgstr ""
#: ../keystone-services.rst:120
msgid "Create the Identity service API endpoints:"
msgstr ""
#: ../keystone-services.rst:174
msgid ""
"Each service that you add to your OpenStack environment requires one or more "
"service entities and three API endpoint variants in the Identity service."
msgstr ""
#: ../keystone-users.rst:2
msgid "Create projects, users, and roles"
msgstr ""
#: ../keystone-users.rst:4
msgid ""
"The Identity service provides authentication services for each OpenStack "
"service. The authentication service uses a combination of :term:`domains "
"<domain>`, :term:`projects<project>` (tenants), :term:`users<user>`, and :"
"term:`roles<role>`."
msgstr ""
#: ../keystone-users.rst:11
msgid "For simplicity, this guide uses the ``default`` domain."
msgstr ""
#: ../keystone-users.rst:13
msgid ""
"Create an administrative project, user, and role for administrative "
"operations in your environment:"
msgstr ""
#: ../keystone-users.rst:16
msgid "Create the ``admin`` project:"
msgstr ""
#: ../keystone-users.rst:39
msgid "Create the ``admin`` user:"
msgstr ""
#: ../keystone-users.rst:56
msgid "Create the ``admin`` role:"
msgstr ""
#: ../keystone-users.rst:68
msgid "Add the ``admin`` role to the ``admin`` project and user:"
msgstr ""
#: ../keystone-users.rst:80
msgid ""
"Any roles that you create must map to roles specified in the ``policy.json`` "
"file in the configuration file directory of each OpenStack service. The "
"default policy for most services grants administrative access to the "
"``admin`` role. For more information, see the `Operations Guide - Managing "
"Projects and Users <http://docs.openstack.org/openstack-ops/content/"
"projects_users.html>`__."
msgstr ""
#: ../keystone-users.rst:87
msgid ""
"This guide uses a service project that contains a unique user for each "
"service that you add to your environment. Create the ``service`` project:"
msgstr ""
#: ../keystone-users.rst:107
msgid ""
"Regular (non-admin) tasks should use an unprivileged project and user. As an "
"example, this guide creates the ``demo`` project and user."
msgstr ""
#: ../keystone-users.rst:110
msgid "Create the ``demo`` project:"
msgstr ""
#: ../keystone-users.rst:130
msgid ""
"Do not repeat this step when creating additional users for this project."
msgstr ""
#: ../keystone-users.rst:133
msgid "Create the ``demo`` user:"
msgstr ""
#: ../keystone-users.rst:150
msgid "Create the ``user`` role:"
msgstr ""
#: ../keystone-users.rst:162
msgid "Add the ``user`` role to the ``demo`` project and user:"
msgstr ""
#: ../keystone-users.rst:174
msgid "You can repeat this procedure to create additional projects and users."
msgstr ""
#: ../keystone-verify.rst:4
msgid ""
"Verify operation of the Identity service before installing other services."
msgstr ""
#: ../keystone-verify.rst:9 ../keystone-verify.rst:19
msgid ""
"For security reasons, disable the temporary authentication token mechanism:"
msgstr ""
#: ../keystone-verify.rst:12
msgid ""
"Edit the ``/etc/keystone/keystone-paste.ini`` file and remove "
"``admin_token_auth`` from the ``[pipeline:public_api]``, ``[pipeline:"
"admin_api]``, and ``[pipeline:api_v3]`` sections."
msgstr ""
#: ../keystone-verify.rst:22
msgid ""
"Edit the ``/usr/share/keystone/keystone-dist-paste.ini`` file and remove "
"``admin_token_auth`` from the ``[pipeline:public_api]``, ``[pipeline:"
"admin_api]``, and ``[pipeline:api_v3]`` sections."
msgstr ""
#: ../keystone-verify.rst:27
msgid "Unset the temporary ``OS_TOKEN`` and ``OS_URL`` environment variables:"
msgstr ""
#: ../keystone-verify.rst:33
msgid "As the ``admin`` user, request an authentication token:"
msgstr ""
#: ../keystone-verify.rst:53
msgid "This command uses the password for the ``admin`` user."
msgstr ""
#: ../keystone-verify.rst:55
msgid "As the ``demo`` user, request an authentication token:"
msgstr ""
#: ../keystone-verify.rst:75
msgid ""
"This command uses the password for the ``demo`` user and API port 5000 which "
"only allows regular (non-admin) access to the Identity service API."
msgstr ""
#: ../keystone.rst:3
msgid "Add the Identity service"
msgstr ""
# #-#-#-#-# launch-instance-cinder.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# launch-instance.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# overview.pot (Installation Guide 0.1) #-#-#-#-#
#: ../launch-instance-cinder.rst:4 ../launch-instance.rst:122
#: ../overview.rst:163
msgid "Block Storage"
msgstr ""
#: ../launch-instance-cinder.rst:7
msgid "Create a volume"
msgstr ""
# #-#-#-#-# launch-instance-cinder.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# launch-instance-heat.pot (Installation Guide 0.1) #-#-#-#-#
#: ../launch-instance-cinder.rst:9 ../launch-instance-heat.rst:52
msgid ""
"Source the ``demo`` credentials to perform the following steps as a non-"
"administrative project:"
msgstr ""
#: ../launch-instance-cinder.rst:16
msgid "Create a 1 GB volume:"
msgstr ""
#: ../launch-instance-cinder.rst:47
msgid ""
"After a short time, the volume status should change from ``creating`` to "
"``available``:"
msgstr ""
#: ../launch-instance-cinder.rst:60
msgid "Attach the volume to an instance"
msgstr ""
#: ../launch-instance-cinder.rst:62
msgid "Attach a volume to an instance:"
msgstr ""
#: ../launch-instance-cinder.rst:68
msgid ""
"Replace ``INSTANCE_NAME`` with the name of the instance and ``VOLUME_ID`` "
"with the ID of the volume you want to attach to it."
msgstr ""
# #-#-#-#-# launch-instance-cinder.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# launch-instance-networks-private.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# launch-instance-networks-public.pot (Installation Guide 0.1) #-#-#-#-#
#: ../launch-instance-cinder.rst:71
#: ../launch-instance-networks-private.rst:100
#: ../launch-instance-networks-public.rst:109
msgid "**Example**"
msgstr ""
#: ../launch-instance-cinder.rst:73
msgid ""
"Attach the ``09e3743e-192a-4ada-b8ee-d35352fa65c4`` volume to the ``public-"
"instance`` instance:"
msgstr ""
#: ../launch-instance-cinder.rst:88
msgid "List volumes:"
msgstr ""
#: ../launch-instance-cinder.rst:99
msgid ""
"Access your instance using SSH and use the ``fdisk`` command to verify "
"presence of the volume as the ``/dev/vdb`` block storage device:"
msgstr ""
#: ../launch-instance-cinder.rst:127
msgid ""
"You must create a file system on the device and mount it to use the volume."
msgstr ""
#: ../launch-instance-cinder.rst:130
msgid ""
"For more information about how to manage volumes, see the `OpenStack User "
"Guide <http://docs.openstack.org/user-guide/index.html>`__."
msgstr ""
#: ../launch-instance-cinder.rst:134
msgid "Return to :ref:`launch-instance`."
msgstr ""
# #-#-#-#-# launch-instance-heat.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# launch-instance.pot (Installation Guide 0.1) #-#-#-#-#
#: ../launch-instance-heat.rst:4 ../launch-instance.rst:133
msgid "Orchestration"
msgstr ""
#: ../launch-instance-heat.rst:7
msgid "Create a template"
msgstr ""
#: ../launch-instance-heat.rst:9
msgid ""
"The Orchestration service uses templates to describe stacks. To learn about "
"the template language, see `the Template Guide <http://docs.openstack.org/"
"developer/heat/template_guide/index.html>`__ in the `Heat developer "
"documentation <http://docs.openstack.org/developer/heat/index.html>`__."
msgstr ""
#: ../launch-instance-heat.rst:15
msgid "Create the ``demo-template.yml`` file with the following content:"
msgstr ""
#: ../launch-instance-heat.rst:48
msgid "Create a stack"
msgstr ""
#: ../launch-instance-heat.rst:50
msgid "Create a stack using the ``demo-template.yml`` template."
msgstr ""
#: ../launch-instance-heat.rst:59
msgid "Determine available networks."
msgstr ""
#: ../launch-instance-heat.rst:73
msgid "This output may differ from your environment."
msgstr ""
#: ../launch-instance-heat.rst:75
msgid ""
"Set the ``NET_ID`` environment variable to reflect the ID of a network. For "
"example, using the ``public`` network:"
msgstr ""
#: ../launch-instance-heat.rst:82
msgid "Create a stack of one CirrOS instance on the public network:"
msgstr ""
#: ../launch-instance-heat.rst:93
msgid "After a short time, verify successful creation of the stack:"
msgstr ""
#: ../launch-instance-heat.rst:104
msgid ""
"Show the name and IP address of the instance and compare with the output of "
"the ``nova`` command:"
msgstr ""
#: ../launch-instance-heat.rst:130
msgid "Delete the stack."
msgstr ""
#: ../launch-instance-networks-private.rst:4
msgid "Private project network"
msgstr ""
#: ../launch-instance-networks-private.rst:6
msgid ""
"If you chose networking option 2, you can also create a private project "
"virtual network that connects to the physical network infrastructure via "
"layer-3 (routing) and NAT. This network includes a DHCP server that provides "
"IP addresses to instances. An instance on this network can automatically "
"access external networks such as the Internet. However, access to an "
"instance on this network from external networks such as the Internet "
"requires a :term:`floating IP address`."
msgstr ""
#: ../launch-instance-networks-private.rst:14
msgid ""
"The ``demo`` or other unprivileged user can create this network because it "
"only provides connectivity to instances within the ``demo`` project."
msgstr ""
#: ../launch-instance-networks-private.rst:19
msgid ""
"You must :ref:`create the public provider network <launch-instance-networks-"
"public>` before the private project network."
msgstr ""
# #-#-#-#-# launch-instance-networks-private.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# launch-instance-networks-public.pot (Installation Guide 0.1) #-#-#-#-#
#: ../launch-instance-networks-private.rst:24
#: ../launch-instance-networks-public.rst:17
msgid ""
"The following instructions and diagrams use example IP address ranges. You "
"must adjust them for your particular environment."
msgstr ""
#: ../launch-instance-networks-private.rst:30
msgid "**Networking Option 2: Self-service networks - Overview**"
msgstr ""
#: ../launch-instance-networks-private.rst:35
msgid "**Networking Option 2: Self-service networks - Connectivity**"
msgstr ""
#: ../launch-instance-networks-private.rst:38
msgid "Create the private project network"
msgstr ""
# #-#-#-#-# launch-instance-networks-private.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# launch-instance-private.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# launch-instance-public.pot (Installation Guide 0.1) #-#-#-#-#
#: ../launch-instance-networks-private.rst:40
#: ../launch-instance-private.rst:12 ../launch-instance-public.rst:12
msgid ""
"On the controller node, source the ``demo`` credentials to gain access to "
"user-only CLI commands:"
msgstr ""
# #-#-#-#-# launch-instance-networks-private.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# launch-instance-networks-public.pot (Installation Guide 0.1) #-#-#-#-#
#: ../launch-instance-networks-private.rst:47
#: ../launch-instance-networks-public.rst:40
msgid "Create the network:"
msgstr ""
#: ../launch-instance-networks-private.rst:68
msgid ""
"Non-privileged users typically cannot supply additional parameters to this "
"command. The service automatically chooses paramters using information from "
"the following files:"
msgstr ""
# #-#-#-#-# launch-instance-networks-private.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# launch-instance-networks-public.pot (Installation Guide 0.1) #-#-#-#-#
#: ../launch-instance-networks-private.rst:72
#: ../launch-instance-networks-public.rst:72
msgid "``ml2_conf.ini``:"
msgstr ""
# #-#-#-#-# launch-instance-networks-private.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# launch-instance-networks-public.pot (Installation Guide 0.1) #-#-#-#-#
#: ../launch-instance-networks-private.rst:82
#: ../launch-instance-networks-public.rst:86
msgid "Create a subnet on the network:"
msgstr ""
#: ../launch-instance-networks-private.rst:89
msgid ""
"Replace ``PRIVATE_NETWORK_CIDR`` with the subnet you want to use on the "
"private network. You can use any arbitrary value, although we recommend a "
"network from `RFC 1918 <https://tools.ietf.org/html/rfc1918>`_."
msgstr ""
# #-#-#-#-# launch-instance-networks-private.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# launch-instance-networks-public.pot (Installation Guide 0.1) #-#-#-#-#
#: ../launch-instance-networks-private.rst:93
#: ../launch-instance-networks-public.rst:102
msgid ""
"Replace ``DNS_RESOLVER`` with the IP address of a DNS resolver. In most "
"cases, you can use one from the ``/etc/resolv.conf`` file on the host."
msgstr ""
#: ../launch-instance-networks-private.rst:97
msgid ""
"Replace ``PRIVATE_NETWORK_GATEWAY`` with the gateway you want to use on the "
"private network, typically the \".1\" IP address."
msgstr ""
#: ../launch-instance-networks-private.rst:102
msgid ""
"The private network uses 172.16.1.0/24 with a gateway on 172.16.1.1. A DHCP "
"server assigns each instance an IP address from 172.16.1.2 to 172.16.1.254. "
"All instances use 8.8.4.4 as a DNS resolver."
msgstr ""
#: ../launch-instance-networks-private.rst:131
msgid "Create a router"
msgstr ""
#: ../launch-instance-networks-private.rst:133
msgid ""
"Private project networks connect to public provider networks using a virtual "
"router. Each router contains an interface to at least one private project "
"network and a gateway on a public provider network."
msgstr ""
#: ../launch-instance-networks-private.rst:137
msgid ""
"The public provider network must include the ``router: external`` option to "
"enable project routers to use it for connectivity to external networks such "
"as the Internet. The ``admin`` or other privileged user must include this "
"option during network creation or add it later. In this case, we can add it "
"to the existing ``public`` provider network."
msgstr ""
# #-#-#-#-# launch-instance-networks-private.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# launch-instance-networks-public.pot (Installation Guide 0.1) #-#-#-#-#
#: ../launch-instance-networks-private.rst:143
#: ../launch-instance-networks-private.rst:202
#: ../launch-instance-networks-public.rst:33
msgid ""
"On the controller node, source the ``admin`` credentials to gain access to "
"admin-only CLI commands:"
msgstr ""
#: ../launch-instance-networks-private.rst:150
msgid "Add the ``router: external`` option to the ``public`` provider network:"
msgstr ""
#: ../launch-instance-networks-private.rst:157
msgid ""
"Source the ``demo`` credentials to gain access to user-only CLI commands:"
msgstr ""
#: ../launch-instance-networks-private.rst:163
msgid "Create the router:"
msgstr ""
#: ../launch-instance-networks-private.rst:181
msgid "Add the private network subnet as an interface on the router:"
msgstr ""
#: ../launch-instance-networks-private.rst:188
msgid "Set a gateway on the public network on the router:"
msgstr ""
#: ../launch-instance-networks-private.rst:198
msgid ""
"We recommend that you verify operation and fix any issues before proceeding "
"The following steps use the IP address ranges from the network and subnet "
"creation examples."
msgstr ""
#: ../launch-instance-networks-private.rst:209
msgid ""
"List network namespaces. You should see one ``qrouter`` namespace and two "
"``qdhcp`` namespaces."
msgstr ""
#: ../launch-instance-networks-private.rst:219
msgid ""
"List ports on the router to determine the gateway IP address on the public "
"provider network:"
msgstr ""
#: ../launch-instance-networks-private.rst:236
msgid ""
"Ping this IP address from the controller node or any host on the public "
"physical network:"
msgstr ""
# #-#-#-#-# launch-instance-networks-private.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# launch-instance-networks-public.pot (Installation Guide 0.1) #-#-#-#-#
#: ../launch-instance-networks-private.rst:251
#: ../launch-instance-networks-public.rst:140
msgid ""
"Return to :ref:`Launch an instance - Create virtual networks <launch-"
"instance-networks>`."
msgstr ""
#: ../launch-instance-networks-public.rst:4
msgid "Public provider network"
msgstr ""
#: ../launch-instance-networks-public.rst:6
msgid ""
"Before launching an instance, you must create the necessary virtual network "
"infrastructure. For networking option 1, an instance uses a public provider "
"virtual network that connects to the physical network infrastructure via "
"layer-2 (bridging/switching). This network includes a DHCP server that "
"provides IP addresses to instances."
msgstr ""
#: ../launch-instance-networks-public.rst:12
msgid ""
"The ``admin`` or other privileged user must create this network because it "
"connects directly to the physical network infrastructure."
msgstr ""
#: ../launch-instance-networks-public.rst:23
msgid "**Networking Option 1: Provider networks - Overview**"
msgstr ""
#: ../launch-instance-networks-public.rst:28
msgid "**Networking Option 2: Provider networks - Connectivity**"
msgstr ""
#: ../launch-instance-networks-public.rst:31
msgid "Create the public network"
msgstr ""
#: ../launch-instance-networks-public.rst:65
msgid "The ``--shared`` option allows all projects to use the virtual network."
msgstr ""
#: ../launch-instance-networks-public.rst:67
msgid ""
"The ``--provider:physical_network public`` and ``--provider:network_type "
"flat`` options connect the flat virtual network to the flat (native/"
"untagged) public physical network on the ``eth1`` interface on the host "
"using information from the following files:"
msgstr ""
#: ../launch-instance-networks-public.rst:79
msgid "``linuxbridge_agent.ini``:"
msgstr ""
#: ../launch-instance-networks-public.rst:94
msgid ""
"Replace ``PUBLIC_NETWORK_CIDR`` with the subnet on the public physical "
"network in CIDR notation."
msgstr ""
#: ../launch-instance-networks-public.rst:97
msgid ""
"Replace ``START_IP_ADDRESS`` and ``END_IP_ADDRESS`` with the first and last "
"IP address of the range within the subnet that you want to allocate for "
"instances. This range must not include any existing active IP addresses."
msgstr ""
#: ../launch-instance-networks-public.rst:106
msgid ""
"Replace ``PUBLIC_NETWORK_GATEWAY`` with the gateway IP address on the public "
"physical network, typically the \".1\" IP address."
msgstr ""
#: ../launch-instance-networks-public.rst:111
msgid ""
"The public network uses 203.0.113.0/24 with a gateway on 203.0.113.1. A DHCP "
"server assigns each instance an IP address from 203.0.113.101 to "
"203.0.113.200. All instances use 8.8.4.4 as a DNS resolver."
msgstr ""
#: ../launch-instance-private.rst:4
msgid "Launch an instance on the private network"
msgstr ""
# #-#-#-#-# launch-instance-private.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# launch-instance-public.pot (Installation Guide 0.1) #-#-#-#-#
#: ../launch-instance-private.rst:7 ../launch-instance-public.rst:7
msgid "Determine instance options"
msgstr ""
# #-#-#-#-# launch-instance-private.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# launch-instance-public.pot (Installation Guide 0.1) #-#-#-#-#
#: ../launch-instance-private.rst:9 ../launch-instance-public.rst:9
msgid ""
"To launch an instance, you must at least specify the flavor, image name, "
"network, security group, key, and instance name."
msgstr ""
# #-#-#-#-# launch-instance-private.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# launch-instance-public.pot (Installation Guide 0.1) #-#-#-#-#
#: ../launch-instance-private.rst:19 ../launch-instance-public.rst:19
msgid ""
"A flavor specifies a virtual resource allocation profile which includes "
"processor, memory, and storage."
msgstr ""
# #-#-#-#-# launch-instance-private.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# launch-instance-public.pot (Installation Guide 0.1) #-#-#-#-#
#: ../launch-instance-private.rst:22 ../launch-instance-public.rst:22
msgid "List available flavors:"
msgstr ""
# #-#-#-#-# launch-instance-private.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# launch-instance-public.pot (Installation Guide 0.1) #-#-#-#-#
#: ../launch-instance-private.rst:37 ../launch-instance-public.rst:37
msgid "This instance uses the ``m1.tiny`` flavor."
msgstr ""
# #-#-#-#-# launch-instance-private.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# launch-instance-public.pot (Installation Guide 0.1) #-#-#-#-#
#: ../launch-instance-private.rst:41 ../launch-instance-public.rst:41
msgid "You can also reference a flavor by ID."
msgstr ""
# #-#-#-#-# launch-instance-private.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# launch-instance-public.pot (Installation Guide 0.1) #-#-#-#-#
#: ../launch-instance-private.rst:43 ../launch-instance-public.rst:43
msgid "List available images:"
msgstr ""
# #-#-#-#-# launch-instance-private.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# launch-instance-public.pot (Installation Guide 0.1) #-#-#-#-#
#: ../launch-instance-private.rst:54 ../launch-instance-public.rst:54
msgid "This instance uses the ``cirros`` image."
msgstr ""
# #-#-#-#-# launch-instance-private.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# launch-instance-public.pot (Installation Guide 0.1) #-#-#-#-#
#: ../launch-instance-private.rst:56 ../launch-instance-public.rst:56
msgid "List available networks:"
msgstr ""
#: ../launch-instance-private.rst:68
msgid ""
"This instance uses the ``private`` project network. However, you must "
"reference this network using the ID instead of the name."
msgstr ""
# #-#-#-#-# launch-instance-private.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# launch-instance-public.pot (Installation Guide 0.1) #-#-#-#-#
#: ../launch-instance-private.rst:71 ../launch-instance-public.rst:74
msgid "List available security groups:"
msgstr ""
# #-#-#-#-# launch-instance-private.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# launch-instance-public.pot (Installation Guide 0.1) #-#-#-#-#
#: ../launch-instance-private.rst:82 ../launch-instance-public.rst:85
msgid "This instance uses the ``default`` security group."
msgstr ""
# #-#-#-#-# launch-instance-private.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# launch-instance-public.pot (Installation Guide 0.1) #-#-#-#-#
#: ../launch-instance-private.rst:84 ../launch-instance-public.rst:90
msgid "Launch the instance:"
msgstr ""
#: ../launch-instance-private.rst:86
msgid ""
"Replace ``PRIVATE_NET_ID`` with the ID of the ``private`` project network."
msgstr ""
# #-#-#-#-# launch-instance-private.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# launch-instance-public.pot (Installation Guide 0.1) #-#-#-#-#
#: ../launch-instance-private.rst:123 ../launch-instance-public.rst:135
msgid "Check the status of your instance:"
msgstr ""
# #-#-#-#-# launch-instance-private.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# launch-instance-public.pot (Installation Guide 0.1) #-#-#-#-#
#: ../launch-instance-private.rst:135 ../launch-instance-public.rst:146
msgid ""
"The status changes from ``BUILD`` to ``ACTIVE`` when the build process "
"successfully completes."
msgstr ""
#: ../launch-instance-private.rst:139
msgid "Access the instance using a virtual console"
msgstr ""
# #-#-#-#-# launch-instance-private.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# launch-instance-public.pot (Installation Guide 0.1) #-#-#-#-#
#: ../launch-instance-private.rst:141 ../launch-instance-public.rst:152
msgid ""
"Obtain a :term:`Virtual Network Computing (VNC)` session URL for your "
"instance and access it from a web browser:"
msgstr ""
# #-#-#-#-# launch-instance-private.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# launch-instance-public.pot (Installation Guide 0.1) #-#-#-#-#
#: ../launch-instance-private.rst:155 ../launch-instance-public.rst:166
msgid ""
"If your web browser runs on a host that cannot resolve the ``controller`` "
"host name, you can replace ``controller`` with the IP address of the "
"management interface on your controller node."
msgstr ""
# #-#-#-#-# launch-instance-private.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# launch-instance-public.pot (Installation Guide 0.1) #-#-#-#-#
#: ../launch-instance-private.rst:159 ../launch-instance-public.rst:170
msgid ""
"The CirrOS image includes conventional user name/password authentication and "
"provides these credentials at the login prompt. After logging into CirrOS, "
"we recommend that you verify network connectivity using ``ping``."
msgstr ""
#: ../launch-instance-private.rst:164
msgid "Verify access to the ``private`` project network gateway:"
msgstr ""
# #-#-#-#-# launch-instance-private.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# launch-instance-public.pot (Installation Guide 0.1) #-#-#-#-#
#: ../launch-instance-private.rst:179 ../launch-instance-public.rst:190
msgid "Verify access to the internet:"
msgstr ""
# #-#-#-#-# launch-instance-private.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# launch-instance-public.pot (Installation Guide 0.1) #-#-#-#-#
#: ../launch-instance-private.rst:195 ../launch-instance-public.rst:206
msgid "Access the instance remotely"
msgstr ""
#: ../launch-instance-private.rst:197
msgid ""
"Create a :term:`floating IP address` on the ``public`` provider network:"
msgstr ""
#: ../launch-instance-private.rst:216
msgid "Associate the floating IP address with the instance:"
msgstr ""
#: ../launch-instance-private.rst:226
msgid "Check the status of your floating IP address:"
msgstr ""
#: ../launch-instance-private.rst:238
msgid ""
"Verify connectivity to the instance via floating IP address from the "
"controller node or any host on the public physical network:"
msgstr ""
# #-#-#-#-# launch-instance-private.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# launch-instance-public.pot (Installation Guide 0.1) #-#-#-#-#
#: ../launch-instance-private.rst:254 ../launch-instance-public.rst:224
msgid ""
"Access your instance using SSH from the controller node or any host on the "
"public physical network:"
msgstr ""
# #-#-#-#-# launch-instance-private.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# launch-instance-public.pot (Installation Guide 0.1) #-#-#-#-#
#: ../launch-instance-private.rst:268 ../launch-instance-public.rst:238
msgid ""
"If your host does not contain the public/private key pair created in an "
"earlier step, SSH prompts for the default password associated with the "
"``cirros`` user, ``cubswin:)``."
msgstr ""
# #-#-#-#-# launch-instance-private.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# launch-instance-public.pot (Installation Guide 0.1) #-#-#-#-#
#: ../launch-instance-private.rst:272 ../launch-instance-public.rst:242
msgid ""
"If your instance does not launch or seem to work as you expect, see the "
"`OpenStack Operations Guide <http://docs.openstack.org/ops>`__ for more "
"information or use one of the :doc:`many other options <common/app_support>` "
"to seek assistance. We want your first installation to work!"
msgstr ""
# #-#-#-#-# launch-instance-private.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# launch-instance-public.pot (Installation Guide 0.1) #-#-#-#-#
#: ../launch-instance-private.rst:277 ../launch-instance-public.rst:247
msgid "Return to :ref:`Launch an instance <launch-instance-complete>`."
msgstr ""
#: ../launch-instance-public.rst:4
msgid "Launch an instance on the public network"
msgstr ""
#: ../launch-instance-public.rst:67
msgid ""
"This instance uses the ``public`` provider network. However, you must "
"reference this network using the ID instead of the name."
msgstr ""
#: ../launch-instance-public.rst:72
msgid ""
"If you chose option 2, the output should also contain the private network."
msgstr ""
#: ../launch-instance-public.rst:88
msgid "Launch the instance"
msgstr ""
#: ../launch-instance-public.rst:92
msgid ""
"Replace ``PUBLIC_NET_ID`` with the ID of the ``public`` provider network."
msgstr ""
#: ../launch-instance-public.rst:96
msgid ""
"If you chose option 1 and your environment contains only one network, you "
"can omit the ``--nic`` option because OpenStack automatically chooses the "
"only network available."
msgstr ""
#: ../launch-instance-public.rst:150
msgid "Access the instance using the virtual console"
msgstr ""
#: ../launch-instance-public.rst:175
msgid "Verify access to the public provider network gateway:"
msgstr ""
#: ../launch-instance-public.rst:208
msgid ""
"Verify connectivity to the instance from the controller node or any host on "
"the public physical network:"
msgstr ""
#: ../launch-instance.rst:5 ../launch-instance.rst:107
msgid "Launch an instance"
msgstr ""
#: ../launch-instance.rst:7
msgid ""
"This section creates the necessary virtual networks to support launching one "
"more instances. Networking option 1 includes one public virtual network and "
"one instance that uses it. Networking option 2 includes one public virtual "
"network, one private virtual network, and one instance that uses each "
"network. The instructions in this section use command-line interface (CLI) "
"tools on the controller node. For more information on the CLI tools, see the "
"`OpenStack User Guide <http://docs.openstack.org/user-guide/"
"cli_launch_instances.html>`__. To use the dashboard, see the `OpenStack User "
"Guide <http://docs.openstack.org/user-guide/dashboard.html>`__."
msgstr ""
#: ../launch-instance.rst:22
msgid "Create virtual networks"
msgstr ""
#: ../launch-instance.rst:24
msgid ""
"Create virtual networks for the networking option that you chose in :ref:"
"`networking`. If you chose option 1, create only the public virtual network. "
"If you chose option 2, create the public and private virtual networks."
msgstr ""
#: ../launch-instance.rst:35
msgid ""
"After creating the appropriate networks for your environment, you can "
"continue preparing the environment to launch an instance."
msgstr ""
#: ../launch-instance.rst:39
msgid "Generate a key pair"
msgstr ""
#: ../launch-instance.rst:41
msgid ""
"Most cloud images support :term:`public key authentication` rather than "
"conventional password authentication. Before launching an instance, you must "
"add a public key to the Compute service."
msgstr ""
#: ../launch-instance.rst:45
msgid "Source the ``demo`` tenant credentials:"
msgstr ""
#: ../launch-instance.rst:51
msgid "Generate and add a key pair:"
msgstr ""
#: ../launch-instance.rst:60
msgid ""
"Alternatively, you can skip the ``ssh-keygen`` command and use an existing "
"public key."
msgstr ""
#: ../launch-instance.rst:63
msgid "Verify addition of the key pair:"
msgstr ""
#: ../launch-instance.rst:75
msgid "Add security group rules"
msgstr ""
#: ../launch-instance.rst:77
msgid ""
"By default, the ``default`` security group applies to all instances and "
"includes firewall rules that deny remote access to instances. For Linux "
"images such as CirrOS, we recommend allowing at least ICMP (ping) and secure "
"shell (SSH)."
msgstr ""
#: ../launch-instance.rst:82
msgid "Add rules to the ``default`` security group:"
msgstr ""
#: ../launch-instance.rst:84
msgid "Permit :term:`ICMP` (ping):"
msgstr ""
#: ../launch-instance.rst:95
msgid "Permit secure shell (SSH) access:"
msgstr ""
#: ../launch-instance.rst:109
msgid ""
"If you chose networking option 1, you can only launch an instance on the "
"public network. If you chose networking option 2, you can launch an instance "
"on the public network and the private network."
msgstr ""
#: ../launch-instance.rst:124
msgid ""
"If your environment includes the Block Storage service, you can create a "
"volume and attach it to an instance."
msgstr ""
#: ../launch-instance.rst:135
msgid ""
"If your environment includes the Orchestration service, you can create a "
"stack that launches an instance."
msgstr ""
# #-#-#-#-# neutron-compute-install-option1.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# neutron-controller-install-option1.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# neutron-verify-option1.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# overview.pot (Installation Guide 0.1) #-#-#-#-#
#: ../neutron-compute-install-option1.rst:2
#: ../neutron-controller-install-option1.rst:2 ../neutron-verify-option1.rst:2
#: ../overview.rst:197
msgid "Networking Option 1: Provider networks"
msgstr ""
# #-#-#-#-# neutron-compute-install-option1.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# neutron-compute-install-option2.pot (Installation Guide 0.1) #-#-#-#-#
#: ../neutron-compute-install-option1.rst:4
#: ../neutron-compute-install-option2.rst:4
msgid "Configure the Networking components on a *compute* node."
msgstr ""
# #-#-#-#-# neutron-compute-install-option1.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# neutron-compute-install-option2.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# neutron-controller-install-option1.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# neutron-controller-install-option2.pot (Installation Guide 0.1) #-#-#-#-#
#: ../neutron-compute-install-option1.rst:7
#: ../neutron-compute-install-option2.rst:7
#: ../neutron-controller-install-option1.rst:297
#: ../neutron-controller-install-option2.rst:270
msgid "Configure the Linux bridge agent"
msgstr ""
# #-#-#-#-# neutron-compute-install-option1.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# neutron-compute-install-option2.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# neutron-controller-install-option1.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# neutron-controller-install-option2.pot (Installation Guide 0.1) #-#-#-#-#
#: ../neutron-compute-install-option1.rst:9
#: ../neutron-compute-install-option2.rst:9
#: ../neutron-controller-install-option1.rst:299
#: ../neutron-controller-install-option2.rst:272
msgid ""
"The Linux bridge agent builds layer-2 (bridging and switching) virtual "
"networking infrastructure for instances including VXLAN tunnels for private "
"networks and handles security groups."
msgstr ""
# #-#-#-#-# neutron-compute-install-option1.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# neutron-compute-install-option2.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# neutron-controller-install-option1.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# neutron-controller-install-option2.pot (Installation Guide 0.1) #-#-#-#-#
#: ../neutron-compute-install-option1.rst:13
#: ../neutron-compute-install-option2.rst:13
#: ../neutron-controller-install-option1.rst:303
#: ../neutron-controller-install-option2.rst:276
msgid ""
"Edit the ``/etc/neutron/plugins/ml2/linuxbridge_agent.ini`` file and "
"complete the following actions:"
msgstr ""
# #-#-#-#-# neutron-compute-install-option1.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# neutron-compute-install-option2.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# neutron-controller-install-option1.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# neutron-controller-install-option2.pot (Installation Guide 0.1) #-#-#-#-#
#: ../neutron-compute-install-option1.rst:16
#: ../neutron-compute-install-option2.rst:16
#: ../neutron-controller-install-option1.rst:306
#: ../neutron-controller-install-option2.rst:279
msgid ""
"In the ``[linux_bridge]`` section, map the public virtual network to the "
"public physical network interface:"
msgstr ""
# #-#-#-#-# neutron-compute-install-option1.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# neutron-compute-install-option2.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# neutron-controller-install-option1.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# neutron-controller-install-option2.pot (Installation Guide 0.1) #-#-#-#-#
#: ../neutron-compute-install-option1.rst:24
#: ../neutron-compute-install-option2.rst:24
#: ../neutron-controller-install-option1.rst:314
#: ../neutron-controller-install-option2.rst:287
msgid ""
"Replace ``PUBLIC_INTERFACE_NAME`` with the name of the underlying physical "
"public network interface."
msgstr ""
# #-#-#-#-# neutron-compute-install-option1.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# neutron-controller-install-option1.pot (Installation Guide 0.1) #-#-#-#-#
#: ../neutron-compute-install-option1.rst:27
#: ../neutron-controller-install-option1.rst:317
msgid "In the ``[vxlan]`` section, disable VXLAN overlay networks:"
msgstr ""
# #-#-#-#-# neutron-compute-install-option1.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# neutron-compute-install-option2.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# neutron-controller-install-option1.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# neutron-controller-install-option2.pot (Installation Guide 0.1) #-#-#-#-#
#: ../neutron-compute-install-option1.rst:34
#: ../neutron-compute-install-option2.rst:42
#: ../neutron-controller-install-option1.rst:324
#: ../neutron-controller-install-option2.rst:305
msgid "In the ``[agent]`` section, enable ARP spoofing protection:"
msgstr ""
# #-#-#-#-# neutron-compute-install-option1.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# neutron-compute-install-option2.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# neutron-controller-install-option1.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# neutron-controller-install-option2.pot (Installation Guide 0.1) #-#-#-#-#
#: ../neutron-compute-install-option1.rst:42
#: ../neutron-compute-install-option2.rst:50
#: ../neutron-controller-install-option1.rst:332
#: ../neutron-controller-install-option2.rst:313
msgid ""
"In the ``[securitygroup]`` section, enable security groups and configure the "
"Linux bridge :term:`iptables` firewall driver:"
msgstr ""
# #-#-#-#-# neutron-compute-install-option1.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# neutron-compute-install-option2.pot (Installation Guide 0.1) #-#-#-#-#
#: ../neutron-compute-install-option1.rst:52
#: ../neutron-compute-install-option2.rst:60
msgid ""
"Return to :ref:`Networking compute node configuration <neutron-compute-"
"compute>`."
msgstr ""
# #-#-#-#-# neutron-compute-install-option2.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# neutron-controller-install-option2.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# neutron-verify-option2.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# overview.pot (Installation Guide 0.1) #-#-#-#-#
#: ../neutron-compute-install-option2.rst:2
#: ../neutron-controller-install-option2.rst:2 ../neutron-verify-option2.rst:2
#: ../overview.rst:221
msgid "Networking Option 2: Self-service networks"
msgstr ""
# #-#-#-#-# neutron-compute-install-option2.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# neutron-controller-install-option2.pot (Installation Guide 0.1) #-#-#-#-#
#: ../neutron-compute-install-option2.rst:27
#: ../neutron-controller-install-option2.rst:290
msgid ""
"In the ``[vxlan]`` section, enable VXLAN overlay networks, configure the IP "
"address of the physical network interface that handles overlay networks, and "
"enable layer-2 population:"
msgstr ""
# #-#-#-#-# neutron-compute-install-option2.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# neutron-controller-install-option2.pot (Installation Guide 0.1) #-#-#-#-#
#: ../neutron-compute-install-option2.rst:38
#: ../neutron-controller-install-option2.rst:301
msgid ""
"Replace ``OVERLAY_INTERFACE_IP_ADDRESS`` with the IP address of the "
"underlying physical network interface that handles overlay networks. The "
"example architecture uses the management interface."
msgstr ""
#: ../neutron-compute-install.rst:2
msgid "Install and configure compute node"
msgstr ""
#: ../neutron-compute-install.rst:4
msgid ""
"The compute node handles connectivity and :term:`security groups <security "
"group>` for instances."
msgstr ""
# #-#-#-#-# neutron-compute-install.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# neutron-controller-install-option1.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# neutron-controller-install-option2.pot (Installation Guide 0.1) #-#-#-#-#
#: ../neutron-compute-install.rst:10
#: ../neutron-controller-install-option1.rst:7
#: ../neutron-controller-install-option2.rst:7
msgid "Install the components"
msgstr ""
# #-#-#-#-# neutron-compute-install.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# neutron-controller-install-option2.pot (Installation Guide 0.1) #-#-#-#-#
#: ../neutron-compute-install.rst:33
#: ../neutron-controller-install-option2.rst:36
msgid "Install and configure the Networking components"
msgstr ""
#: ../neutron-compute-install.rst:39
msgid ""
"Respond to prompts for ``database management``, ``Identity service "
"credentials``, ``service endpoint``, and ``message queue credentials``."
msgstr ""
# #-#-#-#-# neutron-compute-install.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# neutron-controller-install-option1.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# neutron-controller-install-option2.pot (Installation Guide 0.1) #-#-#-#-#
#: ../neutron-compute-install.rst:42
#: ../neutron-controller-install-option1.rst:30
#: ../neutron-controller-install-option2.rst:51
msgid "Select the ML2 plug-in:"
msgstr ""
# #-#-#-#-# neutron-compute-install.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# neutron-controller-install-option2.pot (Installation Guide 0.1) #-#-#-#-#
#: ../neutron-compute-install.rst:49
#: ../neutron-controller-install-option2.rst:57
msgid ""
"Selecting the ML2 plug-in also populates the ``service_plugins`` and "
"``allow_overlapping_ips`` options in the ``/etc/neutron/neutron.conf`` file "
"with the appropriate values."
msgstr ""
#: ../neutron-compute-install.rst:56
msgid "Configure the common component"
msgstr ""
#: ../neutron-compute-install.rst:58
msgid ""
"The Networking common component configuration includes the authentication "
"mechanism, message queue, and plug-in."
msgstr ""
# #-#-#-#-# neutron-compute-install.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# neutron-controller-install-option1.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# neutron-controller-install-option2.pot (Installation Guide 0.1) #-#-#-#-#
#: ../neutron-compute-install.rst:63
#: ../neutron-controller-install-option1.rst:61
#: ../neutron-controller-install-option1.rst:108
#: ../neutron-controller-install-option2.rst:66
msgid ""
"Edit the ``/etc/neutron/neutron.conf`` file and complete the following "
"actions:"
msgstr ""
#: ../neutron-compute-install.rst:66
msgid ""
"In the ``[database]`` section, comment out any ``connection`` options "
"because compute nodes do not directly access the database."
msgstr ""
# #-#-#-#-# neutron-compute-install.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# neutron-controller-install-option1.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# neutron-controller-install-option2.pot (Installation Guide 0.1) #-#-#-#-#
#: ../neutron-compute-install.rst:69
#: ../neutron-controller-install-option1.rst:142
#: ../neutron-controller-install-option2.rst:101
msgid ""
"In the ``[DEFAULT]`` and ``[oslo_messaging_rabbit]`` sections, configure "
"RabbitMQ message queue access:"
msgstr ""
# #-#-#-#-# neutron-compute-install.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# neutron-controller-install-option1.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# neutron-controller-install-option2.pot (Installation Guide 0.1) #-#-#-#-#
#: ../neutron-compute-install.rst:84
#: ../neutron-controller-install-option1.rst:157
#: ../neutron-controller-install-option2.rst:116
msgid ""
"Replace ``RABBIT_PASS`` with the password you chose for the ``openstack`` "
"account in RabbitMQ."
msgstr ""
# #-#-#-#-# neutron-compute-install.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# neutron-controller-install-option1.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# neutron-controller-install-option2.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# neutron-controller-install.pot (Installation Guide 0.1) #-#-#-#-#
#: ../neutron-compute-install.rst:107 ../neutron-compute-install.rst:175
#: ../neutron-controller-install-option1.rst:180
#: ../neutron-controller-install-option2.rst:139
#: ../neutron-controller-install.rst:193 ../neutron-controller-install.rst:249
msgid ""
"Replace ``NEUTRON_PASS`` with the password you chose for the ``neutron`` "
"user in the Identity service."
msgstr ""
# #-#-#-#-# neutron-compute-install.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# neutron-controller-install.pot (Installation Guide 0.1) #-#-#-#-#
#: ../neutron-compute-install.rst:135 ../neutron-controller-install.rst:144
msgid "Configure networking options"
msgstr ""
#: ../neutron-compute-install.rst:137
msgid ""
"Choose the same networking option that you chose for the controller node to "
"configure services specific to it."
msgstr ""
# #-#-#-#-# neutron-compute-install.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# neutron-controller-install.pot (Installation Guide 0.1) #-#-#-#-#
#: ../neutron-compute-install.rst:142 ../neutron-controller-install.rst:151
msgid ""
"Option 2 augments option 1 with the layer-3 (routing) service and enables "
"self-service (private) networks. If you want to use public (provider) and "
"private (self-service) networks, choose option 2."
msgstr ""
# #-#-#-#-# neutron-compute-install.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# neutron-controller-install.pot (Installation Guide 0.1) #-#-#-#-#
#: ../neutron-compute-install.rst:155 ../neutron-controller-install.rst:225
msgid "Configure Compute to use Networking"
msgstr ""
# #-#-#-#-# neutron-compute-install.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# nova-compute-install.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# nova-controller-install.pot (Installation Guide 0.1) #-#-#-#-#
#: ../neutron-compute-install.rst:157 ../nova-compute-install.rst:62
#: ../nova-controller-install.rst:199
msgid ""
"Edit the ``/etc/nova/nova.conf`` file and complete the following actions:"
msgstr ""
#: ../neutron-compute-install.rst:159
msgid "In the ``[neutron]`` section, configure access parameters:"
msgstr ""
# #-#-#-#-# neutron-compute-install.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# neutron-controller-install.pot (Installation Guide 0.1) #-#-#-#-#
#: ../neutron-compute-install.rst:183 ../neutron-controller-install.rst:260
msgid ""
"The Networking service initialization scripts expect a symbolic link ``/etc/"
"neutron/plugin.ini`` pointing to the ML2 plug-in configuration file, ``/etc/"
"neutron/plugins/ml2/ml2_conf.ini``. If this symbolic link does not exist, "
"create it using the following command:"
msgstr ""
#: ../neutron-compute-install.rst:198
msgid ""
"Start the Linux bridge agent and configure it to start when the system boots:"
msgstr ""
# #-#-#-#-# neutron-compute-install.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# neutron-controller-install.pot (Installation Guide 0.1) #-#-#-#-#
#: ../neutron-compute-install.rst:208 ../neutron-controller-install.rst:310
msgid ""
"The Networking service initialization scripts expect the variable "
"``NEUTRON_PLUGIN_CONF`` in the ``/etc/sysconfig/neutron`` file to reference "
"the ML2 plug-in configuration file. Edit the ``/etc/sysconfig/neutron`` file "
"and add the following:"
msgstr ""
#: ../neutron-compute-install.rst:223
msgid ""
"Start the Linux Bridge agent and configure it to start when the system boots:"
msgstr ""
#: ../neutron-compute-install.rst:239
msgid "Restart the Linux bridge agent:"
msgstr ""
#: ../neutron-concepts.rst:2
msgid "Networking (neutron) concepts"
msgstr ""
#: ../neutron-concepts.rst:4
msgid ""
"OpenStack Networking (neutron) manages all networking facets for the Virtual "
"Networking Infrastructure (VNI) and the access layer aspects of the Physical "
"Networking Infrastructure (PNI) in your OpenStack environment. OpenStack "
"Networking enables tenants to create advanced virtual network topologies "
"which may include services such as a :term:`firewall`, a :term:`load "
"balancer`, and a :term:`virtual private network (VPN)`."
msgstr ""
#: ../neutron-concepts.rst:12
msgid ""
"Networking provides networks, subnets, and routers as object abstractions. "
"Each abstraction has functionality that mimics its physical counterpart: "
"networks contain subnets, and routers route traffic between different "
"subnets and networks."
msgstr ""
#: ../neutron-concepts.rst:17
msgid ""
"Any given Networking set up has at least one external network. Unlike the "
"other networks, the external network is not merely a virtually defined "
"network. Instead, it represents a view into a slice of the physical, "
"external network accessible outside the OpenStack installation. IP addresses "
"on the external network are accessible by anybody physically on the outside "
"network."
msgstr ""
#: ../neutron-concepts.rst:24
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 ""
#: ../neutron-concepts.rst:30
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 an "
"external network and one or more interfaces connected to internal networks. "
"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 ""
#: ../neutron-concepts.rst:37
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 ""
#: ../neutron-concepts.rst:43
msgid ""
"Networking also supports *security groups*. Security groups enable "
"administrators to define firewall rules in groups. A VM can belong to one or "
"more security groups, and Networking applies the rules in those security "
"groups to block or unblock ports, port ranges, or traffic types for that VM."
msgstr ""
#: ../neutron-concepts.rst:49
msgid ""
"Each plug-in that Networking uses has its own concepts. While not vital to "
"operating the VNI and OpenStack environment, understanding these concepts "
"can help you set up Networking. All Networking installations use a core plug-"
"in and a security group plug-in (or just the No-Op security group plug-in). "
"Additionally, Firewall-as-a-Service (FWaaS) and Load-Balancer-as-a-Service "
"(LBaaS) plug-ins are available."
msgstr ""
# #-#-#-#-# neutron-controller-install-option1.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# neutron-controller-install-option2.pot (Installation Guide 0.1) #-#-#-#-#
#: ../neutron-controller-install-option1.rst:4
#: ../neutron-controller-install-option2.rst:4
msgid ""
"Install and configure the Networking components on the *controller* node."
msgstr ""
# #-#-#-#-# neutron-controller-install-option1.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# neutron-controller-install-option2.pot (Installation Guide 0.1) #-#-#-#-#
#: ../neutron-controller-install-option1.rst:24
#: ../neutron-controller-install-option2.rst:45
msgid ""
"Respond to prompts for `database management <#debconf-dbconfig-common>`__, "
"`Identity service credentials <#debconf-keystone_authtoken>`__, `service "
"endpoint registration <#debconf-api-endpoints>`__, and `message queue "
"credentials <#debconf-rabbitmq>`__."
msgstr ""
#: ../neutron-controller-install-option1.rst:36
msgid ""
"Selecting the ML2 plug-in also populates the ``core_plugin`` option in the "
"``/etc/neutron/neutron.conf`` file with the appropriate values (in this "
"case, it is set to the value ``ml2``)."
msgstr ""
# #-#-#-#-# neutron-controller-install-option1.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# neutron-controller-install-option2.pot (Installation Guide 0.1) #-#-#-#-#
#: ../neutron-controller-install-option1.rst:59
#: ../neutron-controller-install-option1.rst:100
#: ../neutron-controller-install-option2.rst:64
msgid "Configure the server component"
msgstr ""
#: ../neutron-controller-install-option1.rst:64
msgid "In the ``[DEFAULT]`` section, disable additional plug-ins:"
msgstr ""
# #-#-#-#-# neutron-controller-install-option1.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# neutron-controller-install-option2.pot (Installation Guide 0.1) #-#-#-#-#
#: ../neutron-controller-install-option1.rst:72
#: ../neutron-controller-install-option1.rst:188
#: ../neutron-controller-install-option2.rst:147
msgid ""
"In the ``[DEFAULT]`` and ``[nova]`` sections, configure Networking to notify "
"Compute of network topology changes:"
msgstr ""
# #-#-#-#-# neutron-controller-install-option1.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# neutron-controller-install-option2.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# nova-compute-install.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# nova-controller-install.pot (Installation Guide 0.1) #-#-#-#-#
#: ../neutron-controller-install-option1.rst:94
#: ../neutron-controller-install-option1.rst:210
#: ../neutron-controller-install-option2.rst:169
#: ../nova-compute-install.rst:105 ../nova-controller-install.rst:263
msgid ""
"Replace ``NOVA_PASS`` with the password you chose for the ``nova`` user in "
"the Identity service."
msgstr ""
#: ../neutron-controller-install-option1.rst:102
msgid ""
"The Networking server component configuration includes the database, "
"authentication mechanism, message queue, topology change notifications, and "
"plug-in."
msgstr ""
# #-#-#-#-# neutron-controller-install-option1.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# neutron-controller-install-option2.pot (Installation Guide 0.1) #-#-#-#-#
#: ../neutron-controller-install-option1.rst:129
#: ../neutron-controller-install-option2.rst:87
msgid ""
"Replace ``NEUTRON_DBPASS`` with the password you chose for the database."
msgstr ""
#: ../neutron-controller-install-option1.rst:132
msgid ""
"In the ``[DEFAULT]`` section, enable the Modular Layer 2 (ML2) plug-in and "
"disable additional plug-ins:"
msgstr ""
# #-#-#-#-# neutron-controller-install-option1.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# neutron-controller-install-option2.pot (Installation Guide 0.1) #-#-#-#-#
#: ../neutron-controller-install-option1.rst:233
#: ../neutron-controller-install-option2.rst:192
msgid "Configure the Modular Layer 2 (ML2) plug-in"
msgstr ""
# #-#-#-#-# neutron-controller-install-option1.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# neutron-controller-install-option2.pot (Installation Guide 0.1) #-#-#-#-#
#: ../neutron-controller-install-option1.rst:235
#: ../neutron-controller-install-option2.rst:194
msgid ""
"The ML2 plug-in uses the Linux bridge mechanism to build layer-2 (bridging "
"and switching) virtual networking infrastructure for instances."
msgstr ""
# #-#-#-#-# neutron-controller-install-option1.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# neutron-controller-install-option2.pot (Installation Guide 0.1) #-#-#-#-#
#: ../neutron-controller-install-option1.rst:238
#: ../neutron-controller-install-option2.rst:197
msgid ""
"Edit the ``/etc/neutron/plugins/ml2/ml2_conf.ini`` file and complete the "
"following actions:"
msgstr ""
#: ../neutron-controller-install-option1.rst:241
msgid "In the ``[ml2]`` section, enable flat and VLAN networks:"
msgstr ""
#: ../neutron-controller-install-option1.rst:249
msgid "In the ``[ml2]`` section, disable project (private) networks:"
msgstr ""
#: ../neutron-controller-install-option1.rst:257
msgid "In the ``[ml2]`` section, enable the Linux bridge mechanism:"
msgstr ""
# #-#-#-#-# neutron-controller-install-option1.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# neutron-controller-install-option2.pot (Installation Guide 0.1) #-#-#-#-#
#: ../neutron-controller-install-option1.rst:267
#: ../neutron-controller-install-option2.rst:227
msgid ""
"After you configure the ML2 plug-in, removing values in the ``type_drivers`` "
"option can lead to database inconsistency."
msgstr ""
# #-#-#-#-# neutron-controller-install-option1.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# neutron-controller-install-option2.pot (Installation Guide 0.1) #-#-#-#-#
#: ../neutron-controller-install-option1.rst:270
#: ../neutron-controller-install-option2.rst:234
msgid "In the ``[ml2]`` section, enable the port security extension driver:"
msgstr ""
# #-#-#-#-# neutron-controller-install-option1.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# neutron-controller-install-option2.pot (Installation Guide 0.1) #-#-#-#-#
#: ../neutron-controller-install-option1.rst:278
#: ../neutron-controller-install-option2.rst:242
msgid ""
"In the ``[ml2_type_flat]`` section, configure the public flat provider "
"network:"
msgstr ""
# #-#-#-#-# neutron-controller-install-option1.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# neutron-controller-install-option2.pot (Installation Guide 0.1) #-#-#-#-#
#: ../neutron-controller-install-option1.rst:287
#: ../neutron-controller-install-option2.rst:260
msgid ""
"In the ``[securitygroup]`` section, enable :term:`ipset` to increase "
"efficiency of security group rules:"
msgstr ""
# #-#-#-#-# neutron-controller-install-option1.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# neutron-controller-install-option2.pot (Installation Guide 0.1) #-#-#-#-#
#: ../neutron-controller-install-option1.rst:343
#: ../neutron-controller-install-option2.rst:357
msgid "Configure the DHCP agent"
msgstr ""
# #-#-#-#-# neutron-controller-install-option1.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# neutron-controller-install-option2.pot (Installation Guide 0.1) #-#-#-#-#
#: ../neutron-controller-install-option1.rst:345
#: ../neutron-controller-install-option2.rst:359
msgid "The :term:`DHCP agent` provides DHCP services for virtual networks."
msgstr ""
# #-#-#-#-# neutron-controller-install-option1.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# neutron-controller-install-option2.pot (Installation Guide 0.1) #-#-#-#-#
#: ../neutron-controller-install-option1.rst:347
#: ../neutron-controller-install-option2.rst:361
msgid ""
"Edit the ``/etc/neutron/dhcp_agent.ini`` file and complete the following "
"actions:"
msgstr ""
# #-#-#-#-# neutron-controller-install-option1.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# neutron-controller-install-option2.pot (Installation Guide 0.1) #-#-#-#-#
#: ../neutron-controller-install-option1.rst:350
#: ../neutron-controller-install-option2.rst:364
msgid ""
"In the ``[DEFAULT]`` section, configure the Linux bridge interface driver, "
"Dnsmasq DHCP driver, and enable isolated metadata so instances on public "
"networks can access metadata over the network:"
msgstr ""
# #-#-#-#-# neutron-controller-install-option1.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# neutron-controller-install-option2.pot (Installation Guide 0.1) #-#-#-#-#
#: ../neutron-controller-install-option1.rst:371
#: ../neutron-controller-install-option2.rst:429
msgid ""
"Return to :ref:`Networking controller node configuration <neutron-controller-"
"metadata-agent>`."
msgstr ""
#: ../neutron-controller-install-option2.rst:43
msgid "For networking option 2, also install the ``neutron-l3-agent`` package."
msgstr ""
#: ../neutron-controller-install-option2.rst:90
msgid ""
"In the ``[DEFAULT]`` section, enable the Modular Layer 2 (ML2) plug-in, "
"router service, and overlapping IP addresses:"
msgstr ""
#: ../neutron-controller-install-option2.rst:200
msgid "In the ``[ml2]`` section, enable flat, VLAN, and VXLAN networks:"
msgstr ""
#: ../neutron-controller-install-option2.rst:208
msgid "In the ``[ml2]`` section, enable VXLAN project (private) networks:"
msgstr ""
#: ../neutron-controller-install-option2.rst:216
msgid ""
"In the ``[ml2]`` section, enable the Linux bridge and layer-2 population "
"mechanisms:"
msgstr ""
#: ../neutron-controller-install-option2.rst:232
msgid "The Linux bridge agent only supports VXLAN overlay networks."
msgstr ""
#: ../neutron-controller-install-option2.rst:251
msgid ""
"In the ``[ml2_type_vxlan]`` section, configure the VXLAN network identifier "
"range for private networks:"
msgstr ""
#: ../neutron-controller-install-option2.rst:324
msgid "Configure the layer-3 agent"
msgstr ""
#: ../neutron-controller-install-option2.rst:326
msgid ""
"The :term:`Layer-3 (L3) agent` provides routing and NAT services for virtual "
"networks."
msgstr ""
#: ../neutron-controller-install-option2.rst:329
msgid ""
"Edit the ``/etc/neutron/l3_agent.ini`` file and complete the following "
"actions:"
msgstr ""
#: ../neutron-controller-install-option2.rst:332
msgid ""
"In the ``[DEFAULT]`` section, configure the Linux bridge interface driver "
"and external network bridge:"
msgstr ""
#: ../neutron-controller-install-option2.rst:344
msgid ""
"The ``external_network_bridge`` option intentionally lacks a value to enable "
"multiple external networks on a single agent."
msgstr ""
#: ../neutron-controller-install-option2.rst:385
msgid ""
"Overlay networks such as VXLAN include additional packet headers that "
"increase overhead and decrease space available for the payload or user data. "
"Without knowledge of the virtual network infrastructure, instances attempt "
"to send packets using the default Ethernet :term:`maximum transmission unit "
"(MTU)` of 1500 bytes. :term:`Internet protocol (IP)` networks contain the :"
"term:`path MTU discovery (PMTUD)` mechanism to detect end-to-end MTU and "
"adjust packet size accordingly. However, some operating systems and networks "
"block or otherwise lack support for PMTUD causing performance degradation or "
"connectivity failure."
msgstr ""
#: ../neutron-controller-install-option2.rst:395
msgid ""
"Ideally, you can prevent these problems by enabling :term:`jumbo frames "
"<jumbo frame>` on the physical network that contains your tenant virtual "
"networks. Jumbo frames support MTUs up to approximately 9000 bytes which "
"negates the impact of VXLAN overhead on virtual networks. However, many "
"network devices lack support for jumbo frames and OpenStack administrators "
"often lack control over network infrastructure. Given the latter "
"complications, you can also prevent MTU problems by reducing the instance "
"MTU to account for VXLAN overhead. Determining the proper MTU value often "
"takes experimentation, but 1450 bytes works in most environments. You can "
"configure the DHCP server that assigns IP addresses to your instances to "
"also adjust the MTU."
msgstr ""
#: ../neutron-controller-install-option2.rst:409
msgid ""
"Some cloud images ignore the DHCP MTU option in which case you should "
"configure it using metadata, a script, or other suitable method."
msgstr ""
#: ../neutron-controller-install-option2.rst:413
msgid ""
"In the ``[DEFAULT]`` section, enable the :term:`dnsmasq` configuration file:"
msgstr ""
#: ../neutron-controller-install-option2.rst:422
msgid ""
"Create and edit the ``/etc/neutron/dnsmasq-neutron.conf`` file to enable the "
"DHCP MTU option (26) and configure it to 1450 bytes:"
msgstr ""
#: ../neutron-controller-install.rst:9
msgid ""
"Before you configure the OpenStack Networking (neutron) service, you must "
"create a database, service credentials, and API endpoints."
msgstr ""
#: ../neutron-controller-install.rst:21
msgid "Create the ``neutron`` database:"
msgstr ""
#: ../neutron-controller-install.rst:27
msgid ""
"Grant proper access to the ``neutron`` database, replacing "
"``NEUTRON_DBPASS`` with a suitable password:"
msgstr ""
#: ../neutron-controller-install.rst:48
msgid "Create the ``neutron`` user:"
msgstr ""
#: ../neutron-controller-install.rst:65
msgid "Add the ``admin`` role to the ``neutron`` user:"
msgstr ""
#: ../neutron-controller-install.rst:75
msgid "Create the ``neutron`` service entity:"
msgstr ""
#: ../neutron-controller-install.rst:91
msgid "Create the Networking service API endpoints:"
msgstr ""
#: ../neutron-controller-install.rst:146
msgid ""
"Choose one of the following networking options to configure services "
"specific to it."
msgstr ""
#: ../neutron-controller-install.rst:155
msgid ""
"Complete the procedure for your selected networking option by clicking one "
"of the following links. After finishing that procedure, you will be directed "
"back to this page to proceed with configuring the metadata agent."
msgstr ""
#: ../neutron-controller-install.rst:169
msgid "Configure the metadata agent"
msgstr ""
#: ../neutron-controller-install.rst:171
msgid ""
"The :term:`metadata agent <Metadata agent>` provides configuration "
"information such as credentials to instances."
msgstr ""
#: ../neutron-controller-install.rst:174
msgid ""
"Edit the ``/etc/neutron/metadata_agent.ini`` file and complete the following "
"actions:"
msgstr ""
#: ../neutron-controller-install.rst:177
msgid "In the ``[DEFAULT]`` section, configure access parameters:"
msgstr ""
#: ../neutron-controller-install.rst:196
msgid "In the ``[DEFAULT]`` section, configure the metadata host:"
msgstr ""
#: ../neutron-controller-install.rst:204
msgid ""
"In the ``[DEFAULT]`` section, configure the metadata proxy shared secret:"
msgstr ""
#: ../neutron-controller-install.rst:213
msgid ""
"Replace ``METADATA_SECRET`` with a suitable secret for the metadata proxy."
msgstr ""
#: ../neutron-controller-install.rst:227
msgid ""
"Edit the ``/etc/nova/nova.conf`` file and perform the following actions:"
msgstr ""
#: ../neutron-controller-install.rst:229
msgid ""
"In the ``[neutron]`` section, configure access parameters, enable the "
"metadata proxy, and configure the secret:"
msgstr ""
#: ../neutron-controller-install.rst:252
msgid ""
"Replace ``METADATA_SECRET`` with the secret you chose for the metadata proxy."
msgstr ""
#: ../neutron-controller-install.rst:269 ../neutron-controller-install.rst:350
msgid "Populate the database:"
msgstr ""
#: ../neutron-controller-install.rst:278 ../neutron-controller-install.rst:359
msgid ""
"Database population occurs later for Networking because the script requires "
"complete server and plug-in configuration files."
msgstr ""
#: ../neutron-controller-install.rst:287 ../neutron-controller-install.rst:325
msgid ""
"Start the Networking services and configure them to start when the system "
"boots."
msgstr ""
#: ../neutron-controller-install.rst:290 ../neutron-controller-install.rst:328
#: ../neutron-controller-install.rst:370
msgid "For both networking options:"
msgstr ""
#: ../neutron-controller-install.rst:301 ../neutron-controller-install.rst:341
msgid "For networking option 2, also enable and start the layer-3 service:"
msgstr ""
#: ../neutron-controller-install.rst:368
msgid "Restart the Networking services."
msgstr ""
#: ../neutron-controller-install.rst:379
msgid "For networking option 2, also restart the layer-3 service:"
msgstr ""
#: ../neutron-next-steps.rst:5
msgid ""
"Your OpenStack environment now includes the core components necessary to "
"launch a basic instance. You can :ref:`launch-instance` or add more "
"OpenStack services to your environment."
msgstr ""
# #-#-#-#-# neutron-verify-option1.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# neutron-verify-option2.pot (Installation Guide 0.1) #-#-#-#-#
#: ../neutron-verify-option1.rst:10 ../neutron-verify-option2.rst:10
msgid "List agents to verify successful launch of the neutron agents:"
msgstr ""
#: ../neutron-verify-option1.rst:24
msgid ""
"The output should indicate three agents on the controller node and one agent "
"on each compute node."
msgstr ""
#: ../neutron-verify-option2.rst:25
msgid ""
"The output should indicate four agents on the controller node and one agent "
"on each compute node."
msgstr ""
#: ../neutron-verify.rst:11
msgid ""
"List loaded extensions to verify successful launch of the ``neutron-server`` "
"process:"
msgstr ""
#: ../neutron-verify.rst:45
msgid ""
"Use the verification section for the networking option that you chose to "
"deploy."
msgstr ""
#: ../neutron.rst:5
msgid "Add the Networking service"
msgstr ""
#: ../neutron.rst:7
msgid ""
"This chapter explains how to install and configure the OpenStack Networking "
"service (neutron) using the :ref:`provider networks <network1>` or :ref:"
"`self-service networks <network2>` option. For more information about the "
"Networking service including virtual networking components, layout, and "
"traffic flows, see the `Networking Guide <http://docs.openstack.org/"
"networking-guide>`__."
msgstr ""
#: ../nova-compute-install.rst:2
msgid "Install and configure a compute node"
msgstr ""
#: ../nova-compute-install.rst:4
msgid ""
"This section describes how to install and configure the Compute service on a "
"compute node. The service supports several :term:`hypervisors <hypervisor>` "
"to deploy :term:`instances <instance>` or :term:`VMs <virtual machine "
"(VM)>`. For simplicity, this configuration uses the :term:`QEMU <Quick "
"EMUlator (QEMU)>` hypervisor with the :term:`KVM <kernel-based VM (KVM)>` "
"extension on compute nodes that support hardware acceleration for virtual "
"machines. On legacy hardware, this configuration uses the generic QEMU "
"hypervisor. You can follow these instructions with minor modifications to "
"horizontally scale your environment with additional compute nodes."
msgstr ""
#: ../nova-compute-install.rst:17
msgid ""
"This section assumes that you are following the instructions in this guide "
"step-by-step to configure the first compute node. If you want to configure "
"additional compute nodes, prepare them in a similar fashion to the first "
"compute node in the :ref:`example architectures <overview-example-"
"architectures>` section. Each additional compute node requires a unique IP "
"address."
msgstr ""
#: ../nova-compute-install.rst:55
msgid ""
"Respond to prompts for :doc:`database management <debconf/debconf-dbconfig-"
"common>`, :doc:`Identity service credentials <debconf/debconf-keystone-"
"authtoken>`, and :doc:`message broker credentials <debconf/debconf-"
"rabbitmq>`. Make sure that you do not activate database management handling "
"by debconf, as a compute node should not access the central database."
msgstr ""
#: ../nova-compute-install.rst:67
msgid ""
"In the ``[DEFAULT]`` and [oslo_messaging_rabbit] sections, configure "
"``RabbitMQ`` message queue access:"
msgstr ""
#: ../nova-compute-install.rst:115
msgid ""
"In the ``[DEFAULT]`` section, check that the ``my_ip`` option is correctly "
"set (this value is handled by the config and postinst scripts of the ``nova-"
"common`` package using debconf):"
msgstr ""
#: ../nova-compute-install.rst:125 ../nova-compute-install.rst:140
msgid ""
"Replace ``MANAGEMENT_INTERFACE_IP_ADDRESS`` with the IP address of the "
"management network interface on your compute node, typically 10.0.0.31 for "
"the first node in the :ref:`example architecture <overview-example-"
"architectures>`."
msgstr ""
# #-#-#-#-# nova-compute-install.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# nova-controller-install.pot (Installation Guide 0.1) #-#-#-#-#
#: ../nova-compute-install.rst:145 ../nova-controller-install.rst:294
msgid ""
"In the ``[DEFAULT]`` section, enable support for the Networking service:"
msgstr ""
# #-#-#-#-# nova-compute-install.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# nova-controller-install.pot (Installation Guide 0.1) #-#-#-#-#
#: ../nova-compute-install.rst:158 ../nova-controller-install.rst:307
msgid ""
"By default, Compute uses an internal firewall service. Since Networking "
"includes a firewall service, you must disable the Compute firewall service "
"by using the ``nova.virt.firewall.NoopFirewallDriver`` firewall driver."
msgstr ""
#: ../nova-compute-install.rst:163
msgid "In the ``[vnc]`` section, enable and configure remote console access:"
msgstr ""
#: ../nova-compute-install.rst:174
msgid ""
"The server component listens on all IP addresses and the proxy component "
"only listens on the management interface IP address of the compute node. The "
"base URL indicates the location where you can use a web browser to access "
"remote consoles of instances on this compute node."
msgstr ""
#: ../nova-compute-install.rst:182
msgid ""
"If the web browser to access remote consoles resides on a host that cannot "
"resolve the ``controller`` hostname, you must replace ``controller`` with "
"the management interface IP address of the controller node."
msgstr ""
# #-#-#-#-# nova-compute-install.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# nova-controller-install.pot (Installation Guide 0.1) #-#-#-#-#
#: ../nova-compute-install.rst:187 ../nova-controller-install.rst:322
msgid ""
"In the ``[glance]`` section, configure the location of the Image service:"
msgstr ""
#: ../nova-compute-install.rst:227
msgid "Ensure the kernel module ``nbd`` is loaded."
msgstr ""
#: ../nova-compute-install.rst:233
msgid ""
"Ensure the module loads on every boot by adding ``nbd`` to the ``/etc/"
"modules-load.d/nbd.conf`` file."
msgstr ""
#: ../nova-compute-install.rst:239
msgid ""
"Determine whether your compute node supports hardware acceleration for "
"virtual machines:"
msgstr ""
#: ../nova-compute-install.rst:246
msgid ""
"If this command returns a value of ``one or greater``, your compute node "
"supports hardware acceleration which typically requires no additional "
"configuration."
msgstr ""
#: ../nova-compute-install.rst:250
msgid ""
"If this command returns a value of ``zero``, your compute node does not "
"support hardware acceleration and you must configure ``libvirt`` to use QEMU "
"instead of KVM."
msgstr ""
#: ../nova-compute-install.rst:256
msgid ""
"Edit the ``[libvirt]`` section in the ``/etc/nova/nova.conf`` file as "
"follows:"
msgstr ""
#: ../nova-compute-install.rst:267
msgid ""
"Edit the ``[libvirt]`` section in the ``/etc/nova/nova-compute.conf`` file "
"as follows:"
msgstr ""
#: ../nova-compute-install.rst:278
msgid ""
"Replace the ``nova-compute-kvm`` package with ``nova-compute-qemu`` which "
"automatically changes the ``/etc/nova/nova-compute.conf`` file and installs "
"the necessary dependencies:"
msgstr ""
#: ../nova-compute-install.rst:288
msgid ""
"Start the Compute service including its dependencies and configure them to "
"start automatically when the system boots:"
msgstr ""
#: ../nova-controller-install.rst:4
msgid ""
"This section describes how to install and configure the Compute service, "
"code-named nova, on the controller node."
msgstr ""
#: ../nova-controller-install.rst:12
msgid ""
"Before you install and configure the Compute service, you must create a "
"database, service credentials, and API endpoints."
msgstr ""
#: ../nova-controller-install.rst:24
msgid "Create the ``nova`` database:"
msgstr ""
#: ../nova-controller-install.rst:30
msgid "Grant proper access to the ``nova`` database:"
msgstr ""
#: ../nova-controller-install.rst:39
msgid "Replace ``NOVA_DBPASS`` with a suitable password."
msgstr ""
#: ../nova-controller-install.rst:52
msgid "Create the ``nova`` user:"
msgstr ""
#: ../nova-controller-install.rst:68
msgid "Add the ``admin`` role to the ``nova`` user:"
msgstr ""
#: ../nova-controller-install.rst:78
msgid "Create the ``nova`` service entity:"
msgstr ""
#: ../nova-controller-install.rst:94
msgid "Create the Compute service API endpoints:"
msgstr ""
#: ../nova-controller-install.rst:222
msgid ""
"Replace ``NOVA_DBPASS`` with the password you chose for the Compute database."
msgstr ""
#: ../nova-controller-install.rst:282
msgid ""
"The ``.config`` and ``.postinst`` maintainer scripts of the ``nova-common`` "
"package detect automatically the IP address which goes in the ``my_ip`` "
"directive of the ``[DEFAULT]`` section. This value will normally still be "
"prompted, and you can check that it is correct in the nova.conf after ``nova-"
"common`` is installed:"
msgstr ""
#: ../nova-controller-install.rst:312
msgid ""
"In the ``[vnc]`` section, configure the VNC proxy to use the management "
"interface IP address of the controller node:"
msgstr ""
#: ../nova-controller-install.rst:361
msgid "In the ``[DEFAULT]`` section, disable the EC2 API:"
msgstr ""
#: ../nova-controller-install.rst:380 ../nova-controller-install.rst:388
msgid "Populate the Compute database:"
msgstr ""
#: ../nova-controller-install.rst:399 ../nova-controller-install.rst:415
msgid ""
"Start the Compute services and configure them to start when the system boots:"
msgstr ""
#: ../nova-controller-install.rst:431
msgid "Restart the Compute services:"
msgstr ""
#: ../nova-verify.rst:4
msgid "Verify operation of the Compute service."
msgstr ""
#: ../nova-verify.rst:35
msgid ""
"This output should indicate four service components enabled on the "
"controller node and one service component enabled on the compute node."
msgstr ""
#: ../nova-verify.rst:39
msgid ""
"List API endpoints in the Identity service to verify connectivity with the "
"Identity service:"
msgstr ""
#: ../nova-verify.rst:131
msgid "Ignore any warnings in this output."
msgstr ""
#: ../nova-verify.rst:133
msgid ""
"List images in the Image service catalog to verify connectivity with the "
"Image service:"
msgstr ""
#: ../nova.rst:3
msgid "Add the Compute service"
msgstr ""
#: ../overview.rst:0
msgid "**OpenStack services**"
msgstr ""
#: ../overview.rst:3
msgid "Overview"
msgstr ""
#: ../overview.rst:5
msgid ""
"The :term:`OpenStack` project is an open source cloud computing platform "
"that supports all types of cloud environments. The project aims for simple "
"implementation, massive scalability, and a rich set of features. Cloud "
"computing experts from around the world contribute to the project."
msgstr ""
#: ../overview.rst:10
msgid ""
"OpenStack provides an :term:`Infrastructure-as-a-Service (IaaS)<IaaS>` "
"solution through a variety of complemental services. Each service offers an :"
"term:`application programming interface (API)<API>` that facilitates this "
"integration."
msgstr ""
#: ../overview.rst:15
msgid ""
"This guide covers step-by-step deployment of the following major OpenStack "
"services using a functional example architecture suitable for new users of "
"OpenStack with sufficient Linux experience:"
msgstr ""
#: ../overview.rst:23
msgid "Service"
msgstr ""
#: ../overview.rst:24
msgid "Project name"
msgstr ""
#: ../overview.rst:26
msgid ""
"`Dashboard <http://www.openstack.org/software/releases/liberty/components/"
"horizon>`_"
msgstr ""
#: ../overview.rst:27
msgid "`Horizon <http://docs.openstack.org/developer/horizon/>`_"
msgstr ""
#: ../overview.rst:28
msgid ""
"Provides a web-based self-service portal to interact with underlying "
"OpenStack services, such as launching an instance, assigning IP addresses "
"and configuring access controls."
msgstr ""
#: ../overview.rst:32
msgid ""
"`Compute <http://www.openstack.org/software/releases/liberty/components/"
"nova>`_"
msgstr ""
#: ../overview.rst:33
msgid "`Nova <http://docs.openstack.org/developer/nova/>`_"
msgstr ""
#: ../overview.rst:34
msgid ""
"Manages the lifecycle of compute instances in an OpenStack environment. "
"Responsibilities include spawning, scheduling and decommissioning of virtual "
"machines on demand."
msgstr ""
#: ../overview.rst:38
msgid ""
"`Networking <http://www.openstack.org/software/releases/liberty/components/"
"neutron>`_"
msgstr ""
#: ../overview.rst:39
msgid "`Neutron <http://docs.openstack.org/developer/neutron/>`_"
msgstr ""
#: ../overview.rst:40
msgid ""
"Enables Network-Connectivity-as-a-Service for other OpenStack services, such "
"as OpenStack Compute. Provides an API for users to define networks and the "
"attachments into them. Has a pluggable architecture that supports many "
"popular networking vendors and technologies."
msgstr ""
#: ../overview.rst:48
msgid "**Storage**"
msgstr ""
#: ../overview.rst:49
msgid ""
"`Object Storage <http://www.openstack.org/software/releases/liberty/"
"components/swift>`_"
msgstr ""
#: ../overview.rst:50
msgid "`Swift <http://docs.openstack.org/developer/swift/>`_"
msgstr ""
#: ../overview.rst:51
msgid ""
"Stores and retrieves arbitrary unstructured data objects via a :term:"
"`RESTful`, HTTP based API. It is highly fault tolerant with its data "
"replication and scale-out architecture. Its implementation is not like a "
"file server with mountable directories. In this case, it writes objects and "
"files to multiple drives, ensuring the data is replicated across a server "
"cluster."
msgstr ""
#: ../overview.rst:58
msgid ""
"`Block Storage <http://www.openstack.org/software/releases/liberty/"
"components/cinder>`_"
msgstr ""
#: ../overview.rst:59
msgid "`Cinder <http://docs.openstack.org/developer/cinder/>`_"
msgstr ""
#: ../overview.rst:60
msgid ""
"Provides persistent block storage to running instances. Its pluggable driver "
"architecture facilitates the creation and management of block storage "
"devices."
msgstr ""
#: ../overview.rst:65
msgid "**Shared services**"
msgstr ""
#: ../overview.rst:66
msgid ""
"`Identity service <http://www.openstack.org/software/releases/liberty/"
"components/keystone>`_"
msgstr ""
#: ../overview.rst:67
msgid "`Keystone <http://docs.openstack.org/developer/keystone/>`_"
msgstr ""
#: ../overview.rst:68
msgid ""
"Provides an authentication and authorization service for other OpenStack "
"services. Provides a catalog of endpoints for all OpenStack services."
msgstr ""
#: ../overview.rst:71
msgid ""
"`Image service <http://www.openstack.org/software/releases/liberty/"
"components/glance>`_"
msgstr ""
#: ../overview.rst:72
msgid "`Glance <http://docs.openstack.org/developer/glance/>`_"
msgstr ""
#: ../overview.rst:73
msgid ""
"Stores and retrieves virtual machine disk images. OpenStack Compute makes "
"use of this during instance provisioning."
msgstr ""
#: ../overview.rst:76
msgid ""
"`Telemetry <http://www.openstack.org/software/releases/liberty/components/"
"ceilometer>`_"
msgstr ""
#: ../overview.rst:77
msgid "`Ceilometer <http://docs.openstack.org/developer/ceilometer/>`_"
msgstr ""
#: ../overview.rst:78
msgid ""
"Monitors and meters the OpenStack cloud for billing, benchmarking, "
"scalability, and statistical purposes."
msgstr ""
#: ../overview.rst:82
msgid "**Higher-level services**"
msgstr ""
#: ../overview.rst:83
msgid ""
"`Orchestration <http://www.openstack.org/software/releases/liberty/"
"components/heat>`_"
msgstr ""
#: ../overview.rst:84
msgid "`Heat <http://docs.openstack.org/developer/heat/>`_"
msgstr ""
#: ../overview.rst:85
msgid ""
"Orchestrates multiple composite cloud applications by using either the "
"native :term:`HOT <Heat Orchestration Template (HOT)>` template format or "
"the AWS CloudFormation template format, through both an OpenStack-native "
"REST API and a CloudFormation-compatible Query API."
msgstr ""
#: ../overview.rst:93
msgid ""
"After becoming familiar with basic installation, configuration, operation, "
"and troubleshooting of these OpenStack services, you should consider the "
"following steps toward deployment using a production architecture:"
msgstr ""
#: ../overview.rst:97
msgid ""
"Determine and implement the necessary core and optional services to meet "
"performance and redundancy requirements."
msgstr ""
#: ../overview.rst:100
msgid ""
"Increase security using methods such as firewalls, encryption, and service "
"policies."
msgstr ""
#: ../overview.rst:103
msgid ""
"Implement a deployment tool such as Ansible, Chef, Puppet, or Salt to "
"automate deployment and management of the production environment."
msgstr ""
#: ../overview.rst:109
msgid "Example architecture"
msgstr ""
#: ../overview.rst:111
msgid ""
"The example architecture requires at least two nodes (hosts) to launch a "
"basic :term:`virtual machine <virtual machine (VM)>` or instance. Optional "
"services such as Block Storage and Object Storage require additional nodes."
msgstr ""
#: ../overview.rst:115
msgid ""
"This example architecture differs from a minimal production architecture as "
"follows:"
msgstr ""
#: ../overview.rst:118
msgid ""
"Networking agents reside on the controller node instead of one or more "
"dedicated network nodes."
msgstr ""
#: ../overview.rst:121
msgid ""
"Overlay (tunnel) traffic for private networks traverses the management "
"network instead of a dedicated network."
msgstr ""
#: ../overview.rst:124
msgid ""
"For more information on production architectures, see the `Architecture "
"Design Guide <http://docs.openstack.org/arch-design/>`__, `Operations Guide "
"<http://docs.openstack.org/ops/>`__, and `Networking Guide <http://docs."
"openstack.org/networking-guide/>`__."
msgstr ""
#: ../overview.rst:134
msgid "**Hardware requirements**"
msgstr ""
#: ../overview.rst:137
msgid "Controller"
msgstr ""
#: ../overview.rst:139
msgid ""
"The controller node runs the Identity service, Image service, management "
"portions of Compute, management portion of Networking, various Networking "
"agents, and the dashboard. It also includes supporting services such as an "
"SQL database, :term:`message queue`, and :term:`NTP`."
msgstr ""
#: ../overview.rst:144
msgid ""
"Optionally, the controller node runs portions of Block Storage, Object "
"Storage, Orchestration, and Telemetry services."
msgstr ""
#: ../overview.rst:147
msgid "The controller node requires a minimum of two network interfaces."
msgstr ""
#: ../overview.rst:150
msgid "Compute"
msgstr ""
#: ../overview.rst:152
msgid ""
"The compute node runs the :term:`hypervisor` portion of Compute that "
"operates instances. By default, Compute uses the :term:`KVM <kernel-based VM "
"(KVM)>` hypervisor. The compute node also runs a Networking service agent "
"that connects instances to virtual networks and provides firewalling "
"services to instances via :term:`security groups <security group>`."
msgstr ""
#: ../overview.rst:159
msgid ""
"You can deploy more than one compute node. Each node requires a minimum of "
"two network interfaces."
msgstr ""
#: ../overview.rst:165
msgid ""
"The optional Block Storage node contains the disks that the Block Storage "
"service provisions for instances."
msgstr ""
#: ../overview.rst:168 ../overview.rst:182
msgid ""
"For simplicity, service traffic between compute nodes and this node uses the "
"management network. Production environments should implement a separate "
"storage network to increase performance and security."
msgstr ""
#: ../overview.rst:172
msgid ""
"You can deploy more than one block storage node. Each node requires a "
"minimum of one network interface."
msgstr ""
#: ../overview.rst:176
msgid "Object Storage"
msgstr ""
#: ../overview.rst:178
msgid ""
"The optional Object Storage node contain the disks that the Object Storage "
"service uses for storing accounts, containers, and objects."
msgstr ""
#: ../overview.rst:186
msgid ""
"This service requires two nodes. Each node requires a minimum of one network "
"interface. You can deploy more than two object storage nodes."
msgstr ""
#: ../overview.rst:190
msgid "Networking"
msgstr ""
#: ../overview.rst:192
msgid "Choose one of the following virtual networking options."
msgstr ""
#: ../overview.rst:199
msgid ""
"The provider networks option deploys the OpenStack Networking service in the "
"simplest way possible with primarily layer-2 (bridging/switching) services "
"and VLAN segmentation of networks. Essentially, it bridges virtual networks "
"to physical networks and relies on physical network infrastructure for "
"layer-3 (routing) services. Additionally, a :term:`DHCP` service provides IP "
"address information to instances."
msgstr ""
#: ../overview.rst:208
msgid ""
"This option lacks support for self-service private networks, layer-3 "
"(routing) services, and advanced services such as :term:`LBaaS` and :term:"
"`FWaaS`. Consider the self-service networks option if you desire these "
"features."
msgstr ""
#: ../overview.rst:223
msgid ""
"The self-service networks option augments the provider networks option with "
"layer-3 (routing) services that enable :term:`self-service` networks using "
"overlay segmentation methods such as :term:`VXLAN`. Essentially, it routes "
"virtual networks to physical networks using :term:`NAT`. Additionally, this "
"option provides the foundation for advanced services such as LBaaS and FWaaS."
msgstr ""
# #-#-#-#-# environment-networking-compute.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# environment-networking-controller.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# environment-networking-storage-cinder.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# environment-networking-storage-swift.pot (Installation Guide 0.1) #-#-#-#-#
#: ../shared/edit_hosts_file.txt:1
msgid "Edit the ``/etc/hosts`` file to contain the following:"
msgstr ""
# #-#-#-#-# environment-networking-compute.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# environment-networking-controller.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# environment-networking-storage-cinder.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# environment-networking-storage-swift.pot (Installation Guide 0.1) #-#-#-#-#
#: ../shared/edit_hosts_file.txt:22
msgid ""
"Some distributions add an extraneous entry in the ``/etc/hosts`` file that "
"resolves the actual hostname to another loopback IP address such as "
"``127.0.1.1``. You must comment out or remove this entry to prevent name "
"resolution problems. **Do not remove the 127.0.0.1 entry.**"
msgstr ""
# #-#-#-#-# environment-networking-compute.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# environment-networking-controller.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# environment-networking-storage-cinder.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# environment-networking-storage-swift.pot (Installation Guide 0.1) #-#-#-#-#
#: ../shared/edit_hosts_file.txt:30
msgid ""
"To reduce complexity of this guide, we add host entries for optional "
"services regardless of whether you choose to deploy them."
msgstr ""
# #-#-#-#-# glance-install.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# heat-install.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# horizon-install.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# keystone-install.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# neutron-compute-install.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# neutron-controller-install-option1.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# nova-compute-install.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# nova-controller-install.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# swift-controller-install.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# swift-finalize-installation.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# swift-storage-install.pot (Installation Guide 0.1) #-#-#-#-#
#: ../shared/note_configuration_vary_by_distribution.rst:3
msgid ""
"Default configuration files vary by distribution. You might need to add "
"these sections and options rather than modifying existing sections and "
"options. Also, an ellipsis (``...``) in the configuration snippets indicates "
"potential default configuration options that you should retain."
msgstr ""
#: ../swift-controller-include.txt:4
msgid ""
"In the ``[DEFAULT]`` section, configure the bind port, user, and "
"configuration directory:"
msgstr ""
# #-#-#-#-# swift-controller-install.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# swift-storage-install.pot (Installation Guide 0.1) #-#-#-#-#
#: ../swift-controller-include.txt:15 ../swift-storage-include1.txt:21
#: ../swift-storage-include2.txt:21 ../swift-storage-include3.txt:21
msgid "In the ``[pipeline:main]`` section, enable the appropriate modules:"
msgstr ""
# #-#-#-#-# swift-controller-install.pot (Installation Guide 0.1) #-#-#-#-#
# #-#-#-#-# swift-storage-install.pot (Installation Guide 0.1) #-#-#-#-#
#: ../swift-controller-include.txt:26 ../swift-storage-include1.txt:30
#: ../swift-storage-include2.txt:30 ../swift-storage-include3.txt:30
msgid ""
"For more information on other modules that enable additional features, see "
"the `Deployment Guide <http://docs.openstack.org/developer/swift/"
"deployment_guide.html>`__."
msgstr ""
#: ../swift-controller-include.txt:29
msgid ""
"In the ``[app:proxy-server]`` section, enable automatic account creation:"
msgstr ""
#: ../swift-controller-include.txt:38
msgid "In the ``[filter:keystoneauth]`` section, configure the operator roles:"
msgstr ""
#: ../swift-controller-include.txt:47
msgid ""
"In the ``[filter:authtoken]`` section, configure Identity service access:"
msgstr ""
#: ../swift-controller-include.txt:64
msgid ""
"Replace ``SWIFT_PASS`` with the password you chose for the ``swift`` user in "
"the Identity service."
msgstr ""
#: ../swift-controller-include.txt:69
msgid ""
"Comment out or remove any other options in the ``[filter:authtoken]`` "
"section."
msgstr ""
#: ../swift-controller-include.txt:72
msgid ""
"In the ``[filter:cache]`` section, configure the ``memcached`` location:"
msgstr ""
#: ../swift-controller-install.rst:4
msgid "Install and configure the controller node"
msgstr ""
#: ../swift-controller-install.rst:6
msgid ""
"This section describes how to install and configure the proxy service that "
"handles requests for the account, container, and object services operating "
"on the storage nodes. For simplicity, this guide installs and configures the "
"proxy service on the controller node. However, you can run the proxy service "
"on any node with network connectivity to the storage nodes. Additionally, "
"you can install and configure the proxy service on multiple nodes to "
"increase performance and redundancy. For more information, see the "
"`Deployment Guide <http://docs.openstack.org/developer/swift/"
"deployment_guide.html>`__."
msgstr ""
#: ../swift-controller-install.rst:18
msgid ""
"The proxy service relies on an authentication and authorization mechanism "
"such as the Identity service. However, unlike other services, it also offers "
"an internal mechanism that allows it to operate without any other OpenStack "
"services. However, for simplicity, this guide references the Identity "
"service in :doc:`keystone`. Before you configure the Object Storage service, "
"you must create service credentials and an API endpoint."
msgstr ""
#: ../swift-controller-install.rst:27
msgid ""
"The Object Storage service does not use an SQL database on the controller "
"node. Instead, it uses distributed SQLite databases on each storage node."
msgstr ""
#: ../swift-controller-install.rst:36
msgid "To create the Identity service credentials, complete these steps:"
msgstr ""
#: ../swift-controller-install.rst:38
msgid "Create the ``swift`` user:"
msgstr ""
#: ../swift-controller-install.rst:54
msgid "Add the ``admin`` role to the ``swift`` user:"
msgstr ""
#: ../swift-controller-install.rst:64
msgid "Create the ``swift`` service entity:"
msgstr ""
#: ../swift-controller-install.rst:80
msgid "Create the Object Storage service API endpoints:"
msgstr ""
#: ../swift-controller-install.rst:165
msgid "Complete OpenStack environments already include some of these packages."
msgstr ""
#: ../swift-controller-install.rst:170
msgid "Create the ``/etc/swift`` directory."
msgstr ""
#: ../swift-controller-install.rst:172 ../swift-controller-install.rst:181
msgid ""
"Obtain the proxy service configuration file from the Object Storage source "
"repository:"
msgstr ""
#: ../swift-finalize-installation.rst:8
msgid ""
"Obtain the ``/etc/swift/swift.conf`` file from the Object Storage source "
"repository:"
msgstr ""
#: ../swift-finalize-installation.rst:16 ../swift-finalize-installation.rst:50
msgid ""
"Edit the ``/etc/swift/swift.conf`` file and complete the following actions:"
msgstr ""
#: ../swift-finalize-installation.rst:19 ../swift-finalize-installation.rst:53
msgid ""
"In the ``[swift-hash]`` section, configure the hash path prefix and suffix "
"for your environment."
msgstr ""
#: ../swift-finalize-installation.rst:29 ../swift-finalize-installation.rst:63
msgid "Replace HASH_PATH_PREFIX and HASH_PATH_SUFFIX with unique values."
msgstr ""
#: ../swift-finalize-installation.rst:33 ../swift-finalize-installation.rst:67
msgid "Keep these values secret and do not change or lose them."
msgstr ""
#: ../swift-finalize-installation.rst:35 ../swift-finalize-installation.rst:69
msgid ""
"In the ``[storage-policy:0]`` section, configure the default storage policy:"
msgstr ""
#: ../swift-finalize-installation.rst:45 ../swift-finalize-installation.rst:79
msgid ""
"Copy the ``swift.conf`` file to the ``/etc/swift`` directory on each storage "
"node and any additional nodes running the proxy service."
msgstr ""
#: ../swift-finalize-installation.rst:84
#: ../swift-finalize-installation.rst:112
#: ../swift-finalize-installation.rst:149
msgid "On all nodes, ensure proper ownership of the configuration directory:"
msgstr ""
#: ../swift-finalize-installation.rst:90
msgid ""
"On the controller node and any other nodes running the proxy service, "
"restart the Object Storage proxy service including its dependencies:"
msgstr ""
#: ../swift-finalize-installation.rst:98
msgid "On the storage nodes, start the Object Storage services:"
msgstr ""
#: ../swift-finalize-installation.rst:106
msgid ""
"The storage node runs many Object Storage services and the :command:`swift-"
"init` command makes them easier to manage. You can ignore errors from "
"services not running on the storage node."
msgstr ""
#: ../swift-finalize-installation.rst:118
#: ../swift-finalize-installation.rst:155
msgid ""
"On the controller node and any other nodes running the proxy service, start "
"the Object Storage proxy service including its dependencies and configure "
"them to start when the system boots:"
msgstr ""
#: ../swift-finalize-installation.rst:127
#: ../swift-finalize-installation.rst:164
msgid ""
"On the storage nodes, start the Object Storage services and configure them "
"to start when the system boots:"
msgstr ""
#: ../swift-initial-rings.rst:2
msgid "Create and distribute initial rings"
msgstr ""
#: ../swift-initial-rings.rst:4
msgid ""
"Before starting the Object Storage services, you must create the initial "
"account, container, and object rings. The ring builder creates configuration "
"files that each node uses to determine and deploy the storage architecture. "
"For simplicity, this guide uses one region and zone with 2^10 (1024) maximum "
"partitions, 3 replicas of each object, and 1 hour minimum time between "
"moving a partition more than once. For Object Storage, a partition indicates "
"a directory on a storage device rather than a conventional partition table. "
"For more information, see the `Deployment Guide <http://docs.openstack.org/"
"developer/swift/deployment_guide.html>`__."
msgstr ""
#: ../swift-initial-rings.rst:18
msgid "Create account ring"
msgstr ""
#: ../swift-initial-rings.rst:20
msgid ""
"The account server uses the account ring to maintain lists of containers."
msgstr ""
#: ../swift-initial-rings.rst:22 ../swift-initial-rings.rst:99
#: ../swift-initial-rings.rst:176
msgid "Change to the ``/etc/swift`` directory."
msgstr ""
#: ../swift-initial-rings.rst:24
msgid "Create the base ``account.builder`` file:"
msgstr ""
#: ../swift-initial-rings.rst:34 ../swift-initial-rings.rst:111
#: ../swift-initial-rings.rst:188
msgid "Add each storage node to the ring:"
msgstr ""
#: ../swift-initial-rings.rst:42 ../swift-initial-rings.rst:119
#: ../swift-initial-rings.rst:196
msgid ""
"Replace ``STORAGE_NODE_MANAGEMENT_INTERFACE_IP_ADDRESS`` with the IP address "
"of the management network on the storage node. Replace ``DEVICE_NAME`` with "
"a storage device name on the same storage node. For example, using the first "
"storage node in :ref:`swift-storage` with the ``/dev/sdb`` storage device "
"and weight of 100:"
msgstr ""
#: ../swift-initial-rings.rst:53 ../swift-initial-rings.rst:130
#: ../swift-initial-rings.rst:207
msgid ""
"Repeat this command for each storage device on each storage node. In the "
"example architecture, use the command in four variations:"
msgstr ""
#: ../swift-initial-rings.rst:71 ../swift-initial-rings.rst:148
#: ../swift-initial-rings.rst:225
msgid "Verify the ring contents:"
msgstr ""
#: ../swift-initial-rings.rst:86 ../swift-initial-rings.rst:163
#: ../swift-initial-rings.rst:240
msgid "Rebalance the ring:"
msgstr ""
#: ../swift-initial-rings.rst:94
msgid "Create container ring"
msgstr ""
#: ../swift-initial-rings.rst:96
msgid ""
"The container server uses the container ring to maintain lists of objects. "
"However, it does not track object locations."
msgstr ""
#: ../swift-initial-rings.rst:101
msgid "Create the base ``container.builder`` file:"
msgstr ""
#: ../swift-initial-rings.rst:171
msgid "Create object ring"
msgstr ""
#: ../swift-initial-rings.rst:173
msgid ""
"The object server uses the object ring to maintain lists of object locations "
"on local devices."
msgstr ""
#: ../swift-initial-rings.rst:178
msgid "Create the base ``object.builder`` file:"
msgstr ""
#: ../swift-initial-rings.rst:248
msgid "Distribute ring configuration files"
msgstr ""
#: ../swift-initial-rings.rst:250
msgid ""
"Copy the ``account.ring.gz``, ``container.ring.gz``, and ``object.ring.gz`` "
"files to the ``/etc/swift`` directory on each storage node and any "
"additional nodes running the proxy service."
msgstr ""
#: ../swift-next-steps.rst:5
msgid ""
"Your OpenStack environment now includes Object Storage. You can :ref:`launch-"
"instance` or add more services to your environment."
msgstr ""
#: ../swift-storage-include1.txt:1
msgid ""
"Edit the ``/etc/swift/account-server.conf`` file and complete the following "
"actions:"
msgstr ""
#: ../swift-storage-include1.txt:4 ../swift-storage-include2.txt:4
#: ../swift-storage-include3.txt:4
msgid ""
"In the ``[DEFAULT]`` section, configure the bind IP address, bind port, "
"user, configuration directory, and mount point directory:"
msgstr ""
#: ../swift-storage-include1.txt:18 ../swift-storage-include2.txt:18
#: ../swift-storage-include3.txt:18 ../swift-storage-install.rst:105
msgid ""
"Replace ``MANAGEMENT_INTERFACE_IP_ADDRESS`` with the IP address of the "
"management network on the storage node."
msgstr ""
#: ../swift-storage-include1.txt:33 ../swift-storage-include2.txt:33
msgid ""
"In the ``[filter:recon]`` section, configure the recon (meters) cache "
"directory:"
msgstr ""
#: ../swift-storage-include2.txt:1
msgid ""
"Edit the ``/etc/swift/container-server.conf`` file and complete the "
"following actions:"
msgstr ""
#: ../swift-storage-include3.txt:1
msgid ""
"Edit the ``/etc/swift/object-server.conf`` file and complete the following "
"actions:"
msgstr ""
#: ../swift-storage-include3.txt:33
msgid ""
"In the ``[filter:recon]`` section, configure the recon (meters) cache and "
"lock directories:"
msgstr ""
#: ../swift-storage-install.rst:4
msgid "Install and configure the storage nodes"
msgstr ""
#: ../swift-storage-install.rst:6
msgid ""
"This section describes how to install and configure storage nodes that "
"operate the account, container, and object services. For simplicity, this "
"configuration references two storage nodes, each containing two empty local "
"block storage devices. The instructions use ``/dev/sdb`` and ``/dev/sdc``, "
"but you can substitute different values for your particular nodes."
msgstr ""
#: ../swift-storage-install.rst:13
msgid ""
"Although Object Storage supports any file system with :term:`extended "
"attributes (xattr)`, testing and benchmarking indicate the best performance "
"and reliability on :term:`XFS`. For more information on horizontally scaling "
"your environment, see the `Deployment Guide <http://docs.openstack.org/"
"developer/swift/deployment_guide.html>`_."
msgstr ""
#: ../swift-storage-install.rst:22
msgid ""
"Before you install and configure the Object Storage service on the storage "
"nodes, you must prepare the storage devices."
msgstr ""
#: ../swift-storage-install.rst:27 ../swift-storage-install.rst:145
msgid "Perform these steps on each storage node."
msgstr ""
#: ../swift-storage-install.rst:49
msgid "Format the ``/dev/sdb`` and ``/dev/sdc`` devices as XFS:"
msgstr ""
#: ../swift-storage-install.rst:56
msgid "Create the mount point directory structure:"
msgstr ""
#: ../swift-storage-install.rst:63
msgid "Edit the ``/etc/fstab`` file and add the following to it:"
msgstr ""
#: ../swift-storage-install.rst:70
msgid "Mount the devices:"
msgstr ""
#: ../swift-storage-install.rst:77
msgid "Edit the ``/etc/rsyncd.conf`` file and add the following to it:"
msgstr ""
#: ../swift-storage-install.rst:110
msgid ""
"The ``rsync`` service requires no authentication, so consider running it on "
"a private network in production environments."
msgstr ""
#: ../swift-storage-install.rst:115
msgid "Edit the ``/etc/default/rsync`` file and enable the ``rsync`` service:"
msgstr ""
#: ../swift-storage-install.rst:122
msgid "Start the ``rsync`` service:"
msgstr ""
#: ../swift-storage-install.rst:130
msgid ""
"Start the ``rsyncd`` service and configure it to start when the system boots:"
msgstr ""
#: ../swift-storage-install.rst:171
msgid ""
"Obtain the accounting, container, and object service configuration files "
"from the Object Storage source repository:"
msgstr ""
#: ../swift-storage-install.rst:183 ../swift-storage-install.rst:201
msgid "Ensure proper ownership of the mount point directory structure:"
msgstr ""
#: ../swift-storage-install.rst:189 ../swift-storage-install.rst:207
msgid "Create the ``recon`` directory and ensure proper ownership of it:"
msgstr ""
#: ../swift-verify.rst:4
msgid "Verify operation of the Object Storage service."
msgstr ""
#: ../swift-verify.rst:10
msgid ""
"In each client environment script, configure the Object Storage service "
"client to use the Identity API version 3:"
msgstr ""
#: ../swift-verify.rst:18
msgid "Source the ``demo`` credentials:"
msgstr ""
#: ../swift-verify.rst:24
msgid "Show the service status:"
msgstr ""
#: ../swift-verify.rst:42
msgid "Upload a test file:"
msgstr ""
#: ../swift-verify.rst:49
msgid ""
"Replace ``FILE`` with the name of a local file to upload to the "
"``container1`` container."
msgstr ""
#: ../swift-verify.rst:52
msgid "List containers:"
msgstr ""
#: ../swift-verify.rst:59
msgid "Download a test file:"
msgstr ""
#: ../swift-verify.rst:66
msgid ""
"Replace ``FILE`` with the name of the file uploaded to the ``container1`` "
"container."
msgstr ""
#: ../swift.rst:5
msgid "Add the Object Storage service"
msgstr ""
#: ../swift.rst:7
msgid ""
"The OpenStack Object Storage services (swift) work together to provide "
"object storage and retrieval through a :term:`REST API <RESTful>`. Your "
"environment must at least include the Identity service (keystone) prior to "
"deploying Object Storage."
msgstr ""
View Git Blame Copy Permalink