The OpenStack Placement team is looking for some input on the sort of NUMA topology that they should employ in the Placement tests. See [0], the second paragraph under "## Cleanup", reproduced below. In short, they are looking for input as to the NUMA topology that the test suite should create to run queries against. Any thoughts that we (StarlingX community) can offer would be helpful. I am thinking that at a minimum we have some topologies used in our test suites that we could share, things like the number of cores/sockets/devices and the affinities that go with them? Replies here will be forwarded to the right places or reply directly to cdent's email [0] on openstack-discuss from last week. Thanks dt [0] http://lists.openstack.org/pipermail/openstack-discuss/2019-July/007716.html

As mentioned last week, one of the important cleanup tasks that is not yet in progress is updating the [gabbit](https://opendev.org/openstack/placement/src/branch/master/gate/gabbits/neste...)

that creates the nested topology that's used in nested performance testing. The topology there is simple, unrealistic, and doesn't sufficiently exercise the several features that may be used during a query that desires a nested response. This needs to be someone who is more closely related to real world use of nested than me. efried? gibi?

-- Dean Troyer dtroyer@gmail.com