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

From EGIWiki
Jump to: navigation, search
Line 85: Line 85:
 
=== Request creation  ===
 
=== Request creation  ===
  
#<span style="background: transparent">Enter
+
#Enter e-GRANT, login,
</span>
+
#Click “Request new allocation” button.
 +
#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).
 +
#You may safe your request in draft state (is not beeing processed) and you can edit it later on.
 +
#Before sending request you may, by clicking on “Invalidate Request”.
 +
#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.
  
 +
<br>
  
 +
== 2. Provider Side  ==
  
e-GRANT, login, Click “Request new allocation” button.
+
=== New OLA handling  ===
  
#<span style="background: transparent">Chose
+
#<span style="background: transparent">RP
 
</span>
 
</span>
  
  
  
Start (<span style="background: #ffff00">at least 7 days ahead</span>), end (<span style="background: #ffff00">no more than 1 year)</span>, user community, vo and enter description of activity field. Enter Computing time in HEPSPEC-hours, and Storage capacity <span style="background: #ffff00">(one
+
<br>  
of them may be zero</span>).
+
 
 +
<br>  
  
#<span style="background: transparent">You
+
<br>
 +
 
 +
check (should be notified by email), that new OLA appeared (negotiation scenario)
 +
 
 +
#<span style="background: transparent">RP
 
</span>
 
</span>
  
  
  
may safe your request in draft state (is not beeing processed) and you can edit it later on.
+
<br>
  
#<span style="background: transparent">Before
+
<br>  
</span>
 
  
 +
<br>
  
 +
logs in to e-GRANT tool with GOCBD Admin role.
  
sending request you may, by clicking on “Invalidate Request”.
+
#<span style="background: transparent">In
 
 
#<span style="background: transparent">When
 
 
</span>
 
</span>
  
  
  
satisfied with your Request, click “Submit to EGI” button. The mail to Broker is sent. <span style="background: #ffff00">Await for
+
<br>  
response for a 3 days</span>  
 
  
 
<br>  
 
<br>  
  
== 2. Provider Side  ==
+
<br>
  
=== New OLA handling  ===
+
“Requests being processed” panel clicks on SLA Name to be processed.
  
 
#<span style="background: transparent">RP
 
#<span style="background: transparent">RP
Line 133: Line 142:
  
  
check (should be notified by email), that new OLA appeared (negotiation scenario)
+
<br>
  
#<span style="background: transparent">RP
+
<br>  
</span>
 
  
 +
<br>
  
 +
may reject, negotiate and accept proposal.
  
logs in to e-GRANT tool with GOCBD Admin role.
+
#<span style="background: transparent">When
 
 
#<span style="background: transparent">In
 
 
</span>
 
</span>
  
  
  
“Requests being processed” panel clicks on SLA Name to be processed.
+
<br>
  
#<span style="background: transparent">RP
+
<br>  
</span>
 
  
 +
<br>
  
 +
RP wants to negotiate, clicks on “Negotiate” button.
  
may reject, negotiate and accept proposal.
+
#<span style="background: transparent">RP
 
 
#<span style="background: transparent">When
 
 
</span>
 
</span>
  
  
  
RP wants to negotiate, clicks on “Negotiate” button.
+
<br>  
 
 
#<span style="background: transparent">RP
 
</span>
 
  
 +
<br>
  
 +
<br>
  
 
enters new proposed values. Then RP can save a draft or Send proposal. The mail to the Broker is sent.  
 
enters new proposed values. Then RP can save a draft or Send proposal. The mail to the Broker is sent.  
Line 180: Line 186:
  
  
 +
 +
<br>
 +
 +
<br>
 +
 +
<br>
  
 
checks (should be notified by email), that new request appeared.  
 
checks (should be notified by email), that new request appeared.  
Line 187: Line 199:
  
  
 +
 +
<br>
 +
 +
<br>
 +
 +
<br>
  
 
logs in to e-GRANT tool with Broker role.  
 
logs in to e-GRANT tool with Broker role.  
Line 194: Line 212:
  
  
 +
 +
<br>
 +
 +
<br>
 +
 +
<br>
  
 
“Requests being processed” panel clicks on SLA Name to be processed.  
 
“Requests being processed” panel clicks on SLA Name to be processed.  
Line 201: Line 225:
  
  
 +
 +
<br>
 +
 +
<br>
 +
 +
<br>
  
 
may reject, find pools or negotiate request.  
 
may reject, find pools or negotiate request.  
Line 208: Line 238:
  
  
 +
 +
<br>
 +
 +
<br>
 +
 +
<br>
  
 
clicks “Find pools”. There are possible pools shown.  
 
clicks “Find pools”. There are possible pools shown.  
Line 215: Line 251:
  
  
 +
 +
<br>
 +
 +
<br>
 +
 +
<br>
  
 
checks metric values and decides on usage of given pool by clicking on the select box and click “Save” button.<span style="background: transparent">
 
checks metric values and decides on usage of given pool by clicking on the select box and click “Save” button.<span style="background: transparent">
Line 227: Line 269:
  
  
 +
 +
<br>
 +
 +
<br>
 +
 +
<br>
  
 
“Requests being processed” panel clicks on SLA Name to be processed.  
 
“Requests being processed” panel clicks on SLA Name to be processed.  
Line 234: Line 282:
  
  
 +
 +
<br>
 +
 +
<br>
 +
 +
<br>
  
 
“Underpinned OLAs” clicks Version link  
 
“Underpinned OLAs” clicks Version link  
Line 241: Line 295:
  
  
 +
 +
<br>
 +
 +
<br>
 +
 +
<br>
  
 
appropriate action.  
 
appropriate action.  
Line 248: Line 308:
  
  
 +
 +
<br>
 +
 +
<br>
 +
 +
<br>
  
 
Broker agrees, then click on “Accept” and “Home” to get to the list of all Requests.
 
Broker agrees, then click on “Accept” and “Home” to get to the list of all Requests.

Revision as of 08:38, 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

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 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)

  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.