Hi Chris, On Fri, Jan 19, 2018 at 10:21 AM, Chris Friesen <chris.frie...@windriver.com> wrote: > > The existing mechanisms to control aggregate membership will still work, so > the remaining issue is how to control the allocation ratios. > > What about implementing a new HTTP API call (as a local private patch) to > set the allocation ratios for a given host? This would only be valid for > your scenario where a given host is only present in a single aggregate, but > it would allow your techs to modify the ratios.
While I agree that we can implement something in a private patch, this is something we are trying very hard to much away from. If Nova proposes using the placement API for such use cases, I think it should also provides the same features as the replaced solutions because people could have relied on those. And suggesting a configuration management system is enough was unfortunately a false assumption. I still have to figure out how a workflow based on placement will be feasible for us. But as I said, the lack of granular ACLs is a huge concern for us and I don't know how it can be addressed in the near future. -- Mathieu __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
