On Thu, Apr 19, 2018 at 12:45 AM, Eric Fried <[email protected]> wrote:
I have a feeling we're just going to go back and forth on this, as we have for weeks now, and not reach any conclusion that is satisfactory to everyone. And we'll delay, yet again, getting functionality into this release that serves 90% of use cases because we are obsessing over the0.01% of use cases that may pop up later.So I vote that, for the Rocky iteration of the granular spec, we add a single `proximity={isolate|any}` qparam, required when any numbered request groups are specified. I believe this allows us to satisfy thetwo NUMA use cases we care most about: "forced sharding" and "any fit".And as you demonstrated, it leaves the way open for finer-grained and more powerful semantics to be added in the future.
Can the proximity param specify relationship between the un-numbered and the numbered groups as well or only between numbered groups?
Besides that I'm +1 about proxyimity={isolate|any}
Cheers,
gibi
-efried __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions)Unsubscribe: [email protected]?subject:unsubscribehttp://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
