Topology-as-a-service

= Topology as a Service = As discussed at Juno design summit, there are much demand for Topology-as-a-Service which gather information of physical network topology in one place and provide it to other openstack component.

TODO

 * 1) finish project page for incubation
 * 2) gather use cases and break them down to requirement of the Topology-as-a-Service implementation
 * 3) design API and data model
 * 4) start incubation process and coding

Use cases

 * Vendors like cisco hard code their topology inside the config files currently, this extensions or a similar service is required for large scale deployments. - Arvind
 * Should this be a separate service? Other services like Nova and Cinder might find it useful to have topology information for scheduling etc. - Arvind
 * TripleO has a need to configure link aggregation.  Will this provide enough info/capability? - ChuckC

Links

 * etherpad: https://etherpad.openstack.org/p/topology-as-a-service
 * Juno cycle summit discussion: https://etherpad.openstack.org/p/hierarchical_network_topology
 * summit proposal : http://summit.openstack.org/cfp/details/93
 * blueprint:  https://blueprints.launchpad.net/neutron/+spec/physical-network-topology
 * neutron-spec: https://review.openstack.org/#/c/91275/
 * spec: https://docs.google.com/document/d/1G6v7WxVbeqgtT-iNQBSKZkeEWQd7M2Ch6qcI54mKd38/edit#heading=h.s8eukbngz78c