openstack-volume team mailing list archive

[Vladimir Popovski <vladimir@xxxxxxxxxxxxxxxxx>]

Hi Chuck,

Thanks for the response. I suppose we are very close. In my proposal I was
thinking that drivers will report whatever properties they want and on
Scheduler level we could either parse this data and try match with
volume_type extra_specs or just pass create_volume request to
sub-schedulers (schedulers for particular type of volumes). And in this
point we are very similar. Actually, I suppose your approach might be
considered as a special case of mine, where for all volume types we will
have sub-schedulers.

Anyway, how do you see this volume_type-2-scheduler mapping. As a separate
table configured through some special set of admin APIs or just
configuration flags?

Regards,
-Vladimir

-----Original Message-----
From: Chuck Thier [mailto:cthier@xxxxxxxxx]
Sent: Wednesday, October 19, 2011 7:39 AM
To: Vladimir Popovski
Cc: openstack-volume@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Openstack-volume] Basic volume-type aware scheduler

Hi Vladimir,

I agree that we need a volume-type aware scheduler, and thanks for taking
this on.  I had envisioned it a bit different though.  I was thinking that
the cluster operator would define the volume types (similar to how they
define vm flavors).  Each type would have a mapping to a driver, and the
scheduler would use this mapping to determine which driver to send the
incoming request to.

I think this makes things simpler and more flexible.  For example an
operator may not want to expose every capability of some storage system
that they have added.

--
Chuck


On Tue, Oct 18, 2011 at 2:36 PM, Vladimir Popovski
<vladimir@xxxxxxxxxxxxxxxxx> wrote:
> Hi All,
>
>
>
> I’ve registered a new blueprint for volume-type aware scheduler:
>
> https://blueprints.launchpad.net/nova/+spec/volume-type-scheduler
>
>
>
> Please take a look at specification attached to it explaining main
> principles (feel free to add/change parts of it).
>
>
>
> Regards,
>
> -Vladimir
>
>
>
>
>
> --
> Mailing list: https://launchpad.net/~openstack-volume
> Post to     : openstack-volume@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~openstack-volume
> More help   : https://help.launchpad.net/ListHelp
>
>