DRAFT PROPOSAL FOR COMMENTS

The content of this template is expected to be fill out for M1 Release Planning Milestone.

Overview

Scope

What is this release trying to address?

ONAP Operations Manager will be used to efficiently Deploy, Manage, Operate the ONAP platform and its components (e.g. MSO, DCAE, SDC, etc.) and infrastructure (VMs, Containers). The OOM addresses the current lack of consistent platform-wide method in managing software components, their health, resiliency and other lifecycle management functions.  With OOM, service providers will have a single dashboard/UI to deploy & un-deploy the entire (or partial) ONAP platform, view the different instances being managed and the state of each component, monitor actions that have been taken as part of a control loop (e.g., scale in-out, self-heal), and trigger other control actions like capacity augments across data centers. 

In the Amsterdam release, OOM will be used to automatically deploy and re-deploy all ONAP platform components using containers technology, to monitor components state and to automatically heal broken platform components when required. 

Use Cases

OOM functionality 

Minimum Viable Product

• Run the vFirewall demo on docker/kubernetes
• Document Guidelines for bringing components to kubernetes (all component teams can bring themselves their components to OOM). 
• ONAP platform 1-click deployment using containers for all components:
  • • onap-aai
      • aai-service
      • hbase
      • model-loader-service
    • onap-appc
      • dbhost
      • dgbuilder
      • sdnctldb01
      • sdnctldb02
      • sdnhost
    • onap-message-router
      • dmaap
      • global-kafka
      • zookeeper
    • onap-mso
      • mariadb
      • mso
    • onap-policy
      • brmsgw
      • drools
      • mariadb
      • nexus
      • pap
      • pdp
      • pypdp
      • portalapps
      • portaldb
      • vnc-portal
    • onap-robot
      • robot
    • onap-sdc
      • sdc-be
      • sdc-cs
      • sdc-es
      • sdc-fe
      • sdc-kb
    • onap-sdnc
      • dbhost
      • sdnc-dgbuilder
      • sdnc-portal
      • sdnctldb01
      • sdnctldb02
      • sdnhost
    • onap-vid
      • vid-mariadb
      • vid-server
    • AAF
    • DCAE (old or new or both?)
    • MSB
    • Multi-VIM
    • VFC
    • CLI (Stretch)
    • CLAMP (Stretch)
    • CCF
    • Holmes (Stretch)
• Monitoring of platform containers, i.e. visibility to the state of each components
• Auto-restart of platform containers when required - maybe requires a second level of policies to avoid infinite restarts.
• Configuration management to deploy on different environments
  • POCs for tools like Ansible, Chef, Cloudify for config management
    
  • step 1 - Externalize platform parameters (remove hardcoded params). 
    • Critical parameters like openstack deployments and etc in an environment file. 
    • Need to allow to easily change configurations and manage different versions of the configuration files for each component.
  • Using configuration management to determine which component versions to deploy.
  • Using config management to determine where to deploy each indivirual components across geographies (stretch)
  • Anti-affinity
  • Config management examples so that the community know how to use:
    • 1 would be for lab deployment
    • 1 for a production deployment
  • step 2 - Automated config management (M2)
• Platform Upgradability:
  • Teams must expose endpoints for rollbacks and ensure backward compability. We need to provide requirements to each component teams.
  • Ability to deploy multiple instances of ONAP on different versions.
  • Manage individual components versions - Ability to upgrade 1 component at the time. 
• Running ONAP platform across different hosts (stretch)
• Running ONAP on different geographies (stretch)

• Collaboration
  • Integration team: monitoring an end-to-end platform solution. Make the vFW demo managed by oom. 
  • MSB: Service registration and discovery is overlapping - need to be in MVP.
• Orchestrating infrastructure deployment and more deployment options with Cloudify - will determine if it is MVP or stretch or M2 scope. Maybe we lay the foundation in M1 Amsterdam and then grow. 

Out of scope

• auto scaling of onap platform containers

actions: approach the different teams to make sure we understand their requirements for oom.

Functionalities

List the functionalities that this release is committing to deliver by providing a link to JIRA Epics and Stories. In the JIRA Priority field, specify the priority (either High, Medium, Low). The priority will be used in case de-scoping is required. Don't assign High priority to all functionalities.

Epics

Stories

Longer term roadmap

Indicate at a high level the longer term roadmap. This is to put things into the big perspective.

Release Deliverables

Indicate the outcome (Executable, Source Code, Library, API description, Tool, Documentation, Release Note...) of this release.

Sub-Components

List all sub-components part of this release.
Activities related to sub-component must be in sync with the overall release.

Sub-components are repositories are consolidate in a single centralized place. Edit the Release Components name for your project in the centralized page.

ONAP Dependencies

As OOM manages all of the ONAP components it has dependencies on all other projects. OOM's first goal is to manage all of the components from the 1.0 release and will incorporate newer components as they mature.  In order for a project to be managed by OOM deployment artifacts that must be created - specifically a kubernetes deployment specification(s) and project configuration/environment data - in formats provided by this project.

Architecture

See the ONAP Operation Manager (OOM) Description page. 

High level architecture diagram

At that stage within the Release, the team is expected to provide more Architecture details describing how the functional modules are interacting.

Block and sequence diagrams showing relation within the project as well as relation with external components are expected.

Anyone reading this section should have a good understanding of all the interacting modules.

API Incoming Dependencies

List the API this release is expecting from other releases.
Prior to Release Planning review, Team Leads must agreed on the date by which the API will be fully defined. The API Delivery date must not be later than the release API Freeze date.

Prior to the delivery date, it is a good practice to organize an API review with the API consumers.

API Outgoing Dependencies

API this release is delivering to other releases.

Third Party Products Dependencies

Third Party Products mean products that are mandatory to provide services for your components. Development of new functionality in third party product may or not be expected.
List the Third Party Products (OpenStack, ODL, RabbitMQ, ElasticSearch,Crystal Reports, ...).

In case there are specific dependencies  (Centos 7 vs Ubuntu 16. Etc.) list them as well.

Testing and Integration Plans

Provide a description of the testing activities (unit test, functional test, automation,...) that will be performed by the team within the scope of this release.

Describe the plan to integrate and test the release deliverables within the overall ONAP system.
Confirm that resources have been allocated to perform such activities.

Gaps

This section is used to document a limitation on a functionality or platform support. We are currently aware of this limitation and it will be delivered in a future Release.
List identified release gaps (if any), and its impact.

Known Defects and Issues

Provide a link toward the list of all known project bugs.

Risks

List the risks identified for this release along with the plan to prevent the risk to occur (mitigation) and the plan of action in the case the risk would materialized (contingency).

Resources

Fill out the Resources Committed to the Release centralized page.

Release Milestone

The milestones are defined at the Release Level and all the supporting project agreed to comply with these dates.

Team Internal Milestone

This section is optional and may be used to document internal milestones within a project team or multiple project teams. For instance, in the case the team has made agreement with other team to deliver some artifacts on a certain date that are not in the release milestone, it is erecommended to provide these agreements and dates in this section.

It is not expected to have a detailed project plan.

Documentation, Training

• Highlight the team contributions to the specific document related to he project (Config guide, installation guide...).
• Highlight the team contributions to the overall Release Documentation and training asset
• High level list of documentation, training and tutorials necessary to understand the release capabilities, configuration and operation.
• Documentation includes items such as:
  • Installation instructions
  • Configuration instructions
  • Developer guide
  • End User guide
  • Admin guide
  • ...

Other Information

Vendor Neutral

If this project is coming from an existing proprietary codebase, ensure that all proprietary trademarks, logos, product names, etc. have been removed. All ONAP deliverables must comply with this rule and be agnostic of any proprietary symbols.

Free and Open Source Software

FOSS activities are critical to the delivery of the whole ONAP initiative. The information may not be fully available at Release Planning, however to avoid late refactoring, it is critical to accomplish this task as early as possible.
List all third party Free and Open Source Software used within the release and provide License type (BSD, MIT, Apache, GNU GPL,... ).
In the case non Apache License are found inform immediately the TSC and the Release Manager and document your reasoning on why you believe we can use a non Apache version 2 license.

Each project must edit its project table available at Project FOSS.

Charter Compliance

The project team comply with the ONAP Charter.