18 January 2011, 15:00 - 16:10 Present: Adrian, David, Salman, Christian, Balazs, Daniel, Aleksandr, Jon, Oxana Tasks not in the ToDo list yet ------------------------------ * Janitor: the main problem is the unnecessary RDF dependency (can be replaced with a plain XML database). Adrian thinks he can manage to look at it in February. * Configuration: task for ARC CE is to test that all old arc.conf settings have proper effect on A-REX. Make sure that arc.conf can be used with A-REX. Daniel says A-Rex, GridFTP and LDAP infosys can be configured in arc.conf * JURA vs urlogger: only one should be supported; clean-up should be done by February. Oxana will ask Gabor Szigeti to do the comparison, check whether JURA reports to new SGAS. Check which of them has better perspectives of switching to APEL in future. Compare usage records, communication channels. GLUE2 publishing ---------------- Adrian reports that infoproviders can now provide Glue2 LDIF directly and it even validates agains LDAP Glue2 schema. There is no configuration yet. The code is in SVN, not enabled yet. It should be possible to publish 3 different schemas (ARC, Glue1.3, Glue2), however, some streamlining might be needed (e.g., one shouldn't need to run imfoproviders twice). Possible configuration option: infosys-glue2-ldap=enable Adrian will announce when ready for testing, will discuss with Daniel about modifying grid-infosys startup scripts. XML and LDIF is produced in one go (same script). XML: UserDomain is still missing Documentation ------------- Two back-end documents exist, merger is needed. Christian will be an editor of the merged document, Daniel will help, too. Info on framework, how to integrate new back-ends, explain what info is published and how, and how to configure everything. Access control (related to configuration) ----------------------------------------- Aleksandr raised the question of how the authorization (access control) of the A-REX based CE will be done. The security in arc1 based code is completely different than those of "old" arc0 code. The powerful authorization features of the HED can be used, but that is not yet "enabled" for new CE, config-wise not supported (not even in the ini config). This is a complete new area that needs lot of work. It can actually be seen as HED work, since not only relevant for the CE. Balazs admits that indeed we have a huge gap (problem) here. But since in the February release we still want to use the following combination as production deployment: gridftp interface + A-REX (WS inteface turned off) + ARIS (LDAP for info) we are safe: authorization (along the features of arc.conf) and Grid user mapping is done in/via the GridFTP layer However, for post-EMI-1, we need to plan/allocate real efforts for this area. Aleksandr agreed. Staging, cache -------------- Balazs raised one more potential issue: the status of "new" uploaders/downloaders/cache compared to arc0 code. David confirmed that everything should be there and supposed to work reliably, ready for production deployment. Testing is of course needed but David is confident about this important move (old data -> new data). Next meeting ------------ Monday February 7 morning. A.O.B. ----- Balazs asked everyone to use nordugrid-discuss for communication since arc-emi is not available for everyone.