misleading documentation of filesystem_store_metadata_file config opt

Bug #1775736 reported by Brian Rosmaita on 2018-06-08
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Glance
Low
Unassigned
glance_store
Low
Unassigned

Bug Description

In glance:

The short discussion of the filesystem_store_metadata_file option in doc/source/admin/manage-images.rst is misleading on two counts:

(1) It makes it sound like the location metadata is dynamically pulled from the file and returned in the image-show response for any image. In fact, the way this works is that glance will use the info in the file when it writes the image location--so you will only see this metadata for images created *after* the option has been set.

(2) The example is misleading in that it uses the same UUID for the mountpoint and for the image_id, which I suppose would work, but it makes it look like the two fields are related.

See discussion about this in the glance channel log: http://eavesdrop.openstack.org/irclogs/%23openstack-glance/%23openstack-glance.2018-06-01.log.html#t2018-06-01T20:26:28 to about 21:05

In glance_store:

The help text for this option is a bit vague; could stand a rewrite based on the improvements made in the glance docs.

See https://github.com/openstack/glance_store/blob/cc97b949033f892d6675692cbc8a24df3ce0e15e/glance_store/_drivers/filesystem.py#L109-L125

Changed in glance-store:
status: New → Triaged
importance: Undecided → Low
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers