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
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!
The goal for MVP is to deploy alternative 2 here (CPS core and NXF-REST proxy in one service) with OOM. With a possible inclusion of Temporal DB RETS interface when available (alternative 3)
Misc
The schedule for the LFN Developer & Testing Forum is now live here. Tony Finnerty& Toine Siebelink will be presenting CPS-NF-Proxy MVP on Thursday Toine Siebelink will be presenting on using Spock and Groovy for unit test
E2E Slicing team will provide data sample and query information when ready
Jira
server
ONAP JIRA
serverId
425b2b0a-557c-3c0c-b515-579789cceedb
key
CPS-199
E2E Slicing team will provide query and 'update' information when ready
Jira
server
ONAP JIRA
serverId
425b2b0a-557c-3c0c-b515-579789cceedb
key
CPS-200
E2E Slicing team will provide query and 'update' information when ready
Breakdown of user stories discussion:
New function: retrieve DataNode WITHOUT children, do we need this?
Do we need separate user stories for:
Store & retrieve (keyed) Lists
Store & retrieve leaves (standard attributes)
Store & retrieve leafLists
Alternatively work on E2E Slicing models and handle 'bugs' for what is not working Team agreed to handle functionality through bugs as issues with E2E Models and Data samples arise Tests wil need to be added for specific functionality like stores leaves, leafLists etc
Update functionality (no epic or user stories yet!)
E2E network slicing only required CSP updates (no forwarding of updates to NF required as this is done elsewhere already)
What types of updates do we need (what is achievable in Honolulu) Ahila suggested to use Yang Patch payload, see https://tools.ietf.org/html/rfc8072#page-5 Will try to get more details by next week.
