Open Stack

Eventually I don't fully understand reasons behind need of such service.

As fighting with high load by migrating instances between computes is
fighting with consequences rather then with root cause, not saying that it
brings more negative effects then positive for experience of the end-users,
as you're just moving problem to another place affecting more workloads
with degraded performance.

If you struggling from high load on a daily basis - then you have too high
cpu_allocation_ratio set for computes. As high load issues always come from
attempts to oversell too agressively.

If you have workloads in the cloud that always utilize all CPUs available -
then you should consider having flavors and aggregates with cpu-pinning,
meaning providing physical CPUs for such workloads.

Also don't forget, that it's worth setting more realistic numbers for
reserved resources on computes, because default 2gb of RAM is usually too
small.



ср, 15 мар. 2023 г., 13:11 Nguyễn Hữu Khôi <nguyenhuukhoinw at gmail.com>:

> Hello.
> I cannot use because missing cpu_util metric. I try to match it work but
> not yet. It need some code to make it work. It seem none care about balance
> reources on cloud.
>
> On Wed, Mar 15, 2023, 6:26 PM Thomas Goirand <zigo at debian.org> wrote:
>
>> On 12/11/22 01:59, Nguyễn Hữu Khôi wrote:
>> > Watcher is not good because It need cpu metric
>> > such as cpu load in Ceilometer which is removed so we cannot use it.
>>
>> Hi!
>>
>> What do you mean by "Ceilometer [is] removed"? It certainly isn't dead,
>> and it works well... If by that, you mean "ceilometer-api" is removed,
>> then yes, but then you can use gnocchi.
>>
>> Cheers,
>>
>> Thomas Goirand (zigo)
>>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.openstack.org/pipermail/openstack-discuss/attachments/20230316/13634ddc/attachment.htm>