...
- Review new service proposal with architecture team and project team.
- Identify usecase this service will be targeted under (optional).
- Repository creation (PTL will submit request to RM, who will coordinate with TSC/LF support)
- Work with PTL to scope the service and EPIC/US creations and sprints to target
- Push seed Code into gerrit (if available)
- Build enhance functional component (mS)
- Setup Jenkins job (under ci-management repo) for building artifacts/docker images.
- CLM/coverty scan and address all CRITICAL/HIGH License/security issues identified (Required for passing release candidate)
- Code Coverage of 50% or more (Required for passing release candidate)
- S3P (all scaling/resiliency/security/maintainability) goals should meet at the minimum level defined for DCAE project for the targeted release (Required for passing release candidate)
- Logging compliance (https://wiki.onap.org/pages/viewpage.action?pageId=28378955) (Required for passing release candidate)
- Documentation to be provided (on components configuration, deployment steps and dependencies and overall design)
DCAE Platform Integration
...
If the component is stateful, it should persist its state on external store (eg. pg, redis) to allow support for scaling and resiliency. This should be important design criteria for the component. If the component fails to meet S3P goals, it will not be release candidate.
Demo
To be able to certify the component for release, the MS owner should present demo to project team (and integration team) using onap Jenkins build images/container and manual deployment via blueprint under DCAE platform. This can be done either DCAE tenant on POD-25.
Deployment Integration
Once the components meet all above criteria, the component should will be included in the DCAE bootstrap process to enable deployment during ONAP/DCAE instantiation (this step is optional if component will be deployed through CLAMP).