f2293c5106
This change adds flag 'inventory_dhcp_static_ip' to the
deploy-nodes-dynamic role.
If set to true, it will read the new 'provisioning_ipv4_address'
key from the inventory machine section and use that as assigned
IP for the machine mac.
If set to false, dnsmasq will assign IPs from the configured DHCP
range.
An inventory machine example specifying provisioning_ipv4_address:
"compute00.hpuseast.ic.openstack.org": {
"ansible_ssh_host": "15.126.48.52",
"ipv4_address": "15.126.48.52",
"provisioning_ipv4_address": "10.23.212.5",
"uuid": "30303536-3734-5355-4532-333745314C41",
"driver_info": {
"power": {
"ipmi_address": "1.1.1.1",
"ipmi_username": "xxx"
"ipmi_password": "moarxxx"
}
}
Change-Id: I9083cd34096aad04136564c2ded024527c88c711
17 lines
621 B
YAML
17 lines
621 B
YAML
---
|
|
features:
|
|
-
|
|
The inventory_dhcp feature permits configuration
|
|
of dnsmasq to provide the IP configuration on
|
|
servers deployed by Bifrost, rather than setting
|
|
that information into the config drive.
|
|
Previously, the feature assumed the IP set by
|
|
dnsmasq was both the provisioning and the
|
|
management IP, but on some scenarios that is
|
|
not always the case.
|
|
With the inclusion of the inventory_dhcp_static_ip
|
|
option a user can provide an specific provisioning
|
|
IP via the JSON/YAML/CSV inventory in a server by
|
|
server basis, which will be used just for the
|
|
provisioning.
|