...

• Proposed name for the project: projectname

Project description:

• Provide high level description of intended project and intended use case(s) and benefit, if needed.
• Requirements
  • Deployment run on every or batch of commits
  • Access to failed healtcheck results
  • Access to failed container results "kubectl get pods --all-namespaces | grep -E '0/|1/2' - like http://jenkins.onap.info/job/oom-cd-master/3496/console

Scope:

• Describe the functionality to be provided by the project.  Please provide the full intended scope of the project; not just what is intended for the project's first release.
• Specify any interface/API specification proposed,
• Identity a list of features and functionality will be developed.
• Identify what is in or out of scope. During the development phase, it helps reduce discussion.
  
  

Architecture Alignment:

• How does this project fit into the rest of the ONAP Architecture?
  • Please Include architecture diagram if possible
  • What other ONAP projects does this project depend on?
• How does this align with external standards/specifications?
  • APIs/Interfaces
  • Information/data models
• Are there dependencies with other open source projects?
  • APIs/Interfaces
  • Integration Testing
  • etc.

Other Information:

• link to seed code (if applicable)
• Vendor Neutral
  • if the proposal is coming from an existing proprietary codebase, have you ensured that all proprietary trademarks, logos, product names, etc., have been removed?
• Meets Board policy (including IPR)

Use the above information to create a key project facts section on your project page

Key Project Facts:

Release Components Name:

Note: refer to existing project for details on how to fill out this table

Resources committed to the Release:

Note 1: No more than 5 committers per project. Balance the committers list and avoid members representing only one company. Ensure there is at least 3 companies supporting your proposal.

...

Meeting Minutes

20190124

...