| Table of Contents |
|---|
...
| REQ# | DCAE Commit Status | DCAE Impact Assessment | DCAE JIRA # |
| YES | Slice Analysis enhancement
Commitment from HUAWEI for Development; Wipro team support reviews | |
| YES | Same as REQ-1076 + Introduction of ML/MS mS (POC) Commitment from Wipro | Jira to be created of ML/MS |
| YES | Cloudify/platform-handlers deprecation; MOD helm integration Commitment from AT&T, Nokia, Ericsson, Wipro, Huawei, |
...
Following platform component will be continued to be deployed via helm until all DCAE MS are migrated to new Config management solution via SDK
- ConfigBinding Service*
- Consul
DCAE-MOD deployment is optional and will include following component (controlled via helm chart configuration under OOM)
- Genprocessor
- MOD/NiFI UI
- Distributorapi
- Runtimeapi
- Onboardingapi
* - Will be assessed at M3 depending on Helm migration feature status.
Functionalities
List the functionalities that this release is committing to deliver by providing a link to JIRA Epics and Stories. In the JIRA Priority field, specify the priority (either High, Medium, Low). The priority will be used in case de-scoping is required. Don't assign High priority to all functionalities.
...
| Risk identified | Mitigation Plan | Contingency Plan |
|---|---|---|
| Due to upstream dependency on NIFI project, some of MOD (NiFI) components (designtool/gen-processor/nifi-registry) will remain in java 8 | Request exception for SECCOM. Assess migration to use new MOD2 standalone components for onboarding (based on community resource/support) |
Resources
Please see the INFO.yaml files associated with each repo as the authoritative sources of information. https://gerrit.onap.org/r/admin/repos/q/filter:dcae
...