ONAP Service IM Minutes 20190306

Participants

@Kevin Scaggs @Andy Mayer @guochuyi @Xu Yang @Gil Bullard @Borislav Glozman @Fei Zhang (Ericsson) Bob Papa (AT&T) @Thinh Nguyenphu (Unlicensed) @John Quilty Fukuda (Fujitsu) @Lingli Deng

 

Agenda

  1. Agenda Bashing

  2. Nested Service Modeling (@Kevin Scaggs & @guochuyi ) Composite / Atomic Service

  3. Slicing Service Modeling 

    1. Slicing Proposal Update (@Borislav Glozman & @guochuyi ) Enhanced Service Information Model for Nested and Shared Services

    1. Readout of Resource IM call on alloted resource and slicing modeling (@Xu YangONAP R4 Resource IM Call 2019-3-4

  4. Root Hierachy Sharing @Kevin Scaggs

Minutes

  1. Agenda Bashing
    @Kevin Scaggs requested to do a root hiearchy sharing if time permit it. Add to the bottom of agenda list.

  2. Nested Service Modeling (@Kevin Scaggs & @guochuyi ) Composite / Atomic Service
    Need to do a final cleanup for minor edits as tracked on the wiki page Composite / Atomic Service @guochuyi , and hand in for call for approval @Andy Mayer .

  3. Slicing Service Modeling 

    1. Slicing Proposal Update (@Borislav Glozman & @guochuyi ) Enhanced Service Information Model for Nested and Shared Services

    2. Readout of Resource IM call on alloted resource and slicing modeling (@Xu YangONAP R4 Resource IM Call 2019-3-4

    Agreed on Monday on the separation of the discussion between the "nesting" of Network Slices and Network Slice Subnets and the REsources that comprise the Network Slice Subnets (DUs, Allotted Resources from DUs, etc.).  @Gil Bullard
    Suggested to call for approval of nested services modeling aspects to move on to runtime implementation considerations (SO). @Andy Mayer
    Will have an offline discussion on runtime implementation of slicing creation from service to resource on Thursday and get back to see if anything to be updated to the current proposal. @Borislav Glozman
    Requested access information to the Thursday discussion @fred feisullin @Borislav Glozman
    Requested help from the 5G usecase team for providing an RAN slice example to "run through" the proposed model. @Thinh Nguyenphu (Unlicensed) @Benjamin Cheung
    Suggsted to supplement the current diagram with class/attributes definitions. @Borislav Glozman @guochuyi 

  4. Root Hiearchy Sharing @Kevin Scaggs
    Skipped for the limit of time, and will be on for next week.