[quagga-dev 16022] Re: Quagga to SDN
Quagga = Control Plane (BGP/OSPF/ISIS/RIP/etc routing engine) OS Networking Stack = Data Plane You can magic quagga to speak to another `data plane` or you can extract quaggas routing decisions from the OS (Linux Netlink for eg) to write to a dataplane (as cumulus does). On Wed, Aug 10, 2016 at 4:26 PM srujan k wrote: > Hi All, > what is SDN? My understanding as follows. > Traditional routers have their control plane and data plane are coupled > together and will be used for communication. Control plane is brain for > making decisions and data-plane is carrier/forwarder to transfer the > packets. These 2 planes reside in the same hardware. Data-plane uses some > powerful asics/processors for forwarding, but control plane is a software > which decides the best entries to be inserted into routing table. With SDN, > these 2 planes are divided into separate machines. There will be a control > plane (server) who receives the messages from clients(control/data-plane) > and processes. > > Since quagga is control plane software which can act as Server and > processes the messages. Please throw some pointers and > uses/advantages/disadvantages about integration quagga for SDN. > > My most of the statements may be wrong, please correct if necessary. > > Regards, > Srujan > ___ > Quagga-dev mailing list > Quagga-dev@lists.quagga.net > https://lists.quagga.net/mailman/listinfo/quagga-dev ___ Quagga-dev mailing list Quagga-dev@lists.quagga.net https://lists.quagga.net/mailman/listinfo/quagga-dev
[quagga-dev 16021] Quagga to SDN
Hi All, what is SDN? My understanding as follows. Traditional routers have their control plane and data plane are coupled together and will be used for communication. Control plane is brain for making decisions and data-plane is carrier/forwarder to transfer the packets. These 2 planes reside in the same hardware. Data-plane uses some powerful asics/processors for forwarding, but control plane is a software which decides the best entries to be inserted into routing table. With SDN, these 2 planes are divided into separate machines. There will be a control plane (server) who receives the messages from clients(control/data-plane) and processes. Since quagga is control plane software which can act as Server and processes the messages. Please throw some pointers and uses/advantages/disadvantages about integration quagga for SDN. My most of the statements may be wrong, please correct if necessary. Regards, Srujan ___ Quagga-dev mailing list Quagga-dev@lists.quagga.net https://lists.quagga.net/mailman/listinfo/quagga-dev
[quagga-dev 16020] Proposed-8 Testing Update & Github Pull Requests
All, Trying to solve the issues of the Proposed-8 branch. Where we stand: - The current version of the branch compiles, but fails many protocol tests - Git Bisect is currently not possible for the branch as the branch doesn’t compile up to the last commits (which fix previous bad commits) I’ve started testing from the beginning of the branch and the first approx 25 commits are all fine before the problem starts. Completely retesting and getting every commit working would be nice, but is probably unfeasible. I’ve setup a test for some automated testing and merging on our (OpenSourceRouting) Github (github.com/opensourcerouting/quagga) to experiment with some ideas on how we could do some automated testing/merging of new patches in the future. (Using Github pull requests) I’ve started by creating a dev/automerge branch based on master. If a pull request is created against this branch (only this branch), then the CI system will test the pull request. If it’s successful, the req will be merged by the CI system. (and the next pull request can be opened). If it fails, then I’ve tried to find the later commit which has the fixes, updated the pull request and wait for the next test result. I started at the beginning and cherry-picked commits from proposed 8 into a pull requests and so far got 46 commits of the 159 commits integrated. See https://docs.google.com/spreadsheets/d/16UtC3epcRv6hx5dkRwPOtG3_wRVj5L5guB63g_hmw-s/edit#gid=1711194199 (The green highlighted commits are merged to the dev/automerge branch) I think the system works, but it takes time to reorder the commits. If someone wants to give it a try to continue finding working commits from the remaining commits, then just fork the repo and make pull requests against the dev/automerge branch. If there are any issues, then just email me. If you have better ideas then let me know. Feedback is always welcome. - Martin Winter ___ Quagga-dev mailing list Quagga-dev@lists.quagga.net https://lists.quagga.net/mailman/listinfo/quagga-dev
