Resource Allocation for Provider

From EGIWiki
Revision as of 11:42, 16 April 2014 by Szymocha (talk | contribs)
Jump to: navigation, search

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

  • NGIs/Sites define pools and register them in EGI " Pools of resources repository".
  • Pools definition may be subject of change according to specific Resource alloction policy.
  • NGIs/Sites are free to modify this repository.

[edit] Pool concept

'Definition:Pool is a specific capacity of resources available for EGI allocation according to defined process under defined conditions

Note: Pools covers any scenarios mentioned ever in RATF including “free hand”, “right to revoke”, “negotiation (elastic pool)”

The pool are defined in the Site/NGI declaration:

  • previously referred as pre-agreement, but it should not require EGI to agree/negotiate
  • can be subject of change in time (some limitation apply)


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


Work instruction.

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