Fedcloud-tf:Testbed

From EGIWiki
Revision as of 09:10, 15 November 2011 by Jouvin (talk | contribs)
Jump to: navigation, search
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
CESGA (IBERgrid)
(Ivan Diaz, Esteban Freire)
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
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
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
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
GRIF
(Michel Jouvin)
Production 10 servers (240 cores) StratusLab iSCSI-based permanent disks n/a n/a n/a n/a Private (StratusLab) OCCI X509 certificates preferred, username and password also possible User SSH keys for root access (configured when VM is launched)
GRNET (IBERgrid)
(Panos Louridas, Vangelis Floros)
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
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)
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
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
SARA
(Floris Sluiter, Maurice Bouwhuis)
Trinity College Dublin
(David O'Callaghan, Stuart Kenny)
6 servers StratusLab, OpenNebula Shared NFS filesystem n/a Nagios n/a n/a


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