Versions Compared

Version Old Version 51 New Version Current
Changes made by

LIN MENG

LIN MENG

Saved on

Key

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

This page hosts information about discussion calls dedicated to R3+ service modeling.

...

Logistics

...

Proposed Agenda

Past calls

20181024

Agenda

  • Architecture F2F Meeting Planning From ServiceIM perspective
  • View file
    nameArchitecture F2F Planning - Service IM.pptx
    height250


...

              Will start service model discussion for R4 on 10.10.

20180829

Agenda

  • Continued discussion about NS onboading or other issues. 
  • Review Service model in ONAP Information model in Papyrus.

...

Lingli Deng (China Mobile), Gil Bullard (AT&T), Mehmet (Verizon), Thinh Nguyenphu (Nokia), Xu Yang (Huawei), Andy Mayer (AT&T), Hui Deng (Huawei), Emmanuel Sarris (Vodafone) , Maopeng Zhang (ZTE)

Minutes

  • Continued discussion about NS onboading or other issues. ?Proposed Approach for ONAP Runtime Support of Network Service Onboarding?
    • Agreed ONAP should be evolving as a generic platform offering features as expected by the service providers in its service provisioning
    • There is a difference in defining a service from the rest of industry from the perspective of a consumer rather than the implementation modules/system (as a collection of constitute resources, configuration scripts, etc.)
    • Agreed to continue discussion on this and welcome Mehmet's presentation on MEF Interlude
    • A request to clean up on the wiki workspace for further input to network service descriptor is raised
  • Review Service model in ONAP Information model in Papyrus.

...

1. VFC requirements for NSD (Yan Yang)  

2. Resource/Service IM decision on NSD  (Xu Yang)

3.  NSD Proposal (maopeng zhang)

...

Maopeng Zhang, Xu Yang, Hui Deng

Minutes

1. Yan presents VFC requirements for NSD. VFC project implement ETSI NFVO, which needs to consume the NSD. VFC also needs standard NSD. VFC would like to receive the NSD from SDC. In the long run, VFC also needs to receive NSD from OSS and BSS.
2. YangXu presents NSD updates from the resource IM calls ?Proposed Network Service Descriptor Model?. From his understanding of previous calls of reousrce IM CALL, NS is a composition of VNFs, VLs and topology of how to construct a service, which are all in the domain of resource. NS is different from the service we want ONAP to handle.
3. From Lingli and Andy's discussion: For IM, we agreed to move NSD to resource domain for Casablanca. But for Dublin+, there are considerations on having also service domain reflection on resources (including network service).
4. MaoPeng presents NSD proposal: NSD requires to do some limitation in NFV resoures composition, not all the SDC resources and substitution mappings to NS TOSCA node.
5. Currently we are working on enabling interworking commercial NFVO deployment with ONAP community version
6. For R4+, the relationship between Service template and Network Service Template would bette be guided jointly by Architecture and Modeling subcommittee, for NSD in R3, please Maopeng’s help to propose to SDC and check whether it could be acceptable in SDC for such new node type.

...

Hui Deng, Kevin, Andy, Thinh, Xu Yang, Lin Meng

Minutes

service order - Kevin

  • Kevin illustrate the Papyrus model for the service order, including ServiceOrder and ServiceOrderItem class, based on TMF model (TMF have a root class named businessInteraction of serviceOrder, similarly businessInteractionItem  as root class of serviceOrderItem, but as ONAP doesn’t need business interaction, so here Keven delete the root classes)

...

  • Gil asks whether the discussion about service atomic and service composite was closed?He suggests to allow resource to be directly associated with service, so that a composite service could be comprised of resource or other service or both. Lingli said last time in the discussion, they remove the aggregation relation between service atomic with resource, instead they build a mapping relation between service and resouce. Lingli said she will publish that for offline reading.
  •  Zengjianguo presents service IM proposal for CCVPN
    1. Three services are established for CCVPN service:VPN_infra service, Site_DC service and Site_Enterprise service.
    2. The content of Config_resource in Site mainly include the location and site service type?this kind of information actually belongs to service level. But as it's common sense that SDC  d doesn't support service configuration, we call it config_resource. The restriction that service can't have its own attributes in SDC result in defining an individual part(here we define it as config_resource) in the implementation of DM. But people all agree that the design of IM should be defined in a proper way. We suggest model committee to bring up this restriction to SDC team to solve it.
    3. Chenchuanyu explains how alotted resource works: it combines two instanced service by setting the parameters for VPN like UNI. Such information is confirmed only when a site is placed in. Doing in this way makes the deplyment of site flexible.
    4. There is argument on how to store resource in VPN_infra service like whether to store it in AAI. Still need to be discussed.

...

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

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

...