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?


Thanks!
Tony
________________________________________
From: Numan Siddique <num...@ovn.org>
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 <tonyliu0...@hotmail.com> 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)

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
> d...@openvswitch.org
> https://mail.openvswitch.org/mailman/listinfo/ovs-dev
>
_______________________________________________
discuss mailing list
disc...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss

Reply via email to