...
KEY PRESENTATIONS & OVERVIEWS & RECORDINGS
| DATE | TOPIC | PRESENTER | DESCRIPTION |
| Apr 10, 2019 | Controller LCM API Evolution |
| |
| May 1, 2019 | A&AI GraphGraph Visualizer | Visualizer for A&AI Model Layout | |
| May 8, 2019 | A&AI Model Browser, Sparky | A&AI developer Model Browser to navigate and viewing attributes, object types & edge view Recording & Slides: Use Case Realization Call: May 8, 2019 | |
| May 15, 2019 | A&AI Run Time Browser (Sparky) | A&AI Run-Time Browser | |
| May 22, 2019 | Edge Automation Overview & Discussion | Central & Distributed Edge ONAP configuration. Topics include: Onboarding, Instantiation, Edge Orchestration, A&AI, Architecture, Work-flows, Multi-Tenancy | |
| May 29, 2019 | Modeling S/C , Use Case Project Teams, Architecture S/C Way of Working | Model S/C (Sub committee) contributions page: | |
| Jun 5, 2019 | Use Case slides for Dev. Forum | Use Case Realization Call: June 5 |
| , 2019 |
| July 10, 2019 | R6: PNF Software Upgrade Overview & Discussion | ONAP Read the Docs/R4 Announcements | |
| July 24, 2019 | R6: OOF/SON PCI Use Case Demo, Overview & Discussion | OOF / PCI / SON Use Case | |
| Aug 7, 2019 | 5G NRM (Network Resource Model) Configuration U/C Overview | yaoguang wang | 5G NRM (Network Resource Model) Configuration U/C |
| Aug 14, 2019 | ORAN Standards Harmonization U/C Overview | ORAN Standards Harmonization U/C | |
| Aug 21, 2019 | Modeling Sub-Committee guidelines & Use Case Interactions | Modeling S/C Process Wiki: Proposed ONAP Release Process Updates for Information and Data Modeling Use Case Tracking Template and Use Case Template R6 Modeling High Level Requirements Planning Page: ONAP R6 Modeling High Level Requirements | |
| Sept 4, 2019 | Licensing Management Overview | Introduction of Licensing Management in R6 | |
| Sept 11, 2019 | SDC & R6 Use Case |
| Impacts Discussion | Ofir Sonsino | Discussion with SDC PTL Ofir w/ the Use Case Teams |
SDC Impacting Use Cases & Discussion with Ofir
...
Epic 1: VNF onboarding
E1a: Alignment to SOL 001 (modeling discussions)
E1b: VNFD transforming mapping
E1c: Enhance security for xNF package artifacts.
Epic 2: VNFD Model mapping (modeling discussions)
E2: VNFD (onboarded) to Platform Model (modeling discussions)
Epic 3: S/W Version in Package
E3: S/W Version (modeling discussions)
SDC SUMMARY: Modeling discussion. SDC (Ofir) this acceptable; potential SDC impacts. Can Commit
...
- support generic workflow design
- CBA association enhancement to support PNF upgrade. Impacts on PNFD AID model
- CBA association enhancement to support VNF upgrade. Impacts on VNFD AID model
Jira Tickets SDC-2394 and SDC-2393
SDC SUMMARY: Tickets open already. SDC can Commit.
...
Generic Artifact Browser (GAB) Configuration File (No S/W changes)
Format of the artifact will be changing. If the format will not be changed, then it will only be configuration change, a default configuration; the configuration of the GAB based on the file format.
SDC SUMMARY: Nokia investing impact for the format changes; If proposal is accepted there would be no S/W change only a configuration change for the GAB. SDC can commit.
...
Enhance SDC with properties mapping from composite to nested service.
Foundation for nested svcs is there already. Modeling work. Jira items created. Is it SDC testing only? (1) nested svcs (2) testing.
SDC-2555 - SDC support of Network Slicing Demo in Frankfurt Open
SDC SUMMARY: What will the demo be? More details needed before Committing.
...
New Events & domains will be added to VES events. Should be no impact to SDC, push yaml artifacts to whomever is subscribing. If a new VES event/ VES domain as part of a yaml registration (in CSAR file) would SDC be impacted? New Domains. New Subscribers for DMaAP distribution; API to consume the SDC external APIs consume & parse the CSAR file. The consumers would have to use the existing solution (DMaaP parser). If the A1 interface (new) nonRT RIC + near-RT RIC might be new artifacts associated with that. New artifacts are configurable in SDC (depends on format) no coding impact. Infrastructure already exists. Assumption is that these artifacts would not be validate.
SDC SUMMARY: No SDC S/W impact; possible configuration impact. SDC can commit.
...
(empty)
SDC SUMMARY:
...
Onboarded artifacts for RunTime DB configuration.
building configuration database (global). The vendor run-time package. Yang models in design time; in distribution > downstream applications.
setup structure of Database. (1) get Schema from node; parameters (2) from Yang model under configuration mgmt supported via onboarding package.
As long as it is about existing or new artifacts, the infrastructure is there already. can create new types of artifacts; already supported in SDC API/UIs. > CSAR. Find relevant artifacts in onboarded package. Try to make use of yang model. APIs to create consumers to consume APIs; supply SDKs for components to use distribution clients. consuming the library is documented.
VES collector > CM Notify add VES registration (yaml artifact).
SDC SUMMARY: No SDC S/W impact, no new development needed; usage of existing design time artifact/onboarding functions (already supported). SDC can commit.
...
Self Serve Control Loop.
(1) Integrate w/ blueprint generator to include blueprint for DCAE into CSAR. Nokia will commit based on best effort. BPG (blueprint generator) DCAE instead of TOSCA-lab. otherwise wlil have to upload manually. upload JSON file and generate blue print in design time.
(2) Impact policy models dynamically in run-time. Entities in SDC catalog. Versioning only define pre-defined policy models can't import new ones.
SDC SUMMARY: (partially commit)
...
Eric Multanen , Liang Ding artifact Heat template envelope. passed through. artifact designed as cloud artifact in SDC. any parameters are invisible to SDC. figuring out how to address/solve that. Resources? how to expose parameters; digging into the artifact. Its type and artifact were hard-coded. Should be refactored but works. ideally specify the artifact name & type by user.
SDC SUMMARY: (needs further investigation)
...
Chris Rapposelli-Manzo , schedule opt/deconfliction might impact. W/F for change management. PNF S/W upgrade. Historically there has been SDC impact but no development.
service design W/F designer (amdocs made the original flexible W/F designer). hard-coded SO W/F (sent for every VNF)
choose model before W/F want it to be indep. artifact and attach to any model.
SDC SUMMARY: (needs investigation)
...
Have to start discussions. Mostly for now we will just be using existing features of SDC. May require small tweaks. Satoshi Fujii ; might be able to design with existing SDC features. Might be no impact. Other requirement might need importing svc template from remote ONAP instance. might be impact to SDC. Still some open questions. Still investigating. Review solution.
SDC SUMMARY: SDC can commit based on Fujitsu resources.
...
ONAP Ext API updates SDC catalog by invoking internal SDC API. Atif Husain . SDC-2378
SDC SUMMARY: SDC committed
| and SDC commitments. See the summary Table for SDC impacting Use Cases. | |||
| Sept 18, 2019 | M0/M1 U/C discussion, Preparation for Technical Conference Antwerp | Use Case Teams | M0 Use case Discussion - What is missing where are we now? M1 Use case Discussion - What are the next steps? Preparing slides for Use Cases at the Technical Conference Antwerp (for 5G/PNF use cases) |
| Sept 25, 2019 | A&AI & R6 Use Case Impacts Discussion | Discussion with A&AI PTL (Jimmy Forsyth) and Chandra Cinthala for R6 A&AI Use Case Impacts discussion and commitments. | |
| Oct 2, 2019 | DCAE & R6 Use Case Impacts Discussion | Vijay Venkatesh Kumar | Discussion with DCAE PTL (Vijay Kumar) for R6 Use Case Impacts discussion and commitments for DCAE impacting Use Cases |
| x, 2019 | SO & R6 Use Case Impacts Discussion | Discussion with SO PTL (Seshu Kumar) for R6 Use Case Impacts discussion and commitments. | |
| x, 2019 | Release Manager Discussion | David McBride | Discussion with David McBride of the Linux Foundation, the R6 Release Manager regarding practices, wiki page updates, Jira dashboard and what is a use case? |
| x, 2019 | RunTime DB Discussion | Discussion of the RunTime DB Use Case in R6 Frankfurt which introduces a Common Service Data Layer for a data lake to store configuration and operational parameters. | |
SDC Impacting Use Cases & Discussion with Ofir
| Use Cases | Impacts |
|---|---|
| PNF - Pre-Onboarding / Onboarding | Epic 1: VNF onboarding E1a: Alignment to SOL 001 (modeling discussions) E1b: VNFD transforming mapping E1c: Enhance security for xNF package artifacts. Epic 2: VNFD Model mapping (modeling discussions) E2: VNFD (onboarded) to Platform Model (modeling discussions) Epic 3: S/W Version in Package E3: S/W Version (modeling discussions) SDC SUMMARY: Modeling discussion. SDC (Ofir) this acceptable; potential SDC impacts. Can Commit |
| PNF - S/W Upgrade |
Jira Tickets SDC-2394 and SDC-2393 SDC SUMMARY: Tickets open already. SDC can Commit. |
| PM-FM Dictionary | Generic Artifact Browser (GAB) Configuration File (No S/W changes) Format of the artifact will be changing. If the format will not be changed, then it will only be configuration change, a default configuration; the configuration of the GAB based on the file format. SDC SUMMARY: Nokia investing impact for the format changes; If proposal is accepted there would be no S/W change only a configuration change for the GAB. SDC can commit. |
| Network Slicing | Enhance SDC with properties mapping from composite to nested service. Foundation for nested svcs is there already. Modeling work. Jira items created. Is it SDC testing only? (1) nested svcs (2) testing.
SDC SUMMARY: What will the demo be? More details needed before Committing. |
| ORAN/3GPP Harmonization | New Events & domains will be added to VES events. Should be no impact to SDC, push yaml artifacts to whomever is subscribing. If a new VES event/ VES domain as part of a yaml registration (in CSAR file) would SDC be impacted? New Domains. New Subscribers for DMaAP distribution; API to consume the SDC external APIs consume & parse the CSAR file. The consumers would have to use the existing solution (DMaaP parser). If the A1 interface (new) nonRT RIC + near-RT RIC might be new artifacts associated with that. New artifacts are configurable in SDC (depends on format) no coding impact. Infrastructure already exists. Assumption is that these artifacts would not be validate. SDC SUMMARY: No SDC S/W impact; possible configuration impact. SDC can commit. |
| Dist. Analytics as a Service | (empty) SDC SUMMARY: |
| RunTime DB | Onboarded artifacts for RunTime DB configuration. building configuration database (global). The vendor run-time package. Yang models in design time; in distribution > downstream applications. setup structure of Database. (1) get Schema from node; parameters (2) from Yang model under configuration mgmt supported via onboarding package. As long as it is about existing or new artifacts, the infrastructure is there already. can create new types of artifacts; already supported in SDC API/UIs. > CSAR. Find relevant artifacts in onboarded package. Try to make use of yang model. APIs to create consumers to consume APIs; supply SDKs for components to use distribution clients. consuming the library is documented. VES collector > CM Notify add VES registration (yaml artifact). SDC SUMMARY: No SDC S/W impact, no new development needed; usage of existing design time artifact/onboarding functions (already supported). SDC can commit. |
| Control Loop | Self Serve Control Loop. (1) Integrate w/ blueprint generator to include blueprint for DCAE into CSAR. Nokia will commit based on best effort. BPG (blueprint generator) DCAE instead of TOSCA-lab. otherwise wlil have to upload manually. upload JSON file and generate blue print in design time. Component spec > output Cloudify BP store > was manual (2) Impact policy models dynamically in run-time. Entities in SDC catalog. Versioning only define pre-defined policy models can't import new ones. SDC SUMMARY: (partially commit) |
| K8S Based Cloud Region Support | Eric Multanen , Liang Ding artifact Heat template envelope. passed through. artifact designed as cloud artifact in SDC. any parameters are invisible to SDC. figuring out how to address/solve that. Resources? how to expose parameters; digging into the artifact. Its type and artifact were hard-coded. Should be refactored but works. ideally specify the artifact name & type by user. SDC SUMMARY: (needs further investigation) |
| Change Management | Chris Rapposelli-Manzo , schedule opt/deconfliction might impact. W/F for change management. PNF S/W upgrade. Historically there has been SDC impact but no development. service design W/F designer (amdocs made the original flexible W/F designer). hard-coded SO W/F (sent for every VNF) choose model before W/F want it to be indep. artifact and attach to any model. SDC SUMMARY: (needs investigation) |
| Multi-Domain Optical Service Orchestration | Have to start discussions. Mostly for now we will just be using existing features of SDC. May require small tweaks. Satoshi Fujii ; might be able to design with existing SDC features. Might be no impact. Other requirement might need importing svc template from remote ONAP instance. might be impact to SDC. Still some open questions. Still investigating. Review solution. SDC SUMMARY: SDC can commit based on Fujitsu resources. |
| 3rd Party Op Domain Mgr | ONAP Ext API updates SDC catalog by invoking internal SDC API. Atif Husain . SDC-2378 SDC SUMMARY: SDC committed |
SUPPORTING DOCUMENTATION
| Document | File | ||||||
|---|---|---|---|---|---|---|---|
Use Case Impacts Spreadsheet |
| ||||||
RECORDING
| Recording | FILE | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Zoom Video & Audio (MP4) |
| ||||||||||||
| Audio Only (M4A) |
| ||||||||||||
| Playback (M3U) |
| ||||||||||||
| Chat (Txt) |
|
SUPPORTING DOCUMENTATION
...
Use Case Impacts Spreadsheet
...
| View file | ||||
|---|---|---|---|---|
|
RECORDING
| Recording | FILE | ||||
|---|---|---|---|---|---|
| Zoom Video & Audio (MP4) | Audio Only (M4A) | Playback (M3U) | Chat (Txt) |