- Manager (TBD)
- Invokes Policy Adapter (TBD)
- Invokes OOF Adapter (TBD)
- Invokes Notification Manager (TBD)
- Invokes FM/PM Event Manager (TBD)
- Invoke K8S Client (TBD)
| Yes | Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | SO-2843 |
---|
|
|
|
| Create NS | SOL005 NBI Handler invokes the Create NS workflows which do the following: <Create NS> Image Modified
- Initialize Parameters: set csar_id, ns_name, description, global_customer_id, service_type from the parameters to the execution variables
- Get NS Package from ETSI Catalog Manager: query ETSI Catalog Manager for an NS package with the given csar_id
- Check NSD Validation: check if the NSD package exists in the ETSI Catalog Manager DB; otherwise generates errors
- Check if an NS Instance (with the ns_name as the key) exists in the NS Instance DB (NFVO_NSINST DB table)
- Create NS Instance in NS Instance DB: stores the NS instance data into the NS Instance DB with the status= 'NOT_INSTANTIATED'
- create an ns instance id (uuid)
- store ns_instance_id, ns_name, ns_package_id, nsd_id, nsd_invariant_id, description, lastuptime, global_customer_id, service_type
- Create NS instance in AAI: store an NS instance data to AAI as follows:
- service-instance-id = ns_inst_id
- service-instance-name = ns-name
- service-type = SERVICE_TYPE (NetworkService)
- service-role = SERVICE_ROLE (NetworkService)
- get nsInstance from GetNSInfoService
- return 201 Created with the NsInstance
- Send NsIdentifierCreationNotification
| Yes | Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | SO-2867 |
---|
|
|
|
| Instantiate NS | SOL005 NBI Handler invokes the Instantiate NS workflows which do the following: <Instantiate NS> Image Modified
- Initialize Parameters: set ns_inst_id, plan_input
- plan_input = job_id, ns_inst_id, dst_plan, additionalParamsForNs, additionalParamsForVnf, additionalParamsForPnf
- dst_plan = get nsd with the given nspackage_id, input parameters
- Get an ns instance id from the parameter
- Create a Job: create a job for the ns instance id and return a job_id
- create a job object with job_type = NS, job_action= NS_INST, ns_inst_id
- store it to NFVO_JOB database table
- create an occ id for the ns instance id
- Update the status of ns_instance record in DB: update the ns instance id row of the NFVO_NSINST db for status (= INSTANTIATING)
- get a ns instance data from DB for the given ns_inst_id: get an NS records from the NFVO_NSINST db for the ns instance id
- collect parameters for NS: get and store additional Parameters for NS
- Get an VIM id: get an VIM id from the cloud owner and cloud region parameters
- Get VNF VIM: get an VNF VIM from the location constraints
- set the job status with 'Start Query NSD'
- get NSD from ETSI Catalog Manager & Parse NSD: get and parse a nsd for the ns package id
- Update NFVO_INST db to modify nsd model (dst_plan)
- Prepare each VNF request: get VNF list from the nsd
- for each VNF,
- get vnfd_id, vnfm_type, vimId, s_vimId (with "cloud_owner"_"cloud_regionid")
- select VNFM by leveraging AAI ESR
- store VNF pararms in collection, with vnf info including vnfmInstanceId
- Set VL: set vl vim id
- for each VNF
- if VNF has dependencies, for each dependency
- add VNF properties and id into vl_vnf array
- for each VLs
- get vnfdId and vimId
- add vimId into VL array
- Update NFVO_NSINST db: update NFVO_NSINST with the nsd model
- get PNF parameters
- get VNF parameters (from VNF params above)
- set up Plan Input with job_id, ns_inst_id, tosca plan, additional NS params, VNF params, PNF params)
- start workflows with the job_id, ns_inst, plan_input, occ_id)
- get service template id from ETSI Catalog Manager
- get process id from ETSI Catalog Manager
- workflow run with data (process id, params = plan input)
- createVL
- createVNF
- createSFC (Service Function Chain)
| Yes | Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | SO-2868 |
---|
|
|
|
| Terminate NS | SOL005 NBI Handler invokes the Terminate NS workflows which do the following: <Terminate NS>
Image Modified- Initialize Parameters: Get an ns_inst_d, job_id and request_data from the parameters
- set terminate_type, terminate_timeout from request_data
- set job_id, ns_inst_id
- set occ_id by creating a record in NsLcmOpOccModel DB
- Check if the NS instance in NS_INST DB: if there no matching ns_inst_id from the NFVO_NSINT database table, consider there is nothing to terminate, and return
- Set Job Status to Starting: set job status as "Starting terminate..."
- update the ns_inst_id row from the NFVO_NSINST database table with the status = TERMINATING
- cancel SFC list
- get sfc inst array
- for each sfc inst
- DELETE /api/nslcm/v1/ns/sfcs/{instId}
- cancel VNF list
- get vnf inst list array from NFVO_NFINST
- for each vnf inst
- delete_vnf (nf_instid)
- POST /api/nslcm/v1/ns/terminateVnf/{instId}
- cancel VL list
- get VL Inst array
- for each VL inst
- DELETE /api/nslcm/v1/ns/vls/{instId}
- cancel PNF list
- get pnf inst array
- for each pnf inst
- DELETE /api/nslcm/v1/pnfs/{instId}
- modify the ns_inst_id row state from the NFVO_NSINST database table
- modify NFVO_NSINST status = NOT_INSTANTIATED
- set job status = NS terminate ends
- Update NsLcmOpOCC to COMPLETED
- Send nsLcmOperationOccurrenceNotification
| Yes | Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | SO-2869 |
---|
|
|
|
| Delete NS | SOL005 NBI Handler invokes the Delete NS workflows which do the following: <Delete NS> Image Modified
- Initialize Parameters: get ns_inst_id
- delete ns instance in AAI
- get ns_instances from NFVO_NSINST database table
- if there are ns_instances,
- query AAI for global_customer_id, service_type, ns_inst_id
- invoke delete_ns_aai with global_customer_id, service_type, ns_inst_id, resource_version
- formulate the resource url with parameters
- call_aaI (resource, "DELETE")
- delete ns_inst_id row from the NFVO_NSINST database table
- delete ns_inst_id row from the NFVO_INPutParamMapping database table
- delete ns_inst_id row from the DefPkgMapping database table
- delete ns_inst_id row from the ServiceBaseInfo database table
- return 204 No Content
- Send NsIdentifierDeletionNotification
| Yes | Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | SO-2870 |
---|
|
|
|
| Get NS Operation Status | SOL005 NBI Handler invokes the Get NS Operation Status workflows which do the following: Image Modified
- Initialize Parameters: set lcm_op_occ_id, parameter
- if the nsLcmOpOccId pareameter is present,
- Query NSLCMOPOCCS DB for the nsLcmOpOccId
- return NsLcmOpOcc
- else
- Query NSLCMOPOCCS DB for all
- return NsLcmOpOcc[]
| Yes | Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | SO-2871 |
---|
|
|
|
| Create NS Subscription | SOL005 NBI Handler invokes the Create NS Subscription workflows which do the following: Image Modified
- Initialize Parameters: set subscription filters
- callback_uri
- authentication
- notification_types
- operation_types
- operation_states
- ns_component_types
- lcm_opname_impactin_nscomponent
- lcm_opoccstatus_impacting_nscomponent
- nsInstanceSubscriptionFilter
- Create Subscription ID: create subscription id
- Check valid auth info:
- Check Filter Type:
- check if the notification is NOTIFICATION_TYPE.NSLCM_OPERATION_OCCURRENCE_NOTIFICATION
- Check Valid:
- Check Callback_URI: check callback Uri
- check if the callbackUri exists in the NFVO_SUBSCRIPTION DB
- if no subscription, return true
- else
- check additional filter types, notificationTypes, operationTypes, operationStates
- if the filters are NOT equal, return false
- check ns instance filter, If the filter type is not equal, return false
- return true
- save subscription request to database
- return response with subscription
| Yes | Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | SO-2872 |
---|
|
|
|
| Get NS Subscription |
|
|
|
|
| Delete NS Subscription |
|
|
|
|
| Send NS Notifications |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Support for NS Resource Manager (P1 partial) |
| - Provides Resource Granting Information through OOF (Policy, MultiCloud, A&AI) (P1)
- Supports Or-Vi Interfaces that provided by VIM, Infrastructure Manager, VIM or CaaS manager (note: for Guilin, many of them would be stretch goals) (P1 Partial)
- Software Image Management (P1)
Container Image Management (stretch goal) - Virtualized Resources Information Management
Virtualized Resources Capacity Management - Virtualized Resources Management
Virtualized Resources Change Management - Virtualized Resources Reservation Management
Virtualized Resource Quota Management - Virtualized Resource Performance Management
Virtualized Resource Fault Management - Network Forwarding Path (NFP) Management
| Yes | Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | SO-2844 |
---|
|
|
|
Support for NS Catalog DB Adapter (P1) |
| - Provides access for ETSI Catalog Manager
- Get notifications from ETSI Catalog Manager
| Yes | Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | SO-2845 |
---|
|
|
|
Support for NS Inventory Adapter (P1) |
| - Provides access for AAI for NS LCM
- Refactoring of the current AAI Adapter
| Yes | Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | SO-2846 |
---|
|
|
|
Support for MultiCloud Adapter (P1) |
| - Provides MultiCloud Access
- Refactoring of the current SO MultiCloud Adapter
| Yes | Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | SO-2847 |
---|
|
|
|
Support for Configuration Mgr (P2) |
| - Provides APPC and or CDS access
- Refactoring of the current APPC and CDS connection
| Yes | Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | SO-2848 |
---|
|
|
|
Support for Policy Adapter (P2) |
| - Provides Policy access
- Refactoring of the current Policy access
| Yes | Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | SO-2849 |
---|
|
|
|
Support for OOF Adapter (P1?) |
| - Provides OOF access for homing
- Refactoring of the current OOF access
- Need to discuss further
| Yes | Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | SO-2850 |
---|
|
|
|
Supports for Notification Manager (P1) |
| - Provides notifications to SO E2E
- depends on the SOL003 notification endpoint
| ? | TBD |
|
Support for FM/PM Event Manager (P3) |
| | ? | TBD |
|
Support for K8S client (P3) |
| - Provides access to K8S
- When we support CNF, it will be done, not for Guilin
| ? | TBD |
|
Support for SOL005 Adapter to interface to/from ONAP SO NFVO (P1) |
| SOL005 Adapter supports interfaces to/from ONAP SO NFVO - SOL005 Adapter sends SOL005 requests to the ONAP SO NFVO, as one of the choices (SO NFVO, VFC, External NFVO)
- SOL005 Adapter subscribes (CREATE and DELETE) to ONAP SO NFVO for notifications
- SOL005 Adapter provides notification endpoint(s) to receive notifications (P1)
- Swagger will be provided to the SOL005 Adapter development
| Yes | Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | SO-2857 |
---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|