An OpenFlow controller that acts as a hypervisor/proxy between network switches and multiple controllers, enabling network slicing.
FlowVisor is an OpenFlow controller that acts as a hypervisor or proxy between network switches and multiple OpenFlow controllers. It enables network slicing by allowing different controllers to manage isolated segments of the same physical network infrastructure simultaneously, effectively virtualizing network resources for software-defined networking environments.
Network engineers and researchers working with software-defined networking (SDN) who need to virtualize network infrastructure or run multiple network controllers on shared physical switches.
FlowVisor provides a unique network virtualization layer that enables true network slicing without requiring switch modifications, allowing multiple OpenFlow controllers to operate independently on the same physical infrastructure while maintaining isolation and control.
FlowVisor - A network hypervisor
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Enables multiple controllers to manage isolated segments of the same physical switches, as described in its hypervisor functionality for virtualizing network resources.
Works with any OpenFlow switch and controller, ensuring compatibility without requiring switch modifications, as highlighted in its protocol adherence.
Provides tools like fvctl and APIs for control and visibility over network slices, mentioned in the documentation for easy management.
Allows parallel experimentation on shared infrastructure, making it ideal for SDN research and educational environments, as indicated in its best-use cases.
Setup requires consulting multiple sources (INSTALL file, website, manpages), which can be confusing and time-consuming for new users.
Does not support other SDN or legacy protocols, restricting its use to pure OpenFlow environments and limiting broader network integration.
The proxy layer between switches and controllers introduces latency and processing delays, potentially affecting high-throughput or latency-sensitive applications.