Modify the create workflow for vnf create with configuration management

Bug #1600412 reported by Sripriya
This bug affects 1 person
Affects Status Importance Assigned to Milestone
In Progress

Bug Description

Curren workflow for VNF create with configuration is:


This workflow appears to update the device after the device is ACTIVE (created) which trips the user to think the device is getting updated again.

Modify the workflow as:

PENDING_CREATE->CONFIGURATION_UPDATE->ACTIVE for vnf create with configuration.

1. Remove the duplicate mgmt_call in plugin file which invokes the mgmt driver twice to update the configuration.

2. Also refactor the plugin file to remove the update_device call from create_device which duplicates all previous operations.

Changed in tacker:
importance: Undecided → Medium
Changed in tacker:
assignee: Sripriya (sseetha) → dharmendra (dharmendra-kushwaha)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to tacker (master)

Fix proposed to branch: master

Changed in tacker:
status: New → In Progress
Changed in tacker:
milestone: none → pike-3
Changed in tacker:
milestone: pike-3 → none
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.