Difference between revisions of "Resource Allocation Procedure and Work Instruction"
Line 32: | Line 32: | ||
In case there were not matched Requests, the output of the process is report to EGI.eu allowing to manage Pool Capacity (add new resources). | In case there were not matched Requests, the output of the process is report to EGI.eu allowing to manage Pool Capacity (add new resources). | ||
= | = Resource Allocation activities: = | ||
== User | #<span style="font-size:15px;font-family:Arial;color:#000000;background-color:transparent;font-weight:normal;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;" />Pool creation - P : Creation of Resource Pool [https://wiki.egi.eu/wiki/Pool_Allocation_For_Providers instruction] (for Resource Providers) | ||
#<span style="font-size:15px;font-family:Arial;color:#000000;background-color:transparent;font-weight:normal;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;">User Request creation - C </span>: Creation of Request [[Resource Allocation Request Handling#Request_creation|instruction]] (for Customers) | |||
#<span style="font-size:15px;font-family:Arial;color:#000000;background-color:transparent;font-weight:normal;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;">User Request validation - C and B</span> | |||
#<span style="font-size:15px;font-family:Arial;color:#000000;background-color:transparent;font-weight:normal;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;">OLA creation based on pool matching - B</span> | |||
#<span style="font-size:15px;font-family:Arial;color:#000000;background-color:transparent;font-weight:normal;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;">OLA (re)negotiation - P and B</span> | |||
#<span style="font-size:15px;font-family:Arial;color:#000000;background-color:transparent;font-weight:normal;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;">OLA confirmation/rejection - P</span> | |||
#<span style="font-size:15px;font-family:Arial;color:#000000;background-color:transparent;font-weight:normal;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;">SLA creation/updating - B </span> | |||
#<span style="font-size:15px;font-family:Arial;color:#000000;background-color:transparent;font-weight:normal;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;">SLA negotiation step - B and C</span> | |||
#<span style="font-size:15px;font-family:Arial;color:#000000;background-color:transparent;font-weight:normal;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;"> SLA confirmation/signing - C | |||
</span> | |||
= Resource Allocation Procedure (draft)<br> = | |||
== Request validation (non blocking 3 days, executed in parallel) == | |||
Broker checks that | Broker checks that Customer has valid x.509 certificate supported by EGI.eu. (e.g. EGI EUGridPMA organization). If not, Broker suggest Customer to obtain certificate. | ||
<span lang="en-US"> Broker checks that | <span lang="en-US"> Broker checks that | ||
</span><span lang="en-US"> | </span><span lang="en-US">Customer </span><span lang="en-US">is</span><span lang="en-US"> | ||
member of VO. </span><span lang="en-US">If not, Broker points | member of VO. </span><span lang="en-US">If not, Broker points Customer</span><span lang="en-US"> | ||
</span><span lang="en-US">to documentation on</span><span lang="en-US"> | </span><span lang="en-US">to documentation on</span><span lang="en-US"> | ||
creat</span><span lang="en-US">ion of ne</span><span lang="en-US">w | creat</span><span lang="en-US">ion of ne</span><span lang="en-US">w Virtual Organization (VO)</span><span lang="en-US">:</span><span lang="en-US"> | ||
</span><span lang="en-US"> | |||
</span>[https://wiki.egi.eu/wiki/PROC14 https://wiki.egi.eu/wiki/PROC14] | </span>[https://wiki.egi.eu/wiki/PROC14 https://wiki.egi.eu/wiki/PROC14] | ||
Broker notifies EGI.eu (support@egi.eu Gergely Sipos). Veto to request(with explanations) should be e-mailed to resource-allocation-support at mailman.egi.eu as soon as possible, no more than 3 days. This description will be sent to Customer. | |||
Broker notifies EGI.eu (support@egi.eu Gergely Sipos). Veto to request(with explanations) should be e-mailed to resource-allocation-support at mailman.egi.eu as soon as possible, no more than 3 days. | |||
<br> | <br> | ||
Line 64: | Line 70: | ||
<br> | <br> | ||
== | == SLA/OLA negotiations <br> == | ||
Broker checks wheter there was EGI.eu veto announced. If yes, Request is Rejected and Customer notified about reason. | Broker checks wheter there was EGI.eu veto announced. If yes, Request is Rejected and Customer notified about reason. | ||
Line 70: | Line 76: | ||
If not, Broker sends to Customer SLA proposal. | If not, Broker sends to Customer SLA proposal. | ||
Customer and Broker negotiate values of the metrics. | |||
If agreement is reached, Customer signes SLA and the offer is binding for both parties. | |||
== Binding OLA configured on site (VO on site, resource allocation) == | == Binding OLA configured on site (VO on site, resource allocation) == | ||
Resource Provider configures resources according to the binding Request. | Resource Provider configures resources according to the binding Request.<span style="background: #ffff00" /><br> | ||
<br> | |||
== Offer exploitation == | == Offer exploitation == | ||
User exploits the allocation. In case of problems creates ticket in GGUS assigned to "Resource Allocation" Support Unit. Then ticket may be assigned to related Resource Provider support unit. | User exploits the allocation. In case of problems creates ticket in GGUS assigned to "Resource Allocation" Support Unit. Then ticket may be assigned to related Resource Provider support unit. | ||
<br> | <br> | ||
Line 101: | Line 96: | ||
== Offer review == | == Offer review == | ||
Customer evaluates the cooperation with EGI.eu | Customer evaluates the cooperation with EGI.eu | ||
<br> | <br> | ||
Line 113: | Line 108: | ||
#Enter e-GRANT, login, | #Enter e-GRANT, login, | ||
#Click “Request new allocation” button. | #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). [https://wiki.egi.eu/wiki/Resource_Allocation_Request_Metrics_Description metrics] | #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). [https://wiki.egi.eu/wiki/Resource_Allocation_Request_Metrics_Description metrics] | ||
#You may safe your request in draft state (is not beeing processed) and you can edit it later on. | #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”. | #Before sending request you may, by clicking on “Invalidate Request”. |
Revision as of 12:09, 7 April 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
Customer - person signing SLA with Resource Provider
User - person using resources on base of binding SLA (could be Customer itself)
Introduction
The effective usage of IT resources requires from Customers and Resource Provider reaching agreement on how much resources, with some specific requirements will be available to User at specific time period.
In heterogeneous IT environment it is difficult for Customers to find matching resources and for Resource Providers to manage their IT capacity.
The Resource Allocation process, if possible, facilitates reaching agreement between Customers and Resource Providers.
Starting point are:
- set of Resource Pools defined by Resource Providers describing in common metrics resources they are willing to deliver to Users
- set of Customers expectations (Request) describing in common metrics resources they are willing to use
As a result of the process, if the Request was agreed by all parties, there is binding SLA signed, that is basis for resource configuration, allocation usage, support and allocation accounting.
In case there were not matched Requests, the output of the process is report to EGI.eu allowing to manage Pool Capacity (add new resources).
Resource Allocation activities:
- Pool creation - P : Creation of Resource Pool instruction (for Resource Providers)
- User Request creation - C : Creation of Request instruction (for Customers)
- User Request validation - C and B
- OLA creation based on pool matching - B
- OLA (re)negotiation - P and B
- OLA confirmation/rejection - P
- SLA creation/updating - B
- SLA negotiation step - B and C
- SLA confirmation/signing - C
Resource Allocation Procedure (draft)
Request validation (non blocking 3 days, executed in parallel)
Broker checks that Customer has valid x.509 certificate supported by EGI.eu. (e.g. EGI EUGridPMA organization). If not, Broker suggest Customer to obtain certificate.
Broker checks that Customer is member of VO. If not, Broker points Customer to documentation on creation of new Virtual Organization (VO): https://wiki.egi.eu/wiki/PROC14
Broker notifies EGI.eu (support@egi.eu Gergely Sipos). Veto to request(with explanations) should be e-mailed to resource-allocation-support at mailman.egi.eu as soon as possible, no more than 3 days. This description will be sent to Customer.
Request vs resource pool matching (executed in parallel)
Broker matches resources. Broker choose pool according to https://wiki.egi.eu/wiki/Resource_Pool scenario (Free hands, Right to revoke, Negotiated)
SLA/OLA negotiations
Broker checks wheter there was EGI.eu veto announced. If yes, Request is Rejected and Customer notified about reason.
If not, Broker sends to Customer SLA proposal.
Customer and Broker negotiate values of the metrics.
If agreement is reached, Customer signes SLA and the offer is binding for both parties.
Binding OLA configured on site (VO on site, resource allocation)
Resource Provider configures resources according to the binding Request.<span style="background: #ffff00" />
Offer exploitation
User exploits the allocation. In case of problems creates ticket in GGUS assigned to "Resource Allocation" Support Unit. Then ticket may be assigned to related Resource Provider support unit.
Offer review
Customer evaluates the cooperation with EGI.eu
Work Instructions (draft)
1. User Side
Request creation
- Enter e-GRANT, login,
- 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). metrics
- 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.
2. Provider Side
New OLA handling
- RP check (should be notified by email), that new OLA appeared (negotiation scenario)
- RP logs in to e-GRANT tool with GOCBD Admin role.
- In“Requests being processed” panel clicks on SLA Name to be processed.
- RPmay reject, negotiate and accept proposal.
- 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.
3. Broker Side
New request handling
- Broker checks (should be notified by email), that new request appeared.
- Broker logs in to e-GRANT tool with Broker role.
- In “Requests being processed” panel clicks on SLA Name to be processed.
- Broker may reject, find pools or negotiate request.
- 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 clicks on related underpinned OLA, and clicks Send “OLA”. The mail to Resource Provider is sent.
Request negotiation (vs Provider)
- In “Requests being processed” panel clicks on SLA Name to be processed.
- In “Underpinned OLAs” clicks Version link
- Takes appropriate action.
- If Broker agrees, then click on “Accept” and “Home” to get to the list of all Requests.
Contact
mail: resource-allocation-support at mailman.egi.eu
GGUS: "Resource Allocation" support unit (in preparation)