Alert.png The wiki is deprecated and due to be decommissioned by the end of September 2022.
The content is being migrated to other supports, new updates will be ignored and lost.
If needed you can get in touch with EGI SDIS team using operations @ egi.eu.

Difference between revisions of "Fedcloud-tf:Testbed"

From EGIWiki
Jump to navigation Jump to search
Line 2: Line 2:




= Resource Providers inventory  =
== Resource Providers inventory  ==


The Resource Providers that have joined the Task Force make available a small portion of their cloud infrastructure in order to design and test the technologies described in the blueprint document for clouds federation. These resources are available for testing to every user community interested in testing/using them.  
The Resource Providers that have joined the Task Force make available a small portion of their cloud infrastructure in order to design and test the technologies described in the blueprint document for clouds federation. These resources are available for testing to every user community interested in testing/using them.  


For the description of the Capabilities please refer to the Cloud Integration Profile document available at [https://documents.egi.eu/document/435 https://documents.egi.eu/document/435]  
For the description of the Capabilities please refer to the [https://documents.egi.eu/document/435 Cloud Integration Profile document].


Please note: wherever suitable and possible, any standards implemented by the adopted cloud software should be noted.  
Please note: wherever suitable and possible, any standards implemented by the adopted cloud software should be noted.  




{| cellspacing="1" cellpadding="1" border="1"
{| border="1" cellspacing="1" cellpadding="1"
|- style="background-color: lightgray;"
! rowspan="2" | Provider
! rowspan="2" | Status
! rowspan="2" | capacity
! colspan="6" | Capabilities
! colspan="2" | Management Interface
! colspan="2" | Authentication
|- style="background-color:lightgray;"
|- style="background-color:lightgray;"
! scope="col" | Resource Centre
! | VM Management
! scope="col" | Status
! | Data  
! scope="col" | committed test bed capacity
! | Information  
! scope="col" | Capability:<br>VM Management  
! | Monitoring  
! scope="col" | Capability:<br>Data  
! | Accounting  
! scope="col" | Capability:<br>Information  
! | Notification  
! scope="col" | Capability:<br>Monitoring  
! | Supported
! scope="col" | Capability:<br>Accounting  
! | Planned
! scope="col" | Capability:<br>Notification  
! | Service layer  
| '''Management Interface (curently supported)'''
! | VMs
| '''Management Interface (future consideration''')
| '''Authentication on Service layer'''
| '''Authentication for Login into Cloud Instances'''
|-
|-
| <div id='cesnet'>CESNET</div> (Miroslav Ruda)  
| <div id="cesnet">CESNET</div> (Miroslav Ruda)  
|  
|  
| several servers quickly, more (~10) can be added later this year  
| Several servers quickly, more (~10) can be added later this year  
| OpenNebula 3.0, to increase heterogenity we could add Eucalyptus 2.0 or Nimbus+Cumulus interface too  
| OpenNebula 3.0, to increase heterogeneity we could add Eucalyptus 2.0 or Nimbus + Cumulus interface too  
| Shared NFS filesystem, GridFTP remote access, can provide S3 Cumulus implementation too  
| Shared NFS filesystem, GridFTP remote access, can provide S3 Cumulus implementation too  
| N/A? OpenNebula web interface?  
| N/A? OpenNebula web interface?  
| Nagios infrastructure is ready, custom probes from other groups can be added quickly. Ganglia/Munin can be added on request.  
| Nagios infrastructure is ready, custom probes from other groups can be added quickly. Ganglia / Munin can be added on request.  
| N/A? If reporter for standard usage records is implemented, can be deployed.  
| N/A? If reporter for standard usage records is implemented, can be deployed.  
| N/A? STOMP based EGI messaging infrastructure in available on the site  
| N/A? STOMP based EGI messaging infrastructure in available on the site  
| OCCI and partial EC2 provided by OpenNebula  
| OCCI and partial EC2 provided by OpenNebula  
| Open for discussion  
| Open for discussion  
| X509 certificates prefered, login/password as temporary solution may be possible  
| X509 certificates preferred, username and password as temporary solution may be possible  
| in general up to user, plan to support registered user SSH keys for root access
| In general up to user, plan to support registered user SSH keys for root access
|-
|-
| <div id='oerc'>OeRC (UK NGI)</div> (David Wallom, Matteo Turilli)  
| <div id="oerc">OeRC (UK NGI)</div> (David Wallom, Matteo Turilli)  
|  
|  
| 10 servers, between 8 and 2 VMs each
| 10 servers, between 8 and 2 VMs each  
| Currently open Eucalyptus 2.0, moving to OpenStack, both as supplied by Canonical Ubuntu Enterprise Cloud  
| Currently open Eucalyptus 2.0, moving to OpenStack, both as supplied by Canonical Ubuntu Enterprise Cloud  
| Data supplied through S3/EBS capable storage services  
| Data supplied through S3/EBS capable storage services  
Line 50: Line 54:
| Developed service utilising extended OGF UR schema  
| Developed service utilising extended OGF UR schema  
| N/A  
| N/A  
| Partial EC2 as implemented by OpenStack
| Partial EC2 as implemented by OpenStack  
| OCCI when available
| OCCI when available  
| User name and password as implemented by OpenStack
| Username and password as implemented by OpenStack  
| As chosen by the users
| As chosen by the users
|-
|-
| <div id='cyfronet'>Cyfronet</div> (Tomasz Szepieniec, Marcin Radecki)  
| <div id="cyfronet">Cyfronet</div> (Tomasz Szepieniec, Marcin Radecki)  
|  
|  
| for initial setup 12 servers ready, extensions depending on usage  
| for initial setup 12 servers ready, extensions depending on usage  
Line 62: Line 66:
| Web interface integrated with PL-Grid User Portal  
| Web interface integrated with PL-Grid User Portal  
| Nagios integration, experimenting with zabbix  
| Nagios integration, experimenting with zabbix  
| planned for early 2012 integration with PL-Grid Accounting using OpenNebula 3 accounting components  
| Planned for early 2012 integration with PL-Grid Accounting using OpenNebula 3 accounting components  
| N/A  
| N/A  
|  
|  
Line 69: Line 73:
|  
|  
|- style="background:red; color:white"
|- style="background:red; color:white"
| <div id='sara'>SARA</div> (Floris Sluiter, Maurice Bouwhuis)  
| <div id="sara">SARA</div> (Floris Sluiter, Maurice Bouwhuis)  
|
|
|
|
|
|  
|  
|  
|  
|  
|  
|
|
|
|
|
|  
|  
|  
|  
Line 83: Line 87:
|  
|  
|-
|-
| <div id='kth'>KTH</div> (Zeeshan Ali Shah)  
| <div id="kth">KTH</div> (Zeeshan Ali Shah)  
| Accessible since January, 2011  
| Accessible since January, 2011  
| Initially 2 Servers with Total 4 cores , 16 GB RAM and 1TB storage -
| Initially 2 Servers with Total 4 cores, 16 GB RAM and 1TB storage  
| OpenNebula  
| OpenNebula  
| Possibility to mount nfs storage  
| Possibility to mount nfs storage  
Line 94: Line 98:
| OCCI  
| OCCI  
| Open for discussion  
| Open for discussion  
| User/Pass (current) X509 (need consenus within Taskforce)  
| Username and Password (current) X509 (need consenus within Taskforce)  
| SSH Keys
| SSH Keys
|-
|-
| <div id='cloudsigma'>CloudSigma</div> (Micheal Higgins)  
| <div id="cloudsigma">CloudSigma</div> (Micheal Higgins)  
| Available since 24 October 2011  
| Available since 24 October 2011  
| 100Ghz CPU, 50GB RAM, 5TB Disk  
| 100Ghz CPU, 50GB RAM, 5TB Disk  
Line 108: Line 112:
| Web interface, API, Jclouds  
| Web interface, API, Jclouds  
| OCCI possible in future  
| OCCI possible in future  
| User/Password X.509 future  
| Username and Password X.509 future  
|  
|
|-
|-
| <div id='gwdg'>GWDG</div> (Philipp Wieder)  
| <div id="gwdg">GWDG</div> (Philipp Wieder)  
| Accessible October 23, 2011  
| Accessible October 23, 2011  
| As a start: 4 servers with Dual-Proc AMD Quad-Core "Barcelona", 2,4 GHz, 16 GB Ram, 250 GB HD. More beginning 2012  
| As a start: 4 servers with Dual-Proc AMD Quad-Core "Barcelona", 2,4 GHz, 16 GB Ram, 250 GB HD. More beginning 2012  
Line 120: Line 124:
| N/A  
| N/A  
| N/A  
| N/A  
|  
|
|  
|
|  
|
|  
|
|-
|-
| <div id='tcd'>Trinity College Dublin</div> (David O'Callaghan, Stuart Kenny)  
| <div id="tcd">Trinity College Dublin</div> (David O'Callaghan, Stuart Kenny)  
|  
|  
| 6 servers  
| 6 servers  
Line 134: Line 138:
| n/a  
| n/a  
| n/a  
| n/a  
|  
|
|  
|
|  
|
|  
|
|-
|-
| <div id='fz'>FZ Jülich</div> (B. Hagemeier)  
| <div id="fz">FZ Jülich</div> (B. Hagemeier)  
|  
|
| 1 Server (24 Cores, 24GB RAM, 1.5TB Disk)  
| 1 Server (24 Cores, 24GB RAM, 1.5TB Disk)  
| openStack "Diablo"
| OpenStack 'Diablo'
| To be defined  
| To be defined  
| n/a depends on solution above  
| n/a depends on solution above  
Line 148: Line 152:
| n/a  
| n/a  
| n/a  
| n/a  
|  
|
|  
|
|  
|
|  
|
|-
|-
| <div id='igi'>IGI</div> (Giancinto Donvito, Paolo Veronesi)  
| <div id="igi">IGI</div> (Giancinto Donvito, Paolo Veronesi)  
| work in progress  
| work in progress  
| 24 cores, 48 GB RAM, 2TB Disk  
| 24 cores, 48 GB RAM, 2TB Disk  
| [http://web.infn.it/wnodes/ WNoDeS]
| [http://web.infn.it/wnodes/ WNoDeS]  
| Shared NFS filesystem  
| Shared NFS filesystem  
| Usage of the SoftwareRunTimeEnvironment attribute for publishing VM information by using BDII (work in progress)  
| Usage of the Software&shy;Run&shy;Time&shy;Environment attribute for publishing VM information by using BDII (work in progress)  
| Nagios  
| Nagios  
| accounting at batch system level(pbs)and integrated with DGAS Accounting System used for the Grid infrastructure in Italy  
| accounting at batch system level(pbs)and integrated with DGAS Accounting System used for the Grid infrastructure in Italy  
| notification based on Nagios for system administrator (not for end users)  
| notification based on Nagios for system administrator (not for end users)  
| [http://occi-wg.org/2010/12/15/occi-in-infn/ OCCI]&nbsp;&amp; [http://www.eu-emi.eu/products/-/asset_publisher/z2MT/content/cream-1 CREAM]  
| [http://occi-wg.org/2010/12/15/occi-in-infn/ OCCI] [http://www.eu-emi.eu/products/-/asset_publisher/z2MT/content/cream-1 CREAM]  
| Web Portal (authentication based on X509) expected in the next 2 months. Federated Single Sign-On Authentication Service (based on Shibboleth) should be supported in the next 4/6 months.  
| Web Portal (authentication based on X509) expected in the next 2 months. Federated Single Sign-On Au&shy;then&shy;ti&shy;ca&shy;tion Service (based on Shibboleth) should be supported in the next 4/6 months.  
| GSI (Grid Security Infrastructure based on X509 personal certificates and VO membership based on VOMS)  
| GSI (Grid Security Infrastructure based on X509 personal certificates and VO membership based on VOMS)  
| SSH keys for root access
| SSH keys for root access
|- style="background:red;"
|- style="background:red;"
| <div id='in2p3'>IN2P3</div> (Helene Cordie, Gille Mathieu)
| <div id="in2p3">IN2P3</div> (Helene Cordie, Gille Mathieu)  
|  
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|- style="background:red;"
|- style="background:red;"
| <div id='cesga'>CESGA (IBERgrid) </div> (Ivan Diaz, Esteban Freire)
| <div id="cesga">CESGA (IBERgrid) </div> (Ivan Diaz, Esteban Freire)  
|  
|
|  
|
|  
|
|  
|
|  
|
|  
|
|  
|
|  
|
|  
|
|  
|
|  
|
|  
|
|}
|}


= Technology Provider inventory  =


Likewise, an inventory survey for Technology Providers to fill in below:
== Technology Provider inventory ==
 
The Technology Providers of the Task Force offer support for the technologies that they develop and evaluate further development in accordance with the federation roadmap.


For the description of the Capabilities please refer to the Cloud Integration Profile document available at [https://documents.egi.eu/document/435 https://documents.egi.eu/document/435]  
For the description of the Capabilities please refer to the [https://documents.egi.eu/document/435 Cloud Integration Profile document].


To indicate the type of information we are after, a sample hypothetical Resource Centre is provided for guidanc. Note that wherever suitable and possible, make not of any standards that yo know are implemented by the software you deployed for Cloud infrastructure management.  
Please note: wherever suitable and possible, any standards implemented by the adopted cloud software should be noted.


<br>


{| cellspacing="1" cellpadding="1" border="1"
{| border="1" cellspacing="1" cellpadding="1"
|-
|- style="background-color: lightgray;"
! scope="col" | Technology Provider  
! rowspan="2" | Provider
! scope="col" | Capability:<br>VM Management  
! colspan="6" | Capabilities
! scope="col" | Capability:<br>Data  
|- style="background-color: lightgray;"
! scope="col" | Capability:<br>Information  
! VM Management  
! scope="col" | Capability:<br>Monitoring  
! Data  
! scope="col" | Capability:<br>Accounting  
! Information  
! scope="col" | Capability:<br>Notification
! Monitoring  
! Accounting  
! Notification
|-
|-
| StratusLab (Cal Loomis)  
| StratusLab (Cal Loomis)  
| OpenNebula using XML-RPC interface (eventually OCCI); standard OpenNebula VM description for files (eventually OVF); authentication options are username/password, grid certificates and VOMS proxies, others methods should be easy to add  
| OpenNebula using XML-RPC interface (eventually OCCI); standard OpenNebula VM description for files (eventually OVF); authentication options are username and password, grid certificates and VOMS proxies, others methods should be easy to add  
| Proprietary Persistent Disk Store with RESTful interface (eventually also CDMI)  
| Proprietary Persistent Disk Store with RESTful interface (eventually also CDMI)  
| Planned in architecture, not implemented  
| Planned in architecture, not implemented  
Line 231: Line 237:
EGI-JRA1 offers NAGIOS probes integration Capability - No NAGIOS probes development is foreseen within JRA1 (with the exception of very few cases) - Technology Providers are expected to produce NAGIOS probes for their own systems.  
EGI-JRA1 offers NAGIOS probes integration Capability - No NAGIOS probes development is foreseen within JRA1 (with the exception of very few cases) - Technology Providers are expected to produce NAGIOS probes for their own systems.  


Availability/Reliability calculation and reporting for sites and services are currently produced outside EGI-JRA1.  
Availability and Reliability calculation and reporting for sites and services are currently produced outside EGI-JRA1.  


No information discovery systems are developed within JRA1.  
No information discovery systems are developed within JRA1.  
Line 239: Line 245:
|-
|-
| WNoDeS (Davide Salomoni, Elisabetta Ronchieri)  
| WNoDeS (Davide Salomoni, Elisabetta Ronchieri)  
|
| WNoDeS, with [http://occi-wg.org/2010/12/15/occi-in-infn/ OCCI] interface
WNoDeS, with OCCI interface (http://occi-wg.org/2010/12/15/occi-in-infn/).
| Posix I/O planned on Lustre, NFS and GPFS as persistent storage
| Usage of the Software&shy;Run&shy;Time&shy;Environment attribute for publishing VM information by using BDII
| Internal monitoring system for hypervisors. Not yet integrated with NAGIOS probes
| Accounting at batch system level (like lsf and pbs) and integration with the DGAS Accounting System used by the Italian Grid infrastructure
|
|
Posix I/O planned on Lustre, NFS and GPFS as persistent storage.
Usage of the SoftwareRunTimeEnvironment attribute for publishing VM information by using BDII.
|
Internal monitoring system for hypervisors. Not yet integrated with NAGIOS probes.
|
Accounting at batch system level (like lsf and pbs) and integration with the DGAS Accounting System used by the Italian Grid infrastructure.
|
|}
|}

Revision as of 10:21, 13 November 2011

Main Roadmap and Innovation Technology For Users For Resource Providers Media




Resource Providers inventory

The Resource Providers that have joined the Task Force make available a small portion of their cloud infrastructure in order to design and test the technologies described in the blueprint document for clouds federation. These resources are available for testing to every user community interested in testing/using them.

For the description of the Capabilities please refer to the Cloud Integration Profile document.

Please note: wherever suitable and possible, any standards implemented by the adopted cloud software should be noted.


Provider Status capacity Capabilities Management Interface Authentication
VM Management Data Information Monitoring Accounting Notification Supported Planned Service layer VMs
CESNET
(Miroslav Ruda)
Several servers quickly, more (~10) can be added later this year OpenNebula 3.0, to increase heterogeneity we could add Eucalyptus 2.0 or Nimbus + Cumulus interface too Shared NFS filesystem, GridFTP remote access, can provide S3 Cumulus implementation too N/A? OpenNebula web interface? Nagios infrastructure is ready, custom probes from other groups can be added quickly. Ganglia / Munin can be added on request. N/A? If reporter for standard usage records is implemented, can be deployed. N/A? STOMP based EGI messaging infrastructure in available on the site OCCI and partial EC2 provided by OpenNebula Open for discussion X509 certificates preferred, username and password as temporary solution may be possible In general up to user, plan to support registered user SSH keys for root access
OeRC (UK NGI)
(David Wallom, Matteo Turilli)
10 servers, between 8 and 2 VMs each Currently open Eucalyptus 2.0, moving to OpenStack, both as supplied by Canonical Ubuntu Enterprise Cloud Data supplied through S3/EBS capable storage services N/A NAGIOS based Developed service utilising extended OGF UR schema N/A Partial EC2 as implemented by OpenStack OCCI when available Username and password as implemented by OpenStack As chosen by the users
Cyfronet
(Tomasz Szepieniec, Marcin Radecki)
for initial setup 12 servers ready, extensions depending on usage Most likely OpenNebula 3.0 Possibility for mounting iSCSI devices in VMs, others to be defined Web interface integrated with PL-Grid User Portal Nagios integration, experimenting with zabbix Planned for early 2012 integration with PL-Grid Accounting using OpenNebula 3 accounting components N/A
SARA
(Floris Sluiter, Maurice Bouwhuis)
KTH
(Zeeshan Ali Shah)
Accessible since January, 2011 Initially 2 Servers with Total 4 cores, 16 GB RAM and 1TB storage OpenNebula Possibility to mount nfs storage OpenNebula Web interface with OCCI and OCA api Ganglia (need to experiment) N/A N/A OCCI Open for discussion Username and Password (current) X509 (need consenus within Taskforce) SSH Keys
CloudSigma
(Micheal Higgins)
Available since 24 October 2011 100Ghz CPU, 50GB RAM, 5TB Disk Web Console, Our API and Jclouds Mountable disks, Mountable S3 (future), SSD drives (future), NFS KVM Any user supplied monitoring Accounting in 5 minute intervals, downloadable in CSV Web interface, API, Jclouds OCCI possible in future Username and Password X.509 future
GWDG
(Philipp Wieder)
Accessible October 23, 2011 As a start: 4 servers with Dual-Proc AMD Quad-Core "Barcelona", 2,4 GHz, 16 GB Ram, 250 GB HD. More beginning 2012 OpenNebula 3.0 with OCCI server tbd OpenNebula Web interface with OCCI tbd (most likely Nagios) N/A N/A
Trinity College Dublin
(David O'Callaghan, Stuart Kenny)
6 servers StratusLab, OpenNebula Shared NFS filesystem n/a Nagios n/a n/a
FZ Jülich
(B. Hagemeier)
1 Server (24 Cores, 24GB RAM, 1.5TB Disk) OpenStack 'Diablo' To be defined n/a depends on solution above Nagios n/a n/a
IGI
(Giancinto Donvito, Paolo Veronesi)
work in progress 24 cores, 48 GB RAM, 2TB Disk WNoDeS Shared NFS filesystem Usage of the Software­Run­Time­Environment attribute for publishing VM information by using BDII (work in progress) Nagios accounting at batch system level(pbs)and integrated with DGAS Accounting System used for the Grid infrastructure in Italy notification based on Nagios for system administrator (not for end users) OCCI CREAM Web Portal (authentication based on X509) expected in the next 2 months. Federated Single Sign-On Au­then­ti­ca­tion Service (based on Shibboleth) should be supported in the next 4/6 months. GSI (Grid Security Infrastructure based on X509 personal certificates and VO membership based on VOMS) SSH keys for root access
IN2P3
(Helene Cordie, Gille Mathieu)
CESGA (IBERgrid)
(Ivan Diaz, Esteban Freire)


Technology Provider inventory

The Technology Providers of the Task Force offer support for the technologies that they develop and evaluate further development in accordance with the federation roadmap.

For the description of the Capabilities please refer to the Cloud Integration Profile document.

Please note: wherever suitable and possible, any standards implemented by the adopted cloud software should be noted.


Provider Capabilities
VM Management Data Information Monitoring Accounting Notification
StratusLab (Cal Loomis) OpenNebula using XML-RPC interface (eventually OCCI); standard OpenNebula VM description for files (eventually OVF); authentication options are username and password, grid certificates and VOMS proxies, others methods should be easy to add Proprietary Persistent Disk Store with RESTful interface (eventually also CDMI) Planned in architecture, not implemented Planned in architecture, not implemented Some functionality in OpenNebula, implementation for all StratusLab services planned but not yet implemented Prototype implementation in place, allows notification through AMQP if users provide messaging coordinates when starting a virtual machine
EGI-InSPIRE JRA1 (Daniele Cesini) None None None

EGI-JRA1 offers NAGIOS probes integration Capability - No NAGIOS probes development is foreseen within JRA1 (with the exception of very few cases) - Technology Providers are expected to produce NAGIOS probes for their own systems.

Availability and Reliability calculation and reporting for sites and services are currently produced outside EGI-JRA1.

No information discovery systems are developed within JRA1.

EGI-JRA1 contains a task (TJRA1.4) responsible for the development of an accounting system capable of encompassing the new resource types that will appear in the EGI infrastructure including virtualised resources. See the EGI DoW for TJRA1.4 details. None
WNoDeS (Davide Salomoni, Elisabetta Ronchieri) WNoDeS, with OCCI interface Posix I/O planned on Lustre, NFS and GPFS as persistent storage Usage of the Software­Run­Time­Environment attribute for publishing VM information by using BDII Internal monitoring system for hypervisors. Not yet integrated with NAGIOS probes Accounting at batch system level (like lsf and pbs) and integration with the DGAS Accounting System used by the Italian Grid infrastructure