Difference between revisions of "Resource Allocation for Provider"

From EGIWiki
Jump to: navigation, search
Line 3: Line 3:
 
This is page describing activities  of providerduring Resource Allocation process.  
 
This is page describing activities  of providerduring Resource Allocation process.  
  
Provider edits [https://wiki.egi.eu/wiki/Resource_Allocation#Operations_Level_Agreement_.28OLA.29 OLA] document. On the Figure there is schema presenting OLA document flow between parties (P - provider, B - broker) and available states.<br>
+
Provider edits [https://wiki.egi.eu/wiki/Resource_Allocation#Operations_Level_Agreement_.28OLA.29 OLA] document. On the Figure there is schema presenting OLA document flow between parties (P - provider, B - broker) and available states.<br>  
  
 
<br>  
 
<br>  
  
[[Image:EGI-RA-OLA-flow.png|OLA state flow]]
+
[[Image:EGI-RA-OLA-flow.png|OLA state flow]]  
  
 
<br>  
 
<br>  
Line 13: Line 13:
 
=== 1. Pool creation  ===
 
=== 1. Pool creation  ===
  
Opis
 
  
link1 - metryki
 
  
link2 - resource pool  
+
Pool Creation activity is a preparatory step in which Provider declares size and type of resources and time span when they will be available to Resource Allocation process. All the metrics and declared type of pool should be defined.
  
link3 - work instruction
+
''This procedure is valid only for adding new pool to EGI Resource Allocation process.''
 +
 
 +
''The pool record is visible in e-GRANT tool.''
  
 
<br>  
 
<br>  
  
filmik
+
'''Input/conditions:'''
 +
 
 +
*Provider wants to add resources to Resource Allocation process.
 +
 
 +
'''Action:'''
 +
 
 +
*Provider can add resources to Pool description
 +
*Provider can edit pool (modify metrics) in Pool description
 +
*Provider can accept Pool description and make it available to Broker
 +
 
 +
<br>
 +
 
 +
[https://wiki.egi.eu/wiki/Pool_Allocation_For_Providers Work instruction.]
 +
 
 +
[https://wiki.egi.eu/wiki/Resource_Pool#Resource_allocation_policies Pool type.]
 +
 
 +
[https://wiki.egi.eu/wiki/Resource_Pool#Computing:_QoS_levels Quality of Service.]
 +
 
 +
[https://wiki.egi.eu/wiki/Resource_Allocation_Metrics_Description Metrics description.]
 +
 
 +
 
 +
 
 +
Short film [TODO]
  
 
<br>  
 
<br>  
Line 29: Line 51:
 
=== 2. OLA (re)negotiation  ===
 
=== 2. OLA (re)negotiation  ===
  
&lt;style type="text/css"&gt;P { margin-bottom: 0.21cm; color: rgb(0, 0, 0); }P.western { font-family: "Times New Roman",serif; font-size: 12pt; }P.cjk { font-family: "DejaVu Sans","Arial",sans-serif; font-size: 12pt; }P.ctl { font-family: "Times New Roman",serif; font-size: 12pt; }A:link { color: rgb(0, 0, 255); text-decoration: underline; }&lt;/style&gt;
+
 
  
 
''Note: PARTY is the actor who operates the procedure; OTHER PARTY means: P in case B runs the actions, or B in case P runs the actions;''  
 
''Note: PARTY is the actor who operates the procedure; OTHER PARTY means: P in case B runs the actions, or B in case P runs the actions;''  
Line 35: Line 57:
 
'''Input/condition:'''  
 
'''Input/condition:'''  
  
*
+
*OLA are IN-NEGOTIATION and proposal was received from OTHER PARTY
 
 
OLA are IN-NEGOTIATION and proposal was received from OTHER PARTY  
 
  
 
<br> '''Actions:'''  
 
<br> '''Actions:'''  
  
*
+
*PARTY can agree on the proposal; then the OLA is set AGREED
  
PARTY can agree on the proposal; then the OLA is set AGREED
+
*PARTY can reject the proposal; then the OLA is set to CANCELLED
 
+
*PARTY can send a new proposal (offer changes); then the OLA remains in IN-NEGOTIATION, the new proposal is sent to OTHER PARTY
*
 
 
 
PARTY can reject the proposal; then the OLA is set to CANCELLED  
 
 
 
<br> PARTY can send a new proposal (offer changes); then the OLA remains in IN-NEGOTIATION, the new proposal is sent to OTHER PARTY  
 
  
 
<br>  
 
<br>  
Line 63: Line 78:
 
=== 3. OLA confirmation/rejection  ===
 
=== 3. OLA confirmation/rejection  ===
  
&lt;style type="text/css"&gt;P { margin-bottom: 0.21cm; color: rgb(0, 0, 0); }P.western { font-family: "Times New Roman",serif; font-size: 12pt; }P.cjk { font-family: "DejaVu Sans","Arial",sans-serif; font-size: 12pt; }P.ctl { font-family: "Times New Roman",serif; font-size: 12pt; }A:link { color: rgb(0, 0, 255); text-decoration: underline; }&lt;/style&gt;
+
<br>
  
 
''This procedure is valid only for the right-to-revoke scenario.''  
 
''This procedure is valid only for the right-to-revoke scenario.''  
Line 73: Line 88:
 
'''Input/conditions:'''  
 
'''Input/conditions:'''  
  
- OLA is in the state AGREED-REVOKABLE  
+
*OLA is in the state AGREED-REVOKABLE
  
 
'''Action:'''  
 
'''Action:'''  
  
- provider can confirm OLA, which makes OLA AGREED  
+
*Provider can confirm OLA, which makes OLA AGREED  
 
+
*Provider can reject OLA, which makes OLA CANCELLED  
- provider can reject OLA, which makes OLA CANCELLED  
+
*Provider can propose changes to the OLA, which makes OLA IN-NEGOTIATION and proposal is sent to B
 
 
- provider can propose changes to the OLA, which makes OLA IN-NEGOTIATION and proposal is sent to B
 

Revision as of 11:32, 16 April 2014

Provider-related activities

This is page describing activities  of providerduring Resource Allocation process.

Provider edits OLA document. On the Figure there is schema presenting OLA document flow between parties (P - provider, B - broker) and available states.


OLA state flow


1. Pool creation

Pool Creation activity is a preparatory step in which Provider declares size and type of resources and time span when they will be available to Resource Allocation process. All the metrics and declared type of pool should be defined.

This procedure is valid only for adding new pool to EGI Resource Allocation process.

The pool record is visible in e-GRANT tool.


Input/conditions:

  • Provider wants to add resources to Resource Allocation process.

Action:

  • Provider can add resources to Pool description
  • Provider can edit pool (modify metrics) in Pool description
  • Provider can accept Pool description and make it available to Broker


Work instruction.

Pool type.

Quality of Service.

Metrics description.


Short film [TODO]


2. OLA (re)negotiation

Note: PARTY is the actor who operates the procedure; OTHER PARTY means: P in case B runs the actions, or B in case P runs the actions;

Input/condition:

  • OLA are IN-NEGOTIATION and proposal was received from OTHER PARTY


Actions:

  • PARTY can agree on the proposal; then the OLA is set AGREED
  • PARTY can reject the proposal; then the OLA is set to CANCELLED
  • PARTY can send a new proposal (offer changes); then the OLA remains in IN-NEGOTIATION, the new proposal is sent to OTHER PARTY


link do work instr

opis przycisków

filmik


3. OLA confirmation/rejection


This procedure is valid only for the right-to-revoke scenario.

In case of no action, OLA is made AGREED automatically after revoke period.


Input/conditions:

  • OLA is in the state AGREED-REVOKABLE

Action:

  • Provider can confirm OLA, which makes OLA AGREED
  • Provider can reject OLA, which makes OLA CANCELLED
  • Provider can propose changes to the OLA, which makes OLA IN-NEGOTIATION and proposal is sent to B