Age | Commit message (Collapse) | Author | Files | Lines |
|
When using mapping file with mac address, mapping logic will try
to fetch the mac address of the interface, which will fail. Storing
the mac address also in the DPDK mapping file so that we can satisfy
mapping logic.
Closes-Bug: #1619330
Change-Id: I92ba7f589c8d848feb083f07c3f937b50aca388e
|
|
* os-net-config is called multiple times during the deploy.
Once the interface is bound to a driver, it will not be
listed for ethtool to get the pci address, which will
through exception. Handled this exception.
* Stored the DPDK bound nic configs at '/var/lib/os-net-config/
dpdk_mappings.yaml' file to emulate the same nic numbering
after the nic has been bound to the DPDK driver.
Partial-Bug: #1619330
Change-Id: I6b1e45003f851f1fcf5b8730890c75331e8d0f8f
|
|
This way device eth10 is after eth9, and not directly after eth1
Change-Id: I81eba97cccf6c4f314f9037d16ee1f244dbade02
Closes-Bug: #1482818
|
|
Implements a new active NIC abstraction and naming convention
that allows nic1, nic2, etc. to be translated to actual (active)
network device names like em1, em2 (or eth0, eth1).
This includes some logic to map ordered active nics to the
nic1, nic2 naming scheme. Embedded nics are always listed
first (in sort order) followed by any other active Nics
on the system.
With the new code:
{"type": "interface", "name": "nic1" }
is automatically translated (internally) to:
{"type": "interface", "name": "em1" }
This works for all top level "interface" devices, vlans, bonds, and
bridges alike. For vlans the 'device' name is translated instead
of the device name per vlan object conventions.
|