| VENKATESH KUMAR | 6455974 | 2020-04-29 18:53:53 -0400 | [diff] [blame^] | 1 | ============== |
| 2 | MOD Objectives |
| 3 | ============== |
| PANCHAL | 0424f6f | 2020-03-27 19:28:03 -0400 | [diff] [blame] | 4 | |
| 5 | MOD stands for "micro-service onboarding and design" and the project is |
| 6 | an effort to reboot the onboarding and design experience in DCAE. |
| 7 | |
| 8 | |
| 9 | **Goals and Stretch Goals** |
| 10 | --------------------------- |
| 11 | |
| 12 | |
| 13 | - Due to resource constraints, there are mismatched capabilities between SDC/DCAE-DS and DCAE mS deployment. |
| 14 | |
| 15 | - Due to #1, mS developers upload handcrafted blueprint, and stay involved throughout the deployment process. This also ties mS development to specific Cloudify implementation. |
| 16 | |
| 17 | - There is no Service Assurance flow design in SDC/DCAE-DS, and so there are no reusable flow designs for the Service Designer. |
| 18 | |
| 19 | - There is extensive reliance on developers’ involvement in providing [Inputs.json] as runtime configurations for mS deployment. |
| 20 | |
| 21 | - There is no E2E tracking of the microservice lifecycle. |
| 22 | |
| 23 | |
| 24 | **To address these problems, the new DCAE MOD, replacing the mS onboarding & DCAE-DS in SDC, aims to -** |
| 25 | |
| 26 | |
| 27 | |
| 28 | - Move DCAE mS onboarding & design from SDC project to DCAE Project. |
| 29 | |
| 30 | - Provide simplified mS Onboarding, Service Assurance flow design, & mS microservice design time & runtime configurations to support developers, service designers, and operations. |
| 31 | |
| 32 | - Auto-generate blueprint at the end of the design process, not onboarded before the design process. |
| 33 | |
| 34 | - Support Policy onboarding & artifact distribution to Policy/CLAMP to support Self Service Control Loop. |
| 35 | |
| 36 | - Streamline the process of constructing to deploying flows, Provide the ability to track flows - capture and store the progress and evolution of flows and Provide clear coordination and accountability i.e Provide catalog & data for microservice lifecycle tracking. It fits the ECOMP's release process and must provide clear visibility along the entire process and across different environments. |
| 37 | |
| 38 | - Support automated adaptation of ML model from Acumos to DCAE design & runtime environment through the Acumos Adapter. |
| 39 | |
| 40 | - DCAE-MOD is developed by the DCAE team to ensure consistency across all DCAE implementation, with the long term objective to integrate with SDC as part of the Design Platform. |
| 41 | |
| 42 | - Integrate with ONAP User Experience portals (initially ONAP portal, later SDC portal). |
| 43 | |