[openstack-dev] [goals][upgrade-checkers] [telemetry] Upgrade checks for telemetry services
akhil.jain at india.nec.com
Tue Oct 30 13:30:32 UTC 2018
Thanks Doug for quick response. I will start working accordingly.
From: Doug Hellmann <doug at doughellmann.com>
Sent: Tuesday, October 30, 2018 6:03:24 PM
To: AKHIL Jain; openstack-dev at lists.openstack.org
Subject: Re: [openstack-dev] [goals][upgrade-checkers] [telemetry] Upgrade checks for telemetry services
AKHIL Jain <akhil.jain at india.nec.com> writes:
> Hi Matt and Telemetry Team,
> I was going through the remaining project to be implemented with upgrade-checkers placeholder framework. I would like to know about the projects to implement the same under telemetry tab.
> According to my understanding from below link, multiple projects come under telemetry:
> Aodh being alarming service triggers alarm when collected data breaks over set rules. Also, Aodh work as a standalone project using any backend(ceilometer, gnocchi. etc.):
> So there are expected changes b/w releases.
> Ceilometer being data collection service(that helps in customer billing, resource tracking, and alarming): As this service is involved in data pooling from other projects. So there can be chances to perform upgrade checks.
> Panko being indexing service, that provides the ability to store and query event data. Related changes to indexing objects can be checked while upgrading
> So, should we add upgrade-check command in each project or single command upgrade-checks should be there to tell each service upgrade status?
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
Each of those services has its own configuration file and database, and
the code is in separate repositories, so it seems like we would want a
separate upgrade check command for each one.
More information about the OpenStack-dev