User login

Blogs

08

Aug

2017

Finished updating the disaggregator and method unit tests to work with Python 3. Most of the week I have also spent on updating the simulation tools to run with Python 3 and have updated to the new ExaBGP (version 4.0.2).

I have also worked on the automatic unit tests which will make sure that the disaggregator behaves accordingly when running.

31

Jul

2017

Continued researching and writing for my application protocol paper. Added quite a lengthy background which summarises some of the key events and trends in the history of application protocols which will add a lot of context to my paper.

Also kept investigating new application protocol patterns that continue to appear on the Waikato passive monitor. Added another 5 new protocols this week, so progress continues to be made.

31

Jul

2017

This week I finished the simulation tools which allow building and simulating network topologies in Mininet. I spent some time working on testing the disaggregator in the simulation framework to make sure everything is working correctly.

While testing, I have found and fixed several bugs and issues. For example, there were some problems with parsing the BGP route updates for communities and also some behavioural problems when parsing the communities from the config file filters. The code has been modified to store and process communities as a list of integer tuples. The config file accepts entry of communities in several different formats. I have also addressed an issue that was preventing updates to be processed from peers that do not generate End-of-RIB markers. The dissaggregator now parses a peers Open message to check if they are going to send EoR markers, if not we will no longer defer the table updates until we see a marker for these peers.

I have also spent some time looking at various BGP performance testing tools and on unit testing the code using a similar approach to Faucet. I have also worked on modifying to code to make it Python 3 compatible. Currently, I am in the processes of further testing the code using Python 3 and addressing some issues that I have found.

24

Jul

2017

Spent some time familiarising myself with the BGP project code base. Looked at how the message queues are used and overall how the application is structured and separated. Set up required VMs for simulation and played around with the app to understand how it works.

Implemented a configuration module and factory which allows configuring the application components from a file. This config file is structured and parsed using YAML. The configuration factory will automatically parse and build the required peer, tables and filter objects and associate them as specified in the config file.

I also started looking at implementing a simulation environment using mininet for the BGP project. I currently have some of my 520 code, which I am going to modify, that builds topologies using mininet and allows simulation of networks.

24

Jul

2017

Spent some time working towards releasing a new version of the amplet2-client packages that have been stalled for a few months. Tidied up the Centos build to remove the -lite packages and ported the Debian init/postinst scripts. Merged some outstanding changes and tightened up some dependency checking. Just need to confirm that my transitional packages work correctly and then I think it's ready for release.

Had a look into some edge cases of the amp-web code to support an outside deployment that was seeing unusual behaviour. Found a few areas that need to be cleaned up to support viewing different data in the web interface - we don't use certain combinations of test options in our own deployment so viewing them hasn't been a priority.

Had a short chat with Florin about the BGP project that he is starting to work on this week. Got him up to speed with how how it all works and how it fits together.

24

Jul

2017

Had a quick look at moving the BGP code from python2.7 to python3, and it doesn't look like it will require much work. Didn't go ahead though, as moving to python3 appears to also require moving to exabgp4 which is still rather poorly documented. Probably still worth a look, sooner rather than later.

Spent some time hardening prefix creation to deal with incorrectly formed prefixes, and wrote some unit tests to make sure that it behaves correctly. Also updated unit tests for filters to bring them up to date with recent changes. Wrote some brief overview documentation to describe how it all fits together ahead of Florin starting work on this next week.

10

Jul

2017

Created configuration within my BGP program to peer with routers both internal to my test network and external, and to filter/distribute routes between them. I had to slightly change the way that the network topography was described to better account for loopback addresses and routed interfaces (my earlier networks were just graphs of node names), and update the nexthop calculations to take this into account (especially in the case where my BGP speaker was not directly connected to the external peer). Routes can now be sent around my test network, and filtered or modified as they are received/sent to peers.

Updated and pushed out some updates to the ampweb packages to fix some reported bugs.

10

Jul

2017

Brad set up a physical network using the lab Junipers for me to test my BGP code on, and I made a start working with it. Configured interfaces and set up multihop BGP to get the external peers talking to my controller running a few hops inside the network.

Spent most of the week working on the performance report.

10

Jul

2017

Put together an architecture diagram to help talk about how the BGP program fits together. Spent some more time on scaling - some bits had slow custom implementations of things that were no longer needed, and so were removed.

Spent most of the week working on a performance report based on some measurement data we are collecting, writing code to extract the specific data and generate the appropriate graphs.

10

Jul

2017

Brought the network/topology management into line with the new multi-process model. The topology can now be modified on the fly, which will generate messages to various peers allowing them to re-run their route selection algorithms to take the changes into account.

Removed the distinction between internal and external nodes, and reworked the classes to allow multiple node types, depending on how we want to manage them. We could speak BGP to some, Openflow (or other SDN type protocol) to others, etc.

Spent some more time looking at improving memory usage. Found what I consider a bug in the python multiprocessing queue implementation - a reference to the last message sent to the queue is kept around when it is no longer required, continuing to use memory. I send small infrequent but large messages, which means a lot of memory could be tied up for quite some time for no useful purpose.