In cases when SSH and mgmt networks are different, it might be important
to have valid management_address that services are relying on when
listening on interfaces. At the moment for bare metal hosts
management_address will be equal to ansible_host which leads to
unpredictable behaviour under some scenarios. With management_ip we allow
to define another IP address that will be used as container/management
address for bare metal host, while `ip` will still represent
ansible_host.
Reviewed: https:/ /review. opendev. org/c/openstack /openstack- ansible/ +/870113 /opendev. org/openstack/ openstack- ansible/ commit/ c8ecc9fa10dea22 2f928cbdc1fb090 adebe28b81
Committed: https:/
Submitter: "Zuul (22348)"
Branch: master
commit c8ecc9fa10dea22 2f928cbdc1fb090 adebe28b81
Author: Dmitriy Rabotyagov <email address hidden>
Date: Fri Jan 13 18:27:52 2023 +0100
Add management_ip option for metal hosts
In cases when SSH and mgmt networks are different, it might be important address will be equal to ansible_host which leads to management
to have valid management_address that services are relying on when
listening on interfaces. At the moment for bare metal hosts
management_
unpredictable behaviour under some scenarios. With management_ip we allow
to define another IP address that will be used as container/
address for bare metal host, while `ip` will still represent
ansible_host.
Related-Bug: #2002645 85b9ea520021f9e ea6f5850341
Change-Id: I3152ae7985319e