StratusLab is co-funded by the European Community’s Seventh Framework Programme (Capacities) Grant Agreement INFSO-RI Exploitation and Sustainability StratusLab Final Periodic Review Brussels, Belgium 10 July 2012

2 Introduction Exploitation and Sustainability Plan  First plan delivered June 2011 (D3.3)  Final plan delivered May 2012 (D3.5) Work Package 3, Task T3.3  Process and document managed by WP3  Contributions from all partners

3 The StratusLab Collaboration Existing partners committed to continued collaboration  Move to a community-driven development model  Contributor license to be drawn up to facilitate community contributions  Further funding secured for development of certain components Steps already taken:  Software repositories moved to GitHub  Project documents archived in open-access repositories  New website to form hub of StratusLab community

4 Academic Exploitation LAL, GRNET  Run public StratusLab clouds with common authentication IBCP  Runs a StratusLab cloud for the French Bioinformatics community TCD  Runs a StratusLab cloud for users within Trinity College

5 Commercial Exploitation DS-Cloud Ready Pack  Turnkey cloud solution based on StratusLab and SlipStream  In collaboration with Darest and IBM Certification on IBM PureFlex  StratusLab and SlipStream certification on IBM hardware  With support from IBM Helix Nebula and Atos  Consultancy for rollout of StratusLab for Helix Nebula Atos cloud ESOC/ESA  Rapid-deployment prototype demonstrated in collaboration with Terma  Plans to roll this out in production

6 Commercial Exploitation SlipStream  SlipStream support for StratusLab as cloud back-end  SixSq products based on SlipStream and StratusLab Telefónica I+D Cloud Initiative  Using Claudia and other components within the Telefónica group Advanced Service Management / Scalability prototype  Prototype demonstrating advanced StratusLab cloud features  As a basis for marketing and future products UCM & C12G  Consultancy for OpenNebula and StratusLab OpenNebula extensions

7 Services Documentation and Website  New website in development (on GitHub pages)  Old website to be archived Marketplace Service  TCD will continue to run the Marketplace  EGI also trialing their own Marketplace instance VM Images  LAL to maintain base images  Individual communities to maintain appliances –UMD maintained by EGI –Globus maintained by IGE –Bioinformatics maintained by IBCP

8 Services Reference Cloud Services  GRNET and LAL will continue to run public reference cloud services  Other partners currently running private cloud services Grid Site  GRNET will continue to run the Grid Site on top of StratusLab

9 Development and Software Marketplace  TCD will continue to develop and maintain Persistent Storage  SixSq using persistent storage in several commercial applications  Will continue to develop and maintain Network Manager  Will be maintained by UCM as part of OpenNebula Authentication Proxy  LAL will continue to develop and maintain Claudia  TID will use in future projects  Will continue to develop and maintain

10 Development and Software OpenNebula  UCM will continue to develop and maintain StratusLab OpenNebula Customisations  Many migrated to OpenNebula repository  Maintained and further developed by UCM  Others part of the community-developed OpenNebula Ecosystem Registration Application  LAL will continue to develop and maintain Quattor Installation  CNRS will continue to maintain  Migration into Quattor Working Group Hudson Cloud Adaptor for StratusLab  LAL will continue to maintain

11 Development and Software Manual Installation  Used by SixSq commercial offerings  SixSq will continue to develop and maintain Command-line clients  SixSq to lead development  All partners will continue to contribute to development Monitoring  To be maintained by TID as part of Claudia Accounting  To be maintained by UCM as part of OpenNebula Port Translation  IBCM will continue to develop and maintain

12 Summary Continued collaboration  In the context of a community-driven development model  All partners committed to further development  Community contributions to be encouraged Considerable exploitation  Partner exploitation within local and national infrastructures  Large number of commercial exploitations Software and Services  Commitment from partners to continued running of critical services  Clear plans for continued development of software

13 Questions?

Copyright © 2012, 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