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 | ||||
Application Authorization Framework | |||||
APPC | |||||
CLAMP | |||||
Common Controller SDK | |||||
DCAE | 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 | |||||
Portal Platform Project Proposal | |||||
SDN-C | |||||
Service Design & Creation | |||||
Service Orchestrator | |||||
VF-C: Virtual Function Controller | |||||
VID project | |||||
VNF SDK | |||||
VNF Requirements | |||||
VNF Validation | No | NC | NC | Not in Release A |