Add support for enabling and configuration of ceph telemetry module

[frittentheke]

Is your feature request related to a problem? Please describe.
Currently ceph-ansible seems unable to enable or even configure the options of the Telemetry module (https://docs.ceph.com/en/latest/mgr/telemetry/).

The easier this module can be enabled and set up, the more telemetry is likely submitted by clusters set up and operated via ceph-ansible.

Describe the solution you'd like
I'd like an easy config switch to first enable telemetry (including accepting the license) - https://docs.ceph.com/en/latest/mgr/telemetry/#enabling-telemetry. Additionally setting the enabled channels (https://docs.ceph.com/en/latest/mgr/telemetry/#channels) and collections (https://docs.ceph.com/en/latest/mgr/telemetry/#collections) would be nice.
Last but not least allowing to define ident info (https://docs.ceph.com/en/latest/mgr/telemetry/#contact-and-description) should be possible.

Describe alternatives you've considered
Alternatively those settings have to come either by manual commands after a cluster has been created or by added Ansible tasks.
Both seems not really a clean solution with ceph-ansible managing all other things Ceph out of the box.

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in a week if no further activity occurs. Thank you for your contributions.

[frittentheke]

Is this really stale already?

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in a week if no further activity occurs. Thank you for your contributions.

[frittentheke]

I'd still love to see this feature

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in a week if no further activity occurs. Thank you for your contributions.

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in a week if no further activity occurs. Thank you for your contributions.

[frittentheke]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in a week if no further activity occurs. Thank you for your contributions.

please kindly reconsider

[guits]

I'm not against that, we just don't have the bandwidth at the moment for this.

Contributions are welcome .. 😁

[guits]

@frittentheke,

@asm0deuz is taking a look at this one

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in a week if no further activity occurs. Thank you for your contributions.

[github-actions]

This issue has been automatically closed due to inactivity. Please re-open if this still requires investigation.

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in a week if no further activity occurs. Thank you for your contributions.

[frittentheke]

@guits any way to keep this issue alive?

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in a week if no further activity occurs. Thank you for your contributions.