f4510b6baa
These addresses are given defaults of 0.0.0.0 in the role defaults but in a deployment we know which address each service should bind to. The variable container_address should hold the local mgmt network IP address for either containerised or metal deployments. This patch defines a new variable management_address which removes confusion about container_address for metal deployments, and overrides the role default bind addresses for all roles. Depends-On: https://review.opendev.org/753638 Change-Id: I7471ff1da9602f67134e217f5427e492fa7a7814
21 lines
1.0 KiB
YAML
21 lines
1.0 KiB
YAML
---
|
|
features:
|
|
- |
|
|
Openstack services and infrastructure such as galera, rabbitmq
|
|
and memcached already have defaults in their ansible roles to control the
|
|
IP address which those services bind to. Prior to this release the default
|
|
of 0.0.0.0 was used. A global setting in the openstack-ansible group
|
|
variables now overrides those default bind address to be the local address
|
|
on the openstack management network (typically br-mgmt) for the relevant
|
|
host or container.
|
|
upgrade:
|
|
- |
|
|
The default bind address for all openstack services and infrastructure
|
|
services such as galera, rabbitmq and memcached has changed from 0.0.0.0
|
|
to the IP address of the openstack mangement network on the relevent host
|
|
or container. Deployers should ensure that any additional systems that
|
|
expect to communicate with internal components of their openstack-ansible
|
|
deployment do so over the managment network. Services which are bound to
|
|
the management network IP will not be accessible via other interfaces.
|
|
|