Resource Allocation Procedure and Work Instruction

From EGIWiki
Revision as of 08:28, 19 March 2014 by Szymocha (talk | contribs)
Jump to: navigation, search

This is draft of procedure and related work instructions for User, Provider and Broker


Request – Service Level Agreement (SLA)

OLA – Operations Level Agreement – between and Resource Provieder

SLA Sections – Service Level Agreement Sections related to OLA with given Resource Provider

Request Handling Procedure (draft)

User authentication

Broker checks that users has valid x.509 certificate supported by (e.g. EGI EUGridPMA organization). If not, Broker suggest User to obtain certificate.

Broker checks that User is member of VO. If not, Broker points User to documentation on creation of new vo:

Request validation (non blocking 3 days, executed in parallel)

Broker notifies Gergely Sipos (and mailing list). When Gergely veto is taken into account later in the procedure? At any step?

Request vs resource pool matching (executed in parallel)

Broker matches resources, by clicking on Match pools button. Broker choose pool according to scenario (Free hands, Right to revoke, Negotiated – what is the threshold on resources?!)

Request tuning / fitting activities (matched or „around” matched)

OLA creation – description of Activity 1

OLA confirmation/rejection – description of Activity 2

OLS renegotiation – description of Activity 3

SLA Section creation – description of Activity 4

SLA Section negotiation step – description of Activity 5

Binding OLA configured on site (VO on site, resource allocation)

e-GRANT sends notifications to Resource Providers. Broker checks that resources are configured and available to User?

Offer exploitation

User exploits the allocation. In case of problems creates ticket in GGUS assigned to ???

Offer review

User evaluates the cooperation with

Work Instructions (draft)

1. User Side

Request creation

  1. Enter

e-GRANT, login, Click “Request new allocation” button.

  1. Chose

Start (at least 7 days ahead), end (no more than 1 year), user community, vo and enter description of activity field. Enter Computing time in HEPSPEC-hours, and Storage capacity (one of them may be zero).

  1. You

may safe your request in draft state (is not beeing processed) and you can edit it later on.

  1. Before

sending request you may, by clicking on “Invalidate Request”.

  1. When

satisfied with your Request, click “Submit to EGI” button. The mail to Broker is sent. Await for response for a 3 days

2. Provider Side

New OLA handling

  1. RP

check (should be notified by email), that new OLA appeared (negotiation scenario)

  1. RP

logs in to e-GRANT tool with GOCBD Admin role.

  1. In

“Requests being processed” panel clicks on SLA Name to be processed.

  1. RP

may reject, negotiate and accept proposal.

  1. When

RP wants to negotiate, clicks on “Negotiate” button.

  1. RP

enters new proposed values. Then RP can save a draft or Send proposal. The mail to the Broker is sent.

3. Broker Side

New request handling

  1. Broker

checks (should be notified by email), that new request appeared.

  1. Broker

logs in to e-GRANT tool with Broker role.

  1. In

“Requests being processed” panel clicks on SLA Name to be processed.

  1. Broker

may reject, find pools or negotiate request.

  1. Broker

clicks “Find pools”. There are possible pools shown.

  1. Broker

checks metric values and decides on usage of given pool by clicking on the select box and click “Save” button.

  1. Broker clicks on related underpinned OLA, and clicks Send “OLA”. The mail to Resource Provider is sent.

Request negotiation (vs Provider)

  1. In

“Requests being processed” panel clicks on SLA Name to be processed.

  1. In

“Underpinned OLAs” clicks Version link

  1. Takes

appropriate action.

  1. If

Broker agrees, then click on “Accept” and “Home” to get to the list of all Requests.