Goal: to discuss current integration issues
----------------------------------------------------------------------
----------------------------------------------------------------------
Agenda:
----------------------------------------------------------------------
1) Welcome and overview current status:
----------------------------------------------------------------------
a) Integration of UNICORE services into GOCDB
----------------------------------------------------------------------
was discussed during the OTAG meeting in Amsterdam:
OTAG meeting https://www.egi.eu/indico/conferenceTimeTable.py?confId=153#20110125.detailed
GOCDB overview: https://www.egi.eu/indico/getFile.py/access?contribId=1&sessionId=5&resId=1&materialId=slides&confId=153
David Merediths slides on GOCDB status/roadmap:
https://www.egi.eu/indico/getFile.py/access?contribId=4&sessionId=5&resId=0&materialId=slides&confId=153
Extract from Daniele Cesinis notes (no minutes yet):
*Requirement #944: New GOCDB service-types for Globus and UNICORE resources https://rt.egi.eu/rt/Ticket/Display.html?id=944 (also named
New (GLUE2 compatible) GOCDB service-types enums (e.g. for Globus and UNICORE))
GLUE2 service_t matrix. GOCDB is suggesting reverse NS syntax to identify a service
changing the name of service, could it be a problem?
Comment EI: a number of tools are using the services names. It could be painful.
It was decided that the GLUE2 compliance is ok for the capability part, but for the service naming it should be carefully verified the impact on other tools and m/w. The renaming should apply only for new service types, migrating old ones can be very problematic.
*Requirement #975:New endpointURL field for endpoint service types as needed for UNICORE https://rt.egi.eu/rt/Ticket/Display.html?id=975
Comment EI: the URL collection in GOCDB is not sustainable
It was decided that GOCDB should not contain dynamical information, so on a longer term adding URLs to GOCDB should be rejected. To ease the UNICORE integration a task force will be created - GOCDB representatives should attend - task force should start its work before spring.
In the longer term the Registry that will be released by EMI should contain URLs, not the GOCDB. If the EMI registry will not be out when UNICORE is ready to be integrated in the production infrastructure the quick and dirty solution proposed by David in his slides can be TEMPORARY adopted. This solution is to add URL field for SE and repeat SE to represent different URLs (point 2) in the last slide.
Quick solution: add URL field for SE and repeat SE to represent different URLs. To be applied After having verified the timeline for the EMI registry.
----------------------------------------------------------------------
b) Monitoring
----------------------------------------------------------------------
Krzysztof Benedyczak for NGI_PL is about to provide the first Nagios probe packages. Emir Imagmagic would like to use the 3 weeks of development in February to integrate these packages and config tools.
Quote Krystof Benedyczak:
Our implementation is mostly completed and we are starting internal testing in PL-Grid: RPMs of probes and autoconfigurator are being installed on EGI-Nagios. If you want to also verify this simultaneously then sources are up-to-date in this SF repo:
https://unicore-life.svn.sourceforge.net/svnroot/unicore-life/monitoring
Those SVN modules should be interesting for you:
UMI-Autoconf <- this one contains documentation of the whole system
nagios-service_state_refresher
UMI-Probes <- here you can find short docs on particular probes.
RPM spec files and rpm build scripts are also there.
We are still working on some minor things like updating documentation a bit and few remaining probes to make them fully compliant with Nagios command line conventions.
We haven't done a formal binary release yet, we plan to do this after testing is finished. Anyway the "unofficial" RPMs can be fetched from:
http://alfred.studmat.umk.pl/~szczeles/PL-Grid/
The 3 RPMs which contain the monitoring framework depend on 2 other which are not in standard CENTOS/SL repos: UNICORE and UVOS command line clients. You can find those RPMs also under the above link, however those are RPMs which are going to be included in EMI-1 release (so are the same as the ones build by Etics - those are not coming from PL-Grid).
[End of quote]
The UNICORE Nagios probe ticket
https://rt.egi.eu/rt/Ticket/Display.html?id=306
needs an update on the current development going on!
----------------------------------------------------------------------
c) GGUS
----------------------------------------------------------------------
EMI has set up a 3rd level structure within the EGI Helpdesk (GGUS) for its various middleware stacks and services. Everything allright?
----------------------------------------------------------------------
d) Early Adopters
----------------------------------------------------------------------
----------------------------------------------------------------------
2) GOCDB
----------------------------------------------------------------------
Do we understand the proposed solutions, are we satisfied with it?
Is it time now to add further UNICORE service types into GOCDB, now?
So far
# UNICOREX
# unicore-registry
# unicore-gateway
https://documents.egi.eu/secure/RetrieveFile?docid=111&version=21&filename=EGI-MS407-final.pdf
Workflow Engine
Service Orchestrator
CIS
XUUDB
UVOS
Target System Interface (TSI)
SIMON
correct naming in the new GLUE2 naming scheme?
----------------------------------------------------------------------
3) Monitoring
----------------------------------------------------------------------
Is GOCDB requirement #975 really working as a showstopper now?
Which probes are about to be integrated in the first stage now:
http://alfred.studmat.umk.pl/~szczeles/PL-Grid/UMI-Probes.html
Coordination with NGI_DE?
Information on https://wiki.egi.eu/wiki/UNICORE_6_Nagios_sensors_implementation still valid?
What about CIS?
Who shall update the ticket https://rt.egi.eu/rt/Ticket/Display.html?id=306 ?
----------------------------------------------------------------------
4) Accounting plans
----------------------------------------------------------------------
Currently no means of collecting accounting and usage records are directly implemented within UNICORE. Instead, this is done directly via the underlying batch system, see for example as in the DEISA project, where the accounting data is converted into OGF-UR format and provided according to XUUDB access control.
NGI_PL has a locally working accounting publishing solution. Details, further information?
Accounting roadmap published in https://www.egi.eu/indico/getFile.py/access?contribId=16&sessionId=3&resId=0&materialId=0&confId=153 (page 10 and onward)
" Integrating other accounting systems to make sure all sites/NGIs are covered.
No firm plan. Complete requirements capture and draft solutions by end of April 11." (from John Gordons slides: https://www.egi.eu/indico/materialDisplay.py?contribId=3&materialId=0&confId=299 )
-> Need to collect and specify our requirements until then!
----------------------------------------------------------------------
5) Next meeting?
----------------------------------------------------------------------
When?
Topics?
- More accounting,
- Dashboard
- ARGUS authorization framework
----------------------------------------------------------------------
6) AOB
----------------------------------------------------------------------
----------------------------------------------------------------------
----------------------------------------------------------------------
Connection Details:
----------------------------------------------------------------------
There is an EVO meeting booked:
Title: UNICORE integration taskforce
Description: Today: Status analysis and brainstorming
Community: Universe
Meeting Access Information:
- Meeting URL
http://evo.caltech.edu/evoNext/koala.jnlp?meeting=MsMiMI2i2nDMD29u99Dt9s
- Phone Bridge
ID: 289 1211
Central European Time (+0100)
Start 2011-02-04 09:30
End 2011-02-04 13:00
Japan Standard Time (+0900)
Start 2011-02-04 17:30
End 2011-02-04 21:00
Eastern Standard Time (-0500)
Start 2011-02-04 03:30
End 2011-02-04 07:00
Pacific Standard Time (-0800)
Start 2011-02-04 00:30
End 2011-02-04 04:00
EVO Phone Bridge Telephone Numbers:
---------------
- USA (Caltech, Pasadena, CA)
+1 626 395 2112
- Switzerland (CERN, Geneva)
+41 22 76 71400
- Slovakia (UPJS, Kosice)
+421 55 234 2420
- Italy (INFN, several cities)
http://server10.infn.it/video/index.php?page=telephone_numbers
Enter '4000' to access the EVO bridge
- Germany (DESY, Hamburg)
+49 40 8998 1340
- USA (BNL, Upton, NY)
+1 631 344 6100
- United Kingdom (University of Manchester)
+44 161 306 6802
- Australia (ARCS)
+61
Adelaide 08 8463 1011
Brisbane 07 3139 0705
Canberra 02 6112 8742
Hobart 03 623 70281
Melbourne 03 8685 8362
Perth 08 6461 6718
Sydney 02 8212 4591
- Netherlands (Nikhef, Amsterdam)
+31 20 7165293
Dial '2' at the prompt
- Canada (TRIUMF, Vancouver)
+1 604 222 7700
- Czech Republic (CESNET, Prague)
+420 95 007 2386
- USA (MIT, Cambridge, MA)
+1 617 715 4691
- France (RAP, Paris)
+33 144 27 81 50
