MirrorManager Analysis Proposal: Measuring aggregate adoption delay for updates

[Jeff Spaleta]

Question to try to answer:
   How long does it take for a yum update to reach 50% and 90% adoption.
   Reference -devel-list discussion:
https://www.redhat.com/archives/fedora-devel-list/2009-Jan
uary/msg01456.html
Solution:
  Timestamp analysis of UserAgent string for mirrorlist requests
matching updated yum client information after a yum update is
released.
Output:
  Histogram plot showing number of clients binned in elapsed time
until first occurrence new UserAgent string detected for that IP

I have the pythonic pieces in place now to do this sort of analysis in
fedora infrastructure without having to personally have access to the
log files.  This is the first example of the type of aggregate ip
address analysis that can be done quite easily so that results can be
made available to contributors.  Before I go off and just do it, I
thought it best that there be some sort of approval step to make sure
each of the new analysis efforts is something the Fedora Board feels
should be produced.  There are a number of things I feel would be
interesting and valuable to produce as analysis products from the
mirrormanager logs, but its not my decision to make as to whether or
not they should be produced.    I want to run by each analysis type on
the advisory board list before I implement it to make sure I am not
going to produce something that is harmful.

-jef"hopes this is short enough for Seth"spaleta