1 / 15

WP5 – Flagship Deployment

WP5 – Flagship Deployment. Period 1 Review Phil Evans – Logica/CGI. WP5 Objectives. Porting 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.

zia
Download Presentation

WP5 – Flagship Deployment

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. WP5 – Flagship Deployment Period 1 Review Phil Evans – Logica/CGI

  2. WP5 Objectives Porting 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 goals • To 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.

  3. Effort Contribution • Lead Beneficiary: Logica Germany WP5

  4. Deliverables and MilestonesPeriod 1

  5. Scientific/technical achievementsand their impact • Completed: • Initial Proof of Concept Deployments (H1, 2012) successfully completed and documented in D5.1 • Agreed Success Criteria & Metrics (MS11) • On-Going: • Pilot Phase deployments on preliminary Blue Box environments (WP4) • Task 5.5: Deployment Security Management

  6. MS11: Success Criteria & Metrics • Agreed with both demand/supply-side • Criteria: • Time to First Instance • Time to port image, gain network connectivity, first instance of flagship application running • Scaling • Ability to scale to desired levels, time taken to scale first instance/full-scale, number of failed node deployments • Performance • Performance of application on suppliers’ infrastructure, network performance. • Cost • Actual cost against projected cost, cost per “job” • Support • Suitability of support provision within the federated environment • Flagship Organisation Specific • SLA/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".

  7. Initial Deployments Evaluation • Completed H1, 2012 • Documented in D5.1 • 1-1 Deployments; No federation • Identified key areas to address before future deployments • Shaped the environments currently being used for the Pilot phase deployments.

  8. Pilot Phase Deployments • Evolved Environments, • 1 Commercial Blue Box, 1 Open-Source Blue Box • Evolved Supplier Infrastructure • Began late March • Deployment planning many months before deployments began • Weekly, and in some cases, daily progress and coordination calls • Delays due to factors external to the FP7 project.

  9. Evolving deployment schedulefor second round of deployments

  10. 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 Deployments • Delays due to technical issues

  11. Security Assessment & Challenge • Logica + Cloud Security Alliance • Focuses on the Federated/Blue Box aspects of the pilot • Key Areas: • Federated Cloud Management • Key Management • Availability • Interoperability • Asset Management • Incident Management • Lightweight Penetration Test • Currently underway & results GA3 - Heidelberg • Decision to publish on STAR subject to agreement with all suppliers.

  12. 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) DeploymentEvaluation MS11: Success Criteria & Metrics Task 5.5: Operational Policy Definitions Task 5.6: Technical Requirements for Future Procurement

  13. 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 members • ESA • Daily calls to mitigate problems with specific flagships

  14. Interaction with other FP7 projectsand stakeholders outside the consortium • SixSq (SME): SlipStream : CELAR/StratusLab • SlipStream open-sourced under CELAR, key point in adoption for some suppliers. • Interoute : Cloud Service Provider • ESA – Flagship Application provider • The Server Labs (SME): Service/Deployment Support

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

More Related