Versions Compared

Old Version 15

changes.mady.by.user Lingli Deng

Saved on

compared with

New Version 16

changes.mady.by.user Lingli Deng

Saved on

Key

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

...

Upcoming call

Time

  •  May 2330, Wednesday 911:00 EDT, 68:00 PDT, 1517:00 CET, 911:00PM Beijingijing Time Beijing Time (UTC+8)

Proposed Agenda

  • TBA

Past calls

20180523

Agenda

  • 5 min Agenda Bashing
  • 20min 20 min Zengjianguo CCVPN Usecase Service Modeling Proposal
  • 20min 20 min Nigel Review Comments on Composite Pattern Revision Proposal
  • TBA

...

Participants

Lingli Deng, Joel Halpern, Nigel Davis, Hui Deng, Anatoly Katzman, Jianguo Zeng, Lin Meng, Michel Besson (TMForum), Michela Bevilacqua, Samuli Silvius, Victor Goa, Vishnu Ram OV, Xu Yang

Minutes

  • 5 min Agenda Bashing

               No agenda items added, went with the proposed plan

               Jianguo presenting IM Proposals for resource/service modeling regarding CCVNP usecase.

               Resource classes include site and VNP connector.

               More formal contribution would be handed in for followup discussion, with detailed class/attribute/relation definitions.

  • 20 min Nigel Review Comments on Composite Pattern Revision Proposal
        Nigel raised the concern that composite pattern should be applied in a proper level of hierarchy.
        Since there is not concrete counter proposal on the table, it is advised to move on with the existing proposal, and further excising the proposed skeleton with more detailed attributes/relation definitions and verifying if there is potential issues in the contexts of Casablanca use cases, especially those related to networking scenarios and seeking Nigel‘s constructive suggestions on refinement if needed.

Recording

Audio only

Video and Audio

chat

20180516

Agenda

  • agenda bashing
  • composite patttern proposal with usecase examples (Lingli)
  • wan proposal update (Lingli/Zhuoyao)

Participants

Lingli Deng, Joel Halpern, Nigel Davis, Anatoly Katzman, Gil Bullard, Chuyi Guo, Hui Deng, Lin Meng, Michela Bevilacqua

Minutes

  • agenda bashing

               no agenda items proposed, went with the proposed agenda, but Nigel requested and was granted time to do a partial presentation on his analysis on design pattern options

...

  • Nigel presented partly his anlaysis on design pattern options and will have a further discussion next week
  • next week call is rescheduled two hours earlier than the current time slot for having both Joel and Nigel participance in the pattern discussion

Recording

Audio only

Video and Audio

chat

20180502

Agenda

  • design pattern discussion (composite v.s. recursive)
  • wan service descriptor updated proposal and last call for comment

Participants

Lingli Deng, Andy Mayer, Kevin Scaggs, Hui Deng, Nigel Davis, Michela Bevilacqua, Xu Yang 

Minutes

  • Design Pattern Discussion (composite v.s. recursive)
    • Lingli introduced the wiki page for previous discussion summary and comparison page.
    • Nigel made oral clarifications, John would provide feedback on the Wiki.
    • Andy suggested and Lingli took the action item to provide concrete use cases examples for further discussion.
  • WAN Service Descriptor Updated Proposal
    • Currently in last call which would end by May 20th.
    • Nigel requested the wiki page link and would provide feedback online.

Recording

Audio only

Video and Audio

chat

20180425

Agenda

  • design pattern discussion (composite v.s. recursive)
  • wan service descriptor updated proposal and last call for comment
  • brain storming for R3 service IM working items (suggested by Kevin)

Participants

Lingli Deng, Alex Vul, Andy Mayer, Kevin Scaggs, Zhuoyao Huang, Hui Deng, Janusz Pieczerak, Xu Yang 

Minutes

  • Design Pattern Discussion (composite v.s. recursive)
    Suggestion from LA workshop to use composite pattern instead of recursive aggregation was presented to the modeling subcommittee the two weeks before for a call for consensus. There was no objection but two remaining requests for confirmation on potential comment from Nigel (by Andy) and a comparison between the two (by Kevin). 
    Lingli started an offine discussion thread including related SDO experts for a discussion and clarification of concerns on the two options.
    Due to the MEF meeting this week, neither John or Nigel made it for the discussion online. It is suggested and agreed  that  Lingli would post a public wiki track of discussion points and call for comment from the broader community before the discussion for conclusion.
  • WAN Service Descriptor Updated Proposal (Zhuoyao)
    Zhuoyao presented the latest proposal which is updated according to Nigel's comments and clarified all the class and attributes are currently a subset of ONF CIM. 
    It is suggested that a last call for comments from the community be initiated for two weeks until May 10th.
  • Brain Storming for R3 Service IM Working Items (suggested by Kevin)
    • Connectivity service/resource concepts:
      • Alex and Andy (with Nigel help) suggested clarify similarity/difference/mapping between different SDO concepts for connectivity resource/service. E.g.their relationship similiar connectivity modeling between VNFs and NSDs (Alex), ONF FC concept for connectivity, connectivity as a service, SFC, virtual link.
    • Service component/pattern/flavor
      • Kevin: service component, pattern, service flavor. Potential extension to ESTI concept of network service, suggest to take a reference to OSM also. Alex could help set contact for OSM TSC Chair for later discussion.
    • Service usage/performance monitoring/close loop
      • Lingli and Andy: usage/performance metric modeling at service, potential usecase for assurance, close loop, dace, service level event
    • Service order
      • Andy: service ordering model, license, external API
    •  Coorindation needed with other tracks, and conduct the brain storming at a higher level is suggested

Recording 

 Audio only

Video and Audio

...

Part of the ONAP Friday morning modeling session in ONS 2018 (30 March 2018)

Agenda

0 Agenda bashing

Service session 
1 Yangxu - Service IM Status and Observations 
2 John - MEF MCM Proposal 
3 Jianguo - ONAP R3 Service IM Proposal 
4 Lingli - Service IM Usecase Proposal (Skipped for time limitation) 
5 Discussion on next steps

...

  • Cardiality correction by John
  • Suggest to move to composite pattern  instead of recursive aggregation   
  • Decoration pattern is FFS   
  • Terminology need to be defined (e.g. clarifications on service component as with the one in MEF)

20180325

Agenda

  • ONAP R2+ service IM Discussion Review and Proposal

...

The current status of service IM and my observations (Xu Yang)  (Skipped for time limitation)
Discussion (Partially covered during the flow of discussion)

Minutes

• ONAP R2+ service IM Discussion Review

...

  • The current status of service IM and my observations (Xu Yang) - delayed due to time limitation
  • Discussion for follow-ups
  • Lingli provides customer-facing business scenarios as input for service model discussion and comparison by Tuesday;
  • For Friday workshop, each presenter (including SDOs/individuals) is expected to provide their respective proposal models and with the context of customer facing business scenario;
  • Based on which, the team is expected to develop a more clearly scoped target and collaborative pattern for R3+.

20180321

Agenda

  • Agenda bashing

  • R2 Status summary and priority

  • ONS workshop agenda

  • R2 VNFD DM clean up discussion (added for R2 priority)
  • Network Service Descriptor R2 Implemenation Discussion
  • Service Order Model (added to the agenda, but deferred to next meeting due to time limit)

Minutes

  • Agenda bashing
    Andy suggested to add service order model to the agenda.
    Hui suggested to add VNFD DM discussion for finalizing R2 spec.

  • R2 Status summary and priority
    Agreed to continue work on nsd for R2 implemenation, and defer WAN descriptor discussion for R3 discussion starting next call.
    And service order proposal to R3 discussion.

  • ONS workshop agenda
    Deng Hui suggest to

    1. Add project PTL to explain how they implement service today SDC, SO, A&AI
    2. YANGXU is presenting the relationship between SERVICE and network service
    3. Multi SDO presentation about service IM , tmf/mef/onap
    4. Offline to build tiger team to design service IM

    Andy suggest to

    1. Add service order model
    2. Further Discuss NS 
  • Network Service Descriptor R2 Implemenation Discussion
    NS model as service component added in the R2.
    Maopeng and Anatoly need to discuss more tosca grammar details related to NS model and update the NS model.
  • Wrap up

20180313

Agenda

Minutes

  • Agenda bashing
    Added a time slot for Network service VL Discussion.

  • WAN service IM/DM Proposal (Zhuoyao)

    • WAN (Service Component) IM
      Need clarifications on relationship with ONF CIM and/or TAPI model.

    • WAN (Service Component) DM
      Need clarificationson relationship with parallel TOSCA Data Modeling practice at ONF and avoid collision if possible (e.g. in terms of naming conventions)

  • Network Service Discussion
    • NetworkService Model Diagram (Maopeng)
      Add reference to IFA 014 2.4.1 when appropriate.       Need sync with SDC/VF-C for implementation plan in R2.
    • Network service VL Discussion  (Nagesha)
      Very briefly done due to time limit. Will provide wiki page contribution and kick off further discussion.
  • Wrap up

Recordings

20180307

Agenda

Minutes

  • Agenda bashing (Lingli)
    No comments received and proceeded with the proposed agenda.

  • Service IM recap and update(Kevin) 
    No update made to the clean version as agreed back in December F2F. (Kevin)
    Concerns raised about potential alignment conflicts with MEF service models, which would be discussed further in March F2F.     (Mehmet and others)

  • Service DM proposal (Maopeng)
    It is clarified that both network service and wan service are derived from service component. The network service as it currently represented is a simplified subset of Network Service as define by ETSI NFV, without VNFFG or Deployment Flavour etc. (Maopeng)
    UML class diagram for corresponding IM design was requested to be added. (Andy)
    More sophisticated design for virtual link might need to be considered for some service provider scenario, contribution to be expected in later discussion. (Thinh)
  • WAN service modeling proposal (Zhuoyao)
    It is recognized as a good approach to proceed, suggest to add consideration for covering both intra-DC connectivity and inter-DC connectivity for underlay. (Gil & Andy)
  • Wrap up
    All participants are encouraged to leave their comments to the wiki discussion pages for further discussion and better tracking.

Recording