Versions Compared

Old Version 13

changes.mady.by.user Roger Maitland

Saved on

compared with

New Version 14

changes.mady.by.user David S

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

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
      • CLAMP
      • CLI
      • CCF
      • DMAAP
      • Holmes
      • 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
    • step 1 - Externalize platform parameters (remove hardcoded params). Critical parameters like openstack deployments and etc in an environment file. 
    • step 2 - Configuration management 
    • step 3 - 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.
  • Running ONAP platform across different hosts (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.

...