OSDir


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Openstack] NUMA some of the time?


Greetings Toni,
Not sure I'm answering, but just as a quick note you can prioritize NUMA
and CPU-pinning by creating dedicated flavors [1] with something like:

openstack flavor set m1.largenuma --property hw:numa_cpus.0=0,1 --property
hw:numa_mem.0=2048

Usually NUMA cores are reserved or shared only for specific fixed ops, and
I'm not sure what you mean by "throwing off more cores" in case of need,
probably you need to look into something like Heat autoscale?

Cheers,
Fabrizio

[1] https://docs.openstack.org/nova/pike/admin/cpu-topologies.html

On Wed, Jul 4, 2018 at 5:19 PM Toni Mueller <toni.mueller at oeko.net> wrote:

>
> Hi,
>
> I am still trying to figure how to best utilise the small set of
> hardware, and discovered the NUMA configuration mechanism. It allows me
> to configure reserved cores for certain VMs, but it does not seem to
> allow me to say "you can share these cores, but VMs of, say, appropriate
> flavour take precedence and will throw you off these cores in case they
> need more power".
>
> How can I achieve that, dynamically?
>
> TIA!
>
>
> Thanks,
> Toni
>
>
> _______________________________________________
> Mailing list:
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
> Post to     : openstack at lists.openstack.org
> Unsubscribe :
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack/attachments/20180705/40c19db3/attachment.html>