openstack-volume team mailing list archive

[Chuck Thier <cthier@xxxxxxxxx>]

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
>
>