[baremetal] Fix: wrong nic name idf index 73/52273/1
authorGuillermo Herrero <guillermo.herrero@enea.com>
Fri, 2 Feb 2018 14:43:56 +0000 (15:43 +0100)
committerAlexandru Avadanii <Alexandru.Avadanii@enea.com>
Sat, 17 Feb 2018 02:03:21 +0000 (03:03 +0100)
commit7a464cc994463231bb7d5dfbc9a29bcfcea5bbdb
tree31b8cde10575a2e7981e31443dfea607c24ba34e
parent380b7375c8be9f05277c6f991ba70801985ca8fa
[baremetal] Fix: wrong nic name idf index

This was only affecting pod deployments with
different board models, under the current limited
support:
- 3 KVMs will be same model and have the same NIC names
- 2 Compute nodes will be the same model and have same NIC names

For the computes nodes, br-mesh NIC name was wrong due
to incorrect idf mapping

Change-Id: I9685b35cb23b03be9fc0e6fe16c0712a9ad70e19
Signed-off-by: Guillermo Herrero <guillermo.herrero@enea.com>
(cherry picked from commit 378b4a72c27c941d5e37216edb23f224fbb58e26)
mcp/reclass/classes/cluster/baremetal-mcp-ocata-odl-ha/openstack/compute_pdf.yml.j2
mcp/reclass/classes/cluster/baremetal-mcp-ocata-ovs-ha/openstack/compute_pdf.yml.j2