Feature request: set 'interval' in pipeline.yaml

Bug #1652848 reported by Xav Paice
20
This bug affects 3 people
Affects Status Importance Assigned to Milestone
OpenStack Ceilometer Agent Charm
Triaged
Wishlist
Unassigned
OpenStack Ceilometer Charm
Fix Released
Wishlist
Unassigned
ceilometer (Juju Charms Collection)
Invalid
Wishlist
Unassigned
ceilometer-agent (Juju Charms Collection)
Invalid
Wishlist
Unassigned

Bug Description

I have a customer asking for the collection interval for pollster data to be set to 30 mins rather than the default 10 mins. The charm doesn't currently expose this setting, which is located in multiple places in /etc/ceilometer/pipeline.yaml named 'interval' in each place.

Revision history for this message
Frode Nordahl (fnordahl) wrote :

1) How often/in how many use cases do you anticipate it will be necessary to adjust these values?
2) Would you require fine grained control over interval values for individual sources or would it be sufficient and useful to be able to change all of them with one parameter?

tags: added: sts
tags: added: openstack
Frode Nordahl (fnordahl)
tags: added: bootstack
James Page (james-page)
Changed in ceilometer (Juju Charms Collection):
importance: Undecided → Medium
Changed in ceilometer-agent (Juju Charms Collection):
importance: Undecided → Medium
status: New → Triaged
Changed in ceilometer (Juju Charms Collection):
status: New → Triaged
importance: Medium → Wishlist
Changed in ceilometer-agent (Juju Charms Collection):
importance: Medium → Wishlist
tags: added: canonical-bootstack
Revision history for this message
Xav Paice (xavpaice) wrote :

Hi,

Responding to Frode's query:
1) At least one customer who currently depends on Ceilometer is asking for this right now, but I can't really guess how many future customers would want this. It might be worth asking around on the ops mailing list if we're trying to work out if the effort is worth it for a one off. What I can say is that the customer asking for this doesn't have capacity for the retention they want with the default 10 min interval, and the setting is provided in Ceilometer itself so should be exposed via charm if we want to avoid hacky workarounds.

2) The request I've got from the customer was a single setting for all sources - and I would expect that to be the most logical approach when querying the resulting data sets.

Thanks for looking into this!

James Page (james-page)
Changed in charm-ceilometer:
importance: Undecided → Wishlist
status: New → Triaged
Changed in ceilometer (Juju Charms Collection):
status: Triaged → Invalid
Changed in charm-ceilometer-agent:
importance: Undecided → Wishlist
status: New → Triaged
Changed in ceilometer-agent (Juju Charms Collection):
status: Triaged → Invalid
Revision history for this message
Xav Paice (xavpaice) wrote :

Default for Queens is now 5 mins rather than 10.

See https://bugs.launchpad.net/charm-ceilometer/+bug/1785933 which likely means adding polling.yaml in any case, making this an easy one to implement.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to charm-ceilometer (stable/18.05)

Fix proposed to branch: stable/18.05
Review: https://review.openstack.org/589720

Revision history for this message
Alex Kavanagh (ajkavanagh) wrote :

This one is held up because, in order to patch the stable/18.05 charms, we need to put the feature into master and patch stable/18.11, stable/18.08 as well as stable/18.05. This is because if an operator upgrades their charms it shouldn't break the functionality; i.e. as it stands now, there would be a regression if the op upgraded from stable/18.05 to any newer charm.

Please could a separate review be raised for master with the feature, and once that has landed, it can be backported using a cherry-pick to 18.11, 18.08 and then 18.05.

Thanks.

Revision history for this message
Ryan Beisner (1chb1n) wrote :

Thank you for your work on this.

To be clear, we will not likely port this back to the 18.05 stable charms. We maintain the latest stable charm branch (18.11 currently). The changes need to be landed into the master branch first. Then, a backport to the current stable branch (18.11) can be proposed or requested.

I see recent changes proposed against master regarding this bug:

https://review.openstack.org/#/c/589697/

Awaiting a full check of the func tests.

Changed in charm-ceilometer:
milestone: none → 19.04
Changed in charm-ceilometer-agent:
milestone: none → 19.04
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on charm-ceilometer (stable/18.05)

Change abandoned by Xav Paice (<email address hidden>) on branch: stable/18.05
Review: https://review.openstack.org/589720
Reason: way outdated! Thanks

Revision history for this message
Xav Paice (xavpaice) wrote :

Thanks, I think it's better to update the charms on site to 18.11 (or later, depending on when this lands), and have abandoned the ancient change.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to charm-ceilometer (master)

Reviewed: https://review.openstack.org/589697
Committed: https://git.openstack.org/cgit/openstack/charm-ceilometer/commit/?id=2baf36f4eeca6fad7202f1e914d893619f5569a6
Submitter: Zuul
Branch: master

commit 2baf36f4eeca6fad7202f1e914d893619f5569a6
Author: Xav Paice <email address hidden>
Date: Wed Aug 8 15:25:27 2018 +1200

    Add polling.yaml to managed configs

    This change adds polling.yaml to the list of managed config files, for
    Queens and above. Two new config items are added alongside the
    template, to take into account a choice between the two polling.yaml
    files supplied with the Ceilometer source, one which has a small list of
    pollsters and the other which has all pollsters. Additionally the
    change adds the option to set the polling interval.

    Change-Id: Ifff72870cf79bea23dbd21586857dd832c9e1405
    Closes-Bug: 1785933
    Closes-Bug: 1652848

Changed in charm-ceilometer:
status: Triaged → Fix Committed
David Ames (thedac)
Changed in charm-ceilometer:
status: Fix Committed → Fix Released
David Ames (thedac)
Changed in charm-ceilometer-agent:
milestone: 19.04 → 19.07
David Ames (thedac)
Changed in charm-ceilometer-agent:
milestone: 19.07 → 19.10
David Ames (thedac)
Changed in charm-ceilometer-agent:
milestone: 19.10 → 20.01
James Page (james-page)
Changed in charm-ceilometer-agent:
milestone: 20.01 → 20.05
David Ames (thedac)
Changed in charm-ceilometer-agent:
milestone: 20.05 → 20.08
James Page (james-page)
Changed in charm-ceilometer-agent:
milestone: 20.08 → none
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.