mininet - What alternatives SDN controllers to POX are available? -
i advice best open-source sdn controller available. want implement , test ideas have in research need use simulation such mininet. in fact, familiar mininet , able deal it. however, mininet uses pox controller bit tedious , not user friendly when comes manage network topology , modify flows, becomes hard task since need hard code scratch ( beginner in python well). there user-friendly sdn controller can use instead pox? i've tried floodlight , opendaylight there not ready , involves many bugs.
thank you.
it began nox. while might argue, nox first openflow controller attracted whole lot of researchers around , achieved have wide acceptance. majority of primary software-defined networking (sdn) , openflow papers , applications implemented on top of nox. google used nox build (prototype?) own distributed openflow controller, called onix. being said, fuss left in 2010. on nox mailing-lists abandoned , no major changes know of introduced code base.
pox calls younger sibling of nox. (they both managed/maintained same team/organization.) personal belief pox more or less motivated purpose of creating developer-friendly openflow controller successor nox. openflow newcomers directed either pox or floodlight. hence, no surprise has pretty active mailing list. pox provides limited web api (via json-rpc) , moderate sized collection of manuals on wiki. written in python , provides decent python api pythonistas out there. due python being interpreted language, pox cuts down time spent in develop-and-deploy cycle, particularly compared c++ based nox. further, in addition supporting nox gui, pox provides web-based gui.
to sum up, beacon provides compact , expressive code base , works flawlessly. being said, eclipse , osgi dependency kills me , supporting star topologies (that is, topologies without loops) constraining. if give beacon try, recommend evaluate floodlight instead.
floodlight has unquestionably active , responsive community among f/oss openflow softwares. majority of floodlight developers working in bigswitch networks directly participate in mailing-lists. can find discussing issue actual developer(s) of particular module. have never witnessed neither unanswered question, nor unresolved problem. supportive , active community. floodlight exposes of functionality through rest api , there exists many handy utilities common tasks such static routes , end-to-end route (circuit) pushes. floodlight has web-based ui (contributed wes felter) , java-based gui, called avior, contributed jason parraga. 1 of kind, floodlight can run network backend openstack using quantum plug-in. finally, documented controller project out there in ecosystem.
ryu component-based software defined networking framework. ryu provides software components defined api make easy developers create new network management , control applications. ryu supports various protocols managing network devices, such openflow, netconf, of-config, etc. openflow, ryu supports 1.0, 1.2, 1.3, 1.4, 1.5 , nicira extensions. of code freely available under apache 2.0 license. **
the onos (open network operating system) project open source community hosted linux foundation. goal of project create software-defined networking (sdn) operating system communications service providers designed scalability, high performance , high availability.
the opendaylight project collaborative open source project hosted linux foundation. goal of project accelerate adoption of software-defined networking (sdn) , create solid foundation network functions virtualization (nfv). software written in java.
Comments
Post a Comment