There is no way to specify which port use for which network

[George Shuklin]

Baremetal server has two ports. Each port leads to separate hardware switch (defined by local_link_connection/switch_info).

When nova instance is booted with two nics, pointing to different networks, it randomly assign each (ironic) port to each networking.

Baremetal server:

NIC1 leads to switch sw-1 port 1/1/1
NIC2 leads to switch sw-2 port 2/2/2

switch sw-1 serves net-1
switch sw-2 serves net-2

server is booted with --nic net-id=uuid-of-net-1 --nic net-id=uuid-of-net-2

Run1:

NIC1 pointing to sw-1 port 1/1/1 and configured to serve net1
NIC2 pointing to sw-2 port 2/2/2 and configured to serve net2

Run2:

NIC1 pointing to sw-2 port 2/2/2 and configured to serve net1
NIC2 pointing to sw-1 port 1/1/1 and configured to serve net2

This creates chaos if sw-1 is 'internet' switch and sw-2 is 'local DMZ switch'. sw-2 can not serve internet vlans, and sw-1 can not serve local network vlans.

Ironic version: newton (6.2.1)

[George Shuklin (george-shuklin)]

An excerpt from IRC discussion:

Ironic should add physical_network attribute to local_link_connection and take it in account when selecting which baremetal nic goes to which network.

[Seamanhanshan (yaojun)]

Just as your case shows, if server is booted with only nic --nic net-id=uuid-of-net-1, the result is also random.

[Seamanhanshan (yaojun)]

Update #2, the correct result is always choose first port not random.

[Vladyslav Drok (vdrok)]

Marked as duplicate, as that other bug already has a spec.