Generate configs for C-BGP

We need a better defined format for serializing the ANM and NIDB modules into JSON format.

Currently JSON is used both to serialize each of the ANM and NIDB, and for pushing the updated network topologies to the webserver.

The latter is the problem - currently each of the overlay graphs are individually converted to JSON format, pushed into a dictionary, and then JSON-ified a second time.

Additionally, this dictionary assumes each key is an overlay graph, limiting the ability to pass network-wide data, which applies to all overlay graphs (such as the Network Name). This causes issues for gh-84.

The description format should:

• Allow serialization of each of the ANM and NIDB seperately
• Only have a single JSON step, to serialise all of the overlays, such that the data structure can be extracted cleanly in a single parse in any language
• Allow network-wide data

One solution could take the form of:

{
'data': {
    'name': 'mynetwork'
    },
'anm': {
    'phy': {(graph)}
    'ospf': {(graph)},
    ...
    },
'nidb': {
    (graph)
},
}

split out ip general overlay, and then build v4 and v6 from this,
ie create a collision domain graph, and then clone this for the v4 and v6 graphs

Have support for parsing into Syntax Tree.
Need:

• appropriate flattening into different device formats
• handling of selection syntax for Origin() and Transit()
• Allocation of prefix and community lists

Need to create Junos configs, and also the topology VMM

Basic Junos, with appropriate interfaces.
Initially will NOT handle creating and starting up (ie no deployment step)

Need to allow user to allocate specific IP addresses

Redo nidb as isistance wrapper to allow set and get attributes

stackoverflow.com/questions/1305532/convert-python-dict-to-object

d3 hull throws an error if there are three nodes in a straight line. this can occur if two routers, and the created collision domain between them.

Need checking code to handle this. One solution is to add an epsilon (eg 0.01) to the intermediate node, so they're not in a perfect line.

Bug in IP allocation code for two router networks:

INFO Allocating Collision Domain IPs
edge sn 10.0.0.0/17
edge sn 10.0.128.0/17

If a third node is added:

INFO Allocating Collision Domain IPs
edge sn 10.0.128.1
edge sn 10.0.128.2
edge sn 10.0.0.1
edge sn 10.0.0.2

Need a more general approach to interface naming, than using edge_ids

(This is a large piece of work)

creating junos files, and topology.vmm

Allocate infrastructure and loopback IPs from different pools.

Already generate IOS.
Need to create the dynagen topology file.

Future work can look at automatic deployment and measurement.