Date
May 1, 2020 through December 31, 2020
R6 DISCUSSION
| TOPIC | DISCUSSION |
|---|---|
R6 CCSDK-based Solution | Project as part of CCSDK ( Yuriy Malakov )
|
R7 DISCUSSION
| Topic | Discussion | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
R6 / R7 ReadtheDocs | Read the Docs
| ||||||||||||||||
R7 TSC / Project Proposal | Configuration Persistency Service Project Proposal (Oct 25 2019)
| ||||||||||||||||
R7 Guilin Content / requirements | Requests for R7 Requirements are up. Guilin release - functional requirements proposed list Timeline - Sign-off for R6 is May 7. Historically M0 kickoff for R7 is May 7th PROPOSALS FOR R7 GUILIN FOR WHAT WE PLAN TO BE DOING IN R7:
SUMMARY OF THE STEPS FOR RTCDB "HOW IT OPERATES" (Reference):
A&AI FLOWS: STEP 1...6: Initial A&AI setup of DB (the setup of the DB with the initial set of all xNFs a "getall") STEP 1...6: A&AI Update (e.g. a new xNF is added or deleted)
| ||||||||||||||||
| R7 GuiLin Development | CMNotify specification
| ||||||||||||||||
| State Management | Bruno Sakoto - Listen to Recording from Question from Samuli Silvius - State Management was interesting could we get the basic arch picture and def lines of description? Having references e.g. to A&AI is better solution than planned C&PS to copy inventory data ANSWER: We are going to prepare a public page and share with you. | ||||||||||||||||
| Cell Introduction | Michela Bevilacqua - Introduction of a Cell Slides from SON Use Case - How do we think of LCM of a Cell from SON PoV & C&PS PoV. How will a cell be managed? a new cell is provisioned from a CU/DU. a "read" operation that a cell exists. CELL is a LOGICAL ENTITY ... Should a cell be seen xNF (PNF, VNF, ANF) How could ONAP discover there is a cell? does it need to be on-boarded? when creating a service, do you need to create a cell? with resources, will you also have a cell instance? today when we have a PNF we onboard the PNF package, create res descriptor & service descriptor containing the resource descr; done for any xNF. package is distributed at run time. Yang model for CU/DU has notion of Cell. process to sync up, discovering whether there is a new cell. OOF / SON / PCI - Need know about existence of a Cell. In that U/C "yes we need to know the cell, we assume that info is in C&PS" two kinds of errors - #1 go to config a cell "i don't have this cell" - #2 new cell exists and ONAP doesn't know about it. sync mechanism. What is the relation to C&PS, how could cell info be updated? Onboarding a xNF, when the xNF instance, the configuration mechanism you can get info about cells associated with a xNF. Cell is a service? that configures xNFs. | ||||||||||||||||
| Model Driven C&PS PoC | Proposal (by Ciaran Johnston et al) as a step of Model Driven ONAP, Model Driven C&PS. See slides in the Project Proposal page, and also in the R7 C&PS Wiki. Question: Graph DB? Answer: type of data from xNF to be hierarchical which would fit in a Graph DB. doesn't have to be that though. Likely to be one or more underlying database technologies. time series. Question: Model driven C&PS, uS on-boarding in CCSDK. If you plan to do modeling work in R7, consensus from Arch S/C. Answer: would need C&PS team, modeling, Arch S/C to be aligned. Want something that can be demonstrated/delivered in R7. Question: Are there dependencies on platform components? Answer: TBD - Looking at internal sourcing to get development resources. Sync with theodore johnson | ||||||||||||||||
| State Database PoC | Bell Canada Leading a PoC related to State management using the C&PS project. Communication via Kafka topic (DMaaP). Question: Are there dependencies on platform components? Answer: TBD Wiki: in progress |
PROJECT NAME DISCUSSION
| TOPIC | DESCRIPTION |
|---|---|
| Renaming the Project | RENAMING THE PROJECT ("Service" vs "Database") Database #1 HISTORICAL PRECEDENCE - The original idea was a configuration database available at Runtime. Use cases to store. Historical been with the project since the beginning. Name Inertia. Operators will use. Historical precedence within AT&T. SON & Slicing depend on this project (scope) #2 Contents that it holds - Contents is configuration parameters from the network. Name reflects the initial content of database. Service Since working on project proposal, it has grown, the same argument works against use. #1 QUALIFIERS - A wide variety of qualifiers could be put there and it still won't cover. Would move to something more abstract. Abose and beyond a standard IT database. For example service information, policy information, CLAMP information, exo-inventory (information outside of A&AI), topology information, application information - it is conceivable that many other types of information could before. Config if someone wants to add additional information a place to hold information. e.g. in Bell Canada's case they store more than just configuration, the Operational Data & Current state of network. Collectors that gather metrics in VES consumed put in stateDB. Tied to inventory objects in A&AI self-link from A&AI want to know about interface PNF trying to keep two together, the configuration & the metrics representative what is currently happening in the network. state of I/F being up-down that's more of a state vs a configuration. OpenDaylight Operational data store. Scalability. Collectors & StateDB is yang-driven if collector follows yang-model data store can hold-values. Monitoring interface track as state. #2 Confederation of Databases - Core/Edge/Far Edge - Historical DB - current DB #3 MEANS VS ENDS - Database is a "means" technology not an "end" goal An engine, hubcap is a part of a automobile that provides a service: vehicular motion. A database is a specific technology and implementation. Requirements around for current data & historical (temporal) careful not to talk about the technology. Potentially more than one database. Data Persistency Service → "functional" / Zu Tony Ben Configuration & Persistency Service / Joanne Tony Ben Operational Persistency Service / Bruno Tony Ben Run-Time Configuration DataBase → "technology" State (of Network) Database → what is state of network (storing more than just config) Configuration Operations Database (C.Op.DB) / Swami Golden Configuration Database / Fred (RunTime)(Operational)(Persistency) Policy Topology State Network Configuration Service Exo-Inventory Database |
RECORDING
| Date | Zoom Recording | Audio Only | |
|---|---|---|---|
| |||
| |||
| TSC Answers | ||
| PoC | ||
| |||
| C&PS May 28 Recordings | ||
| C&PS May 29 Recordings | ||
| |||
| |||
| |||
ATTENDEES WEEKLY ROSTER
| Date | Attendees | Topic |
|---|---|---|
| TSC Answer Discussion Architecture S/C presentations | |
| Benjamin Cheung Bruno Sakoto Toine Siebelink Samuli Silvius Swaminathan Seetharaman Joanne Liu Rudel Tony Finnerty Mike Elliott Theodore Johnson Marcin Krasowski Timo Puha Andy Mayer Vimal Begwani Bob Papa Ciaran Johnston Zu Qiang (Ericsson) Michela Bevilacqua Shankar N.K. Junfeng Wang Oskar Malm Marc-Alexandre Choquette Chuyi Guo | Bell Canada & State Management 5G Service Modeling & C&PS - TSC Answers/Response Michela - introduction of Cell Model |
| TSC Answers discussion Amar Kapadia in ONAP R6 Solution Brief | |
| Benjamin Cheung Toine Siebelink Tony Finnerty Oskar Malm Ciaran Johnston Zu Qiang (Ericsson) Fred Feisullin Michela Bevilacqua Bruno Sakoto Theordore Johnson Mike Elliott Joanne Liu Rudel Marc-Alexandre Choquette Samuli Silvius N.K. Shankar Junfeng Wang Claudio David Gasparini | Model Driven architecture PoC TSC Answers discussion (finished) |
| TSC - Agenda POC - Model Driven LF F2F DDF M0 for R7 | |
| ||
| Marcin Sebastian Krasowski Pawel Slowikowski (Samsung / NonRT RIC / A1 policy mgr) Tony Finnerty Toine Siebelink N.K. Shankar Michela Bevilacqua Ciaran Johnston Claudio David Gasparini Swaminathan S. Zu Qiang (Ericsson) Samuli Silvius Fred Feisullin Joanne Liu Rudel | Joint OOF SON PCI discussion TSC Q&A (pre-review) REQ-322 - Getting issue details... STATUS (M0) Ciaran's proposal for PoC R7 > R8 Project Prop Q: 3GPP-PM, Q: FM&PM |
| VF2F / DDF https://events.linuxfoundation.org/lfn-dev-test-forum/ OPEN POINT: CCSDK-2392 (OOF SON PCI) | |
| ||
| TBD | (TBD) | R6/R7 Demo of C&PS (the week of TSC) what was done (Ted J.), Deep Dive on Proposal; API I/F. |
| Joint Discussion with Harmonization Team | ||
| Joint Discussion with Network Slicing Team | ||
| Joint Discussion with OOF/SON/PCI team | ||
| Joint Discussion with A1 Policy Extensions | ||