https://wiki.egi.eu/w/api.php?action=feedcontributions&user=Asimon&feedformat=atom
EGIWiki - User contributions [en]
2024-03-29T14:36:43Z
User contributions
MediaWiki 1.37.1
https://wiki.egi.eu/w/index.php?title=VT_EGI_Pay-for-Use_Technical_Details&diff=66947
VT EGI Pay-for-Use Technical Details
2014-04-29T09:23:58Z
<p>Asimon: </p>
<hr />
<div>{{Template:EGI-PayForUse-PoC_menubar}} {{TOC right}} <br />
<br />
The following table provides an overview of the technical details of the resource and technology providers for the PoC. <br />
<br />
Further below are instructions for adding pricing into the accounting mechanisms. <br />
<br />
= Resource Providers, Services and Prices =<br />
<br />
{| class="wikitable"<br />
|-<br />
! scope="col" | NGI/RC <br />
! scope="col" | GOCDB Name <br />
! scope="col" | Contact <br />
! scope="col" | Service Type <br />
! scope="col" | Services and Resources <br />
! scope="col" | Preferred Payment Direct/Indirect <br />
! scope="col" | Grid Compute Price<br>[HEPSPEC06/hr] <br />
! scope="col" | Cloud Compute Price<br>[TBD] <br />
! scope="col" | Storage Price<br>[€/GB] <br />
! scope="col" | VAT<br>[%]<br />
|-<br />
! scope="row" | Albert Einstein Center, Univ. of Bern <br />
| UNIBE-LHEP <br />
| Sigve Haug <br />
| Batch via CENTOS 5/6 ARC CE <br> <br />
| <br />
*500 cores (approx. 2 months in 2013) on highest priority; <br />
*Consumption preferably in one go, but distributed in time also possible <br />
*10-20 TB disk on local SE for consumption period via DPM SRM interface plus two weeks<br />
<br />
| Both <br />
| €0.03/hr <br />
| <br />
| <br />
Free for PoC Other TBD <br />
<br />
| 8%<br />
|-<br />
! scope="row" | NGI_BG <br />
| BG01-IPP; BG03-NGCC <br />
| Todor Gurov<br>Emanouil Atanassov <br />
| <br />
Batch &amp; Grid: EMI-2/EMI-3 <br> Cloud: OpenStack - FedCloud <br />
<br />
| <br />
*16 NVIDIA Tesla M2090 6 GB + 48 core Intel Xeon E5679 @ 2.53GHz with 4 GB of RAM per core <br />
*576 cores Intel Xeon X5560 @ 2.8GHz with 1.5 GB of RAM per core <br />
*200 cores Intel Xeon E5430 @ 2.66GHz with 2 GB of RAM per core <br />
*MPI jobs <br />
*Non-blocking InfiniBand interconnect <br />
*140 TB of storage provisioned through Lustre FS (/home and /scratch systems), EMI dCache, EMI DPM, OpenStack Swift and OpenStack Cinder<br />
<br />
| Both <br />
| <br />
*€1.00/GPU/hour + VAT (GPU-enabled servers) <br />
*€0.07/core/hour + VAT (CPU only Intel Xeon X5560-based cluster) <br />
*€0.05/core/hour + VAT (CPU only Intel Xeon E5430-based cluster)<br />
<br />
| <br />
| <br />
| 20%<br />
|-<br />
! scope="row" | CESGA-IBERGRID <br />
| CESGA <br />
| Alvaro Simon<br>Ivan Diaz <br />
| Batch + Cloud <br />
| <br />
*720 cores (Batch) AMD Opteron(tm) Processor 6174 2.2Ghz <br />
*240 cores (Cloud) Intel(R) Xeon(R) CPU E5520 2.27GHz <br />
*MPI jobs <br />
*RAM from 1GB to 32GB per core<br />
<br />
| Direct <br />
| <br />
€0.02/core/HEPSPEC06 hour <br />
<br />
| €0.04/core+2GB RAM/hour (+VAT) Example: <br />
*small: 1 core & 2GB €0.04/hour <br />
*medium: 2 cores & 4GB €0.08/hour <br />
*large: 4 cores & 8GB €0.16/hour <br />
| €0.055/GB/month (+VAT) <br />
| 21%<br />
|-<br />
! scope="row" | IFCA-IBERGRID <br />
| IFCA-LCG2 <br />
| Jesus Marco <br />
| Batch (SLURM, SGE) + Cloud <br />
| <br />
*Batch via CREAM CE <br />
*Cloud via OpenStack <br />
*Up to 2500 cores in servers with 4, 8, 16, 40 physical cores <br />
*Infiniband access to other nodes and storage possible for MPI jobs <br />
*RAM from 4GB to 256GB per core (max 1TB)<br />
<br />
| Both, Direct preferred <br />
| <br />
*€0.05/core/hour for usual instances,&nbsp;&lt;0.01/core/HS06 hour (+ VAT) <br />
*€0.04/core/hour for multicore use (&gt;128 cores)<br />
<br />
| <br />
| Minimal storage free, requests up to 100 TB high performance storage possible <br />
| <br />
|-<br />
! scope="row" | Institute of Informatics of the Slovak Academy of Sciences (II SAS) <br />
| IISAS-FedCloud <br />
| <br />
Ladislav Hluchý<br> Viet Tran <br />
<br />
| Cloud (Openstack) <br />
| <br />
*120 cores (Cloud) Intel(R) Xeon(R) CPU E5570 2.93GHz <br />
*1, 2, 4, 8 cores VMs <br />
*RAM up to 4GB per core<br />
<br />
| Both <br />
| not available <br />
| €0.06/core/h +VAT[[]] <br />
| <br />
| 20%<br />
|-<br />
! scope="row" | Latvian Grid <br />
| IMCSUL <br />
| Kaspars Krampis <br />
| Cloud: OpenStack, GRID: ARC + SLURM <br />
| <br />
*CPU: Up to 256 cores, RAM up to 4GB per core<br />
<br />
| TBC <br />
| ~€0.07/core/hr + VAT (TBC) <br />
| <br />
| <br />
| 21%<br />
|-<br />
! scope="row" | MASTER-UP Srl <br />
| UNI-PERUGIA <br />
| <br />
Alessandro Costantini<br>Antonio Lagana <br />
<br />
| EMI1/2, CEs, WNs, SE <br />
| <br />
*EMI1 middleware (phasing to EMI2) - CE's, WN's and SE. <br />
*10 nodes to start (intel 4core, ethernet connection) <br />
*Long experience in Molecular Science and Comp Chem, can provide support for such innovative applications and in the field of R&amp;D for combustion, energy and material science. <br />
*Managing a computer farm of 200 cores and 4TB of storage part of those resources are supporting EGI.<br />
<br />
| Direct <br />
| To be evaluated <br />
| <br />
| <br />
| <br />
|-<br />
! scope="row" | NGI_GRNET <br />
| All HG-* <br />
| Kostas Koumantaros <br />
| Cloud and Grid <br />
| <br />
*TBC<br />
<br />
| TBC <br />
| €0.05/hr + VAT <br />
| <br />
| <br />
| 23%<br />
|-<br />
! scope="row" | NGI-IT <br />
| <br />
INFN-BARI PRISMA-INFN-BARI (cloud) <br />
<br />
INFN-XX <br />
<br />
| Vincenzo Spinoso <br />
| EMI, OpenStack <br />
| <br />
*gLite MW stack: Cream CE, LFC, Storm SE, WMS+LB, BDII. <br />
*Cloud: OpenSTACK<br />
<br />
| TBD <br />
| €0.07/hr + VAT <br />
| €0.05 + VAT <br />
| <br />
| 22%<br />
|-<br />
! scope="row" | 100 Percent IT <br />
| 100IT <br />
| David Blundell <br />
| Cloud (Openstack) <br />
| <br />
*Intel Xeon X5670 @ 2.93GHz <br />
*Cloud via OpenStack<br />
<br />
| Both <br />
| <br />
| €0.07 + VAT <br />
| <br />
| 20%<br />
|-<br />
! scope="row" | PL-Grid <br />
| CYFRONET-LCG2 <br />
| Mariusz Sterzel <br />
| Cloud + Batch via Cream / EMI <br />
| <br />
*Computing power, storage, and human support <br />
*Batch processing via Cream CE/EMI <br />
*Cloud access <br />
*Non-grid, local access to queue system<br />
<br />
| Both <br />
| Capacity and price are a subject to negotiation <br />
| <br />
| <br />
| <br />
|-<br />
! scope="row" | TUBITAK ULAKBIM <br />
| TR-10-ULAKBIM <br />
| Onur Temizsoylu<br>Feyza Eryol <br />
| Cloud + Batch <br />
| <br />
*Batch processing via Cream CE <br />
*VM Management using OpenNebula/OCCI <br />
*Infiniband connected Linux computing resources<br />
<br />
| Both <br />
| €0.15/hour 8 core 24 GB instance <br />
| <br />
| <br />
| <br />
|-<br />
! scope="row" | UIIP NASB <br />
| BY-UIIP <br />
| Serge Salamanka <br />
| Cloud + Batch <br />
| <br />
*Batch processing via UNICORE or Cream CE <br />
*Intel Xeon E5472 (3,0 GHz, 4 Cores) 50 nodes / 100 physical CPUs <br />
*400 virtual CPUs <br />
*400 Gb memory <br />
*8TB Disk storage – 9-12TB Storage servers <br />
*Infiniband DDR 20Gbit/sec]<br />
<br />
| Indirect <br />
| $0.077/hr (TBD) 1 Core <br />
| <br />
| <br />
| <br />
|-<br />
! scope="row" | Fraunhofer SCAI <br />
| SCAI <br />
| Horst Schwichtenberg <br />
| Cloud (Openstack) + Grid (gLite) <br />
| <br />
Cloud: <br />
<br />
*Intel Xeon X5570 @ 2.93GHz <br />
*Non-blocking QDR InfiniBand interconnect (40GBps)<br />
<br />
Grid: <br />
<br />
*AMD Opteron <br />
*DDR Infiniband<br />
<br />
| TBC <br />
| €0.02 <br />
| TBC <br />
| <br />
| <br />
|}<br />
<br />
<br> <br />
<br />
= Price in Accounting<br> =<br />
<br />
== Overview ==<br />
<br />
To test the mechanism for turning your accounting into a monetary charge charging rate needs to be defined. During the pilot this will be one number for your site in euros/HS06 hour. The number does not have to be real but obviously a ballpark figure would be good as it would give more realistic pilot reports. <br />
<br />
To define the charging rate the plan is to use a new feature of GOCDB which is known as ‘[https://wiki.egi.eu/wiki/GOCDB/Release4/Development/ExtensibilityMechanism 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 here]. <br />
<br />
== Instructions ==<br />
<br />
*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.<br />
<br />
#Go to the test GOCDB [https://gocdb-test.esc.rl.ac.uk/v5 https://gocdb-test.esc.rl.ac.uk/v5] which contains a copy of the production database. The same access rights apply but you will not change anything in the production database. <br />
#Navigate to your site. (My Sites) at the top of the left hand sidebar. <br />
#Just above the list of Services you should see a new box called 'Site Extension Properties' <br />
#At the bottom of this box there is a big green plus titled 'Add Properties' – click on it <br />
#This should show a window with two fields 'Property Name' and 'Property Value' <br />
#For 'Property Name' insert TEST_CHARGE <br />
#For 'Property Value' insert a real number which will be interpreted as euros per HEPSPEC06 Hour. <br />
#Click the button 'Add Site Property' <br />
#If you go back to the site view you will see TEST_CHARGE listed. You can edit or delete it.<br />
<br />
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.</div>
Asimon
https://wiki.egi.eu/w/index.php?title=VT_EGI_Pay-for-Use_Technical_Details&diff=66946
VT EGI Pay-for-Use Technical Details
2014-04-29T09:22:41Z
<p>Asimon: </p>
<hr />
<div>{{Template:EGI-PayForUse-PoC_menubar}} {{TOC right}} <br />
<br />
The following table provides an overview of the technical details of the resource and technology providers for the PoC. <br />
<br />
Further below are instructions for adding pricing into the accounting mechanisms. <br />
<br />
= Resource Providers, Services and Prices =<br />
<br />
{| class="wikitable"<br />
|-<br />
! scope="col" | NGI/RC <br />
! scope="col" | GOCDB Name <br />
! scope="col" | Contact <br />
! scope="col" | Service Type <br />
! scope="col" | Services and Resources <br />
! scope="col" | Preferred Payment Direct/Indirect <br />
! scope="col" | Grid Compute Price<br>[HEPSPEC06/hr] <br />
! scope="col" | Cloud Compute Price<br>[TBD] <br />
! scope="col" | Storage Price<br>[€/GB] <br />
! scope="col" | VAT<br>[%]<br />
|-<br />
! scope="row" | Albert Einstein Center, Univ. of Bern <br />
| UNIBE-LHEP <br />
| Sigve Haug <br />
| Batch via CENTOS 5/6 ARC CE <br> <br />
| <br />
*500 cores (approx. 2 months in 2013) on highest priority; <br />
*Consumption preferably in one go, but distributed in time also possible <br />
*10-20 TB disk on local SE for consumption period via DPM SRM interface plus two weeks<br />
<br />
| Both <br />
| €0.03/hr <br />
| <br />
| <br />
Free for PoC Other TBD <br />
<br />
| 8%<br />
|-<br />
! scope="row" | NGI_BG <br />
| BG01-IPP; BG03-NGCC <br />
| Todor Gurov<br>Emanouil Atanassov <br />
| <br />
Batch &amp; Grid: EMI-2/EMI-3 <br> Cloud: OpenStack - FedCloud <br />
<br />
| <br />
*16 NVIDIA Tesla M2090 6 GB + 48 core Intel Xeon E5679 @ 2.53GHz with 4 GB of RAM per core <br />
*576 cores Intel Xeon X5560 @ 2.8GHz with 1.5 GB of RAM per core <br />
*200 cores Intel Xeon E5430 @ 2.66GHz with 2 GB of RAM per core <br />
*MPI jobs <br />
*Non-blocking InfiniBand interconnect <br />
*140 TB of storage provisioned through Lustre FS (/home and /scratch systems), EMI dCache, EMI DPM, OpenStack Swift and OpenStack Cinder<br />
<br />
| Both <br />
| <br />
*€1.00/GPU/hour + VAT (GPU-enabled servers) <br />
*€0.07/core/hour + VAT (CPU only Intel Xeon X5560-based cluster) <br />
*€0.05/core/hour + VAT (CPU only Intel Xeon E5430-based cluster)<br />
<br />
| <br />
| <br />
| 20%<br />
|-<br />
! scope="row" | CESGA-IBERGRID <br />
| CESGA <br />
| Alvaro Simon<br>Ivan Diaz <br />
| Batch + Cloud <br />
| <br />
*720 cores (Batch) AMD Opteron(tm) Processor 6174 2.2Ghz <br />
*240 cores (Cloud) Intel(R) Xeon(R) CPU E5520 2.27GHz <br />
*MPI jobs <br />
*RAM from 1GB to 32GB per core<br />
<br />
| Direct <br />
| <br />
€0.02/core/HEPSPEC06 hour <br />
<br />
| €0.04/core+2GB RAM/hour (+VAT) <br />
Example:<br />
small: 1 core & 2GB €0.04/hour<br />
medium: 2 cores & 4GB €0.08/hour<br />
large: 4 cores & 8GB €0.16/hour<br />
| €0.055/GB/month (+VAT) <br />
| 21%<br />
|-<br />
! scope="row" | IFCA-IBERGRID <br />
| IFCA-LCG2 <br />
| Jesus Marco <br />
| Batch (SLURM, SGE) + Cloud <br />
| <br />
*Batch via CREAM CE <br />
*Cloud via OpenStack <br />
*Up to 2500 cores in servers with 4, 8, 16, 40 physical cores <br />
*Infiniband access to other nodes and storage possible for MPI jobs <br />
*RAM from 4GB to 256GB per core (max 1TB)<br />
<br />
| Both, Direct preferred <br />
| <br />
*€0.05/core/hour for usual instances,&nbsp;&lt;0.01/core/HS06 hour (+ VAT) <br />
*€0.04/core/hour for multicore use (&gt;128 cores)<br />
<br />
| <br />
| Minimal storage free, requests up to 100 TB high performance storage possible <br />
| <br />
|-<br />
! scope="row" | Institute of Informatics of the Slovak Academy of Sciences (II SAS) <br />
| IISAS-FedCloud <br />
| <br />
Ladislav Hluchý<br> Viet Tran <br />
<br />
| Cloud (Openstack) <br />
| <br />
*120 cores (Cloud) Intel(R) Xeon(R) CPU E5570 2.93GHz <br />
*1, 2, 4, 8 cores VMs <br />
*RAM up to 4GB per core<br />
<br />
| Both <br />
| not available <br />
| €0.06/core/h +VAT[[]] <br />
| <br />
| 20%<br />
|-<br />
! scope="row" | Latvian Grid <br />
| IMCSUL <br />
| Kaspars Krampis <br />
| Cloud: OpenStack, GRID: ARC + SLURM <br />
| <br />
*CPU: Up to 256 cores, RAM up to 4GB per core<br />
<br />
| TBC <br />
| ~€0.07/core/hr + VAT (TBC) <br />
| <br />
| <br />
| 21%<br />
|-<br />
! scope="row" | MASTER-UP Srl <br />
| UNI-PERUGIA <br />
| <br />
Alessandro Costantini<br>Antonio Lagana <br />
<br />
| EMI1/2, CEs, WNs, SE <br />
| <br />
*EMI1 middleware (phasing to EMI2) - CE's, WN's and SE. <br />
*10 nodes to start (intel 4core, ethernet connection) <br />
*Long experience in Molecular Science and Comp Chem, can provide support for such innovative applications and in the field of R&amp;D for combustion, energy and material science. <br />
*Managing a computer farm of 200 cores and 4TB of storage part of those resources are supporting EGI.<br />
<br />
| Direct <br />
| To be evaluated <br />
| <br />
| <br />
| <br />
|-<br />
! scope="row" | NGI_GRNET <br />
| All HG-* <br />
| Kostas Koumantaros <br />
| Cloud and Grid <br />
| <br />
*TBC<br />
<br />
| TBC <br />
| €0.05/hr + VAT <br />
| <br />
| <br />
| 23%<br />
|-<br />
! scope="row" | NGI-IT <br />
| <br />
INFN-BARI PRISMA-INFN-BARI (cloud) <br />
<br />
INFN-XX <br />
<br />
| Vincenzo Spinoso <br />
| EMI, OpenStack <br />
| <br />
*gLite MW stack: Cream CE, LFC, Storm SE, WMS+LB, BDII. <br />
*Cloud: OpenSTACK<br />
<br />
| TBD <br />
| €0.07/hr + VAT <br />
| €0.05 + VAT <br />
| <br />
| 22%<br />
|-<br />
! scope="row" | 100 Percent IT <br />
| 100IT <br />
| David Blundell <br />
| Cloud (Openstack) <br />
| <br />
*Intel Xeon X5670 @ 2.93GHz <br />
*Cloud via OpenStack<br />
<br />
| Both <br />
| <br />
| €0.07 + VAT <br />
| <br />
| 20%<br />
|-<br />
! scope="row" | PL-Grid <br />
| CYFRONET-LCG2 <br />
| Mariusz Sterzel <br />
| Cloud + Batch via Cream / EMI <br />
| <br />
*Computing power, storage, and human support <br />
*Batch processing via Cream CE/EMI <br />
*Cloud access <br />
*Non-grid, local access to queue system<br />
<br />
| Both <br />
| Capacity and price are a subject to negotiation <br />
| <br />
| <br />
| <br />
|-<br />
! scope="row" | TUBITAK ULAKBIM <br />
| TR-10-ULAKBIM <br />
| Onur Temizsoylu<br>Feyza Eryol <br />
| Cloud + Batch <br />
| <br />
*Batch processing via Cream CE <br />
*VM Management using OpenNebula/OCCI <br />
*Infiniband connected Linux computing resources<br />
<br />
| Both <br />
| €0.15/hour 8 core 24 GB instance <br />
| <br />
| <br />
| <br />
|-<br />
! scope="row" | UIIP NASB <br />
| BY-UIIP <br />
| Serge Salamanka <br />
| Cloud + Batch <br />
| <br />
*Batch processing via UNICORE or Cream CE <br />
*Intel Xeon E5472 (3,0 GHz, 4 Cores) 50 nodes / 100 physical CPUs <br />
*400 virtual CPUs <br />
*400 Gb memory <br />
*8TB Disk storage – 9-12TB Storage servers <br />
*Infiniband DDR 20Gbit/sec]<br />
<br />
| Indirect <br />
| $0.077/hr (TBD) 1 Core <br />
| <br />
| <br />
| <br />
|-<br />
! scope="row" | Fraunhofer SCAI <br />
| SCAI <br />
| Horst Schwichtenberg <br />
| Cloud (Openstack) + Grid (gLite) <br />
| <br />
Cloud: <br />
<br />
*Intel Xeon X5570 @ 2.93GHz <br />
*Non-blocking QDR InfiniBand interconnect (40GBps)<br />
<br />
Grid: <br />
<br />
*AMD Opteron <br />
*DDR Infiniband<br />
<br />
| TBC <br />
| €0.02 <br />
| TBC <br />
| <br />
| <br />
|}<br />
<br />
<br> <br />
<br />
= Price in Accounting<br> =<br />
<br />
== Overview ==<br />
<br />
To test the mechanism for turning your accounting into a monetary charge charging rate needs to be defined. During the pilot this will be one number for your site in euros/HS06 hour. The number does not have to be real but obviously a ballpark figure would be good as it would give more realistic pilot reports. <br />
<br />
To define the charging rate the plan is to use a new feature of GOCDB which is known as ‘[https://wiki.egi.eu/wiki/GOCDB/Release4/Development/ExtensibilityMechanism 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 here]. <br />
<br />
== Instructions ==<br />
<br />
*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.<br />
<br />
#Go to the test GOCDB [https://gocdb-test.esc.rl.ac.uk/v5 https://gocdb-test.esc.rl.ac.uk/v5] which contains a copy of the production database. The same access rights apply but you will not change anything in the production database. <br />
#Navigate to your site. (My Sites) at the top of the left hand sidebar. <br />
#Just above the list of Services you should see a new box called 'Site Extension Properties' <br />
#At the bottom of this box there is a big green plus titled 'Add Properties' – click on it <br />
#This should show a window with two fields 'Property Name' and 'Property Value' <br />
#For 'Property Name' insert TEST_CHARGE <br />
#For 'Property Value' insert a real number which will be interpreted as euros per HEPSPEC06 Hour. <br />
#Click the button 'Add Site Property' <br />
#If you go back to the site view you will see TEST_CHARGE listed. You can edit or delete it.<br />
<br />
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.</div>
Asimon
https://wiki.egi.eu/w/index.php?title=VT_EGI_Pay-for-Use_Technical_Details&diff=66939
VT EGI Pay-for-Use Technical Details
2014-04-29T08:07:35Z
<p>Asimon: </p>
<hr />
<div>{{Template:EGI-PayForUse-PoC_menubar}} {{TOC right}} <br />
<br />
The following table provides an overview of the technical details of the resource and technology providers for the PoC. <br />
<br />
Further below are instructions for adding pricing into the accounting mechanisms. <br />
<br />
= Resource Providers, Services and Prices =<br />
<br />
{| class="wikitable"<br />
|-<br />
! scope="col" | NGI/RC <br />
! scope="col" | GOCDB Name <br />
! scope="col" | Contact <br />
! scope="col" | Service Type <br />
! scope="col" | Services and Resources <br />
! scope="col" | Preferred Payment Direct/Indirect <br />
! scope="col" | Grid Compute Price<br>[HEPSPEC06/hr] <br />
! scope="col" | Cloud Compute Price<br>[TBD] <br />
! scope="col" | Storage Price<br>[€/GB] <br />
! scope="col" | VAT<br>[%]<br />
|-<br />
! scope="row" | Albert Einstein Center, Univ. of Bern <br />
| UNIBE-LHEP <br />
| Sigve Haug <br />
| Batch via CENTOS 5/6 ARC CE <br> <br />
| <br />
*500 cores (approx. 2 months in 2013) on highest priority; <br />
*Consumption preferably in one go, but distributed in time also possible <br />
*10-20 TB disk on local SE for consumption period via DPM SRM interface plus two weeks<br />
<br />
| Both <br />
| €0.03/hr <br />
| <br />
| <br />
Free for PoC Other TBD <br />
<br />
| 8%<br />
|-<br />
! scope="row" | NGI_BG <br />
| BG01-IPP; BG03-NGCC <br />
| Todor Gurov<br>Emanouil Atanassov <br />
| <br />
Batch &amp; Grid: EMI-2/EMI-3 <br> Cloud: OpenStack - FedCloud <br />
<br />
| <br />
*16 NVIDIA Tesla M2090 6 GB + 48 core Intel Xeon E5679 @ 2.53GHz with 4 GB of RAM per core <br />
*576 cores Intel Xeon X5560 @ 2.8GHz with 1.5 GB of RAM per core <br />
*200 cores Intel Xeon E5430 @ 2.66GHz with 2 GB of RAM per core <br />
*MPI jobs <br />
*Non-blocking InfiniBand interconnect <br />
*140 TB of storage provisioned through Lustre FS (/home and /scratch systems), EMI dCache, EMI DPM, OpenStack Swift and OpenStack Cinder<br />
<br />
| Both <br />
| <br />
*€1.00/GPU/hour + VAT (GPU-enabled servers) <br />
*€0.07/core/hour + VAT (CPU only Intel Xeon X5560-based cluster) <br />
*€0.05/core/hour + VAT (CPU only Intel Xeon E5430-based cluster)<br />
<br />
| <br />
| <br />
| 20%<br />
|-<br />
! scope="row" | CESGA-IBERGRID <br />
| CESGA <br />
| Alvaro Simon<br>Ivan Diaz <br />
| Batch + Cloud <br />
| <br />
*720 cores (Batch) AMD Opteron(tm) Processor 6174 2.2Ghz <br />
*240 cores (Cloud) Intel(R) Xeon(R) CPU E5520 2.27GHz <br />
*MPI jobs <br />
*RAM from 1GB to 32GB per core<br />
<br />
| Direct <br />
| <br />
€0.02/core/HEPSPEC06 hour <br />
<br />
| €0.04/core/hour for 2GB ram (+VAT) <br />
| €0.055/GB/month (+VAT)<br />
| 21%<br />
|-<br />
! scope="row" | IFCA-IBERGRID <br />
| IFCA-LCG2 <br />
| Jesus Marco <br />
| Batch (SLURM, SGE) + Cloud <br />
| <br />
*Batch via CREAM CE <br />
*Cloud via OpenStack <br />
*Up to 2500 cores in servers with 4, 8, 16, 40 physical cores <br />
*Infiniband access to other nodes and storage possible for MPI jobs <br />
*RAM from 4GB to 256GB per core (max 1TB)<br />
<br />
| Both, Direct preferred <br />
| <br />
*€0.05/core/hour for usual instances,&nbsp;&lt;0.01/core/HS06 hour (+ VAT) <br />
*€0.04/core/hour for multicore use (&gt;128 cores)<br />
<br />
| <br />
| Minimal storage free, requests up to 100 TB high performance storage possible <br />
| <br />
|-<br />
! scope="row" | Institute of Informatics of the Slovak Academy of Sciences (II SAS) <br />
| IISAS-FedCloud <br />
| <br />
Ladislav Hluchý<br> Viet Tran <br />
<br />
| Cloud (Openstack) <br />
| <br />
*120 cores (Cloud) Intel(R) Xeon(R) CPU E5570 2.93GHz <br />
*1, 2, 4, 8 cores VMs <br />
*RAM up to 4GB per core<br />
<br />
| Both <br />
| not available <br />
| €0.06/core/h +VAT[[]] <br />
| <br />
| 20%<br />
|-<br />
! scope="row" | Latvian Grid <br />
| IMCSUL <br />
| Kaspars Krampis <br />
| Cloud: OpenStack, GRID: ARC + SLURM <br />
| <br />
*CPU: Up to 256 cores, RAM up to 4GB per core<br />
<br />
| TBC <br />
| ~€0.07/core/hr + VAT (TBC) <br />
| <br />
| <br />
| 21%<br />
|-<br />
! scope="row" | MASTER-UP Srl <br />
| UNI-PERUGIA <br />
| <br />
Alessandro Costantini<br>Antonio Lagana <br />
<br />
| EMI1/2, CEs, WNs, SE <br />
| <br />
*EMI1 middleware (phasing to EMI2) - CE's, WN's and SE. <br />
*10 nodes to start (intel 4core, ethernet connection) <br />
*Long experience in Molecular Science and Comp Chem, can provide support for such innovative applications and in the field of R&amp;D for combustion, energy and material science. <br />
*Managing a computer farm of 200 cores and 4TB of storage part of those resources are supporting EGI.<br />
<br />
| Direct <br />
| To be evaluated <br />
| <br />
| <br />
| <br />
|-<br />
! scope="row" | NGI_GRNET <br />
| All HG-* <br />
| Kostas Koumantaros <br />
| Cloud and Grid <br />
| <br />
*TBC<br />
<br />
| TBC <br />
| €0.05/hr + VAT <br />
| <br />
| <br />
| 23%<br />
|-<br />
! scope="row" | NGI-IT <br />
| <br />
INFN-BARI PRISMA-INFN-BARI (cloud) <br />
<br />
INFN-XX <br />
<br />
| Vincenzo Spinoso <br />
| EMI, OpenStack <br />
| <br />
*gLite MW stack: Cream CE, LFC, Storm SE, WMS+LB, BDII. <br />
*Cloud: OpenSTACK<br />
<br />
| TBD <br />
| €0.07/hr + VAT <br />
| €0.05 + VAT <br />
| <br />
| 22%<br />
|-<br />
! scope="row" | 100 Percent IT <br />
| 100IT <br />
| David Blundell <br />
| Cloud (Openstack) <br />
| <br />
*Intel Xeon X5670 @ 2.93GHz <br />
*Cloud via OpenStack<br />
<br />
| Both <br />
| <br />
| €0.07 + VAT <br />
| <br />
| 20%<br />
|-<br />
! scope="row" | PL-Grid <br />
| CYFRONET-LCG2 <br />
| Mariusz Sterzel <br />
| Cloud + Batch via Cream / EMI <br />
| <br />
*Computing power, storage, and human support <br />
*Batch processing via Cream CE/EMI <br />
*Cloud access <br />
*Non-grid, local access to queue system<br />
<br />
| Both <br />
| Capacity and price are a subject to negotiation <br />
| <br />
| <br />
| <br />
|-<br />
! scope="row" | TUBITAK ULAKBIM <br />
| TR-10-ULAKBIM <br />
| Onur Temizsoylu<br>Feyza Eryol <br />
| Cloud + Batch <br />
| <br />
*Batch processing via Cream CE <br />
*VM Management using OpenNebula/OCCI <br />
*Infiniband connected Linux computing resources<br />
<br />
| Both <br />
| €0.15/hour 8 core 24 GB instance <br />
| <br />
| <br />
| <br />
|-<br />
! scope="row" | UIIP NASB <br />
| BY-UIIP <br />
| Serge Salamanka <br />
| Cloud + Batch <br />
| <br />
*Batch processing via UNICORE or Cream CE <br />
*Intel Xeon E5472 (3,0 GHz, 4 Cores) 50 nodes / 100 physical CPUs <br />
*400 virtual CPUs <br />
*400 Gb memory <br />
*8TB Disk storage – 9-12TB Storage servers <br />
*Infiniband DDR 20Gbit/sec]<br />
<br />
| Indirect <br />
| $0.077/hr (TBD) 1 Core <br />
| <br />
| <br />
| <br />
|-<br />
! scope="row" | Fraunhofer SCAI <br />
| SCAI <br />
| Horst Schwichtenberg <br />
| Cloud (Openstack) + Grid (gLite) <br />
| <br />
Cloud: <br />
<br />
*Intel Xeon X5570 @ 2.93GHz <br />
*Non-blocking QDR InfiniBand interconnect (40GBps)<br />
<br />
Grid: <br />
<br />
*AMD Opteron <br />
*DDR Infiniband<br />
<br />
| TBC <br />
| €0.02 <br />
| TBC <br />
| <br />
| <br />
|}<br />
<br />
<br> <br />
<br />
= Price in Accounting<br> =<br />
<br />
== Overview ==<br />
<br />
To test the mechanism for turning your accounting into a monetary charge charging rate needs to be defined. During the pilot this will be one number for your site in euros/HS06 hour. The number does not have to be real but obviously a ballpark figure would be good as it would give more realistic pilot reports. <br />
<br />
To define the charging rate the plan is to use a new feature of GOCDB which is known as ‘[https://wiki.egi.eu/wiki/GOCDB/Release4/Development/ExtensibilityMechanism 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 here]. <br />
<br />
== Instructions ==<br />
<br />
*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.<br />
<br />
#Go to the test GOCDB [https://gocdb-test.esc.rl.ac.uk/v5 https://gocdb-test.esc.rl.ac.uk/v5] which contains a copy of the production database. The same access rights apply but you will not change anything in the production database. <br />
#Navigate to your site. (My Sites) at the top of the left hand sidebar. <br />
#Just above the list of Services you should see a new box called 'Site Extension Properties' <br />
#At the bottom of this box there is a big green plus titled 'Add Properties' – click on it <br />
#This should show a window with two fields 'Property Name' and 'Property Value' <br />
#For 'Property Name' insert TEST_CHARGE <br />
#For 'Property Value' insert a real number which will be interpreted as euros per HEPSPEC06 Hour. <br />
#Click the button 'Add Site Property' <br />
#If you go back to the site view you will see TEST_CHARGE listed. You can edit or delete it.<br />
<br />
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.</div>
Asimon
https://wiki.egi.eu/w/index.php?title=VT_EGI_Pay-for-Use_Technical_Details&diff=66938
VT EGI Pay-for-Use Technical Details
2014-04-29T08:07:01Z
<p>Asimon: </p>
<hr />
<div>{{Template:EGI-PayForUse-PoC_menubar}} {{TOC right}} <br />
<br />
The following table provides an overview of the technical details of the resource and technology providers for the PoC. <br />
<br />
Further below are instructions for adding pricing into the accounting mechanisms. <br />
<br />
= Resource Providers, Services and Prices =<br />
<br />
{| class="wikitable"<br />
|-<br />
! scope="col" | NGI/RC <br />
! scope="col" | GOCDB Name <br />
! scope="col" | Contact <br />
! scope="col" | Service Type <br />
! scope="col" | Services and Resources <br />
! scope="col" | Preferred Payment Direct/Indirect <br />
! scope="col" | Grid Compute Price<br>[HEPSPEC06/hr] <br />
! scope="col" | Cloud Compute Price<br>[TBD] <br />
! scope="col" | Storage Price<br>[€/GB] <br />
! scope="col" | VAT<br>[%]<br />
|-<br />
! scope="row" | Albert Einstein Center, Univ. of Bern <br />
| UNIBE-LHEP <br />
| Sigve Haug <br />
| Batch via CENTOS 5/6 ARC CE <br> <br />
| <br />
*500 cores (approx. 2 months in 2013) on highest priority; <br />
*Consumption preferably in one go, but distributed in time also possible <br />
*10-20 TB disk on local SE for consumption period via DPM SRM interface plus two weeks<br />
<br />
| Both <br />
| €0.03/hr <br />
| <br />
| <br />
Free for PoC Other TBD <br />
<br />
| 8%<br />
|-<br />
! scope="row" | NGI_BG <br />
| BG01-IPP; BG03-NGCC <br />
| Todor Gurov<br>Emanouil Atanassov <br />
| <br />
Batch &amp; Grid: EMI-2/EMI-3 <br> Cloud: OpenStack - FedCloud <br />
<br />
| <br />
*16 NVIDIA Tesla M2090 6 GB + 48 core Intel Xeon E5679 @ 2.53GHz with 4 GB of RAM per core <br />
*576 cores Intel Xeon X5560 @ 2.8GHz with 1.5 GB of RAM per core <br />
*200 cores Intel Xeon E5430 @ 2.66GHz with 2 GB of RAM per core <br />
*MPI jobs <br />
*Non-blocking InfiniBand interconnect <br />
*140 TB of storage provisioned through Lustre FS (/home and /scratch systems), EMI dCache, EMI DPM, OpenStack Swift and OpenStack Cinder<br />
<br />
| Both <br />
| <br />
*€1.00/GPU/hour + VAT (GPU-enabled servers) <br />
*€0.07/core/hour + VAT (CPU only Intel Xeon X5560-based cluster) <br />
*€0.05/core/hour + VAT (CPU only Intel Xeon E5430-based cluster)<br />
<br />
| <br />
| <br />
| 20%<br />
|-<br />
! scope="row" | CESGA-IBERGRID <br />
| CESGA <br />
| Alvaro Simon<br>Ivan Diaz <br />
| Batch + Cloud <br />
| <br />
*720 cores (Batch) AMD Opteron(tm) Processor 6174 2.2Ghz <br />
*240 cores (Cloud) Intel(R) Xeon(R) CPU E5520 2.27GHz <br />
*MPI jobs <br />
*RAM from 1GB to 32GB per core<br />
<br />
| Direct <br />
| <br />
€0.02/core/HEPSPEC06 hour <br />
<br />
| €0.04/core/hour for 2GB ram (+VAT) <br />
| €0.055/GB/month<br />
| 21%<br />
|-<br />
! scope="row" | IFCA-IBERGRID <br />
| IFCA-LCG2 <br />
| Jesus Marco <br />
| Batch (SLURM, SGE) + Cloud <br />
| <br />
*Batch via CREAM CE <br />
*Cloud via OpenStack <br />
*Up to 2500 cores in servers with 4, 8, 16, 40 physical cores <br />
*Infiniband access to other nodes and storage possible for MPI jobs <br />
*RAM from 4GB to 256GB per core (max 1TB)<br />
<br />
| Both, Direct preferred <br />
| <br />
*€0.05/core/hour for usual instances,&nbsp;&lt;0.01/core/HS06 hour (+ VAT) <br />
*€0.04/core/hour for multicore use (&gt;128 cores)<br />
<br />
| <br />
| Minimal storage free, requests up to 100 TB high performance storage possible <br />
| <br />
|-<br />
! scope="row" | Institute of Informatics of the Slovak Academy of Sciences (II SAS) <br />
| IISAS-FedCloud <br />
| <br />
Ladislav Hluchý<br> Viet Tran <br />
<br />
| Cloud (Openstack) <br />
| <br />
*120 cores (Cloud) Intel(R) Xeon(R) CPU E5570 2.93GHz <br />
*1, 2, 4, 8 cores VMs <br />
*RAM up to 4GB per core<br />
<br />
| Both <br />
| not available <br />
| €0.06/core/h +VAT[[]] <br />
| <br />
| 20%<br />
|-<br />
! scope="row" | Latvian Grid <br />
| IMCSUL <br />
| Kaspars Krampis <br />
| Cloud: OpenStack, GRID: ARC + SLURM <br />
| <br />
*CPU: Up to 256 cores, RAM up to 4GB per core<br />
<br />
| TBC <br />
| ~€0.07/core/hr + VAT (TBC) <br />
| <br />
| <br />
| 21%<br />
|-<br />
! scope="row" | MASTER-UP Srl <br />
| UNI-PERUGIA <br />
| <br />
Alessandro Costantini<br>Antonio Lagana <br />
<br />
| EMI1/2, CEs, WNs, SE <br />
| <br />
*EMI1 middleware (phasing to EMI2) - CE's, WN's and SE. <br />
*10 nodes to start (intel 4core, ethernet connection) <br />
*Long experience in Molecular Science and Comp Chem, can provide support for such innovative applications and in the field of R&amp;D for combustion, energy and material science. <br />
*Managing a computer farm of 200 cores and 4TB of storage part of those resources are supporting EGI.<br />
<br />
| Direct <br />
| To be evaluated <br />
| <br />
| <br />
| <br />
|-<br />
! scope="row" | NGI_GRNET <br />
| All HG-* <br />
| Kostas Koumantaros <br />
| Cloud and Grid <br />
| <br />
*TBC<br />
<br />
| TBC <br />
| €0.05/hr + VAT <br />
| <br />
| <br />
| 23%<br />
|-<br />
! scope="row" | NGI-IT <br />
| <br />
INFN-BARI PRISMA-INFN-BARI (cloud) <br />
<br />
INFN-XX <br />
<br />
| Vincenzo Spinoso <br />
| EMI, OpenStack <br />
| <br />
*gLite MW stack: Cream CE, LFC, Storm SE, WMS+LB, BDII. <br />
*Cloud: OpenSTACK<br />
<br />
| TBD <br />
| €0.07/hr + VAT <br />
| €0.05 + VAT <br />
| <br />
| 22%<br />
|-<br />
! scope="row" | 100 Percent IT <br />
| 100IT <br />
| David Blundell <br />
| Cloud (Openstack) <br />
| <br />
*Intel Xeon X5670 @ 2.93GHz <br />
*Cloud via OpenStack<br />
<br />
| Both <br />
| <br />
| €0.07 + VAT <br />
| <br />
| 20%<br />
|-<br />
! scope="row" | PL-Grid <br />
| CYFRONET-LCG2 <br />
| Mariusz Sterzel <br />
| Cloud + Batch via Cream / EMI <br />
| <br />
*Computing power, storage, and human support <br />
*Batch processing via Cream CE/EMI <br />
*Cloud access <br />
*Non-grid, local access to queue system<br />
<br />
| Both <br />
| Capacity and price are a subject to negotiation <br />
| <br />
| <br />
| <br />
|-<br />
! scope="row" | TUBITAK ULAKBIM <br />
| TR-10-ULAKBIM <br />
| Onur Temizsoylu<br>Feyza Eryol <br />
| Cloud + Batch <br />
| <br />
*Batch processing via Cream CE <br />
*VM Management using OpenNebula/OCCI <br />
*Infiniband connected Linux computing resources<br />
<br />
| Both <br />
| €0.15/hour 8 core 24 GB instance <br />
| <br />
| <br />
| <br />
|-<br />
! scope="row" | UIIP NASB <br />
| BY-UIIP <br />
| Serge Salamanka <br />
| Cloud + Batch <br />
| <br />
*Batch processing via UNICORE or Cream CE <br />
*Intel Xeon E5472 (3,0 GHz, 4 Cores) 50 nodes / 100 physical CPUs <br />
*400 virtual CPUs <br />
*400 Gb memory <br />
*8TB Disk storage – 9-12TB Storage servers <br />
*Infiniband DDR 20Gbit/sec]<br />
<br />
| Indirect <br />
| $0.077/hr (TBD) 1 Core <br />
| <br />
| <br />
| <br />
|-<br />
! scope="row" | Fraunhofer SCAI <br />
| SCAI <br />
| Horst Schwichtenberg <br />
| Cloud (Openstack) + Grid (gLite) <br />
| <br />
Cloud: <br />
<br />
*Intel Xeon X5570 @ 2.93GHz <br />
*Non-blocking QDR InfiniBand interconnect (40GBps)<br />
<br />
Grid: <br />
<br />
*AMD Opteron <br />
*DDR Infiniband<br />
<br />
| TBC <br />
| €0.02 <br />
| TBC <br />
| <br />
| <br />
|}<br />
<br />
<br> <br />
<br />
= Price in Accounting<br> =<br />
<br />
== Overview ==<br />
<br />
To test the mechanism for turning your accounting into a monetary charge charging rate needs to be defined. During the pilot this will be one number for your site in euros/HS06 hour. The number does not have to be real but obviously a ballpark figure would be good as it would give more realistic pilot reports. <br />
<br />
To define the charging rate the plan is to use a new feature of GOCDB which is known as ‘[https://wiki.egi.eu/wiki/GOCDB/Release4/Development/ExtensibilityMechanism 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 here]. <br />
<br />
== Instructions ==<br />
<br />
*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.<br />
<br />
#Go to the test GOCDB [https://gocdb-test.esc.rl.ac.uk/v5 https://gocdb-test.esc.rl.ac.uk/v5] which contains a copy of the production database. The same access rights apply but you will not change anything in the production database. <br />
#Navigate to your site. (My Sites) at the top of the left hand sidebar. <br />
#Just above the list of Services you should see a new box called 'Site Extension Properties' <br />
#At the bottom of this box there is a big green plus titled 'Add Properties' – click on it <br />
#This should show a window with two fields 'Property Name' and 'Property Value' <br />
#For 'Property Name' insert TEST_CHARGE <br />
#For 'Property Value' insert a real number which will be interpreted as euros per HEPSPEC06 Hour. <br />
#Click the button 'Add Site Property' <br />
#If you go back to the site view you will see TEST_CHARGE listed. You can edit or delete it.<br />
<br />
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.</div>
Asimon
https://wiki.egi.eu/w/index.php?title=VT_EGI_Pay-for-Use_Technical_Details&diff=66937
VT EGI Pay-for-Use Technical Details
2014-04-29T08:03:25Z
<p>Asimon: </p>
<hr />
<div>{{Template:EGI-PayForUse-PoC_menubar}} {{TOC right}} <br />
<br />
The following table provides an overview of the technical details of the resource and technology providers for the PoC. <br />
<br />
Further below are instructions for adding pricing into the accounting mechanisms. <br />
<br />
= Resource Providers, Services and Prices =<br />
<br />
{| class="wikitable"<br />
|-<br />
! scope="col" | NGI/RC <br />
! scope="col" | GOCDB Name <br />
! scope="col" | Contact <br />
! scope="col" | Service Type <br />
! scope="col" | Services and Resources <br />
! scope="col" | Preferred Payment Direct/Indirect <br />
! scope="col" | Grid Compute Price<br>[HEPSPEC06/hr] <br />
! scope="col" | Cloud Compute Price<br>[TBD] <br />
! scope="col" | Storage Price<br>[€/GB] <br />
! scope="col" | VAT<br>[%]<br />
|-<br />
! scope="row" | Albert Einstein Center, Univ. of Bern <br />
| UNIBE-LHEP <br />
| Sigve Haug <br />
| Batch via CENTOS 5/6 ARC CE <br> <br />
| <br />
*500 cores (approx. 2 months in 2013) on highest priority; <br />
*Consumption preferably in one go, but distributed in time also possible <br />
*10-20 TB disk on local SE for consumption period via DPM SRM interface plus two weeks<br />
<br />
| Both <br />
| €0.03/hr <br />
| <br />
| <br />
Free for PoC Other TBD <br />
<br />
| 8%<br />
|-<br />
! scope="row" | NGI_BG <br />
| BG01-IPP; BG03-NGCC <br />
| Todor Gurov<br>Emanouil Atanassov <br />
| <br />
Batch &amp; Grid: EMI-2/EMI-3 <br> Cloud: OpenStack - FedCloud <br />
<br />
| <br />
*16 NVIDIA Tesla M2090 6 GB + 48 core Intel Xeon E5679 @ 2.53GHz with 4 GB of RAM per core <br />
*576 cores Intel Xeon X5560 @ 2.8GHz with 1.5 GB of RAM per core <br />
*200 cores Intel Xeon E5430 @ 2.66GHz with 2 GB of RAM per core <br />
*MPI jobs <br />
*Non-blocking InfiniBand interconnect <br />
*140 TB of storage provisioned through Lustre FS (/home and /scratch systems), EMI dCache, EMI DPM, OpenStack Swift and OpenStack Cinder<br />
<br />
| Both <br />
| <br />
*€1.00/GPU/hour + VAT (GPU-enabled servers) <br />
*€0.07/core/hour + VAT (CPU only Intel Xeon X5560-based cluster) <br />
*€0.05/core/hour + VAT (CPU only Intel Xeon E5430-based cluster)<br />
<br />
| <br />
| <br />
| 20%<br />
|-<br />
! scope="row" | CESGA-IBERGRID <br />
| CESGA <br />
| Alvaro Simon<br>Ivan Diaz <br />
| Batch + Cloud <br />
| <br />
*720 cores (Batch) AMD Opteron(tm) Processor 6174 2.2Ghz <br />
*240 cores (Cloud) Intel(R) Xeon(R) CPU E5520 2.27GHz <br />
*MPI jobs <br />
*RAM from 1GB to 32GB per core<br />
<br />
| Direct <br />
| <br />
€0.02/core/HEPSPEC06 hour <br />
<br />
| €0.04/core/hour for 2GB ram (+VAT) <br />
| <br />
| 21%<br />
|-<br />
! scope="row" | IFCA-IBERGRID <br />
| IFCA-LCG2 <br />
| Jesus Marco <br />
| Batch (SLURM, SGE) + Cloud <br />
| <br />
*Batch via CREAM CE <br />
*Cloud via OpenStack <br />
*Up to 2500 cores in servers with 4, 8, 16, 40 physical cores <br />
*Infiniband access to other nodes and storage possible for MPI jobs <br />
*RAM from 4GB to 256GB per core (max 1TB)<br />
<br />
| Both, Direct preferred <br />
| <br />
*€0.05/core/hour for usual instances,&nbsp;&lt;0.01/core/HS06 hour (+ VAT) <br />
*€0.04/core/hour for multicore use (&gt;128 cores)<br />
<br />
| <br />
| Minimal storage free, requests up to 100 TB high performance storage possible <br />
| <br />
|-<br />
! scope="row" | Institute of Informatics of the Slovak Academy of Sciences (II SAS) <br />
| IISAS-FedCloud <br />
| <br />
Ladislav Hluchý<br> Viet Tran <br />
<br />
| Cloud (Openstack) <br />
| <br />
*120 cores (Cloud) Intel(R) Xeon(R) CPU E5570 2.93GHz <br />
*1, 2, 4, 8 cores VMs <br />
*RAM up to 4GB per core<br />
<br />
| Both <br />
| not available <br />
| €0.06/core/h +VAT[[]] <br />
| <br />
| 20%<br />
|-<br />
! scope="row" | Latvian Grid <br />
| IMCSUL <br />
| Kaspars Krampis <br />
| Cloud: OpenStack, GRID: ARC + SLURM <br />
| <br />
*CPU: Up to 256 cores, RAM up to 4GB per core<br />
<br />
| TBC <br />
| ~€0.07/core/hr + VAT (TBC) <br />
| <br />
| <br />
| 21%<br />
|-<br />
! scope="row" | MASTER-UP Srl <br />
| UNI-PERUGIA <br />
| <br />
Alessandro Costantini<br>Antonio Lagana <br />
<br />
| EMI1/2, CEs, WNs, SE <br />
| <br />
*EMI1 middleware (phasing to EMI2) - CE's, WN's and SE. <br />
*10 nodes to start (intel 4core, ethernet connection) <br />
*Long experience in Molecular Science and Comp Chem, can provide support for such innovative applications and in the field of R&amp;D for combustion, energy and material science. <br />
*Managing a computer farm of 200 cores and 4TB of storage part of those resources are supporting EGI.<br />
<br />
| Direct <br />
| To be evaluated <br />
| <br />
| <br />
| <br />
|-<br />
! scope="row" | NGI_GRNET <br />
| All HG-* <br />
| Kostas Koumantaros <br />
| Cloud and Grid <br />
| <br />
*TBC<br />
<br />
| TBC <br />
| €0.05/hr + VAT <br />
| <br />
| <br />
| 23%<br />
|-<br />
! scope="row" | NGI-IT <br />
| <br />
INFN-BARI PRISMA-INFN-BARI (cloud) <br />
<br />
INFN-XX <br />
<br />
| Vincenzo Spinoso <br />
| EMI, OpenStack <br />
| <br />
*gLite MW stack: Cream CE, LFC, Storm SE, WMS+LB, BDII. <br />
*Cloud: OpenSTACK<br />
<br />
| TBD <br />
| €0.07/hr + VAT <br />
| €0.05 + VAT <br />
| <br />
| 22%<br />
|-<br />
! scope="row" | 100 Percent IT <br />
| 100IT <br />
| David Blundell <br />
| Cloud (Openstack) <br />
| <br />
*Intel Xeon X5670 @ 2.93GHz <br />
*Cloud via OpenStack<br />
<br />
| Both <br />
| <br />
| €0.07 + VAT <br />
| <br />
| 20%<br />
|-<br />
! scope="row" | PL-Grid <br />
| CYFRONET-LCG2 <br />
| Mariusz Sterzel <br />
| Cloud + Batch via Cream / EMI <br />
| <br />
*Computing power, storage, and human support <br />
*Batch processing via Cream CE/EMI <br />
*Cloud access <br />
*Non-grid, local access to queue system<br />
<br />
| Both <br />
| Capacity and price are a subject to negotiation <br />
| <br />
| <br />
| <br />
|-<br />
! scope="row" | TUBITAK ULAKBIM <br />
| TR-10-ULAKBIM <br />
| Onur Temizsoylu<br>Feyza Eryol <br />
| Cloud + Batch <br />
| <br />
*Batch processing via Cream CE <br />
*VM Management using OpenNebula/OCCI <br />
*Infiniband connected Linux computing resources<br />
<br />
| Both <br />
| €0.15/hour 8 core 24 GB instance <br />
| <br />
| <br />
| <br />
|-<br />
! scope="row" | UIIP NASB <br />
| BY-UIIP <br />
| Serge Salamanka <br />
| Cloud + Batch <br />
| <br />
*Batch processing via UNICORE or Cream CE <br />
*Intel Xeon E5472 (3,0 GHz, 4 Cores) 50 nodes / 100 physical CPUs <br />
*400 virtual CPUs <br />
*400 Gb memory <br />
*8TB Disk storage – 9-12TB Storage servers <br />
*Infiniband DDR 20Gbit/sec]<br />
<br />
| Indirect <br />
| $0.077/hr (TBD) 1 Core <br />
| <br />
| <br />
| <br />
|-<br />
! scope="row" | Fraunhofer SCAI <br />
| SCAI <br />
| Horst Schwichtenberg <br />
| Cloud (Openstack) + Grid (gLite) <br />
| <br />
Cloud: <br />
<br />
*Intel Xeon X5570 @ 2.93GHz <br />
*Non-blocking QDR InfiniBand interconnect (40GBps)<br />
<br />
Grid: <br />
<br />
*AMD Opteron <br />
*DDR Infiniband<br />
<br />
| TBC <br />
| €0.02 <br />
| TBC <br />
| <br />
| <br />
|}<br />
<br />
<br> <br />
<br />
= Price in Accounting<br> =<br />
<br />
== Overview ==<br />
<br />
To test the mechanism for turning your accounting into a monetary charge charging rate needs to be defined. During the pilot this will be one number for your site in euros/HS06 hour. The number does not have to be real but obviously a ballpark figure would be good as it would give more realistic pilot reports. <br />
<br />
To define the charging rate the plan is to use a new feature of GOCDB which is known as ‘[https://wiki.egi.eu/wiki/GOCDB/Release4/Development/ExtensibilityMechanism 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 here]. <br />
<br />
== Instructions ==<br />
<br />
*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.<br />
<br />
#Go to the test GOCDB [https://gocdb-test.esc.rl.ac.uk/v5 https://gocdb-test.esc.rl.ac.uk/v5] which contains a copy of the production database. The same access rights apply but you will not change anything in the production database. <br />
#Navigate to your site. (My Sites) at the top of the left hand sidebar. <br />
#Just above the list of Services you should see a new box called 'Site Extension Properties' <br />
#At the bottom of this box there is a big green plus titled 'Add Properties' – click on it <br />
#This should show a window with two fields 'Property Name' and 'Property Value' <br />
#For 'Property Name' insert TEST_CHARGE <br />
#For 'Property Value' insert a real number which will be interpreted as euros per HEPSPEC06 Hour. <br />
#Click the button 'Add Site Property' <br />
#If you go back to the site view you will see TEST_CHARGE listed. You can edit or delete it.<br />
<br />
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.</div>
Asimon
https://wiki.egi.eu/w/index.php?title=VT_EGI_Pay-for-Use_Technical_Details&diff=65507
VT EGI Pay-for-Use Technical Details
2014-03-12T07:47:16Z
<p>Asimon: </p>
<hr />
<div>{{Template:EGI-PayForUse-PoC_menubar}} {{TOC right}} <br />
<br />
The following table provides an overview of the technical details of the resource and technology providers for the PoC. <br />
<br />
Further below are instructions for adding pricing into the accounting mechanisms. <br />
<br />
= Resource Providers, Services and Prices =<br />
<br />
{| class="wikitable"<br />
|-<br />
! scope="col" | NGI/RC <br />
! scope="col" | GOCDB Name <br />
! scope="col" | Contact <br />
! scope="col" | Service Type <br />
! scope="col" | Services and Resources <br />
! scope="col" | Preferred Payment Direct/Indirect <br />
! scope="col" | Grid Compute Price<br>[HEPSPEC06/hr] <br />
! scope="col" | Cloud Compute Price<br>[TBD] <br />
! scope="col" | Storage Price<br>[€/GB] <br />
! scope="col" | VAT<br>[%]<br />
|-<br />
! scope="row" | Albert Einstein Center, Univ. of Bern <br />
| UNIBE-LHEP <br />
| Sigve Haug <br />
| Batch via CENTOS 5/6 ARC CE <br> <br />
| <br />
*500 cores (approx. 2 months in 2013) on highest priority; <br />
*Consumption preferably in one go, but distributed in time also possible <br />
*10-20 TB disk on local SE for consumption period via DPM SRM interface plus two weeks<br />
<br />
| Both <br />
| €0.03/hr <br />
| <br />
| <br />
Free for PoC Other TBD <br />
<br />
| 8%<br />
|-<br />
! scope="row" | NGI_BG <br />
| BG01-IPP; BG03-NGCC <br />
| Todor Gurov<br>Emanouil Atanassov <br />
| <br />
Batch &amp; Grid: EMI-2/EMI-3 <br> Cloud: OpenStack - FedCloud <br />
<br />
| <br />
*16 NVIDIA Tesla M2090 6 GB + 48 core Intel Xeon E5679 @ 2.53GHz with 4 GB of RAM per core <br />
*576 cores Intel Xeon X5560 @ 2.8GHz with 1.5 GB of RAM per core <br />
*200 cores Intel Xeon E5430 @ 2.66GHz with 2 GB of RAM per core <br />
*MPI jobs <br />
*Non-blocking InfiniBand interconnect <br />
*140 TB of storage provisioned through Lustre FS (/home and /scratch systems), EMI dCache, EMI DPM, OpenStack Swift and OpenStack Cinder<br />
<br />
| Both <br />
| <br />
*€1.00/GPU/hour + VAT (GPU-enabled servers) <br />
*€0.07/core/hour + VAT (CPU only Intel Xeon X5560-based cluster) <br />
*€0.05/core/hour + VAT (CPU only Intel Xeon E5430-based cluster)<br />
<br />
| <br />
| <br />
| 20%<br />
|-<br />
! scope="row" | CESGA-IBERGRID <br />
| CESGA <br />
| Alvaro Simon<br>Ivan Diaz <br />
| Batch + Cloud <br />
| <br />
*720 cores (Batch) AMD Opteron(tm) Processor 6174 2.2Ghz <br />
*240 cores (Cloud) Intel(R) Xeon(R) CPU E5520 2.27GHz <br />
*MPI jobs <br />
*RAM from 4GB to 32GB per core<br />
<br />
| Direct <br />
| <br />
€0.02/core/HEPSPEC06 hour <br />
<br />
|€0.04/VM hour <br />
| <br />
| <br />
|-<br />
! scope="row" | IFCA-IBERGRID <br />
| IFCA-LCG2 <br />
| Jesus Marco <br />
| Batch (SLURM, SGE) + Cloud <br />
| <br />
*Batch via CREAM CE <br />
*Cloud via OpenStack <br />
*Up to 2500 cores in servers with 4, 8, 16, 40 physical cores <br />
*Infiniband access to other nodes and storage possible for MPI jobs <br />
*RAM from 4GB to 256GB per core (max 1TB)<br />
<br />
| Both, Direct preferred <br />
| <br />
*€0.05/core/hour for usual instances,&nbsp;&lt;0.01/core/HS06 hour (+ VAT) <br />
*€0.04/core/hour for multicore use (&gt;128 cores)<br />
<br />
| <br />
| Minimal storage free, requests up to 100 TB high performance storage possible <br />
| <br />
|-<br />
! scope="row" | Institute of Informatics of the Slovak Academy of Sciences (II SAS) <br />
| IISAS-FedCloud <br />
| <br />
Ladislav Hluchý<br> Viet Tran <br />
<br />
| Cloud (Openstack) <br />
| <br />
*120 cores (Cloud) Intel(R) Xeon(R) CPU E5570 2.93GHz <br />
*1, 2, 4, 8 cores VMs <br />
*RAM up to 4GB per core<br />
<br />
| Both <br />
| €0.06/core/hr <br />
| <br />
| <br />
| <br />
|-<br />
! scope="row" | Latvian Grid <br />
| IMCSUL <br />
| Kaspars Krampis <br />
| Cloud: OpenStack, GRID: ARC + SLURM <br />
| <br />
*CPU: Up to 256 cores, RAM up to 4GB per core<br />
<br />
| TBC <br />
| ~€0.07/core/hr + VAT (TBC) <br />
| <br />
| <br />
| 21%<br />
|-<br />
! scope="row" | MASTER-UP Srl <br />
| TBC <br />
| <br />
Alessandro Costantini<br>Antonio Lagana <br />
<br />
| EMI1/2, CEs, WNs, SE <br />
| <br />
*EMI1 middleware (phasing to EMI2) - CE's, WN's and SE. <br />
*10 nodes to start (intel 4core, ethernet connection) <br />
*Long experience in Molecular Science and Comp Chem, can provide support for such innovative applications and in the field of R&amp;D for combustion, energy and material science. <br />
*Managing a computer farm of 200 cores and 4TB of storage part of those resources are supporting EGI.<br />
<br />
| Direct <br />
| To be evaluated <br />
| <br />
| <br />
| <br />
|-<br />
! scope="row" | NGI_GRNET <br />
| All HG-* <br />
| Kostas Koumantaros <br />
| Cloud and Grid <br />
| <br />
*TBC<br />
<br />
| TBC <br />
| €0.05/hr + VAT <br />
| <br />
| <br />
| 23%<br />
|-<br />
! scope="row" | NGI-IT <br />
| <br />
INFN-BARI PRISMA-INFN-BARI (cloud) <br />
<br />
INFN-XX <br />
<br />
| Vincenzo Spinoso <br />
| EMI, OpenStack <br />
| <br />
*gLite MW stack: Cream CE, LFC, Storm SE, WMS+LB, BDII. <br />
*Cloud: OpenSTACK<br />
<br />
| TBD <br />
| €0.07/hr + VAT <br />
| TBD <br />
| <br />
| 22%<br />
|-<br />
! scope="row" | 100 Percent IT <br />
| 100IT <br />
| David Blundell <br />
| Cloud (Openstack) <br />
| <br />
*Intel Xeon X5670 @ 2.93GHz <br />
*Cloud via OpenStack<br />
<br />
| Both <br />
| <br />
| €0.07 + VAT <br />
| <br />
| 20%<br />
|-<br />
! scope="row" | PL-Grid <br />
| TBC <br />
| Mariusz Sterzel <br />
| Cloud + Batch via Cream / EMI <br />
| <br />
*Computing power, storage, and human support <br />
*Batch processing via Cream CE/EMI <br />
*Cloud access <br />
*Non-grid, local access to queue system<br />
<br />
| Both <br />
| Capacity and price are a subject to negotiation <br />
| <br />
| <br />
| <br />
|-<br />
! scope="row" | TUBITAK ULAKBIM <br />
| TR-10-ULAKBIM <br />
| Onur Temizsoylu<br>Feyza Eryol <br />
| Cloud + Batch <br />
| <br />
*Batch processing via Cream CE <br />
*VM Management using OpenNebula/OCCI <br />
*Infiniband connected Linux computing resources<br />
<br />
| Both <br />
| €0.15/hour 8 core 24 GB instance <br />
| <br />
| <br />
| <br />
|-<br />
! scope="row" | UIIP NASB <br />
| BY-UIIP <br />
| Serge Salamanka <br />
| Cloud + Batch <br />
| <br />
*Batch processing via UNICORE or Cream CE <br />
*Intel Xeon E5472 (3,0 GHz, 4 Cores) 50 nodes / 100 physical CPUs <br />
*400 virtual CPUs <br />
*400 Gb memory <br />
*8TB Disk storage – 9-12TB Storage servers <br />
*Infiniband DDR 20Gbit/sec]<br />
<br />
| Indirect <br />
| $0.077/hr (TBD) 1 Core <br />
| <br />
| <br />
| <br />
|-<br />
! scope="row" | Fraunhofer SCAI <br />
| SCAI <br />
| Horst Schwichtenberg <br />
| Cloud (Openstack) + Grid (gLite) <br />
| <br />
Cloud: <br />
<br />
*Intel Xeon X5570 @ 2.93GHz <br />
*Non-blocking QDR InfiniBand interconnect (40GBps)<br />
<br />
Grid: <br />
<br />
*AMD Opteron <br />
*DDR Infiniband<br />
<br />
| TBC <br />
| €0.02 <br />
| TBC <br />
| <br />
| <br />
|}<br />
<br />
<br> <br />
<br />
= Price in Accounting<br> =<br />
<br />
== Overview ==<br />
<br />
To test the mechanism for turning your accounting into a monetary charge charging rate needs to be defined. During the pilot this will be one number for your site in euros/HS06 hour. The number does not have to be real but obviously a ballpark figure would be good as it would give more realistic pilot reports. <br />
<br />
To define the charging rate the plan is to use a new feature of GOCDB which is known as ‘[https://wiki.egi.eu/wiki/GOCDB/Release4/Development/ExtensibilityMechanism 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 here]. <br />
<br />
== Instructions ==<br />
<br />
*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.<br />
<br />
#Go to the test GOCDB [https://gocdb-test.esc.rl.ac.uk/v5 https://gocdb-test.esc.rl.ac.uk/v5] which contains a copy of the production database. The same access rights apply but you will not change anything in the production database. <br />
#Navigate to your site. (My Sites) at the top of the left hand sidebar. <br />
#Just above the list of Services you should see a new box called 'Site Extension Properties' <br />
#At the bottom of this box there is a big green plus titled 'Add Properties' – click on it <br />
#This should show a window with two fields 'Property Name' and 'Property Value' <br />
#For 'Property Name' insert TEST_CHARGE <br />
#For 'Property Value' insert a real number which will be interpreted as euros per HEPSPEC06 Hour. <br />
#Click the button 'Add Site Property' <br />
#If you go back to the site view you will see TEST_CHARGE listed. You can edit or delete it.<br />
<br />
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.</div>
Asimon
https://wiki.egi.eu/w/index.php?title=Fedcloud-tf:ResourceProviders&diff=65292
Fedcloud-tf:ResourceProviders
2014-03-04T07:28:00Z
<p>Asimon: </p>
<hr />
<div>{{Fedcloud-tf:Menu}} {{TOC_right}} <br />
<br />
== EGI Federated Cloud Resource Providers ==<br />
<br />
EGI Federated Cloud resource providers are institutions and companies that contribute to the FedCloud providing access to their cloud infrastructure via the Federation. Resource providers are free to use any Cloud Manafement Framework (OpenNebula, OpenStack, etc...), the only requirement is that the CMF exposes interfaces compliant to the [[Fedcloud-tf:Technology:Architecture|FedCloud standards]]. <br />
<br />
== Join as a Resource Provider ==<br />
<br />
Every institution and company is invited to join the EGI Federated Cloud. The members of the EGI Federated Cloud have also the opportunity to join the [[Fedcloud-tf:FederatedCloudsTaskForce|EGI Federated Cloud Task Force]], contributing directly to the creation and implementation of the clouds federation. <br />
<br />
If you want to join the EGI Federated Cloud, you can send en email to the [mailto:fedcloud-tf@mailman.egi.eu EGI Federated Cloud Task Force], specifying the following information (fields with * are mandatory) <br />
<br />
*Name* <br />
*Institute* <br />
*Email address* <br />
*One paragraph long description of your organization <br />
*Envisaged timeline (is there a deadline to finish the setup? for how long do you wish to contribute to the EGI Federated project?) <br />
*Estimated number and size of machines that you may provide to EGI <br />
*Type of Cloud Management Framework you are using <br />
*Link to webpage, document or other online resource for further information<br />
<br />
== Current Resource Providers ==<br />
<br />
=== Fully integrated Resource Providers ===<br />
<br />
Reporting period: 1 Jan 2014 - 31 Jan 2014 <br />
<br />
{| width="150%" cellspacing="0" cellpadding="5" style="border:1px solid black; text-align:left;" class="wikitable"<br />
|- style="background:lightgray;"<br />
! style="border-bottom:1px solid black;" | Affiliation <br />
! style="border-bottom:1px solid black;" | CC <br />
! style="border-bottom:1px solid black;" | Main contact <br />
! style="border-bottom:1px solid black;" | Deputies <br />
! style="border-bottom:1px solid black;" | Host Site <br />
! style="border-bottom:1px solid black;" | CMF <br />
! style="border-bottom:1px solid black;" | Certification <br />
! style="border-bottom:1px solid black;" | Resource Endpoints <br />
! style="border-bottom:1px solid black;" | Nagios Avail. (avg.) <br />
! style="border-bottom:1px solid black;" | Comment<br />
|-<br />
| style="border-bottom:1px dotted silver;" | 100 Percent IT Ltd <br />
| style="border-bottom:1px dotted silver;" | UK <br />
| style="border-bottom:1px dotted silver;" | David Blundell <br />
| style="border-bottom:1px dotted silver;" | <br />
| style="border-bottom:1px dotted silver;" | 100IT <br />
| style="border-bottom:1px dotted silver;" | OpenStack <br />
| bgcolor="lime" style="border-bottom:1px dotted silver;" | certified <br />
| style="border-bottom:1px dotted silver;" | OCCI - occi-api.100percentit.com <br />
| bgcolor="#33ff00" style="border-bottom:1px dotted silver;" | 96% <br />
| style="border-bottom:1px dotted silver;" | "(Return code of 127 is out of bounds - plugin may be missing)"<br />
|-<br />
| style="border-bottom:1px dotted silver;" | UNIZAR / BIFI <br />
| style="border-bottom:1px dotted silver;" | ES <br />
| style="border-bottom:1px dotted silver;" | Ruben Valles <br />
| style="border-bottom:1px dotted silver;" | Jaime Ibar Yubero <br />
| style="border-bottom:1px dotted silver;" | BIFI <br />
| style="border-bottom:1px dotted silver;" | OpenStack <br />
| bgcolor="lime" style="border-bottom:1px dotted silver;" | [https://ggus.eu/ws/ticket_info.php?ticket=100239 certified] <br />
| style="border-bottom:1px dotted silver;" | OCCI - server4-epsh.unizar.es <br />
| style="border-bottom:1px dotted silver;" | 11% <br />
| style="border-bottom:1px dotted silver;" | Service 95% plus available/stable since 26 January.<br />
|-<br />
| style="border-bottom:1px dotted silver;" | BSC <br />
| style="border-bottom:1px dotted silver;" | ES <br />
| style="border-bottom:1px dotted silver;" | Daniele Lezzi <br />
| style="border-bottom:1px dotted silver;" | Roger Rafanell <br />
| style="border-bottom:1px dotted silver;" | BSC-Cloud <br />
| style="border-bottom:1px dotted silver;" | Emotive <br />
| style="border-bottom:1px dotted silver;" | <br />
| style="border-bottom:1px dotted silver;" | CDMI - bscgrid05.bsc.es <br />
| bgcolor="lime" style="border-bottom:1px dotted silver;" | 100% <br />
| style="border-bottom:1px dotted silver;" | CDMI-TCP ping probe only<br />
|-<br />
| style="border-bottom:1px dotted silver;" | FCTSG <br />
| style="border-bottom:1px dotted silver;" | ES <br />
| style="border-bottom:1px dotted silver;" | Alvaro Simon <br />
| style="border-bottom:1px dotted silver;" | Ivan Diaz Alvarez <br />
| style="border-bottom:1px dotted silver;" | CESGA <br />
| style="border-bottom:1px dotted silver;" | OpenNebula <br />
| bgcolor="lime" style="border-bottom:1px dotted silver;" | [https://ggus.eu/ws/ticket_info.php?ticket=100948 certified] <br />
| style="border-bottom:1px dotted silver;" | OCCI - cloud.cesga.es <br />
| bgcolor="yellow" style="border-bottom:1px dotted silver;" | 81% <br />
| style="border-bottom:1px dotted silver;" | Spotty service around 7,8,9 January, outage 23-27 January<br />
|-<br />
| style="border-bottom:1px dotted silver;" rowspan="2" | CESNET <br />
| style="border-bottom:1px dotted silver;" rowspan="2" | CZ <br />
| style="border-bottom:1px dotted silver;" rowspan="2" | Miroslav Ruda <br />
| style="border-bottom:1px dotted silver;" rowspan="2" | Boris Parak <br />
| style="border-bottom:1px dotted silver;" rowspan="2" | CESNET-MetaCloud <br />
| style="border-bottom:1px dotted silver;" rowspan="2" | OpenNebula <br />
| bgcolor="lime" style="border-bottom:1px dotted silver;" rowspan="2" | [https://ggus.eu/ws/ticket_info.php?ticket=101197 certified] <br />
| style="border-bottom:1px dotted silver;" | OCCI - carach5.ics.muni.cz <br />
| bgcolor="lime" style="border-bottom:1px dotted silver;" | 87% <br />
| style="border-bottom:1px dotted silver;" | Outages 3, 4 January &amp; 25-27 January<br />
|-<br />
| style="border-bottom:1px dotted silver;" | CDMI - carach3.ics.muni.cz <br />
| bgcolor="lime" style="border-bottom:1px dotted silver;" | 100% <br />
| style="border-bottom:1px dotted silver;" | CDMI-TCP ping probe only<br />
|-<br />
| style="border-bottom:1px dotted silver;" rowspan="2" | FZ Jülich <br />
| style="border-bottom:1px dotted silver;" rowspan="2" | DE <br />
| style="border-bottom:1px dotted silver;" rowspan="2" | Björn Hagemeier <br />
| style="border-bottom:1px dotted silver;" rowspan="2" | Shahbaz Memon <br />
| style="border-bottom:1px dotted silver;" rowspan="2" | FZJ <br />
| style="border-bottom:1px dotted silver;" rowspan="2" | OpenStack <br />
| style="border-bottom:1px dotted silver;" rowspan="2" | <br />
| style="border-bottom:1px dotted silver;" | OCCI - egi-cloud.zam.kfa-juelich.de <br />
| bgcolor="lime" style="border-bottom:1px dotted silver;" | 99% <br />
| style="border-bottom:1px dotted silver;" | 31 January scheduled downtime.<br />
|-<br />
| style="border-bottom:1px dotted silver;" | CDMI - swift.zam.kfa-juelich.de <br />
| bgcolor="lime" style="border-bottom:1px dotted silver;" | 100% <br />
| style="border-bottom:1px dotted silver;" | CDMI TCP probe only. 31 January scheduled downtime.<br />
|-<br />
| style="border-bottom:1px dotted silver;" | CRNS/IN2P3-LAL <br />
| style="border-bottom:1px dotted silver;" | FR <br />
| style="border-bottom:1px dotted silver;" | Michel Jouvin <br />
| style="border-bottom:1px dotted silver;" | Mohammed Araj <br />
| style="border-bottom:1px dotted silver;" | GRIF <br />
| style="border-bottom:1px dotted silver;" | StratusLab <br />
| style="border-bottom:1px dotted silver;" | <br />
| style="border-bottom:1px dotted silver;" | OCCI - onehost-2.lal.in2p3.fr <br />
| style="border-bottom:1px dotted silver;" | 0% <br />
| style="border-bottom:1px dotted silver;" | SAM fails to instantiate VMs: "probe instantiation failed: "/usr/local/bin/VMInstantiation-probe:main:::418] Started probe 'VMInstantiation-probe'..."<br />
|-<br />
| style="border-bottom:1px dotted silver;" rowspan="2" | GWDG <br />
| style="border-bottom:1px dotted silver;" rowspan="2" | DE <br />
| style="border-bottom:1px dotted silver;" rowspan="2" | Piotr Kasprzak <br />
| style="border-bottom:1px dotted silver;" rowspan="2" | Ramin Yahyapour, Philipp Wieder <br />
| style="border-bottom:1px dotted silver;" rowspan="2" | GoeGrid <br />
| style="border-bottom:1px dotted silver;" rowspan="2" | OpenNebula <br />
| style="border-bottom:1px dotted silver;" rowspan="2" | scheduled <br />
| style="border-bottom:1px dotted silver;" | OCCI - occi.cloud.gwdg.de <br />
| bgcolor="yellow" style="border-bottom:1px dotted silver;" | 83% <br />
| style="border-bottom:1px dotted silver;" | Outage 23-28 January.<br />
|-<br />
| style="border-bottom:1px dotted silver;" | CDMI - cdmi.cloud.gwdg.de <br />
| bgcolor="lime" style="border-bottom:1px dotted silver;" | 100% <br />
| style="border-bottom:1px dotted silver;" | CDMI TCP probe only.<br />
|-<br />
| style="border-bottom:1px dotted silver;" | CSIC/IFCA <br />
| style="border-bottom:1px dotted silver;" | ES <br />
| style="border-bottom:1px dotted silver;" | Alvaro Lopez Garcia <br />
| style="border-bottom:1px dotted silver;" | Enol Fernandez, Pablo Orviz <br />
| style="border-bottom:1px dotted silver;" | IFCA-LCG2 <br />
| style="border-bottom:1px dotted silver;" | OpenStack <br />
| bgcolor="lime" style="border-bottom:1px dotted silver;" | [https://ggus.eu/index.php?mode=ticket_info&ticket_id=100990 certified] <br />
| style="border-bottom:1px dotted silver;" | OCCI - cloud.ifca.es <br />
| bgcolor="yellow" style="border-bottom:1px dotted silver;" | 69% <br />
| style="border-bottom:1px dotted silver;" | Spotty service, improved much after service downtime on 15 January.<br />
|-<br />
| style="border-bottom:1px dotted silver;" | II SAS <br />
| style="border-bottom:1px dotted silver;" | SK <br />
| style="border-bottom:1px dotted silver;" | Viet Tran <br />
| style="border-bottom:1px dotted silver;" | Martin Bobak <br />
| style="border-bottom:1px dotted silver;" | IISAS-FedCloud <br />
| style="border-bottom:1px dotted silver;" | OpenStack <br />
| style="border-bottom:1px dotted silver;" | scheduled <br />
| style="border-bottom:1px dotted silver;" | OCCI - nova.ui.savba.sk <br />
| bgcolor="lime" style="border-bottom:1px dotted silver;" | 90% <br />
| style="border-bottom:1px dotted silver;" | Occasional outage. Structural outage 24 - 27 January<br />
|-<br />
| style="border-bottom:1px dotted silver;" | INFN - Catania <br />
| style="border-bottom:1px dotted silver;" | IT <br />
| style="border-bottom:1px dotted silver;" | Roberto Barbera <br />
| style="border-bottom:1px dotted silver;" | Giuseppe Larocca, Maurizio Paone, Diego Scardacci <br />
| style="border-bottom:1px dotted silver;" | INFN-CATANIA-STACK <br />
| style="border-bottom:1px dotted silver;" | OpenStack <br />
| style="border-bottom:1px dotted silver;" | <br />
| style="border-bottom:1px dotted silver;" | OCCI - stack-server-01.ct.infn.it <br />
| style="border-bottom:1px dotted silver;" | 0% <br />
| style="border-bottom:1px dotted silver;" | Service critical, but probe reports no failure?<br />
|-<br />
| style="border-bottom:1px dotted silver;" | KTH <br />
| style="border-bottom:1px dotted silver;" | SE <br />
| style="border-bottom:1px dotted silver;" | Zeeshan Ali Shah <br />
| style="border-bottom:1px dotted silver;" | Ake Edlund <br />
| style="border-bottom:1px dotted silver;" | KTH-CLOUD <br />
| style="border-bottom:1px dotted silver;" | OpenNebula <br />
| bgcolor="lime" style="border-bottom:1px dotted silver;" | [https://ggus.eu/ws/ticket_info.php?ticket=101028 certified] <br />
| style="border-bottom:1px dotted silver;" | OCCI - egi.cloud.pdc.kth.se <br />
| bgcolor="lime" style="border-bottom:1px dotted silver;" | 99% <br />
| style="border-bottom:1px dotted silver;" | One outage on 25 January<br />
|-<br />
| style="border-bottom:1px dotted silver;" | INFN - Bari <br />
| style="border-bottom:1px dotted silver;" | IT <br />
| style="border-bottom:1px dotted silver;" | Marica Antonacci <br />
| style="border-bottom:1px dotted silver;" | Giacinto Donvito, Stefano Nicotri, Vincenzo Spinoso <br />
| style="border-bottom:1px dotted silver;" | PRISMA-INFN-BARI <br />
| style="border-bottom:1px dotted silver;" | OpenStack <br />
| style="border-bottom:1px dotted silver;" | <br />
| style="border-bottom:1px dotted silver;" | OCCI - prisma-cloud.ba.infn.it <br />
| bgcolor="lime" style="border-bottom:1px dotted silver;" | 92% <br />
| style="border-bottom:1px dotted silver;" | Patchy service, occasional outages on 14, 15, 16 &amp; 22 January<br />
|}<br />
<br />
=== Integrating Resource Providers ===<br />
<br />
Reporting period: 1 Jan 2014 - 31 Jan 2014 <br />
<br />
{| width="120%" cellspacing="0" cellpadding="5" style="border:1px solid black; text-align:left;" class="wikitable sortable"<br />
|- style="background:lightgray;"<br />
! style="border-bottom:1px solid black;" | Affiliation <br />
! style="border-bottom:1px solid black;" | CC <br />
! style="border-bottom:1px solid black;" | Representative <br />
! style="border-bottom:1px solid black;" | Deputies <br />
! style="border-bottom:1px solid black;" | Host Site <br />
! style="border-bottom:1px solid black;" | CMF <br />
! style="border-bottom:1px solid black;" | Certification <br />
! style="border-bottom:1px solid black;" | Resource Endpoints <br />
! style="border-bottom:1px solid black;" | Status (avg.) <br />
! style="border-bottom:1px solid black;" | Comment<br />
|-<br />
| style="border-bottom:1px dotted silver;" | GRNET <br />
| style="border-bottom:1px dotted silver;" | GR <br />
| style="border-bottom:1px dotted silver;" | Kostas Koumantaros <br />
| style="border-bottom:1px dotted silver;" | Athanasia Assiki <br />
| style="border-bottom:1px dotted silver;" | HG-09-Okeanos-Cloud <br />
| style="border-bottom:1px dotted silver;" | Synnefo <br />
| style="border-bottom:1px dotted silver;" | Scheduled <br />
| style="border-bottom:1px dotted silver;" | OCCI - okeanos-occi2.hellasgrid.gr <br />
| bgcolor="yellow" style="border-bottom:1px dotted silver;" | 75% <br />
| style="border-bottom:1px dotted silver;" | Partial monitoring (no accounting). Regular service outages, reason not known (no probe failure reported)<br />
|-<br />
| style="border-bottom:1px dotted silver;" | CRNS/IN2P3-CC <br />
| style="border-bottom:1px dotted silver;" | FR <br />
| style="border-bottom:1px dotted silver;" | Gilles MATHIEU <br />
| style="border-bottom:1px dotted silver;" | Mattieu Puel <br />
| style="border-bottom:1px dotted silver;" | IN2P3-CC <br />
| style="border-bottom:1px dotted silver;" | OpenStack <br />
| style="border-bottom:1px dotted silver;" | <br />
| style="border-bottom:1px dotted silver;" | OCCI - ccocci.in2p3.fr <br />
| style="border-bottom:1px dotted silver;" | 0% <br />
| style="border-bottom:1px dotted silver;" | Probe seem to run normally but reports consistent failure?<br />
|}<br />
<br />
=== Interested Resource Providers ===<br />
<br />
{| cellspacing="0" cellpadding="5" style="border:1px solid black; text-align:left;" class="wikitable sortable"<br />
|- style="background:lightgray;"<br />
! style="border-bottom:1px solid black;" | Affiliation <br />
! style="border-bottom:1px solid black;" | CC <br />
! style="border-bottom:1px solid black;" | Representative <br />
! style="border-bottom:1px solid black;" | Deputies <br />
! style="border-bottom:1px solid black;" | CMF <br />
! style="border-bottom:1px solid black;" | Comment<br />
|-<br />
| style="border-bottom:1px dotted silver;" | KISTI <br />
| style="border-bottom:1px dotted silver;" | KR <br />
| style="border-bottom:1px dotted silver;" | Soonwook Hwang <br />
| style="border-bottom:1px dotted silver;" | Sangwan Kim, Taesang Huh, Jae-Hyuck Kwak <br />
| style="border-bottom:1px dotted silver;" | OpenStack <br />
| style="border-bottom:1px dotted silver;" | <br />
|-<br />
| style="border-bottom:1px dotted silver;" | IICT-BAS <br />
| style="border-bottom:1px dotted silver;" | BG <br />
| style="border-bottom:1px dotted silver;" | Emanouil Atanassov <br />
| style="border-bottom:1px dotted silver;" | Todor Gurov <br />
| style="border-bottom:1px dotted silver;" | OpenStack <br />
| style="border-bottom:1px dotted silver;" | <br />
|-<br />
| style="border-bottom:1px dotted silver;" | INFN - Napoli <br />
| style="border-bottom:1px dotted silver;" | IT <br />
| style="border-bottom:1px dotted silver;" | Silvio Pardi <br />
| style="border-bottom:1px dotted silver;" | <br />
| style="border-bottom:1px dotted silver;" | OpenStack <br />
| style="border-bottom:1px dotted silver;" | <br />
|-<br />
| style="border-bottom:1px dotted silver;" | INFN - CNAF <br />
| style="border-bottom:1px dotted silver;" | IT <br />
| style="border-bottom:1px dotted silver;" | Elisabetta Ronchieri <br />
| style="border-bottom:1px dotted silver;" | Davide Salomoni, Andrea Cristofori <br />
| style="border-bottom:1px dotted silver;" | OpenStack <br />
| style="border-bottom:1px dotted silver;" | <br />
|-<br />
| style="border-bottom:1px dotted silver;" | INFN - Torino <br />
| style="border-bottom:1px dotted silver;" | IT <br />
| style="border-bottom:1px dotted silver;" | Andrea Guarise <br />
| style="border-bottom:1px dotted silver;" | <br />
| style="border-bottom:1px dotted silver;" | OpenStack <br />
| style="border-bottom:1px dotted silver;" | <br />
|-<br />
| style="border-bottom:1px dotted silver;" | INFN - Padova <br />
| style="border-bottom:1px dotted silver;" | IT <br />
| style="border-bottom:1px dotted silver;" | Marco Verlato <br />
| style="border-bottom:1px dotted silver;" | Eric Frizziero <br />
| style="border-bottom:1px dotted silver;" | OpenStack <br />
| style="border-bottom:1px dotted silver;" | <br />
|-<br />
| style="border-bottom:1px dotted silver;" | CETA-CIEMAT <br />
| style="border-bottom:1px dotted silver;" | ES <br />
| style="border-bottom:1px dotted silver;" | Guillermo Díaz Herrero, <br />
| style="border-bottom:1px dotted silver;" | Miguel Ángel Díaz, Abel Paz <br />
| style="border-bottom:1px dotted silver;" | OpenStack <br />
| style="border-bottom:1px dotted silver;" | <br />
|-<br />
| style="border-bottom:1px dotted silver;" | MTA SZTAKI <br />
| style="border-bottom:1px dotted silver;" | HU <br />
| style="border-bottom:1px dotted silver;" | Sandor Acs <br />
| style="border-bottom:1px dotted silver;" | Peter Kotcauer, Gabor Kecskemeti <br />
| style="border-bottom:1px dotted silver;" | OpenNebula <br />
| style="border-bottom:1px dotted silver;" | <br />
|-<br />
| style="border-bottom:1px dotted silver;" | Cyfronet (NGI PL) <br />
| style="border-bottom:1px dotted silver;" | PL <br />
| style="border-bottom:1px dotted silver;" | Tomasz Szepieniec <br />
| style="border-bottom:1px dotted silver;" | Marcin Radecki, Jan Meizner <br />
| style="border-bottom:1px dotted silver;" | &nbsp;???? <br />
| style="border-bottom:1px dotted silver;" | <br />
|-<br />
| style="border-bottom:1px dotted silver;" | SURFsara <br />
| style="border-bottom:1px dotted silver;" | NL <br />
| style="border-bottom:1px dotted silver;" | Jhon Masschelein <br />
| style="border-bottom:1px dotted silver;" | Maurice Bouwhuis, Machiel Jansen <br />
| style="border-bottom:1px dotted silver;" | OpenNebula <br />
| style="border-bottom:1px dotted silver;" | <br />
|-<br />
| style="border-bottom:1px dotted silver;" | CRNS/IPHC <br />
| style="border-bottom:1px dotted silver;" | FR <br />
| style="border-bottom:1px dotted silver;" | Jérôme Pansanel <br />
| style="border-bottom:1px dotted silver;" | <br />
| style="border-bottom:1px dotted silver;" | <br />
| style="border-bottom:1px dotted silver;" | <br />
|-<br />
| style="border-bottom:1px dotted silver;" | ISRGrid/IUCC <br />
| style="border-bottom:1px dotted silver;" | IL <br />
| style="border-bottom:1px dotted silver;" | Yossi Baruch <br />
| style="border-bottom:1px dotted silver;" | <br />
| style="border-bottom:1px dotted silver;" | <br />
| style="border-bottom:1px dotted silver;" | <br />
|-<br />
| style="border-bottom:1px dotted silver;" | TUBITAK ULAKBIM <br />
| style="border-bottom:1px dotted silver;" | TR <br />
| style="border-bottom:1px dotted silver;" | Huseyin Cotuk <br />
| style="border-bottom:1px dotted silver;" | Feyza Eryol, Onur Temizsoylu <br />
| style="border-bottom:1px dotted silver;" | OpenStack <br />
| style="border-bottom:1px dotted silver;" | <br />
|-<br />
| style="border-bottom:1px dotted silver;" | DESY <br />
| style="border-bottom:1px dotted silver;" | DE <br />
| style="border-bottom:1px dotted silver;" | Patrick Furhmann <br />
| style="border-bottom:1px dotted silver;" | Paul Millar <br />
| style="border-bottom:1px dotted silver;" | dCache <br />
| style="border-bottom:1px dotted silver;" | Storage only<br />
|-<br />
| style="border-bottom:1px dotted silver;" | STFC/RAL <br />
| style="border-bottom:1px dotted silver;" | UK <br />
| style="border-bottom:1px dotted silver;" | Ian Collier <br />
| style="border-bottom:1px dotted silver;" | Frazer Barnsley, Alan Kyffin <br />
| style="border-bottom:1px dotted silver;" | <br />
| style="border-bottom:1px dotted silver;" | <br />
|-<br />
| style="border-bottom:1px dotted silver;" | STFC/RAL Harwell Science <br />
| style="border-bottom:1px dotted silver;" | UK <br />
| style="border-bottom:1px dotted silver;" | Jens Jensen <br />
| style="border-bottom:1px dotted silver;" | <br />
| style="border-bottom:1px dotted silver;" | Castor <br />
| style="border-bottom:1px dotted silver;" | Cloud storage only<br />
|-<br />
| style="border-bottom:1px dotted silver;" | UKIM <br />
| style="border-bottom:1px dotted silver;" | MK <br />
| style="border-bottom:1px dotted silver;" | Boro Jakimovski <br />
| style="border-bottom:1px dotted silver;" | <br />
| style="border-bottom:1px dotted silver;" | <br />
| style="border-bottom:1px dotted silver;" | <br />
|-<br />
| style="border-bottom:1px dotted silver;" | IFAE / PIC <br />
| style="border-bottom:1px dotted silver;" | ES <br />
| style="border-bottom:1px dotted silver;" | Victor Mendez <br />
| style="border-bottom:1px dotted silver;" | <br />
| style="border-bottom:1px dotted silver;" | <br />
| style="border-bottom:1px dotted silver;" | <br />
|-<br />
| style="border-bottom:1px dotted silver;" | SAGrid <br />
| style="border-bottom:1px dotted silver;" | ZA <br />
| style="border-bottom:1px dotted silver;" | Bruce Becker <br />
| style="border-bottom:1px dotted silver;" | <br />
| style="border-bottom:1px dotted silver;" | <br />
| style="border-bottom:1px dotted silver;" | <br />
|-<br />
| style="border-bottom:1px dotted silver;" | CSC <br />
| style="border-bottom:1px dotted silver;" | FI <br />
| style="border-bottom:1px dotted silver;" | Jura Tarus <br />
| style="border-bottom:1px dotted silver;" | Luís Alves, Ulf Tigerstedt, Kalle Happonen <br />
| style="border-bottom:1px dotted silver;" | OpenStack <br />
| style="border-bottom:1px dotted silver;" | Status: Testing resource integration<br />
|-<br />
| style="border-bottom:1px dotted silver;" | SRCE <br />
| style="border-bottom:1px dotted silver;" | HR <br />
| style="border-bottom:1px dotted silver;" | Emir Imamagic <br />
| style="border-bottom:1px dotted silver;" | <br />
| style="border-bottom:1px dotted silver;" | <br />
| style="border-bottom:1px dotted silver;" | <br />
|-<br />
| style="border-bottom:1px dotted silver;" | GridPP <br />
| style="border-bottom:1px dotted silver;" | UK <br />
| style="border-bottom:1px dotted silver;" | Adam Huffman <br />
| style="border-bottom:1px dotted silver;" | <br />
| style="border-bottom:1px dotted silver;" | OpenStack <br />
| style="border-bottom:1px dotted silver;" | Hosted at Imperial College<br />
|}<br />
<br />
=== Testbed ===<br />
<br />
More information about the Resource Providers belonging to the FedCloud Testbed are available [[Fedcloud-tf:Testbed|here]]. <br />
<br />
== Cloud Management Frameworks ==<br />
<br />
The federation of IaaS Cloud resources in EGI is built upon the extensive autonomy of Resource Providers in terms of ownership of exposed resources. The different cloud providers may have different Cloud Managemnt Frameworks (ex. OpenNebula, OpenStack, etc...), the federation implies only that the CMF exposes a set of [[Fedcloud-tf:Technology:Architecture|common interfaces]] (ex. [[Fedcloud-tf:Technology:Architecture#VM_management_interface:_OCCI|OCCI for VM management]], [[Fedcloud-tf:Technology:Architecture#Data_management_interface:_CDMI|CDMI for Data management]], etc...) <br />
<br />
More in-depth information about the EGI Federated Cloud architecture and technology is provided [[Fedcloud-tf:Technology|here]]. <br />
<br />
=== Compatible CMFs ===<br />
<br />
The table below provides a list of the most famous CMFs and the status of the support of the EGI Federated Cloud interfaces. <br />
<br />
{| class="wikitable"<br />
|-<br />
! Cloud Mgmt. Fram. <br />
! Fed. AAI <br />
! Monitoring<ref>Monitoring happens passive, i.e. no active integration from the side of Cloud Management Frameworks necessary.</ref> <br />
! Accounting <br />
! Img. Mgmt. <br />
! OCCI <br />
! CDMI<br />
|-<br />
! OpenStack <br />
| Yes <br />
| Yes <br />
| Yes <br />
| Yes <br />
| Yes <br />
| Yes<br />
|-<br />
! OpenNebula <br />
| Yes <br />
| Yes <br />
| Yes <br />
| Yes <br />
| Yes <br />
| Yes<br />
|-<br />
! StratusLab <br />
| Yes <br />
| Yes <br />
| Yes <br />
| - <br />
| Yes<ref>StratusLab’s OCCI support is based on OpenNebula. Since StratusLab will discontinue its integration with OpenNebula (see below), the future of StratusLab OCCI interface is unknown at this point in time.</ref> <br />
| -<br />
|-<br />
! WNoDeS <br />
| Yes <br />
| Yes <br />
| Yes <br />
| - <br />
| - <br />
| -<br />
|-<br />
! Synnefo <br />
| Yes <br />
| Yes <br />
| - <br />
| - <br />
| Yes <br />
| -<br />
|}<br />
<br />
== Deployment ==<br />
<br />
Guides for deployment of the FedCloud interfaces for the most used Cloud Management Frameworks are reported below: <br />
<br />
*[[Fedcloud-tf:ResourceProviders:OpenNebula|OpenNebula]] <br />
*[[Fedcloud-tf:ResourceProviders:OpenStack|OpenStack]] <br />
*[[Fedcloud-tf:ResourceProviders:StratusLab|StratusLab]] <br />
*[[Fedcloud-tf:ResourceProviders:WNoDeS|WNoDeS]] <br />
*[[Fedcloud-tf:ResourceProviders:Synnefo|Synnefo]]<br />
<br />
== References ==<br />
<br />
<references /></div>
Asimon
https://wiki.egi.eu/w/index.php?title=Fedcloud-tf:ResourceProviders&diff=65291
Fedcloud-tf:ResourceProviders
2014-03-04T07:26:29Z
<p>Asimon: Undo revision 65290 by Asimon (talk)</p>
<hr />
<div>{{Fedcloud-tf:Menu}} {{TOC_right}} <br />
<br />
== EGI Federated Cloud Resource Providers ==<br />
<br />
EGI Federated Cloud resource providers are institutions and companies that contribute to the FedCloud providing access to their cloud infrastructure via the Federation. Resource providers are free to use any Cloud Manafement Framework (OpenNebula, OpenStack, etc...), the only requirement is that the CMF exposes interfaces compliant to the [[Fedcloud-tf:Technology:Architecture|FedCloud standards]]. <br />
<br />
== Join as a Resource Provider ==<br />
<br />
Every institution and company is invited to join the EGI Federated Cloud. The members of the EGI Federated Cloud have also the opportunity to join the [[Fedcloud-tf:FederatedCloudsTaskForce|EGI Federated Cloud Task Force]], contributing directly to the creation and implementation of the clouds federation. <br />
<br />
If you want to join the EGI Federated Cloud, you can send en email to the [mailto:fedcloud-tf@mailman.egi.eu EGI Federated Cloud Task Force], specifying the following information (fields with * are mandatory) <br />
<br />
*Name* <br />
*Institute* <br />
*Email address* <br />
*One paragraph long description of your organization <br />
*Envisaged timeline (is there a deadline to finish the setup? for how long do you wish to contribute to the EGI Federated project?) <br />
*Estimated number and size of machines that you may provide to EGI <br />
*Type of Cloud Management Framework you are using <br />
*Link to webpage, document or other online resource for further information<br />
<br />
== Current Resource Providers ==<br />
<br />
=== Fully integrated Resource Providers ===<br />
<br />
Reporting period: 1 Jan 2014 - 31 Jan 2014 <br />
<br />
{| width="150%" cellspacing="0" cellpadding="5" style="border:1px solid black; text-align:left;" class="wikitable"<br />
|- style="background:lightgray;"<br />
! style="border-bottom:1px solid black;" | Affiliation <br />
! style="border-bottom:1px solid black;" | CC <br />
! style="border-bottom:1px solid black;" | Main contact <br />
! style="border-bottom:1px solid black;" | Deputies <br />
! style="border-bottom:1px solid black;" | Host Site <br />
! style="border-bottom:1px solid black;" | CMF <br />
! style="border-bottom:1px solid black;" | Certification <br />
! style="border-bottom:1px solid black;" | Resource Endpoints <br />
! style="border-bottom:1px solid black;" | Nagios Avail. (avg.) <br />
! style="border-bottom:1px solid black;" | Comment<br />
|-<br />
| style="border-bottom:1px dotted silver;" | 100 Percent IT Ltd <br />
| style="border-bottom:1px dotted silver;" | UK <br />
| style="border-bottom:1px dotted silver;" | David Blundell <br />
| style="border-bottom:1px dotted silver;" | <br />
| style="border-bottom:1px dotted silver;" | 100IT <br />
| style="border-bottom:1px dotted silver;" | OpenStack <br />
| bgcolor="lime" style="border-bottom:1px dotted silver;" | certified <br />
| style="border-bottom:1px dotted silver;" | OCCI - occi-api.100percentit.com <br />
| bgcolor="#33ff00" style="border-bottom:1px dotted silver;" | 96% <br />
| style="border-bottom:1px dotted silver;" | "(Return code of 127 is out of bounds - plugin may be missing)"<br />
|-<br />
| style="border-bottom:1px dotted silver;" | UNIZAR / BIFI <br />
| style="border-bottom:1px dotted silver;" | ES <br />
| style="border-bottom:1px dotted silver;" | Ruben Valles <br />
| style="border-bottom:1px dotted silver;" | Jaime Ibar Yubero <br />
| style="border-bottom:1px dotted silver;" | BIFI <br />
| style="border-bottom:1px dotted silver;" | OpenStack <br />
| bgcolor="lime" style="border-bottom:1px dotted silver;" | [https://ggus.eu/ws/ticket_info.php?ticket=100239 certified] <br />
| style="border-bottom:1px dotted silver;" | OCCI - server4-epsh.unizar.es <br />
| style="border-bottom:1px dotted silver;" | 11% <br />
| style="border-bottom:1px dotted silver;" | Service 95% plus available/stable since 26 January.<br />
|-<br />
| style="border-bottom:1px dotted silver;" | BSC <br />
| style="border-bottom:1px dotted silver;" | ES <br />
| style="border-bottom:1px dotted silver;" | Daniele Lezzi <br />
| style="border-bottom:1px dotted silver;" | Roger Rafanell <br />
| style="border-bottom:1px dotted silver;" | BSC-Cloud <br />
| style="border-bottom:1px dotted silver;" | Emotive <br />
| style="border-bottom:1px dotted silver;" | <br />
| style="border-bottom:1px dotted silver;" | CDMI - bscgrid05.bsc.es <br />
| bgcolor="lime" style="border-bottom:1px dotted silver;" | 100% <br />
| style="border-bottom:1px dotted silver;" | CDMI-TCP ping probe only<br />
|-<br />
| style="border-bottom:1px dotted silver;" | FCTSG <br />
| style="border-bottom:1px dotted silver;" | ES <br />
| style="border-bottom:1px dotted silver;" | Alvaro Simon <br />
| style="border-bottom:1px dotted silver;" | Ivan Diaz Alvarez <br />
| style="border-bottom:1px dotted silver;" | CESGA <br />
| style="border-bottom:1px dotted silver;" | OpenNebula <br />
| bgcolor="yellow" style="border-bottom:1px dotted silver;" | [https://ggus.eu/ws/ticket_info.php?ticket=100948 in progress] <br />
| style="border-bottom:1px dotted silver;" | OCCI - cloud.cesga.es <br />
| bgcolor="yellow" style="border-bottom:1px dotted silver;" | 81% <br />
| style="border-bottom:1px dotted silver;" | Spotty service around 7,8,9 January, outage 23-27 January<br />
|-<br />
| style="border-bottom:1px dotted silver;" rowspan="2" | CESNET <br />
| style="border-bottom:1px dotted silver;" rowspan="2" | CZ <br />
| style="border-bottom:1px dotted silver;" rowspan="2" | Miroslav Ruda <br />
| style="border-bottom:1px dotted silver;" rowspan="2" | Boris Parak <br />
| style="border-bottom:1px dotted silver;" rowspan="2" | CESNET-MetaCloud <br />
| style="border-bottom:1px dotted silver;" rowspan="2" | OpenNebula <br />
| bgcolor="lime" style="border-bottom:1px dotted silver;" rowspan="2" | [https://ggus.eu/ws/ticket_info.php?ticket=101197 certified] <br />
| style="border-bottom:1px dotted silver;" | OCCI - carach5.ics.muni.cz <br />
| bgcolor="lime" style="border-bottom:1px dotted silver;" | 87% <br />
| style="border-bottom:1px dotted silver;" | Outages 3, 4 January &amp; 25-27 January<br />
|-<br />
| style="border-bottom:1px dotted silver;" | CDMI - carach3.ics.muni.cz <br />
| bgcolor="lime" style="border-bottom:1px dotted silver;" | 100% <br />
| style="border-bottom:1px dotted silver;" | CDMI-TCP ping probe only<br />
|-<br />
| style="border-bottom:1px dotted silver;" rowspan="2" | FZ Jülich <br />
| style="border-bottom:1px dotted silver;" rowspan="2" | DE <br />
| style="border-bottom:1px dotted silver;" rowspan="2" | Björn Hagemeier <br />
| style="border-bottom:1px dotted silver;" rowspan="2" | Shahbaz Memon <br />
| style="border-bottom:1px dotted silver;" rowspan="2" | FZJ <br />
| style="border-bottom:1px dotted silver;" rowspan="2" | OpenStack <br />
| style="border-bottom:1px dotted silver;" rowspan="2" | <br />
| style="border-bottom:1px dotted silver;" | OCCI - egi-cloud.zam.kfa-juelich.de <br />
| bgcolor="lime" style="border-bottom:1px dotted silver;" | 99% <br />
| style="border-bottom:1px dotted silver;" | 31 January scheduled downtime.<br />
|-<br />
| style="border-bottom:1px dotted silver;" | CDMI - swift.zam.kfa-juelich.de <br />
| bgcolor="lime" style="border-bottom:1px dotted silver;" | 100% <br />
| style="border-bottom:1px dotted silver;" | CDMI TCP probe only. 31 January scheduled downtime.<br />
|-<br />
| style="border-bottom:1px dotted silver;" | CRNS/IN2P3-LAL <br />
| style="border-bottom:1px dotted silver;" | FR <br />
| style="border-bottom:1px dotted silver;" | Michel Jouvin <br />
| style="border-bottom:1px dotted silver;" | Mohammed Araj <br />
| style="border-bottom:1px dotted silver;" | GRIF <br />
| style="border-bottom:1px dotted silver;" | StratusLab <br />
| style="border-bottom:1px dotted silver;" | <br />
| style="border-bottom:1px dotted silver;" | OCCI - onehost-2.lal.in2p3.fr <br />
| style="border-bottom:1px dotted silver;" | 0% <br />
| style="border-bottom:1px dotted silver;" | SAM fails to instantiate VMs: "probe instantiation failed: "/usr/local/bin/VMInstantiation-probe:main:::418] Started probe 'VMInstantiation-probe'..."<br />
|-<br />
| style="border-bottom:1px dotted silver;" rowspan="2" | GWDG <br />
| style="border-bottom:1px dotted silver;" rowspan="2" | DE <br />
| style="border-bottom:1px dotted silver;" rowspan="2" | Piotr Kasprzak <br />
| style="border-bottom:1px dotted silver;" rowspan="2" | Ramin Yahyapour, Philipp Wieder <br />
| style="border-bottom:1px dotted silver;" rowspan="2" | GoeGrid <br />
| style="border-bottom:1px dotted silver;" rowspan="2" | OpenNebula <br />
| style="border-bottom:1px dotted silver;" rowspan="2" | scheduled <br />
| style="border-bottom:1px dotted silver;" | OCCI - occi.cloud.gwdg.de <br />
| bgcolor="yellow" style="border-bottom:1px dotted silver;" | 83% <br />
| style="border-bottom:1px dotted silver;" | Outage 23-28 January.<br />
|-<br />
| style="border-bottom:1px dotted silver;" | CDMI - cdmi.cloud.gwdg.de <br />
| bgcolor="lime" style="border-bottom:1px dotted silver;" | 100% <br />
| style="border-bottom:1px dotted silver;" | CDMI TCP probe only.<br />
|-<br />
| style="border-bottom:1px dotted silver;" | CSIC/IFCA <br />
| style="border-bottom:1px dotted silver;" | ES <br />
| style="border-bottom:1px dotted silver;" | Alvaro Lopez Garcia <br />
| style="border-bottom:1px dotted silver;" | Enol Fernandez, Pablo Orviz <br />
| style="border-bottom:1px dotted silver;" | IFCA-LCG2 <br />
| style="border-bottom:1px dotted silver;" | OpenStack <br />
| bgcolor="lime" style="border-bottom:1px dotted silver;" | [https://ggus.eu/index.php?mode=ticket_info&ticket_id=100990 certified] <br />
| style="border-bottom:1px dotted silver;" | OCCI - cloud.ifca.es <br />
| bgcolor="yellow" style="border-bottom:1px dotted silver;" | 69% <br />
| style="border-bottom:1px dotted silver;" | Spotty service, improved much after service downtime on 15 January.<br />
|-<br />
| style="border-bottom:1px dotted silver;" | II SAS <br />
| style="border-bottom:1px dotted silver;" | SK <br />
| style="border-bottom:1px dotted silver;" | Viet Tran <br />
| style="border-bottom:1px dotted silver;" | Martin Bobak <br />
| style="border-bottom:1px dotted silver;" | IISAS-FedCloud <br />
| style="border-bottom:1px dotted silver;" | OpenStack <br />
| style="border-bottom:1px dotted silver;" | scheduled <br />
| style="border-bottom:1px dotted silver;" | OCCI - nova.ui.savba.sk <br />
| bgcolor="lime" style="border-bottom:1px dotted silver;" | 90% <br />
| style="border-bottom:1px dotted silver;" | Occasional outage. Structural outage 24 - 27 January<br />
|-<br />
| style="border-bottom:1px dotted silver;" | INFN - Catania <br />
| style="border-bottom:1px dotted silver;" | IT <br />
| style="border-bottom:1px dotted silver;" | Roberto Barbera <br />
| style="border-bottom:1px dotted silver;" | Giuseppe Larocca, Maurizio Paone, Diego Scardacci <br />
| style="border-bottom:1px dotted silver;" | INFN-CATANIA-STACK <br />
| style="border-bottom:1px dotted silver;" | OpenStack <br />
| style="border-bottom:1px dotted silver;" | <br />
| style="border-bottom:1px dotted silver;" | OCCI - stack-server-01.ct.infn.it <br />
| style="border-bottom:1px dotted silver;" | 0% <br />
| style="border-bottom:1px dotted silver;" | Service critical, but probe reports no failure?<br />
|-<br />
| style="border-bottom:1px dotted silver;" | KTH <br />
| style="border-bottom:1px dotted silver;" | SE <br />
| style="border-bottom:1px dotted silver;" | Zeeshan Ali Shah <br />
| style="border-bottom:1px dotted silver;" | Ake Edlund <br />
| style="border-bottom:1px dotted silver;" | KTH-CLOUD <br />
| style="border-bottom:1px dotted silver;" | OpenNebula <br />
| bgcolor="lime" style="border-bottom:1px dotted silver;" | [https://ggus.eu/ws/ticket_info.php?ticket=101028 certified] <br />
| style="border-bottom:1px dotted silver;" | OCCI - egi.cloud.pdc.kth.se <br />
| bgcolor="lime" style="border-bottom:1px dotted silver;" | 99% <br />
| style="border-bottom:1px dotted silver;" | One outage on 25 January<br />
|-<br />
| style="border-bottom:1px dotted silver;" | INFN - Bari <br />
| style="border-bottom:1px dotted silver;" | IT <br />
| style="border-bottom:1px dotted silver;" | Marica Antonacci <br />
| style="border-bottom:1px dotted silver;" | Giacinto Donvito, Stefano Nicotri, Vincenzo Spinoso <br />
| style="border-bottom:1px dotted silver;" | PRISMA-INFN-BARI <br />
| style="border-bottom:1px dotted silver;" | OpenStack <br />
| style="border-bottom:1px dotted silver;" | <br />
| style="border-bottom:1px dotted silver;" | OCCI - prisma-cloud.ba.infn.it <br />
| bgcolor="lime" style="border-bottom:1px dotted silver;" | 92% <br />
| style="border-bottom:1px dotted silver;" | Patchy service, occasional outages on 14, 15, 16 &amp; 22 January<br />
|}<br />
<br />
=== Integrating Resource Providers ===<br />
<br />
Reporting period: 1 Jan 2014 - 31 Jan 2014 <br />
<br />
{| width="120%" cellspacing="0" cellpadding="5" style="border:1px solid black; text-align:left;" class="wikitable sortable"<br />
|- style="background:lightgray;"<br />
! style="border-bottom:1px solid black;" | Affiliation <br />
! style="border-bottom:1px solid black;" | CC <br />
! style="border-bottom:1px solid black;" | Representative <br />
! style="border-bottom:1px solid black;" | Deputies <br />
! style="border-bottom:1px solid black;" | Host Site <br />
! style="border-bottom:1px solid black;" | CMF <br />
! style="border-bottom:1px solid black;" | Certification <br />
! style="border-bottom:1px solid black;" | Resource Endpoints <br />
! style="border-bottom:1px solid black;" | Status (avg.) <br />
! style="border-bottom:1px solid black;" | Comment<br />
|-<br />
| style="border-bottom:1px dotted silver;" | GRNET <br />
| style="border-bottom:1px dotted silver;" | GR <br />
| style="border-bottom:1px dotted silver;" | Kostas Koumantaros <br />
| style="border-bottom:1px dotted silver;" | Athanasia Assiki <br />
| style="border-bottom:1px dotted silver;" | HG-09-Okeanos-Cloud <br />
| style="border-bottom:1px dotted silver;" | Synnefo <br />
| style="border-bottom:1px dotted silver;" | Scheduled <br />
| style="border-bottom:1px dotted silver;" | OCCI - okeanos-occi2.hellasgrid.gr <br />
| bgcolor="yellow" style="border-bottom:1px dotted silver;" | 75% <br />
| style="border-bottom:1px dotted silver;" | Partial monitoring (no accounting). Regular service outages, reason not known (no probe failure reported)<br />
|-<br />
| style="border-bottom:1px dotted silver;" | CRNS/IN2P3-CC <br />
| style="border-bottom:1px dotted silver;" | FR <br />
| style="border-bottom:1px dotted silver;" | Gilles MATHIEU <br />
| style="border-bottom:1px dotted silver;" | Mattieu Puel <br />
| style="border-bottom:1px dotted silver;" | IN2P3-CC <br />
| style="border-bottom:1px dotted silver;" | OpenStack <br />
| style="border-bottom:1px dotted silver;" | <br />
| style="border-bottom:1px dotted silver;" | OCCI - ccocci.in2p3.fr <br />
| style="border-bottom:1px dotted silver;" | 0% <br />
| style="border-bottom:1px dotted silver;" | Probe seem to run normally but reports consistent failure?<br />
|}<br />
<br />
=== Interested Resource Providers ===<br />
<br />
{| cellspacing="0" cellpadding="5" style="border:1px solid black; text-align:left;" class="wikitable sortable"<br />
|- style="background:lightgray;"<br />
! style="border-bottom:1px solid black;" | Affiliation <br />
! style="border-bottom:1px solid black;" | CC <br />
! style="border-bottom:1px solid black;" | Representative <br />
! style="border-bottom:1px solid black;" | Deputies <br />
! style="border-bottom:1px solid black;" | CMF <br />
! style="border-bottom:1px solid black;" | Comment<br />
|-<br />
| style="border-bottom:1px dotted silver;" | KISTI <br />
| style="border-bottom:1px dotted silver;" | KR <br />
| style="border-bottom:1px dotted silver;" | Soonwook Hwang <br />
| style="border-bottom:1px dotted silver;" | Sangwan Kim, Taesang Huh, Jae-Hyuck Kwak <br />
| style="border-bottom:1px dotted silver;" | OpenStack <br />
| style="border-bottom:1px dotted silver;" | <br />
|-<br />
| style="border-bottom:1px dotted silver;" | IICT-BAS <br />
| style="border-bottom:1px dotted silver;" | BG <br />
| style="border-bottom:1px dotted silver;" | Emanouil Atanassov <br />
| style="border-bottom:1px dotted silver;" | Todor Gurov <br />
| style="border-bottom:1px dotted silver;" | OpenStack <br />
| style="border-bottom:1px dotted silver;" | <br />
|-<br />
| style="border-bottom:1px dotted silver;" | INFN - Napoli <br />
| style="border-bottom:1px dotted silver;" | IT <br />
| style="border-bottom:1px dotted silver;" | Silvio Pardi <br />
| style="border-bottom:1px dotted silver;" | <br />
| style="border-bottom:1px dotted silver;" | OpenStack <br />
| style="border-bottom:1px dotted silver;" | <br />
|-<br />
| style="border-bottom:1px dotted silver;" | INFN - CNAF <br />
| style="border-bottom:1px dotted silver;" | IT <br />
| style="border-bottom:1px dotted silver;" | Elisabetta Ronchieri <br />
| style="border-bottom:1px dotted silver;" | Davide Salomoni, Andrea Cristofori <br />
| style="border-bottom:1px dotted silver;" | OpenStack <br />
| style="border-bottom:1px dotted silver;" | <br />
|-<br />
| style="border-bottom:1px dotted silver;" | INFN - Torino <br />
| style="border-bottom:1px dotted silver;" | IT <br />
| style="border-bottom:1px dotted silver;" | Andrea Guarise <br />
| style="border-bottom:1px dotted silver;" | <br />
| style="border-bottom:1px dotted silver;" | OpenStack <br />
| style="border-bottom:1px dotted silver;" | <br />
|-<br />
| style="border-bottom:1px dotted silver;" | INFN - Padova <br />
| style="border-bottom:1px dotted silver;" | IT <br />
| style="border-bottom:1px dotted silver;" | Marco Verlato <br />
| style="border-bottom:1px dotted silver;" | Eric Frizziero <br />
| style="border-bottom:1px dotted silver;" | OpenStack <br />
| style="border-bottom:1px dotted silver;" | <br />
|-<br />
| style="border-bottom:1px dotted silver;" | CETA-CIEMAT <br />
| style="border-bottom:1px dotted silver;" | ES <br />
| style="border-bottom:1px dotted silver;" | Guillermo Díaz Herrero, <br />
| style="border-bottom:1px dotted silver;" | Miguel Ángel Díaz, Abel Paz <br />
| style="border-bottom:1px dotted silver;" | OpenStack <br />
| style="border-bottom:1px dotted silver;" | <br />
|-<br />
| style="border-bottom:1px dotted silver;" | MTA SZTAKI <br />
| style="border-bottom:1px dotted silver;" | HU <br />
| style="border-bottom:1px dotted silver;" | Sandor Acs <br />
| style="border-bottom:1px dotted silver;" | Peter Kotcauer, Gabor Kecskemeti <br />
| style="border-bottom:1px dotted silver;" | OpenNebula <br />
| style="border-bottom:1px dotted silver;" | <br />
|-<br />
| style="border-bottom:1px dotted silver;" | Cyfronet (NGI PL) <br />
| style="border-bottom:1px dotted silver;" | PL <br />
| style="border-bottom:1px dotted silver;" | Tomasz Szepieniec <br />
| style="border-bottom:1px dotted silver;" | Marcin Radecki, Jan Meizner <br />
| style="border-bottom:1px dotted silver;" | &nbsp;???? <br />
| style="border-bottom:1px dotted silver;" | <br />
|-<br />
| style="border-bottom:1px dotted silver;" | SURFsara <br />
| style="border-bottom:1px dotted silver;" | NL <br />
| style="border-bottom:1px dotted silver;" | Jhon Masschelein <br />
| style="border-bottom:1px dotted silver;" | Maurice Bouwhuis, Machiel Jansen <br />
| style="border-bottom:1px dotted silver;" | OpenNebula <br />
| style="border-bottom:1px dotted silver;" | <br />
|-<br />
| style="border-bottom:1px dotted silver;" | CRNS/IPHC <br />
| style="border-bottom:1px dotted silver;" | FR <br />
| style="border-bottom:1px dotted silver;" | Jérôme Pansanel <br />
| style="border-bottom:1px dotted silver;" | <br />
| style="border-bottom:1px dotted silver;" | <br />
| style="border-bottom:1px dotted silver;" | <br />
|-<br />
| style="border-bottom:1px dotted silver;" | ISRGrid/IUCC <br />
| style="border-bottom:1px dotted silver;" | IL <br />
| style="border-bottom:1px dotted silver;" | Yossi Baruch <br />
| style="border-bottom:1px dotted silver;" | <br />
| style="border-bottom:1px dotted silver;" | <br />
| style="border-bottom:1px dotted silver;" | <br />
|-<br />
| style="border-bottom:1px dotted silver;" | TUBITAK ULAKBIM <br />
| style="border-bottom:1px dotted silver;" | TR <br />
| style="border-bottom:1px dotted silver;" | Huseyin Cotuk <br />
| style="border-bottom:1px dotted silver;" | Feyza Eryol, Onur Temizsoylu <br />
| style="border-bottom:1px dotted silver;" | OpenStack <br />
| style="border-bottom:1px dotted silver;" | <br />
|-<br />
| style="border-bottom:1px dotted silver;" | DESY <br />
| style="border-bottom:1px dotted silver;" | DE <br />
| style="border-bottom:1px dotted silver;" | Patrick Furhmann <br />
| style="border-bottom:1px dotted silver;" | Paul Millar <br />
| style="border-bottom:1px dotted silver;" | dCache <br />
| style="border-bottom:1px dotted silver;" | Storage only<br />
|-<br />
| style="border-bottom:1px dotted silver;" | STFC/RAL <br />
| style="border-bottom:1px dotted silver;" | UK <br />
| style="border-bottom:1px dotted silver;" | Ian Collier <br />
| style="border-bottom:1px dotted silver;" | Frazer Barnsley, Alan Kyffin <br />
| style="border-bottom:1px dotted silver;" | <br />
| style="border-bottom:1px dotted silver;" | <br />
|-<br />
| style="border-bottom:1px dotted silver;" | STFC/RAL Harwell Science <br />
| style="border-bottom:1px dotted silver;" | UK <br />
| style="border-bottom:1px dotted silver;" | Jens Jensen <br />
| style="border-bottom:1px dotted silver;" | <br />
| style="border-bottom:1px dotted silver;" | Castor <br />
| style="border-bottom:1px dotted silver;" | Cloud storage only<br />
|-<br />
| style="border-bottom:1px dotted silver;" | UKIM <br />
| style="border-bottom:1px dotted silver;" | MK <br />
| style="border-bottom:1px dotted silver;" | Boro Jakimovski <br />
| style="border-bottom:1px dotted silver;" | <br />
| style="border-bottom:1px dotted silver;" | <br />
| style="border-bottom:1px dotted silver;" | <br />
|-<br />
| style="border-bottom:1px dotted silver;" | IFAE / PIC <br />
| style="border-bottom:1px dotted silver;" | ES <br />
| style="border-bottom:1px dotted silver;" | Victor Mendez <br />
| style="border-bottom:1px dotted silver;" | <br />
| style="border-bottom:1px dotted silver;" | <br />
| style="border-bottom:1px dotted silver;" | <br />
|-<br />
| style="border-bottom:1px dotted silver;" | SAGrid <br />
| style="border-bottom:1px dotted silver;" | ZA <br />
| style="border-bottom:1px dotted silver;" | Bruce Becker <br />
| style="border-bottom:1px dotted silver;" | <br />
| style="border-bottom:1px dotted silver;" | <br />
| style="border-bottom:1px dotted silver;" | <br />
|-<br />
| style="border-bottom:1px dotted silver;" | CSC <br />
| style="border-bottom:1px dotted silver;" | FI <br />
| style="border-bottom:1px dotted silver;" | Jura Tarus <br />
| style="border-bottom:1px dotted silver;" | Luís Alves, Ulf Tigerstedt, Kalle Happonen <br />
| style="border-bottom:1px dotted silver;" | OpenStack <br />
| style="border-bottom:1px dotted silver;" | Status: Testing resource integration<br />
|-<br />
| style="border-bottom:1px dotted silver;" | SRCE <br />
| style="border-bottom:1px dotted silver;" | HR <br />
| style="border-bottom:1px dotted silver;" | Emir Imamagic <br />
| style="border-bottom:1px dotted silver;" | <br />
| style="border-bottom:1px dotted silver;" | <br />
| style="border-bottom:1px dotted silver;" | <br />
|-<br />
| style="border-bottom:1px dotted silver;" | GridPP <br />
| style="border-bottom:1px dotted silver;" | UK <br />
| style="border-bottom:1px dotted silver;" | Adam Huffman <br />
| style="border-bottom:1px dotted silver;" | <br />
| style="border-bottom:1px dotted silver;" | OpenStack <br />
| style="border-bottom:1px dotted silver;" | Hosted at Imperial College<br />
|}<br />
<br />
=== Testbed ===<br />
<br />
More information about the Resource Providers belonging to the FedCloud Testbed are available [[Fedcloud-tf:Testbed|here]]. <br />
<br />
== Cloud Management Frameworks ==<br />
<br />
The federation of IaaS Cloud resources in EGI is built upon the extensive autonomy of Resource Providers in terms of ownership of exposed resources. The different cloud providers may have different Cloud Managemnt Frameworks (ex. OpenNebula, OpenStack, etc...), the federation implies only that the CMF exposes a set of [[Fedcloud-tf:Technology:Architecture|common interfaces]] (ex. [[Fedcloud-tf:Technology:Architecture#VM_management_interface:_OCCI|OCCI for VM management]], [[Fedcloud-tf:Technology:Architecture#Data_management_interface:_CDMI|CDMI for Data management]], etc...) <br />
<br />
More in-depth information about the EGI Federated Cloud architecture and technology is provided [[Fedcloud-tf:Technology|here]]. <br />
<br />
=== Compatible CMFs ===<br />
<br />
The table below provides a list of the most famous CMFs and the status of the support of the EGI Federated Cloud interfaces. <br />
<br />
{| class="wikitable"<br />
|-<br />
! Cloud Mgmt. Fram. <br />
! Fed. AAI <br />
! Monitoring<ref>Monitoring happens passive, i.e. no active integration from the side of Cloud Management Frameworks necessary.</ref> <br />
! Accounting <br />
! Img. Mgmt. <br />
! OCCI <br />
! CDMI<br />
|-<br />
! OpenStack <br />
| Yes <br />
| Yes <br />
| Yes <br />
| Yes <br />
| Yes <br />
| Yes<br />
|-<br />
! OpenNebula <br />
| Yes <br />
| Yes <br />
| Yes <br />
| Yes <br />
| Yes <br />
| Yes<br />
|-<br />
! StratusLab <br />
| Yes <br />
| Yes <br />
| Yes <br />
| - <br />
| Yes<ref>StratusLab’s OCCI support is based on OpenNebula. Since StratusLab will discontinue its integration with OpenNebula (see below), the future of StratusLab OCCI interface is unknown at this point in time.</ref> <br />
| -<br />
|-<br />
! WNoDeS <br />
| Yes <br />
| Yes <br />
| Yes <br />
| - <br />
| - <br />
| -<br />
|-<br />
! Synnefo <br />
| Yes <br />
| Yes <br />
| - <br />
| - <br />
| Yes <br />
| -<br />
|}<br />
<br />
== Deployment ==<br />
<br />
Guides for deployment of the FedCloud interfaces for the most used Cloud Management Frameworks are reported below: <br />
<br />
*[[Fedcloud-tf:ResourceProviders:OpenNebula|OpenNebula]] <br />
*[[Fedcloud-tf:ResourceProviders:OpenStack|OpenStack]] <br />
*[[Fedcloud-tf:ResourceProviders:StratusLab|StratusLab]] <br />
*[[Fedcloud-tf:ResourceProviders:WNoDeS|WNoDeS]] <br />
*[[Fedcloud-tf:ResourceProviders:Synnefo|Synnefo]]<br />
<br />
== References ==<br />
<br />
<references /></div>
Asimon
https://wiki.egi.eu/w/index.php?title=Fedcloud-tf:ResourceProviders&diff=65290
Fedcloud-tf:ResourceProviders
2014-03-04T07:25:48Z
<p>Asimon: </p>
<hr />
<div>{{Fedcloud-tf:Menu}} {{TOC_right}} <br />
<br />
== EGI Federated Cloud Resource Providers ==<br />
<br />
EGI Federated Cloud resource providers are institutions and companies that contribute to the FedCloud providing access to their cloud infrastructure via the Federation. Resource providers are free to use any Cloud Manafement Framework (OpenNebula, OpenStack, etc...), the only requirement is that the CMF exposes interfaces compliant to the [[Fedcloud-tf:Technology:Architecture|FedCloud standards]]. <br />
<br />
== Join as a Resource Provider ==<br />
<br />
Every institution and company is invited to join the EGI Federated Cloud. The members of the EGI Federated Cloud have also the opportunity to join the [[Fedcloud-tf:FederatedCloudsTaskForce|EGI Federated Cloud Task Force]], contributing directly to the creation and implementation of the clouds federation. <br />
<br />
If you want to join the EGI Federated Cloud, you can send en email to the [mailto:fedcloud-tf@mailman.egi.eu EGI Federated Cloud Task Force], specifying the following information (fields with * are mandatory) <br />
<br />
*Name* <br />
*Institute* <br />
*Email address* <br />
*One paragraph long description of your organization <br />
*Envisaged timeline (is there a deadline to finish the setup? for how long do you wish to contribute to the EGI Federated project?) <br />
*Estimated number and size of machines that you may provide to EGI <br />
*Type of Cloud Management Framework you are using <br />
*Link to webpage, document or other online resource for further information<br />
<br />
== Current Resource Providers ==<br />
<br />
=== Fully integrated Resource Providers ===<br />
<br />
Reporting period: 1 Jan 2014 - 31 Jan 2014 <br />
<br />
{| width="150%" cellspacing="0" cellpadding="5" style="border:1px solid black; text-align:left;" class="wikitable"<br />
|- style="background:lightgray;"<br />
! style="border-bottom:1px solid black;" | Affiliation <br />
! style="border-bottom:1px solid black;" | CC <br />
! style="border-bottom:1px solid black;" | Main contact <br />
! style="border-bottom:1px solid black;" | Deputies <br />
! style="border-bottom:1px solid black;" | Host Site <br />
! style="border-bottom:1px solid black;" | CMF <br />
! style="border-bottom:1px solid black;" | Certification <br />
! style="border-bottom:1px solid black;" | Resource Endpoints <br />
! style="border-bottom:1px solid black;" | Nagios Avail. (avg.) <br />
! style="border-bottom:1px solid black;" | Comment<br />
|-<br />
| style="border-bottom:1px dotted silver;" | 100 Percent IT Ltd <br />
| style="border-bottom:1px dotted silver;" | UK <br />
| style="border-bottom:1px dotted silver;" | David Blundell <br />
| style="border-bottom:1px dotted silver;" | <br />
| style="border-bottom:1px dotted silver;" | 100IT <br />
| style="border-bottom:1px dotted silver;" | OpenStack <br />
| bgcolor="lime" style="border-bottom:1px dotted silver;" | certified <br />
| style="border-bottom:1px dotted silver;" | OCCI - occi-api.100percentit.com <br />
| bgcolor="#33ff00" style="border-bottom:1px dotted silver;" | 96% <br />
| style="border-bottom:1px dotted silver;" | "(Return code of 127 is out of bounds - plugin may be missing)"<br />
|-<br />
| style="border-bottom:1px dotted silver;" | UNIZAR / BIFI <br />
| style="border-bottom:1px dotted silver;" | ES <br />
| style="border-bottom:1px dotted silver;" | Ruben Valles <br />
| style="border-bottom:1px dotted silver;" | Jaime Ibar Yubero <br />
| style="border-bottom:1px dotted silver;" | BIFI <br />
| style="border-bottom:1px dotted silver;" | OpenStack <br />
| bgcolor="lime" style="border-bottom:1px dotted silver;" | [https://ggus.eu/ws/ticket_info.php?ticket=100239 certified] <br />
| style="border-bottom:1px dotted silver;" | OCCI - server4-epsh.unizar.es <br />
| style="border-bottom:1px dotted silver;" | 11% <br />
| style="border-bottom:1px dotted silver;" | Service 95% plus available/stable since 26 January.<br />
|-<br />
| style="border-bottom:1px dotted silver;" | BSC <br />
| style="border-bottom:1px dotted silver;" | ES <br />
| style="border-bottom:1px dotted silver;" | Daniele Lezzi <br />
| style="border-bottom:1px dotted silver;" | Roger Rafanell <br />
| style="border-bottom:1px dotted silver;" | BSC-Cloud <br />
| style="border-bottom:1px dotted silver;" | Emotive <br />
| style="border-bottom:1px dotted silver;" | <br />
| style="border-bottom:1px dotted silver;" | CDMI - bscgrid05.bsc.es <br />
| bgcolor="lime" style="border-bottom:1px dotted silver;" | 100% <br />
| style="border-bottom:1px dotted silver;" | CDMI-TCP ping probe only<br />
|-<br />
| style="border-bottom:1px dotted silver;" | FCTSG <br />
| style="border-bottom:1px dotted silver;" | ES <br />
| style="border-bottom:1px dotted silver;" | Alvaro Simon <br />
| style="border-bottom:1px dotted silver;" | Ivan Diaz Alvarez <br />
| style="border-bottom:1px dotted silver;" | CESGA <br />
| style="border-bottom:1px dotted silver;" | OpenNebula <br />
| bgcolor="lime" style="border-bottom:1px dotted silver;" rowspan="2" | [https://ggus.eu/ws/ticket_info.php?ticket=100948 certified] <br />
| style="border-bottom:1px dotted silver;" | OCCI - cloud.cesga.es <br />
| bgcolor="yellow" style="border-bottom:1px dotted silver;" | 81% <br />
| style="border-bottom:1px dotted silver;" | Spotty service around 7,8,9 January, outage 23-27 January<br />
|-<br />
| style="border-bottom:1px dotted silver;" rowspan="2" | CESNET <br />
| style="border-bottom:1px dotted silver;" rowspan="2" | CZ <br />
| style="border-bottom:1px dotted silver;" rowspan="2" | Miroslav Ruda <br />
| style="border-bottom:1px dotted silver;" rowspan="2" | Boris Parak <br />
| style="border-bottom:1px dotted silver;" rowspan="2" | CESNET-MetaCloud <br />
| style="border-bottom:1px dotted silver;" rowspan="2" | OpenNebula <br />
| bgcolor="lime" style="border-bottom:1px dotted silver;" rowspan="2" | [https://ggus.eu/ws/ticket_info.php?ticket=101197 certified] <br />
| style="border-bottom:1px dotted silver;" | OCCI - carach5.ics.muni.cz <br />
| bgcolor="lime" style="border-bottom:1px dotted silver;" | 87% <br />
| style="border-bottom:1px dotted silver;" | Outages 3, 4 January &amp; 25-27 January<br />
|-<br />
| style="border-bottom:1px dotted silver;" | CDMI - carach3.ics.muni.cz <br />
| bgcolor="lime" style="border-bottom:1px dotted silver;" | 100% <br />
| style="border-bottom:1px dotted silver;" | CDMI-TCP ping probe only<br />
|-<br />
| style="border-bottom:1px dotted silver;" rowspan="2" | FZ Jülich <br />
| style="border-bottom:1px dotted silver;" rowspan="2" | DE <br />
| style="border-bottom:1px dotted silver;" rowspan="2" | Björn Hagemeier <br />
| style="border-bottom:1px dotted silver;" rowspan="2" | Shahbaz Memon <br />
| style="border-bottom:1px dotted silver;" rowspan="2" | FZJ <br />
| style="border-bottom:1px dotted silver;" rowspan="2" | OpenStack <br />
| style="border-bottom:1px dotted silver;" rowspan="2" | <br />
| style="border-bottom:1px dotted silver;" | OCCI - egi-cloud.zam.kfa-juelich.de <br />
| bgcolor="lime" style="border-bottom:1px dotted silver;" | 99% <br />
| style="border-bottom:1px dotted silver;" | 31 January scheduled downtime.<br />
|-<br />
| style="border-bottom:1px dotted silver;" | CDMI - swift.zam.kfa-juelich.de <br />
| bgcolor="lime" style="border-bottom:1px dotted silver;" | 100% <br />
| style="border-bottom:1px dotted silver;" | CDMI TCP probe only. 31 January scheduled downtime.<br />
|-<br />
| style="border-bottom:1px dotted silver;" | CRNS/IN2P3-LAL <br />
| style="border-bottom:1px dotted silver;" | FR <br />
| style="border-bottom:1px dotted silver;" | Michel Jouvin <br />
| style="border-bottom:1px dotted silver;" | Mohammed Araj <br />
| style="border-bottom:1px dotted silver;" | GRIF <br />
| style="border-bottom:1px dotted silver;" | StratusLab <br />
| style="border-bottom:1px dotted silver;" | <br />
| style="border-bottom:1px dotted silver;" | OCCI - onehost-2.lal.in2p3.fr <br />
| style="border-bottom:1px dotted silver;" | 0% <br />
| style="border-bottom:1px dotted silver;" | SAM fails to instantiate VMs: "probe instantiation failed: "/usr/local/bin/VMInstantiation-probe:main:::418] Started probe 'VMInstantiation-probe'..."<br />
|-<br />
| style="border-bottom:1px dotted silver;" rowspan="2" | GWDG <br />
| style="border-bottom:1px dotted silver;" rowspan="2" | DE <br />
| style="border-bottom:1px dotted silver;" rowspan="2" | Piotr Kasprzak <br />
| style="border-bottom:1px dotted silver;" rowspan="2" | Ramin Yahyapour, Philipp Wieder <br />
| style="border-bottom:1px dotted silver;" rowspan="2" | GoeGrid <br />
| style="border-bottom:1px dotted silver;" rowspan="2" | OpenNebula <br />
| style="border-bottom:1px dotted silver;" rowspan="2" | scheduled <br />
| style="border-bottom:1px dotted silver;" | OCCI - occi.cloud.gwdg.de <br />
| bgcolor="yellow" style="border-bottom:1px dotted silver;" | 83% <br />
| style="border-bottom:1px dotted silver;" | Outage 23-28 January.<br />
|-<br />
| style="border-bottom:1px dotted silver;" | CDMI - cdmi.cloud.gwdg.de <br />
| bgcolor="lime" style="border-bottom:1px dotted silver;" | 100% <br />
| style="border-bottom:1px dotted silver;" | CDMI TCP probe only.<br />
|-<br />
| style="border-bottom:1px dotted silver;" | CSIC/IFCA <br />
| style="border-bottom:1px dotted silver;" | ES <br />
| style="border-bottom:1px dotted silver;" | Alvaro Lopez Garcia <br />
| style="border-bottom:1px dotted silver;" | Enol Fernandez, Pablo Orviz <br />
| style="border-bottom:1px dotted silver;" | IFCA-LCG2 <br />
| style="border-bottom:1px dotted silver;" | OpenStack <br />
| bgcolor="lime" style="border-bottom:1px dotted silver;" | [https://ggus.eu/index.php?mode=ticket_info&ticket_id=100990 certified] <br />
| style="border-bottom:1px dotted silver;" | OCCI - cloud.ifca.es <br />
| bgcolor="yellow" style="border-bottom:1px dotted silver;" | 69% <br />
| style="border-bottom:1px dotted silver;" | Spotty service, improved much after service downtime on 15 January.<br />
|-<br />
| style="border-bottom:1px dotted silver;" | II SAS <br />
| style="border-bottom:1px dotted silver;" | SK <br />
| style="border-bottom:1px dotted silver;" | Viet Tran <br />
| style="border-bottom:1px dotted silver;" | Martin Bobak <br />
| style="border-bottom:1px dotted silver;" | IISAS-FedCloud <br />
| style="border-bottom:1px dotted silver;" | OpenStack <br />
| style="border-bottom:1px dotted silver;" | scheduled <br />
| style="border-bottom:1px dotted silver;" | OCCI - nova.ui.savba.sk <br />
| bgcolor="lime" style="border-bottom:1px dotted silver;" | 90% <br />
| style="border-bottom:1px dotted silver;" | Occasional outage. Structural outage 24 - 27 January<br />
|-<br />
| style="border-bottom:1px dotted silver;" | INFN - Catania <br />
| style="border-bottom:1px dotted silver;" | IT <br />
| style="border-bottom:1px dotted silver;" | Roberto Barbera <br />
| style="border-bottom:1px dotted silver;" | Giuseppe Larocca, Maurizio Paone, Diego Scardacci <br />
| style="border-bottom:1px dotted silver;" | INFN-CATANIA-STACK <br />
| style="border-bottom:1px dotted silver;" | OpenStack <br />
| style="border-bottom:1px dotted silver;" | <br />
| style="border-bottom:1px dotted silver;" | OCCI - stack-server-01.ct.infn.it <br />
| style="border-bottom:1px dotted silver;" | 0% <br />
| style="border-bottom:1px dotted silver;" | Service critical, but probe reports no failure?<br />
|-<br />
| style="border-bottom:1px dotted silver;" | KTH <br />
| style="border-bottom:1px dotted silver;" | SE <br />
| style="border-bottom:1px dotted silver;" | Zeeshan Ali Shah <br />
| style="border-bottom:1px dotted silver;" | Ake Edlund <br />
| style="border-bottom:1px dotted silver;" | KTH-CLOUD <br />
| style="border-bottom:1px dotted silver;" | OpenNebula <br />
| bgcolor="lime" style="border-bottom:1px dotted silver;" | [https://ggus.eu/ws/ticket_info.php?ticket=101028 certified] <br />
| style="border-bottom:1px dotted silver;" | OCCI - egi.cloud.pdc.kth.se <br />
| bgcolor="lime" style="border-bottom:1px dotted silver;" | 99% <br />
| style="border-bottom:1px dotted silver;" | One outage on 25 January<br />
|-<br />
| style="border-bottom:1px dotted silver;" | INFN - Bari <br />
| style="border-bottom:1px dotted silver;" | IT <br />
| style="border-bottom:1px dotted silver;" | Marica Antonacci <br />
| style="border-bottom:1px dotted silver;" | Giacinto Donvito, Stefano Nicotri, Vincenzo Spinoso <br />
| style="border-bottom:1px dotted silver;" | PRISMA-INFN-BARI <br />
| style="border-bottom:1px dotted silver;" | OpenStack <br />
| style="border-bottom:1px dotted silver;" | <br />
| style="border-bottom:1px dotted silver;" | OCCI - prisma-cloud.ba.infn.it <br />
| bgcolor="lime" style="border-bottom:1px dotted silver;" | 92% <br />
| style="border-bottom:1px dotted silver;" | Patchy service, occasional outages on 14, 15, 16 &amp; 22 January<br />
|}<br />
<br />
=== Integrating Resource Providers ===<br />
<br />
Reporting period: 1 Jan 2014 - 31 Jan 2014 <br />
<br />
{| width="120%" cellspacing="0" cellpadding="5" style="border:1px solid black; text-align:left;" class="wikitable sortable"<br />
|- style="background:lightgray;"<br />
! style="border-bottom:1px solid black;" | Affiliation <br />
! style="border-bottom:1px solid black;" | CC <br />
! style="border-bottom:1px solid black;" | Representative <br />
! style="border-bottom:1px solid black;" | Deputies <br />
! style="border-bottom:1px solid black;" | Host Site <br />
! style="border-bottom:1px solid black;" | CMF <br />
! style="border-bottom:1px solid black;" | Certification <br />
! style="border-bottom:1px solid black;" | Resource Endpoints <br />
! style="border-bottom:1px solid black;" | Status (avg.) <br />
! style="border-bottom:1px solid black;" | Comment<br />
|-<br />
| style="border-bottom:1px dotted silver;" | GRNET <br />
| style="border-bottom:1px dotted silver;" | GR <br />
| style="border-bottom:1px dotted silver;" | Kostas Koumantaros <br />
| style="border-bottom:1px dotted silver;" | Athanasia Assiki <br />
| style="border-bottom:1px dotted silver;" | HG-09-Okeanos-Cloud <br />
| style="border-bottom:1px dotted silver;" | Synnefo <br />
| style="border-bottom:1px dotted silver;" | Scheduled <br />
| style="border-bottom:1px dotted silver;" | OCCI - okeanos-occi2.hellasgrid.gr <br />
| bgcolor="yellow" style="border-bottom:1px dotted silver;" | 75% <br />
| style="border-bottom:1px dotted silver;" | Partial monitoring (no accounting). Regular service outages, reason not known (no probe failure reported)<br />
|-<br />
| style="border-bottom:1px dotted silver;" | CRNS/IN2P3-CC <br />
| style="border-bottom:1px dotted silver;" | FR <br />
| style="border-bottom:1px dotted silver;" | Gilles MATHIEU <br />
| style="border-bottom:1px dotted silver;" | Mattieu Puel <br />
| style="border-bottom:1px dotted silver;" | IN2P3-CC <br />
| style="border-bottom:1px dotted silver;" | OpenStack <br />
| style="border-bottom:1px dotted silver;" | <br />
| style="border-bottom:1px dotted silver;" | OCCI - ccocci.in2p3.fr <br />
| style="border-bottom:1px dotted silver;" | 0% <br />
| style="border-bottom:1px dotted silver;" | Probe seem to run normally but reports consistent failure?<br />
|}<br />
<br />
=== Interested Resource Providers ===<br />
<br />
{| cellspacing="0" cellpadding="5" style="border:1px solid black; text-align:left;" class="wikitable sortable"<br />
|- style="background:lightgray;"<br />
! style="border-bottom:1px solid black;" | Affiliation <br />
! style="border-bottom:1px solid black;" | CC <br />
! style="border-bottom:1px solid black;" | Representative <br />
! style="border-bottom:1px solid black;" | Deputies <br />
! style="border-bottom:1px solid black;" | CMF <br />
! style="border-bottom:1px solid black;" | Comment<br />
|-<br />
| style="border-bottom:1px dotted silver;" | KISTI <br />
| style="border-bottom:1px dotted silver;" | KR <br />
| style="border-bottom:1px dotted silver;" | Soonwook Hwang <br />
| style="border-bottom:1px dotted silver;" | Sangwan Kim, Taesang Huh, Jae-Hyuck Kwak <br />
| style="border-bottom:1px dotted silver;" | OpenStack <br />
| style="border-bottom:1px dotted silver;" | <br />
|-<br />
| style="border-bottom:1px dotted silver;" | IICT-BAS <br />
| style="border-bottom:1px dotted silver;" | BG <br />
| style="border-bottom:1px dotted silver;" | Emanouil Atanassov <br />
| style="border-bottom:1px dotted silver;" | Todor Gurov <br />
| style="border-bottom:1px dotted silver;" | OpenStack <br />
| style="border-bottom:1px dotted silver;" | <br />
|-<br />
| style="border-bottom:1px dotted silver;" | INFN - Napoli <br />
| style="border-bottom:1px dotted silver;" | IT <br />
| style="border-bottom:1px dotted silver;" | Silvio Pardi <br />
| style="border-bottom:1px dotted silver;" | <br />
| style="border-bottom:1px dotted silver;" | OpenStack <br />
| style="border-bottom:1px dotted silver;" | <br />
|-<br />
| style="border-bottom:1px dotted silver;" | INFN - CNAF <br />
| style="border-bottom:1px dotted silver;" | IT <br />
| style="border-bottom:1px dotted silver;" | Elisabetta Ronchieri <br />
| style="border-bottom:1px dotted silver;" | Davide Salomoni, Andrea Cristofori <br />
| style="border-bottom:1px dotted silver;" | OpenStack <br />
| style="border-bottom:1px dotted silver;" | <br />
|-<br />
| style="border-bottom:1px dotted silver;" | INFN - Torino <br />
| style="border-bottom:1px dotted silver;" | IT <br />
| style="border-bottom:1px dotted silver;" | Andrea Guarise <br />
| style="border-bottom:1px dotted silver;" | <br />
| style="border-bottom:1px dotted silver;" | OpenStack <br />
| style="border-bottom:1px dotted silver;" | <br />
|-<br />
| style="border-bottom:1px dotted silver;" | INFN - Padova <br />
| style="border-bottom:1px dotted silver;" | IT <br />
| style="border-bottom:1px dotted silver;" | Marco Verlato <br />
| style="border-bottom:1px dotted silver;" | Eric Frizziero <br />
| style="border-bottom:1px dotted silver;" | OpenStack <br />
| style="border-bottom:1px dotted silver;" | <br />
|-<br />
| style="border-bottom:1px dotted silver;" | CETA-CIEMAT <br />
| style="border-bottom:1px dotted silver;" | ES <br />
| style="border-bottom:1px dotted silver;" | Guillermo Díaz Herrero, <br />
| style="border-bottom:1px dotted silver;" | Miguel Ángel Díaz, Abel Paz <br />
| style="border-bottom:1px dotted silver;" | OpenStack <br />
| style="border-bottom:1px dotted silver;" | <br />
|-<br />
| style="border-bottom:1px dotted silver;" | MTA SZTAKI <br />
| style="border-bottom:1px dotted silver;" | HU <br />
| style="border-bottom:1px dotted silver;" | Sandor Acs <br />
| style="border-bottom:1px dotted silver;" | Peter Kotcauer, Gabor Kecskemeti <br />
| style="border-bottom:1px dotted silver;" | OpenNebula <br />
| style="border-bottom:1px dotted silver;" | <br />
|-<br />
| style="border-bottom:1px dotted silver;" | Cyfronet (NGI PL) <br />
| style="border-bottom:1px dotted silver;" | PL <br />
| style="border-bottom:1px dotted silver;" | Tomasz Szepieniec <br />
| style="border-bottom:1px dotted silver;" | Marcin Radecki, Jan Meizner <br />
| style="border-bottom:1px dotted silver;" | &nbsp;???? <br />
| style="border-bottom:1px dotted silver;" | <br />
|-<br />
| style="border-bottom:1px dotted silver;" | SURFsara <br />
| style="border-bottom:1px dotted silver;" | NL <br />
| style="border-bottom:1px dotted silver;" | Jhon Masschelein <br />
| style="border-bottom:1px dotted silver;" | Maurice Bouwhuis, Machiel Jansen <br />
| style="border-bottom:1px dotted silver;" | OpenNebula <br />
| style="border-bottom:1px dotted silver;" | <br />
|-<br />
| style="border-bottom:1px dotted silver;" | CRNS/IPHC <br />
| style="border-bottom:1px dotted silver;" | FR <br />
| style="border-bottom:1px dotted silver;" | Jérôme Pansanel <br />
| style="border-bottom:1px dotted silver;" | <br />
| style="border-bottom:1px dotted silver;" | <br />
| style="border-bottom:1px dotted silver;" | <br />
|-<br />
| style="border-bottom:1px dotted silver;" | ISRGrid/IUCC <br />
| style="border-bottom:1px dotted silver;" | IL <br />
| style="border-bottom:1px dotted silver;" | Yossi Baruch <br />
| style="border-bottom:1px dotted silver;" | <br />
| style="border-bottom:1px dotted silver;" | <br />
| style="border-bottom:1px dotted silver;" | <br />
|-<br />
| style="border-bottom:1px dotted silver;" | TUBITAK ULAKBIM <br />
| style="border-bottom:1px dotted silver;" | TR <br />
| style="border-bottom:1px dotted silver;" | Huseyin Cotuk <br />
| style="border-bottom:1px dotted silver;" | Feyza Eryol, Onur Temizsoylu <br />
| style="border-bottom:1px dotted silver;" | OpenStack <br />
| style="border-bottom:1px dotted silver;" | <br />
|-<br />
| style="border-bottom:1px dotted silver;" | DESY <br />
| style="border-bottom:1px dotted silver;" | DE <br />
| style="border-bottom:1px dotted silver;" | Patrick Furhmann <br />
| style="border-bottom:1px dotted silver;" | Paul Millar <br />
| style="border-bottom:1px dotted silver;" | dCache <br />
| style="border-bottom:1px dotted silver;" | Storage only<br />
|-<br />
| style="border-bottom:1px dotted silver;" | STFC/RAL <br />
| style="border-bottom:1px dotted silver;" | UK <br />
| style="border-bottom:1px dotted silver;" | Ian Collier <br />
| style="border-bottom:1px dotted silver;" | Frazer Barnsley, Alan Kyffin <br />
| style="border-bottom:1px dotted silver;" | <br />
| style="border-bottom:1px dotted silver;" | <br />
|-<br />
| style="border-bottom:1px dotted silver;" | STFC/RAL Harwell Science <br />
| style="border-bottom:1px dotted silver;" | UK <br />
| style="border-bottom:1px dotted silver;" | Jens Jensen <br />
| style="border-bottom:1px dotted silver;" | <br />
| style="border-bottom:1px dotted silver;" | Castor <br />
| style="border-bottom:1px dotted silver;" | Cloud storage only<br />
|-<br />
| style="border-bottom:1px dotted silver;" | UKIM <br />
| style="border-bottom:1px dotted silver;" | MK <br />
| style="border-bottom:1px dotted silver;" | Boro Jakimovski <br />
| style="border-bottom:1px dotted silver;" | <br />
| style="border-bottom:1px dotted silver;" | <br />
| style="border-bottom:1px dotted silver;" | <br />
|-<br />
| style="border-bottom:1px dotted silver;" | IFAE / PIC <br />
| style="border-bottom:1px dotted silver;" | ES <br />
| style="border-bottom:1px dotted silver;" | Victor Mendez <br />
| style="border-bottom:1px dotted silver;" | <br />
| style="border-bottom:1px dotted silver;" | <br />
| style="border-bottom:1px dotted silver;" | <br />
|-<br />
| style="border-bottom:1px dotted silver;" | SAGrid <br />
| style="border-bottom:1px dotted silver;" | ZA <br />
| style="border-bottom:1px dotted silver;" | Bruce Becker <br />
| style="border-bottom:1px dotted silver;" | <br />
| style="border-bottom:1px dotted silver;" | <br />
| style="border-bottom:1px dotted silver;" | <br />
|-<br />
| style="border-bottom:1px dotted silver;" | CSC <br />
| style="border-bottom:1px dotted silver;" | FI <br />
| style="border-bottom:1px dotted silver;" | Jura Tarus <br />
| style="border-bottom:1px dotted silver;" | Luís Alves, Ulf Tigerstedt, Kalle Happonen <br />
| style="border-bottom:1px dotted silver;" | OpenStack <br />
| style="border-bottom:1px dotted silver;" | Status: Testing resource integration<br />
|-<br />
| style="border-bottom:1px dotted silver;" | SRCE <br />
| style="border-bottom:1px dotted silver;" | HR <br />
| style="border-bottom:1px dotted silver;" | Emir Imamagic <br />
| style="border-bottom:1px dotted silver;" | <br />
| style="border-bottom:1px dotted silver;" | <br />
| style="border-bottom:1px dotted silver;" | <br />
|-<br />
| style="border-bottom:1px dotted silver;" | GridPP <br />
| style="border-bottom:1px dotted silver;" | UK <br />
| style="border-bottom:1px dotted silver;" | Adam Huffman <br />
| style="border-bottom:1px dotted silver;" | <br />
| style="border-bottom:1px dotted silver;" | OpenStack <br />
| style="border-bottom:1px dotted silver;" | Hosted at Imperial College<br />
|}<br />
<br />
=== Testbed ===<br />
<br />
More information about the Resource Providers belonging to the FedCloud Testbed are available [[Fedcloud-tf:Testbed|here]]. <br />
<br />
== Cloud Management Frameworks ==<br />
<br />
The federation of IaaS Cloud resources in EGI is built upon the extensive autonomy of Resource Providers in terms of ownership of exposed resources. The different cloud providers may have different Cloud Managemnt Frameworks (ex. OpenNebula, OpenStack, etc...), the federation implies only that the CMF exposes a set of [[Fedcloud-tf:Technology:Architecture|common interfaces]] (ex. [[Fedcloud-tf:Technology:Architecture#VM_management_interface:_OCCI|OCCI for VM management]], [[Fedcloud-tf:Technology:Architecture#Data_management_interface:_CDMI|CDMI for Data management]], etc...) <br />
<br />
More in-depth information about the EGI Federated Cloud architecture and technology is provided [[Fedcloud-tf:Technology|here]]. <br />
<br />
=== Compatible CMFs ===<br />
<br />
The table below provides a list of the most famous CMFs and the status of the support of the EGI Federated Cloud interfaces. <br />
<br />
{| class="wikitable"<br />
|-<br />
! Cloud Mgmt. Fram. <br />
! Fed. AAI <br />
! Monitoring<ref>Monitoring happens passive, i.e. no active integration from the side of Cloud Management Frameworks necessary.</ref> <br />
! Accounting <br />
! Img. Mgmt. <br />
! OCCI <br />
! CDMI<br />
|-<br />
! OpenStack <br />
| Yes <br />
| Yes <br />
| Yes <br />
| Yes <br />
| Yes <br />
| Yes<br />
|-<br />
! OpenNebula <br />
| Yes <br />
| Yes <br />
| Yes <br />
| Yes <br />
| Yes <br />
| Yes<br />
|-<br />
! StratusLab <br />
| Yes <br />
| Yes <br />
| Yes <br />
| - <br />
| Yes<ref>StratusLab’s OCCI support is based on OpenNebula. Since StratusLab will discontinue its integration with OpenNebula (see below), the future of StratusLab OCCI interface is unknown at this point in time.</ref> <br />
| -<br />
|-<br />
! WNoDeS <br />
| Yes <br />
| Yes <br />
| Yes <br />
| - <br />
| - <br />
| -<br />
|-<br />
! Synnefo <br />
| Yes <br />
| Yes <br />
| - <br />
| - <br />
| Yes <br />
| -<br />
|}<br />
<br />
== Deployment ==<br />
<br />
Guides for deployment of the FedCloud interfaces for the most used Cloud Management Frameworks are reported below: <br />
<br />
*[[Fedcloud-tf:ResourceProviders:OpenNebula|OpenNebula]] <br />
*[[Fedcloud-tf:ResourceProviders:OpenStack|OpenStack]] <br />
*[[Fedcloud-tf:ResourceProviders:StratusLab|StratusLab]] <br />
*[[Fedcloud-tf:ResourceProviders:WNoDeS|WNoDeS]] <br />
*[[Fedcloud-tf:ResourceProviders:Synnefo|Synnefo]]<br />
<br />
== References ==<br />
<br />
<references /></div>
Asimon
https://wiki.egi.eu/w/index.php?title=VT_EGI_Pay-for-Use_Technical_Details&diff=64496
VT EGI Pay-for-Use Technical Details
2014-02-11T17:20:41Z
<p>Asimon: </p>
<hr />
<div>{{Template:EGI-PayForUse-PoC_menubar}} {{TOC right}} <br />
<br />
The following table provides an overview of the technical details of the resource and technology providers for the PoC. <br />
<br />
Further below are instructions for adding pricing into the accounting mechanisms. <br />
<br />
[1] All prices provided are interpreted as Euro per HEPSPEC06 hour. <br />
<br />
= Resource Providers, Services and Prices =<br />
<br />
{| class="wikitable"<br />
|-<br />
! scope="col" | NGI/RC <br />
! scope="col" | GOCDB Name <br />
! scope="col" | Contact <br />
! scope="col" | Service Type <br />
! scope="col" | Services and Resources <br />
! scope="col" | Preferred Payment Direct/Indirect <br />
! scope="col" | Price [1]<br />
|-<br />
! scope="row" | Albert Einstein Center, Univ. of Bern <br />
| UNIBE-LHEP <br />
| <br />
| Batch via CENTOS 5/6 ARC CE <br> <br />
| <br />
*500 cores (approx. 2 months in 2013) on highest priority; <br />
*Consumption preferably in one go, but distributed in time also possible <br />
*10-20 TB disk on local SE for consumption period via DPM SRM interface plus two weeks<br />
<br />
| Both <br />
| €0.03/hr; Storage free<br />
|-<br />
! scope="row" | Bulgaria Grid Portal <br />
| BG08-Madara <br />
| <br />
| TBC <br />
| <br />
*TBC<br />
<br />
| TBC <br />
| TBC<br />
|-<br />
! scope="row" | CESGA-IBERGRID <br />
| CESGA <br />
| <br />
| Batch + Cloud <br />
| <br />
*720 cores (Batch) AMD Opteron(tm) Processor 6174 2.2Ghz <br />
*240 cores (Cloud) Intel(R) Xeon(R) CPU E5520 2.27GHz <br />
*MPI jobs <br />
*RAM from 4GB to 32GB per core<br />
<br />
| Direct <br />
| <br />
€0.02/core/HEPSPEC06 hour <br />
<br />
|-<br />
! scope="row" | IFCA-IBERGRID <br />
| TBD <br />
| <br />
| Batch (SLURM, SGE) or Cloud (FedCloud soon) <br />
| <br />
*Up to 2500 cores in servers with 4, 8, 16, 40 physical cores <br />
*Infiniband access to other nodes and storage possible for MPI jobs <br />
*RAM from 4GB to 256GB per core (max 1TB)<br />
<br />
| Direct <br />
| <br />
€0.05/core/hour for usual instances <br />
<br />
<span style="line-height: 1.5em;">€0.04/core/hour for multicore use (&gt;128 cores)</span> <br />
<br />
<span style="line-height: 1.5em;">Minimal storage free, requests up to 100 TB high performance storage possible</span> <br />
<br />
|-<br />
! scope="row" | Institute of Informatics of the Slovak Academy of Sciences <br />
| IISAS-FedCloud <br />
| <br />
| Cloud <br />
| <br />
*TBC<br />
<br />
| TBC <br />
| TBC<br />
|-<br />
! scope="row" | Latvian Grid <br />
| IMCSUL <br />
| <br />
| TBC <br />
| <br />
*TBC<br />
<br />
| TBC <br />
| TBC<br />
|-<br />
! scope="row" | Leibniz SC Centre <br />
| LRZ <br />
| <br />
| Globus <br />
| <br />
*Linux Cluster through Globus: GRAM5, GridFTP, Gsissh<br />
<br />
| Indirect <br />
| Price and capacity to be detailed later<br />
|-<br />
! scope="row" | MASTER-UP Srl <br />
| TBC <br />
| <br />
| EMI1/2, CEs, WNs, SE <br />
| <br />
*EMI1 middleware (phasing to EMI2) - CE's, WN's and SE. <br />
*10 nodes to start (intel 4core, ethernet connection) <br />
*Long experience in Molecular Science and Comp Chem, can provide support for such innovative applications and in the field of R&amp;D for combustion, energy and material science. <br />
*Managing a computer farm of 200 cores and 4TB of storage part of those resources are supporting EGI.<br />
<br />
| Direct <br />
| To be evaluated<br />
|-<br />
! scope="row" | NGI-DE <br />
| TBC <br />
| <br />
| UNICORE <br />
| <br />
*Cluster via UNICORE <br />
*Others can be offered (TBD)<br />
<br />
| Both <br />
| €0.06/hr + 19% VAT<br />
|-<br />
! scope="row" | NGI_GRNET <br />
| All HG-* <br />
| <br />
| Cloud and Grid <br />
| <br />
*TBC<br />
<br />
| TBC <br />
| €0.05/hr + 23% VAT<br />
|-<br />
! scope="row" | NGI-IT <br />
| TBC <br />
| <br />
| EMI <br />
| <br />
*gLite MW stack: Cream CE, LFC, Storm SE, WMS+LB, BDII. <br />
*Cloud: WNodes and OpenSTACK<br />
<br />
| TBD <br />
| €0.07/hr + 21% VAT<br />
|-<br />
! scope="row" | PL-Grid <br />
| TBC <br />
| <br />
| Cloud + Batch via Cream / EMI <br />
| <br />
*Computing power, storage, and human support <br />
*Batch processing via Cream CE/EMI <br />
*Cloud access <br />
*Non-grid, local access to queue system<br />
<br />
| Both <br />
| Capacity and price are a subject to negotiation<br />
|-<br />
! scope="row" | TUBITAK ULAKBIM <br />
| TR-10-ULAKBIM <br />
| <br />
| Cloud + Batch <br />
| <br />
*Batch processing via Cream CE <br />
*VM Management using OpenNebula/OCCI <br />
*Infiniband connected Linux computing resources<br />
<br />
| Both <br />
| €0.15/hour 8 core 24 GB instance<br />
|-<br />
! scope="row" | UIIP NASB <br />
| BY-UIIP <br />
| <br />
| Cloud + Batch <br />
| <br />
*Batch processing via UNICORE or Cream CE <br />
*Intel Xeon E5472 (3,0 GHz, 4 Cores) 50 nodes / 100 physical CPUs <br />
*400 virtual CPUs <br />
*400 Gb memory <br />
*8TB Disk storage – 9-12TB Storage servers <br />
*Infiniband DDR 20Gbit/sec]<br />
<br />
| Indirect <br />
| $0.077/hr (TBD) 1 Core<br />
|}<br />
<br />
<br> <br />
<br />
= Price in Accounting<br> =<br />
<br />
== Overview ==<br />
<br />
To test the mechanism for turning your accounting into a monetary charge charging rate needs to be defined. During the pilot this will be one number for your site in euros/HS06 hour. The number does not have to be real but obviously a ballpark figure would be good as it would give more realistic pilot reports. <br />
<br />
To define the charging rate the plan is to use a new feature of GOCDB which is known as ‘[https://wiki.egi.eu/wiki/GOCDB/Release4/Development/ExtensibilityMechanism 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 here]. <br />
<br />
== Instructions ==<br />
<br />
*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.<br />
<br />
#Go to the test GOCDB [https://gocdb-test.esc.rl.ac.uk/v5 https://gocdb-test.esc.rl.ac.uk/v5] which contains a copy of the production database. The same access rights apply but you will not change anything in the production database. <br />
#Navigate to your site. (My Sites) at the top of the left hand sidebar. <br />
#Just above the list of Services you should see a new box called 'Site Extension Properties' <br />
#At the bottom of this box there is a big green plus titled 'Add Properties' – click on it <br />
#This should show a window with two fields 'Property Name' and 'Property Value' <br />
#For 'Property Name' insert TEST_CHARGE <br />
#For 'Property Value' insert a real number which will be interpreted as euros per HEPSPEC06 Hour. <br />
#Click the button 'Add Site Property' <br />
#If you go back to the site view you will see TEST_CHARGE listed. You can edit or delete it.<br />
<br />
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.</div>
Asimon
https://wiki.egi.eu/w/index.php?title=VT_EGI_Pay-for-Use_Technical_Details&diff=64427
VT EGI Pay-for-Use Technical Details
2014-02-11T12:09:23Z
<p>Asimon: </p>
<hr />
<div>{{Template:EGI-PayForUse-PoC_menubar}} {{TOC right}} <br />
<br />
The following table provides an overview of the technical details of the resource and technology providers for the PoC. <br />
<br />
Further below are instructions for adding pricing into the accounting mechanisms. <br />
<br />
[1] All prices provided are interpreted as Euro per HEPSPEC06 hour. <br />
<br />
= Resource Providers, Services and Prices =<br />
<br />
{| class="wikitable"<br />
|-<br />
! scope="col" | NGI/RC <br />
! scope="col" | GOCDB Name <br />
! scope="col" | Contact <br />
! scope="col" | Service Type <br />
! scope="col" | Services and Resources <br />
! scope="col" | Preferred Payment Direct/Indirect <br />
! scope="col" | Price [1]<br />
|-<br />
! scope="row" | Albert Einstein Center, Univ. of Bern <br />
| UNIBE-LHEP <br />
| <br />
| Batch via CENTOS 5/6 ARC CE <br> <br />
| <br />
*500 cores (approx. 2 months in 2013) on highest priority; <br />
*Consumption preferably in one go, but distributed in time also possible <br />
*10-20 TB disk on local SE for consumption period via DPM SRM interface plus two weeks<br />
<br />
| Both <br />
| €0.03/hr; Storage free<br />
|-<br />
! scope="row" | Bulgaria Grid Portal <br />
| BG08-Madara <br />
| <br />
| TBC <br />
| <br />
*TBC<br />
<br />
| TBC <br />
| TBC<br />
|-<br />
! scope="row" | CESGA-IBERGRID <br />
| CESGA <br />
| <br />
| Batch + Cloud <br />
| <br />
*720 cores (Batch) AMD Opteron(tm) Processor 6174 2.2Ghz <br />
*240 cores (Cloud) Intel(R) Xeon(R) CPU E5520 2.27GHz <br />
*MPI jobs <br />
*RAM from 4GB to 32GB per core<br />
<br />
| Direct <br />
| <br />
€0.02/core/hour<br />
<br />
|-<br />
! scope="row" | IFCA-IBERGRID <br />
| TBD <br />
| <br />
| Batch (SLURM, SGE) or Cloud (FedCloud soon) <br />
| <br />
*Up to 2500 cores in servers with 4, 8, 16, 40 physical cores <br />
*Infiniband access to other nodes and storage possible for MPI jobs <br />
*RAM from 4GB to 256GB per core (max 1TB)<br />
<br />
| Direct <br />
| <br />
€0.05/core/hour for usual instances <br />
<br />
<span style="line-height: 1.5em;">€0.04/core/hour for multicore use (&gt;128 cores)</span> <br />
<br />
<span style="line-height: 1.5em;">Minimal storage free, requests up to 100 TB high performance storage possible</span> <br />
<br />
|-<br />
! scope="row" | Institute of Informatics of the Slovak Academy of Sciences <br />
| IISAS-FedCloud <br />
| <br />
| Cloud <br />
| <br />
*TBC<br />
<br />
| TBC <br />
| TBC<br />
|-<br />
! scope="row" | Latvian Grid <br />
| IMCSUL <br />
| <br />
| TBC <br />
| <br />
*TBC<br />
<br />
| TBC <br />
| TBC<br />
|-<br />
! scope="row" | Leibniz SC Centre <br />
| LRZ <br />
| <br />
| Globus <br />
| <br />
*Linux Cluster through Globus: GRAM5, GridFTP, Gsissh<br />
<br />
| Indirect <br />
| Price and capacity to be detailed later<br />
|-<br />
! scope="row" | MASTER-UP Srl <br />
| TBC <br />
| <br />
| EMI1/2, CEs, WNs, SE <br />
| <br />
*EMI1 middleware (phasing to EMI2) - CE's, WN's and SE. <br />
*10 nodes to start (intel 4core, ethernet connection) <br />
*Long experience in Molecular Science and Comp Chem, can provide support for such innovative applications and in the field of R&amp;D for combustion, energy and material science. <br />
*Managing a computer farm of 200 cores and 4TB of storage part of those resources are supporting EGI.<br />
<br />
| Direct <br />
| To be evaluated<br />
|-<br />
! scope="row" | NGI-DE <br />
| TBC <br />
| <br />
| UNICORE <br />
| <br />
*Cluster via UNICORE <br />
*Others can be offered (TBD)<br />
<br />
| Both <br />
| €0.06/hr + 19% VAT<br />
|-<br />
! scope="row" | NGI_GRNET <br />
| All HG-* <br />
| <br />
| Cloud and Grid <br />
| <br />
*TBC<br />
<br />
| TBC <br />
| €0.05/hr + 23% VAT<br />
|-<br />
! scope="row" | NGI-IT <br />
| TBC <br />
| <br />
| EMI <br />
| <br />
*gLite MW stack: Cream CE, LFC, Storm SE, WMS+LB, BDII. <br />
*Cloud: WNodes and OpenSTACK<br />
<br />
| TBD <br />
| €0.07/hr + 21% VAT<br />
|-<br />
! scope="row" | PL-Grid <br />
| TBC <br />
| <br />
| Cloud + Batch via Cream / EMI <br />
| <br />
*Computing power, storage, and human support <br />
*Batch processing via Cream CE/EMI <br />
*Cloud access <br />
*Non-grid, local access to queue system<br />
<br />
| Both <br />
| Capacity and price are a subject to negotiation<br />
|-<br />
! scope="row" | TUBITAK ULAKBIM <br />
| TR-10-ULAKBIM <br />
| <br />
| Cloud + Batch <br />
| <br />
*Batch processing via Cream CE <br />
*VM Management using OpenNebula/OCCI <br />
*Infiniband connected Linux computing resources<br />
<br />
| Both <br />
| €0.15/hour 8 core 24 GB instance<br />
|-<br />
! scope="row" | UIIP NASB <br />
| BY-UIIP <br />
| <br />
| Cloud + Batch <br />
| <br />
*Batch processing via UNICORE or Cream CE <br />
*Intel Xeon E5472 (3,0 GHz, 4 Cores) 50 nodes / 100 physical CPUs <br />
*400 virtual CPUs <br />
*400 Gb memory <br />
*8TB Disk storage – 9-12TB Storage servers <br />
*Infiniband DDR 20Gbit/sec]<br />
<br />
| Indirect <br />
| $0.077/hr (TBD) 1 Core<br />
|}<br />
<br />
<br> <br />
<br />
= Price in Accounting<br> =<br />
<br />
== Overview ==<br />
<br />
To test the mechanism for turning your accounting into a monetary charge charging rate needs to be defined. During the pilot this will be one number for your site in euros/HS06 hour. The number does not have to be real but obviously a ballpark figure would be good as it would give more realistic pilot reports. <br />
<br />
To define the charging rate the plan is to use a new feature of GOCDB which is known as ‘[https://wiki.egi.eu/wiki/GOCDB/Release4/Development/ExtensibilityMechanism 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 here]. <br />
<br />
== Instructions ==<br />
<br />
*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.<br />
<br />
#Go to the test GOCDB [https://gocdb-test.esc.rl.ac.uk/v5 https://gocdb-test.esc.rl.ac.uk/v5] which contains a copy of the production database. The same access rights apply but you will not change anything in the production database. <br />
#Navigate to your site. (My Sites) at the top of the left hand sidebar. <br />
#Just above the list of Services you should see a new box called 'Site Extension Properties' <br />
#At the bottom of this box there is a big green plus titled 'Add Properties' – click on it <br />
#This should show a window with two fields 'Property Name' and 'Property Value' <br />
#For 'Property Name' insert TEST_CHARGE <br />
#For 'Property Value' insert a real number which will be interpreted as euros per HEPSPEC06 Hour. <br />
#Click the button 'Add Site Property' <br />
#If you go back to the site view you will see TEST_CHARGE listed. You can edit or delete it.<br />
<br />
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.</div>
Asimon
https://wiki.egi.eu/w/index.php?title=VT_EGI_Pay-for-Use_Technical_Details&diff=64426
VT EGI Pay-for-Use Technical Details
2014-02-11T12:06:19Z
<p>Asimon: </p>
<hr />
<div>{{Template:EGI-PayForUse-PoC_menubar}} {{TOC right}} <br />
<br />
The following table provides an overview of the technical details of the resource and technology providers for the PoC. <br />
<br />
Further below are instructions for adding pricing into the accounting mechanisms. <br />
<br />
[1] All prices provided are interpreted as Euro per HEPSPEC06 hour. <br />
<br />
= Resource Providers, Services and Prices =<br />
<br />
{| class="wikitable"<br />
|-<br />
! scope="col" | NGI/RC <br />
! scope="col" | GOCDB Name <br />
! scope="col" | Contact <br />
! scope="col" | Service Type <br />
! scope="col" | Services and Resources <br />
! scope="col" | Preferred Payment Direct/Indirect <br />
! scope="col" | Price [1]<br />
|-<br />
! scope="row" | Albert Einstein Center, Univ. of Bern <br />
| UNIBE-LHEP <br />
| <br />
| Batch via CENTOS 5/6 ARC CE <br> <br />
| <br />
*500 cores (approx. 2 months in 2013) on highest priority; <br />
*Consumption preferably in one go, but distributed in time also possible <br />
*10-20 TB disk on local SE for consumption period via DPM SRM interface plus two weeks<br />
<br />
| Both <br />
| €0.03/hr; Storage free<br />
|-<br />
! scope="row" | Bulgaria Grid Portal <br />
| BG08-Madara <br />
| <br />
| TBC <br />
| <br />
*TBC<br />
<br />
| TBC <br />
| TBC<br />
|-<br />
! scope="row" | CESGA-IBERGRID <br />
| CESGA <br />
| <br />
| Batch + Cloud <br />
| <br />
*720 cores (Batch) AMD Opteron(tm) Processor 6174 2.2Ghz<br />
*240 cores (Cloud) Intel(R) Xeon(R) CPU E5520 2.27GHz<br />
*MPI jobs <br />
*RAM from 4GB to 32GB per core<br />
| Direct <br />
| <br />
€0.02/core/hour for usual instances <br />
|-<br />
! scope="row" | IFCA-IBERGRID <br />
| TBD <br />
| <br />
| Batch (SLURM, SGE) or Cloud (FedCloud soon) <br />
| <br />
*Up to 2500 cores in servers with 4, 8, 16, 40 physical cores <br />
*Infiniband access to other nodes and storage possible for MPI jobs <br />
*RAM from 4GB to 256GB per core (max 1TB)<br />
<br />
| Direct <br />
| <br />
€0.05/core/hour for usual instances <br />
<br />
<span style="line-height: 1.5em;">€0.04/core/hour for multicore use (&gt;128 cores)</span> <br />
<br />
<span style="line-height: 1.5em;">Minimal storage free, requests up to 100 TB high performance storage possible</span> <br />
<br />
|-<br />
! scope="row" | Institute of Informatics of the Slovak Academy of Sciences <br />
| IISAS-FedCloud <br />
| <br />
| Cloud <br />
| <br />
*TBC<br />
<br />
| TBC <br />
| TBC<br />
|-<br />
! scope="row" | Latvian Grid <br />
| IMCSUL <br />
| <br />
| TBC <br />
| <br />
*TBC<br />
<br />
| TBC <br />
| TBC<br />
|-<br />
! scope="row" | Leibniz SC Centre <br />
| LRZ <br />
| <br />
| Globus <br />
| <br />
*Linux Cluster through Globus: GRAM5, GridFTP, Gsissh<br />
<br />
| Indirect <br />
| Price and capacity to be detailed later<br />
|-<br />
! scope="row" | MASTER-UP Srl <br />
| TBC <br />
| <br />
| EMI1/2, CEs, WNs, SE <br />
| <br />
*EMI1 middleware (phasing to EMI2) - CE's, WN's and SE. <br />
*10 nodes to start (intel 4core, ethernet connection) <br />
*Long experience in Molecular Science and Comp Chem, can provide support for such innovative applications and in the field of R&amp;D for combustion, energy and material science. <br />
*Managing a computer farm of 200 cores and 4TB of storage part of those resources are supporting EGI.<br />
<br />
| Direct <br />
| To be evaluated<br />
|-<br />
! scope="row" | NGI-DE <br />
| TBC <br />
| <br />
| UNICORE <br />
| <br />
*Cluster via UNICORE <br />
*Others can be offered (TBD)<br />
<br />
| Both <br />
| €0.06/hr + 19% VAT<br />
|-<br />
! scope="row" | NGI_GRNET <br />
| All HG-* <br />
| <br />
| Cloud and Grid <br />
| <br />
*TBC<br />
<br />
| TBC <br />
| €0.05/hr + 23% VAT<br />
|-<br />
! scope="row" | NGI-IT <br />
| TBC <br />
| <br />
| EMI <br />
| <br />
*gLite MW stack: Cream CE, LFC, Storm SE, WMS+LB, BDII. <br />
*Cloud: WNodes and OpenSTACK<br />
<br />
| TBD <br />
| €0.07/hr + 21% VAT<br />
|-<br />
! scope="row" | PL-Grid <br />
| TBC <br />
| <br />
| Cloud + Batch via Cream / EMI <br />
| <br />
*Computing power, storage, and human support <br />
*Batch processing via Cream CE/EMI <br />
*Cloud access <br />
*Non-grid, local access to queue system<br />
<br />
| Both <br />
| Capacity and price are a subject to negotiation<br />
|-<br />
! scope="row" | TUBITAK ULAKBIM <br />
| TR-10-ULAKBIM <br />
| <br />
| Cloud + Batch <br />
| <br />
*Batch processing via Cream CE <br />
*VM Management using OpenNebula/OCCI <br />
*Infiniband connected Linux computing resources<br />
<br />
| Both <br />
| €0.15/hour 8 core 24 GB instance<br />
|-<br />
! scope="row" | UIIP NASB <br />
| BY-UIIP <br />
| <br />
| Cloud + Batch <br />
| <br />
*Batch processing via UNICORE or Cream CE <br />
*Intel Xeon E5472 (3,0 GHz, 4 Cores) 50 nodes / 100 physical CPUs <br />
*400 virtual CPUs <br />
*400 Gb memory <br />
*8TB Disk storage – 9-12TB Storage servers <br />
*Infiniband DDR 20Gbit/sec]<br />
<br />
| Indirect <br />
| $0.077/hr (TBD) 1 Core<br />
|}<br />
<br />
<br> <br />
<br />
= Price in Accounting<br> =<br />
<br />
== Overview ==<br />
<br />
To test the mechanism for turning your accounting into a monetary charge charging rate needs to be defined. During the pilot this will be one number for your site in euros/HS06 hour. The number does not have to be real but obviously a ballpark figure would be good as it would give more realistic pilot reports. <br />
<br />
To define the charging rate the plan is to use a new feature of GOCDB which is known as ‘[https://wiki.egi.eu/wiki/GOCDB/Release4/Development/ExtensibilityMechanism 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 here]. <br />
<br />
== Instructions ==<br />
<br />
*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.<br />
<br />
#Go to the test GOCDB [https://gocdb-test.esc.rl.ac.uk/v5 https://gocdb-test.esc.rl.ac.uk/v5] which contains a copy of the production database. The same access rights apply but you will not change anything in the production database. <br />
#Navigate to your site. (My Sites) at the top of the left hand sidebar. <br />
#Just above the list of Services you should see a new box called 'Site Extension Properties' <br />
#At the bottom of this box there is a big green plus titled 'Add Properties' – click on it <br />
#This should show a window with two fields 'Property Name' and 'Property Value' <br />
#For 'Property Name' insert TEST_CHARGE <br />
#For 'Property Value' insert a real number which will be interpreted as euros per HEPSPEC06 Hour. <br />
#Click the button 'Add Site Property' <br />
#If you go back to the site view you will see TEST_CHARGE listed. You can edit or delete it.<br />
<br />
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.</div>
Asimon
https://wiki.egi.eu/w/index.php?title=Fedcloud-tf:WorkGroups:Brokering&diff=64090
Fedcloud-tf:WorkGroups:Brokering
2014-02-03T08:40:29Z
<p>Asimon: </p>
<hr />
<div>{{Fedcloud-tf:Menu}} {{Fedcloud-tf:WorkGroups:Menu}} {{TOC_right}} <br />
<br />
<font color="red">Leader: Alvaro Simon, JR1 </font> <br />
<br />
== Collaborators ==<br />
<br />
{| border="1"<br />
|-<br />
! Role <br />
! Institution <br />
! Name<br />
|-<br />
| Collaborator <br />
| OeRC <br />
| Matteo Turilli<br />
|-<br />
| Collaborator <br />
| BSC <br />
| Daniele Lezzi<br />
|}<br />
<br />
== Scope ==<br />
<br />
This workgroup deals with the issues around cloud brokering. With 10+ resource providers lined up to be federated into the EGI cloud testbed, users need effective ways to access cloud resources. The goal is for a user to have a choice between a unified, abstracted view of the cloud testbed as a whole and the opportunity to target specific providers for their needs. As a consequence, this workgroup is concerned with both brokers and OCCI clients. <br />
<br />
== Roadmap ==<br />
<br />
*Collect information about existing solutions for cloud brokering compatible with the OCCI and CDMI management interfaces; <br />
*Collect information about existing solutions for OCCI and CDMI clients; <br />
*Make an inventory of the available solutions; <br />
*Choose a broker and a client for the testbed; <br />
*If possible, join the development teams of the chosen solutions to the task force; <br />
*Coordinate with the TF Resorce Providers to deploy the chosen solutions; <br />
*Extend the demo testbed addressing a real-life use case.<br />
<br />
== Clients Comparison Table ==<br />
<br />
{| cellspacing="0" cellpadding="5" width="90%" class="wikitable" style="border:1px solid black;"<br />
|- style="background-color:darkgray;"<br />
! Client/API <br />
! URL <br />
! OS <br />
! Support <br />
! OCCI/CDMI <br />
! Functionalities <br />
! Effort required <br />
! Comments<br />
|-<br />
| Hybridfox <br />
| http://code.google.com/p/hybridfox/ <br />
| Win/OS X/Linux <br />
| AWS/Eucalyptus/OpenStack/OpenNebula/HP Cloud <br />
| <span style="color:red"> '''NO'''</span> <br />
| Manage Images/Instances/Elastic IPs/Security Groups/Key-pairs <br />
| <span style="color:green"> '''Low'''</span> <br />
| Hybridfox does not support x509 auth, it uses EC2 auth for OpenNebula and OpenStack<br />
|-<br />
| DeltaCloud <br />
| http://deltacloud.apache.org <br />
| Win/OS X/Linux <br />
| EC2/Eucalyptus/OpenStack/OpenNebula/vSphere <br />
| <span style="color:red"> '''NO'''</span> <br />
| Create/Start/Stop/Reboot/Destroy instances <br />
| <span style="color:orange"> '''Medium'''</span> <br />
| DeltaCloud uses its own delta-cloud driver for each framework instead of OCCI. It provides storage support for S3, Warlus, Azure and Google Storage.<br />
|-<br />
| Aeolus <br />
| http://aeolusproject.org/about.html <br />
| Win/OS X/Linux <br />
| Same as DeltaCloud <br />
| <span style="color:red"> '''NO'''</span> <br />
| Create/Start/Stop/.. instances. Manage different instances and Images from different private, public, or hybrid cloud providers. <br />
| <span style="color:orange"> '''Medium'''</span> <br />
| Aeolus uses DeltaCloud cross-cloud abstraction library and it includes some extra functionalities. It includes Aeolus Conductor/Composer/Orchestrator/HA Manager<br />
|-<br />
| rOCCI (API) <br />
| http://dev.opennebula.org/projects/ogf-occi <br />
| Linux <br />
| OpenNebula/EC2 <br />
| <span style="color:green"> '''YES'''</span> <br />
| Create/Start/Stop/Reboot/Destroy instances. Upload and register an image. Network conf. x509 auth. <br />
| <span style="color:green"> '''Low'''</span> <br />
| rOCCI is an OCCI 1.1 implementation for OpenNebula 3.x<br />
|}<br />
<br />
== Cloud Brokering Solutions ==<br />
<br />
=== Resource Brokers ===<br />
<br />
{| cellspacing="0" cellpadding="5" width="90%" class="wikitable" style="border:1px solid black;"<br />
|- style="background-color:darkgray;"<br />
! Name <br />
! URL <br />
! Cloud SW Support <br />
! OCCI <br />
! External API <br />
! Functionalities <br />
! Effort required <br />
! Comments<br />
|-<br />
| CompatibleOne <br />
| http://www.compatibleone.org/ <br />
| OpenStack, OpenNebula, Azure, Vcloud <br />
| Yes, supports OCCI, but implements his own OCCI interface for each of the stacks (PROCCI). <br />
| <br />
| Accounting, Brokering, User management, Monitoring. <br />
| <span style="color:red"> '''High'''</span> <br />
| <br />
*Compatible One is a complete plattform, with its own user management, accounting and monitoring, so it overlaps in some aspects with the ongoing work. <br />
*It does not expose an OCCI api, the user has to write its own XML files and send them to the broker. <br />
*The credentials for each of the connectors and providers have to be configured in advance by the administrator of the broker service. <br />
*The user has to specify in the manifests the cloud account that he wants to use, and the specific name of the image in the site. It seems that the purpose of CompatibleONE is to deploy and take care of a complete manifest description: A user wants 3 machines of type A in site FOO, and 2 machine of type B in site BAR, so he explicitly defines it in his manifests and CompatibleOne will deploy it on them.<br />
<br />
|-<br />
| VMDIRAC <br />
| https://github.com/DIRACGrid/VMDIRAC/wiki <br />
| &nbsp; OpenNebula, OpenStack, CloudStack and Amazon EC2 <br />
| Yes, it supports rOCCI, OpenNebula "OCCI 0.8", Amazon EC2, OpenStack Nova 1.1 and CloudStack 2 APIs. <br />
| <br />
| Accounting, monitoring, brokering, scheduling, HEPiX and SSH based VM contextualisation, [https://github.com/DIRACGrid/VMDIRAC/wiki#vm-horizontal-auto-scaling-setup VM Horizontal Auto-scaling]. <br />
| <span style="color:orange"> '''Medium'''</span> <br />
| <br />
*rOCCI support with X509/VOMS auth. <br />
*In production: LHCb (OpenStack and OpenNebula) Belle (Amazon), Work in progress France Federated Cloud. <br />
*Web UI including VM browsing with VM monitoring, and VM Overview Plots (Load, RunningVM, RunnigVM by Endpoint, started jobs, data transfer, transfer files) <br />
*The number of VMs is dynamically adjusted to the current workload. <br />
*Automatic selection of the VMs types depending on the tasks constraints. <br />
*No necessary to install any pluging in the Cloud Managers, works with standard interfaces. <br />
*Separated user credentials are used for job running and VM operator credentials for VM management. <br />
*VMDIRAC developers are willing to collaborate actively with Fedcloud Taskforce.<br />
<br />
|-<br />
| SlipStream™ <br />
| http://sixsq.com/products/slipstream.html <br />
| StratusLab, OpenStack, Abiquo, CloudSigma and Amazon EC2 <br />
| Supports OCCI via rOCCI-cli integration <br />
| EC2 via bridge (experimental), proprietary SlipStream REST APIs <br />
| VM image creation and deployment, contextualisation, VM cluster automated deployments. <br />
| <span style="color:orange"> '''Medium'''</span> <br />
| <br />
*New release 2.0 scheduled for January 2014, with Autoscaling capabilities. <br />
*Acts as single interface and point of entrance to multiple clouds. Does not provide a brokering mechanism at application level. <br />
*It is able to use deploy VMs across different cloud frameworks using common deployment scripts. <br />
*Can deploy clusters concurrently over multiple clouds. <br />
*Deployments can be configured according to custom parameters (ex. number of nodes, services to install on the VM, etc...) <br />
*VM contextualization is performed by Slipstream orchestrator (a separately instantiated VM), using SSH or native RP contextualization methods. <br />
*Autoscaling capabilities will be implemented in 2014. Autoscaling will act at infrastructure level, using CPU/Disk/Memory metrics (not application metrix, ex. number of jobs in queue). <br />
*RPs don't need to configure new services. It uses native cloud APIs. <br />
*Provides EC2 (currently in beta) and SlipStream native REST API interface. <br />
*User do not need to have cloud credentials to instantiate VMs. Slipstream acts as account broker. <br />
*Does not provide accounting or cost information. <br />
*Test interface available on the FedCloud for users, to request access please contact [mailto:salvatore.pinto@egi.eu salvatore.pinto@egi.eu]<br />
<br />
|}<br />
<br />
=== Application Brokers ===<br />
<br />
{| cellspacing="0" cellpadding="5" width="90%" class="wikitable" style="border:1px solid black;"<br />
|- style="background-color:darkgray;"<br />
! Name <br />
! URL <br />
! Cloud SW Support <br />
! OCCI <br />
! External API <br />
! Functionalities <br />
! Effort required <br />
! Comments<br />
|-<br />
| COMPSs <br />
| http://www.bsc.es/compss <br />
| &nbsp; OpenNebula, Amazon, Azure, OpenStack <br />
| Yes, support of rOCCI servers and OCCI+OVF <br />
| OGF-BES SOAP <br />
| &nbsp;Automatic parallelization and orchestration of applications and services, elasticity, auto scaling <br />
| <span style="color:orange"> '''Medium'''</span> <br />
| <br />
*COMPSs allows the execution of applications on distributed infrastructures (grids, clusters, cloud). <br />
*Already used for the BioVeL/OpenBio use case. <br />
*Transparent support to different infrastructures; the user only provides his credentials. <br />
*Automatic selection of the VMs types dependending on the tasks constraints. <br />
*The number of VMs is dynamically adjusted to the current workload.<br />
<br />
|-<br />
| VMDIRAC <br />
| https://github.com/DIRACGrid/VMDIRAC/wiki <br />
| &nbsp; OpenNebula, OpenStack, CloudStack and Amazon EC2 <br />
| Yes, it supports rOCCI, OpenNebula "OCCI 0.8", Amazon EC2, OpenStack Nova 1.1 and CloudStack 2 APIs. <br />
| <br />
| Accounting, monitoring, brokering, scheduling, HEPiX and SSH based VM contextualisation, [https://github.com/DIRACGrid/VMDIRAC/wiki#vm-horizontal-auto-scaling-setup VM Horizontal Auto-scaling]. <br />
| <span style="color:orange"> '''Medium'''</span> <br />
| <br />
*rOCCI support with X509/VOMS auth. <br />
*In production: LHCb (OpenStack and OpenNebula) Belle (Amazon), Work in progress France Federated Cloud. <br />
*Web UI including VM browsing with VM monitoring, and VM Overview Plots (Load, RunningVM, RunnigVM by Endpoint, started jobs, data transfer, transfer files) <br />
*The number of VMs is dynamically adjusted to the current workload. <br />
*Automatic selection of the VMs types depending on the tasks constraints. <br />
*No necessary to install any pluging in the Cloud Managers, works with standard interfaces. <br />
*Separated user credentials are used for job running and VM operator credentials for VM management. <br />
*VMDIRAC developers are willing to collaborate actively with Fedcloud Taskforce.<br />
<br />
|}</div>
Asimon
https://wiki.egi.eu/w/index.php?title=EGI_Quality_Criteria_Verification&diff=63969
EGI Quality Criteria Verification
2014-01-30T14:30:07Z
<p>Asimon: </p>
<hr />
<div>{{SWProv menubar}} {{SWProv QA submenu}} {{TOC_right}} <br />
<br />
== Objective ==<br />
<br />
The main objective of the TSA2.3 is to verify the quality of the software provided by the TP before entering the SR phase and going to production. By doing so we prevent that software that might work enters into the SR and even goes into production but that doesn´t follow the quality criteria defined in TSA2.2. Some of the reasons for doing the verification before the software enters the stage rollout are: <br />
<br />
- Check that the bugs reported in the previous release of the software have been corrected (work in collaboration with DMSU) by the TP. <br />
<br />
- Software can work well in the SR but might not have all the functionalities required <br />
<br />
- Software might not be safe, well documented, or have the necessary installation rules or licenses <br />
<br />
== The Verification Process ==<br />
<br />
When a new product is available, the TP has to follow the [[NSRW IMPLEMENTATION RT|NSRW]]. Once the software is correctly uploaded to the repository, the release enters into the verification phase. The requirements are that the TP has to provide all the necessary information to the verifier (QCV) so that the QCV can assess that the TP has tested in advance the quality of the software. Depending on the type of release, different actions will be taken by the QCV, Verification process is described in detail in the [[EGI Verifier Guideline]]. <br />
<br />
== QC Verification Reports ==<br />
<br />
RT workflow and Verification Templates links are available in this page. First of all verifiers must check QC service mapping to know which test must be verified for each product. This service mapping is available here [https://documents.egi.eu/document/418 QC Verification service mapping] and Verification/Executive Summary templates are available here: [https://documents.egi.eu/document/417 QC Verification Templates]. <br />
<br />
Verifiers must fill all required fields for each product and write a Verification process summary into Executive Summary, this summary should include: <br />
<br />
*A short summary of the installation and configuration process: Installation and configuration were successful?, If not explain any issue or bug found. If the product was rejected explain why. <br />
*If its necessary Verifiers should include a comment for StageRollout: Configuration changes or minor issues found verifying the product. <br />
*If a new QC is necessary and is not included, Verifiers must write a comment to SA2.2 to change current QC.<br />
<br />
<br> <br />
<br />
== UMD Release Candidate Testing ==<br />
<br />
Before each UMD release the verification team checks the new RC. To perform this task SA2.3 VMs have included the [https://github.com/alvarosimon/RC_tester RC_testing script]. This script is available after each SA2 VM instantiation (into /root/configuration_templates/tools directory). This script is able to detect any package inconsistency after UMD RC repo configuration. The RC testing process is as follows: <br />
<br />
*Verifier should instantiate different Linux flavours VM. For UMD case SL5, SL6 and debian. <br />
*Install UMD RC repo files from UMDx RC page. <br />
*Check RC_tester "PRODUCTS" array. '''This array must be updated to include all UMD products!''' <br />
*It is recommended to use ''screen'' program before RC_tester execution. RC tests take about 2h/3h to finish (depends on OS used and the number of products). <br />
*Run ''RC_tester'' and follows its instructions. <br />
*''RC_tester'' generates several logs into log directory, after its execution SA2 verifier should check: <br />
**''installator_OK.log'': List of metapackages installed correctly. <br />
**''installator_ERROR.log'': List of metapackages which contain any issue. <br />
**''&lt;PRODUCT_NAME&gt;_OUTPUT.log'': Complete Product installation log. <br />
**''&lt;PRODUCT_NAME&gt;_postupdate.log'': Info about product update execution. It detects any issue updating current UMD products.<br />
<br />
<br> <br />
<br />
== Verification Work Effort Metrics ==<br />
<br />
Each verification process and change is registered by EGI RT. A complete report is generated on a daily basis each midnight. The XLS file can be downloaded from here [https://rt.egi.eu/rt/SA2/sa2-sw-rel-verification-metrics.xls SA2 Verification Metrics] <br />
<br />
<br> <br />
<br />
== Verification Team ==<br />
<br />
Verifiers team is updated for each UMD release and it is available here: [https://documents.egi.eu/document/514 SA2.3 Verifiers List]. All verifiers are included in the [https://www.egi.eu/sso/groupView/sw-rel-qc SSO sw-rel-qc group] that includes a mailing list and permissions to modify RT tickets related with the verification process. <br />
<br />
== Reference Documents ==<br />
<br />
{| border="1" cellspacing="0" cellpadding="3" style="border: 1px solid black;" class="wikitable sortable"<br />
|- align="left" style="background: none repeat scroll 0% 0% Lightgray;"<br />
! DocDB link <br />
! Release Date <br />
! Document<br />
|-<br />
| [https://documents.egi.eu/document/1700 QCv5] <br />
| 08. 05. 2013 <br />
| UMD Quality Criteria<br />
|-<br />
| [https://documents.egi.eu/document/418 418] <br />
| 08. 05. 2013 <br />
| UMD Products service mapping<br />
|-<br />
| [https://documents.egi.eu/document/417 417] <br />
| 08. 05. 2013 <br />
| QC Verification Templates<br />
|}<br />
<br />
== Metrics ==<br />
<br />
{| border="1" cellspacing="0" cellpadding="3" style="border: 1px solid black;" class="wikitable sortable"<br />
|- align="left" style="background: none repeat scroll 0% 0% Lightgray;"<br />
! Metric <br />
! Description<br />
|-<br />
| M.SA2.4 <br />
| Number of new releases validated against defined criteria: Measures the workload on the validation team.<br />
|-<br />
| M.SA2.5 <br />
| Mean time taken to validate a releas: Indicates how responsive the team is to validating releases.<br />
|-<br />
| M.SA2.6 <br />
| Number of releases failing validation: Indicates the quality assurance process of the software providers.<br />
|}<br />
<br />
== SLAs ==<br />
<br />
EGI SLAs negotiated with the TPs <br />
<br />
[https://documents.egi.eu/document/461 EMI-EGI SLA] <br />
<br />
== Verification engineer skill matrix ==<br />
<br />
{| border="1" class="wikitable" style="text-align: center;"<br />
|+ Verification Cheat Sheet <br />
|-<br />
! width="200" align="left" | Product\Institute <br />
! width="75" | CESGA <br />
! width="75" | IFCA <br />
! width="75" | IFIC <br />
! width="75" | INFN <br />
! width="75" | IN2P3 <br />
! width="75" | JÜLICH <br />
! width="75" | LIP <br />
! width="75" | LRZ <br />
! width="75" | UTC-N <br />
! width="75" | CSC <br />
! width="75" | GRNET <br />
! width="75" | RAL <br />
! width="75" | FZU <br />
! width="300" style="background: none repeat scroll 0% 0% Gray;" | COMMENTS<br />
|-<br />
! align="left" | EMI ARC CE <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI ARC compute cli <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI ARC Infosys <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI dCache <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI gLite MPI <br />
| * <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI CREAM_torque <br />
| * <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI CREAM_lsf <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI EMIR <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
|-<br />
! align="left" | EMI WMS <br />
| * <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI LB <br />
| * <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI FTS <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
|-<br />
! align="left" | EMI DPM <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI LFC_mySQL <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI LFC_Oracle <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI StoRM <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI APEL <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI DGAS <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI BDII <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI UI <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI PX <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI VOMS_mySQL <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" style="background: none repeat scroll 0% 0% Red;" | EMI VOMS_Oracle <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| No verifiers available yet. Oracle training required.<br />
|-<br />
! align="left" style="background: none repeat scroll 0% 0% Red;" | EMI HYDRA <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| No verifiers available yet.<br />
|-<br />
! align="left" style="background: none repeat scroll 0% 0% Red;" | EMI Wnodes <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| No verifiers available yet.<br />
|-<br />
! align="left" style="background: none repeat scroll 0% 0% Red;" | EMI NAGIOS <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| No verifiers available yet.<br />
|-<br />
! align="left" style="background: none repeat scroll 0% 0% Red;" | EMI Pseudonymity <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| No verifiers available yet.<br />
|-<br />
! align="left" | EMI ARGUS <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI UNICORE TSI <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI UNICORE WS <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI UNICORE Client <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI UNICORE Registry <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI UNICORE Gateway <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI UNICORE Hila <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI UNICORE xuudb <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI UNICORE Uvos <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI AMGA <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | IGE SAGA-SD <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| No verifiers available yet.<br />
|-<br />
! align="left" | IGE GRAM5 <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | IGE GSISSH <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | IGE GridFTP <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | IGE myProxy <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | IGE RLS <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | IGE GridWay <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | IGE SAM <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | IGE OGSA-DAI <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | IGE Security <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | IGE Gridsafe <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|}<br />
<br />
<br> <br />
<br />
[https://www.egi.eu/earlyAdopters/table Early Adopters list] <br />
<br />
[https://www.egi.eu/earlyAdopters/teams Early Adopters per UMD product]</div>
Asimon
https://wiki.egi.eu/w/index.php?title=Fedcloud-tf:WorkGroups:Brokering&diff=62928
Fedcloud-tf:WorkGroups:Brokering
2013-12-17T11:56:28Z
<p>Asimon: </p>
<hr />
<div>{{Fedcloud-tf:Menu}} {{Fedcloud-tf:WorkGroups:Menu}} {{TOC_right}} <br />
<br />
<font color="red">Leader: Alvaro Simon, JR1 </font> <br />
<br />
== Collaborators ==<br />
<br />
{| border="1"<br />
|-<br />
! Role <br />
! Institution <br />
! Name<br />
|-<br />
| Collaborator <br />
| OeRC <br />
| Matteo Turilli<br />
|-<br />
| Collaborator <br />
| BSC <br />
| Daniele Lezzi<br />
|}<br />
<br />
== Scope ==<br />
<br />
This workgroup deals with the issues around cloud brokering. With 10+ resource providers lined up to be federated into the EGI cloud testbed, users need effective ways to access cloud resources. The goal is for a user to have a choice between a unified, abstracted view of the cloud testbed as a whole and the opportunity to target specific providers for their needs. As a consequence, this workgroup is concerned with both brokers and OCCI clients. <br />
<br />
== Roadmap ==<br />
<br />
*Collect information about existing solutions for cloud brokering compatible with the OCCI and CDMI management interfaces; <br />
*Collect information about existing solutions for OCCI and CDMI clients; <br />
*Make an inventory of the available solutions; <br />
*Choose a broker and a client for the testbed; <br />
*If possible, join the development teams of the chosen solutions to the task force; <br />
*Coordinate with the TF Resorce Providers to deploy the chosen solutions; <br />
*Extend the demo testbed addressing a real-life use case.<br />
<br />
== Clients Comparison Table ==<br />
<br />
{| width="90%" cellspacing="0" cellpadding="5" style="border:1px solid black;" class="wikitable"<br />
|- style="background-color:darkgray;"<br />
! Client/API <br />
! URL <br />
! OS <br />
! Support <br />
! OCCI/CDMI <br />
! Functionalities <br />
! Effort required <br />
! Comments<br />
|-<br />
| Hybridfox <br />
| http://code.google.com/p/hybridfox/ <br />
| Win/OS X/Linux <br />
| AWS/Eucalyptus/OpenStack/OpenNebula/HP Cloud <br />
| <span style="color:red"> '''NO'''</span> <br />
| Manage Images/Instances/Elastic IPs/Security Groups/Key-pairs <br />
| <span style="color:green"> '''Low'''</span> <br />
| Hybridfox does not support x509 auth, it uses EC2 auth for OpenNebula and OpenStack<br />
|-<br />
| DeltaCloud <br />
| http://deltacloud.apache.org <br />
| Win/OS X/Linux <br />
| EC2/Eucalyptus/OpenStack/OpenNebula/vSphere <br />
| <span style="color:red"> '''NO'''</span> <br />
| Create/Start/Stop/Reboot/Destroy instances <br />
| <span style="color:orange"> '''Medium'''</span> <br />
| DeltaCloud uses its own delta-cloud driver for each framework instead of OCCI. It provides storage support for S3, Warlus, Azure and Google Storage.<br />
|-<br />
| Aeolus <br />
| http://aeolusproject.org/about.html <br />
| Win/OS X/Linux <br />
| Same as DeltaCloud <br />
| <span style="color:red"> '''NO'''</span> <br />
| Create/Start/Stop/.. instances. Manage different instances and Images from different private, public, or hybrid cloud providers. <br />
| <span style="color:orange"> '''Medium'''</span> <br />
| Aeolus uses DeltaCloud cross-cloud abstraction library and it includes some extra functionalities. It includes Aeolus Conductor/Composer/Orchestrator/HA Manager<br />
|-<br />
| rOCCI (API) <br />
| http://dev.opennebula.org/projects/ogf-occi <br />
| Linux <br />
| OpenNebula/EC2 <br />
| <span style="color:green"> '''YES'''</span> <br />
| Create/Start/Stop/Reboot/Destroy instances. Upload and register an image. Network conf. x509 auth. <br />
| <span style="color:green"> '''Low'''</span> <br />
| rOCCI is an OCCI 1.1 implementation for OpenNebula 3.x<br />
|}<br />
<br />
== Cloud Brokering Solutions ==<br />
<br />
=== Resource Brokers ===<br />
<br />
{| width="90%" cellspacing="0" cellpadding="5" style="border:1px solid black;" class="wikitable"<br />
|- style="background-color:darkgray;"<br />
! Name <br />
! URL <br />
! Cloud SW Support <br />
! OCCI <br />
! External API <br />
! Functionalities <br />
! Effort required <br />
! Comments<br />
|-<br />
| CompatibleOne <br />
| http://www.compatibleone.org/ <br />
| OpenStack, OpenNebula, Azure, Vcloud <br />
| Yes, supports OCCI, but implements his own OCCI interface for each of the stacks (PROCCI). <br />
| <br />
| Accounting, Brokering, User management, Monitoring. <br />
| <span style="color:orange"> '''Medium'''</span> <br />
| <br />
*Compatible One is a complete plattform, with its own user management, accounting and monitoring, so it overlaps in some aspects with the ongoing work. <br />
*It does not expose an OCCI api, the user has to write its own XML files and send them to the broker. <br />
*The credentials for each of the connectors and providers have to be configured in advance by the administrator of the broker service. <br />
*The user has to specify in the manifests the cloud account that he wants to use, and the specific name of the image in the site. It seems that the purpose of CompatibleONE is to deploy and take care of a complete manifest description: A user wants 3 machines of type A in site FOO, and 2 machine of type B in site BAR, so he explicitly defines it in his manifests and CompatibleOne will deploy it on them.<br />
<br />
|-<br />
| VMDIRAC <br />
| https://github.com/DIRACGrid/VMDIRAC/wiki <br />
| &nbsp; OpenNebula, OpenStack, CloudStack and Amazon EC2 <br />
| Yes, it supports rOCCI, OpenNebula "OCCI 0.8", Amazon EC2, OpenStack Nova 1.1 and CloudStack 2 APIs. <br />
| <br />
| Accounting, monitoring, brokering, scheduling, HEPiX and SSH based VM contextualisation, [https://github.com/DIRACGrid/VMDIRAC/wiki#vm-horizontal-auto-scaling-setup VM Horizontal Auto-scaling]. <br />
| <span style="color:orange"> '''Medium'''</span> <br />
| <br />
*rOCCI support with X509/VOMS auth. <br />
*In production: LHCb (OpenStack and OpenNebula) Belle (Amazon), Work in progress France Federated Cloud. <br />
*Web UI including VM browsing with VM monitoring, and VM Overview Plots (Load, RunningVM, RunnigVM by Endpoint, started jobs, data transfer, transfer files) <br />
*The number of VMs is dynamically adjusted to the current workload. <br />
*Automatic selection of the VMs types depending on the tasks constraints. <br />
*No necessary to install any pluging in the Cloud Managers, works with standard interfaces. <br />
*Separated user credentials are used for job running and VM operator credentials for VM management. <br />
*VMDIRAC developers are willing to collaborate actively with Fedcloud Taskforce.<br />
<br />
|-<br />
| SlipStream™ <br />
| http://sixsq.com/products/slipstream.html <br />
| StratusLab, OpenStack, Abiquo, CloudSigma and Amazon EC2 <br />
| Supports OCCI via rOCCI-cli integration <br />
| EC2 via bridge (experimental), proprietary SlipStream REST APIs <br />
| VM image creation and deployment, contextualisation, VM cluster automated deployments. <br />
| <span style="color:orange"> '''Medium'''</span> <br />
| <br />
*New release 2.0 scheduled for January 2014, with Autoscaling capabilities. <br />
*Acts as single interface and point of entrance to multiple clouds. Does not provide a brokering mechanism at application level. <br />
*It is able to use deploy VMs across different cloud frameworks using common deployment scripts. <br />
*Can deploy clusters concurrently over multiple clouds. <br />
*Deployments can be configured according to custom parameters (ex. number of nodes, services to install on the VM, etc...) <br />
*VM contextualization is performed by Slipstream orchestrator (a separately instantiated VM), using SSH or native RP contextualization methods. <br />
*Autoscaling capabilities will be implemented in 2014. Autoscaling will act at infrastructure level, using CPU/Disk/Memory metrics (not application metrix, ex. number of jobs in queue). <br />
*RPs don't need to configure new services. It uses native cloud APIs. <br />
*Provides EC2 (currently in beta) and SlipStream native REST API interface. <br />
*User do not need to have cloud credentials to instantiate VMs. Slipstream acts as account broker. <br />
*Does not provide accounting or cost information. <br />
*Test interface available on the FedCloud for users, to request access please contact [mailto:salvatore.pinto@egi.eu salvatore.pinto@egi.eu]<br />
<br />
|}<br />
<br />
=== Application Brokers ===<br />
<br />
{| width="90%" cellspacing="0" cellpadding="5" style="border:1px solid black;" class="wikitable"<br />
|- style="background-color:darkgray;"<br />
! Name <br />
! URL <br />
! Cloud SW Support <br />
! OCCI<br />
! External API <br />
! Functionalities <br />
! Effort required <br />
! Comments<br />
|-<br />
| COMPSs <br />
| http://www.bsc.es/compss <br />
| &nbsp; OpenNebula, Amazon, Azure, OpenStack <br />
| Yes, support of rOCCI servers and OCCI+OVF <br />
| OGF-BES SOAP<br />
| &nbsp;Automatic parallelization and orchestration of applications and services, elasticity, auto scaling <br />
| <span style="color:orange"> '''Medium'''</span> <br />
| <br />
*COMPSs allows the execution of applications on distributed infrastructures (grids, clusters, cloud). <br />
*Already used for the BioVeL/OpenBio use case. <br />
*Transparent support to different infrastructures; the user only provides his credentials. <br />
*Automatic selection of the VMs types dependending on the tasks constraints. <br />
*The number of VMs is dynamically adjusted to the current workload.<br />
<br />
|-<br />
| VMDIRAC <br />
| https://github.com/DIRACGrid/VMDIRAC/wiki <br />
| &nbsp; OpenNebula, OpenStack, CloudStack and Amazon EC2 <br />
| Yes, it supports rOCCI, OpenNebula "OCCI 0.8", Amazon EC2, OpenStack Nova 1.1 and CloudStack 2 APIs. <br />
|<br />
| Accounting, monitoring, brokering, scheduling, HEPiX and SSH based VM contextualisation, [https://github.com/DIRACGrid/VMDIRAC/wiki#vm-horizontal-auto-scaling-setup VM Horizontal Auto-scaling]. <br />
| <span style="color:orange"> '''Medium'''</span> <br />
| <br />
*rOCCI support with X509/VOMS auth. <br />
*In production: LHCb (OpenStack and OpenNebula) Belle (Amazon), Work in progress France Federated Cloud. <br />
*Web UI including VM browsing with VM monitoring, and VM Overview Plots (Load, RunningVM, RunnigVM by Endpoint, started jobs, data transfer, transfer files) <br />
*The number of VMs is dynamically adjusted to the current workload. <br />
*Automatic selection of the VMs types depending on the tasks constraints. <br />
*No necessary to install any pluging in the Cloud Managers, works with standard interfaces. <br />
*Separated user credentials are used for job running and VM operator credentials for VM management. <br />
*VMDIRAC developers are willing to collaborate actively with Fedcloud Taskforce.<br />
<br />
|}</div>
Asimon
https://wiki.egi.eu/w/index.php?title=Middleware_products_verified_for_the_support_of_IPv6&diff=62639
Middleware products verified for the support of IPv6
2013-12-06T09:18:13Z
<p>Asimon: </p>
<hr />
<div>{{Template:Op menubar}} {{Template:Middleware_menubar}} <br />
<br />
<br> The following tables collects the products tested so far during the UMD software provisioning process. <br />
<br />
<br> <br />
<br />
{| width="90%" cellspacing="0" cellpadding="5" class="wikitable" style="border:1px solid black;"<br />
|- style="background-color:darkgray;"<br />
! Product name <br />
! Version <br />
! Released in UMD update # <br />
! IPv6 support <br />
! Comments <br />
! GGUS ticket<br />
|-<br />
| CREAM <br />
| 1.16.2 <br />
| UMD3.0.0 UMD2.0.0 <br />
! align="centre" style="background: none repeat scroll 0% 0% Green;" | YES <br />
| <br />
| <br />
|-<br />
| DPM <br />
| 3.0.3 <br />
| UMD3.0.0 UMD2.0.0 <br />
! align="centre" style="background: none repeat scroll 0% 0% Orange;" | PARTIAL <br />
| srmv2.2 server does not bind to IPv6 socket. workaround available. <br />
| https://ggus.eu/ws/ticket_info.php?ticket=99458<br />
|-<br />
| BDII <br />
| 1.1.3 <br />
| UMD3.0.0 UMD2.0.0 <br />
! align="centre" style="background: none repeat scroll 0% 0% Green;" | YES <br />
| <br />
| <br />
|-<br />
| LFC <br />
| 1.8.7 <br />
| UMD3.0.0 UMD2.0.0 <br />
! align="centre" style="background: none repeat scroll 0% 0% Green;" | YES <br />
| <br />
| <br />
|-<br />
| VOMS-SERVER <br />
| 2.0.11 <br />
| UMD3.3.0 <br />
! align="centre" style="background: none repeat scroll 0% 0% Green;" | YES <br />
| <br />
| <br />
|-<br />
| UI <br />
| 3.5.2-1 <br />
| UMD3.x UMD2.x <br />
! align="centre" style="background: none repeat scroll 0% 0% Green;" | YES <br />
| <br />
| <br />
|-<br />
| StoRM <br />
| 1.11.2 <br />
| UMD3.2.1 <br />
! align="centre" style="background: none repeat scroll 0% 0% Orange;" | PARTIAL <br />
| srmv server does not bind to IPv6 socket. workaround available. <br />
| https://ggus.eu/ws/ticket_info.php?ticket=99461<br />
|}<br />
<br />
<br> Additional wiki page with the tests performed for the [[EGI-JRA1 IPv6 Readiness|operations tools]] by JRA1. <br />
<br />
[[Category:Middleware]]</div>
Asimon
https://wiki.egi.eu/w/index.php?title=Middleware_products_verified_for_the_support_of_IPv6&diff=62638
Middleware products verified for the support of IPv6
2013-12-06T09:17:26Z
<p>Asimon: </p>
<hr />
<div>{{Template:Op menubar}} {{Template:Middleware_menubar}} <br />
<br />
<br> The following tables collects the products tested so far during the UMD software provisioning process. <br />
<br />
<br> <br />
<br />
{| width="90%" cellspacing="0" cellpadding="5" class="wikitable" style="border:1px solid black;"<br />
|- style="background-color:darkgray;"<br />
! Product name <br />
! Version <br />
! Released in UMD update # <br />
! IPv6 support <br />
! Comments <br />
! GGUS ticket<br />
|-<br />
| CREAM <br />
| 1.16.2 <br />
| UMD3.0.0 UMD2.0.0 <br />
! align="centre" style="background: none repeat scroll 0% 0% Green;" | YES <br />
| <br />
| <br />
|-<br />
| DPM <br />
| 3.0.3 <br />
| UMD3.0.0 UMD2.0.0 <br />
! align="centre" style="background: none repeat scroll 0% 0% Orange;" | PARTIAL<br />
| srmv2.2 server does not bind to IPv6. workaround available.<br />
| https://ggus.eu/ws/ticket_info.php?ticket=99458<br />
|-<br />
| BDII <br />
| 1.1.3 <br />
| UMD3.0.0 UMD2.0.0 <br />
! align="centre" style="background: none repeat scroll 0% 0% Green;" | YES <br />
| <br />
| <br />
|-<br />
| LFC <br />
| 1.8.7 <br />
| UMD3.0.0 UMD2.0.0 <br />
! align="centre" style="background: none repeat scroll 0% 0% Green;" | YES <br />
| <br />
| <br />
|-<br />
| VOMS-SERVER <br />
| 2.0.11 <br />
| UMD3.3.0 <br />
! align="centre" style="background: none repeat scroll 0% 0% Green;" | YES <br />
| <br />
| <br />
|-<br />
| UI <br />
| 3.5.2-1 <br />
| UMD3.x UMD2.x <br />
! align="centre" style="background: none repeat scroll 0% 0% Green;" | YES<br />
| <br />
| <br />
|-<br />
| StoRM <br />
| 1.11.2 <br />
| UMD3.2.1 <br />
! align="centre" style="background: none repeat scroll 0% 0% Orange;" | PARTIAL<br />
| srmv server does not bind to IPv6. workaround available.<br />
| https://ggus.eu/ws/ticket_info.php?ticket=99461<br />
|}<br />
<br />
<br> Additional wiki page with the tests performed for the [[EGI-JRA1 IPv6 Readiness|operations tools]] by JRA1. <br />
<br />
[[Category:Middleware]]</div>
Asimon
https://wiki.egi.eu/w/index.php?title=Middleware_products_verified_for_the_support_of_IPv6&diff=61920
Middleware products verified for the support of IPv6
2013-11-12T13:06:30Z
<p>Asimon: </p>
<hr />
<div>{{Template:Op menubar}} {{Template:Middleware_menubar}} <br />
<br />
<br> The following tables collects the products tested so far during the UMD software provisioning process. <br />
<br />
<br> <br />
<br />
{| width="90%" cellspacing="0" cellpadding="5" class="wikitable" style="border:1px solid black;"<br />
|- style="background-color:darkgray;"<br />
! Product name <br />
! Version <br />
! Released in UMD update # <br />
! IPv6 support <br />
! Comments <br />
! GGUS ticket<br />
|-<br />
| CREAM <br />
| 1.16.2 <br />
| UMD3.0.0 UMD2.0.0 <br />
! align="centre" style="background: none repeat scroll 0% 0% Green;" | YES <br />
| <br />
| <br />
|-<br />
| DPM <br />
| 3.0.3 <br />
| UMD3.0.0 UMD2.0.0 <br />
! align="centre" style="background: none repeat scroll 0% 0% Green;" | YES <br />
| <br />
| <br />
|-<br />
| BDII <br />
| 1.1.3 <br />
| UMD3.0.0 UMD2.0.0 <br />
! align="centre" style="background: none repeat scroll 0% 0% Green;" | YES <br />
| <br />
| <br />
|-<br />
| LFC <br />
| 1.8.7 <br />
| UMD3.0.0 UMD2.0.0 <br />
! align="centre" style="background: none repeat scroll 0% 0% Green;" | YES <br />
| <br />
| <br />
|-<br />
| UI <br />
| 3.5.2-1 <br />
| UMD3.x UMD2.x <br />
! align="centre" style="background: none repeat scroll 0% 0% Orange;" | PARTIAL <br />
| lcg-* commands do not work with IPv6 <br />
| https://ggus.eu/ws/ticket_info.php?ticket=98806<br />
|}<br />
<br />
[[Category:Middleware]]</div>
Asimon
https://wiki.egi.eu/w/index.php?title=Middleware_products_verified_for_the_support_of_IPv6&diff=61910
Middleware products verified for the support of IPv6
2013-11-12T09:11:51Z
<p>Asimon: </p>
<hr />
<div>{{Template:Op menubar}} {{Template:Middleware_menubar}} <br />
<br />
<br> The following tables collects the products tested so far during the UMD software provisioning process. <br />
<br />
<br> <br />
<br />
{| width="90%" cellspacing="0" cellpadding="5" style="border:1px solid black;" class="wikitable"<br />
|- style="background-color:darkgray;"<br />
! Product name <br />
! Version <br />
! Released in UMD update # <br />
! IPv6 support <br />
! Comments <br />
! GGUS ticket<br />
|-<br />
| CREAM <br />
| 1.16.2 <br />
| UMD3.0.0 UMD2.0.0 <br />
! align="centre" style="background: none repeat scroll 0% 0% Green;" | YES <br />
| <br />
| <br />
|-<br />
| DPM <br />
| 3.0.3 <br />
| UMD3.0.0 UMD2.0.0 <br />
! align="centre" style="background: none repeat scroll 0% 0% Green;" | YES <br />
| <br />
| <br />
|-<br />
| BDII <br />
| 1.1.3 <br />
| UMD3.0.0 UMD2.0.0 <br />
! align="centre" style="background: none repeat scroll 0% 0% Green;" | YES <br />
| <br />
| <br />
|-<br />
| LFC <br />
| 1.8.7 <br />
| UMD3.0.0 UMD2.0.0 <br />
! align="centre" style="background: none repeat scroll 0% 0% Green;" | YES <br />
| <br />
| <br />
|-<br />
| UI <br />
| 3.5.2-1 <br />
| UMD3.x UMD2.x <br />
! align="centre" style="background: none repeat scroll 0% 0% Orange;" | PARTIAL <br />
| lcg-cr does not work with IPv6 <br />
| https://ggus.eu/ws/ticket_info.php?ticket=98806<br />
|}<br />
<br />
[[Category:Middleware]]</div>
Asimon
https://wiki.egi.eu/w/index.php?title=Middleware_products_verified_for_the_support_of_IPv6&diff=61903
Middleware products verified for the support of IPv6
2013-11-12T08:44:29Z
<p>Asimon: </p>
<hr />
<div>{{Template:Op menubar}} {{Template:Middleware_menubar}} <br />
<br />
<br> The following tables collects the products tested so far during the UMD software provisioning process. <br />
<br />
<br> <br />
<br />
{| width="90%" cellspacing="0" cellpadding="5" class="wikitable" style="border:1px solid black;"<br />
|- style="background-color:darkgray;"<br />
! Product name <br />
! Version <br />
! Released in UMD update # <br />
! IPv6 support <br />
! Comments <br />
! GGUS ticket<br />
|-<br />
| CREAM <br />
| 1.16.2 <br />
| UMD3.0.0 UMD2.0.0 <br />
! align="centre" style="background: none repeat scroll 0% 0% Green;" | YES <br />
| <br />
| <br />
|-<br />
| DPM <br />
| 3.0.3 <br />
| UMD3.0.0 UMD2.0.0 <br />
! align="centre" style="background: none repeat scroll 0% 0% Green;" | YES <br />
| <br />
| <br />
|-<br />
| BDII <br />
| 1.1.3 <br />
| UMD3.0.0 UMD2.0.0 <br />
! align="centre" style="background: none repeat scroll 0% 0% Green;" | YES <br />
| <br />
| <br />
|-<br />
| LFC <br />
| 1.8.7 <br />
| UMD3.0.0 UMD2.0.0 <br />
! align="centre" style="background: none repeat scroll 0% 0% Green;" | YES <br />
| <br />
| <br />
|-<br />
| UI <br />
| 3.5.2-1<br />
| UMD3.x UMD2.x<br />
! align="centre" style="background: none repeat scroll 0% 0% Red;" | NO <br />
| lcg-cr does not work with IPv6<br />
| https://ggus.eu/ws/ticket_info.php?ticket=98806<br />
|}<br />
<br />
[[Category:Middleware]]</div>
Asimon
https://wiki.egi.eu/w/index.php?title=RC_FORUM&diff=61880
RC FORUM
2013-11-11T10:06:27Z
<p>Asimon: </p>
<hr />
<div>{{Template:RC menubar}} {{TOC_right}} <br />
<br />
Grid and Cloud resource provisioning plans for new user communities and Research Infrastructures, 2014 <br />
<br />
{| border="1" class="wikitable sortable"<br />
|- style="background-color: lightgray;"<br />
| '''NGI''' <br />
| '''Resource Centre Name''' <br />
| '''Contact''' <br />
| '''Planned resources by April 2014''' <br />
Please specify resources that the RC will provide for each category (Grid storage, grid computing, cloud storage, cloud computing) <br />
<br />
| '''Planned resources by December 2014''' <br />
Please specify resources that the RC will provide for each category (Grid storage, grid computing, cloud storage, cloud computing) <br />
<br />
| '''Resource allocation policies and business models''' <br />
Provide information about the local policies for gaining access to the resources and the foreseen model (free, pay per use, etc.) <br />
<br />
| '''Area of expertise''' <br />
Areas of technical and user support expertise <br />
<br />
| '''National and international collaborations''' <br />
Current or planned collaborations with national/international user-oriented projects or Research Infrastructures <br />
<br />
|-<br />
| NGI_CZ <br />
| CESNET <br />
| M. Ruda <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
| NGI_DE <br />
| JUELICH, FhG <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
| NGI_GRNET <br />
| GRNET SA <br />
| K. Koumantaros&nbsp; <br />
| We will offer a&nbsp;% of our GRID and CLOUD infrastructure.&nbsp; <br />
| TBA <br />
| TBA <br />
| Operations, Monitoring,A/R, APPDB, Software Privisioning <br />
| <br />
EUDAT, <br />
<br />
PRACE, <br />
<br />
FORGE, <br />
<br />
CLARIN-GR, <br />
<br />
Stratuslab, <br />
<br />
Hellasgrid. <br />
<br />
CHAIN-RED <br />
<br />
GN3 <br />
<br />
Open Discovery Space <br />
<br />
GREENET <br />
<br />
LDA <br />
<br />
ICT-AGRI <br />
<br />
CELAR <br />
<br />
|-<br />
| NGI_HR <br />
| <br />
| D. Dobrenic <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
| NGI_SE <br />
| <br />
| J. Koster <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
| NGI_PT <br />
| NCG-INGRID-PT <br />
| G. Borges, J. Gomes <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
| NGI_ES <br />
| CSIC <br />
| J. Marco/I. Campos <br />
| <br />
Grid storage: ~2 PB <br />
<br />
Grid computing: ~4000 cores&nbsp; <br />
<br />
Cloud storage: ~1 PB&nbsp; <br />
<br />
Cloud computing: ~2000 cores <br />
<br />
| <span style="line-height: 1.5em;">Grid storage: ~2 PB</span> <br />
Grid computing: ~4000 cores&nbsp; <br />
<br />
Cloud storage: ~2 PB <br />
<br />
Cloud computing: ~4000 cores <br />
<br />
| <br />
Resource allocation by VOs /centers <br />
<br />
20% resources are open to projects agreed within NGI<br> <br />
<br />
10% resources prioritized under pay per use (at 0.05 euros/core for "external" users) <br />
<br />
| <br />
Cloud: OpenStack, VOMS <br />
<br />
Image Contextualization <br />
<br />
MPI/parallel framework <br />
<br />
Integration of supercomputing resources <br />
<br />
GPFS/HPC storage <br />
<br />
| <br />
LHC-WLCG <br />
<br />
LIFEWATCH <br />
<br />
PLANCK <br />
<br />
FET projects <br />
<br />
ICT projects <br />
<br />
SMEs projects (modeling, parallel) <br />
<br />
|-<br />
| NGI_ES <br />
| CESGA <br />
| I. Lopez/C. Fernandez <br />
| <br />
Grid storage: ~100 TB <br />
<br />
Grid computing: ~720 cores&nbsp; <br />
<br />
Cloud storage: ~10 TB&nbsp; <br />
<br />
Cloud computing: ~280 cores <br />
<br />
| <span style="line-height: 1.5em;">Grid storage: ~100 TB</span> <br />
Grid computing: ~720 cores&nbsp; <br />
<br />
Cloud storage: ~10 TB <br />
<br />
Cloud computing: ~280 cores <br />
<br />
| <br />
Resource allocation by VOs /centers <br />
<br />
20% resources are open to projects agreed within NGI<br> <br />
<br />
resources can be prioritized under pay per use (at 0.05 euros/core for external users) <br />
<br />
| <br />
Cloud: OpenNebula <br />
<br />
Image Contextualization <br />
<br />
MPI/parallel framework <br />
<br />
Integration of supercomputing resources <br />
<br />
Lustre <br />
<br />
Grid/Cloud Accounting<br />
<br />
Software provisioning<br />
<br />
| <br />
LHC-WLCG <br />
<br />
SMEs projects <br />
<br />
|-<br />
| NGI_ES <br />
| BIFI <br />
| A. Tarancon/R. Valles <br />
| - Grid storage: 4TB <br />
- Grid computing: 864 cores - Cloud storage: 4TB - Cloud computing: 432 cores <br />
<br />
| - Grid storage: 4TB <br />
- Grid computing: 864 cores - Cloud storage: 6TB - Cloud computing: 600 cores <br />
<br />
| The access to grid resources is free for research institutes <br />
and users that belong to research groups from University. The access to cloud resources is the same for researchers from some University or research groups but the companies have to pay depending on the resources they need. <br />
<br />
| We provide technical support for both, users and system administrators from <br />
other research institutes. One of this support is to fusion VO within EGI. <br />
<br />
| CloudSME -&gt; Collaboration with users and companies <br />
SCI-BUS -&gt; Development and deployment of Scientific Gateways and users support. <br />
<br />
|-<br />
| NGI_ES <br />
| UPVLC <br />
| I. Blanquer/M. Caballer <br />
| 90 Grid cores and 40 cloud virtual cores. 1TB of Grid Storage and 1TB of cloud storage. <br />
| 90 Grid cores and 100 cloud virtual cores. 1TB of Grid Storage and 1TB of cloud storage. <br />
| Free access to research groups from Universities and public research centres. For cloud infrastructures, we will request a short report on the purpose of the usage. We will offer additional services such as VM catalogues, automatic contextualization and automatic scaling. <br />
| We will provide technical support for users and application developers on exploiting the infrastructure and the services. <br />
| [http://www.eubrazilopenbio.eu EUBrazilOpenBio], [http://www.eubrazilcloudconnect.eu EUBrazilCC], CODECLOUD (National project).<br />
|-<br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|}</div>
Asimon
https://wiki.egi.eu/w/index.php?title=Middleware_products_verified_for_the_support_of_IPv6&diff=61859
Middleware products verified for the support of IPv6
2013-11-08T08:24:54Z
<p>Asimon: </p>
<hr />
<div>{{Template:Op menubar}} {{Template:Middleware_menubar}} <br />
<br />
<br> The following tables collects the products tested so far during the UMD software provisioning process. <br />
<br />
<br> <br />
<br />
{| width="90%" cellspacing="0" cellpadding="5" style="border:1px solid black;" class="wikitable"<br />
|- style="background-color:darkgray;"<br />
! Product name <br />
! Version <br />
! Released in UMD update # <br />
! IPv6 support <br />
! Comments <br />
! GGUS ticket<br />
|-<br />
| CREAM <br />
| 1.16.2 <br />
| UMD3.0.0 UMD2.0.0 <br />
! align="centre" style="background: none repeat scroll 0% 0% Green;" | YES <br />
| <br />
| <br />
|-<br />
| DPM <br />
| 3.0.3 <br />
| UMD3.0.0 UMD2.0.0 <br />
! align="centre" style="background: none repeat scroll 0% 0% Green;" | YES <br />
| <br />
| <br />
|-<br />
| BDII <br />
| 1.1.3 <br />
| UMD3.0.0 UMD2.0.0 <br />
! align="centre" style="background: none repeat scroll 0% 0% Green;" | YES <br />
| <br />
| <br />
|-<br />
| LFC <br />
| 1.8.7 <br />
| UMD3.0.0 UMD2.0.0 <br />
! align="centre" style="background: none repeat scroll 0% 0% Green;" | YES <br />
| <br />
| <br />
|}<br />
<br />
[[Category:Middleware]]</div>
Asimon
https://wiki.egi.eu/w/index.php?title=Middleware_products_verified_for_the_support_of_IPv6&diff=61858
Middleware products verified for the support of IPv6
2013-11-08T08:03:39Z
<p>Asimon: </p>
<hr />
<div>{{Template:Op menubar}} {{Template:Middleware_menubar}} <br />
<br />
<br> The following tables collects the products tested so far during the UMD software provisioning process. <br />
<br />
<br> <br />
<br />
{| width="90%" cellspacing="0" cellpadding="5" class="wikitable" style="border:1px solid black;"<br />
|- style="background-color:darkgray;"<br />
! Product name <br />
! Version <br />
! Released in UMD update # <br />
! IPv6 support <br />
! Comments <br />
! GGUS ticket<br />
|-<br />
| CREAM <br />
| 1.16.2 <br />
| UMD3.0.0 UMD2.0.0 <br />
! align="centre" style="background: none repeat scroll 0% 0% Green;" | YES <br />
| <br />
| <br />
|-<br />
| DPM <br />
| 3.0.3 <br />
| UMD3.0.0 UMD2.0.0 <br />
! align="centre" style="background: none repeat scroll 0% 0% Green;" | YES <br />
| <br />
| <br />
|-<br />
| BDII <br />
| 1.1.3 <br />
| UMD3.0.0 UMD2.0.0 <br />
! align="centre" style="background: none repeat scroll 0% 0% Green;" | YES <br />
| <br />
| <br />
|}<br />
<br />
[[Category:Middleware]]</div>
Asimon
https://wiki.egi.eu/w/index.php?title=Middleware_products_verified_for_the_support_of_IPv6&diff=61856
Middleware products verified for the support of IPv6
2013-11-08T08:00:53Z
<p>Asimon: </p>
<hr />
<div>{{Template:Op menubar}} {{Template:Middleware_menubar}} <br />
<br />
<br> The following tables collects the products tested so far during the UMD software provisioning process. <br />
<br />
<br> <br />
<br />
{| width="90%" cellspacing="0" cellpadding="5" style="border:1px solid black;" class="wikitable"<br />
|- style="background-color:darkgray;"<br />
! Product name <br />
! Version <br />
! Released in UMD update # <br />
! IPv6 support <br />
! Comments <br />
! GGUS ticket<br />
|-<br />
| UI <br />
| 3.0.3 <br />
| UMD3.0.0 UMD2.0.0<br />
! align="centre" style="background: none repeat scroll 0% 0% Green;" | YES <br />
| <br />
| <br />
|-<br />
| CREAM <br />
| 1.16.2 <br />
| UMD3.0.0 UMD2.0.0<br />
! align="centre" style="background: none repeat scroll 0% 0% Green;" | YES <br />
| <br />
| <br />
|-<br />
| DPM <br />
| 3.0.3 <br />
| UMD3.0.0 UMD2.0.0<br />
! align="centre" style="background: none repeat scroll 0% 0% Green;" | YES <br />
| <br />
| <br />
|-<br />
| BDII<br />
| 1.1.3<br />
| UMD3.0.0 UMD2.0.0<br />
! align="centre" style="background: none repeat scroll 0% 0% Green;" | YES <br />
| <br />
| <br />
|}<br />
<br />
[[Category:Middleware]]</div>
Asimon
https://wiki.egi.eu/w/index.php?title=Middleware_products_verified_for_the_support_of_IPv6&diff=61854
Middleware products verified for the support of IPv6
2013-11-07T14:47:51Z
<p>Asimon: </p>
<hr />
<div>{{Template:Op menubar}} {{Template:Middleware_menubar}} <br />
<br />
<br> The following tables collects the products tested so far during the UMD software provisioning process. <br />
<br />
<br> <br />
<br />
== UMD-2 ==<br />
<br />
{| width="90%" cellspacing="0" cellpadding="5" class="wikitable" style="border:1px solid black;"<br />
|- style="background-color:darkgray;"<br />
! Product name <br />
! Version <br />
! Released in UMD update # <br />
! IPv6 support <br />
! Comments <br />
! GGUS ticket<br />
|-<br />
| UI <br />
| <br />
| UMD2.4.0 <br />
! align="centre" style="background: none repeat scroll 0% 0% Green;" | YES <br />
| <br />
| <br />
|-<br />
| CREAM <br />
| <br />
| UMD2.4.0 <br />
! align="centre" style="background: none repeat scroll 0% 0% Green;" | YES <br />
| <br />
| <br />
|}<br />
<br />
<br> <br />
<br />
== UMD-3 ==<br />
<br />
{| width="90%" cellspacing="0" cellpadding="5" class="wikitable" style="border:1px solid black;"<br />
|- style="background-color:darkgray;"<br />
! Product name <br />
! Version <br />
! Released in UMD update # <br />
! IPv6 support <br />
! Comments <br />
! GGUS ticket<br />
|-<br />
| UI <br />
| 3.0.0-1 <br />
| UMD3.0.0 <br />
! align="centre" style="background: none repeat scroll 0% 0% Green;" | YES <br />
| <br />
| <br />
|-<br />
| CREAM <br />
| 3.0.0-1 <br />
| UMD3.0.0 <br />
! align="centre" style="background: none repeat scroll 0% 0% Green;" | YES <br />
| <br />
| <br />
|}<br />
<br />
[[Category:Middleware]]</div>
Asimon
https://wiki.egi.eu/w/index.php?title=Middleware_products_verified_for_the_support_of_IPv6&diff=61853
Middleware products verified for the support of IPv6
2013-11-07T14:46:57Z
<p>Asimon: Created page with "{{Template:Op menubar}} {{Template:Middleware_menubar}} <br> The following tables collects the products tested so far during the UMD software provisioning process. <br> == ..."</p>
<hr />
<div>{{Template:Op menubar}} {{Template:Middleware_menubar}} <br />
<br />
<br> The following tables collects the products tested so far during the UMD software provisioning process. <br />
<br />
<br> <br />
<br />
== UMD-2 ==<br />
<br />
{| width="90%" cellspacing="0" cellpadding="5" style="border:1px solid black;" class="wikitable"<br />
|- style="background-color:darkgray;"<br />
! Product name <br />
! Version <br />
! Released in UMD update # <br />
! IPv6 support <br />
! Comments <br />
! GGUS ticket<br />
|-<br />
| UI <br />
| <br />
| UMD2.4.0<br />
! align="centre" style="background: none repeat scroll 0% 0% Green;" | YES <br />
| <br />
| <br />
|-<br />
| CREAM<br />
| <br />
| UMD2.4.0 <br />
! align="centre" style="background: none repeat scroll 0% 0% Green;" | YES <br />
| <br />
| <br />
|-<br />
| LFC <br />
| 1.8.6 <br />
| UMD2.4.0 <br />
! align="centre" style="background: none repeat scroll 0% 0% Green;" | YES <br />
| Not tested yet <br />
| <br />
| <br />
|-<br />
| globus-myproxy <br />
| 5.9.1 <br />
| UMD2.4.0 <br />
! align="centre" style="background: none repeat scroll 0% 0% Green;" | YES <br />
| Not tested yet <br />
| <br />
| <br />
|-<br />
| VOMS <br />
| 2.0.10 <br />
| UMD2.4.0 <br />
! align="centre" style="background: none repeat scroll 0% 0% Green;" | YES <br />
! align="centre" style="background: none repeat scroll 0% 0% Red;" | NO <br />
| VOMS rfc proxies only work with SHA1 user certificates <br />
| [https://ggus.eu/ws/ticket_info.php?ticket=91389 GGUS #91389] (On Hold until EMI3)<br />
|-<br />
| UI <br />
| 2.0.1 <br />
| UMD2.3.0 <br />
! align="centre" style="background: none repeat scroll 0% 0% Green;" | YES <br />
! align="centre" style="background: none repeat scroll 0% 0% Green;" | YES <br />
| Available in production <br />
| <br />
|}<br />
<br />
<br> <br />
<br />
== UMD-3 ==<br />
<br />
{| width="90%" cellspacing="0" cellpadding="5" style="border:1px solid black;" class="wikitable"<br />
|- style="background-color:darkgray;"<br />
! Product name <br />
! Version <br />
! Released in UMD update # <br />
! IPv6 support <br />
! Comments <br />
! GGUS ticket<br />
|-<br />
| UI <br />
| 3.0.0-1 <br />
| UMD3.0.0<br />
! align="centre" style="background: none repeat scroll 0% 0% Green;" | YES <br />
| <br />
| <br />
|-<br />
| CREAM<br />
| 3.0.0-1 <br />
| UMD3.0.0<br />
! align="centre" style="background: none repeat scroll 0% 0% Green;" | YES <br />
| <br />
| <br />
|-<br />
| ARGUS <br />
| 1.6.0 <br />
| UMD3.0.0? <br />
! align="centre" style="background: none repeat scroll 0% 0% Green;" | YES <br />
! align="centre" style="background: none repeat scroll 0% 0% Green;" | YES <br />
| <br />
| <br />
|-<br />
| WN <br />
| 3.0.0-1 <br />
| UMD3.0.0? <br />
! align="centre" style="background: none repeat scroll 0% 0% Green;" | YES <br />
! align="centre" style="background: none repeat scroll 0% 0% Green;" | YES <br />
| (uses same VOMS clients as UI) <br />
| <br />
|-<br />
| LFC <br />
| 1.8.6 <br />
| UMD3.0.0? <br />
! align="centre" style="background: none repeat scroll 0% 0% Green;" | YES <br />
! align="centre" style="background: none repeat scroll 0% 0% Green;" | YES <br />
| <br />
| <br />
|-<br />
| glexec-wn <br />
| 1.2.1 <br />
| UMD3.0.0? <br />
! align="centre" style="background: none repeat scroll 0% 0% Green;" | YES <br />
! align="centre" style="background: none repeat scroll 0% 0% Green;" | YES <br />
| <br />
| <br />
|-<br />
| CREAM <br />
| 1.2.1-2 <br />
| UMD3? <br />
! align="centre" style="background: none repeat scroll 0% 0% Green;" | YES <br />
! align="centre" style="background: none repeat scroll 0% 0% Orange;" | PARTIAL <br />
| RFC proxies do not work using InputSandbox files. '''Workaround: voms-proxy-init -rfc -path_length -1 --voms &lt;VO&gt;''' <br />
| [https://ggus.eu/tech/ticket_show.php?ticket=93024 GGUS #93024]<br />
|}<br />
<br />
[[Category:Middleware]]</div>
Asimon
https://wiki.egi.eu/w/index.php?title=Fedcloud-tf:WorkGroups:Brokering&diff=60786
Fedcloud-tf:WorkGroups:Brokering
2013-10-16T07:56:52Z
<p>Asimon: </p>
<hr />
<div>{{Fedcloud-tf:Menu}} {{Fedcloud-tf:WorkGroups:Menu}} {{TOC_right}} <br />
<br />
<font color="red">Leader: Alvaro Simon, JR1 </font> <br />
<br />
== Collaborators ==<br />
<br />
{| border="1"<br />
|-<br />
! Role <br />
! Institution <br />
! Name<br />
|-<br />
| Collaborator <br />
| OeRC <br />
| Matteo Turilli<br />
|-<br />
| Collaborator <br />
| BSC <br />
| Daniele Lezzi<br />
|}<br />
<br />
== Scope ==<br />
<br />
This workgroup deals with the issues around cloud brokering. With 10+ resource providers lined up to be federated into the EGI cloud testbed, users need effective ways to access cloud resources. The goal is for a user to have a choice between a unified, abstracted view of the cloud testbed as a whole and the opportunity to target specific providers for their needs. As a consequence, this workgroup is concerned with both brokers and OCCI clients. <br />
<br />
== Roadmap ==<br />
<br />
*Collect information about existing solutions for cloud brokering compatible with the OCCI and CDMI management interfaces; <br />
*Collect information about existing solutions for OCCI and CDMI clients; <br />
*Make an inventory of the available solutions; <br />
*Choose a broker and a client for the testbed; <br />
*If possible, join the development teams of the chosen solutions to the task force; <br />
*Coordinate with the TF Resorce Providers to deploy the chosen solutions; <br />
*Extend the demo testbed addressing a real-life use case.<br />
<br />
== Clients Comparison Table ==<br />
<br />
{| width="90%" cellspacing="0" cellpadding="5" style="border:1px solid black;" class="wikitable"<br />
|- style="background-color:darkgray;"<br />
! Client/API <br />
! URL <br />
! OS <br />
! Support <br />
! OCCI/CDMI <br />
! Functionalities <br />
! Effort required <br />
! Comments<br />
|-<br />
| Hybridfox <br />
| http://code.google.com/p/hybridfox/ <br />
| Win/OS X/Linux <br />
| AWS/Eucalyptus/OpenStack/OpenNebula/HP Cloud <br />
| <span style="color:red"> '''NO'''</span> <br />
| Manage Images/Instances/Elastic IPs/Security Groups/Key-pairs <br />
| <span style="color:green"> '''Low'''</span> <br />
| Hybridfox does not support x509 auth, it uses EC2 auth for OpenNebula and OpenStack<br />
|-<br />
| DeltaCloud <br />
| http://deltacloud.apache.org <br />
| Win/OS X/Linux <br />
| EC2/Eucalyptus/OpenStack/OpenNebula/vSphere <br />
| <span style="color:red"> '''NO'''</span> <br />
| Create/Start/Stop/Reboot/Destroy instances <br />
| <span style="color:orange"> '''Medium'''</span> <br />
| DeltaCloud uses its own delta-cloud driver for each framework instead of OCCI. It provides storage support for S3, Warlus, Azure and Google Storage.<br />
|-<br />
| Aeolus <br />
| http://aeolusproject.org/about.html <br />
| Win/OS X/Linux <br />
| Same as DeltaCloud <br />
| <span style="color:red"> '''NO'''</span> <br />
| Create/Start/Stop/.. instances. Manage different instances and Images from different private, public, or hybrid cloud providers. <br />
| <span style="color:orange"> '''Medium'''</span> <br />
| Aeolus uses DeltaCloud cross-cloud abstraction library and it includes some extra functionalities. It includes Aeolus Conductor/Composer/Orchestrator/HA Manager<br />
|-<br />
| rOCCI (API) <br />
| http://dev.opennebula.org/projects/ogf-occi <br />
| Linux <br />
| OpenNebula/EC2 <br />
| <span style="color:green"> '''YES'''</span> <br />
| Create/Start/Stop/Reboot/Destroy instances. Upload and register an image. Network conf. x509 auth. <br />
| <span style="color:green"> '''Low'''</span> <br />
| rOCCI is an OCCI 1.1 implementation for OpenNebula 3.x<br />
|}<br />
<br />
== Cloud Brokering Solutions ==<br />
<br />
=== Resource Brokers ===<br />
<br />
{| width="90%" cellspacing="0" cellpadding="5" style="border:1px solid black;" class="wikitable"<br />
|- style="background-color:darkgray;"<br />
! Name <br />
! URL <br />
! Cloud SW Support <br />
! OCCI <br />
! Functionalities <br />
! Effort required <br />
! Comments<br />
|-<br />
| CompatibleOne <br />
| http://www.compatibleone.org/ <br />
| OpenStack, OpenNebula, Azure, Vcloud <br />
| Yes, supports OCCI, but implements his own OCCI interface for each of the stacks (PROCCI). <br />
| Accounting, Brokering, User management, Monitoring. <br />
| <span style="color:orange"> '''Medium'''</span> <br />
| <br />
*Compatible One is a complete plattform, with its own user management, accounting and monitoring, so it overlaps in some aspects with the ongoing work. <br />
*It does not expose an OCCI api, the user has to write its own XML files and send them to the broker. <br />
*The credentials for each of the connectors and providers have to be configured in advance by the administrator of the broker service. <br />
*The user has to specify in the manifests the cloud account that he wants to use, and the specific name of the image in the site. It seems that the purpose of CompatibleONE is to deploy and take care of a complete manifest description: A user wants 3 machines of type A in site FOO, and 2 machine of type B in site BAR, so he explicitly defines it in his manifests and CompatibleOne will deploy it on them.<br />
<br />
|-<br />
| VMDIRAC <br />
| https://github.com/DIRACGrid/VMDIRAC/wiki <br />
| &nbsp; OpenNebula, OpenStack, CloudStack and Amazon EC2 <br />
| Yes, it supports rOCCI, OpenNebula "OCCI 0.8", Amazon EC2, OpenStack Nova 1.1 and CloudStack 2 APIs. <br />
| Accounting, monitoring, brokering, scheduling, HEPiX and SSH based VM contextualisation, [https://github.com/DIRACGrid/VMDIRAC/wiki#vm-horizontal-auto-scaling-setup VM Horizontal Auto-scaling]. <br />
| <span style="color:orange"> '''Medium'''</span> <br />
| <br />
*rOCCI support with X509/VOMS auth. <br />
*In production: LHCb (OpenStack and OpenNebula) Belle (Amazon), Work in progress France Federated Cloud. <br />
*Web UI including VM browsing with VM monitoring, and VM Overview Plots (Load, RunningVM, RunnigVM by Endpoint, started jobs, data transfer, transfer files) <br />
*The number of VMs is dynamically adjusted to the current workload. <br />
*Automatic selection of the VMs types depending on the tasks constraints. <br />
*No necessary to install any pluging in the Cloud Managers, works with standard interfaces. <br />
*Separated user credentials are used for job running and VM operator credentials for VM management. <br />
*VMDIRAC developers are willing to collaborate actively with Fedcloud Taskforce.<br />
<br />
|-<br />
| SlipStream™ <br />
| http://sixsq.com/products/slipstream.html <br />
| StratusLab, OpenStack, Abiquo, CloudSigma and Amazon EC2 <br />
| Not yet, but it will supports OCCI in the future. It supports Cloud SW native APIs. <br />
| VM image creation and deployment, contextualisation, VM cluster automated deployments. <br />
| <span style="color:orange"> '''Medium'''</span> <br />
| <br />
*OCCI plugin is not available yet. (scheduled for January 2014, demo plugin scheduled for September 2013) <br />
*Acts as single interface and point of entrance to multiple clouds. Does not provides a brokering mechanism at application level. <br />
*It is able to use deploy VM acrosse different cloud frameworks using common deployment scripts. <br />
*Can deploy clusters concurrently over multiple clouds <br />
*Deployments can be configured according to custom parameters (ex. number of nodes, services to install on the VM, etc...) <br />
*VM contextualization is performed by Slipstream orchestrator (a separately instantiated VM), using SSH or native RP contextualization methods. <br />
*Autoscaling capabilities will be implemented in 2014. Autoscaling will act at infrastructure level, using CPU/Disk/Memory metrics (not application metrix, ex. number of jobs in queue). <br />
*RPs don't need to configure new services. It uses native cloud APIs. <br />
*Provides EC2 (currently in beta) and SlipStream native REST API interface. <br />
*User do not need to have cloud credentials to instantiate VMs. Slipstream acts as account broker. <br />
*Does not provide accounting or cost information. <br />
*StratusLab Marketplace support<br />
<br />
|}<br />
<br />
=== Application Brokers ===<br />
<br />
{| width="90%" cellspacing="0" cellpadding="5" style="border:1px solid black;" class="wikitable"<br />
|- style="background-color:darkgray;"<br />
! Name <br />
! URL <br />
! Cloud SW Support <br />
! OCCI <br />
! Functionalities <br />
! Effort required <br />
! Comments<br />
|-<br />
| COMPSs <br />
| http://www.bsc.es/compss <br />
| &nbsp; OpenNebula, Amazon, Azure, OpenStack <br />
| Yes, support of rOCCI servers and OCCI+OVF <br />
| &nbsp;Automatic parallelization and orchestration of applications and services, elasticity, auto scaling <br />
| <span style="color:orange"> '''Medium'''</span> <br />
| <br />
*COMPSs allows the execution of applications on distributed infrastructures (grids, clusters, cloud). <br />
*Already used for the BioVeL/OpenBio use case. <br />
*Transparent support to different infrastructures; the user only provides his credentials. <br />
*Automatic selection of the VMs types dependending on the tasks constraints. <br />
*The number of VMs is dynamically adjusted to the current workload.<br />
<br />
|-<br />
| VMDIRAC <br />
| https://github.com/DIRACGrid/VMDIRAC/wiki <br />
| &nbsp; OpenNebula, OpenStack, CloudStack and Amazon EC2 <br />
| Yes, it supports rOCCI, OpenNebula "OCCI 0.8", Amazon EC2, OpenStack Nova 1.1 and CloudStack 2 APIs. <br />
| Accounting, monitoring, brokering, scheduling, HEPiX and SSH based VM contextualisation, [https://github.com/DIRACGrid/VMDIRAC/wiki#vm-horizontal-auto-scaling-setup VM Horizontal Auto-scaling]. <br />
| <span style="color:orange"> '''Medium'''</span> <br />
| <br />
*rOCCI support with X509/VOMS auth. <br />
*In production: LHCb (OpenStack and OpenNebula) Belle (Amazon), Work in progress France Federated Cloud. <br />
*Web UI including VM browsing with VM monitoring, and VM Overview Plots (Load, RunningVM, RunnigVM by Endpoint, started jobs, data transfer, transfer files) <br />
*The number of VMs is dynamically adjusted to the current workload. <br />
*Automatic selection of the VMs types depending on the tasks constraints. <br />
*No necessary to install any pluging in the Cloud Managers, works with standard interfaces. <br />
*Separated user credentials are used for job running and VM operator credentials for VM management. <br />
*VMDIRAC developers are willing to collaborate actively with Fedcloud Taskforce.<br />
<br />
|}</div>
Asimon
https://wiki.egi.eu/w/index.php?title=Fedcloud-tf:WorkGroups:Brokering&diff=60785
Fedcloud-tf:WorkGroups:Brokering
2013-10-16T07:51:44Z
<p>Asimon: </p>
<hr />
<div>{{Fedcloud-tf:Menu}} {{Fedcloud-tf:WorkGroups:Menu}} {{TOC_right}} <br />
<br />
<font color="red">Leader: Alvaro Simon, JR1 </font> <br />
<br />
== Collaborators ==<br />
<br />
{| border="1"<br />
|-<br />
! Role <br />
! Institution <br />
! Name<br />
|-<br />
| Collaborator <br />
| OeRC <br />
| Matteo Turilli<br />
|-<br />
| Collaborator <br />
| BSC <br />
| Daniele Lezzi<br />
|}<br />
<br />
== Scope ==<br />
<br />
This workgroup deals with the issues around cloud brokering. With 10+ resource providers lined up to be federated into the EGI cloud testbed, users need effective ways to access cloud resources. The goal is for a user to have a choice between a unified, abstracted view of the cloud testbed as a whole and the opportunity to target specific providers for their needs. As a consequence, this workgroup is concerned with both brokers and OCCI clients. <br />
<br />
== Roadmap ==<br />
<br />
*Collect information about existing solutions for cloud brokering compatible with the OCCI and CDMI management interfaces; <br />
*Collect information about existing solutions for OCCI and CDMI clients; <br />
*Make an inventory of the available solutions; <br />
*Choose a broker and a client for the testbed; <br />
*If possible, join the development teams of the chosen solutions to the task force; <br />
*Coordinate with the TF Resorce Providers to deploy the chosen solutions; <br />
*Extend the demo testbed addressing a real-life use case.<br />
<br />
== Clients Comparison Table ==<br />
<br />
{| width="90%" cellspacing="0" cellpadding="5" style="border:1px solid black;" class="wikitable"<br />
|- style="background-color:darkgray;"<br />
! Client/API <br />
! URL <br />
! OS <br />
! Support <br />
! OCCI/CDMI <br />
! Functionalities <br />
! Effort required <br />
! Comments<br />
|-<br />
| Hybridfox <br />
| http://code.google.com/p/hybridfox/ <br />
| Win/OS X/Linux <br />
| AWS/Eucalyptus/OpenStack/OpenNebula/HP Cloud <br />
| <span style="color:red"> '''NO'''</span> <br />
| Manage Images/Instances/Elastic IPs/Security Groups/Key-pairs <br />
| <span style="color:green"> '''Low'''</span> <br />
| Hybridfox does not support x509 auth, it uses EC2 auth for OpenNebula and OpenStack<br />
|-<br />
| DeltaCloud <br />
| http://deltacloud.apache.org <br />
| Win/OS X/Linux <br />
| EC2/Eucalyptus/OpenStack/OpenNebula/vSphere <br />
| <span style="color:red"> '''NO'''</span> <br />
| Create/Start/Stop/Reboot/Destroy instances <br />
| <span style="color:orange"> '''Medium'''</span> <br />
| DeltaCloud uses its own delta-cloud driver for each framework instead of OCCI. It provides storage support for S3, Warlus, Azure and Google Storage.<br />
|-<br />
| Aeolus <br />
| http://aeolusproject.org/about.html <br />
| Win/OS X/Linux <br />
| Same as DeltaCloud <br />
| <span style="color:red"> '''NO'''</span> <br />
| Create/Start/Stop/.. instances. Manage different instances and Images from different private, public, or hybrid cloud providers. <br />
| <span style="color:orange"> '''Medium'''</span> <br />
| Aeolus uses DeltaCloud cross-cloud abstraction library and it includes some extra functionalities. It includes Aeolus Conductor/Composer/Orchestrator/HA Manager<br />
|-<br />
| rOCCI (API) <br />
| http://dev.opennebula.org/projects/ogf-occi <br />
| Linux <br />
| OpenNebula/EC2 <br />
| <span style="color:green"> '''YES'''</span> <br />
| Create/Start/Stop/Reboot/Destroy instances. Upload and register an image. Network conf. x509 auth. <br />
| <span style="color:green"> '''Low'''</span> <br />
| rOCCI is an OCCI 1.1 implementation for OpenNebula 3.x<br />
|}<br />
<br />
== Cloud Brokering Solutions ==<br />
<br />
=== Resource Brokers ===<br />
{| width="90%" cellspacing="0" cellpadding="5" style="border:1px solid black;" class="wikitable"<br />
|- style="background-color:darkgray;"<br />
! Name <br />
! URL <br />
! Cloud SW Support <br />
! OCCI <br />
! Functionalities <br />
! Effort required <br />
! Comments<br />
|-<br />
| CompatibleOne <br />
| http://www.compatibleone.org/ <br />
| OpenStack, OpenNebula, Azure, Vcloud <br />
| Yes, supports OCCI, but implements his own OCCI interface for each of the stacks (PROCCI). <br />
| Accounting, Brokering, User management, Monitoring. <br />
| <span style="color:orange"> '''Medium'''</span> <br />
| <br />
*Compatible One is a complete plattform, with its own user management, accounting and monitoring, so it overlaps in some aspects with the ongoing work. <br />
*It does not expose an OCCI api, the user has to write its own XML files and send them to the broker. <br />
*The credentials for each of the connectors and providers have to be configured in advance by the administrator of the broker service. <br />
*The user has to specify in the manifests the cloud account that he wants to use, and the specific name of the image in the site. It seems that the purpose of CompatibleONE is to deploy and take care of a complete manifest description: A user wants 3 machines of type A in site FOO, and 2 machine of type B in site BAR, so he explicitly defines it in his manifests and CompatibleOne will deploy it on them.<br />
<br />
|-<br />
| COMPSs <br />
| http://www.bsc.es/compss <br />
| &nbsp; OpenNebula, Amazon, Azure, OpenStack <br />
| Yes, support of rOCCI servers and OCCI+OVF <br />
| &nbsp;Automatic parallelization and orchestration of applications and services, elasticity, auto scaling <br />
| <span style="color:orange"> '''Medium'''</span> <br />
| <br />
*COMPSs allows the execution of applications on distributed infrastructures (grids, clusters, cloud). <br />
*Already used for the BioVeL/OpenBio use case. <br />
*Transparent support to different infrastructures; the user only provides his credentials. <br />
*Automatic selection of the VMs types dependending on the tasks constraints. <br />
*The number of VMs is dynamically adjusted to the current workload.<br />
<br />
|-<br />
| VMDIRAC <br />
| https://github.com/DIRACGrid/VMDIRAC/wiki <br />
| &nbsp; OpenNebula, OpenStack, CloudStack and Amazon EC2 <br />
| Yes, it supports rOCCI, OpenNebula "OCCI 0.8", Amazon EC2, OpenStack Nova 1.1 and CloudStack 2 APIs. <br />
| Accounting, monitoring, brokering, scheduling, HEPiX and SSH based VM contextualisation, [https://github.com/DIRACGrid/VMDIRAC/wiki#vm-horizontal-auto-scaling-setup VM Horizontal Auto-scaling]. <br />
| <span style="color:orange"> '''Medium'''</span> <br />
| <br />
*rOCCI support with X509/VOMS auth. <br />
*In production: LHCb (OpenStack and OpenNebula) Belle (Amazon), Work in progress France Federated Cloud. <br />
*Web UI including VM browsing with VM monitoring, and VM Overview Plots (Load, RunningVM, RunnigVM by Endpoint, started jobs, data transfer, transfer files) <br />
*The number of VMs is dynamically adjusted to the current workload. <br />
*Automatic selection of the VMs types depending on the tasks constraints. <br />
*No necessary to install any pluging in the Cloud Managers, works with standard interfaces. <br />
*Separated user credentials are used for job running and VM operator credentials for VM management. <br />
*VMDIRAC developers are willing to collaborate actively with Fedcloud Taskforce.<br />
<br />
|-<br />
| SlipStream™ <br />
| http://sixsq.com/products/slipstream.html <br />
| StratusLab, OpenStack, Abiquo, CloudSigma and Amazon EC2 <br />
| Not yet, but it will supports OCCI in the future. It supports Cloud SW native APIs. <br />
| VM image creation and deployment, contextualisation, VM cluster automated deployments. <br />
| <span style="color:orange"> '''Medium'''</span> <br />
| <br />
*OCCI plugin is not available yet. (scheduled for January 2014, demo plugin scheduled for September 2013) <br />
*Acts as single interface and point of entrance to multiple clouds. Does not provides a brokering mechanism at application level. <br />
*It is able to use deploy VM acrosse different cloud frameworks using common deployment scripts. <br />
*Can deploy clusters concurrently over multiple clouds <br />
*Deployments can be configured according to custom parameters (ex. number of nodes, services to install on the VM, etc...) <br />
*VM contextualization is performed by Slipstream orchestrator (a separately instantiated VM), using SSH or native RP contextualization methods. <br />
*Autoscaling capabilities will be implemented in 2014. Autoscaling will act at infrastructure level, using CPU/Disk/Memory metrics (not application metrix, ex. number of jobs in queue). <br />
*RPs don't need to configure new services. It uses native cloud APIs. <br />
*Provides EC2 (currently in beta) and SlipStream native REST API interface. <br />
*User do not need to have cloud credentials to instantiate VMs. Slipstream acts as account broker. <br />
*Does not provide accounting or cost information. <br />
*StratusLab Marketplace support<br />
<br />
|}<br />
<br />
=== Application Brokers ===</div>
Asimon
https://wiki.egi.eu/w/index.php?title=EGI_Quality_Criteria_Verification&diff=60042
EGI Quality Criteria Verification
2013-09-23T11:08:50Z
<p>Asimon: </p>
<hr />
<div>{{SWProv menubar}} {{SWProv QA submenu}} {{TOC_right}} <br />
<br />
== Objective ==<br />
<br />
The main objective of the TSA2.3 is to verify the quality of the software provided by the TP before entering the SR phase and going to production. By doing so we prevent that software that might work enters into the SR and even goes into production but that doesn´t follow the quality criteria defined in TSA2.2. Some of the reasons for doing the verification before the software enters the stage rollout are: <br />
<br />
- Check that the bugs reported in the previous release of the software have been corrected (work in collaboration with DMSU) by the TP. <br />
<br />
- Software can work well in the SR but might not have all the functionalities required <br />
<br />
- Software might not be safe, well documented, or have the necessary installation rules or licenses <br />
<br />
== The Verification Process ==<br />
<br />
When a new product is available, the TP has to follow the [[NSRW IMPLEMENTATION RT|NSRW]]. Once the software is correctly uploaded to the repository, the release enters into the verification phase. The requirements are that the TP has to provide all the necessary information to the verifier (QCV) so that the QCV can assess that the TP has tested in advance the quality of the software. Depending on the type of release, different actions will be taken by the QCV, Verification process is described in detail in the [[EGI Verifier Guideline]]. <br />
<br />
== QC Verification Reports ==<br />
<br />
RT workflow and Verification Templates links are available in this page. First of all verifiers must check QC service mapping to know which test must be verified for each product. This service mapping is available here [https://documents.egi.eu/document/418 QC Verification service mapping] and Verification/Executive Summary templates are available here: [https://documents.egi.eu/document/417 QC Verification Templates]. <br />
<br />
Verifiers must fill all required fields for each product and write a Verification process summary into Executive Summary, this summary should include: <br />
<br />
*A short summary of the installation and configuration process: Installation and configuration were successful?, If not explain any issue or bug found. If the product was rejected explain why. <br />
*If its necessary Verifiers should include a comment for StageRollout: Configuration changes or minor issues found verifying the product. <br />
*If a new QC is necessary and is not included, Verifiers must write a comment to SA2.2 to change current QC.<br />
<br />
<br> <br />
<br />
== UMD Release Candidate Testing ==<br />
<br />
Before each UMD release the verification team checks the new RC. To perform this task SA2.3 VMs have included the [https://github.com/alvarosimon/RC_tester RC_testing script]. This script is available after each SA2 VM instantiation (into /root/configuration_templates/tools directory). This script is able to detect any package inconsistency after UMD RC repo configuration. The RC testing process is as follows: <br />
<br />
*Verifier should instantiate different Linux flavours VM. For UMD case SL5, SL6 and debian. <br />
*Install UMD RC repo files from UMDx RC page. <br />
*Check RC_tester "PRODUCTS" array. '''This array must be updated to include all UMD products!''' <br />
*It is recommended to use ''screen'' program before RC_tester execution. RC tests take about 2h/3h to finish (depends on OS used and the number of products). <br />
*Run ''RC_tester'' and follows its instructions. <br />
*''RC_tester'' generates several logs into log directory, after its execution SA2 verifier should check: <br />
**''installator_OK.log'': List of metapackages installed correctly. <br />
**''installator_ERROR.log'': List of metapackages which contain any issue. <br />
**''&lt;PRODUCT_NAME&gt;_OUTPUT.log'': Complete Product installation log. <br />
**''&lt;PRODUCT_NAME&gt;_postupdate.log'': Info about product update execution. It detects any issue updating current UMD products.<br />
<br />
<br> <br />
<br />
== Verification Work Effort Metrics ==<br />
<br />
Each verification process and change is registered by EGI RT. A complete report is generated on a daily basis each midnight. The XLS file can be downloaded from here [https://rt.egi.eu/rt/SA2/sa2-sw-rel-verification-metrics.xls SA2 Verification Metrics] <br />
<br />
<br> <br />
<br />
== Verification Team ==<br />
<br />
Verifiers team is updated for each UMD release and it is available here: [https://documents.egi.eu/document/514 SA2.3 Verifiers List]. All verifiers are included in the [https://www.egi.eu/sso/groupView/sw-rel-qc SSO sw-rel-qc group] that includes a mailing list and permissions to modify RT tickets related with the verification process. <br />
<br />
== Reference Documents ==<br />
<br />
{| border="1" cellspacing="0" cellpadding="3" style="border: 1px solid black;" class="wikitable sortable"<br />
|- align="left" style="background: none repeat scroll 0% 0% Lightgray;"<br />
! DocDB link <br />
! Release Date <br />
! Document<br />
|-<br />
| [https://documents.egi.eu/document/1700 QCv5] <br />
| 08. 05. 2013 <br />
| UMD Quality Criteria<br />
|-<br />
| [https://documents.egi.eu/document/418 418] <br />
| 08. 05. 2013 <br />
| UMD Products service mapping<br />
|-<br />
| [https://documents.egi.eu/document/417 417] <br />
| 08. 05. 2013 <br />
| QC Verification Templates<br />
|}<br />
<br />
== Metrics ==<br />
<br />
{| border="1" cellspacing="0" cellpadding="3" style="border: 1px solid black;" class="wikitable sortable"<br />
|- align="left" style="background: none repeat scroll 0% 0% Lightgray;"<br />
! Metric <br />
! Description<br />
|-<br />
| M.SA2.4 <br />
| Number of new releases validated against defined criteria: Measures the workload on the validation team.<br />
|-<br />
| M.SA2.5 <br />
| Mean time taken to validate a releas: Indicates how responsive the team is to validating releases.<br />
|-<br />
| M.SA2.6 <br />
| Number of releases failing validation: Indicates the quality assurance process of the software providers.<br />
|}<br />
<br />
== SLAs ==<br />
<br />
EGI SLAs negotiated with the TPs <br />
<br />
[https://documents.egi.eu/document/461 EMI-EGI SLA] <br />
<br />
== Verification engineer skill matrix ==<br />
<br />
{| border="1" class="wikitable" style="text-align: center;"<br />
|+ Verification Cheat Sheet <br />
|-<br />
! width="200" align="left" | Product\Institute <br />
! width="75" | CESGA <br />
! width="75" | IFCA <br />
! width="75" | IFIC <br />
! width="75" | INFN <br />
! width="75" | IN2P3 <br />
! width="75" | JÜLICH <br />
! width="75" | LIP <br />
! width="75" | BADWB <br />
! width="75" | UTC-N <br />
! width="75" | CSC <br />
! width="75" | GRNET <br />
! width="75" | RAL <br />
! width="75" | FZU <br />
! width="300" style="background: none repeat scroll 0% 0% Gray;" | COMMENTS<br />
|-<br />
! align="left" | EMI ARC CE <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI ARC compute cli <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI ARC Infosys <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI dCache <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI gLite MPI <br />
| * <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI CREAM_torque <br />
| * <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI CREAM_lsf <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI EMIR <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
|-<br />
! align="left" | EMI WMS <br />
| * <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI LB <br />
| * <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI FTS <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
|-<br />
! align="left" | EMI DPM <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI LFC_mySQL <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI LFC_Oracle <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI StoRM <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI APEL <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI DGAS <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI BDII <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI UI <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI PX <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI VOMS_mySQL <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" style="background: none repeat scroll 0% 0% Red;" | EMI VOMS_Oracle <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| No verifiers available yet. Oracle training required.<br />
|-<br />
! align="left" style="background: none repeat scroll 0% 0% Red;" | EMI HYDRA <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| No verifiers available yet.<br />
|-<br />
! align="left" style="background: none repeat scroll 0% 0% Red;" | EMI Wnodes <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| No verifiers available yet.<br />
|-<br />
! align="left" style="background: none repeat scroll 0% 0% Red;" | EMI NAGIOS <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| No verifiers available yet.<br />
|-<br />
! align="left" style="background: none repeat scroll 0% 0% Red;" | EMI Pseudonymity <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| No verifiers available yet.<br />
|-<br />
! align="left" | EMI ARGUS <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI UNICORE TSI <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI UNICORE WS <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI UNICORE Client <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI UNICORE Registry <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI UNICORE Gateway <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI UNICORE Hila <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI UNICORE xuudb <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI UNICORE Uvos <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI AMGA <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | IGE SAGA-SD <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| No verifiers available yet.<br />
|-<br />
! align="left" | IGE GRAM5 <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | IGE GSISSH <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | IGE GridFTP <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | IGE myProxy <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | IGE RLS <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | IGE GridWay <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | IGE SAM <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | IGE OGSA-DAI <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | IGE Security <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | IGE Gridsafe <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|}<br />
<br />
<br> <br />
<br />
[https://www.egi.eu/earlyAdopters/table Early Adopters list] <br />
<br />
[https://www.egi.eu/earlyAdopters/teams Early Adopters per UMD product]</div>
Asimon
https://wiki.egi.eu/w/index.php?title=Federated_AAI_Requirements&diff=59750
Federated AAI Requirements
2013-09-10T07:07:45Z
<p>Asimon: </p>
<hr />
<div>This page tracks resource providers' requirements regarding AAI. RPs may have different requirements for authenticating users. We'll try to track the pieces of information that are required at each site to guide decisions about which solutions and configurations are required for the federation. Optional attributes are marked in parentheses. Please consider if these attributes are required to be known directly at each request for new resources or only through a registering authorisation body, i.e. as a resource provider you are able to get this information through a fully documented procedure not necessarily for each submitted instance request.<br> <br />
<br />
{| border="1" width="200" cellspacing="1" cellpadding="1"<br />
|-<br />
! scope="col" | RP<br> <br />
! scope="col" | Full Name<br> <br />
! scope="col" | Email<br> <br />
! scope="col" | Nationality<br> <br />
! scope="col" | ePPN <br />
! scope="col" | Organization <br />
! scope="col" | Other (Please add column before this one)<br> <br />
! scope="col" | Attributes may be derived<br />
|-<br />
| <br />
BSC<br> <br />
<br />
| align="center" | <br> <br />
| align="center" | <br> <br />
| align="center" | <br> <br />
| align="center" | <br />
| align="center" | <br />
| align="center" | <br> <br />
| align="center" | &nbsp;?<br />
|-<br />
| CESGA<br> <br />
| align="center" | x <br />
| align="center" | x <br />
| align="center" | x <br />
| align="center" | <br />
| align="center" | x<br />
| align="center" | <br> <br />
| align="center" | &nbsp;?<br />
|-<br />
| CESNET<br> <br />
| align="center" | x<br> <br />
| align="center" | x<br> <br />
| align="center" | <br> <br />
| align="center" | x <br />
| align="center" | (x) <br />
| align="center" | <br> <br />
| align="center" | &nbsp;?<br />
|-<br />
| CETA-CIEMAT<br> <br />
| align="center" | <br> <br />
| align="center" | <br> <br />
| align="center" | <br> <br />
| align="center" | <br />
| align="center" | <br />
| align="center" | <br> <br />
| align="center" | &nbsp;?<br />
|-<br />
| Cyfronet<br> <br />
| align="center" | <br> <br />
| align="center" | <br> <br />
| align="center" | <br> <br />
| align="center" | <br />
| align="center" | <br />
| align="center" | <br> <br />
| align="center" | &nbsp;?<br />
|-<br />
| FZ Jülich<br> <br />
| align="center" | x<br> <br />
| align="center" | x<br> <br />
| align="center" | x<br> <br />
| align="center" | <br />
| align="center" | <br />
| align="center" | <br> <br />
| align="center" | &nbsp;?<br />
|-<br />
| GRIF<br> <br />
| align="center" | <br> <br />
| align="center" | <br> <br />
| align="center" | <br> <br />
| align="center" | <br />
| align="center" | <br />
| align="center" | <br> <br />
| align="center" | &nbsp;?<br />
|-<br />
| GRNET<br> <br />
| align="center" | <br> <br />
| align="center" | <br> <br />
| align="center" | <br> <br />
| align="center" | <br />
| align="center" | <br />
| align="center" | <br> <br />
| align="center" | &nbsp;?<br />
|-<br />
| GWDG<br> <br />
| align="center" | <br> <br />
| align="center" | <br> <br />
| align="center" | <br> <br />
| align="center" | <br />
| align="center" | <br />
| align="center" | <br> <br />
| align="center" | &nbsp;?<br />
|-<br />
| IFCA<br> <br />
| align="center" | <br> <br />
| align="center" | <br> <br />
| align="center" | <br> <br />
| align="center" | <br />
| align="center" | <br />
| align="center" | <br> <br />
| align="center" | &nbsp;?<br />
|-<br />
| IGI <br />
| align="center" | <br />
| align="center" | <br />
| align="center" | <br />
| align="center" | <br />
| align="center" | <br />
| align="center" | <br />
| align="center" | &nbsp;?<br />
|-<br />
| IPHC<br> <br />
| align="center" | <br> <br />
| align="center" | <br> <br />
| align="center" | <br> <br />
| align="center" | <br />
| align="center" | <br />
| align="center" | <br> <br />
| align="center" | &nbsp;?<br />
|-<br />
| CC-IN2P3<br> <br />
| align="center" | <br> <br />
| align="center" | <br> <br />
| align="center" | <br> <br />
| align="center" | <br />
| align="center" | <br />
| align="center" | <br> <br />
| align="center" | &nbsp;?<br />
|-<br />
| Oxford<br> <br />
| align="center" | <br> <br />
| align="center" | <br> <br />
| align="center" | <br> <br />
| align="center" | <br />
| align="center" | <br />
| align="center" | <br> <br />
| align="center" | &nbsp;?<br />
|-<br />
| SARA<br> <br />
| align="center" | <br> <br />
| align="center" | <br> <br />
| align="center" | <br> <br />
| align="center" | <br />
| align="center" | <br />
| align="center" | <br> <br />
| align="center" | &nbsp;?<br />
|-<br />
| STFC<br> <br />
| align="center" | <br> <br />
| align="center" | <br> <br />
| align="center" | <br> <br />
| align="center" | <br />
| align="center" | <br />
| align="center" | <br> <br />
| align="center" | &nbsp;?<br />
|-<br />
| TCD<br> <br />
| align="center" | <br> <br />
| align="center" | <br> <br />
| align="center" | <br> <br />
| align="center" | <br />
| align="center" | <br />
| align="center" | <br> <br />
| align="center" | &nbsp;?<br />
|-<br />
| KTH<br> <br />
| align="center" | x<br> <br />
| align="center" | x<br> <br />
| align="center" | x<br> <br />
| align="center" | x <br />
| align="center" | (x) <br />
| align="center" | <br> <br />
| align="center" | &nbsp;?<br />
|-<br />
| SZTAKI<br> <br />
| align="center" | <br> <br />
| align="center" | <br> <br />
| align="center" | <br> <br />
| align="center" | <br />
| align="center" | <br />
| align="center" | <br> <br />
| align="center" | &nbsp;?<br />
|-<br />
| INFN-Napoli<br> <br />
| align="center" | <br> <br />
| align="center" | <br> <br />
| align="center" | <br> <br />
| align="center" | <br />
| align="center" | <br />
| align="center" | <br> <br />
| align="center" | &nbsp;?<br />
|-<br />
| IISAS<br> <br />
| align="center" | X<br> <br />
| align="center" | X<br> <br />
| align="center" | <br> <br />
| align="center" | <br />
| align="center" | X<br> <br />
| align="center" | <br> <br />
| align="center" | &nbsp;?<br />
|-<br />
| PLOCAN<br> <br />
| align="center" | <br> <br />
| align="center" | <br> <br />
| align="center" | <br> <br />
| align="center" | <br />
| align="center" | <br />
| align="center" | <br> <br />
| align="center" | &nbsp;?<br />
|-<br />
| 100 Percent IT Ltd<br> <br />
| align="center" | <br> <br />
| align="center" | <br> <br />
| align="center" | <br> <br />
| align="center" | <br />
| align="center" | <br />
| align="center" | <br> <br />
| align="center" | &nbsp;?<br />
|}<br />
<br />
<br></div>
Asimon
https://wiki.egi.eu/w/index.php?title=Middleware_products_verified_for_the_support_of_SHA-2_proxies_and_certificates&diff=59694
Middleware products verified for the support of SHA-2 proxies and certificates
2013-09-09T08:58:08Z
<p>Asimon: </p>
<hr />
<div>{{Template:Op menubar}} {{Template:Middleware_menubar}} <br />
<br />
<br> Starting from January 2013, as part of the [[EGI Quality Criteria Dissemination|UMD quality criteria]] products requiring authentication are tested for the support of SHA-2. The following tables collects the products tested so far during the UMD software provisioning process. <br />
<br />
More information in the [[SHA-2 support middleware baseline]] page. <br />
<br />
<br> <br />
<br />
== UMD-2 ==<br />
<br />
{| width="90%" cellspacing="0" cellpadding="5" class="wikitable" style="border:1px solid black;"<br />
|- style="background-color:darkgray;"<br />
! Product name <br />
! Version <br />
! Released in UMD update # <br />
! SHA-2 support <br />
! RFC proxies support <br />
! Comments <br />
! GGUS ticket<br />
|-<br />
| globus-gsissh <br />
| 5.5.4 <br />
| UMD2.4.0 <br />
! align="centre" style="background: none repeat scroll 0% 0% Green;" | YES <br />
! align="centre" style="background: none repeat scroll 0% 0% Green;" | YES <br />
| <br />
| <br />
|-<br />
| DPM <br />
| 1.8.6 <br />
| UMD2.4.0 <br />
! align="centre" style="background: none repeat scroll 0% 0% Green;" | YES <br />
| Not tested yet <br />
| <br />
| <br />
|-<br />
| LFC <br />
| 1.8.6 <br />
| UMD2.4.0 <br />
! align="centre" style="background: none repeat scroll 0% 0% Green;" | YES <br />
| Not tested yet <br />
| <br />
| <br />
|-<br />
| globus-myproxy <br />
| 5.9.1 <br />
| UMD2.4.0 <br />
! align="centre" style="background: none repeat scroll 0% 0% Green;" | YES <br />
| Not tested yet <br />
| <br />
| <br />
|-<br />
| VOMS <br />
| 2.0.10 <br />
| UMD2.4.0 <br />
! align="centre" style="background: none repeat scroll 0% 0% Green;" | YES <br />
! align="centre" style="background: none repeat scroll 0% 0% Red;" | NO <br />
| VOMS rfc proxies only work with SHA1 user certificates <br />
| [https://ggus.eu/ws/ticket_info.php?ticket=91389 GGUS #91389] (On Hold until EMI3)<br />
|-<br />
| UI <br />
| 2.0.1 <br />
| UMD2.3.0 <br />
! align="centre" style="background: none repeat scroll 0% 0% Green;" | YES <br />
! align="centre" style="background: none repeat scroll 0% 0% Green;" | YES <br />
| Available in production <br />
| <br />
|-<br />
| globus-GridFTP <br />
| 5.2.3 <br />
| UMD2.4.1? <br />
! align="centre" style="background: none repeat scroll 0% 0% Green;" | YES <br />
| Not tested yet <br />
| Not available in production yet <br />
| <br />
|-<br />
| globus-gsisshterm <br />
| 1.3.4 <br />
| UMD2.4.1? <br />
! align="centre" style="background: none repeat scroll 0% 0% Red;" | NO <br />
! align="centre" style="background: none repeat scroll 0% 0% Green;" | YES <br />
| Uses a jGlobus version not compatible with SHA2 <br />
| [https://ggus.eu/ws/ticket_info.php?ticket=90815 GGUS #90815]<br />
|-<br />
| CREAM <br />
| 1.1.0-4 <br />
| UMD2.4.1 <br />
! align="centre" style="background: none repeat scroll 0% 0% Green;" | YES <br />
! align="centre" style="background: none repeat scroll 0% 0% Orange;" | PARTIAL <br />
| RFC proxies do not work using InputSandbox files. '''Workaround: voms-proxy-init -rfc -path_length -1 --voms &lt;VO&gt;''' <br />
| [https://ggus.eu/tech/ticket_show.php?ticket=93024 GGUS #93024]<br />
|}<br />
<br />
<br> <br />
<br />
== UMD-3 ==<br />
<br />
{| width="90%" cellspacing="0" cellpadding="5" class="wikitable" style="border:1px solid black;"<br />
|- style="background-color:darkgray;"<br />
! Product name <br />
! Version <br />
! Released in UMD update # <br />
! SHA-2 support <br />
! RFC proxies support <br />
! Comments <br />
! GGUS ticket<br />
|-<br />
| VOMS <br />
| 3.0.0-1 <br />
| UMD3.0.0? <br />
! align="centre" style="background: none repeat scroll 0% 0% Green;" | YES <br />
! align="centre" style="background: none repeat scroll 0% 0% Orange;" | PARTIAL <br />
| VOMS rfc proxies work with SHA1 and SHA2 user certificates. <br />
RFC proxies are created but are not usable <br />
<br />
| https://savannah.cern.ch/bugs/?101122<br />
|-<br />
| UI <br />
| 3.0.0-1 <br />
| UMD3.0.0? <br />
! align="centre" style="background: none repeat scroll 0% 0% Green;" | YES <br />
! align="centre" style="background: none repeat scroll 0% 0% Green;" | YES <br />
| <br />
VOMS rfc proxies work with SHA1 and SHA2 user certificates. <br />
<br />
'''NOTE: CREAM 2 is still not compatible with RFC proxies''' <br />
<br />
| <br />
|-<br />
| ARGUS <br />
| 1.6.0 <br />
| UMD3.0.0? <br />
! align="centre" style="background: none repeat scroll 0% 0% Green;" | YES <br />
! align="centre" style="background: none repeat scroll 0% 0% Green;" | YES <br />
| <br />
| <br />
|-<br />
| WN <br />
| 3.0.0-1 <br />
| UMD3.0.0? <br />
! align="centre" style="background: none repeat scroll 0% 0% Green;" | YES <br />
! align="centre" style="background: none repeat scroll 0% 0% Green;" | YES <br />
| (uses same VOMS clients as UI) <br />
| <br />
|-<br />
| LFC <br />
| 1.8.6 <br />
| UMD3.0.0? <br />
! align="centre" style="background: none repeat scroll 0% 0% Green;" | YES <br />
! align="centre" style="background: none repeat scroll 0% 0% Green;" | YES <br />
| <br />
| <br />
|-<br />
| glexec-wn <br />
| 1.2.1 <br />
| UMD3.0.0? <br />
! align="centre" style="background: none repeat scroll 0% 0% Green;" | YES <br />
! align="centre" style="background: none repeat scroll 0% 0% Green;" | YES <br />
| <br />
| <br />
|-<br />
| CREAM <br />
| 1.2.1-2 <br />
| UMD3? <br />
! align="centre" style="background: none repeat scroll 0% 0% Green;" | YES <br />
! align="centre" style="background: none repeat scroll 0% 0% Orange;" | PARTIAL <br />
| RFC proxies do not work using InputSandbox files. '''Workaround: voms-proxy-init -rfc -path_length -1 --voms &lt;VO&gt;''' <br />
| [https://ggus.eu/tech/ticket_show.php?ticket=93024 GGUS #93024]<br />
|-<br />
| WMS <br />
| 3.5.0-5 <br />
| UMD3 <br />
| Not tested yet <br />
! align="centre" style="background: none repeat scroll 0% 0% Green;" | YES <br />
| <br />
| <br />
|-<br />
| UNICORE Gateway <br />
| 5.0.0 <br />
| UMD3 <br />
| align="centre" style="background: none repeat scroll 0% 0% Green;" | YES <br />
| not tested yet <br />
| <br />
| <br />
|-<br />
| UNICORE Registry <br />
| 6.0.0 <br />
| UMD3 <br />
| align="centre" style="background: none repeat scroll 0% 0% Green;" | YES <br />
| not tested yet <br />
| <br />
| <br />
|-<br />
| UNICORE unicorex <br />
| 6.0.0 <br />
| UMD3 <br />
| align="centre" style="background: none repeat scroll 0% 0% Green;" | YES <br />
| not tested yet <br />
| <br />
| <br />
|-<br />
| UNICORE xuudb <br />
| 2.0.0 <br />
| UMD3 <br />
| align="centre" style="background: none repeat scroll 0% 0% Green;" | YES <br />
| not tested yet <br />
| <br />
| <br />
|-<br />
| UNICORE client <br />
| 6.0.0 <br />
| UMD3 <br />
| align="centre" style="background: none repeat scroll 0% 0% Green;" | YES <br />
| not tested yet <br />
| <br />
| <br />
|-<br />
| UNICORE tsi <br />
| 6.1.0 <br />
| UMD3 <br />
| align="centre" style="background: none repeat scroll 0% 0% Green;" | YES <br />
| not tested yet <br />
| <br />
| <br />
|-<br />
| dCache <br />
| 2.6.5 <br />
| Not yet released (target: UMD3) <br />
| align="centre" style="background: none repeat scroll 0% 0% Green;" | YES <br />
! align="centre" style="background: none repeat scroll 0% 0% Orange;" | PARTIAL<br />
| RFC proxies do not work from EMI3 UIs.<br />
| [https://ggus.eu/ws/ticket_info.php?ticket=97134 GGUS #97134]<br />
|}<br />
<br />
[[Category:Middleware]]</div>
Asimon
https://wiki.egi.eu/w/index.php?title=EGI_Quality_Criteria_Verification&diff=59244
EGI Quality Criteria Verification
2013-08-22T10:58:54Z
<p>Asimon: </p>
<hr />
<div>{{SWProv menubar}} {{SWProv QA submenu}} {{TOC_right}} <br />
<br />
== Objective ==<br />
<br />
The main objective of the TSA2.3 is to verify the quality of the software provided by the TP before entering the SR phase and going to production. By doing so we prevent that software that might work enters into the SR and even goes into production but that doesn´t follow the quality criteria defined in TSA2.2. Some of the reasons for doing the verification before the software enters the stage rollout are: <br />
<br />
- Check that the bugs reported in the previous release of the software have been corrected (work in collaboration with DMSU) by the TP. <br />
<br />
- Software can work well in the SR but might not have all the functionalities required <br />
<br />
- Software might not be safe, well documented, or have the necessary installation rules or licenses <br />
<br />
== The Verification Process ==<br />
<br />
When a new product is available, the TP has to follow the [[NSRW IMPLEMENTATION RT|NSRW]]. Once the software is correctly uploaded to the repository, the release enters into the verification phase. The requirements are that the TP has to provide all the necessary information to the verifier (QCV) so that the QCV can assess that the TP has tested in advance the quality of the software. Depending on the type of release, different actions will be taken by the QCV, Verification process is described in detail in the [[EGI Verifier Guideline]]. <br />
<br />
== QC Verification Reports ==<br />
<br />
RT workflow and Verification Templates links are available in this page. First of all verifiers must check QC service mapping to know which test must be verified for each product. This service mapping is available here [https://documents.egi.eu/document/418 QC Verification service mapping] and Verification/Executive Summary templates are available here: [https://documents.egi.eu/document/417 QC Verification Templates]. <br />
<br />
Verifiers must fill all required fields for each product and write a Verification process summary into Executive Summary, this summary should include: <br />
<br />
*A short summary of the installation and configuration process: Installation and configuration were successful?, If not explain any issue or bug found. If the product was rejected explain why. <br />
*If its necessary Verifiers should include a comment for StageRollout: Configuration changes or minor issues found verifying the product. <br />
*If a new QC is necessary and is not included, Verifiers must write a comment to SA2.2 to change current QC.<br />
<br />
<br> <br />
<br />
== UMD Release Candidate Testing ==<br />
<br />
Before each UMD release the verification team checks the new RC. To perform this task SA2.3 VMs have included the [https://github.com/alvarosimon/RC_tester RC_testing script]. This script is available after each SA2 VM instantiation (into /root/configuration_templates/tools directory). This script is able to detect any package inconsistency after UMD RC repo configuration. The RC testing process is as follows: <br />
<br />
*Verifier should instantiate different Linux flavours VM. For UMD case SL5, SL6 and debian. <br />
*Install UMD RC repo files from UMDx RC page. <br />
*Check RC_tester "PRODUCTS" array. '''This array must be updated to include all UMD products!''' <br />
*It is recommended to use ''screen'' program before RC_tester execution. RC tests take about 2h/3h to finish (depends on OS used and the number of products). <br />
*Run ''RC_tester'' and follows its instructions. <br />
*''RC_tester'' generates several logs into log directory, after its execution SA2 verifier should check: <br />
**''installator_OK.log'': List of metapackages installed correctly. <br />
**''installator_ERROR.log'': List of metapackages which contain any issue. <br />
**''&lt;PRODUCT_NAME&gt;_OUTPUT.log'': Complete Product installation log. <br />
**''&lt;PRODUCT_NAME&gt;_postupdate.log'': Info about product update execution. It detects any issue updating current UMD products.<br />
<br />
<br> <br />
<br />
== Verification Work Effort Metrics ==<br />
<br />
Each verification process and change is registered by EGI RT. A complete report is generated on a daily basis each midnight. The XLS file can be downloaded from here [https://rt.egi.eu/rt/SA2/sa2-sw-rel-verification-metrics.xls SA2 Verification Metrics] <br />
<br />
<br> <br />
<br />
== Verification Team ==<br />
<br />
Verifiers team is updated for each UMD release and it is available here: [https://documents.egi.eu/document/514 SA2.3 Verifiers List]. All verifiers are included in the [https://www.egi.eu/sso/groupView/sw-rel-qc SSO sw-rel-qc group] that includes a mailing list and permissions to modify RT tickets related with the verification process. <br />
<br />
== Reference Documents ==<br />
<br />
{| border="1" cellspacing="0" cellpadding="3" style="border: 1px solid black;" class="wikitable sortable"<br />
|- align="left" style="background: none repeat scroll 0% 0% Lightgray;"<br />
! DocDB link <br />
! Release Date <br />
! Document<br />
|-<br />
| [https://documents.egi.eu/document/1700 QCv5] <br />
| 08. 05. 2013 <br />
| UMD Quality Criteria<br />
|-<br />
| [https://documents.egi.eu/document/418 418] <br />
| 08. 05. 2013 <br />
| UMD Products service mapping<br />
|-<br />
| [https://documents.egi.eu/document/417 417] <br />
| 08. 05. 2013 <br />
| QC Verification Templates<br />
|}<br />
<br />
== Metrics ==<br />
<br />
{| border="1" cellspacing="0" cellpadding="3" style="border: 1px solid black;" class="wikitable sortable"<br />
|- align="left" style="background: none repeat scroll 0% 0% Lightgray;"<br />
! Metric <br />
! Description<br />
|-<br />
| M.SA2.4 <br />
| Number of new releases validated against defined criteria: Measures the workload on the validation team.<br />
|-<br />
| M.SA2.5 <br />
| Mean time taken to validate a releas: Indicates how responsive the team is to validating releases.<br />
|-<br />
| M.SA2.6 <br />
| Number of releases failing validation: Indicates the quality assurance process of the software providers.<br />
|}<br />
<br />
== SLAs ==<br />
<br />
EGI SLAs negotiated with the TPs <br />
<br />
[https://documents.egi.eu/document/461 EMI-EGI SLA] <br />
<br />
== Verification engineer skill matrix ==<br />
<br />
{| border="1" class="wikitable" style="text-align: center;"<br />
|+ Verification Cheat Sheet <br />
|-<br />
! width="200" align="left" | Product\Institute <br />
! width="75" | CESGA <br />
! width="75" | IFCA <br />
! width="75" | IFIC <br />
! width="75" | INFN <br />
! width="75" | IN2P3 <br />
! width="75" | JÜLICH <br />
! width="75" | LIP <br />
! width="75" | BADWB <br />
! width="75" | UTC-N <br />
! width="75" | UZH <br />
! width="75" | GRNET <br />
! width="75" | RAL <br />
! width="75" | FZU <br />
! width="300" style="background: none repeat scroll 0% 0% Gray;" | COMMENTS<br />
|-<br />
! align="left" | EMI ARC CE <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI ARC compute cli <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI ARC Infosys <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI dCache <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI gLite MPI <br />
| * <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI CREAM_torque <br />
| * <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI CREAM_lsf <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI EMIR <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
|-<br />
! align="left" | EMI WMS <br />
| * <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI LB <br />
| * <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI FTS <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
|-<br />
! align="left" | EMI DPM <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI LFC_mySQL <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI LFC_Oracle <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI StoRM <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI APEL <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI DGAS <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI BDII <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI UI <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI PX <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI VOMS_mySQL <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" style="background: none repeat scroll 0% 0% Red;" | EMI VOMS_Oracle <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| No verifiers available yet. Oracle training required.<br />
|-<br />
! align="left" style="background: none repeat scroll 0% 0% Red;" | EMI HYDRA <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| No verifiers available yet.<br />
|-<br />
! align="left" style="background: none repeat scroll 0% 0% Red;" | EMI Wnodes <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| No verifiers available yet.<br />
|-<br />
! align="left" style="background: none repeat scroll 0% 0% Red;" | EMI NAGIOS <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| No verifiers available yet.<br />
|-<br />
! align="left" style="background: none repeat scroll 0% 0% Red;" | EMI Pseudonymity <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| No verifiers available yet.<br />
|-<br />
! align="left" | EMI ARGUS <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI UNICORE TSI <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI UNICORE WS <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI UNICORE Client <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI UNICORE Registry <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI UNICORE Gateway <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI UNICORE Hila <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI UNICORE xuudb <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI UNICORE Uvos <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI AMGA <br />
| <br />
| <br />
| <br />
| *<br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | IGE SAGA-SD <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| No verifiers available yet.<br />
|-<br />
! align="left" | IGE GRAM5 <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | IGE GSISSH <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | IGE GridFTP <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | IGE myProxy <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | IGE RLS <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | IGE GridWay <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | IGE SAM <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | IGE OGSA-DAI <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | IGE Security <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | IGE Gridsafe <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|}<br />
<br />
<br> <br />
<br />
[https://www.egi.eu/earlyAdopters/table Early Adopters list] <br />
<br />
[https://www.egi.eu/earlyAdopters/teams Early Adopters per UMD product]</div>
Asimon
https://wiki.egi.eu/w/index.php?title=EGI_Quality_Criteria_Verification&diff=59218
EGI Quality Criteria Verification
2013-08-20T11:25:44Z
<p>Asimon: </p>
<hr />
<div>{{SWProv menubar}} {{SWProv QA submenu}} {{TOC_right}} <br />
<br />
== Objective ==<br />
<br />
The main objective of the TSA2.3 is to verify the quality of the software provided by the TP before entering the SR phase and going to production. By doing so we prevent that software that might work enters into the SR and even goes into production but that doesn´t follow the quality criteria defined in TSA2.2. Some of the reasons for doing the verification before the software enters the stage rollout are: <br />
<br />
- Check that the bugs reported in the previous release of the software have been corrected (work in collaboration with DMSU) by the TP. <br />
<br />
- Software can work well in the SR but might not have all the functionalities required <br />
<br />
- Software might not be safe, well documented, or have the necessary installation rules or licenses <br />
<br />
== The Verification Process ==<br />
<br />
When a new product is available, the TP has to follow the [[NSRW IMPLEMENTATION RT|NSRW]]. Once the software is correctly uploaded to the repository, the release enters into the verification phase. The requirements are that the TP has to provide all the necessary information to the verifier (QCV) so that the QCV can assess that the TP has tested in advance the quality of the software. Depending on the type of release, different actions will be taken by the QCV, Verification process is described in detail in the [[EGI Verifier Guideline]]. <br />
<br />
== QC Verification Reports ==<br />
<br />
RT workflow and Verification Templates links are available in this page. First of all verifiers must check QC service mapping to know which test must be verified for each product. This service mapping is available here [https://documents.egi.eu/document/418 QC Verification service mapping] and Verification/Executive Summary templates are available here: [https://documents.egi.eu/document/417 QC Verification Templates]. <br />
<br />
Verifiers must fill all required fields for each product and write a Verification process summary into Executive Summary, this summary should include: <br />
<br />
*A short summary of the installation and configuration process: Installation and configuration were successful?, If not explain any issue or bug found. If the product was rejected explain why. <br />
*If its necessary Verifiers should include a comment for StageRollout: Configuration changes or minor issues found verifying the product. <br />
*If a new QC is necessary and is not included, Verifiers must write a comment to SA2.2 to change current QC.<br />
<br />
<br> <br />
<br />
== UMD Release Candidate Testing ==<br />
<br />
Before each UMD release the verification team checks the new RC. To perform this task SA2.3 VMs have included the [https://github.com/alvarosimon/RC_tester RC_testing script]. This script is available after each SA2 VM instantiation (into /root/configuration_templates/tools directory). This script is able to detect any package inconsistency after UMD RC repo configuration. The RC testing process is as follows: <br />
<br />
*Verifier should instantiate different Linux flavours VM. For UMD case SL5, SL6 and debian. <br />
*Install UMD RC repo files from UMDx RC page. <br />
*Check RC_tester "PRODUCTS" array. '''This array must be updated to include all UMD products!''' <br />
*It is recommended to use ''screen'' program before RC_tester execution. RC tests take about 2h/3h to finish (depends on OS used and the number of products). <br />
*Run ''RC_tester'' and follows its instructions. <br />
*''RC_tester'' generates several logs into log directory, after its execution SA2 verifier should check: <br />
**''installator_OK.log'': List of metapackages installed correctly. <br />
**''installator_ERROR.log'': List of metapackages which contain any issue. <br />
**''&lt;PRODUCT_NAME&gt;_OUTPUT.log'': Complete Product installation log. <br />
**''&lt;PRODUCT_NAME&gt;_postupdate.log'': Info about product update execution. It detects any issue updating current UMD products.<br />
<br />
<br> <br />
<br />
== Verification Work Effort Metrics ==<br />
<br />
Each verification process and change is registered by EGI RT. A complete report is generated on a daily basis each midnight. The XLS file can be downloaded from here [https://rt.egi.eu/rt/SA2/sa2-sw-rel-verification-metrics.xls SA2 Verification Metrics] <br />
<br />
<br> <br />
<br />
== Verification Team ==<br />
<br />
Verifiers team is updated for each UMD release and it is available here: [https://documents.egi.eu/document/514 SA2.3 Verifiers List]. All verifiers are included in the [https://www.egi.eu/sso/groupView/sw-rel-qc SSO sw-rel-qc group] that includes a mailing list and permissions to modify RT tickets related with the verification process. <br />
<br />
== Reference Documents ==<br />
<br />
{| border="1" cellspacing="0" cellpadding="3" style="border: 1px solid black;" class="wikitable sortable"<br />
|- align="left" style="background: none repeat scroll 0% 0% Lightgray;"<br />
! DocDB link <br />
! Release Date <br />
! Document<br />
|-<br />
| [https://documents.egi.eu/document/1700 QCv5] <br />
| 08. 05. 2013 <br />
| UMD Quality Criteria<br />
|-<br />
| [https://documents.egi.eu/document/418 418] <br />
| 08. 05. 2013 <br />
| UMD Products service mapping<br />
|-<br />
| [https://documents.egi.eu/document/417 417] <br />
| 08. 05. 2013 <br />
| QC Verification Templates<br />
|}<br />
<br />
== Metrics ==<br />
<br />
{| border="1" cellspacing="0" cellpadding="3" style="border: 1px solid black;" class="wikitable sortable"<br />
|- align="left" style="background: none repeat scroll 0% 0% Lightgray;"<br />
! Metric <br />
! Description<br />
|-<br />
| M.SA2.4 <br />
| Number of new releases validated against defined criteria: Measures the workload on the validation team.<br />
|-<br />
| M.SA2.5 <br />
| Mean time taken to validate a releas: Indicates how responsive the team is to validating releases.<br />
|-<br />
| M.SA2.6 <br />
| Number of releases failing validation: Indicates the quality assurance process of the software providers.<br />
|}<br />
<br />
== SLAs ==<br />
<br />
EGI SLAs negotiated with the TPs <br />
<br />
[https://documents.egi.eu/document/461 EMI-EGI SLA] <br />
<br />
== Verification engineer skill matrix ==<br />
<br />
{| border="1" class="wikitable" style="text-align: center;"<br />
|+ Verification Cheat Sheet <br />
|-<br />
! width="200" align="left" | Product\Institute <br />
! width="75" | CESGA <br />
! width="75" | IFCA <br />
! width="75" | IFIC <br />
! width="75" | INFN <br />
! width="75" | IN2P3 <br />
! width="75" | JÜLICH <br />
! width="75" | LIP <br />
! width="75" | BADWB <br />
! width="75" | UTC-N <br />
! width="75" | UZH <br />
! width="75" | GRNET <br />
! width="75" | RAL <br />
! width="75" | FZU <br />
! width="300" style="background: none repeat scroll 0% 0% Gray;" | COMMENTS<br />
|-<br />
! align="left" | EMI ARC CE <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI ARC compute cli <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI ARC Infosys <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI dCache <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI gLite MPI <br />
| * <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI CREAM_torque <br />
| * <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI CREAM_lsf <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI EMIR <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
|-<br />
! align="left" | EMI WMS <br />
| * <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI LB <br />
| * <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI FTS <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
|-<br />
! align="left" | EMI DPM <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI LFC_mySQL <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI LFC_Oracle <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI StoRM <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI APEL <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI DGAS <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI BDII <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI UI <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI PX <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI VOMS_mySQL <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" style="background: none repeat scroll 0% 0% Red;" | EMI VOMS_Oracle <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| No verifiers available yet. Oracle training required.<br />
|-<br />
! align="left" style="background: none repeat scroll 0% 0% Red;" | EMI HYDRA <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| No verifiers available yet.<br />
|-<br />
! align="left" style="background: none repeat scroll 0% 0% Red;" | EMI Wnodes <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| No verifiers available yet.<br />
|-<br />
! align="left" style="background: none repeat scroll 0% 0% Red;" | EMI NAGIOS <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| No verifiers available yet.<br />
|-<br />
! align="left" style="background: none repeat scroll 0% 0% Red;" | EMI Pseudonymity <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| No verifiers available yet.<br />
|-<br />
! align="left" | EMI ARGUS <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI UNICORE TSI <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI UNICORE WS <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI UNICORE Client <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI UNICORE Registry <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI UNICORE Gateway <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI UNICORE Hila <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI UNICORE xuudb <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI UNICORE Uvos <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI AMGA <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | IGE SAGA-SD <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| No verifiers available yet.<br />
|-<br />
! align="left" | IGE GRAM5 <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | IGE GSISSH <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | IGE GridFTP <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | IGE myProxy <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | IGE RLS <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | IGE GridWay <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | IGE SAM <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | IGE OGSA-DAI <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | IGE Security <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | IGE Gridsafe <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|}<br />
<br />
<br> <br />
<br />
[https://www.egi.eu/earlyAdopters/table Early Adopters list] <br />
<br />
[https://www.egi.eu/earlyAdopters/teams Early Adopters per UMD product]</div>
Asimon
https://wiki.egi.eu/w/index.php?title=EGI_Quality_Criteria_Verification&diff=59217
EGI Quality Criteria Verification
2013-08-20T11:25:22Z
<p>Asimon: </p>
<hr />
<div>{{SWProv menubar}} {{SWProv QA submenu}} {{TOC_right}} <br />
<br />
== Objective ==<br />
<br />
The main objective of the TSA2.3 is to verify the quality of the software provided by the TP before entering the SR phase and going to production. By doing so we prevent that software that might work enters into the SR and even goes into production but that doesn´t follow the quality criteria defined in TSA2.2. Some of the reasons for doing the verification before the software enters the stage rollout are: <br />
<br />
- Check that the bugs reported in the previous release of the software have been corrected (work in collaboration with DMSU) by the TP. <br />
<br />
- Software can work well in the SR but might not have all the functionalities required <br />
<br />
- Software might not be safe, well documented, or have the necessary installation rules or licenses <br />
<br />
== The Verification Process ==<br />
<br />
When a new product is available, the TP has to follow the [[NSRW IMPLEMENTATION RT|NSRW]]. Once the software is correctly uploaded to the repository, the release enters into the verification phase. The requirements are that the TP has to provide all the necessary information to the verifier (QCV) so that the QCV can assess that the TP has tested in advance the quality of the software. Depending on the type of release, different actions will be taken by the QCV, Verification process is described in detail in the [[EGI Verifier Guideline]]. <br />
<br />
== QC Verification Reports ==<br />
<br />
RT workflow and Verification Templates links are available in this page. First of all verifiers must check QC service mapping to know which test must be verified for each product. This service mapping is available here [https://documents.egi.eu/document/418 QC Verification service mapping] and Verification/Executive Summary templates are available here: [https://documents.egi.eu/document/417 QC Verification Templates]. <br />
<br />
Verifiers must fill all required fields for each product and write a Verification process summary into Executive Summary, this summary should include: <br />
<br />
*A short summary of the installation and configuration process: Installation and configuration were successful?, If not explain any issue or bug found. If the product was rejected explain why. <br />
*If its necessary Verifiers should include a comment for StageRollout: Configuration changes or minor issues found verifying the product. <br />
*If a new QC is necessary and is not included, Verifiers must write a comment to SA2.2 to change current QC.<br />
<br />
<br> <br />
<br />
== UMD Release Candidate Testing ==<br />
<br />
Before each UMD release the verification team checks the new RC. To perform this task SA2.3 VMs have included the [[https://github.com/alvarosimon/RC_tester RC_testing script]]. This script is available after each SA2 VM instantiation (into /root/configuration_templates/tools directory). This script is able to detect any package inconsistency after UMD RC repo configuration. The RC testing process is as follows: <br />
<br />
*Verifier should instantiate different Linux flavours VM. For UMD case SL5, SL6 and debian. <br />
*Install UMD RC repo files from UMDx RC page. <br />
*Check RC_tester "PRODUCTS" array. '''This array must be updated to include all UMD products!''' <br />
*It is recommended to use ''screen'' program before RC_tester execution. RC tests take about 2h/3h to finish (depends on OS used and the number of products). <br />
*Run ''RC_tester'' and follows its instructions. <br />
*''RC_tester'' generates several logs into log directory, after its execution SA2 verifier should check: <br />
**''installator_OK.log'': List of metapackages installed correctly. <br />
**''installator_ERROR.log'': List of metapackages which contain any issue. <br />
**''&lt;PRODUCT_NAME&gt;_OUTPUT.log'': Complete Product installation log. <br />
**''&lt;PRODUCT_NAME&gt;_postupdate.log'': Info about product update execution. It detects any issue updating current UMD products.<br />
<br />
<br> <br />
<br />
== Verification Work Effort Metrics ==<br />
<br />
Each verification process and change is registered by EGI RT. A complete report is generated on a daily basis each midnight. The XLS file can be downloaded from here [https://rt.egi.eu/rt/SA2/sa2-sw-rel-verification-metrics.xls SA2 Verification Metrics] <br />
<br />
<br> <br />
<br />
== Verification Team ==<br />
<br />
Verifiers team is updated for each UMD release and it is available here: [https://documents.egi.eu/document/514 SA2.3 Verifiers List]. All verifiers are included in the [https://www.egi.eu/sso/groupView/sw-rel-qc SSO sw-rel-qc group] that includes a mailing list and permissions to modify RT tickets related with the verification process. <br />
<br />
== Reference Documents ==<br />
<br />
{| border="1" cellspacing="0" cellpadding="3" style="border: 1px solid black;" class="wikitable sortable"<br />
|- align="left" style="background: none repeat scroll 0% 0% Lightgray;"<br />
! DocDB link <br />
! Release Date <br />
! Document<br />
|-<br />
| [https://documents.egi.eu/document/1700 QCv5] <br />
| 08. 05. 2013 <br />
| UMD Quality Criteria<br />
|-<br />
| [https://documents.egi.eu/document/418 418] <br />
| 08. 05. 2013 <br />
| UMD Products service mapping<br />
|-<br />
| [https://documents.egi.eu/document/417 417] <br />
| 08. 05. 2013 <br />
| QC Verification Templates<br />
|}<br />
<br />
== Metrics ==<br />
<br />
{| border="1" cellspacing="0" cellpadding="3" style="border: 1px solid black;" class="wikitable sortable"<br />
|- align="left" style="background: none repeat scroll 0% 0% Lightgray;"<br />
! Metric <br />
! Description<br />
|-<br />
| M.SA2.4 <br />
| Number of new releases validated against defined criteria: Measures the workload on the validation team.<br />
|-<br />
| M.SA2.5 <br />
| Mean time taken to validate a releas: Indicates how responsive the team is to validating releases.<br />
|-<br />
| M.SA2.6 <br />
| Number of releases failing validation: Indicates the quality assurance process of the software providers.<br />
|}<br />
<br />
== SLAs ==<br />
<br />
EGI SLAs negotiated with the TPs <br />
<br />
[https://documents.egi.eu/document/461 EMI-EGI SLA] <br />
<br />
== Verification engineer skill matrix ==<br />
<br />
{| border="1" class="wikitable" style="text-align: center;"<br />
|+ Verification Cheat Sheet <br />
|-<br />
! width="200" align="left" | Product\Institute <br />
! width="75" | CESGA <br />
! width="75" | IFCA <br />
! width="75" | IFIC <br />
! width="75" | INFN <br />
! width="75" | IN2P3 <br />
! width="75" | JÜLICH <br />
! width="75" | LIP <br />
! width="75" | BADWB <br />
! width="75" | UTC-N <br />
! width="75" | UZH <br />
! width="75" | GRNET <br />
! width="75" | RAL <br />
! width="75" | FZU <br />
! width="300" style="background: none repeat scroll 0% 0% Gray;" | COMMENTS<br />
|-<br />
! align="left" | EMI ARC CE <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI ARC compute cli <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI ARC Infosys <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI dCache <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI gLite MPI <br />
| * <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI CREAM_torque <br />
| * <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI CREAM_lsf <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI EMIR <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
|-<br />
! align="left" | EMI WMS <br />
| * <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI LB <br />
| * <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI FTS <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
|-<br />
! align="left" | EMI DPM <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI LFC_mySQL <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI LFC_Oracle <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI StoRM <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI APEL <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI DGAS <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI BDII <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI UI <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI PX <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI VOMS_mySQL <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" style="background: none repeat scroll 0% 0% Red;" | EMI VOMS_Oracle <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| No verifiers available yet. Oracle training required.<br />
|-<br />
! align="left" style="background: none repeat scroll 0% 0% Red;" | EMI HYDRA <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| No verifiers available yet.<br />
|-<br />
! align="left" style="background: none repeat scroll 0% 0% Red;" | EMI Wnodes <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| No verifiers available yet.<br />
|-<br />
! align="left" style="background: none repeat scroll 0% 0% Red;" | EMI NAGIOS <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| No verifiers available yet.<br />
|-<br />
! align="left" style="background: none repeat scroll 0% 0% Red;" | EMI Pseudonymity <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| No verifiers available yet.<br />
|-<br />
! align="left" | EMI ARGUS <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI UNICORE TSI <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI UNICORE WS <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI UNICORE Client <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI UNICORE Registry <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI UNICORE Gateway <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI UNICORE Hila <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI UNICORE xuudb <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI UNICORE Uvos <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI AMGA <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | IGE SAGA-SD <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| No verifiers available yet.<br />
|-<br />
! align="left" | IGE GRAM5 <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | IGE GSISSH <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | IGE GridFTP <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | IGE myProxy <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | IGE RLS <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | IGE GridWay <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | IGE SAM <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | IGE OGSA-DAI <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | IGE Security <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | IGE Gridsafe <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|}<br />
<br />
<br> <br />
<br />
[https://www.egi.eu/earlyAdopters/table Early Adopters list] <br />
<br />
[https://www.egi.eu/earlyAdopters/teams Early Adopters per UMD product]</div>
Asimon
https://wiki.egi.eu/w/index.php?title=EGI_Quality_Criteria_Testing&diff=59070
EGI Quality Criteria Testing
2013-08-14T06:21:21Z
<p>Asimon: </p>
<hr />
<div><br> <br />
<br />
== Quality Criteria Testing ==<br />
<br />
Verifiers should adjust the level of testing for each release (major, minor, revision) as described in the [[Verifiers guideline]]. They must also consider that some of the QC included in the documents are also checked during Stage-Rollout. This list include the '''mandatory''' criteria that must be checked for '''all''' verifications: <br />
<br />
<br> <br />
<br />
{| cellspacing="0" cellpadding="3" border="1" style="border: 1px solid black;" class="wikitable sortable"<br />
|- align="left" style="background: none repeat scroll 0% 0% Lightgray;"<br />
! QC <br />
! Description<br />
|-<br />
| GENERIC_DIST_3 <br />
| Valid binary packages must be available for the tested platform<br />
|-<br />
| GENERIC_SEC_1 <br />
| No world-writable files are used in the product<br />
|-<br />
| INFO_MODEL_SCHEMA_1 <br />
| Glue1.3<br />
|-<br />
| INFO_MODEL_SCHEMA_2 <br />
| Version of middleware published<br />
|-<br />
| INFO_MODEL_SCHEMA_3 <br />
| Glue 2<br />
|-<br />
| AUTHN_CRED_2 <br />
| Use of SHA-2 certificates/proxies<br />
|-<br />
| AUTHN_CRED_3 <br />
| Use of RFC proxies<br />
|-<br />
| AUTHZ_PEP_3 <br />
| Argus integration (only if the service requires some form of authz)<br />
|}<br />
<br />
== How to test criteria ==<br />
<br />
=== Generic ===<br />
<br />
==== GENERIC_DIST_3 ====<br />
<br />
The product '''must be installable''' from the UMD repository (+ epel if using RH based distros) with no extra packages coming from other sources. All packages '''must be signed'''. <br />
<br />
Ideally a meta-package fetches all dependencies. Installing should be done with the regular package management tools of the distro (rh based): <br />
<br />
yum install &lt;meta-package&gt;<br />
<br />
or (debian based): <br />
<br />
apt-get install &lt;meta-package&gt;<br />
<br />
The packages ''should not'' create any files outside the regular OS locations: use of /opt is discouraged, if files are created there, the QC passes, but a note should be included in the report (except for yaim packages) <br />
<br />
==== GENERIC_SEC_1 ====<br />
<br />
An easy way to find world-writable files is using the find command: <br />
<br />
find / -type f -perm -002 -exec ls -l {} \;<br />
<br />
For finding world-writable files in the packages contents: <br />
<br />
rpm -qalv | egrep "^[-d]([-r][-w][-xs]){2}[-r]w"<br />
<br />
=== Information Model Capability ===<br />
<br />
==== INFO_MODEL_SCHEMA_1 ====<br />
<br />
Use [https://tomtools.cern.ch/confluence/display/IS/GLUEValidator GlueValidator] for testing the validity of both Glue1.3 and Glue2. More info about GLUEValidator is available [http://gridinfo.web.cern.ch/glue/glue-validator-guide here] <br />
<br />
Some exceptions may be allowed: <br />
<br />
*AssertionError: The field GLUE2EndpointCapability with value 'information.publication' does not follow the type Capability_t <br />
*<br />
<br />
==== INFO_MODEL_SCHEMA_2 ====<br />
<br />
The basic query would be something like: <br />
<br />
ldapsearch -x -h &lt;hostname&gt; -p 2170 -b GLUE2GroupID=resource,o=glue objectclass=GLUE2Endpoint<br />
<br />
That should return one or more Endpoint objects, containing attributes like <br />
<br />
GLUE2EndpointImplementationVersion: 2.7.0<br />
GLUE2EntityOtherInfo: MiddlewareVersion=2.5.1-1<br />
<br />
GLUEValidator UMD3 installation: <br />
<br />
yum install glue-validator<br />
<br />
GLUEValidator usage: <br />
<br />
glue-validator -g egi-glue2 -H localhost -p 2170 -b o=glue -s egi-profile -n -v 3 --exclude-known-issues<br />
<br />
A complete list of glue-validator Error Codes is available [https://twiki.cern.ch/twiki/bin/view/EGEE/GLUEValidatorErrorCodes here].<br />
<br />
=== Authentication Capability ===<br />
<br />
==== AUTHN_CRED_2 ====<br />
<br />
If you do not have valid SHA-2 certificates, you can get one using a provider like CILogon, using their (unaccredited) OpenID provider like Google <br />
<br />
(instructions from D. Groep) <br />
<br />
#Go to https://cilogon.org/ <br />
#Select "Google" from the list of IdPs. <br />
#After signing in to Google and typing in a password, you can download a pkcs#12 file with your new certificate and private key. <br />
#To get the conventional usercert.pem and userkey.pem, use openssl:<br />
<br />
openssl pkcs12 -in myfile.p12 -info -out usercert.pem -nokeys<br />
openssl pkcs12 -in myfile.p12 -info -out userkey.pem -nocerts<br />
chmod 0600 userkey.pem<br />
<br />
Services to test need to have the OpenID CA just like the other IGTF CAs, which is available from the [https://dist.eugridpma.info/distribution/current/experimental/ experimental repository]. A [https://dist.eugridpma.info/distribution/current/experimental/RPMS/ca_cilogon-openid-1.48-1.noarch.rpm RPM package] is also provided. <br />
<br />
SA2 VM images also include SHA-2 certificates into /etc/grid-security directory (hostcert-SHA2.pem and hostkey-SHA2.pem). These certificates could replace /etc/grid-security/hostcert.pem and /etc/grid-security/hostkey.pem to check SHA-2 service support. First of all backup the old certificates: <br />
<br />
cp /etc/grid-security/hostcert.pem /etc/grid-security/hostcert.pem.orig<br />
cp /etc/grid-security/hostkey.pem /etc/grid-security/hostkey.pem.orig<br />
<br />
And replace them by the new SHA2 certificates: <br />
<br />
cp /etc/grid-security/hostcert-SHA2.pem /etc/grid-security/hostcert.pem<br />
cp /etc/grid-security/hostkey-SHA2.pem /etc/grid-security/hostkey.pem<br />
<br />
An then reconfigure/restart the service. <br />
<br />
==== AUTHN_CRED_3 ====<br />
<br />
RFC proxies can be created by using the <tt>-rfc</tt> option in voms-proxy-init: <br />
<pre>$ voms-proxy-init -rfc --voms dteam<br />
Your identity: /DC=es/DC=irisgrid/O=ifca/CN=Enol-Fernandez-delCastillo<br />
Creating temporary proxy .......................................... Done<br />
Contacting voms.hellasgrid.gr:15004 [/C=GR/O=HellasGrid/OU=hellasgrid.gr/CN=voms.hellasgrid.gr] "dteam" Done<br />
Creating proxy ...................................... Done<br />
Your proxy is valid until Thu Aug 2 01:01:26 2012<br />
</pre> <br />
You can check if the proxy has RFC format with voms-proxy-info: <br />
<pre>$ voms-proxy-info --all<br />
subject &nbsp;: /DC=es/DC=irisgrid/O=ifca/CN=Enol-Fernandez-delCastillo/CN=3300543<br />
issuer &nbsp;: /DC=es/DC=irisgrid/O=ifca/CN=Enol-Fernandez-delCastillo<br />
identity &nbsp;: /DC=es/DC=irisgrid/O=ifca/CN=Enol-Fernandez-delCastillo<br />
type &nbsp;: RFC compliant proxy<br />
strength &nbsp;: 1024 bits<br />
path &nbsp;: /nfs4/home/local/enol/.x509up_u7056<br />
timeleft &nbsp;: 11:59:52<br />
=== VO dteam extension information ===<br />
VO &nbsp;: dteam<br />
subject &nbsp;: /DC=es/DC=irisgrid/O=ifca/CN=Enol-Fernandez-delCastillo<br />
issuer &nbsp;: /C=GR/O=HellasGrid/OU=hellasgrid.gr/CN=voms.hellasgrid.gr<br />
attribute&nbsp;: /dteam/Role=NULL/Capability=NULL<br />
timeleft &nbsp;: 11:59:51<br />
uri &nbsp;: voms.hellasgrid.gr:15004<br />
</pre> <br />
==== AUTHZ_PEP_3 ====<br />
<br />
This criterion needs to be checked for every product that requires some sort of authorization. You will need a working ARGUS instance where the policies are defined. The verification testbed includes one ARGUS instance at <tt>test30.egi.cesga.es</tt> that can be used for this test. <br />
<br />
Configure the service with the following values for testing a policy where any user from <tt>ops</tt>, <tt>dteam</tt> or <tt>ops.vo.ibergrid.eu</tt> VOs is allowed to perform any action (<tt>".*"</tt>): <br />
<br />
{| cellspacing="0" cellpadding="5" style="border:1px solid black;" class="wikitable"<br />
|-<br />
! Argus endpoint <br />
| <tt><nowiki>https://test30.egi.cesga.es:8154/authz</nowiki></tt><br />
|-<br />
! Resource <br />
| <tt><nowiki>http://test30.egi.cesga.es/policy</nowiki></tt><br />
|}<br />
<br />
For testing banning policies, there is another resource that lets users from <tt>ops.vo.ibergrid.eu</tt> and <tt>ops</tt>, but bans <tt>dteam</tt> users. This resource can be configured with: <br />
<br />
{| cellspacing="0" cellpadding="5" style="border:1px solid black;" class="wikitable"<br />
|-<br />
! Argus endpoint <br />
| <tt><nowiki>https://test30.egi.cesga.es:8154/authz</nowiki></tt><br />
|-<br />
! Resource <br />
| <tt><nowiki>http://test30.egi.cesga.es/deny</nowiki></tt><br />
|}<br />
<br />
If you don't belong to those VOs or want to test other banning policies (e.g. on your user DN), you need to contact the verification team for adding new rules into the ARGUS instance. <br />
<br />
[[Category:Technology]] [[Category:Quality_Assurance]]</div>
Asimon
https://wiki.egi.eu/w/index.php?title=EGI_Quality_Criteria_Testing&diff=59049
EGI Quality Criteria Testing
2013-08-13T10:47:25Z
<p>Asimon: </p>
<hr />
<div><br> <br />
<br />
== Quality Criteria Testing ==<br />
<br />
Verifiers should adjust the level of testing for each release (major, minor, revision) as described in the [[Verifiers guideline]]. They must also consider that some of the QC included in the documents are also checked during Stage-Rollout. This list include the '''mandatory''' criteria that must be checked for '''all''' verifications: <br />
<br />
<br> <br />
<br />
{| cellspacing="0" cellpadding="3" border="1" style="border: 1px solid black;" class="wikitable sortable"<br />
|- align="left" style="background: none repeat scroll 0% 0% Lightgray;"<br />
! QC <br />
! Description<br />
|-<br />
| GENERIC_DIST_3 <br />
| Valid binary packages must be available for the tested platform<br />
|-<br />
| GENERIC_SEC_1 <br />
| No world-writable files are used in the product<br />
|-<br />
| INFO_MODEL_SCHEMA_1 <br />
| Glue1.3<br />
|-<br />
| INFO_MODEL_SCHEMA_2 <br />
| Version of middleware published<br />
|-<br />
| INFO_MODEL_SCHEMA_3 <br />
| Glue 2<br />
|-<br />
| AUTHN_CRED_2 <br />
| Use of SHA-2 certificates/proxies<br />
|-<br />
| AUTHN_CRED_3 <br />
| Use of RFC proxies<br />
|-<br />
| AUTHZ_PEP_3 <br />
| Argus integration (only if the service requires some form of authz)<br />
|}<br />
<br />
== How to test criteria ==<br />
<br />
=== Generic ===<br />
<br />
==== GENERIC_DIST_3 ====<br />
<br />
The product '''must be installable''' from the UMD repository (+ epel if using RH based distros) with no extra packages coming from other sources. All packages '''must be signed'''. <br />
<br />
Ideally a meta-package fetches all dependencies. Installing should be done with the regular package management tools of the distro (rh based): <br />
<br />
yum install &lt;meta-package&gt;<br />
<br />
or (debian based): <br />
<br />
apt-get install &lt;meta-package&gt;<br />
<br />
The packages ''should not'' create any files outside the regular OS locations: use of /opt is discouraged, if files are created there, the QC passes, but a note should be included in the report (except for yaim packages) <br />
<br />
==== GENERIC_SEC_1 ====<br />
<br />
An easy way to find world-writable files is using the find command: <br />
<br />
find / -type f -perm -002 -exec ls -l {} \;<br />
<br />
For finding world-writable files in the packages contents: <br />
<br />
rpm -qalv | egrep "^[-d]([-r][-w][-xs]){2}[-r]w"<br />
<br />
=== Information Model Capability ===<br />
<br />
==== INFO_MODEL_SCHEMA_1 ====<br />
<br />
Use [https://tomtools.cern.ch/confluence/display/IS/GLUEValidator GlueValidator] for testing the validity of both Glue1.3 and Glue2. More info about GLUEValidator is available [http://gridinfo.web.cern.ch/glue/glue-validator-guide here] <br />
<br />
Some exceptions may be allowed: <br />
<br />
*AssertionError: The field GLUE2EndpointCapability with value 'information.publication' does not follow the type Capability_t <br />
*<br />
<br />
==== INFO_MODEL_SCHEMA_2 ====<br />
<br />
The basic query would be something like: <br />
<br />
ldapsearch -x -h &lt;hostname&gt; -p 2170 -b GLUE2GroupID=resource,o=glue objectclass=GLUE2Endpoint<br />
<br />
That should return one or more Endpoint objects, containing attributes like <br />
<br />
GLUE2EndpointImplementationVersion: 2.7.0<br />
GLUE2EntityOtherInfo: MiddlewareVersion=2.5.1-1<br />
<br />
GLUEValidator UMD3 installation: <br />
<br />
yum install glue-validator<br />
<br />
GLUEValidator usage: <br />
<br />
glue-validator -g egi-glue2 -H localhost -p 2170 -b o=glue -s egi-profile -n -v 3 --exclude-known-issues<br />
<br />
=== Authentication Capability ===<br />
<br />
==== AUTHN_CRED_2 ====<br />
<br />
If you do not have valid SHA-2 certificates, you can get one using a provider like CILogon, using their (unaccredited) OpenID provider like Google <br />
<br />
(instructions from D. Groep) <br />
<br />
#Go to https://cilogon.org/ <br />
#Select "Google" from the list of IdPs. <br />
#After signing in to Google and typing in a password, you can download a pkcs#12 file with your new certificate and private key. <br />
#To get the conventional usercert.pem and userkey.pem, use openssl:<br />
<br />
openssl pkcs12 -in myfile.p12 -info -out usercert.pem -nokeys<br />
openssl pkcs12 -in myfile.p12 -info -out userkey.pem -nocerts<br />
chmod 0600 userkey.pem<br />
<br />
Services to test need to have the OpenID CA just like the other IGTF CAs, which is available from the [https://dist.eugridpma.info/distribution/current/experimental/ experimental repository]. A [https://dist.eugridpma.info/distribution/current/experimental/RPMS/ca_cilogon-openid-1.48-1.noarch.rpm RPM package] is also provided. <br />
<br />
SA2 VM images also include SHA-2 certificates into /etc/grid-security directory (hostcert-SHA2.pem and hostkey-SHA2.pem). These certificates could replace /etc/grid-security/hostcert.pem and /etc/grid-security/hostkey.pem to check SHA-2 service support. First of all backup the old certificates: <br />
<br />
cp /etc/grid-security/hostcert.pem /etc/grid-security/hostcert.pem.orig<br />
cp /etc/grid-security/hostkey.pem /etc/grid-security/hostkey.pem.orig<br />
<br />
And replace them by the new SHA2 certificates: <br />
<br />
cp /etc/grid-security/hostcert-SHA2.pem /etc/grid-security/hostcert.pem<br />
cp /etc/grid-security/hostkey-SHA2.pem /etc/grid-security/hostkey.pem<br />
<br />
An then reconfigure/restart the service. <br />
<br />
==== AUTHN_CRED_3 ====<br />
<br />
RFC proxies can be created by using the <tt>-rfc</tt> option in voms-proxy-init: <br />
<pre>$ voms-proxy-init -rfc --voms dteam<br />
Your identity: /DC=es/DC=irisgrid/O=ifca/CN=Enol-Fernandez-delCastillo<br />
Creating temporary proxy .......................................... Done<br />
Contacting voms.hellasgrid.gr:15004 [/C=GR/O=HellasGrid/OU=hellasgrid.gr/CN=voms.hellasgrid.gr] "dteam" Done<br />
Creating proxy ...................................... Done<br />
Your proxy is valid until Thu Aug 2 01:01:26 2012<br />
</pre> <br />
You can check if the proxy has RFC format with voms-proxy-info: <br />
<pre>$ voms-proxy-info --all<br />
subject &nbsp;: /DC=es/DC=irisgrid/O=ifca/CN=Enol-Fernandez-delCastillo/CN=3300543<br />
issuer &nbsp;: /DC=es/DC=irisgrid/O=ifca/CN=Enol-Fernandez-delCastillo<br />
identity &nbsp;: /DC=es/DC=irisgrid/O=ifca/CN=Enol-Fernandez-delCastillo<br />
type &nbsp;: RFC compliant proxy<br />
strength &nbsp;: 1024 bits<br />
path &nbsp;: /nfs4/home/local/enol/.x509up_u7056<br />
timeleft &nbsp;: 11:59:52<br />
=== VO dteam extension information ===<br />
VO &nbsp;: dteam<br />
subject &nbsp;: /DC=es/DC=irisgrid/O=ifca/CN=Enol-Fernandez-delCastillo<br />
issuer &nbsp;: /C=GR/O=HellasGrid/OU=hellasgrid.gr/CN=voms.hellasgrid.gr<br />
attribute&nbsp;: /dteam/Role=NULL/Capability=NULL<br />
timeleft &nbsp;: 11:59:51<br />
uri &nbsp;: voms.hellasgrid.gr:15004<br />
</pre> <br />
==== AUTHZ_PEP_3 ====<br />
<br />
This criterion needs to be checked for every product that requires some sort of authorization. You will need a working ARGUS instance where the policies are defined. The verification testbed includes one ARGUS instance at <tt>test30.egi.cesga.es</tt> that can be used for this test. <br />
<br />
Configure the service with the following values for testing a policy where any user from <tt>ops</tt>, <tt>dteam</tt> or <tt>ops.vo.ibergrid.eu</tt> VOs is allowed to perform any action (<tt>".*"</tt>): <br />
<br />
{| cellspacing="0" cellpadding="5" style="border:1px solid black;" class="wikitable"<br />
|-<br />
! Argus endpoint <br />
| <tt><nowiki>https://test30.egi.cesga.es:8154/authz</nowiki></tt><br />
|-<br />
! Resource <br />
| <tt><nowiki>http://test30.egi.cesga.es/policy</nowiki></tt><br />
|}<br />
<br />
For testing banning policies, there is another resource that lets users from <tt>ops.vo.ibergrid.eu</tt> and <tt>ops</tt>, but bans <tt>dteam</tt> users. This resource can be configured with: <br />
<br />
{| cellspacing="0" cellpadding="5" style="border:1px solid black;" class="wikitable"<br />
|-<br />
! Argus endpoint <br />
| <tt><nowiki>https://test30.egi.cesga.es:8154/authz</nowiki></tt><br />
|-<br />
! Resource <br />
| <tt><nowiki>http://test30.egi.cesga.es/deny</nowiki></tt><br />
|}<br />
<br />
If you don't belong to those VOs or want to test other banning policies (e.g. on your user DN), you need to contact the verification team for adding new rules into the ARGUS instance. <br />
<br />
[[Category:Technology]] [[Category:Quality_Assurance]]</div>
Asimon
https://wiki.egi.eu/w/index.php?title=EGI_Quality_Criteria_Testing&diff=59048
EGI Quality Criteria Testing
2013-08-13T09:56:25Z
<p>Asimon: </p>
<hr />
<div><br> <br />
<br />
== Quality Criteria Testing ==<br />
<br />
Verifiers should adjust the level of testing for each release (major, minor, revision) as described in the [[Verifiers guideline]]. They must also consider that some of the QC included in the documents are also checked during Stage-Rollout. This list include the '''mandatory''' criteria that must be checked for '''all''' verifications: <br />
<br />
<br> <br />
<br />
{| cellspacing="0" cellpadding="3" border="1" style="border: 1px solid black;" class="wikitable sortable"<br />
|- align="left" style="background: none repeat scroll 0% 0% Lightgray;"<br />
! QC <br />
! Description<br />
|-<br />
| GENERIC_DIST_3 <br />
| Valid binary packages must be available for the tested platform<br />
|-<br />
| GENERIC_SEC_1 <br />
| No world-writable files are used in the product<br />
|-<br />
| INFO_MODEL_SCHEMA_1 <br />
| Glue1.3<br />
|-<br />
| INFO_MODEL_SCHEMA_2 <br />
| Version of middleware published<br />
|-<br />
| INFO_MODEL_SCHEMA_3 <br />
| Glue 2<br />
|-<br />
| AUTHN_CRED_2 <br />
| Use of SHA-2 certificates/proxies<br />
|-<br />
| AUTHN_CRED_3 <br />
| Use of RFC proxies<br />
|-<br />
| AUTHZ_PEP_3 <br />
| Argus integration (only if the service requires some form of authz)<br />
|}<br />
<br />
== How to test criteria ==<br />
<br />
=== Generic ===<br />
<br />
==== GENERIC_DIST_3 ====<br />
<br />
The product '''must be installable''' from the UMD repository (+ epel if using RH based distros) with no extra packages coming from other sources. All packages '''must be signed'''. <br />
<br />
Ideally a meta-package fetches all dependencies. Installing should be done with the regular package management tools of the distro (rh based): <br />
<br />
yum install &lt;meta-package&gt;<br />
<br />
or (debian based): <br />
<br />
apt-get install &lt;meta-package&gt;<br />
<br />
The packages ''should not'' create any files outside the regular OS locations: use of /opt is discouraged, if files are created there, the QC passes, but a note should be included in the report (except for yaim packages) <br />
<br />
==== GENERIC_SEC_1 ====<br />
<br />
An easy way to find world-writable files is using the find command: <br />
<br />
find / -type f -perm -002 -exec ls -l {} \;<br />
<br />
For finding world-writable files in the packages contents: <br />
<br />
rpm -qalv | egrep "^[-d]([-r][-w][-xs]){2}[-r]w"<br />
<br />
=== Information Model Capability ===<br />
<br />
==== INFO_MODEL_SCHEMA_1 ====<br />
<br />
Use [https://tomtools.cern.ch/confluence/display/IS/GLUEValidator GlueValidator] for testing the validity of both Glue1.3 and Glue2. More info about GLUEValidator is available [http://gridinfo.web.cern.ch/glue/glue-validator-guide here] <br />
<br />
Some exceptions may be allowed: <br />
<br />
*AssertionError: The field GLUE2EndpointCapability with value 'information.publication' does not follow the type Capability_t <br />
*<br />
<br />
==== INFO_MODEL_SCHEMA_2 ====<br />
<br />
The basic query would be something like: <br />
<br />
ldapsearch -x -h &lt;hostname&gt; -p 2170 -b GLUE2GroupID=resource,o=glue objectclass=GLUE2Endpoint<br />
<br />
That should return one or more Endpoint objects, containing attributes like <br />
<br />
GLUE2EndpointImplementationVersion: 2.7.0<br />
GLUE2EntityOtherInfo: MiddlewareVersion=2.5.1-1<br />
<br />
GLUEValidator UMD3 installation:<br />
<br />
yum install glue-validator<br />
<br />
GLUEValidator usage: <br />
<br />
glue-validator -g egi-glue2 -H localhost -b o=glue -s egi-profile -n -v 3<br />
<br />
=== Authentication Capability ===<br />
<br />
==== AUTHN_CRED_2 ====<br />
<br />
If you do not have valid SHA-2 certificates, you can get one using a provider like CILogon, using their (unaccredited) OpenID provider like Google <br />
<br />
(instructions from D. Groep) <br />
<br />
#Go to https://cilogon.org/ <br />
#Select "Google" from the list of IdPs. <br />
#After signing in to Google and typing in a password, you can download a pkcs#12 file with your new certificate and private key. <br />
#To get the conventional usercert.pem and userkey.pem, use openssl:<br />
<br />
openssl pkcs12 -in myfile.p12 -info -out usercert.pem -nokeys<br />
openssl pkcs12 -in myfile.p12 -info -out userkey.pem -nocerts<br />
chmod 0600 userkey.pem<br />
<br />
Services to test need to have the OpenID CA just like the other IGTF CAs, which is available from the [https://dist.eugridpma.info/distribution/current/experimental/ experimental repository]. A [https://dist.eugridpma.info/distribution/current/experimental/RPMS/ca_cilogon-openid-1.48-1.noarch.rpm RPM package] is also provided. <br />
<br />
SA2 VM images also include SHA-2 certificates into /etc/grid-security directory (hostcert-SHA2.pem and hostkey-SHA2.pem). These certificates could replace /etc/grid-security/hostcert.pem and /etc/grid-security/hostkey.pem to check SHA-2 service support. First of all backup the old certificates: <br />
<br />
cp /etc/grid-security/hostcert.pem /etc/grid-security/hostcert.pem.orig<br />
cp /etc/grid-security/hostkey.pem /etc/grid-security/hostkey.pem.orig<br />
<br />
And replace them by the new SHA2 certificates: <br />
<br />
cp /etc/grid-security/hostcert-SHA2.pem /etc/grid-security/hostcert.pem<br />
cp /etc/grid-security/hostkey-SHA2.pem /etc/grid-security/hostkey.pem<br />
<br />
An then reconfigure/restart the service. <br />
<br />
==== AUTHN_CRED_3 ====<br />
<br />
RFC proxies can be created by using the <tt>-rfc</tt> option in voms-proxy-init: <br />
<pre>$ voms-proxy-init -rfc --voms dteam<br />
Your identity: /DC=es/DC=irisgrid/O=ifca/CN=Enol-Fernandez-delCastillo<br />
Creating temporary proxy .......................................... Done<br />
Contacting voms.hellasgrid.gr:15004 [/C=GR/O=HellasGrid/OU=hellasgrid.gr/CN=voms.hellasgrid.gr] "dteam" Done<br />
Creating proxy ...................................... Done<br />
Your proxy is valid until Thu Aug 2 01:01:26 2012<br />
</pre> <br />
You can check if the proxy has RFC format with voms-proxy-info: <br />
<pre>$ voms-proxy-info --all<br />
subject &nbsp;: /DC=es/DC=irisgrid/O=ifca/CN=Enol-Fernandez-delCastillo/CN=3300543<br />
issuer &nbsp;: /DC=es/DC=irisgrid/O=ifca/CN=Enol-Fernandez-delCastillo<br />
identity &nbsp;: /DC=es/DC=irisgrid/O=ifca/CN=Enol-Fernandez-delCastillo<br />
type &nbsp;: RFC compliant proxy<br />
strength &nbsp;: 1024 bits<br />
path &nbsp;: /nfs4/home/local/enol/.x509up_u7056<br />
timeleft &nbsp;: 11:59:52<br />
=== VO dteam extension information ===<br />
VO &nbsp;: dteam<br />
subject &nbsp;: /DC=es/DC=irisgrid/O=ifca/CN=Enol-Fernandez-delCastillo<br />
issuer &nbsp;: /C=GR/O=HellasGrid/OU=hellasgrid.gr/CN=voms.hellasgrid.gr<br />
attribute&nbsp;: /dteam/Role=NULL/Capability=NULL<br />
timeleft &nbsp;: 11:59:51<br />
uri &nbsp;: voms.hellasgrid.gr:15004<br />
</pre> <br />
==== AUTHZ_PEP_3 ====<br />
<br />
This criterion needs to be checked for every product that requires some sort of authorization. You will need a working ARGUS instance where the policies are defined. The verification testbed includes one ARGUS instance at <tt>test30.egi.cesga.es</tt> that can be used for this test. <br />
<br />
Configure the service with the following values for testing a policy where any user from <tt>ops</tt>, <tt>dteam</tt> or <tt>ops.vo.ibergrid.eu</tt> VOs is allowed to perform any action (<tt>".*"</tt>): <br />
<br />
{| cellspacing="0" cellpadding="5" style="border:1px solid black;" class="wikitable"<br />
|-<br />
! Argus endpoint <br />
| <tt><nowiki>https://test30.egi.cesga.es:8154/authz</nowiki></tt><br />
|-<br />
! Resource <br />
| <tt><nowiki>http://test30.egi.cesga.es/policy</nowiki></tt><br />
|}<br />
<br />
For testing banning policies, there is another resource that lets users from <tt>ops.vo.ibergrid.eu</tt> and <tt>ops</tt>, but bans <tt>dteam</tt> users. This resource can be configured with: <br />
<br />
{| cellspacing="0" cellpadding="5" style="border:1px solid black;" class="wikitable"<br />
|-<br />
! Argus endpoint <br />
| <tt><nowiki>https://test30.egi.cesga.es:8154/authz</nowiki></tt><br />
|-<br />
! Resource <br />
| <tt><nowiki>http://test30.egi.cesga.es/deny</nowiki></tt><br />
|}<br />
<br />
If you don't belong to those VOs or want to test other banning policies (e.g. on your user DN), you need to contact the verification team for adding new rules into the ARGUS instance. <br />
<br />
[[Category:Technology]] [[Category:Quality_Assurance]]</div>
Asimon
https://wiki.egi.eu/w/index.php?title=EGI_Quality_Criteria_Testing&diff=59047
EGI Quality Criteria Testing
2013-08-13T09:41:24Z
<p>Asimon: </p>
<hr />
<div><br> <br />
<br />
== Quality Criteria Testing ==<br />
<br />
Verifiers should adjust the level of testing for each release (major, minor, revision) as described in the [[Verifiers guideline]]. They must also consider that some of the QC included in the documents are also checked during Stage-Rollout. This list include the '''mandatory''' criteria that must be checked for '''all''' verifications: <br />
<br />
<br> <br />
<br />
{| cellspacing="0" cellpadding="3" border="1" style="border: 1px solid black;" class="wikitable sortable"<br />
|- align="left" style="background: none repeat scroll 0% 0% Lightgray;"<br />
! QC <br />
! Description<br />
|-<br />
| GENERIC_DIST_3 <br />
| Valid binary packages must be available for the tested platform<br />
|-<br />
| GENERIC_SEC_1 <br />
| No world-writable files are used in the product<br />
|-<br />
| INFO_MODEL_SCHEMA_1 <br />
| Glue1.3<br />
|-<br />
| INFO_MODEL_SCHEMA_2 <br />
| Version of middleware published<br />
|-<br />
| INFO_MODEL_SCHEMA_3 <br />
| Glue 2<br />
|-<br />
| AUTHN_CRED_2 <br />
| Use of SHA-2 certificates/proxies<br />
|-<br />
| AUTHN_CRED_3 <br />
| Use of RFC proxies<br />
|-<br />
| AUTHZ_PEP_3 <br />
| Argus integration (only if the service requires some form of authz)<br />
|}<br />
<br />
== How to test criteria ==<br />
<br />
=== Generic ===<br />
<br />
==== GENERIC_DIST_3 ====<br />
<br />
The product '''must be installable''' from the UMD repository (+ epel if using RH based distros) with no extra packages coming from other sources. All packages '''must be signed'''. <br />
<br />
Ideally a meta-package fetches all dependencies. Installing should be done with the regular package management tools of the distro (rh based): <br />
<br />
yum install &lt;meta-package&gt;<br />
<br />
or (debian based): <br />
<br />
apt-get install &lt;meta-package&gt;<br />
<br />
The packages ''should not'' create any files outside the regular OS locations: use of /opt is discouraged, if files are created there, the QC passes, but a note should be included in the report (except for yaim packages) <br />
<br />
==== GENERIC_SEC_1 ====<br />
<br />
An easy way to find world-writable files is using the find command: <br />
<br />
find / -type f -perm -002 -exec ls -l {} \;<br />
<br />
For finding world-writable files in the packages contents: <br />
<br />
rpm -qalv | egrep "^[-d]([-r][-w][-xs]){2}[-r]w"<br />
<br />
=== Information Model Capability ===<br />
<br />
==== INFO_MODEL_SCHEMA_1 ====<br />
<br />
Use [https://tomtools.cern.ch/confluence/display/IS/GLUEValidator GlueValidator] for testing the validity of both Glue1.3 and Glue2. More info about GLUEValidator is available [http://gridinfo.web.cern.ch/glue/glue-validator-guide here] <br />
<br />
Some exceptions may be allowed: <br />
<br />
*AssertionError: The field GLUE2EndpointCapability with value 'information.publication' does not follow the type Capability_t <br />
*<br />
<br />
==== INFO_MODEL_SCHEMA_2 ====<br />
<br />
The basic query would be something like: <br />
<br />
ldapsearch -x -h &lt;hostname&gt; -p 2170 -b GLUE2GroupID=resource,o=glue objectclass=GLUE2Endpoint<br />
<br />
That should return one or more Endpoint objects, containing attributes like <br />
<br />
GLUE2EndpointImplementationVersion: 2.7.0<br />
GLUE2EntityOtherInfo: MiddlewareVersion=2.5.1-1<br />
<br />
GLUEValidator usage: <br />
<br />
glue-validator -g egi-glue2 -H localhost -b o=glue -s egi-profile -n -v 3<br />
<br />
=== Authentication Capability ===<br />
<br />
==== AUTHN_CRED_2 ====<br />
<br />
If you do not have valid SHA-2 certificates, you can get one using a provider like CILogon, using their (unaccredited) OpenID provider like Google <br />
<br />
(instructions from D. Groep) <br />
<br />
#Go to https://cilogon.org/ <br />
#Select "Google" from the list of IdPs. <br />
#After signing in to Google and typing in a password, you can download a pkcs#12 file with your new certificate and private key. <br />
#To get the conventional usercert.pem and userkey.pem, use openssl:<br />
<br />
openssl pkcs12 -in myfile.p12 -info -out usercert.pem -nokeys<br />
openssl pkcs12 -in myfile.p12 -info -out userkey.pem -nocerts<br />
chmod 0600 userkey.pem<br />
<br />
Services to test need to have the OpenID CA just like the other IGTF CAs, which is available from the [https://dist.eugridpma.info/distribution/current/experimental/ experimental repository]. A [https://dist.eugridpma.info/distribution/current/experimental/RPMS/ca_cilogon-openid-1.48-1.noarch.rpm RPM package] is also provided. <br />
<br />
SA2 VM images also include SHA-2 certificates into /etc/grid-security directory (hostcert-SHA2.pem and hostkey-SHA2.pem). These certificates could replace /etc/grid-security/hostcert.pem and /etc/grid-security/hostkey.pem to check SHA-2 service support. First of all backup the old certificates: <br />
<br />
cp /etc/grid-security/hostcert.pem /etc/grid-security/hostcert.pem.orig<br />
cp /etc/grid-security/hostkey.pem /etc/grid-security/hostkey.pem.orig<br />
<br />
And replace them by the new SHA2 certificates: <br />
<br />
cp /etc/grid-security/hostcert-SHA2.pem /etc/grid-security/hostcert.pem<br />
cp /etc/grid-security/hostkey-SHA2.pem /etc/grid-security/hostkey.pem<br />
<br />
An then reconfigure/restart the service. <br />
<br />
==== AUTHN_CRED_3 ====<br />
<br />
RFC proxies can be created by using the <tt>-rfc</tt> option in voms-proxy-init: <br />
<pre>$ voms-proxy-init -rfc --voms dteam<br />
Your identity: /DC=es/DC=irisgrid/O=ifca/CN=Enol-Fernandez-delCastillo<br />
Creating temporary proxy .......................................... Done<br />
Contacting voms.hellasgrid.gr:15004 [/C=GR/O=HellasGrid/OU=hellasgrid.gr/CN=voms.hellasgrid.gr] "dteam" Done<br />
Creating proxy ...................................... Done<br />
Your proxy is valid until Thu Aug 2 01:01:26 2012<br />
</pre> <br />
You can check if the proxy has RFC format with voms-proxy-info: <br />
<pre>$ voms-proxy-info --all<br />
subject &nbsp;: /DC=es/DC=irisgrid/O=ifca/CN=Enol-Fernandez-delCastillo/CN=3300543<br />
issuer &nbsp;: /DC=es/DC=irisgrid/O=ifca/CN=Enol-Fernandez-delCastillo<br />
identity &nbsp;: /DC=es/DC=irisgrid/O=ifca/CN=Enol-Fernandez-delCastillo<br />
type &nbsp;: RFC compliant proxy<br />
strength &nbsp;: 1024 bits<br />
path &nbsp;: /nfs4/home/local/enol/.x509up_u7056<br />
timeleft &nbsp;: 11:59:52<br />
=== VO dteam extension information ===<br />
VO &nbsp;: dteam<br />
subject &nbsp;: /DC=es/DC=irisgrid/O=ifca/CN=Enol-Fernandez-delCastillo<br />
issuer &nbsp;: /C=GR/O=HellasGrid/OU=hellasgrid.gr/CN=voms.hellasgrid.gr<br />
attribute&nbsp;: /dteam/Role=NULL/Capability=NULL<br />
timeleft &nbsp;: 11:59:51<br />
uri &nbsp;: voms.hellasgrid.gr:15004<br />
</pre> <br />
==== AUTHZ_PEP_3 ====<br />
<br />
This criterion needs to be checked for every product that requires some sort of authorization. You will need a working ARGUS instance where the policies are defined. The verification testbed includes one ARGUS instance at <tt>test30.egi.cesga.es</tt> that can be used for this test. <br />
<br />
Configure the service with the following values for testing a policy where any user from <tt>ops</tt>, <tt>dteam</tt> or <tt>ops.vo.ibergrid.eu</tt> VOs is allowed to perform any action (<tt>".*"</tt>): <br />
<br />
{| cellspacing="0" cellpadding="5" style="border:1px solid black;" class="wikitable"<br />
|-<br />
! Argus endpoint <br />
| <tt><nowiki>https://test30.egi.cesga.es:8154/authz</nowiki></tt><br />
|-<br />
! Resource <br />
| <tt><nowiki>http://test30.egi.cesga.es/policy</nowiki></tt><br />
|}<br />
<br />
For testing banning policies, there is another resource that lets users from <tt>ops.vo.ibergrid.eu</tt> and <tt>ops</tt>, but bans <tt>dteam</tt> users. This resource can be configured with: <br />
<br />
{| cellspacing="0" cellpadding="5" style="border:1px solid black;" class="wikitable"<br />
|-<br />
! Argus endpoint <br />
| <tt><nowiki>https://test30.egi.cesga.es:8154/authz</nowiki></tt><br />
|-<br />
! Resource <br />
| <tt><nowiki>http://test30.egi.cesga.es/deny</nowiki></tt><br />
|}<br />
<br />
If you don't belong to those VOs or want to test other banning policies (e.g. on your user DN), you need to contact the verification team for adding new rules into the ARGUS instance. <br />
<br />
[[Category:Technology]] [[Category:Quality_Assurance]]</div>
Asimon
https://wiki.egi.eu/w/index.php?title=EGI_Quality_Criteria_Testing&diff=59046
EGI Quality Criteria Testing
2013-08-13T09:40:02Z
<p>Asimon: </p>
<hr />
<div><br> <br />
<br />
== Quality Criteria Testing ==<br />
<br />
Verifiers should adjust the level of testing for each release (major, minor, revision) as described in the [[Verifiers guideline]]. They must also consider that some of the QC included in the documents are also checked during Stage-Rollout. This list include the '''mandatory''' criteria that must be checked for '''all''' verifications: <br />
<br />
<br> <br />
<br />
{| cellspacing="0" cellpadding="3" border="1" style="border: 1px solid black;" class="wikitable sortable"<br />
|- align="left" style="background: none repeat scroll 0% 0% Lightgray;"<br />
! QC <br />
! Description<br />
|-<br />
| GENERIC_DIST_3 <br />
| Valid binary packages must be available for the tested platform<br />
|-<br />
| GENERIC_SEC_1 <br />
| No world-writable files are used in the product<br />
|-<br />
| INFO_MODEL_SCHEMA_1 <br />
| Glue1.3<br />
|-<br />
| INFO_MODEL_SCHEMA_2 <br />
| Version of middleware published<br />
|-<br />
| INFO_MODEL_SCHEMA_3 <br />
| Glue 2<br />
|-<br />
| AUTHN_CRED_2 <br />
| Use of SHA-2 certificates/proxies<br />
|-<br />
| AUTHN_CRED_3 <br />
| Use of RFC proxies<br />
|-<br />
| AUTHZ_PEP_3 <br />
| Argus integration (only if the service requires some form of authz)<br />
|}<br />
<br />
== How to test criteria ==<br />
<br />
=== Generic ===<br />
<br />
==== GENERIC_DIST_3 ====<br />
<br />
The product '''must be installable''' from the UMD repository (+ epel if using RH based distros) with no extra packages coming from other sources. All packages '''must be signed'''. <br />
<br />
Ideally a meta-package fetches all dependencies. Installing should be done with the regular package management tools of the distro (rh based): <br />
<br />
yum install &lt;meta-package&gt;<br />
<br />
or (debian based): <br />
<br />
apt-get install &lt;meta-package&gt;<br />
<br />
The packages ''should not'' create any files outside the regular OS locations: use of /opt is discouraged, if files are created there, the QC passes, but a note should be included in the report (except for yaim packages) <br />
<br />
==== GENERIC_SEC_1 ====<br />
<br />
An easy way to find world-writable files is using the find command: <br />
<br />
find / -type f -perm -002 -exec ls -l {} \;<br />
<br />
For finding world-writable files in the packages contents: <br />
<br />
rpm -qalv | egrep "^[-d]([-r][-w][-xs]){2}[-r]w"<br />
<br />
=== Information Model Capability ===<br />
<br />
==== INFO_MODEL_SCHEMA_1 ====<br />
<br />
Use [https://tomtools.cern.ch/confluence/display/IS/GLUEValidator GlueValidator] for testing the validity of both Glue1.3 and Glue2. More info about GLUEValidator is available [http://gridinfo.web.cern.ch/glue/glue-validator-guide here]<br />
<br />
Some exceptions may be allowed: <br />
<br />
*AssertionError: The field GLUE2EndpointCapability with value 'information.publication' does not follow the type Capability_t <br />
*<br />
<br />
==== INFO_MODEL_SCHEMA_2 ====<br />
<br />
The basic query would be something like: <br />
<br />
ldapsearch -x -h &lt;hostname&gt; -p 2170 -b GLUE2GroupID=resource,o=glue objectclass=GLUE2Endpoint<br />
<br />
That should return one or more Endpoint objects, containing attributes like <br />
<br />
GLUE2EndpointImplementationVersion: 2.7.0<br />
GLUE2EntityOtherInfo: MiddlewareVersion=2.5.1-1<br />
<br />
GLUEValidator usage:<br />
<br />
glue-validator -v 3 -g glue2 -H localhost -p 2170 -b o=glue<br />
<br />
=== Authentication Capability ===<br />
<br />
==== AUTHN_CRED_2 ====<br />
<br />
If you do not have valid SHA-2 certificates, you can get one using a provider like CILogon, using their (unaccredited) OpenID provider like Google <br />
<br />
(instructions from D. Groep) <br />
<br />
#Go to https://cilogon.org/ <br />
#Select "Google" from the list of IdPs. <br />
#After signing in to Google and typing in a password, you can download a pkcs#12 file with your new certificate and private key. <br />
#To get the conventional usercert.pem and userkey.pem, use openssl:<br />
<br />
openssl pkcs12 -in myfile.p12 -info -out usercert.pem -nokeys<br />
openssl pkcs12 -in myfile.p12 -info -out userkey.pem -nocerts<br />
chmod 0600 userkey.pem<br />
<br />
Services to test need to have the OpenID CA just like the other IGTF CAs, which is available from the [https://dist.eugridpma.info/distribution/current/experimental/ experimental repository]. A [https://dist.eugridpma.info/distribution/current/experimental/RPMS/ca_cilogon-openid-1.48-1.noarch.rpm RPM package] is also provided. <br />
<br />
SA2 VM images also include SHA-2 certificates into /etc/grid-security directory (hostcert-SHA2.pem and hostkey-SHA2.pem). These certificates could replace /etc/grid-security/hostcert.pem and /etc/grid-security/hostkey.pem to check SHA-2 service support. First of all backup the old certificates: <br />
<br />
cp /etc/grid-security/hostcert.pem /etc/grid-security/hostcert.pem.orig<br />
cp /etc/grid-security/hostkey.pem /etc/grid-security/hostkey.pem.orig<br />
<br />
And replace them by the new SHA2 certificates: <br />
<br />
cp /etc/grid-security/hostcert-SHA2.pem /etc/grid-security/hostcert.pem<br />
cp /etc/grid-security/hostkey-SHA2.pem /etc/grid-security/hostkey.pem<br />
<br />
An then reconfigure/restart the service. <br />
<br />
==== AUTHN_CRED_3 ====<br />
<br />
RFC proxies can be created by using the <tt>-rfc</tt> option in voms-proxy-init: <br />
<pre>$ voms-proxy-init -rfc --voms dteam<br />
Your identity: /DC=es/DC=irisgrid/O=ifca/CN=Enol-Fernandez-delCastillo<br />
Creating temporary proxy .......................................... Done<br />
Contacting voms.hellasgrid.gr:15004 [/C=GR/O=HellasGrid/OU=hellasgrid.gr/CN=voms.hellasgrid.gr] "dteam" Done<br />
Creating proxy ...................................... Done<br />
Your proxy is valid until Thu Aug 2 01:01:26 2012<br />
</pre> <br />
You can check if the proxy has RFC format with voms-proxy-info: <br />
<pre>$ voms-proxy-info --all<br />
subject &nbsp;: /DC=es/DC=irisgrid/O=ifca/CN=Enol-Fernandez-delCastillo/CN=3300543<br />
issuer &nbsp;: /DC=es/DC=irisgrid/O=ifca/CN=Enol-Fernandez-delCastillo<br />
identity &nbsp;: /DC=es/DC=irisgrid/O=ifca/CN=Enol-Fernandez-delCastillo<br />
type &nbsp;: RFC compliant proxy<br />
strength &nbsp;: 1024 bits<br />
path &nbsp;: /nfs4/home/local/enol/.x509up_u7056<br />
timeleft &nbsp;: 11:59:52<br />
=== VO dteam extension information ===<br />
VO &nbsp;: dteam<br />
subject &nbsp;: /DC=es/DC=irisgrid/O=ifca/CN=Enol-Fernandez-delCastillo<br />
issuer &nbsp;: /C=GR/O=HellasGrid/OU=hellasgrid.gr/CN=voms.hellasgrid.gr<br />
attribute&nbsp;: /dteam/Role=NULL/Capability=NULL<br />
timeleft &nbsp;: 11:59:51<br />
uri &nbsp;: voms.hellasgrid.gr:15004<br />
</pre> <br />
==== AUTHZ_PEP_3 ====<br />
<br />
This criterion needs to be checked for every product that requires some sort of authorization. You will need a working ARGUS instance where the policies are defined. The verification testbed includes one ARGUS instance at <tt>test30.egi.cesga.es</tt> that can be used for this test. <br />
<br />
Configure the service with the following values for testing a policy where any user from <tt>ops</tt>, <tt>dteam</tt> or <tt>ops.vo.ibergrid.eu</tt> VOs is allowed to perform any action (<tt>".*"</tt>): <br />
<br />
{| cellspacing="0" cellpadding="5" style="border:1px solid black;" class="wikitable"<br />
|-<br />
! Argus endpoint <br />
| <tt><nowiki>https://test30.egi.cesga.es:8154/authz</nowiki></tt><br />
|-<br />
! Resource <br />
| <tt><nowiki>http://test30.egi.cesga.es/policy</nowiki></tt><br />
|}<br />
<br />
For testing banning policies, there is another resource that lets users from <tt>ops.vo.ibergrid.eu</tt> and <tt>ops</tt>, but bans <tt>dteam</tt> users. This resource can be configured with: <br />
<br />
{| cellspacing="0" cellpadding="5" style="border:1px solid black;" class="wikitable"<br />
|-<br />
! Argus endpoint <br />
| <tt><nowiki>https://test30.egi.cesga.es:8154/authz</nowiki></tt><br />
|-<br />
! Resource <br />
| <tt><nowiki>http://test30.egi.cesga.es/deny</nowiki></tt><br />
|}<br />
<br />
If you don't belong to those VOs or want to test other banning policies (e.g. on your user DN), you need to contact the verification team for adding new rules into the ARGUS instance. <br />
<br />
[[Category:Technology]] [[Category:Quality_Assurance]]</div>
Asimon
https://wiki.egi.eu/w/index.php?title=Middleware_argus_interoperability&diff=57963
Middleware argus interoperability
2013-07-16T10:34:52Z
<p>Asimon: </p>
<hr />
<div>Starting from March 2013, as part of the UMD quality criteria products requiring authentication are tested for the interoperability between argus and other middleware components. The following tables collects the products tested so far during the UMD software provisioning process. <br />
<br />
<br> <br />
<br />
= UMD-3 =<br />
<br />
{| width="90%" cellspacing="0" cellpadding="5" style="border:1px solid black;" class="wikitable"<br />
|- style="background-color:darkgray;"<br />
! Product name <br />
! Version <br />
! Released in UMD update # <br />
! Argus support <br />
! Tested in UMD* <br />
! Available in production <br />
! Comments <br />
! GGUS ticket<br />
|-<br />
| DPM <br />
| 1.8.6 <br />
| Planned for UMD 3.0.0 <br />
! align="centre" style="background: none repeat scroll 0% 0% Red;" | NO<br />
! align="centre" style="background: none repeat scroll 0% 0% Red;" | NO <br />
! align="centre" style="background: none repeat scroll 0% 0% Red;" | NO <br />
| <br />
| <br />
|-<br />
| dCache <br />
| <br />
| not released in UMD <br />
! align="centre" style="background: none repeat scroll 0% 0% Red;" | NO <br />
! <br />
! <br />
| <br />
| <br />
|-<br />
| VOMS <br />
| 3.0.0 <br />
| not released in UMD <br />
! align="centre" style="background: none repeat scroll 0% 0% Red;" | NO <br />
! <br />
! <br />
| <br />
| <br />
|-<br />
| StoRM <br />
| 1.11.0 <br />
| not released in UMD <br />
! align="centre" style="background: none repeat scroll 0% 0% Green;" | YES <br />
! align="centre" style="background: none repeat scroll 0% 0% Green;" | YES <br />
! align="centre" style="background: none repeat scroll 0% 0% Red;" | NO <br />
| Not available in production (failed during verification but authorization was working well) <br />
| <br />
|-<br />
| CREAM-CE <br />
| 1.15.1 <br />
| not released in UMD <br />
! align="centre" style="background: none repeat scroll 0% 0% Green;" | YES <br />
! align="centre" style="background: none repeat scroll 0% 0% Green;" | YES <br />
! align="centre" style="background: none repeat scroll 0% 0% Red;" | NO <br />
| <br />
| <br />
|-<br />
| WMS <br />
| 3.5.0 <br />
| Planned for UMD 3.0.0 <br />
! align="centre" style="background: none repeat scroll 0% 0% Green;" | YES <br />
! align="centre" style="background: none repeat scroll 0% 0% Yellow;" | YES <br />
! align="centre" style="background: none repeat scroll 0% 0% Green;" | YES <br />
| Because SL6 uses the NSS library instead of OpenSSL, the proxy are not correctly handled. It is a known problem in NSS, and will not be corrected soon. <br />
| [https://ggus.eu/tech/ticket_show.php?ticket=92773 GGUS]<br />
|-<br />
| glexec-wn <br />
| 1.2.0 <br />
| Planed for UMD 3.0.0 <br />
! align="centre" style="background: none repeat scroll 0% 0% Green;" | YES <br />
! align="centre" style="background: none repeat scroll 0% 0% Green;" | YES <br />
! align="centre" style="background: none repeat scroll 0% 0% Red;" | NO <br />
| <br />
| <br />
|}<br />
<br />
*Argus 1.6.0 from UMD-3 used<br />
<br />
= UMD-2 =<br />
<br />
{| width="90%" cellspacing="0" cellpadding="5" style="border:1px solid black;" class="wikitable"<br />
|- style="background-color:darkgray;"<br />
! Product name <br />
! Version <br />
! Released in UMD update # <br />
! Argus support <br />
! Tested in UMD <br />
! Comments <br />
! GGUS ticket<br />
|-<br />
| DPM <br />
| 1.8.6 <br />
| UMD2.4.0 <br />
! align="centre" style="background: none repeat scroll 0% 0% Red;" | NO<br />
! <br />
| <br />
| <br />
|-<br />
| dCache <br />
| <br />
! <br />
! align="centre" style="background: none repeat scroll 0% 0% Red;" | NO <br />
! <br />
| <br />
| <br />
|-<br />
| VOMS <br />
| <br />
| <br />
! align="centre" style="background: none repeat scroll 0% 0% Red;" | NO <br />
! <br />
| <br />
| <br />
|-<br />
| SRM <br />
| <br />
| <br />
! align="centre" style="background: none repeat scroll 0% 0% Green;" | YES <br />
! align="centre" style="background: none repeat scroll 0% 0% Red;" | NO <br />
| <br />
| <br />
|-<br />
| CREAM-CE <br />
| <br />
| <br />
! align="centre" style="background: none repeat scroll 0% 0% Green;" | YES <br />
! align="centre" style="background: none repeat scroll 0% 0% Red;" | NO <br />
| <br />
| <br />
|-<br />
| WMS <br />
| <br />
| <br />
! align="centre" style="background: none repeat scroll 0% 0% Green;" | YES <br />
! align="centre" style="background: none repeat scroll 0% 0% Red;" | NO <br />
| <br />
| <br />
|}<br />
<br />
<br></div>
Asimon
https://wiki.egi.eu/w/index.php?title=Fedcloud-tf:WorkGroups:Brokering&diff=57853
Fedcloud-tf:WorkGroups:Brokering
2013-07-11T13:00:14Z
<p>Asimon: </p>
<hr />
<div>{{Fedcloud-tf:Menu}} {{Fedcloud-tf:WorkGroups:Menu}} {{TOC_right}} <br />
<br />
<font color="red">Leader: Alvaro Simon, JR1 </font> <br />
<br />
== Collaborators ==<br />
<br />
{| border="1"<br />
|-<br />
! Role <br />
! Institution <br />
! Name<br />
|-<br />
| Collaborator <br />
| OeRC <br />
| Matteo Turilli<br />
|-<br />
| Collaborator <br />
| BSC <br />
| Daniele Lezzi<br />
|}<br />
<br />
== Scope ==<br />
<br />
This workgroup deals with the issues around cloud brokering. With 10+ resource providers lined up to be federated into the EGI cloud testbed, users need effective ways to access cloud resources. The goal is for a user to have a choice between a unified, abstracted view of the cloud testbed as a whole and the opportunity to target specific providers for their needs. As a consequence, this workgroup is concerned with both brokers and OCCI clients. <br />
<br />
== Roadmap ==<br />
<br />
*Collect information about existing solutions for cloud brokering compatible with the OCCI and CDMI management interfaces; <br />
*Collect information about existing solutions for OCCI and CDMI clients; <br />
*Make an inventory of the available solutions; <br />
*Choose a broker and a client for the testbed; <br />
*If possible, join the development teams of the chosen solutions to the task force; <br />
*Coordinate with the TF Resorce Providers to deploy the chosen solutions; <br />
*Extend the demo testbed addressing a real-life use case.<br />
<br />
== Clients Comparison Table ==<br />
<br />
{| width="90%" cellspacing="0" cellpadding="5" style="border:1px solid black;" class="wikitable"<br />
|- style="background-color:darkgray;"<br />
! Client/API <br />
! URL <br />
! OS <br />
! Support <br />
! OCCI/CDMI <br />
! Functionalities <br />
! Effort required <br />
! Comments<br />
|-<br />
| Hybridfox <br />
| http://code.google.com/p/hybridfox/ <br />
| Win/OS X/Linux <br />
| AWS/Eucalyptus/OpenStack/OpenNebula/HP Cloud <br />
| <span style="color:red"> '''NO'''</span> <br />
| Manage Images/Instances/Elastic IPs/Security Groups/Key-pairs <br />
| <span style="color:green"> '''Low'''</span> <br />
| Hybridfox does not support x509 auth, it uses EC2 auth for OpenNebula and OpenStack<br />
|-<br />
| DeltaCloud <br />
| http://deltacloud.apache.org <br />
| Win/OS X/Linux <br />
| EC2/Eucalyptus/OpenStack/OpenNebula/vSphere <br />
| <span style="color:red"> '''NO'''</span> <br />
| Create/Start/Stop/Reboot/Destroy instances <br />
| <span style="color:orange"> '''Medium'''</span> <br />
| DeltaCloud uses its own delta-cloud driver for each framework instead of OCCI. It provides storage support for S3, Warlus, Azure and Google Storage.<br />
|-<br />
| Aeolus <br />
| http://aeolusproject.org/about.html <br />
| Win/OS X/Linux <br />
| Same as DeltaCloud <br />
| <span style="color:red"> '''NO'''</span> <br />
| Create/Start/Stop/.. instances. Manage different instances and Images from different private, public, or hybrid cloud providers. <br />
| <span style="color:orange"> '''Medium'''</span> <br />
| Aeolus uses DeltaCloud cross-cloud abstraction library and it includes some extra functionalities. It includes Aeolus Conductor/Composer/Orchestrator/HA Manager<br />
|-<br />
| rOCCI (API) <br />
| http://dev.opennebula.org/projects/ogf-occi <br />
| Linux <br />
| OpenNebula/EC2 <br />
| <span style="color:green"> '''YES'''</span> <br />
| Create/Start/Stop/Reboot/Destroy instances. Upload and register an image. Network conf. x509 auth. <br />
| <span style="color:green"> '''Low'''</span> <br />
| rOCCI is an OCCI 1.1 implementation for OpenNebula 3.x<br />
|}<br />
<br />
== Cloud Brokering Solutions ==<br />
<br />
{| width="90%" cellspacing="0" cellpadding="5" style="border:1px solid black;" class="wikitable"<br />
|- style="background-color:darkgray;"<br />
! Name <br />
! URL <br />
! Cloud SW Support <br />
! OCCI <br />
! Functionalities <br />
! Effort required <br />
! Comments<br />
|-<br />
| CompatibleOne <br />
| http://www.compatibleone.org/ <br />
| OpenStack, OpenNebula, Azure, Vcloud <br />
| Yes, supports OCCI, but implements his own OCCI interface for each of the stacks (PROCCI). <br />
| Accounting, Brokering, User management, Monitoring. <br />
| <span style="color:orange"> '''Medium'''</span> <br />
| <br />
*Compatible One is a complete plattform, with its own user management, accounting and monitoring, so it overlaps in some aspects with the ongoing work. <br />
*It does not expose an OCCI api, the user has to write its own XML files and send them to the broker. <br />
*The credentials for each of the connectors and providers have to be configured in advance by the administrator of the broker service. <br />
*The user has to specify in the manifests the cloud account that he wants to use, and the specific name of the image in the site. It seems that the purpose of CompatibleONE is to deploy and take care of a complete manifest description: A user wants 3 machines of type A in site FOO, and 2 machine of type B in site BAR, so he explicitly defines it in his manifests and CompatibleOne will deploy it on them.<br />
<br />
|-<br />
| COMPSs <br />
| http://www.bsc.es/compss <br />
| &nbsp; OpenNebula, Amazon, Azure, OpenStack <br />
| Yes, support of rOCCI servers and OCCI+OVF <br />
| &nbsp;Automatic parallelization and orchestration of applications and services, elasticity, auto scaling <br />
| <span style="color:orange"> '''Medium'''</span> <br />
| <br />
*COMPSs allows the execution of applications on distributed infrastructures (grids, clusters, cloud). <br />
*Already used for the BioVeL/OpenBio use case. <br />
*Transparent support to different infrastructures; the user only provides his credentials. <br />
*Automatic selection of the VMs types dependending on the tasks constraints. <br />
*The number of VMs is dynamically adjusted to the current workload.<br />
<br />
|-<br />
| VMDIRAC <br />
| https://github.com/DIRACGrid/VMDIRAC/wiki <br />
| &nbsp; OpenNebula, OpenStack, CloudStack and Amazon EC2 <br />
| Yes, it supports rOCCI, OpenNebula "OCCI 0.8", Amazon EC2, OpenStack Nova 1.1 and CloudStack 2 APIs. <br />
| Accounting, monitoring, brokering, scheduling, HEPiX and SSH based VM contextualisation, [https://github.com/DIRACGrid/VMDIRAC/wiki#vm-horizontal-auto-scaling-setup VM Horizontal Auto-scaling]. <br />
| <span style="color:orange"> '''Medium'''</span> <br />
| <br />
*rOCCI support with X509/VOMS auth. <br />
*In production: LHCb (OpenStack and OpenNebula) Belle (Amazon), Work in progress France Federated Cloud. <br />
*Web UI including VM browsing with VM monitoring, and VM Overview Plots (Load, RunningVM, RunnigVM by Endpoint, started jobs, data transfer, transfer files) <br />
*The number of VMs is dynamically adjusted to the current workload. <br />
*Automatic selection of the VMs types depending on the tasks constraints. <br />
*No necessary to install any pluging in the Cloud Managers, works with standard interfaces. <br />
*Separated user credentials are used for job running and VM operator credentials for VM management. <br />
*VMDIRAC developers are willing to collaborate actively with Fedcloud Taskforce.<br />
<br />
|-<br />
| SlipStream™<br />
| http://sixsq.com/products/slipstream.html<br />
| &nbsp; StratusLab, OpenStack, Abiquo, CloudSigma and Amazon EC2 <br />
| Not yet, but it will supports OCCI in the future. It supports Cloud SW native APIs.<br />
| VM image creation and deployment, contextualisation, VM cluster automated deployments. <br />
| <span style="color:orange"> '''Medium'''</span> <br />
| <br />
*OCCI plugin is not available yet.<br />
*Does not provides a brokering mechanism but it is able to use different VM deployments between different cloud frameworks.<br />
*RPs don't need to configure new services. It uses native cloud APIs.<br />
*StratusLab Marketplace support<br />
<br />
|}</div>
Asimon
https://wiki.egi.eu/w/index.php?title=Fedcloud-tf:WorkGroups:Brokering&diff=57847
Fedcloud-tf:WorkGroups:Brokering
2013-07-11T11:21:37Z
<p>Asimon: </p>
<hr />
<div>{{Fedcloud-tf:Menu}} {{Fedcloud-tf:WorkGroups:Menu}} {{TOC_right}} <br />
<br />
<font color="red">Leader: Alvaro Simon, JR1 </font> <br />
<br />
== Collaborators ==<br />
<br />
{| border="1"<br />
|-<br />
! Role <br />
! Institution <br />
! Name<br />
|-<br />
| Collaborator <br />
| OeRC <br />
| Matteo Turilli<br />
|-<br />
| Collaborator <br />
| BSC <br />
| Daniele Lezzi<br />
|}<br />
<br />
== Scope ==<br />
<br />
This workgroup deals with the issues around cloud brokering. With 10+ resource providers lined up to be federated into the EGI cloud testbed, users need effective ways to access cloud resources. The goal is for a user to have a choice between a unified, abstracted view of the cloud testbed as a whole and the opportunity to target specific providers for their needs. As a consequence, this workgroup is concerned with both brokers and OCCI clients. <br />
<br />
== Roadmap ==<br />
<br />
*Collect information about existing solutions for cloud brokering compatible with the OCCI and CDMI management interfaces; <br />
*Collect information about existing solutions for OCCI and CDMI clients; <br />
*Make an inventory of the available solutions; <br />
*Choose a broker and a client for the testbed; <br />
*If possible, join the development teams of the chosen solutions to the task force; <br />
*Coordinate with the TF Resorce Providers to deploy the chosen solutions; <br />
*Extend the demo testbed addressing a real-life use case.<br />
<br />
== Clients Comparison Table ==<br />
<br />
{| width="90%" cellspacing="0" cellpadding="5" style="border:1px solid black;" class="wikitable"<br />
|- style="background-color:darkgray;"<br />
! Client/API <br />
! URL <br />
! OS <br />
! Support <br />
! OCCI/CDMI <br />
! Functionalities <br />
! Effort required <br />
! Comments<br />
|-<br />
| Hybridfox <br />
| http://code.google.com/p/hybridfox/ <br />
| Win/OS X/Linux <br />
| AWS/Eucalyptus/OpenStack/OpenNebula/HP Cloud <br />
| <span style="color:red"> '''NO'''</span> <br />
| Manage Images/Instances/Elastic IPs/Security Groups/Key-pairs <br />
| <span style="color:green"> '''Low'''</span> <br />
| Hybridfox does not support x509 auth, it uses EC2 auth for OpenNebula and OpenStack<br />
|-<br />
| DeltaCloud <br />
| http://deltacloud.apache.org <br />
| Win/OS X/Linux <br />
| EC2/Eucalyptus/OpenStack/OpenNebula/vSphere <br />
| <span style="color:red"> '''NO'''</span> <br />
| Create/Start/Stop/Reboot/Destroy instances <br />
| <span style="color:orange"> '''Medium'''</span> <br />
| DeltaCloud uses its own delta-cloud driver for each framework instead of OCCI. It provides storage support for S3, Warlus, Azure and Google Storage.<br />
|-<br />
| Aeolus <br />
| http://aeolusproject.org/about.html <br />
| Win/OS X/Linux <br />
| Same as DeltaCloud <br />
| <span style="color:red"> '''NO'''</span> <br />
| Create/Start/Stop/.. instances. Manage different instances and Images from different private, public, or hybrid cloud providers. <br />
| <span style="color:orange"> '''Medium'''</span> <br />
| Aeolus uses DeltaCloud cross-cloud abstraction library and it includes some extra functionalities. It includes Aeolus Conductor/Composer/Orchestrator/HA Manager<br />
|-<br />
| rOCCI (API) <br />
| http://dev.opennebula.org/projects/ogf-occi <br />
| Linux <br />
| OpenNebula/EC2 <br />
| <span style="color:green"> '''YES'''</span> <br />
| Create/Start/Stop/Reboot/Destroy instances. Upload and register an image. Network conf. x509 auth. <br />
| <span style="color:green"> '''Low'''</span> <br />
| rOCCI is an OCCI 1.1 implementation for OpenNebula 3.x<br />
|}<br />
<br />
== Cloud Brokering Solutions ==<br />
<br />
{| width="90%" cellspacing="0" cellpadding="5" style="border:1px solid black;" class="wikitable"<br />
|- style="background-color:darkgray;"<br />
! Name <br />
! URL <br />
! Cloud SW Support <br />
! OCCI <br />
! Functionalities <br />
! Effort required <br />
! Comments<br />
|-<br />
| CompatibleOne <br />
| http://www.compatibleone.org/ <br />
| OpenStack, OpenNebula, Azure, Vcloud <br />
| Yes, supports OCCI, but implements his own OCCI interface for each of the stacks (PROCCI). <br />
| Accounting, Brokering, User management, Monitoring. <br />
| <span style="color:orange"> '''Medium'''</span> <br />
| <br />
*Compatible One is a complete plattform, with its own user management, accounting and monitoring, so it overlaps in some aspects with the ongoing work. <br />
*It does not expose an OCCI api, the user has to write its own XML files and send them to the broker. <br />
*The credentials for each of the connectors and providers have to be configured in advance by the administrator of the broker service. <br />
*The user has to specify in the manifests the cloud account that he wants to use, and the specific name of the image in the site. It seems that the purpose of CompatibleONE is to deploy and take care of a complete manifest description: A user wants 3 machines of type A in site FOO, and 2 machine of type B in site BAR, so he explicitly defines it in his manifests and CompatibleOne will deploy it on them.<br />
<br />
|-<br />
| COMPSs <br />
| http://www.bsc.es/compss <br />
| &nbsp; OpenNebula, Amazon, Azure, OpenStack <br />
| Yes, support of rOCCI servers and OCCI+OVF <br />
| &nbsp;Automatic parallelization and orchestration of applications and services, elasticity, auto scaling <br />
| <span style="color:orange"> '''Medium'''</span> <br />
| <br />
*COMPSs allows the execution of applications on distributed infrastructures (grids, clusters, cloud). <br />
*Already used for the BioVeL/OpenBio use case. <br />
*Transparent support to different infrastructures; the user only provides his credentials. <br />
*Automatic selection of the VMs types dependending on the tasks constraints. <br />
*The number of VMs is dynamically adjusted to the current workload.<br />
<br />
|-<br />
| VMDIRAC <br />
| https://github.com/DIRACGrid/VMDIRAC/wiki <br />
| &nbsp; OpenNebula, OpenStack, CloudStack and Amazon EC2 <br />
| Yes, it supports rOCCI, OpenNebula "OCCI 0.8", Amazon EC2, OpenStack Nova 1.1 and CloudStack 2 APIs. <br />
| Accounting, monitoring, brokering, scheduling, HEPiX and SSH based VM contextualisation, [https://github.com/DIRACGrid/VMDIRAC/wiki#vm-horizontal-auto-scaling-setup VM Horizontal Auto-scaling]. <br />
| <span style="color:orange"> '''Medium'''</span> <br />
| <br />
*rOCCI support with X509/VOMS auth. <br />
*In production: LHCb (OpenStack and OpenNebula) Belle (Amazon), Work in progress France Federated Cloud. <br />
*Web UI including VM browsing with VM monitoring, and VM Overview Plots (Load, RunningVM, RunnigVM by Endpoint, started jobs, data transfer, transfer files) <br />
*The number of VMs is dynamically adjusted to the current workload. <br />
*Automatic selection of the VMs types depending on the tasks constraints. <br />
*No necessary to install any pluging in the Cloud Managers, works with standard interfaces. <br />
*Separated user credentials are used for job running and VM operator credentials for VM management. <br />
*VMDIRAC developers are willing to collaborate actively with Fedcloud Taskforce.<br />
<br />
|}</div>
Asimon
https://wiki.egi.eu/w/index.php?title=Fedcloud-tf:WorkGroups:Brokering&diff=57846
Fedcloud-tf:WorkGroups:Brokering
2013-07-11T11:18:45Z
<p>Asimon: </p>
<hr />
<div>{{Fedcloud-tf:Menu}} {{Fedcloud-tf:WorkGroups:Menu}} {{TOC_right}} <br />
<br />
<font color="red">Leader: Alvaro Simon, JR1 </font> <br />
<br />
== Collaborators ==<br />
<br />
{| border="1"<br />
|-<br />
! Role <br />
! Institution <br />
! Name<br />
|-<br />
| Collaborator <br />
| OeRC <br />
| Matteo Turilli<br />
|-<br />
| Collaborator <br />
| BSC <br />
| Daniele Lezzi<br />
|}<br />
<br />
== Scope ==<br />
<br />
This workgroup deals with the issues around cloud brokering. With 10+ resource providers lined up to be federated into the EGI cloud testbed, users need effective ways to access cloud resources. The goal is for a user to have a choice between a unified, abstracted view of the cloud testbed as a whole and the opportunity to target specific providers for their needs. As a consequence, this workgroup is concerned with both brokers and OCCI clients. <br />
<br />
== Roadmap ==<br />
<br />
*Collect information about existing solutions for cloud brokering compatible with the OCCI and CDMI management interfaces; <br />
*Collect information about existing solutions for OCCI and CDMI clients; <br />
*Make an inventory of the available solutions; <br />
*Choose a broker and a client for the testbed; <br />
*If possible, join the development teams of the chosen solutions to the task force; <br />
*Coordinate with the TF Resorce Providers to deploy the chosen solutions; <br />
*Extend the demo testbed addressing a real-life use case.<br />
<br />
== Clients Comparison Table ==<br />
<br />
{| width="90%" cellspacing="0" cellpadding="5" style="border:1px solid black;" class="wikitable"<br />
|- style="background-color:darkgray;"<br />
! Client/API <br />
! URL <br />
! OS <br />
! Support <br />
! OCCI/CDMI <br />
! Functionalities <br />
! Effort required <br />
! Comments<br />
|-<br />
| Hybridfox <br />
| http://code.google.com/p/hybridfox/ <br />
| Win/OS X/Linux <br />
| AWS/Eucalyptus/OpenStack/OpenNebula/HP Cloud <br />
| <span style="color:red"> '''NO'''</span> <br />
| Manage Images/Instances/Elastic IPs/Security Groups/Key-pairs <br />
| <span style="color:green"> '''Low'''</span> <br />
| Hybridfox does not support x509 auth, it uses EC2 auth for OpenNebula and OpenStack<br />
|-<br />
| DeltaCloud <br />
| http://deltacloud.apache.org <br />
| Win/OS X/Linux <br />
| EC2/Eucalyptus/OpenStack/OpenNebula/vSphere <br />
| <span style="color:red"> '''NO'''</span> <br />
| Create/Start/Stop/Reboot/Destroy instances <br />
| <span style="color:orange"> '''Medium'''</span> <br />
| DeltaCloud uses its own delta-cloud driver for each framework instead of OCCI. It provides storage support for S3, Warlus, Azure and Google Storage.<br />
|-<br />
| Aeolus <br />
| http://aeolusproject.org/about.html <br />
| Win/OS X/Linux <br />
| Same as DeltaCloud <br />
| <span style="color:red"> '''NO'''</span> <br />
| Create/Start/Stop/.. instances. Manage different instances and Images from different private, public, or hybrid cloud providers. <br />
| <span style="color:orange"> '''Medium'''</span> <br />
| Aeolus uses DeltaCloud cross-cloud abstraction library and it includes some extra functionalities. It includes Aeolus Conductor/Composer/Orchestrator/HA Manager<br />
|-<br />
| rOCCI (API) <br />
| http://dev.opennebula.org/projects/ogf-occi <br />
| Linux <br />
| OpenNebula/EC2 <br />
| <span style="color:green"> '''YES'''</span> <br />
| Create/Start/Stop/Reboot/Destroy instances. Upload and register an image. Network conf. x509 auth. <br />
| <span style="color:green"> '''Low'''</span> <br />
| rOCCI is an OCCI 1.1 implementation for OpenNebula 3.x<br />
|}<br />
<br />
== Cloud Brokering Solutions ==<br />
<br />
{| width="90%" cellspacing="0" cellpadding="5" style="border:1px solid black;" class="wikitable"<br />
|- style="background-color:darkgray;"<br />
! Name <br />
! URL <br />
! Cloud SW Support <br />
! OCCI <br />
! Functionalities <br />
! Effort required <br />
! Comments<br />
|-<br />
| CompatibleOne <br />
| http://www.compatibleone.org/ <br />
| OpenStack, OpenNebula, Azure, Vcloud <br />
| Yes, supports OCCI, but implements his own OCCI interface for each of the stacks (PROCCI). <br />
| Accounting, Brokering, User management, Monitoring. <br />
| <span style="color:orange"> '''Medium'''</span> <br />
| <br />
*Compatible One is a complete plattform, with its own user management, accounting and monitoring, so it overlaps in some aspects with the ongoing work. <br />
*It does not expose an OCCI api, the user has to write its own XML files and send them to the broker. <br />
*The credentials for each of the connectors and providers have to be configured in advance by the administrator of the broker service. <br />
*The user has to specify in the manifests the cloud account that he wants to use, and the specific name of the image in the site. It seems that the purpose of CompatibleONE is to deploy and take care of a complete manifest description: A user wants 3 machines of type A in site FOO, and 2 machine of type B in site BAR, so he explicitly defines it in his manifests and CompatibleOne will deploy it on them.<br />
<br />
|-<br />
| COMPSs <br />
| http://www.bsc.es/compss <br />
| &nbsp; OpenNebula, Amazon, Azure, OpenStack <br />
| Yes, support of rOCCI servers and OCCI+OVF <br />
| &nbsp;Automatic parallelization and orchestration of applications and services, elasticity, auto scaling <br />
| <span style="color:orange"> '''Medium'''</span> <br />
| <br />
*COMPSs allows the execution of applications on distributed infrastructures (grids, clusters, cloud). <br />
*Already used for the BioVeL/OpenBio use case. <br />
*Transparent support to different infrastructures; the user only provides his credentials. <br />
*Automatic selection of the VMs types dependending on the tasks constraints. <br />
*The number of VMs is dynamically adjusted to the current workload.<br />
<br />
|-<br />
| VMDIRAC <br />
| https://github.com/DIRACGrid/VMDIRAC/wiki <br />
| &nbsp; OpenNebula, OpenStack, CloudStack and Amazon EC2 <br />
| Yes, it supports rOCCI, OpenNebula "OCCI 0.8", Amazon EC2, OpenStack Nova 1.1 and CloudStack 2 APIs. <br />
| Accounting, monitoring, brokering, scheduling, HEPiX and SSH based VM contextualisation, [https://github.com/DIRACGrid/VMDIRAC/wiki#vm-horizontal-auto-scaling-setup VM Horizontal Auto-scaling]. <br />
| <span style="color:orange"> '''Medium'''</span> <br />
| <br />
*rOCCI support with X509 auth and generic SSH contextualization.<br />
*In production: LHCb (OpenStack and OpenNebula) Belle (Amazon), Work in progress France Federated Cloud. <br />
*Web UI including VM browsing with VM monitoring, and VM Overview Plots (Load, RunningVM, RunnigVM by Endpoint, started jobs, data transfer, transfer files) <br />
*The number of VMs is dynamically adjusted to the current workload.<br />
*Automatic selection of the VMs types depending on the tasks constraints.<br />
*No necessary to install any pluging in the Cloud Managers, works with standard interfaces.<br />
*Separated user credentials are used for job running and VM operator credentials for VM management.<br />
*VMDIRAC developers are willing to collaborate actively with Fedcloud Taskforce.<br />
<br />
|}</div>
Asimon
https://wiki.egi.eu/w/index.php?title=Fedcloud-tf:WorkGroups:Brokering&diff=57845
Fedcloud-tf:WorkGroups:Brokering
2013-07-11T10:22:05Z
<p>Asimon: </p>
<hr />
<div>{{Fedcloud-tf:Menu}} {{Fedcloud-tf:WorkGroups:Menu}} {{TOC_right}} <br />
<br />
<font color="red">Leader: Alvaro Simon, JR1 </font> <br />
<br />
== Collaborators ==<br />
<br />
{| border="1"<br />
|-<br />
! Role <br />
! Institution <br />
! Name<br />
|-<br />
| Collaborator <br />
| OeRC <br />
| Matteo Turilli<br />
|-<br />
| Collaborator <br />
| BSC <br />
| Daniele Lezzi<br />
|}<br />
<br />
== Scope ==<br />
<br />
This workgroup deals with the issues around cloud brokering. With 10+ resource providers lined up to be federated into the EGI cloud testbed, users need effective ways to access cloud resources. The goal is for a user to have a choice between a unified, abstracted view of the cloud testbed as a whole and the opportunity to target specific providers for their needs. As a consequence, this workgroup is concerned with both brokers and OCCI clients. <br />
<br />
== Roadmap ==<br />
<br />
*Collect information about existing solutions for cloud brokering compatible with the OCCI and CDMI management interfaces; <br />
*Collect information about existing solutions for OCCI and CDMI clients; <br />
*Make an inventory of the available solutions; <br />
*Choose a broker and a client for the testbed; <br />
*If possible, join the development teams of the chosen solutions to the task force; <br />
*Coordinate with the TF Resorce Providers to deploy the chosen solutions; <br />
*Extend the demo testbed addressing a real-life use case.<br />
<br />
== Clients Comparison Table ==<br />
<br />
{| width="90%" cellspacing="0" cellpadding="5" style="border:1px solid black;" class="wikitable"<br />
|- style="background-color:darkgray;"<br />
! Client/API <br />
! URL <br />
! OS <br />
! Support <br />
! OCCI/CDMI <br />
! Functionalities <br />
! Effort required <br />
! Comments<br />
|-<br />
| Hybridfox <br />
| http://code.google.com/p/hybridfox/ <br />
| Win/OS X/Linux <br />
| AWS/Eucalyptus/OpenStack/OpenNebula/HP Cloud <br />
| <span style="color:red"> '''NO'''</span> <br />
| Manage Images/Instances/Elastic IPs/Security Groups/Key-pairs <br />
| <span style="color:green"> '''Low'''</span> <br />
| Hybridfox does not support x509 auth, it uses EC2 auth for OpenNebula and OpenStack<br />
|-<br />
| DeltaCloud <br />
| http://deltacloud.apache.org <br />
| Win/OS X/Linux <br />
| EC2/Eucalyptus/OpenStack/OpenNebula/vSphere <br />
| <span style="color:red"> '''NO'''</span> <br />
| Create/Start/Stop/Reboot/Destroy instances <br />
| <span style="color:orange"> '''Medium'''</span> <br />
| DeltaCloud uses its own delta-cloud driver for each framework instead of OCCI. It provides storage support for S3, Warlus, Azure and Google Storage.<br />
|-<br />
| Aeolus <br />
| http://aeolusproject.org/about.html <br />
| Win/OS X/Linux <br />
| Same as DeltaCloud <br />
| <span style="color:red"> '''NO'''</span> <br />
| Create/Start/Stop/.. instances. Manage different instances and Images from different private, public, or hybrid cloud providers. <br />
| <span style="color:orange"> '''Medium'''</span> <br />
| Aeolus uses DeltaCloud cross-cloud abstraction library and it includes some extra functionalities. It includes Aeolus Conductor/Composer/Orchestrator/HA Manager<br />
|-<br />
| rOCCI (API) <br />
| http://dev.opennebula.org/projects/ogf-occi <br />
| Linux <br />
| OpenNebula/EC2 <br />
| <span style="color:green"> '''YES'''</span> <br />
| Create/Start/Stop/Reboot/Destroy instances. Upload and register an image. Network conf. x509 auth. <br />
| <span style="color:green"> '''Low'''</span> <br />
| rOCCI is an OCCI 1.1 implementation for OpenNebula 3.x<br />
|}<br />
<br />
== Cloud Brokering Solutions ==<br />
<br />
{| width="90%" cellspacing="0" cellpadding="5" style="border:1px solid black;" class="wikitable"<br />
|- style="background-color:darkgray;"<br />
! Name <br />
! URL <br />
! Cloud SW Support <br />
! OCCI <br />
! Functionalities <br />
! Effort required <br />
! Comments<br />
|-<br />
| CompatibleOne <br />
| http://www.compatibleone.org/ <br />
| OpenStack, OpenNebula, Azure, Vcloud <br />
| Yes, supports OCCI, but implements his own OCCI interface for each of the stacks (PROCCI). <br />
| Accounting, Brokering, User management, Monitoring. <br />
| <span style="color:orange"> '''Medium'''</span> <br />
| <br />
*Compatible One is a complete plattform, with its own user management, accounting and monitoring, so it overlaps in some aspects with the ongoing work. <br />
*It does not expose an OCCI api, the user has to write its own XML files and send them to the broker. <br />
*The credentials for each of the connectors and providers have to be configured in advance by the administrator of the broker service. <br />
*The user has to specify in the manifests the cloud account that he wants to use, and the specific name of the image in the site. It seems that the purpose of CompatibleONE is to deploy and take care of a complete manifest description: A user wants 3 machines of type A in site FOO, and 2 machine of type B in site BAR, so he explicitly defines it in his manifests and CompatibleOne will deploy it on them.<br />
<br />
|-<br />
| COMPSs <br />
| http://www.bsc.es/compss <br />
| &nbsp; OpenNebula, Amazon, Azure, OpenStack <br />
| Yes, support of rOCCI servers and OCCI+OVF <br />
| &nbsp;Automatic parallelization and orchestration of applications and services, elasticity, auto scaling <br />
| <span style="color:orange"> '''Medium'''</span> <br />
| <br />
*COMPSs allows the execution of applications on distributed infrastructures (grids, clusters, cloud). <br />
*Already used for the BioVeL/OpenBio use case. <br />
*Transparent support to different infrastructures; the user only provides his credentials. <br />
*Automatic selection of the VMs types dependending on the tasks constraints. <br />
*The number of VMs is dynamically adjusted to the current workload.<br />
<br />
|-<br />
| VMDIRAC <br />
| https://github.com/DIRACGrid/VMDIRAC/wiki <br />
| &nbsp; OpenNebula, OpenStack, CloudStack and Amazon EC2 <br />
| Yes, it supports rOCCI, OpenNebula "OCCI 0.8", Amazon EC2, OpenStack Nova 1.1 and CloudStack 2 APIs. <br />
| Accounting, monitoring, brokering, scheduling, HEPiX and SSH based VM contextualisation, [https://github.com/DIRACGrid/VMDIRAC/wiki#vm-horizontal-auto-scaling-setup VM Horizontal Auto-scaling]. <br />
| <span style="color:orange"> '''Medium'''</span> <br />
| <br />
*rOCCI support <br />
*In production: LHCb (OpenStack and OpenNebula) Belle (Amazon), Work in progress France Federated Cloud. <br />
*Web UI including VM browsing with VM monitoring, and VM Overview Plots (Load, RunningVM, RunnigVM by Endpoint, started jobs, data transfer, transfer files) <br />
*The number of VMs is dynamically adjusted to the current workload. <br />
*Automatic selection of the VMs types depending on the tasks constraints. <br />
*No necessary to install any pluging in the Cloud Managers, works with standard interfaces. <br />
*Separated user credentials are used for job running and VM operator credentials for VM management. <br />
*VMDIRAC developers are willing to collaborate actively with Fedcloud Taskforce.<br />
<br />
|}</div>
Asimon
https://wiki.egi.eu/w/index.php?title=Fedcloud-tf:WorkGroups:Brokering&diff=57844
Fedcloud-tf:WorkGroups:Brokering
2013-07-11T10:21:24Z
<p>Asimon: </p>
<hr />
<div>{{Fedcloud-tf:Menu}} {{Fedcloud-tf:WorkGroups:Menu}} {{TOC_right}} <br />
<br />
<font color="red">Leader: Alvaro Simon, JR1 </font> <br />
<br />
== Collaborators ==<br />
<br />
{| border="1"<br />
|-<br />
! Role <br />
! Institution <br />
! Name<br />
|-<br />
| Collaborator <br />
| OeRC <br />
| Matteo Turilli<br />
|-<br />
| Collaborator <br />
| BSC <br />
| Daniele Lezzi<br />
|}<br />
<br />
== Scope ==<br />
<br />
This workgroup deals with the issues around cloud brokering. With 10+ resource providers lined up to be federated into the EGI cloud testbed, users need effective ways to access cloud resources. The goal is for a user to have a choice between a unified, abstracted view of the cloud testbed as a whole and the opportunity to target specific providers for their needs. As a consequence, this workgroup is concerned with both brokers and OCCI clients. <br />
<br />
== Roadmap ==<br />
<br />
*Collect information about existing solutions for cloud brokering compatible with the OCCI and CDMI management interfaces; <br />
*Collect information about existing solutions for OCCI and CDMI clients; <br />
*Make an inventory of the available solutions; <br />
*Choose a broker and a client for the testbed; <br />
*If possible, join the development teams of the chosen solutions to the task force; <br />
*Coordinate with the TF Resorce Providers to deploy the chosen solutions; <br />
*Extend the demo testbed addressing a real-life use case.<br />
<br />
== Clients Comparison Table ==<br />
<br />
{| width="90%" cellspacing="0" cellpadding="5" style="border:1px solid black;" class="wikitable"<br />
|- style="background-color:darkgray;"<br />
! Client/API <br />
! URL <br />
! OS <br />
! Support <br />
! OCCI/CDMI <br />
! Functionalities <br />
! Effort required <br />
! Comments<br />
|-<br />
| Hybridfox <br />
| http://code.google.com/p/hybridfox/ <br />
| Win/OS X/Linux <br />
| AWS/Eucalyptus/OpenStack/OpenNebula/HP Cloud <br />
| <span style="color:red"> '''NO'''</span> <br />
| Manage Images/Instances/Elastic IPs/Security Groups/Key-pairs <br />
| <span style="color:green"> '''Low'''</span> <br />
| Hybridfox does not support x509 auth, it uses EC2 auth for OpenNebula and OpenStack<br />
|-<br />
| DeltaCloud <br />
| http://deltacloud.apache.org <br />
| Win/OS X/Linux <br />
| EC2/Eucalyptus/OpenStack/OpenNebula/vSphere <br />
| <span style="color:red"> '''NO'''</span> <br />
| Create/Start/Stop/Reboot/Destroy instances <br />
| <span style="color:orange"> '''Medium'''</span> <br />
| DeltaCloud uses its own delta-cloud driver for each framework instead of OCCI. It provides storage support for S3, Warlus, Azure and Google Storage.<br />
|-<br />
| Aeolus <br />
| http://aeolusproject.org/about.html <br />
| Win/OS X/Linux <br />
| Same as DeltaCloud <br />
| <span style="color:red"> '''NO'''</span> <br />
| Create/Start/Stop/.. instances. Manage different instances and Images from different private, public, or hybrid cloud providers. <br />
| <span style="color:orange"> '''Medium'''</span> <br />
| Aeolus uses DeltaCloud cross-cloud abstraction library and it includes some extra functionalities. It includes Aeolus Conductor/Composer/Orchestrator/HA Manager<br />
|-<br />
| rOCCI (API) <br />
| http://dev.opennebula.org/projects/ogf-occi <br />
| Linux <br />
| OpenNebula/EC2 <br />
| <span style="color:green"> '''YES'''</span> <br />
| Create/Start/Stop/Reboot/Destroy instances. Upload and register an image. Network conf. x509 auth. <br />
| <span style="color:green"> '''Low'''</span> <br />
| rOCCI is an OCCI 1.1 implementation for OpenNebula 3.x<br />
|}<br />
<br />
== Cloud Brokering Solutions ==<br />
<br />
{| width="90%" cellspacing="0" cellpadding="5" style="border:1px solid black;" class="wikitable"<br />
|- style="background-color:darkgray;"<br />
! Name <br />
! URL <br />
! Cloud SW Support <br />
! OCCI <br />
! Functionalities <br />
! Effort required <br />
! Comments<br />
|-<br />
| CompatibleOne <br />
| http://www.compatibleone.org/ <br />
| OpenStack, OpenNebula, Azure, Vcloud <br />
| Yes, supports OCCI, but implements his own OCCI interface for each of the stacks (PROCCI). <br />
| Accounting, Brokering, User management, Monitoring. <br />
| <span style="color:orange"> '''Medium'''</span> <br />
| <br />
*Compatible One is a complete plattform, with its own user management, accounting and monitoring, so it overlaps in some aspects with the ongoing work. <br />
*It does not expose an OCCI api, the user has to write its own XML files and send them to the broker. <br />
*The credentials for each of the connectors and providers have to be configured in advance by the administrator of the broker service. <br />
*The user has to specify in the manifests the cloud account that he wants to use, and the specific name of the image in the site. It seems that the purpose of CompatibleONE is to deploy and take care of a complete manifest description: A user wants 3 machines of type A in site FOO, and 2 machine of type B in site BAR, so he explicitly defines it in his manifests and CompatibleOne will deploy it on them.<br />
<br />
|-<br />
| COMPSs <br />
| http://www.bsc.es/compss <br />
| &nbsp; OpenNebula, Amazon, Azure, OpenStack <br />
| Yes, support of rOCCI servers and OCCI+OVF <br />
| &nbsp;Automatic parallelization and orchestration of applications and services, elasticity, auto scaling <br />
| <span style="color:orange"> '''Medium'''</span> <br />
| <br />
*COMPSs allows the execution of applications on distributed infrastructures (grids, clusters, cloud). <br />
*Already used for the BioVeL/OpenBio use case. <br />
*Transparent support to different infrastructures; the user only provides his credentials. <br />
*Automatic selection of the VMs types dependending on the tasks constraints. <br />
*The number of VMs is dynamically adjusted to the current workload.<br />
<br />
|-<br />
| VMDIRAC <br />
| https://github.com/DIRACGrid/VMDIRAC/wiki <br />
| &nbsp; OpenNebula, OpenStack, CloudStack and Amazon EC2<br />
| Yes, it supports rOCCI, OpenNebula "OCCI 0.8", Amazon EC2, OpenStack Nova 1.1 and CloudStack 2 APIs. <br />
| Accounting, monitoring, brokering, scheduling, HEPiX and SSH based VM contextualisation, [[https://github.com/DIRACGrid/VMDIRAC/wiki#vm-horizontal-auto-scaling-setup VM Horizontal Auto-scaling]]. <br />
| <span style="color:orange"> '''Medium'''</span> <br />
| <br />
*rOCCI support<br />
*In production: LHCb (OpenStack and OpenNebula) Belle (Amazon), Work in progress France Federated Cloud. <br />
*Web UI including VM browsing with VM monitoring, and VM Overview Plots (Load, RunningVM, RunnigVM by Endpoint, started jobs, data transfer, transfer files)<br />
*The number of VMs is dynamically adjusted to the current workload.<br />
*Automatic selection of the VMs types depending on the tasks constraints.<br />
*No necessary to install any pluging in the Cloud Managers, works with standard interfaces.<br />
*Separated user credentials are used for job running and VM operator credentials for VM management.<br />
*VMDIRAC developers are willing to collaborate actively with Fedcloud Taskforce.<br />
<br />
|}</div>
Asimon
https://wiki.egi.eu/w/index.php?title=Fedcloud-tf:WorkGroups:Brokering&diff=57835
Fedcloud-tf:WorkGroups:Brokering
2013-07-11T08:51:28Z
<p>Asimon: </p>
<hr />
<div>{{Fedcloud-tf:Menu}} {{Fedcloud-tf:WorkGroups:Menu}} {{TOC_right}} <br />
<br />
<font color="red">Leader: Alvaro Simon, JR1 </font> <br />
<br />
== Collaborators ==<br />
<br />
{| border="1"<br />
|-<br />
! Role <br />
! Institution <br />
! Name<br />
|-<br />
| Collaborator <br />
| OeRC <br />
| Matteo Turilli<br />
|-<br />
| Collaborator <br />
| BSC <br />
| Daniele Lezzi<br />
|}<br />
<br />
== Scope ==<br />
<br />
This workgroup deals with the issues around cloud brokering. With 10+ resource providers lined up to be federated into the EGI cloud testbed, users need effective ways to access cloud resources. The goal is for a user to have a choice between a unified, abstracted view of the cloud testbed as a whole and the opportunity to target specific providers for their needs. As a consequence, this workgroup is concerned with both brokers and OCCI clients. <br />
<br />
== Roadmap ==<br />
<br />
*Collect information about existing solutions for cloud brokering compatible with the OCCI and CDMI management interfaces; <br />
*Collect information about existing solutions for OCCI and CDMI clients; <br />
*Make an inventory of the available solutions; <br />
*Choose a broker and a client for the testbed; <br />
*If possible, join the development teams of the chosen solutions to the task force; <br />
*Coordinate with the TF Resorce Providers to deploy the chosen solutions; <br />
*Extend the demo testbed addressing a real-life use case.<br />
<br />
== Clients Comparison Table ==<br />
<br />
{| width="90%" cellspacing="0" cellpadding="5" style="border:1px solid black;" class="wikitable"<br />
|- style="background-color:darkgray;"<br />
! Client/API <br />
! URL <br />
! OS <br />
! Support <br />
! OCCI/CDMI <br />
! Functionalities <br />
! Effort required <br />
! Comments<br />
|-<br />
| Hybridfox <br />
| http://code.google.com/p/hybridfox/ <br />
| Win/OS X/Linux <br />
| AWS/Eucalyptus/OpenStack/OpenNebula/HP Cloud <br />
| <span style="color:red"> '''NO'''</span> <br />
| Manage Images/Instances/Elastic IPs/Security Groups/Key-pairs <br />
| <span style="color:green"> '''Low'''</span> <br />
| Hybridfox does not support x509 auth, it uses EC2 auth for OpenNebula and OpenStack<br />
|-<br />
| DeltaCloud <br />
| http://deltacloud.apache.org <br />
| Win/OS X/Linux <br />
| EC2/Eucalyptus/OpenStack/OpenNebula/vSphere <br />
| <span style="color:red"> '''NO'''</span> <br />
| Create/Start/Stop/Reboot/Destroy instances <br />
| <span style="color:orange"> '''Medium'''</span> <br />
| DeltaCloud uses its own delta-cloud driver for each framework instead of OCCI. It provides storage support for S3, Warlus, Azure and Google Storage.<br />
|-<br />
| Aeolus <br />
| http://aeolusproject.org/about.html <br />
| Win/OS X/Linux <br />
| Same as DeltaCloud <br />
| <span style="color:red"> '''NO'''</span> <br />
| Create/Start/Stop/.. instances. Manage different instances and Images from different private, public, or hybrid cloud providers. <br />
| <span style="color:orange"> '''Medium'''</span> <br />
| Aeolus uses DeltaCloud cross-cloud abstraction library and it includes some extra functionalities. It includes Aeolus Conductor/Composer/Orchestrator/HA Manager<br />
|-<br />
| rOCCI (API) <br />
| http://dev.opennebula.org/projects/ogf-occi <br />
| Linux <br />
| OpenNebula/EC2 <br />
| <span style="color:green"> '''YES'''</span> <br />
| Create/Start/Stop/Reboot/Destroy instances. Upload and register an image. Network conf. x509 auth. <br />
| <span style="color:green"> '''Low'''</span> <br />
| rOCCI is an OCCI 1.1 implementation for OpenNebula 3.x<br />
|}<br />
<br />
== Cloud Brokering Solutions ==<br />
<br />
{| width="90%" cellspacing="0" cellpadding="5" style="border:1px solid black;" class="wikitable"<br />
|- style="background-color:darkgray;"<br />
! Name <br />
! URL <br />
! Cloud SW Support <br />
! OCCI <br />
! Functionalities <br />
! Effort required <br />
! Comments<br />
|-<br />
| CompatibleOne <br />
| http://www.compatibleone.org/ <br />
| OpenStack, OpenNebula, Azure, Vcloud <br />
| Yes, supports OCCI, but implements his own OCCI interface for each of the stacks (PROCCI). <br />
| Accounting, Brokering, User management, Monitoring. <br />
| <span style="color:orange"> '''Medium'''</span> <br />
| <br />
*Compatible One is a complete plattform, with its own user management, accounting and monitoring, so it overlaps in some aspects with the ongoing work. <br />
*It does not expose an OCCI api, the user has to write its own XML files and send them to the broker. <br />
*The credentials for each of the connectors and providers have to be configured in advance by the administrator of the broker service. <br />
*The user has to specify in the manifests the cloud account that he wants to use, and the specific name of the image in the site. It seems that the purpose of CompatibleONE is to deploy and take care of a complete manifest description: A user wants 3 machines of type A in site FOO, and 2 machine of type B in site BAR, so he explicitly defines it in his manifests and CompatibleOne will deploy it on them.<br />
<br />
|-<br />
| COMPSs <br />
| http://www.bsc.es/compss <br />
| &nbsp; OpenNebula, Amazon, Azure, OpenStack <br />
| Yes, support of rOCCI servers and OCCI+OVF <br />
| &nbsp;Automatic parallelization and orchestration of applications and services, elasticity, auto scaling <br />
| <span style="color:orange"> '''Medium'''</span> <br />
| <br />
*COMPSs allows the execution of applications on distributed infrastructures (grids, clusters, cloud). <br />
*Already used for the BioVeL/OpenBio use case. <br />
*Transparent support to different infrastructures; the user only provides his credentials. <br />
*Automatic selection of the VMs types dependending on the tasks constraints. <br />
*The number of VMs is dynamically adjusted to the current workload.<br />
<br />
|-<br />
| VMDIRAC <br />
| https://github.com/DIRACGrid/VMDIRAC/wiki <br />
| &nbsp; OpenNebula, OpenStack and CloudStack<br />
| Yes, it supports rOCCI (under development), OpenNebula "OCCI 0.8", Amazon EC2, OpenStack Nova 1.1 and CloudStack 2 APIs. <br />
| Accounting, brokering, scheduling and VM contextualisation.<br />
| <span style="color:orange"> '''Medium'''</span> <br />
| <br />
*rOCCI support is under development but it will be available in prod soon.<br />
*Already used by LHCb to instantiate cernVM golden copy images.<br />
*It provides an user frontend with X509/VOMS support.<br />
*VMDIRAC developers are willing to collaborate actively with Fedcloud Taskforce.<br />
<br />
|}</div>
Asimon
https://wiki.egi.eu/w/index.php?title=EGI_Quality_Criteria_Verification&diff=57289
EGI Quality Criteria Verification
2013-07-03T08:30:54Z
<p>Asimon: </p>
<hr />
<div>{{SWProv menubar}} {{SWProv QA submenu}} {{TOC_right}} <br />
<br />
== Objective ==<br />
<br />
The main objective of the TSA2.3 is to verify the quality of the software provided by the TP before entering the SR phase and going to production. By doing so we prevent that software that might work enters into the SR and even goes into production but that doesn´t follow the quality criteria defined in TSA2.2. Some of the reasons for doing the verification before the software enters the stage rollout are: <br />
<br />
- Check that the bugs reported in the previous release of the software have been corrected (work in collaboration with DMSU) by the TP. <br />
<br />
- Software can work well in the SR but might not have all the functionalities required <br />
<br />
- Software might not be safe, well documented, or have the necessary installation rules or licenses <br />
<br />
== The Verification Process ==<br />
<br />
When a new product is available, the TP has to follow the [[NSRW IMPLEMENTATION RT|NSRW]]. Once the software is correctly uploaded to the repository, the release enters into the verification phase. The requirements are that the TP has to provide all the necessary information to the verifier (QCV) so that the QCV can assess that the TP has tested in advance the quality of the software. Depending on the type of release, different actions will be taken by the QCV, Verification process is described in detail in the [[EGI Verifier Guideline]]. <br />
<br />
== QC Verification Reports ==<br />
<br />
RT workflow and Verification Templates links are available in this page. First of all verifiers must check QC service mapping to know which test must be verified for each product. This service mapping is available here [https://documents.egi.eu/document/418 QC Verification service mapping] and Verification/Executive Summary templates are available here: [https://documents.egi.eu/document/417 QC Verification Templates]. <br />
<br />
Verifiers must fill all required fields for each product and write a Verification process summary into Executive Summary, this summary should include: <br />
<br />
*A short summary of the installation and configuration process: Installation and configuration were successful?, If not explain any issue or bug found. If the product was rejected explain why. <br />
*If its necessary Verifiers should include a comment for StageRollout: Configuration changes or minor issues found verifying the product. <br />
*If a new QC is necessary and is not included, Verifiers must write a comment to SA2.2 to change current QC.<br />
<br />
<br> <br />
<br />
== UMD Release Candidate Testing ==<br />
<br />
Before each UMD release the verification team checks the new RC. To perform this task SA2.3 VMs have included the RC_testing script. This script is available after each SA2 VM instantiation (into /root/configuration_templates/tools directory). This script is able to detect any package inconsistency after UMD RC repo configuration. The RC testing process is as follows: <br />
<br />
*Verifier should instantiate different Linux flavours VM. For UMD case SL5, SL6 and debian. <br />
*Install UMD RC repo files from UMDx RC page. <br />
*Check RC_tester "PRODUCTS" array. '''This array must be updated to include all UMD products!''' <br />
*It is recommended to use ''screen'' program before RC_tester execution. RC tests take about 2h/3h to finish (depends on OS used and the number of products). <br />
*Run ''RC_tester'' and follows its instructions. <br />
*''RC_tester'' generates several logs, after its execution SA2 verifier should check: <br />
**''installator_OK.log'': List of metapackages installed correctly. <br />
**''installator_ERROR.log'': List of metapackages which contain any issue. <br />
**''&lt;PRODUCT_NAME&gt;_OUTPUT.log'': Complete Product installation log. <br />
**''&lt;PRODUCT_NAME&gt;_postupdate.log'': Info about product update execution. It detects any issue updating current UMD products.<br />
<br />
<br> <br />
<br />
== Verification Work Effort Metrics ==<br />
<br />
Each verification process and change is registered by EGI RT. A complete report is generated on a daily basis each midnight. The XLS file can be downloaded from here [https://rt.egi.eu/rt/SA2/sa2-sw-rel-verification-metrics.xls SA2 Verification Metrics] <br />
<br />
<br> <br />
<br />
== Verification Team ==<br />
<br />
Verifiers team is updated for each UMD release and it is available here: [https://documents.egi.eu/document/514 SA2.3 Verifiers List]. All verifiers are included in the [https://www.egi.eu/sso/groupView/sw-rel-qc SSO sw-rel-qc group] that includes a mailing list and permissions to modify RT tickets related with the verification process. <br />
<br />
== Reference Documents ==<br />
<br />
{| border="1" cellspacing="0" cellpadding="3" style="border: 1px solid black;" class="wikitable sortable"<br />
|- align="left" style="background: none repeat scroll 0% 0% Lightgray;"<br />
! DocDB link <br />
! Release Date <br />
! Document<br />
|-<br />
| [https://documents.egi.eu/document/1700 QCv5] <br />
| 08. 05. 2013 <br />
| UMD Quality Criteria<br />
|-<br />
| [https://documents.egi.eu/document/418 418] <br />
| 08. 05. 2013 <br />
| UMD Products service mapping<br />
|-<br />
| [https://documents.egi.eu/document/417 417] <br />
| 08. 05. 2013 <br />
| QC Verification Templates<br />
|}<br />
<br />
== Metrics ==<br />
<br />
{| border="1" cellspacing="0" cellpadding="3" style="border: 1px solid black;" class="wikitable sortable"<br />
|- align="left" style="background: none repeat scroll 0% 0% Lightgray;"<br />
! Metric <br />
! Description<br />
|-<br />
| M.SA2.4 <br />
| Number of new releases validated against defined criteria: Measures the workload on the validation team.<br />
|-<br />
| M.SA2.5 <br />
| Mean time taken to validate a releas: Indicates how responsive the team is to validating releases.<br />
|-<br />
| M.SA2.6 <br />
| Number of releases failing validation: Indicates the quality assurance process of the software providers.<br />
|}<br />
<br />
== SLAs ==<br />
<br />
EGI SLAs negotiated with the TPs <br />
<br />
[https://documents.egi.eu/document/461 EMI-EGI SLA] <br />
<br />
== Verification engineer skill matrix ==<br />
<br />
{| border="1" class="wikitable" style="text-align: center;"<br />
|+ Verification Cheat Sheet <br />
|-<br />
! width="200" align="left" | Product\Institute <br />
! width="75" | CESGA <br />
! width="75" | IFCA <br />
! width="75" | IFIC <br />
! width="75" | INFN <br />
! width="75" | IN2P3 <br />
! width="75" | JÜLICH <br />
! width="75" | LIP <br />
! width="75" | BADWB <br />
! width="75" | UTC-N <br />
! width="75" | UZH <br />
! width="75" | GRNET <br />
! width="75" | RAL <br />
! width="75" | FZU <br />
! width="300" style="background: none repeat scroll 0% 0% Gray;" | COMMENTS<br />
|-<br />
! align="left" | EMI ARC CE <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI ARC compute cli <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI ARC Infosys <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI dCache <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI gLite MPI <br />
| * <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI CREAM_torque <br />
| * <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI CREAM_lsf <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI EMIR <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
|-<br />
! align="left" | EMI WMS <br />
| * <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI LB <br />
| * <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI FTS <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
|-<br />
! align="left" | EMI DPM <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI LFC_mySQL <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI LFC_Oracle <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI StoRM <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI APEL <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI DGAS <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI BDII <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI UI <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI PX <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI VOMS_mySQL <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" style="background: none repeat scroll 0% 0% Red;" | EMI VOMS_Oracle <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| No verifiers available yet. Oracle training required.<br />
|-<br />
! align="left" style="background: none repeat scroll 0% 0% Red;" | EMI HYDRA <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| No verifiers available yet.<br />
|-<br />
! align="left" style="background: none repeat scroll 0% 0% Red;" | EMI Wnodes <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| No verifiers available yet.<br />
|-<br />
! align="left" style="background: none repeat scroll 0% 0% Red;" | EMI NAGIOS <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| No verifiers available yet.<br />
|-<br />
! align="left" style="background: none repeat scroll 0% 0% Red;" | EMI Pseudonymity <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| No verifiers available yet.<br />
|-<br />
! align="left" | EMI ARGUS <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI UNICORE TSI <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI UNICORE WS <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI UNICORE Client <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI UNICORE Registry <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI UNICORE Gateway <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI UNICORE Hila <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI UNICORE xuudb <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI UNICORE Uvos <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI AMGA <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | IGE SAGA-SD <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| No verifiers available yet.<br />
|-<br />
! align="left" | IGE GRAM5 <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | IGE GSISSH <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | IGE GridFTP <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | IGE myProxy <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | IGE RLS <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | IGE GridWay <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | IGE SAM <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | IGE OGSA-DAI <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | IGE Security <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | IGE Gridsafe <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|}<br />
<br />
<br> <br />
<br />
[https://www.egi.eu/earlyAdopters/table Early Adopters list] <br />
<br />
[https://www.egi.eu/earlyAdopters/teams Early Adopters per UMD product]</div>
Asimon
https://wiki.egi.eu/w/index.php?title=EGI_Quality_Criteria_Verification&diff=57287
EGI Quality Criteria Verification
2013-07-03T08:30:12Z
<p>Asimon: </p>
<hr />
<div>{{SWProv menubar}} {{SWProv QA submenu}} {{TOC_right}} <br />
<br />
== Objective ==<br />
<br />
The main objective of the TSA2.3 is to verify the quality of the software provided by the TP before entering the SR phase and going to production. By doing so we prevent that software that might work enters into the SR and even goes into production but that doesn´t follow the quality criteria defined in TSA2.2. Some of the reasons for doing the verification before the software enters the stage rollout are: <br />
<br />
- Check that the bugs reported in the previous release of the software have been corrected (work in collaboration with DMSU) by the TP. <br />
<br />
- Software can work well in the SR but might not have all the functionalities required <br />
<br />
- Software might not be safe, well documented, or have the necessary installation rules or licenses <br />
<br />
== The Verification Process ==<br />
<br />
When a new product is available, the TP has to follow the [[NSRW IMPLEMENTATION RT|NSRW]]. Once the software is correctly uploaded to the repository, the release enters into the verification phase. The requirements are that the TP has to provide all the necessary information to the verifier (QCV) so that the QCV can assess that the TP has tested in advance the quality of the software. Depending on the type of release, different actions will be taken by the QCV, Verification process is described in detail in the [[EGI Verifier Guideline]]. <br />
<br />
== QC Verification Reports ==<br />
<br />
RT workflow and Verification Templates links are available in this page. First of all verifiers must check QC service mapping to know which test must be verified for each product. This service mapping is available here [https://documents.egi.eu/document/418 QC Verification service mapping] and Verification/Executive Summary templates are available here: [https://documents.egi.eu/document/417 QC Verification Templates]. <br />
<br />
Verifiers must fill all required fields for each product and write a Verification process summary into Executive Summary, this summary should include: <br />
<br />
*A short summary of the installation and configuration process: Installation and configuration were successful?, If not explain any issue or bug found. If the product was rejected explain why. <br />
*If its necessary Verifiers should include a comment for StageRollout: Configuration changes or minor issues found verifying the product. <br />
*If a new QC is necessary and is not included, Verifiers must write a comment to SA2.2 to change current QC.<br />
<br />
<br> <br />
<br />
== UMD Release Candidate Testing ==<br />
<br />
Before each UMD release the verification team checks the new RC. To perform this task SA2.3 VMs have included the RC_testing script. This script is available after each SA2 VM instantiation (into /root/configuration_templates/tools directory). This script is able to detect any package inconsistency after UMD RC repo configuration. The RC testing process is as follows: <br />
<br />
*Verifier should instantiate different Linux flavours VM. For UMD case SL5, SL6 and debian. <br />
*Install UMD RC repo files from UMDx RC page. <br />
*Check RC_tester "PRODUCTS" array. '''This array should be updated to include all UMD products!''' <br />
*It is recommended to use ''screen'' program before RC_tester execution. RC tests take about 2h/3h to finish (depends on OS used and the number of products). <br />
*Run ''RC_tester'' and follows its instructions. <br />
*''RC_tester'' generates several logs, after its execution SA2 verifier should check: <br />
**''installator_OK.log'': List of metapackages installed correctly. <br />
**''installator_ERROR.log'': List of metapackages which contain any issue. <br />
**''&lt;PRODUCT_NAME&gt;_OUTPUT.log'': Complete Product installation log. <br />
**''&lt;PRODUCT_NAME&gt;_postupdate.log'': Info about product update execution. It detects any issue updating current UMD products.<br />
<br />
<br> <br />
<br />
== Verification Work Effort Metrics ==<br />
<br />
Each verification process and change is registered by EGI RT. A complete report is generated on a daily basis each midnight. The XLS file can be downloaded from here [https://rt.egi.eu/rt/SA2/sa2-sw-rel-verification-metrics.xls SA2 Verification Metrics] <br />
<br />
<br> <br />
<br />
== Verification Team ==<br />
<br />
Verifiers team is updated for each UMD release and it is available here: [https://documents.egi.eu/document/514 SA2.3 Verifiers List]. All verifiers are included in the [https://www.egi.eu/sso/groupView/sw-rel-qc SSO sw-rel-qc group] that includes a mailing list and permissions to modify RT tickets related with the verification process. <br />
<br />
== Reference Documents ==<br />
<br />
{| border="1" cellspacing="0" cellpadding="3" style="border: 1px solid black;" class="wikitable sortable"<br />
|- align="left" style="background: none repeat scroll 0% 0% Lightgray;"<br />
! DocDB link <br />
! Release Date <br />
! Document<br />
|-<br />
| [https://documents.egi.eu/document/1700 QCv5] <br />
| 08. 05. 2013 <br />
| UMD Quality Criteria<br />
|-<br />
| [https://documents.egi.eu/document/418 418] <br />
| 08. 05. 2013 <br />
| UMD Products service mapping<br />
|-<br />
| [https://documents.egi.eu/document/417 417] <br />
| 08. 05. 2013 <br />
| QC Verification Templates<br />
|}<br />
<br />
== Metrics ==<br />
<br />
{| border="1" cellspacing="0" cellpadding="3" style="border: 1px solid black;" class="wikitable sortable"<br />
|- align="left" style="background: none repeat scroll 0% 0% Lightgray;"<br />
! Metric <br />
! Description<br />
|-<br />
| M.SA2.4 <br />
| Number of new releases validated against defined criteria: Measures the workload on the validation team.<br />
|-<br />
| M.SA2.5 <br />
| Mean time taken to validate a releas: Indicates how responsive the team is to validating releases.<br />
|-<br />
| M.SA2.6 <br />
| Number of releases failing validation: Indicates the quality assurance process of the software providers.<br />
|}<br />
<br />
== SLAs ==<br />
<br />
EGI SLAs negotiated with the TPs <br />
<br />
[https://documents.egi.eu/document/461 EMI-EGI SLA] <br />
<br />
== Verification engineer skill matrix ==<br />
<br />
{| border="1" class="wikitable" style="text-align: center;"<br />
|+ Verification Cheat Sheet <br />
|-<br />
! width="200" align="left" | Product\Institute <br />
! width="75" | CESGA <br />
! width="75" | IFCA <br />
! width="75" | IFIC <br />
! width="75" | INFN <br />
! width="75" | IN2P3 <br />
! width="75" | JÜLICH <br />
! width="75" | LIP <br />
! width="75" | BADWB <br />
! width="75" | UTC-N <br />
! width="75" | UZH <br />
! width="75" | GRNET <br />
! width="75" | RAL <br />
! width="75" | FZU <br />
! width="300" style="background: none repeat scroll 0% 0% Gray;" | COMMENTS<br />
|-<br />
! align="left" | EMI ARC CE <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI ARC compute cli <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI ARC Infosys <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI dCache <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI gLite MPI <br />
| * <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI CREAM_torque <br />
| * <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI CREAM_lsf <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI EMIR <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
|-<br />
! align="left" | EMI WMS <br />
| * <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI LB <br />
| * <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI FTS <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
|-<br />
! align="left" | EMI DPM <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI LFC_mySQL <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI LFC_Oracle <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI StoRM <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI APEL <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI DGAS <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI BDII <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI UI <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI PX <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI VOMS_mySQL <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" style="background: none repeat scroll 0% 0% Red;" | EMI VOMS_Oracle <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| No verifiers available yet. Oracle training required.<br />
|-<br />
! align="left" style="background: none repeat scroll 0% 0% Red;" | EMI HYDRA <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| No verifiers available yet.<br />
|-<br />
! align="left" style="background: none repeat scroll 0% 0% Red;" | EMI Wnodes <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| No verifiers available yet.<br />
|-<br />
! align="left" style="background: none repeat scroll 0% 0% Red;" | EMI NAGIOS <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| No verifiers available yet.<br />
|-<br />
! align="left" style="background: none repeat scroll 0% 0% Red;" | EMI Pseudonymity <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| No verifiers available yet.<br />
|-<br />
! align="left" | EMI ARGUS <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI UNICORE TSI <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI UNICORE WS <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI UNICORE Client <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI UNICORE Registry <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI UNICORE Gateway <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI UNICORE Hila <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI UNICORE xuudb <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI UNICORE Uvos <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI AMGA <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | IGE SAGA-SD <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| No verifiers available yet.<br />
|-<br />
! align="left" | IGE GRAM5 <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | IGE GSISSH <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | IGE GridFTP <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | IGE myProxy <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | IGE RLS <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | IGE GridWay <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | IGE SAM <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | IGE OGSA-DAI <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | IGE Security <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | IGE Gridsafe <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|}<br />
<br />
<br> <br />
<br />
[https://www.egi.eu/earlyAdopters/table Early Adopters list] <br />
<br />
[https://www.egi.eu/earlyAdopters/teams Early Adopters per UMD product]</div>
Asimon
https://wiki.egi.eu/w/index.php?title=EGI_Quality_Criteria_Verification&diff=57275
EGI Quality Criteria Verification
2013-07-03T08:07:58Z
<p>Asimon: </p>
<hr />
<div>{{SWProv menubar}} {{SWProv QA submenu}} {{TOC_right}} <br />
<br />
== Objective ==<br />
<br />
The main objective of the TSA2.3 is to verify the quality of the software provided by the TP before entering the SR phase and going to production. By doing so we prevent that software that might work enters into the SR and even goes into production but that doesn´t follow the quality criteria defined in TSA2.2. Some of the reasons for doing the verification before the software enters the stage rollout are: <br />
<br />
- Check that the bugs reported in the previous release of the software have been corrected (work in collaboration with DMSU) by the TP. <br />
<br />
- Software can work well in the SR but might not have all the functionalities required <br />
<br />
- Software might not be safe, well documented, or have the necessary installation rules or licenses <br />
<br />
== The Verification Process ==<br />
<br />
When a new product is available, the TP has to follow the [[NSRW IMPLEMENTATION RT|NSRW]]. Once the software is correctly uploaded to the repository, the release enters into the verification phase. The requirements are that the TP has to provide all the necessary information to the verifier (QCV) so that the QCV can assess that the TP has tested in advance the quality of the software. Depending on the type of release, different actions will be taken by the QCV, Verification process is described in detail in the [[EGI Verifier Guideline]]. <br />
<br />
== QC Verification Reports ==<br />
<br />
RT workflow and Verification Templates links are available in this page. First of all verifiers must check QC service mapping to know which test must be verified for each product. This service mapping is available here [https://documents.egi.eu/document/418 QC Verification service mapping] and Verification/Executive Summary templates are available here: [https://documents.egi.eu/document/417 QC Verification Templates]. <br />
<br />
Verifiers must fill all required fields for each product and write a Verification process summary into Executive Summary, this summary should include: <br />
<br />
*A short summary of the installation and configuration process: Installation and configuration were successful?, If not explain any issue or bug found. If the product was rejected explain why. <br />
*If its necessary Verifiers should include a comment for StageRollout: Configuration changes or minor issues found verifying the product. <br />
*If a new QC is necessary and is not included, Verifiers must write a comment to SA2.2 to change current QC.<br />
<br />
<br> <br />
<br />
== UMD Release Candidate Testing ==<br />
<br />
Before each UMD release the verification team checks the new RC. To perform this task SA2.3 VMs have included the RC_testing script. This script is available after each SA2 VM instantiation (into /root/configuration_templates/tools directory). This script is able to detect any package inconsistency after UMD RC repo configuration. The RC testing process is as follows: <br />
<br />
*Verifier should instantiate different Linux flavours VM. For UMD case SL5, SL6 and debian. <br />
*Install UMD RC repo files from UMDx RC page. <br />
*Check RC_tester "PRODUCTS" array. '''This array should be updated to include all UMD products!''' <br />
*It is recommended to use ''screen'' program before run RC_tester. RC testing should take about 3h to finish (depends on OS). <br />
*Run ''RC_tester'' and follows its intructions. <br />
*''RC_tester'' generates several logs, after its execution SA2 verifier should check: <br />
**''installator_OK.log'': List of metapackages installed correctly. <br />
**''installator_ERROR.log'': List of metapackages which contain any issue. <br />
**''&lt;PRODUCT_NAME&gt;_OUTPUT.log'': Complete Product installation log. <br />
**''&lt;PRODUCT_NAME&gt;_postupdate.log'': Info about product update execution. It detects any issue updating current UMD products.<br />
<br />
<br> <br />
<br />
== Verification Work Effort Metrics ==<br />
<br />
Each verification process and change is registered by EGI RT. A complete report is generated on a daily basis each midnight. The XLS file can be downloaded from here [https://rt.egi.eu/rt/SA2/sa2-sw-rel-verification-metrics.xls SA2 Verification Metrics] <br />
<br />
<br> <br />
<br />
== Verification Team ==<br />
<br />
Verifiers team is updated for each UMD release and it is available here: [https://documents.egi.eu/document/514 SA2.3 Verifiers List]. All verifiers are included in the [https://www.egi.eu/sso/groupView/sw-rel-qc SSO sw-rel-qc group] that includes a mailing list and permissions to modify RT tickets related with the verification process. <br />
<br />
== Reference Documents ==<br />
<br />
{| border="1" cellspacing="0" cellpadding="3" style="border: 1px solid black;" class="wikitable sortable"<br />
|- align="left" style="background: none repeat scroll 0% 0% Lightgray;"<br />
! DocDB link <br />
! Release Date <br />
! Document<br />
|-<br />
| [https://documents.egi.eu/document/1700 QCv5] <br />
| 08. 05. 2013 <br />
| UMD Quality Criteria<br />
|-<br />
| [https://documents.egi.eu/document/418 418] <br />
| 08. 05. 2013 <br />
| UMD Products service mapping<br />
|-<br />
| [https://documents.egi.eu/document/417 417] <br />
| 08. 05. 2013 <br />
| QC Verification Templates<br />
|}<br />
<br />
== Metrics ==<br />
<br />
{| border="1" cellspacing="0" cellpadding="3" style="border: 1px solid black;" class="wikitable sortable"<br />
|- align="left" style="background: none repeat scroll 0% 0% Lightgray;"<br />
! Metric <br />
! Description<br />
|-<br />
| M.SA2.4 <br />
| Number of new releases validated against defined criteria: Measures the workload on the validation team.<br />
|-<br />
| M.SA2.5 <br />
| Mean time taken to validate a releas: Indicates how responsive the team is to validating releases.<br />
|-<br />
| M.SA2.6 <br />
| Number of releases failing validation: Indicates the quality assurance process of the software providers.<br />
|}<br />
<br />
== SLAs ==<br />
<br />
EGI SLAs negotiated with the TPs <br />
<br />
[https://documents.egi.eu/document/461 EMI-EGI SLA] <br />
<br />
== Verification engineer skill matrix ==<br />
<br />
{| border="1" class="wikitable" style="text-align: center;"<br />
|+ Verification Cheat Sheet <br />
|-<br />
! width="200" align="left" | Product\Institute <br />
! width="75" | CESGA <br />
! width="75" | IFCA <br />
! width="75" | IFIC <br />
! width="75" | INFN <br />
! width="75" | IN2P3 <br />
! width="75" | JÜLICH <br />
! width="75" | LIP <br />
! width="75" | BADWB <br />
! width="75" | UTC-N <br />
! width="75" | UZH <br />
! width="75" | GRNET <br />
! width="75" | RAL <br />
! width="75" | FZU <br />
! width="300" style="background: none repeat scroll 0% 0% Gray;" | COMMENTS<br />
|-<br />
! align="left" | EMI ARC CE <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI ARC compute cli <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI ARC Infosys <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI dCache <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI gLite MPI <br />
| * <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI CREAM_torque <br />
| * <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI CREAM_lsf <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI EMIR <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
|-<br />
! align="left" | EMI WMS <br />
| * <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI LB <br />
| * <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI FTS <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
|-<br />
! align="left" | EMI DPM <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI LFC_mySQL <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI LFC_Oracle <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI StoRM <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI APEL <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI DGAS <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI BDII <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI UI <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI PX <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI VOMS_mySQL <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" style="background: none repeat scroll 0% 0% Red;" | EMI VOMS_Oracle <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| No verifiers available yet. Oracle training required.<br />
|-<br />
! align="left" style="background: none repeat scroll 0% 0% Red;" | EMI HYDRA <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| No verifiers available yet.<br />
|-<br />
! align="left" style="background: none repeat scroll 0% 0% Red;" | EMI Wnodes <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| No verifiers available yet.<br />
|-<br />
! align="left" style="background: none repeat scroll 0% 0% Red;" | EMI NAGIOS <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| No verifiers available yet.<br />
|-<br />
! align="left" style="background: none repeat scroll 0% 0% Red;" | EMI Pseudonymity <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| No verifiers available yet.<br />
|-<br />
! align="left" | EMI ARGUS <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI UNICORE TSI <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI UNICORE WS <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI UNICORE Client <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI UNICORE Registry <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI UNICORE Gateway <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI UNICORE Hila <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI UNICORE xuudb <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI UNICORE Uvos <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI AMGA <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | IGE SAGA-SD <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| No verifiers available yet.<br />
|-<br />
! align="left" | IGE GRAM5 <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | IGE GSISSH <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | IGE GridFTP <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | IGE myProxy <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | IGE RLS <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | IGE GridWay <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | IGE SAM <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | IGE OGSA-DAI <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | IGE Security <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | IGE Gridsafe <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|}<br />
<br />
<br> <br />
<br />
[https://www.egi.eu/earlyAdopters/table Early Adopters list] <br />
<br />
[https://www.egi.eu/earlyAdopters/teams Early Adopters per UMD product]</div>
Asimon
https://wiki.egi.eu/w/index.php?title=EGI_Quality_Criteria_Verification&diff=57274
EGI Quality Criteria Verification
2013-07-03T08:07:09Z
<p>Asimon: </p>
<hr />
<div>{{SWProv menubar}} {{SWProv QA submenu}} {{TOC_right}} <br />
<br />
== Objective ==<br />
<br />
The main objective of the TSA2.3 is to verify the quality of the software provided by the TP before entering the SR phase and going to production. By doing so we prevent that software that might work enters into the SR and even goes into production but that doesn´t follow the quality criteria defined in TSA2.2. Some of the reasons for doing the verification before the software enters the stage rollout are: <br />
<br />
- Check that the bugs reported in the previous release of the software have been corrected (work in collaboration with DMSU) by the TP. <br />
<br />
- Software can work well in the SR but might not have all the functionalities required <br />
<br />
- Software might not be safe, well documented, or have the necessary installation rules or licenses <br />
<br />
== The Verification Process ==<br />
<br />
When a new product is available, the TP has to follow the [[NSRW IMPLEMENTATION RT|NSRW]]. Once the software is correctly uploaded to the repository, the release enters into the verification phase. The requirements are that the TP has to provide all the necessary information to the verifier (QCV) so that the QCV can assess that the TP has tested in advance the quality of the software. Depending on the type of release, different actions will be taken by the QCV, Verification process is described in detail in the [[EGI Verifier Guideline]]. <br />
<br />
== QC Verification Reports ==<br />
<br />
RT workflow and Verification Templates links are available in this page. First of all verifiers must check QC service mapping to know which test must be verified for each product. This service mapping is available here [https://documents.egi.eu/document/418 QC Verification service mapping] and Verification/Executive Summary templates are available here: [https://documents.egi.eu/document/417 QC Verification Templates]. <br />
<br />
Verifiers must fill all required fields for each product and write a Verification process summary into Executive Summary, this summary should include: <br />
<br />
*A short summary of the installation and configuration process: Installation and configuration were successful?, If not explain any issue or bug found. If the product was rejected explain why. <br />
*If its necessary Verifiers should include a comment for StageRollout: Configuration changes or minor issues found verifying the product. <br />
*If a new QC is necessary and is not included, Verifiers must write a comment to SA2.2 to change current QC.<br />
<br />
<br> <br />
<br />
== UMD Release Candidate Testing ==<br />
<br />
Before each UMD release the verification team checks the new RC. To perform this task SA2.3 VMs have included the RC_testing script. This script is available after each SA2 VM instantiation (into /root/configuration_templates/tools directory). This script is able to detect any package inconsistency after UMD RC repo configuration. The RC testing process is as follows: <br />
<br />
*Verifier should instantiate different Linux flavours VM. For UMD case SL5, SL6 and debian. <br />
*Install UMD RC repo files from UMDx RC page. <br />
*Check RC_tester "PRODUCTS" array. '''This array should be updated to include all UMD products!'''<br />
*It is recommended to use ''screen'' program before run RC_tester. RC testing should take about 3h to finish (depends on OS). <br />
*Run ''RC_tester'' and follows its intructions. <br />
*''RC_tester'' generates several logs, after its execution SA2 verifier should check: <br />
**''installator_OK.log'': List of metapackages installed correctly. <br />
**''installator_ERROR.log'': List of metapackages which contain any issue. <br />
**''&lt;PRODUC_NAME&gt;_OUTPUT.log'': Complete Product installation log. <br />
**''&lt;PRODUC_NAME&gt;_postupdate.log'': Info about product update execution. It detects any issue updating current UMD products.<br />
<br />
<br> <br />
<br />
== Verification Work Effort Metrics ==<br />
<br />
Each verification process and change is registered by EGI RT. A complete report is generated on a daily basis each midnight. The XLS file can be downloaded from here [https://rt.egi.eu/rt/SA2/sa2-sw-rel-verification-metrics.xls SA2 Verification Metrics] <br />
<br />
<br> <br />
<br />
== Verification Team ==<br />
<br />
Verifiers team is updated for each UMD release and it is available here: [https://documents.egi.eu/document/514 SA2.3 Verifiers List]. All verifiers are included in the [https://www.egi.eu/sso/groupView/sw-rel-qc SSO sw-rel-qc group] that includes a mailing list and permissions to modify RT tickets related with the verification process. <br />
<br />
== Reference Documents ==<br />
<br />
{| border="1" cellspacing="0" cellpadding="3" style="border: 1px solid black;" class="wikitable sortable"<br />
|- align="left" style="background: none repeat scroll 0% 0% Lightgray;"<br />
! DocDB link <br />
! Release Date <br />
! Document<br />
|-<br />
| [https://documents.egi.eu/document/1700 QCv5] <br />
| 08. 05. 2013 <br />
| UMD Quality Criteria<br />
|-<br />
| [https://documents.egi.eu/document/418 418] <br />
| 08. 05. 2013 <br />
| UMD Products service mapping<br />
|-<br />
| [https://documents.egi.eu/document/417 417] <br />
| 08. 05. 2013 <br />
| QC Verification Templates<br />
|}<br />
<br />
== Metrics ==<br />
<br />
{| border="1" cellspacing="0" cellpadding="3" style="border: 1px solid black;" class="wikitable sortable"<br />
|- align="left" style="background: none repeat scroll 0% 0% Lightgray;"<br />
! Metric <br />
! Description<br />
|-<br />
| M.SA2.4 <br />
| Number of new releases validated against defined criteria: Measures the workload on the validation team.<br />
|-<br />
| M.SA2.5 <br />
| Mean time taken to validate a releas: Indicates how responsive the team is to validating releases.<br />
|-<br />
| M.SA2.6 <br />
| Number of releases failing validation: Indicates the quality assurance process of the software providers.<br />
|}<br />
<br />
== SLAs ==<br />
<br />
EGI SLAs negotiated with the TPs <br />
<br />
[https://documents.egi.eu/document/461 EMI-EGI SLA] <br />
<br />
== Verification engineer skill matrix ==<br />
<br />
{| border="1" class="wikitable" style="text-align: center;"<br />
|+ Verification Cheat Sheet <br />
|-<br />
! width="200" align="left" | Product\Institute <br />
! width="75" | CESGA <br />
! width="75" | IFCA <br />
! width="75" | IFIC <br />
! width="75" | INFN <br />
! width="75" | IN2P3 <br />
! width="75" | JÜLICH <br />
! width="75" | LIP <br />
! width="75" | BADWB <br />
! width="75" | UTC-N <br />
! width="75" | UZH <br />
! width="75" | GRNET <br />
! width="75" | RAL <br />
! width="75" | FZU <br />
! width="300" style="background: none repeat scroll 0% 0% Gray;" | COMMENTS<br />
|-<br />
! align="left" | EMI ARC CE <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI ARC compute cli <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI ARC Infosys <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI dCache <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI gLite MPI <br />
| * <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI CREAM_torque <br />
| * <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI CREAM_lsf <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI EMIR <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
|-<br />
! align="left" | EMI WMS <br />
| * <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI LB <br />
| * <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI FTS <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
|-<br />
! align="left" | EMI DPM <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI LFC_mySQL <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI LFC_Oracle <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI StoRM <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI APEL <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI DGAS <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI BDII <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI UI <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI PX <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI VOMS_mySQL <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" style="background: none repeat scroll 0% 0% Red;" | EMI VOMS_Oracle <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| No verifiers available yet. Oracle training required.<br />
|-<br />
! align="left" style="background: none repeat scroll 0% 0% Red;" | EMI HYDRA <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| No verifiers available yet.<br />
|-<br />
! align="left" style="background: none repeat scroll 0% 0% Red;" | EMI Wnodes <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| No verifiers available yet.<br />
|-<br />
! align="left" style="background: none repeat scroll 0% 0% Red;" | EMI NAGIOS <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| No verifiers available yet.<br />
|-<br />
! align="left" style="background: none repeat scroll 0% 0% Red;" | EMI Pseudonymity <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| No verifiers available yet.<br />
|-<br />
! align="left" | EMI ARGUS <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI UNICORE TSI <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI UNICORE WS <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI UNICORE Client <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI UNICORE Registry <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI UNICORE Gateway <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI UNICORE Hila <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI UNICORE xuudb <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI UNICORE Uvos <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | EMI AMGA <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | IGE SAGA-SD <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| No verifiers available yet.<br />
|-<br />
! align="left" | IGE GRAM5 <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | IGE GSISSH <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | IGE GridFTP <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | IGE myProxy <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | IGE RLS <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | IGE GridWay <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | IGE SAM <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | IGE OGSA-DAI <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | IGE Security <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
! align="left" | IGE Gridsafe <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| * <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|}<br />
<br />
<br> <br />
<br />
[https://www.egi.eu/earlyAdopters/table Early Adopters list] <br />
<br />
[https://www.egi.eu/earlyAdopters/teams Early Adopters per UMD product]</div>
Asimon