ARC 2019-11-19

Clarifications to ONAP Frankfurt release.

• 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).

2019-11-05 Archcom

Continue the discussion about the internal NSSMF (which is poc level for frankfurt).

https://wiki.onap.org/download/attachments/71833465/ONAP_E2E_Network_Slicing_Arch_Com_05Nov_2019_v2.0.pptx?version=1&modificationDate=1573035301273&api=v2

• Continue discussion in two weeks
• There was a question regarding about the use of policies as an alternative.

A joint presentation for the Frankfort network slicing was created:

2019-10-29 Archcom.

• Scenario 3 is CSMF and NSSMF outside ONAP, NSMF is within ONAP.
• Scenario 4: CMSF and NSMF are in ONAP, NSSMF is outside ONAP.
• There was a question about whether ONAP is instantiating the "domain - NSSMF"
• Its only the core slice in frankfurt!
• There was a question about the  "bottom up" vs "top down".  Bottom up assumes that the network is already there.
• There was a question what was the interfaces being refered to.
• Vimal was suggestiongthat we take the bottom up first.
• More work is required on how NSSMF maps into ONAP.
• Frankfurt: plug into SO to external NSSMF.  behond that is a PoC.
• The APIs are still under discussion.

2019-10-22 ArchCom:

Swami presented:

• Not covering the closed loop control (monitoring and taking preventative action).
• Proposes that the CSMF and NSMF, and NSSMF; also allowing to connect to an external NSSMF.
• Slide 06 – indicates data lake -> discussion showed that this is the run-time database that is being discussed.
• This is considered as a usecase.
• There are 4 deployments.
• All are in ONAP
• CSMF is outside ONAP
• CSMF and NSSMF are outside ONAP
• CSMF and NSMF are in ONAP.

• Incremental proposal; the NSSMF in ONAP needs further work.