Versions Compared

Old Version 8

changes.mady.by.user Sastry Isukapalli

Saved on

compared with

New Version Current

changes.mady.by.user Sastry Isukapalli

Saved on

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

...

  • Upstreaming and stabilization of seed code (Sprint 1, Sprint 2):
    • OSDF - Done
    • Homing Change Management (demonstrative application)Optimizer (HAS) - Done
  • Jenkins integration (Sprint 2, Sprint 3)
    • Verify, merge, CSIT - Currently working, Arun (MultiCloud) will help with E2E integration testing
    • Sonar Clm- working ONAP HelpDesk
    • clm - Sastry to follow up
  • Nexus: snapshot binaries - sandbox issue, move the patch to ci-management
  • Functional testing:
  • Unit Testing (Sprint 2 Sprint 3):
  • Dockerization: 
  • API design and development:
    • Policy - follow up with Policy to get scope of TOSCA model, fallback plan EMF model - manually upload the model in Policy in R2. API between OOF-Policy remains unaffected.  
    • SO - Need to sync up with Cory/Seshu to confirm the changes to the API. Schedule meeting this week (Matti/Ankit)
    • AAI - defined the schema for the basic structure for HPA in AAI. Exploring custom query for HPA attributes - fallback plan to use regular API to parse information. 
    • MultiCloud - Bin Yang, Ethan
  • Feature Development
    • vCPE HPA- Arun Aurora (MultiCloud) will help with E2E integration testing, 
    • HPA 
    • VNF scale out    (low priority)
    • Change Management (demonstrative application) - requires minizinc pieces, and creation of models (sprint 3) 
  • Platform Maturity (S3P):
    • Scalability - K8S/OOM Integration
    • Resiliency - K8S/OOM Integration
      • MSB - interaction between OOF - MSB (Ankit) 
    • Security - CII badging - 
    • Manageability
    • Stability
    • Usability
    • Documentation
      • Developer guide (Sprint 2)
      • API (SO-OOF)
      • Deployment docs
    • Performance 

...

Goals

  • Speed up the project in an "agile" manner and get the requirements and APIs nailed down

Discussion items

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 Legacy
    serverSystem Jira
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    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)

Scrum Standup Meeting

Probably good to have the following for each contributor:

During the daily weekly scrum meeting (maybe add one more meeting as we get closer to release deadline), each team member answers the following three questions:

  1. What did you do yesterday last week?
  2. What will you do todaythis week?
  3. Are there any impediments in your way?
ContributorWhat did you do last week?

What will you do this week?

Are there any impediments in your way?
Example: SastryNothingNothingNope
DileepWorked on unit/functional testing with OOF-HAS
Had some trouble with Mocking MUSIC. See notes below.


NOTE: we should have these captured from next week

Links and additional notes

...

  1. A PhD student that has worked on Minizinc models for Software-defined Constrained Optimal Routing Platform for SDN (article link). Link for slides is here.
  2. Arun Arora from VMWare will participate in end-to-end integration work (MC, OOF, etc., from vCPE perspective) 
  3. Ramki's question on port numbers: are they fixed (yes), do we want to keep them so (maybe):
    1. As an example, OSDF has 14699 and we don't want it to be so. 
    2. With K8S, we do not even need to specify ports (via proxies). However, how would we reconcile with that?
    3. Decide on which processes go inside K8S pods
  4. A container specifies a port to bind to (inside a pod or container). K8S will provide a proxy for other components to connect to this container. So, modules can have their own ports without ever exposing them and only expose via proxies. Only need to ensure that no collisions occur within a pod.
    1. Older code base was on a "large docker host" and multiple applications had to be on same IP, hence port numbers like 14699.
    2. Conclusion: we can keep weird port numbers, and can use proxies, and one does not interfere with another

  5. Dileep worked with unit tests for HAS with MUSIC. Mocked pecan request, but it expects a Conductor controller service to be up... Need to mock that. In an offline meeting with Dileep, Sastry showed how some corresponding complex objects are mocked in OSDF (e.g. Flask "g" object in osdf/mainapp/test_osdfapp.py)