Direct URL Metadata
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:
- 2013.2
- Started by
- John Bresnahan
- Completed by
- John Bresnahan
Related branches
Related bugs
Sprints
Whiteboard
Gerrit topic: https:/
Addressed by: https:/
Add location specific information to image locations db
Gerrit topic: https:/
Addressed by: https:/
Allow storage drivers to add metadata to locations
Addressed by: https:/
File system store can send metadata back with the location.