On Wed, Nov 11, 2015 at 12:44:46PM +0300, Ilya Shakhat wrote: > Hi Infra team, > > If you haven't heard anything about DriverLog [0 > <https://wiki.openstack.org/wiki/DriverLog>] yet - it is like Stackalytics > but for vendor drivers. Its data is used in the official marketplace [1 > <http://www.openstack.org/marketplace/drivers/>] as well as in Vendor > Drivers report in Stackalytics [2 <http://stackalytics.com/report/driverlog>]. > The same data is used for CI votes metric [3 > <http://stackalytics.com/?metric=ci>] and CI-health reports e.g. [4 > <http://stackalytics.com/report/ci/sahara/7>]. > > From architecture point-of-view DriverLog contains: > > - default_data.json with the list of drivers maintained by community > - processor which polls gerrit to get the recent votes for every driver > and branch > - API service which exposes all data and allows to make simple filtering > - memcached used for storing data and exchanging it between processor > and API service > > Currently DriverLog is deployed at the same host as Stackalytics and it > would make sense to have it manageable by Infra too. > > Thanks, > Ilya > > [0] - https://wiki.openstack.org/wiki/DriverLog > [1] - http://www.openstack.org/marketplace/drivers/ > [2] - http://stackalytics.com/report/driverlog > [3] - http://stackalytics.com/?metric=ci > [4] - http://stackalytics.com/report/ci/sahara/7 I don't see a reason not to do it, looking at the source code for stackaltyics.o.o we are just forwarding /report/driverlog to stackalytics.com/driverlog; so that will need to be fixed. Infra-roots: should I start up a new spec? We likely want to consider moving driverlog to another host since we are closing in on our 15GB limit on stackalytics.o.o. > _______________________________________________ > OpenStack-Infra mailing list > OpenStack-Infra at lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra