For visibility, I will be doing something similar in watcher. We deprecated the Monasca support in watcher this cycle because there is no tempest testing or documentation to speak of for how to use watcher with the Monasca datasource. I will be working on making Monasca an optional dependency for watcher next week by moving the python-monascaclient requirement to extras and making all imports of monascaclient optional. Next cycle, we will likely accelerate the removal of the datasource entirely in 2026.1 instead of waiting for 2026.2 as a result of the retirement. I'll add this as a PTG topic and send a mailing list post before the removal patches are merged as a final warning, but if anyone has watcher deployed and uses Monasca, please be aware that this has effectively been unmaintained on the watcher side for several years now and has a very limited runway of availability. This is one of the few places in watcher that could be a stevedore plugin but currently isn't, so unlike Heat, it won't be possible to re-add it as an external plugin, at least not in a supported way. regards sean On 06/08/2025 14:12, Takashi Kajinami wrote:

I have no objection, but I'd like to re-mention my intention to remove monasca integration from heat upon the retirement.

In case that integration part is required then it can be maintained as an external plugin (which overrides the in-tree resources, which will be replaced by hidden noop resources).

On 7/31/25 4:01 AM, Goutham Pacha Ravi wrote:

...

Hello Stackers,

We intend to retire the Monasca project [1] and all associated repositories [2].

The retirement is being proposed with the support and consent of the current core team members and the Project Team Lead (PTL) [3]. For context, the Monasca project team was marked as being inactive during the 2024.1 (Caracal) release cycle [4]. Since then, no sustained development activity has occurred. There have been no releases tagged for any of the deliverables owned by the team either, and there are no actively maintained stable branches.

So, in accordance with the procedures in the OpenStack governance documentation [5], and based on the current state of the project, we propose the following repositories ahead of the 2025.2 ("Flamingo") coordinated release:

- openstack/monasca-agent - openstack/monasca-api - openstack/monasca-common - openstack/monasca-events-api - openstack/monasca-log-api - openstack/monasca-notification - openstack/monasca-persister - openstack/monasca-specs - openstack/monasca-tempest-plugin - openstack/monasca-thresh - openstack/python-monascaclient - openstack/monasca-ui - openstack/monasca-transform - openstack/monasca-ceilometer - openstack/monasca-grafana-datasource - openstack/monasca-kibana-plugin - openstack/monasca-statsd

Some of the current maintainers intend to fork the project and continue development independently for their purposes. This retirement does not preclude such efforts; nor does it prevent reviving the project after the retirement.

If there are any objections to retiring the project, please respond to this thread. In the event there is interest in continuing Monasca within OpenStack, we would expect the project team to meet the requirements for active status [6] — including identifying a new PTL for the upcoming release cycle and demonstrating plans for sustained maintenance.

Thank you to everyone who has contributed to Monasca over the years.

Thanks, On behalf of the OpenStack TC, Goutham Pacha Ravi (gouthamr) OpenStack TC Chair

[1] https://docs.openstack.org/monasca-api/latest/ [2] https://github.com/openstack/governance/blob/624bb5bf124452eed475c9b6e621444... [3] https://review.opendev.org/c/openstack/governance/+/953671 [4] https://governance.openstack.org/tc/reference/emerging-technology-and-inacti... [5] https://docs.openstack.org/project-team-guide/repository.html#retiring-a-rep... [6] https://governance.openstack.org/tc/reference/new-projects-requirements.html