Agenda:

  • Status / Scrum
  • OOM Readiness for Amsterdam
    • How realistic is it to meet the Sept 14 code freeze? 
      • We need to go through all projects to find gaps and identify major blocks to work on.
      • Need to identify blockers, e.g. seed code unavailable.
      • Formulate joint effort with the Integration team - there are a lot of synergies between the 2 teams. David Sauvageau to reach out to Helen Chen.
      • Likelihood to meet code freeze date is high (probably 90%) to run the vFW demo at minimum. Getting containers up and running = very confident, even for components that were not in 1.0. Getting integration working is dependent on code stability. 
      • By next week the code should have the next phase of the demo.
      • Components out of scope from that estimate:
        • DCAE gen2 (no code available)
        • Tosca based orchestration (no code available)
        • Mult-cloud, MSB, VFC still need to be investigated.
  • News from Cloudify
    • Bringing additional resources to bring our cloudify stretch target on time for code freeze
    • Objective is to provision kubernetes (master, nodes), then create special node type that goes over the YAML file to create the workloads using kubernetes (make onap up and running). Then add a verification test as part of the TOSCA to test that all ONAP services are up and running.

    • Need to first propose an architecture on the wiki and have the community discuss the architecture on the discuss list. Will be presented at the next OOM meeting.(Arthur Berezin)

  • Functional Overlap with MSB
    • There is significant overlap with MSB. Need to work with the MSB team to identify what is redundant with the MSB project given that K8S can perform a lot of what MSB does.
  • should we have a discuss list specific to OOM? David Sauvageau to try to create one so that we can experiment with it,

Wiki page to be reviewed by the team: OOM User Guide



  • No labels