Integrated projects are required to participate in the grenade upgrade testing harness. Ceilometer was integrated before these requirements were added but the requirements apply retroactively. Therefore, ceilometer must be added to the harness.
Testing with grenade involves:
This document considers the upgrade and tempest testing but not the javelin testing. Javelin will be addressed in another (forthcoming) document.
Prior to the Juno cycle ceilometer was neither a default service in DevStack nor enabled in tempest. The relevant configuration must be changed to allow testing in Grenade.
Enable ceilometer in Grenade (see Work Items for details).
Given the commitment to Grenade and the project graduation requirements, this is the way to go.
These changes will mean a more positive upgrade experience for end users.
There have been concerns that running ceilometer in the gate will negatively impact performance there. This had been true but recent changes in the sqlalchemy driver and database schema have shown enough improvement that ceilometer can be turned on.
Active testing will mean the discovery of bugs that someone will have to fix.
Who is leading the writing of the code? Or is this a blueprint where you’re throwing it out there to see who picks it up?
If more than one person is working on the implementation, please designate the primary author and contact.
As/when ceilometer expands to include additional services, it will be necessary to adjust devstack and grenade to manage (stop, start, cleanup) those services.
Other than those listed above, no additional dependencies.
These changes improve testing and will be validated there.