Re: [openstack-dev] [glance] allow a ranking mechanism for glance-api to order image locations

2016-01-18 Thread Jake Yip
Thanks all for the interest. I have submitted a change at https://review.openstack.org/#/c/268865/. Please take a look and give your comments! (There are a few PEP errors that I'll be correcting...) Regards, Jake On Tue, Jan 19, 2016 at 4:41 AM, Steve Lewis wrote: > > > On Wed, Jan 13, 2016 at

Re: [openstack-dev] [glance] allow a ranking mechanism for glance-api to order image locations

2016-01-18 Thread Steve Lewis
On Wed, Jan 13, 2016 at 4:07 PM, Jake Yip wrote: > > 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. > I spoke with an operator in Vancouver (Spring 2015 Summit) who wanted

Re: [openstack-dev] [glance] allow a ranking mechanism for glance-api to order image locations

2016-01-14 Thread Flavio Percoco
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 s

Re: [openstack-dev] [glance] allow a ranking mechanism for glance-api to order image locations

2016-01-13 Thread Fei Long Wang
Hi Jake, Thanks for raising this topic. I'm really interested in it. I reviewed most of the locations patches of Glance, so drop my 2 cents about this. So firstly, I think it's a valid user case. As for the implementation, I think a spec-lite is enough, given it's just a driver for current lo

[openstack-dev] [glance] allow a ranking mechanism for glance-api to order image locations

2016-01-13 Thread Jake Yip
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