Friday, June 17, 2011
Note: Be prepared to zoom in a lot. Job ID's are printed at the beginning of execution. Green lines are successful completions. Red lines are Evicted or Job Disconnected jobs.
View on Google Docs
Very ugly source is on github: https://github.com/djw8605/condor_log_analyze
It's times like this I wish I had a tile wall again.
Note, I found chrome's pdf viewer faster than Preview.
Friday, June 10, 2011
What's interesting is that we rarely run jobs at RENCI-Engagement, OSCER, or GPGRID. It's difficult to interpret this. Since we run so many workflows, it's not clear to me that this means much.
|Special thanks to Purdue!|
Barely a light load on the glidein machine. This many jobs would have not worked on the old glidein machine, which was a Xen VM.
Of course with Condor, load and memory usage are more a function of # running jobs rather than jobs in queue.
Also, the new GlideinWMS gratia monitoring is picking up the usage:
Wednesday, June 8, 2011
|Status captured 6-8-11|
We also keep track of transfers, but they are summarized and aggregated at the probe before reaching the database.
So, in summary, kudos to the gratia operations team.
(NOTE: I may have forgotten some optimizations that we use. But still, that's a lot of records)
Monday, June 6, 2011
I’ve been working on gratia graphs with Ashu Guru for the new GlideinWMS probe. I’ve stumbled upon very odd command line usage of voms-proxy-init.
In order to get a role to work with voms-proxy-init, the command needs to be:
voms-proxy-init -voms hcc:/hcc/Role=collabThis command will give the proxy the role collab in the generic group hcc.
VOMS also has the ability to use ‘groups’ in the vo to distinguish between users. In order to use a group, the syntax is:
voms-proxy-init -voms hcc:/hcc/testgroup/Role=collabThis command will give the proxy the role collab in the group testgroup of the HCC VO.
Not necessarily the most complicated command line I have used, but certainly one of the worst documented.
voms-proxy-init -helpdoesn’t help at all.