wp5 – flagship deployment

WP5 – Flagship Deployment

Period 1 ReviewPhil Evans – Logica/CGI

1

WP5 ObjectivesPorting of the flagships to the cloud infrastructure provisioned by WP4. Evaluate and iteratively refine the deployment environment based on the need to improve the capabilities of each flagship.

Specific goalsTo initially deploy the three flagship applications on the cloud infrastructure, at a limited scale, in such a way that the flagships can be used by their intended user communities;To assess the success of the deployments in terms of key evaluation criteria to be defined by each flagship;To move to a full scale deployment based on the results of the initial deployments and any necessary refinements of the application or deployment environments.

2

Effort ContributionLead Beneficiary: Logica Germany

WP523%

Person-Months per Participant

Participant Person-months

CERN 15.00

EMBL 15.00

Logica Germany

10.00

CNR 5.00

CSA EMEA 1.00

TOTAL 46.00

PM24PM7

WP5

3

Deliverables and MilestonesPeriod 1

Type Del. no

Name Nature Dissemination level

Date Delivered

Deliverable 5.1 Evaluation of initial flagship Deployments Report PU 19/06/20123

Milestone 11 Documented Criteria and Metrics against which the deployment will be evaluated

Report PU 02/04/2013

4

Scientific/technical achievementsand their impact

Completed:Initial Proof of Concept Deployments (H1, 2012) successfully completed and documented in D5.1Agreed Success Criteria & Metrics (MS11)

On-Going:Pilot Phase deployments on preliminary Blue Box environments (WP4)Task 5.5: Deployment Security Management

5

MS11: Success Criteria & Metrics

Agreed with both demand/supply-sideCriteria:

Time to First InstanceTime to port image, gain network connectivity, first instance of flagship application running

ScalingAbility to scale to desired levels, time taken to scale first instance/full-scale, number of failed node deployments

PerformancePerformance of application on suppliers’ infrastructure, network performance.

CostActual cost against projected cost, cost per “job”

SupportSuitability of support provision within the federated environment

Flagship Organisation SpecificSLA/T&Cs analysis against the set of points outlined by the QMUL Cloud Legal Project in their recent paper "Negotiating Cloud Contracts: Looking at Clouds from Both Sides Now".

6

Initial Deployments Evaluation

Completed H1, 2012Documented in D5.11-1 Deployments; No federationIdentified key areas to address before future deploymentsShaped the environments currently being used for the Pilot phase deployments.

7

Pilot Phase Deployments

Evolved Environments, 1 Commercial Blue Box, 1 Open-Source Blue BoxEvolved Supplier Infrastructure

Began late MarchDeployment planning many months before deployments beganWeekly, and in some cases, daily progress and coordination callsDelays due to factors external to the FP7 project.

8

Evolving deployment schedulefor second round of deployments

9

Overall modifications, corrective actions, re-tuning of objectives

Task 5.5: Deployment Security Management extended to cover the CSA’s Cloud Security Alliance Security, Trust and Assurance Registry (STAR) Increased effort for flagship deployment coordination due to increased complexities

Two Blue-Box DeploymentsDelays due to technical issues

10

Security Assessment & Challenge

Logica + Cloud Security AllianceFocuses on the Federated/Blue Box aspects of the pilotKey Areas:

Federated Cloud ManagementKey ManagementAvailabilityInteroperabilityAsset ManagementIncident ManagementLightweight Penetration Test

Currently underway & results GA3 - Heidelberg Decision to publish on STAR subject to agreement with all suppliers.

11

Exploitation and use of foreground

D5.1: Initial Flagship Evaluation (H1, 2012) MS11: Success

Criteria & Metrics

D4.3 Cloud Provisioning Report

Pilot Deployment Environments

(2013)

Deployment Evaluation

Task 5.5: Operational Policy

Definitions

Task 5.6: Technical Requirements for

Future Procurement

MS11: Success Criteria & Metrics

12

Collaboration with other beneficiaries

Demand-Side & Supply-Side Input to D5.1 & MS11

EMBL, CERN (+ ESA)Weekly Deployment Call

CERN, EMBL, T-Systems, Atos, CloudSigma and other Helix Nebula initiative membersESA

Daily calls to mitigate problems with specific flagships

13

Interaction with other FP7 projectsand stakeholders outside the consortium

SixSq (SME): SlipStream : CELAR/StratusLabSlipStream open-sourced under CELAR, key point in adoption for some suppliers.

Interoute : Cloud Service ProviderESA – Flagship Application providerThe Server Labs (SME): Service/Deployment Support

14

Summary

Proof of Concept deployments successfully completed, evaluated against MS11 criteria and documented in D5.1Pilot phase deployments underway via the two Blue Box deploymentsPilot deployments to be evaluated & presented at GA3 Security challenge to complete with results at GA3.Future Flagships…

15