Open Stack

Hi Gauri,

Please have a try with this link[0], Our production haven't use the latest
release and haven't use gnoochi, So sorry for can not provider more advice
about this.

[0]
https://stackoverflow.com/questions/56216683/openstack-get-vm-cpu-util-with-stein-version


Gauri Sindhu <sindhugauri1 at gmail.com>于2019年10月17日 周四16:34写道：

> Hi Rong,
>
> Is there any workaround for this at the moment? Is there any other
> replacement for the cpu_util metric so that we can transfer the metric or
> data to the alarm?
>
> Regards,
> Gauri Sindhu
>
>
> On Thu, Oct 17, 2019 at 12:02 PM Rong Zhu <aaronzhu1121 at gmail.com> wrote:
>
>> Hi Gauri,
>>
>> We received a lot of feedback about cpu_utils, And we had plan to add
>> cpu_utils back in U release.
>>
>>
>> Gauri Sindhu <sindhugauri1 at gmail.com>于2019年10月17日 周四14:20写道：
>>
>>> Hi all,
>>>
>>> As per the Rocky release notes
>>> <https://docs.openstack.org/releasenotes/ceilometer/rocky.html>, *cpu_util
>>> and *.rate meters are deprecated and will be removed in future release in
>>> favor of the Gnocchi rate calculation equivalent.*
>>>
>>> I have two doubts regarding this.
>>>
>>> Firstly, if the 'cpu_util' metric has been deprecated then why has it
>>> been used as an example in the documentation
>>> <https://docs.openstack.org/aodh/stein/admin/telemetry-alarms.html> in
>>> the 'Using Alarms' section? I've attached an image of the same.
>>>
>>> Secondly, I'm using OpenStack Stein and want to use the cpu_util or its
>>> equivalent to create an alarm. If this metric is no longer available then
>>> what do I pass onto Aodh to create the alarm? There seems to be no
>>> documentation that to help me out with this. Additionally, even if Gnocchi
>>> rate calculation is to be used, how am I supposed to transfer the result to
>>> Aodh? I also cannot seem to find the Gnocchi documentation.
>>>
>>> Regards,
>>> Gauri Sindhu
>>>
>> --
>> Thanks,
>> Rong Zhu
>>
> --
Thanks,
Rong Zhu
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-discuss/attachments/20191018/856b6a51/attachment-0001.html>