...
| Time | Item | Who | Notes |
|---|---|---|---|
| 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. |
Action items
- Create a JIRA for Developer Page (Dileep to create and assign to Sastry for now)
- CLM – Sastry to follow up
- Jenkins Merge Job for OSDF – Sastry to follow up
- Meeting with Seshu/Cory on OOF-SO API changes (Matti/Ankit)
- 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 (provide feeback; at a minimum be aware of the scope and functionality)
- 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)
- 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)
...