Open Stack

On 14/01/16 11:07 +1100, Jake Yip wrote:
>Hi all,
>
>I've recently ran across a constraint in glance-api while working with image
>locations. In essence, there is no way to customize ordering of image-locations
>other than the default location strategies, namely location_order and
>store_type [0]. It seems like a more generic method of ordering image locations
>is needed, IMHO.
>
>Some background - We are in a multi-cell environment and each cell has it's own
>glance-api server. All images are stored in a global swift cluster. We would
>like glance to be able to fetch images from a local store, so that we can do
>COW for backends like RBD.
>
>Unfortunately, none of the current location strategies works for us, as we
>might have multiple cells sharing the same backend. I've opened a bug /
>wishlist describing this issue [1]. I have also implemented code that allows us
>to achieve that based on image location metadata.
>
>I am wondering anyone else have solved this before? I would like to hear your
>opinions on how we can achieve this, and whether ranking it by metadata is the
>way to go.
>
>The current wishlist is now tracked as a spec-lite. Is this ok?

Yes, this sounds like a good example of a spec lite. We'll now proceed to review
it, triage it and give a go if everything looks fine.

As far as the feature goes, I think it is fine to add other location strategies.
I'll follow-up on the bug.

Flavio

-- 
@flaper87
Flavio Percoco
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20160114/02fad5be/attachment.pgp>