On 9/26/2018 5:30 PM, Sylvain Bauza wrote:
So, during this day, we also discussed about NUMA affinity and we said
that we could possibly use nested resource providers for NUMA cells in
Stein, but given we don't have yet a specific Placement API query, NUMA
affinity should still be using the NUMATopologyFilter.
That said, when looking about how to use this filter for vGPUs, it looks
to me that I'd need to provide a new version for the NUMACell object and
modify the virt.hardware module. Are we also accepting this (given it's
a temporary question), or should we need to wait for the Placement API
support ?
Folks, what are you thoughts ?
I'm pretty sure we've said several times already that modeling NUMA in
Placement is not something for which we're holding up the extraction.
--
Thanks,
Matt
__________________________________________________________________________
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
