-
Notifications
You must be signed in to change notification settings - Fork 18
ESGFCmip5Meetings|20111025
| Wiki Reorganisation |
|---|
| This page has been classified for reorganisation. It has been given the category MOVE. |
| The content of this page will be revised and moved to one or more other pages in the new wiki structure. |
Attendees
Bob, Estani, Neil, Stephen, Don, Eric, Nate, Sylvia
Original Agenda was as below. We covered the first 3 topics.
- Effective prioritizing of tasks for operational CMIP5: 1. Trackback / CIM harvest consistent accross Gateways 2. Improving MyProxy
3. Next Generation Search -- Gateway 2.0 deployment schedule
4. OPeNDAP -- security, consistent configuration.
5. End-user GridFTP
6. Metrics -- federation-wide download statistics
7. Authorization-aware search
8. DRS conformance. Can Karl's scriptable download scenario be achieved?
9. Replication
Gateway 1.3.3 will be released imminently to patch a cross-site scripting flaw. This version also includes improved CIM Atom feed robustness.
Sylvia will be raising Trackback deployment issues on Jira and pushing to get it consistently deployed throughout the federation. The Gateway FAQ will be updated to include guidance on ensuring Trackback is working.
A full overview of trackback status has been distributed by email. Several Gateways have operational trackback but missing records from the CIM feed (e.g. BADC). Other Gateways need to do more install work to get trackback working (PCMDI, Oakridge).
Some user's find running MyProxyLogon confusing. We'd like users to be able to supply an OpenID and automatically discover their MyProxy endpoint (and username where possible, BADC is an exception). The non-gui MyProxyLogon jar developed by Estani (in esg-myproxy-logon.git) can do this but the code has diverged from the GUI code making them difficult to merge.
-
Neil will add an OpenID discovery option to MyProxyLogon -GUI
-
Stephen will investigate DML for GridFTP and wget
-
Stephen will add OpenID discovery option to the MyProxyClient python package.
We discussed Gateway 2.0 deployment as one route to fixing the search speed and consistency problems. Gateway 2.0-beta will de deployed at NCAR as their operational Gateway within 2 weeks pending tuning of harvesting performance. This will help federation-wide testing. Replication support needs re- implementing and the scope of this task will be established after deployment at NCAR.