'Deleted VNF' message on cli is incorrect for the new Delete VNF behavior

[Sripriya]

With the new behavior https://review.openstack.org/#/c/291032/ coming in for VNF delete, what it implies is: VNF will be in PENDING_DELETE until all background resources are completely deleted before finally removing the db entry for VNF in tacker server.

On the cli, this means: when the user issues a delete command via:
tacker vnf-delete f4450125-d8cc-46eb-b77c-267eceac5173
Deleted vnf: f4450125-d8cc-46eb-b77c-267eceac5173

The 'Deleted vnf' string gives a wrong message to the user that VNF is deleted when in actuality it is still being deleted (PENDING_DELETE) on server

Expected behavior:

The message needs to be modified to something like: (similar to nova)
Request to delete VNF ea406dba-88ac-44fd-8205-86c4fe64cc67 has been accepted.

This will help user understand that VNF is still in PENDING_DELETE before finally getting deleted.

[Sridhar Ramaswamy (srics-r)]

Good observation. Let's see how nova and heat handle this and try be consistent across openstack project.

[dharmendra (dharmendra-kushwaha)]

https://review.openstack.org/#/c/314716/

[Kanagaraj Manickam (kanagaraj-manickam)]

I believe that its better to update , HTTP status code 202 to return, when DELETE action does accept the request but not completed before return the response.

[dharmendra (dharmendra-kushwaha)]

This issue fixed in https://review.openstack.org/#/c/349806/