openstack-ansible-os_nova/README.rst
Steve Lewis 4310931756 Configure DB addresses for each service
To enable partitioning of DB traffic by-service, each service needs to
use a custom connection string. Defaulting the service address to a
common galera_address makes things continue to work by default.

While the galera_address could be overridden on a container or host
basis this requires repeating that behavior across each infra node in
the inventory. Providing service-specific connection address variables
simplifies the management somewhat for large deployments and may reduce
error rates.

The service install playbooks now default the service-specific variables
instead of galera_address to the internal lb vip from inventory to
maintain the ease-of-use currently available.

Any value for a service-specific variable set in user_variables.yml will
override the value in the playbook's vars to provide selective
customization as needed.

Change-Id: I4c98bf906a0c1cb11ddd41277a855dce22ff646a
Closes-Bug: 1462529
2015-06-10 02:07:38 +00:00

28 lines
615 B
ReStructuredText

OpenStack nova
##############
:tags: openstack, nova, cloud, ansible
:category: \*nix
Role for deployment, setup and installation of nova.
This role will install the following:
* nova-consoleauth
* nova-conductor
* nova-compute
* nova-cert
* nova-api-metadata
* nova-spicehtml5proxy
* nova-api-ec2
* nova-api-os-compute
* nova-api-ec2
.. code-block:: yaml
- name: Installation and setup of Nova
hosts: nova_all
user: root
roles:
- { role: "os_nova", tags: [ "os-nova" ] }
vars:
nova_galera_address: "{{ internal_lb_vip_address }}"