OOM Meeting Notes - 2018-02-21

Owned by Michael O'Brien
Last updated: Feb 21, 2018
3 min read

Agenda

  • https://zoom.us/j/118908904 1000 EST (GMT-5)

  • @Mike Elliott will present configuration changes in progress

  • review 4 drafts from Mike on direction of helm chart work - looking for feedback from operators

  • https://gerrit.onap.org/r/#/q/status:open+oom+standardized-configuration

  • Notes: "add common helm chart" - patch TBD of the 4 above

    • global override policy (one of several examples)

    • driving towards acceptance of these configuration changes for early next week so we can apply to the rest of the subcharts

    • Need to have the ability to fully customize the deployments

    • be able to override config for example - openstack specific (where Cinder for example can be setup globally - other projects can consume this specific config)

    • Pull out secrets for example into a higher config level - and then add specific customization per vendor)

    • Need this config work to set the framework for all of these requirements for Beijing

    • GOAL: get all comments to these 4 reviews by END of THIS WEEK - start monday rolling out new components after a merge this Friday

    • Note: we will refactor on the fly the working code - an evolutionary change to fix certain unavoidable defaults as we bring in this work

    • Q) colliding reviews with other work

    • Application teams need to own their config - as currently we clone config and own it.

    • For example own a minimal set of config - but the bulk should be owned by the component teams - we can meet and work through how to minimize cloning

    • @Roger Maitland Health checks - we have done work on health checks - but teams can get involved in this work

      • Some health checks randomly fail on the CD system - the dependencies inside a project and also between projects are not handled correctly? - we need to review both levels of these dependencies with each component team



  • Introduce team from DMaaP and AAF that would like to work with OOM
    https://lf-onap.atlassian.net/wiki/display/DW/Data+Movement+as+a+Platform+Project
    https://lf-onap.atlassian.net/wiki/display/DW/Application+Authorization+Framework+Project
    https://jira.onap.org/browse/OOM-654?filter=-4&jql=project%20%3D%20OOM%20AND%20text%20~%20%22dmaap%22%20order%20by%20created%20DESC
    https://jira.onap.org/browse/OOM-704?filter=-4&jql=project%20%3D%20OOM%20AND%20text%20~%20%22aaf%22%20order%20by%20created%20DESC

  • DMAAP:
    LUNANUOVA, DOMINIC - dl751d (Bus Controller) @Dominic Lunanuova
    UNNAVA, SUNIL-su622b (Message Router) @sunil unnava
    APPAMPALLY, SRIPAD - sa837d (Data Router) 

    AAF:
    GANDHAM, SAI  -sg481n @Sai Gandham
    Ian Howell- ih616h 
    Gabe Maurer -gm789v 

  • JIRA board 

  • M2 functionality freeze results

  • Best Practices: 

  • All PV/PVC need to be cloud-native agnostica - as in we support Azure, AWS and Openstack volumes (EBS, NFS, Cinder) for example - without breaking any other type of deployment.



Notes