Hi I'm still working on the blueprint for affinity, but an optional free-text field that gets passed through to the scheduler and driver should be fine from a user api point-of-view.
Regards -- Duncan Thomas HP Cloud Services, Galway From: openstack-volume-bounces+duncan.thomas=hp....@lists.launchpad.net [mailto:openstack-volume-bounces+duncan.thomas=hp....@lists.launchpad.net] On Behalf Of Vladimir Popovski Sent: 24 October 2011 20:02 To: openstack-volume@lists.launchpad.net Subject: [Openstack-volume] adding auxiliary specs to volume create Team, I would like to propose a change to volume-type aware scheduler we are developing. After last meeting it was unclear how we will treat volume affinity or other types of per-volume specifications. What I think we could do is to add an additional parameter (optional) to create volume API that will hold auxiliary specs for the volume. This parameter will be forwarded to scheduler as one of arguments. The generic scheduler will combine key/value pairs from extra specs together with these auxiliary specs and will perform a search based on combined list. Pls let me know what do you think about it? I've already update a BP spec with this proposal. Regards, -Vladimir
-- Mailing list: https://launchpad.net/~openstack-volume Post to : openstack-volume@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack-volume More help : https://help.launchpad.net/ListHelp
