Open Stack

On Jun 6, 2017, at 4:14 AM, Sylvain Bauza <sbauza at redhat.com> wrote:
> 
> The Plan A option you mention hides the complexity of the
> shared/non-shared logic but to the price that it would make scheduling
> decisions on those criteries impossible unless you put
> filtering/weighting logic into Placement, which AFAIK we strongly
> disagree with.


Not necessarily. Well, not now, for sure, but that’s why we need Traits to be integrated into Flavors as soon as possible so that we can make requests with qualitative requirements, not just quantitative. When that work is done, we can add traits to differentiate local from shared storage, just like we have traits to distinguish HDD from SSD. So if a VM with only local disk is needed, that will be in the request, and placement will never return hosts with shared storage. 

-- Ed Leafe





-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20170606/1aba3497/attachment.html>