INTEGRATION STATUS John Weigand Tanya Levshina Project History 2 - PowerPoint PPT Presentation

GRATIA/APEL & SSM INTEGRATION STATUS John Weigand Tanya Levshina

Project History 2  Started as part of the Gratia Project, now is outside of the project scope  Atlas has contributed some efforts as well, but project is mostly CMS contribution  OSG Operation is expected to take over the operational aspect in FY12 EGI Techical Forum 22/9/2011

GRATIA/APEL (current workflow) 1. register 3 OIM Resource Group LCG Office Resource MOU Resource 2. register Resource GIP probe probes probe accounting probes 5. verify EGI Accounting OSG Data Portal 3. push probes Verificator data 8. send 6. insert APEL Gratia db data APEL report Gratia/Apel Host 4. Pull data db Gratia/WLCG 7. get topology script

Proposed workflow 1. register 4 OIM Resource Group LCG Office Resource MOU Resource 2. register Resource GIP probe Rebus Interface probes probe accounting probes 5. verify EGI Accounting 8. get 3. push probes APEL API Portal APEL report data OSG Data Verificator Gratia db Gratia/Apel Host 7. get topology 4. Pull data 6. insert APEL db Gratia/WLCG APEL data script API

Questions 5 Is there a drop-dead deadline?  What types of reports will be available from the Accounting Portal? Is there a  programmatic way to retrieve data? This is crucial for our verification module. It looks like an acknowledgment is performed indicating the success/failure of the  communication between the client and consumer. Does this acknowledgment indicate the result at the message level or does this extend to the APEL database update the consumer is performing? How are failures handled? Is it possible to set timeouts and retries?  Is an update an atomic operation (like database commit)?  Currently we reload monthly results daily. How would you propose handling  corrections? Can there be a message format that would allow for removing based on site and year/month? This would simplify processing on our end. When does the data become available from the Accounting Portal (what is the time  delay between sending and reporting)? It appears that the test environment is limited to just the messaging and database  update. Will there be an environment which tests the complete data flow inclusive of the EGI portal UI? EGI Techical Forum 22/9/2011

Integration Plans 6  Start working sometime in October  Could take a couple of months to make a transition  Programmatic retrieval of information is essential for us  The ability to drop and resend data for the current month will help to minimize manual work when data correction is needed.  Good communication is crucial for success of this transition! EGI Techical Forum 22/9/2011