[ovs-dev] Bug#757761: openvswitch-switch: Please include ovsk-controller
blp at nicira.com
Mon Aug 11 21:28:31 UTC 2014
On Mon, Aug 11, 2014 at 08:17:19PM +0200, Dariusz Dwornikowski wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
> On 11.08.2014 17:38, Ben Pfaff wrote:
> > On Mon, Aug 11, 2014 at 09:53:09AM +0200, Dariusz Dwornikowski
> > wrote:
> >> Source: openvswitch Severity: wishlist
> >> Dear Maintainer,
> >> Tomasz Buchert and I are working on introducing mininet, an SDN
> >> emulator (http://mininet.org/) to Debian. Mininet heavily depends
> >> on ovsk to provide OpenFlow switch but also an OpenFlow
> >> controller.
> >> Ovsk starting from version 2.1 ships ovsk-controller as
> >> test-controller and resides in tests/ directory of the main
> >> source.
> > Why can't mininet use a real controller instead of the useless
> > test program from OVS?
> Mininet is just an emulator, using test controller from OVS makes it
> easy to start with and use by people who start with OpenFlow and SDNs.
> Using an OVS controller is one of the major options in mininet, and in
> fact the default behavior. You can always use external controller with
> - --remote option in mininet.
> If we ship mininet package without having OVS controller to use, we
> will be shipping partially unusable software.
I don't understand why the OVS controller is useful. OVS has a larger
set of features, and performs better, with no controller, than it does
with the test-controller. Why do mininet users want to use
ovs-controller instead of no controller at all?
More information about the dev