Oh no, you're thinking, yet another cookie pop-up. Well, sorry, it's the law. We measure how many people read us, and ensure you see relevant ads, by storing cookies on your device. If you're cool with that, hit “Accept all Cookies”. For more info and to customize your settings, hit “Customize Settings”.

Review and manage your consent

Here's an overview of our use of cookies, similar technologies and how to manage them. You can also change your choices at any time, by hitting the “Your Consent Options” link on the site's footer.

Manage Cookie Preferences
  • These cookies are strictly necessary so that you can navigate the site as normal and use all features. Without these cookies we cannot provide you with the service that you expect.

  • These cookies are used to make advertising messages more relevant to you. They perform functions like preventing the same ad from continuously reappearing, ensuring that ads are properly displayed for advertisers, and in some cases selecting advertisements that are based on your interests.

  • These cookies collect information in aggregate form to help us understand how our websites are being used. They allow us to count visits and traffic sources so that we can measure and improve the performance of our sites. If people say no to these cookies, we do not know how many people have visited and we cannot monitor performance.

See also our Cookie policy and Privacy policy.

This article is more than 1 year old

OVS to add virtual networking to code-base

Adding L2/L3 to Open vSwitch

The Open vSwitch (OVS) community has announced that it's adding virtual networking to its project.

As explained in this post, the Open Virtual Networking (OVN) project is designed to provide a “lightweight control plane” to support familiar virtual networking abstractions – in particular, Layer 2/3 networking only, so as not to clash with more general-purpose SDN controller capabilities.

The project will allow “users to connect groups of [virtual machines] or containers into private L2 and L3 networks, quickly, programmatically, and without the need to provision VLANs or other physical network resources,” the post claims.

The OVN architecture is explained at the OVS mailing list. OVN will use Open vSwitch, and will get its hypervisor integration from that project.

OVN will exist as a kind of overlay daemon in an OVS implementation. Configuration and state data will be stored in an OVN database, and the OpenFlow and OVSDB interfaces will be used to push that down to the OVS kernel.

The OVN database will hold information about the physical network; the logical network (including topology of logical switches and routers, ACLs, firewall rules and so on); and bindings.

The OVN project intends to write an OpenStack plugin for cloud management. The architectural description notes that there are still features in OVN that are yet to be fleshed out. ®

 

Similar topics

Similar topics

Similar topics

TIP US OFF

Send us news


Other stories you might like