https://github.com/yeasy/lazyctrl
The code for the lazyctrl project.
https://github.com/yeasy/lazyctrl
Last synced: 4 months ago
JSON representation
The code for the lazyctrl project.
- Host: GitHub
- URL: https://github.com/yeasy/lazyctrl
- Owner: yeasy
- License: apache-2.0
- Created: 2013-09-17T02:00:58.000Z (over 11 years ago)
- Default Branch: master
- Last Pushed: 2014-09-25T14:36:41.000Z (over 10 years ago)
- Last Synced: 2025-01-03T12:22:38.239Z (5 months ago)
- Language: C
- Size: 19.6 MB
- Stars: 3
- Watchers: 4
- Forks: 1
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
The LazyCtrl Project
=================================
*A hybrid control plane design for large-scale cloud data centers.*
* Version: 0.21
* Authors: [Baohua Yang](mailto:[email protected]), [Kai Zheng](mailto:[email protected])
* Homepage:
## Download
SSH:
```
git clone [email protected]:yeasy/lazyctrl.git
```
Https:
```
git clone https://github.com/yeasy/lazyctrl.git
```
## Organization
### Central Control Modules
The directory ```ccm``` contains essential centralized control modules that are responsible for handling flow-based centralized control, as well as local control group management, for LazyCtrl.
* Central controller: Our implementation of the central controller in LazyCtrl is based on the [Floodight](http://www.projectfloodlight.org/floodlight) project, which we call ```floodlight-lc```. We extend the basic [OpenFlow 1.0](http://archive.openflow.org/documents/openflow-spec-v1.0.0.pdf) protocol in ```floodlight-lc``` by introducing a function to support installing a new action *Encap* for packet encapsulation and forwarding at edge switches. Besides, the central controller in LazyCtrl is only in charge of inter-group traffic flows.
* Switch grouping management: Some daemons are provided to maintain switch grouping and updating in the network, as well as providing communication channels between the central controller and local control groups.
* The grouping process is based on [METIS](http://glaros.dtc.umn.edu/gkhome/metis/metis/overview) project (version 5.0.2) and the gpmetis binary is suggested to be compiled on your own platform.
### Local Control Modules
All the modules for local control in switch groups are contained under directory ```lcm```. Our implementation of flow switch (called ```openvswitch-lc```) is based on the [Open vSwitch](http://openvswitch.org) project and we extend Open vSwitch by implementing the *Encap* action. Besides, the *ovsd* module in ```openvswitch-lc``` will take the charge of maintaining L-FIB and G-FIB, while the *datapath* kernel module is also modified to provide essential forwarding functions.
We also implement some agent daemons at every flow switch to report its state to the central controller.
###Others
A test platform to test the performance of the grouping algorithm, workload and packet forwarding delay in LazyCtrl.
##Installation
###Basic Requirements:
* Servers supporting [OpenvSwitch](http://openvswitch.org), e.g., most Linux based servers.
* Servers supporting [Floodlight Controller](http://www.projectfloodlight.org/floodlight), e.g., most Linux based servers.
* Servers supporting [METIS](http://glaros.dtc.umn.edu/gkhome/metis/metis/overview), e.g., most Linux based servers.
* Physical switches that support IP multi-cast.
* Server (as controller) can login into the servers (as edge switches, with at least 2 separate network interfaces) running OpenvSwtich via ssh without authorization (Need to put the public authorization key previously).
###Sample Testbed:
* Three edge switch instances (in two local control groups) are connected through a physical switch (IP network), and are connected to the central controller.
* Each edge switch has connections to two subnets: control layer subnet and the datapath layer subnet.
* Edge switches can be installed at Linux based servers.
* Edge switches can login to the central controller via ssh without manual authorization.
* Deploy the local control modules at every edge switches following the [Installation Documents](lcm/openvswitch-lc/INSTALL) inside.
* Modify the address information as necessary. For example, the default control plane IP of edge switch #1 is ```192.168.57.10```, while for edge switch #2, the IP is ```192.168.57.11```. The datapath plane IP addresses are set to ```10.0.0.0/8``` subnet.
* Start the agent.sh daemon at each edge switch.
* Setup the central control modules at the central controller.
* Start floodlight-lc in the central controller to receive PACKET_IN msg, see [Floodlight Getting Started](http://www.projectfloodlight.org/getting-started/). Run ```ant; java -jar target/floodlight.jar``` if all dependencies are already satisfied.
* Start the collect_agent.sh daemon to collect upward statistics.
* Start the *groupManager* daemon to update the grouping.
* Test the deployment
* Capture IP multicast message at each edge switch, confirming that they are broadcasting the LCG location/statistics information.
* Ping between two hosts in the same LCG, it will be handled by the G-FIB, hence no openflow message is generated and forwarded to the controller. The latency will be similar to direct transfer.
* Ping between two hosts in different LCGs, openflow messages are generated and forwarded to the controller and the the central controller will handle it using the C-LIB. The latency would be much higher as the edge switch has to talk with the central controller. Besides, the *Encap* message will be sent to the edge switch.
## How does it work?
Basically, the ```floodlight-lc``` + ```openvswitch-lc``` cooperate as the basic control-datapath model in SDN. Based on them, we enhanced ```openvswitch-lc``` + agent to behave as local control groups, while ```floodlight-lc``` + daemons work as the central controller. More details, e.g., the group maintain algorithm and the implementation technical issues, are discussed in the paper.
##Documentation
Besides the readme files, you can easily make the API document with python/java/c doc tools. Plenty comments in the code would also be helpful.
##Support
Feel free to email to the authors. The project is planned to be community-supported soon.
##Contributing
There are still numbers of components available to optimize. For example, to build more robust message switching system.
Everyone is encouraged to download the code, examine it, modify it, and submit bug reports, bug fixes, feature requests, new features and other issues and pull requests. Thanks to everyone who has contributed to the project.