...
| Time | Item | Who | Notes | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 15 min | A&AI Platform Evolution Items | A&AI Schema Change - PNF-id vs PNF-name PUSH TO R5 EL ALTO. Discussion Will be loaded to Mar 6, 2019 U/CR call. (Jimmy has uploaded to): USE CASE REALIZATION MEETING (Notes 2019-03-06)
(0) ARCHITECTURE - Review with Architecture Sub-Committee. Recommendation to implement in R5. Start early in R5. (1) RELEASE NOTES - to follow new rules , give clients notice that a breaking change comes in the next release. Add a release note to R4/Dublin Release to call out. So people mitigate need for migration. (2) MIGRATION STRATEGY - will in R5, all the objects will have the key as the name. Id will have to be vetted, detect duplicates. Migrate the URIs. Warn, Migration strategy. If there are more "regular" LARGE A&AI Schema changes need a process to introduce changes. Names vs UUIDs, there might be others that would also require migration. (3) SOCIALIZE - Socialize as breaking change as far back as it goes. Jimmy has contacted key players to inform that this has been delayed. (4) MODELING & U/C COMMITTEE - Modeling sub-committee. Produce UML based on A&AI data model with papyrus model that modeling sub-committee can use, way we can talk about it so committee can. Widespread understanding of how A&AI is modeled and how keys work. | |||||||||||
| 15 min | BBS U/C Platform evolution | BBS Use Case in R4.
| |||||||||||
| - | PNF Software Upgrade Use Case (Scope Change) | Huawei is leading the new (re-scoped) PNF Software Upgrade with Ansible. Created new Jira tickets in SDN-C. PTL Ajay has committed. API defined, Req, Integration. Roll-back testing. Reuse of Casablanca Tests. | |||||||||||
| - | Platform Evolution for Data Persistency | MariaDB and platform evolution for run-time persistent configuration information. Used in the OOF/PCI U/C. DCAE Post-gress DB. Primary inventory in A&AI. Base another database off of that. ConfigDB doesn't publish updates. PCI U/C if SDN-R knows of a config change it updates. SDN-R publishes changes on DMaaP. Network Maps & Topology & History. Timestamp. Controllers keeping state of network. | |||||||||||
| - | Firewall U/C carry-over to R3 | SOL005 The A&AI Jira is
| |||||||||||
| 5 min | PM Dictionary Schema GUI display | Focus is on making the FM Meta-Data GUI work first. PM dictionary "stretch goal". Scope Change: SDC-2095 - R4 5G U/C SDC: PM Dictionary GUI Display from PNF Onboarded Package Open | |||||||||||
| 5 min | PNF Pre-Onboarding & Onboarding Use Case | ETSI SOL001/SOL004 extension PNF Modeling PNFD. Mapping onboarding PNFD and ONAP "Platform" info/data model Requirements work. Package requirements Section 7.2. NFV meeting introduced not-backward compatible change in SOL004 2.6.1, adding delay to the project. Updates to the TOSCA Meta and the Manifest File, NFV CR NFVSOL(18)000746r3 CR review will be held Mar 14, 2019. VNF-SDK Development Updates. | |||||||||||
| SO (Service Orchestrator) Service Instantiation Flow | Developing a SO Service Instantiation Flow. First flow was SDC distribution: ARCHCOM: InfoFlow - SDC Service Distribution | ||||||||||||
| 20 min | RAN Network Slicing Examples | Discussion RAN Network Slicing Examples Models of VNFs/PNFs. Simulators, descriptors for VNFs/PNFs and build a ONAP service. DESCRIPTORS NEEDED - Using descriptors to onboard. Build a Service. Want PNFD/VNFD modeling core, VNFs need to have descriptors for NSSF, NEF, NRF, PCF, UDM, AF, AUSF, AMF, SMF. PNFDs for CU/DU. add descriptors in services that can wrap the descriptors. Add properties. How slice impacts the resource. Need to characterize a service as a slice how do we when reserve the resources and to what granularity. FILTERS - contribution from Borislav, ability to share services a network service want a nested service. Nested services can be dedicated or shared. Once composite service is instantiated the nested service is instantiated. Shared new instance isn't instantiated, instead orchestrator tries to find an existing instances. How to choose which existing instance (use criteria to pick). Filter on the composite service "I want to find a nested service with specific properties) e.g. latency < xyz. NESTED SERVICE - Service A which inside/contained has Service B. Non-Recursive. A "complex" vs a "Simple" service. Should network slices be "orchestrated"? Filter applied to SDC. Concept of Affinity. Coupling of resources vs sharing resources. CPU pinning, allocating all processing to the CPU. Capacity management. allow a higher level layers to do provisioning ONAP doesn't maintain the rules, the service itself maintains info. Policy Rules vs Rules associated with how the service is managed & scale & isolated. Slicing is a configuration that is a virtual overlay on existing components, maintaining that view of what the slice looks like & the associated resources. A&AI and SLICING - A&AI would have bookkeeping of ANR different & non-overlapping. Slices where you cant share resources, what is "nailed up" and what is not. I can't touch these NF, but I can use those other NFs. A&AI Framework to track. Identify the available Resources. Modelling. A&AI, SDC, VIM, orchestration. Needs to know how to create slice-related services. Start with SDC. If creating a service, create all the associated resources (xNFs) allow OSS/BSS to take advantage of infrastructure. Don't maintain policies to track connections. To maintain slicing view this would impact components in ONAP. in SDC how do i create slices, resources assigned to slice and how to inventory a slice. E.g., EPC as a service, partitioning resources two or more EPCs. Non-overlapping this EPC#1 is only for IoT w/ this BW. EPC#2 for Video w/ High-BW. EPC#3 for Bronze subscribers for eMBB. Granularity of control down to the VIM level. What needs to be added to information model & descriptors. From ONAP perspective in A&AI 3 instances of vEPC service. Notion of a slice is at the OSS/BSS level: vEPC#1 mapps to IoT. ONAP orchestrates the virtual resources w/ the vEPC#1. A partition with a practical example. | |||||||||||
| 5 min | PNF Plug and Play Requirements Work | M4 Milestone Requirements work for PNF PnP
2. STEP 37a STATE CHANGE UPDATE - State Change VES Event (type = State Change) Old state & New State. CPE Authentication Notification BBS U/C is using this flow to "update" ONAP letting ONAP know that the PNF has been successfully been activated. From VES Event Listener Document:
| |||||||||||
| 5 min | NetConf U/C | Oskar Malm | REQUIREMENTS - Requirements impacts? Expecting impacts. EPIC in jira/user stories. In progress. | ||||||||||
...