[ovs-dev] Bug#757761: openvswitch-switch: Please include ovsk-controller
dariusz.dwornikowski at cs.put.poznan.pl
Mon Aug 11 18:17:19 UTC 2014
-----BEGIN PGP SIGNED MESSAGE-----
On 11.08.2014 17:38, Ben Pfaff wrote:
> On Mon, Aug 11, 2014 at 09:53:09AM +0200, Dariusz Dwornikowski
>> 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
>> Ovsk starting from version 2.1 ships ovsk-controller as
>> test-controller and resides in tests/ directory of the main
>>> From the NEWS of ovsk source:
>> - ovs-controller has been renamed test-controller. It is no
>> longer packaged or installed by default, because too many users
>> assumed incorrectly that ovs-controller was a necessary or
>> desirable part of an Open vSwitch deployment.
> Why do you keep referring to ovs as ovsk? We have never shipped
> anything under that name.
Forgive me for that, it is just a silly mistake on my side.
> 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.
Institute of Computing Science, Poznań University of Technology
room 2.7.2 BTiCW | tel. +48 61 665 29 41
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
-----END PGP SIGNATURE-----
More information about the dev