SO Weekly Meeting 2019-12-4

End to End Layer 1 Service Management. Modeling the Optical Service

TO: SDC, ExtAPI

C: UUI, SO, A&AI, SDN-C, CCSDK

SO - C

A&AI - C

SDN-C - C

UUI - C

CCSDK-C

SDC - TO

ExtAPI - TO

Code will be committed by Fujitsu

AT&T

Orange

Fujitsu

SO: C

CCSDK: C

Integration:C

SO: C

CCSDK: C

Integration:C

Huawei commitment to SO,CCSDK,Integration

Enbo Wang

RANK #2

SO: C

CDS: C

Integration:C

SO: C

CDS: C

Integration:C

Huawei commitment to SO, CDS, Integration

SO: C

DCAE: C

Integration: C

SO: C

DCAE: C

Integration: C

SO, DCAE and Integration committed by Ericsson

SO: C

CDS: C

Modeling: DOC

Integration: C

SO: C

CDS: C

Modeling: P

Integration: C

Huawei commitment to SO, CDS, Integration

RANK #2

DCAE: C

SO: C

VID: C

DCAE: C

SO: C

VID: C

NOKIA Committed to DCAE, SO and VID Development

RANK #3

SDNC: C

SO: TO

Integration: C

SDNC: C

SO: C

Integration: C

SDNC, SO and Integration committed by Ericsson

APPC

CCSDK/CDS

SO

APPC - C

CCSDK - TO

SO - C

APPC - C

CCSDK - C

SO -C (Actor selection of CDS and APPC)

APPC - Nokia Shanghai

CCSDK - Tech Mahindra

SO - Tech Mahindra

AT&T

Nokia/Shanghai

Nokia/Poland

Tech Mahindra

Orange

SO: C

SOL003 Adapter: C

SOL005 Adapter: C

ETSI Catalog Mgr: C

SOL002 Adapter: C

SO (C): committed by Ericsson and others with scale back scope

ETSI Catalog Mgr (C): committed by CMCC

SOL003 Adapter (C): committed by Ericsson with scale back scope 

SOL005 Adapter (C): committed by Verizon with scale back scope

SOL002 Adapter (C): committed by Samsung with scale back scope

Ericsson

Verizon

CMCC

Samsung

Intel

E2E Network Slicing

There are two parts:

•  CSMF, NSMF in ONAP with external (core) NSSMF with a plug-in to SO is ArchCom approved.
  That is SO and External API impacts.
  
• External CSMF with NSMF in ONAP with SO plug-in for core NSSM is Arch com approved
• Arch clarification:
• no NSSMF (potentially PoC only) in ONAP
• There are impacts to OOF; It will be based on the HAS functionality, but modifying the constrints
• AAI -> new schema (no code change).
• SDC -> test only
• Policy -> test only.
• UUI has the CSMF portal and NSMF portal.
• SO has new workflows to reprent the CSMF and NSMF and "NSSMF adapter"
• External API exposes the NSMF NB APIs and shares the API definition with UUI.
• For a example E2E slice. There is a NSI (E2E) - (1:1) - NSSI (E2E) – (NSSI (core) + NSSI (RAN).; howver for frankfurt, we assume that the NSSMF is outside ONAP, hence the "core NSSI handling" is "e2e".

The above is a clarification consistent with previous archcom decisions, but detailing it more and is considered architecturally consistent given the scope (NSSMF outside ONAP).

The following is not approved:

• How the NSSMF is in ONAP
• Slice across two domains (i.e. core and ran)..

RANK #3

TSC:

• For the network slicing.  The following is a Go from architecture
  
  • SO plug-in to an External NSSMF (for core).
  • CSMF and NSMF representation in ONAP, and also allowing CSMF external.
  • What is not approved is NSSMF in ONAP; nor connecting two subslices together as that requires the NSSMF and that still needs quite some more discussion.

This should limit the impacts to SO and External API for Frankfurt 

Lin Meng's comment  (21st Nov):

a) 15th &18th Nov: LinMeng's Mail sent to TSC explaining the "exception".

b) 19th Nov: Steve's clarification of Arc decision in the first column.

c) 20th Nov: Swami's Mail sent to TSC requesting OOF and UUI inclusion in scope (resource commitments and PTL agreements available)

d) 21st Nov: LinMeng updated the columns for impacted modules, commitments based on the request sent to TSC ,  for TSC reference when in discussion

Please help change the status to Green

YES considering

#1 SO, ExtAPI  UUI scope only

#2 NSSMF is outside ONAP

#3 OOF is exceptionally added and will be reviewed at M2

--------------------

Lin Meng (21st Nov)

Confirmation:

1)Yes, we can deliver this feature for Frankfurt even without ExtAPI.

2) The impact in EXT-API for Frankfurt is only minimal impact, the resource has been identified and will be commited.

Please help change the status to YES

SO : C

EXT-API : C 

POLICY : TO

SDC : TO

A&AI : TO

U-UI : C

OOF : C

LinMeng updated on 21st Nov based on the request sent to TSC for including U-UI and OOF into scope, for TSC reference when in discussion

EXT-API : C (Huawei, Wipro)

SO : C (Wipro, China Mobile, Huawei)

POLICY : C (Wipro)

SDC: C (China Mobile, Amdocs)

A&AI : C (Huawei, Amdocs)

U-UI : C (China Mobile)

OOF : C (AT&T, Wipro)

LinMeng updated on 21st Nov:

Reply to TSC Concern:

1)Yes, we can deliver this feature for Frankfurt even without ExtAPI.

2) The impact in EXT-API for Frankfurt is only minimal impact, the resource has been identified and will be committed.

Wipro, 

Amdocs,

China Mobile, Huawei, Tencent,

AT&T,

Verizon

Intel

Aarna

Tech Mahindra

Integration with CDS

Change Management Frankfurt Extensions

MULTICLOUD: C

CDS: C

Integration: C

SO: TO

SDC: TO

CDS commited by Orange and Samsung

MULTICLOUD commited by Samsung, Orange and Intel

Integration commited by Samsung, Orange and Intel 

Extending HPA for K8S

MULTICLOUD: C

OOF:TO

Policy:TO

AAI/ESR:TO

SO: TO

SDC: TO

Intel