You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 8 Next »

Date

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

Beijing Release deliverables:

  • Upstreaming and stabilization of seed code:
    • OSDF
    • Homing
    • Change Management (demonstrative application)
  • Jenkins integration
    • Verify, merge, CSIT
    • Sonar
    • Clm
  • Nexus: snapshot binaries
  • Functional testing:
  • Unit Testing:
  • API design and development:
    • Policy
    • SO
    • AAI
    • MultiCloud
  • Feature Development
    • vCPE
    • HPA
    • VNF scale out   
  • Platform Maturity:
    • Scalability - OOM Integration
    • Resiliency - OOM Integration
    • Security - CII badging
    • Manageability
    • Stability
    • Usability
    • Documentation
      • API (SO-OOF)
      • Deployment docs
    • Performance 

Attendees

Goals

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.

Action items

  • Create a JIRA for Developer Page (Dileep to create and assign to Sastry for now)
  • CLM – Sastry to follow up
  • Functional testing needs: Everyone should review the test cases (provide feeback; at a minimum be aware of the scope and functionality)

Links and additional notes

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.
  • No labels