Hi Numan, Provider VLAN networks is able to connect VM and BMS on L2. I am going to push this topic further.
Provider VLAN network is different from regular virtual network. It seems that I can't create a logical router to connect a provider VLAN and regular VN. The way I am using provider VLAN is as external network whose GW is on physical router. Also in a multi-tenancy cloud, provider VLAN network can't be created by user. I wonder if we can build a regular VN to connect VM and BMS? OVN is using Geneve which is not commonly supported by networking devices. VxLAN doesn't seem to be an option cause OVN needs Geneve to carry metadata. I see some vxlan supports in OVN but not sure how it works or for which case exactly. Tungsten Fabric supports this because it uses vxlan as the overlay. To connect VM to BMS, vrouter will create a vxlan from compute node to BMS VTEP (typically the ToR). That's how BMS is brought into overlay by vxlan, and will be treated just like a VM. With the EVPN support in control plane, routing info is populated between vrouter and VTEPand. And with some orchestration to networking devices, the networking support to BMS is seamless. One concern is that no SG for BMS, which can be actually supported by networking device. Can the similar supported by OVN or any other overlay solution supported by OVN to connect BMS? Thanks! Tony ________________________________________ From: Numan Siddique <[email protected]> Sent: May 18, 2023 11:18 AM To: Tony Liu Cc: ovs-dev; ovs-discuss Subject: Re: [ovs-discuss] [ovs-dev] connect VM on OVN/OVS and BMS on L2 On Thu, May 18, 2023, 1:15 PM Tony Liu via discuss <[email protected]<mailto:[email protected]>> wrote: Hi Numan, Good to see you pick it up, no need to bother OpenStack alias. My ultimate target is to support VM and BMS L2 connectivity with OpenStack. I used to make that work with other virtual networking stack, not sure how much it's supported by OVN/OVS. Any comments in that context It is definitely supported with open stack. I think you need to create a provider vlan neutron network. Thanks Numan Thanks! Tony ________________________________________ From: Numan Siddique <[email protected]<mailto:[email protected]>> Sent: May 18, 2023 09:51 AM To: Tony Liu Cc: ovs-discuss; ovs-dev Subject: Re: [ovs-dev] connect VM on OVN/OVS and BMS on L2 On Thu, May 18, 2023 at 12:19 PM Tony Liu <[email protected]<mailto:[email protected]>> wrote: > > Hi, > > Could you anyone share experiences or point to some reference about how > to connect VM on OVN/OVS and BMS on L2? Or say, how can I connect BMS > to a logical switch on OVN/OVS? For this you need to create a localnet port in the logical switch. Something like this: ovn-nbctl ls-add public # localnet port ovn-nbctl lsp-add public ln-public ovn-nbctl lsp-set-type ln-public localnet ovn-nbctl lsp-set-addresses ln-public unknown ovn-nbctl lsp-set-options ln-public network_name=public # create a few VM ports ovn-nbctl lsp-add public pub-port1 ovn-nbctl lsp-set-addresses pub-port1 "50:54:00:00:00:03 172.168.0.100" (assuming your L2 network is 172.168.0.0/24<http://172.168.0.0/24>) ovn-nbctl lsp-add public pub-port2 ovn-nbctl lsp-set-addresses pub-port2 "50:54:00:00:00:04 172.168.0.101" # On the compute node(s) where you create the VMs ovs-vsctl set open . external_ids:ovn-bridge-mappings="public:br-ex" ovs-vsctl add-br br-ex ovs-vsctl add-port eth1 # assuming eth1 is your physical interface connecting to your L2 switch After this connectivity from your VM (bound to logical port pub-port1) should be able to communicate to your BMS. Thanks Numan > > > Thanks! > Tony > _______________________________________________ > dev mailing list > [email protected]<mailto:[email protected]> > https://mail.openvswitch.org/mailman/listinfo/ovs-dev > _______________________________________________ discuss mailing list [email protected]<mailto:[email protected]> https://mail.openvswitch.org/mailman/listinfo/ovs-discuss _______________________________________________ dev mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-dev
