[openstack-dev] [nova][cinder] Schedule Instances according to Local disk based Volume?

Jay S. Bryant jsbryant at electronicjungle.net
Sat Sep 24 15:39:39 UTC 2016


Erlon,

Thanks for pointing this out.  I didn't know we had this filter!

Jay


On 09/23/2016 01:05 PM, Erlon Cruz wrote:
> Not sure exactly what you mean, but in Cinder using the 
> InstanceLocalityFilter[1], you can  schedule a volume to the same 
> compute node the instance is located. Is this what you need?
>
> [1] 
> http://docs.openstack.org/developer/cinder/scheduler-filters.html#instancelocalityfilter
>
> On Fri, Sep 23, 2016 at 12:19 PM, Jay S. Bryant 
> <jsbryant at electronicjungle.net <mailto:jsbryant at electronicjungle.net>> 
> wrote:
>
>     Kevin,
>
>     This is functionality that has been requested in the past but has
>     never been implemented.
>
>     The best way to proceed would likely be to propose a
>     blueprint/spec for this and start working this through that.
>
>     -Jay
>
>
>     On 09/23/2016 02:51 AM, Zhenyu Zheng wrote:
>>     Hi Novaers and Cinders:
>>
>>     Quite often application requirements would demand using locally
>>     attached disks (or direct attached disks) for OpenStack compute
>>     instances. One such example is running virtual hadoop clusters
>>     via OpenStack.
>>
>>     We can now achieve this by using BlockDeviceDriver as Cinder
>>     driver and using AZ in Nova and Cinder, illustrated in[1], which
>>     is not very feasible in large scale production deployment.
>>
>>     Now that Nova is working on resource provider trying to build an
>>     generic-resource-pool, is it possible to perform
>>     "volume-based-scheduling" to build instances according to volume?
>>     As this could be much easier to build instances like mentioned above.
>>
>>     Or do we have any other ways of doing this?
>>
>>     References:
>>     [1]
>>     http://cloudgeekz.com/71/how-to-setup-openstack-to-use-local-disks-for-instances.html
>>     <http://cloudgeekz.com/71/how-to-setup-openstack-to-use-local-disks-for-instances.html>
>>
>>     Thanks,
>>
>>     Kevin Zheng
>>
>>
>>     __________________________________________________________________________
>>     OpenStack Development Mailing List (not for usage questions)
>>     Unsubscribe:OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
>>     <mailto:OpenStack-dev-request at lists.openstack.org?subject:unsubscribe>
>>     http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>     <http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev>
>     __________________________________________________________________________
>     OpenStack Development Mailing List (not for usage questions)
>     Unsubscribe:
>     OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
>     <http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe>
>     http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>     <http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev> 
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20160924/5bc21ed7/attachment.html>


More information about the OpenStack-dev mailing list