ONAP Service IM Minutes 20190320

Owned by Lingli Deng
Last updated: Mar 24, 2019 by guochuyi
2 min read

Participants

@Kevin Scaggs @guochuyi @Xu Yang @Borislav Glozman @Former user (Deleted)  @Lingli Deng @andreik @fred feisullin @Fei Zhang (Ericsson) @Andy Mayer

Agenda

  1. Agenda Bashing

  2. Reminder of vote for Nested Service Modeling @guochuyi

  3. Enhanced Service Information Model for Nested and Shared Services Reivew @Borislav Glozman@guochuyi

Minutes

  1. Agenda Bashing No bashing received, moved on as planned.

  2. Reminder of vote for Nested Service Modeling @guochuyi
    The deadline of voting on Nested Service will be 21th March.

  3. Enhanced Service Information Model for Nested and Shared Services Reivew @Borislav Glozman@guochuyi

            a. Clarify the conception of ServiceProfile:

  •  

    • ServiceProfile is originally to describe SLA, Kevin thinks SLA is “agreements”, can be associated with license model.

    • Gil points that SLA is UE experience, which related to access point, while configuration is not, so how to distinguish the differences between SLA and configurations?

    • Borislav thinks service profile comes from 3GPP, which is not about SLA or contract for license, it is like a contract between services, and is not for customers. Network slice needs to know the requirements of this service, and instance should be created or picked according to the requirements.

            b. Filter

  •  

    • Gil thinks when receive slice request, in run time, it will be decomposed to “subslices” and find proper instance. But filter is rules to find compatible instance.

    • Borislav clarifies that filter rules are for orchestrator to map a requirement to NS.

            c. Nested service structure

  •  

    • Nested service is must, but need a better understanding. Top level service needs understand the purpose, configuration should be attached to the run time. Bottom level service has the access points (SLA understanding).

    • How to construct nested service influences the rules for filter.

            d.  @fred feisullin will help to give an example of transport slice (target next week to present), to verify the model feasibility, there will be an offline talk before the presentation.

            e. Slice model needs SDC to support nested service and service configuration, run time should support to specify templates.

Recordings

chat.txt

audio_only.m4a