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 | Needed by UC | Heat Template | OOM | Project Tech. Lead | Notes |
|---|---|---|---|---|---|
| A & AI | Yes | D | D | Complete | |
| Application Authorization Framework | No | C | Not Release A | ||
| APPC | Yes | D | D | ||
| CLAMP | Yes | D | Mike will work with CLAMP team on this. They have the container now, OOM needs to look at its env get signed and approve the CI. It will be ready tomorrow. (OOM-12) | ||
| 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. Check with Lusheng the timeline | |
| DMaaP | Yes | D | D | ||
| Documentation | Yes | N/A | N/A | ||
| External API Framework | No | ||||
| Holmes | Yes | N/A | N/A | Managed by DCAE | |
| Integration | Yes | N/A | N/A | ||
| Logging Enhancements Project | No | R2? | Check | ||
| Microservices Bus | Yes | D | D | ||
| Modeling | No | C | |||
| Multi VIM/Cloud | Yes | D |
| Patch | |
| ONAP CLI | No | D | |||
| 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 | Yes | D | Mike to work on this one | ||
| 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; Working on the configuration, 1~2 days from 9/18/2017 | ||
| VF-C: Virtual Function Controller | Yes | D | D | ||
| VID project | Yes | D | D | ||
| VNF SDK | Yes | D | |||
| VNF Requirements | No | N/A | N/A | Documentation | |
| VNF Validation | No | N/A | N/A | Not in Release A |