Difference between revisions of "Resource Allocation Procedure and Work Instruction"

From EGIWiki
Jump to: navigation, search
(Request tuning / fitting activities (matched or „around” matched))
Line 13: Line 13:
 
<br>  
 
<br>  
  
== Request Handling Procedure (draft)<br>  ==
+
= Request Handling Procedure (draft)<br>  =
  
 
== User authentication  ==
 
== User authentication  ==
Line 46: Line 46:
 
== Request tuning / fitting activities (matched or „around” matched)  ==
 
== Request tuning / fitting activities (matched or „around” matched)  ==
  
=== OLA creation – description of Activity 1 https://documents.egi.eu/document/2030 ===
+
=== OLA creation – description of Activity 1 https://documents.egi.eu/document/2030 ===
  
=== OLA confirmation/rejection – description of Activity 2 https://documents.egi.eu/document/2030 ===
+
=== OLA confirmation/rejection – description of Activity 2 https://documents.egi.eu/document/2030 ===
  
=== OLS renegotiation – description of Activity 3 https://documents.egi.eu/document/2030 ===
+
=== OLS renegotiation – description of Activity 3 https://documents.egi.eu/document/2030 ===
  
=== SLA Section creation – description of Activity 4 https://documents.egi.eu/document/2030 ===
+
=== SLA Section creation – description of Activity 4 https://documents.egi.eu/document/2030 ===
  
=== SLA Section negotiation step – description of Activity 5 https://documents.egi.eu/document/2030 ===
+
=== SLA Section negotiation step – description of Activity 5 https://documents.egi.eu/document/2030 ===
  
 
=== <br>  ===
 
=== <br>  ===
Line 98: Line 98:
 
=== New OLA handling  ===
 
=== New OLA handling  ===
  
#RP check (should be notified by email), that new OLA appeared (negotiation scenario)
+
#RP check (should be notified by email), that new OLA appeared (negotiation scenario)  
#RP logs in to e-GRANT tool with GOCBD Admin role.
+
#RP logs in to e-GRANT tool with GOCBD Admin role.  
#In“Requests being processed” panel clicks on SLA Name to be processed.
+
#In“Requests being processed” panel clicks on SLA Name to be processed.  
#RPmay reject, negotiate and accept proposal.
+
#RPmay reject, negotiate and accept proposal.  
#When RP wants to negotiate, clicks on “Negotiate” button.
+
#When RP wants to negotiate, clicks on “Negotiate” button.  
 
#RP enters new proposed values. Then RP can save a draft or Send proposal. The mail to the Broker is sent.
 
#RP enters new proposed values. Then RP can save a draft or Send proposal. The mail to the Broker is sent.
  
Line 114: Line 114:
 
#Broker may reject, find pools or negotiate request.  
 
#Broker may reject, find pools or negotiate request.  
 
#Broker clicks “Find pools”. There are possible pools shown.  
 
#Broker clicks “Find pools”. There are possible pools shown.  
#Broker checks metric values and decides on usage of given pool by clicking on the select box and click “Save” button.
+
#Broker checks metric values and decides on usage of given pool by clicking on the select box and click “Save” button.  
 
#Broker clicks on related underpinned OLA, and clicks Send “OLA”. The mail to Resource Provider is sent.
 
#Broker clicks on related underpinned OLA, and clicks Send “OLA”. The mail to Resource Provider is sent.
  

Revision as of 10:53, 19 March 2014

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


Terms

Request – Service Level Agreement (SLA)

OLA – Operations Level Agreement – between EGI.eu 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 EGI.eu. (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: https://wiki.egi.eu/wiki/PROC14


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 https://wiki.egi.eu/wiki/Resource_Pool 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 https://documents.egi.eu/document/2030

OLA confirmation/rejection – description of Activity 2 https://documents.egi.eu/document/2030

OLS renegotiation – description of Activity 3 https://documents.egi.eu/document/2030

SLA Section creation – description of Activity 4 https://documents.egi.eu/document/2030

SLA Section negotiation step – description of Activity 5 https://documents.egi.eu/document/2030


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 EGI.eu


Work Instructions (draft)

1. User Side

Request creation

  1. Enter e-GRANT, login,
  2. Click “Request new allocation” button.
  3. 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).
  4. You may safe your request in draft state (is not beeing processed) and you can edit it later on.
  5. Before sending request you may, by clicking on “Invalidate Request”.
  6. When satisfied with your Request, click “Submit to EGI” button. The mail to Broker is sent. EGI RA team should contact you within 3 days.


2. Provider Side

New OLA handling

  1. RP check (should be notified by email), that new OLA appeared (negotiation scenario)
  2. RP logs in to e-GRANT tool with GOCBD Admin role.
  3. In“Requests being processed” panel clicks on SLA Name to be processed.
  4. RPmay reject, negotiate and accept proposal.
  5. When RP wants to negotiate, clicks on “Negotiate” button.
  6. 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.
  2. Broker logs in to e-GRANT tool with Broker role.
  3. In “Requests being processed” panel clicks on SLA Name to be processed.
  4. Broker may reject, find pools or negotiate request.
  5. Broker clicks “Find pools”. There are possible pools shown.
  6. Broker checks metric values and decides on usage of given pool by clicking on the select box and click “Save” button.
  7. 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.
  2. In “Underpinned OLAs” clicks Version link
  3. Takes appropriate action.
  4. If Broker agrees, then click on “Accept” and “Home” to get to the list of all Requests.