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 | D | Complete | |
| Application Authorization Framework | No | C | |||
| APPC | Yes | D | D | ||
| CLAMP | No? | C (next 2 weeks) | |||
| Common Controller SDK | Yes | 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 | Yes | Gen 1 - D Gen 2 - C (by M4) |
| DCAE Gen1 - under review: https://gerrit.onap.org/r/#/c/11167/ DCAE Gen2 - dependency on DCAE team to deliver startup container | |
| DMaaP | Yes | D? | D | ||
| Documentation | Yes | N/A | N/A | ||
| External API Framework | No | ||||
| Holmes | No? | N/A | Managed by DCAE | ||
| Integration | Yes | N/A | N/A | ||
| Logging Enhancements Project | No | ||||
| Microservices Bus | Yes | D | |||
| Modeling | No | ||||
| Multi VIM/Cloud | Yes |
| Under review: | ||
| ONAP CLI | No | ||||
| ONAP Operations Manager | Yes? | N/A | N/A | ||
| ONAP Optimization Framework | No | N/A | N/A | Not in Release A | |
| ONAP University | No | N/A | N/A | ||
| ONAP Usecase UI Project Proposal | No | ||||
| Policy Framework Project Proposal | Yes | D | D | Complete for 1.1 | |
| Portal Platform Project Proposal | Yes | D | D | ||
| SDN-C | Yes | D | D | ||
| Service Design & Creation | Yes | D | D | SDC will use the heat based deployment For R1 | |
| Service Orchestrator | Yes | D | MSO 1.1 done, waiting on SO artifacts in Nexus3 | ||
| VF-C: Virtual Function Controller | Yes |
| VF-C team are working on VF-C artifacts in Nexus3 | ||
| VID project | Yes | D | D | ||
| VNF SDK | No | ||||
| VNF Requirements | Np | ||||
| VNF Validation | No | N/A | N/A | Not in Release A |