[ceilometer][octavia] polling meters

Rafael Weingärtner rafaelweingartner at gmail.com
Thu Jul 2 14:49:52 UTC 2020


> Since the merging window for ussuri was long passed for those commits, is
> it safe to assume that it will not land in stable/ussuri at all and those
> will be available for victoria?
>

I would say so. We are lacking people to review and then merge it.

How safe is to cherry pick those commits and use them in production?
>
As long as the person executing the cherry-picks, and maintaining the code
knows what she/he is doing, you should be safe. The guys that are using
this implementation (and others that I and my colleagues proposed), have a
few openstack components that are customized with the
patches/enhancements/extensions we developed so far; this means, they are
not using the community version, but something in-between (the community
releases + the patches we did). Of course, it is only possible, because we
are the ones creating and maintaining these codes; therefore, we can assure
quality for production.




On Thu, Jul 2, 2020 at 9:43 AM Ionut Biru <ionut at fleio.com> wrote:

> Hello Rafael,
>
> Since the merging window for ussuri was long passed for those commits, is
> it safe to assume that it will not land in stable/ussuri at all and those
> will be available for victoria?
>
> How safe is to cherry pick those commits and use them in production?
>
>
>
> On Fri, Apr 24, 2020 at 3:06 PM Rafael Weingärtner <
> rafaelweingartner at gmail.com> wrote:
>
>> The dynamic pollster in Ceilometer will be first released in Ussuri.
>> However, there are some important PRs still waiting for a merge, that might
>> be important for your use case:
>> * https://review.opendev.org/#/c/722092/
>> * https://review.opendev.org/#/c/715180/
>> * https://review.opendev.org/#/c/715289/
>> * https://review.opendev.org/#/c/679999/
>> * https://review.opendev.org/#/c/709807/
>>
>>
>> On Fri, Apr 24, 2020 at 8:18 AM Carlos Goncalves <cgoncalves at redhat.com>
>> wrote:
>>
>>>
>>>
>>> On Fri, Apr 24, 2020 at 12:20 PM Ionut Biru <ionut at fleio.com> wrote:
>>>
>>>> Hello,
>>>>
>>>> I want to meter the loadbalancer into gnocchi for billing purposes in
>>>> stein/train and ceilometer doesn't support dynamic pollsters.
>>>>
>>>
>>> I think I misunderstood your use case, sorry. I read it as if you wanted
>>> to know "if a loadbalancer was deployed and has status active".
>>>
>>>
>>>> Until I upgrade to Ussuri, is there a way to accomplish this?
>>>>
>>>
>>> I'm not sure Ceilometer supports it even in Ussuri. I'll defer to the
>>> Ceilometer project.
>>>
>>>
>>>>
>>>> On Fri, Apr 24, 2020 at 12:45 PM Carlos Goncalves <
>>>> cgoncalves at redhat.com> wrote:
>>>>
>>>>> Hi Ionut,
>>>>>
>>>>> On Fri, Apr 24, 2020 at 11:27 AM Ionut Biru <ionut at fleio.com> wrote:
>>>>>
>>>>>> Hello guys,
>>>>>> I was trying to add in polling.yaml and pipeline from ceilometer the
>>>>>> following:
>>>>>>    - network.services.lb.active.connections
>>>>>>       - network.services.lb.health_monitor
>>>>>>       - network.services.lb.incoming.bytes
>>>>>>       - network.services.lb.listener
>>>>>>       - network.services.lb.loadbalancer
>>>>>>       - network.services.lb.member
>>>>>>       - network.services.lb.outgoing.bytes
>>>>>>       - network.services.lb.pool
>>>>>>       - network.services.lb.total.connections
>>>>>>
>>>>>> But it doesn't work, I think they are for the old lbs that were
>>>>>> supported in neutron.
>>>>>>
>>>>>> I found
>>>>>> https://docs.openstack.org/ceilometer/latest/admin/telemetry-dynamic-pollster.html
>>>>>> but this is not available in stein or train.
>>>>>>
>>>>>> I was wondering if there is a way to meter loadbalancers from
>>>>>> octavia.
>>>>>> I mostly want for start to just meter if a loadbalancer was deployed
>>>>>> and has status active.
>>>>>>
>>>>>
>>>>> You can get the provisioning and operating status of Octavia load
>>>>> balancers via the Octavia API. There is also an API endpoint that returns
>>>>> the full load balancer status tree [1]. Additionally, Octavia has
>>>>> three API endpoints for statistics [2][3][4].
>>>>>
>>>>> I hope this helps with your use case.
>>>>>
>>>>> Cheers,
>>>>> Carlos
>>>>>
>>>>> [1]
>>>>> https://docs.openstack.org/api-ref/load-balancer/v2/?expanded=get-the-load-balancer-status-tree-detail#get-the-load-balancer-status-tree
>>>>> [2]
>>>>> https://docs.openstack.org/api-ref/load-balancer/v2/?expanded=get-load-balancer-statistics-detail#get-load-balancer-statistics
>>>>> [3]
>>>>> https://docs.openstack.org/api-ref/load-balancer/v2/?expanded=get-listener-statistics-detail#get-listener-statistics
>>>>> [4]
>>>>> https://docs.openstack.org/api-ref/load-balancer/v2/?expanded=show-amphora-statistics-detail#show-amphora-statistics
>>>>>
>>>>>
>>>>>
>>>>>>
>>>>>> --
>>>>>> Ionut Biru - https://fleio.com
>>>>>>
>>>>>
>>>>
>>>> --
>>>> Ionut Biru - https://fleio.com
>>>>
>>>
>>
>> --
>> Rafael Weingärtner
>>
>
>
> --
> Ionut Biru - https://fleio.com
>


-- 
Rafael Weingärtner
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-discuss/attachments/20200702/dd10ad70/attachment.html>


More information about the openstack-discuss mailing list