-
Story
-
Resolution: Done
-
Medium
-
None
-
None
SO NFVO needs to enhance the Delete NS backend operations and workflows which do the following sequence: - validate if it works with 3.3.1
- Upgrade the NS LCM and workflows for 3.3.1 and test the existing functions.
- Test the following scenarios are still working:
- Supports SOL005-compliant DeleteNS operation with nsInstanceId
- Creates BPMN workflows and business logic for the following Delete NS operations
- Supports input parameter handling
- Initialize Parameters: get ns_inst_id
- Deletes ns instance in AAI
- Gets ns_instances from NFVO_NSINST database table
- if there are ns_instances,
- Queries AAI for global_customer_id, service_type, ns_inst_id
- set resource_version from ns_info "resource-version"
- Invokes delete_ns_aai with global_customer_id, service_type, ns_inst_id, resource_version
- Formulates the resource url with parameters
- Invoke AAI Rest API: call_aaI (resource, "DELETE")
- Queries AAI for global_customer_id, service_type, ns_inst_id
- note: if there are discrepancies between VNF and NS status in AAI (e.g., VNF was not deleted yet), it is an error condition
- Deletes ns_inst_id row from the NFVO_NSINST database table
- note: if multiple records for the givin ns_inst_id are found, it is an error condition
- Deletes ns_inst_id row from the t_lcm_inputparam_mapping database table
- Deletes ns_inst_id row from the t_lcm_defPackage_mapping database table
- Deletes ns_inst_id row from the t_lcm_servicebaseinfo database table
- Returns 204 No Content
Send NsIdentifierDeletionNotificationNote: this notification will be handled by a separate notification and subscription user story.
- Supports input parameter handling
- mentioned in
-
Page Loading...