Ankit Agrawal b560b1777c Add request_ids attribute to resource objects ...

Added request_ids attribute to resource object for all the volume,
volume_types, volume_type_access and volume_snapshots APIs by
updating following APIs:

volumes: delete, update, force_delete, reset_state, extend,
migrate_volume, retype, update_readonly_flag, manage, unmanage,
promote, reenable, get_pools, initialize_connection,
terminate_connection, get_encryption_metadata

volume_types: delete
volume_type_access: add_project_access remove_project_access
volume_snapshots: delete and update

Returning list with request_ids as attribute in case of
'delete_metadata' and 'delete_image_metadata' APIs.

These changes are required to return 'request_id' from client to
log request_id mappings of cross projects.

For more details on how request_id will be returned to the caller,
please refer to the approved blueprint [1] discussed with the
cross-project team.
[1] http://specs.openstack.org/openstack/openstack-specs/specs/return-request-id.html

DocImpact
'request-ids' will be returned as an attribute with response object.
User can access it using 'res.request_ids' where 'res' is a
response object.

Change-Id: Icc4565291220278a65e6910a840fba623b750cc4
Partial-Implements: blueprint return-request-id-to-caller

2016-02-17 13:38:13 +00:00

2.3 KiB

Raw Blame History

View Raw