Versions Compared

Key

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

Date

Previous Meeting [No Page] 

Date:

Next Meeting

Ideas for Discussion and Tentative Agenda

  • Administrative Items
    • Committer promotion request vote for Ramki
    • Welcome to Siamak Layeghy from University of Queensland
    • We need to capture meeting notes (this page is a starting point)
  • Sync up on M2 Checklist, deadlines, etc.
    • Unit tests and status
    • Functional testing needs
    • Need to start thinking about integration tests
  • Seed code is a bit stabilized, so implementation of use case adaptation and new functionality ramps up
    • Need to coordinate the set of contributors listed
    • One approach is to identify contributors working specifically on (a) R2 items, (b) R3+ items, (c) Longer-term items, etc. 
  • Regular review of Sprints and JIRA items
    • Rotate scrum master responsibilities

...

TimeItemWhoNotes



Discussion on functional features that are applicable across use cases (Alex Vul)



Discussion on fetching policies (EMF vs TOSCA) and whether SDC GUI will show the models. Ramki: strongly recommend Tosca.



What to do if ONAP and ECOMP-SO are differences?



Discussion on A&AI interface – some functionality we want may need agreement from A&AI team



Identification of port numbers (see notes below). This allows for K8S to use the most efficient interface it can find.



Suggestion from Adolfo on recording the meetings (see comment section below)

Action items [All pending items copied over to next week(s)]

  •  Create a JIRA for Developer Page (Dileep to create and assign to Sastry for now) 
    Jira
    serverONAP JIRA
    serverId425b2b0a-557c-3c0c-b515-579789cceedb
    keyOPTFRA-97
  •  CLM – Sastry to follow up (pending)
  •  Jenkins Merge Job for OSDF – Sastry to follow up (Dileep created jobs; nexus pending)
  •  Meeting with Seshu/Cory on OOF-SO API changes (Matti/Ankit) (initial version sent, API discussion with Alan from ATT)
  •  Alex to review functionality that is required for multiple use case (focus on R3 needs) – we can probably do it as needed 
  •  Functional testing needs: Everyone should review the test cases (still to do) (provide feeback; at a minimum be aware of the scope and functionality)
    •  To go through on 2/19 meeting
  •  Develop a scrum stand-up meeting template – get an OK from the team
  •  Identify contributors committed for R2 release (OK to start with small list and add)
  •  Create jira's for model-driven optimization modules (minizinc dockerization and linking to OSDF) – simple unit tests and example CM app (Ramki)
  •  Create jira's for MSB and API (Ankit)
  •  Everyone: Review current jira's to see if any major items are not fully covered (Dileep, Ramki, Shankar, Alex, Ankit, Sastry)
    •  Ramki created items related to platform maturity requirements and added text and (ongoing effort on sub-tasks)?
  •  Interaction wirh policy team to finalize policy modeling language (TOSCA vs EMF) and also the variant (DCAE vs next-gen) – has to be TOSCA sooner than later
    •  Create a requirement for Policy team (so they will either blanket support for ONAP or not)
    •  Extreme case, use DCAE model structure (TOSCA, but is a variant)

...