——————————
Floodlight controller and its Quantum plug-in have a very long way to go before I’d use them in a production environment:
The Floodlight controller is a single point of failure (there’s no provision for a redundant controller);
Unless I can’t read Java code (which wouldn’t surprise me at all), the VirtualNetworkFilter stores all mappings (including MAC membership information) in in-memory structures that are lost if the controller or the server on which it runs crashes;
As mentioned above, per-flow entries used by Floodlight controller don’t scale at all (more about that in an upcoming post).
The whole thing is thus a nice proof-of-concept tool that will require significant efforts (probably including a major rewrite of the forwarding module) before it becomes production-ready.
为啥symantec在胶片中打酱油?
Very interesting comments from:
http://blog.ioshints.info/2012/08/openstackquantum-sdn-based-virtual.html
——————————
Floodlight controller and its Quantum plug-in have a very long way to go before I’d use them in a production environment:
The Floodlight controller is a single point of failure (there’s no provision for a redundant controller);
Unless I can’t read Java code (which wouldn’t surprise me at all), the VirtualNetworkFilter stores all mappings (including MAC membership information) in in-memory structures that are lost if the controller or the server on which it runs crashes;
As mentioned above, per-flow entries used by Floodlight controller don’t scale at all (more about that in an upcoming post).
The whole thing is thus a nice proof-of-concept tool that will require significant efforts (probably including a major rewrite of the forwarding module) before it becomes production-ready.