CSMF and NSMF are implemented using SO bpmn workflow to support 5G slicing usecase. CSMF workflow will process the user input comes from portal and save the order information into a communication service instance in AAI. Then CSMF will send slice request to NSMF workflow and NSMF will start to create service profile, NSI and NSSI. Service profile is a logic concept which will only exist in AAI, it contains two AAI instances, one is a profile instance which will hold the slice parameters, another is a service instance which will be used to organize the NSI. NSI is also a service instance in AAI which will be used to organize NSSI. NSSI is the actual entity which will be created by NSSMF and an AAI service instance will also be created to represent NSSI in ONAP context. NSI and NSSI can both be shared and SO will query OOF for template and instance selection. A new process called Orchestration Task is created to manage recalibration of NSI&NSSI selection as manual optimization. A new SO adapter is created to be the adapter of NSSMF which will interact with external NSSMF for NSSI management.
Prague DDF slides:
Sequence flow:
New tables in catalogdb:
New tables in requestdb:
New API for Orchestration Task:
Method | URL | Description |
GET | /onap/so/infra/orchestrationTasks/{version}/ | Get all orchestration tasks |
GET | /onap/so/infra/orchestrationTasks/{version}/{taskId} | Get orchestration task by ID |
POST | /onap/so/infra/orchestrationTasks/{version}/ | Create orchestration task |
PUT | /onap/so/infra/orchestrationTasks/{version}/{taskId} | Update an orchestration task |
DELETE | /onap/so/infra/orchestrationTasks/{version}/{taskId} | Delete an orchestration task |
POST | /onap/so/infra/orchestrationTasks/{version}/{taskId}/commit | Commit an orchestration task |
POST | /onap/so/infra/orchestrationTasks/{version}/{taskId}/abort | Abort an orchestration task |
swagger changes:
https://gerrit.onap.org/r/c/so/+/100079
SO SouthBoud APIs to NSSMF(core only for Frankfurt):