Direct URL Metadata

Registered by John Bresnahan on 2013-01-29

When a direct URL is returned to a client it will be helpful to the client to have additional information about that URL. For example, with a file:// URL the client may need to know the NFS host that is exporting it, the mount point, and FS type used. This could be directly spelled out or determined by way of some cryptic token. Such information is hard/awkward/kludgy to encapsulate in a URL.

This blueprint requests that each storage system have a means to return direct URL specific meta-data to the client when direct_url is enabled.

Blueprint information

Status:
Complete
Approver:
John Bresnahan
Priority:
Medium
Drafter:
None
Direction:
Needs approval
Assignee:
John Bresnahan
Definition:
Approved
Series goal:
Accepted for havana
Implementation:
Implemented
Milestone target:
milestone icon 2013.2
Started by
John Bresnahan on 2013-07-08
Completed by
John Bresnahan on 2013-08-01

Related branches

Sprints

Whiteboard

Gerrit topic: https://review.openstack.org/#q,topic:bp/direct-url-meta-data,n,z

Addressed by: https://review.openstack.org/31306
    Add location specific information to image locations db

Gerrit topic: https://review.openstack.org/#q,topic:bp/multiple-image-locations,n,z

Addressed by: https://review.openstack.org/34492
    Allow storage drivers to add metadata to locations

Addressed by: https://review.openstack.org/36884
    File system store can send metadata back with the location.

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.