31f12f54ea
For couple of cycles we include our systemd-related roles in openstack_hosts role, with purpose of operators being able to configure their nodes before any actuall service or infra role will kick in. This should also provide ability to configure networking for LXC and setup overall. So with moving systemd role includes during AIO setup to variables which leverage openstack_hosts behavior we achieve multiple goals at once: - Reduce amount of intersecting logic in AIO bootstrap - Add testing for openstack_hosts section and ensure it's functional - Improve transparency for deployers and ability to see and change network configuration, as it will be templated as variables file instead of be directly applied. As a consequence, we need to access host by it's already established IP address, rather then one defined by us. However, we already require having `bootstrap_host_public_address` and rely on it heavily, so it should not bring much regressions with the approach. Depends-On: https://review.opendev.org/c/openstack/openstack-ansible-haproxy_server/+/953670 Depends-On: https://review.opendev.org/c/openstack/openstack-ansible/+/954316 Change-Id: Ib688a5a758ec5ebbd0ebafdcaf2b27aeecdd9aba Signed-off-by: Dmitriy Rabotyagov <dmitriy.rabotyagov@cleura.com>
11 lines
273 B
Plaintext
11 lines
273 B
Plaintext
---
|
|
masakari-infra_hosts:
|
|
aio1:
|
|
ip: {{ bootstrap_host_public_address }}
|
|
management_ip: {{ bootstrap_host_management_address }}
|
|
|
|
masakari-monitor_hosts:
|
|
aio1:
|
|
ip: {{ bootstrap_host_public_address }}
|
|
management_ip: {{ bootstrap_host_management_address }}
|