[openstack-dev] [Manila] Stackalytics 0.9: new features and improvements

Sturdevant, Mark mark.sturdevant at hpe.com
Fri Oct 23 18:06:47 UTC 2015

Hey Manila CI maintainers,

I added [Manila] to the subject to get your attention, but the details are from an earlier post below.  Notice there is a nice new Manila CI report at http://stackalytics.com/report/ci/manila/7.  Unfortunately most of the Manila drivers are not in driverlog yet, so they don't show up in the report.  Please update driverlog with your CI and contact info.


From: Ilya Shakhat [ishakhat at mirantis.com]
Sent: Friday, October 23, 2015 2:26 AM
To: OpenStack Development Mailing List (openstack-dev at lists.openstack.org)
Subject: [openstack-dev] Stackalytics 0.9: new features and improvements

Hi all,

During the last month we've made a number of changes and improvements in Stackalytics that deserve version tag and special announcement. The most important feature is tracking history of official projects list - highly demanded after shift to 'big tent' model.

The full list of changes below:

1. Stackalytics now respects history of changes in the official programs list. Changes are tracked per-release, so if some project was accepted officially in Liberty, it does not appear in the past and thus does not affect Kilo stats. As anchor points we use tags in governance repo (e.g. april-2015-elections)[1]<https://git.openstack.org/cgit/openstack/governance/>. These tags are related to elections and created a bit before the release thus saving from last-minute changes in the stats.

2. With removal of Stackforge, all projects are now classified in 2 groups: 'OpenStack' = listed in the official projects.yaml [2]<http://git.openstack.org/cgit/openstack/governance/tree/reference/projects.yaml> and 'OpenStack Others' = those that are in openstack organization, but not accepted officially. As before, by default Stackalytics shows official projects.

3. CI metric [3]<http://stackalytics.com/?metric=ci> is redesigned from scratch. Now it analyses votes in merged patches only, the numbers are shown for every driver. List of drivers is synced with DriverLog [4]<http://git.openstack.org/cgit/openstack/driverlog/tree/etc/default_data.json>.

4. Added a new driver status report [5]<http://stackalytics.com/report/ci/cinder/7>. The report shows total number of votes, success rate and the latest result per every driver per module. The report is available for projects that have external CI configured (Nova, Neutron, Cinder, Manila, Sahara, number of Fuel plugins) The data may be not complete now and requires proper configuration in DriverLog's default data (maintainers are welcome to contribute into [4]<http://git.openstack.org/cgit/openstack/driverlog/tree/etc/default_data.json>)

5. Abandoning a change request is now treated as reviewing [6]<https://bugs.launchpad.net/bugs/1498769> and is included into review metric. Only abandoning of other's CRs is taken into account.

6. Reviews for own patches are not included into the stats anymore. In the activity log such reviews are marked with prefix 'Self-' (e.g. Self-Code-Review and Self-Approve)

7. Review processing is made compatible with Gerrit 2.9+, making Stackalytics ready for infra upgrade.


[1] - https://git.openstack.org/cgit/openstack/governance/
[2] - http://git.openstack.org/cgit/openstack/governance/tree/reference/projects.yaml
[3] - http://stackalytics.com/?metric=ci
[4] - http://git.openstack.org/cgit/openstack/driverlog/tree/etc/default_data.json
[5] - http://stackalytics.com/report/ci/cinder/7
[6] - https://bugs.launchpad.net/bugs/1498769

More information about the OpenStack-dev mailing list