Bug 979138
| Summary: | [RFE] Specify driver specific metadata with a location | ||
|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | John Bresnahan <jbresnah> |
| Component: | openstack-glance | Assignee: | Flavio Percoco <fpercoco> |
| Status: | CLOSED ERRATA | QA Contact: | Yogev Rabl <yrabl> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | high | ||
| Version: | 4.0 | CC: | abaron, breeler, dron, eglynn, fpercoco, gfidente, hateya, jbresnah, mlopes, sgordon |
| Target Milestone: | Upstream M3 | Keywords: | FutureFeature, TestOnly |
| Target Release: | 4.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| URL: | https://blueprints.launchpad.net/glance/+spec/direct-url-meta-data | ||
| Whiteboard: | |||
| Fixed In Version: | openstack-glance-2013.2-3.el6ost | Doc Type: | Enhancement |
| Doc Text: |
In the OpenStack Image service, when a direct URL is returned to a client it is 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 feature requests that each storage system has a means to return direct URL specific meta-data to the client when direct_url is enabled. Although all stores could support this feature already, only the filesystem one does.
It does that by reading the metadata information from an external path, configurable through a configuration parameter `filesystem_store_metadata_file` in glance-api.conf
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2013-12-20 00:12:23 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 988927, 988928, 1037283 | ||
| Bug Blocks: | 975499 | ||
|
Description
John Bresnahan
2013-06-27 18:08:41 UTC
an upstream patch has been submitted for review: https://review.openstack.org/#/c/34492/ The final patch has been accepted upstream: https://review.openstack.org/#/c/36884/. In order to test please do the following: 1) Install Glance and glance client. 2) create a file with valid JSON data such that it contains only unicode, lists, and dictionaries. 3) In glance-api.conf set: show_multiple_locations = True filesystem_store_metadata_file = <path to the file created in step #2> 4) Add an image to glance with glance client 5) Show the information about the image with glance client and api version 2: glance --os-image-api-version 2 image-show <image id> 6) verify that the metadata is under the locations value in the output. Hi John, How do we expect this to be handled from a packaging perspective and where is that tracked? By that I mean will the initial file be created by the package install and be set up in the filesystem_store_metadata_file configuration key? If this is required for a good gluster experience then we should make sure it works OOTB. Thanks, Steve (In reply to Stephen Gordon from comment #4) > Hi John, > > How do we expect this to be handled from a packaging perspective and where > is that tracked? By that I mean will the initial file be created by the > package install and be set up in the filesystem_store_metadata_file > configuration key? > > If this is required for a good gluster experience then we should make sure > it works OOTB. > > Thanks, > > Steve Steve, Good questions. This feature will be off by default. Creating that file takes coordination with Nova (and further it requires a corresponding patch in nova that has not yet been accepted). This is something that should be explicitly enabled by operators so by default no file is needed. Thus this should not be an issue for packaging. John Resetting needinfo for jbresnah because fpercoco supplied doc text. verified on: python-glance-2013.2-5.el6ost.noarch python-glanceclient-0.12.0-1.el6ost.noarch openstack-glance-2013.2-5.el6ost.noarch Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHEA-2013-1859.html |