Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Added demo guideline for new components

...

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 demo should be ideally completed before around M4 deadline to meet release timeline.

Demo Guidelines

    • Each demo should be under ~20 min + ~5 min Q&A
    • Demo scope to include following
          1. Specify ONAP deployment dependencies/pre-requisite and how to validate them (can be explained from links under - DCAE R4 Service Component (On-demand) deployment Instruction)
          2. Walkthrough component blueprint/input files and configuration
          3. Deployment Demo (though Cloudify/cli)
          4. Validation of the deployment status
          5. Flow simulation (using scripts/curl for mocking up feed)
          6. Corresponding validation (logs and/or dmaap)
    • Common Q&A
        • List of Features/JIRA's deferred for next release
        • Complaint with ONAP Logging guidelines/CBS integration?
        • Can multiple instance be run in-parallel (for scaling)? Any external dependency for persistence?


Deployment Integration

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).

...