Hi Moshe, I'm not aware of any mechanism drivers that actually create the VTEP (that will be a manual step,) but there are drivers that support Hierarchical Port Binding [1]. The networking-arista mechanism driver [2] is one such driver, but there are others. Such drivers will configure a VLAN to VNI mapping on switches based on the segmentation IDs of the neutron network segments bound at each port binding level. In such a deployment, you'd create a VXLAN network in neutron. You could then launch a baremetal instance on that network. The mechanism driver will then be responsible for dynamically allocating a VLAN for the baremetal<->TOR switch segment and mapping that VLAN to the VXLAN network's VNI on the TOR switch such that the baremetal instance is connected to the VXLAN fabric segment. [1] https://specs.openstack.org/openstack/neutron-specs/ specs/kilo/ml2-hierarchical-port-binding.html [2] https://github.com/openstack/networking-arista On Wed, Feb 7, 2018 at 10:06 PM, Moshe Levi <moshele at mellanox.com> wrote: > Hi all, > > > > Ironic supports mutli tenancy for quite few releases and according to the > spec [1] it can work with vlan/vxlan networks. > > I see lot of mechanism driver that support vlan network such as [2] and > [3] , but I didn't find any mechanism driver that work on vxlan network. > > Is there a mechanism driver that can configure vtep on a switch exist for > the bare metal? > > > > Help would be appreciated > > > > > > [1] https://specs.openstack.org/openstack/ironic-specs/specs/ > not-implemented/ironic-ml2-integration.html > > [2] https://github.com/openstack/networking-arista > > [3] https://github.com/openstack/networking-generic-switch > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20180208/56adea16/attachment-0002.html>