Introduction New team Member: Hanif Kukkalli
DB Schema
Software Status
M2 Milestones
- CPS R8 Release Planning
- Deployment in ONAP and related requirements such as documentation were agreed to be a major risk/unknown impact for this new team. Task investigating what is required need to be prioritized
- Benjamin Cheung kindly agreed to present detail about ONAP documentation/process in next week meeting
- Toine Siebelink will works with swam to identify E2E Network Slicing related user stories such as those required for the new models mentioned below.
- Bruno Sakoto will work with Toine to define a list of user stories for the Temporal DB aspects
- One all user stories have been identified a team meeting is required to agree what is feasible in the Honolulu time frame
Architecture Update
- Short Presentation by Tony Finnerty CPS-MVP-Component-Responsibility.pptx
- CPS consist of 3 main components
- DB Generic Yang data store
- CPS (core) CRUD access control, ownership
- xNF Proxy. Cache for CM data
- Additional we will have
- Model-Transform (DES Like modified view)
- Suggested name for API Mapp/DES like transformer: TemplateBasedDataModelTransformer
- TemplateBasedDataModelTransformer will be separate service from CPS and XNF Proxy. for reason of scalability and segregation of responsibilities
E2E Network Slicing Use Case
- Sandeep Shah has presented an overview 'new model' that will represent the 'external; data' not captured in the RAN Network model. Thing like Near RTRIC mapping.:
- 4 models are proposed, all of them contain at least E2E NW Slicing data and some also contain SON data.
- Approx. 15-20 queries are being proposed. However is is expected these can all be executed using the same core CPS and xNF Proxy functionality:
- qualified cpsPath query (get). assuming each model is stored/associated with its own Anchor. Or the models are tied together using an overarching parent model (yang module). To be discussed!
- Swaminathan Seetharaman and Toine Siebelinkagreed to track each model as a user story under
Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | CPS-168 |
---|
|
- The queries can be subtasks of a single query user story assuming all queries need the same basic CPS Cor and xNF Proxy functionality