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

From EGIWiki
Jump to: navigation, search
(Created page with "<style type="text/css">P { margin-bottom: 0.21cm; }A:link { }</style> This is draft of procedure and related work instructions for User, Provider and Broker <br> ...")
 
Line 1: Line 1:
&lt;style type="text/css"&gt;P { margin-bottom: 0.21cm; }A:link { }&lt;/style&gt;
 
 
 
This is draft of procedure and related work instructions for User, Provider and Broker  
 
This is draft of procedure and related work instructions for User, Provider and Broker  
  
Line 89: Line 87:
 
#<span style="background: transparent">Enter
 
#<span style="background: transparent">Enter
 
</span>
 
</span>
 +
 +
  
 
e-GRANT, login, Click “Request new allocation” button.  
 
e-GRANT, login, Click “Request new allocation” button.  
Line 94: Line 94:
 
#<span style="background: transparent">Chose
 
#<span style="background: transparent">Chose
 
</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
 
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
Line 100: Line 102:
 
#<span style="background: transparent">You
 
#<span style="background: transparent">You
 
</span>
 
</span>
 +
 +
  
 
may safe your request in draft state (is not beeing processed) and you can edit it later on.  
 
may safe your request in draft state (is not beeing processed) and you can edit it later on.  
Line 105: Line 109:
 
#<span style="background: transparent">Before
 
#<span style="background: transparent">Before
 
</span>
 
</span>
 +
 +
  
 
sending request you may, by clicking on “Invalidate Request”.  
 
sending request you may, by clicking on “Invalidate Request”.  
Line 110: Line 116:
 
#<span style="background: transparent">When
 
#<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
 
satisfied with your Request, click “Submit to EGI” button. The mail to Broker is sent. <span style="background: #ffff00">Await for
Line 122: Line 130:
 
#<span style="background: transparent">RP
 
#<span style="background: transparent">RP
 
</span>
 
</span>
 +
 +
  
 
check (should be notified by email), that new OLA appeared (negotiation scenario)  
 
check (should be notified by email), that new OLA appeared (negotiation scenario)  
Line 127: Line 137:
 
#<span style="background: transparent">RP
 
#<span style="background: transparent">RP
 
</span>
 
</span>
 +
 +
  
 
logs in to e-GRANT tool with GOCBD Admin role.  
 
logs in to e-GRANT tool with GOCBD Admin role.  
Line 132: Line 144:
 
#<span style="background: transparent">In
 
#<span style="background: transparent">In
 
</span>
 
</span>
 +
 +
  
 
“Requests being processed” panel clicks on SLA Name to be processed.  
 
“Requests being processed” panel clicks on SLA Name to be processed.  
Line 137: Line 151:
 
#<span style="background: transparent">RP
 
#<span style="background: transparent">RP
 
</span>
 
</span>
 +
 +
  
 
may reject, negotiate and accept proposal.  
 
may reject, negotiate and accept proposal.  
Line 142: Line 158:
 
#<span style="background: transparent">When
 
#<span style="background: transparent">When
 
</span>
 
</span>
 +
 +
  
 
RP wants to negotiate, clicks on “Negotiate” button.  
 
RP wants to negotiate, clicks on “Negotiate” button.  
Line 147: Line 165:
 
#<span style="background: transparent">RP
 
#<span style="background: transparent">RP
 
</span>
 
</span>
 +
 +
  
 
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 158: Line 178:
 
#<span style="background: transparent">Broker
 
#<span style="background: transparent">Broker
 
</span>
 
</span>
 +
 +
  
 
checks (should be notified by email), that new request appeared.  
 
checks (should be notified by email), that new request appeared.  
Line 163: Line 185:
 
#<span style="background: transparent">Broker
 
#<span style="background: transparent">Broker
 
</span>
 
</span>
 +
 +
  
 
logs in to e-GRANT tool with Broker role.  
 
logs in to e-GRANT tool with Broker role.  
Line 168: Line 192:
 
#<span lang="en-US"><span style="background: transparent">In
 
#<span lang="en-US"><span style="background: transparent">In
 
</span></span>
 
</span></span>
 +
 +
  
 
“Requests being processed” panel clicks on SLA Name to be processed.  
 
“Requests being processed” panel clicks on SLA Name to be processed.  
Line 173: Line 199:
 
#<span style="background: transparent">Broker
 
#<span style="background: transparent">Broker
 
</span>
 
</span>
 +
 +
  
 
may reject, find pools or negotiate request.  
 
may reject, find pools or negotiate request.  
Line 178: Line 206:
 
#<span style="background: transparent">Broker
 
#<span style="background: transparent">Broker
 
</span>
 
</span>
 +
 +
  
 
clicks “Find pools”. There are possible pools shown.  
 
clicks “Find pools”. There are possible pools shown.  
Line 183: Line 213:
 
#<span style="background: transparent">Broker
 
#<span style="background: transparent">Broker
 
</span>
 
</span>
 +
 +
  
 
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 193: Line 225:
 
#<span style="background: transparent">In
 
#<span style="background: transparent">In
 
</span>
 
</span>
 +
 +
  
 
“Requests being processed” panel clicks on SLA Name to be processed.  
 
“Requests being processed” panel clicks on SLA Name to be processed.  
Line 198: Line 232:
 
#<span style="background: transparent">In
 
#<span style="background: transparent">In
 
</span>
 
</span>
 +
 +
  
 
“Underpinned OLAs” clicks Version link  
 
“Underpinned OLAs” clicks Version link  
Line 203: Line 239:
 
#<span style="background: transparent">Takes
 
#<span style="background: transparent">Takes
 
</span>
 
</span>
 +
 +
  
 
appropriate action.  
 
appropriate action.  
Line 208: Line 246:
 
#<span style="background: transparent">If
 
#<span style="background: transparent">If
 
</span>
 
</span>
 +
 +
  
 
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:28, 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, 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.