User Tools

Site Tools


Models Project Team Meetings

Minutes of Previous Meetings

2016-March-21 Models Project Meeting #3b

Cancelled (no show) See the Meeting #3a for minutes.

2016-March-21 Models Project Meeting #3a


  • Bryan Sullivan, AT&T
  • Serge Manning, Sprint
  • Lingli Deng, China Mobile


  • Status of project setup: Git, JIRA, Wiki
  • JIRA epics and story overview
  • Contributors to various epics/stories
  • R3 project plan and minimum goals
  • Events plan
  • Model analysis status
  • Tools analysis status
  • Model testing status

Meeting summary

  • The overall goal for the meeting was to share and get input on the project setup work so far and planning for R3
  • Most critical is the release plan:
    • MS0 needs to be completed by the end of March. The JIRA, Git, and wiki edits last week are intended to get us further toward that.
      • The resource estimate is intended to make it clear what time commitment is likely needed for the project to succeed, e.g. for Bryan a minimum 10% (4 hours/week, not counting meetings)
      • The JIRA epics/stories provide a starting point for specific items to make progress on
      • We can use the tasks/issues/etc associated with stories to plan detailed analysis steps and report progress
    • The minimum deliverables need to be agreed
      • docs: report (project goals and approach overview; architectural concept/backdrop for model-driven NFV analysis; SDO progress/convergence analysis; tools analysis; use case analysis; references)
      • use case tests
        • framework for model tests using various VNFM/NFVO open source software
        • specific use case tests to be implemented in R3
      • blueprints (as determined by analysis/tests)
  • the "Contributors" table at the bottom of the main wiki page is intended to help us focus on where we can add the most value; specific objectives
    • in general per area (SDOs, upstream projects, other mid-stream or OPNFV projects)
      • take lead on getting references to support/needs for info/data models and analysis related to them
      • publicizing the Models project and driving OPNFV engagement thru collaboration tools (eg. JIRA), e.g.
        • discussions on specific issues
        • ongoing alignment efforts (input/feedback, documenting consensus)
  • how to pick OPNFV and external projects to reach out to, from the list on the wiki
    • focus on overlap e.g. projects that need a medium for model-driven capabilities, or providing model capabilities
    • example is ODL; Bryan is looking into what YANG developers need and how YANG is used for service and device control
  • a model architecture would be good to help focus and explain our analysis of the role of models in VNF lifecycle mgmt
    • Bryan will draft a proposal
  • areas to focus on for 3GPP in the near term may include:
    • control/user plane separation for 4G (presumably different model components would be used for each)
    • also 5G with slicing disaggregation, etc
      • ON.Lab work on Mobile-CORD is relevant here
  • we'll continue on the list in the meantime and flesh out where we can contribute

Meeting ended at 15:59:29 UTC.

2016-March-7 Models Project Meeting #2b


  • Bryan Sullivan, AT&T
  • Ulas Kozat, Huawei
  • Prakash Ramachandran, Huawei
  • Uri Elzur, Intel

Open discussion of the project goals.

  • Prakash: suggest that the testing focus should be wider than CI/CD and Functest should come to own what we develop.
  • Bryan: that was the recommended plan
  • Ulas: intend to focus on SFC and continuous upgrades of VNFs and chain reconfig
  • Prakash: will also focus on scaling
  • Bryan: points to ONOS project proposal for Yang support:
    • we can share the same model for testing across SDNCs to validate interop
  • Ulas: transportability of Tosca templates is a similar goal
  • Ulas: testing SFC in detail will require validation of each hop in the forwarding
  • Ulas: more complex test cases will require a formal model for the expectations so a test framework can validate it
  • Prakash: distribution of the templates is needed for policy that is applied across different domains/locations

We may take a 2nd look at the meeting time for the AM PST call; Ulas has a conflict at 8-9 AM and this is why he was able to attend this session.

2016-March-7 Models Project Meeting #2a


  • Bryan Sullivan, AT&T
  • Mark Flauw, HPE

We had issues getting the bridge to work, still need the logistics setup with the help of LF:

  • GTM bridge
  • Git repo
  • Jira project
  • IRC meetbot for #opnfv-models

The 2nd slot ('b") for the Models weekly meeting will be at 4PM PST Mondays. Bryan will find a GTM link we can borrow in the meantime until LF allocates one.

2016-Feb-29 Models Project Meeting #1


  • Bryan Sullivan, AT&T
  • Serge Manning, Sprint
  • Mark Flauw, HPE
  • Pierre Lynch, Ixia
  • Christopher Price, Ericsson
  • Pasi Vaananen, Stratus
  • Steve Furr, NXP


Project goals

Open discussion and scoping (down) of the project goals for R3/C as needed.

Two main threads emerged in the call:

  • (1) SDO outreach and model convergence assessment/promotion;
  • (2) testing/demo of current model-driven design in current developer tools and platforms (including OPNFV Brahmaputra + extensions, and other adjunct tools e.g. orchestrators). Further clarification of these will take place thru Jira.

Project lead

In the meantime I can continue as project lead, but I would be fine with someone else stepping up to the role, since I'm already lead on one project (Copper).

Meeting format/cadence

Link to the doodle polls for the meeting times:

Bryan: Any day seems to work - we need to pick one, and to keep it simple I recommend Monday as well.

Tools: Jira, GIT, wiki, etc

  • a. Discuss how we will use these tools
    • Familiarity and regular use of the tools varies in the team. No specific suggestions so far on how to use the tools. We can just get engaged thru the tools and see who takes to what roles.

Suggestions made by Bryan during the call include:

  • Jira for setting up the general structure of focus/tasks and SDO interaction, getting more specific as needed as we go.
  • Git/Gerrit for documents and other artifacts in development, pending determination of how familiar/comfortable the team members are with editing or submitting change requests thru "patching" documents etc. In the meantime, Bryan can help out as editor and incorporate suggestions thru calls/email/etherpad/etc into docs as needed.
  • Wiki and etherpad for general idea development and documentation. Rich media (e.g. Powerpoint, Gliffy, Word) can also be used and captured on the wiki prior to ingestion into docs as needed. Most important is collection of info/ideas with minimal impedance.
  • b. Assign tasks to set them up
  • As above, we will figure this out as we go.

Jira task setup

a. Types of docs we will develop
  • Specific suggestions are still welcome, beyond what the etherpad intro covered (doc structure TBD)
    • introductory docs with background clarifying the role of different types of models
    • inventory of references to standards-published models, and models published through other places
    • references to UML modeling from SDOs and related tools
    • normalizing model representations
    • derivation of models from open source implementations
    • references to open source implementations of network functions that could be used in PoCs/demos
    • use cases to be validated and test strategy for each
    • reports published for each release covering
      • Cross-project, SDO, and upstream collaboration
      • use cases, models, platform components, and standards validated
      • issues identified
    • requirements for upstream projects based upon prioritized gaps
  • Chris pointed out the importance of working with the Functest and other testing teams on the use case validation.
  • Bryan agreed clarifying the intent to develop a use case testing plan and strategy, and after some initial manual use case development, to work toward the goal of integrating the use case tests into the OPNFV functest library for ongoing automated testing.
b. Process for reaching establishing/maintaining SDO member participation/communication
  • Chris suggested to create a dialog with the SDOs on how we can consume their models and tools.
  • Serge mentioned that he is active in 3GPP SA2.
  • Marc mentioned that he is the rapporteur for ETSI NFV-IFA015 Report on Information Modeling, and active in 3GPP SA5. Further we could reach out for 3GPP SA5 help from Edwin Tse (Ericsson), Zhou Lan (Huawei), and Anatoly Andrianov (Nokia). Edwin had represented 3GPP at the NFV-ISG Information Modelling Workshop-Louisville:
  • Marc mentioned that there is no expectation of a stage 3 doc from ETSI in this area;.
  • Bryan mentioned that Dan Druta will also be helping with ETSI NFV ISG interaction related to the IFA group, and that Serge and Marc in their SDO roles could help coordinate input/feedback to the SDOs.
c. Existing models and model-driven VNFdevelopment/management/orchestration open source projects
d. Use case development for model testing
e. Test environment for model testing
  • Bryan mentioned the goal to leverage community labs for the project, but in the meantime we need to find a lab environment for functional testing.
f. Expectations for gerrit reviews on issues of varioustypes (e.g. turnaround)
  • Bryan mentioned that unless we get into the mode of multiple direct contributors to docs etc thru git/gerrit (with gerrit-based reviews/comments/etc), he and the other committers can fast-track changes that are suggested and the group can review the results, suggest corrections etc.

Event planning

models/meetings.txt · Last modified: 2016/03/22 00:19 by Bryan Sullivan