Announcement

Collapse
No announcement yet.

NetworkManager Adds In Open vSwitch Support

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • NetworkManager Adds In Open vSwitch Support

    Phoronix: NetworkManager Adds In Open vSwitch Support

    Red Hat has integrated initial support for Open vSwitch within NetworkManager...

    http://www.phoronix.com/scan.php?pag...r-Open-vSwitch

  • #2
    Hello, author of said code here.

    Please note that we *are* supporting the Bond or VLAN functionality -- we're just not pretending (unlike ovs-vsctl) OpenVSwitch VLANs and Bonds are anything else than specially configured Ports. In general, ovs-vsctl, the OpenVSwitch's native command line functionality, goes into great lengths while abstracting what is actually configured in the configuration database. We provide somewhat more low-level interface.

    Why are we doing this is that we aim to provide a more unified interface to network management to remove the burden from other tools that have their network configuration needs. (Hello RHEV!) At this point we expect other tools to use this, not users directly. Even though it's certainly useful for other use cases, just might need some polish.

    Cheers,
    Lubo

    Comment


    • #3
      That's great, I haven't used network manager in a long time but at times it would be easier with a GUI then remembering all the bridge commands for adding vlan or making trunks etc.

      Comment


      • #4
        Originally posted by lkundrak View Post
        Hello, author of said code here.

        Please note that we *are* supporting the Bond or VLAN functionality -- we're just not pretending (unlike ovs-vsctl) OpenVSwitch VLANs and Bonds are anything else than specially configured Ports. In general, ovs-vsctl, the OpenVSwitch's native command line functionality, goes into great lengths while abstracting what is actually configured in the configuration database. We provide somewhat more low-level interface.

        Why are we doing this is that we aim to provide a more unified interface to network management to remove the burden from other tools that have their network configuration needs. (Hello RHEV!) At this point we expect other tools to use this, not users directly. Even though it's certainly useful for other use cases, just might need some polish.

        Cheers,
        Lubo
        TYVM for your work, this looks like a great addition, can't wait to test it on Arch when it lands

        Comment


        • #5
          Originally posted by lkundrak View Post
          Hello, author of said code here.

          Please note that we *are* supporting the Bond or VLAN functionality -- we're just not pretending (unlike ovs-vsctl) OpenVSwitch VLANs and Bonds are anything else than specially configured Ports. In general, ovs-vsctl, the OpenVSwitch's native command line functionality, goes into great lengths while abstracting what is actually configured in the configuration database. We provide somewhat more low-level interface.

          Why are we doing this is that we aim to provide a more unified interface to network management to remove the burden from other tools that have their network configuration needs. (Hello RHEV!) At this point we expect other tools to use this, not users directly. Even though it's certainly useful for other use cases, just might need some polish.

          Cheers,
          Lubo
          Nice work!

          As a cheeky request - It'd be a very nice user experience (for a non networking type, i.e. me) for a point and click LAG/LACP setup. please and thank you!

          Comment

          Working...
          X