...

• Supported at the vnf level.
• Can change only the openstack image, not vfModule assignments or structure.
• When VID sends a vnf level (macro-like) update request, SO will attempt to update EACH vfModule child for that vnf as represented in A&AI inventory (base vfModule first, then addons in any order).
• Functionally like a delete and rebuild.
• Supported at the vnf level.
• Could be done to perform a software upgrade (openstack image change) or to re-build the vnf’s vfModules using the existing image.
• When VID sends a vnf level (macro-like) replace request, SO will attempt to replace EACH vfModule child for that vnf as represented in A&AI inventory. SO will delete any addon vfModules first, then delete the base module last, however the ECOMP provided assignments will be retained and will be re-used on the subsequent “create”.  SO will then create the base vfModule first, then addons in any order.  If so desired by VID user, any associated volumeGroups for each vfModule could be re-built as well (assumed not typically desired since volumeGroups are used to store persistent data).

VNF Replace

• Functionally like a delete and rebuild.
• Supported at the vnf level.
• Could be done to perform a software upgrade (openstack image change) or to re-build the vnf’s vfModules using the existing image.
• When VID sends a vnf level (macro-like) replace request, SO will attempt to replace EACH vfModule child for that vnf as represented in A&AI inventory. SO will delete any addon vfModules first, then delete the base module last, however the ECOMP provided assignments will be retained and will be re-used on the subsequent “create”.  SO will then create the base vfModule first, then addons in any order.  If so desired by VID user, any associated volumeGroups for each vfModule could be re-built as well (assumed not typically desired since volumeGroups are used to store persistent data).

Error Handling for VNF Update and VNF Replace

If a failure is hit during the above flows, policy is consulted. If no policy is found, or if the policy states to perform manual handling, then a manual task is created in Camunda.  The VID user can search for and respond to manual tasks.  VID uses a new API exposed by the infrastructure API Handler for this).  The user can respond with directives: “skip”, “abort”, “retry”, or “rollback”.

...

The new Rainy Day Building Block flow calls Policy to determine an action for an error.  If policy is absent, or if the policy specifies manual action, the Manual Handling Building Block is invoked.  The Manual Handling Building Block suspends the flow until a VID user inputs a directive to resume the flow, one of: “skip”, “abort”, “retry”, or “rollback”.

Swagger Output

...