Need to get more experience in production use to better define the critical attributes.
Went over ITB sites to check validity of attributes. Two sites have problems - FNAL_FERMIGRID_TEST (not up to date). For UCSDT2-ITB1 condor-status not being run since it wasn't a user.
Need to investigate an issue with Class Ad evaluation in the GIP validator.
GUMS service entities query, and translation by CEMon to BDII may have a problem. Is there a problem with the aggregator filtering non-registered ITB sites. Why does the BDII retaining old information.
GIP configuration issue w/ CEMon
triage config issue to GIP support issues to Will
something that can be improved with standard trouble shooting notes to be included in the release documentation
WS-GRAM testing deployment
Follow-up on these issues
VOs willing to run workflows through WS-GRAM (Suchandra, Jeff)
STAR * Have been working with Star developers - looks straightforward. Having problems with production clients at Brookhaven. Older version of Condor 6.8.4. * Firewall problems with the OSG 0.6 client.
LIGO * Confirmed w/Britta the ability to run Pegasus through WS-Gram
Replicating earlier ws-gram work against ITB sites (Jeff)
started this work last week.
Half the sites are working fine, the other are having small problems.
Core container issues that Gram relies on - Charles w
Does Gratia work correctly with WS-Gram if the condor 6.9? Need to address this.
Documentation updated.
RSV status (Arvind)
RSV SAM reporting status update
Sample record uploaded from OSG side to SAM.
Efforts ongoing between Arvind and James/David/Piotr to automate process from ITB RSV collector to other end. On our end, we've clarified what needs to be sent and will write code to make it happen; on their side they need to do some code mods to allow data that conforms to the WLCG specs 0.91 (that we'll be sending -- their system is not tweaked fully to comply with the specs yet).
Arvind will write a debugging guide for failures seen in the SAM console.
From CE point of view, no changes required in advance of OSG 0.8 deployment.
Any follow-up on the issue:
Condor-devel brought in because production condor installations (6.8.x) don't support cron functionality; RSV should use existing condor if user points to the a condor 6.9.x installation; In general case condor should work, but there might be a conflict between ManagedFork and RSV since both use the local universe; Scot Kronenfeld thinks this might not work, but Terrence will try it out on a system to check
Terrence reported back to the ITB list that setting certain environment variables before pulling in the OSG-RSV package, as documented in the twiki, worked fine for him. RSV was using his existing 6.9.x condor install following that.
Arvind going on vaction next Thursday for three weeks.
Will plan to have infrastructure in place for the SAM before
Scott Kronefeld will be the point of contact for RSV
Xin: at BNL experiencing a problem restarting RSV, not removing stale Condor processes. Unique installation? Scott investigating.
OSG 0.8 Deployment readiness (RobQ)
Focus on preparations for central OSG services at GOC and elsewhere.
bdii - schema update required
bdii-aggregator (no change) and monitor (no change)