StratusLab is co-funded by the European Community’s Seventh Framework Programme (Capacities) Grant Agreement INFSO-RI StratusLab: Overview & Collaboration Possibilities Inter-project Collaboration Meeting (Amsterdam) 11 May 2011

2 StratusLab Project Goal  Create comprehensive, open-source, IaaS cloud distribution  Focus on supporting grid services Information  1 June 2010—31 May 2012 (2 years)  6 partners from 5 countries  Budget : 3.3 M€ (2.3 M€ EC) Contacts  Site web:   Support: CNRS (FR)UCM (ES) GRNET (GR)SIXSQ (CH) TID (ES)TCD (IE)

3 Goal  Offer remote access to computing resources Advantages  Customized environments  Rapid access via simple API  Complete control (root access) with “pay as you go” model Disadvantages  Non-standard interfaces (vendor lock-in)  Creating new virtual machines is difficult Infrastructure as a Service (IaaS) Platform as a Service (PaaS) Software as a Service (SaaS)

4 Grid and Cloud Integration Grid Resource Center StratusLab Distribution Private/Public Cloud Cloud API and Service Manager API Grid Services Public Clouds users

5 Architecture of StratusLab v1.0 IaaS Cloud VM Manager (OpenNebula) XML-RPC  OCCI Physical Computing Resources Service Manager (Claudia) TCloud Storage Manager REST/CDMI iSCSI (?)KVM… Physical Storage Resources … Appliance Management StratusLab Marketplace HTTP(S) REST Interface Appliance Storage (Web, Grid, Cloud) users Physical Network Network Services

6 Virtual Machine Management OpenNebula improvements  More complete logging information  Quarantine of stopped images  Ability to pass error messages from plugins to user  Support for users, groups, and roles (post-1.0) PXE Booting  Useful for integration with automated machine mgt. (Quattor)  Useful for automating creation of base/user images Collaboration  StratusLab  OpenNebula  Others: general improvements  StratusLab  Others: Automated machine creation

7 Networking IP  Public/local/private IP addresses  IP address selection (useful for grid services)  IP reservation (post 1.0)  IPv6 use/validation (post 1.0) Dynamic configuration  VLANs (post 1.0)  User-specified firewalls (post 1.0) Collaboration  SARA, Mantichore  StratusLab: dynamic configuration  StratusLab  ?: IPv6  StratusLab  Others: IP reservation, address selection

8 Storage Persistent Disk Store  Prototype exists, production in v0.4  Based on iSCSI and LVM Caching/Latency Reduction  Investigating Ceph, LVM, Lustre, GPFS  Hierarchical (squid?) caches Interfaces  CDMI Collaboration  VENUS-C  StratusLab: CDMI proxy, integration with data mgt.  SARA, SNIA  StratusLab: CDMI reference/SARA implementation  StratusLab  Others: caching and latency reduction

9 Marketplace Appliance Repository (phasing out)  Essentially a webdav server with specific layout  Stores both metadata and image contents Marketplace (phasing in)  Registry of image metadata  Contents stored in cloud, grid, web, … Collaboration  StratusLab  HEPiX: Metadata definition, signing, validation  StratusLab  HEPiX: Interoperability of image catalogs, registries  StratusLab  HEPiX: Policy definition and enforcement

10 Appliances Base images  ttylinux, CentOS 5.5, Ubuntu 10.04, OpenSuSE (?) Grid appliances  CE, SE, WN, APEL/BDII, UI Bioinformatics appliances  Data server and analysis images Collaborations  StratusLab  EGI, EMI, EDGI, user communities: Collaboration on creating and testing of appliances

11 Authn/Authz Implementation  Authn proxy in front of ~all services  Uses Jetty implementation of JAAS  Supports User/Password files, LDAP, Grid certificates, VOMS proxies  Passes authentication information to back-end services  Delegation currently not needed/used *may change if images are protected) Collaborations  StratusLab  EMI: Feedback Jetty support, other changes  EMI  StratusLab: Better packaging, portable voms-proxy-init, delegation service

12 Service Manager (Claudia) Implementation  Provides service (ensemble of machines) management  Dynamic control based on monitoring feedback  Currently being integrated with other StratusLab services Collaborations  StratusLab  VENUS-C, Others: Possibly interesting component for building platforms, "canned" services  StratusLab  Others: OVF and TCloud implementations

13 Accounting Monitoring Implementation  Simple script to extract values from database  No publication of the information at the moment Collaborations  VENUS-C  StratusLab: Use/integration of accounting service  StratusLab  EGI: Integration with EGI accounting, types of resources for accounting

14 Conclusions StratusLab Release(s)  Nearly complete, functional beta available  Used to run production grid site over reference infrastructure  Complete beta (v0.4) ~16 May  Production release (v1.0) ~10 June Collaborations  Looking forward to collaborations with other projects  Software can be tested on reference infrastructure or installed  Want feedback (positive and negative) from user, admins, …

Copyright © 2011, Members of the StratusLab collaboration: Centre National de la Recherche Scientifique, Universidad Complutense de Madrid, Greek Research and Technology Network S.A., SixSq Sàrl, Telefónica Investigación y Desarrollo SA, and The Provost Fellows and Scholars of the College of the Holy and Undivided Trinity of Queen Elizabeth Near Dublin. This work is licensed under the Creative Commons Attribution 3.0 Unported License