(CTTC) Implement new Topology component
Proposers
- Lluis Gifre (CTTC)
- Ricard Vilalta (CTTC)
- Raul Muñoz (CTTC)
Description
Provide a new Topology component. Should provide REST-API--based connectors to gather topological details from external entities.
Demo or definition of done
A new Topology component replacing the context topology entities should be provided.
References
None
Feature Design (for New-Features)
Clarifications to Expected Behavior Changes
The logic managed by Context in terms of topology should be moved to the new Topology component. It should also integrate REST-API--based connectors to gather topological details from external entities. Should manage abstracted topologies.
Assumptions
None
Impacted Components
Context, Topology, Service, PathComp, Slice, Forecaster, InterDomain, Compute, WebUI
Context Impact
Remove topology functionalities.
Topology Impact
New component implementation. Should manage a topology database with events. Should manage abstracted topologies.
Service Impact
Should obtain context and topology data from Topology component.
PathComp Impact
Should obtain context and topology data from Topology component.
Slice Impact
Should obtain context and topology data from Topology component.
Forecaster Impact
Should obtain context and topology data from Topology component.
InterDomain Impact
Should obtain context and topology data from Topology component. Functionality to abstract topologies should be removed.
Compute Impact
Should obtain context and topology data from Topology component.
WebUI Impact
Should obtain context and topology data from Topology component.
Testing
- Upload topology and check it is properly stored in Topology component's database
- Check end-to-end workflow to create/retrieve/update/delete services and slices is operational.
- Check that topology is retrieved properly through Compute component.