Difference between revisions of "Resource Allocation"

From EGIWiki
Jump to: navigation, search
(Operations of Resource Allocation Process)
 
(40 intermediate revisions by 5 users not shown)
Line 1: Line 1:
{{Template:Op menubar}}  
+
{{Template:Op menubar}} {{Template:EGI RA menubar}}<br>  
 
 
{{Template:EGI RA menubar}}<br>  
 
 
 
{| width="100%" style="background: none repeat scroll 0% 0% rgb(255, 255, 255); margin: 1.2em 0px 6px; border: 1px solid rgb(221, 221, 221);"
 
|-
 
| style="width:50%; color:#000;" | <!--            -->
 
{| style="width:260px; border:none; background:none;"
 
|-
 
| style="width:260px; text-align:center; white-space:nowrap; color:#000;" | <div style="font-size:162%; border:none; margin:0; padding:.1em; color:#000;">Welcome to EGI&nbsp;Resource Allocation Page. </div>
 
|}
 
 
 
| style="width:60%; font-size:95%;" | <br>
 
This page is developed for Resource Providers.<br>
 
 
 
It describes Resource Allocation Process supported by [http://e-grant.egi.eu/ e-GRANT] tool.
 
 
 
|}
 
  
 
<br> {{TOC_right}}  
 
<br> {{TOC_right}}  
  
== Introduction to Resource Allocation<br>  ==
+
= '''Introduction to Resource Allocation in EGI'''<br>  =
  
The effective usage of IT&nbsp;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.  
+
The '''goal''' of the Resource Allocation (RA) process is to reach an agreement between Customer and Provider concerning the parameters and conditions of use of resources.<br>
  
In heterogeneous IT environment it is difficult for Customers to find matching resources and for Resource Providers to manage their IT&nbsp;capacity.  
+
The RA process is useful for the Customers (VO representatives, individual users) because in a multi-provider EGI environment they have a single point of contact to ask for a share on resources. RA is also beneficial for Providers (Site Manager, NGI Manager) as it allows more effectively plan the use of resources and closer communication with Customers. <br>
  
The Resource Allocation process, if possible,&nbsp; facilitates reaching agreement between Customers and Resource Providers.  
+
The basic parameters of a RA contact are: '''duration''' and the '''amount of computing and /or storage resources'''.  
  
Starting points are:
+
The EGI offer is expressed in a form of '''Resource Pools''' which are declared by Providers using common [[Resource Allocation Metrics Description|metrics]]. The Customers use the same metrics while describing their needs (resource request).
  
*set of Resource Pools defined by Resource Providers describing in common [[Resource Allocation Metrics Description|metrics]] resources they are willing to deliver to Users
+
<br>
*set of Customers expectations (Request) describing in common [[Resource Allocation Metrics Description|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.
+
= '''Basics'''<br>  =
  
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 this section basic elements of Resource Allocation Process are introduced. Please have a look at the [https://wiki.egi.eu/wiki/Resource_Allocation_Terminology RA terminology] to facilitate further reading.
  
== RA basics<br>  ==
+
== Parties involved<br>  ==
  
In this section the most important elements of Resource Allocation Process can be found. <br>  
+
In RA&nbsp;process there are three parties involved:<br>  
  
=== Terminology  ===
+
*'''Broker (B)''' - matchmaker and coordinator of RA process<br>
 +
*'''Resource Provider (P)''' - Site Manager or NGI Manager responsible for resource allocation on sites in their scope<br>
 +
*'''Customer (C)''' - scientist involved in a science project requesting storage or computing resources in EGI, person signing SLA with Resource Provider<br><br>
  
[https://wiki.egi.eu/wiki/Resource_Allocation_Terminology https://wiki.egi.eu/wiki/Resource_Allocation_Terminology]
+
<br>
  
=== Parties involved<br> ===
+
== Documents ==
  
In RA&nbsp;process there are three parties involved:<br>
+
The RA process operates on the following documents:  
  
*'''Broker (B) '''- coordinator of RA process<br>
+
{| cellspacing="1" cellpadding="1" border="1" width="291"
*'''Resource Provider (P)''' - Site Administrator or NGI manager responsible for resource allocation in involved sites<br>
+
|-
*'''Customer (C) '''– scientist involved in a science project requesting storage or computing resources in EGI, person signing SLA with Resource Provider<br>
+
| '''No.'''  
 +
| '''Document Name'''  
 +
| '''Involved'''
 +
|-
 +
| 1.
 +
| Customer Request
 +
| C
 +
|-
 +
| 2.
 +
| Service Level Agreement
 +
| C, B
 +
|-
 +
| 3.
 +
| SLA Section
 +
| C, B
 +
|-
 +
| 4.
 +
| Operations Level Agreement<br>  
 +
| P, B
 +
|}
  
=== Activities<br> ===
+
<br>  
  
As mentioned Resource Allocation Process main goal is to reach a point at which both engaged sides: Customer and Resource Provider, reach an understanding about resources allocated for Customer and sign SLA.
 
  
There are 9 activities leading to this goal:<br>
 
  
<u>Activities beyond RA&nbsp;Procedure</u>:<br>
+
=== Customer Request  ===
  
#Pool creation - party(-ies) involved: P &nbsp;
+
A document created by Customer describing their resource requirements. In a reply to a Customer Request the Broker creates an SLA containing one or more SLA Sections. There is one SLA Sections for each Resource Pool selected to satisfy a Request.
#User Request creation -&nbsp; party(-ies) involved: C
 
  
<u>Activities directly involved in RA&nbsp;Procedure</u>:<br>
+
=== Service Level Agreement (SLA)  ===
  
#User Request validation - party(-ies) involved: C and B
+
Document created on the basis (in fact it is exact copy) of Customer Request. Parties involved in SLA handling are Broker and Customer. An SLA must contain at least one SLA Section. Each SLA Section is linked to an underpinning OLA. SLA may contain metrics defined on federated level (there are direct obligations of EGI towards the User).
#OLA creation based on pool matching - party(-ies) involved: B
 
#OLA (re)negotiation - party(-ies) involved: P and B
 
#OLA confirmation/rejection - party(-ies)) involved: P
 
#SLA creation/updating &nbsp;- party(-ies) involved: B
 
#SLA negotiation step - party(-ies) involved: B and C
 
#SLA confirmation/signing - party(-ies) involved: C
 
  
All RA&nbsp;connected activities are being conducted in [https://e-grant.egi.eu/slaneg/auth e-GRANT].
+
<u>SLA states:</u>
  
=== Related documents  ===
+
*IN-NEGOTIATION – state indicates that a proposal was sent by one party to another and a negotiation step is expected.
 +
*BINDING-IN-PART – at least one SLA section is binding (also related underpinned OLA must be binding); this state is used in case some of the Site representatives agreed on their OLAs, but negotiations with others are still in progress.
 +
*BINDING – this is terminal state for the SLA; this state indicates that RA process was completed (even in case that the request is not satisfied fully)<br>
 +
*REJECTED – this state indicates that SLA was rejected and is neither binding nor a subject of negotiation.<br>
  
While participating in RA&nbsp;process parties can deal with following documents:
+
=== SLA Section<br>  ===
  
==== Customer Request  ====
+
The document exchanged between Broker and Customer along with SLA. Created as an exact copy of a corresponding OLA, can be modified in the negotiation process. If changed, OLA should be modified accordingly. At the end of negotiations metrics values in SLA Section must be equal to those in OLA. SLA Section cannot be handled separately from SLA.<br>
  
Initial request specified by Customer, describing their resource requirements.
+
<u>SLA Sections states:</u>
  
After Request validation, a reply to this document is an SLA with SLA Sections (underpinning OLAs). It contains all parameters about Customer’s resource allocation request (VO, description of activity, specified metrics etc.)
+
*DRAFT – in this state SLA Sections is visible only to its author
 +
*PROPOSAL – state indicates that a proposal was sent by one party to another and a negotiation step is expected.  
 +
*BINDING – this state indicates that resource allocation must be performed based on details described in the OLA
 +
*REJECTED – this state indicates that OLA was rejected and is neither binding nor a subject of negotiation.<br><br>
  
==== Operations Level Agreement (OLA)  ====
+
=== Operations Level Agreement (OLA)  ===
  
Stand alone document describing a specific Resource Provider allocation associated with user request (SLA).  
+
The document created by the Broker as a result of selecting a Resource Provider to satisfy a given Customer Request. There may be a number of OLAs linked with an SLA. Stand alone document describing a specific Resource Provider allocation associated with some SLA. OLA is created on the basis of SLA parameters and as a result of pool matching. Each created OLA is connected with some specific SLA, but can be handled in parallel with or independently from SLA.  
  
It is created on the basis of SLA parameters and as a result of pool matching. Every created OLA is connected with some specific SLA, but can be handled parallel with or independently from SLA.
+
Parties engaged in OLA negotiation are Broker and Resource Provider (e.g. Site or NGI manager).<br><br>  
 
 
Parties engaged in OLA negotiation are EGI Broker and Resource Provider (e.g. Site or NGI manager).<br>  
 
  
 
<u>OLA states:</u>  
 
<u>OLA states:</u>  
Line 102: Line 100:
 
*AGREED – state indicates that both parties agreed on the OLA, however it is not linked to any binding SLA; OLA in this state can be invalidated only in case the association with underpinned SLA is deleted both based on Broker or User decision).  
 
*AGREED – state indicates that both parties agreed on the OLA, however it is not linked to any binding SLA; OLA in this state can be invalidated only in case the association with underpinned SLA is deleted both based on Broker or User decision).  
 
*BINDING – this state indicates that resource allocation must be performed based on details described in the OLA  
 
*BINDING – this state indicates that resource allocation must be performed based on details described in the OLA  
*REJECTED – this state indicates that OLA was rejected and is neither binding nor a subject of negotiation.
+
*REJECTED – this state indicates that OLA was rejected and is neither binding nor a subject of negotiation.<br>
 
 
==== Service Level Agreement (SLA)  ====
 
  
Document created on the basis (is exact copy) of Users Request after succesful pool matching (at least one OLA must be created/agreed). Parties involved in SLA handling are Broker and Customer. Every SLA contains underpinned OLAs (visible to Broker and Site Representatives) and corresponding to OLAs SLA sections (visible to Broker and Customer).  
+
[[File:EGI-RA-SLA2.png]]
  
SLA must contain at least one SLA section (each section reflects a single underpinned OLA); SLA may contain metrics defined on federated level (there are direct obligations of EGI towards the User).
+
<br>
  
SLA is created as a response to the RA User Request.
+
== Activities<br>  ==
  
<u>SLA states:</u>
+
As mentioned Resource Allocation Process main goal is to reach a point at which Customer and Resource Provider reach an understanding about resources allocated for Customer and sign the SLA.
  
*IN-NEGOTIATION – state indicates that a proposal was sent by one party to another and a negotiation step is expected.
+
There are 9 activities leading to this goal:<br><br>  
*BINDING-IN-PART – at least one SLA section is binding (also related underpinned OLA must be binding); this state is used in case some of the Site representatives agreed on their OLAs, but negotiations with others are still in progress.
 
*BINDING – this is terminal state for the SLA; this state indicates that RA process was completed (even in case that the request is not satisfied fully)<br>  
 
*REJECTED – this state indicates that SLA was rejected and is neither binding nor a subject of negotiation.
 
  
==== SLA Section<br> ====
+
<u>Activities directly involved in RA&nbsp;Procedure</u>:<br><br>  
  
The document corresponding to OLA but exchanged between Broker and Customer along with SLA. Created as an exact copy of appropriate OLA, can be modified in the negotiation process. If changed, OLA should be modified accordingly. At the end of negotiations metrics values in SLA Section must be equal to those in OLA. SLA Section cannot be handled separately from SLA.
+
{| class="wikitable"
 +
|-
 +
! No.
 +
! Activity Name
 +
! Involved
 +
|-
 +
| 1
 +
| User Request validation
 +
| C,B
 +
|-
 +
| 2
 +
| OLA creation based on pool matching
 +
| B
 +
|-
 +
| 3
 +
| OLA (re)negotiation  
 +
| P, B
 +
|-
 +
| 4
 +
| OLA confirmation/rejection
 +
| P
 +
|-
 +
| 5
 +
| SLA creation/updating
 +
| B
 +
|-
 +
| 6
 +
| SLA negotiation step
 +
| B, C
 +
|-
 +
| 7
 +
| SLA confirmation, signing
 +
| C
 +
|}
  
<u>SLA Sections states:</u>  
+
<br> <u>Activities beyond RA&nbsp;Procedure</u>:<br>  
  
*DRAFT – in this state SLA Sections is visible only to its author
+
{| class="wikitable"
*PROPOSAL – state indicates that a proposal was sent by one party to another and a negotiation step is expected.  
+
|-
*BINDING – this state indicates that resource allocation must be performed based on details described in the OLA
+
! No.  
*REJECTED – this state indicates that OLA was rejected and is neither binding nor a subject of negotiation.
+
! Activity Name
 
+
! Involved
=== Example of RA implementation in E-grant  ===
+
|-
 
+
| 1
TBD<br>
+
| Resource Pool creation
 
+
| P
More about Resource allocation Procedure can be found [[Resource Allocation Procedure and Work Instruction|here]].
+
|-
 
+
| 2
== Customer - related activities  ==
+
| User Request creation
 
+
| C
TBD
+
|}
 
 
== Provider - related activities  ==
 
  
[https://wiki.egi.eu/wiki/Resource_Allocation_Provider_Activities]  
+
All activities are being conducted in [https://e-grant.egi.eu/slaneg/auth e-GRANT] tool.<br>
  
== Operations of Resource Allocation Process  ==
+
<br>
  
[[Resource Allocation Operations internals|Internal space for Resource Allocation Operations]]
 
  
[[Resource Allocation|Resource_Allocation]]  
+
More about Resource allocation Procedure can be found [[Resource Allocation Procedure and Work Instruction|here]].<br><br>
  
[[Resource Allocation|&lt;&lt; Go back to Resource Allocation Page]]
 
  
 
[[Category:ResourceAllocation]]
 
[[Category:ResourceAllocation]]

Latest revision as of 15:38, 19 January 2015

Main EGI.eu operations services Support Documentation Tools Activities Performance Technology Catch-all Services Resource Allocation Security


EGI Resource Allocation menu:




Introduction to Resource Allocation in EGI

The goal of the Resource Allocation (RA) process is to reach an agreement between Customer and Provider concerning the parameters and conditions of use of resources.

The RA process is useful for the Customers (VO representatives, individual users) because in a multi-provider EGI environment they have a single point of contact to ask for a share on resources. RA is also beneficial for Providers (Site Manager, NGI Manager) as it allows more effectively plan the use of resources and closer communication with Customers.

The basic parameters of a RA contact are: duration and the amount of computing and /or storage resources.

The EGI offer is expressed in a form of Resource Pools which are declared by Providers using common metrics. The Customers use the same metrics while describing their needs (resource request).


Basics

In this section basic elements of Resource Allocation Process are introduced. Please have a look at the RA terminology to facilitate further reading.

Parties involved

In RA process there are three parties involved:

  • Broker (B) - matchmaker and coordinator of RA process
  • Resource Provider (P) - Site Manager or NGI Manager responsible for resource allocation on sites in their scope
  • Customer (C) - scientist involved in a science project requesting storage or computing resources in EGI, person signing SLA with Resource Provider


Documents

The RA process operates on the following documents:

No. Document Name Involved
1. Customer Request C
2. Service Level Agreement C, B
3. SLA Section C, B
4. Operations Level Agreement
P, B



Customer Request

A document created by Customer describing their resource requirements. In a reply to a Customer Request the Broker creates an SLA containing one or more SLA Sections. There is one SLA Sections for each Resource Pool selected to satisfy a Request.

Service Level Agreement (SLA)

Document created on the basis (in fact it is exact copy) of Customer Request. Parties involved in SLA handling are Broker and Customer. An SLA must contain at least one SLA Section. Each SLA Section is linked to an underpinning OLA. SLA may contain metrics defined on federated level (there are direct obligations of EGI towards the User).

SLA states:

  • IN-NEGOTIATION – state indicates that a proposal was sent by one party to another and a negotiation step is expected.
  • BINDING-IN-PART – at least one SLA section is binding (also related underpinned OLA must be binding); this state is used in case some of the Site representatives agreed on their OLAs, but negotiations with others are still in progress.
  • BINDING – this is terminal state for the SLA; this state indicates that RA process was completed (even in case that the request is not satisfied fully)
  • REJECTED – this state indicates that SLA was rejected and is neither binding nor a subject of negotiation.

SLA Section

The document exchanged between Broker and Customer along with SLA. Created as an exact copy of a corresponding OLA, can be modified in the negotiation process. If changed, OLA should be modified accordingly. At the end of negotiations metrics values in SLA Section must be equal to those in OLA. SLA Section cannot be handled separately from SLA.

SLA Sections states:

  • DRAFT – in this state SLA Sections is visible only to its author
  • PROPOSAL – state indicates that a proposal was sent by one party to another and a negotiation step is expected.
  • BINDING – this state indicates that resource allocation must be performed based on details described in the OLA
  • REJECTED – this state indicates that OLA was rejected and is neither binding nor a subject of negotiation.

Operations Level Agreement (OLA)

The document created by the Broker as a result of selecting a Resource Provider to satisfy a given Customer Request. There may be a number of OLAs linked with an SLA. Stand alone document describing a specific Resource Provider allocation associated with some SLA. OLA is created on the basis of SLA parameters and as a result of pool matching. Each created OLA is connected with some specific SLA, but can be handled in parallel with or independently from SLA.

Parties engaged in OLA negotiation are Broker and Resource Provider (e.g. Site or NGI manager).

OLA states:

  • DRAFT – in this state OLA is visible only to its author
  • INVALIDATED - document (OLA) cancelled by its author before sending to another party
  • PROPOSAL – state indicates that a proposal was sent by one party to another and a negotiation step is expected.
  • AGREED-REVOKABLE – state indicates that OLA was created based on right-to-revoke scenario and it is in a period when it can be revoked.
  • AGREED – state indicates that both parties agreed on the OLA, however it is not linked to any binding SLA; OLA in this state can be invalidated only in case the association with underpinned SLA is deleted both based on Broker or User decision).
  • BINDING – this state indicates that resource allocation must be performed based on details described in the OLA
  • REJECTED – this state indicates that OLA was rejected and is neither binding nor a subject of negotiation.

EGI-RA-SLA2.png


Activities

As mentioned Resource Allocation Process main goal is to reach a point at which Customer and Resource Provider reach an understanding about resources allocated for Customer and sign the SLA.

There are 9 activities leading to this goal:

Activities directly involved in RA Procedure:

No. Activity Name Involved
1 User Request validation C,B
2 OLA creation based on pool matching B
3 OLA (re)negotiation P, B
4 OLA confirmation/rejection P
5 SLA creation/updating B
6 SLA negotiation step B, C
7 SLA confirmation, signing C


Activities beyond RA Procedure:

No. Activity Name Involved
1 Resource Pool creation P
2 User Request creation C

All activities are being conducted in e-GRANT tool.



More about Resource allocation Procedure can be found here.