[baremetal] Fix: wrong nic name idf index 97/51497/1
authorGuillermo Herrero <guillermo.herrero@enea.com>
Fri, 2 Feb 2018 14:43:56 +0000 (15:43 +0100)
committerGuillermo Herrero <guillermo.herrero@enea.com>
Fri, 2 Feb 2018 14:43:56 +0000 (15:43 +0100)
commit378b4a72c27c941d5e37216edb23f224fbb58e26
tree8d6e2f8a74d306d9c2dbf93ae499ba470d34f24e
parent252fd2b6fe32a77a4014ce33ead9f77817b1d2c9
[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>
mcp/reclass/classes/cluster/baremetal-mcp-pike-odl-ha/openstack/compute_pdf.yml.j2
mcp/reclass/classes/cluster/baremetal-mcp-pike-ovs-ha/openstack/compute_pdf.yml.j2