On Thu, Apr 28, 2022 at 4:31 AM Marcos Dione <[email protected]> wrote: > > On 4/27/22 20:10, Ihar Hrachyshka wrote: > > On Mon, Apr 25, 2022 at 7:52 AM Marcos Dione via discuss > >> Why do I have to go all the way down to OVS to create (another?) > >> port with the same > >> MAC addr than the port I created at the OVN level? And similarly, why do I > >> have to assign > >> the _same_ IP to the external interface on the host? > > > > OVN does not create interfaces, it sets up interfaces created > > elsewhere. (e.g. by your CMS, cloud / container management system). > > But in this case it's me with my own hands who's doing it. > > > When you create a ovs port, you establish a link between the ovs port > > and OVN port entity in db through the external_ids:iface-id attribute. > > I thought that OVN would do that for me when it translates things > from the > North DB to the South DB. So CMSs must not only modify OVN but also OVS?
Yes. E.g. in OpenStack, Neutron OVN driver will create logical ports in OVN north db, then Nova (Compute) service, via os-vif library, will also create OVS interfaces on a desired chassis. Then OVN controller that is running on the chassis detects the OVS interface with the correct iface-id and proceeds with flow configuration. > > >> Where it the documentation for the capabilities of this DHCP > >> server; > > > > You can check ovn-nb(5), e.g. here: > > https://man7.org/linux/man-pages/man5/ovn-nb.5.html > > > > Search for "IPv4 DHCP Options". This will allow you to set router and > > dns_server options for native DHCPv4 replies. > > Excelent, thanks. Cheers, > > -- > Marcos Dione | Engineering EMEA - Installer > Phone: +33 6 24 21 59 91 > Zoom: 261-124-4701 > https://cloudian.com/ > _______________________________________________ discuss mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
