Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Sonar coverage requirement updated for Dublin

Table of Contents

...

  • Review new service proposal with architecture team and project team. If new collectors, this typically requires review with ARC and VNFREQ team as this introduces new interface between xNF and DCAE.
  • Identify usecase this service will be targeted under (optional).
  • Capture external and internal dependencies and api consumed/provided.
  • 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 release/sprints to target
  • Push seed code (if available) into gerrit
  • Build/enhance functional component (mS)
  • Setup Jenkins job (under ci-management repo) for building artifacts/docker images.
  • Perform CLM/coverty scan and address all CRITICAL/HIGH License/security issues identified (Required for passing release candidate)
  • Define CSIT test (How to guide → Creating a CSIT Test)
  • Code Coverage of 50% or more  Coverage   (Required for passing release candidate)
    • (Updated 1/12) - New services targeted for DCAE integration should have 80% coverage
    • (Updated 1/12) - Enhancement on existing services should have 80% coverage on impacted files 
  • Logging compliance (https://wiki.onap.org/pages/viewpage.action?pageId=28378955) (Required for passing release candidate)
  • If API's are exposed, need to conform to ONAP API Common Versioning Strategy (CVS) Guidelines

...

The dcae_cli tools enables MS owner to validate the component spec and data_Formats created and also "test" the deployment of MS itself. This allows components to mimic the configuration returned from ConfigBinding Service as expected on typical cloudify based deployment by DCAE platform (Documentation on spec format and tool usage can be found under https://onap.readthedocs.io/en/beijing/submodules/dcaegen2.git/docs/sections/components/dcae-cli/commands.html?highlight=dcae_cli )

Note Updated 1/12: For Dublin, all DCAE MS should be onboarded through SDC  (which include models/blueprint generation from SDC and distributed into DCAE/CLAMP/Policy)

...

 The project wiki space (https://wiki.onap.org/display/DW/DCAE+Documentation) can be used to documents general design about the components itself; can serve the community to know about the component itself and point to other repo/release documentation. 

...

Once the components meet all above criteria, the component 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).



Resources


JJB - https://wiki.onap.org/display/DW/Using+Standard+Jenkins+Job+%28JJB%29+Templates

CSIT  - Creating a CSIT Test

...