Following up on the discussion: Attendees: - Moshe Levi - Nate Johnston - Davidsha - Miguel - Adrian Chirls - Julia Kreger Notes from meeting: - NOTE: The discussions largely focused on the "local" execution on the smartnic case. The remote case is still under discussion but is not blocking to the overall effort. - We will create a new vnic binding type, as to not break baremetal port binding logic that already exists. Smartnics are viewed a separate path of logic that needs to be taken. If hierarchical port binding is needed, the logic will need to be updated at a later point in time. - The binding profile information to be transmitted from ironic to neutron to contain information about the smartnic. No manual port/smartnic mapping file will be added. - There will be no implicit mapping of ironic port.uuid to hostname on the operating smartnic. - Consensus was that the operators should supply the sufficient information to ironic for neutron to relate the smartnic (with the data sent in binding_profile) to the vif and the baremetal port. - Neutron OVS agent will perform the actual final port-plug using os-vif as compared to the current virtualization use case or the existing baremetal vnic use case. On Mon, Dec 10, 2018 at 12:34 PM Moshe Levi <moshele@mellanox.com> wrote:
Hi all,
We started working on specs to support baremetal with smart-nic see [1] and [2].
There are some open issue and different approaches that require further discussion see [3].
To resolve them I would like to propose a meeting tomorrow , December 11th, at 15:00 UTC. For those of you interested in joining please use [4] to connect.
[1] - https://review.openstack.org/#/c/582767/
[2] - https://review.openstack.org/#/c/619920/
[3] - https://etherpad.openstack.org/p/BER-ironic-smartnics
[4] - https://bluejeans.com/u/jkreger
Thanks,
Moshe (moshele)