Two alternatives:
- Using OOM (K8-based strategy), which was approved in the past face-to-face meeting and will be the standard/preferred way in the long run;
- Using Heat template, which is what we did for OpenECOMP.
(D: Done | C: Committed, when? | NC: Not Committed)
| Project Name | MVP | Heat Template | OOM | Project Tech. Lead | Notes |
|---|---|---|---|---|---|
| A & AI | Yes | D | |||
| Application Authorization Framework | |||||
| APPC | D | ||||
| CLAMP | C (next 2 weeks) | ||||
| Common Controller SDK | N/A | N/A | As a library, CCSDK is not installed separately but rather is installed as part of the client project(s) that uses it (e.g. APPC, SDNC) | ||
| DCAE | Gen 1 - D Gen 2 - NC | DCAE Gen1 DCAE Gen2 | |||
| DMaaP | D? | C, Date? | |||
| Documentation | N/A | N/A | |||
| External API Framework | |||||
| Holmes | |||||
| Integration | N/A | N/A | |||
| Logging Enhancements Project | |||||
| Microservices Bus | |||||
| Modeling | |||||
| Multi VIM/Cloud | |||||
| ONAP CLI | |||||
| ONAP Operations Manager | |||||
| ONAP Optimization Framework | |||||
| ONAP University | N/A | N/A | |||
| ONAP Usecase UI Project Proposal | |||||
| Policy Framework Project Proposal | D | ||||
| Portal Platform Project Proposal | D | ||||
| SDN-C | D | ||||
| Service Design & Creation | D | ||||
| Service Orchestrator | D | ||||
| VF-C: Virtual Function Controller | |||||
| VID project | D | ||||
| VNF SDK | |||||
| VNF Requirements | |||||
| VNF Validation | No | NC | NC | Not in Release A |