Tool to analyze update progress

Description

I field fairly constant complaints about slow updates. However, by time we do post-mortem, there's no evidence of problems.

I'd like to have a small CLI available - "oasis-update-status" - that prints out, for a given repo, the age of each Stratum-1 revision, Stratum-0 revision (if possible), and client revision / age.

The idea is that if a user has a complaint along these lines, they can run this script so we can at least isolate where the problem occurs.

I believe such a thing is posted to the twiki; it just needs to be converted to the RPM.

Freshdesk Tickets

None

Activity

Show:
Dave Dykstra
February 5, 2016, 8:26 PM

For the convenience of those looking at this ticket, as noted in the upstream ticket we plan to have this be a script in /cvmfs/grid.cern.ch/utils rather than putting it in any rpm.

Dave Dykstra
December 3, 2015, 4:39 PM
Brian Bockelman
July 28, 2015, 2:36 PM

Note from last OASIS meeting: Dave agreed to spend a very small amount of time on this (1 hour) and post how far he was able to get. If it looks like a lot more time is needed, we'll reevaluate the approach.

Dave Dykstra
July 23, 2015, 2:19 PM

Is it really that high of a priority? I have other things that I think are higher priority that I've not been able to get to yet in my 25% OSG technology time. Also it takes a long time to roll things out to users via any rpm.

Yes some cvmfs_config commands can be run by users, so this one could be too.

Brian Bockelman
July 23, 2015, 1:44 PM

Sure, that works too - I'm more concerned about getting a tool out within the next month or so rather than precisely where it lives.

For cvmfs_config – would users still be able to use this? I understand some functionality might take admin privileges, but would like minimal functionality be unprivileged.

Won't Do

Assignee

Dave Dykstra

Reporter

Brian Bockelman