b95eafb0ee
The requirements.txt contents do not need to be installed on to the host. The majority of the requirements are for ansible, or for release and management tooling which needs to use the Ansible runtime venv. Rather than forcing the installation of pip on the host, we only install virtualenv via distro packages (where possible). With virtualenv in place we can create the runtime venv and install pip, etc and all requirements into there. Doing this keeps the system python libraries as clean as possible, preventing clashes with other packages (eg: ceph) which try to install other python libraries which conflict on CentOS. Change-Id: I0db786645c11649764680697518c97ddf9610cfa
196 lines
5.4 KiB
ReStructuredText
196 lines
5.4 KiB
ReStructuredText
.. _configure:
|
|
|
|
========================
|
|
Configure the deployment
|
|
========================
|
|
|
|
.. figure:: figures/installation-workflow-configure-deployment.png
|
|
:width: 100%
|
|
|
|
Ansible references some files that contain mandatory and optional
|
|
configuration directives. Before you can run the Ansible playbooks, modify
|
|
these files to define the target environment. Configuration tasks include:
|
|
|
|
* Target host networking to define bridge interfaces and
|
|
networks.
|
|
* A list of target hosts on which to install the software.
|
|
* Virtual and physical network relationships for OpenStack
|
|
Networking (neutron).
|
|
* Passwords for all services.
|
|
|
|
Initial environment configuration
|
|
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
|
|
|
OpenStack-Ansible (OSA) depends on various files that are used to build an
|
|
inventory for Ansible. Perform the following configuration on the deployment
|
|
host.
|
|
|
|
#. Copy the contents of the
|
|
``/opt/openstack-ansible/etc/openstack_deploy`` directory to the
|
|
``/etc/openstack_deploy`` directory.
|
|
|
|
#. Change to the ``/etc/openstack_deploy`` directory.
|
|
|
|
#. Copy the ``openstack_user_config.yml.example`` file to
|
|
``/etc/openstack_deploy/openstack_user_config.yml``.
|
|
|
|
#. Review the ``openstack_user_config.yml`` file and make changes
|
|
to the deployment of your OpenStack environment.
|
|
|
|
.. note::
|
|
|
|
The file is heavily commented with details about the various options.
|
|
See :ref:`openstack-user-config-reference` for more details.
|
|
|
|
The configuration in the ``openstack_user_config.yml`` file defines which hosts
|
|
run the containers and services deployed by OpenStack-Ansible. For
|
|
example, hosts listed in the ``shared-infra_hosts`` section run containers for
|
|
many of the shared services that your OpenStack environment requires. Some of
|
|
these services include databases, Memcached, and RabbitMQ. Several other
|
|
host types contain other types of containers, and all of these are listed
|
|
in the ``openstack_user_config.yml`` file.
|
|
|
|
Some services, such as glance, heat, horizon and nova-infra, are not listed
|
|
individually in the example file as they are contained in the os-infra hosts.
|
|
You can specify image-hosts or dashboard-hosts if you want to scale out in a
|
|
specific manner.
|
|
|
|
For examples, please see :ref:`test-environment-config`,
|
|
:ref:`production-environment-config`, and :ref:`pod-environment-config`
|
|
|
|
For details about how the inventory is generated from the environment
|
|
configuration, see
|
|
`developer-inventory <http://docs.openstack.org/developer/openstack-ansible/developer-docs/inventory.html>`_.
|
|
|
|
For details about how variable precedence works, and how to override
|
|
group vars, see
|
|
`developer-inventory-and-vars <http://docs.openstack.org/developer/openstack-ansible/developer-docs/inventory-and-vars.html>`_.
|
|
|
|
Installing additional services
|
|
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
|
|
|
To install additional services, the files in
|
|
``/etc/openstack_deploy/conf.d`` provide examples showing
|
|
the correct host groups to use. To add another service, add the host group,
|
|
allocate hosts to it, and then execute the playbooks.
|
|
|
|
Advanced service configuration
|
|
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
|
|
|
OpenStack-Ansible has many options that you can use for the advanced
|
|
configuration of services. Each role's documentation provides information
|
|
about the available options.
|
|
|
|
Infrastructure service roles
|
|
----------------------------
|
|
|
|
- :role_docs:`galera_server`
|
|
|
|
- :role_docs:`haproxy_server`
|
|
|
|
- :role_docs:`memcached_server`
|
|
|
|
- :role_docs:`rabbitmq_server`
|
|
|
|
- :role_docs:`repo_build`
|
|
|
|
- :role_docs:`repo_server`
|
|
|
|
- :role_docs:`rsyslog_server`
|
|
|
|
|
|
OpenStack service roles
|
|
-----------------------
|
|
|
|
- :role_docs:`os_aodh`
|
|
|
|
- :role_docs:`os_barbican`
|
|
|
|
- :role_docs:`os_ceilometer`
|
|
|
|
- :role_docs:`os_cinder`
|
|
|
|
- :role_docs:`os_designate`
|
|
|
|
- :role_docs:`os_glance`
|
|
|
|
- :role_docs:`os_gnocchi`
|
|
|
|
- :role_docs:`os_heat`
|
|
|
|
- :role_docs:`os_horizon`
|
|
|
|
- :role_docs:`os_ironic`
|
|
|
|
- :role_docs:`os_keystone`
|
|
|
|
- :role_docs:`os_magnum`
|
|
|
|
- :role_docs:`os_neutron`
|
|
|
|
- :role_docs:`os_nova`
|
|
|
|
- :role_docs:`os_rally`
|
|
|
|
- :role_docs:`os_sahara`
|
|
|
|
- :role_docs:`os_swift`
|
|
|
|
- :role_docs:`os_tempest`
|
|
|
|
- :role_docs:`os_trove`
|
|
|
|
|
|
Other roles
|
|
-----------
|
|
|
|
- :role_docs:`apt_package_pinning`
|
|
|
|
- :role_docs:`ceph_client`
|
|
|
|
- :role_docs:`galera_client`
|
|
|
|
- :role_docs:`lxc_container_create`
|
|
|
|
- :role_docs:`lxc_hosts`
|
|
|
|
- :role_docs:`pip_install`
|
|
|
|
- :role_docs:`plugins`
|
|
|
|
- :role_docs:`openstack_hosts`
|
|
|
|
- :role_docs:`openstack_openrc`
|
|
|
|
- :role_docs:`rsyslog_client`
|
|
|
|
Configuring service credentials
|
|
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
|
|
|
Configure credentials for each service in the
|
|
``/etc/openstack_deploy/*_secrets.yml`` files. Consider using the
|
|
`Ansible Vault <http://docs.ansible.com/playbooks_vault.html>`_ feature to
|
|
increase security by encrypting any files that contain credentials.
|
|
|
|
Adjust permissions on these files to restrict access by nonprivileged
|
|
users.
|
|
|
|
The ``keystone_auth_admin_password`` option configures the ``admin`` tenant
|
|
password for both the OpenStack API and Dashboard access.
|
|
|
|
We recommend that you use the ``pw-token-gen.py`` script to generate random
|
|
values for the variables in each file that contains service credentials:
|
|
|
|
.. code-block:: shell-session
|
|
|
|
# cd /opt/openstack-ansible
|
|
# ./scripts/pw-token-gen.py --file /etc/openstack_deploy/user_secrets.yml
|
|
|
|
To regenerate existing passwords, add the ``--regen`` flag.
|
|
|
|
.. warning::
|
|
|
|
The playbooks do not currently manage changing passwords in an existing
|
|
environment. Changing passwords and rerunning the playbooks will fail
|
|
and might break your OpenStack environment.
|