Red Hat Bugzilla – Bug 979138
[RFE] Specify driver specific metadata with a location
Last modified: 2016-04-26 15:57:44 EDT
Allow for driver specific metadata to be associated with an image location. This will allow nova compute to make better decisions when trying to interact with gluster.
an upstream patch has been submitted for review:
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.
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.
(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.
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.
Resetting needinfo for jbresnah because fpercoco supplied doc text.
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.