...
Identified Need | Description | Driver | Dependencies | Project fit |
Homing function | View of placement | A&AI will have a view of where capacity will be | ||
orchestration of multiple VNFs | ||||
imperative vs. declarative approaches | ||||
VNF configuration | interface between SO and AppC | |||
Platform orchestrator and resource orchestrator | provider software that runs on top of OpenStack (and others???) resource orchestrator needed for A&AI (pre-populate database) – need further discussion about role | |||
support for Multi-VIM | merge with platform orchestrator? needs more discussion | |||
service optimization framework | for instantiation, changes, etc. | A&AI, DCAE, Policy | ||
SO/orchestrator federation | geographically distributed orchestrators (scale and federation); hierarchical | could relate to other entities as well | ||
SO scale | geographically distributed orchestrators (scale and federation); hierarchical | |||
service chaining | execute service chain per user | |||
scaling/healing of underlying components | ||||
Is this a framework or a single multi-technology orchestrator? | ||||
monitoring | monitor the orchestrator and recovery | |||
Project proposals.
[repeat for each project. Note: This is not a complete project proposal skeleton, only sufficient enough for this discussion]
Project 1:Service Orchestrator
Project Name: Service Orchestrator
- Provide a brief project name.
Project Description
- Provide a high level description of the project Take and evolve the service orchestration module to support various controllers
Scope:
- Service orchestration-
- interface to "multi-VIM"
- dependencies to SDC and modeling
- non-functional impacts
- support for YANG, Heat, TOSCA
Quickly identify scope, consider: documentation, APIs, models, testing, integration, functionality.
...
- Identify baseline code (if any)
Project 2: Multi-VIM
Project Name: Multi-VIM
- Provide a brief project name.
Project Description
- Support for multiple VIMs
- testing
- Provide a high level description of the project
Scope:
- Common interface for multiple VIMs
- testing
- Quickly identify scope, consider: documentation, APIs, models, testing, integration, functionality.
...