WP5 – Infrastructure Operations Test and Production Infrastructures StratusLab kick-off meeting June 2010, Orsay, France GRNET

2 Activity objectives To setup and operate the StratusLab computing infrastructure. This infrastructure will deploy the software developed in the context of the project and will be used for the following purposes: To serve as a testbed for the StratusLab software To offer to end-user communities and collaborating projects access to the resources and research results developed by StratusLab To provide support for the creation of the virtual appliances for different user communities, and to investigate the feasibility of offering a repository of reference images

3 WP5 at a glance Start month: M1 End month: M24

4 Activity breakdown Task Deployment and Operation of Virtualized Grid Sites (M1-M24). Infrastructure setup. Allocation of hardware resources. Deployment and administration. Operation of certified grid sites. Support to external entities. Task 5.2 – Testing of the StratusLab toolkit (M4 – M24). Pre- production infrastructure. Testing of new releases. Bug reporting. Interaction with WP4 (StratusLab distribution) and WP2 (Applications, Use Cases and scenarios). Task 5.3: Virtual Appliances Creation and Maintenance (M4-M24). Setup and maintenance of a repository of pre-configured virtual machine appliances targeting both system administrators and end users. Define procedures for image creation and certification.

5 Resource allocation Need to make initial partner commitment of the offered resources GRNET: –Newly installed data center. –Allocated 28 physical nodes for the purposes of StratusLab –448 cores effective total (dual quad-core = 8 cores per node x 2 threads per core) –1.3 TB RAM (48 GB per node) –40 TB of storage Need to consider cloud implications on the hardware –VT Extensions (pre-requisite for kvm) –Storage and interconnectivity –Physical monitoring and administration

6 First deliverable: D5.1 Infrastructure Specification Due for month M3. Detailed specification of computing resources committed for the project per partner Internal usage policy Current requirements to cover Future projection. Infrastructure requirements for the coming months.

7 Infrastructure management tools Three layers –Physical – Covered by various ventor tools –Cloud – Part of the cloud layer services. Various tools depending on hypervisor technology and cloud-access library –Grid – Work done in the context of EGEE and EGI Requirements for cross-layer integration? –E.g. In order to have unified look of cloud and grid nodes. Part of the DN5.2 deliverable due for month M6

8 Preliminary installations and tests WP5 strongly depends on WP4 and in some cases from WP2 Until a first release of the software is available we could focus on preparative tasks: –Setup and configuration of nodes. Installation of OS. Configuration of basic system –Preliminary installation of current release of OpenNebula. Setup and verification. –Experiment with different hypervisor options (kvn, xen, vmware). Identify issues and investigate workarounds. –Investigate available tools for VM monitoring and infrastructure operations support. –Start populating a knowledge base of cloud infrastructure operations issues and good practices

9 Resource requirements from other tasks Allocated hardware resources could cover requirements coming internally from other tasks Define allocations Identify requirements Allocation policy Management policy

10 Things to consider Many similar activities taking place during the past year Work at INFN with WN-on-demand BiG Grid. Virtualization of Worker Nodes Activities in DGrid - Univ. of Dortmund CERN large-scale VM installation based on OpenNebula SARA offering of HPC-cloud resources and services … thus Need to seek innovation. Differentiate from the mass. Value-added services.

11 Testing procedures Test workflow. Interaction with WP4 –Timeframe of releases –Bug reporting and overall feedback. –Installation instructions –Feedback Formal procedure Tools –Black box testing Applications and Benchmarking –Selection of benchmark applications –Stress testing –Different use cases and usage scenarios

12 Virtual Appliances repository Architecture –Important component of a cloud infrastructure –Placement and replication Procedures. –Image certification and verification. –Image signing –Security considerations (access control, authentication, authorization) Storage resources –Storage requirements. –File system and performance considerations Query and retrieval –Virtual Appliance metadata –Query interface. Web tools Programming interface –Management/Query/Access API. –RESTful services

13 Administrative issues Define task leaders Collaboration tools, mailing lists Periodic meetings/phone calls

14 AOB?