Latest revision as of 14:27, 15 July 2016

EGI Activity groups

Special Interest groups

Policy groups

Virtual teams

Distributed Competence Centres

EGI Virtual teams:

Main •

Active Projects •

Closed Projects •

Guidelines

Pay-For-Use menu:

Home •

Processes/Instructions •

Service/Price Overview •

Service Management •

Legal/Policy •

Actions •

Meetings •

Further details per step to be provided upon completion of Final Report (19 Dec 2014)

Business Process Overview

Publish Pricing Information

Overview

To test the mechanism for turning your accounting into a monetary charge charging rate needs to be defined. During the pilot the numbers are not legally binding but obviously a ballpark figure would be good as it would give more realistic pilot reports.

To define the charging rate the plan is to use a new feature of GOCDB which is known as 'A Key-Value Pair Property Bag Extensiblity Mechanism'. This allows the definition of arbitrary key-value pairs for a site or any service. If a community agrees a naming scheme for the keys and semantics for the values then they have a flexible and low overhead method of adding more information about anything defined in GOCDB. For anyone interested about more details this is documented https://wiki.egi.eu/wiki/GOCDB/Release4/Development/ExtensibilityMechanism

Instructions

If you do not have access rights to change features of your site please ask the site manager or a site admin to do it for you.

Go to GOCDB https://goc.egi.eu;
Navigate to your site. (My Sites) at the top of the left hand sidebar.
Just above the list of Services you should see a new box called 'Site Extension Properties'
At the bottom of this box there is a big green plus titled 'Add Properties' – click on it
This should show a window with two fields 'Property Name' and 'Property Value'
For 'Property Name' insert the 'Key Name' according to your desired 'Charge Type' (see table below) e.g. P4U_Pilot_Grid_CPU
For 'Property Value' insert a real number which will be interpreted as shown in the Price Calculation column in the table below. e.g. Euros per HEPSPEC06 Hour.
Click the button 'Add Site Property'
If you go back to the site view you will see the 'Key Name' listed. You can edit or delete it.
Then add other properties from the table below as appropriate for your site.

Once you have done this we will query GOCDB to pull the values for the pilot sites and the accounting portal will join them with usage data to produce a charging report.

Charge Types / Properties

Charge Type	Key Name	Pricing
Grid CPU	P4U_Pilot_Grid_CPU	Euros/HEPSPEC06 Hour
Cloud CPU	P4U_Pilot_Cloud_Wall	Euros/Hour
Storage	P4U_Pilot_Storage_Use	Euros/GB*month
Cloud Storage	P4U_Pilot_Storage_Use_Cloud	Euros/GB*month
VAT	P4U_Pilot_VAT	Optional VAT rate to be applied to above

How to handle pay-for-use process for providers (e-GRANT)

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

Benefits for Research Communities:

in a multi-provider EGI environment you have a single point of contact to ask and negotiate resources.

Benefits for Resource Providers:

you will get direct communication with Research Communities and clarity on expectations
it will allow more effectively plan the use of resources

The basic parameters of a RA contact are:

duration
amount of computing and /or storage resources.

The Resource Provider offer is expressed in a form of Resource Pools which are declared by Providers using common <a href="https://wiki.egi.eu/wiki/Resource_Allocation_Metrics_Description" title="Resource Allocation Metrics Description">metrics</a>.

The Research Communities use the same metrics while describing their needs (resource request).

   <ac:structured-macro ac:macro-id="ca8d927c-c6ea-4986-bfa4-df0d951ba6db" ac:name="toc" ac:schema-version="1"/>

Glossary

For basic terms used in Resource Allocation process, please go <a href="https://wiki.egi.eu/wiki/Resource_Allocation_Terminology" title="Resource Allocation Terminology">here</a>

Roles

<a href="https://wiki.egi.eu/wiki/Resource_Allocation_Terminology#Customer" title="Resource Allocation Terminology">Customer</a> - scientist involved in a science project requesting storage or computing resources in EGI, person signing SLA with Resource Provider
<a href="https://wiki.egi.eu/wiki/Resource_Allocation_Terminology#Broker" title="Resource Allocation Terminology">Broker</a> - matchmaker and coordinator of RA process
<a href="https://wiki.egi.eu/wiki/Resource_Allocation_Terminology#Resource_Provider" title="Resource Allocation Terminology">Resource Provider</a> -Site Manager or NGI Manager responsible for resource allocation on sites in their scope

Provider activities

Log in

Click on Login as provider (GOCDB).

==

   <ac:image>
    <ri:attachment ri:filename="P1.png"/>
  </ac:image>

==

Dashboard

After login to e-Grant you are directed to the dashboard. Here you can administrate yours Pools and handle OLAs.

<ac:image ac:height="250"> <ri:attachment ri:filename="P2.png"/> </ac:image>

arranges all OLAs concerning your site(s)

DOCUMENTS REQUIRING ACTION - contains SLAs awaiting for your action (negotiation, approval, rejection)
SLA IN NEGOTIATION - contains SLAs pinned to your pools, but that are on other side (Customer, Broker)
OUTBOX - contains SLA documents being negotiated and awaiting for Broker's action (negotiation, approval, rejection)
AGREED SLAs - documents containing allocations approved by you (Provider), but waiting for Broker verification?
BINDING SLAs - documents with allocation being in place. OLAs change their status automatically from 'Agreed' to 'Binding' after Customers approval of RA Request.
ACTIVE POOLS - list of active pools
INACTIVE POOLS - list of inactive pools
POOLS DRAFTS - list of saved pool drafts
STARRED - contains OLAs requiring special attention - starred by Provider.

Pools

==== Pool creation

  ====

1. Click “Create new pool” button.

<ac:image> <ri:attachment ri:filename="P4.png"/> </ac:image>

2. Edit Pool properties

<ac:image> <ri:attachment ri:filename="P5.png"/> </ac:image>

Basic info

<ac:image ac:height="250"> <ri:attachment ri:filename="P6.png"/> </ac:image>

Start date - date when pool becomes available to Customers
End date - date wen pool will be removed
Site name - name of the site in which resources will be offered
Quality of Service - Resource Provider can offer different types of access to resources according to its local policies and the user requirements:
- Level C1: Opportunistic: Resources are not guaranteed and are subject to local availability.
- Level C2: Time allocation: Resources are available in fair share-like mode for a fixed time period.
- Level C3: Reserved allocation: Resources are exclusively reserved to the VO and the job will be executed immediately after submission.
Description of Pool's local policies - Any relevant information about local polices regarding this Pool

When ready, click on "SAVE POOL" or "SAVE DRAFT FOR POOL" button.

3. Edit pool details (all relevant metrics should be filled in)

According to resources offered by a Site, all metrics describing the resources must be specified.
4 different resource types can be offered (with regards to P4U activity):

HTC Computing
HTC Storage
Cloud Computing
Cloud Storage

To add a resource type choose "Add resources and metrics" button and list of all resource types will drop-out.

<ac:image ac:height="250"> <ri:attachment ri:filename="P7.png"/> </ac:image>

==== General metrics

  ====

Start Date and End Date - when pool will be available for Customers

HTC Computing metric

Metric name <a class="sortheader" href="https://wiki.egi.eu/wiki/Resource_Allocation_for_Provider"> <ac:image> <ri:url ri:value=""/> </ac:image> </a>	Description <a class="sortheader" href="https://wiki.egi.eu/wiki/Resource_Allocation_for_Provider"> <ac:image> <ri:url ri:value=""/> </ac:image> </a>
Max job duration [hours]	Maximum execution time for a single job. After this time, the job can be interrupted by site administrator. Example: For grant with Max Job Duration metric equal to 72h job using four slots will be canceled after 72 real time hours (the number of slots used by the task does NOT affect the task time) The user can expect (require) that a task with a duration of less than defined in this metric will not be interrupted.
Min local storage [GB]	The minimum scratch space used in the calculations for each slot involved in job execution. The User can expect that the amount of scratch space specified in this metric will be the minimum available for each slot allocated for the job. The usage of more scratch space than specified may not be possible.
Min physical memory per core [GB]	The minimum RAM that can take a user application (job) on a single slot. The user can expect that if a job submitted uses no more RAM per slot than declared in the metric, it will be executed.
Opportunistic computing time [HEPSPEC-hours]	Computing time offered on opportunistic basis. Time specified in this metric is a subset of time specified in main metric Total computing time.
Supported middlewares	Middlewares supported in Site
Total computing time [HEPSPEC-hours]	Total computing time offered. This metric is obligatory for computing. By default time offered in this metric is guaranteed. In case metric Opportunistic computing time is specified, the amount of guaranteed time allocated is lowered by the amount of opportunistic time.

HTC Storage metrics

Metric name

       <a class="sortheader" href="https://wiki.egi.eu/wiki/Resource_Allocation_for_Provider">
       
         <ac:image>
           <ri:url ri:value=""/>
         </ac:image>
       
     </a>

Description

       <a class="sortheader" href="https://wiki.egi.eu/wiki/Resource_Allocation_for_Provider">
       
         <ac:image>
           <ri:url ri:value=""/>
         </ac:image>
       
     </a>

Opportunistic storage capacity

[GB]

The target limit of capacity intended to long-term storage of data, on the basis of guarantees.

Total storage capacity

[GB]

By default capacity allocated in this metric is guaranteed. In case metric Opportunistic storage capacity is specified, the amount of guaranteed storage capacity is lowered by the amount of opportunistic capacity.

Cloud Computing metrics

Metric name <a class="sortheader" href="https://wiki.egi.eu/wiki/Resource_Allocation_for_Provider"> <ac:image> <ri:url ri:value=""/> </ac:image> </a>	Description <a class="sortheader" href="https://wiki.egi.eu/wiki/Resource_Allocation_for_Provider"> <ac:image> <ri:url ri:value=""/> </ac:image> </a>
Total number of virtual cores [VC]	Total amount of computing capacity available for allocation measured in <i>virtual cores</i>. EGI virtual core is equal to EC2 virtual core (<a class="external free" href="http://aws.amazon.com/ec2/" rel="nofollow">http://aws.amazon.com/ec2/</a>).
Virtual Machines (maximum) [VM]	Maximum number of each type of resource template that may be hosted within your service. This may take into account the physical characteristics of your facilities.
Small Virtual Machines	- Number of virtual cores < 2 - RAM [GB] < 2 - Scratch/ephemeral storage [GB] < 20
Medium Virtual Machines	- Number of virtual cores < 4 (AND) - RAM [GB] < 4 (AND) - Scratch/ephemeral storage [GB] < 40
Large Virtual Machines	- Number of virtual cores < 8 (AND) - RAM [GB] < 32 (AND) - Scratch/ephemeral storage [GB] < 80
Extra Large Virtual Machines	- Number of virtual cores >= 8 (OR) - RAM [GB] >= 32 (OR) - Scratch/ephemeral storage [GB] >= 80
Allowed level of oversubscription (0% - 50%)	What is the state level of over provisioning that you are utilising in CPU and possibly memory.

Cloud Storage metrics

Metric name

       <a class="sortheader" href="https://wiki.egi.eu/wiki/Resource_Allocation_for_Provider">
       
         <ac:image>
           <ri:url ri:value=""/>
         </ac:image>
       
     </a>

Description

       <a class="sortheader" href="https://wiki.egi.eu/wiki/Resource_Allocation_for_Provider">
       
         <ac:image>
           <ri:url ri:value=""/>
         </ac:image>
       
     </a>

Capacity

[GB]

Total available storage volume made available to the user community, this should also note any over provisioning that is made of storage capability

High availability levels

[yes/no]

Facilities or capabilities to provide high availability quality of service to user communities

Connectivity resilience

[yes/no]

Does the underlying facility have multiple network routes of entry (another form but more specific of high availability).

Editing Pools

At any time Provider can change the Negotiation scenario (default being Free hand to Broker).

Negotiation scenerio - defines the role of EGI Broker EGI Resource Provider in RA Process for a given resource Pool
- Free hand to broker: the broker, responsible of matching demand and offer, is free to allocate the resources from one RP Pool according to local criteria which aim to optimize usage of available resources and user demand. The Resource Provider delegates the responsibility of accepting a proposed resource allocation to the Broker.
- Right to revoke: the broker matches demand and offer and defines a resource allocation proposal. The RP Pool Manager is responsible of accepting or rejecting the resource allocation proposal of the Broker (EGI.eu), in case of no reply to a Broker's proposal after a default time, the resource allocation proposal is considered to be accepted.
- Negotiation: the broker matches demand and offer and defines a resource allocation proposal. The RP Pool Manager is responsible of accepting or rejecting the resource allocation proposal of the Broker (EGI.eu) and to explicitly accept or reject.

Provider may also want to change metric values of the pool. In this case:

1. Click "Edit" button.

<ac:image> <ri:attachment ri:filename="P5.png"/> </ac:image>

2. Change chosen metric values.

<ac:image> <ri:attachment ri:filename="P8.png"/> </ac:image>

   3. Save

==

   OLA (re)negotiation and confirmation/rejection   ==

Provider can negotiate metrics in OLA. (SLA on the pictures)

 <ac:image>
 <ri:attachment ri:filename="Prov12.png"/>
</ac:image>

Provider can choose one of the following actions:

Reject SLA - finishes negotiation with no resources allocated for Customer's SLA (rejection)
Negotiate SLA PROPOSAL - allows Provider to make a counter offer. Provider has 7 days from recieving OLA Proposal to conduct this action.
ALLOCATE RESOURCES - finishes negotiation with resource allocation proposed by Broker (confirmation).

<ac:image> <ri:attachment ri:filename="Prov13.png"/> </ac:image>

In case of NEGOTIATE SLA PROPOSAL Provider can change metric values ans click Save.

<ac:image> <ri:attachment ri:filename="Prov14.png"/> </ac:image>

In case that Provider accepts proposal, after clicking ALLOCATE RESOURCES, proposal is sent to Broker for final verification.

Capacity management

Under construction.

Help and Support

To avoid problems with using e-Grant remember about using HINTS:

Information marks. There is a lot of information marks next to the metrics inbox. When you point with mouse cursor on the mark the hint will show you like on example below:

<ac:image> <ri:attachment ri:filename="p10.png"/> </ac:image>

Contact with us. The staff at EGI.eu will support the applicant at any point of the process, from request creation to accessing the assigned resources. Please send your questions to: <a href="mailto:resource-allocation-support@mailman.egi.eu">resource-allocation-support@mailman.egi.eu</a>

Difference between revisions of "VT EGI Pay-for-Use Processes/Instructions"

Latest revision as of 14:27, 15 July 2016

Contents

Business Process Overview

Publish Pricing Information

Overview

Instructions

Charge Types / Properties

How to handle pay-for-use process for providers (e-GRANT)

Glossary

Roles

Provider activities

Log in

Dashboard

Pools

Basic info

HTC Computing metric

HTC Storage metrics

Cloud Computing metrics

Cloud Storage metrics

Editing Pools

Capacity management

Help and Support

Navigation menu

@@ Line 1: / Line 1: @@
-{{Template:EGI-PayForUse-PoC_menubar}} {{TOC right}}
+{{EGI_Activity_groups_menubar}} {{Menubar_VT}} {{Template:EGI-PayForUse-PoC_menubar}} {{TOC_right}}
-List of selected business cases and overall workplan of agreed activities.
+<br> ''Further details per step to be provided upon completion of Final Report (19 Dec 2014)''
-(To be developed)
+= Business Process Overview  =
-= Business Cases  =
+[[Image:EGI-P4U-Process-Diagram.png]]
-== Roles  ==
+= Publish Pricing Information<br>  =
-*Consumer (User): The person actually using the service (user).
+== Overview  ==
-*Customer: The person or entity that negotiates the level of services and commissions the service provider or broker and may pay, doing so on behalf of a number of consumers (users).
-*Resource Provider: An organisation offering access to ICT resources through service abstractions (e.g., computing power, storage).
-*Broker: An organisation facilitating or arranging transactions and agreements between a customer and one or more resource providers.
-*Technology Provider: A person or entity providing the required technology to support service delivery.
-== User Stories  ==
+To test the mechanism for turning your accounting into a monetary charge charging rate needs to be defined. During the pilot the numbers are not legally binding but obviously a ballpark figure would be good as it would give more realistic pilot reports.
-The below list of potential questions that each role may ask or scenarios will shape User Stories for defining specific developments required. All information is being collected and articulated using a [https://docs.google.com/a/egi.eu/document/d/17d0PijiLmD1ZdqVblMluoTcnFsFehwe4DugOMMfu_5o/edit#heading=h.7z2pn4p7h6dc Google Doc]. Once specific User Stories are defined. The below table will be updated and will feed the required technical developments.
+To define the charging rate the plan is to use a new feature of GOCDB which is known as 'A Key-Value Pair Property Bag Extensiblity Mechanism'. This allows the definition of arbitrary key-value pairs for a site or any service. If a community agrees a naming scheme for the keys and semantics for the values then they have a flexible and low overhead method of adding more information about anything defined in GOCDB. For anyone interested about more details this is documented https://wiki.egi.eu/wiki/GOCDB/Release4/Development/ExtensibilityMechanism
-See [http://en.wikipedia.org/wiki/User_story#Examples wikipedia page]&nbsp;for more information regarding User Stories.<br>
+== Instructions  ==
-=== General  ===
+If you do not have access rights to change features of your site please ask the site manager or a site admin to do it for you.
-Define, at least, the "first level" or "base" service we are going to provide for each class of services.
+#Go to GOCDB https://goc.egi.eu;
+#Navigate to your site. (My Sites) at the top of the left hand sidebar.
+#Just above the list of Services you should see a new box called 'Site Extension Properties'
+#At the bottom of this box there is a big green plus titled 'Add Properties' – click on it
+#This should show a window with two fields 'Property Name' and 'Property Value'
+#For 'Property Name' insert the 'Key Name' according to your desired 'Charge Type' (see table below) e.g. P4U_Pilot_Grid_CPU
+#For 'Property Value' insert a real number which will be interpreted as shown in the Price Calculation column in the table below. e.g. Euros per HEPSPEC06 Hour.
+#Click the button 'Add Site Property'
+#If you go back to the site view you will see the 'Key Name' listed. You can edit or delete it.
+#Then add other properties from the table below as appropriate for your site.
-*Architecture and OS (if not cloud)
+Once you have done this we will query GOCDB to pull the values for the pilot sites and the accounting portal will join them with usage data to produce a charging report.
-*Type of access to the resources
-*Costs (average or a range between providers?)
-*Guaranteed (maximum?) amount of storage space (people have to store their outcomes)
-*Type of support (only related to the resources or it also include support for software? (libraries, compilers, optimizations))
-*Availability (how many (different?)_resources or (different?)_services can I use? Are they subject to availability? See https://documents.egi.eu/secure/RetrieveFile?docid=2032&amp;version=1&amp;filename=List_of_possible_3_QoS_levels_v_3.pdf)
-=== By Roles  ===
+=== Charge Types / Properties  ===
-{| class="wikitable sortable"
+{| class="wikitable"
 |-
-! scope="col" | Role
+! scope="col" | Charge Type
-! scope="col" | Questions for Developing User Stories
+! scope="col" | Key Name
-! scope="col" | Comments
+! scope="col" | Pricing
-! scope="col" | Topic
-! scope="col" | Priority
-! scope="col" | Phase
 |-
-! scope="row" | Consumer
+! scope="row" | Grid CPU
-| I want a list of the available services and their price
+| P4U_Pilot_Grid_CPU
-| As a PoC, list of services that will have a price associated is HIGH
+| Euros/HEPSPEC06 Hour
-| Pricing
-| Low
-| 2nd
 |-
-! scope="row" | Consumer
+! scope="row" | Cloud CPU
-| Who helps me when issues arise&nbsp;? Is this help cost and how much?
+| P4U_Pilot_Cloud_Wall
-| To be agreed, and then defined as part of the SLA
+| Euros/Hour
-| Support / SLA
-| Med
-| 1st
 |-
-! scope="row" | Consumer
+! scope="row" | Storage
-| Where do I get information about your services?
+| P4U_Pilot_Storage_Use
-| This is connected to publishing information, which is low. The AP to be used at the start.
+| Euros/GB*month
-| Service Catalogue
-| Low
-| 2nd
 |-
-! scope="row" | Consumer
+! scope="row" | Cloud Storage
-| How can I access your services? Do you have a portal or something similar?
+| P4U_Pilot_Storage_Use_Cloud
-| AP to be used at the start, more comprehensive tools to be explored.
+| Euros/GB*month
-| Service Access
-| Low
-| 2nd
 |-
-! scope="row" | Consumer
+! scope="row" | VAT
-| What is the price? Is it cheaper than the commercial cloud?
+| P4U_Pilot_VAT
-| Need to have this justification/rational early
+| Optional VAT rate to be applied to above
-| Pricing
+|}
-| High
-| 1st
+<br>
+= How to handle pay-for-use process for providers (e-GRANT)  =
+The&nbsp;'''goal'''&nbsp;of the Resource Allocation (RA) process is to reach an agreement between Research Communities and Resource Provider concerning the parameters and conditions of use of resources.
+<div>Benefits for Research Communities:</div>
+*in a multi-provider EGI environment you have a single point of contact to ask and negotiate resources.
+Benefits for Resource Providers:
+*<div class="O1">you will get direct communication with Research Communities and clarity on expectations</div>
+*it will allow more effectively plan the use of resources
+The basic parameters of a RA contact are:&nbsp;
+*'''duration'''
+*'''amount of computing and /or storage resources'''.
+The Resource Provider offer is expressed in a form of&nbsp;'''Resource Pools'''&nbsp;which are declared by Providers using common&nbsp;&lt;a href="https://wiki.egi.eu/wiki/Resource_Allocation_Metrics_Description" title="Resource Allocation Metrics Description"&gt;metrics&lt;/a&gt;.
+The Research Communities use the same metrics while describing their needs (resource request).
+&nbsp;
+<span class="mw-headline">
+</span>
+    &lt;ac:structured-macro ac:macro-id="ca8d927c-c6ea-4986-bfa4-df0d951ba6db" ac:name="toc" ac:schema-version="1"/&gt;
+== <span class="mw-headline">Glossary </span>  ==
+For basic terms used in Resource Allocation process, please go&nbsp;&lt;a href="https://wiki.egi.eu/wiki/Resource_Allocation_Terminology" title="Resource Allocation Terminology"&gt;here&lt;/a&gt;
+== <span class="mw-headline">Roles </span>  ==
+*&lt;a href="https://wiki.egi.eu/wiki/Resource_Allocation_Terminology#Customer" title="Resource Allocation Terminology"&gt;Customer&lt;/a&gt; - scientist involved in a science project requesting storage or computing resources in EGI, person signing SLA with Resource Provider
+*&lt;a href="https://wiki.egi.eu/wiki/Resource_Allocation_Terminology#Broker" title="Resource Allocation Terminology"&gt;Broker&lt;/a&gt; - matchmaker and coordinator of RA process
+*&lt;a href="https://wiki.egi.eu/wiki/Resource_Allocation_Terminology#Resource_Provider" title="Resource Allocation Terminology"&gt;Resource Provider&lt;/a&gt; -Site Manager or NGI Manager responsible for resource allocation on sites in their scope
+== <span class="mw-headline">Provider activities </span>  ==
+=== <span class="mw-headline">Log in</span>  ===
+<span class="mw-headline">Click on Login as provider (GOCDB).
+</span>
+== <span class="mw-headline">
+</span>
+    &lt;ac:image&gt;
+     &lt;ri:attachment ri:filename="P1.png"/&gt;
+   &lt;/ac:image&gt;
+    ==
+=== <span class="mw-headline">Dashboard </span>  ===
+After login to e-Grant you are directed to the dashboard. Here you can administrate yours Pools and handle OLAs.
+&lt;ac:image ac:height="250"&gt; &lt;ri:attachment ri:filename="P2.png"/&gt; &lt;/ac:image&gt;
+arranges all OLAs concerning your site(s)
+*'''DOCUMENTS REQUIRING ACTION''' - contains SLAs awaiting for your action (negotiation, approval, rejection)
+*'''SLA IN NEGOTIATION - ''' <span style="color: rgb(255,153,0);">contains SLAs pinned to your pools, but that are on other side (Customer, Broker)</span>
+*'''OUTBOX''' - <span style="color: rgb(255,153,0);">contains SLA documents being negotiated and awaiting for Broker's action (negotiation, approval, rejection)</span>
+*'''AGREED SLAs''' - documents containing allocations approved by you (Provider), <span style="color: rgb(255,153,0);">but waiting for Broker verification?</span>
+*'''BINDING SLAs''' - documents with allocation being in place. <span style="color: rgb(255,153,0);">OLAs</span> change their status automatically from 'Agreed' to 'Binding' after Customers approval of RA Request.
+*'''ACTIVE POOLS - ''' <span style="color: rgb(255,153,0);">list of active pools</span>
+*'''INACTIVE POOLS''' - <span style="color: rgb(255,153,0);">list of inactive pools</span>
+*'''POOLS DRAFTS''' - <span style="color: rgb(255,153,0);">list of saved pool drafts</span>
+*'''STARRED''' - contains OLAs requiring special attention - starred by Provider.
+=== <span class="mw-headline">Pools</span>  ===
+==== <span class="mw-headline">Pool creation
+</span>
+   ====
+. Click “Create new pool” button.
+&lt;ac:image&gt; &lt;ri:attachment ri:filename="P4.png"/&gt; &lt;/ac:image&gt;
+. Edit Pool properties
+&lt;ac:image&gt; &lt;ri:attachment ri:filename="P5.png"/&gt; &lt;/ac:image&gt;
+==== Basic info  ====
+&lt;ac:image ac:height="250"&gt; &lt;ri:attachment ri:filename="P6.png"/&gt; &lt;/ac:image&gt;
+*'''Start date''' - date when pool becomes available to Customers
+*'''End date''' - date wen pool will be removed
+*'''Site name''' - name of the site in which resources will be offered
+*'''Quality of Service''' - Resource Provider can offer different types of access to resources according to its local policies and the user requirements: <br>
+**'''Level C1: Opportunistic''': Resources are not guaranteed and are subject to local availability.
+**'''Level C2: Time allocation''': Resources are available in fair share-like mode for a fixed time period.
+**'''Level C3: Reserved allocation''': Resources are exclusively reserved to the VO and the job will be executed immediately after submission.
+*'''Description of Pool's local policies''' - Any relevant information about local polices regarding this Pool
+&nbsp;
+When ready, click on "'''SAVE POOL'''" or "'''SAVE DRAFT FOR POOL'''" button.
+&nbsp;
+. Edit pool details ('''all relevant metrics should be filled in''')
+According to resources offered by a Site, all metrics describing the resources must be specified.<br>4 different resource types can be offered (with regards to P4U activity):
+*HTC Computing
+*HTC Storage
+*Cloud Computing
+*Cloud Storage
+<br>To add a resource type choose "Add resources and metrics" button and list of all resource types will drop-out.
+&lt;ac:image ac:height="250"&gt; &lt;ri:attachment ri:filename="P7.png"/&gt; &lt;/ac:image&gt;
+&nbsp;
+==== <span class="mw-headline">General metrics
+</span>
+   ====
+'''Start Date and End Date '''- when pool will be available for Customers
+=== <span class="mw-headline">HTC Computing metric </span>  ===
+&lt;tbody&gt; &lt;/tbody&gt;
+{|
 |-
-! scope="row" | Consumer
+! <div class="tablesorter-header-inner">Metric name</div>
-| If not, what is the difference with commercial clouds? What are the advantages or using yours?
+        &lt;a class="sortheader" href="https://wiki.egi.eu/wiki/Resource_Allocation_for_Provider"&gt;
-| Need to have this justification/rational early
+        <span class="sortarrow">
-| Value Proposition
+          &lt;ac:image&gt;
-| High
+            &lt;ri:url ri:value="https://wiki.egi.eu/w/skins/common/images/sort_none.gif"/&gt;
-| 1st
+          &lt;/ac:image&gt;
+        </span>
+      &lt;/a&gt;
+! <div class="tablesorter-header-inner">Description</div>
+        &lt;a class="sortheader" href="https://wiki.egi.eu/wiki/Resource_Allocation_for_Provider"&gt;
+        <span class="sortarrow">
+          &lt;ac:image&gt;
+            &lt;ri:url ri:value="https://wiki.egi.eu/w/skins/common/images/sort_none.gif"/&gt;
+          &lt;/ac:image&gt;
+        </span>
+      &lt;/a&gt;
 |-
-! scope="row" | Consumer
+!
-| How can I pay for the services? Credit Card? Bitcoins?
+        '''Max job duration'''
-| Billing aspects/during PoC to start with invoicing/bank transfer; Tokens, credit cards, bitcoins for potential future/production
-| Payment
+'''<span class="mw-headline">[hours] </span> '''
-| Med
-| 1st
+|
+Maximum execution time for a single job. After this time, the job can be interrupted by site administrator.
+Example: For grant with Max Job Duration metric equal to 72h job using four slots will be canceled after 72 real time hours (the number of slots used by the task does NOT affect the task time)
+The user can expect (require) that a task with a duration of less than defined in this metric will not be interrupted.
 |-
-! scope="row" | Consumer
+! colspan="1" |
-| Can I receive a formal invoice with my requirements to put it into my budget?
+'''Min local storage'''
-| Yes. Will be part of AP development and JRA1 tool activity
-| Payment
+'''[<span class="confluence-link">GB</span>]<br> '''
-| Med
-| 1st
+| colspan="1" |
+The minimum scratch space used in the calculations for each slot involved in job execution.<br> The User can expect that the amount of scratch space specified in this metric will be the minimum available for each slot allocated for the job. The usage of more scratch space than specified may not be possible.
 |-
-! scope="row" | Consumer
+! colspan="1" |
-| How can I be sure the price is equal to the quality of resource?
+'''Min physical memory per core'''
-| Add rationale around acceptance of HEPSPEC - fully transparent within the SLA
-| Pricing / Service Quality
+'''[<span class="confluence-link">GB</span>]<br> '''
-| Med
-| 1st
+| colspan="1" | &nbsp;The minimum RAM that can take a user application (job) on a single slot. The user can expect that if a job submitted uses no more RAM per slot than declared in the metric, it will be executed.
 |-
-! scope="row" | Consumer
+!
-| Are any other communities paying for resources?
+'''Opportunistic computing time'''
-| Start an initial list through the PoC, maybe add a survey question
-| Use Cases
+'''<span class="mw-headline">[HEPSPEC-hours] </span> '''
-| High
-| 1st
+| Computing time offered on opportunistic basis. Time specified in this metric is a subset of time specified in main metric ''Total computing time''.
 |-
-! scope="row" | Consumer
+! colspan="1" |
-| Do you have Windows?
+        '''Supported middlewares'''
-| Yes, for the cloud resources; Overall, ambiguous and needs to be specified
-| Technical
+| colspan="1" | &nbsp;Middlewares supported in Site
-| Med
-| 1st
 |-
-! scope="row" | Consumer
+!
-| Do you support products with licensing (like ANSYS, that only allows licenses for a given customer, not shared) even if the license machine is at my site behind a firewall? how?
+'''Total computing time'''
-| To be explored in 2nd phase
-| Licensing
+'''<span class="mw-headline">[HEPSPEC-hours] </span> '''
-| Med
-| 2nd
+| Total computing time offered. This metric is obligatory for computing. By default time offered in this metric is guaranteed. In case metric ''Opportunistic computing time'' is specified, the amount of guaranteed time allocated is lowered by the amount of opportunistic time.
+|}
+=== <span class="mw-headline">HTC Storage metrics </span>  ===
+&lt;tbody&gt; &lt;/tbody&gt;
+{|
 |-
-! scope="row" | Consumer
+! <div class="tablesorter-header-inner">Metric name</div>
-| Can I test for free? (only next 12 months or so)
+        &lt;a class="sortheader" href="https://wiki.egi.eu/wiki/Resource_Allocation_for_Provider"&gt;
-| This will be part of the 2nd phase in designing more comprehensive service packages
+        <span class="sortarrow">
-| Service Package
+          &lt;ac:image&gt;
-| Med
+            &lt;ri:url ri:value="https://wiki.egi.eu/w/skins/common/images/sort_none.gif"/&gt;
-| 2nd
+          &lt;/ac:image&gt;
+        </span>
+      &lt;/a&gt;
+! <div class="tablesorter-header-inner">Description</div>
+        &lt;a class="sortheader" href="https://wiki.egi.eu/wiki/Resource_Allocation_for_Provider"&gt;
+        <span class="sortarrow">
+          &lt;ac:image&gt;
+            &lt;ri:url ri:value="https://wiki.egi.eu/w/skins/common/images/sort_none.gif"/&gt;
+          &lt;/ac:image&gt;
+        </span>
+      &lt;/a&gt;
 |-
-! scope="row" | Consumer
+!
-| Is your firewall open for what I need?
+'''Opportunistic storage capacity'''
-| Part of our technical architecture and description
-| Technical
+'''<span class="mw-headline">[GB] </span> '''
-| Med
-| 1st
+|
+The target limit of capacity intended to long-term storage of data, on the basis of guarantees.
 |-
-! scope="row" | Consumer
+!
-| I can't ftp, do you support dropbox?
+'''Total storage capacity'''
-| More connected to storage, which is in a later phase - for now we are just accounting for current storage sites i.e. DPM and dCache
-| Technical
+'''<span class="mw-headline">[GB] </span> '''
-| Low
-| 2nd
+| By default capacity allocated in this metric is guaranteed. In case metric Opportunistic storage capacity is specified, the amount of guaranteed storage capacity is lowered by the amount of opportunistic capacity.
+|}
+=== C<span class="mw-headline">loud Computing metrics </span>  ===
+&lt;tbody&gt; &lt;/tbody&gt;
+{|
 |-
-! scope="row" | Consumer
+! <div class="tablesorter-header-inner">Metric name</div>
-| Do I need a certificate? who gives it?
+        &lt;a class="sortheader" href="https://wiki.egi.eu/wiki/Resource_Allocation_for_Provider"&gt;
-| For grid services yes, for cloud?
+        <span class="sortarrow">
-| Authentication
+          &lt;ac:image&gt;
-| Med
+            &lt;ri:url ri:value="https://wiki.egi.eu/w/skins/common/images/sort_none.gif"/&gt;
-| 1st
+          &lt;/ac:image&gt;
+        </span>
+      &lt;/a&gt;
+! <div class="tablesorter-header-inner">Description</div>
+        &lt;a class="sortheader" href="https://wiki.egi.eu/wiki/Resource_Allocation_for_Provider"&gt;
+        <span class="sortarrow">
+          &lt;ac:image&gt;
+            &lt;ri:url ri:value="https://wiki.egi.eu/w/skins/common/images/sort_none.gif"/&gt;
+          &lt;/ac:image&gt;
+        </span>
+      &lt;/a&gt;
 |-
-! scope="row" | Consumer
+!
-| Do I get a machine/service for me immediately at any time? will the machine be too busy? is the data transfer too slow? can I use Teamviewer?
+'''Total number of virtual cores'''
-| This will be part of the 2nd phase in designing more comprehensive service packages
-| Service Package / SLA
+'''<span class="mw-headline">[VC] </span> '''
-| Med
-| 2nd
+| Total amount of computing capacity available for allocation measured in &lt;i&gt;virtual cores&lt;/i&gt;. EGI virtual core is equal to EC2 virtual core (&lt;a class="external free" href="http://aws.amazon.com/ec2/" rel="nofollow"&gt;http://aws.amazon.com/ec2/&lt;/a&gt;).
 |-
-! scope="row" | Consumer
+!
-| Is there a Service Level Agreement?
+'''Virtual Machines (maximum)'''
-| Yes, we need to define this now as many other aspects depend on the contents
-| SLA
+'''<span class="mw-headline">[VM] </span> '''
-| High
-| 1st
+| Maximum number of each type of resource template that may be hosted within your service.&nbsp; This may take into account the physical characteristics of your facilities.
 |-
-! scope="row" | Resource Provider
+!
-| I want to set a price for the Grid Compute service on a HEPSPEC-hour (or hour?)
+        '''Small Virtual Machines'''
-| Part of initial core activities
-| Pricing
+|
-| High
+- Number of virtual cores &lt; 2
-| 1st
+- RAM [GB] &lt; 2
+- Scratch/ephemeral storage [GB] &lt; 20
 |-
-! scope="row" | Resource Provider
+! colspan="1" |
-| I want to set a price for the Cloud Compute service based on ....
+'''Medium Virtual Machines'''
-| Part of initial core activities
-| Pricing
+'''<br> '''
-| High
-| 1st
+| colspan="1" |
+- Number of virtual cores&nbsp; &lt; 4 (AND)
+- RAM [GB] &lt; 4 (AND)
+- Scratch/ephemeral storage [GB] &lt; 40
 |-
-! scope="row" | Resource Provider
+! colspan="1" |
-| I want to set a price for the Grid/Cloud Storage service based on GB per month
+        '''Large Virtual Machines'''
-| Instructions are available to do this
-| Pricing
+| colspan="1" |
-| High
+- Number of virtual cores &lt; 8 (AND)
-| 1st
+- RAM [GB] &lt; 32 (AND)
+- Scratch/ephemeral storage [GB] &lt; 80
 |-
-! scope="row" | Resource Provider
+! colspan="1" |
-| How much extra effort &amp; on how many people does this require, and at what level?
+        '''Extra Large Virtual Machines'''
-| This will depend on the desired business model
-| Cost
+| colspan="1" |
-| High
+- Number of virtual cores &gt;= 8 (OR)
-| 2nd
+- RAM [GB] &gt;= 32 (OR)
+- Scratch/ephemeral storage [GB] &gt;= 80
 |-
-! scope="row" | Resource Provider
+! colspan="1" |
-| Can I pay such extra effort to those people?
+'''Allowed level of oversubscription'''
-| This will depend on individual RCs to evaluate available effort and potential return
-| Cost
+(0% - 50%)
-| Med
-| 2nd
+| colspan="1" | What is the state level of over provisioning that you are utilising in CPU and possibly memory.
+|}
+=== <span class="editsection">&nbsp;</span> <span class="mw-headline">Cloud Storage metrics </span>  ===
+&lt;tbody&gt; &lt;/tbody&gt;
+{|
 |-
-! scope="row" | Resource Provider
+! <div class="tablesorter-header-inner">Metric name</div>
-| If I give a contact name, how many mails/calls will she/he receive?
+        &lt;a class="sortheader" href="https://wiki.egi.eu/wiki/Resource_Allocation_for_Provider"&gt;
-| This will be clearly defined in SLAs and OLAs. Current support management to re-used
+        <span class="sortarrow">
-| Support / SLA
+          &lt;ac:image&gt;
-| Med
+            &lt;ri:url ri:value="https://wiki.egi.eu/w/skins/common/images/sort_none.gif"/&gt;
-| 1st
+          &lt;/ac:image&gt;
+        </span>
+      &lt;/a&gt;
+! <div class="tablesorter-header-inner">Description</div>
+        &lt;a class="sortheader" href="https://wiki.egi.eu/wiki/Resource_Allocation_for_Provider"&gt;
+        <span class="sortarrow">
+          &lt;ac:image&gt;
+            &lt;ri:url ri:value="https://wiki.egi.eu/w/skins/common/images/sort_none.gif"/&gt;
+          &lt;/ac:image&gt;
+        </span>
+      &lt;/a&gt;
 |-
-! scope="row" | Resource Provider
+!
-| When do I get the extra funds and under what constraints?
+'''Capacity'''
-| To be defined by the business model and OLA/Contract
-| OLA / Contract
+'''<span class="mw-headline">[GB] </span> '''
-| Low
-| 1st
+| Total available storage volume made available to the user community, this should also note any over provisioning that is made of storage capability
 |-
-! scope="row" | Resource Provider
+!
-| Can I reject potential users that will create more problems than benefits? On what basis?
+'''High availability levels'''
-| Security policies are already available. Any other "restrictions" on usage need to be defined in the SLA or other applicable policies.
-| Security / SLA
+'''<span class="confluence-link">[yes/no</span>] '''
-| Med
-| 2nd
-|-
-! scope="row" | Resource Provider
-| What are the legal issues if the customer is not in my country?
-| To be defined by the legal and policy activities
-| Legal / Policy
-| Med
-| 1st
-|-
-! scope="row" | Resource Provider
-| Will digital certificates be used?
-| To be defined in the technical architecture
-| Authentication
-| High
-| 1st
-|-
-! scope="row" | Resource Provider
-| Do I know these users? (example, bitcoin "researchers") Does it make sense to work with them even if they say they work on research or innovation?
-| Part of the accounting activities
-| Legal / Policy
-| High
-| 1st
-|-
-! scope="row" | Resource Provider
-| Can parts of administration be outsourced? If so, what are the service costs? What are the benefits?
-| This will depend on the business model chosen.
-| Business Model
-| Med
-| 1st
-|-
-! scope="row" | Resource Provider
-| What agreements do I have to make and with whom?
-| To be defined in a dedicated activity.
-| Agreements
-| High
-| 1st
-|-
-! scope="row" | Resource Provider
-| Does VAT apply? If so, when?
-| Taxation also a subject to clarified. Initial report already available
-| Pricing / Legal
-| Low
-| 1st
-|-
-! scope="row" | Resource Provider
-| We are a publicly funded institution, are there any known restrictions for selling services?
-| To be defined by the legal and policy activities
-| Legal / Policy
-| High
-| 1st
-|-
-! scope="row" | Technology Provider
-| What technologies are you lacking that we could offer or develop? Can I develop pay-per-use tools and deploy them? Can I charge for that?
-| Tools will be important, but from an external perspective a later activity
-| Technology / Tools
-| Med
-| 2nd
-|-
-! scope="row" | Technology Provider
-| How do I get paid? who pays me? when?
-| Part of the business model and resulting agreements
-| Payment / Contract
-| Med
-| 2nd
-|-
-! scope="row" | Technology Provider
-| Who is our interface for e.g. agreements/contracts, requirements, improvement, support?
-| Part of the business model and resulting agreements
-| Business Model
-| Med
-| 2nd
-|-
-! scope="row" | Technology Provider
-| Can I deploy a contextualised solution?
-| To be developed as more complex business cases/scenarios are defined
-| Technical
-| Med
-| 2nd
-|-
-! scope="row" | Technology Provider
-| Do you run on Windows?
-| Yes as part of the cloud solution, but this is more covers more areas than the question suggest. To be defined
-| Technical
-| Low
-| 1st
-|-
-! scope="row" | Technology Provider
-| Does it make sense to prepare something for mobile phones?
-| This could be looked at in terms of post-PoC activities/recommendations.
-| Service
-| Low
-| 2nd
-|-
-! scope="row" | Broker
-| What agreements do I have to make and with whom?
-| Part of the business model and resulting agreements
-| Agreements
-| Med
-| 1st
-|-
-! scope="row" | Broker
-| How do I get paid? who pays me? when?
-|
-| Payments
-|
 |
+Facilities or capabilities to provide high availability quality of service to user communities
 |-
-! scope="row" | Broker
+! colspan="1" |
-| Do customers prefer a&nbsp;% and/or flat rate for broker services? Will it depend?
+'''Connectivity resilience'''
-| To be defined as part of the business model activity
-| Business Model
+'''<span class="confluence-link">[yes/no</span>]'''
-| Med
-| 1st
+| colspan="1" | Does the underlying facility have multiple network routes of entry (another form but more specific of high availability).
-|-
-! scope="row" | Broker
-| How is revenue shared in federated service provision? (e.g. GOCDB, Acct Portal)
-| To be defined as part of the business model activity
-| Business Model
-| Low
-| 1st
-|-
-! scope="row" | Multi
-| Do I have to get involved in the communication between provider and user after an agreement/contract is signed? If yes, how do I get a percent or a contract for support?
-| To be defined as part of the business model activity
-| Technical
-| Med
-| 1st
-|-
-! scope="row" | Multi
-| How can I teach this to the users?
-| Support model to be developed.
-| Support
-| Med
-| 2nd
-|-
-! scope="row" | All
-| How can I learn what is this about?
-| This is connected to publishing information, which is low. The AP to be used at the start.
-| Service Description
-| Low
-| 2nd
 |}
-<br>
+=== <span class="mw-headline">Editing Pools </span>  ===
+<span class="mw-headline">At any time Provider can change the Negotiation scenario (default being Free hand to Broker).
+</span>
+*'''Negotiation scenerio -''' defines the role of EGI Broker EGI Resource Provider in RA Process for a given resource Pool<br>
+**'''Free hand to broker''': the broker, responsible of matching demand and offer, is free to allocate the resources from one RP Pool according to local criteria which aim to optimize usage of available resources and user demand. The Resource Provider delegates the responsibility of accepting a proposed resource allocation to the Broker.
+**'''Right to revoke''': the broker matches demand and offer and defines a resource allocation proposal. The RP Pool Manager is responsible of accepting or rejecting the resource allocation proposal of the Broker (EGI.eu), in case of no reply to a Broker's proposal after a default time, the resource allocation proposal is considered to be accepted.
+**'''Negotiation''': the broker matches demand and offer and defines a resource allocation proposal. The RP Pool Manager is responsible of accepting or rejecting the resource allocation proposal of the Broker (EGI.eu) and to '''explicitly''' accept or reject.
+<span class="mw-headline">Provider may also want to change metric values of the pool. In this case:
+</span>
+. Click "Edit" button.
+&lt;ac:image&gt; &lt;ri:attachment ri:filename="P5.png"/&gt; &lt;/ac:image&gt;
+. Change chosen metric values.
+&lt;ac:image&gt; &lt;ri:attachment ri:filename="P8.png"/&gt; &lt;/ac:image&gt;
+<span class="mw-headline">
+</span>
+    <span class="mw-headline">3. Save
+ </span>
+== <span class="mw-headline">
+</span>
+    <span class="mw-headline">OLA (re)negotiation and confirmation/rejection</span>   ==
+&nbsp;
+<div class="message-content">
+'''''Provider can negotiate metrics in OLA. <span style="color: rgb(255,153,0);">(SLA on the pictures)</span> <br> ''' ''
+  &lt;ac:image&gt;
+  &lt;ri:attachment ri:filename="Prov12.png"/&gt;
+ &lt;/ac:image&gt;
+</div> <div class="message-content">
+<br>
-= Workplan Overview  =
+Provider can choose one of the following actions:
-'''January 2014: Kick-off of the activity'''
+*<u>Reject</u> SLA - finishes negotiation with '''no resources allocated for Customer's SLA&nbsp;'''(rejection)
+*<u>Negotiate SLA PROPOSAL</u> - allows Provider to '''make a counter offer'''. Provider has 7 days from recieving OLA Proposal to conduct this action.
+*<u>ALLOCATE RESOURCES</u> - finishes negotiation with '''resource allocation proposed by Broker''' (confirmation).<br> <br>
-*Hold first call - 23 Feb 2014 @ 12:00 CET (TBC)
+&lt;ac:image&gt; &lt;ri:attachment ri:filename="Prov13.png"/&gt; &lt;/ac:image&gt;
-*Establish fixed day and time for semi-monthly calls
-'''April 2014: First phase implementation of all technical specifications, list of required agreements and refinements to policy issues documented in the EGI Sustainability Plan (M48)'''
+&nbsp;
-*Technical
+In case of NEGOTIATE SLA PROPOSAL Provider can change metric values ans click Save.
-**Review [https://wiki.egi.eu/wiki/EGI_Pay-for-Use_PoC_Technical_Details technical detail table] and complete with relevant information
+</div>
-**Associate prices within GOCDB according to instructions provided [https://wiki.egi.eu/wiki/EGI_Pay-for-Use_PoC_Technical_Details#Price_in_Accounting here]
+&lt;ac:image&gt; &lt;ri:attachment ri:filename="Prov14.png"/&gt; &lt;/ac:image&gt;
-**Accounting Portal to make required extraction from GOCDB and accounting for usage
-***Pull the site data and create a table for use in displaying charging. This table should be directly viewable, at least for the pilot.
-***Create test cpu view like the cloud one. Best to base it on the Custom_View so that we can select particular VOs relevant to the pilot.
-**Investigate and implement a billing function (initially a virtual bill)
-**Perform a gap analysis of supporting services (either new or extensions to the current tools) that would enable the increased automation of the process once it has been manually established and subsequent development required for missing functionality.
-**Report back on identified issues and overall progress
-*Policy/Legal
-**Identify and evaluate legal, policy, and organisational issues around the full implementation of the pay-for-use model (review initial information from [https://documents.egi.eu/document/1391 first survey])
-**Articulate appropriate business and responsibility models (review initial [https://documents.egi.eu/public/RetrieveFile?docid=1391&version=4&filename=Policy-PayForUseV2.pdf broker models] developed)
-**Request potential consultation from FedSM regarding service management processes and agreements.
-**Collate information to be presented within Sustainability Plan that is easily digestible (Lead: EGI.eu)
-'''May 2014: Pay-for-Use aspects included in Federated Cloud release (even in Beta/pre-production)'''
+In case that Provider accepts proposal, after clicking ALLOCATE RESOURCES, proposal is sent to Broker for final verification.
-*Identify members involved in the EGI Federated Cloud to serve as pay-for-use representatives
+== <span class="mw-headline">Capacity management</span>  ==
-*Gather requirements from the EGI FedCloud for its inclusion
-'''June 2014: First presentation of activities and feedback from EGI-InSPIRE EC Review'''
+<span style="color: rgb(255,153,0);">Under construction.</span>
-*PoC to decide what information to be presented and ultimate goal
+== <span class="mw-headline">Help and Support </span>  ==
-'''October 2014: Conclusion of phase 2 activities: updates from feedback and overall refinements'''
+To avoid problems with using e-Grant remember about using HINTS:
-*TBD based on activities carried out. Dedicated F2F to be discussed either following EC review or other date TBD (e.g. Sept 2014).
+'''Information marks.''' There is a lot of information marks next to the metrics inbox. When you point with mouse cursor on the mark the hint will show you like on example below:
-'''December 2014: Circulation/Publication of Final Proof of Concept Report'''
+&lt;ac:image&gt; &lt;ri:attachment ri:filename="p10.png"/&gt; &lt;/ac:image&gt;
-*To be included in final EGI-InSPIRE&nbsp;Periodic Report (Lead: EGI.eu with requested contributions from PoC members)
+'''Contact with us.''' The staff at EGI.eu will support the applicant at any point of the process, from request creation to accessing the assigned resources. Please send your questions to: &lt;a href="mailto:resource-allocation-support@mailman.egi.eu"&gt;resource-allocation-support@mailman.egi.eu&lt;/a&gt;<span class="mw-headline">
+</span>
 <br>

Difference between revisions of "VT EGI Pay-for-Use Processes/Instructions"

Latest revision as of 14:27, 15 July 2016

Business Process Overview

Publish Pricing Information

Overview

Instructions

Charge Types / Properties

How to handle pay-for-use process for providers (e-GRANT)

Glossary

Roles

Provider activities

Log in

Dashboard

Pools

Basic info

HTC Computing metric

HTC Storage metrics

Cloud Computing metrics

Cloud Storage metrics

Editing Pools

Capacity management

Help and Support

Navigation menu

Search