Your SlideShare is downloading. ×
Towards Hybrid Strategies - 451 Research & Atos
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Towards Hybrid Strategies - 451 Research & Atos

207

Published on

Published in: Technology, Business
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
207
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
14
Comments
0
Likes
1
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide
  • Cloud adoption is increasing at a healthy rate and usage trends point to mainstream acceptance. The cloud model is transitioning from a largely experimental, specific-use-case computing alternative (phase 1) to a more mainstream IT strategy being embraced by enterprises and government agencies (phase 2). While we are seeing an increase in demand for ‘phase 2’ offerings (cloud management) there continues to be a great deal of activity on the opposite side of the cloud spectrum. New IaaS offerings being launched by hosting companies, managed service providers and telcos. This investment at the low end of the spectrum for on-demand infrastructure demonstrates a continued high-level demand for ‘phase 1’ offerings.Increased number of vendors are marketing their cloud offerings specifically for enterprises. We saw private cloud move to the foreground through 2011, increasingly, it will be hybrid strategies that define the supply side agenda as organizations seek to make the best use of existing resources and domain skills.
  • The majority of enterprises are currently focused on building out their internal private cloud infrastructure. However, what most define as an internal private cloud is largely just virtualization. Attributes like cost transparency, automated hybrid provisioning and self-service, have largely not been implemented.
  • Internal Cloud: 42% of end users interviewed said they are struggling with management. Internal resistance related to fear, uncertainty and doubt are also impacting the uptake of internal private clouds.External Cloud: Security and internal resistance are both leading inhibitors of public cloud adoption. Security was cited by 69% of respondents as a pain point. Security concerns typically revolve around data privacy and location.
  • There were a lot of cloud users who got hurt when Amazon went down on April 21. Following this, on August 7, a lightning strike caused power outages at the major cloud computing data hubs for Amazon and Microsoft in Dublin. On February 29 this year Microsoft’s Windows Azure cloud service was hit with performance problems, leaving customers unable to manage their applications for about 8 hours and knocking Azure-based services offline for some users.
  • As a consequence, a multi-cloud world becomes more inevitable as companies seek to insure themselves against failure. End users seeking ways to automate the delivery of workloads and apps to the most suitable execution environments (be it external/internal) – BEV, whether that is determined by performance, compliance or some other SLA or policy requirement.
  • Ana Juan Ferrer head of Service Engineering & IT platforms at Research and Innovation at AtosOPTIMIS project co-funded by the EU, a collaborative project Atos Coordinates, with participation of universities and research institutions together with Tech industries: SAP and BT.
  • Atos is European IT Services company, delivering hi-tech transactional services, consulting, systems integration and managed services.We are the tech partner of the Olympics.
  • OPTIMIS vision is in the future Cloud Services won’t be provided neither completely in house nor completely externalized, but in a hybrid model realized by private clouds interacting with a wide ecosystem of external cloud providers.In order to make reality this vision, weidentify needs to be addressed in the complete Cloud Service life-cycle. Providing optimized tools for: -Service Construction,Cloud DeploymentCloud Operation Taking into account in all these phases self-management based on Trust, Risk, Eco-efficiency and Cost parameters, what we call the TREC parameters, as well as legal constraints.Optimis is a software toolkit that service providers deploy in the data center. It is a complement to cloud management, orchestration and application lifecycle management platforms. It gives service providers the capability to easily orchestrate cloud services customized for the unique needs of their applications and make intelligent deployment decisions based on their preference regarding trust, risk, eco-efficiency and cost (TREC). It gives them the choice of developing once and deploying services across all types of cloud environments – private, hybrid, federated or multi-clouds. 
  • Ourvision is centered on the following innovations:Construction:Simplified construction of services, enabling developers to determine service needs for TREC parameters. Deployment based on Dependable Sociability = Trust + Risk + Eco + Cost:The combination of these parameters capture the essence of the optimized cloud ecosystem, generated by the mutual trust between consumers and providers in a secure environment and the risk of not accomplishing specific ecological or economical goals. ConsideringMulti-Cloud Architectures and on Federated Cloud Providers enabling novel and complex composition of clouds multiple providers in a transparent fashion.Internal Cloud operation: Adaptive and Eco-Aware Self-Preservation for automated, dynamic and pro-active management of cloud infrastructures. Support self-evaluation and –management based on Trust, Risk, Eco-efficiency and Costholistic approach, not isolated measuresCover both provider and consumer aspects (e.g., elasticity–admission control interplay).4.External Cloud Operation:License Management for external cloud executionVM Security + Federation SecurityData Management between Clouds (legal constraints)In all these phases we take into account both legal and regulatory aspects, considering both data protection and privacy, as well as green legislation
  • What do we mean byhybridClouds?In optimisweconsiderthefloowingscenarios:Privatecloudexecution, thatduetocertaincircumstances decides tomovepart of the load to a cloud,WhatwecallfederatedClouds, a IaaS interactingwithmultiple IaaS CloudsMultiCloud SP withmultipleIpsthat can be considered a ServiceProvideroreven a Broker
  • As previously stated in Optimes we consider two main roles:A service provider: an organisation that has an application or service to be executed in a Cloud. We consider both the model where it has its own infrastructure or not. An infastructure provider which represents a tipical IaaS providers.Of the scenarios I have previously detailed 2 of them decision for this scenario is taken at Deployment type Private Cloud and Multi-Cloud while for Cloud Bursting or Federation it is taken at operation phase.
  • The Toolkit is main Optimis Results. It has three types of tools:Tools for DevelopersFor Service providersAnd For infastructure providersTools for Developers, consist on a programming model implemented in Java where paralelsm among diverse code pieces can be expressed by means of annotations, and an IDE. Tools for Service providersThat enables the owner of an application, developed with the programming model, or just as set of VMs to select the best deployment option based on trec parameters as well as to get information of service performance and configuration during operation. Tools for IaaS providers add a management layer on top of known VM Managers such as Open Nebula or Eucalyptus. It adds capabilities control acceptance of new workload, to manage SLA as well as to control automated Elasticity of applications and FaultTolerance.
  • TREC parameters influence the whole system. First because users express their requirements to deploy a service based on their combination. Trust level is the degree in which a provider fulfuls SLA and represents reputationRisk is the risk of failure a provider offersEco it’s the eco-efficiency of the provider. And Cost is ClearAlso although these are separated parameters there is a clear correlation among them. Trust influences level of risk an user is ready to assume by selecting a providersWhile the less ecologically efficient a provider is, in principle, the upper costs it has, as energy is a very important cost factor in the data center.
  • As I have mentioned in the Toolkit overview we have several components at Infrastructure Provider level that can take decisions in kind of autonomic manner. In order to control their behaviour there are configured to optimize based on policies derived from Provider’s Business level objectives.
  • Based on the Business Level Objectives, its derived policies and Service requirements for TREC components optimize different aspects:Selection of provider or set of providers for a service at Service Management LevelOptimum allocation of VMs into physical nodes, placement and probability of SLA violation for IaaS providers
  • We will now go deeper in the all the deployment scenarios
  • IN a private Cloud scenario, and in fact for all scenarios the starting point is an application that in the case it is developed with the OPTIMIS tools we offer Automatization tools so VMs are generated to run this software and software pre-requisites and contextualisation is done. For the rest of applications the entry point is a set of VMs and what we call a Service Manifest. An XML format that includes an DMTF OVF descriptor, that includes also TREC User requirements as well as legal constraints i.e. the country or the set of countries that can host a given application. At level of deployment this scenario is the simpliest as there is not optimization.
  • At the level of a multi-cloud the selection is done based on TREC and for Broker scenarios we also consider the possibility of executing an application among mulpiple providers and the Broker orchestrating their execution.
  • In Bursting and Federation, we consider that the service is executing in a given IaaS provider and because of the need of adding a new VM to scale the service, or to resolve a potential failure or because a pro-active action taken by TREC the IaaS runs out of capacity and needs to move part the application, i.e. a VM, to another provider. The controler the the IaaS level then takes the same role that had in the deployment to select the appropiated provider to burst to.
  • If it involves more than one provider, and they share resources and the service is an aggregation of two providers offerings we are in a Federation scenario.
  • So, here I have presented you the architectural vision of OPTIMIS. What are our next steps?First to publish and make available trough our website the first version of these components.And at the level of new features we aim to work in supporting different levels of interoperability with Public Cloud providers. As you can see in my presentation all IaaS providers have been represented as OPTIMIS IaaS providers, which is not realistic at all. For the future we would like two suport two levels of interoperability:With providers that are non. Optimis and have their own enviroments.And with only the partial adoption of part of the toolkit by a providers IaaS component are able for i.e. to be able to sit on top of multiple VM Managers
  • OF course standards are basic for both tasks and for it SIENA initiative is a reference pointEU-funded SIENA initiative focuses on Cloudinteroperability and standards challengesacts through liaison and collaborationwith the diversity of stakeholders: industrypublic sectorresearchersstandards developmentinteroperability through standards is a long-term solution (and challenge!)short and mid-term solutions exist today through adapters and point-to-point interfaces, but are difficult to sustain
  • Transcript

    • 1. Towards Hybrid Strategies Csilla Zsigri – Director of Consulting Services EMEA, 451 Research csilla.zsigri@451research.com
    • 2.  A division of The 451 Group  Unique combination of research,      analysis & data Published syndicated research on emerging markets Daily qualitative & quantitative insight Analyst advisory & professional services Go-to-market support Global events
    • 3. Cloud Market Evolution
    • 4. Phase in Journey to the Cloud Source: The 451 Group Cloud End User Survey 1H 2012
    • 5. Top Cloud-related Projects Source: The 451 Group Cloud End User Survey 1H 2012
    • 6. Pain Points Source: The 451 Group Cloud End User Survey 1H 2012
    • 7. What happened on 21 April 2011?  April 21, 2011: Amazon went down  August 7, 2011: Outage in Dublin knocks Amazon and Microsoft data centers offline  February 29, 2012: Azure customers unable to manage their applications for about 8 hours
    • 8. Multi-Cloud Strategies and ‘Best Execution Venues’  Multi-clouds become more inevitable as companies seek to insure themselves against failure  Increased requirement for BEV capability determined by performance, compliance or some other SLA and policy requirement
    • 9. Cloud orchestration, a key requirement here… • Marries the disciplines of automated self-service resource provisioning, on-boarding and management with process, policy, governance and security • Hybrid cloud model won’t work unless the entities and functions in a system can be dynamically orchestrated • Users seek full lifecycle experiences and want to automate the delivery of workloads to the most suitable clouds (internal/external) • Provides a ‘missing link’ between the enterprise and cloud • Growing number of suppliers converging on this opportunity • Taking existing applications and moving them to the cloud is an inevitable requirement for hybrid clouds…
    • 10. Towards Hybrid? Enterprises as Service Providers? • Enterprises seeking to deliver IT as a service to their own organizations using a combination of on-premises and hosted resources • IT departments as cloud service providers/brokers • Service provider offerings should be based on: • Simplicity (portals, orchestration) • Transparency (management tools, diagnostic capabilities) • Trust (service level agreements, reliability) • Security (transparency into process and policies) • End users want mobility. Locking in end users is not a viable longterm strategy…
    • 11. Ana Juan - Head of Service Engineering & IT Platforms Lab, AtoS
    • 12. 22/01/2014 Introducing Atos Corporate Communications Atos is an international information technology services company, delivering hi-tech transactional services, consulting, systems integration and managed services. Atos is focused on business technology that powers progress and helps organizations to create their firm of the future. It is the Worldwide Information Technology Partner for the Olympic Games ▶ Annual revenues of € 8,5 billion (proforma 2011) ▶ Almost 74,000 business technologists worldwide in more 42 countries ▶ Worldwide headquarters in Bezons / Paris, France 12
    • 13. OPTIMIS addresses the scenario of 2013+ where most companies use private and public clouds in combination (hybrid clouds) OPTIMIS aims at optimizing IaaS cloud services by producing an architectural framework and a development toolkit that takes Trust, Risk, Eco-efficiency, Cost (TREC) and legal issues into account The optimization covers the full cloud service lifecycle *
    • 14. ‐ Construction ‐ ‐ Construction: new, legacy, licensed sw. Services Composition Automated Parallelism Operation Public Cloud Operation ‐ ‐ ‐ Deployment Private Cloud operation SW License Management VM Security + Federation Security Data Management between Clouds (legal constraints) ‐ ‐ ‐ ‐ Support self-evaluation and – management based on TREC Holistic, not isolated measures Both provider and consumer aspects (e.g., elasticity– admission control interplay) ‐ ‐ Avoid ad-hoc & manual processes throughout cloud service lifecycle Trust + Risk + Eco + Cost for selecting “best “ deployment option Multiple deployment scenarios
    • 15. Bursted internal clouds * Service Provider Public Cloud Infrastructure Provider Service Provider Infrastructure Provider Infrastructure Provider Service Provider Broker Multiclouds Infrastructure Provider Infrastructure Provider Infrastructure Provider Infrastructure Provider Federated clouds Infrastructure Provider
    • 16. DEPLOYMENT Private Cloud Multi Cloud OPERATION Cloud Bursting Federated Cloud
    • 17. Deployment Tools Construction Tools COMPs PM IDE Image Creation Service VM Contextualize r Service Deployer Operation Tools License Manager Service Manager Deployment Optimizer Developers Monitoring Service Providers TREC Trust Deployment Tools Admission Control Cloud Optimizer SLA Manager IaaS Providers Risk Eco Cost Operation Tools Data Manager Elasticity Engine VM Manager Fault Tolerance Engine
    • 18. Trust Risk * Eco Cost
    • 19. Business Level Objectives Management constraints High-level management Policy tuning Monitor Monitor Algorithms Policies Admission Control Algorithms Policies Elasticity Engine Algorithms Policies VM Manager Algorithms Policies Data Management Algorithms Policies Fault Tolerance Engine
    • 20. * Deployment Tools Construction Tools COMPs PM IDE Automation Tools License Manager Service Deployment Optimizer Service Acceptance Criteria Deployment Tools Admission Control Service Manager VM & Data Security Developers Best execution Cloud Service Providers venue Optimum deployment Operation Tools Cloud Optimizer SLA Management Cloud IaaS Providers Monitoring TREC Trust Risk Eco Cost Operation Tools Data Manager Elasticity Engine VM Manager Fault Tolerance Engine Optimum placement SLA violation risk
    • 21. DEPLOYMENT Private Cloud Multi Cloud OPERATION Cloud Bursting Federated Cloud
    • 22. * Construction Tools Components COMPs PM IDE  Service Manifest Deployment Tools VMs VM repository Automation Tools Data Management Service Deployment Optimizer TREC Trust Risk Eco Cost Cloud Service Provider Deployment Tools TREC Trust Risk Eco Cost Cloud IaaS Provider Admission Control Cloud Optimizer SLA Management Operation Tools Data Manager Elasticity Engine VM Manager Fault Tolerance Engine Operation Tools Service Manager
    • 23. DEPLOYMENT Private Cloud Multi Cloud OPERATION Cloud Bursting Federated Cloud
    • 24. * Construction Tools Components COMPs PM IDE  Service Manifest Deployment Tools VMs Automation Tools VM repository Data Management Cloud Service Provider Service Deployment Optimizer TREC Trust Risk Eco Cost Operation Tools Service Manager
    • 25. DEPLOYMENT Private Cloud Multi Cloud OPERATION Cloud Bursting Federated Cloud
    • 26. * Construction Tools COMPs PM IDE Deployment Tools VMs Automation Tools VM repository Data Management Cloud Service Provider Service Deployment Optimizer TREC Trust Risk Eco Cost Operation Tools Service Manager
    • 27. DEPLOYMENT Private Cloud Multi Cloud OPERATION Cloud Bursting Federated Cloud
    • 28. * Construction Tools Components COMPs PM IDE  Service Manifest Deployment Tools VMs Automation Tools VM repository Data Management Cloud Service Provider Service Deployment Optimizer TREC Trust Risk Eco Cost Operation Tools Service Manager
    • 29. * First version of the OPTIMIS toolkit will be released in June. * Different levels of Interoperability with public Cloud providers: * Non-Optimis – Adaptors system to different infrastructures. Lack of standards, potential solution based on delta Cloud. * Optimis Enhanced providers: Partial adoption of Optimis toolkit. I.e. support for different VM Managers. Again lack of standards are is the issue. Potential solutions based on CIMI and OCCI *
    • 30. * * where are we with Cloud standards? * fragmented landscape with many parallel standards development efforts * limited interaction between groups; difficult consensus-based path * initiatives like SIENA and large institutions like NIST help facilitate this collaboration
    • 31. *

    ×