Skip to end of metadata
Go to start of metadata


Agenda

  • JIRA board https://jira.onap.org/secure/RapidBoard.jspa?rapidView=41&view=planning&selectedIssue=OOM-63&epics=visible
  • Seshu Kumar M from SO - last PTL meeting - would like to discuss scaling and resources - JIRA
  • Reviews https://gerrit.onap.org/r/#/q/status:open+oom
  • OOM-460 configuration work -  OOM-460 - Getting issue details... STATUS
  • Helm version 2.3 to 2.8? test 2.7 to 2.8 - fully test this - JIRA  OOM-486 - Getting issue details... STATUS
  • 1.6.10, 1.8.6k, 2.3x, 1.12d - 1.6.14, 1.8.6, 2.8.(s/c), 1.12d  Michael O'Brien (Amdocs 1705-1905) will test clouds

  • (borislav 2.6.2 testest on R 1.6.14 - vnc-portal testing
  • Amsterdam Release notes - OOM still in "experimental mode" for Amsterdam. 
    • When ready, OOM shall create it's own internal release and let the community know. Target EOW.
  • OOM Roadmap Roger Maitland
    • Persistent volumes: Need to identify which components do not have a good strategy for data persistence and add to OOM backlog, i.e. support restart without loss of data.
  • Proposal for Scaling of ONAP components. Milind Jalwadi
    • Milind Jalwadi bringing the idea of centralizing ONAP component scaling parameters.
    • Current design proposing helm dependency injection for all configuration management / parameters including scaling
    • OOM should start gathering requirements for each component so that we show how that can be done in OOM. 
      • Create a structure in the wiki, advertise in mailing list.
      • OOM team members should join all component project teams and describe the work required to support scaling in OOM.
    • Are we focused on dynamic scaling, manual scaling or both?
      • Make sure we refine the target for Beijing vs Casablanca.
      • Which tool is used for threshold setting? 
        • For manual scaling, probably in helm
        • For auto-scaling, need to involve the component teams to figure out how K8S can be used to scale each of the components,
          • teams are looking for guidance, 
          • Split the work across many team members here. 
  • Update on config management Mike Elliott
    •  Some parameters should maybe populated at run time, e.g. openstack configurations (there will be multiple openstack configs). 
      • This is an SO + AAI requirement more than an OOM requirement. Should be brought to the ARCH sub-committee. Yury Novitsky to bring the issue to the discuss list.
  • Pavan Gupta faced issues installing ONAP Amsterdam from OOM. Recommendation: use Master, was tested on CI/CD to be working. Michael O'Brien - (deprecated as of 20170508) - use obrienlabs and Alexis de Talhouët to support if required
  • Question / Technical issue: Should MSB discover services automatically? 
    • In Amsterdam, need to manually provide the Token. On master this is done automatically. 
    • OOM defect will be opened and discuss list conversation will be started. Hong Guan and Jun Hu
  • Consul health checks
    • Some components are not providing standard ways to provide health checks. 
  • OOM Backlog sanity
  • Anything of interest...

Michael O'Brien (Amdocs 1705-1905) to update the new sprint JIRA board

Notes


  • No labels

2 Comments

  1. ONAP team collaboration

    Multicloud logging Filebeat work  MULTICLOUD-151 - Getting issue details... STATUS in OOM is being tracked under the logging JIRA  LOG-156 - Getting issue details... STATUS

  2. For Q about current health status of master - see the robot output each hour for example on 

    http://jenkins.onap.info/job/oom-cd/1414/console

    There is a kibana dashboard below - for example the last 12 hours show regressions on SDC(90% failure) and SDNC (100% failure) - looking into it

    see CD Healthcheck and top right - select 7 days

    http://kibana.onap.info:5601/app/kibana#/dashboards?_g=(refreshInterval:(display:Off,pause:!f,value:0),time:(from:now-12h,mode:quick,to:now))

    Tracking new AAI as well (last 2 hours) in  OOM-614 - Getting issue details... STATUS