1 / 29

Achieving Visibility in the Cloud

We provide strategic direction, design and plan execution for ... Large Hosting Service Provider Cloud Services business case, design and implementation ...

ryanadan
Download Presentation

Achieving Visibility in the Cloud

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

    Slide 1:Achieving Visibility in the Cloud EGI Event, Vilnius - December 2009

    Liora Rosenblum, Senior Consultant International Business Development

    Slide 2:Agenda

    Cloud Services Sample Client Engagement Industry Position GlassHouse Intellectual Property Differentiators

    Slide 4:What is Cloud Computing? Cloud Confusion

    An abundance of differing opinions “We’ve redefined Cloud Computing to include everything that we already do.” Larry Ellison, CEO Oracle “It’s stupidity. It’s worse than stupidity: it’s a marketing hype campaign.” Richard Stallman, Free Software Foundation "It's definitely not hype. Any technology leader who thinks it's hype is coming at it from the same place where technology leaders said the Internet is hype.” Vivek Kundra, Federal CIO ACM study found 22 definitions of cloud! Everyone from academia (UC Berkeley) to analysts (McKinsey) weighing in

    Slide 5:What is Cloud Computing? Purists, Marketing, and Pragmatism

    Which of these are cloud computing? A. Application Service Provider (ASP) B. Infrastructure as a Service (IaaS) Software as a Service (SaaS) C. Application Development Platform as a Service D. Grid Computing E. Utility Computing F. Platform as a Service (PaaS) G. All of the above Convergence of: Virtualization Utility computing model Distributed computing

    Slide 6:IT As An Internal Cloud Services Provider Requirements for Success

    Service Management Maturity Cost Transparency throughout the IT supply chain Service Definition and SLA Tracking Develop a real demand forecasting capability End the practice of over-provisioning resources Develop effective business-based metrics End the project-based funding model for CapEx It doesn’t work in a world of shared resources Metrics, metrics, metrics Performance, resources capacities, per-unit-costs, and trending

    Slide 7:Our Role in the Cloud

    We are a Cloud-Enabler We offer services to help customers prepare their environment to work effectively with cloud technologies We provide strategic direction, design and plan execution for customers to establish their own private/internal clouds We provide strategic direction, design and plan execution for customers shifting pieces of their environment to an external cloud We provide methodology and tools to move up the Service Provider Maturity Continuum We offer services to help customers monitor and meter their cloud environments – internal and external

    Slide 8:GlassHouse Cloud Services

    Slide 9:GlassHouse Cloud Services

    Slide 10:Customer Example Large Hosting Service Provider – Cloud Services business case, design and implementation

    Slide 11:Large Hosting Service Provider – Cloud Services Programme Objectives

    Phase 1 (Completed): Define Cloud services roadmap for the hosting service provider to take to market Define “Cloud Service 1.0” make-up Produce market opportunity analysis for “Cloud Service 1.0” Position opportunity with vendors and partners Phase 2 (Proposed): Implement “Cloud 1.0” and migrate Internal IT to become a reference case Produce commercial launch materials Position benefits to customer base Launch “Cloud 1.0” March 2010 Develop and implement “Cloud 2.0” and “Cloud 3.0” offerings

    Slide 12:Large Hosting Service Provider – Cloud Services Programme Workflow

    LAUNCH Use Case High Level Service Definition Service Development Roadmap Reference Technical Architecture Support Model Process and Policy Frameworks High-Level Skills Matrix Cost Model High Level Business Case Key Characteristics: On-demand self-service. A consumer can unilaterally provision computing capabilities, such as server time and network storage, as needed without requiring human interaction with each service’s provider. Ubiquitous network access. Capabilities are available over the network and accessed through standard mechanisms that promote use by heterogeneous thin or thick client platforms (e.g., mobile phones, laptops, and PDAs). Location independent resource pooling. The provider’s computing resources are pooled to serve all consumers using a multi-tenant model, with different physical and virtual resources dynamically assigned and reassigned according to consumer demand. The customer generally has no control or knowledge over the exact location of the provided resources. Examples of resources include storage, processing, memory, network bandwidth, and virtual machines. Rapid elasticity. Capabilities can be rapidly and elastically provisioned to quickly scale up and rapidly released to quickly scale down. To the consumer, the capabilities available for rent often appear to be infinite and can be purchased in any quantity at any time. Pay per use. Capabilities are charged using a metered, fee-for-service, or advertising based billing model to promote optimization of resource use. Examples are measuring the storage, bandwidth, and computing resources consumed and charging for the number of active user accounts per month. Clouds within an organization accrue cost between business units and may or may not use actual currency. Note: Cloud software takes full advantage of the cloud paradigm by being service oriented with a focus on statelessness, low coupling, modularity, and semantic interoperability. Delivery Models: Cloud Software as a Service (SaaS). The capability provided to the consumer is to use the provider’s applications running on a cloud infrastructure and accessible from various client devices through a thin client interface such as a Web browser (e.g., web-based email). The consumer does not manage or control the underlying cloud infrastructure, network, servers, operating systems, storage, or even individual application capabilities, with the possible exception of limited user-specific application configuration settings. Cloud Platform as a Service (PaaS). The capability provided to the consumer is to deploy onto the cloud infrastructure consumer-created applications using programming languages and tools supported by the provider (e.g., java, python, .Net). The consumer does not manage or control the underlying cloud infrastructure, network, servers, operating systems, or storage, but the consumer has control over the deployed applications and possibly application hosting environment configurations. Cloud Infrastructure as a Service (IaaS). The capability provided to the consumer is to rent processing, storage, networks, and other fundamental computing resources where the consumer is able to deploy and run arbitrary software, which can include operating systems and applications. The consumer does not manage or control the underlying cloud infrastructure but has control over operating systems, storage, deployed applications, and possibly select networking components (e.g., firewalls, load balancers). Deployment Models: Private cloud. The cloud infrastructure is owned or leased by a single organization and is operated solely for that organization. Community cloud. The cloud infrastructure is shared by several organizations and supports a specific community that has shared concerns (e.g., mission, security requirements, policy, and compliance considerations). Public cloud. The cloud infrastructure is owned by an organization selling cloud services to the general public or to a large industry group. Hybrid cloud. The cloud infrastructure is a composition of two or more clouds (internal, community, or public) that remain unique entities but are bound together by standardized or proprietary technology that enables data and application portability (e.g., cloud bursting). Key Characteristics: On-demand self-service. A consumer can unilaterally provision computing capabilities, such as server time and network storage, as needed without requiring human interaction with each service’s provider. Ubiquitous network access. Capabilities are available over the network and accessed through standard mechanisms that promote use by heterogeneous thin or thick client platforms (e.g., mobile phones, laptops, and PDAs). Location independent resource pooling. The provider’s computing resources are pooled to serve all consumers using a multi-tenant model, with different physical and virtual resources dynamically assigned and reassigned according to consumer demand. The customer generally has no control or knowledge over the exact location of the provided resources. Examples of resources include storage, processing, memory, network bandwidth, and virtual machines. Rapid elasticity. Capabilities can be rapidly and elastically provisioned to quickly scale up and rapidly released to quickly scale down. To the consumer, the capabilities available for rent often appear to be infinite and can be purchased in any quantity at any time. Pay per use. Capabilities are charged using a metered, fee-for-service, or advertising based billing model to promote optimization of resource use. Examples are measuring the storage, bandwidth, and computing resources consumed and charging for the number of active user accounts per month. Clouds within an organization accrue cost between business units and may or may not use actual currency. Note: Cloud software takes full advantage of the cloud paradigm by being service oriented with a focus on statelessness, low coupling, modularity, and semantic interoperability. Delivery Models: Cloud Software as a Service (SaaS). The capability provided to the consumer is to use the provider’s applications running on a cloud infrastructure and accessible from various client devices through a thin client interface such as a Web browser (e.g., web-based email). The consumer does not manage or control the underlying cloud infrastructure, network, servers, operating systems, storage, or even individual application capabilities, with the possible exception of limited user-specific application configuration settings. Cloud Platform as a Service (PaaS). The capability provided to the consumer is to deploy onto the cloud infrastructure consumer-created applications using programming languages and tools supported by the provider (e.g., java, python, .Net). The consumer does not manage or control the underlying cloud infrastructure, network, servers, operating systems, or storage, but the consumer has control over the deployed applications and possibly application hosting environment configurations. Cloud Infrastructure as a Service (IaaS). The capability provided to the consumer is to rent processing, storage, networks, and other fundamental computing resources where the consumer is able to deploy and run arbitrary software, which can include operating systems and applications. The consumer does not manage or control the underlying cloud infrastructure but has control over operating systems, storage, deployed applications, and possibly select networking components (e.g., firewalls, load balancers). Deployment Models: Private cloud. The cloud infrastructure is owned or leased by a single organization and is operated solely for that organization. Community cloud. The cloud infrastructure is shared by several organizations and supports a specific community that has shared concerns (e.g., mission, security requirements, policy, and compliance considerations). Public cloud. The cloud infrastructure is owned by an organization selling cloud services to the general public or to a large industry group. Hybrid cloud. The cloud infrastructure is a composition of two or more clouds (internal, community, or public) that remain unique entities but are bound together by standardized or proprietary technology that enables data and application portability (e.g., cloud bursting).

    Slide 13:Large Hosting Service Provider – Cloud Services Detailed Activities - Define Cloud Services and Roadmap

    Activities: Workshop preparation – current services and capabilities, market requirements Initial workshop – high-level aspirational service offerings Requirements analysis – dependent technology and toolsets, competitive offerings Finalise high-level service definitions – including initial service offering and development roadmap Deliverables: High Level Service Definition Service Development Roadmap

    Slide 14:Large Hosting Service Provider – Cloud Service Detailed Activities - Develop Service Delivery Model

    Activities: Define underlying service delivery model to deliver the agreed services, i.e. Technology – Platforms, O/S, storage, backup and DR Process – Service provider and external customer process requirements Governance – Compliance, security Tools – Monitoring and management, customer tools (e.g. self service provisioning, capacity management) Support Model – Service provider versus customer roles & responsibilities SLAs – provisioning, processes, support, performance, etc. Skills - technical, operational, commercial Deliverables: Reference Technical Architecture Support Model Process and Policy Frameworks High-Level Skills Matrix

    Slide 15:Large Hosting Service Provider – Cloud Services Detailed Activities - Build Supporting Business Case

    Activities: Develop the business case to identify the level of opportunity against the level of investment required Assess the market opportunity, i.e. potential customer volumes and usage Define fully burdened costs for service delivery and the likely service pricing and revenue Identify the costs for implementation Model the potential net profitability, including timescales for ROI Deliverables: Cost Model High-level Business Case

    Slide 16:Large Hosting Service Provider – Cloud Services Detailed Activities - Cloud 1.0 Design and Implementation

    Slide 17:Large Hosting Service Provider – Cloud Services Sample Deliverables - Service Definition and Design

    Items Covered: Cloud Computing Overview Cloud Delivery Model Cloud Service 1.0 Definition Service Management Requirements Security and Data Privacy Requirements Data Centre Facility Requirements SLA Framework Customer Engagement Model Project Constraints and Risks Service Enablement Roadmap Reference Technical Architecture

    Slide 18:Large Hosting Service Provider – Cloud Services Sample Deliverables - Cloud Service Model

    Slide 19:Large Hosting Service Provider – Cloud Services Sample Deliverables - Cloud Portal Definition

    Slide 20:Large Hosting Service Provider – Cloud Services Sample Deliverables - Cloud Service Roadmap

    Slide 21:Large Hosting Service Provider – Cloud Services Sample Deliverables - Reference Technical Architecture

    Slide 22:Industry Position

    Cloud is not going away – the hype will drive current and startup vendors to significant innovation GlassHouse clients will benefit from these efforts Our primary clients are mid to large enterprises Cloud Services for these clients are based on the following assumptions: In the near term Private Cloud Services will be more utilized than External, Public or Federated The most important CSF for Cloud Services within the Enterprise, is maturity within the Service Provider Model. CIO’s will have to provide an answer to Public Cloud Services VMware owns the x86 platform virtualization market and will be the primary vendor short term for Internal Cloud infrastructure Enterprise storage vendors will be pushed to provide more cost effective options to compete with Cloud providers

    Slide 24:GlassHouse Consulting Framework

    Unique Delivery Methods Breaks down IT “ Towers” to accelerate time to deployment Breaks with traditional linear consulting methods (assessment model) Client-focused and collaborative in nature Shifts level of effort from discovery to deliverables Service Provider Model Framework (SPM) Service Process Maturity Model Define Services and Service Levels Map Costs to Service Levels Provide Cost Transparency ITIL/ITSM aligned Facilitated Design & Planning Framework (Accelerate) Facilitated session methodology Proven methodology for accelerating time to value

    Slide 25:Accelerate Delivery Framework

    Slide 26:GlassHouse Technical Tools

    ROI Modeling Tools Built by IT experts, built for IT capital/operational decisions Removes complexity from financial analysis and scenario modeling Fast-tracks path to key financial views required for strategic decisions Service Provider Model toolsets (SPM) Define Services and Service Levels Map Costs to Service Levels Provide Cost Transparency ITIL/ITSM aligned

    Slide 27:Key Differentiators

    Cloud Model aligns very well with core GlassHouse approach and capabilities Service Provider Model Virtualization and Platform Services Storage & Data Protection Services Security Services Monitoring and Metrics Services All of these components are prerequisites for a successful private cloud deployment Service portfolio leverages GlassHouse capabilities to enable clients to: Determine the impact and opportunity to leverage Cloud-based services Select a Cloud Service Provider that best aligns with their business requirements Develop an internal Cloud Services Capability Delivery frameworks scale from mid-market to large enterprise Practice SME’s from virtualization, data center, security, ITSM/SPM, storage Delivery methods offer cost-competitive and efficient means to engage customers and achieve results Financial modeling and analysis focuses on real-world customer needs

    Slide 29:Thank You

    Liora Rosenblum, Senior Consultant +972 9 7622 700 lioraro@glasshouse.com www.glasshouse.com

More Related