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

integration status
SMART_READER_LITE
LIVE PREVIEW

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


slide-1
SLIDE 1

GRATIA/APEL & SSM INTEGRATION STATUS

John Weigand Tanya Levshina

slide-2
SLIDE 2

Project History

 Started as part of the Gratia Project, now is outside

  • f the project scope

 Atlas has contributed some efforts as well, but

project is mostly CMS contribution

 OSG Operation is expected to take over the

  • perational aspect in FY12

22/9/2011 EGI Techical Forum

2

slide-3
SLIDE 3

OIM LCG Office MOU EGI Accounting Portal Gratia db db probe

Resource

probe

Resource

accounting probes

Resource

Resource Group

  • 1. register
  • 2. register
  • 3. push probes

data

  • 4. Pull data
  • 6. insert APEL

data OSG Data Verificator

Gratia/WLCG script

  • 8. send

APEL report

  • 5. verify
  • 7. get topology

GRATIA/APEL (current workflow)

GIP probes 3

Gratia/Apel Host

slide-4
SLIDE 4

Proposed workflow

OIM LCG Office MOU EGI Accounting Portal Gratia db db probe

Resource

probe

Resource

accounting probes

Resource

Resource Group

  • 1. register
  • 2. register
  • 3. push probes

data

  • 4. Pull data
  • 6. insert APEL

data OSG Data Verificator

Gratia/WLCG script

  • 8. get

APEL report

  • 5. verify
  • 7. get topology

GIP probes APEL API APEL API

Rebus Interface

4

Gratia/Apel Host

slide-5
SLIDE 5

Questions

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

  • n 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
  • f the EGI portal UI?

22/9/2011 EGI Techical Forum

5

slide-6
SLIDE 6

Integration Plans

 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!

22/9/2011 EGI Techical Forum

6