Versions Compared

Old Version 9

changes.mady.by.user Lingli Deng

Saved on

compared with

New Version 10

changes.mady.by.user Lingli Deng

Saved on

Key

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

...

Upcoming call

Logistics

Start Time: 9 am US eastern (9 pm Beijing) Wed, March 21 1 pm US western Sunday, March 25

Length: 1  5 hour

Meeting room: https://zoom.us/j/9117271979

Proposed Agenda

TBA

Past calls

20170321

Agenda

  • Agenda bashing

  • R2 Status summary and priority

  • ONS workshop agenda

  • R2 VNFD DM clean up discussion (added for R2 priority)
  • (Tentative) Network Service Descriptor R2 Implemenation Discussion
  • Service Order Model (Maopeng)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

20170313

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

...

  •  

20170307

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.

...