[ha] Fix tenant NIC OS config for VLAN ranges 99/56199/1
authorAlexandru Avadanii <Alexandru.Avadanii@enea.com>
Sun, 22 Apr 2018 00:07:27 +0000 (02:07 +0200)
committerAlexandru Avadanii <Alexandru.Avadanii@enea.com>
Sun, 22 Apr 2018 00:07:27 +0000 (02:07 +0200)
commitcfc5988be48d1317244e71fd7919480db18745d4
treef23765b7b6318a4b3eb87039a3e2822f1ee3e394
parented7bb355c93af5c163d5ae7926012652021abf75
[ha] Fix tenant NIC OS config for VLAN ranges

Previous commits added support for tenant VLAN range parametrization,
yet failed to accomodate the new VLAN range representation ('M:N') in
existing `linux.network.interfaces` reclass configuration.

This lead to the silent removal of <nic_private>.<vlan_private> from
interfaces file and for `br-mesh` to try to use <nic_private> instead
of <nic_private>.<vlan_private>, conflicting with `br-floating`.

Stick to using the first VLAN in the tenant range.

JIRA: FUEL-365

Change-Id: I88f7263159f1742dba3b6e36649c9344f2932c5f
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
mcp/reclass/classes/cluster/mcp-pike-odl-ha/openstack/compute_pdf.yml.j2
mcp/reclass/classes/cluster/mcp-pike-ovn-ha/openstack/compute_pdf.yml.j2
mcp/reclass/classes/cluster/mcp-pike-ovs-ha/openstack/compute_pdf.yml.j2