aboutsummaryrefslogtreecommitdiffstats
path: root/mcp/config/states/maas
diff options
context:
space:
mode:
authorAlexandru Avadanii <Alexandru.Avadanii@enea.com>2017-08-21 22:26:09 +0200
committerAlexandru Avadanii <Alexandru.Avadanii@enea.com>2017-08-21 22:30:41 +0200
commitfd1830cbc79de49be70cc4fe7c3b57559b47c8d9 (patch)
tree742a2aaed17e1b08b91dc5ffdb4e4ee95f25bac9 /mcp/config/states/maas
parentb24bbb99bdf5c09273e360aabf85b2c84573326e (diff)
reclass: baremetal: openstack: Fix eth assignment
Baremetal support introduced a couple of VCP VMs, which have 2 network interfaces: - primary (ens3 inside x86 VM) - connected to "br-mgmt" bridge on each kvm node, serves for MaaS DHCP / connection to salt master; - secondary (ens4 inside x86 VM) - connected to "br-ctl" bridge on each kvm node, serves for Openstack Management network; However, the reclass model was configured to use a single IP address on the primary interface, breaking the connnection to salt master, while also not connecting the Openstack Management network properly. Fix this by configuring the primary interface for DHCP, while the secondary gets a static IP in Openstack Management network. Change-Id: I9f1d6f080e882bfaae7b5f209bc3c5536826ba06 Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
Diffstat (limited to 'mcp/config/states/maas')
0 files changed, 0 insertions, 0 deletions